(ZOS) Dump controls for IBM service

Use these controls to gather information that can be used by IBM service.

ras_minorcode_action= value

Determines the default behavior for gathering documentation about system exception minor codes.

CEEDUMP

Captures callback and offsets.

Tip: It takes time for the system to take CEEDUMPs and this may cause transaction timeouts. For instance, if the WebSphere variable transaction_defaultTimeout is set to 30 seconds, the application transaction may time out because processing a CEEDUMP can take longer than 30 seconds. To prevent this from happening, either:

• Increase the transaction timeout value, or
• Code ras_minorcode_action=NODIAGNOSTICDATA and make sure the ras_trace_minorCodeTraceBacks variable is not specified.

TRACEBACK

Captures Language Environment and z/OS UNIX traceback data.

SVCDUMP

Captures an MVS™ dump (but will not produce a dump in the client).

NODIAGNOSTICDATA

That no diagnostic data will be collected, even if CEEDUMP, TRACEBACK, or SVCDUMP processing occurs because of another WebSphere variable setting. For example, if you code both of the following variables, traceback processing occurs but none of the traceback data is collected: ras_minorcode_action=NODIAGNOSTICDATA and ras_trace_minorCodeTraceBacks=ALL

Default: NODIAGNOSTICDATA

Example:

 ras_minorcode_action=SVCDUMP

ras_trace_minorCodeTraceBacks= value

Enables traceback of system exception minor codes. Values are:

ALL|all

Enables traceback for all system exception minor codes.

Enables traceback of system exception minor codes. Values are:

• minor_code Enables traceback for a specific minor code.

  Example: Type

   1234
  

  for minor code

   C9C21234
  

• (null value) The default. This setting will not cause gathering of a traceback.

  Default: (null value)

  Example:

   ras_trace_minorCodeTraceBacks=all
  

Diagnose problems (using diagnosis tools)

IBM service call preparation