cannot start scheduler. reason code=aa...aa

An error occurred during scheduler normal startup or restart processing.

aa...aa: Reason code indicating the contents of the error. (Up to ten numerals)

The following table shows the reason codes and countermeasures.

S: Stops scheduler normal startup or restart processing.

Countermeasure: Take countermeasures according to the reason code and restart the scheduler.

Reason code	Meaning	Countermeasures
1	Shared memory cannot be reserved.	Check the size of the statically shared memory specified in the system environment definition. Then, restart OpenTP1.
2	Definition analysis error	Take countermeasures according to the error message, if any, that was output before this message, then restart the scheduler.
3	Insufficient process-unique memory	Reduce the value specified for scd_hold_recovery_count in the schedule service definition. If the problem persists, abandon attempting to keep the server/service in the shutdown state and specify 0 for scd_hold_recovery_count.
4	Status file access error	Check the value of the scd_hold_recovery_count operand in the schedule service definition, take countermeasures, and then restart OpenTP1. If the value of the scd_hold_recovery_count operand is correct, take countermeasures according to the error message, if any, that was output before this message. Then, restart the scheduler.
5	Communication error	Take countermeasures according to the previous error message.
6	Queue information file access error	Failed to create a queue information file ($DCDIR/spool/scdqid1, scdqid2). The access authority under $DCDIR, including the access authority to the queue information file, may have been changed. Check whether the access authority has changed. If changed, use the dcsetup command to recreate the structure under $DCDIR. If the error still recurs, contact maintenance personnel.
8	Port number duplicated	Stop the process started by the port number specified in scd_port in the schedule service definition, or re-define scd_port. Then, restart OpenTP1.
10	Invalid schedule buffer group specified	Check the value of scdbufgrp in the schedule service definition, and then restart OpenTP1.
11	The number of servers for sharing the schedule buffer group exceeds the limit.	Check the value of scdbufgrp in the schedule service definition. Then, restart OpenTP1.
21	Failed to start multi-scheduler daemons.	Take countermeasures according to the error message, if any, that was output before this message. Then, restart the OpenTP1 system.
22	Invalid multi-scheduler definition.	The scdmulti definition command in the schedule service definition is invalid. The possible causes of the definition error are: The specified port number is invalid (for example, another process already uses the port number). More than one scdmulti definition command that does not include the -g option is specified. The -g options in some scdmulti definition commands specify the same name. Correct the specification of the scdmulti definition commands and then restart the OpenTP1 system.