Troubleshooting data for Abend 878 or 80A problems

CICS® MustGather for Abend 878 or 80A problems

If the available MVS™ storage is not enough to satisfy an MVS GETMAIN request, you might have an abend 878 or an abend 80A problem in CICS TS. To determine the type of storage that is requested, see the explanation of system completion codes 878 in z/OS MVS System Codes and 80A in z/OS MVS System Codes. Abend 0F9 and 40D might occur when MVS does not have enough storage to create the dump for the abend 80A or 878.

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your Abend 878 or 80A problems.

Required data:
  1. The MVS system dump that is taken when an out of storage condition occurs.
  2. If you do not have an MVS system dump, set the following SLIP traps to get a SLIP dump of the abend 878 or 80A:
    SLIP SET,COMP=878,JOBNAME=cicsjob,A=SVCD,
    SDATA=(ALLNUC,PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
    SLIP SET,COMP=80A,JOBNAME=cicsjob,A=SVCD,
    SDATA=(ALLNUC,PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END

    where cicsjob is the name of your CICS job.

  3. If you see gradual storage growth of MVS storage in the CICS region (excluding CICS DSA storage), you can take an MVS system dump of the region when storage usage is high.
    To take an MVS system dump, use the MVS command followed by a reply:
    DUMP COMM=(dumpname)
    R yy,JOBNAME=(cicsjob),
    SDATA=(ALLNUC,PSA,SQA,CSA,LPA,TRT,LSQA,RGN)
    where:
    dumpname
    Specifies the name of the dump.
    yy
    Specifies the reply identifier.
    cicsjob
    Specifies the job name of your CICS region.
  4. The MVS system trace that is included in the MVS system dump, unless your installation has changed the IBM®-supplied system tracing options. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. The failing GETMAIN might affect an innocent party that is not the cause of the storage leak. The large MVS trace can help identify the real cause. For more information, see Using trace for CICS problem determination on z/OS®.
Optional data:
  1. The CICS message log that shows the abend 878 or 80A.