v
Shared
ICF
and
shared
general
purpose
processors
are
each
managed
as
separate
“pools”
of
physical
resources.
As
such,
the
processing
weights
assigned
to
logical
partitions
using
shared
ICF
processors
are
totaled
and
managed
separately
from
the
total
weights
derived
from
all
of
the
logical
partitions
using
shared
general
purpose
processors.
Similarly,
when
the
processor
running
time
is
dynamically
determined
by
the
system,
the
calculation
of
the
dynamic
running
time
is
performed
separately
for
each
pool.
If
a
user
supplied
run
time
is
specified,
this
will
apply
to
both
processor
pools.
v
RMF
identifies
which
logical
and
physical
CPs
are
of
each
type
when
both
general
purpose
and
ICF
processors
are
present
in
the
configuration
on
its
partition
data
report.
v
An
uncapped
coupling
facility
LP
honors
its
processing
weight
up
to
a
point.
PR/SM
LPAR
attempts
to
help
ensure
that
each
logical
CP
defined
to
a
coupling
facility
LP
gets
at
least
1
run
time
interval
of
service
per
every
100
milliseconds.
For
example,
for
a
typical
12.5
millisecond
run
time
interval,
each
logical
CP
gets
1/8th
of
a
physical
CP.
This
can
translate
into
a
response
time
elongation
that
is
several
thousand
times
as
long
as
a
typical
CF
request
using
dedicated
CPs.
With
dynamic
coupling
facility
dispatch,
the
coupling
facility
will
not
necessarily
consume
entire
run
time
intervals
at
low
request
rate
times.
In
low
request
rate
times,
each
coupling
facility
engine
can
consume
far
less
than
1/8th
of
a
physical
CP.
The
CP
resource
consumption
can
be
more
in
the
1-2%
range.
At
higher
request
rates
(for
example,
when
the
coupling
facility
is
actually
busy
handling
requests),
the
1/8th
minimum
will
again
become
effective.
Note:
Anticipated
processor
usage
by
a
coupling
facility
may
spike
much
higher
than
what
you
would
intuitively
expect
given
the
non-CF
workload.
For
instance,
system
reset
of
a
system
or
logical
partition
that
was
communicating
with
(connected
to)
a
coupling
facility
can
temporarily
cause
a
considerable
increase
in
the
demands
placed
on
the
coupling
facility.
v
All
requests
to
coupling
facilities
from
z/OS
LPs
that
share
CPs
with
a
coupling
facility
are
treated
internally
to
the
machine
as
asynchronous
requests.
This
is
true
even
if
the
requests
are
to
a
coupling
facility
that
the
z/OS
LP
is
not
sharing
CPs
with.
This
conversion
is
transparent
to
z/OS
but
it
can
result
in
increased
synchronous
service
times
to
the
coupling
facility
as
reported
by
RMF.
As
far
as
the
operating
system,
RMF,
and
the
exploiter
code
is
concerned,
the
requests
that
are
initiated
synchronously
by
software
are
still
being
processed
synchronously,
and
they
show
up
as
such
on
RMF
reports.
v
Choose
a
weight
for
the
coupling
facility
LP
based
on
the
anticipated
CP
requirements
of
the
coupling
facility.
When
deciding
how
much
CP
resource
should
be
given
to
each
coupling
facility
logical
CP,
consider
the
following:
–
When
using
dynamic
CF
dispatching,
the
weight
for
the
coupling
facility
can
safely
be
set
to
a
value
that
affords
the
proper
CP
resources
to
the
coupling
facility
in
times
of
the
highest
volume
of
requests
to
the
coupling
facility.
In
low
request
rate
periods,
the
coupling
facility
will
automatically
throttle
back
on
its
CP
usage
making
the
CP
resource
available
for
redistribution
to
the
other
defined
LPs
in
the
configuration.
Also,
note
that
at
low
request
rate
times,
RMF
Coupling
Facility
Activity
Reports
will
show
some
elongation
in
response
times
for
requests
to
the
coupling
facility.
With
the
low
rate
of
these
requests,
overall
system
performance
should
not
be
noticeably
impacted.
–
CP
resource
requirements
vary
depending
on
the
coupling
facility
exploiter
functions
and
your
sysplex
hardware
and
software
configuration.
As
a
general
guideline,
when
the
anticipated
CP
requirement
of
the
coupling
facility
is
less
than
one
physical
CP,
set
the
weight
of
the
coupling
facility
LP
so
that
the
3-32
PR/SM
Planning
Guide
Содержание Z9
Страница 1: ...System z9 Processor Resource Systems Manager Planning Guide SB10 7041 03...
Страница 2: ......
Страница 3: ...System z9 Processor Resource Systems Manager Planning Guide SB10 7041 03...
Страница 12: ...x PR SM Planning Guide...
Страница 18: ...xvi PR SM Planning Guide...
Страница 26: ...xxiv PR SM Planning Guide...
Страница 43: ...ZVSE ZVM Figure 1 1 Characteristics of Logical Partitions Chapter 1 Introduction to Logical Partitions 1 17...
Страница 54: ...1 28 PR SM Planning Guide...
Страница 126: ...2 72 PR SM Planning Guide...
Страница 195: ...Figure 3 23 Security Page Image Profile Chapter 3 Determining the Characteristics of Logical Partitions 3 69...
Страница 220: ...4 8 PR SM Planning Guide...
Страница 232: ...5 12 PR SM Planning Guide...
Страница 250: ...B 16 PR SM Planning Guide...
Страница 266: ...D 10 PR SM Planning Guide...
Страница 272: ...X 6 PR SM Planning Guide...
Страница 273: ......
Страница 274: ...Printed in USA SB10 7041 03...