Steps for searching for a matching problem

Before you begin: You need to verify that this is a problem caused by RACF® and to collect some initial problem symptoms. See Troubleshooting tables for problems in RACF for steps to perform this prerequisite.

Perform these steps to:

Make an initial list of search symptoms.
Use the list to search for a matching problem.
If you did not find a match, try other symptoms.
If you found too many matches, add search symptoms.

Use Table 1 to select which search arguments apply to the type of problem you have.
_________________________________________________________________
Using Table 1 for examples of search arguments, do your first search for a match.
_________________________________________________________________
If your search does not produce a match, try widening your search.
1. Use the word "RACF" instead of the component ID.
2. Use fewer search arguments.
_________________________________________________________________
If a search produces too many matches, use some of the other symptoms listed in this procedure to narrow the search.
_________________________________________________________________
If your preliminary searches are unsuccessful, do the structured search described in Searching for a matching problem.
1. If a structured search is still unsuccessful, gather additional information before reporting the problem to IBM® by using the diagnostic procedures recommended for your type of problem.
2. Return to where you were in the troubleshooting tables.
_________________________________________________________________
If your search has too many matches, consider using these procedures to add search symptoms:
1. Return to the troubleshooting tables to obtain one or more additional symptoms to narrow your search.
2. Obtain additional search symptoms by analyzing a dump or doing other in-depth analysis. (For lists of the procedures for doing the analysis, return to where you were in the troubleshooting tables.)
  Note: Searching for a matching problem summarizes the additional symptoms that you can obtain through in-depth analysis.
_________________________________________________________________

You know you are done when you have found a problem match for your symptom or have contacted IBM for additional help.

Table 1. Preliminary Search Symptoms for RACF
Search Argument	Free-Format Example	Structured Example
Component identification (ID) The component ID matches problems that had RACF as either the cause of the problem or the apparent cause (for a problem that was reassigned to another component).	RACF 5752XXH00 5752SC1BN	PIDS/5752XXH00 PIDS/5752SC1BN
Release level of RACF: Use the FMID (function modification identifier). For a list of RACF FMIDs, see Table 2.	R902 or RI02 (R for release; I, the ninth letter of the alphabet, can stand for 9; and 02 for 02. R922 (for RACF 1.9.2) R210 (for RACF 2.1) R220 (for RACF 2.2) R230 (for FMID HRF2230) R240 (for FMID HRF2240) R260 (for FMID HRF2260) 2608 (for FMID HRF2608) 7703 (for FMID HRF7703)	LVLS/902 or LVLS/RI02 LVLS/922 LVLS/210 LVLS/220
RACF request that failed	RACHECK PROFILE	PCSS/RACHECK PCSS/PROFILE
Error reason code from the RACF request (if available)	rc00000004	PRCS/00000004
Associated error message ID The job log or system log might contain error messages associated with the problem that you encountered. Some problems produce multiple error messages, such as problems initiated by a previous abend or I/O error. General error messages, such as the IEA995I symptom dump message for all types of abends, are not needed as search symptoms.	msgICH408I	MS/ICH408I
Associated reason code from message	rc04	PRCS/04
RACF module	ICHRIN00	RIDS/ICHRIN00
SMF record with error	SMF type 80	RECS/SMF80
Part of a document title	Security Administrator's Guide	PUBS/security PUBS/administrator's PUBS/guide
Symptoms for later searches
Component ID of a service used by RACF, such as Master Scheduler If you suspect a problem in a system service used by RACF, consider a search argument of the service's component ID, plus the failing RACF request and the problem type (such as an abend and reason code).	5752SC1B8	PIDS/5752SC1B8
A PTF number Consider use of this symptom if a recent PTF (program temporary fix) updated a RACF module involved in the problem. This does not mean that an error exists in the PTF, only that the problem might occur after this PTF is installed.	UY00934 UW02010	PTFS/UY00934 PTFS/UW02010
Area within a document, such as a part, section, chapter, appendix, or page	Chapter3 appendixA	PUBS/CHAP3 PUBS/APPXA
Document order number Document order numbers end with a version number, such as the 01 in GC28-1154-01. All version numbers are now two digits, although previously they could be one. You could leave off the second hyphen and the version numbers that follow it. Then, if you receive too many matches, add the version numbers to the search symptom.	GC28-1154-01	PUBS/GC28115401