CA7 Job Type FILE_TRIGGER monitoring existence of file on a Linux Red Hat server

[Dana Pittman]

CA7 Job Type FILE_TRIGGER monitoring existence of file on a Linux Red Hat server.
Can anyone tell me what is the exact mechanism on the server which will tell the Agent (12.1) a file exists?  (Using the CREATE parameter)
Also, what is the mechanism for the UPDATE parameter?

Background:  We have an application wanting to add a file trigger to monitor for the creation of a file.  The challenge is it can be a very large file and therefore can take 15-20 minutes for the data to be completely written to the file.
Has anyone dealt with this situation?  Any ideas about potential solutions?
We have told application folks in the past to create another step to create a "dummy" trigger file after the data file is completely written to but I am wondering if there is any other way around this.  
Thanks for any feedback

[Roderick Woods]

For FILE_TRIGGER jobs you can use additional criteria depending on the type. Using the CREATE parameter, you can also use the NOCHANGE(xxxxxxx) keyword, which instruct the agent to satisfy the file trigger only after the file has remained unchanged for the amount of minutes specified.

For example:
FILENAME C:\TEST\test1.txt CREATE NOCHANGE(2)

The example of above will cause the agent to detect the creation of the file and then wait for the file to remain unchanged for 2 minutes.

Below is a link to the documentation that talk about the FILENAME statement:

https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-workload-automation-ca-7-edition/12-1/related-documentation/use-ca-ias/c-lang-statements/filename-statement-specify-file-to-monitor.html
 

[Dana Pittman]

Thanks Roderick!  I obviously missed the NOCHANGE parameter.  I tested it out and it seems to work as advertised.  I think this is exactly what we and our application team were looking for.