Steve is having a little trouble posting to IBM-Main, so I am posting
this for him. See below:
Howdy,
I didn't catch the beginning of this thread, but I would like you to
know that the Mellon Mods are alive and well! Although I decided a year
or so ago that we should start calling them the SHARED SPOOL MODS, since
I have maintained them for a dozen or so years now, and have done a
completed re-write twice in that time. ANYWAY, they can still be found
on the CBT TAPE website, go to "latest updates are always available to
download here" (at the bottom of the light blue box) then scroll down to
file # 766, Shared Spool Mods- "Mellon" for JES2 z/OS1.7 and 1.8. I
will do 1.9 after we get it ordered ourselves.
I have included in this distribution an INSTALLATION MANUAL, an
OPERATIONS COMMAND MANUAL, and a USER'S MANUAL to explain everything
better than in the past. We can now handle a number of different
methods of controlling how and when jobs do and do not become eligible
for selection including the following:
/*AFTER jobname (allow execution after jobname jobname runs)
/*BEFORE jobname ( same as after, but before!)
/*WITH jobname (only run if and where jobname jobname runs)
/*WITHOUT jobname (run where jobname is not running)
/*HOLDFOR hh:mm:ss (hold the job in the input queue for hh:mm:ss)
/*HOLDTIL hh:mm:ss (hold the job on the input queue until
hh:mm:ss)
/*CNTL resname,EXC (control execution of a number of jobs using
/*CNTL resname,SHR an arbitrary resname, and EXCLUSIVE or
SHARED Control(same basic logic as an ENQ but for
jobs).
/*ROUTE XEQ resname for compatibility - works just like SCHENV=
This was the original reason for these
mods.
Those are the features that are used by the users - the JCL coders.
On the operations side of things, we have begun cutting some SMF
records for some many of the actions we take. We have enhanced the $DJ
command to display reasons that a job may be delayed while in the input
queue. We implemented a number of changes specifically because of WLM
managed inits including, the ability to limit (or stop) the number of
jobs started on any lpar, for a given class, the ability to limit the
number of total jobs that match a specific jobmask, or userid mask, this
prevents one user or group of users from monopolizing resources. The
ability to limit jobs by class, within a single LPAR, gives us the
ability to use WLM managed inits for classes that must not be allowed to
execute on all systems - tape class jobs are limited in our shop for
instance and not allowed to run on some of our lpars, while WLM still
manages the class on the remaining lpars in the MAS. There are other
real advantages to limiting or stopping WLM managed jobs by class when
you start into a maintenance window if you think about it.
As has been the case for at least the last eight years, no changes to
JES2 code, this is all implemented via exits, all source is provided,
and is packaged in SMP/E format. PLUS, if anyone tells me they installed
them, I have a box of coffee cups in my basement that all say "I
INSTALLED THE SHARED SPOOL MODS", that I am still trying to give away. I
just need to know where to send them.
Future changes that I plan to make include Automatic resource routing
based on Program or PROC names. Automatic job Classing (changes the
jobclass) based on program or proc, or owning userid, step completion
notification options, HSM dataset recall at job reader time (or just
prior to job execution time for time delayed jobs), and others. In
short - if you haven't looked at the Shared Spool Mods lately - you
probably should, they do a lot more now, and will do even more in the
near future.
[EMAIL PROTECTED]
Stephen McColley
Enterprise Information Services
SunTrust Banks, Inc.
Tel: 404.230-5182
---------------------------------------------------------
Robert B. Richards (Bob)
US Office of Personnel Management
1900 E Street NW Room: BH04L
Washington, D.C. 20415
Phone: (202) 606-1195
Email: [EMAIL PROTECTED]
---------------------------------------------------------
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of David Cole
Sent: Tuesday, May 27, 2008 11:18 AM
To: [email protected]
Subject: Re: Controlling the execution sequence of dependant jobs in
JES2 (a suggested fix)
snipped
----------------------------------------------------------------------
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
