VSAM. Aaaaah! *turns and runs away* You'll need a RECAT to force cataloging of all the renamed components in the right catalog. (That's why RENUNC(*) is recommended.)
As far as volumes...it's been so long since I've done a restore of a VSAM data set, and that was not in an SMS environment - so hardcoding of volumes was required (OUTDY(volser,unit)). SMS might help here, but I'll have to defer to others. Later, Ray > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin > Sent: Monday March 20 2006 14:40 > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: List contents of DFSMSdss-produced dump? > > In a recent note, Ray Mullins said: > > > Date: Mon, 20 Mar 2006 14:24:30 -0800 > > > > First, run with PARM='TYPRUN=NORUN', so you won't actually copy > > anything off the tape. > > > Got it. Thanks. > > > Then use INCLUDE((**)). ADRDSSU will show you all of the data sets > > dumped/copied onto the tape. > > > > Then, once you figure out what's there, and what to rename > to (usually > > just changing the HLQ is sufficient to get the data on disk, then > > rename afterwards), then take out the PARM. > > > And I have three identical HLQs to play with on the data sets. > > I see some additional detail on the VSAM CLUSTER contained: > CATALOG; COMPONENT; COMPONENT. Will RESTORE unwind the > CATALOG information correctly? > > Do I need to specify a volume to restore to, or can I let SMS > choose the volume(s)? ---------------------------------------------------------------------- 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
