Chase -E does not put long STARTING job to FAILURE

book

Article ID: 206658

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys)

Issue/Introduction

When running chase with the -E parameter, jobs flagged by chase that have been in STARTING state longer than 120 sec (or other configured amount of time) are not set to FAILURE status.

Environment

Release : ALL

Component : CA Workload Automation AE (AutoSys)

Resolution

The -E parameter for the chase command does not apply to jobs that it finds stuck in the STARTING state. Only the jobs in RUNNING state that are not actually running on the agent are set to FAILURE.