OpenTP1 Version 7 Operation
Use the namndchg command or the namchgfl command to change the nodes composing a domain while OpenTP1 is active. The following shows the procedure for changing the domain configuration for each command.
Change the all_node operand in the system common definition and execute the namndchg command to change the domain configuration. The procedure for changing the domain configuration is as follows:
Specify the -l option for the namndchg command to display the names and port numbers of the current nodes of the domain (specification of the all_node operand).
Change the domain configuration by using the domain definition file. You can use the namchgfl command to change the domain configuration without changing the system common definition. To enable the namchgfl command, specify Y in the name_domain_file_use operand in the system common definition. For details about the name_domain_file_use operand, see the manual OpenTP1 System Definition. The procedure for changing the domain configuration is as follows:
If the same node is specified for both the old and new domain configurations, the following information about the node in the old configuration is inherited by the new domain configuration.
You need domain definition files to change the domain configuration without changing the system common definition. There are three domain definition files, one for all_node, one for all_node_ex, and one for priority selection nodes. The method for specifying the definition file for priority selection nodes is the same as for the definition files for all_node and all_node_ex.
You can use any names for the files, but the length of a file name must not exceed 40 bytes. Store the domain definition files in the following directories:
If a node name or port number is invalid in one of these files, the namchgfl command issues the message KFCA00656-E (invalid node name), KFCA00657-E (invalid port number), or KFCA00666-E (host undefined) and then returns control with an error, in which case the specified domain configuration change is ignored.
If a node specified in the definition file for priority selection nodes is not defined in the domain definition file for all_node, the command issues the KFCA00603-W message (undefined in all_node), in which case the specification of the priority selection node is ignored. If a priority selection node is defined correctly on another line in the same file, the specification as a priority selection node is effective.
If you store multiple domain definition files in each directory, one domain (OpenTP1 system) is created by combining all the domain definition files stored in the same directory.
In the cases below, the OpenTP1 system is created as a domain consisting only of the local node. The definition file for priority selection nodes depends on the information specified in the domain definition file.
The format for coding a domain definition file is as follows:
node-name[,[port-number]][,] |
The following is an example of coding a domain definition file:
0---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+- 10.209.117.30,11111, #comment 10.209.117.40,33333, #comment (linefeed)# #ZZZ# 10.209.117.50,11111 10.209.117.60,33333 10.209.117.70 10.209.117.80, 10.209.117.90,, (blank line)# |
Define an area of shared memory that can be used by the name service when OpenTP1 starts. Because you cannot change the size of this area while OpenTP1 is running, you need to secure the required size (determined by the maximum number of nodes) when OpenTP1 starts. You can specify the maximum number of nodes in the all_node_extend_number operand or the all_node_ex_extend_number operand in the system common definition. For details about these operands, see the manual OpenTP1 System Definition.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.