How CA XCOM Data Transport for z/OS manages Generation Data Sets (GDGs)?
How CA XCOM Manages Generation Data Sets
The base needs to be created initially on the partner side. CA XCOM Data Transport then creates the next generation(s). There are no DEFAULT table or config member parameters for GDG's.
If you submit a type=schedule transfer with GDG(0) or GDG(+0) specified for the LFILE, the CA XCOM Data Transport server resolves the filename to be the current GxxxxV00 number at the time the transfer is scheduled. When local file is specified with LFILE=, XCOM transfers according to its relative generation number. This permits maximum flexibility without alteration of the production JCL. Using LCLDS01 to specify the GDG to be transferred is not recommended.
Since the transfer is immediate, the filename is resolved immediately.
Transferring all Generations
CA XCOM Data Transport can transfer all generation data sets within a GDG in a single transfer operation. To do so, specify the GDG by its base name in the request (that is, without a relative generation number).
CA XCOM Data Transport then transfers all data sets in a single stream, starting with the newest generation and ending with the oldest.
Sending a Specific Generation
To send a particular generation, give it a GxxxxV00 suffix. This data set is then processed whenever the transfer executes.
Examples of how to Specify SYSIN01 parameters.
- Specifying the sysin01 parms to transfer a single generation:
- Specifying the sysin01 parms to transfer an entire GDG:
- Specifying the sysin01 parm to transfer a specific generation:
See the Generation Data Groups section located in the XCOM documentation at CA XCOM Data Transport for z/OS - 12.0
NOTE: The absolute generation number of the MVS GDG file processed in a transfer will never show up in the partner's xcom.log. Only the relative generation will show up.