Processing Different File Types › Generation Data Groups

Generation Data Groups

Generation Data Groups present a special problem to most file transfer systems. Generally, when a generation data set is uploaded into a GDG, a relative generation number of (+1) is given as part of the file name. However, relative generation numbers are normally not updated by z/OS until the end of the associated job. Therefore, if (as in CICS) the CA XCOM Data Transport started task is being used to update the generation data set, its relative generation number would not be updated until the started task is brought down.

This generation data set could be updated multiple times before the CA XCOM Data Transport started task is stopped, the second update being, as far as z/OS is concerned, to the (+2) generation, the third to the (+3) generation, and so on.

The situation described above is generally undesirable. CA XCOM Data Transport avoids this by treating each Generation Data Group file transfer request as if it were an autonomous job. This allows for the relative generation of number references in the conventional manner, no matter when the CA XCOM Data Transport started task is brought down. The complete data set name of a generation data set, including the GxxxxV00 suffix, is sent in CA XCOM Data Transport messages to partner systems.

For example, error and log messages concerning a generation data set sent to a PC or workstation display the actual z/OS data set name.