You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

Job errors and warnings are detected by JS7 from a 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 is possibly 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 like this:

  • Return Code on Success: Return code 0 is specified to signal successful execution of the job. Any other exit code signals failed execution. More than one exit code can be specified like this - separated by a comma.
  • Return Code on Failure: Alternatively one or more exit codes can be specified to signal failed execution. Any other exit code signals successful execution.


When an order is added to the workflow the job will fail and log output is created similar 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 that creates output in the stderr channel like this:


The "Job Options" tab offers to select the Fail on output to stderr checkbox like this:


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

Detect Job Warnings

Detect Warnings from Job Return Codes

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

Assume a workflow configuration with a job script that terminates with a non-zero exit code like this:

  • Return Code on Success: Return code 0 is specified to signal successful execution of the job. Any other exit code signals failed execution. More than one exit code can be specified like this - separated by a comma.
  • Alternatively one or more exit codes can be specified to signal failed execution. Any other exit code signals successful execution.

Feature Status:

FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.1

JOC-1350 - Getting issue details... STATUS

JOC-1363 - Getting issue details... STATUS

  • No labels