180 IMS Version 8 Implementation Guide
dependent regions running application programs, VTAM and OTMA network resources, batch
and utility address spaces, and probably several more. Most of these resources have names
by which they are known to IMS. When IMS systems are cloned, or have similar definitions,
many (or all) of these names are the same throughout the IMSplex and can form the basis for
IMSplex-wide system management functions.
Sysplex
terminal
management addresses the management of a subset of these resources,
primarily those defined as part of the VTAM network. These resources, and the names they
are known by, are shown in Figure 14-2. Note that STM supports neither BTAM nor OTMA
resources.
Figure 14-2 Sysplex Terminal Resources
This figure identifies the resources managed by sysplex terminal management. Each of these
resources can be the source or destination of an IMS message, and has one or more names
associated with it. Each name represents an IMS control block. How IMS handles these
messages is determined solely by its
message destination
name, which usually represents
an anchor block from which to queue the message. Each named resource may be
represented by an entry in the resource structure.
Statically defined VTAM resources (not parallel-session ISC)
Statically defined VTAM resources are defined in the IMS system generation using the TYPE,
TERMINAL, and NAME macros, the NODE name being defined on the TERMINAL macro
and the LTERM name being defined on the NAME macro:
TYPE UNITYPE=SLUTYPE2 (for example)
TERMINAL NAME=NODEname
NAME LTERMname
Static
Dynamic
APPC
ISC
MSC
ISC
Parallel Sessions
Single Session
CF
IMSplex