0F7

Explanation
The system found a serious error condition in the
JES2 component specific user environment (HASCxxxx) load modules.
The REASON parameter on the ABEND macro specifies a hexadecimal reason
code that further explains the error. The system records the hexadecimal
reason code associated with this abend in a logrec data set record. Code
Explanation
00
A subsystem interface (SSI) function was unable to cancel an outstanding
ESTAE recovery program, probably because the TRETOKEN field in the
TCB recovery element ($TRE) control block was overlaid during that
SSI function. Following is the text associated with this reason code: ‘UNABLE
TO CANCEL ESTAE’.
04
A task attempted to acquire the lock of two distinct subsystem
job blocks (SJBs); a task may lock only one SJB at a time. Following
is the text associated with this reason code: ‘ATTEMPT MADE
TO LOCK TWO SJBS AT ONCE’.
08
While attempting to return a common storage area (CSA) cell to
the cell pool, $FRECEL routine found one of the following error conditions: The cell being returned does not have a valid cell control element
(CCE) address at offset 0
The cell being returned has not been allocated.
Storage has been overlaid in either the first four bytes
of the cell being returned, or in the CCE associated with the cell.
Following is the text associated with this reason code: ‘INVALID/UNCLAIMED
CELL ADDRESS’.

0C
During a functional subsystem or functional subsystem application
(FSS/FSA) disconnect, a GETMAIN failed to obtain storage from subpool
230 for a parameter list. Following is the text associated with this
reason code: ‘DISCONNECT DENIED-- GETMAIN FAILURE’.
10
During the Job Termination SSI function, the final input/output
table (IOT) could not be written to spool. Following is the text associated
with this reason code: ‘UNABLE TO WRITE FINAL IOT CHAIN’.
14
While attempting to end processing for a job under the control
of an execution batch monitor (joblet), the Job Termination SSI was
unable to locate the PDDB for the job journal. (The PDDB is the control
block that defines a spool data set.) Therefore, the Job Termination
SSI could not nullify the joblet-related spool dataset so that it
could be reused for the next joblet. Following is the text associated
with this reason code: ‘UNABLE TO FIND JOB JOURNAL PDDB’.
18
The common storage $RETURN service determined that there was no
previous save area address associated with the current save area.
Therefore, the service was unable to return to the proper location.
Following is the text associated with this reason code: ‘NO
PREVIOUS SAVE AREA FOUND’.
1C
The JES2 exit effector determined that the exit was invoked from
an FSS assembly environment.  However, while attempting to load the
address of the HFCT control block for the exit, the exit effector
found that the address space was not properly initialized. Following
is the text associated with this reason code: ‘ASXBJSVT DOES
NOT CONTAIN FSVT ADDRESS’.
20
While attempting to write the job control table (JCT) to spool,
the job termination routine received a nonzero return code, probably
because of one of the following: An I/O error
JCT storage was overlaid.

 Following is the text associated with this reason code: ‘UNABLE
TO WRITE JCT’.
24
Without holding a subsystem job block (SJB) lock, the caller attempted
to obtain the job communication queues lock ($SVJLOK) that serializes
communication between address spaces. Following is the text associated
with this reason code: ‘$SVJ LOCK REQUEST FAILED’.
28
A TCB attempted to preempt a holder of the SJB lock while producing
a dump for an abend that occurred while the SJB lock was held. Following
is the text associated with this reason code: ‘UNABLE TO OBTAIN
SJB LOCK’.
2C
Storage could not be obtained for the service request block (SRB)
work area. Following is the text associated with this reason code: ‘HASCDSS
DATA SPACE SERVICES FAILURE’.
30
HASCDSS was entered with a function other than CREATE or DELETE.
Following is the text associated with this reason code: ‘HASCDSS
DATA SPACE SERVICES FAILURE’.
34
The value given for the BLOCKS parameter was either negative or
zero. Following is the text associated with this reason code: ‘HASCDSS
DATA SPACE SERVICES FAILURE’.
38
RMTR EXIT recovery processing was entered. Following is the text
associated with this reason code: ‘HASCDSS DATA SPACE SERVICES
FAILURE’.
3C
FRR recovery processing was entered. Following is the text associated
with this reason code: ‘HASCDSS DATA SPACE SERVICES FAILURE’.
40
The MVS™ macro DSPSERV failed.
Following is the text associated with this reason code: ‘HASCDSS
DATA SPACE SERVICES FAILURE’.
44
The MVS macro ALESERV failed.
Following is the text associated with this reason code: ‘HASCDSS
DATA SPACE SERVICES FAILURE’.
48
The address space control block (ASCB) for the address space that
will own the data space is not equal to the current ASCB. Following
is the text associated with this reason code: ‘HASCDSS DATA
SPACE SERVICES FAILURE’.
4C
Incorrect $DSWA version number. Following is the text associated
with this reason code: ‘HASCDSS DATA SPACE SERVICES FAILURE’.
50
JES2 SAVE/RETURN services detected an error. Following is the
text associated with this reason code: ‘CALLER ADDRESS ARRAY
FILLED UP’.
54
JES2 SAVE/RETURN services detected an error. Following is the
text associated with this reason code: ‘NO ENTRY IN CALLER ADDRESS
ARRAY.’
58
JES2 SAVE/RETURN services detected an error. Following is the
text associated with this reason code: ‘$RETURN - SAVE AREA
HAS IMPROPER FORMAT.’
5C
JES2 SAVE/RETURN services detected an error. Following is the
text associated with this reason code: ‘ENTERED $SSIEND WITH
AN OUTSTANDING $SAVE’.
60
JES2 detected an error while processing a scheduler JCL facility
request. Following is the text associated with this reason code: ‘SJF
SERVICE REQUEST FAILED’.
64
JES2 detected an error while grouping SYSOUT. Following is the
text associated with this reason code: ‘INVALID GROUPING STRINGS
OBJECT’.
68
JES2 detected an error while grouping SYSOUT. Following is the
text associated with this reason code: ‘SWBTUREQ RETRIEVE ERROR’.
6C
JES2 detected an error while grouping SYSOUT. Following is the
text associated with this reason code: ‘INVALID STORAGE BLOCK
POINTER’.
70
JES2 detected an error while grouping SYSOUT. Following is the
text associated with this reason code: ‘SJFREQ KEYLIST ERROR’.
74
JES2 detected an error while building a generic grouping token.
Following is the text associated with this reason code: ‘UNEXPECTED
NUMBER OF SWBIT BUFFERS’.
78
JES2 SAVE/RETURN services detected an error. Following is the
text associated with this reason code: ‘ENTERED $SSIEND WITH
AN OUTSTANDING $ESTAE’.
7C
JES2 detected an error while unlocking a $SJB. Following is the
text associated with this reason code: ‘SJB UNLOCK NOT BY LOCK
HOLDER’.
80
JES2 detected an error while freeing storage buffers. Following
is the text associated with this reason code: ‘NOT ALL PROTECTED
BUFFERS $FREEBUFED’.
84
The $GETHP service detected an error while freeing a task control
block recovery element ($TRE). Following is the text associated with
this reason code: ‘$GETHP ERROR - ATTEMPTED TO FREE THE TRE’.
88
The FRETRE service detected a loop in the cell pool chain.
8C
The GETTRE service detected an error in the $TRE cell pool chain.
Following is the text associated with this reason code: ‘GETTRE
ERROR’.
90
The system encountered a failure while serializing a JES2 trace
table entry. Following is the text associated with this reason code: ‘$TRACER
Trace Table ENQ Error’
94
Truncation of the protected buffer failed.Following is the
text associated with this reason code: ‘UNABLE TO TRUNCATE PROTECTED
BUFFER’.

98
A routine in CSECT HASCRQUE detected an erroneous input parameter.
9C
An incorrect resource number was passed to the $$POST macro.
A0
JES2 detected inconsistent temporary protected buffer pointers.
A4
JES2 requested an ENQ for the SVJ lock but received an unexpected
return code.  The return code from ENQ is in register 2.
A8
JES2 detected a problem in an SJB.  The SJB is not on the expected
queue.  The SJB address is in register 10.
AC
JES2 detected a problem in an SJB.  The SJBQUEUE field is not
valid. The SJB address is in register 10.
B0
JES2 detected a problem in an SJB.  The SJB is not on the queue
indicated in SJBQUEUE.  The SJB address is in register 10.
B4
JES2 detected a problem in an SJB.  The SJB is not on the queue
indicated in SJBQUEUE.  The SJB address is in register 10.
B8
Following an unrecoverable I/O error, JES2 detected that channel-end
processing requested, incorrectly, to re-drive the I/O. The text associated
with the reason code is:  INTERNAL ERROR IN CHANNEL END PROCESSING
BC
JES2 detected a problem during a rebuild of the SJB queues. Either
the $HAVT is bad, or the SVJ lock was not held at entry to the rebuild
routine.
C0
The caller of SJBRQ attempted to move the SJB to a different job
communication queue, but did not hold the SVJ lock.
C4
An invalid SAPID pointer was passed in the SSS2 (SAPI, IAZSSS2)
SSOB extension.
C8
The fields that should be zeroes in the SSS2 (SAPI, IAZSSS2) SSOB
extension were not zeros.
CC
An SJF Request error occurred on an GETDS/SAPI request.
D4
The MVS Cell Pool Service
returns a non-zero return code when JES2 calls the MVS service to process $CPOOL ACTION=GET request.
Following is the text associated with the reason code: '$CPOOL ACTION=GET
FAILED TO ALLOCATE THE CELL'.
D8
The MVS Cell Pool Service
returns a non-zero return code when JES2 calls the MVS service to process $CPOOL ACTION=FREE request.
Following is the text associated with the reason code: '$CPOOL ACTION=FREE
FAILED TO FREE THE CELL'.
DC
When processing a PSO SSI request, JES2 discovered that the $PSO
control  block is in error. Following is the text associated with
the reason code: '$PSO NOT VALID'. 
E0
An inconsistency was detected between the input parameter list
(XMPLIST)  supplied to $XMPOST, and the parameters specified to $XMPOST.
Following is the text associated with the reason code: '$XMPOST PARAMETER
LIST NOT VALID'.
 E4
An error was encountered removing a element using $FIFODEQ which
specified ABENDERR=YES.  The requested element was not found on the
chain. Following is the text associated with this reason code: 'FIFODEQ
ElEMENT NOT ON QUEUE'.
 E8
JES2 end of memory processing was unable to access an SJB that
is associated with the terminating address space.  A VSMLOC for the
SJB storage failed. Following is the text associated with this reason
code: 'SJB MEMORY NOT AVAILABLE'. 
EC
$SUBIT request was made from an address space that does not support
$SUBIT requests (not a NETSERV address space). Following is the text
associated with this reason code: 'SUBIT, NOT A NJE SERVER ADDRESS
SPACE'. 
F0
A request buffer queued by JES2 to a NETSERV address space does
not have a valid request type (TBFTYPE or NRQEYE is not valid). Following
is the text associated with this reason code: 'UNRECOGNIZED TBUF DATA'. 
F4
A JES2 owned subtask in the NETSERV address space has terminated
in such a way that the NETSERV address space must come down. 
F8
The $GETTBUF or $FRETBUF service was called from outside a NETSERV
or the JES2 address space. Following is the text associated with this
reason code: '$FRETBUF CALLED FROM INCORRECT ADDRSPC' or '$GETTBUF
CALLED FROM INCORRECT ADDRSPC'. 
FC
The $GETABLE service has located a table pair in which the JES2
table pointer points to a USER table, or the USER table pointer points
to a HASP table, or a dynamic table pointer does not point to a dynamic
table. The probable cause is either a mismatch of levels of the $MCT
macro, or a failure to use the $PAIR macro to define a table pair.
Following is the text associated with this reason code: '$GETABLE
- INVALID TABLE ENTRY'. 
100
The NETSERV early init routine (in HASCNJEX) has been entered
more than once. Following is the text associated with this reason
code: 'MULTIPLE ROUTINE CALLS'.
104
The length of the message passed to the $NOTIFY service exceeds
the maximum length allowed (132 bytes). Following is the text associated
with this reason code: 'INCORRECT NOTIFY MESSAGE LENGTH'. 
108
Storage key of the ECB encountered by the $ECBEXIT service is
8 or greater.  This implies either a bad ECB pointer was passed to
$XECBSRV or an unauthorized user is attempting to use a service illegally.
Following is the text associated with this reason code: '$ECBEXIT
- UNAUTHORIZED ECB DETECTED'. 
10C
JES2 (CJOBVFY service) detected an error in the parameter list
passed to the Security Authorization Facility (SAF) to validate the
job. Following is the text associated with this reason code: 'JOBVALM
PARM LIST ERROR'. 
110
JES2 (CJOBVFY service) is validating a job that is to execute
locally, however the SAF token returned by JOBVALM is a submitter
token.  The job being processed will be purged. Following is the text
associated with this reason code: 'JOBVALM TOKEN TYPE ERROR'. 
114
NJE JOB header passed to CJOBVFY is in error. Following is the
text associated with this reason code: 'CJOBVFY NJE HEADER ERROR'. 
118
NJE JOB header corruption detected when trying to locate the SPOOL
offload section. Following is the text associated with this reason
code: 'NJE JOB HEADER/TRAILER CORRUPTED'.
11C
ENQ error encountered while attempting to serialize SPOOL space
allocation (TRKCELL routine, TRACK GROUP ALLOCATION ENQ minor name).
Following is the text associated with this reason code: 'TBLOB ENQ
ERROR'. 
120
ENQ error encountered while attempting to serialize CPOOL build
processing (CPBUILD routine, 'cell_pool_type' CPOOL EXPAND minor name).
Following is the text associated with this reason code: '$CPOOL BUILD
ENQ FAILED' or '$CPOOL EXPAND ENQ FAILED'. 
124
JES2 CPOOL GET service detected an update to a free cell. This
update occurred after the cell had been freed. Following is the text
associated with this reason code: 'STORAGE DEBUG CHECK FAILED'. 
128
JES2 CPOOL FREE service detected an alteration to a guard byte
past the end of a cell.  The user of the cell updated storage beyond
the end of the cell. Following is the text associated with this reason
code: 'INVALID STORAGE REFERENCE'.
12C
$NSSTLOK service was called requesting shared access to a JES2
NSST lock by a subtask not known to JES2. Following is the text associated
with this reason code: 'INCORRECT $NSSTLOK ENVIRONMENT'.
130
Error releasing main storage area.Following is the text associated
with this reason code: 'ATTEMPT TO FREE SUBPOOL 0’.

134
Error releasing main storage area.Following is the text associated
with this reason code: 'UNEXPECTED LENGTH OF 0’.

138
A return code of X'18' was returned to JES2 when attempting
to perform an ENQ with the minor name of 'WAITING FOR SPOOL SPACE".
The text is "TBLOBE ENQ ERROR".
13C
An error occurred when a JESXCF service to retrieve messages was
invoked. The text associated with this reason code is FAILURE FROM
AN JESXCF SERVICE. 
140
A recursive call has been detected in module HASCSISC.
144
Unrecoverable error in remote health checker task.
148
Sysout transmitter for TCP/IP discovered null NDH pointer.Following
is the text associated with this reason code: 'NDH POINTER IS NULL’.

150
An invalid DSERV address has been given to the $DSERV service. Following
is the text associated with this reason code: 'BAD DSERV POINTER’.
154
Unrecoverable error detected during $BLDMSG service processing.
The text associated with this reason code is $SCAN ERROR DETECTED.
158
SSI 83 encountered CDCT control block with undefined device type.
The text associated with this reason code is 'Invalid CDCT device
type'.
160
Spin processing was invoked without having SJB lock. The text
associated with this reason code is 'SJB lock not held HFEXJES'.
168
Migration track bitmap was not found during SPOOL migration. The
text associated with this reason code is 'Bitmap problem during SIGIOU
processing'.
16C
$BITMAP service was requested to perform operation on a bit outside
of the bitmap. The text associated with this reason code is '$BITMAP
boundary error'.
178
JES2 detected a JES2-generated data set name that contains invalid
characters. The following text is associated with this reason code:
'Bad character in dataset name'.
17C
There is an error in address space management.  Either a "stale"
HASB has been found (left over from a prior user of the same address
space) or the HASB has been damaged.
180
An SJB has been found to have incorrect data.  One or more of
the following does not match:ASID
Address space Token
Eye catcher (SJB)
JES2 subsystem name

380
$SSIBEGN HASB SJB Q error.
384
$SJBFIND HASB SJB Q error.

System action
If an SSI function took the $ERROR, the system
produces a dump (unless the dump is suppressed by dump analysis elimination
(DAE)), and the SSI function's caller receives a disastrous error
indication upon return. Otherwise, the system abnormally ends the
program.

Programmer response
Take one of the following actions, depending
on the reason code associated with this abend. If the application
programmer response is not specified here, then search problem reporting
databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.Code
Response
00
Determine whether the task control block recovery element ($TRE)
control block was properly addressed, and whether that control block
has been overlaid.
04
Ensure that you release the lock for one SJB before you attempt
to acquire the lock of another SJB.
08
Verify that offset 0 of the cell points to a valid CCE, and shows
that the cell is allocated.
0C
Determine why subpool 230 has been depleted.  Correct the error.
10
Determine why $CBIO failed while attempting to write the IOT chain.
Refer to z/OS JES2 Macros for
information about the return codes for $CBIO.
14
Determine why the PDDB cannot be located.  Correct the error.
Note that an SSI ESTAE recovery program is not active for this abend
because the call to end the job originates from the HASCHAM assembly
module.
18
Determine whether the save area has been overlaid; if not, determine
whether the caller intended to issue a $RETSAVE macro instead and
correct any errors found in the $RETSAVE macro.
1C
Ensure that the following conditions are met: The assembly module that issued the $EXIT call is assembled with
the correct ENVIRON parameter on the $MODULE statement.
The FSS address space is fully initialized before the $EXIT call
is attempted.

20
Determine why $CBIO failed while attempting to write the IOT chain.
Refer to z/OS JES2 Macros for
information about the return codes for $CBIO.
24
Ensure that the caller holds an SJB lock before attempting to
obtain the $SVJLOK.
28
Determine the caller of the $SJBLOCK routine. Notify your programming
support personnel.
FC
Ensure that table pairs have been defined correctly. Ensure that
all modules referencing table pair definitions have been assembled
with the same level of the $MCT macro.
104
Ensure that the message passed to the $NOTIFY service is not longer
than 132 characters.
124
Determine if the data area being updated was previously owned
by JES2 or by a user exit.  Since the data area itself had been zeroed,
it may require a search of the System Trace to determine who last
owned the data area. Attempt to determine where the update access
was made and if in IBM code,
search problem reporting databases for a fix for the problem. If no
fix exists, contact the IBM Support
Center.
128
The data area being freed is the most likely cause of the error.
 Ensure that the modules referencing the data areas have all been
assembled with the correct level of macros (including HASCPOOL). If
the data area was owned and managed by IBM code,
search problem reporting databases for a fix for the problem. If no
fix exists, contact the IBM Support
Center.

Source
JES2