In an Adapter service of the single connector - nonpersistent pattern, the CICS® Service Flow Runtime Link3270 server adapter business state data is stored, retrieved and deleted in a multiple item CICS temporary storage queue (TSQ).
See Deployment patterns for detailed information on runtime processing of Adapter services of the single connector - nonpersistent deployment pattern.
The Link3270 server adapter business state data is mapped by copybook DFHMAL2C in the library hqual.SCIZMAC. There is one TSQ with at most two items for each allocated Link3270 bridge facility. There may not be a TSQ written to store facility business state data if Link3270 server adapter processing does not require it.
See Link3270 node properties for information on the deallocate facility indicator, MP-BR-DEALLOCATE-IND, and other Link3270 server adapter properties.
The TSQ is used to manage the business state data of facilities and ownership of facilities left allocated. Normally, the TSQ is used to store the last bridge vector received (max. 32000 bytes ADS , text, or 3270 datastream data) from the defined target CICS application transaction as modeled in the service flow. The vector data is used in subsequent Link3270 server adapter processing to determine the allocated facility business state, for example, the last CICS transaction run, the last BMS SEND MAP Application Data Structure (ADS), the last BMS mapset and map names and so forth.
If when Link3270 server adapter processing is complete the Link3270 bridge facility is left allocated with it's associated facility business state data stored in the facility business state TSQ, the Link3270 facility state token is returned to the service requestor/client in the outbound reply message in the DFHMAH header structure field, DFHMAH-STATETOKEN, for use in subsequent request processing if desired. See DFHMAH header structure for further information on the meaning and use of DFHMAH header structure field, DFHMAH-STATETOKEN.
If a Link3270 facility state token is left blank in the request message header structure, DFHMAH, and a Link3270 server adapter is invoked, a new Link3270 facility is allocated and used in Link3270 server adapter processing.
As stated, an allocated Link3270 facility may be de-allocated and it's associated facility business state data deleted when Link3270 server adapter processing is complete based upon the setting of the deallocate facility indicator, MP-BR-DEALLOCATE-IND, for that Link3270 server adapter and the execution completion status of that Link3270 server adapter.
In addition, Link3270 facilities and their associated business state data may be de-allocated and deleted, respectively, by the system cleanup tasks. See Facility state cleanup processing in the CICS Service Flow Runtime for a description of how this cleanup is performed.
Also, as a normal end of day processing strategy, the service requestor could invoke a modeled flow to locate any allocated facility, deallocate the facility and delete it's associated facility business state data. This flow would need to be run for each allocated Link3270 facility state token by each service requestor invoking runtime services.