I don't know if this directly applies, but I was doing some cleanup on our
contents of HSM and I found several files with over 300 generations. Of
course they were all cataloged, most to MIGRAT. When I looked at the catalog
the GDG base only specified 30 generations to be kept, BUT the programmer
had also coded NOSCRATCH. The old generations rolled off the sphere record,
and were then cataloged as simple nonvsam files. I subsequently cleaned up
all of our GDG base records to make sure they specified SCRATCH
----- Original Message -----
From: "Daniel McLaughlin" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Thursday, May 31, 2007 11:24 AM
Subject: Broken GDG Chain
This group is invaluable...
Q. HSM ML1 problems, now we're recovering data. SA recalled 3 versions of a
GDG and they show up in 3.4. However, when the GDG base is expanded, they
no long show in its chain. Does anyone have a magic command to repair that?
I am combing manuals. Google, and the collective knowledge of this forum.
Many thanks in advance.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
