Chapter 14. Sysplex terminal management 183
– Static transactions defined in the IMS system generation
– CPI-C transactions defined in the TP_PROFILE
– Dynamic transactions defined by the Output Creation Exit (DFSINSX0)
Logical terminal names (LTERMs):
– Static LTERMs defined in the IMSGEN
– Dynamic LTERMs created in an ETO environment
Logical link names (MSNAMEs):
– Defined by the MSNAME macro in the IMS system generation
APPC descriptor names:
– Defined in IMS.PROCLIB member DFS62DTx. Although messages are not queued by
APPC descriptor name, this name is used to determine, from the descriptor definition,
what the message destination is.
Summary of IMS resources managed by STM
The above resources are managed by the sysplex terminal management function of IMS
using the resource structure as a repository for resource-related information. “Resources and
the resource structure” on page 195 describes these resources in a little more detail,
including when they are created and deleted and how they are used.
14.4 STM terms and concepts
Sysplex terminal management introduces some new terms and concepts that need to be
understood before discussing the functionality.
14.4.1 Resource type consistency
Resource type consistency is based on the concept of an IMS message destination as
described in , “Message destinations” on page 182. For purposes of resource type
consistency, a message destination is any named resource which may also be the name of a
queue of messages for that resource. For example, in a shared queues environment,
transactions are queued off the (serial) Transaction Ready Queue in the shared queue
structure. Messages destined for logical terminals are queued off the LTERM Ready Queue.
Output messages destined for MSC remote destinations are queued off the Remote Ready
Queue. When a message arrives in IMS, or an application program issues a CHNG or ISRT
call to a TP-PCB, IMS must analyze the name in the message (call FINDDEST) to determine
how to queue the message.
Message destinations have a name type of x’01’ as shown in Figure 14-6 and include:
APPC descriptor names
Other resource types are not checked for consistency since they are not used for message
queuing. For example, it is perfectly alright to have the same name for a NODE, a USER, an
LTERM, and a USERID.
In an IMSplex, each IMS system has its own system definition, although certainly a single
system definition can be shared by all IMSs. When this is done, we say these IMSs are