z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


02A

z/OS MVS System Codes
SA38-0665-00

02A

Explanation

An error occurred during execution of a data management request for a spool data set. The hexadecimal reason code in Register 2 indicates the cause of the abend:
Code
Explanation
00000004
HASP access method found that a data management control block (ACB or DEB) was not valid.
00000008
HASP access method found that a JES2 UBUF was not valid.
0000000C
HASP access method detected a serialization error for a spool data set.
00000010
HASP access method found that SETPRT failed when printing UBUF.
00000014
HASP access method found a bad BFDLOC value during GET processing.
0000001C
HASP access method detected inconsistent temporary protected buffer pointers.
00000020
HASP access method detected a serialization error for an internal reader data set.
00000024
HASP access method detected a JES2 internal logic error when processing an internal reader data set.
00000028
HASP access method detected an invalid extent in MTTR during PUT processing.
0000002C
HASP access method found a spool control record that is not valid during PUT processing.
00000030
HASP access method detected an error (loop condition) in HPUTFULL processing.
00000034
HASP access method detected an error (loop condition) in HAMFIX processing.
00000038
HASP access method detected an error (loop condition) in HAMSIO processing.
0000003C
HASP access method detected an error in HCPBUFND processing.
00000040
HASP access method found unauthorized use of authorized request parameter list (RPL) option during protected PUT processing.
00000044
HASP access method detected a serialization problem for JES2 BAT problem.
00000048
HASP access method detected a JES2 internal logic error in a single-buffer mode.
0000004C
HASP access method detected a JES2 internal logic error–migration processing was invoked when local lock was held.
00000050
Start of changeBAT with active I/O operation was discovered after HAM access method quiesced all I/O.End of change
Start of change00000054End of change
Start of changeHASP access method detected a corrupted JES2 BAT chain.End of change
Start of change0000005CEnd of change
Start of changeCorrupted Job Symbol Table (JSMT) was found on SPOOL.End of change
Start of change00000060End of change
Start of changeInternal error detected when performing symbol substitution in instream dataset.End of change
Start of change00000064End of change
Start of changeInternal error detected when performing logging of results of the symbol substitution in instream dataset.End of change
Start of change00000068End of change
Start of changeUnable to allocate storage for the BAT control blocks needed for the SPOOL I/O operations.End of change

System action

The system ends the task, and produces a dump. For reason codes X'0000000C' and X'00000020', the system terminates the job step, and produces a dump.

System programmer response

Obtain the program listing for the job. Look at the messages in the job log. If the JOB statement did not specify MSGLEVEL=(1,1), specify it and run the job again.

Verify that the problem program did not modify data management control blocks or the JES2 UBUF control block. For reason codes X'0000000C' and X'00000020', also verify that the problem program used proper serialization techniques for sharing a SYSIN, SYSOUT or internal reader data set among multiple tasks. After making corrections, execute the job step again.

If the problem recurs and if the program is not in error, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM® Support Center.

In case of reason codes X'00000030' through X'0000003C', contact the IBM Support Center with dump and SYSLOG.

Source

JES2

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014