Naming your CICSPlex SM entities

All the entities that you have defined, and entered on to your CICSPlex® SM map, have to be named. You must devise a convention for naming those entities that is both meaningful and extendable.

The rules governing the naming of CICSPlex SM elements are as follows:
  • Each element name can be up to 8 characters.
  • The element name must begin with an alphabetic (or national) character, and must have no embedded blanks. Subsequent characters can be alphabetic or numeric.
  • Names of CICSplexes and of CMASs must be unique in the enterprise.
  • Names of CICS® systems and CICS system groups must be unique in the CICSplex.
  • All other names must be unique for their type in the CICSplex.
The entity types, for each instance of which a name is required, are:
  • CICSPlex SM components and CICSplex entities
    • CMAS, CICSplex, MAS (CICS system or WUI server), CICS system group, and time-period definition.
  • BAS entities
    • Resource assignments, resource descriptions, resource definitions, and resource groups.
      Application resource definitions are:
      • Db2® transactions, files, map sets, partition sets, programs, transient data queues, transactions, CICS BTS process types, document templates, FEPI nodes, FEPI pools, FEPI property sets, FEPI targets, file and key file segment definitions, LIBRARY definitions, map sets, sysplex enqueue models, TCP/IP services, temporary storage models
      Region resource definitions are:
      • Db2 entries, enterprise beans, journals, journal models, local shared resource (LSR) pools, profiles, temporary storage queue models, transaction classes, terminals, typeterms
      System–system connectivity resource definitions are:
      • Connections, Db2 connections, IPIC connections, partners, sessions
  • Monitor entities
    • Monitor definition, monitor group, and monitor specification
  • Analysis entities
    • Analysis definition, analysis group, analysis point specification, analysis specification, action definition, evaluation definition, and status definition
  • Workload management entities
    • Transaction group, workload definition, workload group, and workload specification.

Ensure that any convention you select can accommodate all of these entity types.

Generic names

CICSPlex SM supports the use of generic names in many of its commands. For example, you can specify that all transactions whose names begin with the letters DNW are monitored once every 300 seconds. You do not need to name each transaction individually.

The rules governing the use of generic names are as follows:
  • The asterisk character (*) can be used in place of one or more characters. It can appear once only in any name, and must appear at the end of any partial string. For example, the string DNW* means all names beginning with the letters DNW.
  • The plus sign (+) can replace any single character and can occur in any position in the name. For example, DNW+++L means any name of 7 characters starting with the letters DNW and ending with the letter L.