RE: IBM job scheduler

[Gary Thompson <gthompson@xxxxxxxxxxx>]

Maybe look at API Overview and Concepts 7.1 
- there is an example of changing the user for a JSE

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, March 15, 2013 7:29 AM
To: Midrange Systems Technical Discussion
Subject: Re: IBM job scheduler

Hold which job queue?
If I have a few hundred job schedule entries, scattered across multiple job queues, which magic job queue do I hold that will stop the job scheduler from submitting any of them?


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:   "Raul A. Jager W." <raul@xxxxxxxxxx>
To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, 
Date:   03/15/2013 09:22 AM
Subject:        Re: IBM job scheduler
Sent by:        midrange-l-bounces@xxxxxxxxxxxx



You can hold the "jobq"

CRPence wrote:

> On 14 Mar 2013 13:11, Michael Smith wrote:
>
>
> > The specific requirement is
> > 1> "hold" the job scheduler before an Go Save>Opt 21 is executed so
> > that "jobs" including the job scheduler jobs will not be allowed to run
> > after the Opt 21 is completed
> > 2> We will then be able to perform business tasks, including but not
> > limited to OS upgrades, RCLSTG.
> > 3>  Execute the QSTRUP program, "release" the job scheduler