Classification: Confidential

1) reduce the number of service class periods and service classes
2) reduce the numberf of workloads
3) set CICS MAXTASKS to a reasonable number
4) Since this is a development system, set your major subsystems to velocity 
goals, not transaction goals (IMS, CICS, DB2, MQ)

This is a combination of experience and remembrance from a WLM training class.

Most people try to over-control WLM instead of letting it do its thing.\

HTH,


-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Wendell Lovewell
Sent: Monday, March 4, 2024 5:08 PM
To: [email protected]
Subject: How to reduce the overhead of WLM?

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

This is probably a strange question, but is there a way to reduce WLM cpu 
usage?   Here's the situation:

- The system is a lightly used development system.  Unless something is in a 
loop (very rare), CPU % probably is usually less than 10%.  And except for 
system regions & CICS, it's rare to have multiple jobs running concurrently.
- Only one processor defined to the VM. No ZIIP either.
- We are charged for CPU cycles.
- WLM is the highest consumer of CPU.  JES2, TCPIP, ZFS and SDSFAUX round out 
the top 5 consumers.

There is a lot of information about WLM tuning, but as best I can tell almost 
none of it relates to reducing WLM usage.

From reading the Init & Tuning manual, I'm trying these settings:
AIMANAGEMENT=NO
HIPERDISPATCH=NO
CCCAWMT=450000
RMPTTOM=15000

I was thinking that perhaps reducing whatever processing intervals I could 
might help.  But I can't tell these changes made a difference.  (I don't have a 
tool to measure WLM usage.)

Any suggestions would be appreciated.

TIA,

Wendell

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] 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 [email protected] with the message: INFO IBM-MAIN

Reply via email to