What’s In a Identify? Mainframe GDGs Get the Job Accomplished

Mainframes are completely different. They’re the biggest, quickest, most succesful programs on the planet, and so they nonetheless run many, if not most, of an important purposes within the industrial world.

One purpose mainframes stay dominant? Their lengthy historical past of successfully coping with enterprise information.

In large-scale enterprise information processing environments, a standard requirement is the necessity to take care of many various successive units of the identical kind of knowledge. Each day recordsdata result in weekly recordsdata, which then roll up into month-to-month and yearly recordsdata, all of which should be simply accessible both individually or as a bunch, within the desired order.

Because the early days of mainframes, the Era Information Group (GDG) has been the technique of managing these successive occurrences (or ‘generations’) of the identical information. Just by utilizing the dataset title, purposes can choose a present or prior era, create new generations, or use your complete assortment of datasets (a ‘GDG-all’) request.

This highly effective but easy technique of managing information is exclusive to z/OS.

Create a Mainframe GDG

Earlier than the person datasets that comprise a GDG might be created, a GDG ‘base’ entry is created within the catalog by IDCAMS. As soon as the GDG base is created, particular person era datasets (GDSs), that are usually peculiar sequential datasets, might be created.

A DEFINE assertion, just like the one beneath, accomplishes a couple of various things:

• Creates the GDG base entry
• Units the variety of generations to maintain monitor of
• Specifies what to do when the utmost variety of era datasets is reached

DEFINE GDG(NAME(MY.BUSINESS.DATA)) LIMIT(255) NOEMPTY SCRATCH

Within the instance above, every particular person era information set (GDS) is catalogued because it’s created, and a most of 255 generations (the LIMIT worth) are retained within the GDG base catalog entry.

As soon as 255 datasets have been created, the GDG base entry is ‘full’ and the oldest era should ‘roll off’ of the GDG and is deleted (SCRATCH). Optionally, if EMPTY is specified relatively than NOEMPTY, all generations (not simply the latest) will roll off when the GDG is full.

The era datasets belonging to the GDG above have dataset names of the shape MY.BUSINESS.DATA.G0001V00, the place the final qualifier (known as the ‘goovoo’ stage) specifies the absolute era quantity – which can vary from 0001 to 9999 as generations are created, rolled off, and deleted. The model quantity (‘Vxx’) is never used. 

Whereas attainable to seek advice from a specific era dataset by its absolute title and model, it’s extra widespread to make use of relative era numbers within the dataset title.

The relative era is specified by inserting it in parentheses following the GDG base title.

The newest, or present era, is era zero – in our instance that is MY.BUSINESS.DATA(0).

• Older era numbers are prefixed by a minus signal – so, the era previous the present era could be BUSINESS.DATA(-1)
• New generations are created by specifying a plus signal: BUSINESS.DATA(+1) and MY.BUSINESS.DATA(+2).

When creating new generations, make certain to specify every new era quantity in ascending order because the dataset names seem within the JCL, significantly in a multi-step job, in order that the generations are catalogued accurately.

Era datasets are generally used not just for peculiar enterprise purposes, however for system information as effectively – significantly SMF information. They’re particularly versatile, since any particular person era dataset inside a GDG can reside on disk or tape, might be SMS-managed or non-SMS, and might have differing block sizes or different traits.

But, GDSs are simply and routinely managed by advantage of their naming conference. Generations are:

• Stored in chronological order
• Routinely deleted as vital
• Referred to individually or as a bunch

Processing All Generations

Whereas most day-to-day processing will most likely take care of era datasets one by one, purposes that course of weekly or month-to-month could wish to take care of all the generations belonging to a GDG directly.

That is achieved by merely specifying the GDG base title within the JCL, with none relative or absolute era quantity. For instance:

//INPUT DD DSN=MY.BUSINESS.DATA,DISP=SHR

This ‘GDG-all’ processing treats the DD assertion as if it had been a mixed enter of all the generations belonging to the GDG.

By default, the generations are processed from the latest to the oldest (LIFO order). They will, nonetheless, be processed from oldest to latest by specifying FIFO both when the GDG base is outlined or on the GDGORDER parameter within the JCL.

In newer releases of z/OS, IBM has continued so as to add options to GDG processing, together with LIFO order and using Prolonged GDGs which may hold monitor of as much as 999 generations relatively than the earlier restrict of 255.

Extra GDG-related parameters have been added to the JCL language. Defaults for GDG DEFINE can now be set within the IGGCATxx member of SYS1.PARMLIB. As well as, customers of Exactly Syncsort Allocation Management Heart (ACC) can benefit from systemwide allocation requirements enforced by the ACC Coverage Guidelines Engine to set insurance policies for the creation and traits of not solely era datasets, however all forms of different SMS or non-SMS information.

GDG: A Core Power of z/OS

GDG processing is a novel energy of the z/OS system.

With little or no effort, a number of iterations of associated information might be grouped collectively, tracked, and managed utilizing peculiar batch job and catalog processing.

GDGs are easy to know and helpful for a variety of each enterprise and system information. They’re usually the spine of a few of the most essential purposes that run on right this moment’s z/OS.

To be taught extra and take the following step past GDGs, see how Syncsort Storage Administration helps you optimize IBM Z storage and keep away from expensive space-related failures.

The publish What’s In a Identify? Mainframe GDGs Get the Job Accomplished appeared first on Exactly.