The ALIAS must be in the same catalog as the actual dataset.
I think you could bypass this in a very "strange" way by:
1. definig an ALIAS XX35.SYS3 in your CATALOG.USERTSO poiting to
CATALOG.USERSYS.
2. Then, definig your ALIAS with the SYMBOLICRELATE in CATALOG.USERSYS.
Regards, Lucas
On Tue, May 29, 2018, 23:10 Michael Babcock <bigironp...@gmail.com> wrote:
> Okay, I'm getting myself confused regarding SYMBOLICRELATE.
>
> I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want
> to define an alias called XX35.SYS3.LINKLIB (XX35 hlq data sets reside in
> CATALOG.USERTSO) that points to the SYS3.LINKLIB data set. I've issued:
>
> DEF ALIAS(NAME(XX35.SYS3.LINKLIB) SYMBOLICRELATE(&SYS3LNK_))
> CAT(CATALOG.USERTSO)
>
> And have SYMDEF(&SYS3LNK_='SYS3.LINKLIB') defined in IEASYMxx.
>
> The define works just fine, but it doesn't locate the data set. I get
> "Dataset Not Cataloged" in ISPF 3.4 What am I doing wrong?
>
> LISTC ALL ENT('XX35.SYS3.LINKLIB')
>
> ALIAS --------- XX35.SYS3.LINKLIB
> IN-CAT --- CATALOG.USERTSO
> HISTORY
> RELEASE----------------2 CREATION--------2018.149
> ENCRYPTIONDATA
> DATA SET ENCRYPTION-----(NO)
> ASSOCIATIONS
> SYMBOLIC-&SYS3LNK_
> RESOLVED-SYS3.LINKLIB
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
