OSI/MHS Configuration and Management Manual

Installing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
4-21
Exiting From a Successful Installation
the MS PDU stores. If your answer is no, installation ends. You must correct the file
names in the installation file, then run the installation program again.
If an error occurs, an error message is displayed and the installation stops. Check the
output location for the complete SQLCI and FUP output.
23 Through 26—Creating PDU Store Databases.
Steps 23 through 26 on the installation menu create PDU stores (databases) for
OSI/MHS groups as follows:
Step 23 Create MR PDU Store Databases
Step 24 Create RS PDU Store Databases
Step 25 Create GI PDU Store Databases
Step 26 Create LO PDU Store Databases
When you select one of these steps, the installation program displays the appropriate
data file names and log file names from the installation file, and asks you to confirm
them. If your answer is yes, the installation program creates the PDU stores. If your
answer is no, installation ends. You must correct the values in the installation file, then
run the installation program again.
The keyword OSIMHS_FILE_SECURITY sets the security for each of these PDU
databases.
27) Create Sample Configuration File.
This step creates a sample configuration file, or “skeleton” file, named MHSSKEL.
The output from this step is an SCF OBEY file or infile containing standard SCF
commands. See Section 5, Configuring Your OSI/MHS Subsystem, for information
about configuration.
Exiting From a Successful Installation
A successful installation procedure ends with the following message.
MS PDU store(s) specified in the installation file
$myvol.osimhs.install2:
Data file Log file
--------- --------
#1 $myvol.mh1msdb.pdums1 $myvol.mh1msdb.logms1
#2 $myvol.mh1msdb.pdums2 $myvol.mh1msdb.logms2
#3 $myvol.mh1msdb.pdums3 $myvol.mh1msdb.logms3
#4 $myvol.mh1msdb.pdums4 $myvol.mh1msdb.logms4
Are these the correct values for the MS PDU store(s)? [y]
Exiting mhsinst