compatible pav user guide

HP XP P9000 for Compatible Parallel AccessVolumes User Guide

AbstractThis guide describes and provides instructions for using Remote Web Console Software to configure and perform CompatibleParallel Access Volume operations on HP XP P9000 disk arrays. The intended audience is a storage system administrator orHP Technical Support provider with independent knowledge of HP XP P9000 disk arrays and the HP Remote Web Console.

HP Part Number: AV400-96479Published: August 2011Edition: Sixth

© Copyright 2010, 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, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Export Requirements

You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.

Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national residentof) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.

This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of CommerceDenied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directlyor indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specifiedin the U.S. Export Administration Regulations (15 CFR 744).

Revision History

DescriptionDateEdition

Applies to microcode version 70-01-01-00/00 or later.October 2010First

Applies to microcode version 70-01-24-00/00 or later.November 2010Second

Applies to microcode version 70-01-62-00/00 or later.January 2011Third

Applies to microcode version 70-02-01-00/00 or later.May 2011Fourth

Applies to microcode version 70-02-5x-00/00 or later.September 2011Fifth

Applies to microcode version 70-03-00-00/00 or later.November 2011Sixth

Applies to microcode version 70-03-00-00/00 or later.August 2012Seventh

Contents1 Overview..................................................................................................5

Parallel Access Volumes.............................................................................................................5Base and alias devices..............................................................................................................5Parallel Access Volumes modes...................................................................................................5

Parallel Access Volumes in dynamic mode...............................................................................6Parallel Access Volumes in static mode....................................................................................6

Workload Manager..................................................................................................................6WLM in goal mode..............................................................................................................7WLM in compatibility mode..................................................................................................7

Hyper Parallel Access Volumes...................................................................................................7Flow of I/O requests using Parallel Access Volumes.......................................................................7Flow of I/O requests using Hyper Parallel Access Volumes.............................................................8

2 Requirements and specifications...................................................................9Requirements...........................................................................................................................9Functions incompatible with Parallel Access Volumes...................................................................10IBM CC and Extended Remote Copy (XRC) for Mainframe restrictions............................................10Sharing Parallel Access Volumes across multiple sysplexes............................................................10Preventive Service Planning......................................................................................................10

3 Performing Parallel Access Volumes operations.............................................11Assigning aliases to base volumes............................................................................................11Removing aliases from base volumes.........................................................................................12Reassigning aliases ................................................................................................................13Calculating Parallel Access Volumes used capacity......................................................................14Refreshing Parallel Access Volumes data....................................................................................15

4 Verifying and monitoring devices................................................................16Verifying base and alias device definition..................................................................................16Verifying status of devices per channel path...............................................................................16Verifying Hyper Parallel Access Volumes aliases from z/OS.........................................................17Verifying Hyper Parallel Access Volumes aliases from z/OS on z/VM...........................................18Monitoring with MVS commands..............................................................................................19DISPLAY command.................................................................................................................19DEVSERV PATHS command......................................................................................................19DEVSERV QPAV commands.....................................................................................................20DISPLAY IOS HYPERPAV command...........................................................................................21GTF I/O tracing.....................................................................................................................22VM CP commands for z/VM....................................................................................................22QUERY CU command.............................................................................................................22QUERY DASD DETAILS command.............................................................................................23QUERY PAV command............................................................................................................23QUERY VIRTUAL DASD DETAILS command.................................................................................24QUERY VIRTUAL PAV command................................................................................................24

5 Troubleshooting........................................................................................25Troubleshooting......................................................................................................................25

6 Support and other resources......................................................................26Contacting HP........................................................................................................................26

Subscription service............................................................................................................26Documentation feedback....................................................................................................26

Related information.................................................................................................................26HP websites......................................................................................................................26

Contents 3

Conventions for storage capacity values....................................................................................27Typographic conventions.........................................................................................................27

A Disabling Hyper Parallel Access Volumes.....................................................29Disabling Hyper Parallel Access Volumes from z/OS...................................................................29Disabling Hyper Parallel Access Volumes from z/OS when multiple storage systems are used...........29Disabling Hyper Parallel Access Volumes from z/OS on z/VM.....................................................29

B Parallel Access Volumes GUI reference........................................................31Parallel Access Volumes window...............................................................................................31

Base Volume List................................................................................................................32Alias Volume List................................................................................................................32Free Volume List.................................................................................................................32

Glossary....................................................................................................34Index.........................................................................................................35

4 Contents

1 OverviewThis chapter provides an overview of Parallel Access Volumes.Unless otherwise specified, the term P9000 in this guide refers to the following disk array:

• P9500 Disk ArrayThe GUI illustrations in this guide were created using a Windows computer with the Internet Explorerbrowser. Actual windows may differ depending on the operating system and browser used. GUIcontents also vary with licensed program products, storage system models, and firmware versions.

Parallel Access VolumesParallel Access Volumes run on the P9500 storage system. Parallel Access Volumes enable a singleIBM host computer to issue multiple I/O requests in parallel to a single logical device (LDEV).Without Parallel Access Volumes, a host system can only initiate and manage one I/O request perLDEV. Parallel Access Volumes allows users to designate LDEVs as alias devices and to assignthose alias devices to base devices. All I/O requests to the alias devices are treated as thoughthey were issued to the base device. In this manner, concurrent I/O requests can be handledsimultaneously. Parallel Access Volumes allows the host computer to access data in the storagesystem substantially faster.For more information on the zSeries and S/390 PAV host software feature, see the following IBMdocuments:

• DFSMS/MVS Software Support for IBM Enterprise Storage Server (SC26–7318)

• DS8000 Performance Monitoring and Tuning (SG24–7146)

• System/390 Command Reference 2105 Models E10, E20, F10, F20 (SC26–7298)

Base and alias devicesThe two types of devices used in Parallel Access Volumes operations are base devices and aliasdevices. The P9500 storage system supports up to 256 devices per control unit (CU).A base device is an LDEV that has a formatted mainframe emulated volume assigned which containsuser data.

CAUTION: A device that has been used as a journal volume in the Continuous Access Journal,as a volume used for Data Exchange, or as a system disk or migration volume, may not be definedas a base device.

An alias device is an unassigned LDEV whose unit address can be used as an alias for a basedevice. Each alias device must be within the same logical CU image as the base device to whichit is assigned. Base and alias devices are defined to the host OS using a combination ofHCD/IODF/IOCDS. Base devices are defined by the storage system when the mainframe emulatedvolumes are defined and installed.Alias devices are created and installed with the Remote Web Console panels.

Parallel Access Volumes modesParallel Access Volumes operations may be performed in one of two standard operational modes.When the P9500 is operating in IBM 2105 control unit emulation, Dynamic or Static PAV modecan be used. When the P9500 is operating in IBM 2107 control unit emulation, Dynamic, StaticParallel Access Volumes, or Hyper Parallel Access Volumes modes can be used.The Parallel Access Volumes mode is controlled by the Dynamic alias management parametersetting for the IBM Workload Manager (WLM) and the WLMPAV parameter setting in the HCDfile.

Parallel Access Volumes 5

Parallel Access Volumes in dynamic modeWhen Parallel Access Volumes operates in dynamic mode, the number of alias devices assignedto each base device may dynamically increase or decrease based on the number of I/O requeststo each device. Dynamic mode assists in balancing workloads on base devices and can optimizethe speed of accessing data in the P9500. A dynamic Parallel Access Volumes operation isimplemented by the WLM feature for Dynamic alias management setting and the WLMPAVparameter setting in the HCD file both being set to YES.In the following figure, the x10, x11, and x12 base devices were original assigned two aliasdevices each. In this example, as I/O requests converge on the base device x10 (indicated by thelarge arrow), the number of alias devices for the base device x10 increases to four, while thenumber of alias devices assigned to the base devices x11 and x12 decreases to one each.

Parallel Access Volumes in static modeWhen Parallel Access Volumes are in static mode, the number of alias devices assigned to eachbase device does not change, even when the number of I/O requests to each device changes. Astatic Parallel Access Volumes operation is implemented when the WLM feature for Dynamic aliasmanagement setting and the WLMPAV parameter setting in the HCD file are both set to NO.In the following figure, the x10, x11 and x12 base devices were originally assigned two aliasdevices each. In this example, as I/O requests converge on the base device x10 (indicated by thelarge arrow), the number of alias devices for each base device does not change.

Workload ManagerThe Workload Manager (WLM) is a software component of the z/OS, and OS/390 operatingsystems that enables the host computer to utilize the dynamic capability of Parallel Access Volumes.The WLM manages workloads on MVS systems and has two operation modes to support dynamicand static Parallel Access Volumes operations.

6 Overview

WLM in goal modeThe WLM must be in goal mode to support dynamic Parallel Access Volumes operations. The WLMis in goal mode when the Dynamic alias management setting in the WLM Service Coefficient/ServiceDefinition Options dialog box is set to YES. While in goal mode, the WLM manages the systemto meet a performance goal.

WLM in compatibility modeThe WLM must be in compatibility mode to support static Parallel Access Volumes operations. TheWLM is in compatibility mode when the Dynamic alias management setting in the WLM ServiceCoefficient/Service Definition Options dialog box is set to NO. While in compatibility mode, theWLM manages the system according to parameters in IPS and ICS (IEAIPSxx and IEAICSxx parmlibmembers).

Hyper Parallel Access VolumesThe Hyper Parallel Access Volumes feature allows you to assign alias devices to one base device,but have all other base devices in the same CU share these aliases.When using the Hyper Parallel Access Volumes feature, the number of alias devices assigned toeach base device does not need to change, as is required when using Parallel Access Volumes indynamic mode. With the Hyper Parallel Access Volumes feature, a whole collection of alias devicescan be mapped to one base device in a CU.You can specify the PAV feature (Parallel Access Volumes or Hyper Parallel Access Volumes) touse for each host computer. Therefore, an alias device may accept I/O requests issued throughParallel Access Volumes or Hyper Parallel Access Volumes.

Flow of I/O requests using Parallel Access VolumesMultiple alias devices are assigned to a base device in a CU to enable the base device to handlemultiple I/O requests.In the following figure, three alias devices are each assigned to base devices 1, 2, and 3. Asillustrated with the arrows in the figure, I/O requests converge on base device 1 when a hostcomputer accesses the device using Parallel Access Volumes. Since alias devices A, B, and C wereassigned to base device 1 in advance of the operation, I/O requests are automatically issued tothese alias devices. Similarly, if a host computer accesses base devices 2 and 3, the I/O requestsare automatically issued to the alias devices assigned to those two base devices. Base device 4is not able to process multiple I/O requests since no alias devices are assigned to the device.

Hyper Parallel Access Volumes 7

Flow of I/O requests using Hyper Parallel Access VolumesMultiple alias devices are assigned to a base device in a CU to enable the base device to handlemultiple I/O requests. In Hyper Parallel Access Volumes, alias devices are pooled together in asingle CU, meaning that all base devices in the CU share alias devices.In the following figure, three alias devices each are assigned to base devices 1, 2, and 3. Asillustrated with the arrows in the figure, I/O requests converge on base device 1 when a hostcomputer accesses the device using Parallel Access Volumes. I/O requests are automatically issuedto unused alias devices among the nine alias devices in the CU. Similarly, if a host computeraccesses base devices 2, 3, and 4, the I/O requests are automatically issued to unused aliasdevices among the nine alias devices. Base device 4 is able to process multiple I/O requests eventhough no alias devices are specifically assigned to the device.

8 Overview

2 Requirements and specificationsThis chapter contains requirements and specifications.

RequirementsThe following table lists the requirements for Parallel Access Volumes and Hyper Parallel AccessVolumes operations.

RequirementsItem

Hyper Parallel Access VolumesParallel Access Volumes

Parallel Access VolumesParallel Access VolumesSoftware License KeysHyper Parallel Access VolumesWorkload Manager (WLM)Workload Manager (WLM)

z/OS 1.8 or laterDynamic modeHost OSz/OS 1.6 with PTF or later• OS/390 V2R7 (DFSMS/DSF 1.5) with

PTF or later z/VM 5.3 or later• OS/390 V2R7 (DFSMS/DSF 1.5) with

PTF or laterStatic mode

• OS/390 V1R3 (DFSMS/DSF 1.3) withPTF or later

• VM/ESA 2.4.0 or later

60-02-4x or laterN/AMicrocode60-03-2x or later for z/VM host

I-2107I-2105, I-2107Controller emulation type

3380-3, 3390-3, 3390-9, 3390-L, 3390-M, 3390-ADevice emulation type for basedevice Data Exchange devices listed below are not supported:

3380-3A, 3380-3B, 3380-3C, 3390-3A, 3390-3B, 3390-3C3390-9A, 3390-9B, 3390-9C, 3390-LA, 3390-LB, 3390-LC3390-MA, 3390-MB, 3390-MC

FICONChannel interface

One SSID (subsystem ID) for each set of 256 LDEVsStorage system ID setting

255Maximum number of aliases for onebase device

Alias device and its base device must belong to the same logical CU imageAlias device management

Virtual LVICompatible Remote Web Consolefunctions Cache Residency Z

Auto LUNContinuous Access Synchronous ZBusiness Copy ZContinuous Access Journal ZIBM Concurrent Copy (CC) with restrictionsCompatible XRC with restrictionsPPRCThin Provisioning Z

Requirements 9

NOTE:1. When you use z/VM, you must use z/OS as a guest OS on z/VM.2. 3390-3R devices are not supported in Hyper Parallel Access Volumes.

Functions incompatible with Parallel Access VolumesDevices using Parallel Access Volumes can coexist in the same storage system but cannot be usedconcurrently with the following functions:

• Open Volume Management

• Cache Residency

• LUN Manager

• Business Copy

• Continuous Access Synchronous

• Continuous Access JournalDevices using Data Exchange cannot coexist in the same CU with devices using Parallel AccessVolumes.

IBM CC and Extended Remote Copy (XRC) for Mainframe restrictionsFor Concurrent Copy (CC) and Compatible XRC, the 2105 and 2107 controller emulation typescannot be intermixed with other emulation types within the same storage system.

Sharing Parallel Access Volumes across multiple sysplexesParallel Access Volumes functionality can be shared across multiple sysplexes that are on a singlestorage system.When sharing static Parallel Access Volumes, all connected systems must be in static mode. Whensharing dynamic Parallel Access Volumes, the following requirements and restrictions apply:

• Only one sysplex should be running in Dynamic Alias Management mode. This master sysplexis the only sysplex in the storage system that assigns aliases.

• For all other connected sysplexes, the WLMPAV (HCD) and Dynamic Alias Management(WLM) settings should be set to No.

NOTE: If more than one sysplex has the Dynamic Alias Management enabled, unsynchronizedalias transition and unpredictable response times may occur.

Preventive Service PlanningIf you are using the Parallel Access Volumes feature on 2105 or 2107 device types, you areencouraged to obtain the Preventive Service Planning (PSP) document from IBM to use as a programtemporary fix (PTF) source. The title of the document is 2105M VSESA, and it can be downloadedvia IBMLINK.The PSP document identifies all current IBM PTF items applicable for z/OS and OS/390 supportof the 2105 or 2107 device types. The P9500 storage system does not have any specific PTFrequirements beyond what is required by the z/OS and OS/390 operating system to provideminimum support for the 2105 or 2107 device types.

10 Requirements and specifications

3 Performing Parallel Access Volumes operationsThis chapter describes performing Parallel Access Volumes operations on the storage system usingthe GUI.

Assigning aliases to base volumesUp to 255 aliases can be assigned to one base device. If the number of selected free volumes islarger than the number of selected base volumes, the Parallel Access Volumes function attempts toallocate the free volumes equally to the base volumes. For example, if six free volumes and twobase volumes are selected, three free volumes (aliases) are allocated to each base volume.If you only use Hyper Parallel Access Volumes to issue I/O requests to a CU, first decide the numberof aliases that are necessary for the CU, and then assign the aliases to arbitrary base volumes.The assigned aliases function as aliases for all base volumes in that CU. In this case, assign threeor less alias devices for each base device.If you want to assign aliases to more than one CU that is used by the host, you should click Applywhenever you assign aliases to one CU. If you click Apply only once to assign aliases simultaneouslyto more than one CU, the host performance may degrade.

Prerequisites• Parallel Access Volumes option or Hyper Parallel Access Volumes option is enabled in Remote

Web Console.• You must have Storage Administrator (Provisioning) role to perform this task.

• Base devices are defined in the storage system.Procedure 1 To assign aliases to base volumes in the P9500:1. In the Remote Web Console main window, select Actions > Mainframe Connection > Parallel

Access Volumes.

2. Click to change to Modify mode.3. In the Parallel Access Volumes window (shown in the following figure), select the LDKC which

includes the CU image to be modified from the LDKC list.

4. From the CU list, select the CU image which contains the desired base volumes.Base volumes are displayed in the Base Volume List.

Assigning aliases to base volumes 11

No volumes are displayed if the selected CU image only contains devices to which aliasescannot be assigned, such as 3390-V type devices or journal volumes. In this case, selectanother CU image.

5. Select one or more base volumes in the Base Volume List. Press Ctrl and click to select multiplebase volumes, press Shift + click to select a series of base volumes, or click Select All to selectall base volumes in the CU image.

6. Select one or more free volumes in the Free Volume List. Press Ctrl and click to select multiplefree volumes, press Shift + click to select a series of free volumes, or click Select All to selectall free volumes in the CU image.

7. Click Add to assign the selected free volume(s) to the selected base volume(s). The assignmentsappear in the Alias Volume List shown in the following figure.

8. Confirm the alias volume(s) assigned to the selected base volume(s) in the Alias Volume List.9. Click Apply to apply the current alias assignments in the Alias Volume List.

Removing aliases from base volumesAlias volumes may be removed from base volumes using the Parallel Access Volumes window.

Prerequisites• No I/O operations are currently being performed on base devices. Removing alias devices

while I/O operations are occurring can cause a serious failure.• You must have the Storage Administrator (Provisioning) role to perform this task.Procedure 2 To remove aliases from base volumes:1. In the Remote Web Console main window, select Actions > Mainframe Connection > Parallel

Access Volumes.

2. Click to change to Modify mode.3. In the Parallel Access Volumes window (shown in the following figure), select the LDKC which

includes the CU image to be modified from the LDKC list.

12 Performing Parallel Access Volumes operations

4. From the CU list, select the CU image which contains the aliases to be removed.5. Select one or more base volumes in the Base Volume List. Press Ctrl and click to select multiple

base volumes, press Shift and click to select a series of base volumes, or click Select All toselect all base volumes in the CU image. Alias volumes for each selected base volume(s)appear in the Alias Volume List as shown in the following figure.

6. Select one or more alias volumes to remove in the Alias Volume List. Press Ctrl and click toselect multiple alias volumes, press Shift and click to select a series of alias volumes, or clickSelect All to select all alias volumes in the CU image.

7. Once one or more alias volumes are selected, click Delete to remove the selected alias volume(s)from the selected base volume(s) and move these alias volumes back to the Free Volume List.

8. Click Apply to apply the changes.

Reassigning aliasesAlias volumes may be reassigned to a different base volume in the same or different CU imageusing the Parallel Access Volumes window.

Reassigning aliases 13

Prerequisites• Before an alias is reassigned, the user must confirm that the number of requests to the base

device that the alias is moved from is less than 50 IOPS. This performance information isacquired using RMF (Resource Measurement Facility Report Analysis) or other available tools.If the alias is reassigned when there are more than 50 IOPS to the base device, the processperformance may decline in the worst cases.

• You must have the Storage Administrator (Provisioning) role to perform this task.Procedure 3 To reassign aliases to a different base volume:1. In the Remote Web Console main window, select Actions > Mainframe Connection > Parallel

Access Volumes.

2. Click to change to Modify mode.3. In the Parallel Access Volumes window, select the LDKC that includes the CU image to be

modified from the LDKC list.4. From the CU list, select the CU image that contains the aliases to be reassigned.5. Select the base volume(s) in the Base Volume List. Press Ctrl and click to select multiple base

volumes, press Shift and click to select a series of base volumes, or click Select All to selectall base volumes in the CU image. Alias volumes for each selected base volume(s) appear inthe Alias Volume List.

6. Select one or more alias volumes to remove in the Alias Volume List. Press Ctrl and click toselect multiple alias volumes, press Shift and click to select a series of alias volumes, or clickSelect All to select all alias volumes in the CU image.

7. When one or more alias volumes are selected, click Delete to remove the selected aliasvolume(s) from the selected base volume(s) and move these alias volumes back to the FreeVolume List.

8. Select different base volume(s). These base volumes can be in the same CU image. Or, theCU image can be changed by using the LDKC and CU lists.

9. When one or more new base volumes are selected in the Base Volume List and one or morefree volumes are selected in the Free Volume List, click Add to assign the selected free volume(s)to the selected base volume(s). The assignments appear in the Alias Volume List.

10. Confirm the alias volume(s) assigned to the selected base volume(s) in the Alias Volume List.11. Click Apply to apply the changes.

Calculating Parallel Access Volumes used capacityAfter each Parallel Access Volumes operation, the Parallel Access Volumes Used Capacity valueis recalculated. These operations include:

• Assigning aliases to a new base volume and clicking Apply

• Canceling all aliases in the corresponding CU and clicking Apply

NOTE: A base volume with no assigned aliases does not contribute the total used capacityvalue.

• Uninstalling base volumes using the VLVI/LUN (VLL) or External Storage software

• Assigning aliases to a new base volume by Dynamic Parallel Access Volumes or Hyper ParallelAccess Volumes function

14 Performing Parallel Access Volumes operations

The used capacity is the sum of the capacities of base volumes which meet at least one of thefollowing conditions:

• Base volumes to which alias volumes are or were assigned through Remote Web Console

• Base volumes that are accessed by alias volumes using Dynamic Parallel Access Volumes orHyper Parallel Access Volumes

The calculation of the used capacity can be time-consuming as it takes three minutes for each CUto calculate this value. If all 255 CUs have volumes, it can take up to 13 hours to calculate anddisplay the updated used capacity. During calculation, the latest value for the used capacity isunavailable. All volumes defined to storage system are calculated. After the calculation has finished,the brackets disappear and the latest value of the used capacity is displayed.

Refreshing Parallel Access Volumes dataTo access the latest data following Parallel Access Volumes calculations or operations, open theParallel Access Volumes window and select File > Refresh.

Refreshing Parallel Access Volumes data 15

4 Verifying and monitoring devicesThis chapter describes the procedures for verifying base and alias devices on the system, and thesyntax and description of the commands used to monitor Parallel Access Volumes activities fromthe host computer.

Verifying base and alias device definitionAfter you have defined the mapping between base and alias devices to the host operating system,you must verify that the host recognizes the devices as specified.Procedure 4 To verify that the host system recognizes the settings for the base and alias devices:1. Run the MVS DEVSERV QPAV command to display information about the base device and

corresponding alias addresses. Use the following syntax for this command.DS QPAV,device_unit_ID,VOLUME

The following figures show sample outputs of this command. First on a Parallel Access Volumesdevice, and then on a Hyper Parallel Access Volumes device.

NOTE: The relationship between base and alias devices is not fixed for the OS using HyperParallel Access Volumes. Therefore, only the information about base devices is displayed.

2. Verify that the information displayed by the DEVSERV QPAV command matches the base andalias device definitions specified on the Remote Web Console client machine.

NOTE: After dynamic Parallel Access Volumes operations are performed, mismatches occurbecause the host system can change the number of aliases assigned to each base device.This type of mismatch will not cause any problems.

Verifying status of devices per channel pathAfter verifying the definition of devices, the status of these devices must be verified for each channelpath (CHP).

16 Verifying and monitoring devices

Procedure 5 To verify the status of the devices by CHP ID:1. Run the MVS Display Matrix command for each CHP ID connected to the storage system. Use

the following syntax for this command.D M=CHP(CHP_ID)

The following figure shows a sample output of this command.

2. Verify that the information displayed by the Display Matrix command matches the devicestatus that was defined when the generation definition was made. If the information is incorrect,the devices must be redefined to the host.

Verifying Hyper Parallel Access Volumes aliases from z/OSWhen you restart a P9500 storage system while using Hyper Parallel Access Volumes, you mustverify that the correct aliases are assisted to a CU.Procedure 6 To verify Hyper Parallel Access Volumes aliases on a z/OS host:1. On the host computer, enable the Hyper Parallel Access Volumes option.2. Issue the DEVSERV QPAV command from the host to verify that the displayed aliases are those

assigned for Hyper Parallel Access Volumes. See “DEVSERV QPAV commands” (page 20)for proper syntax and an example of this command.If the correct aliases for Hyper Parallel Access Volumes do not appear after running theDEVSERV QPAV command, and if the host only accesses the corresponding P9500, disablethe Hyper Parallel Access Volumes option on the host computer, and then enable the optionagain. Proceed to step 3.If the host accesses other storage systems that use Hyper Parallel Access Volumes, issue thefollowing commands from the host to all base devices in the corresponding CU.V base_device_number1-base_device_number2,OFFLINE

CF CHP (channel_path1-channel_path2),OFFLINE

CF CHP(channel_path1-channel_path2),ONLINE

V base_device_number1-base_device_number2,ONLINE

If Data Exchange is being used on the host computer, issue the following commands.VCross_OS_File_Exchange_Volume_1-Cross_OS_File_Exchange_Volume_2,OFFLINE

Verifying Hyper Parallel Access Volumes aliases from z/OS 17

VCross_OS_File_Exchange_Volume_1-Cross_OS_File_Exchange_Volume_2,ONLINE

3. After performing one of the preceding actions, reissue the DEVSERV QPAV command andcheck for the alias devices in the returned results.

Verifying Hyper Parallel Access Volumes aliases from z/OS on z/VMWhen you restart a P9500 storage system while using Hyper Parallel Access Volumes, you mustverify that the correct aliases are sustained to a CU.To verify Hyper Parallel Access Volumes aliases on a z/OS system (which is a guest OS on z/VM):1. Enable the Hyper Parallel Access Volumes option on the z/VM and on the z/OS.2. Issue the QUERY PAV command from z/VM to verify that the displayed aliases are those

assigned for Hyper Parallel Access Volumes. See “QUERY PAV command” (page 23) forproper syntax and an example of this command.

3. Issue the DEVSERV QPAV command from z/OS to verify that the displayed aliases are thoseassigned for Hyper Parallel Access Volumes. See “DEVSERV QPAV commands” (page 20)for proper syntax and an example of this command.

4. If the correct aliases for Hyper Parallel Access Volumes do not appear after running the QUERYPAV and DEVSERV QPAV commands, and if the host only accesses the corresponding P9500,disable the Hyper Parallel Access Volumes option on the host computer, and then enable theoption again. Skip to step 5.If the host accesses other storage systems that use Hyper Parallel Access Volumes, performthe following procedure:1. Issue the following command from z/OS which 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 forHyper Parallel Access Volumes in the corresponding CU.DET alias_device_number1-alias_device_number2

DET base_device_number1-base_device_number2

VARY OFFLINE alias_device_number1-alias_device_number2

VARY OFFLINE base_device_number1-base_device_number2

VARY OFFLINE CHPID channel_path1

VARY OFFLINE CHPID channel_path2

:VARY ONLINE CHPID channel_path1

VARY ONLINE CHPID channel_path2

:VARY ONLINE base_device_number1-base_device_number2

VARY ONLINE alias_device_number1-alias_device_number2

ATT base_device_number1-base_device_number2*

ATT alias_device_number1-alias_device_number2*

3. Issue the following command from z/OS to all base devices in the corresponding CU.V base_device_number1 - base_device_number2,ONLINE

4. Issue the following command from z/OS to all channel paths configured on thecorresponding CU. This command must be issued for each channel path.V PATH(base_device_number1-base_device_number2, channel_path),ONLINE


5. Reissue the DEVSERV QPAV command and check for the alias devices in the returned results.

Monitoring with MVS commandsMVS commands can be used to monitor the Parallel Access Volumes activities on the P9500 fromz/OS. For the complete syntax of MVS commands, see the IBM document OS/390 MVS SystemCommands (GC28–1781).

DISPLAY commandThe MVS DISPLAY command displays path information and alias count for the specified basedevice. Use the following syntax for this command.D M=DEV(device_unit_ID)

The following figure shows a sample output of this command for a Parallel Access Volumes basedevice with five aliases.

The following figure shows a sample output of this command for a Hyper Parallel Access Volumesbase device with 16 aliases.

DEVSERV PATHS commandThe MVS DEVSERV PATHS command displays the status of the specified base device. Use thefollowing syntax for this command.DS P,device_unit_ID


Monitoring with MVS commands 19

DEVSERV QPAV commandsThe MVS DEVSERV QPAV commands can be used for the following functions.

• Display the status of Parallel Access Volumes base devices. Use the following syntax for thiscommand.DS QP,device_unit_ID,4


• Display the status of a Hyper Parallel Access Volumes base device and its alias devices. Usethe following syntax for this command.DS QP,device_unit_ID,HPAV


• Display the status of an entire SSID. Use the following syntax for this command.DS QP,SSID=device_unit_ID



• Display the status of the host and storage system configuration. Use the following syntax forthis command.DS QP,device_unit_ID,VOLUME


DISPLAY IOS HYPERPAV commandThe MVS DISPLAY IOS HYPERPAV command displays the current HYPERPAV enablement status.Use the following syntax for this command.

DISPLAY IOS HYPERPAV command 21

D IOS,HYPERPAV


GTF I/O tracingParallel Access Volumes are compatible with GTF I/O tracing. When a device number is specifiedfor a GTF I/O tracing operation, GTF determines if the device is a Parallel Access Volumes basedevice and automatically includes the alias addresses currently assigned to the base device. Formore information on GTF I/O tracing, see the IBM document OS/390 MVS Diagnosis: Tools andService Aids (SY28-1085).

VM CP commands for z/VMVM CP commands can be used to monitor the Parallel Access Volumes activities on the P9500from z/VM.The following syntax conventions are used for VM CP commands.

• BOLD AND CAPITALIZED characters—Indicate characters that must be entered

• lowercase characters—Indicate characters that can be omitted

• italic characters—Indicate a type of operand. An arbitrary value can be entered

• brackets ([ ])—Indicate an operand that can be omitted

• braces ({ })—Indicate that one operand must be selected from the list of operands enclosedby the braces. Operands enclosed within the braces are delimited by vertical bars (|)

QUERY CU commandThe QUERY CU command displays information about DASD CU. Use the following syntax for thiscommand.

Q CU [DASD] {ssid | ssid1 | ssid2} {ALiases | DEVices | PAVMode}



NOTE: The QUERY CU command may only be executed on the OS that is used directly by thehost computer. Any attempt to execute the QUERY CU command on the z/VM that is operated asa guest OS on the other z/VM is rejected.

QUERY DASD DETAILS commandThe QUERY DASD DETAILS command displays information about DASD (RDEV). Use the followingsyntax for this command.

Query DAsd DETAILS {rdev | rdev1 | rdev2}


CAUTION: The QUERY DASD DETAILS command cannot be used for a 3380 DASD.

QUERY PAV commandThe QUERY PAV command displays the list of Parallel Access Volumes or Hyper Parallel AccessVolumes devices (including information on those devices) that are managed by the correspondingstorage system. Use the following syntax for this command.

Query PAV {rdev | rdev1 | rdev2 | ALL}


QUERY DASD DETAILS command 23

QUERY VIRTUAL DASD DETAILS commandThe QUERY VIRTUAL DASD DETAILS command displays information about all DASDs that can beaccessed by z/VM. Use the following syntax for this command.

Query Virtual DAsd [DETAILS]


CAUTION: The DETAILS operand is only valid for dedicated DASD and mini-disk DASD.

QUERY VIRTUAL PAV commandThe QUERY VIRTUAL PAV command displays the status of all Parallel Access Volumes and HyperParallel Access Volumes devices that can be accessed by z/VM. Use the following syntax for thiscommand.

Query Virtual PAV {vdev | vdev1 | vdev2 | ALL}



5 TroubleshootingThis chapter provides troubleshooting information.

TroubleshootingFor troubleshooting information on Remote Web Console, see the HP XP P9000 Remote WebConsole User Guide. For a complete list of Remote Web Console error codes, see HP XP P9000Remote Web Console Messages.

Troubleshooting 25

6 Support and other resourcesContacting HP

For worldwide technical support information, see the HP support website:http://www.hp.com/support

Before contacting HP, collect the following information:

• Product model names and numbers

• Technical support registration number (if applicable)

• Product serial numbers

• Error messages

• Operating system type and revision level

• Detailed questions

Subscription serviceHP 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 e-mail notification of product enhancements, new driver versions,firmware updates, and other product resources.

Documentation feedbackHP welcomes your feedback.To make comments and suggestions about product documentation, please send a message [email protected]. Include the document title and manufacturing part number. Allsubmissions become the property of HP.

Related informationThe following documents [and websites] provide related information:

• HP XP P9000 Remote Web Console Messages

• HP XP P9000 Remote Web Console User GuideYou can find these documents on the Manuals page of the HP Business Support Center website:

http://www.hp.com/support/manuals

In the Storage section, click Disk Storage Systems for hardware or Storage Software for software,and then select your product.

HP websitesFor additional information, see the following HP websites:

• http://www.hp.com

• http://www.hp.com/go/storage

• http://www.hp.com/service_locator

• http://www.hp.com/support/manuals

26 Support and other resources

http://www.hp.com/support

http://www.hp.com/go/e-updates

mailto:[email protected]


http://www.hp.com

http://www.hp.com/go/storage

http://www.hp.com/service_locator


• http://www.hp.com/support/downloads

• http://www.hp.com/storage/whitepapers

Conventions for storage capacity valuesP9000 disk arrays use the following values to calculate physical storage capacity values (harddisk drives):

• 1 KB (kilobyte) = 1,000 bytes

• 1 MB (megabyte) = 1,0002 bytes

• 1 GB (gigabyte) = 1,0003 bytes

• 1 TB (terabyte) = 1,0004 bytes

• 1 PB (petabyte) = 1,0005 bytes

• 1 EB (exabyte) = 1,0006 bytesP9000 disk arrays use the following values to calculate logical storage capacity values (logicaldevices):

• 1 KB (kilobyte) = 1,024 bytes

• 1 MB (megabyte) = 1,0242 bytes

• 1 GB (gigabyte) = 1,0243 bytes

• 1 TB (terabyte) = 1,0244 bytes

• 1 PB (petabyte) = 1,0245 bytes

• 1 EB (exabyte) = 1,0246 bytes

Typographic conventionsTable 1 Document conventions

ElementConvention

Cross-reference linksBlue text: Table 1 (page 27)

email addressesBlue, bold, underlined text

Website addressesBlue, underlined text: http://www.hp.com

Bold text • Keys that are pressed

• Text typed into a GUI element, such as a box

• GUI elements that are clicked or selected, such as menuand list items, buttons, tabs, and check boxes

Text emphasisItalic text

Monospace text • File and directory names

• System output

• Code

• Commands, their arguments, and argument values

Monospace, italic text • Code variables

• Command variables

Emphasized monospace textMonospace, bold text

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

Conventions for storage capacity values 27

http://www.hp.com/support/downloads

http://www.hp.com/storage/whitepapers

http://www.hp.com

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

28 Support and other resources

A Disabling Hyper Parallel Access VolumesThis appendix describes the procedures for disabling Hyper Parallel Access Volumes on the storagesystem.

Disabling Hyper Parallel Access Volumes from z/OS

Prerequisites• All alias devices must be removed.• You must have the Storage Administrator (Provisioning) role to perform this task.Procedure 7 To disable Hyper Parallel Access Volumes from z/OS:1. Issue the following commands to all base devices in the corresponding CU:

V base_device_number1-base_device_number2,OFFLINE

CF CHP(channel_path1-channel_path2),OFFLINE

2. Issue the following command from the host system console to disable the Hyper Parallel AccessVolumes option on the host computer.SETIOS HYPERPAV=NO

3. Uninstall Hyper Parallel Access Volumes on the Remote Web Console.4. Issue the following DEVSERV command from the z/OS to an arbitrary device per CU:

DS QD,device_ID,VALIDATE

5. Issue the DEVSERV QPAV command from the host to verify that the aliases assigned for HyperParallel Access Volumes are released. See “DEVSERV QPAV commands” (page 20) for propersyntax and an example of this command.

Disabling Hyper Parallel Access Volumes from z/OS when multiple storagesystems are used

This procedure is used when Hyper Parallel Access Volumes and Data Exchange are still used onother storage systems which are accessed from the corresponding host.Procedure 8 To disable Hyper Parallel Access Volumes from the target storage system only:1. Issue the following commands to all base devices in the corresponding CU.

V base_device_number1-base_device_number2,OFFLINE


2. Uninstall Hyper Parallel Access Volumes on the Remote Web Console.3. Issue the following commands to all base devices in the corresponding CU.

CF CHP(channel_path1-channel_path2),ONLINE

V base_device_number1-base_device_number2,ONLINE

4. Issue the DEVSERV QPAV command from the host to verify that the aliases assigned for HyperParallel Access Volumes are released. See “DEVSERV QPAV commands” (page 20) for propersyntax and an example of this command.

Disabling Hyper Parallel Access Volumes from z/OS on z/VM

Prerequisites• All alias devices must be removed.• You must have the Storage Administrator (Provisioning) role to perform this task.

Disabling Hyper Parallel Access Volumes from z/OS 29

Procedure 9 To disable Hyper Parallel Access Volumes from z/OS on z/VM:1. From z/OS on z/VM, issue the following commands to all base devices in the corresponding

CU.V base_device_number1-base_device_number2,OFFLINE


2. Issue the following command from the host system console to disable the Hyper Parallel AccessVolumes option on the host computer.SETIOS HYPERPAV=NO

3. Issue the following commands from z/VM system console to all alias devices that are usedfor Hyper Parallel Access Volumes in the corresponding CU.DET alias_device_number1-alias_device_number2

VARY OFFLINE alias_device_number1-alias_device_number2

SET CU PAV ssid1-ssid2

VARY ONLINE alias_device_number1-alias_device_number2

ATT alias_device_number1-alias_device_number2*

NOTE: An asterisk (*) is required at the end of the ATT command.

4. Uninstall Hyper Parallel Access Volumes on the Remote Web Console.5. Issue the following DEVSERV command from the z/OS to an arbitrary device per CU:

DS QD,device_ID,VALIDATE

6. Issue the QUERY PAV command from z/VM to verify that the aliases assigned for HyperParallel Access Volumes are released. See “QUERY PAV command” (page 23) for propersyntax and an example of this command.

7. Issue the DEVSERV QPAV command from the z/OS to verify that the aliases assigned forHyper Parallel Access Volumes are released. See “DEVSERV QPAV commands” (page 20)for proper syntax and an example of this command.

30 Disabling Hyper Parallel Access Volumes

B Parallel Access Volumes GUI referenceThis appendix describes the fields and options available in the Parallel Access Volumes window.

Parallel Access Volumes windowUse the Parallel Access Volumes window to assign alias devices to base devices.

DescriptionItem

Selects the LDKC that contains the desired CU(s) and LDEV(s).LDKC

Selects the logical CU image that contains the desired LDEV(s). The volume lists on the ParallelAccess Volumes window display only the LDEVs for the selected CU image. CU numbers are

CU

included in the currently selected LDKC. To indicate the CU numbers included in another LDKC,select the LDKC that includes the chosen CU number in the LDKC list.

Indicates the capacity currently being used by base volumes. The value in the parentheses indicatesthe total available capacity (in terabytes) in the storage system for Parallel Access Volumes.

Parallel AccessVolumes UsedCapacity Unlimited indicates that the available capacity is unlimited. If you are using a temporary key or

the emergency key,--- is displayed. If the used capacity is enclosed in brackets (< >), the calculation has not beencompleted.

Displays the LDEVs that are currently in use in the selected CU image. See “Base Volume List”(page 32) for a description of all fields.

Base Volume List

Displays the alias device(s) assigned to the selected base device(s). See “Alias Volume List”(page 32) for a description of all fields.

Alias Volume List

Displays the LDEVs of unused volumes in the selected CU. See “Free Volume List” (page 32) for adescription of all fields.

Free Volume List

Assigns aliases to selected base devices. When you click Add, the selected free LDEVs are assignedto the selected base devices, and the new alias devices are displayed in the Alias Volume Listbox. To complete your request to assign the new aliases as specified, you must click Apply.

Add

Cancels aliases for a selected base device. When you click Delete, the selected alias devices arecanceled, and their LDEVs are displayed the Free Volume List box. To complete canceling thealiases as specified, you must click Apply.

Delete

Applies the settings to the storage system.Apply

Discards any changes and restores the initial settings.Cancel

Parallel Access Volumes window 31

Base Volume ListThe Base Volume List box displays the LDEVs that are currently in use in the selected CU image.Each of these LDEVs can be a Parallel Access Volumes base device. When you assign and cancelaliases for base devices, you select the base devices from this list box. The following table describesthe items in the Base Volume List box.

DescriptionItem

Displays the LDKC number, CU number, and LDEV number of the base volume. For the volumeused for Parallel Access Volumes, an asterisk (*) is attached next to the LDEV number (for example,

Base Volume

00:00:00 *). The capacity of the volumes attached asterisks (*) is an object for calculation ofused capacity.

Displays the number of aliases currently assigned to the base volume in the disk storage system.The number of aliases set in the base volume by the user is also displayed in the parentheses.

Alias Count (Initial)

Displays the number of selected base volumes and the total number of base volumes in the selectedCU image.For example,2/73

Selected

indicates that two base volumes are selected out of a total of 73 base volumes in the selected CUimage.

Selects all volumes in the Base Volume List box.Select All

Alias Volume ListThe Alias Volume List box displays the alias device(s) assigned to the selected base device(s). Toview all alias devices for the selected CU image, you must select all of the base devices. Whenyou cancel aliases for base devices, you select the alias devices from this list. The following tabledescribes the items in the Base Volume List box.

DescriptionItem

Displays the LDKC, CU, and LDEV numbers of the alias volume.Alias Volume

Displays the LDKC, CU, and LDEV numbers of the base volume currently assigned to the aliasvolume in the disk storage system.

Current Base

Displays the LDKC, CU, and LDEV numbers of the base volume set by the user for the alias volume.Initial Base

Displays the number of selected alias devices and the total number of alias devices in the selectedCU image.For example,2/4

Selected

indicates that two aliases are selected out of a total of four alias devices in the selected CU image.

Selects all volumes in the Alias Volume List box.Select All

Free Volume ListThe Free Volume List box displays the LDEV IDs of unused volumes in the selected CU. Any freevolume can be used as a Parallel Access Volumes alias device. Use this list to select aliases toassign to base volumes. The following table describes the items in the Free Volume List box.

DescriptionItem

Displays the complete list of volumes available for assignment.Free Volume

Displays the number of selected free devices and the total number of free devices in the selectedCU image.For example,8/47

Selected

32 Parallel Access Volumes GUI reference

DescriptionItem

indicates that eight free devices are selected out of a total of 47 free devices in the selected CUimage.

Selects all volumes in the Free Volume List box.Select All

Parallel Access Volumes window 33

GlossaryCU Control Unit. Used to organize the storage space attached to the disk controller ( DKC). You can

group similarly configured logical devices (LDEVs) with unique control unit images (CUs). CUsare numbered sequentially. The disk array supports a certain number of CUs, depending on thedisk array model. Each CU can manage multiple LDEVs; therefore, both the CU number and theLDEV number are required to identify an LDEV.

DFSMS Data Facility Storage Management Subsystem.HCD Hardware Configuration Definition.IOCDS I/O control data set. A mainframe definition of information related to I/O and peripheral devices.IPS Installation performance specification.LDKC Logical disk controller.LUN Logical unit number. A LUN results from mapping a logical unit number, port ID, and LDEV ID to

a RAID group. The size of the LUN is determined by the emulation mode of the LDEV and thenumber of LDEVs associated with the LUN.

MVS Multiple virtual storage.parity group A set of hard disk drives that have the same capacity and that are treated as one group. A parity

group contains both user data and parity information, which enables user data to be accessedif one or more drives in the group is not available.

path A path is created by associating a port, a target, and a LUN ID with one or more LDEVs. Alsoknown as a LUN.

PAV Parallel access volume.Remote WebConsole

A browser-based program installed on the SVP that allows you to configure and manage the diskarray.

synchronous Describes computing models that perform tasks in chronological order without interruption. Insynchronous replication, the source waits for data to be copied at the destination beforeacknowledging that it has been written at the source.

volume Volume on disk. An accessible storage area on disk, either physical or virtual.WLM Workload manager.

34 Glossary

Index

Aalias device

definition, 5assigning aliases to base devices, 11

Bbase device

definition, 5Base Volume List, 31

Ccontacting HP, 26conventions

document, 27storage capacity values, 27text symbols, 27

Ddisk arrays

supported models, 5document

conventions, 27related information, 26

documentationHP website, 26providing feedback, 26

dynamic mode, 6, 10

GGTF I/O tracing, 22

HHCD file, 6help

obtaining, 26HP

technical support, 26

II/O request flows , 7, 8

Mmodes, 5MVS commands

DEVSERV PATHS, 19DEVSERV QPAV, 20DISPLAY, 19DISPLAY IOS HYPERPAV, 21introduction, 19

Ooverview, 5

PPreventive Service Planning, 10

Rreassigning aliases to different base devices, 13Refreshing data, 15related documentation, 26removing aliases from base devices, 12requirements, 9

Sstatic mode, 6, 10storage capacity values

conventions, 27Subscriber's Choice, HP, 26symbols in text, 27

Ttechnical support

HP, 26service locator website, 26

text symbols, 27typographic conventions, 27

Uused capacity calculations, 14

Vverifying base and alias device definition, 16verifying status of devices, 17VM CP commands

introduction, 22QUERY CU, 22QUERY DASD DETAILS, 23QUERY PAV, 23QUERY VIRTUAL DASD DETAILS, 24QUERY VIRTUAL PAV, 24

Wwebsites

HP , 26HP Subscriber's Choice for Business, 26product manuals, 26

WindowAlias Count (Initial) column, 32Alias Volume column, 32Alias Volume List, 31Base Volume column, 32CU list, 31Current Base column, 32Free Volume column, 32Free Volume List, 31Initial Base column, 32LDKC list, 31Used Capacity, 31

WLMPAV parameter, 6Workload Manager (WLM)

compatibility mode, 7

35

goal mode, 7overview, 6

36 Index

compatible pav user guide

Documents

microcode version

hp products

hp shallnot

hp remote web console

export requirementsyou

access volumes modes

remote web console software

commercialcomputer software