START TRANSID commands

In a transaction that uses the START TRANSID command to start other transactions, you must maintain logical data integrity.

You can maintain data integrity by following these guidelines:
  1. Always use the PROTECT option of the START TRANSID command. This ensures that if the START-issuing task is backed out, the new task will not start.
  2. If you pass data to the started transaction (on one of the data options FROM, RTERMID, RTRANSID, or QUEUE), ensure you define the associated temporary storage queue as recoverable in its TSMODEL resource definition. You can select a name for the temporary storage queue by specifying the REQID option of the START command when using any of the data options. If you do not use REQID, the temporary storage queue name generated by CICS is in the format ‘DFRxxx'.

Defining the temporary storage queue as recoverable ensures that data being passed to another task is deleted from the temporary storage queue if the START-issuing task fails and is backed out. If a system failure occurs after the START-issuing task has completed its syncpoint, the START command is preserved. CICS® starts the transaction specified on a recoverable START command after an emergency restart, when the expiry time is reached and provided the terminal specified the by TERMID option is available.

Note: Consider using EXEC CICS RETURN TRANSID(…) with the IMMEDIATE option if the purpose is to start the next transaction in a sequence on the same terminal. This does not unlock the terminal, and in a dynamic transaction routing (DTR) environment, the transaction is eligible for DTR.


dfht23y.html | Timestamp icon Last updated: Monday, 5 June 2017