Because CICSPlex® SM has a presence in two major parts of your environment, MVS™ and CICS®, unexpected dumps may be produced at either level.
MVS can cause a dump to be taken for a CICSPlex SM component in the CAS, a CMAS, or a TSO address space. This type of dump is an indication of a problem with the end-user interface.
When an unexpected dump occurs under MVS, CICSPlex SM writes an abend indication and summary to either the console and job log, or to the TSO terminal. The first message in the abend summary is usually:
BBMZE001E Recovery manager ESTAE entered
CICSPlex SM also produces LOGREC records related to the abend and, when appropriate, one of the following dumps:
Figure 12 is an example of a CICSPlex SM dump produced under MVS.
BBMZE001E Recovery manager ESTAE entered
BBMZE002E ABEND S00C4-00000011 for ASID=0034-P; 0034/0034/0034,
BBMZE002E CSECT=MXY10 (MXY13+0A46)
BBMZE003E Error PSW=078D1000 89608962, IL/CC/IC=04/01/0011, LTA=7F4AD000
BBMZE004E Data at PSW-0A 47F0100A DD003000 F00044E0 10040520 47702008 4113E001
BBMZE005E Error registers 00-03 7F68B730 89608958 00000010 7F4AD136
BBMZE005E ............... 04-07 09609A60 09607F1C 7F68B7D0 7F68B7D0
BBMZE005E ............... 08-11 7F4C10D8 7F68B7D0 7F68B7D0 00000002
BBMZE005E ............... 12-15 7F6852E0 7F68B640 0000008A 007719A0
BBMZE005E RB registers 00-03 00000000 00000000 00000000 00000000
BBMZE005E ............... 04-07 00000000 00000000 00000000 00000000
BBMZE005E ............... 08-11 00000000 00000000 00000000 00000000
BBMZE005E ............... 12-15 00000000 00000000 00000000 00000000
BBMZE005E Retry registers 00-03 7F68B730 7F68BA50 00000010 7F4AD136
BBMZE005E ............... 04-07 09609A60 09607F1C 7F68B7D0 7F68B7D0
BBMZE005E ............... 08-11 7F4C10D8 7F68B7D0 7F68B7D0 00000002
BBMZE005E ............... 12-15 7F6852E0 7F68B640 0000008A 007719A0
BBMZE006E Linkage trace MXY13,MXBB2,MXB62,MXB71,MQ4S2,MXB65,MXBG4,MXCB2,MXC74
BBMZE006E ............. MXPMAIN,MXL01,MXUC2,MXG30,GSI=0100041E,MXL04,MXDRX
BBMZE006E ............. MXZRX
BBMZE802I Recovery manager ESTAE 'SDUMP' complete - RC=x'0000'
BBMZE801I Recovery manager ESTAE requested LOGREC recording
BBMZE803I Recovery manager ESTAE requested retry
Each MVS SDUMP has a title that consists of a summary of the abend. The title includes:
Here is an example MVS/ESA SDUMP title:
BBM/ZE ABEND S0C4, PSW=078D1000 89608962, ASID=0034-P/0034/0034/0034,
CSECT=MXY10(MXY13+0A46)
In this example:
Abend code: | S0C4 |
PSW at time of error: | 078D1000 89608962 |
Failing ASID: | 0034 |
Primary, secondary, and home ASIDs: | 0034, 0034, 0034 |
Failing CSECT: | MXY10 |
Failing function and offset: | MXY13 + X'A46' |
CICS causes a dump to be taken for a CICSPlex SM component when an abend occurs in a CMAS or MAS.
When an unexpected abend occurs under CICS, CICSPlex SM writes an abend indication and summary to the console and job log. The first message in the abend summary is usually:
EYUXL0900I Starting environment recovery
CICSPlex SM also writes a summary record to the CICS trace data set and takes a transaction dump, if appropriate. In addition, if the abend occurs in a CMAS or local MAS, CICSPlex SM produces SYMREC records and, when appropriate, takes an SDUMP.
Figure 13 is an example of a CICSPlex SM dump produced under CICS.
+EYUXL0900I Starting Environment Recovery
+EYUXL0905E CICSCMH ASRB IN MCCD, OFFSET 000003D0 PSW=078D4000 8818A880
+EYUXL0905E INTC=0028 ILC=6 TXCP=0550D000 SCODE=S00E0 TRAN=MCCM TASK=0000041
+EYUXL0905E Methods=MCCD,MCCM,XLOP
+EYUXL0906I Registers at ABEND
EYUXL0907I GPR0-GPR3 05402EB8 05401178 00001FA8 0818A4F0
EYUXL0907I GPR4-GPR7 05401EB8 050271B0 0000000C 05400F10
EYUXL0907I GPR8-GPRB 003BE000 0547E6D8 053DC40C 0818B4F0
EYUXL0907I GPRC-GPRF 05400C88 05400F10 D8C3D900 07FD91E8
EYUXL0907I ARR0-ARR3 00000000 00000000 00000000 00000000
EYUXL0907I ARR4-ARR7 00000000 00000000 00000000 00000000
EYUXL0907I ARR8-ARRB 00000000 00000000 00000000 00000000
EYUXL0907I ARRC-ARRF 00000000 00000000 D4D6E2D5 00000000
+EYUXL0908I Storage At ABEND
EYUXL0909I -20 337E4199 00104660 336847F0 39C89AEE
EYUXL0909I -10 900058E0 9004B219 0200D203 D604E018
EYUXL0909I +00 5810D604 88100001 5010D608 B2190000
EYUXL0909I +10 D203D5FC 40105860 D55C9140 D5F047E0
+EYUXL0910I EYU9XLRV Dump,CICSMH ,CICSMH ,MVSH,CMAS,MCCM,0000041,
ASRB,EYU0MCCD,08/26/95,09:55:07
+EYUXL0999I XLRV Exiting Successfully
Each CICS SDUMP has a title that consists of a summary of the abend. The title includes:
Here is an example CICS SDUMP title:
EYU9XLRV Dump,CICSCMH ,CICSCMH ,MVSH,CMAS,MCCM,0000041,ASRB,
EYU0MCCD,08/26/98,09:55:07
In this example:
Name of the recovery routine that requested the SDUMP: | EYU9XLRV |
MVS/ESA jobname: | CICSCMH |
Name of the CMAS or local MAS: | CICSCMH |
4-character MVS/ESA system ID: | MVSH |
Environment (CMAS or MAS): | CMAS |
CICS transaction ID: | MCCM |
CICS task number: | 0000041 |
CICS abend code: | ASRB |
Full name of the CICSPlex SM method that abended: | EYU0MCCD |
Date and time of the abend: | 08/26/98 09:55:07 |
When the CICSPlex SM local MAS agent starts, it automatically adds one CICS TRANDUMPCODE (TRANDUMP) entry for transaction dump code EYUN and two SYSDUMPCODE (SYSDUMP) entries for system dump codes EYU0XZPT and EYU0XZSD. These codes are primarily used for CICSPlex SM Web User Interface users who many want to use the ADD action from the EYUSTARTTRANDUMP and EYUSTARTSYSDUMP view sets to add their own TRANDUMP or SYSDUMP entries.
The presence of these entries does NOT indicate a problem, unless the current dump count for these entries is greater than zero, in which case the MAS job logs and dump may need to be investigated.