2.13.1 Troubleshooting in the event that a job, jobnet, process, or embedded database terminates abnormally during the startup of the JP1/AJS3 service
This subsection describes troubleshooting in the event that a job, jobnet, process, or embedded database terminates abnormally during the startup of the JP1/AJS3 service.
- Organization of this subsection
-
(1) If the ajsinetd process terminates abnormally during the startup of the JP1/AJS3 service on a replicated virtual machine
If the ajsinetd process terminates abnormally and the KAVS1007-E message is output, a possible cause is that the replicated virtual machine failed to resolve the IP address of the local host. In this case, perform the following procedure:
-
Check the error message in the integrated trace log.
-
Make sure that the host name of the replicated virtual machine is correctly set. If the host name has already been set correctly, make sure that the IP address of the local host can be resolved from the host name on the replicated virtual machine.
(2) If a job or jobnet terminates abnormally during the startup of the JP1/AJS3 service on a replicated virtual machine
If a job or jobnet terminates abnormally and the KAVS0265-E or KAVS0262-E message is output, a possible cause is that the JP1/AJS3 service that was terminated during a job execution on the replicated virtual machine was not cold-started. In this case, perform the following procedure:
-
Check the error message in the integrated trace log.
-
Stop the JP1/AJS3 service on the replicated virtual machine.
-
Restart the JP1/AJS3 service in cold-start mode.
(3) If the embedded database terminates abnormally during the startup of the JP1/AJS3 service on a replicated virtual machine
If the embedded database terminates abnormally and the KFPU00219-E message is output, a possible cause is that the system common definition file for the embedded database contains incorrect settings. In this case, perform the following procedure:
-
Identify the incorrect settings according to the KFPU00219-E message.
-
Correct the system common definition file for the embedded database.
-
Restart the JP1/AJS3 service.