: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES2 job execution routing
On Thu, 26 Jan 2006 09:25:55 -0600, Hal Merritt wrote:
>
> We are now running most all our work on z/os.e. We have a z/os LPAR in
>the MAS for exceptions such as TSO. What we would like is for jobs
>submitted on z/os to be e
On Thu, 26 Jan 2006 09:25:55 -0600, Hal Merritt wrote:
>
> We are now running most all our work on z/os.e. We have a z/os LPAR in
>the MAS for exceptions such as TSO. What we would like is for jobs
>submitted on z/os to be executed on z/os.e unless explicitly routed.
>
>We dislike exits. We have a
On 1/26/2006 10:48 AM, Hal Merritt wrote:
We are now running most all our work on z/os.e. We have a z/os LPAR in
the MAS for exceptions such as TSO. What we would like is for jobs
submitted on z/os to be executed on z/os.e unless explicitly routed.
...snipped...
I feel sure this has been di
How about WLM Resources and Scheduling Environments? You could define a
default scheduling environment to all the job classes through the SDSF JC
screen. Then define a resource connected to the scheduling environment that
is on for the little MVS, and off for the big MVS. Have another scheduling
We are now running most all our work on z/os.e. We have a z/os LPAR in
the MAS for exceptions such as TSO. What we would like is for jobs
submitted on z/os to be executed on z/os.e unless explicitly routed.
We dislike exits. We have a grand total of two and that's two too many.
I feel
5 matches
Mail list logo
