Defining remote resources for asynchronous processing

The only remote resource definitions needed for asynchronous processing are for transactions that are named in the TRANSID option of START commands. Note, however, that an application can use the CICS® RETRIEVE command to obtain the name of a remote temporary storage queue which it subsequently names in a function shipping request.

Defining remote transactions for CICS asynchronous processing

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)
    Specifies the name of the transaction as it is known in a remote system, if it is to run in a remote system or region using intersystem communication. The remote system can be another CICS region or an IMS system.
    Restriction: Some asynchronous-processing requests are for processes that involve transaction routing. One example is a START command to attach a remote transaction on a local terminal. To support such requests, the value of the REMOTENAME option and the transaction name must be the same on the local resource definition of the transaction to be started. If they are different, the requested transaction does not start, and the message DFHCR4310 is sent to the CSMT transient-data queue in the requesting system.
  • LOCALQ(NO|YES)

    Local queuing (LOCALQ) can be specified for remote transactions that are initiated by START requests. For further details, see Asynchronous processing.