KAVT0912-E

The process indicated in process-name terminated abnormally with the return code indicated in return-code.

In Windows:

The signal number is 0.

In UNIX:

When the signal number is other than 0, the process terminated abnormally in response to the signal for the signal number.

The probable causes are:

• A JP1/AJS3 resident process was terminated abnormally by a signal.

• A JP1/AJS3 resident process was terminated forcibly by jajs_killall.cluster command.

(S)

Terminates the event/action control if the process indicated in process-name is either of the following:

• jpomgrsub

• jpoagtsub

If one of the following processes is indicated in process-name, the system operates at a reduced level while the function of the process is disabled:

• jpoeventwatch: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job

• jpocwtflMain: Monitoring Files job

• jpocwtmlmain: Email Reception Monitoring job

• jpocwtmqmain: Receive MQ Message job

• jpocwttmMain: Interval Control job or an event job with a timeout specified

• jpocwtmsmain: Receive MSMQ Message job

- Operations based on the specification of the detail process termination option

• When N is specified for the EVProcessHA environment setting parameter to disable the detail process termination option, if a job related to a detail process that terminated abnormally is registered for execution, the job terminates abnormally.

  For example, the file monitoring job that is executed when the jpocwtflMain process has terminated abnormally terminates abnormally.

• If you use a cluster system or enable the detail process termination option by specifying Y for the EVProcessHA environment setting parameter or using the default, the system terminates the event/action control if an error occurs. At this time, operation does not continue at a reduced level irrespective of the process indicated in process-name.

For details about the detail process termination option, see 20.6 Setting up the event/action control environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

Examine the cause of the error from the system error message that was output before or after the message, and then take action. If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

To continue processing, collect data and then restart JP1/AJS3.

There is no problem if this message appears when you execute jajs_killall.cluster command.