Local queuing of EXEC CICS START commands for remote transactions

When a local transaction is ready to ship an EXEC CICS® START command, the intersystem facilities might be unavailable, either because the remote system is not active or because a connection cannot be established. The normal CICS action in these conditions is to raise the SYSIDERR condition.

This can be avoided by using the NOCHECK parameter, and arranging for CICS to queue the request locally and forward it when the required link is in service. Local queuing can be attempted for an EXEC CICS START NOCHECK command if the system name is valid but the system is not available. A system is defined as not available if the system is out of service when the request is initiated, or an attempt to initiate a session to the remote system fails. If either of the above conditions occurs, CICS queues an EXEC CICS START command for a remote transaction only if the following two conditions are met:
  1. The SYSID parameter is not coded in the EXEC CICS START command, and
  2. The local TD entry of the transaction specifies LocalQ=yes.

Local queuing should be used only for EXEC CICS START NOCHECK commands that represent time-independent requests. The delay that is implied by local queuing affects the time at which the request is actually started.