server shutdown info failed to be cataloged; cannot hold server or service in shutdown state after full-scale system recovery. server: aa...aa, reason code=bb...bb

Although the server or service is placed in the shutdown state, writing of the server shutdown information into the file failed. This prevents the server from being kept in the shutdown state after the next full-scale system recovery.

aa...aa: Name of the server which failed in writing the shutdown information. (Up to eight alphanumerics)

bb...bb: Reason code indicating the contents of the error. (Up to ten numerals) The table below shows the reason codes and countermeasures.

S: Continues processing.

O: If the server or service must be kept in the shutdown state after a full-scale system recovery, enter the scdhold command to place it in the shutdown state after the OpenTP1 administrator's action.

Countermeasure: Follow the reason code.

Reason code	Meaning	Countermeasures
1	Status file access error	Take countermeasures according to the error message, if any, that was output before this message. If the server must be kept in the shutdown state, enter the dcsvstop, dcsvstart, and scdhold commands in this order to return it to the shutdown state.
2	Number of shutdown servers/services exceeded	The total number of servers and services to be held in the shutdown state, as specified in the scd_hold_recovery_ count operand of the schedule service definition, is too few. If the shutdown state must be held, check and correct the schedule service definition, the user service definition, and the user service default definition, then restart OpenTP1.
3	Insufficient memory	Apply one of the following countermeasures according to the operating state: (1)Specify service_hold=N in the user service definition. (2)Specify hold_recovery=N in the user service definition. (3)For the number of services per server, set a value of 64 or less.