Messages and Diagnostics

ABA00

PROGRAM CHECK INTERRUPTION WHILE PROCESSING I/O REQUEST

ABA03

WHEN TASK ATTEMPTED TO TERMINATE, ONE OR MORE SUBTASKS NOT TERMINED

ABA05

AREA TO BE FREED BY FREEMAIN MACRO OVERLAPPED

Explanation: Free area in virtual storage or part of the area was still fixed in real storage.

ABA06

PRIOR REQUEST FOR QUEUED MODULE NOW REQUESTED BY LINK, LOAD, ATT OR XCTL MACRO

ABA0A

R-TYPE FREEMAIN MACRO SPECIFIED AREA THAT OVERLAPPED

Explanation: Free area in virtual storage or part of area was still fixed in real storage.

ABA13

DATA SET REQUESTED BY OPEN MACRO NOT FOUND (TAPE ONLY)

ABA14

CLOSE MACRO ENCOUNTERED I/O ERROR WHILE ATTEMPTING PARTIAL RELEASE OF SPACE IN DASD

CAMRA011

NO MEMBERS IN LIBRARY

Explanation: The library specified contains no members.

CAMRA012

NO MATCHES

Explanation: The pattern specified produced no matches.

CAMRA013

CAN'T OPEN LIBRARY

Explanation: An error occurred when opening specified library.

CAMRA014

FREED

Explanation: All possible ddnames were freed.

CAMRA028

MEMBER IS EMPTY

Explanation: The member does not contain any JCL.

CAMRA029

NOT AN EXEC STATEMENT

Explanation: Selected statement is not a valid JCL statement.

CAMRA033

CANNOT LOAD JCLCHECK

Explanation: Load module JCLCHECK cannot be found or loaded.

CAMRA034

NO PROCLIB

Explanation: You must supply at least one PROCLIB

CAMRA035

INVALID DSN

Explanation: The data set name is not valid.

CAMRA036

DDNAME NOT ALLOCATED

Explanation: The ddname specified was not pre-allocated as required.

CAMRA037

SELECTION NOT ALLOWED

Explanation: Member selection list is not allowed; member name is required.

CAMRA038

SOME ALLOCATIONS FAILED

Explanation: Review for highlighted allocations errors.

CAMRA090

DDNAME REQUIRED

Explanation: Data set cannot be allocated without ddname.

CAMRA092

BROWSE/EDIT ERROR

Explanation: ISPF is unable to browse or edit selected data set.

CAMRA093

INVALID LINE COMMAND

Explanation: Enter ALLOCATE, BROWSE, CONVERT (CLIST), EDIT, or FREE.

CAMRA094

INVALID LIBRARY TYPE

Explanation: Only PDS, CA Librarian, and CA Panvalet are supported.

CAMRA095

NOTHING TO ALLOCATE/FREE

Explanation: The member contains only messages or empty lines.

CAMRA097

NO ALLOS TO ALLOCATE

Explanation: ALIB member is empty or contains only message allos.

CAMRA098

INTERNAL ERROR - PLIST

Explanation: Invalid PLIST supplied.

CAMRA099

CANNOT LOAD FAIR/OPEN ERROR

Explanation: Cannot load CA Librarian FAIR modules or OPEN failed.

CAMRA101

INVALID LINE CMD

Explanation: Enter BROWSE, EDIT/SELECT, ALLOC, FREE, or CONVERT.

CAMRA102

MEMBER NAME REQUIRED

Explanation: Enter a member name in the provided field.

CAMRA103

MEMBER REPLACED

Explanation: Member was replaced in data set.

CAMRA104

INVALID LINE CMD

Explanation: Enter F to free, B to browse, or E to edit.

CAMRA105

INVALID LINE CMD

Explanation: Enter B to browse or S to select for JCL conversion.

CAMRA107

INVALID LINE CMD

Explanation: Enter I, D, R, S, AL, or F line command.

CAMRA301

OPEN ERROR

Explanation: OPEN failed for ALIB library.

CAMRA302

MEMBER NOT FOUND

Explanation: Requested member was not found in library.

CAMRA303

FIND ERROR

Explanation: FIND caused an error other than not found.

CAMRA304

INVALID RECORDS

Explanation: Invalid ALLO records found in member.

CAMRA305

EMPTY MEMBER

Explanation: Member requested contains no records.

CAMRA306

NEW MEMBER

Explanation: Member not found in library; new member created.

CAMR910E

SYM RECORD WITHOUT SYMBOLIC OPERAND

CAMR911E

SYM REPLACEMENT RECORD NOT FOUND

CAMR912E

“PGM=” NOT FOUND IN PROGRAM RECORD

CAMR914E

IBM DB2 “SYSTSIN” DD NOT FOUND

CAMR915E

IBM DB2 “LIB” STATEMENT ERROR

CAMR916E

IBM DB2 “LIB” STMT INVALID DSNAME

CAMR917E

IBM DB2 “PROGRAM” STATEMENT ERROR

CAMR950I

SVC INTERCEPT INSTALLED SUCCESSFULLY

CAMR951E

SVC NUMBER WAS NOT SPECIFIED

CAMR952E

INVALID ARGUMENT LENGTH

CAMR954E

VALUE OUT OF RANGE (MUST BE 200-255)

CAMR955E

UNABLE TO LOAD SVC INTERCEPT MODULE

CAMR956E

UNABLE TO LOAD SVC INTERCEPT PROLOGUE

CAMR957E

UNABLE TO INSTALL SVC INTERCEPT

CAMR960E

SYSTEM NOT INITIALIZED FOR BATCH LINK, REPLY “RETRY” OR “CANCEL”

CAMR961E

INT1OPTS DD MISSING OR INVALID

Explanation: The INT1OPTS DD statement was not included in the JCL for a Batch Link step, or the file referenced by the DD statement is the wrong format for Batch Link options. Correct the JCL and resubmit the job.

CAMR962E

EXEC= OPTION MISSING OR INVALID

Explanation: The INT1OPTS DD statement did not contain any EXEC= option, or the name specified was invalid. Correct the JCL and resubmit the job.

CAMRS01W

BLSCHTBL NOT ANCHORED.

Explanation: Batch Link Schedule table not created and anchored off the CAAT. Review the initialization job log to determine cause. Rerun the initialization after correcting the cause.

CAMRS02E

INT1SKUT DD NOT FOUND.

Explanation: The DD statement with INT1SKUT name was not found in the job stream. Correct error and rerun the appropriate job.

CAMRS03E

CANNOT DETERMINE DSORG. EXPORT ABORTED.

Explanation: Export operation has aborted because the DSORG of the dataset pointed to by INT1SKUT DD statement is unknown. DSORG must be either PS or PO.

CAMRS04E

INVALID MEMBER NAME SPECIFIED FOR SEQUENTIAL DATASET. EXPORT ABORTED.

Explanation: Export operation has aborted because a member name was specified for a sequential dataset. Correct the error and rerun Export.

CAMRS05E

PDS WITH NO MEMBER NAME SPECIFIED.

Explanation: Schedule found a partitioned dataset but there was no member name specified. Correct the error and rerun the job.

CAMRS06I

SCHEDULE EXPORTED TO ==> xxxxx

Explanation: Schedule is being exported to an external dataset named xxxxx.

CAMRS07I

TOTAL RECORDS EXPORTED TO INT1SKUT DD: nnnn

Explanation: During a Schedule Export operation, nnnn records were exported to the INT1SKUT DD.

CAMRS08I

BLSCHTBL IS EMPTY.

Explanation: Batch Link Schedule Table was found anchoring off CAAT, however it does not contain any active schedules.

CAMRS09E

DSORG NOT SUPPORTED, EXPORT ABORTED.

Explanation: Schedule Export operation has aborted due to the DSORG of the dataset pointed to by INT1SKUT DD statement is of a type not supported. DSORG must be either PS or PO.

CAMRS10I

INT1SKUT DD OPENED.

Explanation: Informational message.

CAMRS011I

INT1SKUT DD OPEN FAILED.

Explanation: The dataset pointed to by the INT1SKUT DD statement cannot be opened. Determine cause and rerun the job.

CAMRAS12I

RECORD SKIPPED. INVALID DB TYPE

Explanation: Schedule IMPORT operation found an import record with an invalid TYPE. The record is not imported.

CAMAS13I

IMPORT DSN ==> xxxxx

Explanation: xxxxx is the fully qualified dataset containing the Schedule to be imported.

CAMRS14W

SCHEDULE IMPORT NON ZERO RC = nn

Explanation: Import operations received a non zero return code of nn. Possible RC from Import:

0 = Import successful

4 = BLSCHTBL either is not anchored or does not exist

8 = INT1SKUT DD statement is missing.

CAMRS15I

RECORDS READ FROM INT1SKUT DD: nnnnn

Explanation: During a Schedule Import operation, nnnn records were imported

CAMRS16I

BATCH LINK SCHEDULE IMPORTED

Explanation: Informational Message.

CAMRS17I

SCHEDULE WILL BE IMPORTED TO REFRESH BLSCHTBL

Explanation: The default refresh option will be used to import the Schedule.

CAMRS18I

SCHEDULE WILL BE ADDED TO BLSCHTBL.

Explanation: ADD option specified by the Execution PARM is used to add from external dataset to the current active schedules in CSA.

CAMRS19E

INT1SKUT DD OPEN FAILED.

Explanation: Open of dataset pointed to by INT1SKUT DD card failed.

CAMRS20E

INT1SKUT DD CARD NOT FOUND.

Explanation: INT1SKUT DD card is missing from the execution JCL. Make sure the DD Name is correctly spelled.

CAMRS20E

BATCH LINK SCHEDULE NOT IMPORTED.

Explanation: For reasons stated in previous messages, the Batch Link Schedule was not imported.

CAMRS21I

INT1SKUT CLOSED.

Explanation: Informational message.

CAMRS22W

BLSCHTBL NOT ANCHORED.

Explanation: The Batch Link Schedule table is not anchored off CAAT. Review the initialization job log to determine cause. Correct error and rerun export operation.

CAMRS23I

SP241 ACQUIRED AT ADDR ==> xxxxxxxx

Explanation: Information. Subpool 241 at address xxxxxxxx was acquired for Batch Link Schedule in-core table.

CAMRS24E

#CAAT ADD CA ANCHOR FAILED. RC=nn

Explanation: The #CAAT facility to add Batch Link Schedule table failed. Return code is nn. Make sure the initialization program, MR85INIT, is executing out of an APF authorized library.

CAMRS25W

SP241 GETMAIN FAILED.

Explanation: GETMAIN for Subpool 241 storage failed. This could be caused by excessive number of entries defined in BLSCHTBZ. Each entry requires 27 bytes. Another likely cause - your CSA is over utilized. Discuss this issue with your Systems Programmer.

CAMRS26I

ACQUIRED SP241

Explanation: Informational message.

CAMRS27I

CA ANCHORED ADDED.

Explanation: Informational. The Batch Link Schedule table was successfully anchored by the initialization routine.

CAMRS28W

CAMBSTBZ LOAD FAILED. SCHEDULING DISABLED.

Explanation: LOAD of CAMBSTBZ table failed, Batch Link Scheduling facility has been disabled. Make sure the load library containing CAMRBSTBZ is in the STEPLIB concatenation stream. Rerun the initialization routine.

CAMRS29I

MAXIMUM SCHEDULE ENTRIES DEFINED: nnn

Explanation: Your installation has defined nnn as the maximum number of schedule entries that can be defined in the schedule table.

CAMRS29W

0 ENTRIES DEFINED. SCHEDULING DISABLED.

Explanation: Informational. CAMBSTBZ defined 0 entries for Batch Link Schedule table, resulting in the Schedule facility being disabled. To enable the Schedule facility, change table CAMBSTBZ. See the Installation Guide for instructions on modifying this table. Rerun InterTest Batch initialization routine.

CAMRS30I

NUMBER OF SCHEDULE ENTRIES IMPORTED: nnn

Explanation: The total number of entries successfully imported is nnn entries.

CAMRS31W

INSUFFICIENT SCHEDULE TABLE SIZE. nn SCHEDULE ENTRIES NOT IMPORTED.

Explanation: There were nn entries from the INT1SKUT data set not imported due to the restriction defined in the Batch Link Scheduling Table (CAMRSTBZ). A return code of 12 was also raised. To review the entries that were imported, select Option 1 from the CA InterTest Batch DB2 and IMS Schedule Menu.

CAMRS32W

BLSCHTBL IS FULL. CANNOT ADD ANY MORE.

Explanation: The In Core Schedule Table is full. Additional schedule entries cannot be added. A return code of 4 indicated some of the entries from the INT1SKUT data set were added. A return code of 8 indicated that none of the entries from the INT1SKUT were added. You can display the contents of the schedule table by selecting Option 1 from the CA InterTest Batch DB2 and IMS Schedule Menu.

CAMRS33E

SLOT NUMBER REQUESTED > MAXIMUM SIZE.

Explanation: Internal schedule component error. Contact CA for assistance.

CAMRS34E

BLSCHTBL SLOT NUMBER ERROR. FOUND=> nnnn. IN SLOT NUMBER => nnnn.

Explanation: Internal schedule component error. Contact CA for assistance.

INTA006

DATA SET NOT CATALOGED

Explanation: The data set requested on the panel is not a cataloged data set. Check the name of your fully qualified data set and retry.

INTA007

DATA SET IS AN ALIAS

INTA008

CATALOG DOES NOT EXIST

INTA009

SYNTAX ERROR IN DSNAME

INTA010

INVALID DATA SET NAME

Explanation: The data set name entered has invalid syntax.

INTA020

CA PANVALET LIB INVALID

Explanation: Only OS libraries can be specified for output.

INTA021

ENTER REQUIRED FIELD

Explanation: Enter required field at the cursor.

INTA110

INVALID DATA SET NAME

Explanation: The data set name entered has invalid syntax.

INTA120

NO DD STATS TRANSLATED

Explanation: The step selected contained no DD statements to translate.

INTA130

STEP NOT FOUND

Explanation: The input JCL either does not contain an exec card, or the step requested on the input specification panel cannot be found in the member specified.

INTA210

INVALID DATA SET ORG

Explanation: The data set name entered has invalid syntax.

INTA211

INVALID RECORD FORMAT

Explanation: The record format is not fixed.

INTA212

INVALID RECORD LENGTH

Explanation: The record length must be 80.

INTA220

MISSING DDNAME

Explanation: Ddname must be specified at the cursor position.

INTA221

NO DSN, TERM, OR SYSOUT

Explanation: Enter a data set name, terminal, or SYSOUT at the cursor.

INTA222

INVALID DATA SET NAME

Explanation: Check data set name.

INTA223

INVALID DISPOSITION

Explanation: The DISP is incorrect. Valid DISP entries are SHR, OLD, and NEW.

INTA224

INVALID COMMAND

Explanation: An invalid command was entered on the command line.

INTA225

INVALID RECORD FORMAT

Explanation: Check record format.

INTA226

INVALID DSORG

Explanation: Use a DSORG of PS or PO.

INTA300

MSL BUILD ERROR PDS ERR

INTA301

MSL BUILD ERROR PAN ERR

Explanation: A CA Panvalet read error or access error may have occurred.

INTA302

MEMBER NOT FOUND

Explanation: The member name requested on the panel cannot be found in the specified PDS.

INTA303

NOT A PDS OR PANLIB

Explanation: Input file is neither a PDS nor a PANLIB.

INTA304

MEMBER NOT FOUND/PRESENT

Explanation: Selected member was not found or not present during ALIB I/O.

INTA305

I/O ERROR ON DIRECTORY

Explanation: An I/O error occurred during the read of a PDS directory.

INTA306

INPUT FILE NOT PRE-ALLOC

Explanation: The input file was not pre-allocated or the allocation failed.

INTA307

INPUT FILE OPEN ERROR

Explanation: The input PDS you have entered is an ALIB, with a RECL=150. The input data set can be either a JCL PDS or a CA PANVALET LIB.

INTA308

OUT FILE NOT PRE-ALLOC

Explanation: The output file was not pre-allocated or the allocation failed.

INTA309

OUTPUT FILE OPEN ERROR

Explanation: The output PDS you have entered as an ALIB is not defined correctly. An ALIB PDS must be defined as RECL=150.

INTA310

INVALID ACCESS CODE

Explanation: Enter this member's correct access code.

INTA311

MEMBER NOT READ

Explanation: An internal error occurred when trying to read member.

INTA312

INVALID CONTROL CODE

Explanation: Enter this library's correct control code.

INTA510

ALLOCATION FAILED

Explanation: The browse temporary data set could not be allocated.

INTA520

DCB OPEN FAILED

Explanation: The browse temporary data set could not be opened.

INTA610

CLIST ERROR HAS OCCURED

INTA620

CLIST WRITE ERROR

Explanation: An error occurred during CLIST file write.

INTA621

CLIST BUILD ERROR

Explanation: An error occurred during CLIST build.

INTAK210

DATA SET NOT AVAILABLE

Explanation: The DISP specified is requesting exclusive control and the data set may already be in use.

INTAK218

VOLUME IS NOT MOUNTED

Explanation: The volume specified in the JCL is not active. Modify the volume and retry allocation

INTAK219

UNIT NAME UNDEFINED

Explanation: The specified unit name is undefined in DSNAME allocation.

INTAK350

INVALID PARM IN TEXT

Explanation: There is an unacceptable parameter in the JCL. The JCL being used is not valid for execution in batch. Modify the JCL and retry allocation.

INTAK360

INVALID KEY IN TEXT

Explanation: Invalid key specified in text unit (all SVC 99 functions).

INTAK364

DSNAME ALLOCATION ERROR

Explanation: JOBLIB, STEPLIB, JOBCAT, and STEPCAT are not valid ddnames for TSO.

INTAK368

UNAUTHORIZED USER

Explanation: An authorized function was requested by an unauthorized user.

INTAK369

INVALID PARAMETER LIST

Explanation: Invalid parameter list format (all SVC 99 functions).

INTAK410

DDNAME UNAVAILABLE

Explanation: One of the ddnames being allocated is already defined to your TSO session. Free the DD and try to allocate again.

INTAK420

DDNAME IS OPEN

INTAK438

DDNAME NOT ALLOCATED

INTAK448

DATA SET ALREADY EXISTS

Explanation: Occurs when attempting to allocate a data set with a DISP=NEW and the data set already exists.

INTAL708

DATA SET NOT CATALOGED

Explanation: One of the data sets in your JCL is defined with a DISP=OLD or SHR and the data set is not cataloged.

INTAM100

INVALID OPTION

Explanation: Options 1, 2, 3, 4, and 5 are the only options available.

INTAM704

DUPLICATE DSN ON VOL

INTAM714

SPACE NOT AVAILABLE

Explanation: The JCL you are attempting to allocate contains a new data set, and the volume specified for that data set does not have sufficient space to allocate it. Specify another volume.

INTAN708

CATALOG ERROR

Explanation: Structure inconsistent.

INTB000

FUNCTION FAILED

INTB001

CATALOG I/O ERROR

INTB002

CATALOG I/O ERROR

INTB003

INVALID MEMBER NAME

INTB004

INVALID DATA SET NAME

INTB005

VOLUME NOT AVAILABLE

INTB006

DAIR ERROR

Explanation: Error occurred using Dynamic Allocation Interface Request.

INTB007

DAIR CATALOG ERROR

INTB008

DAIR ALLOCATE ERROR

INTB009

DAIR FREE ERROR

Explanation: Dynamic Allocation Interface Request attempted to free a data set via ddname unsuccessfully.

INTB100

NOTHING TO ALLOCATE

Explanation: Allocate was requested but no ddnames existed to allocate.

INTB101

REQUEST BLOCK FAILURE

Explanation: GETMAIN failed to get storage for request block in SVC99.

INTB102

PAGE FAILED FOR TEXTUNIT

Explanation: GETMAIN failed to get a page for SVC99 text units and PTR

INTG001

INVALID LINE COMMAND

INTG002

NUMBER IS INVALID

Explanation: A number is not allowed with the “AL” line command

INTG003

MEMBER NOT FOUND

Explanation: Selected member was not found.

INTG005

INVALID PRIMARY COMMAND

Explanation: Enter UP, DOWN, END, RETURN, SELECT, or LOCATE.

INTG007

NO OPERATOR FOUND

Explanation: Operator for command not present or valid.

INTG008

MEMBER IS SAVED

Explanation: Intaenter has overwritten the input member and DSN

INTG009

MEMBER IS CREATED

Explanation: Intaenter has written to a new member or DSN.

INTG101

COMMAND NOT FOUND

Explanation: Command is either not found or miskeyed.

INTG102

MEM REPLACE NOT ALLOWED

Explanation: REPLACE NO was specified on out panel. Use Y.

XDAIR004

INVALID PARM LIST

Explanation: The parameter list passed to DAIR was invalid.

XDAIR008

CATALOG ERROR

Explanation: An error occurred in the catalog management routine.

XDAIR016

NO TIOT ENTRIES

Explanation: No TIOT entries are available for use.

XDAIR020

DSNAME UNAVAILABLE

Explanation: The data set requested is not available.

XDAIR024

DSNAME IS CONCATENATED

Explanation: DSNAME requested is a member of a concatenated group.

XDAIR028

DSNAME IS NOT ALLOCATED

Explanation: DSN is not allocated or its attribute list is not found.

XDAIR032

DSN PREVIOUSLY ALLOCATED

Explanation: DSN previously allocated permanently, DISP=NEW not allowed.

XDAIR036

ERROR OCCURRED IN CATLG

Explanation: An error occurred on a catalog information routine (IKJEHCIR)

XDAIR040

RETURN AREA EXHAUSTED

Explanation: The provided return area is exhausted and more index blocks exist.

XDAIR044

DELETE PREVIOUSLY USED

Explanation: You specified DELETE or a request of OLD, MOD, or SHR with no volume.

XDAIR048

RESERVED

XDAIR052

REQUEST DENIED

Explanation: Request has been denied by installation exit.

001

I/O error.

Attempt to read after AT END.

Reading a wrong length record.

002

I/O error.

003, 004, and 008

I/O error.

013

Something does not match up between the program and the DD statement. Check the system message (IEC141I) for a more complete description of the error.

02x

Conflicting DCB for a direct file

030

Error in DCB for ISAM file.

031

I/O error on an ISAM file.

032

Error in DCB for ISAM file.

033

I/O error on an ISAM file.

034

Error in DCB for ISAM file.

035

Error in DCB for ISAM file.

036

No prime data area was specified for an ISAM file.

037

Invalid buffer length was specified.

038

The index area is too small.

039

END-OF-DATA problem with an ISAM file.

03A

I/O error on an ISAM file.

03B

Opening an ISAM file that is already open.

03C

Error in DCB for an ISAM file.

03D

Conflict in DCB for ISAM file - the DCB=DSORG=IS was omitted.

03E

I/O error during the load of an ISAM file.

0C1, 0C2, and 0C3

Invalid or missing DD statement.

Reading or writing an unopened file.

Runaway or uninitialized subscript or index.

Dropping out of end of program.

0C4 and 0C6

Invalid or missing DD statement.

Reading or writing an unopened file.

Runaway or uninitialized subscript or index.

Dropping out of end of program.

Opening or closing a file twice.

Coding equal BLKSIZE and LRECL for variable length records.

Omitting a parameter from a CALL list.

Using a divisor or multiplier that is too large.

Using the wrong SORTLIB in a COBOL sort.

0C7

Data item not initialized.

DISPLAY data moved to a numeric group item.

Improper definition in LINKAGE SECTION.

Improper definition in FILE SECTION.

Invalid or improperly aligned data in an input file.

Improper initialization using MOVE ZERO.

Runaway or uninitialized subscript or index.

0C8 and 0CA

Arithmetic overflow: the receiving field of an arithmetic operation is too small.

0C9 and 0CB

Divide exception: dividing by zero.

0CC, 0CD, 0CE, and OCF

A problem in floating point operation. Did you specify COMP-1 or COMP-2 usage accidentally?

13E in BMP Region

CA InterTest Batch END, QUIT, or CANCEL caused a detach error in the BMP region.

213

The system could not find the file as specified in the allocate statement. Check system message for further explanation.

437

An I/O error occurred while processing the end-of-volume condition.

706

Attempt to execute a program that has been marked 'not executable' by the linkage editor.

Attempt to execute an object file.

Attempt to execute a source file.

806

The load module was not found in the system library or the dynamic STEPLIB you provided.

80A

Not enough virtual storage was available to allocate the amount required by the program. Log on specifying a larger region size and retry. Some data centers have TSO size restrictions. If you specify a size larger than permitted, the size allocated will default to the data center's default size.

90A

An area of main storage was released by a program, but it was an area that was not attached to the program. This usually means a file was closed twice.

913

A security or password violation has occurred.

B37

The file required more direct access space than was requested by the DD statement. This is usually caused by incorrect direct access space allocation or a program loop that contains a WRITE statement.

C03

The application that you were debugging has left some files open. Correct the logic in your application to close the files before exiting.

D37

The file required more direct access space than was requested by the DD statement. This is usually caused by an underestimated direct access space allocation or a program loop that contains a WRITE statement.

E37

The volume does not contain enough available space to allocate the amount requested for a file.

519

A procedure exit has been reached, and the user has bypassed statements so the references to the calling statement are not defined.