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)
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
Item
Supported device
emulation types
Main and remote sites
RAID levels supported
Continuous Access
Synchronous Z
Other required licenses
Supported mainframe host
operating systems
Mainframe related
Data path
Requirement
3390- 1 , 3390-2, 3390-3, 3390-9, 3390-L, 3380-3, 3390-M
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.
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.
zLinux
OS/390
zOS
z/VM
z/VSE
Contact your HP account team for the latest information.
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
(page
34).
8 paths at maximum, from MCU to RCU.
provides many specifications,
"Planning data paths"
System requirements
13