Well, 3 jobs with Robot/Schedule-- the job that runs the commands can also have a schedule. But when you have daytime, nighttime, and weekend schedules, and sometimes involved sets of instructions to execute (Robot lets us lists dozens of commands if we need to), not having to maintain 3 sets of instructions (and probably forgetting one of them) is worth the extra jobs.
We also try to talk to the users and find out if they -really- need a job run every 5 minutes! "Oh, we need current data!" How often does the data change? If it's every 10 minutes, that every-5-minute job is scheduled incorrectly!
Every 5 minutes sounds like they're trying to track a real-time process. We found that even when some shop floor process generates information every cycle, the people on the floor batch up data for several cycles and enter it all at once. So much for real-time tracking!
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Friday, April 06, 2018 1:04 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Advanced Job Scheduler - changing run frequency
On Fri, Apr 6, 2018 at 11:46 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx> wrote:
> We do this with AJS. The different jobs are scheduled as needed. All
each of them do is kick off the job
that does all the real work using SBMJOBJS command. We also have some
that kick off a
group using STRGRPJS command too.
Paul, Dana - ooh, I like that. Combines simplicity AND elegance.
What's important is that you're happy with it, but (1) this sounds
like you're wrapping up the one command that "does the work" into
another job entry (so you need four total, assuming "business hours",
"after hours", and "weekend" launchers need to be three separate
entries); and (2) in my book, there is no elegance without simplicity.
If something thinks something is elegant, but not simple, then what
they are probably describing is cleverness, not elegance.
John Y.
midrange.com
