Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Using the DEFINE Command z/OS DFSMS Managing Catalogs SC23-6853-00 |
|
Data sets of all types can be cataloged. This can be accomplished through JCL, dynamic allocation, access method services, IEHPROGM, or other utilities. If you are using the Storage Management Subsystem, data sets are automatically cataloged. When you issue the access method services DEFINE command to create a catalog object, a catalog entry is built that describes the object. Before an object can be defined, there must be a catalog in which to define the object. The catalog is chosen according to the catalog search order. When you define a catalog data set or object, you specify attributes to be associated with it. The attributes include, for example, the SMS Management Class name to be associated with the data set. After the object is defined, it can be processed with other access method services commands and with application programs. Password protection is ignored for the protection of any data set cataloged in a catalog, including the catalogs themselves. This is a change from previous releases where passwords were ignored only for SMS-managed data sets. When you define a catalog, cluster, or alternate index, you can
specify attributes in several different ways. The parameter set
for DEFINE USERCATALOG, MASTERCATALOG, CLUSTER, and ALTERNATEINDEX
is directly related to the way the attributes are stored in the catalog.
The catalog entries that describe a catalog, cluster, or alternate
index are:
When you specify attributes as parameters of USERCATALOG, MASTERCATALOG,
CLUSTER, or ALTERNATEINDEX, consider the following:
You can use the LISTCAT command with the ALL option to list catalog entries and to determine what various attributes are stored in the catalog. See z/OS DFSMS Access Method Services Commands for a description of the attributes for each type of entry. |
Copyright IBM Corporation 1990, 2014
|