OpenTP1 installation or setup must be reexecuted.

An erroneous specification item in the system definitions is output with a message.

The system definition items must be checked and respecified correctly. OpenTP1 can then be restarted.

A message indicating a memory or disk space shortage is output.

Either unneeded processes should be terminated, or unneeded files should be deleted. OpenTP1 can then be restarted.

Additionally, the OS's system constants (especially constants related to the shared memory) should be checked, and the OS should be reconstructed, if necessary. OpenTP1 definition information should also be checked. OpenTP1 can then be restarted.

A message is output indicating that a required file is missing.

The required file must be provided, and OpenTP1 should then be restarted.

The OS should be reconstructed, the OpenTP1 definition information should be checked, and OpenTP1 should then be restarted.

A communication error message is output.

The TCP/IP environment setup should be corrected, and OpenTP1 should then be restarted.

An I/O error message is output.

The erroneous device should be repaired or replaced.

If an incorrect user environment setting command is specified by the user_command operand in the system environment definition, an attempt to start OpenTP1 may fail without outputting a message or dump.

Check if the user environment setting command specified by the user_command operand is correct and take an appropriate action if incorrect. Then, start OpenTP1.

The dcreset command must be executed when the KFCA00715-E message is output. This message is output when OpenTP1 start or restart processing is disabled, indicating that processing of the process service is interrupted. Eliminate the error according to the reason code of the message, and then execute the dcreset command. If the dcreset command is executed while the error still remains, the KFCA00715-E message appears again.

The dcreset command must be executed when OpenTP1 is inactive. For changing the system common definition, his command must be executed after normal termination of OpenTP1. When the KFCA00715-E message is output, the dcreset command can be executed after abnormal termination of OpenTP1. Executing the dcreset command while OpenTP1 is online causes the system go down.

If you have used JP1/AJS2 to set the startup of OpenTP1 from a job, you might not be able to use the dcstart command to start OpenTP1. If this problem occurs, check the usage rate of the CPU. The rate is probably 100%, and the system reports that almost all of that amount is being used by the system service processes of OpenTP1.

If you have used JP1/AJS2 to set the startup of OpenTP1 from a job, the OS priority for the dcstart command is set to the lowest level (the nice value is 39). Therefore, when the load on the CPU increases as the result of many system server processes, CPU time cannot be allocated to the dcstart command.

This case often occurs in the following machine configurations:

• Only one CPU is installed.
• The number of system server processes of OpenTP1 is extensive.

If this situation occurs, execute the ps command to check the nice value for the process in the dcstart command. The following shows an example of executing the ps command:

For AIX

ps -elf|grep dcstart 200001 A betran 16382 21390 2 60 20# e7e4 3780 15:56:13 pts/1 0:00 dcstart

For HP-UX

ps -elf|grep dcstart 1 S betran 6995 6932 0 154 20# 41516c00 344 c0fa80 15:56:43 pts/tn 0:00 dcstart

#

Indicates the nice value. When this value is 39, the OS priority for the dcstart command is at the lowest level.

Hitachi recommends that you set the same value for the OS priority for executing OpenTP1 operation commands as the value set for the priority for OpenTP1. To change the priority for OpenTP1 operation commands, in JP1/AJS2-View, change the execution priority level of the job definitions of JP1/AJS2 that starts the process of the OpenTP1 dcstart command. For details, see the manual Job Management Partner 1/Automatic Job Management System 2 Operator's Guide.