Dumping diagnostic information

Dumps contain diagnostic information that can be used when investigating system problems. Various options are available when obtaining dumps.

Dump options are available for use with the MVS™ system command /F <JOBNAME>,APPL=DUMP.

To get help on the available dump options, issue the following command:
/F <JOB_NAME>,APPL=DUMP,?

If the IBM® JVM is used, a subset of the options can be used to provide JVM dumps. The IBM JVM can produce a Java™ heap dump, a Java dump, or a Java system dump. These are produced by a running JVM, and can be requested during typical operation of the CICS® Transaction Gateway. The dumps contain diagnostic information that can be used when investigating system problems.

For further information on IBM JVM dumps, see the IBM Java Diagnostic Guide at IBM Java Diagnostic Guide.

Parameters

There are no short forms of the parameter names.

Option Description
ALL Generates all dumps. This option must be specified as the only option and cannot be combined with other dump options.
CTGINFO Generates a dump containing information about the configuration of CICS Transaction Gateway.
HEAP Generates a Java heap dump.
JAVA Generates a Java dump.
JVM Generates a dump containing current JVM memory usage.
JVMSTACK Generates a dump containing only the Java call stack.
SYSTEM Generates a Java system dump.

Responses

The Gateway daemon responds to a dump request with a message to the console. In some cases, if the request takes a long time to complete, the message NO RESPONSE RECEIVED is output, although the dump is produced. The stderr log contains the location of the dump.

IBM JVM dump responses

Messages from the JVM contain the name of the dump, and indicate whether the dump was successful. The JVM messages are sent to the stderr error stream.

Possible responses to the dump request are as follows:

  • The Gateway daemon successfully processed the dump request; the dump request completed successfully.
  • Null response received from the Gateway daemon during the dump request; the Gateway daemon received the dump request, but returned an invalid or null response.
  • The dump type is unsupported in the remote JVM; the remote JVM does not support the requested dump type.
  • An invalid response was returned from the Gateway daemon during the dump request; the Gateway daemon received the dump request, but the response returned was invalid.
  • The Gateway daemon encountered a serious error while processing the dump type; the Gateway daemon received the dump request, but an error was detected.
  • Some dump types are unsupported in the remote JVM; the remote JVM executing the Gateway daemon does not support some dump types.

Reference Reference

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//ctgzos/admparm_dumpall.html