Obtaining RACF return codes and reason codes from a RACF callable service invocation

If the program that invoked the callable service received an error return code from the macro, but did not produce a message containing the return code and reason code, you can use one of these techniques to obtain the codes:

Use the RACF® SET TRACE command. See Obtaining trace records using the SET TRACE command.
Place a TSO TEST trap at the instruction after the callable service invocation in the program, and check the return code and reason code when the trap matches.
Note: You could use the SLIP command to set a trap, but it affects system performance. If you use SLIP, consider qualifying it with job name or PVTMOD options, and request an SVC dump when the trap is hit.
Use the SPZAP ("superzap") service aid to modify the program that invoked the callable service:
1. Locate the callable service invocation in the assembly listing or the object code for the program.
2. Use the SPZAP service aid to change the program's instruction that follows the callable service invocation. Change the instruction operation (op) code to an invalid op code, such as X'00'.
3. Re-create the problem, using JCL with a SYSMDUMP, SYSUDUMP, or SYSABEND DD statement. The invalid op code causes an X'0C1' abend.
  The SYSMDUMP DD statement is recommended if you plan to report the problem to IBM®.

At the time of the trap or the 0C1 abend, Register 1 contains the address of the parameter list for the callable service. This parameter list contains the SAF return code and the RACF return code and reason code. See z/OS Security Server RACF Callable Services for more information.