OpenTP1 Version 7 System Definition

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

System common definition

Format

set format

[set rpc_trace=Y|N]
[set rpc_trace_name="RPC-trace-collection-file-name"]
[set rpc_trace_size=RPC-trace-collection-file-capacity]
[set name_port=name-service-port-number]
[set system_id=OpenTP1-identifier]
[set all_node="node-name[:port-number][:high]"
    [,"node-name[:port-number][:high]"...]]
set node_id=node-identifier
[set rpc_retry=Y|N]
[set rpc_retry_count=maximum-number-of-rpc-processing-retries]
[set rpc_retry_interval=rpc-processing-retry-interval]
[set multi_node_option=Y|N]
[set prc_port=port-number-used-by-multinode-linkage-control]
[set rpc_delay_statistics=Y|N]
[set my_host="host-name"|MYHOST]
[set jp1_use=Y|N]
[set rpc_message_level=display-level-for-RPC-troubleshooting-
    messages]
[set rpc_multi_tpl_in_same_host=Y|N]
[set max_socket_descriptors=maximum-number-of-file-descriptors-for-
    sockets]
[set rpc_datacomp=Y|N]
[set domain_masters_addr="domain-name=host-name-1
      [:port-number-1][,host-name-2[:port-number-2]
      [,host-name-3[:port-number-3]]]"
      [,"domain-name=host-name-1[:port-number-1][,host-name-2
      [:port-number-2][,host-name-3[:port-number-3]]]"...]]
[set domain_masters_port=port-number-of-domain-alternate-schedule-
    service]
[set domain_use_dns=Y|N]
[set client_uid_check=Y|N]
[set rpc_port_base=minimum-port-number]
[set prf_trace=Y|N]
[set trn_prf_trace_level=trace-acquisition-level]
[set core_suppress_watch_time=time-period-to-suppress-outputting-the-
    core-dump-about-a-process-being-monitored-in-real-time-for-a-timeout]
[set rpc_netmask=sub-netmask-value-specified-in-TCP/IP-network-
    definition-file]
[set ipc_sockctl_highwater=percentage-of-sockets-at-which-temporary-
    closing-starts
    [,percentage-of-sockets-for-which-temporary-closing-is-not-performed]]
[set ipc_sockctl_watchtime=length-of-time-to-wait-until-the-sockets-
    are-reusable]
[set ipc_conn_interval=length-of-time-to-wait-until-the-connection-is-
    established]
[set ipc_send_interval=interval-for-monitoring-data-transmission]
[set ipc_send_count=number-of-times-data-transmission-is-monitored]
[set ipc_header_recv_time=length-of-time-to-wait-until-the-
    communication-control-data-is-received]
[set name_notify=Y|N]
[set all_node_ex="node-name[:port-number]"[,"node-name[:port-
    number]"...]]
[set rpc_server_busy_count=number-of-bundles-that-output-
                           KFCA00356-W-message]
[set rpc_send_retry_count=number-of-retries-if-an-error-occurs-
                          during-TCP/IP-connection]
[set rpc_send_retry_interval=interval-between-retries-if-an-error-
                             occurs-during-TCP/IP-connection]
[set thdlock_sleep_time=thread's-waiting-time-if-a-lock-conflict-
                        occurs-among-threads]
[set ipc_recvbuf_size=receive-buffer-size-of-TCP/IP]
[set ipc_sendbuf_size=send-buffer-size-of-TCP/IP]
[set ipc_listen_sockbufset=Y|N]
[set rpc_router_retry_count=number-of-retries-if-ENOBUFS-or-
                            ENOMEM-occurs]
[set rpc_router_retry_interval=interval-between-retries-if-
                               ENOBUFS-or-ENOMEM-occurs]
[set ipc_backlog_count=length-of-queue-storing-connection-
                       establishment-requests]
[set statistics=Y|N]
[set name_domain_file_use=Y|N]
[set all_node_extend_number=maximum-number-of-nodes-after-
                            domain-reconfiguration]
[set all_node_ex_extend_number=maximum-number-of-nodes-after-
                               domain-reconfiguration-by-using-
                               domain-definition-files]
[set prc_current_work_path=path-name-of-the-directory-under-
                           which-the-current-working-directory-is-
                           created]
[set rpc_max_message_size=maximum-size-of-a-message-sent-or-
                          received-by-an-RPC]
[set uap_trace_file_put=Y|N]
[set dcstart_wakeup_retry_count=number-of-error-retries-for-
                                OpenTP1-startup-notification]
[set dcstart_wakeup_retry_interval=error-retry-interval-for-
                                   OpenTP1-startup-notification]
[set nam_prf_trace_level=NAM-event-trace-acquisition-level]
[set fil_prf_trace_option=0|1]
[set fil_prf_trace_delay_time=file-access-processing-time-threshold-which-becomes-FIL-event-trace-collection-condition]
[set jnl_prf_event_trace_level=collection-level-for-JNL-performance-verification-trace]
[set jnl_fileless_option=Y|N]
[set watch_time=maximum-response-waiting-time]

command format

{{dcbindht -h host-name
              [-n network-name[,network-name]...]}}

putenv format

[putenv LANG LANG-setting]

Function

The system common definition defines the common execution environment of an OpenTP1 system.

Explanation

set format

rpc_trace=Y|N~<<N>>

Specify whether an RPC trace is to be collected.

Y
An RPC trace is collected.

N
An RPC trace is not collected.

When an RPC trace is collected, the processing speed may be reduced and the RPC may return an error due to a timeout. In this case, increase either of the following values, which are the maximum amount of response waiting time (default: 180 sec.), to an appropriate value:

  1. The maximum response waiting time specified in the watch_time operand of the system common definition, user service definition, or user service default definition
  2. The maximum response waiting time that the RAP-processing server inherited from the client

Whether the RAP-processing server inherits the maximum response waiting time from the client is specified in the DCWATCHTIMINHERIT operand of the client environment definition (for TP1/Client/W or TP1/Client/P) or in the dcwatchtiminherit operand of the TP1/Client/J environment definition (for TP1/Client/J).

If Y is specified in the DCWATCHTIMINHERIT or dcwatchtiminherit operand, use the maximum response waiting time indicated in 2 above.

If N is specified in the DCWATCHTIMINHERIT or dcwatchtiminherit operand, or if these operands are not specified, use the maximum response waiting time indicated in 1 above.

When the remote API facility is used, the RPC trace for RAP-processing clients cannot be acquired even if Y is specified in this operand.

This operand can also be specified in the user service definition (or the RAP-processing listener service definition) and the user service default definition.

The priorities of specified values are (1.>2.>3.):

  1. User service definition or RAP-processing listener service definition
  2. User service default definition
  3. System common definition

rpc_trace_name="RPC-trace-collection-file-name"~<path name> <<$DCDIR/spool/rpctr>>

Specify the path name of the file for collection of the RPC trace.

In the path name, the maximum length of the name of the file for acquiring the RPC trace is 13 characters. The default file name is rpctr.

To specify an environment variable in a path name, make sure that the path name begins with the environment variable (example: $DCDIR/tmp/file-name).

This operand can also be specified in the user service definition (or the RAP-processing listener service definition) and the user service default definition.

The priorities of specified values are (1.>2.>3.):

  1. User service definition or RAP-processing listener service definition
  2. User service default definition
  3. System common definition

rpc_trace_size=RPC-trace-collection-file-capacity~<unsigned integer> ((1024-2147483648)) <<4096>> (Unit: bytes)

Specify the capacity of the file for collection of the RPC trace.

This operand can also be specified in the user service definition (or the RAP-processing listener service definition) and the user service default definition.

The priorities of specified values are (1.>2.>3.):

  1. User service definition or RAP-processing listener service definition
  2. User service default definition
  3. System common definition

Even if you specify 4096 or less for this operand in the system common definition, the user service default definition, or the user service definition, if the length of the transmitted text exceeds the specified value, the size of the trace file to be created may be larger than the value specified by this operand.

name_port=name-service-port-number~<unsigned integer> ((5001-65535)) <<10000>>

Specify the port number that becomes the address of the name service.

If creating a multi-OpenTP1 system, specify a different port number for each system. Specify a different port number also if a program other than an OpenTP1 system is using a specific port number.

The port number specified using this operand must not be used by other programs.

Note that the operating system assigns certain numbers automatically. You should not use such a number for the port number. The numbers assigned by the operating system differ depending on the type and version of the operating system. For details, see the documentation for your operating system.

system_id=OpenTP1-identifier~<1-2 character identifier>

Specify an OpenTP1 identifier.

If you change the value specified in this operand, you need to initialize the checkpoint dump file.

all_node="node-name[:port-number][:high]"[,"node-name[:port-number][:high]"...]

Specify the names of all nodes of the OpenTP1 system and the port numbers whose name server is used as a well-known port number. If this operand is not specified, an OpenTP1 system formed from the local node only is assumed.

When you use the service information prioritizing function, specify :high, which is the service information prioritizing keyword, after specifying of the node whose service information is to be selected at high priority (preferred node). If the port number is omitted, specify :high after the node name. This keyword must be specified at the end of the specification value. If the keyword delimiter (:) is omitted or is specified in an incorrect position, the definition becomes invalid. If the definition is invalid, error message KFCA00606-E (host undefined) or KFCA00607-E (invalid port number) is output, and startup of OpenTP1 fails.

If the system is not in a multi-OpenTP1 configuration, do not specify a host name (or IP address) that indicates the local host or a loopback address (an IP address beginning with 127) in node-name. If you do so, the performance of transactions may be adversely affected or the OpenTP1 system may go down.

If you have created a multi-OpenTP1 system, you can specify the host name (or IP address) of the local host as a node name in this operand. However, each port number must be unique. Note that you must not specify the name of a host that has an IP address that begins with 127 (example: 127.0.0.1), such as a loopback address. Doing so might adversely affect global search and other facilities.

When you specify Y for the name_notify operand and use the startup notification facility, a startup notification is sent to the instance of OpenTP1 that starts on the node specified in this operand. By using the startup notification facility, OpenTP1 can manage connection establishment and communicate with more accuracy.

When you use the global archive journal service, specify this operand as follows:

node-name~<1-255 character identifier>
Specify all nodes of the OpenTP1 system. The identifier you specify can consist of alphanumeric characters, periods, and hyphens. You can specify a node name specified in /etc/hosts. If you specify a node name longer than 255 characters, the first 255 characters are used as the node name.

port-number~<unsigned integer> ((5001-65535)) <<10000>>
Specify a port number for which the name server uses it as a well-known port number.
If this port number is not specified, a port number for the name service specified in the name_port operand is assumed.

Service information prioritizing keyword - :high
When using the service information prioritizing function, specify this keyword for the node whose service information is to be selected at high priority (preferred node). For details about the service information prioritizing function, see the manual OpenTP1 Description.

Note:
If the node specified in this operand is also specified in the all_node_ex operand or if the same node is specified more than once in this operand, the KFCA00604-W message is output to the first operand that is analyzed by OpenTP1. In this case, the first node that is analyzed is valid. The priority of analysis is as follows (A>B indicates that A takes precedence over B):
  • When the same node is specified in both the all_node operand and the all_node_ex operand
    all_node operand > all_node_ex operand
  • When the same node is specified more than once in the all_node (all_node_ex) operand
    Node that is specified first > node that is specified later

node_id=node-identifier~<4 character identifier>

Specify the identifier of the local node. Each name within an OpenTP1 system must be unique.

If you change the value of this operand, you need to initialize the journal file.

rpc_retry=Y|N~<<N>>

For an OpenTP1 RPC, its server may not be active when a service request is made (for example, because of the system being changed over or the remove server being started up) and this may cause a service request to terminate with an error. In this case, the rpc_retry operand is used to specify whether RPC processing is retried.

Y
RPC processing is retried.

N
RPC processing is not retried.

The following describes the types of RPC processing retry.

The table below shows the relationship between RPC processing retry types and the specifications of the rpc_retry_count and rpc_retry_interval operands.

Retry type rpc_retry_count operand specification rpc_retry_interval operand specification
Retry of request destination search by the user server Y Y
Retry of request send by the user server Y N
Retry of request send by the system server Y Y

Legend:
Y: The operand specification is valid.
N: The operand specification is invalid.

rpc_retry_count=maximum-number-of-rpc-processing-retries~<unsigned integer> ((1-3600)) <<18>>

Specify the maximum number of retries for the request destination search and request send.

This specification is applicable when Y is specified in the rpc_retry operand.

rpc_retry_interval=rpc-processing-retry-interval

Specify the retry interval for the request destination search or request send.

multi_node_option=Y|N~<<N>>

Specify whether to use the multinode facility with an applicable OpenTP1 node.

Y
The multinode facility is used.

N
The multinode facility is not used.

If Y is specified with no TP1/Multi installed, a warning message is output and the OpenTP1 system halts.

prc_port=port-number-used-by-multinode-linkage-control~<unsigned integer> ((5001-49999))

Specify the port number to be used by the multinode linkage control function. If N is specified in the multi_node_option operand, the prc_port operand does not need to be specified. To create a multi-OpenTP1 system, use a different number for each OpenTP1 system.

If the OpenTP1 system in current use is not a multi-system and if any program not under the OpenTP1 system needs to use a particular port number, specify a port number different from that number for process service. Also, specify a port number different from the number for name service specified in the name_port operand. The port number specified in the multinode physical definition must be the value specified in the prc_port operand. If the setting of this operand is changed, set up the OpenTP1 system again.

The port number specified using this operand must not be used by other programs.

Note that the operating system assigns certain numbers automatically. You should not use such a number for the port number. The numbers assigned by the operating system differ depending on the type and version of the operating system. For details, see the documentation for your operating system.

rpc_delay_statistics=Y|N~<<N>>

Specify whether to collect communication delay time statistics.

Communication delay time means the time required for actual communication (request send and response send) out of the dc_rpc_call function response time. Communication delay time statistics are collected for synchronous response type RPC only.

Y
Communication delay time statistics are collected.

N
Communication delay time statistics are not collected.

my_host="host-name"|MYHOST~<1-to-255-character identifier>

Specify the network adapter to be used as a host name. The identifier you specify can consist of alphanumeric characters, periods, and hyphens. You cannot specify the identifier in an IP address format. The host name must be mapped with an IP address in the /etc/hosts file or by using DNS. Note that, in host-name, you must not specify localhost or a host whose IP address begins with 127 (example: 127.0.0.1). Only one host name can be specified.

If this operand is omitted or MYHOST is selected, the system assumes that the name returned by the hostname command has been specified.

When a host name longer than 64 characters is specified, no host name is set in the set_host argument during user authentication by a TP1/Client broadcast (dc_clt_cltin_s or dc_clt_cltin).

jp1_use=Y|N~<<N>>

Specify whether to register an event in the JP1 event service facility.

Y
The event is registered.

N
The event is not registered.

For details about the events to be registered in the JP1 event service facility, see the manual OpenTP1 Operation.

rpc_message_level=display-level-for-RPC-troubleshooting-messages~<unsigned integer> ((0-2)) <<2>>

Specify the display level for RPC troubleshooting messages.

0
No RPC troubleshooting messages are displayed.

1
The RPC troubleshooting messages with a display level of 1 or lower are displayed.

2
The RPC troubleshooting messages with a display level of 2 or lower are displayed.

The following shows the RPC troubleshooting messages (KFCA00325-E to KFCA00332-W) and display levels.

Message Display level
KFCA00325-E 0
KFCA00326-W 2
KFCA00327-W 1
KFCA00328-W 2
KFCA00329-E 0
KFCA00330-E 0
KFCA00331-W --
KFCA00332-W 1

Legend:
--: Not displayed.

The RPC troubleshooting messages are output to the standard error output.

rpc_multi_tp1_in_same_host=Y|N~<<N>>

Specify whether more than one OpenTP1 within a host is assumed to be in the same global domain# (group specified by the all_node operand).

#
Here, a global domain means a set of the following node names:
When N is specified for the name_domain_file_use operand of the system common definition:
A set of node names specified in the all_node and all_node_ex operands of the system common definition
When Y is specified for the name_domain_file_use operand of the system common definition:
A set of node names specified in the domain definition file. Note that the domain definition file is stored at the following location:
  • Domain definition file of the all_node operand
    The $DCCONFPATH/dcnamnd directory
  • Domain definition file of the all_node_ex operand
    The $DCCONFPATH/dcnamndex directory

Y
More than one OpenTP1 within a host is assumed to be in the same global domain.

N
More than one OpenTP1 within a host is not assumed to be in the same global domain.

The specification of this operand must be changed after OpenTP1 is stopped. After the specification is changed, enter the dcsetup command before starting OpenTP1.

max_socket_descriptors=maximum-number-of-file-descriptors-for-sockets~<unsigned integer> ((32-2032)) <<64>>

Specify the maximum number of file descriptors to be used for sockets by the processes under the control of OpenTP1#.

The processes under the OpenTP1 control# exchange the process information with the system service or the user server through the TCP/IP communication using sockets. Therefore, the maximum number of file descriptors for sockets must be changed depending on the number of UAP processes that operate concurrently.

#
Use this operand for OpenTP1 processes other than the MCF services (MCF manager service, MCF communication service, and application startup service). For the MCF services, see System service information definition and System service common information definition.

Calculate the maximum number of file descriptors for sockets using the following formula.

[Figure] (Number of UAP processes in the local node#1 + number of system service processes#2)/0.8 [Figure]

[Figure] [Figure]: Rounded up to the nearest whole integer.

#1: The number of UAP processes in the local node is the sum of the following values:
  • Number of UAP processes in the local OpenTP1
  • Number of transactions to be started concurrently by the CUP (value of the parallel_count operand specified in the client service definition)

#2: The number of system service processes in the local OpenTP1.

If the value specified by this operand is too small, the connection cannot be set with other processes under the OpenTP1 control and the process terminates abnormally after outputting the KFCA00307-E error message.

This operand can also be specified in the user service definition and the user service default definition.

The priority of the specified values in decreasing order is as follows.

For the system server, the priority of the specified values is (1. > 2.):
  1. System-specific service definition
  2. System common definitions

For the user server, the priority of the specified values is (1. > 2. > 3.):
  1. User service definition
  2. User service default definition
  3. System common definition

rpc_datacomp=Y|N~<<N>>

Specify whether the OpenTP1 system compresses the user data to be sent when the client requests a service or when the server returns a response to a service request.

The specification of this operand takes effect on the client that issues the dc_rpc_call function for service request. Therefore, if the client node specifies rpc_datacomp=Y, the compressed user data is sent for a service request message or service response message even if the node with a server that accepts the service does not specify rpc_datacomp=Y. This applies to the server system that supports the user data compression facility. On the contrary, if the client node does not specify rpc_datacomp=Y, the non-compressed user data is sent for the service request message or service response message even if the node with a server that accepts the service specifies rpc_datacomp=Y.

When specifying rpc_datacomp=Y at the client node produces no compression effect on the user data, the non-compressed user data is sent for service request. If this specification produces any compression effect on the response message, the compressed user data is sent for response.

Y
The compressed user data is sent when a service is requested or a response is returned to a service request.

N
The non-compressed user data is sent when a service is requested or a response is returned to a service request.

domain_masters_addr="domain-name=host-name-1[:port-number-1] [,host-name-2[:port-number-2][,host-name-3[:port-number-3]]]" [,"domain-name=host-name-1[:port-number-1][,host-name-2[:port-number-2][,host-name-3[:port-number-3]]]"...]

Specify the domain name of the communication destination and the host name (and port number) of the domain-alternate schedule service when the domain-specified RPC is issued. When this definition is specified, the communication can be performed without searching the domain name service when the domain-specified RPC is issued. Therefore, the RPC response time can be reduced.

If the port number is not specified, the value of the domain_masters_port operand is assumed.

domain-name~<identifier of at least 1 character>
Specify the domain name of the communication destination.

host-name-1, host-name-2, host-name-3~<1-to-255-character identifier>
Specify the host name of the schedule service.
Specify the host name of priority 1 as host name 1 and the host name of priority 2 as host name 2 and the rest.
If you specify a host name longer than 255 characters, the first 255 characters are used as the host name.

port-number-1, port-number-2, port-number-3~<unsigned integer> ((5001-65535))
Specify the port number of the schedule service.
Specify the port number of priority 1 as port number 1 and the port number of priority 2 as port number 2 and the rest.

domain_masters_port=port-number-of-domain-alternate-schedule-service~<unsigned integer> ((5001-65535))

Specify the port number of the domain-alternate schedule service of the communication destination, which is required to communicate without searching the domain name service when the domain-specified RPC is issued.

The port number specified using this operand must not be used by other programs.

Note that the operating system assigns certain numbers automatically. You should not use such a number for the port number. The numbers assigned by the operating system differ depending on the type and version of the operating system. For details, see the documentation for your operating system.

domain_use_dns=Y|N~<<Y>>

Specify whether to inquire the domain name service when searching for the domain that is not specified in the domain_masters_addr operand when the domain-specified RPC is issued.

Y
The domain name service is required.

N
The domain name service is not required.

client_uid_check=Y|N

~<<HP-UX or Windows: Y, AIX, Linux, Solaris: N>>

Specify whether to use the user authentication facility for TP1/Client/W or TP1/Client/P.

Y
The user authentication facility for TP1/Client/W or TP1/Client/P is used. Note that if you want to apply Trusted System in HP-UX or apply HP-UX Shadow Passwords, specify S. Specifying S in an OS other than HP-UX results in a definition error.

N
The user authentication facility for TP1/Client/W or TP1/Client/P is not used.

When N is specified, any authentication request from TP1/Client/W or TP1/Client/P is authorized regardless of the log name. When this operand is set to Y (or S in HP-UX) in AIX, Linux, Solaris, or HP-UX, the user ID of the namd process becomes root.

rpc_port_base=minimum-port-number~<unsigned integer> ((5001-65535))

If processes under control of OpenTP1 are not allocated to well-known ports, you can restrict the receiving port numbers to within a specific range. Specify the minimum port number.

The number of port numbers to be used is the value of the rpc_process_count operand (maximum number of server processes to start concurrently) of the process service definition, plus 129. Therefore, specifying the rpc_port_base operand validates the receiving port numbers within the specified range. This operand is effective for the OpenTP1 system servers, SUP, SPP, and MHP.

The sum of the values specified in this operand and the prc_process_count operand of the process service definition, plus 128 must not exceed 65535. If the sum exceeds 65535, the port numbers ranging from the value specified in this operand to 65535, and port numbers assigned by the operating system will be used.

This operand is ignored and the port numbers assigned by the operating system are used for the processes not allocated to well-known ports under OpenTP1 when:

Do not define a well-known port of OpenTP1 or any other program within the range of the minimum port number to the sum of the minimum port number, the maximum number of concurrently started server processes and 128, or as a port number assigned by the operating system if this operand is not specified.

prf_trace=Y|N~<<Y>>

Specifies whether to acquire the performance verification trace.

Y
Acquire the performance verification trace.

N
Do not acquire the performance verification trace.

trn_prf_trace_level=trace-acquisition-level~((00000001-00000003)) <<00000001>>

Specifies the level of performance verification trace to be acquired. The event IDs about transactions are 0x4000 to 0x4150. For details on event IDs, see the manual OpenTP1 Operation.

00000001
Acquires the performance verification trace information (event IDs 0x4000 to 0x4017)

00000002
Acquires the performance verification trace information about the transaction start event and the transaction end event (event IDs 0x4100 and 0x4150).

00000003
Acquires the performance verification traces of both 00000001 and 00000002.

core_suppress_watch_time=time-period-to-suppress-outputting-the-core-dump-about-a-process-being-monitored-in-real-time-for-a-timeout~<unsigned integer> ((0-3600)) <<0>> (units: seconds)

Specify the time period during which the system suppresses outputting the core dump about a process that is monitored in real time for a timeout and is forcibly terminated if a timeout occurs.

The system suppresses outputting the core dump about a process for the specified time period since the last time the core dump for the process was output due to a timeout.

If you specify 0 in this operand, the system does not suppress outputting the core dump. The system outputs the core dumps about all the processes that are forcibly terminated due to a timeout of real-time monitoring.

rpc_netmask=subnet-mask-value-specified-in-the-network-definition-file-for-TCP/IP

When there is a subnet in a network where OpenTP1 is running, specify a dotted decimal form Internet address as the subnet mask value which is specified in the network definition file for TCP/IP. For example, this operand is specified in this way: rpc_netmask=255.255.255.0. Note that if you place a space between a dot and a number, the part after the space is ignored.

If the network definition file for TCP/IP does not specify any subnet mask, you do not need to specify this operand.

This operand is valid when the dcbindht command definition is specified. When OpenTP1 is running in a network that has a subnet and the dcbindht command format definition is specified, you must specify this operand. If you do not specify this operand when OpenTP1 is running in a network that has a subnet, the specification in the dcbindht command has no effect. This is because the network name specified in the dcbindht command format definition does not match any network address that OpenTP1 recognizes.

To use dcbindht with the OpenTP1 system in a network environment having a subnet, all the networks belonging to the OpenTP1 global domain must use the same subnet mask. If those networks do not use the same subnet mask, dcbindht may not work correctly.

ipc_sockctl_highwater=percentage-of-sockets-at-which-temporary-closing-starts[,percentage-of-sockets-for-which-temporary-closing-is-not-performed]~<unsigned integer>((0-100))<<100,0>>

For the max_socket_descriptors operand specification value, specify a percentage of sockets at which temporary closing starts.

When the number of file descriptors that are used for the sockets in a process exceeds the following value, OpenTP1 starts temporary closing.

Value specified in the max_socket_descriptors operand x (Percentage of sockets at which temporary closing starts/100)

If you specify 0 for the percentage of sockets at which temporary closing starts, temporary closing is executed each time a connection is established. For details about temporary closing, see the manual OpenTP1 Description.

You can also specify the percentage of connections that are not to be temporarily closed. The system calculates the number of connections that are not to be temporarily closed as follows:

Value specified in the max_socket_descriptors operand x (Percentage of sockets for which temporary closing is not performed/100)

The percentage of sockets for which temporary closing is not performed should be less than the percentage of sockets at which temporary closing starts. If you specify a value greater than the percentage of sockets at which temporary closing starts, the system assumes the same value as the percentage of sockets at which temporary closing starts.

OpenTP1 chronologically manages the connections that are established within a process. When you specify the percentage of sockets for which temporary closing is not performed, the temporary closing requests are sent starting with the oldest connection that was established.

This operand is used to specify the percentage of sockets at which temporary closing starts, as a percentage of the value specified in the max_socket_descriptors operand. If a small value is specified for the max_socket_descriptors operand and also for this operand (the percentage of sockets at which temporary closing starts), many temporary closing requests occur, affecting the performance or causing communication failures.

You can also specify this operand in the RAP-processing listener service definition, the user service default definition, or the user service definition.

The priority of the specified values is (1.>2.>3.):

  1. User service definition or RAP-processing listener service definition
  2. User service default definition
  3. System common definition

ipc_sockctl_watchtime=length-of-time-to-wait-until-the-sockets-are-reusable~<unsigned integer>((0-65535))<<180>> (unit: seconds)

Specify the length of time (seconds) to wait from the moment the number of file descriptors used for the sockets in the process reaches the value specified in the max_socket_descriptors operand until the sockets become reusable due to temporary closing.

Whether the service or service group is to be shut down if a UAP terminates abnormally depends on the specification of the hold and term_watch_time operands. For details, see the descriptions of the hold and term_watch_time operands of the user service definition.

Since temporary closing disconnects the connection between processes based on the agreement of the processes, the process that sends the request for temporary closing cannot disconnect the connection until it receives the response. When the process receives the response, the connection is disconnected, and the sockets can be reused.

If no process returns the response to the request for temporary closing after the length of time specified in the ipc_sockctl_watchtime operand is exceeded, the process that sent the request is forcibly terminated. If you specify 0 for the ipc_sockctl_watchtime operand, the wait time is unlimited.

You can also specify this operand in the RAP-processing listener service definition, the user service default definition, or the user service definition.

The priority of the specified values is (1.>2.>3.):

  1. User service definition or RAP-processing listener service definition
  2. User service default definition
  3. System common definition

ipc_conn_interval=length-of-time-to-wait-until-the-connection-is-established~<unsigned integer>((8-65535))<<8>> (unit: seconds)

Specify the length of time to wait in seconds until the connection is established when data is sent.

Specify the length of time to wait until the system receives the response to the connect() system call that is called in the nonblocking mode.

You can also specify this operand in the user service definition and the user service default definition.

The priority of the specified values is (1.>2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

ipc_send_interval=interval-for-monitoring-data-transmission~<unsigned integer>((5-32767))<<5>> (unit: seconds)

Specify the interval for monitoring data transmission.

You can also specify this operand in the user service definition and the user service default definition.

The priority of the specified values is (1.>2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

ipc_send_count=number-of-times-data-transmission-is-monitored~ <unsigned integer>((1-32767))<<5>>

Specify the number of times data transmission is monitored until data transmission is completed.

The system monitors the data transmission monitoring time for OpenTP1 which is calculated in seconds as follows:

Value specified in the ipc_send_interval operand x Value specified in the ipc_send_count operand

You can also specify this operand in the user service definition and the user service default definition.

The priority of the specified values is (1.>2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

ipc_header_recv_time=length-of-time-to-wait-until-the-communication-control-data-is-received~<unsigned integer>((5-32767))<<10>> (unit: seconds)

Specify the length of time to wait from when OpenTP1 is notified by TCP/IP that data reception is started until OpenTP1 receives the communication control data.

You can also specify this operand in the user service definition and the user service default definition.

The priority of the specified values is (1.>2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

name_notify=Y|N~<<N>>

This operand specifies whether to send a startup notification to the instance of OpenTP1 that starts on the node specified in the all_node operand or the all_node_ex operand when OpenTP1 in the local node starts, or to have OpenTP1 on the local node receive a startup notification from OpenTP1 on another node.

Y
Uses the startup notification facility

N
Does not use the startup notification facility.

Note that the namunavl command operates regardless of the value specified in this operand.

Note:
If multiple OpenTP1s are started in the notification source host or if multiple OpenTP1s start at the same IP address after a system switchover (only 1 LAN board is used), the startup notification facility does not work. Do not specify Y for this operand in such an environment.

all_node_ex="node-name[:port-number]"[,"node-name[:port-number]"...]

Specify the node name of the OpenTP1 system that might communicate using an RPC with a specified destination other than the node names specified in the all_node operand. Also specify the port number that the name server might use as a well-known port number. When OpenTP1 in the local node starts, a startup notification is issued to all running instances of OpenTP1 in the nodes specified in the all_node_ex operand or the all_node operand. By using the startup notification facility, OpenTP1 can manage connection establishment and communicate with more accuracy.

node-name~<identifier of 1 to 255 characters>
Specify the names of all nodes in the OpenTP1 system. The identifier you specify can consist of alphanumeric characters, periods, and hyphens. You can specify a node name specified in /etc/hosts.
If you specify a node name longer than 255 characters, the first 255 characters are used as the node name. Note that when you specify an IP address, make sure that you do not specify an IP address that begins with 127 (example: 127.0.0.1), such as a loopback address.

port-number~<unsigned integer>((5001-65535))<<10000>>
Specify the port number to be used as a well-known port number by the name server.
If you do not specify a port number, the port number of the name service specified in the name_port operand is assumed.

Note:
If the node specified in this operand is also specified in the all_node operand or if the same node is specified more than once in this operand, the KFCA00604-W message is output to the first operand that is analyzed by OpenTP1. In this case, the first node that is analyzed is valid. The priority of analysis is as follows (A>B indicates that A takes precedence over B):
  • When the same node is specified in both the all_node operand and the all_node_ex operand
    all_node operand > all_node_ex operand
  • When the same node is specified more than once in the all_node (all_node_ex) operand
    Node that is specified first > node that is specified later

rpc_server_busy_count=number-of-bundles-that-output-KFCA00356-W-message ~<unsigned integer>((0-32767))<<20>>

The schedule service registers the received service requests in schedule queues. The schedule queue registration processing uses threads to register multiple service requests in schedule queues in parallel. However, if the threads to be used for schedule queue registering run short and the schedule service cannot accept service requests, the system outputs the KFCA00356-W message.

In this operand, specify the number of bundles that output the KFCA00356-W message. The KFCA00356-W message is output when the schedule service cannot accept a service request for the first time or when the number of times the schedule service cannot accept service requests exceeds the value specified in this operand after the KFCA00356-W message is output.

When you specify 0 for this operand, the KFCA00356-W message will not be output regardless of the number of times the schedule service cannot access service requests. When you specify 1, the KFCA00356-W message will be output each time the schedule service fails to accept a service request.

rpc_send_retry_count=number-of-retries-if-an-error-occurs-during-TCP/IP-connection ~<unsigned integer>((0-65535))<<0>>

Even if any of the errors ECONNREFUSED (239), EHOSTUNREACH (242), and ENETUNREACH (229) occurs during a TCP/IP connection when the server sends a response, you may be able to avoid the error by specifying the number of retries in this operand.

When you specify 0 for this operand, no retry is performed even if any of the above errors occurs during a TCP/IP connection.

When you specify 1 to 65535 and if any of the errors occurs during a TCP/IP connection, retries are performed after waiting for the period of time specified in the rpc_send_retry_interval operand.

This operand can also be specified in the user service definition and the user service default definition.

The priorities of specified values are (1.>2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

rpc_send_retry_interval=interval-between-retries-if-an-error-occurs-during-TCP/IP-connection~<unsigned integer>((0-300000))<<0>> (unit: milliseconds)

Even if any of the errors ECONNREFUSED, EHOSTUNREACH, and ENETUNREACH occurs during a TCP/IP connection when the server sends a response, you may be able to avoid the error by specifying the interval in milliseconds between retries in this operand.

When you specify 0 for this operand, no interval is taken between retries to establish a TCP/IP connection. You cannot specify 1 to 19. If any value of 1 to 19 is specified, 20 is assumed.

This operand becomes valid when any value of 1 to 65535 is specified in the rpc_send_retry_count operand.

This operand can also be specified in the user service definition, the user service default definition, and each system service definition.

The priorities of specified values are (1.>2.>3.>4.):

  1. User service definition
  2. User service default definition
  3. Each system service definition
  4. System common definition

thdlock_sleep_time=thread's-waiting-time-if-a-lock-conflict-occurs-among-threads~<unsigned integer>((1-32767))<<15>> (unit: milliseconds)

Specify the thread's waiting time in milliseconds when the lock control function that the process under OpenTP1 internally uses cannot acquire a lock because a lock conflict occurs among threads.

If you specify a value smaller than the default (15), the select system call is issued more frequently, causing the CPU utilization to increase.

Note:
When more than one thread attempts to lock a resource at the same time, the threads other than the one that has locked the resource wait until the resource is unlocked. When the threads wait, they issue the OS select system call according to the value specified in this operand. Note that the actual wait time might be longer than the value specified in this operand because the wait time precision for the select system call differs depending on the OS or machine environment.
The following table shows sample results of wait time measurement for this operand in different OSs.
Note that the values in the table might be different in some machine environments due to factors such as the OS version and whether patches have been applied. For details about the wait time precision for the select system call, consult the OS specifications.
OS name Version thdlock_sleep_time operand value Wait time
AIX 5L V5.3 Specified value Specified value
Linux 5 (x86)
5 (IPF) (64-bit architecture)
Specified value Specified value + about one millisecond
HP-UX 11i V2 (IPF)
11i V3 (PA-RISC)
1-9 About 10 milliseconds
10-19 About 20 milliseconds
Solaris 8 1-9 About 10 milliseconds
10-19 About 20 milliseconds
Windows Windows Server 2003 1-15 About 16 milliseconds
16-31 About 31 milliseconds

This operand can also be specified in each system service definition.

The priority of specified values is (1.>2.):

  1. Each system service definition
  2. System common definition

ipc_listen_sockbufset=Y|N ~<<N>>

Specify whether to set the TCP/IP send and receive buffer sizes for the listen socket that OpenTP1 uses for inter-process communication during generation of the socket as specified in the ipc_sendbuf_size and ipc_recvbuf_size operands.

Y
Sets the TCP/IP send and receive buffer sizes for the listen socket.

N
Does not set the TCP/IP send and receive buffer sizes for the listen socket.

The TCP/IP send and receive buffer sizes specified in the ipc_sendbuf_size and ipc_recvbuf_size operands are applied after the OpenTP1 process receives a connection establishment request and establishes a connection. Because the buffer sizes change after a connection is established, differences in buffer size between the connection source and destination might cause a communication delay.

If TP1/Client communicates with TP1/Server Base on the same node, Hitachi recommends that you specify Y in this operand.

You can also specify this operand in the user service definition and user service default definition.

The priority of specified values is as follows (1.> 2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

ipc_recvbuf_size=receive-buffer-size-of-TCP/IP~<unsigned integer> ((8192-1048576))<<8192>> (unit: bytes)

Specify the size of the receive buffer of TCP/IP allocated for each connection. When using devices with high speed communication or using a large MTU, the performance can be improved if the value in this operand is increased.

Notes:
TCP returns a delivery acknowledge (ACK) packet in response to the received data. If the length of the received data is much smaller than the size of the receive buffer, TCP may not return ACK immediately (delayed ACK).
If a great value is specified in this operand and a small amount of data is exchanged, the performance may be degraded due to delayed ACK. For details about delayed ACK, see the TCP/IP documentation.
Make sure that the value of this operand does not exceed the TCP/IP receive buffer size that can be specified in the OS. Note that the TCP/IP receive buffer size specified in this operand is not applied for the global archive journal facility. When you use the facility, specify the TCP/IP send-and-receive buffer size in the following operands:
  • The jnl_arc_ipc_buff_size operand in the journal service definition
  • The jnl_arc_ipc_buff_size operand in the global archive journal service definition

This operand can also be specified in the user service definition, the user service default definition, and each system service definition.

The priorities of specified values are:

For a system server (1.>2.):
  1. Each system service definition
  2. System common definition

For a user server (1.>2.>3.)
  1. User service definition
  2. User service default definition
  3. System common definition

ipc_sendbuf_size=send-buffer-size-of-TCP/IP~<unsigned integer> ((8192-1048576))<<8192>> (unit: bytes)

Specify the size of the send buffer of TCP/IP allocated for each connection. When using devices with high speed communication or using a large MTU, the performance can be improved if the value in this operand is increased.

Notes:
Make sure that the value of this operand does not exceed the TCP/IP send buffer size that can be specified in the OS. Note that the TCP/IP send buffer size specified in this operand is not applied for the global archive journal facility. When you use the facility, specify the TCP/IP send-and-receive buffer size in the following operands:
  • The jnl_arc_ipc_buff_size operand in the journal service definition
  • The jnl_arc_ipc_buff_size operand in the global archive journal service definition

This operand can also be specified in the user service definition, the user service default definition, and each system service definition.

The priorities of specified values are:

For a system server (1.>2.):
  1. Each system service definition
  2. System common definition

For a user server (1.>2.>3.)
  1. User service definition
  2. User service default definition
  3. System common definition

rpc_router_retry_count=number-of-retries-if-ENOBUFS-or-ENOMEM-occurs~ <unsigned integer>((0-65535))<<30>>

Specify the number of times message reception (including issuance of the accept system call) is retried if ENOBUFS occurs for the accept system call internally issued by TP1/Server Base or if ENOMEM occurs during message reception.

rpc_router_retry_interval=interval-between-retries-if-ENOBUFS-or-ENOMEM-occurs~<unsigned integer>((0-3600000))<<0>>(unit: milliseconds)

Specify the interval for retrying message reception (including issuance of the accept system call) if ENOBUFS occurs for the accept system call internally issued by TP1/Server Base or if ENOMEM occurs during message reception. If you specify 0 in this operand, message reception is retried with no interval. If any value of 1 to 9 is specified, 10 is assumed.

ipc_backlog_count=length-of-queue-storing-connection-establishment-requests~<unsigned integer>((0-4096))<<0>>

Specify the length of the queue storing connection establishment requests. (Number of backlogged listen system calls)

The actual number to be specified as the number of backlogged listen system calls when 0 (default) is specified depends on the OS. For details, see the Release Notes.

The actual length of the queue may be longer than the specified value.

The upper and lower limits on the length vary depending on the OS. If the length of the queue is restricted with the upper and lower limits by the OS, the specified value may not be valid. For details about the queue storing connection establishment requests, see your OS or TCP/IP documentation.

This operand can also be specified in the user service definition and the user service default definition.

The priorities of specified values are (1.>2.>3.):

  1. User service definition
  2. User service default definition
  3. System common definition

statistics=Y|N~<<N>>

Specify whether to acquire system statistics and place them in shared memory.

Y
Acquires system statistics and places them in shared memory.

N
Does not acquire system statistics and does not place them in shared memory.

To view the acquired system statistics, use the dcstats command to output the system statistics to the journal file or use the dcreport command to output the system statistics to the standard output.

The system statistics to be acquired and placed in shared memory are the same as the statistics that are acquired when the -s option is specified in the dcstats command.

The acquired system statistics are accumulated since the start of OpenTP1 and may overflow the memory. If you run the system for many hours, use the dcstats command to output the system statistics to the journal file or specify the -r option in the dcreport command to periodically reset the value.

name_domain_file_use=Y|N~<<N>>

Select the domain configuration to be enabled when OpenTP1 is started or restarted.

For details on how to specify a definition file when using the namchgfl command to change the domain configuration, and for relevant notes, see the manual OpenTP1 Operation.

Y
Enables the domain configuration specified in domain definition files.

N
Enables the domain configuration specified in the system common definition.

There are three domain definition files. One is used for specifying all_node, another is used for specifying all_node_ex, and the third is used for specifying a preferred node. The method of specifying a definition file for a preferred node is the same as that used for specifying all_node or all_node_ex. The file names are arbitrary. To enable this operand, place these domain definition files in their appropriate directories.

Domain definition file for specifying all_node:
The $DCCONFPATH/dcnamnd directory

Domain definition file for specifying all_node_ex:
The $DCCONFPATH/dcnamndex directory

Definition file for specifying a preferred node:
The $DCCONFPATH/dcnampr directory

If a node name or port number in these files is invalid, error message KFCA00656-E (invalid node name), KFCA00657-E (invalid port number), or KFCA00666-E (host undefined) is output, and startup of OpenTP1 fails.

If the node specified in the preferred node definition file is not specified in the domain definition file for all_node, error message KFCA00603-W (undefined in all_node) is output and OpenTP1 is started by ignoring the specification of the preferred node. For a node that is correctly defined in another line within the same file, the specification of a preferred node is invalid.

If there is more than one domain definition file in one directory, a single domain (OpenTP1 system) is created using the definitions in all of the domain definition files. In the following cases, an OpenTP1 system is created as a domain consisting of only the local node:

OpenTP1 might not operate correctly if the setting of this operand is changed while OpenTP1 is operating.

If Y is specified, the namndchg command returns an error. If N is specified, the namchgfl command returns an error.

The following table explains the differences between specifying Y and N in the name_domain_file_use operand.

OpenTP1 status Value of the name_domain_file_use operand
Y N
Normal startup The command creates an OpenTP1 system, ignoring the all_node and all_node_ex operands of the system common definition. The command creates an OpenTP1 system on the basis of the all_node and all_node_ex operands of the system common definition.
Restart The command creates an OpenTP1 system, ignoring the all_node and all_node_ex operands that were used when the restart occurred. The command creates an OpenTP1 system on the basis of the all_node and all_node_ex operands that were used when the restart occurred.
Operating The domain configuration can be changed by using the namchgfl command. The command reconfigures the domain on the basis of the domain definition files existing when the command is executed. The domain configuration cannot be changed by using the namchgfl command. The value N set in the name_domain_file_use operand when OpenTP1 was started causes an environment error, and the command returns an error.
The domain configuration cannot be changed by using the namndchg command. The value Y set in the name_domain_file_use operand when OpenTP1 was started causes an environment error, and the command returns an error. The domain configuration can be changed by using the namndchg command. The command reconfigures the domain on the basis of the settings of the all_node and all_node_ex operands when the command is executed.

all_node_extend_number=maximum-number-of-nodes-after-domain-reconfiguration~<unsigned integer> ((0-65535)) <<64>>

Specify the maximum number of nodes that make up the domain when you use the namndchg or namchgfl command to change the domain configuration.

If you use the namndchg command, specify the maximum number of nodes to be specified in the all_node operand of the system common definition. If you use the namchgfl command, specify the maximum number of nodes to be specified in the all_node operand in the domain definition files.

The command allocates shared memory area for the number of nodes calculated as follows:

The number of nodes specified in this operand plus the value of all_node operand in the system common definition or plus the number of nodes specified in the domain definition file used to specify the all_node operand.

If the number of nodes you specify in the system common definition or that domain definition file is greater than the value of the all_node_extend_number operand, the namndchg or namchgfl command returns an error, and outputs messages KFCA00616-E and KFCA00654-E. If the command returns an error, the domain configuration is not changed.

all_node_ex_extend_number=maximum-number-of-nodes-after-domain-reconfiguration-by-using-domain-definition-files~<unsigned integer> ((0-65535)) <<64>>

Specify the maximum number of nodes that make up the domain when you use the namchgfl command with the -e option to change the domain configuration.

In this operand, specify the maximum number of nodes that can be specified in the all_node_ex operand in the domain definition files.

The command allocates shared memory area for the number of nodes calculated as follows:

The number of nodes specified in this operand plus the number of nodes specified in the domain definition file used to specify the all_node_ex operand.

If the number of nodes specified in that domain definition file is greater than the value specified in this operand, the namchgfl command returns an error, and outputs message KFCA00655-E. If the command returns an error, the domain configuration is not changed.

prc_current_work_path=path-name-of-the-directory-under-which-the-current-working-directory-is-created~<path name> <<$DCDIR>>

Specify the absolute path name for the directory used to create the current working directory that OpenTP1 processes will use. The actual current working directory for a process is created as follows:

path-specified-in-this-operand/tmp/home/process-specific-directory

If the path name specified in this operand is incorrect or if this operand is not specified, the current working directory is created under $DCDIR. That is, the actual current working directory for a process is created as follows:

$DCDIR/tmp/home/process-specific-directory

You can use a maximum of 50 characters to specify the path name.

If the tmp directory exists when OpenTP1 is started or the dcreset command is executed, the existing tmp directory is deleted and a new tmp directory is created. If core files are contained in the tmp directory specified by this operand, they will be saved in $DCDIR/spool/save or the directory specified in the prc_coresave_path operand of the process service definition.

The following permissions must be set for the directory specified in this operand:

If you use multiple OpenTP1 systems on the same machine, do not specify the same directory in the prc_current_work_path operands of two or more OpenTP1 systems. If the specified directory is already being used by another OpenTP1 system, your OpenTP1 system will use the default directory, without using the specified directory.

If you want to change the value of this operand, first terminate OpenTP1 normally, and then change the value of the operand. You will then need to execute the dcreset command.

After the value of the operand is changed, directories created before the change may remain in the previously specified directory. There are no problems caused by deleting these directories. Before deleting them, terminate OpenTP1 normally.

Hitachi recommends that you set this operand and the prc_coresave_path operand of the process service definition on the same partition.

When you specify this operand, do not use the online tester facility.

rpc_max_message_size=maximum-size-of-a-message-sent-or-received-by-an-RPC~<unsigned integer> ((1-8)) <<1>> (units: MB)

Specify the maximum length of a message that can be sent or received by an RPC call.

If you specify this operand, make sure that the value of this operand is set for all nodes specified in the all_node operand of the system common definition. If different values are set, an RPC call (dc_rpc_call or dc_rpc_call_to) may return a DCRPCER_NET_DOWN error when the inter-node load-balancing facility is executed at the destination node.

Note the following points when you send a message larger than 1 MB by specifying this operand:

If this operand is specified, the maximum length of a message that can be sent using an RPC call changes from the DCRPC_MAX_MESSAGE_SIZE value (1 MB) to the value specified in this operand. However, if you specify no value or 1 in the rpc_max_message_size operand, the maximum message length is set to the DCRPC_MAX_MESSAGE_SIZE value (1 MB).

Be careful if you specify 2 or a greater value in this operand in an environment that is operating without this operand specified. In this situation, if you attempt to send a message larger than 1 MB, a memory shortage may occur. Before you add this operand, consider the amount of installed memory and the maximum amount of memory that the process can use. You can obtain the maximum amount of memory required when the schedule service from the following formula:

Maximum required memory = Value specified in the rpc_max_message_size operand x 64 x 2 (units: MB)

If you acquire an RPC trace after sending a message larger than 1 MB by specifying 2 or a greater value in this operand, the amount of memory used increases. Acquiring the RPC trace may take some time.

OpenTP1 may not operate correctly if you use any of the following operations and functions when this operand is specified:

To send a message larger than 1 MB to a CUP on a one-way basis by specifying this operand, use the TP1/Client version that can receive messages larger than 1 MB.

When this operand is specified and a data compression function is used, the command determines the message size from the in_len value of the RPC call (dc_rpc_call or dc_rpc_call_to). The command assumes the message to be larger than 1 MB if the in_len value is larger than 1 MB, even though the length of the compressed message is not larger than 1 MB.

uap_trace_file_put=Y | N

~<<N>>

Specify whether to acquire the trace information of a UAP trace in a file.

Y
Trace information is acquired in the UAP trace data file.
If the trace information cannot be acquired in a file, it is acquired in a process-specific area.

N
Trace information is acquired in a process-specific area.

When Y is specified, a maximum of six generations of backup files for the UAP trace data file are acquired by each server when the user server fails or restarts after termination of OpenTP1. Three generations of backup files are acquired when the applicable server terminates normally, and also during abnormal termination accompanied by a core file output. Backup files are stored in the core file storage destination specified in the prc_coresave_path operand of the process service definition.

dcstart_wakeup_retry_count=number-of-retries-for-OpenTP1-startup-notification~<unsigned integer> ((0-60))<<0>>

Specify the maximum number of times OpenTP1 startup notification is retried if notification fails.

When the dcstart command is used to start OpenTP1, the process server is notified that OpenTP1 has started. If notification fails, the dcstart command automatically retries notification. This operand specifies the maximum number of times notification is retried.

If this operand is omitted or if 0 is specified in the operand, the command does not retry notification.

dcstart_wakeup_retry_interval=retry-interval-for-OpenTP1-startup-notification~<unsigned integer> ((1-60))<<10>> (units: seconds)

Specify the interval for retrying OpenTP1 startup notification if notification fails.

This operand takes effect when 1 or a greater value is specified in the dcstart_wakeup_retry_count operand.

The retry interval is the period during which the command waits after failing to notify the process server of startup before it attempts notification again.

nam_prf_trace_level=NAM-event-trace-acquisition-level ~((00000000-00000007)) <<00000003>>

Specify the acquisition level of the trace information related to the name service (NAM event trace) of the performance verification trace information. The range of event IDs for the NAM event trace is from 0xf000 to 0xffff. For details about event IDs, see the manual OpenTP1 Operation. Note that if any value other than the following is specified, 00000003 is assumed.

00000000:
A NAM event trace is not acquired.

00000001:
A NAM event trace related to the registration and deletion of service group information or other such events (event IDs 0xf1000 to 0xf1ff) is acquired.

00000002:
A NAM event trace related to communication between the name server (namd) and remote node (event IDs 0xf000 to 0xf0ff) is acquired.

00000003:
A NAM event trace that includes both 00000001 and 00000002 is acquired.

00000004:
A NAM event trace related to communication between the name server (namd) and the processes of UAPs and operation commands is acquired (event IDs 0xf200 to 0xf2ff).

00000005:
A NAM event trace that includes both 00000001 and 00000004 is acquired.

00000006:
A NAM event trace that includes both 00000002 and 00000004 is acquired.

00000007:
A complete NAM event trace (NAM event trace information for 00000001, 00000002, and 00000004) is acquired.

You can use the prfget command to export the acquired trace to a file or use the prfed command to edit and output the acquired trace. For details about the prfget and prfed commands, see the manual OpenTP1 Operation.

This operand requires installation of TP1/Extension 1. If this operand is specified when TP1/Extension 1 has not been installed, operation cannot be guaranteed.

fil_prf_trace_option=0|1

~<<1>>

Specify whether to acquire a FIL event trace.

0
A FIL event trace is not acquired.

1
If processing of a request to access an OpenTP1 file takes longer than the time specified in the fil_prf_trace_delay_time operand, an FIL event trace is acquired as delay information.

Do not specify a value other than 0 or 1 for this operand. If such a value is specified, the operation is not guaranteed.

A FIL event trace is acquired for event IDs 0x6805, 0x6807, 0x6905, 0x6907, and 0x6909.

To output or edit and output the acquired trace to a file, use the prfget or prfed command. For details about event IDs or these commands, see the manual OpenTP1 Operation.

Use this operand only when TP1/Extension 1 is installed. If TP1/Extension 1 is not installed, the operation is not guaranteed.

fil_prf_trace_delay_time=file-access-processing-time-threshold-which-becomes-FIL-event-trace-acquisition-condition

~<unsigned integer> ((1-65535))<<10>> (Unit: seconds)

Specify the file access processing time threshold that becomes the FIL event trace acquisition condition.

Note:
The time precision for monitoring the threshold is in seconds. Consequently, depending on the timing, a FIL event trace may be acquired within the file access processing time that is shorter than the value specified in this operand. Note that as the threshold becomes smaller, it is more prone to be affected by error.

jnl_prf_event_trace_level=acquisition-level-for-JNL-performance-verification-trace

~((00000000-00000002)) <<00000001>>

Specify the acquisition level for the JNL performance verification trace for acquiring performance verification trace information. The event IDs for the JNL performance verification trace are from 0xc000 to 0xcfff. For details about event IDs, see the manual OpenTP1 Operation. When a value other than those listed below is specified, 00000001 is assumed.

00000000
A JNL performance verification trace is not acquired.

00000001
A JNL performance verification trace (event IDs 0xc202, 0xc203, 0xc401, and 0xc402) is acquired.

00000002
A JNL performance verification trace (event IDs 0xc001-0xc402) is acquired.

If 00000002 is specified as the acquisition level, all trace information can be acquired. However, since doing so adversely impacts online performance, we recommend that you use the default output level except during debugging.

To output or edit and output the acquired trace to a file, use the prfget or prfed command. For details about event IDs or these commands, see the manual OpenTP1 Operation.

The use of this operand assumes that TP1/Extension 1 is installed. If TP1/Extension 1 is not installed, the operation is not guaranteed.

jnl_fileless_option=Y|N~<<N>>

Specify whether to use journal fileless mode for the applicable OpenTP1 nodes.

Y
Journal fileless mode is used.

N
Journal fileless mode is not used.

In journal fileless mode, the following facilities cannot be used:

Although use of the statistics acquisition facility does not result in an error, no statistics are acquired.

Using any of the above facilities except the statistics acquisition facility causes OpenTP1 startup processing to fail.

Because the transaction facility is unavailable, OpenTP1 assumes that the atomic_update operand in the user service definition or user service default definition has been set to N even when Y is set.

The XA linkage facility is also unavailable because the transaction facility is unavailable. For this reason, you do not need to use the trnlnkrm command to register the resource manager in OpenTP1.

For details about the facilities and commands that cannot be used in journal fileless mode, see the manual OpenTP1 Operation.

watch_time=maximum-response-waiting-time~<unsigned integer> ((0-65535)) <<180>> (Units: 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.

This operand can also be specified in some system service definitions other than the system common definition. The values specified in system service definitions prevail over those specified in the system common definition.

Use the default for this operand.

When this operand is specified only in the system common definition, it becomes valid for the entire OpenTP1 system. Therefore, we recommend that you do not change the operand unless special tuning is necessary. Even if some tuning is necessary, settings for user services should be specified in the user service default definition.

If a value that is much greater or smaller than the default is specified, a failure may occur causing OpenTP1 to go down.

command format

The command format is described on the next page.

putenv format

LANG LANG-setting~<character string>

Assign environment variable LANG. The LANG setting must be a language type defined by the OS. If this variable is not assigned, or if an invalid value is assigned, the system assumes the English language.