Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Cause
In addition to the application completion code, a completion code specific to Jobscheduler and Job Execution Control may be displayed as the job completion code.
Action method
The job completion codes specific to Jobscheduler and Job Execution Control are explained below. Completion codes not mentioned here are set by the application, so check the meaning of the completion code in the documentation for the application.
The job completion codes are also explained in the following manuals. Use these in conjunction with this document.
V11.0L10/11.0 or later
"Job Completion Codes" in the Reference Guide
"Completion Codes" in the Online Help
V11.0L10/11.0 or earlier
"Job Completion Codes" in the Reference Guide
Jobscheduler completion codes
Of the job completion codes, the values between 201 and 256 are set in Jobscheduler. The job completion codes returned by Jobscheduler, and their meanings, are shown below.
[Windows versions]
Completion code | Meaning |
|---|---|
201 - 231 | The job has ended abnormally. |
232 - 238 | Unused (reserved by Jobscheduler). |
239 | The Jobscheduler service stopped while executing the job. (*1) |
240 - 241 | Unused (reserved by Jobscheduler). |
242 | Copy and startup of the job net failed. |
243 - 244 | The job you requested Job Execution Control to execute has failed. |
245 | The variable parameter, job definition variable, or job net variable value contains invalid characters. |
246 | As a result of replacing a variable parameter, job definition variable, or job net variable, the upper limit for the string length was exceeded. |
247 | Failed to read/write the job definition variable information or the job net variable. |
248 | While waiting for OR conditions, the succeeding job starts because one of the preceding jobs has already ended normally. As a result, the job ends without these conditions being met. |
249 | While waiting for OR conditions, one of the preceding jobs ends abnormally. As a result, the conditions cannot be evaluated and the job ends. |
250 | The specified job does not exist. |
251 - 254 | Unused (reserved by Jobscheduler). |
255 | The job completion code is 256 or more. (*2) |
256 | The job was canceled. |
*1: If backup is performed while a job is executing, and the information that is backed up is restored, the job that is executing ends abnormally with completion code 239.
*2: If the actual completion code is 256 or more, the following is displayed in the Job History window:
... ended code=255.(Actual completion code) |
[UNIX versions]
Completion code | Description |
|---|---|
201 - 231 | [Job Execution Control attribute] |
232 - 237 | Unused (reserved by Jobscheduler). |
238 | Failed to set the job net administrator rights (initgroups system call). |
239 | Jobscheduler daemon stopped while executing the job. (*1) |
240 - 241 | Unused (reserved by Jobscheduler). |
242 | Copy and startup of the job net failed. |
243 - 244 | Failed to execute the job. |
245 | The variable parameter, job definition variable, or job net variable value contains invalid characters. |
246 | As a result of replacing a variable parameter, job definition variable, or job net variable, the upper limit for the string length was exceeded. Alternatively, the upper limit (640) that can be retained by the job net variable was exceeded. |
247 | Failed to read/write the job definition variable information or the job net variable. |
248 | While waiting for OR conditions, the succeeding job starts because one of the preceding jobs has already ended normally. As a result, the job ends without these conditions being met. |
249 | While waiting for OR conditions, one of the preceding jobs ends abnormally. As a result, the conditions cannot be evaluated and the job ends. |
250 | Failed to obtain the job net administrator information (getpwnam system call). Note that, if the attribute is other than Normal, the specified job may not exist. (*2) |
251 | Failed to set the job net administrator rights (setgid system call). |
252 | Failed to set the job net administrator rights (setuid system call). |
253 | Failed to change to the directory specified in the job (chdir system call). |
254 | Failed to start the job (execvp system call). |
255 | Failed to start the job (fork system call). |
256 | The job was canceled. |
*1: If backup is performed while a job was executing, and that information is restored, the job that was executing ends abnormally with completion code 239.
*2: If the job does not exist when the attribute is other than Normal, an error message is output to the Previous log tab of the job.
*3: If the actual completion code is 256 or more, the following is displayed in the Job History window:
...ended code=255.(Actual completion code) |
Point
Completion codes other than 201 to 256, and completion codes from 201 to 256 that are not used, are not values set by Systemwalker Operation Manager. They are values output by the job, for example the command, batch file, or shell script registered in the job command field.
Additionally, consider not making the completion code of the command, batch file, or shell script registered as the job 201 to 256. If 201 to 256 are used as the return value of the job, it will be difficult to tell whether the completion code was set by the job or by Jobscheduler. Note that if the return value of the job is 255 or greater, it will be handled as 255.
Job Execution Control completion codes
For the job completion codes output by Job Execution Control, the values shown below are set according to the job type.
Job type | Job completion code |
|---|---|
Batch file | Batch file return code |
Program | Program return code |
JCL (Job Control Language) | Maximum value for each step/completion code of the last step |
Shell script | Shell script return code |
Note that, if the job execution is canceled, a special value is set in the job completion code. The causes of the cancellation of the job, and the job completion code set when the job is canceled, are shown below.
[Windows versions]
Cause of the cancellation of the job | Completion code | Completion code | Completion code |
|---|---|---|---|
An exception occurred during the execution of the job. | Exception code | Exception code | Exception code |
| 8 | 8 | 0x40000008 |
In the execution of the network job using JCL, the format specified for the control statements for job steps (*3) is invalid. | 12 | 12 | 0x40000012 |
An error occurred when submitting the network job on the remote server. | 16 | 16 | - |
| - | - | 0x40000016 |
In the request from the schedule server to the execution server when a network job was executed, a function not supported by previous versions was being used. As a result, an error occurred, resulting in failure to connect to the server running a previous version that does not support extension functions. | - | - | 0x40000020 |
An error occurred when submitting the network job on the remote server. The effective user of the job is restricted by the effective user control list. | - | - | 0x40000024 |
| 132 | 132 | 0x40000132 |
The job was canceled by a user operation from the screen, the qdel command, or the job deletion API. | 0x40000222 | 0x40000222 | 0x40000222 |
The job was canceled because the cut-off execution time (job execution time-out) has elapsed. | 0x40000322 | 0x40000322 | 0x40000322 |
In the execution of the job using JCL, the executable file specified in the job step does not exist. | 0x40000806 | 0x40000806 | 0x40000806 |
If the function that executes the job with job owner rights is enabled, an error occurs in the user authentication processing when the job is executed (*4). Alternatively, for Distributed Execution jobs (*5) and network jobs, an error occurred in the authentication processing on the remote server. | 0x40000913 | 0x40000913 | 0x40000913 |
The network job could not continue because of a line error or because the other server is down. Alternatively, for Job Execution Control processing, the job could not continue because the error occurred. | 0x40000999 | 0x40000999 | - |
For Job Execution Control processing, the job could not continue because the error occurred. | - | - | 0x40000999 |
[V13.2.0 or later] | - | - | 0xC0000005 |
[V13.2.0 or later] | - | - | 0xC0000094 |
[V13.2.0 or later] | - | - | 0xC0000135 |
[V13.2.0 or later] | - | - | 0xC0000142 |
*1: The commands are as follows:
- connect
- send
- execute
- receive
- disconnect
*2: In Windows Server 2003 or later, the following event is output to the event log when the first desktop heap insufficiency occurs after starting the operating system:
Type: Warning Source: Win32k Event ID: 243 Description: Failed to allocate desktop heap. |
*3: The control statements are as follows:
- file
- exec
*4: Possible causes are as follows:
The settings that are required to execute the job with owner authority were not configured.
Refer to the Systemwalker Operation Manager Technical Guide for information on the required settings.
The domain controller (PDC, BDC) was stopped or restarted.
The Windows Internet Naming Service (WINS) is not operating normally.
*5: In V10.0L21 or earlier, this is "load distribution job".
*6: This is set in V13.1.0 or earlier.
When the application makes the exception (abnormal end), the exception code 0xC******* (in hexadecimal) is set by the operating system. This code is reserved by the operating system. It is not a code set by Job Execution Control. Consider the following action methods for information on exception code 0xC0000005, 0xC0000135, 0xC0000142:
"5.2.14 The Job Ends Abnormally with Exception Code 0xC0000005, 0xe06d7363 [Windows versions]"
"5.2.15 The Job Ends Abnormally with Exception Code 0xC0000135 [Windows versions]"
"5.2.16 The Job Ends Abnormally with Exception Code 0xC0000142 [Windows versions]"
[UNIX versions]
Cause of the cancellation of the job | Completion code | Completion code | Completion code |
|---|---|---|---|
An exception (signal received, core occurrence) occurred while the job was being executed. | Exception code | Exception code | Exception code |
| 8 | 8 | 0x40000008 |
In the execution of the network job using JCL, the format specified for the job step control statement (*3) is invalid. | 12 | 12 | 0x40000012 |
An error occurred when submitting the network job on the remote server. | 16 | 16 | - |
| - | - | 0x40000016 |
In the request from the schedule server to the execution server when a network job was executed, a function not supported by previous versions was being used. As a result, an error occurred, resulting in failure to connect to the server running a previous version that does not support extension functions. | - | - | 0x40000020 |
An error occurred when submitting the network job on the remote server. The effective user of the job is restricted by the effective user control list. | - | - | 0x40000024 |
| 132 | 132 | 0x40000132 |
The job was canceled by a user operation from the screen, the qdel command, or the job deletion API. | 0x40000222 | 0x40000222 | 0x40000222 |
The job was canceled because the cut-off execution time (job execution time-out) has elapsed. | 0x40000322 | 0x40000322 | 0x40000322 |
In the execution of the job using JCL, the executable file specified in the job step does not exist. | 1 | 1 | 0x40000806 |
For Distributed Execution jobs and network jobs, an error occurred in the authentication processing on the remote server. | 128 | 128 | 0x40000913 |
For Job Execution Control processing, the job could not continue because the error occurred. | 0x40000999 | 0x40000999 | 0x40000999 |
*1: The commands are as follows:
- connect
- send
- execute
- receive
- disconnect
*2: In Windows Server 2003 or later, the following event is output to the event log when the first desktop heap insufficiency occurs after starting the operating system:
Type: Warning Source: Win32k Event ID: 243 Description: Failed to allocate desktop heap. |
*3: The control statements are as follows:
- file
- exec
*4: This is set in V13.1.0 or earlier.
When the application receives the signal (abnormal end), the exception code 128 + signal number (octal: 200 + signal number) is set by the operating system. This code is set by the operating system (shell). It is not a code set by Job Execution Control.
Refer to the following action method for information on code 137,138, and 139:
"5.2.4 The Job Ends Abnormally with Code 137, 138, or 139 [UNIX versions]"
[Windows versions/UNIX versions (common)]
If the online job execution has been canceled, the job completion codes shown below are set:
Meaning | Completion code | Completion code | Completion code |
|---|---|---|---|
The online job ended normally. | 0 | 0 | 0 |
Failed to start the online job, because Interstage is not installed on the system. | 1 | 1 | 1 |
Failed to start the online job, because an error occurred in Interstage while initializing the online job startup environment. | 2 | 2 | 2 |
Failed to start the online job, because an error occurred in Interstage while starting the online job. | 3 | 3 | 3 |
Failed to start the online job, because an error occurred in Interstage while monitoring the online job. | 4 | 4 | 4 |
Failed to stop the online job, because an error occurred in Interstage while stopping the online job. | 5 | 5 | 5 |
The online job ended abnormally. | 6 | 6 | 6 |
The online job was canceled before it started. | 256 | 256 | 256 |
| 132 | 132 | 0x40000132 |
The limit value for the execution time-out was exceeded, or the cut-off execution time has elapsed while the job was being executed, therefore the online job was forcibly terminated. | 0x40000322 | 0x40000322 | 0x40000322 |
Failed to start the online job, because a system error occurred. | 0x40000999 | 0x40000999 | 0x40000999 |
