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 NAME 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 SPECIFIC 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 OPEN 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/VTAM 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
- 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 PREVIOUSLY 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. ONLY 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
BY AN ENQ MACRO. THAT IS, THE PROGRAM HAD NOT REQUESTED CONTROL
OF A RESOURCE IT WAS ATTEMPTING TO RELEASE.
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 - I/O ERROR READING EOF ON MAGNETIC TAPE
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 - 18 - DATASET NOT FOUND ON VOLUME
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
S222 - JOB CANCELLED
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
S306 - INSUFFICIENT ACCESS AUTHORITY
S30E - BAD DATA(CHECK ONCODE),CONTENTION
S311 - I/O ERROR READING HEADER LABELS FOR A DATASET
S322 - TIMED OUT, POSSIBLY NO TIME PARAMETER OR OTHER INFO MISSING
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 -
S413 - 18 - UTPROC=RESTART DID NOT WORK
S413 - 20 - I/O ERROR READING VOLUME LABEL ON A DASD VOLUME
S413 - 34 - NO REFERBACK, NO LABEL
S522 - TIMED OUT - TAPE NOT MOUNTED, HSM RECALL
S546 - CANCELLED BY OPERATOR OR SYSTEM
S567 - HARDWARE ERROR - BLOCK OF DATA MISSED OR SKIPPED
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
S637 - OC - CONCATENATION ON UNLIKE ATTRIBUTES
S637 - 2C - I/O ERROR READING HEADER LABEL ON TAPE
S637 - 34 - I/O ERROR READING END OF VOLUME LABEL
S706 - A LOAD MODULE MARKED FOR THE LINKAGE EDITOR IS NON-EXECUTABLE
S714 - BAD TAPE OR TAPE DRIVE
S714 - 0C - BAD TAPE DRIVES
S718 - NOT ENOUGH REGION TO LOAD MODULES
S722 - LINES EXCEEDED, ADD A MAIN LINES CARD - //*MAIN LINES=(100,WARNING)
S737 - 24 - DSN NOT FOUND
S777 - DATA CHECK. TRANSMIT ON INPUT
S806 - PROGRAM NOT FOUND IN LIBRARY, CONTENTION, NO DATA TRANSMITTED
S813 - 04 - I/O ERROR READING HEADER LABEL ON TAPE
S822 - REGION REQUESTED/REQUIRED COULD NOT BE OBTAINED
S837 - SPACE PROBLEM WITH OUTPUT DATASET, VOL SER COUNT TOO LOW 'VOL=(,,,10)'
S848 - NOT ENOUGH REGION. INCREASE THE REGION SIZE, 'REGION=4096K'
S878 - NOT ENOUGH REGION. INCREASE THE REGION SIZE, 'REGION=4096K' OR DECREASE REGION=4M(SAME AS REGION=4096K) REGION=0M ALL STORAGE AVAILABE BELOW THE LINE
S878 - 10 - GETMAIN PROBLEM - INSUFFICIENT STORAGE
S913 - INSUFFICIENT ACCESS AUTHORITY(RACF)
S922 - SPECIFIED MU TIME EXCEEDED
S2333 - DB2 TABLE TIMESTAMP MISMATCH
SB37 - 04 - NOT ENOUGH SPACE WAS ALLOCATED
SD37 - OUTPUT DSN USED ALL PRIMARY SPACE
SA13 - 14 - END OF FILE MARK DATASET NOT ON TAPE
S0C4 - ENTRY NOT FOUND
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
No hay comentarios:
Publicar un comentario