21.2 Job Execution Control Completion Code

Depending on the type of job, the following values are set in the job completion code output by Job Execution Control:

Job type	Job completion code
Batch file [Windows]/Shell script [UNIX]	Return code of batch file [Windows]/shell script [UNIX]
Program	Return code of program
Job Control Language (JCL)	Maximum value for each step/completion code of the last step

Note that if the job execution is interrupted, a special value is assigned to the job completion code. The causes of job interruption and the job completion codes set when an interruption occurs are shown below:

[Windows/UNIX version]

Cause of job interruption	Completion code
When a network job written in JCL was executed, the format of a network job control command (Note 1) was found illegal, or an internal processing error occurred in Job Execution Control on a network job. When a job was submitted to a distributed execution queue and started at an execution server (a remote host which is different to a schedule server), one of the following errors occurred: The input file does not exist. The output file does not exist. When the network job submission destination is a Windows server, it is possible that the desktop heap has been used up (Note 2).	0x40000008
When a network job written in JCL was executed, the format of a control statement (Note 3) pertaining to a job step was found illegal.	0x40000012
Network job submission processing resulted in an error on a remote server. The execution request was rejected since a job with the request host specified was submitted to the distributed execution queue. There is insufficient disk space on either the schedule server or the execution server.	0x40000016
When a network job was executed, a request from the schedule server to the execution server contained a function not supported by an earlier version of Systemwalker Operation Manager. This resulted in an error, which made it impossible to connect to the server running the earlier version that did not support the extended function.	0x40000020
An error occurred while receiving a network job from a remote server. Users are restricted by the user control list for job execution.	0x40000024
A network job was unable to proceed due to a line failure or local server shutdown. When a job was submitted to a distributed execution queue and started at an execution server (a remote host which is different to a schedule server), one of the following errors occurred: Errors related to the network occurred while transferring I/O files. System errors occurred while transferring I/O files. There is insufficient disk space on either the schedule server or the execution server.	0x40000132
The job was canceled by a user, the qdel command or the job termination API.	0x40000222
The job was canceled due to a job processing timeout (the maximum time limit reached).	0x40000322
When a JCL job was executed, the executable file specified in the job step did not exist.	0x40000806
[Windows] An error occurred during the user authentication to start the job as the job owner (Note 4). An error occurred while authenticating the use on the remote server to process the distributed job or the network job. [UNIX] In a network job for Windows on the execution server, an error occurred due to specify the function to start the job on the execution server by the job owner authentication. An error occurred while authenticating the use on the remote server to process the distributed job or the network job.	0x40000913
An error that prevents the job from being continued occurred in the Job Execution Control processing.	0x40000999

Note 1:

The corresponding commands are listed below:

connect
send
execute
receive
disconnect

Note 2:

In Windows Server 2003 or later, the event shown below will be output to the event log when the first desktop heap shortage occurs after starting the operating system.

Type: Warning
Source: Win32k
Event ID: 243
Description: Failed to allocate desktop heap.

Note 3:

The corresponding control statements are listed below:

file
exec

Note 4:

The cause of the error can be attributed to the following:

Settings required for executing jobs with owner's privileges have not been defined.
See the Systemwalker Operation Manager Installation Guide for required settings.
A domain controller (PDC or BDC) has been stopped or restarted.
The Windows Internet Naming Service (WINS) is not operating properly.

[Windows]

Cause of job interruption	Completion code
Illegal memory access by a user application.	0xC0000005
The user application attempted an integer divide by zero.	0xC0000094
Cannot find the DLL required to run the user application. (The DLL path is not set to the PATH environment variable.)	0xC0000135
Unable to initialize the DLL required to run the user application. The system may not have enough desktop heap memory to allocate (Note 1).	0xC0000142

Note 1:

In Windows Server 2003 or later, the event shown below will be output to the event log when the first desktop heap shortage occurs after starting the operating system.

Type: Warning
Source: Win32k
Event ID: 243
Description: Failed to allocate desktop heap.

If an online task is interrupted, the following job completion codes are set:

Meaning	Completion code
Online job ended normally.	0
Online job startup failed because Interstage has not been installed.	1
Online job startup failed because an Interstage error has occurred during initialization of online job startup environment.	2
Online job startup failed because an Interstage error has occurred during startup of online job.	3
Online job monitoring was interrupted because an Interstage error has occurred when the online job was being monitored.	4
Online job stop failed because an Interstage error has occurred when the online job was being stopped.	5
Online job was abnormally terminated.	6
Online job was forcibly stopped before it was started.	256
A network job was unable to proceed due to a line failure or local server shutdown. There is insufficient disk space on either the schedule server or the execution server.	0x40000132
Online job was forcibly terminated because the time lapse limit was exceeded or cut-off execution time arrived during the job execution.	0x40000322
Online job startup failed due to a system error.	0x40000999