Specifying GDG and non-GDG data set names

When defining policies to manage a GDG base entry and a standard data set name, you cannot use the same data set name in two vital record specifications. You also cannot have two vital record specifications that use the same data set name and job name combination when managing GDGs and non-GDGs.

If you want to define different retention and movement criteria for a data set name, you can define vital record specifications using different data set name masks. For one of the vital record specifications, specify a data set name mask using the GDG suffix together with ¬. The other vital record specification can include a specific or a generic data set name. DFSMSrmm manages both sets of non-GDG data sets separately. When you include the GDG suffix and ¬ in the data set name for the first vital record specification, DFSMSrmm manages those data sets as a cycle of pseudo-GDG data sets, even though they are identified as NOGDG.

Figure 1 shows an example of defining two vital record specifications for the same data set name with the CYCLES operand. When you use the CYCLES operand, the retention of duplicate GDGs is controlled by the setting for the DUPLICATE operand of the OPTION GDG in parmlib.

Figure 1. Specifying NOGDG and CYCLES in a vital record specification

RMM ADDVRS DSNAME(a.b.c) NOGDG CYCLES COUNT(5) LOCATION(REMOTE)
RMM ADDVRS DSNAME(a.b.c.G¬¬¬¬V¬¬) -
      NOGDG CYCLES COUNT(5)

Figure 2 shows an example of defining two vital record specifications for the same data set name by using the NOGDG and DAYS operands. When DAYS is specified the duplicate GDGs are retained regardless of the setting of the DUPLICATE operand of the OPTION GDG in parmlib.

Figure 2. Specifying NOGDG and DAYS in a vital record specification

RMM ADDVRS DSNAME(a.b.c) NOGDG DAYS COUNT(5) LOCATION(REMOTE)
RMM ADDVRS DSNAME(a.b.c.G¬¬¬¬V¬¬) -
      NOGDG DAYS COUNT(5)

You must select a vital record specification type of DSNAME, VOLUME, or NAME.