The reason for trying to do this was some user's request who were trying to clone some production application for testing and needed some datasets cloned under a different HLQ and then pointing it to another dataset (with a different HLQ). After experimenting a bit with the define alias and suggestions from others on the list, I have suggested them to use another hlq.
I did try SYMBOLICRELATE as well, but that needed a symbol to be part of the dataset name, and I didn't have any system symbol (already defined) that would fit in the requirement, so I couldn't use that. Regards Varun On Fri, Oct 3, 2014 at 6:48 PM, Lizette Koehler <[email protected]> wrote: > I am not clear on why you want a different HLQ. > > Perhaps the SYMBOLICRELATE might be more helpful. You can use Symbolics > on different LPARs but have the same dataset name used on all. > > For example. > > DSN A.B.C can be used on all lpars > Underneath the symbolicrelate says on > LPAR1 A.B.REL1.C > LPAR2 A.B.REL2.C > LPAR3 A.B.BASE.C > > The Third node would be based on an &REL that is defined in the IEASYMxx > member of parmlib. This way each lpar has the base name of A.B.C cataloged > for all users/tasks. But the resolution of which dataset to use is > controlled by the SYMBOL entry in IEASYMxx. > > > Is this something that you would be able to use for your process? If > not, please let us know what you need to do with the two different HLQs. > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Mainframe Sysprog > > Sent: Thursday, October 02, 2014 10:33 PM > > To: [email protected] > > Subject: Alias relating to Non-VSAM datasets > > > > Hi List, > > > > I am trying to define an alias pointing to a non-VSAM dataset. Such as > HLQ1.DSN > > catalogued in CATALOG.UCAT1 pointing to HLQ2.DSN.LOADLIB catalogued in > > CATALOG.UCAT2 > > > > Is this possible? > > > > I tried following IDCAMS control statements but they failed with the > following > > message: > > > > DEFINE ALIAS - > > (NAME(HLQ1.DSN) - > > RELATE(HLQ2.DSN.LOADLIB)) - > > CATALOG(CATALOG.UCAT1) > > > > IDC3022I INVALID RELATED OBJECT > > IDC3009I ** VSAM CATALOG RETURN CODE IS 80 - REASON CODE IS > > IGG0CLER-4 > > > > The explanation for the message doesn't really offer much help. > > > > If I remove the CATALOG parm from the control statements above, the > alias does > > get defined, but it gets catalogued in CATALOG.UCAT2 (I can't seem to > understand > > why!) > > > > The IBM manual doesn't specifically mention if the two HLQ's should be > cataloged > > in the same user catalog, but that's what I have been thinking. > > Is that correct? > > > > Is it possible at all to define the alias pointing to another dataset in > another catalog? > > > > Thanks > > Varun > > > > > > ---------------------------------------------------------------------- > 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
