Basic information to collect

Whether you decide to diagnose the problem yourself or call the IBM® Support Center for assistance, collect:
  • A dump of JES2. If JES2 did not write a dump, request one by entering the following command from a console with master authority:
    DUMP COMM=(JES2 DUMP 9-1-94)
    
    NOTE:  The keyword value of COMM= that is in parenthesis 
           is a descriptive title of your choosing.
    

    The system will respond with the message:

    
    * id IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND
    

    Reply:

    
    R id,JOBNAME=JES2,SDATA=(SERVERS,PSA,SQA,LSQA,RGN,TRT,LPA,CSA,GRSQ,SUM,XESDATA,COUPLE)
    

    To have JES2 automatically dump its storage if a problem occurs twice in a 24-hour period, set the COUNT parameter on the RECVOPTS initialization statement to 2. This dump includes the same information as the previous SDATA requests and could prevent you from having to recreate the problem. JES2 utilizes the remote feature of SDUMP to capture dumps of all members or an MAS for certain types of errors. These remote dumps will have the same symptoms as the original problem and thus may at first appear to be duplicates. However, they are not duplicates in these cases. You must ensure that all dumps that are created for an error are retained for problem analysis.

  • A dump of any suspect jobs. This is useful when JES2 ends abnormally and it appears that a job running on your system may have caused JES2 to stop running.

    Enter the $D I,LONG command to display the address space identifier (ASID) of the initiator which the job is running. You can then specify ASID=nn in the SDATA when you request the dump to ensure the system dumps the address space which the failing job is running.

  • A copy of the hard-copy log or the most current system log (SYSLOG) available. If you suspect that a job might be causing the problem, the SYSLOG should cover the period of the entire life of the suspect job. Ensure you save the soft-copy version of the SYSLOG for the failure period until you have resolved the problem.
  • Logrec data set error records, if available. This is especially useful in hardware- and teleprocessing (TP)-related problems.
  • Any installation modifications to JES2. Have the source for all exits, table pairs, and installation modifications to JES2.