Transfer generation data groups (GDGs)

Managed File Transfer supports generation data groups (GDGs) for source and destination data sets on z/OS . Absolute and relative GDG names are supported. When you write to a new generation, the base GDG must exist.

Note: When creating a GDG entry in a batch environment using BASEGDG(+n), it cannot be referred to later in the same job by using the same positive generation number. Maintaining the same GDG entry numbers between steps of a job is a function of JCL and is not available to utility functions that update the GDG by using dynamic allocation. Therefore, a job that creates a new generation using BASEGDG(+1) would find the GDG updated as soon as the transfer successfully completes and would then need to refer to the same data set as BASEGDG(0).


GDG examples

The following examples show the fteCreateTransfer command using GDGs. In the examples, the name BASEGDG refers to an existing base GDG name. The name DSET refers to a sequential data set that is to be created. The name /u/user/file.dat refers to the name of a source data file.

This command copies file.dat into a new generation in BASEGDG. The absolute name of the new generation is reported in the transfer log: 
fteCreateTransfer -sa A1 -da A2 -ds "//BASEGDG(+1)" /u/user/file.dat
This command copies file.dat into the generation with the absolute name specified in BASEGDG: 
fteCreateTransfer -sa A1 -da A2 -ds "//BASEGDG.G0009V00" /u/user/file.dat
This command copies the most recent generation in BASEGDG to DSET. The absolute name of the generation is reported in the transfer log: 
fteCreateTransfer -sa A1 -da A2 -ds "//DSET" "//BASEGDG(0)"
This command copies the next most recent generation in BASEGDG to DSET. The absolute name of the generation is reported in the transfer log: 
fteCreateTransfer -sa A1 -da A2 -ds "//DSET" "//BASEGDG(-1)"
Parent topic: Guidelines for transferring files


Related reference