Although an abnormal termination not covered by a recovery environment is unlikely to occur in the OAM address space, a SYSABEND DD statement is included in the default cataloged procedure (member OAM in SYS1.PROCLIB) shipped with the product. This DD statement directs the system to produce a dump if an abnormal termination is encountered. Because SYSOUT=A is specified, any dump produced is written to a system output data set. The system output data set is printed when the OAM address space stops.

Depending on the type of dump required, you can change the SYSABEND DD statement in the default cataloged procedure to a SYSMDUMP or SYSUDUMP DD statement.

Most OAM code is covered by some type of recovery environment (ESTAE, ESTAI or FRR). If an abnormal termination occurs, the recovery routine will cause an SVC dump to be written to a system dump data set (SYS.DUMPxx). The title that is associated with the SVC dump indicates the:

1. SVC dump that is associated with OAM
2. Component ID that is associated with OAM, 5695DF180
3. Name of the OAM module that is generating the SVC dump.

For diagnostic purposes, there are occasions when an SVC dump of the OAM address space and its associated data is required. To make this task easier, OAM provides a DUMP command that will take an SVC dump of the OAM address space, with all of the SDATA parameters that OAM normally requests for problem diagnosis. This command also provides the ability to dump, along with OAM, any address spaces that have work queued to the OAM address space, specific address spaces or specific MVS jobs, specified by the operator on the command invocation.

For more information on the OAM DUMP command, including the command syntax, see z/OS DFSMS OAM Application Programmer's Reference. Also, see z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support.