HP StorageWorks XP24000/XP20000 for Compatible Parallel Access Volumes Software User Guide Including Hyper PAV Abstract This user's guide describes and provides instructions for using the HP StorageWorks XP for Compatible Parallel Access Volumes Remote Web Console software to configure and perform Compatible PAV operations on the HP storage system.
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of HP StorageWorks XP for Compatible Parallel Access Volumes Software......................................................................................................5 About Compatible PAV Feature...................................................................................................5 About XP Compatible Hyper PAV Feature.....................................................................................7 2 About Compatible PAV Operations................................
Verifying Base and Alias Device Definition............................................................................35 Verifying the Status of the Devices........................................................................................36 5 Monitoring Compatible PAV Activities..........................................................38 MVS Commands (for z/OS).....................................................................................................38 GTF I/O Tracing.......................
1 Overview of HP StorageWorks XP for Compatible Parallel Access Volumes Software This chapter provides an overview of how Compatible PAV operates and the interactions it has with other software.
For further information on the zSeries and S/390 PAV host software function, see the following IBM documents: • z/OS DFSMS Software Support for IBM Enterprise Storage Server (SC26-7399-00) • IBM Enterprise Storage Server Performance Monitoring and Tuning (SG24-5656) • System/390 Command Reference 2105 Models E10, E20, F10, F20 (SC26-7298) The use of Compatible PAV, the Compatible PAV, and all HP products is governed by the terms of your license agreements with HP.
About XP Compatible Hyper PAV Feature XP Compatible Hyper PAV was evolved from static Compatible PAV and dynamic Compatible PAV. If you use XP Compatible Hyper PAV, alias devices that are assigned to any base device are shared with all base devices in the same LCU. Thereby, the number of alias devices assigned to each base device by XP Compatible Hyper PAV does not need to change, as it does if you use Dynamic Compatible PAV.
alias devices for any base device in the LCU. If a host computer accesses similarly to the base devise 2 or 3, I/O requests will be also issued to all alias devices in this LCU automatically. The base device 4 in this LCU is also able to use all alias devices in this LCU, even though no alias devices were assigned to it in advance.
2 About Compatible PAV Operations Components The components which are involved in Compatible PAV operations are: • Base devices and alias devices on the storage system (see “Base Devices and Alias Devices” (page 9)) • Controller emulation type for the storage system (see “Controller Emulation Type” (page 10)) • Compatible PAV enabled on the storage system and on the Remote Web Console computer (see “Compatible PAV Software and License Key” (page 10)) • HCD definitions for the storage system (see “HCD
which it is assigned. An alias device must be defined to the host as a 3390A or 3380A device type (for example, 3390A 3, 3390A 9). The 3390A and 3390B devices are not related to the 3390-3A/B/C multiplatform devices. Also, the 3380A and 3380B devices are not related to the 3380-3A/B/C multiplatform devices. Controller Emulation Type The IBM 2105 or 2107 controller emulation type is required for Compatible PAV operations.
WLM Host Software Definitions for Dynamic Alias Management The Workload Manager (WLM) software component of the MVS/ESA, z/OS, or OS/390 operating system enables the host to interface with the Compatible PAV functionality of the storage system. WLM compatibility mode provides static Compatible PAV functionality, and WLM goal mode provides dynamic Compatible PAV functionality. WLM must be in GOAL mode to support Dynamic Alias Management Compatible PAV functionality.
Table 1 HCD Settings for Static and Dynamic Compatible PAV Dynamic Alias Support I/O Priority Management Dynamic Alias Algorithm in Effect NO NO None (that is, static Compatible PAV only) NO YES None (that is, static Compatible PAV only) YES NO Efficiency only YES YES Both efficiency and goal Static Compatible PAV When static Compatible PAV is used, the number of aliases specified for each base device does not change, even when the number of I/O requests to each device changes.
Software Definitions for Dynamic Alias Management” (page 11) and “System Requirements” (page 15). Figure 4 Dynamic Compatible PAV Considerations for Storage System Sharing Across Multiple Systems A storage system that is installed with Compatible PAV can be shared across multiple sharing systems, subject to the following considerations: • When Compatible PAV is used in static mode, any number of sharing systems can be connected. • Each system will use Compatible PAV in static mode.
Maximizing Your Compatible PAV Results To maximize your results from Compatible PAV operations, be aware of the following: • For Compatible PAV ◦ The best results can be obtained if the number of aliases per LCU image is equal to the number of available channel paths minus one. If the number of aliases is specified this way, I/O operations can use all channel paths, thus providing the best results. ◦ The unused device addresses in the storage system are used as alias devices.
3 Preparing for Compatible PAV Operations System Requirements Compatible PAV operations involve the volumes on the XP24000/XP20000 disk arrays and require the following licensed versions: • Compatible PAV. • Workload Manager (WLM). • XP Compatible Hyper PAV. (This license is not required if only Compatible PAV operations are needed.) The system requirements for Compatible PAV are as follows: • Host software: ◦ For static Compatible PAV: OS/390 V1R3 (DFSMS/DSF 1.
• • IOCP definition considerations: If you maintain separate IOCP definitions files and create your SCDS or IOCDS manually by running the IZP IOCP program, the following definition rules apply: ◦ Each LCU on a storage system is defined using one CNTLUNIT statement in IOCP. The unit type is 2105 or 2107 (only 2107 is available if you use XP Compatible Hyper PAV). Up to 16 LCUs can be defined on a storage system.
NOTE: ◦ The WLMPAV parameter value is not relevant when using Compatible Hyper PAV. ◦ To use Compatible Hyper PAV, both the Compatible PAV software and the Compatible Hyper PAV software must be enabled on the Remote Web Console. For information on how to install the Compatible PAV and Compatible Hyper PAV software, see the HP StorageWorks XP24000/XP20000 Remote Web Console User's Guide. ◦ You can use the Compatible PAV window to check the capacity available to the Compatible PAV base volume.
Table 3 Requirements and Restrictions for Compatible PAV (continued) Item Requirement and/or Restriction Compatible PAV Functions that can be used concurrently with Compatible PAV Compatible Hyper PAV Virtual LVI Cache Residency Manager Volume Security HP StorageWorks XP Auto LUN Software TrueCopy for Mainframe Hitachi ShadowImage™ for Mainframe Universal Replicator for Mainframe Concurrent Copy (CC) with restrictions HP StorageWorks XP for FlashCopy Mirroring Software and HP StorageWorks XP for FlashCo
CAUTION: The following restrictions apply if CC will be used with Compatible PAV: • Ensure that the emulation type of all LCUs is either 2105 or 2107. Only 2107 controller emulation is available when you use Compatible Hyper PAV. For CC, 2105 or 2107 emulation cannot be intermixed with other emulation types within the same subsystem. • If CC volumes already exist, you must change to 2105 or 2107 emulation as follows: 1. Stop all Concurrent Copy jobs. 2.
1. 2. 3. Log on to the storage system SVP as administrator. The Remote Web Console Java application will be downloaded to your WWW client computer. For more detailed instructions, see the HP StorageWorks XP24000/XP20000 Remote Web Console User’s Guide. Use Remote Web Console to enable the Compatible PAV option. License keys are required when enabling these options. For more detailed instructions, see the HP StorageWorks XP24000/XP20000 Remote Web Console User’s Guide.
Setting the WLM Operation Mode WLM manages workloads on MVS and z/OS systems and has two operation modes for static and dynamic Compatible PAV: • Goal mode: To use dynamic Compatible PAV, you must set the WLM operation mode to goal mode. In goal mode, WLM can assign more or fewer aliases to a base device depending on the host I/O activity to that device, thereby managing the system to meet the performance goal specified before system operations began.
2. Enable Hyper PAV. Issue the following commands from the system console of z/VM to all alias devices that are used for Compatible Hyper PAV in the corresponding CU: DET alias-device-number1 - alias-device-number2 VARY OFFLINE alias-device-number1 - alias-device-number2 SET CU HYPERPAV ssid1 - ssid2 VARY ONLINE alias-device-number1 - alias-device-number2 ATT alias-device-number1 - alias-device-number2* An asterisk (*) is required at the end of the ATT command. 3. 4. Enable Hyper PAV on z/OS.
Setting the MIH Timer Value The recommended MIH timer value for storage system Compatible PAV operations is 30 seconds. The MIH timer values can be set in MVS/ESA, z/OS, or OS/390 either at IPL or after IPL. To set the MIH timer value: 1. 2. At IPL − Use the MIH parameter in the IECIOSxx parmlib member to set the MIH timer value at IPL time. For the complete syntax of this parameter, see IBM document SC28-1752, OS/390 MVS Initialization and Tuning Reference.
4 Performing Compatible PAV Operations After you have prepared for Compatible PAV operations as described starting in “Preparing for Compatible PAV Operations” (page 15), you are ready to start performing Compatible PAV operations on the storage system.
Figure 10 Compatible PAV Window An LDEV that displays with a pound or gate symbol as a suffix (for example, 00:00:00 #), indicates that the LDEV is an external volume. The LDKC list box allows you to select the desired LDKC number. Item Description LDKC and CU lists Selects the LDKC and CU that contain the desired volumes. Compatible PAV Used Capacity Shows the Compatible PAV capacity values. Base Volume List Displays the LDEVs that are currently in use in the selected CU image.
Figure 11 LDKC/CU Selection Line Table 4 (page 26) describes the LDKC/CU selection line in the Compatible PAV window. Table 4 LDKC/CU Selection Line Item Description LDKC Selects the LDKC that contains the desired CUs and LDEVs. CU Selects the logical CU image that contains the desired LDEVs. The volume lists in the Compatible PAV window display only the LDEVs for the selected CU image. CU numbers are included in the currently selected LDKC.
If all 255 CUs have volumes, it can take up to 13 hours to calculate and display the updated used capacity. During calculation, the latest value for the used capacity is unavailable. Even if the calculation of the used capacity has not been completed, the changes had been enabled already. All volumes defined to XP24000/XP20000 disk arrays are calculated. The value displayed during calculation and enclosed in brackets is temporary.
Alias Volume List The Alias Volume List box (see Figure 14 (page 28)) displays the alias devices assigned to the selected base devices. To view all alias devices for the selected CU image, you must select all of the base devices. When you cancel aliases for base devices, you select the alias devices from this list. Figure 14 Alias Volume List Item Description Alias Volume Displays the LDKC, CU, and LDEV numbers of the alias volume.
Figure 15 Free Volume List Table 6 Free Volume List Item Description Free Volume Displays the complete list of volumes available for assignment. Selected field Displays the number of selected free devices and the total number of free devices in the selected CU image. For example, “8/47” indicates that eight free devices are selected out of a total of 47 free devices in the selected CU image. Select All Selects all volumes in the Free Volume List box.
Delete and Add Buttons The Delete and Add buttons are located between the Alias Volume List and Free Volume List, allow you to delete/cancel existing alias devices that are assigned to base devices and add/assign new alias devices to base devices. Button Description Delete Cancels aliases for a selected base device. When you click Delete, the selected alias devices are canceled, and their LDEV IDs are displayed in the Free Volume List box.
allocate the free volumes equally to the base volumes. For example, if six free volumes and two base volumes are selected, three free volumes (aliases) are allocated to each base volume. WARNING! • If you want to assign aliases to multiple CUs that are used by a host, you need to click Apply as you add each alias to the CU. If you add all of the aliases to a CU, and then click Apply, the host performance will be reduced.
Figure 16 Assigning Aliases Figure 17 Confirming the New Aliases 32 Performing Compatible PAV Operations
Canceling Aliases WARNING! Do not cancel aliases while I/O operations are being performed on the Compatible PAV devices. This can cause a serious failure. To cancel aliases for volumes in the connected storage system: 1. 2. 3. 4. 5. Select the LDKC which includes the LCU number to be canceled, in the LDKC list to select LDKCs located in the upper left part of the Compatible PAV window. In the Compatible PAV window, select the LCU image which contains the aliases that you want to cancel.
Migrating Aliases The alias assigned to the base device must be canceled and reassigned in order to migrate it. WARNING! When migrating aliases, you must confirm that the number of requests to the base device that the alias is moved from, is less then 50 IOPS by acquiring performance information using RMF (Resource Measurement Facility Report Analysis) etc. before migrating the alias.
NOTE: When each base device is assumed to be assigned the same number of aliases, the recommended ratio of base devices to aliases is 1:3. Verifying Base and Alias Device Definition After you have defined the mapping between base devices and alias devices to the host operating system (see “Defining Base and Alias Devices” (page 34)), you need to verify that the host recognizes the storage system devices as specified.
Verifying the Status of the Devices After verifying the generation definition for the storage system devices, you need to verify the status of the devices for each channel path (CHP). To verify the status of the storage system devices by CHP ID: 1. At the MVS console display the status of the storage system devices by issuing the Display Matrix command for each CHPID connected to the storage system (see sample output in Figure 21 (page 36) and Figure 22 (page 37)): D M=CHP(XX) (XX = CHP ID) 2.
Figure 22 Verifying the Status of Devices Defined by CHP ID (Compatible Hyper PAV) Considerations for Defining the Storage System Devices to the Host System 37
5 Monitoring Compatible PAV Activities This chapter shows commands that are used to monitor Compatible PAV activities on the storage system from the host computer. The commands differ according to the operating system of the host computer. For z/OS, see the following section: • MVS Commands (for z/OS) • GTF I/O tracing For z/VM, see the following section: • VM CP Commands (for z/VM) MVS Commands (for z/OS) To monitor the Compatible PAV activities on the storage system from z/OS, use MVS commands.
Figure 23 Output Sample of Display Command − Compatible PAV Base Device with 5 Aliases Figure 24 Output Sample of Display Command – Compatible Hyper PAV with 16 Aliases Figure 25 Output Sample of DEVSERV DISPLAY PATHS Command GTF I/O Tracing 39
Figure 26 Sample DEVSERV QPAV Command (Compatible PAV) Figure 27 Sample DEVSERV QPAV Command (Compatible Hyper PAV) 40 Monitoring Compatible PAV Activities
Figure 28 Output Sample of DEVSERV QPAV,SSID=xxxx Command GTF I/O Tracing 41
Figure 29 Output Sample of DEVSERV QPAV,SSID=xxxx Command (Compatible Hyper PAV) 42 Monitoring Compatible PAV Activities
Figure 30 Output Sample of DS QP,8300,VOLUME Command (Compatible PAV) Figure 31 Output Sample of DS QP,xxxx,VOLUME Command (Compatible Hyper PAV) Figure 32 Output Sample of D IOS,HYPERPAV Command VM CP Commands (for z/VM) To monitor the Compatible PAV activities on the storage system from z/VM, use VM CP commands.
The summary, syntax, and output sample of each commands are shown in the following pages. For the complete syntax of the commands, see the z/VM document. • Conventions used in this section This section uses the following symbols and typefaces to explain syntax: Capital and bold letter Indicates characters that you must type. Small letter Indicates characters that you can omit. Italics Indicates a type of an operand. You can type the arbitrary value. [] Indicates a operand that can be omitted.
Figure 33 Output Sample of QUERY CU Command q cu DASD A0C0 A0C8 A0D0 A0D8 A0E0 A0E8 A0F0 A0F8 dasd b600 ali CU B600 ALIASES: A0C1 A0C2 A0C3 A0C4 A0C9 A0CA A0CB A0CC A0D1 A0D2 A0D3 A0D4 A0D9 A0DA A0DB A0DC A0E1 A0E2 A0E3 A0E4 A0E9 A0EA A0EB A0EC A0F1 A0F2 A0F3 A0F4 A0F9 A0FA A0FB A0FC A0C5 A0CD A0D5 A0DD A0E5 A0ED A0F5 A0FD A0C6 A0CE A0D6 A0DE A0E6 A0EE A0F6 A0FE A0C7 A0CF A0D7 A0DF A0E7 A0EF A0F7 A0FF q cu DASD A000 A008 A040 A048 A050 A058 A060 A068 A070 A078 A080 A088 A090 A098 A0C0 A0C8 A0D0 A0D8 A0
Figure 34 Output Sample of QUERY DASD DETAILS Command q dasd details a000 A000 CUTYPE = 2107-E8, DEVTYPE = 3390-0A, VOLSER = CMA000, CYLS = 3339 CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY -SUBSYSTEM Y Y Y N N -DEVICE Y Y N N DEVICE DETAILS: CCA = 00, DDC = -DUPLEX DETAILS: -HYPERPAV DETAILS: BASE VOLUME IN POOL 0 CU DETAILS: SSID = B600, CUNUM = A000 CAUTION: You cannot use QUERY DASD DETAILS command for 3380 DASD.
CAUTION: The DETAILS operand is valid only for dedicated DASD or mini disk DASD. QUERY VIRTUAL PAV • Summary This command displays the status of all Compatible PAV devices and Compatible Hyper PAV that can be accessed by z/VM.
6 Troubleshooting Troubleshooting For troubleshooting information on the storage system, see the HP StorageWorks XP24000/XP20000 Disk Array Owner Guide. For a complete list of Remote Web Console error codes, see the HP StorageWorks XP24000/XP20000 Remote Web Console Error Codes.
7 Support and Other Resources Related Documentation For further information on configuring RAID storage systems and disk devices for zSeries and S/390 Parallel Access Volumes operations, see the following and other IBM documents: • DFSMS/MVS Software Support for IBM Enterprise Storage Server (SC26-7318) • Enterprise Storage Server Performance Monitoring and Tuning (SG24-5656) • System/390 Command Reference 2105 Models E10, E20, F10, F20 (SC26-7298) • OS/390 MVS Planning: Workload Management (GC28-176
• Operating system type and revision level • Detailed questions Subscription Service HP recommends that you register your product at the Subscriber’s Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources. HP Websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.
A Using HCD to Define and View Storage System Logical Control Units and Compatible PAV Devices The storage system logical control units (LCUs) and PAV base and alias devices are defined to MVS/ESA, z/OS, and OS/390 systems using the configuration dialog boxes of the Hardware Configuration Definition (HCD) Program. The WLMPAV device parameter for existing Compatible PAV devices can also be displayed using the HCD Program.
10. Once the device is defined using the Add Device dialog box, you must direct HCD to add this device to a specific Processor/System-ID combination. “Device / Processor Definition Dialog Box − Selecting the Processor ID” (page 57) and “Define Device / Processor Dialog Box” (page 57) show the HCD dialog boxes used to select the Processor and System-ID to which this device will be added. 11.
Figure 40 Add Control Unit Dialog Box Using HCD to Define LCUs and Base and Alias Devices 53
Figure 41 Selecting the Operating System 54 Using HCD to Define and View Storage System Logical Control Units and Compatible PAV Devices
Figure 42 Select, Change Option Figure 43 Control Unit Chpid, CUADD, and Device Address Range Addressing Using HCD to Define LCUs and Base and Alias Devices 55
Figure 44 Define, Modify, or View Configuration Data Figure 45 I/O Device List 56 Using HCD to Define and View Storage System Logical Control Units and Compatible PAV Devices
Figure 46 Add Device Figure 47 Device / Processor Definition Dialog Box − Selecting the Processor ID Figure 48 Define Device / Processor Dialog Box Using HCD to Define LCUs and Base and Alias Devices 57
Figure 49 Device / Processor Definition Dialog Box Figure 50 Define Device to OS Configuration Dialog Box − Selecting the OS Configuration Figure 51 Select / Disconnect Option 58 Using HCD to Define and View Storage System Logical Control Units and Compatible PAV Devices
Figure 52 HCD Device Parameters Displaying Compatible PAV Device Parameters You can display the device parameters using HCD to determine if a specific device is eligible for Dynamic Compatible PAV management by WLM. To display the device parameters: 1. Starting from the I/O Device List dialog box (see Figure 53 (page 60)), select the desired device by entering a slash (/) by the device number. In our example, we have selected device 8101. 2.
Figure 53 Device Selection Display Figure 54 Actions on Selected Devices Figure 55 View Device Definition 60 Using HCD to Define and View Storage System Logical Control Units and Compatible PAV Devices
Figure 56 Selecting the Processor Definition Figure 57 View Device Candidate List Figure 58 Selecting the OS Configuration Displaying Compatible PAV Device Parameters 61
Figure 59 View Device Parameters 62 Using HCD to Define and View Storage System Logical Control Units and Compatible PAV Devices
B Checking the WLM PAV Settings To view or change the Workload Manager PAV settings: 1. On the WLM initial dialog box (see Figure 60 (page 63)), press Enter to continue. 2. The Service Definition dialog box (see Figure 61 (page 63)) allows you to define where the service coefficient information can be found. Select option 1 (Read saved definition). 3. On the Primary Options dialog box (see Figure 62 (page 64)), select option 8 (Service Coefficients/Options) to display the WLM PAV settings. 4.
Figure 62 WLM Primary Options Dialog Box Figure 63 WLM Service Coefficient/Service Definition Options Dialog Box 64 Checking the WLM PAV Settings
C Using Compatible Hyper PAV This appendix describes the procedures for installing and uninstalling Compatible Hyper PAV. The procedure depends on whether Compatible Hyper PAV is used from z/OS or from z/OS used as a guest OS on z/VM. The following subsections describe each procedure. This appendix also describes the point to be checked when you change the setting to enable or disable Hyper PAV on the host computer and when you restart a storage system while using Compatible Hyper PAV.
CF CHP(channel-pass1 - channel-pass2),ONLINE V base-device-number1 - base-device-number2,ONLINE • Data Exchange is used on the host computer. After performing the installation of Compatible Hyper PAV as mentioned above, issue the following commands.
9. Issue the DEVSERV QPAV command from z/OS, and make sure that the displayed aliases are those assigned for Compatible Hyper PAV. The aliases for Compatible Hyper PAV cannot be displayed after issuing the DEVSERV QPAV command from z/OS or QUERY PAV command from z/VM. Execute either of the following operations, and then issue the command and check the display again. • If the host accesses only the corresponding storage system, disable Hyper PAV on the host computer, and then enable Hyper PAV again.
these aliases cannot be displayed as for Compatible Hyper PAV, execute the following procedure and then check again. 1. Issue the following command from z/OS that is used as a guest OS on z/VM to all base devices in the corresponding CU. V base-device-number1 - base-device-number2,OFFLINE 2. Issue the following commands from z/VM to all base devices and alias devices used for Compatible Hyper PAV in the corresponding CU.
1. Issue the following commands to all base devices in the corresponding CU. V base-device-number1 - base-device-number2,OFFLINE CF CHP(channel-pass1 - channel-pass2),OFFLINE 2. Uninstall the Compatible Hyper PAV software. For more information, see the HP StorageWorks XP24000/XP20000 Remote Web Console User Guide. 3. Issue the following commands to all base devices in the corresponding CU. CF CHP(channel-pass1 - channel-pass2),ONLINE V base-device-number1 - base-device-number2,ONLINE 4.
2. Issue the following commands from z/VM to all base devices and alias devices used for Compatible Hyper PAV in the corresponding CU.
Glossary A ADDR, Adr Address. A data structure or logical convention used to identify a unique entity, such as a particular process or network device. APAR Authorized Problem Analysis Report. C CC Concurrent copy. CCW Channel command word. CH Channel. CHA Channel adapter. A device that provides the interface between the array and the external host system. Occasionally, this term is used synonymously with the term channel host interface processor (CHIP). CHP Channel path. CU Control unit.
LD, LDEV Logical device. An LDEV is created when a RAID group is carved into pieces according to the selected host emulation mode (that is, OPEN-3, OPEN-8, OPEN-9). The number of resulting LDEVs depends on the selected emulation mode. The term LDEV is also known as term volume. LU Logical unit. LVI Logical volume or image (for example, 3390-3R). M MIH Missing interrupt handler. MVS Multiple virtual storage. P PAV Parallel access volume.
VOL, vol Volume. VOLSER Volume serial number. VSE Virtual storage extended. VTOC Volume table of contents. W WLM Workload manager.
Index A alias devices about, 5, 9 best ratio to base devices, 14 define by using HCD, 10, 51 define from the host system, 34 restriction, 17 aliases assign, 30 assignment requirements, 6, 7 cancel, 33 maximum assigned to a base device, 17 maximum assigned to base device, 30 migrate, 34 B base devices about, 5, 9 best ratio to alias devices, 14 define by using HCD, 10, 51 define from the host system, 34 emulation types required, 17 maximum alias assignment, 17 best practices, 14 D documentation about this
M V mapping between base and alias devices, 34 MIH timer value, set, 23 multiple systems storage sharing, 13 MVS commands, 38 VM CP commands, 43 W parameters for WLM support of Dynamic Alias Management, 11 settings for static or dynamic Compatible PAV operations, 11 use HCD to display, 59 PTF requirements, 15 websites HP, 50 HP Subscriber's Choice for Business, 50 product manuals, 49 WLM (Workload Manager) about, 5 set the operation mode, 21 support for Dynamic Alias Management, 11 view or change sett