LU assignment processing for non-unique IDs — synchronous mode

If your site uses LU assignment processing for non-unique UserIDs, and if the process terminates abnormally due to a CICS® Service Flow Runtime system error or an incorrectly modeled flow, this can result in LUs remaining assigned.

The CICS Service Flow Runtime / BTS process that was initiated to execute that modeled flow will, upon issuing a reply to the service requestor, complete.

Under the complete state there will be no CICS Service Flow Runtime / BTS process container information available for subsequent use to locate, use and / or logoff assigned LUs.

For this reason, the LUs that were assigned will have their sessions (FEPI conversations) terminated and assignment deleted before the CICS Service Flow Runtime / BTS process is complete, successfully executed or not.

The CICS Service Flow Runtime DPL Stub program (DFHMADPL), will cleanup / process LUs assigned in this manner before issuing the reply of an executed process to the service requestor.

The DPL Stub program uses the unique tag applied to LU assignments for non-unique UserIDs, in conjunction with the user UserID to:

The CICS Service Flow Runtime / BTS process will then be completed.

Note: If the cleanup / processing of assigned LUs fails, it will render those LUs useless in normal CICS Service Flow Runtime server run-time processing. There is no way to locate, use or release these LUs in subsequent CICS Service Flow Runtime processes. It is essential that process execution of the modeled flow attempt to logoff and release LUs assigned using this method.