Defining channel paths
At first, you define a channel path together with
its access to logical partitions. Then you may define special channel
path characteristics. These possibilities are described in Defining special channel path characteristics.
- On the HCD entry panel, select the task Define,
modify, or view configuration data and from the resulting panel,
select Processors. HCD displays the Processor
List of defined processors.
- On the Processor List:
- for SMP processors, select the processor and
the Work with attached channel paths (SMP) action
from the context menu (or action code s ).
- for XMP processors, select the processor and
the Work with channel subsystems . . (XMP) action
from the context menu (or action code s ) to display
the Channel Subsystem List. From this list, select the appropriate
channel subsystem and the Work with attached
channel paths action from the context menu (or action code s ).
HCD displays the Channel Path List showing
all channel paths defined for the selected processor/channel subsystem.
CBDPCHF0 Channel Path List Row 1 of 78 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel paths, then press Enter. To add use F11.
Processor ID . . . . : PROC03 Processor type 2097
Configuration mode . : LPAR
Channel Subsystem ID : 0 H05LP01 - H05LP15
PCHID Dyn Entry +
/ CHPID AID/P Type+ Mode+ Sw+ Sw Port Con Mng Description
_ 0D 100 OSN SPAN __ __ __ No QD8Z or QD8F for OSN Channel
_ 10 101 CNC SHR __ __ __ No free
_ 11 108 CNC SHR __ __ __ No free
_ 12 109 CNC SHR 1A 1A C2 No Tape
_ 13 110 CNC SHR __ __ __ No free
_ 14 111 CNC SHR __ __ __ No free
_ 15 1F0 CNC SHR __ __ __ No CTC to CSS0/16
_ 16 1F1 CTC SHR __ __ __ No CTC to H05LP4 - H05LP11 If
the Type contains three asterisks (***), the IODF channel
path type is unknown to the currently used HCD.
- Use F11=Add to add channel paths. The data-entry fields are shown
in the following panel, with sample data:
Figure 49. Add Channel Path
*--------------------------- Add Channel Path ----------------------------*
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . : PROC03 Processor type 2097 |
| Configuration mode . : LPAR |
| Channel subsystem ID : 0 H05LP01 - H05LP15 |
| |
| Channel path ID . . . . 02 + PCHID . . . ___ |
| Number of CHPIDs . . . . 1 |
| Channel path type . . . FCV + |
| Operation mode. . . . . SHR + |
| Managed . . . . . . . . No (Yes or No) I/O Cluster ________ + |
| Description . . . . . . ________________________________ |
| |
| Specify the following values only if connected to a switch: |
| Dynamic switch ID . . . 01 + (00 - FF) |
| Entry switch ID . . . . 01 + |
| Entry port . . . . . . . 84 + |
| |
| |
*-------------------------------------------------------------------------*
For physical channels on an XMP processor, you have to specify
the physical channel identifier (PCHID) belonging to the channel path
identifier (CHPID).
The CHPID Mapping Tool
(CMT) can be used to make the mapping between CHPIDs and PCHIDs easier
(see How to interact with the CHPID Mapping Tool).
- For each static channel path you can specify which logical partitions
can access that channel path. After you press the Enter key on the
Add Channel Path panel, HCD displays the Define Access List.
*------------------------ Define Access List --------------------------*
| Row 1 of 6 |
| |
| Select one or more partitions for inclusion in the access list. |
| |
| Channel subsystem ID : 0 H05LP01 - H05LP15 |
| Channel path ID . . : 02 Channel path type . : FCV |
| Operation mode . . . : SHR Number of CHPIDs . . : 1 |
| |
| / CSS ID Partition Name Number Usage Description |
| / 0 H05LP01 1 OS |
| _ 0 H05LP02 2 OS |
| _ 0 H05LP03 3 OS |
| _ 0 H05LP04 4 OS |
| _ 0 H05LP05 5 OS |
| / 0 H05LP06 6 OS |
| / 0 H05LP07 7 OS Mini-OS |
| _ 0 H05LP08 8 OS Automation-OS |
| _ 0 H05LP09 9 OS TEST - OS |
| _ 0 H05LP10 A OS |
*----------------------------------------------------------------------*
If
you are working on spanned channel paths
of an XMP processor, the Define Access List also shows the partitions
defined for other channel subsystems:
*--------------------------- Define Access List ----------------------------*
| Row 1 of 1 |
| Command ===> _________________________________________ Scroll ===> CSR |
| |
| Select one or more partitions for inclusion in the access list. |
| |
| Channel subsystem ID : 0 H05LP01 - H05LP15 |
| Channel path ID . . : 0E Channel path type . : OSC |
| Operation mode . . . : SPAN Number of CHPIDs . . : 1 |
| |
| / CSS ID Partition Name Number Usage Description |
| _ 0 H05LP01 1 OS |
| _ 0 H05LP02 2 OS |
| ... |
| _ 1 H05LP29 E OS Many Guest VM |
| _ 1 H05LP30 F OS TEST - VM |
| _ 2 H05LP31 1 OS |
| _ 2 H05LP32 2 OS |
| ... |
| _ 2 TRX2CFA A CF/OS CF for TRXPLEX |
| _ 3 H05LP46 1 OS |
| _ 3 H05LP47 2 OS |
| |
| **************************** Bottom of data ***************************** |
| |
*---------------------------------------------------------------------------*
If
you want a logical partition to access a dedicated, reconfigurable,
or shared channel path when you initially activate the logical partition,
place that logical partition in the channel path’s access list. For shared channel paths and spanned channel paths,
you can place more than one partition in the access list.
- If you do not include all partitions in the access list, you are
prompted for the candidate list (for reconfigurable and shared channel
paths) after pressing the Enter key.
From the IOCP point of view, the channel path candidate
list includes the channel path access list. From the HCD point of
view, the channel path candidate list does not include the channel
path access list. The partitions already in the access list do not
appear in the candidate list.
*-------------------------- Define Candidate List --------------------------*
| CBDPCH1D Row 1 of 12 |
| Command ===> _________________________________________ Scroll ===> CSR |
| |
| Select one or more partitions for inclusion in the candidate list. |
| |
| Channel subsystem ID : 0 H05LP01 - H05LP15 |
| Channel path ID . . : 02 Channel path type . : FCV |
| Operation mode . . . : SHR Number of CHPIDs . . : 1 |
| |
| / CSS ID Partition Name Number Usage Description |
| _ 0 H05LP02 2 OS |
| / 0 H05LP03 3 OS |
| / 0 H05LP04 4 OS |
| / 0 H05LP05 5 OS |
| _ 0 H05LP08 8 OS Automation-OS |
| _ 0 H05LP09 9 OS TEST - OS |
| _ 0 H05LP10 A OS |
| _ 0 H05LP11 B OS |
| _ 0 H05LP12 C OS |
| _ 0 H05LP13 D OS Mini-OS 2 |
| F1=Help F2=Split F3=Exit F5=Reset F6=Previous |
| F7=Backward F8=Forward F9=Swap F12=Cancel F22=Command |
*---------------------------------------------------------------------------*
If
you want to be able to configure a reconfigurable or shared channel
path online to a logical partition, place that logical partition in
the channel path’s candidate list.
- After pressing the Enter key, you return to the Channel Path List.
Scroll to the right to get an overview of the access and candidate
list of a channel path. The following matrix is displayed:
Figure 50. Channel Path/Partition Matrix
Channel Path List Row 1 of 78 More: <
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel paths, then press Enter. To add, use F11.
Processor ID : PROC03 CSS ID : 0 H05LP01 - H05LP15
1=OS H05LP01 2=OS H05LP02 3=OS H05LP03 4=OS H05LP04 5=OS H05LP05
6=OS H05LP06 7=OS H05LP07 8=OS H05LP08 9=OS H05LP09 A=OS H05LP10
B=OS H05LP11 C=OS H05LP12 D=OS H05LP13 E=OS H05LP14 F=OS H05LP15
PCHID I/O Cluster --------- Partitions 0x -----
/ CHPID AID/P Type+ Mode+ Mng Name + 1 2 3 4 5 6 7 8 9 A B C D E F
_ 0D 100 OSN SPAN No ________ a a a a a a a a a a a a a a a
_ 10 101 CNC SHR No ________ c _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ 11 108 CNC SHR No ________ c _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ 12 109 CNC SHR No ________ c c c c c c c c c c c c c c a
_ 13 110 CNC SHR No ________ c _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ 14 111 CNC SHR No ________ c _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ 15 170 CNC SHR No ________ _ _ _ _ _ _ _ _ _ _ a _ _ _ _
_ 16 172 CTC SHR No ________ c _ _ _ _ _ _ _ _ _ _ _ _ _ _
...
_ 23 1F0 CNC SHR Yes UTCPLX38 * * * * _ _ _ _ _ _ _ * _ _ _
_ 24 1F1 CNC SHR Yes UTCPLX38 * * * * _ _ _ _ _ _ _ * _ _ _
_ 25 16/1 CIB SHR No ________ a c c c c c c _ _ _ _ _ _ _ _
The legend above the partition matrix shows how the partition
names are associated with the columns of the partition matrix. The
headings Partitions 0x, Partitions 1x, Partitions
2x and so on, if scrolling to the right, indicate that the partitions
for the related channel subsystems (0, 1, 2, ...) are shown. The
column numbers correspond to the partition numbers in the pertaining
channel subsystem. Also, the partition usage type OS,
CF or CO (for CF/OS) is indicated in the legend.
In
the example above, column 1 under Partitions 0x shows the definitions
for partition H05LP01 of usage type OS with partition number 1 in
CSS 0.
The following entries may appear in the partition matrix:
- a
- indicates that the partition is in the channel path’s access
list.
- c
- indicates that the partition is in the candidate list.
- *
- is shown for a managed channel path in all logical partitions
that potentially can access that channel path.
- #
- indicates that the channel path (which is defined to the channel
subsystem named in the Channel Subsystem ID field) cannot be attached
to the partitions of another channel subsystem. Either a channel path
with the same identifier is already defined for the other channel
subsystem, or the channel path cannot be spanned or it can be spanned,
but the channel path mode is not SPAN or SHR. For information
on how to change a CHPID's operation mode to SPAN, if applicable,
refer to Changing the operation mode of a channel path.
Defining special channel path characteristics
This section handles the following topics:
Defining managed channel paths
You can define a channel path as being managed by Dynamic Channel
Path Management (DCM). DCM will use such a channel path to dynamically
assign the logical paths to control units in order to optimize I/O
activity. A managed channel path must connect to a dynamic switch
and may be used for control units that connect to the same switch.
If a channel path is defined as managed in an LPAR mode processor,
it must be defined as shared. It cannot be connected to logical partitions
but must specify an I/O cluster name. An I/O cluster is a sysplex
that owns the managed channel path. All systems of the sysplex on
the given processor are allowed to share the managed channel path.
A managed channel path cannot be connected to a control unit by HCD.
Defining multiple channel paths in one step
You can define, in one step, a group of channel paths of the same
type and mode and with consecutive identifiers. It is recommended
to define only a group of channel paths that have the same partitions
in their access and candidate lists. Otherwise, you have to change
the channel paths that have different partitions in their access and
candidate list in a further step.
- Define the group by specifying the first channel path identifier
(CHPID) and the number of channel paths in the group. Define a channel
path type, mode, and description. HCD applies the definition to all
channel paths in the group.
- Type over the fields that are different, for example description,
in the Channel Path List.
Connecting a channel path to a switch
If you have already defined a switch, you can connect the channel
path to the switch on the Add Channel Path panel. Specify the dynamic
switch ID, the entry switch ID, and the entry port to connect the
channel path to a switch.
The values are only valid for the first channel path if you have
defined a group of channel paths in one step. To define values for
the other channel paths of the group, HCD displays an additional panel.
This panel allows you to define the entry ports for all subsequent
channel paths of the group. For information on dynamic switch ID and
entry switch ID, refer to Possibilities of switch connections.
*------------ Update CHPID Settings --------------*
| Row 1 of 3 |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . : PROC1 |
| Channel Subsystem ID : 0 |
| |
| DynEntry --Entry +-- |
| CHPID PCHID Switch + Switch Port |
| 1C ___ 98 98 C8 |
| 1D ___ 98 98 __ |
| 1E ___ 98 98 __ |
| **************** BOTTOM OF DATA ***************** |
*-----------------------------------------------------*
Defining IQD channel parameters
For an IQD channel path type, HCD allows you to specify the following
parameters:
- Maximum frame size
- If you define or update an
IQD channel path, HCD displays a dialog that allows you to specify
a maximum frame size to be used for IQDIO requests on that channel
path. For further information refer to z/OS Communications Server: IP Configuration Guidez/OS Communications Server: IP Configuration Guide
- IQD function
- Starting with processor types 2817 and 2818, the Internal Queued
Direct I/O (IQDIO) support offers two new options besides
the basic HiperSockets functions:
- integration with the intraensemble data network (IEDN) controlled
by the zManager functions which provide access controls, virtualization
and management functions necessary to secure and manage the IEDN.
This functionality is called extended IQD (IQDX).
- bridging an IQD channel to an external (customer managed) network
To support these functions, for IQD channels, HCD offers
three choices:
- Basic HiperSockets
- The IQD channel path is connected to the internal HiperSockets
network and is used without connection to the IEDN or an external
network. This is the default.
- IEDN Access (IQDX)
- The IQD channel path supports IEDN via the Internal Queued Direct
I/O Extensions (IQDX) function.
- External Bridge
- The IQD channel path works in basic HiperSockets mode and can
be transparently bridged to an external (customer managed) network
via the z/VM Virtual Switch bridge support.
- Physical network ID
- An
IQD channel path may be defined to a physical network. If the channel
path is defined with IQD function Basic HiperSockets or External Bridge,
a customer network can be specified. An IQD channel path with IQDX
function is defined to the internal network IEDN, per default.
Specify IQD Channel Parameters
Specify or revise the values below.
Maximum frame size in KB . . . . . . 16 +
IQD function . . . . . . . . . . . . 1 1. Basic HiperSockets
2. IEDN Access (IQDX)
3. External Bridge
Physical network ID . . . . . . . . PNET03__________
Defining more than 160 TCP/IP stacks
When defining or changing channel paths of type OSD, OSM, or OSX
for processors with the corresponding support level, HCD prompts you
with a dialog whether you want to allow for more than 160 TCP/IP stacks
with this channel. This is done by disabling priority queuing. If
priority queuing is disabled, the channel can support four times as
many queues (4 * 480 = 1920 subchannels) corresponding to four times
as many TCP/IP stacks (4 * 160 = 640) as with enabled queue prioritization.
OSM channels require that more than 160 TCP/IP stacks are allowed.
*----------- Allow for more than 160 TCP/IP stacks -----------*
| |
| |
| Specify Yes to allow more than 160 TCP/IP stacks, |
| otherwise specify No. Specifying Yes will cause priority |
| queuing to be disabled. |
| |
| Will greater than 160 TCP/IP stacks |
| be required for this channel? . . . No |
| |
| F1=Help F2=Split F3=Exit F5=Reset F9=Swap |
| F12=Cancel |
*-------------------------------------------------------------*
Defining an OSD channel path to physical networks
When defining or changing channel paths of type OSD
for processors with the corresponding support level, HCD prompts you
with a dialog to add or modify physical network IDs. Up to four physical
network IDs PNET IDs may be specified for
customer networks. The PNET IDs have to be specified in the sequence
of the physical port on the OSA channel adapter card. That means,
Physical network ID 1 has to specify the ID of the physical network
that is used for the first physical port of the channel adapter card,
Physical network ID 2 has to specify the ID of the physical network
that is used for the second physical port, and so on. This dialog
is not shown for channel path types OSX and OSM, since these channel
path types belong to the internal physical network IEDN.
Add/Modify Physical Network IDs
If the PCHID is associated to one or more physical networks, specify
each physical network ID corresponding to each applicable physical port.
Physical network ID 1 . . PNET01__________
Physical network ID 2 . . PNET02__________
Physical network ID 3 . . ________________
Physical network ID 4 . . ________________
F1=Help F2=Split F3=Exit F5=Reset F9=Swap F12=Cancel
Defining or editing a CIB channel
When defining or changing a CIB channel path, HCD prompts you with
a dialog which asks for the specification of the Adapter
ID of the HCA and the Port on the
HCA of that channel path.
*------------------ Specify HCA Attributes -------------------*
| |
| |
| Specify or revise the values below. |
| |
| Adapter ID of the HCA . . __ + |
| Port on the HCA . . . . . _ + |
| |
| |
| F1=Help F2=Split F3=Exit F4=Prompt F5=Reset |
| F9=Swap F12=Cancel |
*-------------------------------------------------------------*
Defining spanned channel paths
You can define a suitable channel path as spanned directly when creating it. On the
Add Channel Path panel from Figure 49, specify
Operation mode . . . . . SPAN
After
pressing the Enter key, HCD displays the combination of the Define
Access List and the Define Candidate List, offering partitions from
multiple logical channel subsystems. Note that if you, nevertheless,
in both lists select only partitions from the current CSS, then the
operation mode of the channel path is set back to SHR.
For information on how to change a CHPID's operation
mode to SPAN, if applicable, refer to Changing the operation mode of a channel path.
Over-defining a CHPID
For an XMP processor, you can define a channel path that is not physically
installed on the machine. This may be useful if you want to migrate
from a machine with more channels defined than the target XMP processor
has currently installed, or if you want to prepare a configuration
for future upgrades of the channel cards.
You can also over-define CIB channel paths for your OS partition.
This avoids an outage for the definition of new CIB connections between
an OS partition and a stand-alone coupling facility CPC.
To distinguish an over-defined CHPID from a physically installed
CHPID, use character * for the PCHID value or the HCA ID
for CIB channels, when over-defining the CHPID. An over-defined CHPID
must adhere to all validation rules.
When installing the channel path later, you must edit the CHPID
and replace the * by its valid PCHID or HCA ID.
Over-defined channel paths are not taken into account by an IOCDS
download, by an IOCP build and by a dynamic activation of an I/O configuration.
If a control unit contains only CHPIDs with a PCHID value or HCA ID *,
the whole control unit (including any attached devices) is omitted
from the configuration.
If a CHPID changes its PCHID or HCA ID from * to a valid
value during a dynamic activation, an Add CHPID request
is generated. Correspondingly, if the PCHID or HCA ID is changed from
a valid value to an *, a Delete CHPID request
is generated.
When building a CONFIGxx member, CHPIDs with a PCHID/HCA ID * are
skipped. Attached control units including attached devices are also
omitted.
When copying a configuration or generating I/O configuration statements,
channel path definitions with PCHID=* and AID=* are included.
When building a production IODF, HCD requires that the CIB channels
are connected, even if they are over-defined. If the connection is
within the same processor, a mix of over-defined and fully-defined
HCA IDs is not accepted. In this case, error message CBDG541I is issued
and the production IODF is not built.
|
z/OS HCD User's Guide
Copyright IBM Corporation 1990, 2014