> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Thomen > Sent: Thursday, June 30, 2005 12:43 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Rename VSAM Cluster and its components > > > "Gilbert Saint-Flour" <[EMAIL PROTECTED]> wrote in message > news:<[EMAIL PROTECTED]>... > > Hello: > > > > I am looking for a simple way to rename a VSAM cluster > along with its > > DATA & INDEX components. Three ALTER commands in an IDCAMS > step is the > > obvious method, but is there some batch utility program > that can do it > > in a single command, i.e. without having to specify the old and new > > names of the associated objects? Same question for the other > > components in a VSAM sphere, i.e. CLUSTERs, AIXs, PATHs. > What's the > > simplest way to rename the whole sphere just by specifying > the name of > > the cluster? > > There is no guarantee that renaming the cluster name means > the component > names want to be renamed. And what methodology would we use to rename > them? Suppose the new cluster name is 44 chars long? How > many levels of > qualification would we use? > > Users have the ability to name their components as they wish (within > certain limits), and arbritrarily changing those component names may > disrupt utilities or other installation-written programs that > they use. > They may have a REASON for picking specific component names. > Thus, for > IDCAMS to arbritrarily rename the components when the cluster name is > renamed is extremely dangerous. > > Thanks, > Mark Thomen > Catalog/IDCAMS/VSAM Development
I agree with what you say. What would really be nice (OEM product?) would be the ability to have a "template" used for the rename. ALTER MY.DSN.CLUSTER REPLACE(MY.DSN,MY.NEWDS) Of course, you could still have the 44 character limit problem. I guess it might be possible to check before doing any renames and about with a __good__ error message which would state the name of the failing component and the fact that the resulting name is greater than 44 characters. As an example from the above: MY.DSN.CLUSTER -> MY.NEWDS.CLUSTER MY.DSN.DATA -> MY.NEWDS.DATA MY.DSN.INDEX -> MY.NEWDS.INDEX MY.DSN.PATH1 -> MY.NEWDS.PATH1 MY.DSN.AIX1 -> MY.NEWDS.AIX1 MY.DSN.AIX1.DATA -> MY.NEWDS.AIX1.DATA MY.DSN.AIX1.INDEX -> MY.NEWDS.AIX1.INDEX And, to be honest, I could probably write a REXX exec to do the above, if I knew how to easily get the names of all the cluster elements. A simple LISTC ENT won't do it. A LISTC ALL ENT will give the AIX cluster names in the ASSOCIATIONS area, but then I need to do a LISTC ENT on each of them to find their component names and associated PATH name. Not really a problem, just a bother. Too bad there is not a LISTC SPHERE ENT(...), or some such thing. Hum, I guess it's time for the old IGGCSI00 routine. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
