IBM Systems Magazine, Mainframe - July/August 2018 - 52
implementation is by using the
content solution. For more details,
see "A Content Solution for
Container Pricing for IBM Z" below.
When you run SCRT, the
DevTest solution LPARs no
longer contribute to the
traditional R4HA product peaks. Instead, they're
isolated to a separate section of the SCRT report.
No other implementation steps are required to
get things going, but in addition to this SCRT
setup, you should review the goals of soft-capping
and other software cost controls used on your
development and test LPARs.
A Content Solution for Container Pricing
for IBM Z
To help you understand and implement Container Pricing for IBM Z*, we
worked in a new way, using IBM Design Thinking and repeated interaction with
clients to produce a content solution, which is a comprehensive set of information and user assistance that's delivered in various formats as appropriate.
The content solution for Container Pricing for IBM Z includes the following:
Comprehensive content collection. This new kind of entry in the
Knowledge Center, which we've nicknamed a c3, serves as a one-stop
shop for all topics in the z/OS* library related to Container Pricing for
IBM Z. It brings together information about SCRT, MVS*, Enterprise workload manager, RMF*, z/OS Management Facility and SMF. With the c3,
there's no jumping from book to book; the information is all together in
one comprehensive, coherent collection. Learn more at ibm.co/2HRmr9D.
The c3 is also available as a PDF, which can be found at ibm.co/2FHLcic.
Video demos. Two brief videos introduce concepts and demonstrate
the process of implementing a Container Pricing solution in a dedicated
LPAR and a Container Pricing solution that's colocated with other workloads in an existing LPAR. You can view the videos at bit.ly/2FHxxbj
z/OSMF workflows. Two z/OSMF workflows provide guided steps for
implementing a dedicated solution and a colocated solution. You can get
the details at bit.ly/2rjyxNi.
You might also want to check out these other important resources:
Whitepaper. This introduces the basic concepts of Container Pricing for
IBM Z. It was made available months before GA and served as the basis
for much of the content that followed. Read on at ibm.co/2HNTEm8.
Software pricing web pages. These are the hub for all content. For
example, you can follow links to read more about Container Pricing for
IBM Z, to watch a video or to download a z/OSMF workflow. Get more
resources at ibm.co/2wcrz2r.
Stay tuned for future additions to the content solution for Container Pricing
for IBM Z. For a complete list of the content solutions for z/OS, see IBM Z
Solutions on the z/OS V2R3 home page within the Knowledge Center at
-A.S and W.K.
52 // JULY/AUGUST 2018 ibmsystemsmag.com
The New Application
Another problem the R4HA
model creates is determining the
cost of a new application.
Suppose for a moment you
want to add a new application
to an existing z/OS LPAR. Even
if you understand the cost of
a new product that you need,
a major variable is whether
the application will impact a
peak hour. This uncertainty
can be especially painful if the
application has characteristics
that make it unpredictable in
any way. All of this can make it
difficult to understand the true
cost of the new application.
By exploiting Container
Pricing for IBM Z, the New
Application solution provides
an obvious benefit. Remember,
all container pricing workloads
are removed from impacting
the traditional R4HA, so they
don't affect the cost of other
software running on the LPAR.
The solution is priced based
on the IBM software stack and
the capacity needed for the
new application (in MSU). With
solution-specific pricing isolated
from the R4HA, the price of
a new application becomes
significantly easier to predict.
Implementing the New
As with any Container Pricing
solution, you'll receive a solution
ID after agreeing to a New
The New Application solution
can be deployed to a new LPAR,
or can be colocated on an
existing LPAR. You determine
this, based on where it will fit
Let's assume you choose to
deploy your new application to
an existing LPAR. In this case,
you use the WLM tenant resource
groups and tenant report classes
introduced in z/OS V2R2 to