Home
Using Z Abend Investigator
Performing Java analysis
Java application samples
The JCL samples provided in the HFZ.SHFZSAM1 sample data set demonstrate how to use Java™ and interlanguage calls with Z Abend Investigator.
Sample 5 (HFZSJAV5): C++ program invoking Java in batch
The JCL in sample HFZ.SHFZSAM1(HFZSJAV5) demonstrates how to use Z Abend Investigator 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 Z Abend Investigator
- Introduction
- Real-time analysis
- The Z Abend Investigator 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 Z Abend Investigator event list
    When an abend includes Java™ events, Z Abend Investigator requests a system dump of the JVM. This Java system dump is analyzed by Z Abend Investigator using Diagnostic Tool Framework for Java (DTFJ) APIs.
  - Java information reporting limitations
  - Java application samples
    The JCL samples provided in the HFZ.SHFZSAM1 sample data set demonstrate how to use Java™ and interlanguage calls with Z Abend Investigator.
    - Sample 1 (HFZSJAV1): Enterprise PL/I invoking Java in batch
      The JCL in sample HFZ.SHFZSAM1(HFZSJAV1) demonstrates how to use Z Abend Investigator 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 (HFZSJAV2): Enterprise COBOL invoking Java in batch
      The JCL in sample HFZ.SHFZSAM1(HFZSJAV2) demonstrates how to use Z Abend Investigator 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 (HFZSJAV3): 64-bit Enterprise PL/I invoking Java in batch
      The JCL in sample HFZ.SHFZSAM1(HFZSJAV3) demonstrates how to use Z Abend Investigator 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 (HFZSJAV4): IMS Java batch processing sample
      The JCL in sample HFZ.SHFZSAM1(HFZSJAV4) demonstrates how to use Z Abend Investigator 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 (HFZSJAV5): C++ program invoking Java in batch
      The JCL in sample HFZ.SHFZSAM1(HFZSJAV5) demonstrates how to use Z Abend Investigator 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 (HFZSJAV6): Call a Java batch application with the Z Abend Investigator wrapper utility
      The JCL in sample HFZ.SHFZSAM1(HFZSJAV6) demonstrates how to use the Z Abend Investigator 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 Z Abend Investigator report

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

The JCL in sample HFZ.SHFZSAM1(HFZSJAV5) demonstrates how to use Z Abend Investigator 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 Z Abend Investigator 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 Z Abend Investigator 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.