Looping
If Db2 or z/OS® is not operational, you can try the diagnostic techniques for looping.
Procedure
- If z/OS is operational, take a z/OS console dump as directed in Guidelines for good operational procedures, before you attempt to break the loop. If z/OS is not operational, take a stand-alone dump and IPL z/OS again.
- Use standard z/OS diagnostic techniques to determine the location and scope of the loop. Refer to the z/OS diagnostic techniques and debugging handbook publications.
- If Db2 is causing the loop, try to determine the CSECT or load module involved. Turn to CSECT keyword and then to Load module modifier keyword.
- Build a keyword similar to LOOP xxxxxx,
replacing xxxxxx with the CSECT name. If
the CSECT name is unavailable, or if a search with this information
proves unsuccessful, replace it with the load module identifier. Add
this information to the keyword string, and turn to Searching the IBM Support site for known problems and solutions.
5740XYR00 R111 LOOP DSNXCR2 (free format) PIDS/5740XYR00 LVLS/111 RIDS/DSNXCRS LOOP (structured format)