Propagation

Edit online

In an all IBM® Connect:Direct® for z/OS COPY step, the source data set’s DSNTYPE is propagated to the destination dataset if PROPAGATE.DSNTYPE=YES is specified in the destination node’s INITPARMs, and the DSNTYPE is not specified for the destination dataset (in the COPY TO section). If either side is not IBM Connect:Direct for z/OS v6.1, then COPY will only support the propagation of the DSNTYPE, and not the DSNTYPE Version or MAXGENS.

If both sides are IBM Connect:Direct for z/OS v6.1, then DSNTYPE propagation will include the DSNTYPE, the DSNTYPE version, and the MAXGENS. More specifically, if DSNTYPE propagation is in effect, and a PDSE is to be created from another PDSE, then the source data set’s DSNTYPE, DSNTYPE version, and MAXGENS will be propagated, provided they are not specified in the COPY TO section.
  1. DSNTYPE is only propagated if the INITPARM PROPAGATE.DSNTYPE=YES on the destination node and the DSNTYPE is not in the TO section of the COPY step.
  2. DSNTYPE Version and MAXGENS are only propagated if the DSNTYPE is propagated.
  3. MAXGENS is only propagated for a PDSEV2.

The results also depend on the combination of JCL parameters and SMS parameters. In a COPY step, the JCL parameters can come from COPY TO parameters (including direct specification, DATACLAS, LIKE and TYPE), and propagation of the source dataset attributes. If those aren’t enough to determine all attributes, the SMS parameters from the Destination system come into play.

Note: From V6.4 onwards, IBM Connect:Direct introduced the new initialization parameter PROPAGATE.DSNTYPE.EXTENDED, this parameter will control DSNTYPE parameter in DYNALLOC for propagating extended format dataset. For more information, refer to PROPAGATE.DSNTYPE.EXTENDED= EXTPREF|EXTREQ.