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

Check the following before starting the installation process.

  • System requirement

  • Installation of other OpenFrame product lines

  • Available disk space

  • Properties file for installation

  • License file

2. System Requirements

System requirements for installing Batch are as follows:

Requirement

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 5 GB hard disk space

More than 8 GB 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 about IBM or HP-UX platform support.

3. Verifying Available Disk Space

Because at least 200 MB of free disk space is required by Batch, the amount of free disk space must be checked before installation. 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 prompt.

The following example shows how to use the df command to check the available disk space for the specified directory on the Linux x86 operating system. Use the -h option for easier understanding of the displayed results.

$ df -h /home/oframe

The following is the previous command result.

Filesystem                         Size  Used Avail Use% Mounted on
/dev/mapper/centos_oflinux64-home  144G   49G   96G  34% /home

It shows that the /home/oframe directory is located on the /dev/mapper/centos_oflinux64-home disk, and that 49 KB is used out of 144 GB. 96 GB is free, meaning that 34% of the total capacity is used.

4. Verifying Installation of OpenFrame Product Lines

Batch has a dependency on other independent products. OpenFrame/Base must be first installed before installing and using Batch.

The following example verifies the OpenFrame product line installed 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

Before running the Batch installer, you must first check the available database table storage for the Batch system repository.

  1. Specifying the same SYSTEM_TABLESPACE is recommended.

  2. For information about installation of other OpenFrame product lines, refer to the respective installation guides of each individual product.

5. Creating an Installation Properties File

Batch is installed by executing an installation script, after setting values in the installation properties file. More specifically, when the installer is executed, all properties written in the file are referenced to execute the installation accordingly.

This section describes items that must be configured in the Batch installation properties file. A sample installation properties file can be found in Sample Installation Properties File.

  1. The name of a properties file must be batch.properties. The file must be a standard text file. It is recommended to create a properties file by using the sample properties file, which is provided with the installer.

  2. In the installation properties file, set the option for automatically creating data set to either 'YES’ or ‘NO’.

5.1. Setting OpenFrame Directory

To specify the directory to install OpenFrame, enter the absolute path in which OpenFrame/Base is installed. The directory set here is subsequently used as the OpenFrame home directory in all configuration files.

The following example specifies the OpenFrame home directory.

OPENFRAME_HOME=<path>
Item Description

OPENFRAME_HOME

Unix directory or file path.

The following specifies /home/oframe/OpenFrame as the OpenFrame home directory.

OPENFRAME_HOME=/home/oframe/OpenFrame

5.2. Setting OpenFrame Tablespace

The properties file for Batch installation must contain the information of the tablespace (OFM_REPOSITORY) created during the installation of OpenFrame/Base.

Enter the following command and press <Enter> to view the information of the tablespaces created in the Tibero DBMS.

SQL> ls TS
SQL>

TABLESPACE_NAME
--------------------------------------------------------------------------------
SYSTEM
UNDO
TEMP
USR
SYSSUB
DEFVOL
OFM_REPOSITORY

After verifying the tablespaces list, set the OpenFrame tablespace as the system tablespace to store system information such as job queues, output queues and statistics.

SYSTEM_TABLESPACE=OFM_REPOSITORY

5.3. Setting Storage Devices

Set the default volume name and whether to automatically create tables used in OpenFrame. The default volume name must be identical to the volume name created during OpenFrame/Base installation.

For information about how to create the default volume for the OpenFrame/Base installation, refer to OpenFrame Base Installation Guide.

The following example specifies the default volume name.

DEFAULT_VOLSER=<default_volume>
BATCH_TABLE_CREATE=YES|NO
Item Description

DEFAULT_VOLSER

Specifies the name of a volume used by OpenFrame as the default volume.

BATCH_TABLE_CREATE

Specifies whether to automatically create tables needed for batch jobs during the installation.

  • YES: Automatically creates tables.

  • NO: Does not automatically create tables, meaning that you must manually install after completing the installation. Run the create_tjes script under the ${OPENFRAME_HOME}/scripts directory to manually create tables.

The following example specifies DEFVOL as the default volume name and enables automatic table creation.

DEFAULT_VOLSER=DEFVOL
BATCH_TABLE_CREATE=YES

5.4. Setting Nodes

Specify the name of a node in which batch jobs are processed, and set a list of all nodes if multiple nodes are configured.

The following specifies nodes.

TP_NODE_NAME=<node_name>
TP_NODE_LIST=<node_list>
Item Description

TP_NODE_NAME

Name of the node in which batch jobs are processed. Must be the same as the node name specified in the oframe.m file during Base installation.

TP_NODE_LIST

List of all nodes configuring the OpenFrame system. Each node name is delimited by a semicolon (;).

  • Single node system: Uses the same name as TP_NODE_NAME.

  • Multiple node system: Enumerates all node names in the system.

TP_NODE_LIST is intended for pre-configuration for multi-node system. It does not configure multi-nodes during the installation.

The following sets the node name to NODE1 in a single node system.

TP_NODE_NAME=NODE1
TP_NODE_LIST=NODE1

The following sets the name of the current node to NODE3 in a system that consists of NODE1, NODE2, and NODE3.

TP_NODE_NAME=NODE3
TP_NODE_LIST=NODE1;NODE2;NODE3

5.5. Configuring ODBC Environment

Specify the information for connecting to database by using ODBC.

ODBC_USERNAME= <name> database username
ODBC_PASSWORD= <password> database user password
ODBC_DATABASE= <name> ODBC database data source name(DSN)
TIBERO_CLIENT_PT= <port> tibero client port
Item Description

ODBC_USERNAME

User name to connect to the database with ODBC. Must be the same as the user account of the database in use. Use a text string comprised of alphanumeric and special characters.

ODBC_PASSWORD

User password to connect to the database with ODBC.

ODBC_DATABASE

Database name.

TIBERO_CLIENT_PT

Port number for Tibero client. Use decimal numbers.

The following specifies the database connection information.

ODBC_USERNAME=tibero
ODBC_PASSWORD=tmax
ODBC_DATABASE=oframe3
TIBERO_CLIENT_PT=7780

5.6. Configuring TJES Environment

Configure the environment for Batch jobs.

DEFAULT_JCLLIB_CREATE=YES|NO
DEFAULT_PROCLIB_CREATE=YES|NO
DEFAULT_USERLIB_CREATE=YES|NO
DEFAULT_TEMPLIB_CREATE=YES|NO
Item Description

DEFAULT_JCLLIB_CREATE

Specifies whether to automatically create the default JCLLIB data set during OpenFrame installation.

  • YES: Automatically creates the JCLLIB data set 'SYS1.JCLLIB' during the installation.

  • NO: You must manually install the JCLLIB data set after the installation, by running the create_jcllib.sh script under the ${OPENFRAME_HOME}/scripts directory.

DEFAULT_PROCLIB_CREATE

Specifies whether to automatically create the default PROCLIB data set during OpenFrame installation.

  • YES: Automatically creates the PROCLIB data set 'SYS1.PROCLIB' during the installation.

  • NO: You must manually install the PROCLIB data set after the installation, by running the create_proclib.sh script under the ${OPENFRAME_HOME}/scripts directory.

DEFAULT_USERLIB_CREATE

Specifies whether to automatically create the default USERLIB data set during OpenFrame installation.

  • YES: Automatically creates the USERLIB data set 'SYS1.USERLIB' during the installation.

  • NO: You must manually install the USERLIB data set after the installation, by running the create_userlib.sh script under the ${OPENFRAME_HOME}/scripts directory.

DEFAULT_TEMPLIB_CREATE

Specifies whether to automatically create the default TEMPLIB data set during OpenFrame installation.

  • YES: Automatically creates the TEMPLIB data set 'SYS1.TEMPLIB' during the installation.

  • NO: You must manually install the USERLIB data set after the installation, by running the create_templib.sh script under the ${OPENFRAME_HOME}/scripts directory.

The following enables automatic data sets creation.

DEFAULT_JCLLIB_CREATE=YES
DEFAULT_PROCLIB_CREATE=YES
DEFAULT_USERLIB_CREATE=YES
DEFAULT_TEMPLIB_CREATE=YES

5.7. Configuring Application Database Environment

Specify an application database in Batch.

IKJEFT01_DBTYPE=DB2|ORACLE|TIBERO|TBOCI|ODBC
Item Description

IKJEFT01_DBTYPE

The following database types are supported.

  • DB2

  • ORACLE

  • TIBERO

  • TBOCI

  • ODBC

The link The link is different depending on the set database type. If not specified, the default link is libtdbconndummy.so.

The following libraries are provided.

  • libtdbconndummy.so

  • libtdbconnsw.so

  • libtdbconntbodbc6.so

  • libtdbconntbr6.so

  • libtdbconnudb10.so

The following specifies TIBERO as the application database type.

IKJEFT01_DBTYPE=TIBERO

6. Locating the License File

Locate the Batch license file in ${OPENFRAME_HOME}/license.

$OPENFRAME_HOME/license/lictjes.dat

If no license file exists, the following error occurs.

TMBOOT for node(NODE1) is starting: (E) BOOT2145 License is expired : [COM0907]