Steps for searching the problem reporting databases

About this task

Use the following steps to search the problem reporting databases and determine if the problem was previously reported:

Procedure

  1. Develop a free-format search argument using the symptoms obtained from the analysis performed. The free-format search argument can include any of the following symptoms:
    • WAITxxx RSNyyyyyyyy (where xxx is the disabled wait state code and yyyyyyyy is the associated reason code)
    • Module or CSECT name
    • Resource name that was found to be in contention
    • Message ID
    • Component ID
  2. If an argument is not provided, use the primary symptom string in VERBEXIT SYMPTOM output, if available, or use the following symptoms:
    • Program identifier: PIDS/ccccccccc
    • CSECT name or module name: RIDS/cccccccc
    • Wait state:
      • If a disabled wait, with a wait state code: WS/D0hhh
      • If an enabled wait: WS/E0000
    • If ANALYZE EXCEPTION output indicates a lockout: PCSS/LOCKOUT
    • Input request (call, command, macro, statement), if one is associated with the problem: PCSS/cccccccccc
    • Symptoms created from information in the STATUS CPU output
  3. Select the problem type on the search tool panel, based on STATUS CPU output:
    Table 1. Selecting the problem type for jSTATUS CPU output
    Problem Type STATUS CPU Output
    Disabled wait DISABLED WAIT STATE CODE
    Enabled wait NO WORK WAIT
    Enabled wait DISABLED FOR ccc (not I/O or EXT)
    Hang None of the above
  4. If the search finds that the problem was previously reported, request the problem fix.

    Searching is an iterative process. If the search finds no match, you can remove some symptoms or change the symptoms and search again. Continue searching for matches by adding, removing, and changing symptoms using the steps in Gathering additional data for hangs and waits.

  5. If you still cannot find the cause of the hang or wait or if the problem is new, report the problem to IBM® using the procedure in Reporting problems to IBM. Record the following problem data in Problem diagnostic worksheet:
    • Problem type: disabled wait, enabled wait, or hang
    • Search argument
    • Dump formatted by IPCS online
    • SMF records, if obtained
    • Accompanying messages: identifiers and texts
    • Hard-copy log, beginning 15 to 30 minutes before the problem, or master trace, if not wrapped between the problem and dump
    • Logrec records, beginning 15 to 30 minutes before the problem and edited using the SPOTCHK and TIMESEQ parameters
    • All output data sets related to the problem
    • Data on any related problems
    • Module name and level
    • Name and level of the operating system(s) with a list of program temporary fixes (PTF) applied at the time of the problem and all installation modifications, exits, and products with other than Class A service
    • Other problem data developed while using the procedures in this document or other diagnosis books for the component, subsystem, or program

Results

You know you are done when you find a match for your problem or report the problem.

Related information:

Parent topic: Searching the problem reporting databases