Page 1 System z9 Processor Resource/Systems Manager Planning Guide SB10-7041-03...
Page 3 System z9 Processor Resource/Systems Manager Planning Guide SB10-7041-03...
Page 4 There may be a newer version of this document in PDF format available on Resource Link . Go to http://www.ibm.com/servers/resourcelink and click on Library on the navigation bar. A newer version is indicated by a lower-case alphabetic letter following the form number suffix (for example: 00a, 00b, 01a, 01b).
Page 6 Version 5 Utilizing IFL Features ....2-60 System z9 Application Assist Processor (zAAP) ... . 2-60 IBM System z9 Integrated Information Processor (zIIP) .
Page 7 Chapter 3. Determining the Characteristics of Logical Partitions ..3-1 Planning Overview ..... . . 3-4 Performance Considerations .
Page 8 Trusted Configuration ..... . B-2 System z9 PR/SM Characteristics ....B-4 Central and Expanded Storage .
Page 9: Figures
3-20. ESA Mode Logical Partition with shared Central Processors (CPs), Integrated Facilities for Applications (IFAs) and System z9 Integrated Information Processors (zIIPs) ..3-63 3-21. Customization for a Linux-Only Mode Logical Partition with shared Integrated Facilities for Linux (IFLs).
Page 10 3-26. Load Page, Image Profile ......3-75 3-27. Crypto Page, Image Profile ......3-77 3-28.
Page 11 Terminology Used in This Publication ..... . xvii 1-1. CPU IDs for a z9 EC ......1-23 2-1.
Page 12 PR/SM Planning Guide...
Page 13: Safety And Environmental Notices
US English source. Before using a US English publication to install, operate, or service this IBM product, you must first become familiar with the related safety information in the booklet. You should also refer to the booklet any time you do not clearly understand any safety information in the US English publications.
Page 14 TI. Se puede encontrar información sobre las ofertas de reciclado de productos de IBM en el sitio web de IBM http://www.ibm.com/ibm/environment/products/index.shtml.
Page 15: Refrigeration
United States, go to http://www.ibm.com/ibm/environment/ products/index.shtml or contact your local waste disposal facility. In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM Equipment.
Page 16: Flat Panel Display
For proper collection and treatment, contact your local IBM representative. For Spain: This notice is provided in accordance with Royal Decree 106/2008. The retail price of batteries, accumulators, and power cells includes the cost of the environmental management of their waste.
Page 17 Oregon – For information regarding recycling covered electronic devices in the State of Oregon, go to the Oregon Department of Environmental Quality Web site at http://www.deq.state.or.us/lq/electronics.htm. Washington – For information about recycling covered electronic devices in the State of Washington, go to the Department of Ecology Web site at http://www.ecy.wa.gov/programs/swfa/eproductrecycle, or telephone the Washington Department of Ecology at 1-800Recycle.
Page 18 PR/SM Planning Guide...
Page 19: About This Publication
This publication is intended for system planners, installation managers, and other technical support personnel who need to plan for operating in logically partitioned (LPAR) mode on the IBM System z9 Enterprise Class (z9 EC) and IBM System z9 Business Class (z9 BC).
Page 20 ® v ES/9000 Processor Resource/Systems Manager Planning Guide, GA22-7123 However, for the most current coupling facility control code information for all models, use this publication. xviii PR/SM Planning Guide...
Page 21: What Is Included In This Publication
Appendix B, “Developing, Building, and Delivering a Certified System,” on page B-1 provides guidance in setting up, operating, and managing a secure consolidated environment using System z9 PR/SM. v Appendix C, “Notices,” on page C-1 contains electronic emission notices, legal notices, and trademarks.
Page 22: Related Publications
Enterprise Systems Architecture/390 Principles of Operation, SA22-7201 Hardware System z9 BC v System z9 Business Class System Overview, SA22-1083 v Input/Output Configuration Program User’s Guide, SB10-7037 v Stand-alone IOCP User’s Guide, SB10-7152 v Hardware Management Console Operations Guide, SC28-6859...
Page 23 Multiple Image Facility: The following publications provide additional information about multiple image facility in the z/OS environment: v z/OS Hardware Configuration Definition: User’s Guide, SC33-7988 Dynamic I/O Configuration: The following publication provides information about dynamic I/O configuration in the z/OS environment: v z/OS Hardware Configuration Definition Planning, GA22-7525 Dynamic Storage Reconfiguration: The following publications provide additional information on the commands, functions, and capabilities of dynamic storage...
Page 24: How To Send Your Comments
How to Send Your Comments Your feedback is important in helping to provide the most accurate and high-quality information. Send your comments by using Resource Link at http://www.ibm.com/ servers/resourcelink. Select Feedback on the Navigation bar on the left. Be sure to...
Page 25: Summary Of Changes
This revision contains editorial changes and the following new technical changes. New Information v This book was updated to include information for both the IBM System z9 Enterprise Class (z9 EC) and the IBM System z9 Business Class (z9 BC).
Page 26 xxiv PR/SM Planning Guide...
Page 28: Overview
Sharing of allocated central storage among multiple LPs is not allowed. On System z9, all storage is defined as central storage. Allocation of storage to logical partitions can be made as either central storage or expanded storage. Any allocation of expanded storage to an LP reduces the amount of storage available for allocation as central storage.
Page 29: Central Processors
Central Processors Central processors (CPs) can be dedicated to a single LP or shared among multiple LPs. CPs are allocated to an LP when the LP is activated. You can use operator tasks to limit and modify the use of CP resources shared between LPs while the LPs are active.
Page 30: Zseries Parallel Sysplex Support
Connect to a coupling facility to share data v Installing a z9 BC or z9 EC with only ICFs (1 or more) operates as a stand-alone coupling facility; it cannot run z/OS or any other operating system.
Page 31: Guest Coupling Simulation
Notes: 1. Use IBM Service Link to view the appropriate PSP bucket subset ID for hardware and software maintenance information. 2. For more detailed information about support for coupling facility levels (including hardware EC, driver, and MCL numbers and software APAR numbers), see “Coupling Facility Level (CFLEVEL) Considerations”...
Page 32 Support for zSeries PCI X Cryptographic Coprocessor feature by the Integrated Cryptographic Services Facility and System SSL functions v Support Crypto Express2 and Crypto Express2-1P (only available on the z9 BC) and provides access to the secure key and System SSL functions via the Integrated Cryptographic Services Facility.
Page 33 Support for zSeries PCI X Cryptographic Coprocessor feature by the Integrated Cryptographic Services Facility and System SSL functions v Support for Crypto Express2 and Crypto Express2-1P (only available on the z9 BC) and provides access to the secure key and System SSL functions via the Integrated Cryptographic Services Facility.
Page 34 Support for zSeries PCI X Cryptographic Coprocessor feature by the Integrated Cryptographic Services Facility and System SSL functions v Support for Crypto Express2 and Crypto Express2-1P (only available on the z9 BC) and provides access to the secure key and System SSL functions via the Integrated Cryptographic Services Facility.
Page 35: Z/Vm
Support for zSeries PCI X Cryptographic Coprocessor feature by the Integrated Cryptographic Services Facility and System SSL functions v Support for Crypto Express2 and Crypto Express2-1P (only available on the z9 BC) with ICSF 64-bit Virtual Support for z/OS V1.6 and z/OS.e V1.6 provides access to the secure key and System SSL functions via the Integrated Cryptographic Services Facility.
Page 36 Version 5 Release 2 Support v CHPID type OSA performance enhancements, for z/OS guests v CHPID type FCP performance enhancements v FICON Express4-2C SX on the z9 BC v Hardware Decimal Foating Point facilities v Support for z9 BC and z9 EC...
Page 37: Z/Vse
FICON Express4-2C SX on the z9 BC v Support for z9 BC and z9 EC (with applicable PTFs) v Support for FICON Express2 (CHPID type FC), including Channel-To-Channel (CTC) v Support for FICON Express2 (CHPID type FCP) for native support of SCSI disks...
Page 38 v ESA/390 or ESA/390 TPF mode v 16 CPs (either shared or dedicated LP) v 2048 MB of central storage v Coupling facility level 9 with APAR support v Shared multiple processor LPs with PUT 03 v 256 channels 1-12 PR/SM Planning Guide...
Page 39: Linux
Linux Linux for S/390 v Support for FICON Express2 (CHPID type FC), including Channel-To-Channel (CTC) v Support for FICON Express2 (CHPID type FCP) for support of SCSI disks v OSA Express2 large send (also called TCP segmentation offload) v Linux-Only mode v 16 CPs v 2048 MB of central storage v 262144 MB of expanded storage...
Page 40: Input/Output Configuration Program (Iocp) Support
IOCDS you need to use the ICP IOCP program. PTFs for supported IOCP versions must be applied and can be obtained from the IBM Software Support Center. For more information on ICP IOCP, see Input/Output Configuration Program User’s Guide, SB10-7037.
Page 41: Logical Partitions
“Determining the Characteristics” on page 3-5). v The maximum number of LPs you can define on a z9 EC is 60. The z9 BC S07 supports 30 LPs. The BC R07 only supports the activation of 15 LPs but you can power-on reset the R07 with an IOCDS containing up to 30 LPs.
Page 42 You cannot define a mix of shared and dedicated CPs for a single LP (except for a coupling facility LP using the internal coupling facility feature. See “Internal Coupling Facility (ICF)” on page 2-46). CPs for an LP are either all dedicated or all shared.
Page 43: Characteristics Of Logical Partitions
ZVSE Figure 1-1. Characteristics of Logical Partitions 1-17 Chapter 1. Introduction to Logical Partitions...
Page 44: Potential Applications
Potential Applications The use of LPs allows multiple systems, including the I/O for the systems, to be migrated to a single CPC while maintaining the I/O performance, recovery, and multipathing capability of each system, and with minimum impact to the system generation procedures.
Page 45: Migration Of Four Production Systems To Lps
CPC. These systems, which were running on four separate IBM 9672 CPCs, now operate as four LPs on a single z9 EC. Two LPs are each running a z/OS system in ESA/390 mode, one is running a z/VM system in ESA/390 mode, and one is running in coupling facility mode.
Page 46: Compatibility And Migration Considerations
This section provides migration and compatibility information for the System z9. Device Numbers When multiple systems are migrated to a System z9 CPC, the combination of systems could include different devices or shared devices with identical device numbers. Each system can operate in an LP without changing the device numbers as long as identical device numbers do not occur in the same LP.
Page 47: Erep
System z9. This capability also allows channel paths to be moved among LPs using z/OS operator commands. v Preferred paths to a device are supported on a System z9. If the preferred path parameter is specified in an LPAR IOCDS, it is accepted.
Page 48: Cpu Ids And Cpu Addresses
The CPU identification number, with the version code and the machine type, permits a unique CPU ID for each logical partition. v The version code for the System z9 is always zero and is not affected by the operating mode.
Page 49: Cpu Ids For A Z9 Ec
The following examples show the format and contents of the CPU ID information stored by the STIDP instruction for logical CPs in active LPs. Table 1-1 shows the CPU ID information for a z9 EC with 3 active LPs. Table 1-1. CPU IDs for a z9 EC...
Page 50: Hsa Allocation
HSA size for the specified configuration and product. The HSA allocation can vary according to the I/O configuration. The following system I/O configurations require the given HSA size on a z9 EC. v Small system I/O configuration (S08): 1344 MB – 1 CSS –...
Page 51: Tod Clock Processing
LP. Sysplex Timer Attached The attachment and use of an IBM Sysplex Timer is supported. Also, during PR/SM initialization, when a Sysplex Timer is attached, the CPC TOD clocks for each CP are set to the TOD value from the Sysplex Timer.
Page 52: Sysplex Testing Without A Sysplex Timer And Server Time Protocol Not Enabled
If a member of its parallel sysplex is on the same server as the coupling facility, required connectivity is already provided to the synchronized time source. However, when a coupling facility is a resident of a System z9 model, which does not include a member of the coupling facilities parallel sysplex, connectivity attached to the synchronized time source must be implemented.
Page 53 register exists for each CPU and contains the TOD programmable field in bits 16-31. The TOD programmable register is set by a new privileged instruction, SET TOD PROGRAMMABLE FIELD (SCKPF). The leftmost byte of the extended form TOD clock is the TOD Epoch Index (TEX), and is stored as zeros in machines running ESA/390.
Page 54 1-28 PR/SM Planning Guide...
Page 55: Chapter 2. Planning Considerations
Coupling Facility LP Storage Planning Considerations ..2-47 Structures, Dump Space, and Coupling Facility LP Storage ..2-47 Estimating Coupling Facility Structure Sizes ... 2-48 © Copyright IBM Corp. 2005, 2008...
Page 56 Version 5 Utilizing IFL Features ....2-60 System z9 Application Assist Processor (zAAP) ... . 2-60 IBM System z9 Integrated Information Processor (zIIP) .
Page 57: Overview
Input/Output Configuration Program User’s Guide, SB10-7037. Planning Considerations PR/SM is standard on all System z9 models. Control Program Support The maximum number of supported devices is limited by the control program. In planning an I/O configuration, installation management should be aware of the maximum number of devices supported by the control program run in each LP.
Page 58: Z/Vm Dynamic I/O Support For Mif And The Coupling Facility
For more information on using HCD with Multiple Image Facility, see v z/OS Hardware Configuration Definition: User’s Guide, SC33-7988 v z/OS Hardware Configuration Definition Planning, GA22-7525 v z/VM I/O Configuration, SC24-6100. z/VM Dynamic I/O Configuration Support z/VM Support for the Coupling Facility: z/VM allows you to define configurations that use the coupling facility.
Page 59: Maximum Number Of Logical Partitions
2-28. Maximum Number of Logical Partitions The maximum number of LPs you can define on a z9 EC is 60. The z9 BC S07 supports 30 LPs. The BC R07 only supports the activation of 15 LPs but you can power-on reset the R07 with an IOCDS containing up to 30 LPs.
Page 60: Recovery Considerations
3. Determine if you want to move any channel paths among LPs. If you do, then these channel paths must be defined as reconfigurable in the IOCP CHPID statement. You cannot move a channel path from an LP in one CSS to an LP in another CSS.
Page 61: Managing Logical Paths For Escon And Ficon Channels
Up to 240 FICON Express2 and FICON Express4 channels on a z9 EC (and 112 channels on a z9 BC) can be employed to greatly expand connectivity and throughput capability. The FICON connectivity solution is based on industry-standard Fibre Channel technology and leverages our exclusive native FICON architecture.
Page 62: Logical Path Summary By Control Unit
Table 2-3. Logical Path Summary by Control Unit Maximum Logical Paths Maximum Control Unit Physical Links per Link Logical Paths 2105 Storage Control 2105 2048 3990 Storage Control 3990-2 Note 1 3990-3 Note 1 3990-6 Note 2 9343 Storage Controller 9343 D04 9343 DC4 3590 Magnetic Tape Subsystem...
Page 63: An Escon Configuration That Can Benefit From Better Logical Path Management
ESCON Example: Figure 2-1 shows a situation where 20 ESCON channel paths routed through an ESCON Director (ESCD) each attempt to establish a logical path to a 3990 Storage Control. The 3990 will allocate all 16 of its logical paths among the 20 channel paths dynamically on a first-come-first-served basis.
Page 64: A Shared Escon Configuration That Can Benefit From Better Logical Path Management
MIF Example: Figure 2-2 shows an ESCON shared channel configuration on an MIF-capable CPC. In this example, all five LPs share each of four ESCON channels attached to a 3990. Each shared ESCON channel represents five channel images corresponding to the five LPs. Each channel image requests a logical path to the 3990.
Page 65: Managing The Establishment Of Logical Paths
Managing the Establishment of Logical Paths You can manage the establishment of logical paths between channels and control units. With proper planning, you can create I/O configuration definitions that allow control units in the configuration to allocate logical paths for every possible request made by channels in either of the following ways: v Create a one-to-one correspondence between the logical path capacity of all control units in the physical configuration and the channels attempting to request...
Page 66: Recommendations
– If you perform POR, only those channels configured online to LPs that are activated at POR will attempt to establish logical paths. Shared channels will attempt to establish logical paths only for those activated LPs with the channel configured online. –...
Page 67 v Workload balancing When a system image becomes overloaded, you may need to reassign a workload and the necessary logical paths (for example, its tape or DASD volumes, a set of display terminals, or a set of printers) to another system image that has available capacity.
Page 68: Deactivating Unneeded Logical Partitions
LP1, LP2, and LP3 are activated. LP4 and LP5: one activated and Production Production Production Test Test one deactivated. LPAR Each shared ESCON channel establishes 4 3990 logical paths to the 3990. Cluster 1 Cluster 2 Figure 2-3. Deactivating Unneeded Logical Partitions Configuring Offline Unneeded Channels or Shared Channels on an LP Basis: You can configure offline unneeded channels or shared channels on an LP basis to manage how logical paths are established.
Page 69: Configuring Offline Unneeded Channels Or Shared Channels On An Lp Basis
For LP1, LP2, and LP3, CHPIDs 30, 31, 32, and 33 are all configured online. For LP4, CHPIDs 30 and 32 are configured offline. For LP5, CHPIDs 31 and LPAR 33 are configured offline. Each shared ESCON channel establishes 4 3990-3 logical paths to the 3990.
Page 70 Defining Devices to a Subset of Logical Partitions: You can limit I/O device access from LPs to I/O devices assigned to shared channels by using IOCP or HCD to specify device candidate lists. By defining devices attached to a control unit to a subset of LPs, you can manage which LPs will attempt to establish logical paths to the control unit through a shared channel.
Page 71: Defining Devices To A Subset Of Logical Partitions
CHPID 30 is a shared LPAR ESCON channel 3174 in 3174 in ESCD non-SNA non-SNA mode mode 3174 in 3174 in non-SNA non-SNA mode mode 3174 in non-SNA mode Figure 2-5. Defining Devices to a Subset of Logical Partitions 2-17 Chapter 2.
Page 72: Defining Devices To A Subset Of Logical Partitions
In Figure 2-6, a 3174 in SNA mode is defined as five control unit headers (CUHs). Because each 3174 CUH supports a maximum of one logical path, it is equally important in this example that the shared channel only attempts to establish a single logical path to each 3174 CUH.
Page 73 CHPID PATH=30,SHARED CNTLUNIT CUNUMBR=10,PATH=30,CUADD=0 IODEVICE ADDRESS=VVVV,CUNUMBR=10,PART=LP1 CNTLUNIT CUNUMBR=11,PATH=30,CUADD=1 IODEVICE ADDRESS=WWWW,CUNUMBR=11,PART=LP2 CNTLUNIT CUNUMBR=12,PATH=30,CUADD=2 IODEVICE ADDRESS=XXXX,CUNUMBR=12,PART=LP3 CNTLUNIT CUNUMBR=13,PATH=30,CUADD=3 IODEVICE ADDRESS=YYYY,CUNUMBR=13,PART=LP4 CNTLUNIT CUNUMBR=14,PATH=30,CUADD=4 IODEVICE ADDRESS=ZZZZ,CUNUMBR=14,PART=LP5 Using a Director to Block Ports or Prohibit Dynamic Connections or Communication: When ESCON or FICON Directors are used in an I/O configuration, you can prevent channels from establishing logical paths or can remove established logical paths by either blocking a Director port or by prohibiting a dynamic connection or communication between two Director ports.
Page 74: Using The Escd To Manage Logical Paths By Prohibiting Dynamic Connections
production CPCs fails, you could transfer the logical paths from the failing CPC to the backup CPC by prohibiting the dynamic connection to the failed CPC and allowing the dynamic connection to the backup CPC. If a control unit is connected to more than one Director, it is necessary to coordinate allocation of the control unit’s logical paths across all of the Directors.
Page 75: Shared Channel Overview
Note: ESCON channels that attach to a 9034 ESCON Converter Model 1 (CVC or CBY) cannot be shared among LPs. v IBM ESCON-capable or FICON-capable control units, or fibre channel switches. Understanding ESCON and MIF Topologies This section describes the following I/O topologies:...
Page 76: Progression Of Busy Condition Management Improvements
control unit interfaces required without a corresponding reduction in I/O activity. See Figure 2-8 for an example of switched point-to-point topology. MIF Channel Sharing Topology: MIF further improves control unit connection topologies for CPCs with multiple LPs. MIF enables many LPs to share a physical channel path.
Page 77: Mif Maximum Channel Requirements
does not require any control unit involvement. Busies are handled by the ESCON or FICON Director. Therefore, the control unit is effectively relieved of handling busy conditions and is able to handle more I/O requests. Because switch port busies require fewer trips over the ESCON or FICON connection link, they are less sensitive to increased distances than control unit busy encounters.
Page 78: Consolidating Escon Channels And Escon Control Unit Ports
Without shared ESCON channels Cluster 1 Cluster 2 LPAR With shared ESCON channels 3990 Cluster 1 Cluster 2 Figure 2-9. Consolidating ESCON Channels and ESCON Control Unit Ports ESCD Configurations: Figure 2-10 on page 2-25 shows how shared ESCON channels can reduce ESCD port requirements. In this example, two shared ESCON channels replace 10 unshared (dedicated or reconfigurable) ESCON channels and use eight fewer ESCD ports without a reduction in I/O connectivity.
Page 79: Consolidating Escon Channels And Escd Ports
Without shared ESCD ESCON channels 3990 Cluster 1 Cluster 2 LPAR With shared ESCON channels ESCD 3990 Cluster 1 Cluster 2 Figure 2-10. Consolidating ESCON Channels and ESCD Ports 2-25 Chapter 2. Planning Considerations...
Page 80: Consolidating Escon Channels Used For Escon Ctc Communications
ESCON CTC Configurations: Figure 2-11 shows how shared ESCON channels can reduce the ESCON channel requirements for ESCON CTC configurations. In this example, the CPC requires CTC communications among all its LPs. Without shared ESCON channels ESCD LPAR With shared ESCON channels Two channel pairs (CTC to CNC) provide redundancy to enhance...
Page 81: Unshared Escon Or Ficon Channel Recommendations
In situations where ESCON CTC communication is required among LPs that exist on two or more CPCs, shared channels can reduce even further channel and other hardware requirements and their associated cost. ESCON CTC configurations are well-suited to take advantage of the consolidation benefits associated with shared channels.
Page 82: Iocp Coding Specifications
most needed. CHPIDs identified as managed in the IOCDS (via CHPARM and IOCLUSTER keywords) are dynamically shared among z/OS images within an LPAR cluster. Prior to DCM, available channels had to be manually balanced across I/O devices in an attempt to provide sufficient paths to handle the average load on every controller.
Page 83 Use the CHPID PART|PARTITION, NOTPART, and SHARED keywords to determine which: v Channel paths are assigned to each LP v Devices and control units are shared among LPs v Channel paths are reconfigurable v Channel paths are shared Use the CHPID CPATH keyword to connect two internal coupling channels. Use the CHPID PATH keyword to define a channel path as spanned to multiple CSSs.
Page 84 access list specifies the LPs that have initial access to the CHPID at the completion of the initial power-on reset. An LP name may only appear once in an access list. You can specify that no LPs will access the channel path following LP activation for the initial POR of an LPAR IOCDS.
Page 85: Shared Devices Using Shared Escon Channels
Shared Devices Using Shared Channels MIF allows you to use shared channels when defining shared devices. Using shared channels reduces the number of channels required, allows for increased channel utilization, and reduces the complexity of your IOCP input. Note: You cannot mix shared and unshared channel paths to the same control unit or device.
Page 86: Physical Connectivity Of Shared Device 190
its own I/O configuration. Notice the recoverability characteristics of this configuration: each logical partition has two channel paths to the shared device, each attached to a different storage director. Logical Logical Logical Logical Partition Partition Partition Partition 8-way Switch Storage Storage Director Director...
Page 87: Duplicate Device Numbers For Different Physical Devices
However, paths cannot be moved between the LPs. Logical Logical Logical Logical Partition Partition Partition Partition 0001 0002 1001 1002 2001 2002 3001 3002 Figure 2-14. Logical View of Shared Device 190 The following example shows the IOCP statement for Figure 2-14. CHPID PATH=(10),PARTITION=(A), .
Page 88: Lpar Configuration With Duplicate Device Numbers
Logical Logical Logical Logical Partition Partition Partition Partition Figure 2-15. LPAR Configuration with Duplicate Device Numbers The following example shows the IOCP statement for Figure 2-15. This IOCP coding example groups the input statements by logical partition. When coding IOCP, view the I/O devices from a logical partition perspective.
Page 89: Duplicate Device Numbers For Console
Figure 2-16 shows another example of a logical partition configuration in which the device number for a console (110) is duplicated for all four logical partitions. Logical Logical Logical Logical Partition Partition Partition Partition 0001 0002 0003 0004 Figure 2-16. Duplicate Device Numbers for Console The following example shows the IOCP coding for the previous configuration.
Page 90: Two Examples Of Duplicate Device Number Conflicts
When an I/O configuration is dynamically modified so the logical partition can gain access to a device not previously accessible, a device conflict can occur. The conflicts are detected when commands are processed that change the I/O configuration or when you attempt to activate the logical partition which has the device number conflict.
Page 91 Unshared Device In the example on the right, the duplicate device numbers refer to a different device from each logical partition (a new device has been moved to ZOSTEST). This may result in a data integrity problem because the control program in logical partition ZOSTEST cannot access the correct device from channel path 04.
Page 92 The configuration can be activated by performing a POR or by performing a dynamic I/O configuration. In Figure 2-17 (shared device), ZOSTEST can access device 180 through CHP 04 and CHP 10 if CHP 04 is defined to ZOSTEST in the IOCDS. In Figure 2-17 (unshared device), ZOSTEST can access either device 180 (unshared device) if one or both of the devices are assigned a new device number in the IOCDS.
Page 93: Coupling Facility Planning Considerations
Coupling Facility Planning Considerations The coupling facility provides shared storage and shared storage management functions for the sysplex (for example, high speed caching, list processing, and locking functions). Applications running on z/OS images in the sysplex define the shared structures used in the coupling facility. The coupling facility allows applications, running on multiple z/OS images that are configured in a sysplex, to efficiently share data so that a transaction processing workload can be processed in parallel across the sysplex.
Page 94: Production Coupling Facility Configuration
Production Coupling Facility Configuration IBM recommends that you run your production applications on a sysplex that uses a production coupling facility configuration. A properly configured production coupling facility configuration can reduce the potential for extended recovery times, achieve acceptable performance, and maximize connectivity to the coupling facility.
Page 95: Internal Coupling Facility (Icf)
IMS, DB2 or VSAM/RLS). You can simplify systems management by using XCF structures instead of ESCON CTC connections. IBM does not recommend use of ICFs for most coupling facility structures involved in data sharing because of the possibility of “double outages” involving the simultaneous loss of an ICF image and one or more z/OS system images that are using the ICF for data sharing.
Page 96: Dynamic Internal Coupling Facility (Icf) Expansion
Dynamic Coupling Facility Dispatching (DCFD) With DCFD, the coupling facility uses CP resources in a shared CP environment efficiently, making a coupling facility using shared CPs an attractive option as a back-up coupling facility. Without DCFD, a coupling facility using shared CPs would attempt to get all the CP resource it could even when there was no real work for it to do.
Page 97: Enhanced Dynamic Icf Expansion Across Icfs
CPs, you must set the processing weight to a high value but this will not affect other work during normal operation. IBM recommends that the processing weight you specify for the shared logical CPs of a coupling facility using dynamic ICF expansion be set higher than the weight for all other logical CPs that are sharing the same physical CPs.
Page 98: System-Managed Coupling Facility Structure Duplexing
Single CPC Software Availability Sysplex For single CPC configurations, System z9 models can utilize an ICF to form a single CPC sysplex, providing significant improvement in software continuous operations characteristics when running two z/OS LPs in data-sharing mode versus one large z/OS image.
Page 99: Coupling Facility Nonvolatility
The following table indicates the optional nonvolatility choices available and their capabilities: Table 2-5. Nonvolatility Choices for Coupling Facility LPs Nonvolatility Choices z9 BC z9 EC Uninterruptible power supply (UPS) (See Note 1) Internal Battery Feature (IBF) Local Uninterruptible Power Supply (LUPS) (See Note 2) Notes: 1.
Page 100: Coupling Facility Lp Definition Considerations
Console or Support Element console using the Activation Profiles task available from the CPC Operational Customization Tasks Area. You can define coupling facility LPs with shared or dedicated CPs on all System z9 models. Coupling facility LPs must be defined with at least 128 MB of central storage.
Page 101: Coupling Facility Lp Storage Planning Considerations
Coupling Facility LP Storage Planning Considerations You must define at least 128 MB of central storage for a coupling facility LP to activate. This storage is reserved for coupling facility control code use and cannot be used for other purposes. Minimum storage size for coupling facilities is primarily a function of the coupling facility control code level.
Page 102: Dump Space Allocation In A Coupling Facility
The following table indicates the maximum central storage possible for the System z9 models: Table 2-7. Coupling Facility LP Storage Definition Capabilities Models Maximum Central Storage (GB) System z9 BC Model R07 Model S07 System z9 EC Model S08 Model S18...
Page 103: Coupling Facility Lp Activation Considerations
Structures share dump space. If a structure is using some of the dump space, other structures cannot use that portion of the dump space until it it released. v Characteristics of the structure saved to a dump table When saving structure objects to a dump table, the amount of dump space used depends on the parameters specified for the structure.
Page 104: Coupling Facility Control Code Commands
Notes: 1. Support for the CP and HELP coupling facility control code commands is available on all System z9 models. 2. The settings established using DYNDISP, MODE and TIMEZONE commands are recorded in the policy file for the coupling facility. As a result, all values are persistent across resets, deactivations, and reactivations.
Page 105: Cpc Support For Coupling Facility Code Levels
Models Level 15 Level 14 Level 13 Level 12 Level 11 Level 10 Level 9 Level 8 2096 EC J99670 z9 BC G40953 (Ver 2.9.1) (Ver 2.9.2) MCL 008 MCL 006 G40953 EC J99670 2094 (Ver 2.9.2) (Ver 2.9.0) z9 EC...
Page 106: Level 15 Coupling Facility
CFLEVEL but rather the recommended service level. For the latest EC and MCL information, use IBM Service Link to view the appropriate PSP bucket subset ID for hardware and software maintenance information. The most current CPC Support for CFCC table can be found online at http://www1.s390.ibm.com/ products/pso/cftable.html.
Page 107: Level 11 Coupling Facility
Software Corequisites: For a list of the software levels that exploit the function and levels that can coexist with CFLEVEL=12, see the “Summary of CFLEVEL Functions” section of the z/OS MVS Setting Up a Sysplex document. Level 11 Coupling Facility A level 11 coupling facility (CFLEVEL=11) provides the following enhancements: v System-Managed Coupling Facility (CF) Duplexing v Support for >15 LPARS.
Page 108: Coupling Facility Resource Management (Cfrm) Policy Considerations
Details panel by opening the CPC object that is running the coupling facility LP. v LP information for the coupling facility For a coupling facility residing on a System z9 model, the partition ID specified on the activation profile for the CF image on the support element or hardware master console must match the number specified in the PARTITION keyword of the CF statement in the policy information defined in the CFRM policy.
Page 109: Internal Coupling Channel
Note: The following bulleted items only describe z/OS to coupling facility connections. However, they also apply to coupling facility duplexing connections (CF to CF). Coupling facility channels: v Require a point-to-point connection (direct channel attach between a CPC or LP and a coupling facility).
Page 110: Integrated Cluster Bus Channels
InfiniBand coupling links for Parallel Sysplex InfiniBand coupling link technology provides increased bandwidth at greater cable distances. The IBM System z10 supports a 12x (12 lanes of fibre in each direction) InfiniBand-Double Data Rate (IB-DDR) coupling link which is designed to support a total interface link data rate of 6 GigaBytes per second (GBps) in each direction.
Page 111: Coupling Facility Channels (Type=Cfp, Type=Cbp, Type=Cib, Or Type=Icp)
ISC-3 coupling link in data centers where systems are less than 150 meters apart. A 12x InfiniBand-Single Data Rate (IB-SDR) coupling link is available on System z9 EC and System z9 BC S07 servers configured as internal coupling facilities (ICFs) only.
Page 112: Defining Internal Coupling Channels (Type=Icp)
This represents a maximum total of ten ICP CHPIDs being defined. I/O Configuration Considerations ICP IOCP supports coupling facility channel path definition on the System z9 CPC. With z/OS, HCD provides controls for defining coupling facility channels. HCD also automatically generates the control unit and device definitions associated with CFP, CBP, CIB, or ICP channel paths.
Page 113: Considerations When Migrating From Icmf To Ics
Linux is an open operating system with a wealth of applications which, in most cases, can run on a System z9 with a simple recompile. The System z9 includes features that provide an extremely cost-effective environment in which to run Linux.
Page 114: Z/Vm Version 5 Utilizing Ifl Features
Customers are encouraged to contact their specific ISVs/USVs directly to determine if their charges will be affected. On System z9 models, you can purchase and install one or more Integrated Facility for Applications (IFA) features with no effect on the model designation.
Page 115: Ibm System Z9 Integrated Information Processor (Ziip)
(CPs). Concurrent Patch Concurrent patch is available on all System z9 models. It is possible to apply BPC, UPC, support element (SE), Hardware Management Console, channel Licensed Internal Code (LIC), LPAR, coupling facility control code, I390, and PU patches nondisruptively and concurrent with system operation.
Page 116: Cfcc Enhanced Patch Apply
CF as identified in the example. v Allow all other LPARs on the System z9 where a disruptive CFCC patch will be applied to continue to run without being impacted by the application of the disruptive CFCC patch.
Page 117: Pr/Sm Shared Partitions
PR/SM Shared Partitions PR/SM configurations supporting multiple partitions, all sharing CPs, support concurrent CP upgrades. PR/SM code, once signaled that one or more central processors have been made available to the configuration, will vary them online automatically into the “shared pool” of physical CPs and begin full utilization of the added capacity.
Page 118: Multiple Dedicated Pr/Sm Partitions
Multiple Dedicated PR/SM Partitions Configurations in which all PR/SM partitions use dedicated CPs, where there is more than one dedicated partition, also support concurrent CP upgrade. CPs are added to the configuration, without disruption to any of the partitions, and can be brought online to a dedicated partition without an interruption.
Page 119: Dynamic Capacity Upgrade On Demand Limitations
Dynamic Capacity Upgrade on Demand Limitations 1. Valid upgrade towers are as follows starting at the smallest model in the pathway: z9 EC Models S08, S18, S28, S38, S54 z9 BC Models R07, S07 Inactive (spare) PUs can be added concurrently, dynamically providing nondisruptive upgrade of processing capability.
Page 120: Concurrent Memory Upgrade
Concurrent Memory Upgrade The System z9 includes a function to dynamically increase the amount of configured storage. Concurrent Memory Upgrade allows for a memory upgrade without changing hardware or experiencing an outage, provided there is enough spare memory already existing on the memory cards. An IML is not required to use the previously unavailable storage.
Page 121: Enhanced Book Availability
CPs that can be specified for an activating logical partition on page 3-28. Enhanced Book Availability The z9 EC is designed to allow a single book, in a multi-book server, to be concurrently removed from the server and reinstalled during an upgrade or repair action, while continuing to provide connectivity to the server I/O resources using a second path from a different book.
Page 122: Example Of A Prepare For Enhanced Book Availability Results Panel
conditions preventing the perform option from being executed will be displayed. Each tab will indicate what the specific conditions are and possible options to correct the conditions. Following is an example panel: Figure 2-18. Example of a Prepare for Enhanced Book Availability Results Panel In the example shown in Figure 2-18, the Processor tab displays, indicating the corrective actions suggested for the processor configuration.
Page 123: Reassigning Non-Dedicated Processors
Availability option from being performed for the targeted book.You may need to deactivate partitions or deconfigure processors to meet requirements as indicated by the panel data. Memory Use this tab to view the corrective actions required for the memory configuration conditions that are preventing the Perform Enhanced Book Availability option from being performed for the targeted book.
Page 124: Customer Initiated Upgrade (Ciu)
System z9 to meet the changing business environments. For example, a z9 EC Model S08 configured with eight CPs could be reconfigured to seven CPs and one IFL by ordering the appropriate PU conversion. This order will generate a new LIC CC which can be installed concurrently in two steps.
Page 125: Planning For Hot Plugging Crypto Features
If the customer plans to use ICSF or the optional cryptographic hardware, the CP Crypto Assist functions (CPACF DES/TDES) must be enabled. Many IBM products will take advantage of the cryptographic hardware using ICSF, so enabling CPACF is recommended. Use the CPC Details panel (double-click the CPC icon from the CPC Work Area) to determine if the CPACF feature is installed.
Page 126 2-72 PR/SM Planning Guide...
Page 127: Chapter 3. Determining The Characteristics Of Logical Partitions
Processing Weight Management ....3-39 Processing Weight Management Examples ... . 3-40 Maintaining the Same Relative Percentages of CPU Resources ..3-42 © Copyright IBM Corp. 2005, 2008...
Page 128 Processor Running Time ....3-43 Wait Completion ..... . 3-44 Workload Manager LPAR CPU Management of Shared CPs .
Page 129 Moving Unshared Channel Paths from a z/OS System ..3-83 Moving a Channel Path from the Hardware Console ..3-83 Releasing Reconfigurable Channel Paths ... . . 3-83 Configuring Shared Channel Paths .
Page 130: Planning Overview
Planning Overview This chapter provides a planning overview for defining logical partitions (LPs). Support for features, functions, and panels can differ depending on machine type, engineering change (EC) level, or machine change level (MCL). During IOCP execution, the names and numbers of the LPs are specified and channel paths are assigned to the LPs.
Page 131: Recovery Considerations
Capped Logical Partitions It is recommended that LPs be defined as capped LPs at the Support Element/Hardware Management Console only when needed to support planned requirements. When a capped LP does not obtain needed CP resources, because it has reached its cap, activity for that LP is similar to a system running out of CP resources.
Page 132: Iocds Requirements
Table 3-1. Control Program Support on z9 Control Program Maximum Maximum Maximum Maximum Control Operating Number Central Expanded Number Program Mode Storage Storage Channels | | | | | | z/OS 1.9 ESA/390 1 TB z/OS 1.8 ESA/390 1 TB z/OS 1.7...
Page 133: Mode Of Operation
Mode of Operation The mode of an LP depending on the model can be ESA/390, ESA/390 TPF, Linux-Only, or Coupling Facility. The mode of an LP must support the mode of the control program loaded into it. ESA/390 LPs support ESA/390 control programs, Coupling Facility LPs support the coupling facility control code, and Linux-Only LPs support Linux, or z/VM Version 5.
Page 134: Central Storage
Use the larger of the initial and reserved central storage amounts to calculate storage granularity. For example, on a z9 EC, for an LP with an initial storage amount of 30 GB and a reserved storage amount of 48 GB, the central storage granularity of initial and reserved central storage fields is 128 MB, using the larger reserved storage amount to determine storage granularity.
Page 135: Reserved Central Storage
Reserved Central Storage v Only ESA/390, ESA/390 TPF, and Linux-Only LPs can have nonzero amounts for this parameter. Coupling facility LPs cannot have reserved central storage amounts. v The reserved amount of central storage defines the additional amount of central storage that can become available to an LP when no other activated LP has this reserved storage online.
Page 136: Expanded Storage
1. If you do not specify a central storage origin, the reserved central storage is available for the LP when there is sufficient physical storage available to meet the reserved central storage request. Storage can be reassigned between LPs that have noncontiguous address ranges.
Page 137: Reserved Expanded Storage
v Initial expanded storage is reconfigurable (can be configured offline or online by the control program) for ESA/390 LPs that have no reserved expanded storage defined. v The initial amount of expanded storage can be zero when the reserved expanded storage is nonzero.
Page 138: Dynamic Storage Reconfiguration
twice the amount of installed storage. You can review current LP storage allocations by using the Storage Information task available from the CPC Operational Customization Tasks list. v The availability of reserved expanded storage depends on whether or not you specify an expanded storage origin for an LP.
Page 139 For z/OS, use the following command format to reconfigure central storage: CF STOR(E=1),<OFFLINE/ONLINE> Dynamic storage reconfiguration on the System z9 for central storage enables central storage to be reassigned between LPs that have noncontiguous address ranges. In this case, LPAR can allocate a “hole” or some set of central storage addresses for which there is no backing physical storage assigned.
Page 140: Central Storage Layout
Central Storage Dynamic Storage Reconfiguration Examples Figure 3-1 shows an example of central storage with dynamic storage reconfiguration capability. This figure shows LP-A, LP-B, and LP-C. 1024 GB 1022 GB Unused Addressability Addressable Storage 30GB Installed LP-C Storage ORIG = 8 GB INIT = 22 GB RSVD = 0 8 GB LP-B (CS0)
Page 141: Reconfigured Central Storage Layout
1024 GB 1022 GB Unused Addressability Addressable Storage 30 GB Installed LP-C Storage ORIG = 8 GB INIT = 22 GB RSVD = 0 8 GB LP-A (CS1) LP-A online to LP-A 4 GB LP-A (CS0) ORIG = 0 INIT = 4 GB RSVD = 4 GB 0 GB Figure 3-2.
Page 142: Initial Central Storage Layout
Figure 3-3 is another example of dynamic reconfiguration of central storage. For this example, assume the amount of installed storage is 32 GB. The amount of physical central storage used by hardware system area (HSA) is 2 GB in this example. The storage granularity is 64 MB so the HSA addressable storage size is 2048 MB.
Page 143: Central Storage Layout Following Reconfiguration
At a later point in time, the reserved storage from LP-A can be reconfigured to LP-B. Note that both LPs should specify an RSU value of at least 32 (2048/64) for reconfigurations of storage to work. From the z/OS software console for LP-A, enter CF STOR(E=1),OFFLINE.
Page 144: Initial Central Storage Layout
1024 GB 1022 GB RSVD = 2 GB (offline) 1020 GB LP-A ORIG = system determined INIT = 14 GB 1006 GB Addressable ORIG = system determined INIT = 14 GB Storage 992 GB LP-B Backing expanded storage INIT = 2 GB 990 GB Unused Addressability 0 GB...
Page 145: Central Storage Layout Following Reconfiguration
At a later point in time, LP-B deconfigures its expanded storage and the physical storage that was used for its expanded storage is reconfigured to LP-A. Note that LP-A should specify an RSU value of at least 32 (2048/64) for reconfigurations of storage to work.
Page 146: Expanded Storage Layout
Expanded Storage Dynamic Storage Reconfiguration Examples To dynamically reconfigure expanded storage, the system programmer may plan which LPs will donate storage and which LPs will receive storage. To do this, the system programmer may specify origins that overlap the reserved (RSVD) storage of the receiver with the initial (INIT) storage (and possibly some RSVD storage) of the donor.
Page 147: Reconfigured Expanded Storage Layout
1024 GB After deactivation Unused Addressability of LP-B Addressable Storage 10 GB LP-C (ES0) ORIG = 6 GB INIT = 4 GB RSVD = 0 6 GB LP-A (ES1) 4 GB LP-A (ES0) ORIG = 0 INIT = 4 GB RSVD = 2 GB 0 GB Figure 3-8.
Page 148: Expanded Storage Layout
1024 GB 1023 GB LP-B (ES1) not populated (offline) LP-B’s 1022 GB addressable LP-B (ES0) Addressable range ORIG = none INIT = 1 GB RSVD = 1 GB Storage 1021 GB LP-A (ES1) not populated (offline) 1020 GB LP-A’s LP-A (ES0) addressable ORIG = none INIT = 1 GB...
Page 149: Initial Central Storage Layout
1024 GB 1022 GB ORIG = system determined INIT = 14 GB 1008 GB LP-A Backing expanded storage INIT = 2 GB 1006 GB Addressable RSVD = 2 GB (online) Storage 1004 GB LP-B ORIG = system determined INIT = 14 GB 990 GB Unused Addressability 0 MB...
Page 150: Central Storage Layout Following Reconfiguration
At a later point in time, the reserved central storage from LP-B can be reconfigured to LP-A as expanded storage. Note that LP-B should specify an RSU value of at least 32(2048/64) for reconfigurations of storage to work. From the z/OS software console for LP-B, enter CF STOR(E=1),OFFLINE.
Page 151: Expanded Storage Layout Following Reconfiguration
1024 GB RSVD = 2 GB (online) LP-A 1022 GB INIT = 2 GB (online) 1020 GB Addressable Storage UnusedAddressability 0 GB Figure 3-13. Expanded Storage Layout Following Reconfiguration Recommendations for Storage Map Planning Planning storage maps as described below will help avoid storage fragmentation and remove dependencies on the order of activation of LPs.
Page 152: Cpcs With The Sysplex Failure Manager (Sfm)
The reserved expanded storage element will remain online if it was already online from the prior IPL. Note: When z/OS is IPLed immediately after the LP is activated, both the reserved central storage element and the reserved expanded storage element are offline. v Whenever z/OS is re-IPLed in an LP that has a reserved central storage element, a load clear or system reset clear followed by load normal should be performed to force the reserved central storage element offline.
Page 153: Backup Partition Layout Before Nonspecific Deactivation
3-27 for the storage layout before nonspecific deactivation. 1024 GB 1022 GB Unused Addressability Addressable Storage 30 GB Installed LP-Y Storage ORIG = 6 GB INIT = 24 GB RSVD = 0 Backup LP’s Addresability 6 GB Range LP-X ORIG = 2 GB INIT = 4 GB RSVD = 0 2 GB Backup LP...
Page 154: Number Of Central Processors
“Maximum Number of Central Processors.” On a System z9, you can optionally install one or more Internal Coupling Facility (ICF) features for use by a coupling facility LP and/or one or more Integrated Facility for Linux (IFL) features for use by a Linux-Only LP.
Page 155: Central Processor Recommendations For Intelligent Resource Director (Ird)
for that LP. The stated maximum supported processors for a particular control program is applied against the sum of the counts of all processor types defined to the partition. Workload Requirements The number of logical CPs defined also depends on the workload requirements and the ability of the control program or application program to effectively use multiple logical CPs.
Page 156: Processor Considerations For Linux-Only Lps
A Linux-Only LP, whether allocated IFLs or general purpose CPs, will not support any of the IBM traditional operating systems (such as z/OS, TPF, or z/VSE). Only Linux, or z/VM Version 5 with only Linux users can run in a Linux-Only mode LP.
Page 157: Coupling Facility Lps Using Dedicated Central Processors (Cps) Or Dedicated Internal Coupling Facility (Icf) Cps
Coupling Facility LPs Using Dedicated Central Processors (CPs) or Dedicated Internal Coupling Facility (ICF) CPs Important Note IBM strongly recommends using dedicated CPs or dedicated ICFs for production coupling facility LPs because coupling facility channel paths and requests have critical response time requirements. When the coupling facility is running on a dedicated CP or dedicated ICF CP, an “active wait”...
Page 158 v Shared ICF and shared general purpose processors are each managed as separate “pools” of physical resources. As such, the processing weights assigned to logical partitions using shared ICF processors are totaled and managed separately from the total weights derived from all of the logical partitions using shared general purpose processors.
Page 159: Considerations For Coupling Facilities Running On Uniprocessor Models
Considerations for Coupling Facilities Running on Uniprocessor Models On a uniprocessor or smaller machine, IBM strongly recommends that coupling facility LPs should not share general purpose CPs with non-CF workloads (for example, z/OS), even in a test environment. Such a configuration carries with it...
Page 160: Coupling Facility Lps Using Dynamic Icf Expansion
™ MVS/ESA Parallel Sysplex Performance (http://www.ibm.com/support/ techdocs/atsmastr.nsf/PubAllNum/W9731A) MVS/ESA Parallel Sysplex Performance - LPAR Performance Considerations for Parallel Sysplex Environments (http://www.ibm.com/ support/techdocs/atsmastr.nsf/PubAllNum/W9609) Coupling Facility LPs Using Dynamic ICF Expansion Important Note Dynamic ICF Expansion and Enhanced Dynamic ICF Expansion across ICFs is not recommended for coupling facilities that are used for primary production workload.
Page 161: Processor Considerations For Lps With Multiple Cp Types
For example, on a z9 EC with 1 ICF installed, one z/OS LP is defined with 8 shared CPs and the LP processing weight is 80 (10 per CP). Another coupling facility LP is defined with 1 dedicated ICF and one shared general purpose CP with a weight of 250.
Page 162: Shared Central Processors
Suitable Workloads Workloads best suited for logical partitions that use dedicated processors are those that maintain a fairly even external throughput rate (ETR) while using most of the capacity of the logical partition. Logical partitions with timing dependencies might require dedicated processors. The installation goals for a logical partition that uses dedicated processors should be similar to the goals of the processor complex.
Page 163: Processing Weights
longer periods, and the peak utilization periods for these workloads occurs simultaneously, then the total capacity of the logical partitions must meet the sum of the peak requirements for each workload. Sharing logical partitions that use event-driven dispatching are better able to maintain high transaction rates with fluctuating demand while being responsive.
Page 164 ZVSE 300/1300 = 23.1% ZOSTEST 100/1300 = 7.7% 900/1300 = 69.2% v The share of processing resource for each online logical CP is calculated by dividing the share for each LP by the number of online logical CPs. The share for each logical CP is as follows: ZVSE 23.1/1 CP = 23.1%...
Page 165: Enforcement Of Processing Weights
resource allocated to that LP. For example, an LP defined to have two CPs on a three-way CPC can never be allocated more than 67% of the CP resources no matter what its processing weight. Capping Processing Weights: The PR/SM capping function provides the capability of limiting CPU resource usage for one or more LP.
Page 166: Pr/Sm Lpar Processor Weight Management With Processor Resource Capping
1/10 or more of one physical CP. Typically, PR/SM LPAR will manage processing weights to within 1% of the LP’s physical CP share. See “Example 1. With Processor Resource Capping.” v For LPs without processor resource capping, PR/SM LPAR enforces the processing weights to within 3.6% of the LP’s physical CP share for logical CPs entitled to 1/2 or more of one physical CP.
Page 167: Pr/Sm Lpar Processor Weight Management Without Processor Resource Capping
Example 2. Without Processor Resource Capping: In the following example: v Six physical CPs are online v No LPs are capped v All LPs have sufficient workload demand to use their shares Table 3-4. PR/SM LPAR Processor Weight Management without Processor Resource Capping Resulting LCPs Weight per...
Page 168: Maintaining The Same Relative Percentages Of Cpu Resources
Maintaining the Same Relative Percentages of CPU Resources To maintain the same relative percentage of CP resources requested for a capped LP, processing weights should be readjusted immediately prior to, or immediately after, the activation or deactivation of an LP. Processing weight values for use when specific LPs are activated or deactivated should be calculated in advance, and be readily available.
Page 169: Processor Running Time
v Define a “dummy” LP (a “dummy” LP configured with 1 logical CP is sufficient) v Make sure that the logical CP in the “dummy” LP is in a fully enabled wait state (the first four bytes of the PSW must be X'030E000') If you have configured the “dummy”...
Page 170: Wait Completion
You can choose to set the runtime value yourself. However, when event-driven dispatching is enabled, it is generally recommended that the processor running time be dynamically determined. If event-driven dispatching is disabled, you should consider setting runtime values of 2 to 8 milliseconds. The recommended procedure is to start by using the default processor running time.
Page 171: Workload Manager Lpar Cpu Management Of Shared Cps
LPAR cluster comprised of multiple logical z/OS images on a single System z9 server. Each LP is assigned a transaction goal (desired response time) and an importance level. WLM monitors how well each LP is achieving its goals.
Page 172: Workload Charging By Soft-Capping To A Defined Capacity
LP the product is running in, rather than on the total capacity of the CPC. The capability is enabled by the LPAR clustering technology of the System z9 servers together with the License Manager component of z/OS. Each LP is assigned a defined capacity by the installation in terms of Millions of Service Units (MSUs).
Page 173: Enabling Management Of Linux Shared Logical Processors By Wlm's Lpar Cpu Management Component
The number of cache buffer data items that can be maintained locally in a Logical Partition is directly proportional to the number of on-line central storage pages in the LP. Each cache buffer or data item needs a local cache vector space bit.
Page 174: Defining Shared Channel Paths
Defining Shared Channel Paths Before defining shared channel paths, consider the following: v Only CTC, CNC, CBP, CFP, CIB, ICP, OSC, OSD, OSE, OSN, FC, FCV, FCP, and IQD channel paths can be shared. CVC and CBY channel paths cannot be shared.
Page 175: I/O Device Candidate List
I/O Device Candidate List The I/O device candidate list specifies the LPs which can access the device. You can use the I/O device candidate list to restrict LP access to I/O devices on shared channel paths. If you do not specify an I/O device candidate list, all LPs that share the channel paths, to which the device is attached, can have access to the device.
Page 176: Dynamic Chpid Management (Dcm) Considerations
Dynamic CHPID Management (DCM) Considerations DCM CHPIDs used by WorkLoad Manager (WLM) to optimize I/O throughput across an LPAR cluster are identified in the IOCDS by specifying CHPARM equals 01 and IOCLUSTER equals name (where name is an 8-byte EBCDIC cluster identifier).
Page 177: I/O Configuration Control Authority
Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset or image profile to enable isolation for an LP. The Logical partition isolation selection is located on the Security page for the LP. Using IOCP, you can control access to channel paths using the channel path candidate list.
Page 178: Dynamic I/O Configuration
Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset or image profile to enable cross-partition authority for an LP. The Cross partition authority selection is located on the Security page for the LP. Dynamic I/O Configuration Dynamic I/O configuration, available with z/OS and z/VM, provides the capability of changing the currently active I/O configuration.
Page 179: Esa/390 Logical Partitions
Channel paths (CFP, CBP, CIB, and ICP) assigned in the IOCDS to coupling facility LPs can be online to only one coupling facility at a time. On System z9 models a coupling facility can be assigned CBP, CFP, CIB, or ICP channel paths.
Page 180: Automatic Channel Path Reconfiguration
targeted to have this new channel path configured online. The dynamic I/O configuration change does not bring the channel path online. The channel path will be configured online to the targeted LP when one of the following occurs: v The system control program running in the targeted LP issues the appropriate reconfiguration command to configure the channel path online.
Page 181: Automatic Load For A Logical Partition
LP definitions. Sample tasks and panels explained in this section reference tasks and panels available from the support element console of a System z9. However, detailed procedures for operator tasks and accurate task and panel references are left to the appropriate operator guides.
Page 182 v Number of general purpose, and IFA, IFL, zIIP, or ICF CPs Security characteristics v Global performance data control v Input/output configuration control v Cross partition authority v Logical partition isolation Storage v Central storage v Expanded storage Time Offset v Time offset Load information v Load during activation...
Page 183: Global Reset Profile Definitions
Global Reset Profile Definitions Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset profile. Options Page Definitions Open the Options page to define the following LP characteristics: v Processor running time v Enablement of event driven dispatching v Enable global input/output (I/O) priority queuing Figure 3-16.
Page 184: Parameter Descriptions
Parameter Descriptions Enable global input/output (I/O) priority queuing Select this option to enable I/O priority queuing. Selecting this option causes I/O requests to be prioritized according to the values specified on the Options page of the Image Profile. Automatic input/output (I/O) interface reset Enables automatic system reset of a logical partition on behalf of a software initiated recovery action.
Page 185: Partitions Page Definitions
Partitions Page Definitions Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset profile. Open the Partitions page to define the following LP characteristics: v LP automatic activation order Figure 3-17. Partitions Page, Reset Profile Parameter Descriptions Partition LP name.
Page 186: General
General Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open an image profile for an LP. Open the General page to define the following LP characteristics: v Logical partition identifier v LP mode of operation v Clock type assignment Figure 3-18.
Page 187: Parameter Descriptions
Figure 3-19. Time Offset, Image Profile Parameter Descriptions Offset Type or spin to the number of days, hours, and minutes you want to set as the offset from the time of day supplied by its time source. You can set an offset within the following range: v 0 to 999 days v 0 to 23 hours v 0, 15, 30, or 45 minutes...
Page 188 time of day supplied by its time source by the number of days, hours, and minutes in the offset. Use this setting to provide a local time zone EAST of GMT or a date and time in the future. 3-62 PR/SM Planning Guide...
Page 189: Processor Characteristics
Figure 3-20. ESA Mode Logical Partition with shared Central Processors (CPs), Integrated Facilities for Applications (IFAs) and System z9 Integrated Information Processors (zIIPs). There can be both an initial and reserved specification for each processor type. Each processor can have it’s own processing weight(s). If WLM enablement or Initial Capping is selected for any processor then all processors types are WLM enabled or are initially capped, respectively.
Page 190: Customization For A Linux-Only Mode Logical Partition With Shared Integrated Facilities For Linux (Ifls). There Can Be Both An Initial And Reserved Specification For The Ifls
Figure 3-21. Customization for a Linux-Only Mode Logical Partition with shared Integrated Facilities for Linux (IFLs). There can be both an initial and reserved specification for the IFLs. 3-64 PR/SM Planning Guide...
Page 191: Customization For A Coupling Facility Mode Logical Partition With Dedicated Internal Coupling
Figure 3-22. Customization for a Coupling Facility Mode Logical Partition with Dedicated Internal Coupling Facilities (ICFs) and shared Central Processors. There can be both an initial and reserved specification for the ICFs and the Central Processors. Parameter Descriptions Note: Depending on the processor page, (see Figure 3-20, Figure 3-21 and Figure 3-22) some of the following parameters may not be present.
Page 192 Not dedicated central processors Select this option if you want the general purpose CPs that are allocated for the LP to be shared when the LP is activated. Dedicated integrated facility for Linux Note: All processors assigned to a coupling facility partition should be dedicated to that logical partition if it is used used for primary production workload.
Page 193 be dedicated to that logical partition if it is used used for primary production workload. If internal coupling facility processors are supported by and installed in the CPC, select Dedicated and not dedicated internal coupling facility processors and not dedicated central processors if you want to assign a combination of dedicated internal coupling facility processors and not dedicated internal coupling facility processors to the logical partition.
Page 194: Security Characteristics
Security Characteristics Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset or image profile for an LP. Open the Security page to define the following LP characteristics: v Global performance data control v Input/output (I/O) configuration control v Cross partition authority v Logical partition isolation...
Page 195: Security Page, Image Profile
Figure 3-23. Security Page, Image Profile 3-69 Chapter 3. Determining the Characteristics of Logical Partitions...
Page 196: Parameter Descriptions
Parameter Descriptions Global performance data control Select this option to allow the LP to view the CPU utilization data and the Input/Output Processor (IOP) data for all LPs in the configuration. Not selecting this option only allows the LP to view its own CPU utilization data.
Page 197: Establishing Optional Characteristics
Establishing Optional Characteristics Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset or image profile for an LP. Open the Options page to define the following LP characteristics: v Minimum input/output (I/O) priority v Maximum input/output (I/O) priority v Defined capacity Figure 3-24.
Page 198: Parameter Descriptions
Parameter Descriptions Minimum input/output (I/O) priority Enter the minimum priority to be assigned to I/O requests from this logical partition. Maximum input/output (I/O) priority Enter the maximum priority to be assigned to I/O requests from this logical partition. Defined capacity Enter the upper bound in terms of millions of service units (MSUs) beyond which the rolling 4-hour average CPU utilization cannot proceed.
Page 199: Storage Characteristics
Storage Characteristics Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization Tasks list to open a reset or image profile for an LP. Open the Storage page to define the following LP characteristics: v Central storage v Expanded storage Figure 3-25.
Page 200: Expanded Storage Parameter Descriptions
the duration of the LP activation. Enter a value that is compatible with the storage granularity supported by your CPC. Storage origin If Determined by the user is selected, enter, in MB, the central storage origin for the LP. When the LP is activated, it is allocated at the origin you specify here.
Page 201: Load Information
Load Information Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open an image or load profile for an LP. Open the Load page to define the following LP characteristics: v Load during activation v Load address v Load parameter v Load timeout value...
Page 202 Load address Enter the hex address of the I/O device containing the operating system to be loaded automatically at LP activation. Use dynamically changed address Select this option if you want to use the load address from a dynamically changed I/O configuration. This option and the Load address option are mutually exclusive.
Page 203: Cryptographic Characteristics
Cryptographic Characteristics Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to open a reset or image profile for an LP. Note: Any changes to the Crypto Image Profile Page settings require a DEACTIVATE and ACTIVATE of the LP to have the change take effect. To verify the active settings for the Cryptographic characteristics use the View LPAR Cryptographic Controls task available from the CPC Operational Customization tasks list (For information regarding the View LPAR...
Page 204 path to this and the other domains’ Master Keys. Indicate all the domains you want to access, including this partition’s own domain, from this partition as control domains. For more TKE Workstation information, refer to the z/OS ICSF TKE Workstation User’s Guide. Usage domain index The Usage Domain Index identifies the cryptographic domain(s) assigned to the partition for all cryptographic coprocessors or accelerators that are...
Page 205: Example Selection Of Crypto Numbers
of cryptographic numbers across the partitions. Or, if you are running z/VM in one or more partitions, you may want to assign more than one Cryptographic number to each VM partition so that one or more than one type of Crypto card is available for use by VM guests. For example, you have 19 logical partitions defined.
Page 206 Cryptographic Candidate List for each of these logical partitions to avoid assignment conflicts. Installation of a Cryptographic Adapter requires the IBM CP Assist for Crpytographic Functions (CPACF) feature. See the z/OS ICSF Application Programmer’s Guide and the z/OS ICSF System Programmer’s Guide for complete information.
Page 207: Enabling Input/Output Priority Queuing
Enabling Input/Output Priority Queuing Use the Enable I/O Priority Queuing task available from the CPC Operational Customization tasks list to either enable or disable I/O priority queuing for the entire CPC. Figure 3-28. Enabling I/O Priority Queuing Changing Logical Partition Input/Output Priority Queuing Values Use the Change LPAR I/O priority queuing task available from the CPC Operational Customization tasks list to set the minimum and maximum I/O priority queuing values for logical partitions.
Page 208: Parameter Descriptions
partitions in a given LPAR cluster should be given the same range of values so that WorkLoad Manager can optimize I/O throughput across the LPAR cluster. If the software in the logical partition does not have an understanding of I/O Priority Queuing, the system programmer should set the Minimum and Maximum I/O priorities to the same value.
Page 209: Moving Unshared Channel Paths
Moving Unshared Channel Paths You can move reconfigurable channel paths owned by one LP to another LP. Moving Unshared Channel Paths from a z/OS System 1. Select the LP that owns the channel path to display channel path information for the LP.
Page 210: Configuring Shared Channel Paths
Configuring Shared Channel Paths Verify the status of the channel path for each LP to which you plan to configure the channel path by opening each LP’s CHPIDs Work Area. Enter CF CHP(nn),ONLINE (where nn is the number of the desired CHPID) from each z/OS operator console to which the CHPID is to be brought online.
Page 211: Changes Available At The Next Lp Activation
– Minimum processing weight – Maximum processing weight – WorkLoad Manager enablement – Processor weight capping – Processor running time (globally applicable to logical CPs of all shared LPs) – Global enablement of event-driven dispatching – Defined capacity v Using the Change Logical Partition Input/Output (I/O) Priority Queuing Controls task, you can change the following LP definitions: –...
Page 212: Changes Available At The Next Power-On Reset (Por)
– Automatic load data v Use the Crypto page in the image profile to update the: – Control domain index – Usage domain index – Cryptographic Candidate List – Cryptographic Online List Changes Available at the Next Power-On Reset (POR) The following changes are available at the next power-on reset.
Page 214: Overview
This chapter provides information on operating the hardware system. Sample tasks and panels explained in this chapter reference tasks and panels available from the support element console of a System z9. However, detailed procedures for operator tasks and accurate task and panel references are explained in the Support Element Operations Guide, SC28-6858.
Page 215 Task Tasks List Customize/Delete Activation Profiles CPC Operational Customization Automatic Activation CPC Operational Customization Customize Scheduled Operations CPC Operational Customization Change LPAR Controls CPC Operational Customization Change LPAR Security CPC Operational Customization Storage Information CPC Operational Customization System Activity Profiles CPC Operational Customization Enable/Disable Dynamic Channel Subsystem CPC Operational Customization...
Page 216: Operator Controls Not Available
Operator Controls Not Available The following tasks are not available when logged on in system programmer mode: v Enable TOD v Change Operation Rate v Stop on I/O Address Match v Stop on I/O Event v Stop on PSW Event v Trace PR/SM Planning Guide...
Page 217: Operator Tasks
Operator Tasks Editing Activation Profiles You can edit reset, image, and load profiles for configurations using the Edit Activation Profiles task available from the CPC Operational Customization tasks list. Reset Profiles Use the reset profile to: v Select an IOCDS v Optionally specify an LP activation sequence v Enable I/O Priority Queuing.
Page 218: Deactivating An Lp
Deactivating an LP Deactivate an LP by dragging and dropping the LP icon onto the Deactivate task available from the Daily Tasks tasks list. This will deactivate the LP and any operating system running in the LP. Locking and Unlocking an LP Lock an LP by double-clicking on the CPC image icon representing the LP to open its Detail page.
Page 219: Deactivating A Cpc
– Channel Problem Determination v Channel Operations tasks – Configure On/Off – Release – Service On/Off – Advanced Facilities – Reassign Channel Path – Channel Problem Determination Deactivating a CPC Deactivate a CPC by dragging and dropping the CPC icon onto the Deactivate task available from the Daily Tasks tasks list.
Page 220 PR/SM Planning Guide...
Page 222: Overview
Overview This chapter describes the panels and tasks that can be used to monitor LP activity. It also provides LP performance information and provides guidelines and suggestions for planning a recovery strategy for operation. Monitoring Logical Partition Activity In addition to viewing LP information located in the General, Processor, Security, Storage, Load, and Channels pages of an LP’s reset, image, and load profiles, you can use the following tasks to further monitor LP activity: v Current storage information...
Page 223: Reviewing And Changing Current Channel Status
V1.8 or later. LPAR group capacity limits may help provision a portion of a System z9 server to a group of LPARs allowing the CPU resources to float more readily between those LPARs, resulting in more productive use of ″white...
Page 224: Change Lpar Group Controls
space″ and higher server utilization. Figure 5-3. Change LPAR Group Controls For information about how workload management and workload license charges relate to the Group Capacity setting, see z/OS MVS Planning: Workload Management, SA22-7602. PR/SM Planning Guide...
Page 225: Reviewing And Changing Current Logical Partition Security
Reviewing and Changing Current Logical Partition Security Use the Change LPAR Security task available from the CPC Operational Customization tasks list to display and modify LP security controls for an LP. Figure 5-4. Change Logical Partition Security Page Chapter 5. Monitoring the Activities of Logical Partitions...
Page 226: Reviewing Current Logical Partition Cryptographic Controls
Reviewing Current Logical Partition Cryptographic Controls Use the View LPAR Cryptographic Controls task available from the CPC Operational Customization tasks list to display the current cryptographic configuration for the logical partition. Figure 5-5. View LPAR Cryptographic Controls Page Reviewing Current System Activity Profile Information Use the System activity profiles task available from the Daily Tasks tasks list to open a System activity information window.
Page 227: Reviewing And Changing Logical Partition I/O Priority Values
Reviewing and Changing Logical Partition I/O Priority Values Use the the Change LPAR I/O Priority Queuing task available from the CPC Operational Customization tasks list to display and modify I/O priority queuing values for one or more LPs. Figure 5-6. Change LPAR I/O Priority Queuing Page Chapter 5.
Page 228: Logical Partition Performance
The configuration of the LPs v The configuration of the CPC v The performance tuning parameters You can contact an service representative who has access to a proprietary IBM performance planning tool (LPARCE from CPSTOOLS at WSCVM) to assist you in this task.
Page 229: Dedicated And Shared Central Processors
CPENABLE The z/OS CPENABLE parameter can be used to provide selective enablement for I/O interrupts. On System z9 CPCs, the best ITR is achieved when the fewest CPs are enabled for I/O interrupts. Selective enablement for I/O and the CPENABLE parameter are described in the z/OS MVS Initialization and Tuning Reference, SA22-7592.
Page 230: Recovery Strategy
Recovery Strategy Recovery planning requires that the appropriate planners and technical support personnel understand the recovery strategy. In planning for recovery, consider the following guidelines: v Recovery is considered successful if an LP is able to perform useful work and critical application programs remain operational (even if one or more LPs are disabled) after a failure occurs.
Page 231: Application Preservation
Transparent sparing configures a spare PU (processor unit) to replace a failed CP, ICF, IFL, IFA, zIIP or SAP. Each z9 EC has 2 spare PUs per processor book. The S08 has 2 spare PUs, the S18 has 4, the S28 has 6, the S38 has 8, and the S54 has 8.
Page 232 5-12 PR/SM Planning Guide...
Page 233: Appendix A. Coupling Facility Control Code Support
Storage increment Indicates that storage allocation requests are rounded up in units of 256 KB (512 KB for CF Level 15). Structure ID limit Cache and list structure ID range 1–1023. © Copyright IBM Corp. 2005, 2008...
Page 234 Retry buffer limit Retry buffer range upper limit. Facility information This area contains coupling facility control code release and service level information Maximum list element characteristic The maximum list element characteristic is 4. The size of a list structure list element in bytes equals 256 * (2 ** list element characteristic), for example, 256 * (2**4) = 4K.
Page 235: Appendix B. Developing, Building, And Delivering A Certified System
The IBM System z9 PR/SM functionality and assurances have been evaluated and certified at an EAL5 level of assurance. This appendix must be used in conjunction with other pertinent System z9 manuals supplied with the System z9 to give a security administrator all the required information to configure and operate an LPAR-mode system in a secure manner.
Page 236: Functional Characteristics
Functional Characteristics Logical partitions are defined, and the I/O resources of the overall physical computing system are pre-allocated by the security administrator. I/O allocation is an integral part of the process of defining a total system configuration, and must be completely performed before that system configuration can be initialized.
Page 237 v The hardware and any networks used to connect the hardware must be physically secure. Access to I/O devices must be restricted to authorized personnel. The hardware system console must be physically protected from access other than by authorized system administrators. v The Hardware Management Console User Interface Style selection must specify ″Classic Style″.
Page 238: System Z9 Pr/Sm Characteristics
System z9 PR/SM Characteristics v There is a Hardware Management Console (HMC) and Support Element (SE) from which the system can be operated. Therefore the system administrators of the system must be cleared for the highest security classification of work being performed on the system.
Page 239: I/O Security Considerations
z/OS or MVS/ESA CONFIG (CF) operator command. See z/OS MVS System Commands for further detail. While processing this command, MVS must interact with PR/SM, via a service call instruction, to request that the storage be varied. Because storage cannot be varied without PR/SM involvement, no way exists to circumvent the validity checking PR/SM does to confine a partition occupant within the storage limits defined for the logical partition.
Page 240: Operational Considerations
Low-speed devices (such as SCP Operator’s Consoles) are especially inviting targets for sharing a single channel path using MIF. The following paragraph discusses how to share the channel path, but none of the console devices. If you choose to share channel paths between logical partitions, and their access to specific devices attached to that channel path must be restricted, I/O Device Candidate Lists are the means for restricting access to devices.
Page 241 devices? What other procedural controls must be followed in order that your organization’s security policy is maintained? What operator actions are required to reconfigure this specific channel path in a secure manner? Lastly, careful attention to the IOCDS language rules relating to the CHPID REC parameter is necessary to achieve the result desired.
Page 242: Input/Output Configuration Data Set (Iocds
Input/Output Configuration Data Set (IOCDS) An IOCDS defines the logical partitions by name, allocates I/O resources to each of them, and specifies the security characteristics of those I/O resources. The following list describes the security-relevant parameters of each type of IOCDS source statement.
Page 243: Activation
Operations task list, a display of the available IOCDSs will be generated. Periodic audits should be made to assure that the IOCDSs have remained unchanged. Activation A reset profile includes information for activating a central processor complex (CPC) and its images (logical partitions). v In the reset profile, after selecting an LPAR IOCDS (A0-A3) deemed valid for secure operation via the Input/Output (I/O) Configuration task, the operating mode selected must be Logically partitioned.
Page 244: Reconfiguring The System
Dynamic I/O Configuration is supported by the Hardware Configuration Definition (HCD) product for the z/OS or z/VM operating system. Note: I/O Configuration control should be enabled for a single, specific logical partition only during the short period of time when it is permitted to write a new IOCDS.
Page 245 MVS is aware of the logical partition objects it owns, and interacts with PR/SM to reconfigure them using the service call instruction. This Execution of this instruction results in a mandatory interception (by the System z9 processor hardware) which causes every use thereof to be mediated by PR/SM. PR/SM mediates the instruction to limit the scope of such requests to the objects that the security administrator defined for the specific logical partition.
Page 246 v Licensed Internal Code (LIC) v Processor Book When service is performed on the above-listed elements of the processor, the physical elements are logically and electrically isolated from the remaining portions of the system still in use. This is begun by first logging on the HMC with a SERVICE ID and then performing the desired maintenance or service task.
Page 247 Usage domains are unique for logical partitions within a single System z9. The TKE host partition’s control domain index list must include the usage domain index for all the TKE target partitions for which it has control. This TKE control allows one logical partition to set-up the domains for usage by other logical partitions.
Page 248: Trusted Facility Library
Cryptographic number assigned to it and the image has been placed in the Cryptographic Online List. On the z9 EC, the maximum number of Crypto Express2 features (0863) is eight (8), (The z9 BC can have a combination of Crypto Express2 and Crypto Express2-1P, but the max of both would be 8.)
Page 249 Table B-1. Trusted Facility Library for PR/SM (continued) Title Order Number System z9 Enterprise Class Safety Inspection GC28-6842 Application Programming Interfaces SB10-7030 Security Architecture: Securing the Open Client/Server Distributed SC28-8135 Enterprise Enterprise Systems Architecture/390 ESCON I/O Interface SA22-7202 Introducing Enterprise Systems Connection...
Page 250 B-16 PR/SM Planning Guide...
Page 251: Appendix C. Notices
Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Page 252: Trademarks And Service Marks
All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM’s suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
Page 253: Electronic Emission Notices
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and...
Page 254 EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022 Klasse A ein. Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verändert bzw.
Page 255 Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. Verantwortlich für die Konformitätserklärung nach Paragraf 5 des EMVG ist die IBM Deutschland GmbH, 70548 Stuttgart. Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4: Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022...
Page 256 Warning: This is a Class A product. In a domestic environment, this product may cause radio interference in which case the user will be required to take adequate measures. PR/SM Planning Guide...
Page 257: Glossary
An cross-partition authority control setting. ARF functions absolute address may itself be a base address. (T) (2) are used by the Sysplex Failure Manager (SFM) policy © Copyright IBM Corp. 2005, 2008...
Page 258 functions within z/OS, when RESETTIME, DEACTTIME, central storage. Storage that is an integral part of the or the RECONFIG statement is coded in the SFM processor and includes both main storage and the policy. hardware system area. asynchronous. (1) Pertaining to two or more CF.
Page 259 (1) The arrangement of a computer Customer Information Control System (CICS). An system or network as defined by the nature, number, IBM licensed program that enables transactions entered and the chief characteristics of its functional units. More at remote terminals to be processed concurrently by specifically, the term configuration may refer to a user-written application programs.
Page 260 FCC. Federal Communications Commission. analysis. feature. A part of an IBM product that may be ordered EREP. Environmental error record editing and printing separately by the customer. A feature is designated as program.
Page 261 IFA. Integrated Facility for Applications. Also referred to can be resumed. (A) (2) To stop a process in such a as zAAPs, or System z9 Application Assist Processors. way that it can be resumed. (3) In data communication, to take an action at a receiving station that causes the IML.
Page 262 A device that observes and records selected Licensed Internal Code (LIC). Software provided for activities within a data processing system for analysis. use on specific IBM machines and licensed to customers under the terms of IBM’s Customer multidrop. A network configuration in which there are Agreement.
Page 263 (PTF). A temporary solution or concurrent or simultaneous operation of two or more bypass of a problem diagnosed by IBM as resulting devices or to concurrent performance of two or more from a defect in a current, unaltered release of the activities in a single device.
Page 264 A person who performs as common timing signals. (T). (2) Occurring with a maintenance services for IBM hardware products or regular or predictable time relationship. Contrast with systems. asynchronous.
Page 265 VM. Virtual machine. VSE. Virtual storage extended. warning message. An indication that a possible error has been detected. WLM. WorkLoad Manager. zAAP. System z9 Application Assist Processor. zIIP. IBM System z9 Integrated Information Processor. Glossary...
Page 266 D-10 PR/SM Planning Guide...
Page 267 CPENABLE 5-9 workload requirement 3-29 CPU addresses 1-22 central storage machine types 1-22 definition 3-8 model numbers 1-22 initial 3-8, 3-10 CPU ID 1-22 origin 3-9, 3-11 examples 1-23 CFCC patch apply 2-62 fields 1-22 © Copyright IBM Corp. 2005, 2008...
Page 268 Cryptographic Online List 3-80 enhanced book availability 2-67 Cryptographic Candidate List 3-78 ESCON channels cryptographic coprocessor feature 3-56, 3-63, 5-6 configuration rules 2-11 Cryptographic Online List 3-80 example, MIF 2-10 overview 2-21 recommendations 2-21 shared channels DCM 3-50 control units, infrequently used 2-27 deactivating LPs CTC configuration 2-25, 2-26 managing logical paths for LPs 2-13...
Page 269: Index
3-6 storage configuration 3-7 I/O topology logical paths point-to-point 2-21 configuration rules 2-11 IBM System z9 Integrated Information Processor configuring offline 2-14 (zIIP) 2-61 consideration 2-11 ICB (integrated cluster bus channels) 2-56 control unit 2-11 ICF (internal coupling facility feature) 3-63...
Page 270 3-7 HCD 1-13 Sysplex Failure Manager (SFM) support 1-5 description 3-26 z/OS 1-20 sysplex timer 1-25 System z9 Application Assist Processor 2-60 system-managed coupling facility structure duplexing 2-44 reconfigurable channel path 3-48 reconfigurable storage unit 1-21 recovery TOD clock 1-25...
Page 271 upgrade, capacity on demand 2-62 Usage Domain Index 3-78 wait completion 3-44 weights, processing 3-37 enforcement 3-39 workload balancing 2-13 requirements, CP 3-29 workload charging by soft-capping to a defined capacity 3-46 workload manager LPAR CPU management of shared CPs 3-45 See extended recovery facility z/VM guest coupling simulation 1-5 zAAP 2-60...
Page 272 PR/SM Planning Guide...
Page 274 Printed in USA SB10-7041-03...

IBM Z9 Planning Manual

Table of Contents

Chapter 1. Introduction to Logical Partitions

Chapter 2. Planning Considerations

Chapter 3. Determining the Characteristics of Logical Partitions

Chapter 4. Operating Logical Partitions

Quick Links

Chapters

Related Manuals for IBM Z9

Summary of Contents for IBM Z9