Setting up a CICS region to flow user IDs

A region flows users IDs to a remote system if the OutboundUserIds attribute of the local CD entry for the remote system is set to sent, sent_maybe_with_password, or sent_only_with_password. If the remote system to which you are sending cannot receive inbound user IDs, set the OutboundUserIds attribute to not_sent.

Table 1 shows which user ID is flowed when a local task issues an intersystem request to a remote system.

Table 1. Which user ID is flowed when local task issues a request
Characteristics of the local task User identifier sent by CICS® to the remote region
Task with associated terminal; user signed on Terminal user identifier.
Task with associated terminal; no user signed on The region's DefaultUserId.
Task with no associated terminal started by interval control EXEC CICS START User identifier for the task that issued the EXEC CICS START command.
Task with no associated terminal, triggered by a transient data queue User Identifier whose TDQ write triggered the task.
CICS system task Local Sysid of the region.
Program started by Distributed Program Link (DPL) The user ID is the one associated with the task. This depends on the CD RemoteSysSecurity and LinkUserId settings for the connection that started the task. For example:

RemoteSysSecurity=local: either link user ID or default user ID.

RemoteSysSecurity=trusted orverify: either flowed user ID or default user ID.

Back-end Program started by Distributed Transaction Processing (DTP). The user ID is the one that is associated with the task. This depends on the CD RemoteSysSecurity and LinkUserId settings for the connection that started the task. For example:

RemoteSysSecurity=local: either link user ID or default user ID.

RemoteSysSecurity=trusted or verify: either flowed user ID or default user ID.

By default, CICS never flows passwords with these user IDs. This is because all local user IDs that are running transactions in a region have had their passwords checked. Therefore, set up remote systems in the SNA definitions to accept user IDs that are flowed by a region as already_verified See Receiving user IDs from SNA-connected systems for more information.

If you want your CICS region to send passwords, see Setting up a CICS region to flow passwords.