z/OS Security Server RACF Diagnosis Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


RACF return codes troubleshooting table

z/OS Security Server RACF Diagnosis Guide
GA32-0886-00

Table 1. Troubleshooting Table: Return Codes
Symptom Recommended Procedures for Return Codes
Return codes from RACF® macros

(nonzero value in register 15)

Action:
  1. For some macros, depending on the return code, there is a reason code in register 0. Check register 0 for this reason code. (To obtain the reason code from a RACF macro, see Obtaining RACF return codes and reason codes from a RACF macro invocation.)
  2. See Utilities for a summary of some commonly encountered macro reason codes and advice on how to resolve problems that are due to an error in the program that issued a RACF macro.
    Note: Error return codes and reason codes from a RACF macro are generally due to a problem in the program that issued the macro.
  3. If you haven't done so already, look up the explanation of the RACF macro's return and reason codes. See z/OS Security Server RACF Macros and Interfaces, except for the RACROUTE macro, which is described in z/OS Security Server RACROUTE Macro Reference.
    Note: For the RACROUTE macro, you should also check the first and second words of the SAF parameter list. These are the return and reason codes from the RACF request (usually a RACF macro invocation).
  4. Check whether any error messages were issued for the user request, and make sure that message IDs are included with the messages.

    If a batch job produced the output, check that the job statement had MSGLEVEL=(1,1) specified. If a TSO/E user had the problem, check that the user profile had these options: PROFILE WTPMSG MSGID.

  5. The module that issued the macro is either owned by IBM® or is a non-IBM product. If the module is owned by IBM (modules owned by IBM usually start with the letters A through I, S, or X), see the diagnosis or logic document for the program of which the module is a part. To determine the name of the component that owns the module. use the component summary in z/OS MVS Diagnosis: Reference.
  6. If the problem still appears to be caused by RACF, use the diagnostic procedures described in these areas:
    1. Performing a preliminary search for a matching problem. If you do not find a matching problem, continue diagnosis, using the procedures in the remainder of this list.
    2. If you need to request a system dump, Obtaining a system dump.
    3. Formatting a system dump.
    4. Validating input.
    5. Searching for a matching problem.
    6. Reporting RACF problems to IBM.
RACF manager return codes
Action:
  1. See z/OS Security Server RACF Messages and Codes for a description of the message and the condition causing it. Attempt to correct the problem from the information in the messages document.
  2. If you cannot correct the problem from the information in the messages document, perform the problem determination procedure that is related to the message.
Return codes from RACF callable services
Action:
  1. Check the parameter list for the SAF return code, the RACF return code, and the RACF reason code.
  2. If you have not done so already, look up the explanations of the return codes and reason codes. See z/OS Security Server RACF Callable Services and z/OS Security Server RACF Messages and Codes.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014