Could you provide a bit more detail? The questions I have are
1) Is this proclib used in JCLLIB DD statements and you want to rename it without having to change all of the JCLLIB statements? 2) Is this proclib buried in a lot of JCL and you cannot identify and change every jcl in a timely manner? 3) Is this proclib in a source management product (CHANGEMAN, ENDEVOR, etc...) and this would be easier than updating the product? Since I am not clear on your needs, let me provide a suggestion If using JES2 (I do not know JES3), if you add the new proclib to the JES2 concatenation and move all of the procs from the old lib to the new one, even if you have a JCLLIB statement in JCL, JES2 will see the JCLLIB proc is empty and then search its PROCLIB concatenation. I will do some testing when I get to work, but I think what you are trying to do is valid, just the steps may not be in the correct order. Steps I think should work 1) Make sure your current proclib is valid (you can browse it) 2) DEFINE new.proclib.name ALIAS RELATE(old.proclib.name) If you cannot browse your current proclib, see if it is still on the volume and catalog it. Then you should be able to do the LISTC on either and get the same dataset. If this does not work, you will need to do the LISTC on both the current and new proclib names and post it here. Also do a listing on your usercat for all entries and see if the old name and new name are in there. If you have a previous catalog entry for new name, delete the new related name. Otherwise, just use a totally different name but the HLQ is in the same catalog. Say the new RELATED name you are trying to create is My.PROCLIB.NEW for MY.PROCLIB. Then try it with MY.PROCLIB.VERYNEW for MY.PROCLIB. If you see the new name in ISPF 3.4 but you cannot browse it, then delete that name from the catalog. You also should post the complete output from your DEF ALIAS command. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of mf db Sent: Wednesday, August 21, 2013 7:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Deleting Alias Lizette, But I am not able to create and relate with same alias and I get a duplicate dataset entry. Here the background is that I am trying to use this alias in one of our proclibs. On Wed, Aug 21, 2013 at 8:12 PM, Lizette Koehler <stars...@mindspring.com>wrote: > In 3.4 if you display the dataset and then PF11 - see if there are > dataset attributes. If there is no space, no lrecl, no blksize, and > so forth, then all you have is a catalog entry and that is it. You > can create as many catalog entries as you like that do not have REAL datasets underneath them. > > Lizette > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of mf db > Sent: Wednesday, August 21, 2013 7:40 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Deleting Alias > > Elardus, > > I tried viewing via ISMF and I could see the alias entry pointing the > same usercatalog, but when I type Browse agains the alias I get a > message as "Dataset not catalogued" > > > On Wed, Aug 21, 2013 at 8:01 PM, Paul Gilmartin <paulgboul...@aim.com > >wrote: > > > On Wed, 21 Aug 2013 07:17:27 -0700, Lizette Koehler wrote: > > > > > >DEF TED.MY.FILE ALIAS RELATE(BOB.MY.FILE) then both BOB hlq and > > >TED hlq must be in MYUCAT1 > > > > > You can control which catalog the TED alias is created in, but if > > the catalogs are different you lose either way. If you create TED > > in BOB's catalog, catalog search fails to find TED; if you create > > TED in its proper catalog, catalog search fails to find BOB. > > > > >I may have that backwards, but it is close. Bottom line, the > > >example IBM has in the book for doing this is very bad. I will be > > >opening a request > > for > > >updating that to a more reasonable example. ... > > > > > Rather, that should be a Requirement that it be done right, not a > > RCF for documentation that it is done wrong. > > > > > ... Second, from the document it appears that the HLQs should > > >be in the same UCAT. At least that is my understanding from > > >reading the IBM doc (which is very nebulous at > best). > > >And I do not believe that you are required to use the CAT parameter > > >in the DEF ... ALIAS RELATE(....) function > > > > -- gil > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
