These installation instructions assume you have available FOCUS documentation.
There are three ways to access MSO: from CICS terminals, from TSO sessions, and directly from VTAM. Depending upon which of the access methods that are to be installed, not all installation steps need to be performed.
The installation steps include:
The following table summarizes the data sets and files that are used by MSO:
|
DDName |
DSName |
Purpose |
|
|
MSO JCL |
JCL for the MSO address space. |
|
|
CICS JCL |
JCL for the CICS address space. |
|
|
FOCCTL.DATA |
Contains FOCUS sample JCL, zaps, assembly and link-edit jobs. |
|
|
MSO.DATA |
Contains MSO sample JCL, zaps, assembly and link-edit jobs, and source code for modules that are locally customizable. |
|
|
MSO.LOAD |
Contains the MSO CICS programs. |
|
STEPLIB |
FOCLIB.LOAD Other load libraries |
Contains FOCUS and MSO product code. Contain other required product code. |
|
USERLIB |
FUSELIB.LOAD Other load libraries |
Contains FUSELIB subroutine library. Contain other required product code. |
|
ERRORS |
ERRORS.DATA |
Contains all FOCUS error message text and explanations. |
|
FOCMSO |
|
MSO Configuration File. |
|
FOCCONS |
|
MSO Console Configuration File. |
|
MSGET MSPUT |
Communication Data sets |
Data sets used by MSO for inter-address-space communications. One pair per MSO address space is needed. Used for CICS and TSO access, and the MSOKILL program, in conjunction with the IBI MVS Subsystem. |
|
MSOPROF |
|
Profile library. |
|
MSOPRINT |
SYSOUT |
MSO log file. |
|
STDOUT |
|
MSO Console communications traces. |
|
IBISNAP |
SYSOUT |
IBI Snapshot Facility dumps. |
| Information Builders |