With the nature of the last eight characters of a GDS name, the likelihood of it not changing between FILE1 and FILE2 is very low. If the GDS is on tape, renaming is not an option.
> Date: Sat, 6 Nov 2010 09:53:53 -0500 > From: [email protected] > Subject: Re: IDCAMS ALTER and GDGs - From A(0) to B(+1) - Relative Generations > To: [email protected] > > If a tape dataset name is 17 characters or longer (and the last 17 > characters do not change), I believe that it can be renamed, using a DEFINE > NVSAM command (with DEVTYPE, VOLUMES and optionally FSEQN), along with the > requisite DELETE '<dsn>' NOSCRATCH command. At least with CA-1, there are > TMC update utilities TMSUPDTE and TMSUDSNB ("restricted use" though), as > well, to consider using with this activity, where any DSN length is a > candidate for change. > > Scott Barry > SBBWorks, Inc. > > > On Fri, 5 Nov 2010 14:37:21 -0700, Ulrich Krueger <[email protected]> wrote: > > >Martin, > >Unless something changed since the last time I looked at this ... > >You cannot rename a dataset on tape. > >1) Your tape management system probably wouldn't like it. > >2) The physical tape label info can not be changed after the tape has been > >created. > > > >AFAIK, your only way to "rename a tape dataset" is to copy it to a new tape. > > > > > >Regards, > >Ulrich Krueger > > > >-----Original Message----- > >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > >Of Martin Packer > >Sent: Friday, November 05, 2010 12:54 PM > >To: [email protected] > >Subject: IDCAMS ALTER and GDGs - From A(0) to B(+1) - Relative Generations > > > >I'm looking at a customer batch job and they are rolling over 12 monthly > >files by 1 - the oldest going off to another data set on tape. They are > >doing this with ICEGENER copy steps. Each monthly file is a different GDG. > >Rather than do the actual copying I'd like them to explore using some form > >of rename. > > > >In this case it boils down to renaming FILE1(0) to FILE2(+1). IDCAMS ALTER > >will do it with hardcoded generations and versions. I checked this and > >that the structure of the target GDG was intact - by coding some JCL on my > >own system. > > > >However, I'd prefer not to have to recommend absolute generations and > >versions. Does anyone know how to do this with (0) and (+1)? > > > >Yes, I'm aware there may be some operational difficulties with this > >approach - we didn't keep n generations this way. I'm not convinced the > >customer actually wants to. I want to present them with options. > > > >Thanks, Martin > > > >Martin Packer, ---------------------------------------------------------------------- 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
