Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Example of command tracing z/OS Security Server RACF Diagnosis Guide GA32-0886-00 |
|
Command tracing would be helpful in this example. You entered the command, ALTUSER MURPHY DATA('PRESIDENT - CATSKILL DIVISION'), and the command seemed to run, but the installation data field was not updated. By reissuing the command with the -c appended to the end of it, ALTUSER MURPHY DATA('PRESIDENT - CATSKILL DIVISION') -c, (note the leading blank between the command and the two characters) you can quickly determine if the RACF® command envelope module parsed and rebuilt the command image properly before invoking the ALTUSER command processor module. The command envelope module does multiple parses and rebuilds of the RACF command. If the traced image has the correct installation data, the problem exists in the command processor or some deeper level of RACF. If the traced image does not have the correct installation data, you isolated the problem to the command envelope module. Figure 1 shows the command:
being
issued, traced, and rebuilt correctly with all the proper keywords.
Therefore, the problem must exist in the command processor or some
deeper level of RACF.Figure 1. Trace Output Showing a Problem
in the Command Processor or RACF
|
Copyright IBM Corporation 1990, 2014
|