When to shut down a UAP which has ended abnormally is determined by the monitoring time and the abnormal termination count.

If the TP1/Server Base is in use, the OpenTP1 shuts down a UAP when the UAP has ended abnormally three times during a period of time equal to or shorter than the monitoring time specified in the system definition. If the TP1/LiNK is in use, the OpenTP1 shuts down a UAP when it terminates abnormally for the first time. Time monitoring for shutdown is not used.

If a UAP has terminated abnormally twice or less during the monitoring time, the OpenTP1 restarts the process of the OpenTP1.

Time monitoring begins when the first abnormal termination occurs. Even if the number of abnormal terminations is two or less, abnormal termination counting restarts when the second abnormal termination occurs.

The following figure shows the relationship between the monitoring time and abnormal termination count.

Figure A-6 Relationship between monitoring time and abnormal termination count

UAPs may be shut down at a time for one service group or one service. If shutdown for each service is specified and even when a UAP terminates abnormally three times during the monitoring time, only UAPs for the pertinent service are shut down. This means that other services belonging to the same service group can continue.

Shutdown for each service can be specified only for queue-receiving SPPs. Shutdown for each service group can be specified only when the basic facility of the OpenTP1 is the TP1/Server Base. For TP1/LiNK SPPs, only shutdown for each service can be specified.

The following user service definitions relate to UAP shutdown. These user service definitions can be specified only when the basic facility of the OpenTP1 is the TP1/Server Base. When a UAP terminates abnormally, SPPs under the TP1/LiNK are immediately shut down if they have been working for the service involved in the shutdown.

• hold operand (valid for SPPs, and MHPs)
  Specifies whether to effect shutdown immediately or after time monitoring when a UAP ends abnormally. Assign Y if you want immediate shutdown or N if you want shutdown with time monitoring.
  
• service_hold operand (valid for SPPs)
  Specifies whether to shut down UAPs for each service group or each service. Assign N if you want shutdown for each service group or Y if you want shutdown for each service.
  
• term_watch_time operand (valid for SPPs, and MHPs)
  Specifies a shutdown monitoring time for each service group if shutdown with time monitoring is in effect. The value assigned to the term_watch_time operand is ignored if the service_term _watch_time operand is specified.
  
• service_term_watch_time operand (valid for SPPs)
  Specifies a shutdown monitoring time for each service if shutdown with time monitoring is in effect. If this operand is specified, the value assigned to the term_watch_time operand is ignored.
  

Combinations of values assigned to the operands related to shutdown determine whether a UAP which has ended abnormally will be restarted or shut down. For details about the relationship between operand value combinations and the execution of shutdown, see the descriptions of the operands.