OpenTP1 Version 7 Programming Guide
After modifying the system definition, start with the work for using OpenTP1.
Setup an OpenTP1 using the dcsetup command. The dcsetup command is placed in the /BeTRAN/bin/ directory.
A command input example is given below:
% /BeTRAN/bin/dcsetup OpenTP1-home-directory-name <CR> |
The OpenTP1 administrator is responsible for this work. Specify the full pathname with the dcsetup command only when using the sample for the first time. It is unnecessary to execute the dcsetup command specifying the full pathname to setup the sample again. For details on the dcsetup command, see the manual OpenTP1 Operation.
The procedure for activating the OpenTP1 system by using the created sample UAP and system definition for the sample is given below.
Start the OpenTP1 system using the dcstart command. A command input example is given below:
% dcstart <CR> |
Start the created UAPs using the dcsvstart command. First start the server UAP (SPP), then start the client UAP (SUP). A command input example is given below:
% dcsvstart -u tamspp <CR> |
A message log is output to indicate that tamspp becomes online.
% dcsvstart -u tamsup <CR> |
A message log is output to indicate that tamsup becomes online.
How the user server process proceeds is indicated by the message log.
The server UAP (SPP) can also be activated automatically when the OpenTP1 system starts if so specified in the user service configuration definition.
After the tam_mkfs command, an OpenTP1 file system creation tool, is executed, an OpenTP1 file system is created under the $DCDIR/examples/tam/betranfile directory. The table below lists the files contained in the created OpenTP1 file system.
Table 8-8 List of files in OpenTP1 file system (TAM sample)
File name | Purpose | Record length | Number of records |
---|---|---|---|
jnf101 | System journal file | 4096 bytes | 50 |
jnf102 | System journal file | 4096 bytes | 50 |
jnf103 | System journal file | 4096 bytes | 50 |
stsfi101 | Status file | 4608 bytes | 256 |
stsfi102 | Status file | 4608 bytes | 256 |
stsfi103 | Status file | 4608 bytes | 256 |
stsfi104 | Status file | 4608 bytes | 256 |
cpdf01 | Checkpoint dump file | 4096 bytes | 100 |
cpdf02 | Checkpoint dump file | 4096 bytes | 100 |
cpdf03 | Checkpoint dump file | 4096 bytes | 100 |
The table below lists the specifications of the created TAM file.
Table 8-9 Specifications of the TAM sample file
File name | tamexam1 |
---|---|
Purpose | TAM file |
Record length | 40 bytes (including the key length) |
Key area length | 20 bytes |
Key start position | 0th byte (beginning of the record) |
Maximum number of records | 10 |
Table format | Tree |
TAM data file name | $DCDIR/examples/tools/tamdata |
To exchange a sample UAP:
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.