Job went to TERMINATED status when it is not running

Products

• Autosys Workload Automation

Issue/Introduction

The results seen in autorep -J for a filewatcher that went to SUCCESS and then went to TERMINATED:

Status/[Event]       Time                                Ntry    ES  Process Time               Machine

-------------------       -----------------------------    ------   -----  ----------------------          ------------------------------

STARTING            03/10/2023  14:40:03      1       PD    03/10/2023 14:40:04   mymachine.mycompany.com

RUNNING             03/10/2023  14:40:04      1       PD    03/10/2023 14:40:05   mymachine.mycompany.com

    <Monitored for CREATE>

[CHK_TERM_RUNTIME]   03/10/2023  15:05:04    1    PD    03/10/2023  15:05:05

    <Event was scheduled based on job definition.>

SUCCESS            03/10/2023  15:05:04      1      PD     03/10/2023  15:05:06  mymachine.mycompany.com

    <File created, size 1794118, NoChange 1 min. Filename("E:\myfilewatcher_directory\myfile")>

TERMINATED      03/10/2023  15:05:05       1     PD     03/10/2023   15:05:07

    <Already finished before>

[CHK_MAX_ALARM]    03/10/2023   15:10:04     1     PD    03/10/2023   15:05:06  mymachine.mycompany.com

Environment

Release : 12.0
System agent 12.0.0

Resolution

This is a known issue that has been fixed in the 12.1 Agent.

Here is the line in the list of fixes under the Release Notes for the 12.1 Agent:

• Filewatcher going to be terminated even if it is not running.
  
  https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-1/release-information/Release-Notes-12-1.html