Home
Using Fault Analyzer
Performing Java analysis
Java application samples
The JCL samples provided in the IDI.SIDISAM1 sample data set demonstrate how to use Java™ and interlanguage calls with Fault Analyzer.
Sample 5 (IDISJAV5): C++ program invoking Java in batch
The JCL in sample IDI.SIDISAM1(IDISJAV5) demonstrates how to use Fault Analyzer when using a 31-bit or 64-bit C++ program to invoke Java™ in batch. It includes Java calling a C++ DLL located in a PDSE data set member.

Using Fault Analyzer
- Introduction
- Real-time analysis
- The Fault Analyzer ISPF interface
- Performing batch reanalysis
- Performing interactive reanalysis
- Performing CICS system abend dump analysis
- Formatting a CICS auxiliary trace data set
- Performing Java analysis
  - Selecting a Java dump data set
    Specification of a Java™ dump data set to be analyzed is done by first selecting File > Analyze MVS Dump Data Set from the Fault Entry List display.
  - Java fault entry reanalysis
  - Displaying the Java information in the interactive report
  - Java event replacement in Fault Analyzer event list
    When an abend includes Java™ events, Fault Analyzer requests a system dump of the JVM. This Java system dump is analyzed by Fault Analyzer using Diagnostic Tool Framework for Java (DTFJ) APIs.
  - Java information reporting limitations
  - Java application samples
    The JCL samples provided in the IDI.SIDISAM1 sample data set demonstrate how to use Java™ and interlanguage calls with Fault Analyzer.
    - Sample 1 (IDISJAV1): Enterprise PL/I invoking Java in batch
      The JCL in sample IDI.SIDISAM1(IDISJAV1) demonstrates how to use Fault Analyzer when Enterprise PL/I invokes Java™ in batch. It includes Java calling an Enterprise PL/I DLL that is located in a PDSE data set member.
    - Sample 2 (IDISJAV2): Enterprise COBOL invoking Java in batch
      The JCL in sample IDI.SIDISAM1(IDISJAV2) demonstrates how to use Fault Analyzer when Enterprise COBOL invokes Java in batch. It includes Java calling an Enterprise COBOL DLL that is located in a PDSE data set member.
    - Sample 3 (IDISJAV3): 64-bit Enterprise PL/I invoking Java in batch
      The JCL in sample IDI.SIDISAM1(IDISJAV3) demonstrates how to use Fault Analyzer when 64-bit Enterprise PL/I invokes 64-bit Java™ in batch. It includes Java calling an Enterprise PL/I DLL that is located in a PDSE data set member.
    - Sample 4 (IDISJAV4): IMS Java batch processing sample
      The JCL in sample IDI.SIDISAM1(IDISJAV4) demonstrates how to use Fault Analyzer with IMS™ Java™ batch processing (JBP) regions. In the sample, IMS calls a Java program, which in turn calls COBOL and assembler programs.
    - Sample 5 (IDISJAV5): C++ program invoking Java in batch
      The JCL in sample IDI.SIDISAM1(IDISJAV5) demonstrates how to use Fault Analyzer when using a 31-bit or 64-bit C++ program to invoke Java™ in batch. It includes Java calling a C++ DLL located in a PDSE data set member.
    - Sample 6 (IDISJAV6): Call a Java batch application with the Fault Analyzer wrapper utility
      The JCL in sample IDI.SIDISAM1(IDISJAV6) demonstrates how to use the Fault Analyzer Java™ wrapper utility to invoke a Java class with a main() method within a try-catch block. Unhandled exceptions are automatically caught and fault entries are created using the Snap.dump() method.
- The Fault Analyzer report
- Using non-ISPF interfaces to access Fault Analyzer history files

Sample 5 (IDISJAV5): C++ program invoking Java in batch

The JCL in sample IDI.SIDISAM1(IDISJAV5) demonstrates how to use Fault Analyzer when using a 31-bit or 64-bit C++ program to invoke Java™ in batch. It includes Java™ calling a C++ DLL located in a PDSE data set member.

For both the 31-bit and the 64-bit Snap.dump(), the Fault Analyzer report displays only Java™ information. Both include source code but no Java™ variable information, because the Java™ virtual machine (JVM) does not provide a mechanism to obtain variable information.

These are the sample results expected in the Fault Analyzer report for both the 31-bit and 64-bit C++ abend reports:

The synopsis section includes the line of C++ source code where the abend occurred.
The event summary includes both Java™ and C++ calls in a single view.
In the C++ events, compiler listings are used for source code information, due to the NODEBUG compiler option.
In the Java™ events, source code information is displayed along with stack frame reference information.