Channel subsystem reports
The following channel subsystem reports are available:
Processor Summary Report
Figure 159. Processor Summary Report
PROCESSOR SUMMARY REPORT TIME: 15:29 DATE: 2012-10-21 PAGE A- 1
PROCESSOR CONFIG. SERIAL ----- SNA ADDRESS -----
ID TYPE MODEL MODE NUMBER DESCRIPTION NETWORK NAME CPC NAME LSYSTEM
_________ ________ ________ ________ __________ ________________________________ _______________________ ________
ERV01WWW 2094 S38 LPAR 1212122094 mix system ZZZZZZZZ ERV01 ERV01
ERV02O1 9672 ZX7 LPAR 4434349672 old system 1 IBM390PS ERV02O1
ERV02O2 9672 ZX7 LPAR 1111119672 old system 2 IBM390PS ERV02O2
ERV05A1 2094 S28 LPAR 9912992094 Standalone FCTC CTC/CNC IBM390PS ERV05A1
ERV05A2 2094 S54 LPAR 9929912094 standalone FCTC CTC/CNC proc IBM390PS ERV05A2
NET01 2096 R07 LPAR 3322332096 Network System ZZZZZZZZ NET01
PROCESSOR ----SUPPORT LEVEL----
ID ID DESCRIPTION
_________ ________ ________________________________________________________________
ERV01WWW H050331 XMP, Basic 2094 support
ERV02O1 H990531 FCV, OSD, OSE, IC, ICB, CF, OSA, ESCON, Parallel
ERV02O2 H990531 FCV, OSD, OSE, IC, ICB, CF, OSA, ESCON, Parallel
ERV05A1 H050331 XMP, Basic 2094 support
ERV05A2 H050331 XMP, Basic 2094 support
NET01 H060930 XMP, 2096-R07 support
| CONFIG. MODE | Indicates the operation mode in which a processor may operate.
These modes are:
- BASIC
- The processor is not logically partitioned.
- LPAR
- The processor is logically partitioned. Several operating systems
may run concurrently in different partitions of the processor.
| | SNA ADDRESS | The SNA Address consists of Network name and CPC name and associates
the CPC and the processor definition in the IODF. | | SUPPORT LEVEL | Shows the ID of the processor support level and an enumeration
of the provided functionality. |
Channel Subsystem Summary Report
Only XMP processors will have a channel subsystem report
which shows the defined channel subsystems.
Figure 160. Channel Subsystem Summary Report
CHANNEL SUBSYSTEM SUMMARY REPORT TIME: 13:33 DATE: 2012-10-21 PAGE A- 2
PROCESSOR ID GOLDENE1 TYPE 2817 MODEL M15
DEVICES IN SS0 DEVICES IN SS1 DEVICES IN SS2
CSS ID MAXIMUM ACTUAL MAXIMUM ACTUAL MAXIMUM ACTUAL DESCRIPTION
______ _______ ______ _______ ______ _______ ______ ________________________________
0 65280 28774 65535 5732 65535 3132
1 65280 30681 65535 9877 65535 4430
2 65280 16336 65535 5344 65535 2837
3 65280 1346 65535 932 65535 1434
Note:
This report and the following channel subsystem reports
show the processor token only if the IODF is a production IODF.
PCIE Function Summary Report
The PCIe Function Summary Report provides an overview of the defined PCIe functions for the specified processor.
Figure 161. PCIe Function Summary Report
PCIE FUNCTION SUMMARY REPORT TIME: 10:57 DATE: 2013-06-11 PAGE A- 6
PROCESSOR ID PROCNEW1 TYPE 2827 MODEL HA1 CONFIGURATION MODE: LPAR
PARTITION NUMBERS
CSS0----------- CSS1----------- CSS2----------- CSS3-----------
FID VF PCHID TYPE 123456789ABCDEF 123456789ABCDEF 123456789ABCDEF 123456789ABCDEF DESCRIPTION
___ __ _____ ____________ _______________________________________________________________ ________________________________
001 1 010 ZEDC-EXPRESS --------------- A-------------- ---------C----- ---------------
002 2 010 ZEDC-EXPRESS --------------- A-------------- ---------C----- ---------------
003 3 010 ZEDC-EXPRESS --------------- A-------------- ---------C----- ---------------
010 500 ROCE --------------- A-------------- ---------C----- ---------------
CSS0 CSS1 CSS2 CSS3
PARTITION PARTITION PARTITION PARTITION
NUM NAME NUM NAME NUM NAME NUM NAME
____ ________ ____ ________ ____ ________ ____ ________
1 * 1 R35LP16 1 R35LP31 1 R35LP46
2 * 2 R35LP17 2 R35LP32 2 R35LP47
3 * 3 R35LP18 3 R35LP33 3 R35LP48
4 * 4 R35LP19 4 R35LP34 4 R35LP49
5 * 5 R35LP20 5 R35LP35 5 R35LP50
6 * 6 R35LP21 6 R35LP36 6 R35LP51
7 * 7 R35LP22 7 R35LP37 7 R35LP52
8 * 8 R35LP23 8 R35LP38 8 R35LP53
9 * 9 R35LP24 9 R35LP39 9 R35LP54
A * A R35LP25 A DWB1 A DWB2
B * B IRD6 B R35LP41 B R35LP56
C * C IRD8 C TRX1 C TRX2
D * D R35LP28 D R35LP43 D R35LP58
E * E R35LP29 E R35LP44 E R35LP59
F * F R35LP30 F R35LP45 F R35LP60
LEGEND FOR PARTITION NUMBERS FIELD:
___________________________________
A - PARTITION IS IN FUNCTION ACCESS LIST
C - PARTITION IS IN FUNCTION CANDIDATE LIST ONLY
- - PARTITION IS NOT IN FUNCTION ACCESS OR CANDIDATE LIST
PCHID Summary Report
The PCHID Summary Report provides
an overview of all PCHIDs defined for channel paths and PCIe functions
of a processor and also gives an overview of the defined PNET IDs
for the PCHIDs.
Figure 162. PCHID Summary Report
PCHID SUMMARY REPORT TIME: 10:57 DATE: 2013-06-11 PAGE A- 11
PROCESSOR ID PROCNEW1 TYPE 2827 MODEL HA1 CONFIGURATION MODE: LPAR
CHPID
PCHID VF FID TYPE SWITCH CSS Numbers PNET-1 PNET-2 PNET-3 PNET-4
_____ __ _____ ____________ ______ ___________ ________________ ________________ ________________ ________________
010 1 001 ZEDC-EXPRESS | |1|2| |
010 2 002 ZEDC-EXPRESS | |1|2| |
010 3 003 ZEDC-EXPRESS | |1|2| |
1D1 A1 OSD | |1| | |
1E0 0A CFP | | |2|3|
1E8 0B CFP | | |2|3|
261 A0 OSD | | |2| |
384 9F OSD | |1| | |
500 010 ROCE | |1|2| | A12345 C223344
551 94 OSE | |1| | |
5A0 76 OSD | | |2|3|
TOTALS FOR CHANNEL CARD TYPES
EXTERNAL CHPIDS INTERNAL CHPIDS PCIE FUNCTIONS
CFP CIB FC FCP OSC OSD OSE OSN ICP IQD ROCE ZEDC
___________________________________________________________________
2 0 0 0 0 4 1 0 0 0 2 3
Partition Report
Figure 163. Partition Report
PARTITION REPORT TIME: 12:57 DATE: 2012-10-21 PAGE B- 3
PROCESSOR ID G33XMP TYPE 2084 MODEL B16
CSS ID 0
PARTITION NAME NUMBER USAGE DESCRIPTION
______________ ______ _____ ________________________________
TCSS0LP2 2 CF/OS OS/CF Partition number 2 CSS0
TCSS0LP3 3 OS OS Partition number 3 CSS0
* 4 CF/OS reserved Partition number 4 CSS0
PARTITION REPORT TIME: 12:57 DATE: 2012-10-21 PAGE B- 4
PROCESSOR ID G33XMP TYPE 2084 MODEL B16
CSS ID 1
PARTITION NAME NUMBER USAGE DESCRIPTION
______________ ______ _____ ________________________________
LIN1 7 OS Linux
LNXCM10 A OS Linux
LNXCM3 6 OS Linux
LNXCM4 8 OS Linux
LNXCM9 9 OS Linux
| NUMBER | Is the partition number (MIF ID). This information
is printed only for EMIF capable processors. | | USAGE | Specifies the usage type of a partition: CF indicates a partition
supporting coupling facility. OS indicates a partition running an
operating system. CF/OS indicates a partition supporting coupling
facility or running an operating system. |
IOCDS Report
IOCDS data are retrieved from the support element when
a SNA address is defined. Otherwise, the IOCDS data are retrieved
from the IODF. An IOCDS status line at the end of the report indicates
the source of the IOCDS data.
Figure 164. IOCDS Report
I O C D S REPORT TIME: 00:06 DATE: 2012-10-21 PAGE C- 1
PROCESSOR ID CFS TYPE 9672 MODEL RX6
-----Token Match---- Write --Last Update--
IOCDS NAME FORMAT STATUS IOCDS/HSA IOCDS/Proc Protect DATE TIME IOCDS Configuration Token Information
_____ ________ ______ __________ _________ __________ _______ __________ _____ ____________________________________________
A0 316ACFS LPAR POR Yes No Yes-POR 2004-11-12 06:14 CFS 16:27:52 04-11-11 SYS4 IODF71
A1 063ACFS LPAR Alternate No No No 2004-03-03 16:49 CFS 16:23:49 04-03-03 SYS4 IODF72
A2 091ACFS LPAR Alternate No No No 2004-04-01 00:01 CFS 16:08:02 04-03-31 SYS4 IODF73
A3 296ACFS LPAR Alternate No No No 2004-10-22 11:45 CFS 14:59:05 04-10-21 SYS4 IODF71
IOCDS status retrieved from the support element
| NAME | Represents the user-defined name of the IOCDS (derived from
the MSG1 parameter) | | FORMAT | IOCDS format (BASIC or LPAR) | | STATUS | Indicates the status of the IOCDS: Alternate,
POR, Invalid (see Build System z cluster IOCDSs). | | Token Match - IOCDS/HSA | Indicates whether the IOCDS token matches the current HSA token | | Token Match - IOCDS/Proc | Indicates whether the IOCDS token matches the current processor
token in the IODF | | Write Protect | Indicates whether the IOCDS is write-protected (Yes)
or not (No), or currently write-protected
because it is the POR IOCDS (Yes-POR). | | Last Update DATE/TIME | Time stamp of IOCDS creation time | | IOCDS Configuration Token Information | is the configuration token information stored in the support
element and shows the relationship between the IOCDS and the production
IODF from which it was created. |
Channel Path Summary Report
If applicable, for spanned channels, there is a separate
sub-report after the partition table of a processor which shows the
connection of spanned channel paths to channel subsystems.
Figure 165. Channel Path Summary Report
CHANNEL PATH SUMMARY REPORT TIME: 16:54 DATE: 2012-10-21 PAGE D- 1
PROCESSOR ID GOLDENE1 TYPE 2094 MODEL S38 CONFIGURATION MODE: LPAR
CSS ID 0
PCHID MFS DIS I/O DYN. SWITCH PARTITION NUMBERS
CHPID AID/P TYPE KB QP MNGD CLUSTER SWITCH ID PORT MODE |1|3|9|F| DESCRIPTION
_____ _____ ____ ___ ___ ____ ________ ______ ______ ____ ____ _______________________________ ________________________________
00 300 FC NO SPAN |A| | |A|
01 301 FC NO SPAN |A|A|C|C|
02 302 FC NO SPAN |A|A|A|A|
10 310 FC NO 50 50 03 SPAN |A|A|A|A|
11 311 FC NO 50 50 04 SPAN |A|A|A|A|
30 330 FC YES TRXPLEX9 50 50 05 SHR | | | | | managed chpids
31 331 FC YES TRXPLEX9 50 50 06 SHR | | | | | managed chpids
50 555 OSD YES NO SPAN |A|A|A|A| up to 1920 subchannels
51 IQD 16 NO SHR |A| |C|A|
52 IQD 24X NO SHR |A| |C|A|
53 IQD 40B NO SHR |A| |C|A|
BB 00/1 CIB NO SPAN |A|A| | |
PARTITION
NUMBER NAME
______ ________
1 GECSS01X
3 GECSS03X
9 GECSS09X
F GECSS0FX
SPANNED CHANNEL PATHS
CHPID CSS IDS
NUMBER TYPE |0|1|2|3|
______ ____ _________
00 FC |X|X|X|X|
01 FC |X|X|X|X|
02 FC |X|X|X|X|
10 FC |X|X|X|X|
11 FC |X|X|X|X|
50 OSD |X|X| | |
LEGEND FOR PARTITION NUMBERS FIELD:
___________________________________
A - PARTITION IS IN CHPID'S ACCESS LIST
C - PARTITION IS IN CHPID'S CANDIDATE LIST ONLY
BLANK - PARTITION IS NOT IN CHPID'S ACCESS OR CANDIDATE LIST
| PCHID AID/P |
For external channels: designates the physical channel identifier (PCHID) or,
if applicable, designates the HCA adapter ID (AID) and the HCA port (P).
| | DIS QP | Indicates whether queue prioritization is disabled. | | MFS KB | Designates the maximum frame size in KB. For channels of type
IQD, this field also indicates whether or how this channel exploits
the extended IQD function:
- blank
- indicates the HiperSockets function
- X
- indicates IEDN support (IQDX)
- B
- indicates bridge support
| | MNGD | Indicates whether the channel path is managed. | | I/O CLUSTER | The I/O cluster name for managed channel paths. | | DYN. SWITCH | Designates the switch holding the dynamic connection. | | SWITCH ID | Designates the switch the channel is physically plugged in
(entry switch). | | PORT | Designates the entry port on the entry switch. | | MODE | Operation mode of the channel path. |
Channel Path Detail Report
The Channel Path Detail Report lists the channel paths defined
per processor with their attributes and attachment information.
In addition, the switch connections on the path between the CHPID
and the control unit are shown if they can be determined by HCD. The
entry switch and port of the CHPID are always shown.
For an entry switch of a CHPID which is defined as a dynamic switch,
the control unit port is shown if it is compatible with the link address
defined for the CHPID. For an entry switch of the CHPID which is defined
as a dedicated switch, the control unit port or the ports connecting
the switches are only shown if switch configurations are defined which
allow HCD determining a valid path between CHPID and control unit.
In case of chained switches, the first print line for a channel
path shows the switch the channel path is physically plugged in.
The second print line shows the switch the control unit is connected
to. In addition, the first print line shows the ID of the switch
with the dynamic connection.
Each attached control unit of a specific channel path is separated
by a line.
The first print line for an attached control unit shows the first
unit address range defined for the control unit. If there are more
unit address ranges defined for a control unit, these are shown in
the following print lines. Together with the unit address range(s)
of the control unit the attached devices of the control unit are shown
grouped according to device types and consecutive numbers and unit
addresses. The report shows the starting device number and range
of the device group. The unit address describes the address of the
first device in the range.
For FICON switches, the dynamic switch ID is empty. The control unit
port ID is shown as a two-byte port address (the port ID prefixed
by the switch address) when used in a cascaded switch environment,
or as a one-byte port address otherwise. For cascaded FICON switches,
only the channel path port ID and the control unit port ID are shown,
but no connection between the switches.
Note:
For a Coupling Facility control unit, all CF devices
attached to this control unit are listed, not only those devices that
are defined for the connected coupling facility channel path described
in the row.
Figure 166. Channel Path Detail Report
CHANNEL PATH DETAIL REPORT TIME: 12:57 DATE: 2012-10-21 PAGE E- 1
PROCESSOR ID R35 TYPE 2817 MODEL M49 CONFIGURATION MODE: LPAR
CSS ID 0
---- SWITCH ---- UNIT ADDR UNIT
PCHID ID PR CU DYN --- CONTROL UNIT --- CU- RANGE -- DEVICE -- ADDR DEVICE
CHPID AID/P TYPE MNGD MODE PN PN ID NUMBER TYPE-MODEL ADD PROTOCOL FROM TO NUMBER,RANGE START TYPE-MODEL
_____ _____ ______ _____ ____ ____________ ___ _____________________ ___ ________ _________ ____________ _____ __________
00 5B0 OSD NO SPAN B302 OSA 00 FE B300,6 00 OSA
B306,42 06 OSA
B330,16 30 OSA
B340,6 40 OSA
B346,42 46 OSA
B370,16 70 OSA
__________________________________________________________________________________________________________________________________
0C 130 OSC NO SPAN 0003 OSC 00 FD 0090,16 00 3270-X
1090,4 10 3270-X
__________________________________________________________________________________________________________________________________
0D 131 OSM NO SPAN
__________________________________________________________________________________________________________________________________
0E 1E1 CFP NO SPAN FFDF CFP F0D4,7 CFP
F0DB,7 CFP
__________________________________________________________________________________________________________________________________
0F 1E9 CFP NO SPAN FFDF CFP F0D4,7 CFP
F0DB,7 CFP
__________________________________________________________________________________________________________________________________
12 1F2 CNC NO SHR 1A 0690 3590 00 03 0690,4 00 3590
_______________________________________________________________________________________________________
1A 1A39 3590 00 0F 0A38,2 00 3590
_______________________________________________________________________________________________________
1A 1A55 3590 00 03 0A54,4 00 3590
__________________________________________________________________________________________________________________________________
30 220 FC NO SPAN 10 2A 6140 2000 2107 2 00 9F 2000,160 00
_______________________________________________________________________________________________________
10 2A 611A 2800 2107 1 00 FF 2800,40 00 3390B
2828 28 3390B
2829,39 29 3390B
2850,2 50 3390B
2852,6 52 3390B
2858,88 58 3390B
28B0,5 B0 3390B
28B5,11 B5 3390B
28C0 C0 3390B
28C1,8 C1 3390B
28C9,7 C9 3390B
28D0,48 D0 3390A
_______________________________________________________________________________________________________
10 2A 612F 4001 2107 0 00 FF 4000,96 00 3390B
40A0,16 A0 3390B
| SWITCH ID | Designates the entry switch the channel path is physically
plugged in. For chained ESCON switches or cascaded FICON switches,
a second line is shown with the ID of the switch to which the control
unit is connected. | | SWITCH PR PN | Designates the entry port of the entry switch. In case of an
ESCON chained switch, it designates the entry port of the chained
switch. | | SWITCH CU PN | Designates the port the control unit is connected to. In case
of an ESCON chained switch, it designates the port of the entry switch
to which the chained switch is connected. For a cascaded FICON switch,
the port ID is prefixed by the switch address. | | SWITCH DYN ID | For an ESCON environment, it designates the switch holding
the dynamic connection. |
CF Channel Path Connectivity Report
For XMP processors, there will be a single CF Channel
Path Connectivity Report. The CHPID numbers are prefixed by the channel
subsystem ID. For example 1.0C denotes CHPID 0C from CSS
1. If a spanned channel path is used, the CHPIDs are reported from
all channel subsystems together with the accessed partitions in the
channel subsystems.
Figure 167. CF Channel Path Connectivity Report
CF CHANNEL PATH CONNECTIVITY REPORT TIME: 13:06 DATE: 2012-10-21 PAGE F- 1
PROCESSOR ID R35 TYPE 2817 MODEL M49 CONFIGURATION MODE: LPAR
--------------- SOURCE ------- -------------------- DESTINATION -------------------- --- SOURCE ---- - DESTINATION -
ACCESS/CAND PROCESSOR ACCESS/CAND CNTRL DEVICE CNTRL DEVICE CNTL
CHPID TYPE MODE O LIST ID TYPE-MODEL CHPID TYPE MODE LIST UNIT NUM,RANGE UNIT NUM,RANGE TYPE
_________________ ____________ _______________________ _______________ ____________ _______________ _______________ ____
0.0E CFP SPAN N IRD7 H05 2097-E26 3.0E CFP SHR *IRD7CF3 FFDF F0D4,14 CFP
1.0E IRD8
--------------------------------------------------------------------------------------------------------------------------
0.0F CFP SPAN N IRD7 H05 2097-E26 3.0F CFP SHR *IRD7CF3 FFDF F0D4,14 CFP
1.0F IRD8
--------------------------------------------------------------------------------------------------------------------------
0.F7 CFP SPAN N IRD7 (C) ECL2 2097-E40 0.81 CFP SPAN *IRD4CFF FFD8 DFBA,7 FFD4 DFB3,7 CFP
D0E (C) DFE4,7 DFDD,7
1.F7 *IRD6 3.81 *D3F (C)
--------------------------------------------------------------------------------------------------------------------------
0.F8 CFP SPAN N IRD7 (C) H05 2097-E26 3.06 CFP SHR *DWB3CFF FFD6 DF9E,7 FFD0 DF97,7 CFP
DFAC,7 DFA5,7
1.F8 *IRD6 (C)
2.F8 DWB1
3.F8 DWB2
LEGEND FOR ACCESS/CAND LIST:
----------------------------
* - PARTITION IS OF TYPE CF OR CF/OS
(C) - PARTITION IS IN CHPID'S CANDIDATE LIST ONLY
| SOURCE/DESTINATION CHPID | The identifier of the source/destination channel path. | | SOURCE/DESTINATION TYPE | Is the type of the source/destination channel path. | | SOURCE/DESTINATION MODE | Is the operation mode of the source/destination channel path. | | SOURCE O | CHPID is identified as occupied | | SOURCE/DESTINATION ACCESS/CAND LIST | Shows those partitions which the source/destination channel
path has in its access or candidate list. Partitions in the candidate
list are flagged with (C) behind the partition name. Partitions of
type CF or CF/OS are prefixed with an *. For example, *D3F (C) or
*IRD6 (C) denote coupling facility partitions in the candidate list. | | DESTINATION PROCESSOR ID | Is the name of the processor the destination channel path is
defined for. | | DESTINATION TYPE-MODEL | Is the type-model of the destination processor.
| | SOURCE CNTRL UNIT | Is the number of the CF control unit used for the source CF
channel path connection. | | SOURCE DEVICE NUM,RANGE | Are the numbers of the CF devices and ranges
of device groups defined for the source CF channel path connections
via the source CF control unit. | | DESTINATION CNTRL UNIT | Is the number of the CF control unit used for the destination
CF channel path connection. | | DESTINATION DEVICE NUM,RANGE | Are the numbers of the CF devices and ranges
of device groups used for the destination CF channel path connections
via the destination CF control unit. | | CNTL TYPE | indicates the type of the connecting control unit(s). |
Control Unit Summary Report
Figure 168. Control Unit Summary Report
CONTROL UNIT SUMMARY REPORT TIME: 16:12 DATE: 2012-10-21 PAGE G- 1
CONTROL UNIT SERIAL LOGICAL
NUMBER TYPE-MODEL NUMBER DESCRIPTION CONNECTED SWITCH ID.PORT NUMBER PATHS
_____________________ __________ ________________________________ |__.__|__.__|__.__|__.__|__.__|__.__|__.__|__.__| _______
0003 OSC CU for OSC Channels
0070 OSN
0120 OSA for all native MVS (also NETMVS)
0480 3480 11333 TAPES 0480 CT1 BL6 1A.CB
04B0 FCP Open FCP 16
0900 1750 DS6K1 (0900-094F) 80 17.54 17.58 17.5C 17.60 72
0950 1750 DS6K1 (0950-098F) 80 17.54 17.58 17.5C 17.60 72
0B20 2105 11111 ESS22 B20 CU2 (3390-3/27)VSE 152 17.45 17.49 34
0BC0 2105 11111 ESS22 BC0 CU4 (3390-mix) VSE 144 17.45 17.49 34
0C50 2105 11111 ESS22 C50 CU5 (3390-mix) VSE 176 17.45 17.49 34
0D80 2107 11222 DS8K0 CU0(D80-DCF) 3390-MIX 80 17.44 17.48 17.4C 17.50 424
0DD0 2107 11222 DS8K0 CU1(DD0-E1F) 3390-MIX 80 17.44 17.48 17.4C 17.50 424
0E20 2107 11222 DS8K0 CU2(E20-E3F) 3390-54 32 17.44 17.48 17.4C 17.50 424
0E40 2107 11222 DS8K0 CU3(E40-E5F) 3390-54 32 17.44 17.48 17.4C 17.50 0
0E60 2105 11111 ESS22 E60 CU0 (3390-9) VSE 96 17.45 17.49 0
0EC0 2105 11111 ESS22 EC0 CU1 (3390-3/27)VSE 152 17.45 17.49 0
0F60 2105 11111 ESS22 F60 CU3 (3390-65) VSE 64 17.45 17.49 0
1010 2032 McData ED-6064 z/OS 10.FE
1011 2032 McData ED-6140 z/OS 11.FE
1028 FCTC H053E3F FCTC H05LP04 to H05LP11 + TRX1
102A FCTC H053E3F2 FCTC H05LP30 to H05LP31
1128 FCTC H053E3F FCTC H05LP04 to H05LP11
112A FCTC H053E3F2 FCTC H05LP30 to H05LP31
112B FCTC H053E3F FCTC H05LP04 to TRX1
1240 OSA OSA (1240-125E,5F)
| CONNECTED SWITCH ID.PORT NUMBER | Describes where the CU is physically connected to (switch and
port) | | LOGICAL PATHS | Displays the number of defined logical paths per control unit. |
Control Unit Detail Report
The Control Unit Detail Report lists all control units defined
in the currently accessed IODF, with their attributes and attachment
information.
For each control unit all processors are shown, where the control
unit is attached to. For each of those processors, all control units,
that are part of the "logical control unit" the currently printed
control unit belongs to, are printed. Also, the currently shown control
unit is listed again to show information about switch connection,
channel path attachment, and attached devices. The information about
each logical control unit the currently printed control unit belongs
to, is separated by a dotted line.
The switch connection information is shown in the Control Unit
Detail Report even if no switch configuration is defined. For example:
If a control unit is connected to a switch, but no complete path
is defined through the switch (that means, no valid path is defined
through the switch, which allows a dynamic connection) the complete
switch connection information with SWITCH ID, CU PN, and PR PN can
be determined.
In case of chained switches, the first information in a print line
is shown for the switch the control unit is connected to. The second
set of switch information is for the switch that the channel path
is connected to. Note that this is different from the Channel Path
Detail report.
To get information about the switch with the dynamic
connection (in case of chained ESCON switches), the Channel Path Detail
Report has to be produced.
For each control unit belonging to a logical control unit, the
channel path it is attached to, is printed together with the link
address (if applicable).
For FICON cascade switching, the link address will be
shown as a two-byte number. If a path from the control unit is via
cascaded FICON switches, the link between the FICON switches is not
shown. Instead, the control unit port of the switch connected to the control unit
and the CHPID port of the switch connected to the channel path are
shown. If no port connections are defined, switch data is extracted
from the dynamic switch and the link address. Port IDs are shown as
one-byte port addresses.
The 'DEVICE' column shows the devices which are attached to the
control unit printed under column 'CU IN LCU'. If the control unit
is attached to more than one channel path, the information about the
attached devices is printed together with the last printed channel
path. The devices attached to a control unit are grouped according
to consecutive number. The report shows the starting device number
and range of the device group.
Columns 'LOG. PATHS PER CU' and 'LOGICAL PATHS PER CU
PORT' display the number of defined logical paths.
Figure 169. Control Unit Detail Report
CONTROL UNIT DETAIL REPORT TIME: 16:12 DATE: 2012-10-21 PAGE H- 2
LOG. -CHAINED/CASC- LOGICAL
CONTROL UNIT PROCESSOR. PATHS CU IN CU- SWITCH CU PR SWITCH CU PR CHPID . -- DEVICE -- PATHS PER
NUMBER TYPE-MODEL CSS ID PER CU LCU IOCL ADD ID PN PN ID PN PN LINK ADDR NUMBER,RANGE CU PORT
_____________________ __________ ______ _____ ____ ___ ______ __ __ ______ __ __ _________ ____________ ________
0950 1750 PROC03.1 4 0950 3 17 5C 14 52 35 . 685C 20
17 60 14 4E 41 . 6860 0950,80 20
-----------------------------------------------------------------------------------------------------------
PROC03.2 4 0950 3 17 5C 14 52 35 . 685C 20
17 60 14 4E 41 . 6860 0950,80 20
----------------------------------------------------------------------------------------------------------------------------------
0B20 2105 PROC03.0 2 0B20 2 17 45 14 52 35 . 6845 27
17 49 14 4E 41 . 6849 0B20,152 27
-----------------------------------------------------------------------------------------------------------
PROC03.1 2 0B20 2 17 45 14 52 35 . 6845 27
17 49 14 4E 41 . 6849 0B20,152 27
-----------------------------------------------------------------------------------------------------------
PROC03.2 4 0B20 2 17 45 14 52 35 . 6845 27
17 49 14 4E 41 . 6849 0B20,152 27
-----------------------------------------------------------------------------------------------------------
PROC03.3 2 0B20 2 17 45 14 52 35 . 6845 27
17 49 14 4E 41 . 6849 0B20,152 27
----------------------------------------------------------------------------------------------------------------------------------
0BC0 2105 PROC03.0 2 0BC0 4 17 45 14 52 35 . 6845 18
17 49 14 4E 41 . 6849 0BC0,144 18
-----------------------------------------------------------------------------------------------------------
PROC03.1 2 0BC0 4 17 45 14 52 35 . 6845 18
17 49 14 4E 41 . 6849 0BC0,144 18
-----------------------------------------------------------------------------------------------------------
PROC03.2 4 0BC0 4 17 45 14 52 35 . 6845 18
17 49 14 4E 41 . 6849 0BC0,144 18
-----------------------------------------------------------------------------------------------------------
PROC03.3 2 0BC0 4 17 45 14 52 35 . 6845 18
17 49 14 4E 41 . 6849 0BC0,144 18
----------------------------------------------------------------------------------------------------------------------------------
0C50 2105 PROC03.0 2 0C50 5 17 45 14 52 35 . 6845 9
17 49 14 4E 41 . 6849 0C50,170 9
-----------------------------------------------------------------------------------------------------------
PROC03.1 2 0C50 5 17 45 14 52 35 . 6845 9
17 49 14 4E 41 . 6849 0C50,170 9
-----------------------------------------------------------------------------------------------------------
PROC03.2 4 0C50 5 17 45 14 52 35 . 6845 9
17 49 14 4E 41 . 6849 0C50,170 9
-----------------------------------------------------------------------------------------------------------
PROC03.3 2 0C50 5 17 45 14 52 35 . 6845 9
17 49 14 4E 41 . 6849 0C50,170 9
----------------------------------------------------------------------------------------------------------------------------------
| PROCESSOR.CSS ID | Designates the processors, and in case of an XMP processor, the
channel subsystem to which the CU is attached. | | LOG. PATHS PER CU | Specifies the number of defined logical paths for a control
unit per channel subsystem. | | CU IN LCU | Designates which CUs belong to the logical CU. | | IOCL | Designates I/O concurrency level (same as SHARED in IOCP). Specifies the level
of concurrency of I/O requests that the parallel channel path allows
for the control unit (CU).
- 1
- One I/O request at a time. (SHARED=Y)
- 2
- Multiple I/O requests at a time. (SHARED=N)
| | CU-ADD | Designates the CU address. | | SWITCH ID | Designates the switch the CU is connected to. | | CU PN | Designates the port the CU is physically connected to. | | PR PN | Designates the entry port of the channel (except in the case
of chained switches) | | CHAINED/CASC (SWITCH ID, CU PN, PR PN) | Designates a possible second switch the CHPID is connected
to. | | CHPID . LINK ADDR | Designates the channel path and the one- or two-byte link address
to which the control unit is connected. n(*)
in this column indicates that the control unit is connected to n managed channel paths. | | DEVICE NUMBER,RANGE | Specifies information about the devices that are attached to
the processors by the control unit. | | LOGICAL PATHS PER CU PORT | Specifies the number of defined logical paths for all control
units connected to a specific port. |
Device Summary Report
The Device Summary Report gives you an overview of the devices
defined in the currently accessed IODF and their attaching control
units. The devices are grouped according to the same characteristics.
The report shows the starting device number and the range of the
group.
For multi-exposure devices, the base devices are grouped separately
from the non-base exposure devices.
Figure 170. Device Summary Report
DEVICE SUMMARY REPORT TIME: 16:04 DATE: 2012-10-21 PAGE I- 2
--- DEVICE --- DEVICE SERIAL PPRC
NUMBER,RANGE TYPE-MODEL ATTACHING CONTROL UNITS NUMBER DESCRIPTION VOLSER USE
______________ _____________ |____|____|____|____|____|____|____|____| __________ ________________________________ ______ ____
0080,16 3174 0080 Merian SNA Connection
0090,2 RS6K 0110
0092,2 RS6K 0112
0094,2 RS6K 0114
0096,2 RS6K 0116
01C0 3270-X 01C0 Console Real and Virt.
01C1,31 3270-X 01C0 Terminal
2100,25 3390A 2124
2200,25 3390B 2126 U
2300,25 3390B 2126 D
2400,25 3390B 2128 D
0300,32 9345 300A 300B
0320,32 9345 320A 320B
0340,32 9345 340A 340B Real Dasd (9345 340-35f) MVSLIB
0360,32 9345 360A 360B Real Dasd (9345 360-37f) TSO001
Device Detail Report
The Device Detail Report lists all devices defined in the currently
accessed IODF, with their attributes and attachment information. Each
device is shown with the processors to which it is attached. The device
- processor attachment attributes are also listed. If
applicable, the subchannel set where the device is located, is also
shown in column SS. If not applicable, this column shows a blank.
For each processor the device is attached to, the CUs for the attachment
to the processor, as well as the channel path(s) the CU is attached
to, are also listed.
The starting device number and the range of subsequent device numbers
are shown in one row. A range value of 1 is omitted.
The Device Detail Report shows a partition matrix which indicates
whether a logical partition of a corresponding processor has access
to the device either via the channel path access list or the channel
path candidate list, and whether a partition is excluded or included
via the device candidate list. Devices with a null-device
candidate list are excluded from the report.
At the end of the report, for SMP processors, the totals for the following
items are listed for each processor:
- CHPIDS
- PHYSICAL CONTROL UNITS
- SUBCHANNELS
- LOGICAL CONTROL UNITS
For the CHPID total, the report lists separate values for the total
shared and the total unshared. For the physical CU total, HCD reports
the total shared (those attaching to shared channel paths) and the
total unshared.
For the subchannel and logical CU totals, the report lists separate
values for the shared, unshared, and additional unshared counts that
are, respectively, assigned and unassigned to a logical partition.
The shared count is the total number assigned to shared channel paths.
The generated for LPAR unshared count is the total that would have
been generated for a basic IOCDS. The additional unshared count contains
the unshared values that were generated for the LPAR IOCDS.
The TOTAL value is the total that would have been contained in
the generated IOCDS. The HSA TOTAL is the total that will exist in
the HSA after POR. At the completion of POR, the HSA may contain more
subchannels and logical CUs than does the IOCDS.
For XMP processors, the following totals are reported:
- CHPIDS
- PHYSICAL CONTROL UNITS
- DEVICES
- LOGICAL CONTROL UNITS
The column CSS TOTAL lists the number of CHPIDs,
physical and logical control units and the maximum number of devices
that are currently defined for that channel subsystem.
The column IOCDS TOTAL lists the number of CHPIDs,
physical and logical control units and the maximum number of devices
without definitions caused by over-defined CHPIDs.
Columns HSA TOTAL and HSA LIMIT are not applicable
for XMP processors.
The column USER LIMIT lists the maximum number of
devices defined by the user for that channel subsystem.
The column SUPPORTED LIMIT lists the maximum number
of CHPIDs, physical and logical control units and the maximum number
of devices that are supported for the processor for that channel subsystem.
Figure 171. Device Detail Report
DEVICE DETAIL REPORT TIME: 13:33 DATE: 2012-10-21 PAGE J- 1
DEVICE DEVICE PROCESSOR. SS UNIT TIME STA PREFERRED CNTL UNIT CHPID. PARTITION NUMBERS
NUMBER TYPE-MODEL CSS ID ADDR OUT DET CHPID PORT NUMBER CUADD LINK |1|2|3|4|5|6|7|8|9|A|B|C|D|E|F| SIDE
__________ _____________ __________ __ ____ ____ ___ _________ ____ ______ _____ __._____ _______________________________ ____
0000,8 3390A GOLDENE1.0 0 00 NO YES 0000 00 |A| |A| | | | | |-| | | | | |A|
01 |A| |A| | | | | |-| | | | | |A|
02 |A| |A| | | | | |-| | | | | |A|
GOLDENE1.1 0 00 NO YES 0000 00 |A| |A| | | | | |A| | | | | |A|
02 |A| |A| | | | | |A| | | | | |A|
GOLDENE1.2 0 00 NO YES 0000 00 | | | | |C|A| | | | | | | | | |
01 | | | | |C|A| | | | | | | | | |
GOLDENE1.3 0 00 NO YES 0000 00 | |-| | |-| | | | | | | | |A| |
-----------------------------------------------------------------------------------------------------------------------------------
...
-----------------------------------------------------------------------------------------------------------------------------------
0020,16 3380A GOLDENE1.0 1 30 NO YES 0000 00 |A| |A| | | | | |A| | | | | |A|
01 |A| |A| | | | | |A| | | | | |A|
02 |A| |A| | | | | |A| | | | | |A|
GOLDENE1.1 1 30 NO YES 0000 00 |A| |A| | | | | |A| | | | | |-|
02 |A| |A| | | | | |A| | | | | |-|
GOLDENE1.2 1 30 NO YES 0000 00 | | | | |C|A| | | | | | | | | |
01 | | | | |C|A| | | | | | | | | |
GOLDENE1.3 1 30 NO YES 0000 00 | |-| | |-| | | |+| | | | |A| |
-----------------------------------------------------------------------------------------------------------------------------------
DEVICE DETAIL REPORT TIME: 13:33 DATE: 2012-10-21 PAGE J- 2
LEGEND FOR PARTITION NUMBERS FIELD:
___________________________________
A - PARTITION IS IN CHPID'S ACCESS LIST
C - PARTITION IS IN CHPID'S CANDIDATE LIST ONLY
BLANK - PARTITION IS NOT IN CHPID'S ACCESS OR CANDIDATE LIST
- - PARTITION IS IN CHPID'S ACCESS OR CANDIDATE LIST BUT PARTITION IS EXCLUDED FROM DEVICE'S CANDIDATE LIST
+ - PARTITION IS NOT IN CHPID'S ACCESS OR CANDIDATE LIST BUT PARTITION IS INCLUDED IN DEVICE'S CANDIDATE LIST
DEVICE DETAIL REPORT TIME: 13:33 DATE: 2012-10-21 PAGE J- 3
PROCESSOR: GOLDENE1
CSS ID: 0
PARTITION
NUMBER NAME
______ ________
1 GECSS01X
3 GECSS03X
9 GECSS09X
F GECSS0FX
TOTALS FOR CHPIDS, DEVICES AND CONTROL UNITS
CSS IOCDS USER SUPPORTED
TOTAL TOTAL LIMIT LIMIT
_____ _____ _____ _________
CHPIDS _______________________ 3 3 N/A 256
PHYSICAL CONTROL UNITS _______ 1 1 N/A 8192
DEVICES IN SUBCHANNEL SET 1__ 32 32 1000 64512
DEVICES IN SUBCHANNEL SET 2__ 32 32 300 65535
LOGICAL CONTROL UNITS ________ 1 1 N/A 4096
|
z/OS HCD User's Guide
Copyright IBM Corporation 1990, 2014