Transaction Manager resources
This topic discusses the following types of Transaction Manager (TM) resources.
TM resources: APPC descriptors
IMS defines APPC descriptors to RM at initialization or during /STA LU62DESC to maintain resource type consistency for message destinations.
TM resources: VTAM LTERMs
IMS defines VTAM® LTERMs to RM for resource type consistency for message destinations, name uniqueness for LTERMs, and LTERM status recovery.
TM resources: MSNAMEs
MSC networks use MSNAMEs to define remote IMS systems and logical link paths between remote and local IMS systems in an MSC network. For MSNAMEs, Resource Manager (RM) enforces only resource type consistency for message destinations, but not resource name uniqueness.
TM resources: VTAM terminal nodes
IMS defines nodes to RM to enforce name uniqueness for single-session VTAM terminals and to recover node status.
TM resources: transactions
IMS defines a transaction dynamically with the type-2 CREATE TRAN command or statically in the system where the application will run or dynamically as a CPI-C transaction executed by an APPC conversation. A transaction can run in multiple systems concurrently as name uniqueness is not enforced.
TM resources: user names
The user name and the user ID are usually the same; however, user exits and descriptors can override the user name. The
user
is the user signed on to a dynamic terminal or parallel session subpool and has associated work and status. The
user ID
identifies a person signed on to a terminal for security authorization by a security product such as RACF®.
TM resources: user IDs
The
user ID
identifies a person signed on to a terminal for security authorization by a security product such as RACF.
Parent topic:
Planning for Transaction Manager resources in an IMSplex