| Any loop during RACF® processing |
Action: - Check whether any error messages were issued for the user request
that had the loop 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.
- Check whether the prefix of one of the modules involved in the
loop is ICH or IRR.
Note: The instructions involved in the loop are
generally pointed to by the PSW that was active when the system dump
was generated. Most modules owned by IBM® have
an identifier with the module name at either the beginning or end
of the object code for the module. See the MVS™ diagnosis publications if you need further
details of general loop analysis techniques.
- If the prefix is ICH or IRR, the problem might be caused by RACF, and you should use these
diagnostic procedures:
- Check that the problem was not due to repeated requests for RACF services. Repeated requests
might be caused by a loop of logic in the application program issuing
the request. If the loop was in a program making repeated requests,
report the problem to the owner of the program. If the loop was within RACF, use the diagnostic procedures
in the remainder of this list.
- See Performing a preliminary search for a matching problem.
- If you do not find a matching problem, you need to request a dump
(if you don't have one already) and collect problem information to
report to IBM.
To Get
the Dump Output and Analysis Results:
- See Searching for a matching problem.
- See Reporting RACF problems to IBM.
- If the prefix of one of the looping modules is neither ICH
nor IRR, the problem was probably not caused by RACF. Note the prefixes of the looping modules.
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 that the module is a part of. To determine the name
of the component that owns the module, use the component summary in z/OS MVS Diagnosis: Reference.
|
z/OS Security Server RACF Diagnosis Guide
Copyright IBM Corporation 1990, 2014