FILE_TRIGGER using GENERATE NOCHANGE(20)

[Loren Watts]

I am not getting FILE_TRIGGER using NOCHANGE to respect the duration in NOCHANGE().

Am I correctly using NOCHANGE() for my FILE_TRIGGER?

The file being monitored is a .zip that is of varying size, but always over 1 GB. It can take 20 minutes for the zip to be fully copied to the target folder. Or just a couple minutes, depending on lunar tides.

The problem is that the current setup using default CREATE causes FILE_TRIGGER to complete just because it sees the file.
But the zip file has not finished coming to full size in target folder.

I have changed from CREATE to GENERATE NOCHANGE(20) - but 20 minutes is not being respected.

FILENAME '\\nasserver\DEV\Batch\Loren\MyZip.zip' GENERATE NOCHANGE(20)  

1. FILE_TRIGGER is in Monitor state (Monitored for INACTIVE)

2. Copy a 4.8gb zip to target NAS folder. It only takes a couple minutes for target file to be full size.

3. Rather than monitoring for the file not to change for 20 minutes, the FILE_TRIGGER completes in a couple minutes.

4. FILE_TRIGGER details show:
  Filename(\\lshnap510\Facets_DEV\Batch\Loren\FOLB_COPY_TESTFOLDER\FOLB.zip), GENERATE
  NC_WNZC_D3_LOREN_FT_NOCHANGE J427978, File appears inactive, size 

^^^^^^^^^^^^^^^
I see a discussion from 2017, but it is for WOBTRIG.

https://community.broadcom.com/mainframesoftware/communities/all-discussions/viewthread?GroupId=1903&MID=763712&CommunityKey=a63272f0-fb9f-44be-b0ff-9657f904076e&tab=digestviewer

^^^^^^^^^^^^^^^

FILENAME Statement: Specify File to Monitor

Broadcom		remove preview
FILENAME Statement: Specify File to Monitor The FILENAME statement specifies the name of the file to monitor for activity within a File Trigger job. The FILENAME statement also specifies the monitor conditions for the file trigger. View this on Broadcom >

[Lucy Zhang]

Hi Loren,

I did a quick search and didn't find any known defect.

Will you open a support case with related agent logs? We will check if the NOCHANGE option was sent to agent correctly. Also we may involve our agent expert to check if there is any agent defect.

As you may know, ESP relies on the response from agent to defect the file status.

Thank you,

Lucy

[Loren Watts]

Thank you Lucy. I will open a support case.

[Rick Romanowski]

My preference would be Alternative # 2 from the 2017 discussion, which eliminates the need for NOCHANGE parameter.

Alternative #2:

If you have input on how the file is being copied to the server for agent NT_XYZ.

 

If the file is first copied to a temporary directory (\\abc\temp) then after successful copy, renamed to destination directory (\\abc) then you guarantee that the process does not trigger until a complete file is available.

------------------------------
Rick Romanowski
[e-mail]
Sr. Systems Analyst
UPS
NJ, USA
------------------------------

[Loren Watts]

Thank you for your thoughts Rick. I don't own the zip file creation code. Currently 7-Zip command line code is creating the zip file in the directory FILE_TRIGGER is monitoring. Good idea to COPY to temporary directory, then MOVE/RENAME to FILE_TRIGGER directory.

[Rick Romanowski]

COPY to temporary directory, then MOVE/RENAME to FILE_TRIGGER directory.

------------------------------
Rick Romanowski
[e-mail]
Sr. Systems Analyst
UPS
NJ, USA
------------------------------

[Loren Watts]

Thank you Rick. I corrected my comment to what you wrote.