set max_socket_descriptors=maximum-number-of-file-descriptors-for- socket set max_open_fds=maximum-number-of-files-accessed-by-MCF- communication-process set thdlock_sleep_time=thread's-waiting-time-if-a-lock-conflict-occurs- among-threads [set mcf_prf_trace_level=acquisition-level-for-MCF-performance verification-trace-information]

The system service common information definition defines the information common to MCF communication services. The OpenTP1 product provides a file that contains the values of this definition set to defaults. For the following operands, use a text editor to modify the values as required. For other operands, do not modify the values.

max_socket_descriptors=maximum-number-of-file-descriptors-for-socket ~<unsigned integer>((64-2047))

Specify the maximum number of file descriptors that each MCF communication process uses for the socket. The processes controlled by OpenTP1 exchange information to each other via the TCP/IP communication using the socket between the system server and the user server. Therefore, you need to change the maximum number of file descriptors for the socket, according to the number of the UAP processes that run concurrently.

The following shows the formula to calculate the maximum number of file descriptors for the socket that an MCF communication process uses. Calculate the maximum number of file descriptors for each MCF communication process. If the largest result is larger than 64, specify the largest result. If the largest result is 64 or smaller, specify 64.

Maximum number of file descriptors for the socket =  (A + B + C) / 0.8 

Where,

A: Number of UAP processes that request the MCF communication process to send a message^#1

B: Number of system service processes^#2

C: Number of operation commands that concurrently send a request to the MCF communication process

: The value enclosed in these symbols is rounded up to the nearest whole number.

#1: This number includes the number of UAP processes that request application startup servers to start applications.

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

max_open_fds=maximum-number-of-files-accessed-by-MCF-communication-process~<unsigned integer> ((100-2016))<<500>>

Specify the maximum number of files that each MCF communication process accesses.

MCF communication processes also use file descriptors to send or receive messages. If file descriptors are insufficient, the connection may not be established. Therefore, you need to specify the number of enough file descriptors.

The following shows the formula for calculating the maximum number of file descriptors that an MCF communication process uses. Calculate the number of file descriptors for each MCF communication process. If the largest result is larger than 500, specify the largest result. If the largest result is 500 or smaller, specify 500.

If the number of files to be accessed exceeds the value specified in this operand, the excess files are treated as files for which the file descriptors for sockets are used. Note that, in this case, the actual maximum number of file descriptors for sockets is the value of the max_socket_descriptors operand minus the excess value for the max_open_fds operand.

Maximum number of file descriptors = (Number of file descriptors used for the protocol controller^#1) + 30^#2

#1

This value differs depending on the protocol controller in use:

Protocol controller	Number of file descriptors used
TP1/NET/HDLC	Number of connections
TP1/NET/HNA-NIF	Number of subconnections
TP1/NET/HNA-560/20	Number of PLUs in the local system
Other protocol controllers	Number of connections x 2

#2

Maximum number of definition files and other files that the MCF communication process handles

Note that one process can use up to 2048 file descriptors. Therefore, you must set this operand to a value that satisfies the following condition:

(Value of this operand + Value of the max_socket_descriptors operand in the same definition) 2048

If you specify a value that does not satisfy this condition, this operand is forcibly set to the following value:

2048 - Value of the max_socket_descriptors operand in the same definition

thdlock_sleep_time=thread's-waiting-time-if-a-lock-conflict-occurs-among-threads ~<unsigned integer> ((1-32767)) <<15>> (units: 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 CPU utilization to increase.

Note:

If 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 (IPF64)	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

If this definition value is omitted, the value in the system common definition is assumed.

mcf_prf_trace_level=acquisition-level-for-MCF-performance-verification-trace-information

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

Specify the acquisition level for the MCF performance verification trace information. To acquire the MCF performance verification trace, specify Y in the prf_trace operand of the system common definition or omit the specification.

00000000

MCF performance verification trace information is not acquired.

00000001

MCF performance verification trace information (event IDs 0xa000-0xa0ff) is acquired. For details about event IDs, see the manual OpenTP1 Operation.

If the operand specification is invalid, OpenTP1 abnormally terminates during startup.

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