Troubleshooting data for file control (VSAM non-RLS) wait problems

CICS® MustGather for file control (non-RLS) problems

Many problems in file control are caused by waits for CICS or VSAM resources.

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your file control (non-RLS) problems.

Required data:
  1. The CICS message log and the MVS™ system log (SYSLOG).
  2. The CICS internal trace that is included in the MVS system dump when tracing is active. 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. When possible, turn on level 1 tracing for all CICS components and level 1-2 for the FC component. For more information, see Using trace for CICS problem determination on z/OS®.
  3. An MVS system dump of the CICS region that is taken as soon as you notice the hang or wait.
    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.
    For more information, see Using dumps for CICS problem determination on z/OS.
Optional data:
  1. If feasible, save the data set by using IDCAMS ALTER NEWNAME to rename the data set and save it in place (note that the example in the link has a DEFINE before the ALTER). If this is not feasible, run IDCAMS EXAMINE ITEST DTEST against the data set and any alternate indexes that are associated with the data set before you continue. For more information, see z/OS DFSMS Access Method Services Commands.
  2. If you can reproduce the problem, consider using the CICS auxiliary trace or the GTF Trace with the MVS system dump. The MVS system dump alone is unlikely to show anything about system activity in the period that leads up to the wait because the trace table probably wraps before you have a chance to respond. For more information, see Using trace for CICS problem determination on z/OS.