Steps for searching the problem reporting databases

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

1. Create a search argument using the symptoms applicable for the type of loop being diagnosed:
   1. Disabled loop search argument - LOOP module/CSECT name
   2. Enabled loop search argument - LOOP module/CSECT name
   3. Spinloop search argument - ABEND071 module/CSECT name.

   Tip: Use free-format search arguments. For more information, see Searching problem reporting databases.

2. If the search finds no match, remove some symptoms or add some symptoms. Search again. Continue searching for matches by adding and removing symptoms.

   If the search finds that the problem was previously reported, request the fix.

3. If the search does not produce a match, continue with the next step. Use problem data from the preceding steps to create more symptoms; use these symptoms in later searches.
4. If you still cannot find the cause of the loop or if the problem is new, report the problem to IBM® using the procedure in Reporting problems to IBM. Provide the following problem data as listed in Problem diagnostic worksheet.
   • Problem type: type of loop
   • Search argument
   • Dump, formatted by IPCS, online or printed
   • Range of loop
   • 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
   • 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 procedures in this document or other diagnosis books for the component, subsystem, or program