hitachi virtual storage platform g1000 · aix, as/400, db2, domino, ds6000, ... 7-1 monitoring pair...

Product Version

Contents

Getting Help

FASTFIND LINKS

Hitachi Virtual Storage Platform G1000Hitachi TrueCopy® for Mainframe User Guide

MK-92RD8018-02

© 2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,electronic or mechanical, including photocopying and recording, or stored in a database or retrievalsystem for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice andassumes no responsibility for its use. This document contains the most current information availableat the time of publication. When new or revised information becomes available, this entiredocument will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions ofthe applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products isgoverned by the terms of your agreements with Hitachi Data Systems Corporation.

Notice on Export Controls: The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. HitachiData Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States andother countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform areregistered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server,ESCON, FICON,FlashCopy, IBM, Lotus, MVS, RS/6000, S/390,System z9, System z10, Tivoli, VM/ESA, z/OS, z9,z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International BusinessMachines Corporation.>

All other trademarks, service marks, and company names in this document or website areproperties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

iiHitachi TrueCopy® for Mainframe User Guide

https://portal.hds.com

Contents

Preface.................................................................................................. ixIntended audience..................................................................................................... xProduct version..........................................................................................................xRelease notes............................................................................................................ xDocument revision level..............................................................................................xChanges in this revision..............................................................................................xReferenced documents.............................................................................................. xiDocument conventions.............................................................................................. xiConvention for storage capacity values...................................................................... xiiAccessing product documentation............................................................................. xiiiGetting help............................................................................................................ xiiiComments...............................................................................................................xiii

1 TrueCopy for Mainframe overview..........................................................1-1How TrueCopy for Mainframe works ........................................................................1-3Typical components ............................................................................................... 1-3Storage systems..................................................................................................... 1-4Volume pairs ......................................................................................................... 1-5Data path ..............................................................................................................1-5Consistency groups ................................................................................................1-5Interfaces ............................................................................................................. 1-6Failover software ................................................................................................... 1-6Error reporting communications .............................................................................. 1-7Overview of initial, update copy operations ..............................................................1-7

Initial copy ......................................................................................................1-7Update copy ....................................................................................................1-8

Pair status..............................................................................................................1-8

2 Requirements and specifications............................................................ 2-1System requirements and specifications....................................................................2-2Business Continuity Manager specifications ..............................................................2-4

Options not supported by Business Continuity Manager.......................................2-4Command device .............................................................................................2-5F/M = FB message output control option ...........................................................2-6

PPRC specifications, restrictions .............................................................................. 2-6

iiiHitachi TrueCopy® for Mainframe User Guide

TrueCopy for Mainframe operations performed with PPRC .................................. 2-6TrueCopy for Mainframe options not supported with PPRC ..................................2-7PPRC, BCM command comparison......................................................................2-8

SAID values for CESTPATH/YKBLDPTH..................................................................... 2-9P/DAS support, restrictions ................................................................................... 2-12

Restrictions.................................................................................................... 2-12GDPS support ...................................................................................................... 2-12RMF PPRC link path statistical information support.................................................. 2-13Planning for Basic HyperSwap function—TPC-R support .......................................... 2-16

Requirements................................................................................................. 2-16Recommendations.......................................................................................... 2-17

Planning for Extended Address Volume...................................................................2-17CCI support for TrueCopy for Mainframe operations................................................ 2-18

Supported operations and options ...................................................................2-18

3 Planning for TrueCopy for Mainframe..................................................... 3-1Storage system preparation.....................................................................................3-2

Cache, additional shared memory requirements..................................................3-2DASD fast write requirements............................................................................3-3Requirements for VSP G1000 with earlier model storage systems.........................3-3S-VOL Read and other system options................................................................3-3

System performance considerations......................................................................... 3-5Determining Round Trip Time............................................................................3-6Determining Minimum Number of Remote Paths................................................. 3-8Analyzing workload, planning data paths............................................................3-8

Planning pairs and pair volumes...............................................................................3-9Pair volume requirements and recommendations.............................................. 3-10Precautions for duplicate VOLSERs...................................................................3-12Allowing I/O to the S-VOL............................................................................... 3-12Allowing I/O to the P-VOL after a split—Fence Level options.............................. 3-13Differential data .............................................................................................3-14Maximum number of pairs supported............................................................... 3-14

Calculating maximum number of pairs.................................................... 3-14Priority for initial copy operations and scheduling order..................................... 3-15

Example 1: more initial copies than previously specified........................... 3-16Example 2: initial copy started, new pairs added......................................3-16

Consistency group planning................................................................................... 3-17Consistency group for pairs in one primary and one secondary VSP G1000......... 3-17Consistency group for pairs in multiple primary and secondary systems.............. 3-18Consistency group requirements ..................................................................... 3-19

Requirements for a CTG for one primary and one secondary system......... 3-20Requirements for a CTG for multiple primary and secondary systems........ 3-20

Assigning pairs to a consistency group............................................................. 3-21Assigning pairs belonging to one primary and secondary system...............3-21Assigning pairs belonging to multiple primary and secondary systems....... 3-21

Split behaviors for pairs in a CTG..................................................................... 3-22Host access after split............................................................................3-24Pair status before and after a split operation........................................... 3-24

Notes when you remove or resynchronize pairs by Business Continuity Manager. 3-25Error reporting communications............................................................................. 3-25Data path requirements and configurations.............................................................3-26

Bandwidth requirements..................................................................................3-26

ivHitachi TrueCopy® for Mainframe User Guide

Fibre Channel requirements.............................................................................3-26Supported data path configurations..................................................................3-27

Direct connection.................................................................................. 3-28Switch connection................................................................................. 3-29Extender connection.............................................................................. 3-29

Ports..............................................................................................................3-30Port requirements .................................................................................3-30Port attributes.......................................................................................3-31

4 Sharing TrueCopy for Mainframe volumes.............................................. 4-1Volume types that can be shared with TrueCopy for Mainframe................................. 4-2Cache Residency Manager....................................................................................... 4-4Compatible XRC and CC.......................................................................................... 4-4Dynamic Provisioning for Mainframe ........................................................................4-5Performance Monitor...............................................................................................4-6ShadowImage for Mainframe...................................................................................4-7

Configurations with ShadowImage for Mainframe P-VOLs.................................... 4-7Configurations with ShadowImage for Mainframe S-VOLs....................................4-8Status reporting and data currency.................................................................... 4-8

Universal Replicator for Mainframe...........................................................................4-9Virtual LVI............................................................................................................ 4-10Volume Migration .................................................................................................4-10

Restrictions.................................................................................................... 4-10Volume Retention Manager....................................................................................4-11

5 TCz configuration..................................................................................5-1Configuration workflow........................................................................................... 5-2Defining port attributes........................................................................................... 5-2Adding remote connection.......................................................................................5-3Setting number of vols. copied, path blockade, other options.....................................5-6Changing SCP time................................................................................................. 5-8

6 TCz pair operations...............................................................................6-1Pair operations workflow......................................................................................... 6-2Checking pair status................................................................................................6-2Creating pairs.........................................................................................................6-3Splitting pairs......................................................................................................... 6-6Resynchronizing pairs..............................................................................................6-7Deleting pairs......................................................................................................... 6-9

7 Monitoring and maintaining the TCz system............................................7-1Monitoring pair status, license capacity.....................................................................7-2

How pair status changes................................................................................... 7-3Pair status definitions........................................................................................7-3

CCI pair status names............................................................................. 7-5Split types.............................................................................................. 7-5System behavior..................................................................................... 7-7

Monitoring TCz pair synchronous rate.......................................................................7-8Monitoring TCz operations history............................................................................ 7-8

Operation descriptions...................................................................................... 7-9

vHitachi TrueCopy® for Mainframe User Guide

Changing P-VOL Fence Level, CFW Data.................................................................7-10Forcibly deleting pairs............................................................................................7-11Saving pair information to a text file ......................................................................7-12Monitoring and maintaining remote connections and paths ..................................... 7-12

Remote path status definitions.........................................................................7-14Configuring additional remote paths.................................................................7-15Changing minimum paths, round trip time, other remote connection options.......7-16Deleting remote paths.....................................................................................7-17

Adding, removing SSIDs on the secondary system...................................................7-18Deleting TrueCopy for Mainframe...........................................................................7-20ICKDSF Considerations for TCz Volumes................................................................. 7-21

ICKDSF on a TCz P-VOL.................................................................................. 7-21ICKDSF on a TCz S-VOL.................................................................................. 7-22

Managing power-off for systems and network devices............................................. 7-22General information........................................................................................ 7-22Planned outage of the primary system............................................................. 7-23Planned outage of the secondary system or remote path...................................7-23Planned outage of both primary and secondary systems....................................7-23

ICKDSF media maintenance...................................................................................7-24

8 Data migration..................................................................................... 8-1Migration overview..................................................................................................8-2

Migrating data..................................................................................................8-2

9 Disaster recovery..................................................................................9-1Disaster recovery overview......................................................................................9-2

Sense information shared between sites.............................................................9-2File and database recovery................................................................................9-3CSUSPEND/QUIESCE TSO command.................................................................. 9-3IEA494I system console message...................................................................... 9-3

Switching operations to the secondary site............................................................... 9-4Checking S-VOL consistency with the P-VOL....................................................... 9-5

Transferring operations back to the primary site....................................................... 9-6

10 Troubleshooting................................................................................10-1Error codes and messages..................................................................................... 10-2General troubleshooting........................................................................................ 10-2Remote path status problems................................................................................ 10-3Split pair problems................................................................................................ 10-5Changing microcode problem.................................................................................10-7Troubleshooting using CCI.....................................................................................10-7

SSB2 error codes when SSB1 = 2E31/B901/B90A/B90B/B912/D004................... 10-8SSB2=B992 error codes when SSB1 = B901 or B90A.......................................10-18

Service Information Messages (SIMs)................................................................... 10-18TPC-R troubleshooting ........................................................................................10-18

Resynchronization fails due to shortage of host resources................................10-19Cache failure, unregistered TPC-R error .........................................................10-19

Pinned track recovery..........................................................................................10-19Calling the Hitachi Data Systems Support Center................................................... 10-19

viHitachi TrueCopy® for Mainframe User Guide

A Pair operations using PPRC................................................................... A-1Overview of PPRC commands.................................................................................. A-2

Options not supported by PPRC.........................................................................A-3Requirements, restrictions, and notes...................................................................... A-3Conventions used in TSO commands........................................................................A-5CESTPATH command.............................................................................................. A-6

Requirements...................................................................................................A-6CESTPATH command syntax............................................................................. A-6CESTPATH parameters......................................................................................A-6

I/O control after failure—with CGROUP FREEZE/RUN ............................................... A-7CGROUP and FREEZE/RUN requirements............................................................A-8

Pair status before and after CGROUP FREEZE/RUN....................................A-9Using CGROUP................................................................................................. A-9

Command sequence example.................................................................A-10Other TSO commands used with CGROUP...............................................A-10Example output for CQUERY.................................................................. A-11

IEA494I and IEA491E console messages................................................................ A-13IEA494I message........................................................................................... A-13IEA491E message...........................................................................................A-14VSP G1000 response characteristics to failure conditions................................... A-14

GDPS and TrueCopy for Mainframe features............................................A-18

B TCz CLI reference.................................................................................B-1Configuration commands and options.......................................................................B-2Pair operation commands and options......................................................................B-3Monitoring commands and options...........................................................................B-5Maintenance commands and options........................................................................B-5

C TCz GUI reference................................................................................C-1Replication window.................................................................................................C-3Remote Replication window.....................................................................................C-5Remote Connections window................................................................................. C-14Add Remote Connection wizard..............................................................................C-18

Add Remote Connection window......................................................................C-18Add Remote Connection confirmation window.................................................. C-21

View Remote Connection Properties window...........................................................C-22Remove Remote Connection window......................................................................C-24Edit Remote Connection Options wizard..................................................................C-24

Edit Remote Connection Options window..........................................................C-25Edit Remote Connection confirmation window...................................................C-26

Add Remote Paths wizard......................................................................................C-27Add Remote Paths window..............................................................................C-27Add Remote Paths confirmation window...........................................................C-28

Remove Remote Paths wizard................................................................................C-29Remove Remote Paths window........................................................................C-29Remove Remote Paths confirmation window.....................................................C-31

Edit Remote Replica Options wizard....................................................................... C-32Edit Remote Replica Options window............................................................... C-32Change CU Options window............................................................................ C-35Edit Remote Replica Options confirmation window............................................ C-36

Edit SCP Time wizard............................................................................................ C-37

viiHitachi TrueCopy® for Mainframe User Guide

Edit SCP Time window.................................................................................... C-37Change SCP Time window...............................................................................C-38Edit SCP Time confirmation window................................................................. C-38

Create Pairs wizard............................................................................................... C-38Create TC Pairs window or Create UR Pairs window.......................................... C-38Change Settings window................................................................................. C-44Create Pairs confirmation window.................................................................... C-46

Split Pairs wizard.................................................................................................. C-48Split Pairs window.......................................................................................... C-48Split Pairs confirmation window....................................................................... C-50

Resync Pairs wizard.............................................................................................. C-51Resync Pairs window...................................................................................... C-52Resync Pairs confirmation window................................................................... C-54

Delete Pairs wizard............................................................................................... C-55Delete Pairs window....................................................................................... C-55Delete Pairs confirmation window.................................................................... C-58

Force Delete Pairs (TC Pairs) window..................................................................... C-59Edit Pair Options wizard........................................................................................ C-60

Edit Pair Options window.................................................................................C-60Edit Pair Options confirmation window............................................................. C-61

View Pair Properties (Remote) window................................................................... C-62View Pair Synchronous Rate window...................................................................... C-65Add SSIDs wizard................................................................................................. C-66

Add SSIDs window......................................................................................... C-66Add SSIDs confirmation window...................................................................... C-68

Remove SSIDs wizard........................................................................................... C-69Remove SSIDs window................................................................................... C-69Remove SSIDs confirmation window................................................................ C-70

Histories window.................................................................................................. C-71

Glossary

Index

viiiHitachi TrueCopy® for Mainframe User Guide

Preface

Hitachi TrueCopy® for Mainframe helps you create and maintain asynchronous backup of critical data in a remote location. This documentdescribes and provides instructions for planning, configuring, and maintaininga TrueCopy for Mainframe system on Hitachi Virtual Storage Platform G1000(VSP G1000) storage systems.

Please read this document carefully to understand how to use this product,and maintain a copy for reference purposes.

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Changes in this revision

□ Referenced documents

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

Preface ixHitachi TrueCopy® for Mainframe User Guide

Intended audienceThis document is intended for system administrators, Hitachi Data SystemsSupport Center, and authorized service providers who install, configure, andoperate the Hitachi Virtual Storage Platform G1000 storage system.

Readers of this document should be familiar with the following:

• Data processing and understands RAID systems and their basic functions.• The Hitachi Virtual Storage Platform G1000 system and has read the

Hitachi Virtual Storage Platform G1000 Hardware Guide.• The Hitachi Command Suite software and the Hitachi Command Suite

User Guide and/or the Hitachi Device Manager - Storage Navigatorsoftware and the VSP G1000 Mainframe System Administrator Guide.

• Remote replication and disaster recovery configurations for enterprisestorage data centers.

Product versionThis document revision applies to VSP G1000 microcode 80-02-0x or later.

Release notesThe Hitachi Virtual Storage Platform G1000 Release Notes are available onthe Hitachi Data Systems Portal: https://portal.hds.com. Read the releasenotes before installing and using this product. They may containrequirements or restrictions that are not fully described in this document orupdates or corrections to this document.

Document revision levelRevision Date Description

MK-92RD8018-00 April 2014 Initial release.

MK-92RD8018-01 August 2014 Supersedes and replaces MK-92RD8018-00

MK-92RD8018-02 October 2014 Supersedes and replaces MK-92RD8018-01

Changes in this revision• Global-active device support is added throughout the manual.• The Priority (Initial Copy Priority) and Entire Copy (Entire Volume) fields

are renamed under the Options step in Creating pairs on page 6-3.• SSB2 error codes are added, deleted and corrected in Troubleshooting

using CCI on page 10-7.• The description is updated in Overview of PPRC commands on page A-2.

x PrefaceHitachi TrueCopy® for Mainframe User Guide

https://portal.hds.com

• The TC Pairs tab is updated with information about Encryption in TC Pairstab on page C-6.

• Information about the Quorum Disks tab is added in Remote Connectionswindow on page C-14 .

• The table is updated in Checking S-VOL consistency with the P-VOL onpage 9-5.

• Information for link speeds up to 16 Gbps is added throughout themanual.

• Added FCoE and Mixed channel types in Remote Connection Propertiestable on page C-23

• Updated screenshots.

Referenced documentsHitachi Virtual Storage Platform G1000 documentation:

• VSP G1000 Product Overview, MK-92RD8051• Hitachi Virtual Storage Platform G1000 Hardware Guide, MK-92RD8007• Hitachi Universal Replicator for Mainframe User Guide, MK-92RD8022• Hitachi ShadowImage® for Mainframe User Guide, MK-92RD8020• Hitachi Thin Image User Guide, MK-92RD8011• Hitachi Compatible FlashCopy® User Guide, MK-92RD8010• Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe

Systems, MK-92RD8013• Hitachi Command Suite User Guide, MK-90HC172• Hitachi Virtual Storage Platform G1000 Mainframe System Administrator

Guide, MK-92RD8016 (for mainframe-only environments)

Document conventionsThis document uses the following terminology conventions:

Convention Description

Hitachi VirtualStorage PlatformG1000, VSP G1000

Unless otherwise noted, these terms refer to all models of theHitachi Virtual Storage Platform G1000 storage system.

Important Procedures in this manual are tailored to the Device Manager -Storage Navigator (HDvM - SN) GUI. When using this GUI, "LocalStorage System" displays for the system you have accessed onthe HDvM - SN server.As a result, if you access the secondary site's HDvM - SN server,the GUI displays "Local Storage System" to refer to the pair'sremote (secondary) system. Likewise, the GUI in this caseidentifies the storage system connecting to the accessed systemas the "Remote Storage System".

Preface xiHitachi TrueCopy® for Mainframe User Guide

This document uses the following typographic conventions:

Convention Description

Regular text bold In text: keyboard key, parameter name, property name,hardware label, hardware button, hardware switchIn a procedure: user interface item

Italic Variable, emphasis, reference to document title, called-out term

Screen text Command name and option, drive name, file name, folder name,directory name, code, file content, system and applicationoutput, user input

< > (angle brackets) Variable (used when italic is not enough to identify variable)

[ ] (square brackets) Optional value

{ } (braces) Required or expected value

| (vertical bar) Choice between two or more options or arguments

This document uses the following icons to draw attention to information:

Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions forperforming tasks more effectively.

Note Provides information that is essential to the completion of atask.

Caution Warns that failure to take or avoid a specified action canresult in adverse conditions or consequences (for example,loss of access to data).

WARNING Warns the user of severe conditions, consequences, or both(for example, destructive operations).

Convention for storage capacity valuesPhysical storage capacity values (such as, disk drive capacity) are calculatedbased on the following values:

Physical capacity unit Value

1 KB 1,000 bytes

1 MB 1,0002 bytes

1 GB 1,0003 bytes

1 TB 1,0004 bytes

1 PB 1,0005 bytes

xii PrefaceHitachi TrueCopy® for Mainframe User Guide

Physical capacity unit Value

1 EB 1,0006 bytes

Logical storage capacity values (such as, logical device capacity) arecalculated based on the following values:

Logical capacity unit Value

1 KB 1,024 bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

1 block 512 bytes

Accessing product documentationThe VSP G1000 user documentation is available on the HDS Support Portal:https://hdssupport.hds.com. Please check this site for the most currentdocumentation, including important updates that may have been made afterthe release of the product.

Getting helpThe HDS customer support staff is available 24 hours a day, seven days aweek. If you need technical support, log on to the HDS Support Portal forcontact information: https://hdssupport.hds.com

CommentsPlease send us your comments on this document: [email protected] the document title, number, and revision. Please refer to specificsections and paragraphs whenever possible. All comments become theproperty of Hitachi Data Systems Corporation.

Thank you! (All comments become the property of HDS.)

Preface xiiiHitachi TrueCopy® for Mainframe User Guide

https://hdssupport.hds.com


mailto:[email protected]

xiv PrefaceHitachi TrueCopy® for Mainframe User Guide

1TrueCopy for Mainframe overview

A TrueCopy for Mainframe system creates and maintains a mirror image of aproduction volume at a remote location. Data in a TrueCopy for Mainframebackup stays synchronized with the data in the primary Virtual StoragePlatform G1000 storage system. This happens when data is written from thehost to the primary storage system then to the secondary storage system,via the Fibre Channel data path. The host holds subsequent output untilacknowledgement is received from the secondary storage system for theprevious output.

This guide provides instructions for planning, configuring, operating,maintaining, and troubleshooting a TrueCopy for Mainframe system.

Important: Procedures in this manual are tailored to the Device Manager -Storage Navigator (HDvM - SN) GUI. When using this GUI, "Local StorageSystem" displays for the system you have accessed on the HDvM - SN server.

As a result, if you access the secondary site's HDvM - SN server, the GUIdisplays information for the pair's remote (secondary) system under "LocalStorage System". Likewise, the GUI in this case identifies the storage systemconnecting to the accessed system as the "Remote Storage System".

□ How TrueCopy for Mainframe works

□ Typical components

□ Storage systems

□ Volume pairs

□ Data path

□ Consistency groups

□ Interfaces

TrueCopy for Mainframe overview 1-1Hitachi TrueCopy® for Mainframe User Guide

□ Failover software

□ Error reporting communications

□ Overview of initial, update copy operations

□ Pair status

1-2 TrueCopy for Mainframe overviewHitachi TrueCopy® for Mainframe User Guide

How TrueCopy for Mainframe worksA pair is created when you:

• Select a volume on the primary storage system that you want to copy.• Create or identify the volume on the secondary system that will contain

the copy.• Connect the primary and secondary storage systems with a Fibre Channel

channel data path.• Copy all primary system data to the secondary volume.

During a typical initial copy, all data written to the primary volume (P-VOL) iscopied to the secondary volume (S-VOL), ensuring that the secondary copy isa complete and consistent backup.

When a pair is split, writes to the P-VOL continue but are no longer copied tothe S-VOL, and the pair is no longer synchronized.

• You can enable read/write from secondary host to S-VOL during pair split.• Changes to P-VOL and S-VOL (if applicable) are tracked by differential

bitmaps until the pair is resynchronized.• When resynchronization takes place, only the changed data is transferred,

reducing copy time.

The VSP G1000 transfers control parameters and FBA-format data forconsecutive, updated records in a track using a single write operation. Thiseliminates the overhead that is usually required for performing FBA-to-CKDand CKD-to-FBA conversions.

When TrueCopy for Mainframe operations and other storage systemprocessing are performed at the same time, performance is affected.

To plan and implement a TrueCopy for Mainframe system an understandingof its components is required. This is provided in the following sections.

Typical components A typical configuration consists of the following components. Many but not allrequire user setup.

• The primary VSP G1000 is connected to a host. The secondary storagesystem is connected to the primary system via Fibre Channel data paths.The secondary system may be VSP G1000 or other Hitachi model.

• A host at the primary site, connected to the primary storage system. It isalso highly desirable to have a host at the secondary site connected tothe secondary system for use in a disaster recovery. If this is notpossible, the host at the primary site must be in communication with thesecondary system.

• A P-VOL on the primary storage system that is copied to the S-VOL on thesecondary system.


• Fibre Channel data paths for data transfer between primary andsecondary system.

• Target, initiator, and RCU target ports for the Fibre Channel interface.• Device Manager - Storage Navigator graphical user interface software,

used to perform TrueCopy for Mainframe configuration and pairoperations. Business Continuity Manager (BCM), Command ControlInterface (CCI), and PPRC commands can be used for pair operations.

The following figure shows a typical TrueCopy for Mainframe environment.

Storage systemsTrueCopy for Mainframe operations take place between the primary VSPG1000 and the secondary system, which can be another Virtual StoragePlatform G1000, Virtual Storage Platform, or Universal Storage PlatformV/VM.

The primary system manages the P-VOL and the following operations:

• Host I/O operations to the P-VOL.• Initial copy and update copy operations between the P-VOL and S-VOL.• Pair status and configuration information.

The secondary system manages the S-VOL and the following operations:


• Secondary copy operations issued by the primary system.• Assists in managing pair status and configuration (for example, rejects

write I/Os to the S-VOL).

The primary system communicates with the secondary system over dedicatedFibre Channel data paths.

The VSP G1000 CU can function simultaneously as a primary system for oneor more P-VOLs, and as a secondary system for one or more S-VOLs. Thiskind of configuration requires that data paths and Fibre Channel ports areconfigured for both copy directions.

Volume pairs As described previously, original data is stored in the P-VOL and the remotecopy is stored in the S-VOL. The pair can be split, resynchronized, reverseresynchronized, and returned to unpaired status.

• When paired, the volumes are synchronized.• When split, new data is sent to the P-VOL but not the S-VOL.• When resynchronized, data that changed while the pair was split is copied

to the S-VOL.• When necessary, data in the S-VOL can be copied to the P-VOL.

During normal operations, the P-VOL remains available to the host for readand write I/O operations. The secondary system rejects write I/Os for the S-VOL. The S-VOL can only be written to when the pair is split and when thewrite-enable option is specified for the S-VOL. In this instance, S-VOL and P-VOL track maps keep track of differential data and are used to resynchronizethe pair.

Data pathTrueCopy for Mainframe operations are carried out between primary andsecondary storage systems connected by a Fibre Channel interface. The datapath, also referred to as the remote copy connection, connects ports on theprimary VSP G1000 storage system to the ports on the secondary storagesystem. The ports are assigned attributes that allow them to send andreceive data.

One data path connection is required, but two or more independentconnections are recommended for hardware redundancy. A maximum of eightpaths per control unit (CU) can be used.

Consistency groups A consistency group is a grouping of pairs upon which copy operations areperformed simultaneously, and in which the pairs' status remains consistent.


A consistency group can include pairs that reside in from one to four primaryand secondary systems.

You can issue a TrueCopy for Mainframe command to the consistency groupso that it is run on all pairs in the group. The pairs' statuses change at thesame time, though this depends on the group options you have set. Somepair operations take priority under certain circumstances. Full information iscovered in Consistency group planning on page 3-17.

Interfaces You can perform TrueCopy for Mainframe operations using one of thefollowing interfaces:

• Device Manager - Storage Navigator, which is a browser-based interfacefrom which TrueCopy for Mainframe is set up, operated, and monitored.The GUI provides the simplest method for performing operations,requiring no previous experience.

¢ The primary system must be LAN-attached to a Device Manager -Storage Navigator computer.

¢ The secondary system must also be LAN-attached to a separateDevice Manager - Storage Navigator at the secondary site. This allowsyou to perform operations more efficiently on the secondary system inthe event that the primary site is not available.

• Command Control Interface, which is a command line interface used todisplay pair information and perform all copying and pair-managingoperations from the UNIX or PC server to the storage system. CCIprovides a full scripting capability that can be used to automatereplication operations.

• Business Continuity Manager (BCM), which is a command line interfacefrom which pair operations are run and pair status is monitored. BCMcommands are issued from the host to the storage system.

• PPRC, with which most operations can be performed from the host. AllVSP G1000 storage systems support IBM PPRC host software functions.

Failover software Host failover software is used to transfer information between host servers atthe primary and secondary sites. It is a critical component of any disasterrecovery solution.

• When TrueCopy for Mainframe is used as a disaster recovery tool, hostfailover is required to ensure effective recovery operations.

• When TrueCopy for Mainframe is used as a data migration tool, hostfailover is recommended.

TrueCopy for Mainframe does not provide host failover functions. Use thefailover software most suitable for your platform and requirements (forexample, Microsoft Cluster Server).


Error reporting communicationsError reporting communications (ERC) transfers information between hostprocessors at the main and secondary sites. It is a critical component of adisaster recovery effort.

Overview of initial, update copy operations When you perform the initial copy operation, all the data in the P-VOL iscopied into the S-VOL. Thereafter, the primary storage system runs updatecopy when it receives write instruction from the host. The update operationcopies host updates to the S-VOL at the same time that they are copied tothe P-VOL.

The following figure illustrates the initial copy and update copy operations.

Initial copy When a new pair is created, the entire contents of the P-VOL are copied tothe S-VOL cylinder by track (this does not include diagnostic and unassignedalternate tracks). The initial copy synchronizes the P-VOL and S-VOLindependently of host I/O processes.

During the create pair operation, you can elect to have no data copied if datain the P-VOL and S-VOL are already identical. You can also specify optionsthat affect the speed of data transfer and storage system performance. Theseare:

• Copy Pace. You specify the number of tracks that can be copiedsimultaneously before the primary system accepts another host requestfor that P-VOL. If more tracks are copied, the operation completesquicker; if fewer tracks are copied, performance is maintained at a higherlevel.

• Maximum Initial Copy Activities. You specify the maximum number ofconcurrent initial copies that the system performs.

• Initial Copy Priority. You specify the order in which copying is performedon multiple pairs. This is used if more pairs are being created in theoperations than the maximum initial copy activity setting.

• Round Trip Time. You specify the time limit for data to travel from P-VOLto S-VOL. The value is used by the storage system to control initial copypace when update copying is in progress.


These options are available on Device Manager - Storage Navigator. Copypace is also available using CCI.

Update copy Update copy has a higher priority than initial copy. However, if an initial copyis in progress when updates are sent by the host, the update copy must waituntil the initial copy's copy pace completes. For example, if the copy pace is15 tracks, the update copy may wait up to 15 tracks (1 cylinder).

When the host issues an update after the initial copy is complete, the data iswritten to the P-VOL and copied to the S-VOL. Subsequent updates are helduntil the current update is completed in both volumes. This keeps the pairsynchronized.

Pair statusThe pair status is managed by the primary storage system which managesthe P-VOLs.

• The primary storage system is able to change the pair status of the P-VOLand the S-VOL.

• The secondary storage system can change the pair status of the S-VOLs,but cannot change the pair status of the P-VOLs. The primary storagesystem detects the change of the pair status of S-VOL, and then changethe status of P-VOL.

• The pair status changes as follows:

¢ If the volume is not assigned to the TrueCopy for Mainframe pair, thevolume status is Simplex.

¢ When the initial copy begins to create a pair, the primary storagesystem changes the status of both volumes to Pending (volumes to becopying). When the initial copy completes, the primary storagesystem changes the status of both volumes to Duplex (volumesbecome a pair).

¢ When user splits the pair from the primary storage system or thesecondary storage system, the status of the P-VOL and the S-VOL arechanged to Suspend.

¢ The primary storage system cannot keep the synchronisation of the P-VOL and the S-VOL by some reasons, for example errors, the primarystorage system changes the status of the P-VOL and the S-VOL toSuspend.

¢ When the user removes the pair from the primary storage system, theprimary storage system changes the status of the P-VOL and the S-VOL to Simplex.

¢ When the user removes the pair from the secondary storage system,the secondary storage system changes the status of the S-VOL toSimplex, and then the primary storage system detects the removal of


the pair at the secondary system (if the path is normal), the primarystorage system changes the status of the P-VOL to Suspend.


2Requirements and specifications

This chapter provides basic system requirements, along with specifications forBCM, PPRC, and other mainframe-related interfaces and functions. In additionto the information here, Chapter 3, Planning for TrueCopy for Mainframe onpage 3-1 provides many specifications, recommendations, and restrictionsfor the elements of a TrueCopy for Mainframe system that require attentionbefore setting up and using TrueCopy for Mainframe.

□ System requirements and specifications

□ Business Continuity Manager specifications

□ PPRC specifications, restrictions

□ SAID values for CESTPATH/YKBLDPTH

□ P/DAS support, restrictions

□ GDPS support

□ RMF PPRC link path statistical information support

□ Planning for Basic HyperSwap function—TPC-R support

□ Planning for Extended Address Volume

□ CCI support for TrueCopy for Mainframe operations

Requirements and specifications 2-1Hitachi TrueCopy® for Mainframe User Guide

System requirements and specificationsThe following table describes general system requirements.

Item Requirement

Virtual StoragePlatform G1000

• Number of CUs: 255• Range of CUs: 0x00 to 0xfe

Supportedemulation types

• 3390-A, 3390-1, 3390-2, 3390-3, 3390-9, 3390-L, 3390-M• Earlier model emulation types that can be used are: 3390-3R.

RAID levelssupported

RAID 1, RAID 5, and RAID6 configurations.

Supported storagesystems

VSP G1000 can be connected to:• VSP G1000 (80-01-01-xx/xx or later)• VSP (70-06-xx-xx/xx or later)• USP V/VM (60-08-4x-xx/xx or later)

When pairs in a consistency group belong to multiple VSPG1000s, USP V/VM cannot be used.See Requirements for VSP G1000 with earlier model storagesystems on page 3-3 for more information.

TrueCopy forMainframe

• Must be installed on primary and secondary system.• Separate license codes are required for each storage system.• Synchronous only. VSP G1000 does not support Asynchronous.• Can co-exist with TrueCopy.For information about exceeding licensed capacity and licenseexpiration, see the Hitachi Virtual Storage Platform G1000Mainframe System Administrator Guide.

Other requiredlicenses

None.However, when combining TrueCopy for Mainframe and DynamicProvisioning for Mainframe, the following licensed capacitylimitations apply:• If using a Dynamic Provisioning for Mainframe DP-VOL (virtual

volume) for the TrueCopy for Mainframe P-VOL or S-VOL, thecapacity of the allocated pages for the DP-VOL will be countedas the licensed capacity of TrueCopy for Mainframe.

• If the actual licensed capacity exceeds the available licensedcapacity, TrueCopy for Mainframe can be used as usual for 30days. After 30 days, only split or release operations will beallowed.

Additional sharedmemory

Required. Contact your Hitachi Data Systems Support Center.

Supportedmainframe hostplatforms

Refer to the Hitachi Data Systems interoperability matrix athttp://www.hds.com/products/interoperability.

Mainframe related • IBM PPRC is supported.• Optional error report communications (ERC) function requires

MVS/DFP 3.2.0 or later.

2-2 Requirements and specificationsHitachi TrueCopy® for Mainframe User Guide

http://www.hds.com/products/interoperability

Item Requirement

• If configuring S-VOL of TCz to P-VOL of URz, SYSPLEX timer isrequired to synchronize all the host's time if there are severalhosts at primary site and secondary site.

• ICKDSF R16 + PTF functions require VM/ESA 2.1.0 or later.Contact your Hitachi Data Systems Support Center for the latestinformation.

Data path A maximum of eight data paths are supported from primarysystem CU to secondary system CU.Fibre Channel (FICON), direct or with switch connections. See Datapath requirements and configurations on page 3-26.

Remote paths • A maximum of eight remote paths are supported from theprimary system CU to the secondary system CU.

• A primary system CU supports a maximum of 32 remote paths(8 paths per secondary system CU x 4 supported secondarysystem CUs per primary system CU).

• Remote paths are established separately for primary andsecondary system CUs.

Maximum numberof secondarysystems (CU)

• A primary system CU can be paired with up to four secondarysystem CUs.

• A primary system can have up to 1,020 paired secondarysystem CUs (255 primary system CUs x maximum of 4secondary system CUs).

• Each secondary system CU must be added (paired) individuallyto a primary system CU.

Pair volumes • The S-VOL must be equal-to or larger-than the P-VOL.However, when the S-VOL is larger than the P-VOL, the swapoperation cannot be performed.

• The maximum size of the P-VOL and S-VOL is 0.9TB each.• A P-VOL may be copied to only one S-VOL.• P-VOL and S-VOL can be shared with other Hitachi software

product volumes. See Volume types that can be shared withTrueCopy for Mainframe on page 4-2.

See Planning pairs and pair volumes on page 3-9 for moreinformation.

Number of pairs Limited per VSP G1000 storage system. See Maximum number ofpairs supported on page 3-14.

Number ofconsistency groups

Maximum: 256 (0x00 to 0xFF)

Disk track format Must be ensured by the user. The track format for the P-VOL andS-VOL must meet the following requirements:• The P-VOL and S-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 primary system aborts theinitial 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 andphysical head address of the track.


Item Requirement

• The CCHH of each user record in a track must be unique.

Error ReportingCommunications(ERC) software

• Required for disaster recovery.• Recommended for data migration.See Error reporting communications on page 3-25 for moreinformation.

Interfaces • Device Manager - Storage Navigator is required.¢ The following HDvM - SN roles are required to operate:

- Storage Administrator (Remote Copy)- Storage Administrator (System Resource Management)- Storage Administrator (Provisioning)

¢ The primary system must be LAN-attached to a DeviceManager - Storage Navigator computer.

¢ The secondary system must be attached using a separateLAN at the secondary site.

• BCM is optional.¢ A command device is required¢ See Business Continuity Manager specifications on page

2-4.• PPRC is optional. See PPRC specifications, restrictions on page

2-6.

Business Continuity Manager specificationsPair operations may be performed using Business Continuity Manager (BCM)commands from the host system to the storage system. With BCMcommands, you can add, split, resynchronize, and delete pairs, and monitorpair status. You can also create the TrueCopy for Mainframe associationbetween primary and secondary system (add RCU).

• For the correspondence between the LINK parameters (ports) and SAIDvalues, see SAID values for CESTPATH/YKBLDPTH on page 2-9.

• For corresponding PPRC functionality, see PPRC, BCM commandcomparison on page 2-8.

• Although the same TrueCopy for Mainframe pair operations may beperformed by using Business Continuity Manager or PPRC, BusinessContinuity Manager and PPRC are independent functions. Do not useBusiness Continuity Manager and PPRC for the same pair operation.

For complete information, see the Business Continuity Manager User's Guide.

Options not supported by Business Continuity ManagerNot all TrueCopy for Mainframe operation options are supported by BusinessContinuity Manager. The following table shows the default values used whenyou run the operation using Business Continuity Manager. Use DeviceManager - Storage Navigator to change these options.


Operation Option Default value used by BCM

Pair creation—YKMAKE

Initial Copy Priority Disabled2, 3

CFW Data Secondary Volume Copy1

DFW to Secondary Volume Not Require6

Pair split—YKSUSPND

SSB Transfer (F/M = FB) Disable7

Primary Volume Write Depend on Primary VolumeFence Level7

Pair resync—YKRESYNC

Copy Priority Disable3, 4

CFW Data Secondary Volume Copy1

Add RemoteConnection—YKBLDPTH5

AddRemoteConnection

Minimum Number ofPaths

1

RIO MIH Time 15 seconds

FREEZE Option Disable

Round Trip Time 1ms

ChangeCUOptions

PPRC support by host No

Services SIM of RemoteCopy

No Report

1. To change options, see Changing P-VOL Fence Level, CFW Data on page 7-10.2. The initial copy operation follows the YKMAKE execution order.3. See Priority for initial copy operations and scheduling order on page 3-15.4. The resync operation follows the YKRESYNC execution order. When YKRESYNC is

performed for a consistency group, the operation begins with the pair having thelowest number within the group.

5. To change these options, see Setting number of vols. copied, path blockade, otheroptions on page 5-6.

6. If you want to assign a different value to this option, use the Device Manager -Storage Navigator Add Pair operation. See Creating pairs on page 6-3.

7. If you want to assign a different value to this option, use the Device Manager -Storage Navigator Suspend Pair operation. See Splitting pairs on page 6-6.

Command deviceBusiness Continuity Manager requires a command device for TrueCopy forMainframe. It must be independent of any command device used forTrueCopy.

Please note the following:

• A command device must be configured from Business Continuity Manageronly. However, you can use Device Manager - Storage Navigator to checkwhether it already exists (click Logical Devices in the Storage Systemstree).


• Missing Interruption Handler (MIH) values are used as I/O monitor timefor volumes used as command devices. Make sure to set the MIH value to45 (seconds), minimum, from the host.

For more information, see the Business Continuity Manager User Guide forinstructions.

F/M = FB message output control optionIn Business Continuity Manager, when a pair in DUPLEX status is split orreleased to the S-VOL, the status of the P-VOL becomes Suspend and the F/M= FB message is output to the host connected to the primary system. You areable to stop output of the message by setting system option mode 776.

However, the F/M = FB message is output even with system option mode 776= ON when the pair status is Suspend due to failure. Also, the F/M = FBmessage is not output regardless of the of mode 776 setting if PPRC supportby host = No is selected on the Change CU Options window.

The following table shows the conditions when the F/M=FB message is output(Yes) or stopped (No).

Cause of P-VOL split

Settings

SOM 776 = ON SOM 776 = OFF

PPRC supportby host = Yes

PPRC supportby host = No

PPRC supportby host = Yes

PPRC supportby host = No

Suspended bysplit or releaseoperation fromBCM to S-VOLs

No No Yes No

Suspended byfailure

Yes No Yes No

PPRC specifications, restrictionsMost TrueCopy for Mainframe operations can be performed using PPRC TSOor ICKDSF PPRCOPY commands from the host system console. All VSPstorage systems support IBM PPRC host software functions.

TrueCopy for Mainframe operations performed with PPRCYou can perform the following operations using PPRC:

• Create, split, resynchronize, and delete TrueCopy for Mainframe pairs.• Split, resynchronize, and delete TrueCopy for Mainframe consistency

groups.• Establish and delete remote paths.• View path and pair status.


The following applies when using PPRC commands:

• The VSP is capable of automatically configuring a Fibre Channel port as aninitiator or RCU target port, if required, in response to the TSO CESTPATHand CDELPATH commands. Initiator and RCU target ports are required forsending and receiving data to and from the primary and secondarysystem. System option mode 114 must be enabled for automatic portconfiguration in response to PPRC commands.The VSP makes sure that the specified primary system port is offline tothe host, and automatically configures it as an initiator port if required.Similarly, the corresponding secondary system port is configured as anRCU target port when required.When the CDELPATH command is issued, TrueCopy for Mainframe remotepaths are removed. If there are no more TrueCopy for Mainframe remotepaths on the port, the port is automatically changed from initiator port toRCU target port.

• Concerning the Fibre Channel interface, do not use the CESTPATH andCDELPATH commands when using LUN Manager's SCSI path definitionfunction. Fibre Channel ports must be configured as initiator or RCUtarget ports before the CESTPATH and CDELPATH commands are issued.

Note: Ensure that the relevant paths are offline before issuing theCESTPATH command. The add path operation fails if active remote pathsexist, because the port attribute cannot be changed.

TrueCopy for Mainframe options not supported with PPRCThe TrueCopy for Mainframe options in the following table are not supportedwith PPRC. Use Device Manager - Storage Navigator to change these options:

OperationDevice Manager -Storage Navigator

screenOption Default value used

by PPRC

Add theremoteconnection(CESTPATH)

Add Remote Connection Minimum Number ofPaths

1

RIO MIH Time 15 sec.

Round Trip Time 1 ms

FREEZE Option CGROUP option inCESTPATH commandwill be applied.

Change CU Options PPRC support by host No


No Report

Pair creation(CESTPAIR)

Create TC Pairs Initial Copy Priority 0

CFW Data Secondary VolumeCopy1

DFW to SecondaryVolume

Not Require2


OperationDevice Manager -Storage Navigator

screenOption Default value used

by PPRC

Notes:1. If you select the Primary Volume Only value for CFW Data option, the data set that

is updated by CFW in the P-VOL cannot be used in the S-VOL. To use this data set inthe S-VOL, release the pair and format the data set. You can set the CFW data =Primary Volume Only using PPRC when the Remote Copy Function Switch is used.Contact your Hitachi Data Systems Support Center for more information.

2. This setting does not affect P-VOL I/O performance. If one side of cache is closeddue to a secondary system failure, the copy operation still uses DFW. The differencebetween Not Require and Require is that new pairs cannot be established with therequired option when one side of RCU cache is closed. In this case, the Add Pairoperation fails (This restriction applies only when the CU emulation type of RCU is3390).

PPRC, BCM command comparisonBCM and PPRC are independent functions. Do not use BCM and PPRC for thesame pair operation.

The following table lists the PPRC commands and corresponding BCMcommands.

PPRC command Parameter BCM command Support type

CESTPATH DEVN YKBLDPTH config

PRIM config

SEC config

LINK config

CGROUP Not supported

RESETHP Not supported

CESTPAIR DEVN YKMAKE or YKRESYNC config

PRIM config

SEC config

MODE Command (RESYNC)Parameter (NOCOPY)

PACE config (CopyPace)

CRIT config (ErrorLevel)

MSGREQ Not supported

ONLINSEC Not supported

CSUSPEND DEVN YKSUSPND*1 config

PRIM config


PPRC command Parameter BCM command Support type

SEC config

PRIMARY Not supported

QUIESCE Not supported

CDELPAIR DEVN YKDELETE config

PRIM

SEC

CRECOVER DEVN YKRECOVER config

PRIM

SEC

ID

CQUERY DEVN YKQUERY config

FORMAT or UNFORMAT Not supported

VOLUME/PATHS Not supported

CGROUP DEVN YKFREEZE or 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 split command for the P-VOL.

SAID values for CESTPATH/YKBLDPTHThe following tables show the correspondence between the LINK parameters(ports) and SAID values (system adapter ID) in :

• SAID values for PATH LINK (CL1) on page 2-10• SAID Values for PATH LINK (CL2) on page 2-11

Note: SAID values for the LINK parameter used in CESTPATH/YKBLDPTHdiffer from those for RMF PPRC link path statistical information. For the latterinformation, see the tables in RMF PPRC link path statistical informationsupport on page 2-13.


SAID values for PATH LINK (CL1)

Packglocal Port SAID Packg

local Port SAID Packglocal Port SAID Packg

local Port SAID

1PC(Basic)

CL1-A X'0000' 1PJ(Basic)

CL1-J X'0008' 1PA(Option)(DKA00Basic)

CL9-A X'0080' 1PG(Option)(DKA10Basic)

CL9-J X'0088'

CL3-A X'0020' CL3-J X'0028' CLB-A X'00A0' CLB-J X'00A8'

CL5-A X'0040' CL5-J X'0048' CLD-A X'00C0' CLD-J X'00C8'

CL7-A X'0060' CL7-J X'0068' CLF-A X'00E0' CLF-J X'00E8'

CL1-B X'0001' CL1-K X'0009' CL9-B X'0081' CL9-K X'0089'

CL3-B X'0021' CL3-K X'0029' CLB-B X'00A1' CLB-K X'00A9'

CL5-B X'0041' CL5-K X'0049' CLD-B X'00C1' CLD-K X'00C9'

CL7-B X'0061' CL7-K X'0069' CLF-B X'00E1' CLF-K X'00E9'

1PD(Option)

CL1-C X'0002' 1PK(Option)

CL1-L X'000A' 1PB(Option)(DKA01Basic)

CL9-C X'0082' 1PH(Option)(DKA11Basic)

CL9-L X'008A'

CL3-C X'0022' CL3-L X'002A' CLB-C X'00A2' CLB-L X'00AA'

CL5-C X'0042' CL5-L X'004A' CLD-C X'00C2' CLD-L X'00CA'

CL7-C X'0062' CL7-L X'006A' CLF-C X'00E2' CLF-L X'00EA'

CL1-D X'0003' CL1-M X'000B' CL9-D X'0083' CL9-M X'008B'

CL3-D X'0023' CL3-M X'002B' CLB-D X'00A3' CLB-M X'00AB'

CL5-D X'0043' CL5-M X'004B' CLD-D X'00C3' CLD-M X'00CB'

CL7-D X'0063' CL7-M X'006B' CLF-D X'00E3' CLF-M X'00EB'

1PE(Option)

CL1-E X'0004' 1PL(Option)

CL1-N X'000C' - - - - - -

CL3-E X'0024' CL3-N X'002C' - - - -

CL5-E X'0044' CL5-N X'004C' - - - -

CL7-E X'0064' CL7-N X'006C' - - - -

CL1-F X'0005' CL1-P X'000D' - - - -

CL3-F X'0025' CL3-P X'002D' - - - -

CL5-F X'0045' CL5-P X'004D' - - - -

CL7-F X'0065' CL7-P X'006D' - - - -

1PF(Add3)

CL1-G X'0006' 1PM(Option)

CL1-Q X'000E' - - - - - -

CL3-G X'0026' CL3-Q X'002E' - - - -

CL5-G X'0046' CL5-Q X'004E' - - - -

CL7-G X'0066' CL7-Q X'006E' - - - -

CL1-H X'0007' CL1-R X'000F' - - - -

CL3-H X'0027' CL3-R X'002F' - - - -

CL5-H X'0047' CL5-R X'004F' - - - -

CL7-H X'0067' CL7-R X'006F' - - - -


SAID Values for PATH LINK (CL2)



local Port SAID

2PC(Basic)



CLA-A X'0090' 2PG(Option)(DKA12Basic)

CLA-J X'0098'

CL4-A X'0030' CL4-J X'0038' CLC-A X'00B0' CLC-J X'00B8'

CL6-A X'0050' CL6-J X'0058' CLE-A X'00D0' CLE-J X'00D8'

CL8-A X'0070' CL8-J X'0078' CLG-A X'00F0' CLG-J X'00F8'

CL2-B X'0011' CL2-K X'0019' CLA-B X'0091' CLA-K X'0099'

CL4-B X'0031' CL4-K X'0039' CLC-B X'00B1' CLC-K X'00B9'

CL6-B X'0051' CL6-K X'0059' CLE-B X'00D1' CLE-K X'00D9'

CL8-B X'0071' CL8-K X'0079' CLG-B X'00F1' CLG-K X'00F9'

2PD(Option)


CL2-L X'001A' 2PB(Option)(DKA03Basic)

CLA-C X'0092' 2PH(Option)(DKA13Basic)

CLA-L X'009A'

CL4-C X'0032' CL4-L X'003A' CLC-C X'00B2' CLC-L X'00BA'

CL6-C X'0052' CL6-L X'005A' CLE-C X'00D2' CLE-L X'00DA'

CL8-C X'0072' CL8-L X'007A' CLG-C X'00F2' CLG-L X'00FA'

CL2-D X'0013' CL2-M X'001B' CLA-D X'0093' CLA-M X'009B'

CL4-D X'0033' CL4-M X'003B' CLC-D X'00B3' CLC-M X'00BB'

CL6-D X'0053' CL6-M X'005B' CLE-D X'00D3' CLE-M X'00DB'

CL8-D X'0073' CL8-M X'007B' CLG-D X'00F3' CLG-M X'00FB'

2PE(Option)


CL2-N X'001C' - - - - - -

CL4-E X'0034' CL4-N X'003C' - - - -

CL6-E X'0054' CL6-N X'005C' - - - -

CL8-E X'0074' CL8-N X'007C' - - - -

CL2-F X'0015' CL2-P X'001D' - - - -

CL4-F X'0035' CL4-P X'003D' - - - -

CL6-F X'0055' CL6-P X'005D' - - - -

CL8-F X'0075' CL8-P X'007D' - - - -

2PF(Option)

CL2-G X'0016' 2PM(Option)

CL2-Q X'001E' - - - - - -

CL4-G X'0036' CL4-Q X'003E' - - - -

CL6-G X'0056' CL6-Q X'005E' - - - -

CL8-G X'0076' CL8-Q X'007E' - - - -

CL2-H X'0017' CL2-R X'001F' - - - -

CL4-H X'0037' CL4-R X'003F' - - - -

CL6-H X'0057' CL6-R X'005F' - - - -

CL8-H X'0077' CL8-R X'007F' - - - -


P/DAS support, restrictionsTrueCopy for Mainframe supports the IBM P/DAS host software function.P/DAS allows you to relocate or migrate data by redirecting all applicationI/Os from the P-VOL to the S-VOL without interrupting access to the data.See the following IBM publications for important information about therequirements and procedures for P/DAS operations: Planning for IBM RemoteCopy (SG24-2595), Advanced Copy Services (SC35-0355), DFSMS MVS V1Remote Copy Guide and Reference (SC35-0169).

RestrictionsThe following restrictions apply to P/DAS use with TrueCopy for Mainframe:

• P/DAS through channel extenders is not supported.• P/DAS does not support CFW operations. You must stop CFW applications

before performing P/DAS operations on TrueCopy for Mainframe volumes.• P/DAS swap option #2 (switch pair & swap) is supported for P/DAS

between the VSP and TagmaStore USP/TagmaStore NSC.

Contact your Hitachi Data Systems Support Center for the latest informationabout P/DAS support.

GDPS supportTrueCopy for Mainframe provides remote copy support for IBM'sGeographically Dispersed Parallel Sysplex® (GDPS) facility. GDPS is an IBMservice for mirroring data and balancing workload on storage systems spreadacross 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 ofthe VSP's suite of remote copy options for data availability.

GDPS operations feature automatic control of groups of PPRC-managedvolumes using host-based scripts and PPRC commands; for example,CGROUP (FREEZE/RUN). GDPS support may have additional installationrequirements for TrueCopy for Mainframe primary and secondary systems,depending on the VSP firmware and TrueCopy for Mainframe versions. Checkwith the Hitachi Data Systems Support Center.

The VSP does not support controlling the FREEZE Option through theCESTPATH LINK parameter. The FREEZE Option must be controlled using theCGROUP option of CESTPATH. Please make changes as needed to theCESTPATH LINK definitions in your GDPS configuration files or configurationdatabase.

For more information about GDPS, see the following IBM publications:Geographically Dispersed Parallel Sysplex: the S/390 Multi-site ApplicationAvailability Solution, Executive Summary (GF22-5114); and GeographicallyDispersed Parallel Sysplex: the S/390 Multi-site Application AvailabilitySolution (GF22-5063).


RMF PPRC link path statistical information supportWhen you use the Resource Measurement Facility (RMF) and specify the IBMTotalStorage Enterprise Storage Server® (ESS), you can acquire PPRC fibrelink path statistical information.

If the total size of the data for the data-acquisition interval is 100 kB or less,zero may be reported for the data size.

The VSP storage system adaptor IDs (SAID) for the LINK parameters (ports)that display when PPRC link path statistical information is acquired with RMFare shown in:

• SAID values for link path statistical information (CL1) on page 2-13• SAID values for link path statistical information (REAR CL2) on page

2-15

SAID values for link path statistical information (CL1)



local Port SAID

1PC(Basic)

CL1-A X'0000'

1PJ(Basic)


CL9-A X'0040' 1PG(Option)(DKA10Basic)

CL9-J X'0060'

CL3-A X'0001'

CL3-J X'0021' CLB-A X'0041' CLB-J X'0061'

CL5-A X'0002'

CL5-J X'0022' CLD-A X'0042' CLD-J X'0062'

CL7-A X'0003'

CL7-J X'0023' CLF-A X'0043' CLF-J X'0063'

CL1-B X'0004'

CL1-K X'0024' CL9-B X'0044' CL9-K X'0064'

CL3-B X'0005'

CL3-K X'0025' CLB-B X'0045' CLB-K X'0065'

CL5-B X'0006'

CL5-K X'0026' CLD-B X'0046' CLD-K X'0066'

CL7-B X'0007'

CL7-K X'0027' CLF-B X'0047' CLF-K X'0067'

1PD(Option)

CL1-C X'0010'

1PK(Option)

CL1-L X'0030' 1PB(Option)(DKA01Basic)

CL9-C X'0050' 1PH(Option)(DKA11Basic)

CL9-L X'0070'

CL3-C X'0011'

CL3-L X'0031' CLB-C X'0051' CLB-L X'0071'

CL5-C X'0012'

CL5-L X'0032' CLD-C X'0052' CLD-L X'0072'

CL7-C X'0013'

CL7-L X'0033' CLF-C X'0053' CLF-L X'0073'

CL1-D X'0014'

CL1-M X'0034' CL9-D X'0054' CL9-M X'0074'




local Port SAID

CL3-D X'0015'

CL3-M X'0035' CLB-D X'0055' CLB-M X'0075'

CL5-D X'0016'

CL5-M X'0036' CLD-D X'0056' CLD-M X'0076'

CL7-D X'0017'

CL7-M X'0037' CLF-D X'0057' CLF-M X'0077'

1PE(Option)

CL1-E X'0008'

1PL(Option)

CL1-N X'0028' - - - - - -

CL3-E X'0009'

CL3-N X'0029' - - - -

CL5-E X'000a'

CL5-N X'002a' - - - -

CL7-E X'000b'

CL7-N X'002b' - - - -

CL1-F X'000c' CL1-P X'002c' - - - -

CL3-F X'000d'

CL3-P X'002d' - - - -

CL5-F X'000e'

CL5-P X'002e' - - - -

CL7-F X'000f' CL7-P X'002f' - - - -

1PF(Add3)

CL1-G X'0018'

1PM(Option)

CL1-Q X'0038' - - - - - -

CL3-G X'0019'

CL3-Q X'0039' - - - -

CL5-G X'001a'

CL5-Q X'003a' - - - -

CL7-G X'001b'

CL7-Q X'003b' - - - -

CL1-H X'001c' CL1-R X'003c' - - - -

CL3-H X'001d'

CL3-R X'003d' - - - -

CL5-H X'001e'

CL5-R X'003e' - - - -

CL7-H X'001f' CL7-R X'003f' - - - -


SAID values for link path statistical information (REAR CL2)



local Port SAID

2PC(Basic)


CL2-J X'00a0' 2PA(Option)(DKA02Basic)

CLA-A X'00c0' 2PG(Option)(DKA12Basic)

CLA-J X'00e0'

CL4-A X'0081' CL4-J X'00a1' CLC-A X'00c1' CLC-J X'00e1'

CL6-A X'0082' CL6-J X'00a2' CLE-A X'00c2' CLE-J X'00e2'

CL8-A X'0083' CL8-J X'00a3' CLG-A X'00c3' CLG-J X'00e3'

CL2-B X'0084' CL2-K X'00a4' CLA-B X'00c4' CLA-K

X'00e4'

CL4-B X'0085' CL4-K X'00a5' CLC-B X'00c5' CLC-K

X'00e5'

CL6-B X'0086' CL6-K X'00a6' CLE-B X'00c6' CLE-K X'00e6'

CL8-B X'0087' CL8-K X'00a7' CLG-B X'00c7' CLG-K

X'00e7'

2PD(Option)


CL2-L X'00b0' 2PB(Option)(DKA03Basic)

CLA-C X'00d0' 2PH(Option)(DKA13Basic)

CLA-L X'00f0'

CL4-C X'0091' CL4-L X'00b1' CLC-C X'00d1' CLC-L X'00f1'

CL6-C X'0092' CL6-L X'00b2' CLE-C X'00d2' CLE-L X'00f2'

CL8-C X'0093' CL8-L X'00b3' CLG-C X'00d3' CLG-L X'00f3'

CL2-D

X'0094' CL2-M X'00b4' CLA-D X'00d4' CLA-M

X'00f4'

CL4-D

X'0095' CL4-M X'00b5' CLC-D X'00d5' CLC-M

X'00f5'

CL6-D

X'0096' CL6-M X'00b6' CLE-D X'00d6' CLE-M

X'00f6'

CL8-D

X'0097' CL8-M X'00b7' CLG-D X'00d7' CLG-M

X'00f7'

2PE(Option)


CL2-N X'00a8' - - - - - -

CL4-E X'0089' CL4-N X'00a9' - - - -

CL6-E X'008a' CL6-N X'00aa' - - - -

CL8-E X'008b' CL8-N X'00ab' - - - -

CL2-F X'008c' CL2-P X'00ac' - - - -

CL4-F X'008d' CL4-P X'00ad' - - - -

CL6-F X'008e' CL6-P X'00ae' - - - -

CL8-F X'008f' CL8-P X'00af' - - - -

2PF(Add3)

CL2-G

X'0098' 2PM(Option)

CL2-Q X'00b8' - - - - - -

CL4-G

X'0099' CL4-Q X'00b9' - - - -




local Port SAID

CL6-G

X'009a' CL6-Q X'00ba' - - - -

CL8-G

X'009b' CL8-Q X'00bb' - - - -

CL2-H

X'009c' CL2-R X'00bc' - - - -

CL4-H

X'009d' CL4-R X'00bd' - - - -

CL6-H

X'009e' CL6-R X'00be' - - - -

CL8-H

X'009f' CL8-R X'00bf' - - - -

Planning for Basic HyperSwap function—TPC-R supportThe Basic HyperSwap function, performed from TPC-R, is an IBM product fordisaster recovery. The following figure illustrates TrueCopy for Mainframeoperations with TPC-R.

Requirements• System option mode 114 set to OFF.• System option mode 484 and 769 set to ON.• A bi-directional path between primary system and secondary system must

be in place.


Recommendations• For best performance, the maximum number of pairs for the Basic

HyperSwap function is 1,000 per CHA.• The MIH value of host I/O and the host operation is about one second.

This allows MIH to be reported for host I/O or for the host operation.• Resources in the host system must be adequate. If a shortage occurs,

resynchronization of TrueCopy for Mainframe pairs may fail.• When running the FREEZE command, make sure that it can complete

within 20 seconds to avoid failure. Hitachi recommends configuring yoursystem as follows:

¢ (Number of Host paths) x (Number of LPARs) x (Number of CGROUPs(Number of CUs)) ≤ 160

¢ Number of pairs ≤ 4,096

Planning for Extended Address VolumeExtended Address Volume (EAV) can be assigned to a TrueCopy forMainframe pair. EAV is a Hitachi function to define a large capacity VOL thatis not supported by existing 3390 type volumes. You can create a pair withand/or without EAV. The following table shows EAV availability for P-VOLs andS-VOLs.

P-VOL(Device emulation type)

S-VOL (Device emulation type)

EAV (3390-A) No EAV (3390-X *1)

EAV (3390-A) Available Not available

non-EAV (3390-X *1) Available Available

1. 3390-X indicates the 3390 series other than 3390-A. For these other supported 3390emulation types, see the table in System requirements and specifications on page 2-2.

Emulation type 3390 combined with non-3390 device types is not available.

To enable data migration from existing storage to the EAV (3390-A), you cancombine a non-EAV (3390-X) as the P-VOL and an EAV (3390-A) as the S-VOL. However, a reversed combination in which EAV (3390-A) is the P-VOLand non-EAV (3390-X) is the S-VOL is not supported.

Note: You can use data migration from an earlier storage model P-VOL to anEAV S-VOL. When you do this, note that the following two field values for theS-VOL in the Device Manager - Storage Navigator Detailed Informationdialog box:

• The emulation type is shown as ......• If the S-VOL's number of cylinders is greater than 65,535, it is still

indicated as 65,535


CCI support for TrueCopy for Mainframe operationsYou can run pair operations and path operations using CCI for TrueCopy forMainframe pairs and TrueCopy pairs on a UNIX or PC server connected to theVSPs.

A LUN on the VSP target port must be defined and a command device createdfor CCI prior to using the interface. You can define the LUN to a logicalvolume for an open server that is connected to a UNIX or PC server. For moreinformation about command device settings, see the Hitachi CommandControl Interface User and Reference Guide.

Supported operations and optionsThe following table shows the Device Manager - Storage Navigator operationsand options that are supported, and not supported, by CCI.

Category HDvM - SNoperation type Option CCI support

PairOperation

Create TC Pairs (no option) Yes

Initial Copy Type Yes

Copy Pace1 Yes

Initial Copy Priority No (fixed to 32)

Difference Management No (fixed to Auto)

CFW Data No (fixed to S-VOL)2

DFW to Secondary Volume No (fixed to DFW not required)

Host I/O Time Stamp Transfer No (fixed to Disable)3

Split Pairs (no option) Yes

SSB Transfer (F/M = FB) No (fixed to Disable)

Primary Volume Write No (fixed to S-VOL)

Resync Pairs (no option) Yes

Primary Volume Fence Level Yes

Copy Pace1 Yes

Copy Priority No (fixed to 32)

CFW Data (not in HDvM - SNfor this operation)

No fixed to S-VOL2

Host I/O Time Stamp Transfer No (fixed to Disable) 3, 4

Delete Pairs (no option) Yes

Delete Mode No (fixed to Normal)3, 4

Edit Pair Options (no option) No

Path Add RemoteConnection

(no option) Yes


Category HDvM - SNoperation type Option CCI support

Operation Minimum Paths No (fixed to 1)

RIO MIH Time (sec) No (fixed to 15 (sec.))

FREEZE Option No (fixed to Disable)

Round Trip Time (msec) No (fixed to 1 (ms))

Remove RemoteConnection

(no option) Yes

Add/Remove RemotePaths

(no option) Yes

Add/Remove SSID (no option) Yes

Change RCU Options (no option) Yes

Minimum Paths Yes

RIO MIH Time (sec) Yes

FREEZE Option Yes

Round Trip Time (msec) Yes

Others Edit Remote ReplicaOptions

(no option) No

Change CU Options (no option) No

Performance Monitor (no option) No

View Histories (no option) No

1. With Device Manager - Storage Navigator you select 3 or 15 tracks for Copy Pace. For CCI, you usethe track size parameter with basically the same track settings: if you specify 1-3, 3 tracks are used;if you specify 4-15, 15 tracks are used.

2. For the CFW Data option, you can specify Primary Volume Only only if Remote Copy Function Switch#12 is also enabled. If you select CFW Data = Primary Volume Only, the data set that is updated byCFW in the P-VOL cannot be used in the S-VOL. To use this data set in the S-VOL, delete the pairand format the data set.

3. You can only enable the Host I/O Time Stamp Transfer option if Remote Copy Function Switch #36 isalso enabled.Enable the Host I/O Time Stamp Transfer option for the following functions:¢ ATTIME Suspend when used in a 3DC cascade configuration. The Host I/O Time Stamp Transfer

option is necessary to support the ATTIME Suspend of an SIz pair that is cascaded with the TCzS-VOL/URz P-VOL in the intermediate site.

¢ In a 3DC cascade configuration when the related URz remote journal is in an extendedconsistency group.

4. You cannot enable or disable the Host I/O Time Stamp Transfer option when the pair isresynchronized in CCI. Unless you delete the pair, you can only disable the Host I/O Time StampTransfer option by resynchronizing using Host I/O Time Stamp Transfer = Disable in Device Manager- Storage Navigator.


3Planning for TrueCopy for Mainframe

This chapter provides information and instructions for planning primary andsecondary system, pair volumes, data paths, and other elements.

□ Storage system preparation

□ System performance considerations

□ Planning pairs and pair volumes

□ Consistency group planning

□ Error reporting communications

□ Data path requirements and configurations

Planning for TrueCopy for Mainframe 3-1Hitachi TrueCopy® for Mainframe User Guide

Storage system preparationThe following preparations are required for the storage systems in aTrueCopy for Mainframe pair relationship.

• Device Manager - Storage Navigator must be LAN-attached to the primaryand secondary system. See the Hitachi Virtual Storage Platform G1000Mainframe System Administrator Guide for information.

• The primary and secondary system must be set up for TrueCopy forMainframe operations. See Cache, additional shared memoryrequirements on page 3-2 and DASD fast write requirements on page3-3. Make sure to consider the amount of Cache Residency Manager datathat will be stored in cache when determining the amount of cache forTrueCopy for Mainframe operations.

• Set the system option modes, if needed, for your TrueCopy for Mainframeconfiguration on the primary and secondary system. See S-VOL Read andother system options on page 3-3 for more information.

• Make sure that the storage system is configured to report senseinformation by connecting storage system and host. It is required toconnect host to both primary and secondary system. If dedicated hostcannot be connected to secondary system, connect secondary system andhost at primary site.

• On the host operating system, make sure that the missing interrupthandler (MIH) value (also called host I/O patrol time) is set high enoughto accommodate the number of pairs, the cable length between theprimary and secondary system, and the initial copy pace. Therecommended MIH value for TrueCopy for Mainframe operations is 60seconds. For MVS, the MIH value is specified in the SYS1.PARMLIB file.The recommended MIH value for Compatible XRC is different than forTrueCopy for Mainframe. If you are performing TrueCopy for Mainframeand Compatible XRC operations on the same storage system at the sametime, contact Hitachi Data Systems Support Center.

• If power sequence control cables are used, set the power select switch forthe cluster to LOCAL to prevent the primary system from being poweredoff by the host. Make sure the S-VOL is not powered off during TrueCopyfor Mainframe operations.

• Install the data path between the primary and secondary system.Distribute data paths between different storage clusters and extenders orswitches to provide maximum flexibility and availability. The remote pathsbetween the primary and secondary system must be different than theremote paths between the host and secondary system. See Data pathrequirements and configurations on page 3-26 for more information.

Cache, additional shared memory requirementsCache must be operable for the pair's primary and secondary system,otherwise pairs cannot be created. The secondary system cache must beconfigured to adequately support TrueCopy for Mainframe remote copyworkloads and any local workload activity.

3-2 Planning for TrueCopy for MainframeHitachi TrueCopy® for Mainframe User Guide

Additional shared memory is prerequisite in both of the primary andsecondary system.

Note: Neither cache nor shared memory can be added to or removed fromthe storage system when pair status is Pending Duplex. When either of thesetasks is to be performed, first split any pairs in Pending Duplex status; thenresynchronize the pairs when the cache or shared memory operation iscompleted.

DASD fast write requirementsDASD fast write (DFW) is required at the primary and secondary system onlywhen Required is specified for the PPRC DFW to Secondary Volume option. IfDFW to an S-VOL is blocked, but the pair was established with the Requiredoption specified, the primary system detects DFW OFF at the S-VOL and splitsthe pair. The default for TrueCopy for Mainframe pairs created using PPRCcommands is Not Required, therefore they are not split when DFW toSecondary Volume is blocked.

The DFW to Secondary Volume setting does not affect P-VOL I/Operformance. If one side of cache is closed due to a secondary system failure,the copy operation still uses DFW. The difference between not required andrequired is that new pairs cannot be established with the required optionwhen one side of secondary system cache is closed. In this case, the Add Pairoperation fails (This restriction applies only when the CU emulation type ofsecondary system is 3390).

Requirements for VSP G1000 with earlier model storage systemsYou can pair VSP G1000 volumes with VSP and USP V/VM volumes. However,if the VSP G1000 volumes are in a consistency group consisting of multipleVSP G1000 systems, USP V/VM cannot be used. In this case, all pairedvolumes must belong to VSP G1000 or VSP.

• When connecting VSP G1000 with VSP or USP V/VM, contact Hitachi DataSystems Support Center for information regarding the supportedmicrocode versions.

• When creating TCz pair using storage machine prior to VSP G1000, makesure the primary and secondary system have unique serial numbers.

Note: When using CCI (or Raidcom), the VSP G1000 serial numberrequires a prefix of "3".

S-VOL Read and other system optionsYou can tailor VSP G1000 storage systems to enable the S-VOL Read optionand other functions. System option modes related to TrueCopy for Mainframeand PPRC operations are shown in the following table.

(For more information about I/O to the S-VOL, see Allowing I/O to the S-VOLon page 3-12.)


VSP G1000 option modes are set to their default values at installation, andcan be changed only by your Hitachi Data Systems Support Center.

Optionmode Description

20 S-VOL read-only function (secondary system only).

36 Selects function of CRIT=Y(ALL) or CRIT=Y(PATHS):• ON: CRIT=Y(ALL) => equivalent to Primary Volume Fence Level =

Data.• OFF: CRIT=Y(PATHS) => equivalent to Primary Volume Fence Level =

Status.

64 Allows you to change the volume that is split when the FREEZE command isissued from the host. The target will change from the volume in the CU forwhich the FREEZE command is issued to the volume in the entire DKC ifthis mode is ON:• ON: The volume in the entire DKC is split.• OFF: The volume in the CU for which the FREEZE command is issued is

split.

114 Allows dynamic port mode setting (Initiator/RCU target for Fibre Channel)through PPRC CESTPATH and CDELPATH commands:• ON: Initiator ports automatically change to RCU target ports, or vice

versa.• OFF (default): Initiator ports do not change to RCU target ports, or

vice versa.For Fibre Channel interface, do not use the CESTPATH and CDELPATHcommands at the same time as the SCSI path definition function of LUNManager. Fibre Channel interface ports need to be configured as initiatorports or RCU target ports before the CESTPATH and CDELPATH commandsare issued.

308 Allows you to specify whether the Remote Copy Path status, SIM218x, isreported to the host or not.• ON: SIM218x will be reported to the host.• OFF: SIM218x will not be reported to the host.

484 Allows you to select the indication type if you use the PPRC CQUERYcommand to display the remote copy path status:• ON: The status of path using the Fibre Channel interface displays.

WWNN is indicated.• OFF: The status of path using an ESCON® interface displays. WWNN is

invalid.If a previous model storage system is connected, mode 484 must be OFF.

689 Allows you to slow the initial copy operation when the write-pending levelto the S-VOL is 60% or higher.• ON: When the S-VOL MP blade WritePending is 60% or higher, the

initial copy operation is inhibited.• OFF: Though the S-VOL MP blade WritePending is 60% or higher, the

initial copy operation is not inhibited.Do not set this mode if the primary or secondary system is connected toUSP V/VM with microcode earlier than 60-02-xx-xx/xx; otherwise TrueCopyfor Mainframe pairs may split.


Optionmode Description

769 Used when the basic HyperSwap function of TPC-R is used. The TPC-RBasic HyperSwap function may allow the CESTPATH operation to establish apath to several secondary systems at the same time. Because attributes ofa port are switched if the CESTPATH operation is performed with systemoption mode 144 ON, the path status between the primary and secondarysystem is changed to linkdown. If the CESTPATH operation is performed totwo or more secondary systems at the same time, MIH may be reported toa host as the other CESTPATH operation, which has detected the linkdownpath, retries the CESTPATH operation. To disable an MIH report to a host,set this system option mode to ON to disable the CESTPATH to retry theoperation when a linkdown is detected.• ON: Does not retry when linkdown is detected during CESTPATH

operation.• OFF: Retries when linkdown is detected during CESTPATH operation.

776 Allows you to select whether to output the F/M = FB message to the host ofprimary system when the split or the release operation is performed fromBusiness Continuity Manager to the S-VOL of a TrueCopy for Mainframepair in Duplex status:• ON: The F/M = FB message is not output.• OFF: The F/M = FB message is output.This mode must be set to both primary and secondary system.

784 Allows you to reduce RIO MIH time to 5-seconds. As a result, after aremote path error, less time elapses until the operation is retried on analternate path. (Both RIO MIH time and the Abort Sequence timeout valueare combined for this retry time.)• ON: Reduces the RIO MIH time to 5-seconds.

Combined with the Abort Sequence timeout value, the total amount oftime that elapses before the operation is retried on another path is amaximum of 10-seconds.

• OFF: The RIO MIH time that you specified at secondary systemregistration (default=15 seconds) is used with the specified AbortSequence timeout value.

System performance considerationsSynchronous copy operations affect I/O performance on the host and on theprimary and secondary systems. TrueCopy for Mainframe provides options forminimizing the impact and for maximizing the efficiency and speed of copyoperations for the best level of backup data integrity. These options arediscussed in:

• Determining Round Trip Time on page 3-6• Determining Minimum Number of Remote Paths on page 3-8• Allowing I/O to the P-VOL after a split—Fence Level options on page

3-13

Performance is also optimized with the proper bandwidth. This is discussed inAnalyzing workload, planning data paths on page 3-8.


Determining Round Trip TimeYou specify a time limit in milliseconds for data to travel from the P-VOL tothe S-VOL when you set up the TrueCopy for Mainframe association betweenprimary and secondary system. Round Trip Time is used by the systems tocontrol the initial copy pace when update copying is in progress.

This section provides instructions for determining your system's Round TripTime.

Note the following Round Trip Time considerations:

• If the difference between Round Trip Time and remote IO response timeis significant, the system slows or even interrupts the initial copyoperation so that the update copy can continue.Example of significant difference between the two: 1ms RT Time : 500msremote IO response time.

• If the difference between the two is insignificant, initial copying is allowedto run at the specified pace.Example of insignificant difference between the two: 1ms : 5 ms

To determine Round Trip Time value

The value of Round Trip time= round trip time between primary system and secondarysystem x 2(*) + initial copy response time (ms)

(*) A data transfer between primary and secondary system involves two responsesequences in one command issuance. Therefore, you need to double the round trip time.But if the host mode option 51 (Round Trip Set Up Option) is enabled, responsesequence will be once for each command so you do not need to double the round triptime.

• For the "round trip time" in the formula, please ask your Hitachi DataSystems Support Center, or use a ping command. If you do not usechannel extenders between the primary and secondary system, specify"1".)

• The "initial copy response time" in the formula is the response timerequired for multiple initial copy operations. With the following formula,determine the initial copy response time using the initial copy pace, thenumber of maximum initial copy, and the bandwidth of the channelextender communication lines between primary and secondary system.

Initial copy response time (ms) = (1[MB] / "Data path speed between primarysystem and secondary system [MB/ms]1") x ("initial copy pace(2 / 15) x (number ofmaximum initial copy3 " / "Number of data paths between primary system andsecondary system"4)

1. When you connect primary system with secondary system without extenders,set "Data path speed between primary system and secondary system" to eitherof below depending on the fiber cable link speed.2 Gbps : 0.17 MB/ms4 Gbps : 0.34 MB/ms8 Gbps : 0.68 MB/ms10 Gbps : 0.85 MB/ms


16 Gbps : 1.36 MB/ms2. For "initial copy pace" in the preceding formula, see the following table.3. For "number of maximum initial copy", use the value set up per storage system.

The default is 64.4. Even if the "number of maximum initial copy" / "Number of data paths between

primary system and secondary system" is larger than 16, specify "number ofmaximum initial copy VOLs" / "Number of data paths between primary systemand secondary system" as 16.

The following table shows the initial copy pace used for the response timecalculation.

Interface Initial copy onlyin progress

Initial, update copy in progress

When initial copy pacespecified at the time ofpair creation is 1 to 8

When initial copy pacespecified at the time ofpair creation is 9 to 15

BusinessContinuityManager

User-specified value User-specified valuebetween 1 and 8

8

DeviceManager -StorageNavigator

User-specified value User-specified valuebetween 1 and 8

8

PPRCcommand(TSO/ICKDSF) andCUemulation isI-2107

15(*) 8(*)

(*) When a PPRC command (TSO/ICKDSF) is used and the CU emulation type is I-2107,the initial copy pace specified is invalid. Therefore, the fixed value will be set.

The following table shows example settings.

Round triptime

betweenprimary

system andsecondary

system [ms]

Data pathspeed

betweenprimarysystem

andsecondary

system(MB/ms)

Number ofdata pathsbetweenprimary

system andsecondary

system

Initial copypace

Number ofmaximuminitial copy

VOLs

Roundtriptime

specified [ms]

0 0.1 4 15 64 160

30 0.1 4 15 64 220

100 0.1 4 15 64 360


Determining Minimum Number of Remote PathsYou specify the minimum number of remote paths to the secondary systemwhen you set up the TCz association between primary and secondarysystems. Using the Minimum Number of Paths option, you set a minimumvalue from one to eight paths, with one being the default.

If the number of paths in Normal status drops below the specified minimum,the primary storage system splits the pair to avoid impact to hostperformance.

• To maintain high performance in the primary storage system, Hitachirecommends setting the minimum number at two.

• For a pair with important data, set the minimum at one. This allows thesystem to continue update operations to the secondary system.

• You can protect data integrity between P-VOL and S-VOL in the event thatthe system splits the pair because the number of paths is lower then theminimum. With the Fence Level setting (specified during the initial copy),you decide whether, when the pair is split due to an error, the hostcontinues to access the P-VOL or is denied access. See Allowing I/O to theP-VOL after a split—Fence Level options on page 3-13 for moreinformation.

Analyzing workload, planning data pathsYou optimize copy operations and performance by carefully planningbandwidth, number of data paths and host interface paths, and number ofports. This is discussed in:

Check with your Hitachi Data Systems Support Center for more information.

• Analyze write-workload. Bottlenecks severely impact performance, butthe workload data you collect (MB/s and IOPS) help determine thefollowing key elements that, when sized properly, form a data path thatoperates free of bottlenecks under all workload levels:

¢ Amount of bandwidth.¢ Number of data paths.¢ Number of host-interface paths.¢ Number of ports dedicated for TrueCopy for Mainframe on the primary

and secondary system.• If you are setting up TrueCopy for Mainframe for disaster recovery, make

sure that secondary systems are attached to a host server. This enablesboth the reporting of sense information and the transfer of host failoverinformation. If the secondary site is unattended by a host, you mustattach the storage systems to a host server at the primary site so thatthe system administrator can monitor conditions.

The following table lists conditions that affect storage system performanceand provides recommendations for addressing them.


Condition Description Recommendation

Write-intensiveworkloads

Write-intensive workloads, such asdatabase logging volumes, canhave a significant impact on storagesystem I/O response times.

Spread write-intensive dataacross several volumes tominimize queuing.

Large blocksize

Workloads with large write blocksizes, such as DB deferred writes,can impact performance.

Spread workloads with large writeblock sizes across severalvolumes.

High hostchanneldemand

The demand on the primary systemhost channels can affectperformance.

Spread the workload acrossseveral storage systems to useadditional channels.

Sequentialwriteoperations

TrueCopy for Mainframe operationscan have a negative impact onworkloads with a high percentage ofsequential write operations, such asbatch processing operations (forexample, dump/restore, sortoperations).

Avoid performing restoreoperations to volumes that belongto TrueCopy for Mainframe pairs.Instead, restore data to a scratchvolume, and then create theTrueCopy for Mainframe pair.

Cache size Large cache size improves readperformance, which allows morestorage system resources to bedevoted to write operations.Insufficient cache resources resultin command retries, state-change-pending (SCP) notifications, andpuncture conditions.

Consider increasing the cache sizeof the TrueCopy for Mainframestorage systems to improveoverall performance. For bestresults, the cache and NVScapacity of the primary andsecondary system should be thesame. This allows the secondarysite to function adequately duringdisaster recovery.

Remote systemperformance

The secondary system'sperformance directly affects theperformance of the primary system.If a secondary system becomesoverloaded with heavy updateactivity, host and primary systemperformance can also be degraded.

Distribute TrueCopy forMainframe remote copyoperations among severalsecondary systems to avoidoverloading any one system.

Data paths An inadequate number of datapaths decreases performance.Performing copy operations overlong distances also degradesperformance.

Install a sufficient number of datapaths to meet all write-workloadlevels. This is especially importantfor systems containing both P-VOLs and S-VOLs.

Planning pairs and pair volumesThis section discusses requirements, options, and settings you need forsetting up pairs and pair volumes. You begin by:

• Identifying data and volumes at the primary site that you want to protectwith a backup

• Setting up volumes at the secondary site that will hold copied data.

The following helps ensure that the pairs you create fit your requirements.


• Pair volume requirements and recommendations on page 3-10• Precautions for duplicate VOLSERs on page 3-12• Allowing I/O to the S-VOL on page 3-12• Allowing I/O to the P-VOL after a split—Fence Level options on page

3-13• Differential data on page 3-14• Maximum number of pairs supported on page 3-14• Options and settings for number of pairs copied, and their priority, during

the initial copy and resync operations. See Priority for initial copyoperations and scheduling order on page 3-15

Pair volume requirements and recommendationsThe following is provided to help you prepare TrueCopy for Mainframevolumes:

• A volume can be assigned to only one pair.• Volumes on the primary and secondary storage systems must be defined

and formatted prior to pairing.• The S-VOL must be equal-to or larger-than the P-VOL. However, if the S-

VOL is larger than the P-VOL, the swap operation cannot be performed.• TrueCopy for Mainframe requires a one-to-one relationship between the

P-VOL and S-VOL. The P-VOL cannot be copied to more than one S-VOL,and an S-VOL cannot have more than one P-VOL.

• Logical Volume Images (LVIs)

¢ All basic mainframe LVIs that can be configured on the VSP G1000system are supported for TrueCopy for Mainframe; for example, 33903, 3R, 9, L.

¢ Multi-platform volumes (3390 3A/B/C) are not supported.¢ Data can be copied between volumes with the same emulation and

capacity (for example, 3390 3R to 3390 3R).¢ Data can be copied from smaller volumes to larger volumes (for

example, 3390 3 to 3390 9) of the same emulation (VTOC expansionmust be used).However, HDS strongly recommends that you limit copying from asmaller volume to a larger volume to data migration purposes and notdisaster recovery. Under the disaster recovery scenario, you wouldnot be able to perform TrueCopy for Mainframe operations in thereverse direction, from the secondary system to the primary system,because a larger volume cannot be copied to a smaller volume.Also, with larger-to-smaller volumes, if the BCM SUSPEND commandis issued, you cannot use the secondary system R/W option andReverse option.

• Pair volumes have the following disk track format requirements. TrueCopyfor Mainframe cannot detect exceptions to these requirements. The


primary system will abort the initial copy operation if the track format forboth the P-VOL and S-VOL does not meet the following requirements:

¢ The P-VOL and S-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 primary system will abort the initial copyoperation if R0 is not standard format.

¢ The CCHH (logical cylinder address and logical head address) of R0must be identical to the physical cylinder address and physical headaddress of the track.

¢ The CCHH of each user record in a track must be unique.• TrueCopy for Mainframe operates on volumes rather than on datasets;

multi-volume datasets require special attention. For complete duplicationand recovery of a multi-volume dataset (for example, a large databasefile that spans several volumes), make sure that all volumes of the fileare copied to TrueCopy for Mainframe S-VOL.

• TrueCopy for Mainframe pair volumes can be shared with non-TrueCopyfor Mainframe Hitachi software products. See Chapter 4, SharingTrueCopy for Mainframe volumes on page 4-1 for more information.

• TrueCopy for Mainframe supports Virtual LVI. This allows you to configureLVIs that are smaller than standard LVIs. When custom-size LVIs areassigned to a TrueCopy for Mainframe pair, the S-VOL must have thesame capacity as the P-VOL. Device Manager - Storage Navigator displaysthe size of P-VOLs and S-VOL.

• Before creating multiple pairs during the Create Pairs operation, makesure to set up S-VOL LUNs to allow the system to correctly match them toP-VOLs.You must do this because, even though you select multiple volumes as P-VOLs, you specify just one S-VOL. The system automatically assignssubsequent secondary system LUs as S-VOLs based on the option youspecify for Selection Type. These are the options:

¢ Interval: The interval you specify will be skipped between LU numbersin the secondary system.For example, suppose you specify LDEV 01 as the initial (base) S-VOL, and specify 3 for Interval. This results in secondary system LU04 being assigned to the next P-VOL, 07 assigned to the subsequentP-VOL, and so on. To use Interval, you set up secondary system LUnumbers according to the interval between them.

¢ Relative Primary Volume. The difference is calculated between theLDEV numbers of two successive P-VOLs. S-VOLs are assignedaccording to the closest LDEV number.For example, if the LDEV numbers of three P-VOLs are 01, 05, and06; and you set LDEV numbers for the initial S-VOL (Base SecondaryVolume) at 02, the LDEV numbers of the three S-VOLs will be set at02, 06, and 07, respectively.


Precautions for duplicate VOLSERsFor the TrueCopy for Mainframe initial copy operation, P-VOL VOLSER(Volume Serial Number) is also copied to the S-VOL when Entire Volume isselected for the Initial Copy Type. Therefore, the P-VOL and S-VOL have thesame VOLSER. Because the host operating system does not allow duplicateVOLSERs, the host system administrator must take precautions to preventsystem problems related to duplicate VOLSERs (such as defining S-VOLs notto come online automatically).

If the volumes that become S-VOLs are physically attached to the samesystem images as the volumes that become the P-VOLs, the following error-prone situations may occur:

• When a pair is established using the TSO CESTPAIR command, thesecondary system might be online (PPRC allows this; TrueCopy forMainframe does not). This could produce a duplex secondary online to ahost image, the results of which are not predictable.

• When a pair is released, the old S-VOL is usually offline. Then, when ahost system is IPL'd (initial program loaded), the operator is offered bothvolumes and asked which volume should be left offline. You can avoidduplication of the VOLSER as follows:

a. Identify the volumes that are not accessed by the host system.b. Perform CHP OFF or some other operation to ensure that the volumes

are inaccessible.c. When performing IPL, make sure to perform LOAD CLEAR.

To avoid such situations:

• HDS strongly recommends that you specify OFFLINE=YES if thesecondary volumes are to be generated in the production host's IOCP andsystem generation.

• If you cannot create a pair because the S-VOL is online with hosts, allpaths must be offline from all hosts. If you cannot identify the hosts thatare online, contact your Hitachi Data Systems Support Center. You canobtain the information about online paths from SSBLOG of the SVP.

Allowing I/O to the S-VOLThe secondary system rejects I/O to the S-VOL, unless the S-VOL-read optionis enabled. The S-VOL read option allows read-only access to an S-VOL whilethe pair is split. Differential data is managed using bitmaps by track; thisdata is used when the pair is resynchronized.

• The S-VOL read option (mode 20) must be enabled by a Hitachi DataSystems Support Center.

• When you read an S-VOL from the host, the reference date in the VTOC isupdated. In this case, you must permit update of the VTOC.

• The CSUSPEND command to the S-VOL of a split pair will be rejectedwhen the S-VOL read option is enabled, for I-2107 controller emulation.


• If system mode 20 is enabled, the VOLSER of the split S-VOL may bechanged, which allows the S-VOL to be online to the same host as the P-VOL, while the pair is split. All other write I/Os to the S-VOL are rejected.The primary system copies the P-VOL VOLSER to the S-VOL when the pairis resynchronized.

• For write-access to an S-VOL, release the pairs, or enable the write optionand then split the pairs.

Allowing I/O to the P-VOL after a split—Fence Level optionsYou can specify whether the host is denied access or continues to access theP-VOL when the pair is split due to an error. This is done with the PrimaryVolume Fence Level setting. You specify one of the following Fence Leveloptions during the initial copy and resync operations. You can also change theFence Level option outside these operations.

• Data – the P-VOL is fenced if an update copy operation fails. Thisprevents the host from writing to the P-VOL during a failure. This settingshould be considered for the most critical volumes for disaster recovery.This setting reduces the amount of time required to analyze theconsistency of S-VOL data with the P-VOL during disaster recoveryefforts.This setting is functionally equivalent to the CRIT(YES-ALL) parameter forthe CESTPAIR command.

• Status – the P-VOL is fenced only if the primary system is not able tochange S-VOL status to suspended when an update copy operation fails.If the primary system successfully changes S-VOL pair status tosuspended, subsequent write I/O operations to the P-VOL will beaccepted, and the system will keep track of updates to the P-VOL. Thisallows the pair to be resynchronized quickly. This setting also reduces theamount of time required to analyze S-VOL consistency during disasterrecovery.This setting is functionally equivalent to the CRIT(YES PATHS) parameterfor the CESTPAIR command.

• Never – the P-VOL is never fenced. This setting should be used when I/Operformance out-weighs data recovery. "Never" ensures that the P-VOLremains available to applications for updates, even if all TrueCopy forMainframe copy operations have failed. The S-VOL may no longer be insync with the P-VOL, but the primary system keeps track of updates tothe P-VOL while the pair is suspended. Host failover capability is essentialif this fence level setting is used. For disaster recovery, the consistency ofthe S-VOL is determined by using the sense information transferred viahost failover or by comparing the S-VOL contents with other filesconfirmed to be consistent.This setting is functionally equivalent to the CRIT(NO) parameter for theCESTPAIR command.


Differential dataDifferential data is update data collected while the pair is split.

With VSP G1000, data is stored in units of tracks using bitmaps, and is thenused to resynchronize the pair.

• If your primary system is a VSP or earlier model, which support tracksand cylinders, make sure that the unit of the differential datamanagement is track.

• If VSP G1000 is the primary system and you are using CCI, though CCIallows you to specify track or cylinder, only track will be used by the VSPG1000.

Maximum number of pairs supportedTrueCopy for Mainframe supports a maximum of 65,280 pairs, which is themaximum number of pairs supported by the VSP G1000 storage system. IfBCM or CCI is used, a command device must be defined for each product;therefore, the maximum number of pairs in VSP G1000 is calculated bysubtracting the number of command devices from 65,280.

Calculating maximum number of pairs

It is necessary to calculate the maximum number of pairs you can have onthe VSP G1000 storage system. The maximum number is based on thefollowing:

• The number of cylinders in the volumes, which must be calculated.• The number of bitmap areas required for a TrueCopy for Mainframe

volume, which is calculated using the number of cylinders.

Note: In the following formulas: for ceil(), round up the result within theparentheses to the nearest integer, and for floor(), round down the resultwithin the parentheses to the nearest integer.

To calculate the maximum number of pairs

1. Calculate the number of cylinders.

a. Calculate the system's number of logical blocks.Number of logical blocks = Volume capacity (bytes) / 512

b. Calculate the number of cylinders:For 3390:Number of cylinders = ceil ( (ceil (Number of logicalblocks / 116) ) / 15)

2. Calculate the number of bitmap areas per volume.In the following calculation, differential data is measured in bits. 122,752bits is the amount of differential data per bitmap area.Number of bitmap areas = ceil ( (Number of cylinders x 15) /122,752)


Note: Doing this calculation for multiple volumes can result ininaccuracies. Perform the calculation for each volume separately, thentotal the bitmap areas. The following examples show correct and incorrectcalculations. Two volumes are used: one of 10,017 cylinders and anotherof 32,760 cylindersCorrect calculationceil ((10,017 x 15) / 122,752) = 2ceil ((32,760 x 15) / 122,752) = 5Total: 7Incorrect calculation10,017 + 32,760 = 42,777 cylindersceil ((42,777 x 15) / 122,752) = 6Total: 6

3. Calculate the maximum number of pairs, which is restricted by thefollowing:

¢ The number of bitmap areas required for TrueCopy for Mainframe(calculated above).

¢ The total number of bitmap areas in the storage system, which is65,536.Bitmap areas are also used by TrueCopy, Universal Replicator, andUniversal Replicator for Mainframe.Therefore, the number of bitmap areas used by these other programproducts (if any) must be subtracted from 65,536, with the differenceused to calculate the maximum number of pairs for TrueCopy forMainframe.If TrueCopy for Mainframe and Universal Replicator for Mainframeshare the same volume, you must use the total number of bitmapareas for both pairs regardless of whether the shared volume isprimary or secondary.

¢ The maximum number of pairs supported per storage system, whichis 65,280 (65,279 if BCM is used).

Use the following formula:Maximum number of pairs = floor (Total number of bitmap areasin the storage system / Required number of bitmap areas)If the calculated maximum number of pairs exceeds the total number ofLDEVs of the storage system, and the total number of LDEVs of thestorage system is less than 65,280, then the total number of LDEVs of thestorage system becomes the maximum number of pairs.

Priority for initial copy operations and scheduling orderThough you can specify a maximum number of initial copies to runconcurrently, you are allowed to perform more initial copies than this whencreating pairs. If you do this, you will set the scheduling order for theadditional operations in the Initial Copy Priority field when creating the pair.


This topic provides two examples in which priority and the pre-set schedulingorder are discussed.

Note: The Initial Copy Priority option discussed here is not supported by thefollowing non-HDvM - SN commands: PPRC CESTPAIR, BCM YKMAKE, andCCI paircreate. When the pair is created using these commands, the initialcopy is performed according to the order that the command is run.

Example 1: more initial copies than previously specified

In this example, four initial copies are being created in the same operation,but Maximum Initial Copy Activities is set at 2. In this scenario, the InitialCopy Priority field in the Create TC Pairs window would be set as shown in thefollowing table.

P-VOL Value set for Initial Copy Priority

LDEV 00 2

LDEV 01 3

LDEV 02 1

LDEV 03 4

The order for the initial copy and the Initial Copy Priority for the P-VOLs areshown in the following table.

Order for initial copy P-VOL Value set for Initial CopyPriority

1 LDEV 02 1

2 LDEV 00 2

3 LDEV 01 3

4 LDEV 03 4

In this case, because the value of Maximum Initial Copy Activities is 2, initialcopy operations for LDEV 02 and LDEV 00 are started. If either one of theinitial copy operations for LDEV 02 and LDEV 00 is completed, the initial copyfor LDEV 01 is started.

Example 2: initial copy started, new pairs added

The following table shows the Initial Copy Priority value when the initial copyis already begun and then two new pairs are added. The P-VOLs are for thenew pairs

P-VOL Value set for Initial Copy Priority

LDEV 10 2

LDEV 11 1


If initial copy is already started, and if a new initial copy is added, theadditional initial copy is started after the previously performed initial copy iscompleted. The priority of all the initial copy operations being performed isshown in the following table.

Starting order forinitial copy P-VOL

Value set forInitial Copy

PriorityRemarks

1 LEDV 02 1 Previously scheduled.

2 LDEV 00 2 Previously scheduled.



5 LDEV 11 1 Scheduled later.

6 LDEV 10 2 Scheduled later.

Initial Copy Priority is determined using the Edit Remote Replica Optionswindow within the range of the number of initial copy operations performedat the same time. Therefore, until the first initial copy operations complyingwith the order set by Initial Copy Priority are completed, the additional initialcopy operations are not started.

Consistency group planningConsistency groups allow you to perform one operation on all pairs in thegroup. Consistency groups also ensure that all pairs are managed in aconsistent status.

You determine which pairs to include in a particular consistency group. This isbased on business criteria for keeping status consistent across a group ofpairs, and for performing specific operations at the same time on the group.

• A consistency group can consist of the pairs in one primary and onesecondary VSP G1000, or pairs in multiple primary and secondary VSPG1000s.

• Both TC and TCz pairs can belong to the same consistency group.

Consistency group for pairs in one primary and one secondary VSPG1000

TC and TCz pairs between one primary and secondary system can be placedin the same consistency group, as shown in the following figure.


Figure notes:

• TC pairs are assigned to a consistency group using CCI.TCz pairs are assigned to a consistency group using Business ContinuityManager (BCM).

• Open and mainframe volumes (P-VOLs/P-VOLs) receive I/O requests fromtheir applications at the primary (main) site, and data in the volumes isupdated.

• TC or TCz runs copy operations in the consistency group.

Consistency group for pairs in multiple primary and secondarysystems

TC and TCz pairs in multiple primary and secondary systems can be placed inthe same consistency group. A maximum of four storage system pairings canbe placed in the same consistency group.


Figure notes:

• CCI manages the consistency group on all primary and secondary system.Business Continuity Manager cannot be used with multiple systems.

• Open and mainframe primary volumes (P-VOLs/P-VOLs) receive I/Orequests from their applications at the primary (main) site, and data inthe volumes is updated.

• TrueCopy or TrueCopy for Mainframe runs the copy operation in theconsistency group.

• When the open or mainframe host system guarantees the update order,then data consistency in P-VOLs and S-VOLs is insured. When the hostsystem does not guarantee update order, data consistency is not insured.

Consistency group requirements Requirements are provided for the following consistency group (CTG)configurations.

• Consistency group for pairs in one primary and one secondary VSP G1000on page 3-17

• Consistency group for pairs in multiple primary and secondary systems onpage 3-18


Requirements for a CTG for one primary and one secondary system

• A consistency group is configured on the primary and secondary system.• A maximum of 8,192 pairs can be assigned to a consistency group.• A maximum of 256 consistency groups can be assigned to one primary

and one secondary system.• Assign a consistency group number in a range from 00-FF. The number

must be unused.• When you have multiple pairs in the same consistency group, they must

exist between the same primary and secondary system.• A pair can be assigned to one consistency group only.• TrueCopy pairs can be in the same consistency group as TrueCopy for

Mainframe pairs. Use the same consistency group number for both types.• If you use BCM to resynchronize a TCz pair in an open/mainframe

consistency group with one primary and secondary system, all pairs in theconsistency group are resynchronized. Even if a TC S-VOL is beingaccessed by a host, the pair is nevertheless resynchronized with theothers. Make sure to check the status of all pairs in the consistency groupbefore resynchronizing.

• If you use BCM to delete a TCz pair in an open/mainframe consistencygroup with one primary and secondary system, only the TCz pairs aredeleted. Use CCI to delete the TC pairs.

Requirements for a CTG for multiple primary and secondary systems

• All requirements for a consistency group between one primary and onesecondary system apply to a consistency group between multiple primaryand secondary systems.

• The primary and secondary systems can be VSP G1000 or VSP. No othermodels can be used.

• A consistency group can consist of a maximum of four primary and foursecondary (paired) systems.

• The microcode for both primary and secondary systems must supportconsistency groups between multiple primary and secondary systems;otherwise, pair creation results in failure.

• You must install the version of CCI that supports a consistency groupconsisting of multiple primary systems and secondary systems.

• Pair operations can be performed from CCI only. Business ContinuityManager and Device Manager - Storage Navigator do not support pairoperations for pairs in a CTG with multiple VSP G1000s.

• Cascade configurations with Universal Replicator for Mainframe pairs isnot supported.


Assigning pairs to a consistency groupPairs are assigned to a consistency group (CTG) during the Add Pairoperation. The procedure to assign pairs depends on the number of VSPG1000s in the CTG, as follows:

• Assigning pairs belonging to one primary and secondary system on page3-21

• Assigning pairs belonging to multiple primary and secondary systems onpage 3-21

Assigning pairs belonging to one primary and secondary system

The method for assigning pairs to a consistency group differs according to theGUI used to create the pairs:

• When using CCI, see the Hitachi Command Control Interface User andReference Guide

• When using Business Continuity Manager, see the Business ContinuityManager User Guide

Assigning pairs belonging to multiple primary and secondary systems

Assigning pairs in multiple primary and secondary systems to a consistencygroup depends on whether you are:

• Using a new CTG on page 3-21• Using an existing CTG on page 3-22

CCI is used when creating and assigning pairs to a consistency group onmultiple VSP G1000s. Business Continuity Manager is not supported for thisconfiguration.

Using a new CTG

You can assign new pairs or existing pairs to a new consistency group.

To assign new pairs to a new consistency group

1. Create CCI configuration definition file C for a multiple primary andsecondary system configuration.

2. Perform the paircreate operation according to configuration definition fileC created in Step 1.

To assign existing pairs to a new consistency group

1. Create CCI configuration definition file A with which to use CCI for pairoperations.

2. Perform the pairsplit operation according to configuration definition file Acreated in Step 1.

3. Perform the pairresync operation without designating a consistencygroup. Do this using configuration definition file A.

4. Perform the pairsplit operation again using configuration definition file A.


5. Create CCI configuration definition file C for the multiple primary andsecondary system configuration.

6. Perform the pairresync operation and register them to configurationdefinition file C.

Using an existing CTG

You can assign new pairs or existing pairs to an existing consistency group.

To assign new pairs to an existing consistency group

1. Add pair information to the existing configuration definition file B, whichconsists of pairs in multiple VSP G1000s.

2. Copy and create CCI configuration definition file C.3. Perform the paircreate operation and register them to configuration

definition file C.

To assign existing pairs to an existing consistency group

1. Create CCI configuration definition file A to use with CCI for pairoperations.

2. Perform the pairsplit operation on pairs that you want to register in theexisting CTG with multiple systems. Do this using configuration definitionfile A.

3. Perform the pairresync operation without designating a consistencygroup. Do this using configuration definition file A.

4. Perform the pairsplit operation again using configuration definition file A.5. Perform the pairsplit operation to the existing configuration definition file

B, which consists of the pairs in the multiple primary and secondarysystem configuration.

6. Add pair information to existing configuration definition file B.7. Delete then re-create the pairs, registering them in configuration

definition file C.

Split behaviors for pairs in a CTGWhen the pairs in a consistency group receive updates while in the process ofbeing split or suspended, or when they are about to be split or suspended, S-VOL data consistency is managed as follows:

• If I/O processing is in progress on pairs in the same consistency group,and the split or suspend operation begins, the I/O processing completesfirst, then the split/suspend operation is run.The following figure shows that I/O processing completes first; then thepair split operation for the pair on Volume B completes.


The following figure shows data in track 2 being copied to the S-VOL, and thedata in track 3 becomes differential data. In this case, track 2 is used for I/Oprocessing to the volume in the consistency group when the split command isissued to the pair.

• If a split operation is in progress when I/O processing on the pairs begins,the split operation on the pairs is given priority. After the pair is split,then the I/O processing begins.In a split operation, the IEA491E message displays on the mainframe hostwhen pair status changes to pair split-error.In a split operation, the IEA491E message displays on the mainframe hostwhen pair status changes to pair split-error.

• Data consistency cannot be ensured when all of the following conditionsexist:- A port is blocked.- A split command is in progress.


- I/O processing begins.In such a case, resynchronize the consistency group and then run thesplit command again.

Host access after split

You can specify settings for read/write access to the P-VOL/P-VOL and S-VOL/S-VOL in consistency groups after pairs are split. These settings arespecified using CCI or Business Continuity Manager.

• The CCI settings for TC are optional.• The Business Continuity Manager settings for TCz are required.

The following tables show the effects of the settings on read and write access.

Interface SettingTC P-VOL TCz P-VOL

Read Write Read Write

CCI* Write access prohibited Y N Y N

No option selected Y Y Y Y


Write access prohibited Y N Y N

Write access permitted Y Y Y Y

* The effect on read/write shown in this table applies to the TC P-VOL. When CCI is usedwith a TCz P-VOL, the effect is the same as "No option selected".

Interface SettingTC S-VOL TCz S-VOL

Read Write Read Write

CCI* Read access permitted Y N N N

Read/Write access permitted Y Y Y Y

No option selected Y N N N


Write access prohibited Y N N N

Write access permitted Y Y Y Y

* The effect on read/write shown in this table applies to the TC S-VOL. When CCI is usedwith a TCz S-VOL, the effect is the same as "No option selected".

Pair status before and after a split operation

Pairs in the same consistency group must be in PAIR/Duplex status when youbegin the split operation in order to maintain consistency. Otherwise, whenthe operation completes, pair status will be inconsistent.

This is shown in the following table, in which font angle indicates thefollowing:

• Italics font: Pair status before the split operation on the consistency group• Regular font: Status after the split operation


Pair statusesTCz pairs

All = Duplex Some = Duplex, some= Suspend All = Suspend

TCpairs

All = PAIR TC: PSUSTCz: Suspend

TC: PSUSTCz: Suspend


Some = PAIR,some = PSUS




All = PSUS TC: PSUSTCz:- CCI: Duplex- BCM: Suspend

TC: PSUSTCz:- CCI: Duplex/Suspend- BCM: Suspend


Notes when you remove or resynchronize pairs by BusinessContinuity Manager

When you resynchronize the TrueCopy for Mainframe pair in the Open/MFconsistency group which consists of one pair of the primary storage systemand the secondary storage system by Business Continuity Manager, all pairsin the consistency group are resynchronized. If the host is accessing the S-VOL of the TrueCopy pair, the TrueCopy pair is also resynchronizedsimultaneously. Resynchronize the pair after you reconfirm the status of allTrueCopy pairs and all TrueCopy for Mainframe pairs in the consistencygroup.

When you remove the TrueCopy for Mainframe pair in the Open/MFconsistency group which consists of one pair of the primary storage systemand the secondary storage system by Business Continuity Manager, only theTrueCopy for Mainframe pairs in the consistency group are removed. If youwant to remove the TrueCopy pair simultaneously, you must remove thepairs by CCI.

Error reporting communicationsError reporting communications (ERC) transfers information between hostprocessors at the primary and secondary sites. It is a critical component of adisaster recovery effort.

You can configure ERC using channel to channel communications, NetViewtechnology, or other inter-connection technologies depending on yourinstallation requirements and standards. TrueCopy for Mainframe does notprovide ERC between the primary and secondary sites.

• When TrueCopy for Mainframe is used as a disaster recovery tool, ERC isrequired to ensure effective recovery operations.

• When TrueCopy for Mainframe is used as a data migration tool, ERC isrecommended.


• When a pair is split due to an error condition, the primary systemgenerates sense information that results in an IEA491E system consolemessage. This information should be transferred to the secondary siteusing ERC for effective disaster detection and recovery.

Data path requirements and configurationsA data path must be designed to adequately manage all possible amounts ofdata that could be generated by the host and sent to the P-VOL and S-VOL.This topic provides requirements and planning considerations for the followingkey elements of the data path:

• Bandwidth requirements on page 3-26• Fibre Channel requirements on page 3-26• Supported data path configurations on page 3-27• Ports on page 3-30

Bandwidth requirementsSufficient bandwidth must be present to handle data transfer of all workloadlevels. The amount of bandwidth required for your TrueCopy for Mainframesystem is based on the amount of I/O sent from the host to the primarysystem. You determine required bandwidth by measuring write-workload.Workload data is collected using performance monitoring software. Consultyour Hitachi Data Systems Support Center for more information.

Fibre Channel requirementsThe primary and secondary system must be connected using multimode orsingle-mode optical fibre cables. As shown in the following table, the cablesand data path relay equipment required depend on the distance between theP-VOL and S-VOL storage systems.

Distance Fibre cable type Data path relayequipment

0.5 km to 1.5 km (4,920feet)

Multimode shortwave FibreChannel interface cables.

At least one switch isrequired, and a maximum oftwo switches can be used.

1.5 km to 10 km (6.2miles)

Single-mode longwave2 opticalfibre cables.

Not required.

10 km to 30 km (18.6miles)

Single-mode longwave2 FibreChannel interface cables.

Up to two switches can beused.

Greater than 30 km(18.6 miles)1

Communications lines arerequired.

Approved third-partychannel extender products.3

1. TrueCopy for Mainframe operations typically do not exceed 30 km.2. Longwave cannot be used for FCoE.


Distance Fibre cable type Data path relayequipment

3. For more information about approved channel extenders, contact HDS (see Gettinghelp on page xiii).

With Fibre Channel connections, no special settings are required for VSPG1000.

Direct connections up to 10 km with single-mode longwave Fibre Channelinterface cables are supported. Link speed determines the maximum distanceyou can transfer data and still achieve good performance. The following tableshows maximum distances at which performance is maintained per linkspeed, over single-mode longwave Fibre Channel.

Link speed Distance maximum performance maintained

1 Gbps 10 km

2 Gbps 6 km

4 Gbps 3 km

8 Gbps 2 km

16 Gbps 1 km

Your Hitachi Data Systems Support Center can provide the latest informationabout the availability of serial-channel TrueCopy for Mainframe connections.

Supported data path configurationsThree Fibre Channel configurations are supported for TrueCopy forMainframe:

• Direct connection on page 3-28• Switch connection on page 3-29• Extender connection on page 3-29

For direct and switch connections, host I/O response time can be improvedon long distance direct connections (longwave, less than 10km/6.2 miles) byimproving the I/O response time between storage systems and by using hostmode options 49 and 50, or 51. The following table describes these optionsfor the open package. Hitachi Data Systems-approved channel extender isrequired. For more information on host mode options, see the Hitachi VirtualStorage Platform G1000 Provisioning Guide for Open Systems.

No Host modeoptions Description

49 BB Credit Set UPOption 1

Fixes higher values of buffer-to-buffer credits (BBCs) toincrease data transfer size over long distances.1 Thishost mode option must be used in conjunction with hostmode option 50.2


No Host modeoptions Description

50 BB Credit Set UPOption 2

Fixes higher values of buffer-to-buffer credits (BBCs) toincrease data transfer size over long distances.1 Thishost mode option must be used in conjunction with hostmode option 49.2

513 Round Trip SetUP Option

Improves host I/O response time for long distance switchconnections.2

Notes:1. Up to 10 km for direct connection and 100 km for switch connection.2. The microcode supporting these functions must be installed on both the primary and

secondary systems.3. Host mode option 51 is not supported for 8FC16 or 16FE10 packages.

Direct connection

The following figure shows a direct connection, in which two devices areconnected directly together.

Set port topology to: Fab off, FC-AL.

As shown in the following table, Fab settings, topology settings, and availablelink speed depend on the settings of the packages and protocols used for thestorage system connections, as well as whether host mode option 51 is used.

Packagename Protocol Host mode

option 51 FabInitiator port andRCU target port

topologyAvailable link speed

16FC8 8GbpsFC OFF OFF FC-AL • 2 Gbps• 4 Gbps• 8 Gbps

ON OFF Point-to-Point • 2 Gbps• 4 Gbps• 8 Gbps

8FC16 16GbpsFC OFF OFF FC-AL • 4 Gbps• 8 Gbps


Switch connection

The following figure shows a switch connection, in which up to three opticalfibre cables are connected using switches. Two switches can be used.

Set port topology to the following:

• NL port: Fab on, FC-AL• N port: Fab on, Point-to-Point• Some switch vendors require F port (for example, McData ED5000).

As shown in the following table, Fab settings, topology settings, and availablelink speed depend on the settings of the packages and protocols used for thestorage system connections, as well as whether host mode option 51 is used.

Packagename Protocol

Hostmode

option 51Fab

Initiator port andRCU target port

topologyAvailable link speed

16FC8 8GbpsFC OFF ON Point-to-Point • 2 Gbps• 4 Gbps• 8 Gbps

ON ON Point-to-Point • 2 Gbps• 4 Gbps• 8 Gbps

8FC16 16GbpsFC OFF ON Point-to-Point • 4 Gbps• 8 Gbps• 16 Gbps

16FE10 10GbpsFCoE OFF ON Point-to-Point 10 Gbps

Extender connection

The following figure shows an extender connection, in which channelextenders and switches are used to connect the devices across largedistances.


Figure 3-1 Extender Connection

• Set port topology to the following:

¢ NL/FL port: Fab on, FC-AL¢ F port: Fab on, Point-to-Point

• Best practice is to create at least two independent data paths (one percluster) between the primary and secondary system for hardwareredundancy for this critical element.

• When 4,000 pairs or more are used, we recommend that you restrict thenumber of pairs when creating pairs, so that 4,000 pairs or less use onephysical path, to distribute load on the physical path.

• When you set up secondary-to-primary data paths, specify the same pathgroup ID as specified for the primary-to-secondary paths.

• You can reverse the primary-to-secondary data path to the secondary-to-primary direction using the PPRC TSO CESTPATH and CDELPATHcommands and system option mode 114. This can be done even if nosecondary-to-primary data path was previously set up. When systemoption mode 114 is enabled, these commands change the portconfiguration automatically.

PortsData is transferred along the data path from the initiator to the RCU targetports on the primary and secondary system. The amount of data each ofthese ports can transmit is limited.

Therefore, you must know the amount of data that will be transferred (write-workload) during peak periods. You can then ensure not only that bandwidthmeets data transfer requirements, but that a sufficient number of eachsystem's ports are specified as initiator and RCU target ports to handle allworkload levels.

Port requirements

Data is sent from the storage system port across the data path to thereceiving system's port.


Note: One secondary system port can be connected to a maximum of 16ports on a primary system. The number of remote paths that can be specifieddoes not depend on the number of ports configured for TrueCopy forMainframe. You can specify the number of remote paths for each remoteconnection.

Note: VSP G1000 automatically configures a Fibre Channel port as aninitiator or RCU target in response to the TSO CESTPATH and CDELPATHcommands. See system option mode 114 in S-VOL Read and other systemoptions on page 3-3.However, make sure not to run the CESTPATH and CDELPATH commands toconfigure a Fibre Channel port at the same time that the SCSI path definitionfunction for LUN Manager is in use.

Port attributes

Plan and define the following Fibre Channel port attributes for TrueCopy forMainframe:

• Initiator ports, which send data. One initiator port can be connected toa maximum of 64 RCU target ports. Configure initiator ports on bothprimary and secondary system for TrueCopy for Mainframe disasterrecovery operations.

• RCU target ports, which receive data. Configure RCU target ports onboth primary and secondary system for TrueCopy for Mainframe disasterrecovery operations.

• Target port: Connects the storage system and a host. When the hostissues a write request, the request is sent to a volume on the VSP G1000system via a target port on the storage system. Target ports must beconfigured on the primary system for TrueCopy for Mainframe operations.

• External port: Required for Universal Volume Manager copy operations.This port is not used for TrueCopy for Mainframe copy operations. Thisport can be changed to a target, initiator, or RCU target port.


4Sharing TrueCopy for Mainframe

volumes

This chapter helps you plan TrueCopy for Mainframe (TCz) pair volumes whenthey are shared with non-TCz volumes. All the software products that can beused with TCz are discussed here.

□ Volume types that can be shared with TrueCopy for Mainframe

□ Cache Residency Manager

□ Compatible XRC and CC

□ Dynamic Provisioning for Mainframe

□ Performance Monitor

□ ShadowImage for Mainframe

□ Universal Replicator for Mainframe

□ Virtual LVI

□ Volume Migration

□ Volume Retention Manager

Sharing TrueCopy for Mainframe volumes 4-1Hitachi TrueCopy® for Mainframe User Guide

Volume types that can be shared with TrueCopy forMainframe

The following table shows when volumes used by other software can also beused as TCz P-VOLs and S-VOLs.

Functions and volumes Used as P-VOL? Used as S-VOL?

Cache Residency Manager

Volume with CRM data Yes Yes

Compatible FlashCopy® V2

S-VOL Yes Yes

T-VOL Yes1, 3, 5 No

Compatible Software for IBM(R) FlashCopy(R) SE(4)

S-VOL Yes Yes

T-VOL No No

Compatible PAV

Compatible PAV volume Yes Yes

Compatible XRC

P-VOL Yes No

S-VOL Yes No

Concurrent Copy (CC)

CC volume Yes No

Cross-OS File Exchange

Volume for mainframe and open-systemsuse

No No

Dynamic Provisioning for Mainframe

DP-VOL Yes Yes

Pool vol No No

Dynamic Tiering for Mainframe

DP-VOL Yes Yes

Pool vol No No

ShadowImage for Mainframe

P-VOL in Split/SUSPOP status Yes Yes

P-VOL in Resync-R/REVRSY status No No

P-VOL when also used as a URz primary orsecondary volume

No No

P-VOL (none of the above) Yes Yes

S-VOL in Split/SUSPOP status Yes No

4-2 Sharing TrueCopy for Mainframe volumesHitachi TrueCopy® for Mainframe User Guide


S-VOL (none of the above) No No

Reserved volume No1, 3, 5 No

Universal Replicator for Mainframe

P-VOL (primary system) in Pending status No No

P-VOL in Duplex status Yes No. The volume canbe used as an S-VOLonly when you restorea TCz pair or performa BCM YKRESYNCREVERSE operation.

P-VOL in Suspend status Yes No. The volume canbe used as S-VOLonly when you restorea TCz pair or performa BCM YKRESYNCREVERSE operation.

P-VOL suspended due to a failure Yes No. The volume canbe used as S-VOLonly when you restorea TCz pair or performa BCM YKRESYNCREVERSE operation.

S-VOL (secondary volume) in Pendingstatus

No No

S-VOL in Duplex status No No

S-VOL in Suspend status Yes No

S-VOL in Swapping status Yes No

S-VOL suspended due to a failure Yes No

Universal Volume Manager

Mapped external volume Yes Yes

Virtual Partition Manager(VPM)

Volume belonging to the Virtual PartitionManager CLPR

Yes Yes

Virtual LVI

Virtual LVI volume Yes Yes

Volume Migration2

Source volume (when volume migration isin progress)

Yes. If the sourcevolume is used as aP-VOL, volumemigration stops.

Yes. If the sourcevolume is used as anS-VOL, volumemigration stops.

Source volume (after vol migrationfinishes)

Yes Yes



Target volume No No

Reserved volume No No

Volume Retention Manager

Volume with Read/Write attribute Yes Yes

Volume with Read Only attribute Yes Yes

Volume with Protect attribute No No

Volume Security

Volume registered in a security group Yes Yes. If the volume isdisabled for use as S-VOL, the volumecannot be used as S-VOL.

1. The volume performs differently according to the type of difference management.2. For more information, contact the Hitachi Data Systems Support Center.3. If you use TCz with Compatible FlashCopy® V2, the TCz pairs must be created

without using the consistency groups.4. See the section on compatible software in the Hitachi Compatible FlashCopy® User

Guide.5. When you create Compatible FlashCopy® V2 Preserve Mirror relationships in COPY

mode, both copies are not synchronized. If you issue Withdraw during the copyoperation, both copies of the relationship are suspended. Therefore, the consistencyof the data between P-VOL and S-VOL is not ensured even though the TCz pair is inDuplex status. To release this status, delete the TCz pair.

The following topics include additional information about shared volumes.

Cache Residency ManagerThe volumes which set the Cache Residency Manager can be assigned as theTrueCopy for Mainframe pair. You can perform Cache Residency Manageroperations on TCz P-VOLs and S-VOLs. For more information, see the HitachiVirtual Storage Platform G1000 Performance Guide.

Compatible XRC and CCVSP G1000 is functionally compatible with the IBM Extended Remote Copy(XRC) function and the IBM I-2107 Concurrent Copy (CC) function. For moreinformation about XRC and/or I-2107 CC, see the applicable IBMdocumentation.


Dynamic Provisioning for Mainframe You can create a Universal Replicator pair by specifying a DP-VOL (DynamicProvisioning virtual volume). DP-VOLs can be assigned to both the TCz P-VOLand S-VOL, or to one of them. However, the following restrictions apply:

• DP-VOL use is limited by emulation type, as indicated in the followingtable.

P-VOL

S-VOL

DP-VOL/3390-A Ordinaryvolume/3390-A

Ordinary volume/3390-X1, 2

DP-VOL/3390-A Yes Yes No

Ordinary volume/3390-A

Yes Yes No

Ordinary volume/3390-X1

Yes Yes Yes

1. 3390 series other than 3390-A2. DP-VOL use in other than the 3390 series emulation type is not supported for

TrueCopy for Mainframe.

• Data migration is supported from an ordinary volume S-VOL/3390-X to aDP-VOL/3390-A S-VOL. However, the swap operation in this case is notsupported.

• You can use DP-VOLs that are also used in a ShadowImage for Mainframeor Compatible FlashCopy® V2 pair, or in a Volume Migration migrationplan. Before creating the TCz pair, delete the SIz or CompatibleFlashCopy® V2 pair, or disable the Volume Migration setting. After thepair is created, then re-create the pair or migration plan.

• When a DP-VOL has pages allocated to an S-VOL, used pool capacity istemporarily larger than the actual capacity because pages must bereallocated in the DP-VOL. Therefore, before creating the pair, make sureof the following:

¢ DP-VOL pool capacity is sufficient.¢ Pool-VOLs that are added to a pool are not blocked. If Pool-VOLs are

blocked, restore the volume status and then create the pair.• Regarding page and license capacity:

¢ When you create a TCz pair with a DP-VOL, the page capacityallocated to the DP-VOL is accumulated on the TCz license capacity.However, Dynamic Provisioning for Mainframe automatically releasespages with reclaiming zero pages in the DP-VOL, thus increasingusable capacity.Pages that include control cylinder information are not released (seenext).

¢ If a pair does not include a DP-VOL, volume capacity is countedtoward TCz license capacity.


If a pair includes a DP-VOL, only the allocated page capacity ofvolume capacity is counted toward TCz license capacity.If a DP-VOL and a non-DP-VOL are included in a pair, the pagecapacity and/or license capacity counted in the P-VOL and the S-VOLmay be different. This applies even when both P-VOL and S-VOLinclude DP-VOLs, because the page capacity of the P-VOL or the S-VOL changes by a relocated pool or released page or other action.

¢ Page or license capacity can also differ between the P-VOL and S-VOLfor the following reasons:- The TCz copy process overwrites S-VOL track data, even when thetrack is assigned to pages with no records in the P-VOL. This happensbecause when S-VOL track data is overwritten, TCz updates thecontrol cylinder information, which manages track information.Additional pages may result for holding control cylinder information inthe S-VOL, and these pages cannot released. Thus, the number ofpages in the S-VOL may be greater than in the P-VOL.- When you update the S-VOL in Suspended status, a page thatincludes control cylinder information may be assigned. Pages thatinclude the control cylinder information are not released, thus, thenumber of pages in the S-VOL may be greater than P-VOL.- When the TCz copy process is run for zero data pages in the P-VOL,the S-VOL may not assign zero data pages, thus there can be fewerpages in the S-VOL.

¢ TCz license capacity can be less than DP-VOL page capacity, howeverit cannot exceed page capacity.

• If the volume you will use for a TCz S-VOL is a DP-VOL and its capacity ismore than the P-VOL's capacity, before creating the pair, delete the S-VOL's datasets using the z/OS Security Server RACF (Resource AccessControl Facility) function. (See the appropriate IBM documents forinstructions.)

• When you run data migration from an P-VOL in an earlier storage modelto a DP-VOL RVOL, the DP-VOL S-VOL may consume the same pagecapacity as the P-VOL.

For more information, see the Hitachi Virtual Storage Platform G1000Provisioning Guide for Mainframe Systems.

Performance MonitorPerformance Monitor software provides detailed information about I/O activityand hardware performance in VSP G1000 systems. Storage system usageand performance data is collected and displayed by Performance Monitor.This information helps you to:

• Identify the optimum timing for performing TCz operations.• Determine the best locations for the TCz S-VOL (for example, parity

groups with less-frequently accessed volumes to avoid bottlenecks ofbackend activity).


• Monitor system performance during TCz operations and during testingactivities.

See the Hitachi Virtual Storage Platform G1000 Performance Guide for moreinformation.

ShadowImage for MainframeShadowImage for Mainframe volumes can be assigned to TCz pairs, and TCzvolumes can be assigned to SIz pairs. The following table shows theconfigurations that are possible.

TCz volume SIz P-VOL SIz S-VOL

P-VOL Yes Yes

S-VOL Yes No

Please note the following when sharing TCz volumes with SIz volumes.

• L1 and L2 SIz pairs can be shared with TCz volumes. Both node and leafS-VOLs are considered secondary volumes by TCz.

• When using PPRC, the Split status cannot be distinguished from the V-Split status. If you share an SIz S-VOL with a TCz P-VOL, either use thePPRC command to perform the Steady Split operation, or use DeviceManager - Storage Navigator to confirm the pair statuses. Perform theSteady Split operation using the CSUSPEND parameters (specify the serialnumber of the PRIM as MPS00).

Configurations with ShadowImage for Mainframe P-VOLsTCz can share an SIz P-VOL in three configurations:

• In the following figure, the TCz P-VOL also functions as an SIz P-VOL. Thisconfiguration allows you to use SIz for on-site data backup in case of TCzfailure. Or, the TCz S-VOL can be used to provide remote backup of theSIz P-VOL in case of an SIz failure.

Figure 4-1 Shared TCz P-VOL with SIz P-VOL

• In the following figure, the TCz S-VOL also functions as an SIz P-VOL. Inthis configuration, SIz provides another (or several more) backup copiesof a TCz P-VOL.


When an SIz P-VOL is shared with the TCz S-VOL, the write operation tothe TCz P-VOL takes a longer time than normal. This is especially truewhen the SIz pair is in the V-Split/SUSPVS status and is caused by theSIz copying process.

Figure 4-2 Shared TCz S-VOL with SIz P-VOL

• In the following figure, the configurations shown in the previous twofigures are combined. Both the TCz P-VOL and S-VOL function as SIz P-VOLs, providing multiple copies at the primary and secondary sites.

Figure 4-3 Shared TCz P-VOL, S-VOL with multiple SIz P-VOLs

Configurations with ShadowImage for Mainframe S-VOLsIn the following figure, an SIz S-VOL also functions as a TCz P-VOL. Thisconfiguration requires that the SIz pair is split before the TCz pair is created.

Figure 4-4 Shared SIz S-VOL with TCz P-VOL

Status reporting and data currencyThe following table shows the pair status that is reported for differentcombinations of shared volumes.

Number ofTCz pairs

Number of SIzS-VOLs Pair status

0 0 It does not display in pair list.


Number ofTCz pairs

Number of SIzS-VOLs Pair status

0 1 SIz pair status

0 2 or more SIz pair status for the S-VOL with lowest LDEV ID

1 0 TCz pair status

1 1 TCz pair status

1 2 or more TCz pair status

• TCz pair status is reported to the host if you query the TCz P-VOL or S-VOL. To obtain the SIz pair status, query the SIz P-VOL pair.

• SIz supports multiple S-VOLs for each of its P-VOLs, but when you issue apair status query, the status is returned only for the pair whose S-VOLhas the lowest LDEV ID. To check pair status for the other S-VOLs, directa host query to the specific S-VOL using the S-VOL's LDEV ID in the hostcommand.Device Manager - Storage Navigator displays the status of all S-VOLs.

The following table shows when data is current on a shared TCz/SIz volumebased on the pair statuses.

TCz pairstatus

SIz pair status

Pending DuplexSplit/

SUSPOPPending

V-Split/SUSPVS

Split/SUSPOP

Resync/Pending

Resync-R/

REVRSY

Suspended

PendingDuplex

NotCurrent

NotCurrent

NotCurrent

NotCurrent

Current NotCurrent

- NotCurrent

Duplex NotCurrent

NotCurrent

NotCurrent

NotCurrent

Current NotCurrent

- NotCurrent

Suspend -S-VOL byoperator/Suspend

NotCurrent

Current Current Current Current Current Current NotCurrent

Universal Replicator for MainframeTCz and Universal Replicator for Mainframe can share the same pair volumes.Using a combined TCz and Universal Replicator for Mainframe configurationcan extend disaster recovery options to a third data center.

Like TCz, a Universal Replicator for Mainframe pair maintains a copy of theproduction volume in a second location. However, unlike TCz, the UniversalReplicator for Mainframe S-VOL is asynchronous, and the secondary systemcan be located much greater distances from the primary and secondary TCzsites.


Creating both a TCz and a Universal Replicator for Mainframe backup ensuresthat a copy in a third location is available in the event that the primary site orone of the systems fails.

Configurations consisting of TCz and Universal Replicator for Mainframe pairvolumes are covered extensively in the Hitachi Universal Replicator forMainframe User Guide.

Virtual LVIVirtual LVI volumes can be assigned to TCz pairs, with the followingrestrictions:

• The S-VOL must have the same capacity as the P-VOL.• When performing Virtual LVI operations on an existing TCz P-VOL or S-

VOL, you must release the pair first to return the volume to Simplexstatus.

For more information, see the Hitachi Virtual Storage Platform G1000Provisioning Guide for Mainframe Systems.

Volume Migration The following table shows when TCz volumes may be used as VolumeMigration volumes.

Volume/pair status Used as Volume Migration volume?

P-VOL/S-VOL in Pending Duplex status No

P-VOL/S-VOL in Duplex status Yes

P-VOL/S-VOL in Suspend status Yes

RestrictionsThe following restrictions must be followed when a TCz volume in Duplexstatus is used as a Volume Migration volume:

• Set I/O rates less than 50 IOPS while migrating volumes; if more than 50IOPS, volumes may not be migrated.

• If a data path failure occurs, remove the failure then migrate the volume.• If an external volume or a DP-VOL is used, information from before the

volume is migrated displays in the secondary system Device Manager -Storage Navigator window. If the Volume Migration is completed and theTCz pair is suspended and resynchronized, the volume's information isupdated.

• Do not migrate P-VOL and S-VOL at the same time, or a host I/O timeoutwill occur.


• Do not change the status of a volume during migration; the status maynot change.

Volume Retention ManagerVolume Retention Manager access attributes can be assigned to TrueCopy forMainframe pair volumes. The following table shows how access attributeschange.

Note that the Protect attribute cannot be successfully assigned because itcauses pair suspension.

- Access attribute of S-VOL

- Read/Write enabled Read Only Protect

- VRM Enabled Disabled Enabled Disabled Enabled Disabled

Accessattributeof P-VOL

Read/Writeenabled

Enabled

P-VOL/S-VOL Read/Writeenabled



P-VOLRead/Writeenabled,S-VOLRead only

Pairscannot becreated


Disabled







ReadOnly

Enabled

P-VOL/S-VOL Readonly






Disabled

P-VOLRead only,S-VOLRead/Writeenabled

P-VOLRead only,S-VOLRead/Writeenabled





Protect Enabled







Disabled








5TCz configuration

This chapter provides instructions for configuring TrueCopy for Mainframe.

□ Configuration workflow

□ Defining port attributes

□ Adding remote connection

□ Setting number of vols. copied, path blockade, other options

□ Changing SCP time

TCz configuration 5-1Hitachi TrueCopy® for Mainframe User Guide

Configuration workflowYou must have Storage Administrator (Remote Copy) role to perform mostTrueCopy for Mainframe operations using Device Manager - StorageNavigator.

Configuration consists of the following operations:

• Check prerequisites for each procedure.• See Planning pairs and pair volumes on page 3-9.• On the primary and secondary system, install the data paths. See Data

path requirements and configurations on page 3-26.• On primary and secondary system, configure the initiator and RCU target

ports Fibre Channel ports that will be used for TrueCopy for Mainframeoperations. See Ports on page 3-30 and Defining port attributes on page5-2 for details.

• On the primary system, create the TrueCopy for Mainframe associationwith the secondary system. See Adding remote connection on page5-3. Remote paths between the systems are added during this procedure.

You may also perform these additional procedures prior to the initial copy:

• Add additional remote paths. See Configuring additional remote paths onpage 7-15.

• Specify the number of volumes to copy at one time. See Setting numberof vols. copied, path blockade, other options on page 5-6.

In this user guide, explanation is written as prerequisite of pair creation byspecifying primary system volume to P-VOL and secondary system volume toS-VOL. Also Local Storage System written here is the storage system whichconnected with Storage Navigator Client PC and Remote Storage Systemwritten here is the storage system which connected with local storagesystem.

Defining port attributesInitiator and RCU target ports must be set up on the primary and secondarysystem for TrueCopy for Mainframe command and data transfer.

Prerequisite information

• Storage Administrator (System Resource Management) is required.• The number of hosts connected to a target port must be limited to 128 or

fewer to avoid disconnection.• See Ports on page 3-30 for information about target, initiator, and RCU

target ports.• If you are changing a target port to an initiator port, prepare the port for

the change as follows:

¢ Confirm that the port is offline.¢ Disconnect the port from the host.

5-2 TCz configurationHitachi TrueCopy® for Mainframe User Guide

¢ Remove all channel paths to the port.• If you are changing an initiator port to target or RCU target port, prepare

the port for the change as follows:

¢ Release all pairs using the ports.¢ Delete the paths from the initiator port to the secondary storage

system.¢ Delete the secondary storage system from the TCz relationship. See

Deleting TrueCopy for Mainframe on page 7-20.

To define port attributes

1. In the Storage Systems tree, click Ports/Host Groups.2. In the Ports/Host Groups window, click the Ports tab and select the

port to be changed.3. From the Actions menu, click Ports/Host Groups > Edit Ports.4. In the Edit Ports window, select a Port Attribute: Initiator or RCU

Target.

For all other settings, see the Hitachi Virtual Storage Platform G1000Provisioning Guide for Mainframe Systems.

5. Click Finish.6. In the Confirm window, review the settings and enter a task name in the

Task Name box.7. Click Apply to save your settings.

Adding remote connectionYou can configure the storage systems for TrueCopy for Mainframe by addinga remote connection from the primary to the secondary system. Adding theconnection and setting up remote paths prepares the systems for TCzcommands and operations.



• The primary and secondary system must be ready for TCz operations. SeeStorage system preparation on page 3-2.

• The data path must be set up. SeeData path requirements andconfigurations on page 3-26.

• The port attributes on the primary and secondary system must beconfigured for TrueCopy for Mainframe. See Defining port attributes onpage 5-2.

• The secondary system serial number, LDKC, controller ID, and portnumbers are required. The secondary SSID may also be required.

Note: When using CCI (including Raidcom), the VSP G1000 serial numberrequires a prefix of "3".

• One of the fields, Round Trip Time, is covered extensively inDetermining Round Trip Time on page 3-6.

• Another field, Minimum Number of Paths, is also covered in moredetail in Determining Minimum Number of Remote Paths on page 3-8.

• Remote path settings are required to perform TCz pair operations andcheck pair status in Device Manager - Storage Navigator. Make sure tocomplete the procedure. If you cancel remote path settings, you will beunable to perform operations and check status.Also, operations involving remote paths cannot be performed whenchanging the microcode. Make sure a microcode change completes beforebeginning operations involving remote paths.

• With VSP G1000, when using virtual storage machine volumes, make sureto specify the VSP G1000's physical serial number. A virtual storagemachine's serial number cannot be specified.

To configure systems and define remote paths

1. In the primary VSP G1000 Device Manager - Storage Navigator's StorageSystems tree, click Replication > Remote Connection.

2. In the Remote Connections window, click the Connections (To) tab.3. From the Actions menu, click Remote Connections > Add Remote

Connection.4. In the Add Remote Connection window, select the Connection Type.

For TCz, select CU (connects CU by CU).


5. In the Local Storage System box, for Local CU, select the CU numberin a range from 00 to FE.

6. In the Remote Storage System box, specify the following:

a. For Model, select the storage system model and number.b. For Serial Number, enter one of the following secondary system

serial numbers.- VSP G1000: 1 to 99999 (5 digits)- VSP or USP V/VM: 1 to 99999 (5 digits)- HUS VM: 200001 to 265535 (6 digits)

c. For Remote CU, select the secondary system's CU number in a rangefrom 00 to FE.

d. For SSID, select the secondary system's SSID. The range is from0004 to FFFE.If two or more valid SSIDs display, the - button is available. Clickingdeletes the SSID text box.You can add or remove an SSID whenever necessary. The maximumis four.

7. In the Remote Paths box, specify the following:

a. For Minimum Number of Paths, select the minimum number ofpaths between the secondary and primary system. If the number ofpaths drops below the minimum, the primary system splits the pair.The maximum is 8; the default is 1.

b. In the path ports boxes, select the ports used by the remote path.


You can add more remote paths by clicking the Add Path button. SeeConfiguring additional remote paths on page 7-15 for moreinformation.

8. Click Options to access additional settings, which are optional.

a. For RIO MIH Time, enter an interval in seconds that, if exceeded,causes the data-transfer operation to be reported as failed by thesystem. Values range from 10 seconds to 100 seconds; 15 is thedefault. RIO MIH means "remote I/O missing interrupt handler".

b. For Round Trip Time, enter a time limit for data copy from P-VOL toS-VOL. Range is 1-500 milliseconds.

c. For FREEZE Option, Enable or Disable CGROUP (FREEZE/RUN)PPRC TSO command support.- This option enabled also requires the option, PPRC Support by Hoston the Edit Remote Replica Option window, to be enabled. See Settingnumber of vols. copied, path blockade, other options on page 5-6.- Make sure remote paths are added before enabling this option.



Setting number of vols. copied, path blockade, other optionsYou can specify the following options that affect the TCz system. Theseoptions can be set at any time (before or after the initial copy).

• The number of volumes that are copied concurrently during the initialcopy. Find related information in Priority for initial copy operations andscheduling order on page 3-15.

• The amount of time the system monitors for blocked paths.• The amount of time the system monitors for path-watch related SIMs.• Whether SIMs in the secondary system are reported to the host.• Whether sense information compatible with PPRC is created.

To set or change TrueCopy for Mainframe options

1. In the Storage Systems tree, click Replications.2. From the Actions menu, click Remote Replication > Edit Remote

Replica Options.3. In the Edit Remote Replica Options window, for Copy Type, select

TC/TCMF.


4. Change Storage System Options as needed. Settings apply to thestorage system.

a. For Maximum Initial Copy Activities, specify the number ofvolumes to be copied concurrently per initial copy operation. Therange is from 1 to 512 volumes; 64 is the default. Note the following:- This setting may impact performance on the primary system. Thisdepends on the number you specify and the amount of I/O activity.The default may or may not limit the impact on performance,depending on your number of data paths, pairs, and so on. You shouldconsider these factors when making a selection.- When you create or resynchronize a greater number of pairs thanyou specify in Maximum Initial Copy Activities, the system processesthe specified maximum number, and starts additional pairs after oneof the specified number is synchronized.For example, if you specify 70 for Maximum Initial Copy Activities andthen create 75 pairs, the system starts the first 70 pairs but does notstart the 71st pair until one of the pairs is synchronized.

b. For Path Blockade Watch, enter the number of seconds for thesystem to monitor blocked paths. The range is from 2 to 45 seconds;40 is the default.


If all paths become monitored because of path error, an MIH mayoccur in the host. Therefore, the time you specify must be less thanthe host's MIH timer setting.

c. For Path Blockade SIM Watch, enter the number of seconds for thesystem to monitor SIMs reported for blocked paths. The range is from2 to 100 seconds.

d. For Services SIM of Remote Copy, specify whether or not servicesSIMs in the remote CU are reported to the host.

5. Change CU Options as needed. Settings apply to the CU only.

a. For Maximum Initial Copy Activities, select one of the following:- Enable to enable and set or reset the maximum number of initialcopies.- Disable to place no restriction on number of initial copies and relyonly on the Initial Copy Priority setting in the Create Pairs wizard.

b. Select the CU with the options to be changed, then click Change CUOptions. If you do not want to change CU options, click Finish.

c. In the Change CU Options dialog box, for Maximum Initial CopyActivities, specify the number of volumes to be copied concurrentlyper initial copy operation for the CU. The range is from 1 to 16volumes.This option is available only when Maximum Initial Copy Activitiesis Enable.

d. For PPRC support by host, specify whether to create senseinformation having compatibility with IBM PPRC.- When you change the PPRC support option for the P-VOL, the pairsplit/resync operations are unnecessary.- When changing PPRC support option for the S-VOL, change theoption in the primary storage system and then split and resync thepairs.

e. For Services SIM of Remote Copy, specify whether or not servicesSIMs in the remote CU are reported to the host.

f. Click OK.6. In the Edit Remote Replica Options window, click Finish.7. In the Confirm window, review the settings and enter a task name in the


Changing SCP timeSCP (state change pending) time is the interval that I/O from the host issuspended. Because SCP time is shared between TrueCopy for Mainframe andCompatible FlashCopy® V2, make sure to take into account the amount oftime required by both products when setting the value.


To specify or change SCP time

1. In the Storage Systems tree, click Replications.2. From the Actions menu, click Remote Replication > Edit SCP Time.3. In the Edit SCP Time window, select the CU with the SCP time to be

changed, and then click Change SCP Time.

4. In the Change SCP Time window, enter the new SCP time. The range isfrom 0 to 518,400 seconds.

5. Click OK.6. In the Edit SCP Time window, click Finish.7. In the Confirm window, review the settings and enter a task name in the



6TCz pair operations

This chapter provides instructions for performing TrueCopy for Mainframe pairoperations.

□ Pair operations workflow

□ Checking pair status

□ Creating pairs

□ Splitting pairs

□ Resynchronizing pairs

□ Deleting pairs

TCz pair operations 6-1Hitachi TrueCopy® for Mainframe User Guide

Pair operations workflowYou must have Storage Administrator (Remote Copy) role to performTrueCopy for Mainframe operations.

Basic TrueCopy for Mainframe operations consist of the following operations.

• Check prerequisites for each procedure.• Always check pair status. Each TrueCopy for Mainframe operation

requires the pair to be in a specific status.• Create a pair, in which the S-VOL becomes a duplicate of the P-VOL.• Split a pair, which separates the P-VOL and S-VOL and allows read/write

access to the S-VOL if desired.• Resynchronize a pair, in which the S-VOL again mirrors the on-going,

current data in the P-VOL.• Delete a pair.

Disaster recovery procedures are discussed in Chapter 9, Disaster recoveryon page 9-1.

Note: Pair operations cannot be performed when changing the microcode,nor if microcode changes are cancelled. If you start a microcode change,make sure it completes before performing pair operations.

Note: When below status continues during TCz pair duplication, sometimethe TCz pair splits to prioritize refresh I/O rather than TCz pair duplication.

• MP blade processor operation rate which P-VOL belongs is 70% or abovein primary system.

• Refresh I/O inflow for P-VOL is large in primary system.• MP blade write-pending which S-VOL belongs is 65% or above in

secondary system.When creating/resynchronizing TCz pair, execute by keeping in mind of loadfor storage systems at each site.

Checking pair statusEvery TrueCopy for Mainframe operation requires that the pairs have aspecific status. Before performing any operation, check pair status.

• Find status requirements under the prerequisite information for eachoperation.

• To view a pair's current status in the GUI, or review status definitions, seeMonitoring pair status, license capacity on page 7-2.

6-2 TCz pair operationsHitachi TrueCopy® for Mainframe User Guide

Creating pairsWhen you create the initial copy, all data in the P-VOL on the primary systemis copied to the S-VOL on the secondary system. The P-VOL remains availableto the host for I/O operations.


• The initial copy is performed from the primary system.• S-VOLs must be offline to all hosts.• Ports must be configured for TrueCopy for Mainframe. See Defining port

attributes on page 5-2 for more information.• The primary and secondary system must be configured for TrueCopy for

Mainframe. See Adding remote connection on page 5-3 for moreinformation.

• Stop Performance Monitor before the initial copy to avoid overloading withTCP/IP traffic.

• During this operation, you select P-VOLs and S-VOLs by CU and/or LDEVnumbers.

• During this operation, you can specify multiple P-VOLs to be paired, butonly one S-VOL. To plan how the system assigns subsequent S-VOLs, seethe bullet, "When creating multiple pairs concurrently...." in Pair volumerequirements and recommendations on page 3-10.

• During this operation, you can specify whether to fence the P-VOL whenan error occurs. This is discussed in detail in Allowing I/O to the P-VOLafter a split—Fence Level options on page 3-13 .

• During this operation, you can specify the priority for initial copyoperations. When performing more initial copies than specified forMaximum Initial Copy Activities (during configuration), see the discussionin Priority for initial copy operations and scheduling order on page 3-15.

To create initial copies

1. In the Storage Systems tree, click Replications > RemoteReplications, and then select the TC Pairs tab.

2. From the Actions menu, click Remote Replications > Create TC Pairs.3. In the Create TC Pairs window, for Copy Type, select TrueCopy for

Mainframe.


4. For Local CU, select the primary system's CU number (00 to FE).5. For Remote Storage System, select the following:

¢ The secondary system's Model/Serial Number.¢ The secondary system's CU/SSID, if a CU number is selected for

Local CU.6. In the Primary Volume Selection box, volumes that can be used as P-

VOLs display in the Available LDEVs table. No action is required at thistime.

7. In the Secondary Volume Selection box, specify the following:

a. For Base Secondary Volume, select the initial S-VOL's CU numberand LDEV number. If you are selecting only one P-VOL, this LDEV isthe secondary volume. If you select multiple P-VOLs for pairing, thisLDEV is the base S-VOL that is assigned to the first P-VOL and fromwhich subsequent S-VOL LDEVs are assigned to the list of P-VOLs.

Caution: In USP V/VM and VSP, LUN IDs display in hexadecimalnumbers. In VSP G1000, LUN IDs display in decimal or hexadecimalnumbers. If you have selected the decimal notation, when assigningan S-VOL in a USP V/VM or VSP storage system, make sure to convertthe hexadecimal LUN ID number to decimal.

b. For Selection Type, select the method for assigning S-VOLs whenmultiple primary volumes are selected.- With Interval, specify an interval the system skips betweensecondary system LDEV numbers.

c. - With Relative Primary Volume, the system assigns secondarysystem LDEV numbers based on proximity to P-VOL LDEV numbers.


8. Click Options to define the following optional settings:

a. For Primary Volume Fence Level, specify whether the primarysystem allows or rejects write operations to the P-VOL when the pairis split due to an error.- Data: The P-VOL cannot be written to.- Status: The P-VOL can be written to if the primary system canchange S-VOL status to Suspended; otherwise it cannot be written to.- Never: The P-VOL can always be written to.

b. For Initial Copy Type, specify whether to copy data from P-VOL toS-VOL during the operation.- Entire Volume creates the pair and copies data to the S-VOL.(Default)- None creates the pair but data is not copied to the S-VOL. Thisrequires that data in the P-VOL and S-VOL are already identical.

c. For Copy Pace, specify the number of tracks to be copied per remoteI/O during the operation. Options are 3 or 15; 15 is the default. Thisoption affects performance as follows:3 is slow, improves performance and lowers impact to host I/O.15 is fast, may lower performance and increase impact to host I/O.

d. For Initial Copy Priority, specify the scheduling order for the initialcopy operation. The range is 1 to 256; 32 is the default.If a time-out error occurs during this operation, the order specified inInitial Copy Priority may not run as expected. A time-out error canoccur because of the CU configuration or data path error. Review theerror, delete the pair with an error, then retry the operation.

e. For CFW Data, specify whether CFW (DASD fast write) data is copiedto the S-VOL.- Primary Volume Only: CFW data is not copied to the S-VOL.- Secondary Volume Copy: CFW data is copied to the S-VOL.

f. For DFW to Secondary Volume, specify whether the primary systemsplits the pair in the event that the secondary system cannot copyDFW data to the S-VOL.- Require: The pair is split.- Not Require: The pair is not split.The interaction of DFW required and the P-VOL fence level setting cancause a host application to fail with a permanent I/O error whenattempting to update an P-VOL. Keep track of which pairs have theDFW required setting, and make sure that DFW to the S-VOL is notblocked.If a TCz pair is established using PPRC commands, the DFW toSecondary Volume option is set to the DFW not required setting.

g. For Host I/O Time Stamp Transfer, specify whether the host I/Otime stamp is transferred from P-VOL to S-VOL. Enable transfers,Disable does not transfer; Disable is the default.


9. Back again in the Primary Volume Selection box, select the primaryvolume to be copied first and click Add. The volume and pair informationmoves to the Selected Pairs table.In the Selected Pairs table, you can change pair options by selecting itand clicking Change Settings. Remove a pair by selecting it and clickingRemove.



Splitting pairsYou can split a pair, which suspends data copying to the S-VOL.

When a pair is split:

• I/O writes from the host continue to the P-VOL, but stop to the S-VOL.• Any current update copy operation completes to the S-VOL, ensuring data

consistency to the point of the split operation.• Pair status changes to Suspended.• The primary system records the updated tracks to the P-VOL that occur

after the split as differential data. This data is copied to the S-VOL whenthe pair is resynchronized.

• You can set an option to block updates to the P-VOL while the pair is split.This results in the P-VOL and S-VOL staying synchronized.

• Another option is to enable system write to the S-VOL from a host. Thesecondary system records the updated tracks as differential bitmaps.When the pair is resynchronized, the secondary system sends thedifferential bitmaps to the primary system, which merges all differentialbitmaps to determine which tracks are out-of-sync.


• Pair status must be Pending Duplex or Duplex.

To split one or more pairs

1. In the Storage Systems tree, click Replications > RemoteReplications.

2. In the Remote Replications window, click the TC Pairs tab, then selectthe pair to be split.

3. From the Actions menu, click Remote Replications > Split Pairs.4. In the Split Pairs window, ensure that the pair to be split appears in the

Selected Pairs table.


5. For Primary Volume Write, specify whether writing to the P-VOL isenabled while the pair is split.

¢ Depend on Primary Volume Fence Level: Writing to the P-VOL isbased on fence level specified during the Create Pairs operation. Thisis the default.

¢ Disable: Write I/Os to the P-VOL are rejected regardless of the fencelevel. Select this option to maintain synchronization of the P-VOL andS-VOL. Do not select this option if the P-VOL is necessary for hostsystem operations.Disable is only available when performing the split operation from thepair's primary storage system.

6. For SSB Transfer (F/M=FB), specify Enable to report SSB (sense byte)to the host, or Disable to not report (default).Enable is only available when performing the split operation from thepair's primary storage system.When SSB Transfer (F/M=FB) is enabled and PPRC Support By Host = Yes(Change CU Options window), the primary system reports the SSB to theall connected hosts ("F/M" means, "Format/Message"). This option mustalways be enabled.If PPRC Support By Host = No, the x'FB' sense information will bereported to the host, even if the SSB (F/M=FB) suspend option isenabled.



Resynchronizing pairsWhile a TrueCopy for Mainframe pair is split, the primary system does notperform update copy operations to the S-VOL. Resynchronizing the pair


updates the S-VOL with differential data accumulated since the split, so thatits data is again identical with the P-VOL's data. Update copy operationsbegin again to the S-VOL.


• Pair status must be Suspended.• This operation is performed from the primary system only.

To resynchronize one or more pairs


2. In the Remote Replications window, click the TC Pairs tab, then selectthe pair to be resynchronized.

3. From the Actions menu, click Remote Replications > Resync Pairs.4. In the Resync Pairs window, ensure that the pair to be resynchronized

appears in the Selected Pairs table.

5. For Primary Volume Fence Level, specify whether the primary systemrejects write operations to the P-VOL when the pair is split due to anerror.

¢ - Status: The P-VOL cannot be written to only if the primary systemis not able to change S-VOL status to Suspended.

¢ - Never: The P-VOL can always be written to.¢ - Data: The P-VOL cannot be written to.For more information, see Allowing I/O to the P-VOL after a split—FenceLevel options on page 3-13 .

6. For Copy Pace, specify the number of tracks to be copied during theinitial copy. Options are 3 or 15to ; 15 is the default. This option affectsperformance as follows:3 is slow, improves performance and lowers impact to host I/O.15 is fast, may lower performance and increase impact to host I/O.


7. For Copy Priority, enter the priority, or scheduling order, for the resyncoperation. You can set priority from 0 to 256. The default is 32. For moreon priority, see the descriptions in Priority for initial copy operations andscheduling order on page 3-15.

8. For Host I/O Time Stamp Transfer, specify whether the host I/O timestamp is transferred from P-VOL to S-VOL. Enable transfers, Disabledoes not transfer; Disable is the default.



Deleting pairsA TrueCopy for Mainframe pair can be deleted. Doing this deletes the TCzrelationship, though not the volumes or their data.

• When it is no longer necessary to maintain a remote copy of the P-VOL,delete a pair from the primary system only. All update operations arestopped and pair status for both the P-VOL and S-VOL changes tounpaired.When a pair is deleted, the primary system continues to accept write I/Oto the former P-VOL but does not keep track of the updates.

• Delete a pair from the secondary system only for disaster recoverypurposes. When you do this, the secondary system changes the S-VOLpair status to unpaired, the primary system detects that the S-VOL statusis unpaired, and then changes P-VOL status to Suspend-delete pair toRCU.The CDELPAIR TSO command can be used to delete pairs from theprimary system.To restart a pair that was deleted from the secondary system, you mustdelete the pair from the primary system, then create the pair from theprimary system.

Note: When you delete a pair from the secondary system, make sure thatthe S-VOL and P-VOL are identical, including the volume labels. Take allnecessary steps to prevent system problems due to duplicate volumes.

To delete pairs


2. In the Remote Replications window, click the TC Pairs tab, then selectthe pair or pairs to be deleted.

3. From the Actions menu, click Remote Replications > Delete Pairs.4. In the Delete Pairs window, ensure that the pairs to be deleted appear

in the Selected Pairs table.


5. For Delete Mode, specify one of the following:

¢ Normal: Deletes the pair only if the primary system can change bothP-VOL and S-VOL to unpaired volumes.

¢ Force: Forcibly deletes pairs even when the primary system cannotcommunicate with the secondary system. Force allows host operationsto continue.

¢ Force (All pairs in the same remote connections): Deletesforcibly all pairs using the same remote connection.




7Monitoring and maintaining the TCz

system

This chapter provides information and instructions for monitoring andmaintaining a TrueCopy for Mainframe system.

□ Monitoring pair status, license capacity

□ Monitoring TCz pair synchronous rate

□ Monitoring TCz operations history

□ Changing P-VOL Fence Level, CFW Data

□ Forcibly deleting pairs

□ Saving pair information to a text file

□ Monitoring and maintaining remote connections and paths

□ Adding, removing SSIDs on the secondary system

□ Deleting TrueCopy for Mainframe

□ ICKDSF Considerations for TCz Volumes

□ Managing power-off for systems and network devices

□ ICKDSF media maintenance

Monitoring and maintaining the TCz system 7-1Hitachi TrueCopy® for Mainframe User Guide

Monitoring pair status, license capacityMonitoring the TrueCopy for Mainframe system is an ongoing operation thatshould be performed frequently to keep track of and maintain your pairs.

• When you want to perform a pair operation, first check the pair's status.Each operation requires a specific status or set of statuses.

• Pair status changes when an operation is performed. Check status to seethat pairs are operating correctly and that data is updated from P-VOLs toS-VOLs in Duplex status, or that differential data management isperformed in Split status.

Monitoring using the GUI is done manually. Monitoring should be repeatedfrequently. Email notifications of problems can be set up using the GUI.

To monitor pair status, license capacity


2. In the Remote Replications window, click the TC Pairs tab, then locatethe pair volume with the status you want to review.

3. From the Actions menu, click Remote Replication > View PairProperties and review Status.

7-2 Monitoring and maintaining the TCz systemHitachi TrueCopy® for Mainframe User Guide

For more information, see Pair status definitions on page 7-3.

To monitor license capacity

1. See the Summary area in the Replications window.

How pair status changesThe primary system changes and maintains the status of the P-VOL and isresponsible for keeping the P-VOL and its S-VOL synchronized. The secondarysystem maintains the status of the S-VOL.

• The primary system can change the status of the P-VOL and S-VOL.• The secondary system can change the status of the S-VOL but not the P-

VOL. When an operation is performed from the secondary system, theprimary system detects a status change in the S-VOL and then changesP-VOL status accordingly.

• The status indicates the state of the volume or pair:

¢ When a pair is started, the secondary system changes the status ofthe P-VOL and S-VOL to Pending Duplex. When the initial copyoperation is complete, the primary system changes the status of bothvolumes to Duplex.

¢ When you split a pair, the system changes the status of the P-VOLand S-VOL to Suspended.

¢ When a pair is suspended due to an error condition, the primary/secondary system changes the P-VOL and S-VOL status toSuspended.

¢ When a pair is deleted from the primary system, that system changesthe status of the P-VOL and S-VOL to unpaired.

¢ When a pair is deleted from the secondary system, that systemchanges the S-VOL status to unpaired, and the secondary systemdetects the pair release and changes the P-VOL status to Suspended.

Pair status definitionsBoth Device Manager - Storage Navigator and Business Continuity Managerpair status names appear in the Status column, except when the names arethe same. When they are the same, the Business Continuity Manager (BCM)status does not appear.

The following table shows both types of status names and their descriptions.In some cases, a particular status has no exact parallel status in the otherinterface. This is noted.

When checking your pairs' status, click Refresh to make sure the data iscurrent. The P-VOL access and S-VOL access columns in the following tableindicate whether the volumes accept read/write.

(For CCI status names, see CCI pair status names on page 7-5.)


HDvM - SNstatus BCM status Description P-VOL

accessS-VOLaccess

Unpaired inHDvM - SN

SIMPLEX This volume is not currently assigned to aTrueCopy for Mainframe pair.

Read/Write Read/Write

PendingDuplex1

PENDING (01) The initial copy operation for this pair is inprogress. This pair is not yet synchronized.

Read/Write No

Duplex DUPLEX (02) • The pair is synchronized• Updates from the host to the P-VOL are

duplicated in the S-VOL.

Read/Write No

Suspended(See alsoSplit typeson page7-5.)

SUSPOP (03),SUSPOP (04),SWAPPING(04), SUSPOP(05), SUSPER(07), SUSPOP(0A)

• The pair was split by a user. The pair isnot synchronized.

• When you split the pair from the primarysystem, that system changes the statusof the P-VOL and S-VOL to Suspended.

• In Suspended status, updates to the S-VOL stop. The storage system keepstrack of updates to the P-VOL in order toupdate the S-VOL when the pair isresynchronized.

• When you split the pair from thesecondary system, that system changesthe status of the S-VOL to Suspended.The primary system detects this andchanges P-VOL status to Suspended.

• When you release the pair from thesecondary system, that system changesthe S-VOL status to Simplex. Theprimary system detects this and changesthe P-VOL status to Suspended. The pairmust be released from the primarysystem in order to change P-VOL statusto Simplex.

BCM split statuses initiated by the user:• SUSPOP (O3): The user split the pair

from the P-VOL.• SUSPOP (04): The user split the pair

from the S-VOL. If the P-VOL is updated,it is recorded as differential data.

• SWAPPING (04): The user split the pairin the reverse direction (S-VOL to P-VOL).

• SUSPOP (05): The secondary systemreceived a split request from the primarysystem and split the pair.

• SUSPER (07): The user deleted the pairfrom the secondary system. The primarysystem detected this and split the P-VOL.

• SUSPOP (0A): The pair was split becausethe user issued PPRC's FREEZE commandon the primary system.

Read/Write Read Only ifMode=20 isON,otherwiseNo.


HDvM - SNstatus BCM status Description P-VOL

accessS-VOLaccess

Suspended(See alsoSplit typeson page7-5.)

SUSPCU (06)(by error),SUSPCU (08),SUSPER (09),SUSPER (50)

• If the primary system cannot keep thepair synchronized for any reason, itchanges the status of the P-VOL and S-VOL (if possible) to Suspended.

• The pair is not synchronized.BCM also includes the following:• SUSPCU (08): The pair was split when

the primary system detected an errorduring the communication with thesecondary system, or detected an I/Oerror during update copy.

• SUSPER (09): The pair was split becausethe primary system detectedvolatilization of pair control informationon memory when power was ON (IMPL).This error occurs when power-off statusof the primary system continues beyondthe backup time for the nonvolatilememory.

• SUSPER (50): The pair was split becausedata mismatch between P-VOL and S-VOL was detected during the initial copyoperation. The cause of the error isinvalid track format.

Read/Write.Read only ifPrimaryVolumeFence Levelis Data.

Read Only ifMode=20 isON,otherwiseNo.

1 When pair status is Pending, neither cache nor shared memory can be added to or removed from thestorage system. When either of these tasks is to be performed, first split any pairs in Pending, status,then resynchronize when the cache or shared memory operation is completed.

CCI pair status names

CCI pair status names are different than Device Manager - Storage Navigatorstatus names. The following shows the corresponding names.

Device Manager - Storage Navigatorpair status name CCI pair status name

Unpaired SMPL

Pending COPY

Duplex PAIR

Suspended (by operation) PSUS

Suspended (by error) PSUE

Split types

This topic discusses pairs that are split by user operation (Suspended-deletepair to RCU), and pairs that are suspended by the system because of failure(Suspended).


• You can split a pair when the initial copy operation is complete.

¢ You must split a pair to perform ICKDSF maintenance on the P-VOL orto access the volume which Secondary Volume write option isenabled. TrueCopy for Mainframe pairs are also split when theCGROUP FREEZE command is processed.

¢ When you split a pair, the primary system ensures synchronization bycompleting any pending update copy operation according to the userspecified drain/purge suspend option before changing the status toSuspended.

• Pairs are split by the primary system only, for any of the followingreasons:

¢ You released the pair from the secondary system.¢ An error condition related to the secondary system, the S-VOL, or an

update-copy operation.¢ When the secondary system cannot run DFW (DASD fast write) to

Secondary Volume (only when Required is selected for DFW toSecondary Volume option).

¢ The primary system cannot communicate with the secondary system.

Split types appear in the Status field on the View Pair Properties window. Thefollowing table describes the split types. (CCI does not display split types.)

Split type Volumeapplies

toDescription

HDvM - SN BCM PPRC

PrimaryVolume byOperator

SUSPOP(03) SUSPEND(03) P-VOL The user operated the pair split from theprimary system by selecting Disable forthe Primary Volume Write field. The S-VOL split type is, "by Local StorageSystem".

SecondaryVolume byOperator

SUSPOP(04)SWAPPING(04)

SUSPEND(04) P-VOLS-VOL

The user operated the pair split from theprimary or secondary system byselecting Disable for the Primary VolumeWrite field.

by LocalStorageSystem

SUSPOP(05) SUSPEND(05) S-VOL The secondary system received arequest from the primary system to splitthe pair. The P-VOL split typeis Suspended-Primary Volume byOperator or Suspended-SecondaryVolume by Operator.

by RemoteStorageSystem

SUSPCU(06) SUSPEND(06) P-VOL The primary system detected an errorcondition at the secondary system(RCU), that caused the primary systemto split the pair. The S-VOL split type isS-VOL Failure.

Delete pair toRCU

SUSPER(07) SUSPEND(07) P-VOL The primary system detected that the S-VOL status changed to Simplex becausethe user released the pair from the


Split type Volumeapplies

toDescription

HDvM - SN BCM PPRC

secondary system. The pair cannot beresynchronized because the S-VOL doesnot have the Suspend status.

S-VOL failure SUSPCU(08) SUSPEND(08) P-VOL The primary system detected an errorduring communication with thesecondary system, or an error duringupdate copy. In this case, the S-VOLsplit type is usually S-VOL Failure. Thissplit type is also used when the numberof paths falls below the minimumnumber of paths setting on the AddRemote Connection window.

MCU IMPL SUSPER(09) SUSPEND(09) P-VOLS-VOL

The primary system could not find validcontrol information in its nonvolatilememory during IMPL. This conditionoccurs only if the primary system iswithout power for more than 48 hours(that is, power failure and fullydischarged backup batteries).

by FREEZE SUSPOP(0A) SUSPEND(0A) P-VOLS-VOL

The pair was split by the CGROUP/FREEZE TSO command.

Initial copyfailed

SUSPER(50) SUSPEND(08) P-VOLS-VOL

The pair was split before the initial copyoperation was complete. The data on theS-VOL is not identical to the data on theP-VOL.

System behavior

Note the following behaviors for split pairs:

• The primary system stops performing update operations to the S-VOL. Itmay or may not continue accepting write I/Os to the P-VOL depending onthe P-VOL fence level setting and split option.

• If an update fails, the primary system reports a unit check and notifiesthe host that Write fails. This ensures that both the host system andapplication program regard the write operation to the P-VOL as failed.

• If the primary system accepts subsequent write I/Os for a split P-VOL, thesystem records the updated data in the P-VOL tracks as differential data.When a split pair is resynchronized, the primary system copies the out ofsync P-VOL tracks to the S-VOL as differential data.

• TCz does not allow access to an S-VOL while the pair is split (whenmode20=ON, Read access is accepted).

• When a pair is split, whether user requested or due to failure, the primarysystem generates sense information to notify the hosts. If the hostsystem supports IBM PPRC (and the "PPRC support by host" CU option isenabled), this notification results in an IEA494I and/or IEA491E systemconsole message, which indicates the reason for suspension.


Monitoring TCz pair synchronous rateYou can check on the percentage of synchronized data between the P-VOLand S-VOL.

To check a pair's synchronous rate

1. In the Storage Systems tree, click Replication > Remote Replication.2. Click the TC Pairs tab, then select the pair whose rate you want to

display.3. Click Actions > Remote Replications > View Pair Synchronous

Rate.

Clicking Refresh displays the latest synchronous rate.

Monitoring TCz operations historyYou can review a pair's history of operations, including the operation'sdescription, date and time it took place, primary and secondary systeminformation, and other details.

To view a pair's operation history

1. In the Storage Systems tree, click Replication.2. Click View Histories > Remote Replication.3. In the Histories window, for Copy Type, click TCMF.


4. The Description column displays operations. They are explained below.

Note the following when viewing histories.

• Operation rows may not appear in descending, chronological order.• The most recent operations display, up to a maximum of 524,288

operations. Information older than seven days is not shown.• If a failed split occurred with two or more LDEVs at the same time, the

number of pairs showing Pair Suspend (Failure) may not match the actualnumber of pairs in which the failure occurs.

• If you enabled the reporting of Services SIM of Remote Copy (Change CUOption window), note that the history is not updated until SIMs arereported to the host. If a SIM is cleared before it is reported to the host,the history of it is deleted.

Operation descriptionsThe following table describes the operations shown in the Histories window.

Operation Displayed Description

Pair Add Start Creation of the pair started.

Pair Add Complete Creation of the pair completed.

Pair Delete The pair was deleted.

Pair Suspend (Operation) The pair was split.

Pair Suspend (Failure) The pair was split (suspended) because of afailure.

Pair Resync. start Resynchronization of the pair was started.


Operation Displayed Description

Pair Resync. Complete Resynchronization of the pair was completed.

Changing P-VOL Fence Level, CFW DataYou can change the P-VOL's fence level, which specifies when to reject writeoperations to the P-VOL under certain failure circumstances. You can alsochange whether CFW (DASD fast write) data is copied to the S-VOL or not.

For more information on fence levels, see Allowing I/O to the P-VOL after asplit—Fence Level options on page 3-13.


• Pair status must be Pending Duplex or Duplex.• The Edit Pair Options window is used for the following procedure. If you

select multiple pairs, the values do not display but are blank. When youchange a value, the change applies to all selected pairs

To change the fence level and CFW data options


2. Click the TC Pairs tab, then select the pair whose options are to bechanged.

3. From the Actions menu, click Remote Replications > Edit PairOptions.

4. In the Edit Pair Options window, for Primary Volume Fence Levelbox, select the fence level for the pairs.- Never: The P-VOL can always be written to.- Data: The P-VOL cannot be written to.- Status: The P-VOL cannot be written to only if the primary system isnot able to change S-VOL status to Suspended.


5. For CFW Data, select whether CFW data is copied to the S-VOL.

¢ - Primary Volume Only: CFW data is not copied to the S-VOL.¢ - Secondary Volume Copy: CFW data is copied to the S-VOL.


Task Name box.8. Click Apply to save your settings in the system.

Forcibly deleting pairsYou forcibly delete a pair for the following reasons:

• A currently unpaired volume that was previously in a pair is unusablebecause previous pair information is still in the volume.

• The pair cannot be connected to the secondary system because of acommunication error. In this case, delete the pair forcibly in both primaryand the secondary systems.


• The volume must be unpaired.

To forcibly delete a pair

1. In the Storage Systems tree, click Logical Device.2. Click the LDEV tab, then select the pair to be forcibly deleted.3. From the Actions menu, select Remote Replications > Force Delete

Pairs (TC Pairs).4. In the Force Delete Pairs (TC Pairs) window, ensure that the volume is

in the Selected LDEV table.


5. Click Apply.

Saving pair information to a text file You can save pair status and other information to a tab-delimited TSV file.

To save pair information

1. In the Remote Replication window, click More Actions > Export.2. If necessary, follow instructions in online Help.

Monitoring and maintaining remote connections and paths To view remote connection status and path information

1. View connection properties and path information by clicking Actions >Remote Connection > View Remote Connection Properties.


2. To check path and port information, from the Storage Systems tree, clickReplication > Remote Connections > Connections (To).Check connections under View Port Condition.

Check Status and other details in the Connections (To) tab.


Remote path status definitionsThe following table provides remote path status descriptions.

Status Definition

Normal This path has been successfully established and can be used forTrueCopy for Mainframe remote copy activities.

InitializationFailed

The link initialization procedure with the secondary system hasfailed, because the physical path connection between either theprimary and secondary system, or between the primary system andthe host, was missing.

CommunicationTimeout

A timeout error has occurred between the primary and secondarysystem.

Path Rejected The remote path link function has been rejected by the secondarysystem. All remote path resources in the secondary system might beused for other connections.

Serial NumberMismatch

The serial number of the control unit that is connected to this remotepath does not match the serial number specified by the Add RemoteConnection window.

Invalid Port Mode The specified port does not have the initiator attribute.

RCU Port NumberMismatch

There are three possible causes:• The specified port in the secondary system is physically

disconnected from the primary system.• The port is not configured as an RCU target port.• The specified port number is not available.

RCU Port TypeMismatch

The microcode on the remote side does not support the fibre remotecopy function; or the specified port type is not RCU target.

CommunicationFailed

A timeout error has occurred on the path between the primary andsecondary system.

Logical Blockade This remote path was blockaded because a path error or a link erroroccurred continuously.

Program Error This remote path was blockaded because a program error occurred.

In Progress This remote path is in progress of changing the attribute of port.


Configuring additional remote pathsYou can configure additional remote paths as needed. A maximum of eightremote paths are supported.


• Review the path-related prerequisites in Adding remote connection onpage 5-3.

To configure additional remote paths

1. In the primary VSP G1000 Storage Systems tree, click Replications >Remote Connections.

2. In the Remote Connections window, click the Connections (To) tab.3. In the Connections (To) tab, select the remote connection where the

remote path is to be added.4. From the Actions menu, click Remote Connections > Add Remote

Paths.5. In the Add Remote Paths window, add a new remote path by selecting

ports for the primary (left side) and secondary systems. You can makemultiple selections. To add paths, click Add Path.




Changing minimum paths, round trip time, other remote connectionoptions

You can change remote connection options that affect how the system runs your copy operations. These are:

• Number of minimum paths for a pair. You can find detailed information inDetermining Minimum Number of Remote Paths on page 3-8

• The interval for data transfer to complete (RIO MIH Time).• FREEZE option, which defines support for the CGROUP (FREEZE/ RUN)

PPRC TSO command.• Round trip time, the time limit for copying data to the S-VOL. For more

information, see Determining Round Trip Time on page 3-6 for moreinformation.

To change remote connection options

1. In the Storage Systems tree, click Replications > RemoteConnections.

2. Click the Connections (To) tab, then select the remote connectionwhose options you want to change.

3. From the Actions menu, click Remote Connections > Edit RemoteConnection Options.

4. In the Edit Remote Connection Options window, for MinimumNumber of Paths, select the minimum number of paths between thesecondary and primary system.

5. For RIO MIH Time, enter an interval in seconds that, if exceeded, causesthe data-transfer operation to be reported as failed by the system. Therange is from 10 to 100 seconds; 15 is the default.

6. For Round Trip Time, enter a time limit for data copy from P-VOL to S-VOL. Range is 1-500 milliseconds.


7. For FREEZE Option, Enable or Disable CGROUP (FREEZE/RUN) PPRCTSO command support.- PPRC support by the host must be enabled to use this option.- Make sure remote paths are added before enabling this option.



Deleting remote pathsYou can delete a remote path between a primary system and secondarysystem.


• Delete remote paths from the primary system.• Make sure that the remaining number of paths is equal to or greater than

the minimum number of paths setting on the Add Remote Connectionwindow, otherwise the delete path operation will fail.

To delete a remote path


2. In the Remote Connections window, click the Connections (To) tab.3. In the Connections (To) tab, select the remote connection with the path

to be deleted.4. From the Actions menu, click Remote Connections > Remove

Remote Paths.5. In the Remove Remote Paths window, click Remove for the remote

paths to be removed. Note that remote paths become unselectable whenthe minimum number of paths is reached.




Adding, removing SSIDs on the secondary systemWhen new LDEVs are added to the secondary system, you make themavailable for TCz operations by adding the associated SSIDs.

When an LDEV is deleted from the secondary system, delete the associatedSSID from the system to avoid mis-operation.


• You can add four SSIDs to each secondary system.• Before adding an SSID, make sure that the remote path is properly

installed.• SSIDs cannot be added when the remote connection is added by System.• Before deleting an SSID, make sure that the remaining SSIDs are still

valid, otherwise the remote paths will be lost.

To add SSIDs


2. In the Remote Connections window, click the Connections (To) tab.


3. In the Connections (To) tab, select the remote connection where youwant to add an SSID.

4. From the Actions menu, click Remote Connections > Add SSIDs.5. In the Add SSIDs window, for SSID, enter the SSID. The range of values

is from 0004 to FFFE.

6. Click Add SSID. You can add up to four SSIDs.7. Click Finish.8. In the Confirm window, review the settings and enter a task name in the


To remove SSIDs


2. In the Remote Connections window, click the Connections (To) tab.3. In the Connections (To) tab, select the remote connection where you

want to delete an SSID.


4. From the Actions menu, click Remote Connections > Remove SSIDs.5. In the Remove SSIDs window, locate the SSID to be deleted and click

Remove.6. Click Finish.7. In the Confirm window, review the settings and enter a task name in the


Deleting TrueCopy for MainframeYou can delete the TrueCopy for Mainframe relationship between the primaryand secondary systems. This is done by deleting remote connections.


• All TCz pairs must be deleted before removing the connection.• When the remote connection is deleted, all remote paths are deleted.• Deleting the TCz relationship with a specific secondary system does not

affect TCz operations between other primary systems and the secondarysystem.

• After a secondary system is deleted, you can reconfigure the remote pathto then connect another secondary system to the primary system. Youcan also delete the remote connection and reconfigure the primarysystem ports (initiator ports to ordinary target ports for fibre) to provideadditional host channels for the primary system.


To delete the TrueCopy for Mainframe relationship


2. In the Remote Connections window, click the Connections (To) tab.3. In the Connections (To) tab, select the remote connection to be

deleted.4. From the Actions menu, click Remote Connections > Remove

Remote Connection.5. In the Remove Remote Connection window, from the Selected

Remote Connection table, select the connection to be removed.

(You can review information about the connection by clicking Detail.)6. Click Apply.

ICKDSF Considerations for TCz VolumesThe VSP G1000 supports the use of the ICKDSF utility program. ICKDSFperforms functions for the installation, use, and maintenance of DASD andservice functions, error detection, and media maintenance. For furtherinformation about ICKDSF, see the IBM document, ICKDSF R16 RefreshUser's Guide (GC35 0033), or other IBM documents on ICKDSF R16 or later.See the Mainframe Host Attachment and Operations Guide (MK 96RD645) forfurther information about using ICKDSF with the VSP G1000.

ICKDSF on a TCz P-VOLICKDSF activities involve write I/O operations with device supportauthorization instead of normal authorization. Because the primary systemdoes not duplicate write I/O operations with device support authorization atthe S-VOL, you must split a pair before running ICKDSF on the P-VOL.

To perform ICKDSF on a P-VOL:

1. Split the pair from the primary system, using the S-VOL split option. Youcan also use the CSUSPEND TSO command.


2. After the P-VOL status changes to secondary volume by operator, runICKDSF to repair the P-VOL.

3. When volume repairs are complete, resynchronize the TCz pair. You canalso use the CESTPAIR (MODE=RESYNC) command to resynchronize thepair.

ICKDSF on a TCz S-VOLIf you need to run ICKDSF on an S-VOL, you must change the status of theS-VOL to unpaired to allow write access. The pair must then be restartedusing the appropriate initial copy options.

To perform ICKDSF on an S-VOL:

1. You can stop write I/Os to the P-VOL while the S-VOL is being repaired.To do this, split the pair from the primary system, specifying Disable forthe Primary Volume Write option. You can also use the CSUSPEND TSOcommand.

2. In the secondary system's Remote Replication window, select the S-VOL to be repaired, and then delete the pair. You can also use theCRECOVER command.

3. If necessary, change the S-VOL VOLSER to avoid problems due toduplicate VOLSERs.

4. Vary the S-VOL online, and run ICKDSF to repair the S-VOL. When thevolume repairs are complete, vary the S-VOL offline.

5. In the primary system's Remote Replication window, select the P-VOL,and then delete the pair.

6. Recreate the pair with the Create Pairs wizard. Specify Entire Volumefor Initial Copy Type. This will resynchronize the P-VOL and S-VOL. (Youcan specify None if the P-VOL and S-VOL are still identical.)You can also use the CESTPAIR TSO command to recreate the pair.

Managing power-off for systems and network devicesThough you are responsible for controlling power-off activities, it is advisableto check with your Hitachi Data Systems Support Center.

The following topics provide information for planned outages when TrueCopyfor Mainframe is present.

General informationPlease review the following system behaviors regarding powering off:

• TCz pairs are not affected when power is removed from a primary systemwhile operations are in progress.

• When power is restored on the primary system, the systemcommunicates with the secondary systems to confirm S-VOL pair


status(es). Make sure that TCz communications are fully restored (allpaths have normal status) before beginning I/O operations to the P-VOL.If primary system accepts an I/O for a P-VOL when path status is notnormal, primary system will split the pair. P-VOL status will change toSuspended-by RCU but primary system cannot change pair status of theS-VOL.

• If power is removed from a secondary system or from a data pathcomponent while TCz operations are in progress, the primary systemdetects the communication failure, splits all affected pairs, and generatesSIMs reporting the failures. The primary system changes the P-VOL statusto Suspend-by RCU but cannot change the status of the S-VOLs.

• If a primary or secondary system is powered off and the backup batteriesare fully discharged while pairs are split, differential data is retained toSSD. In this unlikely case, primary system copies differential data tosecondary system when the pairs are resynchronized.

Planned outage of the primary systemA planned outage of the primary system does not affect TrueCopy forMainframe.

Planned outage of the secondary system or remote pathYou must split the pairs in a secondary system prior to a planned outage ofthe system or to a data path component (for example, switch, channelextender).

To perform a planned outage of a secondary system or data pathcomponent

1. Identify the P-VOLs that are paired with S-VOL in the secondary systemthat is to be powered off.For data path outage, identify all P-VOLs in the primary system that usethe path or component to be powered off.You need to know the primary system, CU, and LDEV ID for each of theP-VOLs.

2. Connect to each primary system that contains affected P-VOLs, and splitall affected pairs. Confirm the changed pair status.

3. Perform the planned outage of the secondary system or data path.4. When the secondary system is fully powered on and ready, resynchronize

the affected pairs at each primary system. Confirm the pair statuschanges.

Planned outage of both primary and secondary systemsWhen you plan an outage of a TrueCopy for Mainframe primary andsecondary systems at the same time, the primary system must be poweredoff first, and then powered on last.


To perform a planned outage of primary and secondary system

1. Perform the planned outage of the primary system first. Because aplanned outage does not affect pairs, nothing out of the ordinary must bedone regarding the TCz system or operations. Do not power on theprimary system at this time.

2. If a secondary system to be powered off is connected to a primary systemthat is not powered off, split the pairs before powering off the secondarysystem. Confirm that the pair status changes.

3. Perform the planned outage of the secondary systems as described inPlanned outage of the secondary system or remote path on page 7-23.

4. Power on the secondary systems. Make sure that they are fullyoperational and ready to resynchronize operations before powering on theprimary system.

5. Power on the primary system, and make sure it is ready to resynchronizeoperations. If you split any pairs in step 2, you can also resynchronizethose pairs now.

ICKDSF media maintenanceThe write operation with a normal permission to the P-VOL will be copied tothe S-VOL of the TrueCopy for Mainframe pair. The write operation with adiagnostic or device support permission (ICKDSF for example) completes inthe P-VOL but does not be copied to the S-VOL. Therefore, you must split theTrueCopy for Mainframe pair before you perform the ICKDSF mediamaintenance.


8Data migration

This chapter discusses using TrueCopy for Mainframe to migrate data fromone storage system to another.

□ Migration overview

Data migration 8-1Hitachi TrueCopy® for Mainframe User Guide

Migration overviewTrueCopy for Mainframe can be used to move data from one system toanother. Data is typically migrated for the following reasons:

• To copy data to a new volume• To temporarily move data from an LDEV to accommodate other activities

(for example, to make repairs)• To relocate LDEVs in order to balance workloads and distribute I/O

activity evenly within or across storage systems

You do not need to use host migration software is unnecessary for datamigration when using TrueCopy for Mainframe. Also, TrueCopy for Mainframedata migration does not affect the host.

TrueCopy for Mainframe operations within one VSP G1000 can only beperformed if the ShadowImage for Mainframe option is not active on thestorage system. If you are migrating data between storage systems using P/DAS, both storage systems must be the same type (VSP G1000).

In a data migration, the entire contents of a volume are copied to thesecondary volume (P-VOL to S-VOL). The volumes are identical when thecopy operation completes. The volumes are then usually released from theTrueCopy for Mainframe pair.

If you need to migrate data from other vendors' storage systems to a VSPG1000 system, contact your Hitachi Data Systems Support Center.

Migrating data1. Make sure that the data path is installed, and TrueCopy for Mainframe

configuration procedures are completed. See Chapter 5, TCz configurationon page 5-1 for details.

2. Vary the target volume (S-VOL) offline from all attached hosts. Thesource volume (P-VOL) can remain online.

3. In Device Manager - Storage Navigator, connect to the storage systemwhere the volume to be migrated is located. Create the TrueCopy forMainframe pair or pairs. See Creating pairs on page 6-3 as needed.When pair status changes to Duplex, the operation is completed. You canmonitor the progress of the operation from the Remote Replicationwindow.

4. Use the IBM P/DAS host software function to redirect all application I/Osto the S-VOLs non disruptively. If the host system does not support P/DAS, use the following procedure to stop using the P-VOLs and switch tothe S-VOLs:

a. Quiesce all applications using the P-VOLs.b. When all update activity to the P-VOLs has stopped, connect to the

primary system, select the correct CU, and release the TCz pairs.c. If the P-VOLs and S-VOLs are attached to the same host, vary the P-

VOLs offline first, and then vary the S-VOLs online. The P-VOLs and S-

8-2 Data migrationHitachi TrueCopy® for Mainframe User Guide

VOLs have the same VOLSERs and cannot be online to the same hostsat the same time.

d. If an S-VOL contains more cylinders than its P-VOL, update the S-VOLvolume table of contents (VTOC) using ICKDSF/REFORMAT.

e. If you want to keep the volumes synchronized, establish the same TCzpairs in the reverse direction by setting None for initial copy type inthe Create TC Pairs window. If the original P-VOLs will be temporarilyunavailable for update copy operations, you can suspend the newpairs so that the new primary system keeps track of changes.

f. Start the applications with the S-VOLs. When the original P-VOLsbecome available, you can resynchronize the pairs.

If the original P-VOL is temporarily unavailable for update copy operations,split the new pair so that the new primary system keeps track of changes.

CFW data is not migrated when you specify Primary Volume Only for the CFWData option in the Edit Pair Options window. Note that there is a possibilitythat I/O will terminate abnormally if you access the corresponding data setwhen you use the S-VOL after migrating data.

Data migration 8-3Hitachi TrueCopy® for Mainframe User Guide

8-4 Data migrationHitachi TrueCopy® for Mainframe User Guide

9Disaster recovery

This chapter discusses disaster recovery.

□ Disaster recovery overview

□ Switching operations to the secondary site

□ Transferring operations back to the primary site

Disaster recovery 9-1Hitachi TrueCopy® for Mainframe User Guide

Disaster recovery overviewPreparing for disaster recovery involves the following major steps:

1. Identify the volumes and groups that contain important files and data fordisaster recovery.

2. Create TrueCopy for Mainframe pairs, paying special attention to theoptions in P-VOL Fence Level Settings to ensure that the system respondsthe way you want in the event of a failure (see Allowing I/O to the P-VOLafter a split—Fence Level options on page 3-13 ).

3. Install and configure host failover software between the primary andsecondary sites.

4. Establish file and database recovery procedures. These procedures forrecovering volumes due to control unit failure must already be in place.

5. Make sure that the host system at the primary site is configured toreceive sense information from the VSP G1000 primary system (forexample, using SNMP). This must also be done at the secondary site if ahost is connected to it.

Note: Procedures for disaster recovery involve releasing pairs. However,when using Business Continuity Manager you can perform disaster recoverywithout releasing pairs. To do this, when setting up TrueCopy for Mainframe,add remote paths between the secondary system Initiator ports and primarysystem RCU Target ports. Then add a remote connection from the secondarysystem CU to the primary system CU.

Remote copy and disaster recovery procedures are complex. Consult yourHitachi Data Systems Support Center on sense-level settings and recoveryprocedures.

Sense information shared between sitesWhen the primary system splits a TrueCopy for Mainframe pair due to anerror condition, the primary and secondary system send sense informationwith unit check status to the appropriate hosts. This is used during disasterrecovery to determine the consistency of the S-VOL, and must be transferredto the secondary site via the host failover software.

If the host system supports IBM PPRC and receives PPRC compatible senseinformation related to a TrueCopy for Mainframe pair, the host OS willperform the following actions:

1. Temporarily split all application I/O operations to the P-VOL.2. Enter an IEA491E message in the system log (SYSLOG) that indicates the

time that the P-VOL was split. Make sure that the system log is commonto both the primary and secondary operating systems.

3. Place specific information about the failure (SIM) in the SYS1.LOGRECdataset for use by service personnel. See Service Information Messages(SIMs) on page 10-18 for more information about SIM.

4. Wait for the IEA491E message to reach the secondary system.

9-2 Disaster recoveryHitachi TrueCopy® for Mainframe User Guide

5. Resume all host application I/O operations to the P-VOL. If the P-VOLfence level setting does not allow subsequent updates, the primarysystem will return a unit check for all subsequent write I/O operations,and the application will terminate.

Make sure that the primary and secondary systems are configured to reportthe service level SIMs to the host. Select the Services SIM of Remote Copy =Report setting on the Change CU Options window.

File and database recoveryFile recovery procedures for disaster recovery should be the same as thoseused for recovering a data volume that becomes inaccessible due to controlunit failure.

TrueCopy for Mainframe does not provide a procedure for detecting andretrieving lost updates. To detect and recreate lost updates, you must checkother current information (for example, database log file) that was active atthe primary system when the disaster occurred.

The detection and retrieval process can take some time. Your disasterrecovery scenario should be designed so that detection and retrieval of lostupdates is performed after the application has been started at the secondarysite.

You should prepare for file and database recovery using files for file recovery(for example, database log files that have been verified as current). You canalso use the sense information with system time stamp that is transferred viaERC.

CSUSPEND/QUIESCE TSO commandSee the IBM documents SG24 2595, SC35 0355, and SC35 0169 forimportant information about the optional QUIESCE parameter for theCSUSPEND TSO command.

The QUIESCE option of the CSUSPEND command has been disabled by APAROW15247 or APAR OW15248. Refer to either of these APARs and the latestIBM PPRC documentation for detailed information about the QUIESCE optionof the CSUSPEND command. Please check with your Hitachi Data SystemsSupport Center before using the CSUSPEND command with the QUIESCEoption to suspend TCz pairs on VSP G1000 storage systems. If theCSUSPEND command with the QUIESCE option is issued to certain volumes(for example, active SPOOL, PAGE, or CATALOG datasets, active SYSRESvolume), the attached hosts may enter a deadlock condition and may requirea storage control IML to correct the condition.

IEA494I system console messageThe IEA494I message is recommended as a trigger for automation over theIEA491E message, because the IEA494I message is reported to all attachedMVS hosts each time the P-VOL pair status changes, whereas the IEA491Emessage is reported to only one host system.


Switching operations to the secondary siteIf a disaster or failure occurs at the primary site, the first disaster recoveryactivity is to switch your operations to the secondary site. S-VOLs arerecovered individually based on the pair status and P-VOL fence levelinformation for each pair.

You can switch operations to the secondary site either by deleting pairs, thenreestablishing them when recovery is completed; or by not deleting pairs.Both methods are presented below.

To switch operations to the secondary site by deleting pairs

1. Record the pair status and fence level of each S-VOL.2. Analyze the consistency of the S-VOLs, based on pair status and Primary

Volume Fence Level setting in the Create TC Pairs window. See CheckingS-VOL consistency with the P-VOL on page 9-5.

3. Perform file recovery as needed.4. Split all pairs from the secondary system using one of the following

commands:

¢ CCI pairsplit¢ BCM YKSUSPND¢ PPRC CSUSPEND

5. Release all pairs using one of the following commands:

¢ CCI pairsplit -S¢ BCM YKRECOVER¢ PPRC CRECOVERIf you are not using these tools, connect to each secondary system withDevice Manager - Storage Navigator to split and release the pairs.

Note: When the S-VOL is no longer paired, it cannot be distinguished itfrom a non-TrueCopy for Mainframe volume. Use the appropriate meansto change the S-VOL volume labels.If necessary, use ICKDSF REFORMAT to change the labels (VOLSERs) ofthe S-VOLs.

6. Complete file recovery procedures.7. Vary the S-VOLs online.8. If an IPL of the remote host system is not required, bring the S-VOLs

online. If an IPL is required:

a. Remote copy SIMs must be cleared from the secondary systemsbefore OS IPL. Contact your service personnel to clear the SIMs.

b. Perform an IPL of the remote host system.c. Wait until the IPL is complete, and then vary the S-VOLs online (if

they did not come online automatically).9. At the secondary site, start critical host operations, with the previous S-

VOLs now the P-VOLs.


To switch operations to the secondary site by not deleting pairs

1. Record the pair status and fence level of each S-VOL.2. Analyze the consistency of the S-VOLs, based on pair status and Primary

Volume Fence Level setting in the Create TC Pairs window. See CheckingS-VOL consistency with the P-VOL on page 9-5.

3. Perform file recovery as needed.4. Run the BCM YKSUSPND REVERSE.5. Complete file recovery procedures.6. Vary the S-VOLs online.7. If an IPL of the remote host system is not required, bring the S-VOLs

online. If an IPL is required:

a. Remote copy SIMs must be cleared from the secondary systemsbefore OS IPL. Contact your service personnel to clear the SIMs.

b. Perform an IPL of the remote host system.c. Wait until the IPL is complete, and then vary the S-VOLs online (if

they did not come online automatically).8. At the secondary site, start critical host operations, with the previous S-

VOLs now the P-VOLs.

Checking S-VOL consistency with the P-VOLAn S-VOL's consistency refers to whether S-VOL data is identical to data inthe P-VOL. This is dependent on your Fence Level setting, which determineswhether data is copied to the P-VOL if an error occurs during an update to theS-VOL.

The following table shows S-VOL consistency information, based on DeviceManager - Storage Navigator pair status and the P-VOL fence level setting.(For the corresponding CCI status names, see CCI pair status names on page7-5.)

S-VOL status Type Fence level Consistency of S-VOL

Unpaired -- Data StatusNever

Not consistent. The S-VOL does not belong to a pair.Even if you have created a pair using this volume, if thepair status is still unpaired, you must regard its data asnot consistent with the P-VOL.

Pending Duplex -- Data StatusNever

Not consistent. The S-VOL is not synchronized becausenot all tracks have been copied from the P-VOL yet. ThisS-VOL must be initialized (or copied from the P-VOL at alater time).

Duplex -- Data Status Consistent. The S-VOL is synchronized with its P-VOL.

Never Needs to be analyzed*. The S-VOL requires furtheranalysis to determine its level of consistency.

Suspended Initial copyfailed

Data StatusNever

Not consistent. The S-VOL is not synchronized becausenot all tracks have been copied from the P-VOL yet. The


S-VOL status Type Fence level Consistency of S-VOL

S-VOL must be initialized (or copied from the P-VOL at alater time).

Suspended S-VOL byoperator

Data StatusNever

Suspect. The S-VOL is not synchronized with its P-VOL ifany write I/Os were issued to the P-VOL after the pairwas split. The pair must be released and restarted usingEntire Volume for the Initial Copy Type option. If you aresure that no data on the P-VOL changed, you can useNone for Initial Copy Type.

Suspend All othertypes

Data Consistent. The S-VOL is synchronized with its P-VOL.

Status Never Suspect. The S-VOL is not synchronized with its P-VOL ifany write I/Os were issued to the P-VOL after the pairwas suspended. Restore the consistency of the S-VOLand update it, if required. The time of suspensionindicated on the Last Update Time field of the DetailedInformation dialog box (MCU SVP time) will help todetermine the last time the S-VOL was updated.

For pairs with a P-VOL fence level setting of Never, further analysis is required to determine the S-VOLconsistency. This can be determined by using sense information transferred via host failover, or bycomparing the contents of the S-VOL with other files that are confirmed to be consistent (for example,database log files). The S-VOLs should be recovered using the files that are confirmed to be consistent.Actual data recovery must be done using recovery point data in the database operation log.

Transferring operations back to the primary siteWhen host operations are running at the secondary site, the primary sitemust be restored and operations transferred back.

Create TrueCopy for Mainframe pair by specifying secondary site volume toprimary volume and primary site volume to secondary volume.

Select the appropriate procedure below based on whether you deleted pairsto switch operations to the secondary site, or ran the Business ContinuityManager YKSUSPND REVERSE command.

To transfer operations to the primary site—if pairs were deleted whenoperations were switched to the secondary site

1. At the primary site, bring up the host. Make sure that TCz componentsare operational.

2. At the primary system, release all pairs on the primary system.Specify Force (All pairs in the same remote connections) in the DeletingMode option to release all TCz pairs in each CU. Make sure to connectwith all primary systems and all CUs to release all pairs.

3. At the primary system, delete the TCz association with the secondarysystems (Remove Remote Connection). In Device Manager - StorageNavigator, connect to each primary system to make sure that allsecondary systems are deleted.

4. At the primary and secondary systems, change path and port settings.


- If you plan to use the same remote paths:

¢ At the primary system, change the existing initiator ports to RCUtarget ports.If system option mode 114 is enabled on all primary and secondarysystems, the ports will reconfigure automatically if you use theCESTPATH or YKBLDPTH command to add the pairs at the secondarysite.For Fibre Channel interface, do not use the CESTPATH or YKBLDPTHand CDELPATH or YKDELPTH commands at the same time as the SCSIpath definition function of LUN Manager. The Fibre Channel interfaceports need to be configured as initiator ports or RCU target portsbefore the CESTPATH or YKBLDPTH and CDELPATH or YKDELPTHcommands are issued.

¢ At the secondary system, change the existing RCU target ports toinitiator ports.If system option mode 114 is enabled on all primary and secondarysystems, the ports will reconfigure automatically if you use theCESTPATH or YKBLDPTH command to add the pairs at the secondarysite.For Fibre Channel interface, do not use the CESTPATH or YKBLDPTHand CDELPATH or YKDELPTH commands at the same time as the SCSIpath definition function of LUN Manager. The Fibre Channel interfaceports need to be configured as initiator ports or RCU target portsbefore the CESTPATH or YKBLDPTH and CDELPATH or YKDELPTHcommands are issued.

5. At the secondary system, check that it is ready to create TrueCopy forMainframe pair.

6. At the secondary system, create TrueCopy for Mainframe pair andsynchronize S-VOL with P-VOL. Make sure to use Entire Volume for theInitial Copy Type option. Confirm that the pairs are created and thatstatus is Duplex.

7. At the secondary system, halt host operations and vary the P-VOL offline.This maintains synchronization of the pairs.

8. At the secondary system, split the pairs. Confirm that the pairs are splitand status is Suspended - S-VOL by operator before proceeding. If anerror occurs, resolve it before proceeding.

9. At the secondary system, release the pairs. You do not need to use theForce Delete Pairs (TC Pairs) option.

10. At the primary and secondary system, change the path and port settings.- If you plan to use the same data paths:

¢ At the primary system, change the existing RCU target ports toinitiator ports.

¢ At the secondary system, change the existing initiator ports to RCUtarget ports.

11. At the primary system, check that it is ready to create TrueCopy forMainframe pair.


12. At the primary system, create TrueCopy for Mainframe pair. If all P-VOLand S-VOL are synchronized, you may use None for the Initial Copy Typeoption. If P-VOL and S-VOL are not fully synchronized, use Entire Volumefor Initial Copy Type.

13. Vary the primary system and P-VOLs online, and start host operations.

Below is the procedure to transfer operation back to the primary sitewithout deleting pairs.

1. At the primary site, bring up the host. Make sure that TCz componentsare operational.

2. Run the Business Continuity Manager YKRESYNC REVERSE command.3. At the secondary system, halt host operations and vary the P-VOL offline.

This maintains synchronization of the pairs.4. Run the YKSUSPND FORWARD command.5. Run YKRESYNC FORWARD command.6. Vary the primary system and P-VOLs online, and start host operations.


10Troubleshooting

This chapter provides TrueCopy for Mainframe troubleshooting information.

□ Error codes and messages

□ General troubleshooting

□ Remote path status problems

□ Split pair problems

□ Changing microcode problem

□ Troubleshooting using CCI

□ Service Information Messages (SIMs)

□ TPC-R troubleshooting

□ Pinned track recovery

□ Calling the Hitachi Data Systems Support Center

Troubleshooting 10-1Hitachi TrueCopy® for Mainframe User Guide

Error codes and messagesDevice Manager - Storage Navigator displays messages when error conditionsoccur during TrueCopy for Mainframe operations. The message describes theerror and provides a part code and error code.

The error message may also include a VSP G1000 error code. You may needto contact Hitachi Data Systems Support Center (see Getting help on pagexiii); please report the error codes. See Hitachi Virtual Storage PlatformG1000 Mainframe System Administrator Guide for a list of the error codes.

General troubleshootingThe following table provides a list of general errors.

For troubleshooting information about PPRC and P/DAS operations, pleaserefer to the IBM PPRC and P/DAS user documentation: Planning for IBMRemote Copy (SG24 2595), Advanced Copy Services (SC35 0355), andDFSMS MVS V1 Remote Copy Guide and Reference (SC35 0169).

Error Corrective action

The Device Manager - StorageNavigator computer hangs, orTrueCopy for Mainframe operationsdo not function properly.

• Make sure that the problem is not beingcaused by the PC or Ethernet hardware orsoftware, and restart the PC. Restarting theDevice Manager - Storage Navigator computerdoes not affect storage system operations.

• Make sure that all TrueCopy for Mainframerequirements and restrictions are met (forexample, Track format, LVI, VOLSER, DFW.

• Make sure that the primary and secondarysystem and data paths are powered on andfully operational (NVS, cache).

• Check all input values and parameters tomake sure that you entered the correctinformation about the Device Manager -Storage Navigator computer (for example,secondary system S/N and ID, pathparameters, P-VOL and S-VOL IDs).

An initiator channel-enabled LEDindicator (on the VSP G1000 controlpanel) is off or flashing.

Contact Hitachi Data Systems Support Center (seeGetting help on page xiii).

The pairs and/or remote systemsare not displaying correctly.

Make sure that the correct CU is selected.

A TrueCopy for Mainframe errormessage displays on the PC.

Resolve the error, and then try the TrueCopy forMainframe operation again.

There is a problem with the DeviceManager - Storage Navigator orTrueCopy for Mainframe software.

Make sure that the problem is not the PC or LANhardware or software. Try restarting the PC andreconnecting to the storage system.

The remote system path status isnot normal.

Check the path status (Remote Connectionwindow), and see Remote path status problems onpage 10-3.

10-2 TroubleshootingHitachi TrueCopy® for Mainframe User Guide


Pair status is Suspend (pairsuspended-error).

See Split pair problems on page 10-5.

Monitoring data is not updatedthough the Monitoring Switch optionis set to Enable.

Because the time setting of SVP is changed, themonitoring data might not be updated. DisableMonitoring Switch, then enable again. For moreinformation about Monitoring Switch, see theHitachi Virtual Storage Platform G1000Performance Guide.

Remote path status problemsThe following table provides a list of remote path status problems.

Path status Description Corrective action

Normal This path has beensuccessfullyestablished and canbe used for TrueCopyfor Mainframe copyactivities.

None required.

InitializationFailed

The link initializationprocedure to theremote storagesystem failed becausethe physical pathconnection wasmissing between thelocal and remotestorage system.

• Make sure that the local and remotestorage systems are physically andcorrectly connected.

• Make sure that you entered the correctremote storage system S/N, ControllerID, and local and remote storage systemport numbers.

• Make sure the local and remote storagesystem ports are configured correctly.

CommunicationTime Out

Communicationbetween the local andremote storagesystem timed out.

• Make sure the remote storage system ispowered on and that NVS and cache arefully functional.

• Make sure that network relay devices areproperly configured and functional. Thisincludes cables, connectors, switches,extender devices, communication lines,and all other devices connected to theextenders.

Port Rejected The local storagesystem rejected thelogical path linkcontrol functionbecause all logicalpath resources in thelocal storage systemare being used forother connections.

• Delete all paths and secondary systemsnot in use.

• Make sure that all local and remotestorage system ports are properlyconfigured: ordinary RCU target ports forremote storage systems, initiator portsfor local storage systems. If necessary,connect to the remote storage system todelete paths.



Serial NumberMismatch

The remote storagesystem's S/N doesnot match thespecified S/N.

• Make sure that you entered the correctremote storage system S/N andController ID, and local and remotestorage system port numbers.

• Make sure the local and remote storagesystem ports are configured correctly.

• Make sure that data path relay equipmentis properly configured and functional. Thisincludes cables, connectors, switches,extender devices, communication lines,and all other devices connected to theextenders.

Invalid Port The specified port isnot configured as aninitiator port, or thispath already exists.

• Make sure the correct port on the localstorage system is configured as aninitiator port.

• Make sure that no two paths betweenlocal and remote storage system portshave the same settings.

• Make sure that you entered the correctremote storage system S/N andController ID, and local and remotestorage system port numbers.

• Make sure that the local and remotestorage system ports are configuredcorrectly.

• Make sure that data path relay equipmentis properly configured and functional. Thisincludes cables, connectors, switches,extender devices, communication lines,and all other devices connected to theextenders.

Pair-Port NumberMismatch

The specified port inthe remote storagesystem is physicallydisconnected from thelocal storage system.

• Make sure that you specified the correctremote storage system port number.Correct the port number if necessary.

• Make sure that the cables between thelocal and remote storage system portsand between the local and remote storagesystem switches are connected correctly.

• Make sure that the topology settings ofthe local and remote storage systemports are correct.

Pair-Port TypeMismatch

The specified remotestorage system portis not configured asan RCU target port.

Make sure that the remote storage systemport is configured as an RCU target port.

CommunicationFailed

The local storagesystem connected tothe remote storagesystem successfully,but logical

• Make sure that the remote storagesystem port and the relay equipment areconfigured correctly.

• Make sure that data path relay equipmentis properly configured and functional. Thisincludes cables, connectors, switches,



communicationtimeout occurred.

extender devices, communication lines,and all other devices connected to theextenders.

In Progress Paths are beingcreated or deleted, orthe port attribute isbeing changed.

Wait until processing is completed.

Path Blockade Blockaded due tocontinual path or linkfailure.

See the following.

The local storagesystem port does notwork.

Repair the port on the local storage system,then restore the path*.

The remote storagesystem port does notwork.

Repair the port on the remote storage system,then restore the path*.

The path relayequipment does notwork.

Repair the path relay equipment, then restorethe path*.

The connection cableis physically broken.

Replace the broken cable, then restore thepath*.

Program Error A program error isdetected.

Restore the path*.

* To restore a path, delete and then add the path again. It may be necessary to deleteand then add the secondary system again.To delete the secondary system or path, see Deleting TrueCopy for Mainframe on page7-20 or Deleting remote paths on page 7-17. To re-register, see Adding remoteconnection on page 5-3. If you cannot restore the path after performing theseoperations, contact Hitachi Data Systems Support Center.

Split pair problemsThe following table provides a list of split pair problem types.

Pairstatus/

type

Appliesto Description Corrective action

P-VOL byOperator

P-VOL The user split the pairfrom the primary systemspecifying Disable for thePrimary Volume Writeoption. The S-VOL splittype is by primarysystem.

Resynchronize the pair from theprimary system (Resume Pair).

S-VOL byOperator

P-VOL,S-VOL

The user split the pairfrom the primary orsecondary system



Pairstatus/

type


specifying Disable for thePrimary Volume Writeoption.

by MCU S-VOL The secondary systemreceived a request fromthe primary system tosplit the pair. The P-VOLsplit type is P-VOL byOperator or S-VOL byOperator.


Suspended(pairsuspended-error)/ byRCU

P-VOL The primary systemdetected an errorcondition at thesecondary system, whichcaused the primarysystem to split the pair.The S-VOL split type is S-VOL Failure.

Clear the error condition at thesecondary system or S-VOL, thenresynchronize the pair from theprimary system.If you need to access the S-VOL toclear the error conditions, release thepair from the secondary system.After you clear the error conditionsfrom S-VOL, restart the pair.

Delete Pairto RCU

P-VOL The primary systemdetected that the S-VOLstatus changed toSimplex because the userreleased the pair fromthe secondary system.The pair cannot beresynchronized becausethe S-VOL does not havethe Suspend status.

Release the pair from the primarysystem, then recreate the pair. UseEntire Volume for the Initial CopyType option to resynchronize thepair. Use None only if data in the P-VOL is identical to data in the S-VOL.

Suspended(pairsuspended-error)/ S-VOL Failure

P-VOL The primary systemdetected an error duringcommunication with thesecondary system, ordetected an I/O errorduring update copy. Inthis case, the split typefor the S-VOL is usuallyS-VOL Failure.

• Check the path status on theRemote Connection window. Iferrors occurred on the path,clear the error conditions.

• Clear any error conditions at thesecondary system or S-VOL,then resynchronize the pair fromthe primary system.

• If you need to access the S-VOLto clear the error conditions,release the pair from thesecondary system. After youclear the error conditions,recreate the pair.

Suspend-delete pairto RCU/MCU IMPL

P-VOL,S-VOL

The primary system couldnot find valid controlinformation in itsnonvolatile memoryduring the IMPLprocedure. This erroroccurs only if the systemis without power for more

Resynchronize the pair from theprimary system. An entire initial copyoperation will be performed inresponse to the Resume Pairrequest.


Pairstatus/

type


than 48 hours (forexample, power failure orfully dischargedbatteries).

Suspended(pairsuspended-error)/Initial CopyFailed

P-VOL,S-VOL

The primary system splitthis pair during the initialcopy operation. The dataon the S-VOL is notidentical to the data onthe P-VOL.

Release the pair from the primarysystem. Clear all error conditions onthe primary system, P-VOL,secondary system, and S-VOL.Recreate the pair.

by FREEZE P-VOL,S-VOL

All TrueCopy forMainframe pairs in theprimary system were splitby the CGROUP/FREEZEcommand.

Resynchronize the pairs from theprimary system using Resume Pair orthe CESTPAIR (MODE=RESYNC) TSOcommand.

Changing microcode problemThe following table provides troubleshooting information for changing themicrocode.


The IEA498I message is reported when youchange the microcode online.

If the controller emulation type of the hostthat is connected to the primary site isI-2107, and a TrueCopy for Mainframe pairexists, the IEA498I message that indicatesthe path blockade may be reported to thehost when you change the microcode of theprimary site or the secondary site online. Ifthe IEA498I message is reported, confirmthe path and the pair status of the primarysite.

Troubleshooting using CCIWhen an error occurs in pair operations using CCI, you can identify the causeof the error by referring to the CCI operation log file. This file is stored in thefollowing directory by default:

/HORCM/log*/curlog/horcmlog_HOST/horcm.logWhere:

• * is the instance number.• HOST is the host name.

Example:


Error codes appear on the right of the equal symbol (=).

Review CCI error codes in the following topics.

• SSB2 error codes when SSB1 = 2E31/B901/B90A/B90B/B912/D004 onpage 10-8

• SSB2=B992 error codes when SSB1 = B901 or B90A on page 10-18

SSB2 error codes when SSB1 = 2E31/B901/B90A/B90B/B912/D004

Error code(SSB2) Description

47A3 The pair cannot be split because of one of the following conditions:• Write access permitted in the S-VOL is unsupported.• The Swap Suspend is unsupported.

47BA The pair cannot be created because the specified P-VOL is one of the following:• Used as an SIz S-VOL.• Intervention-required or protected.

4A5C The pair cannot be created because TCz asynchronous is not supported.

4A96 The pair cannot be created because the specified P-VOL belongs to a different CLPRthan the registered consistency group CLPR.

4B02 A pair cannot be resynchronized because the specified consistency group does not havethe Open/MF attribute.

4B04 The pair cannot be created because the specified P-VOL is defined as the commanddevice.

4B22 The pair cannot be resynchronized because the specified volume is in failover in PPRC.

4B23 The pair cannot be split because the specified volume is in failover in PPRC.

4B2F The pair operation was rejected because the online microcode is being replaced.

4B32 The pair cannot be created because the specified P-VOL is one of the following:• Used by Compatible FlashCopy® V2• Used by Compatible Software for IBM® FlashCopy® SE• A TSE volume

4B85 The consistency group Paircreate or Pairresync was rejected because the specified P-VOL is a Compatible FlashCopy® V2 S-VOL.

4B86 The Paircreate or Pairresync (managed by cylinder) was rejected because the specifiedP-VOL is a Compatible FlashCopy® V2 S-VOL.

4BB2 The Paircreate (Time Stamp mode) was rejected because the specified volume isalready used in Compatible XRC.



4BE0 The pair operation was rejected because the necessary shared memory is not mountedin the primary system.

9100 The command cannot be executed because the user authentication is not performed.

B920 The pair cannot be created because the system identifier is not correct (left-mostnumber in the 6-digit serial number).

B927 You cannot run the following operations to a pair in a 2DC configuration:Swap SuspendTakeover

B928 The pair cannot be created because the Mirror ID is invalid.

B929 The pair operation was rejected because the online microcode is being replaced.

B92A The pair cannot be created because the specified volume is a command device.

B934 The pair cannot be created because TCz is not installed.

B935 S-VOL hide mode is not supported.

B93B The specified volume is a P-VOL. The pair cannot be released because the P-VOL isspecified as an S-VOL.

B941 The specified volume is an S-VOL. The pair cannot be released because the S-VOL isspecified as a P-VOL.

B945 The command was rejected because the volume is unpaired.

B952 The specified LU is not defined. The DKC configuration might have been changed.Restart CCI.

B97B The operation cannot run because pair status is either PSUS (by user) or PSUE (becauseof failure).

B97C The command was rejected because the volume is unpaired.

B990 The pair cannot be created because the consistency group number is greater than isallowed.If this error occurred when you did not specify the consistency group number, ContactHitachi Data Systems Support Center (see Getting help on page xiii).

B994 The Swap Resync operation cannot be performed because the S-VOL is not inSuspended or SSWS status. (Swap Resync resynchronizes differential data when the S-VOL is swapped for the P-VOL.)

B998 The pair cannot be created because the secondary system path setting is invalid.

B99B The pair cannot be created because TCz Asynchronous is not supported.

B9BD The DKC LDEV configuration might have been changed while starting CCI. Restart CCI.

B9C0 The source of the command device has run out. In LUN Manager, set the commanddevice to OFF, then to ON.

C05E The pair split request was rejected because secondary system and primary system werenot paired with the specified serial numbers and SSIDs.

C073 The pair deletion request was rejected because secondary system and primary systemwere not paired with the specified serial numbers and SSIDs.



C075 A request for a Paircreate or Pairresync operation was rejected because the TCzprogram product is not installed.

C0A1 The pair cannot be split because the S-VOL was not paired with the P-VOL.

C0A2 A request for a Pairsplit-S operation was rejected because the S-VOL was not pairedwith the P-VOL using the Paircreate command.

C0F2 The pair cannot be created because the specified DKC is the same for the primary andsecondary system.

C162 The pair cannot be resynchronized because the pair was not in the Suspend status.

C16B The pair cannot be created because the S-VOL is not available.

C184 A request for a Pairsplit-S operation was rejected because the status change of the S-VOL failed.

C189 A request for a Pairsplit-S operation was rejected because the pair status was invalid.

C18A A request for a Pairsplit-S operation was rejected because the corresponding volume orgroup was changing status.

C194 The pair cannot be split because the S-VOL pair status was in transition.

C195 A request for a Pairsplit-r operation was rejected because the pair status was alreadySuspended (by user) Suspended (because of failure).

C198 Pair split cannot run because the group includes no pair that can be split.

C199 A request for a Pairsplit-r operation was rejected because the corresponding volume orgroup was changing status.

C1BE The pair's status cannot be changed during the power-on processing of the DKC.

C1D6 The command was rejected because it was issued to a non-TCz volume.

C211 The command was rejected because the specified volume is a P-VOL. If the error occurswhen the volume is unpaired, select the volume in Device Manager - Storage Navigator,release the pair using the Force Delete Pairs (TC Pairs) window, and then run thecommand again.

C212 The command was rejected because the specified volume is an S-VOL. If the erroroccurs when the volume is unpaired, select the volume in Device Manager - StorageNavigator, release the pair using the Force Delete Pairs (TC Pairs) window, and then runthe command again.

C214 The command was rejected because the secondary system is not registered, or theregistered information is invalid.

C215 The command was rejected because an internal logical error has occurred.

C218 The command was rejected because the pair status is invalid.

C21A The command was rejected because the P-VOL status is other than Suspended (byuser) Suspended (because of failure).

C21C The command was rejected because the secondary system is not registered, or theregistered information is invalid.

C22A The command was rejected because the pair release was run on a volume other than P-VOL.



C22C The command was rejected because the volume is unpaired.

C22D The command was rejected because the specified volume is the volume other than theP-VOL.

C22E The command was rejected because the pairsplit command specifying -P option (writeprotection of P-VOL) was issued to a volume whose status is not Duplex.

C233 The command was rejected because the S-VOL status is unpaired.

C234/C235/C236/C237

The command was rejected because an internal logical error has occurred.

C238 The command was rejected because the specified volume is the volume other than theP-VOL.

C239 The command was rejected because the pair resync was operated on a volume whosestatus is other than Suspended (by user) Suspended (because of failure).

C23A The command was rejected because an internal logical error has occurred.

C23B The command was rejected because the volume is unpaired.

C23C The command was rejected because the volume status is other than Duplex or PendingDuplex.

C23D The command was rejected because the command for TCz asynchronous was issued tothe TCz asynchronous volume.

C23E The command was rejected because the volume status is COPY.

C267 The pair cannot be created because the command was issued to the command device.

C271 The command was rejected because the specified consistency group number is invalid.

C28B The command was rejected because the horctakeover command was issued to a volumewhose status is not SSWS.

C28C The command was rejected because the secondary system is not registered, or theregistered information is invalid.

C28D There is no volume to which the horctakeover command can run.

C28E The command was rejected because an internal logical error has occurred.

C297 The command was rejected because the specified volume is used as an S-VOL.

C2A0 The pair cannot be created because the capacity that is used by software products otherthan TCz exceeds license capacity.

C2A1 The command was rejected because an internal logical error has occurred.

C2A3 The pair cannot be created because the used capacity exceeds the license capacity.

C2B3 The command was rejected because DP-VOL capacity is changing.

C2B4 The command was rejected because an internal logical error has occurred.

C2B5 The pair cannot be created because the TCz P-VOL is being initialized by ShadowImage.

C2B6 The command was rejected because the releasing pages in DP-VOL is in progress.

C300 The TCz pair associated with a URz pair cannot be added because the Disaster RecoveryExtended program product is not installed on the primary system.



C301 The TCz pair associated with a URz pair cannot be added because the Disaster RecoveryExtended program product is not installed on the secondary system.

C304 The pair cannot be created because the S-VOL is a DP-VOL.

C305 The pair cannot be created because the capacity that is used by TCz in the secondarysystem exceeds license capacity. Check license capacity, including for related softwareproducts.

C30D The volume in the secondary system or another volume that belongs to the same groupis changing to Simplex or Suspend status. Retry the operation after several minutes.

C310 The NVS is not ON in the primary system.

C311 The storage system level cache is not valid in the primary system.

C312 The P-VOL is not in unpaired status.

C313 The P-VOL is not in Suspended or Suspended status.

C314 The P-VOL is not in unpaired status.

C315 The P-VOL includes PIN data.

C316 The P-VOL is in the process of drive copy for failure assistance.

C317 The P-VOL is in the process of drive copy for an SVP request.

C318 The P-VOL is terminating the copy task.

C319 The P-VOL is in the process of collection copy.

C31A The P-VOL is in the process of collection access.

C31B The P-VOL is blocked.

C31C The P-VOL is blocked and impossible to access.

C31D The P-VOL is being formatted.

C31E The P-VOL is read only.

C320 The number of remote paths between primary and secondary system is 0 (notspecified).

C321 The number of remote paths between primary and secondary system is smaller than theminimum required.

C322 The DKC type of the primary system does not support TCz.

C324 The secondary system's sequence number, SSID, or CU are invalid.

C325 The NVS is not ON in the secondary system.

C326 The storage system level cache is not valid in the secondary system.

C327 The pair cannot be created because the P-VOL is not available for remote copy.

C328 The track formats of the P-VOL and the S-VOL do not match.

C32A The S-VOL is protected by the Volume Retention Manager.

C32B The P-VOL is protected by the Volume Retention Manager.

C32C The S-VOL is protected by the Volume Retention Manager.



C32D The S-VOL is protected by the Volume Retention Manager.

C32E A request for a Add Pair operation was rejected because the specified secondary systemis an unsupported product.

C32F The number of P-VOL cylinders is not the same or smaller than the number of S-VOLcylinders.)

C330 P-VOL and S-VOL capacities are not the same.

C332 S-VOL cache is unavailable.

C333 S-VOL DFW is disabled.

C335 The S-VOL is the TCz P-VOL.

C336 The S-VOL includes PIN data.

C337 The S-VOL is in reserve status.

C338 Copy pair cannot be created because of the either of the following reasons.• The S-VOL is in the intervention-required condition, protected, or unusable status.• The S-VOL is the S-VOL or Reserved volume of ShadowImage, Reserved volume of

Volume Migration, or the volume of URz pair.

C339 The S-VOL is not available.

C33A A request for an Add Pair operation was rejected because the secondary system is a notsupported by TCz.

C33B The corresponding volume cannot be specified as an S-VOL because the volume is usedas another pair's S-VOL.

C33C A request for an Add Pair operation was rejected because the specified S-VOL was notmounted.

C33E The pair cannot be created because the S-VOL is not implemented or is blocked (DEVNOT READY status).

C33F The corresponding volume cannot be specified as an S-VOL because the volume isalready specified as a TCz pair volume.

C35C The P-VOL is not accessible.

C370 There are fewer paths than the required minimum following a path failure or because aninvalid path was specified.

C371 The process that is performed after the copying process of Volume Migration in the S-VOL is in progress. Retry the operation several minutes later.

C372 The process that is performed after the copying process of Volume Migration in the P-VOL is in progress. Retry the operation several minutes later.

C373 A request for an Add Pair operation was rejected because the specified S-VOL is aShadowImage Reserved volume.

C374 A request for an Add Pair operation was rejected because the specified P-VOL is aShadowImage Reserved volume.

C378 The add pair operation is rejected because the number of active paths is less than thededicated number of minimum paths.



C379 There are fewer paths than the required minimum following a path failure or because aninvalid path was specified.

C37A An internal error occurred.

C37B The S-VOL is not available.

C37C The storage system level cache is not valid in the secondary system.

C37D The NVS is not ON in the secondary system.

C37E The S-VOL cache is unavailable.

C37F The S-VOL DFW is disabled.

C380 The primary system cache is in transition to blockage on one side.

C381 The primary system cache is in the process of being restored.

C382 The primary system cache is either in transition to blockage on one side or in theprocess of being restored on one side.

C388 The pair cannot be created because the emulation type is not available for the specifiedvolume.

C38B The secondary system is already used by TCz.

C38D The S-VOL is not available.

C38E The S-VOL is not supported by TCz.

C390 The S-VOL status is not Suspended or Suspended.

C391 The S-VOL cannot be copied to because it is in the wrong pair status.

C392 The volume cannot be used as an S-VOL because it is in online status, is already beingused by TCz, or is being used by another replication product.

C393 The S-VOL includes PIN data.

C394 The S-VOL is in online status.

C395 The S-VOL cannot be used due to LDEV blockage, collection access, or other reasons.

C398 The pair cannot be created because the emulation type is not available for the specifiedvolume.

C39B An internal error occurred.

C39E The pair cannot be created because the capacity of the P-VOL exceeded the maximumvolume capacity allowed to create a TCz pair.

C39F The pair cannot be created because the capacity of the S-VOL exceeded the maximumvolume capacity allowed to create a TCz pair.

C3A0 The P-VOL is a device not supported by TCz.

C3A5 The TCz pair cannot be added nor resumed because the specified data volume is inonline status.

C3A6 The SSID or CU number of the secondary system is invalid.

C3A8 The device type combination between the P-VOL and S-VOL is invalid.



C3AA The secondary system's cache is blocked on one side.

C3AB The secondary system's cache is blocked on one side.

C3AC TCz is not supported for this controller emulation type of the secondary system.

C3AD The secondary system capacity exceeds the license capacity.

C3AE TCz is not installed on the secondary system.

C3AF The DKC type of the secondary system is not supported by TCz.

C3B1 The number of paths is smaller than the required minimum number of paths.

C3B3 An internal error occurred.

C3B5 The configuration combination of P-VOL and S-VOL is invalid

C3B6 The P-VOL is an SIz volume.

C3B7 The S-VOL is an SIz volume.

C3B8 An internal error occurred.

C3B9 The specified S-VOL LUN is not defined; or the LUN includes a CU LDEV that is notsupported by the primary system.

C3BA A request for an Add Pair operation was rejected because of one of the followingreasons:The secondary system's SSID or CU number is not supported.Though the secondary system's SSID or CU number is supported, the microcode of theprimary system device does not support them.

C3BD The P-VOL is in online status.

C3BE The following volumes cannot be specified as a TCz P-VOL:• SIz S-VOL not in Suspended status• SIz P-VOL in the process of reverse copy

C3BF A TCz S-VOL cannot be specified as an SIz S-VOL, reserved volume, or P-VOL in theprocess of reverse copy.

C3C0 When the P-VOL is the SIz S-VOL, the SIz volumes must be a one to one combination.

C3C7 A request for an Add Pair operation was rejected because the specified volume wasalready part of a TCz or URz pair (including journal volumes).

C3CA The S-VOL is reserved; or a secondary system, S-VOL, or the path between primarysystem and secondary system is in the BUSY status.

C3CD The S-VOL is an SIz volume.

C3D2 The DKC type of the secondary system is not supported by TCz.

C3D3 SSID or CU number is invalid for specified secondary system.

C3D4 A pair cannot be created because the P-VOL is being used by Volume Migration.

C3D6 The specified S-VOL is unavailable because the connecting port cannot recognize it.

C3D7 The pair status of the S-VOL is invalid.



C3D8 The pair cannot be created because the volume specified for the S-VOL is a systemvolume.

C3D9 The pair cannot be created if the TCz S-VOL corresponds to any of the following:The volume is a DP-VOL; the pair using the volume is an SIz pair or a Volume Migrationreserve volume.The volume is a DP-VOL and an addition to volume capacity is in progress, or pages arebeing released.The capacity of the volume is different from the capacity of the P-VOLThe volume is initialized by SIz

C3DB S-VOL pair status is not Suspended or Suspended.

C4FC The required amount of shared memory for the operation is not installed in thesecondary system.

CB12 TC, TCz, UR, and URz cannot be mixed in the consistency group.

CB19 The secondary system consistency group cannot be deleted because the horctakeovercommand reversing operations between the P-VOL and S-VOL failed.

CB1A The secondary system consistency group was abnormally terminated because thehorctakeover command reversing operations between the P-VOL and S-VOL failed.

CB1D No dummy volume can be created in the S-VOL.

CB1F The secondary system does not support TCz.

CB20 In referring to the function bit, the system information reference was abnormallyterminated.

CB21 In a Pairresync operation, all difference setting was abnormally terminated.

CB23 An internal error occurred.

CB60 TCz is not installed in the secondary system.

CB66 The required differential area is not available in the secondary system.

CB67 An additional shared memory is not installed in the secondary system.

CB68 The required differential area is not available in the primary system.

CB69 The number of pairs exceeds the maximum number that can be created in a singleconsistency group.

CB6E The Add Pair operation cannot run because the P-VOL is an external storage systemvolume.

CB6F The Add Pair operation cannot run because the S-VOL is an external storage systemvolume.

CB71 The Add Pair operation cannot run because the P-VOL is an external storage systemmigration volume.

CB73 The Add Pair operation cannot run because the S-VOL is an external storage systemmigration volume.

CB75 The device is not recognized correctly.

CB76 The Add Pair operation cannot run because the paths are specified per storage system.



CB77 The used capacity of the Volume Retention Manager software product on the secondarysystem exceeds the license capacity.

CB78 The Add Pair operation cannot run because the specified S-VOL is defined as thecommand device.

CB7E A request for an Add Pair operation was rejected because the specified S-VOL belongsto a different CLPR than the registered consistency group's CLPR.

CB9E The pair cannot be added because the specified S-VOL does not support the time stamptransfer mode.

CBD7 The storage system is in internal processing. Try the operation again.

CBD8 A pair cannot be created because the specified primary system is one of the following:• A journal volume used for URz.• A URz secondary volume that is in a status other than Suspend.

CBD9 The pair cannot be added because the specified S-VOL is used for CompatibleFlashCopy® V2 or Compatible Software for IBM® FlashCopy® SE, or is the TSE volume.

CBDA The Add Pair operation cannot run because the used capacity of the Volume RetentionManager on the secondary system exceeds the license capacity.

CBDC A request for an Add Pair operation was received in the TCz-URz combination status.However, the command was rejected because the Mirror ID of URz was 0.

CBDD In configuring a TCz-URz multi-target configuration, a request for a TCz Add Pairoperation was rejected because the URz pair was in the process of copying.

CBE2 The Add Pair operation cannot run because the P-VOL is a Dynamic Provisioning Pool-VOL.

CBE3 The Add Pair operation cannot run because the S-VOL is a Dynamic Provisioning Pool-VOL.

CBE7 More than 65,280 pairs cannot be created in one storage system.

CBEB The pair cannot be created because the specified P-VOL is being shredded by VolumeShredder.

CBEC The pair cannot be created because the specified S-VOL is being shredded by VolumeShredder.

CBED The request for an Add Pair operation was rejected because the specified S-VOL was aURz S-VOL or journal volume.

CBEE The pair was not created because the specified P-VOL is part of a URz pair for deltaresync.

CBFA The pair operation failed because of one of the following reasons:• A CHA in the secondary system for connecting Mainframe is not installed.• All CHAs in the secondary system for connecting Mainframe is blocked.

CBFC The pair cannot be created because the consistency group number is not within thesupported range.


SSB2=B992 error codes when SSB1 = B901 or B90A

ErrorCode

(SSB1)

ErrorCode

(SSB2)Description

B901 B992 Pair cannot be created because DKC type dose not support TCzAsynchronous.

B90A B992 Consistency group information cannot be retrieved because TCzor URz is not installed.

Service Information Messages (SIMs)The VSP G1000 generates a service information message (SIM) to notifyusers of a possible service requirement for the storage system. The SVPreports all SIMs related to TrueCopy for Mainframe operations. The SIMsreported to the zSeries and S/390 host are logged in the SYS1.LOGRECdataset of the host operating system.

SIMs are classified according to the following severities: service, moderate,serious, or acute.

The following figure shows a typical 32 byte SIM from the VSP G1000. SIMsdisplay on the host console by reference code (RC) and severity. The six digitRC (composed of bytes 22, 23, and 13) identifies the possible error anddetermines the severity. The SIM type (byte 28) indicates the componentthat experienced the error. When byte 22 = 21, the SIM is a control unit SIM.When byte 22 = Dx, the SIM is a device SIM. When byte 22 = (D8 DC), thepair is TrueCopy for Mainframe. The SIM reference code DBFx indicates thatthe P-VOL status does not match with the S-VOL status, or the capacity ofthe paired volume in the secondary system exceeds the licensed capacity ofVolume Retention Manager.

For further information about SNMP operations and SIMs, see the HitachiVirtual Storage Platform G1000 Mainframe System Administrator Guide, orcontact your Hitachi Data Systems Support Center.

TPC-R troubleshooting The following failure conditions and recovery solutions are provided for BasicHyperSwap function using TPC-R.


Resynchronization fails due to shortage of host resourcesIf a shortage of resources occurs in the host system, resynchronization of theTrueCopy for Mainframe pair may fail with host system messages:IOSHM0803E (HyperSwap Disabled) and IOSHM0201I (Reason Code:40). Inthis case, correct the shortage of host resources by ensure adequateresources. Do this first, then delete the failed TCz pair from TPC-R, and thenperform the pair create operation again.

Cache failure, unregistered TPC-R error Both the pair create and pair resynchronization operations can fail if a cachefailure occurs on the storage system. You may receive an error codeunregistered in TPC-R error messages, 0F0E, in either of these instances.

In both cases, it is important to recover the cache failure first, then run thepair operation again.

Note: If you resynchronize before recovering from the cache failure, theresynchronization will fail and TPC-R will delete the pair and then recreate thepair, copying the entire P-VOL to the S-VOL.

Pinned track recoveryThis procedure ensures the pair's full data integrity while recovering thepinned track.

To recover a pinned track

1. Connect to the primary system of the pair containing a volume with thepinned track and select the CU where the P-VOL is located.

2. Release the pair that contains the volume with the pinned track.3. Perform your usual procedure for recovering data from a pinned track.

See the pinned track recovery procedures for your OS, or contact yourHitachi Data Systems Support Center in recovering the pinned track.

4. Recreate the pair from Create TC Pairs Window. Make sure to use theEntire Volume in the Initial Copy Type option.

Calling the Hitachi Data Systems Support CenterIf you need to call the Hitachi Data Systems Support Center, please provideas much information about the problem as possible, including:

• The circumstances surrounding the error or failure.• The content of any error messages displayed on the host systems.• The content of any error messages displayed on Device Manager -

Storage Navigator.• The Device Manager - Storage Navigator configuration information (use

the Dump Tool).


• The service information messages (SIMs), including reference codes andseverity levels, displayed by Device Manager - Storage Navigator.

The HDS customer support staff is available 24 hours a day, seven days aweek. If you need technical support, log on to the HDS Support Portal forcontact information: https://hdssupport.hds.com



APair operations using PPRC

VSP G1000 supports IBM Peer to Peer Remote Copy (PPRC) TSO and ICKDSFcommands for performing TrueCopy for Mainframe operations from thezSeries and S/390 host system.

PPRC commands and requirements are described in this topic. However, notall instructions for using the commands are provided. Refer to the IBM userdocumentation for more information.

□ Overview of PPRC commands

□ Requirements, restrictions, and notes

□ Conventions used in TSO commands

□ CESTPATH command

□ I/O control after failure—with CGROUP FREEZE/RUN

□ IEA494I and IEA491E console messages

Pair operations using PPRC A-1Hitachi TrueCopy® for Mainframe User Guide

Overview of PPRC commandsThe following operations can be performed using PPRC issued from JCL jobcards:

• Port configuration using Device Manager - Storage Navigator (cannot bedone using PPRC).You can change port type (RCU target to initiator, and so on) as part ofthe pair creation operation using CESTPATH.

• Add and remove remote paths between the main and target systems• Add and delete pairs• Split and resume pairs.• Display pair status and other information.

You cannot change options for remote connections, the CU, initial copypriority, or DFW to Secondary Volume using PPRC commands.

The following table describes TCz operations you perform using DeviceManager - Storage Navigator and the corresponding TSO and ICKDSFcommands.

HDvM - SNoperation

PPRC Commands1

TSO2 ICKDSF3 Issued to: Description

Add remoteconnection (andedit ports)

CESTPATH4 PPRCOPYESTPATH

primarysystem

Establishes remote paths from a primarysystem to a secondary system. The defaultsecondary system options are used. SeeCESTPATH command on page A-6 formore information.

Remove RemoteConnection

CDELPATH4 PPRCOPYDELPATH

primarysystem

Deletes all active paths between a primarysystem and a secondary system.

View RemoteConnectionProperties

CQUERY/PATHS

PPRCOPYQUERY/PATHS

primarysystem

Displays the status of all paths for the CUspecified by the DEVN parameter. TCzsupports the optional FORMAT/UNFORMATand VOLUME/PATHS parameters.

Create TC Pairs CESTPAIR(MODE= COPY)

PPRCOPYESTPAIR

P-VOL Creates a pair and sets the Initial CopyPriority and pair options (copy mode =synchronous only, Initial Copy Priority = 0,CFW data = Primary Volume Only, DFW toSecondary Volume = not required). TCzsupports the optional MODE, PACE, andCRIT parameters. The MSGREQ parameterdefaults to NO.

Split Pairs CSUSPEND PPRCOPYSUSPEND

P-VOL orS-VOL

Splits a pair. TCz supports the optionalPRIMARY parameter. See WARNING aboutthe QUIESCE parameter at the end of thistopic.

Delete Pairs(from primarysystem)

CDELPAIR PPRCOPYDELPAIR

P-VOL Releases a pair from the primary system.

A-2 Pair operations using PPRCHitachi TrueCopy® for Mainframe User Guide

HDvM - SNoperation

PPRC Commands1

TSO2 ICKDSF3 Issued to: Description

Delete Pairs(from secondarysystem)

CRECOVER PPRCOPYRECOVER

S-VOL Releases a pair from the secondary system.

View PairProperties

CQUERY/VOLUME

PPRCOPYQUERY/VOLUME

P-VOL orS-VOL

Displays pair status of the volume. TCzsupports the optional FORMAT/UNFORMATand VOLUME/PATHS parameters.

Resync Pairs CESTPAIR(MODE=RESYNC)

PPRCOPYESTPAIR

P-VOL Resynchronizes a pair, and sets the initialcopy options and pair options. TCz supportsthe optional MODE, PACE, and CRITparameters.

— P/DAS SWAP — primaryandsecondarysystem

Supported by TCz. Redirects applicationI/Os from the P-VOL to the S-VOL.

— CGROUP(FREEZE/RUN)

— primarysystem (P-VOL orsimplex)

Supported by TCz.

Notes1. Parameters and format for PPRC commands are not described in this document. For full information,

see the IBM publications Advanced Copy Services (SC35 0355), DFSMS MVS V1 Remote Copy Guideand Reference (SC35 0169), ICKDSF User's Guide and Reference (GC35 0033), and other IBMdocuments on ICKDSF R16 or later.

2. PPRC TSO commands are issued from the system console to the P-VOL or S-VOL.3. PPRCOPY ICKDSF commands are issued from JCL job cards.4. Port configuration using CESTPATH and CDELPATH requires system option mode 114 set to ON. If

114 is OFF, you must configure the ports using Device Manager - Storage Navigator before addingpaths or after deleting paths.Note that even with 114 set to ON, if the ports are in initiator/external mix mode, initiator ports donot automatically change to RCU target ports, and RCU target ports do not automatically change toinitiator ports. See S-VOL Read and other system options on page 3-3 for more information.

Options not supported by PPRCYou cannot change the following TCz options using PPRC commands:

• RCU options• Initial copy priority option• DFW to Secondary Volume pair options

Requirements, restrictions, and notesNote the following when using PPRC commands:

• TCz must be installed on the VSP G1000.• IBM PPRC must be installed on the host operating system.


• With CU emulation type I-2107, the lss parameter must be set for boththe primary and secondary system.

• Command extensions are supported with I-2107 emulation.• The TSO CESTPATH and PPRCOPY ESTPATH commands remove paths

previously established and replace them with the paths you specify. Makesure to specify existing paths that you want to continue using, or specifynew paths.If you delete all paths prior to running the command—because you wantto specify new paths with the command, the pair operation might suspendbecause no path exists temporarily.

• With Fibre Channel, do not use the CESTPATH and CDELPATH commands atthe same time that you use the SCSI path definition function of LUNManager. FC ports need to be configured as initiator ports or RCU targetports before the CESTPATH and CDELPATH commands are issued.

• The RESETHP option used with the CESTPATH command causes host I/Ooperations to be rejected. Before you use the RESETHP option, stop I/Ooperations from the host.

• PPRC commands may be rejected if you have registered 0xFFXX to theprimary and secondary system SSID. Specify the command excepting0xFFXX. (Note: the 'XX' of 0xFFXX is given in hexadecimal.)

• When you issue the QUERY command with the PATH option to the S-VOLusing ICKDSF, the command might be rejected. If this happens, you cancheck path status using the CQUERY command or Device Manager -Storage Navigator.

• When using I-2107 CU emulation type for the primary system when thehost is online to the S-VOL, run the CESTPAIR command to create a TCzpair requires ONLINSEC(YES). The operation fails if you do not useONLINSEC or if you use ONLINSEC(NO).Note that you cannot check whether a host system is online if thesecondary system does not support I-2107 CU emulation type. In thiscase, you can still run the CESTPAIR command with ONLINSEC(YES)—ifthe primary system is VSP G1000 and supports I-2107 CU emulationtype.

• If the PPRCOPY SUSPEND command issued to a pair in Pending status isrejected, split the pair using Device Manager - Storage Navigator.

WARNING: The CSUSPEND command QUIESCE option is disabled by APARsOW15247/48. Make sure to check with your Hitachi Data SystemsSupport Center before using this command and option on VSP G1000. Ifthe command and option is issued to certain volumes (for example, activeSPOOL, PAGE, or CATALOG datasets, active SYSRES volume), theattached host may enter a deadlock condition, requiring storage controlIML to correct the condition.See APARs OW15247 or 48 and the latest IBM PPRC documentation fordetailed information.

• Preserve Mirror FlashCopy function with Compatible FlashCopy®V2: When you create Compatible FlashCopy® V2 Preserve Mirror


relationships in COPY mode, both copies are not synchronized. If youissue Withdraw during the copy operation, both copies of the relationshipare suspended. Therefore, data consistency between the P-VOL and S-VOL is not ensured even though the TCz pair is in DUPLEX mode. Thisstatus can be confirmed by the CQUERY command.The following figure provides an example of when CQUERY is issued to theTCz P-VOL using the VOLUME parameter. The message, PAIR WAS THETARGET OF A WITHDRAWN PRESERVE MIRROR RELATION, displays. Torelease this status, delete the TCz pair. For details about the PreserveMirror FlashCopy function, see the Hitachi Compatible FlashCopy® UserGuide.

Conventions used in TSO commandsThe following table shows typefaces and symbols used in PPRC TSOcommands.

Typeface orSymbol Description Example

Normal text Used for command and keyword names orconsoles.

CESTPATH

Italic text Used for parameters that are to be replaced bythe appropriate character or number string.

ssid

Square bracket[ ]

Used for keywords and parameters that can beabbreviated.

[CGROUP(YES)]

vertical dash Used to separate selectable keywords. (YES|NO)


CESTPATH commandUse the CESTPATH command to establish remote paths from a primarysystem to a secondary system when using fiber cable. CESTPATH also allowsyou to enter a Controller ID for the secondary system.

Requirements• Fibre Channel ports must be configured as initiator ports or RCU target

ports before the CESTPATH and CDELPATH commands are issued.• When system option mode 114 is enabled, ports are configured

automatically when the CESTPATH and CDELPATH TSO commands are run(RCU target/initiator to initiator/RCU target). If this system option modeis disabled, ports must be configured using Device Manager - StorageNavigator.

• With Fibre Channel, do not use the CESTPATH and CDELPATH commandsat the same time as the LUN Manager SCSI path definition function.

CESTPATH command syntaxUse the following syntax for the CESTPATH command:

CESTPATH DEVN (X'dev#) PRIM (X'ssid' serial# X'lss') SEC (X'ssid'serial# X'lss') LINK (X'aabbccdd') [CGROUP (YES|NO)]When WWNN (World Wide Node Name) is specified, use the following syntax:

CESTPATH DEVN (X'dev#) PRIM (X'ssid' WWNN X'lss') SEC (X'ssid'WWNN X'lss') LINK (X'aabbccdd') [CGROUP (YES|NO)]

Note:

• For CDELPATH, the syntax for both PRIM and SEC is the same asCESTPATH.

• A unit check is reported on earlier model storage systems that do notsupport the syntax above.

CESTPATH parametersWhen fibre is used, CESTPATH parameters are the following.

Parameter Description

aa Bit 0 - 3: secondary system controller IDx2 – xF: Number stands for secondary system controller ID.(VSP G1000: x'7'; VSP: x'6'; USP V/VM: x'5')Bit 4-7: Unused (x0 fixed)

bb Primary system port number (0x00-0xff)

cc Secondary system port number (0x00-0xff)



dd Secondary system CU number (0x00-0xfe)

When WWNN is specified, CESTPATH parameters are the following.


aabb Primary system SAID (x'00 and port number)

ccdd Secondary system SAID (x'00 and port number)

WWN is the unique number for the controller and is indicated as follows.

I/O control after failure—with CGROUP FREEZE/RUNWhen a failure occurs in the P-VOL, you can stop host I/O and copyoperations, and then restart them when conditions improve using the TSOCGROUP command with the FREEZE and RUN options.

• CGROUP FREEZE:

¢ Stops host I/O to specified P-VOLsPresents state change pending (SCP) with extended long busy statusto host I/O requests. This causes the host to queue I/Os for the P-VOLs. SCP is indicated until the CGROUP/RUN command is issued oruntil the SCP time expires. (Pairs registered in a consistency groupare not in the SCP state, even after the CGROUP (FREEZE) commandis run.)

¢ Stops update copy operations to associated S-VOLsRemote paths are blocked between the specified primary andsecondary system to stop update copy operations to the S-VOLs.

¢ Splits pairs with P-VOLs on the specified primary system CU. (Pairsregistered in a consistency group are not in the SCP state, even afterthe CGROUP (FREEZE) command is run.)


• CGROUP RUN:

¢ Starts host I/O to P-VOLs again- Presents a state change interrupt (SCI) to the hosts, so that theyreissue the I/Os that were waiting while the P-VOLs were in the SCPstate.- Changes the P-VOL fence level to Never (PPRC CRIT=NO), so thatthe split P-VOLs accept host write I/O operations.

The CGROUP FREEZE/RUN command is supported for VSP G1000 when itfunctions as the primary system. VSP G1000 provides all required hostreporting for CGROUP operations (for example, IEA494I with extended longbusy (ELB) state), which is a key component of operations in IBM'sGeographically Dispersed Parallel Sysplex (GDPS) environment, which alsouses this command.

For disaster recovery implementations, VSP G1000s must be used at bothsites, because the secondary systems will be switched to primary systems.

Caution: VSP G1000 also supports the Business Continuity Manager Freezeand Run commands, which are equivalent to the TSO CGROUP command. Ifboth commands are performed simultaneously, the VSP G1000s find theappropriate volumes and run the commands.However, in this situation, the host cannot detect which command isperformed. Therefore, it is important not to use the Business ContinuityManager Freeze/Run commands and the CGROUP command at the same time.

CGROUP and FREEZE/RUN requirementsThe CGROUP command can only be issued to an P-VOL or a simplex volume inthe primary system. If issued to an S-VOL, the secondary system rejects itwith F/M=0F, reason code=58.

The requirements for CGROUP FREEZE/RUN support are:

• Storage system: The primary system to which the CGROUP commandwill be issued must be VSP G1000 storage systems (all mainframe andmulti-platform systems are supported). For disaster recoveryimplementations, you must use VSP G1000 storage systems at both sites,because the secondary systems will become primary systems in the eventof a disaster.

• PPRC: The host systems at the primary and secondary sites must haveIBM PPRC support and the PPRC ERP PTF

• SSIDs: The primary system to which the CGROUP command will be issuedmust have consecutive SSIDs. The Hitachi Data Systems Support Centerconfigures the SSIDs on the VSP G1000 SVP.

Caution: MVS requires that the storage system be offline during SSIDchanges. Reconfiguring SSIDs is therefore a disruptive event that must becarefully planned.


Also, SCP time specified from Device Manager - Storage Navigator's CUOption dialog box is invalid for pairs created using a consistency groupfrom Business Continuity Manager. You can, however, specify SCP timefor these pairs using the YKFREEZE command (range from 1 to 5seconds). If a failure suspension occurs, then SCP time becomes fixed at120 seconds and cannot be changed.

• When you run CGROUP FREEZE or RUN, the following information must bespecified:

¢ The device, which is the P-VOL or simplex volume LDEV ID (DEVNparameter)

¢ The primary system, which consists of the serial number and lowestSSID in the CU (PRIM parameter).

¢ The secondary system, which consists of the serial number and lowestSSID in the CU (SEC parameter).

Pair status before and after CGROUP FREEZE/RUN

The following table shows pair status for P-VOLs and S-VOLs before and afterCGROUP FREEZE/RUN operations.

Before CGROUPFREEZE/RUN After CGROUP/FREEZE After CGROUP/RUN

P-VOL S-VOL P-VOL S-VOL P-VOL S-VOL

Status Simplex — Simplex — Simplex —

Pending Pending Suspended Pending Suspended Pending

Duplex Duplex Suspended Duplex Suspended Duplex

Suspended Suspended Suspended Suspended Suspended Suspended

Using CGROUPThe following figure shows a simple example of the CGROUP FREEZE/RUNcommand implemented in a GDPS environment.


Figure key:

1. Read/write I/Os are issued from the host.2. A failure occurs on an P-VOL, and the primary system suspends the pair.3. Split and extended long busy state are reported to the host.4. The host reports IEA494I with extended long busy state.5. CGROUP/FREEZE commands are issued to groups.6. SCP sense bytes are reported if an I/O is issued to a frozen volume.7. I/Os are queued at the host.8. Host operations are switched to secondary site.

Command sequence example

You can issue CGROUP FREEZE/RUN commands manually or throughautomation (such as with GDPS). The following is an example sequence ofactions you may implement.

1. Suspend host updates to all specified TCz P-VOL.2. Block the specified primary-secondary system path to stop update copy

operations to S-VOLs.If the specified primary system does not have any P-VOLs, the FREEZEcommand is run without performing any operations (paths are notblocked, SCP is not indicated).

3. Change all P-VOLs to Suspended status.4. Resume host updates to suspended P-VOLs.5. Run the add secondary system operation to reestablish the blocked

remote paths. After paths are established, make sure to specify thedesired SCP time for the primary system using the Device Manager -Storage Navigator Edit SCP Time window. The range for SCP time is 0 to518,400 seconds (144 hours); the default is 120 seconds.

Note: If your specified SCP time is 601 seconds or longer, the microcodeversion cannot be downgraded to 70-03-xx-xx/xx or earlier. In this case,lower the SCP time setting to 600 seconds or less, downgrade, then resetto the desired time.

6. After the path is reestablished, run the resynchronize pair operation.

Other TSO commands used with CGROUP

You can use the following TSO commands in your CGROUP FREEZE/RUNworkflow:

• Use CESTPATH to recover a blocked primary-secondary path. Make sure touse the same parameters as when the path was established.

• After reestablishing the primary-secondary path that was blocked, useCESTPAIR/RESYNC to resynchronize the TCz pairs split by CGROUP/FREEZE.

• After reestablishing the primary-secondary path that was blocked, useCDELPAIR to release the pairs split by CGROUP/FREEZE. If CDELPAIR is


issued to a pair whose primary-secondary path is still blocked, theprimary system rejects the command (F/M=0F, TCz reason code=5A).

• Use CRECOVER to change a split S-VOL to simplex. This command is issuedto the S-VOL and does not affect the split P-VOL.

• Use CQUERY to generate output about paths and volumes after runningCGROUP FREEZE/RUN. See the next section for examples.

Example output for CQUERY

The following examples show output for CQUERY - PATHS/VOLUMES afterCGROUP FREEZE has run. Output is for illustration only; do not use.

CQUERY - PATHS

The following figure shows example output when CQUERY is issued to aprimary system to which CGROUP/FREEZE was issued.

The following figure shows example output when CQUERY is issued to thesecondary system that has a blocked path due to the CGROUP/FREEZEcommand.


CQUERY - VOLUME

The following figure provides example output when CQUERY is issued to an P-VOL that has been split by CGROUP/FREEZE. The output also shows the statusof the FREEZE option: CGRPLB(YES) = enabled, CGRPLB(NO) = disabled.

Note: The values for WWNN and LIC LEVEL in this figure and the next areinvalid. Do not use the values.

The following figure provides example output when CQUERY is issued to an S-VOL with an P-VOL has been split by the CGROUP/FREEZE command. The pairstatus and path status at the secondary system are not changed.


IEA494I and IEA491E console messagesWhen a pair is split, whether user-requested or caused by failure, the primarysystem generates sense information to notify the hosts. If the PPRC ERP PTFis installed and PPRC support by host = Yes is selected on the DeviceManager - Storage Navigator Change CU Options window, this notificationresults in an IEA494I system console message and an IEA491E message. TheIEA491E message indicates the reason for the split. The IEA494I andIEA491E messages are generated by the zSeries and S/390 host based uponSSBs (sense bytes) from the storage system and not SIMs from the storagesystem. Therefore, SIMs reported by the storage system to the host are notused by the GDPS scripting.

The IEA494I message is recommended as a trigger for automation over theIEA491E message. The IEA491E message is reported to only one hostsystem, whereas the IEA494I message is reported to all attached MVS hostseach time the P-VOL pair status changes. GDPS uses the IEA494I messagewith extended long busy as a trigger for CGROUP (FREEZE/RUN).

If you have specified PPRC support by host = No, the host generates thesystem console message that includes the SIM instead of the IEA494I orIEA491E message.

IEA494I messageWhen a TCz pair status changes, with the exception of the transition statessuspending and deleting, the primary system reports state change interrupt(SCI) to all hosts. In response to the SCI, the IEA494I system consolemessage is generated (if supported by the host). VSP G1000 reports SCI forboth online and offline devices, but the host system does not generateconsole messages for offline devices. Therefore, the IEA494I message isnever generated with an S-VOL device address.

• The primary system reports SCI for all P-VOLs that are in the SCP statedue to the CGROUP/FREEZE command. The following example shows anIEA494I message indicating the extended long busy state:


IEA494I 0FC3,RD0FC3,PPRC PAIR SUSPENDING,SSID=0FC0,CCA=03,EXTENDED LONG BUSY STATE

• The primary system reports SCI for all P-VOLs that are split due to theCGROUP/FREEZE command. This IEA494I message indicates theextended long busy state.

• When the FREEZE option is enabled, the primary system reports SCI for apair that is split due to a failure. When the host supports GDPS, thisIEA494I message with extended long busy triggers the CGROUP (FREEZE/RUN) command.

IEA491E messageWhen a pair is split due to a failure, the primary system reports SCI and unitcheck status and sense bytes with F/M = FB. In response to the F/M=FBsense bytes, the IEA491E system console message is generated (if supportedby the host). The following is an example of an IEA491E message:

IEA491E DSLFC0,PPRC SUSPENDED, SECONDARY NOT READY,INTERVENTION_REQUIRED,(PRI)SER=0113-90797,CCA=00(SEC)SER=0113-90217,CCA=If the host supports GDPS and the FREEZE option is enabled, the IEA494Isystem console message with extended long busy (which was generated inresponse to the SCI) triggers the CGROUP (FREEZE/RUN) command.

VSP G1000 response characteristics to failure conditionsVSP G1000 supports CGROUP in the GDPS environment by performing PPRCcompatible actions and returning PPRC compatible messages according tofailure conditions.

In Device Manager - Storage Navigator's Change CU Options window, PPRCsupport by host =, must be enabled (Yes). If it is disabled (No), the hostprocessor generates a system console message that includes the SIM insteadof the IEA494I or IEA491E message.

The following figure shows failure conditions, with corresponding VSP G1000response characteristics in the table following the figure.


Failure condition Pairs split? Expected messages FREEZEfunction

1. Failure of all channelinterfaces on the primarysystem

No No IEA480E, IEA491E, or IEA494Imessages display.

Not activated1

2. Failure ofa disk on theprimarysystem

Failure ofone physicaldisk in aparity group

No (1) IEA480E message (SIM for blockedphysical disk or disk's port) displays whenthe next I/O is issued to any volume inthe parity group.(2) No IEA491E or IEA494I messagesdisplay.

Not activated1

Failure oftwo physicaldisks in aparity group

No (1) IEA480E message (SIM for blockedLDEV) displays when the next I/O isissued to any volume in the parity group.(2) No IEA491E or IEA494I messagesdisplay.

Not activated2

3. Failure of a link betweenthe primary and secondarysystem

No (1) IEA480E message (SIM for blockedTCz path) is reported when the next I/Oto any device in this primary system isissued.(2) No IEA491E or IEA494I messagesdisplay.

Not activated

4. Failure ofNVS on theprimarysystem;failure ofprimarysystem readcache

One side ofprimarysystemcacheblocked dueto failure

No3 (1) IEA480E (SIM for cache blocked) isreported when the next I/O to any devicein this primary system is issued.(2) No IEA491E or IEA494I messagesdisplay.

Not activated

One side ofprimarysystemcacheblocked due

No3 No IEA480E, IEA491E, or IEA494Imessages display.

Not activated



tomaintenance

One side ofprimarysystemcacheblocked bySET CACHEOFF

No3 No IEA480E, IEA491E, or IEA494Imessages display.

Not activated

5. Both sides of primarysystem cache blocked dueto failure

No No IEA480E, IEA491E, or IEA494Imessages display. The primary systemreturns CC=3 for all I/Os.

Not activated

6. Failure ofa disk on thesecondarysystem

Failure of adisk in aparity group

No (1) The secondary system reportsIEA480E message (SIM for blocked diskor disk's port) to either the primarysystem or the host processor (whicheverissues the next I/O first) when the nextI/O is issued to any volume in the paritygroup. If primary system receives theSIM, it passes the SIM to the attachedhost processor, and the IEA480Emessage is reported when the next I/O tothis primary system is issued to any P-VOL paired with the volume in the paritygroup.(2) No IEA491E or IEA494I messagesdisplay.

Not activated

Failure oftwo disks ina paritygroup

Yes (1) The secondary system reportsIEA480E message (SIM for LDEV blocked)to either the primary system or the hostprocessor (whichever issues the next I/Ofirst) when the next I/O is issued to anyvolume in the parity group. If primarysystem receives the SIM, it passes theSIM to the attached host processor, andthe IEA480E message is reported whenthe next I/O to this primary system isissued to any P-VOL paired with thevolume in the parity group.(2) One or more IEA494I messageshowing EXTENDED LONG BUSY display.(3) One or more IEA491E or IEA494Imessage showing PAIR SUSPENDEDdisplay.

Activated if theFREEZE optionis enabled forthe affectedprimary systempairs.

7. Failure ofNVS on thesecondarysystem;failure ofsecondarysystem readcache

One side ofsecondarysystemcacheblocked dueto failure

No (1) The secondary system reports IEA480message (SIM for cache blocked) toeither the primary system or the hostprocessor (whichever issues the next I/Ofirst). If primary system receives the SIM,it passes the SIM to the attached hostprocessor. Therefore, IEA480 is reportedwhen the next I/O to any device in this

Not activated



primary system issued. (2) No IEA491Eor IEA494I messages display.

One side ofsecondarysystemcacheblocked duetomaintenance

No No IEA480, IEA491E, or IEA494Imessages display.

Not activated

One side ofsecondarysystemcacheblocked bySET CACHEOFF


Not activated

8. Both sides of secondarysystem cache blocked dueto failure

Yes (1) No IEA480 (SIM for blocked cache)displays.(2) One or more IEA494I messageshowing EXTENDED LONG BUSY display.(3) One (or more) IEA491E and IEA494Imessages showing PAIR SUSPENDEDdisplay.(4) If CGROUP FREEZE and RUN areissued, IEA494I messages showing PAIRSUSPENDED display when the primarysystem accepts CGROUP RUN. Thesemessages are from the TCz pairs forwhich FREEZE option is enabled, andfrom main volumes that did not alreadyreport IEA491E/IEA494I at (3).


9. Failure of all linksbetween the primary andsecondary system

Yes (1) IEA480 (SIM for TCz path blocked)message is reported when the next I/O toany device in this primary system isissued.(2) One or more IEA494I messageshowing EXTENDED LONG BUSY display.(3) One or more IEA491E or IEA494Imessage showing PAIR SUSPENDEDdisplay.


10. Powerfailure

a. On theprimarysystem


Not activated

b. On thesecondarysystem

Yes (1) IEA480 (SIM for blocked TCz path)message is reported when the next I/O toany device in this primary system isissued.(2) One or more IEA494I messageshowing EXTENDED LONG BUSY display.




(3) One or more IEA491E or IEA494Imessage showing PAIR SUSPENDEDdisplay.

1. Because of the nature of the failure, there is no means of activating the FREEZE feature.2. FREEZE is not activated, though activation is possible with the relevant command.3. When one side of the primary system cache is blocked, TCz pairs in Duplex status are not affected,

but Pending Duplex pairs are split. Splitting pairs in Pending Duplex status provides additionalprotection against unexpected events caused by cache failure.

GDPS and TrueCopy for Mainframe features

The following table shows GDPS and TCz features supported by IBM3990-6E,VSP G1000, and VSP.

Note: The information shown may not be current. Please contact your HitachiData Systems Support Center for the latest GDPS TCz matrix information.

Feature IBM 3990 6E VSP G1000 VSP

GDPS

Planned outage Supported Supported Supported

Unplanned outage usingIEA494I

Supported Supported Supported

IEA494I Long Busymessage

Default time of 120 secfor FREEZE after IEA494Imessage is issued.

Default time for FREEZEis 120 seconds. Therange for this option is 0to 518,400 seconds (144hours) after IEA494Imessage is issued.

Default time for FREEZEis 120 seconds. Therange for this option is 0to 518,400 seconds (144hours) after IEA494Imessage is issued.

Peer-to-Peer RemoteCopy

PPRC TCz TCz

Hardware based 3990-6 to 3990-6 VSP G1000, VSP, andUSP V/VM to VSP G1000,VSP and USP V/VM.

VSP G1000, VSP, USPV/VM, and TagmaStoreUSP/TagmaStore NSC toVSP G1000, VSP, USPV/VM and TagmaStoreUSP/TagmaStore NSC.

Interface betweenstorage systems

ESCON – max of 43 kmcommunication usingchannel extenders

Communication usingswitch and extenderusing Fibre Channel andFibre Channel cable

Communication usingswitch and extenderusing Fibre Channel andFibre Channel cable

Copy modes supported Synchronous Synchronous Synchronous

Dual Copy combinationsupport

Supported Not Supported. DualCopy is not supported bystorage system.

Not Supported. DualCopy is not supported bystorage system.



TSO command Support Supported Supported. Someadditional options onlyavailable using DeviceManager - StorageNavigator/SVP.

Supported. Someadditional options onlyavailable using DeviceManager - StorageNavigator/SVP.

ICKDSF commandsupport

Supported Supported. Someadditional options onlyavailable using DeviceManager - StorageNavigator/SVP.

Supported. Someadditional options onlyavailable using DeviceManager - StorageNavigator/SVP.

P/DAS support Supported Supported Supported

Maximum pairs 64 65,280 32,768

Maximum paths betweenstorage systems

4 8 per logical control unit 8 per logical control unit

Number of copyoperations on initial copy

4 Default is 4 per CU.Requires Device Manager- Storage Navigator tochange value in rangefrom 1 to 16.

Default is 4 per CU.Requires Device Manager- Storage Navigator tochange value in rangefrom 1 to 16.

Dedicated interfacebetween storagesystems

No Requires main storagesystem port to be set totarget by DeviceManager - StorageNavigator (or SVP) orautomatically inresponse to establishand delete pathcommands.

Requires main storagesystem port to be set totarget by DeviceManager - StorageNavigator (or SVP) orautomatically inresponse to establishand delete pathcommands.

PACE parameter initialcopy option

1-255, default is 15(setting of 1 copies amaximum of 3 tracks ata time, 2-255 copies amaximum of 15 tracks ata time)

3 or 15, default = 15tracks

3 or 15, default = 15tracks

CRITICAL pair erroroptions (Fence Levelparameter)

Yes No – Default S-VOL Data Never –Default S-VOL Status

S-VOL Data Never –Default S-VOL Status

CGROUP FREEZE/RUN by logicalcontroller SSID pair

FREEZE/RUN by logicalcontroller SSID pair.

FREEZE/RUN by logicalcontroller SSID pair.

CQUERY Supported Supported. Supported.

TCz Unique Features specified using Device Manager - Storage Navigator or SVP only

Remote Connection Options

Minimum paths Not supported Default = 1. If theminimum number ofprimary system-secondary system activepaths falls below this

Default = 1. If theminimum number ofprimary system-secondary system activepaths falls below thisvalue, all pairs will be



value, all pairs will besplit based on thePrimary Volume FenceLevel option in effect.

split based on thePrimary Volume FenceLevel option in effect.

CU Options

PPRC support by host Host must support PPRC Default = YES - PPRCsupported, optionalcapability to allow hostsupport for non PPRCcapable operatingsystems.

Default = YES - PPRCsupported, optionalcapability to allow hostsupport for non PPRCcapable operatingsystems.

Secondary system toprimary system SIMreporting

Not supported per IBMdoc Planning for IBMRemote Copy(SG24-2594-009 p.184)

To any host or only tosecondary system host

To any host or only tosecondary system host

Secondary system toprimary system serviceSIM reporting

Not supported per IBMdoc Planning for IBMRemote Copy(SG24-2594-009 p.184)

Default = Not report;Designed for non-MVSoperating systems thatdo not support SIMreporting.

Default = Not report;Designed for non-MVSoperating systems thatdo not support SIMreporting.

Pair Options

CFW Data Not supported Optional to S-VOL,default = PrimaryVolume Only

Optional to S-VOL,default = only M-VOL

Max. volumes 256 per storage system 256 per CU 256 per CU

SIM/error messages Per IBM doc Per IBM doc Per IBM doc

Local storage systeminterface

Parallel or ESCON FICON FICON

Remote storage systeminterface

Parallel or ESCON FICON FICON

Channel extendersupport

Yes Contact your HitachiData Systems SupportCenter.

Contact your HitachiData Systems SupportCenter.


BTCz CLI reference

This appendix provides commands and options for command line userinterfaces and the Device Manager - Storage Navigator gui.

Commands and options for configuring, operating, monitoring, andmaintaining TrueCopy for Mainframe pairs, and for working with consistencygroups, are provided for HDvM - SN, CCI, BCM, and PPRC.

□ Configuration commands and options

□ Pair operation commands and options

□ Monitoring commands and options

□ Maintenance commands and options

TCz CLI reference B-1Hitachi TrueCopy® for Mainframe User Guide

Configuration commands and optionsThe following table shows the commands and options for configuring TCz.

For information about CCI commands, see the Hitachi Command ControlInterface Command Reference.

Operation OptionAvail. inHDvM -

SN?

CCIcommand and options

BCM1

commandPPRC2

command and options

Edit Ports PortAttribute

Yes raidcom modify port-port_attribute portattribute

none none

Add RemoteConnection

ConnectionType

Yes none none none

RemoteStorageSystem

Yes raidcom add rcu-rcu serial# mcu# rcu# id

YKBLDPTH CESTPATH

[Specify by serial#]3

PRIM(mssid#, mserial#,mcu#) SEC(rssid#,rserial#, rcu#)

[Specify by WWNN]4

PRIM(mssid#, mwwnn#,mcu#) SEC(rssid#,rwwnn#, rcu#)

RemotePaths

Yes raidcom add rcu-cu_free serial# id pid

YKBLDPTH CESTPATH

[Specify by serial#]5

LINK(x'abccddee',x'abccddee' …)

[Specify by WWNN]6

LINK(x'ccccdddd',x'ccccdddd' …)

RIO MIHTime

Yes raidcom modify rcu-rcu_option mpth rtortt[fzd|fze]

none none

Edit RemoteReplicaOptions

Copy Type Yes none none none

MaximumInitial CopyActivities

Yes none none none

ServicesSIM ofRemoteCopy

Yes none none none

PPRCsupport

Yes none none CESTPATHnonePPRC:"Yes"other than PPRC:"No"

B-2 TCz CLI referenceHitachi TrueCopy® for Mainframe User Guide


SN?

CCIcommand and options

BCM1

commandPPRC2

command and options

PathBlockadeWatch

Yes none none none

Edit SCPTime

None Yes none none none

1. There are no BCM attribute definitions nor options for configuration commands.2. TSO command/ICKDSF command.3. mssid#: SSID# of CU to which primary volume belongs, mserial#: Serial number of Local Storage

System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondary volume belongs,rserial#: Serial# of Remote Storage System, rcu#: CU# of secondary volume

4. mssid#: SSID# of CU to which primary volume belongs, mwwnn#: WWNN(World Wide Nord Name)of Local Storage System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondaryvolume belongs, rwwnn#: WWNN(World Wide Nord Name) of Remote Storage System, rcu#: CU# ofsecondary volume

5. a: Controller ID, b: "0" fixed, cc: Initiator Port, dd: RCU Target Port, ee: Secondary volume CU#6. cc: Initiator Port, dd: RCU Target Port

Pair operation commands and optionsThe following table shows the commands and options for performing TCz pairoperations.


SN?

CCIcommand and

options

BCM PPRC*command and

optionscommandand option

definitionattribute

Create TCPairs

Copy Type Yes paircreate-fg -jp

YKMAKEnone

Copy GroupType

CESTPAIRnone

PrimaryVolumeFence Level

Yes paircreate-fg

YKMAKEnone

FENCE LVL CESTPAIRCRIT(yes|no)

Initial CopyType

Yes paircreate-nocopy

YKMAKENOCOPY

none CESTPAIRMODE(copy|nocopy|resync)

Copy Pace Yes paircreate-c

YKMAKEnone

COPY PACE(SLOW/NORMAL)

CESTPAIRnone

Initial CopyPriority

Yes paircreate YKMAKEnone

none none

DifferentialManagement

No paircreate-m

YKMAKEnone

DIF UNIT CESTPAIRnone



SN?

CCIcommand and

options

BCM PPRC*command and

optionscommandand option

definitionattribute

DFW toSecondaryVolume

Yes none YKMAKEnone

none CESTPAIRnone

Host I/OTime StampTransfer

Yes none YKMAKEnone

TIMESTAMP CESTPAIRnone

SecondaryVolumeOnlinepermission

No none YKMAKEONLINE

none CESTPAIR

FREEZE SCP No none YKMAKE FREEZE SCP CESTPATH

Split Pairs SSBtransmission(F/M=FB)

Yes none none none CSUSPENDnone

SecondaryVolumeWrite

Yes pairsplit-rw

YKSUSPNDSVOL({PROTECT|PERMIT})

PROT MODE CSUSPENDnone

Suspend forReverseResync

No none YKSUSPNDREVERSE

none CESTPAIRACTION(failover)

ResyncPairs

PrimaryVolumeFence Level

Yes pairresync-fg

YKRESYNCnone

FENCE LVL CESTPAIRCRIT(yes|no)

Copy Pace Yes pairresync-c

YKRESYNCnone

COPYPACE(SLOW/NORMAL)

CESTPAIRnone

Host I/OTime StampTransfer

Yes none YKRESYNCnone

TIMESTAMP CESTPAIRnone

ReverseResync

No pairresync-restore

YKRESYNCREVERSE

none CESTPAIRACTION(failback)

SecondaryVolumeOnlinepermission

No none YKRESYNCONLINE

none CESTPAIRONLINSEC(no/yes)

SwitchingOPEN CTG/MF CTG

No none YKRESYNCOPENMFUPDATE

none CESTPAIRnone

Delete Pairs Delete Mode Yes pairsplit-S

YKDELETEnone

none CDELPAIRnone

*TSO command/ICKDSF commands


Monitoring commands and optionsThe following table shows the commands and options for viewing TCz pairinformation.

Operation OptionsAvail. inHDvM -

SN?

CCIcommand and

options

BCM1

commandPPRC2

command and options

View PairProperties

none Yes pairdisplay-m mode

YKQUERY CQUERYnone

View PairSynchronousRate


YKQUERY CQUERYnone

View RemoteConnectionProperties


YKQRYDEV CQUERYPATHS

1. There are no BCM attribute definitions nor options for monitoring commands.2. TSO command/ICKDSF command.

Maintenance commands and optionsThe following table shows the commands and options for maintaining TCzpairs.

Note: Maintenance commands and options are not available from CCI.

Operation Option Avail. inHDvM - SN?

BCMcommand

PPRCcommand and options 1

Edit Pair Options CFW Data Yes none none

Edit RemoteConnection Options

RIO MIH Time Yes none none

Add Remote Paths none Yes YKBLDPTH CESTPATH 2

[Specify by serial#] 3

LINK(x'abccddee', x'abccddee' …)

[Specify by WWNN] 4

LINK(x'ccccdddd', x'ccccdddd' …)

Remove Remote Paths none Yes none CESTPATH 5

[Specify by serial#]LINK(x'abccddee', x'abccddee' …)6

[Specify by WWNN]LINK(x'ccccdddd', x'ccccdddd' …)7


Operation Option Avail. inHDvM - SN?

BCMcommand

PPRCcommand and options 1

Remove RemoteConnections

none Yes YKDELPTH CESTPATH[Specify by serial#]PRIM(mssid#, mserial#, mcu#)SEC(rssid#, rserial#, rcu#) 8

[Specify by WWNN]PRIM(mssid# , mwwnn# , mcu#)SEC(rssid#, rwwnn#, rcu#) 9

1. TSO command/ICKDSF commands2. Specify by adding the additional path to the registered logical path.3. a: Machine ID, b: "0" fixed, cc: Initiator Port, dd: RCU Target Port, ee: Secondary volume CU#4. cc: Initiator Port, dd: RCU Target Port5. Specify logical path only to leave.6. a: Controller ID, b: "0" fixed, cc: Initiator Port, dd: RCU Target Port, ee: Secondary volume CU#7. cc: Initiator Port, dd: RCU Target Port8. mssid#: SSID# of CU to which primary volume belongs, mserial#: Serial number of Local Storage

System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondary volume belongs,rserial#: Serial# of Remote Storage System, rcu#: CU# of secondary volume

9. mssid#: SSID# of CU to which primary volume belongs, mwwnn#: WWNN(World Wide Nord Name)of Local Storage System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondaryvolume belongs, rwwnn#: WWNN(World Wide Nord Name) of Remote Storage System, rcu#: CU# ofsecondary volume


CTCz GUI reference

This appendix describes Device Manager - Storage Navigator windows andfields used for TrueCopy for Mainframe. The following key topics are covered:

Important: Procedures in this manual are tailored to the Device Manager -Storage Navigator (HDvM - SN) GUI. When using this GUI, "Local StorageSystem" displays for the system you have accessed on the HDvM - SN server.

As a result, if you access the secondary site's HDvM - SN server, the GUIdisplays information for the pair's remote (secondary) system under "LocalStorage System". Likewise, the GUI in this case identifies the storage systemconnecting to the accessed system as the "Remote Storage System".

However, this manual uses the terms "primary storage system" or "primarysystem" for the storage system in which the primary volume (P-VOL) islocated in the primary site, and "secondary storage system" or "secondarysystem" for the storage system in which the secondary volume (S-VOL) islocated in the secondary site, unless otherwise noted.

□ Replication window

□ Remote Replication window

□ Remote Connections window

□ Add Remote Connection wizard

□ View Remote Connection Properties window

□ Remove Remote Connection window

□ Edit Remote Connection Options wizard

□ Add Remote Paths wizard

TCz GUI reference C-1Hitachi TrueCopy® for Mainframe User Guide

□ Remove Remote Paths wizard

□ Edit Remote Replica Options wizard

□ Edit SCP Time wizard

□ Create Pairs wizard

□ Split Pairs wizard

□ Resync Pairs wizard

□ Delete Pairs wizard

□ Force Delete Pairs (TC Pairs) window

□ Edit Pair Options wizard

□ View Pair Properties (Remote) window

□ View Pair Synchronous Rate window

□ Add SSIDs wizard

□ Remove SSIDs wizard

□ Histories window

C-2 TCz GUI referenceHitachi TrueCopy® for Mainframe User Guide

Replication windowUse this window to view information about pairs and pair volumes.

In this topic, you can view the following tables.

• Summary section on page C-3• Replica LDEVs tab on page C-4

Summary section

Item Description

Licensed Capacity (Used/Licensed)

Used capacity and licensed capacity for each local andremote replication program product.

Number of Replica LDEVs Number of LDEVs used in replication.

Number of FCv2/FCSErelationships

Number of Compatible FlashCopy(R) V2 and CompatibleSoftware for IBM® FlashCopy® SE relationships.

Number of differentialtables

Number of differential tables in use.

View Histories - LocalReplication

Clicking opens the Histories window for local replication.

View Histories - RemoteReplication

Clicking opens the Histories window for remote replication.

Edit Options - LocalReplication

Clicking opens the Edit Local Replica Options window.


Item Description

Edit Options - RemoteReplication

Clicking opens the Edit Remote Replica Options window.

Edit Options - SCP Time Clicking opens the Edit SCP Time window.

Replica LDEVs tab

Item Description

LDEV ID LDEV identifier. Clicking the link opens the LDEV Propertieswindow.

LDEV Name LDEV name.

Emulation Type LDEV's emulation type.

Capacity LDEV's capacity.

Copy Type Copy and volume type of the pair.• SI-L1: ShadowImage L1 pair• SI-L2: ShadowImage L2 pair• SIMF: ShadowImage for Mainframe• TI: Thin Image• FCv2: Compatible FlashCopy® V2• FCSE: Compatible Software for IBM® FlashCopy® SE• TC: TrueCopy• TCMF: TrueCopy for Mainframe• UR: Universal Replicator• URMF: Universal Replicator for Mainframe• GAD: global-active device

Virtual Storage Machine* Information about the LDEV's virtual storage machine andabout the LDEV.• Model type/Serial number: Model type and serial

number.• LDEV ID: Volume's virtual LDEV identifier.• Device Name: Volume's virtual device name, in the

format:virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute- Only attributes that are specified display.- "CVS" displays at the end of the device name, if thevirtual CVS attribute is specified.- A blank indicates no values are specified.

• SSID: Volume's virtual SSID. A blank indicates that novirtual SSID is specified.

Export Clicking opens the window for exporting the tableinformation.


Item Description

* This item does not appear in the window by default. To display this item, change theColumn Settings option for the table.

Remote Replication windowUse this window to view information about remote replication pairs andmirrors (UR/URz only).


• Summary section on page C-5• TC Pairs tab on page C-6• UR Pairs tab on page C-8• Mirrors tab on page C-10• GAD Pairs tab on page C-12

Summary section

Item Description

Number of Pairs Number of pairs for each remote replication product and thetotal of all pairs.

Number of Mirrors UR/URz onlyNumber of open and mainframe mirrors and the total of allmirrors.


TC Pairs tab

Item Description

Local Storage System Information about volumes in the accessed storage system.• LDEV ID: LDEV identifier. Clicking the link opens the

LDEV Properties window.• LDEV Name: LDEV name.• Port ID: Port identifier. TC only.• Host Group Name: Host group name. TC only.• LUN ID: LUN identifier. TC only.• Pair Position: Whether the volume is a primary or

secondary volume.• Provisioning Type1: Volume's provisioning type.• Emulation Type1: Volume's emulation type.• Capacity1: Volume's capacity.• CLPR1: Volume's CLPR.• Encryption1: Encryption information

- Enabled: Encryption of the parity group to which theLDEV belongs is enabled.- Disabled: Encryption of the parity group to which theLDEV belongs is disabled.If LDEV is DP-VOL, external volume, or migrationvolume, a hyphen (-) displays.

• Virtual storage machine1: Virtual storage machine'smodel type and serial number.

• Virtual LDEV ID1: Volume's virtual LDEV identifier.• Virtual Device Name1: Volume's virtual device name, in

the format:virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute- Only attributes that are specified display.- "CVS" displays at the end of the device name, if thevirtual CVS attribute is specified.- A blank indicates no values are specified.

• Virtual SSID1: Volume's virtual SSID. A blank indicatesthat no virtual SSID is specified.

Copy Type • TC: TrueCopy• TCMF: TrueCopy for Mainframe

Status Pair status.For status definitions, see Pair status definitions on page7-3

Remote Storage System Information about volumes in the storage system connectedto the accessed system.• Model / Serial Number: Remote system's model and

serial number.• SSID: Remote system's SSID number. TCz only.


Item Description

• LDEV ID: LDEV identifier.• Port ID: Port identifier when specifying an LDEV ID at

pair creation. Note that this field does not change if theremote system path settings are changed. TC only.

• Host Group Name: Host group name. TC only.• LUN ID: LUN identifier. TC only.• Virtual storage machine1: Virtual storage machine's

model type and serial number.• Virtual LDEV ID1: Volume's virtual LDEV identifier.

Path Group ID Path group identifier.

Update Type1 One of the following:• Sync: It is a TC or TCz pair which is not assigned to

consistency group.• Sync (Specified CTG): It is a TC or TCz pair created by

specifying consistency group.

CTG ID1 Pair's consistency group identifier.

CTG Utilization1 Whether the consistency group is shared by multiplestorage systems.• Single: The consistency group consists of a single pair

of primary and secondary storage systems.• Multi: The consistency group consists of multiple

storage systems.

Preserve Mirror Status1 • Blank: Indicates that it is a Preserve Mirror statuswithout any problem or it is not a Preserve Mirror pair.

• Withdrawn: Indicates that pair volume data does notmatch due to suspending copy of CompatibleFlashCopy® V2.

Fence Level1 Specified P-VOL fence level.

Host I/O Time StampTransfer1

Specified time stamp transfer value.

Create TC Pairs Clicking opens the Create TC Pairs window.

Split Pairs Clicking opens the Split Pairs window.

Resync Pairs Clicking opens the Resync Pairs window.

View Pair SynchronousRate2

Clicking opens the View Pair Synchronous Rate windowwhen the pair's primary system is accessed.

View Pair Properties2 Clicking opens the View Pair Properties window.

View Remote ConnectionProperties2

Clicking opens the View Remote Connection Propertieswindow.

Edit Pair Options2 Clicking opens the Edit Pair Options window.

Delete Pairs2 Clicking opens the Delete Pairs window.


Item Description

Export2 Clicking opens the window for exporting the tableinformation.

1. This item does not appear in the window by default. To display this item, change theColumn Settings option for the table.

2. Displays when you select More Actions.

UR Pairs tab

UR/URz only.

Item Description

Local Storage System Information about volumes in the accessed storage system.• LDEV ID: LDEV identifier. Clicking the link opens the

LDEV Properties window.• LDEV Name: LDEV name.• Port ID: Port identifier. UR only.• Host Group Name: Host group name. UR only.• LUN ID: LUN identifier. UR only.• Pair Position: Whether the volume is a primary or

secondary volume.• Journal ID: Journal identifier.• Mirror ID: Mirror identifier.• Provisioning Type1: Volume's provisioning type.• Emulation Type1: Volume's emulation type.• Capacity1: Volume's capacity.• CLPR1: Volume's CLPR.• Encryption1: Encryption information

- Enabled: Encryption of the parity group to which theLDEV belongs is enabled.- Disabled: Encryption of the parity group to which theLDEV belongs is disabled.If LDEV is DP-VOL, external volume, or migrationvolume, a hyphen (-) displays.

• Virtual storage machine1: Virtual storage machine'smodel type and serial number.

• Virtual LDEV ID1: Volume's virtual LDEV identifier.


Item Description

• Virtual Device Name1: Volume's virtual device name, inthe format:virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute- Only attributes that are specified display.- "CVS" displays at the end of the device name, if thevirtual CVS attribute is specified.- A blank indicates that no values are specified.

• Virtual SSID1: Volume's virtual SSID. A blank indicatesthat no virtual SSID is specified.

Copy Type • UR: Universal Replicator• URMF: Universal Replicator for Mainframe

Status Pair status.

Remote Storage System Information about volumes in the system connected to thesystem you accessed.• Model / Serial Number: Remote system's model and

serial number.• LDEV ID: LDEV identifier.• Port ID: Port identifier. UR only.• Host Group Name: Host group name. UR only.• LUN ID: LUN identifier. UR only.• Journal ID: Journal's identifier.• Virtual storage machine1: Virtual storage machine's

model type and serial number.• Virtual LDEV ID1: Volume's virtual LDEV identifier.


CTG ID1 Consistency group identifier.

Error Level1 The error level.

Create UR Pairs Clicking opens the Create UR Pairs window.

Split Pairs Clicking opens the Split Pairs window.




View Pair Properties2 Clicking opens the View Pair Properties window .



Edit Pair Options2 Clicking opens the Edit Pair Options window.


Split Mirrors2 Clicking opens the Split Mirrors window.


Item Description

Resync Mirrors2 Clicking opens the Resync Mirrors window.

Delete Mirrors2 Clicking opens the Delete Mirrors window.




Mirrors tab

UR/URz only.

Item Description

Journal ID Journal identifier. Clicking opens the Journal Volumeswindow.

Mirror ID Mirror identifier.

Journal Type Journal's copy type and journal type option displays. Ifjournal type is standard, only copy type displays.

Attribute Whether the journal is Master, Restore, or Initial-registeredbut with no pair volumes assigned to it.

Status Mirror status.For mirror descriptions, see Hitachi Universal Replicator forMainframe User Guide.

Remote Storage System • Model / Serial Number: Remote system model andserial number.

• Journal ID: Remote system journal identifier


Number of Data VOLs Number of volumes associated with the mirror.

Data Capacity Total capacity of all the associated volumes.

Remote Command Device LDEV number of the remote command device if it isassigned to the mirror.• The column is blank if the remote command device is

not assigned to the mirror.• A hyphen (-) indicates the remote command device

cannot be assigned to the mirror.


Item Description

CTG ID1 Displays the consistency group ID.

CTG Utilization1 Whether the consistency group is shared by multiplestorage systems.• Single: The consistency group consists of a single pair


storage systems.

EXCTG Setting1 Displays the EXCTG ID and Super DKC (device name andserial number).A hyphen (-) displays when no journal is registered in theEXCTG.

Path Watch Time1 Displays the path watch time.

Path Watch Time Transfer1 Specifies whether to forward the Path Watch Time value ofthe master journal to the secondary mirror. If the PathWatch Time value is forwarded from the master journal tothe secondary mirror, both the primary and secondarymirrors will have the same Path Watch Time value.• Yes: The Path Watch Time value will be forwarded to

the secondary mirror.• No: The Path Watch Time value will not be forwarded to

the secondary mirror.

Copy Pace1 Indicates the speed of initial copy of a volume. Slower,Medium, or Faster is displayed. A hyphen is displayed if thejournal is a restore journal.

Transfer Speed1 Specifies the transfer speed (in Mbps (megabits persecond)). Specify one of the following: 256, 100, or 10.

Delta Resync Failure1 Indicates the processing that must be performed if deltaresync cannot be performed.• Entire Copy: Copies all data in the primary volume to

the secondary volume if delta resync cannot beperformed.

• No Copy: Does not perform any processing if deltaresync cannot be performed. Does not update thesecondary volume.

Split Mirrors Clicking opens the Split Mirrors window.

Resync Mirrors Clicking opens the Resync Mirrors window.

Create UR Pairs Clicking opens the Create UR Pairs window.

Edit Mirror Options2 Clicking opens the Edit Mirror Options window.


Clicking opens the View Remote Connection Propertieswindow when the value for Attribute is "Master".

Delete Mirrors2 Clicking opens the Delete Mirrors window.

Assign Remote CommandDevices2

Clicking opens the Assign Remote Command Deviceswindow.


Item Description

Release Remote CommandDevices2

Clicking opens the Release Remote Command Deviceswindow.




GAD Pairs tab

Item Description

Local Storage System Information about volumes in the Local Storage System.• LDEV ID: LDEV identifier. Clicking the link opens the

LDEV Properties window.• LDEV Name: LDEV name.• Port ID: Port identifier.• Host Group Name: Host group name.• LUN ID: LUN identifier.• Pair Position: Whether the volume is a primary or

secondary volume.• Capacity1: Volume's capacity.• CLPR1: Volume's CLPR.• I/O Mode: Volume's I/O Mode.

Status Pair status.

Failure Factor1 Failure Factor.For failure factors displayed in the Failure Factor columnand their meanings, see the Failure Factors on page C-13.

Remote Storage System Information about volumes in the Remote Storage System.• Model / Serial Number: Remote system's model and

serial number.• LDEV ID: LDEV identifier.• Port ID: Port ID when specifying an LDEV ID at pair

creation. Note that this field does not change if theremote system path settings are changed.

• Host Group Name: Host group name when specifyingan LDEV ID at pair creation. Note that this field does


Item Description

not change even if the remote system path settings arechanged.

• LUN ID: LUN identifier when specifying an LDEV ID atpair creation. Note that this field does not change evenif the remote system path settings are changed.


Mirror ID Mirror identifier.

Quorum Disk ID Quorum Disk identifier.

Virtual Storage Machine Information about the LDEV's virtual storage machine.• Model type/Serial number: Model type and serial

number.• LDEV ID: Volume's virtual LDEV identifier.• Device Name: Volume's virtual device name, in the

format: virtual emulation type/number of virtual LUSEvolumes/virtual CVS attribute.- Only attributes that are specified will display.- "CVS" displays at the end of the device name, if thevirtual CVS attribute is specified.- A blank indicates no values are specified.

• SSID: Volume's virtual SSID. A blank indicates that novirtual SSID is specified.

Create GAD Pairs Clicking opens the Create GAD Pairs window.

Suspend Pairs Clicking opens the Suspend Pairs window.




View Pair Properties2 Clicking opens the View Pair Properties window.







Failure Factors

The following table shows failure factors displayed in the Failure Factorcolumn and their meanings.


Failure Factor Meanings

Local VolumeFailure

A failure is detected on a volume in the local storage system.

Remote PathFailure

A failure is detected on the remote path.

Quorum DiskFailure

A failure is detected on the quorum disk.

Internal Error An internal error is detected.

Not Failure No failure is detected. The pair is suspended when the local storagesystem is turned on.

Remote VolumeFailure

A failure is detected on a volume in the remote storage system.

Remote SideUnidentifiedFailure

A failure due to an unidentified factor is detected on a volume in theremote storage system.

blank cell No failure is detected.

Remote Connections windowUse this window to view information about remote connections and paths,and add additional remote connections and paths.

For complete information and instructions, see Monitoring and maintainingremote connections and paths on page 7-12.

In this topic you can review the following tables:

• View Port Condition on page C-14• Connections (To) tab on page C-15• Connections (From) tab on page C-16• Quorum Disks tab on page C-17

View Port Condition


Item Description

Connections (To) • System: Number of system-to-system connectionsfrom local to remote system.

• CU: Number of CU-to-CU connections from local toremote system.

Remote Storage System Number of remote systems connected to the local system.

Connections (From) • System: Number of system-to-system connectionsfrom remote to local system.

• CU: Number of CU-to-CU connections from remote tolocal system.

Only the number of remote connections used for TC pairsand TCz pairs is displayed as the number of connections.

Quorum Disks Number of Quorum Disk.

View Port Location Clicking opens the View Port Location window.

Connections (To) tab

Use this tab to view information about the remote system.

Item Description

Connection Type • System: system-to-system connection (local toremote).

• CU: CU-to-CU connections (local to remote).

Local CU Local system CU number.

Remote Storage System • Model / Serial Number: Model and serial number.• CU: Remote Storage System's CU number.• SSID: Remote Storage System's SSID number.


Status Remote connection status.• Normal: All remote paths are normal.• Failed: All remote paths are abnormal.• Warning: Some remote paths are abnormal.

Number of Remote Paths Number of remote paths.


Item Description

Minimum Number of Paths1 The specified minimum number of paths.

RIO MIH Time (sec.)1 The specified RIO MIH time in seconds.

Roundtrip Time (msec.)1 The specified roundtrip time in milliseconds.

FREEZE Option1 The specified the FREEZE option.

Add Remote Connection Clicking opens the Add Remote Connection window.

Edit Remote ConnectionOptions

Clicking opens the Edit Remote Connection Options window.

View Remote ConnectionProperties


Add Remote Paths2 Clicking opens the Add Remote Paths window.

Remove Remote Paths2 Clicking opens the Remove Remote Paths window.

Add SSIDs2 Clicking opens the Add SSIDs window.

Delete SSIDs2 Clicking opens the Delete SSIDs window.

Remove RemoteConnection2

Clicking opens the Remove Remote Connection window.



2. Displays when More Actions is clicked.

Connections (From) tab

Use this tab to view information about the remote storage system. Thisinformation is displayed only when remote connections are used for TC andTCz pairs.

Item Description

Connection Type • System: system-to-system connection from remote tolocal.

• CU: CU-to-CU connections from remote to local.



Item Description

Remote Storage System Displays the following regarding the remote system.• Model / Serial Number: Model and serial number.• CU: CU number.• SSID: SSID number.


Export Clicking opens the window for exporting the tableinformation.

Quorum Disks tab

Use this tab to view information about the Quorum Disks allocated to users.

Item Description

Quorum Disk ID Quorum Disk identifier.

Quorum Disk Information about Quorum Disk.• LDEV ID: Volume's virtual LDEV identifier.

LDEV Property window displays by clicking LDEVID.

• LDEV Name: Volume's LDEV Name.• Status: Displays the volume status.

¢ Normal: Volume is in normal status.¢ Blocked: Volume is blocked. Access cannot

be made from the host.¢ Warning: Volume has a problem.¢ Formatting: Volume is being formatted.¢ Preparing Quick Format: Preparation for

quick formatting is in progress.¢ Quick Formatting: Volume is under quick

formatting.¢ Correction Access: Access attribute is being

corrected.¢ Copying: Volume data is being copied.¢ Read Only: Volume is in Read Only status.

Data cannot be written.


Item Description¢ Shredding: Volume is being shredded.¢ - : A blank indicates that the volume is in a

status other than the above.• CLPR: Volume's CLPR.• Capacity: Volume's capacity.

Remote Storage System Model/Serial number of Remote Storage System.

Add Quorum Disks Clicking opens the window for adding Quorum Disks.

Remove Quorum Disks Clicking opens the window for removing QuorumDisks.

Export Clicking opens the window for exporting tableinformation.

Add Remote Connection wizardUse this wizard to set up storage systems for replication.

Add Remote Connection windowUse this window to connect storage systems for remote replication.

For complete information and instructions, see Adding remote connection onpage 5-3.



• Local Storage System on page C-19• Remote Storage System on page C-19• Remote Paths on page C-20• Options on page C-20

Item Description

Connection Type • System: system-to-system connection. TC/UR/URz/GAD.

• CU: CU-to-CU connections. TCz only.

Local Storage System

Item Description

Model Local model.

Serial Number Local serial number.

Local CU TCz only.Local system CU number. Displays when Connection Type isCU.

Remote Storage System

Item Description

Model Remote system's model.

Serial Number Last five or six digits of the remote system serial number,as follows:• VSP G1000: 1 to 99999 (5 digits)• VSP or USP V/VM: 1 to 99999 (5 digits)• HUS VM: 200001 to 265535 (6 digits) (TC/UR only)Note: When using CCI (including Raidcom), the VSP G1000serial number requires a prefix of "3".

Remote CU TCz only.Remote system CU number. Displays when Connection Typeis CU.

SSID TCz only.Remote system SSID.

Add SSIDs TCz only.Clicking adds the SSID to the remote system. Themaximum is four.


Remote Paths

Item Description

Path Group ID TC/UR/URz only.Path group identifier. Displays when Connection Type isSystem.

Minimum Number of Paths Minimum number of remote paths.• TC and TCz: Range is from 1 to 8.• UR and URz: The minimum number is 1, regardless of

the number entered.

Port lists • Left side: local port identifier• Right side: remote port identifier

Add Paths Clicking opens a dialog box for creating additional paths(maximum of eight).

Options

Item Description

RIO MIH Time Time limit between 10 and 100 seconds for the data-transfer operation to complete (15 is the default).

Roundtrip Time (msec.) TC/TCz and GAD only.Time limit between 1 and 500 milliseconds for data copyfrom P-VOL to S-VOL (1 is the default).

FREEZE Option TCz only.Enables or disables support for the CGROUP (FREEZE/RUN)PPRC TSO command.


Add Remote Connection confirmation window


• Selected Remote Connection table on page C-21• Selected Remote Paths table on page C-22

Selected Remote Connection table

Item Description

Connection Type System or CU.

Local CU TCz only.Specified local system CU number. Displays whenConnection Type is CU.

Remote Storage System • Model / Serial Number: Model and serial number.• CU: CU number.• SSID: SSID.

Path Group ID Specified path group identifier.

Number of Remote Paths Specified number of remote paths.

Minimum Number of Paths Specified minimum number of remote paths.

RIO MIH Time (sec.) Specified RIO MIH time.

Roundtrip Time (msec.) Specified roundtrip time.

FREEZE Option Specified FREEZE option.


Selected Remote Paths table

Item Description

Local Port ID Local system port identifier.

Remote Port ID Remote system port identifier.

View Remote Connection Properties windowUse this window to view information about remote connections and paths.


• Remote Connection Properties table on page C-23• Remote Paths table on page C-23


Remote Connection Properties table

Item Description

Connection Type • System: system-to-system connection.• CU: CU-to-CU connections.


Remote Storage System • Model / Serial Number: Model and serial number.• CU: CU number.• SSID: SSID.


Channel Type Displays the channel type.• Fibre: Local port type of all remote paths in the remote

connection is Fibre.• FCoE: Local port type of all remote paths in the remote

connection is FCoE.• Mixed: Remote paths with local port types of Fibre and

FCoE both exist in the remote connection.

Status Remote connection status.• Normal: All remote path within remote connection are

fine.• Failed: All remote path within remote connection has

problem.• Warning: Some remote path within remote connection

has problem.

Minimum Number of Paths The specified minimum number of remote paths.

RIO MIH Time The specified RIO MIH time in seconds.

Roundtrip Time The specified roundtrip time in milliseconds.

FREEZE Option Whether the FREEZE option is enabled or disabled.

Registered Time Date and time the connection was established.

Last Update Date Date and time of the last update.

Number of Remote Paths Number of paths specified in the remote connection.

Remote Paths table

Item Description

Local Port ID Remote path's local system port identifier.

Local Port Type Remote path's local port channel type.

Remote Port ID Remote path's remote system port identifier.

Status Remote path status.


Remove Remote Connection windowUse this window to remove remote connections.

For complete information and instructions, see Deleting TrueCopy forMainframe on page 7-20.


Item Description



Remote Storage System Information about the remote system.• Model / Serial Number: Model and serial number.• CU: CU number.• SSID: SSID number. TCz only.

Path Group ID TC only.Path group identifier.

Status Path status.

Number of Remote Paths Number of remote paths including those being added.

Detail Clicking opens the View Remote Connection Propertieswindow.

Edit Remote Connection Options wizardUse this wizard to edit remote connection options.


Edit Remote Connection Options windowUse this window to edit remote connection options, such as minimum pathsand round trip time.

For complete information and instructions, see Changing minimum paths,round trip time, other remote connection options on page 7-16.


Item Description


the number entered.


Roundtrip Time TC/TCz only.Time limit between 1 and 500 milliseconds for data copyfrom P-VOL to S-VOL (1 is the default).

FREEZE Option TCz only.Enables or disables support for the CGROUP (FREEZE/RUN)PPRC TSO command.Displays only when connection type is CU.


Edit Remote Connection confirmation window


Item Description



Remote Storage System Information about the remote system.• Model / Serial Number: Model and serial number.• CU: Remote Storage System's CU number.• SSID: Remote Storage System's SSID number. TCz

only.




the number entered.


Roundtrip Time (msec.) TC/TCz only.Time limit between 1 and 500 milliseconds for data copyfrom P-VOL to S-VOL (1 is the default).

FREEZE Option TCz only.Enables or disables support for the CGROUP (FREEZE/RUN)PPRC TSO command.


Add Remote Paths wizardUse this wizard to add remote paths to a remote connection.

Add Remote Paths windowUse this window to add remote paths to a remote connection.

For complete information and instructions, see Configuring additional remotepaths on page 7-15.


• Local Storage System on page C-27• Remote Storage System on page C-28• Remote Paths on page C-28


Item Description

Model Local system model.

Serial Number Local system serial number.

Local CU Local system CU number.A hyphen displays in case of system connection.



Item Description

Model Remote system model.

Serial Number Remote system serial number.

Remote CU Remote system CU number.A hyphen displays in case of system connection.

SSID Remote system SSID.A hyphen displays in case of system connection.

Remote Paths

Item Description

Path Group ID Path group identifier. A hyphen displays for CU connection.


Port lists • Left side list: local system port identifier.• Right side list: remote system port identifier

Add Paths Clicking adds more paths, up to eight.

Add Remote Paths confirmation window





Item Description








Item Description



Remove Remote Paths wizardUse this wizard to remove paths from a remote connection.

Remove Remote Paths windowUse this window to remove paths from a remote connection.

For complete information and instructions, see Deleting remote paths on page7-17.





Item Description





Item Description



Remote CU Remote system CU number.

SSID Remote system SSID.


Remote Paths

Item Description

Path Group ID Path group identifier. A hyphen displays for CU connection.



Remove Check box for deleting the path from the remoteconnection.

Remove Remote Paths confirmation window




Item Description



Remote Storage System Information about the remote system.• Model / Serial Number: Model and serial number.• CU: CU number.


Item Description

• SSID: SSID number. TCz only.





Item Description



Edit Remote Replica Options wizardUse this wizard to change options that affect the replication system.

Edit Remote Replica Options windowUse this window to change options that affect the replication system.

For complete information and instructions, see Setting number of vols.copied, path blockade, other options on page 5-6.



• Setting Fields on page C-33• Storage System Options on page C-33• CU Options on page C-34

Setting Fields

Item Description

Copy Type Type of pair:• TC: TrueCopy• UR: Universal Replicator• TCMF: TrueCopy for Mainframe• GAD: global-active device• URMF: Universal Replicator for Mainframe

Storage System Options

Following will not be displayed if selecting GAD for Copy Type.


Item Description

Maximum Initial CopyActivities

Number of volumes that can be copied per initial copyoperation.TC/TCMF pair: 1 to 512.UR/URMF pair: 1 to 128

Path Blockade Watch TC/TC only.Number of seconds for the system to monitor blocked paths

Path Blockade SIM Watch TC/TCz only.Number of seconds for the system to monitor SIMs reportedfor blocked paths


TC/TCz only.Whether services SIMs in the remote CU are reported to thehost.

CU Options


Item Description


TC/TCz only.Enables or disables maximum initial copy activities.

CU CU number.


TC/TCz only.Maximum initial copy activities. A hyphen displays if Disableis selected in Maximum Initial Copy Activities.

PPRC Support TCz only.Whether PPRC is supported by the host.

Services SIM Whether remote copy service SIMs are reported to the host.

Change CU Options Clicking opens the Change CU Options window.


Input Maximum Initial Copy Activities between 1 to 512.Displays only if selecting GAD for Copy Type.


Change CU Options window

Item Description


Number of volumes that can be copied per initial copyoperation.

PPRC support by host TCz only.Whether PPRC is supported by the host.


Whether services SIMs in the remote CU are reported to thehost.


Edit Remote Replica Options confirmation window


• Storage System Options on page C-36• CU Options on page C-37

Storage System Options

Item Description


Number of volumes that can be copied per initial copyoperation.

Path Blockade Watch (sec.) TC/TCz only.Number of seconds for the system to monitor blocked paths

Path Blockade SIM Watch(sec.)

TC/TCz only.Number of seconds for the system to monitor SIMs reportedfor blocked paths

Services SIM TC/TCz only.Whether services SIMs are reported to the host.


CU Options


Item Description

CU CU number.


TC/TCz only.Number of volumes that can be copied per initial copyoperation.

PPRC support by host TC/TCz only.Whether PPRC is supported by the host.

Services SIM Whether services SIMs are reported.

Edit SCP Time wizardUse this wizard to edit the SCP time.

Edit SCP Time windowUse this window to edit the SCP time.

For complete information and instructions, see Changing SCP time on page5-8.

Item Description

CU CU number.

SCP Time (sec.) Interval that I/O from the host is suspended. Shared withCompatible FlashCopy® V2.

Change SCP Time Clicking opens the Change SCP Time window.


Change SCP Time window

Item Description

SCP Time The new SCP time. You can specify a value between 0 and518400 (6 days).

Edit SCP Time confirmation window

Item Description

CU CU number.

SCP Time (sec.) New SCP time.

Create Pairs wizardUse this wizard to create pairs.

Create TC Pairs window or Create UR Pairs windowUse this window to create pairs.

For complete information and instructions, see Creating pairs on page 6-3.



• Settings on page C-39• Primary Volume Selection on page C-40• Secondary Volume Selection on page C-40• Mirror Selection on page C-41• Options on page C-41• Selected Pairs table on page C-42

Settings

Item Description

Copy Type Type of pair:• TC: TrueCopy• UR: Universal Replicator• TCMF: TrueCopy for Mainframe• URMF: Universal Replicator for Mainframe

Local CU TCz only.Local system's CU number. You can select the CU numberof the local storage system between [00] and [FE].

Remote Storage System Selections in the remote system.• Model / Serial Number: Model and serial number.• Path Group ID: Select the ID of the path group.

Does not display for TCz.• CU/SSID: CU number and SSID. TCz only.


Item Description

Specify this when you select a provisional CU number inLocal CU.

Primary Volume Selection

Item Description

LU Selection TC and UR only.• Port ID: Local system's port identifier.• Host Group Name: Host group name.

Available LDEVs Information about P-VOLs.• Port ID: Port identifier. TC and UR only.• Host Group Name: Host group name. TC and UR only.• LUN ID: LUN identifier. TC and UR only.• LDEV ID: LDEV identifier.• LDEV Name: LDEV name.• Provisioning Type: Whether the volume is Basic

(internal) or External.• Emulation Type: Emulation type. TC/TCz/URz only.• Capacity: LDEV's capacity.• CLPR: CLPR.• Encryption: Encryption information.

- Enabled: Encryption of the parity group to which theLDEV belongs is enabled.- Disabled: Encryption of the parity group to which theLDEV belongs is disabled.If LDEV is DP-VOL or external volume, a hyphen (-)displays.

Secondary Volume Selection

Item Description

Base Secondary Volume Selections for the initial S-VOL.TC and UR only.• Port ID: Port identifier.• Host Group ID: Host group identifier.• LUN ID: LUN identifier.TCz and URz only.• LDKC: "00" displays, cannot be changed.• CU: For TCz: Volume's CU number.

For URz: the remote system's CU number, ranging from00 to FF.

• LDEV: LDEV number, ranging from 00 to FF.


Item Description

Selection Type • Interval: Interval for allocating S-VOLs.• Relative Primary Volume: S-VOLs paired with P-VOLs

relative to LUN or LDEV numbers.

Mirror Selection

UR and URz only.

Item Description

Master Journal Master journal number and type.

Mirror ID Mirror's identifier.

Restore Journal Restore journal number.

Current Number of MasterJournal Mirrors

Number of mirrors in the master journal.

Total Number of MasterJournal Mirrors

Displays the following:• Number of mirrors in the master journal.• Number of mirrors added during the Create UR Pairs

operation.• Number of mirrors for the selected volume in Selected

Pairs table.

CTG ID UR only.Displays consistency groups registered in the storagesystem. An asterisk indicates it is assigned to a pair in theSelect Pairs table.

Options

Item Description

Primary Volume FenceLevel

TC and TCz onlyWhether the P-VOL can be written to when the pair is splitdue to error.• Data: Cannot be written to.• Status: Can be written to only if the primary system

can change S-VOL status to Suspended; otherwise no.• Never: Can be written to.

Initial Copy Type Whether data is copied to the S-VOL during this operation.• Entire Volume: Data is copied. The default.• None: Data is not copied.• Delta: Data is not copied. UR and URz only.

Copy Pace TC and TCz onlyNumber of tracks to be copied per remote I/O during theoperation.


Item Description

• For TC, the range is 1-15.• TCz options are 3 and 15.

Initial Copy Priority Scheduling order for the initial copy operation. Range is 1 to256; default is 32.

CFW Data TCz only.Whether CFW (DASD fast write) data is copied to the S-VOL.• Primary Volume Only: Data is not copied to S-VOL

(default).• Secondary Volume Copy: Data is copied to S-VOL.

DFW to Secondary Volume TCz only.Whether the primary system splits the pair when thesecondary system cannot copy DFW data to the S-VOL• Require: Splits the pair.• Not Require: Does not split.

Host I/O Time StampTransfer

TCz only.Whether the host I/O time stamp is transferred from P-VOLto S-VOL.

Error Level UR and URz only.Whether to split all pairs in the mirror if a failure occursduring this operation:• Mirror: Pairs in the mirror are split.• LU (UR) or Volume (URz): Only the failed pair is split.

CFW URz only.Whether to copy cache fast write (CFW) data to the S-VOL.• Primary Volume Only: Does not copy. Default.• Secondary Volume Copy: Copies.

Selected Pairs table

Item Description

Local Storage System Information about volumes in the accessed system.• LDEV ID: LDEV identifier.• LDEV Name: LDEV name.• Port ID: Port identifier. TC/UR only.• Host Group Name: Host group name. TC/UR only.• LUN ID: LUN identifier. TC/UR only.• Emulation Type: Volume's emulation type.

TCz/TC/URz only.• Journal ID: Journal's identifier. UR/URz only.• Mirror ID: Mirror identifier. UR/URz only.• Capacity: Volume's capacity.


Item Description

• CLPR: Volume's CLPR.• Encryption: Encryption information


Remote Storage System Information about the remote system.• Model / Serial Number: Model and serial number.• SSID: SSID number. TCz only.• LDEV ID: LDEV identifier. TCz/URz only• Port ID: Port identifier. TC/UR only.• Host Group Name: Host group name. TC/UR only.• LUN ID: LUN identifier. TC/UR only.• Journal ID: Journal's identifier. UR/URz only.

Path Group ID Path group ID. Not used with TCz.

Fence Level TC and TCz only.P-VOL fence level.

CTG ID UR only.Consistency group identifier.

Initial Copy Type Type of the pair create operation.

Copy Pace TC and TCz only.Number of tracks copied per remote I/O operation.

Initial Copy Priority Scheduling order for pair create operation.

CFW Data TCz only.Whether CFW data is copied to the S-VOL.

DFW to Secondary Volume TCz only.Whether the primary system splits pairs when thesecondary system cannot copy DFW data to the S-VOL.


TCz only.Whether the host's time stamp is transferred to the S-VOL.

Error Level UR and URz only.Whether all pairs in the mirror are split if a failure occursduring this operation.

CFW URz only.Whether CFW data is copied to the S-VOL.

Change Settings Clicking opens the Change Settings window.

Delete Deletes the specified pair from the table.


Change Settings windowUse this window in the pair creation wizard to change options that affect howthe pair is created.

Item Description

Base Secondary Volume Selections for the initial S-VOL.TC, UR and GAD only.• Port ID: Port identifier.• Host Group ID: Host group identifier.• LUN ID: LUN identifier.TCz and URz only.• LDKC: "00" displays, cannot be changed.• CU: For TCz: the volume's CU number.

For URz: the remote system's CU number, ranging from00 to FF.

• LDEV: LDEV number, ranging from 00 to FF.• Interval: The interval for allocating S-VOLs to P-VOLs.


TC and TCz onlyWhether the P-VOL can be written to when the pair is splitdue to error.• Data: The P-VOL cannot be written to.• Status: The P-VOL can be written to only if the primary

system can change S-VOL status to PSUE (TrueCopy)or Suspend (TrueCopy for Mainframe); otherwise no.

• Never: The P-VOL can be written to.

Initial Copy Type Whether data is copied to the S-VOL when the pair iscreated.• Entire Volume: Data is copied. The default.• None: Data is not copied. If you choose this option, you

must confirm the data be equal between the P-VOL andS-VOL.

• Delta: Data is not copied. UR and URz only.


Item Description

If the pair is Universal Replicator pair, the status will bechanged to HOLD or LOLDING as a pair for deltaresync. If the pair is the Universal Replicator forMainframe pair, the status will be changed to Hold orHolding as a pair for delta resync.

Copy Pace TC, TCz and GAD only.Number of tracks to be copied per remote I/O during theoperation.• For TC, the range is 1-15.• TCz options are 3 and 15.The default is the value specified in the Create TC Pairswindow.

Initial Copy Priority Scheduling order for the initial copy operation. Range is 1 to256; default is 32. Not displayed for GAD.

CFW Data TCz only.Whether CFW (DASD fast write) data is copied to the S-VOL.• Primary Volume Only: Data not copied (default).• Secondary Volume Copy: Data is copied.

DFW to Secondary Volume TCz only.Whether the primary system splits the pair when thesecondary system cannot copy DFW data to the S-VOL• Require: Splits the pair.• Not Require: Does not split.


TCz only.• Enable: The host I/O time stamp is transferred from P-

VOL to S-VOL (default).• Disable: The host I/O time stamp is not transferred

from P-VOL to S-VOL.Whether the host I/O time stamp is transferred from P-VOLto S-VOL.

Error Level UR and URz only.Whether to split all pairs in the mirror if a failure occursduring this operation:• LU: Only the failed pair is split. UR only.• Mirror: Pairs in the mirror are split.• Volume: Only the failed pair is split.



Create Pairs confirmation window


Item Description

Local Storage System Information about volumes in the accessed system.• LDEV ID: LDEV identifier.• LDEV Name: LDEV name.• Port ID: Port identifier. TC/UR only.• Host Group Name: Host group name. TC/UR only.• LUN ID: LUN identifier. TC/UR only.• Emulation Type: Volume's emulation type.

TCz/TC/URz only.• Journal ID: Journal's identifier. UR/URz only.• Mirror ID: Mirror identifier. UR/URz only.• Capacity: Volume's capacity.• CLPR: Volume's CLPR.• Encryption: Encryption information


Copy Type Type of pair:• TC: TrueCopy


Item Description

• UR: Universal Replicator• TCMF: TrueCopy for Mainframe• URMF: Universal Replicator for Mainframe

Remote Storage System Information about volumes in the system connected to thesystem you accessed.• Model / Serial Number: Model and serial number.• SSID: SSID number. TCz only.• LDEV ID: LDEV identifier. TCz/URz only.• Port ID: Port identifier. TC/UR only.• Host Group Name: Host group name. TC/UR only.• LUN ID: LUN identifier. TC/UR only.• Journal ID: Journal's identifier. UR/URz only.

Path Group ID Path group identifier. Not shown for TCz.

CTG ID UR only.Consistency group identifier.

Fence Level TC and TCz onlyWhether the P-VOL can be written to when the pair is splitdue to error.• Data: Cannot be written to.• Status: Can be written to only if the primary system


Initial Copy Type Whether data is copied to the S-VOL during this operation.• Entire Volume: Data is copied. The default.• None: Data is not copied.• Delta: Data is not copied. UR and URz only.

Copy Pace TC and TCz onlyNumber of tracks to be copied per remote I/O during theoperation.• For TC, the range is 1-15.• TCz options are 3 and 15.

Initial Copy Priority Scheduling order for the initial copy operation. Range is 1 to256; default is 32.

CFW Data TCz only.Whether CFW (DASD fast write) data is copied to the S-VOL.• Primary Volume Only: Data not copied (default).• Secondary Volume Copy: Data is copied.This is displayed only for TCz pairs.

DFW to Secondary Volume TCz only.Whether the primary system splits the pair when thesecondary system cannot copy DFW data to the S-VOL


Item Description

• Require: Splits the pair.• Not Require: Does not split.


TCz only.Whether the host I/O time stamp is transferred from P-VOLto S-VOL.

Error Level UR and URz only.Whether to split all pairs in the mirror if a failure occursduring this operation:• Mirror: Pairs in the mirror are split.• Volume: Only the failed pair is split.


Split Pairs wizardUse this wizard to split pairs.

Split Pairs windowUse this window to split pairs.

For complete information and instructions, see Splitting pairs on page 6-6.


• Selected Pairs table on page C-49• Setting Fields on page C-49



Item Description

Local Storage System Information about volumes in the accessed system.• LDEV ID: LDEV identifier.• LDEV Name: LDEV name.• Pair Position: Whether volume is a P-VOL or S-VOL.• Emulation Type: Volume's emulation type.• Capacity: Volume's capacity.• CLPR: Volume's CLPR.

Copy Type Type of pair:• TC: TrueCopy• TCMF: TrueCopy for Mainframe

Status Pair status.

Remote Storage System Information about the remote system.• Model / Serial Number: Model and serial number.• SSID: SSID number. TCz only.• LDEV ID: LDEV identifier.


CTG ID Pair's consistency group identifier.

CTG Utilization Whether the consistency group is shared by multiplestorage systems.• Single: The consistency group consists of a single pair

of primary and secondary storage systems.• Multi: The consistency group consists: The consistency

group consists of multiple storage systems.

Preserve Mirror Status • Blank: Indicates that it is a Preserve Mirror statuswithout any problem or it is not a Preserve Mirror pair.


Fence Level P-VOL fence level.

Setting Fields

Item Description

Secondary Volume Write TC only.Whether the S-VOL can be written to while the pair is split.• Enable: Can write to S-VOL. Available only when

performing the split operation from the pair's primarystorage system.

• Disable: Prevents writing to S-VOL. Default.


Item Description

Primary Volume Write Whether the P-VOL can be written to while the pair is split.• Depend on Primary Volume Fence Level: Writing to P-

VOL depends on the Primary Volume Fence LevelSetting. Default.

• Disable: Prevents writing to the P-VOL. Available onlywhen performing the split operation from the pair'sprimary storage system.

SSB Transfer (F/M=FB) TCz only.Whether to report SSB (sense byte) to the host. Enable/Disable (the default). Enable is available only whenperforming the split operation from the pair's primarystorage system.

Split Pairs confirmation window


Item Description



Status Pair status.


Item Description

Secondary Volume Write TC only.Whether the S-VOL can be written to while the pair is split.• Enable: Can write to S-VOL.• Disable: Prevents writing to S-VOL. Default.A hyphen displays if performing the split operation from thepair's secondary storage system, regardless of the selectedoption.

Primary Volume Write Whether the P-VOL can be written to while the pair is split.• Depend on Primary Volume Fence Level: Writing to P-

VOL depends on the Primary Volume Fence LevelSetting. Default.

• Disable: Prevents writing to the P-VOL.A hyphen displays if performing the split operation from thepair's secondary storage system, regardless of the selectedoption.

Fence Level P-VOL's fence level setting.

SSB Transfer (F/M=FB) TCz only.Whether to report SSB (sense byte) to the host. Enable/Disable.A hyphen displays if performing the split operation from thepair's secondary storage system, regardless of the selectedoption.






storage systems.



Resync Pairs wizardUse this wizard to resynchronize pairs.


Resync Pairs windowUse this window to resynchronize pairs.

For complete information and instructions, see Resynchronizing pairs on page6-7.


• Selected Pairs table on page C-52• Setting Fields on page C-53


Item Description

Local Storage System Information about volumes in the accessed system.• LDEV ID: LDEV identifier.• LDEV Name: LDEV name.• Emulation Type: Volume's emulation type.• Capacity: Volume's capacity.• CLPR: Volume's CLPR.


Status Pair status.

Copy Priority Order that pairs are resynchronized.


Path Group ID TC only.


Item Description

Path group identifier.




storage systems.




Setting Fields

Item Description


Whether the P-VOL can be written to when the pair is splitdue to error.• Data: The P-VOL cannot be written to.• Status: The P-VOL can be written to only if the primary



Copy Pace Number of tracks to be copied per remote I/O during theoperation.• For TC, the range is 1-15.• TCz options are 3 and 15.


TCz only.• Enable: The host I/O time stamp is transferred from P-

VOL to S-VOL.• Disable: The host I/O time stamp is transferred from P-

VOL to S-VOL.Whether the host I/O time stamp is transferred from P-VOLto S-VOL.


Resync Pairs confirmation window


Item Description



Status Pair status.

Fence Level Whether the P-VOL can be written to when the pair is splitdue to error.• Data: Cannot be written to.• Status: Can be written to only if the primary system


Copy Pace Number of tracks to be copied per remote I/O during theoperation.• For TC, the range is 1-15.• TCz options are 3 and 15.



TCz only.


Item Description

Whether the host I/O time stamp is transferred from P-VOLto S-VOL.






storage systems.



Delete Pairs wizardUse this wizard to delete pairs.

Delete Pairs windowUse this window to delete pairs.

For complete information and instructions, see Deleting pairs on page 6-9.



• Selected Pairs table on page C-56• Settings on page C-57


Item Description



Status Pair status.


Path Group ID TC only.


Item Description

Path group identifier.




storage systems.



Fence Level Whether the P-VOL can be written to when the pair is splitdue to error.• Data: The P-VOL cannot be written to.• Status: The P-VOL can be written to only if the primary



Settings

Item Description

Delete Mode How the pair is deleted.• Normal: Deletes the pair if the primary system can

change both P-VOL and S-VOL to unpaired volumes.Default.

• Force: Deletes the pair even when the primary systemcannot communicate with the secondary system.

• Force (All pairs in the same remote connections):Deletes forcibly all pairs using the same remoteconnection. TCz only.


Delete Pairs confirmation window


Item Description



Status Pair status.

Delete Mode How the pair is deleted.





of primary and secondary storage systems.


Item Description

• Multi: The consistency group consists of multiplestorage systems.




Force Delete Pairs (TC Pairs) windowUse this window to forcibly delete pairs.

For complete information and instructions, see Forcibly deleting pairs on page7-11.

Selected LDEVs table

Item Description

LDEV ID LDEV identifier.

LDEV Name LDEV name.

Emulation Type Emulation type.

Capacity Capacity.

CLPR CLPR number.


Edit Pair Options wizardUse this wizard to change pair options.

Edit Pair Options windowUse this window to change pair options.

For complete information and instructions, see Changing P-VOL Fence Level,CFW Data on page 7-10.

Item Description


Whether the P-VOL can be written to when the pair is splitdue to error.• Data: The P-VOL cannot be written to.• Status: The P-VOL can be written to only if the primary


• Never: The P-VOL can be written to.The value set for the selected pair is the default.

CFW Data TCz only.Whether CFW (DASD fast write) data is copied to the S-VOL.• Primary Volume Only: Data not copied (default).• Secondary Volume Copy: Data is copied.The value set for the selected pair is the default.


Edit Pair Options confirmation window


Item Description




CFW Data TCz only.Whether CFW data is copied to the S-VOL.





Item Description


View Pair Properties (Remote) windowUse this window to view the data related to pairs and their volumes.

For complete information and instructions, see Monitoring pair status, licensecapacity on page 7-2.


• Pair Properties on page C-63• Pair Detail on page C-63


Pair Properties

Item Description

Local StorageSystem box

Displays the following information about the local system.• LDEV ID (LDEV name): P-VOL's LDEV identifier and name, which

displays when you hover the mouse over it.• Number of Paths: Number of data paths between primary and

secondary systems.• Provisioning Type, Encrypted: Local system's volume type and

encryption status.Encryption status is displayed only when the provisioning type isBasic and the volume's encryption is Enabled.

• Emulation Type, Capacity: Local system's emulation type andcapacity.

• Model/Serial number, CLPR: Local system's model, serial number,and CLPR.

Copy Type,Status

Pair's copy type and pair status.

Path Group Pair's path group.If the P-VOL is in the primary storage system, clicking the path groupID (TC) or Remote Paths (TCz) displays the remote path list.

RemoteStorageSystem box

Displays the following information about the remote system.• LDEV ID: S-VOL's LDEV identifier and name, which displays when

you hover the mouse over it.• Port ID/Host Group ID/LUN ID: Port, host group, and LUN

identifiers. Information is useful when specifying an LDEV ID at paircreation. It does not change, even if path settings are changed. TConly.

• Emulation type, Capacity: Remote system's volume emulation typeand capacity.

• Model/Serial number: Remote system's model, serial number.For CU-by-CU connection, SSID is also displayed.

Pair Detail

Item Description

Status Pair's status

Update Type One of the following:• Sync: It is a TC or TCz pair which is not assigned to consistency

group.• Sync (Specified CTG): It is a TC or TCz pair created by specifying

consistency group.

CTG ID Consistency group identifier

CTG Utilization Whether the consistency group is shared by multiple storage systems.• Single: The consistency group consists of a single pair of primary

and secondary storage systems.


Item Description

• Multi: The consistency group consists of multiple storage systems.

Preserve MirrorStatus

TCz only.Preserve Mirror Status.

Fence Level Whether the P-VOL can be written to when the pair is split due to error.• Data: The P-VOL cannot be written to.• Status: The P-VOL cannot be written to only if the primary system

cannot change S-VOL status to PSUE (TrueCopy) or Suspend(TrueCopy for Mainframe); otherwise no.


Host I/O TimeStamp Transfer

TCz only.Specified time stamp transfer value.

SecondaryVolume Written

Whether data can be written (Enabled) or not written (Disabled) to theS-VOL. The pair must be split for Enabled to display.If the volume accessed is an S-VOL and can be written to, Enabled/Received or Enabled/Not Received displays. Indicates whether a writeoperation is received from the host or not.

Copy Pace Speed that data is copied.

Initial CopyPriority

Scheduling order for the initial copy operation.Range is 1 to 256 for TC; 0 to 256 for TCz; default is 32.

Paired Time Date and time pair-creation was completed.

Last UpdateTime

Date and time that the last update was run.

Pair Copy Time Elapsed time for paircreate or pairresync operation.

CFW Data TCz only.Whether CFW data is copied to the S-VOL as specified during paircreation.

DFW toSecondaryVolume

TCz only.Whether the primary system splits the pair when the secondary systemcannot copy DFW data to the S-VOL.

Local StorageSystem

• Virtual storage machine: Virtual storage machine's model type andserial number.

• Virtual LDEV ID: Volume's virtual LDEV identifier.• Virtual Device Name: Volume's virtual device name, in the format:

virtual emulation type/number of virtual LUSE volumes/virtual CVSattribute- Only attributes that are specified display.- "CVS" displays at the end of the device name, if the virtual CVSattribute is specified.- A blank indicates no values are specified.

• Virtual SSID: Volume's virtual SSID. A blank indicates that novirtual SSID is specified.


Item Description

RemoteStorageSystem

• Virtual storage machine: Virtual storage machine's model type andserial number.

• Virtual LDEV ID: Volume's virtual LDEV identifier.

View Pair Synchronous Rate windowUse this window to view the percentage of synchronized data between P-VOLand S-VOL.

For complete information and instructions, see Monitoring TCz pairsynchronous rate on page 7-8.

Pairs table

Item Description

Local Storage System Information about volumes in the local storage system.• LDEV ID: LDEV identifier. Clicking the link opens the

LDEV Properties window.• LDEV Name: LDEV name.• Pair Position: Whether the volume is a primary or

secondary volume.• CLPR: Volume's CLPR.• Virtual storage machine: Virtual storage machine's

model type and serial number.• Virtual LDEV ID: Volume's virtual LDEV identifier.• Virtual Device Name: Volume's virtual device name, in

the format:virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute- Only attributes that are specified display.- "CVS" displays at the end of the device name, if thevirtual CVS attribute is specified.- A blank indicates no values are specified.


Item Description

• Virtual SSID: Volume's virtual SSID. A blank indicatesthat no virtual SSID is specified.

Copy Type TC Pairs tab:• TC: TrueCopy• TCMF: TrueCopy for Mainframe

Status Pair status.For status definitions, see Pair status definitions on page7-3

Synchronous Rate (%) Displays the concordance rate between the volume in theprimary storage system and the volume in the remotesystem. "(queuing)" displays if processing has not started.

Remote Storage System Information about volumes in the system connected to thesystem you accessed.• Model / Serial Number: Remote system's model and

serial number.• SSID: Remote system's SSID number. TCz only.• LDEV ID: LDEV identifier.• Virtual storage machine: Virtual storage machine's

model type and serial number.• Virtual LDEV ID: Volume's virtual LDEV identifier.

Path Group ID Path group identifier. TC only.

Refresh Updates the information.

Add SSIDs wizardUse this wizard to add SSIDs to the remote system.

Add SSIDs windowUse this window to add SSIDs to the remote system.

For complete information and instructions, see Adding, removing SSIDs onthe secondary system on page 7-18.





Item Description





Item Description




SSID Remote system SSID. Range is 0004 to FFFE. Clicking the -(remove) button removes the SSID text box (present whentwo or more valid SSIDs).


Item Description

Add SSIDs Clicking adds the SSID to the remote system. Themaximum is four.

Remote Paths

Item Description

Path Group ID Path group identifier. Always a hyphen displays.



Add SSIDs confirmation window

Item Description

Connection Type CU: Indicates CU-to-CU connections.


Remote Storage System Information about the remote system.• Model / Serial Number: Model and serial number.• CU: CU number.• SSID: SSID number.




Item Description

Minimum Number of Paths Minimum number of remote paths. Range is from 1 to 8.

SSID The SSIDs to be added.

Remove SSIDs wizardUse this wizard to delete SSIDs.

Remove SSIDs windowUse this window to delete SSIDs.

For complete information and instructions, see the procedure in Adding,removing SSIDs on the secondary system on page 7-18.





Item Description





Item Description




SSID Remote system SSID.

Delete Check box for deleting the SSID from the remote system.

Remote Paths

Item Description

Path Group ID Path group identifier. Always a hyphen displays.



Remove SSIDs confirmation window


Item Description






Minimum Number of Paths Minimum number of remote paths. Range is from 1 to 8.

SSID SSID to be deleted.

Histories windowUse this window to review the operations that have been performed on a pair.

For complete information and instructions, see Monitoring TCz operationshistory on page 7-8.


• Settings on page C-72• Histories table on page C-72


Settings

Item Description

Copy Type Type of pair:• TC: TrueCopy• UR: Universal Replicator• TCMF: TrueCopy for Mainframe• URMF: Universal Replicator for Mainframe• GAD: global-active device

Last Updated Date and time of the last update. Displays after Copy Typeis specified.

Page Number Page number. Click the button, turn over the page. Displaysafter Copy Type is specified.

Histories table

Item Description

Date and Time Date and time of the operation.

Local Storage System Information about volumes in the accessed system.• LDEV ID: LDEV identifier.• Provisioning Type: Whether the volume is Basic

(internal) or External.• Pair Position: Whether the volume is a primary or

secondary volume. GAD only.• Journal ID: Journal's identifier. UR/URz only.• Mirror ID: Mirror's identifier. UR/URz only.

Remote Storage System Information about volumes in the system connected to thesystem you accessed.• LDEV ID: LDEV identifier.• Model / Serial Number: Remote Storage System's

model and serial number. GAD only.• Provisioning Type: Whether the volume is Basic

(internal) or External.

EXCTG ID EXCTG identifier.URz only.

Mirror ID Mirror identifier. GAD only.

Quorum Disk ID Quorum Disk identifier. GAD only.

Virtual Storage Machine Information about volumes in the Virtual Storage Machine.GAD only.• Model / Serial Number: Virtual Storage System's model

and serial number.• LDEV ID: Volume's LDEV identifier.

Description Code Description Code. GAD only.


Item Description

Description Describes the operation.

Copy Time Elapsed time for create or resync pairs operation. When theDescription is other than Pair Add Complete or Pair Resync.Complete, a hyphen displays.

Started Start time of create or resync pairs operation. When theDescription is other than Pair Add Complete or Pair Resync.Complete, a hyphen displays.

Export Clicking opens the window for exporting table information.


Glossary

This glossary defines the special terms used in this document. Click the letter links below tonavigate.

#

2DCtwo-data-center. Refers to the primary and secondary sites, or data centers, in whichTrueCopy for Mainframe (TCz) and Universal Replicator for Mainframe (URz) combine toform a remote replication configuration.In a 2DC configuration, data is copied from a TCz primary volume at the primary site tothe URz master journal volume at an intermediate site, then replicated to the URzsecondary volume at the secondary site. Since this configuration side-steps the TCzsecondary volume at the intermediate site, the intermediate site is not considered adata center.

3DCthree-data-center. Refers to the primary, intermediate, and secondary sites, or datacenters, in which TCz and URz combine to form a remote replication configuration. A3DC configuration can also combine three URz sites.In a 3DC configuration, data is copied from a primary site to an intermediate site andthen to a secondary site (3DC cascade configuration), or from a primary site to twosecondary sites (3DC multi-target configuration).

A

alternate pathA secondary path (port, target ID, LUN) to a logical volume, in addition to the primarypath, that is used as a backup in case the primary path fails.

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-1Hitachi TrueCopy® for Mainframe User Guide

arrayAnother name for a RAID storage system.

array groupSee RAID group.

asyncasynchronous

ATTIME suspendA consistency group task in which multiple pairsplit operations are performedsimultaneously at a pre-determined time using BCM or CCI.

audit logFiles that store a history of the operations performed from Device Manager - StorageNavigator and the service processor (SVP), commands that the storage system receivedfrom hosts.

B

base emulation typeEmulation type that is set when drives are installed. Determines the device emulationtypes that can be set in the RAID group.

BCbusiness continuity

BCMBusiness Continuity Manager

bladeA computer module, generally a single circuit board, used mostly in servers.

BLK, blkblock

bmpbitmap

C

C/TSee consistency time (C/T).



cacache

cache logical partition (CLPR)Consists of virtual cache memory that is set up to be allocated to different hosts incontention for cache memory.

capacityThe amount of data storage space available on a physical storage device, usuallymeasured in bytes (MB, GB, TB, etc.).

cascade configurationIn a 3DC cascade configuration for remote replication, data is copied from a primary siteto an intermediate site and then to a secondary site using TrueCopy and UniversalReplicator. See also 3DC.In a ShadowImage for Mainframe cascade configuration, two layers of secondaryvolumes can be defined for a single primary volume. Pairs created in the first andsecond layer are called cascaded pairs.

shared volumeA volume that is being used by more than one replication function. For example, avolume that is the primary volume of a TrueCopy pair and the primary volume of aShadowImage pair is a shared volume.

CCICommand Control Interface

CFWcache fast write

CGSee consistency group (CTG).

CTGSee consistency group (CTG).

CHchannel

channel pathThe communication path between a channel and a control unit. A channel path consistsof the physical channel path and the remote path.

CHAPchallenge handshake authentication protocol

CLcluster



CLIcommand line interface

CLPRcache logical partition

clusterMultiple-storage servers working together to respond to multiple read and writerequests.

command deviceA dedicated logical volume used only by Command Control Interface and BusinessContinuity Manager to interface with the storage system. Can be shared by severalhosts.

configuration definition fileDefines the configuration, parameters, and options of Command Control Interfaceoperations. A text file that defines the connected hosts and the volumes and groupsknown to the Command Control Interface instance.

consistency group (CG, CTG)A group of pairs on which copy operations are performed simultaneously; the pairs'status changes at the same time. See also extended consistency group (EXCTG).

consistency time (C/T)Shows a time stamp to indicate how close the target volume is to the source volume.C/T also shows the time stamp of a journal and extended consistency group.

controllerThe component in a storage system that manages all storage functions. It is analogousto a computer and contains a processors, I/O devices, RAM, power supplies, coolingfans, and other sub-components as needed to support the operation of the storagesystem.

copy-after-writePoint-in-time snapshot copy of a data volume within a storage system. Copy-after-writesnapshots only store changed data blocks, therefore the amount of storage capacityrequired for each copy is substantially smaller than the source volume.

copy pairA pair of volumes in which one volume contains original data and the other volumecontains the copy of the original. Copy operations can be synchronous or asynchronous,and the volumes of the copy pair can be located in the same storage system (localcopy) or in different storage systems (remote copy).A copy pair can also be called a volume pair, or just pair.

CTGSee consistency group (CTG).



CTLcontroller

CUcontrol unit

currency of dataThe synchronization of the volumes in a copy pair. When the data on the secondaryvolume (S-VOL) is identical to the data on the primary volume (P-VOL), the data on theS-VOL is current. When the data on the S-VOL is not identical to the data on the P-VOL,the data on the S-VOL is not current.

CYL, cylcylinder

cylinder bitmapIndicates the differential data (updated by write I/Os) in a volume of a split orsuspended copy pair. The primary and secondary volumes each have their own cylinderbitmap. When the pair is resynchronized, the cylinder bitmaps are merged, and thedifferential data is copied to the secondary volume.

D

DASDdirect-access storage device

data consistencyWhen the data on the secondary volume is identical to the data on the primary volume.

data pathThe physical paths used by primary storage systems to communicate with secondarystorage systems in a remote replication environment.

data poolOne or more logical volumes designated to temporarily store original data. When asnapshot is taken of a primary volume, the data pool is used if a data block in theprimary volume is to be updated. The original snapshot of the volume is maintained bystoring the to-be-changed data blocks in the data pool.

DBdatabase

DBMSdatabase management system



delta resyncA disaster recovery solution in which TrueCopy and Universal Replicator systems areconfigured to provide a quick recovery using only differential data stored at anintermediate site.

deviceA physical or logical unit with a specific function.

device emulationIndicates the type of logical volume. Mainframe device emulation types provide logicalvolumes of fixed size, called logical volume images (LVIs), which contain EBCDIC datain CKD format. Typical mainframe device emulation types include 3390-9 and 3390-M.Open-systems device emulation types provide logical volumes of variable size, calledlogical units (LUs), that contain ASCII data in FBA format. The typical open-systemsdevice emulation type is OPEN-V.

DEVNdevice number

DFWDASD fast write

DHCPdynamic host configuration protocol

differential dataChanged data in the primary volume not yet reflected in the copy.

disaster recoveryA set of procedures to recover critical application data and processing after a disaster orother failure.

disk arrayDisk array, or just array, is another name for a RAID storage system.

disk controller (DKC)The hardware component that manages front-end and back-end storage operations. Theterm DKC is sometimes used to refer to the entire RAID storage system.

DKCdisk controller. Can refer to the RAID storage system or the controller components.

DKCMAINdisk controller main. Refers to the microcode for the RAID storage system.

DKPdisk processor. Refers to the microprocessors on the back-end director features of theUniversal Storage Platform V/VM.



DKUdisk unit. Refers to the cabinet (floor model) or rack-mounted hardware component thatcontains data drives and no controller components.

DMPDynamic Multi Pathing

DRUHitachi Data Retention Utility

DP-VOLDynamic Provisioning for Mainframe-virtual volume. A virtual volume with no memoryspace used by Dynamic Provisioning for Mainframe.

dynamic provisioningAn approach to managing storage. Instead of "reserving" a fixed amount of storage, itremoves capacity from the available pool when data is actually written to disk. Alsocalled thin provisioning.

E

ECerror code

emulationThe operation of the Hitachi RAID storage system to emulate the characteristics of adifferent storage system. For device emulation the mainframe host "sees" the logicaldevices on the RAID storage system as 3390-x devices. For controller emulation themainframe host "sees" the control units (CUs) on the RAID storage system as I-2107controllers.RAID storage system operates the same as the storage system being emulated.

emulation groupA set of device emulation types that can be intermixed within a RAID group and treatedas a group.

env.environment

ERCerror reporting communications

ESCONEnterprise System Connection



EXGexternal volume group

ext.external

external applicationA software module that is used by a storage system but runs on a separate platform.

external portA fibre-channel port that is configured to be connected to an external storage systemfor Universal Volume Manager operations.

external volumeA logical volume whose data resides on drives that are physically located outside theHitachi storage system.

F

failbackThe process of switching operations from the secondary path or host back to theprimary path or host, after the primary path or host has recovered from failure. Seealso failover.

failoverThe process of switching operations from the primary path or host to a secondary pathor host when the primary path or host fails.

FCfibre channel; FlashCopy

FICONFibre Connectivity

free capacityThe amount of storage space (in bytes) that is available for use by the host system(s).

FSWfibre switch

FTPfile-transfer protocol



G

GIDgroup ID

GUIgraphical user interface

H

HAhigh availability

HACMPHigh Availability Cluster Multi-Processing

HDPHitachi Dynamic Provisioning software

HDSHitachi Data Systems

H-LUNhost logical unit

HORCHitachi Open Remote Copy. Another name for Hitachi TrueCopy.

HORCMHitachi Open Remote Copy Manager. Another name for Command Control Interface.

host failoverThe process of switching operations from one host to another host when the primaryhost fails.

host groupA group of hosts of the same operating system platform.

host modeOperational modes that provide enhanced compatibility with supported host platforms.Used with fibre-channel ports on RAID storage systems.

host mode optionAdditional options for fibre-channel ports on RAID storage systems. Provide enhancedfunctionality for host software and middleware.



HRpMHitachi Replication Manager

HURHitachi Universal Replicator

I

IMPLinitial microprogram load

initial copyAn initial copy operation is performed when a copy pair is created. Data on the primaryvolume is copied to the secondary volume.

initiator portA fibre-channel port which connects to RCU Target port. Initiator port cannotcommunicate with host port.

in-system replicationThe original data volume and its copy are located in the same storage system.ShadowImage in-system replication provides duplication of logical volumes; Thin Imageprovides "snapshots" of logical volumes that are stored and managed as virtual volumes(V-VOLs).

intermediate site (I-site)A site that functions as both a TrueCopy secondary site and a Universal Replicatorprimary site in a 3-data-center (3DC) cascading configuration.

internal volumeA logical volume whose data resides on drives that are physically located within thestorage system. See also external volume.

IO, I/Oinput/output

IOPSI/Os per second

J

JNLjournal



journalIn a Universal Replicator system, journals manage data consistency between multipleprimary volumes and secondary volumes. See also consistency group (CTG).

journal volumeA volume that records and stores a log of all events that take place in another volume.In the event of a system crash, the journal volume logs are used to restore lost dataand maintain data integrity.In Universal Replicator, differential data is held in journal volumes until it is copied tothe S-VOL.

L

L1 pairSee layer-1 (L1) pair.

L2 pairSee layer-2 (L2) pair.

LANlocal-area network

layer-1 (L1) pairIn a ShadowImage cascade configuration, a layer-1 pair consists of a primary volumeand secondary volume in the first cascade layer. An L1 primary volume can be pairedwith up to three L1 secondary volumes. See also cascade configuration.

layer-2 (L2) pairIn a ShadowImage cascade configuration, a layer-2 (L2) pair consists of a primaryvolume and secondary volume in the second cascade layer. An L2 primary volume canbe paired with up to two L2 secondary volumes. See also cascade configuration.

LBAlogical block address

LCPlocal control port; link control processor

LCUlogical control unit

LDEVlogical device

LDKCSee logical disk controller (LDKC).



leaf volumeA level-2 secondary volume in a ShadowImage cascade configuration. The primaryvolume of a layer-2 pair is called a node volume. See also cascade configuration.

LEDlight-emitting diode

license keyA specific set of characters that unlocks an application and allows it to be used.

local copySee in-system replication.

local storage systemThe storage system which Hitachi Device Manager - Storage Navigator client isconnected.

logical device (LDEV)An individual logical data volume (on multiple drives in a RAID configuration) in thestorage system. An LDEV may or may not contain any data and may or may not bedefined to any hosts. Each LDEV has a unique identifier or "address" within the storagesystem composed of the logical disk controller (LDKC) number, control unit (CU)number, and LDEV number. The LDEV IDs within a storage system do not change. AnLDEV formatted for use by mainframe hosts is called a logical volume image (LVI). AnLDEV formatted for use by open-system hosts is called a logical unit (LU).

logical disk controller (LDKC)A group of 255 control unit (CU) images in the RAID storage system that is controlledby a virtual (logical) storage system within the single physical storage system.

logical unit (LU)A logical volume that is configured for use by open-systems hosts (for example, OPEN-V).

logical unit (LU) pathThe path between an open-systems host and a logical unit.

logical volumeSee volume.

logical volume image (LVI)A logical volume that is configured for use by mainframe hosts (for example, 3390-9).

LUlogical unit

LUNlogical unit number



LUNMHitachi LUN Manager

LVlogical volume

M

master journal (M-JNL)Holds differential data on the primary Universal Replicator system until it is copied tothe restore journal (R-JNL) on the remote system. See also restore journal (R-JNL).

Mb/sec, Mbpsmegabits per second

MB/sec, MBpsmegabytes per second

MF, M/Fmainframe

MIHmissing interrupt handler

mirrorIn Universal Replicator, each pair relationship in and between journals is called a"mirror". Each pair is assigned a mirror ID when it is created. The mirror ID identifiesindividual pair relationships between journals.

M-JNLmaster journal

MPmicroprocessor

MP bladeBlade containing an I/O processor. Performance in the storage system is tuned byallocating a specific MP blade to each I/O-related resource (LDEV, external volume, orjournal). Specific blades are allocated, or the storage system can automatically select ablade.

mto, MTOmainframe-to-open

MUmirror unit



multi-pathingA performance and fault-tolerant technique that uses more than one physicalconnection between the storage system and host system. Also called multipath I/O.

N

node volumeA level-2 primary volume in a ShadowImage cascade configuration. The secondaryvolume of a layer-2 pair is called a leaf volume. See also cascade configuration.

NVSnonvolatile storage

O

Open/MF consistency groupConsistency group that uses Business Continuity Manager's Open/MF consistencymaintenance function. Open/MF consistency groups include open-system consistencygroups created with CCI and mainframe-system consistency groups created with BCM.You can split or resynchronize TC and TCz pairs in open/MF consistency groupssimultaneously.

OPEN-VA logical unit (LU) of user-defined size that is formatted for use by open-systems hosts.

OPEN-xA logical unit (LU) of fixed size (for example, OPEN-3 or OPEN-9) that is used primarilyfor sharing data between mainframe and open-systems hosts using Hitachi Cross-OSFile Exchange.

P

pairTwo logical volumes in a replication relationship in which one volume contains originaldata to be copied and the other volume contains the copy of the original data. The copyoperations can be synchronous or asynchronous, and the pair volumes can be located inthe same storage system (in-system replication) or in different storage systems(remote replication).

pair statusIndicates the condition of a copy pair. A pair must have a specific status for specificoperations. When an operation completes, the status of the pair changes to the newstatus.



parity groupSee RAID group.

path failoverThe ability of a host to switch from using the primary path to a logical volume to thesecondary path to the volume when the primary path fails. Path failover ensurescontinuous host access to the volume in the event the primary path fails.See also alternate path and failback.

physical deviceSee device.

pinned trackA track that cannot be read or written to because of failure.

PiTpoint-in-time

point-in-time (PiT) copyA copy or snapshot of a volume or set of volumes at a specific point in time. A point-in-time copy can be used for backup or mirroring application to run concurrently with thesystem.

poolA set of volumes that are reserved for storing Thin Image data, or Dynamic Provisioningwrite data.

pool volume (pool-VOL)A logical volume that is reserved for storing snapshot data for Thin Image operations, orwrite data for Dynamic Provisioning.

port attributeIndicates the type of fibre-channel port: target, RCU target, or initiator.

port blockA group of four fibre-channel ports that have the same port mode.

port modeThe operational mode of a fibre-channel port. The three port modes for fibre-channelports on the Hitachi RAID storage systems are standard, high-speed, and initiator/external MIX.

PPRCPeer-to-Peer Remote Copy

Preview listThe list of requested operations on Device Manager - Storage Navigator.



primary siteThe site which executes operation (application) in normal case.

primary volumeThe volume in a copy pair that contains the original data to be replicated. The data inthe primary volume is duplicated synchronously or asynchronously on the secondarypairs.The following Hitachi products use the term P-VOL: Device Manager - StorageNavigator, Thin Image, ShadowImage, ShadowImage for Mainframe, TrueCopy,TrueCopy for Mainframe, Universal Replicator, and Universal Replicator for Mainframe.See also secondary volume (S-VOL).

P-siteprimary site

P-VOLSee primary volume.

Q

quick formatThe quick format feature in Virtual LVI/Virtual LUN in which the formatting of theinternal volumes is done in the background. This allows system configuration (such asdefining a path or creating a TrueCopy pair) before the formatting is completed. Toexecute quick formatting, the volumes must be in blocked status.

quick restoreA reverse resynchronization in which no data is actually copied: the primary andsecondary volumes are swapped.

quick splitA split operation in which the pair becomes split immediately before the differential datais copied to the secondary volume (S-VOL). Any remaining differential data is copied tothe S-VOL in the background. The benefit is that the S-VOL becomes immediatelyavailable for read and write I/O.

R

R/W, r/wread/write

RAIDredundant array of inexpensive disks



RAID groupA redundant array of inexpensive drives (RAID) that have the same capacity and aretreated as one group for data storage and recovery. A RAID group contains both userdata and parity information, which allows the user data to be accessed in the event thatone or more of the drives within the RAID group are not available. The RAID level of aRAID group determines the number of data drives and parity drives and how the data is"striped" across the drives. For RAID1, user data is duplicated within the RAID group, sothere is no parity data for RAID1 RAID groups.A RAID group can also be called an array group or a parity group.

RAID levelThe type of RAID implementation. RAID levels include RAID0, RAID1, RAID2, RAID3,RAID4, RAID5 and RAID6.

RCPremote control port

RCU target portA fibre-channel port which connects to Initiator port. RCU Target port can alsocommunicate with host port.

remote control port (RCP)A serial-channel (ESCON) port on a TrueCopy main control unit (MCU) that is configuredto send remote I/Os to a TrueCopy remote control unit (RCU).

remote copy connectionsThe physical paths that connect a storage system at the primary site to a storagesystem at the secondary site. Also called data path.

remote replicationData replication configuration in which the storage system that contains the originaldata is at a primary site and the storage system that contains the copy of the originaldata is at a secondary site. TrueCopy and Universal Replicator provide remotereplication. See also in-system replication.

remote storage systemThe storage system which is connected to local storage system.

restore journal (R-JNL)Holds differential data on the secondary Universal Replicator system until it is copied tothe secondary volume.

resync"Resync" is short for resynchronize.

RIOremote I/O



R-JNLrestore journal

root volumeA level-1 primary volume in a ShadowImage cascade configuration. The secondaryvolume of a layer-1 pair is called a node volume. See also cascade configuration.

RPOrecovery point objective

R-SIMremote service information message

RTCreal-time clock

RTOrecovery time objective

R/Wread/write

S

S/N, SNserial number

secondary siteThe site which executes operation (application) after switching from primary site in caseof failure.

secondary volumeThe volume in a copy pair that is the copy. The following Hitachi products use the term"secondary volume": Device Manager - Storage Navigator, Thin Image, ShadowImage,ShadowImage for Mainframe, TrueCopy, TrueCopy for Mainframe, Universal Replicator,and Universal Replicator for Mainframe.See also primary volume.

service information message (SIM)SIMs are generated by a RAID storage system when it detects an error or servicerequirement. SIMs are reported to hosts and displayed on Device Manager - StorageNavigator.



service processor (SVP)The computer inside a RAID storage system that hosts the Device Manager - StorageNavigator software and is used by service personnel for configuration and maintenanceof the storage system.

severity levelApplies to service information messages (SIMs) and Device Manager - StorageNavigator error codes.

SIHitachi ShadowImage

SIzHitachi ShadowImage for Mainframe

sidefileAn area of cache memory that is used to store updated data for later integration intothe copied data.

SIMservice information message

sizeGenerally refers to the storage capacity of a memory module or cache. Not usually usedfor storage of data on disk or flash drives.

SMshared memory

SMTPsimple mail transfer protocol

snapshotA point-in-time virtual copy of a Thin Image primary volume (P-VOL). The snapshot ismaintained when the P-VOL is updated by storing pre-update data (snapshot data) in adata pool.

SNMPsimple network management protocol

SOMsystem option mode

SSBsense byte



SSID(storage) subsystem identifier. SSIDs are used as an additional way to identify a controlunit on mainframe operating systems. Each group of 64 or 256 volumes requires oneSSID, therefore there can be one or four SSIDs per CU image. For VSP G1000, oneSSID is associated with 256 volumes.

SSLsecure socket layer

steady splitIn ShadowImage, a typical pair split operation in which any remaining differential datafrom the P-VOL is copied to the S-VOL and then the pair is split.

S-VOLSee secondary volume.

SVPSee service processor (SVP).

syncsynchronous

system option mode (SOM)Additional operational parameters for the RAID storage systems that enable the storagesystem to be tailored to unique customer operating requirements. SOMs are set on theservice processor.

T

target portA fibre-channel port that is configured to receive and process host I/Os.

TBterabyte

TCHitachi TrueCopy

TCzHitachi TrueCopy for Mainframe

TIDtarget ID

total capacityThe aggregate amount of storage space in a data storage system.



U

update copyAn operation that copies differential data on the primary volume of a copy pair to thesecondary volume. Update copy operations are performed in response to write I/Os onthe primary volume after the initial copy operation is completed.

URHitachi Universal Replicator

URzHitachi Universal Replicator for Mainframe

USPHitachi TagmaStore® Universal Storage Platform

USP/NSCHitachi TagmaStore® Universal Storage Platform and Hitachi TagmaStore® NetworkStorage Controller

USP V/VMHitachi Universal Storage Platform V/VM

USP VMHitachi Universal Storage Platform VM

V

Vversion; variable length and de-blocking (mainframe record format)

VBvariable length and blocking (mainframe record format)

virtual device (VDEV)A group of logical devices (LDEVs) in a RAID group. A VDEV typically consists of somefixed volumes (FVs) and some free space. The number of fixed volumes is determinedby the RAID level and device emulation type.

Virtual LVI/LUN volumeA custom-size volume whose size is defined by the user using Virtual LVI/Virtual LUN.Also called a custom volume (CV).



virtual volume (V-VOL)The secondary volume in a Thin Image pair. In PAIR status, the V-VOL is an up-to-datevirtual copy of the primary volume (P-VOL). In SPLIT status, the V-VOL points to data inthe P-VOL and to replaced data in the pool, maintaining the point-in-time copy of the P-VOL at the time of the split operation.When a V-VOL is used with Dynamic Provisioning, it is called a DP-VOL.

VLLHitachi Virtual LVI/LUN

VLVIHitachi Virtual LVI

VMvolume migration; volume manager

VOL, volvolume

volservolume serial number

volumeA logical device (LDEV) that has been defined to one or more hosts as a single datastorage unit. A mainframe volume is called a logical volume image (LVI), and an open-systems volume is called a logical unit. (LU).

volume pairSee copy pair.

V-VOLvirtual volume

V-VOL management areaContains the pool management block and pool association information for Thin Image,Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, andDynamic Tiering for Mainframe operations. The V-VOL management area is createdautomatically when additional shared memory is installed and is required for theprogram product operations.



Index

A

additional shared memory 3-2

B

bandwidth 3-26Basic HyperSwap 2-16bitmap areas 3-14Business Continuity Manager

about 1-6command device for 2-5commands compared with PPRC 2-8specifications for 2-4

C

cache memory changes, and pair status 3-3, 7-5cache planning considerations 3-2cache requirement 3-2CCI

description 1-6troubleshooting 10-7

CESTPATH/YKBLDPTH, SAID values for 2-9CGROUP (FREEZE/RUN) support A-7CGROUP command A-9consistency groups

description 1-5planning 3-17requirements 3-19

creating multiple pairs, assigning S-VOLs 6-3creating pairs 6-3

D

DASD fast write, planning considerations 3-3data path

description 1-5planning 3-26supported configurations 3-27

delete mode, setting 6-10deleting pairs 6-9DFW to Secondary Volume, setting 6-5differential data, planning 3-14disaster recovery 9-2duplicate VOLSERS, handling 3-12Dynamic Provisioning for Mainframe, sharingvolumes with 4-5

E

error codes 10-2Error reporting communications (ERC)

about 1-7planning 3-25

exporting pair information 7-12external port 3-31

F

F/M=FB message 2-6failover software

about 1-6failure conditions and PPRC A-14Fence Level

details 3-13fence level

Index-1Hitachi TrueCopy® for Mainframe User Guide

changing 7-10fence level, setting 6-5Fibre Channel requirements 3-26file and database recovery 9-3FREEZE option, changing 7-16FREEZE option, setting 5-6

G

GDPS feature comparison for storage systems A-18

H

history of operations for a pair 7-8hosts supported 2-2

I

IEA494I and IEA491E console messages A-13IEA494I message 9-3initial copy

about 1-7scheduling multiple 5-6

initial copy priority, setting 6-5interfaces 1-6

L

logical pathsrequirements 2-3

M

maximum initial copy activities, setting 5-7migrating data 8-2minimum number of paths, changing 7-16minimum number of paths, setting 5-4monitoring status 7-2

N

non-volatile storage (NVS), planningconsiderations 3-2

O

operations history, monitoring 7-8overview 1-1

P

P/DAS 2-12pair operations

with PPRC A-1pair status

changing cache or shared memory 3-3, 7-5definitions 7-3monitoring 7-2with CGROUP operations A-9

pairscalculating maximum supported 3-14creating 6-3deleting 6-9forcibly deleting 7-11general information 1-5planning 3-9requirements, recommendations 3-10resynchronizing 6-7suspending 6-6synchronization rate 7-8

Performance Monitor, sharing volumes with 4-6performance, planning for 3-5port attributes 3-31port requirements 3-30ports

defining attributes 5-2planning 3-30

power-off, managing 7-22PPRC

about 1-6commands A-1commands compared with BCM 2-8Fibre Link information 2-13operations performed with 2-6pair operations with A-1specifications, restrictions 2-6TSO commands with CGROUP A-10

primary volume write, setting 6-7primary vs secondary storage systems 1-1, C-1


Q

QUIESCE option 9-3

R

RAID levels supported 2-2remote path status, troubleshooting 10-3remote path, description 1-5remote paths

defining 5-3deleting 7-17monitoring 7-12status definitions 7-14

remote paths, changing minimum number of 7-16removing TCz 7-20required licenses 2-2required SN role for operations 5-2resynchronizing pairs 6-7RIO MIH 5-6RIO MIH time, setting 5-6RIO MIH, changing 7-16RMF 2-13round trip time, changing 7-16round trip time, setting 5-4

S

S-VOL Read option 3-3S-VOL, planning I/O for 3-12SAID values 2-9saving pair information 7-12scheduling order for initial copies 5-6ShadowImage for Mainframe, sharing volumes 4-7shared memory changes, and pair status 3-3, 7-5sharing volumes 4-2SIMs 10-18split types 7-5SSB Transfer (F/M=FB), setting 6-7SSIDs, adding and deleting 7-18Storage Navigator

description 1-6storage systems

configuring 5-3failure conditions and PPRC A-14planning 3-2powering-off 7-22using an earlier model 3-3

suspended pairs, troubleshooting 10-5switching operations to secondary site 9-4synchronous rate, monitoring 7-8system options, planning 3-3system requirements 2-2

T

target port 3-31technical support 10-19timestamp option 2-19TPC-R

planning for 2-16troubleshooting 10-18unregistered error with 10-19

transfer operations to primary site 9-6troubleshooting remote paths 10-3TrueCopy for Mainframe

components 1-3consistency groups 3-17copy operations described 1-7data path planning 3-26disaster recovery 9-2maximum pairs 3-14overview 1-1pair operations 6-2pair requirements,recommendations 3-10ports for 3-30preparing the storage system for 3-2requirements 2-2setup 5-2sharing volumes 4-2typical environment 1-4using to migrate data 8-2

TSO, ICKDSF commands A-2

U

Universal Replicator for Mainframe, sharingvolumes with 4-9update copy 1-8

V

Virtual LVI 4-10VOLSERS, handling duplicate 3-12Volume Migration 4-10volumes, sharing with others 4-2


W

wait time, changing 7-16


Hitachi TrueCopy® for Mainframe User Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

MK-92RD8018-02

hitachi virtual storage platform g1000 · aix, as/400, db2, domino, ds6000, ... 7-1 monitoring pair...

Documents