DYNDUMP

Derivation: DYNamic DUMP

The DYNDUMP runtime option provides a way to obtain dynamic dumps of user applications that would ordinarily be lost due to the absence of a SYSMDUMP, SYSUDUMP, or SYSABEND DD statement. The dynamic dump is written when:

Certain types of ABENDs occur. You can select if a U4039 ABEND or other U40xx ABEND types can cause a dump to be collected.
The first suboption defines the high level qualifier of the dynamic dump data set name.
The second suboption controls when dynamic dumps are taken for U4039 ABENDS.
The third suboption controls when dynamic dumps are taken for other U40xx ABENDS.

Restriction: The dump is written to a z/OS® data set. It cannot be part of a z/OS UNIX file system.

The non-CICS default value is DYNDUMP(*userid,NODYNAMIC,TDUMP).

DYNDUMP is ignored under CICS®.

The AMODE 64 default value is DYNDUMP(*userid,NODYNAMIC,TDUMP).


Syntax

               .-*USERID----.     .-NODYNAMIC-.      
>>-DYNdump--(--+-hlq--------+--,--+-DYNAMIC---+--,-------------->
               '-*TSOPREFIX-'     +-FORCE-----+      
                                  '-BOTH------'      

   .-TDUMP---.      
>--+-NOTDUMP-+--)----------------------------------------------><

hlq

is a high level qualifier for the dynamic dump data set to be created. This is concatenated with a time stamp consisting of the Julian day and the time of the dump. The job name or PID can also be part of the name if the combined length of hlq and the time stamp is 35 characters or less. The hlq value is limited to 26 characters including dot ( . ) separators. hlq allows three keywords:

*USERID: tells Language Environment to use the user ID associated with the job step task as the high level qualifier for the dynamic dump data set.
*TSOPREFIX or TSOPRE: tells Language Environment to use the TSO/E prefix. Restriction: The prefix is only valid in a TSO/E environment. If the prefix is not available, the user ID is used.

Each keyword may be followed by additional characters to be used to create the dataset name. When appended to the USERID or the TSO prefix, they form the hlq used when creating the dump data set.

The data set name is limited to 44 characters. If the combined length of hlq and the time stamp is 35 characters or less, the job name or PID is added to the data set name. If the system is using multilevel security, the SECLABEL is used as the second qualifier. If hlq contains multiple qualifiers, only the first is used, followed by the SECLABEL. The format of the data set name is:

When the application is not exec()ed and not multilevel security:
```
hlq.Djjj.Thhmmsst.jobname
```
When the application is exec()ed and not multilevel security:
```
hlq.Djjj.Thhmmsst.Pppppppp
```
When the application is multilevel security and not exec()ed:
```
hlq.MLS-level.Djjj.Thhmmsst.jobname
```
When the application is both multilevel security and exec()ed:
```
hlq.MLS-level.Djjj.Thhmmsst.Pppppppp
```

For U4039 ABENDS

The following suboptions are used for U4039 ABENDS only:

DYNAMIC: Language Environment creates a dynamic dump automatically when the application has not already specified one of the dump ddnames, (for example, SYSUDUMP).
NODYNAMIC: Language Environment does not create a dynamic dump if no dump DD names are specified.
FORCE: Language Environment always creates a dynamic dump even if other dump DD names have been specified. The SYSnnnnn DD card is ignored if it exists. FORCE should not be used as the default.
BOTH: Language Environment creates a dynamic dump and, if a SYSnnnnn DD name exists, a dump is also written to the DD. BOTH should not be used as the default.

For U40xx ABENDS

The following suboptions are used for other U40xx ABENDS only. Existing SYSnnnnn DD statements are also honored.

TDUMP: Language Environment creates a dynamic dump automatically.
NOTDUMP: Language Environment does not create a dynamic dump.

Usage notes

Recommendations:
- Set up an hlq to which everyone can write.
- Do not use FORCE or BOTH as the default for the U4039 ABENDS.
The DYNDUMP runtime option is ignored under CICS.
When an ABEND occurs during Language Environment initialization, the dynamic dump is not created if runtime options have not been processed yet.
When the dynamic dump fails, messages are written to the operator's console or the job log (for batch). These are written by the IEATDUMP system service, by Language Environment, or by RACF®.
When an ABEND is issued without the DUMP option, no dump is generated.
When Language Environment® terminates with a U4038 abend, the U4038 abend is issued without the DUMP option. Therefore, no system dump is generated, and DYNDUMP does not collect a dump for this ABEND.
The job name is taken from the JOBNAME system symbol.
- A dump for a TSO application uses the user ID of the JOBNAME.
- For a batch job, JOBNAME is taken from the JOB card in the JCL.
- In the shell, JOBNAME is the user ID with a suffix.

CICS considerations

DYNDUMP(smith, force, notdump)
A dynamic dump is generated only for ABEND code U4039. Other SYSnnnnn DD cards are ignored. Other ABENDs might cause a dump to be created if a SYSnnnnn DD card exists. The dynamic dump data set name will be similar to SMITH.D012.T112245.JOB11.
DYNDUMP(smith,DYNAMIC,TDUMP)
A dynamic dump is created if no SYSnnnnn is specified and the ABEND code is U4039. The data set name will be similar to SMITH.D117.T235900.JOBZ2.
DYNDUMP(*TSOPREFIX,NODYNAMIC,TDUMP)
A dynamic dump is generated only for ABEND code U40xx. The data set name will be similar to SMITH.D287.T234560.JOBZ2.
DYNDUMP(*USERID,NODYNAMIC,TDUMP)
A dynamic dump for a U4039 ABEND is taken to SMITH.D109.T234512.JOBZ3.
DYNDUMP(*USERID.HOT.DUMPS,NODYNAMIC,TDUMP)
DYNDUMP(*TSOPRE.A1234567.B1234567,NODYNAMIC,TDUMP)