Tape Parameters

You can use the parameters that follow when tape drives are involved in the transaction. Allowable values for these parameters are the same as for their IBM JCL counterparts, except where noted. You can also refer to this section for parameter information when using the Menu Interface.
xdtz12
You can use the parameters that follow when tape drives are involved in the transaction. Allowable values for these parameters are the same as for their IBM JCL counterparts, except where noted. You can also refer to this section for parameter information when using the Menu Interface.
When tape drives are involved in the transaction, it can be necessary to use some of the parameters that are discussed in the section, FILETYPE=FILE Parameters, such as the parameters LUNIT, LVOL, UNIT, and VOL.
DEN
This parameter specifies the density to be used in creating a tape on the local or remote system.
  • 1 to 4
    Specifies the density to be used in creating a tape on the local or remote system. Valid values are the same as those for the DEN parameter in JCL.
EXPDT
This parameter specifies the expiration date to be placed on the tape data set being created.
  • yyddd
    Specifies an expiration date for the tape data set as a two-digit designation for the year and a three-digit designation for the day of the year. For example, in the expiration date 09021, 09 is the year (namely, 2009), and 021 is the 21st day of that year. The tape data set will expire on January 21, 2009.
  • yyyy
    /
    ddd
    Specifies an expiration date for the tape data set in terms of a four-digit designation for the year and a three-digit designation for the day of the year. For example, in the expiration date 2009/021, 2009 is the year, and 021 is the 21st day of that year. The tape data set will expire on January 21, 2009.
EXPDT and RETPD are mutually exclusive; specify one or the other.
LABEL
This parameter indicates the type of label that is associated with a tape data set. The label of a tape data set is specified in terms of a sequence number and a designation for the type of processing to be applied to the data set. The following table lists the valid values for both label components:
  • sequence number
    (0001 to 9999)
    This value identifies the sequence number of a data set on tape.
    Default
    : 0001
  • processing type
    (AL, AUL, BLP, LTM, NL, NSL, SL, SUL)
    Represents the types of processing to be applied to data sets on tape.
    Default
    : None
Default:
(1,SL)
CA XCOM Data Transport writes only standard label tapes.
This parameter must be specified in the same way that the LABEL parameter appears in the JCL-see the following example.
Example
LABEL=(2,BLP)
This specification refers to the second data set on the tape. The type of processing to be applied to this data set is BLP.
LLABEL
This parameter specifies the sequence number of the file on the tape volume to be used for the local data set, and the type of processing to be applied to the data set (sequence number, processing type).
Valid values that can substitute for these variables are as follows:
  • sequence number
    (1 to 9999)
    This value identifies the sequence number of a data set on tape.
  • processing type
    (AL, AUL, BLP, LTM, NL, NSL, SL, SUL)
    Represents the types of processing to be applied to data sets on tape.
This parameter must be specified in the same way that the LABEL parameter appears in the JCL.
Default:
(1,SL)
Example
LLABEL=(2,BLP)
This specification refers to the second data set on the tape. The type of processing to be applied to this data set is BLP.
LUNITCT
This parameter specifies the number of units to be allocated on the local system.
  • 1 to 20
    Specifies the number of units to be allocated on the local system.
LVOLCT
This parameter specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the local system.
  • 1 to 255
    Specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the local or remote system.
LVOLSQ
This parameter specifies the sequence number of the first volume of a multivolume remote data set to be used.
  • 1 to 255
    Specifies the sequence number of the first volume of a multivolume remote data set to be used.
RETPD
This parameter specifies the number of days to retain the tape data set being created.
  • 1 to 9999
    Specifies the number of days (1 through 9999) that the tape data set being created is to be retained.
Default:
None
RETPD and EXPDT are mutually exclusive; specify one or the other.
TAPE
This parameter indicates to the remote system whether the volume is a tape volume or a disk file.
  • YES
    Indicates that the transfer is to a tape volume and that mounts are allowed when performing dynamic allocation.
  • NO
    Indicates that the transfer is to a disk file.
If the remote data set is on tape, TAPE=YES must be specified for CA XCOM Data Transport to process the other tape parameters. Otherwise, all the tape parameters revert to their default values. This is especially important if the remote data set spans more than five tape volumes.
UNITCT
This parameter specifies the number of units to be allocated on the remote system.
  • 1 to 20
    Specifies the number of units to be allocated on the remote system.
Default:
None
VOLCT
This parameter specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the remote system.
  • 1 to 255
    Specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the remote system.
Default:
None
VOLSQ
This parameter specifies the sequence number of the first volume of a multivolume remote data set to be used.
  • 1 to 255
    Specifies the sequence number of the first volume of a multivolume remote data set to be used.