On Mon, 29 Aug 2016 16:27:38 -0700, Charles Mills wrote:
>
>Tell it when? A "batch JCL" time? Then yes, that largely negates the purpose.
>Or at "define the alias" time? Something like DEFINE ALIAS ...
>CATALOG(MASTER). That would be okay.
>
Well, not really. At execution, the job will seek JOEBLOW.MY.FOO.BAR in the
catalog
associated with JOEBLOW, not SYS1. Unless you configure JOEBLOW as associated
with the master catalog. I doubt your sysadmin will allow that.
Somewhere in there:
Optional Parameters
CATALOG(catname)
Identifies the catalog in which the alias is defined. If the catalog's
volume is physically mounted, it is dynamically allocated. The volume must be
mounted as permanently resident or reserved. See Catalog Selection Order for
DEFINE for the order in which a catalog is selected when the catalog's name is
not given.
catname/alias
Names the catalog or an alias that can be resolved to a catalog. When
the alias is for a user catalog connector, catname is the name of the master
catalog or user catalog in which the connector record has been defined.
Abbreviation: CAT
Parent topic: DEFINE ALIAS Parameters
I deem that useless.
>What about @Lizette's SYMBOLICRELATE? Will that bridge catalog to catalog?
>
I suspect not. I'll wait for an expert's opinion. I suspect the HLQ must not
be
symbolic.
>BTW, why is an alias for a non-VSAM data set called ALIAS but an alias for a
>VSAM data set is called PATH? It seems to me they should be interchangable.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
