We reverse the process when we swap back. Any changes made to the "production" job scheduler are updated to the original production machine and vice versa.
Normal:
System A = Source; System B=Target
Swap:
Save on A. Hold all. Send save to B.
Save on B. Send Save to A.
Restore A on B; Restore B on A.
Swap back:
Save on B. Send save to A.
Save on A. Send save to B.
Restore B on A; Restore A on B.
Now the original job schedule entries are back on the original system, including any changes that were made while swapped.
Since our swaps have historically been just for a short test, we skipped the "Restore B on A" during the Normal->Swapped part, but it's simple code.
--
Sean Porterfield
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, March 20, 2013 09:08
To: Midrange Systems Technical Discussion
Subject: RE: IBM job scheduler
<snip>
We use the SAVOBJ QDFTJOBSCD, HLDJOBSCDE *ALL *ALL method then just RSTOBJ to return to the way it was. (Chuck mentioned this as well.) </snip>
Not a bad technique. A minor concern may be what if other changes were made after the HLDJOBSCDE? If you're just bouncing your server and you just want to ensure that jobs don't start that's one thing. If you're running for an extended length of time (like a H/A switch) that's another.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Porterfield, Sean" <SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/20/2013 08:40 AM
Subject: RE: IBM job scheduler
Sent by: midrange-l-bounces@xxxxxxxxxxxx
-----Original Message-----
From: Voris, John
From: Rob Berendt
We wrote code, using the job scheduler APIs, to hold any entry not
already held, and log those held to a file. Later we can run a
command to release all job scheduler entries that are in the file.
We have hundreds of job schedule entries. An untold number of them
are always on hold. When we do an HA switch from PROD to BACKUP we do
not want ANY of the job scheduler entries on PROD going active.
Rob Berendt
Could you post the code for that?
It would certainly help those in small shops doing WRKJOBSCE *PRINT and
manually putting things on hold and take them off hold later.
It might make for a great article too.
- John V
We use the SAVOBJ QDFTJOBSCD, HLDJOBSCDE *ALL *ALL method then just RSTOBJ
to return to the way it was. (Chuck mentioned this as well.)
--
Sean Porterfield
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.
midrange.com
