MSO/CICS Operations

MSO/CICS is designed to run with little or no operator intervention. All programs needed to establish and destroy the environment can be run from the PLT at CICS startup and shutdown. These programs may also be run manually, if desired.

In this section:

MSO/CICS Startup

Reusable MSO/CICS Control Blocks

Startup for Attention Key Support

MSMT - MSO Master Terminal

CICS Shutdown

MSO/CICS Startup

MSO/CICS is started when the first user runs the MSO transaction. This causes the communication tasks to start and establishes communication with the MSO address space that corresponds to the specified transaction. (The first user to run the MSO transaction will encounter a slightly longer wait as communication is established.)

Reusable MSO/CICS Control Blocks

MSO provides a facility to re-use orphaned control blocks. If you are timed out or disconnected the control block you were using goes into a pool. If you then come back you will get your old control block as long as it's still available. If the system runs out of control blocks it will start re-using the oldest orphaned control blocks. When you time out or if your session was cancelled, restarting your MSO connection after your control block was reissued, you will receive the following message:

FOCUS SESSION ENDED: ERROR UNKNOWN OR NO LONGER AVAILABLE

Top of page

Startup for Attention Key Support

If you are using the optional Attention key support, you must explicitly enable the XZCATT exit. In addition, if Attention support is desired in an MRO environment, the MTOR transaction must be run. Both of these steps must be performed before the first use of the MSO transaction in order for the Attention key support to be active.

The XZCATT exit must be enabled in each CICS region that contains terminals that will run MSO. Under MRO, it must be enabled in each TOR that will access MSO. It is not necessary to enable it in the AOR. The following command may be used to enable XZCATT:

CECI ENABLE EXIT(XZCATT) PROGRAM(MSOEXIT) GALEN(nnn) START

The value for GALEN is calculated by multiplying the maximum number of termids that MSO/CICS will encounter by 8, and then adding 8 bytes for overhead. It is recommended that you use double the number of anticipated termids, to allow for growth. There is no indication of overflow, and the Attention key is ignored from termids not in the table.

After XZCATT is enabled, run the MTOR transaction. MTOR is a long-running transaction (it runs in a loop), and under most circumstances should not be run from a terminal. One way to start it is with the command:

CECI START TRANSID(MTOR)

Top of page

MSMT - MSO Master Terminal

The MSMT transaction can be used to stop communications with one or more MSO address spaces from a CICS address space. To run MSMT, issue the command:

MSMT STOP(transid)

where:

transid
Is the transaction being used to stop communications between an MSO address space and a CICS address space.
MSMT STOP(tran1,tran2,...)

where:

tran1, tran2
Are the transactions being used to stop communications between multiple MSO address spaces and a CICS address space.

Note that MSMT doesn't delete the MTOR transaction, which can be stopped in the same manner as any other CICS transaction.


Top of page

CICS Shutdown

When CICS is shut down, the program MSOPLT should be invoked from the PLTSD list. MSOPLT performs the same processing as MSMT, stopping communication with all attached MSO address spaces and deleting the MVS subtasks that perform the communication.


Information Builders