$HASP9202

module+offset

Explanation

>>-POTENTIAL JES2 MAIN TASK LOOP DETECTED NEAR--module+offset--->

>--DURATION---hh:mm:ss.xx--PCE---pcename--EXIT---exit----------->

>--JOB ID---jobid--COMMAND---jes2_command----------------------><

 JES2 issues this alert message in response
to a $JDJES or a $JDSTATUS monitor command or as a highlighted message.
Based on context, this message can indicate an alert or an incident
being tracked. This message indicates a potential loop condition exists
in the JES2 main task. Loops cant indicate a problem or complex processing
that takes a long time to complete. One way to determine if the loop
is making progress is by studying the job information in the message.
If it is changing over time then the loop might eventually complete.
If it is not changing, it might indicate a problem with the processing
or the current job. In general, most functions in JES2 process jobs
in job number order, and warm start processes jobs in job—index order.
 In the message text: module_offset or address
Module and offset or address near the center of the loop.
hh:mm:ss.xx
The length of time the loop has lasted.
pcename
The name of the PCE in control during the loop.
exit
The exit number in control during the loop (or NONE).
jobid
The job id or job index associated with the current PCE (or NONE).
jes2_command
If the current PCE is the command processor, the current command
is being processed. If the current PCE is not the command processor,
this line is not displayed.

 Note: Because data used to build this message
is sampled without serialization, it is possible, in rare situations,
for the PCE, exit, or job information to not correspond to the address
being displayed. Loop detected is limited to detecting situations
where a single segment of code is constantly executing. If the loop
involves code that calls a service routine or spans a large area of
memory, the loop detection logic might not identify it as a loop.
Instead, JES2 issues the $HASP9203 message indicating a long PCE dispatch
may be issued.

System action
 If the condition persists, JES2 reissues this
message every 30 seconds with updated information.

Operator response
 Monitor alerts indicate potential reasons
why JES2 is not functioning properly. If this condition persists and
is impacting normal JES2 operations, notify your system programmer.

System programmer response
 Loops can be an indication of a tuning
problem, a complex process that takes a long time to complete, or
an error situation. Examine the job information displayed in the messages
to determine if it is being updated. If no progress is being made,
you will need to abend and restart JES2. 
 First, capture a
dump of the JES2 address space using a z/OS® DUMP
command. While JES2 is dumping, JES2 might delete and reissue the
$HASP9202 message. When dump processing completes, issue a $PJES2,ABEND
command followed by a $PJES2,ABEND,FORCE command. The $PJES2,ABEND,FORCE
command is needed because the main task is in a loop. When JES2 terminates,
you can then restart it. Analyze the dump to determine what code is
looping and the cause of the loop. If the problem is in exit code
(or exit–invoked code) correct the exit logic. If the problem is caused
by IBM®–distributed code, contact the IBM support
center.

Module
 HASJSPLR
 Routing Code: 1,2,10,42 or as a command response
 Descriptor Code: 2,7 or 5 when a command response