When there is a stopped unit, you can execute system switchover for the system manager unit by specifying the following operands:

• pd_start_level = 1
• pd_start_skip_unit = unit-identifier-of-stopped-unit
• pd_reduced_check_time = startup-time-limit

Table 25-56 shows how to specify these operands and the actions HiRDB takes during system switchover.

Table 25-56 Operands related to reduced activation and actions HiRDB takes during system switchover

Condition		Actions HiRDB takes when system switchover occurs for the system manager unit
pd_start_level specification value	pd_start_skip_unit specification
0 (default value)		If there is a stopped unit, system switchover for the system manager unit fails.
1	Not specified	Even if there is a stopped unit, system switchover for the system manager unit executes. However, a wait occurs for receipt of a startup processing completion notice from each unit. The startup time limit is specified in the pd_reduced_check_time operand (default value is 20 minutes).
	Specified	Even if there is a stopped unit, system switchover for the system manager unit executes. No checking wait time occurs.

Reference note

• When system switchover for the system manager unit occurs, a check is made for whether or not front-end servers and back-end servers are active at the system manager unit at the switching destination. This is why a wait occurs for receipt of a startup processing completion notice from each unit. If system switchover occurs while there are units that are stopped, the operating status of such units cannot be determined; as a result, system switchover may fail or take a long time to be completed.
• If any of the following conditions is not satisfied, system switchover for the system manager unit fails:
  A front-end server is active
  A back-end server is active
  A dictionary server is active
  

When you specify the pd_start_skip_unit operand, you must terminate HiRDB. Therefore, you should consider the other method if your system must remain active around the clock.