|
The installation procedure assumes that all of MSO has been installed except for the CICS feature. If possible, you should test the MSO installation with VTAM or TSO access before starting the CICS portion of the installation. We strongly recommend installing MSO/TSO access for diagnostic purposes, even if it is not otherwise needed. |
In this section: |
The installation procedure also assumes that the IBI Subsystem has been installed to provide inter-address-space communications. This should be tested before attempting to use it with MSO/CICS, ideally by installing and running MSO/TSO.
Any MVS and CICS releases supported by IBM are supported for the MSO/CICS Interface, although running CICS Version 3 or later provides enhanced trace support. Information Builders currently supports any release of OS/390 currently supported by IBM, and CICS 4.1 or higher.
Both FOCUS and MSO must be installed from the same tape. No mixing of releases is allowable.
All three MSO access methods -- VTAM, CICS, and TSO -- can be used concurrently in the same MSO address space.
Before starting the installation, you should decide:
How many MSO address spaces each CICS needs to communicate with. You will need a separate transaction id and a separate pair of communication data sets for each MSO address space.
How many CICS address spaces will be running MSO/CICS. You will need to repeat the installation procedure for each CICS.
If you will be using MRO. Some of the MSO/CICS code must run in the TOR, although most of it runs in the AOR.
If you will be using the Attention Key support. This allows users to interrupt a running FOCUS command, and optionally end the command or the entire FOCUS session.
If you will be using the Session Termination Key. This allows a user to end a FOCUS session by pressing a PA or PF key, and is provided for compatibility with previous releases.
Whether or not you need to start another transaction upon exiting from FOCUS. You can specify this for all MSO address spaces, by updating and reassembling a table, or in individual MSO address spaces, by specifying it in the configuration file. You may choose, instead, to run a user exit when the MSO transaction ends, which also allows suppression of the session termination message.
If ASSIGN USERID functions properly at your site, or if you need to supply the proper userid through a user exit.
If you want to automate startup and shutdown through the PLT, or if you want to manually start and stop MSO/CICS operation.
Please note that all Information Builders-supplied data sets must come from the same tape. It is not permissible to mix data sets from different releases of FOCUS. In addition, any sample jobs, such as table updates, zaps, assemblies, and link-edits, should be taken from the current tape. These samples change significantly from release to release.
In addition, you should review your MSO JCL and configuration file against the current samples and documentation to confirm their continued correctness in the current release.
|
File |
Description |
|
FOCLIB.LOAD |
Contains FOCUS and MSO product code, and MVS subtasks that run in the CICS address space. |
|
MSO.LOAD |
Contains the MSO CICS programs: MSOCICS, MSOUTIL, MSOPLT, MSOATTN, and MSOTOR. Also contains the locally assembled MSOEXIT (the XZCATT exit) and any MSO/CICS user exits that are in use. |
|
MSO.DATA |
Contains sample JCL, zaps, assembly and link-edit jobs, and source code for CMSOTABL and MSOEXIT. |
|
ERRORS.DATA |
Contains all FOCUS error message text and explanations. Member CMSO1ERR contains messages issued by MSO/CICS. |
|
MSO Configuration File |
Specified by ddname FOCMSO in MSO JCL; is modified during the MSO/CICS installation. |
|
MSO JCL |
JCL for the MSO address space; is modified during the MSO/CICS installation. |
|
CICS JCL |
JCL for the CICS address space; is modified during the MSO/CICS installation. |
|
Communication data sets |
These data sets are used by MSO for inter-address-space communications. One pair per MSO address space is needed. The pair is shared by all CICS regions that communicate with the MSO address space. DDnames used are MSGET/MSPUT in the MSO address space, and xxxxGET/xxxxPUT in the CICS address space, where "xxxx" is the MSO transaction id. |
Customers have a choice between two versions of SASLIB. For specifics see the OS/390 and MVS Installation Guide. The TRANSIENT version of SASLIB may cause conflicts in versions of SASC when operating in an address space in conjunction with other software using SASC runtime routines.
As a result of this conflict, the following messages may appear on the JESLOG or MVS console
+LSCX048 Most recent C runtime library modules not available
+ Use version 93028C5E ( 5.50C) or later to avoid problems.
Information Builders recommends that all MSO customers use the ALLRES version of SASLIB in all MSO/CICS regions.
Affected release levels are:
MVS release 5.2 and above. This includes OS/390.
FOCUS Version 7.0 and above.
The following user exits have not changed since Version 6.8:
The MSCXUID exit, used to supply a userid when ASSIGN USERID does not function properly or when a different userid is desired.
The MSCXWRT exit, used to override the message issued by MSO at normal session termination and the normal next-transaction processing.
You may interconnect multiple CICS and MSO address spaces. When doing so, ensure that all MSO address spaces, and all MSO programs in the CICS address spaces, are at the exact same release level of MSO and FOCUS. While crossing of releases might work under some circumstances, it is not a supported configuration. There are no restrictions on mixing different releases of CICS, however. Any combination may be used, as long as each release used is supported by MSO.
| Information Builders |