System Initialization

This appendix describes the initialization process required to change Base system settings.

1. Overview

Most settings required to start Base are configured automatically during the installation. This chapter describes how to initialize the system settings to manually change the settings during system operation.

The following are the steps of the Base initialization process.

  1. Creating system tables

    Create a system table by using the baseinit program.

  2. Specifying configuration items

    Specify configuration items required for OpenFrame operation by using the ofconfig program.

  3. Creating VSAM volume tablespaces

    Create a tablespace to store VSAM data sets by using the SQL command CREATE TABLESPACE.

  4. Configuring Volumes

    Perform necessary tasks to use volumes by using the volmgr program.

2. Creating System Tables

OpenFrame provides baseinit, a tool program intended to create or remove system tables.

The following example creates a catalog and VTOC on the DEFVOL volume by using baseinit .

$ baseinit create -t DEFVOL

To operate the baseinit program, use the DBCONN connection information specified in the [SYS1_ODBC] clause from the dbconn.conf file.

<dbconn.conf>

[SYS1_ODBC]
    DATABASE=tb_oframe7
    USERNAME=tibero
    ENPASSWD=AA68690384C8042F154AEDF2A7B9F2A52B27EB63AF0777D67076195863248D2A

For more information about baseinit, refer to OpenFrame Tool Reference Guide.

3. Specifying Configuration Items

OpenFrame saves and manages configuration items required for operation in Tibero tables.

To use OpenFrame, modify the openframe_base.conf file as needed, and then save the configuration items in Tibero tables by using the ofconfig tool.

The following example uses ofconfig to apply configuration items of NODE1 to a Tibero table.

$ ofconfig import -f openframe.conf -n NODE1

For more information about ofconfig, refer to OpenFrame Tool Reference Guide.

4. Creating VSAM Volume Tablespaces

OpenFrame provides TSAM, which uses DBMS as its low-level storage, to support functionalities and performance of VSAM in mainframes. Internally, VSAM data sets are mapped to DMBS tables, therefore any volumes containing VSAM datasets can be mapped to DBMS tablespaces.

Just as you must create directories in Unix for non-VSAM data sets, you must also create tablespaces to store VSAM data sets.

The latest version of TSAM supports mapping multiple volumes to a single tablespace.

The following uses the CREATE TABLESPACE statement to create a tablespace for storing VSAM data sets.

SQL> CREATE TABLESPACE "DEFVOL" DATAFILE 'DEFVOL.dbf' SIZE 100M;

5. Configuring Volumes

In mainframes, storage devices are configured by modifying the system configuration file during the system initialization process. In OpenFrame, you can specify any information related to I/O devices and system units by using the volmgr tool.

In OpenFrame, non-VSAM data sets of a mainframe are converted into a single Unix file. If non-VSAM data sets are created in a specified volume, OpenFrame uses these datasets to create a Unix file in the volume directory.

If you use the volmgr tool to define volume information, the volume directory is automatically created. Using volmgr requires Tmax engine.

The following example uses the volmgr tool to prepare DEFVOL.

$ volmgr define device -dn 0001 -dt 3380 -ms 2048 -dg SYSDA
$ volmgr define volume -v DEFVOL -dn 0001

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