Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Defining Aliases for a User Catalog z/OS DFSMS Managing Catalogs SC23-6853-00 |
|
To use a catalog, the system must be able to determine which data sets should be defined in that catalog. The simplest way to accomplish this is to define aliases for the catalog. Choosing Aliases and an Alias Search Level discusses general considerations for choosing aliases. Before defining an alias, carefully consider the effect the new alias will have on old data sets. A poorly chosen alias could make some data sets inaccessible. You can define aliases for the catalog in the same job in which you define the catalog by including DEFINE ALIAS commands after the DEFINE USERCATALOG command. You can use conditional operators to ensure the aliases are only defined if the catalog is successfully defined. After the catalog is defined, you can add new aliases or delete old aliases. Catalog aliases are defined in the master catalog,
which contains an entry for the user catalog.
You cannot define an alias if a data set cataloged in the master catalog has the same high-level qualifier as the alias. The DEFINE ALIAS command fails with a "duplicate data set name" error. For example, if a catalog is named PAYROLL.TESTSYS.ICFCAT, you cannot define the alias PAYROLL for any catalog. |
Copyright IBM Corporation 1990, 2014
|