Thank you for the suggestion Chris. That would solve my issue.
Original Message:
Sent: May 20, 2024 03:04 AM
From: Chris_Elvin
Subject: Use WOBTRIG in Event but also delay trigger by 4 days
Hi Loren,
Your current approach seems perfectly adequate, but if you are looking for an alternative, how about this?:
Use your current WOBTRIG to trigger an application with a single job (lets call it X)
JOB X TASK SELFCOMPLETING
...
ESPNOMSG TRIGGER REAL.APPLNAME ADD AT('NOW PLUS 4 DAYS')......
...
ENDJOB
Where REAL.APPNAME is the trigger associated with the application that actually processes the incoming file.
- The event REAL.APPNAME has no scheduling criteria and is only triggered by this job
- I suspect you might also need to pass the file name and other WOBTRIG information in the USER1..USER4 variables so that the processing application has the required information
The main difference in this approach is that the application containing the WOBTRIG can complete and is not "hanging around" for 4 days
------------------------------
Kind Regards
Chris
Original Message:
Sent: May 17, 2024 02:35 PM
From: Loren Watts
Subject: Use WOBTRIG in Event but also delay trigger by 4 days
Currently my event WOBTRIG triggers the event when the file is seen.
Is it possible to add logic to my event definition to look for a file, but then wait to trigger the event four days after the file is seen?
Currently I use DELAYSUB statements in the appl to accomplish the four day delay to execute the objects in the appl.
in the appl I am using these statements:
IF TODAY('WEDNESDAY') THEN DELAYSUB TODAY PLUS 5 DAYS
DELAYSUB TODAY PLUS 4 DAYS
^^^^^^^^^^^^^^^^^^^^^^^
I'm being asked to do this because our organization prefers not to have appl generations alive but in an unfinished state for days.