File Watcher Job Not Running As Expected

[Arihara Subramanian]

Hello All,

We have set up a file watcher job to monitor the availability of a specific file. However, the job continues to run indefinitely even after the file becomes available. We have verified that similar setups, such as the Autosys installation folder, are functioning correctly.

Could you please provide your valuable input to help us resolve this issue?

Below is the JIL

insert_job: File_Watcher_Test    job_type: fw
description: Filewatcher_Test
machine: Windows551763
owner: owner_1
max_run_alarm: 1
alarm_if_fail: y
alarm_if_terminated: y
avg_runtime: 43
date_conditions: y
timezone: UTC-8
days_of_week: su,mo,tu,we,th,fr,sa
start_times: "00:00, 6:00, 12:00, 18:00"
watch_file: "D:\File_watcher\Reporting\sample.txt"
watch_file_min_size: 0
watch_interval: 60

[Gene Howard]

Is the D drive a local drive on the machine or a mapped drive.
The agent will not see or use a mapped drive



Gene Howard

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.

[Arihara Subramanian]

Hi Gene Howard,

Thanks for your quick reply.

We have tried with this from C drive also, it's not recognized the file. Is there any permission to be granted in file level or in JIL file?

[Gene Howard]

Log in to the target system as user Windows551763,  owner_1.
Open a command prompt non administrative as that user
go to the D: drive, and do a dir command.
Then change to each directory one at a time and do a dir until you are at the final path.
Most likely, at one of these places, you will get a permissions denied error that you need to address.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Arihara Subramanian]

Hi Gene Howard,

Job is working fine now, we just triggered again, and it was successful but still some of its run running infinitely. As of now okay with this setup.

[Robert Hoy]

Arihara,

We have run into this issue in the past as well, which is over the course of many years. File watchers that were working normally for a considerable time suddenly just stopped responding. I opened a case regarding this with CA prior to Broadcom acquiring them, and the CA Support Tech indicated this was a known issue and advised that if, after checking permissions and network access and any changes that may have affected the job were exhausted, then change the job to a file trigger. When we changed those affected jobs to File Triggers, the jobs worked as expected. Note that the reverse is sometimes true as well, going from File Trigger to File Watcher was necessary. The Support Tech at the time said that it was a known issue, and at that time, that was their suggestion for mitigating the issue, as they had no root cause they could focus on to completely resolve the issue. Now, this was several years ago, and many updates to Autosys have occurred since then, so the issue may have been addressed those updates and new revisions, but if all else fails for you, I suggest copying the JIL of the current file watched job and saving it to a text file so that you can roll back easily, and create a File Trigger job to take the place of this File Trigger, then test the functionality of that new File Trigger job.

[Arihara Subramanian]

Hi Hoy

We didn't try file trigger job, we tried again with same setup it was started working but still some of its run running infinitely. As of now, we are okay. Thanks!