z/OS JES2 Messages
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$HASP9211

z/OS JES2 Messages
SA32-0989-01

$HASP9211

Explanation

Read syntax diagramSkip visual syntax diagram
>>-JES MAIN TASK NOT RUNNING--DURATION---hh:mm:ss.xx-----------><

JES2 issues this 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 JES2 is tracking. This message is issued when the JES2 main task has been waiting at its normal wait for the duration specified. There are indicators that the main task does have work to do and should be running, but it is not.

In the message text:
hh:mm:ss.xx
The length of time the main task has been waiting at its normal z/OS® wait.

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, notify your system programmer.

System programmer response

JES2's main task might not be running because of improper tuning of MVS™ parameters or because of a problem in the JES2 address space. If the condition persists, investigate tuning and operational considerations first. For example, consider if online applications have been tuned to run before JES2 (not a recommended practice), or if the operator has issued a command that requires heavy use of system resources.

If the condition persists after investigating a tuning or operational issue, obtain a dump of the JES2 address space and determine why the JES2 main task is not being dispatched. Common problems include the following:
  • A service or an exit has reset the main task STIMER so that the main task is not "waking up."
  • A POST SRB is unable to run because the local lock is not available. Determine which function is holding the local lock and why.
If the problems appear to be in IBM-distributed code, contact the IBM® support center. Restarting JES2 might correct the problem, however, if the condition is a result of tuning, attempting to restart JES2 can aggravate the condition.

Module

HASJSPLR

Routing Code: 1,2,10,42 or as a command response

Descriptor Code: 2,7 or 5 when a command response

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014