LU assignment processing for non-unique UserIDs assumes that UserIDs at your site are not unique.
If you use non-unique UserIDs, you will not be able to take advantage of some CICS® Service Flow Runtime processing capabilities. See Why you should use unique user ids with CICS Service Flow Runtime for information about the benefits of unique UserIDs.
In a configuration where the user UserID is not unique, CICS Service Flow Runtime run time processing ensures that LUs within the same FEPI pool are assigned uniquely to the non-unique UserID. CICS Service Flow Runtime accomplishes this by appending a unique tag to the LU owner assignment on the CICS Service Flow Runtime V3.1 SLU Connection alternate (DFHMAC1F) file key. This unique tag is comprised of the CICS Applid and EIBTASKN of the CICS Service Flow Runtime DPL Stub program (DFHMADPL).
The unique tag, which is retrieved in the CICS Service Flow Runtime DPL Stub program (DFHMADPL), is used in conjunction with the user UserID as part of the LU assignment during process execution. The run time processing of an LU assignment for a non-unique UserID using FEPI adapters is as follows:
In addition to the processing associated with LU assignment for non-unique UserIDs, CICS Service Flow Runtime V3.1 server run-time provides clean-up logic in the DPL Stub program. This clean-up logic is invoked when the process terminates abnormally resulting in LUs remaining assigned. See LU assignment processing for non-unique IDs — synchronous mode and LU assignment processing for non-unique IDs — asynchronous mode for a description of how the DPL Stub program implements clean-up logic to remove the LU assignments that remain on the SLU Connection alternate (DFHMAC1F) file key after a process terminates abnormally.
See CICS Service Flow Runtime FEPI file processing for a description of how CICS Service Flow Runtime uses the CICS Service Flow Runtime SLU Connection file.