, namely for DB2
And for both RCCFXET and RCCFXTT AUTO should be in place.
Then there are a few that deserve consideration, such as INITIMP=E,
MT_ZIIP_MODE=2.
It is possible that the defaults will eventually change:-)
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
reasons and and the (significant) effort. And, to add some larger
context: For those installations that decide for themselves that the
consumption based Tailored Fit Pricing model is the right way to go the whole
capping discussion will become a moot point.
Horst Sinram - STSM, z/OS Workload
to
that partition; the way to go is really having sufficient zIIP capacity for
your workload peaks.
Horst Sinram - IBM z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
On z/OS, you can use SMF78.3 and the RMF IOQ report. Plus, there are some
related overview conditions.
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access
LOADxx, or you would be running out of the limit and you need
to utilize more logical processors. z/OS subsystems are usually well prepared
to deal with model changes.
Horst Sinram - STSM, z/OS Workload and Capacity Management
Hi Andy,
there are many different ways to obtain the workload name. The probably
simplest is to issue a Sysevent REQ(F)ASD against the space and find the
workload name in the IRARASD as RASDWKLD.
Horst Sinram - STSM, z/OS Workload and Capacity Management
in
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaw100/toc.htm
Horst Sinram - STSM, z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send emai
See SMF Type 90, subtype 30:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieag200/iea3g2_RESET_command_complete.htm
Horst Sinram - STSM, z/OS Workload and Capacity Management
--
For IBM-MAIN
describes the accounting scheme.
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
OS-WLM/WLM%20Documents.md
(It is NOT up and running as of today).
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with t
ch priority. Are you
definitively not interested in e.g. in enclave management?
- Is the "job" authorized?
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive a
to loop you would consider a multi period
goal using a *really huge* duration value. Even in that latter case a resource
group would be a better safety net.
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM
may consume some (or more) CPU
resources during initiation before classification is in effect. For such cases
there is the IEAOPTxx INITIMP parameter. Specifying INITIMP(E), or one of the
numeric values, depending on the workload to be protected can be useful to
minimize the spike effect due
In addition, by removing Global Performance Data Control authority one would
also disable some CPC-wide optimizations in z/OS HiperDispatch.
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM-MAIN
d BLWLINTHD IEAOPTxx parameter (BLWLTRPCT is almost never the
limiting fact).
Searching for OA44526 will give you a good list of recommendations.
DB2 and GRS locks are unrelated (except for allocation related ones).
Horst Sinram - STSM, IBM z/OS Wo
es_and_4HRA_Optimization_2016.pdf
you'll find some more details.
Horst Sinram - STSM, z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
freundlichen Gruessen
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
of an address space. Giving the
work unit a high priority can help increasing the parallelism because the
helper node would select by priority.
Horst Sinram - STSM, z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff
tion(s) on your DR backup sets
Horst Sinram - STSM, z/OS Workload and Capacity Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Sysevent REQLPDAT is z/OS only.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Sysevent REQLPDAT offers quite a bit more information than Sysevent QVS
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.iead200/iead200821.htm)
and could also be called unauthorized when that matters.
Horst Sinram - STSM, z/OS Workload and Capacity Management
Hi Kees,
sorry, there is no way to classify based on the existence/specification of a
work qualifier.
On z/OS V2.1 you could simplify your rules by creating a scheduling environment
group but it would still require that the group specification includes all your
scheduling environments.
Horst
Miklos,
it depends on the qualifier what variables are filled in. We intend to add
commentary to provide that information.
In the meantime, SYS1.SAMPLIB(IRAEN55S) has a sample exit that you may find
useful.
Kind regards / Mit freundlichen Gruessen
Horst Sinram - IBM z/OS Workload Management
Personal Communications Version 6.0 supports up to 52 sessions. See
http://pic.dhe.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=%2Fcom.ibm.pcomm.doc%2Freadme%2FreadV60.html
I think you need to use sessions A-Z and a-z -- but I never tried myself :-)
Horst Sinram - IBM z/OS Workload Management
the AORs) with the full
transaction reporting that you would get from Manage to Goal of Transactions.
It's primarily useful for systems where CICS is the predominant workload. (And,
yes, I have seen data from quite a few large sites using it very successfully.)
Horst Sinram - IBM z/OS Workload
in it.
Horst Sinram - IBM z/OS Workload Management
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
. These APIs
could be used through some products (e.g. Tivoli System Automation ProcOps), or
you could (probably, but I did not verify that all operations are supported
e.g. in z/OS BCPii) come up with homegrown automation.
Horst Sinram - IBM z/OS Workload Management
CPU Management such that there is no reason why one
would want to continue with the old management in a HD=YES environment
Horst Sinram - z/OS Workload Management
--
For IBM-MAIN subscribe / signoff / archive access instructions
distribution of your workload within the LPAR cluster
has changed or not, and how long the capping situation persists (with pattern
capping there is obviously a much better chance.)
Horst Sinram - IBM z/OS Workload Management
--
For IBM
of your resource group (i.e. system or Sysplex),
and the amount of work running at a higher priority you may well end up at that
order of magnitude for the achievable granularity for *that* resource group in
your environment.
Horst Sinram - IBM z/OS Workload Management
work
queues...
CPUMF counters won't help you diagnosing anything. CPUMF sampling could help
-theoretically- but the data may be very hard to evaluate.
Horst Sinram - IBM z/OS Workload Management
--
For IBM-MAIN subscribe
10 seconds.
In the MVS System Management Facilities (SMF) book
(http://publibz.boulder.ibm.com/epubs/pdf/iea2g2c1.pdf) you can find a summary
of what subtypes are written. And subtype 12-14 are written every 2 sec but
they are very small as well.
Kind regards - Horst Sinram
IBM z/OS Workload
32 matches
Mail list logo
