5695DF170  Rnnn LOOP modulename

Rnnn is the release keyword, and its optional use reduces the number of matches in the search.

1. If a DFSMShsm program suspends activity for no apparent reason, the program may be in a loop or wait state. A loop can be evident from a never-ending request found by the QUERY ACTIVE command or from some other symptom such as a page of output being printed repeatedly. If a loop is not evident, use the WAIT keyword.
2. If you have a complete storage dump, locate the address where the LOOP occurs. DFSMShsm modules contain the module name near the beginning of the module. See the following example:

       00007C30.  00000000  00000000  00000000  00000000  | ................ |
       00007C40.  00000000  00000000  00000000  00000000  | ................ |
       00007C50.  00000000  00000000  00000000  00000000  | ................ |
       00007C60.  47F0F022  1DC1D9C3  C1C2D4E2  C74BF8F7  | .00..ARCABMSG.87 |
       00007C70.  F0F4F44B  F1F0F0F0  F3F14BC8  C8D4F2F3  | 044.100031.JDZ11 |
       00007C80.  F0F290EC  D00C18CF  1FFF43F0  C5081F00  | BC..Œ......0E... |
       00007C90.  BF07C509  47F0C03C  00000200  89F00008  | ..E..0Œ.....i0.. |

   Note:

   1. This example has been obtained by using IPCS.
   2. See z/OS MVS Diagnosis: Reference and z/OS MVS Diagnosis: Tools and Service Aids for information about locating modules within a loop.
3. Locate the system trace table to determine if a DFSMShsm task is being dispatched repeatedly in the same module. If the loop involves more than one DFSMShsm module, the repetitive invoking of these modules by DFSMShsm can be identified by the PDA trace facility. See Using the problem determination aid facility for further information.