HP XP P9000 for Business Continuity Manager Software 7.6.
© Copyright 2009, 2013 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.
Version: 7.6.0-00 Description This document contains release notes for the HP XP P9000 for Business Continuity Manager Software. About this release This release is a major release that adds new features. Superseded version 7.5.0 Operating systems The operating system shown in the following table is required. Table 1 Applicable operating system Operating systems Required version z/OS V1R10–V1R13 License keys You cannot use the license keys that you installed for release 05-03 or earlier.
Table 3 Supported enhancements and features in 7.6.0-00 (continued) # Item New features and enhancements For this support, creating or updating a disk configuration definition will be available in a batch job. 2 Supported an output function of the CLI command-execution log to the console. Specify a BCM Manager Environment variable to use this function. BCM can use each function by the shown storage system.
Prerequisites Prerequisite programs The following software programs must be installed to use BCM. Table 5 Prerequisite programs to install Program name Notes DFSMS Standard OS component ISPF Standard OS component TSO/E Standard OS component TSO/E REXX Standard OS component Security Server To use the resource access control facility (RACF) IBM Library for REXX on zSeries Release 4 (FMID HWJ9140) The REXX Alternate Library is included in standard OS component.
Performing operations in a 2DC configuration with HyperSwap and Continuous Access Journal The following software program is required when running BCM in a 2DC configuration with HyperSwap and Continuous Access Journal. Table 8 Prerequisite programs when performing operations in a 2DC configuration with HyperSwap and Cnt Ac-J # Program name Notes 1 IBM Tivoli Storage Productivity Center for Replication for System z 4.2.
C: Number of copy group parameters specified in the YKMONCG file. S: Number of action parameters specified in the YKMONCG file.
Installation instructions Installation precautions Review the following manual references for installation: • Before starting installation, ensure that there are sufficient dataset capacity and number of directories in the distribution libraries and the target libraries that are required for installation. • See the installation chapter of the HP XP P9000 for Business Continuity Manager Software Installation Guide for full details.
Compatibility/interoperability System configuration • BCM supports 2DC configurations (1:1). By making multiple units of 2DC configurations, it is possible to create N:N configurations. • BCM supports 3DC (Cnt Ac-S and Cnt Ac-J) configurations (Cascade configurations and Multi-Target configurations). Note that 3DC configurations are supported only when all storage systems in the configurations are XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or XP P9500 disk arrays.
Other • From BCM 04-00, CLI Command-Execution Logs are output to SYSLOG. This applies to the CLI commands that are executed from within the ISPF panels of BCM. Therefore, large amounts of data will be output to SYSLOG when you make frequent use of BCM or issue many CLI commands. • BCM does not support the multiplatform volume. • From z/OS V1R8, a console ID cannot be specified to the CN operand of the TSO/E SEND command.
Table 11 Restrictions (continued) # Restrictions 4 When using BCM to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync, start the business operation after Cnt Ac-S and Cnt Ac-J copy pairs are formed so the Multi-Target configuration is established. 5 BCM does not support a recovery procedure from failure in 4x4x4 Multi-Target configuration with Delta Resync by misoperation.
Table 13 Messages Column Head Column Head Column Head Column Head YKC032I HP storage systems Found HP storage systems Devices Found 7.6.0-00 YKZ330E detected the service error. (return code=[, reason code=]) detected the service error. (return code=[, reason code=][, abend code=]) 7.6.0-00 YK7000T - Added. 7.6.
Table 14 Additional information and documentation updates (continued) Guide name Location to be updated Updates YKMAKE command with the HOLD parameter to the dissolved Cnt Ac-J Z copy pairs or Delta Resync pairs, or issue the YKMAKE command with the SELECT(COND) parameter to (undissolved) Cnt Ac-J Z copy pairs to re-register them to the EXCTG. Messages 1.
Table 16 Prerequisite software Item Description z/OS or OS/390 V2R10 Versions supported by BCM V7.6.0 BCM V7.6.0 • Basic License • Cnt Ac-J 4x4 Extended CTG License Table 17 Storage system settings Item Description Remarks Arbitration command devices Storage systems at the remote site: One Arbitration command devices must be set or more arbitration command devices up with Remote Web Console. for each subordinate DKC. Journal groups Journal groups for Cnt Ac-J. Timer type must be “System.
Table 18 Software settings (OS and BCM) Item Description Remarks Route list (Configuration file) As in the basic 3DC Multi-Target configuration with Delta Resync pairs, the host at each site must have its own route list. None See “Preparing the Software (OS, Business Continuity Manager)” in the User Guide to set up a route list. Cnt Ac-S copy group (Configuration file) • Cnt Ac-S Consistency Preservation function must be applied.
Table 19 Overview of CLI commands (continued) # CLI command 4x4x4 configuration Differences from previous version Remarks Therefore, issuing the YKQUERY command to such copy pairs causes the YKZ296E error message to occur. SELECT(COND) parameter to the Cnt Ac-J copy pairs between the Local and the Remote sites to re-register them to EXCTG.
Table 20 Operation procedure of 4x4x4 Multi-Target configuration with Delta Resync # Operation procedure Description Configuration Difference from 3DC Multi-Target configuration • Bi-directional paths must be set between P-L, P-R and L-R sites. 1DC Arbitration paths and command devices for 4x4 configuration are necessary. Preparation 1 Hardware setup • One or more Journal groups in each site. • Arbitration paths and arbitration command devices.
