The CICS® Service Flow Runtime SLU Connection file (DFHMACOF) is mapped by copybook DFHMARCO
in the CICS Service Flow Runtime product library .SCIZMAC. It has an associated alternate
file, (DFHMAC1F). The files are used to track the state of connections and
conversations and ownership of conversations.
The
CICS Service Flow Runtime Target Interaction file (DFHMATIF), is mapped by copybook
DFHMARTI in the
CICS Service Flow Runtime product library .SCIZMAC. Normally, this file
is used to store the last buffer (max. 3600 bytes) sent or received from and
to the defined target applid or application transaction as modeled in the
service flow. The buffer is used in subsequent FEPI processing when active
conversations are acquired (FEPI ALLOCATE PASSCONVID), to determine the processing
state of the conversation.
- Force, Release, Hold indicate the CICS Service Flow Runtime SLU
Connection file record must be deleted for the defined connection (i.e., the
defined target and node that was in use). There is no buffer written CICS Service Flow Runtime Target
Interaction file in this case.
- Pass indicates the CICS Service Flow Runtime SLU Connection
file record for the connection and conversation in-use should not denote any
ownership (i.e., SC-LU-OWNER = spaces). The SLU Connection file record is
rewritten indicating no ownership of the existing conversation. The conversation
is available for use in another task. The Target Interaction file is written
with the last buffer sent or received.
- Leave assigned indicates the CICS Service Flow Runtime SLU
Connection file record for the connection and conversation that is in-use
should be left assigned or indicate ownership (i.e., SC-LU-OWNER = Userid).
If your site is implementing LU owner assignment
for non-unique UserIDs, CICS Service Flow Runtime appends a unique tag to the LU owner
assignment on the CICS Service Flow Runtime 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). See Run time processing of non-unique UserIDs using FEPI adapters for more information
on how CICS Service Flow Runtime processing works with non-unique UserIDs.
Note: Userid is the signed-on Userid to the local CICS region as determined by an EXEC CICS ASSIGN command,
see the CICS Application Programming Reference.
The conversation is available for subsequent use by the
owner of the conversation in another task. The CICS Service Flow Runtime Target Interaction
file is written with the last buffer sent or received.
If you use LU assignment processing for non-unique UserIDs and
if you have submitted a request to run in synchronous mode, the abnormal termination
of that request can result in LUs remaining assigned. 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. If the request terminates abnormally in asynchronous mode and you are
using LU assignment processing for non-unique UserIDs, the LUs are left for
compensation.
Also, as a normal end of day processing strategy, the service requestor
could invoke a modeled flow as a process to locate, logoff and release any
assigned LUs.