Pre-installation Tasks
This chapter describes how to perform pre-installation tasks.
1. Overview
Perform the following tasks before installing OpenFrame/OSI.
-
Checking system requirements
-
Verifying available disk space
-
Verifying installation of OpenFrame product lines
-
Creating an installation properties file
2. Checking System Requirements
OSI can only be installed on UNIX or Linux systems. Check the following system requirements to install OSI.
Requirements | |
---|---|
Platform |
Solaris 11(SunOS 5.11) (32bit, 64bit) |
Linux x86 2.6 (32bit, 64bit) |
|
Linux ia64 2.6 (32bit, 64bit) |
|
Hardware |
At least 5GB hard disk space |
At least 8GB hard disk space |
|
Database |
Tibero 6 FS07 |
Compiler |
MF-COBOL compiler, NET-COBOL compiler, OpenFrame COBOL compiler |
OpenFrame PL/I compiler |
|
OpenFrame ASM compiler |
|
OpenFrame Product Family |
OpenFrame/Base 7.1, OpenFrame/Batch 7.1, OpenFrame/HiDB 7.2 |
3. Verifying Available Disk Space
Because at least 200 MB of free disk space is required by OSI, the amount of free disk space must be checked before installation. For more information about hardware requirements, refer to Checking System Requirements.
To verify that there is enough free space, execute the df command at the UNIX prompt.
The following example shows how to use the df command to check the free and used space of a disk that contains a specified directory. To display the results in units of KB, use the -k option. This example was done on an HP machine using the HP-UX operating system.
$ df -k /home
The following is the result of the previous example.
/home (/dev/vg01/lv00) : 30425199 total allocated KB 4422401 free allocated KB 26002798 used allocated KB 85 % allocation used
It shows that the /home directory is located on the /dev/vg01/lv00 disk, and 26,002,798 KB is used out of a capacity of 30,425,199 KB. 4,422,401 KB is free, which means that 85% of the capacity is used.
4. Verifying Installation of OpenFrame Product Lines
OSI products are affected by other independent OpenFrame products. To install and use OSI, OpenFrame/Base, OpenFrame/Batch, and Tibero/HiDB products should have been installed in order.
The following example shows how to verify the installed OpenFrame products using the ofversion tool.
$ ofversion ofversion version 7.1.0(0) obuild@tplinux64:ofsrc71/base(#1) 2021-03-17 23:07:27 Print OpenFrame Version Information OpenFrame Solution is Composed of - OpenFrame/Base 7.1 64bit - OpenFrame/Batch MVS 7.1 64bit - OpenFrame/TACF 7.1 64bit - OpenFrame/HiDB 7.2 64bit Tibero
For more information about installing and verifying the OpenFrame product lines, refer to each product’s installation guide. |
5. Installation Properties File
Set all the properties for OSI installation to a file. The installer automatically reads and uses the set data during the installation.
The following describes properties to set in the properties file. You can check the sample file in Sample Installation Properties File.
You must create an installation properties file as a text file and can name it any name that Unix systems allow. It is recommended to create the file by referring to the sample file provided along with the installer. |
5.1. OpenFrame Directory
Set the OSI installation directory.
The following is the item for the OpenFrame home directory.
OPENFRAME_HOME=<path>
Item | Description |
---|---|
OPENFRAME_HOME |
Absolute path to the OpenFrame home directory where OpenFrame/Base was installed and OpenFrame/OSI will be installed. |
The following sets the OpenFrame home directory to /home/oframe/OpenFrame.
OPENFRAME_HOME=/home/oframe/OpenFrame
5.2. Storage Devices
Set storage devices used in OpenFrame.
The following are the items for storage devices.
SYSTEM_TABLESPACE<tablespace> DEFAULT_VOLSER=<volume> DEFAULT_VOLPATH=<path> COMPILER_TYPE<complier>
Item | Description |
---|---|
SYSTEM_TABLESPACE |
Name of the table space to manage system tables. The table space must be created before the installation. |
DEFAULT_VOLSER |
Name of the default volume used in OpenFrame. This name must be the same as the volume name created during the OpenFrame/Base installation. |
DEFAULT_VOLPATH |
DActual path of the volume set in DEFAULT_VOLSER. |
COMPILER_TYPE |
OIVP sample source for compiling when OSI is installed |
The following sets storage devices.
SYSTEM_TABLESPACE=OFM_REPOSITORY DEFAULT_VOLSER=DEFVOL DEFAULT_VOLPATH=$OPENFRAME_HOME/volume_DEFVOL COMPILER_TYPE=OFCOBOL
5.3. VTAM
Set VTAM (TN3270 gateway).
The following are the items for VTAM.
VTAM_PORT=<number>
Item | Description |
---|---|
VTAM_PORT |
Decimal port number used in VTAM. |
|
The following sets VTAM.
VTAM_GW_PORT=8401
5.4. Default Region
Set the default region (IMSID: IMSA) created by the installer.
The following are the items for the default region.
IMSA_JCLLIB=<pds_name> IMSA_MODBLKS=<dataset_name> IMSA_IMSACB=<dataset_name> IMSA_DFSRELB=<dataset_name> IMSA_FORMAT=<dataset_name> IMSA_STEPLIB=<dataset_name> IMSA_MQLIB=<datase_namet>
Item | Description |
---|---|
IMSA_JCLLIB |
Name of PDS that stores JCL. |
IMSA_MODBLKS |
Name of the staging library data set that stores settings of supported resources. |
IMSA_IMSACB |
Name of the staging library data set that stores ACB. Set to VALUE item of ACBLIB_NAME key under the IMS_DEFAULT section of the ims subject in the OpenFrame configuration. |
IMSA_DFSRELB |
Name of the library data set that stores MDA information used to dynamically use data sets. Set to VALUE item of RESLIB_NAME key under the IMS_DEFAULT section of the ims subject in the OpenFrame configuration. |
IMSA_FORMAT |
Name of the staging library data set that stores MFS. |
IMSA_STEPLIB |
Name of the data set that stores shared object type execution modules of developed applications. |
IMSA_MQLIB |
Name of the data set for Message Queue (MQ). |
For more information about OpenFrame configuration, refer to OpenFrame Configuration Guide. |
The following set the default region.
IMSA_JCLLIB=SYS1.JCLLIB IMSA_MODBLKS=OSI.IMSA.DEFLIB IMSA_IMSACB=IMS.ACBLIB IMSA_DFSRELB=IMS.RESLIB IMSA_FORMAT=OSI.IMSA.MFSLIB IMSA_STEPLIB=OSI.IMSA.STEPLIB IMSA_MQLIB=OSI.IMSA.MQLIB
5.5. Others
Set the OSI license path.
The following is the items for the license.
OSI_LICENSE_PATH=<path>
Item | Description |
---|---|
OSI_LICENSE_PATH |
Path to the OSI license file. It is copied to the ${OPENFRAME_HOME}/license directory during the installation. |
The following set the OpenFrame/OSI license path.
OSI_LICENSE_PATH=/home/oframe1/license