Transactional Security with the TDC

The TDC makes transactional security available to z/OS CICS Distributed Processing Servers, allowing three possible modes:

Default: DPS transactions start with the user ID of the TDC, which it inherits from the trigger monitor transaction (CKTI) or the transaction definition.
Security Override: Specify a user ID to be used by all Distributed Processing Servers the TDC has started. The external security manager must also know this ID. If CICS uses surrogate checking, you must define the user ID associated with the transaction as surrogates for the override user IDs.
Message ID Security: The TDC extracts the user ID from the inbound message and uses it as the user ID for starting the DPS. Each individual user ID likely to initiate a DPS must be defined to the external security manager, while the user ID associated with the TDC must be authorized as surrogates for them all.

Note: The TDC uses the CICS system programmer interface (SPI) and must be authorized to use SPI commands.