Disastrous errors

JES2 issues message $HASP096 when a job encountered a disastrous error. The message identifies the job that encountered the disastrous error.

A “disastrous” error can be:

a JES2 logic error
a critical I/O error has occurred on SYS1.HASPACE data set (if the $HASP096 message is accompanied by a I/O error message).

When the situation occurs a $HASP096 message is issued and based on the installation defined RECVOPTS a system dump may be obtained.

Examine the sequence of events in SYSLOG that lead up to the error. Check your RECVOPTS(DISTERR) initialization statement to see if you should change the count defined in the initialization stream. Enter the $D RECVOPTS(DISTERR) command to see the count and interval specified in the initialization statement. Too low a count for RECVOPTS(DISTERR) causes JES2 to suppress dumps when the number of disastrous errors exceeds the count in a 24-hour period; you will lose helpful diagnostic information.

Also determine if any initial program loads (IPL) occurred between the time the job ran and before output for the job was processed. If you must recreate the error, you should set JES2 trace 3.