JCL Generation Data Group Interview Questions and Answers
Q: What is a Generation Data Group (GDG)?A: A generation Data Group is a group of chronologically or functionally related datasets. GDGs are processed periodically, often by adding a new generation, retaining previous generations, and sometimes discarding the oldest generation.
Q: How is GDG base created?A: A GDG base is created in the system catalog and keeps track of the generation numbers used for datasets in the group. IDCAMS utility is used to define the GDG base for MVS/XA, and MVS/ESA. Older systems required that the IEHPROGM utility be used.
Q: What is model dataset label (Model DSCB)?
A: A model dataset label is a pattern for the dataset label created for any dataset named as part of the GDG group. The system needs an existing dataset to serve as a model to supply the DCB parameters for the generation data group one wish to create. The model dataset label must be cataloged. The model DSCB name is placed on the DCB parameter on the DD statement that creates the generation data group.
Q: What is the advantage in using generation data groups?A: The advantage in using the generation data groups is that all datasets have the name, and the system keeps track of adding and deleting successive generations. The JCL does not need to be changed between runs.
Q: How are GDG concatenated?
A: Generation data groups are concatenated by specifying each dataset name and the generation number of all generations of the generation data group . To retrieve all generations of a generation data group, omit the generation number. The DD statements refers to all generations
The result is the same as if all individual datasets were concatenated. If generations are not on the same volume, this will not work.
Q: How are different generations specified?A: Different generations are specified by providing the dataset name and generation number for each GDG desired.
Q: What is the status of the GDG when an abend occurs?A: The GDG is in a bad state because it may consist of partial information. If used in this state, it is possible to get incorrect or improper results. It is recommended to reset the current generation by deleting the bad generation before executing the job, which will re-create a new generation.
Q: How is a previous GDG coded?A: Previous GDGs are coded as (-1) after the dataset name. An example would be DSN=JAN.DATA(-1).
Q: How is the current GDG coded?A: Current GDGs are coded as (0), (+0), or (-0) after the dataset name as follows: DSN=JAN.DATA(0). The +(0) and (-0) have the same effect as (0) Normally, it is coded as (0).
Q: How is a new GDG coded?A: A new GG is coded as (+1) after the dataset name as follows:
DSN=JAN.DATA(+1). This will cause all generations to be pushed down one level at the end of the job.
Q: What is a Generation Data Group (GDG)?A: A generation Data Group is a group of chronologically or functionally related datasets. GDGs are processed periodically, often by adding a new generation, retaining previous generations, and sometimes discarding the oldest generation.
Q: How is GDG base created?A: A GDG base is created in the system catalog and keeps track of the generation numbers used for datasets in the group. IDCAMS utility is used to define the GDG base for MVS/XA, and MVS/ESA. Older systems required that the IEHPROGM utility be used.
Q: What is model dataset label (Model DSCB)?
A: A model dataset label is a pattern for the dataset label created for any dataset named as part of the GDG group. The system needs an existing dataset to serve as a model to supply the DCB parameters for the generation data group one wish to create. The model dataset label must be cataloged. The model DSCB name is placed on the DCB parameter on the DD statement that creates the generation data group.
Q: What is the advantage in using generation data groups?A: The advantage in using the generation data groups is that all datasets have the name, and the system keeps track of adding and deleting successive generations. The JCL does not need to be changed between runs.
Q: How are GDG concatenated?
A: Generation data groups are concatenated by specifying each dataset name and the generation number of all generations of the generation data group . To retrieve all generations of a generation data group, omit the generation number. The DD statements refers to all generations
The result is the same as if all individual datasets were concatenated. If generations are not on the same volume, this will not work.
Q: How are different generations specified?A: Different generations are specified by providing the dataset name and generation number for each GDG desired.
Q: What is the status of the GDG when an abend occurs?A: The GDG is in a bad state because it may consist of partial information. If used in this state, it is possible to get incorrect or improper results. It is recommended to reset the current generation by deleting the bad generation before executing the job, which will re-create a new generation.
Q: How is a previous GDG coded?A: Previous GDGs are coded as (-1) after the dataset name. An example would be DSN=JAN.DATA(-1).
Q: How is the current GDG coded?A: Current GDGs are coded as (0), (+0), or (-0) after the dataset name as follows: DSN=JAN.DATA(0). The +(0) and (-0) have the same effect as (0) Normally, it is coded as (0).
Q: How is a new GDG coded?A: A new GG is coded as (+1) after the dataset name as follows:
DSN=JAN.DATA(+1). This will cause all generations to be pushed down one level at the end of the job.
