Runtime Job Status and Runtime Job Statistics capture the execution level status and statistics of the jobs in a job flow. These are parameters associated to the jobs and can be used in subsequent jobs linked to the jobs or in link conditions. 

Runtime Status These parameters are associated with all the jobs and captures the execution status and related details. Below are the parameter names and their details.

Status - The status of job on execution. This parameter can have value - 'SUCCEEDED', 'FAILED', 'COMPLETED' or 'DEFERRED'. The value in the parameter is always enclosed in single quotes.

    • SUCCEEDED - If the job successfully executes.
    • FAILED - If the job fails to execute.
    • COMPLETED - If the job either executes successfully, fails on execution or is disabled.
    • DEFERRED - If the job goes into deferred state. Deferred status is not considered as completed. 

ReturnCode - Return code captures the exit code from execution of the job.

  • For a Task Command job the return code is set based on the exit codes returned by the command or script executed through it.
  • For all other job the return code is set as 0 for successful execution of the job and 1 for failed execution of the job.

ReturnMessage  - Return message captures the failure message from execution of the job. The value in the parameter is always enclosed in single quotes.

CommandOutput - Valid only for Task command jobs. Command output captures the messages printed on console by the command or script executed by the Task Command job. 

Runtime StatisticsThese parameters are associated only with the data flow instance jobs and captures the record count for source and target instances in the data flow. Below are the parameter names and their details.

SourceCount - The value of source count parameter varies based on Source/Target types and native processing platform. Source count parameter from source unit gives the value of count of extraction SQL generated to load into temp table in case of external source. Source count parameter from target unit gives the value of count of extraction SQL generated to load into target table from native processing platform in case of external target. It does not display source count for source unit and target unit when the source unit is native type. 

TargetCount - The value of target count parameter varies based on Source/Target types and native processing platform. Target count parameter from source unit gives the value of count of load SQL generated to load into temp table in case of external source. Target count parameter from target unit gives the value of count of load SQL generated to load into target table from native processing platform in case of external target unit and also count of target unit in case of native target unit.

ProcessCount - Placeholder for future integration. No value is returned for this parameter.

BadCount - Displays bad records count identified while loading into target for specific native utilities.

Using runtime status and statistics in jobs

  • The runtime status and statistics of jobs can be seen under the parameter dropdown in the Expression Editor of the jobs. In an expression editor of a job these parameters are listed for those jobs that are linked to to it.
  • Consider below job flow. Here the db command job, test_job_status, will see the runtime status and runtime statistics parameters corresponding to data flow instance, test_job1, and runtime status parameter corresponding to task command job, test_job2. 

  • To use these parameters in the linked job, open the expression editor for the job and select the runtime status or runtime statistics from the drop-down. Then, select the job from the list and the parameter to be captured for it.
  • The format of the runtime status parameter displayed in the expression editor is <parameter identifier>_<job name>.<parameter>. Here, <parameter identifier> is always $RSU_ .
  • The format of the runtime statistics parameter displayed in the expression editor is <parameter identifier>_<job name>.<source/target instance name>.<parameter>. Here, <parameter identifier> is always $RST_ .