The userid relation

When you define an affinity relation of userid to a transaction group, all instances of the transactions that are initiated from a terminal, by a START command, or by a CICS BTS activity, and executed on behalf of the same user ID, must execute in the same target region for the lifetime of the affinity.

If the affinity relation is userid , the affinity lifetime must have one of the following values:
Pseudoconversation
The affinity lasts for the whole pseudoconversation, and ends when the pseudoconversation ends for that user ID. Each transaction must end with EXEC CICS RETURN TRANSID , not with the pseudoconversation mode of END.
Signon
The affinity lasts for as long as the user is signed on, and ends when the user signs off. This lifetime is possible only in those situations where only one user per user ID is permitted. Signon lifetime cannot be detected if multiple users are permitted to be signed on with the same user ID at the same time (at different terminals).
System
The affinity lasts for as long as the target region exists, and ends whenever the target region terminates (at a normal, immediate, or abnormal termination).
Permanent
The affinity extends across all CICS restarts. If you are running CICSPlex® SM , this affinity lasts for as long as any CMAS involved in managing the CICSplex using the workload is active.
Delimit
The affinity continues until a transaction with a pseudoconversation mode of END is encountered.

A typical example of transactions that have a userid relation is where the user ID is used dynamically to identify a resource, such as a TS queue. The least restrictive of the affinities in this category is one that lasts only for as long as the user remains signed on.

Figure 1 shows an example of an affinity group with the userid relation and a signon lifetime.
Figure 1. Managing inter-transaction affinity with userid relation and signon lifetime
An example of a transaction in a group with a lifetime signon affiniy relation, routed as described in the following text.

In this example, any instance of a transaction from a terminal starts a signon lifetime affinity. It can be routed to any suitable target region (AOR1 through AOR6), but other transactions in the group for the same user (ANOTHER in this example) must be routed to whichever target region is selected for the first instance of a transaction in the group.