OpenTP1 Version 7 Description

[Contents][Glossary][Index][Back][Next]

5.1.2 Environment setup tasks

This section describes the tasks performed when setting up the OpenTP1 environment. For details, see the manual OpenTP1 Operation.

Organization of this subsection
(1) Environment setup tasks performed by the superuser
(2) Environment setup tasks performed by the OpenTP1 administrator
(3) Using the MCF Message Exchange facility
(4) Using the MQA Message Queuing facility

(1) Environment setup tasks performed by the superuser

(a) Register the OpenTP1 administrator

Set a user ID and associated password for the OpenTP1 administrator. Note that the OpenTP1 system does not support large user IDs. Do not use a large user ID to register the OpenTP1 administrator.

(b) Define the OpenTP1 group

In the group ID for OpenTP1 administrators, define which members are to belong to the OpenTP1 administrator group.

(c) Install OpenTP1

Install the OpenTP1 products required for the system.

(d) Create the OpenTP1 directory

Define directories for installing OpenTP1 products. Set the OpenTP1 administrator as the owner of the directories, and set OpenTP1 administrator group members as the owner group of the directories.

(e) Register OpenTP1 with the OS

Use the OpenTP1 command dcsetup to register OpenTP1 products with the OS.

(f) Assign a disk partition for the OpenTP1 file system

Assign disk or disk partitions to build an OpenTP1 file system on a character special file. If you build the OpenTP1 system file on ordinary files, this assignment is not required.

(2) Environment setup tasks performed by the OpenTP1 administrator

(a) Create the OpenTP1 system definitions

Create the files for the definitions used to define OpenTP1 system services, and write these system definitions. You can check the created definitions by executing the dcdefchk command.

(b) Set the OpenTP1 administrator environment

Set environment variables for the OpenTP1 administrator's login environment. Specify a directory name consisting of 50 bytes or less for the DCDIR environment variable.

(c) Allocate resources for OpenTP1 internal control

Reserve the resources to be used for OpenTP1. To reserve resources, execute the dcmakeup command. The amount of resources to be reserved by the dcmakeup command is automatically resolved according to the system service definition.

(d) Initialize the OpenTP1 file system

Use the OpenTP1 command filmkfs to initialize the area for the OpenTP1 file system. At this time, specify the OpenTP1 file system area name, using 49 or fewer characters.

(e) Create OpenTP1 files

Use OpenTP1 file commands, such as jnlinit or stsinit, to format the area for the OpenTP1 file system.

(f) Create non-OpenTP1 files

Create required ordinary files, such as executable files for UAPs or OpenTP1 definition files.

(g) Register the resource manager

If a resource manager other than the OpenTP1 resource manager is required, use the command trnlnkrm to register the resource manager in the system. If an extended RM registration definition is created, the trnlnkrm command does not need to be executed.

(h) Create transaction control object files

Use the command trnmkobj to create transaction-control object files which control transactional UAPs.

(i) Create UAPs to use with OpenTP1

Create UAPs to use with OpenTP1 after you finish setting up the environment for TP1/Message Control if using the message exchange facility, and for TP1/Message Queue if using the message queuing facility.

(3) Using the MCF Message Exchange facility

The OpenTP1 administrator carries out the following tasks:

  1. The OpenTP1 administrator writes the MCF main function and places it in a directory.
  2. The OpenTP1 administrator registers MCF service names.
  3. The OpenTP1 administrator creates system service information definition files.
  4. The OpenTP1 administrator creates definition object files.

(4) Using the MQA Message Queuing facility

The OpenTP1 administrator carries out the following tasks:

  1. The OpenTP1 administrator creates definition object files.
  2. The OpenTP1 administrator or programmers create UAPs used in OpenTP1.