Unload the MSO data sets from the tape. Two data sets are required for MSO in addition to the data sets required for FOCUS:
If you are not using Internal APF Authorization, copy all of the modules in FUSELIB.LOAD into FOCLIB.LOAD. This removes the need for FUSELIB.LOAD to be authorized.
With Internal APF Authorization, FUSELIB.LOAD may be allocated to ddname USERLIB, and does not need to be authorized beforehand.
If access to MSO from CICS or TSO is required, or MSOKILL will be used, create the communications data sets MSPUT and MSGET. These data sets are used in conjunction with the IBI MVS Subsystem.
These data sets should have LRECL=16, RECFM=F, BLKSIZE=16, and should be one track each. All MSO users must have read access to them; the MSO job itself will need read/write access.
Module MSDEB in FOCLIB.LOAD is a debugging tool to be used with instruction from Information Builders support personnel. This module should be protected from unauthorized execute access by your site's security package. Alternatively, it can be renamed to prevent users from accessing it.
Create the MSOPROF profile partitioned data set. This file contains the entries used by MSO for profile support. The file should have LRECL=80, RECFM=FB, BLKSIZE=1600, with DIR=30. Twenty tracks should be adequate space for this file to start.
Member PROFILE of MSOPROF should contain any FOCUS commands to be executed by all MSO users at logon time.
If you copied part or the entire FOCPARM member of ERRORS.DATA into member PROFILE in Release 6.8, you should delete those commands now. FOCPARM processing has changed, removing the necessity of duplicating any of it in MSO's profile processing.
Details on profile processing may be found in MSO Features and Components.
| Information Builders |