IEB1069E

Explanation
There is a conflict between the JCL and the data
set label. The JCL supplied DSORG=PO overrides the DSORG=PS in the
label.
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.
label_org
value of the DSORG field in the data set label.
jcl_org
value of the DSORG field in the JCL.

The severity is 8.

System action
When IEBCOPY attempts to read the directory at
the start of the data set, one of three things may occur: A Wrong Length Record I/O error may occur because the first record
is not 256 bytes data with an 8 byte key, or
IEBCOPY may find 0 directory records which is interpreted as a
corrupt partitioned data set, or
IEBCOPY may find the directory of a deleted partitioned data set
which used to occupy the disk space, which will cause extra members
(possibly corrupt) to appear in the 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.
A
conflict like this can either be removed at its source or you may
override the conflict by coding DSORG=PS on the DD statement or in
the TSO ALLOCATE or ATTRIB command.

Source
DFSMSdfp