Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
BATCHCOM ALTER SCHEDULER INITIATION OFF
330 views
Skip to first unread message
rip uno
Jul 29, 2014, 5:12:00 PM7/29/14
to
We are preparing for a potential scheduled shutdown of multiple days and when coming back up will reuire a few days of manual runs to come back up to schedule.
My suggestion was to shut the INITIATION off in BATCHCOM and then turn it back on when we were ready to resume operations but the question arose "What about jobs that were set to run during those days the INITIATION was turned off?" Would they automatically start up and run?
My thoughts are that the 'next-runtime' setting would get "reset" when the INITIATION is turned back on and past dates would be reset driven by their calendar or the "every" variable and wouldn't run first.
If I had a jobs with the specs below and we shut down on 28 July and then started the INITIATION back up on 5 August 08:00 - would this job run immediately or wait until 15:00?
JOB ATTRIBUTES for REPORT-MAILER-PROD
jobnumber: 9
volume: \node.$DATA00.PRODOPR, "AGGG"
in: \node.$DATA00.PRODOPR.MGA235O
out: \node.$T.#MGA235.MAIL
executor-program: \node.$SYSTEM.SYSTEM.TACL
pfs: 0
pri: 140
selpri: 3
maxprintlines: None
maxprintpages: 4000
class: DEFAULT
stall: Off
stop-on-abend: Off
calendar: \node.$DATA00.NETCAL.EVRY1500
after: 24MAY12 15:00:00
iffails: On
highpin: Off
submit: 30JUN12 10:06:54
alter: 30JUN12 10:06:54
user: 9,255
next-runtime: 29JUL14 15:00:00
Any thoughts?
My suggestion was to shut the INITIATION off in BATCHCOM and then turn it back on when we were ready to resume operations but the question arose "What about jobs that were set to run during those days the INITIATION was turned off?" Would they automatically start up and run?
My thoughts are that the 'next-runtime' setting would get "reset" when the INITIATION is turned back on and past dates would be reset driven by their calendar or the "every" variable and wouldn't run first.
If I had a jobs with the specs below and we shut down on 28 July and then started the INITIATION back up on 5 August 08:00 - would this job run immediately or wait until 15:00?
JOB ATTRIBUTES for REPORT-MAILER-PROD
jobnumber: 9
volume: \node.$DATA00.PRODOPR, "AGGG"
in: \node.$DATA00.PRODOPR.MGA235O
out: \node.$T.#MGA235.MAIL
executor-program: \node.$SYSTEM.SYSTEM.TACL
pfs: 0
pri: 140
selpri: 3
maxprintlines: None
maxprintpages: 4000
class: DEFAULT
stall: Off
stop-on-abend: Off
calendar: \node.$DATA00.NETCAL.EVRY1500
after: 24MAY12 15:00:00
iffails: On
highpin: Off
submit: 30JUN12 10:06:54
alter: 30JUN12 10:06:54
user: 9,255
next-runtime: 29JUL14 15:00:00
Any thoughts?
Robert Hutchings
Jul 30, 2014, 5:08:56 PM7/30/14
to
I think most people would have to research this...download the NetBatch manual(s) and poke around. Maybe I will have some time tomorrow AM to do that...
rip uno
Aug 1, 2014, 10:51:45 AM8/1/14
to
On Wednesday, July 30, 2014 2:08:56 PM UTC-7, Robert Hutchings wrote:
> I think most people would have to research this...download the NetBatch manual(s) and poke around. Maybe I will have some time tomorrow AM to do that...
I have gone through the NetBatch manual which is less than forthcoming in this area. We set up a Test scheduler and so far, our results are not working in our favor. We set up a job (sends s print job to the spooler) to run every 20 minutes. We let it run several times. We then shut off initiation and waited for an hour and turned initiation back on - it kicked out 3 print jobs.
> I think most people would have to research this...download the NetBatch manual(s) and poke around. Maybe I will have some time tomorrow AM to do that...
wbreidbach
Aug 1, 2014, 3:12:58 PM8/1/14
to
rip uno
Aug 4, 2014, 7:32:43 PM8/4/14
to
On Friday, August 1, 2014 12:12:58 PM UTC-7, wbreidbach wrote:
> Am Freitag, 1. August 2014 16:51:45 UTC+2 schrieb rip uno: > On Wednesday, July 30, 2014 2:08:56 PM UTC-7, Robert Hutchings wrote: > > > I think most people would have to research this...download the NetBatch manual(s) and poke around. Maybe I will have some time tomorrow AM to do that... > > > > I have gone through the NetBatch manual which is less than forthcoming in this area. We set up a Test scheduler and so far, our results are not working in our favor. We set up a job (sends s print job to the spooler) to run every 20 minutes. We let it run several times. We then shut off initiation and waited for an hour and turned initiation back on - it kicked out 3 print jobs. Have you tried to set all the job in HOLD before shutting down the scheduler? After warmstart, alter the state to HOLD OFF. From my experience this solution should work.
No, we haven't tried that, but it might be the only solution available to us although that could end up being quite labor intensive as we run an extensive number of jobs through our scheduler.
> Am Freitag, 1. August 2014 16:51:45 UTC+2 schrieb rip uno: > On Wednesday, July 30, 2014 2:08:56 PM UTC-7, Robert Hutchings wrote: > > > I think most people would have to research this...download the NetBatch manual(s) and poke around. Maybe I will have some time tomorrow AM to do that... > > > > I have gone through the NetBatch manual which is less than forthcoming in this area. We set up a Test scheduler and so far, our results are not working in our favor. We set up a job (sends s print job to the spooler) to run every 20 minutes. We let it run several times. We then shut off initiation and waited for an hour and turned initiation back on - it kicked out 3 print jobs. Have you tried to set all the job in HOLD before shutting down the scheduler? After warmstart, alter the state to HOLD OFF. From my experience this solution should work.
We have given thought to saving the existing jobs out to a saved obey-form and clearing out the scheduler then when ready to come back up, import the jobs back in. We are planning a test of this method later this week to see how it reacts.
0 new messages