HP P9000 Continuous Access Synchronous for Mainframe Systems User Guide
HP
P9000 Continuous Access Synchronous for
Mainframe Systems User Guide
Abstract
This guide describes and provides instructions for using HP P9000 Continuous Access Synchronous Software to configure and
perform Continuous Access Synchronous operations on the HP P9500 disk array. The intended audience is a storage system
administrator or authorized service provider with independent knowledge of HP P9000 disk arrays and the HP Remote Web
Console.
HP Part Number: AV400-96398
Published: September 2011
Edition: Fifth
© 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, 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. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
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 resident
of) 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 Commerce
Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly
or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified
in 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-7x-00/00 or later.September 2011Fifth
Contents
1 Continuous Access Synchronous Z overview...................................................7
How Continuous Access Synchronous Z works .............................................................................7
Typical components .................................................................................................................8
Disk arrays..............................................................................................................................8
Main (MCU), remote (RCU) disk arrays...................................................................................9
Volume pairs ...........................................................................................................................9
Data path .............................................................................................................................10
Consistency groups ................................................................................................................10
Interfaces ..............................................................................................................................10
Failover software ...................................................................................................................10
Error reporting communications ...............................................................................................11
Overview of initial, update copy operations ..............................................................................11
Initial copy .......................................................................................................................11
Update copy ....................................................................................................................11
2 Requirements and specifications.................................................................13
System requirements ...............................................................................................................13
BCM specifications ................................................................................................................14
Command device ..............................................................................................................17
F/M = FB message output control option when operating R-VOLs.............................................17
PPRC specifications, restrictions ................................................................................................17
Continuous Access Synchronous Z operations performed with PPRC .........................................18
Continuous Access Synchronous Z options not supported with PPRC .........................................18
PPRC, BCM command comparison.......................................................................................19
P/DAS support, restrictions .....................................................................................................20
Restrictions........................................................................................................................20
GDPS support .......................................................................................................................20
RMF PPRC Link-path statistical information support.......................................................................21
TPC-R cooperation support.......................................................................................................23
Cache failure....................................................................................................................24
Unregistered error code for TPC-R........................................................................................24
3 Planning for Continuous Access Synchronous Z.............................................25
Preparing P9500 disk arrays....................................................................................................25
Ensuring adequate cache....................................................................................................25
Installing or removing cache memory/shared memory............................................................25
Using DASD fast write........................................................................................................25
Using an earlier model storage system..................................................................................26
Enabling R-VOL Read, other system options...........................................................................26
Planning for system performance..............................................................................................27
Planning volume pairs.............................................................................................................29
Volume pair requirements and recommendations....................................................................29
Handling duplicate VOLSERs ..............................................................................................30
Planning I/O to the R-VOL...................................................................................................31
Managing differential data.................................................................................................31
Maximum number of pairs supported...................................................................................31
Calculating maximum number of pairs.............................................................................31
Priority set for initial copy operations and scheduling order.....................................................33
Planning data paths................................................................................................................34
Amount of bandwidth required............................................................................................34
Fibre Channel requirements.................................................................................................34
Supported data path configurations.....................................................................................35
Contents 3
Planning ports...................................................................................................................37
Port requirements...........................................................................................................37
Error reporting communications................................................................................................37
4 Sharing Continuous Access Synchronous Z volumes......................................39
Volume types that can be shared with Continuous Access Synchronous Z.......................................39
Continuous Access Journal Z....................................................................................................41
Business Copy Z.....................................................................................................................41
Configurations with Business Copy Z S-VOLs.........................................................................41
Configurations with Business Copy Z T-VOLs..........................................................................42
Status reporting, data currency............................................................................................43
Virtual LVI/LUN......................................................................................................................43
Cache Residency....................................................................................................................44
Compatible XRC and CC.........................................................................................................44
Auto LUN..............................................................................................................................44
Restrictions........................................................................................................................44
5 Configuration operations...........................................................................45
Configuration workflow...........................................................................................................45
Define port attributes...............................................................................................................45
Configure disk arrays and define logical paths...........................................................................46
Configure additional logical paths............................................................................................51
Set number of volumes to be copied concurrently, path watch time................................................52
6 Pair operations.........................................................................................55
Pair operations workflow.........................................................................................................55
Check pair status....................................................................................................................55
Create pairs..........................................................................................................................55
Suspend pairs........................................................................................................................58
Resynchronize pairs................................................................................................................59
Delete pairs...........................................................................................................................59
Change fence level, other pair options......................................................................................60
7 Monitoring and maintenance.....................................................................61
Monitor pair status..................................................................................................................61
How pair status changes.....................................................................................................61
Pair status definitions..........................................................................................................61
Suspend types..............................................................................................................62
System behavior............................................................................................................63
Export pair information...........................................................................................................64
Monitor copy operations, I/O .................................................................................................64
Select data to be graphed .................................................................................................65
Resize graph, save data.................................................................................................66
Monitor, maintain logical paths................................................................................................66
Logical path status definitions..............................................................................................67
Delete logical paths...........................................................................................................67
RCU maintenance...................................................................................................................68
Change minimum paths, round trip time, other RCU options....................................................68
Add, delete SSIDs for an RCU.............................................................................................68
Delete Continuous Access Synchronous Z..............................................................................69
Managing power-off for disk arrays and network devices.............................................................69
General information...........................................................................................................69
Planned outage of the main disk array..................................................................................70
Planned outage of the remote disk array or data path.............................................................70
Planned outage of the main and remote systems....................................................................70
Miscellaneous maintenance.....................................................................................................71
ICKDSF maintenance..........................................................................................................71
4 Contents
8 Data migration.........................................................................................72
Migrate data.........................................................................................................................72
9 Planning and procedures for disaster recovery..............................................74
Disaster recovery overview.......................................................................................................74
Transfer sense information between sites...............................................................................74
File and database recovery.................................................................................................74
CSUSPEND/QUIESCE TSO command..................................................................................75
IEA494I system console message.........................................................................................75
Switch operations to the remote site..........................................................................................75
Analyze R-VOL currency......................................................................................................76
Transfer operations back to the main site...................................................................................76
10 Troubleshooting......................................................................................78
General troubleshooting..........................................................................................................78
Error codes and messages.......................................................................................................81
Service Information Messages (SIMs).........................................................................................82
Pinned track recovery..............................................................................................................82
11 Support and other resources.....................................................................83
Contacting HP........................................................................................................................83
Subscription service............................................................................................................83
Documentation feedback....................................................................................................83
Related information.................................................................................................................83
HP websites......................................................................................................................84
Conventions for storage capacity values....................................................................................84
Typographic conventions.........................................................................................................84
A Using PPRC commands for Continuous Access Synchronous Z........................86
Overview of PPRC commands...................................................................................................86
CGROUP (FREEZE/RUN) support.............................................................................................88
Requirements.....................................................................................................................89
CGROUP (FREEZE/RUN) command.....................................................................................89
Using the CGROUP command.............................................................................................90
Using PPRC TSO commands with CGROUP support................................................................91
IEA494I and IEA491E console messages...................................................................................93
IEA494I message...............................................................................................................93
IEA491E message..............................................................................................................94
P9500 response characteristics to failure conditions....................................................................94
GDPS Continuous Access Synchronous Z Compatible XRC matrix.............................................97
B Continuous Access Synchronous Z scripting................................................101
Scripting overview................................................................................................................101
Scripting syntax....................................................................................................................103
Syntax overview...............................................................................................................103
Script file requirements......................................................................................................104
Script symbols.................................................................................................................104
Execute a script....................................................................................................................105
Delete script files..................................................................................................................106
Export script trace files..........................................................................................................106
Operation macro commands..................................................................................................107
Create pairs....................................................................................................................107
Release pairs...................................................................................................................110
Suspend pairs.................................................................................................................111
Resynchronize pairs..........................................................................................................112
Change pair options........................................................................................................113
Start a pair.....................................................................................................................114
Contents 5
Get pair status.................................................................................................................114
Select devices..................................................................................................................115
Internal macro commands......................................................................................................116
Internal macro command definitions...................................................................................117
AddList......................................................................................................................117
Delay........................................................................................................................117
End...........................................................................................................................117
If / EndIf....................................................................................................................117
MakeString................................................................................................................118
Message....................................................................................................................119
SetList........................................................................................................................119
Start..........................................................................................................................119
Work variables.....................................................................................................................120
Reserved variables................................................................................................................120
Reserved result variables...................................................................................................120
Reserved status variables..................................................................................................121
Optional script parameters.....................................................................................................122
Error reporting.....................................................................................................................124
C Continuous Access Synchronous Z GUI reference........................................129
Continuous Access Synchronous Z windows.............................................................................129
Pair Operation window.........................................................................................................130
Detailed Information dialog box.........................................................................................132
Add Pair dialog box.............................................................................................................134
Suspend Pair dialog box.......................................................................................................135
Resume Pair dialog box.........................................................................................................136
Delete Pair dialog box...........................................................................................................137
Change Pair Option dialog box.............................................................................................137
Display Filter dialog box .......................................................................................................138
RCU Operation window........................................................................................................138
RCU Operations list when “MCU&RCU” selected ................................................................140
When LDKC, a CU group, or CU is selected in tree.........................................................140
When an MCU or RCU is selected in tree.......................................................................141
RCU Operations list when “Port” selected ...........................................................................141
RCU Status dialog box..........................................................................................................142
Add RCU dialog box............................................................................................................143
RCU Option dialog box.........................................................................................................144
Add Path dialog box.............................................................................................................144
Add SSID dialog box............................................................................................................145
Usage Monitor window.........................................................................................................145
History window....................................................................................................................146
History window notes.......................................................................................................147
Export operations history..................................................................................................147
System Option window..........................................................................................................148
Glossary..................................................................................................149
Index.......................................................................................................151
6 Contents
1 Continuous Access Synchronous Z overview
Unless otherwise specified, the term P9000 in this guide refers to the following disk array:
• P9500 Disk Array
The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer
browser. Actual windows may differ depending on the operating system and browser used. GUI
contents also vary with licensed program products, storage system models, and firmware versions.
Continuous Access Synchronous Z helps you create and maintain a synchronous backup of critical
data in a remote location. This manual provides information and instructions for planning,
configuring, creating, maintaining, monitoring, and troubleshooting a Continuous Access
Synchronous Z synchronous system on P9500 storage systems.
A Continuous Access Synchronous Z system creates and maintains a mirror image of a production
volume at a remote location. Data in a remote disk array using Continuous Access Synchronous
Z stays synchronized with the data in the local P9500 system. This happens when data is written
from the host to the local disk array then to the remote disk array through an interconnecting Fibre
Channel data path. The local disk array acknowledges the write I/O operation is complete to the
host after the remote disk array has acknowledged to the local disk array that the copy data has
been received.
Continuous Access Synchronous Z can be teamed with Business Copy Z or Continuous Access
Journal Z, on either or both local and remote sites. These copy tools allow restoration from one or
more additional copies of critical data.
How Continuous Access Synchronous Z works
A pair is created in the following procedure:
1. Select a volume on the local system that you want to copy.
2. Create or identify the volume on the remote system that will contain the copy.
3. Connect the local and remote systems with a Fibre Channel data path
4. Copy all local volume data to the remote volume.
During a typical initial copy, all data written to the local volume (M-VOL) is copied to the remote
volume (R-VOL), insuring that the secondary copy is a complete and consistent backup.
When a pair is suspended, writes to the local volume continues but are no longer copied to the
secondary side, and the pair is no longer synchronous.
• If a special R-VOL write option is enabled, the remote volume becomes available for read/write
access by secondary host applications. Otherwise the R-VOL remains as it was at the time of
the suspension.
• Changes to local and remote volumes (if applicable) are tracked by differential bitmaps until
the local and remote volumes are resynchronized.
• When resynchronization takes place, only the changed data is transferred, reducing copy
time.
Continuous Access Synchronous Z system transfers control parameters and FBA-format data for
consecutive updated records in a track using a single write operation. This eliminates the overhead
that is usually required for performing FBA-to-CKD and CKD-to-FBA conversions.
When Continuous Access Synchronous Z is used, the copy processing of Continuous Access
Synchronous Z is performed in addition to the processing to the volume not allocated to the
Continuous Access Synchronous Z pair. Therefore, there is a possibility that the performance
decreases compared with the case where Continuous Access Synchronous Z is not used and rises
utilization rates.
How Continuous Access Synchronous Z works 7
To plan and implement a Continuous Access Synchronous Z installation, an understanding of its
components is required. This is provided in the following sections.
Typical components
A typical configuration consists of the following elements. Many but not all require user set up.
• A P9500 system—on the local side connected to a host. The system on the remote side, which
may be a P9500 system, must be connected to the local array via Fibre Channel data paths.
The remote array may consist of a different model—XP12000 Disk Array/XP10000 Disk
Array, and so on.
• A host at the local site, connected to the local disk array. It is also highly desirable to have a
host at the secondary site connected to the remote system for use in disaster recovery. If this
is not possible, the local host must have channel connections to the remote disk array for the
data to be used in the event of a disaster.
• A volume (M-VOL) on the local system that is copied to a volume (R-VOL) on the remote system.
• Fibre Channel data paths for data transfer between the local and remote disk arrays.
• Initiator and RCU target ports for the Fibre Channel interface.
• Remote Web Console graphical user interface software, used to perform Continuous Access
Synchronous Z configuration and pair operations. Alternatively, Business Continuity Manager
(BCM) and PPRC commands can be used for pair operations.
The following shows a typical Continuous Access Synchronous Z environment.
Figure 1 Continuous Access Synchronous Z components
Disk arrays
This guide documents Continuous Access Synchronous Z operations in which the main system is
a P9500 and the remote system is a P9500, XP24000/XP20000 Disk Array, or XP12000 Disk
Array/XP10000 Disk Array.
• The main disk array consists of a main control unit (MCU) and service processor (SVP).
• The remote disk array consists of the remote control unit (RCU) and the SVP.
The main and remote disk arrays are often referred to as the MCU and RCU.
The main disk array communicates with the remote disk array over dedicated Fibre Channel data
paths.
8 Continuous Access Synchronous Z overview
Main (MCU), remote (RCU) disk arrays
The main disk array manages the M-VOL and the following operations:
• Host I/O operations to the M-VOL
• Initial copy and update copy operations between the M-VOL and R-VOL.
• Pair status and configuration information
The remote disk array manages the R-VOL and the following operations:
• Remote copy operations issued by the main system
• Assists in managing pair status and configuration (for example, rejects write I/Os to the R-VOL).
The P9500 CU can function simultaneously as a main disk array for one or more M-VOLs, and as
a remote disk array for one or more R-VOLs. This kind of configuration requires that data paths
and Fibre Channel ports to be properly configured for both copy directions.
When you use XP12000 Disk Array/XP10000 Disk Array for MCU or RCU, the CU number that
can be used is limited. The following table provides the CU number range when P9500,
XP24000/XP20000 Disk Array, or XP12000 Disk Array/XP10000 Disk Array is used for MCU
or RCU.
Table 1 CU number range when P9500, XP24000/XP20000 Disk Array, or XP12000 Disk
Array/XP10000 Disk Array is used for MCU or RCU
RCUMCU
P9500XP24000/XP20000 Disk
Array
XP12000 Disk
Array/XP10000 Disk Array
MCU:0x00 to 0x3fMCU:0x00 to 0x3fMCU:0x00 to 0x3fXP12000 Disk
Array/XP10000 Disk Array
RCU:0x00 to 0x3fRCU:0x00 to 0x3fRCU:0x00 to 0x3f
MCU:0x00 to 0xfeMCU:0x00 to 0xfeMCU:0x00 to 0x3fXP24000/XP20000 Disk
Array
RCU:0x00 to 0xfeRCU:0x00 to 0xfeRCU:0x00 to 0x3f
MCU:0x00 to 0xfeMCU:0x00 to 0xfeMCU:0x00 to 0x3fP9500
RCU:0x00 to 0xfeRCU:0x00 to 0xfeRCU:0x00 to 0x3f
IMPORTANT: If you are creating a Continuous Access Synchronous Z pair with different series
of disk arrays (for example, P9500 and XP12000 Disk Array/XP10000 Disk Array), make sure
that each disk array has a unique serial number. It is possible that a serial number overlap could
occur (although this would be extremely rare). If you have two disk arrays with the same serial
number and you need to configure remote copy pairs between the two storage systems, contact
your HP account team for assistance.
Volume pairs
As described above, data written from the mainframe host is stored in the M-VOL and the remote
copy is stored in the R-VOL. The pair can be suspended, resynchronized, reverse resynchronized,
and returned to the Simplex state.
• When paired, the volumes are synchronized.
• When suspended, new data is sent to the M-VOL but not the R-VOL.
• When resynchronized, changed data is copied to the R-VOL.
• When necessary, data in the R-VOL can be copied to the M-VOL.
During normal operations, the M-VOL remains available to the host for read and write I/O
operations. The remote system rejects write I/Os for the R-VOL, unless the write-enable option is
Volume pairs 9
specified for the R-VOL. Then, write I/O is allowed to the R-VOL while the pair is suspended. In
this instance, R-VOL and M-VOL track maps keep track of differential data and are used to
resynchronize the pair.
Volumes on the local and remote systems must be defined and formatted prior to pairing.
Data path
Continuous Access Synchronous Z operations are carried out between local and remote disk arrays
connected by a Fibre Channel interface. The data path, also referred to as the remote copy
connection, connects ports on the local P9500 system to the ports on the remote disk array. The
ports are assigned attributes that allow them to send and receive data.
One data path connection is required, but two or more independent connections are recommended,
for hardware redundancy. A maximum of eight paths per control unit (CU) can be used.
Consistency groups
A consistency group is a set of volume pairs that are in the same main and remote system on which
copy operations are performed simultaneously, and in which the pairs status remains consistent.
When you issue a command, it is executed on all pairs in the group. The pairs pair status changes
at the same time, depending on the group options.
Yet, while consistency is a primary function of a group, certain operations take priority. For example,
if the Suspended commend is issued to a consistency group in which one of the pairs is in the
process of being updated, the pair is not suspended immediately, as all the other pairs are. It is
suspended only when the update operation is completed. This allows for data integrity to be
maintained between M-VOLs and R-VOLs. The same behavior occurs for a suspended operation
caused by system failure.
Continuous Access Synchronous Z operations can be performed on pairs in a maximum of 128
consistency groups on the main system.
Interfaces
You perform Continuous Access Synchronous Z operations using any of the following interfaces:
• Remote Web Console, a browser-based interface from which Continuous Access Synchronous
Z can be setup, operated, and monitored. The GUI provides the simplest method for performing
operations, requiring no previous experience.
◦ The main disk array must be LAN-attached to a Remote Web Console computer.
◦ The remote disk array should also be LAN-attached to a separate Remote Web Console
at the remote site. This allows you to perform operations more efficiently on the remote
disk array in the event that the main site is not available.
• Configuration, pair operations, and pair status monitoring can be performed using Business
Continuity Manager commands from the host to the disk array.
• Most operations can be performed using PPRC commands from the host. All P9500 systems
support IBM PPRC host software functions.
Failover software
Host failover software is used to transfer information between host servers at the local and remote
sites. It is a critical component of any disaster recovery solution.
• When Continuous Access Synchronous Z is used as a disaster recovery tool, host failover is
required to insure effective recovery operations.
• When Continuous Access Synchronous Z is used as a data migration tool, host failover is
recommended.
10 Continuous Access Synchronous Z overview
Continuous Access Synchronous Z does not provide host-failover functions. Use the failover software
most suitable for your platform and requirements.
Error reporting communications
Error reporting communications (ERC) transfers information between host processors at the main
and remote sites. It is a critical component of a disaster recovery effort.
Overview of initial, update copy operations
When you perform the initial copy operation, all the data in the M-VOL is copied into the R-VOL.
Thereafter, Continuous Access Synchronous Z and the main and remote systems execute update
copy as often as writes are sent by the host. The update operation copies host updates to the R-VOL
at the same time that they are copied to the M-VOL.
The following figure illustrates the initial and the update copy operations.
Figure 2 Remote copy operations
Initial copy
When a new pair is created, the entire contents of the M-VOL are copied to the R-VOL, cylinder
by track (this does not include for diagnostic and unassigned alternate tracks). The initial copy
synchronizes the M-VOL and R-VOL, independently of host I/O processes.
In an initial copy, you can elect to have no data copied if the M-VOL and R-VOL are already
identical. You can also specify options that provide additional flexibility between the speed of
data transfer and system performance.
• The copy pace option allows you to specify the maximum number of tracks (1-15) that can be
copied simultaneously before the main system accepts another host request for that M-VOL. If
more tracks are copied, the operation completes more quickly; if fewer tracks are copied,
performance is maintained at a higher level.
• The priority option allows you to specify the order in which copying is performed on multiple
pairs. This is used if more pairs are being created than the maximum initial copy activity
setting.
• The maximum initial copy activity option allows you to specify the maximum number of
concurrent initial copy and resync copy operations that each main system performs (not
pair-specific).
• The Round Trip Time option allows you to specify the time limit for data to travel from the
M-VOL to R-VOL. This value is used by the system to control initial copy pace when update
copying is in progress.
These options are available on Remote Web Console only.
Update copy
If the host issues an update after the initial copy is complete, the data is written to the M-VOL and
copied to the R-VOL. The write operation is acknowledged to the host as complete after the data
is copied to the R-VOL in the RCU.
Error reporting communications 11
Update copy has a higher priority than initial copy. However, if an initial copy is in progress when
updates are sent by the host, the update copy must wait until the initial copy’s copy pace completes.
For example, if the copy pace is 15 tracks, the update copy may wait up to 15 tracks (1 cylinder).
12 Continuous Access Synchronous Z overview
2 Requirements and specifications
This chapter provides basic system requirements, along with specifications for BCM, PPRC, and
other mainframe-related interfaces and functions. In addition to the information in this chapter,
“Planning for Continuous Access Synchronous Z” (page 25) provides many specifications,
recommendations, and restrictions for the elements of a Continuous Access Synchronous Z system
that require attention before setting up and using Continuous Access Synchronous Z.
System requirements
Continuous Access Synchronous Z operations require P9500 main and remote disk array containing
the M-VOLs and R-VOLs, data paths between the disk arrays, host(s) on the primary and remote
sites, and interface software.
The following lists and describe general requirements.
Table 2 General system requirements
RequirementItem
3390-1, 3390-2, 3390-3, 3390-9, 3390-L, 3380-3, 3390-MSupported device
emulation types
Main and remote sites
• At the main site, P9500 is required.
• At the remote site, the following models can be used:
P9500
XP24000/XP20000 Disk Array (60–07–51–xx/xx or later)
XP12000/XP10000 Disk Array (50–09–98–xx/xx or later)
Contact your HP team for assistance.
Continuous Access Synchronous Z supports RAID 1, RAID 5, and RAID6 configurations.RAID levels supported
Continuous Access
Synchronous Z
• Separate license keys are required for each system.
• Must be installed on main and remote system
• Synchronous only. P9500 does not support Asynchronous.
• Can co-exist with Continuous Access Synchronous.
None.Other required licenses
Supported mainframe host
operating systems
• zLinux
• OS/390
• zOS
• z/VM
• z/VSE
Contact your HP account team for the latest information.
Mainframe related
• IBM PPRC is supported.
• If the R-VOL is assigned to the M-VOL of Continuous Access Journal Z, and the main
and/or remote systems consist of several CPU complexes, a SYSPLEX timer is required
to provide a common time reference for the host I/O timestamping function.
Contact your HP account team for the latest information.
Fibre Channel (FICON), direct or with switch connections. See “Planning data paths”
(page 34).
8 paths at maximum, from MCU to RCU.
Data path
System requirements 13
Table 2 General system requirements (continued)
RequirementItem
Logical paths
• Maximum of eight from main disk array to remote disk array.
• Logical paths are established for main and remote disk array CUs separately.
• Maximum number of logical paths allowed for a disk array is 32 (8 paths per remote
system X 4 remote systems per main system).
Maximum number of
remote systems
• Maximum of four remote systems per main system.
• Each remote system CU must be added separately to a main system.
Pair volumes
• M-VOL and R-VOL must be the same size and emulation.
• One M-VOL may only be copied to one R-VOL.
• M-VOL and R-VOL can be shared with other program product volumes. See “Volume
types that can be shared with Continuous Access Synchronous Z” (page 39).
See “Planning volume pairs” (page 29) on for more information.
Limited per P9500 system. See “Maximum number of pairs supported” (page 31).Number of pairs
Must be insured by the user. The track format for the M-VOL and R-VOL must meed the
following requirements:
Disk Track Format
• The M-VOL and R-VOL must have the same track format.
• Record zero (R0) must be standard format, with key length of zero and data length of
eight. The main system aborts the initial copy operation if R0 is not standard format.
• The CCHH (logical cylinder address and logical head address) of R0 must be identical
to the physical cylinder address and physical head address of the track.
• The CCHH of each user record in a track must be unique.
Error Reporting
Communications (ERC)
software
• Required for disaster recovery.
• Recommended for data migration.
See “Error reporting communications” (page 37) for more information.
Continuous Access
Synchronous Z Interfaces
• Remote Web Console
Required.◦
◦ Storage Administrator (Remote Copy) role is required.
◦ The main system must be LAN-attached to a Remote Web Console computer.
◦ The remote system should be attached using a separate LAN at the remote site.
• BCM
Optional.◦
◦ Command device required.
See “BCM specifications ” (page 14).
• PPRC
◦ Optional.
See “PPRC specifications, restrictions ” (page 17).
BCM specifications
Pair operations may be performed using BCM commands from the host system to the disk array.
With BCM commands, you can add, suspend, resynchronize, and delete pairs, as well as monitor
pair status. You can also create the Continuous Access Synchronous Z association between main
and remote system (add RCU).
14 Requirements and specifications
NOTE: Although the same Continuous Access Synchronous Z pair operations may be performed
by using Business Continuity Manager or PPRC, Business Continuity Manager and PPRC are
independent functions. Do not use Business Continuity Manager and PPRC for the same pair
operation.
The following tables show the correspondence between the LINK parameters (ports) and (system
adapter ID) values.
For more information on BCM, see the HP P9000 for Business Continuity Manager Software User
Guide. Also see Table 6 (page 19) for corresponding PPRC functionality.
Table 3 SAID values for PATH LINK (CL1)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
X'0088'CL9-J1LUX'0080'CL9-A1AUX'0008'CL1-J1GUX'0000'CL1-A1EU
(DKA
Add2)
(DKA
Basic)
(Add4)(Basic)
X'00A8'CLB-JX'00A0'CLB-AX'0028'CL3-JX'0020'CL3-A
X'00C8'CLD-JX'00C0'CLD-AX'0048'CL5-JX'0040'CL5-A
X'00E8'CLF-JX'00E0'CLF-AX'0068'CL7-JX'0060'CL7-A
X'0089'CL9-KX'0081'CL9-BX'0009'CL1-KX'0001'CL1-B
X'00A9'CLB-KX'00A1'CLB-BX'0029'CL3-KX'0021'CL3-B
X'00C9'CLD-KX'00C1'CLD-BX'0049'CL5-KX'0041'CL5-B
X'00E9'CLF-KX'00E1'CLF-BX'0069'CL7-KX'0061'CL7-B
X'008A'CL9-L1LLX'0082'CL9-C1ALX'000A'CL1-L1GLX'0002'CL1-C1EL
(DKA
Add3)
(DKA
Add1)
(Add5)(Add1)
X'00AA'CLB-LX'00A2'CLB-CX'002A'CL3-LX'0022'CL3-C
X'00CA'CLD-LX'00C2'CLD-CX'004A'CL5-LX'0042'CL5-C
X'00EA'CLF-LX'00E2'CLF-CX'006A'CL7-LX'0062'CL7-C
X'008B'CL9-MX'0083'CL9-DX'000B'CL1-MX'0003'CL1-D
X'00AB'CLB-MX'00A3'CLB-DX'002B'CL3-MX'0023'CL3-D
X'00CB'CLD-MX'00C3'CLD-DX'004B'CL5-MX'0043'CL5-D
X'00EB'CLF-MX'00E3'CLF-DX'006B'CL7-MX'0063'CL7-D
------X'000C'CL1-N1HUX'0004'CL1-E1FU
(Add6)(Add2)
----X'002C'CL3-NX'0024'CL3-E
----X'004C'CL5-NX'0044'CL5-E
----X'006C'CL7-NX'0064'CL7-E
----X'000D'CL1-PX'0005'CL1-F
----X'002D'CL3-PX'0025'CL3-F
----X'004D'CL5-PX'0045'CL5-F
----X'006D'CL7-PX'0065'CL7-F
------X'000E'CL1-Q1HLX'0006'CL1-G1FL
(Add7)(Add3)
----X'002E'CL3-QX'0026'CL3-G
----X'004E'CL5-QX'0046'CL5-G
----X'006E'CL7-QX'0066'CL7-G
BCM specifications 15
Table 3 SAID values for PATH LINK (CL1) (continued)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
----X'000F'CL1-RX'0007'CL1-H
----X'002F'CL3-RX'0027'CL3-H
----X'004F'CL5-RX'0047'CL5-H
----X'006F'CL7-RX'0067'CL7-H
Table 4 SAID values for PATH LINK (CL2)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
X'0098'CLA-J2XUX'0090'CLA-A2MUX'0018'CL2-J2TUX'0010'CL2-A2QU
(DKA
Add2)
(DKA
Basic)
(Add4)(Basic)
X'00B8'CLC-JX'00B0'CLC-AX'0038'CL4-JX'0030'CL4-A
X'00D8'CLE-JX'00D0'CLE-AX'0058'CL6-JX'0050'CL6-A
X'00F8'CLG-JX'00F0'CLG-AX'0078'CL8-JX'0070'CL8-A
X'0099'CLA-KX'0091'CLA-BX'0019'CL2-KX'0011'CL2-B
X'00B9'CLC-KX'00B1'CLC-BX'0039'CL4-KX'0031'CL4-B
X'00D9'CLE-KX'00D1'CLE-BX'0059'CL6-KX'0051'CL6-B
X'00F9'CLG-KX'00F1'CLG-BX'0079'CL8-KX'0071'CL8-B
X'009A'CLA-L2XLX'0092'CLA-C2MLX'001A'CL2-L2TLX'0012'CL2-C2QL
(DKA
Add3)
(DKA
Add1)
(Add5)(Add1)
X'00BA'CLC-LX'00B2'CLC-CX'003A'CL4-LX'0032'CL4-C
X'00DA'CLE-LX'00D2'CLE-CX'005A'CL6-LX'0052'CL6-C
X'00FA'CLG-LX'00F2'CLG-CX'007A'CL8-LX'0072'CL8-C
X'009B'CLA-MX'0093'CLA-DX'001B'CL2-MX'0013'CL2-D
X'00BB'CLC-MX'00B3'CLC-DX'003B'CL4-MX'0033'CL4-D
X'00DB'CLE-MX'00D3'CLE-DX'005B'CL6-MX'0053'CL6-D
X'00FB'CLG-MX'00F3'CLG-DX'007B'CL8-MX'0073'CL8-D
------X'001C'CL2-N2UUX'0014'CL2-E2RU
(Add6)(Add2)
----X'003C'CL4-NX'0034'CL4-E
----X'005C'CL6-NX'0054'CL6-E
----X'007C'CL8-NX'0074'CL8-E
----X'001D'CL2-PX'0015'CL2-F
----X'003D'CL4-PX'0035'CL4-F
----X'005D'CL6-PX'0055'CL6-F
----X'007D'CL8-PX'0075'CL8-F
------X'001E'CL2-Q2ULX'0016'CL2-G2RL
(Add7)(Add3)
----X'003E'CL4-QX'0036'CL4-G
----X'005E'CL6-QX'0056'CL6-G
----X'007E'CL8-QX'0076'CL8-G
16 Requirements and specifications
Table 4 SAID values for PATH LINK (CL2) (continued)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
----X'001F'CL2-RX'0017'CL2-H
----X'003F'CL4-RX'0037'CL4-H
----X'005F'CL6-RX'0057'CL6-H
----X'007F'CL8-RX'0077'CL8-H
Command device
Business Continuity Manager requires a command device on the Continuous Access Synchronous
Z disk array that is independent of the command device for an open system. The command device
for BCM can be configured only from BCM.
To find the command device using Remote Web Console:
1. In Remote Web Console, click File/Reports. The Report Display window displays.
2. Click the LDEV tab.
If you are using XP12000 Disk Array/XP10000 Disk Array, only the volumes with a CU: LDEV
number between 00: 00 to 3F: FF can be used as command devices.
F/M = FB message output control option when operating R-VOLs
When the suspension or the release operation is performed from Business Continuity Manager
(BCM) to the R-VOL of Continuous Access Synchronous Z pair in the Duplex status, the status of
the M-VOL becomes Suspend and the F/M = FB message is output to the host connected to MCU.
You can control the output of this message by setting the system option mode 776.
However, even if the system option mode 776 is set, the F/M = FB message is output when the
pair status becomes Suspend due to the failure. Moreover, the F/M = FB message is not output
regardless of the setting of system option mode 776 if PPRC support by host = No is selected on
the CU Option dialog box.
Table 5 Whether to output the F/M = FB message when operating R-VOLs
SettingsCause of the
suspension of M-VOL
The system option mode 776 is OFFThe system option mode 776 is ON
PPRC support by host
= No
PPRC support by host
= Yes
PPRC support by host
= No
PPRC support by host
= Yes
NoYesNoNoSuspended by the
suspension or the
release operation from
BCM to R-VOLs
NoYesNoYesSuspended by failure
PPRC specifications, restrictions
Most Continuous Access Synchronous Z operations can be performed using PPRC TSO or ICKDSF
PPRCOPY commands from the host system console. All P9500 systems support IBM PPRC host
software functions.
PPRC specifications, restrictions 17
Continuous Access Synchronous Z operations performed with PPRC
Using PPRC commands, you can perform the following operations:
• Create, suspend, resynchronize, and delete Continuous Access Synchronous Z pairs
• Suspend, resynchronize, and delete Continuous Access Synchronous Z consistency groups
• Establish and delete data paths
• View path and pair status
The following applies when using PPRC commands:
• The P9500 is capable of automatically configuring a Fibre Channel port as an initiator or
RCU target port, if required, in response to the TSO CESTPATH and CDELPATH commands.
Initiator and RCU target ports are required for sending and receiving data to and from the
main and remote system. System option mode 114 must be enabled for automatic port
configuration in response to PPRC commands. Only HP Technical Support can set System
Option Modes.
◦ The P9500 makes sure that the main disk array port specified for an interconnecting link
is offline to a host, and automatically configures it as an initiator port if required. Similarly,
the corresponding remote disk array port is configured as an RCU target port when
required.
When the CDELPATH command is issued, Continuous Access Synchronous Z logical paths
are removed. If there are no more Continuous Access Synchronous Z logical paths on
the port, the port is automatically changed from initiator port to RCU target port.
◦ If the ports are in initiator/external mix mode, initiator ports do not automatically change
to RCU target ports, nor to RCU target ports automatically change to initiator ports, even
though system option mode 114 is enabled.
• Relating to the Fibre Channel interface, do not use the CESTPATH and CDELPATH commands
when using LUN Manager’s SCSI path definition function. Fibre Channel ports must be
configured as initiator or RCU target ports before the CESTPATH and CDELPATH commands
are issued.
NOTE: Ensure that the relevant paths are offline before issuing the CESTPATH command.
The add path operation fails if active logical paths exist, because the port attribute cannot be
changed.
Continuous Access Synchronous Z options not supported with PPRC
The following Continuous Access Synchronous Z options cannot be changed using PPRC. Use
Remote Web Console to change these options.
• RCU and CU options. The following default values are used for these options:
Minimum Paths = 1◦
◦ RIO MIH Time = 15 sec
18 Requirements and specifications
◦ PPRC Support = Yes
◦ Service SIM of Remote Copy = Not Report
• Initial copy priority, the CFW (cache fast write) Data option, and DFW (DASD fast write) to
R-VOL option. If CESTPAIR is used to create a pair, the following values are used for these
options. Use Remote Web Console to change these options.
◦ Initial copy priority = 0
◦ CFW Data = Copy to R-VOL. If you select the only M-VOL value, the data set that is
updated by CFW in the M-VOL cannot be used in the R-VOL. To use this data set in the
R-VOL, release the pair and format the data set.
◦ CFW Data = only M-VOL can be set with a PPRC command when the Remote Copy
Function Switch is used. Contact your HP account team for more information.
◦ DFW to R-VOL = DFW not required. This setting does not affect M-VOL I/O performance.
If one side of cache is closed due to a remote system failure, the copy operation still uses
DFW. The difference between not required and required is that new pairs cannot be
established with the required option when one side of RCU cache is closed. In this case,
the Add Pair operation fails (This restriction applies only when the CU emulation type of
RCU is 3390).
PPRC, BCM command comparison
BCM and PPRC are independent functions. Do not use BCM and PPRC for the same pair operation.
The following lists the PPRC commands that correspond BCM commands.
Table 6 Corresponding PPRC, BCM commands
Support typeBCM commandParameterPPRC command
configYKBLDPTHDEVNCESTPATH
configPRIM
configSEC
configLINK
Not supportedCGROUP
Not supportedRESETHP
configYKMAKE/YKRESYNCDEVNCESTPAIR
configPRIM
configSEC
Command (RESYNC)MODE
Parameter (NOCOPY)
config (CopyPace)PACE
config (ErrorLevel)CRIT
Not supportedMSGREQ
Not supportedONLINSEC
configYKSUSPND
*1
DEVNCSUSPEND
configPRIM
configSEC
Not supportedPRIMARY
PPRC specifications, restrictions 19
Table 6 Corresponding PPRC, BCM commands (continued)
Support typeBCM commandParameterPPRC command
Not supportedQUIESCE
configYKDELETEDEVNCDELPAIR
PRIM
SEC
configYKRECOVERDEVNCRECOVER
PRIM
SEC
ID
configYKQUERYDEVNCQUERY
Not supportedFORMAT/UNFORMAT
Not supportedVOLUME/PATHS
configYKFREEZE/YKRUNDEVNCGROUP
configPRIM
configSEC
commandFREEZE/RUN
configYKDELPTHDEVNCDELPATH
configPRIM
configSEC
*1. The YKSUSPEND command supports only the pair suspend command for M-VOL.
P/DAS support, restrictions
Continuous Access Synchronous Z supports the IBM P/DAS host software function. P/DAS allows
you to relocate or migrate data by redirecting all application I/Os from the M-VOL to the R-VOL
without interrupting access to the data. See the following IBM publications for important information
on the requirements and procedures for P/DAS operations: Planning for IBM Remote Copy
(SG24-2595), Advanced Copy Services (SC35-0355), DFSMS MVS V1 Remote Copy Guide and
Reference (SC35-0169).
Restrictions
The following restrictions apply to P/DAS use with Continuous Access Synchronous Z:
• P/DAS through channel extenders is not supported.
• P/DAS does not support CFW operations. You must stop CFW applications before performing
P/DAS operations on Continuous Access Synchronous Z volumes.
• P/DAS swap option #2 (switch pair & swap) is supported for P/DAS between the P9500 and
XP12000 Disk Array/XP10000 Disk Array storage systems.
Contact your HP account team for the latest information on P/DAS support.
GDPS support
Continuous Access Synchronous Z provides remote copy support for IBM’s Geographically Dispersed
Parallel Sysplex® (GDPS) facility. GDPS is an IBM service for mirroring data and balancing
20 Requirements and specifications
workload on disk arrays spread across two or more sites up to 40 km (20 miles) apart. With this
support, users who are running IBM Parallel Sysplex systems can take advantage of the P9500’s
suite of remote copy options for data availability.
GDPS operations feature automatic control of groups of PPRC-managed volumes using host-based
scripts and PPRC commands; for example, CGROUP (FREEZE/RUN). GDPS support may have
additional installation requirements for Continuous Access Synchronous Z main and remote system,
depending on the P9500 firmware and Continuous Access Synchronous Z versions.
Check the following items with your HP representative:
• The P9500 does not support controlling the FREEZE Option through the CESTPATH LINK
parameter. The FREEZE Option must be controlled using the CGROUP option of CESTPATH.
• Please make changes as needed to the CESTPATH LINK definitions in your GDPS configuration
files or configuration database.
For more information on GDPS, see the following IBM publications: Geographically Dispersed
Parallel Sysplex: the S/390 Multi-site Application Availability Solution, Executive Summary
(GF22-5114); and Geographically Dispersed Parallel Sysplex: the S/390 Multi-site Application
Availability Solution (GF22-5063).
RMF PPRC Link-path statistical information support
When you use z/OS Resource Measurement Facility (RMF), and if you specify the IBM TotalStorage
Enterprise Storage Server (ESS), you can acquire PPRC Fibre Link-path statistical information.
If the total size of the data for the data-acquisition interval is 100 KB and below, zero may be
reported for the data size.
The following two tables show P9500 system adaptor IDs (SAID) for the LINK parameters (ports)
that display when PPRC Link-path statistical information is acquired with RMF.
The P9500 system adaptor ID (SAID) values in the following tables are different from the ones for
the LINK parameters of CESTPATH TSO commands (see Table 3 (page 15) and Table 4 (page
16)).
Table 7 SAID values for Link-path statistical Information (CL1)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
X'0060'CL9-J1LUX'0040'CL9-A1AUX'0020'CL1-J1GUX'0000'CL1-A1EU
(DKA
Add2)
(DKA
Basic)
(Add4)(Basic)
X'0061'CLB-JX'0041'CLB-AX'0021'CL3-JX'0001'CL3-A
X'0062'CLD-JX'0042'CLD-AX'0022'CL5-JX'0002'CL5-A
X'0063'CLF-JX'0043'CLF-AX'0023'CL7-JX'0003'CL7-A
X'0064'CL9-KX'0044'CL9-BX'0024'CL1-KX'0004'CL1-B
X'0065'CLB-KX'0045'CLB-BX'0025'CL3-KX'0005'CL3-B
X'0066'CLD-KX'0046'CLD-BX'0026'CL5-KX'0006'CL5-B
X'0067'CLF-KX'0047'CLF-BX'0027'CL7-KX'0007'CL7-B
X'0070'CL9-L1LLX'0050'CL9-C1ALX'0030'CL1-L1GLX'0010'CL1-C1EL
(DKA
Add3)
(DKA
Add1)
(Add5)(Add1)
X'0071'CLB-LX'0051'CLB-CX'0031'CL3-LX'0011'CL3-C
X'0072'CLD-LX'0052'CLD-CX'0032'CL5-LX'0012'CL5-C
X'0073'CLF-LX'0053'CLF-CX'0033'CL7-LX'0013'CL7-C
X'0074'CL9-MX'0054'CL9-DX'0034'CL1-MX'0014'CL1-D
X'0075'CLB-MX'0055'CLB-DX'0035'CL3-MX'0015'CL3-D
RMF PPRC Link-path statistical information support 21
Table 7 SAID values for Link-path statistical Information (CL1) (continued)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
X'0076'CLD-MX'0056'CLD-DX'0036'CL5-MX'0016'CL5-D
X'0077'CLF-MX'0057'CLF-DX'0037'CL7-MX'0017'CL7-D
------X'0028'CL1-N1HUX'0008'CL1-E1FU
(Add6)(Add2)
----X'0029'CL3-NX'0009'CL3-E
----X'002a'CL5-NX'000a'CL5-E
----X'002b'CL7-NX'000b'CL7-E
----X'002c'CL1-PX'000c'CL1-F
----X'002d'CL3-PX'000d'CL3-F
----X'002e'CL5-PX'000e'CL5-F
----X'002f'CL7-PX'000f'CL7-F
------X'0038'CL1-Q1HLX'0018'CL1-G1FL
(Add7)(Add3)
----X'0039'CL3-QX'0019'CL3-G
----X'003a'CL5-QX'001a'CL5-G
----X'003b'CL7-QX'001b'CL7-G
----X'003c'CL1-RX'001c'CL1-H
----X'003d'CL3-RX'001d'CL3-H
----X'003e'CL5-RX'001e'CL5-H
----X'003f'CL7-RX'001f'CL7-H
Table 8 SAID values for Link-path statistical Information (CL2)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
X'00e0'CLA-J2XUX'00c0'CLA-A2MUX'00a0'CL2-J2TUX'0080'CL2-A2QU
(DKA
Add2)
(DKA
Basic)
(Add4)(Basic)
X'00e1'CLC-JX'00c1'CLC-AX'00a1'CL4-JX'0081'CL4-A
X'00e2'CLE-JX'00c2'CLE-AX'00a2'CL6-JX'0082'CL6-A
X'00e3'CLG-JX'00c3'CLG-AX'00a3'CL8-JX'0083'CL8-A
X'00e4'CLA-KX'00c4'CLA-BX'00a4'CL2-KX'0084'CL2-B
X'00e5'CLC-KX'00c5'CLC-BX'00a5'CL4-KX'0085'CL4-B
X'00e6'CLE-KX'00c6'CLE-BX'00a6'CL6-KX'0086'CL6-B
X'00e7'CLG-KX'00c7'CLG-BX'00a7'CL8-KX'0087'CL8-B
X'00f0'CLA-L2XLX'00d0'CLA-C2MLX'00b0'CL2-L2TLX'0090'CL2-C2QL
(DKA
Add3)
(DKA
Add1)
(Add5)(Add1)
X'00f1'CLC-LX'00d1'CLC-CX'00b1'CL4-LX'0091'CL4-C
X'00f2'CLE-LX'00d2'CLE-CX'00b2'CL6-LX'0092'CL6-C
X'00f3'CLG-LX'00d3'CLG-CX'00b3'CL8-LX'0093'CL8-C
X'00f4'CLA-MX'00d4'CLA-DX'00b4'CL2-MX'0094'CL2-D
X'00f5'CLC-MX'00d5'CLC-DX'00b5'CL4-MX'0095'CL4-D
22 Requirements and specifications
Table 8 SAID values for Link-path statistical Information (CL2) (continued)
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
SAIDPortPackage
Local
X'00f6'CLE-MX'00d6'CLE-DX'00b6'CL6-MX'0096'CL6-D
X'00f7'CLG-MX'00d7'CLG-DX'00b7'CL8-MX'0097'CL8-D
------X'00a8'CL2-N2UUX'0088'CL2-E2RU
(Add6)(Add2)
----X'00a9'CL4-NX'0089'CL4-E
----X'00aa'CL6-NX'008a'CL6-E
----X'00ab'CL8-NX'008b'CL8-E
----X'00ac'CL2-PX'008c'CL2-F
----X'00ad'CL4-PX'008d'CL4-F
----X'00ae'CL6-PX'008e'CL6-F
----X'00af'CL8-PX'008f'CL8-F
------X'00b8'CL2-Q2ULX'0098'CL2-G2RL
(Add7)(Add3)
----X'00b9'CL4-QX'0099'CL4-G
----X'00ba'CL6-QX'009a'CL6-G
----X'00bb'CL8-QX'009b'CL8-G
----X'00bc'CL2-RX'009c'CL2-H
----X'00bd'CL4-RX'009d'CL4-H
----X'00be'CL6-RX'009e'CL6-H
----X'00bf'CL8-RX'009f'CL8-H
TPC-R cooperation support
The Basic HyperSwap function of TPC-R (IBM disaster recovery software) has the following
requirements:
• System option mode 114 is set to OFF.
• System option modes 484 and 769 are set to ON.
• Cnt Ac-S Z synchronous pairs are created after both the paths from MCU to RCU and from
RCU to MCU are established.
When performing a Basic HyperSwap to exchange M-VOLs and R-VOLs, Cnt Ac-S Z synchronous
pairs are resynchronized using the path that is already established (see “Configuration of Cnt Ac-S
Z synchronous pair M-VOLs and R-VOLs using TPC-R” (page 24). If a path is not established, Basic
HyperSwap will not complete correctly.
For optimal performance, the maximum number of pairs for Basic HyperSwap is 1,000 per CHA,
which is the path for accessing connected Cnt Ac-S Z volumes.
If Basic HyperSwap is performed from TPC-R, the MIH value of the host I/O and host operation
needs to be approximately one second.
If the Basic HyperSwap function is performed from TPC-R, the resources in the host system must be
ensured sufficiently. If the shortage of resources occurs, resynchronization for Cnt Ac-S Z synchronous
pair may fail with the messages of IOSHM0803E (HyperSwap Disabled) and IOSHM0201I (Reason
Code:40) in the host system. If the resynchronization failed, restore the resource shortage, and
then delete the failed M-VOL and R-VOL Cnt Ac-S Z pair in suspend status from the TPC-R. The pair
create operation must be initiated again after the failed pair deletion.
TPC-R cooperation support 23
The Basic HyperSwap function performed from TPC-R may fail, when the FREEZE command process
does not complete within 20 seconds. We recommend the following conditions to complete the
FREEZE command process within 20 seconds.
• (Number of Host paths) x (Number of LPARs) x (Number of CGROUPs (Number of CUs)) ≤
160
• Number of pairs ≤ 4,096
Figure 3 Configuration of Cnt Ac-S Z synchronous pair M-VOLs and R-VOLs using TPC-R
Cache failure
When a cache failure occurs on the storage system, recover the cache failure, and then
resynchronize the Cnt Ac-S Z pair from TPC-R. Resynchronizing the Cnt Ac-S Z pair before recovering
the cache failure causes the resynchronization to fail. In this case, TPC-R issues a pair-deletion
command and resynchronizes the Cnt Ac-S Z pair automatically. All data in the M-VOL is recopied
to the R-VOL.
Unregistered error code for TPC-R
When using Basic HyperSwap, an unregistered error code for TPC-R might be displayed. In this
case, recover the Cnt Ac-S Z pair using the method described in the following table.
Table 9 Unregistered error code for TPC-R
Recovery procedureDescriptionOperationError code
Remove the failure on the
cache, and then retry the Cnt
Ac-S Z pair creation operation.
The Cnt Ac-S Z pair creation failed because
it was executed when a failure occurred in
the cache.
Pair creation0F0E
Remove the failure in the
cache, and then retry the Cnt
The Cnt Ac-S Z pair resynchronization
operation failed because it was executed
Pair
resynchronization
Ac-S Z pair resynchronization
operation.
when a failure occurred in the cache.
Although the Cnt Ac-S Z pair is deleted and
recreated (a whole copy) by the recovery
operation of TPC-R from the Cnt Ac-S Z pair
resynchronization failure, the recovery
operation fails.
24 Requirements and specifications
3 Planning for Continuous Access Synchronous Z
This chapter provides information and instructions for planning main and remote system, pair
volumes, data paths, and the other elements.
Preparing P9500 disk arrays
The following preparations are required for the disk arrays in a Continuous Access Synchronous
Z pair relationship:
• Remote Web Console must be LAN-attached for the main and remote disk arrays. See the HP
P9000 Remote Web Console User Guide for information.
• The main and remote disk arrays must be set up for Continuous Access Synchronous Z
operations. See “Ensuring adequate cache” (page 25) and “Using DASD fast write” (page 25).
Make sure to consider the amount of Cache Residencydata that will be stored in cache when
determining the amount of cache for Continuous Access Synchronous Z operations.
• Set the system option modes, if needed, for your Continuous Access Synchronous Z
configuration on the main and remote disk arrays. See “Enabling R-VOL Read, other system
options” (page 26) for more information.
• Make sure that the main disk array is configured to report sense information to the host. The
remote disk array should also be attached to a host server for reporting of sense information
in the event of a problem with a R-VOL or remote system. If the remote disk array is not attached
to a host, it is recommended that it be attached to a main site host so that monitoring can be
performed.
• On the host operating system, make sure that the missing interrupt handler (MIH) value is set
high enough to accommodate the number of pairs, the cable length between the main and
remote system, and the initial copy pace. The recommended MIH value for Continuous Access
Synchronous Z operations is 60 seconds. For MVS, the MIH value is specified in the
SYS1.PARMLIB file. The recommended MIH value for Compatible XRC is different than for
Continuous Access Synchronous Z. If you are performing Continuous Access Synchronous Z
and Compatible XRC on the same disk array at the same time, contact your HP representative
for assistance.
• Install the data path between the main and remote system. Distribute data paths between
different storage clusters and extenders or switches to provide maximum flexibility and
availability. The logical paths between the main and remote system must be different than the
logical paths between the host and remote system. See “Planning data paths” (page 34) for
more information.
Ensuring adequate cache
Cache must be operable for the pair’s main and remote disk arrays; otherwise, the create pair
operation fails. The remote cache should be configured to adequately support Continuous Access
Synchronous Z remote copy workloads, as well as any local workload activity.
Installing or removing cache memory/shared memory
Cache memory/shared memory cannot be installed or removed when a Cnt Ac-S Z pair is in
Pending status. Check the pair status before installing or removing cache memory/shared memory.
If the pair is in Pending status, split the pair, install or remove cache memory/shared memory, and
then resynchronize the pair.
Using DASD fast write
DASD fast write (DFW) is required at the main and remote system only when Required is specified
for the PPRC DFW to R-VOL option. If DFW to an R-VOL is blocked but the pair was established
Preparing P9500 disk arrays 25
with the Required option specified, the main system detects DFW OFF at the R-VOL and suspends
the pair. The default for Continuous Access Synchronous Z pairs created using PPRC commands
is Not Required, therefore they are not suspended when DFW to R-VOL is blocked.
The DFW to R-VOL setting does not affect M-VOL I/O performance. If one side of cache is closed
due to a remote system failure, the copy operation still uses DFW. The difference between not
required and required is that new pairs cannot be established with the required option when one
side of RCU cache is closed. In this case, the Add Pair operation fails (This restriction applies only
when the CU emulation type of RCU is 3390).
Using an earlier model storage system
• If you are creating a Continuous Access Synchronous Z pair using an earlier model disk array
at the remote site (such as the XP12000/XP10000 Disk Array), make sure that both the main
and remote disk array have a unique 5–digit serial number. It is possible that a serial number
overlap could occur. If you have two systems with the same serial number, contact your HP
account team for assistance.
• When you connect the storage systems with the following combinations, the range you can
specify for each model is restricted.
◦ P9500 Disk Array and XP12000/XP10000 Disk Array
When you connect P9500 Disk Array and XP12000/XP10000 Disk Array, you can specify
the ranges in the following table.
Table 10 Range you can specify when connecting P9500 Disk Array and XP12000/XP10000
Disk Array
XP12000/XP10000 Disk Array
*1*3
P9500 Disk Array
*1
Restriction item
From 1A to GRFrom 1A to GRPort number
From 00:00 to 3F:FFFrom 00:00:00 to 00:3F:FFLDKC*2:CU:LDEV
*1 It does not affect to the value whether the model connects as MCU or RCU.
*2 LDKC number is applied only for P9500.
*3 If you connect a P9500 with an XP12000/XP10000 Disk Array, or a P9500 with an XP24000/XP20000
Disk Array, contact HP Technical Support for further information on the XP12000/XP10000 Disk Array and the
XP24000/XP20000 Disk Array DKCMAIN program version.
Enabling R-VOL Read, other system options
You can tailor P9500 systems to enable the R-VOL Read option and other functions. System option
modes related to Continuous Access Synchronous Z and PPRC operations are shown in the table
below.
(For more information on I/O to the R-VOL, see “Planning I/O to the R-VOL” (page 31).
P9500 option modes can only be changed by your HP representative. Since they are set to their
default values at installation, discuss changes with your HP team.
Table 11 Option modes for Continuous Access Synchronous Z
DescriptionOption mode
R-VOL read-only function (RCU only).20
Selects function of CRIT=Y(ALL) or CRIT=Y(PATHS).36
• Mode 36 ON: CRIT=Y(ALL) => equivalent to Fence Level = Data.
• Mode 36 OFF: CRIT=Y(PATHS) => equivalent to Fence Level = Status.
26 Planning for Continuous Access Synchronous Z
Table 11 Option modes for Continuous Access Synchronous Z (continued)
DescriptionOption mode
Allows you to change the volume that is suspended when the FREEZE command is issued from the
host. The target will change from the volume in the CU for which the FREEZE command is issued to
the volume in the entire DKC if this mode is ON.
64
• Mode 64 ON: The volume in the entire DKC is suspended.
• Mode 64 OFF: The volume in the CU for which the FREEZE command is issued is suspended.
Allows dynamic port mode setting (Initiator/RCU target for Fibre Channel) through PPRC CESTPATH
and CDELPATH commands.
114
• Mode 114 ON: Initiator ports automatically change to RCU target ports. or vice versa.
• Mode 114 OFF (default): Initiator ports do not change to RCU target ports, or vice versa.
For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same time
as the SCSI path definition function of LUN Manager. Fibre Channel interface ports need to be
configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands
are issued.
Even if you set system option mode 114 ON, initiator ports will not automatically change to RCU
target ports, nor vice versa, when these ports are in initiator/external mix mode.
Allows you to update the VOLSER and VTOC of the R-VOL while the pair is suspended, if both mode
20 and 190 are ON.
190
Allows you to select whether the Remote Copy Path status, SIM218x, is reported to the host or not.308
• Mode 308 ON: SIM218x will be reported to the host.
• Mode 308 OFF: SIM218x will not be reported to the host.
Allows you to select the indication type if you use the PPRC CQUERY command to display the remote
copy path status.
484
• Mode 484 ON: The status of path using the Fibre Channel interface is displayed. WWNN will
be indicated.
• Mode 484 OFF: The status of path using an ESCON interface is displayed. WWNN is invalid.
If the a previous model storage system or the storage system of XP12000 Disk Array/XP10000 Disk
Array microcode version 50-05-XX-XX or earlier is connected, mode 484 must be OFF.
Allows you to specify when the Basic HyperSwap function of TPC-R is used. This function can allow
the CESTPATH operation to establish a path to several RCUs at a time. Since attributes of a port are
769
switched if the CESTPATH operation is performed with system option mode 144 ON, the path status
between the main storage system and remote storage system is changed to linkdown. If the CESTPATH
operation is performed to two or more RCUs, MIH may be reported to a host, and the other CESTPATH
operation, which has detected the linkdown path, retries the CESTPATH operation. To disable an
MIH report to a host, set the system option mode to ON to disable the CESTPATH and retry the
operation when a linkdown is detected.
• Mode 769 ON: Does not retry when linkdown is detected during the CESTPATH operation.
• Mode 769 OFF: Retries when linkdown is detected during the CESTPATH operation.
Allows you to select whether to output the F/M = FB message to the host of MCU when the suspension
or the release operation is performed from Business Continuity Manager to the R-VOL of Continuous
Access Synchronous Z pair in the Duplex status.
776
• Mode 776 ON: The F/M = FB message is not output.
• Mode 776 OFF: The F/M = FB message is output.
This mode must be set to both MCU and RCU.
Planning for system performance
Remote copy operations can affect I/O performance on the host as well as the main and remote
disk arrays. Continuous Access Synchronous Z provides several options for minimizing the impact
Planning for system performance 27
of synchronous operations on performance, or maximize the effectiveness of copy operations to
ensure the best level of backup data integrity. The following options address I/O and performance:
• RCU options (see “RCU maintenance” (page 68) and accompanying information)
• System- and CU-wide options regarding initial copy (see “Set number of volumes to be copied
concurrently, path watch time” (page 52)).
• Pair options (see field descriptions in “Create pairs” (page 55))
Your HP service provider can also help you optimize copy operations and performance as follows:
• Analyze write-workload. The workload data you collect (MB/s and IOPS) helps determine the
following key elements. When sized properly, they form a data path that operates free of
data bottlenecks under all workload levels. (Bottlenecks severely impact performance.)
◦ Amount of bandwidth
◦ Number of data paths
◦ Number of host-interface paths
◦ Number of ports dedicated for Continuous Access Synchronous Z on the main and remote
system
• If you are setting up Continuous Access Synchronous Z for disaster recovery, make sure that
remote disk arrays are attached to a host server. This enables both the reporting of sense
information and the transfer of host failover information. If the remote site is unattended by a
host, you should attach the remote disk arrays to a host server at the main site so that the
system administrator can monitor conditions.
The following lists conditions that affect storage system performance and provides recommendations
for addressing them.
Table 12 Conditions affecting performance, recommendations
RecommendationDescriptionCondition
Spread write-intensive data across several
volumes to minimize queuing.
Write-intensive workloads, such as database
logging volumes, can have a significant impact
on storage system I/O response times.
Write-intensive
workloads
Spread workloads with large write block sizes
across several volumes.
Workloads with large write block sizes, such
as DB deferred writes, can impact performance.
Large block size
Spread the workload across several storage
systems to use additional channels.
The demand on the main system host channels
can affect performance.
High host channel
demand
Avoid performing restore operations to volumes
that belong to Continuous Access Synchronous
Continuous Access Synchronous Z operations
can have a negative impact on workloads with
Sequential write
operations
Z pairs. Instead, restore data to a scratcha high percentage of sequential write
volume, and then create the Continuous Access
Synchronous Z pair.
operations, such as batch processing operations
(for example, dump/restore, sort operations).
Consider increasing the cache size of the
Continuous Access Synchronous Z storage
Large cache size improves read performance,
which allows more storage system resources to
Cache size
systems to improve overall performance. Forbe devoted to write operations. Insufficient
best results, the cache and NVS capacity ofcache resources results in command retries,
the main and remote system should be thestate-change-pending (SCP) notifications, and
puncture conditions. same. This allows the remote site to function
adequately during disaster recovery.
28 Planning for Continuous Access Synchronous Z
Table 12 Conditions affecting performance, recommendations (continued)
RecommendationDescriptionCondition
Distribute Continuous Access Synchronous Z
remote copy operations among several remote
systems to avoid overloading any one system.
The remote system’s performance directly affects
the performance of the main system. If a remote
system becomes overloaded with heavy update
Capacity of remote
system
activity, host and main system performance can
also be degraded.
Install a sufficient number of data paths to will
meet all write-workload levels. This is especially
An inadequate number of data paths decreases
performance. Performing copy operations over
long distances also degrades performance.
Data paths
important for systems containing both M-VOLs
and R-VOLs.
Planning volume pairs
To plan Continuous Access Synchronous Z pair volumes, you need to do the following:
• At the local site, identify the volumes that contain important data to be backed up
• At the remote site, set up the volumes that will hold the copied data
Volume pair requirements and recommendations
The following requirements and information are provided to help you prepare Continuous Access
Synchronous Z volumes:
• A volume can only be assigned to one Continuous Access Synchronous Z pair.
• The R-VOL must be at least the same size as the M-VOL.
• Continuous Access Synchronous Z requires a one-to-one relationship between the M-VOL and
R-VOL. The M-VOL cannot be copied to more than one R-VOL, and more than one M-VOL
cannot be copied to one R-VOL.
• Logical Volume Images (LVIs)
All basic mainframe LVIs that can be configured on the P9500 system are supported for
Continuous Access Synchronous Z; for example, 3390 3, 3R, 9, L.
◦
◦ Data Exchange volumes (3390 3A/B/C) are not supported.
◦ Data can be copied between volumes with the same emulation and capacity (for example,
3390 3R to 3390 3R).
◦ Data can be copied from smaller volumes to larger volumes (for example, 3390 3 to
3390 9) of the same emulation (VTOC expansion must be used).
However, HP strongly recommends that you limit copying from a smaller volume to a
larger volume to data migration purposes and not disaster recovery. Under the disaster
recovery scenario, you would not be able to perform Continuous Access Synchronous Z
operations in the reverse direction, from the remote disk array to the main disk array,
because a larger volume cannot be copied to a smaller volume.
Also, with larger-to-smaller volumes, if the BCM SUSPEND command is issued, you cannot
use the remote system R/W option and Reverse option.
• The following disk track format are required for pair volumes. Continuous Access Synchronous
Z cannot detect exceptions to these requirements. The main system will abort the initial copy
operation if the track format for both the M-VOL and R-VOL does not meet the following
requirements.
◦ The M-VOL and R-VOL must have the same track format.
◦ Record zero (R0) must be standard format, with key length of zero and data length of
eight. The main system will abort the initial copy operation if R0 is not standard format.
Planning volume pairs 29
◦ The CCHH (logical cylinder address and logical head address) of R0 must be identical
to the physical cylinder address and physical head address of the track.
◦ The CCHH of each user record in a track must be unique.
• Continuous Access Synchronous Z operates on volumes rather than on datasets; multivolume
datasets files require special attention. For complete duplication and recovery of a multivolume
datasets (for example, a large database file that spans several volumes), make sure that all
volumes of the file are copied to Continuous Access Synchronous Z R-VOLs.
• Continuous Access Synchronous Z pair volumes can be shared with non-Continuous Access
Synchronous Z program products. See “Sharing Continuous Access Synchronous Z volumes”
(page 39) for more information.
• Continuous Access Synchronous Z also supports Virtual LVI. This allows you to configure LVIs
that are smaller than standard LVIs. When custom-size LVIs are assigned to a Continuous
Access Synchronous Z pair, the R-VOL must have the same capacity as the M-VOL. Remote
Web Console displays the LVI of M-VOLs and R-VOL.
• When creating multiple pairs concurrently, make sure that you set up R-VOL LDEV IDs in a
way that allows the system to correctly match them to your selected M-VOLs.
Even though you select multiple volumes as M-VOLs in the Remote Web Console Add Pair
procedure, only one of them displays in the dialog box—the one with the lowest LDEV ID.
Because of this, you are able to specify only one R-VOL. The system automatically assigns
LDEVs on the remote system as R-VOLs for the other selected M-VOLs according to LDEV ID.
For example, three LDEVs have been set up on the remote system to become an R-VOL, named
LDEV 01, LDEV 02, and LDEV 03. During the Add Pair operation, you select three volumes
as M-VOLs, and then select LDEV 01 as the R-VOL. The system will then assign LDEV 02 and
LDEV 03 as the R-VOL for the other two M-VOLs. Therefore, make sure that you assign LDEV
IDs to your R-VOL that will be selected in the proper order.
Handling duplicate VOLSERs
When the M-VOL is copied to the R-VOL during the initial copy operation, the M-VOL VOLSER
(Volume Serial Number) is also copied to the R-VOL. Therefore, the M-VOL and R-VOL have the
same VOLSER. Because z/OS does not allow duplicate VOLSERs, the host system administrator
must take precautions to prevent system problems related to duplicate VOLSERs (such as defining
R-VOLs not to come online automatically to the same z/OS sysplex).
If the volumes that become R-VOLs are physically attached to the same system images as the
M-VOLs, the following error-prone situations may occur:
• When a pair is established using the TSO CESTPAIR command, the remote system might be
online (PPRC allows this; Continuous Access Synchronous Z does not). This could produce a
duplex secondary online to a host image, the results of which are not predictable.
• When a pair is released, the old R-VOL is usually offline. Then, when a host system is IPL’d
(initial program loaded), the operator is offered both volumes and asked which volume should
be left offline. You can avoid duplication of the VOLSER as follows:
1. Identify the volumes that are not accessed by the host system.
2. Perform CHP OFF or some other operation to ensure that the volumes are inaccessible.
3. When performing IPL, make sure to perform LOAD CLEAR.
To avoid these problems
• HP strongly recommends that your specify OFFLINE=YES if the remote volumes are to be
generated in the production host’s IOCP and system generation.
• If you cannot create a pair because the R-VOL is online with hosts, all paths must be offline
from all hosts. If you cannot identify the hosts that are online, contact HP Technical Support.
30 Planning for Continuous Access Synchronous Z
Loading...