Preparing for compatible pav operations, System requirements, 3 preparing for compatible pav operations – HP StorageWorks XP Remote Web Console Software User Manual
Page 23: 3preparing for compatible pav operations
![background image](/manuals/398721/23/background.png)
HPAV for z/OS user guide for the XP128/XP1024/XP12000/XP10000
23
3
Preparing for Compatible PAV Operations
System Requirements
Compatible PAV operations involve the volumes on the XP1024/XP128/XP12000/XP10000, the licensed
Command View XP or XP Remote Web Console software, and the WLM host software function. If you want
to use Compatible Hyper PAV, you also need XP Remote Web Console. The system requirements for
Compatible PAV are:
•
Host software:
• For static Compatible PAV: OS/390 V1R3 or later, and DFSMS/MVS® 1.3 or later VM/ESA 2.4.0
or later.
• For dynamic Compatible PAV: OS/390 V2R7 with APAR OW39854, and DFSMS/MVS 1.5 or
later.
• For Compatible Hyper PAV: z/OS 1.8 or later, and z/OS 1.6 with PTF or later
• Hyper PAV for zOS 1.6/1.7/1.8: OA13915 IOS support, OA13928, OA13929, OA14002
and OA14005, DFSMS support, OA12699 WLM support, OA14556 GRS support, OA14248 ASM
support
•
XP1024/XP128/XP12000/XP10000: The emulation type for a CU image that controls Compatible PAV
devices must be 2105 (see ”
Changing the Controller Emulation Type
•
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 an XP1024/XP128/XP12000/XP1000 is defined using one CNTLUNIT statement in
IOCP. The unit type is 2105 or 2107 for XP12000K/XP10000. Up to 16 LCUs can be defined. An
LCU is identified by its ‘Control Unit Address’ (‘CUADDR=x’ parameter) and is specified as a
hexadecimal number in the range of ‘0’ to ‘F’. An LCU is the same as an IBM Logical Sub-System or
LSS. While it is possible to have an LCU on an XP1024/XP12000/XP10000 defined using multiple
CNTLUNIT statements in IOCP, the resulting input deck cannot be migrated to HCD due to an IBM
restriction to allow only one CNTLUNIT definition.
• Up to 256 devices may be defined on each LCU. Base device addresses are identified as unit type
3390B. Alias device addresses are identified as 3390A.
•
HCD definition considerations: If you use HCD exclusively to define I/O definitions to z/OS and
OS/390 and to automatically run the IOCP program to create SCDS or IOCDS, the following definition
rules apply:
• Each LCU on an XP1024/XP128/XP12000/XP10000 is defined as a 2105 or 2107 control unit.
• Base devices are defined as 3390B device types. HCD will only connect base devices to one
control unit. Base device optional parameter definitions in HCD include the ‘WLMPAV=xxx’
parameter. The default setting is ‘YES’.
• Alias devices are defined as 3390A device types. HCD will only connect alias devices to one
control unit. Alias devices have only one optional parameter definition in HCD. The ‘WLMPAV=xxx’
parameter defaults to ‘YES’.
•
Command View XP or XP Remote Web Console: See the HP StorageWorks Command View XP User
Guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console User Guide for the specific
disk array.
NOTE:
Administrator access to the Command View XP management station or XP Remote Web Console
is required to perform Compatible PAV operations. Users without administrator access can only view
Compatible PAV information.