IBM 2818: Systems Assurance Product Review Guide
IBM® zEnterprise™ 114 (z114)
SA11-002-02
Advanced Technical Skills
w3.ibm.com/support/assure
Copyright 2011 IBM Corporation. All rights reserved
SA11-002-02
Advanced Technical Support
SA11-002-02
IBM 2818:Systems Assurance Product Review Guide
Copyright 2011 IBM Corporation. All rights reserved
Copyright 2011 IBM Corporation. All rights reserved
Take Note!
Before using this information and the product it supports, be sure to read the general information in Appendix G
Special Notices.
Third Edition October 12, 2011
This edition applies to the IBM 2818 Processor Models.
Comments may be addressed to:
IBM Corporation
Systems Assurance Program Administrator
IBM Global Services, PSS
4111 Northside Parkway H07R01
Atlanta, GA 30327
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 2011 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.
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 1. Technical Description and Features . . . . . . . . . . . . . . . . . . . . . .1
1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.1.1 IBM BladeCenter Extension (zBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
1.1.2 Availability Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
1.2 Processor and Drawers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
1.2.1 Processor Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
1.3 Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
1.3.1 Plan Ahead Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
1.4 IO Channel Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.4.1 Hydra Cards - Combined Ordering Rules . . . . . . . . . . . . . . . . . . . . .12
1.4.2 Channels - FICON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.4.3 Channels - OSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
1.4.4 Cryptography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.5 Channels - ESCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
1.4.6 Channels - Coupling Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
1.5 Other Feature Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
1.5.1 Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Chapter 2. Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
2.1 Operating System Support Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
2.1.1 Advanced Workload License Charges . . . . . . . . . . . . . . . . . . . . . . . .27
2.1.2 Advanced Entry Workload License Charges . . . . . . . . . . . . . . . . . . .27
2.1.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
2.1.4 Coupling Facility Control Code Level 17 . . . . . . . . . . . . . . . . . . . . . .33
2.2 Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
2.3 Minimum Function/Feature Requirements . . . . . . . . . . . . . . . . . . . . . . . . .35
2.3.1 IBM zEnterprise Unified Resource Manager . . . . . . . . . . . . . . . . . . .35
2.3.2 CP Assist for Cryptographic Function (CPACF) (#3863) enhancements
35
2.3.3 Crypto Express3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
2.3.4 Crypto Express3 (when defined as a coprocessor) supporting ANSI X9.8
PIN security, Enhanced CCA key wrapping, Secure Keyed-Hash Message
Authentication Code (HMAC), and initial Elliptic Curve Cryptography (ECC)
functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
2.3.5 Crypto Express3 (when defined as a coprocessor) supporting PKA RSA
OAEP
with SHA-256 algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
2.3.6 Crypto Express3 (when defined as a coprocessor) with Expanded support for
AES algorithm, Enhanced ANSITR-31 Secure Key Exchange, PIN block
decimalization table protection, and Additional Elliptic Curve Cryptography
(ECC)
functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
2.3.7 Crypto Express3 (when defined as an accelerator) supporting Modulus
Exponent
I
Copyright 2011 IBM Corporation. All rights reserved.
ME) and Chinese Remainder Theorem (CRT) . . . . . . . . . . . . . . . . . . . . . . 37
2.3.8 FICON Express8S (CHPID type FC) when utilizing native FICON or
Channel-To-Channel (CTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3.9 FICON Express8S (CHPID type FC) for support of zHPF single-track
operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3.10 FICON Express8S (CHPID type FC) for support of zHPF multitrack operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3.11 FICON Express8S (CHPID type FCP) for support of SCSI devices 38
2.3.12 T10-DIF support by the FICON Express8S and FICON Express8 features when
defined as CHPID type FCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3.13 z/OS discovery and autoconfiguration (zDAC) for FICON Express8 and
FICON
Express4 channels (CHPID type FC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3.14 Up to 32 HiperSockets (CHPID type IQD) . . . . . . . . . . . . . . . . . . . 38
2.3.15 HiperSockets network traffic analyzer (HS NTA) on IBM zEnterprise 114
and
System z10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.3.16 OSA Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.3.17 OSA-Express4S GbE LX (#0404) and GbE SX (#0405) . . . . . . . . . 40
2.3.18 OSA-Express4S 10 GbE LR (#0406) and 10 GbE SR (#0407) . . . . 41
2.3.19 OSA-Express4S Large Send for IPv6 packets (CHPID types OSD and
OSX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.3.20 Checksum offload for LPAR-to-LPAR traffic for the OSA-Express4S
features
when defined as CHPID type OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.3.21 Inbound workload queuing for Enterprise Extender for the
OSA-Express4S
and OSA-Express3 features when defined as CHPID types OSD or OSX . 41
2.3.22 OSA-Express3 1000BASE-T (#3367 and #3369) . . . . . . . . . . . . . . 42
2.3.23 Display OSAINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.3.24 Inbound workload queuing (IWQ) for OSA-Express3 CHPID types OSD
and
OSX (exclusive to IBM zEnterprise 114) on IBM zEnterprise 114 and z10 .
2.3.25 12x InfiniBand and 1x InfiniBand coupling links . . . . . . . . . . . . . . .
2.3.26 Coupling Facility Control Code Level 17 . . . . . . . . . . . . . . . . . . . .
2.3.27 Independent Software Vendors (ISV) . . . . . . . . . . . . . . . . . . . . . . .
2.4 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
43
44
44
45
Chapter 3. Physical Site Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.2 Physical Specifications
Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
II
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
3.3 Operating environment:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
3.3.1 Temperature (powered on): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
3.3.2 Electrical Power: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
3.3.3 Customer Circuit Breaker Requirements
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
3.3.4 Capacity of Exhaust: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
3.3.5 Noise Level: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
3.3.6 Leakage and Starting Current: . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
3.4 Physical Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
3.4.1 General requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
3.4.2 Important Power Selection Considerations . . . . . . . . . . . . . . . . . . . .51
3.4.3 Power Estimation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
3.4.4 Power Capping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
3.4.5 Top exit power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
3.4.6 Top exit I/O cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
3.4.7 Non-raised Floor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
3.5 Ethernet network connection requirements . . . . . . . . . . . . . . . . . . . . . . . .53
Chapter 4. Installation Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
4.1 Customer Expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
4.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
4.1.2 ResourceLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
4.1.3 Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
4.1.4 Other Designated Product List (DPL) Equipment/Features . . . . . . . .56
4.1.5 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
4.1.6 Acquisition and Contractual Considerations . . . . . . . . . . . . . . . .56
4.1.7 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
4.1.8 Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
4.1.9 Future Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
4.2 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
4.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
4.2.2 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
4.2.3 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
4.2.4 Hardware Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . .61
4.2.5 Devices and Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
4.2.6 Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
4.2.7 Coupling Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
4.2.8 Server Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
4.2.9 Channel Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
4.2.10 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
4.3 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
4.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
4.3.2 Standalone Dump Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . .69
4.3.3 IOCP and HCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
4.3.4 CIU, CBU, On/Off Capacity on Demand . . . . . . . . . . . . . . . . . . . . . .71
4.3.5 CFCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
4.3.6 IBM and ISV Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
4.3.7 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
4.3.8 Sysplex Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
4.3.9 Linux Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
4.3.10 zIIP and zAAP Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
4.3.11 SCRT Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
III
Copyright 2011 IBM Corporation. All rights reserved.
4.3.12 OSA-Express4S and OSA-Express3 Considerations . . . . . . . . . . . 75
4.4 Installation Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.4.2 FICON Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.4.3 CHPID Mapping Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.4.4 Configuration files and PCHID assignment changes . . . . . . . . . . . . 78
4.4.5 Capacity Back Up and On/Off Capacity on Demand. . . . . . . . . . . . . 79
4.4.6 Hardware Management Console LAN . . . . . . . . . . . . . . . . . . . . . . 80
4.4.7 ESCON Converters and 3745 (Carry over from past servers) . . . . . 80
4.4.8 HCD/IOCP DEFINITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.4.9 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.4.10 Activation Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.4.11 OSA-Express Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.4.12 Crypto Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.5 Physical Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.5.2 OSA-Express3 Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.5.3 Cabling-Using IBM zSeries Fiber Cabling Service Contract . . . . . . . 83
4.5.4 Cabling-Customer Not Using IBM Cabling Service . . . . . . . . . . . . . . 84
4.5.5 Raised Floor Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.5.6 Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.5.7 Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.5.8 Floor Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.5.9 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.5.10 Telephone and Remote Support Service . . . . . . . . . . . . . . . . . . 88
4.5.11 Machine Arrival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.5.12 OTHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.6 System Management Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.1 Problem Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.2 Service and EC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.3 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.4 Availability Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.6 Customer/IBM Meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.7 RSF and Internet Remote Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.7.1 RSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.7.2 Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.8 Resources and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.8.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.8.2 Agreement On Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.9 Service Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.9.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.10 Installation Planning and Documentation . . . . . . . . . . . . . . . . . . . . . . . . 96
4.10.1 Teams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.10.2 Plan Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.10.3 Systems Assurance Confirmation Form . . . . . . . . . . . . . . . . . . . . . 96
4.11 Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.11.1 RESPONSIBILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.12 zIIP Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.12.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.12.2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.12.3 Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.12.4 Sizing the zIIP Requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
IV
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
4.12.5 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
4.12.6 ISV Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
4.12.7 Installation Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
4.12.8 Activation Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
4.12.9 IRD Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
4.12.10 Systems Assurance Confirmation Form . . . . . . . . . . . . . . . . . . . .106
Chapter 5. Must-Read Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
5.1 MR-Customer Expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
5.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
5.1.2 ResourceLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
5.1.3 Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
5.1.4 Other Designated Product List (DPL) Equipment . . . . . . . . . . . . . . .110
5.1.5 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
5.1.6 Acquisition and Contractual Considerations . . . . . . . . . . . . . . . . . .111
5.1.7 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
5.1.8 Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
5.1.9 Future Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
5.2 MR-Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
5.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
5.2.2 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
5.2.3 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
5.2.4 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . .120
5.2.5 Devices and Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
5.2.6 Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
5.2.7 Coupling Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
5.2.8 Server Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
5.2.9 Channel Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
5.2.10 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
5.3 MR-Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
5.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
5.3.2 Standalone Dump Considerations . . . . . . . . . . . . . . . . . . . . . . . . . .132
5.3.3 IOCP and HCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
5.3.4 CIU,CBU, ON/OFF Capacity on Demand . . . . . . . . . . . . . . . . . . . .134
5.3.5 CFCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
5.3.6 IBM and ISV Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
5.3.7 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
5.3.8 Sysplex Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
5.3.9 Linux Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
5.3.10 zIIP and zAAP Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . .137
5.3.11 SCRT Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
5.3.12 OSA-Express4S and OSA-Express3 Considerations . . . . . . . . . . .138
5.4 MR-Installation Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
5.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
5.4.2 FICON Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140
5.4.3 CHPID Mapping Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
5.4.4 Configuration files and PCHID assignment changes . . . . . . . . . . . .143
5.4.5 Capacity Backup and On/Off Capacity on Demand . . . . . . . . . . . . .146
5.4.6 Hardware Management Console LAN . . . . . . . . . . . . . . . . . . . . . . .149
5.4.7 ESCON Converters and 3745 (Carry Over from 9672 and z900) . . .149
5.4.8 HCD/IOCP Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
5.4.9 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
5.4.10 Activation Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
V
Copyright 2011 IBM Corporation. All rights reserved.
VI
SA11-002-02
5.4.11 OSA-Express Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.12 Crypto Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 MR-Physical Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.2 OSA-Express3 Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3 Cabling-Using IBM zSeries Fiber Cabling Service Contract . . . . . .
5.5.4 Cabling-Customer Not Using IBM Cabling Service . . . . . . . . . . . . .
5.5.5 Raised Floor Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.6 Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.7 Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.8 Floor Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.9 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.10 Telephone and Remote Support Service . . . . . . . . . . . . . . . . .
5.5.11 Machine Arrival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.12 Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 MR-System Management Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Problem Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.2 Service and EC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.3 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.4 Availability Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.6 Customer/IBM Meetings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 MR-RSF and Internet Remote Support . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1 RSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.2 Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 MR-Resources and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.2 Agreement on Responsibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9 MR-Service Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.10 MR-Installation Planning and Documentation. . . . . . . . . . . . . . . . . . . .
5.10.1 Teams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.10.2 Plan Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.10.3 Systems Assurance Confirmation Form . . . . . . . . . . . . . . . . . . . .
5.11 MR-Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.11.1 Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12 MR-zIIP Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.3 Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.4 Sizing the zIIP Requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.5 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.6 ISV Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.7 Installation Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.8 Activation Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.9 IRD Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.12.10 Systems Assurance Confirmation Form . . . . . . . . . . . . . . . . . . .
153
153
155
155
156
156
156
159
159
160
160
160
161
161
162
163
163
163
163
163
163
164
165
165
165
167
167
167
168
168
170
170
170
170
171
171
172
172
175
176
177
177
178
178
178
179
179
Chapter 6. Pre-Sales Checklists . . . . . . . . . . . . . . . . . .
6.1 Customer Expectations . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3 Acquisition and Contractual Considerations .
181
181
181
181
181
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Copyright 2011 IBM Corporation. All rights reserved.
6.1.4 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
6.1.5 Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
6.2 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
6.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
6.2.2 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
6.2.3 Devices and Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
6.2.4 Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
6.2.5 Coupling Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
6.2.6 Server Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
6.2.7 Channel Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
6.2.8 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
6.3 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
6.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
6.3.2 CIU, CBU, On/Off Capacity on Demand . . . . . . . . . . . . . . . . . . . . .187
6.3.3 CFCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
6.3.4 IBM and ISV Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . .187
6.3.5 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
6.3.6 Sysplex Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
6.3.7 Linux Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
6.3.8 zIIP and zAAP Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
6.4 Installation Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
6.4.1 OSA-Express Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
6.4.2 Crypto Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
6.5 Physical Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
6.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
6.5.2 Cabling-Using IBM zSeries Fiber Cabling Service Contract . . . . . . .190
6.5.3 Cabling-Customer Not Using IBM Cabling Service . . . . . . . . . . . . .191
6.5.4 Raised Floor Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
6.5.5 Hardware Management Console. . . . . . . . . . . . . . . . . . . . . . . . . .192
6.5.6 Telephone and Remote Support Service . . . . . . . . . . . . . . . . . . .192
6.6 System Management Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
6.6.1 Service and EC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
6.7 Service Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
6.7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
6.8 Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
6.8.1 RESPONSIBILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Chapter 7. Pre-Sales Must-Read Information . . . . . . . . . . . . . . . . . . . . . .197
7.1 MR-Customer Expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
7.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
7.1.2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
7.1.3 Acquisition and Contractual Considerations . . . . . . . . . . . . . . . . . .199
7.1.4 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
7.1.5 Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
7.2 MR-Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
7.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
7.2.2 Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
7.2.3 Devices and Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
7.2.4 Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
7.2.5 Coupling Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
7.2.6 Server Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
7.2.7 Channel Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
7.2.8 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
VII
Copyright 2011 IBM Corporation. All rights reserved.
7.3 MR-Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.2 CIU,CBU, ON/OFF Capacity on Demand . . . . . . . . . . . . . . . . . . . .
7.3.3 CFCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.4 IBM and ISV Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.5 Crypto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.6 Sysplex Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.7 Linux Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.8 zIIP and zAAP Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 MR-Installation Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.1 OSA-Express Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.2 Crypto Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 MR-Physical Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.2 Cabling-Using IBM zSeries Fiber Cabling Service Contract . . . . . .
7.5.3 Cabling-Customer Not Using IBM Cabling Service . . . . . . . . . . . . .
7.5.4 Raised Floor Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.5 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.6 Telephone and Remote Support Service . . . . . . . . . . . . . . . . . .
7.6 MR-System Management Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6.1 Service and EC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.7 MR-Service Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.8 MR-Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.8.1 Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
209
209
209
209
210
210
210
211
211
212
212
212
213
213
213
213
216
216
216
217
217
218
218
220
220
Chapter 8. Publications and Education . . . . . . . . . . . . . . . . . . . . . . . . . . 221
8.1 Information about the IBM z114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Appendix A. MSU Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Appendix B. Cabling and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
B.1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
B.2 Cabling Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
B.3 InfiniBand Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
B.4 Connectors and Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
B.5 Fiber Quick Connect (FQC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
B.6 Top exit I/O cabling (FC7920) and Top Exit Power Cords (FC7901) . . . . . . .229
B.7 FC8012 Frame bolt down kit, raised floor . . . . . . . . . . . . . . . . . . . . . . . . . . .230
B.8 FC8013 Frame bolt down kit, non-raised floor . . . . . . . . . . . . . . . . . . . . . . . .231
B.9 Installation Manual for Physical Planning (IMPP) . . . . . . . . . . . . . . . . . . . . .231
Appendix C. Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
C.1 Capacity on Demand - Temporary Capacity . . . . . . . . . . . . . . . . . . . . . . . . .233
8.1.1 On/Off CoD Administrative Test - . . . . . . . . . . . . . . . . . . . . . . . . . . 242
C.2 Temporary Capacity Enablement Features . . . . . . . . . . . . . . . . . . . . . . . . . .243
C.3 CBU (Capacity Backup Upgrade) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243
C.4 Capacity on Demand - Permanent Capacity . . . . . . . . . . . . . . . . . . . . . . . . .246
8.1.2 CIU enhancement (on z196 and z114 only) . . . . . . . . . . . . . . . . . . 246
Appendix D. Installation Practices and Policies . . . . . . . . . . . . . . . . . . . . .249
Appendix E. Crypto Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
E.1 CCF to PCI Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
VIII
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
E.2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Appendix F. Actions requiring an outage . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
F.1 What about an outage in a member of a multi-node Ensemble? . . . . . . . . . 253
Appendix G. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
IX
Copyright 2011 IBM Corporation. All rights reserved.
X
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Preface
The Solution Assurance information, tools and documentation ("Materials") are being
provided to IBM Business Partners to assist them with customer installations. Such
Materials are provided by IBM on an "as-is" basis. IBM makes no representations or
warranties regarding these Materials and does not provide any guarantee or
assurance that the use of such Materials will result in a successful customer
installation. These Materials may only be used by authorized IBM Business Partners
for installation of IBM products and otherwise in compliance with the IBM Business
Partner Agreement.
This document remains the property of IBM and may not be disclosed outside of
IBM without proper management approval. Its purpose is to provide insight into
the installation of a IBM z114. It is intended to be read by IBM personnel (both
marketing and service), as well as customers involved in the Systems Assurance
process. The layout of this guide follows the sequence of the Systems Assurance
Discussion Guide used at the Systems Assurance Review.
This document has not been subjected to any formal IBM test and is distributed
on an “as is” basis without any warranty either expressed or implied. Contents
must be evaluated for applicability to a particular installation. Pertinent
information from this document may be discussed with, and/or abstracted for a
presentation to a customer. However, any code included is for internal information
purposes only and may not be given to customers. If included code is identified
as “incidental programming” its use must conform to IBM guidelines. IBM
personnel may make reproductions of this information for their own use.
Responsibility for maintaining appropriate security accompanies such
reproductions.
In this document, any references made to an IBM licensed program are not
intended to state or imply that only IBs licensed program may be used; any
functionally equivalent program may be used instead. References in this
publication to IBM products, programs or services do not imply that IBM intends
to make these available outside of the United States.
SAPR Guide Generation and Support
This SAPR Guide is produced by the Advanced Technical Skills organization in
Gaithersburg Maryland.
Paul S Hagen is the primary author and the point of contact for any errors,
discrepancies, comments, or suggestions for improvement.
Comments welcome
Your comments are important to us!
It is intended that this SAPR Guide to be as helpful as possible. Please send your
comments about this SAPR Guide in one of the following ways:
• Fax the evaluation form found in the Appendix to the fax number shown on the
form.
XI
Copyright 2011 IBM Corporation. All rights reserved.
• Send your comments via Internet note to hagen@us.ibm.com or via Lotus
Notes to Paul Hagen/Poughkeepsie/IBM@IBMUS.
XII
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Summary of Changes in this Edition
Third Release -02 (October 12, 2011)
• This is the third release of the z114 SAPR.
• Updated to reflect items in the October 12, 2011 announcement. Most of the
announcements pertained to the zBX, but some apply here, and to the
zEnterprise 196. See the zBX SAPR Guide also, SA10-006. Some of the items
in this announcement contain:
• zBX support for Windows (64-bit only) on select System x blades
• Unified Resource Manager enhancements
• Support for Windows
• API for Unified Resource Manager
• Dynamic discovery of storage resources
• Performance improvements to High Performance FICON for System z
(zHPF)
• GDPS support for zEnterprise System
• IBM Implementation Services for System z
• New DataPower XI50z support features
• Added additional Statements of Direction in Future Planning
• A Statement of Direction that has changed, related to FICON Express4.
• Added a Checklist item related to z/OS Synchdest the parameter for consoles.
• Added a Checklist item related to a new feature code (FC0033) regarding the
shipment of some publications.
• Added a Checklist item related to PMV records.
• Updated the requirements to order an ECA for Driver 93 on installed HMCs.
• Corrected an HMC item related to 32 subchannels on InfiniBand coupling
links.
• Added more information to the MustRead related AWLC.
• Minor changes to Chapter 8 Publications and Education
• Added information in the MustRead and Publications chapter regarding a new
feature code (FC0033) regarding publication ordering of the Service Guide,
Install Guide, and Safety inspection guide.
• Added information about the IBM Lifecycle Extensions for z/OS V1.10, V1.9
and V1.8
• Added some Checklist and MustRead items, related to Driver 93.
• FYI - IBM has announced IBM z/VM Single System Image Feature (VMSSI)
contained in z/VM V6.2.
• Removed FC9970 Weight Distribution Kit, not relevant to z114.
XIII
Copyright 2011 IBM Corporation. All rights reserved.
Second Release -01 (September 9, 2011)
• This is the second release of the z114 SAPR.
• Sec 4.3.1 Item 1 - Clarified SMP/E and FIXCAT
• Sec 4.3.1 Item 4 - Clarified C/C++ Compiler Options
• Sec 4.2.4 Item 13 - Clarified Customized Data Replication Facility usage
• Sec 4.2.10 Item 35 - Moved FC3863 CPACF to Sec 4.2.1 Item 5
• Sec 4.5.2 Item 5 - Added OSA-Express4S
• Sec 5.6.3 Item 5 - Added Techdocs url for HMC 2.11.1 PRS4707
• Sec 1.4.3 - Added OSA-Express3 1000BaseT FC3369
• Sec 5.4.4 Item 19 - Added OSA-Express3 1000BaseT FC3369
• Sec 5.4.4 Item 19 - Changed z990 to z9, z9 to z10
• Sec 5.4.4 Item 19 - Deleted FC0409 and FC0410 FICON Express 8S
• Sec 5.5.4 Item 13 - Added OSA-Express3 1000BaseT FC3369
• Sec 7.5.3 Item 9 - Added OSA-Express3 1000BaseT FC3369
• Sec 4.3.7 Item 23 - Changed wording for Crypto UDX
• Sec 6.3.5 Item 8 - Changed wording for Crypto UDX
• Sec 4.3.3 Item 11 - Deleted Migrating non-MCSS (z890) to an MCSS server
• Sec 5.3.3 Item 11 - Deleted Migrating non-MCSS (z890) to an MCSS server
• Sec 4.3.12 Item 36 - Changed wording for ports/CHPIDS
• Sec 4.4.6 Item 27 - Added SE’s
• Sec 5.3.7 Item 22 - Added wording for Crypto UDX
• Sec 5.1.1 Item 2 - Removed Concurrent Book Replace
• Sec 5.2.4 Item 12 - Fixed typo on D93
• Sec 5.2.4 Item 13 - Added comments for Ensemble CPC’s at different Drivers
• SAPR Guides Evaluation - Changed to Paul S Hagen
• SAPR Guides Evaluation - Deleted reference to SA Advisor Lotus ID
• Sec 5.2.4 Item 13 - Added HMC machine types for FC0090 and FC0091
• Sec 1.5.1.1 - Updated 2819 GBC description
• Sec 1.5.1.2 - Added RPQ 8P2534 explanation
• Sec 1.2.2 - Added Sub-Capacity Processor Granularity Description and Chart
• Sec 1.4.2 - Changed FC 3325 and 3326 to carry forward only
• Sec 3.5 Figure 1 - Changed to 2818 Diagram
• Sec 5.2.9 Item 34 - Changed diagram for 2818
• Sec 5.5.6 Item 27 - Deleted comments ‘example shown below’.
• Sec 4.4.2 Item 15 - Added Comments at zHPF
• Sec 5.4.2 Item 15 - Added comments about zHPF
• Sec 4.1.5 Item 8 - Added URL’s for zPCR and zCP3000
XIV
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
• Sec 5.2.4 Item 12 - Change FC 0090 and 0091 to FC 0084 and 0090
• Sec 1.5.1.3 - Added Month, Day, Hour, Minute Indicator Description
• Sec 5.3.9 Item 27 - Added url for Business Partners
• Sec 4.5.5 Item 20 - Changed to Non-Raised Floor Requirements
• Sec 5.5.5 Item 20 - Added in Non-Raised Floor Requirements
• Sec 1.1.1 - Added Ensemble Notes
• Sec 2.3.1.8 - Removed two typos
• Sec 2.3.22.3 - Changed V1.7 to V1.8
• Sec 2.3.22.6 - Changed V1.7 to V1.8
• Sec 4.3.3 Item 12 - Added comments to point to Must Read
• Sec 4.3.7 Item 18 - Added latest version of ICSF download url
• Sec 5.1.1 Item 2 - Deleted line.
• Sec 5.2.10 Item 35 - Moved FC3863 CPACF to Sec 5.2.1 Item 5
• Sec 5.2.4 Item 12 - Changed EC SSR orders to EC D77155 (ECA 285)
• Sec 5.2.10 Item 36 - Added comments
• Sec 5.2.10 Item 38 - Rewrote this step.
• Sec 5.3.3 Item 12 - Added comments about LSYSTEM
• Sec 5.3.7 Item 18 - Added comments about HCR7790
• Sec 5.3.12 Item 36 - Added two more urls for reference
• Sec 5.4.2 Item 40 - Changed DR to Disaster Recovery
• Sec 5.4.2 Item 10 - Removed typo.
• Sec 6.1.2 Item 5 - Same change as 4.1.5 Item 8.
• Sec 6.2.1 Item 4 - Added same as 4.2.1 Item 5.
• Sec 7.2.1 Item 4 - Added same as 5.2.1 Item 5.
• Sec 7.2.4 Item 10 - Same change as 5.2.4 Item 13.
• Sec 7.2.8 Item 19 - Same change as 5.2.10 Item 35.
• Sec 7.2.8 Item 20 - Same change as 5.2.10 Item 38.
• Sec 7.3.5 Item 8 - Same change as 5.3.7 Item 22.
• Sec 7.4.2 Item 2 - Same change as 5.4.12 Item 40.
• Sec 3.4.4 - Removed Set Power Capping
First Release -00 (July 12, 2011)
• This is the first release of the z114 SAPR.
XV
Copyright 2011 IBM Corporation. All rights reserved.
XVI
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 1. Technical Description and Features
This chapter provides an overview of technical and ordering details.
1.1 Overview
The IBM zEnterprise System (TM) is a system that combines the gold standard of
enterprise computing with built-in function to extend IBM's mainframe-like
governance and qualities of service to special-purpose workload optimizers and
general-purpose application serving. End-to-end management is enabled for this
heterogeneous environment by the IBM zEnterprise Unified Resource Manager
(sometimes erroneously referred to as zManager), which provides energy
monitoring and management, goal-oriented policy management, increased
security, virtual networking, and data management, consolidated in a single
interface that can be tied to business requirements. The IBM zEnterprise System
is comprised of the IBM zEnterprise 114, the IBM zEnterprise Unified Resource
Manager, the IBM zEnterprise BladeCenter Extension (zBX), and optimizers or
blades.
The IBM zEnterprise 114 (z114) is designed with improved scalability,
performance, security, resiliency, availability, and virtualization. The new 14-way
core design delivers massive scalability for secure data serving and transaction
processing for large-scale consolidation. As environmental concerns raise the
focus on energy consumption, the IBM zEnterprise 114 central processor
complex (CPC) is designed with new energy efficiencies that can reduce energy
use and save floor space when consolidating workloads from distributed servers.
For clients looking to build green data centers, optional water cooling and
high-voltage DC power allow a bold step into the future of cooler computing and
increased energy efficiency without changing the system footprint. See
http://www.ibm.com/systems/z/hardware/zenterprise/index.html.
The IBM zEnterprise Unified Resource Manager manages System z ensembles,
collections of one or more zEnterprise System nodes in which each node is
comprised of a z114 and its optionally attached IBM zEnterprise BladeCenter
Extension (zBX) model 002 (2458-002). The resources of a zEnterprise System
ensemble are managed and virtualized as a single pool of resources, integrating
system and workload management across the multisystem, multi tier, multi
architecture environment.
When IBM zEnterprise BladeCenter Extension (zBX) is attached to IBM
zEnterprise 114, the zBX infrastructure works with the IBM zEnterprise 114 to
support the multi platform environment, combining mainframe and distributed
technologies. The zBX can support
• IBM Smart Analytics Optimizer for DB2 for z/OS, V1.1 (5697-AQT)
• POWER7 blades
• IBM WebSphere DataPower Integration Appliance XI50 for zEnterprise
(DataPower XI50z).
• IBM System x blades
The IBM Smart Analytics Optimizer for DB2 for z/OS, V1.1 (5697-AQT) is
designed to deliver improved service through accelerated and accurate business
insight. This workload-optimized, appliance-like add-on is installed in the zBX and
Chapter 1. Technical Description and Features
1
Copyright 2011 IBM Corporation. All rights reserved.
connects to DB2, providing transparency to all applications.
The optional POWER7 and System x blades are installed in the zBX, enabling
application integration with System z transaction processing, messaging, and
data serving capabilities. The blades are managed as a single logical virtualized
environment by IBM zEnterprise Unified Resource Manager. IBM Global
Technology Services (GTS) and Systems Lab Services can help you assess and
perform application fit-for-purpose analysis, and design an IBM zEnterprise
System that integrates IT strategy and business priority. This includes developing
the business case and high-level transition plan, and a road map for an adaptable
and efficient infrastructure.
DataPower XI50z is a multifunctional appliance that can help provide multiple
levels of XML optimization, streamline and secure valuable service-oriented
architecture (SOA) applications, and provide drop-in integration for
heterogeneous environments by enabling core Enterprise Service Bus (ESB)
functionality, including routing, bridging, transformation, and event handling. It
can help to simplify, govern, and enhance the network security for XML and Web
services.
The IBM WebSphere DataPower Integration Appliance XI50 for zEnterprise
(DataPower XI50z), integrated into the zEnterprise system, is a high-performance
hardware appliance that:
• Provides fast and flexible integration with any-to-any transformation between
disparate message formats with integrated message-level security and
superior performance
• Provides web services enablement for core System z applications to enable
web-based workloads
• Enables SOA and XML applications with System z web services for seamless
integration of distributed and System z platforms
• Offers standards-based, centralized System z governance, and extreme
reliability through integrated operational controls, "call home," and integration
with RACF security through a secured private network
GTS and Systems Lab Services can also enable you to build and run a smarter
IBM zEnterprise System environment. With these services, you can migrate
effectively and efficiently to an IBM zEnterprise System, create a more
cost-effective and manageable computing environment with server, storage, and
network optimization, integration, and implementation, and effectively run and
manage the IBM zEnterprise System with maintenance and technical support
services.
1.1.1 IBM BladeCenter Extension (zBX)
IBM z114 represents a state of the art scalable server designed and optimized for
growth and large-scale consolidation as well as the premier platform to host
traditional mission critical workloads along side new application workloads. z114
provides an advanced combination of scalability, availability, reliability, security,
and virtualization.
z114 is a total systems approach to delivering advanced heterogeneous systems
management functions. Under the management of one system – z114 delivers
higher total system capacity, memory, and I/O bandwidth; z114 allows you to
integrate system and workload management across a multisystem, multi tier, and
2
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
multi architectural environment; and z114 enables you to efficiently monitor and
management your energy consumption.
There may be feature codes charges associated with the z114, as shown in the
table below. The charges are tiered and are associated with added value base on
functionality.
Manage:
Delivers Unified Resource Manager’s function for core operational controls,
installation and configuration, and energy monitoring.
Advanced Management:
Delivers workload definition and performance policy monitoring and reporting.
Automate:
Delivers workload definition and performance policy monitoring and reporting.
Delivers goal oriented monitoring and goal oriented management of resources
and energy management.
Manage
Charges per
connection
Advance
Management
Charges per
connection
Automate
Charges per
connection
z/OS
FC0019
N/C
N/A
FC0020
N/C
IFL
N/C
N/A
FC0052
Yes
ISAOPT
FC0039
Yes
N/A
FC0043
N/C
POWER7
FC0041
Yes
N/A
FC0045
Yes
XI50z
FC0040
N/A
FC0044
N/C
HX5 Blade
FC0042
Yes
FC0046
Yes
N/A
zBX, machine type 2458 (model number 002), is a hardware infrastructure that
consists of a BladeCenter chassis attached to a z114.
Ensemble notes:
• Multiple zEnterprise systems in an ensemble with a zBX can be at different
driver levels (GA1/Driver 86 and GA2/Driver 93 CPCs).
• If one zEnterprise server in the ensemble has FC0020 (automate suite), then
all zEnterprise servers in the ensemble must have FC0020.
• The zEnterprise server must be at driver level 93 or greater for managing the
z/VM 6.2 hypervisor from the Unified Resource Manager.
Chapter 1. Technical Description and Features
3
Copyright 2011 IBM Corporation. All rights reserved.
• The zEnterprise server must be at driver level 93 or greater to support the use
of AIX 7.1 as an operating system on the POWER7 blades.
If you currently have an ensemble and want to upgrade nodes to add FC0020,
follow the following procedure.
a. Order an upgrade from Manage to Automate for all nodes in the Ensemble
via eConfig. This produces a new LICCC record for each node.
b. Install the upgrade via the Perform Model Conversion task on the SE of
each node.
c. Once all Ensemble nodes have been upgraded, the entire ensemble will
automatically start running at the Automate level and the associated
functions can be exploited.
d. Until all nodes have been upgraded, the Ensemble will continue to run at
the Manage level (i.e., we force the Ensemble to the lowest level installed
on all nodes).
The IBM Smart Analytics Optimizer processes and analyzes CPU intensive DB2
queries. It provides a single enterprise data source for queries providing fast and
predictable query response time. For a quick step-through of prerequisite,
installation, and configuration information about the IBM Smart Analytics
Optimizer, see the IBM Smart Analytics Optimizer for DB2 for z/OS Quick Start
Guide. The POWER7 Application Server Blade is installed with a hypervisor that
enables application integration with System z transaction processing, messaging,
and data serving capabilities.
The Power7 blades and IBM Smart Analytics Optimizer in the BladeCenter, along
with the z114 central processors, can be managed as a single logical virtualized
system by the Unified Resource Manager.
DataPower XI50z is a multifunctional appliance that can help provide multiple
levels of XML optimization, streamline and secure valuable service-oriented
architecture (SOA) applications, and provide drop-in integration for
heterogeneous environments by enabling core Enterprise Service Bus (ESB)
functionality, including routing, bridging, transformation, and event handling. It
can help to simplify, govern, and enhance the network security for XML and web
services.
Microsoft Windows is a supported operating system running on select IBM
BladeCenter HX5 (7873) blades installed in the IBM zEnterprise BladeCenter
Extension Model 002, expanding access to an even wider scope of applications
for integration between System z and System x blades for multi-tiered
applications. Supported configurations and operating system levels can be found
at:
http://www.ibm.com/common/ssi/cgi-bin/ssialias?
infotype=SA&subtype=WH&apname=
STGE_ZS_ZS_USEN&htmlfid=ZSL03128USEN&attachment=ZSL03128USEN.P
DF.
As part of IBM's previously stated plans for the zEnterprise Unified Resource
Manager, IBM is introducing two important new capabilities. The first relates to
extending the management functions with programmatic access to application
programming interfaces (APIs) to enable integration between Unified Resource
Manager and the broader ecosystem of management tools. These APIs provide
4
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
access to the underlying functions of the user interface and can be exploited to
enable discovery, monitoring, and provisioning for zEnterprise resources.
The second area relates to the enhanced capability of the Unified Resource
Manager to dynamically discover storage resources. A server administrator will
now be able to trigger auto-discovery and configuration support for new storage
resources installed in support of blades and z/VM virtual servers, and make them
available when doing workload resource configurations.
z114 (left) and zBX (right)
1.1.2 Availability Dates
§Planned Availability Dates - July 21, 2011 Announcement
• September 09, 2011 – Driver 93
• IBM zEnterprise 14 Models M05 and M10 new builds
• Field installed features and conversions that are delivered solely through a
modification to the machine's Licensed Internal Code (LIC):
• LIC only upgrades for any PU type and memory
• LIC for CBU and On/Off Capacity upgrade for installed z114s
• z114 Capacity Setting downgrades
• IBM System z9® Business Class (z9® BC) upgrades to z114
Chapter 1. Technical Description and Features
5
Copyright 2011 IBM Corporation. All rights reserved.
•
•
•
•
IBM System z10™ Business Class (z10 BC™) upgrades to z114
NEW z196s at GA2 level
MES for new function/features for installed z196s
TKE Support for LIC 7.1
• September 26, 2011
•
•
•
•
•
Unified Resource manager functions:
Manage suite (#0019) enhancements
Automate/Advanced Management Firmware Suite (#0020) enhancements
Manage Firmware System x Blade (#0042)
Advanced Management Firmware System x Blade (#0046)
• October 21, 2011
• Add a zBX as an MES to the installed z114
• December 31, 2011
• z114 Model M05 to M10 upgrades
• Feature adds (memory, I/O, RPQs and zBX features)
§Planned Availability Dates - October 12, 2011 Announcement
• November 18, 2011
• High Performance FICON for System z enhancements
• Support for certain I/O transfers for workloads using QSAM, BPAM, and
BSAM access methods
• Basic nonextended format physical sequential data sets
• Basic and large format sequential data sets
• GDPS support for zEnterprise System
• IBM Implementation Services for System z
• New DataPower XI50z support features
• December 16, 2011
• zBX support for Windows (64-bit only) on select System x blades
• Unified Resource Manager enhancements
• Support for Windows
• API for Unified Resource Manager
• Dynamic discovery of storage resources
6
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
1.2 Processor and Drawers
z114 is offered in two models. The model naming is representative of the
maximum number of customer configurable processor units (PUs) in the system.
PUs are delivered in single engine increments orderable by feature code. The
model number also reflects the number of PUs installed. Unlike the
zEnterprise196 (z196), which has up to four books that are mounted vertically in
the top of the CPC frame, the z114 has either one or two CPC drawers which are
mounted horizontally in the CPC frame.
Model
Drawers
Feature Code
M05
1
FC1135
M10
2
FC1136
Disruptive upgrade from M05 to M10
No model downgrades
Upgrades from z9 BC and z10 BC into either model M05 or M10
M10 will upgrade to z196 Model M15 (Air cooled only)
Model
CPs
IFLs
Unassigned
IFLs
zAAPs
zIIPs
ICFs
Std.
SAPs
Addition
SAPs
Spares
M05
0-5
0-5
0-2
0-2
0-5
2
0-2
0
M10
0-5
0-10
0-5
0-5
0-10
2
0-2
2
1.2.1 Processor Features
1.2.1.1 Central Processor FC3074 - FC3099
These are the standard general purpose processors and are used for general
workload. General purpose processors can be used in a partition to run not only
general workloads (i.e. z/OS, z/VM, etc.) but can also be used to run specialty
workloads such as coupling facility code (CFCC) or Linux code. However, the use
of specialty processors (e.g. zIIP, IFL, ICF, etc.) will help decrease the software
costs associated with the use of general purpose processors.
1.2.1.2 Integrated Facilities for Linux (IFL) FC3394
The purpose of the IFL feature is to designate processors to be used specifically
for executing the Linux application programs.
1.2.1.3 Integrated Coupling Facility (ICF) FC3395
The purpose of the ICF feature is to designate processors to be used specifically
for coupling facility control code (CFCC).
1.2.1.4 Optional System Assist Processor (Optional SAP) FC3396
The purpose of the SAP feature is to designate processors to be used specifically
for assisting I/O operations.
Chapter 1. Technical Description and Features
7
Copyright 2011 IBM Corporation. All rights reserved.
1.2.1.5 IBM System z Application Assist Processor (zAAP) FC3397
The purpose of the zAAP "Off Load Processor" feature is to designate processors
to be used specifically for executing strategic application programs, such as,
Java applications. The zAAP processor hardware and architecture is identical to
standard processors but is restricted by systems firmware to operate only as an
Off Load processor.
1.2.1.6 IBM System z Integrated Information Processor (zIIP) FC3398
An "Off Load Processor" similar to zAAP but workload is restricted to DB2 type
applications.
1.2.1.7 Unassigned Integrated Facilities for Linux (IFL) FC3399
The purpose of this IFL feature is to designate processors to be used specifically
for executing the Linux application programs which are purchased but are not
active.
1.2.2 Sub-capacity Processor Granularity
Unlike the z196, the z114 offers a larger range of 130 distinct capacity levels for
CPs (full capacity and 25 sub-capacities). A processor characterized as anything
other than a CP is always set at full capacity. There is, correspondingly, a pricing
model for non-CP processors regarding purchase and maintenance prices, and
various offerings for software licensing costs. Granularity levels are similar to z10
BC to facilitate upgrades and incremental growth. A capacity level is a setting of
each CP to a sub-capacity of the full CP capacity. Full capacity CPs are identified
as CP-Z. On the z114 server, 5 CPs can be configured as CP-Z. Besides full
capacity CPs, 25 sub-capacity levels (CP-A to CP-Y), each for the 5 CPs, are
offered. The capacity levels appear in hardware descriptions as feature codes on the
CPs.
8
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
z114 Sub-capacity Processor Granularity
 The z114 has 26 CP capacity levels (26 x 5 = 130)
– Up to 5 CPs at any capacity level
• All CPs must be the same capacity level
 The one for one entitlement to purchase one zAAP
and/or one zIIP for each CP purchased is the same for
CPs of any speed.
– All specialty engines run at full speed
– Processor Unit Value for IFL = 100
Number of z114
CPs
Base Ratio Ratio z10 BC
1 CP
z10 BC Z01
to z114
1.18
2 CPs
z10 BC Z02
1.16
3 CPs
z10 BC Z03
1.14
4 CPs
z10 BC Z04
1.13
5 CPs
z10 BC Z05
1.12
5-way
3139 PCIs
1-Way
5-Way
4-Way
3-Way
2-W ay
A BC
1-way
(sub-capacity
26 PCIs)
DE F
GH
PCI – Processor Capacity Index
50
I J
K L
MN
O P
Cap
Q R
aci t
y lev
S T
el
U V
W X
s
i ne
ng
E
#
Y
Z
1-way
782 PCIs
FULL size
Speci alty Engine
© 2011 IBM Corporation
Chapter 1. Technical Description and Features
9
Copyright 2011 IBM Corporation. All rights reserved.
1.3 Memory
A z114 server has more physical memory installed than what is ordered. Part of
the physical installed memory is used to implement the redundant array of
independent memory (RAIM) design and the Hardware System Area (HSA).
Redundant array of independent memory (RAIM) on System z servers, which in
the disk industry is known as redundant array of independent drives (RAID).
RAIM design detects and recovers from DRAM, socket, memory channel or
DIMM failures.
Various memory offerings exist. It is recommended to use the eConfig to
determine upgrade offerings. However, while looking at eConfig output,
attempting to determine physical memory installed will be difficult at best. Rather,
we suggest that you simply focus on what memory is purchased for use by the
customer.
• Purchase Memory – Memory available for assignment to LPARs
• Hardware System Area – Standard 8 GB outside customer memory for system
use
• Standard Memory – Provides minimum physical memory required to hold base
purchase memory plus 8 GB HSA
• Plan Ahead Memory – Provides additional physical memory needed for a
concurrent upgrade (LIC CC change only) to a preplanned target customer
memory
The following table lists the two z114 models and the memory range of each
model. Memory upgrades within the same color (except white) are concurrent
without the need for memory plan ahead.
10
FC
GB
Increment
3609
8
8
3610
16
8
3611
24
8
3612
32
8
3613
40
3614
48
3615
M05
M10
(2 CPC drawers)
Dial Max
Dimm (GB)
# plugged
Dial Max
Dimm (GB)
24
4
10
N/A
N/A
N/A
4
10
56
4/4
10/10
4
10
4/4
10/10
8
10
4/4
10/10
8
8
10
4/4
10/10
8
8
10
4/4
10/10
56
8
8
10
4/4
10/10
3616
64
8
16
10
4/8
10/10
3617
72
8
16
10
4/8
10/10
3618
80
8
16
10
4/8
10/10
3619
88
8
16
10
4/8
10/10
56
120
88
# plugged
3620
96
8
16
10
8/8
10/10
3621
104
8
16
10
8/8
10/10
3622
112
8
16
10
8/8
10/10
3623
120
8
16
10
3624
152
32
3625
184
32
3626
216
32
3627
248
32
SA11-002-02
N/A
120
8/8
10/10
152
4/16
10/10
184
8/16
10/10
248
16/16
10/10
16/16
10/10
Copyright 2011 IBM Corporation. All rights reserved.
1.3.1 Plan Ahead Memory
Plan ahead memory, an optional feature, allows you to preplan to future memory
upgrades. The memory upgrades can be made nondisruptively and also
concurrently.
The pre planned memory feature will add the necessary physical memory
required to support target memory sizes. The granularity of physical memory in
the System z114 design is more closely associated with the granularity of logical,
entitled memory, leaving little room for growth. If you anticipate an increase in
memory requirements, a "target" logical memory size can be specified in the
configuration tool along with a "starting" logical memory size. The configuration
tool will then calculate the physical memory required to satisfy this target
memory. Should additional physical memory be required, it will be fulfilled with
the currently available pre planned memory features.
1.3.1.1 Plan Ahead Memory (FC1993)
The Plan Ahead Memory feature (FC1993) adds the necessary physical memory
required to support target memory sizes. Therefore, it gives you the flexibility to
activate memory to any logical size offered between the starting logical memory
size and the target logical memory size. You can preplan future upgrades to be
nondisruptive.
1.3.1.2 Plan Ahead Memory Activation (FC1903)
The Plan Ahead Memory Activation feature (FC 1903) allows you to activate a
Plan Ahead Memory feature. One Plan Ahead Memory Activation is required for
each Plan Ahead Memory feature.
Note: Normal memory upgrades use up the plan-ahead memory first.
Chapter 1. Technical Description and Features
11
Copyright 2011 IBM Corporation. All rights reserved.
1.4 IO Channel Features
The z114 will utilize the I/O drawer introduced on the z10 BC and as well as the
new PCIe I/O drawer. The full sized Cargo cage is not supported in the z114.
Drawers
Links
I/O Drawers
Links
PCIe Drawer
Models
Links
Hubs
0
2
0
4
0
M05/M10
0
0
1
2
0
4
1
M05/M10
4
2
2
2
0
4
2
M05/M10
8
4
1
2
1
4
0
M05/M10
2
1
2
2
1
4
1
M05/M10
6
3+1
3
2
1
4
2
M10
10
5+1
2
2
2
4
0
M05/M10
4
2
3
2
2
4
1
M05/M10
8
4
3
2
3
4
0
M05/M10
6
3+1
4
2
4
4
0
M05
8
4
The z114 supports up to 3 I/O drawers with 2 CPC drawers or up to 4 I/O drawers
with 1 CPC drawer. The PCIe I/O Drawer will be limited to a maximum of 2
drawers and the I/O Drawer will support a maximum of 4 I/O drawers. The table
below is the supported combinations of I/O drawers.
I/O Subsystem General Rules
1. New build orders will only be offered the PCIe based FICON and OSA.
2. I/O Drawers will be limited to a maximum of 2 drawers unless an I-Listed RPQ,
8P2533, is ordered.
3. I/O Drawers will be assigned in the following sequence: A16, A09, A02, A26.
4. PCIe Drawers will be assigned in the following sequence: A02, A09.
5. I/O drawers can be added concurrently without preplanning.
6. All card assemblies can be added concurrently.
7. The maximum number of channels orderable per Model M05 is 240.
8. All models will require at least one I/O card (ESCON/FICON) or one Coupling
Link (ISC/IFB).
9. PCHID (Physical Channel ID) is a 3 character field identifying the physical
assignment of a channel to a card slot. The PCHID passed by VPD is 4
characters, preceding zero plus the PCHID value. MRPD will drop the leading
zero and pass a 3 character value to Econfig.
10.With each addition of I/O the configurator will issue a pop-up and configuration
output message alerting the customer to the number of I/O slots remaining
before an additional I/O expansion cage is required. Example message, “The
addition of more than xx I/O cards will require an additional I/O expansion
cage/drawer."
12
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
11.Whenever the order adds I/O and the maximum number of I/O cages is
already installed determine how many cage slots remain available for I/O
plugging and issue the following pop-up message, “XX I/O card slots remain
available for I/O Plugging, based on current configuration.”
12.I/O warning messages will be included in the configuration report.
13.Messages are required for new build, upgrade MESs and loose piece MES
configurations with I/O.
Cards will be slotted in the following order:
1. PSC24V
2. ISC Mother Cards
3. Select the card group with the least cards, equal order is Crypto,
OSA-Express, ESCON and FICON.
4. If Crypto: select card with largest ports first and than by latest version first.
5. If OSA-Express: select card type with least cards, equal order is 10Gbe (LR
then SR), Gbe (SX then LX), 1000BaseT. Than order card with largest ports
first, and than by latest version first.
6. If ESCON: Order by largest ports first,
7. FICON: select card type with least cards, equal order is short wave, long
wave, 10KM, 4KM. Then order card with largest ports first, and then by latest
version first.
Repeat step 3 until all groups processed.
The I/O subsystem is designed to offer a balanced system with our processor and
memory enhancements. A new I/O infrastructure is being introduced.
A new I/O drawer (PCIe I/O Drawer) and new form/factor I/O cards are being
introduced to support a direct Peripheral Component Interconnect Express
Generation 2 (PCIe Gen2) infrastructure with increased capacity, granularity, and
infrastructure bandwidth, as well as increased reliability, availability, and
serviceability. New features are being introduced for the SAN and the LAN to
support PCIe Gen2 - FICON Express8S and OSA-Express4S.
Granularity: With the PCIe I/O drawer we are introducing enhanced granularity
features for the storage area network (SAN) and the local area network (LAN).
• For the FICON/zHPF/FCP storage area network: FICON Express8S for single
mode fiber (LX) and multimode fiber (SX) environments with two channels per
feature, and two channel path identifiers (CHPIDs).
• For the 10 Gigabit Ethernet and Gigabit Ethernet local area network:
OSA-Express4S for single mode fiber (LX, LR) and multimode fiber (SX, LR)
environments. The 10 GbE features have one port per feature and one
CHPID. The GbE features have two ports per feature and one CHPID shared
by the two ports.
Increased infrastructure bandwidth: The new I/O infrastructure introduces the
industry standard Peripheral Component Interconnect Express Generation 2
(PCIe Gen2) infrastructure from the processor book to the I/O cards now supports
an 8 gigabytes per second (8 GBps) bus. This new infrastructure offers enhanced
Chapter 1. Technical Description and Features
13
Copyright 2011 IBM Corporation. All rights reserved.
bandwidth in the connection to the processor book as well as the distribution
buses contained in the drawer.
Reliability, Availability, Serviceability: The PCIe I/O drawer is designed with
symmetrical, redundant cooling across all I/O cards and power supplies for
improved RAS. Dual PCIe paths to the system processors from an I/O card
provides enhanced resiliency. Also included are temperature monitoring of critical
ASICs to optimize cooling and reliability.
PCIe based I/O was introduced and the z114 will support a mix of legacy and new
I/O. The PCIe based I/O will be housed in a PCIe I/O drawer. The PCIe I/O
drawer offers improvements in host bus bandwidth, decreased power
requirements, increased I/O plug capacity and concurrent add, remove and
repair.
Drawers and Fanout Cards: The z114 continues with the nodal structure. Each
machine may have one to two drawers installed. Each CEC drawer has four (4)
fanout slots, numbered D1-D8 (slots D3 & D4 are used for OSC and D5 & D6 are
for FSP, not fanout cards), leaving D1 & D2 and D7 & D8 for fanout cards. A fanout
slot can accommodate one fanout card. There are two main fanout card features.
One is a copper HCA, called HCA2-C, and is used to connect to the I/O cages.
The other has optical connections for customer coupling, and has two versions,
HCA2-O for shorter distances and HCA2-O LR for long distances. All HCA fanout
cards have two ports that are numbered J01 and J02.
Three new fanout cards are introduced. One, PCIe fanout, provides a PCIe
interface to the new PCIe I/O drawer and has two ports. The other two are for
customer coupling. They are HCA3-O (2-port) and HCA3-O LR (4-port). For every
two (or four) ports ordered, install one appropriate fanout card.
1.4.1 Hydra Cards - Combined Ordering Rules
Hydra type cards include the following channel types:
• FICON
• OSA
• Crypto
The maximum number of Hydra Type cards (FICON, OSA-Express and PCI
Crypto (PCIXCC 3.0)) that can be ordered in combination is limited to the highest
individual limit in the order. Each card type cannot exceed its personal maximum
while maintaining the combined maximum.
a. Maximum FICON Express4/8/8S cards is 32 per system.
b. The maximum OSA-Express2/3/4S cards is dependent on the mix.
Maximum OSA-E2/3 alone is 24 cards, maximum OSA-E4S alone is 48
cards, OSA-E2/3/4S mixed is determined based on a maximum of 48
PCHIDs).
c. Maximum Crypto Express3 cards are 8 per system.
14
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
1.4.2 Channels - FICON
Table 1. FICON Channel Features
Key
Feature
Description
Comment
c/o
3318
FICON Express4-2C SX
2 Ports
c/o
3321
FICON Express4 LX (10KM)
4 Ports
c/o
3322
FICON Express4 SX
4 Ports
c/o
3323
FICON Express4-2C LX
2 Ports
c/o
3324
FICON Express4 LX (4KM)
4 Ports
c/o
3325
FICON Express8 LX (10KM)
4 Ports - RPQ 8P2534 only
c/o
3326
FICON Express8 SX
4 Ports - RPQ 8P2534 only
nb
0409
FICON Express8S 10KM LX
2 Ports
nb
0410
FICON Express8S SX
2 Ports
Key:
ok = Available for new build or carry over (as available)
c/o = carry forward only, not available new build
nb = Available on new build only
The following can not be installed on a z114:
FC2319
FC2320
FC3319
FC3320
FICON
FICON
FICON
FICON
Express LX
Express SX
Express2 LX
Express2 SX
1.4.2.1 FICON General Rules:
1. FICON Express8S (0409, 0410) will be the GA1 FICON selections.
2. FICON Express8 (3325, 3326) will be available w/8P2534 if there are open
slots available in any installed I/O drawers.
3. FICON Express4 (3318, 3323) will be available w/8P2534 if there are open
slots available in any installed I/O drawers.
4. FICON Express4 (FCs 3321, 3322, 3324) cards will NOT be available to order
on new builds and MESs at GA1. If installed on current system and converting
to zEnterprise the cards will be carried over. The user may decrement the
amount carried forward but will not be allowed to increment the amount.
5. FICON 1.5, 1.75 and Express2 cards will NOT be supported on zEnteprise.
6. Any unsupported FICON cards cards found on the base during an upgrade to
zEnterprise will be deleted and an equal quantity of the latest comparable
FICON offering will be added to the order. The customer will have the
opportunity to reduce, remove or change the configurator selection.
7. The maximum number of FICON cards in any combination is 32 cards. The
maximum number of FICON channels is 128.
Chapter 1. Technical Description and Features
15
Copyright 2011 IBM Corporation. All rights reserved.
1.4.2.2 FICON Express4 General Rules:
Any FICON Express4 found on the base during an upgrade to z114 will be carried
forward. The customer will have the opportunity to reduce, remove or change the
configurator selection.
1.4.2.3 FICON Express8 General Rules:
The FICON Express8 cards for zEnteprise will be offered as a 4 port fully
populated card with either a quantity of four (4) 10KM-LX or four (4) SX modules
Each base card will be shipped with all 4 optic ports plugged.
1. Cards will not be offered as new build selections.
2. Cards will be shown as MES selections only if Cayuga slots are open.
3. Optics are ordered in increments of 4 channels.
4. There is no mixing of optic types on the same card, but there is the possibility
that OEM supplied optics could be used.
5. The OEM optic does not report VPD. If the first optic position does not contain
a CCIN an OEM optic is assumed. MRPD will continue evaluating optic
positions until the first optic CCIN is returned. The first optic CCIN will be used
to translate to the FICON card FC.
6. VPD/MRPD will translate the CCIN combination of optic and mother card to
primary FCs.
CCIN 57E4 -- translates to --> FC 3325 if Daughter card is CCIN 57E0.
CCIN 57E4 -- translates to --> FC 3326 if Daughter card is CCIN 57E1.
7. There is no mixing of optics type on the same card, but different card types are
supported in the same system.
8. Each card feature requires a 54, 55, 56 and 08 record with quantity of 1.
9. The configurator will plug each type of card using the respective primary FC's
(3325, 3326).
1.4.2.4 FICON Express8S
Two FICON Express8S cards will be offered as 2 port fully populated card with
either a quantity of two 10KM-LX or two SX modules Each base card will be
shipped with both optic ports plugged.
With the introduction of the PCIe I/O drawer, several cards will be offered to fill
that drawer. Two FICON Express8S cards will be offered as 2 port fully populated
card with either a quantity of two 10KM-LX or two SX modules Each base card
will be shipped with both optic ports plugged.
16
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
1. The FICON Express8S cards will be the only inital order FICON cards offered.
2. Optics are ordered in increments of 2 channels.
3. There is no mixing of optic types on the same card, but there is the possibility
that OEM supplied optics could be used.
4. The OEM optic does not report VPD. If the first optic position does not contain
a CCIN an OEM optic is assumed. MRPD will continue evaluating optic
positions until the first optic CCIN is returned. The first optic CCIN will be used
to translate to the FICON card FC.
5. VPD/MRPD will translate the CCIN combination of optic and mother card to
primary FCs.
CCIN 58AC -- translates to --> FC 0409 if Daughter card.
CCIN 58AC -- translates to --> FC 0410 if Daughter card.
6. There is no mixing of optics type on the same card, but different card types are
supported in the same system.
7. Each card feature requires a 54, 55, 56 and 08 record with quantity of 1.
8. The configurator will plug each type of card using the respective primary FC's
(0409, 0410).
1.4.2.5 SCSI IPL - List-directed IPL
Also referred to as Open IPL, Enhanced IPL, SCSI IPL or LD-IPL
LD-IPL is required to allow IPL from FCP attached devices. It is mandatory in
SCSI-only environments (i.e. systems without DASD ECKD drives)
The SCSI IPL function/feature will be included as a base function on every z114
system. FC9904 is not required to order and is removed from the z114
configurator.
1.4.2.6 High Performance FICON for System z enhancements
Announced on October 12, 2011
Enhancements for QSAM, BPAM, and BSAM access methods
High Performance FICON for System z (zHPF) has been enhanced to support
certain I/O transfers for workloads using QSAM, BPAM, and BSAM access
methods. Significant I/O performance improvements are expected without the
need for application changes. This builds upon existing zHPF support for VSAM,
Extended Format sequential, zFS, and PDSE data sets and provides support for
these QSAM, BPAM, and BSAM data set types when a new parameter is
specified in the IGDSMSxx member of parmlib:
• Basic nonextended format physical sequential data sets
• Basic and large format sequential data sets
Chapter 1. Technical Description and Features
17
Copyright 2011 IBM Corporation. All rights reserved.
The zHPF enhancement for QSAM, BPAM, and BSAM access methods is
exclusive to the zEnterprise servers and applies to all supported FICON features
(CHPID type FC). It is supported by the IBM System Storage DS8700 and
DS8800 series and z/OS.
See Chapter 2 ‘zHPF Enhancements’ for requirements.
Performance improvements for format writes
zHPF has been enhanced to support format writes. This capability applies to all of
the same data set types that were originally supported by the Modified Indirect
Data Address Word (MIDAW) facility and zHPF, in addition to QSAM, BPAM, and
BSAM data sets described above. The performance value of these
enhancements are highest for small blocks, which are typically used for
databases.
DB2 utilities use format writes. Those utilities that load or restore data into a table
space or index with a 4K page size are expected to experience the most benefit.
The zHPF enhancement for format writes is exclusive to the zEnterprise servers
and applies to all supported FICON features (CHPID type FC). It is supported by
the IBM System Storage DS8700 and DS8800 series and z/OS.
Improvements for zHPF DB2 list prefetch in FICON Express8S
environments
zHPF has been enhanced to provide improvements for DB2 list prefetch
processing.
zHPF list prefetch is supported by the FICON Express4 and FICON Express8
features. However, those features limit the number of discontinuities that a single
zHPF channel program can have to 22. If the number exceeds 22, z/OS splits the
operation into two I/Os. This is applies to 4K pages, since DB2 for z/OS typically
reads 32x4K pages. The FICON Express8S features remove this limitation. The
result is fewer I/Os than when using FICON Express4 or FICON Express
features.
The zHPF enhancement for DB2 list prefetch is exclusive to the zEnterprise
servers and applies to the FICON Express8S features (CHPID type FC)
exclusively. It is supported by the IBM System Storage DS8700 and DS8800
series and z/OS.
For more information on IBM System Storage support of these zHPF
enhancements, refer to Hardware Announcement 111-xxx, IBM System Storage
DS8000 series (M/T 242X) offers higher scalability, additional tiering capabilities,
and additional drive options to address today's price/performance requirements,
dated October 12, 2011.
Prerequisites
The zHPF enhancements require one of the following storage prerequisites:
• IBM System Storage DS8700 level 7.6.2.xx.xx (bundle version
76.20.xxx.xx), or later
• IBM System Storage DS8800 level 7.6.2.xx.xx (bundle version
86.20.xxx.xx), or later
18
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
1.4.3 Channels - OSA
Table 2. OSA Channel Features
Key
Feature
Description
Comment
nb
0404
OSA-Express4S GbE LX
2 Ports - PCIe I/O Drawer
Note: No OSN CHPID support.
nb
0405
OSA-Express4S GbE SX
2 Ports - PCIe I/O Drawer
Note: No OSN CHPID support.
nb
0406
OSA-Express4S 10 GbE LR
1 Port - PCIe I/O Drawer
Note: No OSN CHPID support.
nb
0407
OSA-Express4S 10 GbE SR
1 Port - PCIe I/O Drawer
Note: No OSN CHPID support.
c/o
3362
OSA-Express3 GbE LX
4 Port
c/o
3363
OSA-Express3 GbE SX
4 Port
c/o
3364
OSA-Express2 GbE LX
2 Port
c/o
3365
OSA-Express2 GbE SX
2 Ports
c/o
3366
OSA-Express2 1000BaseT-EN
2 Ports, RJ45 Connector
CHPID types OSC, OSD, OSE, OSN
ok
3367
OSA-Express3 1000BASET-EN
4 Port card, 2 ports per PCHID/CHPID.
CHPID types OSC, OSD, OSE, OSN, OSM
ok
3369
OSA-Express3 1000BASET-EN
2 Port card, 2 ports per PCHID/CHPID
CHPID types OSC, OSD, OSE, OSN, OSM
c/o
3370
OSA-Express3 10 GbE LR
2 Ports
CHPID type OSD and OSX supported
c/o
3371
OSA-Express3 10 GbE SR
2 port
CHPID type OSD and OSX supported
c/o
3373
OSA-Express3-2P GbE SX
2 Ports
Key:
ok = Available for new build or carry over (as available)
c/o = carry forward only, not available new build
nb = Available on new build only
1.4.3.1 OSA Express4S General Rules:
The PCIe based OSA cards, called OSA-Express4S, will replace OSA-Express3
as the primary networking features. Like OSA-Express3, OSA-Express4S will
have two GbE ports per PCHID, and one 10 GbE port per PCHID.
There is no OSA-Express4S 1000BaseT feature on z114.
1. OSA-Express4S and the OSA-Express3 1000BASE-T cards will be the only
selections offered for a new build configuration.
2. OSA-Express 2 cards can not be ordered new or as a MES but will be allowed
to carry forward on the upgrade to z114. The user may decrement the quantity
of the carried forward features but may not increment.
3. The exception is OSA-Express2 10GbE LR FC 3368, this card will not be
carried forward. If found on the base during an upgrade to z114 FC 3368 will
be deleted and an equal quantity of the latest comparable OSA offering will be
Chapter 1. Technical Description and Features
19
Copyright 2011 IBM Corporation. All rights reserved.
added to the order. The customer will have the opportunity to reduce, remove
or change the configurator selection. Tagging for pricing purposes will be A/D.
Feature Conversion tagging will not be offered.
4. OSA-Express3 cards, with the exception of OSA-Express3 1000BASE-T will
not be offered as new build selections.
5. OSA-Express3 cards will be shown as selections via 8P2534 only if I/O
Drawer slots are open.
6. Earlier cards, OSA Express 1.5 and 1.75 cards will not be carried forward on
the upgrade to z114. These cards if found on the base during an upgrade to
z114 will be deleted and an equal quantity of the latest comparable OSA
offering will be added to the order. The customer will have the opportunity to
reduce, remove or change the configurator selection. Tagging for pricing
purposes will be A/D. Feature Conversion tagging will not be offered.
7. Maximum number of OSA-Express2/3/4S cards in any combination is 48
cards. The maximum number of OSA-E channels that can be configured is 96.
8. The configurator will calculate the quantity of cards required based on number
of ports specified for each feature. Ports are ordered in increments of 1, 2 or 4
ports (2 PCHIDs). See table above for number of ports per card.
1.4.4 Cryptography
Crypto Express2 cards (FC 0863, FC 0870) are not supported on the z114 and
will not be carried forward. Configurator action will be to delete FC 0863 or FC
0870 found on base and add a comparable number of most respective 2P or 1P
Crypto card offering. Tagging for pricing purposes is A/D. Feature conversion
pricing will not be offered.
Table 3. Cryptography Features
Key
Feature
Description
Comment
ok
0841
TKE Workstation
ok
0867
TKE 7.1 LIC
ok
0884
TKE additional Smart Cards
ok
0885
TKE Smart Card Reader
ok
0864
Crypto Express3
2 engines per card. Plugs in I/O drawer.
ok
0871
Crypto Express3-1P
1 engine per card. Plugs in I/O drawer.
ok
3863
CPACF Enablement
DES/TDES
Smart Card Reader Blank Cards 10 pack
Key:
ok = Available for new build or carry over (as available)
c/o = carry forward only, not available new build
nb = Available on new build only
1.4.4.1 FC 3863 (CPACF Enablement)
1. Machines will ship with a minimum level of cryptographic function, SHA-1,
resident in CP hardware, always enabled.
2. To enable the CP Assist CPACF DES/TDES Enablement FC 3863 must be
ordered. FC 3863 is no charge.
20
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
3. There are no prerequisites to ordering/using CPACF DES/TDES Enablement,
however keep in mind that CPACF DES/TDES Enablement is a prerequisite to
ordering/using the PCI adapter cards.
4. A CP machine downgraded to a zero CP machine is not required to disable
the CPACF function. LINUX applications are also capable of utilizing the
CPACF function.
5. Configuration LICCC will be loaded prior to ship for a New Builds. CPACF
DES/TDES enablement is contained in the same LICCC record as the PU
features and memory. MESs will ship via CD (same CD used for PU/Memory
loads) or Web download.
6. CPACF DES/TDES Enablement is managed using the same panels and
procedures as a CP upgrade.
7. VPD will recognize the presence of CPACF DES/TDES Enablement when the
CFGMGR reads the SEEPROM for Book 0 and finds it has been loaded. At
that time the record will be added into VPD indicating the feature.
8. To utilize the function the customer must enable it via the SE panel. The
function may also be disabled from this panel. This action is not a concern to
the configurator.
9. To remove the CPACF DES/TDES Enablement function, in the event the
machine is sold, an order must be placed to deselect (set to zero) the feature.
The option to delete CPACF DES/TDES Enablement is only presented if no
PCI adapter cards are installed or after all PCI adapter cards have been
deleted.
10.The configurator will issue FC 3863 with a delete tag and FPL340 with an add
tag. LICCC will reload the system data without the CPACF DES/TDES
Enablement function included.
1.4.4.2 FC 0864 (Crypto Express3)
1. Card carries forward on upgrade into z114.
2. Card is plugged into the I/O Drawer.
3. Two Crypto engines per card.
4. FC 3863 is a prerequisite
5. This card is sensed by VPD
6. There is an initial minimum two card selection for this card after which
increments are by 1 card.
7. Min/max is 0/8 cards.
1.4.4.3 FC 0871 (Crypto Express3-1P)
1. Card is plugged into the I/O Drawer.
2. Single Engine card
3. FC 3863 is a prerequisite
4. This card is sensed by VPD
5. There is an initial minimum two card selection for this card after which
increments are by 1 card.
6. Min/max is 0/8 cards.
Chapter 1. Technical Description and Features
21
Copyright 2011 IBM Corporation. All rights reserved.
1.4.4.4 TKE workstation & Code – General Rules
• Selection for new TKE workstations will be FC 0841 (GuanYin).
• The ship level TKE code will be FC 0867 TKE 7.1 LIC.
• The Smart card reader selection will be FC 0885 (Omnikey unit).
• The selection for additional Smart Card blanks will be FC 0884 (NXP).
1.4.4.5 Crypto Configurator Rules
• If the base TKE workstation is a Jaguar (FC 0839) or Guandu (FC 0840) the
units cannot not be carried forward. Configurator action will be to delete FC
0839/0840 and add a comparable number of FC 0841 (GuanYin).
• On an MES or M/T upgrade when the base TKE hardware is Guanyin (0841)
or greater and the base code level is less then what is currently shipping the
latest code level will be added to the order to ensure the customer has the
ability to communicate with the z114.
• All the qualifying base level TKE code FCs less then the most current will be
deleted and an equal number of current level TKE Code FCs will be added.
Tagging for pricing purposes is A/D.
• If the customer elects to upgrade the installed TKE hardware to the latest
hardware offering or adds a new TKE and the base TKE(s) already had the
latest level of TKE code installed, the configurator will issue with ADD tag the
latest level of TKE code for every TKE in the configuration. This will prevent an
install problem in case the base TKE code CD can not be located at the
customer location.
• When the first Crypto card is added and if the base TKE (which was carried
over on an upgrade) is not at the latest TKE code level (for whatever reason)
the configurator will issue with ADD tag the latest level of TKE code for all
TKEs assigned to that system.
• If the base TKE does not reflect a TKE Code FC then the configurator will offer
a selectable checkbox for the latest level of code rather than force on the FC.
• Transaction tagging for pricing purposes in all the above scenarios is
Delete/Add.
• FC 0887(OMNIKey SCR) and FC 0888 (DataKey) SCR blank cards will not be
carried forward on the upgrade to z114. The configurator will delete FCs 0887
and 0888 and issue a warning message, “FC 0887 and 0888 are not
supported on z114. Visit the TKE tab to order a replacement.”
1.4.4.6 FC 0841 (TKE 7.0 Workstation - GuanYin)
1. A LAN on board, single Ethernet will be the only networking selection offered.
2. The TKE operating system will be Linux based.
3. Can be used to control z10 EC and BC, z9 EC and BC, and z990 servers.
4. The feature is not sensed.
5. Min/max is 0/10.
1.4.4.7 FC 0867 (TKE 7.1 LIC)
The Trusted Key Entry (TKE) 7.1 level of Licensed Internal Code (LIC) is installed
in a TKE workstation (#0841). TKE 7.1 LIC is a no-charge enablement feature
which is loaded prior to shipment when a TKE workstation is ordered. The TKE
7.1 LIC includes support for the Smart Card Reader (#0885).
• Minimum: None.
• Maximum: Ten (10).
22
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
• Prerequisites: TKE workstation (#0841).
• Prerequisites: CP Assist for Cryptographic Function (#3863); Crypto
Express3 (#0864), or Crypto
• Express3-1P (#0871).
• Compatibility Conflicts: TKE workstations with TKE 7.1 LIC can also be
used to control z114, z196, z10 EC, and z10 BC servers.
• Customer Set-up: No.
• Limitations: None.
• Field Installable: Yes. Parts removed as a result of feature change become
the property of IBM.
1.4.4.8 FC 0884 (TKE additional smart cards)
1. These blanks support both Omnikey and Kobil SCRs
2. Feature provides the ability to order an additional 10 blank smart cards.
3. Requires TKE 7.1 Code level or greater be loaded on the TKE that the SCR
using these cards will be attaching to. The configurator will add the latest code
level FC for every TKE in base if less than 7.0 code and FC 0884 is being
ordered.
4. FC 0884 is available for order on new builds as well as MES.
5. No VPD.
6. There is a charge for this feature.
7. Min/max is 0/99.
1.4.4.9 FC 0885 (Smart Card Reader “OmniKey SCR”)
1. The smart card reader (SCR) is an optional security device that attaches to
the TKE workstation. The SCR provides swipe card function thus further
restricting access to the TKE.
2. The MFI B/M will contain two Smart Card Readers, two serial port ‘Y’
adapters, two serial cables plus 20 blank smart cards.
3. FC 0885 is orderable on new builds as well as MES.
4. A grey box message on the panel will display the following information, “FC
0885 contains two smart card readers and 20 blank cards.”
5. Requires TKE 7.1 Code level or greater to be loaded on the TKE that the SCR
is attaching to. The configurator will add the latest code level FC for every TKE
in base if less than 7.1 code and FC 0885 is being ordered.
6. Prerequisite are; a PCIxCC, TKE workstation and TKE code
7. Min/max is 0/10.
8. A mix of Kobil and OmniKey SCRs on a single TKE is not supported.
1.4.5 Channels - ESCON
Table 4. ESCON Channel Features
Key
Feature
Description
Comment
ok
2323
16 Port ESCON Card
Not orderable, configurator
generated feature
ok
2324
ESCON Channel Ports (4)
qty 1 = 4 ports enabled
Key:
ok = Available for new build or carry over (as available)
c/o = carry forward only, not available new build
nb = Available on new build only
Chapter 1. Technical Description and Features
23
Copyright 2011 IBM Corporation. All rights reserved.
1.4.5.1 General Rules:
1. ESCON channels have a maximum of 240 channels (16 cards). These may be
ordered new or carried forward.
2. After the first pair, ESCON cards are installed in increments of one.
3. The configurator will assign up to 15 of the 16 ports on the card. The 16th port
is used as a spare.
4. ESCON channel function is ordered at the port level (FC2324) and must be
ordered in increments of four (4). FC2324 represents four ports, i.e. FC2324,
qty. 2 equals 8 ports.
5. It is not required that the channels within a group are assigned to the same
card.
6. The assignment of each port will be determined by the configurator based on
the cards on the system and the number of available ports.
7. The configurator will place additional cards as required based on the number
of channels ordered.
1.4.5.2 New Builds:
1. When channels are ordered a minimum of four ports (FC2324) are required.
The ports will be balanced across two (16 port) channel cards (FC2323).
2. Orders requiring more then four (4) ports will be balanced across the cards.
3. After the first pair, 16 port cards will be plugged in increments of one.
1.4.5.3 Channel MES:
Handling FC2323 ESCON Cards with Ports Failures
1. For an ESCON MES involving FC2323 any available port on the 16 port card
will be assigned. Available means not assigned and not reporting a failure.
2. Failed ports on FC2323 will be handled in two ways:
a. When a sparing action has occurred and the last port on a card is assigned
(meaning no spare remains) a message will be issued on output report
indicating that a "no spare" condition exists. An asterisk (*) in the comment
field will indicate the condition; the message will read "The last unused port
is being activated with this MES. No spare ports remain on this card."
b. Card(s) will be repaired (ROLLED) if the number of failed ports on the
card(s) would satisfy the full MES or repairing the card(s) will prevent
additional hardware, card or cage, from being driven out to satisfy MES.
Only the number of cards needed to satisfy the MES will be replaced.
1.4.6 Channels - Coupling Links
General Rules:
Coupling features include:
• ISC-3
This will be the last System z server that will support ISC-3 coupling links.
• IFB (InfiniBand coupling links)
ICB is not offered.
24
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Combined Ordering Rules:
1. The ordering limitation for maximum number of combined ICs, IFBs and ISC-3
links has been removed for z114.
2. The maximum number of Coupling CHPIDs per server is 128.
3. Each feature cannot exceed its personal maximum.
• Maximum ISC links are 48 per system.
• See the table on next page for other maximums.
Maximum Coupling Links and CHPIDs
Server
1x IFB
(HCA3-O LR)
12x IFB
&
12x IFB
(HCA3-O)
1x IFB
(HCA2-O LR)
12x IFB
(HCA2-O)
IC
ICB-4
ICB-3
ISC-3
Max
External
Links
Max
Couplin
CHPIDs
z196
48
M15 - 32*
32
M15 - 16*
32
M15 - 16*
CF only
32
M15 - 16*
32A
N/A
N/A
48
104 (1)
128
z114
M10 - 32*
M05 - 16*
M10 - 16*
M05 - 8*
M10 - 12
M05 - 8*
CF only
M10 - 16*
M05 - 8*
32
N/A
N/A
48
M10 (2)
M05 (3)
128
z10 EC
N/A
N/A
32
E12 - 16*
32
E12 - 16*
32
16
(32/RPQ)
N/A
48
64
64
z10 BC
N/A
N/A
12
12
32
12
N/A
48
64
64
z9 EC
N/A
N/A
N/A
16
HCA1-O
S08 - 12
32
16
16
48
64
64
z9 BC
N/A
N/A
N/A
12
HCA1-O
32
16
16
48
64
64
1.
A z196 M49, M66 or M80 supports a maximum of 96 extended distance links (48 1x IFB and 48 ISC-3) plus 8 12x IFB links
A z196 M32 supports a maximum of 96 extended distance links (24 1x IFB and 48 ISC-3) plus 4 12x IFB links*.
A z196 M15 supports a maximum of 72 extended distance links (48 1x IFB and 48 ISC-3) with no 12x IFB links*.
2.
A z114 M10 supports a maximum of 72 extended distance links (24 1x IFB and 48 ISC-3) with no 12x IFB links*.
3.
A z114 M05 supports a maximum of 56 extended distance links (8 1x IFB and 48 ISC-3) with no 12x IFB links*.
Note: Effective December 31, 2011 IBM System z will withdraw from marketing the following feature on IBM zEnterprise 19
HCA2-O LR fanout for 1x IFB (FC0168)
* Uses all available fanout slots. Allows no other I/O or coupling.
Chapter 1. Technical Description and Features
25
Copyright 2011 IBM Corporation. All rights reserved.
The following table depicts feature codes associated with coupling links.
Table 5. Coupling Link Channel Features
Key
Feature
Description
Comment
ISC (Intersystem Channel)
ok
0217
ISC-M
Mother Card
ok
0218
ISC-D
Daughter Card (1-2 links)
ok
0219
ISC-3 Link activated on FC 0218
Activated Link
ok
8P2197
ISC-D 10 t o20 KM 2 Ports
Daughter card (both links activated) for
extended distance (1 Gb/s)
ICB (Integrated Cluster Bus) - Not offered
IB (Infiniband Coupling)
ok
0162
IB Link Copper
2 port hub card
Source: CEC Book
Destination: Internal/External
ok
0163
IB Link Optical
2 port hub card
Source: CEC Book
Destination: External
c/o
0168
HCA2-O LR port
fanout card Optical
Source: CEC Book
Destination: External
Not available after GA2 on a new build.
Effective December 31, 2011 IBM System z
will withdraw from marketing the following
feature on IBM zEnterprise 196: HCA2-O
LR fanout for 1x IFB (#0168)
nb
0170
HCA3-O LR fanout for 1x
InfiniBand
Source: CEC Book
Destination: External
nb
0171
HCA3-O fanout for 12x InfiniBand
Source: CEC Book
Destination: External
Key:
ok = Available for new build or carry over (as available)
c/o = carry forward only, not available new build
nb = Available on new build only
1.4.6.1 ISC Links
General Rules:
1. Feature Code 0218 is a 1/2 GB combo ISC daughter card
2. There are two links per daughter card. Two daughter cards per mother card.
3. These links can function up to 10 km.
4. ISC links can be ordered in increments of one (1), however, it is recommended
that initial orders (first time order of this feature) have two. Maximum links
order able is 48.
5. When two ISC links (FC 0218) are ordered (during the initial order) two Mother
cards (FC 0217) are also ordered and the links are balanced across the two
mother cards.
26
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
6. The configurator will allow the number of mother cards to be incremented up
to the maximum (12) with the restriction that the number of mother cards
cannot exceed the number of daughters.
7. Links are activated (FC 0219) as required and will require activation LICCC to
be issued.
8. RPQ 8P2197 (20 KM at 1 Gbps) is a "I listed" (but handled as "P" - no
approval necessary) RPQ order able via the configurator.
9. The RPQ 8P2197 daughter card has two links per card as well, however, both
links are active when installed and do not need to be activated via microcode.
1.4.6.2 IB (InfiniBand)
InfiniBand technology positions IBM and it’s customers to move all of it’s parallel
sysplex support to a single type of interface which can provide high speed
interconnection at short distances (replacing ICB), longer distance fiber optic
interconnection (replacing ISC), and interconnection between partitions on the
same system without external cabling (replacing IC).
General Rules
1. The coupling tab will be renamed to IFB as ICB will no longer be offered. Only
the external IFB Coupling selections will be presented for selection on this tab.
2. The external coupling selections will be FC0163, for z9 connectivity, and
FC0171 and FC0170. FC0168 will change to carry forward only.
3. IFB links are ordered in increments of two.
4. At GA1 the maximum number of IFB links in any combination is 16 per system
(max 4 card features) on the M05 and 32 per system (max 8 card features) on
the M10.
5. For external IFB optical coupling IGS Cable Services will be used to order an
appropriate industry standard cable. These cables will not be offered in the
configurator.
6. If STP, FC1021, is not configured then the first selection of ISC or IFB features
will default on the selection of FC1021. With the removal of ETR support on
the z114, STP is required to support ISC/IFB. The customer will not be allowed
to deselect FC 1021.
7. For internal connections the configurator will calculate the required quantity of
copper links, FC0162, based on the I/O selections made by the customer and
add to the order.
1.4.7 Geographically Dispersed Parallel Sysplex (GDPS)
This section lists the GDPS enhancements being made with the October 12, 2011
announcement.
1.4.7.1 GDPS support for zEnterprise System
With the zBX exploitation for distributed servers becoming more prevalent in
production environments, IBM is enhancing GDPS, its automated end-to-end
continuous availability / disaster recovery (CA / DR) solution with support for the
zEnterprise environment. This builds upon the existing GDPS ability to:
• Manage data on distributed systems using its Open LUN Management
Chapter 1. Technical Description and Features
27
Copyright 2011 IBM Corporation. All rights reserved.
• Provide a business continuity solution across z/OS, z/VM, and Linux
applications on System z (xDR)
• Provide coordinated planned/unplanned site switches using the Distributed
Cluster Management (DCM) function.
The GDPS support for the zEnterprise System includes:
• Disaster Recovery with synchronous remote copy up to 300 km
GDPS/PPRC on z/OS together with either Tivoli System Automation
Application Manager (AppMan) or Veritas Cluster Server (VCS) on the zBX
can be used to support a synchronous remote copy target up to 300 km away.
This is an increase from the previously announced distance for AppMan of 100
km, allowing more flexibility where the DR site can be positioned. Note that
the near-continuous availability capability is still limited to 200 fiber km.
• Application CA / DR at unlimited distance
GDPS/XRC or GDPS/GM on z/OS together with VCS running on a zBX blade
can be used to support an asynchronous remote copy target at unlimited
distances away.
• xDR extension to support z/VSE
GDPS extends its xDR capability to provide availability for z/VSE. Using
heartbeat signals, GDPS can detect if a z/VSE guest under z/VM is
unavailable and restart it in place.
• Reduced HyperSwap impact and improved scalability
In addition to addressing the heterogeneous requirements with zBX, GDPS is
reducing the impact of a HyperSwap event by having the disk subsystem
proactively notify the host system that it is entering recovery processing in
order to trigger a HyperSwap. This reduces outage time for certain events by
allowing the former primary PPRC disk to complete its recovery while allowing
host I/Os to proceed on the swapped-to disk. This is supported by the IBM
System Storage DS8700 and DS8800 series.
Additionally, the IBM DS8700/DS8800 disk subsystems in the GDPS
configuration will notify each of the attached hosts of PPRC suspension
events at the Logical Subsystem (LSS) level instead of at the individual
PPRCed device level, greatly reducing the message traffic between the disk
subsystems and the attaching hosts and providing greater scalability during
HyperSwap and Freeze events.
28
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
1.5 Other Feature Codes
Some runs of eConfig may result in some new features that are not familiar.
These are related to pricing.
Features
Description
Comments
FC0001
MTU 1-D
Diagonal Upgrade
FC0002
MTU 100-D
Diagonal Upgrade
FC0003
MTU 1-V
Vertical upgrade or initial order
FC0004
MTU 100-V
Vertical upgrade or initial order
FC0005
GTU 1-D
Diagonal Upgrade
FC0006
GTU 100-D
Diagonal Upgrade
FC0007
GTU 1-V
Vertical upgrade
FC0008
GTU 100-V
Vertical upgrade
To address a shortcoming in the ePricer tool the configurator will alert the Pricer
when a particular order’s price needs to be adjusted. Several flag FCs will be
used to alert the Pricer to the fact that an order’s reference price (one price per
capacity setting regardless of the book quantity) doesn’t cover the cost of the
order configuration and that the price needs to be “uplifted”.
With these feature codes on the order the sales bid cannot be processed through
ePricer without a pricing approval / override. The enhancements added with z114
assist the Pricer by passing moré information regarding the extent of the capacity
deltas.
1.5.1 Other
1.5.1.1 2819-GBC
See U.S. announcement letter 111-123, dated July 12, 2011 for the z196.
See U.S. announcement letter 111-124, dated July 12, 2011 for the z114. The
zEnterprise 114 uses 2819-GBC.
The z10 EC uses 2819-EEC. The z10 BC uses 2819-EBC. The z10s have
announced that they will be withdrawn from marketing on June 30, 2012.
IBM System z is implementing a machine type, model, and feature structure for
the delivery of site preparation and installation support materials on zEnterprise
196, zEnterprise 114, System z10 EC, and System z10 BC servers.
This machine type, its models, and its feature codes are for administrative
purposes only and are no charge. Through this ordering vehicle, IBM will deliver
certain required materials for System z servers.
Machine shipments of initial order or frame roll MES upgrades into z114, include
materials required for service and in the case of water models, materials required
Chapter 1. Technical Description and Features
29
Copyright 2011 IBM Corporation. All rights reserved.
for install. These materials are deemed not compliant with REACH laws making
them unshippable into countries within the European Union. To learn more about
“REACH laws”, search the internet.
To comply with REACH laws the required chemical materials (benzotriazole
(BTA) corrosion inhibitor, wipes, grease) must be shipped from Montpelier when
the world trade box shipment originates from Singapore or offload from
Poughkeepsie. To split the sourcing of parts a new machine type and model has
been introduced (2819-GEC). Under each model, feature codes will be assigned,
as needed, to ship parts.
2819-GEC feature codes:
9882 - Water Cooled Machines
9883 - Air Cooled Machines
Note: USA shipments also add REACH.
1.5.1.2 RPQ 8P2534
With the introduction of new features on the IBM® zEnterpriseTM 196 and IBM
zEnterprise 114 - FICON® Express8S features to support the storage area
network (SAN), and OSA-Express4S 10 Gigabit Ethernet and Gigabit Ethernet
features to support the local area network (LAN) - IBM is removing the FICON
Express8, FICON Express4-2C, and OSA-Express3 10 Gigabit Ethernet and
Gigabit Ethernet features as optional features for most zEnterprise System
machines.
The FICON Express8, FICON Express4-2C, and OSA-Express3 10 Gigabit
Ethernet and Gigabit Ethernet features remain available only by request for
price quotation (RPQ), and only for certain qualifying machine configurations.
The new FICON Express8S and OSA-Express4S 10 Gigabit Ethernet and Gigabit
Ethernet features are designed for use in the zEnterprise 196 new PCIe I/O
drawers (#4003, #4006) and the zEnterprise 114 new PCIe I/O drawer (#4003).
Under specific circumstances the FICON Express8, FICON Express4-2C, and
OSA-Express3 10 Gigabit Ethernet and Gigabit Ethernet features are available
for installation in the zEnterprise 196 I/O cages (#4002, #4005) or I/O drawers
(#4000, #4004) or the zEnterprise 114 I/O drawer (#4000).
When the specific circumstances are met, the FICON Express8, FICON
Express4-2C, and OSA-Express3 10 Gigabit Ethernet and Gigabit Ethernet
features are available by request for price quotation (RPQ).
The FICON Express4-2C features are available on the z114. They are not
applicable to the z196
30
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
RPQ 8P2534 – Access to Legacy IO
MES/U pgrade
with b ase machine containing
legacy I/O card types
Slots available in
legacy I/O d rawer
or I/O cage
(z196/z114)?
NO
Yes
Slots available
In PCIe I/O
D rawer?
Yes
Must order
PCIe I/O Drawer
FICON Express8S
OSA-Express4S
NO
Order RPQ 8P2534
allows selectio n of add itional supported
legacy F ICON and OSA card types
(FICON Express4, FICON Express8, and OSA-Express3)
RPQ 8P2534 notes:
1.RPQ is only available for MES and not New Build, MO, or Hybrids
2.Does not allow for the addition of I/O drawers, only allows for existing drawers to be filled with current legacy I/O cards.
1
1.5.1.3 Month, Day, Hour, Minute Indicator
When there is a configuration proposal that affects more then one machine type
order, for example, the z196 and the zBX, the configurator will add to each piece
of the order four identical date/time FCs with quantities. The matched FCs and
matched quantities will indicate that the orders are linked and will be used by the
IBM Order Department to help detect an alteration to either piece of a linked
order.
• FC0660 Month Indicator
• FC0661 Day Indicator
• FC0662 Hour Indicator
• FC0663 Minute Indicator
Chapter 1. Technical Description and Features
31
Copyright 2011 IBM Corporation. All rights reserved.
32
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 2. Software Requirements
The IBM z114 Processor only supports operation in Logically Partitioned Mode
(LPAR). There are no provisions for operating the IBM z114 in Basic Mode.
2.1 Operating System Support Overview
2.1.1 Advanced Workload License Charges
For a z114 in a plex, an the agreement for Advanced Workload License Charges
must be in effect if z/OS or z/TPF will run on the z114.
Note: this excludes customers who will remain on PSLC pricing.
The "ICA Attachment for System z Advanced Workload License Charges" was
deployed worldwide through model contract number INTC-8538 (US form number
is Z125-8538), and its associated "IBM Exhibit for Advanced Workload License
Charges" was deployed worldwide through model contract number INTC-8539
(US form number is Z125-8539).
Advanced Workload License Charges (AWLC) is a monthly license pricing metric
designed to support today's on demand business requirements. IBM zEnterprise
114 (z114) servers may have AWLC when in a fully qualified Parallel Sysplex
consisting entirely of zEnterprise servers.
See http://www.ibm.com/systems/z/resources/swprice/mlc/awlc.html.
2.1.2 Advanced Entry Workload License Charges
For z114 NOT in a plex, an agreement for Advanced Entry Workload License
Charges must be in effect if z/OS or z/TPF will run on the z114.
Note: this excludes customers who will remain on PSLC pricing.
Coinciding with the announcement of the IBM zEnterprise 196 (z196) server, IBM
introduced a new software pricing structure called Advanced Entry Workload
License Charges (AEWLC). The AEWLC pricing metric leverages the reporting
mechanisms and existing Millions of Service Units per hour (MSU) tiers of the
Entry Workload License Charges (EWLC) pricing metric and the Midrange
Workload License Charges (MWLC) pricing metric while extending the software
price performance provided by the EWLC and MWLC tiers. AEWLC applies only
to eligible z/OS, z/TPF, and z/VSE operating systems and their associated
middleware programs when running on a z114 server. For additional AEWLC
information, refer to Software Announcement 211-250, (RFA54941) "Advanced
Entry Workload License Charges offers price / performance for the IBM
zEnterprise 114," dated July, 12, 2011.
When a z114 server is in an actively coupled Parallel Sysplex, you may elect
aggregated Advanced Workload License Charges (AWLC) pricing or aggregated
Parallel Sysplex License Charges (PSLC) pricing, subject to all
Chapter 2. Software Requirements
33
Copyright 2011 IBM Corporation. All rights reserved.
applicable terms and conditions.
For additional information on AWLC, refer to Software Announcement 210-238,
(RFA53175) "Advanced Workload License Charges offers price / performance for the
IBM zEnterprise 196," dated July, 22, 2010.
2.1.3 Overview
The Operating System support plan for the z114 is intended to provide the
broadest practical coverage of hardware features across currently supported
software releases.
The Operating Systems will, in general, enhance your value of the z114 hardware
by delivering increased function, scalability and performance across a broad
range of workloads.
2.1.3.1 z/OS discovery and autoconfiguration for FICON channels:
With z114 and z/OS, a new function, z/OS discovery and autoconfiguration
(zDAC), is designed to automatically perform a number of I/O configuration
definition tasks for new and changed disk and tape controllers connected to a
switch or director when attached to a FICON channel. When new controllers are
added to an I/O configuration or changes are made to existing controllers, the
system is designed to discover them and propose configuration 1 changes based
on a policy you define in the hardware configuration dialog (HCD). Your 1 policy
can include preferences for availability and bandwidth including parallel access
volume (PAV) definitions, control unit numbers, and device number ranges.
zDAC is designed to perform discovery for all systems in a sysplex that support
the function. The proposed configuration will incorporate the current contents of
the I/O definition file (IODF) with additions for newly installed and changed
control units and devices. zDAC is designed to help simplify I/O configuration on
z114 running z/OS and reduce complexity and setup time. zDAC applies to all
FICON features supported on z114 when configured as CHPID type FC and is
supported by z/OS.
2.1.3.2 Access to high-speed intraserver network - HiperSockets
A single logical partition can now connect up to 32 HiperSockets, double the
number of HiperSockets previously supported. With HiperSockets, you have
independent, integrated, virtual local area networks (LANs). No physical cabling
or external connections are required. HiperSockets supports Internet Protocol
version 4 (IPv4) and IPv6. Up to 32 HiperSockets are supported by z/OS, z/VM,
zVSE, and Linux on System z.
2.1.3.3 HiperSockets network traffic analyzer (HS NTA) for Linux on
System z environments:
An enhancement to the HiperSockets architecture is designed to help simplify
problem isolation and resolution. You now have the capability to trace Layer 2
and Layer 3 HiperSockets network traffic.
HS NTA allows Linux on System z to control the trace for the internal virtual LAN,
to capture the records into host memory and storage (file systems). Linux on
System z tools can be used to format, edit, and process the trace records for
analysis by system programmers and network administrators. Refer to the
34
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Software requirements section. HiperSockets network traffic analyzer is
supported on IBM zEnterprise 114 and IBM System z10.
2.1.3.4 For network performance- inbound workload queuing:
z/OS workloads are becoming more diverse; each type of workload may have
unique service level requirements. OSA-Express-3 introduces inbound workload
queuing (IWQ), which creates multiple input queues and allows OSA to
differentiate workloads "off the wire" and then assign work to a specific input
queue (per device) to z/OS. With each input queue representing a unique type of
workload, each having unique service and processing requirements, the IWQ
function allows z/OS to preassign the appropriate processing resources for each
input queue. This approach allows multiple concurrent z/OS processing threads
to then process each unique input queue (workload), avoiding traditional
resource contention. In a heavily mixed workload environment, this "off the wire"
network traffic separation provided by OSA-Express3 IWQ reduces the
conventional z/OS processing required to identify and separate unique
workloads, which results in improved overall system performance and scalability.
A primary objective of IWQ is to provide improved performance for
business-critical interactive workloads by reducing contention created by other
types of workloads. The types of z/OS workloads that are identified and assigned
to unique input queues are:
1. z/OS Sysplex Distributor traffic - Network traffic that is associated with a
distributed dynamic virtual IP address (DVIPA) is assigned a unique input
queue allowing, the Sysplex Distributor traffic to be immediately distributed to
the target host.
2. z/OS bulk data traffic - Network traffic that is dynamically associated with a
streaming (bulk data) TCP connection is assigned to a unique input queue
allowing, the bulk data processing to be assigned the appropriate resources
and isolated from critical interactive workloads.
IWQ is supported on z114 and System z10 and is exclusive to OSA-Express3
CHPID types OSD and OSX (exclusive to z114). IWQ is also supported by the
z/OS operating system and by z/VM for guests. This applies to z114 and z10.
2.1.3.5 For network management - query and display OSA
configuration:
Previously, OSA-Express system architecture introduced the capability for
operating systems to dynamically register the OSA configuration. This approach
significantly improved the OSA-Express usability by reducing the burden placed
on the system administrator to manually configure OSA-Express for each unique
operating system configuration. Traditionally, the Open Systems Adapter Support
Facility (OSA/SF) has provided the administrator with the ability to monitor the
OSA configuration.
As additional complex functions have been added to OSA, the ability for the
system administrator to display, monitor, and verify the specific current OSA
configuration unique to each operating system has become more complex.
OSA-Express3 introduces the capability for the operating system to directly query
and display the current OSA configuration information (similar to OSA/SF). z/OS
exploits this new OSA capability by introducing a new TCP/IP operator command
called Display OSAINFO. Display OSAINFO allows the operator to monitor and
Chapter 2. Software Requirements
35
Copyright 2011 IBM Corporation. All rights reserved.
verify the current OSA configuration, which helps to improve the overall
management, serviceability, and usability of OSA-Express3.
Display OSAINFO is exclusive to OSA-Express3 CHPID types OSD, OSM, and
OSX, the z/OS operating system, and z/VM for guest exploitation.
2.1.3.6 New zArchitecure Instructions
In support of the z114 server, the High Level Assembler introduced new
mnemonics for the new machine instructions. The new mnemonics may collide
with (be identical to) the names of Assembler macro instructions you use. In the
event of such collisions, the Assembler's default opcode table (UNI) will treat
specification of these names as instructions, probably causing Assembler error
messages and possibly causing generation of incorrect object code.
If you write programs in Assembler Language, you should compare the names of
Assembler macro instructions you use to the new machine instructions
(documented in the Principles of Operation SA22-7832-08) to identify any such
conflicts or collisions which would occur. Identical names will cause Assembler
errors or the generation of incorrect object code when you assemble your
programs following installation of the enabling PTF.
If a conflict is identified, take one of these actions:
1. Change the name of your macro instruction.
2. Specify PARM='…OPTABLE(YOP)…' (or some other earlier opcode table).
3. Specify a separate ASMAOPT file containing assembler options such as in the
previous method (this method requires no changes to source code or JCL).
4. Add as the first statement of your source program: *PROCESS
OPTABLE(YOP)
5. Specify the PROFILE option either in JCL or the ASMAOPT file, and the
specified or default member of the SYSLIB data set is copied into the front of
the source program.
6. If you must use both a new instruction and a macro with the same name in an
assembly, you can use the following technique (where XXX is a sample
mnemonic):
Note: Refer to Technical document TD105581 in www.ibm.com/support/techdocs
for an "as is" tool to help identify conflicts.
2.1.3.7 SMP/E 3.5
SMP/E 3.5 provides a function which greatly simplifies the identification,
verification, acquisition, and installation tasks for service documented in PSP
buckets by processing a new kind of HOLDDATA associating PTFs to fix
categories. Each ++HOLD statement identifies an APAR and its resolving PTF
needed to provide support for the fix category. The FIXCAT HOLDDATA is now
being delivered with existing ERROR HOLDDATA. Fix categories have been
defined for hardware devices, new software FMIDs, and selected hardware and
software functions.
The minimum support required has been separated from the exploitation support,
so that you can identify what is minimally required. For releases z/OS V1.9-z/OS
V1.12 all PTFs listed in this PSP bucket have associated FIXCAT HOLDDATA
that identifies fixes in the following categories:
36
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
•
•
•
•
•
•
IBM.Device.Server.z114-2818
IBM.Device.Server.z114-2818.ParallelSysplexInfiniBandCoupling
IBM.Device.Server.z114-2818.ServerTimeProtocol
IBM.Device.Server.z114-2818.zHighPerformanceFICON
IBM.Device.Server.zBX-2458
IBM.Device.Server.zBX-2458.ISAOPT
Additional fix categories may be added in the future.
For the z BladeCenter Extension, you may use IBM.Device.Server.zBX-2458.
When SMP/E V3.5 processes FIXCAT ++HOLD statements (during RECEIVE
processing) the resolving PTF identified on the ++HOLD statement is assigned
an SMP/E SOURCEID matching the fix category on that statement. This enables
specifying fix categories as part of the SOURCEID operand on APPLY, ACCEPT,
and LIST commands. Many customers fall into one of two camps when it comes
to acquiring and installing service:
1. You choose to RECEIVE all available applicable PTFs and filter which PTFs
get installed using parameters on the APPLY command; or
2. You only acquire PTFs you need when you want to install them
No matter which approach you use, SMP/E V3.5 can simplify your task.
In the first scenario, you have all available PTFs applicable to your environment
already RECEIVED. To install all the PTFs needed for minimal support of a z114,
you could use something like the following command. You don't have to access
the PSP bucket, nor download any extra files.
APPLY CHECK GROUPEXTEND BYPASS(HOLDSYS)
SOURCEID(IBM.Device.Server.z114-2818).
If you wanted to include all support for the z114 optional functions, then the
SOURCEID operand could either list all fix categories that you are interested in,
or use wildcarding to have SMP/E determine all applicable fix categories. This
latter approach would automatically express interest in future z114 functions
(should new fix categories be created).
Specifying IBM.Device.Server.z114-2818* or just *2818* all result in similar
results: an interest in the minimal support for z114 as well as exploitation of all
optional functions. In these examples the asterisk ('*') represents 0-n characters,
while the percent sign ('%') represents a single character. Based on the
structured names of the fix categories for hardware support, you can use
SOURCEIDs with wildcarding to ensure that PTFs for multiple generations of
servers are installed.
In the second scenario, you don't know if you have RECEIVEd all the PTFs
needed since you only obtain PTFs right before you want to install them. You
need to first obtain the latest HOLDDATA using your favorite method (mine is
RECEIVE ORDER(CONTENT(HOLDDATA))...). Then you can use the new
REPORT MISSINGFIX command to identify PTFs missing from your system. For
example:
SET BDY(GLOBAL).
Chapter 2. Software Requirements
37
Copyright 2011 IBM Corporation. All rights reserved.
REPORT MISSINGFIX ZONES(ZOSR8T)
FIXCAT(IBM.Device.Server.z114-2818).
The REPORT MISSINGFIX command checks your GLOBAL zone for FIXCAT
HOLDDATA matching the FIXCAT values specified on the command. The
command then compares the APARs identified in that FIXCAT HOLDDATA with
the PTFs installed in the specified zones, and produces a report to identify any
APARs not resolved. In other words, it reports which PTFs (fixes) are missing for
the specified fix categories. Furthermore, the command produces a customized
job used to obtain any PTFs not already RECEIVEd via the RECEIVE ORDER
command, and install any missing service via the APPLY CHECK command.
Please note the FIXCAT operand on the REPORT MISSINGFIX command can list
multiple fix categories, as well as using the same wildcarding techniques
described above for the SOURCEID operand. Because both of these techniques
are simple and integrated into basic SMP/E commands, you can use them
periodically to ensure you have the latest PTFs specified in the hardware PSP
bucket installed (since PSP buckets can be updated daily). SMP/E V3.5 also
provides an Explorer function which helps in identifying new fix categories which
may be of interest.
2.1.3.8 Sysplex
z/OS on a z990, z890, z900 or z800 cannot participate in a sysplex with a z114
server. If you have any z/OS images or coupling facilities on a z990, z890, z900
or z800, and you intend to introduce a z114 server into that sysplex, you must
migrate those images to z9 (or higher) prior to introducing the z114 server.
When you change coupling facility control code (CFCC) levels, your coupling
facility structure sizes might change. z114 servers initially ship with CFCC Level
17. If, as part of your migration to a z114 server, you change CFCC levels (either
by placing a coupling facility on the z114 server or by moving the coupling facility
to a z10 or z9 at a higher CFCC level), you may require larger structure sizes
than previously. If your CFCC levels are identical, structure sizes are not
expected to change when you migrate from a previous server to a z114 server.
Use the CFSIZER tool (http://www.ibm.com/systems/support/z/cfsizer/) to
determine appropriate structure sizes.
2.1.3.9 Parallel Sysplex Enhancements
As data sharing workloads continue to grow, the Parallel Sysplex infrastructure
needs to anticipate the increased requirements for coupling resources. To do this,
we have added connectivity capabilities to support larger data sharing
environments.
2.1.3.10 Connectivity improvements with up to 72 coupling links:
The IBM zEnterprise 114 increases the number of external coupling links allowed
from 64 to 72. This allows the full configuration of 24 1x IFB links and 48 ISC-3 links
to be used. In addition, one can also configure up to 32 (internal) IC links for coupling
between images defined on the same server. Having more coupling links is important
to provide sufficient coupling connectivity for larger single Parallel Sysplexes, as well
as for configurations where the same server hosts multiple Parallel Sysplexes and
Coupling Facility images.
38
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
2.1.3.11 Connectivity improvements with 128 CHPIDs per server:
To support larger Parallel Sysplexes with ever-increasing amounts of data sharing
traffic to the Coupling Facility, the throughput and capacity of more coupling CHPIDs
are also required. With the z114, IBM has increased the number of coupling CHPIDs
per server from 64 to 128. Since IFB links allow for multiple (logical) CHPIDs over the
same (physical) link, this can also allow for larger Parallel Sysplexes without
requiring more coupling link hardware.
2.1.4 Coupling Facility Control Code Level 17
2.1.4.1 Coupling Facility Control Code improvements for CFCC
CFCC Level 17 increases the number of structures that can be allocated in a
CFCC image from 1023 to 2047. Allowing for more CF structures to be defined
and used in a sysplex, permits more discrete data sharing groups to operate
concurrently and can help environments which require many structures to be
defined, z114, with CFCC level 17, also provides improved serviceability of
Coupling Facilities with enhanced data collection and triggering of non-disruptive
CF dumps.
Note: In order to provide these functional and serviceability enhancements, the
Coupling Facility Control Code will require more storage allocation for internal
control blocks and dump space. Clients should ensure they allocate additional
storage capacity when setting up the image profiles for the Coupling Facility
image. The CFCC code Release 17 will use about 400M to 450M of total storage
for each image. This usage is a significant increase over storage usage in
previous CF levels.
2.1.5 zVM 6.2 (available December 02, 2011)
This release implements multisystem virtualization using a z/VM single system
image cluster composed of up to four z/VM systems. This multisystem
virtualization technology for the mainframe will extend the z/VM virtualization
technology to a new level allowing members of the cluster to share resources and
synchronize between nodes, appearing to be a single system.
The zEnterprise server must be at driver level 93 or greater for managing the
z/VM 6.2 hypervisor from the Unified Resource Manager.
Introducing Live Guest Relocation
Live Guest Relocation (LGR) provides the capability for a running Linux virtual
machine to be moved without disruption from one z/VM system to another within
a Single System Image.
Live guest relocation provides continuity for virtual server workloads over planned
z/VM and machine outages, such as service and hardware upgrades. LGR allows
applications to remain available over such outages with less impact to the
application and less setup required. Verification that needed resources and
machine features are available on the destination system prior to the relocation is
provided. This verification may also be performed on request to assess a guest's
eligibility for relocation. In an SSI cluster comprising different machine models,
the architecture level presented to each guest is tailored to the set of machine
features common to the member systems within the guest's specified relocation
domain.
Chapter 2. Software Requirements
39
Copyright 2011 IBM Corporation. All rights reserved.
With the introduction of Live Guest Relocation among members of the SSI
cluster, it is increasingly important to identify the level of Linux on System z
running within each guest. Unsupported levels of Linux may not operate correctly
following relocation. Additional information is at the following website:
http://www.vm.ibm.com/zvm620.
Further details on z/VM requirements can be found in:
http://www.vm.ibm.com/service/vmrequrm.html.
The Unified Resource Manager has been enhanced with firmware driver level 93
to support life cycle management of individual members within a z/VM V6.2 SSI
environment. Driver 93 is required for managing z/VM 6.2. However, the Unified
Resource Manager does not support relocation of managed guests.
40
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
2.2 Operating System Support
• The IBM zEnterprise 114 requires :
z/OS V1.13 with PTFs.
z/OS V1.12 with PTFs.
z/OS V1.11 with PTFs.
z/OS v1.10 + PTFs AND the z/OS 1.10 Lifecycle Extended Service
(5656-A01). The Lifecycle Extension must be in place before a customer may
obtain required PTFs for the z114 and z196. There are no exceptions.
z/OS v1.9 + PTFs AND the z/OS 1.9 Lifecycle Extended Service (5646-A01).
The Lifecycle Extension must be in place before a customer may obtain
required PTFs for the z114 and z196. There are no exceptions.
z/OS v1.8 Lifecycle Extended Service (5646-A01). has expired and is no longer
available. Contact GTS for qualifications for a contract. Contract must be in place
to obtain required PTFs for the z114 or z196. There are no exceptions.
• z/VM V6.1 with PTFs.
z/VM V5.4 with PTFs.
z/VSE V4.3 with PTFs.
z/VSE V4.2 with PTFs.
z/TPF V1.1
Linux on System z distributions:
Novell SUSE SLES 10 and SLES 11.
Red Hat RHEL 5 and RHEL6.
Note: See
http://www.ibm.com/systems/z/os/linux/resources/testedplatforms.html to see
earlier releases of Linux on System z that have been tested and approved.
Older releases may not be able to exploit all features and functions available
on the z114.
Chapter 2. Software Requirements
41
Copyright 2011 IBM Corporation. All rights reserved.
2.3 Minimum Function/Feature Requirements
Refer to the z/OS, z/VM, z/VSE subsets of the 2818DEVICE Preventive Service
Planning (PSP) bucket prior to installing a z114.
2.3.1 IBM zEnterprise Unified Resource Manager
Requires at a minimum:
• z/OS V1.13 with PTFs.
z/OS V1.12 with PTFs.
z/OS V1.11 with PTFs.
z/OS V1.10 with PTFs.
Older versions of z/OS will tolerate, but do not exploit, IBM zEnterprise Unified
Resource Manager.
z/VM 6.1 with PTFs for enablement of virtual server lifecycle management and
support for managing real and virtual networking resources by the Unified
Resource Manager.
2.3.2 CP Assist for Cryptographic Function (CPACF) (#3863) enhancements
Require at a minimum:
z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support for z/OS
V1R10-V1R12 Web deliverable This may be obtained at:
http://www.ibm.com/systems/z/os/zos/downloads/
z/VM V5.4 with PTFs for guest exploitation.
z/VSE V4.2 and later supports the CPACF features with the functionality
supported on IBM System z10.
z/TPF V1.1.
Linux on System z distributions:
Novell SUSE SLES 11 SP1.
Red Hat RHEL 6.1.
For Message-Security-Assist-Extension 4 exploitation, IBM is working with its
Linux distribution partners to include support in future Linux on System z
distribution releases.
2.3.3 Crypto Express3
Requires at a minimum:
z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support for z/OS
V1R10-V1R12 Web deliverable This may be obtained at:
http://www.ibm.com/systems/z/os/zos/downloads/
z/VM V5.4 with PTFs for guest exploitation. NOTE: z/VM V5.4 and later support
clear-and secure-key operations.
z/VSE V4.2 and IBM TCP/IP for VSE/ESA (TM) V1.5.0 with PTFs. NOTE: z/VSE
supports clear-key RSA operations only.
z/TPF V1.1 (acceleration mode only).
Linux on System z distributions:
For toleration:
Novell SUSE SLES10 SP3 and SLES 11.
42
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Red Hat RHEL 5.4 and RHEL 6.0.
For exploitation:
Novell SUSE SLES11 SP1.
Red Hat RHEL 6.1.
2.3.4 Crypto Express3 (when defined as a coprocessor) supporting ANSI X9.8
PIN security, Enhanced CCA key wrapping, Secure Keyed-Hash Message
Authentication Code (HMAC), and initial Elliptic Curve Cryptography (ECC)
functions
Requires one of the following
• z/OS V1.11, z/OS V1.12, or z/OS V1.13 with the Cryptographic Support for
z/OS V1R11-V1R13 Web deliverable (available September 9, 2011).
• z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support for
z/OS V1R10-V1R12 Web deliverable with PTFs. The Cryptographic Web
deliverables are available at:
• http://www.ibm.com/systems/z/os/zos/downloads/
• z/OS V1.13 with PTFs.
2.3.5 Crypto Express3 (when defined as a coprocessor) supporting PKA RSA OAEP
with SHA-256 algorithm
Requires at one of the following at a minimum:
• z/OS V1.10 (1), z/OS V1.11, or z/OS V1.12 with the Cryptographic Support for
z/OS V1R10-V1R12 Web deliverable with a PTF (available September 9,
2011).
• z/OS V1.11, z/OS V1.12, or z/OS V1.13 with the Cryptographic Support for
z/OS V1R11-V1R13 Web deliverable (available September 9, 2011).
• z/OS V1.13 with a PTF (available September 9, 2011).
• z/VM 5.4 with PTFs for guest exploitation
2.3.6 Crypto Express3 (when defined as a coprocessor) with Expanded support for
AES algorithm, Enhanced ANSITR-31 Secure Key Exchange, PIN block
decimalization table protection, and Additional Elliptic Curve Cryptography (ECC)
functions
Requires at a minimum:
• z/OS V1.11, z/OS V1.12, or z/OS V1.13 with the Cryptographic Support for
z/OS V1R11-V1R13 Web deliverable (available September 9, 2011). The
Cryptographic Web deliverables are available at:
• http://www.ibm.com/systems/z/os/zos/downloads/
• z/VM V5.4 with PTFs for guest exploitation.
• Linux on System z distributions:
• Support is planned for a future release of Common Cryptographic Architecture
Support Program for Linux on System z.
.
Chapter 2. Software Requirements
43
Copyright 2011 IBM Corporation. All rights reserved.
2.3.7 Crypto Express3 (when defined as an accelerator) supporting Modulus Exponent
ME) and Chinese Remainder Theorem (CRT)
Requires at a minimum :
• z/OS V1.11, z/OS V1.12, or z/OS V1.13 with the Cryptographic Support for
z/OS V1R11 - V1R13 Web deliverable (available September 9, 2011). The
Cryptographic Web deliverables may be obtained at:
• http://www.ibm.com/systems/z/os/zos/downloads/
• z/VM V5.4 with PTFs for guest exploitation.
• Linux on System z distributions:
• For RSA encryption and decryption with key lengths up to 2048-bits:
• Novell SUSE SLES10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.
• For RSA encryption and decryption with key lengths up to 4096-bits:
• IBM is working with its Linux distribution partners to include support in future
Linux on System z distribution releases.
2.3.8 zHPF Enhancements
High Performance FICON for System z (zHPF) enhancement for QSAM, BPAM,
and BSAM access methods as well as format writes with all supported FICON
features (CHPID type FC) on zEnterprise servers requires at a minimum:
• z/OS V1.13 with PTFs.
• z/OS V1.12 and V1.11 with PTFs.
2.3.9 zHPF enhancement for DB2 list prefetch
zHPF enhancement for DB2 list prefetch with FICON Express8S features (CHPID
type FC) on zEnterprise servers requires at a minimum:
• z/OS V1.13.
• z/OS V1.12 and V1.11 with PTFs.
2.3.10 FICON Express8S (CHPID type FC) when utilizing native FICON or
Channel-To-Channel (CTC)
Requires at a minimum :
• z/OS V1.8.
• z/VM V5.4.
• z/VSE V4.2.
• z/TPF V1.1.
• Linux on System z distributions:
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.
44
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
2.3.11 FICON Express8S (CHPID type FC) for support of zHPF single-track
operations
Requires at a minimum:
• z/OS V1.11.
• z/OS V1.8, V1.9, or V1.10 with PTFs.
• Linux on System z distributions:
• Novell SUSE SLES 11 SP1.
• Red Hat RHEL 6.
2.3.12 FICON Express8S (CHPID type FC) for support of zHPF multitrack operations
Requires at a minimum:
• z/OS V1.11 with PTFs.
• z/OS V1.9 or V1.10 with PTFs.
• Red Hat RHEL 6.1
• Linux on System z distributions:
• IBM is working with its Linux distribution partners to include support in
future Linux on System z distribution releases.
2.3.13 FICON Express8S (CHPID type FCP) for support of SCSI devices
Requires at a minimum :
• z/VM V5.4.
• z/VSE V4.2.
• Linux on System z distributions:
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.
2.3.14 T10-DIF support by the FICON Express8S and FICON Express8 features when
defined as CHPID type FCP
Requires at a minimum :
• z/VM 5.4 with PTFs for guest exploitation
• Linux on System z distributions:
• IBM is working with its Linux distribution partners to include support in
future Linux on System z distribution releases.
2.3.15 z/OS discovery and autoconfiguration (zDAC) for FICON Express8 and FICON
Express4 channels (CHPID type FC)
Requires at a minimum:
• z/OS V1.12 with PTFs.
Chapter 2. Software Requirements
45
Copyright 2011 IBM Corporation. All rights reserved.
2.3.16 Up to 32 HiperSockets (CHPID type IQD)
Requires at a minimum:
• z/OS V1.12 with PTFs.
• z/OS V1.11 with PTFs.
• z/OS V1.10 with PTFs.
• z/VM V5.4 with PTFs.
• z/VSE V4.1.
• Linux on System z distributions:
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.
2.3.17 HiperSockets network traffic analyzer (HS NTA) on IBM zEnterprise 114 and
System z10
Requires at a minimum:
• z/VM V5.4 with PTFs for guest exploitation.
• Linux on System z distributions:
• Novell SUSE SLES 11 SP1.
• Red Hat RHEL 6.0
2.3.18 OSA Considerations
OSA-Express4S GbE contains two ports per PCIe adapter.
OSA-Express4S 10 GbE contains one port per feature.
OSA-Express3 GbE and 1000BASE-T contain two ports per PCIe adapter. The
ports "share" one channel path identifier (CHPID). There may be two or four ports
per feature, depending upon feature number.
OSA-Express3 10 GbE SR and LR contain one port per PCIe adapter. There are
two ports per feature.
There is no OSA-Express4S 1000 Base-T feature. If a 1000 Base-T feature is
required, OSA-Express3 1000 Base-T should be ordered.
46
SA11-002-02
CHPID Type
Features
Purpose
OSC
1000Base-T
OSA-Integrated Console Controller (OSA-ICC)
Supports TN3270E, non-SNA DFT to IPL CPCs
& LPs.
OSD
All
Queue Direct Input/Output (QDIO) architecture;
TCP/IP traffic when Layer 3 (uses IP address)
and Protocol-independent when Layer 2 (uses
MAC address).
Copyright 2011 IBM Corporation. All rights reserved.
CHPID Type
Features
Purpose
OSE
1000Base-T
Non-QDIO; For SNA/APPN/HPR traffic and
TCP/IP 1 passthru traffic.
OSM
1000Base-T
OSA-Express for Unified Resource Manager.
Connectivity to intranode management network
(INMN) from z114 to Unified Resource
Manager functions.
OSN
GbE and 1000Base-T
OSA-Express for NCP; Appears to OS as a
device supporting channel data link control
(CDLC) protocol. Enables Network Control
Program (NCP) channel-related functions such
as loading and dumping to NCP. Provides
LP-to-LP connectivity OS to IBM
Communication Controller for Linux (CCL).
Note: OSN is not supported on the
OSA-Express4S GbE or OSA-Express4S 10
GbE features.
OSX
10 GbE
OSA-Express for zBX. Provides connectivity
and access control to the intraensemble data
network (IEDN) from z114 to Unified Resource
Manager functions.
2.3.19 OSA-Express4S GbE LX (#0404) and GbE SX (#0405)
Require at minimum :
CHPID type OSD with exploitation of two ports per CHPID:
• z/OS V1.10.
• z/OS V1.9 with PTFs.
• z/OS V1.8 with PTFs.
• z/VM V6.1.
• z/VM V5.4 with PTFs.
• z/VSE V4.2.
• z/TPF V1.1 PUT 4 with PTFs.
• Linux on System z distributions:
• Novell SUSE SLES 10 SP2 and SLES 11.
• Red Hat RHEL 5.2 and RHEL 6.0.
CHPID types OSD without maximum port exploitation (one port on the PCIe
adapter is available for use):
• z/OS V1.8.
• z/VM V5.4.
• z/VSE V4.2.
• z/TPF V1.1.
• Linux on System z distributions:
Chapter 2. Software Requirements
47
Copyright 2011 IBM Corporation. All rights reserved.
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.0.
2.3.20 OSA-Express4S 10 GbE LR (#0406) and 10 GbE SR (#0407)
Require at a minimum :
CHPID type OSD:
• z/OS V1.8.
• z/VM V5.4.
• z/VSE V4.2.
• z/TPF V1.1.
• Linux on System z distributions:
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.0.
CHPID type OSX for access control to the intraensemble data network (IEDN)
from z114 to Unified Resource Manager functions:
• z/OS V1.12 with PTFs.
• z/OS V1.11 with PTFs.
• z/OS V1.10 with PTFs.
• z/VM V6.1 with PTFs.
• z/VM V5.4 with PTFs to define, modify, and delete OSX CHPID types when
z/VM is the controlling LPAR for dynamic I/O.
• zVSE 5.1 (when available)
• z/TPF V1.1 PUT 4 with PTFs.
• Linux on System z:
• Novell SUSE SLES 10 SP4 and SLES 11 SP1 (maintenance update)
• Red Hat RHEL 5.6 and RHEL 6.0.
2.3.21 OSA-Express4S Large Send for IPv6 packets (CHPID types OSD and OSX)
Requires at a minimum :
• z/OS V1.13 .
• z/VM V5.4 for guest exploitation.
2.3.22 Checksum offload for LPAR-to-LPAR traffic for the OSA-Express4S features
when defined as CHPID type OSD
Requires at a minimum :
• z/OS V1.13 .
• z/VM V5.4 for guest exploitation
48
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
2.3.23 Inbound workload queuing for Enterprise Extender for the OSA-Express4S
and OSA-Express3 features when defined as CHPID types OSD or OSX
Require at a minimum :
• z/OS V1.13.
• z/VM V5.4 for guest exploitation.
2.3.24 OSA-Express3 1000BASE-T (#3367 and #3369)
Requires at minimum:
2.3.24.1 CHPID type OSC supporting TN3270E and non-SNA DFT:
• z/OS V1.8.
• z/VM V5.4.
• z/VSE V4.2.
2.3.24.2 CHPID type OSD with exploitation of all four ports:
• z/OS V1.10 .
• z/OS V1.9 with PTFs .
• z/OS V1.8 with PTFs.
• z/VM V5.4 with PTFs.
• z/VSE V4.2 with PTFs.
• z/TPF V1.1 PUT 4 with APARs.
• Linux on System z distributions - for four ports per feature (#3367):
• Novell SUSE SLES 10 SP2 and SLES 11.
• Red Hat RHEL 5.2 and RHEL 6.0.
• Linux on System z distributions - for two ports per feature (#3369):
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.0.
2.3.24.3 CHPID type OSD without maximum port exploitation (one port
per PCIe adapter is available for use; two ports per feature):
• z/OS V1.8
• z/TPF V1.1.
• Linux on System z distributions:
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.0.
2.3.24.4 CHPID type OSE supporting 4 or 2 ports per feature:
• z/OS V1.8.
• z/VM V5.4.
• z/VSE V4.2.
2.3.24.5 CHPID type OSM for intranode management network:
• z/OS V1.12 with PTFs.
Chapter 2. Software Requirements
49
Copyright 2011 IBM Corporation. All rights reserved.
• z/OS V1.11 with PTFs.
• z/OS V1.10 with PTFs.
• z/VM V6.1 with PTFs.
• z/VM V5.4 with PTFs to define, modify, and delete OSM CHPID types when
z/VM is the controlling LPAR for dynamic I/O.
• IBM is working with its Linux distribution partners to include support in future
Linux on System z distribution releases.
2.3.24.6 CHPID type OSN supporting OSA-Express for NCP:
Note: CHPID type OSN does not use ports. All communication is LPAR-to-LPAR.
• z/OS V1.8.
• z/VM V5.4.
• z/VSE V4.2.
• z/TPF V1.1.
• Linux on System z distributions:
• Novell SUSE SLES 10 and SLES 11.
• Red Hat RHEL 5 and RHEL 6.0.
2.3.25 Display OSAINFO
Display OSAINFO for OSA-Express3 CHPID types OSD, OSM (exclusive to IBM
zEnterprise 114), and OSX (exclusive to IBM zEnterprise 114) on z114 and z10
requires at a minimum:
• z/OS V1.12 with PTFs.
2.3.26 Inbound workload queuing (IWQ) for OSA-Express3 CHPID types OSD and
OSX (exclusive to IBM zEnterprise 114) on IBM zEnterprise 114 and z10
Requires at a minimum:
• z/OS V1.12 with PTFs.
• z/VM V5.4 with PTFs for guest exploitation.
2.3.27 12x InfiniBand and 1x InfiniBand coupling links
Require at a minimum
• z/OS V1.10 with PTFs
• z/OS V1.9 with PTFs.
• z/OS V1.8 with PTFs.
• z/VM V5.4 to define, modify, and delete an InfiniBand coupling link, CHPID
type CIB, when z/VM is the controlling LPAR for dynamic I/O.
50
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
2.3.28 Coupling Facility Control Code Level 17
Exploiting the new functions of Coupling Facility Control Code Level 17, including
support for up to 2047 Coupling Facility structures
Requires at a minimum:
• z/OS V1.12 with PTFs
• z/OS V1.11 with PTFs
• z/OS V1.10 with PTFs.
• z/VM V5.4 for guest virtual coupling.
2.3.29 Independent Software Vendors (ISV)
• There is a document that contains many ISVs and applications on an internal
w3 page. However, this listing is generated through a variety of internal and
external sources. It is provided as a reference only and is not external. Check
directly with an ISV to verify their support of the System z platform.
http://w3.ibm.com/ibm/resource/isv.html
• Help in Enabling ISVs onto the System z Platform
If your customer has a request for an ISV application that is not enabled on
the platform, please use the Client Project Management (CPM) process
(formerly known as the 5IAB Account Planning DB) to enter your ISV request.
http://w3.tap.ibm.com/w3ki2/display/stgsales/z+ISVs
From your customer account record, enter the ISV product information which
is found under the tab "ISV Products Required". Be sure to fill in all the fields
as this will provide the enablement team with the information they need to
contact the ISV. The Status of the enablement activity can be found in the field
"Next Steps" which is also in the tab "ISV Products Required". The database is
checked on a daily basis for new ISV application request.
Additional Information
More information on how to conduct a planning session with your team and
customers, please review the process found at:
http://w3.tap.ibm.com/w3ki2/display/stgsales/5IAB+Planning/
Contacts:
Andrew Schmidt, Linux on System z Program Manager
Andrew Schmidt/Poughkeepsie/IBM
Sue Tuczynski, z/OS ISV Program Manager, CPM/5IAB Management Susan
Tuczynski/Poughkeepsie/IBM
Chapter 2. Software Requirements
51
Copyright 2011 IBM Corporation. All rights reserved.
2.4 Additional Information
Refer to technical document TD105581 for additional information located at
www.ibm.com/support/techdocs.
52
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 3. Physical Site Planning
The information in this section is provided as a convenience only. Detailed
Physical Site planning and requirements should be based on a review of the
following publication:
zEnterprise 114 Installation Manual - Physical Planning GC28-6907
This manual can be obtained from ResourceLink at:
• www.ibm.com/servers/resourcelink
3.1 General
z114 Front (left) and Rear (right) view
Chapter 3. Physical Site Planning
53
Copyright 2011 IBM Corporation. All rights reserved.
3.2 Physical Specifications
Physical Dimensions
z10 BC
# of Frames
Height (with covers)
Width (with covers)
Depth (with covers)
Height Reduction
Width Reduction
z114 Models M05 and M10
1 Frame
1 Frame
201.5 cm / 79.3 in (42 EIA)
77.0 cm / 30.3 in
180.6 cm / 71.1 in
201.3 cm/ 79.3 in (42 EIA)
78.4 cm/ 30.9 in
157.5 cm/ 62.0 in
180.9 cm / 71.2 in (EIA)
None
180.9 cm/ 71.2 in (EIA)
None
Machine Area
1.42 Sq. Meters / 15.22 Sq. Feet
Service Clearance
3.50 Sq. Meters / 37.62 Sq. Feet
(all numbers without (IBF Contained within the Frame)
overhead cabling option)
1.24 Sq. Meters / 13.3 Sq. Feet
3.22 Sq. Meters / 34.7 Sq. Feet
(IBF Contained within the Frame)
z114 Weight
z114 Single Frame
Model M05
54
Model M10
Without IBF
With IBF
With IFB and
Overhead cabling
Without IFB
With IBF
With IFB and
Overhead cabling
872.71 Kg
967.97 Kg
1011.06 Kg
887.68 Kg
982.93 Kg
1026.03 Kg
1924 lbs
2134 lbs
2229 lbs
1957 lbs
2167 lbs
2262 lbs
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
3.3 Operating environment:
3.3.1 Temperature (powered on):
High Ambient Temperature
Long-term recommended 27°C (80.6°F) 4
Maximum ambient allowed 35°C (95°F) 4
Low Ambient Temperature
Long-term recommended 18° (64.4°F)
Minimum ambient allowed 10° (50°F)
Low end humidity
Long-term recommended 5.5°C (41.9°F) dew point
Minimum relative humidity allowed 20%
High end humidity
Long-term recommended 60% relative humidity and 15°C (59°F) dew point
Maximum relative humidity allowed 80% relative humidity and 21°C (69.8°F) dew point
3.3.2 Electrical Power:
z114 Power in Kilowatts
Model M05
Model 10
1
2
3
1
2
3
Zero I/O drawers
1.53
1.86
1.87
2.15
2.77
2.74
1 FC 4000
2.35
2.77
2.92
3.05
3.69
3.80
1 FC 4003
3.05
3.48
3.53
3.73
4.40
4.41
2 FC 4000
3.25
3.69
3.97
3.92
4.62
4.87
1 FC 4000 + 1 FC 4003
3.92
4.42
4.61
4.62
5.34
5.49
3 FC 4000 (RPQ approval)
4.13
4.62
5.06
4.82
5.55
5.95
2 FC 4003
4.54
5.04
5.12
5.24
5.97
6.02
2 FC 4000 + 1 FC 4003
4.79
5.30
5.63
5.48
6.23
6.53
4 FC 4000 (RPQ approval)
4.98
5.51
5.84
-
-
-
-
-
-
6.80
7.58
7.78
1 FC 4000 + 2 FC 4003
FC 4000 = I/O Drawer
FC 4003 = PCIe I/O Drawer
Chapter 3. Physical Site Planning
55
Copyright 2011 IBM Corporation. All rights reserved.
3.3.3 Customer Circuit Breaker Requirements
Input Voltage Range (V)
System Rated Current (A)
Circuit Breaker
200 - 240V
24A
30 amps
380 - 415V
16A
16 amps
480V
14A
20 amps
380 - 520 VDC
24A
30 A DC / 32 A DC WT
3.3.4 Capacity of Exhaust:
• Max - 3806 cubic meters / hour (2240 CFM).
3.3.5 Noise Level:
• Declared A-Weighted Sound Power Level, LWAd(B) = 7.2
• Declared A-Weighted Sound Pressure Level, LpAm(dB) = 54
3.3.6 Leakage and Starting Current:
350 mA / 170A (less than one millisecond)
56
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
3.4 Physical Planning
3.4.1 General requirements
The z114 requires 3 customer power feeds:
1. Two identical three-phase feeds to the A frame - one to the front, one to the
rear, OR two identical single phase feeds to the A frame - one to the front, one to
the rear.
2. One single-phase feed for customer-supplied service outlets for the Hardware
Management Console and its modem. The service outlets require standard 100V
to 130V or 200V to 240V, 50/60Hz, single-phase power.
z114 operates with:
50/60Hz AC power
Voltages ranging from 200V to 480V
Three-phase or single phase wiring
3.4.2 Important Power Selection Considerations
As you select features for your z114 server, be aware of the following when
choosing server power:
If you choose single phase power, you will have unbalanced power.
If you choose three phase power, you may have either balanced or unbalanced
power, depending on server configuration. If you choose three phase power, you
can guarantee balanced power by selecting FC 3003, Balanced Power Plan
Ahead. This feature adds two more Bulk Power Regulators to each side of the
power supplies, assuring adequate and balanced power for all possible
configurations.
3.4.3 Power Estimation Tool
The Power estimator Tool for z114 allows you to enter your precise server
configuration to produce an estimate of power consumption.
Login to Resource Link with any userid. Navigate to Planning, then to Tools,
then to Power Estimation Tools. Specify the quantity for the features that are
installed in your machine. This tool estimates the power consumption for the
specified configuration. The tool does not verify that the specified configuration
can be physically built.
Note: The exact power consumption for your machine will vary. The object of the
tool is to produce an estimation of the power requirements to aid you in planning
for your machine installation. Actual power consumption after installation can be
confirmed using the Monitor task for current and historical power consumption.
3.4.4 Top exit power cords
The z114 has the option of top exit cabling. This includes the power cords. There
are several power cord options specifically made for top exit, and you must
choose one of these if you wish to have the power cords exit through the top of
Chapter 3. Physical Site Planning
57
Copyright 2011 IBM Corporation. All rights reserved.
the server. The top exit power cords are manufactured with additional hardware
that mounts the cord to the frame of the machine and provides an EMC seal at
the same time.
3.4.5 Top exit I/O cabling
The z114 has an optional feature for top exit I/O cabling. These frame towers for
I/O top exit will add approximately 43 kg (95 lbs) to the server weight, 152 mm (6
inches) to the width, and 117 mm (4.6 in) to the height.
All I/O cables can be routed through the top exit towers, including those
designated for the Fiber Quick Connect feature. For z114 servers installed on a
non-raised floor, this can be the ideal solution for I/O cabling.
The top exit towers are installed on the left side of the server (viewed from the
front) and are mounted to the side of the frame at the corners. A short left side
cover fits between the towers.
3.4.6 Non-raised Floor
If you elect to use top exit cabling on a non-raised floor, your server will be
configured for both top exit I/O and top exit power cord. If you elect to keep the
power cord on the floor, your I/O cabling must also exit onto the floor.
58
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
3.5 Ethernet network connection requirements
On the z114, the install team must connect the Ethernet adapters for any HMC(s)
into an Ethernet switch. This switch can then be connected to J01 and J02 on the
Bulk Power Hubs. (See the illustration below). This configuration is required since
the SEs have no external connection to the HMCs, and communicate only
through the Bulk Power Hubs.
The switch on the z114 is now FC0070 instead of FC0089 as in the past. FC0089
may be carried forward during an upgrade. This new switch is capable of
10/100/1000 mbps. Note that the z196 and z114 are the last machines to offer a
switch.
Initially, FC0070 is not available in some countries (Belize, Brazil, Egypt,
Haiti, Moldavia, Nicaragua and Oman. and Venezuela).
Notes:
1. Only Ethernet switches can connect to the customer ports J01 and J02 on the
Bulk Power Hubs.
2. Never connect an HMC directly to J01 and J02 on the Bulk Power Hubs.
3. Never connect customer LANs to any ports other than J01 and J02 on the Bulk
Power Hubs.
4. Customer LAN 1 should be plugged into J02 on the Bulk Power Hubs.
Customer LAN 2 should be plugged into J01 on the Bulk Power Hubs.
5. Port J06 on the Bulk Power Hubs is unused. Do not connect anything to this
port.
Chapter 3. Physical Site Planning
59
Copyright 2011 IBM Corporation. All rights reserved.
Refer to the IMPP for more detail.
Figure 1.
60
HMC LAN
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 4. Installation Checklists
Note 1: The following checklist items are intended to be brief and identify areas that
need to be addressed as part of the installation planning effort. Further details, if
required, will be contained in the Must Read Section of this SAPR document and
within the SAPR guide main sections.
Note 2: You can review these checklist sections in an order appropriate for your
meeting. For example, to expedite the use of an SSR’s time, it could be beneficial to
review the Physical Site section first.
4.1 Customer Expectations
Table 6. Customer Expectations
Activity
Status
Due Date
Owner
Comments
4.1.1 General
1
Customer’s planned implementation and
use of the z114 Processor is understood.
2
The machine configuration has been
reviewed to ensure that all features
required by the customer have been
correctly ordered. See Must Read.
3
For large installations or migrations, IBM
Account Team has considered the
benefits of involving the zSeries Project
Office.
4
Customer is aware of the IBM Code
Change Recommendations and the need
to stay current. See MustRead section for
more detail.
4.1.2 ResourceLink
5
Appropriate customer personnel have
obtained an IBM Registration ID (IBM ID)
in order to access ResourceLink
www.ibm.com/servers/resourcelink
4.1.3 Publications
6
Publications for the z114 processor have
been obtained from the IBM
ResourceLink web site.
www.ibm.com/servers/resourcelink
Chapter 4. Installation Checklists
61
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.1.4 Other Designated Product List (DPL) Equipment/Features
7
A separate review has been conducted
for any new devices, functions, or
features associated with the installation
of the z114 which are identified on the
DPL as requiring an SA Review.
See the MustRead for examples where
an assessment must be performed.
4.1.5 Performance
8
Appropriate sizing tools and
methodologies have been used to
determine the required processor model.
IBM internal URL for zPCR:
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/PRS689
IBM internal URL for zCP3000:
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/PRS1772
Partner World URL for zPCR:
http://partners.boulder.ibm.com/src/atsm
astr.nsf/WebIndex/PRS1796
Partner World URL for zCP3000:
http://partners.boulder.ibm.com/src/atsm
astr.nsf/WebIndex/PRS1865
9
The customer’s plan for measuring and
evaluating the performance of the
processor has been determined.
10 Encourage enabling CPU MF counters
on key production partitions as a
supplement to other metrics (SMF, RMF)
to understand why performance may
have changed.
SMF 113s can optionally
be used in System z
capacity planning to view
cache memory usage, by
application.
– See Must Read for CPU MF Techdocs:
TC000041
TC000066
SMF 113 data may prove
useful in support of an
installation of a z114 to
gain insight into
interactions of workloads.
Available on z114, z196 and z10 only.
11 Use the IBM® zEnterprise™
BladeCenter® Extension (zBX) SAPR
Guide (SA10-006) for sizing information
of the 2458-002.
62
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.1.6 Acquisition and Contractual Considerations
12 Contractual requirements associated
with the processor acquisition are in
place and agreed to by the customer and
IBM.
13 Customer is aware and has planned for
additional charges that may be incurred
in the future after the z114 has been
initially installed.
See the Must Read section for more
information.
14 Customer is aware of the changes to the
pricing metric used to license middleware
running on Linux for System z and
distributed platforms. See the Must Read
section for further information.
15 If the installation of the z114 is ordered via
a System z Exchange Program (formerly
known as a hybrid offering) or other push
pull which will result in a new serial
number machine replacing an installed
machine, insure that the maintenance
contract for the machine being replaced
has been canceled if required.
16 Has an installation date been agreed to
with the customer? Any shipment must
be installed within 30 days of shipment.
Note: IBM now charges for installs after 6
months from hardware shipment.
17 If planning to use the Crypto Express3 to
exploit the Elliptical Curve Cryptography
(ECC) capability, there is an LIC license
addendum that must be read and
understood by the customer.
4.1.7 Capacity on Demand
18 Customer and IBM Account Team/IBM
Business Partner are in agreement on
the contractual requirements associated
with any Capacity on Demand offering
involved with this machine.
Note! Even if the On/Off CoD and CIU
features are on order, the features won’t
function if the appropriate contracts have
not been signed and processed by IBM.
Chapter 4. Installation Checklists
63
Copyright 2011 IBM Corporation. All rights reserved.
Activity
19 Customer is aware that central
processors and specialty engines can be
added via an On/Off Capacity on
Demand order and understands there is
one 24 hour test allowed.
Also, administrative tests were reinstated
on the z114. See the MustRead for more
information.
4.1.8 Education and Training
20 Provisions have been made for customer
personnel to obtain training in the
definition, use, and function of the
processor and associated tools if
required.
4.1.9 Future Planning
21 IBM Account Team and Customer are
aware of the Statements of Direction
which may impact future planning. See
the MustRead.
22 FCP channels - for Storage Area
Networks (SANs):
Customer is aware of the worldwide port
name (WWPN) prediction tool that
provides advance SAN pre planning to
set up the environment prior to the z114
arrival.
23 Addition of a zBX at a later point in time is
a concurrent MES.See Must Read.
64
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
4.2 Hardware Configuration
Table 7. Hardware Configuration
Activity
Status
Due Date
Owner
Comments
4.2.1 General
1
Configuration and PCHID reports have
been provided to the customer and the
Configuration Control Number (CCN) is
verified.
2
If ISC links or InfiniBand links are to be
connected cross site via DWDM, verify
that the DWDM supports the rated link
speeds.
3
If using DWDMs to extend channels,
determine if the DWDMs support
auto-negotiation if the channels are set
up to use that capability.
4
If DWDMs will be used for coupling links,
determine if the DWDMs are rated to
support Server Time Protocol.
Do NOT use DWDMs to transmit STP
information if the DWDM has not been
qualified to support STP
5
Even if Crypto Express3 has not been
ordered, it is suggested to order (no
charge) FC3863 (CPACF).
Some ISV’s depend on CPACF.
4.2.2 Capacity on Demand
6
If the z114 is replacing a previous server
that had temporary capacity records
installed or staged, those records should
be deleted prior to replacing the server.
Refer to the documentation on
ResourceLink and the relevant contracts
for additional information.
7
If the IBM team does not use the VPD
Tool (IBM use only), everything in this
item can be ignored.
The status of temporary CBU features
are reflected in the machine and shown in
the VPD Tool.
However, the information in the tool won’t
be accurate unless the customer has
ordered FC9900 (On-line CoD Buying)
and the record is moved from “Staged” to
“Installed” (if applicable).
Chapter 4. Installation Checklists
65
Copyright 2011 IBM Corporation. All rights reserved.
Activity
8
To limit the exposure to unexpected CoD
charges, the customer can order pre-paid
On/Off Capacity on Demand Tokens and
bank them.
Status
Due Date
Owner
Comments
Same as z10 BC
This may be an attractive alternative to
paying for temporary capacity after it’s
use.
See the MustRead for more details.
9
Appropriate feature codes and hardware
are included on the z114 to support the
Capacity on Demand functions.
Ensure that the configurator order reflects
what the customer expects to be able to
do. CoD feature codes are listed in an
appendix C of the SAPR Guide.
10 On the z114, the customer has the option
to have active OOCoD records
automatically renew expiration dates.
See the MustRead.
4.2.3 Service
11 Have the appropriate installation Tool Kit
features been ordered (or not ordered)?
FC3759 Universal Lift Tool/Ladder:
Chargeable Feature Code.
Universal Lift Tool/Ladders, FC3759, is
common with all 24” rack products, z114,
z196, z10 and some System P products.
The equipment associated with FC3759
are quite large. The local SSR will be able
to determine if more than one feature is
desirable in a data center.
FC9969 Site Tool Kit:
Nonchargeable Feature Code.
The Site Tool Kit, FC9969, contains tools
specific to the z114 and the z10 BC.See
Must Read.
Note:
There may be no requirement to have
more than one FC3759 or more than one
FC9969 per data center.
The configurator selects some tool kits by
default. The account team should use
good judgement when adding or
removing these features within the order.
See the MustRead for more detail
66
SA11-002-02
New with z196/z114
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.2.4 Hardware Management Console
12 The Hardware Management Console to
be used to control the z114 must be
FC0084 (carried forward during an
upgrade) or FC0090 (carried forward
during an upgrade) or FC0091 (new).
If other FC 0084 HMC's are installed at
the time of the upgrade to the z114 they
may be retained. See Must read.
STOP - Important:
See the MustRead for details.
13 If using an IBM® zEnterprise™
BladeCenter® Extension (zBX) or the
IBM Unified Resource Manager on a
single CPC, the Primary-HMC and
Alternate-HMC have very strict
requirements.
STOP - Important:
See the MustRead for details.
14 If there are plans to use the HMC
Customizable Data Replication (CDR)
Facility for the Traditional HMC’s, all
Traditional HMCs in the group must be at
the same HMC Version. (V2.n.n to
V2.n.n)
CDR Facility is not available for the
Unified Resource Manager HMC Pri/Alt
Pair.(FC0025)
4.2.5 Devices and Controllers
15 All equipment that will connect to the
z114 (both IBM and OEM) has been
verified to be supported and at the correct
maintenance level for attachment. See
Must Read for url for D93G Exception
Letter.
Chapter 4. Installation Checklists
67
Copyright 2011 IBM Corporation. All rights reserved.
Activity
16 The FICON Express8S and the FICON
Express8 support an 8 Gbps link data
rate with autonegotiation to 2, 4 or 8
Gbps.
NOTE: 1 Gb devices can be connected to
directors and switches with 8Gb links if
they use 4Gb optics in the 8Gb blade
and/or a 4Gb blade in the director or
switch.
So the scenario would be, FICON
Express8S or FICON Express8
connected to an 8Gb director blade and
then the connection to the 1Gb device is
accomplished via a 4Gb director blade.
If the FICON Express8S or FICON
Express8 channel is routed through a
switch, it is important to read the z114
Exception Letter. See Must Read for url
for D93G Exception Letter.
17 Is there an IBM 3590-A60 directly
attached (no FICON Director) to a FICON
Express4, FICON Express8, or FICON
Express8S? If so, See Must Read.
4.2.6 Consoles
18 Provisions have been made for IPL
consoles for each operating system
image (OSA-ICC, 2074, 3174).
Note 1: If migrating OSA-ICC to an
OSA-Express3 1000Base-T, planning
must include the fact that this 4-port
feature has two ports per CHPID type.
See the OSA-ICC manual and
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/PRS3591.
Note 2: Additional OSA-Express3
1000Base-T features will be required if
Unified Resource Management FC0025
has been ordered.
Note 3: The 2074 is an ESCON device.
ESCON channels can't be spanned to
talk to LPARs in different logical channel
subsystems. An ESCON channel can
only be shared by the LPARs in one
LCSS or dedicated to one LPAR.
68
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
19 The routing of “synchronous WTOR”
messages to consoles is under the
control of the SYNCHDEST parameter
for each z/OS system. An understanding
of how these messages are routed can
be very important to help ensure that the
messages will be visible to the
appropriate operations staff when they
are issued.
See FLASH 10771 http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/FLASH10761.
This Flash will explain the processing of
synchronous WTORs and the availability
implications associated with them.
4.2.7 Coupling Links
20 If PSIFB coupling links are to be used or
are being considered, a study has been
undertaken to analyze the performance
characteristics of PSIFB links and the
ability to support the intended workload
requirements.
21 If defining HCA3-O 12x or HCA2-O 12x
InfiniBand coupling links with HCD,
reduce the default number of
subchannels per CHPID from 32 to 7.
See the MustRead for more information.
22 If using HCA3-O 12x InfiniBand links
(FC0171), there is an opportunity to
improve service time by up to 40 percent
using IFB3. See the MustRead for details.
23 If ordering HCA2-O or HCA3-O
InfiniBand coupling links, ensure you
have ordered enough ports to provide
you with physical card redundancy.
24 If using HCA3-O, check the Driver
Exception letter to see if there are MCL
requirements on the other machines
being attached. See Must Read.
Chapter 4. Installation Checklists
69
Copyright 2011 IBM Corporation. All rights reserved.
Activity
4.2.8 Server Time Protocol
25 Any z114 which contains a coupling link
channel will require the installation of
Server Time Protocol (FC1021). e-Config
will add FC1021 automatically.
Note 1: The z114 cannot be connected to
a 9037 Sysplex Timer.
Note 2: If the z114 will be in a Sysplex
with other machines, they are required to
have STP installed, enabled and
configured.
See the MustRead.
26 If implementing STP for the first time, an
STP Technical Delivery and Assessment
must be conducted (refer to SA06-012)
and the “STP confirmation form” must be
submitted on ResourceLink.
27 Prior to an upgrade to a server (z10 to
z114) that has an STP Role, reassign the
STP role to another server in the CTN or
eliminate the role if necessary to “Not
Configured” (Arbiter or BTS). After the
upgrade, manually reassign the role to
the upgraded or other appropriate server.
The MustRead contains a URL that
explains this in detail.
70
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
28 For any disruptive action (MES, driver
upgrade, power-off, power-on-reset,
CPC Deactivate, etc) determine if this
server is in an STP-only CTN or a Mixed
CTN.
A) STP-only CTN
If the server is in an STP-only CTN, and
has ANY of the following server roles:
- Preferred Time Server (PTS)
- Backup Time Server (BTS)
- Arbiter
the STP role of this server MUST either
be assigned as "Not Configured" or
reassigned to another server in the CTN,
before taking the disruptive action. After
the disruptive action is completed, the
roles should be reassigned for normal
operations. See MustRead section for
more details.
B) Mixed CTN
If the server is in a Mixed CTN, determine
the Stratum level of this server. If the
server is a Stratum 1 server, verify that all
attached Stratum 2 servers have an
alternate Stratum 1 server available as a
clock source and are not solely
dependent on this server as a clock
source. If the server is a Stratum 2 server,
verify that all attached Stratum 3 servers
have an alternate Stratum 2 server
available as a clock source and are not
solely dependent on this server.
29 If this is a single CPC or there are only
two CPCs in the STP-Only CTN, see
TD105103:
http://www-03.ibm.com/support/techdocs
/atsmastr.nsf/WebIndex/TD105103
30 Prior to a server upgrade that changes
the machine type (for example, z10 BC to
z114) and if you have implemented the
enhancement that allows you to restore
STP configuration information across
Power on Resets in a two server CTN,
(refer to Techdoc TD105103), special
action is required.
See the MustRead for details.
Chapter 4. Installation Checklists
71
Copyright 2011 IBM Corporation. All rights reserved.
Activity
31 FYI:
If you plan to run in a Mixed CTN, do NOT
plan to do a reverse migration from a
Mixed CTN to ETR mode or the z114 will
be taken out of the CTN.
4.2.9 Channel Configuration
32 If an upgrade, ensure that customer has
accounted for channel features not
supported on the z114. The configuration
should be reviewed for any deleted
channel types.
33 Customer is aware that the FICON
Express4, FICON Express8S and FICON
Express8 features do not support FICON
converter channels (FCV).
Note: The FICON Express and FICON
Express2 are not supported on the z114.
See the PRIZM FICON converter
products at http://www.opticatech.com/ if
required.
34 For ESCON converter channels attached
to a 3745, it is recommended to split the
EP traffic out onto a separate 3745 CAL6
channel adapter from the 3745 channel
adapter(s) that will run NCP traffic.
Business as usual - the same item
applied to z10 and z9.
72
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
35 If FC0025, Unified Resource Manager, is
to be used on a single z114 without a
zBX, and if LPAR to LPAR
communications is required in a Unified
Resource Manager defined VLAN, the
customer must provide
a) Two 10 GbE OSA features
b) an LC Duplex cable that goes from
OSX to OSX CHPIDs.
The cable plugs into the two
OSA-Express4S or OSA-Express3 10
GbE features, which are required (but not
forced) by eConfig.
IBM has stopped recommending using
two LC Duplex loop back testers, also
known as wrap plugs.
Note: The IODF must be shared among
participating z/OS LPARs.
See the MustRead for additional
information.
4.2.10 Crypto
36 Customer is aware that some functions
on the z800/z900 (CCF based crypto) are
no longer supported.
37 The Crypto Express3 must be assigned
to the LPAR in the LPAR Activation
Profile. The Online List defines which
crypto engines will be brought online
when the LPAR is activated. The
Candidate List defines which crypto
engines are eligible to be brought online
after the LPAR has been activated. The
Usage Domain defines where this LPAR
will find its master keys, and the Control
Domain defines which Domains can be
managed by a TKE attached to this
LPAR.
38 In order to gain the accelerator
performance boost for SSL operations,
the Crypto Express3 needs to be
configured as an accelerator via the
HMC.
39 If the customer plans to use a TKE
workstation, insure that it is the proper
feature and LIC level to support a z114.
Chapter 4. Installation Checklists
73
Copyright 2011 IBM Corporation. All rights reserved.
Activity
40 Customer understands the use of master
keys and has procedures in place for
managing keys and reloading master
keys in case of a problem with
cryptographic hardware.
Refer to the MustReads for additional
considerations.
41 If the customer plans to use secure keys
as protected keys on the CPACF, a
Crypto Express3 is required.
42 With Crypto Express3 code release CCA
4.1.0z, IBM has tightened up parameter
checking and validation to match what is
published in the manuals for the
Symmetric Key Generate(SYG) service
when using the PKA92 key-formatting
method.
See TechDoc Flash http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/FLASH10729
Also, see the MustRead section, as this
may affect your cryptographic operations.
74
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
4.3 Software Configuration
Table 8. Software Configuration
Activity
Status
Due Date
Owner
Comments
4.3.1 General
1
IBM PSP Buckets and ISV equivalent
publications have been obtained and
carefully reviewed on a regular basis.
Note: This should be done for the initial
install as well as for any future upgrades
to the machine either by feature
adds/removes, processor conversions, or
upgrades to a newer driver level.
SMP/E is a product customers use to
install PTF service and products. For a
description of the function, refer to the
following Techdoc:
http://www-03.ibm.com/support/techdocs
/atsmastr.nsf/WebIndex/TD105581
Investigate SMP/E 3.5 and the FIXCAT
category in HOLDDATA as a replacement
for the Enhanced PSP Tool.
You should use the FIXCAT named:
IBM.Device.Server.z114-2818.
Additionally you may include
IBM.Device.Server.z114-2818.* as this
will include exploiters of a z114 such as
STP and InfiniBand.
See SAPR Guide Software Chapter 2 for
more details.
2
Only supported levels of Operating
Systems along with the required
maintenance will be run on the z114.
See the Must Read and Software chapter
2 of the SAPR Guide.
3
Customer will review new mnemonics
introduced by HLASM for conflict with
new machine instructions. See Must
Read.
4
The ARCHITECTURE C/C++ compiler
option selects the minimum level of
machine architecture on which your
program will run. Customer is aware that
once programs exploit the ARCH(9) or
TUNE(9) option, those programs can
only run on z196 or z114 servers, or an
operation exception will occur.
z/OS 1.12 required for
exploitation.
Chapter 4. Installation Checklists
75
Copyright 2011 IBM Corporation. All rights reserved.
Activity
5
Status
Plans are in place to enable
Hiperdispatch.
Due Date
Owner
Comments
Same as for z196.
Hiperdispatch can be turned on or turned
off via the IEAOPTxx member of
SYS1.PARMLIB.
Note 1: LSPR measurement data is
based on Hiperdispatch being enabled.
See Must Read.
6
If the z114 will be used with an IBM®
zEnterprise™ BladeCenter® Extension
(zBX), use the 2458-002 SAPR Guide,
SA10-006.
4.3.2 Standalone Dump Considerations
7
Review stand-alone dump procedures to
ensure IBM best
practices/recommendations are being
followed. See Technical document
TD103286 for details. URL provided in
the Must Read.
4.3.3 IOCP and HCD
8
Customer is aware that for HCD/HCM
and IOCP, there will always be two
Logical Channel Subsystems defined,
each with 15 partitions and two
subchannel sets (per LCSS) defined for
the maximum.
All partitions will be initially designated
with an “*” as the name place holder until
changed.
76
SA11-002-02
Same as for z10 BC.
Copyright 2011 IBM Corporation. All rights reserved.
Activity
9
Status
Due Date
Owner
Comments
Two subchannel sets are available on the
z114.
The first subchannel set (SS 0) allows
definitions of any type of device (such as
bases, aliases, secondaries, and those
other than disk that do not implement the
concept of associated aliases or
secondaries).
The second subchannel set (SS1) can
now both be designated for use for disk
alias devices (of both primary and
secondary devices) and/or Metro Mirror
secondary devices only.
Second subchannel set applies to
ESCON (CHPID type CNC) and FICON
(CHPID type FC; both FICON and zHPF
paths)
Note: With Driver 93G, a device may be
IPLed when on an alternate subchannel
set. This requires z/OS V1.11 or higher,
with PTFs.
10 An evaluation has been made for
definitions which may have to be modified
when consolidating multiple system
images onto a single z114.
Of concern are CTCs and the associated
CUADDS as well as the partition
identifiers used within CFRM policies.
Consider migrating ESCON CTCs to
FICON CTCs.
11 A mis-definition of PSIFB links normally
shows up as a LOSS OF SIGNAL for
InfiniBand links for what is really a
DEFINITON ERROR.
Care should be taken in the creation of
the IOCDS but if missed, customer
should be aware of how the problem will
be seen.
Chapter 4. Installation Checklists
77
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
12 If because of a machine upgrade (z10 to
z114 for example) the LSYSTEM
parameter is changed, the remote
systems at the other end of the PSIFB
connection may need a dynamic activate
or a Power-on Reset (on a stand alone
CF).
If the LSYSTEM statement is unchanged,
this is not required. More information is
available in the Must Read.
4.3.4 CIU, CBU, On/Off Capacity on Demand
13 Impact on contractual requirements and
functioning of both IBM and ISV software
following an upgrade via CBU, CPE, or
On/Off Capacity on Demand to increase
processing power has been evaluated.
4.3.5 CFCC
14 Memory planning has taken into account
the structure size increases associated
with various CFCC level releases.
More storage is required for CFCC 17.
See the MustRead.
15 See the Driver Exception letter to
determine the minimum MCLs required
for coupling facility connectivity on all
systems in the Sysplex.
4.3.6 IBM and ISV Software Support
16 IBM and ISV vendor software licensed by
CPU serial number has been licensed for
the z114 CPC serial number.
17 For z114 in a plex, an agreement for
Advanced Workload License Charges
must be in effect if z/OS, z/VSE or z/TPF
will run on the z114. (Note: this excludes
customers who will remain on PSLC
pricing.) See the MustRead.
18 For z114 NOT in a plex, An agreement for
Advanced Entry Workload License
Charges must be in effect if z/OS, z/VSE
or z/TPF will run on the z114. (Note: this
excludes customers who will remain on
PSLC pricing.) See the MustRead.
78
SA11-002-02
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.3.7 Crypto
19 The latest version of ICSF should be
installed to take full advantage of the new
crypto hardware capabilities on the 2817.
Prior support provides the
same capabilities for
Crypto Express3 as found
on the z10.
Please see
http://www.ibm.com/systems/z/os/zos/do
wnloads/.
20 Installation of a more current version of
ICSF may require compatibility fixes
(PTF’s) for ICSF be installed on older
systems that share the key repositories
(CKDS, PKDS or TKDS).
21 A TKE wizard is available to allow users
to collect configuration data, from a
Crypto Express2 and configuration data
and key material from a Crypto Express3
coprocessor and migrate the data to a
different Crypto coprocessor. The target
Crypto Express coprocessor must have
the same or greater capabilities.
22 Use ICSF Healthchecks to check for the
existence of retained keys that are no
longer supported, and/or 4096-bit PKDS
support.
23 If you use a User Defined Extension
(UDX) of the Common Cryptographic
Architecture (CCA), you should contact
your UDX provider (IBM) for an updated
version of the UDX before ordering a new
server or before migrating or activating
your UDX application.
Chapter 4. Installation Checklists
79
Copyright 2011 IBM Corporation. All rights reserved.
Activity
4.3.8 Sysplex Considerations
24Ensure that all processors within the same
sysplex as the z114 are z114, z196, z10
or z9.
At the time of this writing, the D93
Exception Letter listed the following
minimum levels (subject to change):
z114 Requirements:
Required driver level for z196 is Driver
93. Minimal required code level: CFCC
Product Release 17 Service Level 4.15.
(Driver/Bundle not specified in the
Exception Letter)
Recommended MCL level for coupling:
Highest available level on D93.
z196 Requirements:
Required driver level for z196 is Driver
86. Minimal required code level: CFCC
Product Release 17 Service Level 2.25.
(D86 MCL N29866.009 Bundle 37c).
Recommended MCL level for coupling:
Highest available level on D86.
z10 Requirements:
Required driver level for z10 is Driver 79.
Minimal required code level: CFCC
Product Release 16 Service Level 4.03.
(D79 MCL N24403.011 Bundle 47a).
Recommended MCL level for coupling:
Highest available level on D79.
z9 Requirements:
Required driver level for z9 is Driver 67.
Minimal required code level: CFCC
Product Release 15 Service Level 2.12
(D67 MCL G40953.015 Bundle 57a).
Recommended MCL level for coupling:
Highest available level on D67.
These servers can not exist in the same
Sysplex as a z114: z990/z890/z900/z800
or earlier.
Note: A z9 can not be connected to an
InfiniBand HCA3-O coupling link. If using
InfiniBand on the z9, the z114 must use
an HCA2-O 12x feature. Also note that
InfiniBand on a z9 increases the z9 HSA
size by approximately 512 MB.
25 The default setting for a z114 Coupling
Facility Partition is Volatile. Ensure plans
are in place to set this to Non-volatile if
required.
More information is in the MustRead.
80
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
26 If this installation involves a model or
serial number change and IRD is being
used, plans are in place to define a new
CF structure for the cluster.
27 Check the LOADxx member to assure
customer has not hard coded a value for
the optional HWNAME parameter.
If the customer has specified the
HWNAME in the LOADxx member then it
must match the hardware processor
name as defined in the IODF.
IPL will result in 0B1 disable waits if
customer has specified the HWNAME
and it does NOT match the hardware
processor name in the IODF.
28 FYI z/VM 6.2 supports Single System Images
in a z/VM Cluster of up to four z/VM
systems, across CPCs (zEnterprise or
z10) or within one CPC.
This multisystem virtualization
technology allows the cluster members
appearing to be a single system.
With this technology, you can exploit Live
Guest Relocation, thus reducing the
effect of planned outages and provide for
load balancing.
Chapter 4. Installation Checklists
81
Copyright 2011 IBM Corporation. All rights reserved.
Activity
4.3.9 Linux Considerations
29 The Linux Installation Checklist has been
obtained and reviewed. See Must Read.
30 The z114 officially supports Novell SUSE
SLES 10 and SLES 11 and Red Hat
RHEL 5. Some earlier release can be run,
but some supported functions are not
available.
SLES9 SP4 latest maintenance web
update and RHEL 4.8 have been tested
on z114. Please note that both
distributions are approaching end of life.
Please check with your distribution
partner for the exact dates and start
migration planning.
When upgrading from OSA-Express2
features to the multi-port
OSA-Express4S or OSA-Express3
features, be aware that these two
distributions (SLES9 SP4 and RHEL 4.8)
will detect port 0 only. Consolidation of
ports may prove difficult and you need to
plan accordingly.
31 In order to have a Linux partition make
use of IFL engines, the partition must be
defined as a Linux only partition or a VM
Mode in the image profile.
32 If running Linux guests under VM, the VM
Directory entry must assign the crypto
cards to the appropriate guests. If running
Linux in an IFL, the LPAR Activation
profile must assign the crypto cards as
appropriate.
33 The appropriate device drivers must be
installed to access the crypto hardware.
34 If using a Crypto Express3 as a
coprocessor you must install the IBM
CCA Support program software.
82
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
35 z/VM Live Guest Relocation (LGR)
provides the capability for a running Linux
virtual machine to be moved without
disruption from one z/VM system to
another within a Single System Image
(SSI).
The Unified Resource Manager has been
enhanced with Driver 93 to support life
cycle management of individual
members within a z/VM V6.2 SSI
environment.
FYI - Unified Resource Manager:
Driver 93 is required for managing z/VM
6.2. However, the Unified Resource
Manager does not support Live Guest
Relocation (LGR).
Additional information is at the following
website: http://www.vm.ibm.com/
36 Driver 93 for the z114 level changes the
HiperSockets firmware such that patches
are required for Linux on System z. See
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/FLASH10762 or
the Driver Exception Letter for details.
4.3.10 zIIP and zAAP Considerations
37 Appropriate sizing tools have been used
to determine the benefits associated with
the use of either zIIP or zAAP processors
in the environment.
38 For your awareness, you may now run
System z Application Assist Processor
(zAAP) eligible workloads on System z
Integrated Information Processors
(zIIPs).
“zAAP on zIIP” planning considerations
can be found at
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/WP101642
Chapter 4. Installation Checklists
83
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
4.3.11 SCRT Considerations
39 Any customer who collects SMF data on
the z114 for processing by Sub-Capacity
Reporting Tool (SCRT) must use the
latest level to generate their next SCRT
Reports.
This latest level of SCRT will be available
for download from the SCRT website:
http://ibm.com/zseries/swprice/scrt/
IBM's policy requires you to always use
the most current Version of SCRT.
However, IBM does not require a specific
Release level. Therefore, you may select
the appropriate release within the current
version for your environment. Please
note that only the most current version
and release are available for download
from the website.
4.3.12 OSA-Express4S and OSA-Express3 Considerations
40 For the operating system to recognize all
ports on an OSA-Express4S or
OSA-Express3 (QDIO CHPID
TYPE=OSD), a PTF may be required.
If software updates are not applied, only
one of the two ports on a CHPID will be
visible to the operating system.
See the MustRead for advice on the
Portname parameter.
41 Note: The OSA-Express4S features do
not support CHPID TYPE=OSN.
84
SA11-002-02
Comments
Copyright 2011 IBM Corporation. All rights reserved.
4.4 Installation Plans
Table 9. Installation Plans
Activity
Status
Due Date
Owner
Comments
4.4.1 General
1
The customized information planning
application available on ResourceLink
has been used to plan for the installation
of the z114.
2
An installation plan is in place and agreed
to by all participants
3
If FC0025 is ordered on the z114 with a
zBX, the zBX part installation should not
be delayed until another day or weekend.
Please have all of the prerequisites ready
(OSAs, HMCs, cabling, etc) and follow
the installation instructions, as written. If
you attempt do the install piecemeal, call
home events will occur every 15 minutes.
If you plan diverge from this advice, you
should have the SSR contact service
planning or product engineering or the
Opportunity Project Office (OPO).
4
For a coupling facility partition on the
z114, verify that the CFRM policies have
been updated to use the Partition
Identifier as specified in the image profile
of the HMC.
5
Plans are in place to account for any
impact to other systems in the
environment which may be affected by
the installation of the z114.
i.e. Deactivate any coupling link or CTC
connections on other connected systems
prior to an upgrade or you may
experience boxed devices.
However, you must account for other
servers depending on STP message for
time synchronization.
6
Any coupling facility in the sysplex with
connectivity to the z114 must be at the
latest supported CFCC level as defined in
the Driver Exception Letter.
7
For an upgrade which will reuse existing
channel cards, the z114 cannot be
powered on until the cards have been
moved to the new z114.
Chapter 4. Installation Checklists
85
Copyright 2011 IBM Corporation. All rights reserved.
Activity
8
FYI - Minimum required code level to
perform an MES frame roll upgrade from
a z10 BC to a z114.
- z10 must be Driver 79
- MCL N24409.128 Bundle 36a
- Recommended MCL level for MES
activity: Highest available level on D79
- See the Driver Exception Letter to
determine if the minimum requirements
have changed.
9
Driver Exception Letter (available on
ResourceLink) has been reviewed for
any restrictions affecting the installation
of the z114.
Tip: This is also important when you are
upgrading a System z server that
includes a new Driver level.
10 IBM Personnel will monitor for any alerts
released which may affect the installation
of the z114.
4.4.2 FICON Considerations
11 z114 FICON has a changed function (for
FCP channels using NPIV) that allows to
use an assigned WWPN for the physical
WWPN.
In the past whenever a FICON card was
replaced, the customer needed to
change their Switch for zoning due to a
built-in WWPN.
Now WWPN has affinity with the CHPID
and not the physical card. So now, the
customer does not need to update the
zoning after card replacement.
12 Migration from older technology to newer
technology both in processors (such as
z9 to z114) or a migration in channel I/O
(such as FICON Express2 to FICON
Express8S or FICON Express8), can
cause performance stress in the existing
SAN (Storage Area Network).
It is very important to review the SAN
infrastructure for potential hot spots of
contention in devices, switches, and
cabling prior to the z114 installation.
This review should include a thorough
performance evaluation using RMF
(Resource Measurement Facility) ESS
link statistics reports.
See the Must Read.
86
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
13 The FICON Express8S or FICON
Express8 10KM LX feature is designed to
support distances up to 10 kilometers
(6.2 miles) over 9 micron single mode
fiber cabling without performance
degradation.
To avoid performance degradation at
extended distance, FICON switches or
directors (for buffer credit provision) or
Dense Wavelength Division Multiplexing
(for buffer credit simulation) may be
required.
See “MustReads” for further information.
14 For FICON Express8S or FICON
Express8 configurations, implementation
plan has taken into account the reduction
in buffer credits and the effect of distance
and link speed on buffer credits.
15 When changing to an 8 Gb/s structure for
FICON, changes may be required to the
attached switches/directors. Contact your
switch vendor for advice.
Note: FICON Express8S and FICON
Express8 can run at 2, 4, or 8 Gbps
only.
16 IBM encourages customers to exploit
zHigh Performance FICON (zHPF). This
is a System z no charge function that can
significantly improve FC channel
performance. See the MustRead for
requirements.
4.4.3 CHPID Mapping Tool
17 The preferred option for using the CHPID
Mapping Tool is the Availability Option.
However, it is imperative that regardless
of what option is used to map the z114, an
analysis has been made to determine the
impacts to the cabling infrastructure.
18 Appropriate customer personnel who will
run the CHPID Mapping Tool have
acquired an IBM Registration ID for
access to ResourceLink ID, the Mapping
Tool has been installed on the
appropriate customer workstation(s), and
the configuration files have been
successfully obtained.
Chapter 4. Installation Checklists
87
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
19 The z114 and z10 versions of the CHPID
Mapping Tool do not support loading of a
saved session file generated in the
previous version. If there is a need to load
an earlier saved session file, then the
user should keep a copy of the update
files and use the update function of the
tool to switch between the different
versions.
4.4.4 Configuration files and PCHID assignment changes
20 If the installation involves an upgrade or
migration from an older processor,
ensure the customer has backed up any
channel customization data.
The MustRead explains this in more
detail.
21 Output reports from the CHPID Mapping
Tool will be available for any PCHID
changes that may have been required
and need to be accounted for as part of
the upgrade or migration to a z114.
4.4.5 Capacity Back Up and On/Off Capacity on Demand
22 If an older machine is being displaced
and if it had temporary CoD records on it,
see the MustRead for removal
instructions prior to powering down the
older machine.
23 For any machine being upgraded to a
z114 that has OOCoD records, customer
will need to download from ResourceLink
any OOCoD records that will be used on
the z114.
Note: As part of this step, the machine
records on ResourceLink will need to be
updated to reflect the new machine and
the SSR must transmit the TSAD data
after the upgrade.
24 Plans are in place to adequately test the
CBU and On/Off Capacity on Demand
Procedures.
88
SA11-002-02
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
25 For new machines with temporary
capacity ordered (any record type) the
machine will have up to 4 temporary
orders available as installed records.
This is new with z114. They were only
staged records on the z10. If there are
more than 4 temporary records on the
z114, all will be staged, and none will be
installed.
This is only available on an initial
new-build order. Not available on an MES
upgrade to the z114.
26 Customer is aware that the Capacity on
Demand (OOCoD, CBU, CPE, etc.)
usage on the z114 and z10 is significantly
different on the zEnterprise as compared
to the z9 and previous generations. Plans
are in place to become familiar with the
changes and new procedures required.
27 Procedures and policies should be
reviewed if On/Off Capacity on Demand
is ordered for a Disaster Recovery
Machine configured with CBU which is
part of a GDPS environment.
4.4.6 Hardware Management Console LAN
28 Ensure that a unique TCP/IP address is
available for each of the Support
Elements on the z114 and each
Hardware Management Console on a
common LAN.
Business as usual.
Note that if Unified Resource Manager is
being deployed, the Primary HMC and
Alternate HMC must be on the same
subnet.
4.4.7 ESCON Converters and 3745 (Carry over from past servers)
29 The MustRead section has been
reviewed for any restrictions associated
with the use of ESCON converters.
Nothing new as compared
to previous System z
servers.
Note: The z114 is the last high-end
System z server that will support ESCON.
Chapter 4. Installation Checklists
89
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.4.8 HCD/IOCP DEFINITION
30 Plans are in place to ensure the IOCDS
will be loaded on the z114.
The z114 level of HMC allows the loading
of the IOCP source file from a USB flash
memory smart drive (formerly referred to
as the memory key).
4.4.9 Software
31 Review the recommendations for the
CPENABLE Parameter.
32 RSU parameter is set correctly for the
storage size and granularity. See Must
Read.
4.4.10 Activation Profiles
33 Customer is aware that the Dynamic ICF
Expansion function is not available on the
z114.
34 Reserved processors will be defined as
appropriate in each image profile that
would use additional processors
following a concurrent upgrade or change
to the operating characteristics of the
partition which increases the number of
allocated processors.
Note: Reserving processors is not
required if using z/OS V1.10 or higher or
z/VM 5.3 + PTF.
See the Logical Processor Add icon on
the HMC.
Note: Do not exceed the total number of
processors that can be supported by the
Operating System to be loaded.
35 Reserved storage is allocated to
partitions that will utilize the concurrent
memory upgrade capability.
Memory granularity frequently changes
when new machines are announced. See
the publications for specifics on the z114.
See Must Read and Checklist Section
4.4.9 Item 30 above
36 VM IMAGE MODE - On the z114 and on
the z10 there is a new Image Profile
Mode that can specified.
Do not use this Image Profile type unless
the LPAR will be IPL’ed with z/VM V5.4 or
later. See the MustRead for further detail.
90
SA11-002-02
Same as z9 and z10.
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.4.11 OSA-Express Considerations
37 If using Unified Resource Manager
(FC0025) or managing a 2458-002 zBX,
a minimum of two OSA-Express3
1000Base-T and possibly two OSA
Express4S or OSA-Express3 10 GBE
features are required.
38 This item only applies to 1000Base-T
features that are modified by OSA/SF to
run in SNA Mode.
Any time an OSA-Express2 or
OSA-Express3 card is installed or
changed, ensure that any changes to the
universal MAC address have been
accounted for.
39 During machine service, sometimes the
SSR will activate the server using IOCDS
D0.
If there is a customized OSA (modified
OAT or ICC Configuration file), the next
activation (power-on reset) may want to
use the same IOCDS (A0, A1, A2, or A3)
that was used prior to using IOCDS D0.
Or use an IOCP deck that makes no
changes to the previous OSA CHPIDs.
If not, the customized OSA files will be
lost. See the MUSTREAD for more detail.
4.4.12 Crypto Considerations
40 If the customer uses Crypto and have
implemented a Disaster Recovery (DR)
Site using a z800 or z900, insure there
are plans to migrate the CKDS records.
41 All Disaster Recovery (DR) contracts
have been reviewed to insure there is the
required support provided at the DR site.
Master keys loaded at the production site
and associated with the CKDS and PKDS
must be available and loaded into the
secure hardware at the DR site.
42 Customer is aware that keys stored
securely by ICSF and the crypto
hardware cannot be recovered without
compromise to security policies and no
work-around exists for recovery of private
keys.
Chapter 4. Installation Checklists
91
Copyright 2011 IBM Corporation. All rights reserved.
4.5 Physical Site
Table 10. Physical Site
Activity
Status
Due Date
Owner
4.5.1 General
1
IBM does not provide channel cables as
features on the z114.
Note: It is recommended that the
customer utilize the services included in
one of the options of the IBM Fiber
Cabling Services.
Refer to the MustRead and the Appendix
of the SAPR guide for a description of
these services.
2
Customer will provide the reports
generated by the CHPID mapping tool for
use during the installation.
3
If Fiber Quick Connect has been ordered,
it is understood that this will pre-wire the
z114 for both ESCON and FICON LX
connections.
4
If using an IBM® zEnterprise™
BladeCenter® Extension (zBX), the zBX
must be near the z114. There are a pair
26 meter (85 feet) cables copper cables
supplied by IBM that must be connected
from the z114 to the zBX.
4.5.2 OSA-Express3 and OSA-Express4S Considerations
5
Review the z114 IMPP or see Must Read
to determine the port nomenclature for
the OSA-Express3 and OSA-Express4S
features.
The port numbers may not go in the
sequence as one might expect.
Also, be aware that two ports may be
assigned to the same CHPID. This can
affect you communications definitions
and/or your OSA-ICC definitions.
92
SA11-002-02
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.5.3 Cabling-Using IBM zSeries Fiber Cabling Service Contract
6
Identify which option was chosen if the
zSeries Fiber Cabling Service was
selected:
Option 1: zSeries fiber optic jumper
cabling package
Option 2: zSeries fiber optic jumper
cable migration and reuse for a zSeries
upgrade
Option 3: zSeries jumper cables and
installation (not available in EMEA)
7
Identify what option was chosen If an IBM
Enterprise Fiber Cabling service contract,
was selected:
Option 1: zSeries fiber optic trunk
cabling package (for a single zSeries
system)
Option 2: enterprise fiber cabling
(trunking for the entire data center)
8
Identify what work is included if a custom
cabling contract was selected:
Jumper Cables
Trunks
Jumper Cables and Trunks
Fiber cable clean-up under the floor
Other
9
Cabling Service contract has been
signed and returned to IBM.
10 Planning has been completed, a cable list
has been generated, and cables have
been ordered.
11 Cables will be delivered to the data center
prior to installation date.
4.5.4 Cabling-Customer Not Using IBM Cabling Service
12 All required channel cables, link cables,
sysplex timer cables, Hardware
Management Console LAN cables,
converter cables, and mode conditioning
jumper cables for the z114 processor
have been identified and placed on order.
13 A complete analysis has been made of
the connectors used on existing systems
being upgraded to the z114 to ensure that
the appropriate fiber cabling is installed.
Note: The OSA-Express4S and
OSA-Express3 10 GbE connectors are
different than OSA-Express2 10 GbE.
Chapter 4. Installation Checklists
93
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
14 If applicable, the customer has made
arrangements for installation of any fiber
optic trunk cable and panels required to
complete the installation.
15 Provisions have been made for the
labeling of all cables required for the z114
installation.
At a minimum the labels should identify
the PCHID number on the cables.
16 Accurate and current documentation is
available that illustrates clearly all of the
cabling infrastructure associated with the
processor complex.
17 All required cables will be delivered to the
data center prior to installation date.
18 Customer is aware of the services
provided as part of installation as defined
in the z114 IMPP manual and in the
Appendix B of the SAPR Guide.
19 Does the customer intend to use top exit
I/O? If so, it must be specifically ordered.
If ordering top exit I/O, be aware that the
server physical dimensions and weight
are slightly different. See Must Read.
4.5.5 Non-Raised Floor Requirements
20 Processor can either be installed on a
raised floor or a non-raised floor. If
installed on a non-raised floor, see Must
Read.
4.5.6 Power
21 Balanced power requires three phase
input power be used.
For a z114 under a certain size, single
phase input power can be used and
balanced power is optional. However, if
the z114 is over a certain size, then
balanced power is required and three
phase input power is also required.
See Must Read.
22 If the z114 is ordered with DC Power, see
the MustRead.
23 FYI, z114 can be ordered with Top Exit
Power.
94
SA11-002-02
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
24 There are only two power cords on the
z114. One feed from one PDU goes to
side A and one feed from other PDU goes
to side B.
Care has been taken to correctly
configure the power feeds to the site
PDUs.
One feed from one PDU go to side A and
one feed from other PDU go to B-side.
25 Customer has obtained and reviewed
Installation Manual for Physical Planning
for the z114 electrical service
requirements. This manual is available on
ResourceLink.
26 Customer has arranged for contracting of
electrical service and that the electrical
work is on schedule.
Two power cables per
power feature code.
27 The use of a metal backbox is strongly
recommended for power.
28 FYI: There is a Power Estimation Tool
available on ResourceLink. It now also
provides approximate weight of your
machine, based on the features being
installed.
4.5.7 Cooling
29 Installed air conditioning and ventilation
equipment satisfy the cooling and air flow
requirements for the z114 processor.
4.5.8 Floor Space
30 Space requirements, floor loading, and
service clearance requirements meet or
exceed the requirements as listed in the
IMPP. See 4.5.4 Item 19 above if Top Exit
I/O is ordered.
31 Required floor panels for access holes
have been marked, cut, and set in place
prior to delivery of the z114.
32 Additional support pedestals at selected
cut floor panels have been installed
where required.
Chapter 4. Installation Checklists
95
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
4.5.9 Hardware Management Console
33 A suitable location has been determined
for any new hardware management
consoles.
Note: This should take into account the
physical form factor (physical size) for the
new Hardware Management Console.
Both the PC hardware unit and/or the
display may be different than a previous
model.
34 Two 110/120 VAC power outlets (NEMA
5-15R) are available within six feet of
planned location for any new hardware
management console.
35 Customer understands that disruptions to
a LAN not dedicated to the Hardware
Management Consoles may interfere
with operating the z114 and can affect the
operation of components in a defined
ensemble.
36 It is recommended that customers use
the ethernet switch that can be ordered
with the z114 and a power outlet will be
provided for the switch.
Note: If the switch is to be connected to
the customers intranet, it should be
connected in such a manner that it can be
quickly disconnected in order to facilitate
problem determination.
Note: The configurator used to create the
z114 order currently defaults to quantity
of 0 for the ethernet switch. With the
z114, the recommended LAN
configuration is different from previous
processors and it is recommended that
two of the switches be provided.
96
SA11-002-02
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
37 HMC ordering considerations:
If Unified Resource Manager will be used
(FC0025), a minimum of two HMC’s must
be available.
One of the two is an alternate Ensemble
HMC. The alternate can not be used at all
unless it takes over as the primary
following a primary HMC failure.
Therefore, customers using Unified
Resource Manager may want to have a
total of three HMCs or more available.
The primary Ensemble HMC can
continue to perform the duties of any
standard HMC.
38 If FC0025 is a feature on the z114 (even
without a zBX), the following information
will need to be obtained from the
customer and will be used at installation
time by the SSR.
The name of primary ensemble HMC.
The name of alternate ensemble HMC.
The ensemble name.
The ensemble description.
The ensemble HMCs must be defined by
service during the installation. The
Alternate HMC can only be used for
mirroring the Primary HMC.
4.5.10 Telephone and Remote Support Service
39 A separate analog telephone line is
installed within 15 feet of each hardware
management console for RSF access, if
used.
Note 1: If a zBX to be installed and
owned by this z196, RSF via broadband
is required. MCL delivery for the zBX is
designed only for broadband delivery. If a
modem is used, MCL retrieval is not
possible (RETAIN file size Limitations).
Note 2: The z114 will be the last System
z server to support dial-up modems.
Chapter 4. Installation Checklists
97
Copyright 2011 IBM Corporation. All rights reserved.
Activity
40 IBM VERY STRONGLY recommends
that the customer use the internet via
broadband for the RSF function.
If the RSF internet feature is to be used,
customer has established the appropriate
network infrastructure and security
requirements.
The requirements for setting up this
interface have been reviewed and plans
are in place to implement. Documentation
is on ResourceLink.
41 A separate voice telephone line and
instrument near each hardware
management console will be provided.
4.5.11 Machine Arrival
42 The customer has made arrangements to
accept shipment of the z114.
A staging area for equipment (if required)
before installation has been identified.
The location where the z114 will be
placed or stored meets appropriate
temperature and humidity environment
requirements to protect it until installation
and power on.
Note: Specifications identified in the
IMPP manual should be reviewed.
43 Special arrangements with movers have
been made, if required, such as floor
protection material for office hallways.
44 Customer security or audit personnel are
scheduled to accept equipment into
inventory records.
45 A point of contact at the customer
location has been identified in the event
that the trucking company driver needs to
make contact in an emergency.
46 Customer's receiving dock can
accommodate the delivery truck and the
transfer of the equipment.
47 Path from the receiving dock/staging area
to the computer room has been
evaluated.
98
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
48 It is vital that systems services
representatives (SSRs) and the customer
understand that moving equipment that
weighs in excess of 500 lbs. (227kg) and
is 60 inches (152.4 cm) or more in height
can cause personal injury or equipment
damage.
Only professional movers or riggers
should move or transport equipment that
falls into this category. IBM incorporates
this requirement in the agreement with
the shipping company.
4.5.12 OTHER
49 Ensure FC0033 has either been selected
or deselected as desired. If not selected,
the machine will not ship with the Service
Guide, Install Guide, or Safety inspection
guide.
See the MustRead for more information.
50 Arrangements have been made for the
timely removal of discontinued or
displaced equipment/parts that need to
be returned to manufacturing.
Note: For servers purchased via the
System z Exchange Program (formerly
known as a hybrid offering), a
considerable amount of unfolded packing
material is included for shipping the older
components back to IBM. This could
become a potential storage issue,
especially if more than one server is
being displaced.
There are two ways in which or order
return packing material. You may use
either an RPQ order during the eConfig
run or IBM Global Technology Services
(GTS).
Note: IBM Global Technology Services
will require a separate contract, whereas
the eConfig method will not.
If you want the packaging material
delivered at a later date than when the
new machine arrives, use the GTS
website.
See
http://rtsweb1.raleigh.ibm.com/SSRHom
epage/packingsealing.html.
51 Arrangements have been made for the
timely removal of packing material and
trash.
Chapter 4. Installation Checklists
99
Copyright 2011 IBM Corporation. All rights reserved.
4.6 System Management Plans
Table 11. System Management Plans
Activity
4.6.1 Problem Management
1
Ensure that any problem encountered
with software installed on the Hardware
Management Console (a PC) will be
treated as a “z114 Hardware” problem.
Business as usual.
2
Customers may now submit unreported
hardware problems that are Unified
Resource Manager - Ensemble related.
Problem Management Viewable (PMV)
records are designed to report problems
that do not automatically call home.
Unlike other hardware PMHs, PMVs are
viewable by the customer.
4.6.2 Service and EC Updates
3
Customer has plans in place and is
committed to staying at the latest driver
and MCL level of the machine.
4
Customer understands the microcode
maintenance strategy for the z114 and
the ability to perform enhanced driver
maintenance.
5
Customer understands that the z114 or
some features will occasionally have to
be taken out of service to apply
engineering changes and some LIC
machine change levels.
4.6.3 Operations
6
Procedures are in place to manage the
assignment of activation profiles either
manually or via the automated features
provided in the Hardware Management
Console.See Must Read for online
documentation websites.
4.6.4 Availability Management
7
100
Historical availability data is available for
any system(s) being replaced by the
z114.
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
4.6.5 Security
8
Requirements for passwords and userids
for the Hardware Management Console
and Support Element of the z114 Server
have been determined.
Same as z10.
9
The HMC on the z114 includes a new
security audit function.
Same as z196
If applicable, review the HMC User’s
Guide and see the MustRead.
10 If planning to implement a zBX solution,
see recommended reading on network
security - (URL listed in the MustRead).
4.6.6 Customer/IBM Meetings
11 The z114 installation project team will
schedule meetings on a regular basis to
review the progress of the installation
plan.
Chapter 4. Installation Checklists
101
Copyright 2011 IBM Corporation. All rights reserved.
4.7 RSF and Internet Remote Support
Table 12. Communication and Networking
Activity
4.7.1 RSF
1
Remote Support Facility (RSF) use is
understood and all phone lines are ready
if the analog modem will be used.
2
Remote Support Facility (RSF)
information will be verified and updated
as required.
4.7.2 Internet
3
102
Customer has made arrangements for
internet remote support to include
infrastructure and required security
precautions.
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
4.8 Resources and Responsibilities
Table 13. Resources and Responsibilities
Activity
Status
Due Date
Owner
Comments
4.8.1 General
1
Appropriate IBM and Customer
resources have been identified and
scheduled to support the installation.
4.8.2 Agreement On Responsibilities
2
Customer and IBM agree on the
responsibilities for assigned tasks to
accomplish the installation.
Chapter 4. Installation Checklists
103
Copyright 2011 IBM Corporation. All rights reserved.
4.9 Service Offerings
Table 14. Service Offerings
Activity
4.9.1 General
1
Customer understands any services
included as part of the z114 or zBX
installation.
See the MustRead for examples of
available services.
2
104
z114 Installation Practices and
Policies section in the SAPR appendix
has been carefully reviewed to determine
if there will be any fee based services
required for the installation.
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
4.10 Installation Planning and Documentation
Table 15. Planning and Documentation
Activity
Status
Due Date
Owner
Comments
4.10.1 Teams
1
Members of the z114 installation team
have been identified.
2
Customer and IBM team leaders have
been identified.
4.10.2 Plan Documentation
3
Method of recording, updating, and
distributing an installation plan has been
defined.
4
Checkpoint meetings with the customer
and IBM have been scheduled.
4.10.3 Systems Assurance Confirmation Form
5
After putting a z114 on order, a member
of the IBM or IBM Business Partner
Account team must complete the
Systems Assurance Confirmation Form
on ResourceLink.
Chapter 4. Installation Checklists
105
Copyright 2011 IBM Corporation. All rights reserved.
4.11 Business Partners
Table 16. Business Partners
Activity
4.11.1 RESPONSIBILITIES
1
106
All parties (IBM, customer, and business
partners) understand each others roles
and expectations. If these relationships
are not established by a formal contract,
it is recommended that expectations be
documented in letters of understanding.
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
4.12 zIIP Considerations
Note: There may be some redundancy in this section with previous checklist
items. However, an order which only adds zIIP processors requires a Systems
Assurance Review per the Designated Product List and this section can be used
as an isolated entity for those situations. It is still strongly recommended that for a
zIIP only Systems Assurance the remainder of the checklists be at least quickly
scanned outside of the formal review.
Table 17. zIIP Considerations and Planning
Activity
Status
Due Date
Owner
Comments
4.12.1 General
1
Customer's planned implementation and
use of the zIIP processor is understood
by the IBM Account Team.
2
Applicable publications can be obtained
from the TechDocs internal and external
web sites.
Internet:
http://www.ibm.com/support/techdocs
Intranet:
http://w3.ibm.com/support/techdocs/ats
mastr.nsf/Web/Techdocs
Many of these are listed in the Must
Reads Section.
3
The customer is aware that a zIIP can be
added as part of both a CIU and CBU
contract.
4
Customer is aware that a zIIP can be
added via an On/Off Capacity on
Demand order and understands there is
one 24 hour test allowed on the z114 but
no administrative test are allowed on a
z10 EC or z10 BC.
5
Customer is aware that the total number
of zIIP Processors cannot exceed the
number of purchased general purpose
processors (Active + Undefined).
6
Customer is aware that a zIIP processor
can only be used on a z9 at driver 67, the
final driver level for this processor.
The zIIP is supported on the z114, z196,
z10 and z9.
7
DRDA workloads that make use of Stored
Procedures and/or User Defined
Functions (UDFs) are not eligible to be
off-loaded to the zIIP.
Chapter 4. Installation Checklists
107
Copyright 2011 IBM Corporation. All rights reserved.
Activity
8
Contractual requirements associated
with the zIIP acquisition are in place and
agreed to by the customer and IBM.
9
The maintenance that is required to
support the zIIP processor will NOT be
found in one PSP bucket.
It is imperative that you read the chapter
System z Integrated Information
Processor contained in the SAPR Guide,
as well as this zIIP Checklist
Considerations, and the Must-Reads
section which can all be found in the
System Assurance guide.
Flashes 10477 (Positioning Software for
the z9 EC and z9 BC Servers),
TD104518 (z/OS Positioning Software for
z10 EC and z10 BC Servers) and Flash
TD103516 (zIIP and zAAP Software
Update) which can all be found on the
TechDocs website provides information
on how to obtain all the required
maintenance using the Enhanced PSP
Tool.
Note: The Enhanced PSP Tool will be
obsolete after December 2010.
Effective December 31, 2010 the
Enhanced PSP Tool's function has been
replaced by the addition of FIXCAT (fix
category) information to Enhanced
HOLDDATA and the REPORT
MISSINGFIX function introduced in z/OS
V1.10 SMP/E, which offers distinct
advantages over the Enhanced PSP
Tool. This SMP/E function is also
available for all supported releases of
z/OS in SMP/E for z/OS V3.5
(5655-G44), which you can order
separately. Enhanced HOLDDATA is
available in all IBM service delivery
offerings and in the 730-day file from the
Enhanced HOLDDATA Web site at
http://service.software.ibm.com/holdata/
390holddata.html
108
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
10 zAAP workloads on zIIPs:
The following IBM functions can now take
advantage of a zIIP processor.
- Portions of BI, ERP, and CRM remote
connectivity to DB2.
- IPSec Network Encryption
- XML Parsing
- Global Mirror Function
- HiperSockets for outbound large
messages
- IBM Scalable Architecture for Financial
Reporting
- z/OS CIM Server processing for
Intra-Server Communications
- DB2 Sort Utility using IBM's memory
object sorting technique zAAP work
(JAVA) is now supported on zIIP if no
zAAPs installed on the server.
11 One hundred percent of the middleware
and applications requesting z/OS XML
System Services Parsing in TCB Mode
will execute on a zAAP processor. This
was made available with z/OS 1.9 and
DB2 V9 and rolled back to z/OS 1.7 and
1.8.
Additionally, z/OS XML Services
executing in SRB mode will be partially
directed to a zIIP when utilized as part of
any zIIP eligible workload (like DRDA
workloads). This partial zIIP redirection is
available with z/OS 1.8 and with
maintenance on z/OS 1.7 with DB2 V9 in
New Function Mode only. The same
percentage of this XML work in SRB
mode is redirected to the zIIP as is DB2
DRDA work.
One hundred percent of the z/OS XML
System Services parsing, called in SRB
Mode, is now zIIP eligible with DB2 V9
and z/OS 1.10.
12 If you are testing with DB2 V9 and XML,
with the proper levels of software, you
can use the PROJECTCPU facility in
z/OS for XML inserts, loads, and queries
to measure these workloads and show
what workload is eligible for zAAPs and
zIIPs
.
Chapter 4. Installation Checklists
109
Copyright 2011 IBM Corporation. All rights reserved.
Activity
4.12.2 Performance
13 Appropriate sizing tools and
methodologies have been used to
determine the expected benefits of
installing a zIIP processor as well as the
impact to the overall system
performance. PROJECTCPU is the best
method for accomplishing this.
Note: This issue is critical and proper
sizing is a must in order to ensure the zIIP
meets the expected results for the
customer's workload and applications.
The addition of zIIP processors will also
impact the overall performance
characteristics of the server. The use of
single number metrics (MIPS, MSU, etc)
is not acceptable. zPCR, zTPM or
zCP3000 must be used to estimate the
overall effect of adding zIIP processors.
14 The customer's plan for measuring and
evaluating the performance of the zIIP
has been determined.
15 Specialty CPs including the zIIP
processor will run at full speed on the
z114, z10 and z9 processors even when
the base processor is running as a
sub-capacity model.
16 Customer is aware of the changes to
SMF records and RMF reporting in
support of the zIIP processor.
4.12.3 Education and Training
17 Provisions have been made for customer
personnel to obtain training in the
definition, use, and function of the zIIP
processor and associated reporting tools
if required.
110
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
18 There are multiple documents that should
be reviewed on the TechDocs Website:
http://www.ibm.com/support/techdocs
The document numbers are:
- PRS2123 - 'WSC Experiences with the
zIIP Processor'
- TD103516 - Specialty Engines zIIP and
zAAP Software Update
- PRS2220 - 'Utilizing zIIP Processors for
Data Warehousing and BI Apps.
- WP100836 - 'IBM System z9™ zIIP
Measurements: SAP® OLTP, BI Batch,
SAP BW Query, and DB2 Utility
Workloads'.
- TD103622 - Checklist for zIIP and zAAP
Trials
See the Must Reads Section for more
information on these and additional
documents on zIIPs.
19 There is an excellent White Paper on
XML on the TechDocs Website WP101227 DB2 V9 and z/OS XML
System Services Synergy Update.
See the Must Reads Section for more
information.
4.12.4 Sizing the zIIP Requirement
20 The most accurate way of sizing the zIIP
requirement is to use the PROJECTCPU
option in IEAOPTxx in SYS1.PARMLIB
which requires a minimum of DB2 V8 and
z/OS 1.6 with the Web Deliverable. This
deliverable is included in z/OS 1.8.
21 If the customer is still running z/OS 1.6,
z/OS 1.7 or 1.8 (all unsupported) and
DB2 V8, there is a zIIP Web Deliverable
available on the z/OS Downloads website
that must be installed for 1.6 and 1.7 only.
http://www.ibm.com/systems/z/os/zos/do
wnloads
Chapter 4. Installation Checklists
111
Copyright 2011 IBM Corporation. All rights reserved.
Activity
22 Insure that all the appropriate
maintenance for the hardware, Web
Deliverable, z/OS and DB2 is installed by
checking the appropriate Hardware
Device and Software PSP buckets and
TD105581 on the Techdocs website.
The recommended way to apply
maintenance is using SMP/E 3.5 and the
FIXCAT category in HOLDDATA which is
discussed in referenced flashes.
23 The zIIP Web deliverable on the z/OS
downloads site is integrated into z/OS 1.8
and 1.9 and is no longer necessary for
these z/OS releases.
4.12.5 Software
24 Software Maintenance for the processor
and subsystems should be carefully
reviewed on a regular basis.
Note: This should be done for the initial
install as well as for any future upgrades
to the machine either by feature
adds/removes, processor conversions, or
upgrades to a newer driver level.
For information on all the software and
maintenance that must be installed to
support the zIIP processor, see
TD105581 on the Techdocs Website:
www.ibm.com/support/techdocs/atsmast
r.nsf/Web/TechDocs
25 The minimum requirements to support
the zIIP processor are z/OS 1.6 or 1.7
with the Web Deliverable and DB2 V8.
The specific DB2 workloads that will
exploit zIIP are portions of DRDA,
complex long running queries as well as
some DB2 Utility Functions including
DB2 sort utility.
Other workloads which will exploit the
zIIP are IPSec, HiperSockets for Large
Messages, B.I. (IBM Scalable
Architecture for Financial Reporting),
z/OS Global Mirror, z/OS CIM Server for
Intra-System communications and XML.
26 DB2 can exploit the zIIP processor if DB2
V8 is running in Compatibility Mode.
112
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
27 The pre-requisites for zIIP assisted IPSec
are:
- z114
- System z10
- System z9 at driver 67
- z/OS 1.8 + Maintenance for z/OS
Communications Server and TCP/IP.
As stated in other checklist items all the
maintenance required for zIIP processing
is not in one PSP bucket.
See Flashes 10477 and TD103516, and
WP100988 (Capacity Planning for zIIP
Assisted IPSec) for all the information on
obtaining the necessary maintenance to
support zIIP processors.
28 If you already have IPSec enabled, you
only need to make two additional
configuration changes to enable zIIP
Assisted IPSec.
1. z/OS Communications Server
Configuration
Modify the configuration statement to
change the default setting:
GLOBALCONFIG ZIIP IPSECURITY
Note: The default is NOIPSECURITY
2. WLM Policy Customization:
Although this is an optional customization
task, it is strongly recommended that you
also complete this step. See the
'Enabling The Support Section of White
Paper WP100988 (Capacity Planning for
zIIP Assisted IPSec) and PRS2745
(WSC Experiences with IPSec) in
TechDocs for additional information.
29 Depending on the level of z/OS software
that you are running as well as the
maintenance level of that system, the
options in IEAOPTxx for CrossOver and
HonorPriority which control how z/OS will
dispatch zIIP and zAAP eligible work and
whether it flows back to the general
purpose CPs have changed and these
must be understood and specified
correctly to obtain the desired results.
4.12.6 ISV Software Support
30 ISV vendor software licensed by CPU
serial number has been evaluated for any
impacts due to the use or addition of a
zIIP processor on the z114, z196,
z10-EC, z10-BC, z9-EC and z9-BC.
Chapter 4. Installation Checklists
113
Copyright 2011 IBM Corporation. All rights reserved.
Activity
31 Customer can use the "D M =CPU'
command to display the status of any
Specialty Processor.
4.12.7 Installation Plans
32 Plans are in place for defining and
evaluating the zIIP.
33 Appropriate Driver Exception Letter
(available on ResourceLink) has been
reviewed for any restrictions affecting the
installation or use of the zIIP processor.
4.12.8 Activation Profiles
34 Customer understands that the Activation
Profiles for any LPAR(s) that plan to use
zIIPs must be updated by specifying
zIIPs in either the INIT or RESERVED
field. If the zIIP has been previously
defined in the RESERVED field, then for
z/OS to use it, it can simply be Configured
online.
On a z9-EC and z9-BC, if the zIIP has not
been previously defined to the LPAR, the
LPAR must be Deactivated, Reactivated
with the zIIP defined and Re-IPL'ed in
order for z/OS to use it.
On a z10 and later, even if the zIIP was
not previously specified, this is
accomplished -without an LPAR outageusing the HMC and SE task called
‘Logical Processor Add’.
The presence of zIIP can be verified by
issuing the Display Matrix Command on
the MVS console. See the Must Read
section for an example of this command.
35 Customer understands that shared IFL,
ICF, zAAP and zIIP processors are now
managed by PR/SM in separate pools
and can have separate weights.
114
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
36 On the z9-EC and z9-BC, In order to
avoid an IPL following a concurrent
upgrade, reserved processors should be
specified for any partition that will use the
added resources. However, an IPL of an
operating system that does not support
the total number of processors defined to
the LPAR (the sum of initial and reserved
GPs and the initial and reserved zIIPs
and zAAPs) will result in a failure of the
IPL.
Note: z10 and z/OS 1.10 and later
support dynamically modifying the image
profiles to change the value of reserved
processors. See Logical Processor Add.
4.12.9 IRD Considerations
37 If you are utilizing IRD (Intelligent
Resource Director), be aware that IRD
will only manage general purpose CPs
and not any of the specialty processors.
However in z/OS 1.11 on a z114 or z10
processor, HiperDispatch will manage
zIIPs.
4.12.10 Systems Assurance Confirmation Form
38 For an MES order that only adds zIIP
processors, there is no requirement for
an IBM Account team to complete the
Systems Assurance Confirmation Form.
Chapter 4. Installation Checklists
115
Copyright 2011 IBM Corporation. All rights reserved.
116
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 5. Must-Read Information
5.1 MR-Customer Expectations
5.1.1 General
1. It is critical that the IBM Account Team and customer completely understand
the planned usage and implementation of the processor. It is highly
recommended that the review start off with an overview of the project by the
customer. Although this review will focus on the processor installation, it is
important to have an overall understanding of the customer’s enterprise in
terms of mission and goals.
2. It is extremely important that the machine configuration match what the
customer expects. It is also important to verify that the channel types being
ordered match the I/O device which will attach. For example, some channels
offer the option of Long Wave or Short Wave characteristics. The device
attaching must match.
All features on a base machine should be reviewed against the proposed
machine. It may be that some features cannot be carried forward and this
needs to be evaluated.
• FC0033 Service Docs Optional Print
Declining this feature will result in the following guides to not be shipped in
paper format. The guides however continue to be available, and printable,
from the documentation DVD that is shipped with every machine
• Service Guide
• Install Guide
• Safety inspection guide
Rules on usage:
• Do not de-select the hard copy doc if this is the first machine at this
location (Same address, same building and same floor)
• Allow de-selection of subsequent copies if multiple machines are
ordered/shipped in the same timeframe.
• Do not de-select the hard copy doc at this location if this is a "dark
account" (raised floor that does not allow laptops and/or media inside)
• Although not selectable as part of the configuration process, IC channels and
Hipersockets require real CHPID numbers and should be included in any
configuration analysis. The CHPIDs to be used for InfiniBand channels should
also be considered.
• Any machine that will be in an ensemble requires FC0025, regardless of
whether or not there is a zBX.
• The Hardware Management Consoles has very specific requirements when
using FC0025, Unified Resource Manager. Both the Primary HMC and
Alternate HMC must have various identical components.
• For customers migrating from a machine that has parallel channels, it should
be verified that the new system no longer requires parallel channels or that
appropriate ESCON converters have been ordered.
Chapter 5. Must-Read Information
117
Copyright 2011 IBM Corporation. All rights reserved.
• For customer upgrading a processor which is part of a parallel sysplex
environment, it is important to account for the requirement that all coupling link
channels be defined to run in peer mode. Processors being upgraded which
have ISC coupling links defined to run in CFS/CFR mode will require a
redefinition of those links to peer mode before the upgrade.
• All of the following features should be verified
•
•
•
•
•
•
•
Quantity and types of channels (including coupling links)
Verify the usage of long wave and short wave channel types
Quantity and types of processors
Memory
Hardware Management Console features
Capacity on Demand features (CIU, OOCoD, CBU, CPE)
Crypto Features
Note: In verifying that the order represents the desired configuration, the CHPID
Mapping Tool along with the CFREPORT file from eConfig may prove to be very
valuable. The customer could use the tool with a planned IOCP file and verify that
the features in the IOCP are on the planned machine as well as to identify early in
the planning cycle any availability issues that could be resolved with the addition
of IO.
The analysis should include not only processor CPs but also ICF, IFL, CBU, zIIP,
zAAP, and SAP requirements.
3. To engage the zSeries Project Office, send a note to John Cholewa in
Poughkeepsie. (cholewa@us.ibm.com) with the following information:
• Client Company Name/location:
• IBM requestor name/location:
• Date Requested:
• What is driving this request?
• For example:
• Deal closure
• Migration
• Potential customer dissatisfaction with ongoing problem(s).
• Please describe some specifics of the project/request?
• What is the start time frame and duration expected?
4. The following describes the Product Engineering recommendations and
requirements:
MAKE A CURRENT BACKUP BEFORE ANY MES/MCL ACTIVITY
MCL Recommendations
• Apply and activate MCLs AT LEAST once a quarter
• Download MCLs to Removable Media (keep SUL media current)
• Use AROM/DVD/SUL when MCL apply would be disruptive
• Activate POR/IML only once after all MCL activity
• Combine MCL activity with other activity (MES/Service/Reconfiguration)
118
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Advantages
• Fewer unique LIC images to support
• Shorter download and install/activate times
• Reduced exposure to problems fixed in non-activated MCLs
• Emergency fixes can be supplied more expeditiously
EC Upgrade Recommendations
• MAKE SURE there are NO OUTSTANDING HARDWARE PROBLEMS on the
machine.
• PE recommends performing a POR, if possible, to ensure all self-test logic is
functional.
• Make a current backup before ANY EC/MES/MCL activity
Driver Migration Strategy
Because new drivers contain LIC fixes as well as new function, driver upgrades
should be installed regularly as part of normal machine maintenance. For
customers with conservative change management policies, Product Engineering
recommends migration to the latest driver one quarter (three months) after its
availability date. Once a new driver becomes available, the previous driver will be
supported with MCLs for one quarter after the availability of the latest driver. This
is done to allow Customers enough time to transition to the latest driver.
However, Customers who wish to use new function(s) associated with a new
driver may do so by having an IBM CSR install the latest driver as soon as it
becomes available.
Between driver upgrades, regular installation of MCLs is key for optimal
performance. IBM Product Engineering recommends MCLs be installed quarterly
at minimum. Hiper MCLs should be reviewed continuously and customers should
decide whether to wait for the next scheduled apply session, or schedule one
earlier if their risk assessment of hiper MCLs warrants.
Specific historical Driver recommendations:
• z114 - 2818
• D93G is the GA1 driver
• z196 - 2817
• D93G is the GA2 driver
• D86 is the GA1 driver
• z10 - 2097/2098
• D79 is the latest GA HMC/SE/TKE driver.
• D76 Customers should upgrade to D79
• z9 - 2094/2096
• D67 is the latest GA SE driver. D73 is the latest GA HMC/TKE driver.
• D63 SE Customers should upgrade immediately to Driver 67.
• z990/z890 - 2084/2086
• D55 is the latest and final SE driver.
Chapter 5. Must-Read Information
119
Copyright 2011 IBM Corporation. All rights reserved.
• D52, D53 Customers should be planning to upgrade to Driver 55.
• D51 Customers should upgrade immediately to Driver 55.
• z900 - 2064
• D3G is the latest and final SE driver.
• D34-3C Customers should upgrade immediately to Driver 3G.
• z800 - 2066
• D3G is the latest and final SE driver.
• D3E Customers should upgrade to Driver 3G.
zBX Installation:
zBX installs are designed to be concurrent with operation of the z114, however, if
back level MCLs are needed, an outage may first be needed.
MCL installs may also affect the availability of OSAs, Crypto, or CFCC. Note that
during preparation for the zBX, installing the preparation MCLs can cause the
Support Elements to be unavailable, affecting configuration changes, LPAR
activation or Capacity on Demand activations.
5.1.2 ResourceLink
5. All customer personnel requiring access to ResourceLink should obtain an
IBM Registration ID (IBM ID) and password. There is information on the login
page at the ResourceLink web site to obtain an IBM ID and password. The url
for ResourceLink is as follows: www.ibm.com/servers/resourcelink
5.1.3 Publications
6. There are no customer oriented publications shipped with the processor. All
required publications can be obtained from ResourceLink in pdf format. Refer
to the SAPR guide for further information.
Note: The z114 SAPR guide is available on ResourceLink to IBM personnel
only. The IBM Account Team is encouraged to provide a copy of the SAPR
guide to the customer to aid in the planning process. The SA process is
considered an IBM Value-add for customers installing IBM products. Thus, it is
not accessible by the general populace.
Also, the SAPR guide and the editable checklist can be obtained at the
following IBM internal web site:
• w3.ibm.com/support/assure
IBM Business Partners can obtain the SAPR guides at the following sites:
• www-306.ibm.com/partnerworld/partnertools/assur30i.nsf/Web/SA
• www-306.ibm.com/partnerworld/partnertools/assur30i.nsf/Web/Guides
120
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.1.4 Other Designated Product List (DPL) Equipment
7. SAPR Guides and product checklists for other DPL products that will attach to
the z114 processor can be found at the following IBM internal web site:
• w3.ibm.com/support/assure
For example:
- zEnterprise Ensemble Pre-sale TDA Checklist (even without a zBX), see
SA10-018.
- zEnterprise BladeExtension, see SA10-006.
- Server Time Protocol, see SA06-012.
5.1.5 Performance
8. It is extremely important that the appropriate capacity planning tools have
been used to determine the class of z114 machine required to process the
customer’s workload. Rough estimates using MIPs or equivalent values
should not be acceptable. Please refer to the CPSTOOLs suite of tools for
determining the proper sizing tools to use. The following tool options are
considered minimal requirements for determining the capacity of the proposed
z114:
Note: A zPCR study is the minimum requirement
• zPCR study using LPAR configuration capacity planning function
• A zCP3000 study should be used when
• SCP is z/OS, z/VM, and/or Linux (under z/VM)
• Customer can provide RMF data or z/VM monitor data
• Growth over a period of time
• Focus is on capacity and potentially storage, I/O and response time
• FICON study
• zTPM (a workload simulator) should used when
• SCP is z/OS
• Customer can provide RMF/CMF data
• Focus is on a primary partition, whose activity is time simulated against the
remaining processor partition workloads
Note: zPCR is required to obtain processor capacity relationships and LPAR
cost.
9. Account team should understand what metrics the customer plans to use to
evaluate the performance of the z114 to ensure they are compatible with the
sizing tools used and that meaningful data will be obtained.
10.SMF 113s can optionally be used in z114 capacity planning: Capacity Sizing
process is the same as today with zPCR (based on DASD I/Os per MSU
consumed). Optionally use a new Relative Nest Intensity “Hint”. SMF 113 data
may prove useful in support of an installation of z114.See CPU MF Techdocs
TC000041 and TC000066 at
http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs
Chapter 5. Must-Read Information
121
Copyright 2011 IBM Corporation. All rights reserved.
- or http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TC000041
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TC000066
11.No additional information.
5.1.6 Acquisition and Contractual Considerations
12.No additional clarification
13.There are numerous actions that may result in additional charges after the
z114 is initially installed. For example, activating processors that were initially
designated as unassigned. The account team should review the configuration
for any of these potential charges and ensure the customer is aware of any
such charges that may be generated over the life of the machine.
14.Software licensing the IBM z114 requires 100 Processor Value Units (PVUs)
for each Integrated Facility for Linux (IFL) engine or CP engine (one processor
core). This pricing metric is used to license middleware running on Linux for
System z and distributed platforms. With significantly higher processor
performance over predecessor IBM System z offerings, along with superior
workload scheduling and processor utilization capabilities, this licensing
requirement is designed to provide enhanced software value over other
processor technologies it is likely to replace.
IBM continues the practice of licensing to the processor core. This practice
provides the licensing granularity customers require, while offering the
flexibility to configure their systems to best support their business objectives.
Processors are defined as cores (one IFL or CP engine) on z114, so for PVU
licensing the number of processors identified on the hardware is the same
number of processors to be used for software licensing. For instance, if a z114
CPC has 5 processors, the number of PVUs required would be 5 processor
cores times 100 PVUs (5 x 100 = 500 PVUs).
Note: POWER6 is also rated at 120 PVUs per core. POWER7 is generously
rated at no more than 120 PVU's per core on the higher level machines, and
100 PVU's on the lower 750/755 series.
z/VM is licensed with Engine Based Value Units which are unchanged with this
announcement.
External web site with Processor Value Unit table:
• http://www-306.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_
customers.html
Internal web site with additional information, e.g. customer presentation and a
Q&A package, for z10 only:
• http://w3-103.ibm.com/software/xl/portal/viewcontent?type=doc&srcID=XT&do
cID=B887620M95345Y79
Refer to IBM United States Announcement 208-048, dated March 4, 2008
15.Maintenance requires a 30 day written notice since this type of change is a
swap out (change of serial number), not a physical upgrade.
16.No additional information.
122
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
17.The licensee is not authorized to use an Elliptical Curve Cryptography
feature's machine code as a commercial certificate authority in the issuance of
digitally signed electronic certificates on a public key for the purpose of
identifying the holder for use as credentials in a digital transaction.
See
http://www-947.ibm.com/systems/support/machine_warranties/machine_code
_cryptadd.html
5.1.7 Capacity on Demand
18.No additional information.
19.One 24 hour test is allowed for OOCoD, incurring no charges.
Also, there were administrative tests available on the z9. The administrative
tests are not allowed on the z10, but this is again possible on the z114.
No charge administrative tests enabled customers to order 'zero' quantity
features and go through the entire order, download and activate steps. This
provides a method for operator training and the test can be performed multiple
times.
APIs can also be used to with administrative tests.
See Capacity on Demand User's Guide SC28-2605 for complete details.
5.1.8 Education and Training
20.The following web site should be reviewed for any education that may be
required to support the z114 processor:
http://www.ibm.com/systems/services/labservices
http://www.ibm.com/services/learning
Chapter 5. Must-Read Information
123
Copyright 2011 IBM Corporation. All rights reserved.
There are also several online courses offered at ResourceLink that will be
valuable in operating and installing the z114 processor. Refer to the SAPR
guide for further information.
5.1.9 Future Planning
21.All statements regarding IBM's plans, directions, and intent are subject to
change or withdrawal without notice. Any reliance on these statements of
general direction is at the relying party's sole risk.
• HMC/SE Switch
The IBM zEnterprise 196 and zEnterprise 114 will be the last servers to
offer ordering of the external Ethernet switch (FC0070).
• Removal of modem support
Beginning with the next System z server after the IBM zEnterprise 196 and
114, the new Hardware Management Console (HMC) is intended to no
longer provide modem support. As a result, modems will not be allowed for
use with the Remote Support Facility (RSF), and one of the External Time
Source (ETS) options of Server Time Protocol (STP). Only broadband
connections will be allowed. The new HMC driver is planned to provide
enhanced security by providing Network Time Protocol (NTP)
authentication support, when a NTP server is accessed to get accurate
time for the STP Coordinated Timing Network (CTN).
• Note that the above changes will affect new orders of z196 and z114, as
well as upgrades of HMC driver levels to this new version. Enterprises
using modems for RSF or STP should plan on migrating to broadband
connections. The currently available NTP server option for ETS, as well
as internet time services available using broadband connections, can be
used to provide the same degree of accuracy as dial-up time services.
• HMC z/VM Tower Systems Management Support IBM does not plan to enhance the HMC z/VM Tower systems management
support, initially provided with System z9 servers and further enhanced
with System z10 servers. In addition, z/VM 6.2 will be the last release
supported by the HMC z/VM Tower systems management support. Virtual
Server and virtual resource management for z/VM V6 continues to be
supported by the zEnterprise Unified Resource Manager.
• GDPS/Global Mirror clusters managed by SA AppMan
fsGDPS plans on enhancing its Distributed Cluster Management (DCM)
support for IBM Tivoli System Automation Application Manager (SA
AppMan) by extending it to the GDPS/Global Mirror (GM) offering in
addition to the GDPS/PPRC offering available today. This will allow for
coordinated disaster recovery across System z and distributed servers at
unlimited distances. With GDPS/GM managing replication of data for both
System z and for the distributed servers under SA AppMan control, this
solution can also provide cross-platform data consistency across the
System z and distributed servers.
• GDPS DCM support for stand alone distributed servers
GDPS plans on enhancing its DCM support for SA AppMan by extending it
to stand alone distributed servers, building upon the support for clustered
distributed servers available today. This capability can benefit distributed
servers running on a zBX or on other distributed platforms, which are not
members of a clustered network, and will allow continuous availability and
124
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
disaster recovery across heterogeneous platforms. Support is planned for
GDPS/PPRC and GDPS/GM.
• GRS ring to support FICON channels
Many customers are migrating from ESCON channels to FICON channels
and in Hardware Announcement 111-136, "The IBM zEnterprise 114 Freedom by Design," dated July 12, 2011, IBM announced that the
zEnterprise 196 (z196) and zEnterprise 114 (z114) generation of servers is
intended to be the last to support ESCON channels. Although IBM
recommends that you use GRS Star, and for GRS Ring environments
recommends XCF communications for CTC management, IBM intends to
extend z/OS Global Resource Serialization (GRS) Ring function to natively
support FICON channel-to-channel (CTC) connections in the z/OS release
following z/OS V1.13, and to make this support available on z/OS V1.11,
V1.12, and V1.13.
• HiperSockets integration with the IEDN
Within a zEnterprise environment, it is planned for HiperSockets to be
integrated with the intraensemble data network (IEDN), extending the
reach of the HiperSockets network outside of the central processor
complex (CPC) to the entire ensemble, appearing as a single Layer 2
network. HiperSockets integration with the IEDN is planned to be
supported in z/OS V1.13 and z/VM in a future deliverable.
• HiperSockets Completion Queue
IBM plans to support transferring HiperSockets messages asynchronously,
in addition to the current synchronous manner on z196 and z114. This
could be especially helpful in burst situations. The Completion Queue
function is designed to allow HiperSockets to transfer data synchronously if
possible and asynchronously if necessary, thus combining ultra-low latency
with more tolerance for traffic peaks. HiperSockets Completion Queue is
planned to be supported in the z/VM and z/VSE environments.
• Support for High Performance FICON (zHPF) Guest Exploitation
IBM intends to provide support for guest virtual machines utilizing the High
Performance FICON for System z (zHPF) I/O protocol. z/VM will support
guest operating systems that issue single track as well as multiple track
zHPF I/O.
• The IBM zEnterprise 196 and the IBM zEnterprise 114 are the last System
z servers to support ESCON channels. IBM plans not to offer ESCON
channels as an orderable feature on System z servers that follow the z196
(machine type 2817) and z114 (machine type 2818). In addition, ESCON
channels cannot be carried forward on an upgrade to such follow-on
servers. This plan applies to channel path identifier (CHPID) types CNC,
CTC, CVC, and CBY and to features 2323 and 2324.
System z customers should continue to eliminate ESCON channels from
the mainframe wherever possible. Alternate solutions are available for
connectivity to ESCON devices. IBM Global Technology Services offers an
ESCON to FICON Migration solution, Offering ID #6948-97D, to help
facilitate migration from ESCON to FICON. This offering is designed to help
customers to simplify and manage a single physical and operational
environment - FICON channels on the mainframe with continued
connectivity to ESCON devices.
Chapter 5. Must-Read Information
125
Copyright 2011 IBM Corporation. All rights reserved.
This is a restatement of general direction already published. Refer to
Hardware Announcement 111-012, dated February, 15, 2011.
• The IBM z196 CPC will be the last high-end server to offer ordering of
ISC-3. Enterprises should begin migrating from ISC-3 features (#0217,
#0218, #0219), to
12x InfiniBand (#0171 - HCA3-O fanout) or
1x InfiniBand (#0170 - HCA3-O LR fanout) or
12x InfiniBand (#0163 - HCA2-O fanout) or
1x InfiniBand (#0168 - HCA2-O LR fanout)
coupling links.
Note: Effective December 31, 2011 IBM System z will withdraw from
marketing the following feature on IBM zEnterprise 196: HCA2-O LR fanout
for 1x IFB (#0168)
• The IBM zEnterprise 196 and the zEnterprise 114 are the last System z
servers to support the Power Sequence Controller (PSC) feature. IBM
intends to not offer support for the PSC (feature 6501) on future System z
servers after the z196 (machine type 2817) and z114 (machine type 2818).
PSC features cannot be ordered and cannot be carried forward on an
upgrade to such a follow-on server. This is a revision to the PSC statement
of general direction published July 22, 2010. Refer to, Hardware
Announcement 110-170 (RFA53067), The IBM zEnterprise System
A new dimension in computing. At that time we indicated the PSC feature
could not be ordered on future servers. We are further clarifying that PSC
features will also not be supported as carry forward on an upgrade.
• The IBM z196 CPC will be the last high-end server to support FICON
Express4 channels: Enterprises should begin migrating from FICON
Express4 channel features (#3321, #3322, #3324) to FICON Express8S or
FICON Express8 channels.
• In previous statements of direction IBM stated that the IBM zEnterprise 196
and IBM zEnterprise 114 would be the last servers to support FICON
Express4 channels.
IBM now plans to support carry forward of the FICON Express4 features
(FC3321, FC3322) into the server after the zEnterprise System. Refer to
Hardware Announcements 110-170, dated July 22, 2010 and to 111-136,
dated July 12, 2011.
• FC3321 FICON Express4 10KM LX
• FC3322 FICON Express4 SX
• The IBM z196 CPC will be the last high-end server to support
OSA-Express2 features: Enterprises should begin migrating from
OSA-Express2 features (#3364, #3365, #3366) to OSA-Express4S or
OSA-Express3 features where possible.
• The z10 EC and z10 BC will be withdrawn from marketing effective June
30, 2012
•
22.A worldwide port name (WWPN) prediction tool is available to assist with
preplanning a Storage Area Network (SAN) environment prior to the
126
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
installation of a z114.
This standalone tool is designed to allow customers to set up a SAN in
advance, so that it can be up and running much faster once the server is
installed. The tool assigns WWPNs to each virtual Fibre Channel Protocol
(FCP) channel/port using the same WWPN assignment algorithms a system
uses when assigning WWPNs for channels utilizing N_Port Identifier
Virtualization (NPIV). The tool needs to know the FCP-specific I/O device
definitions in the form of a .csv file.
This file can either be created manually, or exported from Hardware
Configuration Definition/Hardware Configuration Manager (HCD/HCM). The
tool will then create the WWPN assignments, which are required to set up your
SAN. The tool will also create a binary configuration file that can be imported
later by your system.
The WWPN prediction tool can be downloaded from Resource Link and is
applicable to all FICON channels defined as CHPID type FCP (for
communication with SCSI devices).
• http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS3659
• http://www.ibm.com/servers/resourcelink/
23.zBX MES while concurrent is not completely transparent, this should be
mentioned in any zBX Install Planning meetings. May need to update the z114
MCL level as a Pre-Req to the MES. Clients with tight change management
controls take great care in planning MCL updates, especially if Crypto, OSA
and/or CFCC changes are involved. zBX Installation requires the SE be Held
in 'Reserve' for a few hours. During this reserve time the SE is not avail for
Config changes, LPAR activations, OOCOD change, etc..
.
Chapter 5. Must-Read Information
127
Copyright 2011 IBM Corporation. All rights reserved.
5.2 MR-Hardware Configuration
5.2.1 General
1. The PCHID report will be needed by the customer to define the channel
configuration for input into HCD/HCM. If the customer plans to use the CHPID
mapping tool, the correct CCN number is required or someone from the
account team can provide the CFREPORT file from econfig which is an option
with the mapping tool. It is strongly recommended that the CCN file be used
but the CFREPORT file could be useful for initial planning and evaluation.
Note: The ResourceLink CHPID mapping tool can be used for a z114 initial install or
an upgrade from a previous processor. The CHPID mapping tool supports MES
upgrades or changes to a z114 processor.
2. If the DWDM does not support peer mode link speeds, an alternative is to
order RPQ 8P2197. Note: this RPQ generates priced hardware features.
3. The FICON Channel has the ability to auto-negotiate (2, 4 or 8 gbps) with the
attached devices. It is possible that not all DWDM ports will support
auto-negotiate with success (channel errors). For those DWDM ports that do
not support auto-negotiate, ensure that the DWDM port is set (hard-coded) to
the same data rate on both sides or will auto negotiate on both sides, for both
the working and protect paths of the network.
4. Ensure that only approved WDM devices will be used in the STP environment.
Please ensure that the vendor qualification document is inspected carefully by
a WDM technical expert. The document is written to be very specific (unit
number, version number, applicable features that are qualified for STP). Time
Division Multiplexing (TDM) may (or may not) be qualified, depending on the
vendor.
The list of GDPS and STP qualified WDMs on ResourceLink should be
checked frequently. Once in ResourceLink, click on the library link, then look
under the Hardware Products For Servers heading. You must open the PDF
file of the relevant vendor to determine whether or not STP is supported. It is
imperative that the details within each vendor qualification letter is completely
understood.
IBM cannot support the use of unqualified WDM equipment in a customer
installation. Note that each and every coupling link going through WDM must
be on a vendor product that supports STP. That is, you may NOT use a
mixture of STP qualified and unqualified vendor WDM products.
5. Hardware support of crypto functions changed significantly between the CCF
based machines (z800/z900 and earlier) and the CPACF based machines
(z890/z990 and later).
Because the crypto architecture has changed, in-house applications and some
product code may not be able to run without the optional secure crypto
hardware. For example, secure key APIs have moved from the CCF hardware
to the optional Crypto Express3 feature, so a Crypto Express3 is required for
secure key support.
The CP Assist for Cryptographic Function (CPACF) is standard on every PU.
128
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
However, FC3863 must be ordered for enablement. FC3863 enables CP
Assist for Cryptographic functions and is a prerequisite for all crypto functions
on the z114. On the CPACF machines, the Crypto Express3 (FC0864) is an
option and must be specified via feature codes on the order.
5.2.2 Capacity on Demand
6. If a prior machine is being discontinued, ensure that temporary records are
removed from the machine prior to its final power off. If not, there is a chance
that billing for an On/Off CoD temporary record will continue to be billed even
when the machine is no longer in use. Recommended procedures:
a) Deactivate any currently active On/Off CoD upgrades
b) Using the HMC/SE interfaces, delete any staged On/Off CoD orders from
the support element
c) Rebuild VPD and export to media
d) Upload the VPD to Resource Link using the upload VPD link on the
Resource Link machine profile
e) Send a note to reslink@us.ibm.com saying that this machine is no longer
active. Please make sure the note includes the machine type and serial
number.
f) Power Off
7. No additional clarification
8. On/Off Capacity on Demand Tokens (Pre-paid On/Off CoD) is also sometimes
known as Capacity Provisioning Phase 2.
Before Capacity Provisioning Phase 2, customers were charged for temporary
hardware after the On/Off CoD record has been activated. With Phase 2,
customers can now pre-pay for temporary capacity.
Capacity Provisioning Phase 2 is designed to provide the customer the means to
limit their financial liability by automatically deactivating resources through the
use of capacity tokens. Customers are assigned tokens through the order
process. On/Off CoD Tokens can be purchased and “banked” by the customer.
The CEC will manage the use and consumption of tokens.
Tokens can be purchased for any speciality engine (per day of use) or for CP
capacity (MSU’s per day of use). Each day of usage (times the amount of
capacity activated) will decrement the token pool available for future On/Off
Temporary Capacity on Demand activations of the specific temporary record.
On/Off CoD and related tokens can only be ordered via ResourceLink by the
customer.
There is no scheduled expiration date for pre-paid tokens (true of CP MSU’s
also). Tokens decrement as used, but they can be replenished to add capacity
and/or days as needed. Auto deactivation will be attempted after all tokens have
been used.
9. Refer to the SAPR Guide Appendix C for further information.
10.This z114 capability allows for the automatic renewal of installed records - this
function is intended for use with On/Off CoD, to automatically update the
expiration date for "customers in good standing". Customers in good standing
Chapter 5. Must-Read Information
129
Copyright 2011 IBM Corporation. All rights reserved.
consistently transmit VPD and regularly pay of bills. This is managed at the
Resource Link level.
The request is to auto-replenish the expiration date of installed On/Off CoD
records, there is no intent to replenish tokens automatically, only the
expiration date.
Staged records are not subject to automatic replenishment. Participation in
this program is a customer option. This is not available for records on RPQ
machines.
5.2.3 Service
11.FC3759 and FC9969 should only be ordered for an initial order or in some
cases, an upgrade to a z114. This feature can be added later as an MES if the
machine will be moved to a different site where this feature may not be
available. The recommendation is to have no more than one each of these at
a single site.
• (FC3759) - Universal Lift Tool and Service Ladder
This feature delivers the Universal Lift Tool and Service Ladder for the 24"
wide IBM servers. FC3759 is a feature that is available on multiple server
types (z114, z196, z10, Power 595 and Power 575). Failure to have at least
one FC3759 available in a location may result in delayed or prolonged
maintenance times.
• Attributes provided: Universal Lift Tool and Service Ladder
• Attributes required: 24-inch wide IBM Server
130
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
What you need to note in the above is that there are some tools that will be
used for the z114, z196, z10, and the P-Series products listed. The
recommendation will continue to be that you only need one FC3759 per
site. This applies for z114, z196, z10's and Power 595 and Power 575
systems. If you have any of those, you only need one FC3759.
There may be instances where having more than one FC3759 is needed.
Examples are:
• When a customer has multiple machines and feels that they need to
have a second lift tool as back-up in case the first lift tool breaks.
• When a customer requests that multiples exist at their sites.
• If a customer is going to move their processors from one location to
another. In all cases the lift tool is needed for installations and for some
repair actions.
• If a customer is going to sell their processor and has a requirement to
ship a lift tool with the machine. Again, a lift tool is needed for
installations and for some repair actions.
• (FC9969) - Site Tool Kit
FC9969 will have some unique tools for the z114 and z10 BC. One of the
components is a Drawer Cradle. These processor books are shipped in a
horizontal position and they are installed in the horizontal position. The
other component in FC9969 is a bridge adapter. When the lift tool is
attached to the frame, there is a gap between the tool and where the books
reside...thus, a "bridge" is required.
So, if you have a z114, z196, z10 EC, Power 595, and Power 575 installed,
you only need one FC3759 per site. If you are installing the first z114 or
z10 BC at a site that already has a FC3759 installed because you also
have a Power 595 or Power 575, then you only need to order FC9969. If
this is the first of any of those, you need to order FC3759 and order
FC9968 if you are ordering a z114.
Any other tools that are specific to the z114 are already shipped
within the z114 ship group.
5.2.4 Hardware Management Console
12.The HMC must be at Driver 93 or higher, with a minimum of 5 GB of HMC
memory. Carried forward HMCs (FC0084 or FC0090) will require these
changes/additions. If upgraded from a z9 or a z10, the additional components
will be provided with the upgrade.
If you need to upgrade an HMC 0084 or 0090, shipped and installed on an
older machine (e.g. z10), a no charge EC is needed. The CE orders the EC on
the CPC that "owns" the HMC as a feature.
The EC ships LIC and memory (for HMCs that need it) for EVERY HMC
feature 0084 or 0090 on that CPC. The EC to have the SSR get is EC D77155
(ECA 285).
NOTE: This EC includes memory hardware so it is very important to upgrade
using the EC. Just putting on the Driver LIC won't work if the HMC needs
memory.
Chapter 5. Must-Read Information
131
Copyright 2011 IBM Corporation. All rights reserved.
Two FC0090 or FC0091 HMCs are the minimum requirements for use when
using Unified Resource Manager. If Unified Resource Manager is to be used,
a minimum of two HMCs are required.
The z114 HMC Driver 93G is not supported on any HMC that does not have
dual ethernet adapters. FC0079 and FC0081 are not supported on the z114.
Once the HMC is a Driver 93G, it can not control servers older than a 9672 G5.
The older machines must be at their latest Driver levels.
13.Important HMC Requirements, when using Unified Resource Manager are
listed here.
The Unified Resource Manager HMCs must be equal to or higher in Driver LIC
level than every CPC in the Ensemble. CPC’s at Driver 86 can participate in
the Ensemble with CPC’s at Driver 93, for example, provided the Unified
Resource Manager HMCs are both (PRI/ALT) at Driver 93.
Before you begin, be aware of the following requirements and error/warning
messages:
The machine type and model number of the primary HMC and alternate HMC
must be identical. Both must be either Feature Code 0090 or Feature Code
0091. Verify this information by viewing the sticker on top of the HMC
hardware tower
HMC FC 0084 is a 4362PAT machine type
HMC FC 0090 is a 4367PAM/PAA machine type
HMC FC 0091 is a 7327PAA machine type
The AROM control level (LIC control level) of the primary HMC and alternate
HMC must be identical. Verify this information using the View Console
Information task.
The ethernet configurations on the primary HMC and the alternate HMC must
be the same. Both HMCs must have the same number of adapters, and each
port must be attached to the same subnet. Verify this information on LAN
Adapter page on the Customize Network Settings task.
The modem configuration must be the same on the primary HMC and the
alternate HMC to ensure the call-home function works after a switch over
occurs. Verify this information using the Customize Modem Settings task.
If you attempt to enable an HMC to be an unassigned alternate HMC and any
of the following conditions are in effect, you will receive an error message:
- The HMC has CPCs assigned to it (verify using the System Information task).
- The HMC is set up to be an NTP server (verify on the Configure NTP
Settings page using the Customize Console Data and Time task).
- The HMC is set up to be a call home server (verify using the Customize
Outbound Connectivity task).
- The HMC is enabled for data replication (verify using Configure Data
Replication task).
132
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
- The HMC is configured to use DHCP (verify using the Customize Network
Settings task).
If you attempt to enable an HMC to be an unassigned alternate HMC and any
of the following conditions are in effect, you will receive warning message, but
the function will complete:
- The HMC is set up to be an FTP server (verify using the Enable Electronic
Service Agent task).
- API support is enabled on the HMC (verify using Customize API Settings
task). When the primary HMC and alternate HMC are defined, the ability to
send API requests is not available.
14.The Customizable Data Replication service provides the ability to configure a
set of Hardware Management Consoles to automatically replicate any
changes to certain types of data so that the configured set of Hardware
Management Consoles automatically keep this data synchronized without
manual intervention.
The following types of data can be configured:
•
•
•
•
•
•
•
•
•
•
Acceptable Status Settings
Associated Activation Profiles
Customer Information Data
Group Data
Modem Configuration Data
Monitor System Events Data
Object Locking Data
Outbound Connectivity Data
Remote Service Data
User Profile Data
See the appropriate Appendix in your Hardware Management Console User’s
Guide for much more detail.
5.2.5 Devices and Controllers
15.There is no longer an up to date list of devices supported for attachment to
System z machines. IBM devices previously attached to IBM System z servers
are supported for attachment to the z114 channels, unless otherwise noted.
The subject I/O devices must meet ESCON or FICON/FCP architecture
requirements to be supported. I/O devices that meet OEMI architecture
requirements are supported only using an external converter. Prerequisite
Engineering Change Levels may be required. For further detail, contact IBM
service personnel. While the z114 supports devices as described above, IBM
does not commit to provide support or service for an IBM device that has
reached its End of Service effective date as announced by IBM.
For a z114 machine, it is NOT true that a device that attached to an earlier
generation machine will work on a z114 without change. There may be
devices that require microcode updates (both IBM and OEM) in order to attach
to a z114. Refer to the Driver Exception Letter on ResourceLink, contact the
Chapter 5. Must-Read Information
133
Copyright 2011 IBM Corporation. All rights reserved.
appropriate IBM device support team for any required microcode levels on the
devices, and contact any OEM supplier for verification.
For equipment (both IBM and OEM) that supports MIDAW or zHPF may
require minimum levels of microcode or feature codes. The supplier of the
equipment must be contacted to determine any requirements.
Note: The MIDAW function was first available on the z9 processor and applies
to both ESCON and FICON channels.
The majority of the announcement materials for MIDAWs focuses primarily on
FICON architecture but ESCON also supports MIDAWs. MIDAWs does not
affect ESCON performance at short distances. However, MIDAWs may
improve the performance of EF data sets with ESCON at extended distances,
but since ESCON doesn't support multiplexing, non-EF data sets will not
improve.
Other relevant information:
ResourceLink Library - Qualified Switches and Directors for z https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/switchesAndDir
ectorsQualifiedForIbmSystemZRFiconRAndFcpChannels?OpenDocument
ResourceLink Library - Qualified DWDMs:
https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/systemzQualifie
dWdmProductsForGdpsSolutions?OpenDocument&pathID=
ResourceLink Fixes - Exception Letters - z114 - Customer Exception
Letter - (Additional information about IBM and Brocade directors with
FICON Express8S or FICON Express8)
https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/exceptionLetter
s?OpenDocument
FICON Open Exchanges (Max=32) with STK devices:
FICON channels have the capacity to support more than 64 open exchanges.
The 64 limit is how many FICON will initiate. Device reconnects can cause the
actual number of exchanges open at the channel to be much higher at any
single point in time.
STK devices can only support up to 32 open exchanges.
In System z9, the function existed for customers to change the open exchange
limit for FICON channels from 64 open exchanges to 32 open exchanges.
In System z10 and z114, access to the function was moved to a Service only
capability and is accessed with the machine in PEMODE. If a customer has an
STK device and requires open exchanges to be set to 32, IBM System z
supports the change as long as the change is only made to the FICON
channels connected to the STK control units.
Contact service personnel for assistance. IBM support must be contacted
134
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
before changing the open exchange limit from 64 to 32 open exchanges on
any FICON channels that are not connected to STK control units.
16.D93G Exception Letter
https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/exceptionLetter
s?OpenDocument.
17.A 3590-A60 with 1 GB FICON adapters is not supported when directly
attaching to a z114, z196, z9 or z10 processor (i.e. no FICON Director). If a
customer would like to attach a 3590-A60 with 1 GB adapters, they must order
an MES for the 3590 to change the adapters to the 2 GB versions.
Channel problems can occur when there is an attempt to direct connect (i.e.
no FICON director) a 3590-A60 with 1 GB FICON adapter cards to a FICON
Express4 or FICON Express8. The only fix available is to have the 1GB
adapter in the 3590 replaced with a 2 GB adapter. If you have this attachment
configuration, then it is critical that you have the SSR contact Tucson Product
Field Engineering (PFE) to discuss the situation and arrange for corrective
actions. This is not an issue with the FICON Express card but rather with the
3590.
5.2.6 Consoles
18.This can take the form of Sysplex console support or use of IBM 2074 Console
Support Controllers, IBM 3174 Cluster Controller, or the OSA-ICC.
Note: As a general rule, the Hardware Management Console console integration
function should NOT be used unless the limitations are understood and agreed
to.
19.By default, if SYNCHDEST is not explicitly specified, synchronous WTORs will
be routed only to the System Console (the Hardware Management Console, or
HMC), and will not be routed to any active z/OS consoles. Given this default
behavior, such messages may or may not be obvious or even visible to the
z/OS operations staff.
Refer to:
http://w3.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10761
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10761
http://partners.boulder.ibm.com/src/atsmastr.nsf/WebIndex/FLASH10761
5.2.7 Coupling Links
20.InfiniBand Coupling Links provide the opportunity to consolidate CF Links, but
ensure that the selections made will perform as expected. PSIFB coupling
links are a good choice for ISC-3 consolidation, within distance limits. The
level of consolidation possible depends upon workload. A zCP3000 CF study
is highly recommended.
It may be possible to consolidate up to 8 ISC-3 channels on 1 PSIFB coupling
link.
If planning a 1:1 replacement of ICB-4 with PSIFB, then use zCP3000 to
validate changes to coupling efficiency are acceptable. See the "host effect"
matrix in the Coupling Config Options whitepaper.
Chapter 5. Must-Read Information
135
Copyright 2011 IBM Corporation. All rights reserved.
For guidelines, see www.ibm.com/systems/z/advantages/pso/whitepaper.html.
Additionally, the “Getting Started with InfiniBand on System z10 and System
z9” Redbook (SG24-7539) available on the Redbooks™ Web site provides a
good overview of the InfiniBand capabilities on System z10 and System z9:
• http://www.redbooks.ibm.com/
Note: The z114 is the last server to offer ordering of new ISC-3 coupling links.
21.On the zEnterprise servers, the HCD default is 32 subchannels for any CIB
channel definitions for z196 (GA2) and/or z114 servers (whether HCA2 or
HCA3). The default in the past (and the only choice in the past) was 7
subchannels.
For 1x (LR) InfiniBand coupling links, 32 subchannels per CHPID is
recommended. This can improve throughput in 1x InfiniBand coupling links.
The additional subchannels allow more requests to be in-flight simultaneously.
Where 1x is not at an extended distance, one can also define 7 subchannels,
but IBM recommends providing those links with 32 subchannels.
HCA3-O LR 1x IFB, FC0170
HCA2-O LR 1x IB-DDR, FC0168
For 12x InfiniBand coupling links, 7 subchannels per CHPID are
recommended. The HCD user should take specific action to make this
change to their CIB definition. 12x InfiniBand coupling links can only take
advantage of 7 subchannels.
HCA3-O 12x IFB, FC0171
HCA2-O 12x IB-DDR, FC0163
HCD cannot differentiate between Short range and Long range adapters. The
systems programmer must validate correct subchannel use for CIB. HCD help
panel guidance available.
This support is available in z/OS R13 and rolled back to z/OS R10 and higher
via APAR OA32576. HCD support levels prior to GA2 will offer 7 subchannels.
For further information, refer to
http://public.dhe.ibm.com/common/ssi/ecm/en/zsw01971usen/ZSW01971USE
N.PDF. See pages 15-18.
22.IFB3 protocol is designed to improve InfiniBand service time by up to 40
percent (z196 or z114 to z196 or z114). To enable IFB3 protocol, you must
have a connection from HCA3-O 12x (FC0171) to HCA3-O 12x (FC0171).
Also, you must not define more than four CHPIDs on the two IFB ports making
the remote connection on another HCA3-O 12x. If more than four CHPIDS are
defined per port, the coupling links will run at normal 12x IFB service times.
23.If ordering HCA2-O or HCA3-O InfiniBand coupling links, ensure you have
ordered enough ports to provide you with physical card redundancy. For
example, if order FC0170 (HCA3-O LR which is a 4-port card), order 8 ports to
get two cards for redundancy.
136
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
24.93G Exception Letter
https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/exceptionLetter
s?OpenDocument.
5.2.8 Server Time Protocol
25.If using a coupling link, the customer must have a plan to implement STP in
the environment. Either a Mixed CTN or an STP-only CTN is adequate.
This can take a considerable amount of time for planning and education if STP
is new to your environment.
The z114 can exist in a Mixed CTN if necessary. There should be at least two
other servers connected to the 9037 that have the STP feature installed and
configured. The z114 should be connected via redundant coupling links to two
of these machines (at a minimum). This will permit the z114 to have two
machines to act as sources of time.
Sysplex Tim er
ETR Network ID =31
ET R
N etw o rk
C oordinated
T im ing
Netw ork
ET R T im ing M ode
ISC -3
z9 EC, Stratum 1
CTN ID = HM CTEST - 31
ET R T im ing M ode
z9 BC, not STP enabled
ETR Network ID = 31
z10 EC , Stratum 1
CTN ID = HM CTEST - 31
ST P T im ing M ode
ISC-3
2817, Stratum 2
CTN ID = HM CTEST - 31
26.See STP SAPR Guide, SA06-012 and schedule a TDA.
27.See
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101833
28.Note that when a CTN with roles assigned (PTS/CTS, BTS, Arbiter), if the BTS
and Arbiter are gone (due to maintenance or an machine upgrade or customer
action), the PTS/CTS will go to local timing mode (Stratum 0), and the entire
CTN will go down. This can happen if roles on machines are not moved to
other machines in the CTN or configured in the STP panels as “not
configured”.
Important: After a machine upgrade (z10 to z114 for example), the node
descriptor of the machine changes, thus STP does not recognize the role
being on the upgraded machine. So, always remove the STP role prior to a
machine upgrade.
29.No further clarification.
Chapter 5. Must-Read Information
137
Copyright 2011 IBM Corporation. All rights reserved.
30.If you have implemented the enhancement that allows you to restore STP
configuration information across Power on Resets in a two server CTN (refer
to http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD105103),
you must take a special action prior to an upgrade.
The upgraded server will not be able to join its partner server in the previous
CTN if the upgrade changes the machine type (2098 to 2818). The customer
will first need to:
• Remove the check mark that specifies, "Only allow the server(s) specified
above to be in the CTN in a two server CTN
• After the upgrade, assign the CTN roles on both servers, as desired
• Check the check box again that specifies, "Only allow the server(s) specified
above to be in the CTN in a two server CTN”, as desired.
31.No further clarification.
5.2.9 Channel Configuration
32.Review in detail the output from the configurator to determine channel types
that may be deleted as part of an upgrade.
33.The FICON Express 4, FICON Express8 or FICON Express8S features do not
support the use of FCV CHPIDs. See the PRIZM product at
http://www.opticatech.com/.
34.Refer to RETAIN TIP H176013 for further information.
35.Be aware that when a z114 and FC0025 Unified Resource Manager are
ordered without a zBX, eConfig does not force you to order two
OSA-Express4S or OSA-Express3 10 GbE features, however they are
required if LPAR to LPAR communication is required in this circumstance.
Usage notes:
A) When using two OSX devices in a high availability environment, meaning
same IP subnet and vlan, the OSX device must be connected with a direct
connect cable. This will simulate a LAN existing between the OSX devices,
allowing Layer 2 routing to work.
B) Otherwise, the OSX devices should be configured with LC Duplex wrap
plugs and on separate IP subnets and vlans. This will allow direct connectivity
to other images sharing the OSX device.
Best Practices:
When implementing a zEnterprise System Ensemble Node without an
attached zBX, interconnect all OSX ports via Direct-Connect cables and not
wrap cables as has been recommended in previous zEnterprise
documentation. For technical reasons, a zero-zBX implementation should
have no more than two OSX IEDN ports on any LPAR.
1. If the LPAR is a native z/OS LPAR with a z/OS Virtual Server, ensure that
the LPAR has been configured with connections into each OSX port. The
connections should represent connection pairs, where each pair has been
defined with the same IP Subnet and VLAN ID for the IEDN.
2. If the LPAR is a z/VM LPAR, any guest with native attachment to the OSX
138
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
ports must also configure interfaces with the same VLAN ID and IP Subnet to
each of the OSX ports. (This is the same as what was described in Bullet #1
above.)
3. If z/VM is to support guests on a VSwitch, then this VSwitch must be
attached to each of the OSX ports, again using the same VLAN ID and IP
Subnet.
2458-002 IED N, no zB X
V Sa
VSb
C HPID #1
O
S
M
CH PID# 2
O S X 1 0G b E
L R /SR
MA T CH ED
C HPID
PA IR
(M INIMU M)
z19 6 EC
C PC 1
IE D N (O SX )
V L AN ID
‘A ’ & ‘B’
C us tome r sup pli ed di rec tly c onne c ted LC D U PL EX c a ble (IE D N ) b etw ee n the 2 OS X C H P ID pai r.
U se ‘ ON E ’ OS X C H P ID p er c a rd, loc a ted on d iffer ent phy si ca l H /W ca rds / ports .
5.2.10 Crypto
36.With the change to the CPACF architecture (from the CCF based architecture)
some functions which are not widely used have been dropped on the CPACF
machines.
See 'Migrating from the IBM eServer zSeries 800 and the IBM eServer zSeries
900 in the ICSF Systems Programmer's Guide.
Support for the following crypto functions were dropped on the CPACF based
machines:
a. There is no KMMK (key management master key).
b. The Commercial Data Masking Facility (CDMF) is no longer supported. The
CDMF keyword on KGUP control statements and panels is no longer
supported.
Chapter 5. Must-Read Information
139
Copyright 2011 IBM Corporation. All rights reserved.
c. The Public Key Algorithm Digital Signature Standard is not supported. This
affects callable services CSNDPKG, CSNDPKI, CSNDDSG, and
CSNDDSV.
d. The PBVC keyword is not supported on a PCI X Cryptographic
Coprocessor. This affects callable services Clear PIN Generate Alternate
(CSNBCPE), Clear PIN Encrypt (CSNBCPE), PIN Translate (CSNBPTR)
and PIN Verify (CSNBPVR).
e. RSA keys of modulus less than 512 bits are not supported on a 2098
Cryptographic Coprocessor.
The following services are not available on the CPACF based machines (Refer to
the ICSF Application Programmer's Guide).
• ANSI X9.17 EDC Generate (CSNAEGN)
• ANSI X9.17 Key Export (CSNAKEX)
• ANSI X9.17 Key Import (CSNAKIM)
• ANSI X9.17 Key Translate (CSNAKTR)
• ANSI X9.17 Transport Key Partial Notarize (CSNAKTR)
• Ciphertext Translate (CSNBCTT)
• PKSC Interface Service (CSFPKSC)
• Transform CDMF Key (CSNBTCK)
• User Derived Key (CSFUDK)
37.No additional information.
38.No additional information.
39.If a customer wants to use a TKE for securely loading keys on the z114, they
must use a supported TKE workstation (FC0841) for attachment to the 2818.
The z114 requires TKE hardware FC0841 and TKE LIC V7.1 (FC0867).
During a machine upgrade, if the base TKE workstation is FC0859, FC0839 or
FC0840 the units cannot not be carried forward. The configurator will delete
these features and add a comparable number of FC0841.
This workstation hardware and TKE 7.1 LIC can also manage host
cryptographic adapters on machine types 2097 and 2098.
To exploit new cryptography enhancements, the new TKE LIC 7.1 LIC and
specific operating system releases and service are required.
40.If your configuration includes a secure device (Crypto Express3 configured as
a coprocessor) then it requires that a master key be loaded before it is
operational. Master keys are required to protect operational keys (a secure
operational key is itself encrypted under the master key before it can leave the
secure boundary of the crypto device, i.e. when it is stored in the CKDS,
PKDS or other external data set).
The master keys that protect operational keys in the CKDS and PKDS must be
available to use those operational keys. When the CKDS/PKDS are taken to a
DR site or moved to a new machine, the master keys must be loaded into the
secure hardware at the DR site or on the new machine.
140
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Master keys can be loaded via Passphrase Initialization, loading multiple key
parts via the ICSF ISPF panels or using the Trusted Key Entry (TKE)
Workstation. See the ICSF Administrator's Guide for details. If the master key
is not available, for some reason, the master key can be changed to a new,
known value in the current environment; however the master key cannot be
changed as part of a machine upgrade. That is, the master keys are stored
within the secure boundary of the secure hardware and there is no way to
extract those values from the hardware. If the passphrase that was used to
generate the master keys is not available, or if the key parts that were loaded
via the ICSF panels is not available, then a key change ceremony can be
performed in the current environment and the operational keys stored in the
CKDS/PKDS can be re enciphered to correspond with the new master key.
This new master key can then be loaded into the secure hardware on the new
machine and the CKDS/PKDS transported to the new machine along with the
new master keys.
41.With the z114 or the z10, new Protected keys are available. If using a secure
key as the source for a protected key, a Crypto Express3 is required. The
Crypto Express3 will decrypt the secure key from under the master key and
re-encrypt it under the appropriate CPACF wrapping key before providing it to
the CPACF.
42.With the latest Crypto Express-3 code release with Driver 93G on the z114
(Common Cryptographic Architecture code level 4.1.0z), IBM has
implemented additional parameter checking and validation to match what has
been published in the manual Cryptographic Services ICSF Application
Programmers Guide. This rule checking is for the Symmetric Key Generation
(SYG) service when using the PKA92 key forming method. Applications that
do not conform to these rules many need to be modified to work successfully
for this service.
An example would be if an external token instead of an internal token was
specified for the RSA_encipher_key_token variable. In previous releases, this
call to the service would have returned 0/0 as the return code / reason code.
That same service call with the z114 will return 8/181. To avoid problems with
your application, please verify that the rules outlined in the Cryptographic
Services ICSF Application Programmer's Guide, are followed.
Please contact your local cryptographic application programmer to address
any issues.
Chapter 5. Must-Read Information
141
Copyright 2011 IBM Corporation. All rights reserved.
5.3 MR-Software Configuration
5.3.1 General
1. Customers are strongly encouraged to review the PSP Buckets on a regular
basis. At a minimum, the buckets should be reviewed if there are plans to
change the processor configuration in any way. This includes upgrading the
Driver Level or applying any hardware MCLs that may be required.
2. Operating system requirements depends on the capabilities that you intend to
exploit.
• The IBM zEnterprise 114 requires :
z/OS V1.13 with PTFs.
z/OS V1.12 with PTFs.
z/OS V1.11 with PTFs.
z/OS v1.10 + PTFs AND the z/OS 1.10 Lifecycle Extended Service
(5656-A01). The Lifecycle Extension must be in place before a customer may
obtain required PTFs for the z114 and z196. There are no exceptions.
z/OS v1.9 + PTFs AND the z/OS 1.9 Lifecycle Extended Service (5646-A01).
The Lifecycle Extension must be in place before a customer may obtain
required PTFs for the z114 and z196. There are no exceptions.
z/OS v1.8 Lifecycle Extended Service (5646-A01). has expired and is no longer
available. Contact GTS for qualifications for a contract. Contract must be in place
to obtain required PTFs for the z114 or z196. There are no exceptions.
z/VM V6.1 with PTFs.
z/VM V5.4 with PTFs.
z/VSE V4.3 with PTFs.
z/VSE V4.2 with PTFs.
z/TPF V1.1
Linux on System z distributions:
Novell SUSE SLES 10 and SLES 11
Red Hat RHEL 5 and RHEL6.
Note: See
http://www.ibm.com/systems/z/os/linux/resources/testedplatforms.html to see
earlier releases of Linux on System z that have been tested and approved.
The z114 contains new functions that require the later versions or
releases of these operating systems. More information can be found in
Chapter 2 Software Requirements.
3. In support of the z114, the High Level Assembler introduced new mnemonics
for the new machine instructions. The new mnemonics may collide with (be
identical to) the names of Assembler macro instructions you use. In the event
of such collisions, the Assembler’s default opcode table (UNI) will treat
specification of these names as instructions, probably causing Assembler
142
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
error messages and possibly causing generation of incorrect object code
If you write programs in Assembler Language, you should compare the names
of Assembler macro instructions you use to the new machine instructions
(documented in the Principles of Operation SA22-7832-08) to identify any
such conflicts or collisions which would occur. Identical names will cause
Assembler errors or the generation of incorrect object code when you
assemble your programs following installation of the enabling PTF.
If a conflict is identified, take one of these actions:
• Change the name of your macro instruction.
• Specify PARM=’…OPTABLE(YOP)…’ (or some other earlier opcode table).
• Specify a separate ASMAOPT file containing assembler options such as in
the previous method (this method requires no changes to source code or
JCL).
• Add as the first statement of your source program: *PROCESS
OPTABLE(YOP)
• Specify the PROFILE option either in JCL or the ASMAOPT file, and the
specified or default member of the SYSLIB data set is copied into the front
of the source program.
If you must use both a new instruction and a macro with the same name in an
assembly, you can use the following technique (where XXX is a sample
mnemonic):
*Assume the default OPTABLE(UNI) is in effect
XXX
a,b (new instruction)
PUSH
ACONTROL (save current optable definition)
ACONTROL OPTABLE(YOP) (switch optable dynamically)
XXX
r,s,t (macro invocation)
POP
ACONTROL(restore previous definition)
XXX
c,d (new instruction)
4. The ARCHITECTURE C/C++ compiler option selects the minimum level of
machine architecture on which your program will run. Certain features
provided by the compiler require a minimum architecture level. ARCH(9)
exploits instructions available on z114 servers. For more information, refer to
the ARCHITECTURE compiler option in z/OS XL C/C++ User’s Guide.
The TUNE compiler option allows you to optimize your application for specific
machine architecture within the constraints imposed by the ARCHITECTURE
option. The TUNE level must not be lower than the setting in the
ARCHITECTURE option. For more information, refer to the TUNE compiler
option in z/OS XL C/C++ User’s Guide.
You must have at least z/OS V1.12 to use this function.
Once programs exploit the ARCH(9) or TUNE(9) option, those programs can
only run on z114 servers, or an operation exception will occur. This is a
consideration for programs that will run on different server levels (z10 or z9)
Chapter 5. Must-Read Information
143
Copyright 2011 IBM Corporation. All rights reserved.
during development, test, and production, as well as during fallback or
disaster recovery.
5. Information regarding Hiperdispatch can be found in Techdocs. See
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs and
search for the keyword HIPERDISPATCH. Also, see the 2818DEVICE PSP
Bucket.
There is a HIPERDISPATCH=YES|NO parameter in IEAOPTxx member of
PARMLIB, and on the SET OPT=xx command to control whether
HiperDispatch is enabled or disabled for the system. It can be changed
dynamically.
The default is that HiperDispatch is disabled on z/OS. A Health Check is
provided to verify that HiperDispatch is enabled on a z114. The Health Check
is shipped active, but only will detect an exception when z/OS is running on a
z114 and HIPERDISPATCH is set to NO.
WLM goal adjustment may be required when using this function. Review and
update your WLM policies as necessary. You may need to turn off and on VCM
while adjusting your WLM goals.
Refer to white paper WP101229 to understand the benefits of HiperDispatch
available via Techdocs web site (www.ibm.com/support/techdocs). It is
recommended to enable HiperDispatch after all the required PTFs and the
zIIP web deliverable (z/OS 1.7 requirement only), are installed.
6. No additional information.
5.3.2 Standalone Dump Considerations
7. IBM has described a set of "best practices" for optimizing stand-alone dump
data capture, optimizing problem analysis time, and ensuring the stand-alone
dump is successful at capturing the necessary information for use by IBM
Service. In particular, the following areas are described:
• Stand-Alone dump data set definition and placement
• IPCS performance considerations
• Preparing documentation to be analyzed
• Sending documentation to IBM support
• Testing your stand-alone dump setup
Technical document, TD103286, contains all the specific details of each step
outline here. This document is at URL:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD103286
This paper is also being updated with information which was described in "Every
picture tells a story: Best practices for stand-alone dump", published in the
February 2007 issue of the z/OS Hot Topics Newsletter. You can access all
issues of the Newsletter at:
www.ibm.com/servers/eserver/zseries/zos/bkserv/hot_topics.html
This paper assumes the installation is operating at least at the z/OS V1R6 level.
z/OS V1R7 enhancements are noted where appropriate. The planning steps are
144
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
highlighted here. The background, details for each step and examples are
documented in the technical paper TD103286. The intent of this paper is to
describe current best practices in setting up for a stand-alone dump, taking the
dump, and post-processing the result. The hope is for the overall process of
getting the dump to IBM Service does not get in the way of getting a quick
resolution to your reported problem. While there are multiple steps to deal with,
z/OS will offer a streamlined process in a future release.
a. Plan a multi-volume stand-alone dump data set, being sure to place each
volume on a separate DASD volume, and on a separate control unit.
b. Create the multi-volume stand-alone dump data set using the AMDSADDD
utility.
c. Define a dump directory with the right attributes to facilitate
post-processing of large stand-alone dumps and large SVC dumps
d. Prepare the dump for further processing using IPCS COPYDUMP
e. Compress data transferred to enable faster transmission and analysis
f. Use PUTDOC to transmit the data to IBM
g. Set up remote access via RSVSF or AOS to allow remote viewing of your
dump by IBM in time-critical situations.
h. Test stand-alone dump setup
5.3.3 IOCP and HCD
8. It will not be possible or allowed to delete any unused Logical Channel
Subsystem or partitions.
9. You now have the ability to extend the amount of addressable storage
capacity to help facilitate storage growth with the introduction of a second
subchannel set - an additional 64K devices - to help complement other
functions such as "large" or extended addressing volumes and HyperPAV.
This may also help to facilitate consistent device address definitions
simplifying addressing schemes for congruous devices.
The first subchannel set (SS 0) allows definitions of any type of device (such
as bases, aliases, secondaries, and those other than disk that do not
implement the concept of associated aliases or secondaries). The second
subchannel set (SS1) can now both be designated for use for disk alias
devices (of both primary and secondary devices) and/or Metro Mirror
secondary devices only.
Second subchannel set applies to ESCON (CHPID type CNC) and FICON
(CHPID type FC; both FICON and zHPF paths).
10.Many times during consolidation of multiple systems onto a single z114 LCSS
it may be necessary to change the MIFID of one or more partitions. Within a
single LCSS there are only 15 MIFIDs allowed and each partition must have a
unique identifier. In some cases, the MIFIDs of partitions being consolidated
are the same and thus modifications need to be made. Since CTCs utilize the
MIFID in the CUADD parameter for the CTC control unit, these definitions will
need to be adjusted.
As noted above, it should also be considered that the partition identifier
Chapter 5. Must-Read Information
145
Copyright 2011 IBM Corporation. All rights reserved.
specified in a CFRM policy must match the value that is specified in the image
profile of the coupling facility partition.
11.No further clarification.
12.LSYSTEM specifies the system name of the local server. It is an alphanumeric
value of 1-8 characters and can begin with either an alphabetic or numeric
character. All alphabetic characters are upper case. HCD will default to the
Central Processor Complex (CPC) name that is specified for the Processor ID.
CSYSTEM is the system name of the target server that is connected by the
LSYSTEM. It is an alphanumeric value of 1-8 characters. It can begin with
either an alphabetic or numeric character. All alphabetic characters are
uppercase. This is handled by HCD.
We recommend defining a customer-specific name for LSYSTEM and not to
accept the default of the CPC name. If the LSYSTEM parameter is changed
(because of a machine upgrade of z10 to z196, for example) the remote
systems at the other end of the PSIFB connection may need a dynamic
activate or a Power-on Reset (for a stand-alone CF) in order to pick up the
new LSYSTEM name. If the LSYSTEM statement remains unchanged from its
original value, then these requirements are not necessary. The LSYSTEM
name is only used in relation to CF link CHPIDs, so using an LSYSTEM name
that is different to the CPC name should not cause any confusion.
5.3.4 CIU,CBU, ON/OFF Capacity on Demand
13.No additional clarification
5.3.5 CFCC
14.The Sizer tool is the only source of determining structure sizes. It can be
found at the following web site:
• http://www.ibm.com/systems/support/z/cfsizer/
CFCC Level 17 increases the number of structures that can be allocated in a
CFCC image from 1023 to 2047. Allowing for more CF structures to be defined
and used in a sysplex, permits more discrete data sharing groups to operate
concurrently and can help environments which require many structures to be
defined, z114, with CFCC level 17, also provides improved serviceability of
Coupling Facilities with enhanced data collection and triggering of
non-disruptive CF dumps.
Note: In order to provide these functional and serviceability enhancements,
the Coupling Facility Control Code will require more storage allocation for
internal control blocks and dump space. Clients should ensure they allocate
additional storage capacity when setting up the image profiles for the Coupling
Facility image. The CFCC code Release 17 will use about 400MB to 450MB of
total storage for each image. This usage is a significant increase over storage
usage in previous CF levels.
Please refer to software co-requirement deliverables for exploitation.
15.No additional clarification
5.3.6 IBM and ISV Software Support
16.No additional clarification
146
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
17.To help avoid unexpected delays, the customer should review and sign the
AWLC agreement right away. The "ICA Attachment for System z Advanced
Workload License Charges" was deployed worldwide through model contract
number INTC-8538 (US form number is Z125-8538), and its associated "IBM
Exhibit for Advanced Workload License Charges" was deployed worldwide
through model contract number INTC-8539 (US form number is Z125-8539).
Advanced Workload License Charges (AWLC) is a monthly license pricing
metric designed to support today's on demand business requirements. IBM
zEnterprise 114 (z114) servers may have AWLC when in a fully qualified
Parallel Sysplex consisting entirely of zEnterprise servers.
See http://www.ibm.com/systems/z/resources/swprice/mlc/awlc.html.
18.Advanced Entry Workload License Charges
Coinciding with the announcement of the IBM zEnterprise 114 (z114) server,
IBM introduces a new software pricing structure called Advanced Entry
Workload License Charges (AEWLC). The AEWLC pricing metric leverages
the reporting mechanisms and existing Millions of Service Units per hour
(MSU) tiers of the Entry Workload License Charges (EWLC) pricing metric and
the Midrange Workload License Charges (MWLC) pricing metric while
extending the software price performance provided by the EWLC and MWLC
tiers. AEWLC applies only to eligible z/OS, z/TPF, and z/VSE operating
systems and their associated middleware programs when running on a z114
server. For additional AEWLC information, refer to Software Announcement
211-250, (RFA54941) "Advanced Entry Workload License Charges offers price
/ performance for the IBM zEnterprise 114," dated July, 12, 2011.
When a z114 server is in an actively coupled Parallel Sysplex, you may elect
aggregated Advanced Workload License Charges (AWLC) pricing or
aggregated Parallel Sysplex License Charges (PSLC) pricing, subject to all
applicable terms and conditions.
For additional information on AWLC, refer to Software Announcement 210-238,
(RFA53175) "Advanced Workload License Charges offers price / performance for
the IBM zEnterprise 196," dated July, 22, 2010.
5.3.7 Crypto
19.ICSF is the crypto software that provides the interface to the crypto hardware
and comes with z/OS. As new hardware and new functions become available
new versions of ICSF that exploit the new functions are available via web
download. In general, ICSF is very upward and downward compatible, so the
currently installed version will generally work on new hardware, however if a
newer version of ICSF is available it may provide additional functionality and
take advantage of the latest hardware capabilities.
HCR7790 (z/OS V1.11, z/OS V1.12, or z/OS V1.13 with Cryptographic
Support for z/OS V1R11-V1R13) is required to fully exploit the capabilities of
the Crypto Express3 and the z114.
Earlier versions of ICSF are supported on the z114 with the appropriate
APARs, see the PSP buckets for details. However, support will be limited to
Chapter 5. Must-Read Information
147
Copyright 2011 IBM Corporation. All rights reserved.
the capabilities available in that earlier version of ICSF. For example, if
HCR7750 is installed you will not be able to take advantage of AES secure key
support on the CEX3 because HCR7751 was the first version of ICSF to
support that functionality.
20.Installation of a new version of ICSF may require that compatibility PTFs for
ICSF be installed on other systems when sharing the CKDS, PKDS or TKDS.
Check the PSP bucket for the version of ICSF being installed for details.
21.No additional clarification
22.Beginning with the z10 machine we dropped support for storing key
management keys as retained keys. Also on the z10 we began supporting
4096-bit RSA keys, which required a migration to a larger LRECL size for the
PKDS (Public Key Data Set). If migrating from an older platform you can use
IBM Healthchecks to check for retained keys and whether 4096-bit keys can
be supported.
23.A UDX is custom code that is installed in the secure hardware of the Crypto
Express card. It allows customers to implement their own unique code within
the tamper resistant hardware. On System z, the UDX code is always
developed based on customer specs by IBM (either the Crypto Competence
Center in Denmark or IBM Global Services in the US) and delivered to the
customer for installation inside the Crypto Card. There is also a key
management software package, called DKMS, from the Crypto Competence
Center that may require a UDX depending, on the customer environment.
Because a UDX interfaces directly with the card and with ICSF (the z/OS
component that provides the software interface to the crypto hardware),
anytime either a new crypto hardware device is installed or the version of
ICSF changes, the UDX must be rebuilt. So if a customer will be migrating
from one hardware device to another (for example, from a CEX2 on a z10 to a
CEX3 on a z196) or upgrading the version of ICSF on their new machine, the
UDX will need to be rebuilt.
You can check for the existence of a UDX in the UDX Status column on the
Crypto Configuration panel on the HMC.
In most cases, the contract with the Services organization covers rebuilding for
new hardware and software platforms, so it is simply a matter of contacting the
appropriate organization to have the UDX updated and tested, however you
should build time into the install schedule for getting the updated UDX's from IBM.
Additionally, if the customer's support contract for the UDX has lapsed, there may
be additional time required to get the paperwork in place..
5.3.8 Sysplex Considerations
24.No further clarification.
25.Volatile is referring to the capability to keep the contents of the CFs memory
intact across a power failure. The volatility of a CF is important to some CF
exploiters, and is also important from an overall recovery point of view. Some
exploiters, like JES2 and System Logger, prefer to use a non-volatile CF, and
may behave differently if forced to use a volatile one.
The non volatility attribute refers to the ability of CFs to maintain their stored
148
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
data should a power outage occur. If coupling facility can’t maintain stored
data during a power outage then it is Volatile.
How is volatility attribute determined and set?
• If the CEC hosting the CF LPAR has an IBF (Internal Battery Feature)
installed, hardware sets the CF to be Nonvolatile.
• If IBF is not installed, but the CEC has UPS installed, the hardware can’t
detect UPS but z/OS can determine failure-independence.
Issue MODE NONVOL command from the HMC to set the CF to be
Nonvolatile. Non volatility is carried across PORs. Non volatility attribute can’t
be set from z/OS console but it can be displayed (Display CF).
It is possible to order a System z processor with an Internal Battery Feature.
The battery backup maintains power to the processor for a short time so that
the structure contents are not lost in case of a power failure. If the processor is
configured with a battery backup, the CFCC senses this and automatically
sets the status of the CF to NONVOLATILE.
However, if you are relying solely on a UPS for power during a power failure,
the CF is not able to sense this and automatically sets its status to be
VOLATILE. The setting of this status can affect the XES algorithms that decide
where to allocate a structure.
If possible, use both the Internal Battery Feature and UPS for your CFs. This
is because it is possible for either type of power source to fail, so by providing
both battery backup and UPS, you improve your likelihood of your CF contents
surviving a power failure.
Regardless of whether you use a battery backup, or a UPS, set up automation
to check the CF volatility status after every POR. This can easily be done
using the D CF command. If the
status is incorrect, you can set it to the correct state using the MODE
command on the CF console on the HMC.
Health check: The XCF_CF_STR_NONVOLATILE check verifies that any
structure that has requested a non-volatile CF is actually residing in such a
CF. If you are unable to provide a non-volatile CF, this check can be disabled.
But if you do have a non-volatile CF and this check issues an exception,
immediately investigate the cause of the exception.
Refer to the PR/SM Planning Guide (Coupling facility non volatility) and the
Redbook, titled "Achieving the Highest Levels of Parallel Sysplex Availability",
SG24-6061 from www.redbooks.ibm.com.
26.When using IRD, each LPAR cluster (which is all LPARs on that CEC that are
part of the same SYSPLEX) use a CF structure to communicate with each
other. The CF structure name is SYSZWLM_SSSSMMMM, where SSSS is the
serial number of the CEC and MMMM is the model number. If the model
number or serial number for that CEC changes a new CF structure will need to
be defined. Otherwise, when WLM initializes it won't find the structure it needs
to communicate and IRD will not be active.
Chapter 5. Must-Read Information
149
Copyright 2011 IBM Corporation. All rights reserved.
27.Some customers elect to specify the HWNAME in the LOADxx parm
This parm is used as a filter to assure that the correct system is IPLed in a
multi-system environment. There is no system default value for this parameter,
the parm is only used if it is hard coded by the customer.
LOADxx Example
IODF
A1 IODFST B710
A1
HWNAME CEC3
IEASYM
(A4,A5)
SYSPLEX UTCPLXJ4
SYSCAT CMNJ4C113CCATALOG.J40CAT
28.No further clarification.
5.3.9 Linux Considerations
29.The Linux Installation Checklist can be obtained from the following web sites.
Customer’s can not access these, so they must be retrieved by either a
business partner or an IBM’er and then provided to the customer.
• http://partners.boulder.ibm.com/src/assur30i.nsf/WebIndex/SA428
• w3.ibm.com/support/assure/assur30i.nsf/WebIndex/SA428
30.No additional information.
31.A partition is defined as a Linux only partition or a VM Mode partition on the
“General” tab of the image profile. Selecting this option will allow the partition
to utilize an IFL processor. Note that VM MODE, if used, requires z/VM V5.4 or
higher.
Note: A shared IFL is no longer managed by PR/SM as part of the pool
which contains shared IFLs, ICFs, and zAAP processors. It is managed
independently.
32.The crypto hardware must be assigned to the LPAR and guests if running as
Linux guests under VM. The Directory entry for the virtual guest must assign
the device and domain as appropriate. For an IFL, the LPAR activation profile
of the VM machine or the Linux partition must have the appropriate devices
defined.
33.The appropriate device drivers (for coprocessors or accelerators) must be
installed to access any new functions on the Crypto Express3.
34.If using a Crypto Express3 as a coprocessor and if you want any new function
provided with the z114, you must install the latest IBM CCA Support Program
software, available for download at
http://www.ibm.com/security/cryptocards/pcixcc/ordersoftware.shtml.
Also, see TechDoc FLASH10620.
35.No additional information.
36.Changes to HiperSockets firmware with driver 93 shipped on September 09,
2011 on z114 and z196 GA2 systems may cause Linux on System z virtual
machines to abend. This change only affects current versions of Linux when a
guest is using dedicated HiperSockets subchannels and z/VM qioassist is
active.
150
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.3.10 zIIP and zAAP Considerations
37.Adding specialty processors to a z114 will affect the overall processor
performance due to the n-way effect. Capacity planning tools must be used to
evaluate the impact to the overall machine.
Before proposing any specialty processors, it is critical that an analysis be
made to determine the benefits to be obtained and that the appropriate levels
of software are installed that can exploit them.
38.No additional information.
5.3.11 SCRT Considerations
39.Customers who do not need to process SMF data from a z114 are not required
to download or use SCRT.
http://ibm.com/zseries/swprice/scrt/
5.3.12 OSA-Express4S and OSA-Express3 Considerations
40.With the OSA-Express4S and OSA-Express3 multi port model (two ports per
CHPID), you must ensure that QDIO ports on the same CHPID have different
names from each other even when being activated by separate VTAMs and IP
Stacks. You must provide a unique name to each PORT on the same CHPID.
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS3950
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS3591
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH1070
6
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101377.
41.OSN CHPIDs are use in conjunction with Communication Server to create a
LINUX LPAR which simulates a 3745.
Chapter 5. Must-Read Information
151
Copyright 2011 IBM Corporation. All rights reserved.
5.4 MR-Installation Plans
5.4.1 General
1. Use customized planning information to prepare for the arrival and installation
of z114 hardware. In order to use the customized planning information
application, a valid order number and a Configuration Control Number (CCN)
are required.
In order to use the customized planning information:
• Logon to the ResourceLink web site,
http://www.ibm.com/servers/resourcelink, to access the aids.
• Go to User profiles on the navigation bar to Request access to customized
planning information. An e-mail confirmation will be sent when access is
available.
• Once authorized, logon to Resource Link and access the customized planning
information in the Planning section of the site. The customized planning
document can be opened and read online, and downloaded for printing or
reference at a later time.
• When accessing the customized plan, use 'Subscribe to customized planning
aids' to automatically receive e-mail notification when changes are made to
the customized document. This eliminates the need to re-check the site for
updates to your customized plan.
The planning aids are customized by order number. They include the feature
codes that affect the weight, height, power requirements, cooling, and cables
necessary for system installation as well as customized system information for:
• Processor codes and descriptions
• System power information
• Frame requirements
• Cooling requirements
• Environmental specifications
• Hardware management console and support element information
2. The plan should include agreed upon dates and outage time estimates.
Ensure that the plan includes provisions for post-implementation production
fall back to a configuration without the z114.
3. See RETAIN TIP H202864
4. If a coupling facility image resides on a z114 server, then the partition number
specified in the CFRM policy is the logical partition identifier specified in the
Hardware Management Console Image Profile (Partition ID). The CFRM policy
utility was changed to accept a two digit hexadecimal PARTITION value for an
LPAR ID greater than 15.
5. Any CTC connections, coupling link connections, or other connections from
systems in the environment which will connect to the z114 should be disabled
during the installation of the z114 in order to avoid any boxed or error
conditions that might be generated during the install if the connections are left
active.
152
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
6. Refer to the following web sites for additional information:
• http://www-03.ibm.com/servers/eserver/zseries/pso/cftable.html
• http://w3.pok.ibm.com/prodeng-cgi/mclinfo.pl
7. No initial power on or diagnostics can be performed until all the IO cards have
been fully moved to the z114 processor. Installation plans and duration should
take this into consideration. This is business as usual.
8. No additional information.
9. Driver Exception Letters can be obtained from ResourceLink
(www.ibm.com/servers/resourcelink).
This letter can be found under the menu “Fixes”.
10.IBM personnel can review alerts at the following web site:
• http://nascpok.pok.ibm.com/
5.4.2 FICON Considerations
11.No further clarification.
12.With the z114 processor speeds and the FICON Express8S or FICON
Express8 performance capabilities, it is very possible to overrun an existing
SAN infrastructure capacity if careful considerations are not given to capacity
planning and the cable environment. Also contentious hot spots, which may
have caused no issues in a 2Gbs environment, may cause issues with the new
processor (or 8Gbs environment) and must be identified and eliminated in
order to smoothly transition from a z9 or z10 to a z114 processor.
Best Practice Guidelines include the following:
A) Verify that the fiber cable infrastructure meets the Fiber Channel Standard
requirements for the speed of operation.
- Detailed information is available in the "Maintenance Information for Fiber
Optic Links", SY27-2597-14.
B) DS8000 Advance Technical Support (ATS) recommends control unit port
utilization needs to be kept at less than 50% or stated differently: I/O intensity
values need to be kept at less than 1000. I/O Intensity values can be obtained
from the RMF ESS link statistics report.
- Ensure that the channels for a disk subsystem are balanced over the Host
Adapters with the same number of paths to each host adapter.
- Ensure that the total workload on Host Adapters is as balanced as possible if
different workloads are sharing the same disk subsystem.
- Ensure that workload is evenly balanced over ISLs in a cascaded FICON
environment.
C) Ensure High Performance FICON for System z (zHPF) and Modified
Indirect Data Address Word Facility (MIDAW) are considered for use.
- More information can be obtained through: "Benefits of using zHPF See:
http://www-01.ibm.com/support/docview.wss?uid=swg27015698.
D) Consider use of the IBM Health Checker for zOS (APAR OA33367).
- The complexity of the network fabric can make it hard to determine the root
of a problem and the symptoms accompanying that problem might not be very
Chapter 5. Must-Read Information
153
Copyright 2011 IBM Corporation. All rights reserved.
clear. Clients using a FICON connection might see I/O errors in the form of
Interface Control Checks or perhaps missing interrupts. I/O service time
degradations might occur without an easily identifiable symptom other than
the average I/O service times increasing as reported by z/OS RMF. Out of all
the variation, one consistent symptom of fabric problems stands out: a high
initial command response (CMR) time for some paths to a control unit, while
the CMR time for other paths to the same control unit are normal.
- The IBM Health Checker for zOS can be used to monitor CMR time and to
provide alerts for problem areas.
- See: "IBM Health Checker for z/OS Users Guide", SA22-7994.
E) Disk Magic is the premier sizing tool for IBM Storage Systems and is
strongly recommended for capacity planning. This tool can help validate data
layout and model storage cache size.
- See: http://w3.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4228.
F) zCP3000 can assist with DASD storage projections.
- See http://w3.ibm.com/support/americas/wsc/cpsproducts.html.
Corrective actions may include:
- adding additional switch or device ports
- adding additional inter-device link capacity (eg: DS8000 PPRC function)
- adding extra inter-switch link capacity
- replacing cabling causing Interface control checks
Additional information can be obtained at the System z I/O Connectivity
website http://www.ibm.com/systems/z/hardware/connectivity/ficon_performance.html.
Also, there are some excellent redbooks which discuss these topics.
- SAN Survival Guide http://www.redbooks.ibm.com/abstracts/sg246143.html?Open
- Intro to SANs http://www.redbooks.ibm.com/abstracts/sg245470.html?Open
- Designing an IBM Storage Area Network http://www.redbooks.ibm.com/abstracts/sg245758.html?Open
- FICON Planning and Implementation guide http://www.redbooks.ibm.com/abstracts/sg246497.html?Open
For FICON Directors, see the Storage SAPR Guides at
http://w3.ibm.com/support/assure/assur30i.nsf/Web/SA (search word =
Storage).
G) Dynamic CHPID Management (DCM)
The objectives for FICON DCM are:
- Simplify I/O configuration planning and definition
- Reduce the customer skills required to manage z/OS
- Dynamically balance I/O channel resources
- More efficient use of channel resources
- Enhance availability
Dynamic Channel Path Management does this by allowing customers to
154
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
identify channels they wish to be “managed”. Managed channels are channels
which are not assigned to any specific control unit by the customer, but
instead viewed as a pool of channels (or CHPIDs).
For more information on DCM setup and implementation refer to the “FICON
DCM for System Programmers” document, which can be found on the web at
http://www.ibm.com/support/techdocs
Search for document number WP101544 under the category of “White
Papers”.
H) During an machine upgrade, it’s an excellent time to clean fiber
connections. Recommended cleaning procedures can be found at
http://ehngsa.ibm.com/home/n/l/nl27971/web/public/FTS_home/Maintenance/
maintenance.html.
13.Review buffer credits on FICON Director(s) ports to insure that there are an
adequate number of buffer credits to sustain a good performance over the un
repeated distance as well as repeated distances when upgrading to a 8 Gbps
link. FICON director(s) ports "may" only have a minimum set of buffer credits
defined as the default, and in some cases that might mean 26 or less buffer
credits. Adjusting the number of buffer credits appropriately will depend on
average frame size, distance and bandwidth. Average frame size can be
obtained through the FICON Director Activity Report when defining the FICON
Director or the Control Unit Port (CUP). Additional examples for the buffer
credit values can be found in the RedBook entitled, FICON Implementation
Guide SG24-6497.
Buffer credits for FICON Express8
 40 buffer credits available per channel
 Conforms to Fibre Channel standard flow control
?
?
?
Avoids overwriting the buffer
40 credits is 80 KB of buffer at the receiver
Sufficient to hold the maximum data payload on the fiber for 20 km (round trip) of data
Anything less will not fill the buffer
 Receiver side of port should contain sufficient buffer credits to ensure channel is
fully utilized
?
Receiver must contain = > 4 buffer credits per km of fiber distance at 8 Gbps
 Buffer credits are directly related to the distance supported
?
?
8 Gbps needs about 4 credits/km...
10 km = about 40 credits. 100 km = about 400 credits
4 Gbps needs about 2 credits/km...
10 km = about 20 credits. 100 km = about 200 credits
 In the short block case, the concern is response time, not data bandwidth. Where
the buffer-to-buffer credits (BtoB credits) becomes an issue is when large blocks
per I/O are being transferred, so link bandwidth becomes the factor of interest. In
this case, the frames will be almost always full (2K).
14.For FICON Express8S or FICON Express8 there are 40 buffer credits per
channel and buffer credits are directly related to the distance and speed of the
channel:
• 8 Gbps needs about 4 credits/km.
Chapter 5. Must-Read Information
155
Copyright 2011 IBM Corporation. All rights reserved.
• 10 km = about 40 credits. 100 km = about 400 credits
• .4 Gbps needs about 2 credits/km.
• 10 km = about 20 credits. 100 km = about 200 credits
In the short block case, the concern is response time, not data bandwidth. Where
the buffer-to-buffer credits (BtoB credits) becomes an issue is when large blocks
per I/O are being transferred, so link bandwidth becomes the factor of interest. In
this case, the frames will be almost always full (2K).
15.Contact provider of the switches/directors to determine appropriate levels.
16.zHPF is no charge on the z114, but there may a charge on the storage
controller. A parmlib modification is required and a storage control unit that
supports zHPF. For z/OS, you must then set ZHPF=YES in IECIOSxx in
SYS1.PARMLIB or issue the SETIOS ZHPF=YES command. ZHPF=NO is the
default setting.
For FICON performance improvements due to zHPF, see
http://www.ibm.com/systems/z/hardware/connectivity/ficon_performance.html.
See http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FQ126612
for storage controller requirements.
5.4.3 CHPID Mapping Tool
17.It is possible within HCD/HCM or IOCP to directly assign PCHIDs to CHPIDs.
However, the use of the CHPID Mapping Tool is strongly encouraged in order
to avoid errors generated when entering the data directly. Regardless of what
method is used to assign CHPIDs to PCHIDs, it is imperative that any analysis
take into account the cabling infrastructure of the machine. Furthermore, the
availability option of the CHPID Mapping Tool is the preferred method for
assigning CHPIDs to PCHIDS for the following reasons:
• The availability option minimizes changes required to HCD/HCM/IOCP in that
existing CHPID assignments can be maintained. Maintaining the CHPID
assignments will also minimize changes to in-house documentation as well as
operations familiarity with the system.
• The availability option frees the customer from requiring an in-depth
knowledge of the underlying machine infrastructure and availability
boundaries
• The availability option spreads channels for availability across four levels of
availability: Book, MBA, STI, and card. It is extremely difficult to manually
assign channels across this many levels.
18.The only options for downloading the tool are the full version (with java) or the
update file.
Note: ResourceLink enforces a five minute limit on downloads. If the file has
not completed after five minutes, the download will stop without much
indication. Customers should make sure they are on a fast link to insure
successful completion of the download. Dial-up connections should never be
used for downloading the tool.
Note: Customers must define the complete IOCP in HCD/HCM or IOCP
156
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
before using the mapping tool. If the z114 is a new-build, no PCHIDs are
needed in the IOCP input.
19.No additional information.
5.4.4 Configuration files and PCHID assignment changes
20.The following information applies if you are performing:
• An MES from a z9 or z10 BC to a z114
• A MES from a z10 to another z10
• An upgrade from a z9 to a z10.
On the “from” machines, customization information is stored in files on the SE.
The files are called configuration files (or config files), and they are named
based on the PCHID value (physical location) of the channel. The following
table lists channel or CHPID types that have config files on a z10, z9, z990 or
z890, and the kind of information stored in these files:
Table 18. Channel or CHPID Type Information in Configuration Files
Channel or CHPID Type
Information in Configuration Files
OSA-Express2 or OSA-Express3
Any user specified MAC addresses and OAT
tables
1000BaseT channel defined as CHPID type
OSC
Console session information.
FCP CHPID using LUN access control
Access Control Table (ACT)
For an upgrade, if channels or CHPIDs have associated configuration files,
the CHPID Mapping Tool can assign PCHIDs to your logical CHPID definitions
or move a CHPID definition to a new location. This can occur regardless of
whether channels are moving. The CHPID Mapping Tool can override PCHID
assignments for the following:
FICON channels supporting FCP:
•
•
•
•
•
•
•
•
•
•
•
2319
2320
3318
3319
3320
3321
3322
3323
3324
3325
3326
FICON
FICON
FICON
FICON
FICON
FICON
FICON
FICON
FICON
FICON
FICON
Express LX
Express SX
Express4-2C SX
Express2 LX
Express2 SX
Express4 10KM LX
Express4 SX
Express4-2C 4KM LX
Express4 4KM LX
Express8 10KM LX
Express8 SX
OSA Express2 and OSA Express3 channels supporting OSC:
•
•
•
•
1366
3366
3367
3369
OSA-Express
OSA-Express2 1000Base-T
OSA-Express3 1000Base-T
OSA-Express3 1000Base-T
The following explains how the system preserves the config files on an
upgrade. However, it is ultimately your responsibility to have a record or
Chapter 5. Must-Read Information
157
Copyright 2011 IBM Corporation. All rights reserved.
backup of the customization data stored in config files. You should always
make a backup record:
• For OSA-Express2 and OSA-Express3 channels, record all user assigned
MAC addresses using the Display or alter MAC address function in Card
specific advanced facilities or user-specified OSA Address Tables (OAT).
Note: If you are an OSA/SF user, a better method is to use OSA/SF to
back-up and restore the configuration information for the OSA Express2 and
OSA-Express3 channels.
• For CHPIDs defined as OSC (OSA-ICC), use the Export source file
function in Manual configuration options.
• For FCP ACT, ensure the access rights source is current and available to
the privileged (the one with access to the ‘FC’ or ‘FD’ unit address) Linux
image.
For an upgrade, most of the existing channels cards to move from the old
machine to the new machine are rebalanced to take advantage of the
availability characteristics of the z114. This rebalancing also takes into
consideration any new channels that may be added as part of the upgrade.
The configurator creates machine configuration data and reports that contain
information on which PCHIDs have been relocated.
The information contained in the configurator data is used to create a CD that
the service representative uses as part of the installation (or MES) activities of
the z114. This CD supports the relocation for channel types that have specific
files containing customization data.
It is important that the file names containing the customization data be
renamed to the new PCHID value. As part of the installation (or MES) process,
the service representative is presented with a panel (Migrate Channel
Configuration Files) that shows the movement of PCHIDs based on the
information contained in the manufacturing-provided CD. This function
provides the capability to automatically rename the files so that they reflect the
new PCHID values (so that the customization data is not lost and follows the
physical movement for those cards). If you used the CHPID Mapping Tool to
perform the CHPID to PCHID assignments (a process that is recommended),
then the service representative need only accept the values on the panel and
the files are copied correctly. On the panels displayed, the service
representative can change the “TO” PCHID during this process.
This can accommodate those customers who choose not to follow the
recommendations (those who do not use the CMT CHPID Mapping Tool or
who override the CHPID Mapping Tool default assignments). If the customer
and service representative team preplan and develop their own
from-to-PCHID list, manual entry can be used to override the CD.
It is strongly recommended that you use the CHPID Mapping Tool to configure
the CHPID to PCHID assignments because the tool ensures that logical
CHPIDs are assigned to the new PCHID values. The tool has been changed to
handle the previously described issues. When the appropriate files have been
loaded into the tool, the tool assigns new PCHID values to those affected
CHPIDs based solely on the physical movement of the channel cards. If you
use the manual mode, these PCHIDs have an identifier (config file). You are
not recommended to change that these assignments.
158
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
The availability mapping option is recommended. If you choose the availability
mapping option (this is the recommended method), the CHPID Mapping Tool
protects any CHPID/PCHIDs that have been assigned because of config files.
The tool does not make any changes unless you select the option to change
the assignments as part of the availability process. A Reset CHPIDs assigned
by CMT for config files option is available to reset the CMT CHPID Mapping
Tool assignments for config files. The other reset options do not reset the
config file assignments. You are recommended not to reset the config file
assignments. After you run the availability option and review the intersects, if
you believe the config file assignments are causing unacceptable intersects,
you are recommended to use manual mapping to reset only those config file
assignments that are causing the unacceptable intersects. Remember it is
your responsibility to have backed up the customization data (and to restore it
to the PCHID to which the logical CHPID has been assigned).
21.After having completed working with the CHPID Mapping Tool, one of the
available reports will identify all the CHPIDs that have new PCHID values. A
subset of these may have had config files associated with the old PCHIDs.
The service representative can use this report to verify or change the “to”
column of the Migrate Channel Configuration Files panel.
Note: The use of the mapping tool is highly recommend for this migration
because it ensures the logical CHPIDs are assigned to the new PCHID values.
The IOCP file that is input to the CHPID Mapping Tool must contain the current
CHPID to PCHID assignments for the CHPID Mapping Tool to perform the
function as previously described.
5.4.5 Capacity Backup and On/Off Capacity on Demand
22.Discontinuance and removal of Capacity on Demand features:
Certain events require that you discontinue your use of one or more of the
Capacity on Demand (CoD) features on a machine and remove those features
from the machine. The events include:
•
•
•
•
•
You are upgrading your machine to a newer model
You are selling your machine to another party
You are returning your machine to IBM or another leasing company
You no longer wish to participate in the CoD offering
IBM has withdrawn the machine's CoD features from marketing (not
applicable to CBU or CPE features).
Upgrading your system
If you are upgrading your machine from a z9, then prior to the upgrade, you
need to follow these steps on the z9:
a. Deactivate any active CBU or On/Off CoD records,
b. Delete any staged On/Off CoD records, and
c. Transmit or upload vital product data (VPD) to IBM.
If you are upgrading your machine from a z10 to a z114, then how the
upgrade is being done determines what steps are required. For upgrades
where the machine's serial number remains the same, your IBM service
representative will migrate your CoD records to the upgraded machine as part
of the upgrade installation. But prior to the upgrade you need to perform the
following actions:
Chapter 5. Must-Read Information
159
Copyright 2011 IBM Corporation. All rights reserved.
a. Deactivate any active CoD records, and
b. Transmit or upload vital product data (VPD) to IBM.
Step b gives IBM an accurate representation of your machine's current CoD
record state prior to the upgrade. It is especially important for On/Off CoD
users to ensure that IBM Resource Link has an accurate record of all On/Off
CoD activity that has occurred on the system prior to the upgrade being
performed. IBM computes charges for On/Off CoD usage based on
information returned with the VPD, and incomplete VPD could result in
incorrect charges.
If your z10 to z114 upgrade is a System z Exchange Program (formerly known as a
hybrid offering) or other type of upgrade where the new/upgraded machine has a
different serial number than the original machine, then you need to take the
following steps for all CoD records:
a.
b.
c.
d.
Deactivate any active CoD records,
Delete any installed CoD records,
Delete any staged CoD records, and
Transmit or upload vital product data (VPD) to IBM.
Selling your machine to another company If you are selling your machine to a third party, you must remove all CoD
records on the machine, including CBU and CPE records, prior to deinstalling
the machine and transferring it to the new owner.
Returning your leased machine to IBM If you are returning a leased machine to IBM or another lessor, the temporary
CoD records on the system must be removed prior to returning it. You need
to perform the following steps:
a.
b.
c.
d.
Deactivate any active CoD records,
Delete any installed CoD records,
Delete any staged CoD records, and
Transmit or upload vital product data (VPD) to IBM.
IBM withdraws the machine from marketing When IBM withdraws a machine from marketing, the right to use post-paid
On/Off CoD records typically is withdrawn. Your right to use prepaid CoD
records, such as CBU, CPE, or prepaid On/Off CoD typically remains until
terminated per the terms of the offering. You should check the announcement
and offering terms for details. Upon the withdrawal from marketing of your
System z machine, you need to perform the following operations unless
instructed otherwise by IBM.
a.
b.
c.
d.
Deactivate any active post-paid On/Off CoD records,
Delete any installed post-paid On/Off CoD records,
Delete any staged post-paid On/Off CoD records, and
Transmit or upload vital product data (VPD) to IBM.
23.Refer to the Capacity on Demand User’s Guide and educational items on
ResourceLink for further information.
160
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
24.The CBU contract provides for multiple tests and the CBU contract should be
reviewed to identify any limitations.
On/Off Capacity on Demand provides for a single test of the capability. This
test of the On/Off Capacity on Demand automatically terminates at the end of
the 24 hour period.
25.On the z10, new machines with CBU ordered the machine would have all the
temporary orders available as "staged records". Before any of the resources in
the CBU could be used, the order needed to be installed. Once a record had
been installed, it is removed from the Staged Records panel and can never be
restored into "Staged Records".
This is also true on z114 as well, but on the z114 up to 4 temporary records
will be “installed” instead of staged.
Refer to the zEnterprise Capacity on Demand User's Guide SC28-2605 in
ResourceLink for further information. Setting up the records for CBU is a
customer responsibility.
26.Refer to the publications and education offerings available on ResourceLink
for additional information.
27.The On/Off Capacity on Demand capability allows customers to temporarily
add processors to their servers to accommodate peak/unforeseen workloads
and to remove these processors when no longer needed. There are no special
GDPS facilities to perform On/Off CoD activation/deactivation as there are for
CBU activation/deactivation. On/Off CoD activation/deactivation (or the
removal of a sufficient number of active On/Off CoD processor units) must be
performed manually from the HMC following the standard procedures.
If On/Off CoD engines have been activated on a server and there are not
enough processor units (PUs) to active a CBU record simultaneously, some
number of PUs must first be deleted from the On/Off CoD record before CBU
can be fully activated. That is, there will be “pending” CBU activation capacity.
GDPS has no awareness of active On/Off CoD engines in a configuration.
If there is an attempt to activate CBU capacity using GDPS when On/Off
Capacity is already active, the CBU activation may not fully activate all
planned CBU capacity. If both On/Off Capacity on Demand and CBU
configured on a server, customer should place an ASSIST statement in the
script prior to CBU activation to have the operator check whether On/Off
Capacity on Demand is active and to remove an PUs that may interfere with
CBU activation.
Also, if your GDPS scripts (or other automation solutions) use the Application
Programming Interface via the Hardware Management Console, be sure that
Chapter 5. Must-Read Information
161
Copyright 2011 IBM Corporation. All rights reserved.
“Allow capacity change API requests” is checked in the panel shown here.
5.4.6 Hardware Management Console LAN
28.Each SE will require a unique IP address.
5.4.7 ESCON Converters and 3745 (Carry Over from 9672 and z900)
29.The following ESCON converter requirements are a carry over from previous
generation processors.
• If any devices are to be attached via ESCON Converters, review RETAIN Tips
H125640, H125641, H016049.
• If any ESCON channels are to be defined as TYPE=CVC or CBY, ensure that
each of these channels will have an ESCON converter 9034 or equivalent
attached prior to POR. If this is not done, errors will occur during POR causing
unnecessary delay. If a converter will not be installed, the CVC channel should
be placed in Service Status to avoid generating the associated errors during
machine POR.
• If any ESCON channel is to be defined as TYPE=CBY, ensure that the
ESCON converter 9034 attached has serial number 53345 or higher OR has
had RPQ 8P1767 applied. If this is not done, POR will fail.
• If the customer intends to attach a 3745 running PEP at a supported EC level
but without ECA110, have the Service Representative review RETAIN
hardware tip H062352 for applicability and take action to add ECA110 if
needed.
162
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.4.8 HCD/IOCP Definition
30.See the Standalone IOCP User's Guide, SB10-7152.
The DVD-RAM in the HMC has been replaced with a removable write able
media - the USB flash memory drive. The new media has better portability,
reliability, and storage capacity.
More than one USB flash memory drive can be present in the console at the
same time. This capability allows the Backup Critical Data task, which requires
a USB flash memory drive in the console, and other tasks to have access to a
USB flash memory drive simultaneously.
Note: Some tasks available in Service Representative ('service' user ID) still
support the DVD-RAM, but this support will be phased out in future versions of
the HMC.
The USB (SMART) drives will have color coded labels. Red is BACKUP and
Blue is everything else.
5.4.9 Software
31.Measurements show improved ITR benefits of 0% - 5% when running with
CPENABLE= (10, 30). Environments with a high n-way and/or high I/O rates
showed greater improvement, whereas when running with
CPENABLE=(10,30) in lower n-way and lower I/O rates showed no difference.
Thus rather than try to differentiate between certain n-ways, since low is not
disadvantage the decision was made to make a single new recommendation
Therefore, IBM recommends a CPENABLE=(10,30) setting for z990, z890,
IBM System z9, z10 and the z114. Recommendations for all other processors
remain the same.
CPENABLE is a parameter which allows z/OS to dynamically manage the
number of processors which fields I/O interrupts. The original benefit of
CPENABLE was to provide increased ITR in the environment by limiting the
code used to process I/O interrupts to fewer CPs. This improves the locality of
reference in the HSB for CPs enabled for I/O processing and provides overall
ITR benefits.
With shared CPs under PR/SM, z/OS would enable logical CPs for I/O but had
no control over which physical CP would be dispatched to the logical. Thus the
efficiency algorithm had limited impact because there was no method to
control the physical CP dispatching and reap the benefits of assigning the I/O
processing to few CPs. This is why CPENABLE was set to (0,0) for a shared
environment.
The reason for the current change is the I/O processing in the z990, z890,
System z9 and the System z10 is different and provides better throughput
when there are fewer CPs in the path due to some serialization issues.
CPENABLE provides this behavior. So in this case we are not worried that
z/OS is enabling logicals and PR/SM is dispatching across different physical
processors. Instead in this case CPENABLE does gain us the benefit of
having fewer CPs in the I/O processing path. Installations reviewing this
change should review the I/O response time of their LPARs. CPENABLE is a
parameter which involves a trade-off of I/O responsiveness for throughput. It is
Chapter 5. Must-Read Information
163
Copyright 2011 IBM Corporation. All rights reserved.
our expectation, based on benchmark measurement across a wide range of
environments, no change in I/O response times will be seen.
Table 19. CPENABLE Settings
Processor Family
Basic Mode
LPAR Dedicated
LPAR Shared
2817/2818
z196/z114
N/A
(10,30)
(10,30)
2097/2098
z10 EC/z10 BC
N/A
(10,30)
(10,30)
2094/2096
z9 EC/z9 BC
N/A
(10,30)
(10,30)
2084/2086
z990/z890
N/A
(10,30)
(10,30)
2064/2066
z900/z800
(10,30)
(10,30)
(0,0)
9672 G5, G6
(10,30)
(10,30)
(0,0)
9672 G1, G2, G3,
G4
(10,30)
(10,30)
(10,30)
MP3000 (1)
(10,30)
(10,30)
(0,0)
MP2000 (2),
ASP3000(3)
(10,30)
(10,30)
(10,30)
ES/3090, ES9021
(10,30)
(10,30)
(0,0)
(1) Model Type = 7060
(2) Model Type = 2003
(3) Model Type = 3000
32.Storage granularity on the z990 and later processors is not based on total
installed storage as in earlier processors. Rather, granularity is determined for
each Logical Partition when activated and is based on the amount of total
storage to be configured to the partition.
Granularity of initial and reserved central storage amounts is dependent on
the largest central storage amount (CSA) for the LPAR as follows:
Largest Central Storage Amount
Storage Granularity
< or = 64 GB
128 MB
64 GB < CSA < or = 128 GB
256 MB
128 GB < CSA < or = 248 GB
512 MB
Set the RSU parameter to the same value that you specified in the central
storage Reserved field.
If the customer manipulates storage on the processor then an analysis should
be done to determine the current setting for RSU and what the value should
164
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
be on the new processor. An incorrect RSU setting will result in performance
issues that may be very difficult to diagnose. There have been cases where an
incorrect setting has caused a processor installation to fail and resulted in the
backing out of all installation steps.
5.4.10 Activation Profiles
33.The dynamic expansion capability allowed a coupling facility partition defined
with dedicated ICFs to use CPs or ICFs from the shared pools when needed.
Whenever the use of a CP or ICF from the shared pool is needed, it was
important that the coupling facility partition be given the highest priority when
competing with other partitions for the use of shared resources.
Note: This function has been removed on the z114.
34.In order to avoid an IPL following a concurrent upgrade, reserved processors
should be specified for any partition that will use the added resource. The
z114 hardware will allow the customer to specify more processors than might
be supported by the operating system to be loaded into the partition. Defining
greater than maximum number of processors (sum of initial and reserved for
all processor types which includes any specialty processors) supported by the
operating system will result in a failure of the IPL. Refer to the operating
system documentation or the PR/SM Planning Guide for detailed information
and limits.
35.Concurrent memory upgrade uses the same mechanisms as Dynamic Storage
Reconfiguration. Refer to the PR/SM Planning Guide for the z114 for a
discussion on this topic.
36.VM Image Mode On System z9, the supported Activation Image Profile Modes included the
following: (a, b, c, d).
a) ESA/390 - Supports CPs, zAAPs, & zIIPs
b) ESA/390 TPF - Support CPs
c) Coupling Facility - Supports CPs & ICFs
d) Linux only - Support CPs & IFLs
e) VM MODE - Support for CPs, zIIPs, zAAPs, IFLs, ICFs
VM MODE (e) is a new mode on the z114 and z10.
Do not use VM MODE without z/VM V5.4 due to unpredictable results (IPL
failure of z/OS for example).
The HMC and SE versions support an additional Activation Image Profile
mode called VM MODE. This image mode will support CPs, zAAPs, zIIPs,
ICFs, and IFLs. It allows all the varying rules and processor combinations in
the above modes. The only requirement is that z/VM is the base operating
system in that Image. This allows for easier Image Profile planning for
whatever guest operating systems may run in that z/VM image. This also
allows running different operating systems within that z/VM image for different
purposes/processor requirements.
The key advantage of this support is for environments where customers need
to use z/VM 5.4 to host Linux and z/OS or z/VSE guests in the same "box",
they will not have to artificially separate the management of those two
Chapter 5. Must-Read Information
165
Copyright 2011 IBM Corporation. All rights reserved.
environments if they do not want to. They can manage one z/VM image to host
the entire collection of guests they want to deploy.
5.4.11 OSA-Express Considerations
37.Unified Resource Manager (FC0025) requires a minimum of two
OSA-Express3 1000Base-T features.
38.Changing or adding OSA-Express2 or OSA-Express3 cards may result in a
changed MAC address. Ensure that any networking considerations have been
addressed.
39.The following text is taken from Retain Tip H192934.
We have had a number of problems reporting the loss of a customer defined
OAT on OSE PCHIDs, and the loss of customer configurations on OSA/ICC
(OSC) PCHIDs during patch apply sessions or after Power-on Resets (PORs).
This is occurring because of PORs being done that change the OSA PCHID
definition....IE; OSE > OSD.
A POR with the D0 IOCDS 'DOES NOT' delete the OSA configuration files on
the SE, but subsequent customer PORs may, If the wrong IOCDS is POR'ed,
that changes the PCHID configuration. This includes any IOCDS, if the IOCDS
changes the OSA PCHID definition, the previous SE configuration file will be
overlaid, and have to be restored, from a backup file.
When the D0 IOCDS is used, ALL OSA Express cards PCHIDs are put into
OSD mode. OSD mode does not allow customer configurations or OSC
operation.
Subsequently, when returning the PCHID to the normal operating mode
defined by the customer, the correct Customer IOCDS must be used. OR the
OAT or ICC configuration may be lost and must be reloaded from the
customer's backup copy of this data.
If current backups are not kept, a manual rebuild must be done by the
customer.
PE stresses the importance of keeping current backups for this and other
issues that cause the loss of data stored on the card.
OSA/SF is used to load the Customer defined OAT. OSA/ICC configuration
files can be exported & imported.
5.4.12 Crypto Considerations
40.If the client’s CKDS was first initialized on a CPACF based machine (z990/890
or later), is the client aware that it will not be usable on a CCF based machine
(z900/800 or earlier) without migrating the records to a CCF-initialized CKDS?
See ‘Sharing and migrating a CKDS/PKDS between a CCF system and a
PCIXCC/CEX2C system’ in the ICSF Administrator’s Guide.
41.Disaster Recovery (DR) agreements should be reviewed for crypto
considerations.
166
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
If a secure device (CEX coprocessor) is available at the production site, a
secure device must be available at the DR site to provide equivalent function.
If using clear key, you can not run DR using z900/800 or below processors.
The CPACF based machines (z890/z990 or later) provide support for clear key
APIs. The CCF based machines (z800/z900 or earlier) do not support those
clear key APIs, so applications or products which invoke those APIs may fail.
42.Have plans been made to have the master key parts and loading procedures
available at DR site? The master keys that protect operational keys in the
CKDS and PKDS must be available to use those operational keys. When the
CKDS/PKDS are taken to a DR site or moved to a new machine, the master
keys must be loaded into the secure hardware at the DR site or on the new
machine.
If you no longer have the master keys that are loaded into the secure key
hardware, you can change them to a known value prior to the upgrade and
then load those known values when the new system(s) are IPL'ed. See the
appropriate chapter on 'Managing Master Keys' in the ICSF Admin Guide for
key change ceremony steps.
The key point here is that if you don't know the master keys you can change
the keys today (before the upgrade) and then load those known values after
the upgrade. If you don't know the keys today, its too late after the upgrade.
Because of the security of the cryptographic hardware, recovering operational
keys stored in the secure repositories cannot be accomplished without system
changes that may impact operational policies. For example, a secure key
cannot be retrieved from the CKDS by an typical application. During normal
operation, ICSF will retrieve the key, but if an application needs access to the
key material it must be running APF authorized. Private keys (from an RSA
key pair) cannot be retrieved from the PKDS.
Chapter 5. Must-Read Information
167
Copyright 2011 IBM Corporation. All rights reserved.
5.5 MR-Physical Site
5.5.1 General
1. The following can be used to engage IBM Global Facilities Cabling Services
team:
a. Register the project using the form:
• http://ehngsa.ibm.com/home/n/l/nl27971/web/public/Training/Projectregi
stration/GTS%20Project%20registration%20cabling.doc
b. Send the form to Cabling@us.ibm.com
c. Send output of the System configurator or configuration in the same mail
d. The IBM Global Facilities Cabling Services team will involve the local
cabling practitioner
e. The local responsible IBM cabling practitioner will contact the STG account
team
f. Customer will be contacted to collect requirements
g. An assessment will be done
h. A structured cabling design (including IBM FTS) will be made
i. Proposal will be made to the customer or the local IBM STG account team
j. After acceptance of the proposal, cables will be ordered, delivered and
installed
2. The CHPID mapping tool provides several useful reports as part of the final
output. It is strongly recommended that all reports be printed and saved for
use during the installation and follow on support. There are two cabling
worksheets that are available from the CHPID Mapping Tool (CMT):
• CHPID Mapping Tool - Fiber Cable Worksheet
• CHPID Mapping Tool - FQC Report (a section of the Report is the FQC
Worksheet).
• On an upgrade, the CHPID Mapping Tool will provide a “moved report” for all
the channel cards that are located in different physical locations on the z114.
This report contains the from-to CHPIDs and will be invaluable in updating
cable labels.
As a minimum the CHPID Mapping Tool CHPID report should be made
available. Note that the FQC report/worksheet is available from the CMT even
if the machine is not ordered with FQC (if the customer forgets to order FQC
and wants it installed in the field, the FQC report will help). In addition, the
reports from the mapping tool can be used when creating cable labels for the
installation.
3. If only ESCON Quick Connect or only FICON Quick Connect is to be used,
there will need to be time allocated to handle the modification to the internal
harnesses to accommodate that as part of the installation activities.
4. No additional information.
168
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.5.2 OSA-Express3 Considerations
5. The following diagram shows the port nomenclature for an OSA-Express3
card that supports multiple ports per CHPID.
Note the naming of ports on the bottom part of the card. Overall, the ports are
numbered from top to bottom as P0, P1, P1, P0 and not P0, P1,P0, P1 as one
might expect.
Port 0
Port 1
Port 0
Port 1
5.5.3 Cabling-Using IBM zSeries Fiber Cabling Service Contract
6. Refer to the Appendix in the SAPR guide for further information.
7. Refer to the Appendix in the SAPR guide for further information.
8. Any custom contracts should be reviewed to ensure that the Customer and
IBM are in agreement as to what services are included and what services are
excluded.
9. Determine the status of the contract and if there are any impediments.
10.No additional clarification.
11.No additional clarification.
5.5.4 Cabling-Customer Not Using IBM Cabling Service
12.No additional clarification.
13.The following illustrates the connectors required on various features.
Chapter 5. Must-Read Information
169
Copyright 2011 IBM Corporation. All rights reserved.
Older features (not available on the z114) are included as a comparative
reference.
Table 20. FICON Connectors
Feature Code
Description
Connector Type
FC 2319
FICON Express LX (Long
Wave)
Single Mode LC Duplex (9
micron)
FC 2320
FICON Express SX (Short
Wave)
Multimode LC Duplex (50
and 62.5 micron)
FC3319
FICON Express2 LX (Long
Wave)
Single Mode LC Duplex
(9/125 micron)
FC3320
FICON Express2 SX (Short
Wave)
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
FC3321
FICON Express4 10KM LX
Single Mode LC Duplex (9
micron)
FC3322
FICON Express4 SX
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
FC3323
FICON Express4-2C 4KM
LX
Single Mode LC Duplex (9
micron)
FC3324
FICON Express4 4KM LX
Single Mode LC Duplex (9
micron)
FC3325
FICON Express8 10KM LX
Single Mode LC Duplex (9
micron)
FC3326
FICON Express8 SX
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
FC0409
FICON Express8S 10KM LX
Single Mode LC Duplex (9
micron)
FC0410
FICON Express8S SX
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
Feature Code
Description
Connector Type
FC 2324 (FC 2323)
ESCON Ports
Multimode MT-RJ (62.5
micron)
Feature Code
Description
Connector Type
FC 0218/0219
2 port ISC-3
Single Mode LC Duplex (9
micron)
Table 21. ESCON Connectors
Table 22. ISC-3 Connectors
Table 23. OSA-Express Connectors
170
SA11-002-02
Feature Code
Description
Connector Type
FC 1364
2-Port LX Gigabit Ethernet
Single Mode LC Duplex (9
micron)
Copyright 2011 IBM Corporation. All rights reserved.
Feature Code
Description
Connector Type
FC 1365
2-Port SX Gigabit Ethernet
Multimode LC Duplex (50
and 62.5 micron)
FC 2364
2-Port LX Gigabit Ethernet
Single Mode SC Duplex (9
micron)
FC 2365
2-Port SX Gigabit Ethernet
Multimode SC Duplex (50
and 62.5 micron)
FC3364
OSA -Express2 GbE LX
Single Mode LC Duplex (9
micron)
FC3365
OSA-Express2 GbE SX
Multimode LC Duplex (50
and 62.5 micron)
FC3368
OSA-Express2 10 GbE
Long Reach
Single Mode SC Duplex (9
micron)
Note: different connector
than OSA-Express2 GbE
FC 2366
2-Port Fast Ethernet
RJ-45 (copper wire, not fiber
optic)
FC 1366
2-Port 1000Base-T Ethernet
RJ-45 (copper wire, not fiber
optic)
FC 3366
OSA Express2 2-Port
1000Base-T Ethernet
RJ-45 (copper wire, not fiber
optic)
FC3362
OSA-Express3 4-Port LX
Gigabit Ethernet
9 micron single mode
LC Duplex
FC3363
OSA-Express3 4-Port SX
Gigabit Ethernet
50 and 62.5 micron multimode
LC Duplex
FC3367
OSA-Express3 4-Port
1000BaseT Ethernet
Category 5 UTP copper wire
RJ-45
FC3369
OSA-Express3 2-Port
1000BaseT Ethernet
Category 5 UTP copper wire
RJ-45
FC3370
OSA-Express3 2-Port LR 10
Gigabit Ethernet
9 micron single mode
LC Duplex
FC3371
OSA-Express3 2-Port SR 10
Gigabit Ethernet
50 and 62.5 micron multimode
LC Duplex
FC0404
OSA-Express4S 1 GbE EN
LX PCIe I/O drawer only 2
port card - 1 PCHID
9 micron single mode
LC Duplex
FC0405
OSA-Express4S 1 GbE EN
SX PCIe I/O drawer only 2
port card - 1 PCHID
50 and 62.5 micron multimode
LC Duplex
Chapter 5. Must-Read Information
171
Copyright 2011 IBM Corporation. All rights reserved.
Feature Code
Description
Connector Type
FC0406
0406 OSA-Express4S 10
GbE EN LR
9 micron single mode
LC Duplex
FC0407
OSA-Express4S 10 GbE EN
SR
50 and 62.5 micron multimode
LC Duplex
Feature Code
Description
Connector Type
Not available.
ETR Port
N/A
Table 24. ETR Connector
14.No additional clarification
15.In an installation comprised of more than one Logical Channel Subsystem,
there will more than likely be multiple occurrences of the same CHPID
number. It is extremely important that the labels on cables reflect the PCHID
number on the machine where the cable will be plugged.
16.No additional clarification
17.No additional clarification.
18.Refer to the appendix in SAPR guide to determine those activities provided as
part of the machine installation and those items that may require a services
contract. Significant cabling work is required for new and upgrading systems.
For upgrading systems, work is needed to plan, unplug, relabel, and relocate
the existing cables to the correct tile floor cutouts. If IBM is going to perform
this work, a service contract will be required.
For Site Planning Services (water cooling help for example), see
http://www-935.ibm.com/services/us/index.wss/offering/its/a1000240 or
http://www-935.ibm.com/services/us/index.wss/itservice/igs/a1026000.
19.Top Exit I/O adds 6 inches to both sides of the machine and approximately 95
pounds (43.1 kg) to the weight. Refer to z114 IMPP GC28-6907 Chapter 8 in
Resource Link.
5.5.5 Non-Raised Floor Requirements
20.If the z114 has been ordered to be installed on a raised floor, installation on a
non-raised floor environment may be in violation of local codes and
requirements and is absolutely prohibited.
Top Exit I/O & Bottom Exit Power or Bottom Exit I/O & Top Exit Power Are not orderable or supported
Bottom Exit I/O and Bottom Exit Power - These FC's are Ordered
a) Order FC7998 - Includes a modified EMC skirt. Loose torroids for the Input
Power, HMC LAN pigtails with built in torroids, OSA Copper (1000BaseT
OSAE2/3/4S) with one foot long pigtails with built in torroids
b) Order FC7921 - (Normal Side Covers (default))
c) When both FC7998 and FC7921 are both selected, eConfig forces the
user to order one of four 14 foot power cord options (8983, 8987, 8990 or
8966)
172
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Top Exit I/O and Top Exit Power - These FC's are Ordered :
a) Order FC7998 - The unique Top Exit Power cords (below item c) are all
built with a molded torroid.
b) Order FC 7920 - (Top Exit I/O) - Includes a pair of chimneys that replace
the normal side cover (FC 7921). FC7920 adds 12 inches to the machine's
width. The I/O chimneys for the z114 eliminate the need for any loose piece
chokes for the OSA Copper cables or the HMC LAN cables.
c) When FC7998 and FC7920 are both selected, eConfig forces the use to
order one of four 6 foot power cord options (8969, 8975, 8971, 8973)
5.5.6 Power
21.Refer to IMPP GC28-6907 Chapter 5 Tables 3 and 4. The number of
processor drawers and the number of I/O drawers or I/O cages determines the
point where balanced power and three phase input power are required.
22.If the z114 was ordered with DC Power, be aware of the following:
The nominal DC voltage range required from your DC generator is
380VDC-520VDC, but should not exceed 550VDC.
The power line cords should not be removed without first switching the EPO
switch to the Off (down) position. In the case of a DC source, the only
permissible means of removing power is to turn off the wall breakers as the
line cord plug is not rated for source current interruption and significant
arc/flash hazard could occur if the cords are removed under power.
FYI: Power can be MES’ed on an installed z114 (AC to DC or DC to AC). An
outage is required.
23.No additional information.
24.Refer to the appendix of the manual Installation Manual for Physical
Planning GC28-6907 for detailed information. The z114 models are designed
with a fully redundant power system.
Each z114 has two line cords attached to two input ports which, in turn, power
a pair of fully redundant power distribution systems within the computer. To
take full advantage of the redundancy/reliability that is built into the computer
system, the server must be powered from two distribution panels.
25.No additional clarification.
26.No additional clarification
27.IBM continues to strongly recommend the use of a metal backbox with our line
cords using IEC-309 plugs. Although in-line connectors and nonmetallic
backboxes are available and compatible, they are not recommended. These
recommendations are based on the metal backbox providing:
• An added level of protection against a miswired phase and ground reversal
• In some cases, a metal backbox may be better for EMI mitigation
Note: Customers may choose not to use a metal backbox. In this case,
local codes should be checked for specific requirements.
Chapter 5. Must-Read Information
173
Copyright 2011 IBM Corporation. All rights reserved.
• Refer to the “Physical Site Planning” section of the SAPR guide for
additional information.
28.No additional clarification.
5.5.7 Cooling
29.No additional clarification
5.5.8 Floor Space
30.No additional clarification.
31.No additional clarification
32.No additional clarification
5.5.9 Hardware Management Console
33.If the new Hardware Management Console is going to replace an existing unit,
the physical form factor (physical size) may be different. Refer to the IMPP
manual for the specifications of the new Hardware Management Console
(hardware unit and display).
34.A power outlet is required for the system unit and display.
35.This is important in sites where the Hardware Management Console to
processor LAN uses a customer LAN not dedicated to the Hardware
Management Console/Processor.
Note: It is important that the Hardware Management Console LAN be isolated
from any LAN which may be subject to virus infections or other intrusions. It
may be that the Hardware Management Console will not be infected by a virus
but other systems on the same LAN could drastically disrupt the LAN
functioning should they become infected.
36.The HMC/SE LANs should be capable of being quickly isolated from the
customer’s intranet in the event of problems. Refer to the IMPP manual for
further information and guidance.
37.Two ensemble HMCs are required for redundancy. One is primary and the
other is the alternate. The alternate should not be used unless a take over has
been performed.
Both ensemble HMCs must be in the same customer-assigned subnet to allow
swap of IP addresses during fail over. Also, both HMCs need equivalent
network accessibility to all systems to be managed. The pair require network
connectivity to each other to allow coordination and data replication. See
SG27-2608, Ensemble Planning and Configuration Guide.
38.Refer to GC27-2608 - zEnterprise Ensemble Planning and Configuration
Guide.
While it is true that the Ensemble created by the SSR can be deleted if not
needed immediately, it is wise to keep the ensemble intact. If an Alternate
HMC has been set up and used as an ordinary HMC, some work will have to
be done on it to remove certain object definitions and change certain settings
before that HMC can be used again as an Alternate.
With an alternate, there is a better backup than just the "backup critical data"
function. The primary HMC is dynamically keeping the alternate HMC
174
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
synchronized. So, if the primary fails, you just have to reboot the alternate and
you now have primary again. Otherwise, you would have to reload from a
backup set and then manually make changes.
Note that the ensemble name can be changed without a disruption.
5.5.10 Telephone and Remote Support Service
39.No additional clarification
40.Refer to HMC Guide and the HMC online books application for instructions on
setting up the interface.
41.No additional clarification
5.5.11 Machine Arrival
42.The Installation Manual for Physical Planning should be reviewed to ensure
that the environmental specifications associated with the z114 are satisfied.
43.Account Team should not assume that special arrangements are automatic.
44.No additional clarification
45.No additional clarification
46.No additional clarification
47.Refer to the Installation Physical Planning Manual for specifications.
48.For initial shipments of IBM systems that exceed the weight and/or height
requirements listed in the checklist, IBM pays the shipper to place the
equipment in the "install location." ("Install location" means the intended, final
installation location within the room where the equipment is to be installed in
the client's site.) In anticipation of the delivery, the client should have the
install location prepared so that professional movers can deliver the
equipment to the intended, final install location.
If this is not possible at the time of delivery, the client must make
arrangements to have professional movers or riggers return to finish the
transportation at a later date. IBM authorized service personnel will provide
only minimal frame repositioning of a few feet involving large, heavy systems
and frames. This repositioning must be within the same room where the
equipment is to be installed and only to the degree necessary to enable them
to provide required service actions (i.e., connection / set-up of the equipment
or diagnosis / repair).
In the event large, heavy systems or frames are to be relocated or rearranged,
even if the relocation or rearrangement is within the same room, the customer
is responsible for contracting professional movers for the movement, except in
circumstances where IBM contractually agreed to accept the responsibility to
arrange for the professional movers to move the large, heavy equipment.
For systems or frames and related equipment not considered large and heavy,
the mover is contracted for “inside delivery” at the customer location. "Inside
delivery" means that the mover is obligated only to deliver the machine inside
the client account, not to a specific location within the account. The client is
responsible to have the equipment moved to within a few feet of the install
Chapter 5. Must-Read Information
175
Copyright 2011 IBM Corporation. All rights reserved.
location. Again, the SSR will perform only minimal frame repositioning within
the computer room to perform required service actions.
5.5.12 Other
49.FC0033 Service Docs Optional Print
Declining this feature will result in the following guides to not be shipped in
paper format. The guides however continue to be available, and printable,
from the documentation DVD that is shipped with every machine
• Service Guide
• Install Guide
• Safety inspection guide
Rules on usage:
• Do not de-select the hard copy doc if this is the first machine at this
location (Same address, same building and same floor)
• Allow de-selection of subsequent copies if multiple machines are
ordered/shipped in the same timeframe.
• Do not de-select the hard copy doc at this location if this is a "dark
account" (raised floor that does not allow laptops and/or media inside)
50.A upgrade from an earlier generation processor to a z114 will be a frame roll.
Ensure that arrangements have been made to return the resulting frames from
the upgrade.
51.Some customer shops have very restrictive locations for disposing of trash. Of
particular interest are customer sites who have construction underway
wherein a contractor pays for trash bins associated with the construction
effort.
176
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.6 MR-System Management Plans
5.6.1 Problem Management
1. No additional clarification
2. By selecting “Report a Problem” from the HMC Console Actions, you can
choose to submit a PMV.
The new View PMV Records task is used to obtain Problem Management
Viewable (PMV) records issued to the IBM Service Support System (Retain)
for the Hardware Management Console or selected servers (CPCs). These
problems are typically sent to the IBM Service Support System where errors
are not recorded by the console. A PMV record is initially created from the
Report a Problem task via a new option. The customer is able to view and edit
the PMV records on the console and have the ability for an interactive dialog
with an IBM service representative.
5.6.2 Service and EC Updates
3. It is important that customer have plans in place to stay current with the driver
and MCL levels available for the machine so as not to end up in an
unsupported state.
4. Whenever a new driver level is released, the then current driver will be
supported for a period of six months. During this period, the level of support
will decrease in stages for the replaced Driver. With enhanced driver
maintenance, there will be the ability to concurrently upgrade to the newest
driver level at certain points over time.
5. It is intended that MCL patches be concurrent, however it is still possible that
some maintenance will require some channels to be configured off/on. It is
intended that all driver upgrades will be concurrent.
Chapter 5. Must-Read Information
177
Copyright 2011 IBM Corporation. All rights reserved.
5.6.3 Operations
6. The HMC provides the ability to synchronize all Hardware Management
Consoles used in an environment. Refer to the Hardware Management Guide
for information on setting up automatic synchronization of Hardware
Management Consoles used.
1) Hardware Management Console Operations Guide · Version 2.11.1
SC28-6905 on Resource Link.
2) For HMC V2.11.0 (D86) Enhancements (from z10), Refer to Techdoc
Presentation PRS4582 at
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4582
3) For HMC V2.11.1 (D93) Enhancements, Refer to Techdoc Presentation
PRS4707 at
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4707
5.6.4 Availability Management
7. The intent of this item is to make sure that the availability of a system being
replaced is documented so as to form a basis for measuring the availability of
the new system.
5.6.5 Security
8. The Hardware Management Console now provides an option for stricter
password rules. The administrator (using the ACSADMIN userid) is required to
activate these new features.
9. System z already provided all of the necessary security controls and audit
trails, but there is no easy way for our users to be able to quickly view and/or
offload all of this information.
The z114 has the following enhancements.
• A new Audit & Log Management task was added to the access
administrator to allow for audit reports to be generated, viewed, saved, and
offloaded.
• The Customize Scheduled Operations task was enhanced to allow for
scheduling of audit report generation, saving, and offloading.
• The Monitor System Events task was enhanced to allow for Security Logs
to result in e-mail notifications using the same type of filters and rules that
are used for both hardware and operating system messages.
• The Password Profiles task was altered to allow for the removal of
pre-defined password rules by the access administrator.
• The SNMP and CIM APIs was enhanced to allow user ID audit reports to
be generated and retrieved.
10.See
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=SA&subtype=WH&
appname=STGE_ZS_ZS_USEN&htmlfid=ZSW03167USEN&attachment=ZS
W03167USEN.PDF.
This paper is provided for both IBM and IBM customers who have an interest
178
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
in the IBM zEnterprise™ System “Network Security” topic. It is assumed that
readers already have a basic background in both the zEnterprise System and
fundamental Network Security concepts. The primary purpose of this paper is
to describe why, for many customers, traditional network firewalls will not be
required for their network traffic associated with multi-tier application
workloads within a zEnterprise Ensemble.
5.6.6 Customer/IBM Meetings
11.No additional clarification
Chapter 5. Must-Read Information
179
Copyright 2011 IBM Corporation. All rights reserved.
5.7 MR-RSF and Internet Remote Support
5.7.1 RSF
1. No additional clarification
2. Ensure that the correct customer call back number and contacts and any other
pertinent customer information have been listed and verified in the RSF
customization data.
5.7.2 Internet
3. Remote support connections for service are initiated by the customer machine
(HMC) to IBM Retain. With customer consent, IBM may connect to the
System. If allowed, an RSF connection can be made via a phone connection
or an internet connection. If it is via a phone connection, the protocol used is
PPP and TCPIP and data transfer is done using SSL encryption. Phone
connections are made using ATT as the global service provider. Provision is
made for the use of local phone connections where available. ATT system is
designed to limit access for these connections to a restricted set of destination
IP addresses. ATT system is designed so that general internet access is not
available through these connections.
Internet Option (RECOMMENDED):
If it is via an internet connection, the protocol used is TCPIP and data transfer
is done using SSL encryption. Internet connections are assumed to go through
a customer firewall system before entering the global internet.
On either style connection, the IBM Retain system is designed to validate that
the incoming requesting system is known and authorized.
See
https://www.ibm.com/servers/resourcelink/lib03011.nsf/pages/zIntegratingHm
cBroadbandRsfSSSIPAddresses?OpenDocument
For implementation tips and instructions, see
http://nascpok.pok.ibm.com/ma-alert/ma120507B.pdf
On ResourceLink, in the Library section, see
• Z121-0244, Broadband Remote Support Facility (RSF)
• SC28-6880, Integrating the HMC's Broadband RSF on your Enterprise
Firewall
The Hardware Management Console has an internal firewall that blocks all
access to the Internet itself, opening only those areas needed by the console
functions. IBM recommends an external customer firewall system be
configured between the Hardware Management Console and the global
Internet, as an additional protection when Internet connectivity is configured.
SSL Support:
A customer SSL proxy server can forward requests to the Internet from the
HMC, providing an added layer of security. Potential additional advantages
include the possibilities of logging and audit facilities using the proxy.
180
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
To forward SSL sockets, the proxy server must support the basic proxy header
functions (as described in RFC #2616) and the CONNECT method. Optionally,
basic proxy authentication (RFC #2617) may be configured so that the HMC
authenticates before attempting to forward sockets through the proxy server.
Server Address List
Whether you are using a direct connection (the HMC only) or an indirect
connection (with a proxy server) for Internet access, the HMC (V2.11.0)
utilizes the following IP addresses and port 443 for all Internet activity:
• For connections with IPV4:
• 129.42.26.224
• 129.42.34.224
• 129.42.42.224
• For connections with IPV6:
• 2620:0:6C0:1::1000
• 2620:0:6C1:1::1000
• 2620:0:6C2:1::1000
LDAP Support:
Lightweight Directory Access Protocol (LDAP) support for Hardware
Management Console (HMC) user authentication allows a user to configure
their HMCs to use a LDAP server to perform user ID and password
authentication at logon time. This function allows the use of the current user
ID and password policy for HMC user IDs and passwords, and provides one
centralized user ID and password control mechanism to help address this
requirement which exists in many users' corporate security guidelines.
The user ID is defined on the HMC along with the roles to be given to the user
ID. HMC settings related to the userid will continue to reside on the HMC, and
the LDAP directory will be used to authenticate the user, thus eliminating the
need to store the user ID's password locally. SSL and non-SSL connections to
the LDAP server are supported.
This function is designed to more easily assist system administrators in the
creation of HMC user IDs matching existing company user names. This can
help reduce the need to create and distribute passwords by leveraging
operations that may already be managed by the corporate control procedures.
Refer to product publications for further information.
Chapter 5. Must-Read Information
181
Copyright 2011 IBM Corporation. All rights reserved.
5.8 MR-Resources and Responsibilities
5.8.1 General
1. No additional clarification
5.8.2 Agreement on Responsibilities
2. It is extremely important that all aspects and responsibilities of the installation
be defined and agreed to by both the customer and IBM. It is strongly
encouraged that customers make use of the IBM Cabling Services. Refer to
the appendix of this SAPR for further information.
182
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.9 MR-Service Offerings
5.9.1 General
1. Examples of some of the available services:
a. Rapid Workload Optimization Assessment
This interactive workshop based service will evaluate the feasibility and
measure technical and business impact of implementing a zEnterprise
solution. It is based on a rapid method to help clients optimize their workloads
from business and technical perspectives. The analysis is based on the
client's own environment. As part of this service we can work with clients to
select workloads that may benefit from zEnterprise.
b. IBM Smart Analytics Optimizer Enablement Services
This offering provides services to configure the hardware components
necessary to enable a basic functional IBM Smart Analytics Optimizer
environment and IBM System Storage unit. In addition, this offering assists
current DB2 for z/OS clients with the planning and installation activities for the
integration of the optimizer into their data center. A test data mart will be
provided to demonstrate functionalities. Customers will be provided with a
high performance system that is ready to be loaded with the data for their
queries. This service is 3-4 weeks long.
c. zEnterprise Ensemble Enablement JumpStart Assistance for zBX Blades
This service is targeted for implementations involving IBM Blades and is
designed to help accelerate the implementation of an Ensemble. The service
will set up the z/OS and zBX infrastructure, use a test application to show the
functionality of the Ensemble environment, and provide education to the client.
Focus of this offering is on the “Manage” functionality for Unified Resource
Manager. Additional services for the “Automate” functionality, including some
advanced Unified Resource Manager features, can be provided through the
zEnterprise Ensemble Enablement for zBX Blades offering. This service is 3-4
weeks long.
d. zEnterprise Ensemble Enablement JumpStart Assistance for z/VM
This service is targeted for implementations that will use the Unified Resource
Manager to manage Linux virtual servers under the z/VM Hypervisor. The
service will set up the z/VM and Unified Resource Manager infrastructure, use
a test application to show the functionality of the Ensemble environment, and
provide education to the client. Focus of this offering is on the “Manage”
functionality for Unified Resource Manager. This service is 3-4 weeks long.
e. zEnterprise Ensemble Enablement for zBX Blades
This is a comprehensive service offering designed to accelerate the
implementation of an Ensemble with a functional application test environment
selected by the client. Services are provided to implement the Ensemble with
a Test Workload Environment spanning the zCEC and zBX blades. The virtual
resources and virtual servers will be defined on the blades. A blade operating
system will be installed and a test application environment established. The
required z/OS, z/VM, zBX Blade, and Unified Resource Manager skills will be
provided to enable the Ensemble. The migration to this environment can be a
complex task requiring an extended implementation period to activate the
technology. The Ensemble Enablement offering also provides project
Chapter 5. Must-Read Information
183
Copyright 2011 IBM Corporation. All rights reserved.
management and Unified Resource Manager skills transfer to operations and
systems administration personnel. Additional services to assist in the
migration to production can also be provided on a customized basis. This
Ensemble Enablement offering is a more comprehensive offering, covering all
aspects of the implementation process. While this service provides the
customer the optimal implementation experience, it is priced higher than the
JumpStart services. This service is 9 weeks long.
f. Server Time Protocol Implementation Services
Get more details about the available services by contacting one of the STG
Lab Services opportunity managers in the US:
George Ng/Poughkeepsie/IBM@IBMUS; phone: 845-705-8439, See US
announcement letter 609-021.
g. z/VM Single System Image and Live Guest Relocation
This service is intended to help clients plan for and implement a z/VM
Single System Image (SSI) cluster. It is ideal for clients who want to take
advantage of the z/VM guest mobility solution, Live Guest Relocation
(LGR), in order to increase the availability of their Linux on System z
servers.
This service will:
- Educate you about z/VM clusters and their capabilities
- Provide cluster planning and deployment assistance
- Provide operational guidance and recommendations
- Optionally provide migration assistance for users of IBM's existing
Cross-System Extensions technology
- Demonstrate the technology in your own environment.
h. IBM Implementation Services for System z
Global Technology Services, "IBM Implementation Services for System z zBX and Unified Resource Manager offering (6948-L66)" will be enhanced
to support Linux on System x with the zEnterprise BladeCenter Extension
(zBX) infrastructure.
The offering will assist you with the planning, implementation and
deployment of the IBM zEnterprise BladeCenter Extension (zBX) and
Unified Resource Manager infrastructure, enabling you to deploy on an
integrated platform of System z, POWER7, and System x technologies.
This service will help you to accelerate the adoption of IBM zEnterprise
technology and realize the value faster.
For more information about the offering, please refer to:
www.ibm.com/services/us/en/it-services/
server-product-services-for-system-z.html.
2. This question is intended to identify any other services that have been
included as part of the installation activities. If so, the account team should
ensure the scope of the services are clear to the customer and that plans are
in place to fully utilize any services offered.
184
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.10 MR-Installation Planning and Documentation
5.10.1 Teams
1. No additional clarification
2. No additional clarification
5.10.2 Plan Documentation
3. No additional clarification
4. No additional clarification
5.10.3 Systems Assurance Confirmation Form
5. A member of the IBM Account Team is responsible for submission of the SA
Confirmation Form on ResourceLink. The online form can be found online at
ResourceLink (http://www.ibm.com/servers/resourcelink). From the left
margin, Click Planning. Then select the z114 found under "Systems
Assurance" followed by Systems Assurance Review Confirmation Form.
Chapter 5. Must-Read Information
185
Copyright 2011 IBM Corporation. All rights reserved.
5.11 MR-Business Partners
5.11.1 Responsibilities
1. No additional clarification
186
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
5.12 MR-zIIP Considerations
5.12.1 General
1. It is critical that the IBM Account Team completely understand the customer's
planned usage and implementation of the zIIP processor. It is highly
recommended that the review start off with an overview of the project by the
customer. Although this review will focus on the processor installation, it is
important to have an overall understanding of the customer's enterprise in
terms of mission and goals.
2. Customers and IBM Account Team members are strongly encouraged to
review the publications that may be available at the following web site:
www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs
www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs (IBM Intranet)
Of particular interest are the following:
Flash10477 z/OS Positioning for the z9-EC and z9-BC Servers
TD103050 The IBM z9 Integrated Information Processor (zIIP) and Its Effect
on PeopleSoft Enterprise Application Architecture
FQ115394 Can the IBM System z9 Integrated Information Processors (zIIP)
be used with SAP?
PRS2123 WSC Experiences with the zIIP Processor
PRS2220 Utilizing the zIIP Processor for Data Warehousing and BI
Applications
WP100836 IBM System z9™ zIIP Measurements: SAP® OLTP, BI Batch, SAP
BW Query, and DB2 Utility Workloads
TD103516 zIIP and zAAP Software Update
TD105581 z/OS Positioning Software for the zEnterprise (z196) Server
TD103548 Capacity Planning for zIIP and zAAP
WP100988 Capacity Planning for zIIP-Assisted IPSec
PRS2745 - WSC Experiences with IPSec on the zIIP Processor
zAAPs and zIIPs: Increasing the Strategic Value of System Z which can be
found at web address:
http://domino.watson.ibm.com/tchjr/journalindex.nsf/c469af92ea9eceac85256
bd50048567c/df3acf446a88551a8525728900768743?OpenDocument
There are numerous other documents on the Techdocs website that can be
found by doing a search using the keyword zIIP on the homepage. Some of
these document experiences with specific workloads like Siebel, PeopleSoft
and SAP. A quick search of this site should uncover all documents that may
Chapter 5. Must-Read Information
187
Copyright 2011 IBM Corporation. All rights reserved.
apply to your customer. Some of these are listed in the Must Reads of this
SAPR Guide.
3. No further clarification
4. One 24 hour test is allowed for On/Off CoD for zIIPs. However, on the z10,
there are no Administrative tests allowed. These Administrative tests are
supported on the z114 and were supported on 2094 and 2096 Processors
which enabled customers to order 'zero' quantity features and go through the
entire order, download and activate steps.
With the z10 BC and z10 EC, the administrative On/Off CoD test was
eliminated, but reinstated on the z114.
5. No further clarification.
6. No further clarification.
7. Customers who are using Stored Procedures and/or UDFs cannot use the
RMF sizing methodology (Method 1), as shown below. To estimate what may
be off-loaded to the zIIP but must use SMF 101 methodology (Method 2).
Method #1: Analyze RMF type 70 and 72 records
• First cut to determine total amount of DRDA work running in a partition
• Minimal amount of data
• Requires good granularity of DRDA work in WLM service classes or report
classes
• Can provide complete analysis if customer is NOT using stored procedures
or UDF (User Defined Function) or SNA
Note: This method should be used for all scenarios.
Issues to be aware of with RMF (Method #1)
Be sure that the Service classes are right. (Includes all DDF and nothing else.)
• Check by reviewing RMF Workload Activity
Note: If Service Classes are not granular enough, sometimes can use Report
Classes.
• Two approaches in CP2KEXTR:
a. Remove a service class and add corresponding reporting classes. Remove
"The Rest" service class. Preserves Capture Ratio.
b. Add reporting classes you are interested in. Resulting EDF ONLY valid in
zIIP Analysis application which assumes a capture ratio of 1. WARNING:
Other parts of zCP3000 give invalid results since capture ratio is now wrong
and you are double-counting work.
Method #2: Analyze SMF 101 (DB2 accounting) records
• Required if customer makes extensive use of Stored Procedures or UDF
• Can use a significant amount of data
• IBM provides a tool which can be run on the customer machine to process
the data and create a small file to be sent to IBM for further analysis
• DB2 for z/OS DRDA zIIP Redirect Data Collector
• Available from Techline
• Results of this tool are integrated with the EDF Model in zCP3000.
• Can process DB2 V7 or V8 data
• Results can provide more accurate estimates with V8 data
188
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Issues to be aware of with Data Collector (Method #2)
• Requires the processing a lot of data. More than it makes sense to ask the
customer to FTP.
• Plan on running the data Collection Tool on Customer system.
• Ideally you are processing the same date/times as your Extract file.
• You MUST use the same DURATION as you did for the EDF Extract.
• Times and occurrences need to be reviewed (Times are in GMT).
• Missing hours and low numbers of occurrences may mean long running work
is going on and data may span intervals.
• Long running tasks can cause problems with this data
• If you have multiple CSV files, note that the Union of the files will be
presented. Be sure you have data from all subsystems in the times that you
are presenting.
Method 2 uses DB2 SMF 101 accounting records in addition, to estimate DB2
DRDA zIIP re-direct for environments with Stored Procedures and UDFs.
Method 2 uses a zIIP Estimator Data Collector tool that runs in the customer
environment and collects the needed accounting data and creates a spread
sheet file in CSV format. The CSV spread sheet file will be processed at an
IBM site and merged with the corresponding RMF data intervals for all the
LPARs in the CEC and shows the DRDA zIIP re-direct potential for the
customer workload as shown in the chart below.
Chapter 5. Must-Read Information
189
Copyright 2011 IBM Corporation. All rights reserved.
8. No further clarification.
9. No further clarification.
10.Please see in the TechDocs Database White Paper - WP101642 Planning
Considerations for Running zAAP Work on zIIPs.
11.This XML enhancement further benefits eligible work by directing the full
amount of the z/OS XML System Services processing to zIIPs when it is
utilized as part of any zIIP eligible workload (like DRDA). Specifically, 100% of
z/OS XML System Services parsing that is executed in SRB mode from
zIIP-eligible enclaves will be redirected to the zIIP and 100% of z/OS XML
work operating in TCB Mode will be eligible to run on a zAAP. And now with
zAAP on zIIP capability, 100% of both types of work can be redirected to zIIPs.
12.No further clarification.
5.12.2 Performance
13.It is extremely important that the appropriate capacity planning tools have
been used to determine the benefits from usage of a zIIP processor. Rough
estimates using MIPs or equivalent values should not be acceptable. Also,
due to the n-way effect, the adding of zIIP processors can impact the overall
190
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
system performance. An appropriate sizing tool such as zTPM, zCP3000 or
zPCR should be used at a minimum to identify the potential impact.
14.Account team should understand what metrics the customer plans to use to
evaluate the performance of the zIIP to ensure they are compatible with the
sizing tools used and that meaningful data will be obtained.
15.No further clarification.
16.Refer to the appropriate z/OS release of the RMF User's Guide and RMF
Report Analysis manuals for detailed information on controlling RMF reporting
for the zIIP Processor and the MVS System Management Facilities (SMF)
manual for the changes to SMF to support the zIIP processor.
5.12.3 Education and Training
17.The following web site should be reviewed for any education that may be
required to support System z processors:
• http://www.ibm.com/services/learning
There is also planning information at the following site:
• http://www.ibm.com/systems/z
Once at the site click the down arrow under MAINFRAME TOPICS and
select SPECIALTY ENGINES and then click the arrow on the right. This will
bring you to the Specialty Engine Web Page.
18.PRS2123 - 'WSC Experiences with the zIIP Processor'. This document
contains a zIIP Overview, Tuning Options, RMF Updated Reports and
Measurements of zIIP effectiveness with DRDA and DB2 Utilities.
• TD103516 - Specialty Engines zIIP and zAAP Software Update. This
document provides an overview of the zIIP Processor, the software exploiters
for zIIP, how to estimate the amount of work that will be redirected to zIIP and
the zIIP Software Requirements.
• PRS2220 - 'Utilizing zIIP Processors for Data Warehousing and BI
Applications which provide System z value to DW/BI Applications'. PRS2220
is only on the internal TechDocs website:
• http://w3.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs
• WP100836 - 'IBM System z9™ zIIP Measurements: SAP® OLTP, BI Batch,
SAP BW Query, and DB2 Utility Workloads'. This paper describes various
software workloads and the measurements done in IBM's Laboratories
utilizing z9 zIIP hardware and software. While it is z9 specific, it is still
applicable to the z114 and z10.
19.The three whitepapers are:
• Whitepaper showing results of XML document inserts and XML table-loads.
• WP101088 DB2 V9 and z/OS XML System Services Synergy
• Whitepaper updates on XML mixed transaction workload, additional
application tuning and performance, and DB2 V9 accounting record updates
(May and December 2008).
• WP101227 DB2 V9 and z/OS XML System Services Synergy Update
• WP101387 DB2 9 and z/OS XML System Services synergy for distributed
workloads
Chapter 5. Must-Read Information
191
Copyright 2011 IBM Corporation. All rights reserved.
5.12.4 Sizing the zIIP Requirement
20.No Additional Clarification
21.No Additional Clarification
22.This deliverable will provide the same performance information in RMF for the
zIIP that is also available for the zAAP. If a zIIP is not currently installed, then
by utilizing the PROJECTCPU parameter, in IEAOPTxx member of
SYS1.PARMLIB, with the YES option, RMF will record all zIIP eligible work.
See the General Information Section RMF Reporting Using the Web
Deliverable for more information.
23.No Additional Clarification.
5.12.5 Software
24.Information on obtaining the PSP buckets needed to support the software
required for the zIIP processors can be located in Flash10477 (Positioning
Software for the z9 EC and z9 BC Servers) and TD103516 (zIIP and zAAP
Software Update) on the Techdocs website. There are sections in both of
these documents that provide information on obtaining all the required
maintenance that is necessary to support zIIP processors. Reviewing the PSP
buckets should be done on a regular basis.
25.For z/OS V1.6 and V1.7 and z/OSe V1.6 and V1.7: If the customer will exploit
the IBM System z9 Integrated Information Processor (zIIP), this requires the
"IBM System z9 Integrated Information Processor Support for z/OS and z/OSe
Web Deliverable, available on the z/OS downloads website, plus PTFs. This
Web deliverable contains FMID JBB77S9 for z/OS and z/OS.e V1.6, and FMID
JBB772S for z/OS and z/OS.e V1.7.
http://www.ibm.com/servers/eserver/zseries/zos/downloads/
Install the service identified in the program directory that comes with this Web
deliverable and the recommended service in the appropriate ZOSV1Rn
BCPZIIP PSP bucket. IBM DB2 UDB for z/OS V8 with PTFs, is also required
for exploitation for portions of eligible workloads. See Flash10477 on the
Techdocs website for more information. For z/OS and z/OS.e V1.8, this Web
deliverable is not needed.
The customer and IBM Account team should clearly understand that only
portions of certain DB2 workloads are eligible to exploit the zIIP processor and
will actually take advantage of it. The actual amount of work that will be
redirected to the zIIP can be determined by using the appropriate sizing tools
that are available from IBM.
26.No further clarification.
27.No further clarification.
28.White Paper WP100988 provides detailed information enabling IPSec, and
capacity planning methodologies for zIIP IPSecurity as well as performance
information. This paper is a must-read if zIIP Assisted IPSec will be
implemented.
29.There is no need for special software setup to use zIIPs on z/OS 1.6 with the
Web Deliverable. There are parameters which can be defined in IEAOPTxx to
192
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
control how the operating system will dispatch zIIP and zAAP eligible work.
These parameters have changed several times since these specialty engines
have been introduced and also with the release of z/OS that you are running.
For the latest information on which parameters and which options are
available, check out the following information.
• APARs: OA14131, zIIP Web Deliverable documentation, OA20045, and
OA21993
5.12.6 ISV Software Support
30.No further clarification
31.The output of the D M=CPU display identifies any specialty processors that
may be on the machine. Refer to the commands publications for further
information.
5.12.7 Installation Plans
32.Ensure that the plan includes provisions for post-implementation production
fall back to a configuration without the zIIP
33.Driver Exception Letters can be obtained from ResourceLink
• www.ibm.com/servers/resourcelink
This letter can be found under the menu "Fixes".
5.12.8 Activation Profiles
34.Refer to the following example of the output from the display command.
Chapter 5. Must-Read Information
193
Copyright 2011 IBM Corporation. All rights reserved.
z9 Display CPU information with zIIP
D M=CPU
IEE174I 10.37.03 DISPLAY
PROCESSOR STATUS
ID CPU
SERIAL
00 +
02B29E2094
01 +
02B29E2094
02 +A
02B29E2094
03 +I
02B29E2094
CPC ND = 002094.S28.IBM.02.00000004B29E
CPC SI = 2094.724.IBM.02.000000000004B29E
CPC ID = 00
CPC NAME = SYSS01
LP NAME = STLABH2
LP ID = 2
CSS ID = 0
MIF ID = 2
+ ONLINE
- OFFLINE
N NOT AVAILABLE
A
I
. DOES NOT EXIST
W WLM-MANAGED
APPLICATION ASSIST PROCESSOR (zAAP)
INTEGRATED INFORMATION PROCESSOR (zIIP)
Figure 2. Verifying zIIP processors
35.Make sure the processing weights for each LPAR using specialty processors
are understood. Shared IFL, ICF, zAAP and zIIP processors are now managed
by PR/SM in separate pools. Ensure that the processing weights for all LPARs
utilizing IFLs, zAAPs, zIIPs and ICFs are reviewed especially if a new server is
being installed which is replacing an older server or where all specialty
engines were in the same shared pool.
36.Reserved zIIPs will be defined as appropriate in each image profile that will
use additional zIIPs following a concurrent upgrade. Careful consideration
should be given to the total number of initial and reserved CPs and zIIPs
allocated to a partition to avoid an unwanted IPL.
5.12.9 IRD Considerations
37.No further clarification
5.12.10 Systems Assurance Confirmation Form
38.Any MES order that involves the addition of only a zIIP requires that a
Systems Assurance be conducted. However, there is no requirement for an
IBM representative to submit the Systems Assurance Confirmation form on
ResourceLink.
194
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 6. Pre-Sales Checklists
Note 1: The following checklist items are intended to be brief and identify areas that
need to be addressed as part of the pre-sale effort. Further details, if required, will
be contained in the pre-sales Must Read Section of this SAPR document and within
the SAPR guide main sections.
6.1 Customer Expectations
Table 25. Customer Expectations
Activity
Status
Due Date
Owner
Comments
6.1.1 General
1
Customer’s planned implementation and
use of the z114 Processor is understood.
2
If this is a solution that includes Unified
Resource Manager, FC0025, you must
perform a pre-sales review using the
SA10-018 checklist.
Do this, even if there is no zBX.
3
If configured with eConfig, the machine
configuration has been reviewed to
ensure that all features required by the
customer have been correctly ordered.
See Must Read.
4
For large installations or migrations, IBM
Account Team has considered the
benefits of involving the zSeries Project
Office.
6.1.2 Performance
5
Appropriate sizing tools and
methodologies have been used to
determine the required processor model.
IBM internal URL for zPCR:
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/PRS689
IBM internal URL for zCP3000:
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/PRS1772
Partner World URL for zPCR:
http://partners.boulder.ibm.com/src/atsm
astr.nsf/WebIndex/PRS1796
Partner World URL for zCP3000:
http://partners.boulder.ibm.com/src/atsm
astr.nsf/WebIndex/PRS1865.
Chapter 6. Pre-Sales Checklists
195
Copyright 2011 IBM Corporation. All rights reserved.
Activity
6
Status
Due Date
Use the IBM® zEnterprise™
BladeCenter® Extension (zBX) SAPR
Guide (SA10-006) for sizing information
of the 2458-002.
6.1.3 Acquisition and Contractual Considerations
7
Contractual requirements associated
with the processor acquisition are in
place and agreed to by the customer and
IBM.
8
Customer is aware and has planned for
additional charges that may be incurred
in the future after the z114 has been
initially installed.
See the Must Read section for more
information.
9
Customer is aware of the changes to the
pricing metric used to license middleware
running on Linux for System z and
distributed platforms. See the Must Read
section for further information.
10 If the installation of the z114 is ordered via
a System z Exchange Program (formerly
known as a hybrid offering) or other push
pull which will result in a new serial
number machine replacing an installed
machine, insure that the maintenance
contract for the machine being replaced
has been canceled if required.
11 If planning to use the Crypto Express3 to
exploit the Elliptical Curve Cryptography
(ECC) capability, there is an LIC license
addendum that must be read and
understood by the customer.
6.1.4 Capacity on Demand
12 Customer and IBM Account Team/IBM
Business Partner are in agreement on
the contractual requirements associated
with any Capacity on Demand offering
involved with this machine.
Note! Even if the On/Off CoD and CIU
features are on order, the features won’t
function if the appropriate contracts have
not be signed and processed by IBM.
6.1.5 Education and Training
13 Provisions have been made for customer
personnel to obtain training in the
definition, use, and function of the
processor and associated tools if
required.
196
SA11-002-02
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
6.2 Hardware Configuration
Table 26. Hardware Configuration
Activity
Status
Due Date
Owner
Comments
6.2.1 General
1
If ISC links or InfiniBand links are to be
connected cross site via DWDM, verify
that the DWDM supports the rated link
speeds.
2
If using DWDMs to extend channels,
determine if the DWDMs support
auto-negotiation if the channels are set
up to use that capability.
3
If DWDMs will be used for coupling links,
determine if the DWDMs are rated to
support Server Time Protocol.
Do NOT use DWDMs to transmit STP
information if the DWDM has not been
qualified to support STP.
4
Even if Crypto Express3 has not been
ordered, it is suggested to order (no
charge) FC3863 (CPACF).
Some ISV’s depend on CPACF.
6.2.2 Capacity on Demand
5
To limit the exposure to unexpected CoD
charges, the customer can now order
pre-paid On/Off Capacity on Demand
Tokens and bank them.
This may be an attractive alternative to
paying for temporary capacity after it’s
use.
See the MustRead for more details.
6.2.3 Devices and Controllers
6
All equipment that will connect to the
z114 (both IBM and OEM) has been
verified to be supported and at the correct
maintenance level for attachment.
Chapter 6. Pre-Sales Checklists
197
Copyright 2011 IBM Corporation. All rights reserved.
Activity
7
The FICON Express8S or FICON
Express8 supports an 8 Gbps link data
rate with autonegotiation to 2, 4 or 8
Gbps.
NOTE: 1 Gb devices can be connected to
directors and switches with 8Gb links if
they use 4Gb optics in the 8Gb blade
and/or a 4Gb blade in the director or
switch.
So the scenario would be, FICON
Express8S or FICON Express8
connected to an 8Gb director blade and
then the connection to the 1Gb device is
accomplished via a 4Gb director blade.
If the FICON Express8S or FICON
Express8 channel is routed through a
switch, it is important to read the z114
Exception Letter.
8
Is there an IBM 3590-A60 directly
attached (no FICON Director) to a FICON
Express4, FICON Express8, or FICON
Express8S? If so, read the related
MUSTREAD item.
6.2.4 Consoles
9
Provisions have been made for IPL
consoles for each operating system
image (OSA-ICC, 2074, 3174).
Note 1: If migrating OSA-ICC to an
OSA-Express3 1000Base-T, planning
must include the fact that this 4-port
feature has two ports per CHPID type.
See the OSA-ICC manual and
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/PRS3591.
Note 2: Additional OSA-Express3
1000Base-T features will be required if
Unified Resource Management FC0025
has been ordered.
Note 3: The 2074 is an ESCON device.
ESCON channels can't be spanned to
talk to LPARs in different logical channel
subsystems. An ESCON channel can
only be shared by the LPARs in one
LCSS or dedicated to one LPAR.
198
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
10 If using an IBM® zEnterprise™
BladeCenter® Extension (zBX) or the
IBM Unified Resource Manager on a
single CPC, the Primary-HMC and
Alternate-HMC have very strict
requirements.
6.2.5 Coupling Links
11 If PSIFB coupling links are to be used or
are being considered, a study has been
undertaken to analyze the performance
characteristics of PSIFB links and the
ability to support the intended workload
requirements.
12 If ordering HCA2-O or HCA3-O
InfiniBand coupling links, ensure you
have ordered enough ports to provide
you with physical card redundancy.
6.2.6 Server Time Protocol
13 Any z114 which contains a coupling link
channel will require the installation of
Server Time Protocol (FC1021). e-Config
will add FC1021 automatically.
Note 1: The z114 cannot be connected to
a 9037 Sysplex Timer.
Note 2: If the z114 will be in a Sysplex
with other machines, they are required to
have STP installed, enabled and
configured.
See the MustRead.
14 If implementing STP for the first time, an
STP Technical Delivery and Assessment
must be conducted - and the “STP
confirmation form” must be submitted on
ResourceLink.
6.2.7 Channel Configuration
15 If an upgrade, ensure that customer has
accounted for channel features not
supported on the z114. The configuration
should be reviewed for any deleted
channel types.
Chapter 6. Pre-Sales Checklists
199
Copyright 2011 IBM Corporation. All rights reserved.
Activity
16 Customer is aware that the FICON
Express4, FICON Express8S or FICON
Express8 features do not support FICON
converter channels (FCV).
Note: The FICON Express and FICON
Express2 are not supported on the z114.
See the PRIZM FICON converter
products at http://www.opticatech.com/ if
required.
17 For ESCON converter channels attached
to a 3745, it is recommended to split the
EP traffic out onto a separate 3745 CAL6
channel adapter from the 3745 channel
adapter(s) that will run NCP traffic.
Business as usual - the same item
applied to z10 and z9.
18 If FC0025, Unified Resource Manager, is
to be used on a single z114 without a
zBX, and if LPAR to LPAR
communications is required in a Unified
Resource Manager defined VLAN, the
customer must provide
a) Two 10 GbE OSA features
b) an LC Duplex cable that goes from
OSX to OSX CHPIDs.
The cable plugs into the two
OSA-Express4S or OSA-Express3 10
GbE features, which are required (but not
forced) by eConfig.
IBM has stopped recommending using
two LC Duplex loop back testers, also
known as wrap plugs.
Note: The IODF must be shared among
participating z/OS LPARs.
See the MustRead for additional
information.
6.2.8 Crypto
19 Customer is aware that some functions
on the z800/z900 (CCF based crypto) are
no longer supported.
20 If the customer plans to use a TKE
workstation, insure that it is the proper
feature and LIC level to support a z114
21 If the customer plans to use secure keys
as protected keys on the CPACF, a
Crypto Express3 is required.
200
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
6.3 Software Configuration
Table 27. Software Configuration
Activity
Status
Due Date
Owner
Comments
6.3.1 General
1
Only supported levels of Operating
Systems along with the required
maintenance will be run on the z114.
See the MustRead for details.
2
If the z114 will be used with an IBM®
zEnterprise™ BladeCenter® Extension
(zBX), use the 2458-002 SAPR Guide,
SA10-006.
6.3.2 CIU, CBU, On/Off Capacity on Demand
3
Impact on contractual requirements and
functioning of both IBM and ISV software
following an upgrade via CBU, CPE, or
On/Off Capacity on Demand to increase
processing power has been evaluated.
6.3.3 CFCC
4
Memory planning has taken into account
the structure size increases associated
with various CFCC level releases.
More storage is required for CFCC 17.
See the MustRead.
6.3.4 IBM and ISV Software Support
5
IBM and ISV vendor software licensed by
CPU serial number has been licensed for
the z114 CPC serial number.
6
For z114 in a plex, an agreement for
Advanced Workload License Charges
must be in effect if z/OS or z/TPF will run
on the z114. (Note: this excludes
customers who will remain on PSLC
pricing.) See the MustRead.
7
For z114 NOT in a plex, An agreement for
Advanced Entry Workload License
Charges must be in effect if z/OS or
z/TPF will run on the z114. (Note: this
excludes customers who will remain on
PSLC pricing.) See the MustRead.
Chapter 6. Pre-Sales Checklists
201
Copyright 2011 IBM Corporation. All rights reserved.
Activity
6.3.5 Crypto
8
If you use a User Defined Extension
(UDX) of the Common Cryptographic
Architecture (CCA), you should contact
your UDX provider (IBM) for an updated
version of the UDX before ordering a new
server or before migrating or activating
your UDX application.
6.3.6 Sysplex Considerations
9
Ensure that all processors within the
same sysplex as the z114 are no older
than a z10 or z9.
10 FYI z/VM 6.2 supports Single System Images
in a z/VM Cluster of up to four z/VM
systems, across CPCs (zEnterprise or
z10) or within one CPC.
This multisystem virtualization
technology allows the cluster members
appearing to be a single system.
With this technology, you can exploit Live
Guest Relocation, thus reducing the
effect of planned outages and provide for
load balancing.
6.3.7 Linux Considerations
11 The z114 officially supports Novell SUSE
SLES 10 and SLES 11 and Red Hat
RHEL 5. Some earlier release can be run,
but some supported functions are not
available.
SLES9 SP4 latest maintenance web
update and RHEL 4.8 have been tested
on z114. Please note that both
distributions are approaching end of life.
Please check with your distribution
partner for the exact dates and start
migration planning.
When upgrading from OSA-Express2
features to the multi-port
OSA-Express4S or OSA-Express3
features, be aware that these two
distributions (SLES9 SP4 and RHEL 4.8)
will detect port 0 only. Consolidation of
ports may prove difficult and you need to
plan accordingly.
202
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
12 Live Guest Relocation (LGR) provides
the capability for a running Linux virtual
machine to be moved without disruption
from one z/VM system to another within a
Single System Image (SSI).
The Unified Resource Manager has been
enhanced with Driver 93 to support life
cycle management of individual
members within a z/VM V6.2 SSI
environment.
FYI - Unified Resource Manager:
Driver 93 is required for managing z/VM
6.2. However, the Unified Resource
Manager does not support Live Guest
Relocation (LGR).
Additional information is at the following
website:
http://www.vm.ibm.com/zvm620.
6.3.8 zIIP and zAAP Considerations
13 Appropriate sizing tools have been used
to determine the benefits associated with
the use of either zIIP or zAAP processors
in the environment.
14 For your awareness, you may now run
System z Application Assist Processor
(zAAP) eligible workloads on System z
Integrated Information Processors
(zIIPs).
“zAAP on zIIP” planning considerations
can be found at
http://www.ibm.com/support/techdocs/at
smastr.nsf/WebIndex/WP101642.
Chapter 6. Pre-Sales Checklists
203
Copyright 2011 IBM Corporation. All rights reserved.
6.4 Installation Plans
Table 28. Installation Plans
Activity
Status
6.4.1 OSA-Express Considerations
1
If using Unified Resource Manager
(FC0025) or managing a 2458-002 zBX,
a minimum of two OSA-Express3
1000Base-T and possibly two OSA
Express4S or OSA-Express3 10 GBE
features are required.
6.4.2 Crypto Considerations
2
All Disaster Recovery (DR) contracts
have been reviewed to insure there is the
required support provided at the DR site.
Master keys loaded at the production site
and associated with the CKDS and PKDS
must be available and loaded into the
secure hardware at the DR site.
204
SA11-002-02
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
6.5 Physical Site
Table 29. Physical Site
Activity
Status
Due Date
Owner
Comments
6.5.1 General
1
IBM does NOT provide channel cables as
features on the z114.
Note: It is recommended that the
customer utilize the services included in
one of the options of the IBM Fiber
Cabling Services.
Refer to the MustRead and the Appendix
of the SAPR guide for a description of
these services.
6.5.2 Cabling-Using IBM zSeries Fiber Cabling Service Contract
2
Identify which option was chosen if the
zSeries Fiber Cabling Service was
selected:
Option 1: zSeries fiber optic jumper
cabling package
Option 2: zSeries fiber optic jumper
cable migration and reuse for a zSeries
upgrade
Option 3: zSeries jumper cables and
installation (not available in EMEA)
3
Identify what option was chosen If an IBM
Enterprise Fiber Cabling service contract,
was selected:
Option 1: zSeries fiber optic trunk
cabling package (for a single zSeries
system)
Option 2: enterprise fiber cabling
(trunking for the entire data center)
4
Identify what work is included if a custom
cabling contract was selected:
Jumper Cables
Trunks
Jumper Cables and Trunks
Fiber cable clean-up under the floor
Other
5
Cabling Service contract has been
signed and returned to IBM.
6
Planning has been completed, a cable list
has been generated, and cables have
been ordered.
7
Cables will be delivered to the data center
prior to installation date.
Chapter 6. Pre-Sales Checklists
205
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
6.5.3 Cabling-Customer Not Using IBM Cabling Service
8
All required channel cables, link cables,
sysplex timer cables, Hardware
Management Console LAN cables,
converter cables, and mode conditioning
jumper cables for the z114 processor
have been identified and placed on order.
9
A complete analysis has been made of
the connectors used on existing systems
being upgraded to the z114 to ensure that
the appropriate fiber cabling is installed.
Note: The OSA-Express4S and
OSA-Express3 10 GbE connectors are
different than OSA-Express2 10 GbE.
10 If applicable, the customer has made
arrangements for installation of any fiber
optic trunk cable and panels required to
complete the installation.
11 Provisions have been made for the
labeling of all cables required for the z114
installation.
At a minimum the labels should identify
the PCHID number on the cables.
12 Accurate and current documentation is
available that illustrates clearly all of the
cabling infrastructure associated with the
processor complex.
13 All required cables will be delivered to the
data center prior to installation date.
14 Customer is aware of the services
provided as part of installation as defined
in the z114 IMPP manual and in the
Appendix of the SAPR Guide.
15 Does the customer intend to use top exit
I/O? If so, it must be specifically ordered.
If ordering top exit I/O, be aware that the
server physical dimensions and weight
are slightly different.
6.5.4 Raised Floor Requirements
16 Processor can either be installed on a
raised floor or a non-raised floor. If
installed on a non-raised floor, see Must
Read.
206
SA11-002-02
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Activity
Status
Due Date
Owner
Comments
6.5.5 Hardware Management Console
17 HMC ordering considerations:
If Unified Resource Manager will be used
(FC0025), a minimum of two HMC’s must
be available.
The two HMCs are designated as
ensemble HMCs by the customer after
the z114 is installed.
One of the two is an alternate Ensemble
HMC. The alternate can not be used at all
unless it takes over as the primary
following a primary HMC failure.
Therefore, customers using Unified
Resource Manager may want to have a
total of three HMCs or more available.
The primary Ensemble HMC can
continue to perform the duties of any
standard HMC.
6.5.6 Telephone and Remote Support Service
18 IBM VERY STRONGLY recommends
that the customer use the internet via
broadband for the RSF function.
If the RSF internet feature is to be used,
customer has established the appropriate
network infrastructure and security
requirements.
The requirements for setting up this
interface have been reviewed and plans
are in place to implement. The MustRead
section provides information and
publication reference to assist.
6.5.7 OTHER
19 Ensure FC0033 has either been selected
or deselected as desired. If not selected,
the machine will not ship with the Service
Guide, Install Guide, or Safety inspection
guide.
See the MustRead for more information.
Chapter 6. Pre-Sales Checklists
207
Copyright 2011 IBM Corporation. All rights reserved.
6.6 System Management Plans
Table 30. System Management Plans
Activity
6.6.1 Service and EC Updates
1
208
Customer understands the microcode
maintenance strategy for the z114 and
the ability to perform enhanced driver
maintenance.
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
6.7 Service Offerings
Table 31. Service Offerings
Activity
Status
Due Date
Owner
Comments
6.7.1 General
1
z114 Installation Practices and
Policies section in the SAPR appendix
has been carefully reviewed to determine
if there will be any fee based services
required for the installation.
2
Customer understands any services
included as part of the z114 or zBX
installation.
See the MustRead for examples of
available services.
Chapter 6. Pre-Sales Checklists
209
Copyright 2011 IBM Corporation. All rights reserved.
6.8 Business Partners
Table 32. Business Partners
Activity
6.8.1 RESPONSIBILITIES
1
210
All parties (IBM, customer, and business
partners) understand each others roles
and expectations. If these relationships
are not established by a formal contract,
it is recommended that expectations be
documented in letters of understanding.
SA11-002-02
Status
Due Date
Owner
Comments
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 7. Pre-Sales Must-Read Information
7.1 MR-Customer Expectations
7.1.1 General
1. It is critical that the IBM Account Team and customer completely understand
the planned usage and implementation of the processor. It is highly
recommended that the review start off with an overview of the project by the
customer. Although this review will focus on the processor installation, it is
important to have an overall understanding of the customer’s enterprise in
terms of mission and goals.
2. The SA10-018 Checklist can be found in
http://www.ibm.com/support/assure/assur30i.nsf/WebIndex/SA937.
3. It is extremely important that the machine configuration match what the
customer expects. It is also important to verify that the channel types being
ordered match the I/O device which will attach. For example, some channels
offer the option of Long Wave or Short Wave characteristics. The device
attaching must match.
In addition, the following should be considered:
• FC0033 Service Docs Optional Print
Declining this feature will result in the following guides to not be shipped in
paper format. The guides however continue to be available, and printable,
from the documentation DVD that is shipped with every machine
• Service Guide
• Install Guide
• Safety inspection guide
Rules on usage:
• Do not de-select the hard copy doc if this is the first machine at this
location (Same address, same building and same floor)
• Allow de-selection of subsequent copies if multiple machines are
ordered/shipped in the same timeframe.
• Do not de-select the hard copy doc at this location if this is a "dark
account" (raised floor that does not allow laptops and/or media inside)
• All features on a base machine should be reviewed against the proposed
machine. It may be that some features cannot be carried forward and this
needs to be evaluated.
• Although not selectable as part of the configuration process, IC channels and
Hipersockets require real CHPID numbers and should be included in any
configuration analysis. The CHPIDs to be used for InfiniBand channels should
also be considered.
• Any machine that will be in an ensemble requires FC0025.
• The Hardware Management Consoles has very specific requirements when
using FC0025, Unified Resource Manager. Both the Primary HMC and
Alternate HMC must have various identical components. These requirements
are described in the MustRead.
Chapter 7. Pre-Sales Must-Read Information
211
Copyright 2011 IBM Corporation. All rights reserved.
• For customers migrating from a machine that has parallel channels, it should
be verified that the new system no longer requires parallel channels or that
appropriate ESCON converters have been ordered.
• For customer upgrading a processor which is part of a parallel sysplex
environment, it is important to account for the requirement that all coupling link
channels be defined to run in peer mode. Processors being upgraded which
have ISC coupling links defined to run in CFS/CFR mode will require a
redefinition of those links to peer mode before the upgrade.
• All of the following features should be verified
•
•
•
•
•
•
•
•
Quantity and types of channels (including coupling links)
Verify the usage of long wave and short wave channel types
Quantity and types of processors
Memory
Hardware Management Console features
Use of flexible memory in order to support a concurrent book replace
Capacity on Demand features (CIU, OOCoD, CBU, CPE)
Crypto Features
Note: In verifying that the order represents the desired configuration, the CHPID
Mapping Tool along with the CFREPORT file from eConfig may prove to be very
valuable. The customer could use the tool with a planned IOCP file and verify that
the features in the IOCP are on the planned machine as well as to identify early in
the planning cycle any availability issues that could be resolved with the addition
of IO.
The analysis should include not only processor CPs but also ICF, IFL, CBU, zIIP,
zAAP, and SAP requirements.
4. To engage the zSeries Project Office, send a note to John Cholewa in
Poughkeepsie. (cholewa@us.ibm.com) with the following information:
• Client Company Name/location:
• IBM requestor name/location:
• Date Requested:
• What is driving this request?
• For example:
• Deal closure
• Migration
• Potential customer dissatisfaction with ongoing problem(s).
• Please describe some specifics of the project/request?
• What is the start time frame and duration expected?
7.1.2 Performance
5. It is extremely important that the appropriate capacity planning tools have
been used to determine the class of z114 machine required to process the
customer’s workload. Rough estimates using MIPs or equivalent values
should not be acceptable. Please refer to the CPSTOOLs suite of tools for
determining the proper sizing tools to use. The following tool options are
212
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
considered minimal requirements for determining the capacity of the proposed
z114:
Note: A zPCR study is the minimum requirement
• zPCR study using LPAR configuration capacity planning function
• A zCP3000 study should be used when
• SCP is z/OS, z/VM, and/or Linux (under z/VM)
• Customer can provide RMF data or z/VM monitor data
• Growth over a period of time
• Focus is on capacity and potentially storage, I/O and response time
• FICON study
• zTPM (a workload simulator) should used when
• SCP is z/OS
• Customer can provide RMF/CMF data
• Focus is on a primary partition, whose activity is time simulated against the
remaining processor partition workloads
Note: zPCR is required to obtain processor capacity relationships and LPAR
cost.
6. No additional information.
7.1.3 Acquisition and Contractual Considerations
7. No additional clarification
8. There are numerous actions that may result in additional charges after the
z114 is initially installed. For example, activating processors that were initially
designated as unassigned. The account team should review the configuration
for any of these potential charges and ensure the customer is aware of any
such charges that may be generated over the life of the machine.
9. Software licensing the IBM z114 requires 100 Processor Value Units (PVUs)
for each Integrated Facility for Linux (IFL) engine or CP engine (one processor
core). This pricing metric is used to license middleware running on Linux for
System z and distributed platforms. With significantly higher processor
performance over predecessor IBM System z offerings, along with superior
workload scheduling and processor utilization capabilities, this licensing
requirement is designed to provide enhanced software value over other
processor technologies it is likely to replace.
IBM continues the practice of licensing to the processor core. This practice
provides the licensing granularity customers require, while offering the
flexibility to configure their systems to best support their business objectives.
Processors are defined as cores (one IFL or CP engine) on z114, so for PVU
licensing the number of processors identified on the hardware is the same
number of processors to be used for software licensing. For instance, if a z114
CPC has 5 processors, the number of PVUs required would be 5 processor
cores times 100 PVUs (5 x 100 = 500 PVUs).
Chapter 7. Pre-Sales Must-Read Information
213
Copyright 2011 IBM Corporation. All rights reserved.
Note: POWER6 is also rated at 120 PVUs per core. POWER7 is generously
rated at no more than 120 PVU's per core on the higher level machines, and
100 PVU's on the lower 750/755 series.
z/VM is licensed with Engine Based Value Units which are unchanged with this
announcement.
External web site with Processor Value Unit table:
• http://www-306.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_
customers.html
Refer to IBM United States Announcement 208-048, dated March 4, 2008
10.Maintenance requires a 30 day written notice since this type of change is a
swap out (change of serial number), not a physical upgrade.
11.The licensee is not authorized to use an Elliptical Curve Cryptography
feature's machine code as a commercial certificate authority in the issuance of
digitally signed electronic certificates on a public key for the purpose of
identifying the holder for use as credentials in a digital transaction.
See
http://www-947.ibm.com/systems/support/machine_warranties/machine_code
_cryptadd.html
7.1.4 Capacity on Demand
12.No additional information.
7.1.5 Education and Training
13.The following web site should be reviewed for any education that may be
required to support the z114 processor:
http://www.ibm.com/systems/services/labservices
http://www.ibm.com/services/learning
There are also several online courses offered at ResourceLink that will be
valuable in operating and installing the z114 processor. Refer to the SAPR
guide for further information.
214
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
7.2 MR-Hardware Configuration
7.2.1 General
1. If the DWDM does not support peer mode link speeds, an alternative is to
order RPQ 8P2197. Note: this RPQ generates priced hardware features.
2. The FICON Channel has the ability to auto-negotiate (2, 4 or 8 gbps) with the
attached devices. It is possible that not all DWDM ports will support
auto-negotiate with success (channel errors). For those DWDM ports that do
not support auto-negotiate, ensure that the DWDM port is set (hard-coded) to
the same data rate on both sides or will auto negotiate on both sides, for both
the working and protect paths of the network.
3. Ensure that only approved WDM devices will be used in the STP environment.
Please ensure that the vendor qualification document is inspected carefully by
a WDM technical expert. The document is written to be very specific (unit
number, version number, applicable features that are qualified for STP). Time
Division Multiplexing (TDM) may (or may not) be qualified, depending on the
vendor.
The list of GDPS and STP qualified WDMs on ResourceLink should be
checked frequently. Once in ResourceLink, click on the library link, then look
under the Hardware Products For Servers heading. You must open the PDF
file of the relevant vendor to determine whether or not STP is supported. It is
imperative that the details within each vendor qualification letter is completely
understood.
IBM cannot support the use of unqualified WDM equipment in a customer
installation. Note that each and every coupling link going through WDM must
be on a vendor product that supports STP. That is, you may NOT use a
mixture of STP qualified and unqualified vendor WDM products.
4. Hardware support of crypto functions changed significantly between the CCF
based machines (z800/z900 and earlier) and the CPACF based machines
(z890/z990 and later).
Because the crypto architecture has changed, in-house applications and some
product code may not be able to run without the optional secure crypto
hardware. For example, secure key APIs have moved from the CCF hardware
to the optional Crypto Express3 feature, so a Crypto Express3 is required for
secure key support.
The CP Assist for Cryptographic Function (CPACF) is standard on every PU.
However, FC3863 must be ordered for enablement. FC3863 enables CP
Assist for Cryptographic functions and is a prerequisite for all crypto functions
on the z114. On the CPACF machines, the Crypto Express3 (FC0864) is an
option and must be specified via feature codes on the order.
7.2.2 Capacity on Demand
5. Refer to the SAPR Guide for further information.
On/Off Capacity on Demand Tokens (Pre-paid On/Off CoD) is also sometimes
known as Capacity Provisioning Phase 2.
Chapter 7. Pre-Sales Must-Read Information
215
Copyright 2011 IBM Corporation. All rights reserved.
Before Capacity Provisioning Phase 2, customers were charged for temporary
hardware after the On/Off CoD record has been activated. With Phase 2,
customers can now pre-pay for temporary capacity.
Capacity Provisioning Phase 2 is designed to provide the customer the means
to limit their financial liability by automatically deactivating resources through
the use of capacity tokens. Customers are assigned tokens through the order
process. On/Off CoD Tokens can be purchased and "banked" by the customer.
The CEC will manage the use and consumption of tokens.
Tokens can be purchased for any speciality engine (per day of use) or for CP
capacity (MSU's per day of use). Each day of usage (times the amount of
capacity activated) will decrement the token pool available for future On/Off
Temporary Capacity on Demand activations of the specific temporary record.
On/Off CoD and related tokens can only be ordered via ResourceLink by the
customer.
There is no scheduled expiration date for pre-paid tokens (true of CP MSU's
also). Tokens decrement as used, but they can be replenished to add capacity
and/or days as needed. Auto deactivation will be attempted after all tokens
have been used.
7.2.3 Devices and Controllers
6. There is no longer an up to date list of devices supported for attachment to
System z machines. IBM devices previously attached to IBM System z servers
are supported for attachment to the z114 channels, unless otherwise noted.
The subject I/O devices must meet ESCON or FICON/FCP architecture
requirements to be supported. I/O devices that meet OEMI architecture
requirements are supported only using an external converter. Prerequisite
Engineering Change Levels may be required. For further detail, contact IBM
service personnel. While the z114 supports devices as described above, IBM
does not commit to provide support or service for an IBM device that has
reached its End of Service effective date as announced by IBM.
For a z114 machine, it is NOT true that a device that attached to an earlier
generation machine will work on a z114 without change. There may be
devices that require microcode updates (both IBM and OEM) in order to attach
to a z114. Refer to the Driver Exception Letter on ResourceLink, contact the
appropriate IBM device support team for any required microcode levels on the
devices, and contact any OEM supplier for verification.
For equipment (both IBM and OEM) that supports MIDAW or zHPF may
require minimum levels of microcode or feature codes. The supplier of the
equipment must be contacted to determine any requirements.
Note: The MIDAW function was first available on the z9 processor and applies
to both ESCON and FICON channels.
The majority of the announcement materials for MIDAWs focuses primarily on
FICON architecture but ESCON also supports MIDAWs. MIDAWs does not
216
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
affect ESCON performance at short distances. However, MIDAWs may
improve the performance of EF data sets with ESCON at extended distances,
but since ESCON doesn't support multiplexing, non-EF data sets will not
improve.
Other relevant information:
ResourceLink Library - Qualified Switches and Directors for z https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/switchesAndDir
ectorsQualifiedForIbmSystemZRFiconRAndFcpChannels?OpenDocument
ResourceLink Library - Qualified DWDMs:
https://www.ibm.com/servers/resourcelink/lib03020.nsf/pages/systemzQualifie
dWdmProductsForGdpsSolutions?OpenDocument&pathID=
ResourceLink Fixes - Exception Letters - z114 - Customer Exception
Letter - (Additional information about IBM and Brocade directors with
FICON Express8S or FICON Express8)
FICON Open Exchanges (Max=32) with STK devices:
FICON channels have the capacity to support more than 64 open exchanges.
The 64 limit is how many FICON will initiate. Device reconnects can cause the
actual number of exchanges open at the channel to be much higher at any
single point in time.
STK devices can only support up to 32 open exchanges.
In System z9, the function existed for customers to change the open exchange
limit for FICON channels from 64 open exchanges to 32 open exchanges.
In System z10 and z114, access to the function was moved to a Service only
capability and is accessed with the machine in PEMODE. If a customer has an
STK device and requires open exchanges to be set to 32, IBM System z
supports the change as long as the change is only made to the FICON
channels connected to the STK control units.
Contact service personnel for assistance. IBM support must be contacted
before changing the open exchange limit from 64 to 32 open exchanges on
any FICON channels that are not connected to STK control units.
7. No additional information.
8. A 3590-A60 with 1 GB FICON adapters is not supported when directly
attaching to a z114, z9 or z10 processor (i.e. no FICON Director). If a
customer would like to attach a 3590-A60 with 1 GB adapters, they must order
an MES for the 3590 to change the adapters to the 2 GB versions.
Channel problems can occur when there is an attempt to direct connect (i.e.
no FICON director) a 3590-A60 with 1 GB FICON adapter cards to a FICON
Express4 or FICON Express8. The only fix available is to have the 1GB
adapter in the 3590 replaced with a 2 GB adapter. If you have this attachment
configuration, then it is critical that you have the SSR contact Tucson Product
Field Engineering (PFE) to discuss the situation and arrange for corrective
Chapter 7. Pre-Sales Must-Read Information
217
Copyright 2011 IBM Corporation. All rights reserved.
actions. This is not an issue with the FICON Express card but rather with the
3590.
7.2.4 Consoles
9. This can take the form of Sysplex console support or use of IBM 2074 Console
Support Controllers, IBM 3174 Cluster Controller, or the OSA-ICC.
Note: As a general rule, the Hardware Management Console console integration
function should NOT be used unless the limitations are understood and agreed
to.
10.Important HMC Requirements, when using Unified Resource Manager are
listed here.
The Unified Resource Manager HMCs must be equal to or higher in Driver LIC
level than every CPC in the Ensemble. CPC’s at Driver 86 can participate in
the Ensemble with CPC’s at Driver 93, for example, provided the Unified
Resource Manager HMCs are both (PRI/ALT) at Driver 93.
Before you begin, be aware of the following requirements and error/warning
messages:
The machine type and model number of the primary HMC and alternate HMC
must be identical. Both must be either Feature Code 0090 or Feature Code
0091. Verify this information by viewing the sticker on top of the HMC
hardware tower
HMC FC 0084 is a 4362PAT machine type
HMC FC 0090 is a 4367PAM/PAA machine type
HMC FC 0091 is a 7327PAA machine type
The AROM control level (LIC control level) of the primary HMC and alternate
HMC must be identical. Verify this information using the View Console
Information task.
The ethernet configurations on the primary HMC and the alternate HMC must
be the same. Both HMCs must have the same number of adapters, and each
port must be attached to the same subnet. Verify this information on LAN
Adapter page on the Customize Network Settings task.
The modem configuration must be the same on the primary HMC and the
alternate HMC to ensure the call-home function works after a switch over
occurs. Verify this information using the Customize Modem Settings task.
If you attempt to enable an HMC to be an unassigned alternate HMC and any
of the following conditions are in effect, you will receive an error message:
- The HMC has CPCs assigned to it (verify using the System Information task).
- The HMC is set up to be an NTP server (verify on the Configure NTP
Settings page using the Customize Console Data and Time task).
- The HMC is set up to be a call home server (verify using the Customize
Outbound Connectivity task).
218
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
- The HMC is enabled for data replication (verify using Configure Data
Replication task).
- The HMC is configured to use DHCP (verify using the Customize Network
Settings task).
If you attempt to enable an HMC to be an unassigned alternate HMC and any
of the following conditions are in effect, you will receive warning message, but
the function will complete:
- The HMC is set up to be an FTP server (verify using the Enable Electronic
Service Agent task).
- API support is enabled on the HMC (verify using Customize API Settings
task). When the primary HMC and alternate HMC are defined, the ability to
send API requests is not available.
7.2.5 Coupling Links
11.InfiniBand Coupling Links provide the opportunity to consolidate CF Links, but
ensure that the selections made will perform as expected. PSIFB CF Links
(HCA2-O 12x IB-DDR (FC0163) or HCA2-O LR 1x IB-DDR (FC0168)) are a
good choice for ISC-3 consolidation, within distance limits. The level of
consolidation possible depends upon workload. A zCP3000 CF study is highly
recommended.
It may be possible to consolidate up to 8 ISC-3 channels on 1 PSIFB.
If planning a 1:1 replacement of ICB-4 with PSIFB, then use zCP3000 to
validate changes to coupling efficiency are acceptable. See the "host effect"
matrix in the Coupling Config Options whitepaper.
Note: The z114 is the last server to offer ordering of new ISC-3 coupling links.
For guidelines, see www.ibm.com/systems/z/advantages/pso/whitepaper.html.
Additionally, the “Getting Started with InfiniBand on System z10 and System
z9” Redbook (SG24-7539) available on the Redbooks™ Web site provides a
good overview of the InfiniBand capabilities on System z10 and System z9:
• http://www.redbooks.ibm.com/
12.If ordering HCA2-O or HCA3-O InfiniBand coupling links, ensure you have
ordered enough ports to provide you with physical card redundancy. For
example, if order FC0170 (HCA3-O LR which is a 4-port card), order 8 ports to
get two cards for redundancy.
7.2.6 Server Time Protocol
13.If using a coupling link, the customer must have a plan to implement STP in
the environment. Either a Mixed CTN or an STP-only CTN is adequate.
This can take a considerable amount of time for planning and education if STP
is new to your environment.
The z114 can exist in a Mixed CTN if necessary. There should be at least two
Chapter 7. Pre-Sales Must-Read Information
219
Copyright 2011 IBM Corporation. All rights reserved.
other servers connected to the 9037 that have the STP feature installed and
configured. The z114 should be connected via redundant coupling links to two
of these machines (at a minimum). This will permit the z114 to have two
machines to act as sources of time.
Sysplex Tim er
ETR Network ID =31
ET R
N etw o rk
C oordinated
T im ing
Netw ork
ET R Tim ing M ode
ISC -3
z9 EC, Stratum 1
CTN ID = HM CTEST - 31
ET R T im ing M ode
z9 BC, not STP enabled
ETR Network ID = 31
z10 EC , Stratum 1
CTN ID = HM CTEST - 31
ST P T im ing M ode
ISC-3
2817, Stratum 2
CTN ID = HM CTEST - 31
14.See STP SAPR Guide, SA06-012 and schedule a TDA.
7.2.7 Channel Configuration
15.Review in detail the output from the configurator to determine channel types
that may be deleted as part of an upgrade.
16.The FICON Express 4, FICON Express8S or FICON Express8 features do not
support the use of FCV CHPIDs. See the PRIZM product at
http://www.opticatech.com/.
17.Refer to RETAIN TIP H176013 for further information.
18.Be aware that when a z114 and FC0025 Unified Resource Manager are
ordered without a zBX, eConfig does not force you to order two
OSA-Express4S or OSA-Express3 10 GbE features, however they are
required if LPAR to LPAR communication is required in this circumstance.
Usage notes:
A) When using two OSX devices in a high availability environment, meaning
same IP subnet and vlan, the OSX device must be connected with a direct
connect cable. This will simulate a LAN existing between the OSX devices,
allowing Layer 2 routing to work.
B) Otherwise, the OSX devices should be configured with LC Duplex wrap
plugs and on separate IP subnets and vlans. This will allow direct connectivity
to other images sharing the OSX device.
Best Practices:
When implementing a zEnterprise System Ensemble Node without an
attached zBX, interconnect all OSX ports via Direct-Connect cables and not
wrap cables as has been recommended in previous zEnterprise
documentation. For technical reasons, a zero-zBX implementation should
220
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
have no more than two OSX IEDN ports on any LPAR.
1. If the LPAR is a native z/OS LPAR with a z/OS Virtual Server, ensure that
the LPAR has been configured with connections into each OSX port. The
connections should represent connection pairs, where each pair has been
defined with the same IP Subnet and VLAN ID for the IEDN.
2. If the LPAR is a z/VM LPAR, any guest with native attachment to the OSX
ports must also configure interfaces with the same VLAN ID and IP Subnet to
each of the OSX ports. (This is the same as what was described in Bullet #1
above.)
3. If z/VM is to support guests on a VSwitch, then this VSwitch must be
attached to each of the OSX ports, again using the same VLAN ID and IP
Subnet.
VSb
VSa
CHPID#1
OSX 10GbE
LR/SR
MATCHED
CHPID
PAIR
(MINIMUM)
z196 EC
O
S
M
CHPID#2
CPC 1
IEDN
VLAN ID
‘A’ & ‘B’
7.2.8 Crypto
19.With the change to the CPACF architecture (from the CCF based architecture)
some functions which are not widely used have been dropped on the CPACF
machines.
See 'Migrating from the IBM eServer zSeries 800 and the IBM eServer zSeries
900 in the ICSF Systems Programmer's Guide.
Support for the following crypto functions were dropped on the CPACF based
machines:
a. There is no KMMK (key management master key).
b. The Commercial Data Masking Facility (CDMF) is no longer supported. The
CDMF keyword on KGUP control statements and panels is no longer
supported.
Chapter 7. Pre-Sales Must-Read Information
221
Copyright 2011 IBM Corporation. All rights reserved.
c. The Public Key Algorithm Digital Signature Standard is not supported. This
affects callable services CSNDPKG, CSNDPKI, CSNDDSG, and
CSNDDSV.
d. The PBVC keyword is not supported on a PCI X Cryptographic
Coprocessor. This affects callable services Clear PIN Generate Alternate
(CSNBCPE), Clear PIN Encrypt (CSNBCPE), PIN Translate (CSNBPTR)
and PIN Verify (CSNBPVR).
e. RSA keys of modulus less than 512 bits are not supported on a z10 BC
Cryptographic Coprocessor.
The following services are not available on the CPACF based machines (Refer to
the ICSF Application Programmer's Guide).
• ANSI X9.17 EDC Generate (CSNAEGN)
• ANSI X9.17 Key Export (CSNAKEX)
• ANSI X9.17 Key Import (CSNAKIM)
• ANSI X9.17 Key Translate (CSNAKTR)
• ANSI X9.17 Transport Key Partial Notarize (CSNAKTR)
• Ciphertext Translate (CSNBCTT)
• PKSC Interface Service (CSFPKSC)
• Transform CDMF Key (CSNBTCK)
• User Derived Key (CSFUDK)
20.If a customer wants to use a TKE for securely loading keys on the z114, they
must use a supported TKE workstation (FC0841) for attachment to the 2818.
The z114 requires TKE hardware FC0841 and TKE LIC V7.1 (FC0867).
During a machine upgrade, if the base TKE workstation is FC0859, FC0839 or
FC0840 the units cannot not be carried forward. The configurator will delete
these features and add a comparable number of FC0841.
This workstation hardware and TKE 7.1 LIC can also manage host
cryptographic adapters on machine types 2097 and 2098.
To exploit new cryptography enhancements, the new TKE LIC 7.1 LIC and
specific operating system releases and service are required..
21.With the z114 or the z10, new Protected keys are available. If using a secure
key as the source for a protected key, a Crypto Express3 is required. The
Crypto Express3 will decrypt the secure key from under the master key and
re-encrypt it under the appropriate CPACF wrapping key before providing it to
the CPACF.
222
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
7.3 MR-Software Configuration
7.3.1 General
1. Operating system requirements depends on the capabilities that you intend to
exploit.
The IBM zEnterprise 114 requires :
z/OS V1.13 with PTFs.
z/OS V1.12 with PTFs.
z/OS V1.11 with PTFs.
z/OS v1.10 + PTFs AND the z/OS 1.10 Lifecycle Extended Service
(5656-A01). The Lifecycle Extension must be in place before a customer may
obtain required PTFs for the z114 and z196. There are no exceptions.
z/OS v1.9 + PTFs AND the z/OS 1.9 Lifecycle Extended Service (5646-A01).
The Lifecycle Extension must be in place before a customer may obtain
required PTFs for the z114 and z196. There are no exceptions.
z/OS v1.8 Lifecycle Extended Service (5646-A01). has expired and is no longer
available. Contact GTS for qualifications for a contract. Contract must be in place
to obtain required PTFs for the z114 or z196. There are no exceptions.
z/VM V6.1 with PTFs.
z/VM V5.4 with PTFs.
z/VSE V4.3 with PTFs.
z/VSE V4.2 with PTFs.
z/TPF V1.1
Linux on System z distributions:
Novell SUSE SLES 10 and SLES 11
Red Hat RHEL 5 and RHEL6.
Note: See
http://www.ibm.com/systems/z/os/linux/resources/testedplatforms.html to see
earlier releases of Linux on System z that have been tested and approved.
The z114 contains new functions that require later versions or releases
of these operating systems. More information can be found in Chapter 2
Software Requirements.
2. See the software chapter of the zBX SAPR Guide.
7.3.2 CIU,CBU, ON/OFF Capacity on Demand
3. No additional clarification
7.3.3 CFCC
4. The Sizer tool is the only source of determining structure sizes. It can be found
at the following web site:
Chapter 7. Pre-Sales Must-Read Information
223
Copyright 2011 IBM Corporation. All rights reserved.
• http://www.ibm.com/systems/support/z/cfsizer/
CFCC Level 17 increases the number of structures that can be allocated in a
CFCC image from 1023 to 2047. Allowing for more CF structures to be defined
and used in a sysplex, permits more discrete data sharing groups to operate
concurrently and can help environments which require many structures to be
defined, z114, with CFCC level 17, also provides improved serviceability of
Coupling Facilities with enhanced data collection and triggering of
non-disruptive CF dumps.
Note: In order to provide these functional and serviceability enhancements,
the Coupling Facility Control Code will require more storage allocation for
internal control blocks and dump space. Clients should ensure they allocate
additional storage capacity when setting up the image profiles for the Coupling
Facility image. The CFCC code Release 17 will use about 400MB to 450MB of
total storage for each image. This usage is a significant increase over storage
usage in previous CF levels.
Full 2047 structure support was delivered via an MCL December 15,
2010. Please refer to software co-requirement deliverables for exploitation.
7.3.4 IBM and ISV Software Support
5. No additional clarification
6. To help avoid unexpected delays in closing these opportunities, you should
start the process of having your customer review and sign the AWLC
agreement right away. The "ICA Attachment for System z Advanced Workload
License Charges" was recently deployed worldwide through model contract
number INTC-8538 (US form number is Z125-8538), and its associated "IBM
Exhibit for Advanced Workload License Charges" was deployed worldwide
through model contract number INTC-8539 (US form number is Z125-8539).
7. Advanced Entry Workload License Charges
Coinciding with the announcement of the IBM zEnterprise 114 (z114) server,
IBM introduces a new software pricing structure called Advanced Entry
Workload License Charges (AEWLC). The AEWLC pricing metric leverages
the reporting mechanisms and existing Millions of Service Units per hour
(MSU) tiers of the Entry Workload License Charges (EWLC) pricing metric and
the Midrange Workload License Charges (MWLC) pricing metric while
extending the software price performance provided by the EWLC and MWLC
tiers. AEWLC applies only to eligible z/OS, z/TPF, and z/VSE
operatingsystems and their associated middleware programs when running on
a z114 server. For additional AEWLC information, refer to Software
Announcement 211-250, (RFA54941) "Advanced Entry Workload License
Charges offers price / performance for the IBM zEnterprise 114," dated July,
12, 2011.
When a z114 server is in an actively coupled Parallel Sysplex, you may elect
aggregated Advanced Workload License Charges (AWLC) pricing or
aggregated Parallel Sysplex License Charges (PSLC) pricing, subject to all
applicable terms and conditions.
For additional information on AWLC, refer to Software Announcement 210-238,
(RFA53175) "Advanced Workload License Charges offers price / performance for
the IBM zEnterprise 196," dated July, 22, 2010.
224
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
7.3.5 Crypto
8. A UDX is custom code that is installed in the secure hardware of the Crypto
Express card. It allows customers to implement their own unique code within
the tamper resistant hardware. On System z, the UDX code is always
developed based on customer specs by IBM (either the Crypto Competence
Center in Denmark or IBM Global Services in the US) and delivered to the
customer for installation inside the Crypto Card. There is also a key
management software package, called DKMS, from the Crypto Competence
Center that may require a UDX depending, on the customer environment.
Because a UDX interfaces directly with the card and with ICSF (the z/OS
component that provides the software interface to the crypto hardware),
anytime either a new crypto hardware device is installed or the version of
ICSF changes, the UDX must be rebuilt. So if a customer will be migrating
from one hardware device to another (for example, from a CEX2 on a z10 to a
CEX3 on a z196) or upgrading the version of ICSF on their new machine, the
UDX will need to be rebuilt.
You can check for the existence of a UDX in the UDX Status column on the
Crypto Configuration panel on the HMC.
In most cases, the contract with the Services organization covers rebuilding for
new hardware and software platforms, so it is simply a matter of contacting the
appropriate organization to have the UDX updated and tested, however you
should build time into the install schedule for getting the updated UDX's from IBM.
Additionally, if the customer's support contract for the UDX has lapsed, there may
be additional time required to get the paperwork in place.
7.3.6 Sysplex Considerations
9. No further clarification.
10.No further clarification
7.3.7 Linux Considerations
11.No additional information.
12.No additional information.
7.3.8 zIIP and zAAP Considerations
13.Adding specialty processors to a z114 will affect the overall processor
performance due to the n-way effect. Capacity planning tools must be used to
evaluate the impact to the overall machine.
Before proposing any specialty processors, it is critical that an analysis be
made to determine the benefits to be obtained and that the appropriate levels
of software are installed that can exploit them.
14.No additional information.
Chapter 7. Pre-Sales Must-Read Information
225
Copyright 2011 IBM Corporation. All rights reserved.
7.4 MR-Installation Plans
7.4.1 OSA-Express Considerations
1. Unified Resource Manager (FC0025) requires a minimum of two
OSA-Express3 1000Base-T features (FC3367).
7.4.2 Crypto Considerations
2. Disaster Recovery (DR) agreements should be reviewed for crypto
considerations.
If a secure device (CEX coprocessor) is available at the production site, a
secure device must be available at the DR site to provide equivalent function.
If using clear key, you can not run DR using z900/800 or below processors.
The CPACF based machines (z890/z990 or later) provide support for clear key
APIs. The CCF based machines (z800/z900 or earlier) do not support those
clear key APIs, so applications or products which invoke those APIs may fail.
226
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
7.5 MR-Physical Site
7.5.1 General
1. The following can be used to engage IBM Global Facilities Cabling Services
team:
a. Register the project using the form:
• http://ehngsa.ibm.com/home/n/l/nl27971/web/public/Training/Projectregi
stration/GTS%20Project%20registration%20cabling.doc
b. Send the form to Cabling@us.ibm.com
c. Send output of the System configurator or configuration in the same mail
d. The IBM Global Facilities Cabling Services team will involve the local
cabling practitioner
e. The local responsible IBM cabling practitioner will contact the STG account
team
f. Customer will be contacted to collect requirements
g. An assessment will be done
h. A structured cabling design (including IBM FTS) will be made
i. Proposal will be made to the customer or the local IBM STG account team
j. After acceptance of the proposal, cables will be ordered, delivered and
installed
7.5.2 Cabling-Using IBM zSeries Fiber Cabling Service Contract
2. Refer to the Appendix in the SAPR guide for further information.
3. Refer to the Appendix in the SAPR guide for further information.
4. Any custom contracts should be reviewed to ensure that the Customer and
IBM are in agreement as to what services are included and what services are
excluded.
5. Determine the status of the contract and if there are any impediments.
6. No additional clarification.
7. No additional clarification.
Chapter 7. Pre-Sales Must-Read Information
227
Copyright 2011 IBM Corporation. All rights reserved.
7.5.3 Cabling-Customer Not Using IBM Cabling Service
8. No additional clarification.The following illustrates the connectors required on
various features. Older features (not available on the z114) are included as a
comparative reference.
Feature Code
Description
Connector Type
FC 2319
FICON Express LX (Long
Wave)
Single Mode LC Duplex (9
micron)
FC 2320
FICON Express SX (Short
Wave)
Multimode LC Duplex (50
and 62.5 micron)
FC3319
FICON Express2 LX (Long
Wave)
Single Mode LC Duplex
(9/125 micron)
FC3320
FICON Express2 SX (Short
Wave)
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
FC3321
FICON Express4 10KM LX
Single Mode LC Duplex (9
micron)
FC3322
FICON Express4 SX
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
FC3323
FICON Express4-2C 4KM
LX
Single Mode LC Duplex (9
micron)
FC3324
FICON Express4 4KM LX
Single Mode LC Duplex (9
micron)
FC3325
FICON Express8 10KM LX
Single Mode LC Duplex (9
micron)
FC3326
FICON Express8 SX
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
FC0409
FICON Express8S 10KM LX
Single Mode LC Duplex (9
micron)
FC0410
FICON Express8S SX
Multimode LC Duplex
(50/125 micron or 62.5/125
micron)
Feature Code
Description
Connector Type
FC 2324 (FC 2323)
ESCON Ports
Multimode MT-RJ (62.5
micron)
Feature Code
Description
Connector Type
FC 0218/0219
2 port ISC-3
Single Mode LC Duplex (9
micron)
Table 33. ESCON Connectors
Table 34. ISC-3 Connectors
228
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Table 35. OSA-Express Connectors
Feature Code
Description
Connector Type
FC 1364
2-Port LX Gigabit Ethernet
Single Mode LC Duplex (9
micron)
FC 1365
2-Port SX Gigabit Ethernet
Multimode LC Duplex (50
and 62.5 micron)
FC 2364
2-Port LX Gigabit Ethernet
Single Mode SC Duplex (9
micron)
FC 2365
2-Port SX Gigabit Ethernet
Multimode SC Duplex (50
and 62.5 micron)
FC3364
OSA -Express2 GbE LX
Single Mode LC Duplex (9
micron)
FC3365
OSA-Express2 GbE SX
Multimode LC Duplex (50
and 62.5 micron)
FC3368
OSA-Express2 10 GbE
Long Reach
Single Mode SC Duplex (9
micron)
Note: different connector
than OSA-Express2 GbE
FC 2366
2-Port Fast Ethernet
RJ-45 (copper wire, not fiber
optic)
FC 1366
2-Port 1000Base-T Ethernet
RJ-45 (copper wire, not fiber
optic)
FC 3366
OSA Express2 2-Port
1000Base-T Ethernet
RJ-45 (copper wire, not fiber
optic)
FC3362
OSA-Express3 4-Port LX
Gigabit Ethernet
9 micron single mode
LC Duplex
FC3363
OSA-Express3 4-Port SX
Gigabit Ethernet
50 and 62.5 micron multimode
LC Duplex
FC3367
OSA-Express3 4-Port
1000BaseT Ethernet
Category 5 UTP copper wire
RJ-45
FC3369
OSA-Express3 2-Port
1000BaseT Ethernet
Category 5 UTP copper wire
RJ-45
FC3370
OSA-Express3 2-Port LR 10
Gigabit Ethernet
9 micron single mode
LC Duplex
FC3371
OSA-Express3 2-Port SR 10
Gigabit Ethernet
50 and 62.5 micron multimode
LC Duplex
FC0404
OSA-Express4S 1 GbE EN
LX PCIe I/O drawer only 2
port card - 1 PCHID
9 micron single mode
LC Duplex
Chapter 7. Pre-Sales Must-Read Information
229
Copyright 2011 IBM Corporation. All rights reserved.
Feature Code
Description
Connector Type
FC0405
OSA-Express4S 1 GbE EN
SX PCIe I/O drawer only 2
port card - 1 PCHID
50 and 62.5 micron multimode
LC Duplex
FC0406
0406 OSA-Express4S 10
GbE EN LR
9 micron single mode
LC Duplex
FC0407
OSA-Express4S 10 GbE EN
SR
50 and 62.5 micron multimode
LC Duplex
Feature Code
Description
Connector Type
Not available.
ETR Port
N/A
Table 36. ETR Connector
9. No additional clarification
10.No additional clarification
11.In an installation comprised of more than one Logical Channel Subsystem,
there will more than likely be multiple occurrences of the same CHPID
number. It is extremely important that the labels on cables reflect the PCHID
number on the machine where the cable will be plugged.
12.No additional clarification
13.No additional clarification.
14.Refer to the appendix in SAPR guide to determine those activities provided as
part of the machine installation and those items that may require a services
contract. Significant cabling work is required for new and upgrading systems.
For upgrading systems, work is needed to plan, unplug, relabel, and relocate
the existing cables to the correct tile floor cutouts. If IBM is going to perform
this work, a service contract will be required.
For Site Planning Services (water cooling help for example), see
http://www-935.ibm.com/services/us/index.wss/offering/its/a1000240 or
http://www-935.ibm.com/services/us/index.wss/itservice/igs/a1026000.
15.Top Exit I/O adds 6 inches to both sides of the machine and approximately 95
pounds (43.1 kg) to the weight.
7.5.4 Raised Floor Requirements
16.If the z114 has been ordered to be installed on a raised floor, installation on a
non-raised floor environment may be in violation of local codes and requirements
and is absolutely prohibited.
7.5.5 Hardware Management Console
17.Two ensemble HMCs are required for redundancy. One is primary and the
other is the alternate. The alternate should not be used unless a take over has
been performed.
Both ensemble HMCs must be in the same customer-assigned subnet to allow
swap of IP addresses during fail over. Also, both HMCs need equivalent
230
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
network accessibility to all systems to be managed. The pair require network
connectivity to each other to allow coordination and data replication. See
SG27-2608, Ensemble Planning and Configuration Guide.
7.5.6 Telephone and Remote Support Service
18.Refer to HMC Guide and the HMC online books application for instructions on
setting up the interface.
7.5.7 Other
19.FC0033 Service Docs Optional Print
Declining this feature will result in the following guides to not be shipped in
paper format. The guides however continue to be available, and printable,
from the documentation DVD that is shipped with every machine
• Service Guide
• Install Guide
• Safety inspection guide
Rules on usage:
• Do not de-select the hard copy doc if this is the first machine at this
location (Same address, same building and same floor)
• Allow de-selection of subsequent copies if multiple machines are
ordered/shipped in the same timeframe.
• Do not de-select the hard copy doc at this location if this is a "dark
account" (raised floor that does not allow laptops and/or media inside)
Chapter 7. Pre-Sales Must-Read Information
231
Copyright 2011 IBM Corporation. All rights reserved.
7.6 MR-System Management Plans
7.6.1 Service and EC Updates
1. Whenever a new driver level is released, the then current driver will be
supported for a period of six months. During this period, the level of support
will decrease in stages for the replaced Driver. With enhanced driver
maintenance, there will be the ability to concurrently upgrade to the newest
driver level at certain points over time
232
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
7.7 MR-Service Offerings
7.7.1 General
1. Examples of some of the available services:
a. Rapid Workload Optimization Assessment
This interactive workshop based service will evaluate the feasibility and
measure technical and business impact of implementing a zEnterprise
solution. It is based on a rapid method to help clients optimize their workloads
from business and technical perspectives. The analysis is based on the
client's own environment. As part of this service we can work with clients to
select workloads that may benefit from zEnterprise.
b. IBM Smart Analytics Optimizer Enablement Services
This offering provides services to configure the hardware components
necessary to enable a basic functional IBM Smart Analytics Optimizer
environment and IBM System Storage unit. In addition, this offering assists
current DB2 for z/OS clients with the planning and installation activities for the
integration of the optimizer into their data center. A test data mart will be
provided to demonstrate functionalities. Customers will be provided with a
high performance system that is ready to be loaded with the data for their
queries. This service is 3-4 weeks long.
c. zEnterprise Ensemble Enablement JumpStart Assistance for zBX Blades
This service is targeted for implementations involving IBM Blades and is
designed to help accelerate the implementation of an Ensemble. The service
will set up the z/OS and zBX infrastructure, use a test application to show the
functionality of the Ensemble environment, and provide education to the client.
Focus of this offering is on the “Manage” functionality for Unified Resource
Manager. Additional services for the “Automate” functionality, including some
advanced Unified Resource Manager features, can be provided through the
zEnterprise Ensemble Enablement for zBX Blades offering. This service is 3-4
weeks long.
d. zEnterprise Ensemble Enablement JumpStart Assistance for z/VM
This service is targeted for implementations that will use the Unified Resource
Manager to manage Linux virtual servers under the z/VM Hypervisor. The
service will set up the z/VM and Unified Resource Manager infrastructure, use
a test application to show the functionality of the Ensemble environment, and
provide education to the client. Focus of this offering is on the “Manage”
functionality for Unified Resource Manager. This service is 3-4 weeks long.
e. zEnterprise Ensemble Enablement for zBX Blades
This is a comprehensive service offering designed to accelerate the
implementation of an Ensemble with a functional application test environment
selected by the client. Services are provided to implement the Ensemble with
a Test Workload Environment spanning the zCEC and zBX blades. The virtual
resources and virtual servers will be defined on the blades. A blade operating
Chapter 7. Pre-Sales Must-Read Information
233
Copyright 2011 IBM Corporation. All rights reserved.
system will be installed and a test application environment established. The
required z/OS, z/VM, zBX Blade, and Unified Resource Manager skills will be
provided to enable the Ensemble. The migration to this environment can be a
complex task requiring an extended implementation period to activate the
technology. The Ensemble Enablement offering also provides project
management and Unified Resource Manager skills transfer to operations and
systems administration personnel. Additional services to assist in the
migration to production can also be provided on a customized basis. This
Ensemble Enablement offering is a more comprehensive offering, covering all
aspects of the implementation process. While this service provides the
customer the optimal implementation experience, it is priced higher than the
JumpStart services. This service is 9 weeks long.
f. Server Time Protocol Implementation Services
Get more details about the available services by contacting one of the STG
Lab Services opportunity managers in the US:
George Ng/Poughkeepsie/IBM@IBMUS; phone: 845-705-8439, See US
announcement letter 609-021.
g. z/VM Single System Image and Live Guest Relocation
This service is intended to help clients plan for and implement a z/VM
Single System Image (SSI) cluster. It is ideal for clients who want to take
advantage of the z/VM guest mobility solution, Live Guest Relocation
(LGR), in order to increase the availability of their Linux on System z
servers.
This service will:
- Educate you about z/VM clusters and their capabilities
- Provide cluster planning and deployment assistance
- Provide operational guidance and recommendations
- Optionally provide migration assistance for users of IBM's existing
Cross-System Extensions technology
- Demonstrate the technology in your own environment.
h. IBM Implementation Services for System z
Global Technology Services, "IBM Implementation Services for System z zBX and Unified Resource Manager offering (6948-L66)" will be enhanced
to support Linux on System x with the zEnterprise BladeCenter Extension
(zBX) infrastructure.
The offering will assist you with the planning, implementation and
deployment of the IBM zEnterprise BladeCenter Extension (zBX) and
Unified Resource Manager infrastructure, enabling you to deploy on an
integrated platform of System z, POWER7, and System x technologies.
This service will help you to accelerate the adoption of IBM zEnterprise
technology and realize the value faster.
234
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
For more information about the offering, please refer to:
www.ibm.com/services/us/en/it-services/
server-product-services-for-system-z.html.
2. This question is intended to identify any other services that have been
included as part of the installation activities. If so, the account team should
ensure the scope of the services are clear to the customer and that plans are
in place to fully utilize any services offered.
Chapter 7. Pre-Sales Must-Read Information
235
Copyright 2011 IBM Corporation. All rights reserved.
7.8 MR-Business Partners
7.8.1 Responsibilities
1. No additional clarification
236
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Chapter 8. Publications and Education
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this SAPR Guide.
8.1 New Feature Code (FC0033) - Service Docs Optional Print
Declining this feature in eConfig will result in the following guides to not be
shipped in paper format. The guides however continue to be available, and
printable, from the documentation DVD that is shipped with every machine.
• Service Guide
• Install Guide
• Safety inspection guide
Rules on usage:
1. Do not de-select the hard copy document if this is the first machine at this
location (Same address, same building and same floor)
2. Allow de-selection of subsequent copies if multiple machines are
ordered/shipped in the same timeframe.
3. Do not de-select the hard copy document at this location if this is a "dark
account" (raised floor that does not allow laptops and/or media inside)
Chapter 8. Publications and Education
237
Copyright 2011 IBM Corporation. All rights reserved.
8.2 Information about the IBM z114
The following publications are available in the Library section of Resource
Link by accessing the following Web site:
www.ibm.com/servers/resourcelink
API for Java API-JAVA
Application Programing Interfaces SB10-7030
Capacity on Demand User’s Guide SC28-2605
CHPID Mapping Tool Users Guide GC28-6900
CIM Management Interface SB10-7154
Coupling Links I/O Interface Physical Layer SA23-0395
Environmental Notices and User Guide Z125-5823
ESCON and FICON CTC Reference SB10-7034
ESCON I/O Interface Physical Layer SA23-0394
ESCON PD Guide ESCONPD
Fiber Optic Cleaning Procedures SY27-2604
Fibre Channel Connection (FICON) I/O Interface Physical Layer SA24-7172
Hardware Management Console Operations Guide Version 2.11.1 SC28-6905
Hardware Management Console Operations Guide for Ensembles Version 2.11.1
SC27-2615
Installation Manual - Physical Planning GC28-6907
Installation Manual Delta Pages 41U9435
Installation Manual (including PN 41U9435) GC28-6902
Integrating the HMC Broadband Remote Support Facility on your Enterprise
SC28-6880
IOCP User’s Guide (ICP) SB10-7037
License Agreement for Machine Code SC28-6872
License Agreement for Machine Code Addendum for ECC GC27-2612
Maintenance Information for Fiber Optic Links SY27-2597
OSA-Express Customer’s Guide and Reference SA22-7935
OSA-Express3 Integrated Concole Controller Dual-Port User’s Guide SA23-2266
238
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Parts Catalog GC28-6908
Planning for Fiber Optics GA23-0367
PR/SM Planning Guide SB10-7155
Safety Inspection GC28-6904
Safety Notices G229-9054
SAPR Guide SA11-002
SAPR Guide for Server Time Protocol SA06-012
SCSI IPL - Machine Loader Messages SC28-6839
Service Guide Delta Pages 41U9438
Service Guide for HMCs and SEs GC28-6861
Service Guide for Trusted Key Entry Workstations GC28-6901
Service Guide (including PN 41U9438) GC28-6903
Stand-Alone Input/Output Configuration Program User’s Guide SB10-7152
Statement of Limited Warranty GC28-6883
Support Element Operations Guide Version 2.11.1 SC28-6906
System Overview SA22-1087
System z Functional Matrix ZSW0-1335
z/Architecture Principles of Operation SA22-7832
z/Architecture Reference Summary SA22-7871
The following publications are shipped with the product providing FC0033
(See Section 8.1 above) is ordered.
Environmental Notices and User Guide Z125-5823
Installation Manual GC28-6902
License Agreement for Machine Code SC28-6872
License Agreement for Machine Code Addendum for ECC GC27-2612
Safety Inspection GC28-6904
Safety Notices G229-9054
Service Guide for Trusted Key Entry Workstations GC28-6901
Chapter 8. Publications and Education
239
Copyright 2011 IBM Corporation. All rights reserved.
Service Guide (including PN 41U9438) GC28-6903
Statement of Limited Warranty GC28-6883
For IBM Redbooks publications, refer to:
• http://www.redbooks.ibm.com/
240
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Appendix A. MSU Values
The following table lists the MSU ratings for the z114 family of processors. For
accurate capacity planning, LSPR data should be the metric of choice in choosing
a valid solution.
Note: The IBM software pricing MSUs for other z servers can be located at the
following Web site:
• http://www.ibm.com/servers/eserver/zseries/library/swpriceinfo/
Table 37. 2818 MSU Ratings
Model
Capacity
Indicator
MSU
1-way
MSU
2-way
MSU
3-way
MSU
4-way
MSU
5-way
A0x
3
6
9
11
13
B0x
4
7
10
12
15
C0x
5
9
12
16
19
D0x
6
11
15
19
23
E0x
7
12
16
21
26
F0x
7
13
19
25
30
G0x
9
16
23
29
35
H0x
10
18
26
33
40
I0x
11
20
29
37
44
J0x
12
22
32
41
49
K0x
14
25
36
46
55
L0x
16
30
42
54
65
M0x
19
34
49
62
75
N0x
21
40
56
71
86
O0x
24
44
62
80
97
P0x
27
49
70
90
108
Q0x
31
56
80
102
123
R0x
34
62
88
113
136
S0x
38
69
98
125
151
T0x
42
77
110
140
170
U0x
49
88
125
161
194
Appendix A. MSU Values
241
Copyright 2011 IBM Corporation. All rights reserved.
242
Model
Capacity
Indicator
MSU
1-way
MSU
2-way
MSU
3-way
MSU
4-way
MSU
5-way
V0x
53
98
138
177
214
W0x
60
109
155
198
239
X0x
73
132
188
240
290
Y0x
86
156
221
283
343
Z0x
98
177
251
321
388
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Appendix B.
Cabling and Services
Fiber Optic Cable Orders
Fiber optic cables are available via IBM Networking Services
Refer to the services section of Resource Link (TM) for further details. Access
Resource Link at:
• www.ibm.com/servers/resourcelink
B.1 Services
IBM Networking Services has a comprehensive set of scalable solutions to
address IBM cabling requirements, from product-level to enterprise-level. IBM
Network Integration and Deployment Services for zSeries fiber cabling provides
planning and installation services for individual fiber optic connections. IBM
Network Integration and Deployment Services for enterprise fiber cabling
provides planning, IBM Fiber Transport System trunking components, and
installation services for small, medium, and large enterprises.
IGS has the expertise and personnel available to effectively plan and deploy the
appropriate cabling with the future in mind. These services may include planning,
consultation, cable selection, installation, and documentation, depending upon
the services selected.
These services are designed to be right-sized for your products or the end-to-end
enterprise, and to take into consideration the requirements for all of the protocols
and media types supported on zSeries (e.g. ESCON, FICON, Coupling Links,
OSA) whether the focus is the data center, the Storage Area Network (SAN), the
Local Area Network (LAN), or the end-to-end enterprise.
IBM Networking Services are designed to deliver convenient, packaged services
to help reduce the complexity of planning, ordering, and installing fiber optic
cables. The appropriate fiber cabling is selected based upon the product
requirements and the installed fiber plant.
The services are packaged as follows:
B.1.1 For the US, AP, LA
Under the zSeries fiber cabling services umbrella there are three options to
provide individual fiber optic cables (jumper cables, conversion kits, and MCP
cables) for connecting to z900, z800, z990, z890, z9, z10, z114 and z196, each
option incorporating a specific set of services.
• Option 1 - Fiber optic jumper cabling package. IBM does the detailed planning.
This option includes planning, new cables, installation, and documentation. An
analysis of the zSeries channel configuration, I/O devices, and any existing
fiber optic cabling is required to determine the appropriate fiber optic cables.
Appendix B. Cabling and Services
243
Copyright 2011 IBM Corporation. All rights reserved.
• Option 2 - Fiber optic jumper cable migration and reuse for a System z
upgrade. IBM organizes the existing fiber optic cables based upon the System
z connection details. Re-labeling, rerouting, and reconnection to the
appropriate channels is performed. New cables are not offered as a part of
this option.
• Option 3 - Fiber optic jumper cables and installation. The customer tells us
what they need. They do the detailed planning. The service includes new
cables, installation, and documentation. Planning and providing the list of
required cables are customer responsibilities.
Note: Options 1 and 2 can be combined within one statement of work to provide
comprehensive upgrade coverage.
Under the enterprise fiber cabling services umbrella there are two options to
provide IBM Fiber Transport System (FTS) trunking commodities (fiber optic trunk
cables, fiber harnesses, and panel-mount boxes) for connecting to the z900,
z800, z990, z890, z9, z10, z114 and z196.
• Option 1 - zSeries fiber optic trunk cabling package. IBM reduces the cable
clutter under the floor. An analysis of the zSeries (z900, z800, z990, z890, z9,
z10, z114 and z196) channel configuration and any existing fiber optic cabling
is performed to determine the required FTS fiber optic trunking commodities
(trunk cables, harnesses, and panel-mount boxes). This option includes
zSeries planning, FTS fiber optic trunking commodities, installation, and
documentation. This option does not include enterprise-level planning.
• Option 2 - Enterprise fiber cabling services. IBM organizes the entire
enterprise. This option includes enterprise planning, new cables, fiber optic
trunking commodities, installation, and documentation. This is IBM's most
comprehensive set of services.
B.1.2 For EMEA
Under the zSeries fiber cabling services umbrella there are two options to provide
individual fiber optic cables (jumper cables, conversion kits, and MCP cables) for
connecting to z900, z800, z990, z890, z9, z10, z114 and z196, each option
incorporating a specific set of services.
• Option 1 - Fiber optic jumper cabling package. IBM does the detailed planning.
This option includes planning, new cables, installation, and documentation. An
analysis of the zSeries channel configuration, I/O devices, and any existing
fiber optic cabling is required to determine the appropriate fiber optic cables.
• Option 2 - Fiber optic jumper cable migration and reuse for a zSeries upgrade.
This option includes planning, reuse of existing cables, and documentation.
IBM organizes the existing fiber optic cables based upon the zSeries
connection details. Relabeling, rerouting, and reconnection to the appropriate
channels is performed. New cables are not offered as a part of this option.
Options 1 and 2 can be combined within one statement of work to provide
comprehensive upgrade coverage.
Under the enterprise fiber cabling services umbrella there are two options to
provide IBM Fiber Transport System (FTS) trunking commodities (fiber optic trunk
cables, fiber harnesses, panel-mount boxes) for connecting to zSeries.
244
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
• Option 1 - zSeries fiber optic trunk cabling package. IBM reduces the cable
clutter under the floor. An analysis of the zSeries (z900, z800, z990, z890, z9,
z10, z114 and z196) channel configuration and any existing fiber optic cabling
is performed to determine the required FTS fiber optic trunking commodities
(fiber optic trunk cables, fiber harnesses, panel-mount boxes). This option
includes zSeries planning, FTS fiber optic trunking commodities, installation,
and documentation. This option does not include enterprise-level planning.
• Option 2 - Enterprise fiber cabling services. IBM organizes the entire
enterprise. This option includes enterprise planning, new cables, fiber optic
trunking commodities, installation, and documentation. This is IBM's most
comprehensive set of services.
B.2 Cabling Responsibilities
Fiber optic cables, cable planning, labeling, and placement are all customer
responsibilities for new installations and upgrades. Fiber optic conversion kits
and Mode Conditioning Patch (MCP) cables are not orderable as features on the
z114 and z196. Installation Planning Representatives (IPRs) and System Service
Representatives (SSRs) will not perform the fiber optic cabling tasks without a
services contract.
The following tasks are required to be performed by the customer prior to
machine installation:
• All fiber optic cable planning.
• All purchasing of correct fiber optic cables.
• All installation of any required Mode Conditioning Patch (MCP) cables.
• All installation of any required Conversion Kits.
• All routing of fiber optic cables to correct floor cutouts for proper installation to
server.
• Use the Physical Channel Identifier (PCHID) report or the report from the
Channel Path Identifier (CHPID) Mapping Tool to accurately route all
cables.
• All labeling of fiber optic cables with PCHID numbers for proper installation to
server.
• Use the PCHID report or the report from the CHPID Mapping Tool to
accurately label all cables.
Additional Charges
Additional service charges may be incurred during the server installation
if the above cabling tasks are not accomplished as required.
B.3 InfiniBand Cables
An OM3 50/125 micrometer (2000 MHz-km @ 850 nm) multimode fiber optic
cable with Multifibre Push On (MPO) connectors is used for 12x IB-DDR
connections for System z10 and System z9 servers.
Appendix B. Cabling and Services
245
Copyright 2011 IBM Corporation. All rights reserved.
The cable is an InfiniBand Trade Association® (IBTA) industry standard cable. It
contains one pair of fibers per lane for the 12x IB-DDR connection (resulting in 24
duplex fibers). The following is a picture of the cable:
Figure 3. InfiniBand Cable
The sender and receiver connectors are clearly marked with either RX or TX and
the connectors are keyed.
The following standard cable lengths are available from IBM Global Technology
Services (GTS) and Anixter:
• 10 meters (32.8 feet)
• 13 meters (42.7 feet)
• 15 meters (49.2 feet)
• 20 meters (65.6 feet)
• 40 meters (131.2 feet)
• 80 meters (262.4 feet)
• 120 meters (393.7 feet)
• 150 meters (492.1 feet)
Refer to the Physical Site Planning section of this SAPR guide for additional
information.
B.4 Connectors and Cabling
The following link is to a very informative reference for determining the cabling
connectors for various processors and features:
• http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD102278
B.5 Fiber Quick Connect (FQC)
FC7830, FC7832, FC7833, FC7834, FC7835, FC7836, FC7837, FC7901,
FC7920, FC7921, FC7998, FC8012 and FC8013.
246
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
The Fiber Quick Connect (FQC) features are optional features for factory
installation of the IBM Fiber Transport System (FTS) fiber harnesses for
connection to ESCON and FICON LX channels in an I/O cage or I/O drawer.
Fiber Quick Connect is for factory installation only, and is available on new
servers and on initial upgrades to z114 and z196. FQC is not available as an MES
to an existing z114 or z196. Each direct-attach fiber harness connects to six
ESCON or FICON LX channels at one end and one coupler in a Multi-Terminated
Push-On Connector (MTP) coupler bracket at the opposite end. Each bracket has
positions for 10 MTP connectors to be plugged, each MTP supporting 12 fiber
pairs (six ESCON or FICON LX channels), for a total of 120 fiber pairs for each
MTP coupler bracket.
When FQC is ordered, the configuration tool selects the required number of MTP
mounting brackets and mounting hardware based upon the ESCON and FICON
LX feature quantity.
Note: FQC supports all of the ESCON and FICON LX channels. FQC cannot be
ordered for selected channels.
B.6 Top exit I/O cabling (FC7920) and Top Exit Power Cords (FC7901)
On the z114 you now have the option of ordering the infrastucture to support top
exit of your fiber optic cables (ESCON, FICON, OSA, 12x InfiniBand, 1x
InfiniBand, and ISC-3), your copper cables for the 1000BASE-T Ethernet
features, as well as the I/O power cords.
Top exit I/O cabling and power cords are designed to provide you with an
additional option. Instead of all of your cables and power cords exiting under the
server and/or under the raised floor, you now have the flexibility to choose the
option that best meets the requirements of your data center. Top exit I/O cabling
and power cords can also help to increase air flow.
This option is offered on new build as well as MES orders.
B.6.1 Top exit power: This feature provides support for top exit line cords (FC7901)
• Minimum: None
• Maximum: One.
• Prerequisites: None
• Corequisites: None
• Compatibility Conflicts: None known.
• Customer Set-up: No.
• Limitations: If non-raised floor (#7998) is selected, along with top exit power
(#7901) must also have top exit I/O cabling (#7920). Refer to z114 Installation
Manual for Physical Planning, GC28-6907 for line cord assembly guidance.
There are unique line cords for top exit power.
• Field Installable: Yes. Parts removed as a result of feature conversions
become the property of IBM.
• Cable Order: Cabling is a customer responsibility.
Appendix B. Cabling and Services
247
Copyright 2011 IBM Corporation. All rights reserved.
B.6.2 Top exit I/O cabling (FC7920)
When top exit I/O cabling is selected on an order, the required infrastructure is
provided. Frame extensions are added to each corner of the system with this
option. Routing of cabling from I/O drawers will exit out the top of the frame.
Top exit I/O cabling applies to all of your fiber optic cables (ESCON, FICON,
OSA-Express, 12x InfiniBand, 1x InfiniBand, and ISC-3) as well as your copper
cables for the 1000BASE-T Ethernet features.
Top exit I/O cabling is designed to provide you with an additional option. Instead
of all of your cabling exiting under the server and/or under the raised floor, you
now have the flexibility to choose the option that best meets the requirements of
your data center. Top exit I/O cabling can also help to increase air flow.
• Minimum: None
• Maximum: One.
• Prerequisites: None
• Corequisites: None
• Compatibility Conflicts: Cannot coexist with side covers (#7921).
• Customer Set-up: No.
• Limitations: This feature #7920 is mutually exclusive with the side cover
feature (#7921). If #7920 is on the order, #7921 cannot be ordered.
• Field Installable: Yes. Parts removed as a result of feature conversions
become the property of IBM.
• Cable Order: Cabling is a customer responsibility.
B.7 FC8012 Frame bolt down kit, raised floor
This feature supplies the kit of parts that is designed to help secure the frame and
its contents from damage when exposed to vibrations and shocks such as those
in a seismic event. The 3n1 kit supplies parts to cover raised floor heights from 9
inches to 13 inches, 12 inches to 22 inches, and 12 inches to 36 inches. Service
personnel will select the parts that best match the customer's raised floor height.
• Minimum: None.
• Maximum: One.
• Prerequisites: Non-raised floor (#7998).
• Corequisites: None.
• Compatibility Conflicts: Features #8012 and #8013 are mutually exclusive with
each other.
• Customer Set-up: No.
• Limitations: None known.
• Field Installable: Yes. Parts removed as a result of feature conversions
become the property of IBM.
248
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
B.8 FC8013 Frame bolt down kit, non-raised floor
This feature supplies the kit of parts that is designed to help secure the frame and
its contents from damage when exposed to vibrations and shocks such as those
in a seismic event.
• Minimum: None.
• Maximum: One.
• Prerequisites: Non-raised floor support (#7998).
• Corequisites: None.
• Compatibility Conflicts: Features #8012 and #8013 are mutually exclusive with
each other.
• Customer Set-up: No.
• Limitations: None known.
• Field Installable: Yes. Parts removed as a result of feature conversions
become the property of IBM.
B.9 Installation Manual for Physical Planning (IMPP)
For further details also refer to the Installation Manual for Physical Planning
(IMPP), available on Resource Link.
Appendix B. Cabling and Services
249
Copyright 2011 IBM Corporation. All rights reserved.
250
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Appendix C. Capacity on Demand
C.1 Capacity on Demand - Temporary Capacity
Just-in-time deployment of the z196, z114 and System z10 Capacity on Demand
(CoD) is a radical departure from previous System z and zSeries servers. This
new architecture allows:
• Up to eight temporary records to be installed on the CEC and active at any
given time
• Up to 200 temporary records to be staged on the SE
• Variability in the amount of resources that can be activated per record
• The ability to control and update records independent of each other
• Improved query functions to monitor the state of each record
• The ability to add capabilities to individual records concurrently, eliminating
the need for constant ordering of new temporary records for different user
scenarios
• Permanent LIC-CC upgrades to be performed while temporary resources are
active
These capabilities allow customers to access and manage processing capacity
on a temporary basis, providing increased flexibility for on demand environments.
The CoD offerings are built from a common Licensed Internal Code Configuration
Code (LIC-CC) record structure. These Temporary Entitlement Records (TERs)
contain the information necessary to control which type of resource can be
accessed and to what extent, how many times and for how long, and under what
condition - test or real workload. Use of this information gives the different
offerings their personality.
Three types of temporary-capacity offerings will be available.
C.1.1 Capacity Back Up (CBU) Temporary access to dormant processing units (PUs), intended to replace
capacity lost within the enterprise due to a disaster. CP capacity or any and all
specialty engine types (zIIP, zAAP, SAP, IFL, ICF, SAP) can be added up to what
the physical hardware model can contain for up to 10 days for a test activation or
90 days for a true disaster recovery.
As of the April 2009 announcement on z10 and now on the z196 and z114:
• Change in the number of free CBU test activations. The number of free
CBU test activation is determined by the number of years that are
purchased with the CBU record. (For example, a three year CBU record
has three tests activations, a one year CBU record has one test
activation.)
• Ability to purchase additional CBU test activations beyond the free tests
in single increments up to a maximum of 15 CBU tests per record. This
is done with feature code (FC6805).
• Addition of a pre check function to help prevent conflicts between a
requested new permanent configuration and any currently active
temporary resources.
Appendix C. Capacity on Demand
251
Copyright 2011 IBM Corporation. All rights reserved.
Additional test activations may be ordered but a record can not contain more than
15 test activations. Each CBU record provides the entitlement to these resources
for a fixed period of time, after which the record is rendered useless. This time
period can span from 1 to 5 years and is specified through ordering quantities of
CBU years.
C.1.1.1 Restrictions
• Can not decrement capacity level
• Can not remove permanent engines from configuration
• No Tests while in Real activation
• No Tests if number of Real activations allowed equals zero. In other words, a
full disaster situation has been invoked.
• Auto deactivation of activated resources upon time limit. The machine will not
enter a “slow-down” mode requiring a POR to recover as on previous
generation machines.
• If any resource can not be removed all resources stay active
• Ability to remove resources checked every 24 hours
C.1.2 Capacity for Planned Events (CPE) Temporary access to dormant PUs, intended to replace capacity lost within the
enterprise due to a planned event such as a facility upgrade or system relocation.
This offering is available only on the z196, z114, z10 BC or System z10 EC. CPE
is similar to CBU in that it is intended to replace lost capacity; however, it differs
in its scope and intent. Where CBU addresses disaster recovery scenarios that
can take up to three months to remedy, CPE is intended for short-duration events
lasting up to 3 days, maximum. Depending on the capacity ordered, a CPE
record, once activated, could provide you access to all dormant PUs on the
machine that can be configured in any combination of CP capacity or specialty
engine types (zIIP, zAAP, SAP, IFL, ICF, SAP).
C.1.2.1 Restrictions
• Can not decrement capacity level
• Can not remove permanent engines from configuration
• Auto deactivation of activated resources upon time limit
• If any resource can not be removed all resources stay active
• Ability to remove resources checked every 24 hours
• All dormant resources are available for use during the activation
8.2.0.1 CPE ordering
CPE allows you to select the capacity to meet your business needs.
Capacity for Planned Event features (FC0116 - FC0128):
1 CPE Capacity Unit - FC0116
100 CPE Capacity Unit - FC0117
10000 CPE Capacity Unit - FC0118
1 CPE Capacity Unit-IFL - FC0119
100 CPE Capacity Unit-IFL - FC0120
1 CPE Capacity Unit-ICF - FC0121
252
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
100 CPE Capacity Unit-ICF - FC0122
1 CPE Capacity Unit-zAAP - FC0123
100 CPE Capacity Unit-zAAP - FC0124
1 CPE Capacity Unit-zIIP - FC0125
100 CPE Capacity Unit-zIIP - FC0126
1 CPE Capacity Unit-SAP - FC0127
100 CPE Capacity Unit-SAP - FC0128
FC6833 - Capacity for Planned Event (CPE): This feature code corresponds to
the number of different CPE Temporary Entitlement Records (TERs) ordered.
•
•
•
•
•
•
Minimum: None.
Maximum: Eight (8) per ordering session.
Prerequisites: None.
Corequisites: CPE authorization (#9912).
Compatibility Conflicts: None known.
Customer Setup: The CBU TER must be installed via the HMC
Configuration Manager before it can be activated.
• Limitations: None.
• Field Installable: Yes.
FC0116 - 1 CPE Capacity Unit: Pricing feature code equal to the remainder of
three days multiplied by the number of CPE Capacity Units divided by 100
purchased in a given Capacity for Planned Event record.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: None.
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0117 - 100 CPE Capacity Unit: Pricing feature equal to the quotient of three
days multiplied by the number of CPE Capacity Units purchased in a given
pre-paid Capacity for Planned Event record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: # 0116
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0118 - 10000 CPE Capacity Unit: Pricing feature equal to the quotient of
three days multiplied by the number of CPE Capacity Units purchased in a given
pre-paid Capacity for Planned Event record divided by 10,000.
•
•
•
•
•
Minimum: None.
Maximum: 250
Prerequisites: # 0117
Corequisites: # 6833
Compatibility Conflicts: None known.
Appendix C. Capacity on Demand
253
Copyright 2011 IBM Corporation. All rights reserved.
• Customer Setup: NA.
• Limitations: None.
• Field Installable: Yes.
FC0119 - 1 CPE Capacity Unit-IFL: Pricing feature equal to the remainder of the
three days multiplied by the number of temporary Integrated Facility for Linux
(IFL) features in a given Capacity for Planned event record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: None.
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0120 - 100 CPE Capacity Unit-IFL: Pricing feature equal to the quotient of
three days multiplied by the number of temporary Integrated Facility for Linux
(IFL) features in a given Capacity for Planned event record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 1
Prerequisites: # 0119
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0121 - 1 CPE Capacity Unit-ICF: Pricing feature equal to the remainder of the
three days multiplied by the number of temporary Internal Coupling Facility (ICF)
features in a given Capacity for Planned event record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: None.
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0122 - 100 CPE Capacity Unit-ICF: Pricing feature equal to the quotient of
three days multiplied by the number of temporary Internal Coupling Facility (ICF)
features in a given Capacity for Planned event record divided by 100.
•
•
•
•
•
•
•
•
254
SA11-002-02
Minimum: None.
Maximum: 1
Prerequisites: # 0121
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
Copyright 2011 IBM Corporation. All rights reserved.
FC0123 - 1 CPE Capacity Unit-zAAP: Pricing feature equal to the remainder of
the three days multiplied by the number of temporary System z Application Assist
Processor (zAAP) features in a given Capacity for Planned event record divided
by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: None.
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0124 - 100 CPE Capacity Unit-zAAP: Pricing feature equal to the quotient of
three days multiplied by the number of temporary System z Application Assist
Processor (zAAP) features in a given Capacity for Planned event record divided
by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 1
Prerequisites: # 0123
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0125 - 1 CPE Capacity Unit-zIIP: Pricing feature equal to the remainder of
the three days multiplied by the number of temporary System z Integrated
Information Processor (zIIP) features in a given Capacity for Planned event
record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: None.
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0126 - 100 CPE Capacity Unit-zIIP: Pricing feature equal to the quotient of
three days multiplied by the number of temporary System z Integrated
Information Processor (zIIP) features in a given Capacity for Planned event
record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 1
Prerequisites: # 0125
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
Appendix C. Capacity on Demand
255
Copyright 2011 IBM Corporation. All rights reserved.
FC0127 - 1 CPE Capacity Unit-SAP: Pricing feature equal to the remainder of
the three days multiplied by the number of temporary System Assist Processor
(SAP) features in a given Capacity for Planned event record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 99
Prerequisites: None.
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
FC0128 - 100 CPE Capacity Unit-SAP: Pricing feature equal to the quotient of
three days multiplied by the number of temporary System Assist Processor (SAP)
features in a given Capacity for Planned event record divided by 100.
•
•
•
•
•
•
•
•
Minimum: None.
Maximum: 1
Prerequisites: # 0127
Corequisites: # 6833
Compatibility Conflicts: None known.
Customer Setup: NA.
Limitations: None.
Field Installable: Yes.
C.1.3 On/Off Capacity on Demand (On/Off CoD)
Temporary access to dormant PUs, intended to augment the existing capacity of
a given system. On/Off CoD helps you contain workload spikes that may exceed
permanent capacity such that Service Level Agreements cannot be met and
business conditions do not justify a permanent upgrade.
An On/Off CoD record allows you to temporarily add CP capacity or any and all
specialty engine types (zIIP, zAAP, SAP, IFL, ICF, SAP) up to the following limits:
• The quantity of temporary CP capacity ordered is limited by the quantity of
purchased CP capacity (permanently active plus unassigned).
• The quantity of temporary IFLs ordered is limited by quantity of purchased
IFLs (permanently active plus unassigned).
• Temporary use of unassigned CP capacity or unassigned IFLs will not incur a
hardware charge. There is no hardware charge for capacity below the
high-water-mark on the z196, z114, z10 BC or z10 EC (unlike the IBM System
z9).
• The quantity of permanent zIIPs plus temporary zIIPs can not exceed the
quantity of purchased (permanent plus unassigned) CPs plus temporary CPs
and the quantity of temporary zIIPs can not exceed the quantity of permanent
zIIPs.
• The quantity of permanent zAAPs plus temporary zAAPs can not exceed the
quantity of purchased (permanent plus unassigned) CPs plus temporary CPs
and the quantity of temporary zAAPs can not exceed the quantity of
permanent zAAPs.
256
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
• The quantity of temporary ICFs ordered is limited by the quantity of permanent
ICFs as long as the sum of permanent and temporary ICFs is less than or
equal to 5.
Although the z196 and z114 will allow up to eight temporary records of any type
to be installed, only one temporary On/Off CoD record may be active at any given
time. An On/Off CoD record may be active while other temporary records are
active.
C.1.3.1 Restrictions
• Can not decrement capacity level
• Can not remove permanent engines from configuration
• Positive increase in capacity with temporary activations
C.1.4 On/Off Capacity on Demand Tokens (Pre-paid On/Off CoD)
This is also known as Capacity Provisioning Phase 2 on the z10.
Before Capacity Provisioning Phase 2, customers were charged for temporary
hardware after the On/Off CoD record has been activated. With Phase 2,
customers can now pre-pay for temporary capacity.
Capacity Provisioning Phase 2 is designed to provide the customer the means to
limit their financial liability by automatically deactivating resources through the
use of capacity tokens. Customers are assigned tokens through the order
process. On/Off CoD Tokens can be purchased and “banked” by the customer.
The CEC will manage the use and consumption of tokens.
Tokens can be purchased for any speciality engine (per day of use) or for CP
capacity (MSU’s per day of use). Each day of usage (times the amount of
capacity activated) will decrement the token pool available for future On/Off
Temporary Capacity on Demand activations of the specific temporary record.
On/Off CoD and related tokens can only be ordered via ResourceLink by the
customer.
There is no scheduled expiration date for pre-paid tokens (true of CP MSU’s
also). Tokens decrement as used, but they can be replenished to add capacity
and/or days as needed. Auto deactivation will be attempted after all tokens have
been used.
On/Off CoD Tokens for Specialty Processors
On/Off CoD Tokens can be used for IFLs, ICFs, zIIPS, or zAAPs. Each day of use
of one of the specialty processors (such as an IFL) might be called - 1-IFL-Day.
Each pre-paid token permits the use of 1 IFL for 1 day.
Example: The customer might pre-pay for 5 IFL’s for a period of 20 days. So, 5
IFL day engines for 20 days (5x20=100 tokens).
Now, if the customer activates just 2 IFL’s for 5 days, (2x5=10 tokens) 10 of the
100 tokens are used. Now the customer has 90 IFL-day tokens remaining for a
future activation.
Appendix C. Capacity on Demand
257
Copyright 2011 IBM Corporation. All rights reserved.
Once all tokens are used, On/Off CoD will attempt to automatically remove the
temporary activated IFLs. After auto deactivate, you may re-activate those
resources that still have tokens left (remaining zIIP tokens for example).
There is no expiration date associated with On/Off CoD Tokens. Post-paid On/Off
CoD expiration dates remain, but tokens can also be used with post paid On/Off
CoD. Also, the customer can request that the expiration date be automatically
replenished on the z196 and z114.
Tokens decrement as they are used. Token pools can be replenished on
ResourceLink to increase a specialty engine-day pool.
Tokens are always purchased via ResourceLink (not e-Config).
On/Off CoD Tokens for Central Processors
Pre-paid On/Off CoD Tokens can also be purchased for central processors. They
are measured as CP-MSU-Days. An MSU-Day equals the peak MSU value
activated during a 24 hour period. (CI=Capacity Indicator)
An x-value of tokens are decremented where x is the CP MSU days deltas
between max purchased base capacity and the currently active On/Off Capacity
on Demand record.
The customer is permitted to temporarily activate up to two times their purchased
capacity. Once all tokens are used, On/Off CoD will attempt to automatically
remove the temporary CPs.
CP - High Water Mark with On/Off CoD Tokens
A z196 and z114 can be ordered with a high water mark of a higher capacity
indicator than the base configuration that is delivered. This permits a customer to
purchase more capacity than initially needed on day one. The pre-purchased
permanent capacity can be turned on later with LIC-CC.
When using temporary CP Tokens, there is NO reduction of tokens as long as the
temporary activation is less than the high water mark.
C.1.4.1 On/Off CoD Token Feature Codes
(#9917) 1 MSU-day: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary Central Processor (CP) resource
tokens purchased through Resource Link.
(#9918) 100 MSU-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased
through Resource Link.
(#9919) 10,000 MSU-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased
through Resource Link.
(#9920) IFL-day: Pricing feature is used to facilitate the billing of On/Off Capacity
on Demand (On/Off CoD) temporary Integrated Facility for Linux (IFL) resource
tokens purchased through Resource Link.
258
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
(#9921) 100 IFL-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary IFL resource tokens purchased
through Resource Link.
(#9922) 1 ICF-day: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary Internal Coupling Facility (ICF)
resource tokens purchased through Resource Link.
(#9923) 100 ICF-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary ICF resource tokens purchased
through Resource Link.
(#9924) 1 zIIP-day: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary System z Integrated Information
Processor (zIIP) resource tokens purchased through Resource Link.
(#9925) 100 zIIP-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary zIIP resource tokens purchased
through Resource Link.
(#9926) 1 zAAP-day: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary System z Application Assist
Processor (zAAP) resource tokens purchased through Resource Link.
(#9927) 100 zAAP-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary zAAP resource tokens purchased
through Resource Link.
(#9928) 1 SAP-day: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary System Assist Processor (SAP)
resource tokens purchased through Resource Link.
(#9929) 100 SAP-days: Pricing feature is used to facilitate the billing of On/Off
Capacity on Demand (On/Off CoD) temporary SAP resource tokens purchased
through Resource Link.
C.1.5 Capacity provisioning An installed On/Off CoD record is a necessary prerequisite for automated control
of temporary capacity through z/OS MVS Capacity Provisioning. z/OS MVS
Capacity Provisioning allows you to set up rules defining the circumstances under
which additional capacity should be provisioned in order to fulfill a specific
business need. The rules are based on criteria, such as: a specific application,
the maximum additional capacity that should be activated, time and workload
conditions. This support provides a fast response to capacity changes and
ensures sufficient processing power will be available with the least possible delay
even if workloads fluctuate. See z/OS MVS Capacity Provisioning User's Guide
(SA33-8299) for more information.
C.1.6 On/Off CoD Test On/Off CoD allows for a no-charge test. No IBM charges are assessed for the
test, including IBM charges associated with temporary hardware capacity, IBM
software, or IBM maintenance. This test can be used to validate the processes to
Appendix C. Capacity on Demand
259
Copyright 2011 IBM Corporation. All rights reserved.
download, stage, install, activate, and deactivate On/Off CoD capacity
nondisruptively.
Each On/Off CoD-enabled server is entitled to only one no-charge test. This test
may last up to a maximum duration of 24 hours commencing upon the activation
of any capacity resources contained in the On/Off CoD record. Activation levels of
capacity may change during the 24 hour test period. The On/Off CoD test
automatically terminates at the end of the 24 hours period. In addition to
validating the On/Off CoD function within your environment, you may choose to
use this test as a training session for your personnel who are authorized to
activate On/Off CoD.
8.2.1 On/Off CoD Administrative Test There were administrative tests available on the z9. The administrative tests are
not allowed on the z10, but this is again possible on the z196 and z114.
No charge administrative tests enabled customers to order 'zero' quantity
features and go through the entire order, download and activate steps. This
provides a method for operator training and the test can be performed multiple
times.
APIs can also be used to with administrative tests.
See the zEnterprise Capacity on Demand User's Guide SC28-2605 for complete
details.
260
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
C.2 Temporary Capacity Enablement Features
As a basis for ordering any CoD feature, enablement features must be in place.
Table 38. Temporary Capacity Enablement Features
Feature Code
Description
Comment
9900
On line CoD Buying
Drives contract to cover terms of use to place
orders through Resource Link. FC 9900 is a
pre-req to using ResourceLink for CIU and
On/Off CoD.
9910
CBU Enablement
Drives contract addendum to cover terms of use
for CBU. This feature is generated when Capacity back up (#6818) is ordered, or it can be ordered by itself. This feature along with On Line
Capacity on Demand (#9900) is required to order CBU through Resource Link.
9912
Capacity for
Planned Event
Enablement
Drives contract addendum to cover terms of use
for Capacity for Planned Event
9896
On/Off CoD Enablement
Drives contract addendum to cover terms of use
for On/Off CoD order and downloads via ResourceLink.
9898
CIU Enablement for
permanent upgrades
Drives contract addendum to cover terms of use
for CIU order and downloads via ResourceLink.
C.3 CBU (Capacity Backup Upgrade)
Table 39.
Feature
Code
Description
Comment
6805
Additional CBU Test
activations.
Additional test activations are available in quantities of one
(FC6805) and the number of test activations remains limited at 15 per CBU entitlement record (FC6818).
Appendix C. Capacity on Demand
261
Copyright 2011 IBM Corporation. All rights reserved.
Feature
Code
Description
Comment
6817
Total CBU Years Ordered
Used to set record expiration date, to calculate Pricing FCs,
included on contract supplement. min/max =1/5.
Notes as of the April 2009 z10 (applicable to the z196 and
z114) announcement:
1. Rather than a fixed default number of five test activations for each CBU entitlement record (FC6818), the number of test activations per instance of FC6818 will coincide
with the number of CBU years. That is, FC6817 equals the
number of years assigned to the CBU record. This equates
to one test activation per year for each CBU entitlement
purchased. Additional tests can be purchased with FC6805.
2. On system z10 the CBU entitlement records (FC6818)
contain an expiration date that is established at the time of
order and is dependent upon the quantity of CBU years
(FC6817). You now have the capability to extend your
CBU entitlements through the purchase of additional CBU
years. The number of FC6817 per instance of FC6818
remains limited to five and fractional years are rounded up
to the near whole integer when calculating this limit. For
instance, if there are two years and eight months to the
expiration date at the time of order, the expiration date can
be extended by no more than two additional years.
One test activation is provided for each additional CBU
year added to the CBU entitlement record.
6818
CBU Records Ordered
CBU Anchor Record
min/max=0/1
6819
5 Additional CBU Tests
5 initial tests w/contract, min/max=0/2 for new build,
0/3 for replenishment MES This feature was replaced by FC6805
with the April 2009 z10 announcement. Also, by default there is
one CBU test per year per each CBU Record.
6820
Single CBU CP-Year
Assigned Pricing (FC 6817 qty x COD0CP qty
6821
25 CBU CP-Year
Assigned Pricing (FC 6817 qty x COD0CP qty)
divided by 25
262
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Feature
Code
Description
Comment
6822
Single CBU IFL-Year
Assigned Pricing (FC 6817 qty x CODIFL qty)
6823
25 CBU IFL-Year
Assigned Pricing (FC 6817 qty x CODIFL qty)
divided by 25
6824
Single CBU ICF-Year
Assigned Pricing (FC 6817 qty x CODICF qty)
6825
25 CBU ICF-Year
Assigned Pricing (FC 6817 qty x CODICF qty)
divided by 25
6826
Single CBU zAAP-Year
Assigned Pricing (FC 6817 qty x CODAAP qty)
6827
25 CBU zAAP-Year
Assigned Pricing (FC 6817 qty x CODAAP qty)
divided by 25
6828
Single CBU zIIP-Year
Assigned Pricing (FC 6817 qty x CODIIP qty)
6829
25 CBU zIIP-Year
Assigned Pricing (FC 6817 qty x CODIIP qty)
divided by 25
6830
Single CBU SAP-Year
Assigned Pricing (FC 6817 qty x CODSAP qty)
6831
25 CBU SAP-Year
Assigned Pricing (FC 6817 qty x CODSAP qty)
divided by 25
6832
CBU Replenishment
Customer selects to reactivate record. Triggers
MFG to set activation bit back to “00”
6837
Feature Converted CBU
CP
Used only on upgrade from z9 or z990
From z990 CP, z9 CP7, CP6, CP5 or CP4
6838
Feature Converted CBU
IFL
Used only on upgrade from z9 or z990
6839
Feature Converted CBU
ICF
Used only on upgrade from z9 or z990
6840
Feature Converted CBU
zAAP
Used only on upgrade from z9 or z990
6841
Feature Converted CBU
zIIP
Used only on upgrade from z9 or z990
6842
Feature Converted CBU
SAP
Used only on upgrade from z9 or z990
Appendix C. Capacity on Demand
263
Copyright 2011 IBM Corporation. All rights reserved.
C.4 Capacity on Demand - Permanent Capacity
C.4.1 Customer Initiated Upgrade (CIU) facility
When a business needs additional capacity quickly, Customer Initiated Upgrade
(CIU) is designed to deliver it. CIU is designed to allow you to respond to sudden
increased capacity requirements by requesting a z196, z114 or System z10 PU
and/or memory upgrade via the Web, using IBM Resource Link, and downloading
and applying it to your server using your system's Remote Support connection.
Further, with the Express option on CIU, an upgrade may be made available for
installation as fast as within a few hours after order submission.
C.4.2 Permanent upgrades
Orders (MESs) of all PU types and memory for z196, z114 and z10 servers that
can be delivered by Licensed Internal Code, Control Code (LIC-CC) are eligible
for CIU delivery. CIU upgrades may be performed up to the maximum available
processor and memory resources on the installed server, as configured. While
capacity upgrades to the server itself are concurrent, your software may not be
able to take advantage of the increased capacity without performing an Initial
Programming Load (IPL).
8.2.2 CIU enhancement (on z196 and z114 only)
Purchase of permanent unassigned engines On permanent engine purchased, Resource Link will provide the customer with
the options to adjust the active capacity mark.
264
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
On z10, via CIU, you can add active engines or activate already purchased, but
not inactive (unassigned) engines or deactivate engines. Also, deactivation of
engines is a priced transaction. All transactions must be separate and distinct.
This can cause a lot of time to be added to multiple orders and changes.
The z196 and z114 Customer Initiated Upgrade (CIU) has been enhanced with
the following:
• On permanent engine purchased, Resource Link will provide the customer
with the options to adjust the active capacity mark
• Customers will be billed for purchase of new engines
• No charges made for deactivation of the capacity
• Hardware billing request will contain necessary Feature Codes to indicate
new capacity level.
Appendix C. Capacity on Demand
265
Copyright 2011 IBM Corporation. All rights reserved.
266
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Appendix D.
Installation Practices and Policies
It is important that there is agreement and understanding between the customer
and the IBM team as to what items are covered as part of normal warranty
provisions and those that will require a services contract.
Table 40. Scenario #1 - New Build, Net Add
Cabling Service
Contract Exists
Installation Tasks
Services
Responsibilities
Under Contract
Customer
Responsibilities
Yes
No Planning or
Perform Work for
Cabling
All cable planning
and perform work
(including picking,
reading and
plugging of each
cable into channel
card)
None
No
Pick, read and plug
of cables into card
from proper
machine cable
opening (1.3
minutes per cable)
Not Applicable
All planning and
perform work (route
to proper machine
tailgate, label.)
except pick, read &
plug
Table 41. Scenario #2 - Push-Pull (New Build or MES)
Cabling Service
Contract Exists
Installation Tasks
Services
Responsibilities
Under Contract
Customer
Responsibilities
Yes for new cables
Pick, read and plug
of EXISTING cables
ONLY into card from
proper machine
cable opening (1.3
minutes per cable)
All Planning and
Perform work of
NEW cables ONLY
(including pick, read
& plug)
All planning and
perform work of
EXISTING cables
(route to proper
machine tailgate,
label) except pick,
read & plug
Yes for EXISTING
Cables
Pick, read and plug
of NEW cables
ONLY into card from
proper machine
cable opening (1.3
minutes per cable)
All Planning and
Perform work of
EXISTING cables
ONLY (including
pick, read & plug)
All planning and
perform work of
NEW cables (route
to proper machine
tailgate, label.)
except pick, read &
plug
Yes for NEW AND
EXISTING Cables
No Planning or
Perform Work for
Cabling
All cable planning
and perform work for
ALL (both new and
existing) (including
picking, reading and
plugging of each
cable into channel
card)
None
Appendix D. Installation Practices and Policies
267
Copyright 2011 IBM Corporation. All rights reserved.
Cabling Service
Contract Exists
Installation Tasks
Services
Responsibilities
Under Contract
Customer
Responsibilities
No
Pick, read & plug of
ALL cables (both
new and existing)
from proper
machine cable
opening (1.3
minutes per cable)
Not Applicable
All planning and
perform work of ALL
cables (both new &
existing), (route to
proper machine
tailgate, label.)
except pick, read &
plug
Table 42. Scenario #3 - Consolidation of Multiple Machines
268
SA11-002-02
Cabling Service
Contract Exists
Installation Tasks
Services
Responsibilities
Under Contract
Customer
Responsibilities
YES (NEW Cables)
Pick, read and plug
of EXISTING Cables
from proper
machine cable
opening (1.3
minutes per cable)
All Planning &
Perform Work of
NEW Cables
(including pick, read
and plug)
All Planning &
Perform work (route
to proper machine
tailgate, label) for
EXISTING cables
YES (EXISTING
Cables)
Pick, read and plug
of NEW Cables from
proper machine
cable opening (1.3
minutes per cable)
All Planning &
Perform Work of
EXISTING Cables
(including pick, read
and plug)
All Planning &
Perform work (route
to proper machine
tailgate, label) for
NEW cables
YES (BOTH NEW
AND EXISTING
Cables)
No Planning or
Perform Work for
Cabling
All Planning &
Perform Work of
BOTH NEW AND
EXISTING Cables
(including pick, read
and plug)
None
No
Pick, read & plug of
ALL cables (both
new & existing) from
proper machine
cable opening (1.3
minutes per cable)
Not Applicable
All Planning &
Perform work (route
to proper machine
tailgate, label) for
ALL cables (both
new and existing)
except pick, read &
plug
Copyright 2011 IBM Corporation. All rights reserved.
Appendix E. Crypto Planning
E.1 CCF to PCI Migration Considerations
Customers migrating from a machine that uses the Cryptographic Coprocessor
Facility (CCF on z800/z900 and earlier) should be aware of potential performance
differences when doing cryptography on the CPACF based machines (z890, z990
and z9 (EC and BC) and z10 (EC and BC). Some of the functions supported on
the CCF (which is part of the MCM) have been moved to the Crypto Express2
which is a PCI card installed in the I/O cage. A limited set of functions from the
CCF are available on the CPACF which will provide better performance than the
PCI cards.
For example, the secure key encryption and decryption APIs (CSNBENC/1,
CSNBDEC/1) and PIN and MAC functions are now supported on the PCI cards
and depending on how the APIs are invoked (blocksizes, application logic,
parameters) and what is measured (CPU vs. wall-clock time), response time may
be significantly slower than on the CCF.
The clear key encryption and decryption APIs (CSNBSYD/1, CSNBSYE/1) are
new on the CPACF and should perform as well or better than the secure key
encryption and decryption APIs on the CCF.
Performance for the hashing APIs will be about the same for APIs handled in
software (MD5 and RIPEMD-160), and since SHA is now done on the CPACF, it
will be faster than on a CCF.
There are two ways to improve performance for APIs that are slower on the PCI
cards. First, using the Clear Key APIs which run on the CPACF will greatly
improve performance versus the Secure Key APIs, but is appropriate if the
customer's encryption environment allows the use of Clear Key APIs. Second,
the customer may need to modify their application to use multi-threading to take
advantage of the multiprocessing capability of the crypto cards. If the application
is single threaded using only one CCF, then the application should be modified to
use multi-threading and take advantage of the multiple crypto engines to drive
workload and increase throughput. Depending on the complexity of the
application, this may not be a trivial change. In addition, large blocking tends to
be more efficient, and the customer should consider using large blocksizes when
using the secure key encryption and decryption APIs.
Finally, for SSL, if the SSL volume was low, and the customer was using only
software in a CCF environment, then they may continue to use software on the
CPACF based machines. In this environment, they will see a slight improvement
in performance when using the clear key encryption/decryption APIs mentioned
above on the CPACF (for the record level component of SSL). That improvement
would be overwhelmed by the slower performance of the handshakes in software.
If the customer required a PCICC or PCICA to support SSL volumes, then they
will likely require a Crypto Express2 on the CPACF based machines. If the SSL
volume was being handled only on the CCF (no PCICC, PCICA and too much
volume for software alone), then they should consider using a Crypto Express2 in
the CPACF environment. If the customer had a PCICA installed to support SSL
volumes on their current machine, that PCICA can not be moved forward to the
Appendix E. Crypto Planning
269
Copyright 2011 IBM Corporation. All rights reserved.
new processor. Customers should instead consider adding a Crypto Express2
and configuring it as an accelerator.
E.2 References
The following web site should be reviewed as part of crypto planning. Use the
search word “crypto” for a list of informative documents.
• http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs
270
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Appendix F. Actions requiring an outage
The following table attempts to identify machine changes and actions that will
require an outage. It is intended to be as inclusive as possible but in the final
analysis the MES or Installation instructions should be reviewed well ahead of the
planned implementation to ensure that any requirements can be accommodated
either concurrently or within the outage time limits. e-config should also indicate
whether an outage is required in the output listing.
Table 43. Outage Actions
Action
Outage Type
Loading a new IOCDS
Power on Reset
Adding an additional I/O cage
Power on Reset, Long Outage
Adding storage to a partition following a
concurrent memory upgrade if the Reserved
value has not been specified.
Deactivate and Activate of the partition
(Requires changing the image profile)
Loading a new level of the machine driver
May require a Power on Reset. It is strongly
recommended that customers take
advantage of the Enhanced Driver
Maintenance capability by staying current
with released maintenance MCLs and
bundles.
Updating machine with disruptive patches (if
any)
Power on Reset
Storage upgrades which require larger size
cards for a single book model.
Power on Reset
Changing PU usage in a partition from
dedicated to shared or shared to dedicated.
IPL of the partition
Other as may be indicated in the MES or
upgrade instructions or other
determining circumstances.
F.1 What about an outage in a member of a multi-node Ensemble?
Given the following 2-node Ensemble:
z114 (A) with attached zBX having POWER7 blades that access data. Also, the
zBX is cabled to customer existing external network.
z114 (B) with no zBX. It is cabled to the z114 (A) zBX.
If z116 (A) goes down with a complete outage, will it's zBX POWER7 blades
continue to have access to data via z114 (B)? If so, is it transparent to the
POWER7 application(s)?
Answer:
Yes, processing continues transparently. The only issue, and it's minor, would be
if z114 (A) lost power and its Support Element lost power along with it. In that
case, no new management actions could be initiated against the zBX resources
Appendix F. Actions requiring an outage
271
Copyright 2011 IBM Corporation. All rights reserved.
until Support Element power is restored, but existing operations would continue
unimpeded.
272
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Appendix G. Special notices
This publication is intended to help IBM personnel and customers who are
planning the installation/implementation of an IBM z114 processor complex. The
information in this publication is not intended as the specification of any
programming interfaces that are provided by the z114 architecture. See the
PUBLICATIONS section for more information about what publications are
available and 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.
The information contained in this document has not been submitted to any formal
IBM test and is distributed AS IS. The information about non-IBM ("vendor")
products in this manual has been supplied by the vendor and IBM assumes no
responsibility for its accuracy or completeness. 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.
Any performance data contained in this document was determined in a controlled
environment, and therefore, the results that may be obtained in other operating
environments may vary significantly. Users of this document should verify the
applicable data for their specific environment.
Reference to PTF numbers that have not been released through the normal
distribution process does not imply 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.
Appendix G. Special notices
273
Copyright 2011 IBM Corporation. All rights reserved.
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
IBM 
The following terms are trademarks of other companies:
Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anything.
Anywhere.,TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli,
and Tivoli Enterprise are trademarks or registered trademarks of Tivoli Systems
Inc., an IBM company, in the United States, other countries, or both. In Denmark,
Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.
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.
274
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
Index
Numerics
Processor Features 6
S
2819-GEC 26
SCRT 75
SMP/E 3.5 30
C
T
Capacity Back Up (CBU) - 233
Capacity for Planned Events (CPE) - 234
Capacity on Demand 233
Capacity on Demand - Permanent Capacity 246
Capacity provisioning 241
Channels - Coupling Links 21
Channels - ESCON 13
Channels - FICON 13
Channels - OSA 15
CP - High Water Mark with On/Off CoD Tokens 240
Cryptography 25
Customer Initiated Upgrade (CIU) facility 246
Temporary Capacity Enablement Features 243
D
Dynamic ICF Expansion 80
F
Flexible memory 9
H
HMC LAN 54
I
IBM z196 BladeCenter Extension (zBX) 2
Independent Software Vendors (ISV) 44
Installation Checklists 55, 181
IO Channel Features 10
M
Memory 8
MSU 223
Must-Read Information 107, 197
O
On/Off Capacity on Demand (On/Off CoD) 238
On/Off CoD Administrative Test 242
On/Off CoD Test 241
On/Off CoD Tokens for Central Processors 240
Open Exchanges 123, 203
Operating System Support 34
Operating System Support Overview 27
P
Permanent upgrades
246
Physical Site Planning 47
Plan Ahead Memory 9
Processor and Book Details 6
275
Copyright 2011 IBM Corporation. All rights reserved.
276
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
IBM SAPR Guides evaluation
IBM 2818 Systems Assurance Product Review (SAPR) Guide SA11-002-02
Your feedback is very important to help us maintain the quality of IBM SAPR Guides. Please complete this
questionnaire and return it using one of the following methods:
• Complete this form and mail it to:
IBM Corporation
Systems Assurance Program Administrator
IBM Global Services, PSS
4111 Northside Parkway H07R01
Atlanta, GA 30327
• Fax this form to: USA International Access Code 1-404-238-4061
• Comments or errors can also be sent directly to the author Paul S Hagen (hagen@us.ibm.com)
Which of the following best describes you?
Business Partner
_ Solution Developer
above
_ IBM employee
_ None of the
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 SAPR Guide published in time for your needs?
Yes___ No___
If no, please explain:
What other SAPR Guides would you like to see published?
Comments/Suggestions:
© Copyright IBM Corp. 2011
(THANK YOU FOR YOUR FEEDBACK!)
277
Copyright 2011 IBM Corporation. All rights reserved.
278
SA11-002-02
Printed in the U.S.A.
2818 Systems Assurance Product Review (SAPR) Guide SA11-002-02
SA11-002-02
SA11-002-02
Copyright 2011 IBM Corporation. All rights reserved.
280
SA11-002-02