Abend Codes and explanation

 

Thanks for visiting my blog, if you feel my blog helped you or worth reading for someone please like mainframegeek facebook page.

Abend Codes

Abend happens during the execution of a program in a step(JCL). Generally it can be categorized into system abend and user abend.

  • System Abend – It will occurs when the system is not able to execute a statement which is coded in a program. This abend code will be thrown by OS.
  • User Abend – This is due to unexpected condition occurs in data passed; this abend will be thrown by application based on the requirement.

Condition Code Abends

CC=0001 – (1016) PIE JOBS – BAD PART NUMBER – FOLLOW PACBOOK VERY CAREFULLY

CC=001 – I/O ERROR

CC=002 – I/O INVALID RECORD

CC=0004 – DATASET NOT FOUND, TABLESPACE IN COPY PENDING, ETC MAY BE OK(CHECK COND STATEMENTS OR CALL ADM TO VERIFY)

CC=0008 – EQUIP CHECK, UNABLE TO DBR DB RLAO00, RC-08 SQL ERROR, EMPTY DATASET

CC=0010 – (CC=0016 IN HEX) BAD DATA

CC=0012 – I/O ERROR TAPE, VSAM DATASETS CLOSED, INVALID DATA, EMPTY TABLE, COULD BE ANYTHING

CC=0014

CC=0016 – COULD BE ANYTHING, CONTENTION ,INVALID DATA, EMPTY TABLE, # OF FILES EXPECTED NOT EQUAL TO # OF FILES RECEIVED

CC=0020 – COULD BE ANYTHING (CATCHALL)

CC=0030 – DB2 TABLES WRONG DATES

CC=0152 – ERROR ATTEMPTING TO TRANSLATE NEXT TRANSACTION

CC=0696 – FTP LINE DOWN

CC=804 OR 80A – REGION SIZE TOO SMALL – SPECIFY REGION=0M

CC=1000 – BAD DATA, CONTENTION(-911)

CC=1008 – TOTALS OUT OF BALANCE

CC=1016 – NUMBER OF FILES EXPECTED DOES NOT EQUAL NUMBER RECEIVED, BAD DATA, CONTENTION

CC=1999 – DATA EXCEPTION, BAD DATA

CC=2000 – RESOURCE NOT FOUND (07D0), PROGRAMMING ERROR WAITING FOR FILE, RACF (-922), REBIND (-805)

CC=2004 – CYCLE OUT OF SEQUENCE

CC=2016 – TOO MUCH DATA FOR ARRAY SIZE, TABLE UPDATE INCORRECT, NULL DATA

CC=2444 – INVALID RECORD LENGTH

CC=8000 DATASET ALREADY IN USE, I/O ERROR, FILES NOT SENT RESOURCE NOT AVAILABLE

CC=FFF – FATAL INTER ADDRESS COMMUNICATION ERROR


User Abends

U046 – NOT ENOUGH OR NO SORT WORK SPACE ALLOCATED.

U048 – USER DOES NOT HAVE ACCESS AUTHORIZATION FOR THE DATASET

U061 – REORDER DATASETS, CHECK BLOCKSIZES. LARGEST BLOCKSIZE FIRST

U063 – CHECK SPELLING OF DD STATEMENTS

U099 – DATASET NOT FOUND

U0000 – DB2 STOPPED UTILID, TABLESPACE

U0007/U0240 – VSAM I/O ERROR ON ACKS DATASET(WIDEBAND PROBLEM)

U0100 – USER ERROR

U0102 – PROBLEM WITH CHECKPOINT – MAY NOT HAVE BEEN ANY CHECKPOINTS

U0103 – ENTRY NOT FOUND

U0111 – TAPE TOO SHORT

U0136 – I/O Error on a Read Data CCW for the first VTOC record on a migration target volume

U0240 – BAD TRANSMISSION

U0378 – I/O ERROR, DIRTY TAPE DRIVE, EQUIP CHECK

U0436 – INVALID REGION ID IN IMS COMMAND

U0437 – RACF, INSUFFICIENT ACCESS AUTHORITY, SECURITY PROBLEM

U0452 – STOPPED TRANSACTION OR PROGRAM

U0456 – PROGRAM DOWN, PROGRAM NOT FOUND

U0457 – TRANSACTION STOPPED, CONTENTION

U0474 – IMS NOT AVAILABLE(COULD BE BECAUSE DB2 CONNECTION IS DOWN)

U0476 – APPLICATION PROGRAM HAS INVALID PCB

U0659 – TAPE POSITIONING ERROR

U0688 – IMS DOWN

U0777 – CONTENTION

U0778 – BAD DATA, DATABASE NOT AVAILABLE(CONTENTION), ETC.

U0746 – BAD DFP CODE

U0779/U0888 – VOLUME FENCED

U0999 – BAD DATA

U1812 – I/O ERROR WRITING THE TAPE MARK DURING CLOSING OF A MACRO INSTRUCTION.

U2000 – I/OR ERROR. CHECK THE STEP WHERE THE ABEND OCCURRED. LOOK FOR AN ONCODE ERROR AT THE BOTTOM OF THE JCL.

U2052 – INCREASE REGION SIZE, NOT ENOUGH CORE.

U3042 – DB2 NOT AVAILABLE

U3312 – DBRC INITIALIZATION FAILED. CHECK AUTHORIZED SUBSYSTEM.

U3690 – SYSTEM SOFTWARE OR DISK PROBLEM OCCURRED DURING THE EXECUTION OF A LINK OR LOAD INSTRUCTION / INSURE THAT THE LOAD REQUEST IN THE PROBLEM WAS SPECIFIED CORRECTLY AND WAS NOT INCORRECTLY MODIFIED

U3999 – CONTENTION, BAD DATA

U4047– IMS PROBLEM(POSSIBLY PROGRAM OR TRAN DOWN)

U4048 – GETMAIN PROBLEM – INSUFFICENT STORAGE(INCREASE REGION SIZE)

U4087 – A recursive error was detected. A condition was raised, causing the number of nested conditions to exceed the limit set by the DEPTHCONDLMT option. The reason code indicates which subcomponent or process was active when the exception was detected.

U4095 – CONTENTION

UFB0 – B37 – (SPACE)

UBB8 – BAD TRAILER RECORD

UB888 – (U3000) FILE ID DOES NOT MATCH CONTROL FILE, FILE OUT OF SEQUENCE

UFA2 – INVALID DATA IN CONTROL TABLE

U3E7 – INVALID DESTINATION, DATASET NOT FOUND, BAD DATA, ETC.

U1C8

U2500

U3000 – FILE OUT OF SEQUENCE

U3303 – DATABASES DOWN

U3391 – BAD DATA

U3501 – BAD DATA, DCB MISSING

U3400 – BAD DATA

U3502 – BAD CONTROL CARD

U3507 – INSERT TO CERIS ACTIVITY LOG, BAD DATA

U4000 – SOURCE DOES NOT EXIST, PROGRAM TERMINATED, BAD DATA

U4002 – DB2 TABLESPACE IN RECP, IN RO DUPLICATE DATA(-904), UNAVAILABLE RESOURCE

U4012 – MISSING REGION PARAMETER

U4092 – CONTENTION


XE03 – DUPLICATE DATASET NAMES

XE04 – CONTENTION S013-18 – MISSING MEMBER, MEMBER NOT FOUND IN PDS


System Abends

S001 – AN INPUT/OUTPUT ERROR CONDITION WAS ENCOUNTERED DURING EXECUTION OF A CHECK/GET/PUT MACRO INSTRUCTION. EITHER NO SYNAD ROUTINE WAS PROVIDED TO HANDLE THE ERROR, OR DCB=EROPT=ABE WAS SPECIFIED OR DEFAULTED.
IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S001 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S001-RC)
POSSIBLE CAUSE
INPUT RECORD DESCRIBED INCORRECTLY, LENGTH ERROR
TRIED TO READ AFTER ENCOUNTERING END OF FILE
RECFM V IS INCOMPATIBLE WITH TRTCH ET
TRIED TO WRITE ON AN INPUT FILE
READ INTO A TABLE WHOSE SUBSCRIPT WAS ZERO
INCORRECT LABEL PARAMETER
TRTCH PARM WAS WRONG
TAPE BEING READ IN WRONG DENSITY
DIRECTORY OF PDS WAS OVERWRITTEN
NSL LABEL HAD INCORRECT DSNAME, OPERATOR CANCELLED
TRUE I/O FAILURE, UCB SHOW REDUNDANCY
HARDWARE ERROR – BAD TAPE OR TAPE DRIVE
SECONDARY SPACE ALLOCATION FOR DASD OUTPUT FILE TOO SMALL (SEE SB37)
COBOL – INCORRECT USE OF BLOCK CONTAINS CLAUSE
– HAD RECORDING MODE F WHEN GENERATED, BUT NOT WHEN READ

S001 – 01 – AN I/O ERROR OCCURRED DURING BDAM CREATE, BSAM, BISAM, QSAM, OR BDAM AND NO SYNAD EXIT WAS SPECIFIED BY THE USER.

S001 – 02 – AN ERROR WAS ENCOUNTERED WHILE ATTEMPTING TO CLOSE THE DATASET.

**S001 – 03 – FOR QSAM, AN ERROR WAS ENCOUNTERED THAT COULD NOT BE ACCEPTED.

S001 – 04 – FOR QSAM, ABE OR AN INVALID VALUE FOR EROPT PARAMETER IN THE DCB AND/OR NO ERROR HANDLING (SYNAD) EXIT WAS SPECIFIED.

S001 – 05 – FOR QSAM, A GET WAS ISSUED AFTER END-OF-FILE.

S002 – RECORD IS GREATER THAN 32,768 BYTES, EXCEEDS MAXIMUM TRACK LENGTH OR STATED BLOCKSIZE, COULD NOT BE CONTAINED IN ONE EXTENT, OR TOO MANY TRACKS SPECIFIED FOR CYLINDER OVERFLOW.
IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
S002 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S002-RC)
POSSIBLE CAUSE
DCB HAD THE WRONG BLOCK SIZE
IEHMOVE – ATTEMPT TO RENAME DATA SET WHEN NEW NA
ME ALREADY EXISTS
WRONG RECORD FORMAT SPECIFIED IN JCL

S002 – 04 – AN INVALID RECORD WAS ENCOUNTERED ON A GET OPERATION.
THE LENGTH FIELD OF A RECORD DESCRIPTOR WORD (RDW) FOR A VARIABLE LENGTH RECORD SPECIFIES A VALUE LESS THAN 4.

S002 – 08 – AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION. THE RECORD OR BLOCK LENGTH PLUS THE KEY LENGTH AND REQUIRED OVERHEAD ADD UP TO MORE THAN 32,767 BYTES.

S002 – 0C – AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION. THE RECORD OR BLOCK LENGTH PLUS THE KEY LENGTH AND REQUIRED OVERHEAD IS GREATER THAN THE DASD TRACK CAPACITY.

S002 – 10 – AN INVALID RECORD WAS ENCOUNTERED ON A PUT OPERATION;
THE DATASET USES THE TRACK OVERFLOW FEATURE. THE RDW FOR A VARIABLE LENGTH RECORD SPECIFIES A LENGTH GREATER THAN 32,752.

S002 – 14 – AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION. THE RECORD LENGTH IS GREATER THAN THE BLOCKSIZE SPECIFIED IN THE DCB.

S002 – 18 – AN INVALID RECORD WAS ENCOUNTERED ON A PUT OPERATION;
THE DATASET USES THE VARIABLE RECORD FORMAT. THE LENGTH VALUE OF THE RDW IS EITHER: LESS THAN 4, GREATER THAN 32,767, GREATER THAN THE BLOCKSIZE SPECIFIED IN THE DCB, OR LESS THAN 5 IF ASA CONTROL CHARACTERS ARE BEING USED.

S002 – 1C – THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. A WRITE MACRO WAS ISSUED FOR A RECORD LARGER THAN THE TRACK CAPACITY, AND THE RECORD FORMAT DOES NOT USE THE TRACK OVERFLOW FEATURE.

S002 – 20 – THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. A WRITE MACRO WAS ISSUED CAUSING A SECONDARY EXTENT TO BE OBTAINED. THE BLOCK WILL NOT FIT ON THE AMOUNT OF SPACE ALLOCATED FOR THE
SECONDARY EXTENT.

S002 – 24 – THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. A WRITE MACRO WAS ISSUED TO WRITE OUT A BLOCK LARGER THAN THE PRIMARY EXTENT ON THE PREALLOCATED DATASET. THIS COULD ALSO OCCUR IF ALLOCATION OF THE PRIMARY EXTENT WAS NON-CONTIGUOUS AND ANY OF THE SECONDARY EXTENTS WERE SMALLER THAN THE BLOCK.

S002 – 28 – THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. DURING THE EXECUTION OF OPEN IT WAS DETECTED THAT THE BLOCKSIZE WAS LARGER THAN THE PRIMARY EXTENT.

S002 – 2C – THE ERROR OCCURRED WHILE OPENING AN ISAM DATASET. TOO MANY TRACKS WERE SPECIFIED FOR CYLINDER OVERFLOW.

S002 – 30 – ONE OF THE FOLLOWING IS TRUE:
– A READ WAS ISSUED BUT THE LENGTH TO BE READ WAS ZERO.
– A QSAM PUT WITH MOVE MODE WAS ISSUED FOR RECFM=F, FB OR U BUT DCBLRECL CONTAINED A NON-POSITIVE VALUE.

S002 – 34 – A READ MACRO WAS ISSUED FOR AN OUTPUT-ONLY DASD DATA SET.

S002 – 3C – PDSE MEMBER CREATION WAS PREVENTED BECAUSE THE PDSE ALREADY HAD THE MAXIMUM NUMBER OF MEMBERS (2**19 – 2).

S002 – 50 – SERIALIZATION OF AN INTERNAL SAM CONTROL BLOCK (SACB) USED FOPR PROCESSING HAS BEEN VIOLATED.

S002 – 54 – DEBCHK FAILURE DURING PDSE PROCESSING.

S002 – 58 – AN INTERNAL SAM CONTROL BLOCK (SACB) USED FOR PROCESSING PDSE REQUESTS IS INCORRECT.

S002 – 5C – AN INTERNAL SAM CONTROL BLOCK (FRQ) USED FOR QUEUING PDSE REQUESTS IS INCORRECT.

S002 – 60 – NON-ZERO KEYLENGTH SPECIFIED FOR OUTPUT PDSE MEMBER.

S002 – 64 – FOR BSAM, THE READ OR WRITE REQUEST COULD NOT BE ACCEPTED BECAUSE THE VALUE OF NCP INT THE DCB HAD ALREADY BEEN REACHED.

S002 – 68 – INCORRECT BLOCKSIZE SPECIFIED.

S002 – 6C – UNABLE TO CREATE A PDSE MEMBER.

S002 – 70 – UNABLE TO UPDATE AN INTERNAL SAM CONTROL BLOCK (PACB) USED FOR PDSE PROCESSING WITH INFORMATION CONCERNING THE MEMBER BEING ACCESSED.

S002 – 74 – AN INTERNAL SAM CONTROL BLOCK (PACB) USED FOR STORING PDSE DIRECTORY AND MEMBER INFORMATION IS INCORRECT.

S002 – 78 – ERROR RETURN FROM IGWFMPCR WHEN ATTEMPTING TO GIVE CONTROL TO A ROUTINE TO PROCESS PDSE REQUESTS.

S002 – 7C – POINT DETECTED THAT INFORMATION CONCERNING THE MEMBER BEING ACCESSED IS NOT FOUND IN THE PACB.

S002 – 80 – POINT DETECTED AN ERROR WHILE ATTEMPTING TO SYNCHRONIZE DATA ON OUTPUT.

S002 – 84 – POINT DETECTED AN ERROR WHILE ATTEMPTING TO RECONNECT TO A PDSE MEMBER FOR HOLD.

S002 – 88 – POINT DETECTED AN ERROR WHILE ATTEMPTING TO RECONNECT TO A PDSE MEMBER FOR I/O.

S002 – 8C – POINT DETECTED AN ERROR WHILE ATTEMPTING TO DISCONNECT FROM A PDSE MEMBER.

S002 – 90 – POINT DETECTED AN ERROR WHILE ATTEMPTING TO CONNECT TO A PDSE MEMBER.

S002 – 94 – INCORRECT ATTEMPT TO CREATE A PDSE MEMBER SINCE THE MAXIMUM NUMBER OF MEMBERS HAVE ALREADY BEEN CREATED.

S002 – 98 – UNABLE TO COMPLETE A WRITE REQUEST ISSUED WITHIN A PDSE MEMBER.

S002 – 9C – INCORRECT UPDATE WRITE DETECTED. ALL OUTSTANDING READS HAD NOT BEEN CHECKED PRIOR TO THE WRITE.

S002 – A0 – INCORRECT ATTEMPT TO ACCESS A PDSE DIRECTORY. EITHER:
– WRITE ATTEMPTED TO THE DIRECTORY OF A PDSE.
– READ ATTEMPTED TO THE DIRECTORY OF A PDSE AND EITHER THE RECFM WAS NOT F WITH BLKSIZE >= 256
OR
RECFM WAS NOT U WITH BLKSIZE >= 256.

S002 – A4 – UNABLE TO COMPLETE THE READ AGAINST THE PDSE DIRECTORY DUE TO AN ERROR RETURN CODE FROM AN SMS SERVICE USED TO OBTAIN DIRECTORY INFORMATION.

S002 – A8 – MAXIMUM NUMBER OF RECORDS IN MEMBER HAS BEEN EXCEEDED.

S002 – AC – BAD BUFFER FORMAT DETECTED FOR VARIABLE LENGTH RECORDS.
EITHER:
– RDW LENGTH IS LESS THAN 4.
– LENGTH OF SPANNED RECORD IS GREATER THAN 32760.
– THE SUM OF THE LENGTHS IN THE RDWS PLUS 4 DOES NOT EQUAL THE LENGTH SPECIFIED IN THE BDW.
– RECFM DOES NOT SPECIFY BLOCKED BUT MORE THAN 1 RDW IN BUFFER.

S002 – B0 – EITHER RECFM=F AND DCBBLKSI DOES NOT EQUAL DCBLRECL, OR RECFM=FB AND DCBBLKSI IS NOT A MULTIPLE OF DCBLRECL.

S003 – THE ERROR OCCURED DURING END-OF-BLOCK PROCESSING USING EITHER BSAM OR QSAM. THE ERROR OCURRED BECAUSE THE I/O MACRO INSTRUCTIONS FOR A 3525-ASSOCIATED DATA SET WERE NOT EXECUTED IN THE PROPER SEQUENCE.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
– S003 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S003-RC)

S003 – 01 – THE ERROR WAS A READ SEQUENCE ERROR.

S003 – 02 – THE ERROR WAS A PUNCH SEQUENCE ERROR.

S003 – 03 – THE ERROR WAS A PRINT SEQUENCE ERROR.

S004 – THE ERROR OCCURED DURING OPEN PROCESSING USING EITHER BSAM OR QSAM BECAUSE A CONFLICTING OR INVALID DCB PARAMETER (FUNC OR RELATED PARAMETER) IS SPECIFIED.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
– S004 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S004-RC)

S004 – 01 – INVALID DCB FUNC PARAMETER SPECIFIED.

S004 – 02 – INVALID COMBINATION OF DCB FUNC PARAMETER AND CNTRL MACRO SPECIFIED.

S004 – 03 – CONFLICTING ACCESS METHODS SPECIFIED.

S004 – 04 – INVALID DCB SPECIFIED FOR 3505 OR 3525.

S004 – 05 – INVALID FORMAT CARD OR AN INVALID DEVICE SPECIFIED WITH OPTICAL MARK READ (OMR).

S004 – 06 – DATA PROTECTION IMAGE NOT FOUND IN THE SYS1.IMAGELIB DATA SET, VOLUME CONTAINING SYS1.IMAGELIB NOT MOUNTED, OR SYS1.IMAGELIB NOT CATALOGED.

S005 – THE ERROR OCCURRED BECAUSE OF AN INVALID DECB DURING READ PROCESSING USING BSAM.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
– S005 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S005-RC)

S005 – 04 – A REQUIRED ADDRESS WAS NOT SPECIFIED IN THE DECB. THIS CAN BE EITHER THE HEADER ADDRESS AND/OR THE AREA ADDRESS.

S005 – 08 – THE RBL TYPE OF READ WAS NOT USED FOR THE 3886.

S006 – THE PROGRAM HAD AN INCORRECT AUTHORIZATION TO RUN A 1419.

S008 – THE ERROR OCCURRED DURING EXECUTION OF A SYNAD ROUTINE. THE ROUTINE WAS GIVEN CONTROL FOLLOWING EXECUTION OF A BSAM CHECK MACRO INSTRUCTION.

S013 – CONFLICTING OR UNSUPPORTED PARAMETERS IN DCB; MEMBER NAME SPECIFIED IN DD NOT FOUND; NO DIRECTORY ALLOCATION SUBPARAMETER IN DD.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
– S013 OPERAND FOR MORE S
PECIFIC INFORMATION: H ABEND O(S013-RC)

POSSIBLE CAUSE
DCB PARAMETERS CONFLICT, NO BLKSIZE OR NOT VALID MULTIPLE OF LRECL
MISSING OR MISPLACED SYSIN DD CARD
PARTITIONED DATA SET MEMBER NOT FOUND
MERGE – SORTIN01 DOES NOT CONTAIN THE MAXIMUM BLOCKSIZE
JCL – TRIED TO CREATE A PDS WITHOUT ALLOCATING DIRECTORY BLOCKS

S013 – 04 – AMERICAN NATIONAL STANDARD LABELS WERE SPECIFIED IN THE LABEL PARAMETER OF THE DD STATEMENT, BUT ARE NOT SUPPORTED BY THE SYSTEM. CORRECT THE LABEL PARAMETER.
– OPTCD=Q WAS SPECIFIED BUT IS NOT SUPPORTED BY THE SYSTEM. CORRECT THE DCB OPTCD OPTION.

S013 – 08 – AMERICAN NATIONAL STANDARD LABELS WERE SPECIFIED IN THE LABEL PARAMETER OF THE DD STATEMENT, BUT THE UNIT PARAMETER SPECIFIED A 7-TRACK TAPE DRIVE. ANSI LABELS A VALID ONLY FOR 9-TRACK UNITS.

S013 – 0C – A BUFFER LENGTH OF 0 WAS SPECIFIED FOR A BDAM DATASET FOR WHICH DYNAMIC BUFFERING WAS REQUESTED.

S013 – 10 – AN OPEN MACRO WAS ISSUED FOR A NULL DATASET AND BLKSIZE AND BUFL ARE BOTH 0. SPECIFY ONE OR THE OTHER AS NON-ZERO.

S013 – 14 – AN OPEN MACRO WAS ISSUED WITH OUTPUT OR OUTIN SPECIFIED. DCB SPECIFIES DSORG=PO, BUT THE DSCB INDICATES THE DATASET IS NOT PARTITIONED. CHANGE DSORG TO PS, OR CREATE DATASET AS PDS.
– AN OPEN MACRO WAS ISSUED WITH INPUT SPECIFIED. THE DSCB INDICATES THAT DSORG=PO, BUT THE DCB SPECIFIES NEITHER DSORG=PO NOR PS.

S013 – 18 – AN OPEN WAS ISSUED FOR A PARTITIONED DATASET. THE SPECIFIED MEMBER NAME WAS NOT FOUND IN THE DATASET.

S013 – 1C – AN OPEN MACRO WAS ISSUED FOR A PARTITIONED DATASET, BUT AN I/O ERROR WAS ENCOUNTERED SEARCHING THE DIRECTORY.

S013-20 – OPEN MACRO INSTR FOR SEQUENTIAL DATASET USING DCB, BLKSIZE IS NOT A MULTIPLE OF THE LRECL.

S013 – 24 – AN OPEN WAS ISSUED WITH INPUT, INOUT, RDBACK, OR UPDATE SPECIFIED, BUT THE DCB MACRF DID NOT SPECIFY EXCP, GET, OR READ.

S013 – 28 – AN OPEN MACRO WAS ISSUED WITH OUTPUT OR OUTIN SPECIFIED, BUT THE DCB DID NOT SPECIFY A MACRF OF EXCP, PUT, OR WRITE.

S013 – 2C – A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE WITH EXCHANGE BUFFERING WAS OPENED FOR INPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0.

S013 – 30 – A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE WITH EXCHANGE BUFFERING WAS OPENED FOR OUTPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS (DCBBUFCB) WAS 0.

S013-34 – INVALID LRECL(INCOMPATIBLE DCB INFO)

S013 – 38 – AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET ON A DIRECT ACCESS DEVICE WITH TRACK OVERFLOW, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS ZERO. THIS TYPE OF ERROR OFTEN OCCURS IF A DCB IS SHARED BY TWO OR MORE TASKS, OR IS OPENED AND CLOSED SEVERAL TIMES WITHIN ONE JOB STEP.

S013 – 3C – A SEQUENTIAL DATASET WAS OPENED FOR INPUT OR OUTPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0. THIS TYPE OF ERROR OFTEN OCCURS IF A DCB IS SHARED BY TWO OR MORE TASKS, OR IS OPENED AND CLOSED SEVERAL TIMES WITHIN ONE JOB STEP.

S013 – 40 – A SEQUENTIAL OR DIRECT DATASET WAS OPENED FOR INPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0.

S013 – 44 – AN OPEN MACRO WAS ISSUED FOR A DATASET ON A DIRECT ACCESS DEVICE FOR WHICH CHAINED SCHEDULING WAS SPECIFIED, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0.

S013 – 48 – AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS ZERO.

S013 – 4C – AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE. THE SYSTEM DETERMINED THAT A BUFFER POOL EXISTED FOR THIS DATASET AND MADE THE APPROPIATE TEST SHOWN BELOW WITH UNSATISFACTORY RESULTS:
– IF THE DATA WAS TO BE SENT DIRECTLY TO A UNIT RECORD DEVICE (NO SPOOLING), THE BUFFER LENGTH VALUE IN THE BUFFER CONTROL BLOCK HAD TO BE EQUAL TO OR GREATER THAN THE VALUE SPECIFIED IN THE DCB FOR LOGICAL RECORD LENGTH (LRECL).
– OTHERWISE, THE BUFFER LENGTH VALUE IN THE BUFFER CONTROL BLOCK HAD TO BE EQUAL TO OR GREATER THAN THE VALUE SPECIFIED IN THE DCB FOR BLKSIZE.

S013 – 50 – AN OPEN MACRO ISSUED FOR A DATASET ALLOCATED TO A PRINTER DID NOT HAVE OUTPUT SPECIFIED AS AN OPEN OPTION.

S013 – 54 – NO SECONDARY CONTROL UNIT COULD NOT BE FOUND FOR A 1419.

S013 – 58 – AN OPEN MACRO WAS ISSUED FOR A PAPER TAPE DATASET AND CONCATENATION WITH UNLIKE ATTRIBUTES WAS SPECIFIED.

S013 – 5C – AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE. THE DATASET CONTAINED SPANNED VARIABLE LENGTH RECORDS LARGER THAN 32,756 BUT GET LOCATE MODE WAS NOT USED.
ALTERNATIVELY, BFTEK=A WAS SPECIFIED WITH MACRF=GM OR MACRF=PM.

S013 – 60 – AN OPEN MACRO WAS ISSUED FOR A DATASET WITH A DCB SPECIFYING RECFM=F, AND BLKSIZE WAS NOT EQUAL TO LRECL. CORRECT THE RECFM TO FB, OR MAKE LRECL AND BLKSIZE EQUAL.

S013 – 64 – AN OPEN MACRO WAS ISSUED FOR A NULL DATASET USING AN ACCESS METHOD OTHER THAN QSAM OR BSAM. THIS IS A NO-NO.
S013 – 68 – AN OPEN WAS ISSUED FOR A DATASET WHOSE DCB SPECIFIED BLKSIZE GREATER THAN 32,767, WHICH IS THE MAXIMUM ALLOWED.

S013 – 6C – AN OPEN MACRO WAS ISSUED FOR A DATASET WITH RECFM=T IN THE DCB, REQUESTING TRACK OVERFLOW, BUT THE DIRECT ACCESS DEVICE DOES NOT SUPPORT TRACK OVERFLOW.

S013 – 70 – AN OPEN MACRO WAS ISSUED FOR A DATASET ON MAGNETIC TAPE. A CONFLICT EXISTS AMONG LABEL PARAMETERS ON THE DD STATEMENT, AND DCBRECFM, DCBOPTCD, DCBBUFOF, AND DCBUSASI GIVE THE APPEARANCE
OF MIXED USASI AND EBCDIC ATTRIBUTES TO THE DATASET; OR OPTCD=Q WAS SPECIFIED FOR A DATASET ON A DEVICE OTHER THAN MAGNETIC TAPE.

S013 – 74 – AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET, BUT THE OPEN OPTION DID NOT SPECIFY INPUT.

S013 – 78 – AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET. THE BUFL PARAMETER IN THE DCB WAS SPECIFIED AS ZERO.

S013 – 7C – AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET, BUT THE LRECL PARAMETER IN THE DCB WAS ZERO.

S013 – 80 – AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET, BUT THE BUFL WAS LESS THAN THE LRECL.

S013 – 84 – AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET. THE NUMBER OF BUFFERS SPECIFIED IN THE BUFFER POOL CONTROL BLOCK IS NOT THE SAME AS THAT SPECIFIED IN THE DCBBUFNO.

S013 – 88 – AN OPEN MACRO WAS ISSUED FOR A TELECOMMUNICATIONS DEVICE BUT THE DCBDSORG DID NOT SPECIFY TSO.

S013 – 8C – AN OPEN MACRO WAS ISSUED FOR A DIRECT ORGANIZATION DATASET (BDAM) BUT THE DCBRECFM PARAMETER WAS NOT SPECIFIED.

S013 – A4 – A DCB WAS OPENED FOR A SYSIN OR SYSOUT DATASET BUT THE DSORG WAS NOT SPECIFIED AS PS.

S013 – A8 – AN INVALID RECORD FORMAT WAS REQUESTED FOR A SYSIN OR SYSOUT DATASET. (RECFM=D, VS, OR VBS ARE INVALID FOR SYSIN)

S013 – AC – A QSAM OPEN WAS ISSUED WITH A NON-ZERO KEYLENGTH IN THE DCB WHICH IS NOT SUPPORTED. (NOW SUPPORTED, BUT WITH INPUT ONLY.)

S013 – B0 – AN OPEN MACRO WAS ISSUED WITH THE RDBACK OPTION FOR A DCB SPECIFYING A RECORD FORMAT OF VARIABLE SPANNED RECORDS. THESE ARE CONFLICTING PARAMETERS.

S013 – B4 – AN OPEN MACRO WAS ISSUED WITH THE INOUT/OUTIN OPTION FOR A DCB SPECIFYING THE QSAM MACRF VALUES; THESE ARE CONFLICTING PARAMETERS.

S013 – B8 – AN OPEN MACRO WAS ISSUED FOR THE 3890 DOCUMENT PROCESSOR AND DCBHDR WAS NOT SPECIFIED IN THE DCB.

S013 – BC – A SYSIN OR SYSOUT DCB WAS OPENED WITH INVALID OPTIONS. EITHER OPEN SPECIFIED UPDAT OR RDBACK, OR THE POINT MACRO FUNCTION WAS SPECIFIED IN MACRF=RP OR WP. REPOSITIONING OR UPDATING A SPOOLED DATASET IS NOT PERMITTED.

S013 – C0 – A SYSIN OR SYSOUT DATASET COULD NOT BE OPENED BY A JOB ENTRY SUBSYSTEM. THE FAILING DCB IS NOT OPENED, HOWEVER THE TASK IS NOT TERMINATED. PROCESSING CONTINUES FOR OTHER DCBS OPENED.

S013 – C4– DURING THE CREATION OF A DIRECT DATASET, THE OPEN ROUTINE FOUND THAT THE DCB SPECIFIED READ(R) OR GET(G) IN THE MACRF FIELD. ONLY WRITE LOAD (WL) IS ALLOWED.

S013 – C8 – THE OPE
N SUBSYSTEM EXECUTOR MODULE WAS PASSED AN ERROR RETURN CODE IN REGISTER 15 AFTER ISSUING THE IEFSSREQ MACRO TO CONNECT THE USER’S ACB TO THE SUBSYSTEM. THIS INDICATES THE SUBSYSTEM WAS NOT OPERATING.

S013 – CC – SETPRT PROCESSING FAILED TO SET UP THE DEVICE DURING AN OPEN FOR THE IBM 3800 PRINTING SUBSYSTEM.

S013 – D0 – AN INVALID RECORD FORMAT OF FBS OR FS WAS SPECIFIED FOR A PARTITIONED DATA SET.

S013 – D0 – A DB/DBS RECORD FORMAT WAS SPECIFIED FOR QSAM LOCATE MODE, BUT THE LOGICAL RECORD INTERFACE IS NOT PRESENT IN THE ASSOCIATED BUFFER CONTROL BLOCK; IE. SEGMENT MODE IS IMPLIED.

S013 – D8 – A CONFLICT HAS OCCURRED FOR THE SPANNED RECORD FORMAT EXTENDED LOGICAL RECORD INTERFACE (XLRI). BUFFER CONTROL BLOCK; IE. SEGMENT MODE IS IMPLIED.

S013 – E4 – THE LIMIT OF 123 EXTENTS FOR A CONCATENATED PARTITIONED DATA SET HAS BEEN EXCEEDED. (USED TO BE 256 EXTENTS?)

S013 – E8 – THE OPEN VERIFICATION FUNCTION OF THE IEFSSREQ MACRO RETURNED AN ERROR CODE IN REGISTER 15.

S014 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S014)
– THE TASK WHICH ISSUED A CLOSE FOR A DASD DATA SET WAS NOT THE TASK WHICH OPENED THE DATA SET.

S016 – AN ERROR OCCURRED IN SAM SIO/PAGE FIX OR DASD END-OF-BLOCK MODULES BECAUSE OF ONE OF THE FOLLOWING:
– THE DASD END-OF-BLOCK MODULES ISSUED AN EXCPVR SVC REQUEST ON BEHALF OF A USER REQUEST, BUT A PREVIOUS EXCPVR SVC REQUEST HAD NOT COMPLETED. ONE OF THE FOLLOWINF OCCURRED:
– A DATA EXTENT CONTROL BLOCK (DECB) WAS USED TWICE.
– MULTIPLE READS OR WRITES WERE ISSUED, BUT ONLY THE LAST READ OR WRITE WAS CHECKED.
– AN EXCPVR SVC REQUEST ON BEHALF OF A USER REQUEST WAS GOING TO BE ISSUED TO READ A DATA SET THAT IS EXECUTE ACCESS PROTECTED, BUT THE USER IS NOT IN SUPERVISOR STATE. (THE SAM SIO APPENDAGE ISSUED THIS ABEND.)

S020 – DURING AN OPEN FOR A BDAM DATA SET THE CONTROL PROGRAM FOUND THAT DCBMACRF DID NOT CONTAIN AN A, K OR I (RC=04), OR THE BDAM DATA SET CONTAINED ZERO EXTENTS (RC=08).

S021 – A CALLER OF THE ASCBCHAP ROUTINE PASSED TO ASCBCHAP AN ASCB ADDRESS THAT HAD BITS SET TO ONE IN ITS HIGH ORDER BYTE.

S022 – THE VPSS ENCOUNTERED A MISSING DEVICE END ON CONTROL PORT 0.

S023 – LNKLST LOOKASIDE (LLA) COULD NOT OBTAIN ALL THE LNKLST DIRECTORY ENTRIES.

S024 – AN ABNORMAL TERMINATION OCCURRED IN PRINT SERVICES FACILITY.

S027 – AN ABNORMAL TERMINATION OCCURRED IN PRINT SERVICES FACILITY.

S028 – A PAGING OPERATION HAS NOT COMPLETED SUCCESSFULLY DUE TO ONE OF THE FOLLOWING:

– A PERMANENT I/O ERROR OCCURRED WHILE ATTEMPTING A PAGE-IN OR SWAP-IN OPERATION. THE DATA BEING PAGED IN OR SWAPPED IN IS LOST.
– A REAL STORAGE MANAGEMENT ROUTINE OR ANOTHER SYSTEM ROUTINE PERFORMING A SERVICE FOR RSM SUFFERED AN INTERMEDIATE ERROR. THE FUNCTION PERFORMED IS TERMINATED.
– A AUXILIARY STORAGE MANAGEMENT ROUTINE SUFFERED A TRANSLATION ERROR WHILE USING THE CONTROL REGISTER OF ANOTHER ADDRESS SPACE TO UPDATE THAT ADDRESS SPACE’S LSQA.

S029 – LINES EXCEEDED

S02A – JES2 FOUND THAT DATA MANAGEMENT CONTROL BLOCKS OR THE JES2 UBUF CONTROL BLOCK WAS NO LONGER VALID DURING EXECUTION OF A DATA MANAGEMENT REQUEST FOR A SPOOL DATA SET.

S02B – A USER EXIT ROUTINE ISSUED A RETURN CODE GREATER THAN THAT SPECIFIED IN THE &MAXRC PARAMETER OF THE $EXIT### MACRO.

S02C – AN ERROR OCCURRED IN JES2 SUPPORT OF AN FSS ADDRESS SPACE.

S02D – THE JES2 MAIN TASK WAS ABENDED BY THE OPERATOR OR A CATASTROPHIC ERROR.

S030 – DURING A BISAM OR QISAM OPEN DCBMACRF DID NOT INDICATE A VALID MODE OF OPERATION.

S031 – SPACE REQUESTED NOT AVAILABLE, DECREASE THE SPACE ALLOCATION

S032 – DURING A BISAM OR QISAM OPEN DCBMACRF WAS NOT VALID FOR ISAM.

S03B – ISAM DATASET TO BE PROCESSED, BUT NOT CREATED OR ITS DCB NOT CLOSED AFTER CREATION.

POSSIBLE CAUSE

– DATASET WAS TO BE WRITTEN ON BUT WAS OPENED AS INPUT
– LRECL/BLKSIZE PROBLEM EXISTS – INVALID VALUES OR NOT MULTIPLES

S03D – THE ERROR OCCURRED DURING THE EXECUTION OF A QISAM OR BISAM OR BDAM MACRO INSTRUCTION.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S03D OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S03D-RC)

S03D – 04 – AN OPEN MACRO WAS ISSUED FOR AN INDEXED SEQUENTIAL OR DIRECT DATASET. THE VOLUME SERIAL NUMBERS ON THE DD STATEMENT WERE NOT SPECIFIED IN THE SAME ORDER THAT THE DATASET WAS CREATED.

S03D – 08 – AN OPEN MACRO WAS ISSUED FOR AN INDEXED SEQUENTIAL DATASET. THE FIRST VOLUME OF THE DATASET DOE NOT HAVE A FORMAT2 DSCB.

S03D – 0C – AN OPEN MACRO WAS ISSUED FOR A DIRECT DATASET. THE DATASET HAS AN INDEXED SEQUENTIAL ORGANIZATION.

S046 – SORT CAPACITY EXCEEDED

S047 – AN UNAUTHORIZED PROGRAM REQUESTED A RESTRICTED SVC.

S04B – AN INVALID OPERATION CODE WAS PASSED TO A TSO LINKAGE ASSIST ROUTINE (LAR).

S04B – 04 – THE LAR (IKJEFTSL) FOR THE TERMINAL MONITOR PROGRAM (TMP) RECEIVED AN INVALID FUNCTION NUMBER.

S04B – 08 – THE SERVICE ROUTINE’S LAR (IKJTSLAR) WAS INVOKED AT IKJTSLAR, WHICH IS AN INVALID SERVICE ROUTINE ENTRY POINT.

S04C – THE TERMINAL MONITOR PROGRAM (TMP) WAS INVOKED AT ENTRY POINT IKJEFT1A AND THE TMP DETACHED A PROGRAM THAT COMPLETED WITH A NON-ZERO COMPLETION CODE (WHICH IS IN REGISTER 15).

S04E – INTERNAL IBM DATABASE 2 (DB2) ERROR.

S04F – DB2 ABNORMAL TERMINATION TO AVOID DATA INTEGRITY PROBLEMS.

S052 – A PROGRAM MADE AN INVALID PC/AUTH REQUEST. CHECK THE CODE IN REGISTER 15.

S053 – A PROGRAM MADE A PC/AUTH REQUEST BUT AN ERROR PREVENTED NORMAL COMPLETION. CHECK THE CODE IN REGISTER 15.

S061 – I/O ERROR IN SORT EXEC, CHECK FOR DATA MESSAGES

S063 – SORTIN DATA PROBLEM

S064 – AN ADDRESS SPACE THAT HOLDS A CROSS MEMORY LOCAL LOCK (CML LOCK) TERMINATED ABNORMALLY BEFORE IT FREED THE LOCK.

S66D – LIBRARY ACCESS PROBLEM. LOOKS THE SAME AS A S106 ABEND. (LLA)

S071 – THE OPERATOR PRESSED THE RESTART KEY TO ACTIVATE THE SYSTEM’S RECOVERY AND TERMINATION PROCESS. THE PROGRAM RUNNING AT THE TIME THE OPERATOR PRESSED THE RESTART BUTTON WAS SENT THROUGH
ABEND PROCESSING BECAUSE THE OPERATOR DETERMINED IT WAS IN A NONCANCELABLE LOOP OR WAIT STATE.

S078 – RCT (REGION CONTROL TASK) PROCESSING HAS RECEIVED AN UNACCEPTABLE RETURN CODE FROM AN INVOKED ROUTINE AND CANNOT CONTINUE PROCESSING. RCT RECOVERY RECORDS THE ERROR IN SYS1.LOGREC, PERFORMS RESOURCE CLEAN-UP, REQUESTS A SYS1.DUMP OF THE ADDRESS SPACE AND THEN REQUESTS ADDRESS TERMINATION.

S079 – RCT (REGION CONTROL TASK) ATTENTION EXIT PROCESSING HAS RECEIVED AN UNACCEPTABLE RETURN CODE FROM AN INVOKED ROUTINE AND CANNOT CONTINUE PROCESSING. RCT RECOVERY RECORDS THE ERROR IN
SYS1.LOGREC, PERFORMS RESOURCE CLEAN-UP, REQUESTS A SYS1.DUMP OF THE ADDRESS SPACE AND THEN REQUESTS ADDRESS TERMINATION.

S07C – SUPERVISOR CONTROL RECOVERY HAS DETECTED AN ERROR WHICH REQUIRES THAT THE CURRENT TASK BE TERMINATED OR THAT THE CURRENT ADDRESS SPACE BE TERMINATED.

S07F – DURING RECOVERY, VERIFICATION OF THE TCB QUEUE ASSOCIATED WITH THE TERMINATED ADDRESS SPACE RESULTED IN AN EMPTY TCB QUEUE.

S0A7 – DURING Z NET,CANCEL COMMAND PROCESSING, VTAM FOUND THAT A USER HAD NOT SPECIFIED A TPEND EXIT ROUTINE, OR VTAM COULD NOT SCHEDULE A USER’S TPEXIT ROUTINE.

S0A8 – VTAM DETECTED AN ERROR DURING EXECUTION OF AN APPLICATION PROGRAM. THE TWO LOW-ORDER BYTES OF REGISTER 15 CONTAIN A HEXADECIMAL REASON CODE.
– 2101 – A VTAM VALIDITY CHECK OF THE USER’S RPL FAILED BECAUSE THE RPL DOES NOT HAVE THE SAM PROTECTION KEY AS THE APPLICATION PROGRAM’S TCB.
– 7001 – THE USER’S RPL OR ECB IS INVALID.

S0A9 – EITHER A HALT NET,CANCEL COMMAND WAS ENTERED OR AN ERROR OCCURRED DURING EXECUTION OF A VTAM MODULE. THE TWO LOW-ORDER BYTES OF REGISTER-15 CONTAIN A HEXIDECIMAL REASON CODE.
– 0000 – A HALT NET,CANCEL COMMAND HAS BEEN PROCESSED.
– 10F1 – THE ACF/V
TAM STAE RETRY ROUTINE ISSUED AN ABEND 0A9 IN ORDER TO GIVE CONTROL TO THE USER RECOVERY ROUTINE (STAE EXIT ROUTINE).
– 3100 – THERE ARE NOT ENOUGH I/O BUFFERS TO SATISFY A VTAM STORAGE REQUEST.
– 3111 – A VTAM MODULE FINISHED PROCESSING BEFORE IT RELEASED A LOCK.
– 3141 – A VTAM DESTINATION VECTOR TABLE (DVT) ENTRY IS INVALID FOR THE DEFINED ATTACHMENT.
– 7002 – A VTAM REQUEST FOR STORAGE FAILED
– 7003 – A VTAM REQUEST TO RELEASE STORAGE FAILED BECAUSE THE STORAGE HAD ALREADY BEEN RELEASED.
– 7004 – VTAM COULD NOT OBTAIN A LOCAL MEMORY LOCK.
– 7009 – VTAM WAS UNABLE TO RESTORE ITS REGISTERS AFTER A USER EXIT ROUTINE RETURNED CONTROL TO VTAM.
– 7071 – A RELSTORE WAS ISSUED FOR A PREVIOSLY FREED BUFFER.
– 7141 – CONTROL CANNOT BE PASSED TO THE PROPER VTAM MODULE. EITHER A VTAM DESTINATION VECTOR TABLE ENTRY IS INVALID FOR THE DEFINED ATTACHMENT OR VTAM STOARGE HAS BEEN ALTERED.

S0AA – AN ABEND CONDITION OCCURRED DURING EXECUTION OF VTAM. THE ERROR COULD NOT BE ASSOCIATED WITH ANY PARTICULAR TCB. ALL TASKS IN THE ADDRESS SPACE ARE ABNORMALLY TERMINATED.

S0AE – IOS SUPPORT OF SYSTEM RESTART PROCESSING FOUND THAT THE I/O PURGE MODULE (IGC0001F) WAITING FOR THE COMPLETION OF AN I/O REQUEST. THE SYSTEM ABNORMALLY TERMINATES ALL TASKS IN THE ADDRESS SPACE, THEN THE SYSTEM TERMINATES THE ADDRESS SPACE.

S0B0 – AN UNCORRECTABLE ERROR WAS DETECTED BY THE SWA MANAGER. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S0B0-RC)

S0B0 – 04 – INVALID FUNCTION REQUESTED.

S0B0 – 08 – INVALID SVA (DOES NOT POINT TO THE BEGINNING OF A SWA PREFIX OR THE SWA PREFIX HAS BEEN DESTROYED).

S0B0 – 0C – ATTEMPTING TO READ A BLOCK NOT YET WRITTEN.

S0B0 – 10 – INVALID LENGTH (0 OR NEGATIVE FOR ASSIGN LOCATE OR ATTEMPTING TO READ OR WRITE A RECORD, WHICH IS NOT 176 BYTES, IN MOVE MODE).

S0B0 – 14 – INVALID COUNT FIELD (0 FOR READ, WRITE, ASSIGN OR 00 FOR WRITE AND ASSIGN).

S0B0 – 18 – QMNGRIO MACRO WAS ISSUED WITH BOTH OR NEITHER OF THE READ AND WRITE BITS SET.

S0B0 – 1C – INVALID ID (THE CALLER ATTEMPTED TO WRITE A BLOCK FOR THE FIRST TIME AND HAS EITHER PASSED A NON-EXISTING ID OR HAS FAILED TO PASS ONE AND THE BLOCK DOES NOT HAVE AN IMBEDDED ID).

S0B0 – 20 – INVALID BLOCK POINTER (WRITE LOCATE IS ATTEMPTING TO WRITE AND IS PASSING A BLOCK POINTER WHICH IS NOT VALID FOR THE SVA REQUESTED).

S0C1 – OPERATION EXCEPTION – AN OPERATION CODE IS NOT ON THE MACHINE
POSSIBLE CAUSE
– SUBSCRIPT ERROR
– CLOBBERED CODE TRIED TO READ A FILE THAT WAS NOT OPEN
– MISSPELLED DDNAME
– ERROR IN PARAMETERS PASSED TO SUBROUTINES
– MISSING DD CARD
– RECORDING MODE WAS WRONG, OR DENSITY WAS INCORRECT
– BAD LOAD MODULE, POSSIBLE BAD OBJECT DECK OR MISSING SUBROUTINE
– FORTRAN – MISSING DIMENSION STATEMENT, SAME NAME FOR ARRAY AND A SUBROUTINE
– COBOL – SUBROUTINE PROG ID WAS THE SAME AS THE ENTRY NAME
– COBOL – TRIED TO CALL WITHIN COBOL F SORT INPUT/OUTPUT PROCEDURE
– COBOL – TRIED TO CALL A SUBROUTINE WHICH COULD NOT BE FOUND
– COBOL – INCOMPLETE DCB FOR SORTIN
– COBOL – USING SORT VERB, DDNAME WAS NOT SORTOUT WHEN THE GIVING OPTION WAS USED.
– COBOL – EXECUTING SORT-USING AFTER OPENING SORTIN

S0C2 – PRIVILEGED OPERATION EXCEPTION
POSSIBLE CAUSE
– UNINTENTIONAL BRANCH TO INVALID INSTRUCTION DUE TO SUBSCRIPT ERROR
– COBOL – MISSING PERIOD AT END OF PARAGRAPH OR PARAGRAPH NAMES
– MISSING GOBACK AFTER SORT VERB – LOGIC FELL INTO INPUT PROCEDURE
– ACCEPT VERB EXECUTED WHEN NO SYSIN DD WAS AVAILABLE.

S0C3 – EXECUTION EXCEPTION – THE SUBJECT INSTRUCTION OF EXECUTE IS ANOTHER EXECUTE.
POSSIBLE CAUSE
– UNINTENTIONAL BRANCH, LOSS OF ADDRESSABILITY.

S0C4 – PROTECTION EXCEPTION – A VIRTUAL ADDRESS COULD NOT BE TRANSLATED INTO A REAL ADDRESS.
POSSIBLE CAUSE
– ENTRY NOT FOUND
– INVALID ADDRESS WAS REFERENCED DUE TO SUBSCRIPT ERROR OR BAD PARMS
– THE KEY OF AN INSTRUCTION OR AN OPERAND IN STORAGE DOES NOT
– MATCH THE PROTECTION KEY IN THE PSW (INTERRUPT CODE 4)
– THE VIRTUAL SEGMENT OR PAGE WAS NEVER ALLOCATED (INTERRUPT CODE 10 OR 11, RESPECTIVELY)
– THE PAGE WAS PAGED OUT AND THE ROUTINE REQUESTING THE CODE WAS DISABLED FOR I/O INTERRUPTS (INTERRUPT CODE 11)
– COBOL – IN GROUP MOVE, RECEIVING RECORD VARIABLE LENGTH DEFINED WRONG
– TRIED MOVING VAR. LENGTH REC. LARGER THAN TARGET FIELD MAX
– TRIED TO READ OR WRITE A FILE WHICH WAS NOT OPEN
– USED DD DUMMY AND LOGIC SAYS AT END MOVE HIGH VALUES TO FD
– TRIED TO CALL WITHIN COBOL F SORT INPUT/OUTPUT PROCEDURE
– U WITH SORT – TRIED TO GOBACK IN THE OUTPUT PROCEDURE

S0C5 – ADDRESSING EXCEPTION – AN ADDRESS BEYOND THE AVAILABLE REAL STORAGE WAS REQUETED
POSSIBLE CAUSE
– SEE S0C1 FOR MORE INFORMATION
– SUBSCRIPT ERROR – REFERENCED BEYOND TABLE IN PROGRAM RUNNING V=R
– COBOL – PERFORMED PROCEDURE NOT EXITED PROPERLY
– RECORD DESCRIBED TOO SHORT
– REFERENCED A RECORD WITHOUT GIVING A READ
– TRIED TO USE WRITE WITHOUT FROM OPTION ON APPLY WRITE ONLY FILE

S0C6 – SPECIFICATION EXCEPTION – AN INCORRECT BOUNDARY WAS SPECIFIED. USUALLY CAUSED BY UNINTENTIONAL BRANCH TO INVALID INSTRUCTION.

S0C7 – DATA EXCEPTION – DECIMAL DATA IS INCORRECT OR IMPROPERLY OVERLAPPED OR NOT VALIDLY INITIALIZED.
POSSIBLE CAUSE
– SUBSCRIPT ERROR, REFERENCED BEYOND TABLE
– COBOL – WORKING STORAGE NOT INITIALIZED
– BAD DATA, SHOULD CHECK DATA FOR ERRORS
– GARBAGE IN A FIELD BEING TESTED OR DISPLAYED
– MOVE ZEROES TO GROUP LEVEL IS DISPLAY, HAD SUBLEVELS THAT WERE NOT
– PERIOD MISSING AFTER IMPERATIVE STATEMENTS WITHIN AT END CLAUSE
– BINARY FIELD IN AN ARITHMETIC OPERATION IS NOT LARGE ENOUGH TO ACCEPT RESULT (FOR MORE INFORMATION, SEE DESCRIPTION OF S0C1)

S0C8 – FIXED POINT OVERFLOW EXCEPTION NOTE – MASKED BY FORTRAN

S0C9 – FIXED POINT DIVIDE EXCEPTION NOTE – MASKED BY FORTRAN

S0CA – DECIMAL OVERFLOW EXCEPTION THE DESTINATION FIELD IS TOO SMALL TO CONTAIN THE RESULT FIELD
IN A DECIMAL OPERATION.

S0CB – DECIMAL DIVIDE EXCEPTION A QUOTIENT EXCEEDS THE SPECIFIED DATA FIELD SIZE.

S0CC – EXPONENT OVERFLOW EXCEPTION A FLOATING POINT NUMBER EXCEEDS THE MAXIMUM SIZE.
NOTE – THIS ERROR IS DETECTED AND FIXED IN FORTRAN

S0CD – EXPONENT UNDERFLOW EXCEPTION A FLOATING POINT NUMBER IS SMALLER THAN THE MINIMUM.
NOTE – FORTRAN WILL SET THE RESULT TO ZERO AND CONTINUE PROCESSING

S0CE – SIGNIFICANCE EXCEPTION A FLOATING POINT ADDITION OR SUBTRACTION RESULTS IN AN ALL ZERO
FRACTION
NOTE – THIS IS MASKED IN FORTRAN

S0CF – FLOATING POINT DIVIDE EXCEPTION – DIVIDE BY ZERO
NOTE – THIS ERROR IS DETECTED AND NOTED BY FORTRAN

S0D2 – A PROGRAM CHECK WAS DETECTED; AN INTERRUPTION CODE OF 18 X’12’ (TRANSLATION SPECIFICATION EXCEPTION) HAS OCCURRED. THERE IS INVALID DATA IN EITHER CONTROL REGISTERS ZERO OR ONE, OR A SEGMENT OR PAGE TABLE. THE ERROR IS THE RESULT OF A HARDWARE ERROR OR A PROGRAM RUNNING IN KEY ZERO HAS CAUSED DATA DAMAGE.

S0D3 – A PROGRAM CHECK, INTERRUPTION CODE 19 X’13’ (SPECIAL OPERATION ERROR) HAS OCCURRED. A PRIVILEGED PROGRAM ISSUED A SET SYSTEM MASK. THIS INSTRUCTION IS NOT VALID IN OS/VS2 (SINCE RELEASE 2).

S0D9 – A PROGRAM CHECK, INTERRUPTION CODE 38 (PAGE FAULT ASSIST ERROR) HAS OCCURRED. EITHER A HARDWARE ERROR OCCURRED OR A PROGRAM RUNNING IN KEY ZERO CAUSED DATA DAMAGE.

S0E0 – AN INVALID OR UNRECOGNIZED PROGRAM INTERRRUPT OCCURRED.
POSSIBLE CAUSE
– THIS LEVEL OF MVS IS NOT THE CORRECT ONE FOR THE HARDWARE, ESPECIALLY IF THE INTERRUPT CODE IS UNKNOWN.

S0E0 – 1D – A SQUARE ROOT EXECEPTION OCCURED.

S0E0 – 1E – AN UNNORMALIZED OPERAND EXECEPTION OCCURED.

S0E0 – 28 – RESERVED BIT POSITIONS IN AN ALET WERE NON-ZERO.

S0E0 – 29 – AN ALET SPECIFIED AN INVALID ACCESS LIST ENTRY.

S0E0 – 2A – AN ALET SPECIFIED A PREVI
OUSLY DELETED ACCESS LIST ENTRY.

S0E0 – 2B – AN ACCESS LIST ENTRY SPECIFIED AN INVALID DATA SPACE.

S0E0 – 2C – THE SEQUENCE NUMBER IN THE ASTE THAT THE ACCESS LIST ENTRY REFERS TO IS NOT EQUAL TO THE NUMBER IN THE ACCESS LIST ENTRY.

S0E0 – 2D – A PRIVATE ACCESS LIST ENTRY IS SPECIFIED, AND THE CURRENT EAX IS NOT AUTHORIZED TO THE TARGET ADDRESS SPACE.

S0E0 – 30 – A STACKING INTRUCTION WAS ISSUED WHEN THE LINKAGE STACK WAS FULL.

S0E0 – 31 – AN UNSTACKING INTRUCTION WAS ISSUED WHEN THE LINKAGE STACK HAS NO STACK ENTRIES.

S0E0 – 32 – A LINKAGE STACK SPECIFICATION INTERRUPT OCCURED.

S0E0 – 33 – AN INVALID LINKAGE STACK ENTRY (LSE) TYPE WAS ENCOUNTERED BY THE HARDWARE OR BY AN UNSTACKING OPERATION.

S0E0 – 34 – A PR INSTRUCTION WAS ISSUED AGAINST A LINKAGE STACK ENTRY THAT HAS THE UNSTACK SUPPRESSION BIT SET. MVS SETS THIS BIT IN A LINKAGE STACK ENTRY TO PREVENT SVC ROUTINES FROM UNSTACKING
ENTRIES THEY DID NOT ADD TO THE STACK.

S0E1 – THE ERROR OCCURRED WHILE PROCESSING THE FIRST EXCP OF A VIO DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.

S0E2 – THE ERROR OCCURRED WHILE PROCESSING THE FIRST EXCP OF A VIO DATASET. THE SYSTEM WAS UNABLE TO ASSIGN, LOCATE, FIX, FREE, OR ACCESS VIO PAGES FOR THE DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.

S0E3 – THE ERROR OCCURRED WHILE PROCESSING A VIO DATASET. THE SYSTEM WAS UNABLE TO ASSIGN, LOCATE, FIX, FREE, OR ACCESS VIO PAGES FOR THE DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.

S0E4 – THE ERROR OCCURRED WHILE TRYING TO SCRATCH A VIO DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.

S0E5 – UNABLE TO DISCONNECT THE VIRTUAL TRACK BUFFER FORM THE VIO DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.

S0E6 – UNABLE TO PROCESS A DATA SET THAT HAS ALREADY BEEN SCRATCHED.

S0F0 – AN ERROR OCCURRED WHILE PROCESSING A MACHINE CHECK INTERRUPTION. IN AN ATTEMPT TO RECOVER THE SYSTEM THE INTERRUPTED TASK WAS TERMINATED.

S0F1 – PROGRAM INTERRUPTION IN I/O INTERRUPTION HANDLER RECORD DESCRIBED AS WRONG LENGTH

S0F2 – I/O INTERRUPT PROCESSING ERROR. I/O RECOVERY ROUTINE FAILED. CLOBBERED IOB OR OTHER SVC PARAMETERS – SEE S0C1

S0F3 – MACHINE CHECK INTERRUPTION DISK I/O FAILURE OR MACHINE TROUBLE

S0F8 – THE ISSUER OF AN SVC WAS EITHER IN SRB MODE, HELD A LOCK, WAS DISABLED, OR WAS IN CROSS MEMORY MODE.

S0F8 – 04 – THE SVC ISSUER WAS NOT IN TCB MODE.

S0F8 – 08 – THE SVC ISSUER HELD A LOCK.

S0F8 – 0C – THE SVC ISSUER WAS DISABLED.

S0F8 – 10 – THE SVC ISSUER WAS IN CROSS MEMORY MODE.

S0F8 – 14 – THE SVC ISSUER HAD AN ENABLED UNLOCKED TASK MODE FRR. IE. EUT=YES WAS SPECIFIED ON THE SETFRR MACRO.

S0F8 – 18 – THE SVC ISSUER WAS IN AR ADDRESS SPACE CONTROL MODE FOR AN SVC WHICH DOES NOT ALLOW THIS.

S0F8 – 1C – THE SVC ISSUER WAS NOT AUTHORIZED FOR SVC MICROCODE ASSIST.

S0F9 – THE ERROR OCCURRED WHILE TRYING TO ACQUIRE OR RELEASE AN SVRB.

S0F9 – 00– LSQA HAS BEEN EXHAUSTED AND AN SVRB CANNOT BE CREATED TO HONOUR AN SVC REQUEST IN THE ADDRESS SPACE.

S0F9 – 04 – AN SVRB BEING FREED MAY NOT BELONG TO THE SVRB POOL.

S0FB – A TRANSLATION EXCEPTION HAS OCCURRED. INVALID CONTENTS WERE DETECTED IN CONTROL REGISTER 0.

S0FC – A TRANSLATION ERROR OCCURRED WHILE REFERENCING DATA NOT IN THE HOME ADDRESS SPACE. BAD DAT TABLES OR WRONG STO ADDRESS.

S0FD – A TYPE 6 SVC REQUESTED THE SVC FIRST LEVEL INTERRUPT HANDLER (FLIH) TO SCHEDULE A CROSS MEMORY SRB. T6EXIT MACRO POINTS TO SRB WHERE SRBASCB IS NOT HOME ASCB.

S0FE – AN ERROR WAS DETECTED WHILE RMF WAS SAMPLING DATA ABOUT THE STATE OF THE SYSTEM.

S100 – I/O INTERBLOCK GAP DETECTED WHEN WRITING RECORD

S101 – DURING EXECUTION OF A WAIT MACRO, THE PROBLEM PROGRAM SPECIFIED MORE EVENTS THAN THERE WERE ECBS.

S102 – THE ERROR OCCURRED DURING EXECUTION OF A POST MACRO INSTRUCTION. THE CONTROL PROGRAM FOUND AN INVALID EVENT CONTROL BLOCK ADDRESS, OR THE ECB WAS IN A STORAGE AREA WITH A PROTECTION KEY DIFFERENT FROM THAT OF THE TASK ISSUING THE MACRO.

S102 – 00 – INVALID ECB FOR POST IN THE USER’S KEY.

S102 – 04 – INVALID ECB FOR AN XMPOST (CROSS MEMORY POST).

S102 – 08 – INVALID ECB FOR BRANCH ENTRY POST IN THE USER’S KEY.

S102 – 0C – INVALID ECB FOR BRANCH ENTRY XMPOST.

S104 – GETMAIN ERROR. AN AUTHORIZED PROGRAM REQUESTED VIRTUAL STORAGE THAT REQUIRES MORE REAL STORAGE THAN IS AVAILABLE.

S104 – 04 – NOT ENOUGH REAL STORAGE FOR SPACE IN SQA SUBPOOL.

S104 – 08 – NOT ENOUGH REAL STORAGE FOR SPACE IN FIXED CSA SUBPOOL.

S104 – 0C – NOT ENOUGH REAL STORAGE FOR SPACE IN LSQA SUBPOOL.

S104 – 1C – LSQA REQUEST FAILED – PAGE TABLE PAGED OUT.

S104 – 20 – AUTHORIZED PRIVATE REQUEST FAILED – PAGE TABLE PAGED OUT.

S106 – CAN’T FIND IBM SUBTOUTINE. RECOMPILE AND RERUN. AN ERROR WAS DETECTED BY THE CONTROL PROGRAM WHEN IT ATTEMPTED TO FETCH THE REQUESTED PROGRAM INTO VIRTUAL STORAGE.
POSSIBLE CAUSE
– PREVIOUS LKED STEP FAILED TO OUTPUT A SYSLMOD, NEEDS LARGER SIZE= I/O ERROR – MACHINE TROUBLE OR DISK FAILURE

S106-D – INVALID RECORD TYPE IN LOAD MODULE

S106 – 0E – THE CONTROL PROGRAM FOUND AN INVALID ADDRESS IN THE LOAD MODULE. CHECK REGISTER 0:
– 20 – ERROR CONVERTING TTR.
– 24 – BLOCK IS OUTSIDE OF THE MODULE.
– 28 – AN ADCON LOCATION IS INVALID.

S106-F – UNCORRECTABLE I/O ERROR WHEN LOADING MODULE.

S106 – 10 – THE CONTROL PROGRAM DETECTED A RELOCATION ERROR IN THE LOAD MODULE.

S10A – GETMAIN ERROR. A PROGRAM REQUESTED VIRTUAL STORAGE THAT REQUIRES MORE REAL STORAGE THAN IS AVAILABLE.

S10A – 04 – NOT ENOUGH REAL STORAGE FOR SPACE IN SQA SUBPOOL.

S10A – 08 – NOT ENOUGH REAL STORAGE FOR SPACE IN FIXED CSA SUBPOOL.

S10A – 0C – NOT ENOUGH REAL STORAGE FOR SPACE IN LSQA SUBPOOL.

S10A – 1C – LSQA REQUEST FAILED – PAGE TABLE PAGED OUT.

S10A – 20 – AUTHORIZED PRIVATE REQUEST FAILED – PAGE TABLE PAGED OUT.

S10B – TIME SERVICE ROUTINE ERROR – ERROR IN INPUT PARAMETERS.

S10D– JOBSTEP TASK ABENDED WHEN A SUBTASK THAT IS ALSO A JOBSTEP TASK IS IN STEP-MUST-COMPLETE STATUS.

S10E – SPIE MACRO ERROR. THE PICA ADDRESS IS INVALID.

S112 – INVALID INPUT WAS PASSED TO SVC 18 BY THE BLDL OR FIND MACRO. REQUIRES MORE REAL STORAGE THAN IS AVAILABLE.
POSSIBLE CAUSE:
THE DCB HAS BEEN OVERLAID, ESPECIALLY DCBDEBAD OR DCBPOINT.

S112 – 01 – PARAMETER LIST NOT IN CALLER’S STORAGE.

S112 – 02 – DCB NOT IN CALLER’S STORAGE.

S112 – 03 – DCB DOES NOT POINT TO A VALID DEB.

S112 – 04 – PROGRAM CHECK OCCURRED IN THE POINT ROUTINE.

S112 – 13 – DCB DOES NOT POINT TO A VALID DEB. DCB DUMPED TO GTF.

S112 – 14 – PROGRAM CHECK OCCURRED IN THE POINT ROUTINE. THE DCB IS DUMPED TO THE GTF DATA SET.

S113 – AN ERROR OCCURRED DURING AN OPEN WITH A TYPE=J OPERAND.

S113 – 08 – A JFCB EXTENSION BLOCK WAS NEEDED FOR PROCESSING A PHYSICAL SEQUENTIAL DATA SET BUT NONE WAS AVAILABLE.

S113 – 0C – AN OPEN TYPE=J WAS ISSUED, BUT NO JFCB EXIT WAS FOUND IN THE DCB EXIT LIST. SPECIFY A JFCB EXIT, SUPPLY THE JFCB.

S113 – 18 – A JFCB EXTENSION BLOCK WAS NEEDED FOR PROCESSING A DIRECT OR INDEX SEQUENTIAL DATA SET.

S113 – 20 – END-OF-VOLUME ENCOUNTERED FOR A VSAM DATA SET. MULTI-VOLUME VSAM FILES CANNOT BE OPENED WITH A DCB.

S113 – 24 – OPEN ISSUED TO A MULTI-VOLUME VSAM DATA SET. MULTI-VOLUME VSAM FILES CANNOT BE OPENED WITH A DCB.

S113 – 28 – OPEN ATTEMPT FOR CONCATENATED VSAM USING A DCB.

S113 – 2C – OPEN ATTEMPT FOR VSAM USING A DCB WHEN THE CALLER WAS NOT APF AUTHORIZED OR IN SUPERVISOR STATE.

S113 – 30 – INVALID JCL DISPOSITION DETECTED FOR VSAM OPENED WITH A DCB. O
NLY ALLOWED (OLD,KEEP,KEEP) OR (SHR,KEEP,KEEP).

S113 – 34 – AN UNSUPPORTED DCB OPTION WAS SPECIFIED FOR A VSAM DATA SET OPENED WITH A DCB. ONLY VALID OPTIONS ARE INPUT AND UPDAT.

S113 – 38 – AN OPEN WAS ISSUED FOR A VSAM DATA SET WITH A DCB, BUT THE VTOC DOES NOT INDICATE THAT IT IS A VSAM DATA SET.

S115 – SVC 21 (STOW) ERROR. THE DCB DID NOT POINT TO A VALID DEB, OR THE DEB DID NOT POINT BACK TO THE DCB.

S117 – AN I/O ERROR OCCURRED DURING A BSAM CLOSE TYPE=T MACRO.

S118 – INVALID PARAMETERS WERE PASSED TO DEVTYPE (SVC 24). IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S118 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S118-RC)

S118 – 01 – THE DDNAME (ADDRESS IN GPR 1) WAS NOT IN CALLER’S REGION.

S118 – 02 – OUTPUT AREA (ADDRESS IN GPR 0) WAS NOT IN CALLER’S REGION.

S11A – A PROTECTION CHECK OCCURRED WHEN THE SYSTEM TRIED TO STORE INTO A USER SUPPLIED OS/VS CAMLST WORK AREA.

S121 – A MODULE ISSUED SVC 33 (IOHALT) WITH THE LOW ORDER BIT OF GPR1 OFF, WHICH INDICATES THE PRE-XA (2-BYTE UCB ADDR) INTERFACE.

S122 – EITHER THE OPERATOR OR THE JOB ENTRY SUBSYSTEM CANCELLED THE JOB, REQUESTING A DUMP. CHECK THE JOB LOG LISTING FOR MORE INFO.

S128 – AN INVALID ADDRESS LIST WAS SPECIFIED FOR AN EXTRACT MACRO. LIST NOT ON A FULLWORD BOUNDARY OR NOT IN JOB STEP’S STORAGE.

S12D – INVALID SEGMENT TABLE IN AN OVERLAY PROGRAM, SEE S0C1.

S12E – ERROR FOUND IN INPUT PARAMETERS TO TTIMER SERVICE ROUTINE.

S130 – THE DEQ MACRO SPECIFIED A RESOURCE NOT PREVIOUSLY SPECIFIED BY AN ENQ MACRO. THAT IS, THE PROGRAM HAD NOT REQUESTED CONTROL
A RESOURCE IT WAS ATTEMPTING TO RELEASE.

S137 – I/O ERROR IN END OF VOLUME LABEL PROCESSING ON MAGNETIC TAPE. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S137 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S137-RC)

S137 – 04 – AN I/O ERROR OCCURRED WHILE WRITING AN END OF VOLUME LABEL OR TAPE MARK.

S137 – 08 – AN I/O ERROR OCCURRED WHILE POSITIONING THE TAPE IN PREPARATION FOR LABEL PROCESSING.

S137 – 0C – AN I/O ERROR OCCURRED READING A TRAILER LABEL FOR A DATASET OPENED WITH THE INPUT OR INOUT OPTION, OR READING THE HEADER LABEL FOR A DATASET OPENED WITH THE RDBACK OPTION.

S137 – 10 – AN I/O ERROR OCCURRED WHILE POSITIONING A MAGNETIC TAPE AT THE END OF THE DATASET.

S137-14 – I/O ERROR READING HEADER LABELS FOR A DATASET

S137-18 – I/O ERROR WHILE POSITIONING A TAPE FOR THE FIRST DATA RECORD

S137-10 – I/O ERROR WHILE POSITIONING A TAPE FOR THE END OF A DATASET

S137-1C – AN INVALID TRAILER RECORD WAS READ DURING THE END-OF-VOLUME

S137 – 20 – AN INVALID HEADER LABEL WAS READ DURING END OF VOLUME.

S137 – 24 – A SPECIFIC VOLUME SERIAL NUMBER WAS SPECIFIED FOR THE SECOND OR SUBSEQUENT VOLUME OF AN OUTPUT DATASET ON MAGNETIC TAPE. DURING EOV PROCESSING, IT WAS DISCOVERED THAT THE EXPIRATION DATE (FROM THE HDR1 LABEL OF THE FIRST DATASET CURRENTLY ON THE SPECIFIED VOLUME) HAD NOT PASSED. WHEN REQUESTED TO SPECIFY WHETHER THE VOLUME COULD BE USED IN SPITE OF THE EXPIRATION DATE, THE OPERATOR DID NOT REPLY ‘U’. ASK THE OPERATOR TO REPLY ‘U’ OR SPECIFY ANOTHER VOLUME SERIAL.

S137 – 28 – THE OPERATOR REPLIED ‘M’ (REJECT VOL1 LABEL REWRITE) TO MESSAGE IEC704A.

S137 – 2C – THE INPUT VOLUME CONTAINS AN ISCII/ASCII VOLUME LABEL WITH A STANDARD VERSION LABEL THAT IS NOT 1 OR 3.

S137 – 30 – A LABEL VIOLATED THE PUBLISHED STANDARD FOR THE LABEL, AND THE LABEL VALIDATION EXIT REQUESTED OPEN/EOV TO REJECT THE VOLUME.

S137 – 38 – AN I/O ERROR OCCURRED WHILE PROCESSING A READ BLOCK ID TO STABLISH THE TAPE POSITION.

S138 – THE ERROR OCCURRED DURING THE EXECUTION OF AN ENQ MACRO. TWO ENQ MACROS WERE ISSUED FOR THE SAME RESOURCE IN THE SAME TASK
WITHOUT AN INTERVENING DEQ MACRO. THE SECOND ENQ MACRO DID NOT SPECIFY TEST, USE, OR HAVE IN ITS RET OPERAND.

S13E – THE TASK WHICH CREATED A SUBTASK HAS ISSUED A DETACH FOR THAT SUBTASK, SPECIFYING STAE=NO, BEFORE THAT SUBTASK HAS TERMINATED.

S14F – THE ROUTINE ATTEMPTED TO EXECUTE THE STATUS MACRO INSTRUCTION FOR OTHER THAN THE STOP, STOP SYNCH, OR START FUNCTION AND WAS NOT IN SUPERVISOR KEY (0-7).

S16E – THE CONTROL PROGRAM REQUESTED THAT A DEBCHK FUNCTION BE PERFORMED ON A DATA EXTENT BLOCK OBTAINED FROM THE DCB PASSED BY THE PROGRAM. THAT FUNCTION COULD NOT BE COMPLETED. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S16E OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S16E-RC)

S16E – 04 – THE INDICATED DEB POINTER IS NOT IN THE DEB TABLE. A DEB WHOSE ADDRESS IS NOT IN THE DEB TABLE CANNOT BE VERIFIED, DELETED, OR PURGED

S16E – 08 – INVALID TYPE SPECIFIED (MACRO NOT ISSUED). ACCEPTABLE TYPES ARE ADD, DELETE, VERIFY, AND PURGE.

S16E – 10 – DEBDCBAD DOES NOT POINT TO DCB. IT IS NORMALLY ASSUMED THAT THE DCBDEBAD FIELD OF THE DCB POINTES TO THE DEB, BUT THE
DEBDCBAD FIELD OF THE DEB MUST POINT TO THE DCB WHEN TYPE=VERIFY, ADD, OR DELETE.

S16E – 14 – AM VALUE DOES NOT EQUAL DEBAMTYP VALUE. WHEN A DEB POINTER IS ADDED TO THE TABLE, THE ACCESS METHOD POINTER (AM) VALUE, IF
GIVEN IS PLACED IN THE DEBAMTYP FIELD OF THE DEB. IF NO AM VALUE IS CODED, A 0 IS INSERTED IN THE FIELD. SUBSEQUENT DEBCHKS ISSUED TO VERIFY OR DELETE THAT DEB POINTER MUST EITHER SPECIFY THE SAME AM VALUE OR OMIT THE OPERAND. WHEN THE OPERAND IS OMITTED, NO COMPARISON IS MADE.

S16E – 18 – DEB NOT ON TCB CHAIN FOR TYPE = ADD. BEFORE THE DEB POINTER CAN BE ADDED TO THE TABLE, THE DEB ITSELF MUST BE QUEUED ON THE CURRENT TCB DEB CHAIN.

S16E – 1C – DEBAMTYP OR DEBTBLOF = 0 FOR TYPE = ADD. VALUES OTHER THAN 0 INDICATE A POINETR TO THIS DEB ALREADY EXISTS IN THE DEB TABLE.

S16E – 20 – DEB TABLE CONTAINS 32760 BYTES AND TYPE = ADD. THE CURRENT DEB TABLE DOES NOT HAVE SPACE FOR THIS NEW DEB POINTER. TO
INCREASE THE TABLE SIZE BY THE REQUIRED INCREMENT OF 24 WOULD CAUSE THE TABLE TO EXCEED ITS MAXIMUM SIZE.

S171 – THE REAL STORAGE MANAGER WAS INVOKED WITH A REQUEST FOR A PGFIX, PGFREE, PGLOAD, OR PGOUT SERVICE AND THE REQUEST WAS
ILLEGAL OR INVALID. THE REQUEST IS CONSIDERED TO BE ILLEGAL IF THE STORAGE RANGE SPECIFIED BY THE INPUT PARAMETERS DOES NOT EXIST (A GETMAIN WAS NOT ISSUED FOR IT).
NOTE: THE MEANINGS OF THE CONTENTS OF GENERAL REGISTERS 11, 12, 13, AND 14 ARE PROVIDED FOR DIAGNOSTIC PURPOSES IN THE FULL DESCRIPTION OF THIS ABEND IN THE SYSTEM CODES MANUAL. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S171 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S171-RC)
POSSIBLE CAUSE:
INPUT PARAMETER ERROR IN VIRTUAL SUBAREA LIST (VSL):
– VSL NOT ON A FULLWORD BOUNDARY.
– VSL NOT IN FIXED STORAGE.
– UNDEFINED OR CONFLICTING OPTION FLAGS. END ADDRESS OF RANGE NOT GREATER THAN BEGINNING ADDRESS. AN OPTION WAS SPECIFIED WHICH IS NOT SUPPORTED BY MVS. THESE ARE RSAOPT AND ECBIND.
– VSL IS STORE PROTECTE FROM THE CALLER.
INPUT PARAMETER ERROR ON ECB:
– ECB NOT ON FULLWORD BOUNDARY.
– ECB IS STORE-PROTECTED FROM CALLER.
– ECB NOT SPECIFIED FOR PGFIX.
– ECB SPECIFIED FOR PGOUT.

S171 – 04 – THE ERROR WAS DETECTED BY THE PAGE SERVICES ROUTINE. THIS GENERALLY INDICATES THAT THE CALLER DID NOT OWN THE VIRTUAL
STORAGE DEFINED BY THE VSL LIST ENTRY.

S171 – 16 – THE INPUT VSL OR ECB FAILED TO PASS THE PAGE SERVICES INTERFACE VALIDITY CHECK.

S178 – GETMAIN ERROR. AN AUTHORIZED PROGRAM REQUESTED VIRTUAL STORAGE THAT REQUIRES MORE REAL STORAGE THAN IS AVAILABLE. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S178 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S178-RC)**

S178 – 04 – NOT ENOUGH REAL STORAGE FOR SPACE IN SQA SUBPOOL.

S178 – 08 – NOT ENOUGH REAL STORAGE FOR SPACE IN FIXED CSA SUBPOOL.

S178 – 0C – NOT ENOUGH REAL STORAGE FOR SPACE IN LSQA SUBPOOL.

S178 – 1C – LSQA RE
QUEST FAILED – PAGE TABLE PAGED OUT.

S178 – 20 – AUTHORIZED PRIVATE REQUEST FAILED – PAGE TABLE PAGED OUT.

S201 – THE WAIT MACRO EXPANSION CONTAINED AN INVALID EVENT CONTROL BLOCK (ECB) ADDRESS OR THE PROGRAM IS NOT IN THE SAME KEY AS THE ECB.

S202 – THE POST MACRO INSTRUCTION ENCOUNTERED AN ERROR WHILE PROCESSING AN EVENT CONTROL BLOCK (ECB). IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S202 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S202-RC)**

S202 – 00 – THE CONTROL PROGRAM FOUND AN INVALID REQUEST BLOCK (RB) ADDRESS IN THE 3 LOW-ORDER BYTES OF THE ECB SPECIFIED IN A WAIT
MACRO. THE RB ADDRESS MUST REMAIN IN THE ECB UNTIL A POST IS ISSUED.

S202 – 04 – THE WAITING RB IS NOT ENABLED FOR INTERRUPTS.

S202 – 08 – FOR A POST IN A USER KEY AND A WAIT IN A SYSTEM KEY, THE ECB TO BE POSTED DOES NOT MATCH ANY ECB BEING WAITED ON.

S202 – 0C – FOR A WAIT IN A USER KEY, THE ECB ADDRESS IS INVALID.

S204 – 00 – (00 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S204) GETMAIN ERROR. NOT ENOUGH REAL STORAGE AVAILABLE TO BACK A MINIMUM NUMBER OF VSM CELLS (IN LSQA) DURING LOCAL CELL POOL EXPANSION.

S205 – 00 – (00 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S205)GETMAIN ERROR. NOT ENOUGH REAL STORAGE AVAILABLE TO BACK A MINIMUM NUMBER OF VSM CELLS (IN LSQA) DURING LOCAL CELL POOL EXPANSION.

S206 – THE ADDRESS OF THE PARAMETER LIST, OR ONE OF THE PARAMETERS PASSED TO A LINK, LOAD, XCTL, OR DELETE MACRO WAS INVALID.

S20A – 00 – (00 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S20A) GETMAIN ERROR. NOT ENOUGH REAL STORAGE AVAILABLE TO BACK A MINIMUM NUMBER OF VSM CELLS (IN LSQA) DURING LOCAL CELL POOL EXPANSION.

S213 – DSCB NOT FOUND; I/O ERROR IN READING OR WRITING DSCB. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S213 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S213-RC)
POSSIBLE CAUSE:
THE DATA SET IS NOT ON THE SPECIFIED VOLUME
DISP = MOD IS NOT COMPATIBLE WITH A VOLUME REFERENCE
INCORRECT TAPE POSITIONING

S213-04 – I/O ERROR WRITTEN IN THE DCB OF A DATAET

S213-08 – DATASET NOT FOUND ON VOLUME

S04E – RESOURCE UNAVAILABLE, CONTENTION, BAD INPUT, COULD BE ANYTHING READ SYSTEM MESSAGE CODE AND REASON CODE

S213-04 – I/O ERROR WRITING DCB OF A DATASET

S213 – 08 – AN OPEN MACRO WAS ISSUED FOR A PASSWORD PROTECTED DATASET BUT THE SYSTEM WAS UNABLE TO LOCATE THE PASSWORD DATASET.

S213 – 0C – AN I/O ERROR OCCURRED READING A FORMAT-1 DSCB FOR A DIRECT OR INDEXED SEQUENTIAL DATASET, OR THE FORMAT-1 DSCB COULD NOT BE FOUND ON THE VOLUME SPECIFIED BY THE DD STATEMENT.

S213-18 – DATASET NOT FOUND ON VOLUME

S213 – 18 – AN I/O ERROR OCCURRED WRITING BACK A FORMAT-1 DSCB.

S213 – 20 – DURING AN OPEN, A VOLUME CONTAINED MORE THAN 16 EXTENTS OF THE INDICATED DATASET. GOOD LUCK FIGURING THIS ONE OUT!
(SAM ACCESS OF AN ICF VSAM COMPONENT, PERHAPS?)

S213 – 24 – DURING AN OPEN, A VOLUME HAD A TYPE OF SPLIT CYLINDER ALLOCATION NOT SUPPORTED UNDER OS. POSSIBLE DOS VOLUME.

S213 – 28 – AN OPEN MACRO WAS ISSUED FOR A DIRECT ACCESS DATASET SPECIFING UNIT=SYSDA, BUT THE UNIT ALREADY CONTAINED 127 USERS,
WHICH IS THE MAXIMUM NUMBER ALLOWED.

S213 – 2C – THE FORMAT-1 DSCB NOT FOUND INSTALLATION EXIT MODULE ENCOUNTERED AN ERROR.

S213 – 30 – AN ATTEMPT WAS MADE TO OPEN A PDS FOR OUTPUT,DISP=SHR. THE PDS IS ALREADY OPEN IN THIS CONDITION.

S213 – 38 – WHEN OPENING A PDSE THE KEYLENGTH WAS NOT ZERO (0), OR THE KEYLENGTH WAS NOT ZERO (0) OR EIGHT (8) FOR DIRECTORY INPUT.

S213 – 3C – WHEN OPENING A PDSE THE RECFM IN THE DCB WAS DIFFERENT FROM THE RECFM ALREADY IN THE FORMAT-1 DSCB IN THE VTOC.

S213 – 40 – WHEN OPENING A PDSE, MACRF=(E) WAS SPECIFIED. ACCESS OF A PDSE BY EXCP IS NOT SUPPORTED.

S213 – 48 – OPEN DETECTED A BAD RETURN CODE FROM THE EXTENDED CACHE ATTRIBUTE FACILITY.

S213 – 4C – WHEN OPENING A PDSE DSORG=PS WAS SPECIFIED, BUT NO MEMBER WAS SPECIFIED.

S213 – 50 – OPEN DETECTED AN ERROR RETURN CODE FROM AN SMS SERVICE WHILE PROCESSING A PDSE.

S213 – 58 – AN ATTEMPT WAS MADE TO CHANGE THE DSORG OF AN SMS-MANAGED DATA SET TO UNMOVEABLE WHICH IS NOT ALLOWED ON SMS-MANAGED VOLUMES.

S213 – 60 – OPEN DETECTED AN ERROR RETURN CODE FROM THE RESIDENT CONVERT ROUTINE WHILE PROCESSING A PDSE DATA SET.

S213 – 64 – AN INCORRECT OPEN OPTION WAS SPECIFIED FOR A PDSE DATA SET.

S213 – 68 – AN OPEN FOR A PDSE WAS ISSUED WITH RECFM=FB AND LRECL=0.

S213 – 6C – AN OPEN FOR A PDSE WAS ISSUED REQUESTING QSAM UPDATEBUT LOCATE MODE WAS NOT SPECIFIED IN MACRF.

S213 – 70 – OPEN DETECTED A CROSS SYSTEM SHARE CONFLICT FOR THE PDSE.

S214 – I/O ERROR IN TAPE POSITIONING OR VOLUME DISPOSITION. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S214 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S214-RC)

S214-04 – I/O ERROR READING A USER LABEL ON A TAPE

S214-08 – I/O ERROR

S214-0C – EQC – I/O ERROR ON TAPE DRIVE

S214 – 10 – THE NUMBER OF BLOCKS PROCESSED ACCORDING TO THE TAPE POSITION DOES NOT MATCH THE DCB BLOCK COUNT.

S222 – JOB CANCELLED

S233 – INVALID PARAMETERS HAVE BEEN PASSED TO SVC DUMP. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S233 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S233-RC)

S233 – 04 – THE ADDRESS OF THE PARAMETER LIST IS ZERO.

S233 – 08 – THE PARAMETER LIST IS NOT A VALID SVC DUMP OR SNAP PARAMETER LIST FOR MVS.

S233 – 0C – THE CALLER-SUPPLIED DATASET IS ON AN UNSUPPORTED DEVICE.

S233 – 10 – IN A USER-SUPPLIED STORAGE RANGE, THE START ADDRESS IS GREATER THAN THE END ADDRESS.

S233 – 14 – THE USER-SUPPLIED DATA (FOR HDR= OR HDRAD=) IS GREATER THAN 100 CHARACTERS.

S233 – 18 – THE 4K SQA BUFFER HAS BEEN REQUESTED (BUFFER=YES) BUT IT IS NOT SERIALIZED (BY SETTING ON THE HIGH ORDER BIT IN CVTSDBF)

S233 – 1C – THE PARAMETER LIST OR WHAT IT POINTS TO IS IN THE 4K SQA BUFFER.

S233 – 20 – THE USER SUPPLIED A DCB ADDRESS AND THE DCB IS NOT OPEN, OR THE DCB ADDRESS IS INVALID.

S233 – 24 – THE SPECIFIED ASID PARAMETER WAS SYNTACTICALLY INVALID. THE ASID WAS LESS THAN ZERO, OR GREATER THAN THE MAXIMUM VALUE.

S233 – 28 – AN ASID SPECIFIED IN THE ASID LIST POINTED TO BY THE ASIDLST PARAMETER WAS SYNTACTICALLY INVALID. THE ASID WAS LESS THAN ZERO, OR GREATER THAN THE MAXIMUM VALUE.

S233 – 2C – THE ASIDLST ADDRESS IS ZERO, OR POINTS TO AN AREA THAT THE USER CANNOT REFERENCE.

S233 – 38 – THE CALLER SPECIFIED THE 4K SQA BUFFER (BUFFER=YES) BUT AN SVC DUMP WAS ALREADY IN PROGRESS.

S237 – THE ERROR OCCURRED DURING END-OF-VOLUME LABEL VERIFICATION. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S237 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S237-RC)
POSSIBLE CAUSE:
INCORRECT VOLUME SERIAL
INCORRECT VOLUME MOUNTED
INCORRECT LABELS

S237-04 – HARDWARE ERROR – BLOCK OF DATA MISSED OR SKIPPED

S237-08 – DSN ON HEADER LABEL DOESN’T MATCH VOLUME SERIAL

S237-567 – HARDWARE ERROR. THE BLOCK COUNT DOES NOT MATCH TRAILER LABEL

S237 – 0C – THE NUMBER OF BLOCKS PROCESSED, WHICH IS DETERMINED BY THE POSITION OF THE TAPE, DOES NOT MATCH THE DCB BLOCK COUNT.

S23E – THE ERROR WAS DETECTED DURING EXECUTION OF A DETACH MACRO INSTRUCTION. EITHER 1) THE PARAMETER PASSED TO DETACH IN REGISTER
1 WAS NOT A FULLWORD ADDRESS, 2) THE STORAGE KEY OF THAT ADDRESS DID NOT MATCH THAT OF THE ISSUER OF THE DETACH, OR 3) THE PARAMETER CONTAINED IN THE ADDRESSED FULLWORD OF THE ISSUER WAS NOT THE ADDRESS OF A SUBTASK OF THE ISSUER OF THE DETACH.

S240 – AN ERROR OCCURRED DURING EXECUTION OF A RDJFCB MACRO. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S240 OPERAND FOR MORE SPECIFIC INFORMATIO
N: H ABEND O(S240-RC)

S240 – 04 – A RDJFCB MACRO INSTRUCTION WAS ISSUED, BUT THE DCB DID NOT CONTAIN A FOUNDATION EXTENSION BLOCK.

S240 – 08 – A RDJFCB MACRO INSTRUCTION WAS ISSUED, BUT NO EXLST ADDRESS WAS FOUND IN THE DCB.

S240 – 0C – A RDJFCB MACRO INSTRUCTION WAS ISSUED, BUT NO JFCB EXIT WAS SPECIFIED IN THE DCB EXIT LIST.

S240 – 10 – A RDJFCB MACRO INSTRUCTION WAS ISSUED, BUT THE JFCB BUFFER IS NOT WITHIN THE USER’S STORAGE.

S278 – 00 – (00 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S278) GETMAIN ERROR. NOT ENOUGH REAL STORAGE AVAILABLE TO BACK A MINIMUM NUMBER OF VSM CELLS (IN LSQA) DURING LOCAL CELL POOL EXPANSION.

S2F3 – JOB WAS BEING EXECUTED WHEN SYSTEM FAILURE OCCURRED – A SYSTEM RESTART WAS PERFORMED

S300 – AN ERROR WAS DETECTED WHEN AN I/O OPERATION WAS REQUESTED;
– EITHER THE IOBM FIELD IN THE I/O BLOCK (IOB) IS HIGHER THAN THE MAXIMUM EXTENT COUNT (DEBNMEXT) IN THE DATA EXTENT BLOCK (DEB) OR THE STORAGE PROTECTION KEY OF THE DATA EXTENT BLOCK WAS NOT ZERO OR THE DEB VALIDITY CHECK ROUTINE RETURNED TO EXCP WITH A NON ZERO RETURN CODE. IN THE ABNORMAL TERMINATION DUMP, THE TCB FIELD TCBEXCPD (AT OFFSET C0) POINTS TO THE EXCP PROBLEM DETERMINATION AREA. THE ITEMS IN THE PROBLEM DETERMINATION AREA OF GREATEST INTEREST TO YOU ARE: (ALL OFFSETS IN HEX)
– OFFSET 10 CONTAINS A COPY OF THE REGISTERS WHEN EXCP DETERMINED THE ERROR CONDITION.
– OFFSET 50 CONTAINS THE CONTENTS OF THE REQUEST QUEUE ELEMENT (RQE) IF ALLOCATED, WHEN THE PROGRAM CHECK OCCURRED.
POSSIBLE CAUSES OF A NON-ZERO RETURN CODE FROM IFGDEBCK ARE:
– THE DEBTABLE DOES NOT EXIST.
– THE DEBTBLOF VALUE IN THE DEB IS LESS THAN ONE OR GREATER THAN THE NUMBER OF ENTRIES IN THE DEBTABLE.
– THE DEB ADDRESS FROM THE DCB DOES NOT MATCH ANY DEBTABLE ENTRY.

S301 – AN ECB SPECIFIED IN A WAIT MACRO ALREADY HAD ITS WAIT FLAG ON.

S305 – THE ERROR OCCURRED DURING EXECUTION OF A FREEMAIN MACRO:
– THE SPECIFIED SUBPOOL COULD NOT BE FOUND.
– THE SP PARAMETER WAS SPECIFIED BUT THE VIRTUAL STORAGE AREA TO BE RELEASED WAS NOT WITHIN THE SUBPOOL SPECIFIED.
– THE SP PARAMETER WAS NOT SPECIFIED BUT THE VIRTUAL STORAGE AREA TO BE RELEASED WAS NOT WITHIN SUBPOOL ZERO.
– THE SP PARAMETER WAS SPECIFIED CORRECTLY, BUT THE BOUNDARIES OF THE STORAGE AREAS TO BE FREED WERE NOT COMPLETELY DESCRIBED BY A DESCRIPTOR QUEUE ELEMENT.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S305 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S305-RC)

S305 – 08 – SQA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S305 – 0C – CSA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S305 – 10 – LSQA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S305 – 18 – PRIVATE AREA SUBPOOL NOT FOUND.

S305 – 1C – ZERO LENGTH WAS NOT SPECIFIED ON A SUBPOOL FREEMAIN.

S306 – INSUFFICIENT ACCESS AUTHORITY

S306 – 04 – THE REQUESTED PROGRAM WAS NOT FOUND IN THE INDICATED SOURCE. THAT IS, IT WAS FOUND IN AN UNAUTHORIZED LIBRARY.

S306 – 08 – AN UNCORRECTABLE I/O ERROR OCCURRED WHEN THE CONTROL PROGRAM ATTEMPTED TO SEARCH THE DIRECTORY OF THE LIBRARY
CONTAINING THE MODULE, OR THE MODULE IS NOT RE-ENTRANT.

S306 – 0C – THE MODULE COULD NOT BE FOUND IN THE LPA OR IN THE LPA DIRECTORY OR AN AUTHORIZED LIBRARY.

S306 – 10 – A LOAD MACRO REQUESTED A MODULE REQUIRING PAGE ALIGNMENT WITH GLOBAL=(YES,F) SPECIFIED.

S306 – 20 – A JOB STEP MODULE WAS FOUND IN AN UNAUTHORIZED LNKLST LIBRARY WHEN AN APF AUTHORIZED MODULE WAS REQUIRED.

S306 – 24 – AN AUTHORIZED SERVICE ATTEMPTED TO ACCESS A NON-REENTRANT LOAD MODULE WHICH WAS LOADED FROM AN AUTHORIZED LIBRARY BY AN UNAUTHORIZED CALLER. ANOTHER COPY OF THE MODULE COULD NOT BE FOUND.

S306 – 30 – THE USER WAS DENIED ACCESS TO THE PROGRAM BY THE SYSTEM AUTHORIZATION FACILITY.

S306 – 34 – THE USER ATTEMPTED TO USE A PROGRAM WHILE A PROGRAM-ACCESSED DATA SET WAS OPEN.

S30A – THE ERROR OCCURRED DURING EXECUTION OF AN R-FORM FREEMAIN MACRO FOR ONE OF THE FOLLOWING REASONS:
– A FREEMAIN FOR AN ENTIRE SUBPOOL WAS REQUESTED (REGISTER 1 WAS ZERO) BUT THE LENGTH IN REGISTER 0 WAS NOT SET TO ZERO.
– THE SPECIFIED SUBPOOL COULD NOT BE FOUND.
– THE SP PARAMETER WAS SPECIFIED, BUT THE VIRTUAL STORAGE AREA TO BE RELEASED WAS NOT WITHIN THE SUBPOOL SPECIFIED.
– THE SP PARAMETER WAS NOT SPECIFIED, BUT THE VIRTUAL STORAGE AREA TO BE RELEASED WAS NOT WITHIN SUBPOOL ZERO.
– THE SP PARAMETER WAS SPECIFIED CORRECTLY, BUT THE BOUNDARIES OF THE STORAGE AREAS TO BE FREED WERE NOT COMPLETELY DESCRIBED BY A DECSRIPTOR QUEUE ELEMENT (DQE).
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S30A OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S30A-RC)

S30A – 08 – SQA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S30A – 0C – CSA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S30A – 10 – LSQA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S30A – 14 – PRIVATE STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S30A – 18 – PRIVATE AREA SUBPOOL NOT FOUND.

S30A – 1C – ZERO LENGTH WAS NOT SPECIFIED ON A SUBPOOL FREEMAIN.

S30A – 20 – FOR A CSA STORAGE FREEMAIN, THE AREA TO BE FREED IS LARGER THAN WAS SPECIFIED ON THE ORIGINAL GETMAIN, OR THE FREEMAIN START ADDRESS IS NOT VALID.

S30A – 24 – FOR A PRIVATE STORAGE FREEMAIN, THE AREA TO BE FREED IS LARGER THAN WAS SPECIFIED ON THE ORIGINAL GETMAIN, OR THE FREEMAIN START ADDRESS IS NOT VALID.

S30E – BAD DATA(CHECK ONCODE),CONTENTION

S311 – I/O ERROR READING HEADER LABELS FOR A DATASET

S313 – AN ABEND OCCURRED WHILE OPENING A DASD DATA SET BECAUSE OF A VTOC I/O ERROR OR A SYSTEM LOGIC ERROR.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S313 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S313-RC)

S313 – 04 – AN I/O ERROR OCCURRED READING A FORMAT-2 OR FORMAT-3 DSCB DURING THE EXECUTION OF AN OPEN MACRO.

S313 – 08 – OPEN RECEIVED A NON-ZERO RETURN CODE FROM DASD CALCULATION SERVICES (DCS) WHILE TRYING TO GET A SYSTEM-DETERMINED BLOCKSIZE.

S314 – I/O ERROR IN READING DSCB
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S314 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S314-RC)
POSSIBLE CAUSE:
SORTIN JCL GAVE WRONG BLOCK SIZE FOR A VARIABLE RECORD

S314 – 04 – AN I/O ERROR OCCURRED READING A DSCB FOR A DATASET ON A DIRECT ACCESS DEVICE DURING EXECUTION OF A CLOSE MACRO.

S314 – 08 – AN I/O ERROR OCCURRED READING A FORMAT-1 DSCB DURING EXECUTION OF A CLOSE MACRO AND STANDARD USER LABELS WERE SPECIFIED.

S317 – AN OCCURRED DURING A BSAM CLOSE TYPE=T MACRO FOR A DASD FILE.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S317 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S317-RC)

S317 – 04 – AN I/O ERROR OCCURRED READING A FORMAT-1 DSCB DURING EXECUTION OF A BSAM CLOSE TYPE=T MACRO INSTRUCTION.

S317 – 08 – THE DSCB READ DURING EXECUTION OF A BSAM CLOSE TYPE=T MACRO INSTRUCTION DID NOT HAVE THE EXPECTED FORMAT-1 OR FORMAT-4
FORMAT ID.

S322 – TIMED OUT, POSSIBLY NO TIME PARAMETER OR OTHER INFO MISSING

S32D – ADDRESS IN SEGMENT TABLE OR ENTRY TABLE OUTSIDE OF STORAGE FOR JOB STEP AN OVERLAY PROGRAM WAS FOUND TO CONTAIN A RECORD OF INCORRECT LENGTH, OR AN I/O ERROR WAS ENCOUNTERED – RE-LINKEDIT IT

S337 – THE ERROR OCCURRED WHEN THE END OF A DATA SET WAS REACHED.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THES337 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S337-RC)
POSSIBLE CAUSE:
NO END OF DATA ROUTINE WAS PROVIDED
TRIED TO READ PAST END OF FILE
TRIED TO WRITE ON A TAPE DEFINED AS INPUT

S337 – 04 – THE END OF DATASET WAS REACHED, BUT NO END-OF-DATASET ROUTINE (EODAD) WAS SPECIFIED IN THE DCB.

S337 – 08 – NO END-OF-DATASET ROUTINE (EODAD) SPECIFIED IN THE DCB FOR DD DUMMY DATASET.

S338 – AN UNAUTHORIZED TASK A
TTEMPTED TO USE AUTHORIZED OPTIONS OF THE ENQ MACRO INSTRUCTION.

S33E – A DETACH MACRO INSTRUCTION SPECIFYING THE STAE=YES OPERAND HAS BEEN ISSUED BY THE ORIGINATING TASK, BUT THE SPECIFIED SUBTASK HAS NOT COMPLETED EXECUTION.
POSSIBLE CAUSE:
THIS MAY OR MAY NOT BE AN ERROR. IF YOU INTEND FOR THE SUBTASK TO COMPLETE PROCESSING BEFORE IT IS DETACHED, USE THE ECB OR EXTR OPERAND ON THE ATTACH MACRO INSTRUCTION THAT CREATES THE SUBTASK TO ACHEIVE SYNCHRONIZATION.

S378 – THE ERROR OCCURRED DURING EXECUTION OF AN RC OR RU FORM FREEMAIN MACRO.
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S378 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S378-RC)
POSSIBLE CAUSE:
A FREEMAIN FOR AN ENTIRE SUBPOOL WAS REQUESTED (REGISTER 1 WAS ZERO) BUT THE LENGTH IN REGISTER 0 WAS NOT SET TO ZERO.
THE SPECIFIED SUBPOOL COULD NOT BE FOUND.
THE SP PARAMETER WAS SPECIFIED, BUT THE VIRTUAL STORAGE AREA TO BE RELEASED WAS NOT WITHIN THE SUBPOOL SPECIFIED.
THE SP PARAMETER WAS NOT SPECIFIED, BUT THE VIRTUAL STORAGE AREA TO BE RELEASED WAS NOT WITHIN SUBPOOL ZERO.
THE SP PARAMETER WAS SPECIFIED CORRECTLY, BUT THE BOUNDARIES OF THE STORAGE AREA TO BE FREED WERE NOT COMPLETELY DESCRIBED BY THE DESCRIPTOR QUEUE ELEMENT (DQE).

S378 – 08 – SQA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S378 – 0C – CSA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S378 – 10 – LSQA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S378 – 14 – PRIVATE AREA STORAGE IS NOT IN THE SUBPOOL SPECIFIED.

S378 – 18 – PRIVATE AREA SUBPOOL NOT FOUND.

S378 – 1C – ZERO LENGTH WAS NOT SPECIFIED ON A SUBPOOL FREEMAIN.

S400 – THE DCB IN THE DEB DOES NOT EQUAL THE DCB ADDRESS IN THE IOB. IN THE ABNORMAL TERMINATION DUMP, THE TCB FIELD TCBEXCPD (AT OFFSET C0) POINTS TO THE EXCP PROBLEM DETERMINATION AREA. THE ITEMS IN THE PROBLEM DETERMINATION AREA OF GREATEST INTEREST TO YOU ARE: (ALL OFFSETS IN HEX)
– OFFSET 10 CONTAINS A COPY OF THE REGISTERS WHEN EXCP DETERMINED THE ERROR CONDITION.
– OFFSET 50 CONTAINS THE CONTENTS OF THE REQUEST QUEUE ELEMENT (RQE) IF ALLOCATED, WHEN THE PROGRAM CHECK OCCURRED.

S402 – THE EVENTS POST MACRO INSTRUCTION ENCOUNTERED AN ERROR WHILE PROCESSING AN EVENT CONTROL BLOCK (ECB).

S402 – 00 – THE CONTROL PROGRAM FOUND AN INVALID EVENTS TABLE ADDRESS IN THE 3 LOW-ORDER BYTES OF THE ECB SPECIFIED.

S402 – 04 – THE WAITING RB IS NOT ENABLED FOR INTERRUPTS.

S402 – 08 – FOR A WAIT OR POST IN A USER KEY, THE ECB ADDRESS IS INVALID.

S406 – THE REQUESTED LOAD MODULE WAS MARKED BY THE LINKAGE EDITOR AS ONLY LOADABLE.

S40A – AN R-FORM FREEMAIN MACRO IS ATTEMPTING TO FREE AN ENTIRE SUBPOOL THAT SHOULD NOT BE FREEMAINED.

S40A – 04 – ATTEMPTING TO FREEMAIN A SUBPOOL THAT CANNOT BE SUBPOOL FREEMAINED.

S40A – 08 – A PROBLEM PROGRAM IS TRYING TO FREE SUBPOOL ZERO.

S40D – THIS COMPLETION CODE IS FOUND ONLY IN ASCBS. BECAUSE OF RECURSIVE ERRORS TRYING TO TERMINATE A TASK IT BECAME NECESSARY TO TERMINATE THE MEMORY. THE RTM ATTEMPTS TO TERMINATE THE ADDRESS SPACE. A DUMP MAY HAVE BEEN TAKEN TO THE SYS1.DUMP DATASET.

S413 – INPUT, INOUT, OR RDBACK SPECIFIED, BUT NO VOL SER IN DD; I/O ERROR IN READING VOLUME LABEL; COULD NOT MOUNT VOLUME ON
DEVICE; VOLUMES SPECIFIED LESS THAN DEVICES ALLOCATED.

POSSIBLE CAUSE
FORGOTTEN VOLUME SERIAL FOR INPUT TAPE
HAD DISP NEW WHEN SHOULD HAVE HAD OLD
GENERATED AS NL, TRIED TO READ AS SL
MISSING OR INCONSISTENT DCB INFORMATION
VOLUME COULD NOT BE MOUNTED, OPERATOR MOUNTED SCRATCH
ERROR READING LABEL
OPENED A FILE AS INPUT WITHOUT FIRST GENERATING THE FILE
TRIED TO CLOSE A FILE WITHOUT OPENING IT
TRIED TO OPEN SECOND DATA SET ON A TAPE WITHOUT CLOSING THE FIRST
THE REQUESTED DRIVE WAS SWITCHED OFF
SORT VERB BLEW DUE TO SD NOT MATCHING FD WITH USING OR GIVING

S413-04 – UNIT NOT AVAILABLE FOR MOUNTING VOLUME

S413-08 – AN I/O ERROR OCCURRED POSITIONING A MAGNETIC TAPE VOLUME TABE DRIVE PROBLEM(IF ‘EQC’ OR ‘SIM’ IN MSG) TAPE PROBLEM(IF ‘SEQ’ IN MSG)

S413-0C – AN I/O ERROR OCCURRED READING THE VOLUME LABEL ON A MAGNETIC TAPE VOLUME.

S413 – 10 – AN I/O ERROR OCCURRED WRITING A TAPE MARK.

S413-18 – UTPROC=RESTART DID NOT WORK

S413-20 – I/O ERROR READING VOLUME LABEL ON A DASD VOLUME

S413 – 24 – AN OPEN MACRO WAS ISSUED FOR A DATASET ON MAGNETIC TAPE. A DENSITY WAS SPECIFIED IN THE DCB DEN PARAMETER WHICH WAS INCOMPATIBLE WITH THE RECORDING DENSITY OF THE DRIVE ALLOCATED TO THE DATASET.

S413 – 28 – NON-ZERO RETURN CODE FROM OPEN DAVV (DIRECT ACCESS VOLUME VERIFICATION) MODULE AFTER A IEFSSREQ MACRO INSTRUCTION. THIS CODE INDICATES THE SUBSYSTEM DISCOVERED A FUNCTIONAL OR LOGICAL ERROR THAT IT COULD NOT PROCESS.

S413 – 2C – ERROR DURING MSS MOUNT, DEMOUNT, ACQUIRE OR RELINQUISH.

S413 – 30 – THE MSS HARDWARE MOUNTED THE WRONG VIRTUAL VOLUME.

S413-34 – NO REFERBACK, NO LABEL

S413 – 38 – DURING A READ BLOCK ID COMMAND TO ESTABLISH THE TAPE POSITION, AN ERROR OCCURRED.

S413 – 40 – THE DEVICE DOES NOT SUPPORT THE RECORDING MODE REQUESTED BY THE USER OR DETERMINED BY THE SYSTEM.

S413 – 44 – THE TAPE VOLUME DOES NOT CONFORM TO THE SINGLE RECORDING MODE RULES. FOR INPUT, THE VIOLATION OCCURRED WHEN THE TAPE WAS WRITTEN WHEN THE RULES COULD NOT BE ENFORCED. FOR OUTPUT, THE ABEND PREVENTS ANY VIOLATION FROM HAPPENING.

S414 – AN ERROR OCCURRED DURING CLOSE PROCESSING FOR A DATASET ON A DIRECT ACCESS DEVICE.

S414 – 04 – AN I/O ERROR OCCURRED WRITING A DSCB DURING CLOSE OF A DASD FILE.

S414 – 08 – FOR A QSAM DATA SET EITHER AN I/O ERROR OCCURRED WHILE FLUSHING THE BUFFERS DURING CLOSE PROCESSING, OR A CLOSE WAS ISSUED IN THE CALLER’S SYNAD ROUTINE.

S417 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S417) AN I/O ERROR OCCURRED WRITING AN UPDATED FORMAT-1 DSCB DURING THE EXECUTION OF A BSAM CLOSE TYPE=T MACRO INSTRUCTION.

S437 – AN ERROR OCCURRED DURING END-OF-VOLUME.

S437 – 08 – WHEN FEOV WAS ISSUED, THE DCB POINTER WAS INVALID.

S437 – 0C – DEB NOT IN DEB TABLE.

S478 – AN RC-FORM OR RU-FORM FREEMAIN MACRO IS ATTEMPTING TO FREE AN ENTIRE SUBPOOL THAT SHOULD NOT BE FREEMAINED.

S478 – 04 – ATTEMPTING TO FREEMAIN A SUBPOOL THAT CANNOT BE SUBPOOL FREEMAINED.

S478 – 08 – A PROBLEM PROGRAM IS TRYING TO FREE SUBPOOL ZERO.

S502 – DURING EXECUTION OF A POST MACRO INSTRUCTION, THE CONTROL PROGRAM FOUND THAT THE EVENTS TABLE SPECIFIED IN THE ECB HAD NO AVAILABLE ENTRIES TO CONTAIN THE POSTED ECB ADDRESS.

S504 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S504) AT LEAST ONE OVERLAP AMONGST LENGTH LIST, ADDRESS LIST AND PARAMETER LIST AT GETMAIN EXECUTION TIME.

S505 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S505) AT LEAST ONE OVERLAP AMONGST LENGTH LIST, ADDRESS LIST AND PARAMETER LIST AT FREEMAIN EXECUTION TIME.

S513 – THE ERROR OCCURRED DURING EXECUTION OF AN OPEN MACRO INSTRUCTION FOR A DATA SET ON MAGNETIC TAPE.

S513 – 04 – AN OPEN MACRO WAS ISSUED FOR A MAGNETIC TAPE DATASET ALLOCATED TO A DEVICE THAT ALREADY HAS AN OPEN DATASET ON IT.

S513 – 08 – A LABEL VIOLATED THE PUBLISHED STANDARD FOR THAT LABEL, AND THE LABEL VALIDATION EXIT REQUESTED OPEN/EOV TO REJECT THE VOLUME.

S513 – 0C – NON-STANDARD VOL1 HEADER ON AN ASCII TAPE.

S522 – TIMED OUT – TAPE NOT MOUNTED, HSM RECALL

S546 – CANCELLED BY OPERATOR OR SYSTEM

S567 – HARDWARE ERROR – BLOCK OF DATA MISSED OR SKIPPED

S582 – 00 – (00 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S582) WHILE PERFORMING RACHECK SVC PROCESSING, RACF WAS UNABLE TO VERIFY A USER BECAUSE NO ACCESS CONTROL ENVIRONMENT (ACEE) WAS AVAILABLE.

__POSSIBLE CAUSE— __
USER LOGGED ON OR JOB STARTED WHILE RACF WAS INACTIVE, BUT RACF HAS SINCE BEEN REA
CTIVATED.

S604 – GETMAIN ERROR
POSSIBLE CAUSE
MISSING SORTLIB CARD
SUBSCRIPT ERROR – CLOBBERED FREE QUEUE ELEMENT

S604 – 04 – THE PARAMETER LIST IS NOT ON A WORD BOUNDARY.

S604 – 08 – THE PARAMETER LIST IS IN PROTECTED STORAGE.

S604 – 0C – THE LENGTH LIST IS NOT ON A WORD BOUNDARY.

S604 – 10 – THE LENGTH LIST IS IN PROTECTED STORAGE.

S604 – 14 – THE ADDRESS LIST IS NOT ON A WORD BOUNDARY.

S604 – 18 – THE ADDRESS LIST IS IN PROTECTED STORAGE.

S604 – 1C – THE PARAMETER LIST REQUEST FLAGS ARE INVALID.

S605 – FREEMAIN ERROR

POSSIBLE CAUSE
MISSING SORTLIB CARD
SUBSCRIPT ERROR – CLOBBERED FREE QUEUE ELEMENT

S605 – 04 – THE PARAMETER LIST IS NOT ON A WORD BOUNDARY.

S605 – 08 – THE PARAMETER LIST IS IN PROTECTED STORAGE.

S605 – 0C – THE LENGTH LIST IS NOT ON A WORD BOUNDARY.

S605 – 10 – THE LENGTH LIST IS IN PROTECTED STORAGE.

S605 – 14 – THE ADDRESS LIST IS NOT ON A WORD BOUNDARY.

S605 – 18 – THE ADDRESS LIST IS IN PROTECTED STORAGE.

S605 – 1C – THE PARAMETER LIST REQUEST FLAGS ARE INVALID.

S60A – (NON-MVS/XA) FREEMAIN QUEUE ELEMENT OR ADDRESS ERROR NEEDS MORE CORE JCL FOR INPUT DISKS REQUESTED 2 UNITS, GAVE 1 VOLUME SERIAL FORGOT DD CARD FOR SYS1.SORTLIB

S613 – I/O ERROR IN TAPE POSITIONING OR LABEL PROCESSING

POSSIBLE CAUSE
TAPE LABEL WAS NOT IN REQUESTED DENSITY
DCB MISSING
DEN MISSING ON A TAPE THAT REQUIRES IT DEFAULT DEN=3 (1600 BPI)
RECFM=F WAS SPECIFIED FOR A FILE WHICH WAS FB
INCORRECT HEADER
TAPE POSITIONING ERROR
TAPE DRIVE FAILURE DURING OPEN

S613 – 04 – AN I/O ERROR OCCURRED POSITIONING A MAGNETIC TAPE VOLUME.

S613-08 – TAPE POSITIONING ERROR

S613(SF13) – BAD TAPE OR DRIVE – ERROR READING LABEL ON TAPE IF YOU SEE MESSAGE IN RMDS OUTPUT: DATA SET NAME DOES NOT MATCH FOR A MASTER VOLUME INSTALLATION OPTION ALLOWS UPDATE OF ONLY THE LAST FILE ON MASTER VOLUMES CHECK JCL AT FAILED STEP TO MAKE SURE LABEL IS CORRECT – POSSIBLY NO LABEL

S613 – 0C – AN INVALID LABEL WAS READ FROM A MAGNETIC TAPE VOLUME. THIS ERROR MAY BE DUE TO A PREVIOUS ABNORMAL TERMINATION ASSOCIATED WITH THE SAME TAPE SINCE IT WAS LAST MOUNTED, POSSIBLY IN A PREVIOUS JOB OR STEP, LEAVING THE TAPE POSITIONED IMPROPERLY.

S613 – 10 – AN I/O ERROR OCCURRED WRITING A TAPE LABEL.

S613 – 14 – AN I/O ERROR OCCURRED WRITING A TAPE MARK AFTER THE HEADER LABELS.

S614 – AN ERROR OCCURRED DURING CLOSE PROCESSING FOR A DATASET ON A DIRECT ACCESS DEVICE OR FOR A SUBSYSTEM DATASET.

POSSIBLE CAUSE
OPERATOR DISMOUNTED VOLUME WHILE PROGRAM WAS PROCESSING

S614 – 04 – AN I/O ERROR OCCURRED WRITING A FILE MARK FOR A DATASET ON A DIRECT ACCESS DEVICE DURING EXECUTION OF A CLOSE MACRO.

POSSIBLE CAUSE
OPERATOR DISMOUNTED VOLUME WHILE PROGRAM WAS PROCESSING

S614 – 08 – A FILE MARK SHOULD HAVE BEEN WRITTEN ON AN OUTPUT DATASET. THE DCBFDAD FIELD IN THE DCB INDICATED AN EXTENT NUMBER IN THE DEB GREATER THAN THE NUMBER OF EXTENTS IN THE DATASET. CONSEQUENTLY, IT COULD NOT BE DETERMINED WHERE THE FILE MARK
SHOULD HAVE BEEN WRITTEN.

S614 – 0C – IEFSSREQ MACRO RETURNED AN ERROR CODE IN REGISTER 15 WHICH INDICATES THAT THE SUBSYSTEM WAS NOT OPERATING.

S614 – 10 – A SPOOLED OR SUBSYSTEM DATASET COULD NOT BE CLOSED BY THE JOB ENTRY SUBSYSTEM OR ALTERNATE SUBSYSTEM.

S614 – 14 – A CLOSE MACRO INSTRUCTION DETECTED AN ERROR RETURN CODE FROM AN SMS SERVICE WHILE PROCESSING A PDSE DATA SET.

S622 – TSO SESSION WAS CANCELLED OPERATOR STOPPED TSO OR CANCELLED THE USER USER SIGNALLED ATTN AFTER THE ALLOCATION PROCESS HAD COMPLETED THE USER DISCONNECTED HIS TERMINAL FROM THE SYSTEM

S637 – I/O ERROR IN WRITING TAPE MARK, TAPE POSITIONING, READING LABEL, SENSING FOR FILE PROTECTION RING; DCB BIT DOES NOT
INDICATE CONCATENATION OF UNLIKE ATTRIBUTES. IMPROPER INFO ON JCL FOR MULTIREEL NSL TAPE

S637-OC – CONCATENATION ON UNLIKE ATTRIBUTES

S637-2C – I/O ERROR READING HEADER LABEL ON TAPE

S637 – 04 – AN I/O ERROR OCCURRED WHILE READING A TAPE LABEL, WRITING A TAPE MARK, OR POSITIONING A MAGNETIC TAPE VOLUME.

S637 – 08 – FOLLOWING USER TRAILER LABEL PROCESSING, AN I/O ERROR OCCURRED POSITIONING A MAGNETIC TAPE.

S637 – 0C – CONCATENATION OF DATASETS WITH UNLIKE ATTRIBUTES WAS DETECTED, BUT NOT SPECIFIED IN THE DCB.

S637 – 10 – AN I/O ERROR OCCURRED WHILE POSITIONING A MAGNETIC TAPE DATASET THAT WAS OPENED WITH THE OPTION INPUT OR INOUT TO BE READ BACKWARD. IF IT IS A TAPE WITH STANDARD LABELS, THE ERROR OCCURRED POSITIONING AT THE LABELS. IF IT IS A TAPE WITH NO LABELS, THE ERROR OCCURRED POSITIONING AT THE DATA.

S637 – 14 – AN I/O ERROR IN TAPE POSITIONING OCCURRED FOR A DATASET WITH THE LEAVE OPTION SPECIFIED IN THE OPEN MACRO OR IN THE FEOV MACRO.

S637 – 18 – AN I/O ERROR IN TAPE POSITIONING OCCURRED FOR A DATASET OPENED WITH THE REREAD OPTION.

S637 – 1C – AN I/O ERROR IN TAPE POSITIONING OCCURRED WHEN FEOV WAS ISSUED FOR A DATASET WITH DISP=PASS AND NO OPEN OPTION 2 SPECIFIED.

S637 – 20 – RDBACK WAS INVALIDLY SPEICFIED FOR A NEW CONCATENATED TAPE VOLUME. RDBACK IS NOT SUPPORTED WITH CONCATENATION.

S637 – 24 – AN I/O ERROR OCCURRED REWINDING A SCRATCH MAGNETIC TAPE VOLUME. EITHER FEOV WITH A REWIND OPTION WAS ISSUED, OR NO OPEN OPTION 2 WAS SPECIFIED WHEN THE DISPOSITION WAS NOT PASS.

S637 – 2C – AN I/O ERROR OCCURRED WHILE REWINDING A MAGNETIC TAPE VOLUME PRIOR TO VERIFYING THE VOLUME LABEL.

S637-34 – I/O ERROR READING END OF VOLUME LABEL

S700 – A PROGRAM CHECK OCCURRED DURING EXCP PROCESSING OF AN I/O REQUEST. THE PROGRAM CHECK OCCURRED IN A SUPERVISOR SERVICE ROUTINE CALLED BY EXCP. THIS IS LIKELY NOT A PROGRAMMER ERROR. IN THE ABNORMAL TERMINATION DUMP, THE TCB FIELD TCBEXCPD (AT OFFSET C0) POINTS TO THE EXCP PROBLEM DETERMINATION AREA. THE ITEMS IN THE PROBLEM DETERMINATION AREA OF GREATEST INTEREST TO YOU ARE: (ALL OFFSETS IN HEX)
– OFFSET 2 CONTAINS A FLAG BYTE INDICATING WHERE THE ERROR OCCURRED.

THE BIT PATTERN IS AS FOLLOWS:
1… …. ERROR IN SVC PORTION OF EXCP
.1.. …. ERROR IN SRB PORTION OF EXCP
..1. …. ERROR IN PCI APPENDAGE
…1 …. ERROR IN CHE APPENDAGE
…. 1… ERROR IN ABE APPENDAGE
…. .1.. ERROR IN EOE APPENDAGE
…. ..1. ERROR IN PGFX APPENDAGE
…. …1 APENDAGE IS ACTIVE
…. …. ERROR IN SIO APPENDAGE

– OFFSET 4 CONTAINS A COPY OF THE PROGRAM STATUS WORD (PSW) BEFORE RTM WAS ENTERED.
– OFFSET E CONTAINS THE INTERRUPTION CODE. THE ABEND MACRO.
– OFFSET 54 CONTAINS THE CONTENTS OF THE REQUEST QUEUE ELEMENT (RQE), IF ALLOCATED, FOR THE I/O REQUEST BEING PROCESSED

S706 – A LOAD MODULE MARKED FOR THE LINKAGE EDITOR IS NON-EXECUTABLE

S713 – TRIED TO WRITE ON A DATASET WHOSE DATE PROTECTION HAD NOT EXPIRED. OPERATOR REPLIED ‘M’ TO IEC507D TO HONOR EXP DATE.

S713 – 04 – A DATASET ON MAGNETIC TAPE WAS OPENED FOR INOUT, OUTIN, OUTPUT, OUTINX, OR EXTEND, BUT THE VOLUME CONTAINED A DATASET WHOSE EXPIRATION DATE HAD NOT BEEN REACHED.

S713 – 08 – AN OPEN MACRO WAS ISSUED WITH INOUT FOR A DATASET ON A DIRECT ACCESS DEVICE WITH DISP=OLD SPECIFIED ON THE DD STATEMENT. THE EXPIRATION DATE ON THE DATASET HAD NOT BEEN REACHED.

S713 – 0C – THE OPERATOR REPLIED ‘M’ TO IEC704A TO REJECT THE REQUEST TO REWRITE THE TAPE VOLUME’S VOL1 HEADER.

S714 – I/O ERROR IN LABEL PROCESSING – CLOSE FOR MAGNETIC TAPE TAPE DRIVE FAILURE DURING CLOSE

S714 – 04 – AN I/O ERROR OCCURRED WRITING TRAILER LABEL 1 FOR A DATASET ON MAGNETIC TAPE DURING EXECUTION OF A CLOSE MACRO.

S714 – 08 – AN I/O ERROR OCCURRED WRITING TRAILER LABEL 2 FOR A DATASET ON MAGNETIC TAPE DURING EXECUTION OF A CLOSE MACRO.

S714-0C – AN I/O ERROR OCCURRED WRITING A TAPE MARK DURING EXECUTION OF A CLOSE MACRO.

S717
AN I/O ERROR OCCURRED DURING EXECUTION OF A BSAM CLOSE TYPE=T MACRO INSTRUCTION. THE RETURN CODE INDICATES THE EXACT ERROR.

S717 – 04 – I/O ERROR FOR BSAM CLOSE TYPE=T WHEN WRITING A TAPE MARK FOLLOWING THE LAST RECORD

S717 – 08 – I/O ERROR FOR BSAM CLOSE TYPE=T WHEN WRITING TRAILER LABEL-1 OR TRAILER LABEL-2

S717 – 0C – I/O ERROR FOR BSAM CLOSE TYPE=T WHEN WRITING A TAPE MARK FOLLOWING THE TRAILER LABELS

S717 – 10 – I/O ERROR FOR BSAM CLOSE TYPE=T WHEN READING TRAILER LABEL-1 TO UPDATE THE DCB BLOCK COUNT

S718 – NOT ENOUGH REGION TO LOAD MODULES

S722 – LINES EXCEEDED, ADD A MAIN LINES CARD – //*MAIN LINES=(100,WARNING)

S737 – I/O ERROR; DSCB NOT FOUND FOR MULTI-VOLUME OR CONCATENATEDDATA SET. BE SURE ALL THE DATA SETS EXIST FOR CONCATENATED DATA SETS
– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S737-RC)

S737 – 04 – AN I/O ERROR OCCURRED READING A DSCB DURING END OF VOLUME PROCESSING OR THE DSCB COULD NOT BE FOUND ON THE SPECIFIED VOLUME.

S737 – 08 – AN I/O ERROR OCCURRED READING A DIRECT ACCESS VOLUME LABEL DURING END OF VOLUME PROCESSING.

S737 – 0C – AN I/O ERROR OCCURRED READING THE DSCB FOR A CONCATENATED PARTITIONED DATASET.

S737 – 10 – AN I/O ERROR OCCURRED WRITING A FILE MARK FOR A DATASET ON A DIRECT ACCESS DEVICE.

S737 – 14 – AN I/O ERROR OCCURRED READING A DSCB PREPARING FOR USER TRAILER LABEL PROCESSING.

S737 – 1C – AN I/O ERROR OCCURRED WHILE READING A FORMAT-3 DSCB.

S737-24 – DSN NOT FOUND. A MISSING MEMBER NAME WAS DETECTED BY BLDL WHILE SEARCHING FOR THE TTR OF A CONCATENATED MEMBER.

S737 – 2C – THE ERROR OCCURRED WHEN A FEOV MACRO WAS ISSUED WHILE ATTEMPTING TO WRITE A FILE MARK AT THE END OF DATA. THE DCBFDAD FIELD IN THE DCB INDICATED AN EXTENT NUMBER IN THE DEB GREATER THAN THE NUMBER OF EXTENTS IN THE DATASET. CONSEQUENTLY IT COULD NOT BE DETERMINED WHERE THE FILE MARK SHOULD HAVE BEEN WRITTEN.

S737 – 3C – THE FORMAT-1 DSCB NOT FOUND INSTALLATION EXIT MODULE ENCOUNTERED AN ERROR.

S738 – AN UNEXPECTED ERROR OCCURRED DURING THE EXECUTION OF AN ENQ MACRO. RELATED INFORMATION IS RECORDED IN SYS1.LOGREC.

S777 – DATA CHECK. TRANSMIT ON INPUT

S800 – AN ERROR OCCURRED WHEN EXCP ATTEMPTED TO FIX A PAGE FOR THIS EXCP REQUEST.

S804 – REQUEST FOR 0 BYTES OF VIRTUAL STORAGE OR NOT ENOUGH VIRTUAL STORAGE AVAILABLE FOR GETMAIN REQUEST.

– IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S804 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S804-RC)
POSSIBLE CAUSE:
PROGRAM EXCEEDED REGION SIZE

S804 – 04 – THERE IS NOT ENOUGH VIRTUAL SQA TO SATISFY THE REQUEST.

S804 – 08 – THERE IS NOT ENOUGH VIRTUAL CSA TO SATISFY THE REQUEST.

S804 – 0C – THERE IS NOT ENOUGH VIRTUAL LSQA TO SATISFY THE REQUEST.

S804 – 10 – THERE IS NOT ENOUGH PRIVATE AREA TO SATISFY THE REQUEST. MAY BE A V=R REGION BEFORE ITS INITIALIZATION HAS COMPLETED.

S804 – 1C – THERE IS NOT ENOUGH VIRTUAL LSQA FOR VSM’S CELLPOOL REQUIRED DURING THE REQUEST.

S805 – 1C – (1C IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S805) THERE IS NOT ENOUGH VIRTUAL LSQA FOR VSM’S CELLPOOL REQUIRED DURING THE FREEMAIN REQUEST.

S806 – BLDL DETECTED ERROR: MODULE NOT FOUND OR I/O ERROR DURING DIRECTORY SEARCH
POSSIBLE CAUSE
MISSING JOBLIB OR STEPLIB CARD
TRIED TO EXECUTE A NON-EXISTENT PROGRAM
TRIED TO EXECUTE IN BATCH A PROGRAM ASSEMBLED WITH ‘TEST’ OPTION
SYSIN DESCRIBED INCORRECTLY TO LKED OR NAME CARD MISSING

S806 – 04 – THE PROGRAM ENTRY POINT SPECIFIED WAS NOT FOUND IN THE INDICATED LIBRARY (PRIVATE LIBRARY, JOB LIBRARY, OR LINK LIBRARY).

S806 – 08 – AN UNCORRECTABLE INPUT/OUTPUT ERROR OCCURRED WHEN THE BLDL CONTROL PROGRAM ROUTINE ATTEMPTED TO SEARCH THE DIRECTORY OF THE LIBRARY THAT CONTAINED THE PROGRAM WHOSE ENTRY POINT WAS SPECIFIED. THIS CAN OCCUR IF THE INDICATED LIBRARY IS AN UNINITIALIZED PARTITIONED DATASET.

S806 – 0C – THE SUPERVISOR ATTEMPTED TO SEARCH A LIBRARY FOR THE SPECIFIED ENTRY POINT, BUT THE DCB OF THE LIBRARY WAS NOT OPEN.

S806 – 10 – AN EXPLICIT LOAD WAS ISSUED WITH NO DCB SPECIFIED.

S806 – 14 – AN SVC ROUTINE REQUIRED BY THE SYSTEM COULD NOT BE FOUND IN THE LINK PACK AREA.

S806 – 18 – AN SVC ROUTINE REQUIRED BY THE SYSTEM COULD NOT BE FOUND IN THE LINK PACK AREA BECAUSE THE DIRECTORY WAS NOT YET BUILT.

S806 – 1C – SPECIFIED DCB FOR ATTACH, LINK, LOAD, OR XCTL IS INCORRECT.

S80A – REQUEST FOR 0 BYTES OF VIRTUAL STORAGE OR NOT ENOUGH VIRTUAL STORAGE AVAILABLE FOR GETMAIN OR FREEMAIN REQUEST.

S80A – 04 – THERE IS NOT ENOUGH VIRTUAL SQA TO SATISFY THE REQUEST.

S80A – 08 – THERE IS NOT ENOUGH VIRTUAL CSA TO SATISFY THE REQUEST.

S80A – 0C – THERE IS NOT ENOUGH VIRTUAL LSQA TO SATISFY THE REQUEST.

S80A – 10 – THERE IS NOT ENOUGH PRIVATE AREA TO SATISFY THE REQUEST. MAY BE A V=R REGION BEFORE ITS INITIALIZATION HAS COMPLETED.

S80A – 1C – THERE IS NOT ENOUGH VIRTUAL LSQA FOR VSM’S CELLPOOL
REQUIRED DURING THE REQUEST.

S813 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S813)AN OPEN MACRO WAS ISSUED FOR A DATASET ON MAGNETIC TAPE, BUT THE DATASET NAME ON THE HEADER LABEL DID NOT MATCH THAT IN THE JFCB.

POSSIBLE CAUSE
WRONG DSNAME OR VOLUME SERIAL – JCL DISAGREES WITH LABEL
INCORRECT RECORD FORMAT OR BLOCK SIZE
THE REQUESTED DRIVE WAS NOT SWITCHED TO THIS MACHINE

S822 – A REGION REQUIRED TO RUN THE STEP COULD NOT BE OBTAINED. ONE OF THE FOLLOWING MESSAGES WILL BE WRITTEN TO THE PROGRAMMER, DEPENDING UPON WHETHER THE JOB WAS AN ORDINARY JOB OR A DEFERRED CHECKPOINT RESTART:
– IEF085I REGION UNAVAILABLE, ERROR CODE = CDE
– IEF186I REGION UNAVAILABLE FOR RESTART, ERROR CODE = CDE

S822 – 08 – IEF085I – A V=V REGION WAS REQUESTED AND A REGION SIZE WAS SPECIFIED WHICH WAS LARGER THAN THE PRIVATE AREA, OR A V=R REGION WAS REQUESTED AND A REGION SIZE GREATER THAN THE V=R AREA WAS SPECIFIED.

IEF186I – THE REGION PARAMETER WAS INCREASED SO THAT THE REGION COULD NOT BE ALLOCATED OR THE CONFIGURATION OF THE SYSTEM CHANGED SO THAT THE REGION COULD NOT BE OBTAINED:
– FOR ADDRSPC=REAL, THE SIZE OF THE REAL AREA WAS DECREASED.
– FOR ADDRSPC=VIRT, THE SIZE OF THE PRIVATE AREA DECREASED BECAUSE THE SIZE OF THE NUCLEUS INCREASED OR THE SIZE OF THE SQA OR THE IPA INCREASED.

S822 – 16 – IEF085I – A V=R AREA WAS REQUESTED, BUT EITHER LONG-FIXED OR DAMAGED PAGES IN THE V=R AREA MADE IT IMPOSSIBLE TO OBTAIN THE REQUESTED REGION, OR A V=R REGION WAS REQUESTED AND THERE WAS NOT ENOUGH SQA AVAILABLE FOR THE SYSTEM TO COMPLETE THE PROCESSING OF THE REQUEST.

IEF186I – IF A REAL REGION WAS REQUESTED, EITHER LONG-FIXED OR DAMAGED PAGES IN THE REAL AREA MADE IT IMPOSSIBLE TO OBTAIN THE REQUIRED REGION.

S822 – 20 – IEF085I AND IEF186I – EITHER A V=V OR V=R REGION WAS REQUESTED FRAGMENTATION BY LSQA, SWA, OR SUBPOOLS 229 OR 230 HAS MADE IT IMPOSSIBLE TO OBTAIN THE REQUESTED REGION.

S822 – 24 – IEF085I AND IEF186I – A REQUEST FOR A V=R REGION COULD NOT BE SATISFIED BECAUSE THE INSTALLATION GETPART EXIT ROUTINE REJECTED THE REQUEST.

S837 – THE ERROR OCCURRED DURING END OF VOLUME FOR A SEQUENTIAL DATA SET.

S837 – 04 – THE UNIT IS NOT CAPABLE OF HANDLING THE REQUESTED DENSITY.

S837 – 08 – THE VOLUME SERIAL NUMBER WAS NOT FOUND IN THE JFCB.
POSSIBLE CAUSES
VOLUME COUNT TO SMALL IN VOL PARAMETER OF DD STATEMENT
OPEN TYPE=J WAS USED TO CHANGE VOLUME SERIAL BUT NOT WRITTEN BACK

S837 – 0C – ANOTHER DATA SET ON THE VOLUME WAS IN USE.

S837 – 10 – THE DEVICE DOES NOT SUPPORT THE SELECTED RECORDING MODE.

S837 – 14 – THE TAPE VOLUME DOES NOT CONFORM TO THE SINGLE RECORDING MODE RULES. FOR INPUT, THE VIOLATION OCCURRED WHEN THE TAPE WAS WRITTEN WHEN THE RULES COULD NO
T BE ENFORCED. FOR OUTPUT,
THE ABEND PREVENTS ANY VIOLATION FROM HAPPENING.

S848 – NOT ENOUGH REGION. INCREASE THE REGION SIZE, ‘REGION=4096K’

S878 – REQUEST FOR 0 BYTES OF VIRTUAL STORAGE OR NOT ENOUGH VIRTUAL STORAGE AVAILABLE FOR GETMAIN OR FREEMAIN REQUEST.

S878 – 04 – THERE IS NOT ENOUGH VIRTUAL SQA TO SATISFY THE REQUEST.

S878 – 08 – THERE IS NOT ENOUGH VIRTUAL CSA TO SATISFY THE REQUEST.

S878 – 0C – THERE IS NOT ENOUGH VIRTUAL LSQA TO SATISFY THE REQUEST.

S878 – 10 – THERE IS NOT ENOUGH PRIVATE AREA TO SATISFY THE REQUEST. MAY BE A V=R REGION BEFORE ITS INITIALIZATION HAS COMPLETED.

S878 – 14 – A NEGATIVE STORAGE AMOUNT WAS SPECIFIED FOR A GETMAIN.

S878 – 18 – A NEGATIVE STORAGE AMOUNT WAS SPECIFIED FOR A FREEMAIN.

S878 – 1C – THERE IS NOT ENOUGH VIRTUAL LSQA FOR VSM’S CELLPOOL REQUIRED DURING THE REQUEST.

S905 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S905) AREA TO BE FREED BY FREEMAIN IS NOT ON A DOUBLEWORD BOUNDARY.

S90A – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S90A) THE ERROR OCCURRED DURING THE EXECUTION OF AN R-FORM FREEMAIN MACRO. THE ADDRESS OF THE STORAGE AREA TO BE RELEASED WAS NOT ON A DOUBLEWORD BOUNDARY (A MULTIPLE OF 8).

S913 – THE ERROR OCCURRED DURING:
1) THE EXECUTION OF AN OPEN MACRO OR DURING END-OF-VOLUME PROCESSING FOR A PASSWORD PROTECTED DATASET, OR 2) THE EXECUTION OF AN OPEN MACRO INVOLVING A CHECKPOINT DATASET

POSSIBLE CAUSE
OPERATOR FAILED TO SUPPLY CORRECT PASSWORD FOR PROTECTED DATASET
UNAUTHORIZED ATTEMPT TO USE LABEL=BLP
PREVIOUS DATASET ON THIS TAPE WAS PROTECTED, NEW DATASET IS NOT

S913 – 04 – AN OPEN MACRO WAS ISSUED FOR A MAGNETIC TAPE DATASET WITH AMERICAN NATIONAL STANDARD LABELS. THE VOLUME ACCESSABILITY BYTE (OFFSET X’0A’) IN THE VOLUME LABEL IS NOT BLANK. THIS INDICATES THE LABEL WAS NOT WRITTEN FOR USE ON AN IBM SYSTEM, OR THAT IT WAS WRITTEN BY THE USER. THE VOLUME MUST BE RECREATED.

S913 – 08 – AN OPEN MACRO WAS ISSUED FOR A MAGNETIC TAPE DATASET WITH AMERICAN NATIONAL STANDARD LABELS. THE SECURITY BYTE IN THE HEADER LABEL WAS NOT BLANK AND NOT EQUAL TO X’F1′. THIS MEANS THE LABEL EITHER WAS NOT CREATED ON AN IBM SYSTEM OR WAS CREATED BY THE USER. THE VOLUME MUST BE RECREATED FOR USE ON AN IBM SYSTEM.

S913 – 0C – AN OPEN MACRO WAS ISSUED FOR A PROTECTED DATASET FOR WHICH YOU ARE NOT ALLOWED THIS TYPE OF ACCESS.

S913 – 10 – AN OPEN MACRO WAS ISSUED TO THE VTOC FOR OUTPUT PROCESSING BY AN UNAUTHORIZED JOB STEP OR JOB-STEP TASK.

S913 – 14 – AN OPEN MACRO WAS ISSUED TO CONCATENATE CHECKPOINT AND NONCHECKPOINT DATASETS.

S913 – 18 – AN OPEN TYPE=J MACRO WAS ISSUED FOR A MAGNETIC TAPE VOLUME. THE JFCB WAS MODIFIED TO INDICATE LABEL=BLP (BYPASS LABEL PROCESSING) AN THE TASK WAS NOT AUTHORIZED. BLP MAY BE SPECIFIED IN THE JCL (IF THE INSTALLATION READER PROCEDURE ALLOWS IT), BUT THE JFCB MAY NOT BE MODIFIED TO INDICATE BLP UNLESS THE TASK IS
AUTHORIZED.

S913 – 1C – THE ERROR OCCURRED DURING THE EXECUTION OF AN OPEN TYPE=J MACRO TO A DIRECT ACCESS DEVICE DATASET. THE DATASET NAME SUPPLIED TO OPEN WAS NOT AVAILABLE TO THE JOB. EITHER THE DATASET WAS BEING
OPENED FOR INPUT AND SOME OTHER JOB HAD EXCLUSIVE CONTROL OF IT, OR THE DATASET WAS BEING OPENED FOR AN OPTION OTHER THAN INPUT (THUS REQUIRING EXCLUSIVE CONTROL) AND SOME OTHER JOB WAS USING THE DATASET.

S913 – 20 – AN OPEN MACRO USING THE EXCP ACCESS METHOD WAS ISSUED IN WHICH USER-WRITTEN APPENDAGES WERE REQUIRED. THE APPENDAGE NAMES WERE NOT INCLUDED IN THE PARMLIB MEMBER IEAAPP00, AND THE PROGRAM
ISSUING THE OPEN WAS NOT AUTHORIZED (BY APF OR PROTECT KEY).

S913 – 28 – AN OPEN MACRO WAS ISSUED FOR A CHECKPOINT DATASET. THE DATASET ORGANIZATION WAS NOT BPAM OR BSAM AND THE TASK WAS NOT AUTHORIZED VIA THE AUTHORIZED PROGRAM FACILITY (APF).

S913 – 2C – AN OPEN MACRO WAS ISSUED TO AN ISAM DATASET DEFINED BY TWO OR THREE DD STATEMENTS. EITHER THE DATASET NAMES CODED IN THE DD STATEMENTS WERE NOT ALL THE SAME, OR THE JFCB PASSED TO OPEN
(IF AN OPEN TYPE=J IS BEING USED) HAS A DATASET NAME DIFFERENT FROM THAT CODED IN THE DD STATEMENTS.

S913 – 30 – AN OPEN MACRO WAS ISSUED TO WRITE A DATASET ON A MAGNETIC TAPE CONTAINING ONE OR MORE PREVIOUS DATASETS. THE PROTECTION MODE OF THE DATASET TO BE WRITTEN WAS DIFFERENT THAN THE PROTECTION MODE OF THE PREVIOUS DATASET.

S913 – 34 – AT OPEN, THE CALLER IS NOT AUTHORIZED TO REJECT FOR INPUT.

S913 – 38 – AN OPEN WAS ISSUED FOR A RACF-PROTECTED DATA SET ON DASD OR A RACF-PROTECTED TAPE VOLUME TO WHICH THE CALLER WAS NOT AUTHORIZED.

S913 – 3C – AN OPEN WAS ISSUED FOR A RACF-INDICATED (RACF BIT ON IN THE FORMAT-1 DSCB IN THE VTOC) DATA SET, BUT THE DATA SET IS NOT DEFINED TO RACF.

S913 – 40 – A VSAM DATA SPACE BEING OPENED IS RACF-DEFINED.

S913 – 44 – INVALID SPECIFICATION OF PROTECT – THE TAPE VOLUME WAS ALREADY RACF-PROTECTED.

S913 – 48 – INVALID SPECIFICATION OF PROTECT – THE SYSTEM TAPE OPTION IS NOT IN EFFECT.

S913 – 4C – INVALID SPECIFICATION OF PROTECT – THE USER IS NOT DEFINED TO RACF.

S913 – 50 – INVALID SPECIFICATION OF PROTECT – THE REQUEST IS FOR A NL, BLP OR LTM TAPE.

S913 – 54 – INVALID SPECIFICATION OF PROTECT – THE REQUEST IS FOR INPUT OR INOUT.

S913 – 58 – INVALID SPECIFICATION OF PROTECT – THE VOLUME SEQUENCE NUMBER OR THE FILE SEQUENCE NUMBER IS NOT EQUAL TO ONE ON A AL, SUL, AL OR AUL TAPE, OR THE TAPE IS BEING OPENED WITH DISP=MOD (INCLUDING OPEN OPTIONS OUTINX AND EXTEND).

S913 – 5C – INVALID SPECIFICATION OF PROTECT – THE VOLUME BEING USED IS A PUBLIC VOLUME.

S913 – 60 – THE USER IS NOT AUTHORIZED TO DEFINE A DATA SET WITH THE SPECIFIED NAME. THIS NAME AND FILE SEQUENCE INDICATOR DO NOT MATCH THE CORRESPONDING NAMES IN THE TVTOC (TAPE VTOC).

S913 – 64 – THE USER IS NOT AUTHORIZED TO SPECIFY BLP.

S913 – 68 – THE USER IS NOT AUTHORIZED TO ADD A DATA SET TO THE VOLUME.

S913 – 6C – PROTECT WAS NOT SPECIFIED IN THE JCL. THE USER IS NOT AUTHORIZED TO DEFINE A DATASET PROTECTED BY A GENERIC PROFILE.

S913 – 70 – THE USER HAS RACF EXECUTE ACCESS ONLY AND ONE OF THE FOLLOWING REQUIREMENTS WAS VIOLATED:
– THE CALLER MUST BE IN SUPERVISOR STATE OR THE DATA SET MUST BE A PDS.
– THE ACCESS METHOD MUST NOT BE EXCP.

S913 – 72 – AN UNEXPECTED RETURN CODE HAS BEEN RETURNED FROM RACF.

S922 – SPECIFIED MU TIME EXCEEDED

S978 – 04 – (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S978) AREA TO BE FREED BY FREEMAIN IS NOT ON A DOUBLEWORD BOUNDARY.

S2333 – DB2 TABLE TIMESTAMP MISMATCH

ATUALIZANDO

SB37-04 – NOT ENOUGH SPACE WAS ALLOCATED

SD37 – OUTPUT DSN USED ALL PRIMARY SPACE

SA13-14 – END OF FILE MARK DATASET NOT ON TAPE

SE37 – ALL SPACE USED ON CURRENT VOLUME. SPECIFY MORE VOLUMES


JCLI – SYNTAX, DATASET NOT FOUND JCL – SYNTAX, DATASET NOT FOUND, SPACE, DUPLICATE NAME, CONTENTION COULD BE ANYTHING

07D5 – I/O ERROR

2001 – CONTENTION

2005 – I/O ERROR

2004 – BAD DATA(07D)

2016 – EMPTY GENERATIONS

0406

44004 – SQL

013 – OPEN ERROR

028 – PAGING I/O ERROR

052-084 – INVALID CHARACTER ID

076-002 – UNABLE TO OPEN DATASET

072-053 – UNABLE TO OPEN DDNAME


0CX – PROGRAM CHECK EXCEPTIONS:

0C1 – OPERATION,

OC4 – PROTECTION/ADDRESSING,

0C5 – ADDRESSING,

0C6 – SPECIFICATION,

0C7 – DATA


706 – NON-EXECUTABLE PROGRAM

804 – INSUFFICIENT VIRTUAL STORAGE

806 – UNABLE TO LOAD (LINK ETC) PROGRAM

80A – INSUFFICIENT VIRTUAL STORAGE

852 – BAD DATA

878
INSUFFICIENT VIRTUAL STORAGE

998 – POSSIBLE CONTENTION, TABLESPACE IN USE

737 – I/O ERROR

A14 – I/O ERROR

B37 – INSUFFICIENT DASD SPACE ON SEQUENTIAL DATASET

D37 – INSUFFICIENT DASD SPACE – NO SECONDARY SPACE ALLOCATED

E37 – INSUFFICIENT DASD SPACE ON PARTITIONED DATASET


SQL Abends

SQLCODE= -104 – ILLEGAL SYMBOL, ILLEGAL TOKEN IN SQL STATEMENT

SQLCODE= -110 – EMPTY TABLE, BAD QUERY

SQLCODE= -180 – THE STRING REPRESENTATION OF A DATETIME VALUE BAD DATA HAS INVALID SYNTAX

SQLCODE= -181 – THE STRING REPRESENTATION OF A DATETIME VALUE IS BAD DATA NOT A VALID DATETIME VALUE

SQLCODE= -204 – UNDEFINED TABLE NAME – TABLE NAME DOESN’T EXIST UNDEFINED ALIAS – ALIAS DOES NOT EXIST

SQLCODE= -305 – THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT BECAUSE NO INDICATOR VARIABLE IS SPECIFIED

SQLCODE= -501 – CURSOR IS CLOSED DUE TO PREVIOUS CONDITIONS

SQLCODE= -551 – DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION DROP ALIAS ON OBJECT

SQLCODE= -556 – CANNOT HAVE THE EXECUTE PRIVILEGE, REVOKED BY DB2DBA BECAUSE THE REVOKEE DOES NOT POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT

SQLCODE= -562 – A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM THE GRANTOR

SQLCODE= -626 – THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE PAGE SET IS NOT STOPPED – CALL DBA

SQLCODE= -803 – DATA PROBLEM – MAY BE BAD PART NUMBER COULD BE DUPLICATE VALUES IN EXISTING ROW

SQLCODE= -805 – BIND PROBLEM

SQLCODE= -811 – ERROR ON SQL TABLE

SQLCODE= -818 – LOAD MODULE AND DBR MODULE OUT OF SYNCH NEED TO DO BIND REPLACE OR REBIND

SQLCODE= -904 – CONTENTION

SQLCODE= -911 – CONTENTION

SQLCODE= -922 – TIME STAMP PROBLEM AFTER REBIND

SQLCODE= -923 – DB2 ERROR – SOME DB2 COMPONENT NOT AVAILABLE

SQLCODE= -924 – SUBSYSTEM NOT AVAIALABLE, CONTENTION IN DATABASE


ONCODE=9 – DATA PROBLEM

ONCODE=22 – LENGTH OF RECORD VARIABLE GREATER THAN RECORD LENGTH

ONCODE=0084 – UNDEFINED FILE CONDITION RAISE

ONCODE=1040 – SPACE PROBLEM

ONCODE=3920 – STORAGE PROBLEM

ONCODE=8094 – PROTECTION EXCEPTION – CAUSED BY BAD COMPILE – CALL ADM, B37(SPACE PROBLEM)

ONCODE=8097 – BAD DATA, DATA EXCEPTION

ONCODE=9050 – BAD DATA


‘INVALID’, ‘ERROR’, ‘RESOURCE NOT AVAILABLE’, ‘PROGRAM NOT FOUND’, ‘INVALID RECORD LENGTH’, ‘FAILED’, ‘UTILITY NOT COMPATIBLE’, ‘DOES NOT MATCH’, ‘DUPLICATE’, ‘DATASET ALREADY USED’

DUPLICATE DATASET NAME – EITHER THE PROGRAM CONTAINS TWO DATASETS WITH THE SAME NAME, OR A DELETE UNCATALOG STEP IS NOT WORKING

‘DUPLICATE UTILITY’ AND ‘EMPTY DATASET’

EQC – EQUIPMENT CHECK

FBI – FAILED BY INITIATOR – CHECK THE JCL FOR THE CAUSE OF THE ABEND

PROTECTION EXCEPTION – CAUSED BY A BAD COMPILE. CONTACT A PROGRAMMER

OPEN – MESSAGE STATES THAT DATASETS ARE OPEN

SEQ – TAPE DRIVE PROBLEM

UNABLE TO ALLOCATE SORTWORK SPACE – NO SORTWORK SPACE AVAILABLE. WAIT
A LITTLE WHILE UNTIL SOME JOBS FINISH PROCESSING AND THEN RESUBMIT THE
JOBS.

WRONG PASSWORD OR ACCESS NOT ALLOWED – MEANS THAT THE JOB HAS NOT A SECURITY (ACF,RACF) RULE TO EXECUTE ON THAT SCHEDULLING TOOL OR FOR ONE DATASET, ETC.


REASON CODE 00E30083 – DEADLOCK – CONTENTION

REASON CODE 00D70024 – RESOURCE UNAVAILABLE

REASON CODE 00E40034 – STORAGE UNAVAILABLE

REASON CODE 1008 – FTP LINE DOWN

REASON CODE OOE40034 – STORAGE PROBLEM – NOT ENOUGH STORAGE

SIM – PROBLEM WITH DRIVE OR TAPE, I/O ERROR

JCL – ENVIRONMENT CHANGED. NOW UNABLE TO ALLOCATE

One thought on “Abend Codes and explanation

  1. SQLCODE= -904 – CONTENTION

    what it means? Freshers wil unable understand this type of errors so mention with clarity

Leave a Reply

Your email address will not be published. Required fields are marked *

eight − six =