Previous Topic: Cold Start a Request Using GDGs

Next Topic: Collective Concatenation of Data Sets in a GDG


Potential Errors with GDGs

The number of entries in the GDG can be an important factor. Depending on how the GDG was originally established, the number of entries in a GDG can determine the point at which either the oldest generation or all of the generations are deleted by the operating system.

Assume the addition of yet another data set to the GDG in our earlier example. The earliest generation, GDG.IN(-3), which is actually data set GDG.IN.G0001V00, would be deleted and the new generation added, resulting in the following:

Absolute Generation

Relative Generation

GDG.IN.G0005V00

GDG.IN(0)

GDG.IN.G0004V00

GDG.IN(-l)

GDG.IN.G0003V00

GDG.IN(-2)

GDG.IN.00002V00

GDG.IN(-3)

CA SOLVE:FTS plays no part in this deletion. It is purely a function of the way the operating system supports GDGs.

Because of this fact, the number of entries and possible auto-deletion of required data sets may impact the ability of a failed transmission to be restarted. This is always the case if the data set is deleted during transmission or before a restart can take place.

Important! The installation must therefore ensure that sufficient entries exist in the GDG to allow for possible interrupted transmissions and required restarts.