| 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.
Check that error message handling is ON. This can be done
with the command SET EMSG ON (not SET EMSG TEXT). If a batch job encountered
the error, check that the batch console was spooled back to the originating
user.
- 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 your system diagnosis guide
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 the following
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 did not find a matching problem, you will need to request
a dump (if you don't have one already) and collect problem information
to report to IBM.
Use the following procedures:
- Obtaining a System Dump on z/VM, if you need to request
a dump
- Formatting a System Dump on z/VM
- Validating Input.
- 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 book for the program that
the module is a part of.
To determine which diagnosis or logic
book contains information about the program, find the name of the
component that owns the module. If the component is owned by IBM, the general information manual
for the product containing the component has the name and order number
of any diagnosis or logic publication.
|