RE: advanced job schedule and restore to new hardware

Jim,

GO JS
11. Work with AJS job monitors
Automatically start monitor . . *YES
Change this to *NO.

Automatically start monitor (AUTOSTART) - Help
Specifies whether the job monitor is to be automatically
started after an IPL. The job monitor will not be
automatically started if the Monitor field is set to *NO.

This prevents the monitor job from starting, which controls the AJS jobs.
In the screen shot below, we have AJS setup for multiple environments, each environment has its own monitor job.

After the maintenance is complete, manually start the monitor job, and set auto back to *yes.

Data Job Auto
Library Monitor Monitor Start Status Text
D1JS D1JS *YES *YES *ACTIVE D1 Slice
ITJS ITJS *YES *YES *ACTIVE IT Slice
MSJS MSJS *YES *YES *ACTIVE MS Slice
P1JS P1JS *YES *YES *ACTIVE P1 Slice
QUSRIJS QIJSSCD *YES *YES *ACTIVE Pencor06 base system
SPJS SPJS *YES *YES *ACTIVE SP Slice
TPJS TPJS *YES *YES *ACTIVE TP Slice
UPJS UPJS *YES *YES *ACTIVE UP Slice

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, June 23, 2014 2:04 PM
To: Midrange Systems Technical Discussion
Subject: Re: advanced job schedule and restore to new hardware

Well, there's always CHGIPLA and tell it to start the system in a restricted state. Failing that, you could set that lpar to "Manual"
versus "Normal". Makes the upgrade process a little more "interesting", but it's documented. And there's a stage during the manual mode where you can tell it to start in restricted state.
There's also changing the system value QSTRUPPGM to some highly restricted program.

For the standard job scheduler we have a process that holds all entries and records those it held, which were not already held. When we want them to run a process releases those which were not already held is ran. Some intelligence is built into that to say if the "Recovery action" was *SBMRLS then submit the job right away.
You could probably duplicate this for the advanced job scheduler.


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: Jim Franz <franz9000@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/23/2014 01:49 PM
Subject: advanced job schedule and restore to new hardware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Looking at AJS in our plan to restore to new hardware.
We need the system up in a minimal way (QSYS/QSTRUP), to apply license
keys
for some products. Not all like IBM where we can run days without the
keys.
Our first test, the subsystems all came up from our customized startup,
and
several apps immediately crashed.
How do I keep the AJS from starting on the first IPL? We don't want AJS
submitting all the missed jobs till we are ready.
A "hold" command would be nice.

Jim Franz