An IAL scheduled with a custom expression like FREQ=DAILY;BYHOUR=10,11 to run twice a day at exactly 10:00 and 11:00 instead computes an odd time (like 10:28), apparently influenced by the current sysdate at the time the schedule was saved — how do you pin it to the exact intended times?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Add explicit BYMINUTE and BYSECOND values to the expression, not just BYHOUR — for example, FREQ=DAILY;BYHOUR=10,11;BYMINUTE=00;BYSECOND=00. Without pinning minutes and seconds explicitly, the schedule falls back to whatever minute/second the expression was saved at (drawn from sysdate), which is why it lands on an odd time like 10:28 instead of exactly on the hour; fully specifying BYHOUR, BYMINUTE, and BYSECOND together locks the schedule to the exact times intended.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions