Dude, Is there any important procedure to do before submitting this job? BTW really thanks for the valuable response.
On Thu, Mar 20, 2014 at 7:48 PM, Pommier, Rex <[email protected]>wrote: > Do you have access to the DFSMSdss Storage Administration manual? The > following is example 5 from the manual, which shows how to do a logical > restore with rename of a VSAM dataset. I would make a minor change, > changing RENAME to RENUNC, but otherwise the example looks like a good one > to start with. > > > > > __________________________________________________________________________________ > | > | > | //JOB3 JOB accounting information,REGION=nnnnK > | > | //STEP1 EXEC PGM=ADRDSSU > | > | //TAPE DD UNIT=3480,VOL=SER=TAPE04, > | > | // LABEL=(1,SL),DISP=(OLD,KEEP),DSN=USER3.BACKUP > | > | //SYSPRINT DD SYSOUT=A > | > | //SYSIN DD * > | > | RESTORE INDD(TAPE) OUTDYNAM(338000) - > | > | DS(INCL(PARTS.VSAM1)) - > | > | RENAME(*.VSAM1,*.VSAM2) - > | > | CATALOG > | > | /* > | > | > | > > |__________________________________________________________________________________| > > > A VSAM key-sequenced data set, PARTS.VSAM1, is restored from a logical > dump tape in this example. It is renamed as PARTS.VSAM2 and cataloged in > the standard order of search. The cluster's components, PARTS.VSAM1.DATA > and PARTS.VSAM1.INDEX, are also renamed. > > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Rajesh Janakiraman > Sent: Thursday, March 20, 2014 9:10 AM > To: [email protected] > Subject: Re: Restoring a VSAM dataset in Production > > Buddy, i have done non VSAM restorations, but i am unaware of VSAM > restoration. I need to know the procedure for how to restore a VSAM dataset > which is the logical one, So kindly provide it. > > > On Thu, Mar 20, 2014 at 7:21 PM, Pommier, Rex <[email protected] > >wrote: > > > Are you saying the backup is a logical backup rather than a physical one? > > If so, you can simply do a restore of the dataset using the RENUNC > > parameter to rename it to the appropriate name to get restored onto your > > restore volume. If it was a physical backup and you are not on z/OS 2.1 > as > > Peter pointed out, you cannot rename a VSAM dataset on a restore. > > > > Rex > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Rajesh Janakiraman > > Sent: Thursday, March 20, 2014 8:29 AM > > To: [email protected] > > Subject: Re: Restoring a VSAM dataset in Production > > > > Sorry mates, > > > > The dataset is a logical one and i need to restore to the volume which we > > created for all restore datasets (we have separate Storage Group for > > restoration). > > So kindly provide the procedure for this logical one. > > > > > > On Thu, Mar 20, 2014 at 6:42 PM, Pommier, Rex <[email protected] > > >wrote: > > > > > IF you have the ability to rename the current production dataset, I > > > believe you could do the following: > > > > > > 1. rename current dataset to a temporary name (don't forget to rename > > the > > > data/index/aix etc, not just the cluster name). > > > 2. restore the backed up dataset - I don't think it would need to go > the > > > same volume but may be wrong, yes you can restore a single dataset > from a > > > full volume backup. > > > 3. It's been a while since I've done this, but you may need to do an > > > IDCAMS DEFINE RECATALOG step here to get the dataset cataloged - I > don't > > > remember what the requirements are for SMS managed datasets. > > > 4. Rename the just-restored dataset to something else. > > > 5. Rename you temporarily-renamed production dataset back to its > > original > > > name. > > > > > > > > > I'm sure others will chime in here if I have something incorrect or am > > > missing steps. I'm giving this procedure based on fading brain > cells... > > > > > > Rex > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List [mailto:[email protected]] > On > > > Behalf Of Rajesh Janakiraman > > > Sent: Thursday, March 20, 2014 6:55 AM > > > To: [email protected] > > > Subject: Re: Restoring a VSAM dataset in Production > > > > > > It is DFSMSdss backup and yes it is physical backup > > > > > > > > > On Thu, Mar 20, 2014 at 5:21 PM, Peter X. DeFabritus < > [email protected] > > > >wrote: > > > > > > > What product took the backup? FDR? DFSMSdss? If the latter, was it > a > > > > full-volume, i.e physical backup? > > > > > > > > On Thu, 20 Mar 2014 06:22:55 -0500, Rajesh Janakiraman < > > > > [email protected]> wrote: > > > > > > > > >Friends, please help me in restoring a VSAM dataset from tape in > > > > Production system. I don't want to replace the existing VSAM dataset > in > > > the > > > > system, since it is the production system i need to restore the VSAM > > > > dataset by renaming it. Kindly help me in it. > > > > > > > > > > >---------------------------------------------------------------------- > > > > >For IBM-MAIN subscribe / signoff / archive access instructions, > > > > >send email to [email protected] with the message: INFO > > IBM-MAIN > > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to [email protected] with the message: INFO > IBM-MAIN > > > > > > > > > > > > > > > > -- > > > Regards, > > > *Rajesh Janakiraman* > > > +91 9790851126 > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > The information contained in this message is confidential, protected > from > > > disclosure and may be legally privileged. If the reader of this > message > > is > > > not the intended recipient or an employee or agent responsible for > > > delivering this message to the intended recipient, you are hereby > > notified > > > that any disclosure, distribution, copying, or any action taken or > action > > > omitted in reliance on it, is strictly prohibited and may be unlawful. > > If > > > you have received this communication in error, please notify us > > immediately > > > by replying to this message and destroy the material in its entirety, > > > whether in electronic or hard copy format. Thank you. > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > > > > > > -- > > Regards, > > *Rajesh Janakiraman* > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > The information contained in this message is confidential, protected from > > disclosure and may be legally privileged. If the reader of this message > is > > not the intended recipient or an employee or agent responsible for > > delivering this message to the intended recipient, you are hereby > notified > > that any disclosure, distribution, copying, or any action taken or action > > omitted in reliance on it, is strictly prohibited and may be unlawful. > If > > you have received this communication in error, please notify us > immediately > > by replying to this message and destroy the material in its entirety, > > whether in electronic or hard copy format. Thank you. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > -- > Regards, > *Rajesh Janakiraman* > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > The information contained in this message is confidential, protected from > disclosure and may be legally privileged. If the reader of this message is > not the intended recipient or an employee or agent responsible for > delivering this message to the intended recipient, you are hereby notified > that any disclosure, distribution, copying, or any action taken or action > omitted in reliance on it, is strictly prohibited and may be unlawful. If > you have received this communication in error, please notify us immediately > by replying to this message and destroy the material in its entirety, > whether in electronic or hard copy format. Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Regards, *Rajesh Janakiraman* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
