|
CICS transactions and MSO FOCEXECs may now communicate directly with each other in a synchronous mode. A CICS pseudo conversational transaction may start an MSO session on behalf of a CICS user. Once a cooperative processing session is started, data can be handed back and forth between FOCEXECs and CICS transactions in packets containing up to 256 bytes. |
Topics: MSO FOCEXEC Cooperative Processing Service |
Additionally, a suspend function is available. When this is invoked in MSO, the CICS transaction is given control. This allows a "hot" MSO to be available to the CICS user. The CICS user may go in and out of MSO without terminating their MSO session.
These new facilities allow CICS transactions to get and retrieve data from the MSO region and vice versa. The FOCEXEC interaction is implemented in MSO via a FUSELIB routine, CICSCOMM.
The CICS transaction functions are implemented by linking the installation's transaction module with the Information Builders supplied module, CMSOAPI. CMSOAPI provides five function calls that supply the MSO/CICS communications.
Also, a reconnect facility is available for cooperative processing sessions and for standard MSO connections from CICS. This allows the reconnection of an MSO session when the logical connection from a CICS terminal is lost.
The figure below illustrates the relationship between a FOCEXEC running in the MSO address space and user programs running in the CICS address space when a cooperative session has been established.
| Information Builders |