Job run report showing status and exit code that doesn't match AutoSys

Products

• iDash Workload Automation

Issue/Introduction

iDash job run report lists -656 as the exit code for RUNNING jobs.

Why does the iDash job run report show a job with -656 as the exit code?

Environment

Release:
Component: AEIDSH

Cause

The "Exit Code" entry in the iDash "AutoSys job run report" comes from the iDash DB's idash_run table. This value in turn comes from the AutoSys Database. The value is temporarily stored as -656 in the AutoSys DB's Exit_Code field for the ujo_job_runs table while a box job is in a RUNNING state.

Jobs that are in a RUNNING state are always considered as current since there is no End Time. For reports that are defined with Timeframe = Past days Time Qualifier = End Time the generated report will always contain jobs with RUNNING status. There are many reasons why jobs are stuck in RUNNING. One of them is when the job is stuck in RUNNING and you execute a sendevent to FORCE_STARTJOB. A new instance of the job would run but the old run will stay in both AutoSys and iDash as RUNNING with End Time = 0

Resolution

You can safely delete these entries from the iDash DB to remove them from reports.

--Delete all runs with a exit code = -656

delete from idash_run where exit_code=-656;

--Delete specific job runs with a exit code = -656

select * from idash_run where joid = <joid> and exit_code=-656;

delete from idash_run where joid = <joid> and exit_code=-656;