AutoSys Workload Automation

Hello,

actually  I used both of them.  What is the CA recommendation ?

Hello Yanis

File Watcher jobs come from  Autosys legacy environment while File Trigger jobs are new job types in release 11.3.x with much more possibilities.

The System Agent can also launch the file trigger job as a separate process to:
   - Perform variable substitution
   - Support Windows UNC file paths
  -  Support files residing on a UNIX NFS mounted drive

It also has several other attributes to help you to meet some special goals when monitoring files.

Some of these new attributes:

watch_file_change_type – change of file size. Valid values are DELTA, PERCENT or SIZE
watch_file_change_value – value of change in file size. This must be >= 1 for watch_file_type of Expand and Shrink.
watch_file_recursive – search for file down this path. Valid values: Y or N
watch_file_win_user – userid that is used to monitor UNC files. This is mutually exclusive with the watch_file_owner and watch_file_groupname keyword.
watch_file_groupname – group name of the file to be monitored
watch_file_type – valid values are : Create / Delete / Exist / Expand / Notexist / Shrink/ Update. If this is value is expand or     shrink, watch_file_change_type must be specified and watch_file_change_value must be >= 1.
Continuous – indicates if you want the job to wait for the condition to be satisfied before the job ends. Valid values: Y or N.

And there is also a difference between File Watcher and File Trigger Jobs on Windows: File Watcher and File Trigger jobs produce different results when the dot (.) character is used as a literal. The pattern "*.*" is treated differently depending on which job is used:

• File Trigger jobs treat a dot character (.) as a literal. To be considered a match, a file must contain a dot and characters on either side of it. For example, if two files exist in the same directory, one named "abc" and the other "abc.txt," only "abc.txt" is considered a match.
• File Watcher jobs use Windows native APIs, which assume the dot character can be implicit. For example, File Watcher jobs consider "abc" to be the same as "abc." So, in this case, either "abc" or "abc.txt" is a match.

With all these differences, recommendation is to use  FT jobs

Regards

Jean Paul

Thanks a lot Jean Paul !

Jean Paul,

  Is the owner attribute in the file trigger job used at all?

It looks like to run the file trigger job as a separate process you need to specify filemonplugin.runexternal=true and also a default userid and password that ALL file triggers on that server will use.

We need the file trigger to run as a separate process using the ID specified in the owner field.