Defining remote transactions

A remote transaction for CICS asynchronous processing is a transaction that is owned by another system and is invoked from the local CICS system only by START commands.

CICS application programs can name a remote system explicitly on START commands, by means of the SYSID option. If this is done, there is no need for the remote transaction to be defined on the local CICS system.

More generally, however, applications are designed to start transactions without being aware of their location, and in this case an installed transaction definition for the transaction must be available.

Note: If the transaction is owned by another CICS system and may be invoked by CICS transaction routing as well as by START commands, you must define the transaction for transaction routing.
Remote transactions that are invoked only by START commands without the SYSID option require only basic information in the installed transaction definition. Specify the following attributes:
TRANSACTION(name)
REMOTESYSTEM(sysidnt)
REMOTENAME(name)
LOCALQ(NO|YES)
Local queuing (LOCALQ) can be specified for remote transactions that are initiated by START requests. For further details, see Asynchronous processing.


dfht1c00155.html | Timestamp icon Last updated: Sunday, 4 June 2017