On Thu, 2 Jul 2009 06:38:17 -0500, Barbara Nitz <[email protected]> wrote:
>WLM- Initiators:
>Someone here had changed the 'sysprog class' (the only one open right after
>IPL) to WLM-managed (and didn't care about the serviceclass).
>
>IPL'd of one system in order to upgrade a database to a new release. Used the
>class for sysprogs (which traditionally under JES2 would lead to the job being
>converted and executed on the system it was submitted). Fell flat on my face
>with an abend806 for the product to be upgraded. Panic. Why the hell is the
>new product not working? The 'missing' module is in linklist!
>
>It took me quite a while to figure out that the job had been routed by WLM
>(despite an open initiator on a system without *any batch*) to a system it
>shoudn't/cannot run on! Not having the command ready to make it JES-
>managed again and not using the sysaff statement correctly, it took me a
>good 45 minutes to get that job to run on the system it was supposed to run!
>
>(To explain further, we do NOT use SYSAFF. Our system-affinity is set by
>specifying an init that only exists on *that* system!)
>
>So don't tell me how great WLM-managed inits are! They're not. We're 1.8.
>Regards, Barbara Nitz
Sad story. :-) But just because "someone" changed something they
shouldn't have or decided to use WLM inits without planning, doesn't make
them bad. You could have used SYSAFF (unless you have some exit
preventing you), you also could have SCHENV defined and activated on
the LPAR you needed to run on. In our sysplexes that use SCHENV (the
others use ThruPut manager binds... around long before SCHENV) there
is a "SYSAFF" type of SCHENV (one per system) in addition to all the other
SCHENVs.
For a complete opposite view: Our very first use of WLM inits was for
a single sysprog class. Just like you are talking about... the one we
could use during maintenance windows. During our change windows all
the JES2 inits are drained and all a $PXEQ is issued. The sysprogs can
then submit jobs to the WLM jobclass and force them to run when and
where they want to (without SYSAFF) by using $SJOB ("J" next to the job
in the input queue in SDSF).
Regards,
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[email protected]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
----------------------------------------------------------------------
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
