Hitachi Universal Storage Platform V Hitachi TrueCopy for IBM z/os User s Guide

Transcription

1 Hitachi Universal Storage Platform V Hitachi TrueCopy for IBM z/os User s Guide FASTFIND LINKS Document Organization Product Version Getting Help Contents

2 ii

3 Contents Preface...ix Overview of Hitachi TrueCopy for z/os Hitachi TrueCopy for IBM z/os Feature Highlights Business Benefits Applications of TrueCopy Synchronous and TrueCopy Asynchronous About TrueCopy for z/os Operations TrueCopy for z/os Components USP V Control Units (MCUs and RCUs) Pairs (M-VOLs and R-VOLs) Remote Copy Connections Initiator Ports and RCU Target Ports USP V TrueCopy Software Asynchronous Consistency Groups Host I/O Time-Stamping Function Error Reporting Communications Remote Copy Operations Initial Copy Operation Update Copy Operation Read and Write I/O Operations for TrueCopy for z/os Volumes R-VOL Read Option TrueCopy for z/os Async Recordset Operations Creating and Storing Recordsets at the MCU Sending Recordsets to the RCU Storing Recordsets at the RCU Selecting and Settling Recordsets at the RCU Types of Recordsets Contents iii

4 Inflow Control of Recordsets Graduated Delay Sidefile Management TrueCopy for z/os Async Consistency Group Operations Group Options Group Consistency Time Group Operations Pair Status Suspended Pairs Suspended TrueCopy for z/os Async Pairs Business Continuity Manager Support Command Device PPRC Support P/DAS Support GDPS Support RMF PPRC Link -path Statistical Information Support Interoperability with Other Products and Functions ShadowImage for z/os (SIz) Universal Replicator for z/os (URz) Virtual LVI Cache Residency Manager Server Priority Manager Preparing for TrueCopy for z/os Operations System Requirements Requirements and Restrictions Track Format One-to-One Volume Copy Operations Duplicate VOLSER Logical Volume Image (LVI) Accessing TrueCopy for z/os M-VOLs and R-VOLs Cache, NVS, and DASD Fast Write Consistency Groups Restrictions on Volumes Assessing TCz Requirements Calculation of the Maximum Number of Pairs Performance and DR Considerations Identifying the Source and Target Volumes Installing the Hardware Remote Copy Connections Channel Extenders for Serial Remote Copy Connections Enabling TrueCopy for z/os Options Configuring the MCUs and RCUs for TrueCopy for z/os Operations Fibre-Channel Interface Configuration iv Contents

5 Using TrueCopy for z/os GUI TrueCopy for z/os Windows Pair Operation Window Volume List Display Filter Snapshot Function RCU Operation Window MCU&RCU Display on the RCU Operation Window Port Display on the RCU Operation Window Asynchronous Operation Window Usage Monitor Window Script Operation Window History Window System Option Window Performing TrueCopy for z/os Configuration Operations RCU Operations Configuring the Host Interface Ports Adding an RCU RCU Path Parameters Changing the RCU Options Adding and Deleting Logical Paths to an RCU Adding and Deleting SSIDs for an RCU Viewing RCU Status Deleting an RCU Asynchronous Operations Setting the Asynchronous Copy Options Adding Consistency Groups Changing the Consistency Group Options Viewing Consistency Group Status Deleting Consistency Groups Usage Monitor Operations Starting and Stopping Monitoring Displaying the Usage Monitor Graph Exporting the Usage Monitor Data File Script Operations Executing the Script Exporting the Script Trace Files History Operations Exporting the History File Other Operations Clearing SIMs Changing the Option Settings of Storage System Contents v

6 Changing the Option Settings of CUs Configuring and Maintaining Your TCz Environment Optimizing TrueCopy for z/os Operations and Storage System Performance Changing from 3990 to 2105 or 2107 Emulation Powering Off/On TrueCopy for z/os Components Planned Outage of the MCU Planned Outage of the RCU or Remote Copy Connection Planned Outage of the MCU and RCU Discontinuing TrueCopy for z/os Operations Performing TrueCopy for z/os Pair Operations Creating TrueCopy for z/os Pairs Initial Copy Options Pair Options Changing Pair Options Viewing TrueCopy for z/os Pair status Splitting TrueCopy for z/os Pairs Resynchronizing TrueCopy for z/os Pairs Releasing TrueCopy for z/os Pairs ICKDSF Considerations for TrueCopy for z/os Volumes ICKDSF on a TrueCopy for z/os M-VOL ICKDSF on a TrueCopy for z/os R-VOL Pinned Track Recovery for TCz Volumes TrueCopy for z/os Usage Scenarios This chapter describes several usage scenarios for TrueCopy for z/os Using TrueCopy for z/os for Disaster Recovery Using TrueCopy for z/os for Disaster Recovery Preparing for Disaster Recovery Considering the M-VOL Fence Level Setting Transferring Sense Information Between Sites File and Database Recovery Procedures CSUSPEND/QUIESCE TSO Command IEA494I System Console Message Analyzing the Currency of TrueCopy for z/os Sync R-VOLs Analyzing the Consistency of TrueCopy for z/os Async R-VOLs Transferring Operations Back to the Main Site Resuming Normal Operations at the Main Site Using TrueCopy for z/os for Data Migration Using TrueCopy for z/os for Duplication vi Contents

7 Troubleshooting General Troubleshooting Error Codes and Messages SIM Reporting Calling the HDS Support Center Using PPRC Commands for TrueCopy for z/os... 1 Overview of PPRC Commands...2 Using PPRC TSO Commands with TCzA...7 CESTPATH...9 CESTPAIR...15 CSUSPEND...19 CDELPAIR...21 CRECOVER...22 CQUERY...23 CGROUP (FREEZE/RUN) Support...29 Requirements...29 CGROUP (FREEZE/RUN) Command...32 Using the CGROUP Command...35 Using PPRC TSO Commands with CGROUP Support...36 IEA494I and IEA491E Console Messages...41 IEA494I Message...41 IEA491E Message...43 USP V Response Characteristics to Failure Conditions...44 GDPS-TCz Matrix...47 TrueCopy for z/os Scripting... 1 Overview of Scripting...2 Syntax for Scripting...4 Syntax Overview...4 Script File Requirements...6 Script Symbols...6 Operation Macro Commands...7 Create Pairs...7 Release Pairs...11 Suspend Pairs...13 Resynchronize Pairs...15 Change Pair Options...17 Starting a Pair...19 Getting Pair Status...20 Selecting Devices...21 Internal Macro Commands...23 Contents vii

8 Internal Macro Command Definitions Work Variables Reserved Variables Reserved Result Variables Reserved Status Variables Optional Script Parameters Error Reporting TrueCopy for z/os Load Balancing and Sidefile Management and Control... 1 Load Balancing and Sidefile Management and Control... 2 Acronyms and Abbreviations... 1 Index... 1 viii Contents

9 Preface This document describes and provides instructions for performing Hitachi TrueCopy for IBM z/os operations on the Hitachi Universal Storage Platform V storage system using the TrueCopy for IBM z/os software on Storage Navigator. Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes. This preface includes the following information: Intended Audience Product Version Document Revision Level Changes in this Revision Document Organization Referenced Documents Document Conventions Convention for Storage Capacity Values Getting Help Comments Note: The Storage Navigator windows shown in this document were captured on a Windows system with the Internet Explorer web browser. The Storage Navigator screens may display differently on other operating systems and browsers. Please refer to the Storage Navigator User s Guide for information on other supported operating systems and browsers. Notice: The use of Hitachi TrueCopy for IBM z/os and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems. Preface ix

10 Intended Audience This document is intended for system administrators, Hitachi Data Systems representatives, and Authorized Service Providers who are involved in installing, configuring, and operating the Hitachi Universal Storage Platform V storage system. This document assumes the following: The user has a background in data processing and understands RAID storage systems and their basic functions. The user is familiar with the Hitachi Universal Storage Platform V storage system and has read the Universal Storage Platform V User and Reference Guide. The user is familiar with the Storage Navigator software for the Universal Storage Platform V and has read the Storage Navigator User s Guide. Product Version This document revision applies to Universal Storage Platform V microcode x and higher. Document Revision Level Revision Date Description MK-96RD623-P February 2007 Preliminary Release MK-96RD April 2007 Initial Release, supersedes and replaces MK-96RD623-P MK-96RD May 2007 Revision 1, supersedes and replaces MK-96RD Changes in this Revision Not applicable to this release. x Preface

11 Document Organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter / Appendix Description 1 Overview of Hitachi TrueCopy for z/os Provides an overview of Hitachi TrueCopy for z/os. 2 About TrueCopy for z/os Operations Describes Hitachi TrueCopy for z/os operations. 3 Preparing for TrueCopy for z/os Operations Describes the requirements for using TrueCopy for z/os and provides instructions for installing the TrueCopy for z/os hardware and software and preparing the Hitachi storage systems for TrueCopy for z/os operations. 4 Using the TrueCopy for z/os GUI Describes the TrueCopy for z/os windows on Storage Navigator. 5 Performing TrueCopy for z/os Configuration Operations Provides instructions for performing TrueCopy for z/os configuration operations. 6 Performing TrueCopy for z/os Pair Operations Provides instructions for performing TrueCopy for z/os pair operations. 7 Usage Scenarios Describes several usage scenarios for TrueCopy for z/os. 8 Troubleshooting Provides troubleshooting information for TrueCopy for z/os and instructions for calling technical support. A Using PPRC Commands for TrueCopy for z/os Describes how to use PPRC commands to perform TrueCopy for z/os operations. B TrueCopy for z/os Scripting Describes how to use script files to perform TrueCopy for z/os operations. C Load Balancing and Sidefile Management and Controls Discusses performance considerations for TrueCopy for z/os such as load balancing and sidefile management and provides recommendations for optimizing TrueCopy for z/os operations. -- Acronyms and Abbreviations Defines the acronyms and abbreviations used in this document. -- Index Lists the topics in this document in alphabetical order. Referenced Documents Hitachi Universal Storage Platform V: Storage Navigator Messages, MK-96RD613 LUN Manager User s Guide, MK-96RD615 ShadowImage for IBM z/os User s Guide, MK-96RD619 Storage Navigator User s Guide, MK-96RD621 TrueCopy User s Guide, MK-96RD622 Universal Replicator for IBM z/os User s Guide, MK-96RD625 Virtual LVI/LUN and Volume Shredder User s Guide, MK-96RD630 USP V User and Reference Guide, MK-96RD635 Mainframe Host Attachment and Operations Guide, MK-96RD645 Preface xi

12 Hitachi TagmaStore Universal Storage Platform and Network Storage Controller: TagmaStore USP User and Reference Guide, MK-94RD231 TagmaStore NSC User and Reference Guide, MK-95RD279 Storage Navigator Error Codes, MK-94RD202 LUN Manager User s Guide, MK-94RD203 Storage Navigator User s Guide, MK-94RD206 TrueCopy for z/os User and Reference Guide, MK-94RD214 Performance Manager User s Guide, MK-94RD218 Universal Volume Manager User's Guide, MK-94RD220 Virtual Partition Manager User s Guide, MK-94RD259 Hitachi Business Continuity Manager: User s Guide, MK-94RD247 Messages, MK-94RD262 Installation, MK-95HC104 Reference Guide, MK-95HC105 IBM Documentation: Planning for IBM Remote Copy, SG Advanced Copy Services, SC DFSMS MVS V1 Remote Copy Guide and Reference, SC Geographically Dispersed Parallel Sysplex: The S/390 Multi-site Application Availability Solution, Executive Summary, GF xii Preface

13 Document Conventions The terms Universal Storage Platform V and USP V refer to all models of the Hitachi Universal Storage Platform V, unless otherwise noted. This document uses the following typographic conventions: Typographic Convention Bold Description Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables. screen/code Indicates text that is displayed on screen or entered by the user. Example: # pairdisplay -g oradb < > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group> Note: Italic font is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. underline Indicates the default value. Example: [ a b ] This document uses the following icons to draw attention to information: Icon Meaning Description Note Tip Caution WARNING DANGER ELECTRIC SHOCK HAZARD! ESD Sensitive Calls attention to important and/or additional information. Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Warns the user of adverse conditions and/or consequences (e.g., disruptive operations). Warns the user of severe conditions and/or consequences (e.g., destructive operations). Dangers provide information about how to avoid physical injury to yourself and others. Warns the user of electric shock hazard. Failure to take appropriate precautions (e.g., do not touch) could result in serious injury. Warns the user that the hardware is sensitive to electrostatic discharge (ESD). Failure to take appropriate precautions (e.g., grounded wriststrap) could result in damage to the hardware. Preface xiii

14 Convention for Storage Capacity Values Getting Help Physical storage capacity values (e.g., disk drive capacity) are calculated based on the following values: 1 KB = 1,000 bytes 1 MB = 1,000 2 bytes 1 GB = 1,000 3 bytes 1 TB = 1,000 4 bytes 1 PB = 1,000 5 bytes Logical storage capacity values (e.g., logical device capacity) are calculated based on the following values: 1 KB = 1,024 bytes 1 MB = 1,024 2 bytes 1 GB = 1,024 3 bytes 1 TB = 1,024 4 bytes 1 PB = 1,024 5 bytes 1 block = 512 bytes If you need to call the Hitachi Data Systems Support Center, make sure to provide as much information about the problem as possible, including: The circumstances surrounding the error or failure. The exact content of any error messages displayed on the host system(s). The exact content of any error messages displayed by Storage Navigator. The Storage Navigator configuration information (use the FD Dump Tool). The service information messages (SIMs), including reference codes and severity levels, displayed by Storage Navigator and/or logged at the host. The Hitachi Data Systems customer support staff is available 24 hours/day, seven days a week. If you need technical support, please call: United States: (800) Outside the United States: (858) xiv Preface

15 Comments Please send us your comments on this document. Make sure to include the document title, number, and revision. Please refer to specific section(s) and paragraph(s) whenever possible. Fax: Mail: Technical Writing, M/S Hitachi Data Systems Scripps Ranch Blvd. San Diego, CA Thank you! (All comments become the property of Hitachi Data Systems Corporation.) Preface xv

16

17 1 Overview of Hitachi TrueCopy for z/os This chapter provides an overview of Hitachi TrueCopy for IBM z/os. Overview of Hitachi TrueCopy for z/os 1-1

18 Hitachi TrueCopy for IBM z/os Hitachi TrueCopy for z/os Remote Replication software provides a continuous, nondisruptive, host-independent remote data replication solution for disaster recovery or data migration over any distance. TrueCopy for z/os supports both SMS- and non-sms-managed data, is completely applicationindependent, and is designed to run unattended. For distances within the same metropolitan area, TrueCopy Synchronous software provides a no-data-loss, rapid-restart solution. And for enterprise environments, TrueCopy Synchronous software, combined with Universal Replicator and the Universal Storage Platform V, allows for advanced threedata-center configurations for optimal data protection. TrueCopy Asynchronous software can also be deployed for wide-area disaster protection across virtually any distance. TrueCopy Asynchronous software uses a unique method of sequence numbers and timestamps in each data record to ensure proper sequencing and data integrity during transmission and recovery. This document describes and provides instructions for performing TrueCopy for z/os operations on the Universal Storage Platform V using the TrueCopy for z/os software on Storage Navigator. The licensed TrueCopy for z/os software displays the TrueCopy for z/os information and allows you to perform TrueCopy for z/os operations. For further information on Storage Navigator, please refer to the Storage Navigator User s Guide (MK-96RD621). Hitachi TrueCopy for z/os operations can also be performed from the mainframe host using IBM PPRC commands. 1-2 Overview of Hitachi TrueCopy for z/os

19 Feature Highlights The key features of TrueCopy include: Hitachi TrueCopy software does not require a server or server overhead to complete its operations, and is application- and operating systemsindependent. TrueCopy Remote Replication Synchronous software yields the highest degree of data integrity because its real-time copies are the same as the originals. TrueCopy Asynchronous software delivers premier data integrity with minimal performance impact on the primary system: Able to operate at any distance, TrueCopy software supports fast restarts and recovery by ensuring proper database update sequences for each transaction during transmission between enterprise storage systems. Overview of Hitachi for z/os 1-3

20 Business Benefits Hitachi TrueCopy provides the following business benefits: Supports your business continuity and disaster recovery efforts and plans. Provides distance replication while maintaining application and data integrity. Improves business resilience by enabling frequent, nondisruptive disaster recovery testing with an online copy of current and accurate production data. Improves service levels by reducing planned and unplanned downtime of customer-facing applications. 1-4 Overview of Hitachi TrueCopy for z/os

21 Applications of TrueCopy Synchronous and TrueCopy Asynchronous TrueCopy provides a storage-based hardware solution for disaster recovery which enables fast and accurate system recovery. Once TrueCopy operations are established, duplicate copies of data are automatically maintained for backup and disaster recovery purposes. During normal TrueCopy operations, the primary volumes remain online to all hosts and continue to process both read and write I/O operations. In the event of a disaster or system failure, the secondary copy of data can be rapidly invoked to allow recovery with a very high level of data integrity. TrueCopy can also be used for data duplication and migration tasks. TrueCopy Synchronous provides volume-based real-time data backup and is ideal for high-priority data backup, duplication, and migration tasks. In the event of a disaster or system failure at the primary site, the secondary TrueCopy Synchronous data can be rapidly invoked to allow recovery at the volume level with an extremely high level of data integrity. TrueCopy Asynchronous represents a unique and outstanding disaster recovery solution for large amounts of data which span multiple volumes. The TrueCopy Asynchronous group-based update sequence consistency solution enables fast and accurate database recovery, even after a rolling disaster, without the need for time-consuming data recovery procedures. The TrueCopy Asynchronous volume groups at the remote site can be recovered with full update sequence consistency, but the updates will be behind the primary site due to the asynchronous remote copy operations. TrueCopy Asynchronous provides update sequence consistency for userdefined groups of volumes (e.g., large databases) as well as protection for write-dependent applications in the event of a disaster. Overview of Hitachi for z/os 1-5

22 1-6 Overview of Hitachi TrueCopy for z/os

23 2 About TrueCopy for z/os Operations This chapter describes TrueCopy for z/os operations. Components Operations Asynchronous recordset operations Asynchronous consistency group operations Pair status and suspend types Business Continuity Manager support PPRC support, including P/DAS and GDPS (CGROUP) operations About TrueCopy for z/os Operations 2-1

24 TrueCopy for z/os Components TrueCopy for z/os operations involve the USP V at the main and remote sites, the physical communications paths between the main and remote storage systems, and the USP V TrueCopy software. TCz copies the original online data at the main site to the offline backup volumes at the remote site via the dedicated fibre-channel remote copy connections. The TrueCopy for z/os software is included in the Storage Navigator Java application, and all TrueCopy for z/os functions and operations can be performed from within a web browser. The I/O time-stamping host software function (provided by MVS DFSMSdfp) is required for TCzA consistency groups which span multiple storage systems. Error reporting communications (ERC) is required for effective disaster recovery with TCz. Figure 2-1 shows the TrueCopy for z/os components and their functions. USP V Note: The additional Shared Memory option is required for TrueCopy operations. Main and remote control units (MCUs and RCUs) TagmaStore USP/NSC and Lightning 9900V can also be used as RCUs with some restriction. Pairs (local M-VOLs and remote R-VOLs) TrueCopy for z/os Async consistency groups Host I/O time-stamping function Remote copy connections Ordinary target ports, initiator ports, and RCU target ports for fibre-channel interface TrueCopy for z/os software Error reporting communications 2-2 About TrueCopy for z/os Operations

25 Host Processor(Primary) PPRC Support (MVS) Time-Stamping Function Error Reporting Communications Host Processor(Secondary) PPRC Support (MVS) Time-Stamping Function Fibre Remote Copy Connections Target Initiator Disk Subsystem (MCU) TCz Volume Pair RCU Target Target Disk Subsystem (RCU) SVP M-VOL M-VOL M-VOL M-VOL Copy Direction R-VOL R-VOL R-VOL R-VOL SVP Ethernet (TCP/IP) TCz Async Consistency Group Storage Navigator PC Storage Navigator PC Figure 2-1 TrueCopy for z/os Components for Fibre-Channel Connection About TrueCopy for z/os Operations 2-3

26 USP V TrueCopy for z/os operations involve the main (primary) storage systems and the remote (secondary) storage systems. This document covers TCz operations in which the main storage system is a USP V and the remote storage system is a USP V (or TagmaStore USP/NSC) storage system. The main storage systems contain the TCz main volumes (M-VOLs), which contain the original data and are online to the host(s). The remote storage systems contain the TCz secondary volumes (R-VOLs), which are the synchronous or asynchronous copies of the M-VOLs. TCz supports all CUs, volumes, and physical hard drive options for the USP V. TCz supports RAID 1, RAID 5 and RAID6 configurations. All USP Vs with TCz installed are compatible with the IBM PPRC host software function. Note: The additional Shared Memory option is required for TrueCopy operations. Table 2-1 RAID Level Configurations of TrueCopy for z/os RAID Level of M-VOL RAID Level of R-VOL RAID1 RAID5 RAID6 RAID1 Supported Supported Supported RAID5 Supported Supported Supported RAID6 Supported Supported Supported To provide greater flexibility and to enable USP V to be tailored to unique customer operating requirements, additional operational parameters, or optional modes, are available for the USP V. At installation, the USP V modes are set to their default values, so make sure to discuss these settings with your Hitachi team. The USP V modes can only be changed by your Hitachi representative. Table 2-2 shows the USP V modes related to TCz and PPRC operations. Note: This mode information was current at the time of publication of this document, but it may change. Please contact your Hitachi representative for the latest USP V system option mode information. Note: The USP V performing TCzA operations (main and remote) utilize sidefiles in cache for storing the TCzA recordsets. Concurrent Copy (CC) also utilizes cache sidefiles. Storage systems performing TCzA and/or CC must have sufficient cache installed to handle the increased sidefile usage. Insufficient cache can degrade storage system I/O performance and cause command retry requests and state-change-pending (SCP) messages. See Inflow Control of Recordsets for further information on cache usage and sidefile thresholds. 2-4 About TrueCopy for z/os Operations

27 Table 2-2 USP V Modes for TrueCopy for z/os (continues on the next page) Mode Description 20 Enables TCz R-VOL read-only function (RCU only). 36 TCz Synchronous Selects function of CRIT=Y(ALL) or CRIT=Y(PATHS). Mode 36 ON: CRIT=Y(ALL) => equivalent to Fence Level = Data. Mode 36 OFF: CRIT=Y(PATHS) => equivalent to Fence Level = Status. 93 Graduated delay process for sidefile control: Mode 93 OFF (default) = strong delay type Mode 93 ON = soft delay type Amount of sidefile Strong delay type Soft delay type threshold [15-20%] (HWM) 100 ms 1 time 20 ms 1 time threshold [10-15%] 200 ms 1 time 40 ms 1 time threshold [5-10%] 300 ms 1 time 60 ms 1 time threshold [0-5%] 400 ms 1 time 80 ms 1 time threshold or higher 500 ms permanent 100 ms permanent 104 TCz CGROUP Selects storage system default for CGROUP FREEZE option. Applies to 3990 emulation only. Note: Mode 104 is invalid if the controller emulation is 2105 or For 2105 or 2107, use the CGROUP option of CESTPATH. Mode 104 ON: FREEZE enabled. Mode 104 OFF (default): FREEZE disabled. 114 TCz Allows dynamic port mode setting (Initiator/RCU target for fibre-channel) through PPRC CESTPATH and CDELPATH commands. Mode 114 ON: Initiator ports will automatically change to RCU target ports. or vice versa. Mode 114 OFF (default): Initiator ports will not automatically change to RCU target ports, nor vice versa. Note: 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. The fibre-channel interface ports need to be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued. Note: Even if you set ON for system option mode 114, initiator ports will not automatically change to RCU target ports, nor vice versa, when these ports are in initiator/external mix mode. Caution: Before issuing the CESTPATH command, you must make sure that the relevant paths are offline from the host(s) (e.g., configure the Chipid offline, or deactivate the LPAR, or block the port in the ESCD). If any active logical paths still exist, the add path operation will fail because the port mode cannot be changed. 118 TCzA Allows you to select whether to generate SIM when the sidefile of TCzA and CC reaches high-water mark (HWM = sidefile threshold - 20%. See mode 93). This mode takes effect on the volume to which the inflow control is set. Mode 118 ON: Generate SIM. Mode 118 OFF (default): No SIM generated. Note: The reported SIM when this mode is ON is reported per CLPR. 190 TCz 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. 308 Allows you to select whether the Remote Copy Path status, SIM218x, will be reported to the host or not. Mode 308 ON: SIM218x will be reported to the host. Mode 308 OFF: SIM218x will not be reported to the host. About TrueCopy for z/os Operations 2-5

28 Table 2-2 Mode USP V Modes for TrueCopy for z/os (continued) Description 464 TCzA Allows you to select whether to generate SIM when the sidefile of TCzA and CC reaches high-water mark (HWM = sidefile threshold - 20%. See mode 93). This mode takes effect on the volume to which the inflow control is not set. Mode 464 ON: Generate SIM. Mode 464 OFF: No SIM generated. The SIM generated according to Mode 464 ON is same as Mode 118 ON. If both Mode 464 and Mode 118 are ON, the SIM will be generated for the volume that was detected to have reached high-water mark earlier. Note: The reported SIM when this mode is ON is reported per CLPR. 484 Allows you to select the indication type if you use the PPRC CQUERY command to display the remote copy path status. Mode 484 ON: The status of path as using the fibre channel interface will be displayed. WWNN will be indicated. Mode 484 OFF: The status of path as using an ESCON interface will be displayed. WWNN is invalid. Note: If the former type storage system or the storage system of TagmaStore USP/NSC microcode version XX- XX or earlier is connected, mode 484 must be OFF. 2-6 About TrueCopy for z/os Operations

29 Control Units (MCUs and RCUs) The main control unit (MCU) and remote control unit (RCU) control TCz operations: The MCU is the control unit (CU) in the main storage system which controls the M-VOLs of the TCz pairs. The Storage Navigator computer must be LANattached to the MCU of each TCz pair. The MCU communicates with the RCU via the dedicated remote copy connections. The MCU controls the host I/O operations to the TCz M-VOLs as well as the TCz initial copy and remote copy operations between the M-VOLs and R-VOLs. The MCU also manages the TCz pair status and configuration information. The RCU is the CU in the remote storage system which controls the R-VOLs of the TCz pairs. The RCU assists in managing the TCz pair status and configuration (e.g., rejects write I/Os to TCz R-VOLs). The RCU executes the remote copy operations issued by the MCU. The secondary Storage Navigator computer should be attached to the RCUs at the remote site on a separate LAN. The RCUs should also be attached to a host system to allow sense information to be reported in case of a problem with a secondary volume or remote storage system and to provide disaster recovery capabilities. The MCU and RCU can be defined separately for each TCz pair. The USP V CU can function simultaneously as an MCU for one or more M-VOLs and as an RCU for one or more R-VOLs, provided the remote copy connections and ports are properly configured. The USP V provides two logical disk controllers (LDKC). Each LDKC provides up to 255 logical CUs (00-FE), with each CU controlling up to 256 logical devices (LDEVs). TCz operations can be performed on all logical devices (LDEVs) without the command device for Business Continuity Manager in all logical CUs. The TCz software allows you to select the desired CU in the connected MCU and specify the desired CU in the RCU. For detailed information about the command device for Business Continuity Manager, please refer to the user documentation for Business Continuity Manager. Note: This document provides instructions for performing TCz operations with the USP V as the MCUs. If you are using non-usp V models as MCUs, please refer to the TrueCopy for z/os User and Reference Guide for the storage system. Other Hitachi RAID storage systems can be used as RCUs connected to the USP V MCU for TCz Synchronous and/or Asynchronous operations. Caution: If you are creating a TCz pair with different series of storage systems (e.g., USP V and TagmaStore USP), make sure that each storage system 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 storage systems with the same serial number and you need to configure remote copy pairs between the two storage systems, please contact your Hitachi account team for assistance. About TrueCopy for z/os Operations 2-7

30 Pairs (M-VOLs and R-VOLs) TrueCopy for z/os performs remote copy operations for pairs established by the user. Each TCz pair consists of one main volume (M-VOL) and one remote volume (R-VOL) which are located in different storage systems. The TCz M- VOLs are the primary volumes which contain the original data, and the TCz R- VOLs are the secondary or mirrored volumes which contain the backup or duplicate data. The main and remote volumes must have the same format and capacity. During normal TCz operations, the M-VOL remains available to all hosts at all times for read and write I/O operations. The RCU rejects all I/Os to an R-VOL. The R-VOL read option allows read-only access to a TCz R-VOL while the pair is suspended. TrueCopy for z/os supports a maximum of 32,768 pairs (entire USP V RCU). If the command device for Business Continuity Manager is defined, the TCz pair can be created up to 32,767 pairs. TCz supports the basic logical volume images (LVIs) available on the USP V (e.g., , R, ). Caution: Do not use M-VOLs or R-VOLs from hosts that have different CU emulation types (2105 or 2107, and 3990) at the same time. If you use the M- VOLs or R-VOLs from the 2105 or 2107, and 3990 hosts simultaneously, an MIH message might be reported to the 3990 host. 2-8 About TrueCopy for z/os Operations

31 Remote Copy Connections The remote copy connections are the physical paths used by the TrueCopy for z/os MCUs to communicate with the TCz RCUs. The maximum number of physical paths per logical CU is eight for fibre-channel. The MCUs and RCUs are connected via fibre-channel interface cables. When fibre-channel interface (single-mode longwave) connections are used, two switches are required for distances greater than 10 km (6.2 miles), and distances up to 30 km (18.6 miles) are supported. Long-distance solutions are provided, based on user requirements and workload characteristics, using approved channel extenders and communication lines (e.g., T1/T3/ATM). The MCU-to-RCU remote copy configuration for TCz Asynchronous has different requirements than the TCz Synchronous configuration, as follows: TrueCopy for z/os Sync supports 1-to-n and n-to-1 remote copy connections (n 4). One MCU can be connected to as many as four RCUs, and one RCU can be connected to as many as four MCUs (one MCU/RCU = one physical CU, including all CUs). TCz supports the dynamic switching capability of the ESCDs which is used to share the physical interface cables between the components. The ESCDs can accommodate channel-to-mcu and channel-to- RCU connections in addition to the remote copy connections. TrueCopy for z/os Async supports 1-to-1 remote copy connections within the same consistency group. The M-VOLs and R-VOLs of the pairs in a consistency group must be located within one physical MCU and one physical RCU. This configuration ensures backup integrity for data which is spread across multiple volumes within one USP V (e.g., large databases). Note: TrueCopy 1-to-n and n-to-1 configurations are valid for TrueCopy for z/os Async, as long as each consistency group does not span local or remote storage systems. Fibre remote copy supports 1-to-1 remote copy connections. One USP V as an MCU can be connected to only one USP V as an RCU via optical fibre cables. For the CUs within one USP V, 1-to-4 and 4-to-1 remote copy connections are supported. One MCU port (initiator port) can be connected to 64 RCU ports (RCU target ports). One RCU port can be connected to 16 MCU ports. However, the number of logical paths that can be specified does not depend on the number of connectable RCU or MCU ports. Note: Hitachi strongly recommends that you establish at least two independent remote copy connections (one per cluster) between each MCU and RCU to provide hardware redundancy for this critical communications path. About TrueCopy for z/os Operations 2-9

32 TrueCopy for z/os with FICON : For USP Vs with both TCz and FICON host attachment, you must set the path configuration carefully. Table 2-3 lists the possible path configurations and indicates which combinations are supported. Table 2-3 TrueCopy for z/os Configuration with FICON Host Interface Channel MCU MCU RCU Supported? ESCON ESCON No ESCON Fibre-channel Yes FICON ESCON No * FICON Fibre-channel Yes * Note: The configuration of FICON for channel-mcu paths and ESCON for MCU-RCU paths is not supported, because the bandwidth of FICON is greater than that of ESCON interface. If FICON is used for channel-mcu paths, use fibre-channel interface for the MCU-RCU paths About TrueCopy for z/os Operations

33 Initiator Ports and RCU Target Ports The initiator ports are the dedicated fibre-channel interface ports on the main storage system (MCU) to which the RCUs (RCU target ports) are connected. The initiator ports connect to the RCUs to send write I/O operations directly to the RCUs. Any fibre-channel interface port of the USP V can be configured as an initiator port. The TrueCopy for z/os software allows you to change the configuration of the USP V fibre-channel ports (ordinary target port, initiator port, or RCU target port) as needed. The RCU target ports are the dedicated fibre-channel interface ports on the remote storage system (RCU) to which the MCU (initiator ports) are connected. Any fibre-channel interface port of the USP V can be configured as an RCU target port. The RCU target ports can be connected to the host channel paths via the fibre-channel switch. To fully support an automated environment, the USP V automatically configures a fibre-channel port as an initiator or RCU target if required in response to the TSO CESTPATH and CDELPATH commands. See system option mode 114 in Table 2-2. Note: 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. Note: Two or more initiator ports must be configured before you can add the RCUs and create the TCz pairs. The initiator ports cannot communicate with the host processor channels. To enable the host processor channels to send write I/O operations to the MCU, the host channel paths must be connected to the other fibre-channel interface ports in the MCU. Ordinary fibre-channel interface ports cannot be connected to the MCU. These ports (usually called target ports) can be connected to the host processor channels only. About TrueCopy for z/os Operations 2-11

34 USP V TrueCopy Software The USP V program product includes TrueCopy for z/os and TrueCopy. The USP V Storage Navigator software communicates with the SVP of the USP V via defined TCP/IP connections. For further information on USP V Storage Navigator's operations, please refer to the Storage Navigator User's Guide (MK-96RD621), or contact your Hitachi account team. If you plan to use PPRC to perform TCzA operations, you must use the TrueCopy for z/os software to add the consistency groups and select the desired group options and async options before you can add any TCzA pairs. These functions can only be performed using the USP V Storage Navigator software (or SVP*). Once the groups and async options have been configured, PPRC commands can be used to establish and manage TCzA pairs. If you will be using the USP V Storage Navigator software to perform TrueCopy for z/os operations (instead of PPRC), the MCU of each TrueCopy for z/os pair must be LAN-attached to the USP V Storage Navigator computer. You should also attach all RCUs to a USP V Storage Navigator computer on a separate LAN at the remote site. Having a separate LAN at the remote site enables you to access the RCUs and TrueCopy for z/os R-VOLs and perform TrueCopy for z/os operations at the remote site in the event that the main site is not available (e.g., due to disaster). If you need to perform TrueCopy for z/os operations in the reverse direction from the remote site to the primary site (e.g., disaster recovery), the TrueCopy for z/os software at the remote site simplifies and expedites this process. *Note: For information on TrueCopy for z/os Async configuration services, please contact your Hitachi account team About TrueCopy for z/os Operations

35 Asynchronous Consistency Groups A TrueCopy for z/os Async consistency group is a user-defined set of pairs across which update sequence consistency is maintained and ensured at the remote site. Each TCzA pair must be assigned to a consistency group. TCzA allows you to configure up to 128 consistency groups (00-7F) for each MCU and provides group-based operations for consistency groups (e.g., suspend and resynchronize group). Consistency groups enable you to maintain update sequence consistency for databases which span multiple volumes, allowing immediate database recovery at the remote site when needed. Host I/O Time-Stamping Function If you plan to establish TCzA consistency groups, the I/O time-stamping function must be installed on the host processor at the main (primary) site. The I/O time-stamp, which is provided by MVS DFSMSdfp, is the same timestamp that is used by IBM XRC pairs. The RCU requires the I/O time-stamp information to process TCzA recordsets. The I/O time-stamping function should also be installed on the host processor at the remote (secondary) site, so that time-stamps can be used when copying data in the reverse direction. Note: If the main and/or remote system consists of several CPU complexes, a SYSPLEX timer is required to provide a common time reference for the I/O time-stamping function. Error Reporting Communications Error reporting communications (ERC), which transfers information between host processors at the main and remote sites, is a critical component of any disaster recovery effort. You can configure ERC using channel-to-channel communications, NetView technology, or other interconnect technologies, depending on your installation requirements and standards. Neither TCz nor the TrueCopy for z/os software provides ERC between the main and remote sites. When TCz is used as a data migration tool, ERC is recommended but is not required. When TCz is used as a disaster recovery tool, ERC is required to ensure effective disaster recovery operations. When a TCz pair is suspended due to an error condition, the MCU generates sense information which results in an IEA491E system console message. This information should be transferred to the remote site via the ERC for effective disaster detection and recovery. About TrueCopy for z/os Operations 2-13

36 Remote Copy Operations Figure 2-2 illustrates the two types of TrueCopy for z/os remote copy operations: initial copy and update copy. To reduce the overhead associated with these remote copy activities and maximize data transfer, the USP V utilizes a special write command which is allowed only for TCz initial and update copy operations. This command transfers the control parameters and the FBA-format data for consecutive updated records in a track using a single write operation. Host Processor at Main Site Disk Subsystem (MCU) Disk Subsystem (RCU) Write I/O M-VOL Initial Copy Update Copy R-VOL Figure 2-2 TrueCopy for z/os Remote Copy Operations This section describes the following aspects of TrueCopy for z/os remote copy operations: Initial copy operations Update copy operations Read and Write I/O Operations for TrueCopy Volumes S-VOL Write Option 2-14 About TrueCopy for z/os Operations

37 Initial Copy Operation The initial copy operation synchronizes the M-VOL and R-VOL independently of host I/O processes. The initial copy operation is the same for TCz Synchronous and Asynchronous pairs. A TCz initial copy operation takes place when you add a new pair or resynchronize a suspended pair. When a new pair is established, the entire contents of the M-VOL are copied to the R-VOL by track, including the VTOC (volume table of contents) but not including the diagnostic and unassigned alternate tracks. If None is selected, the user is responsible for ensuring that the M-VOL and R-VOL are already identical. The MCU cannot verify the contents of the volumes. When a suspended pair is resynchronized, only the VOLSER and out-of-sync tracks (updated by write I/Os while the pair was suspended) are copied to the R-VOL. For additional flexibility, TCz provides the following options for the initial copy operation: The number of tracks option allows you to specify how many tracks are copied simultaneously by the TCz initial copy operation when adding/resynchronizing a TCz pair. This option can be specified using the TCz software and the CESTPAIR TSO command (PACE parameter). The Initial Copy Priority option allows you to specify the order in which the initial copy operations are performed when adding/resynchronizing multiple TCz pairs. This option can only be specified using the TCz software (not PPRC). The Maximum Initial Copy Activities option allows you to specify the maximum number of concurrent initial copy operations that each MCU can perform (not pair-specific). This option can only be specified using the TCz software (not PPRC). About TrueCopy for z/os Operations 2-15

38 Update Copy Operation A TrueCopy for z/os update copy operation occurs when the host issues a write I/O operation to the M-VOL of a TCz pair. The update copy operation duplicates the M-VOL write I/O at the R-VOL to keep the M-VOL and R-VOL synchronized. TCz provides two modes for update copy operations: synchronous and asynchronous. The update copy mode is specified when you add a TCz pair and cannot be changed. TCz also allows you to specify whether the cache-fast-write (CFW) data is included in the update copy operations. For synchronous update copy mode, the MCU ensures that the M-VOL and R- VOL are synchronized at all times. The MCU does not return device-end status for the M-VOL write I/O until both the M-VOL write and its associated update copy operation at the RCU are complete. For synchronous mode, the MCU starts the update copy operation when it receives: the last write command in the current domain, specified by the preceding locate record command, or a write command which requires switching to the next track, or a write command which was not preceded by a locate record command. Note: If many consecutive records are updated by a single CCW chain which does not use the locate record command (e.g., long sequential chained write operations), storage system performance may be significantly impacted. For asynchronous update copy mode, the MCU stores the M-VOL updates along with additional control information in cache, and sends the updates and control information to the RCU completely independent of the host I/O processes. These updates with their associated control information are called TCzA recordsets. The RCU stores the TCzA recordsets in cache and performs the updates to the R-VOLs in the same order as they were performed at the MCU(s) according to the TCzA time-stamp and sequence information. Priority of initial and update copy: In both TrueCopy for z/os Sync and Async, update copy has higher priority than initial copy. However, initial copy is executed based on the copy pace (3 or 15 tracks); therefore, update copy must wait this interval if initial copy is being executed. For example, if the copy pace is 15 tracks, the update copy may wait up to 15 tracks (1 cylinder). In the case of TrueCopy for z/os Async, update copy is executed asynchronously, but the same scheduling conflict can occur between the asynchronous update copy (write recordset) and initial copy About TrueCopy for z/os Operations

39 Read and Write I/O Operations for TrueCopy for z/os Volumes When an MCU receives a read command for a TrueCopy for z/os M-VOL, the MCU completes the read from either cache or the M-VOL. If the read fails, the redundancy provided by RAID technology recovers the failure. The MCU does not read the TCz R-VOL for recovery. When an MCU receives a write command for a TCz Synchronous M-VOL with pending duplex status (and the track has already been copied to the R-VOL), the MCU performs a synchronous update copy operation to complete the write at the R-VOL. When an MCU receives a write command for a pending duplex TCzA M-VOL (and the track has already been copied to the R-VOL), the MCU performs an asynchronous update copy operation. When an MCU receives a write command for an M-VOL with duplex status, the user-selected update copy mode of the pair (synchronous or asynchronous) determines the sequence of events: Synchronous Mode: The MCU performs the write operation on the M-VOL, reports channel-end status to the host, starts the update copy operation for the R-VOL, and then reports device-end status to the host only after the update copy operation is complete. If the M-VOL write or R-VOL update copy operation fails, the MCU reports a unit check, and the host system and application program will regard that write operation to the M-VOL as failed. If a failure occurs at the M-VOL or the R-VOL, the corresponding volume of the TCz pair will decommit the update to maintain exact synchronization of the volumes. Asynchronous Mode: The MCU completes M-VOL write operations independently of the associated update copy operations at the R-VOL. The RCU manages the R-VOL updates according to the TCzA recordset information and maintains time-based data consistency for the R-VOLs. If the M-VOL write operation fails, the MCU reports a unit check and does not create the TCzA recordset for this operation. If the update copy operation fails, the RCU suspends either the affected pair or all TCzA pairs in the consistency group, depending on the type of failure. When the suspended TCzA pair or group is resynchronized, the MCU and RCU negotiate the resynchronization of the pair(s). The RCU does not allow a TCz R-VOL to be online and rejects all hostrequested read and write I/O operations for a TCz R-VOL. The TCz R-VOLs must be offline during normal TCz operations. Note: TrueCopy for z/os provides a special R-VOL read option which allows read-only access to the R-VOL while the pair is suspended. If you need write access to a TCz R-VOL, you must release the pair. About TrueCopy for z/os Operations 2-17

40 R-VOL Read Option For additional flexibility, TrueCopy for z/os offers a special R-VOL read option. The Hitachi representative enables the R-VOL read option on the RCU (mode 20). The R-VOL read option allows you to read a TCz R-VOL only while the pair is suspended, that is, without having to release the pair. Note: When you read a TCz R-VOL from a host, the reference date in the VTOC is updated. In this case, you must permit to update the VTOC. The RCU will allow you to change only the VOLSER of the suspended R-VOL, so that the R-VOL can be online to the same host as the M-VOL while the pair is suspended. All other write I/Os will be rejected by the RCU. The MCU copies the M-VOL VOLSER back onto the R-VOL when the pair is resynchronized. If mode 20 and mode 190 is enabled simultaneously, the Hitachi representative permits to only update the VOLSER and VTOC of the TCz R-VOL from a host while a pair is suspended. The MCU copies the M-VOL VOLSER and VTOC back onto the R-VOL when the pair is resynchronized. When the R-VOL read option is not enabled and/or the pair is not suspended, the RCU rejects all read and write I/Os to a TCz R-VOL. Note: If you need write access to an R-VOL, you must release the pair. Note: For 2105 or 2107 controller emulation, the CSUSPEND command to the R-VOL of a suspended TCz pair will be rejected when the TCz R-VOL read option is used About TrueCopy for z/os Operations

41 TrueCopy for z/os Async Recordset Operations The TCzA recordsets contain the TCzA M-VOL updates and the associated control information, including the time-stamp of the M-VOL update, which enables the RCU to maintain update consistency of the TCzA R-VOLs. TCzA recordset operations include: Creating and storing recordsets at the MCU Sending recordsets to the RCU Storing recordsets at the RCU Selecting and settling recordsets at the RCU Types of recordsets Inflow control for sidefiles. Creating and Storing Recordsets at the MCU When an MCU performs an update (host-requested write I/O) on a TCzA M- VOL, the MCU creates a TCzA recordset which contains: the updated record, time-stamp information, sequence number, record location (device, cylinder, track, record number), and record length. The TCzA recordsets are queued in the cache storage of the MCU and sent to the RCU independent of host I/O processes. The RCU utilizes the time-stamp and sequence number information in the recordsets to update the R-VOL(s) in the same order as the M-VOL(s). The time-stamp information is acquired from the (MVS) host s I/O time-stamp function. This time stamp provides a protective measure for write-dependent applications and minimizes recovery time in the event of a disaster. The sequence number indicates the number of recordsets that the MCU has created for each consistency group. The recordset information, except for the updated records, is stored and queued in an area of cache known as sidefile cache. About TrueCopy for z/os Operations 2-19

42 Sending Recordsets to the RCU The MCU sends the TCzA recordsets to the RCU in a similar manner to the TCz Synchronous updates. The MCU s initiator ports act as host processor channels and issue special I/O operations, called remote I/Os (RIOs), to the RCU. The RIO transfers the recordsets in FBA format (not CKD) using a single channel command, eliminating the overhead associated with FBA-CKD conversion and thus providing more efficient transfer of user data. The MCU can send several recordsets using a single RIO, even if their sequence numbers are not contiguous. Therefore, TCzA recordsets are usually sent to the RCU in a different order than the arrivals at the MCU. The RCU ensures that records are applied to the R-VOLs in the correct sequence. This method of remote I/O provides the most efficient use of MCU-to-RCU link resources. Note: The parameter length and detailed specification of this TCzA channel command are different than for TCz Synchronous RIOs. You must make sure that your channel extenders are capable of supporting this command. For further details, please contact your Hitachi account team. Storing Recordsets at the RCU The RCU maintains queues to control the storing of recordsets in the sidefile and commitment of updating records in the R-VOLs. The RCU queuing mechanism uses time-stamping to control the sequence in which R-VOL updates are applied, and uses sequence numbers provided by the MCU to check for any missing updates. Note: The MCU does not remove the sidefile entry for a recordset from its cache until it receives an I/O completion signal (device end) from the RCU. This is true even if the MCU and RCU are connected via a channel extender product. If a recordset is lost in transmission from the MCU to the RCU, the MCU s differential data ensures that the missing recordset is identified and resent to the RCU About TrueCopy for z/os Operations

43 Selecting and Settling Recordsets at the RCU The RCU selects the recordset to be promoted to formal data (or settled ) as follows: 1. The RCU checks for a valid entry at the top of each queue in the consistency group. If the top of any queue is empty (i.e., recordset not yet received), the RCU waits for that entry. 2. When the top of each queue contains a valid entry (recordset), the RCU selects the entry which has the earliest time-stamp value, and then settles this recordset. 3. The RCU repeats steps (1) and (2) to select and settle TCzA recordsets. Figure 2-3 (next page) illustrates recordset selection and settling at the RCU. In this example, the top of the queue contains a valid entry: S1/T1. The RCU selects recordset S1/T1 to be settled, because T1 is the earliest time-stamp. When S1/T1 is removed from the MCU queue, recordset S2 becomes the top entry, but it is empty. When recordset S2 arrives (and its time-stamp is later than T1 and earlier than T3), the RCU selects S2/T2 as the next recordset to be settled. The recordset selected by the RCU is marked as host-dirty and treated as formal data. The time-stamp value of that recordset is promoted to the consistency time (C/T) of the group. The RCU settles the updated records in the recordset as follows: If the corresponding track is in cache (track-hit), the updated records in the recordset are copied to the existing cached track, and the cache space for the sidefile is released. If the corresponding track is not in cache (track-miss), the RCU changes the cache designation of the sidefile to formal data. The data is not physically moved. About TrueCopy for z/os Operations 2-21

44 Types of Recordsets In addition to host update recordsets, the MCU passes control information to the RCU in special non-update recordsets. These special recordsets indicate when pair status changes and when an MCU power-off sequence is initiated, and also maintain sequence numbers in periods of low host activities. Receiving Recordsets Grp=n S4/T4 S3/T3 S2* S1/T1 Selecting Recordset Si = sequence number which shows the order that write I/Os are received from MCU (S2 = S1+1, S3 = S2+1, S4 = S3+1). Ti = time stamp which shows the time of receiving write I/O from MCU (T1 < T2 < T3 < T4). S1/T1 Settling Recordset Consistency Time T1 Data Grp=n Formal Data * Since the recordset has not yet arrived at RCU, S2 does not have a time stamp now. Figure 2-3 Selecting and Settling TrueCopy for z/os Async Recordsets at the RCU 2-22 About TrueCopy for z/os Operations

45 Inflow Control of Recordsets As described in the previous sections, both the MCU and RCU create sidefiles for storing TCzA recordsets. Since the sidefiles occupy exclusive space in cache, both the MCU and RCU perform inflow control to prevent an overload of the storage system s cache resources. The USP V uses the following parameters for TCzA cache inflow control: Sidefile Threshold = maximum cache % available for use by TCzA sidefiles. Table 2-4 shows the TCzA sidefile threshold values and describes the actions that occur when each threshold is reached. The high-water mark (HWM), which is the sidefile threshold minus 20%, indicates when graduated delay begins for TCzA pairs (see next section). If system option mode 118 is ON, a warning SIM is also generated. The puncture threshold, which is the sidefile threshold plus 10%, indicates when the TCzA pairs will be suspended due to sidefile overflow. Inflow control by MCU: When the amount of MCU sidefile cache reaches the HWM, the MCU responds to update I/Os from the host with state-change-pending (SCP) or channel-command-retry requests and begins graduated delay. Inflow control by RCU: When the amount of RCU sidefile cache reaches the HWM, the RCU responds with channel-command-retry requests to the RIO commands which transfer the recordsets from the MCU. The only recordset accepted by the RCU is the recordset with the sequence number required to continue settling pending recordsets. Offloading Timer = maximum time between TCzA recordset transfers. Inflow control by MCU: If the MCU is not able to send a recordset to the RCU within the user-specified offloading timer value, the MCU suspends all TCzA pairs and resets the SCP condition to avoid hanging up the system. Inflow control by RCU: If the RCU is not able to settle a recordset within the user-specified offloading timer value, the RCU suspends all TCzA pairs and resets the channel-command-retry condition to avoid hanging up the MCU. Concurrent Copy (CC). CC operations utilize a different cache sidefile than TCzA. Table 2-4 also shows the sidefile threshold values for CC operations and describes the actions that occur when each threshold is reached. Storage systems performing TCzA in combination with CC must have sufficient cache installed to handle the increased sidefile activity. If a sidefile puncture condition occurs (CC sidefiles reach 10% over threshold), the CC session having the highest sidefile usage is terminated. Important: SIM reporting for sidefile conditions is disabled when mode 118 is OFF (Table 2-2). About TrueCopy for z/os Operations 2-23

46 Note: Cache Residency Manager operations may decrease the total amount of cache available for TCzA and CC operations but do not directly affect sidefile cache usage. Available cache is defined as the amount of physical cache memory installed on the storage system minus any cache reserved for the Cache Residency Manager feature About TrueCopy for z/os Operations

47 Table 2-4 Sidefile Thresholds Operation Threshold(s) Action(s) TCzA High-water mark (HWM) = sidefile threshold 20% Sidefile threshold = 30-70% of cache, default = 50%. TCzA threshold can be adjusted from 30-70% (in 10% increments) using the TCz software. Puncture threshold = sidefile threshold + 10% CC [CC sidefile] / [avail cache] = 40%, 50%, 60% CC thresholds can be adjusted by using modes 85 and 86 (see Table 2-2). Threshold 1/2/3 = 30/40/50%, 40/50/60%, or 60/70/80% Write Pending [write pending] / [avail cache - sidefile] = 70% MCU (RCU) reaches HWM: command retry to host (MCU), begin graduated delay. Delay times can be adjusted using mode 93 (see Table 2-2). MCU (RCU) reaches threshold: command retry to host (MCU), max delay time (500 or 100 ms). Delay time can be adjusted using mode 93 (see Table 2-2). MCU (RCU) reaches puncture: suspend affected TCzA pairs due to sidefile overflow condition. Threshold 1 = no action. Threshold 2 = SCP message. Threshold 3 = puncture condition. Command retry. About TrueCopy for z/os Operations 2-25

48 Graduated Delay Sidefile Management Figure 2-4 shows the graduated delay process for TrueCopy for z/os sidefile management. When the sidefile value reaches the high-water mark (threshold minus 20%), the USP V begins command retry delay for host updates to TCz M-VOLs and reports a warning SIM to the host. As the amount of sidefile increases, the delay increases incrementally as shown in Figure 2-4. Mode 93 on the USP V SVP (refer to Table 2-2) allows you to select the delay type (long or short). This graduated delay methodology minimizes the potential for sidefile overcommitment, while at the same time providing another level of automation control. Note: If there is a network problem, lack of bandwidth, or lack of sufficient Fibre links, the sidefile will grow and the microcode will add delay to host I/O until the sidefile goes below a certain level again. Disabling this function will cause the pairs to suspend. Important: SIM reporting for sidefile conditions is enabled only when system option mode 118 or 464 is ON (refer to Table 2-2). The reported SIM(s) when system option mode 118 or 464 is ON, however, do not support a CLPR. When this SIM is reported to the host, the SIM reference code is indicated as 490xyy ("x" is CU number, and "yy" is LDEV number). For further information on the SIM reference code, please call the Hitachi Support Center. You can disable the command retry delay for a limited number of critical volumes using the special No delay parameter for the CESTPAIR TSO command. When this parameter is set, the USP V will not delay host write I/Os to the M-VOL until the sidefile amount reaches the puncture threshold (threshold + 10%). This prevents performance degradation for critical volumes and should be used only for a small number of volumes About TrueCopy for z/os Operations

49 100% Sidefile Threshold (ST) = 30% to 70% user-specified Example: Threshold = 50% (default) Host Write I/O delayed 500 ms for every write if Mode 93=OFF 100 ms for every write if Mode 93=ON until below threshold. Suspend TCzA pairs at puncture due to sidefile overflow condition. 70% 60% 50% 45% 40% 35% 30% Puncture Threshold = ST+10% Sidefile Threshold (ST) High-Water Mark = ST-20% Long Delay Type Mode 93 = OFF +400ms X1 delay +300ms X1 delay +200ms X1 delay +100ms X1 delay Short Delay Type Mode 93 = ON +80ms X 1 delay +60ms X 1 delay +40ms X 1 delay +20ms X 1 delay SIM generated at HWM when mode 118 or 464 is ON. SIM ref code = 490x, x = CU This SIM is reported per CLPR every 30 sec. as long as condition exists. Figure 2-4 Graduated Delay Process for Sidefile Management About TrueCopy for z/os Operations 2-27

50 TrueCopy for z/os Async Consistency Group Operations TrueCopy for z/os Async consistency groups enable update sequence consistency to be maintained across a group of volumes. The R-VOLs of the pairs in a consistency group must be located within one RCU (n-to-1 requirement). The TCzA consistency group operations include: Group options Group consistency time Group operations. Group Options TrueCopy for z/os Async provides the following options for each consistency group: Timer Type, Copy Pending timeout, and RCU Ready Timeout. These options are selected when you add a group. If you want to change the timeout options of a group, you must suspend all pairs in the group first. If you want to change the Timer Type option, you must release all pairs. The Timer Type option Copy Pending timeout option must be the same for all MCUs which contain M-VOLs in the group. The RCU Ready timeout option can be different at each MCU if desired. Timer Type. This group option determines how the MCU will acquire the timestamp for the TCzA recordsets: System. When the System timer option is selected, the MCU acquires the time-stamp information for each recordset as follows. When a TCzA pair is established, the MCU reports state-change-interrupt (SCI) to all hosts. The host then issues a series of sense group commands to determine the device status change, and the MCU returns the same response as if the device had been added to an XRC session to activate I/O time-stamping for the device. Once I/O time-stamping is activated, the MVS IOS routine attaches the timestamp information (contents of time-of-day (TOD) clock) to each write I/O operation for the device. The time-stamp indicates the time that the update was generated during start subchannel (SSCH) at the main host system, and the time-stamp is transferred to the MCU at the beginning of each I/O operation. Local. The Local timer option enables the MCU to generate the time-stamp for each update I/O using its own internal clock, rather than using the SMS I/O time-stamp. None. The None timer option should only be selected when establishing TCzA pairs in the reverse direction (from secondary to primary). When the None option is selected, the MCU still acquires the time-stamp information from the host I/O time-stamping function About TrueCopy for z/os Operations

51 Time Out [Copy Pending]. This group option specifies the maximum delay allowed for TCzA copy operations. WARNING: See Adding Consistency Groups for instructions on selecting the correct Time Out [Copy Pending] setting for your operational environment. The RCU will suspend all R-VOLs in the group when: The RCU has not had any communication from the MCU within the specified time. This situation could indicate a disaster or failure at the primary site. The RCU has been receiving recordsets from the MCU(s) but has not been able to settle a recordset within the specified time. This situation may indicate that the RCU does not have enough resources to handle the remote copy and I/O workloads. RCU Ready. This option specifies the maximum delay for re-establishing MCU- RCU communications following MCU power-off. During MCU power-on, the MCU re-establishes communication with all registered RCUs. If it is not able to re-establish communication with an RCU within the specified time, the MCU suspends all affected TCzA pairs. Group Consistency Time During normal TCzA operations, the consistency time (C/T) of a group corresponds to the time-stamp value of the most recently settled recordset at the RCU. The consistency time for the group is indicated as part of the TCzA R- VOL pair status (also displayed by the CQUERY TSO command to the R-VOL). As the main system continues to update the TCzA M-VOLs, the difference between the current system time and the group consistency time indicates the amount of time that the R-VOLs are behind the M-VOLs. The M-VOL updates which take place during this time may be lost when a disaster occurs. When a TCzA pair is suspended, the C/T of the suspended R-VOL is frozen. If the RCU can ensure the update sequence consistency between the suspended R-VOL and the other R-VOLs in the consistency group, the R-VOL C/T is frozen at the latest consistency time of the group. Otherwise, the R-VOL C/T is frozen at the time-stamp value of the most recent update that was successfully copied to the R-VOL. The C/T of a suspended R-VOL may be older than the C/T of other R-VOLs in the group, and if the entire group was not also suspended, the consistency time of the group is still ticking. For suspended TCzA R-VOLs, the TCz Detailed Information dialog box displays whether the C/T was frozen to the group or R-VOL time. About TrueCopy for z/os Operations 2-29

52 Once you have established TCzA operations, you should monitor the consistency time of each group at the RCU(s). If the average delay is longer than your disaster recovery design can accept, you should consider adding remote copy resources (e.g., paths, cache) and/or reducing the I/O workload to improve storage system performance. If the delay between the M-VOL update and the corresponding R-VOL update reaches the time specified by the Time Out [Copy Pending] group option, the MCU will suspend all affected pair(s) due to the heavy I/O workload (at MCU or RCU). To prevent timeout errors, you can increase the Time Out [Copy Pending] value, reduce I/O workload, and/or add remote copy resources. Note: This information is valid only when the timer type is System About TrueCopy for z/os Operations

53 Group Operations TrueCopy for z/os Async provides the following group-based operations to simplify and expedite disaster/failure recovery procedures: Group operations at the MCU: Suspend all pairs in a consistency group (Group suspend option, supported by CSUSPEND TSO command). Resynchronize all suspended pairs in a consistency group (Group resynchronize option, supported by the CESTPAIR TSO command with MODE=RESYNC). Release all pairs in a consistency group (Group release option, supported by CDELPAIR TSO command). Group operations at the RCU: Suspend all pairs in a consistency group (Group suspend option, supported by CSUSPEND TSO command). Release all suspended pairs in a consistency group except for any inconsistent pairs (C/T release option, not supported by CDELPAIR, CDELPAIR cannot be issued to the RCU). Release all pairs in a consistency group regardless of their consistency status (Group release option, not supported by CDELPAIR, CDELPAIR cannot be issued to the RCU). TCzA also provides the Error level pair option which is used to trigger automatic suspension of an entire consistency group. When a TCzA pair is suspended due to failure (not user-requested), this TCzA pair option determines whether all pairs in the same consistency group will also be suspended. If you select the Group error level for a TCzA pair, all pairs in the same group will be suspended. If you select the Volume error level, only the affected TCzA pair will be suspended. Note: The Error level pair option is very important for managing TCzA groups and planning for disaster recovery. The Group error level should be selected for all TCzA volumes which are essential to disaster recovery. Suspended TCzA R-VOLs which have the Volume error level should not be used for disaster recovery. About TrueCopy for z/os Operations 2-31

54 Pair Status TrueCopy for z/os displays the pair status for each volume in the selected logical CU of the connected USP V. The MCU maintains the status of the M-VOL and is responsible for keeping the M-VOL and its R-VOL synchronized. The RCU maintains the status of the R-VOL. The MCU can change the pair status of the M-VOL and R-VOL. The RCU can change the pair status of the R-VOL but not the M-VOL. The MCU will detect when the RCU changes the R-VOL status (if the path status is normal) and will change the M-VOL status accordingly. The TCz pair status can be acquired from the MCU and RCU using the TCz software (Pair Status) and the CQUERY TSO command. Table 2-5 lists and describes the TCz pair status descriptions. A volume which is not assigned to a TCz pair has the status simplex. When a TCz pair is started, the MCU changes the status of both volumes (M-VOL and R-VOL) to pending duplex. When the initial copy operation is complete, the MCU changes the status of both volumes to duplex. When a pair is suspended from the MCU, the MCU changes the status of the M-VOL and R-VOL (if the path status is normal) to suspended. When a pair is suspended from the RCU, the RCU changes the status of the R-VOL to suspended, and the MCU detects the pair suspension (if the path status is normal) and changes the M-VOL status to suspended. When you release a pair from the MCU, the MCU changes the status of the M-VOL and R-VOL (if the path status is normal) to simplex. When you release a pair from the RCU, the RCU changes the R-VOL status to simplex, and the MCU detects the pair release (if the path status is normal) and changes the M-VOL status to suspended. TCzA-Specific Pair Status The TCzA suspending and deleting transitional states occur when a request to change TCzA pair status has been accepted, but the change to the requested status (suspended or simplex) is not yet complete. These states are not reported to the host. In the case of suspending, both the user and the MCU can request the status change. In the case of deleting, only the user can request the status change. If the user requested the status change, the final status is reported at the end of the transition. If an error caused the status to change to suspended, the suspended status is reported at the beginning of the transition. The TCzA SEQCHK status is indicated when a TCzA pair assigned to a consistency group with the System timer type accepts a non-time-stamped update from the primary system. The SEQCHK status does not affect TCzA copy activities and will be removed when the next time-stamped update is successfully copied to the R-VOL. However, if a disaster or system failure occurs before the next time-stamped update, the update sequence consistency between the R-VOL and other R-VOLs in the consistency group is not ensured. To ensure effective disaster recovery, you should detect and remove the source of the SEQCHK status. The SEQCHK status can be caused by any of the following: 2-32 About TrueCopy for z/os Operations

55 An application may issue update I/Os bypassing the MVS standard I/O procedure. The I/O time-stamping function may not be active at the primary system. About TrueCopy for z/os Operations 2-33

56 Table 2-5 Pair Status Simplex Pending Duplex Duplex Suspended (see Table 2-6 for suspend types) TrueCopy for z/os Pair Status Description This volume is not currently assigned to a TCz pair. When this volume is added to a TCz pair, its status will change to pending duplex. The TCz initial copy operation for this pair is in progress. This pair is not yet synchronized. When the initial copy is complete, the status changes to duplex. This pair is synchronized. Updates to the M-VOL are duplicated on the R-VOL. This pair is not synchronized: For TCz Synchronous only, if the MCU cannot keep the pair synchronized for any reason, the MCU changes the status of the M-VOL and R-VOL (if possible) to suspended. For TCzA only, if the MCU detects a TCzA suspension condition, the MCU changes the M-VOL status and R-VOL status (if possible) to suspended. For TCzA only, when the RCU detects a TCzA suspension condition, the RCU changes the R-VOL status to suspended. For TCz Synchronous only, the MCU changes the status of all TCz Synchronous pairs to suspended when it performs the CGROUP/RUN command. When you suspend a pair from the MCU, the MCU changes the status of the M-VOL and R-VOL (if possible) to suspended. When you suspend a pair from the RCU, the RCU changes the status of the R-VOL to suspended. When the MCU detects that the pair was suspended or released from the RCU, the MCU changes the status of the M-VOL to suspended. Pair Status for TCzA only: Suspending Deleting SEQCHK This pair is not synchronized. This pair is in transition from duplex or pending duplex to suspended. When the suspension is requested (by user, MCU, or RCU), the status of all affected pairs changes to suspending. When the suspension is complete, the status changes to suspended. This pair is not synchronized. This pair is in transition from duplex, pending duplex, or suspended to simplex. When the release pair operation is requested (by user), the status of all affected pairs changes to deleting. When the release pair operation is complete, the status changes to simplex. The RCU encountered a non-time-stamped recordset for a TCzA pair using the System timer type option. This status can be displayed at the MCU and RCU, but the MCU may not have the most current information. Always use the pair status information displayed at the RCU for disaster recovery About TrueCopy for z/os Operations

57 Suspended Pairs Table 2-6 lists and describes the TCz suspend types, which indicate the reason for suspension. A TCz pair can be suspended by the user at any time after the initial copy operation is complete. The user must suspend a TCz pair in order to perform ICKDSF maintenance on the M-VOL or to access the R-VOL (read only mode). TCz pairs are also suspended when the CGROUP/ RUN command is processed. When a TCz Synchronous pair is suspended by the user, the MCU ensures synchronization by completing any pending update copy operation before changing the status to suspended. When a TCzA pair is suspended by the user, the MCU and RCU ensure synchronization by either completing or discarding any pending update copy operations according to the user-specified drain/purge suspend option. A TrueCopy for z/os pair is suspended by the MCU when the following suspension conditions are detected. A TCzA pair can also be suspended by the RCU. When the MCU detects that the user has released the pair from the RCU (e.g., to access an R-VOL at the remote site) When the MCU detects an error condition related to the RCU, R-VOL, a TCz Synchronous update copy operation or a TCzA recordset operation When the RCU cannot execute DFW (DASD fast write) to the R-VOL (only if DFW required is selected) When the MCU is unable to communicate with the RCU If a TCz Synchronous update copy operation fails, the MCU maintains exact synchronization by reporting a unit check and decommitting the M-VOL update, so that the host system and application program regard that write operation to the M-VOL as failed. When a TCz pair is suspended, the MCU stops performing update copy operations to the R-VOL. For a suspended TCz Synchronous pair, the MCU may or may not continue accepting write I/Os for the M-VOL depending on the M- VOL fence level and suspend option (if user-requested). If the MCU accepts write I/Os for a suspended M-VOL, the MCU records the data in the M-VOL tracks that are updated while the pair is suspended as the differential data. For a suspended TCzA pair, the MCU and RCU keep track of any recordsets that were discarded during suspension, and the MCU continues accepting write I/Os for the M-VOL and records the data in the M-VOL tracks that are updated while the pair is suspended as the differential data. A suspended TCzA R-VOL has an additional status called the consistency status which is displayed only at the RCU. The consistency status of a suspended TCzA R-VOL indicates its update sequence consistency with respect to the other R-VOLs in the same group. Table 2-7 lists and describes the consistency status descriptions for suspended TCzA R-VOLs. About TrueCopy for z/os Operations 2-35

58 When a TCz pair is suspended, whether user-requested or due to failure, the MCU generates sense information to notify the host(s). If the host system supports IBM PPRC (and the PPRC support RCU option is enabled), this notification results in an IEA494I and/or IEA491E system console message which indicates the reason for suspension. Note: If you need write access to an R-VOL, you must release the pair About TrueCopy for z/os Operations

59 Table 2-6 Suspend Types Suspend Type Applies to Description M-VOL by operator R-VOL by operator M-VOL (TCz Sync only) M-VOL, R-VOL The user suspended the pair from the MCU using the M-VOL Failure option. The R-VOL suspend type is by MCU. The user suspended the pair from the MCU or RCU using the R-VOL option. by MCU R-VOL The RCU received a request from the MCU to suspend the pair. The M-VOL suspend type is M-VOL by Operator or R-VOL by Operator. by RCU M-VOL The MCU detected an error condition at the RCU which caused the MCU to suspend the TCz pair. The R-VOL suspend type is by MCU. Release Pair to RCU M-VOL The MCU detected that the R-VOL status changed to simplex because the user released the pair from the RCU. The pair cannot be resynchronized because the R-VOL does not have the suspended status. R-VOL Failure M-VOL The MCU detected an error during communication with the RCU or an I/O error during update copy. In this case, the R-VOL suspend type is usually by MCU. MCU IMPL M-VOL, R-VOL The MCU could not find valid control information in its nonvolatile memory during the IMPL procedure. This condition occurs only if the MCU is completely without power for more than 48 hours (e.g., power failure and fully discharged backup batteries). Initial Copy failed by FREEZE MCU P/S-OFF by sidefile overflow M-VOL, R-VOL M-VOL, R-VOL (TCz Sync only) R-VOL (TCzA only) M-VOL, R-VOL (TCzA only) The pair was suspended before the initial copy operation was complete. The data on the R-VOL is not identical to the data on the M-VOL. The pair was suspended by the CGROUP/RUN TSO command. The RCU received a request from the MCU to suspend the R-VOL due to MCU power-off. The RCU stops expecting recordsets from that MCU. The amount of sidefile exceeds the specified current pending update data rate, and the RCU data is not transferred within the specified offloading timer. Table 2-7 Consistency Status for Suspended TrueCopy for z/os Async R- VOLs Consistency Status Description Volume This TCzA pair was probably suspended alone. Update sequence consistency between this R- VOL and other R-VOLs in this consistency group is not ensured. This R-VOL cannot be used for disaster recovery at the secondary system. This status is indicated when: This pair was suspended due to a failure that did not affect the entire consistency group, and the Error Level pair option for this pair is set to Volume. This pair was suspended by a user-initiated suspend pair operation with the TCzA Suspend Range suspend option set to Volume. Group This TCzA pair was suspended along with the other pair in its consistency group. Update sequence consistency between this R-VOL and other R-VOLs in this consistency group is ensured. This R-VOL can be used for disaster recovery at the secondary system (after releasing the TCz pair from the RCU). This status is indicated when: All pairs in this consistency group were suspended due to a failure that affected the entire consistency group (not just one pair) (e.g., MCU-RCU communication failure). The pair was suspended due to a failure that did not affect the entire group, and the Error Level TCzA pair option for this pair is set to Group. About TrueCopy for z/os Operations 2-37

60 This pair was suspended by a user-initiated suspend pair operation with the TCzA Suspend Range suspend option set to Group About TrueCopy for z/os Operations

61 Suspended TrueCopy for z/os Async Pairs TrueCopy for z/os Async operations involve additional suspension conditions related to the asynchronous recordset operations. Both the MCU and RCU can detect TCzA suspension conditions and suspend TCzA pairs. Table 2-8describes the TCzA suspension conditions and indicates which CU detects the condition and which pairs are suspended. The TCzA offloading timer async option and timeout group options are used to control the TCzA suspension conditions. See Table 8-4 for troubleshooting information for TCzA suspension conditions. Table 2-8 TrueCopy for z/os Async Suspension Conditions Suspension Condition The MCU could not send a pending recordset to the RCU before the offloading timer async option expired. During MCU power-on, the MCU could not establish communication with the RCU before the RCU Ready timeout group option expired. The RCU could not settle a pending recordset before the copy pending timeout group option expired. The RCU could not communicate with the MCU before the copy pending timeout group option expired. The RCU could not receive the recordset successfully due to a hardware failure. The RCU detected a logical error while selecting the recordset to be settled. The RCU could not settle the recordset due to a hardware failure, a track condition, or a logical error. Detected by: MCU MCU RCU RCU RCU RCU RCU TCzA Pairs to be Suspended All TCzA pairs with M-VOLs in the MCU. All TCzA pairs with M-VOLs in the MCU. All TCzA R-VOLs in the consistency group. All TCzA R-VOLs in the consistency group. Only the affected R-VOL. All TCzA R-VOLs in the group, or only the affected R-VOL, depending on the failure type and error level TCzA pair option. The MCU stores a differential data in the shared memory for each TCzA M- VOL, and the RCU stores a differential data in the shared memory for each TCzA R-VOL. When a TCzA pair is suspended, the tracks which contain the following records are marked in the differential data as modified (to be copied during the resynchronize pair operation): The recordsets that were created by the MCU but not yet sent to the RCU. After marking these tracks as modified, the MCU discards these recordsets. The recordsets that were sent to the RCU but not acknowledged by the RCU. The MCU marks these M-VOL tracks as modified and discards these recordsets. This ensures that recordsets which are lost during transmission to the RCU are identified and marked. The recordsets that reached the RCU but have not yet been settled. After marking these tracks as modified, the RCU discards these recordsets. About TrueCopy for z/os Operations 2-39

62 The M-VOL records updated by host-requested write I/Os after the pair was suspended (same function as for TCz Synchronous pairs). When a suspended TCzA pair is resynchronized, the contents of the RCU s differential data are sent to the MCU and merged into the MCU s differential data. The MCU then performs the resync operation according to the merged differential data. This ensures that all tracks containing recordsets that were discarded are resynchronized at this time About TrueCopy for z/os Operations

63 Business Continuity Manager Support The USP V on which TCz is installed support the Business Continuity Manager commands. If the host system console issues the Business Continuity Manager commands to the USP V, the TCz pair operations can be performed. The Business Continuity Manager commands allow you to add pairs, suspend pairs, resynchronize pairs, release pairs, monitor the pair status, add RCU, and delete RCU. Table 2-11 and Table 2-12 give the USP V adaptor ID (SAID) values. For further information and instructions on Business Continuity Manager, please refer to the Business Continuity Manager User's Guide. Note: Although the same TCz 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. Table 2-9 lists the Business Continuity Manager commands corresponding to PPRC commands. For further information on the PPRC commands. For further information on Business Continuity Manager, please refer to the Business Continuity Manager User s Guide. Table 2-9 Business Continuity Manager Commands Corresponding to PPRC Commands PPRC commands Parameter Business Continuity Manager commands Support type CESTPATH DEVN YKBLDPTH config PRIM config SEC config LINK config CGROUP Not supported RESETHP Not supported CESTPAIR DEVN PRIM *2 YKMAKE/ YKRESYNC config config SEC config MODE Command (RESYNC) Parameter (NOCOPY) PACE config (CopyPace) CRIT config (ErrorLevel) MSGREQ Not supported ONLINSEC Not supported About TrueCopy for z/os Operations 2-41

64 PPRC commands Parameter Business Continuity Manager commands Support type CSUSPEND DEVN YKSUSPND *1 config PRIM *2 config SEC config PRIMARY Not supported QUIESCE Not supported CDELPAIR DEVN YKDELETE config PRIM *2 SEC CRECOVER DEVN YKRECOVER config PRIM *2 SEC ID CQUERY DEVN YKQUERY config FORMAT/UNFORMAT Not supported VOLUME/PATHS Not supported CGROUP DEVN YKFREEZE/YKRUN config PRIM config SEC config FREEZE/RUN Command CDELPATH DEVN YKDELPTH config PRIM config SEC config *1 The YKSUSPEND command supports only the pair suspend command for M-VOL. *2 For further information of parameter, refer to Table About TrueCopy for z/os Operations

65 Table 2-10 Supporting Condition of PPRC Command Parameter PPRC command Parameter Business Continuity Manager support CESTPAIR CSUSPEND CDELPAIR CRECOVER AgnnX AvnnX AGD00 AGP00 AVD00 AVP00 AG000 AV000 AC000 AG000 AV000 config (X is not supported.) Not supported DRAIN operand PURGE operand Not supported Not supported config Not supported Not supported config Not supported About TrueCopy for z/os Operations 2-43

66 Table 2-11 SAID Values for the PATH LINK Parameter (=ports) (FRONT CL1) Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* 1EU CL1-A X'0000 ' (Basic) CL3-A X'0020 ' CL5-A CL7-A CL1-B CL3-B CL5-B CL7-B X'0040 ' X'0060 ' X'0001 ' X'0021 ' X'0041 ' X'0061 ' 1EL CL1-C X'0002 ' (Add2) CL3-C X'0022 ' CL5-C CL7-C CL1-D CL3-D CL5-D CL7-D X'0042 ' X'0062 ' X'0003 ' X'0023 ' X'0043 ' X'0063 ' 1FU CL1-E X'0004 ' (Add1) CL3-E X'0024 ' CL5-E CL7-E CL1-F CL3-F CL5-F X'0044 ' X'0064 ' X'0005 ' X'0025 ' X'0045 ' 1GU CL1-J X'0008' 1KU CL9-N X'008C' 1BU CL9-E X'0084' (Add4) CL3-J X'0028' (Add10) CLB-N X'00AC' (Add14) CLB-E X'00A4' CL5-J X'0048' CLD-N X'00CC' CLD-E X'00C4' CL7-J X'0068' CLF-N X'00EC' CLF-E X'00E4' CL1-K X'0009' CL9-P X'008D' CL9-F X'0085' CL3-K X'0029' CLB-P X'00AD' CLB-F X'00A5' CL5-K X'0049' CLD-P X'00CD' CLD-F X'00C5' CL7-K X'0069' CLF-P X'00ED' CLF-F X'00E5' 1GL CL1-L X'000A' 1KL CL9-Q X'008E' 1BL CL9-G X'0086' (Add6) CL3-L X'002A' (Add8) CLB-Q X'00AE' (Add12) CLB-G X'00A6' CL5-L X'004A' CLD-Q X'00CE' CLD-G X'00C6' CL7-L X'006A' CLF-Q X'00EE' CLF-G X'00E6' CL1-M X'000B' CL9-R X'008F' CL9-H X'0087' CL3-M X'002B' CLB-R X'00AF' CLB-H X'00A7' CL5-M X'004B' CLD-R X'00CF' CLD-H X'00C7' CL7-M X'006B' CLF-R X'00EF' CLF-H X'00E7' 1HU CL1-N X'000C' 1LU CL9-J X'0088' 1AU CL9-A X'0080' (Add5) CL3-N X'002C' (Add11) CLB-J X'00A8' (Add15) CLB-A X'00A0' CL5-N X'004C' CLD-J X'00C8' CLD-A X'00C0' CL7-N X'006C' CLF-J X'00E8' CLF-A X'00E0' CL1-P X'000D' CL9-K X'0089' CL9-B X'0081' CL3-P X'002D' CLB-K X'00A9' CLB-B X'00A1' CL5-P X'004D' CLD-K X'00C9' CLD-B X'00C1' 2-44 About TrueCopy for z/os Operations

67 CL7-F X'0065 ' 1FL CL1-G X'0006 ' (Add3) CL3-G X'0026 ' CL5-G CL7-G CL1-H CL3-H CL5-H CL7-H X'0046 ' X'0066 ' X'0007 ' X'0027 ' X'0047 ' X'0067 ' CL7-P X'006D' CLF-K X'00E9' CLF-B X'00E1' 1HL CL1-Q X'000E' 1LL CL9-L X'008A' 1AL CL9-C X'0082' (Add7) CL3-Q X'002E' (Add9) CLB-L X'00AA' (Add13) CLB-C X'00A2' CL5-Q X'004E' CLD-L X'00CA' CLD-C X'00C2' CL7-Q X'006E' CLF-L X'00EA' CLF-C X'00E2' CL1-R X'000F' CL9-M X'008B' CL9-D X'0083' CL3-R X'002F' CLB-M X'00AB' CLB-D X'00A3' CL5-R X'004F' CLD-M X'00CB' CLD-D X'00C3' CL7-R X'006F' CLF-M X'00EB' CLF-D X'00E3' * Please note that the SAID values in Table 2-11 are different from the ones in Table Table 2-12 SAID Values for the PATH LINK Parameter (=ports) (REAR CL2) Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* 2QU CL2-A X'0010' 2TU CL2-J X'0018' 2WU CLA-N X'009C' 2NU CLA-E X'0094' (Basic) CL4-A X'0030' (Add4) CL4-J X'0038' (Add10) CLC-N X'00BC' (Add14) CLC-E X'00B4' CL6-A X'0050' CL6-J X'0058' CLE-N X'00DC' CLE-E X'00D4 ' CL8-A X'0070' CL8-J X'0078' CLG-N X'00FC' CLG-E X'00F4' CL2-B X'0011' CL2-K X'0019' CLA-P X'009D' CLA-F X'0095' CL4-B X'0031' CL4-K X'0039' CLC-P X'00BD' CLC-F X'00B5' CL6-B X'0051' CL6-K X'0059' CLE-P X'00DD' CLE-F X'00D5 ' CL8-B X'0071' CL8-K X'0079' CLG-P X'00FD' CLG-F X'00F5' 2QL CL2-C X'0012' 2TL CL2-L X'001A' 2WL CLA-Q X'009E' 2NL CLA-G X'0096' (Add2) CL4-C X'0032' (Add6) CL4-L X'003A' (Add8) CLC-Q X'00BE' (Add12) CLC-G X'00B6' CL6-C X'0052' CL6-L X'005A' CLE-Q X'00DE' CLE-G X'00D6 ' CL8-C X'0072' CL8-L X'007A' CLG-Q X'00FE' CLG-G X'00F6' CL2-D X'0013' CL2-M X'001B' CLA-R X'009F' CLA-H X'0097' CL4-D X'0033' CL4-M X'003B' CLC-R X'00BF' CLC-H X'00B7' CL6-D X'0053' CL6-M X'005B' CLE-R X'00DF' CLE-H X'00D7 ' CL8-D X'0073' CL8-M X'007B' CLG-R X'00FF' CLG-H X'00F7' 2RU CL2-E X'0014' 2UU CL2-N X'001C' 2XU CLA-J X'0098' 2MU CLA-A X'0090' About TrueCopy for z/os Operations 2-45

68 Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* (Add1) CL4-E X'0034' (Add5) CL4-N X'003C' (Add11) CLC-J X'00B8' (Add15) CLC-A X'00B0' CL6-E X'0054' CL6-N X'005C' CLE-J X'00D8' CLE-A X'00D0 ' CL8-E X'0074' CL8-N X'007C' CLG-J X'00F8' CLG-A X'00F0' CL2-F X'0015' CL2-P X'001D' CLA-K X'0099' CLA-B X'0091' CL4-F X'0035' CL4-P X'003D' CLC-K X'00B9' CLC-B X'00B1' CL6-F X'0055' CL6-P X'005D' CLE-K X'00D9' CLE-B X'00D1 ' CL8-F X'0075' CL8-P X'007D' CLG-K X'00F9' CLG-B X'00F1' 2RL CL2-G X'0016' 2UL CL2-Q X'001E' 2XL CLA-L X'009A' 2ML CLA-C X'0092' (Add3) CL4-G X'0036' (Add7) CL4-Q X'003E' (Add9) CLC-L X'00BA' (Add13) CLC-C X'00B2' CL6-G X'0056' CL6-Q X'005E' CLE-L X'00DA' CLE-C X'00D2 ' CL8-G X'0076' CL8-Q X'007E' CLG-L X'00FA' CLG-C X'00F2' CL2-H X'0017' CL2-R X'001F' CLA-M X'009B' CLA-D X'0093' CL4-H X'0037' CL4-R X'003F' CLC-M X'00BB' CLC-D X'00B3' CL6-H X'0057' CL6-R X'005F' CLE-M X'00DB' CLE-D X'00D3 ' CL8-H X'0077' CL8-R X'007F' CLG-M X'00FB' CLG-D X'00F3' * Please note that the SAID values in Table 2-12 are different from the ones in Table Command Device To use Business Continuity Manager, you must set the command device for it separately from the command device for an open system. The command device for Business Continuity Manager may be set only from Business Continuity Manager. For information about Business Continuity Manager, please refer to the Business Continuity Manager User s Guide. You can also use Storage Navigator to find the command device for Business Continuity Manager. To find the command device, click File, and then Basic Information on the menu bar of the Storage Navigator main window, and then click the LDEV tab in the Basic Information Display window. For detailed information on the Basic Information Display window, please refer to the Storage Navigator User's Guide. Note: If you use TagmaStore USP/NSC or Lightning 9900V for MCU or RCU, only the volumes whose CU: LDEV number is between 00: 00 to 3F: FF can be used as command devices About TrueCopy for z/os Operations

69 PPRC Support All USP V with TCz installed support IBM PPRC host software functions. You can perform most TCz operations by issuing PPRC TSO (or ICKDSF PPRCOPY) commands from the host system console to the USP V. Using PPRC commands, you can establish and delete remote copy communication paths; establish, suspend, resynchronize, and release TCz Synchronous and TCzA pairs/groups; and view TCz path and pair status. For operating systems that do not support PPRC, the TCz software* is used to control and monitor TCz operations. In this case, TCz provides only state-change-pending (SCP) notifications with service information messages (SIMs). Restrictions. If you plan to use PPRC commands instead of the TCz software to perform TCz operations, the following restrictions apply: System option mode 114 (see Table 2-2) must be enabled to allow automatic port configuration in response to PPRC commands. To fully support an automated environment, the USP V 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. However, even if you set ON for system option mode 114, initiator ports will not automatically change to RCU target ports, nor vice versa, when these ports are in initiator/external mix mode. The USP V will make sure that the specified MCU port is offline to the host, and will automatically configure it as an initiator port if required. Similarly, the corresponding RCU port will also be configured as an RCU target port if required. When the CDELPATH command is issued, the TCz logical paths are removed, and if there are no more TCz or TC logical paths on the port, the port is automatically changed from initiator port mode to RCU target port mode. Note: 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. The fibre-channel interface ports need to be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued. Caution: Before issuing the CESTPATH command, you must make sure that the relevant paths are offline from the host(s) (e.g., configure the Chipid offline, or deactivate the LPAR, or block the port in the ESCD). If any active logical paths still exist, the add path operation will fail because the port mode (RCU Target/Initiator) cannot be changed. The PPRC commands do not allow you to: Change the RCU and CU options. The current default values are: minimum paths = 1, RIO MIH time = 15 sec, incident of RCU = to any host, PPRC support = yes, remote copy service SIM = not report, Freeze option = disable. The TCz software* must be used to change these options. Change the TCz async options. The current default values are: sidefile threshold = 50%, offloading timer = 5 minutes. The TCz software* must be used to change these options. About TrueCopy for z/os Operations 2-47

70 Configure TCzA consistency groups. Since each TCzA pair must belong to one group, the TCz software* must be used to add and configure the groups (timer type, copy pending timeout, RCU ready timeout) before you can add any TCzA pairs. Once the async options, groups, and group options are configured, the PPRC commands can be used to control/monitor TCzA pairs. Change the initial copy priority, CFW data option, or DFW to R-VOL option. If CESTPAIR is used to establish a TCz pair, the following options will be used: initial copy priority = 0, CFW data = copy to R-VOL**, and DFW to R-VOL = not required. The TCz software* must be used to change these options. Note: The DFW to R-VOL setting does not affect the I/O performance of the M-VOLs. If one side of cache is closed due to an RCU failure, the TCz copy operation still uses DFW. The only difference between not required and required is that new pairs cannot be established with the DFW-to-R- VOL required option when one side of RCU cache is closed (the add pair operation fails). Note: When you create a TCz pair, and if you select only M-VOL for the CFW data option, the data set which is updated by CFW in M-VOL cannot be used in R-VOL. To use this data set in R-VOL, release a TCz pair, and format the data set. *Note: If the USP V Storage Navigator software is not installed, please contact your Hitachi account team for further information on TCz configuration services. **Note: By using Remote Copy Function Switch, you can set the following option with PPRC command: CFW data = only M-VOL. If you want to use this function, please contact your Hitachi account team. P/DAS Support TrueCopy for z/os Sync 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 of a TCz pair to the R-VOL without interrupting access to the data. Please refer to the following IBM publications for important information on the requirements and procedures for P/DAS operations: Planning for IBM Remote Copy (SG ), Advanced Copy Services (SC ), DFSMS MVS V1 Remote Copy Guide and Reference (SC ). Note: TCzA does not support P/DAS SWAP. Restrictions: P/DAS does not support CFW operations. You must stop CFW applications before performing P/DAS operations on TCz volumes. P/DAS through channel extenders is not supported About TrueCopy for z/os Operations

71 P/DAS swap option #2 (switch pair & swap) is supported for P/DAS between the USP V, TagmaStore USP/NSC, and 9900V storage systems. Please contact your Hitachi account team for the latest information on P/DAS support. About TrueCopy for z/os Operations 2-49

72 GDPS Support TrueCopy for z/os provides remote copy support for IBM s Geographically Dispersed Parallel Sysplex (GDPS) facility. GDPS is an IBM service offering for mirroring data and balancing workload on storage systems 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 USP V 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 (e.g., CGROUP (FREEZE/RUN)). GDPS support may have additional installation requirements for the USP V TCz MCUs and RCUs, depending on USP V microcode levels and program product versions. Please check the following items with your Hitachi representative: System option modes (e.g., 104). Mode 104 must be ON for 3990 controller emulation (not valid for 2105 and 2107 emulation). For further information on USP V system option modes related to TCz operations, please refer to Table 2-2. Mode 104 must be set before any TCz pairs are established in a GDPS environment. If TCz pairs have already been established, you must release all pairs and logical paths (CDELPAIR, CDELPATH), change the SSIDs and mode settings on the MCUs and RCUs, and then re-establish the paths and pairs (CESTPATH, CESTPAIR). Note on LINK definitions in GDPS: The USP V 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 further information on GDPS, please refer to the following IBM publications: Geographically Dispersed Parallel Sysplex: the S/390 Multi-site Application Availability Solution, Executive Summary (GF ); and Geographically Dispersed Parallel Sysplex: the S/390 Multi-site Application Availability Solution (GF ) About TrueCopy for z/os Operations

73 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 the PPRC Fibre Link-path statistical information. For further information on the PPRC Link-path statistical information acquisition, please refer to the IBM publications. Table 2-13and Table 2-14 give the USP V adaptor ID (SAID) values for the LINK parameters (ports) that are displayed when you acquire the PPRC Linkpath statistical information using RMF. Note: The USP V adaptor ID (SAID) values in Table 2-13 and Table 2-14 are different from the ones for the LINK parameters of CESTPATH TSO commands (see Table 2-11, Table 2-12, Table A-2 ). Note: If you acquire the PPRC Fibre Link-path statistical information by using RMF, and if the total data size per the interval for which you acquire the data is 100 kb and below, zero may be reported for the data size. Even if the data is not updated by host I/O during TCzA operations, the data size is reported. This is because the recordset which does not have data is sent from MCU to RCU. In this case, if the total data size per the interval for which you acquire the data is 100 kb and below, zero may also be reported for the data size. About TrueCopy for z/os Operations 2-51

74 Table 2-13 SAID Values for the LINK Parameters (=ports) of RMF PPRC Link-path Statistical Information (FRONT CL1) Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* 1EU CL1-A X'0000 ' 1GU CL1-J X'0020' 1KU CL9-N X'0070' 1BU CL9-E X'0050' (Basic) CL3-A X'0001 ' (Add4) CL3-J X'0021' (Add10) CLB-N X'0071' (Add14) CLB-E X'0051' CL5-A X'0004 ' CL5-J X'0024' CLD-N X'0074' CLD-E X'0054' CL7-A X'0005 ' CL7-J X'0025' CLF-N X'0075' CLF-E X'0055' CL1-B X'0008 ' CL1-K X'0028' CL9-P X'0078' CL9-F X'0058' CL3-B X'0009 ' CL3-K X'0029' CLB-P X'0079' CLB-F X'0059' CL5-B X'000C ' CL5-K X'002C' CLD-P X'007C' CLD-F X'005C' CL7-B X'000 D' CL7-K X'002D' CLF-P X'007D' CLF-F X'005D' 1EL CL1-C X'0002 ' 1GL CL1-L X'0022' 1KL CL9-Q X'0072' 1BL CL9-G X'0052' (Add2) CL3-C X'0003 ' (Add6) CL3-L X'0023' (Add8) CLB-Q X'0073' (Add12) CLB-G X'0053' CL5-C X'0006 ' CL5-L X'0026' CLD-Q X'0076' CLD-G X'0056' CL7-C X'0007 ' CL7-L X'0027' CLF-Q X'0077' CLF-G X'0057' CL1-D X'000A ' CL1-M X'002A' CL9-R X'007A' CL9-H X'005A' CL3-D X'000B ' CL3-M X'002B' CLB-R X'007B' CLB-H X'005B' CL5-D X'000E ' CL5-M X'002E' CLD-R X'007E' CLD-H X'005E' CL7-D X'000F ' CL7-M X'002F' CLF-R X'007F' CLF-H X'005F' 1FU CL1-E X'0010 ' 1HU CL1-N X'0030' 1LU CL9-J X'0060' 1AU CL9-A X'0040' (Add1) CL3-E X'0011 ' (Add5) CL3-N X'0031' (Add11) CLB-J X'0061' (Add15) CLB-A X'0041' CL5-E X'0014 ' CL5-N X'0034' CLD-J X'0064' CLD-A X'0044' CL7-E X'0015 ' CL7-N X'0035' CLF-J X'0065' CLF-A X'0045' CL1-F X'0018 ' CL1-P X'0038' CL9-K X'0068' CL9-B X'0048' CL3-F X'0019 ' CL3-P X'0039' CLB-K X'0069' CLB-B X'0049' CL5-F X'001C ' CL5-P X'003C' CLD-K X'006C' CLD-B X'004C' 2-52 About TrueCopy for z/os Operations

75 CL7-F X'001 D' CL7-P X'003D' CLF-K X'006D' CLF-B X'004D' 1FL CL1-G X'0012 ' 1HL CL1-Q X'0032' 1LL CL9-L X'0062' 1AL CL9-C X'0042' (Add3) CL3-G X'0013 ' (Add7) CL3-Q X'0033' (Add9) CLB-L X'0063' (Add13) CLB-C X'0043' CL5-G X'0016 ' CL5-Q X'0036' CLD-L X'0066' CLD-C X'0046' CL7-G X'0017 ' CL7-Q X'0037' CLF-L X'0067' CLF-C X'0047' CL1-H X'001A ' CL1-R X'003A' CL9-M X'006A' CL9-D X'004A' CL3-H X'001B ' CL3-R X'003B' CLB-M X'006B' CLB-D X'004B' CL5-H X'001E ' CL5-R X'003E' CLD-M X'006E' CLD-D X'004E' CL7-H X'001F ' CL7-R X'003F' CLF-M X'006F' CLF-D X'004F' * Please note that the SAID values in Table are different from the ones in Table 2-11 and Table A-2. Table 2-14 SAID Values for the LINK Parameters (=ports) of RMF PPRC Link-path Statistical Information (REAR CL2) Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* 2QU CL2-A X'0080 ' 2TU CL2-J X'00A0' 2WU CLA-N X'00F0' 2NU CLA-E X'00D0' (Basic) CL4-A X'0081 ' (Add4) CL4-J X'00A1' (Add10) CLC-N X'00F1' (Add14) CLC-E X'00D1' CL6-A X'0084 ' CL6-J X'00A4' CLE-N X'00F4' CLE-E X'00D4' CL8-A X'0085 ' CL8-J X'00A5' CLG-N X'00F5' CLG-E X'00D5' CL2-B X'0088 ' CL2-K X'00A8' CLA-P X'00F8' CLA-F X'00D8' CL4-B X'0089 ' CL4-K X'00A9' CLC-P X'00F9' CLC-F X'00D9' CL6-B X'008C ' CL6-K X'00AC' CLE-P X'00FC' CLE-F X'00DC' CL8-B X'008 D' CL8-K X'00AD' CLG-P X'00FD' CLG-F X'00DD' 2QL CL2-C X'0082 ' 2TL CL2-L X'00A2' 2WL CLA-Q X'00F2' 2NL CLA-G X'00D2' (Add2) CL4-C X'0083 ' (Add6) CL4-L X'00A3' (Add8) CLC-Q X'00F3' (Add12) CLC-G X'00D3' CL6-C X'0086 ' CL6-L X'00A6' CLE-Q X'00F6' CLE-G X'00D6' CL8-C X'0087 ' CL8-L X'00A7' CLG-Q X'00F7' CLG-G X'00D7' CL2-D X'008A ' CL2-M X'00AA' CLA-R X'00FA' CLA-H X'00DA' About TrueCopy for z/os Operations 2-53

76 CL4-D X'008B ' CL4-M X'00AB' CLC-R X'00FB' CLC-H X'00DB' CL6-D X'008E ' CL6-M X'00AE' CLE-R X'00FE' CLE-H X'00DE' CL8-D X'008F ' CL8-M X'00AF' CLG-R X'00FF' CLG-H X'00DF' 2RU CL2-E X'0090 ' 2UU CL2-N X'00B0' 2XU CLA-J X'00E0' 2MU CLA-A X'00C0' (Add1) CL4-E X'0091 ' (Add5) CL4-N X'00B1' (Add11) CLC-J X'00E1' (Add15) CLC-A X'00C1' CL6-E X'0094 ' CL6-N X'00B4' CLE-J X'00E4' CLE-A X'00C4' CL8-E X'0095 ' CL8-N X'00B5' CLG-J X'00E5' CLG-A X'00C5' CL2-F X'0098 ' CL2-P X'00B8' CLA-K X'00E8' CLA-B X'00C8' CL4-F X'0099 ' CL4-P X'00B9' CLC-K X'00E9' CLC-B X'00C9' CL6-F X'009C ' CL6-P X'00BC' CLE-K X'00EC' CLE-B X'00CC' CL8-F X'009 D' CL8-P X'00BD' CLG-K X'00ED' CLG-B X'00CD' 2RL CL2-G X'0092 ' 2UL CL2-Q X'00B2' 2XL CLA-L X'00E2' 2ML CLA-C X'00C2' (Add3) CL4-G X'0093 ' (Add7) CL4-Q X'00B3' (Add9) CLC-L X'00E3' (Add13) CLC-C X'00C3' CL6-G X'0096 ' CL6-Q X'00B6' CLE-L X'00E6' CLE-C X'00C6' CL8-G X'0097 ' CL8-Q X'00B7' CLG-L X'00E7' CLG-C X'00C7' CL2-H X'009A ' CL2-R X'00BA' CLA-M X'00EA' CLA-D X'00CA' CL4-H X'009B ' CL4-R X'00BB' CLC-M X'00EB' CLC-D X'00CB' CL6-H X'009E ' CL6-R X'00BE' CLE-M X'00EE' CLE-D X'00CE' CL8-H X'009F ' CL8-R X'00BF' CLG-M X'00EF' CLG-D X'00CF' * Please note that the SAID values in Table 2-14 are different from the ones in Table 2-12 and Table A About TrueCopy for z/os Operations

77 Interoperability with Other Products and Functions Some types of volumes used by non-tcz and non-tcza functions can also be used as M-VOL and R-VOL of TCz and TCzA. Table 2-15 explains whether non- TCz and non-tcza volumes are also usable as TCz and TCzA volumes. Table 2-15 Whether Non-TCz and non-tcza Volumes Can Be Used as TCz and TCzA Volumes Functions and Volumes Can the Volumes be Used as TCz M-VOL? Can the Volumes be Used as TCz R-VOL? Can the Volumes be Used as TCzA M-VOL? Can the Volumes be Used as TCzA R-VOL? ShadowImage TM for z/os (SIz) S-VOL in Split status Yes Yes Yes Yes S-VOL in Resync-R status No No No No S-VOL that is also used as a URz primary data volume or URz secondary data volume No No No No S-VOL (none of the above) Yes Yes Yes Yes T-VOL in Split status Yes No Yes No T-VOL (none of the above) No No No No Reserved volume No No No No Compatible FlashCopy S-VOL Yes Yes Yes Yes T-VOL No No No No Compatible FlashCopy V2 S-VOL Yes Yes Yes Yes T-VOL No No No No Concurrent Copy Concurrent Copy volume Yes No Yes No Volume Migration Source volume (when volume migration is in progress) Yes Note: If the source volume is used as M-VOL, the volume migration will stop. Yes Note: If the source volume is used as R- VOL, the volume migration will stop. Yes Note: If the source volume is used as M- VOL, the volume migration will stop. Yes Note: If the source volume is used as R- VOL, the volume migration will stop. Source volume (after volume migration is finished) Yes Yes Yes Yes Target volume No No No No Reserved volume No No No No Universal Replicator for z/os (URz) Primary data volume in Pending duplex status No No No No About TrueCopy for z/os Operations 2-55

78 Functions and Volumes Can the Volumes be Used as TCz M-VOL? Can the Volumes be Used as TCz R-VOL? Can the Volumes be Used as TCzA M-VOL? Can the Volumes be Used as TCzA R-VOL? Primary data volume in Duplex status Yes No. However, the volume can be used as R-VOL only when you restore a TCz pair or perform a Business Continuity Manager YKRESYNC REVERSE operation. No No Primary data volume in Suspend status Yes No. However, the volume can be used as R-VOL only when you restore a TCz pair or perform a Business Continuity Manager YKRESYNC REVERSE operation. No No Primary data volume that is suspended due to a failure Yes No. However, the volume can be used as R-VOL only when you restore a TCz pair or perform a Business Continuity Manager YKRESYNC REVERSE operation. No No Secondary data volume in Pending status Secondary data volume in Duplex status Secondary data volume in Suspend status Secondary data volume in Swapping status Secondary data volume that is suspended due to a failure Yes No No No Yes No No No Yes No No No Yes No No No Yes No No No Volume Retention Manager Volume with Read/Write attribute Volume with Read Only attribute Volume with Protect attribute Yes Yes Yes Yes Yes Yes Yes Yes No No No No Volume Security 2-56 About TrueCopy for z/os Operations

79 Functions and Volumes Can the Volumes be Used as TCz M-VOL? Can the Volumes be Used as TCz R-VOL? Can the Volumes be Used as TCzA M-VOL? Can the Volumes be Used as TCzA R-VOL? Volume registered in a security group Yes Yes However, if the volume is disabled for use as S-VOL, the volume cannot be used as R- VOL. Yes Yes Cross-OS File Exchange Volume usable by both mainframe and open systems No No No No Cache Residency Manager Cache Residency Manager applied volume Yes Yes Yes Yes Compatible PAV Compatible PAV volume Yes Yes Yes Yes Virtual LVI Virtual LVI volume Yes Yes Yes Yes Note: When TCzA, TCA and Universal Replicator coexist in the same USP V, TCzA pairs, TCA pairs and Universal Replicator pairs cannot be mixed in one consistency group. If TCA pair has been allocated to Consistency group No. 00, TCzA pair and Universal Replicator pair cannot be allocated to Consistency group No. 00. TCzA and TCA share the same cache sidefile area. About TrueCopy for z/os Operations 2-57

80 ShadowImage for z/os (SIz) SIz volumes can be assigned to TCz pairs, and TCz volumes can be assigned to SIz pairs. For further information on ShadowImage for z/os, please refer to the ShadowImage for IBM z/os User's Guide. Note: When TCz and ShadowImage for z/os are both active on the same USP V, TCz cannot be used to copy within that storage system. ShadowImage for z/os is recommended for storage system-internal copy. If ShadowImage for z/os is not active, TCz Synchronous supports intra-storage system copy and requires at least one external fibre cable loop. TrueCopy for z/os and ShadowImage for z/os can be used together in the same storage system and on the same volumes to provide multiple copies of data at the main and/or remote sites. Table 2-16 describes the host pair status reporting for TCz volumes, SIz volumes, and TCz/SIz shared volumes. Table 2-17 shows the currency of the data on a shared TCz/SIz volume based on TCz and SIz pair status. For shared TCz/SIz volumes, the TCz pair status is reported to the host if you query the TCz R-VOL. To obtain the SIz pair status, query from the host: the SIz T-VOL status of the SIz pair if the SIz S-VOL and TCz M-VOL share the same volume the SIz T-VOL status of the SIz pair if the SIz S-VOL and TCz R-VOL share the same volume the SIz S-VOL status of the SIz pair if the SIz T-VOL and TCz M-VOL share the same volume. ShadowImage for z/os supports multiple target volumes (T-VOLs) for each source volume (S-VOL). If you issue a pair status query to a SIz S-VOL (e.g., CQUERY), the status for only one SIz pair is reported (the pair with the T-VOL with the lowest LDEV ID). To obtain the pair status for the SIz pair(s) with the other T-VOL(s), you must direct the host query to the specific T-VOL using the T-VOL s LDEV ID in the host command (e.g., CQUERY DEVN parameter). The ShadowImage for z/os software displays the LDEV ID and SIz pair status of all T-VOLs associated with an S-VOL About TrueCopy for z/os Operations

81 Table 2-16 Host Pair Status Reporting for TCz/SIz Shared Volumes Number of TCz Pairs Number of SIz T-VOLs Pair Status Reported by USP V 0 0 Simplex 0 1 SIz pair status 0 2 or more SIz pair status for the pair whose T-VOL has the lowest LDEV ID 1 0 TCz pair status 1 1 TCz pair status 1 2 or more TCz pair status Table 2-17 Data Currency of a Shared TCz/SIz Volume TCz Pair Status SIz Pair Status Pending Duplex SP-Pend V-Split Split Resync Resync-R Suspend Pending Not current Not current Not current Not current CURRENT Not current -- Not current Duplex Not current Not current Not current Not current CURRENT Not current -- Not current Suspend Not current CURRENT CURRENT CURRENT CURRENT CURRENT CURRENT Not current Figure 2-5 through Figure 2-8 show the various TCz/SIz configurations which share volumes. TCz supports synchronous and asynchronous operations for shared volumes. Figure 2-5 shows an example of a volume which is functioning as both a TCz M-VOL and a SIz S-VOL. This configuration allows you to: Use TCz to provide remote backup copies of SIz S-VOLs, and/or Use SIz to provide on-site backup copies of TCz M-VOLs. TCz M-VOL SIz R-VOL S-VOL T-VOL Figure 2-5 TrueCopy for z/os and ShadowImage for z/os: Shared M- VOL/S-VOL About TrueCopy for z/os Operations 2-59

82 Figure 2-6 shows an example of a volume which is functioning as both a TCz R-VOL and a SIz S- VOL. This configuration allows you to use ShadowImage for z/os to provide additional remote copies of TCz M-VOLs. TCz M-VOL R-VOL SIz S-VOL T-VOL Figure 2-6 TrueCopy for z/os and ShadowImage for z/os: Shared R- VOL/S-VOL Figure 2-7 shows an example of a volume which is functioning as both a TCz M-VOL and a SIz S- VOL, while the R-VOL of the same TCz pair is also functioning as the S-VOL of another SIz pair. This configuration allows you to: Use TrueCopy for z/os to provide remote backup of SIz S-VOLs, and/or Use ShadowImage for z/os to provide on-site backup copies of TCz M-VOLs and R-VOLs. TCz M-VOL SIz R-VOL SIz S-VOL T-VOL S-VOL T-VOL Figure 2-7 TrueCopy for z/os and ShadowImage for z/os: Shared M- VOL/S-VOL and R-VOL/S-VOL Figure 2-8 shows an example of a volume functioning as both a TCz M-VOL and a SIz T-VOL. Note: This configuration does not allow SIz and TCz to copy at the same time. Create the SIz pair first, and then split the pair before creating the TCz pair. You must suspend the TCz pair in order to resync the SI pair About TrueCopy for z/os Operations

83 SIz TCz M-VOL R-VOL S-VOL T-VOL Figure 2-8 TrueCopy for z/os and ShadowImage for z/os: Shared M- VOL/T-VOL Caution: When you share a TCz R-VOL with an SIz S-VOL as shown in Figure 2-6 or Figure 2-7 the write operation to the TCz M-VOL takes time. Especially, when the SIz pair is in the V-Split status, the write operation to the TCz M-VOL may takes extra time according to the time for copying process of the SIz pair. In addition, note that in the case of TCzA, the TCz pair may be suspended by failure because of the shortage of the capacity of its side file. Universal Replicator for z/os (URz) TCz volumes can be assigned to URz pairs. For further information on URz, please refer to the Universal Replicator for IBM z/os User's Guide. Virtual LVI Virtual LVI volumes can be assigned to TCz pairs, as long as the R-VOL has the same or larger capacity than the M-VOL. If you need to perform Virtual LVI/LUN operations on an existing TCz M-VOL or R-VOL, you must release the pair first to return the volume to simplex status. For further information on Virtual LVI/LUN, please refer to the Virtual LVI/LUN and Volume Shredder User s Guide. Cache Residency Manager The volumes that are applied Cache Residency Manager can be assigned to TCz pairs, and Cache Residency Manager operations can be performed on TCz M-VOLs and R-VOLs. For further information on Cache Residency Manager, please refer to the Cache Residency Manager User's Guide. About TrueCopy for z/os Operations 2-61

84 Server Priority Manager The Server Priority Manager (SPM) software can give higher priority to the I/O operations of the server that requires the high processing performance than the I/O operations of the other servers. SPM can set the priority of I/O operation to ports, but if the remote copy is performed with the fibre-channel interface connection, the initiator ports do not support the Server Priority Manager option. For further information on SPM, please refer to the Performance Manager User's Guide About TrueCopy for z/os Operations

85 About TrueCopy for z/os Operations 2-63

86

87 3 Preparing for TrueCopy for z/os Operations This chapter describes the requirements for using TrueCopy for z/os and provides instructions for installing the TrueCopy for z/os hardware and software and preparing the Hitachi storage systems for TrueCopy for z/os operations. Please read this chapter before you start the operation of TrueCopy for z/os. Preparing for TrueCopy for z/os Operations 3-1

88 System Requirements TrueCopy for z/os operations involve the USP V MCUs and RCUs containing the main and remote volumes, the remote copy connections between the MCUs and RCUs, the zseries and S/390 host(s) at the main and remote sites, and the TrueCopy for z/os software. The TrueCopy for z/os system requirements are: MCU: USP V storage system with TrueCopy for z/os installed by using license code. Note: For information on remote copy operations using the TagmaStore USP/NSC storage system as an MCU, please refer to the Hitachi TagmaStore USP/NSC TrueCopy for z/os User and Reference Guide (MK-94RD214). Note: For important information about proper configuration for your operational environment, refer to Appendix C. RCU: USP V storage system with TrueCopy for z/os installed by using license code. Note: TagmaStore USP/NSC storage system with TrueCopy for z/os installed can be used as an RCU connected to a USP V MCU. For assistance with mixed storage system configurations, please contact your Hitachi representative. Note: TrueCopy for z/os can coexist with TrueCopy (all copy modes) in the same USP V storage system. Full fibre-channel support will allow concurrent fibre-mode TrueCopy and TCz operations. Note: The USP V storage systems may have additional installation requirements (e.g., system option modes, DKC-F510I-32FS2, DKC-F515I- MIX2, additional cache, etc.). For information on system option modes for TrueCopy for z/os, refer to Table 2-2. zseries and S/390 host: MVS/DFP PTF, or VM/ESA PTF. Optional error recover procedure (ERP) functions require MVS/DFP or later. ICKDSF R16 + PTF functions require VM/ESA or later. If the primary and/or secondary system consists of several CPU complexes, a SYSPLEX timer is required to provide a common time reference for the host I/O time-stamping function. Remote copy connections fibre channel: Multimode or single-mode optical fibre cables are required at both the MCU and RCU. For distances from 0.5 km to 1.5 km (1,640 to 4,920 feet), multimode shortwave fibre channel interface cables with up to two switches are required. For distances from 10 km to 30 km (6.2 to 18.6 miles), single-mode longwave fibre channel interface cables with up to two switches are required. 3-2 Preparing for TrueCopy for z/os Operations

89 For distances greater than 30 km, approved third-party channel extender products and telecommunications lines are required. Preparing for TrueCopy for z/os Operations 3-3

90 Storage Navigator software and TrueCopy for z/os license code(s): The USP V Storage Navigator software is required for USP V TrueCopy for z/os operations. The TrueCopy for z/os software is a component of the USP V Storage Navigator. The TrueCopy for z/os license key code(s) are required to enable the TrueCopy for z/os software on the USP V storage system. Separate license codes are required for each USP V storage system. Note: Administrator or TrueCopy for z/os write access to the USP V Storage Navigator software is required to perform TrueCopy for z/os operations. Users without Administrator or TrueCopy for z/os write access can only view TrueCopy for z/os information. Note: You must operate the USP V Storage Navigator software in Modify mode to perform TrueCopy for z/os operations. Users in view mode can only view TrueCopy for z/os information. About the license of TrueCopy Asynchronous for z/os: If you want to use TrueCopy for z/os Async, you must install not only TrueCopy Asynchronous for z/os but also for TrueCopy for z/os. So, you need license codes for both TrueCopy Asynchronous for z/os and TrueCopy for z/os. Also, the license capacity of TrueCopy for z/os and the license capacity of TrueCopy Asynchronous for z/os must satisfy the following equation: License capacity of TrueCopy for z/os License capacity of TrueCopy Asynchronous for z/os 3-4 Preparing for TrueCopy for z/os Operations

91 Requirements and Restrictions TrueCopy for z/os has the following requirements and restrictions: Track format One-to-one volume copy operations Duplicate VOLSER (Volume Serial Number) Logical volume image (LVI) Accessing TCz M-VOLs and R-VOLs Cache, NVS, and DASD fast write Consistency groups Restrictions on volumes Track Format TrueCopy for z/os has the following disk track format requirements which must be ensured by the user. TCz cannot detect exceptions to these requirements. The MCU will abort the TCz initial copy operation if the track format for both the M-VOL and R-VOL does not meet the following requirements. The TCz 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 MCU will abort 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. One-to-One Volume Copy Operations TrueCopy for z/os requires a one-to-one relationship between the volumes of the pairs. A volume can only be assigned to one TCz pair at a time. TCz does not support operations in which one M-VOL is copied to more than one R-VOL, or more than one M-VOL is copied to one R-VOL. Since TCz pairs are created on volumes rather than datasets, multivolume datasets require special attention. For complete duplication and recovery of multivolume datasets, make sure that all volumes of a multivolume dataset are copied to TCz R- VOLs, and use TCzA to ensure update sequence consistency across the R-VOLs at the remote site. Preparing for TrueCopy for z/os Operations 3-5

92 Duplicate VOLSER The TrueCopy for z/os initial copy operation copies the VOLSER of the M-VOL to the R-VOL, if the No Copy initial copy option is not selected. For this reason, the M-VOL and R-VOL of a TCz pair must have the same VOLSER. Since the host OS does not allow duplicate VOLSERs, the host system administrator must take precautions to prevent system problems related to duplicate VOLSERs. For example, the TCz R-VOLs must be defined in the system generation so they do not come online automatically (see WARNING below). WARNING: If the volumes which will become TCz R-VOLs are physically attached to the same system images as the production volumes which will become the TCz M-VOLs, the following problems can occur: When a TCz pair is established using the TSO CESTPAIR command, the secondary volume might be online (PPRC allows this; TCz does not*). This could produce a duplex secondary online to a host image, the results of which are not predictable. When a TCz pair is released, the old secondary volume is usually offline. If a host image is IPL d, the operator will be offered both volumes and asked which volume should be left offline the old duplicate volser message. This can be confusing and is prone to error. To avoid duplication of VOLSER, first you must identify the volumes that will not be accessed by the host system. Next, you must perform CHP OFF or some other operation to ensure that the volumes are inaccessible. After that, when performing IPL, you must perform LOAD CLEAR. To avoid these problems, Hitachi strongly recommends that the user specify OFFLINE=YES if the secondary volumes are to be generated in the production host s IOCP and system generation. *Note: If you cannot create a pair because the TCz R-VOL is online with hosts, all paths must be offline from all hosts. If you cannot identify the hosts that are online, please contact your Hitachi account team. You can obtain the information about online paths from SSBLOG of SVP. 3-6 Preparing for TrueCopy for z/os Operations

93 Logical Volume Image (LVI) TrueCopy for z/os supports all basic mainframe LVIs which can be configured on the USP V (e.g., , -3R, -9, -L). TCz does not support multiplatform volumes (3390-3A/B/C). TCz can copy data between volumes with the same emulation and capacity (e.g., R to R), and can also copy from smaller volumes to larger volumes* (e.g., to ) of the same emulation (VTOC expansion must be used). TCz also supports the Virtual LVI/LUN feature of the USP V, enabling you to establish TCz pairs with custom-size LVIs as well as standard-size LVIs. When custom-size LVIs are assigned to TCz pairs, the R-VOL must have the same or larger capacity than the M-VOL. The TCz software displays the LVI of the M-VOLs and R-VOLs. *WARNING: If you utilize TCz to copy from a smaller volume to a larger volume, you will not be able to perform TCz operations in the reverse direction (from the secondary site to the primary site) after a disaster has occurred and the secondary site was used for production. If the SUSPEND command is issued from Business Continuity Manager, you will not be able to use the Secondary Volume R/W option and Reverse option. This restriction exists because TCz does not support copying from a larger volume to a smaller volume. Hitachi strongly recommends that this capability (copying from a smaller volume to a larger volume) only be used for data migration purposes. WARNING: If you use a Fujitsu operating system, and utilize TCzA to copy from a smaller capacity of M-VOL to the larger capacity of R-VOL, an error will occur when the write operation will be performed to the former R-VOL after the pair has been released. If the write operation is required on this volume, make the capacity of M-VOL and R-VOL same, and then create a pair. Preparing for TrueCopy for z/os Operations 3-7

94 Accessing TrueCopy for z/os M-VOLs and R-VOLs Write operations to a TCz M-VOL which specify normal authorization are duplicated on the R-VOL of the TCz pair. Write operations with diagnostic or device support authorization (e.g., ICKDSF) are completed at the M-VOL but are not duplicated at the R-VOL. Therefore, you must suspend a TCz pair before performing ICKDSF media maintenance on the M-VOL. To ensure maximum data integrity during normal TCz operations, the RCU rejects all read and write operations issued by a host to a TCz R-VOL. If you need read-only access to a TCz R-VOL, you must have the R-VOL read option enabled on the RCU, and you must suspend the pair to read the R-VOL. The R- VOL read option can only be enabled by the Hitachi representative. If you need write access to a TCz R-VOL (e.g., to perform ICKDSF), you must release the pair from the RCU to change the R-VOL pair status to simplex. Cache, NVS, and DASD Fast Write Cache and nonvolatile storage (NVS) must be operable for both the MCU and RCU of a TCz pair. If not, the Add Pair operation will fail. The remote storage system cache should be configured to adequately support the TCz remote copy workloads as well as any local workload activity. DASD fast write (DFW) is required at the MCU and RCU only when the DFWto-R-VOL required TCz pair option is specified. If DFW to an R-VOL is blocked and the TCz pair was established with the DFW-to-R-VOL required pair option, the MCU detects DFW OFF at the R-VOL and suspends the pair. TCz pairs which were established using PPRC commands use the default value of not required and therefore are not suspended when DFW to the R-VOL is blocked. Note: The DFW to R-VOL setting does not affect the I/O performance of the M-VOLs. If one side of cache is closed due to an RCU failure, the TCz copy operation still uses DFW. The only difference between not required and required is that new pairs cannot be established with the DFW-to-R-VOL required option when one side of RCU cache is closed (the add pair operation fails). 3-8 Preparing for TrueCopy for z/os Operations

95 Consistency Groups The TCzA consistency groups have the following requirements: All TCzA pairs must be assigned to one and only one consistency group. The maximum number of pairs in one consistency group is The maximum number of consistency groups established for one MCU-RCU pair is 128. The RCU supports a maximum of 128 groups. This limit of 128 groups includes both TCzA groups and TC Asynchronous groups (e.g., 64 TCzA + 64 TCA). Each update I/O to the M-VOLs in one consistency group must be timestamped using a common timer facility. The primary host system cannot access pairs of the same consistency group if the pairs do not have a common timer reference. A consistency group must consist of TCzA pairs or TCA pairs, but not both. Only TCzA pairs that belong to the same CLPR can be allocated to one consistency group. For further information on CLPR, please refer to the Virtual Partition Manager User's Guide. Restrictions on Volumes If CSUSPEND or FREEZE command is used, TCz M-VOLs may report SCP (State Change Pending) to the host. If the CSUSPEND, or FREEZE command is issued to certain volumes (e.g., active SPOOL, PAGE, or CATALOG datasets, active SYSRES volume), the attached host(s) may enter a deadlock condition and may require a storage control IML to correct the condition. Preparing for TrueCopy for z/os Operations 3-9

96 Assessing TCz Requirements Calculation of the Maximum Number of Pairs The differential data (updated by write I/Os during suspension) between M- VOL and R-VOL is stored in each track bitmap. When a released/suspended pair is resynchronized, the MCU merges the M-VOL and R-VOL bitmaps, and the differential data is copied to the R-VOL. The maximum number of pairs you can create is restricted. Use the number of cylinders and bitmap areas to calculate the maximum number of pairs that can be created in a storage system. The number of cylinders: The number of cylinders depends on the capacity of the volumes (the number of cylinders set by VLL, if you set the VLL feature) used for the pairs. Both the MCU and RCU are restricted. The number of bitmap areas: To calculate the number of bitmap areas in each volume: The number of bitmap areas = ( ((Number of cylinders 15) / 122,752) ) The symbols around a value indicate that the value should be rounded up to the next integer. Note: 122,752 is the amount of differential data per bitmap area. The unit for the amount of differential data is bits. The maximum number of pairs that can be created: The number of bitmap areas you can use in storage system depends on the number of shared memories you add to storage system. Table 3-1 shows the relation between the number of shared memories and the number of usable bitmap areas of storage system. Table 3-1 Relation between the Additional Shared Memory and the Number of Usable Bitmap Areas of Storage System Additional Shared Memory for TCz Number of Usable Bitmap Areas of Storage System No additional shared memory for TCz 0 Additional shared memory for TCz is installed 7,424 Extension 1 16,384 Extension 2 32,768 Extension 3 44,256 Extension 4 65, Preparing for TrueCopy for z/os Operations

97 If the calculated number of bitmap areas exceeds the total number of bitmap areas in the storage system, the number of pairs that can be created will be limited. To calculate the maximum number of pairs that you can create: The maximum number of pairs that you can create = ( (the total number of bitmap areas in the storage system Number of bitmap areas) ) The symbols around a value indicate that the value should be rounded down to the nearest whole number.. Note: The maximum number of pairs that you can create cannot exceed 37,768. Preparing for TrueCopy for z/os Operations 3-11

98 Caution: The bitmap areas that are used for TC-MF are shared with Universal Replicator for z/os. If you use both TC-MF and Universal Replicator for z/os, use the total value of both pairs. Also, if you use the same volume with TC-MF and Universal Replicator for z/os, use the total value of both pairs regardless of whether the volume is P-VOL or S-VOL. The unit of Difference Management (track or cylinder): The differential data between P-VOL and S-VOL is stored in units of tracks or cylinders. Caution: You may specify the unit of Difference Management when you create a pair with the Add Pair dialog box. If USP V is connected with TagmaStore USP/NSC or Lightning 9900V, the unit of Difference Management is applied as it is when you specify the unit. If USP V is connected with TagmaStore USP/NSC or Lightning 9900V, the maximum number of pairs that you can create is the lesser number by comparing both numbers. If USP V is connected with TagmaStore USP/NSC or Lightning 9900V, you can use both the Storage Navigator software and the Command Control Interface software to specify the unit of Difference Management: "Auto", "Track" and "Cylinder". You can also refer to the setting of Difference Management by using them. Caution: If the unit of Difference Management is set to "Auto", "Track" or "Cylinder" will be set automatically according to the number of cylinders of a volume that a pair will be created with. If VLL has been used, the number of cylinders that you set with VLL software is applied. If the volume that you want to create a pair with has 10,019 or more cylinders, "Cylinder" will be set. If the volume has less than 10,019 cylinders, "Track" will be set. Note: If the unit of Difference Management is set to "Track" by using the TrueCopy for z/os software from the Storage Navigator computer, the number of pairs that you can create with the storage system is restricted. If the number of pairs that you create exceeds the restriction, the differential data will be stored in units of cylinders automatically, and pairs will be created. To restrict automatic changing of the unit of Difference Management, call the service engineer Preparing for TrueCopy for z/os Operations

99 Performance and DR Considerations Before starting TrueCopy for z/os operations, you must consider the relative importance of storage system I/O performance and disaster recovery preparation. TCz operations can affect the I/O performance of the MCUs and RCUs. TCz provides many options (RCU options, initial copy options, pair options, group options, and async options) which allow you to control the impact of TCz operations on storage system I/O performance. These options can be set separately for each TCz pair, for each TCzA group, and for each MCU to provide maximum flexibility. You can select options which minimize the impact of TCz operations on storage system performance, or options which maximize the effectiveness of TCz operations to ensure the best level of backup data integrity. System-level factors (e.g., number of paths) can also affect TCz operations and storage system performance (Table 5-7). For TCz disaster recovery operations, you should make sure that the RCUs are attached to a host processor to enable reporting of sense information and transfer of ERC information. If the remote site is unattended, you should attach the RCUs to a host processor at the main site, so that the system administrator can monitor the operational condition of the RCUs. Note: TrueCopy for z/os and ShadowImage for z/os can function together in the same USP V to provide both internal and remote backup for your important data. If you are planning to combine TrueCopy for z/os and ShadowImage for z/os, please read the important configuration information in Interoperability with Other Products and Functions. Identifying the Source and Target Volumes To prepare for TCz pair operations, you need to identify the volumes (by LDEV ID) for which you want to establish TCz remote copy operations. You should identify not only the volumes which contain the important data to be backed up (e.g., DB2 log files), but also the volumes which contain the catalog and control datasets (i.e., master catalog, key user catalogs, system control datasets). Copying these datasets to the remote site will enable faster disaster recovery than maintaining a current version of these files at the remote site. For large databases which span multiple volumes and even multiple USP Vs, you should plan to establish a TCzA consistency group for each database, so that the update sequence consistency of the database can be ensured at the remote site. You can start establishing the TCz pairs as soon as you have: Identified the volumes which will become the TCz M-VOLs and R-VOLs Ensured that all system and TCz requirements have been met Assessed TCz Requirements Completed hardware and software installation Configured the MCUs and RCUs for TCz operations Preparing for TrueCopy for z/os Operations 3-13

100 Installing the Hardware Initial installation of the TrueCopy for z/os hardware is planned and performed by the user and the Hitachi representative. To install the hardware required for TCz operations: 1. User: Identify the TCz M-VOLs and R-VOLs (main and remote volumes), so that the TCz hardware can be installed and configured properly. 2. User: On the host operating system, make sure that the missing interrupt handler (MIH) value (also called host I/O patrol time) is set high enough to accommodate the number of pairs, the cable length between the MCUs and RCUs, and the initial copy pace. The recommended MIH value for TCz operations is 60 seconds. For MVS, the MIH value is specified in the SYS1.PARMLIB file. 3. Hitachi Representative: Make sure that the MCU(s) and RCU(s) are configured for the USP V Storage Navigator's operations (e.g., SVP connected to LAN). Refer to the Storage Navigator User's Guide for information and instructions on setting up the USP V Storage Navigator's operations. 4. Hitachi Representative: Make sure that the MCUs and RCUs are properly configured for TCz operations (e.g., cache, NVS, DFW). If the user plans to perform TCzA and/or Concurrent Copy operations in the same storage system, make sure to install adequate cache to handle the increased sidefile usage. When determining the required amount of cache, you must also consider the amount of Cache Residency Manager data to be stored in cache. 5. Hitachi Representative: Make sure that the desired system option modes are enabled (see Table 2-2). 6. Hitachi Representative: Make sure the MCUs are configured to report sense information to the host(s). The RCUs should also be attached to a host processor to enable reporting of sense information in case of a problem with an R-VOL or RCU. If the remote site is unattended, the RCUs should be attached to a host processor at the main site, so that the system administrator can monitor the operational condition of the RCUs. 7. Hitachi Representative: For fibre-channel interface connections, install the fibre channel adapter features (e.g., DKC-F510I-32FS2, DKC-F515I-MIX2). Please refer to the Installation section of the USP V Maintenance Manual for detailed information and instructions Preparing for TrueCopy for z/os Operations

101 8. Hitachi Representative: If the user plans to use the Local TCzA timer type option, set the SVP clock to local time so that the TCzA time-stamps will be correct. 9. Hitachi Representative: Install the TCz remote copy connections between the MCU(s) and RCU(s). This hardware (optical fibre cables, switches, etc.) is supplied by the user. Distribute the paths between different storage clusters and ESCDs or switches to provide maximum flexibility and availability. The logical paths between the MCU and RCU must be separate from the logical paths between the host and RCU. For fibre-channel interface connections, all remote copy activities between two USP Vs (i.e., TCz, TCzA, TrueCopy Sync, and TrueCopy Async) can share the same remote copy connections. Remote Copy Connections Figure 3-1 shows the remote copy connection configurations for fibre-channel interface TCz operations. The MCU and RCU of each TCz pair must be connected via multimode shortwave or single-mode longwave optical fibre cables. If you use multimode shortwave optical fibre cables, fibre cables up to 1.5 km in length and up to two switches are required for distances greater than 0.5 km. If you use single-mode longwave optical fibre cables, fibre cables up to 30 km in length and up to two switches are required for distances greater than 10 km. TCz operations can be performed at distances of up to 30 km (18.6 miles) using standard single-mode longwave support. Long-distance solutions are provided using approved channel extenders and communication lines. MCU/RCU Shortwave: 0.5 km Longwave: 10 km RCU/MCU Multimode shortwave optical fibre cables up to 0.5 km MCU/RCU MCU/RCU MCU/RCU MCU/RCU Shortwave: 1.5 km Longwave: 30 km (Max) Unrestricted distance RCU/MCU RCU/MCU RCU/MCU RCU/MCU Single-mode longwave optical fibre cables up to 10 km Switch Channel Extender ATM telecommunications lines Figure 3-1 Fibre-Channel Remote Copy Connection Configurations Note: For fibre-channel interface connections, you can use the switches as for ordinary switch connections, and no special settings are required for the USP Vs. Preparing for TrueCopy for z/os Operations 3-15

102 Fibre-channel interface connection provides three different configurations (see also the LUN Manager User s Guide): Direct connection (see Figure 3-2): Two devices are connected directly together. Switch connection (see Figure 3-3): Up to three optical fibre cables are connected together via the switches to connect the devices. Up to two switches can be used. Extender connection (see Figure 3-4): Channel extenders and switches are used to connect the devices across large distances. Host (Primary) Host (Secondary) NL Port * Initiator port MCU RCU RCU target port Ordinary fibre-channel interface port (target port) * To set ports, use LUN Manager and set port topology to: Fab off, FC-AL. Figure 3-2 Fibre Channel Interface Direct Connection (NL_Port) Host (Primary) FL_Port or F Port [1] E Port FL_Port or F Port [1] Host (Secondary) Initiator port RCU target port MCU NL_Port or N Port [2] RCU Ordinary fibre-channel interface port (target port) Switch 1. Some switch vendors require F port (e.g., McData ED5000). 2. To set ports, use LUN Manager and set port topology to: NL port: Fab on, FC-AL N port: Fab on, Point-to-Point Figure 3-3 Fibre Channel Interface Switch Connection (NL_Port or N_Port) 3-16 Preparing for TrueCopy for z/os Operations

103 Host (Primary) Host (Secondary) Initiator port RCU target port MCU NL_Port or N Port * RCU Ordinary fibre-channel interface port (target port) Switch Channel extender * To set ports, use LUN Manager and set port topology to: NL port: Fab on, FC-AL N port: Fab on, Point-to-Point Figure 3-4 Fibre Channel Interface Extender Connection Preparing for TrueCopy for z/os Operations 3-17

104 Channel Extenders for Serial Remote Copy Connections TrueCopy for z/os Async (TCzA) can be integrated with third-party channel extender products to provide remote data backup for distances greater than 43 km. The following information was current at the time of publication of this document, but may change. Please contact your Hitachi account team for the latest information on channel extender support for TCz. Note: For fibre-channel interface connections, you can use the switches as for ordinary switch connections, and no special settings are required for the USP Vs. TrueCopy for z/os has been tested with the CNT UltraNet Storage Director: UltraNet supports T3 and ATM (asynchronous transfer mode) communication lines. UltraNet supports ATM OC-3 (optical carrier) levels. The transfer speed of OC-3 is a maximum of 155 Mb/s. The transfer speed of T3 is a maximum of 44 Mb/s. The USP Vs serial numbers must be set on the channel extenders as follows. If the serial numbers are not set correctly, the TCz add pair operation will terminate with an error. For CNT UltraNet, this operation must be coordinated with the Hitachi representative and performed by the CNT representative. Set the RCU serial number to the MCU-side extender. Set the MCU serial number to the RCU-side extender. Set the serial number on each CNT UltraNet port. Make sure that your channel extenders are capable of supporting the TCzA channel command. The parameter length and detailed specification of the TCzA channel command are different than for TCz Synchronous RIOs. The LDEV IDs of the R-VOLs must be assigned on each port of the MCU-side extender. The maximum number of LDEVs which can be assigned on each port is 254. Figure 3-5 shows the required LDEV assignment on each extender port. If the LDEV IDs are not assigned properly, the TCz add pair operation will terminate with an error. For CNT UltraNet, this operation must also be performed by the CNT representative Preparing for TrueCopy for z/os Operations

105 CU# LDEV ID Range Port #0 00-FD #A #1 00-FD #B CNT #2 00-FD #C UltraNet #3 00-FD #D Example 1: Assigning the same LDEV IDs of a specific CU number to each port. CU# #0 #1 #2 #3 Port 00-3F 00-3F 00-3F 00-3D #A LDEV ID 40-7F 40-7F 40-7F 40-7D #B CNT Range 80-BF 80-BF 80-BF 80-BD #C UltraNet C0-FF C0-FF C0-FF C0-FD #D Example 2: Assigning specific LDEV IDs on each CU number to each port. Figure 3-5 Assigning R-VOL LDEV IDs to the Channel Extender Ports Preparing for TrueCopy for z/os Operations 3-19

106 Enabling TrueCopy for z/os Options You must enable the TrueCopy for z/os option(s) (Asynchronous and/or Synchronous) on the USP Vs using the USP V Storage Navigator software. Each TrueCopy for z/os option requires a separate license key code, and each USP V requires its own separate set of license key codes. For instructions on using the USP V Storage Navigator software and enabling the TrueCopy for z/os option(s), please refer to the Storage Navigator User's Guide (MK-96RD621). Note: When you use Storage Navigator on UNIX workstations or in other non-windows environments, certain additional operating conventions must be followed. For details, refer to the Storage Navigator User's Guide (MK-96RD621). Disabling TrueCopy For information on disabling the TrueCopy for z/os options, please refer to the Storage Navigator User's Guide. Caution: Before disabling a TrueCopy for z/os option, you must release all affected pairs and MCU-RCU paths. See Discontinuing TrueCopy for z/os Operations for instructions Preparing for TrueCopy for z/os Operations

107 Configuring the MCUs and RCUs for TrueCopy for z/os Operations After you have installed the TrueCopy for z/os hardware and software, you can configure the MCUs and RCUs for TCz operations. Fibre-Channel Interface Configuration To configure the MCUs and RCUs for TCz fibre-channel operations: 1. Identify the volumes that will become the TrueCopy for z/os M-VOLs and R- VOLs. You need to know the storage system S/N, SSID, and CU of each volume, so that you can configure the MCUs and RCUs correctly for your desired pairs and async groups. When you create the pairs, you will need to know the LDEV ID of each volume. 2. At the RCUs (i.e., remote site), use the TrueCopy for z/os software to configure the fibre-channel ports which are connected to the MCUs as RCU target ports (see Figure 3-6). 3. At the main site, connect to and log on to the USP V that you want to configure as a TCz MCU. You must log on with Administrator or TrueCopy for z/os write access, and you must be in Modify mode. 4. Click Go, TrueCopy for z/os(r), and then RCU Operation on the menu bar of the Storage Navigator main window to display the TrueCopy for z/os window (RCU Operation window is displayed). 5. Configure the fibre-channel ports which are connected to the RCUs as initiator ports (see Figure 3-6). 6. Add the desired RCU(s) to each MCU CU, and set the desired RCU options using the Add RCU dialog box (see Figure 3-7) and RCU Option dialog box (see Figure 3-8). Enter the following information on the Add RCU dialog box: RCU S/N = serial number of the RCU LDKC = the number of LDKC which the RCU belongs to (00 or 01). Controller ID = For fibre-channel, the controller ID must be 5 (4 for TagmaStore USP/NSC, 03 for 9900V RCU). Logical Adr. (RCU CU) = RCU CU number (00-FE for USP V, 00-3F for TagmaStore USP/NSC, 00-1F for 9900V) SSID = maximum of four SSIDs per CU with 64 LDEVs per SSID. Note: If only one SSID is specified, there are 256 LDEVs per SSID. Path Gr. ID = path group ID for using CU Free. MCU-RCU path = physical port numbers (1A-2R) for each path (initiator port-to-rcu target port). Preparing for TrueCopy for z/os Operations 3-21

108 7. If you plan to create TCzA pairs with M-VOLs in this MCU, configure the Async options (see Figure 3-9), and add the desired consistency group(s) to the MCU (see Figure 3-10). 8. When you are finished configuring this MCU, exit the TrueCopy for z/os software, and disconnect from the storage system. 9. Repeat steps (3) (8) for each storage system which will function as a TrueCopy MCU. After you have configured the MCUs, added the RCUs, and configured the TrueCopy Async options and consistency groups, you are ready to begin TrueCopy pair operations Preparing for TrueCopy for z/os Operations

109 Figure 3-6 Configuring the RCU Target and Initiator Ports Preparing for TrueCopy for z/os Operations 3-23

110 Figure 3-7 Adding the RCUs Figure 3-8 Configuring the RCU Options 3-24 Preparing for TrueCopy for z/os Operations

111 Figure 3-9 Setting the Async Options Figure 3-10 Adding the Consistency Groups Preparing for TrueCopy for z/os Operations 3-25

112 3-26 Preparing for TrueCopy for z/os Operations

113 4 Using TrueCopy for z/os GUI This chapter describes the TrueCopy for z/os windows on Storage Navigator. Using TrueCopy for z/os GUI 4-1

114 TrueCopy for z/os Windows To open the TrueCopy for z/os windows: 1. Using the USP V Storage Navigator software, connect to and log on to the desired USP V with Administrator access or TrueCopy for z/os write access. 2. On the Storage Navigator main window, select Modify mode to perform TrueCopy for z/os operations. Users in view mode can only view TrueCopy for z/os information. 3. Click Go, TrueCopy for z/os(r), and then the name of the window that you want to open on the menu bar of the Storage Navigator main window. Note: For information and instructions on using the USP V Storage Navigator Java application, please refer to the Storage Navigator User's Guide (MK-96RD621). Note: The storage partition administrator cannot perform the TrueCopy for z/os operations. 4-2 Using TrueCopy for z/os GUI

115 Table 4-1 shows the operations available for each tab. To start the operations that you set on each TrueCopy for z/os function tab, use the Apply button at the lower right of the TrueCopy for z/os window. Table 4-1 TrueCopy Functions Tab Menu Command Description Pair Operation Detailed Information Displays CU information, path information, pair status, and options for TrueCopy for z/os pairs. RCU Operation Asynchronous Operation Add Pair Synchronous Add Pair Asynchronous Delete Pair Suspend Pair Resume Pair Change Pair Option RCU Status RCU Operation Add RCU RCU Operation Change RCU Option RCU Operation Delete RCU Edit SSID(s) & Path(s) Add Path Edit SSID(s) & Path(s) Delete Path Edit SSID(s) & Path(s) Add SSID Edit SSID(s) & Path(s) Delete SSID Port CT Group Operation CT Group Status CT Group Operation Add CT Group CT Group Operation CT Group Option CT Group Operation Delete CT Group Async Option Allows you to create new TrueCopy for z/os Sync pairs. Allows you to create new TrueCopy for z/os Async pairs. Allows you to release TrueCopy for z/os pairs. Allows you to suspend TrueCopy for z/os pairs. Allows you to resynchronize TrueCopy for z/os pairs which are suspended. Allows you to change the TrueCopy for z/os pair options. Displays the RCU status and path status for an RCU. Allows you to add an RCU to the connected storage system. Allows you to change the RCU options. Allows you to delete an RCU. Allows you to add paths to existing RCUs. Allows you to delete paths for existing RCUs. Allows you to add SSIDs to existing RCUs. Allows you to delete SSIDs from existing RCUs. Allows you to change the port types for the connected storage system. Displays information of the consistency groups which are already registered. Allows you to assign the consistency groups to the CUs. Allows you to change the consistency group options. Allows you to delete consistency groups. Allows you to change the Async options. Usage Monitor Allows you to collect I/O statistics using the Remote Copy Monitoring function. Script Operation Allows you to configure and perform scripting operations. History Allows you to view and export the operation history of the TrueCopy for z/os pairs. System Option Clear SIM Allows you to clear the remote copy SIMs. System Option Allows you to change the storage system options.. CU Option Allows you to change the CU Options. Using TrueCopy for z/os GUI 4-3

116 Pair Operation Window The Pair Operation window (see Figure 4-1) displays the TrueCopy for z/os pair information for the connected storage system and allows you to perform all TrueCopy for z/os pair operations. To update the information on the Pair Operation window, click another tab and then click the Pair Operation tab again, or click File, and then Refresh on the menu bar of the Storage Navigator main window. The pair information is also updated when you click the Apply button. Figure 4-1 Pair Operation Window The Pair Operation window presents: Tree: displays the connected storage system, LDKC, CU grouping (grouping each 16 CUs), and the CUs which contain LVIs (CUs without LVIs are not displayed). Select the desired CU to display the LVIs for that CU. You can only select one CU at a time. List: displays the detailed LVI information for the selected item (Subsystem or CU). The LVI information can be sorted by column and in ascending or descending order. Preview List: displays the requested operation(s). You can change or delete the settings from the preview list. 4-4 Using TrueCopy for z/os GUI

117 Display Filter button: opens the Display Filter dialog box, which allows you to control which volumes are displayed in the list by CU, pair type (sync and/or async), volume type (M-VOL and/or R-VOL), CT group, path type, and pair status. Export button: Use this button to write the user-selected TrueCopy for z/os pair status information to a text file. Used Volume: displays the used capacity and the licensed capacity for all pairs and asynchronous pairs. Licensed capacity is enclosed in parenthesis. Note: When the licensed capacity is unlimited, Used Volume displays nothing. The Pair Operation window allows you to perform the TrueCopy for z/os pair operations. All operations performed on the Pair Operation window have a common procedure. To perform any operation on the Pair Operation window: 1. Select the desired CU grouping or the CU in the tree. Note: When a CU grouping is selected, operations for creating pairs cannot be performed. 2. Select the desired LVI(s) or pair(s) in the list. 3. Right-click the selected LVI(s)/pair(s) to display the pop-up menu: Detailed Information: displays the LVI/pair status. Add Pair: allows you to create new pairs (sync or async). Delete Pair: allows you to release pairs. Suspend Pair: allows you to suspend pairs. Resume Pair: allows you to resynchronize pairs. Change Pair Option: allows you to change the pair options. Note: The availability of the commands (enabled/disabled) depends on the status of the LVI(s) or pair(s) selected in the list. 4. Click the command for the desired operation, use the dialog box to perform the operation, and close the dialog box. The preview list now displays the requested operation(s). 5. Verify the specified pair operation(s). Make changes as follows: To change an operation, select the desired operation from the preview list, right-click, click Modify, make the desired changes, and close the dialog box. The preview list displays the updated information. To omit one or more operations, select the operation(s) to be omitted from the preview list, right-click, and click Delete. The operation(s) is/are removed from the list. If all operations are removed, the list returns to its original display. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. All operations are removed, and the list returns to its original display. 6. To start the operation(s), click Apply. Using TrueCopy for z/os GUI 4-5

118 Note: If an error occurs after you click Apply, the preview list displays an error code. To display an error message, select one LU, right-click, and click Error Detail. After you see the error message(s), click OK button to close the error message. 4-6 Using TrueCopy for z/os GUI

119 Volume List The volume list on the Pair Operation window displays detailed information for each volume (LVI) in the selected CU (or entire storage system when the Subsystem is selected). You can sort the LVIs in the volume list by selecting the column heading to sort on. The CU column is selected by default. The screen in Figure 4-2 shows the volume list sorted by CU number in ascending order. To change the sort order (ascending or descending), select the column heading. Note: The number of columns displayed without horizontal scrolling can be changed by adjusting the font size. Figure 4-2 List on the Pair Operation Window The detailed volume (LVI) information includes: Volume icon: Indicates the status of volumes. : Simplex. : M-VOL. : R-VOL. CU and LDEV: CU number and LDEV ID. Note: If "#" is added to the end of the number like 3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. Using TrueCopy for z/os GUI 4-7

120 Status: : Simplex. The volume is not currently assigned to a TCz pair. When the initial copy is started by an add pair operation, the volume status changes to Pending. : Pending. The TCz initial copy operation is in progress. Data on the pair is not fully identical. When the initial copy is complete, the status will change to Duplex. : Duplex. The volume is currently assigned to a TCz pair, and the pair is synchronized. All updates from the host to the M-VOL are duplicated at the R-VOL. : Suspend. The pair has been suspended by the MCU or RCU due to an error condition. The volumes in this pair are not synchronized. : Suspending. TrueCopy for z/os Async only. This pair is not synchronized. This pair is in transition from Duplex or Pending state to the Suspend state. : Deleting. TrueCopy for z/os Async only. This pair is not synchronized. This pair is in transition from the Duplex, Pending, or Suspend state to the Simplex state. Sub: Suspend Sub Status GRP: Consistency time of volume is same as that of the consistency group. VOL: Consistency time of volume is not same as that of the consistency group. OFF: Suspended by the PS OFF by the MCU. S/N and SSID of the other storage system (MCU or RCU) of the pair. LDKC and CU and LDEV: LDKC number, CU number and LDEV ID of the other volume of the pair. Note: If "#" is added to the end of LDEV number (i.e. 3C#), the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. Type: Pair mode: Synchronous or Asynchronous. Fence: The M-VOL fence level of the TCz pair: data, status, or never. Diff: The differential data setting (bitmap table managed by cylinder or track). CTG: Consistency group number (00-7F) of the pair (only for Asynchronous pairs). ErrLvl: Error level (GRP or VOL) of the pair (only for Asynchronous pairs). Sync: Percentage of completion of the copy operation. 4-8 Using TrueCopy for z/os GUI

121 CLPR: The number and name of the CLPR which the volumes forming pairs belong to. For further information on CLPR, please refer to the Virtual Partition Manager User's Guide. Note: The S/N, SSID, and Fence columns can be blank while a TrueCopy pair is in transition to the Simplex status. To display the latest information in these columns, refresh the screen. Display Filter The Display Filter dialog box(see Figure 4-3) allows you to control which volumes are displayed in the list. To open the Display Filter dialog box, click the Display Filter button on the Pair Operation window. Note: You must close the Display Filter dialog box to use other dialog boxes. When a CU is selected, the CU# setting is not available. Figure 4-3 Display Filter Dialog Box Using TrueCopy for z/os GUI 4-9

122 Type: allows you to select the pair type, sync or async (or all types), to be displayed. M-VOL/R-VOL: allows you to select the volume type, M-VOL or R-VOL (or all types), to be displayed. CT Group: allows you to select the consistency group (or all groups) to be displayed. This applies only to Asynchronous pairs. MCU-RCU Path: allows you to select the path type (or all types) to be displayed. At present, you cannot select the path type because the serial interface is not supported. CLPR: allows you to select the CLPR (or all CLPRs). Internal/External VOL: allows you to select the volume type, internal or external (or all types), to be displayed. Status: allows you to display only volumes which have the selected pair status: Simplex, Pending, Duplex, Suspend, Suspending (async only), and/or Deleting (async only). Sub Status: allows you to select the consistency status of the Asynchronous pairs. SEQ(SEQCHK) only: allows you to display only volumes with the SEQCHK status. When this option is selected, TCz Synchronous and simplex volumes are not displayed. The Reset button clears your selections and displays the default settings (ALL). The Set button applies your selections to the volume list and closes the Display Filter dialog box Using TrueCopy for z/os GUI

123 Snapshot Function The TrueCopy for z/os snapshot function writes the user-selected TCz pair status information to a text file on the SVP. The status information reported in this file is determined by the selections on the Display Filter dialog box. You can use this function to verify completion of your TCz operations. Note: You can use the snapshot function only while the client file access is enabled. When the client file access is not enabled, the Export button (a button for snapshot function) is not displayed on the Pair Operation window. For the further information of the client file access settings, please refer to the Storage Navigator User's Guide. Table 4-2 describes the Snapshot function. Figure 4-4 shows an example of a TCz snapshot file. Table 4-2 Snapshot Function Data format Target data Text file. Please refer to the example shown in Figure 4-4. The TrueCopy for z/os pairs to be reported are determined by the selections on the Display Filter dialog box. Termination When Subsystem or LDKC is selected in the tree, you can stop the process by clicking the Cancel button in the dialog box displayed during the execution of the Snapshot function. Initialization Each time the Export command is clicked, the previous status data is deleted and the new data is written. Note: If "#" is added to the end of number for LDEV on the primary site like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. <Pair status at 05/10/ :22:12> Vol Status Sub S/N SSID Vol Type Fence Diff CTG EL Prio Sync CLPR 00:00:00 Simplex : : 00:CLPR0 00:00:01 Duplex :1F:1E Sync(M) Data Cylinder :CLPR1 00:00:02 Suspend GRP :1F:1D Asyn(R) Never Cylinder 0C GRP :CLPR2 (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (1) LDEV number (6) LDEV number of other CU (11) Error level (2) Status of the pair (7) Pair mode (12) Copy priority (3) Suspend sub status (8) Fence Level (13) Pairing progress (%) (4) Other CU S/N (9) Differential data setting (14) CLPR number and CLPR name (5) Other CU SSID (10) Consistency group number Figure 4-4 Example of TrueCopy for z/os Snapshot File To create and export (download) a TrueCopy for z/os snapshot file: 1. After completing the desired TrueCopy for z/os operations, open the Display Filter dialog box, select the desired options, and then close the Display Filter dialog box. Using TrueCopy for z/os GUI 4-11

124 2. Click the Export button at the upper right of the list. When the confirmation message appears, click OK to create a new snapshot file, or click Cancel to cancel your request to create a new snapshot file. 3. If you clicked OK, the TrueCopy for z/os snapshot file is created, and then the dialog box for saving the snapshot file is displayed. 4. To save the snapshot data, enter the desired name for the snapshot file, and click OK button. The completion message of exporting snapshot data is appeared. 5. Click OK to close the message dialog box. RCU Operation Window The RCU Operation window (see Figure 4-5) displays the MCU/RCU and port information and allows you to perform the TrueCopy for z/os RCU and port configuration operations. To update the information on the RCU Operation window: Click another tab and then click the RCU Operation tab again. Click File, and then Refresh on the menu bar of the Storage Navigator main window Click Apply button Select modify mode when you are in view mode. Click RCU Status. Close the RCU Status dialog box. The MCU/RCU or port information is also updated when you click the Apply button Using TrueCopy for z/os GUI

125 Figure 4-5 RCU Operation Window Using TrueCopy for z/os GUI 4-13

126 The RCU Operation window presents: Display buttons: allows you to select either MCU&RCU display (default) or Port display for the RCU Operation window. Tree: When you select the MCU&RCU display with the Display button, the tree displays the CUs of the connected storage system. Select and doubleclick the desired CU to display the MCU/RCU information for that CU. Select the desired RCU to display the SSID and path information for that RCU. You can only select one CU or one RCU at a time. When you select the Port display with the Display button, the tree displays the channel adapters (CHAs) and port types of the connected storage system. Select the Subsystem to display all CHA/port information. Select the desired channel adapter or port type to display the port information for that adapter/port type. You can only select one CHA or port type at a time. List: When you select the MCU&RCU display with the Display button, the list displays the detailed MCU/RCU information for the selected LDKC, for the selected CU grouping, for the selected CU, or for the selected RCU. The MCU/RCU information can be sorted by column and in ascending or descending order. For CUs with more than one MCU-RCU path, each path is displayed in a separate row. When you select the Port display with the Display button, the list displays the detailed port information for the storage system (if selected ) or for the selected channel adapter or port type. The port information can be sorted by column and in ascending or descending order. Preview list: When you select the MCU&RCU display with the Display button, the preview list displays the settings before you click the Apply button for adding or deleting RCU(s), or changing RCU options. To change or delete settings, right-click the preview list. When you select the Port display with the Display button, the preview list displays the settings before you click the Apply button for changing the settings of port(s). To change or delete settings, right-click the preview list. Operation: indicates the current operation performed on the RCU Operation window. Preview: indicates the number of rows in the preview list Using TrueCopy for z/os GUI

127 MCU&RCU Display on the RCU Operation Window When the MCU&RCU button is clicked in the Display box, the RCU Operation window displays the LDKC#, CU grouping, CUs (CU Free and CU#) in the tree in a hierarchical structure, and the MCU/RCU information in the list and the preview list. Only CUs which include active MCUs or RCUs are displayed. Note: LDKC#01 is not available for the current microcode version. When an MCU-RCU path fails, the TrueCopy for z/os software displays an error icon ( ) for the affected CU. Select Subsystem to display all MCU/RCU information (refer to Figure 4-5). Select the desired CU to display the MCU/RCU information for that CU (see Figure 4-6). You can select only one CU at a time. The MCU/RCU information includes: CU: CU number which is selected on the tree view. Type: MCU or RCU. MCU is displayed when the USP V that you are accessing is used as the RCU of the pair. S/N and SSID: Serial number and SSID of the other CU of the pair. LDKC number (with two digits) is also displayed next to the S/N. Paired CU: CU number of the other CU of the pair. M-R Path: Path channel type (fibre) between the other CU of the pair. This column is blank when the connected CU is an MCU. Status: "Normal" indicates no path failure to the RCU. "Failed" indicates that a failure occurs in all paths to the RCUs. "Warning" indicates that a failed path to the RCU exists. This column is blank when the connected CU is an MCU. Num. of Path: Number of paths (blank when the connected CU is an MCU). Double-click the selected CU to display the RCU information for that CU (see Figure 4-7). The Controller ID, model name, RCU serial number, LDKC number, and CU number are displayed next to the RCU icon. You can also double-click an RCU to display the SSID and path information for that RCU in the list (also shown in Figure 4-7). The RCU SSID and path information includes: Item: SSID or path. SSID: SSID of the other CU of the pair. M-R Path: Path channel type between MCU and RCU (fibre). Status: Status of the path. MCU Port: Port number on the MCU side. RCU Port: Port number on the RCU side. Using TrueCopy for z/os GUI 4-15

128 Figure 4-6 MCU&RCU Display on the RCU Operation Window showing CU List 4-16 Using TrueCopy for z/os GUI

129 Figure 4-7 MCU&RCU Display on the RCU Operation Window showing RCU List Port Display on the RCU Operation Window When the Port button is clicked in the Display box, the RCU Operation window displays the channel adapters and port types in the tree and the port information in the List. Select Subsystem to display all port information. Select the desired channel adapter to display the port information for that adapter (see Figure 4-8). Select the desired port type to display the port information for that port type. You can select only one channel adapter or port type at a time. The port information includes: Port: Cluster and port number (CL1-A to CLG-R). Attribute: Port type: initiator, target, RCU target, External, Initiator/External. PCB Mode: Speed mode of the (fibre-channel) port: standard, high speed, or MIX. Using TrueCopy for z/os GUI 4-17

130 Figure 4-8 Port Display on the RCU Operation Window 4-18 Using TrueCopy for z/os GUI

131 Asynchronous Operation Window The Asynchronous Operation window (see Figure 4-9) allows you to perform the TrueCopy for z/os Async configuration operations. To update the information on the Asynchronous Operation window, click another tab and then click the Asynchronous Operation tab again, or click File, and the Refresh on the menu bar of the Storage Navigator main window. The CT group information is also updated when you click the Apply button. Note: The information about a consistency group that is registered from TrueCopy - Mainframe is not shown. Figure 4-9 Asynchronous Operation Window Using TrueCopy for z/os GUI 4-19

132 The Asynchronous Operation window presents: Operation: indicates the current operation performed on the Asynchronous Operation window. Tree: allows you to display all consistency groups (except groups used for TrueCopy) belonging to LDKC#00 (default), or all consistency groups (except groups used for TrueCopy) belonging to LDKC#01. For each LDKC, this tree displays the consistency groups that are already in use (Used), and the consistency groups that are available for use (Not Used). Note: LDKC#01 is not available for the current microcode version. List: displays the following consistency group information: CTG: Consistency group number. This CU: the CU to which the group is registered. MCU: The group was added from the connected CU. RCU: The group was added from the paired CU (connected CU is RCU). M&R: MCU and RCU are in the same storage system. M-R Path: Channel type: fibre. If the consistency group is not in use, this column is blank. Offloading Timer: the time until the TrueCopy for z/os Async recordset is transferred. If the consistency group is not in use, this column is blank. If this CU is RCU, this parameter is invalid, and a hyphen is displayed in this column. Inflow Control: indicates whether the inflow control is enabled or not. If the consistency group is not in use, this column is blank. If this CU is RCU, this parameter is invalid, and a hyphen is displayed in this column. Paired S/N: Serial number of the paired storage system (if there is more than one RCU, the storage system with the lowest S/N is displayed). LDKC number is also displayed next to the S/N. If the consistency group is not in use, this column is blank. Paired SSID: SSID of the paired storage system (if there is more than one RCU, the storage system with the lowest SSID is displayed). If the consistency group is not in use, this column is blank. Other S/N: Exist: indicates that there is more than one RCU for the group. If there is only one RCU, this column is blank. CLPR: the number and name of the CLPR which the volumes forming pairs belong to. If the consistency group is not in use, this column is blank. For further information on CLPR, please refer to the Virtual Partition Manager User's Guide. Preview List: displays the settings before you click the Apply button for changing the settings. To change or delete settings, right-click the preview list. Preview: indicates the number of rows in the preview list Using TrueCopy for z/os GUI

133 Usage Monitor Window The Usage Monitor window (see Figure 4-10) displays the remote copy I/O statistics for all LDEVs to be monitored on the connected storage system, displays the status of remote copy usage monitoring, and allows you to perform the TrueCopy for z/os usage monitor operations. Figure 4-10 Usage Monitor Window Monitoring Switch: allows you to see whether monitoring is on or off. Monitoring Switch displays Enable when monitoring is on; displays Disable when monitoring is off. Note: When monitoring is stopped, the usage monitor graph is closed. The usage monitor graph can only be displayed when monitoring is running. Gathering Interval: allows you to see the data collection interval for usage monitoring. Note: When monitoring is stopped, the default value (1) is displayed in the Gathering Interval box. Update: displays the most recent data sample time of the data on the graph. Graph: displays the remote I/O statistic information and the status of remote copy monitor. Using TrueCopy for z/os GUI 4-21

134 Note: The settings of Usage Monitor is linked up with the settings of the monitoring switch in the Monitoring Options window of Performance Monitor. If you start or stop monitoring, or change the value of Gathering Interval with the Usage Monitor window of TrueCopy for z/os, the status of monitoring or the value of Gathering Interval on the Performance Monitor window is also changed. If the settings of monitoring switch are changed from the Monitoring Options window of Performance Monitor, the settings on the Usage Monitor window of TrueCopy for z/os are automatically changed Using TrueCopy for z/os GUI

135 Script Operation Window The Script Operation window (see Figure 4-11) allows you to perform script operations and displays information on the script being executed. Figure 4-11 Script Operation Window Status: displays the status of script execution. To update the script status information, click File, and then Refresh on the menu bar of the Storage Navigator main window. Stop: a script has not yet been executed, or script execution has been completed. Analyzing: the script analysis operation is running. Running: the script is running. Script File Name: allows you to enter the name of the TCz script file to be executed. The script file name can have up to eight characters, and the file extension must be.spt. Operation: allows you to run/stop the specified script file. The TrueCopy for z/os software must be in Modify mode. Run: Run the TCz script file specified in the Script File Name field. If a script file is currently running, Run cannot be selected. Using TrueCopy for z/os GUI 4-23

136 Stop: Stop the TCz script file being executed. The script operation is stopped on the script line basis. If script execution has been completed, Stop cannot be selected. Result: displays the error code (four-digit hexadecimal number). Information: displays the script information. Message: displayed when script execution has been completed. Normal End indicates that the operation completed normally. When the script ended abnormally due to an error in the script file, a message indicating the abnormal end is displayed. When the script is stopped by the Stop command, Abort by operator is displayed. Date: The date when the script status changed. Line: The script file line number being executed. Loop: The current/total repetition count for a looped command (e.g., 150/300). Macro: The macro being executed. Macros which execute a process for a device are listed: CreateHrcPair, ChangeHrcPair, SuspendHrcPair, ResumeHrcPair, and DeleteHrcPair. File Operation button: allows you to download the trace file and upload the script file. Note: You can perform the file operation only if you can access the local client file in the Storage Navigator computer. If you cannot access the local client file, the File Operation button will not be displayed on the Script Operation window. For further information on the settings for accessing local client files, please refer to the Storage Navigator User's Guide. Apply button: applies settings in the Script Operation window to the storage system. The specified script is executed. Cancel button: cancels the settings in the Script Operation window. The script is not executed Using TrueCopy for z/os GUI

137 History Window The History window (see Figure 4-12) displays the history information for the TrueCopy for z/os pairs and allows you to perform TrueCopy for z/os history operations. The history information includes the records of the main status changes (e.g., pair creation, release, etc.) of the TrueCopy for z/os pairs. To display the latest information on the History window, click File, and then Refresh on the menu bar of the Storage Navigator main window. The latest information on the History window is not displayed by only clicking another tab and then clicking the History tab again. Note: Only when you can access the local file in the Storage Navigator computer, you can download the history file. When you cannot access the local file, the Export button is not displayed on the History window. For further information on the settings for accessing local files, please refer to the Storage Navigator User's Guide (MK-96RD621). Figure 4-12 History Window Using TrueCopy for z/os GUI 4-25

138 The History window presents: Status displays the current status of the history file: No history file exists The history file does not exist. Reading a history file failed A failure occurred during referring to the history file. Updating... n (%) Updating of the history file is now in progress. "n (%)" indicates the progress (in %) of the updating process of the history file. Complete: Updating of the history file has been completed. Note: When the updating process is in progress, the checking process automatically continues until the updating process finishes. The updating process is checked at ten-second intervals. Last Update displays the updated date and time of the history file. The History List displays the history information for the TrueCopy for z/os pairs in the connected storage system. TrueCopy for z/os history information is saved for seven days, and the maximum number of the information that can be saved is 524,288. By default, the list is in the order in which the information are received from the storage system. The information displayed in the History List are: Operation Date/Time: The date and time when the operation was completed. Start Date/Time: The date and time when the operation was started. Operation: The operations are: Pairing Start: Add pair operation was started. Pairing Complete: Add pair operation was completed. Pair Delete: The pair was released. Suspend Operation: Pair suspending operation was performed. Pair Suspend (Failure): The pair was suspended because of a failure. Pair Resync. Start: Resynchronize pair operation was started. Pair Resync. Complete: Resynchronize pair operation was completed. VOL: LDKC number, CU number and LDEV number of the operated volume. Paired VOL: LDKC number, CU number and LDEV number of the paired volume. Copy Time: The time taken for the operation (from the start of the operation to the end). Displayed only for Pairing Complete and Pair Resync. Complete operations. If Operation displays Pairing Complete or Pair Resync. Complete but Copy Time displays nothing, you can check the copy time in the Detailed Information dialog box Using TrueCopy for z/os GUI

139 Note: History information older than seven days is automatically deleted. However, if the number of operations exceeds 524,288, the oldest operations are deleted in chronological order to keep the number at 524,288, even if the operations occurred within the last week. The history file always contains the most recent operations up to a maximum of 65,535 operations. The maintenance information for an entire week may not always be available. Note: The history information can be sorted by column and in ascending or descending order. Note: Even if a suspend-failure occurs in several LDEVs at the same time, only two rows showing "Pair Suspend (Failure)" are displayed. Note: If you select "Report" for Service SIM of Remote Copy on the CU Option dialog box, the history file is not updated until SIMs have been reported to the host. If you click the Clear SIM button before SIMs have not been reported to the host, the history file that has not been reported is deleted. Page displays the page number in the following format: "Currently displayed page number / number of pages" If no history file exists, it will display as "0/0". Previous and Next buttons: The list displays up to a maximum of 16,384 operations at a time. Use these buttons to display the previous or next 16,384 operations. Export button: You can obtain the history file in the CSV file format. Note: Even though the updating process is in progress, you can download the history file, but there is a possibility that the history file is the data before update. We recommend that you obtain the history file when the status is Complete. Note: Only when you can access the local file in the Storage Navigator computer, you can download the history file. When you cannot access the local file, the Export button is not displayed on the History window. For further information on the settings for accessing local files, please refer to the Storage Navigator User's Guide (MK-96RD621). Using TrueCopy for z/os GUI 4-27

140 System Option Window The System Option window (see Figure 4-13) allows you to clear the TrueCopy for z/os remote copy SIMs and to change the option settings of the storage system and CUs. Figure 4-13 System Option Window The Clear SIM button: allows you to clear all remote copy SIMs (service information messages) from the connected storage system. Tree: displays Option at the top of the tree. Subsystem Option and CU Option will be displayed below Option. CU Option will be displayed for each LDKC. List: displays nothing by default. When you select Subsystem Option or CU Option, the option settings will be displayed. Preview List: displays the settings before you click the Apply button for changing or deleting the settings. To change or delete settings, right-click the preview list. Operation: displays the status of the process in progress. The following status of operation is displayed: No Operation 4-28 Using TrueCopy for z/os GUI

141 Set the System Option Set the CU Option Clear SIM Preview: indicates the number of rows in the preview list. The Apply button: applies settings in the System Option window to the storage system. The Cancel button: cancels the settings in the System Option window. Using TrueCopy for z/os GUI 4-29

142 4-30 Using TrueCopy for z/os GUI

143 5 Performing TrueCopy for z/os Configuration Operations This chapter provides instructions for performing TrueCopy for z/os configuration operations. Performing TrueCopy for z/os Configuration Operations 5-1

144 RCU Operations The RCUs are the control units which control the R-VOLs of the TrueCopy for z/os pairs. The RCUs are connected to the MCUs via the remote copy connections and receive and process commands from the MCUs. For TCz operations, the USP V Storage Navigator should be installed on a separate LAN at the remote site to allow TrueCopy for z/os commands to be issued directly to the RCU (e.g., in case of disaster or failure at the primary site). The MCUs are the control units which control the M-VOLs of the pairs. The MCUs receive and process user-requested TrueCopy for z/os commands from the Storage Navigator, and send the remote copy operations to the RCUs. The MCUs can also function as RCUs, provided the remote copy connections are properly configured. The RCU operations are performed separately for each CU of each MCU and RCU to provide maximum flexibility in TrueCopy for z/os configurations. The RCU operations are: Configuring the host interface ports for MCU-RCU connection Adding an RCU Changing the RCU options Adding and deleting logical paths to an RCU Adding and deleting SSIDs for an RCU Viewing RCU status Deleting an RCU The RCU Operation window allows you to perform the RCU operations. All operations performed on the RCU Operation window have a common procedure. 5-2 Performing TrueCopy for z/os Configuration Operations

145 To perform any operation on the RCU Operation window: 1. Click the desired display mode: MCU&RCU, or Port. 2. Select the desired CU, or channel adapter from the tree. 3. Select the desired RCU(s) or port(s) from the list. When adding an RCU, do not select anything from the list. 4. Right-click the selected item(s) to display the pop-up menu. For the MCU&RCU display, the pop-up menu commands are: RCU Status: allows you to display the RCU status. RCU Operation: allows you to perform the following RCU operations: add RCU, change RCU option, and delete RCU. Edit SSID(s) & Path(s): allows you to add and delete paths, and allows you to add and delete SSIDs. For the Port display, the pop-up menu commands are: Initiator: allows you to change the selected fibre port(s) to initiator ports. RCU Target: allows you to change the selected fibre port(s) to RCU targets. Target: allows you to change the selected fibre port(s) to target ports. 5. For the MCU&RCU display, click the menu command for the desired operation. When two or more RCUs are selected, only the RCU Operation command is available. For the add and change operations, use the dialog box to perform the operation, and click Set to close the dialog box. There is no dialog box for the delete operations. The RCU Operation preview list now displays the requested operation(s). To cancel the add or change operations, click Cancel. For the Port display, select the desired port type. The RCU Operation preview list displays the requested port change operation(s). 6. Verify the specified RCU or port operation(s) in the preview list. Make changes as follows: a. For the MCU & RCU display, to change an operation, select the desired operation (RCU, path, SSID), right-click it, click Modify, make the desired changes, and close the dialog box. The preview list displays the updated information. For the Port display, to change the port type, select the desired port, right-click it, and select the desired port type. The preview list displays the updated information. b. To omit one or more operations, select the operation(s) to be omitted (RCU, path, SSID, port), right-click, and click Delete. The operation(s) is/are removed from the preview list. If all operations are removed, the list returns to its original display. Performing TrueCopy for z/os Configuration Operations 5-3

146 c. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. All operations are removed, and the list returns to its original display. 7. To start the operation(s), click Apply. 5-4 Performing TrueCopy for z/os Configuration Operations

147 Configuring the Host Interface Ports TrueCopy for z/os software allows you to change the configuration of the USP V host interface ports as needed to accommodate the desired host and TrueCopy for z/os communications paths. The USP V fibre-channel interface ports can be configured as target ports (default), initiator ports, or RCU target ports. Target: The fibre-channel ports which will be connected to the host must be configured as target ports (default). Target mode is used for host processor channel interface. Initiator: The fibre-channel ports which will be used for TCz communications to the RCUs must be configured as initiator ports. Initiator mode emulates a host channel to enable the MCU to send write I/O operations directly to the RCU target port. Note: Two or more initiator ports must be configured before you can add the RCUs and create the TrueCopy for z/os pairs. RCU target: The fibre-channel ports in the RCU that will be used to communicate with the MCUs must be configured as RCU target ports. External: This attribute can be set by the Universal Volume Manager software. The external port is used for Universal Volume Manager, not TrueCopy for z/os. To use this port for TrueCopy for z/os, please change the attribute to the initiator, RCU target or target port. Initiator/External: This setting shows the combination of ports that have an initiator port and an external port attributes. Only port that has an initiator port attribute within these ports can be used for TrueCopy for z/os. This attribute cannot be changed by the TrueCopy for z/os software. For details on the port to which an initiator/external mix mode is set, please refer to the Universal Volume Manager User's Guide. Note: The port assigned to SLPR other than SLPR0 can be set to the Target port attribute only. Performing TrueCopy for z/os Configuration Operations 5-5

148 WARNING: Before changing a fibre-channel port to an initiator port, disconnect the port from the host, release all affected TrueCopy for z/os pairs, delete all paths from the port to the MCU (if RCU target), and then remove all channel paths to the port. WARNING: Before changing a fibre-channel port from initiator to target or RCU target, release all affected TrueCopy for z/os pairs, delete all paths from the initiator port to the RCU, and then delete the RCU from the MCU. Caution: Limit the number of hosts connected to an RCU target port to 128 or fewer to avoid mistaken disconnection. If more than 128 hosts are connected to an ordinary target, some hosts may be disconnected after changing the type from target to RCU target. To configure the USP V fibre-channel ports: 1. click the RCU Operation tab, and click the Port display button to display the channel adapters and port types for the connected storage system in the tree. 2. Select the desired channel adapter to display only the ports for that channel adapter. Select the desired port type to display all ports of the selected type. 3. Select the port(s) that you want to configure. Make sure to select only fibre ports. 4. Right-click the selected port(s), and then select the desired port type: initiator, RCU target, or target for fibre channel. "Modified" is displayed on the rightmost column of the selected port. The preview list displays the updated information. 5. Verify the requested port change operation(s) displayed in the lists. To change one or more port operations, select the operation(s), right-click the upper list, and select the desired port type. To remove one or more operations, select the operation(s), right-click the preview list, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. WARNING: Read and follow the important warnings and caution above before starting the port change operations. 6. To start the operation(s), click Apply. 5-6 Performing TrueCopy for z/os Configuration Operations

149 Adding an RCU You can add up to four RCUs to each MCU and establish up to eight paths to each RCU. You must add each CU as a separate RCU to each CU of the MCU. The logical paths are established for the CUs of the MCU and RCU separately. The maximum number of logical paths for each MCU is 32 (8 paths per RCU 4 RCUs per MCU). The remote copy connections and MCU ports must be properly installed and configured before you can add an RCU. When you add an RCU, the selected CU of the connected MCU adds the specified CU as a TrueCopy for z/os RCU and establishes the specified number of logical paths to the RCU. After you have added an RCU (and path status is normal), you can create TrueCopy for z/os pairs which have R-VOLs in the newly added RCU. The Add RCU dialog box (see Figure 5-1) allows you to add an RCU to the selected CU of the connected MCU. To open the Add RCU dialog box, select the MCU&RCU display on the RCU Operation window, select the desired CU in the tree, right-click the list, click the RCU Operation command, click the Add RCU command, and then click the Add RCU (Fibre) command. Performing TrueCopy for z/os Configuration Operations 5-7

150 Figure 5-1 Add RCU Dialog Box 5-8 Performing TrueCopy for z/os Configuration Operations

151 RCU S/N: allows you to enter the five-digit serial number of the RCU being added. LDKC: allows you to enter the LDKC number which the RCU belongs to. Specify 00 or 01. Note: You can specify only 00 for the current microcode version. Controller ID: allows you to select the controller ID (storage system family ID) of the RCU being added from the drop-down list. The controller ID for USP V is 5, the controller ID for TagmaStore USP/NSC is 4, and the controller ID for a 9900V RCU is 3. Logical Adr. (RCU CU): allows you to enter the CU number of the RCU being added. The CU number differs by the specified controller ID as follows: When the specified controller ID is 5 (USP V), you can select a CU number from 0 to FE. When the specified controller ID is 4 (TagmaStore USP/NSC), you can select a CU number from 0 to 3F. When the specified controller ID is 3 (9900V), you can select a CU number from 0 to 1F. SSID: allows you to enter the SSID(s) of the RCU being added. USP V uses one SSID for each set of 256 volumes and one SSID for each set of 64 volumes or four SSIDs per CU. SSID is 4-FFFF (hexadecimal). MCU-RCU Path: displays different boxes depending on the channel interface type (fibre). MCU Port: allows you to select the MCU port number from the drop-down list or to enter the port number directly. Initiator ports are listed. RCU Port: allows you to select the RCU port number from the drop-down list or to enter the port number directly. You must select RCU target ports. Note: You can specify the port number with two characters. For instance, you can abbreviate CL1-A to 1A. You can also enter the port number in both lowercase and uppercase characters. The Option button opens the RCU Option dialog box. The Cancel button cancels the settings you made on the Add RCU dialog box and closes the dialog box. To add an RCU to the connected MCU: 1. Make sure the remote copy connections and ports are properly configured. Get the S/N and SSID(s) for the desired CU of the RCU. The add RCU operation will fail without this information. The USP V storage system should have a label or tag indicating its S/N and SSIDs, or ask your Hitachi representative for the RCU S/N and SSIDs. 2. Click the RCU Operation tab, click the MCU&RCU display button, and select the desired CU in the tree. You must add RCUs to each CU separately. Performing TrueCopy for z/os Configuration Operations 5-9

152 3. Right-click the list (an RCU does not have to be selected), click RCU Operation, and click Add RCU to open the Add RCU dialog box (refer to Figure 5-1). 4. On the Add RCU dialog box, enter the S/N, LDKC number, controller ID (5 for USP V, 4 for TagmaStore USP/NSC, 3 for 9900V), CU number, and SSID(s) for the desired RCU CU. The MCU verifies the S/N when the paths are established, and verifies the SSIDs when the pairs are created. If desired, you can add and delete SSIDs later using the Add SSID dialog box. 5. Select the MCU port and RCU port (for fibre). The MCU will not allow you to establish less than the minimum number of paths as specified on the RCU Option dialog box. If desired, you can add and delete paths later using the Add Path dialog box. 6. Click the Option button to open the RCU Option dialog box, and enter the desired settings for the TrueCopy for z/os RCU options. Note: When you have TrueCopy for z/os Async pairs configured on fibrechannel interface, set the same value for the Minimum Paths option for all RCUs. 7. Click Set to close the RCU Option dialog box, even if you made no changes. (Click Cancel to cancel the add RCU operations.) The preview list now displays the requested add RCU operation(s). 8. Verify the requested operation(s) displayed in the preview list. To change one or more operations, select the operation(s), right-click the preview list, and click Modify. To remove one or more operations, select the operation(s), right-click the preview list, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 9. To start the operation(s), click Apply. The changes that you set are reflected in the upper list on the window. The preview list is cleared. If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed on the Error Code column in the preview list. To display the error message, rightclick the preview list and click Error Detail command. If some errors occur simultaneously, the error messages are displayed at the same time. Click the Apply button again Performing TrueCopy for z/os Configuration Operations

153 RCU Path Parameters For fibre-channel interface, two types of PCB mode settings are provided: Standard and High. Therefore, when you configure paths among the initiator ports, target ports, and RCU target ports, please study the port modes and specify the correct mode for each port. For details on the relationship between ports and PCB modes and instructions for setting the PCB mode, please refer to the LUN Manager User s Guide (MK-96RD615). Figure 5-2 shows a sample TrueCopy for z/os fibre-channel interface configuration with connections going through switches and the TrueCopy for z/os Add RCU window used to define this configuration. Performing TrueCopy for z/os Configuration Operations 5-11

154 Switch Switch : FL-Port Connection : Fibre Channel Interface Port Switch Switch 1C 2C 1D 2D 2E SSID: 0244 Serial #: MCU SSID: 0088 Serial #: RCU Add RCU RCU S# = 05031, SSID = 0088, No. of Paths = 3 For path 1: MCU Port = 1C, RCU Port = 2D, Logical Adr = 00 For path 2: MCU Port = 1C, RCU Port = 2E, Logical Adr = 00 For path 3: MCU Port = 2C, RCU Port = 1D, Logical Adr = 00 Figure 5-2 Add RCU Operation 5-12 Performing TrueCopy for z/os Configuration Operations

155 Changing the RCU Options The RCU Option dialog box (see Figure 5-3) allows you to set the RCU options for the connected MCU. The RCU options apply to all MCU CUs and to all RCUs connected to the MCU. The RCU Option dialog box is presented during the add RCU process, and can also be opened by right-clicking on the RCUs and clicking the RCU Operation Change RCU Option command. Figure 5-3 RCU Option Dialog Box The Minimum Paths option allows you to specify the minimum number of paths required for each RCU connected to the current MCU (default = 1). If you enter a larger number than the number of paths already set on the Add RCU dialog box, or if the number of paths falls below this number (e.g., failed path), an error occurs. When the error occurs, the MCU suspends all affected TrueCopy for z/os (and TrueCopy) pairs to prevent remote copy operations from adversely affecting performance due to the inadequate number of paths. If the MCU contains TrueCopy for z/os pairs which contain critical data for disaster recovery, set the minimum number of paths to one, so that TrueCopy for z/os operations continue even if there is only one path to an RCU. If you need high performance at the MCU, set the minimum number of paths to two or more (up to eight per CU), depending on the number of pairs managed by the MCU. Note: When you have TrueCopy for z/os Async pairs configured on fibrechannel interface, set the same value for the Minimum Paths option for all RCUs. Note: The RCU options are common to both TrueCopy for z/os and TrueCopy operations. The most recently entered Minimum Paths value (entered on TrueCopy for z/os or TrueCopy RCU Option dialog box) will be applied to both TrueCopy for z/os and TrueCopy operations. Performing TrueCopy for z/os Configuration Operations 5-13

156 Caution: If TrueCopy for z/os pairs are suspended because the number of paths has dropped below this setting, the M-VOL fence level pair option determines whether the TrueCopy for z/os Sync M-VOLs are fenced (i.e., reject all write operations). The RIO MIH Time setting specifies the time value for the remote I/O (RIO) missing interrupt handler (MIH), which is the wait time until data transfer from the MCU to RCU is complete. The RIO MIH time value must be from 10 to 100 seconds. The default setting is 15 seconds. The Incident of RCU option allows you to specify which host(s) the RCUs will report link incident records to. When to any host is selected, the RCUs will send link incident records to all RCU hosts and to all MCU hosts. When only to RCU host is selected, the RCUs send link incident records only to the RCU host(s). Make sure that RCU link incidents are reported to the proper host(s) so that corrective action, if needed, can be taken. The to any host setting is recommended when TCz is being used for disaster recovery purposes. The FREEZE Option setting allows you to enable or disable support for the CGROUP (FREEZE/ RUN) PPRC TSO command. The FREEZE option is available only when PPRC support = Yes. If you select Enable, the MCU will accept and perform the CGROUP command. If you select Disable, the MCU will reject the CGROUP command. Note: Enable the FREEZE option only after all MCU-RCU paths have been added. Note: The PPRC commands do not allow you to change the RCU options. The Round Trip Time setting is used for Initial Copy operations. This setting gives a priority to a remote I/O for an update copy operation. When an Initial Copy operation is in progress, the copy pace is automatically adjusted based on the value (the actual time required for the initial copy), which can be obtained by subtracting the specified Round Trip time (obtained using the formula below) from the remote I/O response time. The actual time required for the initial copy operation is large, it means that the workload of the update copy is relatively high. Therefore, the copy pace of the initial copy will be slowed. When the time is relatively small, the copy pace will speed up to the specified value. In this way, we can curb the influence of the exclusive line use in the initial copy operation on the host performance. Note: This option is available only in the case of TCz pairs (In the case of TCzA pairs, this option value is invalid) Performing TrueCopy for z/os Configuration Operations

157 The default value of Round Trip Time is 1 ms. You may specify 1 ms to 500 ms. You can use the following formula to figure out the Round Trip Time. Round Trip time = Round Trip Time between MCU-RCU x 2 (*) + Initial Copy response time (ms) (*) A data transfer between MCU and RCU involves two response sequences in one command issuance. Therefore, you need to double the Round Trip Time between MCU-RCU. For Round Trip Time between MCU and RCU, please ask your carrier, or use a ping command and etc. to measure the time. If you do not use lines etc. between MCU and RCU, specify 1. Initial Copy response time is the response time required for multiple initial copy operations. You can use the following formula to get the Initial Copy response time. To get the time, you should use the following values: the initial copy pace, the max number of maximum initial copy VOLs, the speed of the line between MCU and RCU, and the number of lines. Initial Copy response time (ms) = (1[MB] / Speed of line between MCU- RCU[MB/ms] (*1) ) x ( initial copy pace (*2) / 15) x ( max number of maximum initial copy VOLs (*3) / Number of lines between MCU-RCU (*4) ) (*1) When you connect MCU with RCU without lines etc., specify 0.17[MB/ms] in Speed of line between MCU and RCU. (*2) For initial copy pace in the formula above, see Table 5-1. (*3) For the maximum number of maximum initial copy volumes, use the value set up per disk subsystem. The default is 64. (*4) Even if Max number of maximum initial copy VOLs / Number of lines between MCU-RCU is larger than 16, specify Max number of maximum initial copy VOLs / Number of lines between MCU-RCU as 16. Table 5-1 Initial Copy Pace for Calculating The Initial Copy Response Time Operation Perform Initial Copy Only Perform Initial Copy and Update Copy at a Time Initial Copy Pace Specified at the Time of Pair Creation is 1 to 8 Initial Copy Pace Specified at the Time of Pair Creation 9 to 15 Storage Navigator Initial copy pace specified at the time of pair creation Initial copy pace specified at the time of pair creation 8 Business Continuity Manager Initial copy pace specified at the time of pair creation Initial copy pace specified at the time of pair creation 8 PPRC command (TSO/ICKDSF) and CU emulation type=3990 Initial copy pace specified at the time of pair creation Initial copy pace specified at the time of pair creation 8 Performing TrueCopy for z/os Configuration Operations 5-15

158 PPRC command (TSO/ICKDSF) CU emulation type=2105 or (*) 8 (*) (*) When a PPRC command (TSO/ICKDSF) is used and the CU emulation type is 2105 or 2107, the initial copy pace specified is invalid. Therefore, the fixed value will be set. Table 5-2 Example setting Round Trip Time [ms] Line Speed b/w MCU/RCU [MB/ms] Number of Lines b/w MCU/RCU Initial Copy Pace Max. Number of maximum Initial Copy VOLs Round Trip Time Specified [ms] The Cancel button cancels the settings you have made and closes the RCU Option dialog box. The Set button sets the parameters and closes the RCU Option dialog box. To users who use the TagmaStore USP/NSC or Lightning 9900V series storage system: To set the following parameters, use the System Option window. Maximum Initial Copy Activities Path Blockade Watch SCP Delay Time PPRC Support by host Service SIM of Remote Copy To change the RCU options: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select and right-click the desired RCU in the list, click RCU Operation, and click Change RCU Option to open the RCU Option dialog box (refer to Figure 5-3). 3. On the RCU Option dialog box, change the RCU options as desired, and click Set to close the RCU Option dialog box (or click Cancel to cancel the RCU option operation). The preview list displays the requested change RCU option operation. 4. Verify the requested operation(s) displayed in the preview list Performing TrueCopy for z/os Configuration Operations

159 To change the change RCU option operation, select the operation from the preview list, right-click, and click Modify. To remove the operation, select it, right-click and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 5. To apply the settings, click Apply. Performing TrueCopy for z/os Configuration Operations 5-17

160 Adding and Deleting Logical Paths to an RCU Before adding a path to an RCU, make sure that the remote copy connection is properly installed, the appropriate MCU ports are configured as initiator ports, and the appropriate MCU CU is selected. You can add up to four RCUs to each MCU CU and establish up to eight paths to each RCU. When you add a path to an RCU, TrueCopy for z/os will automatically start using the new path to perform copy activities. The Add Path dialog box (see Figure 5-4) allows you to add one or more paths to an existing RCU. To open the Add Path dialog box, select the MCU&RCU display on the RCU Operation window, select and double-click the desired MCU CU in the tree, select the desired RCU, right-click the SSID and path list, and then click the Add Path command. Figure 5-4 Add Path Dialog Box (Fibre) MCU Port: allows you to select the MCU port number from the drop-down list or to enter the port number directly. Initiator ports are listed. RCU Port: allows you to select the RCU port number from the drop-down list or to enter the port number directly. You must select an RCU target port Performing TrueCopy for z/os Configuration Operations

161 Note: The number of enabled fields indicates the number of paths that can be added. Note: You can specify the port number with two characters. For instance, you can abbreviate CL1-A to 1A. You can also enter the port number in both lowercase and uppercase characters. To add one or more new logical paths from the connected MCU to an existing RCU: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select and double-click the desired MCU CU in the tree, and select the RCU to which you want to add one or more paths. Alternatively, select the RCU in the list, right-click, and click Edit SSID(s) & Path(s). All paths to the selected RCU are listed. 3. Right-click the path and SSID list, and click Add Path to open the Add Path dialog box. 4. On the Add Path dialog box, enter the new path(s). 5. Click Set to close the Add Path dialog box. The preview list now displays the requested add path operation(s). 6. Verify the requested operation(s) displayed in the preview list. To change the add path operation, select the operation from the preview list, right-click, and click Modify. To remove the operation, select the operation, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 7. To start the operation(s), click Apply. The MCU will automatically begin using the new logical path for TrueCopy for z/os activities. Before deleting a path to an RCU, make sure that the remaining number of paths will be equal to or greater than the minimum number of paths setting (on the RCU Option dialog box). The delete path operation will fail if the number of remaining paths is less than the minimum number of paths. Performing TrueCopy for z/os Configuration Operations 5-19

162 The Delete Path command allows you to delete a path to an existing RCU. To delete one or more paths from the connected MCU to an existing RCU: 1. Open the RCU Option dialog box, and check the Minimum Paths setting. If the remaining number of paths will be less than this value, the delete path operation will fail. If needed, change the Minimum Paths RCU option so that you can delete the desired path. 2. Click the RCU Operation tab, and click the MCU&RCU display button. 3. Select and double-click the desired MCU CU in the tree, and select the RCU for which you want to delete path(s). Alternatively, select the RCU in the list, right-click and click Edit SSID(s) & Path(s). All paths to the selected RCU are listed. 4. Right-click the path(s) that you want to delete, and click Delete Path. When the confirmation message appears, click OK to delete the path(s), or click Cancel to cancel your request to delete it/them. The preview list displays the path(s) that you want to delete. "Delete" is displayed on the rightmost column of the selected path in the SSID/Path list. 5. Verify the requested operation(s) displayed in the preview list and the SSID/Path list. To remove an operation, select the operation, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, rightclick, and click the Delete command, or click the Cancel button. 6. To start the operation(s), click Apply Performing TrueCopy for z/os Configuration Operations

163 Adding and Deleting SSIDs for an RCU Before adding an SSID, make sure that the remote copy connection is properly installed. You can add three SSIDs to each RCU. Before deleting an SSID, make sure that the remaining SSIDs are still valid, or the connection between the MCU and RCU may be lost. The Add SSID dialog box (see Figure 5-5) allows you to add up to three SSIDs to an existing RCU. To open the Add SSID dialog box, select the MCU&RCU display on the RCU Operation window, select and double-click the desired MCU CU in the tree, select the desired RCU, right-click the SSID and path list, and then click the Add SSID command. Figure 5-5 Add SSID Dialog Box To add one or more SSIDs to an existing RCU: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select and double-click the desired MCU CU in the tree, and select the RCU to which you want to add SSID(s). Alternatively, select the RCU in the list, right-click and click Edit SSID(s) & Path(s). All SSIDs for the selected RCU are listed. 3. Right-click the SSID and path list, and then click Add SSID to open the Add SSID dialog box. 4. On the Add SSID dialog box, enter the new SSID(s). 5. Click Set to close the Add SSID dialog box. The preview list now displays the requested add SSID operation(s). 6. Verify the requested operation(s) displayed in the preview list. Performing TrueCopy for z/os Configuration Operations 5-21

164 To change the add SSID operation, select the operation, right-click, and click Modify. To remove the operation, select the operation from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 7. To start the operation(s), click Apply Performing TrueCopy for z/os Configuration Operations

165 Before deleting an SSID, make sure that all affected TrueCopy for z/os pairs (pairs having R-VOLs in the RCU SSID to be deleted) have already been released. If all affected pairs have not been released, the MCU will reject the delete SSID operation to prevent accidental release of TrueCopy for z/os pairs. The Delete SSID command allows you to delete an SSID from an existing RCU. To delete one or more SSIDs from an existing RCU: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select and double-click the desired MCU CU in the tree, and then select the RCU for which you want to delete the SSID(s). Alternatively, select the RCU from the list, right-click, and click Edit SSID(s) & Paths. All SSIDs for the selected RCU are listed. 3. Right-click the SSID that you want to delete, and then click Delete SSID. When the confirmation message appears, click OK to delete SSID, or click Cancel to cancel your request to delete SSID. The preview list now displays the requested delete SSID operation(s). "Delete" is displayed on the rightmost column of the selected SSID in the path/ssid list. 4. Verify the requested operation(s) displayed in the preview list. To remove an operation, select the operation from the preview list, rightclick, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 5. To start the operation(s), click Apply. To cancel the operation and return the lists to their original display, click Cancel. Performing TrueCopy for z/os Configuration Operations 5-23

166 Viewing RCU Status The RCU Status dialog box (see Figure 5-6) displays the detailed status information for the selected RCU Performing TrueCopy for z/os Configuration Operations

167 Table 5-3 describes the path status descriptions. To view the detailed RCU status information: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select the RCU for which you want to display the status in the list. You can only view status for one RCU at a time. 3. Right-click the RCU, and click RCU Status to open the RCU Status dialog box. Figure 5-6 RCU Status Dialog Box Performing TrueCopy for z/os Configuration Operations 5-25

168 Path List: No.: Path number (path list item number). Path Status: Path status Performing TrueCopy for z/os Configuration Operations

169 Table 5-3 describes the path status descriptions. MCU Port number and RCU Port number. RCU S/N: Serial number of the RCU. LDKC number is displayed enclosed in parentheses to the right of the RCU S/N. Controller ID: Controller ID and model name. SSID: SSID(s) of the RCU. RCU CU No.: CU number of the RCU. MCU-RCU Path: Type of channel interface between the storage systems (fibre). Minimum Paths: Minimum number of MCU-RCU paths for the selected RCU. Incident: The host(s) to which the RCUs will report link incident records. RIO MIH Time: Time value for the remote I/O (RIO) missing interrupt handler (MIH), which is the wait time until data transfer from the MCU to RCU is complete. RCU Registered: Date and time when the RCU was added. Last Updated: Date and time when the RCU was last updated. FREEZE Option: Support for the CGROUP (FREEZE/ RUN) PPRC TSO command. Round Trip Time: Delay time because of remote I/O according to the connection devices and the distance of line between MCU and RCU. Check box, "Refresh the RCU Operation window after this dialog box is closed": To refresh the RCU Operation window after closing the RCU Status dialog box, click the check box. By default, the check box is not selected. The Refresh button refreshes the status information. The Close button closes the RCU Status dialog box. Performing TrueCopy for z/os Configuration Operations 5-27

170 Table 5-3 Logical Path Status Status Description Normal Initialization Failed Communication Timeout Resource Shortage Serial Number Mismatch Invalid Port RCU Port Number Mismatch RCU Port Type Mismatch Communication Failed Logical Blockade Program Error Condition This path has been successfully established and can be used for TCz remote copy activities. The link initialization procedure with the RCU has failed, because either the physical path connection between the MCU and the RCU or the connection between the MCU and the host was missing. A timeout error has occurred between the MCU and RCU. The establish logical path link function has been rejected by the RCU. All logical path resources in the RCU might be used for other connections. The serial number of the control unit which is connected to this logical path does not match the serial number specified by the Add RCU dialog box. The interface port specified is not in the initiator mode. There are three possible factors: The specified port in the RCU is physically disconnected from the MCU. The port is not configured as an RCU target port. The specified port number is not available. The microprogram at the RCU side does not support the fibre remote copy function. Or the specified port type is not RCU target. A timeout error has occurred on the fibre path between MCU and RCU. This logical path was blockaded because a path error or a link error had occurred continuously. This logical path was blockaded because a program error had occurred Performing TrueCopy for z/os Configuration Operations

171 Deleting an RCU You can delete an RCU from an MCU only after all TrueCopy for z/os pairs between the MCU CU and RCU CU have been released. When you delete an RCU from an MCU, the MCU deletes all logical paths from the current MCU CU to the selected RCU CU. Deleting an RCU does not affect the TrueCopy for z/os operations between the other MCU CUs and that RCU. After an RCU has been deleted, you can reconfigure the remote copy connections to add another RCU to the MCU, or you can remove the remote copy connections and reconfigure the MCU ports (initiator ports to ordinary target ports for fibre) to provide additional host channels for the MCU. Note: If all affected TrueCopy for z/os pairs have not been released, the MCU will reject the delete RCU operation to prevent accidental release of TrueCopy for z/os pairs. The RCU Operation Delete RCU command allows you to delete an RCU from an MCU CU. The MCU will not allow you to delete an RCU which still has pairs with the MCU. To delete one or more RCUs from an MCU CU: 1. Make sure that all affected TrueCopy for z/os pairs have been released. 2. Click the RCU Operation tab, and click the MCU&RCU display button. 3. Click the RCU(s) that you want to delete on the RCU list. 4. Right-click the RCU(s), click RCU Operation, and then click Delete RCU. When the confirmation message appears, click OK to delete RCU, or click Cancel to cancel your request to delete RCU. The preview list displays the requested delete RCU operation(s). 5. Verify the requested operation(s) displayed in the preview list. To remove one or more operations, select the operation(s) from the preview list, rightclick, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 6. To delete the RCU(s), click Apply. Performing TrueCopy for z/os Configuration Operations 5-29

172 Asynchronous Operations The TrueCopy for z/os Async operations include: Setting the asynchronous copy options. Adding consistency (CT) groups Changing the consistency group options Viewing consistency group status Deleting consistency groups The Asynchronous Operation window allows you to perform the asynchronous operations. All operations performed on the Asynchronous Operation window have a common procedure. To perform any operation on the Asynchronous Operation window: 1. Select the LDKC where the desired consistency group belongs, or select Used or Not Used from the tree in the Asynchronous Operation tab. 2. Select the desired consistency group(s) in the tree. 3. Right-click the selected item(s) to display the pop-up menu: Async Option: allows you to set the parameters per CLPR for asynchronous copy operations. For further information on CLPR, please refer to the Virtual Partition Manager User's Guide. CT Group Operation: allows you to perform the following operations: add CT group, change CT group option, view CT group status, and delete CT group. 4. Click the command for the desired operation, use the dialog box to perform the operation, and close the dialog box. There is no dialog box for the delete CT group operation. The preview list now displays the requested operation(s). 5. Verify the specified asynchronous operation(s). Make changes as follows: To change an operation, select the desired operation from the preview list, right-click, click Modify, make the desired changes, and close the dialog box. The preview list displays the updated information. To omit one or more operations, select the operation(s) to be omitted from the preview list, right-click, and click Delete. The operation(s) is/are removed from the preview list. If all operations are removed, the list returns to its original display. To cancel all operations, select all the operations in the preview list, rightclick, and click the Delete command, or click the Cancel button. 6. To start the operation(s), click Apply Performing TrueCopy for z/os Configuration Operations

173 Setting the Asynchronous Copy Options The Async Option dialog box (see Figure 5-7) allows you to set and modify the TrueCopy for z/os Async copy option parameters for the connected storage system. To open the Async Option dialog box, right-click the CT groups and click the Async Option command. The async options apply to the entire physical control unit, including all TrueCopy for z/os M-VOLs and R-VOLs behind the control unit. The async options can only be modified when no TrueCopy Async pairs or groups exist in the connected CU (M-VOLs or R-VOLs). Figure 5-7 Async Option Dialog Box The CLPR(#) drop-down list allows you to specify CLPR ID. The default setting is 00. The Pending Update Data Rate (%) option allows you to specify the TrueCopy for z/os Async (and TrueCopy Async) sidefile threshold, which is the maximum amount of cache that can be used for storing TrueCopy for z/os (and TrueCopy) Async recordsets (sidefiles). You can select any value between 30% and 70% (10% increments). For further information on sidefile inflow control. Note: The current pending update data rate is common to both TrueCopy for z/os and TrueCopy operations. The most recently entered value (on the TrueCopy for z/os or TrueCopy Async Option dialog box) will be applied to all TrueCopy for z/os Async operations. Performing TrueCopy for z/os Configuration Operations 5-31

174 To set the async options: 1. Click the Asynchronous Operation tab. You do not need to select anything in the tree. 2. Right-click the CT group list (you do not need to select anything), and click Async Option to open the Async Option dialog box (refer to Figure 5-7). The async options can only be modified when no TrueCopy for z/os Async pairs or groups exist in the connected CU (M-VOLs or R-VOLs). 3. On the Async Option dialog box, select the desired parameters. For further information on the asynchronous copy options. 4. Click Set to close the Async Option dialog box. (Click Cancel to cancel the async option operation.) The preview list displays the requested async option operation. 5. Verify the requested operation displayed in the preview list. To change the async option operation, select the operation from the preview list, right-click, and click Modify. To remove the operation, select it from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 6. To apply the settings, click Apply Performing TrueCopy for z/os Configuration Operations

175 Adding Consistency Groups The Add CT Group dialog box (see Figure 5-8) allows you to add consistency groups and select the options for the new groups. To open the Add CT Group dialog box, click the Asynchronous Operation tab, select Display All or Not Used in the tree, select the group(s) to be added, right-click the group(s), click CT Group Operation, and click Add CT Group. Figure 5-8 Add CT Group Dialog Box Timer Type: allows you to select the timer type option for the group: System = system timer (CPU TOD clock) provided by the I/O time-stamping function Local = local timer (internal MCU TOD clock) None = system timer (CPU TOD clock) provided by the I/O time-stamping function. This timer type should only be selected when establishing TCzA pairs in the reverse direction (to copy from the secondary site back to the primary site). When None is selected, the MCU still acquires the time-stamp information from the host I/O time-stamping function. MCU-RCU Path: indicates the path type (fibre) for the remote copy connections. Currently, you can not change the path type. Offloading Timer (min.): allows you to specify the amount of time for monitoring to transfer data to a sidefile between 0 and 20 minutes in one second increment. The default setting is 5 minutes. Performing TrueCopy for z/os Configuration Operations 5-33

176 Enable Inflow Control: allows you to enable the inflow control. To enable the inflow control, click the check box. By default, the check box is selected. Before changing this option, you should release or suspend pairs in the selected consistency group. Note: If you use Business Continuity Manager, please refer to the Business Continuity Manager User s Guide and see explanations about Set Copy Group Attributes and FLOW CTL. If you use PPRC, please refer to information about NO DELAY options that are available in PPRC operations. Time Out (Copy Pending) (min.): allows you to select the maximum delay allowed for TrueCopy for z/os Async copy (none or from 3 to 15 min., none = 0 min.). The default setting is five minutes. If the delay between the TCz M-VOL update and the corresponding R-VOL update reaches the specified time, the RCU will suspend all R-VOLs in the group. A timeout occurs when the RCU was not able to settle a recordset within the specified time, or when the RCU has not had any communication from one of the MCUs in the group within the specified time. WARNING: See step (9) below for instructions on selecting the correct Time Out (Copy Pending) setting for your operational environment. RCU Ready (min.): allows you to select the maximum delay allowed for reestablishing MCU-RCU communications following MCU power-off (none or from 0 to 10 min., 0 = no timeout for RCU ready). The default setting is five minutes. If the MCU is not able to re-establish communication with the RCU within the specified time, the MCU suspends all M-VOLs in the group. To add one or more consistency groups to the connected MCU: 1. Make sure that the async options are configured as desired. 2. Click the Asynchronous Operation tab, and select the LDKC that the consistency groups you want to operate belong to, or Not Used in the tree to display the unused consistency groups in the list. 3. Select the (unused) consistency group(s) that you want to add. USP V supports up to 128 consistency groups (00-7F). The 9900 storage system supports up to 64 groups (00-3F). If you are adding a group with a 9900 RCU, select a group ID between 00 and 3F. The USP V storage system supports up to 128 consistency groups (00-7F) per LDKC, and allows you to use up to 128 consistency groups per entire storage system. TagmaStore USP/NSC supports up to 128 consistency groups (00-7F). 4. Right-click the selected group(s), click CT Group Operation, and then click Add CT Group to open the Add CT Group dialog box (refer to Figure 5-8). 5. On the Add CT Group dialog box, select the desired port type and group options (copy pending timeout, RCU ready timeout). Note: You will not be able to modify the port type of the group, after you assign a pair to the group Performing TrueCopy for z/os Configuration Operations

177 6. Click Set to close the Add CT Group dialog box. (Click Cancel to cancel the add group operations.) The preview list now displays the requested add group operation(s). 7. Verify the requested operation(s) displayed in the preview list. To change one or more operations, select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s) from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 8. To start the operation(s), click Apply. 9. If you are using TCz Async in the n-to-1 configuration, reset the Time Out (Copy Pending) option as follows to avoid suspension of TCz pairs due to timeout errors: a) Suspend all pairs in the group, so that you can change the group options. b) Select the group on the Asynchronous Operation window, right-click and click CT Group Operation CT Group Option, change the Time Out (Copy Pending) option to None, and click Set. c) Resynchronize all pairs in the group, and then perform normal I/O operations to the M-VOLs in this group. d) Acquire the current TCz async copy delay time by calculating the difference between the host I/O time-stamp information and the consistency time shown on the CT Group Status dialog box. e) Suspend all pairs in the group again, and set the Time Out (Copy Pending) group option to a value greater than the current copy delay time. If the value exceeds the maximum time (15 min.), reduce the host I/O rate, or set the option to None. f) Resynchronize all pairs in the group. Performing TrueCopy for z/os Configuration Operations 5-35

178 Changing the Consistency Group Options The CT Group Option dialog box (see Figure 5-9) allows you to change the group options for the existing consistency groups. To display the CT Croup Option dialog box, select the LDKC where the desired consistency group belongs, or select Used from the tree in the Asynchronous Operation tab, select the consistency group from the list, right-click, and then click CT Group Option command in the sub menu command of the CT Group Operation command. Note: If you want to change the group options, you must suspend all pairs in the group first. Figure 5-9 CT Group Option Dialog Box Timer Type: allows you to select the timer type option for the group: System = system timer (CPU TOD clock) provided by the I/O time-stamping function Local = local timer (internal MCU TOD clock) None = system timer (CPU TOD clock) provided by the I/O time-stamping function. This timer type should only be selected when establishing TCzA pairs in the reverse direction (to copy from the secondary site back to the primary site). When None is selected, the MCU still acquires the time-stamp information from the host I/O time-stamping function Performing TrueCopy for z/os Configuration Operations

179 MCU-RCU Path: allows you to select the port type for the remote copy connections. You can only change the port type when the group does not contain any pairs. Offloading Timer (min.): allows you to specify the amount of time for monitoring to transfer data to a sidefile between 0 and 20 minutes in one second increment. The default setting is 5 minutes. Enable Inflow Control: allows you to enable the inflow control. To enable the inflow control, click the check box. By default, the check box is selected. Before changing this option, you should release or suspend pairs in the selected consistency group. Note: If you use Business Continuity Manager, please refer to the Business Continuity Manager User s Guide and see explanations about Set Copy Group Attributes and FLOW CTL. If you use PPRC, please refer to information about NO DELAY options that are available in PPRC operations. Time Out (Copy Pending) (min.): allows you to select the maximum delay allowed for TrueCopy for z/os Async copy (none or from 3 to 15 mins., none = no timeout for copy pending). The default setting is five minutes. If the delay between the TCz M-VOL update and the corresponding R-VOL update reaches the specified time, the RCU will suspend all R-VOLs in the group. A timeout occurs when the RCU was not able to settle a recordset within the specified time, or when the RCU has not had any communication from one of the MCUs in the group within the specified time. RCU ready (min.): allows you to select the maximum delay allowed for reestablishing MCU-RCU communications following MCU power-off (none or from 1 to 10 min., 0 = no timeout for RCU ready). The default setting is five minutes. If the MCU is not able to re-establish communication with the RCU within the specified time, the MCU suspends all M-VOLs in the group. To change the group options for one or more groups: 1. Make sure that all pairs in the group(s) have been suspended, so that you can change the group options. 2. Click the Asynchronous Operation tab, and select the LDKC that the consistency groups you want to operate belong to, or Used in the tree to display the existing consistency groups in the list. 3. Select the consistency group(s) for which you want to change the options. You can only select groups for which the connected storage system is the MCU (This CU Type = MCU). 4. Right-click the selected group(s), click CT Group Operation, and then click CT Group Option to open the CT Group Option dialog box. If the CT Group Option command is not enabled, you need to suspend the remaining pairs in this group. Performing TrueCopy for z/os Configuration Operations 5-37

180 5. On the CT Group Option dialog box, select the desired group options. For further information on the consistency group options. You can only change the port type when the group does not contain any pairs. 6. Click Set to close the CT Group Option dialog box. (Click Cancel to cancel the group option operation.) The preview list displays the requested change group option operation(s). 7. Verify the requested operation(s) displayed in the preview list. To change the group option operation(s), select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s) from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 8. To apply the settings, click Apply. 9. When you are finished changing the CT group options, you can resynchronize all pairs in the group(s). Viewing Consistency Group Status The CT Group Status dialog box (see Figure 5-10) displays the detailed status information for the selected TrueCopy for z/os Async consistency group. To view the detailed consistency group status information: 1. Click the Asynchronous Operation tab, and select the LDKC that the consistency groups you want to operate belong to, or Used in the tree. 2. Select the desired CT group in the list. Note: Select only one consistency group. 3. Right-click the group, click CT Group Operation, and then click CT Group Status to open the CT Group Status dialog box Performing TrueCopy for z/os Configuration Operations

181 Figure 5-10 CT Group Status Dialog Box CT Group: Group number of the selected consistency group. This CU Type: CU type (MCU or RCU) of the selected consistency group. LDKC: LDKC number where the consistency group belongs. CLPR: the number and name of the CLPR which the volumes forming pairs belong to. S/N, SSID: Serial number and SSID of the CUs of the selected consistency group. The LDKC number is also displayed enclosed by parentheses to the right of the CU number. CU, LDEV: Pairs in the connected CU that are in the selected consistency group. Note: If "#" is added to the end of LDEV number like 3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. MCU-RCU Path: Type of channel interface between the storage systems (fibre). Offloading Timer (min.): The amount of time for monitoring to transfer data to a sidefile. If the CU type is RCU, this parameter is not displayed. Performing TrueCopy for z/os Configuration Operations 5-39

182 Inflow Control: Enable or disable the inflow control. If the CU type is RCU, this parameter is not displayed. Time Out (Copy Pending) (min.): Maximum delay allowed for TrueCopy for z/os Async copy. Time Out (RCU Ready) (min.): Maximum delay allowed for re-establishing MCU-RCU communications following MCU power-off. If the CU type is RCU, this parameter is not displayed. C/T: Group consistency time of the selected consistency group). Timer Type: Timer type of this group. SEQCHK: indicates that at least one pair of this group has SEQCHK status. Note: The RCU manages the C/T and SEQCHK status, and the MCU acquires these from the RCU. If MCU-RCU communications are down, the MCU may not display the latest C/T and SEQCHK information. Always use the group status and R-VOL status displayed at the RCU for disaster recovery. Note: The SEQCHK status is also displayed as a pair status. To determine exactly which pair(s) in the group has the SEQCHK status, check the R-VOL pair status at the RCU. The Previous button displays status information for the consistency group number before the current consistency group. The Next button displays status information for the CT group after the current group. The Refresh button refreshes the status information. The Close button closes the CT Group Status dialog box Performing TrueCopy for z/os Configuration Operations

183 Deleting Consistency Groups A consistency group can be deleted only from the MCU and only if the MCU does not contain any M-VOLs still assigned to the group. Deleting a consistency group from an MCU does not affect the consistency groups registered at other MCUs. The RCU will automatically delete a consistency group when the last pair in the group is released. The CT Group Operation Delete CT Group command allows you to delete a group from the current MCU. The MCU will not allow you to delete a group which still has M-VOLs in the current MCU. To delete one or more consistency groups from an MCU: 1. Make sure that all affected TrueCopy for z/os Async pairs have been released. 2. Select the LDKC where the desired consistency group belongs, or select Used from the tree in the Asynchronous Operation tab to display the existing consistency groups in the list. 3. Select the consistency group(s) that you want to delete. You can only delete consistency groups from the MCU (This CU Type = MCU). 4. Right-click the RCU, click CT Group Operation, and then click Delete CT Group. The preview list displays the requested consistency group. If the Delete CT Group command is not enabled, one of the groups still contains M-VOLs in this MCU. The preview list displays the requested delete group operation(s). 5. Verify the requested operation(s) displayed in the preview list. To remove one or more delete CT group operations, select the operation(s), right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 6. To delete the group(s), click Apply. Performing TrueCopy for z/os Configuration Operations 5-41

184 Usage Monitor Operations The Usage Monitor window allows you to display and view the I/O statistics for all LDEVs to be monitored on the connected storage system. The I/O statistics are collected by Performance Monitor. From the Usage Monitor window, you can display and view only the data for remote copy. Up to 1,440 monitoring data can be collected for each LDEV at a sampling time interval specified by Performance Monitor, and up to 1,440 pieces of data can be collected for the entire LDEVs to be monitored. The usage monitor operations are: Starting and stopping monitoring Displaying the usage monitor graph Exporting the usage monitor data file Starting and Stopping Monitoring To make settings for starting and stopping the monitor, use Performance Monitor. For procedures to start and stop the monitor, please refer to the Performance Manager User's Guide Performing TrueCopy for z/os Configuration Operations

185 Displaying the Usage Monitor Graph When usage monitoring is running, the Usage Monitor window can display user-selected remote copy I/O statistics in real time. The usage monitor graph plots the user-selected I/O statistics (up to 65 data points) on an x-y graph. The x-axis displays time. The y-axis displays the number of I/Os during the last sampling period. The legend (right side of the graph) indicates the data being displayed. A value on the y-axis varies according to the maximum value of the statistical data that is displaying. If the value on the y-axis exceeds 10,000,000, the value is displayed in exponential notation (e.g., 1E7 = = 10,000,000; 2E8 = = 200,000,000). The Update field displays the most recent data sample time for the data on the graph. To display the usage monitor graph: 1. Make sure that usage monitoring is running (Monitoring Switch = Enable). The usage monitor graph can only be displayed when monitoring is on. 2. Right-click the graph area of the Usage Monitor window, and click Display Item to open the Display Item dialog box (see Figure 5-11). 3. If you want to display I/O statistics for all volumes to be monitored in the storage system, click All Volumes. If you want to display I/O statistics for a specific volume, click Volume, and then enter the LDKC number (00 or 01), CU number (00-3F) and LDEV ID (00-FF) of the desired volume. Note: If you specify unmounted volume, the graph is not displayed. Note: LDKC number:cu number:ldev number is displayed on the top of the graph. If "#" is added to the end of LDEV number like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. If you want to display I/O statistics for the sidefile data, click CLPR, and then select the desired CLPR from the drop-down list. 4. In the Monitor Data box, select the I/O statistics data that you want to display on the graph. You must select at least one box. Table 5-4 describes the I/O statistics data. Note: If you want to display Average Transfer Rate, Pair Synchronized, or SideFile, you cannot select any other statistics at the same time. The graph can only display one type of data at a time: I/O count, rate, or percent. 5. Click Set to close the Display Item dialog box. The Usage Monitor window now displays a graph showing the selected I/O statistics data for the selected LDEV(s). To enlarge the displayed graph, right-click the graph, and click the Large Size command. To return the graph to normal size, right-click the graph, and click the Normal Size command. Performing TrueCopy for z/os Configuration Operations 5-43

186 Note: To stop displaying the usage monitor graph, right-click the graph, and click Close. To stop displaying all graphs, click Close All. The usage monitor graph closes automatically in the following cases: When you click another tab When you select another program product When you exit the Storage Navigator software Figure 5-11 Selecting the Data for the Usage Monitor Graph 5-44 Performing TrueCopy for z/os Configuration Operations

187 Table 5-4 Remote Copy I/O Statistics RIO count Statistic [1] All RIO count All write count RIO error count Initial copy Initial copy RIO count Average transfer rate (kb/s) Average response (ms) Update copy Update copy RIO count Average transfer rate (kb/s) Average response (ms) Asynchronous Copy Asynchronous RIO count Total number of recordsets Average transfer rate (kb/s) Average response (ms) Number of Scheduling Recordsets Scheduling Miss Count Number of Remaining Recordsets Scheduling Attempt Count Description Total number of remote I/Os. Total number of remote write I/Os. Number of errors that occur during remote I/O Number of initial copy remote I/Os. Average transfer rate (kb/sec) for initial copy remote I/Os. Average response time (msec) for initial copy remote I/Os. Number of update copy remote I/Os. Average transfer rate (kb/sec) for update copy remote I/Os. Average response time (msec) for update copy remote I/Os. Number of asynchronous update copy remote I/Os. Number of asynchronous recordsets. Average transfer rate (kb/sec) for TrueCopy/TCz Async update copy remote I/Os. Average response time (msec) for asynchronous update copy remote I/Os. Number of recordsets that are scheduled for the settlement of sidefile Number of times recordsets do not arrive during the schedule Number of remaining recordsets when the schedule is completed Number of job activations of consistency manager Synchronization [2] Pair Synchronized (%) Percent completion of initial copy operations (i.e., number of synchronized pairs / total number of pairs). Out of Sync Tracks Number of tracks that have not yet been copied by the initial copy or resync copy operation (this applies only when suspended during initial copy or during resync copy). Cache Sidefile usage ratio (%) SideFile Note: You can select only when you select Device Total or CLPR in the Select Device on the Display Item dialog box. Notes: 1. The RIO statistics include both TrueCopy for z/os and TrueCopy remote copy operations (e.g., Async RIO Count = TCzA RIOs + TCA RIOs). 2. The Synchronization data cannot be displayed for pairs which were created by the previous version of TrueCopy for z/os (0 is always displayed). Performing TrueCopy for z/os Configuration Operations 5-45

188 Exporting the Usage Monitor Data File To export the monitoring data file, use Export Tool of Performance Monitor. For information and instructions on using Export Tool, please refer to the Performance Manager User s Guide Performing TrueCopy for z/os Configuration Operations

189 Script Operations The TCz software supports scripting for managing pre-defined TCz operations. The TCz scripting function enables you to define multiple TCz operations in a text file that the TCz software reads and executes as a batch file. Scripting allows you to perform a series of TCz operations without having to issue the commands separately. Using TCz scripting, you can set up and execute a large number of TCz commands within a short period of time. The TCz scripting function enables you to: save time by executing multiple TCz operations with a single command run a series of predefined and tested TCz operations after hours or overnight, and/or allow a non-resident system administrator to set up and start an entire day s worth of TCz operations in the limited time that the administrator is on-site. Caution: Do not perform TCz operations using the TrueCopy for z/os windows while the scripting function is being executed. To perform operations on the TrueCopy for z/os windows, wait until the script is complete, or make sure that the script in execution is aborted. The Script Operation window (see Figure 4-11) displays information for the script being executed. This section describes the selection and execution of an existing TCz script file. Performing TrueCopy for z/os Configuration Operations 5-47

190 Executing the Script To execute the script: 1. Create a script in a text format. Note: For the information of syntax and format requirements of TrueCopy for z/os script file. 2. Save the script file. Note: Enclose the file name within the double quotation marks, with an.spt extension, then click the Save button. 3. Transfer the script file to SVP. Click the File Operation button on the Script Operation window to open the File Operation dialog box (see Figure 5-12). 4. To display the Upload the script file dialog box, click the Import button in Script File box. 5. Select the file that you want to transfer, and click the Open button. 6. When the completion message appears, click the OK button. If you want to upload the other script files, repeat steps (4) to (6). 7. To close the File Operation dialog box, click the Close button. 8. Select the file name from the Script File Name drop-down list on the Script Operation window. 9. Select Run from the Operation drop-down list on the Script Operation window. 10. To start the script, click Apply button. 11. When the confirmation message appears, click the OK button Performing TrueCopy for z/os Configuration Operations

191 Figure 5-12 File Operation Dialog Box Exporting the Script Trace Files The File Operation dialog box allows you to export the TrueCopy for z/os script trace files. The downloaded file includes two files: the macro trace file, and the error trace file. Both trace files are compressed into the tgz format when you export. At this time, you can name the compressed files arbitrarily. By uncompressing the compressed files, you will be able to extract a macro trace file (MACROEX.TRC) and an error trace file (ERROREX.TRC), respectively. The macro trace file traces the macros used (see Figure 5-13). Table 5-5 describes the contents of the macro trace file. The error trace file details the errors that occurred while running scripts (see Figure 5-14). Table 5-6 describes the contents of the error trace file /03/05 10:06: Start HRC_CR19.SPT /03/05 10:06: CreateHrcPair $Dev = _ildeva, /03/05 10:06: x0200: 0x0201: 0x0202: 0x0203: /03/05 10:06: CreateHrcPair $Dev = _ildeva, /03/05 10:06: x0200: 0x0201: 0x0202: 0x0203: /03/05 10:06: StartHrcPair /03/05 10:06: End (1) (2) (3) (4) (5) (6) Figure 5-13 Macro Trace File Performing TrueCopy for z/os Configuration Operations 5-49

192 Table 5-5 Number Macro Trace File Information Description (1) All macros executed by TCz are listed in chronological order and numbered. (2) The date that the macro was executed. (3) The time that the macro was executed. (4) The location (script file line number) of the macro. (5) The TCz scripting error code (0000 = no error). See the error trace file, except when "0000" is displayed. (6) The executed macro is displayed. If the macro was completed successfully, the status is End /03/05 10:06: API error (SetCreatePair). ErrorCode= /03/05 10:06: API error (SetCreatePair). ErrorCode= (1) (2) (3) (4) (5) (6) (7) Figure 5-14 Table 5-6 Number Error Trace File Error Trace File Information Description (1) All macro errors encountered by TCz are listed in chronological order and numbered. (2) The date that the macro error occurred. (3) The time that the macro error occurred. (4) The location (script file line number) of the macro that caused the error. (5) The TCz scripting error code (see Table B.18). (6) The TCz scripting error code message ID (see Table B.18). (7) Brief description of the error Performing TrueCopy for z/os Configuration Operations

193 To export the script trace files: 1. Click the File Operation button on the Script Operation window to display the File Operation dialog box (see Figure 4-11 and Figure 5-12). 2. Click the Export button in the Trace File box. 3. When the confirmation message appears, click the Yes button. The Save the macro trace file dialog box appears. 4. On the Save the macro trace file dialog box, enter the desired name and location for export the macro trace file. After the download is completed, the Save the error trace file dialog box appears. 5. On the Save the error trace file dialog box, enter the desired name and location for export the error trace file. After the download is completed, the completion message appears. 6. Click the OK button. 7. To close the File Operation dialog box, click the Close button. Performing TrueCopy for z/os Configuration Operations 5-51

194 History Operations To display the latest information on the History window, click File, and then Refresh on the menu bar of the Storage Navigator main window. Exporting the History File To export the remote copy history file: 1. Click the History tab. 2. Click the Export button on the History window (see Figure 4-12). 3. When the confirmation message appears, click the Yes button. The Save the history file dialog box opens. 4. On the Save the history file dialog box, enter the desired name and location for the export file, and click Save (or click Cancel to cancel your request to export the file). Figure 5-15 shows the displayed history file. The displayed items are: (1) Date and time when the operation was completed. (2) Status of the operation. (3) LDKC number, CU number, and LDEV number of the operated volume. (4) This column is not used. (5) LDKC number, CU number, and LDEV number of the paired volume. (6) The time taken for the operation (from the start of the operation to the end). Displayed only for Pairing Complete and Pair Resync. Complete operations. 2002/07/25 20:26:43,Pairing Start,00:1a:80,-----,00:1a: /07/25 20:25:30,Pair Delete,00:00:84,-----,00:00: /07/25 17:01:33,Suspend Operation,00:00:85,-----,00:00: /07/19 20:01:58,Pair Resync. Complete,00:1a:80,-----,00:1a:9e,000:00: /07/19 20:01:56,Pair Resync. Start,00:1a:8a,-----,00:1a:a8 2002/07/18 09:36:22,Pairing Complete,00:1a:80,-----,00:1a:85,000:00:10 (1) (2) (3) (4) (5) (6) Figure 5-15 Example of TrueCopy for z/os History File 5-52 Performing TrueCopy for z/os Configuration Operations

195 Other Operations The System Option window allows you to clear the remote copy SIMs for the connected USP V, and to change the option settings of the storage system or CUs. Clearing SIMs The Clear SIM button on the System Option window allows you to clear all remote copy SIMs (service information messages) from the connected storage system. Remote copy SIMs include all SIMs issued for TrueCopy for z/os and TrueCopy operations. The clear SIM function is intended for use during disaster recovery operations, while switching operations to the remote (secondary) backup site. To clear all remote copy SIMs from the connected USP V: 1. Click the System Option tab, and then click the Clear SIM button (see Figure 4-13). 2. On the Clear SIM confirmation dialog box, click Yes to clear all remote copy SIMs from the connected storage system, or click No to cancel your request to clear SIMs. 3. If you clicked Yes, the storage system verifies that the existing SIMs are being cleared. Note: When all SIMs have been cleared, the storage system MESSAGE lamp on the USP V control panel turns off. This may take up to 30 minutes. If there are any existing SIMs which are not related to remote copy operations, the MESSAGE lamp will not turn off. Performing TrueCopy for z/os Configuration Operations 5-53

196 Changing the Option Settings of Storage System The information of the storage system's option settings is displayed if you select Subsystem Option from the tree on the System Option window. Figure 5-16 Option Settings List for the Storage System Activities: Number of volumes in concurrent initial copy operations (1 to 512). Activities (CU): It shows whether the CU-by-CU setting of concurrent initial copy operations will be enabled or disabled. Path Watch: Time for monitoring blockade in the paths (2 to 45 seconds). Path SIM Watch: Time for monitoring SIMs that are reported when paths are blocked (2 to 100 seconds). SIM Report: Reporting status for service-level remote-copy SIMs (SIM type: except DEVICE) to the host(s). Report or No Report will be displayed. To change the option settings of the storage system: 1. Click the System Option tab, and then select Subsystem Option in the tree (see Figure 4-13). 2. Right-click the list to display the pop-up menu, and click System Option to open the System Option dialog box (see Figure 5-16). 3. On the System Option dialog box, change the storage system options. Note: When the System Option dialog box opens, current settings are displayed. 4. Click the Set button to close the System Option dialog box. The desired change(s) is/are now displayed in the preview list. Note: To cancel the change(s), click the Cancel button. 5. Verify the desired change(s) in the preview list (see Figure 5-17). To change the settings, right-click the preview list, click Modify, make the desired changes, and close the dialog box. The preview list displays the updated information Performing TrueCopy for z/os Configuration Operations

197 To omit the settings, right-click the preview list, and click Delete. The changes are cancelled. To cancel all operations, select all the operations in the preview list, rightclick, and click the Delete command or click the Cancel button. To display error code, right-click the preview list, and click Error Detail. Error code is displayed on the rightmost the preview list. 6. To apply the settings, click Apply. If an error occurs in the setting, an error code is displayed in the Error Code column in the preview list. To display the error message, right-click on the list, display the pop-up menu and click Error Detail. After you check the error message, click OK button to close the error message. If necessary, please remove the cause of the error message. Figure 5-17 System Option Dialog Box The Maximum Initial Copy Activities setting specifies the number of concurrent initial copy operations. You can set a number from 1 to 512. The default setting is 64 volumes. TrueCopy for z/os initial copy activities can impact the performance of the main storage system, depending on the amount of I/O activity and the number of pairs being registered at the same time. The maximum initial copy activities setting of 64 volumes allows you to limit the impact of initial copy activities on storage system performance. For example, if you set the maximum initial copy activities to 64 volumes and then add 65 TrueCopy for z/os pairs at the same time, the MCU starts the first 64 pairs and will not start the 65th pair until one of the first 64 pairs is synchronized (Duplex status). When you change the maximum initial copy activities setting, the new setting applies to pairs created after the setting was changed, not to existing pairs. The Maximum Initial Copy Activities (CU) setting specifies whether the CU-by-CU setting of concurrent initial copy operations will be enabled or disabled. If it is enabled, you can specify the CU-by-CU setting of concurrent initial copy operations, and if it is disable, you cannot specify the setting. Performing TrueCopy for z/os Configuration Operations 5-55

198 The Path Blockade Watch (sec.) setting specifies the time for monitoring blockade in the paths. The path blockade watch value must be from 2 to 45 seconds. The default setting is 40 seconds. Note: If you create a pair with the synchronous mode, and if the status of all paths becomes "Monitoring" because of a path error, MIH may occur in the host. The time of the Path Blockade Watch must be shortened than the setting time of MIH timer in the host. The Path Blockade SIM Watch (sec.) setting specifies the time for monitoring SIMs that are reported when paths are blocked. The path blockade SIM watch value must be from 2 to 100 seconds. The default setting is 70 seconds. The value of the Path Blockade SIM Watch cannot be smaller than the value of the Path Blockade Watch. The Services SIM of Remote Copy setting displays the status of whether the service SIM in storage system is reported to the host or not. Changing the Option Settings of CUs The information of the CUs' option settings is displayed if you select CU Option from the tree on the System Option window. Figure 5-18 Option Settings List for the CUs CU: Number of CUs in the LDKC that you choose from the tree (00 to FE). SIM Report: Reporting status for service-level remote-copy SIMs (SIM type: DEVICE) to the host(s). PPRC Support: Status of PPRC support for the host Performing TrueCopy for z/os Configuration Operations

199 SCP Time: State-change-pending (SCP) time. SCP Time of TrueCopy for z/os and the state-change-pending time of Compatible FlashCopy V2 are same. If you change the state-change-pending time of TrueCopy for z/os, the state-change-pending time of Compatible FlashCopy V2 will change simultaneously. If you also change the state-change-pending time of Compatible FlashCopy V2, the state-change-pending time of TrueCopy for z/os will change. For more information on state-change-pending time of Compatible FlashCopy V2, please refer to the Compatible Mirroring for IBM FlashCopy User s Guide. Activities: Number of volumes in concurrent initial copy operations (1 to 16).When you set Disable for Maximum Initial Copy Activities (CU) option on the System Option dialog box, Disable is shown instead of number. To change the option settings of the CU: Note: In order to specify the Maximum Initial Copy Activities on the CU Option dialog box, you need to set the Maximum Initial Copy Activities (CU) to Enable on the System Option dialog box in advance. 1. Click the System Option tab, and then select CU Option for the LDKC containing the desired CU from the tree. (see Figure 4-13). 2. Select one or more CU from the list, right-click to display the pop-up menu. 3. Click the CU Option button to display the CU Option dialog box (see Figure 5-19). 4. On the CU Option dialog box, change the CU options. Note: When the CU Option dialog box opens, current settings are displayed. If you specified plural CUs, and the option settings of each CU are different, the inputting box(es) on the CU Option dialog box is/are blank. If you change the setting(s) on the CU Option dialog box, the settings of all specified CUs will be same. 5. Click the Set button to close the CU Option dialog box. The desired change(s) is/are now displayed in the preview list. Note: To cancel the change(s), click the Cancel button. 6. Verify the desired change(s) in the preview list. To change the settings, right-click the preview list, click Modify, make the desired changes, and close the dialog box. The preview list displays the updated information. To omit the settings, right-click the preview list, and click Delete. The changes are cancelled. To cancel all operations, select all the operations in the preview list, rightclick, and click the Delete command or click the Cancel button. To display error code, right-click the preview list, and click Error Detail. Error code is displayed on the rightmost the preview list. Performing TrueCopy for z/os Configuration Operations 5-57

200 7. To apply the settings, click Apply. Figure 5-19 CU Option Dialog Box The Service SIM of Remote Copy option allows you to specify whether the MCU will report the service-level remote-copy SIMs to the host(s). (The moderate-, serious-, and acute-level SIMs are always reported to the host.) Select Report to configure the MCU to report the service-level remote-copy SIMs to the host(s). The Report setting should be selected for TCz disaster recovery planning. Select No Report to suppress service-level SIM reporting. Default setting is No Report. The PPRC support by host option allows you to specify whether the MCU will generate sense information which is compatible with IBM PPRC. This option is extremely important for TCz disaster recovery planning. If the host does not support PPRC, select No to configure the MCU to report SIMs. If the host system supports PPRC, select Yes to configure the MCU to generate PPRCcompatible sense information when a TCz pair is suspended instead of a service information message (SIM). Default setting is No. If Yes is selected, the MCU will still report moderate- and serious-level SIMs, as well as DF40 and DF48 device SIMs. Note: If you plan to utilize the CGROUP (FREEZE/RUN) command for TCz pairs, you must select Yes. The SCP Time(sec.) setting specifies the state-change-pending (SCP) delay time in seconds (0-600 seconds, default = 120). CGROUP/FREEZE utilizes the SCP state to suspend host I/Os to TCz M-VOLs. TCzA utilizes the SCP state for inflow control to prevent cache storage overload. Make sure to set the SCP Time after you have added all MCU-RCU paths Performing TrueCopy for z/os Configuration Operations

201 Note: SCP Time of TrueCopy for z/os and the state-change-pending time of Compatible FlashCopy V2 are same. To determine the SCP Time of TrueCopy for z/os, take into account the fact that if you change the SCP Time setting by the CU Option dialog box, the state-change-pending time of Compatible FlashCopy V2 will change. For more information on state-change-pending time of Compatible FlashCopy V2, please refer to the Compatible Mirroring for IBM FlashCopy User s Guide. The Maximum Initial Copy Activities: allows you to specify the number of volumes on which copy operations can be performed at the same time from 1 to 16 volumes for the selected CU. When you set Disable for Maximum Initial Copy Activities (CU) option on the System Option dialog box, you cannot specify this option. Even if you set a value larger than the setting for Maximum Initial Copy Activities on the System Option dialog box, the priority is given to Maximum Initial Copy Activities on the System Option dialog box. Performing TrueCopy for z/os Configuration Operations 5-59

202 Configuring and Maintaining Your TCz Environment Optimizing TrueCopy for z/os Operations and Storage System Performance All TCz operations result in increased utilization of the USP V s channel resources because of the additional write (remote copy) operations to the secondary volumes. The TCz update copy mode (synchronous or asynchronous) determines exactly how the remote copy operations will impact storage system performance as follows: Synchronous copy mode (TCz Synchronous) has an additional effect on storage system performance: increased service and disconnect time for write I/Os to TCz M-VOLs due to the delay between channel-end and device-end. The length of this delay increases as the distance between the M-VOL and R- VOL increases, so that the longest delay occurs when the main and remote volumes are the maximum distance apart. Asynchronous copy mode (TCzA) eliminates all delays associated with TCz Synchronous operations while providing increased protections for writedependent applications in the event of a disaster. Write I/Os for TCzA M-VOLs are processed in the same way as writes for simplex volumes, without any increase in service or disconnect time. The asynchronous R-VOL updates are performed completely independent of all host I/O processes at the M-VOLs, and there are no restrictions on subsequent read/write operations to TCzA M- VOLs. The only performance concerns for TCzA are: To ensure that adequate cache resources are available for sidefiles which are used to store the recordsets at both the MCUs and RCUs. To ensure that sufficient MCU-RCU paths are defined for copy operations. In addition to the TCz update copy mode, several other factors can also affect USP V performance. You can optimize both the TCz operations and the I/O performance of the storage systems by analyzing workloads and addressing system-level conditions (e.g., number of remote copy connection paths) which can affect storage system performance. You can also control the impact of TCz operations on storage system performance by selecting the appropriate RCU options for each MCU and the appropriate update copy mode (synchronous or asynchronous) and pair options for each TCz pair. In addition, you can upgrade the TCz hardware components and/or adjust the configuration of the components to improve storage system performance under a wide range of operating conditions. Table 5-7 lists some of the conditions which affect storage system performance and provides recommendations for addressing these conditions Performing TrueCopy for z/os Configuration Operations

203 Note: For important information about proper configuration for your operational environment. Performing TrueCopy for z/os Configuration Operations 5-61

204 Table 5-7 Optimizing TrueCopy for z/os Operations and USP V Performance Condition Description Recommendation(s) Write-intensive workloads Write-intensive workloads, such as SPOOL volumes and database logging volumes, can have a significant impact on storage system I/O response times. Spread write-intensive data across several volumes to minimize queuing. Large block size High host channel demand Sequential write operations Cache size RCU capacity Remote copy connection paths Workloads with large write block sizes, such as DB2 deferred writes, can impact performance. The demand on the MCU s host channels can affect performance. TCz operations can have a negative impact on workloads with a high percentage of sequential write operations, such as batch processing operations (e.g., dump/restore, sort operations). Large cache size improves read hit performance, which allows more storage system resources to be devoted to write operations. The resulting performance improvement can offset some or all of the performance loss due to the TCz remote copy operations. TCzA and Concurrent Copy (CC) require additional cache for sidefile data. Insufficient cache resources can result in command retries, SCP notifications, and puncture conditions. The performance of the RCUs directly affects the performance of the MCUs. If an RCU becomes overloaded with heavy update activity, MCU and system performance can also be degraded. An inadequate number of remote copy connection paths may decrease storage system performance. Performing TCz Synchronous operations over long distances can also degrade storage system performance. TCzA is recommended for long distances. Spread workloads with large write block sizes across several volumes. Spread the workload across several storage systems to utilize additional channels. Avoid performing restore operations to volumes which belong to TCz pairs. Instead, restore data to a scratch volume and then establish the TCz pair. Consider increasing the cache size of the TCz storage systems to handle TCzA and CC sidefile operations and to improve overall storage system performance. For best results, the cache and NVS capacity of the main and remote storage systems should be the same (for TCzA the RCU sidefile requirements are 2x that of the MCU) to enable the remote site to function adequately during disaster recovery. Distribute TCz remote copy operations among several remote storage systems to avoid overloading any one RCU. Make sure to install an adequate number of remote copy connection paths between the main and remote storage systems. This is especially important for storage systems which contain both M-VOLs and R-VOLs Performing TrueCopy for z/os Configuration Operations

205 Changing from 3990 to 2105 or 2107 Emulation TrueCopy for z/os supports , E, 2105, and 2107 controller emulation types for the USP V MCU and RCU. The , E, 2105 or 2107emulation is required for SMS I/O time-stamping of TCzA recordsets. The 2105 and 2107 emulation type is required for Compatible PAV operations. Changing from 3990 to 2105 or 2107: If you need to change the emulation from 3990 to 2105 or 2107 for a USP V which has existing Concurrent Copy (CC) pairs, you must: 1. Stop all Concurrent Copy jobs. 2. Change the CU emulation type of all CHA packages in the USP V to 2105 or For CC operations, 3990 and 2105 or 2107 emulations cannot be intermixed in the same storage system. 3. Restart Concurrent Copy jobs. Note: The PPRC commands are different for 3990 and 2105 or 2107 emulation types. Note on 2105 or 2107 CU Emulation Type of MCU: When the CU emulation type of MCU is 2105 or 2107, and a host system is online to R-VOL, even if you want to create a TC-MF pair by using the CESTPAIR command, the CESTPAIR command is rejected. If you use the ONLINSEC(YES), you can create a TC-MF pair even though a host system is online to R-VOL. If you do not use the ONLINSEC (default), or if you use the ONLINSEC(NO), you cannot create a TC-MF pair. If RCU does not support the 2105 or 2107 CU emulation type, you cannot check whether a host system is online or not. In this case, if you use the CESTPAIR command, and both MCU and RCU fulfill the following condition, specify the ONLINSEC(YES). MCU is USP V, and the host on the MCU side is connected to the package of 2105 or 2107 CU emulation type. Performing TrueCopy for z/os Configuration Operations 5-63

206 Powering Off/On TrueCopy for z/os Components The user is responsible for controlling power-off activities for storage systems involved in TCz operations. If you need to power off the USP V, please call your Hitachi representative or the Hitachi Support Center for assistance. If power is removed from an MCU while TCz operations are in progress, the TCz pairs are not affected, but the update sequence consistency of the TCzA groups at the RCU may be affected. When power is restored to an MCU, the MCU communicates with its RCU(s) to confirm the pair status of the R-VOLs. Make sure that TCz communications are fully restored (all RCU paths have normal status) before beginning I/O operations to the M-VOLs. If the MCU accepts a write I/O operation for an M-VOL before this confirmation is complete, the MCU will suspend the pair and change the status of the M-VOL to suspended-by RCU (the MCU will not be able to change the pair status of the R-VOL). If power is removed from an RCU or remote copy connection while TCz operations are in progress, the MCU(s) will detect the communication failure, suspend all affected pairs, and generate SIMs and console messages reporting the failures. The MCU will change the status of the M-VOLs to suspended-by RCU but will not be able to change the status of the R-VOLs. Note: If an MCU/RCU is powered off and its backup batteries are fully discharged while TCz pairs are suspended, the M-VOL/R-VOL cylinder maps will not be retained. In this unlikely case, the MCU/RCU will mark all cylinders of all suspended TCz volumes as modified, so that the MCU will perform the equivalent of an entire initial copy operation when the pairs are resynchronized. (The R-VOL cylinder map is used only for TCzA operations.) Planned Outage of the MCU A planned MCU outage does not affect TCz Synchronous pairs. For TCzA operations, the MCU must communicate with the RCU even when there are no M-VOL update I/Os from the primary system. During the power-off sequence, the MCU will automatically suspend all TCzA pairs in the duplex and duplex pending state (suspend type = MCU P/S-OFF). During power-on-reset sequence, the MCU will automatically resynchronize these suspended pairs (pairs with other suspend types are not automatically resynchronized). If a TCzA group contains M-VOLs in the MCU being powered off and in other MCU(s) which is/are not being powered off, the pairs behind the other MCU(s) will not be suspended and will continue to be updated. If you need to maintain a fully consistent group at the RCU during the planned MCU outage, take the following steps: 1. Quiesce the applications using all M-VOLs in the consistency group. 2. Suspend the group at the RCU using the Group suspend option. You can use the Purge or Drain suspend option since the M-VOL updates have stopped Performing TrueCopy for z/os Configuration Operations

207 3. Perform the planned outage of the TCz MCU. 4. When the MCU is fully powered on and ready to resynchronize operations, resynchronize the TCzA pairs at all MCUs that were powered off (use the resynchronize group option). Performing TrueCopy for z/os Configuration Operations 5-65

208 Planned Outage of the RCU or Remote Copy Connection You must suspend all affected TCz pairs prior to a planned outage of an RCU or of a remote copy connection component (e.g., switch, extender). If you do not suspend the pairs first, the MCU(s) will detect the communication failure, suspend all affected pairs, and generate SIMs and console messages reporting the failures. To perform a planned outage of a TCz RCU or remote copy connection component: 1. Identify all TCz M-VOLs which will be affected by the equipment outage. You need to know the MCU, CU, and LDEV ID for each of these M-VOLs. For RCU power-off, identify all M-VOLs which are paired with R-VOLs in the RCU to be powered off. For remote copy connection outage, identify all M-VOLs in all MCUs which use the path/component to be powered off. 2. Connect to each MCU which contains affected M-VOLs, and suspend all affected TCz pairs. Make sure to confirm the pair status changes (TCz Detailed Information dialog box or CQUERY TSO command). 3. Perform the planned outage of the RCU or remote copy connection. 4. When the RCU is fully powered on and ready to resynchronize operations, resynchronize all TCz pairs at each MCU. Make sure to confirm the pair status changes. Planned Outage of the MCU and RCU When you plan an outage of TCz MCUs and RCUs at the same time, the MCUs must be powered off before the RCUs and powered on after the RCUs. To perform a planned outage of a TCz MCU and RCU: 1. If RCU power-on will be difficult to control (e.g., Power-Control-Interface setting), you should consider increasing or disabling the RCU Ready CT group option for each TCzA group with R-VOLs in the RCU(s) to be powered off. 2. Perform the planned outage of the MCU(s). Do not power-on the MCU(s) yet. 3. If an RCU to be powered off is connected to an MCU which is not powered off, make sure to suspend those TCz pairs before powering off the RCU. 4. Perform the planned outage of the RCU(s). 5. Power on the RCU(s). Make sure that they are fully operational and ready to resynchronize operations before powering on the MCUs. Power on the MCU(s), and make sure that they are ready to resynchronize operations. If you suspended any pairs in step (3), you can also resynchronize those pairs now Performing TrueCopy for z/os Configuration Operations

209 Discontinuing TrueCopy for z/os Operations If you plan to use TCz for nondisruptive data migration or duplication, you will configure and establish TCz operations, allow TCz to synchronize the volumes, redirect application I/Os (if migrating), and then discontinue TCz operations. When you are ready to discontinue TCz operations, you will need to perform TCz operations in the correct order to avoid generating error messages. For example, TCz will not allow you to delete an RCU path until you have released all TCz pairs still using that path, and you cannot delete a group until you have released all TCzA pairs in that group from the MCU. To discontinue all TCz operations, perform the following actions in the following order: 1. First release all TCz pairs from the MCU(s). For TCzA pairs, you can use the Group for Delete Rangeoption to release all pairs in a group using one operation. Verify that the pair status has changed to simplex for all TCz volumes before continuing. 2. Delete the TCzA group(s) from the MCU(s). The RCU will automatically delete a group when all pairs in the group have been released. 3. Delete the RCUs. Check each CU of each MCU to make sure that all RCUs have been deleted before continuing. Note: If system option mode 114 is enabled, you can use the CDELPATH TSO command to delete the RCUs and automatically reset the ports. 4. Remove the remote copy connections (physical paths). If you are not familiar with the operation of the remote copy hardware components (e.g., switches), please call the Hitachi Support Center for assistance. 5. At the MCU(s), reset the USP V initiator port(s) to ordinary target(s). At the RCU(s), reset the USP V RCU target port(s) to ordinary target(s). Note: If you used the CDELPATH TSO command to delete the RCUs, USP V automatically reset each port after the last path to an RCU was deleted. Note: 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. Performing TrueCopy for z/os Configuration Operations 5-67

210 5-68 Performing TrueCopy for z/os Configuration Operations

211 6 Performing TrueCopy for z/os Pair Operations This chapter provides instructions for performing TrueCopy for z/os pair operations. Performing TrueCopy for z/os Pair Operations 6-1

212 Creating TrueCopy for z/os Pairs You can start establishing the TCz pairs as soon as you have: Identified the volumes which will become the TCz M-VOLs and R-VOLs Ensured that all system and TCz requirements have been met Assessed TCz Requirements Completed hardware and software installation Configured the MCUs and RCUs for TCz operations The Add Pair dialog box (see Figure 6-1 and Figure 6-2) allows you to add new TrueCopy for z/os pairs and set the initial copy options and pair options for the new pairs. To open the Add Pair dialog box, click the Pair Operation tab, select a CU from the tree, select the desired device from the list, right-click and click Add Pair command. And then select the desired copy mode (sync or async) for the new pair(s). Figure 6-1 Add Pair Dialog Box for Synchronous Pairs 6-2 Performing TrueCopy for z/os Pair Operations

213 Figure 6-2 Add Pair Dialog Box for Asynchronous Pairs M-VOL: Displays the LDKC number, CU image number, LDEV ID, CLPR number, and CLPR name of the selected LVI(s). If you selected more than one M-VOL, the M-VOL with the lowest LDEV ID is displayed. Note: If "#" is added to the end of the device ID like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. R-VOL: Allows you to select the R-VOL(s) for the new pair(s). If you selected more than one M-VOL, select the R-VOL for the M-VOL being displayed. The R- VOLs for the rest of the M-VOLs are automatically assigned according to the LDEV ID. For example, if you select three M-VOLs and select LDEV 01 as the R-VOL for the first M-VOL, the R-VOLs for the two other M-VOLs will be LDEV 02 and LDEV 03. Performing TrueCopy for z/os Pair Operations 6-3

214 RCU: Select the RCU (the serial number, the LDKC number, the CU number, SSID, and path type) for the TCz pair(s) being created. The RCUs which have been added to the current MCU are displayed. The RCU must be the same for all pairs being created during one operation. M-VOL Fence Level (Synchronous only): Select the fence level for the new pair(s) (default = Never). Data: the M-VOL will be fenced (reject write operations) when the MCU cannot successfully execute an update copy operation for any reason. This setting is functionally equivalent to the CRIT(YES-ALL) parameter for the CESTPAIR command. Status: the M-VOL will be fenced only if the MCU is not able to change the R-VOL status to suspended when an update copy operation fails. This setting is functionally equivalent to the CRIT(YES-PATHS) parameter for the CESTPAIR command. Never: the M-VOL will never be fenced. This setting is functionally equivalent to the CRIT(NO) parameter for the CESTPAIR command. Note: For further information on the CESTPAIR CRIT parameter and its two modes of operation, CRIT(YES-PATHS) and CRIT(YES-ALL), Initial Copy Parameters: Select the initial copy options for the new pair(s). Initial Copy (default = Entire Volume): Entire Volume= copy the data in all M-VOL tracks to R-VOL. This setting is functionally equivalent to the MODE=COPY parameter for the CESTPAIR command. None = do not copy any M-VOL data to R-VOL. This setting is functionally equivalent to the MODE=NOCOPY parameter for the CESTPAIR command. WARNING: The user must ensure that the M-VOL and R-VOL are already identical when using the No Copy setting. Copy Pace: desired number of tracks to be copied at one time during the initial copy operation (default = 15): 15 Tracks. This setting is functionally equivalent to the PACE=2-255 parameter for the CESTPAIR TSO command. 3 Tracks. This setting is functionally equivalent to the PACE=1 parameter for the CESTPAIR command. Priority: priority (scheduling order) of the initial copy operations (1-256). The default setting is 32. Note: The CESTPAIR TSO command does not support the initial copy priority option. When CESTPAIR is used to establish TCz pairs, the initial copy operations are performed in the order that the CESTPAIR commands are issued. 6-4 Performing TrueCopy for z/os Pair Operations

215 Note: If the time out error occurs during the Add Pair operation, the copy operation may not be executed correctly in the order that you have set with the Priority parameter. The time out error may be caused by the CU configuration or a remote copy path error. Review the error, release the pair with the error, and then retry the Add Pair operation. Difference Management: Select Auto, Cylinder or Track as the basis for managing the differential data. The default is Auto. When you select Auto, either Cylinder or Track is selected depending upon the basis size of the logical volume image. CFW Data: Specifies whether the CFW data will be copied to the R-VOL: Copy to R-VOL: the MCU will copy the CFW data to the R-VOL. Only M-VOL: the MCU will not copy the CFW data to the R-VOL. This setting is recommended for two reasons: (1) copying the CFW data impacts subsystem performance, (2) CFW data is typically used for temporary files (e.g., sort work datasets) which are not usually required for disaster recovery. Note: When you create a TCz pair, and if you select only M-VOL for the CFW data option, the data set which is updated by CFW in M-VOL cannot be used in R-VOL. To use this data set in R-VOL, release a TCz pair, and format the data set. Note: If a TrueCopy for z/os pair is established using PPRC commands, the CFW data option is set to the Copy to R-VOL setting. Note: By using Remote Copy Function Switch, you can set the following option with CESTPAIR: CFW data = only M-VOL. If you want to use this function, please contact your Hitachi account team. DFW to R-VOL (Synchronous only): Specifies whether the MCU will suspend a TCz pair when the RCU cannot execute DFW to the R-VOL: DFW not required: the pair is not suspended when DFW to the R-VOL is blocked. DFW required: the pair is suspended when DFW to the R-VOL is blocked. Caution: The interaction of the DFW required setting and the M-VOL fence level setting can cause a host application to fail with a permanent I/O error when attempting to update an M-VOL. Keep track of which pairs have the DFW required setting, and make sure that DFW to the R-VOL is not blocked. Note: If a TrueCopy for z/os pair is established using PPRC commands, the DFW to R-VOL option is set to the DFW not required setting. Asynchronous Parameters (Asynchronous only): CT Group: consistency group for the new pair(s). Consistency groups which have already been added to the current MCU are displayed. Note: This option cannot be changed after a pair has been added. Performing TrueCopy for z/os Pair Operations 6-5

216 Note: Only TCzA pairs that belong to the same CLPR can be allocated to one consistency group. For further information on CLPR, please refer to the Virtual Partition Manager User's Guide. Error Level: Select the desired error level for the new pair(s): Group, or Volume (default = Group). Note: The CESTPAIR TSO command also allows you to specify the error level for TrueCopy for z/os Async pairs. The Cancel button cancels the settings you have made and closes the Add Pair dialog box. The Set button sets the parameters and closes the Add Pair dialog box. 6-6 Performing TrueCopy for z/os Pair Operations

217 To add (establish) one or more TCz pairs: 1. At the remote site: g) Make sure that the LVI(s) which will be the R-VOL(s) are offline from all hosts. h) Connect to the storage system which will be the RCU for the new pair(s), and log on with Administrator or TrueCopy write access. i) Make sure that the RCU remote copy port(s) is/are configured to RCU target port(s). 2. At the main site: j) Connect to the storage system which will be the MCU for the new pair(s), and log on with Administrator or TrueCopy write access. d. Make sure that the MCU remote copy port(s) is/are configured to initiator port(s). Make sure that the correct RCU CU (contains the LVIs that will be R-VOLs) has been added to the correct MCU CU (contains the LVIs that will be M-VOLs). Click the Pair Operation tab, and select the CU which contains the LVI(s) which will be the M-VOL(s) of the new pairs. Make sure that you selected proper CU, port, or host group. Use the Display Filter as needed to display the desired LVIs (e.g., select Simplex status only). 3. Select the LVI(s) which will be the M-VOL(s) of the new TrueCopy for z/os pair(s). You can create multiple pairs at the same time only when: (1) the R- VOLs are in the same RCU, and (2) the pairs have the same copy mode (sync or async). You cannot create TrueCopy for z/os Sync pairs and TrueCopy for z/os Async pairs at the same time. 4. Right-click, click Add Pair, and then select the desired pair mode (Synchronous or Asynchronous) to open the Add Pair dialog box (refer to Figure 6-1 and Figure 6-2). Note: The update copy mode, sync or async, has the greatest impact on performance and must be considered carefully. Factors in mode selection include (but are not limited to) the use of TrueCopy for z/os (for disaster recovery or migration), the number of pairs, and the write I/O activity to the M-VOLs. 5. On the Add Pair dialog box, enter the desired R-VOL for the pair, and select the RCU. If you are creating multiple pairs, select the R-VOL for the M-VOL being displayed. The R-VOLs for the rest of the M-VOLs will be assigned automatically according to the LDEV ID. For example, if you select three M- VOLs and select device 01 as the R-VOL for the first M-VOL, the R-VOLs for the two other M-VOLs will be device 02 and device Select the desired initial copy options and pair options. The initial copy options and pair options you select are applied to all pairs being created, and you can modify the options for each pair as needed before starting the add pair operations (see step 9). Performing TrueCopy for z/os Pair Operations 6-7

218 7. Click Set to close the Add Pair dialog box. The requested add pair operation(s) is/are now displayed in the preview list. 8. Verify the requested operation(s) displayed in the preview list. Make sure that all options for each new pair are correct. After a pair has been created, you can only change the M-VOL fence level, CFW data, and error level options. To change one or more operation(s), select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s) from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command or click the Cancel button. Note: If you want to set the parameters on the multiple volumes at once without changing individual parameters per volume, make the box of parameters that you do not want to change blank. Only the parameters that you input will be changed. 9. To start the operation(s), click Apply. The MCU will start the initial copy operations according to the initial copy priority and the maximum initial copy activities setting on the System Option window. If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed on the Error Code column in the preview list. To display an error message, select one LU, right-click, and click Error Detail. After you see the error message, click OK button to close the error message. 10. On the Pair Operation window, verify that the add pair operation(s) is/are displayed correctly (Pending status) in the list. To monitor the progress of the add pair operation(s), click File, and then Refresh on the menu bar of the Storage Navigator main window to update the information in the list, or use the Detailed Information dialog box to monitor the detailed status of each pair. Note: If an error occurs after you click Apply, you can display the error message by right-clicking on the operation and clicking the Error Detail command. Note: The add pair operation will be rejected if the M-VOL is in the correction access or correction copy state. If this occurs, wait for the volume state to change, and then repeat this procedure. If the status is not displaying correctly, make sure that the correct CU is selected. Note: The CESTPAIR TSO command can be used to add TrueCopy for z/os Sync and Async pairs. CESTPAIR does not allow you to specify the initial copy priority, or DFW to R-VOL option. 6-8 Performing TrueCopy for z/os Pair Operations

219 Initial Copy Options When you add new TrueCopy pairs, you select the initial copy options on the Add Pair dialog box. After a pair has been added (i.e., the add pair operation has started), you cannot change the initial copy options, unless you release and then restart the pair. Initial Copy. Specifies the initial copy mode for the new pair(s). If Entire Volume is selected, the initial copy operation will copy the data in all tracks on the M-VOL (except diagnostic and unassigned alternate tracks) to the R-VOL. This setting is functionally equivalent to the MODE=COPY parameter for the CESTPAIR command. If None is selected, the initial copy operation will not be performed. The MCU will begin performing update copy operations as needed. This setting is functionally equivalent to the MODE=NOCOPY parameter for the CESTPAIR command. Caution: The user must ensure that the M-VOL and R-VOL are already identical when using this setting. Copy Pace. Specifies the maximum number of tracks that can be copied at one time by the TCz initial copy operation before the MCU accepts another host request: 15 Tracks: speeds up the initial copy operation but may affect the storage system s I/O performance if the M-VOL is experiencing high write I/O activity. This setting is functionally equivalent to the PACE=2-255 parameter for the CESTPAIR TSO command. 3 Tracks: slows down the initial copy operation to minimize the impact of the initial copy operation on the storage system s I/O performance. This setting is functionally equivalent to the PACE=1 parameter for the CESTPAIR command. Priority. Specifies the order in which the initial copy operations will be performed, if the number of requested initial copy operations is greater than the maximum initial copy activities setting on the System Option window. The highest priority is 1, and the lowest priority is 256 (current default = 32). The TCz initial copy priority option can be used to spread initial copy operations across array groups and/or array domains (ACP pairs) to reduce initial copy time as well as host I/O contention. Example: Let s say the maximum initial copy activities setting is 4, and you add 6 TCz pairs at the same time (for LDEVs 00 through 05) with the initial copy priority set as follows: M-VOL of TCz pair Priority LDEV 03 1 LDEV 05 2 LDEV 00 3 LDEV 04 4 The MCU will start the initial copy operations for LDEVs 03, 05, 00, and 04 immediately, then start LDEV 01 when one of the first four initial copy operations is complete, and then start LDEV 02 when the next initial copy operation is Performing TrueCopy for z/os Pair Operations 6-9

220 LDEVs 01, 02 5 complete. If additional TCz pairs are added, the MCU also prioritizes the initial copy operations by time requested, so that all TCz pairs in the first group are started before any pair in the next group is started. Note: The CESTPAIR TSO command does not support the initial copy priority option. When CESTPAIR is used to establish TCz pairs, the initial copy operations are performed in the order that the CESTPAIR commands are issued. Note: If the time out error occurs during the Add Pair operation, the copy operation may not be executed correctly in the order that you have set with the Priority parameter. The time out error may be caused by the CU configuration or a remote copy path error. Review the error, release the pair with the error, and then retry the Add Pair operation. Difference management. Specifies the measurement method that TrueCopy for z/os will use to manage the differential data for the pair: auto, cylinder, or track. The default setting is Auto. When you select Auto, either Cylinder or Track is selected depending on the basic size of the logical volume image. DFW to R-VOL (TrueCopy for z/os Sync only). Specifies whether the MCU will suspend a TCz pair when the RCU cannot execute DFW to the R-VOL: DFW not required: the MCU will not suspend the TCz pair when DFW on the RCU is blocked. This option is recommended if you need to maintain synchronization of the TCz pair. Note: If a TCz pair is established using PPRC commands, the DFW to R-VOL option is set to not required. DFW required: the MCU will suspend the pair when DFW on the RCU is blocked. This option is recommended if you need to maintain high MCU I/O performance. Caution: The interaction of the DFW required setting and the M-VOL fence level setting can cause a host application to fail with a permanent I/O error when attempting to update an M-VOL. Keep track of which pairs have the DFW required setting, and make sure that DFW to the R-VOL is not blocked. Note: The DFW to R-VOL setting does not affect the I/O performance of the M-VOLs. If one side of cache is closed due to an RCU failure, the TCz copy operation still uses DFW. The only difference between not required and required is that new pairs cannot be established with the DFW-to-R- VOL required option when one side of RCU cache is closed (the add pair operation fails). C/T Group (TrueCopy for z/os Async only). Specifies the consistency group for the pair(s) being added. All TCzA pairs must be assigned to a consistency group. Note: The CESTPAIR command can be used to start TCzA pairs and assign them to groups, but the groups must already be configured (using the Add C/T Group dialog box Performing TrueCopy for z/os Pair Operations

221 Pair Options When you add new TrueCopy for z/os pairs, you select the pair options on the Add Pair dialog box. You can change the fence level, CFW data, and error level pair options after a pair has been added. You cannot change the difference management, DFW to R-VOL, or CT group of an existing pair. You need to release and then restart the pair to change any of these options. M-VOL Fence Level (TCz Synchronous only). Specifies the conditions under which the MCU will reject write operations to the M-VOL, which is known as fencing. This option is very important for disaster recovery planning. TCzA M-VOLs are never fenced. Data: the M-VOL will be fenced when the MCU cannot successfully execute an update copy operation for any reason. This setting is functionally equivalent to the CRIT(YES-ALL) parameter for the CESTPAIR command. Status: the M-VOL will be fenced only if the MCU is not able to change the R-VOL pair status to suspended when an update copy operation fails. If the MCU changes the R-VOL pair status to suspended, subsequent write operations to the M-VOL will be permitted, and the MCU will keep track of all updates to the M-VOL while the pair is suspended. This setting is functionally equivalent to the CRIT(YES-PATHS) parameter for the CESTPAIR command. Never: the M-VOL will never be fenced. If the TCz pair is suspended, write operations to the M-VOL will be accepted. This setting is functionally equivalent to the CRIT(NO) parameter for the CESTPAIR command. Note: For further information on the CESTPAIR CRIT parameter and its two modes of operation, CRIT(YES-PATHS) and CRIT(YES-ALL), please refer to the IBM document Advanced Copy Services (SC ) or DFSMS MVS V1 Remote Copy Guide and Reference (SC ). The CFW Data option specifies whether the CFW data will be copied to the R- VOL: Copy to R-VOL: the MCU will copy the CFW data to the R-VOL. Note: If a TrueCopy for z/os pair is established using PPRC commands, the CFW data option is set to the Copy to R-VOL setting. Note: By using Remote Copy Function Switch, you can set the following option with CESTPAIR: CFW data = only M-VOL. If you want to use this function, please contact your Hitachi account team. Only M-VOL: the MCU will not copy the CFW data to the R-VOL. This setting is recommended for two reasons: (1) copying the CFW data impacts storage system performance, (2) CFW data is typically used for temporary files (e.g., sort work datasets) which are not usually required for disaster recovery. Performing TrueCopy for z/os Pair Operations 6-11

222 Error Level option (Async only). Specifies the error level for the TCzA pair(s): Group: When the specified pair is suspended, all TCzA pairs in the same group will be suspended, even if the failure affects only that pair and not the entire group. Important: Select the Group error level for all TCzA volumes which are essential to disaster recovery. Suspended TCzA R-VOLs which have the Volume error level should not be used for disaster recovery. Volume: If the failure affects only the specified pair, then only that pair will be suspended. A failure that affects an entire group will always result in the suspension of all pairs in the group, as well as all other affected TCz pairs. Note: The CESTPAIR TSO command also allows you to specify the error level for TCzA pairs Performing TrueCopy for z/os Pair Operations

223 Changing Pair Options The Change Pair Option dialog box (see Figure 6-3) allows you to change the pair options of existing TrueCopy for z/os pairs. To open the Change Pair Option dialog box, click the Pair Operation tab, select a CU grouping or CU from the tree, select M-VOL from the list, right-click and click Change Pair Option command. Figure 6-3 Change Pair Option Dialog Box (Asynchronous) Volume: The LDKC number, the CU number, and the device ID. Note: If "#" is added to the end of the device ID like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. M-VOL Fence Level (Synchronous only): Select the fence level for the new pair(s). The fence level determines the conditions under which the MCU will reject write operations to the M-VOL. Never is automatically set for an asynchronous pair. Never: the M-VOL will never be fenced. Data: the M-VOL will be fenced when the MCU cannot successfully execute an update copy operation for any reason. Status: the M-VOL will be fenced only if the MCU is not able to change the R-VOL status to suspended when an update copy operation fails. Performing TrueCopy for z/os Pair Operations 6-13

224 CFW Data: specifies whether the CFW data will be copied to the R-VOL. Asynchronous Parameters (Async only): Error Level: error level for the new pair(s): Group, or Volume. Note: If you want to set the parameters on the multiple volumes at once without changing individual parameters per volume, make the box of parameters that you do not want to change blank. Only the parameters that you input will be changed. The Cancel button cancels the settings you have made and closes the Change Pair Option dialog box. The Set button sets the parameters and closes the Change Pair Option dialog box. To change the fence level, CFW data, or error level pair option for one or more pairs: 1. Connect to the MCU of the pair(s) for which you want to change the option(s), and open the TrueCopy for z/os Pair Operation window. 2. In the tree, select the CU or the upper CU grouping, which contains the M-VOL(s) of the pair(s). 3. In the list, select the pair(s) for which you want to change the pair option. When a port is selected in the tree, the pair(s) can be selected from the current Volume List. Select either TrueCopy for z/os Sync pairs or Async pairs (not both). Use the Display Filter as needed to display the desired pairs (e.g., select Async only). 4. Right-click, and click Change Pair Option to open the Change Pair Option dialog box (refer to Figure 6-3). 5. On the Change Pair Option dialog box, select the desired option(s) for the selected pair(s), and click Set to close the Change Pair Option dialog box. The preview list displays the requested change pair option operation(s). 6. Verify the requested operation(s) in the list. To change one or more operations, select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s), right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command or click the Cancel button. 7. To perform the operation(s), click Apply. If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed on the Error Code column in the preview list. To display an error message, select one LU, right-click, and click Error Detail. After you see the error message, click OK button to close the error message Performing TrueCopy for z/os Pair Operations

225 8. On the Pair Operation window, verify that the change pair option operation(s) completed successfully. Note: If an error occurs after you click Apply, you can display the error message by right-clicking on the operation and clicking the Error Detail command. Performing TrueCopy for z/os Pair Operations 6-15

226 Viewing TrueCopy for z/os Pair status The Detailed Information dialog box (see Figure 6-4) displays the detailed status of the selected pair. To open the Detailed Information dialog box, click the Pair Operation tab, select a CU grouping or CU from the tree, select the desired pair, right-click, and then click Detailed Information command. Note: The CQUERY TSO command can also be used to display pair status for TrueCopy for z/os Sync and Async pairs at the MCU and RCU. Figure 6-4 Detailed Information Dialog Box 6-16 Performing TrueCopy for z/os Pair Operations

227 M-VOL and R-VOL: LDKC number, CU number, and device ID Device emulation type Capacity (number of cylinders) Note: If "#" is added to the end of the device ID (i.e. 00:00:3F#), the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. CLPR: The CLPR number and the CLPR name of the volume on the primary site are displayed. Pair Status: Current TCz pair status of the selected volume: simplex, pending, duplex, or suspend, suspending, deleting. If the pair status is suspended, the suspend type and consistency status (TCzA only) are also displayed. Pair Synchronized: For pending duplex pairs, this value indicates the percent completion of the initial copy operation. For duplex TCz Synchronous pairs, this value is always 100% after the initial copy operation is complete. For TCzA pairs: For a duplex TCzA pair, this value indicates the number of cylinders/tracks (% of total) that are marked as modified in the bitmap for resynchronization. The total number of cylinders/tracks = the number of M-VOL cylinders/tracks (since the R-VOL can be larger than the M-VOL). For a suspended TCzA R-VOL, this value indicates the number of cylinders/tracks (% of total) containing recordsets lost at the RCU (reached the RCU but not settled before suspension). For a suspended TCzA M-VOL, this value indicates the number of cylinders/tracks (% of total) which contain: Tracks that have not yet been copied by the initial copy or resync copy operation (this applies only when suspended during initial copy or during resync copy) Records updated by the primary system after suspension Recordsets lost at the MCU (created but not sent to the RCU before suspension) Recordsets lost at the RCU (if the MCU can get this information from the RCU). RCU S/N and SSID: S/N and SSID of the RCU (or MCU if connected to the RCU). Controller ID: allows you to select the controller ID of the RCU. The controller ID for USP V is 5, the controller ID for TagmaStore USP/NSC is 4, and the controller ID for 9900V is 3. The model name is displayed next to the controller ID. Performing TrueCopy for z/os Pair Operations 6-17

228 MCU-RCU Path: Fibre. Update Type: Synchronous or asynchronous. Copy Pace: 3 tracks or 15 tracks (displayed during initial copy and resync copy). Initial Copy Priority: (displayed during initial copy and resync copy).note: 0 is the value for pairs created by CESTPAIR command or Business Continuity Manager. M-VOL Fence Level: Data, Status, or Never. R-VOL Write: Status of the R-VOL write suspend option (enabled or disabled). Pair Established: Date and time that the pair was established. Last Updated: Date and time that the pair status was last updated. Pair Copy Time: Time that was taken to copy pairs. Note: The time that is shown in Pair Copy Time differs from the time that is shown in Copy Time on the History window. To create a pair: 1. MCU receives a request to create a pair. 2. MCU receives a request to start the creating pair operation. 3. The creating pair operation is started according to the conditions of initial copy priority and maximum initial copy activities. Pair Copy Time on the Detailed Information dialog box shows the amount of time that has been needed from step 3 to the completion of the creating pair operation (i.e., the progress of the creating pair operation reaches 100%). Copy Time on the History window shows the amount of time that has been needed from step 1 to the completion of the creating pair operation. Difference Management: Auto, Cylinder or Track. CFW Data: Copy to R-VOL or Only M-VOL. DFW to R-VOL: Required or Not required. Check box, "Refresh the Pair Operation window after this dialog box is closed": To refresh the Pair Operation window after closing the Detailed Information dialog box, click the check box. By default, the check box is not selected. Asynchronous Parameters CT Group: Consistency group to which the TCzA pair is assigned. Error Level: Error level of the TCzA pair (Group or Volume). CT: Consistency time of the group (displayed only for the R-VOL). CT Type: Timer type (system, local, or none) for the TCzA group Performing TrueCopy for z/os Pair Operations

229 SEQCHK: Displayed when the TCzA pair has the SEQCHK status. This status is managed by the RCU, and the MCU may not have the most current information. Always use the R-VOL pair status information displayed at the RCU for disaster recovery. The Previous button displays the pair status information for the previous pair in the list (the pair in the row above). The Next button displays the pair status information for the next pair in the list (the pair in the row below). The Refresh button updates the pair status information. The Close button closes the Detailed Information dialog box. Note: The Display Filter settings can affect how Previous or Next is recognized. Note: The list displays a maximum of 4,096 rows at once. The Previous and Next buttons on the Detailed Information dialog box can only be used for the currently displayed 4,096 rows. Performing TrueCopy for z/os Pair Operations 6-19

230 Splitting TrueCopy for z/os Pairs The Suspend Pair dialog box (see Figure 6-5) allows you to suspend TCz pairs and select the suspend options for the pair. To open the Suspend Pair dialog box, click the Pair Operation tab, select a CU grouping or CU from the tree, select the desired pair, right-click, and then click Suspend Pair command. For further information on suspended pairs. Figure 6-5 Suspend Pair Dialog Box (Asynchronous) The suspend options are: Volume: Device ID of the selected M-VOL (R-VOL if connected to the RCU). Note: If "#" is added to the end of LDEV number like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide Performing TrueCopy for z/os Pair Operations

231 SSB [F/M=FB]: When this option is enabled (and PPRC Support = Yes), the MCU will notify all attached hosts (IEA494I message) that the pair was suspended. This option should always be enabled. Note: If PPRC support = No, the x FB sense information will not be reported to the host, even if the SSB (F/M = FB) suspend option is enabled. Suspend Kind (default = R-VOL): R-VOL: the M-VOL will accept all subsequent write I/O operations, and the MCU will keep track of updates while the pair is suspended. Subsequent write I/O operations to the M-VOL will be accepted or rejected depending on the fence level of the pair. This setting is available from the MCU and RCU, and should be used if you need to keep the M-VOL online. All TrueCopy for z/os Async pairs have this setting. This setting is functionally equivalent to CSUSPEND with the optional PRIMARY parameter (without QUIESCE). M-VOL Failure (available only for TrueCopy for z/os Sync and only when connected to the MCU): the MCU will reject all write I/O operations to the M-VOL while the pair is suspended, regardless of the M-VOL fence level setting. This setting should be used if you need to maintain synchronization of the TCz pair. This setting is functionally equivalent to CSUSPEND without the optional PRIMARY parameter. Asynchronous Parameters: Suspend Range: Group or Volume (default = Group when one pair is selected, default = Volume when two or more pairs are selected). The CSUSPEND TSO command supports the TCzA suspend range option. Group: The MCU/RCU will suspend all other pairs in the same consistency group as the selected pair. This option is available only when one pair is selected. Volume: The MCU/RCU will suspend only the specified pair(s) (even if the error level of the pair is group). Note: For the Volume suspend range setting, if you select pairs with duplex status and other than duplex status in the same consistency group, unexpected suspend may occur during the pair operations (suspend, resynchronize, release) under heavy I/O load conditions. You can estimate whether the I/O load is heavy or not from the rate of sidefile cache (around 30%), or if you cannot see the sidefile cache rate, from the frequency of host I/O. The suspend pair operations should be performed under light I/O load conditions. Pending Update: Drain or Purge (default = Drain). The CSUSPEND TSO command supports the TCzA pending update suspend option. Drain: As soon as the RCU accepts the Suspend Pair operation, the RCU will finish settling all pending recordsets for the pair. After settling all pending recordsets, if there are no recordsets for a fixed period of time, the MCU will change the pair status from Suspending to Suspended. Performing TrueCopy for z/os Pair Operations 6-21

232 Note: If there is no period of time without recordsets (i.e., recordsets continue to be generated), the RCU will discontinue the original Suspend Pair operation and forcibly suspend the pair. Purge: The MCU will change the pair status from Suspending to Suspend as soon as the RCU accepts the suspend pair operation. The MCU and RCU discard all pending recordsets and mark the cylinders/tracks that contain discarded recordsets as modified in the M- VOL and R-VOL bitmaps, respectively. When the pair is resynchronized, the M-VOL and R-VOL bitmaps will be merged at the MCU, and all cylinders/tracks marked as modified will be copied to the R-VOL. Note: If the MCU does not receive acknowledgement of the suspend operation from the RCU within the copy pending timeout setting, the MCU will forcibly suspend all affected TCz Async pairs and report an IEA491E host console message. WARNING: The QUIESCE option of the CSUSPEND command has been disabled by APAR OW15247 or APAR OW Refer to either of these APARs and the latest IBM PPRC documentation for detailed information on the QUIESCE option of the CSUSPEND command. Please check with your Hitachi account team before using the CSUSPEND command with the QUIESCE option to suspend TCz pairs on USP V storage systems. If the CSUSPEND command with the QUIESCE option is issued to certain volumes (e.g., active SPOOL, PAGE, or CATALOG datasets, active SYSRES volume), the attached host(s) may enter a deadlock condition and may require a storage control IML to correct the condition. TCzA does not support the CSUSPEND/QUIESCE option. Note: If you select a pair from the volume list and change the settings, and if you use a drop-down list to set blank to a parameter, the parameter takes the default value for each pair. If you select the settings from the preview list before applying the changed settings, and if you use a drop-down list to set blank to a parameter in the Suspend Pair dialog box, the parameter value in the preview list will not be changed. To suspend one or more TrueCopy for z/os pairs: 1. If you plan to suspend one or more TCzA pairs using the drain suspend option, you must STOP all application I/Os to the TCzA M-VOL(s) before suspending the pair(s). This ensures that all pending data in cache is written to the R-VOL(s) during pair suspension. You do not need to vary the M- VOL(s) offline. 2. Connect to the MCU or RCU of the pair(s) to be suspended, open the TrueCopy for z/os Pair Operation window. For TCz Synchronous, you must connect to the MCU. For TCzA, you can connect to the MCU or RCU. 3. In the tree, select the CU or the upper CU grouping, which contains the pair(s) to be suspended Performing TrueCopy for z/os Pair Operations

233 4. In the list, select the pair(s) that you want to suspend. Select either TrueCopy for z/os Sync or Async pairs (not both). If you plan to use the Group suspend option, select only one pair in the desired group. The pair status must be Duplex. Use the Display Filter as needed to display the desired pairs (e.g., select Duplex status and Async only). 5. Right-click, and click Suspend Pair to open the Suspend Pair dialog box (refer to Figure 6-5). 6. On the Suspend Pair dialog box, select the desired suspend options for the pair(s), and click Set to close the dialog box. The preview list displays the requested suspend operation(s). WARNING: Do not use the M-VOL failure suspend kind option if the M-VOL is required for system operation (e.g., spool, page, or SYSRES volume). Make sure to use the R-VOL suspend kind option, so that the M-VOL continues accepting I/Os. 7. Verify the requested operation(s) in the preview list. Make sure that the suspend options for each pair are correct. The suspend kind option (R-VOL or M-VOL failure) and fence level of the pair (never, data, or status) determine whether the M-VOL will accept write I/O operations after the pair is suspended. To change one or more operations, select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s), that you want to delete from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 8. To start the operation(s), click the Apply button. If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed on the Error Code column in the preview list. To display an error message, select one LU, right-click, and click Error Detail. After you see the error message, click OK button to close the error message. For TCz Synchronous pairs, the MCU will complete all M-VOL write operations in progress and the associated update copy operations at the R- VOL before suspending the pair, so that the pair is synchronized at the time of suspension. For TCz Asynchronous pairs, the pending update option (drain or purge) determines whether the pair is synchronized at the time of suspension. 9. On the Pair Operation window, verify that the suspend pair operation(s) is/are completed successfully (Suspend status in the list). To monitor the progress of the suspend pair operation(s), click File, and then Refresh on the menu bar of the Storage Navigator main window to update the information in the list, or use the Detailed Information dialog box to monitor the detailed status of each pair. You can also monitor the host console messages (IEA494I vs. IEA491E) to verify the operation(s). Performing TrueCopy for z/os Pair Operations 6-23

234 Resynchronizing TrueCopy for z/os Pairs While a TCz pair is suspended, the MCU does not perform any update copy operations. For a suspended TCz Synchronous pair, the MCU may or may not continue accepting write I/Os for the M-VOL depending on the M-VOL fence level and suspend kind option (if user-requested). If the MCU accepts write I/Os for a suspended M-VOL, the MCU records the data in the M-VOL tracks that are updated while the pair is suspended as a differential data, and copies the outof-sync tracks to the R-VOL when the pair is resynchronized. If you use an earlier storage system model than USP V as RCU, the VOLSER is also copied. For a suspended TCz Asynchronous pair, the MCU and RCU keep track of any recordsets that were discarded during suspension, and the MCU continues accepting write I/Os for the M-VOL. When a TCzA pair is resynchronized, the MCU merges the M-VOL and R-VOL differential data and then copies the outof-sync tracks to the R-VOL to resynchronize the pair. If you use an earlier storage system model than USP V as RCU, the VOLSER is also copied. The Resume Pair dialog box (see Figure 6-6) allows you to resynchronize suspended TCz pairs. To open the Resume Pair dialog box, click the Pair Operation tab, select a CU grouping or CU from the tree, select the M-VOL(s) of the pair(s) to be resynchronized, right-click, and then click Resume Pair. Figure 6-6 Resume Pair Dialog Box 6-24 Performing TrueCopy for z/os Pair Operations

235 The resynchronize options are: M-VOL: the LDKC number, CU number, and device ID of the selected M- VOL. If you selected more than one M-VOL, the M-VOL with the lowest device ID is displayed. Note: If "#" is added to the end of the device ID like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. M-VOL Fence Level (sync only): if desired, you can change the fence level of the pair(s). Initial Copy Parameters: Copy Pace (3 or 15): select the number of the tracks for the resynchronize operation(s) (default = 15). Priority (from 0 to 256): set the desired priority (0-256) (scheduling order) for the resynchronize operations (default = 32). Note: 0 is the value for pairs created by CESTPAIR command or Business Continuity Manager. Asynchronous Parameters: Resume Range (default = Group): Group: all suspended TrueCopy for z/os Async pairs in the same group as the selected pair will be resynchronized. Volume: only the selected TrueCopy for z/os Async pair(s) will be resynchronized. Note: For the Volume resynchronize range setting, if you select pairs with duplex status and other than duplex status in the same consistency group, unexpected suspend may occur during the pair operations (suspend, resynchronize, release) under heavy I/O load conditions. You can estimate whether the I/O load is heavy or not from the rate of sidefile cache (around 30%), or if you cannot see the sidefile cache rate, from the frequency of host I/O. The resynchronize pair operations should be performed under light I/O load conditions. Error Level: if desired, you can change the error level of the pair(s). This option is available only when the Volume Resume Range option is selected. Note: If an MCU or RCU is powered off and its backup batteries are fully discharged while TrueCopy for z/os pairs are suspended, the M-VOL/R-VOL differential data will not be retained. In this unlikely case, the MCU/RCU will mark all tracks of all suspended TrueCopy volumes as modified, so that the MCU will perform the equivalent of an entire initial copy operation when the pairs are resynchronized. (The R-VOL cylinder/track map is used only for TCz Asynchronous operations.) Note: The CESTPAIR (MODE=RESYNC) command can be used to resynchronize suspended TCz Synchronous and TCzA pairs. Performing TrueCopy for z/os Pair Operations 6-25

236 Note: If you select a pair from the volume list and change the settings, and if you use a drop-down list to set blank to a parameter, the parameter takes the default value for each pair. If you select the settings from the preview list before applying the changed settings, and if you use a drop-down list to set blank to a parameter in the Resume Pair dialog box, the parameter value in the preview list will not be changed. To resynchronize one or more suspended TrueCopy for z/os pairs: 1. Determine if any data on the R-VOL has changed while the pair has been suspended. If so, do not resynchronize the pair. You must release the pair from the MCU and then restart the pair using the Entire initial copy mode option to resynchronize the M-VOL and R-VOL. 2. If any pair was suspended due to an error condition (use the Detailed Information dialog box to view the suspend type), make sure that the error condition has been removed. The MCU will not resynchronize the pair(s) until the error condition has been removed. 3. Connect to the MCU of the pair(s) to be resynchronized, open the TrueCopy for z/os Pair Operation window. 4. In the tree, select the CU or the upper CU grouping, which contains the pair(s) to be resynchronized. Use the Display Filter as needed to display the desired pairs (e.g., select Async and Suspend status only). 5. In the list, select the M-VOL(s) of the pair(s) to be resynchronized. Select either Sync or Async pairs (not both). If you want to use the Group Resume Range option (async only), select only one pair in the group. 6. Right-click, and click Resume Pair to open the Resume Pair dialog box (refer to Figure 6-6). 7. On the Resume Pair dialog box, select the desired resynchronize options, and click Set to close the dialog box. The preview list displays the requested resynchronize pair operation(s). Note: If you want to resynchronize all suspended pairs in a consistency group, select the Group Resume Range option. 8. Verify the requested operation(s) in the preview list. Make sure that the resynchronize options for each pair are correct. To change one or more operations, select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s) from the preview list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. Note: If you selected the Group Resume Range option, time-saving mode is not available. 9. To start the operation(s), click Apply Performing TrueCopy for z/os Pair Operations

237 If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed on the Error Code column in the preview list. To display an error message, select one LU, right-click, and click Error Detail. After you see the error message, click OK button to close the error message. 10. On the Pair Operation window, verify that the resynchronize pair operation(s) is/are completed successfully (Pending and then Duplex status in the list). To monitor the progress of the resynchronize pair operation(s), click File, and then Refresh on the menu bar of the Storage Navigator main window to update the information in the list, or use the Detailed Information dialog box to monitor the detailed status of each pair. You can also monitor the host console messages (IEA494I vs. IEA491E) to verify the operation(s). Performing TrueCopy for z/os Pair Operations 6-27

238 Releasing TrueCopy for z/os Pairs A TrueCopy for z/os pair should be released from the MCU only when it is no longer necessary to maintain a remote copy of the M-VOL. When a TCz pair is released from the MCU, the MCU stops all TCz copy operations for that pair and changes the pair status of the M-VOL and R-VOL to simplex. After a pair is released, the MCU continues to accept all subsequent write I/O operations to the M-VOL and will not keep track of the M-VOL updates. A TCz pair should be released from the RCU only if you need to access the R- VOL, for example, to perform ICKDSF on the R-VOL or for disaster recovery. When a TCz pair is released from the RCU, the RCU changes the R-VOL pair status to simplex but does not change the pair status of the corresponding M- VOL. When the MCU performs the next TCz operation, the MCU detects that the R-VOL status changed and changes the status of the M-VOL to suspendeddelete pair to RCU. When you release a pair from the RCU in order to access the R-VOL, remember that the R-VOL and M-VOL have the same VOLSER, and take appropriate precautions to prevent a system problem due to duplicate VOLSERs. To restart a pair which was released from the RCU, you must first release the pair from the MCU, and then add the pair from the MCU using the appropriate initial copy option (Entire Volume or None) to restart the pair. You can release all TCz Synchronous pairs between an MCU and RCU (same CU). You can also release all TCzA pairs in a consistency group by connecting to the MCU. The TCzA pair status will change to deleting when the delete operation is accepted by the MCU and RCU, and then to simplex after the internal release pair process is complete. In addition, you can release TCzA pairs according to their consistency status (e.g., for disaster recovery) by connecting to the RCU (the RCU maintains the consistency status). Note: The CDELPAIR TSO command can be used to release TCz pairs and TCzA groups of pairs from the MCU. WARNING: Please see the warning about duplicate VOLSERs. WARNING: As a general rule, when you want to release a TrueCopy for z/os Async pair from the MCU, it is strongly recommended that you perform the release pair operation after the update copy operation is completed. If you request the release pair operation while the update copy process is still in progress, it may take a long time to complete the operation. However, when you urgently need to release a TCz Asynchronous pair, you can perform the release pair operation from the RCU. In this case, you will find the suspended status at the MCU after performing the release pair operation from the RCU Performing TrueCopy for z/os Pair Operations

239 The Delete Pair dialog box (see Figure 6-7) allows you to release one or more TCz pairs and select the release options for the pair(s). To open the Delete Pair dialog box, click the Pair Operation tab, select a CU grouping or CU from the tree, select the desired pair(s), right-click, and then click Delete Pair command. Figure 6-7 Delete Pair Dialog Box (Asynchronous) Note: If you select a pair from the volume list and change the settings, and if you use a drop-down list to set blank to a parameter, the parameter takes the default value for each pair. If you select the settings from the preview list before applying the changed settings, and if you use a drop-down list to set blank to a parameter in the Delete Pair dialog box, the parameter value in the preview list will not be changed. Volume: the device ID of the selected volume. If you selected more than one volume, the volume with the lowest device ID is displayed. Note: If "#" is added to the end of the device ID like 00:00:3F#, the LDEV that the LDEV number indicates is an external volume. For details on an external volume, please refer to the Universal Volume Manager User's Guide. Deleting Mode: Normal: performs a normal release pair operation for the selected pair(s). The pair(s) will only be released if the MCU is able to change the pair status of the M-VOL and R-VOL to Simplex. All: allows you to release all TCz Synchronous pairs with the same MCU and RCU (same CU) as the selected pair. This option can be selected from the MCU or RCU. This option releases the pairs more quickly than if you select all pairs on the TCz windows and release them. Performing TrueCopy for z/os Pair Operations 6-29