IMS problem determination

IMS messages and codes problem determination is accomplished by using procedures established by IBM®.

Problem determination is accomplished by using procedures for identifying a failing module or program and determining whether the user or IBM is responsible for resolution of a given problem.

Problem determination information is included, as appropriate, for all messages and codes. In most instances, one or more numbers (for example, "4,6") appear after the heading Problem Determination for a given message or code. These numbers are cross-references to the numbered items that appear in the following list of standard problem determination actions to be taken by the user.
  1. Save the console sheet from the z/OS® console.
  2. Save the input associated with the job.
  3. Save the SYSOUT (system output) associated with the job.
  4. Save the storage memory dump at time of failure of the IMS control region, and save the memory dump of all associated message regions. (If SYS1.DUMP is used, print, and save it.)
  5. Save the IMS log printout.
  6. Save the IMS master terminal printout.
  7. Save the local or remote terminal printout.
  8. Save the JCL listings.
  9. Save the ACB generation output.
  10. Save the IMSGEN listing.
  11. Save the SYSABEND memory dump. (If SYS1.DUMP is used, print, and save it.)
  12. Save the assembly listing of any user-modified IMS modules.
  13. Save the bind map.
  14. Save the LOG trace.
  15. Save the IMS log printout starting with the records that were written just before abnormal termination.
  16. Save the output listing from the MFS Language Utility execution.
  17. Collect the following problem-related data:
    1. System memory dump if running batch.
    2. If running online, print log records type X'67', sub-record type X'FF' (Pseudoabend). Use the File Select and Formatting Print program to print these records. The OPTION PRINT control statement must specify EXITR=DFSERA30.
    3. Run the DL/I test program (DFSDDLTO) with SNAP statements before and after the failing call.
    4. Save the PSB and DBD listings or statements, or both, related to the failure.
    5. Create a memory dump of log records type X'67', sub-record type X'FE' (program isolation trace). Use the File Select and Formatting print program to print the records. Program isolation trace must be enabled when the log is created. The OPTION PRINT control statement must specify EXITR=DFSERA40.
    6. If online, a snap from the log of the online region.
    7. A history of the database backout, recovery, and reorganization activity.
  18. Save the assembly listing for the associated DBDs.
  19. Save the assembly listing for the associated PSBs.
  20. Save a listing of the VSAM catalog entries for the associated data sets at the time of failure.
  21. Reserved for future use
  22. Reserved for future use
  23. Contact IBM for hardware support.
  24. Create a memory dump of the 3270 diagnostic error log records off the IMS log: Record type X'67': sub-record type X'03'.
  25. Submit a copy of the IMS log.
  26. Determine the CCB involved from the SPACCB field of the scratch pad area or from the CTBCCBPT field. Determine the associated (a) source and output CNT, and (b) the line and PTERM (CTB).
    Determine from log records 01, 02, 03, 07, 08, 11, 12 and 13 the status of the conversation:
    1. The message was ready, but the application was not scheduled. A 01 destination is a conversational SMB.
    2. The application was scheduled and a 08 record was produced.
    3. The application inserted a segment to a conversational terminal. If the destination of the message is CNT, 03 and 13 records are produced.
    4. The application inserted a segment to a conversational program. SPA is the first segment of a message in the 03 records.
    5. The application finished normally or terminated abnormally. The 07 record contains the completion code of a conversational application. The DLRFLAG2 area (the last word of the 07 log record) contains synchronization point information.
    6. A 12 record indicates that the conversation was terminated.
    7. Determine if 02 records, produced for the following commands, affected the terminal in conversation: /EX1, /HOLD, /REL, or /START LINE (no PTERM).
    8. Does restarting IMS affect the conversation? For details, see the input to and output logs from restart.
  27. Save the z/OS hardcopy message log output.
  28. Determine the status of z/OS and IRLM operating in the other system with which this system is connected during normal operations.
  29. Save the IRLM address space dump generated at the time of the failure.
  30. Save the memory dump of any IMS online or batch address space that failed near the time of the IRLM failure. Follow IMS problem determination procedures relative to the IMS memory dump. The IMS failure might be related to the IRLM failure.
  31. Save a listing of the IRLM start procedure JCL.
  32. Save a listing of the IMSGEN performed to install the IRLM.
  33. Save listings of the VTAM® definitions performed to install the IRLM.
  34. Save the GTF trace output, if any is available showing activity at the time of the failure.
  35. Refer to the following manuals for further assistance to resolve your problem:
    • IMS Version 13 Messages and Codes, Volume 1: DFS Messages
    • IMS Version 13 Messages and Codes, Volume 2: Non-DFS Messages
    • IMS Version 13 Messages and Codes, Volume 3: IMS Abend Codes
    • IMS Version 13 Messages and Codes, Volume 4: IMS Component Codes
    • IMS Version 13 Diagnosis

    Check all input for accuracy and analyze any memory dumps.

    If you are still unable to solve your problem, contact IBM Software Support for further assistance.

  36. If you are unable to solve the problem, contact IBM Software Support for assistance.
  37. Submit a copy of the type X'02' log records.
  38. Save the CCTL SNAP or SDUMP data set.
  39. Save a listing of the DBRC RECON.
  40. Take an SVC memory dump and contact IBM Software Support for further assistance.