Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
$HASP9211 z/OS JES2 Messages SA32-0989-01 |
|
$HASP9211 ExplanationJES2 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:
System actionIf the condition persists, JES2 reissues this message every 30 seconds with updated information. Operator responseMonitor alerts indicate potential reasons why JES2 is not functioning properly. If this condition persists, notify your system programmer. System programmer responseJES2'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:
ModuleHASJSPLR Routing Code: 1,2,10,42 or as a command response Descriptor Code: 2,7 or 5 when a command response |
Copyright IBM Corporation 1990, 2014
|