IBM S390 FICON Implementation Guide

IBM S/390 FICON Implementation Guide
Ken Trowell, Dennis Ng, John Stimson,

Craig Vernon, Lothar Zimmermann
International Technical Support Organization
www.redbooks.ibm.com
SG24-5169-00
SG24-5169-00
International Technical Support Organization
November 1999
Take Note!
Before using this information and the product it supports, be sure to read the general information in Appendix B,
“Special notices” on page 111.
First Edition (November 1999)
This edition applies to the IBM 9672 Generation 5 and 6 at LIC driver level 22 (or higher) planning to install FICON
channels in FCV mode, and the IBM 9032 Model 5 ESCON Director at an LIC level of 5.1 or higher to support the
FICON Bridge adapter.
Comments may be addressed to:

IBM Corporation, International Technical Support Organization
Dept. HYJ Mail Station P099
522 South Road
Poughkeepsie, NY 12601-5400
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way
it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1999. All rights reserved.

Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
The team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Comments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Chapter 1. About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Chapter 2. Why implement FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Chapter 3. Introduction to FICON implementation . . . . . . . . . . . . . . . . . . . .7

3.1 FICON prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3.2 FICON design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Part 2. Configuration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Chapter 4. Implementation of a simple FICON configuration . . . . . .. . . . .13

4.1 Example of a simple FICON configuration . . . . . . . . . . . . . . . . . . . .. . . . .13
4.1.1 CHPID Placement Report . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .14
4.1.2 ESCON Director Placement Report . . . . . . . . . . . . . . . . . . . . .. . . . .15
4.2 Implementation sequence for a simple FICON configuration . . . . . .. . . . .17
Chapter 5. Planning of a complex FICON configuration . . . . . . . . . . . . . . .19

5.1 Example of a complex FICON configuration . . . . . . . . . . . . . . . . . . . . . . .19
5.1.1 Customer design extract for a complex FICON configuration. . . . . . .20
5.2 CHPID Placement Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
5.2.1 CHPID Placement Report example . . . . . . . . . . . . . . . . . . . . . . . . . .22
5.3 9032 Model 5 Placement Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Chapter 6. FICON Implementation Worksheets . . . . . . . . . . . . . . . . .. . . . .31

6.1 Configuration Definition - Impact Worksheet . . . . . . . . . . . . . . . . . .. . . . .31
6.2 ESCON Director Impact Analysis Worksheet . . . . . . . . . . . . . . . . .. . . . .32
6.3 Phase Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .32
6.4 Completing the Configuration Definition - Impact Worksheet . . . . . .. . . . .33
6.5 Completing the ESCON Director Impact Analysis Worksheet . . . . .. . . . .36
6.6 Completing the Phase Planning Worksheet. . . . . . . . . . . . . . . . . . .. . . . .38
Part 3. Implementation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Chapter 7. Processor phase actions . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .45

7.1 Phase Perform Worksheet completion instructions . . . . . . .. . . . . .. . . . .45
7.1.1 Phase # Row. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .47
7.1.2 Delete Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .47
7.1.3 Delete/Move Row . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .49
7.1.4 Add Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .52
7.1.5 Bridge row. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .54
7.2 Example of completed Phase Perform Worksheets . . . . . . .. . . . . .. . . . .54
7.3 Sorting phase actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .58
© Copyright IBM Corp. 1999 iii

Chapter 8. ESCON Director phase actions. . . . . . . . . . .. . . . . .. . . . . .. . 61
8.1 Phase Perform Worksheet completion instructions . . .. . . . . .. . . . . .. . 61
8.1.1 For each phase row . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . .. . 63
8.2 Example of completed Phase Perform Worksheets . . .. . . . . .. . . . . .. . 67
8.3 Sorting phase actions . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . .. . 72
8.4 ESCD Phase Perform Summary Table . . . . . . . . . . . .. . . . . .. . . . . .. . 73
Chapter 9. Pre-phase insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

9.1 Phase evaluation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 10. Phase merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

10.1 Analysis of phase contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Part 4. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 11. Executing the install actions . . . . . .. . . . .. . . . . .. . . . . .. . 81

11.1 Executing processor actions . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 81
11.1.1 Definition actions . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 81
11.1.2 Vary Off actions . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 82
11.1.3 Hardware actions . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 82
11.1.4 Vary On actions . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 83
11.2 Executing ESCD actions . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 83
11.2.1 Definition actions . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 83
11.2.2 Vary Off actions . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 84
11.2.3 Hardware actions . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 84
11.2.4 Vary On actions . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . . .. . 85
Part 5. Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Chapter 12. FICON post-install . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 89

12.1 Verification procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 89
12.2 Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 90
12.2.1 Channel Path Measurement Facility (CPMF) Modes . . .. . . . . .. . 90
12.2.2 Capacity planning and performance monitoring . . . . . . .. . . . . .. . 92
12.3 Problem diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 95
12.3.1 Error types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 95
12.3.2 Error indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 97
12.3.3 Diagnostic data and tools. . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 98
12.3.4 Diagnostic procedure . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. 102
Appendix A. Blank FICON planning worksheets . . . . . . . . . . . . . . . . . . . . .105
Appendix B. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Appendix C. Related publications . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 113

C.1 International Technical Support Organization publications . . . ...... . . . . . 113
C.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 113
C.3 Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 113
How to get ITSO redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

IBM Redbook Fax Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
iv FICON Implementation Guide

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
ITSO redbook evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
v
vi FICON Implementation Guide
Figures
1. FCV configuration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Customer design and implementation flowchart . . . . . . . . . . . . . . . . . . . . . . . . 4
3. FICON configuration design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Configuration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. FICON design - no availability impact to current configuration . . . . . . . . . . . . 13
6. CHPID Placement Report for a simple FICON implementation - no impact . . 14
7. CHPID Placement Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Default Placement Report for IBM 9032 ESCON Director Model 5 . . . . . . . . . 16
9. Recommended FICON Bridge plugging for an ESCON Director . . . . . . . . . . . 17
10. Simple FICON configuration - IOCDS example . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Example of a complex FICON configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 20
12. Example of a CHPID Placement Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. CHPID report for FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
14. Example of CHPID Report - CHPID changes/card moves and I/O deleted . . . 25
15. Example of a 9032-5 Placement Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
16. Recommended plugging for ESCON Director model 5 . . . . . . . . . . . . . . . . . . 29
17. FICON Implementation Worksheets - how they relate to each other . . . . . . . . 31
18. Configuration Definition - Impact Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . 35
19. ESCON Director Impact Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
20. Phase Planning Worksheet number 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
21. Phase Planning Worksheet number 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
22. Implementation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
23. Phase Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
24. Phase Perform Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
25. Phase Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
26. Phase Perform Worksheet for Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
32. Phase Perform Worksheet for Phase 2 Unsorted . . . . . . . . . . . . . . . . . . . . . . 59
33. Phase Perform Worksheet for Phase 2 Sorted . . . . . . . . . . . . . . . . . . . . . . . . 59
34. ESCON Director impact analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
35. Phase Perform Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
36. Logical port addresses relative to Slot # . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
37. ESCON Director Impact Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
38. Phase Perform Worksheet - Phase 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
44. ESCON Phase Perform Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
45. Installation instructions and actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
46. RMF Monitor II Channel Path Activity Report with CPMF=COMPAT . . . . . . . 90
47. RMF Monitor I Channel Path Activity Report with CPMF=COMPAT . . . . . . . . 91
48. RMF Monitor II Channel Path Activity Report with CPMF=EXTENDED . . . . . 91
49. RMF Monitor I Channel Path Activity Report with CPMF=EXTENDED . . . . . . 92
50. I/O showing Device Active Only (DAO) time . . . . . . . . . . . . . . . . . . . . . . . . . . 94
© Copyright IBM Corp. 1999 vii

51. DAO Measurement Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
52. Typical error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
53. RMF Monitor II IOQUEUE and Device Activity Report . . . . . . . . . . . . . . . . . . 100
54. System Trace Table - ORB in SSCH entry and IRB in I/O entry. . . . . . . . . . . 101
55. Blank configuration definition - configuration worksheet . . . . . . . . . . . . . . . . . 105
56. Blank ESCON Director Impact Analysis Worksheet . . . . . . . . . . . . . . . . . . . . 106
57. Blank Phase Planning Worksheet - No. 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
58. Blank Phase Planning Worksheet - No. 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
59. Phase Perform Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
viii FICON Implementation Guide

Preface
This redbook covers the practicalities of implementing S/390 FICON channels
operating in FCV mode into an existing S/390 ESCON channel environment. It
describes all stages of implementing the FICON channel in FCV mode which
includes the installation of the FICON Bridge adapter in the 9032 Model 5
ESCON Director, and the OS/390 definition changes to support the movement of
control units from ESCON to FICON (FCV mode) channels.
The team that wrote this redbook

This redbook was produced by a team of specialists from around the world
working at the International Technical Support Organization Poughkeepsie
Center.
Ken Trowell is a S/390 Systems Specialist at the International Technical Support

Organization, Poughkeepsie Center. He writes extensively and presents at IBM
workshops worldwide on all areas of S/390 Processors, Channels, Channel
Topology, and S/390 Architecture. Before joining the ITSO 3 years ago, Ken has
worked in a number of countries during his extensive career in IBM, providing
system support and consulting activities in the S/390 area.
Dennis Ng works at the IBM WSC in Gaithersburg Maryland as a processor and

I/O configuration Support Specialist. Dennis also provides support for the 9032-5
ESCON Director which is part of the FICON implementation. Before joining the
IBM WSC he worked as an IBM SE S/390 specialist.
John Stimson is a Senior IT Consultant working for IBM in the United Kingdom.
He has 15 years of experience in OS/390 and S/390 Server hardware. He has
worked at IBM for 17 years. His areas of expertise include S/390 connectivity,
Parallel Sysplex, and Server Consolidation. He has written extensively on
OS/390, Geographically Dispersed Parallel Sysplex, GDPS and Peer-to-Peer
Remote Copy (PPRC).
Craig Vernon is an Advisory IT Specialist in IBM Australia. He has 18 years of

experience in OS/390 and large systems. He has worked at IBM for 10 years. He
holds degrees in computing science and in law. His areas of expertise include
OS/390 software problem diagnosis and RACF conversions.
Lothar Zimmermann is an IT Specialist in IBM Germany working for PSS. He

has worked on S/390 large systems. His areas of expertise includes both S/390
processors and S/390 I/O Configurations in the ESCON environment.
Comments welcome
Your comments are important to us!
We want our redbooks to be as helpful as possible. Please send us your

comments about this or other redbooks in one of the following ways:
• Fax the evaluation form found in “ITSO redbook evaluation” on page 119 to the
fax number shown on the form.
• Use the online evaluation form found at http://www.redbooks.ibm.com/
© Copyright IBM Corp. 1999 ix

• Send your comments in an internet note to redbook@us.ibm.com
x FICON Implementation Guide

Part 1. Introduction
© Copyright IBM Corp. 1999 1

2 FICON Implementation Guide
Chapter 1. About this book
This redbook will help you with the configuration planning, implementation
planning, and installation of FICON channels on an IBM 9672 G5/G6 Processor
and the IBM FICON Bridge Adapter on the IBM 9032 model 5 ESCON Director.
The arrows to the right of the chart in Figure 1 lead to the Implementation Phase,
the subject of this redbook.
Concurrent S/390 I/O Configuration
FICON Customers' I/O FICON

Knowledge Configurations and Benefits
Topology Requirements
FICON Configuration Design

Customer documents Processor and ESCD Changes Implementation
the configuration Aggregation - I/O Connectivity Phase
and design changes
FICON Ordering
Channel - Bridge - Cabling
IBM provides 9672 Implementation

these reports Phase
CHPID Report
Figure 1. FCV configuration planning
Figure 2 on page 4 presents a flowchart of the steps required to design, configure

and implement FICON.

Configuration Configuration Implementation
Design and Order Planning Planning Install
Customer IBM Customer Customer Customer Customer Customer

and IBM and IBM and IBM and IBM
Configuration Ordering Determine Determine Determine Build an Installation &

impact on FICON channel impact of each Implementation
Design Resource install task
CHPID and FICON sequence,.
Topology Plan numbers Bridge then build
list, per phase Definitions
I/O Resources ahead install Definitions Vary off
CPR FICON
Characteristics Design sequence channel Vary off Hardware
or install phases Activate
Benefit Review
Hardware
Addressing CPR phases Vary on
IBM FICON Activate
Customer
Fiber channel configuration Vary on
Consolidation install
Aggregation sequence
Distance (IBM CPR)
CPR phases
Customer's
configuration
IBM FICON Planning Guide IBM FICON Implementation

Redbook Redbook
Figure 2. Customer design and implementation flowchart
This book provides descriptions of the configuration planning, implementation

planning and installation steps required for both a simple FICON configuration
and a more complex FICON configuration.
The simple FICON configuration is described in Chapter 4, “Implementation of a

simple FICON configuration” on page 13. This simple configuration provides an
example of local-to-remote site connectivity using S/390 FICON channels in FCV
mode.
The complex FICON configuration is described in Chapter 5, “Planning of a

complex FICON configuration” on page 19. This complex configuration provides
an example of channel aggregation to provide constraint relief, thereby enabling
the installation of additional DASD subsystems to a processor that was already
fully configured with ESCON and other channel types (that is, there are no more
free I/O slots and CHPID numbers available for the installation of FICON
channels).

Chapter 2. Why implement FICON
Today some IBM S/390 customers are experiencing limitations in their S/390
ESCON environment that S/390 FICON channels (in FCV mode) may help
overcome.
Enhancements to the customer's S/390 ESCON channel environment may be

provided by S/390 FICON channels (in FCV mode) for system environments that
are experiencing:
1. S/390 256 ESCON channel constraint
2. 9672 ESCON channel 1024 device address limitation (per channel)
3. Data rate performance droop at extended distances (over 9 km)
4. High fiber cabling costs between local and remote sites
5. Distance limitations for dark fiber
FICON native channels (operating in FC mode) support different requirements

and are not covered in detail in this version of the FICON Implementation Guide.
Channel constraint relief

Channel constraint occurs when the customer wants to install additional ESCON
channels to support attachment of additional I/O, but his S/390 processor is
already at or near the S/390 256 channel architecture limit (244 channels or
greater are installed). FICON channels (in FCV mode) provide additional I/O
connectivity, while keeping within the S/390 256 channel architecture limit. Be
aware that when moving workloads from ESCON to FICON (in this channel
constraint case), you should aim to move the workloads of 5 to 8 ESCON
channels (a minimum of 5) to a FICON channel (in FCV mode) on an IBM 9672
Processor.
Device addressing limitation relief

The IBM 9672 Processor ESCON channel implementation limits the device
support to 1024 devices (subchannel/device numbers) per channel, whereas an
IBM 9672 Processor FICON channel (in FCV mode) can be used to support up to
16 K devices. Customers that are at or near the S/390 256 ESCON channel
architecture limit and are experiencing the 1024 device number implementation
limit (some DASD CUs today require the support of 1024 device numbers) can
install a FICON channel (in FCV mode) and then connect a second 1024 device
CU on the same FICON channel, as well as support the other ESCON CUs that
were aggregated onto the same FICON channel (in FCV mode). Again, the aim
for an IBM 9672 FICON channel (in FCV mode) must be to move a minimum of 5
ESCON connections/workloads onto the one FICON (FCV) channel (in this
address constraint case).
Impact of Data Rate droop at distance reduced

As the ESCON channel-to-an-ESCON-attached CU distance is increased, the
performance decreases (reduced data transfer rate) up to a point of 9 km, where
the performance decreases more rapidly. This point of sudden rapid decrease in
performance is called the distance data rate droop point . For FICON channel
links the distance where this data rate droop point occurs is not until 100 km. This
allows the customer to get the benefit of extended distance from a FICON
channel (in FCV mode) without having the same performance impact as seen on
Chapter 2. Why implement FICON 5

the ESCON channels after the 9 km distance (allowable device connectivity
distances must still be considered on the ESCON links).
Fiber cabling cost reduction

Multiple ESCON channel fibers between two extended distance sites can be very
expensive. With the use of FICON channels (in FCV mode) between two sites we
would expect the customer to get up to an 8-to-1 reduction in the number of fibers
required to connect the two sites. This, in most cases, will benefit the customer
via a reduction (or prevention) of the overall cost of the fiber infrastructure.
Supported distances increased

Some customers prefer the use of dark fiber with no retransmission of the fiber
signal. Using ESCON LED channels, dark fiber distances can only be 3 km, while
using FICON single mode 9-micron fiber, the dark fiber distance can be extended
to 10 km or even to 20 km with an IBM-approved RPQ.

Chapter 3. Introduction to FICON implementation
A FICON channel can operate in one of two modes:
1. FICON converter (FCV) mode using a FICON bridge adapter in an IBM 9032
model 5 ESCON Director.
2. FICON native (FC) mode, either point-to-point or switched point-to-point
through a fiber channel standard switch.
This redbook only covers the FICON channels operating in FCV mode.
A FICON channel implementation plan can vary greatly in complexity, from what
might be a very straightforward non disruptive installation of hardware and
software, to a more complex staged approach where some hardware actions are
concurrent but require a number of phases which might be disruptive to normal
operations.
The FICON implementations that require the most careful planning are those that
have no spare I/O slots (or not enough) in the IBM 9672 processor, and those that
have no spare port slots (or not enough) in the IBM 9032 model 5 ESCON
Director.
This book provides implementation plans to cover both the simple implementation
and the more complex scenarios where there are not enough spare I/O slots in
the processor or not enough ports in the ESCON Director.
A number of worksheets have been developed throughout this implementation

guide to assist in the implementation of complex multi-stage FICON installations.
Blank copies of these worksheets can be found in Appendix A.
3.1 FICON prerequisites

Planning for the implementation of FICON is covered in the IBM S/390 FICON
Planning Guide, SG245445. This guide covers all the hardware and software
prerequisites for FICON and also assists in the preparation of a FICON design.
The implementation of the hardware, microcode and software prerequisites for

FICON can be done at various points in the overall implementation plan. These
prerequisites include:
• Installation of Driver 22 or higher on the IBM 9672
• Installation of FICON Enablement features on the IBM 9032 model 5
• Installation of software PTFs, and possibly HCM
• Installation of cables
Clearly, in some installations these prerequisites may already be installed, or

could be scheduled in advance during a scheduled maintenance slot, or may
need to be implemented at the same time as the installation of the FICON
channels and bridge adapters.
In our case, let us take each one in turn and assume that they are to be
implemented prior to the FICON channel installation.

Licensed Internal Code, LIC, for IBM 9672 Processors
FICON is supported at Driver Level 22 and above on the IBM 9672 G5 and G6
CMOS processors. Driver Level 22 is the initial base level on all IBM G6 CMOS
Processors.
The implementation of Driver Level 22 is a disruptive process. Consult an IBM

Customer Service representative to find out how much time is required to install
the new microcode level.
The installation of the LIC to support FICON is recommended to be done as far in

advance of the installation of FICON channels as possible, to avoid multiple
change activities going on at the same time.
Prior to physical implementation of the FICON channels, the IBM Customer

Service representative may need to install additional microcode patches (MCLs)
to bring the processor up to the latest level. These MCLs can usually be installed
non disruptively.
FICON enablement feature FC5700 on IBM ESCON Director model 5

The FICON enablement feature, FC 5700, provides:
• Licensed Internal Code (LIC)
• A new Matrix Controller card, MXC2
• New power supplies
All new orders for the IBM ESCON Director model 5 are shipped with the FICON
enablement feature.
Consult an IBM Customer Service Representative to ascertain the current

configuration of a particular Director, and also to understand whether the
installation of the enablement feature is necessary. Your Customer Service
Representative will also be able to advise on how long this upgrade will take.
The installation of the FICON enablement feature, FC 5700, should be done as

far in advance of the installation of the FICON bridge adapter as possible, to
avoid multiple change activities going on at the same time.
The physical installation of the ESCON Director Bridge Adapter in an IBM 9032
model 5 Director can be non disruptive, provided the installed machine has the
following features already installed:
• Redundant Central Control Processor, CTP, feature #5500
• Redundant Matrix Controller Card, MXC, feature #5600
However, if these features are not installed the ESCON Director must be taken
out of normal operation in order to replace parts and upgrade the LIC.
Installation of software PFTs, and possibly HCM

The FICON Planning Guide provides a description of the software prerequisites
for FICON. Customers should obtain the latest PSP 9672DEVICE subset
9672OS390G5+ bucket from IBM for the most up-to-date list of required software
support, and also contact their ISVs for the latest software and fixes for their
environment.

The installation of the software prerequisites should be done as far in advance of
the installation of FICON hardware as possible, to avoid multiple change activities
going on at the same time.
Installation of cables.
IBM S/390 FICON Planning Guide, SG24-5445, provides a description of the
types of fiber cables required to support FICON.
Using the FICON Configuration Definition - Configuration Worksheet described in

6.1, “Configuration Definition - Impact Worksheet” on page 31 may help in the
identification of cables that are moved during the implementation of FICON
channels and the aggregation of ESCON channels to FICON.
The installation of the fiber trunk cables and jumper cables should be done as far
in advance of the installation of FICON hardware as possible to reduce the time
to implement any change in the I/O configuration of a system.
3.2 FICON design

A customer’s FICON design is used as input to the FICON order and the
implementation phase; see Figure 3. IBM S/390 FICON Planning Guide,
SG24-5445, will assist the customer in developing a valid design that meets the
connectivity requirements of the installation.
The design should document any changes to the I/O configuration of a processor
made as a result of installing FICON channels in the processor or FICON Bridge
Adapters in an ESCON Director. This includes all new connectivity, changes to
existing connectivity, and any control units/devices that have been removed from
the configuration. The design document should detail all the CHPID numbers and
control unit numbers that are affected by the installation of FICON, or by the
aggregation of ESCON onto FICON.
Concurrent S/390 I/O Configuration
FICON Customers' I/O FICON

Knowledge Configurations and Benefits
Topology Requirements
FICON Configuration Design

Customer documents Processor and ESCD Changes Implementation
the configuration Aggregation - I/O Connectivity Phase
and design changes
FICON Ordering
Channel - Bridge - Cabling
IBM provides 9672 Implementation

these reports Phase
CHPID Report
Figure 3. FICON configuration design
Chapter 3. Introduction to FICON implementation 9

The Customer design document, the IBM 9672 CHPID Placement Report, and
the IBM 9032 Model 5 Placement Report are essential documents in the
preparation of the implementation plan.

Part 2. Configuration planning
In this part of the book we use the customer design document and the IBM
Placement Reports for the IBM 9672 G5/G6 Processor and ESCON Directors to
determine the impact of the FICON installation and to plan the sequence of the
implementation. The Configuration Planning part of this book is highlighted in
Figure 4.



Design Resource and FICON install task
CHPID sequence,then
Topology Plan numbers Bridge build FICON
I/O Resources ahead CPR install Definitions Vary off
channel
Characteristics Design sequence install phases Vary off Hardware
or CPR phases Activate
Benefit Review Hardware
Addressing Customer Vary on
IBM FICON configuration Activate
Fiber channel Vary on
(IBM CPR)
Distance
CPR phases
Customer's
configuration

Redbook Redbook
Figure 4. Configuration planning

Chapter 4. Implementation of a simple FICON configuration
A simple FICON configuration is defined here as one that involves the addition of
FICON hardware and microcode without the need to remove or move existing
channel cards in the IBM 9672 CMOS Processor or port cards in the IBM 9032
Model 5 ESCON Director.
This chapter describes the implementation of a simple FICON configuration.

Chapter 5, “Implementation of a complex FICON configuration.” on page 17, and
subsequent chapters of this book describe a complex FICON configuration where
channel cards and port cards will be removed or moved.
The design of the FICON configuration, built with the aid of the IBM FICON
Planning Guide, SG24-5446, will have identified whether the implementation is
simple or complex.
Whether a configuration is simple or complex can be validated by checking the

the, and the 9032 Model 5 Placement Report produced by the IBM ordering
process. If processor channel cards or director port cards are moved during the
installation of the FICON channels or the FICON Bridge Adapter, then the
implementation will be complex.
4.1 Example of a simple FICON configuration

The FICON design produces a configuration to support the remote connection of
DASD and Tape in a new data centre approximately 9 km away from primary data
centre. A FICON implementation is chosen over ESCON to reduce the cost of
leasing the dark fiber between the two buildings
Four FICON channels from a single IBM 9672 G5/G6 Processor are sufficient to
provide the required capacity, performance and redundancy. Therefore, an order
is placed for four FICON channels and four FICON Bridge Adapters for two new
IBM 9032-005 ESCON Directors.
Fiber 9 km Fiber IBM 9032-005

Channel Patch ESCON ESCON
Patch Channel Directors CU
Panel Panel
Cabinet ESCON
Cabinet
CU
Diverse Fibre ESCON

4 FICON Routes CU
Channels
ESCON
CU
ESCON
Fiber Fiber CU
Channel Channel
Patch Patch ESCON
Panel Panel ESCON CU
Cabinet 7.5 km Cabinet Links
Site A Site B
Figure 5. FICON design - no availability impact to current configuration

4.1.1 CHPID Placement Report
The IBM order of the FICON channels produces a CHPID Placement Report for
the currently installed and new FICON channels that are to be added to the IBM
9672 G5/G6 Processor, and a Port Placement report for each of the 9032 Model 5
Directors ordered, or for the case where additional ports are added to an installed
9032 Model 5 Director.
The CHPID Placement Report in Figure 6 shows the four new FICON channels.
The FICON CHPIDs have been assigned the addresses F8, F9, FC, FD. These
are the addresses that must be used. No channels are moved or removed as a
result of this customer’s 9672 FICON CHPID installation. This is because the I/O
slots that the FICON channels will be installed in are currently empty. This
provides confirmation that this will be a simple installation, least as far as the IBM
9672 G5/G6 Processor is concerned.
9672-R66 S/N 69770 CHPID REPORT September 21, 1999

STI - CHA SLOT - CAGE LOCATION - I/O SLOT - CHPID/TYPE
0 - 24 - FRAME Z BOTTOM - 11 - 00/E 01/E 02/E 03/E
0 - 9 - FRAME Z BOTTOM - 29 - 08/E 09/E 0A/E 0B/E
0 - 24 - FRAME Z BOTTOM - 26 - 14/P4 15/P4 16/P4 17/P4
0 - 9 - FRAME Z BOTTOM - 8 - 1C/E 1D/E 1E/E 1F/E
1 - - FRAME Z BOTTOM - 21 - 24/C3 25/C3
4 - 24 - FRAME A BOTTOM - 11 - 80/E 81/E 82/E 83/E
4 - 9 - FRAME A BOTTOM - 29 - 88/E 89/E 8A/E 8B/E
4 - 24 - FRAME A BOTTOM - 26 - 94/P4 95/P4 96/P4 97/P4
4 - 9 - FRAME A BOTTOM - 8 - 9C/E 9D/E 9E/E 9F/E
5 - 23 - FRAME A BOTTOM - 22 - A0/E A1/E A2/E A3/E
5 - 16 - FRAME A BOTTOM - 18 - A8/E A9/E AA/E AB/E
5 - 16 - FRAME A BOTTOM - 17 - AC/E AD/E AE/E AF/E
5 - 23 - FRAME A BOTTOM - 15 - B0/E B1/E B2/E B3/E
5 - 23 - FRAME A BOTTOM - 14 - B4/2F
5 - 16 - FRAME A BOTTOM - 20 - B8/E B9/E BA/E BB/E
5 - 16 - FRAME A BOTTOM - 19 - BC/P4 BD/P4 BE/P4 BF/P4
6 - 30 - FRAME Z BOTTOM - 7 - C0/E C1/E C2/E C3/E
6 - - FRAME Z BOTTOM - 6 - C4/C3 C5/C3
6 - 4 - FRAME Z BOTTOM - 34 - C8/E C9/E CA/E CB/E
6 - 4 - FRAME Z BOTTOM - 33 - CC/E CD/E CE/E CF/E
6 - 4 - FRAME Z BOTTOM - 32 - D0/E D1/E D2/E D3/E
10 - - FRAME A BOTTOM - 6 - F8/H1 NEW
10 - - FRAME A BOTTOM - 7 - F9/H1 NEW
9 - - FRAME A BOTTOM - 31 - FC/H1 NEW
9 - - FRAME A BOTTOM - 32 - FD/H1 NEW
Figure 6. CHPID Placement Report for a simple FICON implementation - no impact
The second part of the CHPID Placement Report, shown in Figure 7 on page 15,
provides a sequence plan for the concurrent installation of the FICON CHPIDs.
The concurrent installation of the FICON cards must be done in the sequence
provided in the CHPID Placement Report; refer to Figure 7 on page 15.

FICON OSA-EXPRESS INSTALLATION DELETE CARDS, CHPID CHANGES/CARD MOVES & NEW CARDS
- STI - CHA SLOT - CAGE LOCATION - I/O SLOT - CHPID/TYPE
Sequence 001 - ACTION - FEATURE

FROM - 0 - - FRAME A BOTTOM - 31 - /AF - DELETE - 0012
TO - 9 - 0 - FRAME A BOTTOM - 31 - FC/H1 - NEW - 2314
--------------------------------------------------------------------------------
Sequence 002
TO - 10 - 0 - FRAME A BOTTOM - 6 - F8/H1 - NEW - 2314
--------------------------------------------------------------------------------
Sequence 003
TO - 9 - 0 - FRAME A BOTTOM - 32 - FD/H1 - NEW - 2314
--------------------------------------------------------------------------------
Sequence 004
TO - 10 - 0 - FRAME A BOTTOM - 7 - F9/H1 - NEW - 2314
--------------------------------------------------------------------------------
LEGEND FOR TYPE VALUES IN CHPID/TYPE COLUMN:
C1 - COUPLING LINK - #0216->#0007 OR 8P1967

C3 - COUPLING LINK - #0216->#0008
C0 - NO COUPLING LINK - #0216->
E - ESCON (LED, 3KM) - #2313
P4 - PARALLEL - #2304
2F - OSA2 FDDI - #5202
H1 - FICON CHANNELS - #2314
/AF - Air flow card - #0012
Figure 7. CHPID Placement Report
In the following extract from the CHPID Placement Report, Sequence 001- the Air
Flow card, /AF - is removed (DELETE) from slot 31 in the I/O cage at the bottom
of the A frame, to make way for the installation of the new FICON CHPID in the
same I/O slot and cage. The FICON CHPID will have address FC.
Sequence 001 -ACTION - REATURE

FROM - 0 - - FRAME A BOTTOM - 31 - /AF -DELETE - 0012
FROM - 9 - 0 - FRAME A BOTTOM - 31 - FC/H1 -NEW - 2314
4.1.2 ESCON Director Placement Report

The FICON Bridge Cards, if ordered at the same time as a new Director, will
come installed in the new IBM 9032 model 5 ESCON Directors.
The default plugging of port cards in an IBM 9032 model 5 ESCON Director,
shown in Figure 8 on page 16, is done for ease of later upgrade. Port cards are
placed in the lower quadrants of the Director so that later installation of port cards
in the top quadrants of the Director are not hindered by fiber cables. The use of
IBM’s Fiber Transport Services negates this problem, as fiber cable harnesses
are used within the Director to keep jumper cables tidy and in place.
The 9032 Model 005 Placement Report gives the logical port address of the two
FICON cards as 24 and 2C.
Chapter 4. Implementation of a simple FICON configuration 15

Figure 8 shows the default plugging of port cards in the IBM ESCON Director
model 5 as delivered by IBM. Only the bottom two quadrants are shown in this
figure. Quadrants 3 and 4 are empty, apart from the high availability feature of the
4-Port ESCON spare card.
9032 Model 005 Placement Report September 20, 1999

Model 005 Default Plugging Configuration
32 ESCON ports - 2 FICON ports - Spare port card (4 ESCON)
QUADRANT 2 QUADRANT 1
+---------------------------------------------------------------------------------+
| | | | | | | | | | | | FCV| FCV| ESC| ESC| ESC| ESC|
+---------------------------------------------------------------------------------+
| | | | | | | | | | | | 28 | 20 | 18 | 10 | 08 | 00 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | 2C | 24 | 1C | 14 | 0C | 04 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 19 | 11 | 09 | 01 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 1D | 15 | 0D | 05 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 1A | 12 | 0A | 02 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 1E | 16 | 0E | 06 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 1B | 13 | 0B | 03 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 1F | 17 | 0F | 07 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 1C | 14 | 0C | 04 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 20 | 18 | 10 | 08 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 1D | 15 | 0D | 05 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 21 | 19 | 11 | 09 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 1E | 16 | 0E | 06 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 22 | 1A | 12 | 0A |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | 1F | 17 | 0F | 07 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | 23 | 1B | 13 | 0B |
+---------------------------------------------------------------------------------|
| 15 | 14 | 13 | 12 | 11 | 10 | 09 | 08 | | 07 | 06 | 05 | 04 | 03 | 02 | 01 | 00 |
+---------------------------------------------------------------------------------+
----------- ------
| 4 | 3 | | 17 | - PHYSICAL PORT NUMBER
+----+----+ | |
| 2 | 1 | | 1B | - LOGICAL PORT ADDRESS
----------- ------
(FRONT VIEW)
Quadrant Locations ESC = Multimode ESCON 8 Port Card
in Machine Frame XDF = LASER XDF 8 Port Card
FCV = FICON Bridge Card
SP1 = 4 Port ESCON Spare
SP2 = 2 Port ESCON / 2 Port XDF Spare
Figure 8. Default Placement Report for IBM 9032 ESCON Director Model 5
Although the FICON Bridge Cards can be installed anywhere in the Director, IBM
recommends that port cards be moved, prior to implementation, to the
recommended configuration described in Figure 9 on page 17. The
recommended configuration balances ESCON and FICON Bridge Adapters
across all four quadrants of the Director for resilience and maximum availability.

Plugging Considerations
FICON Bridge port cards
Quadrant S S S S Quadrant Bridge port cards can be installed in any slot position
C C
T
P
T
P
4 3 except the spare port slot.
Port Port To provide the maximum availability, the bridge port
MXC/ MXC/
Addr. MXS MXS Addr. cards should be installed in the order of Quadrant 1,
Card Card 3, 2, 4.
FB - C4 set 1 set 2
C3 - 84
Shown are the recommended slot locations and installation
sequence for 4 FICON Bridge port cards; this allows for
0 1 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
high availability.
T T Quadrant 1 - FICON Bridge port address 0C
K K
R
G
R
G Quadrant 3 - FICON Bridge port address 84
Quadrant Quadrant Quadrant 2 - FICON Bridge port address 4C
0 1 2 1 Quadrant 4 - FICON Bridge port address C4
Port Port
Addr. Addr.
0 0 1 1 2 3
83 - 44 43 - 04
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Figure 9. Recommended FICON Bridge plugging for an ESCON Director
Therefore, in this example, the four initially provided ESCON Port cards in the
Director would be distributed evenly among the four quadrants of the Director.
Using slots that are not the preferred locations for FICON Bridge Adapters allows
for future requirements or upgrades. The ESCON Port Cards are installed in slots
0, 8, 17, and 25, giving the ESCON ports the logical addresses 04-0B, 44-4B,
8C-93, and CC-D3.
The two FICON Bridge Adapters are placed in Quadrant 1, slot 1, and Quadrant
3, slot 16, giving the logical port addresses 0C and 84.
4.2 Implementation sequence for a simple FICON configuration

1. Install hardware and software prerequisites.
The hardware and software prerequisites are covered in 3.1, “FICON
prerequisites” on page 7 of this book.
2. Create a new IODF for FICON connectivity.
The customer design, using the CHPID placement report, will have identified
the CHPID numbers, which target the Director and the port address of the
Director for each FICON channel. The CHPID Placement Report will provide
the CHPID numbers for the FICON channels.
Use HCD or HCM to create a new OS/390 IODF that includes the FICON
channels. In the example provided in this chapter, the new ESCON Directors
need to be added, along with the control units and devices in the remote site.
For simplicity, here only the FICON-related specific actions are discussed.
For HCD, do the following:
• Define the 9032 Model 5 ESCON Directors and their installed ports.
• Define each FICON, (FCV) CHPID connection to a target FICON Bridge
Adapter port address in a Director.
Chapter 4. Implementation of a simple FICON configuration 17

• Define the new control units and devices to the processor and to the
operating system.
For HCM, do the following:
• Define the new control units and devices to the processor and to the
operating system.
• Define the connection of each ESCON Director FICON Bridge (the port
address) to an FCV CHPID on the processor.
3. Install S/390 FICON Channels and IBM 9032 Model 5 ESCON Directors.
Concurrent installation of the FICON channels will be possible. New ESCON
Directors can be added dynamically to the I/O configuration.
4. Connect the fiber cables.
For complex fiber connections, that is, those involving more than one jumper
cable, experience has shown it is worthwhile for the customer or fiber provider
to do a confirmation test to verify that light can pass through the entire
physical fiber route and that send and transmit fibers are correctly crossed
throughout the connection.
5. Activate new IODFs.
6. Configure CHPIDs online.
7. Vary devices online.
The following extract from an OS/390 IOCDS (Figure 10) takes the simple FICON
installation example provided earlier in this chapter (Figure 5) and shows the
definition statements. One logical control unit with a range of devices is defined
with connectivity to two ESCON Directors (port addresses A3 and C3). These
ESCON Directors (switch 1 and switch 2) are connected via FICON Bridge
Adapters to FICON channels (F8, F9, FC and FD) operating in FCV mode.
ID MSG1='9672-R66', x
MSG2='FICON (FCV) CHANNEL TO ESCON CU DEFINITIONS', x
SYSTEM=(9672,6)
RESOURCE PARTITION=((LP1,1),(LP2,2),(LP3,3))
CHPID PATH=(F8),TYPE=FCV,SHARED,SWITCH=01, x
PARTITION=((LP1,LP2,LP3),(LP1,LP2,LP3))
CHPID PATH=(F9),TYPE=FCV,SHARED,SWITCH=02, x
CHPID PATH=(FC),TYPE=FCV,SHARED,SWITCH=01, x
CHPID PATH=(FD),TYPE=FCV,SHARED,SWITCH=02, x
*******************************************************************
**
** DASD CU 1000 and 1001, plus DEVICES 1000 to 103F
**
*******************************************************************
CNTLUNIT CUNUMBR=1000,PATH=(F8,FC),UNITADD=((00,64)), x
LINK=(A3,C3),UNIT=3990-6
CNTLUNIT CUNUMBR=1001,PATH=(F9,FD),UNITADD=((00,64)), x
LINK=(A3,C3),UNIT=3990-6
IODEVICE ADDRESS=(1000,064),UNITADD=00,CUNUMBR=(1000,1001), x
STADET=Y,UNIT=3390
Figure 10. Simple FICON configuration - IOCDS example

Chapter 5. Planning of a complex FICON configuration
A complex FICON implementation and configuration is defined here as one that
involves the installation of FICON channels, resulting in the removal or movement
of existing channel cards in the IBM 9672 G5/G6 Processor or port cards in an
IBM 9032 Model 5 ESCON Director.
This chapter and subsequent chapters of this book describe a complex FICON
configuration and implementation where channel cards and port cards are
removed or moved, these are detailed in:
Chapter 6, “FICON Implementation Worksheets” on page 31,
Chapter 7, “Processor phase actions” on page 45.
Chapter 8, “ESCON Director phase actions” on page 61
Chapter 9, “Pre-phase insertion” on page 75
Chapter 10, “Phase merging” on page 77
Chapter 11, “Executing the install actions” on page 81
The design of a FICON configuration, built with the aid of the IBM S/390 FICON
Planning Guide, SG24-5445, will have identified whether the implementation is
simple or complex.
Whether a configuration is simple or complex can be determined by checking the

the CHPID Placement Report and the 9032 Model 5 Placement Report produced
by the IBM order process. If processor channel cards or director port cards are
deleted or moved during the installation of the FICON channels or the FICON
Bridge Adapter, then the implementation is considered to be complex.
5.1 Example of a complex FICON configuration

The FICON design produces a configuration to support the attachment of
additional I/O to an already channel constrained processor. The design allows for
the installation of two new IBM 2105 Enterprise Storage Subsystems, on the
same channels, by providing additional I/O connectivity through aggregating
existing ESCON channels to FICON.
In this example, ESCON-to-FICON channel aggregation will remove the channel

constraint, but necessitate the move of some ESCON channel-to-control unit
connections to other channels within the processor and the removal of two
ESCON and two Parallel channel cards from the IBM 9672 CMOS Processor.
These card removals are necessary to make available I/O slots and CHPID
addresses in the processor for the installation of the FICON channels.
Two already installed IBM 9032 Model 5 ESCON Directors will also be upgraded
with FICON Bridge Cards.
The installation of the FICON Bridge Cards in one of the installed Directors
necessitates the relocation of ESCON ports to allow for the subsequent removal
of ESCON port cards. The design also highlights that the channel aggregation
activity sometimes necessitates moving port connections between Directors.

In summary, the example used for a complex FICON configuration includes a
single IBM 9672-RX6 Processor, and two IBM 9032 model 5 ESCON Directors.
The IBM 9672-RX6 already has all 64 normal channel I/O slots full, and one of
the Director port slots is full.
Figure 11 on page 20 provides a diagram of the complex FICON configuration

example. It depicts all the hardware installations, as well as the movement and
removal of other channel cards.
Remove
2 x ESCON Channel Cards
2 x Parallel Channel Cards
IBM 9672-RX6
IBM 9032-005 IBM 2105
Move ESCON
Director Port
Move 2 x cards to
ESCON alternate Director
Channel Cards
Install 2 new
Enterprise
Storage
Subsystems
Install 3 x FICON
Install
Bridge Adapters in
6 x FICON Cards each Director
Figure 11. Example of a complex FICON configuration
5.1.1 Customer design extract for a complex FICON configuration

The customer’s planning process using the IBM S/390 FICON Planning Guide,
SG24-5445, has identified which of the installed ESCON CHPIDs can be
aggregated, and which Parallel CHPIDs are no longer in use. The planning
process also identifies that some of the channels freed up during this ESCON to
FICON aggregation can then be used, along with the six new FICON CHPIDs to
support the new I/O requirement to the two new IBM 2105 Enterprise Storage
Subsystems.
These decisions are documented in a design document, extracts of which are

shown in the next paragraph:
ESCON to FICON Aggregation

ESCON CHPID F8, FC, E4, E6, 48, 6A, 08 and 31 channel to control unit path
definitions and workloads can be aggregated to one FICON channel.
ESCON CHPID F9, FD, F1, E1, E5, E7, 49 and 6B channel to control unit path
definitions and workloads can be aggregated to another FICON channel.
ESCON CHPID FF, FB, F3, E3, AB, 9F, 81 and 4B channel to control unit path
definitions and workloads can be aggregated to another FICON CHPID.

ESCON CHPID F0, E0, C0, 68, 64, and 82 channel to control unit path
definitions and workloads can be aggregated to another FICON CHPID.
ESCON CHPID C1, 69, 56, 83, one path to IBM 2105 #1, and one path to IBM
2105 #2, definitions and workloads can be aggregated to another FICON
CHPID.
ESCON CHPID 30, 09, one path to IBM 2105 #1, and one path to IBM 2105
#2, definitions and workloads can be aggregated to another FICON CHPID.
The last three FICON channels are not fully utilized; they will provide additional
I/O connectivity in the future, possibly through further ESCON aggregation or
additional new control unit channel path connections.
The design document also identifies that the six FICON Bridge Adapters that are
required to support the six FICON channels working in FCV mode will be installed
evenly across the two IBM 9032 Model 5 ESCON Directors.
All this information is used in the FICON Planning Worksheets introduced in

Chapter 6, “FICON Implementation Worksheets” on page 31.
The other essential information required to start implementation planning is the

CHPID Placement Report.
5.2 CHPID Placement Report

The CHPID Placement Report is an important input document to the
implementation process and to the Configuration Definition - Configuration
Worksheet, described later in this chapter. The CHPID placement Report is
generated by IBM during the hardware configuration process of placing a new
order or an upgrade to an existing system.
The CHPID Placement Report is divided into three sections. All three sections
provide important information.
The first section of the CHPID Placement Report, an example of which is shown
in Figure 12 on page 22, provides a schematic of the I/O cages of the IBM 9672
CMOS Processor, and a statement as to whether the MES (upgrade) is
hot-pluggable (non-disruptive).
The second part of the CHPID Placement Report, an example of which is shown
in Figure 13 on page 23, provides the information about the allocation of CHPID
numbers to the different channel types.
The third part of the CHPID Placement Report, an example of which is shown in
Figure 14 on page 25, provides a set of sequences for each FICON installation. A
sequence includes all the physical actions that are required to be taken to install
that one FICON channel card.
The CHPID Placement Report used here, as an example, is taken from an order
for six FICON Channels to be added to an already fully configured IBM 9672
Processor. The aim is to highlight a complex case scenario; in many instances,
customers may not see DELETED or MOVED CHPIDs on their processor’s report
when upgrading to FICON channels.
Chapter 5. Planning of a complex FICON configuration 21

5.2.1 CHPID Placement Report example
9672-RX6 000000001 PLACEMENT REPORT September 24, 1999

CCN 26746774
FRAME A 0 FRAME Z 0
EIA+-----------------------------------+ +-----------------------------------+
35 | | | |
34 | | | |
33 | | | |
32 |-----------------------------------| |-----------------------------------|
31 | 0058 | | 2020 |
30 | | | |
29 | SLOTS 01-17 | | SLOTS 01-17 |
28 ||D|D|D*||0|0|M *|0 * * * *|C|M *|O|| ||D|D *|0|2|2|2|2|0|2|5|2|2|5|2|0|2||
27 ||C|C|C*||0|0|E *|9 * * * *|P|E *|S|| ||C|C *|0|3|3|3|3|0|3|2|3|3|2|3|0|3||
26 ||A|A|A*||1|1|M *|1 * * * *|1|M *|C|| ||A|A *|1|3|1|1|1|1|1|0|3|3|0|1|1|1||
25 ||0|1|2*||2|2| *|4 * * * *|4| *| || || | *|8|9|4|4|3|8|3|2|9|9|8|3|8|3||
24 |-----------------------------------| |-----------------------------------|
23 |6|U|0|0|0|C|* M| |* M|0|0| |U|2|2|2|2|0|2|2|2|2|2|0|0|2|2|2|2|2|
22 |1|P|0|0|0|A|* E| STI |* E|0|0| |P|3|3|3|3|0|3|3|3|3|3|0|0|3|3|3|3|3|
21 |5|C|1|1|1|P|* M| INTERFACE |* M|1|1| |C|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|
20 |2| |2|2|2| |* | |* |2|2| | |4|4|4|4|8|3|3|3|3|3|8|8|3|3|3|3|3|
19 | SLOTS 35-18 | | SLOTS 35-18 |
18 |-----------------------------------| |-----------------------------------|
17 | | | |
16 | | | |
15 |-----------------------------------| |-----------------------------------|
14 | 2020 | | 2020 |
13 | | | |
12 | SLOTS 01-17 | | SLOTS 01-17 |
11 ||D|D *|0|2|0|2|2|0|2|5|2|2|5|2|0|2|| ||D|D *|0|2|0|2|2|0|2|5|2|2|5|2|0|2||
10 ||C|C *|0|3|2|3|3|0|3|2|3|3|2|3|0|3|| ||C|C *|0|3|2|3|3|0|3|2|3|3|2|3|0|3||
09 ||A|A *|1|3|1|1|1|1|1|0|3|3|0|1|1|1|| ||A|A *|1|3|1|1|1|1|1|0|3|3|0|1|1|1||
08 || | *|8|9|6|3|3|8|3|2|9|9|1|3|8|3|| || | *|8|9|6|3|3|8|3|1|9|9|8|3|8|3||
07 |-----------------------------------| |-----------------------------------|
06 |U|2|2|2|2|0|2|2|2|2|2|0|0|2|2|2|2|2| |U|2|2|2|2|0|2|2|2|2|2|0|0|2|2|2|2|2|
05 |P|3|3|3|3|0|3|3|3|3|3|0|0|3|3|3|3|3| |P|3|3|3|3|0|3|3|3|3|3|0|0|3|3|3|3|3|
04 |C|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|0|1| |C|1|1|1|1|1|1|1|1|0|1|1|1|1|1|1|1|1|
03 | |3|3|3|3|8|3|3|3|3|3|8|8|3|3|3|4|3| | |3|3|3|3|8|3|3|3|4|3|8|8|3|3|3|3|3|
02 | SLOTS 35-18 | | SLOTS 35-18 |
01 +-----------------------------------+ +-----------------------------------+
This MES is hot-pluggable (non-disruptive).
Figure 12. Example of a CHPID Placement Report
Most installations will be non disruptive; however, in certain circumstances

including where an Coupling Link card is moved within the processor, the
installation of FICON channels will be disruptive. In this case the CHPID
Placement Report will state that the MES is disruptive, and will also provide the
reason why this is the case.
The legend for the report is provided at the very end of report; however, to aid
understanding of Figure 12, note the following:
C3 - COUPLING LINK - #0216->#0008
E - ESCON (LED) - #2313
P4 - PARALLEL 4 PORT - #2304
2E - OSA2 EN/TR - #5201
2F - OSA2 FDDI - #5202
28 - OSA2 FAST EN - #5208
H1 - FICON Channels - #2314
We can see FICON channels, #2314, are to be installed in the I/O cage at the top
of the Z frame in I/O slots 31, 32, 33, 6, 7, and 34.

The second part of the CHPID Placement Report is shown in Figure 13.
******** NOTICE ****** NOTICE ****** NOTICE ****** NOTICE ****** NOTICE *******
* *
* The CHPIDs for some of the features have changed. *
* *
******** NOTICE ****** NOTICE ****** NOTICE ****** NOTICE ****** NOTICE *******
9672-RX6 000000001 CHPID REPORT September 24, 1999

CCN 26746774
STI - CHA SLOT - CAGE LOCATION - I/O SLOT - CHPID/TYPE
0 - 24 - FRAME Z BOTTOM - 11 - 00/2E
0 - 24 - FRAME Z BOTTOM - 26 - 14/P4 15/P4 16/P4 17/P4
1 - 23 - FRAME Z BOTTOM - 14 - 34/28
2 - 24 - FRAME Z TOP - 11 - 40/2F
2 - 24 - FRAME Z TOP - 10 - 44/E 45/E 46/E 47/E
2 - 9 - FRAME Z TOP - 29 - 48/E 49/E 4A/E 4B/E
2 - 9 - FRAME Z TOP - 28 - 4C/E 4D/E 4E/E 4F/E
2 - 9 - FRAME Z TOP - 27 - 50/E 51/E 52/E 53/E
2 - 24 - FRAME Z TOP - 26 - 54/E 55/E 56/E 57/E
3 - 23 - FRAME Z TOP - 22 - 60/E 61/E 62/E 63/E
3 - 23 - FRAME Z TOP - 21 - 64/E 65/E 66/E 67/E
3 - 23 - FRAME Z TOP - 15 - 70/E 71/E 72/E 73/E
3 - 23 - FRAME Z TOP - 14 - 74/28
4 - 24 - FRAME A BOTTOM - 11 - 80/2F
5 - 16 - FRAME A BOTTOM - 18 - A8/E A9/E AA/E AB/E
5 - 16 - FRAME A BOTTOM - 17 - AC/E AD/E AE/E AF/E
5 - 23 - FRAME A BOTTOM - 15 - B0/E B1/E B2/E B3/E
5 - 23 - FRAME A BOTTOM - 14 - B4/2E
5 - 16 - FRAME A BOTTOM - 20 - B8/E B9/E BA/E BB/E
5 - 16 - FRAME A BOTTOM - 19 - BC/P4 BD/P4 BE/P4 BF/P4
6 - 30 - FRAME Z BOTTOM - 7 - C0/E C1/E C2/E C3/E
6 - - FRAME Z BOTTOM - 6 - C4/C3 C5/C3
6 - 4 - FRAME Z BOTTOM - 34 - C8/E C9/E CA/E CB/E
6 - 4 - FRAME Z BOTTOM - 33 - CC/E CD/E CE/E CF/E
6 - 4 - FRAME Z BOTTOM - 31 - D4/E D5/E D6/E D7/E CARD MOVED, CHPID CHANGE
7 - 30 - FRAME A BOTTOM - 7 - D8/E D9/E DA/E DB/E
7 - - FRAME A BOTTOM - 6 - DC/C3 DD/C3
7 - 4 - FRAME A BOTTOM - 34 - E0/E E1/E E2/E E3/E
7 - 4 - FRAME A BOTTOM - 33 - E4/E E5/E E6/E E7/E
7 - 4 - FRAME A BOTTOM - 32 - E8/E E9/E EA/E EB/E
7 - 4 - FRAME A BOTTOM - 31 - EC/E ED/E EE/E EF/E CARD MOVED, CHPID CHANGE
9 - - FRAME Z TOP - 31 - FC/H1 NEW
9 - - FRAME Z TOP - 32 - FD/H1 NEW
9 - - FRAME Z TOP - 33 - FE/H1 NEW
10 - - FRAME Z TOP - 6 - F8/H1 NEW
10 - - FRAME Z TOP - 7 - F9/H1 NEW
10 - - FRAME Z TOP - 34 - FA/H1 NEW
ALL CHPIDS IN THE RANGE F8-FB WILL CHANGE TO RANGE EC-EF.

ALL CHPIDS IN THE RANGE FC-FF WILL CHANGE TO RANGE D4-D7.
Figure 13. CHPID report for FICON

There are a number of other key areas to note on this report:
• Note the CHPID numbers of the new FICON channels. The CHPID Report
identifies new channels added to the processor configuration with the word
NEW in the right-most column of the report. The CHPID numbers are assigned
by the order process and cannot be predetermined by the customer or
changed after the order is placed. FICON channels are identified in the report
as type H1. Looking at Figure 13 on page 23, the FICON channels have been
given the CHPID address ranges FC to FE and F8 to FA, and are highlighted
as NEW.
• The report highlights the CHPID addresses of those channels that need to be
relocated with the words CARD MOVED, CHPID CHANGE in the right-most
column of the report; see Figure 13 on page 23.
• A short summary is provided at the bottom of the report for all CHPIDs in a
particular range that will move to a different CHPID range.
The third and last part of the CHPID Placement Report is shown in Figure 14.

9672-RX6 000000001 CHPID REPORT September 24, 1999
FICON OSA-EXPRESS INSTALLATION DELETE CARDS, CHPID CHANGES/CARD MOVES, & NEW CARDS
- STI - CHA SLOT - CAGE LOCATION - I/O SLOT - CHPID/TYPE -ACTION - FEATURE
Sequence 001
FROM - 8 - 4 - FRAME Z TOP - 31 - /AF -DELETE - 0012
FROM - 6 - 4 - FRAME Z BOTTOM - 31 - D4/P4 D5/P4 D6/P4 D7/P4 -DELETE - 2304
FROM - 8 - 4 - FRAME Z TOP - 33 - FC/E FD/E FE/E FF/E -MOVES ’TO’ - 2313
TO - 6 - 4 - FRAME Z BOTTOM - 31 - D4/E D5/E D6/E D7/E -CARD MOVE, CHPID CHANGE
TO - 9 - - FRAME Z TOP - 31 - FC/H1 -NEW -2314
--------------------------------------------------------------------------------
Sequence 002
FROM - 8 - 30 - FRAME Z TOP - 6 - F4/E F5/E F6/E F7/E -DELETE - 2313
FROM - 7 - 4 - FRAME A BOTTOM - 31 - EC/P4 ED/P4 EE/P4 EF/P4 -DELETE - 2304
FROM - 8 - 4 - FRAME Z TOP - 34 - F8/E F9/E FA/E FB/E -MOVES ’TO’ - 2313
TO - 7 - 4 - FRAME A BOTTOM - 31 - EC/E ED/E EE/E EF/E -CARD MOVE, CHPID CHANGE
TO - 10 - - FRAME Z TOP - 6 - F8/H1 -NEW -2314
--------------------------------------------------------------------------------
Sequence 003
FROM - 8 - 4 - FRAME Z TOP - 32 - /AF -DELETE - 0012
TO - 9 - - FRAME Z TOP - 32 - FD/H1 -NEW -2314
--------------------------------------------------------------------------------
Sequence 004
FROM - 8 - 30 - FRAME Z TOP - 7 - F0/E F1/E F2/E F3/E -DELETE - 2313
TO - 10 - - FRAME Z TOP - 7 - F9/H1 -NEW -2314
--------------------------------------------------------------------------------
Sequence 005
TO - 9 - - FRAME Z TOP - 33 - FE/H1 -NEW -2314
--------------------------------------------------------------------------------
Sequence 006
TO - 10 - - FRAME Z TOP - 34 - FA/H1 -NEW -2314
--------------------------------------------------------------------------------
LEGEND FOR TYPE VALUES IN CHPID/TYPE COLUMN:

C3 - COUPLING LINK - #0216->#0008
E - ESCON (LED) - #2313
P4 - PARALLEL 4 PORT - #2304
2E - OSA2 EN/TR - #5201
2F - OSA2 FDDI - #5202
28 - OSA2 FAST EN - #5208
H1 - FICON Channels - #2314
The above CHPID assignments are based upon the recommended

channel plugging rules from S/390 division. The plugging
rules have taken into account availability and performance
considerations. It is strongly recommended that you adhere
to these plugging rules. Any changes will invalidate this
information.
Figure 14. Example of CHPID Report - CHPID changes/card moves and I/O deleted
This last section of the CHPID Placement Report highlights the sequences in
which the FICON cards must be installed.
The example in Figure 14 on page 25 has the following for Sequence 001:
Sequence 001 -ACTION

FROM - 8 - 4 - FRAME Z TOP - 31 - /AF -DELETE
FROM - 6 - 4 - FRAME Z BOTTOM - 31 - D4/P4 D5/P4 D6/P4 D7/P4 -DELETE
FROM - 8 - 4 - FRAME Z TOP - 33 - FC/E FD/E FE/E FF/E -MOVES ’TO’
TO - 6 - 4 - FRAME Z BOTTOM - 31 - D4/E D5/E D6/E D7/E -CARD MOVE, CHPID CHANGE
TO - 9 - - FRAME Z TOP - 31 - FC/H1 -NEW
Sequence 001 has the following steps:

1. DELETE , Card Type /AF from Z TOP 31. This is removal of an air flow card
from the processor, which makes available the I/O slot into which the first
FICON channel card will be installed into.

2. DELETE , CHPID type P4 from Z BOTTOM 31. This is the removal of one
parallel channel card (four CHPIDs) from the processor. This step is required
so that an ESCON card can be moved into the I/O slot that the parallel card
was occupying. The decision to remove parallel channels from the machine
was done during the configuration design, and was necessary because the
processor was channel-constrained (all 64 normal I/O slots were full) and I/O
slot space and CHPID numbers are required to support the installation of the
FICON channels.
3. MOVES ’TO’ , moves ESCON channel card type E from Z TOP 33. This is the
temporary removal of one ESCON channel card from the machine. This step
is required so that the CHPID address for the first FICON channel is made
available.
4. CARD MOVE,CHPID CHANGE, moves CHPID type E to Z BOTTOM 31. This
is the installation of the ESCON channel card removed in step 3; these
ESCON channels have changed their CHPID addresses in the process of
moving between I/O slots in the processor.
5. NEW, CHPID type H1 to Z TOP 31F. This is the installation of the (1st) FICON
channel card. This FICON channel will have a CHPID address of FC.
The example in Figure 14 on page 25 has the following for installation Sequence
002:
Sequence 002 -ACTION

FROM - 8 - 30 - FRAME Z TOP - 6 - F4/E F5/E F6/E F7/E -DELETE
FROM - 7 - 4 - FRAME A BOTTOM - 31 - EC/P4 ED/P4 EE/P4 EF/P4 -DELETE
FROM - 8 - 4 - FRAME Z TOP - 34 - F8/E F9/E FA/E FB/E -MOVES ’TO’
TO - 7 - 4 - FRAME A BOTTOM - 31 - EC/E ED/E EE/E EF/E -CARD MOVE, CHPID CHANGE
TO - 10 - - FRAME Z TOP - 6 - F8/H1 -NEW
Sequence 002 has the following steps:

1. DELETE , ESCON channel card type E from Z TOP 6. This is a removal of an
ESCON channel card from the processor, making available the I/O slot that
the second FICON channel card will go in. The decision to remove ESCON
channels from the processor was done during the configuration design, and
was necessary because the processor was channel-constrained. (all 64
normal I/O slots were full) and I/O slot space and CHPID numbers are
required to support the installation of the FICON channels.
2. DELETE , parallel channel card type P4 from A BOTTOM 31. This is the
removal of the second parallel channel card (4 CHPIDs) from the processor.
This step is required to be done so that an ESCON card can be moved into the
I/O slot that the parallel card was occupying. The decision to remove parallel
channels from the machine was done during the configuration design, and
was necessary because the processor was channel-constrained.
3. MOVES ’TO’ , moves ESCON channel card type E from Z TOP 34. This is the
temporary removal of one ESCON channel card from the machine. This step
is required so that the CHPID address for the second FICON channel is made
available.
4. CARD MOVE,CHPID CHANGE, moves ESCON channel card to A BOTTOM
31. This is the installation of the ESCON channel card removed in step 3; the

ESCON channels have changed their CHPID addresses in the process of
moving between I/O slots in the processor.
5. NEW, installs FICON channel card type H1 to Z TOP 6. This is the installation
of the second FICON channel card. This CHPID has address F8.
The other sequences outlined in the CHPID Placement Report are less complex.
Sequence order must be maintained to enable concurrent installation of the six
FICON channel cards to work.
As a result of installing the six FICON channel cards, two parallel channel cards
and two ESCON channel cards have been removed from the processor.
5.3 9032 Model 5 Placement Report

The IBM order process for a new IBM ESCON Director model 5, or an upgrade to
an existing Director, produces a 9032 Model 005 Placement Report.
Figure 15 on page 28 shows part of a 9032-005 Placement Report (quadrants 1

and 2 are not shown).
This example shows a nearly full ESCON Director configuration that had spare
slots available in quadrants 3 and 4. The customer order for six FICON Bridge
adapters resulted in these adapters occupying the next available slots in the
Director.
The default port plugging for a new 9032 Model 5 ESCON Director is to install
ports in order in quadrants 1, 2, 3, then 4. All ESCON ports are plugged first,
followed by ESCON XDF and then finally the FICON Bridge cards.

9032 Model 005 Placement Report September 20, 1999
Model 005 Default Plugging Configuration
136 ESCON ports - 16 XDF ports - 6 FICON ports - Spare port card (2 ESCON/2 XDF)
QUADRANT 4 QUADRANT 3
+---------------------------------------------------------------------------------+
| SP2| | | | | | | FCV| | FCV| FCV| FCV| FCV| FCV| XDF| XDF| ESC|
+---------------------------------------------------------------------------------+
| F8 | | | | | | | C0 | | B8 | B0 | A8 | A0 | 98 | 90 | 88 | 80 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | C4 | | BC | B4 | AC | A4 | 9C | 94 | 8C | 84 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| F9 | | | | | | | | | | | | | | 91 | 89 | 81 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 95 | 8D | 85 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| FA | | | | | | | | | | | | | | 92 | 8A | 82 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 96 | 8E | 86 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| FB | | | | | | | | | | | | | | 93 | 8B | 83 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 97 | 8F | 87 |
|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | | 94 | 8C | 84 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 98 | 90 | 88 |
| |----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | | 95 | 8D | 85 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 99 | 91 | 89 |
| |----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | | 96 | 8E | 86 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 9A | 92 | 8A |
| |----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|
| | | | | | | | | | | | | | | 97 | 8F | 87 |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | 9B | 93 | 8B |
+---------------------------------------------------------------------------------|
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
+---------------------------------------------------------------------------------+
----------- ------
| 4 | 3 | | 17 | - PHYSICAL PORT NUMBER
+----+----+ | |
| 2 | 1 | | 1B | - LOGICAL PORT ADDRESS
----------- ------
(FRONT VIEW)
Quadrant Locations ESC = Multimode ESCON 8 Port Card
in Machine Frame XDF = LASER XDF 8 Port Card
FCV = FICON Bridge Card
SP1 = 4 Port ESCON Spare
SP2 = 2 Port ESCON / 2 Port XDF Spare
Figure 15. Example of a 9032-5 Placement Report
Although FICON Bridge adapters can be installed in any port slot of the Director,
the default placement is not the recommended configuration. The recommended
placement for FICON in a new ESCON Director is as shown in Figure 16 on page
29., The figure shows the placement for the first eight FICON bridge cards.

Plugging Considerations
FICON Bridge port cards
Quadrant S S S S
Quadrant
C C Bridge port cards can be installed in any slot
T
P
T
P
4 3 position except the spare port slot.
Port Port To provide the maximum availability, the bridge port
MXC/ MXC/
Addr. MXS MXS Addr. cards should be installed in the order of Quadrant A,
Card Card C, B, D.
FB - C4 set 1 set 2
C3 - 84
Shown are the recommended slot locations and installation
sequence for 8 FICON Bridge port cards, this allows for
0 1 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
high availability.
T T
Quadrant A - FICON Bridge port address 0C
K K
R
G
R
G Quadrant C - FICON Bridge port address 84
Quadrant Quadrant Quadrant B - FICON Bridge port address 4C
0 1 2 1 Quadrant D - FICON Bridge port address C4
Port Port Quadrant A - FICON Bridge port address 2C
Addr. Addr. Quadrant C - FICON Bridge port address A4
0 0 1 1 2 3
Quadrant B - FICON Bridge port address 6C
83 - 44 43 - 04
Quadrant D - FICON Bridge port address E4
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Figure 16. Recommended plugging for ESCON Director model 5
The FICON planning and design process should have already identified the most
appropriate slots for the FICON Bridge cards.
For example, a configuration that has prompted an order for a new IBM ESCON
Director model 5 should ignore the default port placement. Instructions should be
provided to the IBM Customer Service representative to re-plug the ESCON
Director to the desired configuration.
An upgrade to an existing ESCON Director will also produce a 9032 Placement

Report that shows FICON installed in the next available slot of a quadrant that is
partially populated. Again, the FICON planning and design process should have
already documented the most appropriate slots for the FICON Bridge cards, so
this default placement report can be used to determine the current director port
slot status. Instructions should be provided to the IBM Customer Service
representative to install the new FICON Bridge cards in the recommended slots.
To aid the installation of new ESCON Directors, and upgrades to existing

Directors, we have produced an ESCON Director Impact Analysis Worksheet.
This worksheet is discussed in 6.2, “ESCON Director Impact Analysis Worksheet”
on page 32.

Chapter 6. FICON Implementation Worksheets
A number of implementation worksheets have been developed to aid the
configuration planning and implementation planning tasks of FICON installation.
It is recommended that implementations involving the movement, removal or

aggregation of CHPIDs, or ESCON Director ports use these worksheets to avoid
overlooking important steps in the implementation.
The installation of FICON channels and FICON Bridge cards for new control unit
connectivity, where existing channels, Director ports and control units are not
disrupted, could be treated as business as usual I/O configuration and planning
tasks without reference to these implementation worksheets.
The relationship between the various worksheets created in this implementation

process is shown in Figure 17.
Customer's CHPID Placement

& ESCD Placement Configuration
FICON Configuration
Design & Order
Design Reports
Configuration ESCON Director

Configuration
Definition - Impact Impact Analysis
Planning
* Worksheet * Worksheet
Phase Planning
* Worksheet
Processor/ESCD Implementation
Phase Perform Planning
* Worksheet
Phase Evaluation - * Worksheets

Resource Availability
Figure 17. FICON Implementation Worksheets - how they relate to each other
This chapter is confined to a discussion of the configuration planning tasks and

related worksheets
6.1 Configuration Definition - Impact Worksheet

The first step in using the 9672 processor Configuration Definition - Impact
Worksheet is to consolidate configuration information from both the Customer
FICON Configuration Design information and the IBM 9672 CHPID Placement
Report.

From this consolidated information the next step is to assign new CHPID
numbers for control unit channel paths for those channels (CHPIDs) that have
been removed from the machine as a result of installing the FICON channel
cards, and have not been aggregated, and whose channel functions are still
required.
See 6.4, “Completing the Configuration Definition - Impact Worksheet” on page

33, for details on how this worksheet is completed.
The completed Configuration Definition - Impact Worksheet can then be used in

the planning of each phase of the FICON implementation. A phase includes all
the physical installation activity and definition changes associated with the
implementation of each FICON channel (or in some cases phases may be
merged and would include more than one FICON channel). These phases are
introduced in the Phase Planning Worksheet described 6.3, “Phase Planning
Worksheet” on page 32.
6.2 ESCON Director Impact Analysis Worksheet

The ESCON Director Impact Analysis Worksheet consolidates information from
the Customer FICON Configuration Design information, and the physical
configuration of the ESCON Director model 5 - either from the 9032 Model 005
default (IBM) or customized Placement Report.
See 6.5, “Completing the ESCON Director Impact Analysis Worksheet” on page
36, for the details on how this worksheet is completed.
The completed ESCON Director Impact Analysis Worksheet can then be used to
plan for each phase of the FICON implementation. A phase includes all the
physical installation activity and definition changes associated with the
implementation of each FICON channel (including the ESCON Director Bridge
card it connects to). These phases are planned for in the Phase Planning
Worksheet described 6.3, “Phase Planning Worksheet” on page 32
6.3 Phase Planning Worksheet

The Phase Planning Worksheet provides a structured approach to compiling a list
of definition activities associated with the implementation of each FICON channel
card.
The implementation of each FICON channel card is initially regarded as a

separate phase, with a separate set of physical resources that are added, moved
or deleted.
See 6.6, “Completing the Phase Planning Worksheet” on page 38, for details on
how this worksheet is completed.
The Phase Planning Worksheet also provides a summary, for each phase, of the
CHPIDs requiring definition changes within HCM/HCD. See columns H-L in
Figure 20 on page 40.
During the actual implementation (install), multiple phases could be combined;

however, phases cannot be taken out of sequence or skipped.

By making an early (preemptive), aggregation of a CHPID, that CHPID becomes
eligible to be RE-ASSIGNED to. This will avoid DEFERRED RE-ASSIGNMENTS
in a phase, thereby removing interdependencies of phases, resulting in a less
complex implementation.
6.4 Completing the Configuration Definition - Impact Worksheet

The process of completing the Configuration Definition - Impact Worksheet is
straightforward, (a copy in shown in Figure 18 on page 35):
1. From the Customer FICON Configuration Design information, note the
addresses of the ESCON CHPIDs to be aggregated into the FICON channels.
The ESCON CHPIDs to be aggregated were identified as part of the FICON
Design phase. The FICON design phase will also have identified which
ESCON CHPIDs would be aggregated to the same FICON CHPID and those
that would be kept separate (for bothpathing, performance and availability
considerations). Update the Configuration Definition - Impact Worksheet,
column E with this information. Clearly show which ESCON channels will be
aggregated to which FICON channels by referring to the FICON channels as
FCV1, FCV2, FCV3, etc.
The information in this column/row will also be required when using the Phase
Planning Worksheet.
2. From the Customer FICON Configuration Design information, note the CHPID
addresses that are no longer required, and in the case of ESCON CHPIDs
have not been the target of ESCON-to-FICON aggregation. Update the
Configuration Definition - Impact Worksheet, column C with this information for
each channel type effected (use the correct channel type row for each channel
type).
3. From the Customer FICON Configuration Design information, note the type
and quantity of channels required to support any new control unit requirement
to be implemented at the same time as FICON. Update the Configuration
Definition - Impact Worksheet, column D with this information for each channel
type effected (use the correct channel type row).
4. From the 9672 CHPID Report (an example copy is shown in Figure 14 on
page 25), note the CHPID addresses of the channels identified as "CARD
MOVE, CHPID CHANGE" and "DELETE". These are the non-FICON channels
(they including ESCON, parallel, OSA-2, OSA-E, ISC and ICB) that are
potentially impacted by the I/O slot requirements and the CHPID
addressability requirements of the new FICON channels (and in some cases
this can also be due to the requirements of new, OSA-Express, PCI Crypto
and ICB channels). Update the Configuration Definition - Impact Worksheet,
column B with this information for each channel type effected (use the correct
channel type row).
5. From the 9672 CHPID Report, note the CHPID addresses assigned to the new
FICON channels; these will be highlighted as "NEW" in the 9672 CHPID
Report. Update the Configuration Definition - Impact Worksheet, column F
with this information, (use the FICON channel type row).
6. From the 9672 CHPID Report, note the CHPID addresses assigned to the new
FICON channels; these will be highlighted as "NEW" in the 9672 CHPID
Report. Update the Configuration Definition - Impact Worksheet, column F
with this information, (use the FICON channel type row).
Chapter 6. FICON Implementation Worksheets 33

7. From the 9672 CHPID Report, note the CHPID addresses assigned to any
other the new channel (non-FICON); these will be highlighted as "NEW" in the
9672 CHPID Report. Update the Configuration Definition - Impact Worksheet,
column F with this information, (use the correct channel type row).
8. From the 9672 CHPID Report, note the CHPID addresses in the "TO" rows of
the CHPID CHANGES/CARD MOVES table. Update the Configuration
Definition - Impact Worksheet, column F with this information for each channel
type effected (use the correct channel type row).
The information required for each of the following steps are derived from the
information already placed on the Configuration Definition - Impact Worksheet up
to this point.
9. Use the list of ESCON CHPID addresses to be released by the aggregation of
ESCON channels paths into the FICON channels (this is shown in column E ).
Then exclude from this set of aggregated ESCON CHPID addresses those
CHPIDs identified as part of the "CARD MOVES, CHPID CHANGE" and
"DELETE" column of the Configuration Definition - Impact Worksheet. Update
the Configuration Definition - Impact Worksheet, column G with this
information, (use the ESCON channel type row).
10.Determine the customer-assigned "From and To" CHPID numbers and place
the result in column (H).
a. Using the ESCON channel type row
For each ESCON CHPID number from the set of displaced CHPIDs (B),
that the customer had not indicated was no longer required (C) and that
have not been subject to ESCON-to-FICON aggregation (E), allocate a
CHPID from the list of “ESCON-aggregated CHPID numbers not used by
and NEW or MOVED CHPID numbers” (G). The activity of an earlier
planning step should have ensured that there would be sufficient freed
ESCON CHPID addresses to accommodate all the displaced ESCON
CHPIDs. There are several important considerations to take into account
when re-assigning CHPID numbers, one is, ensuring device path
separation for availability reasons. Update the Configuration Definition -
Impact Worksheet, column H with this information, (use the ESCON
channel type row).
b. Using the each of the other channel type rows
For each of the other type CHPID numbers from the set of displaced
CHPIDs (B), that the customer had not indicated was no longer required
(C), allocate a CHPID from the list of “New and Moved CHPID numbers by
type” (F). The activity of an earlier planning step should have ensured that
there would be sufficient freed CHPID addresses (of this channel type) to
accommodate all the displaced CHPIDs of this type. There are several
important considerations to take into account when re-assigning CHPID
numbers, one is, ensuring device path separation for availability reasons.
Update the Configuration Definition - Impact Worksheet, column H with this
information, (use the correct channel type row).
The information in these column/rows will be required when using the Phase
Planning Worksheet.
11.The Configuration Definition - Impact Worksheet can now be used to identify
individual channel cables that have to be moved from one CHPID to another.
Each channel cable can be identified by number and documented from where

CHPID Placement Report Customer Design Worksheet CHPID Worksheet ESCON Worksheet output
Placement step
Report
A B C D E F G H I
Channel Type CARD MOVE CHPID New CUs Path ESCON to FICON NEW, and ESCON Aggregated Customer- System
and CHPID numbers no requirement Aggregation, by ESCON CARD MOVE CHPID number not assigned Cabling
CHANGE, longer by CHPID type CHPID number CHPID used by any NEW CHPID Require-
and DELETE required & not & quantity numbers by or MOVED CHPID numbers From ment
aggregated type number and To
information.
ESCON (E) E4 E5 E6 E7 NONE New CU #1 F8 FC E4 E6 48 6A 08 31 => 48 6A 08 31 FROM E2 TO 48

E0 E1 E2 E3 8 Paths F1 49 6B FROM C2 TO 6A
C0 C1 C2 C3 1 per FICON F9 FD F1 E1 E5 E7 49 6B => AB 9F 4B FROM C3 TO 08
80 81 82 83 F2 68 FROM 80 TO 31
64 65 66 67 New CU #2 FF FB F3 E3 AB 9F 81 4B => 69 FROM 66 TO 49
F0 F1 F2 F3 8 Paths F3 FROM 67 TO 6B
FC FD FE FF 1 per FICON F0 E0 C0 68 64 82 => F4 30 FROM F2 TO 68
F8 F9 FA FB C1 69 65 83 3 new paths => 09 FROM FE TO 69
New CU #3 F5 FROM FA TO 30
8 Paths 3 new paths => F6
3 new paths => F7
1 per FICON
30 09 3 new paths => F8
FICON F1 TO FC
3 new paths => F9
3 new paths => F10 FICON F2 TO F8
3 new paths => F11 FICON F3 TO FD
3 new paths => F12 FICON F4 TO F9
FICON F5 TO FE
FICON F6 TO FA
FICON F7 TO F4
FICON F8 TO F0
FICON F9 TO F5
FICON F10 TO
F1
FICON F11 TO
F6
FICON F12 TO
F2
FICON (H1) F0 F1 F2 F4
F5 F6 F8 F9
FA FC FD FE
Figure 18. Configuration Definition - Impact Worksheet

Parallel (P3/P4) EC ED EE EF C0 C1 C2 C3
E8 E9 EA EB
D8 D9 DA DB
Processor/ESCD Phase Perform Worksheet.
OSA-2 EN/TR DC 80
(2E)
OSA-2 FDDI
OSA-2 ATM
Multimode(2M)
OSA-2 ATM
Singlemode(2S)
OSA-EXPRESS
OSA2 FENET
Fast-Ethernet(28)
ISC 1Km (C1)
ISC-SM (C3) F4 F5 64 65
ICB (CB)
the Configuration Definition - Impact Worksheet, column I with this
The information in this column/row will be required when using the
IC Channel
customer-
assigned
CHPID number

A sample Configuration Definition - Impact Worksheet is provided in Figure 18.
it must be disconnected and to which channel is must be re-plugged. Update
35
6.5 Completing the ESCON Director Impact Analysis Worksheet
Use the customer’s design and the ESCON Director Placement Reports to
identify where the ESCON Director FICON Bridge adapter will be installed. There
are three scenarios for the physical installation:
A new ESCON Director Model 5 - no impact
A partially configured ESCON Director - possible impact, unlikely to affect
service availability
A fully configured ESCON Director - possible impact, complex planning
involved, may effect service availability
A recommended approach to minimize the disruption caused by the installation of

an ESCON Director Bridge Card is to plan according to the following the
guidelines:
• Place the ESCON Director Bridge Card in an empty slot on the ESCON
Director. There is no impact to other ports on the Director. Use the IBM
recommended placement guidelines where possible.
• If the ESCON Director is full, but there are eight or more free ports, then either
use the port move capability of HCM, or use HCD to move all free port
definitions onto a single ESCON port card, move the cables, then replace the
port card with an ESCON Director Bridge Card.
• If the ESCON Director Bridge Card must replace an existing ESCON port card
and there are insufficient free ports, then choose a card which provides ports
that will be aggregated by the same ESCON-to-FICON aggregation phase.
• If the ESCON Director Bridge Card must replace an existing ESCON port
card, then choose a card with ports connecting to devices that support multiple
paths; that is, a DASD control unit may have four or eight paths, and the loss
of a single path while implementing a phase of the FICON installation will not
be disruptive to a customers operations if scheduled at an appropriate time. In
contrast, the loss of a path to a single path control unit such as a printer or
3745/6 will undoubtedly cause disruption and thus should be avoided.
• If the ESCON Director Bridge Card must replace an existing ESCON port card
and this card is then required to be installed in another Director, or even if the
paths are moved to another Director, without the card be careful. Remember:
all the control unit ports associated with each CHPID port must be moved and
the similarly all CHPID ports associated with a Control Unit port must be
moved at the same time to maintain connectivity for that path.
This step can be complex and result in many ports being moved between
ESCON Directors, so there is a potential impact to service availability as a
large number of paths could be offline at a single point in the phased
introduction of the ESCON Director Bridge Card.
• ESCON Director configurations in place to support PPRC need to be handled
carefully. HCM and HCD do not know of the path between the primary and
secondary DASD control units. HCM does have the capability of showing a
physical cable or connection between DASD control units. ESCON Director
ports used for PPRC primary DASD control unit-to-secondary DASD control
unit connectivity should be excluded from the list of ports to be moved by HCM
in any phase of FICON installation.

• The worst case is that during the phased implementation of an ESCON
Director Bridge Card, eight paths to CHPIDs or control units will be lost per
Bridge card installed.
When deciding which ports to move or relocate on an IBM ESCON Director model
5, the standard availability requirements must be taken into consideration.
The following worked example shows how to analyze impacts of installing an

ESCON Director Bridge Card. A blank worksheet is available in Appendix A.
FICON BRIDGE INSTALLATION ESCON PORT AGGREGATION & RE-ASSIGNMENT

A B C D E F G H
FICON ESCON FICON Bridge Processor Port address ESCON ports Ports freed by Ports Ports
Channel Director Port Number CHPID range in use but ESCON - FICON relocated Re-assigned
Worksheet Identifier Number assigned to displaced by channel Old=>New to alternate
Phase FICON Bridge FICON Bridge aggregation Same ESCD ESCD
Phase 1 ESCD #1 B4 CPU #1234 B4 - BB None - -

(Empty slot) FC
Phase 2 ESCD #2 4C CPU #1234 4C - 53 4C 36 CE DA DB 4C => 36

F8 4D 4D => 46
4E 4E => 63
50 50 => A8
51 51 => A9
52 52 => C3
Phase 3 ESCD #1 C4 CPU #1234 C4 - CB None - -
(Empty slot) FD
Phase 4 ESCD #2 84 CPU #1234 84 - 8B 85 8B 85 => CE

F9 86 86 => DA
87 87 => DB
Phase 5 ESCD #1 BC CPU #1234 BC - C3 None - -

(Empty slot) FE
Phase 6 ESCD #2 E4 CPU #1234 E4 - EB E4 E4 => DE

FA E5 E5 => DF
E6 E6=>57 ESCD#1
BD=>9D ESCD#1
B5=>A5 ESCD#1
E7 E7=>77 ESCD#1
24=>AD ESCD#1
1C=>95 ESCD#1
0C=>AC ESCD#1
04=>94 ESCD#1
E9 E9=>8D ESCD#1
25=>AE ESCD#1
1D=>96 ESCD#1
0D=>AB ESCD#1
05=>97 ESCD#1
EA EA=>93 ESCD#1
33=>98 ESCD#1
42=>AF ESCD#1
Figure 19. ESCON Director Impact Analysis
Determine the address at which the first ESCON Director Bridge Card will be
installed.
1. Write in the worksheet (column A-D in Figure 19) all the changes that will
occur as a result of installing this first ESCON Director Bridge Card. This
entails entering the Phase number from the Phase Planning Worksheet,
ESCON Director identifier, FICON Bridge Port address, the Processor and
CHPID number and finally the Port Address range assigned to the ESCON
Director Bridge Card.

2. Write in the worksheet (column E in Figure 19) the port numbers (in the range
displaced by the ESCON Director Bridge Card) that are currently in use but
will be displaced as a result of installing the Bridge card.
3. Write in the worksheet (column F in Figure 19) the CHPID ports that are freed,
during this phase, by the ESCON - FICON aggregation onto the ESCON
Director Bridge Card.
4. Write in the worksheet (column G in Figure 19) those ESCON Director ports
that are not freed by the aggregation of an ESCON channel onto the FICON
channel and need to be relocated as a result of their addresses being stolen
by the installation of the ESCON Director Bridge Card. Assign a free port on
this Director to the port eliminated by the installation of the ESCON Director
Bridge Card.
5. Write in the worksheet (column H in Figure 19) those ESCON Director ports
that are to be reassigned to a port on an alternate ESCON Director. Assign the
port to a port number and identify which ESCON Director 4 on page 38.
Immediately following each reassignment, write in the worksheet all other
ports that may have to move to this new Director as a result of being logically
connected to the original port being moved (these ports will have been
identified in an earlier step). Assign these ports to unused ports on the new
Director.
Note that in identifying an alternate ESCON Director to reassign ports to, all the
normal availability considerations for pathing through Directors must be
considered.
Not part of this worksheet, but facilitated by its completion, is a list of cabling
requirements associated with each step.
Repeat this process for each ESCON Director Bridge Card to be installed.
6.6 Completing the Phase Planning Worksheet

The worksheet is designed to be filled in one phase (a number of rows) at a time,
taking care to complete each column as appropriate.
To complete the Phase Planning Worksheet:

1. Determine all the changes (ADDS, DELETES, MOVES) listed on the CHPID
Placement Report (CPR) that will occur as a result of installing just the first
FICON channel card.
2. Document these changes in Phase 1 of the Phase Planning Worksheet in the
ADD, DELETE/MOVE or the DELETE row by entering the physical channel
location in the processor (Card Location), the CHPID number, and CHPID
type. See columns B, C, D, E, F, and G in Figure 20 on page 40.
3. Write in the worksheet for this phase all the ESCON channels (CUs on
ESCON channel) that will be aggregated to this FICON channel. See column
H in Figure 20 on page 40. Remember, by making an early (preemptive),
aggregation of a CHPID, CHPID becomes eligible for RE-ASSIGNMENT. This
will avoid DEFERRED RE-ASSIGNMENTS in a phase, thereby removing
interdependencies of phases, resulting in a simplified implementation.

4. Write in the worksheet all the ESCON channels that will be deleted during this
phase that will be reassigned to another ESCON channel during this phase.
Enter it as work that needs to be done during this phase. See column I in
5. Write in the worksheet all the ESCON channels that will be deleted during this
phase that will be reassigned to another ESCON channel in another phase
(deferring CU-Path assignment). See column J in Figure 20 on page 40. Enter
the ESCON channels in the phase where the reassignment will be performed
(defining deferred CU-Path). See column L in Figure 20 on page 40.
6. Write in the worksheet all the other channels (including ESCON) that will be
deleted during this phase that will not be aggregated or reassigned during any
other phase. This means that the paths to the CUs that were defined to use
this CHPID are not longer required and will not be aggregated to a FICON
channel or reassigned to another channel of the same type. See column K in
7. Write in the beginning of the channel card action row if this change can be
performed concurrently with the customer’s operation or nonconcurrently. See
Column A in Figure 20 on page 40.
8. Write in the Bridge row on the Phase Planning Worksheet the identity of the
target ESCON Director, and the intended port number of the ESCON Director
Bridge Card that the FICON channel installed in this phase will connect to.
This information will help cross-reference the Phase Planning Worksheet for
the FICON channel with the ESCON Director planning worksheet.
9. Not shown on the chart but possibly a valuable task at this stage would be to
identify any cable moves associated with a phase. Cable management
procedures can be vary between customer sites, but the Phase Planning
Worksheet can help build a list of cables that are no longer required (for
aggregated or deleted CHPIDs), or cables that must be re-plugged for
CHPIDs re-assigned to another address.
Repeat this process for each FICON channel card to be installed in the IBM 9672
CMOS Processor.
If multiple processors will be upgraded with FICON, fill out a Phase Planning
Worksheet for each CPU, and write the CPU identifier on the worksheet. Make
sure that each FICON installed is planned for within a phase, and that the
installation sequence is maintained.
A concurrent install of an IBM FICON card requires that you install each FICON
card in the correct sequence (correct phase) and perform all the other actions
listed on the implementation worksheet for this phase. You must not change the
FICON installation plugging sequence (the phase).
Figure 20 on page 40 and Figure 21 on page 41 provide an examples of Phase

Planning Worksheets.
The examples show both an ISC (phase 2) and an OSA (phase 8) CHPID being
re-assigned within the processor, while ESCON and Parallel CHPIDs are
released from the machine through aggregation.

40
WORKSHEET FOR CHPID Card CHPID Card HCD / HCM DEFINITIONS
IBM 9672-RX6 #1234 DELETED/MOVED FROM DELETED/MOVED TO
A B C D E F G H I J K L
FICON Implementation Guide

N CARD CHPID CHPID CARD CHPID CHPID ESCON=>FICON CHPID REMOVING CHPID NOT DEFINING
C LOCATION NUMBER TYPE LOCATION NUMBER TYPE AGGREGATION REASSIGNMENT DEFERRED AGGREGATED DEFERRED
CU-PATH or CU->PATH
ASSIGNMENT REASSIGNED
Phase #1
DELETE Z TOP 33 FC-FF ESCON FC FD,FE,FF
DELETE/MOVE
DELETE
DELETE/MOVE
ADD Z TOP 31 FC FICON F8,E4,E6,48
6A,08,31
Bridge ESCD #1 Port
Phase #2
DELETE Z TOP 34 F8-FB ESCON F9 FA,FB
DELETE/MOVE
DELETE Z TOP 21 64-67 ESCON 66=>49,67=>6 64,65
B
DELETE/MOVE X Z TOP 6 F4-F5 ISC Z TOP 21 64-65 ISC F4=>64,F5=>6
5
ADD Z TOP 6 F8 FICON FD,F1,E1,E5 FD=>F8
E7,49,6B
Bridge ESCD #2 Port
Phase #3
DELETE
DELETE/MOVE
DELETE
Figure 20. Phase Planning Worksheet number 1

DELETE/MOVE
ADD Z TOP 32 FD FICON FF,FB,F3,E3, FF=>FD
AB,9F,81,4B FB=>FD
Bridge ESCD #3 Port
Phase #4
DELETE Z TOP 7 F0-F3 ESCON F0 F2=>68
DELETE/MOVE
DELETE
DELETE/MOVE
ADD Z TOP 7 F9 FICON E0,C0,68,64, 64=>F9
82
Bridge ESCD #1 Port
Phase #5
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD Z TOP 33 FE FICON C1,69,65,83, FE=>69
New CUs 65=>FE
Bridge ESCD #2 Port
Phase #6
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD Z TOP 34 FA FICON New CUs
Bridge ESCD #3 Port
CU-PATH or CU->PATH
Phase #7
DELETE
DELETE/MOVE
DELETE A BOT 31 EC-EF PARALLEL EC-EF
DELETE/MOVE
ADD A BOT 31 F4 FICON New CUs
Bridge ESCD #1 Port EC
Phase #8
DELETE
DELETE/MOVE
DELETE A BOT 11 80-83 ESCON 80=>31
DELETE/MOVE A BOT 6 DC OSA A BOT 11 80 OSA DC=>80
ADD A BOT 6 F0 FICON 30,09,New CUs 30=>F0
Bridge ESCD #2 Port
Phase #9
DELETE
DELETE/MOVE
DELETE A BOT 32 E8-EB PARALLEL E8-EB
DELETE/MOVE
ADD A BOT 32 F5 FICON New CUs
Bridge ECSD #1 Port
Figure 21. Phase Planning Worksheet number 2

Phase #10
DELETE
DELETE/MOVE
DELETE Z BOT 7 C0-C3 ESCON C2=>6A
C3=>08
DELETE/MOVE A BOT 7 D8-DB PARALLEL Z BOT 7 C0-C3 PARALLE D8=>C0,D9=>C1
L DA=>C2,DB=>C3
ADD A BOT 7 F1 FICON
Bridge ESCD #2 Port
Phase #11
DELETE
DELETE/MOVE
DELETE A BOT 33 E4-E7 ESCON
DELETE/MOVE
Bridge ESCD #1 Port
Phase #12
DELETE
DELETE/MOVE
DELETE A BOT 34 E0-E3 ESCON E2=>48
DELETE/MOVE
Bridge ESCD #2 Port

41
Part 3. Implementation planning
In this part of the book we look at how FICON will be implemented, using the
installation sequences provided by the IBM CHPID Placement Report.
A task list is produced for each sequence or phase.
The Implementation Planning part of this book is highlighted in Figure 22.



Design Resource and FICON install task
CHPID sequence,.
Topology Plan numbers Bridge then build
I/O Resources ahead CPR install Definitions Vary off
FICON
Characteristics Design sequence channel Vary off Hardware
or install phases Activate
Benefit Review Hardware
CPR phases Vary on
Addressing IBM FICON Activate
Customer
Fiber channel configuration Vary on
(IBM CPR)
Distance
CPR phases
Customer's
configuration

Redbook Redbook
Figure 22. Implementation planning

Chapter 7. Processor phase actions
This chapter describes how to use the Phase Planning Worksheet (see Figure 23
on page 46) to produce the Processor Phase Perform Worksheet (see Figure 24
on page 47). There will be one Phase Perform Worksheet for each phase.
How to use an ESCD Impact Analysis to build the ESCD Perform Worksheet for
each phase is covered in Chapter 8, “ESCON Director phase actions” on page
61.
The rows within the Phase Planning Worksheet are segmented into phases. That
is, the rows pertaining to a phase are grouped together and clearly delineated
from rows belonging to other phases. This will make it easier to work through the
Phase Planning Worksheet phase by phase. One Phase Perform Worksheet will
be produced for each phase in the Phase Planning Worksheet.
Each row generally represents a task within the phase, whether it be to delete or
move a CHPID in order to free either an I/O slot or CHPID number, required for
FICON installation, or the task of installing a FICON Bridge card in an ESCD.
Only the ESCD and port number to which the FICON channel is to be attached
are identified on the Phase Planning Worksheet.
Each row is to be worked through column by column, that is moving left to right.
By following the instructions for using the data in each column a list of actions will
be derived. These actions are added to the Phase Perform Worksheet. The end
result is an unsorted list of actions. Although some sorting may be required, there
is not a great deal to it and common sense is the best guide to use when sorting
the actions, if necessary.
7.1 Phase Perform Worksheet completion instructions

The Phase Perform Worksheet, when correctly completed, will contain all the
actions necessary to be performed within a phase. Each task in the phase (for
example, delete/move/add CHPID) will contain a number of steps in common -
the actions to be performed for each step, when added together for all tasks, will
perform the implemetantion of the phase.
Each phase in the Phase Planning Worksheet contains six rows with the titles:
1. DELETE
2. DELETE/MOVE
3. DELETE
4. DELETE/MOVE
5. ADD
6. Bridge
The Bridge row is used to identify the ESCD and port to which the FICON channel
will be attached (and therefore will require some cabling action). If a FICON
Bridge card is not already installed in the ESCD and port identified, then an
ESCD Phase Perform Worksheet will be completed for this phase (see 24 on
page 47). The actions related to the task of installing the FICON bridge card will
be treated as a separate phase for simplicity. This now separate phase will be a

46

C LOCATION NUMBER TYPE LOCATION NUMBER TYPE AGGREGATION RE-ASSIGNMENT DEFERRED AGGREGATED DEFERRED
CU-PATH or CU->PATH
ASSIGNMENT RE-ASSIGNED
Phase #1
DELETE/MOVE
DELETE
DELETE/MOVE
6A,08,31
Bridge ESCD #1 Port
Phase #2
DELETE Z TOP 34 F8-FB ESCON F9 FA,FB
DELETE/MOVE
DELETE Z TOP 21 64-67 ESCON 66=>49,67=>6B 64,65
Figure 23. Phase Planning Worksheet

E7,49,6B
Bridge ESCD #2 Port
Phase #3
DELETE
DELETE/MOVE
DELETE
one way a pre-phase may come about.
DELETE/MOVE
AB,9F,81,4B FB=>FD
Bridge ESCD #3 Port
Phase #4
DELETE/MOVE
DELETE
DELETE/MOVE
82
Bridge ESCD #1 Port
Phase #5
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
New CUs 65=>FE
Bridge ESCD #2 Port
Phase #6
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
Bridge ESCD #3 Port
preceding phase or what will be referred to as a pre-phase . This is an example of
P ro c e s s o r/E S C D P h a s e P e r fo r m W o rk s h e e t
P hase # ________ N o n C o n c u rr e n t In s ta ll (Y e s /N o ) ______
D e fin it io n s V a rie s O ff H a rd w a re A c t io n s V a r ie s o n
Figure 24. Phase Perform Worksheet
The following sections give detailed instructions on completing the areas of the
Phase Perform Worksheet for the tasks related to FICON installation at the
processor by working through the Phase Planning Worksheet row by row and
column by column within the rows.
If an X appears in Column A for any of the rows in a phase, the phase will be
nonconcurrent and therefore disruptive, so a Yes must be placed in the
underscored area next to (Yes/No) on the same line as the phase number.
7.1.1 Phase # Row

Using the phase number from this row, place it at the top of the Phase Perform
Worksheet in the underscored area next to Phase #.
7.1.2 Delete Row

This row indicates a CHPID or number of CHPIDs are to be deleted. Deleting a
CHPID or range of CHPIDs will free CHPID numbers, or an I/O slot, or both,
where required for the installation of a FICON channel.
7.1.2.1 Column A
An X in column A indicates that the hardware action of deleting the channel card
will be disruptive.
1. If there is an X in the column A, write Yes at Non Concurrent Install.
2. If there are no X s in column A for all rows within the phase, write No.
7.1.2.2 Column B
This is the I/O slot to be freed. The external cable(s) and the card there will be
removed.
1. In the Hardware Actions column of the Phase Perform Worksheet:
• Write REMOVE CARD+CABLE @ <B>
Ex.: REMOVE CARD+CABLE @ ZT33
Chapter 7. Processor phase actions 47

7.1.2.3 Columns C and D
The CHPID number(s) in column C and their associated CHPID type in column D
of Phase Planning Worksheet will be removed.
For each CHPID in column C:

1. In the Definitions column of the Phase Perform Worksheet:
• Write DELETE CHPID (<C>)
Ex.: DELETE CHPID(FC-FF)
Note: Note any attached CUs for later reassignment to another CHPID, and
if any aggregations are to be done in the phase, do them first if possible.
2. In the Varies off column of the Perform Worksheet:
• Write CF CHP(<C>),OFF
Ex.: CF CHP(FC-FF),OFF
Note: These commands are to be performed on all LPARs if the CHPID is
shared. After varying off check on HMC’s channel display that all CHPIDs
are in “configure off” status.
7.1.2.4 Columns E to G
These columns are not used in a DELETE row.
7.1.2.5 Column H
The CUs for the CHPID(s) in this column will be reassigned to the FICON CHPID
in the same phase (column F of the ADD row). That is, the CHPID(s) in column H
in the DELETE row will be aggregated to the CHPID in column F of the ADD row
in this phase.
• Write AGGR CHPID(<H>) -> CHPID(<F>)
Note: Place before the DELETE CHPID(<H>).
Ex. 1: AGGR CHPID(FC)->CHPID(FC) (In this case the CHPID numbers
are the same but the type changes from CNC to FCV.)
Ex. 2: AGGR CHPID(F9)->CHPID(F8)
7.1.2.6 Column I
Old and new CHPID pairs will be found in this column. The CUs attached to the
old CHPID are to be aggregated to the new CHPID.
1. In the Definitions column in the Perform Worksheet:
• Write AGGR CHPID(<I1>)->CHPID(<I2>)
Ex. 1: AGGR CHPID(66)->CHPID(49)
Ex. 2: AGGR CHPID(67)->CHPID(6B)
2. In the Hardware Actions column of the Phase Perform Worksheet for each
CHPID pair:
• Write MOVE CABLE CHPID(<I1>)->CHPID(<I2>)
Ex. 1: MOVE CABLE CHPID(66)->CHPID(49)
Ex. 2: MOVE CABLE CHPID(67)->CHPID(6B)

3. In the Varies Off column of the Phase Perform Worksheet, for each "new"
CHPID:
• Write CF CHP(<I1>),OFF
Ex.: CF CHP(49,6B),OFF
Note: No need to configure off the old CHPID (that is, I1), already handled
in column C.
4. In the Varies On column of the Phase Perform Worksheet, for each "new"
CHPID:
• Write CF CHP(<I2>),ON
Ex.: CF CHP(49,6B),ON
7.1.2.7 Column J
Of the CHPID numbers deleted in column C, those that will not be reassigned or
aggregated in this phase are noted here. The reassignment of their conected I/O
subsystems will be deferred to later phases. The information about the attached
CUs needs to be saved, so that they can be reassigned later. Once the CHPID is
deleted in HCM or HCD, the information will be lost.
By scanning column L for subsequent ADD rows, the eventual target CHPID may
be found but the reassignment cannot be done at this point.
• Write SAVE CUs:CHPID(<J>)
Note: Place before DELETE CHPID(<J>).
Ex.: SAVE CUs:CHPID(FD,FE,FF)
7.1.2.8 Column K
This field is really only of value for accounting or bookkeeping. Of the CHPID
numbers deleted in column C, those that will not be reassigned or aggregated are
noted here. That is, the CHPID is decommissioned.
7.1.2.9 Column L
This column will not be used in a DELETE row.
7.1.3 Delete/Move Row

7.1.3.1 Column A
will be disruptive.
1. If there is an X in column A, write Yes at Non Concurrent Install.
7.1.3.2 Column B
This is the I/O slot to be freed. The external cable(s) and the card there will be
removed.
• Write REMOVE CARD+CABLE @ <B>
Ex.: REMOVE CARD+CABLE @ ZT06

7.1.3.3 Column C
The CHPID number(s) in column C and their associated CHPID type in column D
of Phase Planning Worksheet will be removed.
For each CHPID in column C:

• Write DELETE CHPID (<C>)
Ex.: DELETE CHPID(F4-F5)
Note: Note any attached CUs for later reassignment to another CHPID, and
if any aggregations are to be done in the phase, do them first if possible.
2. In the Varies Off column of the Perform Worksheet:
• Write CF CHP(<C>),OFF
Ex.: CF CHP(F4-F5),OFF
shared. After varying off, check on HMC’s channel display that all CHPIDs
7.1.3.4 Column D
If the CHPID type is OSA, then additional actions must be performed when an
OSA channel is moved, both in definition and operation. The OSA configuration
file must be changed or copied for the new CHPID number to be used (see
column F in the Phase Planning Worksheet) and then an ACTIVATE NOINSTALL
must be done for the OSA channel from the OSA manager screen.
1. In the Definitions column on the Phase Perform Worksheet:
• Write CHANGE OSA CONFIG: CHPID(<C>)->CHPID(<F>)
Ex.: CHANGE OSA CONFIG: CHPID(30)->CHPID(40)
7.1.3.5 Column E
This is the I/O slot into which the moving CHPID’s card and external cable will be
installed.
• Write INSTALL CARD+CABLE @ <E> (optional: CHPID(<F>)
Ex. 1: INSTALL CARD+CABLE @ ZT21
Ex. 2: INSTALL CARD+CABLE @ ZT21 CHPID(64,65)
7.1.3.6 Column F
This will contain the new CHPID number(s) to which the old CHPID number(s) will
be moved. The new CHPID number(s) will need to be defined and cabled; in
effect, this is like an ADD. The channel type is to be found in column F.
For each CHPID in column F:

• Write ADD CHPID(<F>) TYPE=<G>
Ex.: ADD CHPID(64,65) TYPE=ISC
2. In the Varies On column of the Phase Perform Worksheet:

• Write CF CHPID(<F>),ON
Ex.: CF CHPID(64,65),ON
shared. After varying off, check on HMC’s channel display that all CHPIDs
7.1.3.7 Column G
As already mentioned, this is the new CHPID type. It should be appropriate for
the old CHPID type found in column D (for example, move OSA to OSA and ISC
to ISC). However, an ESCON (CNC) can move to a FICON (FCV & FC). For OSA
channels, additional actions are required to activate them from the OSA
configuration manager console (???).
1. If TYPE=OSA, then in the Varies On column of the Phase Perform Worksheet:
• Write ACTIVATE NOINSTALL after the CF CHPID(<F>),ON for the OSA
7.1.3.8 Column H
This column won’t be used for a DELETE/MOVE because ESCON-to-FICON
aggregation is handled on either an ADD or DELETE row.
7.1.3.9 Column I
Old and new CHPID pairs will be found in this column. The CUs attached to the
old CHPID are to be aggregated to the new CHPID.
1. In the Definitions column in the Perform Worksheet:
• Write AGGR CHPID(<I1>)->CHPID(<I2>)
Ex. 1: AGGR CHPID(F4)->CHPID(64)
Ex. 2: AGGR CHPID(F5)->CHPID(65)
2. In the Hardware Actions column of the Phase Perform Worksheet for each
CHPID pair:
• Write MOVE CABLE CHPID(<I1>)->CHPID(<I2>)
Ex. 1: MOVE CABLE CHPID(F4)->CHPID(64)
Ex. 2: MOVE CABLE CHPID(F5)->CHPID(65)
3. In the Varies Off column of the Phase Perform Worksheet, for each "new"
CHPID:
• Write CF CHP(<I2>),OFF
Ex.: CF CHP(64,65),OFF
4. In the Varies On column of the Phase Perform Worksheet, for each "new"
CHPID:
• Write CF CHP(<I2>),ON
Ex.: CF CHP(64,65),ON
7.1.3.10 Column J
Of the CHPID numbers deleted in column C, those that will not be reassigned or
aggregated in this phase are noted here. The reassignment of their conected I/O
subsystems will be deferred to later phases. The information about the attached
CUs needs to be saved, so that they can be reassigned later. Once the CHPID is
deleted in HCM or HCD the information will be lost. By scanning column L for

subsequent ADD rows the eventual target CHPID may be found but the
reassignment can not be done at this point.
• Write SAVE CUs:CHPID(<J>)
Ex.: SAVE CUs:CHPID(FA,FB)
7.1.3.11 Column K
This field is really only of value for accounting or bookkeeping. Of the CHPID
numbers deleted in column C, those that will not be reassigned or aggregated are
noted here. That is, the CHPID is decommissioned.
7.1.3.12 Column L
This column will not be used in a DELETE/MOVE row.
7.1.4 Add Row

7.1.4.1 Column A
will be disruptive.
1. If there is an X in column A, write Yes at Non Concurrent Install.
7.1.4.2 Column B to D
These columns are not used in an ADD row.
7.1.4.3 Column E
This is the I/O slot into which the new FICON CHPID’s card and external cable
will be installed.
• Write INSTALL CARD+CABLE @ <E> (optional: CHPID(<F>))
Ex. 1: INSTALL CARD+CABLE @ ZT31
Ex. 2: INSTALL CARD+CABLE @ ZT31 CHPID(FC)
7.1.4.4 Column F and G

This will contain the CHPID number for the new FICON channel. The channel
type is to be found in column G. This will be one of the FICON channel types:
either FCV (when attached to a bridge card in an ESCON switch), or FC (when
attached directly to a FICON switch or FICON-capable CU).
• Write ADD CHPID(<F>) TYPE=<G>
Ex.: ADD CHPID(FC) TYPE=FCV
2. In the Varies Off column of the Phase Perform Worksheet:
• Write CF CHPID(<F>),OFF
Ex.: CF CHPID(FC),OFF
shared. After varying off check on HMC’s channel display that the CHPID is
in “configured on” status.

• Write CF CHPID(<F>),ON
Ex.: CF CHPID(FC),ON
shared. After varying off check on HMC’s channel display that the CHPID is
in ’configured on’ status.
7.1.4.5 Column H
The CUs for the CHPID(s) in this column will be reassigned to the FICON CHPID
in column F of this row. That is, the CHPID(s) in column H will be aggregated to
the CHPID in column F.
Where there are new devices (and, therefore, control units too), a notation is
made to include the definitions. No details are supplied as this is not directly
FICON install-related and is handled by the usual procedures for installing new
devices.
• Write AGGR CHPID(<H>) -> CHPID(<F>)
Ex.:1 AGGR CHPID(F8,E4,E6,48,6A,08,31)->CHPID(FC)
• Write CF CHPID(<H>),OFF
Ex.:1 CF CHPID(F8,E4,E6,48,6A,08,31),OFF
Note: These commands are to be performed on all LPARs if the CHPIDs
are shared. After bringing on, check on HMC’s channel display that the
CHPIDs are in “configured on” status.
If "New CUs" appears in column H, then for each CU:

• Write INSTALL CU<#> CABLE->CHPID(<F>)
Ex.: INSTALL CU23 CABLE->CHPID(FE)
• Write ADD CU<#>->CHPID(<F>)
Ex.: ADD CU23->CHPID(FE)
Column H data is related to column L data. That is, the CHPIDs in H may also
appear in column L. If they do it is important to understand the relationship
between them.
If the CHPID number is the first in a pair in column L, then this really means that
the aggregation for this CHPID is coming from a saved list; that is, there would
have been an instruction generated for the action of saving the CU information in
a prior phase. So the CHPID at this point in time will already have been deleted
and there will really be nothing to aggregate. Instructions in column L will
generate an action to use saved data so that, effectively, a deferred aggregation
takes place.

If the CHPID number is second in a pair in column L, then the aggregation action
generated for it here is to free it so that it may then be used to assign to it a saved
list of CU information from some CHPID that had to be deleted in a prior phase.
7.1.4.6 Column I to K
These columns are not used in an ADD row.
7.1.4.7 Column L
This column for an ADD row is really only of bookkeeping value. A doublecheck
will show the actions for aggregation of the pair were generated for this row in
column H.
This column indicates that some CHPID whose reassignment or aggregation that
was deferred can now be done.
• Write AGGR SAVED(<L1>)->CHPID(<L2>)
Ex.: AGGR SAVED(FE)->CHPID(69)
Note: The order will be important, because for some reason, the
aggregation or reassignment was deferred, which means the second of the
pair of channels was not available until now. That means there is an action
that must be performed to make it available (it either has to be freed or
created). This action to make it available must be performed before this
aggregation action.
7.1.5 Bridge row

7.1.5.1 Column E
This identifies the ESCD to which the FICON channel will be attached. This
ESCD will have a FICON bridge card installed in it.
7.1.5.2 Column F
This identifies the port in which the FICON Bridge card has been installed. Along
with the ESCD number, the port number will identify, for hardware actions --
specifically, cabling -- where the ESCD end of the FICON channel cable is to be
plugged.
7.2 Example of completed Phase Perform Worksheets

What follows is an example of a planned installation of six FICON channels. The
Phase Planning Worksheet (Figure 25 on page 55) and the six completed Phase
Perform Worksheets (Figure 26 on page 56 to Figure 31 on page 58) are
included. Only the processor actions are included in the completed Phase
Perform Worksheets. The CHPIDs installed are FC, F8, FD, F9, FE, FA, in that
order, due to plugging rules and the CHPID number assignment sequence. Note
that ESCON CHPID FA is decommissioned in this example, that is, no
reassignment of any attached CUs takes place.

CU-PATH or CU->PATH
Phase #1
DELETE/MOVE
DELETE
DELETE/MOVE
6A,08,31
Bridge ESCD #1 Port
Figure 25. Phase Planning Worksheet

Phase #2
DELETE Z TOP 34 F8-FB ESCON F9 FB FA
DELETE/MOVE
DELETE Z TOP 21 64-67 ESCON 66=>49,67=>6B 64,65

E7,49,6B
Bridge ESCD #2 Port
Phase #3
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
AB,9F,81,4B FB=>FD
Bridge ESCD #3 Port
Phase #4
DELETE/MOVE
DELETE
DELETE/MOVE
82
Bridge ESCD #1 Port
Phase #5
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
New CUs 65=>FE
Bridge ESCD #2 Port
Phase #6
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
Chapter 7. Processor phase actions

Bridge ESCD #3 Port
55
P ro c . 9 6 72 -5 1 1 2 3 4 5 P ro c e s s o r/E S C D P h a s e P e rfo rm W o rk s h e e t
Phase # 1 N o n -C o n c u rre n t In s ta ll (Y e s /N o ) N o
D e f i n it i o n s V a r ie s O f f H a r d w a r e A c tio n s V a r ie s O n
D E L E T E C H P ID (F C -F F ) C F C H P (F C -F F ) O F F R E M O V E C A B LE + C A R D @ Z T3 3
A G G R C H P ID ( F C ) - > C H P ( F C )
S A V E C U s : C H P ID ( F D , F E , F F )
A D D C H P ID ( F C ) T Y P E = F C V C F C H P ( F 8 ,E 4 ,E 6 ,4 8 ) O F F IN S T A LL C A R D + C A B L E @ Z T 3 1 C F C H P (F C ) O N
A G G R C H P ID ( F 8 , E 4 , E 6 , 4 8 ) C F C H P (6 A ,0 8 ,3 1 ) O F F
-> C H P ID ( F C )
A G G R C H P ID ( 6 A ,0 8 ,3 1 )
-> C H P ID ( F C )
Figure 26. Phase Perform Worksheet for Phase 1
P r o c .9 6 7 2 -5 1 1 2 3 4 5 P r o c e s s o r /E S C D P h a s e P e rfo rm W o rk s h e e t
Phase # 2 N o n - C o n c u r r e n t I n s t a ll ( Y e s / N o ) Y E S
D e fi n it io n s V a r ie s O ff H a r d w a r e A c t io n s V a r ie s O n
D E L E T E C H P ID ( F 8 -F B ) C F C H P (F 8 -F B ) O F F R E M O V E C A B LE +C A R D @ ZT 34
A G G R C H P ID (F 9 ) - > C H P ID (F 8 )
S A V E C U s : C H P ID ( F A ,F B )
D E L E T E C H P ID ( 6 4 -6 7 ) C F C H P (64 ,6 7) O F F R E M O V E C A B LE +C A R D @ ZT 21
C F C H P ( 4 9 ,6 B ) O N
A G G R C H P ID (6 4 ) -> C H P (4 9 ) C F C H P (49 ,6 B ) O F F M O V E C A B L E + C A R D C H P ( 6 6 )-> C H P ( 4 9 )
A G G R C H P ID (6 7 ) -> C H P (6 B ) M O V E C A B L E + C A R D C H P ( 6 7 )-> C H P ( 6 B )
S A V E C U s : C H P ID ( 6 4 ,6 5 )
D E L E T E C H P ID ( F 4 ,F 5 ) C F C H P (64 ,6 5) O F F C F C H P ( 6 5 ,6 5 ) O N
R E M O V E C A B LE +C A R D @ ZT 06
A D D C H P ID ( 6 4 ,6 5 ) T Y P E = IS C IN S T A L L C A R D + C A B L E @ Z T 2 1
A G G R C H P ID (F 4 ) - > C H P ID (6 4 ) M O V E C A B L E + C A R D C H P ( F 4 )- > C H P (6 4 )
A G G R C H P ID (F 5 ) - > C H P ID (6 5 ) M O V E C A B L E + C A R D C H P ( F 5 )- > C H P (6 5 )
A D D C H P ID ( F 8 ) T Y P E = F C V C F C H P ( F D ,F 1 , E 1 , E 5 ) O F F C F C H P (F 8 ) O N
A D D C A R D + C A B LE @ ZT 0 6
A G G R C H P ID (F D ,F 1 ,E 1 ,E 5 ) C F C H P (E 7 ,4 9,6 B ) O F F
-> C H P ID ( F 8 )
A G G R C H P ID (E 7 ,4 9 ,6 B 1 )
-> C H P ID ( F 8 )
A G G R S A V E D (F D )-> C H P (F 8 )

P ro c . P ro c e s s o r /E S C D P h a s e P e rfo rm W o rk s h e e t
P hase # 3 N o n -C o n c u rre n t In s ta ll (Y e s /N o ) N o
D e fin itio n s V a rie s O ff H a rd w a re A c tio n s V a rie s O n
A D D C H P ID ( F D ) C F C H P (F D ) O N
C F C H P (F D ) O F F I N S T A LL C A R D + C A B LE @ Z T 3 2
A G G R C H P ID ( F F , F B ,F 3 ,E 3 )
-> C H P ID ( F 8 )
A G G R C H P ID ( A B ,9 F ,8 1 ,4 3 )
-> C H P ID ( F D ) C F C H P (F F ,F B ,F 3 ,E 3 ) O F F
A G G R S A V E D (F F )-> C H P (F D ) C F C H P (A B ,9 F ,8 1 ,4 3 ) O F F
A G G R S A V E D (F B ) -> C H P (F D )
P r o c . 9 6 7 2 - 5 1 1 2 3 4 5 P r o c e s s o r /E S C D P h a s e P e r fo r m W o r k s h e e t
Phase # 4 N o n - C o n c u r r e n t I n s ta ll ( Y e s /N o ) N o
D e f in it io n s V a r ie s O f f H a r d w a r e A c t io n s V a r ie s O n
D E L E T E C H P ID (F 0 -F 3 ) C F C H P (F 0 -F 3 ) O F F R EM O VE CA BLE+C ARD @ ZT07 C F C H P (6 8 ) O N
A G G R C H P ID ( F 0 ) -> C H P ID (F 9 ) C F C H P ( 6 8 ) O F F M O V E C A B L E C H P (F 2 )-> C H P (6 8 )
A G G R C H P ID ( F 2 ) -> C H P ID (6 8 )
A D D C H P ID ( F 9 )
IN S T A L L C A R D + C A B L E @ Z T 0 7
A G G R C H P ID ( E 0 ,C 0 ,6 8 ,6 4 ,8 2 ) C F C H P ( E 0 ,C 0 , 6 8 ,6 4 , 8 2 ) O F F C F C H P (F 9 ) O N
- > C H P ID (F 9 )
A G G R S A V E D (6 4 ) -> C H P ( F 9 )

P r o c . 9 6 7 2 -5 1 1 2 3 4 5 P r o c e s s o r /E S C D P h a s e P e r fo r m W o r k s h e e t
Phase # 5 N o n - C o n c u r r e n t In s ta ll ( Y e s /N o ) N o
A D D C H P ID ( F E ) T Y P E = F C V C F C H P (F E ) O F F IN S T A L L C A R D + C A B L E @ Z T 0 7 C F C H P (F E ) O N
A G G R C H P ID (C 1 , 6 9 ,6 5 , 8 3 ) C F C H P (C 1 ,6 9 ,6 5 ,8 3 ) O F F
- > C H P ID ( F E )
A D D C U # - > C H P ID (F E ) IN S T A L L C U # C A B L E - > C H P (F E )
A G G R S A V E D (F E )-> C H P (6 9 )
A G G R S A V E D (6 5 )-> C H P (F E )
Phase # 6 N o n - C o n c u r r e n t I n s t a ll ( Y e s /N o ) N o
A D D C H P I D (F A ) T Y P E = F C V C F C H P (F A ) O F F IN S T A L L C A R D + C A B L E @ Z T 3 4 C F C H P (F A ) O N
A D D C U # -> C H P ID ( F A ) IN S T A L L C U # C A B L E -> C H P ( F A )
Notice that the actions in the completed Phase Perform Worksheets have been
grouped according to the row in the Phase Planning Worksheet from which they
were generated. These groupings have been separated by a blank line. This
makes checking easier and will help when ordering or sorting the actions.
7.3 Sorting phase actions

This section describes the considerations for sorting the processor actions within
a phase. Some ordering will be necessary as some actions have prerequisite
actions that must be performed beforehand.
The example used will be the second phase in the previous section.

P ro c .9 6 7 2 -5 1 1 2 3 4 5 P ro c e s s o r/E S C D P h a s e P e rfo rm W o rk s h e e t
P hase # 2 N o n -C o n c u rre n t In s ta ll (Y e s /N o ) Y e s
D e fi n itio n s V a r ie s O ff H a r d w a r e A c t io n s V a r ie s O n
D E L E T E C H P ID ( F 8 -F B ) C F C H P (F 8 -F B ) O F F R E M O V E C A B LE + C A R D @ Z T 34
A G G R C H P ID ( F 9 )- > C H P ID ( F 8 )
S A V E C U s :C H P ID ( F A ,F B )
D E L E T E C H P ID ( 6 4 -6 7 ) C F C H P ( 6 4 ,6 7 ) O F F R E M O V E C A B LE + C A R D @ Z T 21 C F C H P ( 4 9 ,6 B ) O N
A G G R C H P ID ( 6 4 ) - > C H P ( 4 9 ) C F C H P ( 4 9 ,6 B ) O F F M O V E C A B L E + C A R D C H P ( 6 6 ) -> C H P ( 4 9 )
A G G R C H P ID ( 6 7 ) - > C H P ( 6 B ) M O V E C A B L E + C A R D C H P ( 6 7 ) -> C H P ( 6 B )
S A V E C U s :C H P ID ( 6 4 , 6 5 )
D E L E T E C H P ID ( F 4 ,F 5 ) C F C H P ( 6 4 ,6 5 ) O F F C F C H P ( 6 5 ,6 5 ) O N
R E M O V E C A B LE + C A R D @ Z T 06
A D D C H P ID ( 6 4 ,6 5 ) T Y P E = I S C IN S T A L L C A R D + C A B L E @ Z T 2 1
A G G R C H P ID ( F 4 )- > C H P ID ( 6 4 ) M O V E C A B L E + C A R D C H P ( F 4 )-> C H P (6 4 )
A D D C H P ID ( F 8 ) T Y P E = F C V C F C H P ( F D ,F 1 , E 1 ,E 5 ) O F F C F C H P (F 8) O N
AD D C A R D +C A B LE @ ZT 06
A G G R C H P ID ( F D ,F 1 ,E 1 ,E 5 ) C F C H P (E 7,4 9,6B ) O F F
- > C H P ID ( F 8 )
A G G R C H P ID ( E 7 ,4 9 ,6 B 1 )
- > C H P ID ( F 8 )
A G G R S A V E D (F D ) - > C H P (F 8 )
Figure 32. Phase Perform Worksheet for Phase 2 Unsorted
P hase # 2 N o n - C o n c u r r e n t I n s t a ll ( Y e s / N o ) Y e s
D e fin iti o n s V a r ie s O f f H a r d w a r e A c tio n s V a rie s O n
A G G R C H P ID ( F 9 )- > C H P ID ( F 8 ) C F C H P ( F 8 - F B ) O F F R E M O V E C A BL E +C A R D @ ZT 34
S A V E C U s : C H P I D ( F A ,F B )
D E L E T E C H P ID ( F 8 - F B )
A G G R C H P ID ( 6 4 ) - > C H P ( 4 9 ) C F C H P ( 6 4 ,6 7 ) O F F R E M O V E C A BL E +C A R D @ ZT 21
C F C H P ( 4 9 ,6 B ) O N
A G G R C H P ID ( 6 7 ) - > C H P ( 6 B ) C F C H P ( 4 9 ,6 B ) O F F M O V E C A B L E + C A R D C H P ( 6 6 ) -> C H P ( 4 9 )
S A V E C U s : C H P I D ( 6 4 ,6 5 ) M O V E C A B L E + C A R D C H P ( 6 7 ) -> C H P ( 6 B )
D E L E T E C H P ID ( 6 4 -6 7 )
A D D C H P ID ( 6 4 , 6 5 ) T Y P E = I S C C F C H P ( 6 4 ,6 5 ) O F F C F C H P ( 6 5 ,6 5 ) O N
R E M O V E C A BL E +C A R D @ ZT 06
A G G R C H P ID ( F 4 )- > C H P ID ( 6 4 ) IN S T A LL C A R D + C A B L E @ Z T 21
D E L E T E C H P ID ( F 4 ,F 5 ) M O V E C A B L E + C A R D C H P ( F 5 )-> C H P (6 5 )
A D D C H P ID ( F 8 ) T Y P E = F C V C F C H P ( F D ,F 1 , E 1 ,E 5 ) O F F C F C H P (F 8) O N
A D D C AR D +C A B LE @ Z T0 6
A G G R C H P ID ( F 1 ,E 1 , E 5 ) C F C H P (E 7,4 9,6B ) O F F
-> C H P ID ( F 8 )
A G G R C H P ID ( E 7 , 4 9 , 6 B 1 )
-> C H P ID ( F 8 )
A G G R S A V E D ( F D ) - > C H P (F 8 )
Figure 33. Phase Perform Worksheet for Phase 2 Sorted
Figure 32 is unsorted and Figure 33 is sorted. Sorting is a relatively simple task.

Most of the order is provided by the order of the rows in the Phase Planning
Worksheet. It is only necessary to order the actions within a row.
In addition to this, it is not necessary to order vary commands, so the actions in

the Varies Off and Varies On columns of the Phase Perform Worksheet require no
sorting. It is only in the case of definition and hardware activities that some logical
sequencing of actions is necessary.
In the case of hardware actions, the row sequence in the Phase Planning
Worksheet within a phase, combined with the left-to-right sequence of the
columns, provides the logical ordering necessary to perform the hardware actions
in proper sequence. This same logical consequence is true for definition actions,

except for the case of a delete of CHPIDs. In this case, the DELETE must be the
last action to be performed of the actions for the row.
Therefore, the only column on the Phase Perform Worksheet that requires sorting
is the Definitions column. The algorithm to sort is simple:
1. Within the group of actions for the row (from the Phase Planning Worksheet),
ensure deletes are done last and adds are done first.
2. Keep the groups of row actions in the same order as their rows within the
phase.
In practice, it will only be necessary to move the delete action to the last position
in the group of actions.

Chapter 8. ESCON Director phase actions
This chapter describes how to use the ESCON Director Impact Analysis (see
Figure 34 on page 62) to produce the ESCD Phase Perform Worksheet (see
Figure 35 on page 63). There will be one Phase Perform Worksheet for each
phase.
There is only one row per phase in the ESCON Director Impact Analysis. All
columns in the row will contain all necessary actions related to the tasks
associated with installation of a FICON Bridge card in an ESCD. This includes
freeing ports, moving ports, adding the card and connecting the FICON channel.
For each phase, its row will be worked through column by column, left to right.
There are instructions for each column on what actions are to be written into the
Phase Perform Worksheet.
8.1 Phase Perform Worksheet completion instructions

As already mentioned, installation of a Bridge card requires eight free ports,
which if the ESCD is fully populated, adds complexity and will increase the
number of actions required. The procedure described here will accommodate this
circumstance.
The following instructions document what is to be written into the Phase Perform
Worksheet based on what is found in columns of the ESCON Director Impact
Analysis.

A B C D E F G H

(Empty slot) FC

F8 4D 4D => 46
4E 4E => 63
50 50 => A8
51 51 => A9
52 52 => C3
(Empty slot) FD

F9 86 86 => DA
87 87 => DB

(Empty slot) FE

FA E5 E5 => DF
E6 E6=>57 ESCD#1
BD=>9D ESCD#1
B5=>A5 ESCD#1
E7 E7=>77 ESCD#1
24=>AD ESCD#1
1C=>95 ESCD#1
0C=>AC ESCD#1
04=>94 ESCD#1
E9 E9=>8D ESCD#1
25=>AE ESCD#1
1D=>96 ESCD#1
0D=>AB ESCD#1
05=>97 ESCD#1
EA EA=>93 ESCD#1
33=>98 ESCD#1
42=>AF ESCD#1
Figure 34. ESCON Director impact analysis
The output from this process is a completed Phase Perform Worksheet. Figure 35
on page 63 shows a blank Phase Perform Worksheet.

P ro c .# _ _ _ _ _ _ _ _ P ro c e s s o r/E S C D P h a s e P e rfo rm
W o rk s h e e t
P hase # ________ N o n C o n c u rre n t In s ta ll (Y e s /N o ) _ _ _
D e fin itio n s V a rie s O ff H a rd w a re A c tio n s V a rie s o n
The output document from this process will be a completed Phase Perform
Worksheet containing all the actions related to installation of the FICON Bridge
card in an ESCD for the phase. There will be one Phase Perform Worksheet
produced for each phase. Each row in the ESCD Impact Analysis represents a
phase and therefore one Phase Perform Worksheet.
The Phase Perform Worksheet has been designed to accommodate

processor-related actions in the top portion and ESCD-related actions in the
lower portion. It is not mandatory to adhere to this scheme, as the actions for
processor and ESCD can be on two separate sheets. However, remember that in
the sequence of actions, while mostly processor actions will be independent of
ESCD actions, the definition of the FICON CHPID must be complete before it can
be connected to the ESCD “bridge” port.
8.1.1 For each phase row

The following procedure will be used to work through each row in the ESCD
Impact Analysis, working column by column from left to right.
8.1.1.1 Column A
Column A will identify the ESCON Director, column B will identify the FICON port
address, and column C will identify the processor and the CHPID for this
particular FICON connection.
1. In the Definition column of the Phase Perform Worksheet:
• Write CONVERT PORT#<B>.ESCD#<A>
Ex.: CONVERT PORT#B4.ESCD#1
• Write CONNECT CHPID#<C>->PORT#<B>.ESCD#<A>
Ex.: CONNECT CHPID#FC->PORT#B4.ESCD#1
Chapter 8. ESCON Director phase actions 63

8.1.1.2 Column B
This will identify the port where the FICON Bridge card will be installed. It also
may indicate if the port slot is EMPTY.
• Write EDIT PORT#<B>.CHPID#<C>.PROC#<C>
Ex.: EDIT PORT#B4.CHPID#FC.PROC#CPU1234
If the slot is not empty, then:
• Write REMOVE CABLES+CARD PORT#<B>[.SLOT#<X>].ESCD#<A>
Ex. 1: REMOVE CABLES+CARD PORT#B4.SLOT#22.ESCD#1
Ex. 2: REMOVE CABLES+CARD PORT#B4.ESCD#1
If reusing multimode fiber, then:
• Write INSTALL M/C CABLE PORT#<B>[.SLOT#<X>].ESCD#<A>
Ex. 1: INSTALL M/C CABLE PORT#B4.SLOT#22.ESCD#1
Ex. 2: INSTALL M/C CABLE PORT#B4.ESCD#1
• Write INSTALL F/B PORT#<B>[.SLOT#<X>].ESCD#<A>
Ex. 1: INSTALL F/B PORT#B4.SLOT#22.ESCD#1
Ex. 2: INSTALL F/B PORT#B4.ESCD#1
• Write BLOCK PORT#<B-B+7>.ESCD#<A>
Ex.: BLOCK PORT#B4-BB.ESCD#1
• Write UNBLOCK PORT#<B>.ESCD#<A>
Ex.: UNBLOCK PORT#B4.ESCD#1
Figure 36 maps the port number to a slot number. A similar figure will appear on
the inside of the 9032-005’s front door. This mapping is also described in
Planning for the 9032 Model 3, 9033 Model 4, and 9032 Model 5, SA22-7295.

L o g ic a l p o rt S lo t # L o g ic a l p o rt S lo t #
a d d re s s e s a d d re s s e s
04 - 0B 00 84 - 8B 16
0C - 13 01 8C - 93 17
14 - 1B 02 94 - 9B 18
1C - 23 03 9C - A3 19
24 - 2B 04 A4 - AB 20
2C - 33 05 AC - B3 21
34 - 3B 06 B4 - BB 22
3C - 43 07 BC - C3 23
44 - 4B 08 C4 - CB 24
4C - 53 09 CC - D3 25
54 - 5B 10 D4 - DB 26
5C - 63 11 DC - E3 27
64 - 6B 12 E4 - EB 28
6C - 73 13 EC - F3 29
74 - 7B 14 F4 - FB 30
7C - 83 15
Figure 36. Logical port addresses relative to Slot #
8.1.1.3 Columns C, D and E

There are no actions for these columns.
Column C information has already been used in instructions for column A.
Column D repeats information already derived from column B.
Column E’s information is included in other columns (G and H) and is handled by

instructions for those columns.
8.1.1.4 Column F
Port numbers in this column will now be free due to ESCON-to-FICON CHPID
aggregation (or were not in use???).
• Write BLOCK PORT#<F>.ESCD#<A>
Ex.: BLOCK PORT#B4.ESCD#1
Use ESCON Manager to BLOCK the ports identified in this column to
insure that the “new” ports will be available for use. These ports will be
the"new" ports for column "G".
2. In the Hardware Action column of the Phase Perform Worksheet:
• Write REMOVE CABLES+CARD PORT#<B>[.SLOT#<X>].ESCD#<A>
Ex. 1: REMOVE CABLES+CARD PORT#B4.SLOT#22.ESCD#1
Ex. 2: REMOVE CABLES+CARD PORT#B4.ESCD#1

8.1.1.5 Column G
This contains pairs of ports. The first port will be relocated to the second port
within the same ESCD.
• Write MOVE PORT#<G1>.ESCD#<A>->PORT#<G2>[.ESCD#<A>]
Ex. 1: MOVE PORT#4C.ESCD#1->PORT#36.ESCD#1
Ex. 2: MOVE PORT#4C.ESCD#1->PORT#36
• Write BLOCK PORT#<G1>.ESCD#<A>
• Write BLOCK PORT#<G2>.ESCD#<A>
Ex. 1: BLOCK PORT#4C.ESCD#1
Ex. 2: BLOCK PORT#36.ESCD#1
• Write MOVE CABLES
PORT#<G1>.ESCD#<A>=>PORT#<G2>[.ESCD#<A>]
Ex. 1: MOVE CABLES PORT#4C.ESCD#1=>PORT#36.ESCD#1
Ex. 2: MOVE CABLES PORT#4C.ESCD#1=>PORT#36
• Write UNBLOCK PORT#<G2>.ESCD#<A>
Ex.: UNBLOCK PORT#36.ESCD#1
8.1.1.6 Column H
This identifies ports to be moved to another port in a different ESCD.
• Write MOVE PORT#<H1>.ESCD#<A>->PORT#<H2>[.ESCD#<H3>]
Ex.: MOVE PORT#E6.ESCD#2->PORT#57.ESCD#1
• Write BLOCK PORT#<H1>.ESCD#<A>
• Write BLOCK PORT#<H2>.ESCD#<H3>
Ex.: BLOCK PORT#E6.ESCD#2
Ex.: BLOCK PORT#57.ESCD#1
• Write
MOVE CABLES PORT#<G1>.ESCD#<A>=>PORT#<G2>[.ESCD#<A>]
Ex.: MOVE CABLES PORT#E6.ESCD#2=>PORT#57.ESCD#1
• Write UNBLOCK PORT#<H2>.ESCD#<H3>
Ex.: UNBLOCK PORT#57.ESCD#1

8.2 Example of completed Phase Perform Worksheets
The following is an example of a six-phase installation. This means on the processor
there will be six FICON channels installed and therefore there must be six FICON
Bridge cards installed.
In the example, these Bridge cards are installed in two ESCDs. That is, there are
three FICON Bridge cards installed in each of the two ESCDs.
The ESCON Director Impact Analysis shown in Figure 37 is used to produce the six
Phase Perform Worksheets that follow. For the purposes of this example, it is
assumed that there will be no reuse of multimode fiber cables.

A B C D E F G H

(Empty slot) FC

F8 4D 4D => 46
4E 4E => 63
50 50 => A8
51 51 => A9
52 52 => C3
(Empty slot) FD

F9 86 86 => DA
87 87 => DB

(Empty slot) FE

FA E5 E5 => DF
E6 E6=>57 ESCD#1
BD=>9D ESCD#1
B5=>A5 ESCD#1
E7 E7=>77 ESCD#1
24=>AD ESCD#1
1C=>95 ESCD#1
0C=>AC ESCD#1
04=>94 ESCD#1
E9 E9=>8D ESCD#1
25=>AE ESCD#1
1D=>96 ESCD#1
0D=>AB ESCD#1
05=>97 ESCD#1
EA EA=>93 ESCD#1
33=>98 ESCD#1
42=>AF ESCD#1
Figure 37. ESCON Director Impact Analysis

Phase # 1 N o n -C o n c u rre n t In s ta ll (Y e s /N o ) N o
D E L E T E C H P I D (F C -F F ) C F C H P (F C -F F ) O F F R EM O V E CA BLE+CA RD @ ZT 33
A G G R C H P ID (F C )-> C H P (F C )
S A V E C U s :C H P ID (F D ,F E ,F F )
A D D C H P ID (F C ) T YP E = F C V C F C H P (F 8 ,E 4 , E 6 ,4 8) O F F C F C H P (F C ) O N
A G G R C H P ID (F 8 ,E 4 ,E 6 ,4 8 ) C F C H P (6 A ,0 8 ,3 1) O F F IN S T A L L C A R D + C A B LE @ Z T 3 1
-> C H P ID (F C )
A G G R C H P ID (6 A , 08 ,3 1 )
-> C H P ID (F C )
C O N NEC T CH P#FC IN S T A L L F B
=> P O R T # B 4 .E S C D # 1 P O R T # B 4 .S L O T # 2 2. E S C D # 1 U N B L O C K P O R T # B 4 .E S C D # 1
E D IT P O R T # B 4 B L O C K P O R T # B 4 -B B .E S C D # 1
C P U # 1 23 4 _ C H P ID _ F C _ F C V
Figure 38. Phase Perform Worksheet - Phase 1
The ESCD actions can be written into the bottom portion of the Phase Perform
Worksheet, or, as in Figure 39, because of space, a separate worksheet may be
used.

Phase # 2 N o n C o n c u rre n t In s ta ll (Y e s /N o ) Y E S
R E M O V E C A B L E + C A R D P O R T # 4 C .E S C D # 2
C O N N E C T C H P ID # F 8 = > P O R T # 4 C .E S C D # 2
IN S T A L L F B P O R T # 4 C . E S C D # 2
E D IT P O R T # 4 C C P U # 1 2 3 4 _C H P ID _F 8 _ F C V
R E M O V E C A B L E + C A R D P O R T # 3 6 .E S C D # 2
M O V E P O R T # 4C .E S C D # 2= > 3 6
R E M O V E C A B L E + C A R D P O R T # C E .E S C D # 2
M O V E P O R T # 4D .E S C D # 2= > 4 6
R E M O V E C A B L E + C A R D P O R T # D A .E S C D # 2
M O V E P O R T # 4E .E S C D # 2 = > 6 3
R E M O V E C A B L E + C A R D P O R T # D B .E S C D # 2
M O V E P O R T # 50 .E S C D # 2 = >A 8
M O V E C A B L E + C A R D P O R T #4 C .E S C D # 2= > P O R T # 3 6.E S C D # 2
M O V E P O R T # 51 .E S C D # 2 = >A 9
M O V E C A B L E + C A R D P O R T #4 D .E S C D # 2= > P O R T # 4 6.E S C D # 2
M O V E P O R T # 52 .E S C D # 2 = >C 3 BLOC K P O R T # 36 .E S C D # 2 M O V E C A B L E + C A R D P O R T #4 E .E S C D # 2 = > P O R T # 6 3 .E S C D #2
BLOC K P O R T # C E .E S C D # 2 M O V E C A B L E + C A R D P O R T #5 0 .E S C D # 2 => P O R T # A 8 .E S C D #2
BLOC K P O R T # D A .E S C D # 2 M O V E C A B L E + C A R D P O R T #5 1 .E S C D # 2 => P O R T # A 9 .E S C D #2
BLOC K P O R T # D B .E S C D # 2 M O V E C A B L E + C A R D P O R T #5 2 .E S C D # 2 => P O R T # C 3.E S C D # 2
BLOC K P O R T # 4C .E S C D # 2
BLOC K P O R T # 4D .E S C D # 2 U NBLO CK P O R T # 3 6 .E S C D #2
BLOC K P O R T # 46 .E S C D # 2 U NBLO CK P O R T # 4 6 .E S C D #2
BLOC K P O R T # 4E .E S C D # 2 U NBLO CK P O R T # 6 3 .E S C D #2
BLOC K P O R T # 63 .E S C D # 2 U NBLO CK P O R T # A 8 .E S C D # 2
BLOC K P O R T # 50 .E S C D # 2 U NBLO CK P O R T # A 9 .E S C D # 2
BLOC K P O R T # A 8 .E S C D # 2 U NBLO CK P O R T # C 3. E S C D # 2
BLOC K P O R T # 51 .E S C D # 2
BLOC K P O R T # A 9 .E S C D # 2
BLOC K P O R T # 52 .E S C D # 2
BLOC K P O R T # C 3 .E S C D # 2

P ro c. 9 6 7 2 -5 1 1 2 3 4 5 P ro c e s so r/E S C D P h a s e P e rfo rm W o rksh e e t
P h a se # 3 N o n -C o n cu rre n t In s ta ll (Y e s/N o ) N o
D e fin itio n s V a rie s O ff H a rd w a re A ctio n s V a rie s O n
A D D C H P ID (F D ) C F C H P (F D ) O F F IN S T A L L C A R D + C A B L E @ Z T 3 2 C F C H P (F D ) O N
A G G R C H P ID (F F ,F B ,F 3 ,E 3 )
-> C H P ID (F 8 )
A G G R C H P ID (A B , 9F ,8 1 ,4 3 )
-> C H P ID (F D ) C F C H P (F F ,F B ,F 3 ,E 3) O F F
A G G R S A V E D (F F )-> C H P (F D ) C F C H P (A B ,9 F ,8 1 ,4 3 ) O F F
A G G R S A V E D (F B )-> C H P (F D )
C O N N E C T C H P ID #F D IN S T A L L F B P O R T # C 4 .E S C D # 1 U N B L O C K P O R T # C 4 .E S C D #1
=> P O R T # C 4 .E S C D # 1
E D IT P O R T # C 4 B L O C K P O R T #C 4 -C B .E S C D # 1
C P U # 1 2 3 4 _ C H P ID _ F D _ F C V
P ro c . 9 6 7 2 -5 1 1 2 3 4 5 P ro c e s s o r/E S C D P h a s e P e rfo rm W o rk s h e e t
P ha se # 4 N o n C o n c u rre n t In s ta ll (Y e s /N o ) N O
D E L E T E C H P ID (F 0-F 3 ) C F C H P (F 0 -F 3 ) O F F RE M O VE CAB LE+CA RD @ ZT 07 C F C H P (6 8 ) O N
A G G R C H P I D (F 0 )-> C H P ID (F 9 ) C F C H P (6 8 ) O F F M O V E C A B L E C H P (F 2)-> C H P (6 8 )
A G G R C H P I D (F 2 )-> C H P ID (68 )
A D D C H P I D (F 9 )
A G G R C H P I D (E 0 ,C 0 ,6 8 ,6 4 ,8 2 ) C F C H P (E 0 ,C 0 ,68 , 64 ,8 2 ) O F F IN S T A LL C A R D +C A B L E @ Z T 0 7 C F C H P (F 9 ) O N
->C H P ID (F 9 )
A G G R S A V E D (6 4 )-> C H P (F 9 )
C O N N E C T C H P ID # F 9 => P O R T # 8 4 .E S C D #2 R E M O V E C A B L E + C A R D P O R T # 84 -8 C .E S C D # 2
E D IT P O R T # 8 4. E S C D # 2 C P U 12 3 4 _ C H P _ F 9 _ F C V
IN S T A LL F B P O R T # 8 4 .E S C D #2
B L O C K P O R T # 8 4-8 B .E S C D # 2 U N B L O C K P O R T # 84 . E S C D # 2
M O V E P O R T # 8 5 .E S C D #2 = > P O R T # C E .E S C D # 2
M O V E C A B L E S P O R T # 8 5 .E S C D # 2= > P O R T # C E .E S C D #2
M O V E P O R T # 8 6 .E S C D #2 = > P O R T # D A .E S C D # 2 M O V E C A B L E S P O R T # 8 6 .E S C D # 2= > P O R T # D A .E S C D #2
M O V E P O R T # 8 7 .E S C D #2 = > P O R T # D B .E S C D # 2 M O V E C A B L E S P O R T # 8 7 .E S C D # 2= > P O R T # D B .E S C D #2
B L O C K P O R T # 8 5-8 7 .E S C D # 2 U N B L O C K P O R T # C E .E S C D #
B LO C K P O RT #CE ,DA ,DB .E S C D#2 U N B L O C K P O R T # D A -D B .E S C D #2

P ro c . 9 6 7 2 -5 1 1 2 3 4 5 P ro c e s so r/E S C D P h a s e P e rfo rm W o rk s h e e t
Phase # 5 N o n -C o n cu rre n t In s ta ll (Y e s /N o ) N o
A D D C H P I D (F E ) T Y P E = F C V C F C H P (FE ) O FF IN S T A L L C A R D + C A B LE @ Z T 07 C F C H P (FE) O N
A G G R C H P ID (C 1,6 9,6 5,8 3) C F C H P ( C 1,6 9,6 5,8 3 ) O F F
-> C H P ID (F E )
A D D C U #- > C H P ID (F E ) IN S T A L L C U # C A B L E -> C H P (F E )
A G G R S A V E D ( F E )-> C H P (6 9 )
A G G R S A V E D ( 65 )-> C H P ( F E )
C O N N E C T C H P ID # F E IN S T A L L F B P O R T #B C .E S C D # 1
= > P O R T # B C .E S C D # 1
E D IT P O R T # B C .E S C D # 1 B L O C K P O R T # B C -C 3 .E S C D # 1 U N B LO C K P O R T # B C .E S C D # 1
C P U # 12 34 _ C H P ID _ F E _F C V
P ro c. 9 6 72 -51 1 23 4 5 P ro c e sso r/E S C D P h a se P e rfo rm W o rksh e e t
Phase # 6 N o n -C o n c u rre n t In sta ll (Y e s /N o ) N o

D e fin itio n s V a rie s O ff H a rd w a re A ctio n s V a rie s O n
A D D C H P ID (F A ) TY P E = FC V C F C H P (F A ) O F F IN S T A L L C A R D + C A B L E @ Z T 3 4 C F C H P (F A ) O F F
A D D C U # -> C H P ID (FA ) IN S T A L L C U # C A B LE ->C H P (F A )
C O N N E C T C H P ID # FA => P O R T# E 4 .E S C D # 2 R E M O V E C A B L E + C A R D P O R T #E 4 -E B .E S C D # 2
E D IT P O R T # E 4 .E S C D # 2 C P U # 1 2 3 4 _ C H P ID _ F A _F C V IN S T A L L F B P O R T # E 4.E S C D # 2
B L O C K P O R T # E 4 -E B .E S C D # 2 U N B L O C K P O R T # E 4 .E S C D # 2
M O V E P O R T # E 4 .E S C D # 2 = > P O R T# D E .E S C D # 2 M O V E C A B L E S P O R T # E 4 .E S C D #2 = >P O R T # D E .E S C D # 2
M O V E P O R T # E 5 .E S C D # 2 = > P O R T# D F.E S C D # 2 M O V E C A B L E S P O R T # E 4 .E S C D #2 = >P O R T # D E .E S C D # 2
B L O C K P O R T # E 4 -E 5 .E S C D # 2 U N B L O C K P O R T # D E -D F.E S C D # 2
B L O C K P O R T # D E -D F.E S C D # 2
M O V E P O R T # E 6 .E S C D # 2 = > P O R T# 5 7 .E S C D #1 B LO C K B O T H MOVE CABLE PO R T # E 6 .E S C D # 2 => P O R T # 57 .E S C D #1 U N B LO C K 57
M O V E P O R T # B D .E S C D # 2 => P O R T # 9 D .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # B D .E S C D # 2 => P O R T #9 D .E S C D # 1 U N B LO C K 9D
M O V E P O R T # B 5 .E S C D # 2 = > P O R T# A 5 .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # B 5 .E S C D # 2 => P O R T # A 5.E S C D # 1 U N B LO C K A5
M O V E P O R T # E 7 .E S C D # 2 = > P O R T# 7 7 .E S C D #1 B LO C K B O T H MOVE CABLE PO R T # E 7 .E S C D # 2 => P O R T # 77 .E S C D #1 U N B LO C K 77
M O V E P O R T # 2 4 .E S C D # 2 = > P O R T# A D .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 2 4.E S C D # 2 => P O R T #A D .E S C D #1 U N B LO C K AD
M O V E P O R T # 1 C .E S C D # 2 = >P O R T # 9 5 .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 1 C .E S C D # 2= > PO R T # 9 5.E S C D # 1 U N B LO C K 95
M O V E P O R T # 0 C .E S C D # 2 = >P O R T # A C .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 0 C .E S C D # 2= > PO R T # A C .E S C D # 1 U N B LO C K AC
M O V E P O R T # 0 4 .E S C D # 2 = > P O R T# 9 4 .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 0 4.E S C D # 2 => P O R T #9 4 .E S C D # 1 U N B LO C K 94
M O V E P O R T # E 9 .E S C D # 2 = > P O R T# 8 D .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # E 9 .E S C D # 2 => P O R T # 8D .E S C D #1 U N B LO C K 8D
M O V E P O R T # 2 5 .E S C D # 2 = > P O R T# A E .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 2 5.E S C D # 2 => P O R T #A E .E S C D # 1 U N B LO C K AE
M O V E P O R T # 1 D .E S C D # 2 = >P O R T # 9 6 .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 1 D .E S C D # 2= > PO R T # 9 6.E S C D # 1 U N B LO C K 96
M O V E P O R T # 0 D .E S C D # 2 = >P O R T # A B .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 0 D .E S C D # 2= > PO R T # A B .E S C D # 1 U N B LO C K AB
M O V E P O R T # E A .E S C D # 2 = > P O R T# 9 3 .E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # E A .E S C D # 2= > P O R T # 9 3.E S C D # 1 U N B LO C K 93
M O V E P O R T # 4 2 .E S C D # 2 = > P O R T# A F.E S C D # 1 B LO C K B O T H MOVE CABLE PO R T # 4 2.E S C D # 2 => P O R T #A F.E S C D # 1 U N B LO C K AF

Due to space constraints, Figure 43 uses further abbreviation of the actions.
8.3 Sorting phase actions

As a logical consequence of the order in which the Phase Perform Worksheet is
completed following the instructions in the preceding section, no logical ordering
is required of the actions. All prerequisite actions will precede subsequently
dependent actions.

8.4 ESCD Phase Perform Summary Table
The ESCD Phase Perform Summary Table (see Figure 44) maps directly across
the ESCON Director Impact Analysis Worksheet and provides a summary of
actions that need to be performed during the installation of a FICON Bridge card.
This summary chart follows the detailed instructions and allows the necessary
actions to be performed for each column at a glance.
A B C D E F G H
ESCON FICON PROCESSOR PORT ESCON PORTS FREED PORT PORT
DIRECTOR BRIDGE CHPID ADDRESS PORTS BY CONNECTIONS CONNECTIONS
IDENTIFIER PORT NUMBER RANGE INUSE BUT ESCON-FICON RELOCATIONS RELOCATIONS
ADDRESS ASSIGNED TO DISPLACED CHANNEL OLD=>NEW OLD=> NEW
FICON BY AGGREGATION SAME DIRECTOR DIFFERENT
BRIDGE FICON DIRECTOR
BRIDGE
DEFINITION CONNECT EDIT MOVE PORT MOVEPORT

CHPID<C> PORT<B> (TONEW ESCD)
PORT<B> ESCD<A>
ESCD<A>
VARY OFF BLOCK BLOCK PORT BLOCK PORTS BLOCKPORT

PORT (OLD& NEW) (OLD& NEW)
HARDWARE IF NOT REMOVE MOVE CABLES MOVE CABLES

ACTIONS EMPTY: CABLE +CARD (TONEWESCD)
REMOVE
CARD+
CABLE
IFREUSING
MULTI
MODE
FIBRE:
INSTALL
M/CCABLE
INSTALLFB
VARYON UNBLOCK UNBLOCK PORT UNBLOCK

PORT<B> (NEWs) (NEW)
ESCD<A>
Figure 44. ESCON Phase Perform Summary Table

Chapter 9. Pre-phase insertion
The actions within a phase must be evaluated to see if they will cause a required
resource to become unavailable. In the case of a four-path device, all of its paths
may be affected in the one phase. If the resource were critical, then some of the
actions affecting its paths will have to be placed in a preceding phase. This may
be an existing phase or a new one that is inserted into the sequence.
This chapter provides a procedure to evaluate any phase to determine if a

pre-phase action is required. The information for determining a pre-phase action
will come from the Phase Planning Worksheet, the ESCON Director Worksheet,
and the customer’s design. It is important that the pre-phase action be completed
before proceeding to the phase action.
For example, four FICON channels are to be installed and they will be used to
provide access to a new DASD string. For simplicity, assume the required CHPID
numbers FC, F8, FD, and F9, and I/O slots 31, 06, 32, and 07 are free. There will
be no impact to existing CHPIDs or devices and the ESCDs to be used already
have the FICON Bridge cards installed. The FICON channels can simply be
added to the processor; in this case, it can all be achieved in the one IODF
activation.
Taking the same example but changing it so that the four FICON channels are
now to provide access to an existing DASD string that contains a 24 x 7
production database and an availability issue arises: the FICON channels will
provide the only four paths to the DASD. If all four FICON channels were installed
in the same phase, then application access to the database would be lost.
Therefore, it will be necessary to split the installation of these four FICON
channels back into separate phases. It may be possble to use just two phases if
the loss of two paths at a time is acceptable, or it may be necessary to use four
phases.
9.1 Phase evaluation procedure

The thing to look at is the elements that will be taken offline. If all paths to a
device are taken off, then access to that device is lost. It must then be determined
if there is required application data or function on that device.
Only the vary off actions for the phase need be analyzed. After all these actions
have been performed, the resources or elements will then be unavailable. It is
when all paths to a device are lost that the device is effectively taken offline.
It is when a device is taken offline that an availability problem may arise. For
example, when DASD are taken offline their data is no longer available. So there
is a two-stage test. The first is to determine what devices will be taken offline. The
second is to determine if the devices contain any data or function that is required.
A configuration diagram for the current configuration, or IOCP statements

produced by HCD, will be needed to assess paths to devices and help identify
when all paths will be taken off to a device. As each vary off action is analyzed,
the path can be checked off on the configuration diagram. After all these actions
have been analyzed in this way, it should then be apparent where devices have
lost all paths.

The second stage is to then identify the data or function of these devices and
assess whether it is critical. An alternative approach would be to clearly have
identified devices which are critical to maintaining application availability by the
customer. Then with this list, simply check if any of the devices that will be lost
during the phase are on the “critical” device list.

Chapter 10. Phase merging
In this chapter, all phases (phases and prerequisite phases) are evaluated to see
if they must be executed separately or can be merged to reduce the number of
installation phases. Can some phases be performed together, that is, can they be
implemented in the same IODF activation?
While it may be possible to merge some phases, it will never be possible to

merge two phases that are not consecutive.To do so would change the sequence
of the phases, which cannot be done because the installation sequence is fixed
due to the plugging rules (the way in which the I/O slots must be used) and the
CHPID number assignment algorithm. So only consecutive phases may be
merged.
It is best to avoid attempting to merge phases unless there is some requirement

to reduce the number of phases used. The amount of work for the return gained
may prove to be of little value. When a phase can be merged with another, the
saving is an IODF activate, which in the scheme of things, is a small timesaving.
The amount of work for definition, hardware and vary actions will remain the
same. In addition, the benefit of smaller incremental changes that can be
checked and verified during the progress of the transition is lost. Therefore, it is
recommended unless there is a good reason, do not attempt to merge phases.
10.1 Analysis of phase contents

Pre-phases cannot be merged with the phase of which they are a pre-phase.
They became pre-phases for some reason.
Availability of business-critical application resources is to be maintained. It is this

criteria which is to be used to evaluate whether a phase can be merged with
another. The actions of the two phases to be merged must be combined and then
investigated to see if their combination will make unavailable some required
application resource.
By combining phases, the net effect is to increase the number of elements that
will be taken offline, which increases the probability that access to a required
resource will be lost.
Keep the following points in moind when considering phase merging:

1. Looking along the total sequence of phases, only phases of the same type
(FCV inst. phases or pre-phases) can be merged because merging of different
phase types will break the sequence rule.
2. A phase can only be merged to a preceding phase of same type. There is only
one exception: a pre-phase can be merged with the preceding FCV-phase if
possible.
3. Again, the customer’s availability requirements must be maintained during
merge analysis.
4. The given sequence of phases should now be investigated if there are
possibilities to put consecutive phases of the same type together in one
execution sequence.

5. If there is an entry in a phase in the Bridge line at column E and F of the
Phase Worksheet, the corresponding line in ESCON Director Impact Analysis
must also be reviewed. If there are Port entries in column G for the
corresponding Phase Worksheet Bridge line entry, these must also be covered
by merge analysis.
6. If a phase will only add cards either in the processor and/or ESCD and has no
pre-phase, it can be merged with a preceding phase of the same type.
Example: Assume a customer has a three-cage 9672 G5 that is fully
populated and has free ESCD slots for FICON Bridge cards. This customer
wants to install 12 FCV cards.
In this case, phase 3 can be merged with phase 2. Phases 5 and 6 can also be
merged with phase 4 because in both cases, merged phases only contain card
installations.
7. If adding only an FCV phase with an ESCD Bridge card installation as a
pre-phase that was merged to a pre-phase before, this FCV phase can be
merged to the preceding FCV phase.

Part 4. Installation
This part of the book describes the actual installation phase.
Installation
I/O Definition
Resources Resources Resources
HCD/HCM
IODF In-use Not In-use In-use
HCM Varies and Deletes, Moves, Adds Varies and

Move Port Config Off Recable Config On
Aggregate Verify
Convert
Activate
One Implementation Phase (or pre-phase or merged phases)
Figure 45. Installation instructions and actions

Chapter 11. Executing the install actions
In this chapter the actions in the Phase Perform Worksheets will be interpreted
and executed. The actions have been written in a concise and abbreviated form
that will provide the necessary instructions to allow for correct implementation
regardless of whether the recommended software is available. HCM and ESCM
(now replaced by SA/390 IOOPS) are recommended for large sites, from a
manageability and operational viewpoint. The necessary software, of course,
must be available and meet requisite levels of maintenance.
INSTALL TIMELINE DIAGRAM GOES HERE
11.1 Executing processor actions

The following describes the actions that are to be performed on the processor
side and discuss at a general level how they are performed and their intention. It
is expected that the reader is familiar with use of HCD or HCM and the MVS
system commands used.
11.1.1 Definition actions

These actions require the use of HCD or HCM, and will make the required I/O
configuration changes.
11.1.1.1 ADD CHPID(xx[-yy|,yy,zz,...]) TYPE=aa

This is to add definitions for a CHPID, a range of CHPIDs, or a list of CHPIDs.
Whether HCM or HCD is used, adding a CHPID to a processor is a

straightforward procedure.
11.1.1.2 ADD CU#=>CHPID(xx)

This indicates that there are devices and control unit definitions required to be
defined and connected to a CHPID.
Again, whether HCM or HCD is used, adding the devices and their control unit
and then connecting to the CHPID indicated will be straightforward.
11.1.1.3 AGGR CHPID(xx[-yy|,yy,zz,..])=>CHPID(aa)

The CHPID, or range, or list of CHPIDs is to be aggregated to the single CHPID
“aa”. In essence, the control units and devices attached to the old CHPID are
moved to the new CHPID.
When using HCM or HCD the aggregate function can be used to aggregate
CHPIDs to other CHPIDs that are connected to the same ESCD. The difference is
that HCM will allow more than one source CHPID to be aggregated to a target
CHPID, whereas HCD will only allow it to be done one at a time.
If the target and source CHPIDs are not connected to the same ESCD, then the
task becomes a more manually-intensive one. The control units and devices will
need to be connected to the new ESCD and then to the target CHPID.

11.1.1.4 AGGR SAVED(xx[-yy|,yy,zz,..])=>CHPID(aa)
This indicates that the source CHPIDs no longer exist and had to be saved,
temporarily, before reassignment or aggregation in a later phase. The control unit
and devices on the saved CHPID will need to be connected to the target CHPID
via the ESCD to which it is connected.
The exact manner in which the CUs connected to a CHPID may be saved can
vary. If fortunate, a CHPID might be aggregated to “spare” CHPID, or at worst,
the information recorded on paper.
11.1.1.5 CHANGE OSA CONFIG CHPID(xx)=>CHPID(yy)

This action is used when the CHPID being moved or reassigned is an OSA
CHPID type. The OSA Configuration Manager must be used to change the
configuration, and also to implement it. See the ACTIVATE NOINSTALL action in
11.1.4, “Vary On actions” on page 83.
11.1.1.6 DELETE CHPID(xx[-yy|,yy,zz,...])

The CHPID, or range, or list of CHPIDs is to be deleted. This is achieved easily
by either HCM or HCD.
11.1.1.7 SAVE CUs:CHPID(xx[-yy|,yy,zz,..])

The CHPID, or range, or list of CHPIDs will be deleted in the phase and will not
be reassigned until a subsequent phase. This action is to save the CHPID-to-CU
connection information for later use, so that a deferred aggregation or CHPID
reassignment may take place.
The exact manner in which the CUs connected to a CHPID may be saved can
vary. If fortunate, a CHPID might be aggregated to spare CHPID, or at worst, the
information recorded on paper.
11.1.2 Vary Off actions

11.1.2.1 CF CHPID(xx[-yy|,yy,zz,..]) OFF
Configure off the CHPID, or range, or list of CHPIDs using the MVS CONFIG
command. This will need to be performed on all LPARs to which the CHPID is
shared.
11.1.3 Hardware actions

11.1.3.1 INSTALL CARD+CABLE@<frame/slot>
This action is to install a FICON channel card and cable into the frame and I/O
slot specified.
11.1.3.2 INSTALL CU# CABLE=>CHP(xx)

This action is used when new devices and control units are also being installed
(or have been), and are to be connected to the CHPID specified. The customer’s
design will specify which devices and control unit are to be attached to which
CHPID and through which ESCD and port.
11.1.3.3 MOVE CABLE+CARD CHP(xx)=>CHP(yy)

This action is to REASSIGN a CHPID to a new CHPID number. The cable and
card are removed from one CHPID location in the processor and relocated to the
new location for the new CHPID number. This will be in the case of
ESCON-to-ESCON channel moves.

11.1.3.4 REMOVE CABLE+CARD@<frame/slot>
This action is to remove a CHPID from the processor. The CHPID in definition
terms is deleted.
11.1.4 Vary On actions

11.1.4.1 ACTIVATE NOINSTALL
This action is performed using the OSA Configuration Manager. This is to be
executed once the OSA CHPID is configured online, after the IODF activation for
the phase. This action is related to the CONFIGURE command of the CHPID
immediately above it on the Phase Perform Worksheet.
11.1.4.2 CF CHPID(xx[-yy|,yy,zz,..]) ON
Configure on the CHPID, or range, or list of CHPIDs using the MVS CONFIG
command. This will need to be performed on all LPARs to which the CHPID is
shared.
11.2 Executing ESCD actions

The following describes the actions that are to be performed down at an ESCD
and discusses at a general level how they are performed and their intention. It is
assumed that the reader is familiar with use of HCD or HCM, the MVS system
commands and the ESCM commands used.
11.2.1 Definition actions

11.2.1.1 CONNECT CHPID(xx)=>PORT#yy.ESCD#zz
This action connects the specified CHPID to the port and ESCD specified. That
is, it defines a new FICON CHPID as being connected to a bridge port of an
ESCD. Using either HCM or HCD this is trivial, but before this can be done the
port will need to be converted.
11.2.1.2 CONVERT PORT#yy.ESCD#zz

This will convert a port in an ESCD to a FICON Bridge port.
An alternative, is to uninstall and install the port.???
11.2.1.3 EDIT PORT#xx.ESCD#yy.CHPID#zz.<procid>

This action is optional, but recommended. This is not a definition in the IODF; that
is, this action is not performed using HCM or HCD.
From the ESCD console EDIT PORT NAME with information on the processor,
CHPID, and channel type.
Ex.: 9672_xxx _CHPID_yy_FCV
11.2.1.4 MOVE PORT#xx.ESCD#yy=>PORT#zz

This action will bring about the definition changes to change the port through
which a CHPID connects to a CU, or the port through which a CU is attached to a
CHPID.
The intention is to only change the port within the same ESCD through which the
CU or CHPID is connected; ultimately it will maintain the paths between the
CHPID and the devices.
Chapter 11. Executing the install actions 83

HCM’s move port utility is recommended for this activity. The equivalent can be
achieved using HCD, but more work is required; you must manually disconnect
the port from either the CHPID or CU and then connect the new port to the
CHPID or CU.
11.2.1.5 MOVE PORT#ww.ESCD#xx=>PORT#yy.ESCD#zz

This action will bring about the definition changes to change the port and ESCD
through which a CHPID connects to a control unit and its devices, or the port and
ESCD through which a CU is attached to a CHPID.
The intention is to only change the port and ESCD through which the CHPID is
connected; ultimately it will maintain the paths between the CHPID and the
devices.
HCM’s move port utility is recommended for this activity. The equivalent can be
achieved using HCD, but more work is required; you must manually disconnect
the port from either the CHPID or CU and then connect the new port to the
CHPID or CU.
11.2.2 Vary Off actions

11.2.2.1 BLOCK PORT#xx.ESCD#yy
This action will cause the paths to devices to be varied off, and the port to be
blocked, to prevent use and error conditions due to loss of light while hardware
actions are being performed.
Using the ESCM command F IHV,B port# switch# the appropriate commands
will be issued for all the device paths on all LPARs that are routed through this
port.
If ESCM is not installed, then VARY PATH(chp,dev),OFFLINE commands need

to be issued for every device path on all LPARs that use the port, and then the
port must be blocked from the ESCD console.
11.2.3 Hardware actions

11.2.3.1 INSTALL FB+CABLE PORT#xx.ESCD#yy
This action is to install the FICON Bridge card in the port and ESCD specified.
11.2.3.2 MOVE CABLE+CARD PORT#ww.ESCD#xx=>PORT#yy

This action is to move a cable and card from one port to another port on the same
ESCD. This hardware action is related to the MOVE PORT definition action
above.
11.2.3.3 MOVE CABLE+CARD PORT#ww.ESCD#xx=>PORT#yy.ESCD#zz

This action is to move a cable and card from one port to another port on a
different ESCD. This hardware action is related to the MOVE PORT definition
above where both the port and ESCD are changed.
11.2.3.4 REMOVE CABLE+CARD PORT#xx.ESCD#yy

This action is to remove the cable and card for a port that will no longer be used.

11.2.4 Vary On actions
11.2.4.1 UNBLOCK PORT#xx.ESCD#yy
This action will cause the paths to devices to be varied on, and the port to be
unblocked, to allow use after the hardware actions have been performed and the
new IODF for the phase has been activated.
Using the ESCM command F IHV,U port# switch# the appropriate commands
will be issued for all the device paths on all LPARs that are routed through this
port.
If ESCM is not installed then VARY PATH(chp,dev),ONLINE commands need to

be issued for every device path on all LPARs that use the port after the port has
been unblocked from the ESCD console.
Chapter 11. Executing the install actions 85

Part 5. Post-Installation

Chapter 12. FICON post-install
This chapter covers the post-installation tasks and procedures. The tasks that
were performed during installation of FICON need to be verified and performance
of the FICON channels needs to be measured.
12.1 Verification procedure

The best form of verification of the new FICON installation and subsequent
aggregation of ESCON channels to FICON channels is to see successful I/O to
the devices concerned. Simple procedures can be devised for the various
devices. The quickest and easiest is an ISPF option 3.4 volume listing, in the
case of DASD, of the volume behind the control unit which has had a path
changed from an ESCON channel to a FICON channel. Only one volume needs
to be listed to show that access is available to devices on the control unit through
the FICON channel. In order to be certain the I/O was processed down the
“FICON path” it will be necessary to vary other paths offline for the device
chosen.
While successful I/O is the best way to verify, the first thing to look for is an
absence of message IOS291I RC21. If this message is displayed, it indicates a
cable (or cables) have been misplugged. If this does occur, see 12.3, “Problem
diagnosis” on page 95.
By displaying the devices behind the control units that now have a path with a
FICON channel, it can be seen whether the path is online, the channel is
physically online, and the path is operational. Likewise, the CHPID can be
displayed to see its status with respect to each device on it. Use the following
commands.
D M=DEV(2500)
D M=CHP(9A)
Displaying the device using the display unit command is of little value as this will
indicate little about the path status, only whether the device is online or not. In the
case of DASD a DEVSERV command can indicate path status as well as cause
I/O to the control unit. However, which path the I/O will use cannot be controlled
among the available paths. It can only be forced down a particular path by taking
all other paths away.
DS P,2500,1 for example, the DEVSERV command
Whether an ISPF volume listing (option 3.4) or a DEVSERV command is chosen

to cause I/O down the FICON path, it may not be feasible to take all other paths
away. However, using an RMF Monitor II Channel Activity display, the FICON
channels can be monitored for activity. Sooner or later I/O will occur on the
FICON channel and it will be seen in the Channel Activity display. This should
also show up on the RMF Monitor I Channel Activity Report. Activity indicated by
either of these reports will indicate successful I/O through FICON channels.
Provided there are no error messages for the times I/O is going down a FICON
channel, it can be concluded I/O was successful.

12.2 Measurements
At OS/390 V2R7, RMF has enhancements to report on FICON channels.
Changes are made to the RMF Monitor I and RMF Monitor II Channel Activity
reports which provide more details on FICON channel performance.
12.2.1 Channel Path Measurement Facility (CPMF) Modes

There are two Channel Path Measurement Facility (CPMF) modes: Compatibility
mode and Extended mode, which provide the new measurements for FICON
channels (that is, for the FC channel type only). The support for this is available
in the base code for OS/390 V2R7 RMF. For prior levels of RMF, support will be
provided by PTF, as will be the case for OS/390 as far back as V1R3. Check the
PSP for 9672DEVICE and the subset 9672MVS/ESA.
APAR OW35586 provides the required support for these new CPMF modes.
12.2.1.1 SYS1.PARMLIB(IEAOPTxx)
There is a new Channel Path Measurement Facility (CPMF) option which allows
for two modes of measurement. Extended mode will enable RMF to provide
extended channel measurements for FICON channels. Compatibility mode will
not report the new measurements.
1. New entry: CPMF=COMPAT/EXTENDED
2. Activate using SET OPT=xx
12.2.1.2 Compatibility mode

This is the default mode. FICON channels are still reported upon, but only to the
same level of detail as other channel types; see Figure 46 and Figure 47 on page
91.
RMF 2.7.0 Channel Path Activity Line 1 of 12
Samples: 100 System: SYS1 Date: 07/22/98 Time: 15.55.00 Range: 120 Sec
Channel Path Utilization(%)

ID Type SHR Partition Total
80 CNC_S Y 0.00 0.00

83 BLOCK 0.00 0.00
96 BLOCK 0.00 0.00
B8 CNC_S Y 0.00 0.00
D9 CNC_S Y 0.00 0.00
DB CVC_P Y 1.43 25.00
FC FCV Y 2.56 0.00
FD FCV Y 4.02 25.00
Figure 46. RMF Monitor II Channel Path Activity Report with CPMF=COMPAT

CHANNEL PATH ACTI VI TY
OS/390 SYSTEM ID MVSA DATE 03/08/1998 INTERVAL 10.01.799

REL 02.07.00 RPT VERSION 2.7.0 TIME 12.55.05 CYCLE 0.333 SECONDS
IODF = 12 CR-DATE: 03/01/98 CR-TIME: 10.23.17 ACT: POR MODE: LPAR CPMF: COMPATIBILITY
CHANNEL PATH UTILIZATION(%) CHANNEL PATH UTILIZATION(%) CHANNEL PATH UTILIZATION(%)

ID TYPE SHR PARTITION TOTAL ID TYPE SHR PARTITION TOTAL ID TYPE SHR PARTITION TOTAL
00 BLOCK OFFLINE 08 BLOCK OFFLINE 10 BLOCK OFFLINE

01 BLOCK OFFLINE 09 BLOCK OFFLINE 11 BLOCK OFFLINE
02 BLOCK OFFLINE 0A BLOCK OFFLINE 12 BLOCK OFFLINE
03 BLOCK 0.33 0B BLOCK OFFLINE 13 BLOCK OFFLINE
04 BLOCK OFFLINE 0C BLOCK OFFLINE 14 BLOCK OFFLINE
05 BLOCK OFFLINE 0D BLOCK 0.00 15 BLOCK OFFLINE
06 BLOCK OFFLINE 0E BLOCK OFFLINE 16 BLOCK 0.00
07 BLOCK OFFLINE 0F BLOCK OFFLINE 17 BLOCK 0.00
18 CNC_S 0.00 20 CNC_S OFFLINE 28 CNC_S OFFLINE
.
.
FC FCV Y 9.25 11.25 FD FCV Y 9.50 11.50
Figure 47. RMF Monitor I Channel Path Activity Report with CPMF=COMPAT
12.2.1.3 Extended mode

In this mode not only is the channel utilization given for FICON channels, but also
the MB/SEC transfer rate for READ and WRITE in total and per LPAR (if in LPAR
mode). The measurement of the data transfer rate allows better performance
monitoring, analysis and capacity planning.
RMF 2.7.0 CHANNEL PATH ACTIVITY LINE 1 of 12
SAMPLES: 100 SYSTEM: SYS1 Date: 07/22/98 TIME: 15.55.00 RANGE: 120 SEC
CHANNEL PATH UTILIZATION(%) READ (MB/SEC) WRITE(MB/SEC)

ID TYPE SHR PART TOTAL BUS PART TOTAL PART TOTAL
80 CNC_S Y 0.00 0.00
83 BLOCK 0.00 0.00

96 BLOCK 0.00 0.00
B8 CNC_S Y 0.00 0.00
D9 CNC_S Y 0.00 0.00 1 2 3
DB CVC_P Y 1.43 25.00
FC FCV Y 2.56 0.00 5.00 20.00 20.00 40.00 40.00
FD FCV Y 4.02 25.00 28.00 10.00 10.00 35.00 45.00
Figure 48. RMF Monitor II Channel Path Activity Report with CPMF=EXTENDED
Chapter 12. FICON post-install 91

Figure 48 on page 91 shows the new fields in the Channel Path Activity report for
RMF Monitor II. Those fields are:
1. Channel path utilization for FICON is now a measure of how busy the channel
processor is, rather than time the actual channel is busy with frames; BUS is
the utilization of the internal PCI bus.
2. Megabytes per second read for the partition and for the total complex.
3. Megabytes per second written for the partition and for the total complex.
CHA NNE L P A TH A CTI V I TY
OS/390 SYSTEM ID MVSA DATE 03/08/1998 INTERVAL 10.01.799

REL 02.07.00 RPT VERSION 2.7.0 TIME 12.55.05 CYCLE 0.333 SECONDS
IODF = 12 CR-DATE: 03/01/98 CR-TIME: 10.23.17 ACT: POR MODE: LPAR CPMF: EXTENDED
CHANNEL PATH UTILIZATION(%) READ(MB/SEC) WRITE(MB/SEC) CHANNEL PATH UTILIZATION(%) READ(MB/SEC) WRITE
ID TYPE SHR PART TOTAL BUS PART TOTAL PART TOTAL ID TYPE SHR PART TOTAL BUS PART TOTAL PART
00 CNC_S OFFLINE 08 CNC_S OFFLINE

01 CNC_S OFFLINE 09 CNC_S OFFLINE
02 CNC_S OFFLINE 0A CNC_S OFFLINE
03 CNC_S Y 20.00 50.00 0B BLOCK OFFLINE
04 CNC_S OFFLINE 0C CNC_S OFFLINE
05 CNC_S OFFLINE 0D CNC_S Y 20.00 25.00
06 CNC_S OFFLINE 1 2 3 0E CNC_S OFFLINE
07 CNC_S Y 15.00 31.00 0F CNC_S OFFLINE
.
.
FC FCV Y 9.25 11.25 41.00 11.00 22.00 1.00 1.00 FD FCV Y 9.50 11.50 40.00 7.00 7.00 2.00
FE FCV Y 9.25 11.25 41.00 11.00 22.00 1.00 1.00 FF FCV Y 9.50 11.50 40.00 7.00 7.00 2.00
Figure 49. RMF Monitor I Channel Path Activity Report with CPMF=EXTENDED
Figure 49 shows the new fields in the Channel Path Activity report for RMF
Monitor I. Those fields are:
1. Channel path utilization for FICON is now a measure of how busy the channel
processor is, rather than time the actual channel is busy with frames; BUS is
the utilization of the internal PCI bus.
2. Megabytes per second read for the partition and for the total complex.
3. Megabytes per second written for the partition and for the total complex.
The new measurements are contained in SMF record type 79(13). The new fields
described in the Channel Path Measurement Block (CPMB) are described by the
IRACPMB mapping macro.
12.2.2 Capacity planning and performance monitoring

Through the use of RMF, measurements for the channels are reported which can
be used for both the purposes of capacity planning and performance monitoring.
12.2.2.1 Capacity Planning

In a controlled engineering environment, the aggregate read/write data transfer
rate was measured at 68 MB/sec full duplex. In the same environment, the
read-only rate was 60 MB/sec. Channel utilization could not be driven to 100%
due to bottlenecks in other areas in the I/O process. In any event, these
maximums still represent the most the channel can be utilized in terms of data
transfer rate.

ESCON channels for DASD in a controlled engineering environment have been
measured at 100% utilization yielding a 9.8 MB/sec transfer rate. Using this
information, an estimate may be made of the data transfer rate of an ESCON
channel. For example, the estimated data transfer rate for an ESCON channel
that has 40% utilization would be 3.92 MB/sec.
Using these numbers, it can be estimated whether a FICON channel has capacity
for more ESCON channels to be aggregated to it. By calculating an estimate for
the data transfer rate being achieved for an ESCON channel, you may then see if
there is further capacity on the FICON channel to aggregate a particular ESCON
channel.
By observing what the transfer rate for a FICON channel is, both before and after
aggregating an ESCON channel, the actual change in data transfer rate can be
compared with the estimated change in data transfer rate. Thus, further estimates
may be refined.
12.2.2.2 Performance monitoring

An essential ingredient in performance monitoring is understanding the
components of response time. Because of the change in the way a FICON
channel works, the components of response time have changed. Due to CCW
pipelining, there will be fewer channel ends and device ends. For devices there is
now a device active only (DAO) field in the channel measurement block (CMB).
This field captures time which previously had to be calculated by device support
code and was included in disconnect time by RMF, but only for DASD. Loosely
described, this is the time between test subchannels (TSCHs) for primary and
secondary status, or alternatively, the difference in time between a channel end
and device end, where they don’t occur together. So the components of DASD
response time are:
• Queue Time
• Pend Time
• Connect Time
• Disconnect Time
• Device Active Only Time (RMF includes this as part of disconnect time but it is
reported in SMF record type 42)
The other component’s meanings remain the same.
12.2.2.3 Device Active Only (DAO) measurement

As mentioned, DAO is that portion of time in an I/O between which a channel end
is received and a device end is received.

SCSW Fields - FC/AC/SC
SSCH TSCH
4400 40C0 4007 0000 CMB
SSCH SAMPC
CONNECT
DIS-
PEND CONNECT CONNECT CONNECT PENDING
DISCONNECT
CE/DE
CU QUEUE
DAO
RESERVED
SCSW Fields - FC/AC/SC

RESERVED
*
SSCH TSCH TSCH
4400 40C0 4045 0040 0003 0000
* Items stored in CMB
at status pending time
DIS-
PEND CONNECT CONNECT CONNECT DAO
* * * * CE
* DE
Figure 50. I/O showing Device Active Only (DAO) time
Figure 50 shows two I/Os on a timeline. The first SSCH has no DAO time, as
channel end (CE) and device end (DE) are presented at the same time. The
second SSCH shows DAO as the device end is presented separated from the
channel end. The figure also shows the fields in the Channel Measurement Block
(CMB) where the Channel SubSystem (CSS) stores the measurements.

RMF
Device Activity
CMB
PEND DISC CONN
TIME TIME TIME
SSCH SAMPC
0.0 0.0 0.0
CONNECT 0.0 0.8 9.6
0.0 0.0 0.0
PENDING 0.0 0.0 0.0
DISCONNECT
+
CU QUEUE
DAO
RESERVED
SMF Record Type 42
RESERVED
Figure 51. DAO Measurement Reporting
Figure 51 shows how DAO measurements are reported. In RMF Monitor I and
Monitor II Device Activity Reports, DAO is included in the DISC TIME. This used
to be done in the past, but through a different method. Device support software
had to calculate the DAO; however, this was only done for DASD. DAO is
recorded in SMF record type 42, which can be extracted to obtain it. The DAO
measurement is recorded in subtypes 5 and 6. For subtype 5, the fields are
S42SCDAO, S42VDDAO, S42VXDAO, and S42VVDAO. For subtype 6, the field
is S42DSDAO.
12.3 Problem diagnosis

A number of different error types are covered in this section that can be related to
FICON. That is, they could occur in ESCON configurations, but the intention is to
only deal within a FICON setting.
Errors will be most likely indicated by an MVS error message. The message
explanation in the appropriate message manual will give a partial understanding
of the type of problem and what the remedy may be. Notwithstanding that an
error message is the most likely indication, there are other error indicators and
they are also discussed here.
12.3.1 Error types

After implementing FICON and experiencing the complexity of the procedures
and steps involved, it can be easily seen that there is opportunity for error. The
following list is not exhaustive but covers the likely errors that may arise.

1. Sequence errors
2. Cabling errors
3. Configuration definition errors
4. Director errors
5. Activation errors
6. Software prereq errors
Cabling errors and sequence errors potentially may cause the most obscure and
unpredictable results. The sequence for installation of FICON cards in the
processor is fixed due to plugging rules and the machine’s algorithm for CHPID
assignment. If this is not strictly adhered to, CHPIDs may be reassigned after a
power-on reset, which will then mean the cables will be in the wrong cards and
there will be a configuration mismatch. Recabling would be required to follow the
CHPID to the new FICON card to which it was reassigned.
While the sequence for installation of FICON cards is fixed due to the plugging
rules, this same kind of rigidity is not imposed over tasks covering freeing of
switch ports and reassignment of CHPIDs or ports.This might make it more likely
that a sequence error may occur. In any event, the sequence will be part of the
implementation sequence plan; if the sequence is wrong here, then it will be a
planning error. If the plan was executed wrongly then it will be an operational
error. No matter how the sequence error occurs, it needs to be understood at
what point tasks were performed out of sequence and why, to prevent a repetition
and to speed a backout if required.
Configuration definition errors will lead to a configuration mismatch in the same

way that a misplugged cable will. That is, the active definition of the configuration
will not match the physical configuration as cabled.
Director or switch error refers to the blocking of a port before all the required
paths have been varied offline and where a cable is pulled from a port before it
has been blocked. So long as it is the correct port or cable, the impact could
simply be annoying error messages and not the loss of a required resource,
although it may cause the failure of an already active I/O. The impact of this I/O
failure could range from triggering a successful recovery to causing the
termination of an application. Naturally, this type of error is to be avoided but if it
does occur it should not necessarily mean a backout as the application should be
restartable.
Activation errors lead to something like a configuration mismatch either by

activation of the wrong IODF or not correctly doing the activation on all the
required images.
Software prerequisite errors could perhaps occur because required APARs (in the
case of IBM software) or fixes (in the case of vendor code) have not been applied
or have been incorrectly applied. At OS/390 V2.7, FICON support is built into the
base level of the code and PTFs will be required to add FICON support for lower
levels of OS/390 back to V1.3. If the IBM software does not have the required
code to support FICON, the errors are unpredictable, but a backout will be
required.

Vendor code should be a different matter. This will be restricted only to code that
makes use of the PCI bit in channel programming to get control back so the
channel program can be modified (usually by chaining more CCWs). The number
of vendor products that do this is small, but the impact would be that the channel
program ends before the application program can add more CCWs and thus end
prematurely, forcing all the overhead of a SSCH again. The net effect will likely be
a noticeable extension of elapsed time for the application.
12.3.2 Error indicators

When errors do occur, there will usually be a number of different indications.
When looking at individual indications, it will be important to bear in mind that
there are other indications or symptoms which must be considered altogether.
This allows a better picture of the problem to be formed and will help hypothesize
a cause which can be specifically tested as part of the problem analysis.
12.3.2.1 Messages
The first sign of trouble may be indicated by IOS messages once I/O is actually
tried down a FICON path. Generally, the explanations and actions should be
followed as indicated in the message manuals. Other symptoms will usually
accompany the messages, for example, programs ending with bad return codes
or system abend codes. It is important to look at all the symptoms presented in
their entirety to get to the cause of the problem.
12.3.2.2 I/O contention

I/O contention may be indicated by RMF in the Device Activity Report, combined
with the I/O activity report. More immediately, however, it may be experienced by
end users as slow response, or as a slowdown in throughput, and may be
accompanied by I/O-related messages. The first place to look would be in the
SYSLOG for any I/O-related messages and any messages involving the FICON
CHPIDs and any connected devices. For example, there may be start pendings
(IOS071I messages) for the device.
The objective is to narrow down the scope of the impact or of the contention. Is it
channel wide? Or is it restricted only to specific devices? Historical performance
data can help here, as FICON installation will not help with specific device
contention as paths within the control unit will be the bottleneck.
It is recommended for performance problems that the general approach outlined

in OS/390 RMF Performance Management Guide, SC28-1951 Chapters 2 and 5
be followed.
12.3.2.3 Unexpected channel utilizations (RMF)

Depending on how many ESCON channels have been aggregated to a FICON
channel, the expected channel utilization will vary. Channel utilization alone is not
a good indication of performance even with ESCON channels, and this continues
to be the case with FICON and possibly more so. Measurements of data transfer
rates have not been at 100% channel utilization as other factors come into play
and the bottlenecks occur elsewhere, preventing 100% being reached.
READ/WRITE ratios, cache miss rates, block sizes, sequential or random access
all combine to limit the effective transfer rate. In the initial stages of a FICON
implementation, however, low utilizations might be expected rather than high. Any

high utilizations at an early implementation phase would need to be investigated
to ensure that there is no problem.
12.3.2.4 Unexpected I/O errors

I/O errors may manifest in the form of unexpected output, channel program
checks and/or bad return codes and system codes. These errors need to be
identified as having occurred down a FICON channel path. This may be
confirmed by other symptoms, most likely being a message in SYSLOG. If no
other path identifying symptoms are present but a dump is, it may be examined to
locate the UCB for the device and inspecting the last path used mask (LPUM) to
confirm what path was used. The IPCS command IOSCHECK ACTVUCBS will
list UCBs with active I/O at the time of the dump.
Even though a FICON path may have been involved in an active I/O at the time of
the error, this does not necessarily implicate FICON. Identifying the channel path
as FICON is only the first step. The error, even if I/O-related, could still be for
some other reason, regardless of the channel type used.
Unexpected output may not have any other symptom associated. In the unlikely
event of this, tracing will likely be the only option to identify the point at which the
data becomes “corrupted”. Start by tracing output and working backwards
towards the source of the data.
12.3.2.5 Some programs perform poorly

If bad performance is limited to specific devices, it is likely that it is due to some
kind of device contention. But if it is limited to specific programs regardless of
device (that is FICON connected), it is a possible PCI synchronization problem. If
these programs perform normally over ESCON channels, then it is fairly certain
that it is a PCI synchronization problem. IBM has modified IEBCOPY and
program fetch to avoid this. However, there may be either OEM software or
in-house software that modify channel programs using the PCI bit in order to
chain more CCWs for performance gains. If this is the case, a fix needs to be
ordered from the OEM vendor or changes made to any in-house programs. An
I/O trace using GTF will confirm if PCIs are taking place.
12.3.3 Diagnostic data and tools

The intention in this section is not to describe in detail the various diagnostic data
and tools available, but to make the reader aware of the existence of helpful data
and tools and some of the features useful in problem diagnosis of FICON
problems.
12.3.3.1 SYSLOG or OPERLOG

Since messages will usually be issued to the MVS console in most error
situations, they often provide good information for diagnosis. The system log (or
operlog) is a record of these messages. Nearly all diagnosis should begin with an
initial scan of the syslog. The only exceptions might be for a performance
problem where it is known that the program uses PCIs to synchronize for channel
program modification.
Figure 52 gives an example of many of the types of messages that could be

expected of errors related to channel problems.

IOS251I PATH F2 TAKEN OFFLINE FROM DEVICE 15AD
*IOS002A 0FFB,NO PATHS AVAILABLE
IOS050I CHANNEL DETECTED ERROR ON 00E3,F4,**,**04
*IOS202E CHANNEL PATH F4 FORCED OFFLINE - DEVICE IS: UNKNOWN
$HASP100 NTVMP14 ON INTRDR FROM TSU00047
IRR010I USERID MARIO IS ASSIGNED TO THIS JOB.
ICH70001I MARIO LAST ACCESS AT 13:29:44 ON THURSDAY, FEBRUARY 4, 19
$HASP373 NTVMP14 STARTED - INIT 29 - CLASS 9 - SYS S08
D M=DEV(1500)
IEE174I 13.45.54 DISPLAY M 555
DEVICE 1500 STATUS=ONLINE
CHP 18 A2 E0 0D F4 F3 F2 F0
PATH ONLINE Y Y Y N N Y Y Y
CHP PHYSICALLY ONLINE Y Y Y Y Y Y Y Y
PATH OPERATIONAL Y Y Y N Y Y Y Y
*IEA480E 0211,DASD,SERIOUS ALERT,MT=9392-3,SER=0175-X6407,REFCODE=EE12-1
43-0B56,VOLSER=/UNKN/,ID=1B,REPEATED
*CONTINUATION OF IEA480E SNS=00000610583ACF1BC583C010430B5604E5610367101
EE1205100603FE585F00
IOS050I CHANNEL DETECTED ERROR ON 04F9,F2,**,**04
IOS581E LINK FAILED REPORTING CHPID=F3 513
INCIDENT UNIT TM=009672/RX6 SER=IBM02-047658 IF=00F3 IC=00
*IOS202E CHANNEL PATH F5 FORCED OFFLINE - DEVICE IS: UNKNOWN
IOS444I DYNAMIC PATHING NOT OPERATIONAL ON PATH (15FF,F0)
IOS444I DYNAMIC PATHING NOT OPERATIONAL ON PATH (1A20,F0)
IEE754I NOT ALL PATHS BROUGHT ONLINE WITH CHP(F0)
IEE502I CHP(F0),ONLINE
IOS444I DYNAMIC PATHING NOT OPERATIONAL ON PATH (15FF,F2)
IEE754I NOT ALL PATHS BROUGHT ONLINE WITH CHP(F2)
IEE502I CHP(F2),ONLINE
IEE712I CONFIG PROCESSING COMPLETE
IEE076I CHP(F3) NOT BROUGHT ONLINE, HARDWARE FAILURE
IEE148I CHP(F3) NOT RECONFIGURED - TARGET HARDWARE ERROR
IEE712I CONFIG PROCESSING COMPLETE
IOS581E LINK FAILED REPORTING CHPID=19 862
INCIDENT UNIT TM=009032/005 SER=IBM02-040468 IF=0038 IC=03
INCIDENT UNIT LIF=3C
Figure 52. Typical error messages
In Figure 52, the CHPIDs F0 to F5 are FICON channels. This is an extract from a
test system used to simulate and create various hardware types of errors.
12.3.3.2 Display commands

The quickest way to gauge the scope of a problem is through displays of devices,
paths, and DASD subsystems using MVS and SMS display commands. ESCM
provides a number of useful displays via the MVS MODIFY command too.
The following commands will be the most helpful most frequently.
D U,,,dev,n
D M=DEV(dev)
D M=CHP(chpid)
F IHV,D D dev * (ESCM or SA/OPS required)
DS P,dev,n
12.3.3.3 RMF
RMFMON (RMF Monitor II) provides dynamic data on system performance. Of
specific interest are the channel activity, device activity and I/O queue reports.

The channel activity report contains the new channel measurements if
CPMF=EXTENDED. Examples of the new channel activity reports are shown in
Figure 48 on page 91 and Figure 49 on page 92. Examples of IOQUEUE and
device activity reports are shown in Figure 53.
RMF - IOQUEUE I/O Queuing Activity Line 1 of 30
MIG=14.4K CPU= 6/ 4 UIC=254 PFR= 0 System= SC53

Total
15:04:19 I= 43% CONT DEL Q %ALL CHPID %DP %CU

CHAN PATHS CONTROL UNITS LCU RATE LNGTH CH BUSY TAKEN BUSY BUSY
08 0CC0 0081 0.0 0.00 0.00 1.51 1.51 0.00

88 0CC0 0081 1.51 3.47 0.00
20 0CC1 0081 1.54 1.48 0.00
A4 0CC1 0081 1.50 2.02 0.00
28 0FC0 0082 0.1 0.14 0.00 4.03 20.95 0.30
A8 0FC0 0082 4.13 22.39 0.58
98 0FC1 0082 3.83 24.40 0.60
2C 0FC1 0082 4.22 20.00 0.22
A4 2000 0083 0.0 0.00 0.08 0.02 0.00 0.00
RMF - DEV Device Activity Line 1 of 30
MIG=13.4K CPU= 9/ 7 UIC=254 PFR= 0 System= SC53 Total
14:52:27 DEV ACTV RESP IOSQ ---DELAY--- PEND DISC CONN %D %D

STG GRP VOLSER NUM LCU RATE TIME TIME DPB CUB DB TIME TIME TIME UT RV I%
PMUDAS 0CC0 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
SBOX01 0CC1 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
SBOX02 0CC2 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
TOTSP1 0CC3 0081 0.006 2 0 0.0 0.0 0.0 0.4 0.0 1.2 0 0 24
SBOX07 0CC4 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
SBOX08 0CC5 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
BOOK01 0CC6 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
BOOK02 0CC7 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
RES009 0CC8 0081 0.013 6 0 0.0 0.0 0.0 0.3 0.1 6.1 0 0 24
RES010 0CC9 0081 0.000 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 24
Figure 53. RMF Monitor II IOQUEUE and Device Activity Report
RMFWDM (RMF Monitor III) specifically helps determine where delays are
occurring. Reports of interest are found in the RESOURCE option and they are
DEV, DEVR and IOQUEUE.
The RMF Monitor I reports on channel activity and I/O activity give a better
picture over time, which is helpful in quantifying the length of time over which a
problem existed.
12.3.3.4 Dumps
Where an I/O error causes an application to abend, there will generally be a
dump produced. The best dump for debugging errors of this nature will be an
SVC dump as this will contain more system related areas than an abend dump
(that is, SYSUDUMP, SYSABEND, or SYSMDUMP style dumps). If an SVC dump
is not produced in the first instance or if it is suppressed due to a SLIP command,
a re-creation will be necessary to capture one.

Of interest will be the UCBs with active I/O; these can be formatted with the
IOSCHECK ACTVUCBS command in IPCS. IPCS is used to view and format
areas of storage in a dump.
The system trace table (SYSTRACE) will also contain entries for events leading
up to and after the error. The SSCH and I/O trace entries for the failing I/O will
provide a good starting point for identifying the device and its UCB, the path it
used, the type of I/O and the response. The SSCH entry (see Figure 54) will
contain the device number, the condition code, the address of the IOSB, and the
contents of the ORB. The first word of the ORB contains the address of the UCB.
The second word of the ORB contains the flags which shows if CCW prefetch is
allowed (ORBP X’40’ in ORBFLG1), and whether synchronization control is being
used (ORBM X’02’, ORBY X’01’ in ORBFLG0). ORBY indicates synchronization
control is being used and ORBM whether synchronization on PCIs is to occur.
The I/O entry (seeFigure 54) in the system trace table will indicate the success(or
otherwise) of the I/O. There will be an I/O entry for every I/O interrupt the channel
subsystem presents to the system. This entry will indicate the device and the
UCB address, allowing it to be matched back to the SSCH entry in the system
trace table that initiated the I/O (but be aware the interrupt may be for a HSCH or
CSCH). The entry also contains the first four words of the IRB. That is, the
UNIQUE-1 field of the entry contains IRBWORD1, UNIQUE-2 contains
IRBCCWAD, UNIQUE-3 contains IRBSTAT and IRBCOUNT, and UNIQUE-4
contains IRBESW. UNIQUE-5 actually contains the UCB address. IRBWORD1
contains status and control flags, indicating the function for which this interrupt
has been received (SSCH, HSCH or CSCH) among other things, such as whether
CCW prefetch is allowed (IRBP) and whether the path is operational (IRBN).
IRBSTAT will show device and subchannel status, which will identify the cause of
the interrupt, for example a normal channel end and device end (IRBDSCE and
IRBDSDE) or a PCI (IRBSSPCI).
------------------------------------------------- SYSTEM TRACE TABLE ----------------------------------

PR ASID WU-ADDR IDENT CD/D PSW----- ADDRESS- UNIQUE-1 UNIQUE-2 UNIUE-3 PSACLHS- PSALOCAL PASD SASD
UNIQUE-4 UNIQUE-5 UNIUE-6
01 000C 00AFF090 SSCH 271 00 02 00F3E12C 00F5FDF8 00008000 00C04C30
01 000C 00AFF090 SVCR 0 070C2000 00EB19C2 00000000 00F1845F 00A08B48
01 000C 00AFF090 SVC 1 070C2000 00EB19CC 00000000 00000001 00C03340
01 000C 00AFF090 SVCR 1 070C2000 00EB19CC 80AEAF20 00000001 00C03340
01 0001 00000000 I/O 271 070E0000 00000000 00004007 00CEFE58 0C000000 00000080 00000000 0001 0001
00800010 00F5FDF8
Figure 54. System Trace Table - ORB in SSCH entry and IRB in I/O entry
The master trace table (MTRACE) will also contain buffered messages for the
console. LOGDATA will format buffered LOGREC entries.
12.3.3.5 LOGREC
As errors of a system nature occur, a record of the event will be written to
SYS1.LOGREC. A program called EREP can format LOGREC data to report on
hardware and software errors of specific types. This is very useful for correlating
software errors with hardware events or errors. An “events” report for a specific
time range will report all events that occurred for a specific time period.
Different record types may be produced by different errors and even more than
one type of record may be produced for the one error. The following keywords will

produce EREP reports that will be useful if required: EVENT, SYSEXN, and
PRINT.
EVENT produces the Event Report, while SYSEXN produces the System
Exception Report which will identify probably failing units based on the number of
temporary errors; there is a specific section on channels. PRINT needs to be
used in combination with the TYPE keyword to select the type of records to be
reported.
TYPE=C will report on channel check, channel report word and subchannel
logout records. TYPE=H will report on missing interrupt records. TYPE=S will
report on software records that are captured for system abends and other
software events.TYPE=O will report on outboard records and unit checks. To
determine when a particular type of report or record is needed, see the MVS
console messages that were produced at the time of the error. For example, the
IOS291I message will indicate that software records are produced for the error
and that in a software record report the symptom string RIDS/IOSCACDR can be
used to search upon to find the record.
12.3.3.6 GTF
GTF is a valuable tracing tool. In particular CCWs and their data can be traced
along with IO events, including PCIs. IPCS is used to view and format the trace.
Use the following trace parameters as input to GTF to trace CCWs, SSCHs, I/O
interrupts and PCI interrupts, where dev is the device number that is to be traced:
TRACE IOP,IOXP,SSCHP,PCI,CCW
IO=SSCH=dev
12.3.4 Diagnostic procedure

A general approach to diagnostic procedure is outlined here. It is not possible
give a detailed procedure that will handle any problem that may arise. This is due
to the fact that problems by their very nature arise because of unknown factors or
omissions. Problems which arise because of unknown factors are difficult to
devise procedures for beforehand. Only once the unknown factors become
known can procedures be devised to cover them with any certainty.
This procedure is a general outline for guidance. The recommendation is to follow

it and only depart from it if there is a need or good reason. This procedure will
allow you to quickly identify whether the problem is related to FICON or not. If
FICON error is eliminated, then return to “normal” problem determination and
problem source identification procedures (PD/PSI). By this it is meant to return to
whatever procedures a site may follow for PD/PSI.
1. Problem awareness
• Users complain
• Operator advises of red message
• The performance analyst notices something unusual
• and so on
2. Symptom gathering
• Message - job, channel command, path, chpid
• Abend - dump

• Hang/loop/jobs hanging - use the MVS dump command or, if no recovery,
the SADump
• Anecdotal evidence
• Slow response - get details of transaction, online system, DB or DSN,
userid
• Elongated elapsed time for job - get jobname, JCL, DSNs, devices
3. Collect diagnostic data
• Syslog - for other messages
• Displays of devices, CHPIDs, paths and switches if already identified
• Dump - use the MVS DUMP command, or set a SLIP, or take an SA dump if
the system is unrecoverable
• Traces - use GTF trace if the need is determined after some analysis
• EREP - again, use the “events” report if the need is determined after initial
analysis
4. Analyze diagnostic data and symptoms
• Identify channel path used in I/O from messages in syslog.
• Dump - IOSCHECK ACTVUCBS get to device involved and path.
• EREP- software errors correlated to device errors by time.
• GTF Trace - does PCI show for FICON device? Does data change?
• Is the error I/O-related? If yes, continue; if no, do “normal” PD/PSI.
• Was a FICON path used? yes, continue; if no, do “normal” PD/PSI; if you
can’t tell, go to Step 3 to collect more diagnostic data.
5. FICON path identified
• Is the problem re-creatable on FICON? If yes, continue.
• Is the problem re-creatable on ESCON? If yes, do “normal” PD/PSI; if no,
continue.
• Messages - what actions do they indicate?
• Abend - continue with “normal” PD/PSI to determine FICON involvement,
that is, is FICON an innocent bystander?
• Performance problem - run GTF and look for PCIs or check source code.
6. Cause identification
• No cause identified - hypothesize likely scenarios and go to Step 3 to
collect more data.
• Cause known - go to Step 7, fix identification.
• Non-FICON cause - do “normal” PD/PSI; that is, if FICON is an innocent
bystander or the problem is re-creatable on ESCON (see Step 5).
7. Fix identification
• Is a fix identified? If yes, go to Step 8, test fix; if no, contact the component
owner.
8. Test fix
• Is the test fix OK? If yes or no, contact the component owner.

Appendix A. Blank FICON planning worksheets
CHPID Placement Report Customer Design Worksheet CHPID Worksheet Worksheet Output
Placement ESCON step
Report
A B C D E F G H I
CHPID Type CHPID CHPID New CUs ESCON to FICON New & ESCON Customer System
Changes & numbers no Path Aggregation, by ESCON Moved Aggregated assigned Cabling
I/O Deleted longer requirement CHPID number CHPID CHPID number CHPID Require
required & by CHPID numbers by not used by any numbers ment
not type & type NEW or MOVED From and To
aggregated quantity CHPID number
ESCON (E)
FICON (H1)
Parallel
(P3/P4)
OSA2 EN/TR
(2E)
OSA2 FDDI
OSA2 ATM
Multimdone(2
M)
OSA2 ATM Sin
glemode(2S)
OSA
EXPRESS
OSA2 FENET
fast
Ethernet(2A)
ISC 1Km (C1)
SM ISC (C3)
ICB (CB)
IC Channel
customer
assigned
CHPID number
Figure 55. Blank configuration definition - configuration worksheet

A B C D E F G H
Channel Director Port Number CHPID range in use but ESCON - FICON relocated Reassigned to
Worksheet Identifier Number assigned to displaced by channel Old=>New alternate
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
Phase 6
Phase 7
Phase 8
Figure 56. Blank ESCON Director Impact Analysis Worksheet

DELETED/MOVED FROM DELETED/MOVED TO
CU-PATH or CU->PATH
Phase #1
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #2
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #3
DELETE
Figure 57. Blank Phase Planning Worksheet - No. 1

DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #4
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #5
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #6
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge

107
108
DELETED/MOVED FROM DELETED/MOVED TO
CU-PATH or CU->PATH
Phase #7
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE

ADD
Bridge
Phase #8
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #9
DELETE
Figure 58. Blank Phase Planning Worksheet - No. 2

DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #10
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #11
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Phase #12
DELETE
DELETE/MOVE
DELETE
DELETE/MOVE
ADD
Bridge
Proc.# ________ Processor/ESCD Phase Perform
Worksheet
Phase # ________ Non Concurrent Install (Yes/No) ___
Definitions Varies Off Hardware Actions Varies on

109
Appendix B. Special notices
This publication is intended to help system engineers and IT specialists to
understand all S/390 FICON connectivity options and to plan what FICON options
fit their system requirements. The information in this publication is not intended
as the specification of any programming interfaces that are provided by specific
products. See the PUBLICATIONS section of the IBM Programming
Announcement for products that you are interested in for more information about
what publications are considered to be product documentation.
References in this publication to IBM products, programs or services do not imply

that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBM's product, program, or service may be used. Any functionally
equivalent program that does not infringe any of IBM's intellectual property rights
may be used instead of the IBM product, program or service.
Information in this book was developed in conjunction with use of the equipment
specified, and is limited in application to those specific hardware and software
products and levels.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact IBM Corporation, Dept.
600A, Mail Drop 1329, Somers, NY 10589 USA.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The information contained in this document has not been submitted to any formal
IBM test and is distributed AS IS. The use of this information or the
implementation of any of these techniques is a customer responsibility and
depends on the customer's ability to evaluate and integrate them into the
customer's operational environment. While each item may have been reviewed by
IBM for accuracy in a specific situation, there is no guarantee that the same or
similar results will be obtained elsewhere. Customers attempting to adapt these
techniques to their own environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for
convenience only and do not in any manner serve as an endorsement of these
Web sites.
Reference to PTF numbers that have not been released through the normal
distribution process does not imply general availability. The purpose of including
these reference numbers is to alert IBM customers to specific information relative
to the implementation of the PTF when it becomes available to each customer
according to the normal IBM PTF distribution process.

The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
IBM  RACF
AS/400 RMF
AT RS/6000
CT S/390
ESCON XDF SP
ESCON SP1
FICON SP2
MVS/ESA System/390
Netfinity XT
OS/390 400
Parallel Sysplex
The following terms are trademarks of other companies:
C-bus is a trademark of Corollary, Inc. in the United States and/or other countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and/or other countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States and/or other countries.
PC Direct is a trademark of Ziff Communications Company in the United States

and/or other countries and is used by IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel

Corporation in the United States and/or other countries.
UNIX is a registered trademark in the United States and/or other countries

licensed exclusively through X/Open Company Limited.
SET and the SET logo are trademarks owned by SET Secure Electronic
Transaction LLC.
Other company, product, and service names may be trademarks or service marks
of others.

Appendix C. Related publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this redbook.
C.1 International Technical Support Organization publications

For information on ordering these ITSO publications see “How to get ITSO
redbooks” on page 115.
None
C.2 Redbooks on CD-ROMs

Redbooks are also available on the following CD-ROMs. Click the CD-ROMs
button at http://www.redbooks.ibm.com/ for information about all the CD-ROMs
offered, updates and formats.
CD-ROM Title Collection Kit
Number
System/390 Redbooks Collection SK2T-2177
Networking and Systems Management Redbooks Collection SK2T-6022
Transaction Processing and Data Management Redbooks Collection SK2T-8038
Lotus Redbooks Collection SK2T-8039
Tivoli Redbooks Collection SK2T-8044
AS/400 Redbooks Collection SK2T-2849
Netfinity Hardware and Software Redbooks Collection SK2T-8046
RS/6000 Redbooks Collection (BkMgr Format) SK2T-8040
RS/6000 Redbooks Collection (PDF Format) SK2T-8043
Application Development Redbooks Collection SK2T-8037
IBM Enterprise Storage and Systems Management Solutions SK3T-3694
C.3 Other Publications

These publications are also relevant as further information sources:
• OS/390 RMF Performance Management Guide, SC28-1951
• Planning for the 9032 Model 3, 9033 Model 4, and 9032 Model 5, SA22-7295
• S/390 I/O Configuration Program User’s Guide and ESCON
Channel-to-Channel Reference , GC38-0401
• Enterprise Systems Connection (ESCON) Implementation Guide, SG24-4662
• Optical Fiber Link Planning, GA23-0367
• Fiber Channel Connection for S/390 I/O Interface Physical Layer, SA23-0395
• S/390 (FICON) I/O Interface Physical Layer, SA24-7172
• IBM Cabling System Optical Fiber Planning and Installation , GA27-3943
• Planning for the 9032 Model 5 with FICON Converter Feature , SA22-7415
• Installation Manual-Physical Planning, G5/G6 , GC22-7106

How to get ITSO redbooks
This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, and
CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.
• Redbooks Web Site http://www.redbooks.ibm.com/
Search for, view, download, or order hardcopy/CD-ROM redbooks from the redbooks Web site. Also read
redpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbooks
site.
Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a few chapters will
be published this way. The intent is to get the information out much quicker than the formal publishing process
allows.
• E-mail Orders
Send orders by e-mail including information from the redbooks fax order form to:
e-mail address
In United States usib6fpl@ibmmail.com
Outside North America Contact information is in the “How to Order” section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl
• Telephone Orders
United States (toll free) 1-800-879-2755
Canada (toll free) 1-800-IBM-4YOU
Outside North America Country coordinator phone number is in the “How to Order” section at
this site:
• Fax Orders
United States (toll free) 1-800-445-9269
Canada 1-403-267-4455
Outside North America Fax phone number is in the “How to Order” section at this site:
This information was current at the time of publication, but is continually subject to change. The latest information
may be found at the redbooks Web site.
IBM Intranet for Employees

IBM employees may register for information on workshops, residencies, and redbooks by accessing the IBM
Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials
repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical
professionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ for
redbook, residency, and workshop announcements.

IBM Redbook Fax Order Form
Please send me the following:
Title Order Number Quantity
First name Last name
Company
Address
City Postal code Country
Telephone number Telefax number VAT number
Invoice to customer number
Credit card number
Credit card expiration date Card issued to Signature
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not
available in all countries. Signature mandatory for credit card payment.

Index
Numerics
9672 LIC 8
C
channel constraint relief 5
CHPID placement report 14
configuration planning 11
D
data rate droop 5
device address limitation 5
E
ESCON port placement report 15
F
Feature Code
FC 5700 8
fiber cables 9
fiber cabling cost 6
FICON design 9
FICON prerequisites 7
S
simple FICON configuration
example 13
implementation 17
IOCDS example 18
software PFTs 8
supported distances 6

ITSO redbook evaluation
SG24-5169-00
Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this
questionnaire and return it using one of the following methods:
• Use the online evaluation form found at http://www.redbooks.ibm.com/
• Fax this form to: USA International Access Code + 1 914 432 8264
• Send your comments in an Internet note to redbook@us.ibm.com
Which of the following best describes you?

_ Customer _ Business Partner _ Solution Developer _ IBM employee
_ None of the above
Please rate your overall satisfaction with this book using the scale:
(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)
Overall Satisfaction __________
Please answer the following questions:
Was this redbook published in time for your needs? Yes___ No___
If no, please explain:
What other redbooks would you like to see published?
Comments/Suggestions: (THANK YOU FOR YOUR FEEDBACK!)

IBM S/390 FICON Implementation Guide SG24-5169-00
Printed in the U.S.A.
SG24-5169-00

IBM S390 FICON Implementation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IBM S390 FICON Implementation Guide

Uploaded by

Copyright:

Available Formats

IBM S/390 FICON Implementation Guide

Ken Trowell, Dennis Ng, John Stimson,

International Technical Support Organization

IBM S/390 FICON Implementation Guide

First Edition (November 1999)

Comments may be addressed to:

© Copyright International Business Machines Corporation 1999. All rights reserved.

Chapter 1. About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Chapter 2. Why implement FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Chapter 3. Introduction to FICON implementation . . . . . . . . . . . . . . . . . . . .7

Part 2. Configuration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Chapter 4. Implementation of a simple FICON configuration . . . . . .. . . . .13

Chapter 5. Planning of a complex FICON configuration . . . . . . . . . . . . . . .19

Chapter 6. FICON Implementation Worksheets . . . . . . . . . . . . . . . . .. . . . .31

Part 3. Implementation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Chapter 7. Processor phase actions . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .45

© Copyright IBM Corp. 1999 iii

Chapter 9. Pre-phase insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 10. Phase merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 11. Executing the install actions . . . . . .. . . . .. . . . . .. . . . . .. . 81

Chapter 12. FICON post-install . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . 89

Appendix A. Blank FICON planning worksheets . . . . . . . . . . . . . . . . . . . . .105

Appendix B. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Appendix C. Related publications . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 113

How to get ITSO redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

iv FICON Implementation Guide

ITSO redbook evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

© Copyright IBM Corp. 1999 vii

viii FICON Implementation Guide

The team that wrote this redbook

Ken Trowell is a S/390 Systems Specialist at the International Technical Support

Dennis Ng works at the IBM WSC in Gaithersburg Maryland as a processor and

Craig Vernon is an Advisory IT Specialist in IBM Australia. He has 18 years of

Lothar Zimmermann is an IT Specialist in IBM Germany working for PSS. He

We want our redbooks to be as helpful as possible. Please send us your

© Copyright IBM Corp. 1999 ix

x FICON Implementation Guide

© Copyright IBM Corp. 1999 1

Concurrent S/390 I/O Configuration

FICON Customers' I/O FICON

FICON Configuration Design

IBM provides 9672 Implementation

Figure 1. FCV configuration planning

Figure 2 on page 4 presents a flowchart of the steps required to design, configure

© Copyright IBM Corp. 1999 3

Customer IBM Customer Customer Customer Customer Customer

Configuration Ordering Determine Determine Determine Build an Installation &

IBM FICON Planning Guide IBM FICON Implementation

Figure 2. Customer design and implementation flowchart

This book provides descriptions of the configuration planning, implementation

The simple FICON configuration is described in Chapter 4, “Implementation of a

The complex FICON configuration is described in Chapter 5, “Planning of a

4 FICON Implementation Guide

Enhancements to the customer's S/390 ESCON channel environment may be

FICON native channels (operating in FC mode) support different requirements

Channel constraint relief

Device addressing limitation relief

Impact of Data Rate droop at distance reduced

Chapter 2. Why implement FICON 5

Fiber cabling cost reduction

Supported distances increased

6 FICON Implementation Guide

A number of worksheets have been developed throughout this implementation

3.1 FICON prerequisites