Collect troubleshooting data for CICSPlex SM problems in CICS TS for z/OS

The following is the original MustGather information:

• Collecting general information for all problems
• Collecting data for CICSPlex SM problems
• Troubleshooting hints and tips
• Exchanging data with IBM Support


• Collect troubleshooting data for CICS products - Read first

Collecting general information for all problems

If you have already contacted IBM Support, you can continue on to the component-specific MustGather information. Otherwise, go to Collect troubleshooting data for CICS products - Read first.

Back to top

• The complete CICS job output for the CMAS, and MAS or WUI Server experiencing the problem.
  
  For problems related to a CMAS, in addition to gathering the output for the CMAS experiencing the problem, you must also gather the output from ALL other CMASs in the CICSplex. The requirement for gathering documentation from all CMASs is due to the way CMAS to CMAS communications works.
  
  For problems related to a MAS or WUI server region, you should gather this output for the MAS or WUI server as well as the CMAS to which it connects.
  
  This output must include the job log, JES messages, JCL, MSGUSR DD output, and the EYULOG DD output. Do not attempt to limit the size of the output by excluding anything. CPSM problems are often caused by events that occurred minutes, hours, or even days before you notice anything unusual.
• The complete MVS System Log from the LPAR where the problem is occurring. Do not attempt to shorten or cut down the size of the log in any way. IBM is used to dealing with millions of lines of output. If you attempt to cut out and send only what you think is relevant, you might inadvertently cut out critical information.
• MVS system dump taken at the point of failure.
  
  If your CICS region is hanging or looping, and you are not getting a CICS or CPSM dump or message at the time of the problem, refer to SYS1.SAMPLIB(IEADMCCP) to use an MVS dump command to dump the CPSM environment. See Using the MVS DUMP command for more information about dumping CPSM.
  
  If you do not automatically get a dump but you are receiving a CICS or CPSM message at the time of the problem, you should set an MVS SLIP trap to let MVS take an SVC dump of the appropriate address spaces and dataspaces.
  
  For example, if you always get an EYUXL0105E message in your MAS when a certain problem occurs, your SLIP trap should look like the following:
  
  SL SET,MSGID=EYUXL0105E,ID=CPSM,ACTION=SVCD,MATCHLIM=1,
  R y,JL=(cmas,mas,EYUX###),DSPNAME=('EYUX###'.*),
  R y,SDATA=(ALLNUC,LPA,LSQA,PSA,RGN,SQA,TRT,CSA,GRSQ),END Customize the SLIP as follows:
  • y is the reply id that displays on the console
  • cmas is the name of the CMAS that the MAS connects to
  • mas is the jobname for the region you see the problem message in.
  • EYUX### in both the JL and DSPNAME parameters is the ESSS address space and must reflect the release of CICS that you are running:
  
  
  • For CICS TS V3.1, use EYUX310 in both parameters
    For CICS TS V3.2, use EYUX320 in both parameters
    For CICS TS V4.1, use EYUX410 in both parameters
    For CICS TS V4.2, use EYUX420 in both parameters
    For CICS TS V5.1, use EYUX510 in both parameters
    For CICS TS V5.2, use EYUX520 in both parameters
    
    It is critical that you dump the CMAS and EYUX### address spaces even if you only 'see' a problem in a MAS.


• If you are taking a dump using the MVS console DUMP command, you MUST make sure you take a dump of the ESSS and its dataspaces as well. A sample DUMP command that you can use is:
  
  DUMP COMM=(DumpTitle)
  R xxx,JOBNAME=(cmas,mas1,mas2,EYUX###),DSPNAME=('EYUX###'.*),CONT
  R xxx,SDATA=(ALLNUC,LPA,LSQA,PSA,RGN,SQA,TRT,CSA,GRSQ),END
  
  If you need to add additional MAS names to the JOBNAME parm above, you may.


• Unformatted (raw) CICS auxiliary trace data sets (DFHAUXT and DFHBUXT) from the CMAS. and MAS or WUI Server.
  
  For problems related to a CMAS, in addition to gathering the unformatted (raw) AUX trace files for the CMAS, you must also gather the unformatted (raw) AUX trace files from ALL other CMASs in the CICSplex. The requirement for gathering documentation from all CMASs is because of the way CMAS to CMAS communications works.
• When you have a routing failure and you want to know why, capture CPSM WLM trace generated from the routing region. Also, include the dump and the auxiliary trace from both the CMAS and the routing region as documented in the CPSM WLM trace instructions.

Back to top

Troubleshooting hints and tips

• Review the logs and dumps generated at the point of failure.
• Search the CICS support site for known problems using symptoms like the message number and error codes.
• If you find a fixing PTF, see Ordering CICS products and maintenance for the options that are available to order CICS maintenance.
• Gather the documentation and work with the CICS support team to resolve your problem.
   

• CICSPlex SM roadmap
• CICSPlex SM problem determination
• CICSPlex SM messages
• Webcast: Best Practices for Maintaining a Healthy CICSPlex SM Configuration
• Webcast: CPSM WLM Level Tracing

1. See Exchanging information with IBM Technical Support for FTP and email instructions using the IBM Enhanced Customer Data Repository (ECuRep).
2. Go to the Service Request page to open or update a problem. If you have a SoftwareXcel enterprise edition for zSeries contract, you can also ask a non-defect installation and usage questions.
   
   Note: Always update your Service Request (problem record) to indicate that data has been sent.

Back to top