For its configuration and for its operation, CICSPlex® SM requires a variety
of entities to be defined. 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 within the enterprise.
- Names of CICS® systems and CICS system groups must be unique within the CICSplex.
- All other names must be unique for their type within the CICSplex.
The entity types, for each instance of which a name
is required, are:
- CICSPlex SM components and CICSplex entities
- CAS, CMAS, CICSplex, MAS (CICS system), 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, IIOP request models, map sets,
sysplex enqueue models, TCP/IP services, temporary storage models
Region resource definitions are:
- DB2 entries, enterprise beans, journals, journal models (CICS Transaction Server for OS/390, Version 1 Release 3 or
later), local shared resource (LSR) pools, profiles, temporary storage queue
models, transaction classes, terminals, typeterms
System-system connectivity resource definitions are:
- Connections, DB2 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. A naming convention, for use generally in CICS environments, is described in the CICS/ESA publication Dynamic Transaction Routing in a CICSplex. For an example, see The Starter Set naming convention.
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 to be monitored once every 300
seconds. You do not have to name each transaction individually.
The rules governing 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.
[[ Contents Previous Page | Next Page Index ]]