cannot start server aa...aa. reason code=bb...bb

An error occurred while starting the server.

aa...aa: Name of the server that cannot be started. (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: Stops server startup processing.

O: If the server must be started, enter the dcsvstart command to start it after the OpenTP1 administrator's action.

Countermeasure: Follow the reason code.

Reason code	Meaning	Countermeasures
1	Server or service group is already started.	Specified server or service group is already started. For specification error, specify the correct server name or service group name (user service definition) and enter the dcsvstart command.
2	Timing error	The scheduler is not started or is being terminated. Restart the system and enter the dcsvstart command.
3	Invalid server count	Number of servers exceeds the limit for operating under the scheduler. Check scd_server_count in the schedule service definition. Then, enter the dcsvstart command.
4	Communication error	Take countermeasures according to the error message, if any, that was output before this message. Then, enter the dcsvstart command.
5	Program version unmatched	Check and correct the versions of OpenTP1 libraries. Then, enter the dcsvstart command.
6	Resident process cannot be started.	Take corrective action as follows: (1)Check and correct the number of processes specified for the prc_process_count operand in the process service definition. (2)Check and correct the number of processes for the OS. (3)Enter the dcsvstart command.
7	Insufficient memory	If the KFCA00855-E message showing STATIC_SHMPOOL or DYNAMIC_SHMPOOL as the area type was output immediately before this message, check and correct the memory size specified in the system environment definition. For other cases, take countermeasures according to the message that was output immediately before this message, and then enter the dcsvstart command.
8	Definition analysis error	Take countermeasures according to the error message, if any, that was output before this message. Then, enter the dcsvstart command. If there has been no output of failure message, check the user service definition and the user service default definition's parallel_count operand or service operand and take corrective action before entering the dcsvstart command.
10	Invalid schedule buffer group specified	The schedule buffer group name specified in the user service definition is invalid. Specify the correct schedule buffer group name, and then restart the user server.
21	Invalid multi-scheduler definition	An incorrect scdmulti definition command is specified in the user service definition or in the user service default definition. The possible causes are: More than one scdmulti definition command exists. The name specified in the -g option is not specified in the scdmulti definition command of the scheduler service definition. This scdmulti definition command does not include the -g option but the scdmulti definition command in the schedule service definition includes the -g option. Correct the error in the scdmulti definition command and restart the server.
31	Definition of the extended inter-node load-balancing facility is invalid	The levelup_queue_count operand or the leveldown_queue_count operand in the user service definition or the user service default definition is invalid. Check the value specified in the definition, correct the error, and enter the dcsvstart command.
32	Failure in acquiring the shared memory used by the extended inter-node load-balancing facility	The shared memory required by the extended inter-node load-balancing facility is insufficient. Check the size of the statically shared memory specified in the system environment definition, and then enter the dcsvstart command.