Configuration for Transaction Routing

This section describes any configuration required that is specific to transaction routing. See the section Common Configuration Tasks for configuration that is required for all types of intersystem communication.

You might need to do some specific configuration for outbound transaction routing. There are two ways of ensuring that transactions get routed to a remote system:

• Specify the transaction that you want to route and the system ID of the remote system in an EXEC CICS START command. For example:

  EXEC CICS START TRANSID(CWEN)SYSID(HS01)
  

  starts the transaction CWEN on the remote system HS01.

• Specify the system ID and transaction ID in the resource's local definition. The following table shows the fields that need updating

  Table

  Required Entry

  PCT

  Each remote transaction that can be initiated (using ATI) by a local transaction, specifying: Remote SYSID on the PCT Details page of ESMAC The ID of the SysC table entry for the remote system Remote PCT on the PCT Details page of ESMAC The name by which the transaction is known on the remote system. If you do not specify this field, the transaction is assumed to have the same name on both systems

No specific configuration is required for inbound transaction routing.