MSO/CICS Installation Steps

MSO Setup

The following steps are used to prepare the MSO address space for communications with one or more CICS address spaces. They should be performed once for each MSO address space that will be accessed from CICS.

• As mentioned above, the IBI Subsystem must be installed in the MSO address space before the MSO/CICS installation is performed. Ensure that this has been tested before continuing. (The best test is to set up access to MSO from TSO and to confirm that this works properly.)

• Add the MSGET and MSPUT ddnames to the MSO JCL. Note that the ddnames are always MSGET and MSPUT in the MSO JCL regardless of the ddnames that are used in the CICS JCL. There is only one pair of communication data sets per MSO address space; it is shared by all CICS and TSO address spaces that are communicating with that MSO. An example of these DD cards is:

//MSGET DD DSNAME=PROD.MSO.MSOGET,DISP=SHR

//MSPUT DD DSNAME=PROD.MSO.MSOPUT,DISP=SHR

• Update the MSO configuration file:

1. Ensure SERVICE=FOCUS is specified. Only MSO/VTAM users may connect to a service with a name other than FOCUS; MSO/CICS (and MSO/TSO) users are restricted to SERVICE=FOCUS.
2. If desired, code the TRANSID parameter to cause the MSO transaction to start another transaction when it completes. This specification overrides the default that is set by re-assembling CMSOTABL.
3. If desired, code the CICSBREAK parameter. This parameter activates the Session Termination Key, which replaces the old CICS Attention Key feature.

CICS Setup

Perform these steps once for each CICS address space to be connected to an MSO address space:

• Choose transaction ids for the two MSO transactions. This manual uses the name MSO for the transaction used to access MSO, and MSMT for the utility transaction used to terminate MSO operations. Any valid transaction ids may be used, but keep in mind that the name of the MSO transaction will affect the ddnames used in the CICS JCL for the communication data sets.

• Change the CICS JCL:

1. Include the data set MSO.LOAD to the DFHRPL concatenation. If required by your version of MVS, ensure the blocksizes of the data sets in the concatenation are in descending order, or override them if necessary.
2. Add a DD statement for FOCLIB, pointing to FOCLIB.LOAD.
3. Add a DD statement for ERRORS, pointing to ERRORS.DATA.
4. Add the MSOGET/MSOPUT ddnames. These are the communications data sets created above. The actual ddnames used should be the transaction id used for the MSO transaction, with GET and PUT appended to the name. For example, if you use transaction id FOC, you would use ddnames FOCGET and FOCPUT.
5. If using a version of CICS that uses the OSCOR parameter, ensure that it is set to a large enough value. MSO needs at least 165K above current needs.

Thus, the following might be added to the CICS JCL:

//DFHRPL  DD DSN=prefix.MSO.LOAD,DISP=SHR,DCB=BLKSIZE=23476

//FOCLIB  DD DSN=prefix.FOCLIB.LOAD,DISP=SHR

//ERRORS  DD DSN=prefix.ERRORS.DATA,DISP=SHR

//MSOPUT  DD DSN=prefix.MSO.MSOPUT,DISP=SHR

//MSOGET  DD DSN=prefix.MSO.MSOGET,DISP=SHR

Do not put these DD statements into the CICS FCT. These files are not going to be opened by CICS, but rather are used via MVS facilities.

• Add the following programs to the PPT:

• MSOCICS - This is the MSO transaction, run by end users.
• MSOUTIL - This is the MSMT utility transaction, currently used for stopping MSO communications links.
• MSOPLT - This program is run from the PLT to shut down all active MSO communications at CICS termination.
• MSOATTN - This program is part of the Attention Key support under MRO.
• MSOTOR - This program is part of the Attention Key support under MRO.
• MSOEXIT - This program is used as the XZCATT exit if Attention Key support is needed.

The following RDO (Resource Definition Online) definitions are compatible with the storage protection attribute STGPROT=YES in the DFHSIT (System Initialization Table for the MSO region):

• Information Builders-supplied PROGRAMS that are defined to CICS should specify EXECKEY(CICS).
• The MSO/CICS TRANSACTION definition should specify TASKDATAKEY(USER).

All of the above programs should have LANG(ASSEMBLER) specified.

While DTIMOUT is valid for program MSOCICS, you should consider using the TIMEOUT parameter in the MSO configuration file instead, as it provides for an orderly shutdown of the FOCUS session when the session times out.

The DTIMOUT parameter may not be specified for program MSOTOR.

• Add the following transactions to the PCT:

Transid	Program
MSO	MSOCICS
MSMT	MSOUTIL
MTOR	MSOTOR (MRO only)
MSAT	MSOATTN (MRO only)

• Set up transaction security as required:

1. MSO must be run by all users.
2. MSMT is run by personnel authorized to stop MSO communications.
3. MTOR is started at CICS startup.
4. MSAT is started by MTOR when required.
• Link the IBM Command-Level stubs into the programs in MSO.LOAD. Sample JCL is provided in MSO.DATA(MSLNKSTB).

• Change the PLT for proper operation at CICS startup and shutdown. Details on PLT processing are given in the Operations section below.

1. If Attention Key support is needed, enable MSOEXIT (an XZCATT exit) at startup.
2. Run MSOPLT at shutdown.
• If Attention Key support is needed, update, assemble and link-edit MSOEXIT. You must update the table at the end of this exit with the transaction ids that you will be using for MSO. Source code is provided in MSO.DATA(MSOEXIT), and sample JCL is provided in MSO.DATA(MSXZCATJ).

• Set up the MSCXUID exit if required. The MSCXUID exit is used to supply a CICS userid when ASSIGN USERID is not supported, or when it is desired to use a different userid than the one returned by ASSIGN USERID. This exit is described in MSO/CICS Technical Description.

• Set up the MSCXWRT exit if required. The MSCXWRT exit allows customization or elimination of the MSO13206 message when the MSO transaction completes normally; it also suppresses the next-transaction processing. This exit is described in MSO/CICS Technical Description.

• If you need to modify the defaults set in CMSOTABL, update and re-assemble it. Source and JCL for this are provided in members CMSOTABL and MSOTABLJ in MSO.DATA. You may change the user auxtrace number, the default value for TRANSID, and the flag to suppress the session initialization message.

CICS Setup for MRO

The following steps are only required when Attention key support is required in an MRO environment. Except as described below, all MSO transactions and programs run in the AOR and are fully compatible with MRO.

1. Define transaction MTOR to run in the TOR.
2. Ensure that exit XZCATT (program MSOEXIT) is enabled in the TOR at CICS startup.
3. Start transaction MTOR from the PCT after XZCATT is enabled.
4. Ensure that transaction MSAT, which runs in the AOR, can be started by transaction MTOR in the TOR.

Multiple Address Spaces

When connecting multiple CICS address spaces to a single MSO address space, simply perform the installation procedure once in the MSO address space (adding a single pair of MSGET and MSPUT data sets), and once per CICS address space (adding the MSO transaction and xxxxGET and xxxxPUT data sets under any valid names, which may be different in each CICS address space).

When connecting to multiple MSO address spaces from a single CICS address space, install an extra instance of the MSO transaction (using program MSOCICS) and an extra pair of communication data sets (appending GET" and PUT to the transaction id to create the ddnames) for each MSO address space to be used. For example, assuming transactions MSO and MFOC were both installed pointing to program MSOCICS, you would have the following allocations in the JCL for CICS:

//MSOPUT  DD DSN=prefix.MSO.MSOPUT,DISP=SHR

//MSOGET  DD DSN=prefix.MSO.MSOGET,DISP=SHR

//MFOCPUT DD DSN=prefix.MSO.MFOCPUT,DISP=SHR

//MFOCGET DD DSN=prefix.MSO.MFOCGET,DISP=SHR

The first MSO would have the following allocation for its communication data sets:

//MSPUT   DD DSN=prefix.MSO.MSPUT,DISP=SHR

//MSGET   DD DSN=prefix.MSO.MSGET,DISP=SHR

The second MSO would have its communication data sets allocated as follows:

//MSPUT DD DSN=prefix.MSO.MFOCPUT,DISP=SHR

//MSGET DD DSN=prefix.MSO.MFOCGET,DISP=SHR