By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,458 Members | 1,216 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,458 IT Pros & Developers. It's quick & easy.

DB2 UDB v7 for z/OS TEMPLATE not creating GDG base for absolute generations

P: n/a
The discussion in the Utilities manual under working with GDGs says:

| TEMPLATE DSN operands support both GDG absolute version references and
| relative references. DB2 detects the absence of a GDG base and creates it,
| with a limit of 99 entries, by default.

I coded GDGLIMIT as (27), so the discussion about coding (0) to suppress
this shouldn't apply.

When I add a new Tablespace Image Copy to an existing stack I like to have
the same absolute generation number for everything in the stack, so
I coded an absolute generation number on the template the last time I did
that, instead of (+1). My intent was to have the newly added Image Copies
start with the same absolute generation that the previously existing GDGs
would have used.

Why do I care? These were for development Image Copies and the developers
may want to recover farther back than TOLASTCOPY and farther back than
log data is available for TORBA. Synchronizing the Absolute Generation
numbers makes that chore a bit simpler.

The COPY failed with codes indicating that a DEFINE GDG had not been done for
the GDG Base needed for the new Image Copy datasets.

Changing the Template to (+1) got COPY to run to the end without a problem.

Did I miss something about automatic creation of GDG bases being restricted
to relative generation references?
Dec 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.