Discussion:
Job await main select and cannot execution
Add Reply
Tommy Tsui
2017-10-06 10:21:23 UTC
Reply
Permalink
Raw Message
Hi all,
We are running in wlm mode with schedule environment, wlm managed all
class with xeqcount=200, but we don't know why when all new jobs reached
around 20, and CPU reached 100% all other new coming job will be in "job
await main select" status, we don't know why, is it CPU reached 100%, and
wlm decided not to start more initiator? Can we force to start new jobs?
The mode is correct , in wlm mode both side
The job class are defined as wlm managed,


Any help will be appreciated

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lucas Rosalen
2017-10-06 10:43:21 UTC
Reply
Permalink
Raw Message
If you're running z/OS 2.2 (maybe 2.1 as well) there's an JES2/WLM APAR
that might be of interest.
I don't have its number now, but you might find it in some discussions on
this forum.

Lucas
Post by Tommy Tsui
Hi all,
We are running in wlm mode with schedule environment, wlm managed all
class with xeqcount=200, but we don't know why when all new jobs reached
around 20, and CPU reached 100% all other new coming job will be in "job
await main select" status, we don't know why, is it CPU reached 100%, and
wlm decided not to start more initiator? Can we force to start new jobs?
The mode is correct , in wlm mode both side
The job class are defined as wlm managed,
Any help will be appreciated
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lucas Rosalen
2017-10-06 11:06:39 UTC
Reply
Permalink
Raw Message
Back to my desk, it looks like APAR that I refer to is OA51343.

Lucas
Post by Lucas Rosalen
If you're running z/OS 2.2 (maybe 2.1 as well) there's an JES2/WLM APAR
that might be of interest.
I don't have its number now, but you might find it in some discussions on
this forum.
Lucas
Post by Tommy Tsui
Hi all,
We are running in wlm mode with schedule environment, wlm managed all
class with xeqcount=200, but we don't know why when all new jobs reached
around 20, and CPU reached 100% all other new coming job will be in "job
await main select" status, we don't know why, is it CPU reached 100%, and
wlm decided not to start more initiator? Can we force to start new jobs?
The mode is correct , in wlm mode both side
The job class are defined as wlm managed,
Any help will be appreciated
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Marchant
2017-10-06 12:08:48 UTC
Reply
Permalink
Raw Message
Post by Tommy Tsui
We are running in wlm mode with schedule environment, wlm managed all
class with xeqcount=200, but we don't know why when all new jobs reached
around 20, and CPU reached 100% all other new coming job will be in "job
await main select" status, we don't know why, is it CPU reached 100%, and
wlm decided not to start more initiator?
WLM manages the number of initiators based upon resources available and
the goals that you have set. If your goals are too aggressive and are not
being met, WLM is less likely to start more initiators.

CPU at 100% suggests to me that the system can't productively do more
work. What do you hope to accomplish by having more jobs running?

If you are using all the available CPU resources and you start twice as
many similar jobs, they will likely all run twice as long. Perhaps longer
because of additional work required to manage the additional jobs, and
possible shortage of other resources, such as memory.
Post by Tommy Tsui
Can we force to start new jobs?
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.
--
Tom Marchant

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Peter Hunkeler
2017-10-06 15:15:23 UTC
Reply
Permalink
Raw Message
Post by Tom Marchant
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.


Yes it does. It's the "R" action character in (E)JES. I never cared to look what the resulting JES3 command is.
--
Peter Hunkeler

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tommy Tsui
2017-10-06 15:43:01 UTC
Reply
Permalink
Raw Message
I am interesting how the WLM manages the number of initiators based upon
resources available and where to set
the goals ? For initiators
Post by Tom Marchant
Post by Tom Marchant
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.
Yes it does. It's the "R" action character in (E)JES. I never cared to
look what the resulting JES3 command is.
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Allan Staller
2017-10-06 16:27:08 UTC
Reply
Permalink
Raw Message
Try here:

http://www-03.ibm.com/systems/z/os/zos/features/wlm/WLM_Further_Info.html

Scroll down to " Specific WLM Functions"

There are 3 papers related to WLM batch initiators.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tommy Tsui
Sent: Friday, October 6, 2017 10:44 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: Job await main select and cannot execution

I am interesting how the WLM manages the number of initiators based upon resources available and where to set the goals ? For initiators
Post by Tom Marchant
Post by Tom Marchant
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.
Yes it does. It's the "R" action character in (E)JES. I never cared to
look what the resulting JES3 command is.
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2017-10-06 16:32:02 UTC
Reply
Permalink
Raw Message
Tommy,

This is not a science, but an art. So it takes time and study and adjustments to get WLM where you want it.

The first phase is understanding how WLM works. This written up in many manuals. It is not quick to learn. If you have a sandbox where you can work things out, that would be best.

This has to do with system capacity. How much work can the system run? How much work do you want the system to run.

If you do not have sufficient resources, MIPs, Storage, Memory, then WLM will not run more work than it has resources available.

Yes you can tell WLM to try and run more work than it has resources for, but then your processes run longer and are waiting longer for resources.


What problem are you trying to solve? If WLM has jobs in awaiting main status (this is a JES2 message in SDSF), then the system does not have sufficient MIPS, MEMORY, STORAGE to run the tasks.

You may want to start, if you have not done so, reviewing this Redbook

System Programmer's Guide to: Workload Manager

http://www.redbooks.ibm.com/abstracts/sg246472.html?Open


It can help with understanding this process.

The section on setting goals could be helpful
This chapter discusses tips to:
 Manage your service definition.
 Use a service class.
 Select the type of goals to use.
 Use Resource Groups.


Lizette
Post by Allan Staller
-----Original Message-----
Behalf Of Tommy Tsui
Sent: Friday, October 06, 2017 8:44 AM
Subject: Re: Job await main select and cannot execution
I am interesting how the WLM manages the number of initiators based upon
resources available and where to set the goals ? For initiators
Post by Tom Marchant
Post by Tom Marchant
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.
Yes it does. It's the "R" action character in (E)JES. I never cared to
look what the resulting JES3 command is.
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tommy Tsui
2017-10-07 07:57:46 UTC
Reply
Permalink
Raw Message
Thanks all, information, I will try
Post by Lizette Koehler
Tommy,
This is not a science, but an art. So it takes time and study and
adjustments to get WLM where you want it.
The first phase is understanding how WLM works. This written up in many
manuals. It is not quick to learn. If you have a sandbox where you can
work things out, that would be best.
This has to do with system capacity. How much work can the system run?
How much work do you want the system to run.
If you do not have sufficient resources, MIPs, Storage, Memory, then WLM
will not run more work than it has resources available.
Yes you can tell WLM to try and run more work than it has resources for,
but then your processes run longer and are waiting longer for resources.
What problem are you trying to solve? If WLM has jobs in awaiting main
status (this is a JES2 message in SDSF), then the system does not have
sufficient MIPS, MEMORY, STORAGE to run the tasks.
You may want to start, if you have not done so, reviewing this Redbook
System Programmer's Guide to: Workload Manager
http://www.redbooks.ibm.com/abstracts/sg246472.html?Open
It can help with understanding this process.
The section on setting goals could be helpful
Manage your service definition.
Use a service class.
Select the type of goals to use.
Use Resource Groups.
Lizette
Post by Allan Staller
-----Original Message-----
<javascript:;>] On
Post by Allan Staller
Behalf Of Tommy Tsui
Sent: Friday, October 06, 2017 8:44 AM
Subject: Re: Job await main select and cannot execution
I am interesting how the WLM manages the number of initiators based upon
resources available and where to set the goals ? For initiators
Post by Tom Marchant
Post by Tom Marchant
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.
Yes it does. It's the "R" action character in (E)JES. I never cared to
look what the resulting JES3 command is.
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Edward Finnell
2017-10-08 02:39:07 UTC
Reply
Permalink
Raw Message
Cheryl has gobs of info at her website www.watsonwalker.com with notes and howtos from her tuning newsletter and numerous SHARE presentations. Couple of products GOAL Tender and Box Score?
 
Understanding all the tuning mechanatians of z/MVS is a formidable undertaking but judiciously applied can increase thruput and prevent unplanned outages and/or upgrades.
 
In a message dated 10/7/2017 2:59:08 AM Central Standard Time, ***@GMAIL.COM writes:

 
Thanks all, information, I will try

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Ed Jaffe
2017-10-13 12:10:52 UTC
Reply
Permalink
Raw Message
Post by Tom Marchant
Post by Tom Marchant
In JES2, you can issue $S JOB and WLM will start another initiator for
that job. Your message suggests to me that you are JES3. I don't know
if JES3 has a similar function.
Yes it does. It's the "R" action character in (E)JES. I never cared to look what the resulting JES3 command is.
In JES3, the (E)JES 'RUN' line command generates the '*F,J=jobnum,RUN'
command. In JES2, it generates the $SJ(jobnum) command.
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Allan Staller
2017-10-06 13:02:21 UTC
Reply
Permalink
Raw Message
You are describing what appears to be on the surface, normal WLM behavior.
You should note that XEQCOUNT is a max allowed, not a minimum.

Possible reasons for WLM not starting additional jobs/initiators:
1) XEQCOUNT is a maximum and is enforced by JES, not WLM and is thus irrelevant to this discussion
2) Workload mix was meeting goals. No action needed by WLM
2) Corollary: improper goal setting
3) CPU "saturation" indicated to WLM that starting additional initiators would not help performance would reduce performance.
4) more important workloads needed help as opposed to batch
5) many many other possibilities

There are too many possibilities to list them all. Since I don't have a copy of your WLM policy, the best I can do is a WAG, not even a SWAG.
The only way to know for sure what WLM is thinking is to turn on SMF99 and sent the info to IBM for analysis.

You can force jobs to start via SDSF or console command. IIRC, in SDSF a "j" command for the job will cause it to start.
Check the fine manuals in case I have a memory fault.

HTH,



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tommy Tsui
Sent: Friday, October 6, 2017 5:23 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Job await main select and cannot execution

Hi all,
We are running in wlm mode with schedule environment, wlm managed all class with xeqcount=200, but we don't know why when all new jobs reached around 20, and CPU reached 100% all other new coming job will be in "job await main select" status, we don't know why, is it CPU reached 100%, and wlm decided not to start more initiator? Can we force to start new jobs?
The mode is correct , in wlm mode both side The job class are defined as wlm managed,


Any help will be appreciated

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Loading...