A multi-OpenTP1 system is defined as several OpenTP1 systems operating independently on one machine.

1. Different partitions or different files for each different OpenTP1 system are allocated for use as an OpenTP1 file system.
2. A different definition file storage directory is created for each OpenTP1 system.
3. A definition file for each OpenTP1 system is created under the respective directory.

However, definition parameters, as summarized in Table 6-1, must be different for each OpenTP1 system. For details on the directory and other parameters, see the manual OpenTP1 Operation.

Table 6-1 Definition parameters which must be different for each OpenTP1 system

No.	Definition file name	Definition	Contents
1	System common definition	name_port	Well-known port number of the name service
		system_id	OpenTP1 identifier
		all_node	All node names and the well-known port numbers1 of all the name services in the OpenTP1 system
		prc_port	Port number used by multinode linkage control function
2	Status service definition	sts_file_name	Path name of physical file of status file
3	Journal function definition System journal service definition Checkpoint dump service definition	jnladdpf	Path name for physical file of journal function file
4	DAM service definition	damfile	Path name for physical file of DAM file
5	TAM service definition	tamtable	Path name for physical file of TAM table
6	Message queue service definition	quegrp	Path name for physical file of queue file

¹ When you specify the host name (or IP address) of the local host as the node name, make sure you do not use the same port number twice.

To perform a remote procedure call among the OpenTP1 systems in the multi-OpenTP1 system environment, define the host names of the OpenTP1 nodes other than the local node in the all_node operand of the system common definition of each OpenTP1 node. Then specify Y in the rpc_multi_tp1_in_same_host operand.