JS7 JobScheduler

Space shortcuts

Page tree

Introduction

Job errors and warnings are detected by JS7 from the job's return code:

  • For Shell Jobs the return code corresponds to the job's exit code.
  • For JVM Jobs the return code is available from the order outcome with the returnCode return variable.

In addition, for Shell Jobs, output that possibly is available from the stderr channel can be used to decide about errors and warnings.

Detect Job Errors

Detect Errors from Job Return Codes

Download workflow example: (upload .json): pdwExitCodeError.workflow.json

Assume a workflow configuration with a job script that terminates with a non-zero exit code configured as follows:

  • Return Code on Success: Return code 0 is specified to signal successful execution of the job. Any other return code signals failed execution. More than one return code can be specified, separated by commas.
  • Return Code on Failure: Alternatively one or more return codes can be specified that signal failed execution. Any other return code signals successful execution.
  • If a number of return codes are used to indicate success or failure then
    • they can be specified from a list of comma separated values, for example 1,2,4,8.
    • they can be specified from a range of return codes using two dots between return codes, for example, 1,2..4,8.
  • Negative return codes can be indicated
    • by specifying negative numbers, for example 1,2,4,-1,-2,-4.
    • by specifying a range of negative numbers, for example 1,-1,-2..-4.
  • Some operating systems use 32-bit unsigned integers as exit codes. Therefore positive numbers in the range between 0x80000000 to 0xffffffff are considered negative return codes, for example the values -1 and 4294967295 are considered the same.
  • JS-2035 - Getting issue details... STATUS
    JOC-1463 - Getting issue details... STATUS



When an order is added to the workflow, the job will fail and log output will be created like this:

Detect Errors from Output to the stderr Channel

Download workflow example: (upload .json): pdwStdError.workflow.json

Assume a workflow configuration with a job script which creates output in the stderr channel like this:


The "Job Options" tab allows the Fail on output to stderr checkbox to be selected like this:


When an order is added to the workflow, the job will fail and log output will be created like this:

Detect Job Warnings

Detect Warnings from Job Return Codes

Download workflow example (upload .json): pdwExitCodeWarning.workflow.json

Assume a workflow configuration with a job script which terminates with a non-zero exit code and is configured like this:

  • Return Code on Success: Return code 0 is specified to signal successful execution of the job. Any other return code signals failed execution. More than one return code can be specified separated by comma.
  • Return Code on Warning: Return code 1 is specified to signal a warning. A number of return codes can be specified separated by commas. Such return codes are considered successful, however, a JS7 - Notifications will be created for jobs that terminate with a return code signaling warnings.
  • Consider explanations on return codes available from chapter Detect Errors from Job Return Codes.


When an order is added to the workflow, the job will terminate successfully and log output will be created like this:


Feature Status:

FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.1

JOC-1350 - Getting issue details... STATUS

Detect Warnings from Output to the stderr Channel

Download workflow example: (upload .json): pdwWarnStderr.workflow.json

Assume a workflow configuration with a job script which creates output in the stderr channel like this:


The "Job Options" tab allows the Warn on output to stderr checkbox to be selected like this:


When an order is added to the workflow, the job will run successfully and a notification, for example by e-mail, will be created.

Feature Status:

FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.1

JOC-1363 - Getting issue details... STATUS

Resources