Generating a suppressed dump

You may want to obtain a dump that is being suppressed. Perhaps the first dump was ignored and thrown out, but since then the dump has been requested often enough so that you would like to analyze the dump. Do the following to obtain the suppressed dump through the IPCS TAKEDUMP option:
  1. Customize the TSO user ID that will invoke the TAKEDUMP action. Make sure it:
    • has authority to issue an MVS™ operator SET command and, if DAE is active in a sysplex, the ROUTE command
    • has RACF® UPDATE access to the DAE data set.
  2. Ensure that the ADYSET01 member(s) contains DAE=STOP (or DAE=STOP,GLOBALSTOP in a sysplex).
  3. Check that the active IKJTSOxx member includes the program name ADYOPCMD in the AUTHCMD NAMES section.
  4. In a sysplex, the maximum benefit is realized when DAE is started using ADYSETxx members which contain at least SHARE(DSN) — enabling shared data set activities.
  5. Use the IPCS DAE dialog Panel to issue action code T (the TAKEDUMP option) on the line showing the symptom string of interest.
To process the TAKEDUMP option of the IPCS DAE dialog, DAE processing is stopped, dialog processing occurs, and DAE processing is restarted on the systems involved. There are some cases where a particular system may end up using different DAE parameters from those it was previously using. Table 1 illustrates possible results.
For this discussion there are two systems (SY1 and SY2), and five ADYSETxx members involved. Members ending with G1 and G2 include GLOBAL(DSN,OPTIONS) parameters. Members ending with S1 and S2 have SHARE(DSN,OPTIONS) without GLOBAL options. The center column in Table 1 indicates the system where the TSO user is issuing the TAKEDUMP request.
Table 1. Examples of when DAE parameters may change
Start State TSO Final State
G1 G1 SY1 G1 G11
S1 S2 SY1 S1 S12
S1 S2 SY2 S2 S22
S1 G1 SY1 S1 S12
S1 G2 SY2 G2 G22
G2 S2 SY2 S2 S22
00 * SY1 00 *3
  1. GLOBAL(DSN) systems remain synchronized.
  2. When all systems are NOT in GLOBAL(DSN) mode, the system will be started using the member last active on the system where the IPCS TAKEDUMP dialog runs.
  3. No change to other systems if all work is done on a system which is not sharing the DAE data set. Here, ADYSET00 contains the default IBM—supplied values.
  4. The commands necessary to accomplish the task are issued by the TSO user at their dispatching priority. It is possible that the system may not dispatch the TSO user due to that dispatching priority, and therefore the action may not complete in a timely manner.

The system will generate the next dump for the symptom string. After that dump, DAE resumes suppressing dumps for the symptom string.

Note: Despite specifying action code T, the dump might still be suppressed. See Determining why a dump was suppressed for the reasons, other than DAE suppression.