CICS® uses the userid specified on transient data queue definition for security checking in any trigger-level transactions that are not associated with a terminal. Code the USERID operand with the userid that you want CICS to use for security checking for the trigger-level transaction specified on the TRANSID operand. USERID is valid only when the destination facility is a file.
The trigger-level transaction runs under the authority of the specified userid, which must be authorized to all the resources used by the transaction.
If you omit the userid from a qualifying trigger-level entry, CICS uses the default userid specified on the DFLTUSER system initialization parameter. Ensure that the userid of any CICS region in which the transient data queue definition is installed is defined as a surrogate of all the userids specified in the transient data destination definition. This is because, during a cold start, CICS performs a surrogate user security check for the CICS region userid against all the userids specified in transient data queue definitions that are being installed. If the surrogate security check fails, the transient data queue definition is not installed.