Special attribute and resource table considerations

Certain attributes in the CICSPlex® SM resource tables are for internal use only; you should not attempt to modify or manipulate them. Similarly, certain resource tables can be accessed only in certain ways.

EYU_ attributes

In CICS® resource and CICS monitored tables, CICSPlex SM uses the following attributes to uniquely identify which CICS system contains the resource:
  • EYU_CICSNAME
  • EYU_CICSREL

These attributes are included in every CICS resource and CICS monitored resource table record and can be used by the CICSPlex SM API. However, you cannot refer to these attributes in any batched repository-update facility command.

CHANGEAGENT, CHANGEAGREL, CHANGETIME, CHANGEUSRID, and CREATETIME attributes

The resource table descriptions identify the CHANGETIME attribute for CICSPlex SM and CICS definitions. The CHANGETIME attribute always contains the date and time of the last modification to the definition. CICS definition resource tables also include the CREATETIME attribute, which is the date and time when the definition was created.

Attribute fields CHANGEAGENT, CHANGEAGREL, and CHANGEUSRID in the resource table resource definition record, combined with the existing CHANGETIME and CREATETIME attributes, form the resource definition signature and are valid only for BAS resource definitions.

CHANGEAGENT displays how the resource was defined or last modified. CHANGEAGREL contains the level of CICS system that created or last modified the resource definition. CHANGEUSRID contains the user ID that created or last modified the resource definition.

The CHANGEAGENT, CHANGEAGREL, CHANGETIME, CHANGEUSRID and CREATETIME attributes are maintained internally by CICSPlex SM. Do not attempt to change their values in any way.

LNKSxSCG Records (LNKSMSCG, LNKSRSCG, LNKSWSCG)

When a CICSPlex SM specification-to-CICS group link record (LNKSxSCG) is created or removed, an additional operand, keyword, is required. This keyword indicates how the link being created or removed applies to the current members of the CICS system group.

The keywords for the CREATE and REMOVE commands are as follows:
CREATE
Specify one of the following parameters:
FORCE
All current members of the CICS system group should have implicit links established to the named specification. When a link already exists, it is replaced with the newly created link.
NULL
Current members of the CICS system group should have implicit links established to the named specification only if no link already exists.
NONE
No implicit links should be established.
REMOVE
Specify one of the following parameters:
KEEP
All implicit links are to be converted to explicit links.
NONE
No implicit links are to be converted to explicit links.
Note: You cannot update LNKSxSCG records using the API or batched repository-update facility; you must use either the CICS Explorer® or the Web User Interface.

LNKSxSCS Records (LNKSMSCS, LNKSRSCS, LNKSWSCS)

When a CICSPlex SM specification-to-CICS link record (LNKSxSCS) is created or removed using the batched repository-update facility, two of the keyword (value) operand pairs cannot be used. The keyword(value) pairs that must be omitted from the CREATE and REMOVE commands are the LINK and GROUP pairs.

CSYSDEF xxxACTION and xxxSEV attributes

The CICSPlex SM API allows the CSYSDEF xxxACTION and xxxSEV attributes to be used in more than one way.

The following values can be specified for the xxxACTION attributes:
  1. The name of an action that is to be taken when this condition occurs.
  2. An asterisk (*). This allows the action to be inherited. The rules for specifying inheritance are given in the CSYSDEF Resource Table in CICSPlex SM resource tables.
  3. Leave the attribute blank. This causes a default value to be used. Default notification values are listed in Default notification values.
The following values can be specified for the xxxSEV attributes:
  1. The value that is to be used as the severity for this condition.
  2. NO. This means that the condition is not to be monitored.
  3. The EYUDA INHERIT value. This causes the value to be inherited.
  4. The EYUDA N_A value. This causes the default security level for this condition to be used.