MAINFRAME ABEND CODES and DETAILS - All in one

MAINFRAME

A one-stop Reference Document by

Ramkumar. S

Mainframe – Abend Codes and Details

Page 1

7/30/2008

CONTENTS: 

SQL CODES



COBOL / VSAM FILE-STATUS CODES



IMS ERROR CODES



PL/1 ONCODES



SYSTEM ABEND CODES



MORE DETAILS on SYSTEM ABEND CODES



MORE DETAILS on USER ABEND CODES


Page 2

7/30/2008

SQL CODES Successful Execution SQLCODE: 000

SUCCESSFUL EXECUTION

Warning SQLCODES: +100

ROW NOT FOUND FOR FETCH, UPDATE OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE

+162

TABLE SPACE

+304

A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION position-number WITH DATA TYPE data-type2

+402

LOCATION location IS UNKNOWN

+403

THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST

+558

THE WITH GRANT OPTION IS IGNORED BECAUSE GRANT IS TO PUBLIC

+560

THE WITH GRANT OPTION IS IGNORED FOR UPDATE (COLUMN-LIST)

+561

THE ALTER AND INDEX PRIVILEGES CANNOT BE GRANTED TO “PUBLIC AT ALL LOCATIONS”

+625

THE DEFINITION OF TABLE table-name HAS BEEN CHANGED TO INCOMPLETE

+802

EXCEPTION ERROR exception-type HAS OCCURRED DURING operation-type OPERATION ON data-type DATA, POSITION positionnumber.

database-name, tablespace-name HAS BEEN PLACED IN CHECK PENDING

Error SQLCODES: -007

STATEMENT CONTAINS THE ILLEGAL CHARACTER character

-010

THE STRING CONSTANT BEGINNING string IS NOT TERMINATED

-060

INVALID type SPECIFICATION: spec

-084

UNACCEPTABLE SQL STATEMENT

-101

THE STATEMENT IS TOO LONG OR TOO COMPLEX

-102

THE LENGTH OF THE STRING CONSTANT BEGINNING string IS GREATER THAN 254 CHARACTERS OR 124GRAPHIC CHARACTERS

-103

literal IS AN INVALID NUMERIC LITERAL

-104

ILLEGAL SYMBOL token VALID SYMBOLS ARE token-list

-105

INVALID STRING

-107

THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS size

-109

clause CLAUSE IS NOT PERMITTED

-110

INVALID HEXADECIMAL LITERAL BEGINNING string

-111

A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME

-112

THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN FUNCTION OR DISTINCT FOLLOWED BY AN EXPRESSION

-113

INVALID CHARACTER FOUND IN NAME: name

-115

A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR operator IS FOLLOWED BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY

-117

THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NEMBER OF OBJECT COLUMNS

-118

THE OBJECT TABLE OR VIEW OF THE INSERT, DELETE, OR UPDATE STATEMENT IS ALSO INDENTIFIED IN A FROM CLAUSE

-119

A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY CLAUSE

-120

A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN FUNCTION OR A WHERE CLAUSE REFERENCES A COLUMN [columnname] WHICH IS DERIVED FROM A COLUMN FUNCTION OR EXPRESSION IN A VIEW DEFINITION

-121

THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE STATEMENT

-122

A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE

-125

AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT

-126

THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE


Page 3

7/30/2008

-127

DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT

-128

INVALID USE OF NULL IN A PREDICATE

-129

THE STATEMENT CONTAINS TOO MANY TABLE NAMES

-131

STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES

-132

A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A COLUMN OR THE SECOND OPERAND IS NOT A STRING

-133

A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE IT INCLUDES AN EXPRESSION THAT APPLIES AN OPERATIOR TO A CORRELATED REFERENCE

-134

IMPROPER USE OF LONG STRING COLUMN column-name OR A HOST VARIABLE OF MAXIMUM LENGTH GREATER THAN 254

-136

SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES

-137

RESULT OF CONCATENATION TOO LONG

-138

THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE

-150

THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED

-151

THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN column-name INDICATES THAT IT CANNOT BE UPDATED

-153

THE CREATE VIEW STATEMENT DOES NOT INCLUDE A REQUIRED COLUMN LIST

-154

THE CREATE VIEW FAILED BECAUSE THE VIEW DEFINITION CONTAINS A UNION, A UNION ALL, OR A REMOTE OBJECT

-156

THE STATEMENT DOES NOT IDENTIFY A TABLE

-157

ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. Object-name IS NOT THE NAME OF A TABLE

-158

THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE

-159

DROP OR COMMENT ON token IDENTIFIES A(N) token RATHER THAN A(N) token

-160

THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW

-172

function-name IS NOT A VALID FUNCTION NAME

-180

THE STRING REPRESENTATION OF DATETIME VALUE HAS INVALID SYNTAX

-181

THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID VALUE

-182

AN ARITHMETIC EXPRESSION WITH DATETIME VALUE IS INVALID

-183

AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN VALID RANGE OF DATES

-184

AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARAKER

-185

THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED

-186

THE LOCAL DATE OR TIME LENGTH HAS BEEN INCREASED AND EXECUTING PROGRAM RELIES ON OLD LENGTH

-187

A REFERENCE TO A CURRENT DATE/TIME SPECIAL REGISTER IS INVALID BECAUSE THE MVS TOO CLOCT IS BAD OR THE MVS PARMTE IS OUT OF RANGE

-198

THE OPERAND OF THE PREPARE OF THE EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY

-199

ILLEGAL USE OF KEYWORD keyword, TOKEN token-list WAS EXPECTED

-203

A REFERENCE TO COLUMN col-name IS AMBIGOUS

-204

name IS AN UNQUALIFIED NAME

-205

column-name IS NOT A COLUMN OF TABLE table-name

-206

column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE OR ANY TABLE IDENTIFIED IN THE FROM CLAUSE

-207

ORDER BY CLAUSE IS INVALID BECAUSE IT INCLUDES A COLUMN NAME BUT IT APPLIES TO RESULT OF A UNION OR UNION ALL

-208

THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN col-name IS NOT PART OF THE RESULT TABLE

-219

THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST

-220

THE COLUMN NAME col-name IN EXPALANATION TABLE table-name IS NOT DEFINED PROPERLY

-301

THE VALUE OF THE INPUT HOST VARIABLE NUMBER position-num CANNOT BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE

-302

THE VALUE OF INPUT VARIBLE NUMBER position-num IS TOO LARGE TO THE TARGET COLUMN


Page 4

7/30/2008

-303

VALUE CANNOT BE ASSIGNED TO THE OUTPUT HOST VARIABLE NUMBER position-num BECAUSE DATA TYPES ARE NOT COMPARABLE

-304

A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN RANGE OF HOST VARIABLE IN POSITION posit-num WITH DATATYPE data-type2

-305

THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER posit-num BECAUSE NO INDICATOR VARIABLE IS SPECIFIED

-309

A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLEHAS THE NULL VALUE

-312

UNDEFINED OR UNUSABLE HOST VARIABLE variable-name

-313

THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS

-401

THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE

-402

AN ARITHMETIC FUNCTION OR OPERATOR arith-top IS APPLIED TO CHARACTER OR DATETIME DATA

-404

THE UPDATE OR INSERT STATEMENT SPECIFIES A STRING THAT IS TOO LONG column-name

-405

THE NUMERIC LITERAL literal CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE

-406

A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN

-407

AN UPDATE OR INSERT VALUE IS NULL BUT THE OBJECT COLUMN column name CANNOT CONTAIN NULL VALUES

-408

AN UPDATE OR INSERT VALUE IS NOT COMPARABLE WITH THE DATA TYPE OF ITS OBJECT COLUMN column name

-409

INVALID OPERAND OF A COUNT FUNCTION

-410

THE FLOATING POINT LITERAL literal CONTAINS MORE THAN 30 CHARACTERS

-411

THE CURRENT DATETIME, CURRENT SQLID OR USER KEYWORD CANNOT BE USED AS SPECIFIED

-412

THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS

-414

THE NUMERIC OR DATETIME COLUMN column-name IS SPECIFIED IN A LIKE PREDICATE

-415

THE CORRESPONDING COLUMNS, column-number, OF THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE COMPARABLE COLUMN DESCRIPTIONS

-416

AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN

-417

A STATEMENT STRING TO BE PREPARED INCLUDES PARAMENTER MARKERS AS THE OPERANDS, THE SAME OPERATOR

-418

STATEMENT STRING TO BE PREPARED OR AN EXECUTE IMMEDIATE STMNT CONTAINS INVALID US OF PARM MARKERS

-419

DECIMAL DIVIDE OPERATION IS INVALID BECAUSE RESULT WOULD HAVE A NEGATIVE SCALE

-421

THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS

-501

CURSOR INDENTIFIED IN FETCH OR CLOSE IS NOT OPEN

-502

CURSOR IDENTIFIED IN OPEN IS ALREADY OPEN

-503

A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR

-504

THE CURSOR NAME cursor-name IS NOT DEFINED

-507

THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN

-508

THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON A ROW

-509

THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLE DESIGNATED BY THE CURSOR

-510

THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE STATEMENT CANNOT BE MODIFIED

-511

THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE TABLE DESIGNATED BY THE CURSOR CANNOT BE MODIFIED

-514

THE CURSOR cursor-name IS NOT IN A PREPARED STATE

-516

THE DESCRIBE STATEMENT DOES NOT IDENTIFY A PREPARED STATEMENT

-517

CURSOR cursor-name CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY A PREPARED SELECT STATEMENT

-518

THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT

-519

THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSOR cursor-name

-530

THE INSERT OR UPDATE VALUE OF FOREIGN DEY constraint-name IS INVALID

-531

THE PRIMARY KEY IN A PARENT ROW CANNOT BE UPDATED BECAUSE IT HAS ONE OR MORE DEPENDENT ROWS IN A RELATIONSHIP constraint-name


Page 5

7/30/2008

-532

THE RELATIONSHIP constraint-name RESTRICTS THE DELETION OF ROW WITH RIX X ‘rid-number’

-533

INVALID MULTIPLE-ROW INSERT

-534

THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-ROW UPDATE

-535

INVALID UPDATE OR DELETE WITH WHERE CURRENT OF

-536

THE DELETE STATEMENT IS INVALID BECAUSE TABLE table-name CAN BE AFFECTED BY THE OPERATION

-537

THE PRIMARY KEY OR FOREIGN KEY CLAUSE IDENTIFIES COLUMN column-name MORE THEN ONCE

-538

FOREIGN KEY name DOES NOT CONFORM TO THE DESCRIPTION OF THE PRIMARY KEY OF TABLE table- name

-539

TABLE table-name DOES NOT HAVE A PRIMARY KEY

-540

THE DEFINITION OF TABLE table-name IS INCOMPLETE BECAUSE IT DOES NOT HAVE A PRIMARY INDEX

-541

FOREIGN KEY name IS INVALID BECAUSE IT IS A DUPLICATE REFERENTIAL CONSTRAINT

-542

column-name CANNOT BE A COLUMN OF A PRIMARY KEY BECAUSE IT CAN CONTAIN NULL VALUES

-551

auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation ON OBJECT object-name

-552

auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation

-553

auth-id SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS

-554

AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF

-555

AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM ITSELF

-556

A PRIVILEGE CANNOT BE REVOKED BECAUSE IT IS NOT POSSESSED BY authorization ID

-557

INCONSISTENT GRANT/REVOKE KEYWORD keyword. PERMITTED KEYWORDS ARE keyword-list

-558

INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR REVOKE

-559

ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED

-571

THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE

-601

THE NAME OF THE OBJECT TO BE CREATED IS IDENTICAL TO THE EXISTING NAME name OF THE OBJECT TYPE obj-type

-602

TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX

-603

A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS

-604

A COLUMN DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE

-607

OPERATION operation IS NOT DEFINED FOR SYSTEM TABLES

-612

column-name IS A DUPLICATE COLUMN NAME

-613

THE PRIMARY KEY IS TOO LONG OR HAS TOO MANY COLUMNS

-614

THE INDEX CANNOT BE CREATED BECAUSE THE SUM OF THE INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS IS GREATER THAN THE ALLOWABLE MAXIMUM

-616

obj-type1 obj-name1 CANNOT BE DROPPED BECAUSE IT IS REFERENCED BY obj-type2 obj-name2\

-618

OPERATION operation IS NOT ALLOWED ON SYSTEM DATA BASES

-619

OPERATION DISALLOWED BECAUSE THE WORKFILE DATA BASE IS NOT STOPPED

-620

KEYWORD keyword IN stmt type STATEMENT IS NOT PERMITTED FOR A TABLESPACE IN THE WORKFILE DATABASE

-621

DUPLICATE DBID dbid WAS DETECTED AND PREVIOUSLY ASSIGNED TO database-name

-623

A CLUSTERING INDEX ALREADY EXISTS ON TABLE table-name

-624

TABLE table-name ALREADY HAS A PRIMARY KEY

-625

TABLE table-name DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PRIMARY KEY

-626

THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGESET IS NOT STOPPED

-627

THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS USER-NANAGED DATA SETS

-628

A SEGMENTED TABLESPACE MAY NOT BE PARTITIONED

-629

SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY NAME CANNOT CONTAIN NULL VALUES

-631

FOREIGN DEY NAME IS TOO LONG OR HAS TOO MANY COLUMNS


Page 6

7/30/2008

-632

THE TABLE CANNOT BE DEFINED AS DEPENDENT OF table-name BECAUSE OF DELETE RULE RESTRICTIONS

-633

THE DELETE RULE MUST BE delete-rule

-634

THE DELETE RULE MUST NOT BE CASCADE

-635

THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL

-636

THE PARTITIONING KEYS ARE NOT SPECIFIED IN ASCENDING OR DESCENDING ORDER

-637

DUPLICATE keyword KEYWORD

-638

TABLE table-name CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING

-639

A NULLABLE COLUMN OF A FOREIGN DEY WITH A DELETE RULE OF SET NULL NCANNOT BE A COLUMN OF THE DEY OF A PARTITIONED INDEX

-644

INVALID VALUE SPECIFIED FOR KEYWORD keyword IN STMT-TYPE STATEMENT

-646

TABLE table-name CANNOT BE CREATED IN PARTITIONED/DEFAULT TABLESPACE tspace-name BECAUSE IT ALREADY CONTAINS A TABLE

-647

BUFFERPOOL bp-name CANNOT BE SPECIFIED BECAUSE IT HAS NOT BEEN ACTIVATED

-652

VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE proc-name

-653

TABLE table-name IN PARTITIONED TABLESPACE tspace-name IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED

-660

INDEX index-name CANNOT BE CREATED ON PARTITIONEDTABLESPACE space-name BECAUSE KEY LIMITS ARE NOT SPECIFIED

-661

INDEX index-name CANNOT BE CREATED ON PARTITIONED TABLESPACE tspace-name BECAUSE THE NUMBER OF PART SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS OF THE TABLESPACE

-662

A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED TABLESPACE tspace-name

-663

THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO OR GREATER THAN THE NUMBER OF COLUMNS IN THE KEY OF INDEX index-name

-664

THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE PARTITIONED INDEX index-name EXCEEDS THE LENGTH IMPOSED BY THE INDEX MANAGER

-665

THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID

-666

stmt-verb object CANNOT BE EXECUTED BECAUSE function IS IN PROGRESS

-667

THE CLUSTERING INDEX FOR A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED

-668

THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE

-669

A TABLE IN A PARTITIONED TABLESPACE CANNOT BE EXPLICITLY DROPPED

-670

THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT

-671

THE BUFFERPOOL ATTRIBUTE OF THE TABLESPACE CANNOT BE ALTERED AS SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLESPACE

-676

A 32K PAGE BUFFERPOOL MAY NOT BE USED FOR AN INDEX

-677

INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION

-678

THE LITERAL literal SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM TO THE DATA TYPE data-type OF THE CORRESPONDING COLUMN column-name

-679

THE OBJECT name CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJECT

-680

TOO MANY COLUMNS SPECIFIED FOR A TABLE

-681

COLUMN column-name IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE RT: return-code RS: reason-code, MSG: message-token

-682

FIELD PROCEDURE procedure-name COULD NOT BE LOADED

-683

INVALID COLUMN TYPE FOR FIELDPROC OR BIT DATA OPTION, COLUMN-NAME

-684

THE LENGTH OF LITERAL LIST BEGINNING string IS TOO LONG

-685

INVALID FIELD TYPE, column-name

-686

COLUMN DEFINED WITH A FIELD PROCEDURE CANNOT COMPARE WITH ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE

-687

FIELD TYPES INCOMPARABLE

-688

INCORRECT DATA RETURNED FROM FIELD PROCEDURE, column-name, msgno

-802

EXCEPTION ERROR ‘exception-type’ HAS OCCURRED DURING ‘operation-type’ OPERATION ON ‘data-type’ DATA, POSITION ‘position-number’


Page 7

7/30/2008

-803

AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE INDEX index-name CONSTRAINS COLUMNS OF THE TABLE SUCH THAT NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS RID OF EXISTINGF ROW IS X’rid’

-804

AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT

-805

PROGRAM NAME program-name NOT FOUND IN PLAN plan-name

-811

THE RESULT OF AN EMBEDDED SELECT STATEMENT IS A TABLE OF MORE THAN ONE ROW OR THE RESULT OF THE SUBQUERY OF A BASIC PREDICATE IS NORE THAN ONE VALUE

-815

A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY SPECIFIED IN AN EMBEDDED SELECT STATEMENT OR A SUBQUERY OF A BASIC PREDICATE

-817

THE INSERT, UPDATE, DELETE, DDL, OR AUTHORIZATION STATEMENT CANNOT BE EXECUTED BECAUSE THE IMS/VS TRANSACTION IS INQUIRY ONLY

-818

THE PRECOMPLIER-GENERATED TIMESTAMP x IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP y BUILT FROM THE DBRM

-819

THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS PARSE TREE IN THE CATALOG IS ZERO

-820

THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE catalog-table CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE

-822

THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VARIABLE ADDRESS

-840

TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST

-901

UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS

-904

UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE, REASON reason-code, TYPE OF RESOURCE resourcetype, AND RESOURCE NAME resource-name

-905

UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED, RESOURCE NAME = resource name LIMIT = limitamount1 CPU SECONDS (limit-amount2 SERVICE UNITS) DERIVED FROM limit-source

-906

THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS DISABLED DUE TO A PRIOR ERROR

-907

UNABLE TO DETERMINE IF THE ATTEMPT TO COMMIT UPDATES MADE AT A REMOTE SITE WAS SUCCESSFUL OR NOT

-909

THE OBJECT HAS BEEN DELETED

-910

THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP OR ALTER IS PENDING

-911

THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT, REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name

-913

UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT, REASON CODE reason-code, TYPE OF RESOURCE resourcetype, AND RESOURCE NAME resource-name

-922

CONNECTION AUTHORIZATION FAILURE error-type ERROR

-923

CONNECTION NOT ESTABLISED DB2 condition REASON reason-code, TYPE resource-type, NAME resource-name

-924

DB2 CONNECTION INTERNAL ERROR, function-code, return-code, reason-code

-925

COMMIT NOT VALID IN IMS/VS OR CICS ENVIRONMENT

-927

THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING ENVIRONMENT WAS NOT ESTABLISHED THE PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND


Page 8

7/30/2008

COBOL / VSAM FILE-STATUS CODES RC

EXPLANATION Successful completion

0 1, 2

The record has been processed with duplicate Alternate record key

4

A read statement has been successfully completed, but length of the record does not conform to the file description specification.

5

OPEN – Optional File is not present

10

Unsuccessful completion. A sequential read statement has been attempted, but there are no more input records.

14

A sequential READ statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file.

15

CICS EIBCODE Indicating Duplicate (Alternate) Index

21

A sequence error exists for a sequentially accessed indexed file. The prime record key value has been changed by the program between the successful execution of a READ statement and the execution of next REWRITE statement for that file, or the ascending requirements for successive record key values were violated.

22

An attempt was made to write a record that would create a duplicate key in a relative file; or an attempt was made to write or rewrite a record that would create a duplicate prime record key or a duplicate alternate record key without the DUPLICATES phrase in an indexed file. This key value applies to an indexed file in which the alternate key has been declared ‘UNIQUE’

23

An attempt was made to randomly access a record that does not exist in the file or a START or random READ statement was attempted on an optional input file that was not present.

24

An attempt was made to write beyond the externally defined boundaries of a relative or indexed file. Or, a sequential WRITE statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file.

30

A permanent data error has occurred (this is a hardware problem)

34

A permanent error exists because of a boundary violation; an attempt was made to write beyond the externally defined boundaries of a sequential file.

35

An OPEN statement with the INPUT, I-O, or EXTEND phrase was attempted on a non-optional file that was not present

37

An OPEN statement was attempted on a file that would not support the open mode specified in the OPEN statement. Possible violations are : The EXTEND or OUTPUT phrase was specified but the file would not support write operations. The I-O phrase was specified but the file would not support the input and output operations permitted. The INPUT phrase was specified but the file would not support read operations. Under VSE, the EXTEND phrase was specified for a SAM file.

38

An OPEN statement was attempted on a file previously closed with lock.

39

The OPEN statement was unsuccessful because a conflict was detected between the fixed file attributes and the attributes specified for that file in the program. These attributes include the organization of the file (Sequential, Relative or Indexed), the prime record key, the code set, the maximum record size, the record type (fixed or variable), and the blocking factor.

41

An OPEN statement was attempted for a file in the open mode.

42

A CLOSE statement was attempted for a file not in the open mode.

43

For a mass storage file in the sequential access mode, the last input-output statement executed for the associated file prior to the execution of a REWRITE statement was not a successfully executed READ statement.

For relative and indexed files in the sequential access mode, the last input-output statement executed for the file prior to the execution of a DELETE or REWRITE statement was not a successfully executed READ statement.

44

A boundary violation exists because an attempt was made to rewrite a record to a file and the record was


Page 9

7/30/2008

not the same size as the record being replaced, or an attempt was made to write or rewrite a record that was larger than the largest or smaller than the smallest record allowed by the RECORD IS VARYING clause of the associated file-name.

46

A sequential READ statement was attempted on a file open in the input or I-O mode and no valid next record had been established because : The preceding READ statement was unsuccessful but did not cause an at end condition. The preceding statement caused an at end condition.

47

The execution of a READ statement was attempted on a file not open in the input or I-O mode.

48

The execution of a WRITE statement was attempted on a file not open in the I-O, OUTPUT, or EXTEND mode.

49

The execution of a DELETE or REWRITE statement was attempted on a file not open in the I-O mode.

90

No further information.

91

For VSAM only: Password failure.

92

Logic error.

93

For VSAM only: Resource not available.

94

For VSAM with CMPR2 compiler-option only: No file position indicator for sequential request.

95

For VSAM only: Invalid or incomplete file information.

96

For VSAM under MVS: No DD statement specified for this file. For VSAM under VSE: No DLBL statement specified for this file.

97

For VSAM only: OPEN statement execution successful: File integrity verified.

108

When trying to Load a VSAM File from a Sequential File, there is a mismatch in LRECL (IDC3351I)


Page 10

7/30/2008

PL/1 ONCODE DETAILS ONCODE 3 4 9 10 20 21 22 23 24 40 41 42 43 44 45 46 50 51 52 53 54 55 56 57 58 70 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 99 100 150 151 290 300 310 320 330 340 341 350 360 361 362 400

Meaning of the ONCODE in a SELECT/WHEN/OTHERWISE group, no WHEN clause satisfies the condition and no OTHERWISE clause is given SIGNAL FINISH, STOP or EXIT statement executed SIGNAL ERROR statement executed SIGNAL NAME statement executed or NAME condition occurred SIGNAL RECORD statement executed Record variable smaller than record size Record variable larger than record size Record variable length is zero or is too short to contain the key a record with a length of zero was read from a REGIONAL data set SIGNAL TRANSMIT statement executed. transmission error in output data set transmission error in input data set transmission error on output to VSAM index set transmission error on input from VSAM index set transmission error on output to VSAM sequence set transmission error on input from VSAM sequence set SIGNAL KEY statement executed specified key can not be found specified key already exists key is out of sequence during creation of a INDEXED or REGIONAL data set key conversion error either the specified key is the null string or begins with X'FF' or a REWRITE was attempted but the embedded key has changed key is outside of the data set limits No space available to insert a record key is outside of range SIGNAL ENDFILE statement executed or ENDFILE condition occurred SIGNAL UNDEFINEDFILE statement executed conflicting attributes between DECLARE statement and OPEN statement Conflict between file attributes and physical organization of data set data set specification is incomplete DD statement is missing in JCL an I/O error occurred during initialization of DIRECT OUTPUT file LINESIZE greater than maximum conflicting attributes between DECLARE statement and JCL DD statement conflicting attributes between DECLARE statement and JCL DD statement password not specified or invalid SIGNAL ENDPAGE statement executed or ENDPAGE condition occurred ENV() option invalid for file accessing VSAM data set. error while opening a VSAM data set error while opening a data set (subcodes) REUSE specified, but data set is not reusable Alternate index specified for an empty VSAM data set. Attempt to OPEN the MSGFILE(SYSPRINT) file after a subtask has been created open failed for dataset (subcodes) SIGNAL PENDING statement executed or PENDING condition occurred SIGNAL STRINGSIZE statement executed or STRINGSIZE condition occurred truncation occurred while assigning a mixed-character string SIGNAL INVALIDOP statement executed or INVALIDOP condition occurred SIGNAL OVERFLOW statement executed or OVERFLOW condition occurred SIGNAL FIXEDOVERFLOW statement executed or FIXEDOVERFLOW condition occurred SIGNAL ZERODIVIDE statement executed or ZERODIVIDE condition occurred SIGNAL UNDERFLOW statement executed or UNDERFLOW condition occurred SIGNAL SIZE statement executed or SIZE condition occurred SIZE condition occurred during I/O operation SIGNAL STRINGRANGE statement executed or STRINGRANGE condition

occurred

insufficient free storage for allocation of a based variable insufficient space in target area for assignment of source area SIGNAL AREA statement executed SIGNAL ATTENTION statement executed or ATTENTION condition occurred


Page 11

7/30/2008

450 451 500 510 520 521 600 601-684 1002 1003 1004 1005 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1040 1041 1042 1102 1104 1105 1500-2531 2002 2050 3000 3001 3006 3009 3010 3011 3012 3013 3014 3015 3016 3017 3500 3501 3502 3503 3797 3798 3799

SIGNAL STORAGE statement executed ALLOCATE failed, not enough storage available SIGNAL CONDITION (name) statement executed SIGNAL CHECK statement executed SIGNAL SUBSCRIPTRANGE statement executed, or SUBSCRIPTRANGE condition occurred subscript of sub-defined variable lies outside bounds of corresponding dimension of base variable SIGNAL CONVERSION statement executed Invalid conversion attempted during input/output of a character string. GET or PUT STRING specifies data exceeding size of string output not allowed due to previously raised TRANSMIT or KEY condition PAGE, LINE or SKIP attempted for non-print file. DISPLAY() REPLY () statement uses zero length expression REWRITE or a DELETE statement not preceded by a READ statement Invalid data for a GET STRING DATA statement. I/O statement conflicts with the file attributes BUILTIN function or pseudo-variable references a file, which is not open I/O error with no more information provided by OS READ SET or READ INTO statement not preceded by a REWRITE statement REWRITE or DELETE statement can not be executed as the preceding READ statement has not yet completed number of incomplete operations reaches maximum Event variable for an input/output operation is already in use. file is not open due to an UNDEFINEDFILE condition EOF encountered in data before end of data-list or format-list attempt to close file not opened in current task I/O attempted before WAIT statement executed to ensure completion of previous READ record can not be accessed as it is locked by another file in this task unable to extend VSAM data set file closed but records still locked by a subtask sequence of I/O operations on device-associated file is incorrect Insufficient virtual storage available for VSAM to complete request no position established in VSAM data set Record or VSAM control interval already held in exclusive control volume not mounted repositioning failed in VSAM data set error occurred during index upgrade on a VSAM data set invalid sequential write attempted on VSAM data set no more space available for output data set record contains a record-delimiter record contains an invalid record-delimiter storage management failed to free storage as the address of the storage to be freed was invalid internal error in a library "object window" couldn't be created computational error while executing a built-in function WAIT statement cannot be executed because of restricted system facility (checkout or optimizing compiler only) WAIT statement would cause a permanent wait edit directed I/O would lead to a loss of significant digits or sign value of W field in F format specification too small PIC description of target does not match source mixed-character string contains a shift-out but no shift-in mixed-character string contains invalid data MPSTR built-in function contains invalid character Retry for graphic conversion error not allowed. graphic string is too long graphic or mixed string does not conform to the continuation rules X or GX constant has an invalid number of digits Improper use of graphic data in stream I/O Invalid graphic, mixed, or DBCS continuation when writing stream I/O to a file containing fixed-length records error during execution of a WAIT-statement error during execution of a DETACH-statement error during execution of an ATTACH-statement error during execution of a STOP-statement attempt to convert to or from graphic data ONCHAR or ONSOURCE pseudo-variable used out of context ON-unit was entered due to a CONVERSION condition and the character that caused the condition is used but has not been corrected by use of the ONSOURCE or ONCHAR Pseudo-variables.


Page 12

7/30/2008

3800 3801 3808 3809 3810 3901 3904 3906 3907 3909 3910 3911 3912 3913 3914 3915 3920 3951 3952 3953 4001 4002 4003 8091 8092 8093 8094 8095 8096 8097 8098 8099 9002 9003 9050 9051 9200 9201 9202 9203 9204 9205 9206 9207 9208 9249 9250 9251 9252 9253 9254 9255 9257 9999

length of data aggregate exceeds system limit Array structure element not mapped Aggregate cannot be mapped in COBOL or FORTRAN data aggregate exceeded the maximum length extent of an array exceeds maximum task variable is already used COMPLETION pseudo-variable specifies an event variable that is already in use assignment to an event variable that is already active DISPLAY statement specifies an event variable that is already active insufficient main storage available to create subtask ( using CALL statement ) maximum number of subtasks reached WAIT statement in ON-unit references an event variable already being waited for CALL with TASK option in block invoked while executing PUT FILE(SYSPRINT) statement CALL statement with TASK option specifies an unknown entry point FORTRAN or COBOL already invoked by an other task multitasking library not selected in the link-edit step An out-of-storage abend occurred Open Edition callable service BPX1MPI failed Open Edition callable service BPX1MP failed Open Edition callable service BPX1PTB failed CONTROLLED variable not allocated during GET DATA CONTROLLED-Variable not allocated during PUT DATA CONTROLLED-Variable not allocated during PUT DATA with STRING-option operation exception ( machine instruction code is invalid ) privileged operation exception ( a privileged instruction cannot be executed in "problem program state" ) EXECUTE exception ( an EXECUTE instruction must not target itself ) protection exception ( address translation error or storage protected ) addressing exception ( address lies outside the available virtual storage ) specification exception data exception ( decimal packed value is invalid ) not enough stack-storage ( result of a fixed-point operation is too large ) Fixed point divide exception (result of a fixed-point division is too large - division by zero?) GOTO statement references label in an inactive block label of the GOTO statement does not exist program terminated by an abend error occurred in CICS ( address of a parameter might be invalid ) program check in SORT/MERGE program VM does not support SORT (if enterprise compiler: CMS does not support SORT) RECORD TYPE is missing in PLISRTx-call RECORD TYPE is invalid in PLISRTx-call specification of "LENGTH=" is missing in PLISRTB- or PLISRTD-call specification of "LENGTH=" is not numeric in PLISRTB- or PLISRTD-call E15 or E35 routine returns an invalid return-code DFSORT failed ( check separate messages ) PLISRTx invoked, but environment is not ADMVS routine cannot be RELEASEd procedure to be fetched cannot be found transmission error during fetch of a procedure FETCH/RELEASE not supported in VM (if enterprise compiler: FETCH/RELEASE not supported in CMS) debugging tool not available ( if enterprise compiler: PLITEST not available ) a MAIN procedure from a PL/I routine can not be fetched under CICS attempt to release a load module containing a high-level language program, which is not PL/1 attempt to fetch a subroutine using the PLICALLA entry point invocation of an Language Environment for MVS/VM service failed


Page 13

7/30/2008

IMS - ERROR CODES SC

EXPLANATION

AB

The call did not specify a segment I/O area. This is a programming error

AC

The call included a SSA with a hierarchical error. This is a programming error

AD

The function code specified for the call contains an incorrect value.

AH

The call requires at least one SSA. This is a programming error (ISRT call).

AI

The error occurred when trying to open the database data set .The most common cause of the AI status code is an error in the JCL defining the database data set. You might also get this error if you try to load an existing database or do other than load processing on empty data set.

AJ

The call specified an invalid SSA. This is a programming error. If the format of the SSA is correct make sure the call doesn't specify an invalid SSA type. For an ISRT call, the lowest level SSA must be unqualified. For a REPL call, there may not be a qualified SSA, and for a DLET call, there may be only one SSA and it must be unqualified.

AK

The field named on a qualified SSA is not correct. This is a programming error.

AM

The call attempted an unauthorized operation, that is , one not allowed by the processing options or sensitive segments specified in the PCB. This is a programming error.

AO

The call caused an operation that resulted in a physical I/O error. This is a serious error that probably requires intervention by a system programmer.

AT

The I/O area the call specified is too large. This is usually a programming error, but the program's PSB may be incorrect.

AU

The SSA's specified in the call exceeded the maximum length allowed for them in the PSB. This is usually a programming error, but the PSB may be incorrect.

DA

The key field (or a non-replaceable field) has been changed in the program's I/O area.

DJ

The update call wasn't preceded by a successful get hold call. This is a programming error. The call violated a delete rule for a segment. This is usually a programming error.

GA

A higher-level segment was retrieved during sequential retrieval, usually a GA isn't a error but an expected condition.

GB

The end of database was reached during sequential retrieval.

GD

Position was lost before the call could be completed, probably because a segment in the path to it was deleted through another PCB.

GE

A segment occurrence meeting all the specified qualifications wasn't found (for a get call) or couldn't be added due to an error in the specified path (for an ISRT call).

GK

A segment of different type but at the same hierarchical level was retrieved during sequential retrieval. Usually GK isn't an error but an expected condition.

GP

Proper parentage isn't in effect. This is usually a programming error.

II

The segment trying to be inserted already exists in the database.

IX

The call violated an insert rule for a segment. This is usually a programming error.

LB

The segment trying to be inserted already exists in the database.

LC

The input data is not in hierarchical sequence.

LD

One or more segments in the path to the segment being loaded are missing ( an error in hierarchical sequence).

LE

The sequence of segment types at the same level isn't the same as that specified in the DBD (an error in hierarchical sequence).

NO

The call caused an operation that resulted in a physical I/O error on a secondary index. This is a serious error that requires intervention by a system programmer.

RX

The call violated a replace rule for a segment. This is usually a programming error for an ISRT call.

V1

A variable length segment longer than the maximum segment size was specified. This is a programming error.


Page 14

7/30/2008

SYSTEM and USER ABEND CODES SYSTEM CODE S000

EXPLANATION Could mean that no IMS segments were selected by DLI call. Look for status code of GE and check your SSA qualifications.

S001

Probably incorrect DCB information. Checking RECORDING MODE and BLOCK CONTAINS clauses in COBOL FD as compared with RECFM of JCL. Check LRECL and BLKSIZE of JCL as compared with the number of characters in the 01 level(s) under the FD in the program. Check for correct tape mounted. The current release of COBOL II takes its recording mode from the 01 items below the FD in determining fixed or variable and maximum record length. Trying to open a dataset that is cataloged but never has been opened or closed.

S002

Same as S001

S013

Same as S001

S02A

Sometimes happens in changeman for no apparent reason. It usually is no problem. Just press enter. Worst case, sign off changeman or tso and back on; problem gone.

S03B

Check DCB info – information must be identical when using a file in more than one place Cannot dummy a VSAM file?

S04E

Forgot to prime the pump with an initial FETCH (read) before trying to insert or replace using the cursor values (DB2) If DBUTIL abends set UTPROC = ‘RESTART’ when restarting job. DB2 jobs that abend with S04E usually means DB2 table was migrated and job issued recall and then abended waiting for HSM. Check reason code and DB2 sysprint for added information. Eg. Dataset Names : prod : NW40DB2P.DSNDBD.XXXXXX.YYYYYY.IXXX.AXXX test : NW20DB2T.DSNDBD.XXXXXX.YYYYYY.IXXX.AXXX test : NW20DB2T.DSNDBC.XXXXXX.YYYYYY.IXXX.AXXX XXXXXX and YYYYYY are often in the sysprint information.

S04E

THIS HAPPENS WHEN A DB2 JOB ABENDS USING A UTILITY ID AND THE UTILITY ID HAS NOT BEEN CLEANED UP YET. GO INTO OPTION N.D.7 DISPLAY UTILITY IDS PENDING AND THEN TERM THE PENDING UTILID’S RELATED TO YOUR USER ID. =N.D.7 DISPLAY UTILID’S 1 === > - DIS UTITILITY(*) TERM UTILID’S 1 === > - TERM UTITILITY(TSTGML01.STEP20)

SOC1

Program ID not right Probably a call to an unlinked module; ABEND at location 2, 4 or 6 usually. Can be the result of a call to ‘ABENDX’ Sometimes caused by a read or write to an unopened file ABEND at location 48 or 4800 or 52 or 5200 In each case, check register 14 for program error location

SOC4

May be caused by bad subscripting or indexing More short record from input buffer; check for BUFL option in JCL DCB field. More parms in called module than in calling module


Page 15

7/30/2008

Directory block full will cause SOC4 in module init routines. In TSO dialog – full profile, change call to use diff profile. SOC4 – 11 can be bad index on a VSAM file. Repro file to check. Can also be using incorrect PSB for database if segments are changed recently. "UNABLE TO OPEN D????X01" means you are using an update PSB and the database is allocated online. Mixed RES/NORES job – can cause other abends - often SOC4. ABEND in IGZ … module of link can be incompatible subroutines. Include IGZCPCO IGZENRI IGZENRT and ILBOSRV in the start of your link. Could also cause SOC6 or SOC1. Last data set of a concatenation empty. COBOL sort cannot concatenate disk and tape (JCL sort can ) NOMAD read past end of file May need to execute DBAU03P instead of DBAU03T READY TRACE used in a module that is linked to a COBOL II module. Also make sure ‘if’ verbs end with ‘end-if’

SOC5

Same causes as OC4

SOC6

Same causes as OC1. ( May be executing an old version of the program. )

SOC7

Check for bad data – maybe defined as COMP, COMP-3 or incorrect location. Could also be bad subscripting.

SOCB

Divisor is zero

S106

If register 15 contains a ‘C’, not enough core was available If register 15 contains an ‘F’, look for the message FETCH FAILED FOR MODULE XXXXXXXX RETURN CODE XX. If you find this message resubmit the job – if you still get a ‘F’ check your input data sets. Fixed by overriding the REGION size in DBTSTQLD JCL

S122

Job cancelled by operator with dump

S213

Data set not found – check spelling of dsn Check vol-ser parameter. Check if data set has been scratched. Check VSAM vs Sequential in select statement of COBOL program If 213-70 and are printing a member in a PDSE you can’t be in edit mode for that member.

S222

Job cancelled by operator without dump

S237

Abend at end of volume. If input tape, check end of output and if ok, ignore abend

S2F3

System crashed while running your program. Also gives a Jcl error msg. Resubmit job

S30A

Add DCB=nnnn, to your JCL

S322

Time out on a job. Check the class the job is running in. See TSO JOBCLASS for what types of jobs run in which classes Check for valid DSN or valid DISP USER=888, REASON=0000000 Try increasing region size, usually when IKJEFT01 utility

S4EC

If you have specified more than one volume in the JCL VOL=SER parm, remove all but one

S497

A program called the common abend module GPXCDABN and the error message is displayed. This reusable abend module allows more detailed messages up to 300 bytes

S522

Interactive session timed out


Page 16

7/30/2008

S706

Program not found: Check link to see program(s) were included Check link name

S722

OUTLIM maximum has been reached

S737

Missing or empty data set in a concatenation

S806

Program not found : Check program name being executed Check JOBLIB or STEPLIB card Check executive compiled DYNAM. Link to other modules via a link job will NOT resolve called modules. Dynamic environment : Is a module compiled as DYNAM? Is DYNAM LIB in the execute JCL? If call to other than PROGRAM-ID, you need to LINK step of translate / link of called module change the SYSLIN to add a line ALIAS called-entry. ( A space ahead of ALIAS ). Has occurred when VSAM files dummied out.

S813

The tape VOL-SER number does not match the tape DSN. Either the tape VOL-SER number is wrong, the G000V00 is wrong, or the tape DSN is incorrect

S913

If need access to data file, obtain RACF authority. If position 8 of a test DSN = P RACF thinks it is a production dataset

S923

DB2 is up but SAS job has something locked up.

S929

DLI - check for missing or misspelled PSB name

U929

PSB not found. Check your PSB lib or PSB spelling

9XX-12

BLP tapes must have USER=TSPRX7

S9EC

BLP tapes must have USER=TSPRX7

SA78

Cancelled / timed-out in middle of sort. Check other message / dump

SB37

Not enough space on output file – increase SPACE parameter on file named in console messages section of your output

SB78

Accessing the same database another job is currently using. Rerun after the other job completes.

SC03

This is believed to be MIXRES error problem. The executable module needs to have the following modules added to the beginning of its LINKMOD set : - INCLUDE SYSLIB (ICZCPCO) *MODULES TO HELP RESOLVE - INCLUDE SYSLIB(IGZENRI) * mixres error for the 3.0 - INCLUDE SYSLIB(IGZENRT) * rel of VS COBOL II - INCLUDE SYSLIB(ILBOSRV) * these were pulled from LINKMOD GRPL206A

SD37

Not enough space on output file – increase SPACE parameter on file named in console messages section of your output. For file expansions, reduce the size of the parm.

SE37

Not enough space on output file – increase SPACE parameter on file named in console messages section of your output.

U0003

Usually a call to a non-existent program TMS volume number does not contain DSN Tried to access data set but missing - check console messages Call to abend – check displays on SYSOUT data set

U0016

Usually abend on sort. Check sort message area for reason for bad sort. If insufficient core, increase


Page 17

7/30/2008

REGION size, or if executing a ‘SORTD’ add a DYNALLOC and FILSZ as in this example : //SYSIN DD * SORT FIELDS=(438,12,CH,A), DYNALLOC=(SWORK,6),FILSZ=E10000 If still abend, try deleting the FILSZ=Ennnn part of the above card. Sort cannot handle spanned records on sortout. See JR’s memo located in NW20GRPT.EBS.GTOOLKIT.ABEND.CNTL(M901126).

U0020-08

Means that the D????P01 file has zero space available. You need to do an unload reload with more space allocated.

U0039

If this is a batch DLI job with a return code of 20, try changing the job name and resubmitting – i.e., change TSxxx80A to TSxxx80. Or run IMS backout step or on rare situation change IRLM.

U0041

If this is a batch DLI job with a return code of 20, try changing the job name and resubmitting- i.e., change TXxxx80A to TSxxx80.

U0047

Try changing from production DLI database to test and/or change to exec DBAU03T. or change IRLM=N Set //STEPLIB DD blanks with the number of lines = the number of steplib DD’s in the proc.

U0048

?? Invalid parm card or pds file being brought into the program

U0403

If occurs during a DATAVANTAGE load of a database – correct by deleting the data portion of the database and reallocating that data portion.

U203

Same as S0CB

U0259

IMS compile with DATA(31)

U295

Look for unopened file that your program is trying to use or file being opened twice

U0476

Means your PSB does not match your COBOL ENTRY statement. Make sure the databases are in the same sequence in both & recompile. YOU FORGOT TO PUT ‘Y’ IN THE CBLTDLI PARAMETER ON THE CHGMAN COMPILE OPTIONS FIELD! You may have the wrong linkset for ims program You may need to have procedure division using instead of entry DLITCBL.

U504

Check for too large of a block size.

U514

Check for missing GOBACK, especially within an entry point.

U0595

IMS get core failure – must call ‘DLITCBL’ before call ‘CBLTDLI’

U826

Happened when the key length and record length were incorrect in the initialize database index step.

U850

Pointer problem – reload from backup file.

U852

Your DBD stuff is not appropriate for the database !!\ Maybe looking for incorrect segment layouts and like that.

U853

Happened when the DRATEP01 DSN was different than DRATEX01 DSN.

U0868

Means something is wrong with your test database. Make a new database and try again.

U1002

Check for ‘block contains 0 records’ missing in FD. Record length does not agree with the copy member in the FD. - If are working with a production program and you are dummy-ing out the file include the following in your JCL: //* //VSAMFILE DD DUMMY,AMP=AMORG //QSAMFILE DD DUMMY,DCB=BLKSIZE=18 // If are opening a dataset that has a card – as output : //cardin dd * - Could possibly indicate syntax error.


Page 18

7/30/2008

U1010

New COBOL calling old COBOL with DISPLAYs or READY TRACE. Job will process and put out DISPLAYs; however, upon completion or call to COBOL2 module it will abend with a 1010.

U1020

User logic error – see console message section for clue Call ‘DLITCBL’ entry from IMS in middle of perform Check for extraneous generated SYSIN DD statements Read past end of file? Trying to close a file that is not open The VSAM file is allocated online and must be de-allocated first (Use TZDA or TQDA to de-allocate the file online)

U1033

- Look at +IGZ033I error message. Attempt to call an AMODE(24) ‘callpgm’ … passing 16 meg. Recompile program with DATA(24) instead of DATA(31). Rerun job. You may need to set DATA(24) in the link step.

U1034

Same as SB37

U1044

Old cobol calling new cobol

U1035

VSAM LRECL does not match your COBOL record layout – 4 bytes. DD statement missing. Inconsistent between FD, 01, and/or JCL COBOL II treats your recording mode line as comments and sets mode based on the 01’s under the FD.

U2658

Happened when using IDCAMS instead of UTYPAMS DB load.

U3003

VSAM return code 97 on open.

U3040

DGS6421 … Param exceeds max allowable length IRLM param or one of the other ims parameters may be incorrect.

U3057

Check your DB2 stuff that is called from IMS. Make sure you have DDOTV02 DD and MBR=DSNMTV01. Check your DDITV02 data

U4092

Build buffer error – increase region size

U4094

De-allocate file from online or make sure file is VSAM Empty VSAM file

X900

File used by GLK0G3CM in security checking received a error on read. Check for file(s) closed.

1nnn

VSAM abend when ‘nnn’ is the feedback code in decimal-SHOWCB

2nnn

VSAM abend when ‘nnn’ is the feedback code in decimal-MODCB

3nnn

VSAM abend when ‘nnn’ is the feedback code in decimal-GENCB

IECTMS3 IEC141 013-20

IMS needs oper VOL-SER-NO reply of input tape specified as BLP that is exactly equal to VOL=SER=…. Specified in JCL. Sequential dataset open. Error is either : BLKSIZE is not a multiple of LRECL LRECL = 0 when RECFM = FB or FBS, BLKSIZE is not 4 bytes greater than LRECL when RECFM = V


Page 19

7/30/2008

More Details on ‘S’YSTEM ABEND CODES 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.


Page 20

7/30/2008

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 Mainframe – Abend Codes and Details

Page 21

7/30/2008

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. Mainframe – Abend Codes and Details

Page 22

7/30/2008

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 - AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE WITH RECFM=FB, BUT BLKSIZE IS NOT A MULTIPLE OF LRECL, OR FOR VARIABLE-LENGTH RECORDS, BLKSIZE IS NOT 4 BYTES GREATER THAN THE LRECL. S013 - 24 - AN OPEN WAS ISSUED WITH INPUT, INOUT, RDBACK, OR UPDAT 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 - ONE OF THE FOLLOWING WAS DETECTED: - AN OPEN MACRO WAS ISSUED FOR A DATASET WITH BLKSIZE AND BUFL EQUAL TO 0. THE SYSTEM DETERMINED THAT IT HAD TO OBTAIN BUFFERS BUT WAS UNABLE TO DO SO. - RECFM WAS SPECIFIED WITH BOTH A AND M ATTRIBUTES. - QSAM, LRECL=0 AND RECFM WAS NOT V OR VB. - RECFM=V OR VB AND LRECL > (BLKSIZE-4). - QSAM AND BLKSIZE=0. - RECFM NOT VARIABLE OR UNDEFINED AND LRECL > BLKSIZE. - BFTEK=A,LRECL=0,RECFM=VBS. 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, Mainframe – Abend Codes and Details

Page 23

7/30/2008

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. Mainframe – Abend Codes and Details

Page 24

7/30/2008

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 - AN INVALID VIO REQUEST WAS DETECTED BY THE PAGE OPERATIONS Mainframe – Abend Codes and Details

Page 25

7/30/2008

STARTER ROUTINE OF ASM. THE SYS1.LOGREC ERROR RECORD CONTAINS A HEXADECIMAL REASON CODE. 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 - A QISAM I/O ERROR OCCURRED. 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 CUASE-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. S047 - AN UNAUTHORIZED PROGRAM REQUESTED A RESTRICTED SVC. S04B - AN INVALID OPERATION CODE WAS PASSED TO A TSO LINKAGE ASSIST ROUTINE (LAR). ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S04B OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S04B-RC)** 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. S064 - AN ADDRESS SPACE THAT HOLDS A CROSS MEMORY LOCAL LOCK (CML LOCK) TERMINATED ABNORMALLY BEFORE IT FREED THE LOCK. 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. Mainframe – Abend Codes and Details

Page 26

7/30/2008

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. THE ADDRESS SPACE OR JOB IS TERMINATED. RESUBMIT THE JOB. 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*** ***S0B0 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 Mainframe – Abend Codes and Details

Page 27

7/30/2008

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 REQUESTED --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 Mainframe – Abend Codes and Details

Page 28

7/30/2008

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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S0E0 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S0E0-RC)** 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 Mainframe – Abend Codes and Details

Page 29

7/30/2008

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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S0F8 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S0F8-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S0F9 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S0F9-RC)** 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 - A DEVICE TO BE USED WAS NOT OPERATIONAL OR A PSEUDO DEVICE PREVIOUSLY ALLOCATED HAS BEEN REALLOCATED. 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S102 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S102-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S104 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S104-RC)** 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. Mainframe – Abend Codes and Details

Page 30

7/30/2008

S106 - AN ERROR WAS DETECTED BY THE CONTROL PROGRAM WHEN IT ATTEMPTED TO FETCH THE REQUESTED PROGRAM INTO VIRTUAL STORAGE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S106 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S106-RC)** --POSSIBLE CAUSE-PREVIOUS LKED STEP FAILED TO OUTPUT A SYSLMOD, NEEDS LARGER SIZE= I/O ERROR - MACHINE TROUBLE OR DISK FAILURE S106 - 0B - A PROGRAM CHECK OR LOOP OCCURRED IN FETCH. S106 - 0C - NOT ENOUGH STORAGE WAS AVAILABLE FOR FETCH TO DO A GETMAIN FOR THE MODULE OR CONTROL BLOCKS. CHECK REGISTER 0: 04 - NO STORAGE FOR DATD. 08 - NO STORAGE FOR DEB. 0C - NO STORAGE FOR IOSB. 10 - NO STORAGE FOR EXLIST. 14 - NO STORAGE FOR MODULE. 18 - UNABLE TO FIX STORAGE. S106 - 0D - THE CONTROL PROGRAM FOUND AN INVALID RECORD TYPE IN THE 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 - 0F - AN UNCORRECTABLE INPUT/OUTPUT ERROR OCCURRED, THE LOAD MODULE HAD AN ERROR WHICH CAUSED THE CHANNEL PROGRAM TO FAIL, OR A LINKLIST LIBRARY EXPANDED INTO ANOTHER EXTENT SINCE IPL. CHECK REGISTER 0: 40 - I/O ERROR ON A PDS. 44 - ERROR ON A VIRTUAL DS. 48 - SEEK ADDRESS OUTSIDE EXTENT. 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S10A OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S10A-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S112 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S112-RC)** --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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S113 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S113-RC)** 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. Mainframe – Abend Codes and Details

Page 31

7/30/2008

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 - 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 - AN I/O ERROR OCCURRED READING HEADER LABELS FOR A DATASET OPENED FOR INPUT OR INOUT, OR READING THE TRAILER LABEL FOR A DATASET OPENED FOR RDBACK. S137 - 18 - AN I/O ERROR OCCURRED WHILE POSITIONING A MAGNETIC TAPE DATASET AT THE FIRST DATA RECORD, OR ON A READ BLOCK ID COMMAND USED TO ESTABLISH THE TAPE POSITION. S137 - 1C - AN INVALID TRAILER LABEL WAS READ DURING 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 Mainframe – Abend Codes and Details

Page 32

7/30/2008

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 ESTABLISH 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 PROTECTED FROM THE CALLER. INPUT PARAMETER ERROR ON ECB: - ECB NOT ON FULLWORD BOUNDARY. Mainframe – Abend Codes and Details

Page 33

7/30/2008

- 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 REQUEST 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 - AN I/O ERROR OCCURRED READING THE FORMAT-1 DSCB, OR THE FORMAT-1 DSCB COULD NOT BE FOUND ON THE FIRST VOLUME SPECIFIED BY THE DD STATEMENT VOLUME SERIAL FIELD. 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 - 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 Mainframe – Abend Codes and Details

Page 34

7/30/2008

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 UPDATE BUT 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 - AN I/O ERROR OCCURRED READING A USER LABEL ON MAGNETIC TAPE. S214 - 08 - AN I/O ERROR POSITIONING A MAGNETIC TAPE VOLUME DURING EXECUTION OF A CLOSE MACRO. S214 - 0C - AN I/O ERROR OCCURRED WHILE PROCESSING A READ BLOCK ID COMMAND TO ESTABLISH THE TAPE POSITION. S214 - 10 - THE NUMBER OF BLOCKS PROCESSED ACCORDING TO THE TAPE POSITION DOES NOT MATCH THE DCB BLOCK COUNT. S222 - EITHER THE OPERATOR OR THE JOB ENTRY SUBSYSTEM CANCELLED THE JOB. CHECK THE JOB LOG LISTING FOR MORE INFORMATION. IF THERE IS NO APPARENT EXPLANATION, CONTACT OPERATIONS BEFORE RESUBMITTING. --POSSIBLE CAUSE-LINE OR CARD ESTIMATE EXCEEDED JCL ERROR CAUSED MOUNT REQUEST FOR INVALID OR NON-EXISTING VOLUME REQUESTED DEVICES NOT CURRENTLY AVAILABLE (JOB MAY BE REQUEUED) 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. Mainframe – Abend Codes and Details

Page 35

7/30/2008

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 - THE BLOCK COUNT IN THE DCB DOES NOT MATCH THAT IN THE TRAILER LABEL. A BLOCK OF DATA HAS BEEN MISSED OR SKIPPED. S237 - 08 - THE DSNAME IN A HEADER LABEL DOES NOT MATCH THAT IN THE JFCB ON THE SECOND OR SUBSEQUENT VOLUME OF A MAGNETIC TAPE DATASET. VERIFY THAT THE CORRECT VOLUME AND DSNAME WERE SPECIFIED. 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 INFORMATION: 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 Mainframe – Abend Codes and Details

Page 36

7/30/2008

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 - THE ERROR OCCURRED DURING THE EXECUTION OF THE LINK, XCTL, ATTACH, OR LOAD SERVICE ROUTINES. THE AUTHORIZED ROUTINE REQUESTED A MODULE WHICH COULD NOT BE FOUND ON AN AUTHORIZED LIBRARY, BUT A COPY OF THE MODULE MAY HAVE BEEN FOUND ON A NONAUTHORIZED LIBRARY. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S306 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S306-RC)** 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. 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)** Mainframe – Abend Codes and Details

Page 37

7/30/2008

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 - JOB OR STEP TIME EXCEEDED THE SPECIFIED LIMIT PROGRAM IS IN A LOOP INSUFFICIENT TIME PARAMETER ON JOB OR EXEC CARD 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 THE*** ***S337 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 ATTEMPTED 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. Mainframe – Abend Codes and Details

Page 38

7/30/2008

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.


Page 39

7/30/2008

S402 - THE EVENTS 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*** ***S402 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S402-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S40A OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S40A-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S413 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S413-RC)** --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 - NO UNIT IS AVAILABLE FOR MOUNTING THE VOLUME FOR THE DATASET BEING OPENED. THE VOLUME ALREADY ON THE ALLOCATED UNIT AS SPECIFIED BY THE VOL=SER IS EITHER PERMANENTLY RESIDENT OR RESERVED. IT COULD NOT BE DEMOUNTED IN ORDER TO MOUNT THE REQUIRED VOLUME, OR THE VOLUME CANNOT BE DEMOUNTED BECAUSE ANOTHER DCB IS OPEN ON THAT DEVICE OR THE DEVICE TYPE IS INCOMPATIBLE WITH THE DSORG IN THE DCB. THIS ERROR MAY BE DUE TO A PREVIOUS ABNORMAL TERMINATION ASSOCIATED WITH THE SAME UNIT IN THE SAME STEP. S413 - 08 - AN I/O ERROR OCCURRED POSITIONING A MAGNETIC TAPE VOLUME. 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 - THE SPECIFIED DATASET WAS OPENED FOR INPUT, BUT NO VOLUME SERIAL NUMBER WAS SPECIFIED ON THE DD STATEMENT. S413 - 1C - AN OPEN MACRO WAS ISSUED FOR A DATASET, BUT THE VOLUME SEQUENCE NUMBER ON THE ASSOCIATED DD STATEMENT WAS GREATER THAN THE NUMBER OF VOLUMES CONTAINING THE DATASET. S413 - 20 - AN I/O ERROR OCCURRED READING THE VOLUME LABEL OR FORMAT-4 DSCB ON A DIRECT ACCESS 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. Mainframe – Abend Codes and Details

Page 40

7/30/2008

S413 - 30 - THE MSS HARDWARE MOUNTED THE WRONG VIRTUAL VOLUME. S413 - 34 - LABEL=(N) WAS SPECIFIED, WHERE N IS GREATER THAN 1, AND VOL=SER WAS NOT SPECIFIED FOR A TAPE DATASET. 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S414 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S414-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S437 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S437-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S478 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S478-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S513 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S513-RC)** 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 - JOB OR TSO SESSION EXCEEDED MAXIMUM JOB WAIT TIME OR OPERATOR DID NOT MOUNT THE REQUIRED TAPE WITHIN ALLOWED TIME LIMIT 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 REACTIVATED. S604 - GETMAIN ERROR --POSSIBLE CAUSE-MISSING SORTLIB CARD SUBSCRIPT ERROR - CLOBBERED FREE QUEUE ELEMENT Mainframe – Abend Codes and Details

Page 41

7/30/2008

***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S604 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S604-RC)** 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 ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S605 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S605-RC)** 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 ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S613 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S613-RC)** --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 - AN I/O ERROR OCCURRED READING A LABEL ON A MAGNETIC TAPE. 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S614 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S614-RC)** --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. Mainframe – Abend Codes and Details

Page 42

7/30/2008

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 ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S637 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S637-RC)** 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 - AN I/O ERROR OCCURRED DURING END OF VOLUME PROCESSING WHILE READING THE VOLUME LABEL OF A MAGNETIC TAPE. S637 - 38 - AN I/O ERROR OCCURRED WHILE POSITIONING A TAPE WITHOUT LABELS OR WITH NONSTANDARD LABELS. S637 - 3C - AN I/O ERROR OCCURRED WHILE POSITIONING A CONCATENATED MAGNETIC TAPE DATASET. S637 - 40 - AN I/O ERROR OCCURRED POSITIONING A MAGNETIC TAPE DATASET THAT WAS OPENED WITH THE OPTION INPUT OR INPUT TO BE READ FORWARD.


Page 43

7/30/2008

S637 - 44 - AN I/O ERROR OCCURRED WHILE CHECKING SENSE BYTES TO DETERMINE IF A FILE PROTECT RING IS ON A MAGNETIC TAPE CONTAINING A DATASET OPENED FOR INOUT. S637 - 4C - AN I/O ERROR OCCURRED IN TAPE POSITIONING FOLLOWING USER HEADER LABEL PROCESSING. S684 - THE MODULE CALLING THE RACF MANAGER OR THE RACLIST FUNCTION IS NOT AUTHORISED TO THE SVC FUNCTION.THE MODULE CALLING THE RACF MANAGER MUST BE AUTHORISED (APF-AUTHORISED, IN SYSTEM KEY 0-7, OR IN SUPERVISOR STATE). THE MODULE CALLING THE RACLIST FUNCTION MUST BE AUTHORISED (APF-AUTHORISED, IN SYSTEM KEY 0-7, OR IN SUPERVISOR STATE) OR IN THE RACF-AUTHORISED CALLER TABLE AND FETCHED FROM AN AUTHORISED LIBRARY. - POSSIBLE USER ERROR. IF THE RACF MANAGER WAS CALLED, VERIFY THAT THE CALLING MODULE WAS EXECUTING IN AN AUTHORISED STATE. IF THE RACLIST FUNCTION WAS CALLED, VERIFY THAT THE MODULE NAME WAS ENTERED IN THE RACF-AUTHORISED CALLER TABLE AND THAT THE CALLING MODULE WAS LINK EDITED INTO AN AUTHORISED LIBRARY. 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. - OFFSET 10 CONTAINS A COPY OF THE REGISTERS WHEN EXCP ISSUED THE ABEND MACRO. - OFFSET 54 CONTAINS THE CONTENTS OF THE REQUEST QUEUE ELEMENT (RQE), IF ALLOCATED, FOR THE I/O REQUEST BEING PROCESSED. S706 - THE REQUESTED LOAD MODULE WAS MARKED BY THE LINKAGE EDITOR AS NOT EXECUTABLE. BAD PRIOR LINKEDIT - CHECK THE LKED SYSPRINT S713 - TRIED TO WRITE ON A DATASET WHOSE DATE PROTECTION HAD NOT EXPIRED. OPERATOR REPLIED 'M' TO IEC507D TO HONOR EXP DATE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S713 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S713-RC)** 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 ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S714 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S714-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S717 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S717-RC)** Mainframe – Abend Codes and Details

Page 44

7/30/2008

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 S722 - THE OUTPUT LIMIT SPECIFIED BY THE OUTLIM KEYWORD ON THE SYSOUT DD STATEMENT OR BY THE LINES KEYWORD ON THE JOBPARM DD STATEMENT WAS EXCEEDED. S737 - I/O ERROR; DSCB NOT FOUND FOR MULTI-VOLUME OR CONCATENATED DATA SET. BE SURE ALL THE DATA SETS EXIST FOR CONCATENATED DATA SETS ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S737 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 - 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. 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 ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S806 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S806-RC)** --POSSIBLE CAUSE-Mainframe – Abend Codes and Details

Page 45

7/30/2008

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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S80A OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S80A-RC)** 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 ***IF THE IEF085I OR IEF186I ERROR CODE IS AVAILABLE, SUPPLY IT *** ***IN THE S822 OPERAND FOR MORE INFORMATION: H ABEND O(S822-EC)*** 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. Mainframe – Abend Codes and Details

Page 46

7/30/2008

S837 - THE ERROR OCCURRED DURING END OF VOLUME FOR A SEQUENTIAL DATA SET. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S837 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S837-RC)** 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 NOT BE ENFORCED. FOR OUTPUT, THE ABEND PREVENTS ANY VIOLATION FROM HAPPENING. S878 - REQUEST FOR 0 BYTES OF VIRTUAL STORAGE OR NOT ENOUGH VIRTUAL STORAGE AVAILABLE FOR GETMAIN OR FREEMAIN REQUEST. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S878 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S878-RC)** 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. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***S913 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S913-RC)** --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.


Page 47

7/30/2008

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.


Page 48

7/30/2008

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. S978 - 04 - (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S978) AREA TO BE FREED BY FREEMAIN IS NOT ON A DOUBLEWORD BOUNDARY.

SA00 - A PROGRAM CHECK OCCURRED IN AN APPENDAGE. IN THE ABNORMAL TERMINATION DUMP, THE TCB FIELD TCBEXCPD (AT OFFSET C0) POINTS TO THE EXCP PROVIDED DEBUGGING AREA. THE ITEMS IN THE DEBUGGING 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. - OFFSET 10 CONTAINS A COPY OF THE REGISTERS WHEN EXCP ISSUED THE ABEND MACRO. - OFFSET 54 CONTAINS THE CONTENTS OF THE REQUEST QUEUE ELEMENT (RQE), IF ALLOCATED, FOR THE I/O REQUEST BEING PROCESSED.

SA05 - ERROR DURING FREEMAIN. AREA TO BE RELEASED OVERLAPS FREE STORAGE OR PAGE-FIXED STORAGE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SA05 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SA05-RC)**

SA05 - 04 - THE SQA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA05 - 08 - THE CSA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA05 - 0C - THE LSQA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA05 - 10 - THE PRIVATE AREA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA05 - 14 - PART OF THE CSA BEING FREED IS STILL FIXED. SA05 - 18 - PART OF THE PRIVATE AREA BEING FREED IS STILL FIXED. SA0A - ERROR DURING R-FORM FREEMAIN. AREA TO BE RELEASED OVERLAPS FREE STORAGE OR PAGE-FIXED STORAGE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SA0A OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SA0A-RC)**

SA0A - 04 - THE SQA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA0A - 08 - THE CSA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA0A - 0C - THE LSQA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA0A - 10 - THE PRIVATE AREA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA0A - 14 - PART OF THE CSA BEING FREED IS STILL FIXED. SA0A - 18 - PART OF THE PRIVATE AREA BEING FREED IS STILL FIXED. SA13 - THE ERROR OCCURRED DURING EXECUTION OF AN OPEN MACRO ON MAGNETIC TAPE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SA13 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SA13-RC)**

SA13 - 04 - AN UNEXPECTED LOAD POINT WAS ENCOUNTERED WHILE POSITIONING A TAPE. FOR NL TAPE THIS IS PROBABLY A USER ERROR ASSOCIATED WITH THE USE OF A MULTIVOLUME MULTIFILE NL TAPE.

SA13 - 08 - THE REQUESTED FILE SEQUENCE NUMBER IS LESS THAN THAT OF THE FIRST FILE ON THE SL TAPE DURING AN OPEN TO THE START OF THE FILE.

SA13 - 0C - THE REQUESTED FILE SEQUENCE NUMBER IS LESS THAN THAT OF THE


Page 49

7/30/2008

FIRST FILE ON THE SL TAPE DURING AN OPEN TO THE END OF A FILE.

SA13 - 10 - A TAPE MARK WAS READ INSTEAD OF A HDR1 LABEL WHILE FORWARD SPACING TO THE DESIRED FILE ON AN SL TAPE. THUS, THE MULTIFILE TAPE ENDS BEFORE THE DESIRED FILE. WHEN POSITIONING TO THE END OF FILE 1, THIS MEANS THE VOL LABEL IS FOLLOWED BY A TAPE MARK. CHECK THE FILE SEQUENCE NUMBER AND THE VOLUME SERIAL NUMBERS AND THAT THE JOB THAT WROTE THE TAPE WROTE ALL THE FILES.

SA13 - 14 - A TAPE MARK WAS READ INSTEAD OF A HDR1 LABEL WHILE OPENING FOR INPUT TO THE START OF THE DESIRED FILE ON AN SL TAPE. THUS, THE TAPE ENDS JUST BEFORE THE DESIRED FILE. CHECK THE FILE SEQUENCE NUMBER AND THE VOLUME SERIAL NUMBERS AND THAT THE JOB THAT WROTE THE TAPE WROTE ALL THE FILES.

SA13 - 18 - AN EOV1 LABEL WAS READ ON THE LAST SL TAPE VOLUME WHILE FORWARD SPACEING TO THE DESIRED FILE. IF OPENING TO THE END OF THE FILE, IT COULD NOT BE TREATED AS THE END OF THE DATA SET BECAUSE IT WAS FOR A PREVIOUS FILE SEQUENCE NUMBER.

SA14 - 04 - (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH SA14) I/O ERROR OCCURRED DURING A CLOSE ATTEMPTING A PARTIAL RELEASE OF SPACE ON A DIRECT ACCESS DEVICE.

SA37 - THE ERROR OCCURRED DURING END OF VOLUME PROCESSING. THE TASK IS TERMINATED UNLESS THE ERROR IS TO BE IGNORED AS SPECIFIED IN THE DCB ABEND EXIT ROUTINE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SA37 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SA37-RC)** --POSSIBLE CAUSE-AN OPEN DCB MAY HAVE BEEN PARTIALLY OVERLAID THE DCB MAY HAVE BEEN CLOSED IN A SYNAD ROUTINE THE DCB MAY HAVE BEEN AUTOMATICALLLY CLOSED BY A PREVIOUS END OF OF VOLUME ERROR WHERE IGNORE WAS SPECIFIED IN THE DCB ABEND EXIT

SA37 - 04 - AN SVC 55 (EOV) WAS ISSUES, USUALLY BY A CHECK, GET, OR PUT ROUTINE, AGAINST A DCB WHICH WAS NOT OPEN.

SA37 - 08 - THE DATA EXTENT BLOCK (DEB) DOES NOT POINT TO THE DCB. SA78 - ERROR DURING RU-FORM FREEMAIN. AREA TO BE RELEASED OVERLAPS FREE STORAGE OR PAGE-FIXED STORAGE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SA78 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SA78-RC)**

SA78 - 04 - THE SQA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA78 - 08 - THE CSA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA78 - 0C - THE LSQA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA78 - 10 - THE PRIVATE AREA STORAGE BEING FREED OVERLAPS FREE STORAGE. SA78 - 14 - PART OF THE CSA BEING FREED IS STILL FIXED. SA78 - 18 - PART OF THE PRIVATE AREA BEING FREED IS STILL FIXED. SACC - NOT AN ERROR - FORTRAN ACCOUNTING TERMINATION SB00 - A PROGRAM CHECK OCCURRED IN AN EXCP PROCEDURE. IN THE ABNORMAL TERMINATION DUMP, THE TCB FIELD TCBEXCPD (AT OFFSET C0) POINTS TO THE EXCP PROVIDED DEBUGGING AREA. THE ITEMS IN THE DEBUGGING 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. - OFFSET 10 CONTAINS A COPY OF THE REGISTERS WHEN EXCP ISSUED THE ABEND MACRO. - OFFSET 50 CONTAINS THE TRANSLATION EXCEPTION ADDRESS, IF APPLICABLE. - OFFSET 54 CONTAINS THE CONTENTS OF THE REQUEST QUEUE ELEMENT (RQE), IF ALLOCATED, FOR THE I/O REQUEST BEING PROCESSED. - OFFSET 80 IS THE START OF THE 160 BYTE BLOCKS INVOLVED IN THE I/O REQUEST, IF ALLOCATED.


Page 50

7/30/2008

SB04 - THE ERROR OCCURRED DURING EXECUTION OF A GETMAIN MACRO: - A SUBPOOL NUMBER GREATER THAN 127 WAS SPECIFIED BY A PROBLEM PROGRAM (A PROGRAM NOT AUTHORIZED TO USE VALID SUBPOOL NUMBERS GREATER THAN 127) (RC=08) - AN AUTHORIZED PROGRAM REQUESTED AN INVALID SUBPOOL (RC=04) --POSSIBLE CAUSE-TRIED TO CHANGE BLOCKING FACTOR WHILE LOADING A DATASET COBOL - CONTROL PASSED BEYOND END OF PROGRAM DUE TO INVALID PERFORM

SB05 - THE ERROR OCCURRED DURING EXECUTION OF A FREEMAIN MACRO: - A SUBPOOL NUMBER GREATER THAN 127 WAS SPECIFIED BY A PROBLEM PROGRAM (A PROGRAM NOT AUTHORIZED TO USE VALID SUBPOOL NUMBERS GREATER THAN 127) (RC=08) - AN AUTHORIZED PROGRAM REQUESTED AN INVALID SUBPOOL (RC=04) --POSSIBLE CAUSE-TRIED TO CHANGE BLOCKING FACTOR WHILE LOADING A DATASET COBOL - CONTROL PASSED BEYOND END OF PROGRAM DUE TO INVALID PERFORM

SB0A - THE ERROR OCCURRED DURING EXECUTION OF AN R-FORM GETMAIN OR FREEMAIN MACRO: - A SUBPOOL NUMBER GREATER THAN 127 WAS SPECIFIED BY A PROBLEM PROGRAM (A PROGRAM NOT AUTHORIZED TO USE VALID SUBPOOL NUMBERS GREATER THAN 127) (RC=08) - AN AUTHORIZED PROGRAM REQUESTED AN INVALID SUBPOOL (RC=04) --POSSIBLE CAUSE-TRIED TO CHANGE BLOCKING FACTOR WHILE LOADING A DATASET COBOL - CONTROL PASSED BEYOND END OF PROGRAM DUE TO INVALID PERFORM

SB13 - THE ERROR OCCURRED DURING THE EXECUTION OF AN OPEN MACRO FOR A DATA SET ON A PRINTER WITH UNIVERSAL CHARACTER SET (UCS). ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SB13 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SB13-RC)**

SB13 - 04 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. THE OPERATOR REPLIED 'CANCEL' TO IEC120A, IEC122D OR 1EC123D BECAUSE THE UCS IMAGE COULD NOT BE FOUND IN SYS1.IMAGELIB.

SB13 - 08 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. BLDL FOUND A PERMANENT I/O ERROR WHEN SEARCHING SYS1.IMAGELIB FOR THE REQUESTED UCS IMAGE.

SB13 - 0C - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER OR TO A 3886. A PERMANENT I/O ERROR PERSISTED AFTER TWO ATTEMPTS AT LOADING THE UCS BUFFER -OR- A PERMANENT I/O ERROR OCCURRED WHEN LOADING THE FORMAT RECORD INTO THE 3886.

SB13 - 10 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. A PERMANENT I/O ERROR RESULTED WHEN TRYING TO PRINT THE CHARACTER SET IMAGE FOR VISUAL VERIFICATION, OR DURING AN OPERATION WHICH RESULTED IN POSSIBLE LOST DATA.

SB13 - 14 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. THE OPERATOR REPLIED 'CANCEL' TO IEC121D AFTER THE CHARACTER SET IMAGE WAS PRINTED FOR VISUAL VERIFICATION.

SB13 - 18 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. A PERMANENT I/O ERROR RESULTED WHEN TRYING TO PRINT THE FCB IMAGE FOR VISUAL VERIFICATION.

SB13 - 1C - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. THE OPERATOR REPLIED 'CANCEL' TO IEC128D AFTER THE FCB IMAGE WAS PRINTED FOR VISUAL VERIFICATION -OR- SOME OTHER I/O ERROR.

SB13 - 20 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER, BUT NOT ENOUGH STORAGE WAS AVAILABLE TO OPEN SYS1.IMAGELIB. DURING 3886 OPEN, EITHER THE PROPER VOLUME WAS NOT MOUNTED OR A PERMANENT I/O ERROR OCCURRED WHILE READING SYS1.IMAGELIB.

SB13 - 24 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER, BUT THE VOLUME CONTAINING SYS1.IMAGELIB WAS NOT MOUNTED OR WAS NOT CATALOGUED. DURING 3886 OPEN, THE FORMAT RECORD IDENTIFIER WAS NOT SPECIFIED.

SB13 - 28 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER, BUT A PERMANENT I/O ERROR PERSISTED WHILE OPENING SYS1.IMAGELIB.

SB13 - 2C - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. BLDL FOUND A PERMANENT I/O ERROR WHEN SEARCHING SYS1.IMAGELIB FOR THE REQUESTED FCB IMAGE.

SB13 - 30 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. A PERMANENT I/O ERROR PERSISTED AFTER TWO ATTEMPTS AT LOADING THE FORMS CONTROL BUFFER (FCB).

SB13 - 34 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. THE OPERATOR REPLIED 'CANCEL' TO IEC127D BECAUSE THE FCB IMAGE COULD NOT BE FOUND IN SYS1.IMAGELIB.


Page 51

7/30/2008

SB13 - 38 - AN OPEN WAS ISSUED TO A DATA SET ALLOCATED TO A PRINTER. NO OPERATION WAS PERFORMED FOR ONE OF THE FOLLOWING REASONS: - THE DATA CONTROL BLOCK (DCB) WAS NOT OPEN. - THE DCB WAS NOT VALID FOR A SEQUENTIAL DATA SET. - THE SETPRT PARAMETER LIST WAS NOT VALID. - THE OUTPUT DEVICES WAS NOT A UCS OR 3800 PRINTER.

SB14 - AT CLOSE A PARTITIONED DATA SET DIRECTORY CANNOT BE UPDATED BECAUSE THE NAME IS ALREADY IN THE DIRECTORY, NO SPACE IS AVAILABLE IN THE DIRECTORY, OR AN I/O ERROR WAS ENCOUNTERED IN THE DIRECTORY. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SB14 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SB14-RC)** --POSSIBLE CAUSE-ALLOCATED DIRECTORY SPACE IN JCL, WRITTEN AS SEQUENTIAL DATA SET

SB14 - 04 - A DUPLICATE NAME WAS FOUND IN THE DIRECTORY OF THE PDS. SB14 - 08 - THE TTRN FOR A MEMBER WAS NOT WITHIN THE EXTENTS IN THE DEB SB14 - 0C - THE ATTEMPTED UPDATE OF THE PARTITIONED DATASET FOUND THAT THERE WAS NO SPACE LEFT IN THE DIRECTORY.

SB14 - 10 - AN I/O ERROR OCCURRED TRYING TO UPDATE THE DIRECTORY OF THE PARTITIONED DATASET.

SB14 - 14 - THE CLOSE ROUTINE ATTEMPTED TO UPDATE THE DIRECTORY OF THE PARTITIONED DATASET, HOWEVER THE DCB OF THE DATASET WAS NOT OPEN.

SB14 - 18 - UNSUCCESSFUL GETMAIN FOR STOW WORKAREA WHEN CLOSE TRIED TO UPDATE A PARTITIONED DATASET. REGION SIZE IS TOO SMALL.

SB37 - AT END OF VOLUME, THE VOLUME MUST BE DEMOUNTED, BUT THE SYSTEM IS UNABLE TO DISMOUNT THE VOLUME. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SB37 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SB37-RC)** --POSSIBLE CAUSE-THE DATA SET ON DASD - OUTPUT - ALREADY HAD 16 EXTENTS, BUT REQUIRED MORE SPACE - SECONDARY SPACE WAS TOO SMALL NO MORE SPACE WAS AVAILABLE ON THE VOLUME THE VOLUME TABLE OF CONTENTS WAS FULL

SB37 - 04 - DURING END-OF-VOLUME PROCESSING THE SYSTEM HAD TO DEMOUNT A VOLUME IN ORDER TO MOUNT THE NEXT VOLUME OF THE DATASET. IT WAS UNABLE TO DEMOUNT THE VOLUME FOR ONE OF THE FOLLOWING REASONS: - THE VOLUME WAS PERMANENTLY RESIDENT OR WAS RESERVED. - ANOTHER JOB HAD DATASETS ALLOCATED ON THE VOLUME. - THE FAILING TASK HAD OPEN DATASETS ON THE VOLUME. FOR AN OUTPUT DATASET ON A DIRECT ACCESS DEVICE: - NO MORE SPACE WAS AVAILABLE ON THE VOLUME. - THE DATASET ALREADY HAD 16 EXTENTS BUT REQUIRED MORE SPACE. - MORE SPACE WAS REQUIRED, BUT THE VTOC WAS FULL. FOR AN OUTPUT DATASET ON MAGNETIC TAPE: - A VOLUME NEEDED TO BE DEMOUNTED BECAUSE THE REFLECTIVE SPOT WAS ENCOUNTERED AND MORE RECORDS NEEDED TO BE WRITTEN, BUT THE LIMIT OF OUTPUT TAPES HAD BEEN REACHED.

SB37 - 08 - DURING END-OF-VOLUME PROCESSING THE SYSTEM ATTEMPTED TO EXTEND THE DATASET TO A VOLUME ON WHICH THE DIRF BIT WAS SET. THE VTOC FOR THE VOLUME COULD NOT BE CONVERTED TO THE STANDARD FORMAT FOR ONE OF THE FOLLOWING REASONS: - TWO DATASETS WERE ALLOCATED TO THE SAME SPACE ON THE VOLUME. - A SPLIT CYLINDER DATASET WAS LOCATED ON THE SAME CYLINDER AS A NON-SPLIT CYLINDER DATASET. - THE VTOC CONVERSION ROUTINE IS SET TO REJECT DIRF REQUESTS.

SB37 - 0C - THE MOUNTED DIRECT ACCESS VOLUME WAS REQUESTED TO CONTINUE PROCESSING THE DATASET, BUT THE UNIT ALREADY CONTAINED THE MAXIMUM OF 127 CONCURRENT USERS.

SB78 - THE ERROR OCCURRED DURING EXECUTION OF A GETMAIN OR FREEMAIN MACRO: - A SUBPOOL NUMBER GREATER THAN 127 WAS SPECIFIED BY A PROBLEM PROGRAM (A PROGRAM NOT AUTHORIZED TO USE VALID SUBPOOL NUMBERS GREATER THAN 127) (RC=08) - AN AUTHORIZED PROGRAM REQUESTED AN INVALID SUBPOOL (RC=04) --POSSIBLE CAUSE-TRIED TO CHANGE BLOCKING FACTOR WHILE LOADING A DATASET COBOL - CONTROL PASSED BEYOND END OF PROGRAM DUE TO INVALID PERFORM

SC03 - A DATA SET COULD NOT BE CLOSED BY THE CONTROL PROGRAM, BECAUSE THE DCB HAD BEEN ERRONEOUSLY MODIFIED. ISAM FILE - BAD BLOCK SIZE

SC13 - THE ERROR OCCURRED DURING THE EXECUTION OF AN OPEN MACRO FOR


Page 52

7/30/2008

A CONCATENATED PARTITIONED OR GRAPHICS DATASET. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SC13 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SC13-RC)** --POSSIBLE CAUSE-ATTEMPED TO WRITE OUTPUT TO CONCATENATED PARTITIONED DATASETS MISSING OR DELETED JOBLIB DATA SET GRAPHICS - SYSTEM PROBLEM - WAIT FOR IPL

SC13 - 04 - THE CURRENT TASK TRIED TO OPEN A GRAPHICS DEVICE THAT WAS PREVIOUSLY OPENED AND NOT CLOSED.

SC13 - 10 - AN OPEN MACRO WAS ISSUED SPECIFYING OUTPUT OR EXTEND FOR A CONCATENATED PARTITIONED DATASET. OUTPUT DATASETS CANNOT BE CONCATENATED.

SC13 - 18 - AN OPEN MACRO WAS ISSUED FOR A PARTITIONED DATA SET THAT WAS CONCATENATED WITH A DATA SET THAT DOES NOT RESIDE ON DASD.

SC37 - THE ERROR OCCURRED WHEN AN INPUT OPERATION WAS REQUESTED ON A DIRECT ACCESS DEVICE. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SC37 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SC37-RC)**

SC37 - 04 - END-OF-VOLUME OCCURRED ON INPUT BUT THE NEXT VOLUME CONTAINED MORE THAN SIXTEEN (16) EXTENTS.

SC37 - 08 - END-OF-VOLUME OCCURRED ON INPUT BUT THE NEXT VOLUME CONTAINED A SPLIT CYLINDER ALLOCATION NOT SUPPORTED UNDER MVS.

SD04 - 08 - (08 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH SD04) ERROR DURING GETMAIN: - THERE IS NO REAL STORAGE AVAILABLE FOR THE LSQA AQAT TABLE OR TO BACK THE RSM CONTROL BLOCKS.

SD05 - ERROR DURING FREEMAIN. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SD05 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SD05-RC)**

SD05 - 04 - THE FREEMAIN FOR LSQA SPECIFIED STORAGE THAT WAS NOT ASSOCIATED WITH THE TASK.

SD05 - 08 - THERE IS NO REAL STORAGE AVAILABLE FOR THE LSQA AQAT TABLE OR TO BACK THE RSM CONTROL BLOCKS.

SD0A - ERROR DURING R-FORM GETMAIN OR FREEMAIN. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SD0A OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SD0A-RC)**

SD0A - 04 - THE FREEMAIN FOR LSQA SPECIFIED STORAGE THAT WAS NOT ASSOCIATED WITH THE TASK.

SD0A - 08 - THERE IS NO REAL STORAGE AVAILABLE FOR THE LSQA AQAT TABLE OR TO BACK THE RSM CONTROL BLOCKS.

SD0D - INVALID ABEND RECURSION DURING ABNORMAL TERMINATION OF SUBTASK JOB STEP TASK TERMINATED

SD13 - 04 - (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH SD13) OPEN FOR GRAPHICS - DCB FOR OTHER THAN GRAPHICS DEVICE.

SD14 - THE TASK WHICH ISSUED A CLOSE FOR A GRAPHIC DEVICE WAS NOT THE SAME TASK WHICH PERFORMED THE OPEN.

SD23 - THE ERROR OCCURRED DURING THE EXECUTION OF A WTO OR WTOR MACRO FOR ONE OF THE FOLLOWING REASONS: - THE PARAMETER LIST SUPPLIED TO THE WTOR MACRO DOES NOT BEGIN ON A FULLWORD BOUNDARY. - A WTOR/MLWTO PARAMATER LIST WAS SPECIFIED. - A MULTILINE WTO WAS SPECIFIED AND SPACE WAS NOT AVAILABLE IN SUBPOOL 229 FOR A WORKAREA FOR SVC 35. - THE PARAMETER LIST PASSED BY THE USER DOES NOT RESIDE IN STORAGE THAT IS ACCESSIBLE BY THE USER. - SPACE WAS NOT AVAILABLE IN SUBPOOL 231 FOR AN ORE OR WQE BUFFER.

SD2D - OVERLAY SUPERVISOR FOUND INVALID RECORD TYPE BAD LOAD MODULE RE-LINKEDIT

SD37 - 04 - (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH SD37) A DATASET OPENED FOR OUTPUT USED ALL THE PRIMARY SPACE, AND NO SECONDARY SPACE WAS REQUESTED. EITHER SPECIFY A LARGER PRIMARY QUANTITY OR ADD A SECONDARY QUANTITY TO THE REQUEST.

SD78 - ERROR DURING RU- OR VRU-FORM GETMAIN OR RU-FORM FREEMAIN. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SD78 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SD78-RC)**


Page 53

7/30/2008

SD78 - 04 - THE FREEMAIN FOR LSQA SPECIFIED STORAGE THAT WAS NOT ASSOCIATED WITH THE TASK.

SD78 - 08 - THERE IS NO REAL STORAGE AVAILABLE FOR THE LSQA AQAT TABLE OR TO BACK THE RSM CONTROL BLOCKS.

SE00 - AN ERROR OCCURRED DURING EXCP PROCESSING OF AN I/O REQUEST. THE IOSB RETURNED TO EXCP TERMINATION HAD A RETURN CODE OF X'45'. THE I/O REQUEST WAS TERMINATED. NO EXCP DEBUGGING ERROR IS SUPPLIED. A RECORD IS WRITTEN TO SYS1.LOGREC. THE PREVIOUS LOGREC ERROR RECORD SHOULD INDICATE THE CAUSE OF THE ABEND. --POSSIBLE CAUSE-A PROGRAM CHECK OR MACHINE CHECK OCCURRED WHILE THE IOS IRB ANALYSIS MODULES OR MODULE IECVPST WAS EXECUTING. A PROGRAM CHECK OR MACHINE CHECK OCCURRED WHILE A NONRESIDENT ERP OR ERP LOADER MODULE WAS EXECUTING. THE OPERATOR CAUSED A SYSTEM RESTART DURING I/O REQUEST PROCESSING

SE03 - A TASK ATTEMPTED TO TERMINATE NORMALLY BUT WAS OPERATING IN MUST-COMPLETE STATUS AND DID NOT RESET MUST-COMPLETE. ENSURE THAT EACH ISSUANCE OF AN ENQ, RESERVE AND STATUS MACRO IS PAIRED WITH A DEQ OR STATUS MACRO REQUESTING 'RESET MUST-COMPLETE'.

SE13 - 04 - (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH SE13) WHEN OPENING A GRAPHIC DATA CONTROL BLOCK THE GNCP (MAXIMUM NUMBER OF CONCURRENT CHANNEL PROGRAMS) BYTE CONTAINED A VALUE OUTSIDE THE ACCEPTABLE RANGE OF 1 TO 99.

SE1A - CAS (THE CATALOG ADDRESS SPACE) ALLOCATE TASK ABENDED BECAUSE IT EXCEEDED THE ALLOTTED TIME FOR PROCESSING. IT MAY HAVE BEEN WAITING FOR SOME PERMANENTLY UNAVAILABLE SYSTEM RESOURCE. THE SYSTEM ATTACHES A NEW TASK TO RESTORE THE ALLOCATE FUNCTION.

SE37 - THE ERROR OCCURRED DURING END OF VOLUME PROCESSING WHEN AN OUTPUT OPERATION WAS REQUESTED FOR A DATASET. ***IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*** ***SE37 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(SE37-RC)** --POSSIBLE CAUSE-RAN OUT OF DIRECTORY SPACE IN A PDS OUTPUT EXCEEDED VOLUME COUNT

SE37 - 04 - A DATASET OPENED FOR OUTPUT USED ALL SPACE AVAILABLE ON THE CURRENT VOLUME, AND NO MORE VOLUMES WERE AVAILABLE: - NOT ENOUGH VOLUMES WERE SPECIFIED FOR THE DATASET THROUGH THE 'SER', VOLUME COUNT, OR 'REF' SUBPARAMETER OF THE VOLUME PARAMETER. WHEN ALL THE VOLUMES WERE FILLED, THE PROGRAM ATTEMPTED TO WRITE ANOTHER RECORD. - FOR A PARTITIONED DATASET ON A DIRECT ACCESS VOLUME, ALL SPACE WAS FILLED WHEN THE PROGRAM ATTEMPTED TO WRITE ANOTHER RECORD. (A PARTITIONED DATASET CAN RESIDE ON ONLY ONE VOLUME.) - FOR A PARTITIONED DATASET ON A DIRECT ACCESS VOLUME, 16 EXTENTS HAD BEEN USED WHEN THE PROGRAM ATTEMPTED TO WRITE ANOTHER RECORD; HOWEVER, NO VOLUME WAS AVAILABLE FOR DEMOUNTING.

SE37 - 08 - ON A DATASET OPENED FOR OUTPUT, END-OF-VOLUME HAD FOUND A DSCB WITH A DUPLICATE DATASET NAME ON THE NEXT VOLUME, WITH A VOLUME SEQUENCE NUMBER LESS THAN THAT IN THE DEB. - A MULTI-VOLUME PHYSICAL SEQUENTIAL DATASET WAS BEING WRITTEN ON A DIRECT ACCESS DEVICE. ALL SPACE WAS FILLED ON A VOLUME, AND AN ATTEMPT WAS MADE TO OBTAIN SPACE ON THE NEXT SPECIFIED VOLUME. EITHER THE SPACE WAS NOT AVAILABLE ON THAT VOLUME OR THE DATASET ALREADY EXISTED ON THAT VOLUME.

SE37 - 0C - AN INSTALLATION DADSM EXIT, IGGPRE00, REJECTED THE EXTEND REQUEST.

SE82 - DISABLED CODE WAS EXECUTING AND ISSUED RACHECK (SVC 130) WHICH IS INACTIVE BECAUSE RACF IS NOT INSTALLED ON THE SYSTEM.

SE83 - DISABLED CODE WAS EXECUTING AND ISSUED RACINIT (SVC 131) WHICH IS INACTIVE BECAUSE RACF IS NOT INSTALLED ON THE SYSTEM.

SE84 - DISABLED CODE WAS EXECUTING AND ISSUED RACLIST (SVC 132) WHICH IS INACTIVE BECAUSE RACF IS NOT INSTALLED ON THE SYSTEM.

SE85 - DISABLED CODE WAS EXECUTING AND ISSUED RACDEF (SVC 133) WHICH IS INACTIVE BECAUSE RACF IS NOT INSTALLED ON THE SYSTEM.

SF2D - OVERLAY SUPERVISOR - INVALID SUPERVISOR CALL BAD LOAD MODULE. RE-LINKEDIT ENTIRE MODULE.

SF37 - HARDWARE ERROR


Page 54

7/30/2008

More Details about ‘U’SER ABEND CODES U002

U016

* TEST HAS TERMINATED AND HAS FORCED TERMINATION OF ALL ACTIVE MESSAGE REGIONS AND BATCH MESSAGE REGIONS. * AFTER OPERATIONS HAS RESTARTED THE REGIONS, RESUBMIT USING CKPT. * WHEN USING SYSIN CARDS, YOU CANNOT HAVE COMMENT CARDS WITHIN SYSIN CARDS. REMOVE THE COMMENTS AND P=XCE THEM ELSEWHERE.

* WHEN USING WAAPDSUT, THERE ARE MAJOR ERRORS IN THE CONTROL CARDS * * * *

JOB REQUIRES MORE SPACE TO EXECUTE. ADD AMOUNT OF CYL ON EXECUTE STATEMENT AFTER PARM. EXAMPLE: CYL=50. SYSIN ON A SORT MAY HAVE TOO MANY ENTRIES. MAY BE SORTING BEYOND REC LENGTH WHEN WORKING WITH VAR RECORDS.

U047

* NO DATA BASE AUTHORIZATION.

U049

* CALL TO DBA GROUP TO BUMP UP BUFFER ALLOCATION.

U069

* * * *

U080

* ACF2 ON A DATASET. CHECK LOG IN EXECUTION WHEN TESTING WITH 'DLICHKPT' THE DD NAMES FOR YOUR DATABASE MAY BE INCORRECT. CHECK THE PSBLIB.

U089

* RESTART EVERYTHING.

U100

* WRONG USER CODE GENERATED BY PROGRAM. CHECK PROGRAM FOR PROBLEM. FIX IT AND CHANGE USER CODE TO A CORRECT PROGRAM GENERATED CODE.

U102

* CHECKPOINT NOT FOUND ON RESTART GO INTO IMSCHKPT, AND SET CHECKPOINT COUNTER TO ZERO IF YOU REALLY DON'T CARE TO RESTART. TO RESTART >>>> DO NOT CHANGE JOB NAME ON RESTART<<<<<<<<<< * MAYBE THE CHECKPOINT RECORD GOT DELETED BECAUSE YOU DID NOT TRY AND RESTART IMMEDIATELY. YOUR RESTART RECORD WAS ROLLED OFF THE RESTART FILE. * OPERATOR STARTED WRONG LOG TAPE. * ENSURE THAT THE MBR= IN BOTH DLICHKPT STEPS ARE THE SAME.

U103

* CHECKPOINT SAVE AREA LENGTH IS 0 OR NEGATIVE.

U134

* DEPENDANT REGION ISSUED AN IDENTIFY REQUEST WHEN CONTROL REGION SHUTDOWN WAS IN PROGRESS.(IMS TEST IS IN PROCESS OF COMING DOWN).

U205

* ERROR OCCURRED DURING A FORM OF FREEMAIN MACRO INSTRUCTION. * NO REAL STORAGE AVAILABLE FOR A REQUEST. TRY JOB AGAIN SAME ERROR CALL SYSTEMS GROUP.

U222

* CANCELLED BY OPERATOR.

U240

* THE EXECUTION (CPU TIME) ALLOTTED FOR A TRANSACTION HAS BEEN EXCEEDED. PROBABLY IN A LOOP.

U242

* INCORRECT GSAM, DATA COUNT TO LARGE. * SPECIFY DIRCA=ON BMP.

U250

* ONE OR MORE DATASETS NOT CLOSED AT THE END OF THE PROGRAM.

U259

* CHECK THE AMODE DATA IN THE LINKAGE EDITOR OUTPUT SHOULD BE (24) AMODE IF NOT SEEK HELP.

U260

* PCNT = 0 * IF COBOL PGM AND ON A OPEN STMT RECOMMEND DO NOT UES PCNT OPTION AND REMOVE ANY COMMAS IN THE STMT.

U261

* ADD 3 CHAMP LINK CONTROL STATEMENTS TO COBOL PROGRAM - STARTCTL: - LINKB4: ENTRY DLITCBL - ENDCTL: * ONE OF THE PARMAMETERS PASSED IN A DL/I CALL FROM THE APPLICATION PROGRAM TO IMS/VS IS INVALID. IT EITHER EXCEEDS OBJ MACH SIZE,DOES NOT MEET ALIGNMENT REQUIREMENTS, OR VIOLATES STORAGE PROTECTION BOUNDS. POSSIBLE PROBLEM CAN BE THAT A POINTER IS BEING USED TO POINT TO DB SEGMENT BUT WAS NEVER SET TO AN ADDRESS. * I/O AREA NAME OR SSA NOT DECLARED. * PCNT TO LARGE * MISSPELLED FUNCTION CODE * PCNT DECLARED AS FIXED BIN (15) RATHER THAN 31. * PCBNAME DOES NOT HAVE "P" AT END. * NO CMPAT=YES FOR BATCH.

ERROR FOR FAST PATH DATABASES CHECK R15 FOR RETURN CODE. RC 4 = RECURSIVE ENTRY TO INTERREGION COMM (IRC) OCCURRED RC 8 = F/P WAS UNAVAILABLE AND A F/P CALL WAS DETECTED NOTIFY DBA REPRESENTITIVE FOR CORRECTION.


Page 55

7/30/2008

* LEVEL NBR MISSING FROM FIELD IN STRUCTURE. * PROGRAM NOT LINKED AS AN 'IMS' PROGRAM.

U262

* BMP IGNORED A 'XD' STATUS FROM CHECKPOINT, WHICH MEANS THAT THE IMS SYSTEM WAS UNDERGOING A CHECKPOINT FREEZE OR SHUTDOWN.

U271

* INCREASE CHECK POINT RESTART LIMITS * POSSIBLE I/O ERROR ON GSAM FILE

U273

* COULD NOT PROCESS CHECKPOINT FILE. EITHER THE FILE IS BAD, OR IS NOT FOUND.

U322

* CPU TIME LIMIT EXCEEDED

U328

* PSB NOT DEFINED

U402

* BAD IMS CALL LIST * TP PCB MISSING IN PSB

U428

* #IMS STATEMENT DOES NOT MATCH PSB OR PGM DOES NOT HAVE A PSB PROGRAM NOT DEFINED TO THE SYSTEM. MAKE SURE PROGRAM WAS DEFINED TO THE SYSTEM (NUCREQ)

U430

* IS A RESULT OF TOO SMALL OF A REGION OR NO REGION SUPPLIED. * DFS0430 AND DFS0432 MESSAGES ARE ABOUT VSAM BUFFER POOLS TO CORRECT, SUPPLY REGION RECORD ON JOB CARD OF 1024 OR GTR. * TRY INCREASING THE SIZE OF THE REGION PARAMETER.

U452

* TRANSACTION STOPPED

U454

* PGM STARTED AFTER A SHUTDOWN CHECKPOINT HAD ALREADY STOPPED

U456

* PROGRAM/TRANSACTION IS STOPPED OR DCB LIBRARY TOOK AN EXTENT, CALL DBA FOR POINTER CHANGE TO NEW EXTENT AREA. * PSB NOT FOUND FOR PROGRAM. * LOOK AT TWDDB.OLSJIM15.PSBLIB(MEMBER) IF NOT THERE PROBLEM IN IOF LOOK AT OLSJIM15 (IMSTEST) THAT IS RUNNING IN THE (6) HARDCPY1 IF ZIP PSB, MUST BE IN DCBLIB. * THE PSB IN QUESTION MAY BE STOPPED BY A PRIOR PGM FAILURE IF DOPT, CN NOT BE IN ACBLIB ... ONLY IN DBDLIB. * PSB STOPPED * PROGRAM WAS STOPPED WHEN EXECUTING.

U457

* PSB WAS SCHEDULED IN ANOTHER REGION.

U458

* DB USED BY A BMP IS STOPPED. * IMS TAKEN DOWN WHEN PROGRAM EXECUTING. * '/STOP REGION N ABDUMP’ WAS USED TO CANCEL JOB

U476

* #IMS STMT DOES NOT MATCH PSB OR DLI CALL ARGUMENTS COUNT WRONG DLI CALL ARGUMENTS NOT IN CORRECT ORDER. * MAY NEED TO ADD LINKB4 CARDS FOR CHAMP 3.1 COMPILES A DL/I CALL DOES NOT INCLUDE A VALID PCB ADDRESS. * POSSIBLE CAUSE IS THAT NUMBER OF PCBS IN PSB DO NOT MATCH THE #IMS STATMENT IN THE PROGRAM. IF THEY DO, ALSO CHECK IF DBA ADDED A TP DEFINITION IN THE PSB GEN. IF SO, ANOTHER TPPCB MUST BE ADDED TO THE PROGRAM #IMS STATEMENT. * IF YOU ARE MAKING A DLI CALL FROM A SUBPROGRAM, MAKE SURE THE "USING" LIST OF ARGUMENTS IN THE MAIN PROGRAM'S CALL STATEMENT MATCHES THE "USING" LIST IN THE SUBPROGRAM'S ENTRY STATEMENT * CHECK LANGUAGE TYPE IN PSB * CMPAT = YES FOR BATCH ONLY * PSB CHGED TO ADD GSAM D/B, BUT JCL/PGM NOT CHGED. ABENDS AT CHKPT MUST NOT HAVE>CMPAT=YES FOR TRANSACTION * INVALID DB PCB NAME. * DCB'S MISSING ON GSAM D/B. * NBR OF PCBS IN PSB DOES NOT AGREE WITH #IMS IN PROGRAM * INVALID FUNCTION CODE. * PSB ADDRESS NOT ESTABLISHED (I.E. GSAM PTR) * NO LEVEL NBRS ON THE ELEMENT FIELD NAMES IN THE STRUCTURE. * IF PROGRAM IS COBOL CONSIDER THE FOLLOWING. SEE THAT THE DATA: CONTENT IN THE LINKAGE SECTION IS IN LINE WITH THE PSB AND CONTENT IN THE ENTRY SECTION IS IN LINE WITH THE PSB * ENTRY STATEMENT DOES NOT MATCH PSB * MAKING A CALL TO A DB NOT DEFINED IN THE ENTRY STATEMENT OR PSB. (EX. SECONDARY INDEX DB) * ENSURE CALL HAS A DATABASE POINTER NAME * PROGRAM WAS NOT COMPILED AS AN IMS PROGRAM, RECOMPILE AND TRY AGAIN.

U477

* IMS BMP DOING GETMAINS FOR MORE SPACE DURING EXECTION, ABENDS WHEN SPACE NOT AVAILABLE. JUST HAVING PROGRAM RESTARTED MAY SOLVE YOUR PROBLEM.

U499

* MAXIMUM INSERT CALL COUNT EXCEEDED. A "A7" STATUS IS RETURNED CHECK APP. PGM AND MAKE SURE IT RECOGNIZES A7 OR INCREASE THE


Page 56

7/30/2008

MAX. INSERT COUNT SPECIFIED IN THE TRANSACT MACRO AT SYSGEN.

U502

* START TRANSACTION AND PROGRAM AND TRY AGAIN. * WAASABND WAS CALLED WITH ABEND CODE WITH PIC S9(04) COMP AND IT SHOULD HAVE BEEN PIC S9(09) COMP

U513

* IF ISRTING A MSG TO A PRINTER INCLUDE A OUTBUF=9000 ON YOUR ./D CARD WITHIN YOUR BTS CONTROL CARDS. BE SURE TO USE THE "MDL" OPTION WITH "P1" OR "P2" IF YOU ARE NOT USING MFS OR "TYPE=SCS1" IF YOU ARE USING MFS FOR THIS MSG.

U551

* GSAM PCBS WERE PRESENT BUT DEPENDENT REGION IS NOT A BMP. CHECK YOUR PSB, PROBABLY GENNED AS BMP. DBA MUST REDO THE PSB.

U616

* I/O AREA LGTH TOO SMALL, ABEND AT XRST CALL. * LOG DATASETS ARE FULL, INCREASE CHECKPOINT LIMIT.

U662

* FIRST POSITIONAL VALUE IN PARM FIELD IS INVALID. TRIED TO USE * EXEC PGM=A0770, PARM=ISASIZE (4K), R) IN JCL.

U688

* IMS DOWN WHEN JOB STARTED, OR YOU ARE SUBMITTING UNDER SYTEM 'N' AND THE JOB NEEDS TO RUN UNDER SYSTEM '7' OR VICE VERSA. * OPERATOR CANCELLED IN RESPONSE TO MESSAGE DFS690A. IMS CONTROL REGION NOT ACTIVE. * OPERATOR CANCEL. IMS IS DOWN. * IF RUNNING TESTBTCH OR MDLDBTCH ON SYSTEM N, MUST HAVE A SYSAFF=AHI7 ADDED TO THE JOB'S JOBPARM STATEMENT.

U717

* REGION SIZE POSSIBLY TOO SMALL.

U722

* CANCELLED BY OPERATOR * LINES PRINTED, EXCEEDS LIMIT

U742

* PROBLEM WITH IMS. CALL IMS GROUP.

U752

* AN ISAM SETL MACRO CALL WAS ISSUED SPECIFYING THE KEY WHICH INITIATES THE DATA SET. A MESSAGE WAS RETURNED WITH THE NEXT HIGHER KEY IN THE DATA SET, INDICATING THAT THE ERROR CONDITION WAS NOT FOUND. A SECOND SETL ALSO FAILED BECAUSE OF THE ERROR NOT BEING FOUND. THE SECOND SETL MAY HAVE FAILED BACAUSE THE DATABASE WAS NOT COMPLETELY LOADED OR BECAUSE THE DD STATEMENT FOR THE DATA SET SEPCIFIED FECFM = F INSTEAD OF RECFM = FB. RESPONSE IN SYSTEM MANUAL: RELOAD DATA BASE SPECIFYING RECFM=FB.

U758

* MESSAGE QUEUE DATASET FULL.

U769

* SERIOUS SYSTEM ERROR. DO A RESTART. * REFER TO S322. TIME ALLOTMENT EXCEEDED. INFINITE LOOP?

U775

* UNABLE TO AQUIRE A BLOCK OF STORAGE FOR QUEING CONTROL BLOCKS. * THE ENQUEUE TABLE IS FULL. * PROGRAM IS NOT TAKING ENOUGH CHECKPOINTS. DECREASE YOUR CHECKPOINT COUNT IN THE PROGRAM CAUSING THE ABEND.

U777

* IMS CHOSE YOUR PGM TO TERMINATE TO AVOID A DEADLOCK. HAVE JOB RESTARTED.

U778

* AN SQL ERROR OCCURED AND THE ABORT ROUTINE WAS CALLED. THE ABORT ROUTINE ISSUED A ROLLBACK COMMAND WHICH GIVES THE U778 CODE. TO SEE THE REAL SQL CODE IN ERROR VIEW DATASET PRPAC.DBAUF.ABORTTEST(0) THE DAY AFTER THE ABEND, OR CALL YOUR LOCAL IBM DBA TO CREATE THIS DATASET FOR YOU. * IF ONLINE PRESS PA2 KEY. THIS WILL SHOW YOU THE ERROR.

U779

* TO MANY "Q" COMMANDS BETWEEN CHECKPOINT

U80A

* REGION SIZE TOO SMALL

U801

* DATABASE NOT OPENED FOR UPDATE.

U806

* INVALID RETURN FROM BUFFER HANDLER. * (GSAM NAME) GSAM DBD IS NOT PRESENT OR THE ACB GEN WAS NOT PERFORMED TO DCBLIB. * INCORRECT JOBLIB/STEPLIB OR PROGRAM WAS NOT LINKED.

U811

* DLETE/REPLA ATTEMPING TO CHANGE A POINTER IN A SEG'S PREFIX. * IT FOUND THAT THE OLD VALUE OF THE POINTER WAS NOT AS EXPECTED. * PRIOR POINTER MAINTANCE WAS ERRONEOUS.

U813

* DATA SET NAME ON TAPE DOESN'T MATCH ONE SPECIFIED IN JCL

U840

* THERE IS A PROBLEM WITH A BMC PRODUCT THAT UTILIZED DATA PACKER. CONTACT DBA! THIS IS NOT A PROGRAM PROBLEM.

U844

* NOT ENOUGH SPACE ON DATABASE


Page 57

7/30/2008

* NO AVAILABLE SPACE IN DATA SET * DATABASE FULL * DATABASE MAY BE FOUND IN I.OLSJIM15 (IMSTEST) (HARDCPY1), MAX. TO THE BOTTOM AND FIND 'DATASET FULL' PREV. CALL A DATA BASE ADMIN PERSON.

U850

* LIKE B37, RAN OUT OF SPACE ON THE GSAM FILE

U852

* * * *

U853

* BAD POINTERS ON THE DATA BASE. * DATABASE CLOBERED BY BTS TEST BECAUSE OF AN INVALID BACKOUT.

U888

* WHEN USING F.A.T.A.R. : FATAR HAS ABENDED DUE TO A SERIOUS ERROR. GO TO THE BOTTOM OF SYSPRINT FOR ABEND DETAILS. * CORE UNAVAILABLE.

U905

* INSUFFIEIENT STORAGE FOR PSB (INCREASE REGION SIZE)

U913

* THE NAMED DBD CONTAINS AN INVALID OR UNKNOWN ACCESS METHOD.

U929

* BLDL FAILED *CAN NOT FIND MBR TO BUILD FROM (PSB/DBD LIB)

U999

* WRONG LRECL ON INPUT DATA SET OF A SORT STEP. * ONE OF THE DATA SETS THAT IS INPUT TO THE SORT MAY BE EMPTY. * IF THE ABOVE TWO CONDITIONS ARE FALSE, AND THE JCL IS USING A ROUND TAPE DRIVE (UNIT=TAPE9) AS AN OUTPUT FILE, THE PROBLEM COULD BE BECAUSE THE TAPE DRIVE IS DIRTY. HAVE AUBURN HILLS CLEAN THE TAPE DRIVE AND TELL YOUR SUPERVISOR!!!! * IF USING PGM SSGPXLBL, MAKE SURE DSNAMES IN JCL MATCH DSNAMES IN SYSIN CARDS.

U0016

* WHEN USING WAAPDSUT, THERE ARE MAJOR ERRORS IN THE CONTROL CARDS CONCAT. DATA SETS ON A SORT. FIRST DATA SET DOES NOT CONTAIN THE LARGEST BLOCKSIZE. * JOB REQUIRES MORE SPACE TO EXECUTE. * SYSIN ON A SORT MAY HAVE TOO MANY ENTRIES. * MAY BE SORTING BEYOND REC LENGTH WHEN WORKING WITH VAR RECORDS. * IF USING SYNCSORT, CHECK 'SYSOUT' MESSAGES WITH SYNCSORT MANUAL SYNCSORT: CHECK LRECL OF SORTIN AND SORTOUT FILES. SYNCSORT: USE PARM VLTEST=0 SO WON'T VERIFY THE LRECLS

U0102

* SEE U102

U0211

* JCL IN 'ALWAYS LOAD' DATASET, BUT NO PROC IN CHAMP

U0250

* ONE OR MORE DATASETS NOT CLOSED AT THE END OF THE PROGRAM.

U0271

* SEE U271

U0428

* SEE U428

U0457

* SEE U457

U0474

* SEE U474

U0688

* SEE U688

U0777

* SEE U777

U0844

* SEE U844

U0999

* SEE U999

U1002

* I/O EXCEPTION *CHECK TO SEE IF RECORD LENGTH IN PROGRAM AND RECORD LENGTH OF FILE ARE THE SAME. * REGION SIZE MAY BE TOO SMALL FOR SORT.

U1005

* MIXED PROGRAM CALLS OF DYNAMIC AND STATIC CALL, IMPROPER LINK OR, IN COBOL A RECENT COMPILE (AFTER 7/90) HAS MIX OF RES/NORES

U1012

* PROGRAM STOPPED BEFORE SORT WAS FINISHED, CHECK TO SEE IF PROGRAM FALLS THRU. ADD A SECTION AFTER THE SORT EXIT.

U1026

* POINTERS IN YOUR DATABASE ARE MUCKED UP. CALL DBA!!!

U1033

* FASTER PATH DATABASE BUFFERS NEEDED. INCREASE NBA/OBA IN THE DEPENDENT REGIONS JCL. IF A TRANSACTION THEN ASSIGN TO A DIFFERENT CLASS SO THAT IT RUNS IN A REGION WITH MORE NBA/OBA.

U1999

* DYNAMICALLY CALLED MODULE HAS EXPIRED 'WAASDATE'

DATA BASE CORRUPTED. BAD POINTER DAMAGED DATABASE WRONG DBD BEING USED


Page 58

7/30/2008

U2301

* CHECK IMS RETURN CODES FROM DATABASE CALLS.

U2750

* LINK CANNOT FIND A CALLED SUBROUTINE. * IF LATE AT NIGHT, THE SYSTEM MAY BE COMING DOWN. * MAY ALSO INDICATE PSB IS MISSING.

U2810

* INSUFFICIENT SPACE FOR WORK FILE, SEE IOF FOR FILE.

U3072

* NEEDS MORE RESOURCES THAN ALLOWED

U3303

* THIS USER ABEND BASICALLY MEANS THAT ONE OF THE APPLICATION DATA BASES IN YOUR PSB IS STOPPED. WHEN YOUR APPLICATION GOES AFTER IT, SOME SORT OF SUBTASK ABEND OCCURS. * BEFORE CURRENT RELEASE OF IMS THE PGM WOULD ABEND ON A U458. * MEANS THAT THE PGM WILL RUN UNTIL A DATABASE THAT IS NEEDED IS NOT AVAILABLE. * ENSURE THAT THE ENTIRE NEEDED DATABASE ARE UP AND RUNNING. * DB USED BY A BMP IS STOPPED.

U3560

* DATAVANTAGE ERROR DUE TO LACK OF CHECKPOINT ROUTINE FOR UPDATES ADD TO EXEC STMT: ,MBR=DV1CHKP AS NOTED ABOVE FOR UPDATE ONLY. YOU MAY NEED TO ADD THE PARMS "NBA=4 AND OBA=4" IF PROCESSING AGAINST FAST PATH DATABASES.

U3561

* MAY NEED TO CHANGE DBD IN DVAN SEGD HEADER RECORD TO POINT TO CORRECT DBD FOR TEST VERSION. * DVAN RAN OUT OF BUFFERS. INCREASE NBA AND OBA PARMS.

U3592

* BTS TEST RAN OUT OF BUFFERS.

U1006

* JOB IS ASKING FOR MORE FAST PATH BUFFERS (NBA) THAN IS CURRENTLY AVAILABLE * USE IMS COMMAND "/DIS POOL FPDB" AND LOOK AT "UNFIXED" TO DETERMINE HOW MANY BUFFERS ARE CURRENTLY AVAILABLE. YOU MUST THEN REDUCE THE JOB NBA PARAMETER TO REQUEST NO MORE THAN WHAT IS "UNFIXED" OR WAIT FOR OTHER JOBS TO END AND THUS FREE UP MORE BUFFERS........ RFS 2/6/90

U1008

* SYNC CALL HAD TO BE MADE AT END OF RUN. THIS IS FOR EITHER AN UPDATER OR AN INQUIRY BMP. FOR IFP MESSAGE DRIVEN APPLICATION PROGRAMS AND MPPS PROGRAM RETURNED NORMALLY BUT WITHOUT A QC STATUS CODE POSTED IN I/O PCB OR WITHOUT RELEASING FAST PATH BUFFERS. * SOLUTION: RETURN CONTROL TO IMS ONLY AFTER A QC STATUS CODE IS RETURNED IN I/O PCB OR AFTER ISSUING A SYNC OR ROLB CALL TO RELEASE BUFFERS.

U1016

* DD CARD IN THE JCL IS MISSING

U1017

* PSB IS MISSING OR DOES NOT MATCH THE PROGRAM * DD CARD IN THE JCL IS INCORRECT * FOR COBOL, OPEN OF DISPLAY/ACCEPT FILE WAS UNSUCCESSFUL. CHECK IF THE DDNAME IS SUPPLIED IN THE JCL OR CLIST IF RUNNING BTS YOU NEED A "SYSOUT(D)" ON THE PROC LINE OF YOUR BTS CLIST

U1020

* THE PROGRAM TRIED TO READ PASS THE END OF FILE MARKER ON THE INPUT RECORD * THE PROGRAM TRIED TO CLOSE AN UNOPENED FILE * THE PROGRAM TRIED TO OPEN AN ALREADY OPENED FILE * FOR GSAM FILE, MAKE SURE THE DCB IS INCLUDED ON THE INPUT DD STATEMENT * ADD SORTWK DD STATEMENTS TO JOB STEP USING PRINT UTILITY (DMGPRPT). * THE PROGRAM ABENDED ON A CLOSE STATEMENT BECAUSE THERE WAS NOT ENOUGH SPACE IN THE FILE FOR EOF MARK

U1034

* FILE SECONDARY ALLOCATION LIMIT ENCOUNTERED....... * WRONG DDNAME IN JCL OR IN COBOL FD IS MISSING BLOCK CONTAINS * OR, AN OPEN ERROR HAS OCCURED. THIS MAY BE BECAUSE YOU ARE PROCESSING A VARIABLE BLOCKED FILE AND THE RECORD LENGTH IN YOUR PROGRAM FD DOES NOT MATCH THE VB FILE'S LRECL MINUS FOUR OR, CHECK JCL FOR IMPROPER RECORD LENGTH

U1320

* ERROR WRITING CHECK POINT, INCREASE REGION ON STEP OR JOB

U1055

* DD NAME IS MISSPELLED OR MISSING

U1525

* NOT CAT2 CONDITION DURING A CHECK POINT/RESTART EXECUTION

U1806

* CHECK THE GSAM FILE NAME MATCES DD NAME IN JCL

U2047

* PROD REGION W/TEST PSB (OR IMS DATASET) OR VICE VERSA. * REGION AND PSB/DATASET MISMATCH.

U2658

* BMC2658, CANNOT FIND SEGMENT NAME IN DBD FOR RELOAD


Page 59

7/30/2008

U2749

* BMC2749, OPEN FAILURE ON DDNAME '

U2871

* REGION SIZE IS NOT LARGE ENOUGH * INCREASE IT

U3001

* TRYING TO USE GENERATION DATA GROUPS IN TESTLIB?. CANNOT. * ABEND AID: ISSUED BY PL/I AFTER NORMAL RETURN FROM AN ERROR, OR FINISH ONUNIT FOR ERROR ONCODE 0084. CHECK SYSPRINT, OR ABEND-AID

U3007

* ABEND DURING AN ASSEMBLY OF A MFS SCREEN. * DIRECTORY BLOCKS ARE FULL. * IMSVS1.TEST.TFORMAT DATASET IS FULL. DELETE UNNEEDED MEMBERS IN DATASET AND RETRY.

U3300

* STORAGE SPACE FOR DATABASE ENQUEUES HAS BEEN FILLED UP. ALL IMS PROGRAMS CURRENTLY RUNNING WILL ABEND. CAUSE IS: AN UPDATE BMP IS NOT CHECKPOINTING FREQUENTLY ENOUGH. THE SYSTEM DOES NOT IDENTIFY WHICH BMP IS AT FAULT. OLD ABEND CODE WAS U775.

U3303

* INSTEAD OF U458 WHEN PROGRAM IS ACCESSING A DATABASE THAT HAS BEEN STOPPED. TRAN PUT ON SUSPEND QUEUE. DO A /STA TRAN COMMAND AFTER DATABASE IS BACK UP

U3500

* GENERIC USER ABEND CODE USED FOR PROGRAMMER FORCED ABENDS * CHECK SYSOUT FOR DESCRIPTIVE ERROR MESSAGES DISPLAYED BY PROGRAM REPLACEMENT OF THE COMPUTE XXX = 1 / 0 STATEMENT

U3501

* INVALID PARM LENGTH OR VALUE

U3502

* ERROR DETECTED BUT NO ABEND; RETURN CODE SPECIAL * REGISTER SET TO 3502 AND INTERROGATED IN THE JCL TO EXECUTE WAASABND.

U3503

* ENCOUNTERED STOP AND/OR ACCEPT STATEMENT

U3504

* AFTER ANY INVALID RETURN CODE FROM "WAASDYN"

U3505

* WHEN THE CHECKPOINT LIMIT RECORD IS INVALID

U3506

* RESERVED AS THE STANDARD JCL PARM= VALUE FOR PROGRAM "CURPB002"

U3507

* INVALID SQLCODE VALUE AFTER EXECUTION OF ANY SQL CODE IN TSO BATCH DB2 APPLICATION PROGRAMS

U3508

* USED BY CURSU002 (DATE/TIME) WHEN A BAD RETURN FROM WAASDATE IS FOUND.

U3509

* REPLACEMENT OF SETTING THE ATTRIBUTE STATUS TO "*1" IN BATCH COBOL PROGRAMS.

U3510

* AFTER ANY INVALID RETURN CODE FROM "DM028X"

U3511

* USER ABEND IN "BATCH PRINT" PROGRAM

U3512

* DATA SET EMPTY

U3513

* SSDPDB2Q.INVALID FUNCTION CODE PARM

U3514

* SSDPDB2Q.UNSUCCESSFUL DEQUEUE

U3515

* ANY NON*DATABASE RELATED TPS ERROR IN TSO BATCH APPLICATION PROGRAMS

U3516

* BAD RETURN FROM CURSU002 IN CALDATE CALL REPLACEMENT.

U3517

* RETURN CODE INDICATING AN UNSUCCESSFUL CALL TO WAASCTLM.

U3518

* INTERNAL TABLE LIMIT EXCEEDED.

U3501

* GENERIC USER ABEND CODE USED FOR PROGRAMMER FORCED ABENDS * CHECK SYSOUT FOR DESCRIPTIVE ERROR MESSAGES DISPLAYED BY PROGRAM

U3506

* NO TIE CONDITION FOR ELECTRONIC TIEINS

U3514

* BAD RETURN FROM ISRT TO RI7ORDR

U3516

* BAD RETURN FROM GHU TO RI7PRGM

U3550

* BAD RETURN FROM CHKPT/RSTR CALL TO COCSS03


'.

Page 60

7/30/2008

U3599

* BAD RETURN FROM DB CALL

U3600

* BAD RETURN FROM OPEN OF GSAM FILE

U3604

* THE ABEND-CODE SENT TO WAASABEND WAS TOO HIGH * ONLY 1 THRU 4905 IS ACCEPTABLE

U3650

* BAD RETURN FROM CLOSE OF GSAM FILE

U3700

* BAD RETURN FROM READ OF GSAM FILE

U4000

* CHECK DISPOSITION OF FILES BEING USED FOR POSSIBLE NOT CATLG2 ERROR WITH FIRST XRST CALL TO CHECKPOINT.

U4002

* PSB AND CONTROL NUMBER DO NOT MATCH * CHECK THE PROGRAM NAME. DO NOT ADD 'T'!

U4006

* IMS BATCH ABEND, ONE OR MORE FILES WERE NOT CLOSED AT END.

U4011

* TC UPDATE ABEND, CURRECT UPDATE JOB NOT ZERO, ANOTHER UPDATE JOB WAS RUNNING. PLEASE FOLLOW RESTART INSTRUCTIONS AFTER OTHER UPDATE JOB IS DONE. HAVE A NICE DAY!!!!!

U4028

* INVALID ISA SIZE. INITIAL STORAGE AREA NOT LARGE ENOUGH.

U4032

* GSAM FILE NOT SPECIFIED IN PSB * IF ACCESS TO CHAMP LOST: LOGOFF/LOGON TO RESET POINTERS.

U4036

* ERROR IN IBM ERROR HANDLING ROUTINE. (CHECK STMT TO DEBUG) * A PROGRAM CHECK OCCURRED DURING AN IMS CALL STATEMENT. * REGISTER 2 POINTS TO THE PIE/EPIE. SUGGESTION TO PUT A CHECK STATEMENT ON EACH PROC TO DETERMINE WHICH PROC ABENDED. * SYSTEM USUALLY WILL NOT REFLECT WHERE THE ABEND OCCURRED. * BE SURE THAT YOU ARE EXECUTING "EXEC TESTBTCH, MBR=XXXXXX" * CHECK DCB INFO IS PRESENT AND CORRECT IN JCL. LRECL, BLKSIZE * BE SURE THAT PROGRAM HAS CORRECT DATA SET TYPE IN CHAMP.

U4048

* CHECK THAT A TABLE (ARRAY) IS NOT BEING OVERFILLED ALSO.

U4050

* THE IMP2CNTL DD STATEMENT WAS NOT PROVIDED OR IS DUMMY.

U4051

* THE IMP1LIST DD STATEMENT WAS NOT PROVIDED.

U4052

* FILE DD MISSING ON JCL (IMP1)

U4078

* THE CHKPM VALUE SPECIFIED IN THE CHKP OPERAND OF MI1UDATA WAS EXHAUSTED PRIOR TO THE ARRIVAL OF A SEQUENCED UNIQUE SEGMENT. * EXAMINE AND ADJUST MI1UDATA CHECKPOINT PARAMETERS.

U4094

* HARDWARE ERROR; CORRECT IT, RESTART AND TRY AGAIN.


Page 61

7/30/2008

MAINFRAME ABEND CODES and DETAILS - All in one

Recommend Documents