How to search for a matching problem

This procedure summarizes search symptoms that you can collect by using this document's problem analysis procedures for RACF®. You might want to use these symptoms to search for a matching problem in a problem database, or to report to IBM®.

If you need descriptions or examples of entire search arguments, see the prerequisite procedure, Performing a preliminary search for a matching problem.

Scan Table 1 for more RACF symptoms that you might want to use in your search for a matching problem (or to report to IBM). It lists some of the most probable search symptoms for problems in RACF.

Note: For abends, more symptoms such as a register/PSW (program status word) difference and a failing instruction area are automatically produced in DAEDATA output, so they are not repeated here. Notes about the symptoms are indicated with asterisks (*) and *Note n*, where n is the number of the note.

Table 1. Additional Search Symptoms for RACF
Description of Search Symptom	Free-Format Example	Structured Example
Control block name	ACEE	FLDS/ACEE
Control block field name &rbl;&rbl;&rbl;&rbl;&rbl;Note 1	ACEEFLG1	FLDS/ACEEFLG1
Symptoms for later searches
Level of failing module &rbl;&rbl;&rbl;&rbl;&rbl;Note 2	HRF2220 or UW09958	LVLS/HRF2220 or PTFS/UW09958

Note:

If you receive too many matches on your first search, consider adding a control block field name or other text from a RACF error message. (Avoid use of addresses or other values that would vary between executions of the RACF function.)
The ID and level at the beginning of a failing module might be pointed to by RACF's PSW at the time of the failure. For abends, the module level might be in the SDWAMLVL field and in DAEDATA output.