Pre-installation Tasks

This chapter describes how to perform pre-installation tasks, such as verifying hard disk space and writing an installation properties file.

1. Overview

The following must be checked before installation.

Verification of system requirements
Whether available disk space is sufficient
Whether other OpenFrame products are properly installed
Whether an installation properties file is created

2. System Requirements

System requirements for installing OSC are as follows:

	Requirements
Platform	Solaris 11 (SunOS 5.11) or later (32-bit, 64-bit)
Linux x86 2.6 or later (32-bit, 64-bit)
Linux ia64 2.6 or later (32-bit, 64-bit)
Hardware	More than 5GB hard disk space
More than 8GB RAM
Database	Tibero 6 FixSet07
Compiler	MF-COBOL, NET-COBOL or OpenFrame COBOL compiler
OpenFrame PL/I compiler
OpenFrame ASM compiler
OpenFrame Product Line	OpenFrame/Base 7.1

Requirements

Platform

Solaris 11 (SunOS 5.11) or later (32-bit, 64-bit)

Linux x86 2.6 or later (32-bit, 64-bit)

Linux ia64 2.6 or later (32-bit, 64-bit)

Hardware

More than 5GB hard disk space

More than 8GB RAM

Database

Tibero 6 FixSet07

Compiler

MF-COBOL, NET-COBOL or OpenFrame COBOL compiler

OpenFrame PL/I compiler

OpenFrame ASM compiler

OpenFrame Product Line

OpenFrame/Base 7.1

Contact TmaxSoft Technical Support for IBM or HP-UX platform support.

3. Verifying Available Disk Space

Check the amount of free disk space in Unix before installing OSC. For more information about hardware requirements, refer to System Requirements.

To verify that there is enough free space, execute the df command at the UNIX/Linux prompt.

The following example uses the df command to check the amount of free and used disk space on a Linux system. To display the results in units of KB, use the -k option.

tmax@oframe:/home/oframe>df -k /home

The command result is as follows:

Filesystem               1K-blocks     Used         Available   Use%     Mounted on
/dev/mapper/centos-home  30425199      26002798     4422401     85%      /home

It shows that the /home directory is located on the /dev/mapper/centos-home 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 the Installation of the Other OpenFrame Products

In order to run OSC, other products in the OpenFrame product suite must be properly installed.

Required Products

OpenFrame/Base must have been installed in order to install or use OSC. After installing OSC, OpenFrame GW must be installed in order to view transaction activities.

For more information about the installation, refer to OpenFrame Base Installation Guide.

Optional Products

The optional products that can be installed according to users' needs are OpenFrame/Batch, OpenFrame/OSI, and OpenFrame/TACF. OSC must be last installed among the OpenFrame products as the way to install the OSC installer may differ according to the product to be installed with OSC. However, OpenFrame Manager, a GUI tool, must be installed after verifying that all OpenFrame products including OSC have been properly installed and run.

5. Creating an Installation Properties File

When the installer is executed after all properties referenced to install OSC are written in a file, then the installer will read the values defined in the properties file and proceed with the installation based on those values.

This section explains the items that you must define in the OSC installation properties file. Sample file for an installation properties file can be checked in Sample Installation Properties File.

You can specify any name, allowed in the Unix system, for the installation properties file, without restriction. The file must be a general text file. It is recommended to make a properties file by referring to the sample configuration file provided along with the installer.

5.1. Setting the Compiler

Before installing OSC, specify a compiler that supports the installation requirements.

The following are the options for choosing the compiler type.

COBOL=[MFCOBOL|OFCOBOL|NO]
PLI=[YES|NO]

Item	Description
COBOL	Specifies whether to use COBOL with the OSC to be installed and which compiler to use. Depending on the specified value, the $OPENFRAME_HOME/lib/libcics.so module links to an appropriate compiler. Since all compiler type modules are provided, it can be changed after installation. MFCOBOL OFCOBOL NO (if COBOL is not used)
PLI	Option to use PL/I.

Item

Description

COBOL

Specifies whether to use COBOL with the OSC to be installed and which compiler to use. Depending on the specified value, the $OPENFRAME_HOME/lib/libcics.so module links to an appropriate compiler. Since all compiler type modules are provided, it can be changed after installation.

MFCOBOL
OFCOBOL
NO (if COBOL is not used)

PLI

Option to use PL/I.

The following example shows how to enable the OFCOBOL compiler and disable PL/I.

COBOL=OFCOBOL
PLI=NO

5.2. Setting OpenFrame’s Home Directory

Set a directory in which OSC is installed, and enter the absolute path in which OpenFrame/Base is installed.

The following is the item required to set OpenFrame’s home directory.

OPENFRAME_HOME=<path>

Item	Description
OPENFRAME_HOME	Specifies Unix directory or file path where OSC will be installed.

Item

Description

OPENFRAME_HOME

Specifies Unix directory or file path where OSC will be installed.

The following example illustrates how to set OpenFrame’s home directory to /home/oframe/OpenFrame.

OPENFRAME_HOME=/home/oframe/OpenFrame

5.3. Setting Tmax Environment Variables

Set environment variables for using Tmax in an OpenFrame engine. The Tmax-associated items must be the same as those specified when installing OpenFrame/Base. Refer to the Tmax configuration file ${TMAXDIR}/config/oframe.m.

The following is an item required to specify Tmax environment variables.

TP_NODE_NAME=<tp_node_name>

Item	Description
TP_NODE_NAME	Specifies a name of the node where OpenFrame will be installed with a character string made of 0~9, A~Z, a~z, @, #, $, or -.

Item

Description

TP_NODE_NAME

Specifies a name of the node where OpenFrame will be installed with a character string made of 0~9, A~Z, a~z, @, #, $, or -.

The following example shows how to configure Tmax environment variables.

TP_NODE_NAME=NODE1

5.4. Storage Device Configuration

Specify a volume for a VSAM data set to be used in OpenFrame.

The following is an item to configure the storage device.

DEFAULT_VOLSER=<volser_dataset>

Item	Description
DEFAULT_VOLSER	Specifies the name of the default volume for OpenFrame. The default volume name must be the same as used when installing OpenFrame/Base.

Item

Description

DEFAULT_VOLSER

Specifies the name of the default volume for OpenFrame. The default volume name must be the same as used when installing OpenFrame/Base.

The following example shows how to configure the storage device.

DEFAULT_VOLSER=DEFVOL

5.5. OIVP Configuration

This section describes the items for the OIVP region (OSCOIVP1) that are automatically configured after the OSC installation.

Configure the environment for OIVP, a demo application used to check the installation of OCS.

OSCOIVP1 Region Configuration
OSCOIVP1 Region CPM Configuration
OSCOIVP1 Region TL Server Configuration

For more information about executing OIVP, refer to Installation Verification.
For a further description of each item, refer to OpenFrame OSC Administrator’s Guide.
For more information about OpenFrame configuration, refer to OpenFrame Configuration Guide.

OSCOIVP1 Region Configuration

Configure the basic parameters in OSCOIVP1. All parameters are set to their recommended values during installation. Only parameters that require unique values can be set. Even when multiple regions are used, duplication is not allowed.

OSC_APP_SYS_SHMKEY=<osc_app_sys_shmkey>
OSC_APP_USR_SHMKEY=<osc_app_usr_shmkey>
OSC_APP_TSQ_SHMKEY=<osc_app_tsq_shmkey>
CORE_TDL_SHMKEY=<core_tdl_shmkey>

Item	Description
OSC_APP_SYS_SHMKEY	Specifies a key either in the decimal or hexadecimal format for the shared memory used by the system. Values in hexadecimal format start with "0x". The value is specified to the VALUE of the SYS_SHMKEY key in the GENERAL section, from the osc.{servername} subject under OpenFrame Configuration.
OSC_APP_USR_SHMKEY	Specifies a key either in the decimal or hexadecimal format for the shared memory used by the user. Values in hexadecimal format start with "0x". The value is specified to the VALUE of the USR_SHMKEY key in the GENERAL section, from the osc.{servername} subject under OpenFrame Configuration.
OSC_APP_TSQ_SHMKEY	Specifies a key either in the decimal or hexadecimal format for the shared memory used by the TSQ. Values in hexadecimal format start with "0x". The value is specified to the VALUE of the TSQ_SHMKEY key in the TSQ section, from the osc.{servername} subject under OpenFrame Configuration.
CORE_TDL_SHMKEY	Specifies a key for the shared memory for the TDL module. The value is specified in the TDL configuration file (${OPENFRAME_HOME}/osc/region/OSCOIVP1/tdl/config/tdl.cfg) in the region.

Item

Description

OSC_APP_SYS_SHMKEY

Specifies a key either in the decimal or hexadecimal format for the shared memory used by the system. Values in hexadecimal format start with "0x". The value is specified to the VALUE of the SYS_SHMKEY key in the GENERAL section, from the osc.{servername} subject under OpenFrame Configuration.

OSC_APP_USR_SHMKEY

Specifies a key either in the decimal or hexadecimal format for the shared memory used by the user. Values in hexadecimal format start with "0x". The value is specified to the VALUE of the USR_SHMKEY key in the GENERAL section, from the osc.{servername} subject under OpenFrame Configuration.

OSC_APP_TSQ_SHMKEY

Specifies a key either in the decimal or hexadecimal format for the shared memory used by the TSQ. Values in hexadecimal format start with "0x". The value is specified to the VALUE of the TSQ_SHMKEY key in the TSQ section, from the osc.{servername} subject under OpenFrame Configuration.

CORE_TDL_SHMKEY

Specifies a key for the shared memory for the TDL module. The value is specified in the TDL configuration file (${OPENFRAME_HOME}/osc/region/OSCOIVP1/tdl/config/tdl.cfg) in the region.

The following example shows how to configure the environment variables of OSCOIVP1 Region.

OSC_APP_SYS_SHMKEY=25140
OSC_APP_USR_SHMKEY=21477
OSC_APP_TSQ_SHMKEY=23658
CORE_TDL_SHMKEY=35211

OSCOIVP1 Region CPM Configuration

Configure the CPM parameters used in OSCOIVP1.

Each value is specified in the REGION_CCSID and 3270_CCSID keys respectively, in the CPM section of the osc.{servername} subject under OpenFrame Configuration.

OSC_APP_CPM_REGION_CCSID=<osc_app_cpm_region_ccsid>
OSC_APP_CPM_3270_CCSID=<osc_app_cpm_3270_ccsid>,[<osc_app_cpm_3270_ccsid>]

Item	Description
OSC_APP_CPM_REGION_CCSID	Specifies a decimal value for the CCSID used in the region.
OSC_APP_CPM_3270_CCSID	Specifies a decimal value for the CCSID for the TN3270 gateway. If a 1-byte character code page and a 2-byte character code page are used together, then up to two CCSIDs can be specified.

Item

Description

OSC_APP_CPM_REGION_CCSID

Specifies a decimal value for the CCSID used in the region.

OSC_APP_CPM_3270_CCSID

Specifies a decimal value for the CCSID for the TN3270 gateway. If a 1-byte character code page and a 2-byte character code page are used together, then up to two CCSIDs can be specified.

The following example shows how to set the OSCOIVP1 language as English.

OSC_APP_CPM_REGION_CCSID=437
OSC_APP_CPM_3270_CCSID=37

OSCOIVP1 Region TL Server Configuration

Specify TDQ log server parameters for the region.

Each value is specified to the TDQ_LOG_ADDRESS key in the TDQ section of the osc.{servername} subject and to the PORT key in the OSCTLSVR section of the osc.{osctlsvrname} subject, respectively.

OSC_TL_OSCTLSVR_PORT=<port>

Item	Description
OSC_TL_OSCTLSVR_PORT	Specifies a decimal value for the port for OSCTLSVR.

Item

Description

OSC_TL_OSCTLSVR_PORT

Specifies a decimal value for the port for OSCTLSVR.

The following example shows how to configure the TDQ log server for OSCOIVP1 .

OSC_TL_OSCTLSVR_PORT=8696

5.6. VTAM Port Setting

Set the port number used by VTAM included in the OpenFrame engine to the VTAM_PORT item. The item value must be identical to the value of lu.port in the OpenFrame GW environment. Refer to the OpenFrame GW configuration file, ${OFGW_HOME}/ofgwconf/ofgw.properties. The item is stored in a database table and can be checked through the vtamdump tool.

For more information about the vtamdump tool, refer to OpenFrame Tool Reference Guide.

The following is an item required to configure a VTAM port.

VTAM_PORT=<port>

Item	Description
VTAM_PORT	Specifies a decimal port number used by VTAM.

Item

Description

VTAM_PORT

Specifies a decimal port number used by VTAM.

The following example shows a VTAM port that can be checked through vtamdump.

BEGINVTAM
 PORT 5556
 LUGROUP LUGRP1 TESTTERM ENDLUGROUP
 LUGROUP LUGRP2 TESTTRM0..TESTTRM9..FFFFFFFN ENDLUGROUP
 IPGROUP IPGRP1 1.1.1.1..100.100.100.100 ENDIPGROUP
 IPGROUP IPGRP2 100.100.100.101..255.255.255.255 ENDIPGROUP
 LUMAP LUGRP1 IPGRP1
 LUMAP LUGRP2 IPGRP2
ENDVTAM