On Wed, Nov 27, 2019 at 10:18 AM Mark Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Use two WRKJOBSCDE entries, to keep it simple, one for every Saturday, and one for the first of each month, and ensure that they both submit these jobs to the same single-threaded job queue, and have the job set an indicator, e.g. in a *DTAARA, to show the date the job was last run.

What is "simple" is in the eye of the beholder, but to my eye, Luis's
suggestion (of having a single gatekeeper program that opens the gate
if the day of the month is 1 or the day of the week is Saturday) is by
far the simplest. It requires just one job schedule entry and one
"additional" object (the gatekeeper program). The logic is butt-easy.

Like Justin, this is what I always do for anything that isn't directly
handled by the standard job scheduler.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.