Normal TSO alias's - ‘yes’, but I don't understand why you want to do this Alan 
?



Are you trying to solve a problem or a new design of some sort ?



Regards,

Scott





From: Ted MacNEIL
Sent: ‎Friday‎, ‎October‎ ‎3‎, ‎2014 ‎12‎:‎03‎ ‎PM
To: [email protected]





‎Experimented with this, years ago.
Then the HLQS all had to be in the same UCAT to be found.
I tried a relate to a different UCAT: the system never found the library.

-
-teD
-
  Original Message  
From: Staller, Allan
Sent: Friday, October 3, 2014 09:25
To: [email protected]
Reply To: IBM Mainframe Discussion List
Subject: Re: Alias relating to Non-VSAM datasets

I do not believe you can do this (using only "standard" facilities). 

Without looking it up, I am 99% positive that hlq1 and hlq2 *must* be in the 
same user catalog for this to work.

As others have also pointed out, symbolicrelate may be of help, however, I 
would not be optimistic based on the sample below.

HTH,

<snip>
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?

----------------------------------------------------------------------
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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to