Steps for searching the problem reporting databases

  1. Search the problem reporting database to determine if the problem was previously reported. See Searching for a known problem.

    Use the free-format search argument abstract as a symptom string to determine if the problem already exists. For example ABEND05C RSN00000241.

    For example, the following search argument abstract would generate the free-format search argument: ABEND03C RSN2D000810:
    SEARCH ARGUMENT ABSTRACT

  PIDS/5752SC1CR RIDS/NUCLEUS#L RIDS/IARYTASS AB/S003C PRCS/2D000810 REGS/0E0B
  REGS/088FA RIDS/IARRR#R
  2. If the search provides no match, remove some symptoms to broaden the search. If the search provides too many symptoms, trying adding some symptoms to limit the scope. Check to see which matches pertain to the operating system environment.
  3. If the search finds that the problem was previously reported, request the problem fix. If not, continue with Gathering additional problem data for abends. Use the problem data gathered there to create more symptoms; use these symptoms in later searches.
  4. If you still cannot find the cause of the abend or if the problem is new, report the problem to IBM®.
    Provide the information in Problem diagnostic worksheet, such as:
    • Any changes made to the system recently, preceding when the problem began occurring (for example, PTFs or new products installed or new hardware).
    • Problem type: abend
    • Search argument
    • Dump, formatted by IPCS, online or printed
    • Failing input request: macro, command, or statement
    • SDWAVRA keys, lengths, and contents
    • Offset of the failing instruction into the module or CSECT
    • Accompanying messages: identifiers and texts
    • Logrec report, if used
    • All printed output and 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 diagnosis book for the component, subsystem, or program
Parent topic: Searching the problem reporting databases