The temporary closing request monitoring facility lets you regularly check whether or not a temporary closing request has been received. This facility allows reception of a temporary closing request even when the SPP or MHP of OpenTP1 is waiting to receive a service request.

In temporary closing, a connection established between processes is closed after a necessary interaction between the processes is complete. The interaction consists of one process sending a temporary closing request, and another process receiving the request and returning a response.

That is, when the number of sockets used by a process has reached the maximum^#, if the process sends a temporary closing request, the connection cannot be closed until the other process receives the request and returns a response.

SPPs and MHPs of OpenTP1 use a msgrcv system call while waiting for an incoming service request. Once an SPP or MHP begins to wait as the result of the system call, the connection with the other process cannot be closed because the SPP or MHP cannot receive a temporary closing request from the other process.

The temporary closing request monitoring facility is effective when the number of sockets used by a process has reached the maximum^# and the process has sent a temporary closing request. In this situation, the facility allows the other process to receive the request and to return a response, even if the other process is waiting for a service request as the result of an msgrcv system call.

You can specify the following operands in the user service definition and user service default definition:

set polling_control_data = Whether to check the arrival of a socket reuse instruction (temporary closing request)

set thread_yield_interval = Interval time to wait for a trigger to receive a socket reuse instruction

#

The maximum number of file descriptors for sockets is specified in the max_socket_descriptors operand.