$HASP246

Explanation

>>-DISASTROUS ERROR--+-WRITING-+--+-SPOOL--+--MESSAGES---------><
                     '-READING-'  '-REMOTE-'             

 A disastrous error occurred while JES2 was
reading or writing commands and messages to or from the spool volumes
or a remote console. The system has discarded commands and messages.
 Possible causes of this problem are any of the following:  The time of day (TOD) clock setting for one of the systems is
out of synchronization relative to one or more of the other systems.
The synchronization tolerance is specified by the SYNCTOL parameter
on the MASDEF initialization statement.
Physical I/O errors on the spool volumes may have occurred if
the system has issued message $HASP094. See the explanation of that
message.
JES2 ended with a $Q02 abend and was then restarted with a hot
start.

System action
 Processing continues.

Operator response
 Notify the system programmer. The system
may issue message $HASP096 or $HASP094.

System programmer response
  If JES2 has issued an associated
$HASP096 message or a $HASP094 message, see the explanation of that
message for more information. Do the following: 
 For cause 1, correct the clock values on the system in error with
the older clock value. IPL to set the TOD clock and perform a single
system warm start.
For cause 2, evaluate the $HASP094 explanation. Consider evaluating
the disk surface for bad cylinders in the SYS1.HASPACE data set or
consider possible spool contamination (logical error in processing
on spool).
For cause 3, see the $Q02 explanation under $HASP095. To ensure
a clean recovery from a $Q02 abend, perform an all-member warm start
of JES2.

Module
 HASPRTAM
 Routing Code: 8,10
 Descriptor Code: 4