Replying on both lists ---
Thanks for all the great ideas. I went with the CHGJOBSCDE and its been
moving along nicely all day.
Thanks,
Steve
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Darren
Strong
Sent: Thursday, November 19, 2020 07:41
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Recurring Interval Job
I run the processes as a scheduled job that does a CHGJOBSCDE at the end of
processing. The advantage of this is that it's easy to hold the process to
stop it, as opposed to have 24 or 48 scheduled jobs to deal with. Starting
it means releasing and running the job schedule entry.
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve M
via RPG400-L
Sent: Wednesday, November 18, 2020 6:00 PM
To: 'RPG programming on IBM i' <rpg400-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve M <txpenguin1@xxxxxxxxxxx>
Subject: Recurring Interval Job
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
It sure seems like there should be an easier way to do this, so let's see
what everyone's done before.
I have an RPGLE program that needs to run at 15 and 45 minutes past the
hour, every hour, every day, exactly. There are other dependent jobs, so
the timing is important.
We have ROBOT installed, but when you use the job interval (run every 30
minutes) option, you lose the ability to choose the time the job runs the
first time; it's as soon as you place it into ROBOT. That's great right up
until we do an IPL each week and the return time from the IPL varies and
ROBOT would submit the first run of the job as soon as it returned from the
IPL (odds are that's not exactly on 15 or 45 past the hour). So that's not
a player.
The easiest solution has always been to create a CLLE that's submitted from
ROBOT (at a specific time each week sufficiently after the IPL on either a
15 or 45), and have that job then submit the RPGLE program and then do a
DLY(1800) and continue like that until the next IPL. I'm trying not to put
a never-ending job on the system, if possible, that spends 99.999% of it's
time just taking up space and being tracked by the system.
Has anyone come up with a better way to have a job execute (in this case
twice per hour), at a specific time, that doesn't involve having a
never-ending job running in the background?
Thanks,
Steve
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
