Bob Stark wrote:
In all the years since this post, has anyone come up with a new, good,
foolproof way to have one LPAR in a JES2 SYSPLEX only run SYSPROG jobs
during a test window?
This is easy in JES3 since job class groups -- no JES2 equivalent -- may
be individually activated or inactivated at a system level.
In our shop, we have groups called BATCH, PRODWORK, SOFTWARE, ONLINE,
and SYSPROG.
To stop all jobs from being scheduled in all groups on all systems in
the JESplex, we issue (in a script):
*F,G,ALL,G,BATCH,OFF
*F,G,ALL,G,PRODWORK,OFF
*F,G,ALL,G,SOFTWARE,OFF
*F,G,ALL,G,ONLINE,OFF
*F,G,ALL,G,SYSPROG,OFF
Then, we can selectively activate any group on any system we want. For
example, to allow only sysprog jobs to run on MVS70, we would issue:
*F,G,MVS70,G,SYSPROG,ON
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
