KAVS0265-E
Job ended abnormally. (name: job-name: exception-ID, status: status, code: code, host: host-name, JOBID: job-number)
The job has abnormally terminated.
The character strings displayed in status and their meanings are as follows:
-
a: An error was detected.
-
f: The job could not be started.
-
c: The job forcibly terminated.
-
?: Unknown status.
For details, see the Execution Result Details dialog box.
execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.
- (S)
-
Continues processing.
- (O)
-
Examine the cause of the error and take action to correct it. 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).
If code 128 is displayed for a PC job, the job may have terminated abnormally due to a desktop heap that is too small.
See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, check the account of the JP1/AJS3 service. You must also take measures such as checking the number of concurrent jobs or the startup processes for the entire system to prevent errors caused by a desktop heap that is too small.
This message also appears when you start the JP1/AJS3 service after executing the jpomanevreset command without the -e option. In this case, however, ignore the message because it is output as a result of terminating an event job by resetting the event.