Timer service definition

tim_watch_count=maximum-time-check-service-count~<unsigned integer> ((0-65535)) <<128>>

Specify the maximum number of time check services. An OpenTP1 system monitors the processing time of a transaction branch and the time of an MHP, as well as monitoring of the execution time of a service function.

Use the following formula for calculating the maximum number of time check services:

Maximum number of time check services = A + B + C + D

A: Number of transaction branches that are concurrently started: This is the value of the trn_tran_process_count operand in the transaction service definition.

B: Number of MHP processes for which monitoring of a timeout for non-transaction MHPs is specified

This is the number of processes concurrently executing MHPs that satisfy both of the following conditions:

The trnmode operand is set to nontrn by using the -n option in the application attribute definition (mcfaalcap).
The ntmetim operand is set to a value other than 0 by using the -v option in the application attribute definition (mcfaalcap) or the -u option in the UAP common definition (mcfmuap).

C: Number of SPP processes for which monitoring of the service function execution time is specified: This is the number of SPP processes affected by the service_expiration_time operand in the user service definition or user service default definition. When you want to run SPPs in a multi-server environment, add the value of the parallel_count operand in the user service definition or user service default definition.

D: Number of processes for which monitoring of the time limit for completing a transaction is specified

This is the total of the following numbers, each of which is the number of processes affected by the trn_completion_limit_time operand^#:

Number of SUP, SPP, and MHP processes that execute the transaction. When you want to run SPPs and MHPs in a multi-server environment, add the value of the parallel_count operand in the user service definition or user service default definition.
Number of transactional RPC executing processes. Add the value of the parallel_count operand in the client service definition.
Number of CUP executing processes that execute the transaction. Add the value of the cup_parallel_count operand in the client service definition.
Number of RAP-processing servers that execute the transaction. When you want to run the RAP-processing servers in a multi-server environment, add the value of the rap_parallel_server operand in the RAP-processing listener service definition.

#: The trn_completion_limit_time operand in the user service definition, user service default definition, RAP-processing listener service definition, client service definition, or transaction service definition

Specify 0 if there are no transaction services, MCFs or SPPs that specify monitoring of service function execution time within the same node. In this case the timer service performs no time check service.

Request of a time check service in excess of the value specified here disables the timer service. If the timer service cannot monitor the processing time of a transaction branch, OpenTP1 returns error to the API that requests to start the transaction. If the timer service cannot monitor the execution time of a service function, OpenTP1 outputs the error message and continues processing. If the timer service cannot monitor the service function execution time or the time limit for completing a transaction, OpenTP1 outputs an error message and continues processing.