Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Autosys Global Variable

Mar 22, 2017 5:29AM PDT

Hi all,

We have autosys job to set the value for the global variable as a date pattern(YYYYMMDD) value on daily basis. After setting the value to the global variable the file watcher jobs starts looking for the file as eg: filename_20170322.dat at specified location (considering todays date as an example). The file is available for todays date but the filewatcher job is running long time and keep running with Status RU. After we looked at log, the file watcher job is looking for filename_20170321.dat. Here is the problem/issue which couldn't get why the file watcher job is looking for yesterdays dated file even after the global value value is set with todays date.

If someone has encountered please let me know the resolution for this issue.

Thanks in advance!

Discussion is locked

- Collapse -
Answer
Re: autosys
Mar 22, 2017 6:14AM PDT

I'm afraid very few of our members are using that Workload Automation tool from CA Tehnologies in their data center. So this seems a question for their support.
But it looks like you should restart the file watcher job when you change the global variable.

- Collapse -
Autosys Global Variable
Mar 22, 2017 11:54PM PDT

Hi,

This is the structure of the autosys box we have.

MB001 -- Main box starts at 5:00 AM
S1000 -- Command job to set the value for the global variable.
F1000 -- File watcher job look for filename_YYYYMMDD.dat

F1000 job starts after completion of S1000 as we set the dependency.

As per todays(Job ran on 20170322) case, S1000 sets the global variable to 20170322 at 5:00:23 AM. The file watcher job started at 5:00:33 AM which is after 08secs of S1000 job. But Still the file watcher job is looking for file "filename_20170321.dat" instead "filename_20170322.dat".

But after we kill the file watcher job and rerun the same it is taking the latest values 20170322 for Global variable. This we are not encountering always, But once in a while. This is the 3rd time we have seen in span of 6months.

Can you please tell me what is causing for this misbehavior.

- Collapse -
Sorry, no.
Mar 23, 2017 1:16AM PDT

We don't give support for this program. In fact, we don't give support for any program. Contact CA Technology for that.