General documentation needed for all problems with WebSphere MQ for z/OS

Here is a list of the general documentation you might be asked to submit for a PMR:

• Any hardcopy or softcopy illustrating the symptoms of the problem.

• The dump of the problem, see Getting a dump.

• The appropriate SYS1.LOGREC records, see SYS1.LOGREC information.

• The system log.

• A portion of the WebSphere MQ for z/OS job log.

• Trace records, see Using trace for problem determination.

• Trace information produced by the CICS or IMS adapter, see The CICS adapter trace.

• Buffer pool statistics, see the sections on using SMF and type 115 records in the WebSphere MQ for z/OS System Setup Guide.

• Listings of relevant application programs.

• A list of PTFs and APARs applied.

  Use the sample JCL below to produce a list of all the PTFs, APARs, user modifications and product code that has been installed in the global zone specified by SMPCSI:

  //SMPELIST  EXEC PGM=GIMSMP,REGION=4096K               
  //SMPCSI    DD  DSN=shlqual.global.csi,DISP=SHR        
  //SYSPRINT  DD SYSOUT=*                                
  //SMPCNTL   DD *                                       
      SET BOUNDARY(GLOBAL) .                             
      LIST                                               
        SYSMODS                                          
           APARS                                         
           FUNCTIONS                                     
           PTFS                                          
           USERMODS                                      
      ALLZONES .                                         
  /*                                        

• Dump of Coupling Facility administration structure, see Figure 6.

• Dump of Coupling Facility application structure, see Figure 6.

• Dump of other queue managers in queue-sharing group, see Figure 2.

• Definitions of the objects in your system.

  We can find these by using the DISPLAY command for each type of object, for example:

  DISPLAY QUEUE (*) ALL

  Or, if you regularly make a backup of your object using the MAKEDEF feature of CSQUTIL COMMAND function, the output from that backup job.

• Your WebSphere MQ DB2 tables.

  We can get these by using the sample job CSQ45STB in thlqual.SCSQPROCS to produce a report of all the DB2 tables used by WebSphere MQ.

Because of the size of SVC dumps in the cross memory environment, transfer the SYS1.DUMPxx data set to a tape or like device. We can use the PRDMP service aid program to transfer the SYS1.DUMPxx data set contents to another data set for archiving until the problem is resolved. Alternatively, your support center representative might give you the address of an FTP site where you can send your dump electronically.

Depending on the nature of the problem, the IBM support center might ask you to send the entire dump on tape. This allows the support center to extract any additional data needed to resolve the problem; for example, CSA, SQA, or the private storage area.