ile dit dit_Settings enu tilities ompilers est elp Like this page
EDIT MOSHIX.WORK(RESULT) - 01.04 Columns 00001 00080
Command ===> ____________________________________________________________________________Scroll ==> CSR_
******* ********************************************** Top of Data ******************************************
....... GLOBEMVS Abend Codes
....... QSAM FILE STATUS 90 Check the DD statement and the SELECT.
....... QSAM FILE STATUS 91 Attempting to process a closed file.
....... QSAM FILE STATUS 92 Probable user error. Attempting to process a closed file.
....... S001 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, tape being read in wrong density, PDS directory is overwritten, NSL label had incorrect DSNAME, operator cancelled, true I/O failure, UCB show redundnacy, harware error - bad tape or tape drive, secondary space allocation for DASD output file too small (see SP37), in COBOL: incorrect use of BLOCK CONTAINS CLAUSE or had a RECORDING MODE F when generated, but not when read. SUGGESTION: On DCB, add ',erropt=skp)' to skip a block with bad I/O. Check DCB in JCL against FD statement; In concatenation, largest blocksize must be first. Verify BLOCK CONTAINS 0; verify FD.
....... 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 DCB had the wrong block size, IEHMOVE-attempt to rename dataset 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 is greater than the DASD track capacity.
....... S002-10 An invalid record was encountered on a PUT or WRITE 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 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 as 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.
....... S013 Conflicting or incomplete parameters in DCB, such as BLKSIZE not a multiple of LRECL, or missing SYSIN DD; Tried to create a PDS without allocating directory blocks; Member name specified in DD not found; no directory allocation subparameter in DD; Open output dataset as input; Track overflow or updating attempted, but not supported by the OS. May be a record length or OPEN statement error.
....... S013-08 ANSI standard labels were specified in the LABEL parameter but are not supported by the system.
....... 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 blocksize 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.
....... 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 blocksize is not a multiple of LRECL, or for variable-length records, blocksize 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 MACRF did not specify 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 was 0.
....... S013-34 An OPEN macro was issued for a dataset with blocksize and BUFL equal to 0. The system determined that it had to obtain buffers but was unable to do so
....... 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.
....... 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 is a DCB is shared by two or more tasks, or is opened and closed several times within one job step.
....... S013-40 A sequential or direct dataset was opened for input, but the buffer control block address was 0.
....... S013-44 An OPEN macro was issued for a dataset on a direct access device for which chained scheduling was specified, but the buffer control block address was 0.
....... S013-48 An OPEN macro was issued for a sequential dataset using the queued access technique, but the buffer control block address was zero.
....... S013-4C An OPEN macro was issued for a sequential dataset using the queued access technique. The system determined that a buffer pool existed for this dataset and made the appropriate 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 or greater than the value specified in the DCB for logical record length. Otherwise the buffer length in the buffer control block had to be equal 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-58 An OPEN macro was issued for a paper tape dataset and concatonation 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.
....... S013-60 An OPEN macro was issued for a dataset with a DCB specifying RECFM=F, and blocksize was not equal to LRECL. Correct the RECFM to FB, or make LRECL and blocksize 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 macro was issued for a dataset whose DCB specified a BLKSIZE greater than 32,767, which is the maximum allowed.
....... 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 devise 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, but the BUFL parameter was specified as 0.
....... S013-7C An OPEN macro was issued for an optical character reader dataset, but the BUFL parameter in the DCB was specified as 0.
....... S013-80 An OPEN macro was issued for an optical character reader dataset, but the LRECL parameter was less than the BUFL.
....... 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 so.
....... S013-8C An OPEN macro was issued for a direct organization dataset (BDAM) but the DCBRECFM parameter was not specific.
....... 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-B0 An OPEN macro was issued with the Reback option for a DCB specifying a record format of variable spanned records. These are conflicting parameters.
....... S013-B4 An OPEN macro was issued with the INOUT/OUTIN option for a DCB specifying the QSAM MACRF values; these are conflicting parameters.
....... S013-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 MACRG 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.
....... 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.
....... -An auxiliary storage management routine suffered a translation error while using the control register of another address space to update that address space's LSQA.
....... SO3B ISAM dataset to be processed, but not created or its DCB not closed after creation. - Possible cause: dataset was to be written on but was opened as input. LRECL/BLKSIZE problem exists-invalid values or not multiples.
....... SO3D The error occurred during the execution of a QISAM or BISAM or BDAM macro instructions.
....... 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 does 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.
....... 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 a noncancelable loop or wait state.
....... S07C Supervisor control recovery has detected an error which requires that the current task be terminated or that the current address space be terminated.
....... S0B0 An uncorrectable error was detected by the SWA Manager.
....... 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-10 Invalid length (0 or negative for asign locate or attempting to read or write a record which is not 176 bytes, in move mode).
....... S0B0-14 Invalid coutn 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 an non-existing ID or has failed to pass one and the block does not have an embedded ID.
....... S0B0-20 Invalid block pointer (write locate is attempting to write and is passing a block pointer which is not valied for the SVA requested).
....... S0C1 Operation Exception - An Operation is code is not on the machine. Possible Causes:
....... subscript error - clobbered code
....... tried to read a file that was not open
....... misspelled DDName
....... error in parameters passed to subroutines
....... missing DD card
....... RECORDING MODE i wrong or density is incorrect
....... bad load module, possible bad object deck
....... FORTRAN - Missing DIMENSION statement, same name for array and subroutine
....... COBOL - subroutine PROGRAM ID is 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 GIVING option used.
....... COBOL - executing sort-using after opening SORTIN
....... S0C2 Privileged operation exception. 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 was executed when no SYSIN DD was available.
....... S0C3 Failure to close input/output file in source code.
....... S0C4 Protection exception - virtual address could not be translated into a real address; Possible subscript error or bad parms; Variable length record larger than maximum target field size; missing or misspelled dd statement; I/O against unopened file; Using GOBACK in an output procedure; Move to an area not passed in a CALL statement; COBOL Sort with STOP RUN in input or output procedure; blocksize and logical record size equal for a variable length dataset.
....... S0C5 Index or subscript out of range; uninitialized index or subscript; invalid data address; Reference to a field in a record before OPEN or after CLOSE; Closing the same file twice; improper exit of a PERFORM statement; 88 level cannot be last statement before Report section; date not initialized; Problem with a GO TO, GO TO DEPENDING ON, or GO TO that has been ALTERED.
....... S0C6 Specifcation exception -an incorrect boundary was specified. Usually caused by unintentional branch to invalid instruction. Ddname/Select statement conflict; ACCEPT statement with SYSIN DD and data missing; No GO TO statement in a paragraph named in an ALTER statement; I/O attempted against a file not open.
....... S0C7 Data exception -decimal data is incorrect or improperly overlapped or not validly initialized. Subscript error, referenced beyond table. COBOL -working storage not initialized. -bad data, should check data for errors. -Garbage in a filed being tested; subroutine parm missing or in wrong order.
....... S0C8 Fixed point overflow exception note -masked by FORTRAN.
....... S0C9 Fixed point divide exception note-masked by FORTRAN.
....... S0CA Decimal overflow exception. The destination field is too small to contain the result field in a decimal operation.
....... S0CB Decimal divide exception. A quotient exceeds the specified data field size.
....... S0CC Exponent overflow exception. A floating point number exceeds the maximum size. Note- This error is detected and fixed in FORTRAN.
....... S0CD Exponent underflow exception. A floating point number is smaller than the minimum. Note -FORTRAN will set the result to zero and continue processing.
....... S0CE Significance exception a floating point addition or subtraction results in an all zero fraction note -this is masked in FORTRAN.
....... S0CF Floating point divide exception -divide by zero note- this error is detected and noted by FORTRAN.
....... S0D2 A program check was detected; an interruption code of 18 (translation specification exception) has occurred. There is invalid data in either control registers 0 or 1, 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 was detected; and interruption code of 19 (special operation error) has occurred. A privileged program issued a set system mask. This instruction is not valid in OS/VS2 (since Release 2).
....... SOE3 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.
....... SOF1 Program interruption in I/O interruption handler record described as wrong length.
....... SOF2 Program interruption in Type 1 SVC routine clobbered IOB or other SVC paramters -see SOC1.
....... SOF3 Machine check interruption disk I/O failure or machine trouble.
....... SOF8 The issuer of an SVC was either in SRB mode, held a lock, or was disabled.
....... S100 A device to be used was not operational or a pseudo device previously allocated has been reallocated.
....... 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.
....... S106 Region size too small. An error was detected by the control program when it attempted to fetch the requested program into virtual storage. Possible cause: Previous LKED step failed to output a SYSLMOD, needs larger SIZE=I/O error-machine trouble or disk failure.
....... S106-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.
....... 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
....... S106-0F An uncorrectable input/output error occurred.
....... S122 Either the operator or the job entry subsystem cancelled the job, requesting a dump. Check the job log listing for more information.
....... S12D Invalid segment table in an overlay program. See S0C1.
....... S130 The DEQ macro specified a resource not previously specified 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.
....... 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.
....... 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 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 spit of the expiration date, the operator did not reply 'U'. Ask the operator to reply 'U' or specify another volume serial.
....... 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.
....... 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 points to the DEB, but the DEBDCABAD 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 O 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 the 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 pointer 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. Possible causes:
....... 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
....... ECB not on fullword boundary
....... ECB is store-protected from caller
....... ECB not specified for PGFIX.
....... ECB specified for PGOUT
....... S171-04 The error was detected by the page services routine. This generally indicates that the caller did not own the virtual storage defined by the VSL list entry.
....... S171-16 The input VSL or ECB failed to pass the page services interface validity check.
....... S206 The address of the parameter list, or one of the parameters passed to a LINK, LOAD, XCTL, or DELETE macro invalid.
....... S213 DSCB not found; I/O error in reading or writing DSCB. Possible causes:
....... the data set is not 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 extends of the indicated dataset. Try browsing or editing the file via SPF 3.4. Check the upper right-most corner of the ISPF panel for an indicator message.
....... S213-28 An OPEN macro ws issued for a direct access dataset specifying UNIT=SYSDA, but the UNIT already contained 127 users, whcih is the maximum allowed.
....... S214 I/O error in tape positioning or volume disposition.
....... 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.
....... S222 Either the operator or the job enter subsystem cancelled the job. Check the job log listing for more information. If there is no apparent explanation, contact operations before resubmitting. Possible causes:
....... Line or card estimate exceeded.
....... JCL error caused mount request
....... Excessive runtime.
....... S233 Invalid parameters have been passed to SVC dump.
....... S233-04 The address of the parameter list is zero.
....... S233-08 The parameter list is not a valid SVC dump or snap parameter list for MVS.
....... S233-0C The caller-supplied dataset is on an unsupported device.
....... S233-10 In a user-supplied storage range, the start address is greater than the end address.
....... S233-14 The user-supplied data (for HDR= or HDRAD=) is greater than 100 characters.
....... S233-18 The 4K SQA buffer has been requested (BUFFER=YES) but it is not serialized (by setting on the high order bit in CVTSDBF)
....... S233-1C The parameter list or what it points to is in the 4K SQA buffer.
....... S233-20 The user supplied a DCB address and the DCB is not open, or the DCB address is invalid.
....... S233-24 The specified ASID parameter was syntactically invalid. The ASID was less than 0 or greater than the maximum value.
....... S233-28 An ASID specified in the ASID list pointed to the by the ASIDLST parameter was syntactically invalid. The ASID was less than 0 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 specifoed the 4K SQA buffer (BUFFER=YES) but and SVC dump was already in progress.
....... S237 The error occurred during end-of-volume label verification. Possible causes:
....... 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 misused 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.
....... S23E The error was detected during execution of a DETACH macro instruction. Either:
....... The parameter passed to detach in register 1 was not a fullword address
....... The storage key of that address did not match that of the issuer of the detach
....... The parameter contained in the addressed fullword of the issuer was not the address of a subtask of the isser of the detach.
....... S240 An error occurred during execution of a RDJFCB macro.
....... 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.
....... S2F3 Job was being executed when system failure occurred- A system restart was performed.
....... S300 An error was detected when and I/O operatoin was requested; the storage protection key was not 0 or the DEB validity check routine returned to EXCP wit 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 are 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.
....... 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 strage area to be released was not within subpool zero.
....... The SP parameter was not specified but the virtual storage area to be released was not within subpool zero.
....... The SP parameter was specified correctly, but the boundaries of the storage areas to be freed were not completely described by a descriptor queue element.
....... S306 The error occurred during the execution of the LINK, XCTL, ATTACH, or LOAD SERVICE ROUTINES. The authorized routine requested a module, which could bot be found on an authorized library, but a copy of the module may have been found on a non-authorized library.
....... S306-04 The requested program was not found in the indicated source.
....... S306-08 An uncorrectable I/O error occurred when the control program attempted to search the directory of the library containing the module.
....... S306-0C The module could not be found in the LPA or in the LPA directory or an authorized library.
....... 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 NT 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 subpool zero.
....... The SP parameter was not specified, but the Virtual Storage Area to be released was not within subpool zero.
....... The SP parameter was specified correctly, but the boundaries of the storage areas to be freed were not completely described by a descriptor queue element (DQE).
....... S313-04 (04 is the only possible return code associated with S313). An I/O error occurred reading a format 2 or format 3 DSCB during the execution of an OPEN macro.
....... S314 I/O error in reading DSCB. 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.
....... S322 Job or step time exceeded the specified limit. Program is in a loop. Insufficient time parameter on JOB or EXEC card.
....... S337 The error occurred when the end of a data set was reached. Possible causes:
....... No end of file 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) specified in the DCB for DD dummy dataset.
....... S337-08 No end-of-dataset routine (EODAD) specified in the DCB for DD dummy dataset.
....... S338 An unauthorized ptask attempted to use authorized options of the ENQ macro instruction.
....... S378 The error occurred during execution of an RC or RU form FREEMAIN macro. Possible causes:
....... A FREEMAIN for an entire subpool was requested (register 1 was zero) but the length in register 0 was not set to zero.
....... 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 areas to be released wit not within subpool zero.
....... The specified subpool could not be found.
....... 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).
....... 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 CO) points to the EXCP problem determination area. The items in the problem determination area of the greatest interest to you are:
....... hex offset 10 contains a copy of the registers when EXCP determined the error condition;
....... hex offset 50 contains the contents of the request queue element (RQE) if allocated when the program check occurred.
....... S413 INPUT, INOUT, or RDBACK specified, but no vol ser in DD; or I/O error in reading volume label; or could not mount volume on device; or volumes specified less than devices allocated. Possible causes:
....... Forgotten volume serial for input tape.
....... Had DISP new when should have had OLD.