Link3270 bridge server adapter processing for non-unique user IDs assumes that the user IDs at your site are not unique. When you use non-unique user IDs, you will not be able to take advantage of some CICS® Service Flow Runtime processing capabilities.
In a configuration where the user UserID is not unique, CICS Service Flow Runtime processing ensures that Link3270 bridge facility session state data is stored uniquely to the non-unique UserID. CICS Service Flow Runtime accomplishes this by appending a unique tag to the Link3270 State file (DFHMALSF) owner assignment. This unique tag is comprised of the CICS Applid and the EIBTASKN of the DPL Stub program (DFHMADPL).
The unique tag, which is retrieved in the DPL Stub program (DFHMADPL), is used in conjunction with the user ID as part of the Link3270 State file assignment during process execution. The runtime processing of a non-unique user ID using Link3270 bridge server adapters is as follows:
In addition to the processing associated with Link3270 bridge facility assignment for non-unique user IDs, CICS Service Flow Runtime provides cleanup logic in the DPL Stub program and in the Navigation Manager (DFHMAMGR). This cleanup logic is invoked when the process terminates abnormally resulting in allocated Link3270 bridge facilities and associated state data. See Link3270 State file processing for non-unique IDs — synchronous mode and Link3270 State file processing for non-unique IDs — asynchronous mode for a description of how the DPL Stub program implements cleanup logic to remove the bridge facility state data that remains on the CICS Service Flow Runtime Link3270 State file (DFHMALSF) after a process terminates abnormally.