GDG - using NoEmpty and Noscratch together

arindambanerjee · New User Joined: 30 Jun 2007 Posts: 39 Location: India

Hi,

In GDG attribute:

Empty-->will uncatalog the all the generation.
NoEmpty-->will uncatalog the oldest generation
&
Scratch-->will physically delete the dataset
NoScratch-->will uncatalog the dataset.

Then could you please explain what is the use of using NoEmpty and Noscratch together, both will do the same thing. Please correct me if I am wrong.

superk · Posted: Fri Jul 10, 2009 11:56 pm

Your information is not quite correct:

15.1 DEFINE GENERATIONDATAGROUP Parameters.

EMPTY|NOEMPTY

Specifies what action is to be taken for the catalog entries for the
GDG base when the number of generation data sets in the GDG base is
equal to the LIMIT value and another GDS is to be cataloged. The
disposition of the actual data sets uncatalogued from the GDG base is
determined by the setting of the SCRATCH/NOSCRATCH parameter for the GDG base.

EMPTY

remove all GDS entries from GDG base when a new GDS is created
that causes the GDG LIMIT to be exceeded.

NOEMPTY

remove only the oldest GDS entry when a new GDS is created that
causes GDG LIMIT to be exceeded.

SCRATCH|NOSCRATCH

Specifies what action is to be taken for a generation data set located
on disk volumes when the data set is uncataloged from the GDG base as
a result of EMPTY/NOEMPTY processing. For generation data sets located
on tape, this parameter has no effect.

You can override the SCRATCH|NOSCRATCH attribute when issuing the
DELETE command.

SCRATCH

The GDS is deleted from all disks it occupies when uncatalogued
from the GDG base, regardless of whether it is SMS-managed or not.

NOSCRATCH

If the data set is a non-SMS managed data set it is not removed
from any of the volumes it occupies. If the data set is an
SMS-managed data set it is recataloged as a non-VSAM data set in
rolled-off status, and is no longer associated with the GDG base.
It is not deleted from any of the SMS-managed volumes it occupies.