set format

set sts_file_name_1="logical-file-name","system-A-status-file-name",
                    "system-B-status-file-name"
[set sts_file_name_2="logical-file-name","system-A-status-file-name",
                     "system-B-status-file-name"]
[set sts_file_name_3="logical-file-name","system-A-status-file-name",
                     "system-B-status-file-name"]
[set sts_file_name_4="logical-file-name","system-A-status-file-name",
                     "system-B-status-file-name"]
[set sts_file_name_5="logical-file-name","system-A-status-file-name",
                     "system-B-status-file-name"]
[set sts_file_name_6="logical-file-name","system-A-status-file-name",
                     "system-B-status-file-name"]
[set sts_file_name_7="logical-file-name","system-A-status-file-name",
                     "system-B-status-file-name"]
[set sts_initial_error_switch=stop|continue|excontinue]
[set sts_single_operation_switch=stop|continue]
[set sts_last_active_file="logical-file-name"]
[set sts_last_active_side=A|B]
[set watch_time=maximum-response-waiting-time]

command format

None

The status service definition defines the execution environment to manage the status of each system service operated under an OpenTP1 system environment. There is one status service for each node.

A maximum of 7 status file names can be defined. If an OpenTP1 system opens normally, the first defined status file becomes active. The other status files become reserved files. After a restart, the previous file in use will continue to be active.

Status files are managed in duplicate as system A and system B files for better reliability. The same contents are written into the active status file as system A and system B files. Thus, be sure to specify files in which all records are of the same length. Also specify files of the same capacity for each logical file.

Distribute the physical files of system A and system B to more than one disk. When all the physical files of the same system are created in one disk, the system cannot be used if the entire disk becomes faulty. For example, when all the physical files of the same system are created in one disk, there will be no generation of system A and B files that can be duplicated if a disk failure occurs. In this case, OpenTP1 may be terminated urgently or continues operation using only one system, and this may cause a loss of files.

Should a status file be damaged during a normal OpenTP1 system startup, a restart, or during on-line operation, the status service will swap status files to prevent OpenTP1 from suspending. However, this swap function requires that a spare status logical file be defined.

sts_file_name_1-sts_file_name_7="logical-file-name","system-A-status-file-name","system-B-status-file-name"

Specify up to seven status files. One file is created as the active file, and the other six files as spare files. Each status file will be created in duplicate as a system A status file and system B status file, to improve reliability.

The logical file name, system A status file name, and system B status file name must each be unique for each of the seven status files.

logical-file-name~<1-8 character identifier>

Specify the logical file name of the status file.

system-A-status-file-name~<path name>

Specify the full path name of the system A status file name that will make up the logical file.

system-B-status-file-name~<path name>

Specify the full path name of the system B status file name that will make up the logical file.

Specify files of the same record length and record number as for the system A file.

No environment variables can be used for the full path name of the system A or B status file name.

The same file name cannot be specified for the status files more than once even if the full path names are different.

sts_initial_error_switch=stop|continue|excontinue~<<stop>>

Specify the action of the status service if either of the following abnormalities is detected when opening the defined status file:

• the status file has not been created, or
• the status file is damaged.

stop

Specify stop to suspend OpenTP1 without starting the status service; this will guarantee that OpenTP1 can restart.

A stop specification will suspend OpenTP1 if even one of the specified files is abnormal. Take corrective action for the abnormal file, then restart OpenTP1. However, OpenTP1 cannot be restarted if both system A and system B files of the status logical file active in the last on-line operation were damaged.

continue

Specify continue to start the status service even with an abnormality in the specified status logical file.

1. Should an error occur in either system A or system B file of the status logical file active in the last online operation, the contents of the normal system file are copied into a spare system A and system B file. These spare files then become the active files and the status service is started. If there is no spare file to perform the copying, whether the status service stops or continues depends on the specification of the sts_single_operation_switch operand.
2. In starting a system service, if OpenTP1 cannot determine whether the status file selected to be active was the last active file in the previous online operation, OpenTP1 compares it with the logical file name specified with the sts_last_active_file operand. If the file names match, then the status service is started; otherwise the status service is suspended. If the sts_last_active_file operand is not specified, and the last active file cannot be determined, the status service will not be started. The last active file cannot be determined if any of the defined logical files are in a state as shown in Table 3-4 during startup.
   

   Table 3-4 Logical file states for which active file cannot be determined (continue)

   No.	System A state	System B state
   1	BLOCKADE	BLOCKADE
   2	BLOCKADE	OPEN (INIT)
   3	BLOCKADE	NONE
   4	OPEN (INIT)	BLOCKADE
   5	OPEN (INIT)	NONE
   6	NONE	OPEN (INIT)
   7	NONE	BLOCKADE
   8	NONE	NONE

3. If at least one normal status logical file does not exist in either system A or system B, the status service will not be started and OpenTP1 will be suspended.

excontinue

Specify excontinue to perform the same processing as for continue. When nothing or stop is specified for the sts_single_operation_switch operand, any logical file of which either system file has error and the other system file is initialized is skipped for processing during determination of the active file.

The last active file cannot be determined if any of the defined logical files are in a state as shown in Table 3-5 during the status service startup.

Table 3-5 Logical file states for which active file cannot be determined (excontinue)

No.	System A state	System B state
1	BLOCKADE	BLOCKADE
2	BLOCKADE	NONE
3	NONE	BLOCKADE
4	NONE	NONE

Note that if stsinit command initializes either system of the logical file active in the last online operation, the active file cannot be determined correctly.

For troubleshooting of status files, see the manual OpenTP1 Operation.

sts_single_operation_switch=stop|continue~<<stop>>

Specify the status service action to be taken if an I/O error occurs with one system for the active status file during startup or after starting the status service and there is no logical file of which both system files are swappable.

stop

Specify this operand to stop the status service.

continue

Specify this to continue the status service with only the normal system for the active status file.

The KFCA01044-I message appears when single-system operation begins. Perform troubleshooting as soon as this message appears because OpenTP1 can no longer restart if either of the following errors occurs during single-system operation:

• During single-system operation, an error occurs with the normal system.
• During single-system operation, the system goes down at file updating.

sts_last_active_file="logical-file-name"~<1-8 character identifier>

Specify the name of the last active file up to the last online operation as the logical file name. Specify this definition only if continue or excontinue is specified in the sts_initial_error_switch operand. It becomes effective if OpenTP1 cannot determine if the selected active file is the same as the last active file for the previous online operation.

Specify this operand as follows:

1. If the definition can be revised as the active file is changed
   If OpenTP1 is started after all status files are initialized, specify the logical file name with the smallest number as specified in the sts_file_name operand. Then, if the active file is changed because of a swap, change this definition to the new active file name.
   
2. If the definition cannot be revised when the active file is changed
   If during system startup, KFCA01011-I and KFCA01005-E (reason code=0000000015 or 0000000016) is output to indicate a system startup error, inspect the last active file of the previous on-line operation with the log file. If it matches the logical file name output with KFCA01011-I, specify that logical file name in this definition statement, and restart OpenTP1.
   

sts_last_active_side=A|B

If an error occurred with one system for the active status file and this file was shut down in the previous online session, the system that was normal at that time must be specified in this operand.

This specification is used to prevent the defective system (detected in the previous online session) from being selected at restart of OpenTP1.

The sts_last_active_side operand must be specified if one system is shut down due to an error. It is valid only with continue specified in the sts_single_operation_switch operand.

watch_time=maximum-response-waiting-time~<unsigned integer> ((0-65535)) (Unit: seconds)

Specify the maximum waiting time between sending a service request and receipt of a response when communicating between processes by RPC.

OpenTP1 may suspend termination processing for the length of time specified in this operand. Therefore, if you specify a large value, the termination processing of OpenTP1 may take some time.

If no response is received within the specified time, RPC returns a transmission timeout error.

Specify 0 if the system is to wait for a response. When you specify 0, OpenTP1 may not terminate.

If this operand is omitted, the value specified with the watch_time operand of the system common definition is assumed.

Use the default of the watch_time operand of the system common definition for this operand.

We recommend that you do not change the operand unless special tuning is necessary.

If a value that is much greater or smaller than the default of the watch_time operand of the system common definition is specified, a failure may occur causing OpenTP1 to go down.

None