access
list
specifies
the
LPs
that
have
initial
access
to
the
CHPID
at
the
completion
of
the
initial
power-on
reset.
An
LP
name
may
only
appear
once
in
an
access
list.
You
can
specify
that
no
LPs
will
access
the
channel
path
following
LP
activation
for
the
initial
POR
of
an
LPAR
IOCDS.
Specifying
0
indicates
a
null
access
list.
candidate
list
specifies
the
LPs
that
have
authority
to
access
the
CHPID.
Any
LP
that
is
not
in
a
CHPIDs
candidate
list
cannot
access
the
CHPID.
You
may
specify
as
many
LP
names
as
your
CPC
supports.
However,
the
number
of
unique
LP
names
specified
in
both
the
access
list
and
candidate
list
may
not
exceed
the
number
of
LPs
your
CPC
supports.
If
you
specify
the
candidate
list,
you
do
not
need
to
specify
again
the
LP
names
specified
in
the
initial
access
list.
The
initial
access
list
is
always
included
in
the
candidate
list.
An
LP
name
can
only
appear
once
in
a
candidate
list.
If
the
candidate
list
is
not
specified,
it
defaults
to
all
LPs
in
the
configuration
for
reconfigurable
and
shared
channels.
Note:
It
is
highly
recommended
that
a
peer
mode
CHPID
(CBP,
CFP,
CIB,
or
ICP)
have
at
most
one
coupling
facility
LP
specified
in
its
initial
access
list
in
order
to
avoid
confusion
on
subsequent
LP
activations.
A
peer
mode
CHPID
can
be
online
to
only
one
coupling
facility
LP
at
a
time.
Using
the
SHARED
keyword
specifies
that
the
channel
paths
on
the
CHPID
statement
are
shared.
More
than
one
LP,
at
the
same
time,
can
access
a
shared
CHPID.
When
CHPIDs
are
not
shared,
only
one
LP
can
access
it.
Although
you
can
dynamically
move
a
reconfigurable
CHPID
between
LPs,
it
can
only
be
accessed
by
1
LP
at
any
given
time.
Only
CNC,
CTC,
CBP,
CIB,
CFP,
ICP,
OSC,
OSD,
OSE,
OSN,
FC,
FCV,
FCP,
and
IQD
channel
paths
(TYPE
keyword)
can
be
shared.
The
CPATH
keyword
is
only
valid
for
ICP
and
CIB
channel
paths
(TYPE
keyword)
and
required
for
all
ICP
and
CIB
definitions.
CPATH
specifies
the
connection
between
2
ICPs
at
either
end
of
a
coupling
link:
PATH=FE,TYPE=ICP,CPATH=FF,...
PATH=FF,TYPE=ICP,CPATH=FE,...
specifies
that
ICP
channel
path
FF
connects
to
ICP
channel
path
FE.
Every
ICP
channel
path
of
a
coupling
facility
must
be
connected
to
an
ICP
channel
path
of
a
z/OS
LP.
The
connection
needs
to
be
specified
for
each
channel
path.
ICP
channel
paths
cannot
connect
to
each
other
if
they
both
have
candidate
lists
with
the
same,
single
logical
partition.
Note
that
this
prevents
the
definition
of
internal
coupling
channels
in
a
LPAR
configuration
with
only
one
logical
partition.
Also,
an
ICP
channel
path
cannot
connect
to
itself.
The
CPATH
value
for
a
CIB
CHPID
specifies
the
CSS
and
CHPID
number
this
CIB
CHPID
connects
with
on
the
target
system.
For
example:
PATH=C0,TYPE=CIB,CPATH=(CSS(1),D0),...
Defines
a
CIB
CHPID,
C0,
on
this
system
that
connects
with
CIB
CHPID
D0
in
CSS
1
on
the
remote
system.
2-30
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...