2.2.3.2 Return Code Management
Oracle Tuxedo Application Runtime for Batch uses several return-code variables to manage the result of a function execution and the result of job execution.
Table 2-1 Oracle Tuxedo Application Runtime for Batch Return Codes
Return Code | Description |
---|---|
MT_RC
|
The Return code for an Oracle Tuxedo Application Runtime for
Batch function execution.
|
MT_RC_JOB
|
General return code (for the job) MT_RC_JOB is updated with MT_RC at the end of each phase. It contains the maximum MT_RC value for the job.
|
MT_RC_ABORT
|
Value fixed to D0000 . The MT_RC return code is compared to this value to determine if the result of the execution was normal or not.
|
MT_RC_PROGRAM_ABORT
|
By default 127.
Contains the return code from an executable (not applicative COBOL program).
|
MT_RC_STEP_RETURNCODE_{LABEL}
|
Each phase return code is saved. The variable name contains the phase label. This variable can be used for specific chaining within the script. |
Table 2-2 EJR Return Code
Return Code | Description |
---|---|
0
|
Normal end Normal execution with user error |
1
|
System error (abort) |
5
|
No present of JOBID on command line
|
6
|
No present of JES2ROOT on command line
|
11
|
Some files or directories used for JES2 are not found |
12
|
Access right problem |
13
|
Write error - File is not created or written |
21
|
The KSH script is not found |
22
|
The KSH script is not readable |
23
|
The KSH script is not executable |
50
|
Cancel by user |
51
|
Cancel by system |
87
|
PID is not running (killing process) |
52 <= RC <= 99
|
Temporary Runtime error (the error may appear in case of restart) For example: no enough space in technical temporary storage |
123
|
Default return code must be changed during treatment |
125
|
Bad verbose level (in case of using option V )
|
>= 100
|
Permanent Runtime error (the error appears in case of restart) For example: an missing of batch RT component |
Parent topic: Tools for Managing the Execution of Jobs