day, different WLM
Thank you, everyone, for all the responses. What appeared to be an extra
level of difficulty surrounding a relatively simple problem now seems to
have so many answers it's difficult to select the right one!
I'll probably be going down the PERFORM= route for t
ity.
John
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Norman Hollander
Sent: 17 July 2005 20:33
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Different day, different WLM
Yes, "force" may be a bit strong. "Assign" may have been bette
cussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Mark Zelden
Sent: Sunday, July 17, 2005 SYSN 10:43 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Different day, different WLM
On Sat, 16 Jul 2005 11:06:19 -0700, Norman Hollander
<[EMAIL PROTECTED]> wrote:
>You can actually use a PERFORM= or SCHE
On Sat, 16 Jul 2005 11:06:19 -0700, Norman Hollander
<[EMAIL PROTECTED]> wrote:
>You can actually use a PERFORM= or SCHEDENV= on the Jobcard to force a Job
>into
>a particular Service Class. You may want to make it more specific by
>Jobname or Jobclass, or else everyone will find out about it. U
rritt
Sent: Saturday, July 16, 2005 SYSN 10:34 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Different day, different WLM
Have your scheduler run the job under a different ID. Then tell WLM. Use
this as a shop policy to control which jobs get higher juice. Security
folks may freak out, but don't ask
Yes and no. Most jobs have (or should have) a HOTBATCH service class.
Shuffling it in there sounds like the right thing to do. Issuing that
SVC 34 in a little program of ten lines or less (or even with the JES
mod that allows you to issue operator commands) can be done in about a
gazillion ways
Sent: Friday, July 15, 2005 3:13 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Different day, different WLM
Any hints/tips/warnings, please, on concepts surrounding the idea of
having a 'special' WLM policy that would get activated on specific
day(s)
(of the month)?
I have a situation where one p
...
Policy override isn't a good idea here since it will change the
entire SRVCLASS, not just a single job.
...
If you're willing to 'waste' an entire service class for one job (or set of
jobs), it's the simplest approach.
-teD
In God we Trust!
All others bring data!
-- W. Edwards Deming
---
On Fri, 15 Jul 2005 03:12:56 -0500, John Compton <[EMAIL PROTECTED]>
wrote:
>>I have a situation where one particular batch job becomes extra-important
>>on the '5th working day of the month', and at those times it needs extra
>>priority over other batch work.
>>Yes, we could manually change the
important job on the particular day you need it? And put that job name
in a high importance in your WLM?
Best regards,
Gary Diehl
| Subject: Differen
cc: (bcc: Joel Wolpert/SIAC)
|
| Subject: Differe
...
Someone here has raised the idea of having two policies, which would be
switched in and out automatically at the required time (persoanlly I think
that's opening a very large can of worms).
...
Not if the second policy is an override policy.
Both are stored at the same time.
You could have a s
<[EMAIL PROTECTED]>
Subject: Different day, different WLM
Any hints/tips/warnings, please, on concepts surrounding the idea of
having a 'special' WLM policy that would get activated on specific day(s)
(of the month)?
I have a situation where one particular batch job becomes extra-
Lots of places have different policies for day/night.
Nothing mystical that I'm aware of. Never seen the need myself, but each to
their own.
I find it strange that you would be able to successfully automate a policy
change, but not a service class change.
Odd, downright odd.
Shane ...
From: "Joh
Any hints/tips/warnings, please, on concepts surrounding the idea of
having a 'special' WLM policy that would get activated on specific day(s)
(of the month)?
I have a situation where one particular batch job becomes extra-important
on the '5th working day of the month', and at those times it needs
15 matches
Mail list logo
