I am reading about the WLM Managed Initiator possibility. As fas as I
understand, the option is designed to use it in a Sysplex environment with
mutiple systems. Are there any advantages and/or disadvantages when
activating it in a Monoplex environment (so only on a single system) or is it
of
Hi,
We would like to use WLM managed initiators for some of our classes.
The jobs running in these classes can only run on one of the systems in our
sysplex.
Is there a way to make sure that the jobs will run on oe system other that
using /*JOBPARM SYSAFF=?
TIA
Gadi
age-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ???
> Sent: Sunday, August 10, 2008 3:16 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: WLM managed initiators
>
> Hi,
>
> We would like to use WLM managed initiators for some of our classes.
Gadi, John,
>The WLM managed initiators are defined on a sysplex level. Once you tell
JES that a particular class is WLM managed, it will run jobs >on all (in
our case both) system in the sysplex.
WLM initiators are defined on a JESPLEX level, not a Sysplex Level. Of
course, if your Syspl
ama.ua.edu
Subject: WLM managed Initiators
I am reading about the WLM Managed Initiator possibility. As fas as I
understand, the option is designed to use it in a Sysplex environment with
mutiple systems. Are there any advantages and/or disadvantages when
activating it in a Monoplex environment (so
Works just fine in a MONOPLEX. I am doing it now. Additional initiators
are started/stopped based on the mix of work currently in the system. If
you have some mix of JES and WLM managed inits, this can be used (as one
example) to limit test/dev work when production is heavy.
Pay close attention to
On Wed, 13 Aug 2008 12:14:12 -0400, Stephen McColley <[EMAIL PROTECTED]>
wrote:
>I suppose I should have been a bit more specific - during our
>maintenance window we typically want to stop all initiator classes
>except one which we use to run our maintenance job in. The $PXEQ will
>stop everythin
Bob Rutledge wrote:
Yep, and it almost works for the Gadi's requirement :(
$TJOBCLASS(Q),XEQMEMBER(Z890)=(MAXIMUM=0)
$HASP003 RC=(08),T 344
$HASP003 RC=(08),T JOBCLASS(Q) XEQMEMBER(Z890) MAXIMUM - VALUE
$HASP003 IS OUTSIDE NUMERICAL RANGE, RANGE IS
$HASP003 (1-4294967295)
Looks like one of those packages - commercial, or non-commercial are
looking better and better.
Stephen McColley
On Wed, 2008-08-13 at 10:27 -0700, Edward Jaffe wrote:
> Bob Rutledge wrote:
> >
> > Yep, and it almost works for the Gadi's requirement :(
> >
> > $TJOBCLASS(Q),XEQMEMBER(Z890)=(MAXIMU
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ???
> Sent: Sunday, August 10, 2008 3:16 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: WLM managed initiators
>
> Hi,
>
> We would like to use WLM mana
>I'm not really very knowledgable about WLM initiators, but wouldn't it be
>possible to only tell the JES2 on a particular system to service a specific
>class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM defination in it. JES2 on
>SY2 has JOBCLASS(C) MODE=JES and does not have any "static" initi
Hi John,
The WLM managed initiators are defined on a sysplex level. Once you tell JES
that a particular class is WLM managed, it will run jobs on all (in our case
both) system in the sysplex.
We found this out the hard way.
Gadi
-Original Message-
From: IBM Mainframe Discussion List
age-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ???
> Sent: Sunday, August 10, 2008 3:16 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: WLM managed initiators
>
> Hi,
>
> We would like to use WLM managed initiators for some of our cl
On Sun, 10 Aug 2008 21:38:12 +, Ted MacNEIL <[EMAIL PROTECTED]> wrote:
John wrote:
>>I'm not really very knowledgable about WLM initiators, but wouldn't it be
possible to only tell the JES2 on a particular system to service a specific
class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM definati
>>I wouldn't mix up WLM & JES management in the same MAS.
>Why?
I was responding to John's comment about mixed for the same jobclass, I meant
what John said about two types of management for the same jobclass -- which at
the time I responded, I had forgotten that a jobclass is sysplex wide.
>
bci ao `ai wrote:
Hi,
We would like to use WLM managed initiators for some of our classes.
The jobs running in these classes can only run on one of the systems in our sysplex.
Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=?
This has
I prefer using scheduling environments. In our environment, we set up
scheduling environments to handle most jobs by supplying it in several JES2
exits.
However, one issue scheduling environments does not address is JCL
conversion. Conversion could occur on any system in the MAS. Most jobs ha
Actually, IBM recommends using both types of initiators depending on the
type of work. Specifically, production batch under JES2 and the rest
under WLM.
Anyway, Scheduling Environments will segregate the work. Define an
unique SE for each LPAR or member of the MAS, e.g. LPAR1, LPAR2 ...
Define a
Edward Jaffe wrote:
bci ao `ai wrote:
Hi,
We would like to use WLM managed initiators for some of our classes.
The jobs running in these classes can only run on one of the systems
in our sysplex.
Is there a way to make sure that the jobs will run on oe system other
that using /*JOBPARM
Bob Rutledge wrote:
Edward Jaffe wrote:
This has always been a trivial setting for JES3 (EXCRESC for the job
class group) and the lack of this capability in JES2 was a glaring
omission. To compensate, the most recent JES2 releases implement a
maximum XEQCOUNT by member by class.
XEQCOUNT has
Edward Jaffe wrote:
Bob Rutledge wrote:
Edward Jaffe wrote:
This has always been a trivial setting for JES3 (EXCRESC for the job
class group) and the lack of this capability in JES2 was a glaring
omission. To compensate, the most recent JES2 releases implement a
maximum XEQCOUNT by member by
Take care if you've assigned a resource group capping for these batch
because WLM doesn't take into account this type of delay (RGC-delay).
If your system is not saturated, WLM will continue to start new inits as more
jobs are submitted.
Regards
Hi,
We implemented WLM managed inits in our shop back at 1.7, and ran into
some of the same issues with WLM mangaged init - YES - if you change the
class to wlm managed it takes effect for the entire mas, and at least prior
to 1.9 (I haven't checked 1.9 yet), you could set a class limit but that
On Wed, 13 Aug 2008 08:50:09 -0500, Stephen G. McColley
<[EMAIL PROTECTED]> wrote:
> The problems can get more
>complex when you want to stop jobs on only one system for a maintenance
>window for example so this should not be unique to your shop...
>
That has never been a problem. $PXEQ is sing
I suppose I should have been a bit more specific - during our
maintenance window we typically want to stop all initiator classes
except one which we use to run our maintenance job in. The $PXEQ will
stop everything on that one system, and we still want to do some work -
it's just very selective.
25 matches
Mail list logo
