just a random pick

JCL Abend code : S013

Conflicting or unsupported parameters in DCB; member name specified in DD not found; no directory allocation subparameter in DD.

--possible causes could be--

  • 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

Sub Response code

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.
08 American national standard labels were specified in the label parameter of the BB statement, but the unit parameter specified a 7-track tape drive. ANSI labels a valid only for 9-track units.
0C A buffer length of 0 was specified for a BDAM dataset for which dynamic buffering was requested.
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.
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.
18 An open was issued for a partitioned dataset. The specified member name was not found in the dataset.
1C An open macro was issued for a partitioned dataset,but an I/O error was encountered searching the directory.
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.
24 An open was issued with input, inout, rdback, or updat specified, but the DCB MACRF did not specify excp, get, or read.
28 An open macro was issued with output or outin specified, but the DCB did not specify a MACRFof excp, put, or write.
2C A sequential dataset using the queued access technique with exchange buffering was opened for input, but the buffer control block address was 0.
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.
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.
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.
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.
40 A sequential or direct dataset was opened for input, but the buffer control block address was 0.
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.
48 An open macro was issued for a sequential dataset using the queued access technique, but the buffer control block address was zero.
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 buffe
50 An open macro issued for a dataset allocated to a printer did not have output specified as an open option.
54 no secondary control unit could not be found for a 1419.
58 An open macro was issued for a paper tape dataset and concatenation with unlike attributes was specified.
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.
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.
64 An open macro was issued for a null dataset using an access method other than QSAM or BSAM. this is a no-no.
68 An open was issued for a dataset whose DCB specified BLKSIZE greater than 32,767, which is the maximum allowed.
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.
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.
74 An open macro was issued for an optical character reader dataset, but the open option did not specify input.
78 An open macro was issued for an optical character reader dataset. the BUFL parameter in the DCB was specified as zero.
7C An open macro was issued for an optical character reader dataset, but the LRECL parameter in the DCB was zero.
80 An open macro was issued for an optical character reader dataset, but the BUFL was less than the LRECL.
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.
88 An open macro was issued for a telecommunications device but the DCBDSORG did not specify TSO.
8C An open macro was issued for a direct organization dataset (BDAM) but the DCBRECFM parameter was not specified.
A4 A DCB was opened for a SYSIN or SYSOUT dataset but the DSORG was not specified as PS.
A8 An invalid record format was requested for a SYSIN or SYSOUT dataset. (RECFM=d, vs, or vbs are invalid for SYSIN)
AC A QSAM open was issued with a non-zero keylength in the DCB which is not supported. (now supported, but with input only.)
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.
B4 An open macro was issued with the inout/outin option for a DCB specifying the QSAM MACRF values; these are conflicting parameters.
B8 An open macro was issued for the 3890 document processor and DCBHDR was not specified in the DCB.
BC A SYSIN or SYSOUT DCB was opened with invalid options. either open specified update or rdback, or the point macro function was specified in MACRF=rp or wp. repositioning or updating a spooled dataset is not permitted.
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.
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.
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.
CC SETPRT processing failed to set up the device during an open for the ibm 3800 printing subsystem.
D0 An invalid record format of fbs or fs was specified for a partitioned data set.A SB/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.
D8 A conflict has occurred for the spanned record format extended logical record interface (xlri).buffer control block; ie. segment mode is implied.
E4 The limit of 123 extents for a concatenated partitioned data set has been exceeded. (used to be 256 extents?)
E8 The open verification function of the iefssreq macro returned an error code in register 15.

Suggestion / Complaint / Feedback