There may be many instances of actual objects for a given resource class in a CICSplex. Each object instance is a named entity. One or more attributes provide the instance key. For example, the attribute TRANID in the LOCTRAN resource class identifies the attribute that is the name or key field. Resource class key fields are highlighted in the resource table descriptions. Some resource classes have multiple key fields.
For resource classes that describe CICSPlex® SM definitions, the key attributes are used to construct the physical keys used in the EYUDREP VSAM KSDS file. For these resource classes, one or two key fields are defined. One key field is identified as the Primary key. The other field, if used, is identified as the Secondary key. A suffix of -n where n is the key level number is aded to the name in the table.
Key fields are used to:
When you create, update, or remove a CICSPlex SM definition, you must supply all the key values. Furthermore, the values for the key fields must be specific; generic values are not allowed.
When you list or dump CICSPlex SM definitions, only the Primary key field can be referenced. For these statements, both specific and generic values are allowed for key fields.
The instance pattern field in the EVALDEF create panel identifies a specific or generic pattern for the key field of a resource table. The INSTANCE attribute of the EVALDEF resource table is the field in which this information is stored.
The CICSPlex SM resource table descriptions in the following sections identify the Primary key field for each CICSplex definition resource class.