A CICSPlex® SM-requested dump may be one of the following:
An SDUMP is scheduled for all abends in the CAS or any address space connected to it, except when:
In addition to the failing address space, the master address space is always dumped so as to provide the MTRACE. If the abend occurred while in cross-memory mode, all the address spaces involved are also dumped. Because the CAS is often required to correctly diagnose a problem, it is always dumped, regardless of its involvement in the failure.
The CAS also provides DAE suppression support. Only one dump is taken for a specific set of symptoms. If it is a recordable failure, LOGREC entries are always written, but only one SDUMP is created. Symptom records are created and passed to SDUMP to prevent duplicate SDUMPs.
If an abend occurs during CMAS initialization, the CMAS terminates. CICSPlex SM takes an SDUMP with a dump code of EYUXL001 and writes a failure summary to the job log and console.
If an abend occurs during MAS initialization, the MAS agent code terminates; the CICS® system continues to initialize, but it is not known to CICSPlex SM. CICSPlex SM takes a transaction dump with a dump code of EYUK and writes a failure summary to the job log and console.
If an abend occurs while a CICSPlex SM PC routine is executing, the functional recovery routine (FRR) takes an SDUMP with a title whose format is as follows:
CICSPlex SM (rrrr) Abend,(PC Set Name),(PC Routine Name),
(Job Name),(SID),(date),(time)
where:
For each PC Set Name, the PC Routine Names are as follows:
After it takes the SDUMP, the PC routine returns to its caller with a return code indicating that an abend occurred during processing.
[[ Contents Previous Page | Next Page Index ]]