Service flows with different user IDs

When you use different user IDs for service flows, the FEPI logical units are assigned and released as modeled in the service flow project tools.

Leaving a user ID assigned for subsequent processing might improve the performance because the signon processing to access target applications is not required for each service flow request.

If a logical unit is left assigned to a user ID in synchronous or asynchronous mode for use in subsequent process execution, the service requester is responsible for logging off the user ID when it is no longer required. For example, as a normal end of day processing strategy, the service requester could invoke a service flow to locate, log off, and release any assigned logical units. Failure to incorporate a cleanup strategy for a specific user might not leave logical units available over time to other users, unless your configuration is such that a significant number of logical units are available.

The CICS Service Flow Runtime does not locate and clean up logical units that are left assigned upon successful or unsuccessful execution of service flows.



luownersynch.html | Timestamp icon Last updated: Sunday, 4 June 2017