Establishing coupling facility channel path connections
Before you start to establish a Coupling Facility (CF) channel
path connection, you must have defined a processor that supports coupling
facilities, a coupling facility partition, a coupling facility receiver
(CF receiver) channel path and coupling facility sender (CF sender)
channel path, or peer channel paths.
- On the Channel Path List (Figure 50) select a channel
path and the Connect CF channel path action
from the context menu (or type action code f ). HCD
displays the CF Channel Path Connectivity
List showing all CF channel paths defined for a processor.
To
show that a CHPID is already connected in another IODF you can set
the indicator in the Occ (occupied) column to Y (yes).
You cannot connect a CHPID labeled Y. However, you can
change the occupied status by overwriting.
Figure 51. CF Channel Path Connectivity List
CF Channel Path Connectivity List Row 1 of 6
Command ===> ____________________________________________ Scroll ===> CSR
Select one or more channel paths, then press Enter.
Source processor ID . . . . . : R35 Proc type 2817 (z196)
Source channel subsystem ID . : 0
Source partition name . . . . : *
----------Source---------- -----------Destination----------- -CU- -#-
/ CHP PCHID CF Type Mode Occ Proc.CSSID CHP PCHID CF Type Mode Type Dev
_ 02 00/1 Y CIB SHR N
_ 03 01/1 Y CIB SHR N
_ 0E 1E1 N CFP SPAN N H05.3 0E 518 Y CFP SHR CFP 7
_ 0F 1E9 N CFP SPAN N H05.3 0F 528 Y CFP SHR CFP 7
_ F7 270 Y CFP SPAN N ECL2.0 81 201 Y CFP SPAN CFP 7
_ F8 271 Y CFP SPAN N H05.3 06 519 Y CFP SHR CFP 7
_ F9 278 Y CFP SPAN N ECL2.0 85 211 Y CFP SPAN CFP 7
_ FA 279 Y CFP SPAN N H05.3 07 529 Y CFP SHR CFP 7
******************************* Bottom of data ********************************
Notes:
- The Source partition name field indicates
a name only when the Filter function is employed.
- Column PCHID for both the source
and destination of the connection, is either the physical channel
identifier to which the channel path is assigned or, for some CHPID types,
its host communication adapter ID and port number.
- Column CF indicates Y if at least one partition specified in the access
or candidate list is of type CF or CF/OS, which
is a prerequisite for establishing CF channel path connections.
- Column CU Type indicates the
type of the connected control unit(s).
- Column # Dev indicates the
number of CF devices connected to the CU(s) and used for the CF connection.
- Select the source channel path for a coupling facility connection
and the Connect to CF channel path action
from the context menu (or action code p ). HCD displays
the Connect to CF Channel Path panel. The data-entry fields are shown
in the following figure, with sample data:
Figure 52. Connect to CF Channel Path
*---------------- Connect to CF Channel Path ---------------------*
| |
| |
| Specify the following values. |
| |
| Source processor ID . . . . . : XMPPROC1 |
| Source channel subsystem ID . : 0 |
| Source channel path ID . . . . : 1B |
| Source channel path type . . . : CFP |
| |
| Destination processor ID . . . . . . XMPPROC2 + |
| Destination channel subsystem ID . . 0 + |
| Destination channel path ID . . . . 1B + |
| |
| Timing-only link . . . . . . . . . . No |
| |
| |
*-----------------------------------------------------------------*
- To establish the CF channel path connection, specify the destination
processor ID, destination channel subsystem ID and
destination channel path ID.
If the CF control unit definition
does not yet exist, HCD automatically generates a CF control unit
and CF devices for a sending channel path when CF channel paths are
connected. HCD uses type CFS for a (legacy) CF sender channel path
and type CFP for a CF peer channel path. The sending CF channel paths,
that connect one CSS of a processor to a CF partition,
are assigned to the same CF control unit. For each CF sender channel
path connection, HCD generates two CF devices. For each sending CF
peer channel path, HCD generates seven (or 32)
CF devices. This allows eight CF links between a single
CSS and a specific target CF partition. HCD proposes the highest
unused control unit number and highest unused consecutive device numbers
in the IODF. If a CF peer channel path does not connect to a target
CF partition (that is, the sending function is not used), HCD does
not connect the channel path to CF control unit and CF devices.
If
a CF control unit definition is already used for another CF connection
from the CSS of the sending CF channel path to
the same target CF partition, HCD proposes the same control unit number.
This control unit number may be overwritten by an unused control unit
number, provided the partition lists of the channel paths on the existing
control unit do not overlap with the partition list of the sending
CF channel path for the new CF connection. Thus, it is possible to
establish more than eight CF links between a single CSS
of a CPC and a specific target CF partition.
Note:
HCD
checks the partition access lists of the channel paths for an overlap.
That means, you can define an overlap in the partition candidate lists.
In such cases however, you must ensure by operational means that at
any one time, the CHPIDs of only one of the control units with overlapping
partitions are configured online.
You
can also choose to use the same control unit for all partitions of
a sysplex that is shared across more than one CSS of a processor for
the CF links to a specific target CF partition. This is necessary,
if you plan to use a mix of shared (SHR) and spanned (SPAN) CIB connections
between your syplex and the target CF partition. In such a case, it
is recommended to define first the SPAN and then the SHR CHPIDs.
Note:
If you start defining SHR CHPIDs from two CSSs
connected to the same target CF partition, HCD proposes for each CSS
its own control unit with the CHPIDs from its CSS. If you now want
to add a connection with a spanned CHPID that is spanning both of
the original CSSs, you cannot add the new spanned CHPID to both control
units. Instead, you must break all the connections from one CSS, then
connect the new spanned CHPID, with HCD forcing you to use just one
control unit, and then reconnect all the broken CHPIDs, with HCD also
forcing them to use the same control unit.
The Add CF Control Unit and Devices panel is
displayed twice (for the source and for the destination side), where you must confirm or revise the values for the
CF control unit and CF devices. The data-entry fields are shown in Figure 53, with sample data:
Figure 53. Add CF Control Unit and Devices
*--------------- Add CF Control Unit and Devices ------------------*
| |
| |
| Confirm or revise the CF control unit number and device numbers |
| for the CF control unit and devices to be defined. |
| |
| Processor ID . . . . . . . : XMPPROC1 |
| Channel subsystem ID . . . : 0 |
| Channel path ID . . . . . : 1B Operation mode . . : SHR |
| Channel path type . . . . : CFP |
| |
| Control unit number . . FFFE + |
| |
| Device number . . . . . FFCF |
| Number of devices . . : 7 |
| |
| |
*------------------------------------------------------------------*
Notes:
- The CF control unit and device definitions are displayed on the
Control Unit List and on the I/O Device List, but in a disabled state
where they cannot be modified or deleted.
- If you specified a timing-only link in the dialog from Figure 52, then the field Number of devices is
set to 0 and cannot be changed, as no devices are created for such
links. For more information on timing-only links (STP links), read Defining Server Time Protocol (STP) links.
- If you are connecting a CIB coupling facility link (CIB
CHPIDs), and both processors support more than seven subchannels,
then the field Number of devices is set
to 7 and can be changed to 32.
Changing the Number of devices results in a new device number
(except you changed this value as well; in this case a message is shown) and a redisplay of the window
showing the modified values. Pressing Enter again displays the same window again, but this time with the
desination side values.
- After you press the Enter key, HCD redisplays the CF Channel Path
Connectivity List with the new connection defined.
|
z/OS HCD User's Guide
Copyright IBM Corporation 1990, 2014