IEB1072W
JCL FOR DD ddname IMPLIES THAT THE DATA SET IS PARTITIONED BUT IT IS ON MAGNETIC TAPE. PROCESSING IT AS SEQUENTIAL. (DEVTYPE= X'dev_type' JFCDSORG= X'jcl_org' JFCBDQTY=dir_blocks)

Explanation

There is a conflict in the JCL or between the JCL and the catalog entry for the data set.

The unit allocated to the data set is a tape drive. Therefore the data set must be an unload (sequential) data set. However, the JCL contains DSORG=PO and/or a SPACE parameter which specifies directory blocks which indicates that the data set is partitioned.

Parameters like DSORG=PO can be added to your JCL even though you did not code them. SMS ACS routines, Data Classes, the JCL SPACE, LIKE and DCB parameters can all implicitly add to JCL.

Message inserts and meanings:
ddname
DD name identifying the data set.
dev_type
device type from the UCBDEVT field.
jcl_org
value of the DSORG field in the JCL.
dir_blocks
number of directory blocks specified in the JCL.

The severity is 0.

System action

The data set is treated as an unload data set.

User response

Determine where the DSORG=PO is coming from. Look for directory blocks in the space parameter, look at the label of data sets referenced by the LIKE or DCB parameter, and use ISMF to look at the definition of any Data Class assigned to the data set.

Add DSORG=PS to the DD statement or the TSO ALLOCATE or ATTRIB command to explicitly override the DSORG.

Source

DFSMSdfp