SMS Support

The Connect:Direct® for z/OS® COPY statement supports transmitting and creating data sets with SMS attributes. The following restrictions apply to the transmission of these data sets:

  • If the TO data set is specified with SMS attributes, DCB or SPACE parameters are not propagated by default from the FROM data set, because dynamic allocation treats them as overrides and they replace attributes from the SMS DATA CLASS. Use the DATACLAS parameter and an appropriate SMS definition at the receiving site to acquire default values for DCB and SPACE. See SMS Propagation for more information.
  • VSAM data sets can be created as new data sets as part of the COPY TO statement. All forms of VSAM data sets (KSDS, ESDS, RRDS, and LINEAR) are supported as new data sets.

    If allocating a NEW VSAM file, the following VSAM attributes are propagated to the receiving node if they are not specifically coded in the process or in the TYPE file definition, and no DATACLAS or LIKE= keywords are coded in the process or TYPE file definition (and no data class is propagated):

    • KEYLEN - For KSDS data sets only. The length of the key.
    • KEYOFF - For KSDS data sets only. The offset where the key starts.
    • LRECL - The MAX RECSIZE. If this is propagated, the output file will be allocated with a MAX and AVG record size of the input file’s MAX RECSIZE.
    • RECORG - The record organization (KS, RR, ES, or LS).

      This way, you do not need to code any file attributes for the TO file when dynamically allocating a NEW VSAM file.

      The parameters not supported by SMS cannot be propagated by IBM® Connect:Direct.

  • For platforms other than z/OS, all SMS parameters must be specified as subparameters in SYSOPTS. SYSOPTS is a mechanism that allows you to pass system-specific parameters between platforms. See the COPY statement of the appropriate platform for syntax requirements for the SYSOPTS parameter.
  • For a data set to be SMS-controlled, it must be created with either a STORAGE CLASS or a MANAGEMENT CLASS or both.
  • SMS attributes are not propagated from the FROM data set by default because dynamic allocation treats them as overrides. See SMS Propagation for more information.
  • The disposition of all SMS controlled data sets is always CATLG. For example, if you code DISP=(NEW, KEEP) on the COPY TO statement, the system uses DISP=(NEW, CATLG) to control the data set.