emc srdf host component for z/os - dell · emc corporation corporate headquarters: hopkinton, ma...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® SRDF® Host Component for z/OSVersion 7.0

Product GuideP/N 300-007-862

REV A02

EMC SRDF Host Component for z/OS Product Guide2

Copyright © 2001- 2009 EMC Corporation. All rights reserved.

Published April, 2009

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC SRDF Host Component for z/OS Product Guide 3

The EMC SRDF Host Component for z/OS Product Guide is for use with the following products:

◆ SRDF/Synchronous (SRDF/S)

◆ SRDF/Asynchronous (SRDF/A)

◆ SRDF/Data Mobility (SRDF/DM)

◆ SRDF/Automated Replication (SRDF/AR)

◆ SRDF/Consistency Groups (SRDF/CG)

◆ SRDF/Star

DocumentCoverage

4 EMC SRDF Host Component for z/OS Product Guide

Document Coverage


Preface

Chapter 1 OverviewMainframe Enablers and SRDF Host Component ....................... 22

Activating SRDF/Host Component ........................................22Introduction to SRDF Host Component ........................................ 23SRDF Host Component features..................................................... 25

Automation..................................................................................25Security.........................................................................................25ISPF interface...............................................................................26Multitasking and messages.......................................................27Command queueing...................................................................28Commands executed by queue name......................................29RDF groups and data replication .............................................30Synchronization direction .........................................................31Support for unequal size R1 and R2 ........................................33Using metadata ...........................................................................33Remote Symmetrix query and configuration .........................34Command completion status checking ..................................34Consistency group support .......................................................34SRDF/S and consistency groups..............................................35Defined groups ...........................................................................36Batch utility..................................................................................36Extended address volumes .......................................................36Virtualized RAID architecture..................................................37Multiple SRDF/A groups per Symmetrix ..............................39Concurrent SRDF/S with SRDF/A..........................................40Dynamic RDF ..............................................................................40Movement of SRDF pairs ..........................................................41

Contents


Contents

SRDF/S – SRDF/A mode change ............................................ 41SRDF/A tunable cache .............................................................. 42SRDF/A Reserve Capacity........................................................ 42SRDF Automated Recovery ...................................................... 45SRDF/A last applied cycle age................................................. 46Consistency exempt option....................................................... 47Concurrent SRDF........................................................................ 48Cascaded SRDF........................................................................... 50SRDF/Extended Distance Protection ...................................... 53SRDF/Star support .................................................................... 55EMC TimeFinder option............................................................ 64

Chapter 2 Getting StartedUsing SRDF Host Component ........................................................ 66Installing SRDF Host Component.................................................. 67Creating the configuration file........................................................ 68

Specifying defined groups ........................................................ 68Rules for group definitions ....................................................... 68Examples of group definitions ................................................. 70

Starting SRDF Host Component..................................................... 85Stopping SRDF Host Component ............................................ 85

Chapter 3 ConfigurationInitialization parameters.................................................................. 89ALIAS ................................................................................................. 93ALLOW_CRPAIR_NOCOPY.......................................................... 95COMMAND_DETAILS ................................................................... 96COMMAND_PREFIX ...................................................................... 97EXCLUDE_CUU ............................................................................... 99EXCLUDE_DEVICE_RANGE ...................................................... 100EXCLUDE_SYM.............................................................................. 102EXCLUDE_VOL.............................................................................. 103FBA_ENABLE ................................................................................. 105FILTER_KNOWN ........................................................................... 106FILTER_ONLINE............................................................................ 107FILTER_R1 ....................................................................................... 108FILTER_R2 ....................................................................................... 109GROUP_END.................................................................................. 110GROUP_NAME ............................................................................... 111GROUP_SORT_BY_VOLSER........................................................ 112GROUP_SORT_BY_MVSCUU...................................................... 113

7EMC SRDF Host Component for z/OS Product Guide

Contents

HCLOG............................................................................................. 114INCLUDE_CUU .............................................................................. 115INCLUDE_RAG .............................................................................. 116INCLUDE_VOL............................................................................... 117INIT_VOLSER ................................................................................. 119LOGONLY_FOR_TRACKED_COMMANDS ............................. 120MAX_ALIAS ................................................................................... 121MAX_COMMANDQ...................................................................... 122MAX_QUERY .................................................................................. 123MESSAGE_LABELS........................................................................ 124MESSAGE_PROCESSING ............................................................. 125MSC_ACTIVATE_MS ..................................................................... 126MSC_ALLOW_INCONSISTENT.................................................. 127MSC_CYCLE_TARGET.................................................................. 128MSC_GROUP_END........................................................................ 129MSC_GROUP_NAME.................................................................... 130MSC_INCLUDE_SESSION............................................................ 131MSC_STAR....................................................................................... 136MSC_VALIDATION ....................................................................... 137MSC_WEIGHT_FACTOR .............................................................. 138OPERATOR_VERIFY...................................................................... 140REGISTER_COMMAND_PREFIX................................................ 142SAF_CLASS...................................................................................... 144SAF_PROFILE.................................................................................. 145SECURITY_CONFIG ...................................................................... 148SECURITY_QUERY ........................................................................ 149SHOW_COMMAND_SEQ# .......................................................... 150SINGLE_CONCURRENT .............................................................. 151SMFREC............................................................................................ 152SORT_BY_COMMAND ................................................................. 153SORT_BY_MVSCUU ...................................................................... 154SORT_BY_VOLSER......................................................................... 155SRDFA_AUTO_RECOVER............................................................ 156SRDFA_AUTO_RECOVER_BCV.................................................. 157SRDFA_AUTO_RECOVER_ITRK................................................. 158SRDFA_AUTO_RECOVER_MINDIR .......................................... 159SRDFA_AUTO_RECOVER_PROC............................................... 160SUBSYSTEM_NAME...................................................................... 161SYNCH_DIRECTION_ALLOWED .............................................. 162SYNCH_DIRECTION_INIT .......................................................... 163USER_VERIFICATION .................................................................. 164USER_VERIFICATION_TIMEOUT.............................................. 165VONOFF_BLOCKED ..................................................................... 166


Contents

VONOFF_OFF_ONLY ................................................................... 167VONOFF_ON_ONLY..................................................................... 168VONOFF_R1_ONLY ...................................................................... 169VONOFF_R2_ONLY ...................................................................... 170VONOFF_STATUS_WAIT............................................................. 171

Chapter 4 Command ReferenceIntroduction..................................................................................... 175Conventions..................................................................................... 176Getting help ..................................................................................... 177

#HELP ....................................................................................... 177Common parameters...................................................................... 178#SQ ADC.......................................................................................... 180#SQ CNFG ....................................................................................... 184#SQ DSTAT ...................................................................................... 190#SQ GLOBAL .................................................................................. 196#SQ LINK......................................................................................... 200#SQ MIRROR................................................................................... 208#SQ MSG.......................................................................................... 217#SQ RAID......................................................................................... 220#SQ RAID5....................................................................................... 223#SQ RAID6....................................................................................... 227#SQ RAID10..................................................................................... 231#SQ RDFGRP................................................................................... 234#SQ SRDFA ...................................................................................... 242#SQ SRDFA_DSE ............................................................................ 262#SQ SRDFA_VOL............................................................................ 270#SQ SSID .......................................................................................... 276#SQ STATE....................................................................................... 278#SQ VOL .......................................................................................... 285#SC CNFG........................................................................................ 299#SC GLOBAL................................................................................... 301#SC LINK ......................................................................................... 305#SC MSG .......................................................................................... 306#SC RDFGRP ................................................................................... 307#SC RECOVER ................................................................................ 315#SC SRDFA ...................................................................................... 316#SC SRDFA_DSE............................................................................. 320#SC VOL........................................................................................... 324#STOP ............................................................................................... 362#TF .................................................................................................... 363


Contents

Chapter 5 SRDF OperationsConfiguring SRDF operations ....................................................... 366

Suspending SRDF for a single address ..................................366Suspending SRDF for a range of addresses ..........................366Resuming SRDF for a single device .......................................366Resuming SRDF for a range of devices..................................367Resuming SRDF for a range of devices in a concurrent environment...............................................................................367Changing status to ready.........................................................367Changing status to read only ..................................................368Changing status to read/write ...............................................368

Performing operations using a multihop list .............................. 369Querying devices ......................................................................370Changing devices to adaptive copy disk mode....................370RDF-suspending devices .........................................................370Changing R2 devices to R/W..................................................370

Resetting TNR status for an R1 device......................................... 371Performing a personality swap (non-Cascaded SRDF) ............. 375

Personality swap for Cascaded SRDF operations ................377Creating a dynamic RDF pair ....................................................... 378Creating an RDF group .................................................................. 385Modifying an RDF group............................................................... 388Performing Cascaded SRDF operations ...................................... 390Performing Cascaded SRDF operations (diskless)..................... 394Moving dynamic SRDF pairs ........................................................ 402Performing recovery in a diskless environment......................... 408

Scenario 1 ...................................................................................408Scenario 2 ...................................................................................417

Chapter 6 Recovery ProceduresGetting started ................................................................................. 428

Resuming SRDF/A operation.................................................428Recovering using operational host ............................................... 429

Making the operational site available ....................................429When non-operational site becomes available .....................430

Recovery procedure concepts and testing ................................... 432SRDF command syntax considerations .................................433Examples ....................................................................................433Conventions...............................................................................434

Procedure 1: R2 read/write testing .............................................. 435Presynchronization procedure R1<R2 ...................................438

Procedure 2: Synchronization method selection......................... 440


Contents

Procedure 3: R1>R2 full volume resynchronization ................. 443Procedure 4: R1<R2 full volume resynchronization ................. 446Procedure 5: R1>R2 changed tracks resynchronization............ 449Procedure 6: R1<R2 changed tracks resynchronization ........... 451SRDF/A recovery scenarios.......................................................... 454

Temporary link loss ................................................................. 454Permanent link loss .................................................................. 454Primary Symmetrix cache “full” condition .......................... 455Failback from R2....................................................................... 455

SRDF/A MSC recovery scenario.................................................. 456SRDF/A MSC is deactivated or dropped ............................. 456

SRDF/A MSC and SRDF/Star recovery considerations .......... 458Utility recovery requirements................................................. 459Possible MSC group recovery cases ...................................... 461SCFRDFME report output....................................................... 470

SRDF Automated Recovery .......................................................... 473Recovery automation tasks ..................................................... 473Tracking the automated recovery process............................ 474Environment and system requirements................................ 475Restrictions ................................................................................ 475User interface ............................................................................ 475SRDF Automated Recovery procedure ................................. 476Resuming after an auto recovery failure............................... 478

Appendix A SC VOL Command Device FilteringPhase 1 filtering - determining devices for processing ............. 484

Filtering rules ........................................................................... 484Phase 1 complete ..................................................................... 485Comments................................................................................. 485

Phase 2 filtering - validating devices ........................................... 486Comments................................................................................. 486

Device processing ........................................................................... 487

Appendix B Batch InterfaceIntroduction..................................................................................... 490

Details......................................................................................... 490Example............................................................................................ 493

Appendix C Director and Volume StatusRemote link director and the host ................................................ 496SRDF volume statuses and the host............................................. 497


Contents

Appendix D EnhancementsSRDF Host Component enhancements........................................ 500

Index


Contents


Title Page

1 SRDF bidirectional configuration ................................................................ 232 Initial state of RAID-1 device with SRDF ................................................... 373 Synchronizing the RAID-5 group ................................................................ 384 RAID-5 group with SRDF ............................................................................. 385 Initial concurrent SRDF configuration ........................................................ 496 Cascaded SRDF configuration...................................................................... 507 SRDF/EDP configuration ............................................................................. 538 Concurrent SRDF/Star configuration ......................................................... 569 Cascaded SRDF/Star configuration ............................................................ 5710 Concurrent R22 SRDF/Star environment................................................... 5911 Cascaded R22 SRDF/Star environment...................................................... 6012 Cascaded SRDF/Star EDP (diskless) environment with an R2 site ....... 6113 Cascaded SRDF/Star EDP (diskless) environment with an R22 site ..... 6214 SRDF Host Component operational steps.................................................. 6615 #SQ LINK extended command output for SRDF .................................... 20316 #SQ LINK command output for SRDF ..................................................... 20617 #SQ SRDFA command issued to the primary side ................................. 24518 #SQ SRDFA command secondary side ..................................................... 25319 #SQ SRDFA_DSE - primary side output................................................... 26320 #SQ SRDFA_DSE - one pool draining from primary side ..................... 26721 #SQ SRDFA_DSE - secondary side output ............................................... 26822 #SQ SRDFA_DSE - secondary side output with DSE active and MSC 26923 #SQ SRDFA_VOL command primary side .............................................. 27224 #SQ SRDFA_VOL command secondary side........................................... 27325 #SQ RDFGRP command output for SRDF ............................................... 31126 #SQ RDFGRP command output for SRDF ............................................... 31227 R22 device implementation ........................................................................ 36128 SRDF multihop configuration .................................................................... 36929 R1 device range after RDF-SUSP action.................................................... 37130 R2 device range prior to procedure ........................................................... 372

Figures


Figures

Title Page

31 Status of R1 devices after the procedure................................................... 37332 Status of R2 devices after the procedure................................................... 37433 R2 read/write testing .................................................................................. 43734 Synchronization method............................................................................. 44235 R1>R2 full volume resynchronization ...................................................... 44536 R1<R2 full volume resynchronization ...................................................... 44837 R1>R2 changed tracks resynchronization ............................................... 45038 R1<R2 changed tracks resynchronization ............................................... 45339 #SQ SRDFA command issued to the secondary side.............................. 45940 Batch cleanup utility RPTOUT for case 1 from primary side ................ 46441 Batch cleanup utility RPTOUT for case 1 from secondary side ............ 46542 Batch cleanup utility RPTOUT for case 2 from primary side ................ 46643 Batch cleanup utility RPTOUT for case 2 from secondary side ............ 46744 Batch cleanup utility RPTOUT for case 3 from primary side ................ 46845 Batch cleanup utility RPTOUT for case 3 from secondary side ............ 469


Title Page

1 Data modes allowed for Cascaded RDF ...................................................... 512 Initialization parameters ................................................................................ 903 SRDF Host Component commands/suffixes............................................ 1454 Common command parameters ................................................................. 1785 Source is configured for LINKS-DOMINO=Yes; target=No .................. 1886 Source is configured for LINKS-DOMINO=Yes; target=Yes ................. 1887 Source is configured for LINKS-DOMINO=No; target=Yes .................. 1888 Possible state-filter values............................................................................ 2879 SQ VOL display CNTLUNIT STATUS values.......................................... 29510 CNTLUNIT STATUS values for FBA meta mismatches ......................... 29611 #SC CNFG command actions for SRDF..................................................... 30012 #SC GLOBAL command actions for SRDF................................................ 30313 #SC RDFGRP command actions for SRDF ................................................ 30814 #SC SRDFA command actions for SRDF/A mode................................... 31715 #SC SRDFA_DSE command actions for SRDF/A mode ......................... 32116 #SC VOL command actions ......................................................................... 32717 SC VOL command action options............................................................... 34318 Options affecting device or pair eligibility ................................................ 34419 Options used to set device or device pair attributes ................................ 34820 Options affecting device synchronization to be performed.................... 35321 Options to be used in a recovery situation only ....................................... 35722 #SC VOL command restrictions.................................................................. 35823 Synchronization procedure selections ....................................................... 44124 SRDF Host Component utilities.................................................................. 45825 Case 1 cycles................................................................................................... 46226 Case 2 cycles................................................................................................... 46227 Case 3 cycles (option 1)................................................................................. 46328 Case 3 cycles (option 2)................................................................................. 463

Tables


Tables

Title Page

29 Link status and recovery.............................................................................. 49630 Volume status and recovery ....................................................................... 49731 SRDF Host Component enhancements...................................................... 500


Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the EMC product line, EMC periodically releases new versions of both the EMC Enginuity operating environment for Symmetrix and the SRDF Host Component. Therefore, some functions described in this guide may not be supported by all versions of Enginuity currently in use. For the most up-to-date information on product features, see your product release notes.

If a feature does not function properly or does not function as described in this guide, contact the EMC Customer Support Center for assistance.

Note: This document is accurate at the time of publication. However, as information is added, new versions of this document will be released to the EMC Powerlink website at http://Powerlink.EMC.com. Check the Powerlink website to ensure that you are using the latest version of this document.

Audience This guide is intended for the host system administrator, system programmer, or operator who is involved in managing or operating the Symmetrix storage subsystem.

Relateddocumentation

Related documents include:

◆ EMC Mainframe Enablers Release Notes

◆ EMC Mainframe Enablers Installation and Customization Guide

◆ EMC Mainframe Enablers Message and Code Guide

◆ EMC Symmetrix Remote Data Facility (SRDF) Product Guide

◆ EMC Symmetrix Remote Data Facility (SRDF) Connectivity Guide


Preface

◆ EMC ResourcePak Base for z/OS Product Guide

◆ EMCSPE Programmer’s Reference Guide

◆ REXX Interface Programmer’s Reference Guide

◆ EMC Geographically Dispersed Disaster Restart (GDDR) Product Guide

For additional information about EMC documentation, contact your EMC sales representative or refer to the EMC Powerlink website at:

http://Powerlink.EMC.com

Conventions used inthis guide

EMC uses the following conventions for notes and cautions.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system calls, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

http://powerlink.emc.com


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example

http://powerlink.emc.com


Preface

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this guide to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.

Overview 21

1

This chapter presents an overview of SRDF Host Component including its features, requirements, and options. Topics include:

◆ Mainframe Enablers and SRDF Host Component ........................ 22◆ Introduction to SRDF Host Component ......................................... 23◆ SRDF Host Component features...................................................... 25

Overview


Overview

Mainframe Enablers and SRDF Host ComponentEMC® SRDF® Host Component is a component of the Mainframe Enablers. The Mainframe Enablers are a suite of components that can aid you in monitoring and managing your storage. The components listed below are distributed and installed as a single package. This combined packaging simplifies installation and maintenance, and provides assurance of component compatibility.

◆ ResourcePak® Base for z/OS

◆ Consistency Groups for z/OS

◆ SRDF Host Component for z/OS

◆ TimeFinder®/Clone Mainframe SNAP Facility

◆ TimeFinder/Mirror for z/OS

◆ TimeFinder Utility

Activating SRDF/Host ComponentFollow the steps outlined in the EMC Mainframe Enablers Installation and Customization Guide to install and activate SRDF/Host Component.

Introduction to SRDF Host Component 23

Overview

Introduction to SRDF Host ComponentSymmetrix® Remote Data Facility (SRDF) is a business continuance solution that maintains a mirror image of data at the device level in Symmetrix arrays located in physically separate sites. The SRDF product family provides a mirrored data storage solution that allows you to duplicate production site data on one or more local or remote target Symmetrix systems.

SRDF provides a recovery solution for component or site failures between remotely mirrored devices, as shown in Figure 1. SRDF mirroring reduces backup and recovery costs and significantly reduces recovery time after a disaster.

Figure 1 SRDF bidirectional configuration

Host Host

SymmetrixSymmetrix

RDF Pair

RDF Pair

SRDF Links

I/O Transfer

Target(R2)

Device

Source(R1)

Device

Site A

Source(R1)

Device

Target(R2)

Device

I/O Transfer

Site B


Overview

SRDF Host Component is a z/OS subsystem for controlling SRDF processes and monitoring SRDF status by using commands executed from a host. SRDF Host Component for z/OS is delivered with members of the SRDF product family.

User interfaces to SRDF Host Component are provided via both TSO (ISPF) and batch commands, as well as via the system console. An optional interface is provided for TimeFinder commands as well as SRDF commands to centralize commands for both replication products.

You can issue SRDF Host Component commands to both local and remote Symmetrix systems. Commands destined for remote Symmetrix systems are transmitted via local Symmetrix systems to remote Symmetrix systems via SRDF links.

This manual describes SRDF Host Component support for all SRDF family variants, including Synchronous, Asynchronous, Data Mobility, and SRDF/Star, as well as the TimeFinder option.

IMPORTANT!Before using SRDF Host Component, you should have an understanding of basic SRDF features and operations. For an operational overview of these SRDF concepts, refer to the Symmetrix Remote Data Facility (SRDF) Product Guide.

SRDF Host Component features 25

Overview

SRDF Host Component featuresThis remainder of this chapter describes the features supported by the SRDF Host Component software.

Automation

SRDF Host Component provides command automation by associating a command, response token, and console ID for all responses to SRDF Host Component commands. This automation allows you to enter commands from and retrieve responses to automation products such as:

◆ NETVIEW◆ AutoOPERATOR◆ AF/OPERATOR

Security

SRDF Host Component provides security by allowing you to validate authorization through the z/OS SAF interface. As a result, you can use any of the following SAF-compliant security products to ensure proper user authorization:

◆ RACF◆ CA-ACF2◆ CA-Top Secret

Note: The security product you select must be compatible with RACF release version 1.9 or higher.


Overview

ISPF interfaceSRDF Host Component provides a TSO ISPF interface that is implemented as an ISPF dialog. The ISPF interface allows you to enter SRDF Host Component commands and view the command responses from your TSO session.

EMC ResourcePak Base includes EMCTOOLS, an ISPF interface that allows you to control several of the EMC zSeries products. The menus and panels of the EMCTOOLS interface use REXX and ISPF dialogs to:

◆ Query your Symmetrix environment

◆ Issue commands to control that environment

◆ Build and retain customized command streams

EMCTOOLS provides a main menu that includes an SRDF Host Component option. This option allows you to issue SRDF Host Components commands and perform Host Component functions.

Note: The EMC ResourcePak Base for z/OS Product Guide describes EMCTOOLS and its Host Component option. The ISPF panels illustrated in the EMC ResourcePak Base for z/OS Product Guide are a representation of the interface at the time the document was published. The panel contents may differ as the software is updated.


Overview

Multitasking and messagesSRDF Host Component multitasks SRDF commands to allow configuration, display, and recovery procedure testing to be performed on multiple Symmetrix systems at the same time. Two concurrent MVS tasks are supported for each Symmetrix system, one dedicated to SQUERY (SQ) commands and one dedicated to SCONFIG (SC) commands. In addition, an MVS subtask known as the Host Component global task or main task is dedicated to running commands not specific to a single Symmetrix system.

Many of the SRDF Host Component displays are issued as multiline WTO (Write to Operator) messages. When two or more commands are running concurrently, the output of these commands can appear interspersed in the Host Component job log and in the HCLOG dataset. However, the command output displays appear separately in the z/OS SYSLOG.

When running multiple requests simultaneously, the MESSAGE_LABELS and SHOW_COMMAND_SEQ# initialization parameters can help you to associate messages with the commands that produced them.

Note: “MESSAGE_LABELS” on page 124 and “SHOW_COMMAND_SEQ#” on page 150 describe these initialization parameters.

Some actions which run under the global task may require an extended period of time to complete, for example, SSID_REFRESH, RDF group commands, and SCF group name service (GNS) commands.


Overview

Command queueingWhen you enter a command, SRDF Host Component places it on a command queue for parsing; commands are parsed in the order entered. Once a command has been parsed, SRDF Host Component places it on a queue for the appropriate Host Component subtask.

SRDF Host Component has the following subtask queues:

◆ One queue for global commands (commands that are not associated with a specific Symmetrix system).

◆ One queue for #TF commands

◆ Two queues for each Symmetrix system in the configuration:

• One queue for SQuery commands associated with that specific Symmetrix system

• One queue for SConfig commands associated with that specific Symmetrix system

The maximum number of commands that can be queued for parsing is controlled by the MAX_COMMANDQ initialization parameter. “MAX_COMMANDQ” on page 122 describes this parameter.

Each command queued for parsing occupies 68 bytes plus the length of the command in extended CSA. Commands on the subtask queues occupy extended private storage.


Overview

Commands executed by queue nameTo ensure that mutually dependent commands are executed one at a time in the order in which you enter them, SRDF Host Component allows you to place most commands on designated named command queues. To designated the named command queue on which a command should be placed, append the following text to the end of the command:

,CQNAME=qname

where qname is the name of a command queue. The command queue name can be from 1 through 15 characters.

SRDF Host Component moves commands queued on the same named command queue to the appropriate subtask queue one at a time. Note that there is no inherent relationship between named command queues and subtask queues. Thus, different commands on the same named command queue may be placed on the subtask queues for different Symmetrix systems, or on the global task queue. However, the commands are always scheduled in the order in which they appeared on the named command queue. A command on a named command queue is never scheduled until the command that preceded it on the named command queue completes execution. If a queued-by-name command fails, you may elect to:

◆ Purge the remaining commands on the same named command queue.

By specifying CQNAME=(qname,P), you request that in the event of a command failure, all subsequent commands on the same named command queue are to be purged.

◆ Continue executing those commands.

By specifying CQNAME=(qname,C), you request that even though a command fails, processing continues with the next command queued on the same named command queue.

Note: The character C or P that you may specify with the CQNAME keyword is referred to in this document as the queue option.

If you do not specify the queue option on the first command for the qname queue, SRDF Host Component uses the default P (purge). On subsequent commands, you can elect to change the queue option. The new queue option takes effect when the command on which you specify it is released to the subtask queue.


Overview

RDF groups and data replicationAn RDF group is a user-defined group of devices on a Symmetrix system. RDF groups are a prerequisite for Symmetrix remote mirroring functions. Enginuity™ operating environment for Symmetrix at level 5874 allows up to 250 RDF groups to be created, with a maximum of 64 RDF groups on any one RDF director.

RDF groups are created in pairs. When an RDF group is created on a Symmetrix system, it is associated with an RDF group that is created simultaneously on another Symmetrix system. Subsequently, devices in either of the Symmetrix systems may be paired with devices in the other Symmetrix system. In creating such a device pair, a device on either of the Symmetrix systems is assigned to an RDF group on that Symmetrix system. A device on the Symmetrix system on which the associated RDF group resides is paired with the first device and simultaneously assigned to the associated RDF group.

In a device pair, one of the groups is referred to as a source or R1 device. The device with which it is paired is referred to as a target or R2 device. Each device in the pair may be referred to as a remote mirror or a partner of the other device in the pair.

The following types of device pairings exist:

◆ An R1 device can be paired with an R2 device. In an SRDF configuration, if the source (R1) device fails, the data on its corresponding target (R2) device can be accessed.

◆ An R1 device may be paired with two R2 devices at once, an arrangement referred to as concurrent SRDF.

◆ An R2 device in one pairing may be simultaneously paired as an R1 device with a different remote (R2) device, an arrangement known as Cascaded SRDF. The device that is performing both R1 and R2 functions is an R21 device. “Cascaded SRDF” on page 50 describes the use of R21 devices.

Note: With Enginuity 5874, in the SRDF/Extended Distance Protection (SRDF/EDP) environment, an R21 device can be designated as a diskless device. The purpose of a diskless R21 device is to directly cascade data to the remote R2 disk device, streamlining the linkage and reducing the cost of storage at the middle site. For information about SRDF/EDP, see “SRDF/Extended Distance Protection” on page 53.


Overview

◆ A device that can act as the target device for two distinct remote mirrors is an R22 device. R22 devices will accept write operations from only one of the source R1 devices at a time. “SRDF/Star with an R22 site” on page 58 describes the use of R22 devices.

In normal SRDF operation, data written to an R1 device is replicated on the paired R2 device. However, SRDF data replication may be temporarily suspended to allow certain operational actions to be performed. Also, some recovery operations and various operational procedures require data to be replicated from an R2 device to an R1 device. The direction of data replication is referred to as synchronization direction, described in the next section.

Synchronization direction

In a device pair, SRDF attempts to keep the R1 and R2 devices synchronized; that is, to maintain identical data on the paired devices. Synchronization is performed on a per-track basis. When corresponding tracks on an R1 device and its paired R2 device differ, the user must determine whether the data from the track on the R1 device should be copied to the corresponding track on the R2 device or whether the data from the track on the R2 device should be copied to the corresponding track on the R1 device. This decision is based on the current synchronization direction that applies to the device pair as well as on the Host Component command currently being processed, if any.

Note: The synchronization direction setting permits Host Component "synching" commands to act upon the appropriate device type. Note that the synchronization direction is solely a host concept, and has no direct effect on the Symmetrix system. The synchronization direction returns to default values specified in the initialization parameters at startup.

The following synchronization direction settings are possible:

◆ R1>R2

When corresponding tracks differ, data is copied from the track on the R1 device to the corresponding track on the R2 device. When this setting is in effect, commands that would cause data to be copied from an R2 to its partner R1 are not permitted.


Overview

◆ R1<R2

When corresponding tracks differ, data is copied from the track on the R2 device to the corresponding track on the R1 device. When this setting is in effect, commands that would cause data to be copied from an R1 to its partner R2 are not permitted.

◆ NONE

When this setting is in effect, synchronization direction commands cannot be issued.

To enhance multitasking support, SRDF Host Component allows you to set the synchronization direction separately for each Symmetrix system and/or RDF group to:

◆ R1>R2 ◆ R1<R2 ◆ NONE ◆ GLOBAL

When you start SRDF Host Component, it sets the synchronization direction to GLOBAL for each Symmetrix system. This action causes the value of the SYNCH_DIRECTION_INIT initialization parameter to be used for each system. Subsequently, global synchronization direction may be reset with the SC GLOBAL,SYNCH_DIRECTION command.

The default SYNCH_DIRECTION for RDF groups that you do not explicitly set by the SC RDFGRP command is either the control unit’s synchronization direction (set using the SC CNFG command), or if absent, the current global synchronization direction. The two Symmetrix systems in an SRDF relationship may have the control unit level set differently.

Associated RDF groups always have the same synchronization direction when they are set at the RDF group level. If CNFG is used, then each side must be set. Note that setting the synchronization direction for a Symmetrix system does not alter any synchronization direction for an RDF group that has been set explicitly. Similarly, setting the global synchronization direction does not alter any synchronization direction for a Symmetrix system or an RDF group that has been set explicitly.


Overview

Support for unequal size R1 and R2SRDF Host Component provides support for pairing unequal-size R1 and R2 devices. This Symmetrix feature supports the establishment of an SRDF pair where the R1 device is smaller (fewer cylinders) than the R2 device. The devices must still be of the same emulation type, however. Resynchronization procedures are supported for a SYNCH_DIRECTION of R1>R2. A SYNCH_DIRECTION of R1<R2 is not supported.

The Symmetrix system with the R1 volume must be at Enginuity level 5568 or higher. The Symmetrix system with the R2 volume must be at Enginuity level 5669 or higher.

For unequal-size pairs, static and dynamic SRDF support is provided as well as concurrent and Cascaded SRDF support. For dynamic SRDF, the #SC VOL command CREATEPAIR and DELETEPAIR actions are supported. However, the SWAP and the KEEPR2 options of the CREATEPAIR action are not supported.

Using metadataSince the metadata (VTOC, VTOC index, VVDS, and so forth) is copied along with the rest of the data when the devices are resynchronized, the R2 volume still appears as though it has the same number of cylinders as the R1 volume. The additional cylinders at the end of the R2 volume can be regained by running the ICKDSF utility using the REFORMAT statement with the REFVTOC option after a DELETEPAIR or with the R2 volume in R/W mode. The free space information is updated at the next new dataset allocation on the volume.

Note: If you want to continue to use the R2 volume as a mirror of the R1 volume, you need to run resynchronization procedures with sync direction set to R1>R2 to recover the metadata.


Overview

Remote Symmetrix query and configurationSRDF Host Component supports query and configuration commands to remote Symmetrix systems across the SRDF link. This provides control of Symmetrix systems which may or may not be accessible directly from any locally connected Host Component subsystem, thereby providing control of recovery testing procedures from a single Host Component subsystem.

Note: “Recovery procedure concepts and testing” on page 432 describes remote query and configuration.

Remote query and configuration is provided using the RMT(cuu[,mhlist][,rdfgroup#]) operand. For multihop remote configurations, mhlist# can be a single RDF group number or a list of up to four RDF group numbers, delimited by periods. Each RDF group number in such a list is known as a hop.

Command completion status checking

When processing a command that changes the status of a link or device, SRDF Host Component checks to see whether the device or link has successfully changed status. If it has, the command terminates normally. However, if the device or link did not successfully change status, SRDF Host Component retries the command one or more times depending upon the particular command. If the device or link status has not been successfully changed after having been retried the requisite number of times, the command is deemed to have failed, and an error message is issued.

Consistency group support

An SRDF consistency group is a set of RDF devices which has been enabled for remote database consistency. The devices in a consistency group may reside on one or more Symmetrix systems and are required for SRDF/S operations. The consistency groups operate in unison to preserve the integrity and dependent write consistency of a database distributed across any devices within the consistency group.

Note: Operation and detailed features of consistency groups are fully described in the EMC Consistency Group for z/OS Product Guide.


Overview

SRDF Host Component provides the following support for consistency groups:

◆ SRDF Host Component does not allow you to place a device that is in a consistency group into either of the Adaptive Copy modes.

◆ The SC VOL,cuu,SUSP-CGRP command trips a consistency group.

◆ The SC VOL,cuu,RDF-SUSP and SC VOL,cuu,RDF-RSUM commands are not allowed for a device in a consistency group.

◆ The SC VOL,cuu,SUSP-CGRP command is not allowed for a device that is not in a consistency group.

◆ The SQ VOL,cuu,CGROUP and SQ MIRROR,cuu,CGROUP commands display all devices that are in a consistency group for the selected Symmetrix system. The consistency group is detected by the mirror to support concurrent SRDF operations. Note that the consistency group does not need to be active to use these commands.

SRDF/S and consistency groups

When running SRDF/S, it is important to consider using EMC Consistency Group for z/OS (ConGroup). ConGroup operates to preserve the integrity and dependent write consistency of a database distributed across multiple devices within a consistency group. In an SRDF/S environment, ConGroup protects against exposure to individual SRDF link failures which may compromise the dependent write consistency. To achieve this, in the event of the failure of a link supporting an R1-R2 mirror pair belonging to the consistency group, the consistency group will be tripped, ensuring a consistent copy on the corresponding secondary (R2) devices.

In a consistency group trip, ConGroup suspends all SRDF transfers to the volumes defined for the consistency group before completing the intercepted I/O and returning control to the application. In this way, ConGroup prevents dependent I/O from reaching its remote mirror in the case where a previous I/O only gets as far as the local mirror. This ensures that all devices on the target (R2) side of SRDF/Synchronous relationships in this consistency group definition are dependent-write consistent. They can later be safely restarted from an operating system and DBMS perspective.


Overview

Defined groupsSRDF Host Component allows you to define groups of Symmetrix devices and/or controllers, and then issue commands against these groups. You specify these defined groups using the initialization parameters beginning 'GROUP_', 'EXCLUDE_', and 'INCLUDE_'. You can then use defined groups you have specified in SRDF Host Component query and configuration commands by means of the 'G' keyword parameter.

SRDF Host Component also supports SCF group syntax implemented through the SCF Group Name Service (GNS). You can specify the use of GNS groups in SRDF Host Component query and configuration commands by means of the 'SCFG' keyword parameter. The EMC ResourcePak Base for z/OS Product Guide describes the Group Name Service and SCF groups.

Note: GNS group name is referred to as SCF group name in this document.

Batch utilitySRDF Host Component provides the EMCSRDF batch utility to submit Host Component commands from a batch job environment. Commands are read from the SYSIN file and passed to the SRDF Host Component subsystem. Once a command has been processed, the resulting output is written to the SYSPRINT file.

Sample JCL for the batch utility is provided in the SAMPLIB member, EMCSRDF.

Extended address volumesStarting with Version 7.0, SRDF Host Components can perform operations against extended address volumes (EAVs). EAV support has been added to the SQ VOL and SQ MIRROR commands. Invalid track counts greater than 9999 are displayed in K up to 999K and counts greater than 999K are displayed in M. In all cases, 1K = 1024 and 1M = 1000*1K.


Overview

Virtualized RAID architectureWith Enginuity level 5874, SRDF Host Component V7.0 has virtualized the RAID architecture so that RAID-1 and RAID-5 protection mechanisms are virtualized behind the Symmetrix mirror positions, as RAID-6 was with Enginuity level 5772.

Virtualized RAID architecture does not provide a new RAID protection level—as before, there are unprotected, RAID-1 (mirrored), RAID-5, and RAID-6 levels. The CKD RAID-10 is still four RAID-1 devices grouped together with meta-striping. The virtualized architecture does hide the backend management of the RAID groups. RAID protection is now associated with individual mirrors of a device and not the whole device itself.

Virtualized RAID allows multiple, independent RAID groups per Symmetrix logical volume. It also reduces the protection positions required. The primary use for more than one RAID group per Symmetrix logical volume is tiered storage migration, which allows data to be migrated from one RAID group to another (for example, mirrored to RAID-5 to RAID-6) via online configuration changes without changing the host address assignment.

As shown in Figure 2, migrating a RAID-1 device group device to a RAID-5 device group device leverages virtual RAID to attach and synchronize the new hypers.

Figure 2 Initial state of RAID-1 device with SRDF


Overview

The new target RAID group is associated as an additional mirror to the specified source device. A brief configuration lock is taken for the devices at this time. As shown in Figure 3, the system then begins the process of synchronizing the data between the primary and the secondary mirrors of the source device.

Figure 3 Synchronizing the RAID-5 group

Reads and writes are serviced from either protection type if the data has been synchronized; otherwise, they are sent to the target.

As shown in Figure 4, when the data has been fully synchronized on all of the devices associated with a specific migration session, the system automatically promotes the secondary mirror on the source device to be the new primary mirror.

Figure 4 RAID-5 group with SRDF

The following occurs on the target side:

Configured space — The original primary mirror of the source devices will become the primary mirror of the target devices.

Unconfigured space — The system deletes the original primary mirror and returns the space to the pool of free space on the Symmetrix array.

During the migration the source device will be available for all local and remote replication. The target device will be set by the system as ‘user not ready’ for the duration of the migration and all operations to set the device to ready will be blocked.


Overview

RestrictionsThe following restrictions apply to the primary and secondary RAID type combinations per Symmetrix logical device:

◆ Any combination of Unprotected, RAID-1/Mirrored, RAID-5/3+1, RAID-5/7+1, RAID-6/6+2 and RAID-6/14+2 will be supported on a device at once, including more than one instance of the same RAID protection type (for example, on different speed drives).

◆ RAID-10 is currently limited to single RAID protection.

Multiple SRDF/A groups per Symmetrix

The Symmetrix system supports SRDF/Asynchronous (SRDF/A) operations. SRDF/A provides a point-in-time image on the target (R2) device which is only slightly behind the source (R1) device. Data is transferred to the remote Symmetrix system in predefined timed cycles; the data transferred during each cycle is called a delta set. Note that only the latest change to a particular track in a cycle needs to be included in a delta set; earlier changes in the same cycle can be discarded. SRDF/A provides a long-distance replication solution with minimal impact on performance.

With Enginuity level 5x71 and higher, the SRDF/A environment is expanded to allow multiple SRDF/A instances on a Symmetrix system, each with an SRDF/A relationship between the devices in an RDF group on the Symmetrix system and their partner devices in the other-side RDF group on the associated remote Symmetrix system. You can take advantage of this feature to use SRDF/A with bi-directional operation. Note that there cannot be bi-directional operation within a single SRDF/A RDF group; all source-to-target data flow for devices in an SRDF/A RDF group is in the same direction. However, there can be bi-directional operation by utilizing multiple SRDF/A instances between the same pair of Symmetrix systems.


Overview

Concurrent SRDF/S with SRDF/AThis feature provides the ability to replicate a group of devices in synchronous mode to one target site and in asynchronous mode to a second target site which may be an extended distance site. In this configuration, each source device is replicated synchronously using SRDF/S on one link and asynchronously using SRDF/A on the other link.

Dynamic RDFDynamic RDF functionality enables you to:

◆ Create, delete, and swap RDF pairs while the Symmetrix system is in operation.

◆ Create, modify, and remove RDF groups.

◆ Add and remove device pairs from SRDF/A groups.

◆ Add a concurrent mirror dynamically to a device that is in an SRDF/A group, subject to the normal restrictions for dynamic concurrent RDF.

Note: Only one mirror per device is allowed to be in an SRDF/A group.

“Creating and adding dynamic RDF groups” on page 309 provides additional information on dynamic RDF operations.


Overview

Movement of SRDF pairsThis feature allows you to move dynamic SRDF devices from one RDF group (the source) to another RDF group (the target) without having to execute a full synchronization of the devices. This dynamic movement provides faster operations.

Full device pair moves require that both the source and the target sides of the SRDF connection are running Enginuity level 5773 or higher. Note also that prior to Enginuity level 5874, SRDF/A cannot be active on the target RDF group of a MOVEPAIR action.

SRDF/S – SRDF/A mode changeSRDF/S – SRDF/A mode change functionality enables you to switch between asynchronous mode and synchronous mode while maintaining dependent write consistency on the remote R2 side throughout the process. This functionality only applies to a single SRDF/A group.

As an example, this feature could be used during processing where transactions are so numerous that the application might not tolerate the latency involved with handling the transaction load while in synchronous mode. With the mode change capability, if you are currently using SRDF/S, you can switch to SRDF/A mode during high workload periods to minimize performance impacts to applications. Once the overload situation has passed, you can switch from SRDF/A back to SRDF/S mode (and catch up tracks owed) before reverting to SRDF/A again if necessary.

To switch between SRDF/S and SRDF/A mode, use the SC SRDFA command with the ACT or CONS_DEACT action. Use ACT to switch to SRDF/A mode. Use CONS_DEACT to switch to SRDF/S mode. Table 14, “#SC SRDFA command actions for SRDF/A mode,” on page 317 provides more information on these actions.

Note: SRDF/S – SRDF/A mode change requires Enginuity level 5671 or higher.


Overview

SRDF/A tunable cacheThis feature provides a method for limiting the number of write pending slots in cache available to SRDF/A.

SRDF/A delta sets can grow until they reach the system write pending limit, at which point you can choose to throttle the host for a given amount of time or to drop SRDF/A immediately. You can specify the throttle settings using the SC SRDFA command. Without this feature, if write pending limits are being exceeded, performance suffers across the entire Symmetrix, not just for the SRDF/A devices.

SRDF/A Reserve CapacitySRDF/A Reserve Capacity enhances SRDF/A's ability to maintain an operational state when encountering network resource shortfalls that would have previously caused SRDF/A to suspend operations (to “drop”). With SRDF/A Reserve Capacity functions enabled, additional resource allocation can be applied to address temporary workload peaks, periods of network congestion, or even temporary network outages.

The two functions that implement SRDF/A Reserve Capacity are Transmit Idle and Delta Set Extension (DSE). These functions work together to maximize availability of continuous remote replication operations while minimizing operational overhead. It is important to note that Transmit Idle can be enabled without enabling DSE. However, when DSE is enabled, Transmit Idle must also be enabled.

Note: SRDF/A Reserve Capacity requires Enginuity level 5772 or higher.

Transmit Idle Intermittent link loss due to conditions such as network outages, network or switch maintenance, and other transient states can cause SRDF/A to drop. SRDF/A Transmit Idle provides resiliency under these conditions by allowing SRDF/A to remain active while the links are down.

When the RDF links associated with SRDF/A are unable to transmit, the Transmit Idle state is activated and the RDF mirrors continue to present normal status. SRDF/A is no longer transferring data to the remote site, but remains up and continues to accept new writes in the capture cycle.


Overview

SRDF/A Transmit Idle allows SRDF/A (following link loss) to:

◆ Continue to collect incoming data in the capture cycle (until R1 system cache limits are reached)

◆ Continue applying existing data to the R2

Once the error condition is resolved and the link resumes, SRDF/A cycle switching proceeds.

Transmit Idle requires both sides of the SRDF/A relationship to be available on the link and the SC SRDFA command action TRANSMIT_IDLE to be set to ON for both sides. Table 14, “#SC SRDFA command actions for SRDF/A mode,” on page 317 describes how to turn on/off the Transmit Idle state.

SRDF/A Delta Set ExtensionThe SRDF/A Delta Set Extension (DSE) feature enhances SRDF/A resiliency by maintaining SRDF/A operational status during temporary shortages of link capacity or outages caused by link or other infrastructure failures in the SRDF environment. It is designed as an adjunct to the Transmit Idle state and becomes active when the cache buffer reserved for SRDF/A in the Symmetrix becomes full.

SRDF/A DSE operationSRDF/A is designed to reduce the impact of distance on host I/O response time in a long distance replication configuration. It does this by buffering data in cache, thereby approximating the response times that the host would experience if no replication were occurring. Thus, the inherent delay in host I/O that occurs in synchronous replication is not present when SRDF/A is active. There may be periods of time when the incoming write I/O rate exceeds both the available bandwidth and the cache buffer of the SRDF/A configuration. This can upset the balance of cache, link, and Symmetrix processing capacity required for successful SRDF/A operation.

Prior to SRDF/A Delta Set Extension, such imbalances would cause SRDF/A to drop, requiring SRDF/A to be restarted, SRDF/A device pairs resynchronized, and consistency re-established at the remote site. This process would result in elongated recovery times.

SRDF/A Delta Set Extension absorbs the impact of a temporary imbalance or loss of SRDF/A resources by writing SRDF/A data to a dedicated pool of disks in the Symmetrix called a delta set extension pool, or DSE pool.


Overview

Four possible emulation types can be established for DSE pools, one each of the 3380, 3390, FBA(512), and FBA(520) device geometries. The emulation type associated with a DSE pool is determined by the emulation type of the first log device configured in that pool. While a DSE pool can support multiple SRDF/A groups in a Symmetrix system, a device having a particular emulation type in an SRDF/A RDF group can spill over to only one DSE pool. If multiple emulation types exist in an SRDF/A RDF group, then multiple pools of the appropriate geometry will be associated with that RDF group.

The size of the DSE pool is defined in the Symmetrix system and can be as large as desired, but may employ only the RAID 1, RAID 5, or RAID 6 protection mechanism. RAID 10 is not supported in DSE pools. The performance of the DSE pool will be affected by the protection mechanism you choose.

Usage of the pool management utilityDSE pools are managed using the pool management utility included with ResourcePak Base. The pool management utility provides support for creating either DSE pools or SNAP pools and populating them with log devices defined in the Symmetrix configuration file.

Note: The EMC ResourcePak Base for z/OS Product Guide provides details on pool management.

SRDF Host Component can associate or disassociate DSE pools that have previously been defined and populated with log devices by the pool management utility.

DSE pool assignment guidelinesIt is only necessary to have as many DSE pools associated with an RDF group as the number of different device emulation types of devices in the RDF group. Thus, if all devices in an RDF group have the same emulation type, you would need only a single DSE pool associated with the RDF group. At most four DSE pools need to be associated with an RDF group, one for each emulation type.

DSE benefits are available for an RDF group only when a DSE pool exists for each emulation type in the RDF group. If you have a device of a particular emulation type defined in an RDF group and no DSE pool associated with the RDF group for that emulation type, then none of the tracks for that device can spill over. This could cause SRDF/A to drop if cache limits are exceeded.


Overview

SRDF/A DSE commandsThere are two SRDF/A Delta Set Extension commands: SC SRDFA_DSE and SQ SRDFA_DSE. Chapter 4, “Command Reference,” describes these commands.

◆ The SC SRDFA_DSE command can be used to activate or deactivate SRDF/A DSE, or to control the AUTO_ACTIVATE feature of SRDF/A DSE.

◆ The SQ SRDFA_DSE command displays SRDF/A DSE information for an RDF group in the Symmetrix system.

Note: SC SRDFA_DSE and SQ SRDFA_DSE commands only act on one side of an RDF group pair, either the R1 or R2 side. You need to set SRDF/A Delta Set Extension on both sides of the RDF group pair. This means that if you turn on SRDF/A Delta Set Extension on the primary side of your SRDF/A RDF group pair, then you also need to turn it on for the secondary side.

SRDF Automated RecoverySRDF Automated Recovery is a utility implemented by the SC RECOVER command to monitor and perform automated recovery of SRDF/A environments. SRDF Automated Recovery is available with Enginuity level 5670 or higher versions. SRDF Automated Recovery eliminates the need for external automation or manual intervention by automatically restoring SRDF/A to operational status following a planned or unplanned outage. You can configure the software to prompt you for authorization before proceeding with automated recovery.

“SRDF Automated Recovery” on page 473 describes this feature in detail.


Overview

SRDF/A last applied cycle ageSRDF/A provides a consistent but slightly older copy of the data at the R2 (recovery) site. There is a time lag between the R2 and R1 (primary) SRDF/A data. Beginning with Enginuity level 5773, new functionality includes the ability to retrieve the time lag of the SRDF/A R2 data through host software at the R2 site in the event of a source disaster where the primary site is unavailable.

The time lag is an estimate intended to help you determine the approximate date and time that the R2 data represents. SRDF Host Component displays both the time lag and the approximated time-of-day TOD timestamp. The SQ SRDFA command provides an approximation of the time of day (CYCLETOD) that the data on the SRDF/A R2 represents.

For the age to be reported, the R1 side must also support this feature. If the R1 side does not support this feature, the age will be reported as unavailable.

IMPORTANT!The CYCLETOD reported by the SQ SRDFA command provides an approximate timestamp for the data in the 'apply' cycle of an SRDF/A configuration. It is based on the Symmetrix timers and is accurate to within a few seconds. It does not represent z/OS system time and should not be used for any recovery operations that require accurate system time as input.

The timestamp is expressed in the time of the host issuing the SQ SRDFA command. It is computed by subtracting the Symmetrix provided time lag (that is, the number of seconds elapsed since the apply cycle became a transmit cycle) from the current z/OS TOD.


Overview

Consistency exempt optionStarting with Enginuity 5874, a consistency exempt option is provided for an SRDF/A environment to indicate that a volume should be considered exempt from the consistency requirements for the group. This allows for dynamic expansion without taking the group offline and while maintaining consistency.

In normal operation, SRDF/A provides a consistent copy of the data on the R2 side. However, if there are tracks that need to be copied as part of an initial synchronization operation, the data is not consistent until those tracks have been copied to the remote Symmetrix. Also, when new RDF device pairs are created, a full synchronization is required. As a result, adding new RDF devices to an existing SRDF/A group causes the group to look inconsistent.

To solve this problem, a new CEXMPT option is available for the Host Component SC VOL command to allow a new device to be excluded from the consistency check until the tracks have been copied to the remote Symmetrix system. When the devices are added to the SRDF/A group in CEXMPT mode, you must then wait for the CEXMPT indication to clear before starting to use those devices or to consider them part of the consistent image. The CEXMPT indication will clear after two cycle switches once synchronization has been established.

IMPORTANT!Note that you cannot use devices in the CEXMPT state until this state is cleared.


Overview

Concurrent SRDFThree-site SRDF topologies are configurable for both concurrent and cascaded environments. These two SRDF three-site topologies address different recovery and availability objectives.

◆ Concurrent SRDF positions the local site (B) or the remote site (C) as potential recovery sites. To achieve this positioning, some level of reconfiguration intervention is required to access point-of-disaster data.

◆ Cascaded SRDF is oriented toward recovery only at the remote site (C) with minimal intervention to access point-of-disaster data

With concurrent SRDF, two target R2 devices are configured as concurrent mirrors of a single source R1 device. Using a concurrent SRDF pair allows the creation of two copies of the same data at two remote locations. When the two R2 devices are split from their source R1 device, each target site copy of the application can be accessed independently.

The data from a primary site is synchronously replicated to a secondary site and asynchronously replicated to a tertiary site. SRDF/Star adds the ability to resynchronize the recovery site differentially.

With concurrent SRDF, site B serves as the secondary site and the target of the SRDF/S link from site A. Site C serves as the tertiary site and the target of the SRDF/A link from site A.

Figure 5 on page 49 shows the initial concurrent SRDF configuration.


Overview

Figure 5 Initial concurrent SRDF configuration

The core benefit behind a concurrent configuration is its support of recovery at the synchronous remote site. This site can then be rapidly configured as protected at the remote asynchronous site with a differential reconfiguration.

Symmetrix

Host

Site C

Symmetrix

Host

Site B

Symmetrix

BCV R11 SRDF/S Link

R2 BCV

SRDF/A Link

R2 BCV

Host

Site A


Overview

Cascaded SRDF Cascaded SRDF is a three-way data mirroring and recovery solution that provides enhanced replication capabilities, greater interoperability, and multiple ease-of-use improvements. In Cascaded SRDF, data from a primary site is synchronously replicated to a secondary site, and then asynchronously replicated to a tertiary site.

Cascaded SRDF support allows replication between three sites without requiring the need for RDF BCVs on the second Symmetrix array. Note that a Cascaded SRDF configuration does not require three separate site locations, although that is the most common configuration for a disaster recovery solution.

The main benefit of configuring Cascaded SRDF is the capability to continue replicating from the secondary site to the tertiary site if the primary site goes down. This enables a faster recovery at the tertiary site, provided that is where the data operation is restarted.

As shown in Figure 6, site B serves as the secondary site and the target of the SRDF/S link from site A. Site C serves as the tertiary site and the target of the SRDF/A link from site B.

Figure 6 Cascaded SRDF configuration

Cascaded SRDF introduces the concept of a dual-role R1/R2 device referred to as an R21 device. Prior to Enginuity level 5773, an SRDF device could be a source device (R1) or a target device (R2), but could not function in both roles simultaneously. The R21 device is both an R1 mirror and an R2 mirror, for use only in Cascaded SRDF operations. When thinking of the R21 device, it is easier to understand the concept if you think of it as a mirror type, instead of as a device. The controls for these devices are relationship-based.

R1 R2

Workload site A

Synchronous

Secondary site B Tertiary site C

AsynchronousR21

Host I/O


Overview

Note: In an SRDF/Extended Distance Protection (SRDF/EDP) environment, the R21 device can be designated as a diskless device. The purpose of a diskless R21 device is to directly cascade data to the remote R2 disk device, streamlining the linkage and reducing the cost of storage at the middle site. For information about SRDF/EDP, see “SRDF/Extended Distance Protection” on page 53.

The R21 device is the R2 mirror of the primary site R1 device, and the R1 mirror of the tertiary site R2 device. The site A and site B devices have an RDF pair state, and the site B and site C devices have an RDF pair state. These two pair states are separate from each other; however, when performing a control operation on one pair, the state of the other device pair must be known and considered. That is, the SC VOL command CREATEPAIR and DELETEPAIR actions may be applied independently to the R1-R2 primary/secondary site pair and to the R1-R2 secondary/tertiary site pair.

Note that in Figure 6 on page 50 the data from site A to site B is synchronous and the data from site B to site C is asynchronous. These modes are the most common; however, other modes are allowed as shown in Table 1.

Note: Use of Adaptive Copy mode on the first leg will cause loss of consistency for SRDF/A operating on the second leg.

Table 1 Data modes allowed for Cascaded RDF

Site A to Site B (R1 - R21) Site B to Site C (R21 - R2)

Synchronous Asynchronous

Adaptive copy -disk Asynchronous

Adaptive copy - wp Asynchronous

Semi-synchronous (Enginuity 5671 only) Asynchronous

Synchronous Adaptive copy -disk (non-SRDF/EDP)

Synchronous Adaptive copy -wp (SRDF/EDP only)

Asynchronous (non-SRDF/EDP) Adaptive copy -disk (non-SRDF/EDP)

Adaptive copy -wp Adaptive copy -disk (non-SRDF/EDP)

Adaptive copy -disk Adaptive copy -disk (non-SRDF/EDP)

Semi-Synchronous (Enginuity 5671 only) Adaptive copy -disk (non-SRDF/EDP)

Semi-synchronous (Enginuity 5671 only) Adaptive copy -wp (SRDF/EDP only)


Overview

Composite actionsWith Enginuity level 5874, composite SC VOL command actions are available to support Cascaded SRDF operations. These actions allow you to manage Cascaded SRDF with a single command. The SC VOL command actions are:

◆ CASCRE - creates a cascaded configuration

◆ CASSUSP - suspends pairs in a cascaded configuration

◆ CASRSUM - resumes pairs in a cascaded configuration

◆ CASDEL - terminates relationships in a cascaded configuration

◆ CASSWAP - performs SRDF personality swap on both device pairs

Table 16, “#SC VOL command actions,” on page 327 describes these actions in detail.

RestrictionsSRDF Host Component Cascaded SRDF has the following restrictions:

◆ Enginuity level 5773 or higher is required on the secondary site (with R21 devices). The primary and tertiary sites can run with Enginuity level 5671, 5772, or 5773.

◆ An R21 device cannot be paired with another R21 device (R1→R21→R21→R2 is not allowed).

◆ R21 devices cannot be BCV devices, PPRC devices, or thin devices.

◆ R21 devices are only supported on Gig-E and Fibre adapters.

◆ SRDF Host Component does not support controlling (or creating) a single RDF relationship that contains both concurrent and cascaded components. For example, these are not allowed:

R2←R11→R21→R2

R2←R21←R11→R21→R2

The one exception is if a relationship like this is discovered, the DELETEPAIR action is allowed to make the relationship legal for control.


Overview

SRDF/Extended Distance ProtectionSRDF/Extended Distance Protection (SRDF/EDP) allows you to streamline a Cascaded SRDF linkage out to a remote site with a more direct (diskless) connection. Diskless Cascaded SRDF support allows replication between the source (site A) and remote target (site C) without the need for RDF BCVs or any replication at the middle site.

In a standard three-site cascaded environment, a regular R21 device has its own local mirrors so there are three full copies of data, one at each of the three sites. The R21 device assumes a dual role of both an R1 and an R2 simultaneously. However, in an SRDF/EDP cascaded environment, a diskless R21 device is in the middle Symmetrix (site B) of the total RDF link out to the remote target site. The diskless R21 device is a new type of device which does not have any local mirrors. The device has no local disk space allocated to store the user data; therefore it reduces the cost of having disk storage in the R21 site. This results in only two full copies of data, one on the source R1 disk device and one on the target R2 disk device as shown in Figure 7.

SRDF/EDP allows replication between the source and target sites without the need for RDF BCVs or any replication at the middle Symmetrix site.

Figure 7 SRDF/EDP configuration

The purpose of a diskless R21 device is to cascade data directly to the remote R2 disk device. When using a diskless R21 device, the changed tracks received from the R1 mirror are saved in cache until these tracks are sent to the R2 disk device. Once the data is sent to the R2 device and the receipt is acknowledged, the cache slot is freed and the data no longer exists on the R21 Symmetrix site.

Note: Diskless RDF is supported in conjunction with the SRDF/A Delta Set Extension feature (see “SRDF/A Delta Set Extension” on page 43).

R1 R2

Diskless DeviceSource Device Target Device

Site A Site B Site C

R21


Overview

Requirements The SRDF/Extended Distance Protection feature requires Enginuity level 5874 at the middle (diskless) site. Diskless devices are only supported on Enginuity 5874 or above; however, if the diskless device is an RDF device then only the Symmetrix that contains the diskless RDF device is required to be running Enginuity 5874 or above. The Enginuity level for the Symmetrix systems containing the RDF partners of diskless RDF devices can be running Enginuity 5773 or above.

Note: For Enginuity levels 5773, a patch is required in order to connect to a diskless RDF device.

Restrictions◆ It is recommended that the composite SC VOL command actions

be used to manage diskless device operations whenever possible. “Composite actions” on page 52 provides a list of these actions. However, in certain instances, the individual environments may need to be managed using standard SC VOL actions rather than the composite actions.

◆ A diskless device can not be mapped to the host. Therefore, no host will be able to directly access a diskless device for I/O (read or write).

◆ Diskless RDF devices are only supported on GigE and Fibre Channel directors.

◆ Diskless devices cannot perform dynamic sparing.

◆ Diskless devices cannot be RDF paired with other diskless devices.

◆ When used for SRDF/A operations, all devices in the SRDF/A session must be diskless; non-diskless device types are not allowed.

◆ All Symmetrix replication technologies other than RDF (TF, SNAP, and CLONE) will not work with diskless devices as either the source or the target of the operation.


Overview

SRDF/Star supportThe SRDF/Star disaster recovery solution provides advanced multi-site business continuity protection for enterprise environments. It combines the power of SRDF synchronous and asynchronous replication, enabling the most advanced three-site business continuance solution available today.

Note: Automation for SRDF/Star configurations is provided by EMC GDDR. The Star recovery sample scripts are not delivered with Mainframe Enablers V7.0 and later.

SRDF/Star enables SRDF/S and SRDF/A operations from the same source volumes with the ability to incrementally establish an SRDF/A session between the two remaining sites in the event of a primary site outage—a capability only available through SRDF/Star software.

SRDF/Star allows you to quickly re-establish protection between the two remote sites in the event of a primary site failure, and then, just as quickly, rejoin the primary site when conditions permit.

Three-site SRDF topologies are configurable in both concurrent and cascaded enviroments. You can use SRDF/Star with both of these three-site topologies. SRDF/Star adds the ability to resynchronize the recovery site differentially. With concurrent SRDF, the differential resynchronization is between the local site B and the remote site C. With Cascaded SRDF, the differential resynchronization is between the primary site A and the remote site C.

Concurrent and cascaded environments address different recovery and availability objectives:

◆ Concurrent SRDF/Star positions the local site (B) or the remote site (C) as potential recovery sites. To achieve this positioning, some level of reconfiguration intervention is required to access point-of-disaster data.

◆ Cascaded SRDF/Star is oriented toward recovery only at the remote site (C) with minimal intervention to access point-of-disaster data.


Overview

Concurrent SRDF/Star In concurrent SRDF/Star, data from a primary site is synchronously replicated to a secondary site and asynchronously replicated to a tertiary site.

With concurrent SRDF/Star, site B serves as the secondary site and the target of the SRDF/S link from site A. Site C serves as the tertiary site and the target of the SRDF/A link from site A. The recovery link is between site C and site B over an SRDF/A link.

Figure 8 shows the initial concurrent SRDF/Star configuration.

Figure 8 Concurrent SRDF/Star configuration

Note: The concurrent SRDF/Star configuration requires Enginuity level 5671 or higher at the three sites and an SRDF/Star license.

R1

R2

R2

SRDF/Synchronous

SRDF/Asynchronous

Site A

Site B

SRDF/A(recovery links)

Site C


Overview

Cascaded SRDF/Star A base Cascaded SRDF configuration can be enhanced using SRDF/Star differential resynchronization functionality. SRDF/Star in a Cascaded SRDF configuration offers the ability to differentially synchronize and protect the Symmetrix systems at the primary site and tertiary site (the long-distance asynchronous site) in the event the secondary site (the synchronous site) goes down.

Cascaded SRDF/Star has the ability to incrementally establish an SRDF/A session between the primary and the asynchronous site in the event of a synchronous target outage. With Cascaded SRDF/Star, the synchronous target site is always more current than the asynchronous target site.

Figure 9 shows the initial Cascaded SRDF/Star configuration. Site B serves as the secondary site and the target of the SRDF/S link from site A. Site C serves as the tertiary site and the target of the SRDF/A link from site B. The recovery link is between site C and site A over an SRDF/A link.

Figure 9 Cascaded SRDF/Star configuration

SRDF/Asynchronous

(recovery links only)

R1

SRDF/Synchronous

Site A

Site B

SRDF/A

Site C

R21

R2


Overview

Cascaded SRDF uses a dual-role SRDF R21 device on the secondary site that acts as both an R2 to the primary site and an R1 to the tertiary site.

Cascaded SRDF/Star provides a mechanism to determine when current active R1 cycle (capture) contents reach the active R2 cycle (apply) on the long-distance SRDF/A link. This minimizes the amount of data that must be moved to fully synchronize site B and site C.

Note: The Cascaded SRDF/Star configuration requires Enginuity level 5773 or higher on the workload site and its synchronous target site, and Cascaded SRDF and SRDF/Star licenses.

SRDF/Star with an R22 siteWith Enginuity 5874 and SRDF Host Component V7.0, SRDF/Star configurations with concurrent R2 RDF sites are possible. Similar to concurrent R1 devices that are referred to as R11 devices, concurrent R2 devices are referred to as R22 devices.

As shown in Figure 10 on page 59, this functionality is based on a new concurrent R2 feature that allows an R2 device to have two RDF mirrors. Each R2 mirror is paired with a different R1 mirror and only one of the R2 mirrors can be R/W on the link at a time.

The primary intended use for R22 devices is to simplify failover situations in SRDF/Star configurations and to improve the resiliency of the SRDF/Star application. The use of R22 devices in an SRDF/Star environment significantly reduces the amount of steps involved in some of the long running procedures (such as reconfigure, switch, connect), thus enabling the command sequences to finish quicker.

While designed primarily for SRDF/Star, R22 devices can be used for both concurrent and cascaded operations.


Overview

Figure 10 Concurrent R22 SRDF/Star environment

As shown in Figure 11 on page 60, you can also operate in Cascaded SRDF R22 mode with a synchronous relationship between the workload source site and the short distance target site. There will also be an asynchronous relationship to the long distance target site from the synchronous target site. The workload site to long distance asynchronous site path is passive and is referred to as the recovery path if the workload and synchronous target sites lose connectivity.

Workload siteSite A

Synchronous target siteSite B

R11 R21

R22

Asynchronous target site

Recovery path


Overview

Figure 11 Cascaded R22 SRDF/Star environment

When creating a new SRDF/Star configuration with R22 devices:

◆ All devices at the workload site must be configured as concurrent (R11) devices with one mirror paired with the R2 mirror of the remote R21 device (synchronous target site) and the other mirror paired with the R2 mirror of the remote R22 device (asynchronous target site).

◆ All devices at the synchronous target site must be configured as R21 devices paired with an R1 remote partner at the workload site and R2 remote partner at the asynchronous target site.

◆ All devices at the asynchronous target site must be configured as R22 devices paired with an R21 remote partner at the synchronous target site and R11 remote partner at the workload site.

Workload siteSite A

Synchronous target siteSite B

R11 R21

R22

Asynchronous target site

Recovery path


Overview

Extended Distance Protection with SRDF/StarWith Enginuity 5874 and SRDF Host Component V7.0, SRDF/Extended Distance Protection (EDP) configurations that make up an SRDF/Star environment are possible.

Note: “SRDF/Extended Distance Protection” on page 53 provides detailed information on the use of diskless R21 devices for SRDF/EDP functionality.

SRDF/EDP is primarily intended for use with the cascaded SRDF/Star mode, as the concurrent SRDF/Star mode has limited functionality in this environment. Figure 12 illustrates a Cascaded SRDF/Star EDP diskless environment with an R2 device at the asynchronous remote target site. The diskless R21 device streamlines the linkage connections out to the remote R2 site in cascaded mode. No data copies are available at the diskless site B.

Figure 12 Cascaded SRDF/Star EDP (diskless) environment with an R2 site

Workload siteSite A

Synchronous target site(diskless) Site B

R11 R21

R2

Asynchronous target siteSite C

Recoverypath


Overview

Figure 13 illustrates a Cascaded SRDF/Star EDP diskless environment with an R22 device at the asynchronous remote target site. The R22 device is based on a new concurrent R2 feature that allows an R2 device to have two RDF mirrors. Each R2 mirror is paired with a different R1 mirror and only one of the R2 mirrors can be RW on the link at a time.

The primary intended use for R22 devices is to simplify failover situations in SRDF/Star configurations and to improve the SRDF/Star application's resiliency. The use of R22 devices and R21 diskless devices in an SRDF/Star environment significantly reduces the amount of steps involved in some of the long running commands (such as reconfigure, switch, connect) thus enabling the command sequences to finish quicker. The diskless R21 device streamlines the linkage connections out to the remote R22 site in cascaded mode. No data copies are available at the diskless site B.

Figure 13 Cascaded SRDF/Star EDP (diskless) environment with an R22 site

Workload siteSite A

Synchronous target site(diskless) Site B

R11 R21

R22

Asynchronous target siteSite C

Recoverypath


Overview

General requirementsThe following are required to support an EDP (diskless) synchronous target site using SRDF/Star:

◆ Enginuity 5874 or higher at the diskless target site (Site B).

◆ SRDF Host Component V7.0 or higher on all sites.

◆ All devices at the synchronous target site must be configured as diskless R21 devices with R2 mirror paired with the R1 mirror of the device at the workload site and the R1 mirror paired with the R2 mirror of the device at the asynchronous target site.

Requirements when not using R22 devices◆ Enginuity 5773 or higher at the workload site (Site A) if R22s are

not being used.

◆ If the recovery RDF pairs are not configured (that is, not using R22 feature), all devices at the workload site must be configured as R1 devices paired with the R2 mirror of the diskless R21 device at the synchronous target site.

◆ If the recovery RDF pairs are not configured (i.e. not using R22 feature), all devices at the asynchronous target site must be configured as R2 devices paired with the R1 mirror of the diskless R21 device at the synchronous target site.

Requirements for using R22 devices◆ If an R22 configuration is being used, then Enginuity level 5874 is

required at all three sites.

◆ If the recovery RDF pairs are configured (that is, using the R22 feature), all devices at the workload site must be configured as concurrent R11 devices with one mirror paired with the R2 mirror of the diskless R21 device at the synchronous target site and the other mirror paired with the R2 mirror of the R22 device at the asynchronous target site.

◆ If the recovery RDF pairs are configured, all devices at the asynchronous target site must be configured as R22 devices with one mirror paired with the R1 mirror of the diskless R21 device at the synchronous target site and the other mirror paired with the R1 mirror of the R11 device at the workload site.


Overview

EMC TimeFinder option

Note: This option is configured by an EMC Customer Support Engineer at installation or service time.

SRDF Host Component includes an interface to EMC TimeFinder. TimeFinder is a business continuance solution that allows customers to use special devices that contain a copy of Symmetrix devices from one or more attached host(s) while the standard Symmetrix devices are online for regular I/O operation from their host(s). Uses for these copies can include:

◆ Backup

◆ Restore

◆ Decision support

◆ Applications testing

Note: The TimeFinder/Mirror for z/OS Product Guide describes the syntax and description of TimeFinder functions and commands.

As TimeFinder evolves, EMC provides advanced capabilities that you can only access through the native TimeFinder interfaces (batch or ISPF). Use the #TF command to access these TimeFinder features. This #TF command supports single, nonqueued TimeFinder commands using native TimeFinder syntax.

Note: Support for the #SC BCV and #SQ BCV commands was discontinued with the Version 5.5.0 release of SRDF Host Component. Use the #TF command for TimeFinder commands and queries.

Getting Started 65

2Invisible Body Tag

This chapter describes how to get started using SRDF Host Component. Topics include:

◆ Using SRDF Host Component ......................................................... 66◆ Installing SRDF Host Component ................................................... 67◆ Creating the configuration file ......................................................... 68◆ Starting SRDF Host Component...................................................... 85

Getting Started


Getting Started

Using SRDF Host ComponentAfter installation, you are ready to set up and use SRDF Host Component. Figure 14 provides an overview of the process.

Figure 14 SRDF Host Component operational steps

Specify the defined groups

Start SRDFHost Component

Create the configuration file

Install SRDFHost Component

Installing SRDF Host Component 67

Getting Started

Installing SRDF Host ComponentAs a first step in using SRDF Host Component, you install EMC Mainframe Enablers and enable the SRDF Host Component software. The installation and enabling process is described in the EMC Mainframe Enablers Installation and Customization Guide.

Making sure ResourcePak Base is runningSRDF Host Component requires that EMCSCF (ResourcePak Base) be running before issuing the start command.

Running multiple EMCSCF copiesYou can run multiple instances of EMCSCF as separate subsystems. You may want to do this when you are testing new versions of EMCSCF or EMCSCF-enabled products.

To run multiple instances of EMCSCF as separate subsystems, add the following DD statement to the EMCSCF test procedure.

//SCF$nnnn DD DUMMY

nnnn defines this instance of EMCSCF as a unique z/OS subsystem, and may be any characters permitted in a JCL ddname. The identical DD statement would then be included in the JCL of any task where you want to use this copy of EMCSCF.

For example:

Test version of EMCSCF

//EMCSCF EXEC PGM=SCFMAIN,TIME=1440,REGION=0M//STEPLIB DD DISP=SHR,DSN=test.load_library//SCFINI DD DISP=SHR,DSN=init_dataset //SYSABEND DD SYSOUT=*//SCF$0100 DD DUMMY

Any task needing to use this instance of EMCSCF would add a connection DD statement. If a version of SRDF Host Component needed to use this version of EMCSCF, the JCL for SRDF Host Component would add the DD statement:

//HCTEST EXEC PGM=EMCSTC//SYSOUT DD SYSOUT=A//SYSIN DD *//SCF$0100 DD DUMMY


Getting Started

Creating the configuration fileYour first step is to create the SRDF Host Component configuration file. The SRDF Host Component initialization parameters are specified as a series of parameter specifications in the following format:

<keyword> = <value>

Chapter 3, “Configuration,” documents the initialization parameters associated with SRDF Host Component.

Specifying defined groupsAs part of the configuration definition process, you can define groups of devices and or controllers. You can later issue commands against these groups. These Defined Groups are defined in the initialization parameters, and can be used in the query commands: SQ ADC, SQ CNFG, SQ LINK, SQ MIRROR, SQ STATE, and SQ VOL, and the configuration commands: SC CNFG and SC VOL.

There are two types of Defined Groups:

◆ Symmetrix device-defined groups — Definitions are performed based on Symmetrix device number.

◆ MVS device-defined groups — Definitions are performed based on the z/OS device number.

Rules for group definitionsThis section lists the rules for specifying Defined Groups.

General rules The rules listed in this section apply to both Symmetrix device-defined groups and MVS device-defined groups:

◆ You cannot mix Symmetrix device-defined groups and MVS device-defined groups in the same group definition.

◆ If a defined group has the same name as a SMS group, the defined group is used.

◆ All statements must start in column one.

◆ An asterisk (*) in column one treats the entire line as a comment.

Creating the configuration file 69

Getting Started

◆ Each group must have GROUP_NAME= and GROUP_END statements.

◆ If a group does not use at least one INCLUDE statement, the definition passes syntax checking, but any commands issued using the group fail.

◆ Any number of the INCLUDE and EXCLUDE statements can be used in a group definition in any sequence.

◆ If a device is both included and excluded in a group definition, the device is excluded.

◆ Assume a device is included but not excluded in the group definition. If the same device is excluded by the EXCLUDE_DEVICE_RANGE initialization statement, the device is excluded from the group definition.

Group specific rules The rules listed in this section are divided according to the group to which they apply:

Symmetrix device-defined group rules◆ If an z/OS device number used on the INCLUDE_RAG or

EXCLUDE_SYM statements is invalid or in the EXCLUDE_DEVICE list, the SRDF Host Component issues WTORs giving the operator the opportunity to stop and correct the error or to continue. If the operator continues, the group is not built as requested.

◆ INCLUDE_RAG and EXCLUDE_SYM use gatekeeper devices. Gatekeeper devices can be online or offline, as long as a valid path is available to the Symmetrix system that is being referenced.

◆ Symmetrix device-defined groups include by RDF group number and exclude by Symmetrix device number.

◆ Symmetrix device-defined groups must use the GROUP_NAME and GROUP_END statements. Symmetrix device-defined groups may use the INCLUDE_RAG, EXCLUDE_SYM, FILTER_R1, and FILTER_R2 statements.

◆ Symmetrix device-defined groups cannot use the INCLUDE_CUU, INCLUDE_VOL, EXCLUDE_CUU, EXCLUDE_VOL, FILTER_ONLINE, and, FILTER_KNOWN statements.

◆ Both online and offline devices are included in the Symmetrix device-defined group.


Getting Started

◆ Symmetrix device-defined groups include only RDF devices, both R1 and or R2 devices.

◆ Symmetrix device-defined groups may use GROUP_SORT_BY_VOLSER and GROUP_SORT_BY_MVSCUU.

MVS device-defined group rules◆ MVS device-defined groups include and exclude by MVS CUU or

VOLSER.

◆ MVS device-defined groups must use the GROUP_NAME and GROUP_END statements. MVS device-defined groups may use the INCLUDE_CUU, INCLUDE_VOL, EXCLUDE_CUU, EXCLUDE_VOL, FILTER_R1, FILTER_R2, FILTER_ONLINE, and, FILTER_KNOWN statements.

◆ MVS device-defined groups cannot use the INCLUDE_RAG and EXCLUDE_SYM statements.

◆ By default (or with the use of the FILTER_ONLINE statement) only online devices are included in MVS device-defined groups .

◆ Some offline devices can be included into a MVS device-defined group if the FILTER_KNOWN statement is used. FILTER_KNOWN includes devices known to the SRDF Host Component.

◆ Any device type (R1, R2, BCV, DR, and, STD devices) can be included in an MVS device-defined group.

◆ MVS device-defined groups may use GROUP_SORT_BY_MVSCUU and GROUP_SORT_BY_VOLSER.

Examples of group definitionsThis section provides example group definitions for MVS device-defined groups and Symmetrix device-defined groups.

Note: In the following examples, question marks (?) indicate that the device was specified in the SCF exclude list.


Getting Started

MVS device-defined group examplesExample 1 GROUP_NAME=ALL

FILTER_KNOWNINCLUDE_CUU=9820-983FINCLUDE_CUU=A020-A03FGROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (2) #SQ VOL,G(ALL) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %9820 20 0020 UGH020 1113 ONPV 0 R/W ML 9821 21 0021 UGH021 1113 ONPV 0 R/W ML 9822 22 0022 UGH022 1113 ONPV 0 R/W ML 9823 23 0023 UGH023 1113 ONPV 0 R/W ML 9824 24 0024 UGH024 1113 ONPV 0 R/W ML 9825 25 0025 UGH025 1113 ONPV 0 R/W ML 9826 26 0026 UGH026 1113 ONPV 0 R/W ML 9827 27 0027 UGH027 1113 ONPV 0 R/W ML 9828 28 0028 0028 00 UGG028 1113 ONPV 0 R/O L2 0 0 **9829 29 0029 0029 00 UGG029 1113 ONPV 0 R/O L2 0 0 **982A 2A 002A 002A 00 UGG02A 1113 ONPV 0 R/O L2 0 0 **982B 2B 002B 002B 00 UGG02B 1113 ONPV 0 R/O L2 0 0 **982C 2C 002C 002C 01 UGG02C 1113 ONPV 0 R/O B2 0 0 **982D 2D 002D 002D 01 UGG02D 1113 ONPV 0 R/O B2 0 0 **982E 2E 002E 002E 01 UGG02E 1113 ONPV 0 R/O B2 0 0 **982F 2F 002F 002F 01 UGG02F 1113 ONPV 0 R/O B2 0 0 **9830 30 0030 0030 00 UGH030 1113 ONPV 0 R/W-SY L1 0 0 **9831 31 0031 0031 00 UGH031 1113 ONPV 0 R/W-SY L1 0 0 **9832 32 0032 0032 00 UGH032 1113 ONPV 0 R/W-SY L1 0 0 **9833 33 0033 0033 00 UGH033 1113 ONPV 0 R/W-SY L1 0 0 **9834 34 0034 0034 01 UGH034 1113 ONPV 0 R/W-SY B1 0 0 **9835 35 0035 0035 01 UGH035 1113 ONPV 0 R/W-SY B1 0 0 **9836 36 0036 0036 01 UGH036 1113 ONPV 0 R/W-SY B1 0 0 **9837 37 0037 0037 01 UGH037 1113 ONPV 0 R/W-SY B1 0 0 **9838 38 0038 UGH038 1113 ONPV 0 R/W BC 9839 39 0039 UGH039 1113 ONPV 0 R/W BC 983A 3A 003A UGH03A 1113 ONPV 0 R/W BC 983B 3B 003B UGH03B 1113 ONPV 0 R/W BC 983C 3C 003C UGH03C 1113 ONPV 0 R/W BC 983D 3D 003D UGH03D 1113 ONPV 0 R/W BC 983E 3E 003E UGH03E 1113 ONPV 0 R/W BC 983F 3F 003F UGH03F 1113 ONPV 0 R/W BC END OF DISPLAY EMCQV00I SRDF-HC DISPLAY FOR (2) #SQ VOL,G(ALL) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %A020 20 0020 UGG020 1113 ONPV 0 R/W ML A021 21 0021 UGG021 1113 ONPV 0 R/W ML A022 22 0022 UGG022 1113 ONPV 0 R/W ML A023 23 0023 UGG023 1113 ONPV 0 R/W ML A024 24 0024 UGG024 1113 ONPV 0 R/W ML


Getting Started

A025 25 0025 UGG025 1113 ONPV 0 R/W MLA026 26 0026 UGG026 1113 ONPV 0 R/W MLA027 27 0027 UGG027 1113 ONPV 0 R/W MLA038 38 0038 UGG038 1113 ONPV 0 R/W BCA039 39 0039 UGG039 1113 ONPV 0 R/W BCA03A 3A 003A UGG03A 1113 ONPV 0 R/W BCA03B 3B 003B UGG03B 1113 ONPV 0 R/W BCA03C 3C 003C UGG03C 1113 ONPV 0 R/W BCA03D 3D 003D UGG03D 1113 ONPV 0 R/W BCA03E 3E 003E UGG03E 1113 ONPV 0 R/W BCA03F 3F 003F UGG03F 1113 ONPV 0 R/W BCEND OF DISPLAY


Getting Started

Example 4 GROUP_NAME=ALL_ONLINE_RDFFILTER_R1FILTER_R2FILTER_ONLINEINCLUDE_CUU=9820-983FINCLUDE_CUU=A020-A03FGROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (5) #SQ VOL,G(ALL_ONLINE_RDF) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %9828 28 0028 0028 00 UGG028 1113 ONPV 0 R/O L2 0 0 **9829 29 0029 0029 00 UGG029 1113 ONPV 0 R/O L2 0 0 **982A 2A 002A 002A 00 UGG02A 1113 ONPV 0 R/O L2 0 0 **982B 2B 002B 002B 00 UGG02B 1113 ONPV 0 R/O L2 0 0 **982C 2C 002C 002C 01 UGG02C 1113 ONPV 0 R/O B2 0 0 **982D 2D 002D 002D 01 UGG02D 1113 ONPV 0 R/O B2 0 0 **982E 2E 002E 002E 01 UGG02E 1113 ONPV 0 R/O B2 0 0 **982F 2F 002F 002F 01 UGG02F 1113 ONPV 0 R/O B2 0 0 **9830 30 0030 0030 00 UGH030 1113 ONPV 0 R/W-SY L1 0 0 **9831 31 0031 0031 00 UGH031 1113 ONPV 0 R/W-SY L1 0 0 **9832 32 0032 0032 00 UGH032 1113 ONPV 0 R/W-SY L1 0 0 **9833 33 0033 0033 00 UGH033 1113 ONPV 0 R/W-SY L1 0 0 **9834 34 0034 0034 01 UGH034 1113 ONPV 0 R/W-SY B1 0 0 **9835 35 0035 0035 01 UGH035 1113 ONPV 0 R/W-SY B1 0 0 **9836 36 0036 0036 01 UGH036 1113 ONPV 0 R/W-SY B1 0 0 **9837 37 0037 0037 01 UGH037 1113 ONPV 0 R/W-SY B1 0 0 **END OF DISPLAY


Getting Started

Symmetrix device-defined group examplesExample 1 GROUP_NAME=RAGRP00_98BOX

INCLUDE_RAG=9820,(00)GROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (1) #SQ VOL,G(RAGRP00_98BOX) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %???? ?? 0008 0008 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0009 0009 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 000A 000A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 000B 000B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0010 0010 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0011 0011 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0012 0012 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0013 0013 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **9828 28 0028 0028 00 UGG028 1113 ONPV 0 R/O L2 0 0 **9829 29 0029 0029 00 UGG029 1113 ONPV 0 R/O L2 0 0 **982A 2A 002A 002A 00 UGG02A 1113 ONPV 0 R/O L2 0 0 **982B 2B 002B 002B 00 UGG02B 1113 ONPV 0 R/O L2 0 0 **9830 30 0030 0030 00 UGH030 1113 ONPV 0 R/W-SY L1 0 0 **9831 31 0031 0031 00 UGH031 1113 ONPV 0 R/W-SY L1 0 0 **9832 32 0032 0032 00 UGH032 1113 ONPV 0 R/W-SY L1 0 0 **9833 33 0033 0033 00 UGH033 1113 ONPV 0 R/W-SY L1 0 0 **???? ?? 0048 0048 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0049 0049 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 004A 004A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 004B 004B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0050 0050 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0051 0051 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0052 0052 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0053 0053 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0068 0068 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0069 0069 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 006A 006A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 006B 006B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0070 0070 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0071 0071 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0072 0072 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0073 0073 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **END OF DISPLAY


Getting Started

Example 2 GROUP_NAME=RAGRP00_98BOX_W02A2BINCLUDE_RAG=9820,(00)EXCLUDE_SYM=9820,(002A-002B)GROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (2) #SQ VOL,G(RAGRP00_98BOX_W02A2B) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %???? ?? 0008 0008 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0009 0009 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 000A 000A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 000B 000B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0010 0010 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0011 0011 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0012 0012 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0013 0013 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **9828 28 0028 0028 00 UGG028 1113 ONPV 0 R/O L2 0 0 **9829 29 0029 0029 00 UGG029 1113 ONPV 0 R/O L2 0 0 **9830 30 0030 0030 00 UGH030 1113 ONPV 0 R/W-SY L1 0 0 **9831 31 0031 0031 00 UGH031 1113 ONPV 0 R/W-SY L1 0 0 **9832 32 0032 0032 00 UGH032 1113 ONPV 0 R/W-SY L1 0 0 **9833 33 0033 0033 00 UGH033 1113 ONPV 0 R/W-SY L1 0 0 **???? ?? 0048 0048 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0049 0049 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 004A 004A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 004B 004B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0050 0050 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0051 0051 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0052 0052 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0053 0053 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0068 0068 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0069 0069 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 006A 006A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 006B 006B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0070 0070 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0071 0071 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0072 0072 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0073 0073 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **END OF DISPLAY


Getting Started

Example 3 GROUP_NAME=RAGRP00_98BOX_W02AINCLUDE_RAG=9820,(00)EXCLUDE_SYM=9820,(002A)GROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (3) #SQ VOL,G(RAGRP00_98BOX_W02A) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %???? ?? 0008 0008 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0009 0009 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 000A 000A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 000B 000B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0010 0010 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0011 0011 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0012 0012 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **???? ?? 0013 0013 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 **9828 28 0028 0028 00 UGG028 1113 ONPV 0 R/O L2 0 0 **9829 29 0029 0029 00 UGG029 1113 ONPV 0 R/O L2 0 0 **982B 2B 002B 002B 00 UGG02B 1113 ONPV 0 R/O L2 0 0 **9830 30 0030 0030 00 UGH030 1113 ONPV 0 R/W-SY L1 0 0 **9831 31 0031 0031 00 UGH031 1113 ONPV 0 R/W-SY L1 0 0 **9832 32 0032 0032 00 UGH032 1113 ONPV 0 R/W-SY L1 0 0 **9833 33 0033 0033 00 UGH033 1113 ONPV 0 R/W-SY L1 0 0 **???? ?? 0048 0048 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 0049 0049 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 004A 004A 00 OFLINE 1113 N/A 0 R/O L2 0 0 **???? ?? 004B 004B 00 OFLINE 1113 N/A 0 R/O L2 0 0 **


Getting Started

Example 4 GROUP_NAME=RAGRP00_98BOX_R1FILTER_R1INCLUDE_RAG=9820,(00)GROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (4) #SQ VOL,G(RAGRP00_98BOX_R1) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0010 0010 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0011 0011 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0012 0012 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0013 0013 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** 9830 30 0030 0030 00 UGH030 1113 ONPV 0 R/W-SY L1 0 0 ** 9831 31 0031 0031 00 UGH031 1113 ONPV 0 R/W-SY L1 0 0 ** 9832 32 0032 0032 00 UGH032 1113 ONPV 0 R/W-SY L1 0 0 ** 9833 33 0033 0033 00 UGH033 1113 ONPV 0 R/W-SY L1 0 0 ** ???? ?? 0050 0050 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0051 0051 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0052 0052 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0053 0053 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0070 0070 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0071 0071 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0072 0072 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 0073 0073 00 OFLINE 1113 N/A 0 R/W-SY L1 0 0 ** END OF DISPLAY


Getting Started

Example 5 GROUP_NAME=RAGRP00_98BOX_R2FILTER_R2INCLUDE_RAG=9820,(00)GROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (5) #SQ VOL,G(RAGRP00_98BOX_R2) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0008 0008 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 0009 0009 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 000A 000A 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 000B 000B 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** 9828 28 0028 0028 00 UGG028 1113 ONPV 0 R/O L2 0 0 ** 9829 29 0029 0029 00 UGG029 1113 ONPV 0 R/O L2 0 0 ** 982A 2A 002A 002A 00 UGG02A 1113 ONPV 0 R/O L2 0 0 ** 982B 2B 002B 002B 00 UGG02B 1113 ONPV 0 R/O L2 0 0 ** ???? ?? 0048 0048 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 0049 0049 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 004A 004A 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 004B 004B 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 0068 0068 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 0069 0069 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 006A 006A 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** ???? ?? 006B 006B 00 OFLINE 1113 N/A 0 R/O L2 0 0 ** END OF DISPLAY


Getting Started

Example 6 GROUP_NAME=KCH1INCLUDE_RAG=LCL(6C00,3F)INCLUDE_RAG=LCL(A320,05)GROUP_END*

EMCQV00I SRDF-HC DISPLAY FOR (1) ¢¢SQ VOL,G(KCH1) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6C20 20 0020 0208 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 ** 6C21 21 0021 0209 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 ** 6C22 22 0022 020A 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 ** 6C23 23 0023 020B 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 ** 6C30 30 0030 0030 3F U6A030 1113 ONPV 0 R/W-SY R1 0 0 ** 6C31 31 0031 0031 3F U6A031 1113 ONPV 0 R/W-SY R1 0 0 ** 6C32 32 0032 0032 3F U6A032 1113 ONPV 0 R/W-SY R1 0 0 ** 6C33 33 0033 0033 3F U6A033 1113 ONPV 0 R/W-SY R1 0 0 ** 6C34 34 0034 0034 3F U6A034 1113 ONPV 0 R/W-SY R1 0 0 ** 6C35 35 0035 0035 3F U6A035 1113 ONPV 0 R/W-SY R1 0 0 ** END OF DISPLAY

EMCQV00I SRDF-HC DISPLAY FOR (1) ¢¢SQ VOL,G(KCH1) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % A030 30 0030 0030 05 OFLINE 1113 OFFL 0 N/R R2 0 0 ** A031 31 0031 0031 05 OFLINE 1113 OFFL 0 N/R R2 0 0 ** A032 32 0032 0032 05 OFLINE 1113 OFFL 0 N/R R2 0 0 ** A033 33 0033 0033 05 OFLINE 1113 OFFL 0 N/R R2 0 0 ** A034 34 0034 0034 05 OFLINE 1113 OFFL 0 N/R R2 0 0 ** A035 35 0035 0035 05 OFLINE 1113 OFFL 0 N/R R2 0 0 ** A2C8 C8 0208 0020 05 OFLINE 3339 OFFL 0 R/O R2 0 0 ** A2C9 C9 0209 0021 05 OFLINE 3339 OFFL 0 R/O R2 0 0 ** A2CA CA 020A 0022 05 OFLINE 3339 OFFL 0 R/O R2 0 0 ** A2CB CB 020B 0023 05 OFLINE 3339 OFFL 0 R/O R2 0 0 **

END OF DISPLAY


Getting Started

Example 8 GROUP_NAME=KCH3INCLUDE_RAG=RMT(6C00,3F,05)GROUP_END

Example 9 GROUP_NAME=KCH4INCLUDE_RAG=RMT(A000,05,3F)GROUP_END

EMCQV00I SRDF-HC DISPLAY FOR (3) ¢¢SQ VOL,G(KCH3) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %A030 30 0030 0030 05 OFLINE 1113 OFFL 0 N/R R2 0 0 **A031 31 0031 0031 05 OFLINE 1113 OFFL 0 N/R R2 0 0 **A032 32 0032 0032 05 OFLINE 1113 OFFL 0 N/R R2 0 0 **A033 33 0033 0033 05 OFLINE 1113 OFFL 0 N/R R2 0 0 **A034 34 0034 0034 05 OFLINE 1113 OFFL 0 N/R R2 0 0 **A035 35 0035 0035 05 OFLINE 1113 OFFL 0 N/R R2 0 0 **A2C8 C8 0208 0020 05 OFLINE 3339 OFFL 0 R/O R2 0 0 **A2C9 C9 0209 0021 05 OFLINE 3339 OFFL 0 R/O R2 0 0 **A2CA CA 020A 0022 05 OFLINE 3339 OFFL 0 R/O R2 0 0 **A2CB CB 020B 0023 05 OFLINE 3339 OFFL 0 R/O R2 0 0 **END OF DISPLAY

EMCQV00I SRDF-HC DISPLAY FOR (4) ¢¢SQ VOL,G(KCH4) DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %6C20 20 0020 0208 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 **6C21 21 0021 0209 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 **6C22 22 0022 020A 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 **6C23 23 0023 020B 3F OFLINE 1113 OFFL 0 TNR-SY R1 0 0 **6C30 30 0030 0030 3F U6A030 1113 ONPV 0 R/W-SY R1 0 0 **6C31 31 0031 0031 3F U6A031 1113 ONPV 0 R/W-SY R1 0 0 **6C32 32 0032 0032 3F U6A032 1113 ONPV 0 R/W-SY R1 0 0 **6C33 33 0033 0033 3F U6A033 1113 ONPV 0 R/W-SY R1 0 0 **6C34 34 0034 0034 3F U6A034 1113 ONPV 0 R/W-SY R1 0 0 **6C35 35 0035 0035 3F U6A035 1113 ONPV 0 R/W-SY R1 0 0 **END OF DISPLAY

Starting SRDF Host Component 85

Getting Started

Starting SRDF Host ComponentTo initiate SRDF Host Component at a mainframe console, type the following command:

S EMCRDF

The EMCRDF started task initializes SRDF Host Component, and provides server functions to the mainframe subsystem.

All SRDF Host Component I/O is done in the EMCRDF address space for recovery and performance purposes. EMC recommends leaving the subsystem active at all times.

Stopping SRDF Host ComponentTo terminate SRDF Host Component at a mainframe console, type the following command:

P EMCRDF(or #STOP)

Note: The “#” character is used as the SRDF Host Component command prefix throughout this guide. The command prefix you will actually use when entering SRDF Host Component commands will be the value specified for the COMMAND_PREFIX initialization parameter.


Getting Started

Configuration 87

3Invisible Body Tag

This chapter describes the initialization parameters used to configure SRDF Host Component. Topics include:

◆ Initialization parameters ................................................................... 89◆ ALIAS .................................................................................................. 93◆ ALLOW_CRPAIR_NOCOPY ........................................................... 95◆ COMMAND_DETAILS..................................................................... 96◆ COMMAND_PREFIX........................................................................ 97◆ EXCLUDE_CUU ................................................................................ 99◆ EXCLUDE_DEVICE_RANGE........................................................ 100◆ EXCLUDE_SYM............................................................................... 102◆ EXCLUDE_VOL............................................................................... 103◆ FBA_ENABLE .................................................................................. 105◆ FILTER_KNOWN............................................................................. 106◆ FILTER_ONLINE ............................................................................. 107◆ FILTER_R1......................................................................................... 108◆ FILTER_R2......................................................................................... 109◆ GROUP_END ................................................................................... 110◆ GROUP_NAME ................................................................................ 111◆ GROUP_SORT_BY_VOLSER ......................................................... 112◆ GROUP_SORT_BY_MVSCUU....................................................... 113◆ HCLOG.............................................................................................. 114◆ INCLUDE_CUU............................................................................... 115◆ INCLUDE_RAG ............................................................................... 116◆ INCLUDE_VOL ............................................................................... 117◆ INIT_VOLSER .................................................................................. 119◆ LOGONLY_FOR_TRACKED_COMMANDS.............................. 120◆ MAX_ALIAS..................................................................................... 121◆ MAX_COMMANDQ....................................................................... 122

Configuration


Configuration

◆ MAX_QUERY................................................................................... 123◆ MESSAGE_LABELS ........................................................................ 124◆ MESSAGE_PROCESSING.............................................................. 125◆ MSC_ACTIVATE_MS...................................................................... 126◆ MSC_ALLOW_INCONSISTENT .................................................. 127◆ MSC_CYCLE_TARGET .................................................................. 128◆ MSC_GROUP_END ........................................................................ 129◆ MSC_GROUP_NAME..................................................................... 130◆ MSC_INCLUDE_SESSION ............................................................ 131◆ MSC_STAR........................................................................................ 136◆ MSC_VALIDATION ........................................................................ 137◆ MSC_WEIGHT_FACTOR............................................................... 138◆ OPERATOR_VERIFY ...................................................................... 140◆ REGISTER_COMMAND_PREFIX ................................................ 142◆ SAF_CLASS ...................................................................................... 144◆ SAF_PROFILE .................................................................................. 145◆ SECURITY_CONFIG....................................................................... 148◆ SECURITY_QUERY......................................................................... 149◆ SHOW_COMMAND_SEQ#........................................................... 150◆ SINGLE_CONCURRENT............................................................... 151◆ SMFREC ............................................................................................ 152◆ SORT_BY_COMMAND.................................................................. 153◆ SORT_BY_MVSCUU ....................................................................... 154◆ SORT_BY_VOLSER ......................................................................... 155◆ SRDFA_AUTO_RECOVER............................................................. 156◆ SRDFA_AUTO_RECOVER_BCV .................................................. 157◆ SRDFA_AUTO_RECOVER_ITRK ................................................. 158◆ SRDFA_AUTO_RECOVER_MINDIR ........................................... 159◆ SRDFA_AUTO_RECOVER_PROC ............................................... 160◆ SUBSYSTEM_NAME ...................................................................... 161◆ SYNCH_DIRECTION_ALLOWED............................................... 162◆ SYNCH_DIRECTION_INIT........................................................... 163◆ USER_VERIFICATION ................................................................... 164◆ USER_VERIFICATION_TIMEOUT .............................................. 165◆ VONOFF_BLOCKED ...................................................................... 166◆ VONOFF_OFF_ONLY..................................................................... 167◆ VONOFF_ON_ONLY...................................................................... 168◆ VONOFF_R1_ONLY ....................................................................... 169◆ VONOFF_R2_ONLY ....................................................................... 170◆ VONOFF_STATUS_WAIT .............................................................. 171

Initialization parameters 89

Configuration

Initialization parametersSRDF Host Component initialization parameters are specified as a series of parameter specifications in the following format:

<keyword> = <value>

◆ The keyword must begin in column 1.

Note: An asterisk (*) in column 1 denotes a comment.

◆ Each individual parameter specification must begin on a separate line in the parameter file. However, you may continue parameter statements across multiple input lines. All leading blanks will be honored. To continue a parameter statement, place a hyphen (-) as the last non-blank character on the line you wish to continue. The second line will be appended to the original line at the column where the hyphen was located. The character that is in column 1 on the second line will overlay the hyphen. (Note that this applies to a blank character as well.)

For example:

SUBSYSTEM_NAME=RA-H3

Will result in SUBSYSTEM_NAME=RAH3 being processed.

◆ The first specification must be SUBSYSTEM_NAME. You can specify all other parameters (except the SRDF group parameters, which are order-dependent) in any order.

◆ The initialization parameter file must be saved as a member of a parameter library. This parameter library member is identified to SRDF Host Component by means of the RDFPARM DD statement of the EMCRDF procedure.


Configuration

Table 2 summarizes the initialization parameters associated with SRDF Host Component.

Table 2 Initialization parameters (page 1 of 3)

Parameter Required/optional Default setting

ALIAS Optional N/A

ALLOW_CRPAIR_NOCOPY Optional NO

COMMAND_DETAILS Optional N/A

COMMAND_PREFIX Required N/A

EXCLUDE_CUU Optional N/A

EXCLUDE_DEVICE_RANGE Optional No devices are excluded

EXCLUDE_SYM Optional N/A

EXCLUDE_VOL Optional N/A

FBA_ENABLE Optional NO

FILTER_KNOWN Optional N/A

FILTER_ONLINE Optional N/A

FILTER_R1 Optional N/A

FILTER_R2 Optional N/A

GROUP_END Optional N/A

GROUP_NAME Optional N/A

GROUP_SORT_BY_VOLSER Optional N/A

GROUP_SORT_BY_MVSCUU Optional N/A

HCLOG Optional COMMANDS

INCLUDE_CUU Optional N/A

INCLUDE_RAG Optional N/A

INCLUDE_VOL Optional N/A

INIT_VOLSER Optional N/A

LOGONLY_FOR_TRACKED_COMMANDS

Optional N/A

Initialization parameters 91

Configuration

MAX_ALIAS Optional 200

MAX_COMMANDQ Optional 500

MAX_QUERY Optional 512

MESSAGE_LABELS Optional NONE

MESSAGE_PROCESSING Required N/A

MSC_ACTIVATE_MS Optional N/A

MSC_ALLOW_INCONSISTENT Optional N/A

MSC_CYCLE_TARGET Optional N/A

MSC_GROUP_END Optional N/A

MSC_GROUP_NAME Optional N/A

MSC_INCLUDE_SESSION Optional N/A

MSC_STAR Optional N/A

MSC_VALIDATION Optional WARN

MSC_WEIGHT_FACTOR Optional 0

OPERATOR_VERIFY Optional ALL

REGISTER_COMMAND_PREFIX Optional N/A

SAF_CLASS Optional DATASET

SAF_PROFILE Optional EMC.VALIDATE.ACCESS

SECURITY_CONFIG Required N/A

SECURITY_QUERY Required N/A

SHOW_COMMAND_SEQ# Optional NO

SINGLE_CONCURRENT Optional N/A

SMFREC Optional SMF option is not active

SORT_BY_COMMAND Optional N/A

SORT_BY_MVSCUU Optional N/A




Configuration

SORT_BY_VOLSER Optional N/A

SRDFA_AUTO_RECOVER Optional NO

SRDFA_AUTO_RECOVER_BCV Optional ESTablish for startup_optionNONE for post_recovery_option

SRDFA_AUTO_RECOVER_ITRK Optional 30

SRDFA_AUTO_RECOVER_MINDIR Optional 1

SRDFA_AUTO_RECOVER_PROC Optional EMCRCVRY

SUBSYSTEM_NAME Required N/A

SYNCH_DIRECTION_ALLOWED Optional R1>R2

SYNCH_DIRECTION_INIT Optional NONE

USER_VERIFICATION Optional NO

USER_VERIFICATION_TIMEOUT Optional (5,0)

VONOFF_BLOCKED Optional N/A

VONOFF_OFF_ONLY Optional N/A

VONOFF_ON_ONLY Optional N/A

VONOFF_R1_ONLY Optional N/A

VONOFF_R2_ONLY Optional N/A

VONOFF_STATUS_WAIT Optional 30



ALIAS 93

Configuration

ALIAS

Description The optional ALIAS initialization parameter allows you to assign an alias to an SRDF Host Component command parameter. You can substitute aliases for command parameters within an SRDF Host Component command. The replacement can be any part of a command preceded and followed by one of these characters: a blank, open parenthesis, close parenthesis, or comma.

An alias must be unique, and must not be the same as any SRDF Host Component command or action name. For example, VOL cannot be an alias because it is an existing command. You can assign multiple aliases to the same SRDF Host Component command parameter.

Note: Do not assign "C" and "P" as aliases, since these assignments would conflict with the Continue and Purge parameters of the command queuing function. Table 4 on page 178 describes these parameters.

Format ALIAS=srdf-hc command-portion,alias-name

Where:

command-portion

Is the portion of the command to which you want to assign an alias.

alias-name

Is the alias you want to assign.

Examples ALIAS=GLOBAL,GALIAS=SSID_REFRESH,S

◆ If ALIAS is set to the following:

'VOL,LCL(9800,02),CREATEPAIR(KEEPR1,SYNC,RDY,LCLISR2)',CPR

The #SC CPR,02-03,00 command expands to:

#SC VOL,LCL(9800,02),CREATEPAIR(KEEPR1,SYNC,RDY,LCLISR2),02-03,00


'RMT(3004,00.01.02.03)',MHL

The #SQ V,MHL command expands to:


Configuration

#SQ VOL,RMT(3004,00.01.02.03)


'SQ VOL,G(GROUP_ONE)',CMD1

The #CMD1 command expands to:

#SQ VOL,G(GROUP_ONE)

Note: The SRDF SAMPLIB library member RDFALIAS contains a set of alias assignments using the ALIAS initialization parameter.

ALLOW_CRPAIR_NOCOPY 95

Configuration

ALLOW_CRPAIR_NOCOPY

Description The ALLOW_CRPAIR_NOCOPY parameter specifies whether the NOCOPY option will be allowed with the #SC VOL CREATEPAIR action.

Format ALLOW_CRPAIR_NOCOPY=NO|YES|STAR

Where:

NO

Indicates NOCOPY will not be allowed for any CREATEPAIR action. This is the default setting.

YES

Indicates NOCOPY will be allowed for all CREATEPAIR actions.

STAR

Indicates NOCOPY will only be allowed for CREATEPAIR actions to an SRDF/Star group.

Example ALLOW_CRPAIR_NOCOPY=STAR


Configuration

COMMAND_DETAILS

Description You can use the COMMAND_DETAILS initialization parameter with #SC CNFG, #SC LINK, #SC SRDFA, and #SC RDFGRP commands to cause EMCGM40I messages to be issued, and with the #SC VOL command to cause messages EMCGM40I through EMCGM43I to be issued. When this parameter is not present, EMCGM40I through EMCGM43I are not issued.

No keyword value is used with this initialization parameter.

Format COMMAND_DETAILS

Example None.

COMMAND_PREFIX 97

Configuration

COMMAND_PREFIX

Description The required COMMAND_PREFIX parameter indicates the prefix for all SRDF Host Component commands. This command prefix should be unique to SRDF Host Component.

The specified command prefix can be registered with the Sysplex by appending the keyword REGister to the parameter value. For example:

Registering the command prefix prevents ambiguity between similar command prefixes defined for different subsystems.

z/OS does not allow you to register a command prefix that is the same as or that matches an initial substring of an existing registered command prefix, nor does z/OS allow you to register a command prefix if an existing registered command prefix matches an initial substring of the command prefix you are attempting to register. Any attempt to do so results in an error message and an initialization failure.

Format COMMAND_PREFIX=prefix

Where:

prefix

Is the one- to eight-character command prefix you want to use for this SRDF Host Component subsystem.

Comments When you precede the COMMAND_PREFIX parameter by the REGISTER_COMMAND_PREFIX parameter, the value specified is not parsed for the ,REG= keyword. Instead, the entire 1-8 character string specified on COMMAND_PREFIX is used as the prefix.

Consider the following example:

REGISTER_COMMAND_PREFIX=YESCOMMAND_PREFIX=@,REG

COMMAND_PREFIX=# Prefix not registered with the Sysplex

COMMAND_PREFIX=#HC,REG Prefix registered with the Sysplex


Configuration

In this example, the prefix is set to the 5-character string ’@,REG’ and the prefix would be registered. On the other hand, if, the REGISTER_COMMAND_PREFIX parameter is not specified, and the same COMMAND _PREFIX parameter is used, the prefix would be set to ’@’ and the prefix would be registered.

Example COMMAND_PREFIX=#

Note: Be careful when selecting characters for the command prefix. Be sure to choose characters that do not conflict with characters used in forming z/OS commands or with prefixes assigned to other subsystems.

EXCLUDE_CUU 99

Configuration

EXCLUDE_CUUDescription Use the EXCLUDE_CUU initialization parameter when defining a

Defined Group. EXCLUDE_CUU allows you to exclude a list of devices from the Defined Group that would otherwise be included. You can use this statement parameter only after the GROUP_NAME parameter. EXCLUDE_CUU is valid only for MVS device-defined groups.

Formats The formats for this parameter are as follows:

◆ EXCLUDE_CUU=aaaa

Where aaaa is a mainframe device number to be excluded from the group definition.

◆ EXCLUDE_CUU=bbbb,cccc,dddd

Where bbbb, cccc, and dddd are mainframe device numbers to be excluded from the group definition.

◆ EXCLUDE_CUU=eeee-ffff,gggg-hhhh

Where eeee-ffff and gggg-hhhh are ranges of mainframe device numbers to be excluded from the group definition. Note that ffff > eeee and hhhh > gggg.

Note: “VONOFF_STATUS_WAIT=30” on page 171 provides more information.


Configuration

EXCLUDE_DEVICE_RANGE

Description The optional EXCLUDE_DEVICE_RANGE parameter statement specifies a mainframe device number, or range of mainframe device numbers, to be excluded from use in commands issued to SRDF Host Component.

Note: This does not stop SRDF Host Component from acting upon devices listed in this parameter.

The ending device number, if specified, must be greater than or equal to the starting device number. Up to 128 separate EXCLUDE_DEVICE_RANGE statements may be included in the initialization deck, allowing for up to 128 distinct ranges of devices to be excluded.

Format EXCLUDE_DEVICE_RANGE=scuu[-ecuu]

Where:

scuu

Specifies the starting or only mainframe device number of the range of devices to be excluded.

ecuu

Specifies the ending mainframe device number of a range of devices to be excluded from SRDF Host Component processing, if different from the starting device number.

If ecuu is omitted, the range will consist only of the single device specified by scuu.

Example To exclude a whole Symmetrix system from SRDF Host Component use, you have to include EXCLUDE_DEVICE_RANGE specifications for all device ranges in that Symmetrix system. For example:

EXCLUDE_DEVICE_RANGE=200-3FFEXCLUDE_DEVICE_RANGE=420EXCLUDE_DEVICE_RANGE=800-FFF

In the previous example, devices 200 through 3FF, 420, and 800 through FFF would be excluded from use as the cuu parameter in commands issued to SRDF Host Component.

EXCLUDE_DEVICE_RANGE 101

Configuration

In the example, device 420 cannot be used in an SRDF Host Component command, but can still be included in the processing of other commands. That is, the command SQ VOL,420,ALL would be prohibited. However, the command SQ VOL,421,ALL would be allowed and would process device 420.

CAUTION!EXCLUDE_DEVICE_RANGE does not exclude devices from being processed. The statement specifies which devices are not to be used to issue the actions or query to the Symmetrix system.


Configuration

EXCLUDE_SYM

Description You can use the EXCLUDE_SYM initialization parameter when defining a Defined Group. EXCLUDE_SYM allows you to exclude a Symmetrix device or range of Symmetrix devices residing on a single Symmetrix system. You can only use EXCLUDE_SYM after the GROUP_NAME parameter. EXCLUDE_SYM is valid only for Symmetrix device-defined groups.

Formats The formats for this parameter statement are as follows:

◆ EXCLUDE_SYM=aaaa,(bbbb)

Where aaaa is the mainframe device number of a device residing on the Symmetrix system on which the Symmetrix device number bbbb to be excluded from the group definition is located.

◆ EXCLUDE_SYM=cccc,(dddd-eeee)

Where cccc is the mainframe device number of a device residing on the Symmetrix system on which the Symmetrix device number range dddd-eeee to be excluded from the group definition is located. For this format, eeee must be greater than dddd.

◆ EXCLUDE_SYM=RMT(cccc,rdfgrp),(dddd-eeee)

Where cccc is the mainframe device number of a device residing on the local Symmetrix system, rdfgrp is an RDF group on the local Symmetrix system whose partner RDF group resides on the remote Symmetrix system, and dddd-eeee identify the Symmetrix device numbers on the remote Symmetrix system that are to be excluded from the group definition. Note that eeee must be greater than dddd.

Example None.

EXCLUDE_VOL 103

Configuration

EXCLUDE_VOL

Description You can use the EXCLUDE_VOL initialization parameter when defining a Defined Group. EXCLUDE_VOL allows you to exclude a list of mainframe volumes and/or patterns of volumes. You can only use EXCLUDE_VOL after the GROUP_NAME parameter. EXCLUDE_VOL is valid only for MVS device-defined groups.

Note: EXCLUDE_VOL is a dynamic exclude statement. The mainframe device number of the device to be excluded is obtained at the time the command is issued. The mainframe device number is obtained from the online mainframe volume serial number (volser). The dynamic exclude ability of this statement may produce unexpected results for an R1 and R2 pair with the same volser.

Formats The formats for this parameter are as follows:

◆ EXCLUDE_VOL=aaaaaa

Where aaaaaa is a mainframe volser to be included in the group definition. Note that volume aaaaaa must be online to be excluded.

◆ EXCLUDE_VOL=bbbbbb,cccccc,dddddd

Where bbbbbb, cccccc, and dddddd are mainframe volsers to be excluded in the group definition. Note that volumes bbbbbb, cccccc, and dddddd must be online to be excluded.

Comments When you use EXCLUDE_VOL, SRDF Host Component permits the use of patterns.

For example:

◆ EXCLUDE_VOL=e*

Where e* excludes all online mainframe volumes whose volsers begin with the character e.

◆ EXCLUDE_VOL=fghij*

Where fghij* excludes all online mainframe volumes whose volsers begin with the characters fghij.

The following rules apply when using patterns:

◆ At least one significant character must be used; a pattern consisting of only of a single asterisk is not permitted.


Configuration

◆ The only pattern character is * and it can be used for any number of characters.

◆ An asterisk (*) is always an ending character.

◆ In order for the pattern to match, the device with the volser must be online.

◆ Using a pattern requires the entire UCB list for the z/OS image to be scanned at the time the command is issued.


Example None.

FBA_ENABLE 105

Configuration

FBA_ENABLE

Description The optional FBA_ENABLE initialization parameter specifies whether SRDF Host Component is to allow #SC VOL commands to change the status of FBA devices. You can change this operating mode using the #SC GLOBAL command, and display the operating mode using the #SQ GLOBAL command.

Format FBA_ENABLE=YES|NO

Where:

YES

Specifies that the #SC VOL command is enabled for FBA devices.

NO

Specifies that the #SC VOL command is disabled for FBA devices.

If you do not specify FBA_ENABLE, FBA_ENABLE defaults to NO.

Example FBA_ENABLE=YES


Configuration

FILTER_KNOWN

Description You can use the FILTER_KNOWN initialization parameter when defining a Defined Group. You can only use FILTER_KNOWN after the GROUP_NAME initialization parameter. FILTER_KNOWN is a initialization parameter that, when used with an MVS device-defined group, includes both online and offline devices known to SRDF Host Component.

A device is known to SRDF Host Component when it has been online or has been found while SRDF Host Component has been running. No keyword value is used with this initialization parameter.

Note: If the INCLUDE_VOL statement is used for group definition, then the FILTER_KNOWN parameter is not applicable. “VONOFF_STATUS_WAIT=30” on page 171 provides more information.

Format FILTER_KNOWN

Example FILTER_KNOWN

FILTER_ONLINE 107

Configuration

FILTER_ONLINE

Description You can use the FILTER_ONLINE initialization parameter when defining a Defined Group. You can only use FILTER_ONLINE after the GROUP_NAME initialization parameter. FILTER_ONLINE is a parameter that, when used with an MVS device-defined group, includes only online devices known to SRDF Host Component. No keyword value is used with this initialization parameter.


Format FILTER_ONLINE

Example FILTER_ONLINE


Configuration

FILTER_R1

Description You can use the FILTER_R1 initialization parameter when defining a Defined Group. You can only use FILTER_R1 after the GROUP_NAME parameter. FILTER_R1 is a parameter that, when used, includes only R1 devices in the group, unless you use it with a FILTER_R2 initialization parameter. The included devices (included with INCLUDE statements) are filtered to include only the R1 devices in the group.

If you use both FILTER_R1 and FILTER_R2 in a group definition, both R1 and R2 devices are included in the group. FILTER_R1 is valid for both Symmetrix device-defined groups and MVS device-defined groups.


Format FILTER_R1

Example FILTER_R1

FILTER_R2 109

Configuration

FILTER_R2

Description You can use the FILTER_R2 initialization parameter when defining a Defined Group. You can only use FILTER_R2 after the GROUP_NAME parameter. FILTER_R2 is a parameter that, when used, includes only R2 devices in the group, unless you use it with a FILTER_R1 initialization parameter. The included devices (included through INCLUDE statements) are filtered to include only the R2 devices in the group.

If you use both FILTER_R1 and FILTER_R2 in a group definition, both R1 and R2 devices are included in the group. FILTER_R2 is valid for both Symmetrix device-defined groups and MVS device-defined groups.


Format FILTER_R2

Example FILTER_R2


Configuration

GROUP_END

Description Use the GROUP_END initialization parameter when defining a Defined Group. You can only use GROUP_END after the GROUP_NAME parameter. GROUP_END is required in order to complete the group definition. GROUP_END is valid for both Symmetrix device-defined groups and MVS device-defined groups.


Format GROUP_END

Example GROUP_END

GROUP_NAME 111

Configuration

GROUP_NAME

Description Use the GROUP_NAME initialization parameter when defining a Defined Group. GROUP_NAME is required in order to start the definition of a group.

The group name you specify can be from 1 through 24 alphanumeric or national characters. The group name is delimited by the first blank encountered, and can therefore contain no embedded blanks. The GROUP_NAME parameter is valid for both Symmetrix device-defined groups and MVS device-defined groups.

Both local and remote groups may be defined. Local and remote groups can be defined to operate upon only a single mirror of a concurrent SRDF relationship using the remote (RMT) form. If a Defined Group name is the same as a SMS Group name, the Defined Group is used for that name.

Note: “VONOFF_STATUS_WAIT=30” on page 171 gives more information.

Format GROUP_NAME=value

Where:

value

Is a name consisting of 1-24 alphanumeric or national (@#$) characters.

Example None.


Configuration

GROUP_SORT_BY_VOLSER

Description You can use the GROUP_SORT_BY_VOLSER initialization parameter in a group definition (must be after a GROUP_NAME initialization parameter statement and before a GROUP_END initialization parameter statement).

If the Global Sort Order is set to COMMAND, the output is sorted in VOLSER sequence. If the Global Sort Order is not set to COMMAND, this parameter is ignored. This parameter only applies to #SQ VOL, #SQ MIRROR, and #SQ STATE commands.

Format GROUP_SORT_BY_VOLSER

Example GROUP_SORT_BY_VOLSER

GROUP_SORT_BY_MVSCUU 113

Configuration

GROUP_SORT_BY_MVSCUU

Description You can use the GROUP_SORT_BY_MVSCUU initialization parameter in a group definition (must be after a GROUP_NAME initialization parameter statement and before a GROUP_END initialization parameter statement).

If the Global Sort Order is set to COMMAND, the output is sorted in MVSCUU sequence. If the Global Sort Order is not set to COMMAND, this parameter is ignored. This parameter only applies to #SQ VOL, #SQ MIRROR, and #SQ STATE commands.

Format GROUP_SORT_BY_MVSCUU

Example GROUP_SORT_BY_MVSCUU


Configuration

HCLOG

Description The optional HCLOG initialization parameter specifies whether SRDF Host Component is to log only commands, or to log commands and command responses to the HCLOGn datasets.

Note: HCLOG is only effective if one or more HCLOGn DD statements are included in the initialization JCL, as described in the Mainframe Enablers Installation and Customization Guide.

Format HCLOG=COMMANDS|ALL

Where:

COMMANDS

Only the commands are to be logged.

ALL

Commands and responses are to be logged.

Example HCLOG=ALL

INCLUDE_CUU 115

Configuration

INCLUDE_CUU

Description You can use the INCLUDE_CUU initialization parameter when defining a Defined Group. You can only use INCLUDE_CUU after the GROUP_NAME parameter. INCLUDE_CUU is a parameter you use to include a list of mainframe devices. INCLUDE_CUU is only valid for MVS device-defined groups.


Format The formats for this parameter statement are as follows:

◆ INCLUDE_CUU=aaaa

Where aaaa is an mainframe device number to be included in the group definition.

◆ INCLUDE_CUU=bbbb,cccc,dddd

Where bbbb, cccc and dddd are mainframe device numbers to be included in the group definition.

◆ INCLUDE_CUU=eeee-ffff,gggg-hhhh

Where eeee-ffff and gggg-hhhh are ranges of mainframe device numbers to be included in the group definition. Note that ffff>eeee and hhhh>gggg.

Example None.


Configuration

INCLUDE_RAGDescription You can use the INCLUDE_RAG initialization parameter when

defining a Defined Group. You can only use INCLUDE_RAG after the GROUP_NAME parameter. Use the INCLUDE_RAG parameter to include an entire RDF group from a local or remote EMC controller. INCLUDE_RAG is only valid for Symmetrix device-defined groups.


Format INCLUDE_RAG=aaaa,(rdfgroup#)

INCLUDE_RAG=LCL(aaaa,rdfgroup#)

INCLUDE_RAG=RMT(aaaa,mhlist,rdfgroup#)

Where:

aaaa

Indicates the mainframe device number of the gatekeeper device in the control unit.

mhlist

Specifies the rdfgroup# used to identify the remote Symmetrix unit. For multihop remote configurations, mhlist can be a single rdfgroup# or a list of up to four hops, separated by periods.

rdfgroup#

Indicates the controller RDF group to be included.

Example The following example defines a group consisting of devices in RAG 19 on the remote Symmetrix accessed via gatekeeper 6C00 and local RAG 17.

GROUP_NAME=RMTRAG1 INCLUDE_RAG=RMT(6C00,17,19) GROUP_END

INCLUDE_VOL 117

Configuration

INCLUDE_VOL

Description You can use the INCLUDE_VOL initialization parameter when defining a Defined Group. You can only use INCLUDE_VOL after the GROUP_NAME parameter. INCLUDE_VOL is a parameter that you use to include a list of mainframe volumes and/or patterns of volumes. INCLUDE_VOL is only valid for MVS device-defined groups.

INCLUDE_VOL is a dynamic include statement. The mainframe device number of the device to be included is obtained at the time the command is issued. The mainframe device number is obtained from the online mainframe volume serial name. The dynamic include ability of this statement may produce unexpected results with an R1 and R2 pair with the same volume serial name.

For example, assume that both devices in an R1/R2 pair have a volume serial name of ABCDEF and that the R2 device is online. INCLUDE_VOL=ABCDEF includes the R2 device. If FILTER_R1 is applied, neither the R1 nor the R2 is included. Assume that the R2 device is taken offline and the R1 device is taken online. INCLUDE_VOL=ABCDEF includes the R1 device. The group dynamically changes which device is included, which may not be the expected result.


Format The formats for this parameter statement are as follows:

◆ INCLUDE_VOL=aaaaaa

Where aaaaaa is a mainframe volume serial name to be included in the group definition. Note that aaaaaa must be online to be included.

◆ INCLUDE_VOL=bbbbbb,cccccc,dddddd

Where bbbbbb, cccccc and dddddd are mainframe volume serial names to be included in the group definition. Note that bbbbbb, cccccc, and dddddd must be online to be included.


Configuration

Comments SRDF Host Component supports the use of patterns with INCLUDE_VOL. For example:

◆ INCLUDE_VOL=e*

Where e* includes all online z/OS volume serial names that begin with the character e.

◆ INCLUDE_VOL=fghij*

Where fghij* includes all online z/OS volume serial names that begin with the characters fghij.

The following rules apply when using patterns:

◆ At least one significant character must be used (in other words, a* matches every online volume serial starting with a).

◆ The only pattern character is * and it can be used for any number of characters.

◆ Asterisk (*) is always an ending character.

◆ For the pattern to match, the device with the Volume Serial name must be online.

◆ Using a pattern requires the entire UCB list for the z/OS image to be scanned at the time the command is issued.

Example None.

INIT_VOLSER 119

Configuration

INIT_VOLSER

Description The INIT_VOLSER initialization parameter is an initial value for the VOLSER. If a device is not discovered later and filled in from the online UCB, this initial value is used in the displays for the #SQ VOL and #SQ STATE commands.

Note that the opening quote (‘) is required. The first six characters after the opening quote are used as the value for the device volume serial for any device found offline.

Format INIT_VOLSER=’init volser’

Where:

init volser

Specifies the initial value for the VOLSER.

Example INIT_VOLSER=’ABCDEF’


Configuration

LOGONLY_FOR_TRACKED_COMMANDS

Description If you specify LOGONLY_FOR_TRACKED_COMMANDS, then command output for commands entered from the batch and REXX interfaces do not appear in the syslog or system consoles. This output is still returned to the submitter of the command, and will appear in the hclog.

Format LOGONLY_FOR_TRACKED_COMMANDS

Example LOGONLY_FOR_TRACKED_COMMANDS

MAX_ALIAS 121

Configuration

MAX_ALIAS

Description The optional MAX_ALIAS initialization parameter specifies the maximum number of alias statements that can be included in the parameter file.

Format MAX_ALIAS=nnnn

Where:

nnnn

Represents the maximum number of alias statements, a decimal integer in the range of from 200 to 4095. If you do not specify MAX_ALIAS, it defaults to 200.

Example MAX_ALIAS=330


Configuration

MAX_COMMANDQ

Description The optional MAX_COMMANDQ initialization parameter specifies the maximum number of commands that can be queued to the SRDF Host Component main task for parsing.

MAX_COMMANDQ prevents the scheduling of multiple commands on multiple command queues. For example, MAX_COMMANDQ=1 will result in the commands being single-threaded on one queue, MAX_COMMANDQ =2 will allow two task queues, and so forth.

Note: Each command queued for parsing occupies 80 bytes plus the length of the command in extended private.

Format MAX_COMMANDQ=nnnn

Where:

nnnn

Is a value from 1 through 4096. If you omit this parameter, MAX_COMMANDQ defaults to 500.

Example MAX_COMMANDQ=4096

MAX_QUERY 123

Configuration

MAX_QUERY

Description The optional MAX_QUERY initialization parameter specifies the maximum number of lines that may be displayed for #SQ VOL, #SQ MIRROR, and #SQ STATE commands.

Note: This parameter affects only the console commands; it does not have any effect on commands issued during batch processing.

Format MAX_QUERY=nnnn

Where:

nnnn

Is a value from 1 through 8192. If you omit MAX_QUERY, it defaults to 512.

Note: If the Symmetrix being displayed has more than 8192 devices, use command syntax specifying the starting Symmetrix device number. For example:

#SQ VOL,cuu,count,startingdev#

Console buffering should be considered when setting MAX_QUERY.

Example MAX_QUERY=256


Configuration

MESSAGE_LABELS

Description The optional MESSAGE_LABELS initialization parameter specifies whether SRDF Host Component is to attach labels to the end of certain SRDF Host Component messages to make it easier to associate responses with commands when multiple commands are running concurrently.

Format MESSAGE_LABELS=NONE|SYMMETRIX_SERIAL|MVS_CUU|COMMAND_SEQ

Where:

NONE

Specifies that labels are not attached to messages.

If you do not specify MESSAGE_LABELS, MESSAGE_LABELS defaults to NONE.

SYMMETRIX_SERIAL

Specifies the last five digits of the serial number of the Symmetrix to which the command was directed. This number is appended to the end of command status messages. The label takes the form of “(SER:nnnnn).”

MVS_CUU

Specifies the mainframe device number to which the command was directed. This number is appended to the end of command status messages. If a range of devices was selected, the first device number in the range is used. The label takes the form of “(CUU:xxxx).”

COMMAND_SEQ

Specifies the command sequence number assigned at command entry. This number is appended to the end of command status messages. This parameter can be used with the SHOW_COMMAND_SEQ#=YES initialization statement to make it easier to identify in the log which messages are associated with which commands.

Note: It is recommended that you use COMMAND_SEQ for issues that require contacting the EMC Customer Support Center for technical assistance.

Example MESSAGE_LABELS=SYMMETRIX_SERIAL

MESSAGE_PROCESSING 125

Configuration

MESSAGE_PROCESSING

Description SRDF Host Component has the ability to intercept and interpret certain Service Information Messages (SIMs). The SIMs may then be saved. The required MESSAGE_PROCESSING initialization parameter indicates whether or not message processing is enabled.

Format MESSAGE_PROCESSING=YES[,nnn]|LOG][,nnn]|NO

Where:

YES[,nnn]

Enables message processing. Optionally, uses nnn as the size of the message table. The value of nnn can range from 1 through 512.

LOG[,nnn]

Enables message processing and also sends the EMCQM821 message to the HCLOG dataset (if it is allocated). Optionally, uses nnn as the size of the message table. The value of nnn can range from 1 through 512.

The message log is displayed using the #SQ MSG command.

Note: “HCLOG” on page 114 provides more information about the HCLOG dataset.

NO

Disables message processing.

Example MESSAGE_PROCESSING=YES,20MESSAGE_PROCESSING=LOG,400


Configuration

MSC_ACTIVATE_MS

Description The MSC_ACTIVATE_MS initialization parameter is optional. MSC_ACTIVATE_MS tells MSC to activate the MSC GROUP after startup in the SCF address space. You must use MSC_ACTIVATE_MS after the MSC_GROUP_NAME parameter and before the MSC_GROUP_END parameter.

Note: The MSC_ACTIVATE_MS parameter is no longer used and is only provided to allow downward compatibility for older environments.

Format MSC_ACTIVATE_MS

Example MSC_ACTIVATE_MS

MSC_ALLOW_INCONSISTENT 127

Configuration

MSC_ALLOW_INCONSISTENT

Description The MSC_ALLOW_INCONSISTENT parameter is optional. MSC_ALLOW_INCONSISTENT instructs the MSC to allow an SRDF/A RDFGRP to join MSC, even if the SRDF/A session is inconsistent.

Note: The default is to not allow an SRDF/A RDFGRP to join MSC until that SRDF/A session is consistent on the secondary side.

You must use the MSC_ALLOW_INCONSISTENT parameter after the MSC_GROUP_NAME parameter and before the MSC_GROUP_END parameter.

Format MSC_ALLOW_INCONSISTENT

Example MSC_ALLOW_INCONSISTENT


Configuration

MSC_CYCLE_TARGET

Description The MSC_CYCLE_TARGET parameter sets the desired length of each cycle in seconds. You can only use MSC_CYCLE_TARGET after the MSC_GROUP_NAME parameter statement and before the MSC_GROUP_END parameter statement.

If you include more than one MSC_CYCLE_TARGET statements in an MSC Group definition, the last one will be the one used.

The higher the value you use, the longer each cycle will be and thus the further behind your secondary side may be. Depending on the Host Throttle value set in the IMPL bin, if you set MSC_CYCLE_TARGET to too large a value, you can cause either:

◆ SRDFA to drop

◆ Your host I/O to be slowed down by the Symmetrix system

Format MSC_CYCLE_TARGET=cycle_length

Where:

cycle_length

Is a value from 3 through 1800 seconds. The default value is 30.

Example MSC_CYCLE_TARGET=30

MSC_GROUP_END 129

Configuration

MSC_GROUP_END

Description The MSC_GROUP_END parameter terminates the definition of an SRDF/A multi-session group. You can only use the MSC_GROUP_END parameter after the MSC_GROUP_NAME parameter and after at least one MSC_INCLUDE_SESSION parameter.

Format MSC_GROUP_END

Example MSC_GROUP_END


Configuration

MSC_GROUP_NAME

Description Use the MSC_GROUP_NAME parameter to define an SRDF/A multi-session definition. MSC_GROUP_NAME is a required key word that starts the definition of the group.

Format MSC_GROUP_NAME=groupname

Where:

groupname

Specifies the name of the group. The groupname can be from 1 through 24 alphanumeric or national (@#$) characters. The groupname must be contiguous and cannot contain blanks in the definition.

The name must be unique for each:

• SRDF/A multi-session group

• SRDF Host Component group

• SCFG group

• SMS group

Note: The groupname should be unique in the first 8 characters of the possible 24 characters. The first 8 characters are recorded and used for identifying the MSC group.

Example MSC_GROUP_NAME=MSCGROUP1

MSC_INCLUDE_SESSION 131

Configuration

MSC_INCLUDE_SESSION

Description Use the MSC_INCLUDE_SESSION statement to include the SRDF/A RDF group in the SRDF/A multi-session group.

The MSC_INCLUDE_SESSION statement can only be used after the MSC_GROUP_NAME statement and before the MSC_GROUP_END statement. Multiple MSC_INCLUDE_SESSION parameters can be included in the MSC definition, or one MSC_INCLUDE_SESSION can incorporate multiple groups.

You must use the GNS format (“Format 2” on page 134) of this parameter if a BCV GNS group is desired for the Auto Recovery procedure.

Format 1 Use this format for MSC and SRDF/Star groups.

MSC_INCLUDE_SESSION=ccuu,(nn,[xx]),(mm),ITRK=aaaaaa,MINDIR=bb,BCV(startup_option,post_recovery_option){,JOBNAME=jobname}

Where:

ccuuSpecifies the z/OS device number in the Symmetrix where the SRDF/A session exists.

nn

Specifies the RDF group to include in the MSC group.

xx

This optional parameter is part of a Cascaded SRDF environment, where xx is the RDF group between site B and site C.

mmThis optional parameter is only used for an SRDF/Star definition. To use this parameter, you also need to use the MSC_STAR statement. In an SRDF/Star definition, this is the RDF group that goes from the SRDF/A secondary Symmetrix to the non-SRDF/A secondary Symmetrix that will be used for failover procedures.


Configuration

IMPORTANT!The following optional override parameters (ITRK, MINDIR, BCV, and JOBNAME) apply to the jobs submitted to recover the specific MSC group—these parameter settings do not apply to the initial automated recovery job that is submitted to perform validation and cleanup.

ITRK=aaaaaaThis optional parameter indicates the number of outstanding R2 invalid tracks on the R1 that the recovery automation uses as a trigger point for activating SRDF/A for this session, where the value of n is multiplied by 1000. Allowable values for nnnnnn are 0-999999.

Note: Any ITRK value specified in MSC_INCLUDE_SESSION will override the global value specified by the SRDFA_AUTO_RECOVER_ITRK parameter.

MINDIR=bbThis optional parameter indicates the number of directors that must be online for this session. Allowable values are 1-255.

Note: Any MINDIR value specified in MSC_INCLUDE_SESSION will override the global value specified by the SRDFA_AUTO_RECOVER_MINDIR parameter.

BCV(startup_option, post_recovery_option)This optional parameter specifies BCV gold copy management options for this session.

Note: Any BCV option specified in MSC_INCLUDE_SESSION will override the global values specified by the SRDFA_AUTO_RECOVER_BCV parameter.


Configuration

startup_option

Defines the desired behavior at the start of the gold copy management routine. Valid states are:

post_recovery_option

Defines the desired state of the BCV relationships at the completion of the SRDF/A recovery operation. Valid states are:

JOBNAME=jobnameThis optional parameter allows you to specify a jobname override to the SRDF Automated Recovery Started Task name. The JOBNAME parameter will override the name of the Started Task for the group recovery tasks.

Note: Any jobname specified here in MSC_INCLUDE_SESSION will override the JCL recovery procedure name specified by the SRDFA_AUTO_RECOVER_PROC parameter.

Examples MSC example:

MSC_INCLUDE_SESSION=A100,(02)

MSC example with ITRK and MINDIR values specified for the session:

MSC_INCLUDE_SESSION=C400,(03),ITRK=997,MINDIR=01

NONE BCV management will be bypassed for this phase.

ESTablish Results in a new PiT (point-in-time) copy on the BCVs. If a BCV is not attached to an R2, a BCV will be established/re-established. If a relationship does not exist, the BCV GNS group (if specified) will be used to choose a BCV. If a relationship does not exist and no BCV GNS group is specified, an error message is issued. After all the BCVs are attached, they will be split.


ESTablish Results in a re-establish of all the BCVs to the R2s.


Configuration

SRDF/Star example:

MSC_INCLUDE_SESSION=A100,(02),(05)

Cascaded SRDF example:

MSC_INCLUDE_SESSION=C120,(63,06)

Cascaded SRDF/Star example:

MSC_INCLUDE_SESSION=8701,(21,F1),(1F)

Format 2 Use this format for a BCV GNS group.

MSC_INCLUDE_SESSION=SCFG(MSC_Gatekeeper_Group,MSC_RA_Group, MSC_BCV_Group)

Where:

SCFG

Indicates that this a GNS-based MSC definition.

MSC_GATEKEEPER_GROUP

Specifies the GNS group containing gatekeeper devices for this Symmetrix.

MSC_RA_GROUP

Specifies the RDF group number of the SRDF/A group to be included in this MSC group.

MSC_BCV_GROUP

Specifies the GNS group containing BCVs to be used to preserve a PiT copy as part of the SRDF Automated Recovery function.

Examples MSC_INCLUDE_SESSION=SCFG(EMCARGK,EMCARMSC1,EMCARBCV1)

The GNS group EMCARGK contains a grouping of valid MSC gatekeeper devices (non-RDF or non-BCV devices that are addressed to the host). At least one device per RDF group should be included in the GNS group.

◆ GNS group EMCARMSC1 contains the GNS group by RDF group.

◆ GNS group EMCARBCV1 contains valid BCV devices to pair up with the R2 devices. If the device size or emulation do not match to the R2 devices or there are not enough BCVs to match to the R2s, the recovery will result in failure.


Configuration

The following example shows a gatekeeper definition:

DEFINE GROUP 'EMCARGK' - INCLUDE DEVICE SYMM = 000187990175,(166-16F,170-177) - INCLUDE DEVICE SYMM = 000190300344,(040,048-04F) - INCLUDE DEVICE SYMM = 000190300351,(030-37) - INCLUDE DEVICE SYMM = 000190300097,(040,048-04F) DISPLAY GROUP 'EMCARGK'

The following example shows an RDF group definition:

DEFINE GROUP 'EMCARMSC1' - INCLUDE RDF GROUP = 000187990175,(LCL=01) DISPLAY GROUP 'EMCARMSC1'

The following example shows a BCV group definition:

DEFINE GROUP 'EMCARBCV1' - INCLUDE DEVICE SYMM = 000187900699,(A0-AF,B0-BF) DISPLAY GROUP 'EMCARBCV1'

The following example shows a GNS group definition that incorporates multiple RDF groups:

DEFINE GROUP 'EMCARMSCX' - INCLUDE RDF GROUP = 000187990175,(LCL=01) - INCLUDE RDF GROUP = 000187990175,(LCL=02) - INCLUDE RDF GROUP = 000187990876,(LCL=01) DISPLAY GROUP 'EMCARMSCX

Note: The EMC ResourcePak Base for z/OS Product Guide provides additional information on GNS groups.


Configuration

MSC_STAR

Description This parameter is only used when defining an SRDF/Star definition.

When you use MSC_STAR, you must also use the optional part of the MSC_INCLUDE_SESSION statement. You must use the MSC_STAR statement after the MSC_GROUP_NAME statement and before the MSC_GROUP_END statement.

Format MSC_STAR=cgrpname

Where:

cgrpname

Is the name of the consistency group protecting the non-SRDF/A mirror of the concurrent RDF device.

Example MSC_STAR=STARCGRP

MSC_VALIDATION 137

Configuration

MSC_VALIDATION

Description When running MSC in SRDF/Star mode, the protection level on all of the devices in the SRDF/Star configuration can be validated. All devices in an SRDF/Star configuration (that is, concurrent R1, SRDF/A R2, and the synchronous R2) will be checked to ensure that they are locally protected in some manner. If any device is found that does not meet the protection check, then the action to take is based on this parameter setting.

Format MSC_VALIDATION=WARN|FAIL|NONE

Where:

WARN

Issues a warning message if devices are found that fail the protection check. This is the default setting.

FAIL

Does not allow the SRDF/Star definition to complete when the protection check is made and any device does not meet the requirements.

NONE

Bypasses the protection check.


Configuration

MSC_WEIGHT_FACTOR

Description The MSC_WEIGHT_FACTOR parameter is used to weight the redundant MSC servers.

◆ Setting MSC_WEIGHT_FACTOR = 0 will cause the server to immediately attempt the MSC cycle switch process once all RDF groups in the MSC group are ready to cycle switch.

In an SRDF/Star configuration, the server running with a weight factor of 0 will also perform the SDDF processing necessary for the differential resynchronization.

◆ Setting MSC_WEIGHT_FACTOR to a value greater than 0 instructs the MSC server to wait the value (in seconds) after all RDF groups are ready to cycle switch, before attempting to cycle switch.

In an SRDF/Star configuration, the server running with a weight factor greater than 0 will only attempt to cycle switch. The SDDF processing will not be done.

Single MSC server

If you are running a single MSC server, set MSC_WEIGHT_FACTOR = 0.

Multiple MSC servers

If you are running multiple MSC servers for a single MSC group, set one to a primary server (n=0) and set the other servers to a secondary server (n >0). The recommended values for secondary MSC servers are n=2 or n=3.

You must use the MSC_WEIGHT_FACTOR statement after the MSC_GROUP_NAME statement and before the MSC_GROUP_END statement.

If more than one MSC server is running an MSC Group, each server has the MSC_WEIGHT_FACTOR. Regardless of the MSC_WEIGHT_FACTOR, all MSC servers running an MSC group will verify and attempt to cycle switch. Each MSC server will verify that all RDF groups in the MSC group are ready to cycle switch. When all RDF groups are ready to cycle switch, then the MSC servers will examine the MSC_WEIGHT_FACTOR.

MSC_WEIGHT_FACTOR 139

Configuration

◆ If the MSC_WEIGHT_FACTOR = 0 then the server will immediately attempt to do the cycle switch. If more than one MSC server has MSC_WEIGHT_FACTOR = 0, then each one will immediately attempt to perform the cycle switch.

◆ If the MSC_WEIGHT_FACTOR > 0 then the MSC server will wait the value of MSC_WEIGHT_FACTOR in seconds and then attempt to cycle switch.

Note that all MSC servers can tell if another device has already done the cycle switch and continue to the next step.

If multiple MSC servers are running an MSC group and one goes offline, then the others continue the process. There is no takeover required since all MSC servers are already doing the cycle switch process.

If the server running with MSC_WEIGHT_FACTOR = 0 goes away and another MSC server with MSC_WEIGHT_FACTOR > 0 actually performs the cycle switch, then the target cycle time will be elongated by the MSC_WEIGHT_FACTOR. For example, if a 15 second cycle target is required and a MSC server running with MSC_WEIGHT_FACTOR = 2 is used, then a 17 second cycle target will occur.

Format MSC_WEIGHT_FACTOR=n

Where:

n

Is a value of 0, 1, 2, or 3. The default value is 0 (by omitting the parameter you get MSC_WEIGHT_FACTOR=0).

Example MSC_WEIGHT_FACTOR=0


Configuration

OPERATOR_VERIFY

Description The optional OPERATOR_VERIFY initialization parameter indicates whether or not operator verification has been enabled.

Format OPERATOR_VERIFY=ALL|CRITICAL|NONE

Where:

ALL

Specifies that operator verification is requested for all command types. If you do not specify OPERATOR_VERIFY, the OPERATOR_VERIFY parameter defaults to ALL.

CRITICAL

Specifies that operator verification should be requested for the following commands:

• #SC VOL command actions:

• #SC RDFGRP command actions:

• #SC SRDFA command actions:

NONE

Specifies that no operator verification is requested.

CASCRE CASDEL CASSWAP

CREATEPAIR DELETEPAIR HDELETEPAIR

HMOVEPAIR HSWAP INVALIDATE

ITA MOVEPAIR NITA

OFFLINE ONLINE R/W

REFRESH RNG-REFRESH SWAP

VALIDATE

ADD DELETE MODIFY

DEACT_TO_ADCOPY DEACT_TO_ADCOPY_DISK DROP

PEND_DEACT PEND_DROP TOL_ON

TOL_OFF

OPERATOR_VERIFY 141

Configuration

Example OPERATOR_VERIFY=CRITICAL

Note: The ISPF interface allows you to override the OPERATOR_VERIFY feature so as to suppress messages that would otherwise be written to the console as Write To Operator with Reply messages (WTORs). These messages are generated as a direct result of commands you enter when the OPERATOR_VERIFY parameter is specified as ALL or CRITICAL. The USER_VERIFICATION and USER_VERIFICATION_TIMEOUT parameters activate this feature.


Configuration

REGISTER_COMMAND_PREFIX

Description The optional REGISTER_COMMAND_PREFIX initialization parameter specifies whether or not to register the command prefix and the scope of the registration. If you specify REGISTER_COMMAND_PREFIX, you must place it before the COMMAND_PREFIX parameter.

When the REGISTER_COMMAND_PREFIX parameter appears in the initialization deck before the COMMAND_PREFIX parameter, it alters the way the COMMAND_PREFIX parameter is parsed. The full 1 through 8 character string on the COMMAND_PREFIX parameter is used as the command prefix string regardless of the string contents.

If no REGISTER_COMMAND_PREFIX parameter appears in the initialization deck before the command prefix parameter, the command prefix is parsed for the ,REG parameter. In this case, the command prefix cannot contain a comma.

When the REGISTER_COMMAND_PREFIX parameter appears in the initialization deck after the COMMAND_PREFIX parameter, it is ignored.

Format REGISTER_COMMAND_PREFIX=NO|YES|SYSPLEX|SYSTEM

Where:

NO

Indicates the command prefix is not to be registered.

YES

Indicates the command prefix is to be registered SCOPE=SYSPLEX.

Note: This has the same effect as specifying a value for SYSPLEX.

SYSPLEX

Indicates the command prefix is to be registered SCOPE=SYSPLEX.

SYSTEM

Indicates the command prefix is to be registered SCOPE=SYSTEM.

REGISTER_COMMAND_PREFIX 143

Configuration

Example REGISTER_COMMAND_PREFIX=YES COMMAND_PREFIX=@,REG

In the previous example, the command prefix is set to the string “@,REG.” However, if the user omitted the REGISTER_COMMAND_PREFIX parameter, the command prefix would be set to @ and the prefix would be registered.


Configuration

SAF_CLASS

Description The optional SAF_CLASS initialization parameter specifies the SAF class name (from 1 through 8 characters). The SAF class name is used to validate access to SRDF Host Component commands.

Format SAF_CLASS=SAF class name

Where:

SAF class name

Specifies the SAF class name. If you do not specify SAF_CLASS, the SAF_CLASS parameter defaults to a class name of DATASET.

Note: If this parameter is set to or allowed to default to DATASET, you must define the resource as a generic dataset profile and generic dataset checking must be active.

Example SAF_CLASS=HC#CLASS

SAF_PROFILE 145

Configuration

SAF_PROFILE

Description The optional SAF_PROFILE initialization parameter specifies the resource name to be used for SAF validation calls. The resource name can be from 1 through 44 characters.

Note: The resource name is limited to 35 characters in length when using the APPEND_COMMAND=YES subparameter.

Format SAF_PROFILE=EMC.VALIDATE.ACCESS[,APPEND_COMMAND=YES]

Where:

EMC.VALIDATE.ACCESS

Specifies that access must be validated. If this parameter is not specified, SAF_PROFILE defaults to a resource name of EMC.VALIDATE.ACCESS.

APPEND_COMMAND=YES

The optional APPEND_COMMAND=YES subparameter provides more granularity in RACF validations. This option allows you to have a security check related to an SRDF Host Component command that you entered. If this option is chosen, any SRDF Host Component command that you enter is appended to your SAF profile resource name.

Comments Table 3 provides a listing of SRDF Host Component commands that are returned along with their corresponding suffixes when you issue a command with the APPEND_COMMAND option specified for the parameter.

Table 3 SRDF Host Component commands/suffixes (page 1 of 2)

Command Suffix

SQ[UERY] ADC SQADC

SQ[UERY] CNFG SQCNFG

SQ[UERY] DSTAT SQDSTAT

SQ[UERY] GLOBAL SQGLOBAL

SQ[UERY] LINK SQLINK

SQ[UERY] MIRROR SQMIRROR


Configuration

SQ[UERY] MSG SQMSG

SQ[UERY] RAID SQRAID

SQ[UERY] RAID10 SQRAID10



SQ[UERY] RDFGRP SQRDFGRP

SQ[UERY] SRDFA SQSRDFA

SQ[UERY] SRDFA_DSE SQSRDFAD

SQ[UERY] SRDFA_VOL SQSRDFAV

SQ[UERY] SSID SQSSID

SQ[UERY] STATE SQSTATE

SQ[UERY] VOL SQVOL

SC[ONFIG] CNFG SCCNFG

SC[ONFIG] GLOBAL SCGLOBAL

SC[ONFIG] LINK SCLINK

SC[ONFIG] MSG SCMSG

SC[ONFIG] RDFGRP SCRDFGRP

SC[ONFIG] RECOVER SCRECOVER

SC[ONFIG] SRDFA SCSRDFA

SC[ONFIG] SRDFA_DSE SCSRDFAD

SC[ONFIG] VOL SCVOL

STOP STOP

TF CONFIG TFCONFIG

TF QUERY TFQUERY

TF OTHER TFCONFIG

Table 3 SRDF Host Component commands/suffixes (page 2 of 2)

Command Suffix

SAF_PROFILE 147

Configuration

Example SAF_PROFILE=EMC.VALIDATE.ACCESS,APPEND_COMMAND=YES

Command issued:

#SQ VOL,0F00,ALL

Validation is performed for the resource name:

EMC.VALIDATE.ACCESS.SQVOL


Configuration

SECURITY_CONFIG

Description The required SECURITY_CONFIG initialization parameter specifies the security associated with the #SC commands.

Format SECURITY_CONFIG=ANY|MASTER|SAF|(SAF,ANY)|(SAF,MASTER)

Where:

ANY

Specifies that commands are accepted from any mainframe console.

MASTER

Specifies that commands are accepted from the master console.

SAF

Specifies the use of the SAF interface to validate #SC commands.

(SAF,ANY)

Specifies the use of the SAF interface to validate #SC commands, unless issued from a mainframe console. #SC commands can be issued from any mainframe console.

(SAF,MASTER)

Specifies the use of the SAF interface to validate #SC commands unless issued from a z/OS console. #SC commands can only be issued from a z/OS master console.

Example SECURITY_CONFIG=MASTER

SECURITY_QUERY 149

Configuration

SECURITY_QUERY

Description The required SECURITY_QUERY initialization parameter specifies the security associated with the #SQ commands.

Format SECURITY_QUERY=ANY|MASTER|SAF|(SAF,ANY)|(SAF,MASTER)

Where:

ANY

Specifies that commands are accepted from any mainframe console.

MASTER

Specifies that commands are accepted from the master console.

SAF

Specifies the use of the SAF interface to validate #SQ commands.

(SAF,ANY)Specifies the use of the SAF interface to validate #SC commands unless issued from an mainframe console. #SQ commands can be issued from any mainframe console.

(SAF,MASTER) Specifies the use of the SAF interface to validate #SQ commands unless issued from a z/OS console. #SQ commands can only be issued from a z/OS master console.

Example SECURITY_QUERY=ANY


Configuration

SHOW_COMMAND_SEQ#

Description The SHOW_COMMAND_SEQ# initialization parameter indicates whether you want to display the sequence numbers of entered SRDF Host Component commands on the EMCMN00I message.

Note: It is recommended that you enable this parameter for issues that require contacting the EMC Customer Support Center for technical assistance.

Format SHOW_COMMAND_SEQ#=YES|NO

Where:

YES

Displays sequence numbers of entered SRDF Host Component commands on the EMCMN00I message. The command sequence number appears enclosed in parenthesis before the command text.

NO

Does not display sequence numbers of entered SRDF Host Component commands on the EMCMN00I message. The default value for the SHOW_COMMAND_SEQ# parameter is NO.

Example SHOW_COMMAND_SEQ#=YES

SINGLE_CONCURRENT 151

Configuration

SINGLE_CONCURRENT

Description The SINGLE_CONCURRENT initialization parameter allows each leg of an R11/R21/R22 relationship to be displayed. For the following commands, only the mirror belonging to RDF group rdfgroup# appears in the command output when device cuu has multiple remote mirrors:

◆ #SQ VOL,cuu,RA(rdfgroup#)

◆ #SQ STATE,cuu,RA(rdfgroup#)

◆ #SQ VOL,LCL(cuu,rdfgroup#)

◆ #SQ VOL,RMT(cuu),RA(rdfgroup#)

Note: If any other format of the command is used, both mirrors of a concurrent R1 appear.

Format SINGLE_CONCURRENT

Example SINGLE_CONCURRENT


Configuration

SMFREC

Description The optional SMFREC initialization parameter is used to activate the z/OS Systems Management Facilities (SMF) recording by SRDF Host Component.

An SMF record is written for each SRDF Host Component command issued. The record includes the time of the command, the console ID from which the command was issued, the userID that entered the command, and the command text before and after ALIAS substitution.

Note: If this statement is omitted, the SMF option is not active, and no SMF records are written by SRDF Host Component. The SMF record layout is provided in the SRDF SAMPLIB library member RDFSMFR.

Note: When specifying the SMFREC parameter, select an unassigned SMF record number in the range reserved for users (from 128 through 255).

Format SMFREC=nnn

Where:

nnn

Indicates the number of the SMF record to be written, a decimal number from 128 to 255.

Example SMFREC=255

SORT_BY_COMMAND 153

Configuration

SORT_BY_COMMAND

Description Use the SORT_BY_COMMAND initialization parameter to determine the display sort order. When you use SORT_BY_COMMAND, the display sort order depends on the query command you use:

Format SORT_BY_COMMAND

Example SORT_BY_COMMAND

Command Displays output according to

#SQ VOL,cuu MVSCUU

#SQ VOL,LCL(cuu) SYMDEV

#SQ VOL,RMT(cuu) SYMDEV

#SQ VOL,V(volser) VOLSER

#SQ VOL,SSID(ssid) SYMDEV

#SQ VOL,G(groupname) Refer to the following descriptions for SORT_BY_VOLSER and SORT_BY_MVSCUU.


Configuration

SRDFA_AUTO_RECOVER

Description This parameter enables the SRDF Automated Recovery facility for SRDF/A environments.

Note: This parameter will initiate SRDF Automated Recovery only if SRDF/A is not active for at least one of the RDF groups in the MSC group.

Format SRDFA_AUTO_RECOVER=YES|NO|PROMPT

Where:

YES

Indicates SRDF Automated Recovery will execute following SRDF/A failures. SRDF/A drops initiated via SC SRDFA PEND_DROP will not invoke recovery automation.

NO

Indicates SRDF Automated Recovery will not be invoked upon SRDF/A failures. This is the default setting.

PROMPT

Indicates SRDF Automated Recovery will issue a message requiring operator confirmation before proceeding with recovery after SRDF/A failures.

Example SRDFA_AUTO_RECOVER=YES

SRDFA_AUTO_RECOVER_BCV 157

Configuration

SRDFA_AUTO_RECOVER_BCV

Description This parameter specifies BCV gold copy management options.

Note: The SRDFA_AUTO_RECOVER_BCV statement can be overridden by specifying BCV((startup_option,post_recovery_option) in the MSC_INCLUDE_SESSION statement.

Format SRDFA_AUTO_RECOVER_BCV(startup_option,post_recovery_option)

Where:

startup_option

Defines the desired behavior at the start of the gold copy management routine. The valid states are:

post_recovery_option

Defines the desired state of the BCV relationships at the completion of the SRDF/A recovery operation. The valid states are:

Example SRDFA_AUTO_RECOVER_BCV(EST,NONE)


ESTablish Results in a new PiT (point-in-time) copy on the BCVs. If a BCV is not attached to an R2, a BCV will be established/re-established. If a relationship does not exist, the BCV GNS group (if specified) will be used to choose a BCV. If a relationship does not exist and no BCV GNS group is specified, an error message will be issued. After all the BCVs are attached, they will be split. This is the default setting for startup_option.

NONE BCV management will be bypassed for this phase. This is the default setting for post_recovery_option.

ESTablish Results in a re-establish of all the BCVs to the R2s.


Configuration

SRDFA_AUTO_RECOVER_ITRK

Description This parameter allows you to specify the number of outstanding R2 invalid tracks on the R1 that the recovery automation will use as a trigger point for activating SRDF/A.

Ensure that the number of invalid tracks you specify considers the cache limit settings in the Symmetrix system. If SRDF/A is started, but reaches the cache limit, SRDF/A will drop again.

Note: The SRDFA_AUTO_RECOVER_ITRK statement can be overridden by specifying ITRK=aaaaaa in each MSC_INCLUDE_SESSION statement.

Format SRDFA_AUTO_RECOVER_ITRK=nnnnnn

Where:

nnnnnn

Indicates the number of outstanding R2 invalid tracks on the R1 that the recovery automation uses as a trigger point for activating SRDF/A, where the value of n is multiplied by 1000. Allowable values for nnnnnn are 0-999999. The default setting is 30 (which represents 30,000).

Example SRDFA_AUTO_RECOVER_ITRK=100

SRDFA_AUTO_RECOVER_MINDIR 159

Configuration

SRDFA_AUTO_RECOVER_MINDIR

Description This parameter allows you to specify a minimum number of directors that must be online for the automation to begin execution.

Note: The SRDFA_AUTO_RECOVER_MINDIR statement can be overridden by specifying MINDIR=bb in each MSC_INCLUDE_SESSION statement.

Format SRDFA_AUTO_RECOVER_MINDIR=nn

Where:

nn

Indicates the number of directors that must be online. Allowable values are 1-255. The default setting is 1.

Example SRDFA_AUTO_RECOVER_MINDIR=4


Configuration

SRDFA_AUTO_RECOVER_PROC

Description This parameter allows you to change the name of the JCL recovery procedure.

Note: The SRDFA_AUTO_RECOVER_PROC statement can be overridden by specifying jobname=jobname in each MSC_INCLUDE_SESSION statement.

Format SRDFA_AUTO_RECOVER_PROC=procname

Where:

procname

Indicates the name of the JCL recovery procedure. An EBCDIC name from 1 to 8 characters is allowed. The default name is EMCRCVRY.

Note: A sample EMCRCVRY procedure is included in the SAMPLE file.

Example SRDFA_AUTO_RECOVER_PROC=EMCRCV1

SUBSYSTEM_NAME 161

Configuration

SUBSYSTEM_NAME

Description The required SUBSYSTEM_NAME initialization parameter must be the first noncommented initialization parameter. It indicates the z/OS subsystem name specified in IEFSSNxx for use by SRDF Host Component.

Format SUBSYSTEM_NAME=name

Where:

name

Indicates the name of the subsystem; it can be up to four characters.

Example SUBSYSTEM_NAME=EMC2


Configuration

SYNCH_DIRECTION_ALLOWED

Description The optional SYNCH_DIRECTION_ALLOWED initialization parameter sets valid values for synchronization direction command processing that can be specified in the SYNCH_DIRECTION_INIT initialization parameter and in the#SC GLOBAL,SYNCH_DIRECTION command.

Note: Chapter 6, “Recovery Procedures,” provides more information.

Format SYNCH_DIRECTION_ALLOWED=R1>R2|R1<R2|R1<>R2|NONE

Where:

R1>R2

Only allows the synchronization direction to be set to source (R1)→target (R2) or NONE.

If you do not specify SYNCH_DIRECTION_ALLOWED, SYNCH_DIRECTION_ALLOWED defaults to R1>R2.

R1<R2

Only allows the synchronization direction to be set to target (R2)→source (R1) or NONE.

R1<>R2

Allows the synchronization direction to be set to any valid setting.

NONE

Only allows the synchronization direction to be set to NONE.

Note: When you specify NONE for SYNCH_DIRECTION_ALLOWED, the #SC VOL command VALIDATE, INVALIDATE, REFRESH, and RNG-REFRESH parameters do not function.

Example SYNCH_DIRECTION_ALLOWED=R1>R2

SYNCH_DIRECTION_INIT 163

Configuration

SYNCH_DIRECTION_INIT

Description The optional SYNCH_DIRECTION_INIT initialization parameter sets the synchronization direction at the time SRDF Host Component is started.

You can change the current SYNCH_DIRECTION using the #SC GLOBAL,SYNCH_DIRECTION command.

Note: This parameter must not conflict with SYNCH_DIRECTION_ALLOWED and is therefore subject to all constraints set by SYNCH_DIRECTION_ALLOWED.

Format SYNCH_DIRECTION_INIT=R1>R2|R1<R2|NONE

Where:

R1>R2

Specifies that the REFRESH, RNG-REFRESH, and VALIDATE actions on the #SC VOL command may only be used on a target (R2) volume and INVALIDATE may only be used on a source (R1) volume.

R1<R2

Specifies that the REFRESH, RNG-REFRESH, and VALIDATE actions on the #SC VOL command may only be used on a source (R1) volume and INVALIDATE may only be used on a target (R2) volume.

NONE

Specifies no synchronization direction.

If you do not specify SYNCH_DIRECTION_INIT, SYNCH_DIRECTION_INIT defaults to NONE.

Example SYNCH_DIRECTION_INIT=R1<R2


Configuration

USER_VERIFICATION

Description The optional USER_VERIFICATION initialization parameter works in conjunction with the OPERATOR_VERIFY parameter to indicate if a user entering SRDF Host Component commands from the REXX Interface will have the ability to respond to messages requesting permission to proceed.

Format USER_VERIFICATION=YES|NO

Where:

YES

If the REXX interface supports this feature, Write To Operator with Reply messages (WTORs) normally issued due to the OPERATOR_VERIFY setting will be bypassed and the TSO/REXX user will be prompted for permission to proceed.

NO

TSO/REXX users will not have the ability to respond to messages requesting permission to proceed.

Examples USER_VERIFICATION=YESUSER_VERIFICATION=NO

USER_VERIFICATION_TIMEOUT 165

Configuration

USER_VERIFICATION_TIMEOUT

Description The USER_VERIFICATION_TIMEOUT parameter specifies the amount of time that the TSO/REXX user has to reply before a timeout occurs. If a timeout occurs, then processing proceeds as if the user replied CANCEL to the request.

Format USER_VERIFICATION_TIMEOUT=minutes | (minutes,seconds)

Examples USER_VERIFICATION_TIMEOUT=5USER_VERIFICATION_TIMEOUT=(2,30)


Configuration

VONOFF_BLOCKED

Description If the VONOFF_BLOCKED initialization parameter is present, then the #SC VOL ONLINE and #SC VOL OFFLINE commands will be blocked.

Format VONOFF_BLOCKED

Example VONOFF_BLOCKED

VONOFF_OFF_ONLY 167

Configuration

VONOFF_OFF_ONLY

Description If the VONOFF_OFF_ONLY initialization parameter is present, then the #SC VOL ONLINE command will be blocked.

Format VONOFF_OFF_ONLY

Example VONOFF_OFF_ONLY


Configuration

VONOFF_ON_ONLY

Description If the VONOFF_ON_ONLY initialization parameter is present, then the #SC VOL OFFLINE command will be blocked.

Format VONOFF_ON_ONLY

Example VONOFF_ON_ONLY

VONOFF_R1_ONLY 169

Configuration

VONOFF_R1_ONLY

Description If the VONOFF_R1_ONLY initialization parameter is present, then the #SCVOL ONLINE and #SC VOL OFFLINE commands will be done only on R1 devices.

Format VONOFF_R1_ONLY

Example VONOFF_R1_ONLY


Configuration

VONOFF_R2_ONLY

Description If the VONOFF_R2_ONLY initialization parameter is present, then the #SC VOL ONLINE and #SC VOL OFFLINE commands will be done only on R2 devices.

Format VONOFF_R2_ONLY

Example VONOFF_R2_ONLY

VONOFF_STATUS_WAIT 171

Configuration

VONOFF_STATUS_WAIT

Description The VONOFF_STATUS_WAIT initialization parameter specifies the amount of time to let the #SC VOL ONLINE or #SC VOL OFFLINE command run before issuing a status. SRDF Host Component issues a preliminary status every xxx seconds until the command completes, at which time it will issue a final status.

Format VONOFF_STATUS_WAIT=xxx

Where:

xxx

Can be set from 10 to 120 seconds, where 30 seconds is the default.

Example VONOFF_STATUS_WAIT=30


Configuration

Command Reference 173

4

This chapter describes the SRDF Host Component query (SQ) and configuration (SC) commands. Topics include:

◆ Introduction ...................................................................................... 175◆ Conventions ...................................................................................... 176◆ Getting help ...................................................................................... 177◆ Common parameters ....................................................................... 178◆ #SQ ADC ........................................................................................... 180◆ #SQ CNFG......................................................................................... 184◆ #SQ DSTAT........................................................................................ 190◆ #SQ GLOBAL.................................................................................... 196◆ #SQ LINK .......................................................................................... 200◆ #SQ MIRROR.................................................................................... 208◆ #SQ MSG ........................................................................................... 217◆ #SQ RAID .......................................................................................... 220◆ #SQ RAID5 ........................................................................................ 223◆ #SQ RAID6 ........................................................................................ 227◆ #SQ RAID10 ...................................................................................... 231◆ #SQ RDFGRP .................................................................................... 234◆ #SQ SRDFA ....................................................................................... 242◆ #SQ SRDFA_DSE.............................................................................. 262◆ #SQ SRDFA_VOL............................................................................. 270◆ #SQ SSID............................................................................................ 276◆ #SQ STATE ........................................................................................ 278◆ #SQ VOL............................................................................................ 285◆ #SC CNFG ......................................................................................... 299◆ #SC GLOBAL.................................................................................... 301◆ #SC LINK........................................................................................... 305◆ #SC MSG............................................................................................ 306

Command Reference


Command Reference

◆ #SC RDFGRP .................................................................................... 307◆ #SC RECOVER ................................................................................. 315◆ #SC SRDFA ....................................................................................... 316◆ #SC SRDFA_DSE.............................................................................. 320◆ #SC VOL............................................................................................ 324◆ #STOP ................................................................................................ 362◆ #TF...................................................................................................... 363

Introduction 175

Command Reference

IntroductionYou can issue SRDF Host Component commands to both local and remote Symmetrix systems. Commands destined for remote Symmetrix systems are transmitted via local Symmetrix systems to remote Symmetrix systems via SRDF links.

Query commands — The SRDF Host Component query (SQ) commands presented in this chapter allow you to view various aspects of SRDF status.

Configuration commands — The SRDF Host Component configuration (SC) commands presented in this chapter allow you to manage the operation of the SRDF environment from a system console.


Command Reference

Conventions

Syntax maps The following notes apply to all SRDF Host Component command syntax maps:

◆ Read the maps left to right and top to bottom.

◆ Command syntax maps start with and end with |.

◆ Lines of syntax that continue to the next line end with ❍, where the circle contains a connecting reference number. A continuation line starts with ❍ , where the circle contains a matching reference number.

◆ Required keyword and symbols are shown in uppercase text.

◆ Information supplied by the user is shown in lowercase italic text.

◆ Options for positional parameters are shown as stacked boxes.

◆ If the map line passes through a stack of parameters, one must be selected.

◆ If the map line connects one keyword with another and passes over a stack of parameters, the parameters are optional.

Command examples The following notes apply to the command examples:

◆ The command examples in this chapter use a variety of command prefix characters, for example, the “#” and “@” characters. When executing the SRDF commands, substitute the command prefix you have specified for your system via the COMMAND_PREFIX initialization parameter.

◆ All Symmetrix device numbers in display output and command response messages are in hex.

◆ All SSIDs are in hex.

Getting help 177

Command Reference

Getting help

#HELP The #HELP command displays all available SRDF Host Component commands.

Syntax #HELP

Parameters None.

Example

EMCMN00I SRDF-HC : (238) #HELP EMCMN25I EMC CONSOLE DISPLAY COMMANDS - V5.5.0 209 #HELP #SC CNFG - SRDF HOST COMPONENT CONFIGURATION FOR A SYMMETRIX #SC GLOBAL - SET GLOBAL SRDF HOST COMPONENT CONFIGURATION CHANGES #SC LINK - MODIFY REMOTE LINK DIRECTORS #SC MSG - CLEAR MESSAGES - FROM SQ MSG BUFFER #SC RDFGRP - MODIFY RDF GROUP STATUS #SC RECOVER - AUTOMATED RECOVERY#SC SRDFA - MODIFY SRDFA STATUS #SC SRDFA_DSE - MODIFY SRDFA_DSE STATUS #SC VOL - MODIFY VOLUMES SRDF STATUS #SQ ADC - DISPLAY ADAPTIVE COPY SKEW VALUES #SQ CNFG - DISPLAY SYMMETRIX CONFIGURATION INFORMATION #SQ DSTAT - DISPLAY SYMMETRIX STATISTICS INFORMATION #SQ GLOBAL - DISPLAY SRDF HC GLOBAL CONFIGURATION #SQ LINK - DISPLAY REMOTE LINK DIRECTOR STATUS #SQ MIRROR - DISPLAY LOGICAL TO PHYSICAL RELATIONSHIP #SQ MSG - DISPLAY CAPTURED SRDF RELATED SERVICE ALERT MESSAGES #SQ RAID - DISPLAY SYMMETRIX RAID CONFIGURATION #SQ RAID5 - DISPLAY SYMMETRIX RAID 5 CONFIGURATION #SQ RAID6 - DISPLAY SYMMETRIX RAID 6 CONFIGURATION #SQ RAID10 - DISPLAY SYMMETRIX RAID10 CONFIGURATION #SQ RDFGRP - DISPLAY SYMMETRIX RDF GROUP CONFIGURATION #SQ SRDFA - DISPLAY SRDFA STATUS #SQ SRDFA_DSE - DISPLAY SRDFA_DSE STATUS #SQ SRDFA_VOL - DISPLAY SRDFA VOLUME(S) STATUS #SQ SSID - DISPLAY SUBSYSTEM ID(S) FOUND BY SRDF HOST COMPONENT #SQ STATE - DISPLAY VOLUME SRDF STATUS SHOWING STACKED STATUSES #SQ VOL - DISPLAY VOLUME SRDF STATUS #TF - TIMEFINDER PASS THROUGH COMMAND - REPLACES SC/SQ BCV #STOP END OF DISPLAY


Command Reference

Common parametersCommand parameters are listed for each SRDF Host Component command in this chapter. Table 4 describes common parameters which are used by many of the commands. Unique command parameters are described under the descriptions of the commands in which they are used.

Table 4 Common command parameters (page 1 of 2)

Name Description

cqname Specifies the name of a command queue into which this command should be placed. Commands in the same queue are processed sequentially, while commands in different queues may be processed concurrently.

cuu Specifies a z/OS device number.

G(groupname) Specifies the name of the SMS or Defined group whose devices are to be displayed or acted upon. Only online devices are selected for display.

Note that both SMS and Defined groups can span multiple Symmetrix systems. If this is the case, multiple display tasks are triggered, one for each Symmetrix system with volumes in the group.

Note: If both an SMS group and a Defined group are defined having the specified name, the command will apply to the Defined group.

LCL Specifies that the operation is directed to the local Symmetrix system in an SRDF configuration; that is, the Symmetrix system on which the specified gatekeeper resides.

mhlist Specifies the RDF group used to identify the remote Symmetrix system. For multihop remote configurations, mhlist can be a single RDF group or a list of up to four hops, separated by periods. For example, an mhlist of 0.1.2 is for three hops. The command hops from the source box on a remote adapter (RA) for rdfgroup# 0 to the first hop box, through the first hop box on an RA for rdfgroup# 1 to the second hop box, and through the second hop box on an RA for rdfgroup# 2 to the third hop box. “Performing operations using a multihop list” on page 369 provides examples illustrating usage of a multihop list.

queue-option Takes effect when a command that is queued on a named command queue fails.• If the P (purge) option is specified, then in the event of a command failure, all

subsequent commands in the same queue are purged. • If the C (continue) option is specified, then if a command fails, processing continues

with the next command in the cqname queue. If you do not specify a queue option on the first command for a particular queue, the default for that queue is P (purge).

Common parameters 179

Command Reference

rdfcuu Specifies the z/OS device number of a source R1 device.

rdfgroup# Specifies the RDF group through which you want to perform an operation. This must be a 1- or 2-digit (hex) value.For concurrent SRDF configurations, a local device may be paired with two remote devices. In this case, rdfgroup# identifies the partner device for which the operation is to be performed. In an LCL(cuu[,rdfgroup#]) operand, rdfgroup# identifies the partner device.

In an RMT(cuu[,mhlist][,rdfgroup#] operand:• If not specified, rdfgroup# defaults to the partner RDF group of the last hop of the

multihop list specified by mhlist. • If specified, rdfgroup# can be the RDF group of the partner device to operate upon or

the character “*” indicating that the action is to be performed upon both partner devices of a concurrent R1 device.

RMT Specifies that the command action is to be directed to a remote Symmetrix system in an RDF configuration.

SCFG(scfgroupname) Specifies the SCF group name whose devices are to be displayed. This parameter specifies that the mirror configurations of devices in the specified SCF group name be displayed.

Note that SCF groups can span multiple Symmetrix systems. If this is the case, multiple display tasks are triggered, one for each Symmetrix system with volumes in the group. SCF groups are defined using the Group Name Services (GNS) feature of SCF.

SSID(ssidnumber) Indicates the subsystem ID and the ssidnumber that identifies the devices to be included when processing the command.

startingdev# Specifies the first or only Symmetrix device number in a range of devices. A Symmetrix device number is always specified in hex.

symdev# Specifies the first or only Symmetrix device number in a range of devices. A Symmetrix device number is always specified in hex.

VOL(volser) Identifies a specific device by its volume serial, or specifies a pattern that is used to include online devices whose volume serials match the pattern. A pattern must start with at least one alphanumeric value and end with an asterisk (*). The asterisk means that characters starting in this position are not considered when determining whether a volser matches the mask.For example, the #SQ VOL,VOL(UG*) command generates a list of all online volumes whose serials start with UG.

Table 4 Common command parameters (page 2 of 2)

Name Description


Command Reference

#SQ ADCThe #SQ ADC command displays the adaptive copy skew values and adaptive copy rate for the specified device(s).

Syntax

#SQ ADC , cuu

,LCL( cuu , rdfgroup#)

,RMT( cuu , mhlist , rdfgroup#)

,G( groupname)

,CQNAME=(cqname,queue-option)

,CQNAME=cqname

,RMT( rdf cuu )

,RMT( cuu,mhlist )

1

1

,count

,ALL

,SCFG(scfgroupname)


,CQNAME=cqname

2

,VOL( volser ) 2

#SQ ADC 181

Command Reference

Parameters count

Specifies the maximum number of devices to display that have adaptive copy information. You can assign a numeric value from 1 to the value specified in the MAX_QUERY initialization parameter, or you can specify ALL. If you do not specify this parameter, count defaults to 1.

This parameter cannot be used with the G(groupname) or SCFG(scfgroupname) parameters.

cqname

See “cqname” on page 178.

cuu

See “cuu” on page 178.

G(groupname)

See “G(groupname)” on page 178.

LCL

See “LCL” on page 178.

mhlist

See “mhlist” on page 178.

queue-option

See “queue-option” on page 178.

rdfgroup#

See“rdfgroup#” on page 179.

rdfcuu

See “rdfcuu” on page 179.

RMT

See “RMT” on page 179.

SCFG(scfgroupname)

See “SCFG(scfgroupname)” on page 179.

VOL(volser)

See “VOL(volser)” on page 179.


Command Reference

Comments Only the source (R1) volumes in Adaptive Copy mode are displayed. The display includes volumes in either Adaptive Copy Disk mode or Adaptive Copy Write-Pending mode.

Example The following example displays the output from an #SQ ADC command:

The fields below the column headers in this example have the indicated meanings:

◆ DV_ADDR SYS

The device’s z/OS device number.

◆ DV_ADDR CH

The first device address (hex) on the channel as specified in the IOCP gen.

◆ SYM_DV

The device’s Symmetrix device number.

◆ SYM_RD

The Symmetrix device number of the device's remote mirror.

◆ SYM_GP

The number of the RDF group to which the device belongs.

◆ ADC MODE

The Adaptive Copy mode in effect. Possible values are AW (Adaptive Copy - Write Pending) or AD (Adaptive Copy - Disk).

@SQ ADC,2150,8EMCMN00I SRDF-HC : (124) @SQ ADC,2150,8EMCGM81I SRDF-HC DISPLAY FOR (124) @SQ ADC,2150,8 698DV_ADDR| SYM |ADC | ADC_CUR | ADC_MAXSYS CH|_DV_ _RD_ GP|MODE| SKEW | SKEW2150 50 0050 0050 00 AD 1227 655352151 51 0051 0051 00 AD 1227 655352152 52 0052 0052 00 AW 0 250002153 53 0053 0053 00 AD 1332 655352154 54 0054 0054 00 AD 1237 655352155 55 0055 0055 00 AW 0 655352156 56 0056 0056 00 AW 0 655352157 57 0057 0057 00 AD 1247 65535END OF DISPLAY

#SQ ADC 183

Command Reference

◆ ADC_CUR SKEW

The current skew value. For Adaptive Copy Write Pending mode, this is the number of write pendings for the target (R2) volume. For the Adaptive Copy Disk mode, this is the number of tracks marked as out-of -synchronization between the source (R1) and the target (R2) volumes.

◆ ADC_MAX SKEW

Adaptive Copy maximum skew value for device(s). Range is from 1 to 65,535 (decimal). This value may be set by means of the #SC VOL command with the ADC_MAX action described in Table 16 on page 327.


Command Reference

#SQ CNFGThe #SQ CNFG command displays the status of the Symmetrix system. It lists the following:

◆ The serial number of the Symmetrix system

◆ The amount of installed cache memory

◆ The controller emulation type

◆ The Symmetrix system model number

◆ The Enginuity level, the SSIDs

◆ Features supported and enabled on the Symmetrix system, such as concurrent RDF or dynamic RDF

◆ The LINK DOMINO status

◆ The local Symmetrix-level SYNCH DIRECTION

◆ The link type

◆ The director type and layout

Syntax

#SQ CNFG , cuu

,CQNAME=( cqname ,queue-option)

,CQNAME= cqname

,LCL( cuu,rdfgroup#)

,RMT( rdf cuu )

1

1

,RMT( cuu,mhlist )

,G( groupname)

,SCFG(scfgroupname)

,RMT( cuu,mhlist,rdfgroup#)

#SQ CNFG 185

Command Reference

Parameters cqname


cuu


G(groupname)


LCL


mhlist


queue-option


rdfgroup#

See “rdfgroup#” on page 179.

rdfcuu


RMT


SCFG(scfgroupname)


Comments Issue #SQ CNFG to determine the location of the remote link directors in your Symmetrix system for the SRDF operations.

To correctly display the configuration information after a Symmetrix Enginuity upgrade, you must shut down and restart SRDF Host Component.


Command Reference

Example The following example displays the output from an #SQ CNFG command:

EMCMN00I SRDF-HC : (41) &SQ CNFG,5500 EMCGM11I SRDF-HC DISPLAY FOR (41) &SQ CNFG,5500 008 SERIAL NUMBER: 000192600296 MEM:24576 MB TYPE:2107 MODEL: VMAX-1 MICROCODE LEVEL: 5874-103 CONCURRENT DRDF: YES 3-DYN-MIRROR SWITCHED-RDF NO-AUTO-LINKS RDFGRP LINKS-OFF-ON-POWERUP LINKS-DOMINO: RDFGRP SYNCH_DIRECTION: GLOBAL LINK: LOCAL SSID(S): 5500 5501 5502 5503 5506 5507 5508 5509 0150 0001 DISK (DA) DIRECTORS: 007(07A) 008(08A) 009(09A) 00A(10A) 017(07B) 018(08B) 019(09B) 01A(10B) 027(07C) 028(08C) 029(09C) 02A(10C) 037(07D) 038(08D) 039(09D) 03A(10D) FICON (EF) DIRECTORS: 047(07E) 048(08E) 069(09G) 06A(10G) FIBRE CHANNEL ADAPTER (SF) DIRECTORS: 049(09E) 04A(10E) FIBRE CHANNEL REMOTE (RF) DIRECTORS: 059(09F) 05A(10F) GIGE OPEN SYSTEMS (SE) DIRECTORS: 067(07G) 068(08G) 077(07H) 078(08H) END OF DISPLAY

The fields below the column headers in this example have the indicated meanings:

◆ SERIAL NUMBER

The Symmetrix system serial number.

◆ MEM

The cache size; if MB, the amount is the number of megabytes; if GB, the amount is the number of gigabytes.

◆ TYPE

The controller emulation type.

◆ MODEL

The Symmetrix system model.

◆ MICROCODE LEVEL

The Enginuity level of the Symmetrix system.

◆ CONCURRENT-RDF

Indicates that concurrent RDF is enabled on the Symmetrix system. This feature allows multiple remote mirrors for a single device to be configured.

#SQ CNFG 187

Command Reference

◆ CONCURRENT DRDF

If YES, indicates that the concurrent Dynamic RDF feature is enabled. This feature allows you to define a second RDF pair for a device already paired with a single remote mirror using the SC VOL CREATEPAIR action, thereby creating an R1 device with two R2 remote mirrors.

◆ 3-DYN-MIRROR

Displays if this feature is enabled on the Symmetrix system.

◆ SWITCHED-RDF


◆ DYNAMIC-RDF


◆ NO-AUTO-LINK-RECOVERY


◆ NO-AUTO-LINK RDFGRP

Displays if this feature may be set at the RDF group level. If not displayed, the NO-AUTO-LINK-RECOVERY feature is set at the Symmetrix system level.

◆ LINKS-OFF-ON-POWERUP


◆ SSID(S)

The SSIDs defined for this Symmetrix system are listed.

◆ LINKS DOMINO

Note: This field is displayed only if the Symmetrix system is configured with SRDF.

LINKS-DOMINO:YES indicates the mode is in effect, LINKS-DOMINO:NO indicates the mode is not in effect, and LINKS-DOMINO:RDFGRP indicates the feature is in effect by RDF group (introduced as a feature of dynamic RDF groups). For more information, see “#SQ RDFGRP” on page 234. LINKS-DOMINO mode is a mode of operation in which all R1 devices go RDF_NOT READY if all links are dropped.

When an SRDF link not running with the LINKS-DOMINO mode fails or is intentionally disabled, the application writing to the R1 is not aware of the failure of writes to the R2. When the link is


Command Reference

restored, the invalid R2 tracks are automatically filled in by the more up-to-date R1 tracks.

Note: There are differences between dropping the links logically (that is, by means of Host Component commands) and physically (for example, by disconnecting link cables) when LINKS-DOMINO is enabled.

Table 5 through Table 7 show the source and target R1 results for various combinations of LINKS-DOMINO and target settings.

Table 5 Source is configured for LINKS-DOMINO=Yes; target=No

Action taken Source R1 Target R1

Links logically dropped at source RDF-NRDY & LNR LNR

Links logically dropped at target RDF-NRDY & LNR LNR

Links physically dropped at source RDF-NRDY & LNR LNR

Links physically dropped at target RDF-NRDY & LNR LNR

Table 6 Source is configured for LINKS-DOMINO=Yes; target=Yes


Links logically dropped at source RDF-NRDY & LNR RDF-NRDY & LNR

Links logically dropped at target RDF-NRDY & LNR RDF-NRDY & LNR

Links physically dropped at source RDF-NRDY & LNR RDF-NRDY & LNR

Links physically dropped at target RDF-NRDY & LNR RDF-NRDY & LNR

Table 7 Source is configured for LINKS-DOMINO=No; target=Yes


Links logically dropped at source LNR RDF-NRDY & LNR

Links logically dropped at target LNR RDF-NRDY & LNR

Links physically dropped at source LNR RDF-NRDY & LNR

Links physically dropped at target LNR RDF-NRDY & LNR

#SQ CNFG 189

Command Reference

◆ SYNCH_DIRECTION

Symmetrix-level synchronization. Values that may appear are R1>R2, R1<R2, NONE, or GLOBAL.

Note: This field is displayed only if the Symmetrix system is configured with SRDF.

◆ LINK

Symmetrix implementation:

Note: This field is only displayed if the Symmetrix system is configured with SRDF.

◆ Symmetrix director types. As shown in the example on Page 186, the director numbers are listed for each type in hex format for SRDF Host Component and for the SymmWin configuration program (in parentheses). Director types that may be displayed are:

DISK (DA) DIRECTORS

ESCON CHANNEL (EA) DIRECTORS

FAST-WIDE SCSI CHANNEL (SA) DIRECTORS

FIBRE CHANNEL ADAPTER (SF) DIRECTORS

FIBRE CHANNEL REMOTE (RF) DIRECTORS

FICON (EF) DIRECTORS

GIGE OPEN SYSTEMS (SE) DIRECTORS

GIGE REMOTE (RE) DIRECTORS

PARALLEL CHANNEL (CA) DIRECTORS

REMOTE LINK (RA) DIRECTORS

REMOTE LINK SOURCE (RA1) DIRECTORS

REMOTE LINK TARGET (RA2) DIRECTORS

LOCAL SRDF campus solution

EXTENDED SRDF extended distance solution


Command Reference

#SQ DSTATThe #SQ DSTAT command displays director statistics. Statistics include writes, number of I/Os, number of I/Os per port, and throughput in kilobytes per port.

Syntax

Parameters cqname


cuu


dir#

Specifies the director number. Values that may appear are from 1 to 80 (hex) or ALL.

G(groupname)


#SQ DSTAT ,cuu

,RMT(rdfcuu)

,SSID(ssidnumber)

,SCFG(scfgroupname)


,CQNAME=cqname

,RMT(cuu,mhlist)

,VOL(volser)

1

1

dir#

,ALL

,G(groupname)

#SQ DSTAT 191

Command Reference

mhlist


queue-option


rdfcuu


RMT


SSID(ssidnumber)

See “SSID(ssidnumber)” on page 179.

VOL(volser)


SCFG(scfgroupname)


Example The following example displays the output from an #SQ DSTAT command:

EMCMN00I SRDF-HC : (4) #SQ DSTAT,6C00,ALL EMCQT00I SRDF-HC DISPLAY FOR (4) @SQ DSTAT,6C00,ALL DIR TYP STATS --- --- --------------------------------------------------------- 33 RE WRT: 2,000 IOS: 2,000 IO0: 1,500 IO1: 500 TP0: 400 TP1: 350 HIT: 250 REQ: 250 MIS: 0 SWP: 0 DWP: 0

3E RE WRT: 14,001 IOS: 14,001 IO0: 7,001 IO1: 7,000 TP0: 850 TP1: 848 HIT: 100 REQ: 800 MIS: 0 SWP: 0 DWP: 0 END OF DISPLAY

The fields shown in this example have the following meanings:

◆ DIR

The director number.

◆ TYP

The type of director.


Command Reference

The mainframe host director types are:

• CA - Parallel channel host adapter

• EA - ESCON channel host adapter

• EF - FICON channel host adapter

The open systems host director types are:

• SA - SCSI host adapter

• FA - Fibre SA host adapter

• F2 - Four-port fibre SA host adapter

• SE - GigE SA host adapter

The disk director types are:

• DA - Disk director

• DF - Disk fibre director

The RDF director types are:

• R1 - ESCON RDF director (RA1 mode)

• R2 - ESCON RDF director (RA2 mode)

• RE - GigE RDF director

• RF - Fibre RDF director

◆ STATS

Statistics for each host director. The set of statistics shown depends upon the director type, and the descriptions for the fields may differ slightly depending upon the director type as well.

#SQ DSTAT 193

Command Reference

Mainframe director type

The format for a mainframe host director statistics display is as follows:

02 EF WRT: 1,098,822 TIO: 508,071 HIT: 9,333REQ: 9,334,466 MIS: 436 SWP: 0DWP: 9,814

The fields for a mainframe host director statistics display are:

Open systems director type

The format for an open systems host director statistics display is as follows:

21 F2 WRT: 0 TIO: 0 IO0: 0IO1: 0 TP0: 0 TP1: 0HIT: 0 REQ: 0 MIS: 0SWP: 0 DWP: 0

The fields for an open systems host director statistics display are:

WRT Number of writes

TIO Total I/Os

HIT Hits

REQ Requests

MIS Read misses

SWP System write pending events

DWP Device write pending events

WRT Number of writes

TIO Total I/Os

IO0 I/Os port 0

IO1 I/Os port 1

TP0 Throughput port 0

TP1 Throughput port 1

HIT Hits

REQ Requests

MIS Read misses

SWP System write pending events

DWP Device write pending events


Command Reference

Disk director

The format for a disk director statistics display is as follows:

01 DF TIO: 60,324 REQ: 21,685 REA: 1,804WRT: 19,881 PFT: 1,362 PTN: 18PTU: 1,029 SMS: 524 LMS: 95RES: 330 PMM: 0 PCR: 0FTT: 27,907

The fields for a disk director statistics display are:

TIO Total I/Os

REQ Requests

REA Reads

WRT Writes

PFT Prefetch tracks

PTN Prefetch tracks not used

PTU Prefetch tracks used

SMS Short misses

LMS Long misses

RES Prefetch restarts

PMM Prefetch mismatches

PCR Perma cache requests

FTT Fall through time

#SQ DSTAT 195

Command Reference

RDF Director

The format for an RDF director statistics display is as follows:

31 RF TIO: 18,696,228 LUC: 0 LU1: 0LU2: 0 RCV: 35 SNT: 24

The fields for an RDF director statistics display are:

TIO Total I/Os

LUC Link utilization counter

LU1 T1 link utilization counter

LU2 T2 link utilization counter

RCV Bytes received:KB - Value is expressed in kilobytesMB - Value is expressed in megabytesGB - Value is expressed in gigabytesTB - Value is expressed in terabytesPB - Value is expressed in petabytes

SNT Bytes sent:KB - Value is expressed in kilobytesMB - Value is expressed in megabytesGB - Value is expressed in gigabytesTB - Value is expressed in terabytesPB - Value is expressed in petabytes


Command Reference

#SQ GLOBALThe #SQ GLOBAL command displays the settings for various global parameters, including the current SRDF Host Component version, the current and allowed synch directions, the status of message processing, the size of the message table, the setting that determines which Host Component commands require operator confirmation, the ddname of the current log file, and whether or not status changes to FBA devices are allowed.

Syntax

Parameters cqname


queue-option


Comments None.

Example The following example displays the output from an #SQ GLOBAL command:

EMCQG00I SRDF-HC DISPLAY FOR (5) &SQ GLOBAL 084 VERSION: 5.6.0 SYNCH_DIR_CURR: R1>R2 MSG_PROC: YES,512 OPER_VERIFY: NONE SYNCH_DIR_ALWD: R1<>R2 LOG_DDNAM: HCLOG1 CONFIG_FBA: ENABLED MAX_QUERY: 4096 MAX_CMDQ: 4096 DISPLAY_SORT_ORDER: SYMDEV MESSAGE_EXIT: INACTIVE HC-PTF: 0001 SCF-VERSION: 5.8.0 SCF-PTF: 0001 CRPAIR_NCPY: STAR

The fields in this example have the following meanings:

◆ VERSION

The SRDF Host Component release version.

#SQ GLOBAL

,CQNAME=cqname


#SQ GLOBAL 197

Command Reference

◆ SYNCH_DIR_CURR

The value of this field indicates the current synchronization direction. This value is initially set by the SYNCH_DIRECTION_INIT parameter, and may be subsequently modified by the #SC GLOBAL,SYNC_DIRECTION command.

◆ MSG_PROC

The value of this field indicates the message processing option in effect. When YES is shown, the number following is the number of messages that can be held in the message table. When LOG is shown, the number following indicates the number of messages that can be held in the message table.

Note that all messages are also written to the HCLOGn file, provided a corresponding dd statement has been included in the JCL. The message processing option is set by he MESSAGE_PROCESSING initialization parameter.

◆ OPER_VERIFY

The value of this field indicates the setting for operator verification of Host Component command specified by the OPERATOR_VERIFY initialization parameter. Possible values are:

• ALL - Operator verification, consisting of a reply of CONTINUE to a WTOR identifying the command being requested, will be required prior to processing of any SC command.

• CRITICAL - Operator verification, consisting of a reply of CONTINUE to a WTOR identifying the command being requested, will be required prior to processing of any SC command deemed critical to Host Component operation.

• NONE - No operator verification of any command will be required.

◆ SYNCH_DIR_ALWD

The value of this field indicates the allowable synchronization directions that may be specified in subsequent #SC GLOBAL,SYNCH_DIRECTION commands specified by the SYNCH_DIRECTION_ALLOWED initialization parameter. One of the values R1<R2, R1>R2, R1<>R2, or NONE will be shown.


Command Reference

◆ LOG_DDNAM

The value shown in this field is the ddname of the current log file if defined by HCLOGx DD statements in the execution JCL. A value is N/A indicates that commands are not being logged. This value may change when the #SC GLOBAL,SWAPLOG command is entered.

◆ DISPLAY_SORT_ORDER

The value of this field shows the order in which devices are displayed in the output from an #SQ VOL, #SQ STATE, or #SQ MIRROR command.

◆ CONFIG_FBA

The value of this field indicates whether #SC VOL commands directed to FBA devices will be processed by SRDF Host Component.

• A value of ENABLED indicates that #SC VOL commands are processed for FBA devices.

• A value of DISABLED indicates that FBA devices are skipped during processing of #SC VOL commands.

The setting can be changed with the #SC GLOBAL command by specifying FBA_ENABLE or FBA_DISABLE.

◆ MAX_QUERY

The value of this field indicates the maximum number of lines that may be displayed by individual #SQ(uery) commands.This value is set by the MAX_QUERY initialization parameter.

◆ MAX_CMDQ

The value of this field indicates the maximum number of Host Component commands that can be queued for parsing. This value is set by the MAX_COMMANDQ initialization parameter.

◆ HC-PTF

The value of this field shows the highest level PTF applied to the running SRDF Host Component.

◆ SCF-VERSION

The value of this field shows the running SCF (ResourcePak Base) version.

#SQ GLOBAL 199

Command Reference

◆ SCF-PTF

Displays the highest level PTF applied to SCF (ResourcePak Base).

◆ CRPAIR_NCPY

This field shows the permitted usage of the NOCOPY option on #SC VOL CREATEPAIR commands. The values that may appear are:

• YES - 'NOCOPY' may be used on any CREATEPAIR action.

• NO - 'NOCOPY' may not be used on any CREATEPAIR action

• STAR - 'NOCOPY' may be used only on CREATEPAIR actions on which the RDF group specified is an SRDF/Star group.

The value of this option is set by means of the ALLOW_CRPAIR_NOCOPY initialization statement.


Command Reference

#SQ LINKThe #SQ LINK command displays the port connection and online/offline status of individual remote link directors. It also displays the number of I/Os per second during a short interval and the total number of I/Os across the link since Host Component discovery of the Symmetrix.

Note: EMC recommends that you use the extended format display option with this command.

Syntax

Parameters cqname


cuu


#SQ LINK

, cuu

,LCL(

cuu

, rdfgroup#)

,G(

groupname)

,SCFG(scfgroupname)

,CQNAME=(

cqname

,queue-option)

,CQNAME=

cqname

,RMT(

rdf

cuu

)

,RMT(

cuu,mhlist

)

1

1

,RMT(

cuu,mhlist,rdfgroup#)

,E

#SQ LINK 201

Command Reference

E

Requests extended format display.

G(groupname)


LCL


mhlist


queue-option


rdfgroup#


rdfcuu


RMT


SCFG(scfgroupname)


Comments Calculating SQ LINK I/O statistics

For this discussion, SRDF Host Component "discovery" of a Symmetrix system refers to the initial building of the Host Component control block structure for each Symmetrix system when it is first encountered. Each local Symmetrix system is discovered when the Host Component address space is started. Each remote Symmetrix is discovered when the first remote Host Component command is issued to that Symmetrix system.

Long-term statistics — When each Symmetrix system is discovered, Host Component records an initial “Total I/O Count” and an initial timestamp for each RDF director. When an SQ LINK command is entered, Host Component collects the current “Total I/O Count” and the current timestamp for each RDF director in the target Symmetrix system.


Command Reference

The long-term statistics for each RDF director in the SQ LINK display are then calculated as follows:

TOTAL-I/O = Current “Total I/O Count” – Initial “Total I/O Count”DD:HH:MM:SS = Current timestamp – Initial timestamp

Short-term statistics — For each discovered Symmetrix system, Host Component collects an interval “Total I/O Count” and an interval timestamp for each RDF director at three minute intervals. For each RDF director, interval statistics for the four most recent intervals are retained.

When an SQ LINK command is entered, Host Component collects the current “Total I/O Count” and the current timestamp for each RDF director in the target Symmetrix system. Host Component also selects the interval timestamp which represents a time duration closest to but not more than ten minutes prior to the current timestamp. The short-term statistics in the SQ LINK display are then calculated as follows:

M:SS = Current timestamp – Selected interval timestamp

RATE = (Current “Total I/O Count” – Selected interval “Total I/O Count” ) ÷ (Current timestamp – Selected interval timestamp )

Figure 15 on page 203 and Figure 16 on page 206 provide illustrations of the SQ LINK command display.

#SQ LINK 203

Command Reference

Example 1 Command #SQ LINK,9800,E issued twice as indicated in Figure 15, results in the following output:

Figure 15 #SQ LINK extended command output for SRDF

The fields below the column headers in Figure 15 have the following meanings:

◆ DR

Director number of the remote link director.

◆ GP

This field shows the RDF group number of the remote link director. For switched SRDF configurations, the field contains SW. For concurrent SRDF, the field contains the RDF group number. Asterisks appear in this field in lines for which the corresponding director has not been online since Host Component was started.

For the first display, directors 0E and 13 are offline and have never been online since SRDF Host Component was started.

EMCQL01I SRDF-HC EXTENDED DISPLAY FOR (15) #SQ LINK,9800,E DR GP _OTHER__S/N_ OD OG RCS | %S M:SS RATE| %L DD:HH:MM:SS TOTAL-I/O 03 SW 000184600045 .. .. FYY | .. 4:37 2 | .. 07:00:08:16 2,402,782 0E ** ************ ** ** FNN | .. 4:37 0 | .. 07:00:08:15 1 10 00 000184600045 10 00 SYY | 00 8:34 0 | 00 07:00:08:36 4,720,468 13 ** ************ ** ** FNN | .. 4:37 0 | .. 07:00:08:16 1 1E SW 000184600045 .. .. FYY | .. 4:37 1 | .. 07:00:08:14 2,395,112 20 01 000184600045 20 01 MYY | 00 8:34 0 | 00 07:00:08:31 212,775 30 02 000184600045 30 02 SYY | 00 8:34 0 | 00 07:00:08:36 1,939,605 40 03 000184600045 40 03 MYY | 00 8:34 0 | 00 07:00:08:31 30,519 END OF DISPLAY

For the second part of the display, director 30 was taken offline, so information may be out of date. Note the asterisk after the serial number.

EMCQL01I SRDF-HC EXTENDED DISPLAY FOR (17) #SQ LINK,9800,E DR GP _OTHER__S/N_ OD OG RCS | %S M:SS RATE| %L DD:HH:MM:SS TOTAL-I/O 03 SW 000184600045 .. .. FYY | .. 4:18 2 | .. 07:00:12:13 2,403,282 0E ** ************ ** ** FNN | .. 4:18 0 | .. 07:00:12:12 1 10 00 000184600045 10 00 SYY | 00 8:15 0 | 00 07:00:12:33 4,720,481 13 ** ************ ** ** FNN | .. 4:18 0 | .. 07:00:12:13 1 1E SW 000184600045 .. .. FYY | .. 8:34 2 | .. 07:00:12:11 2,395,627 20 01 000184600045 20 01 MYY | 00 8:15 0 | 00 07:00:12:28 212,787 30 02 000184600045*** ** SNN | 00 8:15 0 | 00 07:00:12:33 1,939,616 40 03 000184600045 40 03 MYY | 00 8:15 0 | 00 07:00:12:28 30,528 END OF DISPLAY


Command Reference

◆ Other S/N

This field contains the serial number of the partner Symmetrix system. That is, the serial number may show as *’s if you configured the director for switched RDF. This could indicate that there is more than one remote serial number.

◆ OD

This field shows the director number of the remote link director on the partner Symmetrix system. For switched SRDF configurations “..” appears instead of a director number.

◆ OG

This field shows the RDF group number of the remote link director on the partner Symmetrix system. For switched SRDF configurations, “..” appears instead of an RDF group number. For concurrent SRDF, the RDF group number of the target device is displayed.

◆ RCS

This field consists of a three-character string indicating characteristics of the remote link director as follows:

• Character 1 indicates the remote link director type. Values that may appear as character 1 are:

• Character 2 indicates the port connection status. Values that may appear as character 2 are:

• Character 3 indicates the link status of the remote link director. Values that may appear as character 3 are:

M Source remote link director S Target remote link director F Fibre remote link directorE GigE

Y Link path established N No link path established

Y Link is online N Link is not online

#SQ LINK 205

Command Reference

◆ %S

This field shows the percentage of times that the remote link director has returned a status of 'busy' during a short time interval whose duration is given by the value of field M:SS described below.

Note: This field displays “..” for Fibre remote adapters.

◆ M:SS

This field shows the short interval duration during which the average number of I/Os across the link are calculated as shown by field RATE described below, and during which the percent busy is computed as shown by field %S described above. This time duration varies between 0:01 and 9:59 (M:SS). This time duration is calculated by Host Component as described in “Calculating SQ LINK I/O statistics” on page 201.

◆ RATE

This field shows the average number of I/Os per second traversing the remote link director during the short time interval whose duration is given by the value of field M:SS described above.

◆ %L

This field shows the percentage of times that the remote link director has returned a status of 'busy' during a long time interval whose duration is given by the value of field DD:HH:MM:SS described below.

Note: This field displays “..” for Fibre remote adapters.

◆ DD:HH:MM:SS

This field shows the lowest of either the elapsed time since Host Component discovery of the Symmetrix or the last utility reset command issued from the service processor.

◆ TOTAL-I/O

This field shows the total number of IOs across the link since Host Component discovery of the Symmetrix or since the most recent utility reset command issued from the service processor.


Command Reference

Example 2 Command #SQ LINK,3018 displays the output shown in Figure 16:

Figure 16 #SQ LINK command output for SRDF

The fields below the column headers in Figure 16 have the following meanings:

◆ CUU

This field indicates the z/OS device number.

◆ DIR

This field indicates the director number of the remote link director.

◆ RA

This field indicates the remote link director type. Values that may be shown and their meanings are:

◆ P

This field indicates the number of ports on the remote link director.

◆ CONN

This field indicates the port connection status (Y means that a link path is established; N means that no link path is established).

Note: Appendix C, “Director and Volume Status,” describes the CONN field.

MA Source remote link director

SL Target remote link director

RF Fibre remote link director

#SQ LINK 207

Command Reference

◆ STATUS

This field indicates the link status. Values that may appear are ONLINE or OFFLINE.

◆ MM:SS

This field indicates the short interval duration during which the average number of IOs across the link are calculated. This time duration varies between 00:01 and 09:59 (MM:SS). This time duration is calculated by Host Component as described in “Calculating SQ LINK I/O statistics” on page 201.

◆ I/O-RATE

This field shows the average I/Os per second over the short time interval.

◆ DDD:HH:MM:SS

This field shows the elapsed time since Host Component discovery of the Symmetrix or since the last utility reset command issued from the service processor.

◆ TOTAL_I/O

This field shows the total number of IOs across the link since Host Component discovery of the Symmetrix or since the most recent utility reset command issued from the service processor.


Command Reference

#SQ MIRRORThe #SQ MIRROR command displays the relationship of the logical devices to the physical devices, the invalid track count for each associated physical device, and the “NOT READY” and “WRITE DISABLED” status of each associated physical device.

Note: For RAID 10 devices, the Symmetrix devices that make up the logical volume are listed individually in the command response display.

Syntax

The #SQ MIRROR command syntax continues on the next page.

#SQ MIRROR

, state-filter

, cuu

,LCL(

cuu

, rdfgroup#)

,G(

groupname)

,SCFG(scfgroupname)

,RMT(

rdf

cuu

)

,RMT(

cuu,mhlist

)

1

,VOL(

volser

)

,SSID(

ssidnumber

)

3

,RMT(


, count

, count,startingdev#

, ALL,

startingdev#

1

3

2

, ALL

, state-filter

#SQ MIRROR 209

Command Reference

Parameters count|ALL|state-filter

Indicates the number of devices to display or include. count can be specified as an integer from 1 through the value specified in the MAX_QUERY initialization parameter.

ALL indicates that all devices are to be included up to the value of the MAX_QUERY initialization parameter.

Note: The maximum value for MAX_QUERY is 8192. If the Symmetrix being displayed has more than 8192 devices, use command syntax specifying the starting Symmetrix device number. For example:

#SQ MIRROR,cuu,count,startingdev#

Console buffering should be considered when setting MAX_QUERY.

state-filter indicates that only devices whose state matches the state-filter value you specify are to be included in the display.

The count and ALL options cannot be used with the SCFG(scfgroupname), G(groupname), or VOL(volser) parameters.

Note: Table 8 on page 287 describes valid state-filter values.


,CQNAME=cqname

3

,count

,count,startingdev#

,ALL,startingdev#

2 3

,ALL


Command Reference

cqname


cuu


G(groupname)


LCL


mhlist


queue-option


rdfgroup#


rdfcuu


RMT


SCFG(scfgroupname)


SSID(ssidnumber)


startingdev#

Specifies the Symmetrix device number at which to start the display. This parameter is optional.

• If the SC GLOBAL sort order is set to SORT_BY_VOLSER, this is a starting VOLSER.

• If the SC GLOBAL sort order is set to SORT_BY_MVSCUU, this is a starting MVSCUU.

VOL(volser)


#SQ MIRROR 211

Command Reference

Examples

Example 1 The following example shows the protection types for devices 431 and 432. Device 431 is locally protected with a RAID-6 (14+2) and RAID-5 (3+1) scheme. It is also protected remotely as a target in SRDF group 70. Device 432 is locally protected with a RAID-6 (6+2) and RAID-5 (7+1) scheme. It is also protected remotely as a target in SRDF group 70.

EMCMN00I SRDF-HC : (41) #SQ MIRROR,8200,2,431EMCQV15I SRDF-HC DISPLAY FOR (46) #SQ MIRROR,8200,2,431 ---MIRROR 1--- ---MIRROR 2--- ---MIRROR 3--- ---MIRROR 4---HOST SYMM| NW| NW| NW| NW CUU DEV|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD???? 0431 *RAID6 (14+2)* *RAID5 (3+1)* 0431 28-D04 . .. 38-C00 . .. *T70* 0 XX . .. 0431 38-C04 . .. 08-D00 . .. ...... . .. ...... . .. 0431 08-C03 . .. 18-C00 . .. ...... . .. ...... . .. 0431 18-D03 . .. 28-D00 . .. ...... . .. ...... . .. 0431 28-C03 . .. ...... . .. ...... . .. ...... . .. 0431 38-D03 . .. ...... . .. ...... . .. ...... . .. 0431 07-D03 . .. ...... . .. ...... . .. ...... . .. 0431 17-C03 . .. ...... . .. ...... . .. ...... . .. 0431 27-D03 . .. ...... . .. ...... . .. ...... . .. 0431 37-C03 . .. ...... . .. ...... . .. ...... . .. 0431 07-C04 . .. ...... . .. ...... . .. ...... . .. 0431 17-D04 . .. ...... . .. ...... . .. ...... . .. 0431 27-C04 . .. ...... . .. ...... . .. ...... . .. 0431 37-D04 . .. ...... . .. ...... . .. ...... . .. 0431 08-D04 . .. ...... . .. ...... . .. ...... . .. 0431 18-C04 . .. ...... . .. ...... . .. ...... . ..???? 0432 *RAID6 (6+2)* *RAID5 (7+1)* 0432 18-C02 . .. 27-C04 . .. *T70* 0 XX . .. 0432 28-D02 . .. 37-D04 . .. ...... . .. ...... . .. 0432 38-C02 . .. 08-D04 . .. ...... . .. ...... . .. 0432 07-C02 . .. 18-C04 . .. ...... . .. ...... . .. 0432 17-D02 . .. 28-D04 . .. ...... . .. ...... . .. 0432 27-C02 . .. 38-C04 . .. ...... . .. ...... . .. 0432 37-D02 . .. 07-C04 . .. ...... . .. ...... . .. 0432 08-D02 . .. 17-D04 . .. ...... . .. ...... . ..END OF DISPLAY

Note: Starting with Enginuity 5874, the RAID-1 and RAID-5 implementations now abstract each local RAID group to a single mirror position.


Command Reference

The fields in the previous example have the meanings indicated for each column header:

◆ Host CUU

Specifies the z/OS device number.

◆ Symm Dev

Specifies the Symmetrix device number.

◆ Mirror 1 - Mirror 4

Each of these columns describes a mirror. For SRDF Host Component V7.0 with Enginuity level 5874, the RAID types are displayed for the Symmetrix logical volumes as the first line in the mirror columns pertaining to the device. The types are:

• *RAID0*

• *RAID1*

• *RAID5 (3+1)*

• *RAID5 (7+1)*

• *RAID6 (6+2)*

• *RAID6 (14+2)*

Note: Host Component V7.0 checks all the mirror positions for a device to determine whether it gets included in the SQ MIRROR display. For example, if a device is multi-RAID and is RAID5 in mirror position 1 and RAID6 in another mirror position, the device would get included in an SQ MIRROR command display that used the RAID6 filter. The previous versions of SRDF Host Component only checked mirror position 1.

These columns are further subdivided as follows:

• DA-IF Identifies the physical address (disk adapter and SCSI interface). For SRDF devices, this field could display *Snn* or *Tnn* where nn is the RDF group number indicating that the mirror position represents the SRDF partner device on the remote Symmetrix system.

– *Snn* is displayed when the local device is a target (R2) and the remote partner is a source (R1) device.

– *Tnn* is displayed when the local device is a source (R1) and the remote partner is a target (R2) device.

– *Bsymdv#* is displayed for devices with attached BCVs, where symdv# is the Symmetrix device number.

#SQ MIRROR 213

Command Reference

If the device is a BCV source device, the mirror that is being used as a BCV contains Snnnn where nnnn is the Symmetrix device number of the STD device.

If the device is a standard device with an attached BCV, the mirror of the BCV is marked as Bnnnn where nnnn is the Symmetrix device number of the BCV.

• ITRKS

This field shows the invalid track count for the mirror. The numbers reported are displayed as K or M as appropriate, where 1K = 1024 and 1M = 1000*1024.

• NR

An X in this column indicates the mirror is not ready.

• WD

An X in this column indicates the mirror is read-only.


Command Reference

Example 2 Below is a display resulting from an #SQ MIRROR command specifying an FBA meta device. This query is specifically requesting information for six Symmetrix devices starting at device number 601.

EMCQV15I SRDF-HC DISPLAY FOR (21) @@SQ MIRROR,600,6,601 918 ---MIRROR 1--- ---MIRROR 2--- ---MIRROR 3--- ---MIRROR 4--- HOST SYMM| NW| NW| NW| NW CUU DEV|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD ???? 0601 21-C2 0 .. ..... . .. ..... . .. ..... . .. 0602 10-D2 . .. ..... . .. ..... . .. ..... . .. 0603 31-D2 . .. ..... . .. ..... . .. ..... . .. 0604 20-C2 . .. ..... . .. ..... . .. ..... . .. 0605 01-C2 . .. ..... . .. ..... . .. ..... . .. ???? 0606 30-D2 0 .. ..... . .. ..... . .. ..... . .. 0607 11-D2 . .. ..... . .. ..... . .. ..... . .. 0608 40-C2 . .. ..... . .. ..... . .. ..... . .. 0609 21-D3 . .. ..... . .. ..... . .. ..... . .. 060A 10-C3 . .. ..... . .. ..... . .. ..... . .. ???? 060B 21-C6 0 .. ..... . .. ..... . .. ..... . .. 060C 10-D6 . .. ..... . .. ..... . .. ..... . .. 060D 31-D6 . .. ..... . .. ..... . .. ..... . .. 060E 20-C6 . .. ..... . .. ..... . .. ..... . .. 060F 01-C6 . .. ..... . .. ..... . .. ..... . .. ???? 0610 30-D6 0 .. ..... . .. ..... . .. ..... . .. 0611 11-D6 . .. ..... . .. ..... . .. ..... . .. 0612 40-C6 . .. ..... . .. ..... . .. ..... . .. 0613 21-D7 . .. ..... . .. ..... . .. ..... . .. 0614 10-C7 . .. ..... . .. ..... . .. ..... . .. ???? 0615 21-C4 0 .. ..... . .. ..... . .. ..... . .. 0616 10-D4 . .. ..... . .. ..... . .. ..... . .. 0617 31-D4 . .. ..... . .. ..... . .. ..... . .. 0618 20-C4 . .. ..... . .. ..... . .. ..... . .. 0619 01-C4 . .. ..... . .. ..... . .. ..... . .. 061A 30-D4 . .. ..... . .. ..... . .. ..... . .. END OF DISPLAY

#SQ MIRROR 215

Command Reference

Example 3 The following is a display resulting from an #SQ MIRROR command specifying the RAID6 attribute.

EMCMN00I SRDF-HC : (247) &SQ MIRROR,C100,RAID6 EMCQV15I SRDF-HC DISPLAY FOR (247) &SQ MIRROR,C100,RAID6 374 ---MIRROR 1--- ---MIRROR 2--- ---MIRROR 3--- ---MIRROR 4--- HOST SYMM| NW| NW| NW| NW CUU DEV|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD C110 0272 01-C1C 0 .. *S60* 0 .. . .. . .. 02-C1B . .. ...... . .. ...... . .. ...... . .. 20-C1A . .. ...... . .. ...... . .. ...... . .. 1F-C1B . .. ...... . .. ...... . .. ...... . .. 10-D1C . .. ...... . .. ...... . .. ...... . .. 0F-D1B . .. ...... . .. ...... . .. ...... . .. 11-D1C . .. ...... . .. ...... . .. ...... . .. 12-D1B . .. ...... . .. ...... . .. ...... . .. C111 0273 10-C1B 0 .. *S07* 0 .. . .. . .. 0F-C1C . .. ...... . .. ...... . .. ...... . .. 11-C1B . .. ...... . .. ...... . .. ...... . .. 12-C1A . .. ...... . .. ...... . .. ...... . .. 01-D1B . .. ...... . .. ...... . .. ...... . .. 02-D1C . .. ...... . .. ...... . .. ...... . .. 20-D1B . .. ...... . .. ...... . .. ...... . .. 1F-D1C . .. ...... . .. ...... . .. ...... . .. C112 0274 01-C1E 0 .. *SE0* 0 .. . .. . .. 02-C1D . .. ...... . .. ...... . .. ...... . .. 20-C1C . .. ...... . .. ...... . .. ...... . .. 1F-C1D . .. ...... . .. ...... . .. ...... . .. 10-D1E . .. ...... . .. ...... . .. ...... . .. 0F-D1D . .. ...... . .. ...... . .. ...... . .. 11-D1E . .. ...... . .. ...... . .. ...... . .. 12-D1D . .. ...... . .. ...... . .. ...... . .. C113 0275 10-C1D 0 .. *SC0* 0 .. . .. . .. 0F-C1E . .. ...... . .. ...... . .. ...... . .. 11-C1D . .. ...... . .. ...... . .. ...... . .. 12-C1C . .. ...... . .. ...... . .. ...... . .. 01-D1D . .. ...... . .. ...... . .. ...... . .. 02-D1E . .. ...... . .. ...... . .. ...... . .. 20-D1D . .. ...... . .. ...... . .. ...... . .. 1F-D1E . .. ...... . .. ...... . .. ...... . ..


Command Reference

Example 4 The following is a display resulting from an #SQ MIRROR command specifying the MRG filter. This filter limits the output display to devices with least one RAID 5 or RAID 6 mirror and at least one other mirror position of RAID 0, RAID 1, RAID 5, or RAID 6 type.

EMCMN00I SRDF-HC : (12) #SQ MIRROR,8200,MRGEMCQV15I SRDF-HC DISPLAY FOR (12) #SQ MIRROR,8200,MRG ---MIRROR 1--- ---MIRROR 2--- ---MIRROR 3--- ---MIRROR 4---HOST SYMM| NW| NW| NW| NW CUU DEV|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD|DA-IF ITRKS RD???? 042A *RAID6 (6+2)* *RAID5 (3+1)* 042A 27-D03 . .. 38-C04 . .. *T70* 0 XX . .. 042A 37-C03 . .. 08-D04 . .. ...... . .. ...... . .. 042A 08-C03 . .. 18-C04 . .. ...... . .. ...... . .. 042A 18-D03 . .. 28-D04 . .. ...... . .. ...... . .. 042A 28-C03 . .. ...... . .. ...... . .. ...... . .. 042A 38-D03 . .. ...... . .. ...... . .. ...... . .. 042A 07-D03 . .. ...... . .. ...... . .. ...... . .. 042A 17-C03 . .. ...... . .. ...... . .. ...... . ..???? 042B *RAID6 (6+2)* *RAID5 (3+1)* 042B 28-D04 . .. 37-D04 . .. *T70* 0 XX . .. 042B 38-C04 . .. 07-C04 . .. ...... . .. ...... . .. 042B 07-C04 . .. 17-D04 . .. ...... . .. ...... . .. 042B 17-D04 . .. 27-C04 . .. ...... . .. ...... . .. 042B 27-C04 . .. ...... . .. ...... . .. ...... . .. 042B 37-D04 . .. ...... . .. ...... . .. ...... . .. 042B 08-D04 . .. ...... . .. ...... . .. ...... . .. 042B 18-C04 . .. ...... . .. ...... . .. ...... . .. ???? 042C *RAID6 (6+2)* *RAID5 (3+1)* 042C 17-C01 . .. 38-D03 . .. *T70* 0 XX . .. 042C 27-D01 . .. 08-C03 . .. ...... . .. ...... . .. 042C 37-C01 . .. 18-D03 . .. ...... . .. ...... . .. 042C 08-C01 . .. 28-C03 . .. ...... . .. ...... . .. 042C 18-D01 . .. ...... . .. ...... . .. ...... . .. 042C 28-C01 . .. ...... . .. ...... . .. ...... . .. 042C 38-D01 . .. ...... . .. ...... . .. ...... . .. 042C 07-D01 . .. ...... . .. ...... . .. ...... . ..

#SQ MSG 217

Command Reference

#SQ MSGThe #SQ MSG command displays any SRDF error or informational messages presented to the host console if the message processing startup option was selected. These messages can be generated by any Symmetrix system in the SRDF configuration.

Syntax

Parameters count

Specifies the number of messages to display. You can set this value from 1 to the size of the message log (as specified in the MESSAGE_PROCESSING initialization parameter), or ALL (which specifies all the messages). If you do not specify this parameter, count defaults to 1. The maximum count value is 512.

cqname


queue-option


Comments This command, when issued with the ALL parameter, displays all messages currently held in the message log. The newest messages appear at the top of the display and the oldest messages at the bottom of the display.

SIM (Service Information Messages) are produced by Symmetrix systems to report events. The SIM notification is sent in response to the first I/O following the occurrence of the event. The device to which this I/O is issued is recorded as the REPORTING device. When z/OS receives a SIM notification, an IEA480E message is generated.

#SQ MSG

,count ,CQNAME=cqname

,CQNAME=(cqname,queue-option),ALL


Command Reference

The SIM contains a description of the abnormal condition in the REFCODE. This is a hex code identifying the event and the device(s) with which the event was associated. SRDF Host Component detects the event and issues an EMC9998W message in an attempt to more clearly interpret the SIM notification.

The format for SIM IEA480E is as follows:

IEA480E rptdv#,SCU,SERVICE ALERT,MT=ctltype,SER=ctlser,REFCODE=xxxx-yyyy-zzzz

Where:

Note: The MVS/ESA system messages manual for your release of z/OS provides further details about the IEA480E message.

The format of the EMC9998W message varies slightly depending on the exception code. The EMC Consolidated Mainframe Software Suite Message and Code Guide contains details about the EMC9998W message.

Depending on the MESSAGE_PROCESSING initialization parameter, the SIM message may be saved by SRDF Host Component for later display using the #SQ MSG command.

Example The following example displays the output from an #SQ MSG, ALL command:

rptdv# Specifies the reporting device number

ctltype Specifies the controller type (for example, 3990-3)

ctlser Specifies the controller serial number

xxxx Specifies the exception code

yyyy Specifies additional information about the event

zzzz Specifies additional information about the event

EMCQM81I SRDF-HC DISPLAY FOR (7) #SQ MSG,ALL___DATE___ __TIME__ CUU_ DV_ CT_ SSID __________MESSAGE______ NNNN RCUU11/02/2001 13:28:28 N/A 00 N/A 3402 RDF ADAPTER LNK PROBLEM 0006 B85F11/02/2001 13:28:28 N/A 00 N/A 3402 RDF ADAPTER LNK PROBLEM 0005 B85F11/02/2001 13:28:21 N/A 00 N/A 3001 RDF ADAPTER LNK PROBLEM 0004 316B11/02/2001 13:28:15 N/A 00 N/A 3000 RDF ADAPTER LNK PROBLEM 0003 300411/02/2001 13:28:15 N/A 00 N/A 3000 RDF ADAPTER LNK PROBLEM 0002 300411/02/2001 13:28:14 N/A 00 N/A 3001 RDF ADAPTER LNK PROBLEM 0001 316BEND OF DISPLAY

#SQ MSG 219

Command Reference

The fields in this example have meanings corresponding to the column headers as follows:

◆ DATE

Date of event.

◆ TIME

Time of event.

◆ CUU

z/OS device number.

◆ DV

Symmetrix device number or remote link director number.

◆ CT

The number of devices affected by the event with which the message is associated (in decimal).

◆ SSID

Subsystem ID of the reporting device.

◆ MESSAGE

Symmetrix message. The following messages may appear in this column:• DYNAMIC SPARING INVOKED• TARG VOLUME RESYNC W/SOURCE• SOURCE VOLUME RESYNC W/TARGET• R1 CONGROUP TASK INACT• R1/M1/ML VOL NOT READY STATE• R1 VOL SRDF WRITE-DISABLED• R2 VOLUME IN NOT RDY STATE• RDF ADAPTER LINK PROBLEM• RESYNC PROCESS HAS BEGUN• RDF ADAPTER LINK OPERATIONAL

◆ nnnn

A number associated with an event, allowing different messages that may result from a single event to be tied to that event. Some IDs of messages that may be linked to an event in this way are EMCQM81I, EMCQM82I in HCLOG, and EMC9998W.

◆ RCUU

Reporting device address.


Command Reference

#SQ RAIDThe #SQ RAID command displays the Symmetrix RAID-S configuration. The z/OS device number is displayed as well as the Symmetrix device number and the physical device numbers. The parity device also appears.

Syntax

Parameters ALL

Specifies that all eligible devices or all eligible devices starting from startingdev# are to be displayed.

count

Specifies the number of eligible devices to be displayed (starting from startingdev# or from the beginning of the configuration).

#SQ RAID

, cuu

,RMT(

rdf

cuu

)

,RMT(

cuu,mhlist

)

1

,LCL(

cuu,rdfgroup#)

,RMT(


, count


, ALL,

startingdev#

1

2


,CQNAME=

cqname

2

,ALL,

#SQ RAID 221

Command Reference

cqname


cuu


LCL


mhlist


queue-option


rdfgroup#


rdfcuu


RMT


startingdev#

Identifies the device at which to start the display. This parameter is optional. If the SC GLOBAL sort order is set to (or allowed to default to) SORT_BY_SYMDEV, the value specified is treated as a Symmetrix device number.

• If the SC GLOBAL sort order is set to SORT_BY_VOLSER, the value specified is treated as a starting volume serial.

• If the SC GLOBAL sort order is set to SORT_BY_MVSCUU, the value specified is treated as a starting MVS device address.


Command Reference

Example The following is an example of the #SQ RAID command output:

EMCMN00I SRDF-HC : (47) #SQ RAID,2800,2 EMCQV17I SRDF-HC DISPLAY FOR (47) #SQ RAID,2800,2 RAID PTY GROUP| CUU_ DEV_ DA-IF | CUU_ DEV_ DA-IF | CUU_ DEV_ DA-IF | DA-IF8004 ???? 0309 21-C04 ???? 030B 31-D04 ???? 030D 30-D04 01-C4 ???? 030F 20-C04 ???? 0311 11-D04 ???? 0313 10-D04 ???? 0315 40-C04 8005 ???? 030A 20-D05 ???? 030C 01-D05 ???? 030E 10-C05 30-C5 ???? 0310 31-C05 ???? 0312 40-D05 ???? 0314 21-D05 ???? 0316 11-C05 END OF DISPLAY

The fields in this example have the meanings corresponding to the column headers as follows:

◆ RAID GROUP

RAID group number.

◆ CUU

z/OS device number.

Note: This field displays “????” for devices specified in the SCF exclude list.

◆ DEV

Symmetrix device number.

◆ DA-IF

Identifies the physical address (disk adapter and SCSI interface).

◆ PTY DA-IF

Identifies the physical address (disk adapter and SCSI interface) of the RAID parity device.

#SQ RAID5 223

Command Reference

#SQ RAID5The #SQ RAID5 command displays the Symmetrix RAID 5 configuration. The z/OS device number is displayed as well as the Symmetrix device number and the physical device numbers. The parity device also appears.

Syntax

Parameters ALL


count


#SQ RAID5 , cuu

,RMT( rdf cuu )

,RMT( cuu,mhlist )

1



, count


, ALL, startingdev#

1 2

, ALL


,CQNAME=

cqname

2


Command Reference

cqname


cuu


LCL


mhlist


queue-option


rdfcuu


rdfgroup#


RMT


startingdev#




Example The following example shows information about spares that have been invoked for a member. In the example, a hot spare has been invoked for member 4. The physical address of the spare is displayed.

One member is reported per line. All not-rdy and write-disabled information is displayed for both the member and for any spare that may be invoked for that member. Note that the '>' on the line for member # 4 indicates the copy direction for the spare. In this case, data is being copied from the member to the spare.

#SQ RAID5 225

Command Reference

EMCQV19I SRDF-HC DISPLAY FOR (10) //SQ RAID5,6F60 |DEV| | |MEMBER|SPARE | STRIPE|N W| SPARE |MBR| | N W | N W |CUU_|DEV_|WIDTH |R D|MEM|DA-IF| # |DA-IF | R D | R D |6F60 0060 0004 . . 4 3A-C0 1 01-C0 . . X X 2 04-D8 . . X X 3 1A-C2 . . X X 4 20-C0 . X > . . 5 22-C0 . . X X 6 28-C0 . . X X 7 30-C2 . . X X 8 31-C0 . . X X


◆ CUU

z/OS device number.

◆ DEV


◆ STRIPE WIDTH

The number of tracks in a single stripe.

◆ DEV

• NR An X appears in this column if the device is not ready.

• WD An X appears in this column if the device is write disabled (read only).

◆ SPARE MEM

Identifies which member the spare is invoked for.

◆ SPARE DA-IF

Identifies the physical address (disk adapter and SCSI interface) for the spare device.


Command Reference

◆ MBR #

Indicates the member number described by the DA-IF field to the right. Note that this number can be used to tie back to the SPARE MEM column if a spare is invoked for that member. The number of members displayed will be either 4 (for RAID5 3+1) or 8 (for RAID5 7+1).

◆ DA-IF

Identifies the physical address (disk adapter and SCSI interface) for the member device.

◆ MEMBER

• NR

An X appears in this column if the member device is not ready.

• WD

An X appears in this column if the spare device is write-disabled (read only).

◆ < or >

A < or > indicates the direction of data flow (to or from the spare). In the example, a spare has been invoked for member 4 and the data is flowing from the member to the spare.

◆ SPARE

• NR

An X appears in this column if the spare device is not ready.

• WD

An X appears in this column if the spare device is write-disabled (read only).

#SQ RAID6 227

Command Reference

#SQ RAID6The #SQ RAID6 command displays the Symmetrix RAID 6 configuration. The z/OS device number is displayed as well as the Symmetrix device number and the physical device numbers. The parity device also appears.

Syntax

Parameters ALL


count


#SQ RAID6 , cuu

,RMT( rdf cuu )

,RMT( cuu,mhlist )

1

, count


, ALL, startingdev#

1 2

, ALL

,CQNAME=( cqname,queue-option)

,CQNAME=

cqname

2


,RMT( ) cuu,mhlist,rdfgroup#


Command Reference

cqname


cuu


LCL


mhlist


queue-option


rdfgroup#


rdfcuu


RMT


startingdev#




#SQ RAID6 229

Command Reference

Example The following example displays the output from an #SQ RAID6 command:

EMCMN00I SRDF-HC : (13) @@SQ RAID6,C100 EMCQV20I SRDF-HC DISPLAY FOR (13) @@SQ RAID6,C100,10 624 | DEV | |MEMBER| STRIPE| N W | MBR| | N W | CUU_|DEV_|WIDTH | R D | # |DA-IF | R D | C110 0272 0004 . . 1 01-C1C . . 2 02-C1B . . 3 20-C1A . . 4 1F-C1B . . 5 10-D1C . . 6 0F-D1B . . 7 11-D1C . . 8 12-D1B . . END OF DISPLAY


◆ CUU

z/OS device number.

◆ DEV


◆ STRIPE WIDTH

The number of tracks in a single stripe.

◆ DEV

• NR

An X appears in this column if the device is not ready.

• WD

An X appears in this column if the device is write disabled (read only).

◆ MBR #

Indicates the member number described by the DA-IF field to the right. The number of members displayed will be either 8 or 16.

◆ DA-IF

Identifies the physical address (disk adapter and SCSI interface).


Command Reference

◆ MEMBER

• NR

An X appears in this column if the ? is not ready.

• WD

An X appears in this column if the device is write disabled (read only).

#SQ RAID10 231

Command Reference

#SQ RAID10The #SQ RAID10 command displays the Symmetrix devices making up a RAID 10 logical volume. The z/OS device number is displayed as well as the Symmetrix device numbers.

Syntax

Parameters ALL


count


#SQ RAID10

, cuu

,RMT(

rdf

cuu

)

,RMT(

cuu,mhlist

)

1

)

,RMT(


, count


, ALL,

startingdev#

1

2

, ALL

,CQNAME=(

cqname

,queue-option)

,CQNAME=

cqname

2

,LCL(

cuu,rdfgroup#


Command Reference

cqname


cuu


LCL


mhlist


queue-option


rdfgroup#


rdfcuu


RMT


startingdev#




#SQ RAID10 233

Command Reference

Example The following example displays the output from an #SQ RAID10 command:


◆ CUU

z/OS device number.

◆ DEV


EMCMN00I SRDF-HC : (96) #SQ RAID10,9820,4EMCQV18I SRDF-HC DISPLAY FOR (96) #SQ RAID10,9820,4CUU_ | DEV_ DEV_ DEV_ DEV_9820 0020 0040 0060 00809821 0021 0041 0061 00819822 0022 0042 0062 00829823 0023 0043 0063 0083END OF DISPLAY


Command Reference

#SQ RDFGRPThe #SQ RDFGRP command displays the Symmetrix RDF group configuration.

Syntax

Parameters ALL

Specifies that complete details for every RDF group in the Symmetrix system are to be displayed.

cqname


cuu


G(groupname)


,CQNAME= cqname


,RA(rdfgroup#)

,ALL

#SQ RDFGRP , cuu


,G( groupname)

,SCFG(scfgroupname)

,RMT( rdf cuu )

,RMT( cuu,mhlist )

1


1

#SQ RDFGRP 235

Command Reference

LCL


mhlist


queue-option


rdfgroup#


RA(rdfgroup#)

Specifies the RDF group for which you want to display complete details.

rdfcuu


RMT


SCFG(scfgroupname)


Comments The #SQ RDFGRP command supports Symmetrix systems running Enginuity levels lower than 5x67. However, the parameters ALL and RA(rdfgroup#) are ignored on the lower Enginuity levels.

If no remote commands have been issued, the output appears similar to the following:

EMCQR00I RDF-HC DISPLAY FOR (3) #SQ RDFGRP,2804 MY SERIAL # MY MICROCODE ------------ ------------ 000000003273 5266-41 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR------ --- -- ------ ------------ ------------ -------- 00 . . 00 000000003274 UNKNOWN G(NONE) 01 . . 01 000000003274 UNKNOWN G(NONE) 02 . . 02 000000003274 UNKNOWN G(NONE) 03 . . 03 000000003274 UNKNOWN G(NONE) 04 . . 04 000000003274 UNKNOWN G(NONE) 05 . . 05 000000003274 UNKNOWN G(NONE) 06 . . 06 000000003274 UNKNOWN G(NONE) 07 . . 07 000000003274 UNKNOWN G(NONE)


Command Reference

However, once a command has been issued to a remote Symmetrix system, the output looks similar to the following:

EMCQR00I RDF-HC DISPLAY FOR (8) ¢¢SQ RDFGRP,2804 MY SERIAL # MY MICROCODE ------------ ------------ 000000003273 5266-41 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR ------ --- -- ------ ------------ ------------ -------- 00 . . 00 000000003274 5266-41 G(NONE) 01 . . 01 000000003274 5266-41 G(NONE) 02 . . 02 000000003274 5266-41 G(NONE) 03 . . 03 000000003274 5266-41 G(NONE) 04 . . 04 000000003274 5266-41 G(NONE) 05 . . 05 000000003274 5266-41 G(NONE) 06 . . 06 000000003274 5266-41 G(NONE) 07 . . 07 000000003274 5266-41 G(NONE)

Note: ONL and PC are not filled in on these Symmetrix systems. The RDF group cannot be taken online/offline, and the protocol is not at the RDF group level but at the director level.

Examples The following examples show the output from various #SQ RDFGRP commands:

Example 1 The command #SQ RDFGRP,6E4C generates the following output:

EMCQR00I SRDF-HC DISPLAY FOR (5) ¢¢SQ RDFGRP,6E4C 750 MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-11 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- 01 Y F 32 000187990132 5671-12 G(R1>R2) SRDFA ACTIVE RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 06 Y F 16 000187990132 5671-12 G(R1>R2) LRGROUPB DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 07 Y F 07 000187990175 5670-77 G(R1>R2) LRGROUPC DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 08 Y F 18 000187990171 5671-11 G(R1>R2) STAR LRGROUP5 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO (LRSTAR ) 0D Y F 00 000184600309 5568-65 G(R1>R2) UWE2U6A STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 0E Y F 06 000184500309 5568-65 G(R1>R2) UWF2U6A STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 10 Y F 05 000187990132 5671-12 G(R1>R2)

#SQ RDFGRP 237

Command Reference

RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 11 Y F 14 000187990171 5671-11 G(R1>R2) LRGROUP6 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 13 Y F 33 000000006205 5670-79 G(R1>R2) LRGROUP7 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 15 Y F 25 000187900699 5670-71 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 17 Y F 27 000187990171 5671-11 G(R1>R2) WJGRP1 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 18 Y F 28 000187990132 5671-12 G(R1>R2) WJGRP2 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 24 Y F 27 000187990132 5671-12 G(R1>R2) MSF01 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 25 Y F 15 000187790072 5670-77 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 27 Y F 24 000187990171 5671-11 G(R1>R2) MAKOTO DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 2A Y F 2A 000187990132 5671-12 G(R1>R2) AMRAG1 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 2B Y F 2B 000187990171 5671-11 G(R1>R2) AMRAG2 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 2C Y F 2C 000187990132 5671-12 G(R1>R2) AMRAG3 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 2D Y F 2D 000187990171 5671-11 G(R1>R2) AMRAG4 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 3D Y F 3B 000187990132 5671-12 G(R1>R2) SRDFA ACTIVE BRUCE DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 3E Y F 3F 000187990132 5671-12 G(R1>R2) SRDFA ACTIVE LRGROUP4 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 3F Y F 3E 000187990132 5671-12 G(R1>R2) STAR LRGROUP3 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO (LRSTAR )END OF DISPLAY


Command Reference

Example 2 The command #SQ RDFGRP,6E4C,RA(25) generates the following output:

EMCQR00I SRDF-HC DISPLAY FOR (165) ¢¢SQ RDFGRP,6E4C,RA(25) 986 MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-08 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 25 Y F 15 000187990132 5671-08 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ---------------- 33 17 02 5006048800060A52 00000000043D23F8 00000000005B4118 36 02 00000000043DE608 00000000005D7450 00000000087B0A00 0000000000B8B568 3E 17 02 5006048800060A5D 0000000004474650 0000000000641C40 36 02 000000000426FAC0 0000000000627418 00000000086E4110 0000000000C69058 END OF DISPLAY

Example 3 The command #SQ RDFGRP,6F60,RA(15) displays the labels associated with RDF groups as follows:

EMCQR00I SRDF-HC DISPLAY FOR (2) #SQ RDFGRP,6F60,RA(15) MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5670-05 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ 15 Y F 10 000000006205 5670-05 G(R1>R2) SRDFA ACTIVE GROUP LABEL: rdfgroup2 STATIC MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ---------------- 13 22 02 5006048000060A52 0000000073247748 00000004B1B018C0 0000000073247748 00000004B1B018C0

The fields in the previous examples have the meanings associated with the headers as indicated below:

◆ MY SERIAL #

The complete 12-digit serial number of the Symmetrix system to which the command was issued.

◆ MY MICROCODE

The major-minor Enginuity level of the Symmetrix system to which the command was issued.

#SQ RDFGRP 239

Command Reference

◆ MY GRP

The RDF group in the Symmetrix system to which the command was issued.

◆ ONL

Y indicates that the RDF group is online. N indicates that the RDF group is offline.

◆ PC

The protocol of the RDF group. The values ESCON, Fibre, IP, and U may appear. If a U appears, the protocol is unknown and the group is likely offline.

◆ OS GRP

The number of the associated RDF group on the remote Symmetrix system.

◆ OS SERIAL

The complete 12-digit serial number of the remote Symmetrix system.

◆ OS MICROCODE

The major-minor Enginuity level of the remote Symmetrix system.

◆ SYNCHDIR

The current synchronization direction. G indicates the setting is at the global level, C for the control unit, and R for the RDF group.

◆ FEATURE

Indicates which feature(s) are currently enabled:

(Blank) Not SRDF/A at this time.

SRDFA ACTIVE SRDF/A is active on the RDF group at this time.

SRDFA INACT SRDF/A is in a transitional state. Once cleanup is done, it will no longer be SRDF/A active.

SRDFA A MSC An active SRDF/A RDF group is running in MSC.

SRDFA I MSC An inactive SRDF/A RDF group was running in MSC.

SRDFA T MSC An active SRDF/A RDF group is running in MSC mode in Transmit Idle

SRDFA A STAR An active SRDF/A RDF group is running in both MSC and SRDF/Star.


Command Reference

◆ LABEL

An alphanumeric group label (up to 10 characters).

◆ TYPE

The group type, STATIC or DYNAMIC.

◆ AUTO-LINKS-RECOVERY

AUTO-LINKS-RECOVERY indicates the mode is in effect (all devices will become ready on the link when it is recovered). NO-AUTO-LINKS-RECOVERY indicates the mode is not in effect (which will leave the devices TNR when the link is restored).

◆ LINKS_DOMINO

LINKS-DOMINO:YES indicates the mode is in effect, LINKS-DOMINO:NO indicates the mode is not in effect, and LINKS-DOMINO:RDFGRP indicates the feature is in effect by RDF group. LINKS-DOMINO mode is a mode of operation in which all R1 devices go RDF-NOT READY if all links are dropped.

◆ MSC_GROUP

If an RDF group is running MSC or SRDF/Star, then this field will display the first eight bytes of the MSC group that was specified on the MSC_GROUP_NAME initialization statement that defined the MSC group.

◆ MY DIR#

The RA director that supports the RDF group in the Symmetrix system to which the command was issued.

◆ OS RA#

The RA director on the remote Symmetrix system supporting the RDF group.

◆ ST

The state of the port on the remote Symmetrix system supporting the RDF group. A value of 02 indicates that the physical link on the remote system has been brought up. A value of 01 indicates that the remote system is in IML (initial microcode load).

SRDFA I STAR An inactive SRDF/A RDF group was running in MSC and SRDF/Star.

STAR An RDF group defined to an SRDF/Star definition that is not running SRDF/A.

#SQ RDFGRP 241

Command Reference

◆ -----MY WWN-----

The World Wide Name (WWN) of the RA in the Symmetrix system to which the command was issued.

◆ ----IN COUNT----

The number of I/O on the logical link coming from the remote Symmetrix system.

◆ ---OUT COUNT----

The number of I/O on the logical link coming from the Symmetrix system to which the command was issued.


Command Reference

#SQ SRDFAThe #SQ SRDFA command displays information about the SRDF/A RDF groups in the Symmetrix system.

Note: After an SRDF/A RDF group status is changed, the volume status may take a few seconds to refresh. Devices may not report the new device status for a few seconds.

Note that the device used in the command does not have to be an SRDF/A device. The device is used as a gatekeeper and identifies the Symmetrix system on which the RDF group (or multiple RDF groups when running Enginuity level 5x71) with SRDF/A in the box may be found.

The #SQ SRDFA,cuu command format displays data about the entire SRDF/A configuration in the Symmetrix (that is, the display will be for all RDF groups found with SRDF/A). Use the command format #SQ SRDFA,LCL or #SQ SRDFA,RMT to display data about a single RDF group.

#SQ SRDFA 243

Command Reference

Syntax

Parameters cqname


cuu


CYCLETOD

Provides an approximation of the time of day (TOD) that the data on the SRDF/A R2 represents.This parameter is used only for an SRDF/A query for all groups. It is ignored for an SRDF/A query for a specific group.

G(groupname)


#SQ SRDFA ,cuu

,LCL(cuu,rdfgroup#)

,RMT(cuu,mhlist,*)

,G(groupname)

,RMT(rdfcuu)

,RMT(cuu,mhlist)

1

,RMT(cuu,mhlist,rdfgroup#)

1

,CQNAME= cqname


,SCFG(scfgroupname)

,CYCLETOD


Command Reference

LCL


mhlist


queue-option


rdfgroup#


RMT


SCFG(scfgroupname)


#SQ SRDFA 245

Command Reference

Examples

Example 1 The following example shows output generated by an #SQ SRDFA command issued to the primary side:

Figure 17 #SQ SRDFA command issued to the primary side

The fields that can appear in the #SQ SRDFA primary side display have the following meanings:

◆ MY SERIAL #


◆ MY MICROCODE


◆ MY GRP

The SRDF/A group number. If this is part of a Cascaded SRDF/A configuration, the group number will have a -C suffix.

EMCMN00I SRDF-HC : (53) &SQ SRDFA,LCL(8600,28) EMCQR00I SRDF-HC DISPLAY FOR (53) &SQ SRDFA,LCL(8600,28) 053 MY SERIAL # MY MICROCODE ------------ ------------000192600304 5874-57

MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------

LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ----------

28 Y F 28 000192600312 5874-57 G(R1>R2) SRDFA ACTIVEGROUP28 STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO

----------------------------------------------------------------------PRIMARY SIDE: CYCLE NUMBER 171 MIN CYCLE TIME 30 SECONDARY CONSISTENT ( Y ) TOLERANCE ( Y )CAPTURE CYCLE SIZE 142 TRANSMIT CYCLE SIZE 22,832 AVERAGE CYCLE TIME 30 AVERAGE CYCLE SIZE 3,010 TIME SINCE LAST CYCLE SWITCH 2 DURATION OF LAST CYCLE 30 MAX THROTTLE TIME 0 MAX CACHE PERCENTAGE 94 HA WRITES 1,820 RPTD HA WRITES 18 HA DUP. SLOTS 0 SECONDARY DELAY 32 LAST CYCLE SIZE 30,000 DROP PRIORITY 33 CLEANUP RUNNING ( N ) MSC WINDOW IS OPEN ( N ) SRDF/A TRANSMIT IDLE ( Y ) SRDF/A DSE ACTIVE ( N ) MSC ACTIVE ( N ) CEXMPT COUNT 3----------------------------------------------------------------------END OF DISPLAY


Command Reference

◆ ONL


◆ PC

The protocol of the RDF group. The values E (ESCON), F (Fibre), IP, and U may appear. If a U appears, the protocol is unknown and the group is likely offline.

◆ OS GRP


◆ OS SERIAL


◆ OS MICROCODE


◆ SYNCHDIR


◆ FEATURE











#SQ SRDFA 247

Command Reference

◆ LABEL


◆ TYPE




◆ LINKS_DOMINO


◆ MSC_GROUP


◆ PRIMARY SIDE

Primary Side indicates that the query was done on the primary side of the RDF configuration.

◆ CYCLE NUMBER

Cycle Number is a number representing the current SRDF/A.

◆ MIN CYCLE TIME

Min Cycle Time is the interval time that SRDF/A is targeting for cycle switches. When running without MSC, this is the time the Symmetrix will try to cycle switch. When running with MSC active, this time is not used.


Command Reference

◆ SECONDARY CONSISTENT

Secondary Consistent indicates whether the secondary side is consistent:

◆ TOLERANCE

When Tolerance mode is on, SRDF/A can be active and the following events do not cause it to drop: R2 made R/W and R1 made TNR.

The Tolerance option indicates if Tolerance mode is on or off:

◆ CAPTURE CYCLE SIZE

Capture Cycle Size is the number of cache slots currently in the active cycle.

◆ TIME SINCE LAST CYCLE SWITCH

Time Since Last Cycle Switch is the number of seconds since the last time SRDF/A has cycle switched.

◆ DURATION OF LAST CYCLE

Duration of Last Cycle is the number of seconds the last cycle lasted.

◆ TRANSMIT CYCLE SIZE

Transmit Cycle Size is the number of slots left in the cycle being sent to the secondary side.

◆ AVERAGE CYCLE TIME

Average Cycle Time is the average time each cycle is taking over the past sixteen cycles.

◆ AVERAGE CYCLE SIZE

Average Cycle Size is the average number of slots in the past sixteen cycles.

Y SRDF/A is consistent

N SRDF/A is not consistent

? SRDF/A is not active, and the data on the secondary side may or may not be consistent. Since SRDF/A is not active the consistency cannot be determined by SRDFA.

Y Tolerance mode is on for the SRDF/A sessions

N Tolerance mode is not on for the SRDF/A sessions

#SQ SRDFA 249

Command Reference

◆ MAX THROTTLE TIME

Maximum Throttle Time indicates how long SRDF/A will slow the host adapters once cache limits are reached.

• If the value is 0, then once cache limits are reached, SRDF/A is dropped.

• If the value is 65535, then the host adapters will work at write pending limits indefinitely.

• Any other value represents the number of seconds the host adapters will work at write pending limits before SRDF/A will be dropped.

◆ MAX CACHE PERCENTAGE

Maximum Cache Percentage is the percentage of cache that SRDF/A will be allowed to use. When SRDF/A processing would cause more than this percentage of cache to be used, SRDF/A is dropped for RDF groups in accordance with their Drop Priority settings.

Note: In the initial release of SRDF/A, the Maximum Cache Percentage is 100 percent.

◆ HA WRITES

Host Adapter Writes is the number of tracks written by the host adapters.

◆ RPTD HA WRITES

Repeated Host Adapter Writes is the total number of tracks written multiple times in a cycle by the host adapters.

◆ HA DUP SLOTS

Host Adapter Duplicated Slots is the number of times a slot had to be duplicated because it was written to in multiple cycles.

◆ SECONDARY DELAY

Secondary Delay is the approximate time that the SRDF/A-managed data on the secondary side is behind that on the primary side.

◆ LAST CYCLE SIZE

The Last Cycle Size is the size of the complete previous cycle.


Command Reference

◆ DROP PRIORITY

Drop Priority displays the relative priority of this SRDF/A session. If the percent of cache SRDF/A can use is exceeded, the Drop Priority determines the order, high to low priority, in which SRDF/A sessions are dropped in this Symmetrix to relieve the condition. The highest priority is 1; the lowest is 64.

Note: The Drop Priority set in the remote side RDF group has no effect on the Drop Priority in this RDF group.

◆ CLEANUP RUNNING

Cleanup Running indicates the cleanup status as follows:

◆ MSC WINDOW IS OPEN

The SRDF/A Multi-Session Consistency window is a small time frame that the cycle switch must be run in when running in MSC. When the MSC window is open, all write I/Os to SRDF/A primary devices are disconnected. Read I/Os continue to run.

◆ SRDFA TRANSMIT IDLE

This option indicates the Transmit Idle state:

In addition, a “T” in the FEATURE field of the command display indicates that an SRDF/A group is currently in the Transmit Idle state. “FEATURE” on page 246 lists the possible values for this field.

MSC will not initialize or refresh if the Transmit Idle state exists for one or more SRDF groups in the MSC group. If the Transmit Idle state exists when initializing MSC, message SCF1587R is issued to provide retry or cancel options:

08.31.07 S0041602 *nn SCF1587R MSC - GROUP=AGROUP WAIT FOR SRDFA TRANSMIT IDLE - RETRY OR CANCEL

Y The secondary side will reject non-SRDF/A for a small window of time (approximately 30 seconds) Cleanup only runs immediately after SRDF/A goes from the Active to the Inactive state. Cleanup prevents RDF_RSUM, REFRESH RFR-RSUM, RNG_REFRESH, RNG_RSUM, or VALIDATE/INVALIDATE from being run on the SRDF/A devices. After the cleanup is finished, these commands may be run.

N Cleanup is not running.

Y Transmit Idle is enabled for the RDF group.

N Transmit Idle is not enabled for the RDF group.

#SQ SRDFA 251

Command Reference

If the Transmit Idle state occurs while MSC is active and cycle switching, the following messages are generated.

08.23.17 S0041602 SCF1586I MSC - GROUP=AGROUP (07FB,16) SER= 000000006134 IN SRDFA TRANSMIT IDLE 08.23.17 S0041602 SCF1562I MSC - GROUP=AGROUP (07FB,16) SER= 000000006134 CYCLE SWITCH DELAY - TRANSMIT08.23.17 S0041602 SCF1563I MSC - GROUP=AGROUP (07FB,16) SER= 000000006143 CYCLE SWITCH DELAY - RESTORE

The following message is issued when the Transmit Idle state no longer exists:

08.24.44 S0041602 SCF1588I MSC - GROUP=AGROUP (07FB,16) SER= 000000006134 NO LONGER IN SRDFA TRANSMIT IDLE 08.24.45 S0041602 SCF1343I MSC - GROUP=AGROUP PROCESS_FC04-TIME FOR SWITCH

◆ SRDFA DSE ACTIVE

SRDFA DSE Active indicates whether Delta Set Extension (DSE) mode is active:

◆ MSC ACTIVE

MSC Active indicates whether the SRDF/A RDF group is part of an MSC group:

◆ ACTIVE SINCE

Active Since is the date and time that the SRDF/A session joined MSC.

◆ CAPTURE TAG

Capture Tag is the tag for the data in the capture cycle. The Capture Tag verifies the multiple SRDF/A RDF groups in the MSC group are coordinated. When MSC is active, the Capture Tag functions like the cycle number when SRDF/A is active and MSC is not active.

Y The SRDF/A RDF group is running in DSE mode.

N SRDF/A is not running in DSE mode.

Y The SRDF/A RDF group is part of an MSC group. The MSC group is one of a set of SRDF/A RDF groups whose cycle switching is controlled by the host and not the Symmetrix. When SRDF/A is not active and MSC Active = “Y”, it indicates that SRDF/A was deactivated or dropped while MSC was active.

N SRDF/A is not part of an MSC group.


Command Reference

◆ TRANSMIT TAG

Transmit Tag is the tag for the data in the transmit cycle. Transmit Tag verifies that the multiple SRDF/A RDF groups in the MSC group are coordinated. When MSC is active, the Transmit Tag functions like the cycle number when SRDF/A is active and MSC is not active.

◆ GLOBAL CONSISTENCY

Global Consistency indicates the status of dependent write consistency as follows:

◆ STAR RECOVERY AVAILABLE

Star Recovery Available indicates the status of MSC and SRDF/Star mode as follows:

◆ CEXMPT COUNT

This field indicates the number of consistency exempt devices in the RDF group. Consistency exempt is activated on a group basis.

Y Dependent write consistency has been achieved at the remote site across all RDF groups in the MSC group.

N SRDF/A is not running in MSC or dependent write consistency has not been achieved at the remote site across all RDF groups in the MSC group.

Y MSC is running in SRDF/Star mode and the SRDF/Star environment is now able to provide a differential resynchronization between the two remote sites.

N MSC is either not running in SRDF/Star mode or has not yet achieved the ability to provide differential resynchronization between the two remote sites.

#SQ SRDFA 253

Command Reference

Example 2 The #SQ SRDFA,LCL command issued to the secondary side generates the following output:

EMCQR00I SRDF-HC DISPLAY FOR (15) &SQ SRDFA,LCL(4D00,BF) 097 MY SERIAL # MY MICROCODE ------------ ------------ 000190300341 5772-97 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- BF Y F B0 000190300353 5773-134 G(R1>R2) SRDFA A STAR MSFSE2SC2 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO (MSFSTAR ) ---------------------------------------------------------------------- SECONDARY SIDE: CYCLE NUMBER 1,516 CYCLE TOD Unavailable R2<5773 SECONDARY CONSISTENT ( Y ) CYCLE SUSPENDED ( N ) RESTORE DONE ( Y ) RECEIVE CYCLE SIZE 933 APPLY CYCLE SIZE 0 AVERAGE CYCLE TIME 4 AVERAGE CYCLE SIZE 942 TIME SINCE LAST CYCLE SWITCH 18 DURATION OF LAST CYCLE 4 MAX THROTTLE TIME 0 MAX CACHE PERCENTAGE 80 TOTAL RESTORES 15,248,329 TOTAL MERGES 1,596,192 SECONDARY DELAY 7,872 DROP PRIORITY 33 CLEANUP RUNNING ( N ) HOST INTERVENTION REQUIRED ( N ) SRDF/A TRANSMIT IDLE ( Y ) SRDF/A DSE ACTIVE ( N ) MSC ACTIVE ( Y ) ACTIVE SINCE 03/26/2009 12:10:56 RECEIVE TAG E0000000 000000C5 APPLY TAG E0000000 000000C4 GLOBAL CONSISTENCY ( Y ) STAR RECOVERY AVAILABLE ( Y ) STAR SRDF/A AHEAD ( N ) STAR/S TARGET INCONSISTENT ( N ) CEXMPT COUNT ( 3 ) ---------------------------------------------------------------------- END OF DISPLAY

Figure 18 #SQ SRDFA command secondary side

The fields that can appear in the #SQ SRDFA secondary side display have the following meanings:

◆ MY GRP


◆ SECONDARY SIDE

Secondary Side indicates that the query was done on the secondary side of the RDF configuration.

◆ CYCLE NUMBER

The Cycle Number is a number representing the cycle that SRDF/A is on. When running in either MSC active or not this number will continue to increase each time a cycle switch occurs.


Command Reference

◆ CYCLE TOD

The approximate time of day (TOD) that the data on the SRDF/A R2 represents. The CYCLE TOD value is provided as a convenience when an approximate time of day value for an SRDF/A R2 would be useful for operational purposes.

The timestamp is expressed in the time of the host issuing the #SQ SRDFA command. It is computed by subtracting the Symmetrix-provided time lag (that is, the number of seconds elapsed since the apply cycle became a transmit cycle) from the current z/OS TOD.

If the TOD is not reported, the CYCLE TOD field will contain one of the following responses:

• "UNAVAILABLE R1<5773" indicates that the Symmetrix system on the R1 source side is at an Enginuity level prior to 5773.

• "UNAVAILABLE R2<5773" indicates that the Symmetrix system on the R2 target side is at an Enginuity level prior to 5773.

IMPORTANT!CYCLE TOD provides an approximate timestamp for the data in the 'apply' cycle of an SRDF/A configuration. It is based on the Symmetrix timers and is accurate to within a few seconds. It does not represent z/OS system time and should not be used for any recovery operations that require accurate system time as input.

◆ SECONDARY CONSISTENT

Secondary Consistent indicates whether the secondary side is consistent:

Y SRDF/A is consistent

N SRDF/A is not consistent

? SRDF/A is not active, and the data on the secondary side may or may not be consistent. Since SRDF/A is not active, the consistency cannot be determined by SRDFA.

#SQ SRDFA 255

Command Reference

◆ CYCLE SUSPENDED

Cycle Suspended indicates the status of cycle switching as follows:

◆ RESTORE DONE

Restore Done indicates the status of the apply cycle as follows:

◆ RECEIVE CYCLE SIZE

Receive Cycle Size is the number of slots currently in the cycle actively being written to from the primary side.

◆ APPLY CYCLE SIZE

Apply Cycle Size is the number of slots currently in the cycle actively being restored to the secondary devices.

◆ AVERAGE CYCLE TIME

Average Cycle Time is the average time each cycle has taken over the past sixteen cycles.

◆ AVERAGE CYCLE SIZE

Average Cycle Size is the average number of slots in the past sixteen cycles.

◆ TIME SINCE LAST CYCLE SWITCH

Time Since Last Cycle Switch is the number of seconds since the last time SRDF/A has cycle switched.

◆ DURATION OF LAST CYCLE

The Duration of Last Cycle is the number of seconds the last cycle lasted.

Y The cycle switching will be delayed by software to perform a consistent operation (TimeFinder Remote Consistent Split).

N SRDF/A will operate in the normal cycle switching mechanism.

Y The apply cycle is completely restored.

N The apply cycle is not completely restored.


Command Reference

◆ MAX THROTTLE TIME

Maximum Throttle Time indicates how long SRDF/A will slow the host adapters once cache limits are reached.

• If the value is 0, then once cache limits are reached, SRDF/A is dropped.

• If the value is 65535, then the host adapters will work at write pending limits indefinitely.

• Any other value represents the number of seconds the host adapters will work at write pending limits before SRDF/A will be dropped.

◆ MAX CACHE PERCENTAGE

Maximum Cache Percentage is the percentage of cache that SRDF/A is allowed to use.

◆ TOTAL RESTORES

Total Restores is the total number of slots restored from all of the apply cycles up to the time the display was requested.

◆ TOTAL MERGES

Total Merges is the total number of slots merged in cache during the restore of all of the apply cycles up to the time the display was requested.

◆ SECONDARY DELAY

Secondary Delay is the approximate amount of time the data on the secondary side is behind the data on the primary side.

◆ DROP PRIORITY

Drop Priority displays the relative priority of this SRDF/A session with regard to the dropping of SRDF/A sessions. If the maximum percentage of cache SRDF/A may use is exceeded, the Drop Priority determines the order in which SRDF/A sessions are dropped in this Symmetrix to relieve the condition. The highest priority is 1; the lowest is 64.

Note: The Drop Priority set in the remote side RDF group has no effect on the Drop Priority in this RDF group.

#SQ SRDFA 257

Command Reference

◆ CLEANUP RUNNING

Cleanup Running indicates the cleanup status as follows:

If cleanup is running on the secondary side and Host Intervention Required is also “Y”, then cleanup will not finish until MSC tells SRDF/A what to do with the complete receive cycle on.

◆ HOST INTERVENTION REQUIRED

Host Intervention Required indicates status as follows:

◆ SRDFA TRANSMIT IDLE

This option indicates the Transmit Idle state:

“SRDFA TRANSMIT IDLE” on page 250 provides information about the Transmit Idle state.



Y Indicates a small window of time (approximately 30 seconds when not running in MSC) that non-SRDF/A I/O will be rejected by the secondary side. Cleanup will only run immediately after SRDF/A goes from active to inactive. Cleanup prevents RDF_RSUM, REFRESH RFR_RSUM,RNG_REFRESH, RNG_RSUM, or VALIDATE INVALIDATE from being run on the SRDF/A devices. After the cleanup is finished, these commands may be run.

N Cleanup is not running.

Y When Cleanup Running is also Y, MSC must tell SRDF/A what to do with the complete receive cycle on.

Note: In an SRDF/Star environment, the SCFRDFME utility may be required to clear the intervention. “SRDF/A MSC and SRDF/Star recovery considerations” on page 458 provides additional information.

N Host intervention is not required.

Y Transmit Idle is enabled for the RDF group.

N Transmit Idle is not enabled.

Y The SRDF/A DSE feature is active for this RDF group on this Symmetrix.

N The SRDF/A DSE feature is not active for this RDF group on this Symmetrix.


Command Reference

◆ MSC ACTIVE

MSC Active indicates whether the SRDF/A RDF group is part of an MSC group:

◆ ACTIVE SINCE

This is the date and time that the SRDF/A session joined MSC.

◆ RECEIVE TAG

Receive Tag is the tag for the data in the receive cycle. The tag is used to verify that the SRDF/A RDF groups in the MSC group are in step. The tag when MSC is active is analogous to the cycle number used when SRDF/A is active and MSC is not active.

◆ APPLY TAG

Apply Tag is the tag for the data in the apply cycle. The tag is used to verify that the SRDF/A RDF groups in the MSC group are in step. When MSC is active, this tag is analogous to the cycle number used when SRDF/A is active and MSC is not active.

◆ GLOBAL CONSISTENCY

Global Consistency indicates the status of dependent write consistency as follows:

◆ STAR RECOVERY AVAILABLE

Star Recovery Available indicates the status of MSC and SRDF/Star mode as follows:

Y The SRDF/A RDF group is part of an MSC group. The MSC group is one of a set of SRDF/A RDF groups whose cycle switching is controlled by the host and not the Symmetrix. When SRDF/A is not active and MSC Active = “Y”, it indicates that SRDF/A was deactivated or dropped while MSC was active.

N SRDF/A is not part of an MSC group.

Y Dependent write consistency has been achieved at the remote site across all RDF groups in the MSC group.

N SRDF/A is not running in MSC or dependent write consistency has not been achieved at the remote site across all RDF groups in the MSC group.

Y MSC is running in SRDF/Star mode and the SRDF/Star environment is now able to provide a differential resynchronization between the two remote sites.

N MSC is either not running in SRDF/Star mode or has not yet achieved the ability to provide differential resynchronization between the two remote sites.

#SQ SRDFA 259

Command Reference

◆ STAR SRDFA AHEAD

Star SRDFA Ahead indicates the following:

◆ STAR/S TARGET INCONSISTENT

Star/S Target Inconsistent indicates the following:

◆ CEXMPT COUNT

This field indicates the number of consistency exempt devices in the RDF group. Consistency exempt is activated on a group basis.

Y MSC is running in SRDF/Star mode and the data on the SRDF/A secondary device is more current than that on the non-SRDF/A secondary device.

N MSC is not running in SRDF/Star mode or the SRDF/A secondary device does not contain more current data than the non-SRDF/A secondary device.

Y Synchronous secondary data should be considered as inconsistent.

N Synchronous secondary data should be considered as consistent. Synchronous secondary data is considered consistent if you are running SRDF/Star and Star recovery is available.


Command Reference

Example 3 This example illustrates use of the CYCLETOD parameter. The CYCLETOD parameter is used only for an SRDF/A query for all groups. It is ignored for an SRDF/A query for a specific group.

To query all local groups, use the following format:

#SQ SRDFA,cuu,CYCLETOD

To query all remote groups, use the following format:

#SQ SRDFA,RMT(cuu,mhlist,*),CYCLETOD

where * is a wildcard character that represents all RDF groups.

For example, the #SQ SRDFA,4200,CYCLETOD command generates the following output:

EMCMN00I SRDF-HC : (1) @@SQ SRDFA,4200,CYCLETOD EMCQR00I SRDF-HC DISPLAY FOR (1) @@SQ SRDFA,4200,CYCLETOD 629 IGRP(00) UNKNOWN SIDE: CYCLE# N/A CYCLE TOD = 0 (UNAVAILABLE) IGRP(02) UNKNOWN SIDE: CYCLE# N/A CYCLE TOD = 0 (UNAVAILABLE) AGRP(06) PRIMARY SIDE: CYCLE# N/A CYCLE TOD UNAVAILABLE ON PRIMARY AGRP(26) SECONDARY SIDE: CYCLE# N/A CYCLE TOD (UNAVAILABLE R1<5773) IGRP(44) SECONDARY SIDE: CYCLE# 1 CYCLE TOD 04/03/2008 19:34:42 AGRP(79) PRIMARY SIDE: CYCLE# N/A CYCLE TOD UNAVAILABLE ON PRIMARY IGRP(82) SECONDARY SIDE: CYCLE# 1,325 CYCLE TOD 03/25/2008 20:41:17 IGRP(E0) SECONDARY SIDE: CYCLE# 11,002 CYCLE TOD 04/07/2008 09:55:07 IGRP(F3) UNKNOWN SIDE: CYCLE# N/A CYCLE TOD = 0 (UNAVAILABLE) END OF DISPLAY

Note: For a specific group query where SRDF/A is active, the full #SQ SRDFA display appears. If SRDF/A is inactive on that group, message EMCQR06I is issued to display any available CYCLE TOD information.

◆ AGRP indicates that SRDF/A is active on the RDF group shown in parentheses.

◆ IGRP indicates that SRDF/A is inactive on the RDF group shown in parentheses.

The line will have one of the formats listed below:

Note: If the local Symmetrix system is below Enginuity level 5773, then Format 7 will be automatically issued (only once as it applies to the entire Symmetrix).

Format 1 — IGRP(nn) SECONDARY SIDE: CYCLE# <#> CYCLE TOD mm/dd/yyyy hh:mm:ss

The command was issued to the secondary side and the primary side was at Enginuity level 5773 or higher. The reported CYCLE# is the last cycle that was completed at the date and time indicated in the message.

#SQ SRDFA 261

Command Reference

Format 2 — IGRP(nn) SECONDARY SIDE: CYCLE# N/A CYCLE TOD (UNAVAILABLE R1<5773)

The command was issued to the secondary side and the cycle TOD is unavailable because the primary side is below Enginuity level 5773.

Format 3 — AGRP(nn) SECONDARY SIDE: CYCLE# N/A CYCLE TOD UNAVAILABLE < 5773

The command was issued to the secondary side and the cycle TOD is unavailable because the secondary side is below Enginuity level 5773.

Format 4 — IGRP(nn) PRIMARY SIDE: CYCLE# N/A CYCLE TOD UNAVAILABLE ON PRIMARY

The command was issued to the primary side and the cycle TOD is not available on the primary side.

Format 5 — IGRP(nn) UNKNOWN SIDE: CYCLE# N/A CYCLE TOD = 0 (UNAVAILABLE)

The cycle age is zero.

Format 6 — IGRP(nn) UNKNOWN SIDE: CYCLE# N/A CYCLE TOD = -1 (UNAVAILABLE)

The cycle age is -1.

Format 7 — GRP(ALL) UNKNOWN SIDE: CYCLE# N/A CYCLE TOD UNAVAILABLE < 5773

The side to which the command was issued is below Enginuity level 5773.


Command Reference

#SQ SRDFA_DSEThe #SQ SRDFA_DSE command displays Delta Set Extension status and resource usage. This command requires Enginuity level 5772 or higher.

Note: “SRDF/A Delta Set Extension” on page 43 provides a detailed description of this feature.

Syntax

Parameters cqname


cuu


G(groupname)


LCL


#SQ SRDFA_DSE , cuu


,G( groupname)

,SCFG(scfgroupname)

,RMT( rdf cuu )

,RMT( cuu,mhlist )

1


1

,CQNAME= cqname


#SQ SRDFA_DSE 263

Command Reference

mhlist


queue-option


rdfgroup#


RMT


SCFG(scfgroupname)


Examples

Example 1 Figure 19 displays the output shown from the primary side when SRDF/A is active:

EMCQR00I SRDF-HC DISPLAY FOR (38) ¢¢SQ SRDFA_DSE,LCL(DE01,F0) 985 MY SERIAL # MY MICROCODE ------------ ------------ 000190300097 5772-37 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- F0 Y F F1 000190300338 5772-37 G(R1>R2) SRDFA ACTIVE KCH0F0B DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO ---------------------------------------------------------------------- PRIMARY SIDE: CYCLE NUMBER 7,887 SRDFA DSE ACTIVE ( N ) THRESHOLD PERCENTAGE 20 SRDFA DSE AUTO ACTIVATE ( N ) CAPTURE CYCLE SIZE 0 TRANSMIT CYCLE SIZE 0 DSE USED TRACKS 0 DSE USED TRACKS 0 DSE MDATA TRACKS 0 DSE MDATA TRACKS 0 ---------------------------------------------------------------------- FBA POOL NAME DSE FBA2 3390 POOL NAME DSE 33902 AS400 POOL NAME DSE A4002 3380 POOL NAME DSE 33802 ---------------------------------------------------------------------- END OF DISPLAY

Figure 19 #SQ SRDFA_DSE - primary side output


Command Reference

The fields in Figure 19 on page 263 have the following meanings:

◆ MY SERIAL #


◆ MY MICROCODE


◆ MY GRP


◆ ONL


◆ PC

The protocol of the RDF group. The values E (ESCON), F (Fibre), IP, and U may appear. If a U appears, the protocol is unknown and the group is likely offline.

◆ OS GRP


◆ OS SERIAL


◆ OS MICROCODE


◆ SYNCHDIR


#SQ SRDFA_DSE 265

Command Reference

◆ FEATURE


◆ LABEL


◆ TYPE




◆ LINKS_DOMINO












Command Reference

◆ MSC_GROUP


◆ PRIMARY SIDE

Indicates that the query was done on the R1 side of the SRDF/A RDF group.



◆ THRESHOLD PERCENTAGE

This is the percentage of the system write pending limit which, when reached for an SRDF/A RDF group in the system (or Cache Partition) causes SRDF/A Delta Set Extension to be invoked for that RDF group.

◆ SRDFA DSE AUTO ACTIVATE

SRDFA DSE Auto Activate indicates the status of the DSE auto-activate feature as follows:


The total number of tracks in the Capture cycle, including the delta set extension and metadata slots.


Total number of tracks in the Transmit cycle, including the delta set extension and metadata slots.

◆ DSE USED TRACKS

The number of tracks in the associated Capture, Transmit, Receive, or Apply cycle that have been spilled onto disk.

Y The SRDF/A DSE feature is active for this RDF group on this Symmetrix.

N The SRDF/A DSE feature is not active for this RDF group on this Symmetrix.

Y The auto-activate feature of SRDF/A DSE is enabled for the RDF group when SRDF/A is active. Once auto-activate is set, it continues to apply even if SRDF/A drops and resumes.

N The auto-activate feature for DSE is not enabled.

#SQ SRDFA_DSE 267

Command Reference

◆ DSE MDATA TRACKS

The number of metadata tracks used by associated Capture, Transmit, Receive, or Apply cycle. Metadata tracks are used approximately 1 for every 512 tracks of delta set extension tracks.

◆ FBA POOL NAME

The DSE pool name associated with the RDF group for FBA(512) emulation.

◆ AS400 POOL NAMEThe DSE pool name associated with the RDF group for FBA(520) emulation.

◆ 3390 POOL NAME

The DSE pool name associated with the RDF group for 3390 emulation.

◆ 3380 POOL NAME

The DSE pool name associated with the RDF group for 3380 emulation.

Example 2 Figure 20 displays the output shown when DSE is engaged and one pool is draining from the primary side:

EMCQR00I SRDF-HC DISPLAY FOR (74) ¢¢SQ SRDFA_DSE,LCL(DE01,F0) 289 MY SERIAL # MY MICROCODE ------------ ------------ 000190300097 5772-37 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- F0 Y F F1 000190300338 5772-37 G(R1>R2) SRDFA A MSC KCH0F0B DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO (MSCKCH ) ---------------------------------------------------------------------- PRIMARY SIDE: CYCLE NUMBER 7,913 SRDFA DSE ACTIVE ( Y ) THRESHOLD PERCENTAGE 20 SRDFA DSE AUTO ACTIVATE ( Y ) CAPTURE CYCLE SIZE 17,876 TRANSMIT CYCLE SIZE 0 DSE USED TRACKS 5,602 DSE USED TRACKS 0 DSE MDATA TRACKS 16 DSE MDATA TRACKS 0 ---------------------------------------------------------------------- FBA POOL NAME DSE FBA2 3390 POOL NAME DSE 33902 AS400 POOL NAME DSE A4002 3380 POOL NAME DSE 33802 ----------------------------------------------------------------------DRAINING POOL 0 DSE 3390 DRAINING POOL 1 ----------------------------------------------------------------------END OF DISPLAY

Figure 20 #SQ SRDFA_DSE - one pool draining from primary side


Command Reference

The additional field in Figure 20 on page 267 has the following meaning:

◆ DRAINING POOL x

Where x = 0 - 7

When a DSE pool associated with an RDF group is disassociated from the RDF group, the data will naturally drain off of that pool after two SRDF/A cycles. While the RDF group is still draining the data, up to eight of these pools can be displayed. When there are no pools draining, this field will be blank.

Example 3 Figure 21 displays the secondary side output with SRDF/A active:

EMCQR00I SRDF-HC DISPLAY FOR (79) ¢¢SQ SRDFA_DSE,RMT(DE01,F0) 784 MY SERIAL # MY MICROCODE ------------ ------------ 000190300338 5772-37 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- F1 Y F F0 000190300097 5772-37 G(R1>R2) SRDFA ACTIVE KCH0F0B DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO ----------------------------------------------------------------------SECONDARY SIDE: CYCLE NUMBER 7,917 SRDFA DSE ACTIVE ( Y ) THRESHOLD PERCENTAGE 20 SRDFA DSE AUTO ACTIVATE ( Y ) RECEIVE CYCLE SIZE 3,185 APPLY CYCLE SIZE 0 DSE USED TRACKS 0 DSE USED TRACKS 0 DSE MDATA TRACKS 0 DSE MDATA TRACKS 0 ----------------------------------------------------------------------FBA POOL NAME DSE FBA2 3390 POOL NAME DSE 33902 AS400 POOL NAME DSE A4002 3380 POOL NAME DSE 33802 ---------------------------------------------------------------------- END OF DISPLAY

Figure 21 #SQ SRDFA_DSE - secondary side output

The fields in this output are described starting on page 263. The following additional secondary fields display:

◆ SECONDARY SIDE

Indicates that the query was done on the R2 side of the SRDF/A RDF group.


Total number of tracks in the Receive cycle, including the delta set extension and metadata slots.

#SQ SRDFA_DSE 269

Command Reference


Total number of tracks in the Apply cycle, including the delta set extension and metadata slots.

Example 4 Figure 22 displays the secondary side output with the Delta Set Extension (DSE) active and MSC:

EMCQR00I SRDF-HC DISPLAY FOR (115) &SQ SRDFA_DSE,LCL(C100,34) 346 MY SERIAL # MY MICROCODE ------------ ------------ 000190300338 5772-43 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- F0 Y F F1 000190300344 5772-42 G(R1>R2) SRDFA A MSC KCH0F0B DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO (MSCKCH ) ---------------------------------------------------------------------- SECONDARY SIDE: CYCLE NUMBER 46 SRDFA DSE ACTIVE ( Y ) THRESHOLD PERCENTAGE 20 SRDFA DSE AUTO ACTIVATE ( Y ) RECEIVE CYCLE SIZE 24,997 APPLY CYCLE SIZE 0 DSE USED TRACKS 1,444 DSE USED TRACKS 0 DSE MDATA TRACKS 8 DSE MDATA TRACKS 0 ---------------------------------------------------------------------- FBA POOL NAME DSE FBA2 3390 POOL NAME DSE 33902 AS400 POOL NAME DSE A4002 3380 POOL NAME DSE 33802 ---------------------------------------------------------------------- END OF DISPLAY

Figure 22 #SQ SRDFA_DSE - secondary side output with DSE active and MSC


Command Reference

#SQ SRDFA_VOLThe #SQ SRDFA_VOL command displays volume information.

Note that the gatekeeper specified by cuu in the command does not have to be an SRDF/A device. It is used only to identify the Symmetrix system containing the RDF group whose SRDF/A volume status is being determined.

Syntax

The #SQ SRDFA_VOL command syntax continues on the next page.

, cuu

,G( groupname)

,SCFG(scfgroupname)

,RMT( rdf cuu )

,RMT( cuu,mhlist )

2

1

,VOL( volser )

,SSID( ssidnumber )

3


1

,LCL( cuu , rdfgroup#) 2

#SQ SRDFA_VOL

,count

,count,startingdev#

,ALL,startingdev#

2 3

,ALL

#SQ SRDFA_VOL 271

Command Reference

Parameters count

Specifies the number of devices to display. This value can be set from 1 to 64 (decimal), or ALL. ALL indicates that all devices are to be included up to the number equal to the value of the MAX_QUERY initialization parameter.

If this parameter is not specified, count defaults to 1.

cqname


cuu


G(groupname)


LCL


queue-option


RMT


SCFG(scfgroupname)


SSID(ssidnumber)


3

,CQNAME= cqname



Command Reference

startingdev#

Specifies the Symmetrix device number at which to start the display. This parameter is optional.



VOL(volser)


Examples

Example 1 #SQ SRDFA_VOL displays the output shown in Figure 23.

EMCMN00I SRDF-HC : (9) ¢¢SQ SRDFA_VOL,6F00 EMCQV31I SRDF-HC DISPLAY FOR (9) ¢¢SQ SRDFA_VOL,6F00 225 DV_ADDR| _SYM_ | | CAPTURE | TRANSMIT | SYS CH|DEV RDEV GP|VOLSER| CYCLE SIZE | CYCLE SIZE | 6C00 00 0000 0000 01 U6A000 0 0 END OF DISPLAY

Figure 23 #SQ SRDFA_VOL command primary side

The fields in Figure 23 have the following meanings:

◆ DV_ADDR SYS

z/OS device number.

Note: This displays “????” for devices specified in the SCF exclude list.

◆ DV_ADDR CH

First device address (hex) on the channel as specified in the IOCP gen.

Note: This field displays “??” for devices not online during startup and devices put online after the last #SC GLOBAL,SSID_REFRESH command.

◆ SYM_DEV


◆ SYM_RDEV

Remotely-mirrored Symmetrix device number.

#SQ SRDFA_VOL 273

Command Reference

◆ SYM_GP

RDF group number.

◆ VOLSER

Device volume serial. If the device was online at EMCRDF startup or during an #SC GLOBAL,SSID_REFRESH command, the volume serial is from the UCB; otherwise, it is the volume serial assigned to the device when the Symmetrix system was installed, or the value set in the INIT_VOLSER parameter in the initialization parameters.

If the device is identified as a Fixed Block Architecture (FBA) device, it appears as follows:

• *FBA* denotes FBA devices (that are not in an FBA meta group) on all Symmetrix models with an Enginuity level lower than 5771.

• *F64* denotes FBA devices (that are not in an FBA meta group) on Symmetrix models with an Enginuity level higher than 5771.

• *FBAM* denotes FBA meta head devices on all Symmetrix models with an Enginuity level lower than 5771.

• *F64M* denotes FBA meta head devices on all Symmetrix models with an Enginuity level higher than 5771.


The current number of tracks in the cycle that is being created on the primary side of the SRDF/A session. This value is shown only on a display of the primary side of the SRDF/A session.


The number of tracks remaining to be transmitted in the cycle that is currently being transmitted to the secondary side of the SRDF/A session. This value is shown only on a display of the primary side of the SRDF/A session.

Example 2 #SQ SRDFA_VOL command displays output shown in Figure 24.

EMCMN00I SRDF-HC : (10) ¢¢SQ SRDFA_VOL,RMT(6F00,01) EMCQV31I SRDF-HC DISPLAY FOR (10) ¢¢SQ SRDFA_VOL,RMT(6F00,01) DV_ADDR| _SYM_ | | RECEIVE | APPLY | SYS CH|DEV RDEV GP|VOLSER| CYCLE SIZE | CYCLE SIZE | ???? ?? 0000 0000 32 OFLINE 0 0 END OF DISPLAY

Figure 24 #SQ SRDFA_VOL command secondary side


Command Reference

The fields in Figure 24 have the following meanings:

◆ DV_ADDR SYS

z/OS device number. This displays “????” for devices specified in the SCF exclude list.

◆ DV_ADDR CH

First device address on the channel as specified in the IOCP gen. This field displays “??” for devices not online during startup and devices put online after the last #SC GLOBAL,SSID_REFRESH.

◆ SYM_DEV


◆ SYM_RDEV


◆ SYM_GP

RDF group number.

◆ VOLSER

Device volume serial. If the device was online at EMCRDF startup or during an #SC GLOBAL,SSID_REFRESH command, the value is obtained from the UCB; otherwise, it is the volume serial assigned to the device when the Symmetrix system was installed, or the value set in the INIT_VOLSER parameter in the initialization parameters. If the device is identified as a Fixed Block Architecture (FBA) device, it appears as follows:




• *F64M* denotes FBA meta head devices on all Symmetrix models with an Enginuity level higher than 5771.

#SQ SRDFA_VOL 275

Command Reference


The number of tracks in the cycle that is currently being transmitted from the primary side of the SRDF/A session. This value is shown only on a display of the secondary side of the SRDF/A session.


The number of tracks remaining to be applied to secondary-side devices in the cycle most recently received from the primary side of the SRDF/A session. This value is shown only on a display of the secondary side of the SRDF/A session.


Command Reference

#SQ SSIDThe #SQ SSID command displays the subsystem IDs found on this z/OS image and the number of devices associated with them during the SRDF initialization, or after execution of the most recent #SC GLOBAL,SSID_REFRESH. command.

Syntax

Parameters ALL

All indicates that all SSIDs are to be included up to the number of MAX_QUERY initialization parameter.

count

Specifies the number of SSIDs to display. You can set this value from 1 to 64. If you do not specify this parameter, count defaults to 1.

cqname


queue-option


Comments Setting the parameter value to ALL displays all SSIDs found with devices online to the z/OS image.

Example The following example displays the output from an #SQ SSID command:

EMCQS81I SRDF-HC DISPLAY FOR (1) JS SQ SSID,ALL 241 SSID #DEV EMUL SYM CUU_ CH _DV_ CUU_ CH _DV_ ONLN SERIAL# 0C00 0100 2105 7 0C00 00 0010 0CFF FF 01EF 0020 000190300044 1000 0100 2105 6 1000 00 00C0 10FF FF 027F 0000 000187720603 1001 0100 2105 6 1100 00 0280 11FF FF 043F 0000 000187720603

#SQ SSID

,count

,ALL

,CQNAME= cqname


#SQ SSID 277

Command Reference


◆ SSID

Subsystem ID.

◆ #DEV

Number of devices (in hex) that are known for this SSID.

◆ EMUL

The emulation mode. If the Symmetrix is marked 'invalid' internally, INV is shown here. Otherwise, the emulation mode can be 2105, 2107, or 3990. It can also be 'EMC' if the controller flags indicate that none of the above emulation modes is in effect but that the controller is an EMC controller.

◆ SYM

The Symmetrix model level. This can be 3, 4, 5, 6 or 7. If the model is none of these, an asterisk is shown.

◆ CUU

The first z/OS device number found online for this SSID.

◆ CH

The first device address (hex) on the channel as listed in the IOCP gen.

◆ DV

The first Symmetrix device number.

◆ CUU

The last cuu found online for this SSID.

◆ CH

The last device address on the channel as listed in the IOCP gen.

◆ DV

The last Symmetrix device number.

◆ ONLN

The number of devices (in hex) that are online (at this point in time) for this SSID.

◆ SERIAL#

The Symmetrix serial number.


Command Reference

#SQ STATEThe #SQ STATE command displays the status of individual Symmetrix volumes including online, offline, synchronization state, write protection state, and SRDF mode of operation. All of the statuses that a volume has when the command is issued are shown; positions are provided on the display lines for all status indicators.

Syntax

The #SQ STATE command syntax continues on the next page.

#SQ STATE

, state-filter

, cuu

,G(

groupname)

,SCFG(scfgroupname)

,RMT(

rdf

cuu

)

,RMT(

cuu,mhlist

)

1

,VOL(

volser

)

,SSID(

ssidnumber

)

3

,RMT(


, count


, ALL,

startingdev#

1

3

, ALL

, state-filter

,LCL(

cuu

, rdfgroup#)

2

#SQ STATE 279

Command Reference


Specifies the means by which the particular devices to display or include are determined.

count specifies the number of devices, starting from the first, that are to be included. It can be specified as an integer from 1 through the value specified in the MAX_QUERY initialization parameter.

ALL indicates that all devices are to be included starting from the first up to the number specified by the value of the MAX_QUERY initialization parameter.


#SQ STATE,cuu,count,startingdev#


Note: Table 8 on page 287 describes valid state-filter values.

The count and ALL options cannot be used with the SCFG(scfgroupname), G(groupname), or VOL(volser) parameters.

3

,count

,count,startingdev#

,ALL,startingdev#

2 3

,ALL

,CQNAME= cqname



Command Reference

cqname


cuu


G(groupname)


LCL


mhlist


queue-option


rdfcuu


rdfgroup#


RMT


SCFG(scfgroupname)


SSID(ssidnumber)


startingdev#

Specifies the Symmetrix device number with which to start the display. This parameter is optional.



#SQ STATE 281

Command Reference

VOL(volser)


Comments Only SRDF volumes display INV_TRK values.

An invalid track occurs when data is written to a disk track, and that data is not yet reflected on the partner device. The track on the partner device is said to be invalid. In the normal case, where the source (R1) and target (R2) volumes are in communication and staying in synch, the updated track is passed to the target device, and once it is written there, it is no longer invalid. If the source and target devices are not in communication for some reason, for instance, if the SRDF links are disabled, the invalid tracks build up over time.

The R1 invalid track count can also be built up if the local source (R1) mirrors are not ready while the link is operational and data is being written to the source (R1) volume. In this case the data would be sent across the link to the R2 devices. The invalid tracks may be cleared using the procedures outlined in Chapter 6, “Recovery Procedures.”

Example The following example displays the output from an #SQ STATE command:

EMCMN00I SRDF-HC : (163) &SQ STATE,8700 EMCQV01I SRDF-HC DISPLAY FOR (163) &SQ STATE,8700 077 DVA | _SYM_ | |SYS |W S A L R T I D A N C| | R1 | R2 | SY SYS |DEV RDEV GP|VOLSER|STAT|R N D N N G T O C / X|MR|INVTRK|INVTRK| % | | | |T C C R R T A M T R T| | | | 8700 0020 OFFLIN OFFL W . . . . . . . . . . END OF DISPLAY

The fields in this example have the meanings indicated for each column header:

◆ DVA SYS

z/OS device number. This field displays “????” for devices specified in the SCF exclude list.

◆ SYM_DEV


◆ SYM_RDEV


◆ SYM_GP

RDF group number.


Command Reference

◆ VOLSER

Device volume serial. If the device was online at EMCRDF startup or during an #SC GLOBAL,SSID_REFRESH command, the volume serial is from the UCB; otherwise, it is the volume serial assigned to the device when the Symmetrix system was installed or the value set in the INIT_VOLSER parameter in the initialization parameters. If the device is identified as a Fixed Block Architecture (FBA) device, it appears as follows:




• *F64M* denotes FBA meta head devices on all Symmetrix models with Enginuity level higher than 5771.

◆ SYS STATUS

z/OS device status. Values that may appear are:

NOSC No subchannel for device

HTIO Device is in hot I/O status

PAPV Pending offline, allocated, mounted private

PAPB Pending offline, allocated, mounted public

PAST Pending offline, allocated, mounted storage

OFFL Device offline to z/OS

ONPV Online, mounted private

ONPB Online, mounted public

ONST Online, mounted storage

OAPV Online allocated, mounted private

OAPB Online allocated, mounted public

OAST Online allocated, mounted storage

N/A UCB was not available

#SQ STATE 283

Command Reference

◆ WRT

Read/Write mode. Values that may appear are:

◆ SNC

Synchronous mode. Values that may appear are:

Note: Semi-synchronous mode is not supported on Symmetrix DMX-3 models or on any Symmetrix model with FICON directors.

◆ ADC

Adaptive Copy mode. Values that may appear are:

◆ LNR

Link status. Values that may appear are:

◆ RNR

RDF status. Values that may appear are:

W Read/Write enabled

. Read/Write disabled

SS Semi-synchronous mode

SY Synchronous mode

. Neither

W Adaptive Copy Write Pending mode

D Adaptive Copy Disk mode

A SRDF/A

. None

L Links not ready

. Links ready

U USR not ready

R RDF not ready

. RDF ready


Command Reference

◆ TGT

Target status. Values that may appear are:

◆ ITA

Invalid track attribute status. Values that may appear are:

◆ DOM

Domino mode. Values that may appear are:

◆ ACT

Recovery action. Values that may appear are:

◆ N/R

Not ready. Values that may appear are:

◆ CXT

Consistency exempt. Values that may appear are:

R RDF write disabled

T Target not ready

. Neither

I Invalid track attribute enabled

. Invalid track attribute disabled

D Domino mode enabled

. Domino mode disabled

R Refresh

V Validate

. Neither

N Not ready

. Ready

X Consistency exempt mode enabled for the device

. Consistency exempt mode disabled for the device

M Mixed - in the case where a logical Symmetrix device is a meta and some of the meta members are consistency exempt and others are not

#SQ VOL 285

Command Reference

#SQ VOLThe #SQ VOL command displays the status of individual Symmetrix volumes including online, offline, synchronization state, write protection state, and SRDF mode of operation. One line per remote mirror, or exactly one line for volumes that are not RDF volumes, is displayed.

Syntax

1 When the format RMT(rdfcuu) is used, rdfcuu must be the MVS device address of an R1 device. If the device is not an RDF device, or if it is not an R1 device, message EMCPC07I will be issued. If rdfcuu is a concurrent or cascaded device, then one of the rdfgroups must be specified, or message EMCMN00I will be issued.

The #SQ VOL command syntax continues on the next page.

#SQ VOL

,RMT(rdfcuu)


,SSID( ssidnumber )

,RMT( cuu,mhlist )


1

,G( groupname)

,SCFG(scfgroupname)

,VOL( volser ) 3

,cuu

2

, state-filter

1


Command Reference


Specifies the means by which the particular devices to display or include is determined.

count specifies the number of devices, starting from the first, that are to be included. It can be specified as an integer from 1 through the value specified in the MAX_QUERY initialization parameter.

ALL indicates that all devices are to be included up to the value of the MAX_QUERY initialization parameter.

3

,count

,count,startingdev#

,ALL,startingdev#

2 3

,ALL

,CQNAME= cqname


,count

,count,startingdev#

,All,startingdev#

1

,ALL

,state-filter

3

#SQ VOL 287

Command Reference


#SQ VOL,cuu,count,startingdev#


The count and ALL parameters cannot be used with the SCFG(scfgroupname), G(groupname), or VOL(volser) parameters.

Table 8 lists values you may specify for state-filter.

Table 8 Possible state-filter values (page 1 of 3)

Value Includes devices that...

ADCOPY have a control unit status of AW

ADCOPY_DISK have a control unit status of AD

ALLD are all diskless (equivalent to DL + D1 + D2)

ALLRAID are RAID-S, RAID 5, RAID 6, or RAID 10

ALLT are all thin or thin data devices (equivalent to TD + TH)

B1 are business continuance volumes source (R1 BCVs)

B2 are business continuance volumes target (R2 BCVs)

BCV are standard business continuance volumes

BCVATT are standard devices with an attached (established) BCV

CEXMPT have the consistency exempt state

CGROUP belong to consistency groups

COVD a are cache-only virtual devices

D1 are diskless R1 (transient state)

D2 are diskless R2 (transient state)

D21 are diskless cascaded devices

DL are diskless devices that have not been paired with remote partners

DOMINO have the Domino attribute

DR are dynamic reallocation volumes (used by the Optimizer)


Command Reference

DYNR1 are dynamic-R1 capable

DYNR1_ONLY are only dynamic-R1 capable but not dynamic-R2 capable

DYNR2 are dynamic-R2 capable

DYNR2_ONLY are dynamic-R2 capable but not dynamic-R1 capable

DYNRDF support dynamic RDF functions

EAS b have more than 64K cylinders

ESTBCV are established BCV volumes (that is, actively being used as BCVs)

FBA have Fixed Block Architecture format

FSD are File System devices

IL are link-blocked

INV_TRKS have a non-zero invalid track count

ITA have the Invalid Track attribute

L1 are R1 volumes that are also mirrored locally

L2 are R2 volumes that are also mirrored locally

LNR have a control unit status of LNR

ML are local mirror volumes

MR5 have two or more RAID 5 mirrors

MR6 have two or more RAID 6 mirrors

MRG have at least one RAID 5 or RAID 6 mirror and have at least one other mirror position of RAID 0, RAID 1, RAID 5, or RAID 6 type

NRDY have control unit status of N/R

PREFRESH have the PREFRESH attribute

PVD are PowerVault volumes

R/O have a control unit status of R/O

R/W have a control unit status of R/W

R1 are source (R1) remote volumes in an SRDF device pair

R2 are target (R2) remote volumes



#SQ VOL 289

Command Reference

a. COVDs are required only with Enginuity level 5x70 and earlier. For version 5x71, COVDs are not required.

b. EAS can be specified for the SQ VOL and SQ MIRROR commands only; it is not available for SQ STATE.

R21 are cascaded (R21) devices

R22 are R22 devices

RA(rdfgroup) belong to RA group rdfgroup

RAID are RAID volumes

RAID10 are striped CKD devices

RAID5 are RAID 5 volumes

RAID6 are RAID 6 volumes

RDF_WR_DISABLE have a control unit status of RWD

RDF_NRDY have a control unit status of RNR

REFRESH have the Refresh attribute

SEMI-SYNC have a control unit status of SS

SRDFA includes SRDF/A devices

SV are saved devices in an SRDF device pair

SYNC have a control unit status SY

TD are thin data devices (not host-accessible)

TGT_NRDY have a control unit status of TNR

TH are thin devices (host accessible)

TRANSMIT_IDLE are SRDF/A devices whose SRDF/A session is in the transmit-idle state

VD are virtual devices

Note: Virtual devices do not display in Symmetrix DMX systems. For these systems, use the TimeFinder/Snap query functions to display virtual devices.




Command Reference

cqname


cuu


G(groupname)


LCL


mhlist


queue-option


rdfcuu


rdfgroup#


RMT


SCFG(scfgroupname)


SSID(ssidnumber)


startingdev#

Specifies the Symmetrix device number to start the display. This parameter is optional. This parameter cannot be used with the state-filter parameter.



#SQ VOL 291

Command Reference

VOL(volser)


Comments Only SRDF volumes display INV_TRK values.

Note: Page 281 provides more information regarding invalid track values.

For #SQ VOL, #SQ STATE, #SQ RAID, #SQ MIRROR, and#SQ RAID10 commands, the startingdev# can be a starting VOLSER, or starting MVSCUU if the SORT_BY_MVSCUU or SORT_BY_VOLSER parameters are used.

Examples

Example 1 The following example displays the status of individual Symmetrix volumes for R1 devices:

EMCMN00I SRDF-HC : (92) &SQ VOL,6DB0,5 EMCQV00I SRDF-HC DISPLAY FOR (92) &SQ VOL,6DB0,5 100 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6DB0 B0 00F0 01C0 04 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 6DB1 B1 00F1 01C1 04 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 6DB2 B2 00F2 01C2 04 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 6DB3 B3 00F3 01C3 04 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 6DB4 B4 00F4 01C4 04 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** END OF DISPLAY

Example 2 The following example displays the status of individual Symmetrix volumes for R2 devices:

EMCMN00I SRDF-HC : (93) &SQ VOL,RMT(6C00,04),5,1C0 EMCQV00I SRDF-HC DISPLAY FOR (93) &SQ VOL,RMT(6C00,04),5,1C0 141 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4E68 68 01C0 00F0 04 OFFLIN 1113 OFFL 0 N/R B2 0 0 ** 4E69 69 01C1 00F1 04 OFFLIN 1113 OFFL 0 N/R B2 0 0 ** 4E6A 6A 01C2 00F2 04 OFFLIN 1113 OFFL 0 N/R B2 0 0 ** 4E6B 6B 01C3 00F3 04 OFFLIN 1113 OFFL 0 N/R B2 0 0 ** 4E6C 6C 01C4 00F4 04 OFFLIN 1113 OFFL 0 N/R B2 0 0 ** END OF DISPLAY


Command Reference

Example 3 The following example displays the status of individual Symmetrix volumes for concurrent R1 devices:

EMCMN00I SRDF-HC : (87) &SQ VOL,6D90,5 EMCQV00I SRDF-HC DISPLAY FOR (87) &SQ VOL,6D90,5 945 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D90 90 00D0 00D0 14 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 00D0 2F OFFLIN 1113 OFFL 0 R/W-AS L1 0 ** 6D91 91 00D1 00D1 14 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 00D1 2F OFFLIN 1113 OFFL 0 R/W-AS L1 0 ** 6D92 92 00D2 00D2 14 OFFLIN 1113 OFFL 0 R/W-SY L1 0 0 ** 00D2 2F OFFLIN 1113 OFFL 0 R/W-AS L1 0 ** 6D93 93 00D3 00D3 2F OFFLIN 1113 OFFL 0 R/W-AS L1 0 0 ** 00D3 14 OFFLIN 1113 OFFL 0 R/W-SY L1 0 ** 6D94 94 00D4 00D4 2F OFFLIN 1113 OFFL 0 R/W-AS L1 0 0 ** 00D4 14 OFFLIN 1113 OFFL 0 R/W-SY L1 0 ** END OF DISPLAY

Example 4 The following example displays the status of individual Symmetrix volumes for Cascaded SRDF R21 devices:

EMCMN00I SRDF-HC : (91) &SQ VOL,C400,5,2A80 EMCQV00I SRDF-HC DISPLAY FOR (91) &SQ VOL,C400,5,2A80 021 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 2A80 3D00 B0 OFFLIN 1113 N/A 0 CAS-AD L1 0 7 99 0020 F9 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 2A81 3D01 B0 OFFLIN 1113 N/A 0 CAS-AD L1 0 0 ** 0021 F9 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 2A82 3D02 B0 OFFLIN 1113 N/A 0 CAS-AD L1 0 0 ** 0022 F9 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 2A83 3D03 B0 OFFLIN 1113 N/A 0 CAS-AD L1 0 0 ** 0023 F9 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 2A84 3D04 B0 OFFLIN 1113 N/A 0 CAS-AD L1 0 0 ** 0024 F9 OFFLIN 1113 N/A 0 N/R L2 0 ** END OF DISPLAY

Example 5 The following example displays the status of individual Symmetrix volumes for Cascaded SRDF R22 devices:

EMCQV00I SRDF-HC DISPLAY FOR (4) &SQ VOL,RMT(5100,84),5,130 730 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0130 03C0 40 OFFLIN 1113 N/A 0 N/R L2 0 0 ** 0100 84 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 0131 03C1 40 OFFLIN 1113 N/A 0 N/R L2 0 0 ** 0101 84 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 0132 03C2 40 OFFLIN 1113 N/A 0 N/R L2 0 0 ** 0102 84 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 0133 03C3 40 OFFLIN 1113 N/A 0 N/R L2 0 0 ** 0103 84 OFFLIN 1113 N/A 0 N/R L2 0 ** ???? ?? 0134 03C4 40 OFFLIN 1113 N/A 0 N/R L2 0 0 ** 0104 84 OFFLIN 1113 N/A 0 N/R L2 0 ** END OF DISPLAY

#SQ VOL 293

Command Reference

The fields in the previous examples have the following meanings:

◆ DV_ADDR SYS

z/OS device number. If the device was in the SCF exclude list, "????" appears in this field.

◆ DV_ADDR CH

First device address on the channel, in hex, as specified in the IOCP gen. For devices not online during startup and devices varied online after the last #SC GLOBAL,SSID_REFRESH command, “??” appears in this field.

◆ SYM_DEV


◆ SYM_RDEV


◆ SYM_GP

RDF group number.

◆ VOLSER

Device volume serial. If the device was online at EMCRDF startup or during an #SC GLOBAL,SSID_REFRESH command, the volume serial is from the UCB; otherwise, it is the volume serial assigned to the device when the Symmetrix system was installed, or the value set in the INIT_VOLSER parameter in the initialization parameters.

If the device is identified as a Fixed Block Architecture (FBA) device, it appears as follows:




• *F64M* denotes FBA meta head devices on all Symmetrix models with Enginuity level higher than 5771.


Command Reference

◆ TOTAL CYLS

Total number of cylinders on a volume.

Note: When the cylinder count exceeds 99999, the count will display in kilobytes (1K = 1024).

◆ SYS STATUS

z/OS device status. Values that may appear are:

◆ DCB OPN

Number of open DCBs.

NOSC No subchannel for device

HTIO Device is in hot I/O status

PAPV Pending offline, allocated, mounted private

PAPB Pending offline, allocated, mounted public

PAST Pending offline, allocated, mounted storage

OFFL Device offline to z/OS

ONPV Online, mounted private

ONPB Online, mounted public

ONST Online, mounted storage

OAPV Online allocated, mounted private

OAPB Online allocated, mounted public

OAST Online allocated, mounted storage

N/A UCB was not available

#SQ VOL 295

Command Reference

◆ CNTLUNIT STATUS Control Unit status, in format xxx-yy-z. Table 9 lists values that may appear.

a. This status indicates a status of RDF_NOT_READY (RNR). When a device is in this state, any attempt to perform I/O to the device from the host results in an INTERVENTION_REQUIRED status. The RNR status can occur as a result of the Domino Attribute, Invalid Tracks Attribute, or as a result of an #SC VOL,cuu,RDF_NRDY command.

b. Appendix C, “Director and Volume Status,” presents more information about this field.

c. This status indicates that communication between the SRDF pair is currently inactive because the SRDF pair is SRDF-Suspended.

d. If the source (R1) and target (R2) volumes are write enabled and links are not suspended, any writes to the source (R1) volume suspends the link between that pair. These writes accumulate as R2 invalid tracks on the source (R1) volume until the target (R2) volume is write enabled. Synchronization can then occur by issuing the #SC VOL,cuu,RDF_WR_ENABLE command.

Table 9 SQ VOL display CNTLUNIT STATUS values

Format Possible values

xxx AS = asynchronous modeR/W = read/write modeR/O = read only modeN/R = not ready modeCAS = cascading modeIL = inactive link in an R22 environmentRNR = SRDF devices globally not readya,b

TNR = target (R2) not readyb,c

RWD = SRDF write-disabledb,d

LNR = link not readye

UNR = USR not ready

yy AS = Asynchronous modeAX = Asychronous mode with CEXMPTSY = Synchronous modeSX = Synchronous mode with CEXMPTSS = Semi-Synchronous modef

AW = Adaptive Copy - Write Pending modeAD = Adaptive Copy - Disk mode

z I = Invalid Track Attribute: The target (R2) volume will go not ready if the source (R1) volume (its mirrored device) has invalid tracks on the target (R2) volume and a state of change has been requested on the target (R2) volumeD = Domino Attribute: The source (R1) volume will go not ready if the target (R2) volume is not ready or links are downR = Refresh command has been issued for this device.P = A PREFRESH command has been issued for this device.

V = A VALIDATE command has been issued for this device.


Command Reference

e. This status indicates that communication between the SRDF pair is currently inactive because the link is offline or the link path is physically unavailable.

f. Semi-synchronous mode is not supported on Symmetrix DMX-3 models or on any Symmetrix model with FICON directors.

Table 10 indicates the returned CNTLUNIT STATUS values for FBA meta devices when the state of the meta head does not match the state of the meta members.

Table 10 CNTLUNIT STATUS values for FBA meta mismatches (page 1 of 2)

Format Head status Not all members Some members

xxx

??0 N/R N/R

??1 NOT N/R N/R

??2 RNR RNR

??3 NOT RNR RNR

??4 UNR UNR

??5 NOT UNR UNR

??6 LNR LNR

??7 NOT LNR LNR

??8 TNR TNR

??9 NOT TNR TNR

??A RWD RWD

??B NOT RWD RWD

??C R/W R/W

??D NOT R/W R/W

??E R/O R/O

??F NOT R/O R/O

yy

?0 SRDF/A SRDF/A

?1 NOT SRDF/A SRDF/A

?2 ADCOPY_DISK ADCOPY_DISK

?3 NOT ADCOPY_DISK ADCOPY_DISK

?4 ADCOPY ADCOPY

?5 NOT ADCOPY ADCOPY

?6 SYNC SYNC

?7 NOT SYNC SYNC

#SQ VOL 297

Command Reference

◆ MR

Type of Symmetrix device. Values that may appear, and their meanings, are:

?8 SEMI-SYNC SEMI-SYNC

?0 NOT SEMI-SYNC SEMI-SYNC

z

?0 PREFRESH PREFRESH

?1 NOT PREFRESH PREFRESH

?2 REFRESH REFRESH

?3 NOT REFRESH REFRESH

?4 VALIDATE VALIDATE

?5 NOT VALIDATE VALIDATE

?6 INVALIDATE INVALIDATE

?7 NOT INVALIDATE INVALIDATE

?8 DOMINO DOMINO

?0 NOT DOMINO DOMINO

Table 10 CNTLUNIT STATUS values for FBA meta mismatches (page 2 of 2)

Format Head status Not all members Some members

blank Denotes a standard, local, non-mirrored device

A1 Asynchronous R1

A2 Asynchronous R2

AS Asynchronous SRDF/A volume

B1 Business continuance volume source (R1)

B2 Business continuance volume target (R2)

BC Business continuance volume (BCV)

D1 Diskless R1 (transient state)

D2 Diskless R2 (transient state)

D21 Diskless cascaded device

DL Diskless device that has not been paired with a remote partner

DR Dynamic reallocation volume (used by the Optimizer)

FS File system volume

L1 Source (R1) volume that is also mirrored locally

L2 Target (R2) volume that is also mirrored locally

ML Local mirror volume


Command Reference

◆ R1 INVTRK

Source (R1) volume invalid track count. The numbers reported are displayed as K or M as appropriate, where 1K = 1024 and 1M = 1000*1024.

Note: Symmetrix systems maintain their own invalid track tables that identify invalid tracks on both the source (R1) and target (R2) volumes.

◆ R2 INVTRK Target (R2) volume invalid track count.

Note: Symmetrix systems maintain invalid track tables that identify invalid tracks on both the source (R1) and target (R2) volumes. The number of R2 invalid tracks displayed for an R2 volume indicates the number of tracks that the source Symmetrix has accumulated to be sent to the target Symmetrix, as a result of adaptive copy mode or when the R1 source volumes have been updated while SRDF is suspended (TNR status). This value provides an indication of how “out of sync” the R1 and R2 volumes are when entering a recovery situation. The actual physical mirror invalid tracks can be displayed with the #SQ MIRROR command.

◆ SY% Source (R1)/target (R2) volume synchronization percentage. ** denotes 100% synchronization.

P Volume protected locally. Displays for any non-RDF RAID-S, RAID 5, or RAID 6 device. (Does not apply to RAID 10 devices.)

PV PowerVault volume

R1 Source (R1) volume

R2 Target (R2) volume

RS RAID-S volume

#SC CNFG 299

Command Reference

#SC CNFGThe #SC CNFG command sets the operating state for one entire Symmetrix system.

Syntax

Parameters action

Table 11 on page 300 describes this parameter.

cqname


cuu


G(groupname)


queue-option


value

SYNCH_DIRECTION represents the desired synchronization direction for recovery procedures.

Note: SYNCH_DIRECTION set at the CNFG level does not change the SYNCH_DIRECTION set at the RDF group level. Attempting to do so results in an EMCCC30W warning message.

#SC CNFG

,action,value

,cuu

,G(groupname)

,SCFG(scfgroupname)

1

1

,CQNAME= cqname



Command Reference

Comments Table 11 lists the possible actions for the #SC CNFG command.

Example The following command example sets the synchronization direction to NONE, so synchronization direction commands cannot be issued.

#SC CNFG,cuu,SYNCH_DIRECTION,NONE

Table 11 #SC CNFG command actions for SRDF

Action Values Description

SYNCH_DIRECTION R1>R2, R1<R2, NONE, or GLOBAL Set synchronization direction for an individual Symmetrix system. A setting of GLOBAL causes the global synch_direction value to be used for this Symmetrix system. “#SC GLOBAL” on page 301 presents further information about each setting.

#SC GLOBAL 301

Command Reference

#SC GLOBALThe #SC GLOBAL command sets the operating state for overall function of the SRDF Host Component subsystem. For example, this command, when used with the SSID_REFRESH parameter, causes SRDF Host Component to “refresh” its internal control blocks with information regarding any SSIDs, devices, and VOLSERs that have been brought online since SRDF Host Component was started or the last refresh command was issued. This command may also be used to reset the current SYNCH_DIRECTION, to change how FBA devices are affected by the #SC VOL command, and to specify the sort order for various query commands.

Syntax

Parameters action


PARM_REFRESH

When issued, Host Component rereads the initialization parameter file, and does the following:

a. Makes any necessary changes to the following parameters:

– ALIAS– ALLOW_CG_OVERRIDE– ALLOW_CRPAIR_NOCOPY– EXCLUDE_DEVICE_RANGE– SINGLE CONCURRENT

#SC GLOBAL ,action

,PARM_REFRESH

,SSID_REFRESH

1

1

,SWAPLOG

,value


Command Reference

– SRDF GROUP statements:

– MAX_QUERY– MAX_COMMANDQ– MSC statements:

– VONOFF statements:

– SHOW_COMMAND_SEQ#– OPERATOR_VERIFY– SYNCH_DIRECTION_ALLOWED– MESSAGE_LABELS

b. Deletes the SSID tables.

c. Performs an SSID_REFRESH.

Changing MSC parameters — Once MSC is running (as noted by the “time of cycle switch” messages in the ResourcePak Base job log), the specified parameters will remain in effect until an MSC,REFRESH or MSC,DISABLE command is issued. The #SC GLOBAL,PARM_REFRESH command will not post any new parameters to be run.

SSID_REFRESH

Refreshes SRDF Host Component internal control blocks with the latest information on SSIDs, devices, and VOLSERs.

Note: The cqname parameter is not valid with this parameter.

GROUP_NAME FILTER_ONLINEGROUP_END FILTER_R1EXCLUDE_CUU FILTER_R2EXCLUDE_SYM INCLUDE_CUUEXCLUDE_VOL INCLUDE_RAGFILTER_KNOWN INCLUDE_VOL

MSC_INCONSISTENT MSC_INCLUDE_SESSIONMSC_CYCLE_TARGET MSC_STARMSC_GROUP_END MSC_VALIDATIONMSC_GROUP_NAME

VONOFF_BLOCKED VONOFF_R1_ONLYVONOFF_OFF_ONLY VONOFF_R2_ONLYVONOFF_ON_ONLY VONOFF_STATUS_WAIT

#SC GLOBAL 303

Command Reference

SWAPLOG

Closes the current log file and opens the alternate log file. DDnames for the log files are HCLOG1 and HCLOG2.

Note: The cqname parameter is not valid with this parameter.

Comments Table 12 lists the possible actions for the #SC GLOBAL command.

Table 12 #SC GLOBAL command actions for SRDF (page 1 of 2)


FBA_DISABLE N/A Disables the #SC VOL command from being used to change operating parameters for FBA devices.

FBA_ENABLE N/A Allows the #SC VOL command to be used to change the operating parameters for FBA devices.

SORT_BY_COMMAND N/A The display sort order is determined by the type of query request as follows:

Command#SQ VOL,cuu #SQ VOL,LCL(cuu) #SQ VOL,RMT(cuu)

#SQ VOL,V(volser) #SQ VOL,SSID(ssid) #SQ VOL,G(groupname)

Displays output according to

MVSCUUSYMDEVSYMDEV

VOLSERSYMDEVRefer to the following descriptions for SORT_BY_VOLSER and SORT_BY_MVSCUU

SORT_BY_MVSCUU N/A Show devices in the order of their MVS device addresses when presenting displays resulting from #SQ VOL, #SQ STATE, #SQ RAID, #SQ MIRROR, #SQ RAID5, and #SQ RAID10 commands. Devices appear at the end in Symmetrix device number order.

SORT_BY_SYMDEV N/A Show devices in the order of Symmetrix device number when presenting displays resulting from #SQ VOL, #SQ STATE, #SQ RAID, #SQ MIRROR, #SQ RAID5, and #SQ RAID10 commands.

SORT_BY_VOLSER N/A Show devices in the order of volume serial when presenting displays resulting from #SQ VOL, #SQ STATE, #SQ RAID, #SQ MIRROR, #SQ RAID5, and #SQ RAID10 commands. Devices without a volume serial appear at the end of the display, presented in Symmetrix device number order.


Command Reference

Devices that have been taken offline are not deleted from the SRDF Host Component internal control blocks during refresh processing. This condition allows SRDF Host Component to maintain the z/OS device number to Symmetrix device number mapping to simplify the entry of #SC VOL commands.

SYNCH_DIRECTION R1>R2, R1<R2, NONE Sets current synchronization direction. Values that may appear, and their meanings, are subject to restrictions set by the SYNCH_DIRECTION_ALLOWED initialization parameter. • R1>R2 only allows synchronization commands (REFRESH,

RNG_REFRESH, VALIDATE, and INVALIDATE) to cause synchronization from source (R1)→target (R2). The REFRESH, RNG_REFRESH, and VALIDATE actions on the #SC VOL command may only be used on a target (R2) volume and INVALIDATE may only be used on a source (R1) volume.

• R1<R2 only allows synchronization commands (REFRESH, RNG_REFRESH, VALIDATE, and INVALIDATE) to cause synchronization from target (R2)→source (R1). The REFRESH, RNG_REFRESH, and VALIDATE actions on the #SC VOL command may only be used on a source (R1) volume and INVALIDATE may only be used on a target (R2) volume.

• NONE specifies no synchronization direction.

Note: This parameter identifies the intended resynchronization command sequence so that Host Component can validate the sequence. This parameter has no effect on Symmetrix systems.

Table 12 #SC GLOBAL command actions for SRDF (page 2 of 2)


#SC LINK 305

Command Reference

#SC LINKThe #SC LINK command modifies the status of a remote link director.

Syntax

Parameters cqname


cuu


dir#

Specifies the remote link director number. Values that may appear are from 1 to 80 (hex) or ALL.

queue-option


state

Specifies the states of the specified remote link director(s). Values that may appear are OFFLINE and ONLINE.

Comments The director number specified must be a remote link director. If necessary, issue the #SQ LINK command to determine the remote link director numbers.

When ALL is specified as the dir# parameter value, the requested status change is applied to all remote link directors.

When OFFLINE is specified as the state parameter value, any SRDF/A session will drop, even if Transmit Idle is enabled.

#SC LINK ,cuu

,ALL

1,directornumber

,state1

,CQNAME= cqname



Command Reference

#SC MSGThe #SC MSG command, when used with the RESET parameter, clears the message log.

Syntax

Parameters cqname


queue-option


RESET

Clears the message log of all entries.

Comments None.

#SC MSG ,RESET

,CQNAME= cqname


#SC RDFGRP 307

Command Reference

#SC RDFGRPThe #SC RDFGRP command modifies the state of an RDF group.

Note: All #SC RDFGRP commands require you to confirm the action you have specified, unless this has been disabled by specifying the value NO for the OPERATOR_VERIFY initialization parameter.

Syntax

Parameters action


cqname


cuu


mhlist


queue-option


, cuu

,RMT( rdfcuu#)

,RMT( cuu,mhlist )

1


1 2

2

#SC RDFGRP

,action

,CQNAME= cqname


,value ,rdfgroup#


Command Reference

rdfcuu


rdfgroup#


RMT


Table 13 lists the possible actions for the #SC RDFGRP command.

a. action, if present, specifies whether a director is added to the RDF group. For the ADD, action can only be missing or “+”. For the MODIFY action, the value may be missing or “+” to add a director to the group or “-” to remove.

b. directorlist specifies the director number in hex in the range of x’01’ through x’80’ to be added or removed from the local (LDIR) or remote (RDIR) group.

Table 13 #SC RDFGRP command actions for SRDF


ADD[(][DOM][,NO-AUTO-RCVRY][)]

LDIR([actiona]directorlistb)

RDIR([action]directorlist)[,LABEL(label)RGRP(group#)

RSER(symmserial#)

Optionally, sets the Links Domino and/or Prevent Auto Links Recovery options for the RDF group. LDIR and RDIR identify the local/remote directors, and RSER specifies the full 12-digit remote serial number. RGRP supplies the RDF group number for the remote side.

Note: The maximum RDF group number on either side is based on the Enginuity level of the Symmetrix software. The maximum RDF group number that can participate in the RDF configuration is the lower of the maximum numbers on both sides. Review the Symmetrix documentation for the RDF group ranges supported.

During normal SRDF operations, when all links between an R1 and R2 go down, the devices go not ready on the link (TNR / LNR). When the links come back up, the devices automatically recover back to a "Ready on the link" state (R/W). With NO-AUTO-RCVRY set, when the link comes back up, the devices will stay TNR until the user explicitly RDF_RSUMs the devices. This provides protection to preserve consistency.

DELETE Deletes the identified RDF group.

MODIFY LDIR([action]directorlist)RDIR([action]directorlist)

Adds or removes the directors identified in the LDIR or RDIR parameter from the identified RDF group.

SYNCH_DIRECTION R1>R2, R1<R2, NONE, or CNFG Sets synchronization direction for an individual RDF group. A setting of CNFG causes the config synch_direction value to be used for this RDF group. “#SC CNFG” on page 299 presents further information about each setting.

#SC RDFGRP 309

Command Reference

Comments Creating and adding dynamic RDF groups

Beginning with Enginuity level 5669, support is added for dynamic RDF groups. This Enginuity feature allows you to add RDF groups dynamically, and to modify and delete dynamic groups.

A group is defined with a group number (x’00’ - x’3F’ for Enginuity level 5771 and lower; x’00’ - x'F9' for level 5772 and higher) and a list of directors for each side of the SRDF relationship. In addition, you can set options at group creation time to enable the Links Domino and Prevent Auto Links Recovery attributes. When dynamic groups are added, you can assign 10-character alphanumeric labels to them. You can also assign labels to static groups as part of the Symmetrix configuration activity.

Once a dynamic group is defined, devices may be added or removed using the #SC VOL command CREATEPAIR and DELETEPAIR actions. Definitions for dynamic groups are persistent across IMLs.

The following restrictions apply to adding and creating RDF groups:

◆ Only GigE and switched Fibre Channel directors are supported.

◆ Point-to-point Fibre Channel configurations are not supported.

◆ PPRC is supported for dynamic RDF groups.

◆ ESCON directors are not supported.

◆ Dynamic RDF group operations applied to static groups are not supported.

◆ When an RDF group is initially created, it is assigned a unique label that is applied to both sides of the group. Note that this label must not already exist as a label on either side before the group is created. A label name of RDFDVGROUP is not allowed for dynamic groups. RDFDVGROUP is the default label assigned to static groups if a label is not explicitly specified.

◆ Each group must be empty and all pairs deleted before it can be deleted.

◆ At least one physical link must be present before a group can be added.

◆ #SC RDFGRP MODIFY actions can only add or remove directors, not change option settings or labels. These actions cannot delete all directors from the group on one side while leaving one or more directors on the other side.

◆ Only one dynamic group operation is allowed at a time.


Command Reference

◆ Dynamic group operations are not allowed during IML.

◆ Each Fibre Channel director can have a maximum of 64 connections for Enginuity level 5772 or higher. For example:

In this case, each group that was added generates four connections on each director because each source director makes a connection to each of the target directors:

1 group = 4 connections2 groups = 8 connections3 groups = 12 connections4 groups = 16 connections

This can be adjusted by setting each group to use only two of the directors, allowing fewer connections per group.

Examples #SC RDFGRP,3004,04,SYNCH_DIRECTION,R1>R2

Sets the synchronization direction to R1>R2 in both Symmetrix systems for RDF group 04. Figure 25 on page 311 provides more information.

#SC RDFGRP,3004,04,SYNCH_DIRECTION,R1<R2

Sets the synchronization direction to R1<R2 in both Symmetrix systems for RDF group 04. Figure 25 on page 311 provides more information.

#SC RDFGRP,3004,04,SYNCH_DIRECTION,NONE

Sets the synchronization direction to NONE in both Symmetrix systems for RDF group 04. Figure 25 on page 311 provides more information.

#SC RDFGRP,3004,04,SYNCH_DIRECTION,CNFG

Sets the synchronization direction to use Control Unit level synchronization direction in both Symmetrix systems for RDF group 04. Figure 26 on page 312 provides more information.

Source Box Target Box

4 RDF directors 4 Fibre Channel directors

#SC RDFGRP 311

Command Reference

Note: The default SYNCH_DIRECTION for RDF groups not explicitly set by the #SC RDFGRP command is either the control unit’s synchronization direction (if previously set via an #SC CNFG command) or, if absent, the GLOBAL synchronization direction. The two Symmetrix systems in an SRDF relationship may have the control unit level set differently.

Related RDF groups (that is, RDF groups created via the same #SC RDFGRP ADD action) always have the same synchronization direction.

Figure 25 #SQ RDFGRP command output for SRDF

EMCQR00I SRDF-HC DISPLAY FOR (6) #SQ RDFGRP,3004 MY SERIAL # MY MICROCODE ------------ ------------ 000184501175 5567-37 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR ------ --- -- ------ ------------ ------------ -------- 00 Y F 00 000184500399 5567-37 R1>R2

01 Y F 01 000184500399 5567-37 G(NONE) 02 Y F 02 000184500399 5567-37 R1<R2 03 Y F 03 000184500399 5567-37 G(NONE) 04 Y E 04 000184500399 5567-37 G(NONE) 05 Y E 05 000184500399 5567-37 G(NONE) 06 Y E 09 000184500399 5567-37 G(NONE) 07 Y E 08 000184500399 5567-37 G(NONE) 08 Y E 07 000184500399 5567-37 G(NONE) 09 Y E 06 000184500399 5567-37 G(NONE)

END OF DISPLAY

Set at RDFGRP level(both Symmetrix systems)R1>R2

Set at Global asSynch Direction of None. That is, RDFGRP SYNC of CNFG and CNFG Synch of Global

Set at RDFGRP level(both Symmetrix systems)R1<R2


Command Reference

Figure 26 #SQ RDFGRP command output for SRDF

When issuing range commands that have devices synchronizing in opposite directions, the messages shown on the following page appear:

EMCQR00I SRDF-HC DISPLAY FOR (8) #SQ RDFGRP,3404 MY SERIAL # MY MICROCODE ------------ ------------ 000184500399 5567-37 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR ------ --- -- ------ ------------ ------------ -------- 00 Y F 00 000184501175 5567-37 R1>R2 01 Y F 01 000184501175 5567-37 C(R1<R2) 02 Y F 02 000184501175 5567-37 R1<R2 03 Y F 03 000184501175 5567-37 C(R1<R2) 04 Y E 04 000184501175 5567-37 C(R1<R2) 05 Y E 05 000184501175 5567-37 C(R1<R2) 06 Y E 09 000184501175 5567-37 C(R1<R2) 07 Y E 08 000184501175 5567-37 C(R1<R2) 08 Y E 07 000184501175 5567-37 C(R1<R2) 09 Y E 06 000184501175 5567-37 C(R1<R2) END OF DISPLAY

Set at Control Unit levelR1<R2

#SC RDFGRP 313

Command Reference

Any REFRESH, RNG_REFRESH, VALIDATE, or INVALIDATE command that would select both R1 and R2 devices because the synch directions are set differently generates the EMCCVF8I, EMCCVF9I, and/or EMCCVFAI messages, as appropriate.

If OPERATOR VERIFY is set to CRITICAL, an EMCCVFBR message is issued.

EMCMN00I SRDF-HC : (9) ¢¢SQ RDFGRP,3004 EMCQR00I SRDF-HC DISPLAY FOR (9) ¢¢SQ RDFGRP,3004 MY SERIAL # MY MICROCODE ------------ ------------ 000184501175 5567-37 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR ------ --- -- ------ ------------ ------------ -------- 00 Y F 00 000184500399 5567-37 R1>R2 01 Y F 01 000184500399 5567-37 G(NONE) 02 Y F 02 000184500399 5567-37 R1<R2 03 Y F 03 000184500399 5567-37 G(NONE) 04 Y E 04 000184500399 5567-37 G(NONE) 05 Y E 05 000184500399 5567-37 G(NONE) 06 Y E 09 000184500399 5567-37 G(NONE) 07 Y E 08 000184500399 5567-37 G(NONE) 08 Y E 07 000184500399 5567-37 G(NONE) 09 Y E 06 000184500399 5567-37 G(NONE) END OF DISPLAY

EMCMN00I SRDF-HC : (10) ¢¢SC VOL,3004,REFRESH,ALL EMCCVF8I DEVICE(S) EXCLUDED WITH SYNC DIRECTION OF NONE 0040-0083,0088-008F,0095,0098-01BF,0200-027F,02C0-033F EMCCVF9I DEVICE(S) CHOOSEN WITH SYNC DIRECTION OF R1>R2 0280-02BF EMCCVFAI DEVICE(S) CHOOSEN WITH SYNC DIRECTION OF R1<R2 0340-037F *89 EMCCVFBR RANGE W/ DIFFERENT SYNC DIRECTIONS, REPLY CONTINUE TO PROCEED OR CANCEL TO TERMINATE


Command Reference

#SC RDFGRP,6F60,12,ADD(DOM,NO-AUTO-RCVRY),LDIR(1-3,5),RDIR(2-4,8),LABEL(TEST),RSER(771877900065),RGRP(21)

This command adds RDF group 12 on the local Symmetrix system and RDF group 21 on the remote Symmetrix system as related RDF groups. (Each RDF group is the other-side RDF group of the other.) The options are set to add Domino mode to the group and prevent auto link recovery. The defaults for these options are no domino and allow auto link recovery. Local directors 1, 2, 3, and 5 are included in the group as well as remote directors 2, 3, 4, and 8. All director # specifications are in hex. The Label “TEST” is assigned to this group, and RSER specifies the full 12-digit remote serial number.

#SC RDFGRP,6F60,08,MODIFY,LDIR(-1,+2-3),RDIR(-1,+2-3)

This command modifies RDF group 08 and its other-side RDF group. It removes director 1 from and adds directors 2 and 3 to the local side, and it removes director 1 from and adds directors 2 and 3 to the remote side. A director number prefixed by ’-’ indicates that the director is to be removed while a director number prefixed by a ’+’ indicates that the director is to be added. When this form of director list is used, each item in the list must be prefixed by a ’+’ or ’-’.

#SC RDFGRP,6F60,08,MODIFY,LDIR(1-3,5),RDIR(2-4,B)

This command modifies RDF group 08 and its other-side RDF group, and specifies the full list of directors for each side.

#SC RDFGRP,6F60,08,DELETE

This command deletes RDF group 08. The group must be empty for this command to work. In other words, all device pairs must have been deleted from RDF group 08.

#SC RECOVER 315

Command Reference

#SC RECOVERThe #SC RECOVER command initiates SRDF Automated Recovery for MSC or non-MSC environments.

Note: “Restrictions” on page 475 lists operating restrictions for this release of SRDF Automated Recovery.

Syntax

Parameters MSC

Specifies that the recovery operation is for an MSC environment.

group_name

The name of the group. The group_name can be from 1 through 24 alphanumeric or national (@#$) characters. The group_name must be contiguous and cannot contain blanks in the definition.

NOBCV

Disables BCV management for this recovery event only.

SRDFA

Specifies that the recovery operation is for a non-MSC SRDF/A environment.

cuu

The z/OS device number.

rdfgroup#

The RDF group number through which you want to perform an operation. This must be a 1- or 2-digit (hex) value representing the RDF group number.

#SC RECOVER

,MSC(group_name){,NOBCV}

,SRDFA(cuu,#rdfgroup)


Command Reference

#SC SRDFAThe #SC SRDFA command sets SRDF/A configuration options.

Syntax

Note: The #SC SRDFA,cuu,action format works only with Enginuity level 5x70, which allows only one SRDF/A group. With Enginuity level 5x71 and later, multiple SRDF/A sessions may be active simultaneously, each on a different RDF group, and you should specify the LCL(cuu,rdfgroup#) format. (For some actions, you may use the RMT(cuu,mhlist,rdfgroup#) format.)

Parameters cqname


cuu


LCL


queue-option


RMT


, cuu


,RMT( cuu,mhlist )

1


1 2

2

#SC SRDFA

,action,

,CQNAME= cqname


#SC SRDFA 317

Command Reference

Table 14 lists #SC SRDFA command actions for SRDF/A mode.

Table 14 #SC SRDFA command actions for SRDF/A mode (page 1 of 3)

Action Description Requirements

ACT Activates the SRDF/A session. The SRDF/A session must not be active.All primary devices must be ready on the link.

CONS_DEACT Changes an SRDF/A RDF group from SRDF/A active mode to SRDF/S mode while maintaining consistency. Note that this is a long running command and it requires several cycle switches before it is complete.

The SRDF/A session must be active.This command will be rejected if the RDF group is in an active MSC group.This command will be rejected if the RDF group includes cascaded devices (R21s).

Requires Enginuity level 5x71 or higher.

DEACT_TO_ADCOPY Takes an SRDF/A RDF group from SRDF/A active to ADCOPY. Note that this is equivalent to a PEND_DEACT followed by internally setting the devices to ADCOPY. If the SRDF/A session primary side includes cascaded devices (R21s) that are not diskless, the action will be forced to DEACT_TO_ADCOPY_DISK.

The SRDF/A session must be active.This command will be rejected if the RDF group is in an active MSC group.Requires Enginuity level 5x71 or higher.

DEACT_TO_ADCOPY_DISK Takes an SRDF/A RDF group from SRDF/A active to ADCOPY_DISK. Note that this is equivalent to a PEND_DEACT followed by internally setting the devices to ADCOPY_DISK.If the SRDF/A session primary side includes cascaded devices (R21s) that are diskless, the action will be forced to DEACT_TO_ADCOPY.

The SRDF/A session must be active.This command will be rejected if the RDF group is in an active MSC group.


DROP Deactivates the SRDF/A session and makes all devices TNR. The primary side may have R2 invalid tracks. The secondary side may have R1 invalid tracks. A consistent copy is on the secondary side.

Issuing this command to a RDF group running in an active MSC group will cause MSC to DROP all SRDF/A sessions in the MSC group.

The SRDF/A session must be active.

DROP_SIDE If SRDF/A is in the Transmit Idle state, the DROP action will not work because Transmit Idle requires that both sides of the SRDF/A relationship be available on the link. If the DROP state is required, then this DROP_SIDE action can be used.


Command Reference

PEND_DEACT Waits until the end of the SRDF/A cycle, and then deactivates the SRDF/A session, but leaves all devices Ready on the link. The secondary side cannot be considered consistent.If the SRDF/A session primary side includes cascaded devices (R21s), the action will be forced to DEACT_TO_ADCOPY if the R21s are diskless and to DEACT_TO_ADCOPY_DISK if not.

The SRDF/A session must be active.This command will be rejected if the RDF group is in an active MSC group.

PEND_DROP Waits until the end of the SRDF/A cycle and then performs a DROP. Upon completion, the primary side may have R2 invalid tracks. The secondary side does not have R1 invalid tracks. A consistent copy is on the secondary side.

SRDF/A session must be active.

Must be issued to the primary side.This command will be rejected if the RDF group is in an active MSC group.

SET_CACHE_LIMIT,VVV Where 0 ≤ VVV ≤ 100Sets the cache limit. The cache limit is a Symmetrix-level setting that applies to all RDF groups on the target Symmetrix system. The value is the percentage of write pending space that SRDF/A can use before the Symmetrix will start dropping SRDF/A groups


SET_DROP_PRIORITY,VV Where 1 ≤ VV ≤ 64 Setting the Drop Priority is an RDF group-specific change. You can set the Drop Priority differently on the R1 side as compared to the R2 side. The priority within the Symmetrix is what matters. The highest priority allowed is 1 and the lowest is 64.


SET_HOST_THROTTLE,VVVVV Where 0 ≤ VVVVV ≤ 65535Sets the I/O delay for writes to SRDF/A devices when cache resources for SRDF/A exceed preset limits.Note that setting a non-zero value for Host Throttle will cause the Cache Usage and Drop Priority to be not used. The Host Throttle is a Symmetrix-level setting that applies to all RDF groups in the Symmetrix system.




#SC SRDFA 319

Command Reference

a. For the initial release of Enginuity level 5772, the default setting for Transmit Idle is OFF. For Enginuity level 5772.52 and later, the default setting for Transmit Idle is ON.

b. If issued to only one side and the RDF link cannot transmit data, then the side that does not have Transmit Idle set will appear to drop and the side that has Transmit Idle set will display in the idle state. In an MSC or SRDF/Star environment, if this condition is met, then the MSC/STAR transmission will also drop.

SET_MIN_CYCLE_TIME,VV Where 1 ≤ VV ≤ 59Setting the Minimum Cycle Time is specific to RDF groups. Setting this value does not impact MSC. MSC uses the cycle time specified in the MSC_CYCLE_TARGET.

This action requires Enginuity level 5x71 or higher.

Note: Minimum cycle times less than 5 are valid only if both the remote and local Symmetrix systems for the RDF group are at Enginuity level 5773 or higher.

TOL_ON Turns Tolerance mode on. When Tolerance mode is on and when SRDF/A is active, the following events do not cause SRDF/A to drop:• an R2 device in the SRDF/A group is made

R/W• an R1 in the SRDF/A group is made TNR• devices in the SRDF/A group are removed

from the SRDF/A group and made standard volumes (by issuing DELETEPAIR)

Must be issued to the primary side.This action will be rejected if the RDF group is in an active MSC group.

TOL_OFF Turns Tolerance mode off. When Tolerance mode is off, the following events cause SRDF/A to drop: • an R2 in the SRDF/A group is made R/W• an R1 in the SRDF/A group is made TNR

Must be issued to the primary side.All Primary devices must be ready on the link.

TRANSMIT_IDLE,[ON|OFF a] Turns the Transmit Idle state on or off. The default is off and the setting is persistent. That is, the setting is retained even if SRDF/A is deactivated; when SRDF/A is reactivated, the setting will apply to the newly-activated SRDF/A session.

Transmit Idle is enabled at the RDF group level and can be set in advance of SRDF/A activation.

No ESCON RA support.Must be issued to both the primary and the secondary sides of the RDF group. b




Command Reference

#SC SRDFA_DSEThe #SC SRDFA_DSE command is used to activate, deactivate, and auto-activate the SRFA/A Delta Set Extension feature and to associate pools with an SRDF/A session. It can also be used to set the cache threshold value that will trigger the start of SRDF/A Delta Set Extension. This command requires Enginuity level 5772 or higher.

Note: “SRDF/A Delta Set Extension” on page 43 provides a detailed description of this feature.

Syntax

Parameters action


cqname


cuu


, LCL(cuu,rdfgroup#)

,RMT( rdf cuu )

,RMT( cuu,mhlist )

1


1 2

2

#SC SRDFA_DSE

,action,

,poolgeometry

P( poolname )

,CQNAME= cqname


#SC SRDFA_DSE 321

Command Reference

LCL


poolgeometry

Table 15 lists the possible values (A400, 3380, 3390, FBA) for this parameter.

queue-option


rdfgroup#


RMT


Table 15 #SC SRDFA_DSE command actions for SRDF/A mode (page 1 of 3)


ACT Activate SRDF/A Delta Set Extension. This action applies only to the SRDF/A session active on the RDF group specified in the command.Example: #SC SRDFA_DSE,LCL(dddd,rdfgrp#),ACT

An SRDF/A session must be active for the RDF group specified in the command.At least one pool must be associated with the SRDF/A RDF group specified in the command.

DEACT Deactivate SRDF/A Delta Set Extension. This action applies only to the SRDF/A session active on the RDF group specified in the command.Example: #SC SRDFA_DSE,LCL(dddd,rdfgrp#),DEACT

An SRDF/A session must be active for the RDF group specified in the command.At least one pool must be associated with the SRDF/A RDF group specified in the command.SRDF/A Delta Set Extension must be active.

A400_POOL,P(POOLNM) Define the AS400 DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),A400_POOL,P(POOLNM)

Where POOLNM represents the name of the DSE pool to use.

The specified pool must be of emulation type FBA(520) and must be a DSE pool.


Command Reference

A400_POOL,P() Remove the AS400 DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.

Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),A400_POOL,P()

The specified pool must be of emulation type FBA(520) and must be a DSE pool.

3380_POOL,P(POOLNM) Define the 3380 DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),3380_POOL,P(POOLNM)

The specified pool must be of emulation type 3380 and must be a DSE pool.

3380_POOL,P() Remove the 3380 DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.

Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),3380_POOL,P()


3390_POOL,P(POOLNM) Define the 3390 DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.

Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),3390_POOL,P(POOLNM)


3390_POOL,P() Remove the 3390 DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.

Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),3390_POOL,P()


FBA_POOL,P(POOLNM) Define the FBA DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.

Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),FBA_POOL,P(POOLNM)

The specified pool must be of emulation type FBA and must be a DSE pool.

FBA_POOL,P() Remove the FBA DSE pool. This action applies only to the SRDF/A session active on the RDF group specified in the command.Example:#SC SRDFA_DSE,LCL(dddd,rdfgrp#),FBA_POOL,P()

The specified pool must be of emulation type FBA and must be a DSE pool.



#SC SRDFA_DSE 323

Command Reference

AUTO_ACT,ON Turn on auto-activate for Delta Set Extension. This action applies only to the SRDF/A session active on the RDF group specified in the command.

AUTO_ACT will automatically activate SRDF/A Delta Set Extension for the specified RDF group when SRDF/A is active. The default is OFF, but once set ON, it continues to apply even if SRDF/A drops and resumes.

Example: #SC SRDFA_DSE,LCL(dddd,rdfgrp#),AUTO_ACT,ON

The associated DSE pool must be in good working order.

AUTO_ACT,OFF Turn off auto-activate for Delta Set Extension. This action applies only to the SRDF/A session active on the RDF group specified in the command.

Example: #SC SRDFA_DSE,LCL(dddd,rdfgrp#),AUTO_ACT,OFF

The associated DSE pool must be in good working order.

THRESHOLD,xxx Change the cache threshold value to start SRDF/A Delta Set Extension. The default value is 50 (percent). Values that may appear are from 20 to 100. This command applies only to the SRDF/A session active on the RDF group specified in the command.

Note: The cache percentage is the percentage of total system cache or, if you are using cache partitioning, then it is the percentage of the cache partition containing the RDF group specified in the command.

Example: #SC SRDFA_DSE,LCL(dddd,rdfgrp#),THRESHOLD,30




Command Reference

#SC VOLThe #SC VOL command modifies the status of SRDF volumes. This command provides the ability to set the SRDF operational mode.

All #SC VOL commands require you to confirm the action you have specified, unless this has been disabled by specifying the value NO for the OPERATOR_VERIFY initialization parameter.

Note: Devices go through a filtering process before they are considered for #SC VOL command processing. Appendix A, “SC VOL Command Device Filtering,”describes this process.

Syntax

The #SC VOL command syntax continues on the next page.

#SC VOL

,cuu-cuu

,action,,cuu

,RMT(rdfcuu)

,SCFG(scfgroupname)

,G(groupname)

,VOL(volser) ,action

,LCL(cuu,rdfgroup#1,rdfgroup#2)

,RMT(cuu,mhlist)

,RMT(cuu,mhlist,rdfgroup#)

1

2

,LCL(cuu,rdfgroup#)

,RMT(cuu,mhlist,rdfgroup#1,rdfgroup#2)

#SC VOL 325

Command Reference

Parameters action


cqname


cuu


cuu-cuu

Specifies a range of z/OS device numbers where the first cuu is the starting z/OS device number and the second cuu is the ending z/OS device number of the range.

symdev#

Specifies a Symmetrix device number or a range of Symmetrix device numbers in the form of dev1-dev2 where dev1 is the starting Symmetrix device number and dev2 is the ending Symmetrix device number. If ALL is specified, all devices on the Symmetrix system that are eligible for the specified action are affected.

Note: If no dev1-dev2 parameter is specified, SRDF Host Component attempts to use the cuu range to determine the Symmetrix device number on which to perform the action. If you choose to specify a range of devices, you may specify either a range of z/OS device numbers or a range of Symmetrix device numbers, but not both.

2

,CQNAME= cqname


,symdev#-symdev#

,symdev#

,ALL

,value

1 2

,value


Command Reference

G(groupname)


LCL


mhlist


queue-option


rdfcuu


rdfgroup#


RMT


SCFG(scfgroupname)


value

If setting ADC_MAX, this value specifies the maximum skew value for the device(s) that are or will be placed in Adaptive Copy mode. This value can range from 1 to 65535 (decimal).

VOL(volser)


#SC VOL 327

Command Reference

Command actions Table 16 lists the possible #SC VOL actions.

Table 16 #SC VOL command actions (page 1 of 16)

Action

Valid volume typea Description

ADC_MAX R1/L1/B1 This action sets the Adaptive Copy maximum skew value for the volume(s).

Example: #SC VOL,F00,ADC_MAX,,80

The maximum skew value that may be specified must be a value from 1 to 65535. This action may only be specified for devices in one of the supported Adaptive Copy modes.

Note: Setting the skew value too high for devices in Adaptive Copy - Write Pending mode could result in excessive cache use, adversely affecting subsystem performance.

ADCOPY R1/L1/B1 This action enables the Adaptive Copy function for the source (R1) volume. When this attribute is enabled, the Symmetrix system acknowledges all writes to source (R1) volumes as if they were local volumes.Notes:• This setting is not retained and must be reset following an IML.• This action is not valid against volumes in a consistency group.• This action is not valid against cascaded non-diskless devices.

ADCOPY_DISK R1/L1/B1 This action places the specified volume(s) into Adaptive Copy Disk mode.

Notes:• This setting is not retained and must be reset following an IML.• This action is not valid against volumes in a consistency group.• This action is not valid against cascaded (R21) diskless devices.


Command Reference

CASCRE Dynamic SRDF devices

This action establishes a cascaded triplet relationship among three devices in the configurations R1↔R21↔R2. This action is implemented via a command using non-standard syntax in one of the following formats:#SC VOL,LCL(cuu, rdfgroup#1, rdfgroup#2),CASCRE(options),r1dv-r1dv,r21dv,r2dvor

#SC VOL,RMT(cuu, mhlist, rdfgroup#1, rdfroup#2),CASCRE(options),r1dv-r1dv,r21dv,r2dv The following rules apply:• The R21 devices may be diskless, but the R1 and R2 devices may not. • The RDF group specifications may not result in R1 and R2 devices residing on the same

Symmetrix system.• The R2 devices may not already have remote mirroring in effect; that is, they must be

standard devices at the start of the action.• If the device that will become the R21 of a triplet is diskless, the devices of the triplet must

have the same emulation mode and must be the same size. The ADSRDF option is not permitted.

• If the device that will become the R21 device of a triplet is diskless, the secondary Symmetrix system on which the R21 device will reside is required to be at Enginuity level 5874.

• The Symmetrix system on which the R1 and R2 devices of a triplet will reside are required to be at Enginuity level 5773 or higher. If at Enginuity level 5773, application of an Enginuity patch is required in order to connect to diskless devices at the secondary site.

CASDEL R1/L1/B1R2/L2/B2

This action terminates the SRDF relationships between both the R1→R21 and the R21→R2 pairs of one or more cascaded triplets. The devices in each triplet must be suspended.

Example:#SC VOL,RMT(cuu, mhlist, rdfgroup),CASDEL(options),r1dv-r1dvNotes:• If any eligible device triplet cannot be deleted because a device in the triplet has invalid

tracks and the FORCE option was not specified, no device pairs will be deleted. • If the R21 device of a triplet is diskless, CASDEL must be used to delete the pairs of the

triplet. If the R21 device of a triplet is not diskless, either component pair may be deleted individually via the DELETEPAIR action.


Action


#SC VOL 329

Command Reference

CASRSUM R1/L1/B1 This action may be used to resume the pairs in cascaded triplets. If the R21 device of a triplet is diskless, CASRSUM must be used for this purpose. If the R21 device is not diskless, the device pairs may be resumed individually by means of the RDF_RSUM action.

Example:#SC VOL,LCL(cuu, rdfgroup),CASRSUM(options),r1dv-r1dvNotes:• Similar to the RDF_RSUM action, the CASRSUM action will affect only those triplets in

which the R1 device of the cascaded triplet is the local device.• If the R21 device of a triplet is diskless, CASRSUM must be used to resume SRDF

replication activity for the pairs of the triplet. If the R21 device of a triplet is not diskless, either component pair may be resumed individually via the RDF_RSUM action.

CASSUSP R1/L1/B1 This action may be used to suspend the pairs in cascaded triplets. If the R21 device of a triplet is diskless, CASSUSP must be used for this purpose. If the R21 device is not diskless, the device pairs may be suspended individually by means of the RDF_SUSP action.Example:

#SC VOL,RMT(cuu, mhlist, rdfgroup),CASSUSP(options),r1dv-r1dvNotes:• Similar to the RDF_SUSP action, the CASSUSP action will affect only those triplets in which

the R1 device of the cascaded triplet is the local device.• If the R21 device of a triplet is diskless, CASSUSP must be used to suspend SRDF

replication activity on the pairs of the triplet. If the R21 device of a triplet is not diskless, either component pair may be suspended individually via the RDF_SUSP action.

• CASSUSP will also work against non-diskless device types.

CASSWAP R1 or R2 This action effects personality swaps of the two device pairs in each of one or more cascaded triplets. Each cascaded triplet R1↔R21↔R2 is thus transformed to the triplet R2↔R21↔R1, and each cascaded triplet R2↔R21↔R1 is transformed to the triplet R1↔R21↔R2.Example:#SC VOL,LCL(cuu, rdfgroup),CASSWAP(options),r1dv-r1dv

Notes:• All devices participating in the action must be suspended. If any eligible device triplet cannot

be swapped because a device in the triplet has invalid tracks and the FORCE option was not specified, no devices will be swapped.

• If the R21 device of a triplet is diskless, CASSWAP must be used to swap the pairs of the triplet. If the R21 device of a triplet is not diskless, either component pair may be swapped individually via the SWAP action.


Action



Command Reference

CREATEPAIR Dynamic SRDF devices

This action establishes an SRDF relationship between two dynamic SRDF-enabled devices. The default synchronization direction is primary to secondary (R1>R2). The CREATEPAIR action will fail if either side contains a diskless device.

This action is implemented via a command using non-standard syntax in one of the following formats:#SC VOL,LCL(cuu,rdfgroup#),CREATEPAIR(options),r1dv-r1dv,r2dv

or#SC VOL,RMT(cuu,mhlist,rdfgroup#),CREATEPAIR(options),r1dv-r1dv,r2dv Where r2dv indicates the beginning Symmetrix device number of a contiguous range of devices in the remote Symmetrix system.To create a concurrent dynamic RDF device arrangement:• Issue a CREATEPAIR to establish an RDF pair. Then issue a second CREATEPAIR

specifying the new R1 device and a second remote standard device to add a second R2 mirror for the R1 device.

To create a cascaded dynamic RDF device arrangement:• Issue a CREATEPAIR pairing an existing R2 device with a standard device, specifying an

RDF group linking the R2's Symmetrix system to the standard device's Symmetrix system. This CREATEPAIR must specify the ADCOPY_DISK option. This adds an R2 mirror to the existing R2 device, which has now become an R21 device, and results in an R1>R21>R2 configuration. The three devices configured in this way are often referred to as a cascaded triplet, and the R21 device as a cascaded device.It is also possible to create a cascaded dynamic RDF device arrangement by issuing a CREATEPAIR specifying, as the secondary device, a device which is already the primary device of an existing pair. The existing pair must be in ADCOPY_DISK mode prior to issuing the command to create the second pair.

Note: A cascaded device cannot be paired with devices on the same Symmetrix system. This state, which is known as a loopback, is not supported in Host Component. A CREATEPAIR action which would result in a loopback will not be allowed to proceed.

Cascaded SRDF is only available with Enginuity 5773 and higher. See “Cascaded SRDF” on page 50 for more information.

If the CREATEPAIR action results in creation of an R22 device, the newly created R2 mirror will be blocked and the new pair will be created in a suspended state. Moreover, if the newly created R22 device is not valid, the R2 mirror that previously existed will be blocked and suspended as well. R22 devices are only available with Enginuity 5874 and higher.


Action


#SC VOL 331

Command Reference

CREATEPAIR (continued)

The maximum Symmetrix device number on either side is dependent on the Enginuity level of the Symmetrix software. The maximum device number that can participate in the RDF configuration is the lower of the maximum numbers on both sides. The maximum device numbers (in hex) for the various Enginuity levels that support dynamic RDF are as follows:

5X68 - 0FFF5X69 - 1F3F5X70 - 1F3F5671 - 3E7F5771 and higher- F9FF

Note: Table 17 on page 343 lists the options available to the CREATEPAIR action.

Under Enginuity 5x68, the CREATEPAIR action can fail with EMCMN001 and EMCCV25I messages when devices are TimeFinder/Mirror Mainframe SNAP Facility devices. To avoid this, run the TimeFinder/Mirror command CONFIG RELEASE on the SNAP target volumes only to clear the SNAP target sessions. Then you can run CREATEPAIR against the SNAP devices.

DELETEPAIR Dynamic SRDF devices

This action terminates the SRDF relationship between two devices that have a relationship previously established by CREATEPAIR. The devices must be suspended.

If DELETEPAIR is issued to a concurrent device using a command that does not specify an RDF group, both remote mirrors will be deleted. To delete only one of the concurrent mirrors of a concurrent device, use one of the following methods:• If the partner of the remote mirror to be deleted is not concurrent, you may issue a

DELETEPAIR to the partner without specifying an RDF group.• You may issue a DELETEPAIR to either remote mirror or to the partner device, specifying

the LCL(cuu,rdfgrp#) or RMT(cuu,mhlist,rdfgrp#) format.To terminate an R1↔R21 device pairing for Cascaded SRDF of a cascaded triplet, use one of the following methods:• Issue a DELETEPAIR to the R21 device specifying the LCL(cuu,rdfgrp#) or

RMT(cuu,mhlist,rdfgrp#) format where rdfgrp# specifies the RDF group number for which you wish to delete the pair, or issue a DELETEPAIR to the R1 or the R2 device specifying the LCL(cuu,rdfgrp#) or RMT(cuu,mhlist,rdfgrp#) format where rdfgrp# refers to the RDF group linking the R1 or the R2 to the R21 partner.

A DELETEPAIR action against a pair in which either of the devices has a non-zero invalid track count will fail unless the FORCE option is specified.

DOMINO R1/L1/B1 This action enables Domino mode for the source (R1) device. This ensures that the data on the source (R1) and target (R2) volumes are fully synchronized at all times in the event of a failure.


Action



Command Reference

HDELETEPAIR Dynamic SRDF devices

This action, known as half deletepair, deletes only the local side of an RDF pair, leaving the remote partner unchanged. If HDELETEPAIR is issued to an R2 device and the remote partner is an accessible R1 device, the R1 must be suspended (TNR state).

If the R2 device is not part of a valid pair (for example, if the partner device was itself the object of an HDELETEPAIR or HSWAP action), the requirement that the R1 partner must be suspended does not apply. If the remote device is not accessible, the requirement that the R1 partner must be suspended likewise does not apply.If the HDELETEPAIR is issued to an R1 device, the requirements applied to the R1 device are the same as for a DELETEPAIR action. That is, the R1 device must be suspended, and if invalid tracks are detected, the FORCE option must be specified. If the FORCE option is not specified and a device range of ALL is specified, then if any eligible devices are found to have invalid tracks, the command is failed with no devices having been processed.

This action is provided for use in a disaster situation. When the failing site becomes operational, you should be prepared to do an HDELETEPAIR on that side as well and issue a CREATEPAIR to re-establish the partnership. Special procedures are provided for an SRDF/Star environment.

HMOVEPAIR Dynamic SRDF devices

This action, known as half movepair, changes the RDF group of only the local device of an RDF pair, leaving the remote partner unchanged. The action is implemented via a command using non-standard syntax in one of the following formats:#SC VOL,LCL(cuu,rdf-group),HMOVEPAIR,symdev#1-symdev#2,target-rdf-group

or#SC VOL RMT(cuu,mhlist,rdfgrp#),HMOVEPAIR,symdev#1-symdev#2,target-rdfgrp

If HMOVEPAIR is issued to an R2 device and the remote partner is an accessible R1 device, the R1 device must be suspended (TNR state). If the R2 device is not part of a valid pair (for example, if the partner device was itself the object of an HDELETEPAIR or HSWAP action), the requirement that the R1 partner must be suspended does not apply. If the remote device is not accessible, the requirement that the R1 partner must be suspended likewise does not apply.

If the HMOVEPAIR is issued to an R1 device, the device must be suspended, and if invalid tracks are detected, the FORCE option must be specified. If the FORCE option is not specified and a device range of ALL is specified, then if any eligible devices are found to have invalid tracks, the command is failed with no devices having been processed.The target group always denotes an RDF group defined on the same Symmetrix system as that on which the source RDF group is defined. If the other-side Symmetrix system of the target RDF group is accessible, it must be the same as the other-side system of the source RDF group.SRDF/A cannot be active on either the source or the target RDF group.


Action


#SC VOL 333

Command Reference

HSWAP Dynamic SRDF Devices

This action, known as half swap, swaps the SRDF relationship between only one side of the RDF pair, leaving the remote partner unchanged. Example:

#SC VOL RMT(cuu,mhlist,rdfgrp#),HSWAP(options),symdev#1-symdev#2

If HSWAP is issued to an R2 device and the remote partner is an accessible R1 device, the R1 device must be suspended (TNR state).

If the R2 device is not part of a valid pair (for example, if the partner device was previously the object of an HDELETEPAIR or HSWAP action), the requirement that the R1 partner must be suspended does not apply. If the remote device is not accessible, the requirement that the R1 partner must be suspended likewise does not apply.If the HSWAP is issued to an R1 device, the requirements applied to the R1 device are the same as for a SWAP action. That is, the R1 device must be suspended, and if invalid tracks are detected, the FORCE option must be specified. If the FORCE option is not specified and a device range of ALL is specified, then if any eligible devices are found to have invalid tracks, the command is failed with no devices having been processed.

If the HSWAP action is issued to an R11 device, the requirements applied to the R1 device are again the same as for a SWAP action. That is, the R1 mirror must be suspended, and if invalid tracks are detected, the FORCE option must be specified. Additionally, the Symmetrix system on which the R11 device resides must be at an Enginuity level of at least 5773. Finally, the ADCOPY_DISK option must be specified for the HSWAP action.This action is provided for use in a disaster recovery situation. If the HSWAP action results in creation of an R22 device, the newly created R2 mirror will be blocked. Moreover, if the newly created R22 device is not valid, the R2 mirror that previously existed will be blocked and suspended as well.

Caution: HSWAP can result in an invalid SRDF configuration. If, as a result of HSWAP, you end up with an R1 partnered with an R1 or an R2 partnered with an R2, you need to assess the status of both sides of the relationship and correct using HSWAP or HDELETEPAIR actions as required.


Action



Command Reference

INVALIDATE R1/R2/L1/L2/B1/B2

Use this action when all tracks on the SRDF partner volume are considered to be invalid from the point of view of the volume to which the command was issued. Keep in mind that in an SRDF configuration, both Symmetrix systems maintain their own invalid track tables for both the source (R1) and target (R2) volumes.When the SYNCH_DIRECTION is set to R1>R2, this action may be directed to the source (R1) volume to ensure that all of the R2 tracks are considered invalid from the source (R1) volume point of view. When the SYNCH_DIRECTION is set to R1<R2, this action may be directed to the target (R2) volume to ensure that all of the R1 tracks are considered invalid from the target (R2) volume point of view.

Note: Chapter 6, “Recovery Procedures,” describes how to use this action.

ITA R2/L2/B2 This action sets the Invalid Track Attribute. When set, if tracks are owed from the R1/L1 and the R2/L2 changes state, the R2/L2 is put into the RDF_NRDY state allowing a decision to be made concerning the invalid tracks owed to the R2/L2.

MOVEPAIR R1/R2/L1/L2/B1/B2

This action changes the RDF group of one or more RDF device pairs from one RDF group (the source) to another RDF group (the target). Partner devices are moved to the other-side RDF group of the target RDF group.

The action is implemented via a command using non-standard syntax in one of the following formats:#SC VOL,LCL(cuu,rdf-group),MOVEPAIR,symdev#1-symdev#2,target-rdf-group

or#SC VOL RMT(cuu,mhlist,rdfgrp#),MOVEPAIR,symdev#1-symdev#2,target-rdfgrp

The device pairs must be suspended. SRDF/A cannot be active on the target RDF group of a MOVEPAIR action unless in TOLERANCE mode or the CEXMPT option is specified.The target group always denotes an RDF group defined on the same Symmetrix system as that on which the source RDF group is defined. The other-side RDF group of the target RDF group must reside on the same Symmetrix system on which the other-side RDF group of the source RDF group resides.

NADCOPY R1/L1/B1 This action disables Adaptive Copy SRDF replication mode for the source (R1) volume.

When this command is issued to remove a volume from Adaptive Copy mode, the state change does not take place until the volumes comprising the device pair are synchronized. NADCOPY is not valid for cascaded (R21↔R2 device pairs.

Note: To switch between Adaptive Copy Disk mode and Adaptive Copy Write Pending mode, you must first use the NADCOPY action and then set the new Adaptive Copy mode.


Action


#SC VOL 335

Command Reference

NDOMINO R1/L1/B1 This action disables Domino mode for the source (R1) volume. During this default operating condition, a source (R1) volume continues processing I/Os with its host even when an SRDF volume or link failure occurs. These failures cause loss of source (R1) and target (R2) synchronization. When the failure is corrected, the volumes begin synchronizing.

Note: When switching from DOMINO mode to NDOMINO mode to clear an SRDF Not Ready (RNR) intervention required condition, after setting the state to NDOMINO and to RDF_RDY, issue the z/OS VARY ONLINE command to the device to clear the “intervention required” state.

NITA R2/L2/B2 This action removes the Invalid Track Attribute. When not set, if tracks are owed from the R1/L1 and the R2/L2 changes state, the R2/L2 is not put into the RDF_NRDY state.

NRDY R2/L2/B2 This action makes target (R2) volume(s) not ready. In this state, the target (R2) volume responds “intervention required” to the host for all read and write operations to that volume. This is the default state for a target (R2) volume.

OFFLINE When this action is issued, the SRDF Host Component address space uses the EMCSCF Cross System Communication component (CSC) to tell all ResourcePak Base SCF address spaces that support this function to vary the specified Symmetrix devices offline. Note that this can be a very long running command. The devices will be taken offline to all LPARs that have a ResourcePak Base address space with CSC active and that support the function. Note that ResourcePak Base V5.6.0 or later is required.

Note: If there is more than one instance of ResourcePak Base on an LPAR that supports the function, then one ResourcePak Base instance will vary the devices offline and the other will wait on serialization. If the command takes more than five minutes to run, the ResourcePak Base instance waiting on serialization will timeout and no longer attempt to process the commands.

ONLINE When this action is issued, the SRDF Host Component address space uses the EMCSCF Cross System Communication component (CSC) to tell all ResourcePak Base SCF address spaces that support this function to vary the specified Symmetrix devices online. Note that this can be a very long running command. The devices will be taken online to all LPARs that have a ResourcePak Base address space with CSC active and that support the function. Note that ResourcePak Base V5.6.0 or later is required.

Note: If there is more than one instance of ResourcePak Base on an LPAR that supports the function, then one ResourcePak Base instance will vary the devices online and the other will wait on serialization. If the command takes more than five minutes to run, the ResourcePak Base instance waiting on serialization will timeout and no longer attempt to process the commands.


Action



Command Reference

PREFRESH R1/L1/B1 This action causes only the updated tracks to be refreshed from the SRDF partner volume. The command is entered from the system with access to the volume that is being refreshed.This action is used when the R2 is R/W. The R1 must be RNR. This action is not valid when the SYNCH_DIRECTION is set to R1>R2.When the SYNCH_DIRECTION is set to R1<R2, invalid tracks are to be refreshed from the target (R2) volume to the source (R1) volume. Enter the PREFRESH command from the system with access to the source (R1) volume. The tracks are refreshed after a subsequent PRE_RSUM command is issued for the source (R1) volume.PREFRESH executes the REFRESH action by bypassing tests related to working with a R/W R2. Other than echoing the command, all messages indicate REFRESH processing.When used, a PREFRESH option is set. When this option is set, RFR_RSUM is rejected until either a REFRESH or PRE_RSUM is issued. If a device has the PREFRESH option set, an #SQ VOL command displays a P for PREFRESH rather than an R for REFRESH.

Note: The PREFRESH, RNG_PREFRESH, PRE_RSUM, and RNG_PRE_RSUM actions provide a way to start the synchronization of an R1 from an R2 that is still R/W to a host. Chapter 6, “Recovery Procedures,” discusses how this can be used as an additional recovery option.

PRE_RSUM R1/L1/B1 This action is used after an #SC VOL,cuu,PREFRESH command to commence synchronization. This command should be entered from the same system that the PREFRESH action was entered on.This action only operates on devices that have been objects of a PREFRESH action.PRE_RSUM executes the RFR_RSUM action but bypassing tests related to working with a R/W R2. Other than echoing the command, all messages indicate RFR_RSUM processing.

Note: The PREFRESH, RNG_PREFRESH, PRE_RSUM, and RNG_PRE_RSUM actions provide a way to start the synchronization of an R1 from an R2 that is still R/W to a host. Chapter 6, “Recovery Procedures,” discusses how this can be used as an additional recovery option.

RDY R2/L2/B2 This actions makes target (R2) volume(s) ready to the host.

RDF_NRDY R1/R2/L1/L2/

B1/B2

This action sets the volume not ready to the host. This action is valid for both source (R1) and target (R2) volumes.

When a volume is set RDF_NRDY, (RNR in the control unit status of the #SQ VOL command output) any attempt to perform I/O to the volume from the host results in an “intervention required” status. This command action may be used during R2 Read/Write testing to prevent host access during critical phases of recovery.


Action


#SC VOL 337

Command Reference

RDF_RDY R1/R2/L1/L2/B1/B2

This action sets the volume ready to the host. This action is valid for both source (R1) and target (R2) volumes.

RDF_RSUM R1/L1/B1 This action resumes SRDF operation on the RDF device pairs specified by the device range. Only device pairs in which the primary device is local are eligible for processing. Notes:• If the secondary device of an eligible device pair is an invalid R22 device, the RDF_RSUM

will be skipped for that device pair.• This action is not valid against volumes in a consistency group.• If either partner of a device pair to be resumed is diskless, the action will fail.

RDF_SUSP R1/L1/B1 This action suspends SRDF operation on a specified volume. If the volume is already suspended or in SRDF Write Disable status, this action is ignored. Notes:• If the device belongs to a consistency group, the suspend action is disallowed. If the volume

is configured for the Adaptive Copy mode, that volume is suspended immediately. • All Adaptive Copy skew tracks that have not been sent to the target (R2) volume become

invalid and are not sent until resynchronization begins after an RDF_RSUM action.• If the device to be suspended is the primary device of a device pair in an RDF group on

which an SRDF/A session is active, the suspend action will fail unless either the SRDF/A session is in tolerance mode or the CEXMPT option is specified.

• To ensure that the remotely mirrored volumes are synchronized, volumes operating in the adaptive copy mode must first be set to a synchronous or semi-synchronous state using the NADCOPY action. Use the #SQ VOL command to verify that the volumes are in the synchronous or semi-synchronous mode prior to issuing the RDF_SUSP action.

• If either the device to be suspended or its remote partner is diskless, the suspend action will fail.

RDF_WR_ENABLE R1/L1/B1 This action is issued to a source (R1) volume that has a control unit status of RWD as displayed in the #SQ VOL command. Before issuing this command, you must set the target (R2) volume to Read/Only status. This command clears the RWD status and allow the SRDF pair to begin synchronization.

Note: If the R2 volume indicates R1 invalid tracks, you must RDF_SUSP the R1 and follow the recovery procedures (starting with procedure 2) outlined in Chapter 6, “Recovery Procedures.”


Action



Command Reference

REFRESH R1/R2/L1/L2/B1/B2

This action causes only the updated tracks to be refreshed from the SRDF partner volume. The command is entered from the system with access to the volume that is being refreshed.• When the SYNCH_DIRECTION is set to R1>R2, invalid tracks are to be refreshed from the

source (R1) volume to the target (R2) volume. Enter the refresh command from the system with access to the target (R2) volume.

• When the SYNCH_DIRECTION is set to R1<R2, invalid tracks are to be refreshed from the target (R2) volume to the source (R1) volume, enter the refresh command from the system with access to the source (R1) volume.

The tracks are refreshed after a subsequent RFR_RSUM command is issued for the source (R1) volume.

RFR_RSUM R1/R2/L1/L2/

B1/B2

This action is used after a #SC VOL,cuu,REFRESH command to commence synchronization. This command should be entered from the same system on which the REFRESH action was entered.

RNG_PREFRESH This action adds range support, but otherwise functions the same as PREFRESH. This action causes only the updated tracks to be refreshed from the SRDF partner volume. The command is entered from the system with access to the volume that is being refreshed.

This action is used when the R2 is R/W. The R1 must be RNR. This action is not valid when the SYNCH_DIRECTION is set to R1>R2.

When the SYNCH_DIRECTION is set to R1<R2, invalid tracks are to be refreshed from the target (R2) volume to the source (R1) volume. Enter the RNG_PREFRESH command from the system with access to the source (R1) volume. The tracks are refreshed after a subsequent PRE_RSUM command is issued for the source (R1) volume.RNG_PREFRESH executes the RNG_REFRESH action by bypassing tests related to working with a R/W R2. Other than echoing the command, all messages indicate RNG_REFRESH processing.When used, a RNG_PREFRESH option is set. When this option is set, RNG_RSUM is rejected until either a RNG_REFRESH or RNG_PRE_RSUM is issued. If a device has the RNG_PREFRESH option set, an #SQ VOL command displays a P for RNG_PREFRESH rather than an R for RNG_REFRESH.Notes:• The RNG actions change #SC VOL processing so that, instead of passing one device at a

time to the Symmetrix, one or more ranges (contiguous sequences) of devices are passed to the Symmetrix system for processing. The discussion under “Range support” on page 359 provides additional information about this behavior.

• The PREFRESH, RNG_PREFRESH, PRE_RSUM, and RNG_PRE_RSUM actions provide a way to start the synchronization of an R1 from an R2 that is still R/W to a host. Chapter 6, “Recovery Procedures,” discusses how this can be used as an additional recovery option.


Action


#SC VOL 339

Command Reference

RNG_PRE_RSUM This action adds range support, but otherwise functions the same as PRE_RSUM. This action is used after an #SC VOL,cuu,RNG_PREFRESH command to commence synchronization. This command should be entered from the same system that the RNG_PREFRESH action was entered on.This action only operates on devices that have been objects of an RNG_PREFRESH action.RNG_PRE_RSUM executes the RNG_RSUM action but bypassing tests related to working with a R/W R2. Other than echoing the command, all messages indicate RNG_RSUM processing.Notes:• The RNG actions change #SC VOL processing so that, instead of passing one device at a

time to the Symmetrix, one or more ranges (contiguous sequences) of devices are passed to the Symmetrix system for processing. The discussion under “Range support” on page 359 provides additional information about this behavior.

• The PREFRESH, RNG_PREFRESH, PRE_RSUM, and RNG_PRE_RSUM actions provide a way to start the synchronization of an R1 from an R2 that is still R/W to a host. Chapter 6, “Recovery Procedures,” discusses how this can be used as an additional recovery option.

RNG_REFRESH This action adds range support, but otherwise functions the same as REFRESH. This action causes only the updated tracks to be refreshed from the SRDF partner volume. The command is entered from the system with access to the volume that is being refreshed.• When the SYNCH_DIRECTION is set to R1>R2, invalid tracks are to be refreshed from the

source (R1) volume to the target (R2) volume. Enter the refresh command from the system with access to the target (R2) volume.

• When the SYNCH_DIRECTION is set to R1<R2, invalid tracks are to be refreshed from the target (R2) volume to the source (R1) volume, enter the refresh command from the system with access to the source (R1) volume.

The tracks are refreshed after a subsequent RNG_RSUM command is issued for the source (R1) volume.

Note the following #SC VOL command format restrictions when using RNG_REFRESH:• Must use the SCFG, LCL, or RMT format• Must specify a range of devices or the ,ALL parameter

Note: The RNG actions change #SC VOL processing so that, instead of passing one device at a time to the Symmetrix, one or more ranges (contiguous sequences) of devices are passed to the Symmetrix system for processing. The discussion under “Range support” on page 359 provides additional information about this behavior.


Action



Command Reference

RNG_RSUM This action adds range support, but otherwise functions the same as RFR_RSUM. This action is used after a #SC VOL,cuu,RNG_REFRESH command to commence synchronization. This action should be entered from the same system on which the RNG_REFRESH action was entered.Note the following #SC VOL command format restrictions when using RNG_REFRESH:• Must use the SCFG, LCL, or RMT format• Must specify a range of devices or the ,ALL parameter

Note: The RNG actions change #SC VOL processing so that, instead of passing one device at a time to the Symmetrix, one or more ranges (contiguous sequences) of devices are passed to the Symmetrix system for processing. The discussion under “Range support” on page 359 provides additional information about this behavior.

R/O R2/L2/B2 This action makes target (R2) volume(s) read only. When a target (R2) volume is in this state, any attempt to issue a write from the host produces an I/O error.

R/W R2/L2/B2 This action makes target (R2) volume(s) read and write enabled. This allows a target (R2) volume to be written to from the channel.If you are running in SRDF/A mode, R/W cannot be issued to an R2 unless the R1 is TNR. SRDF/A drops if an R2 goes R/W.

Note: If you write to the target (R2) volume, you need to perform the testing and recovery procedures listed in Chapter 6, “Recovery Procedures.”

SEMI-SYNC R1/L1/B1 This action sets the source (R1) volume to the semi-synchronous mode. This is an SRDF mode of operation that provides an asynchronous mode of operation. Notes:• This value does not need to be reset following an IML. • Setting SYNC or SEMI-SYNC does not affect Adaptive Copy mode if in effect. Note that

semi-synchronous mode is not supported on Symmetrix DMX-3 models or on any Symmetrix model with FICON directors.


Action


#SC VOL 341

Command Reference

SUSP_CGRP R1/L1/B1 This is a special form of the RDF_SUSP action that works with consistency groups.

Note: The SUSP_CGRP action functions exactly as RDF_SUSP, except it trips an SRDF consistency group. This command must be issued to a valid MVS cuu that is in the consistency group.

SWAP Dynamic SRDF devices or R1/L1/B1/R2/L2/B2

This action swaps the SRDF relationship between two SRDF devices. Example:#SC VOL RMT(cuu,mhlist,rdfgrp#),SWAP(options),symdev#1-symdev#2

The swap is not permitted if either partner device would enter an invalid state. Thus, in the device arrangement R1→R21→R2 in which the R21 device resides on an Enginuity level 5773 Symmetrix system, the R1→R21 pair may be swapped but the R21→R2 pair may not be swapped because R22 devices are not supported on Enginuity level 5773 Symmetrix systems. Also, in the device arrangement R2↔R11↔R2, a swap of either pair, or a half-swap of either mirror of the R11 device, is permitted only if the R11 device resides on a Symmetrix system at Enginuity level 5x73 or later. The ADCOPY_DISK option must be specified.The SWAP action will fail if either partner is a diskless device.Notes:• If none of the device options (DOMINO|NODOMINO,SYNC|SEMI-SYNC,

ADCOPY|ADCOPY_DISK|NADCOPY,ITRK|NOITRK, RDY|NRDY, R/O|R/W) is specified, these options are set according to the R1/R2 state prior to the swap action. Otherwise, the requested options are used to determine the resulting device state, and for any option not specified, the default (underlined) option is applied.

• When the swap completes, the devices are placed into the state defined by the options. Table 17 on page 343 describes the options available to the SWAP action. Because the R1 has to be TNR to perform the SWAP, setting the DOMINO option causes the R1 to go RNR.

• If the SWAP action results in the creation of an R22 device, the newly created R2 mirror will be blocked. Moreover, if the newly created R22 device is not valid, the R2 mirror that previously existed will be blocked and suspended as well.

SYNC R1/L1/B1 This action sets the source (R1) volume to synchronous replication mode. This is an SRDF mode of operation that ensures 100% synchronized mirroring between the two Symmetrix systems.Notes:

• This setting is preserved and does not need to be reset following an IML. • Setting SYNC or SEMI-SYNC does not affect Adaptive Copy mode if in effect. Note that

semi-synchronous mode is not supported on Symmetrix DMX-3 models or on any Symmetrix model with FICON directors.


Action



Command Reference

a. R1 = source volume, R2 = target volume. Additional mirror types are described on page 297.

VALIDATE R1/R2/L1/L2/B1/B2

This action updates the invalid track table to remove all invalid track flags for all tracks residing on the SRDF partner device. Once this action is taken, all tracks on the SRDF partner volume are considered to be valid from the point of view of the volume to which the command was issued. Keep in mind that in an SRDF configuration, both Symmetrix systems maintain their own invalid track tables for both the source (R1) and target (R2) volumes.When the SYNCH_DIRECTION is set to R1>R2, this action may be issued to the target (R2) volume to ensure that all of the R1 device tracks are considered valid from the target (R2) volume point of view. Conversely, when the SYNCH_DIRECTION is set to R1<R2, this action may be issued to the source (R1) volume to ensure that all of the R2 device tracks are considered valid from the source (R1) volume point of view.

Note: Chapter 6, “Recovery Procedures,” describes how to use this action.


Action


#SC VOL 343

Command Reference

Options for commandactions

Many of the #SC VOL command actions have options that allow you to control the processing of the actions. Table 17 below lists the options available for the specified #SC VOL actions. Tables 18 through 21 on the following pages describe the types of operations that these options control.

Note: With SRDF Host Component (but not with the REXX interface), the NOEXEC option is available for a number of #SC VOL command actions. Specify the NOEXEC option to skip command processing after the validation phase. This allows you to view in advance the devices that would be processed if the command were allowed to execute. It also allows you to correct conditions resulting in device ineligibility prior to actually issuing the command.

Table 17 SC VOL command action options

Action Available options (defaults not shown)

CASCRE {ADCOPY_WP | ADCOPY_DISK}, CEXMPT, DIFFERENTIAL, ITRK, KEEPR2, LCLISR2, NOCOPY, NOEXEC, R/W, RDY, SEMI-SYNC, STAR, SUSPEND

CASDEL FORCE, NOEXEC

CASRSUM NOEXEC

CASSUSP CEXMPT, FORCE, NOEXEC

CASSWAP {ADCOPY_WP | ADCOPY_DISK | NADCOPY}, FORCE, NOEXEC

CREATEPAIR {ADCOPY_WP | ADCOPY_DISK}, ADSRDF, CEXMPT, DIFFERENTIAL, ITRK, KEEPR2, LCLISR2, NOCOPY, NOEXEC, RCVRY, R/W, RDY, SEMI-SYNC, STAR, SUSPEND

DELETEPAIR FORCE, NOEXEC, RCVRY, STAR

HDELETEPAIR FORCE, NOEXEC, RCVRY, STAR

HMOVEPAIR FORCE, NOEXEC, RCVRY

HSWAP {ADCOPY_WP | ADCOPY_DISK | NADCOPY}, FORCE, ITRK, KEEPR2, NOEXEC, NOSYNC, R/W, RCVRY, RDY, SEMI-SYNC, STAR

MOVEPAIR CEXMPT, NOEXEC, RCVRY

RDF_SUSP CEXMPT

SWAP {ADCOPY_WP | ADCOPY_DISK | NADCOPY}, DOMINO, FORCE, ITRK, KEEPR2, NOEXEC, NOSUSPEND, NOSYNC, R/W, RCVRY, RDY, SEMI-SYNC, STAR


Command Reference

Table 18 describes command action options that can affect device or pair eligibility for processing by the action.

Table 18 Options affecting device or pair eligibility (page 1 of 4)

Option: ADSRDF

Action Effect on eligibility

CREATEPAIR If not specified: Devices to be paired must be of equal size. Devices for which the intended partners are of unequal sizes are ineligible. If specified: Devices to be paired for which the intended secondary device is larger than the intended primary device are eligible.

Option: ADCOPY_DISK This option is mutually exclusive with the ADCOPY_WP and NADCOPY options.


CREATEPAIR If not specified: Devices to be paired for which the intended primary device would be cascaded are ineligible. If specified: Devices to be paired for which the intended primary device would be cascaded and is not diskless are eligible.

HSWAP If not specified: Devices which would become primary and would be cascaded after the half-swap are ineligible.If specified: Devices which would become primary and would be cascaded after the half-swap and are not diskless are eligible.

SWAP If not specified: Device pairs for which the primary device would be cascaded after the swap are ineligible.If specified: Device pairs for which the primary device would be cascaded after the swap and are not diskless are eligible.

Option: ADCOPY_WPThis option is mutually exclusive with the ADCOPY_DISK and NADCOPY options.


CREATEPAIR If not specified: Devices to be paired for which the intended primary device would be cascaded are ineligible.

If specified: Devices to be paired for which the intended primary device would be cascaded and is diskless are eligible.

HSWAP If not specified: Devices which would become primary and would be cascaded after the half-swap are ineligible.If specified: Diskless devices which would become primary and would be cascaded after the half-swap are eligible.

#SC VOL 345

Command Reference

Option: ADCOPY_WP (continued)

SWAP If not specified: Device pairs for which the primary device would be cascaded after the swap are ineligible.If specified: Device pairs for which the primary device is diskless and would be cascaded after the swap are eligible.

Option: CEXMPT


CASCRE If not specified: If an active SRDF/A session exists on the RDF group in which a new device pair will be defined and the SRDF/A session is not in Tolerance mode, the devices are ineligible to be paired.

If specified: The presence of an active SRDF/A session on the RDF group in which a new device pair will be defined is not considered in determining whether the devices are eligible to be paired.

CASSUSP If not specified: If any device triplet in the range includes a device pair in an RDF group on which there is an active SRDF/A session with tolerance mode off, no triplets are eligible and command processing is ended following validation.If specified: SRDF/A status is not considered in determining device triplet eligibility.

CREATEPAIR If not specified: If an active SRDF/A session exists on the RDF group in which a new device pair will be defined and the SRDF/A session is not in Tolerance mode, the devices are ineligible to be paired.

If specified: The presence of an active SRDF/A session on the RDF group in which a new device pair will be defined is not considered in determining whether the devices are eligible to be paired.

MOVEPAIR If not specified: If an active SRDF/A session exists on the specified target RDF group of the RDF group switch (movepair) action and the SRDF/A session is not in Tolerance mode, all device pairs are ineligible.

If specified: The presence of an active SRDF/A session on the specified target RDF group of the RDF group switch (movepair) action is not considered in determining whether device pairs are eligible.

RDF_SUSP If not specified: Devices which are primary and for which there is an active SRDF/A session not in Tolerance mode on the RDF group of the mirror to be suspended are ineligible.

If specified: The presence of an active SRDF/A session on the RDF group of the mirror to be suspended is not considered in determining whether the device is eligible.



Command Reference

Option: FORCE


CASDEL If not specified: If any device triplet in the range includes a device with invalid tracks, no triplets are eligible and command processing is ended following validation.If specified: The existence of invalid tracks is not considered in determining device triplet eligibility.

CASSWAP If not specified: If any device triplet in the range includes a device with invalid tracks, no triplets are eligible and command processing is ended following validation.

If specified: The existence of invalid tracks is not considered in determining device triplet eligibility.

DELETEPAIR If not specified: A device pair with invalid tracks on either device in the pair is not eligible.If specified: The existence of invalid tracks on either device in a pair is not considered in determining whether the device pair is eligible.

HDELETEPAIR If not specified: A device with invalid tracks is not eligible.If specified: The presence of invalid tracks on a device is not considered in determining whether the device is eligible.

HMOVEPAIR If not specified: A device with invalid tracks is not eligible.If specified: The presence of invalid tracks on a device is not considered in determining whether the device is eligible.

HSWAP If not specified: A device with invalid tracks is not eligible.If specified: The presence of invalid tracks on a device is not considered in determining whether the device is eligible.

MOVEPAIR If not specified: A device pair with invalid tracks on either device in the pair is not eligible.

If specified: The existence of invalid tracks on either device in a pair is not considered in determining whether the pair is eligible.

SWAP If not specified: A device pair with invalid tracks owed to the primary (R1) device on either device in the pair is not eligible.If specified: The existence of invalid tracks owed to the primary (R1) device on either device in a pair is not considered in determining whether the pair is eligible.


#SC VOL 347

Command Reference

Option: NADCOPYThis option is mutually exclusive with the ADCOPY_DISK and ADCOPY_WP options.


SWAP If not specified: If either of the adaptive copy options ADCOPY_DISK or ADCOPY_WP is specified, validation proceeds according as described under the specified adaptive copy option. Otherwise, a request to swap a device pair that would result in a primary device that is cascaded is denied.If specified: A request to swap a device pair resulting in a primary device that is cascaded is denied.

Option: STAR


CREATEPAIR If not specified: A request to create a device pair either partner of which would be in an RDF group with the Star or Star recovery attribute is denied.If specified: The Star and Star recovery attributes of the target RDF group are not considered when validating a request to create a device pair.

DELETEPAIR If not specified: A request to delete a device pair either partner of which is in an RDF group with the Star or Star recovery attribute is denied.If specified: The Star and Star recovery attributes of the RDF group in which a device pair is defined are not considered when validating a request to delete the device pair.

HDELETEPAIR If not specified: A request to half-delete a device from an RDF group with the Star or Star recovery attribute is denied.

If specified: The Star and Star recovery attributes of the RDF group in which a device is defined are not considered when validating a request to half-delete the device.

HSWAP If not specified: A request to half-swap a device in an RDF group with the Star or Star recovery attribute is denied.If specified: The Star and Star recovery attributes of the RDF group in which a device is defined are not considered when validating a request to half-swap the device.

SWAP If not specified: A request to swap a device pair either partner of which is in an RDF group with the Star or Star recovery attribute is denied.If specified: The Star and Star recovery attributes of the RDF group in which a device pair is defined are not considered when validating a request to swap the device pair.



Command Reference

Table 19 describes options used to set device state or device pair attributes after the action is complete but before any required synchronization takes place.

Table 19 Options used to set device or device pair attributes (page 1 of 5)

Option: ADCOPY_DISK This option is mutually exclusive with ADCOPY_WP and NADCOPY options.

Action Result

CASCRE If not specified: If the option ADCOPY_WP is specified, each newly created R1↔R21 device pair is set to adaptive copy write pending mode. Otherwise, each newly created R1↔R21 device pair is placed into synchronous replication mode.If specified: Each newly created R1↔R21 device pair is placed into adaptive copy disk mode.

Note: This option affects only newly created R1↔R21 device pairs; it has no effect on newly created R21↔R2 device pairs.

CASSWAP If not specified: If the option ADCOPY_WP is specified, each resulting R1↔R21 device pair is set to adaptive copy write pending mode. Otherwise, each resulting R1↔R21 device pair is placed into synchronous replication mode.

If specified: Each resulting R1↔R21 device pair is placed into adaptive copy disk mode.Note: This option affects only resulting R1↔R21 device pairs; it has no effect on resulting R21↔R2 device pairs.

CREATEPAIR If not specified: If the option ADCOPY_WP is specified, each newly created device pair is set to adaptive copy write pending mode. Otherwise, each newly created device pair is placed into synchronous replication mode.

If specified: Each newly created device pair is placed into adaptive copy disk mode.Notes: • This option is not permitted when creating a diskless cascaded device

pair (R21↔R2). • This option is required when creating a non-diskless cascaded device

pair (R21↔R2).

#SC VOL 349

Command Reference

Option: ADCOPY_DISK (continued)

HSWAP If not specified: Each half-swapped primary device is placed into synchronous replication mode; no effect if a secondary device.

If specified: Each half-swapped primary device is placed into adaptive copy disk mode; no effect if a secondary device.Notes: • This option is not permitted when a mirror of a diskless R22 cascaded

device is being half-swapped. • This option is required when a mirror of a non-diskless cascaded device

is being half-swapped.

SWAP If not specified: Each swapped device pair is placed into synchronous replication mode.

If specified: Each swapped device pair is placed into adaptive copy disk mode.Notes: • This option is not permitted when a pair including an R2 mirror of a

diskless R22 cascaded device is being swapped. • This option is required when a pair including an R2 mirror of a

non-diskless R22 cascaded device is being swapped.

Option: ADCOPY_WPThis option is mutually exclusive with the ADCOPY_DISK and NADCOPY options.

Action Result

CASCRE If not specified: If the option ADCOPY_DISK is specified, each newly created R1↔R21 device pair is set to adaptive copy disk mode. Otherwise, each newly created R1↔R21 device pair is placed into synchronous replication mode.

If specified: Each newly created R1↔R21 device pair is placed into adaptive copy write-pending mode.Note: This option affects only newly created R1↔R21 device pairs; it has no effect on newly created R21↔R2 device pairs.

CASSWAP If not specified: If the option ADCOPY_DISK is specified, each resulting R1↔R21 device pair is set to adaptive copy disk mode. Otherwise, each resulting R1↔R21 device pair is placed into synchronous replication mode.

If specified: Each resulting R1↔R21 device pair is placed into adaptive copy write-pending mode.Notices option affects only resulting R1↔R21 device pairs; it has no effect on resulting R21↔R2 device pairs.



Command Reference

Option: ADCOPY_WP (continued)

CREATEPAIR If not specified: If the option ADCOPY_DISK is specified, each newly created device pair is set to adaptive copy disk mode. Otherwise, each newly created device pair is placed into synchronous replication mode.If specified: Each newly created device pair is placed into adaptive copy write pending mode.

Notes:• This option is required when creating a diskless cascaded device pair

(R21↔ R2). • This option is not permitted when creating a non-diskless cascaded

device pair (R21↔R2).

HSWAP If not specified: Each half-swapped primary device is placed into synchronous replication mode; not applicable for a secondary device.If specified: Each half-swapped primary device is placed into adaptive copy write pending mode; no effect if a secondary device.

Notes:• This option is required when a mirror of a diskless R22 cascaded device

is being half-swapped. • This option is not permitted when a mirror of a non-diskless cascaded

device is being half-swapped.

SWAP If not specified: Each swapped device pair is placed into synchronous replication mode.If specified: Each swapped device pair is placed into adaptive copy write pending mode.Notes:• This option is required when a pair including an R2 mirror of a diskless

R22 cascaded device is being swapped. • This option is not permitted when a pair including an R2 mirror of a

non-diskless R22 cascaded device is being swapped.


#SC VOL 351

Command Reference

Option: CEXMPTAt initialization, SRDF/A establishes consistency between the local and remote sides. Thereafter, during normal operation, SRDF/A assures a consistent copy of the data on the R2 side. Adding a new device pair to the RDF group on which an SRDF/A session is active with tolerance mode on causes the SRDF/A session to become inconsistent; consistency is only regained after a full SRDF/A resynchronization. If tolerance mode is not set, the request to add a new device pair is denied.

Using the CEXMPT option when adding a device pair to an RDF group on which an SRDF/A session is active and tolerance mode is off, or when suspending a device pair in such an RDF group, addresses these issues as follows:• The request can be honored without deactivating the SRDF/A session. • Consistency of the existing SRDF/A session R2 data is maintained.• If a device pair is being added, the newly added device pair participates in the

consistency of the R2 data afforded by SRDF/A within two cycle switches once synchronization of the newly added device pair has been established. (If the pair already exists and is synchronized, synchronization is established immediately.)

WARNING

Do not use devices in the CEXMPT state until this state is cleared.

Action Result

CASCRE If not specified: No change in device or device pair state or attributes will occur if any device pair in any triplet to be created by the command would be in an RDF group on which there is an active SRDF/A session with tolerance mode off, because command processing will have been terminated following validation. If specified: If there is an active SRDF/A session with tolerance off on one of the RDF groups in which devices pairs will be created by the action, the state for all device pairs thus created is set to consistency exempt and the SRDF/A session is set to an inconsistent state. This option has no effect if SRDF/A is not active on the RDF groups on which device pairs are being created.

CASSUSP If not specified: No change in device or device pair state or attributes will occur if any triplet in the device range includes a device pair in an RDF group on which there is an active SRDF/A session with tolerance mode off, because the request will have been denied during validation.If specified: If a triplet to be suspended includes a device pair in an RDF group on which an active SRDF/A session exists, the device pair state within the SRDF/A group is set to consistency exempt and the SRDF/A session is set to an inconsistent state. This option has no effect for triplets neither of whose device pairs is in an RDF group on which an active SRDF/A session exists.



Command Reference

Option: CEXMPT (continued)

CREATEPAIR If not specified: A request to create a device pair in an RDF group on which an active SRDF/A session with tolerance mode off is denied.

If specified: Each device pair created in an SRDF/A group is set to consistency exempt state and the SRDF/A session is set to an inconsistent state. This option has no effect if SRDF/A is not active in the RDF group in which a new device pair has been defined.

MOVEPAIR If not specified: A request to move a device pair to an RDF group on which an active SRDF/A session with tolerance mode off is denied. If specified: Each device pair that has been moved to an RDF group on which SRDF/A is active is set to consistency exempt state and the SRDF/A session is set to an inconsistent state. This option has no effect if SRDF/A is not active in the RDF group to which device pairs are being moved.

RDF_SUSP If not specified: A request to suspend a device pair in an RDF group on which an active SRDF/A session with tolerance mode off is denied. If specified: Sets device pair state within SRDF/A group to consistency exempt and the SRDF/A session is set to an inconsistent state. This option has no effect if SRDF/A is not active in the RDF group to which the device pair belongs.


#SC VOL 353

Command Reference

Table 20 describes options that specify device synchronization performed after the device state or device pair status has been set.

Table 20 Options affecting device synchronization to be performed (page 1 of 4)

Option: DIFFERENTIAL This option is valid only if the STAR option is also specified and the specified RDF group has the Star attribute.

Action Result

CREATEPAIR If not specified: Full device synchronization takes place.If specified: Only changed tracks are copied, as identified by the SRDF/Star maintained track information.

Option: DOMINOIn LINKS-DOMINO mode, a source (R1) volume will go not-ready if the target (R2) volume is not ready or links are down. An R1 volume that is ready will become not ready if the R2 volume becomes not-ready or if the link to the R2 volume is lost.

Action Result

CREATEPAIR If not specified: A newly created device pair is not automatically placed into LINKS-DOMINO mode (but may be placed into LINKS-DOMINO mode if the target RDF group has the LINKS-DOMINO attribute).If specified: Each newly created device pair is placed into LINKS-DOMINO mode.

SWAP If not specified: A device pair retains its LINKS-DOMINO mode (but may be placed into LINKS-DOMINO mode if the target RDF group has the LINKS-DOMINO attribute).If specified: The swapped device pair is placed into LINKS-DOMINO mode.

Option: ITRKIf the Invalid Track Attribute is set, the target (R2) volume will go not ready if the source (R1) volume (its mirrored device) has invalid tracks on the target (R2) volume and a state of change has been requested on the target (R2) volume.

Action Result

CREATEPAIR If not specified: A newly created device pair is not automatically assigned the Invalid Track Attribute.If specified: : Each newly created device pair is assigned the Invalid Track Attribute.

SWAP If not specified: A device pair retains its Invalid Track Attribute setting.If specified: The swapped device pair is assigned the Invalid Track Attribute.


Command Reference

Option: KEEPR1

Action Result

CREATEPAIR If not specified: Device synchronization proceeds from R1 to R2.If specified: Device synchronization proceeds from R1 to R2.

Option: KEEPR2

Action Result

CREATEPAIR If not specified: Device synchronization proceeds from R1 to R2.If specified: Causes device synchronization to proceed from R2 to R1.

Option: LCLISR2

Action Result

CASCRE If not specified: The local device of each newly created device pair in each environment is the primary (R1) device in the pair.If specified: The local device of each newly created device pair in each environment is the secondary (R2) device in the pair.

CREATEPAIR If not specified: The local device of each newly created device pair is the primary (R1) device in the pair.

If specified: The local device of each newly created device pair is the secondary (R2) device in the pair.

Option: NADCOPY

Action Result

CREATEPAIR If not specified: If either of the adaptive copy options ADCOPY_DISK or ADCOPY_WP is specified, each newly created device pair is set to the corresponding adaptive copy replication mode. Otherwise, each newly created device pair is set to synchronous replication mode. If specified: Each newly created device pair is set to synchronous replication mode.

HSWAP If not specified: If either of the adaptive copy options ADCOPY_DISK or ADCOPY_WP is specified, each half-swapped device is set to the corresponding adaptive copy replication mode. Otherwise, each half-swapped primary device is set to synchronous replication mode.If specified: Each half-swapped primary device is set to synchronous replication mode.


#SC VOL 355

Command Reference

Option: NADCOPY (continued)

SWAP If not specified: If either of the adaptive copy options ADCOPY_DISK or ADCOPY_WP is specified, each swapped device pair is set to the corresponding adaptive copy replication mode. Otherwise, each swapped device pair is set to synchronous replication mode.

If specified: Each swapped device pair is set to synchronous replication mode.

Option: NOCOPY

Action Result

CREATEPAIR If not specified: Device synchronization proceeds in a manner governed by other options.

If specified: Causes device synchronization to be bypassed. This option may be appropriate during failover procedures in an SRDF/Star environment.

WARNING

Specify the NOCOPY option only if the devices that will become partner devices are already in sync. If the devices are not in sync, specifying this option can cause errors in the Symmetrix system when SRDF replication is resumed.

Option: NOSUSPEND

Action Result

SWAP If not specified: Each swapped device pair remains suspended.If specified: Each swapped device pair is resumed, enabling SRDF replication activity.

Option: R/W

Action Result

CREATEPAIR If not specified: The primary device of a newly created device pair is set read only.If specified: The primary device of a newly created device pair is set read write.

SWAP If not specified: The primary device of a newly created device pair is set read only.If specified: The primary device of a swapped device pair is set read write.



Command Reference

Option: RDY

Action Result

CREATEPAIR If not specified: The primary device of a newly created device pair appears not ready to the host.If specified: The primary device of a newly created device pair appears ready to the host.

SWAP If not specified: The primary device of a newly created device pair appears not ready to the host.

If specified: The primary device of a swapped device pair appears ready to the host.

Option: SEMI-SYNC

Action Result

CREATEPAIR If not specified: The SRDF replication mode of each newly created device pair is set to synchronous mode.

If specified: The SRDF replication mode of each newly created device pair is set to semi-synchronous mode.

SWAP If not specified: The SRDF replication mode of each swapped device pair is unchanged.If specified: The SRDF replication mode of each swapped device pair is set to semi-synchronous mode.

Option: SUSPEND

Action Result

CREATEPAIR If not specified: Device synchronization proceeds in a manner governed by other options.If specified: Causes newly created device pairs to be suspended and device synchronization to be delayed.

Option: SYNC

Action Result

SWAP If not specified: The SRDF replication mode of each swapped device pair is unchanged.If specified: The SRDF replication mode of each swapped device pair is set to synchronous mode.


#SC VOL 357

Command Reference

Table 21 describes options affecting device or pair eligibility in a recovery situation.

IMPORTANT!The RCVRY option is to be used in a recovery situation only.

Table 21 Options to be used in a recovery situation only

Option: RCVRY

Action Result

CREATEPAIR If not specified: Diskless devices are not eligible.If specified: Diskless devices are not considered when determining eligibility.

DELETEPAIR If not specified: Device pairs including a diskless device are not eligible.

If specified: Diskless devices are not considered when determining eligibility.

HDELETEPAIR If not specified: Diskless devices are not eligible.If specified: Diskless devices are not considered when determining eligibility.

HMOVEPAIR If not specified: Diskless devices are not eligible.If specified: Diskless devices are not considered when determining eligibility.

HSWAP If not specified: Diskless devices are not eligible.

If specified: Diskless devices are not considered when determining eligibility.

MOVEPAIR If not specified: Device pairs including a diskless device are not eligible.If specified: Diskless devices are not considered when determining eligibility.

SWAP If not specified: Device pairs including a diskless device are not eligible.If specified: Diskless devices are not considered when determining eligibility.


Command Reference

RestrictionsTable 22 lists the #SC VOL command restrictions.

Comments

Creating an RDF relationship to a second R2If the CONCURRENT RDF feature is enabled, then you can use the CREATEPAIR action to create an RDF relationship to a second R2 mirror. You can determine whether CONCURRENT RDF is enabled in your configuration by using the #SQ CNFG command, described on Page 186. The second R2 mirror must be in a different RDF group from the first. If, when adding the second R2 mirror, KEEPR2 is specified, the existing R2 must be in the suspended state (RDF_SUSP).

Use of the DELETEPAIR actionWhen using the DELETEPAIR action against a device with concurrent remote mirrors, make sure to correctly identify which device pairing to remove. This can be done either by deleting the pair from the R2 side, or by selecting the appropriate RDF group using the LCL(cuu,rdfgroup#) or RMT(cuu,mhlist,rdfgroup#) parameter.

WARNINGWARNING

If no group is specified and the specified device has two remote mirrors, the default action is to delete both pairs.

Table 22 #SC VOL command restrictions

Action Description Exception Messages

R/W R/W cannot be issued to an R2 unless the R1 is TNR. SRDF/A drops if an R2 goes R/W.

If the link is down when this action is issued, the informational message EMCPC081 RAGROUP SPECIFIED DOES NOT EXIST is generated. However, the R2 does change to R1. You can issue an SQ STATE command to confirm the personality change.When a REFRESH is issued, the link must be available because the R1 is checked to see if it is in TNR status.

None

#SC VOL 359

Command Reference

Use of the ADSRDF optionTo create a dynamic SRDF pair with the R1 device smaller than the R2 device, type the following command:

#SC VOL,LCL(2830,31),CREATEPAIR(ADSRDF),30,40

If a CREATEPAIR is requested without the ADSRDF option and an attempt to create a pair with different size R1 and R2 volumes is detected, the CREATEPAIR fails. This safeguard prevents a CREATEPAIR to the wrong volumes erroneously. The ADSRDF specification does not prevent the creation of same-size pairs, however. One or more (or all) of the pairs could be same size volumes and no error would be generated.

Range supportRange support is implemented through the use of the #SC VOL actions RNG_REFRESH, RNG_RSUM, RNG_PREFRESH, and RNG_PRE_RSUM.

The RNG action causes #SC VOL to process one or more ranges (contiguous sequences) of devices instead of a single device at a time. This provides increased parallelism in device processing. Optimum results are obtained if the devices are in contiguous ranges. If #SC VOL RNG specifies a list of devices that are not all contiguous, it will pass the devices to the Symmetrix individually or in ranges where they are contiguous. EMCCV1DI messages are issued to indicate the ranges that were processed.

Note: Range processing does not support unequal size R1/R2 device pairs. Unequal size R1/R2 pairs found in the device pair set in a RNG_REFRESH request will be excluded from processing and must be processed by a REFRESH request (message EMCCV7EI).

RNG_REFRESH or RNG_RSUM processing time can be one fifth or even one seventh of the standard REFRESH or RFR_RSUM time when processing a large number of contiguous devices. But it is also possible for the RNG processing time to be no better than standard REFRESH / RFR_RSUM processing time when the number of separate contiguous ranges in a single RNG_REFRESH / RNG_RSUM gets very large. For example, if a RNG request processes every other device (few or no contiguous devices), the processing time will not be better than standard processing. The host and Symmetrix activity levels and the pattern of the breaks in contiguous ranges also affect the processing time reduction.


Command Reference

The following #SC VOL command format limitations apply when using the RNG_REFRESH and RNG_RSUM action parameters:

◆ #SC VOL must use SCFG, LCL, or RMT formats.

◆ #SC VOL must specify a range of devices or the ,ALL parameter.

◆ For LCL and RMT, #SC VOL must specify a valid RDF group with the gatekeeper device to identify the correct RDF mirror for the action.

◆ For RMT, #SC VOL must specify a valid multihop (RDF group) list with the gatekeeper device to identify the target box.

Swap operationsFor an #SC VOL SWAP action, any device in the specified range is ineligible if it is:

◆ Not TNR

◆ Part of a consistency group

◆ A member of an RDF group on which SRDF/A is active

If such a device is found, the command fails unless FORCE is specified, in which case a warning message is issued and the command proceeds for eligible devices.

If OPERATOR_VERIFY is set to ALL or CRITICAL, operator verification is requested for SWAP operations. If any primary (source R1) or secondary (target R2) in the dev-range has invalid tracks on either mirror, an operator confirmation is requested (regardless of the setting of OPERATOR_VERIFY) or a warning message is issued that resynchronization procedures need to be performed after the swap completes.

The R2 in all CREATEPAIR actions is set to Read Only (RO) and Not Ready (NR). If another state is desired, use the Host Component#SC VOL command on the R2.

On R1-R2 personality swap actions, the new R2 defaults to Not Ready to the host (NRDY) unless otherwise specified in the SWAP. It is strongly suggested that the R1 devices be offline prior to the SWAP action. If an R1 device has two remote mirrors and Cascaded SRDF is not available, the SWAP action is disabled.

If the Adaptive Copy states are selected, the ADC_MAX skew is defaulted to the maximum possible value, 65535. To specify another value, use the Host Component #SC VOL command to set the desired ADC_MAX for the device.

#SC VOL 361

Command Reference

R22 device implementation guidelinesAn R22 device is valid if a single R11 is the source for the R22 data on each of its mirrors as shown in Figure 18:

Figure 27 R22 device implementation

◆ If a device becomes an R22 device due to a CREATEPAIR, SWAP, or HSWAP action, the newly created R2 mirror is always inactive, and if the newly created R22 device is invalid, the R2 mirror that existed previously becomes inactive as well.

◆ If one of the R2 mirrors of an R22 device is eliminated via a SWAP, HSWAP, DELETEPAIR, or HDELETEPAIR action, the remaining R2 mirror becomes active.

◆ If an R22 device is valid and the partner of the inactive R2 mirror is in TNR state, if RDF_RSUM is applied to the partner of the inactive R2 mirror then the inactive R2 mirror becomes active and the active R2 mirror becomes inactive.

R11 R21

R22

Recoverypath


Command Reference

#STOPThe #STOP command terminates SRDF Host Component.

Syntax #STOP

Parameters None.

#TF 363

Command Reference

#TFThe #TF command allows EMC TimeFinder commands to be issued. The commands are issued one at a time directly to EMC TimeFinder using TimeFinder syntax. All #TF commands require you to confirm the action you have specified, unless this has been disabled by the OPERATOR_VERIFY initialization parameter. TimeFinder security is also honored.

Format #TF TimeFinderCommand

Parameters TimeFinderCommand

EMC TimeFinder commands use the syntax described in the TimeFinder/Mirror for z/OS Product Guide.

Note: The TimeFinder output is optimized to avoid overflow of the SRDF message table. The following messages may be eliminated when they occur redundantly:

BCVM039I (XXXX) Process input statementBCVM069I Security Exit allowed the bypassing of the online state checkBCVM140I Command processed via TF/Clone emulation

Blank lines between device output are also eliminated.


Command Reference

SRDF Operations 365

5

This chapter provides examples of operations performed using the SRDF Host Component commands. Topics include:

◆ Configuring SRDF operations........................................................ 366◆ Performing operations using a multihop list............................... 369◆ Resetting TNR status for an R1 device.......................................... 371◆ Performing a personality swap (non-Cascaded SRDF).............. 375◆ Creating a dynamic RDF pair ........................................................ 378◆ Creating an RDF group ................................................................... 385◆ Modifying an RDF group................................................................ 388◆ Performing Cascaded SRDF operations ....................................... 390◆ Performing Cascaded SRDF operations (diskless)...................... 394◆ Moving dynamic SRDF pairs ......................................................... 402◆ Performing recovery in a diskless environment.......................... 408

SRDF Operations


SRDF Operations

Configuring SRDF operationsThe examples in this section illustrate how to use the #SC VOL command to set up SRDF operations.

Suspending SRDF for a single address

The following example suspends SRDF for one z/OS address:

#SC VOL,2150,RDF-SUSP

SRDF suspends z/OS address 2150.

Suspending SRDF for a range of addressesThe following example suspends SRDF for a range of z/OS addresses:

#SC VOL,2150-215F,RDF-SUSP

SRDF suspends z/OS addresses 2150 - 215F.

Resuming SRDF for a single deviceThe following example resumes SRDF for one device using Symmetrix device number:

#SC VOL,2100,RDF-RSUM,0050

This example accesses the Symmetrix associated with z/OS address 2100 and SRDF suspends Symmetrix device number 0050. The device for z/OS address 2100 is used as a gatekeeper. In other words, the software uses that device to communicate with the Symmetrix. The action is not performed on 2100.

Configuring SRDF operations 367

SRDF Operations

Resuming SRDF for a range of devicesThe following example resumes SRDF for a range of devices using Symmetrix device numbers:

#SC VOL,2100,RDF-RSUM,0050-005F

This example accesses the Symmetrix system associated with z/OS address 2100 and SRDF suspends Symmetrix device numbers 0050 thru 005F. The device for z/OS address 2100 is used as a gatekeeper. In other words, the software uses that device to communicate with the Symmetrix system. The action is not performed on 2100.

Resuming SRDF for a range of devices in a concurrent environment

The following example resumes SRDF for a range of devices using Symmetrix device numbers in a concurrent SRDF environment:

#SC VOL,LCL(4440,3),RDF-RSUM,0050-005F

This example accesses the Symmetrix system associated with z/OS address 4440, and SRDF suspends Symmetrix device numbers 0050 thru 005F for only RDF group 03. The device for z/OS address 4440 is used as a gatekeeper. In other words, the software uses that device to communicate with the Symmetrix. The action is not performed on 4440.

Changing status to ready

The following example changes status to ready for a range of R2 devices from a host connected to an R1 device:

#SC VOL,RMT(8BD0),RDY,01D0-01DF

This example accesses the Symmetrix system associated with z/OS address 8BD0, and passes the command over the SRDF link to the target Symmetrix system and changes the remote target Symmetrix device numbers 01D0 thru 01DF to a READY status.


SRDF Operations

Changing status to read onlyThe following example changes status to read only for one R2 device from host connected to a R1 device:

#SC VOL,RMT(8BD0,1),R/O,01D0

This example accesses the Symmetrix system associated with z/OS address 8BD0, and passes the command over the SRDF link defined to RDF group 01 to the target Symmetrix system and changes the remote target Symmetrix device number 01D0 to READ ONLY status.

Changing status to read/writeThe following example changes status to read/write for a range of R2 devices from a host connected to an R1 device in a concurrent SRDF environment:

#SC VOL,RMT(4450,3),R/W,0060-006F

This example accesses the Symmetrix system associated with z/OS address 4450, and passes the command over the SRDF link defined to RDF group 03 to the target Symmetrix system and changes the remote target Symmetrix device numbers 0060 thru 006F to READ/WRITE status.

Performing operations using a multihop list 369

SRDF Operations

Performing operations using a multihop listThe examples in this section explain how to carry out various SRDF operations in a multihop configuration. Figure 28 shows the configuration to which the examples apply.

Figure 28 SRDF multihop configuration

Note: Normally, configurations are created starting at RDF group 0, but to make these examples easier to understand, we made them unique.

Symm A

MVS Addr1000

0 5

Symm D

6

7

Symm C

3 4

Symm E

8

Symm F

9

Symm B

21

*** Numbers denote RDF group#Only MVS address available is 1000


SRDF Operations

Querying devicesThe following example queries 16 devices on Symmetrix C, starting at symdev# 0070:

#SQ VOL,RMT(1000,0.2),16,0070

The following example queries all devices on Symmetrix F:

#SQ VOL,RMT(1000,0.2.4.7),ALL

Changing devices to adaptive copy disk modeThe following example changes all devices on Symmetrix C to adaptive copy disk mode:

#SC VOL,RMT(1000,0.2),ADCOPY-DISK,ALL

RDF-suspending devices

The following example RDF-suspends devices 0080 - 00AF on Symmetrix D to Symmetrix E only:

#SC VOL,RMT(1000,0.2.4,6),RDF-SUSP,0080,48

Changing R2 devices to R/WThe following example changes all R2 devices to R/W on Symmetrix F:

#SC VOL,RMT(1000,0.2.4.7),R/W,ALL

Resetting TNR status for an R1 device 371

SRDF Operations

Resetting TNR status for an R1 deviceThe following examples assume an R1 controller at cuu=2100 and an R2 controller with no host attachment. The Symmetrix device range for the R1 controller is 020-02F. The Symmetrix device range for the R2 controller is 031-03F. The R1 controller (2100) is channel attached to the host. The R2 controller is connected to the R1 controller through rdfgroup 01.

A range of SRDF R1 devices can be in TNR (Target Not Ready) status for a number of reasons. The most common reason is caused by the RDF-SUSP action for the #SC VOL command:

#SC VOL,2100,RDF-SUSP,020-02F

The previous command sets the TNR status for the range of Symmetrix devices 020-02F in control unit 2100. Figure 29 provides more information.

Figure 29 R1 device range after RDF-SUSP action

If no I/O has been performed on the partner R2 devices, the R1 TNR status can be reset by the following command:

#SC VOL,2100,RDF-RSUM,020-02F

EMCQV00I SRDF-HC DISPLAY FOR (96) #SQ VOL,2100,16,020 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %2120 20 0020 0030 00 MV2120 3339 OFFL 0 TNR-SY L1 0 0 **2121 21 0021 0031 00 MV2121 3339 OFFL 0 TNR-SY L1 0 0 **2122 22 0022 0032 00 MV2122 3339 OFFL 0 TNR-SY L1 0 0 **2123 23 0023 0033 00 MV2123 3339 OFFL 0 TNR-SY L1 0 0 **2124 24 0024 0034 00 MV2124 3339 OFFL 0 TNR-SY L1 0 0 **2125 25 0025 0035 00 MV2125 3339 OFFL 0 TNR-SY L1 0 0 **2126 26 0026 0036 00 MV2126 3339 OFFL 0 TNR-SY L1 0 0 **2127 27 0027 0037 00 MV2127 3339 OFFL 0 TNR-SY L1 0 0 **2128 28 0028 0038 00 MV2128 3339 OFFL 0 TNR-SY L1 0 0 **2129 29 0029 0039 00 MV2129 3339 OFFL 0 TNR-SY L1 0 0 **212A 2A 002A 003A 00 MV212A 3339 OFFL 0 TNR-SY L1 0 0 **212B 2B 002B 003B 00 MV212B 3339 OFFL 0 TNR-SY L1 0 0 **212C 2C 002C 003C 00 MV212C 3339 OFFL 0 TNR-SY L1 0 0 **212D 2D 002D 003D 00 MV212D 3339 OFFL 0 TNR-SY L1 0 0 **212E 2E 002E 003E 00 MV212E 3339 OFFL 0 TNR-SY L1 0 0 **212F 2F 002F 003F 00 MV212F 3339 OFFL 0 TNR-SY L1 0 0 **


SRDF Operations

If the partner R2 devices have received I/O while the R1 TNR status existed, the RDF-RSUM action may fail. Figure 30 on page 372 provides more information.

The "EMCCVCFE THE FOLLOWING DEVICES REQUIRE SPECIAL PROCESSING BEFORE RESUME" message indicates that the partner R2 devices can be set to discard any changes that may have occurred.

Figure 30 R2 device range prior to procedure

To reset TNR status for R1 devices and to clear R1 invalid tracks from R2 device display, perform the following steps:

1. Ensure the R1 control unit is set for SYNCH_DIRECTION of R1>R2 by issuing the following command:

#SC CNFG,2100,SYNCH_DIRECTION,R1>R2

2. Set the R2 device range to read-only by issuing the following command:

#SC VOL,RMT(2100,01),R/O,030-03F

3. Prepare the range of changed R2 devices to discard any changed tracks by issuing the following command:

#SC VOL,RMT(2100,01),REFRESH,030-03F

EMCMN00I SRDF-HC : (58) #SQ VOL,RMT(2100,01),16,030EMCQV00I SRDF-HC DISPLAY FOR (58) #SQ VOL,RMT(2100,01),16,020 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %3130 30 0030 0020 00 MV2120 3339 ONPV 0 R/W -I L2 8 0 993131 31 0031 0021 00 MV2121 3339 ONPV 0 R/W -I L2 8 0 993132 32 0032 0022 00 MV2122 3339 ONPV 0 R/W -I L2 8 0 993133 33 0033 0023 00 MV2123 3339 ONPV 0 R/W -I L2 8 0 993134 34 0034 0024 00 MV2124 3339 ONPV 0 R/W -I L2 8 0 993135 35 0035 0025 00 MV2125 3339 ONPV 0 R/W -I L2 8 0 993136 36 0036 0026 00 MV2126 3339 ONPV 0 R/W -I L2 8 0 993137 37 0037 0027 00 MV2127 3339 ONPV 0 R/W -I L2 8 0 993138 38 0038 0028 00 MV2128 3339 ONPV 0 R/W -I L2 7 0 993139 39 0039 0029 00 MV2129 3339 ONPV 0 R/W -I L2 7 0 99313A 3A 003A 002A 00 MV212A 3339 ONPV 0 R/W -I L2 7 0 99313B 3B 003B 002B 00 MV212B 3339 ONPV 0 R/W -I L2 7 0 99313C 3C 003C 002C 00 MV212C 3339 ONPV 0 R/W -I L2 7 0 99313D 3D 003D 002D 00 MV212D 3339 ONPV 0 R/W -I L2 7 0 99313E 3E 003E 002E 00 MV212E 3339 ONPV 0 R/W -I L2 7 0 99313F 3F 003F 002F 00 MV212F 3339 ONPV 0 R/W -I L2 7 0 99END OF DISPLAY

Resetting TNR status for an R1 device 373

SRDF Operations

4. Replace the R2 discarded tracks with R1 track data, and reset the R1 TNR status by issuing the following command:

#SC VOL,RMT(2100,01),RFR-RSUM,030-03F

5. Monitor the resynchronization process until all invalid tracks show zero by issuing the following commands:

#SQ VOL,2100,16,020#SQ VOL,RMT(2100,01),16,030

Figure 31 and Figure 32 on page 374 show the status of the R1 and R2 devices after the procedure completes.

Figure 31 Status of R1 devices after the procedure

EMCMN00I SRDF-HC : (84) #SQ VOL,2100,16,020EMCQV00I SRDF-HC DISPLAY FOR (84) #SQ VOL,2100,16,020 166DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %2120 20 0020 0030 00 MV2120 3339 OFFL 0 R/W-SY L1 0 0 **2121 21 0021 0031 00 MV2121 3339 OFFL 0 R/W-SY L1 0 0 **2122 22 0022 0032 00 MV2122 3339 OFFL 0 R/W-SY L1 0 0 **2123 23 0023 0033 00 MV2123 3339 OFFL 0 R/W-SY L1 0 0 **2124 24 0024 0034 00 MV2124 3339 OFFL 0 R/W-SY L1 0 0 **2125 25 0025 0035 00 MV2125 3339 OFFL 0 R/W-SY L1 0 0 **2126 26 0026 0036 00 MV2126 3339 OFFL 0 R/W-SY L1 0 0 **2127 27 0027 0037 00 MV2127 3339 OFFL 0 R/W-SY L1 0 0 **2128 28 0028 0038 00 MV2128 3339 OFFL 0 R/W-SY L1 0 0 **2129 29 0029 0039 00 MV2129 3339 OFFL 0 R/W-SY L1 0 0 **212A 2A 002A 003A 00 MV212A 3339 OFFL 0 R/W-SY L1 0 0 **212B 2B 002B 003B 00 MV212B 3339 OFFL 0 R/W-SY L1 0 0 **212C 2C 002C 003C 00 MV212C 3339 OFFL 0 R/W-SY L1 0 0 **212D 2D 002D 003D 00 MV212D 3339 OFFL 0 R/W-SY L1 0 0 **212E 2E 002E 003E 00 MV212E 3339 OFFL 0 R/W-SY L1 0 0 **212F 2F 002F 003F 00 MV212F 3339 OFFL 0 R/W-SY L1 0 0 **END OF DISPLAY


SRDF Operations

Figure 32 Status of R2 devices after the procedure

EMCMN00I SRDF-HC : (98) #SQ VOL,RMT(2100,01),16,030EMCQV00I SRDF-HC DISPLAY FOR (98) #SQ VOL,RMT(2100,01),16,030 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %3130 30 0030 0020 00 MV2120 3339 ONPV 0 R/O L2 0 0 **3131 31 0031 0021 00 MV2121 3339 ONPV 0 R/O L2 0 0 **3132 32 0032 0022 00 MV2122 3339 ONPV 0 R/O L2 0 0 **3133 33 0033 0023 00 MV2123 3339 ONPV 0 R/O L2 0 0 **3134 34 0034 0024 00 MV2124 3339 ONPV 0 R/O L2 0 0 **3135 35 0035 0025 00 MV2125 3339 ONPV 0 R/O L2 0 0 **3136 36 0036 0026 00 MV2126 3339 ONPV 0 R/O L2 0 0 **3137 37 0037 0027 00 MV2127 3339 ONPV 0 R/O L2 0 0 **3138 38 0038 0028 00 MV2128 3339 ONPV 0 R/O L2 0 0 **3139 39 0039 0029 00 MV2129 3339 ONPV 0 R/O L2 0 0 **313A 3A 003A 002A 00 MV212A 3339 ONPV 0 R/O L2 0 0 **313B 3B 003B 002B 00 MV212B 3339 ONPV 0 R/O L2 0 0 **313C 3C 003C 002C 00 MV212C 3339 ONPV 0 R/O L2 0 0 **313D 3D 003D 002D 00 MV212D 3339 ONPV 0 R/O L2 0 0 **313E 3E 003E 002E 00 MV212E 3339 ONPV 0 R/O L2 0 0 **313F 3F 003F 002F 00 MV212F 3339 ONPV 0 R/O L2 0 0 **END OF DISPLAY


SRDF Operations

Creating a dynamic RDF pair The following example creates dynamic RDF pairs using the #SC VOL CREATEPAIR action.

1. Issue the #SQ CNFG command to verify that dynamic RDF is turned on for the Symmetrix. Dynamic RDF needs to be set for each device.

EMCMN00I SRDF-HC : (44) #SQ CNFG,EC50EMCGM11I SRDF-HC DISPLAY FOR (44) #SQ CNFG,EC50 466SERIAL NUMBER: 000185500038 MEM: 8,192 MB TYPE:3990 MODEL: 8430MICROCODE LEVEL: 5568-44SWITCHED-RDF DYNAMIC-RDF NO-AUTO-LINK-RECOVERY LINKS-OFF-ON-POWERUPLINKS-DOMINO: NO SYNCH_DIRECTION: GLOBAL LINK: LOCALSSID(S): EC00 EC01 EC02 EC03 EC04 EC05 EC06 EC07 EC08 EC09 EC0A EC0B EC0C EC0D EC0E EC0F EC10 EC11 EC12 EC13 EC14 EC15D01: DA D02: DA D03: EA D04: __ D05: __ D06: __ D07: __ D08: __D09: __ D10: __ D11: __ D12: RF D13: __ D14: EA D15: DA D16: DAD17: DA D18: DA D19: EA D20: __ D21: __ D22: __ D23: __ D24: __D25: __ D26: __ D27: __ D28: RF D29: __ D30: EA D31: DA D32: DAD33: __ D34: __ D35: EA D36: __ D37: __ D38: __ D39: __ D40: __D41: __ D42: __ D43: __ D44: __ D45: __ D46: EA D47: __ D48: __D49: __ D50: __ D51: EA D52: __ D53: __ D54: __ D55: __ D56: __D57: __ D58: __ D59: __ D60: __ D61: __ D62: EA D63: __ D64: __END OF DISPLAY

EMCMN00I SRDF-HC : (45) #SQ CNFG,9500EMCGM11I SRDF-HC DISPLAY FOR (45) #SQ CNFG,9500 473SERIAL NUMBER: 000184501803 MEM: 4,096 MB TYPE:2105 MODEL: 8430MICROCODE LEVEL: 5568-44 CONCURRENT-RDFSWITCHED-RDF DYNAMIC-RDF NO-AUTO-LINK-RECOVERY LINKS-OFF-ON-POWERUPLINKS-DOMINO: NO SYNCH_DIRECTION: GLOBAL LINK: LOCALSSID(S): 9400 9401 9402D01: DA D02: DA D03: RF D04: EA D05: __ D06: __ D07: __ D08: __D09: __ D10: __ D11: __ D12: __ D13: SA D14: EA D15: DA D16: DAD17: DA D18: DA D19: RF D20: R2 D21: __ D22: __ D23: __ D24: __D25: __ D26: __ D27: __ D28: __ D29: SA D30: R2 D31: DA D32: DAD33: __ D34: __ D35: __ D36: __ D37: __ D38: __ D39: __ D40: __D41: __ D42: __ D43: __ D44: __ D45: __ D46: __ D47: __ D48: __D49: __ D50: __ D51: __ D52: __ D53: __ D54: __ D55: __ D56: __D57: __ D58: __ D59: __ D60: __ D61: __ D62: __ D63: __ D64: __END OF DISPLAY

2. Issue the #SQ LINK command to verify that it is a switched configuration.

EMCMN00I SRDF-HC : (117) #SQ LINK,EC50,E EMCQL01I SRDF-HC EXTENDED DISPLAY FOR (117) #SQ LINK,EC50,E DR GP _OTHER__S/N_ OD OG RCS | %S M:SS RATE| %L DD:HH:MM:SS TOTAL-I/O 0C SW 000184501803 .. .. FYY | .. 6:59 12 | .. 19:21:04:58 13,672,690 1C SW 000184501803 .. .. FYY | .. 6:59 15 | .. 19:21:04:58 13,388,009 END OF DISPLAY

Creating a dynamic RDF pair 379

SRDF Operations

3. The #SQ RDFGRP command displays the RDF group information.

EMCMN00I SRDF-HC : (118) #SQ RDFGRP,EC50 EMCQR00I SRDF-HC DISPLAY FOR (118) #SQ RDFGRP,EC50 MY SERIAL # MY MICROCODE ------------ ------------ 000185500038 5568-44

MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR ------ --- -- ------ ------------ ------------ -------- 00 N U 00 ............ 01 N U 00 ............ 02 N U 00 ............ 03 N U 00 ............ 04 Y F 05 000184501803 5568-44 G(NONE) 05 Y F 04 000184501803 5568-44 G(NONE) END OF DISPLAY

4. Issue #SQ VOL commands to query the devices. Devices EC50 – EC5F will be changed to the R1 devices. Devices 9500 – 950F will be changed to the R2 devices. Note that because they are BCVs, they will become R2 BCVs. All normal TimeFinder operations can be performed on an R2 BCV, as well as on an R1 BCV.

EMCMN00I SRDF-HC : (110) #SQ VOL,EC50,16 EMCQV00I SRDF-HC DISPLAY FOR (110) #SQ VOL,EC50,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % EC50 50 0050 MVEC50 3339 ONPV 0 R/W ML EC51 51 0051 MVEC51 3339 ONPV 0 R/W ML EC52 52 0052 MVEC52 3339 ONPV 0 R/W ML EC53 53 0053 MVEC53 3339 ONPV 0 R/W ML EC54 54 0054 MVEC54 3339 ONPV 0 R/W ML EC55 55 0055 MVEC55 3339 ONPV 0 R/W ML EC56 56 0056 MVEC56 3339 ONPV 0 R/W ML EC57 57 0057 MVEC57 3339 ONPV 0 R/W ML EC58 58 0058 MVEC58 3339 ONPV 0 R/W ML EC59 59 0059 MVEC59 3339 ONPV 0 R/W ML EC5A 5A 005A MVEC5A 3339 ONPV 0 R/W ML EC5B 5B 005B MVEC5B 3339 ONPV 0 R/W ML EC5C 5C 005C MVEC5C 3339 ONPV 0 R/W ML EC5D 5D 005D MVEC5D 3339 ONPV 0 R/W ML EC5E 5E 005E MVEC5E 3339 ONPV 0 R/W ML EC5F 5F 005F MVEC5F 3339 ONPV 0 R/W ML END OF DISPLAY

EMCMN00I SRDF-HC : (111) #SQ VOL,9500,16 EMCQV00I SRDF-HC DISPLAY FOR (111) #SQ VOL,9500,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9500 00 0100 ?????? 3339 OFFL 0 R/W BC 9501 01 0101 ?????? 3339 OFFL 0 R/W BC 9502 02 0102 ?????? 3339 OFFL 0 R/W BC 9503 03 0103 ?????? 3339 OFFL 0 R/W BC 9504 04 0104 ?????? 3339 OFFL 0 R/W BC 9505 05 0105 ?????? 3339 OFFL 0 R/W BC 9506 06 0106 ?????? 3339 OFFL 0 R/W BC 9507 07 0107 ?????? 3339 OFFL 0 R/W BC 9508 08 0108 ?????? 3339 OFFL 0 R/W BC 9509 09 0109 ?????? 3339 OFFL 0 R/W BC


SRDF Operations

950A 0A 010A ?????? 3339 OFFL 0 R/W BC 950B 0B 010B ?????? 3339 OFFL 0 R/W BC 950C 0C 010C ?????? 3339 OFFL 0 R/W BC 950D 0D 010D ?????? 3339 OFFL 0 R/W BC 950E 0E 010E ?????? 3339 OFFL 0 R/W BC 950F 0F 010F ?????? 3339 OFFL 0 R/W BC END OF DISPLAY

5. Issue the #SC VOL command with the CREATEPAIR action. The options set to indicate the RDF mode will be adaptive copy disk and the R2s will be made not ready.

EMCMN00I SRDF-HC : (112) #SC VOL,LCL(EC50,4),CREATEPAIR(ADCOPY-DISK,NRDY),0050-005F,100EMCGM07I COMMAND COMPLETED (CMD:112)

6. Issue #SQ VOL commands to query the devices to show they are now RDF devices and RDF is active.

EMCMN00I SRDF-HC : (120) #SQ VOL,9500,16 EMCQV00I SRDF-HC DISPLAY FOR (120) #SQ VOL,9500,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9500 00 0100 0050 04 ?????? 3339 OFFL 0 N/R B2 0 40,024 20 9501 01 0101 0051 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 9502 02 0102 0052 04 ?????? 3339 OFFL 0 N/R B2 0 25,314 49 9503 03 0103 0053 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 9504 04 0104 0054 04 ?????? 3339 OFFL 0 N/R B2 0 32,178 35 9505 05 0105 0055 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 9506 06 0106 0056 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 9507 07 0107 0057 04 ?????? 3339 OFFL 0 N/R B2 0 45,348 9 9508 08 0108 0058 04 ?????? 3339 OFFL 0 N/R B2 0 45,486 9 9509 09 0109 0059 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 950A 0A 010A 005A 04 ?????? 3339 OFFL 0 N/R B2 0 33,874 32 950B 0B 010B 005B 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 950C 0C 010C 005C 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0

950D 0D 010D 005D 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0950E 0E 010E 005E 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0950F 0F 010F 005F 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0END OF DISPLAY

EMCMN00I SRDF-HC : (119) #SQ VOL,EC50,16EMCQV00I SRDF-HC DISPLAY FOR (119) #SQ VOL,EC50,16DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %EC50 50 0050 0100 05 MVEC50 3339 ONPV 0 R/W-AD L1 0 40,777 18EC51 51 0051 0101 05 MVEC51 3339 ONPV 0 R/W-AD L1 0 50,145 0EC52 52 0052 0102 05 MVEC52 3339 ONPV 0 R/W-AD L1 0 25,995 48EC53 53 0053 0103 05 MVEC53 3339 ONPV 0 R/W-AD L1 0 50,145 0EC54 54 0054 0104 05 MVEC54 3339 ONPV 0 R/W-AD L1 0 32,799 34EC55 55 0055 0105 05 MVEC55 3339 ONPV 0 R/W-AD L1 0 50,145 0EC56 56 0056 0106 05 MVEC56 3339 ONPV 0 R/W-AD L1 0 50,145 0EC57 57 0057 0107 05 MVEC57 3339 ONPV 0 R/W-AD L1 0 45,599 8EC58 58 0058 0108 05 MVEC58 3339 ONPV 0 R/W-AD L1 0 46,089 7EC59 59 0059 0109 05 MVEC59 3339 ONPV 0 R/W-AD L1 0 50,145 0EC5A 5A 005A 010A 05 MVEC5A 3339 ONPV 0 R/W-AD L1 0 34,361 31EC5B 5B 005B 010B 05 MVEC5B 3339 ONPV 0 R/W-AD L1 0 50,145 0EC5C 5C 005C 010C 05 MVEC5C 3339 ONPV 0 R/W-AD L1 0 50,145 0EC5D 5D 005D 010D 05 MVEC5D 3339 ONPV 0 R/W-AD L1 0 50,145 0


SRDF Operations

EC5E 5E 005E 010E 05 MVEC5E 3339 ONPV 0 R/W-AD L1 0 50,145 0EC5F 5F 005F 010F 05 MVEC5F 3339 ONPV 0 R/W-AD L1 0 50,145 0END OF DISPLAY

7. Issue the #SC VOL command with the RDF-SUSP action to suspend RDF for devices EC58 through EC5F.

EMCMN00I SRDF-HC : (121) #SC VOL,EC50,RDF-SUSP,58-5F EMCGM07I COMMAND COMPLETED (CMD:121)

EMCMN00I SRDF-HC : (122) #SQ VOL,EC50,16 EMCQV00I SRDF-HC DISPLAY FOR (122) #SQ VOL,EC50,16DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY

SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % EC50 50 0050 0100 05 MVEC50 3339 ONPV 0 R/W-AD L1 0 22,304 55 EC51 51 0051 0101 05 MVEC51 3339 ONPV 0 R/W-AD L1 0 41,812 16 EC52 52 0052 0102 05 MVEC52 3339 ONPV 0 R/W-AD L1 0 6,808 86 EC53 53 0053 0103 05 MVEC53 3339 ONPV 0 R/W-AD L1 0 50,145 0 EC54 54 0054 0104 05 MVEC54 3339 ONPV 0 R/W-AD L1 0 20,927 58 EC55 55 0055 0105 05 MVEC55 3339 ONPV 0 R/W-AD L1 0 50,145 0 EC56 56 0056 0106 05 MVEC56 3339 ONPV 0 R/W-AD L1 0 50,145 0 EC57 57 0057 0107 05 MVEC57 3339 ONPV 0 R/W-AD L1 0 35,477 29 EC58 58 0058 0108 05 MVEC58 3339 ONPV 0 TNR-AD L1 0 36,424 27 EC59 59 0059 0109 05 MVEC59 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5A 5A 005A 010A 05 MVEC5A 3339 ONPV 0 TNR-AD L1 0 25,028 50 EC5B 5B 005B 010B 05 MVEC5B 3339 ONPV 0 TNR-AD L1 0 46,429 7 EC5C 5C 005C 010C 05 MVEC5C 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5D 5D 005D 010D 05 MVEC5D 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5E 5E 005E 010E 05 MVEC5E 3339 ONPV 0 TNR-AD L1 0 47,525 5 EC5F 5F 005F 010F 05 MVEC5F 3339 ONPV 0 TNR-AD L1 0 50,145 0 END OF DISPLAY

8. Issue an #SC VOL command to query devices until all invalid

tracks are sent for devices EC50 thru EC57.

EMCMN00I SRDF-HC : (125) #SQ VOL,EC50,16 EMCQV00I SRDF-HC DISPLAY FOR (125) #SQ VOL,EC50,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % EC50 50 0050 0100 05 MVEC50 3339 ONPV 0 R/W-AD L1 0 0 ** EC51 51 0051 0101 05 MVEC51 3339 ONPV 0 R/W-AD L1 0 0 ** EC52 52 0052 0102 05 MVEC52 3339 ONPV 0 R/W-AD L1 0 0 ** EC53 53 0053 0103 05 MVEC53 3339 ONPV 0 R/W-AD L1 0 0 ** EC54 54 0054 0104 05 MVEC54 3339 ONPV 0 R/W-AD L1 0 0 ** EC55 55 0055 0105 05 MVEC55 3339 ONPV 0 R/W-AD L1 0 0 ** EC56 56 0056 0106 05 MVEC56 3339 ONPV 0 R/W-AD L1 0 0 ** EC57 57 0057 0107 05 MVEC57 3339 ONPV 0 R/W-AD L1 0 0 ** EC58 58 0058 0108 05 MVEC58 3339 ONPV 0 TNR-AD L1 0 36,424 27 EC59 59 0059 0109 05 MVEC59 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5A 5A 005A 010A 05 MVEC5A 3339 ONPV 0 TNR-AD L1 0 25,028 50 EC5B 5B 005B 010B 05 MVEC5B 3339 ONPV 0 TNR-AD L1 0 46,429 7 EC5C 5C 005C 010C 05 MVEC5C 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5D 5D 005D 010D 05 MVEC5D 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5E 5E 005E 010E 05 MVEC5E 3339 ONPV 0 TNR-AD L1 0 47,525 5 EC5F 5F 005F 010F 05 MVEC5F 3339 ONPV 0 TNR-AD L1 0 50,145 0 END OF DISPLAY


SRDF Operations

9. Issue an #SC VOL command with the DELETEPAIR action to delete RDF pairs for EC50 through EC57. You will receive EMCCV20E because RDF was still active.

EMCMN00I SRDF-HC : (128) #SC VOL,EC50,DELETEPAIR,0050-0057 EMCCV20E DEVICES MUST BE SUSPENDED 0050-0057 EMCCV25I NO ELIGIBLE DEVICES FOUND, COMMAND ABORTED (CMD:128)

10. Issue the #SC VOL command with the RDF-SUSP action to suspend RDF.

EMCMN00I SRDF-HC : (129) #SC VOL,EC50-EC5F,RDF-SUSP EMCGM07I COMMAND COMPLETED (CMD:129)

EMCMN00I SRDF-HC : (130) #SQ VOL,EC50,16 EMCQV00I SRDF-HC DISPLAY FOR (130) #SQ VOL,EC50,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % EC50 50 0050 0100 05 MVEC50 3339 ONPV 0 TNR-AD L1 0 0 ** EC51 51 0051 0101 05 MVEC51 3339 ONPV 0 TNR-AD L1 0 0 ** EC52 52 0052 0102 05 MVEC52 3339 ONPV 0 TNR-AD L1 0 0 ** EC53 53 0053 0103 05 MVEC53 3339 ONPV 0 TNR-AD L1 0 0 ** EC54 54 0054 0104 05 MVEC54 3339 ONPV 0 TNR-AD L1 0 0 ** EC55 55 0055 0105 05 MVEC55 3339 ONPV 0 TNR-AD L1 0 0 ** EC56 56 0056 0106 05 MVEC56 3339 ONPV 0 TNR-AD L1 0 0 ** EC57 57 0057 0107 05 MVEC57 3339 ONPV 0 TNR-AD L1 0 0 ** EC58 58 0058 0108 05 MVEC58 3339 ONPV 0 TNR-AD L1 0 36,424 27 EC59 59 0059 0109 05 MVEC59 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5A 5A 005A 010A 05 MVEC5A 3339 ONPV 0 TNR-AD L1 0 25,028 50 EC5B 5B 005B 010B 05 MVEC5B 3339 ONPV 0 TNR-AD L1 0 46,429 7 EC5C 5C 005C 010C 05 MVEC5C 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5D 5D 005D 010D 05 MVEC5D 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5E 5E 005E 010E 05 MVEC5E 3339 ONPV 0 TNR-AD L1 0 47,525 5 EC5F 5F 005F 010F 05 MVEC5F 3339 ONPV 0 TNR-AD L1 0 50,145 0 END OF DISPLAY

11. Re-issue the #SC VOL command with the DELETEPAIR action. Notice in the last queries that R1s are now standard devices and R2s are now BCVs.

EMCMN00I SRDF-HC : (131) #SC VOL,EC50,DELETEPAIR,0050-0057 EMCGM07I COMMAND COMPLETED (CMD:131)

EMCMN00I SRDF-HC : (132) #SQ VOL,EC50,16 EMCQV00I SRDF-HC DISPLAY FOR (132) #SQ VOL,EC50,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % EC50 50 0050 MVEC50 3339 ONPV 0 R/W ML EC51 51 0051 MVEC51 3339 ONPV 0 R/W ML EC52 52 0052 MVEC52 3339 ONPV 0 R/W ML EC53 53 0053 MVEC53 3339 ONPV 0 R/W ML EC54 54 0054 MVEC54 3339 ONPV 0 R/W ML EC55 55 0055 MVEC55 3339 ONPV 0 R/W ML EC56 56 0056 MVEC56 3339 ONPV 0 R/W ML EC57 57 0057 MVEC57 3339 ONPV 0 R/W ML EC58 58 0058 0108 05 MVEC58 3339 ONPV 0 TNR-AD L1 0 36,424 27 EC59 59 0059 0109 05 MVEC59 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5A 5A 005A 010A 05 MVEC5A 3339 ONPV 0 TNR-AD L1 0 25,028 50 EC5B 5B 005B 010B 05 MVEC5B 3339 ONPV 0 TNR-AD L1 0 46,429 7


SRDF Operations

EC5C 5C 005C 010C 05 MVEC5C 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5D 5D 005D 010D 05 MVEC5D 3339 ONPV 0 TNR-AD L1 0 50,145 0 EC5E 5E 005E 010E 05 MVEC5E 3339 ONPV 0 TNR-AD L1 0 47,525 5 EC5F 5F 005F 010F 05 MVEC5F 3339 ONPV 0 TNR-AD L1 0 50,145 0 END OF DISPLAY

EMCMN00I SRDF-HC : (133) #SQ VOL,9500,16 EMCQV00I SRDF-HC DISPLAY FOR (133) #SQ VOL,9500,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9500 00 0100 ?????? 3339 OFFL 0 R/W BC 9501 01 0101 ?????? 3339 OFFL 0 R/W BC 9502 02 0102 ?????? 3339 OFFL 0 R/W BC 9503 03 0103 ?????? 3339 OFFL 0 R/W BC 9504 04 0104 ?????? 3339 OFFL 0 R/W BC 9505 05 0105 ?????? 3339 OFFL 0 R/W BC 9506 06 0106 ?????? 3339 OFFL 0 R/W BC 9507 07 0107 ?????? 3339 OFFL 0 R/W BC 9508 08 0108 0058 04 ?????? 3339 OFFL 0 N/R B2 0 36,424 27 9509 09 0109 0059 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 950A 0A 010A 005A 04 ?????? 3339 OFFL 0 N/R B2 0 25,028 50 950B 0B 010B 005B 04 ?????? 3339 OFFL 0 N/R B2 0 46,429 7 950C 0C 010C 005C 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 950D 0D 010D 005D 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 950E 0E 010E 005E 04 ?????? 3339 OFFL 0 N/R B2 0 47,525 5 950F 0F 010F 005F 04 ?????? 3339 OFFL 0 N/R B2 0 50,145 0 END OF DISPLAY

12. Issue the #SC VOL command with the DELETEPAIR action to devices EC58 thru EC5F. However; because of invalid tracks owed to the R2, an EMCCVE5W warning is received and the command is aborted.

EMCMN00I SRDF-HC : (134) #SC VOL,EC50,DELETEPAIR,0058-005A EMCCVE5W DELETEPAIR: R1 INDICATES DATA OWED TO THE R2 0108-010A EMCGM10I COMMAND ABORTED (CMD:134)

13. Issue the #SC VOL command with the DELETEPAIR action to devices EC58 thru EC5F, this time with the FORCE option. You will continue to receive EMCCVE5W warnings because there are tracks owed, but the command is successful. The last queries show that devices are set as they were in step 4.

EMCMN00I SRDF-HC : (135) #SC VOL,EC50,DELETEPAIR(FORCE),0058-005F EMCCVE5W DELETEPAIR: R1 INDICATES DATA OWED TO THE R2 0108-010F EMCGM07I COMMAND COMPLETED (CMD:135)

EMCMN00I SRDF-HC : (136) #SQ VOL,EC50,16 EMCQV00I SRDF-HC DISPLAY FOR (136) #SQ VOL,EC50,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % EC50 50 0050 MVEC50 3339 ONPV 0 R/W ML EC51 51 0051 MVEC51 3339 ONPV 0 R/W ML EC52 52 0052 MVEC52 3339 ONPV 0 R/W ML EC53 53 0053 MVEC53 3339 ONPV 0 R/W ML EC54 54 0054 MVEC54 3339 ONPV 0 R/W ML EC55 55 0055 MVEC55 3339 ONPV 0 R/W ML


SRDF Operations

EC56 56 0056 MVEC56 3339 ONPV 0 R/W ML EC57 57 0057 MVEC57 3339 ONPV 0 R/W ML EC58 58 0058 MVEC58 3339 ONPV 0 R/W ML EC59 59 0059 MVEC59 3339 ONPV 0 R/W ML EC5A 5A 005A MVEC5A 3339 ONPV 0 R/W ML EC5B 5B 005B MVEC5B 3339 ONPV 0 R/W ML EC5C 5C 005C MVEC5C 3339 ONPV 0 R/W ML EC5D 5D 005D MVEC5D 3339 ONPV 0 R/W ML EC5E 5E 005E MVEC5E 3339 ONPV 0 R/W ML EC5F 5F 005F MVEC5F 3339 ONPV 0 R/W ML END OF DISPLAY

EMCMN00I SRDF-HC : (137) #SQ VOL,9500,16 EMCQV00I SRDF-HC DISPLAY FOR (137) #SQ VOL,9500,16 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9500 00 0100 ?????? 3339 OFFL 0 R/W BC 9501 01 0101 ?????? 3339 OFFL 0 R/W BC 9502 02 0102 ?????? 3339 OFFL 0 R/W BC 9503 03 0103 ?????? 3339 OFFL 0 R/W BC 9504 04 0104 ?????? 3339 OFFL 0 R/W BC 9505 05 0105 ?????? 3339 OFFL 0 R/W BC 9506 06 0106 ?????? 3339 OFFL 0 R/W BC 9507 07 0107 ?????? 3339 OFFL 0 R/W BC 9508 08 0108 ?????? 3339 OFFL 0 R/W BC 9509 09 0109 ?????? 3339 OFFL 0 R/W BC 950A 0A 010A ?????? 3339 OFFL 0 R/W BC 950B 0B 010B ?????? 3339 OFFL 0 R/W BC 950C 0C 010C ?????? 3339 OFFL 0 R/W BC 950D 0D 010D ?????? 3339 OFFL 0 R/W BC 950E 0E 010E ?????? 3339 OFFL 0 R/W BC 950F 0F 010F ?????? 3339 OFFL 0 R/W BC END OF DISPLAY

Creating an RDF group 385

SRDF Operations

Creating an RDF groupThe following example demonstrates how to create an RDF group.

1. Find the serial number of the remote Symmetrix using the #SQ CNFG,cuu command (or #SQ CNFG,RMT(cuu) ).

EMCGM11I SRDF-HC DISPLAY FOR (43) #SQ CNFG,9680 SERIAL NUMBER: 000187990132 MEM:32,768 MB TYPE:2105 MODEL: DMX800 MICROCODE LEVEL: 5671-20 CONCURRENT-RDF CONCURRENT DRDF: YES SWITCHED-RDF DYNAMIC-RDF NO-AUTO-LINKS RDFGRP LINKS-OFF-ON-POWERUP LINKS-DOMINO: RDFGRP SYNCH_DIRECTION: GLOBAL LINK: LOCAL SSID(S): 9600 9601 0001 0140 0141 D01: DF D02: EF D03: __ D04: __ D05: __ D06: __ D07: __ D08: __ D09: __ D10: __ D11: __ D12: __ D13: __ D14: __ D15: EF D16: DF D17: DF D18: __ D19: __ D20: __ D21: __ D22: __ D23: __ D24: __ D25: __ D26: __ D27: __ D28: __ D29: __ D30: __ D31: __ D32: DF D33: SF D34: __ D35: __ D36: __ D37: __ D38: __ D39: __ D40: __ D41: __ D42: __ D43: __ D44: __ D45: __ D46: __ D47: __ D48: SF D49: RF D50: RE D51: __ D52: __ D53: __ D54: __ D55: __ D56: __ D57: __ D58: __ D59: __ D60: __ D61: __ D62: __ D63: RE D64: RF END OF DISPLAY

2. Obtain the link director numbers for both the remote and local systems using the #SQ LINK,cuu and the #SQ LINK,RMT(cuu) commands.

Note: Multiple directors can be selected and specified in the command. “Modifying an RDF group” on page 388 provides more information.

EMCQL00I SRDF-HC DISPLAY FOR (46) #SQ LINK,6D50 CUU_ DIR RA P CONN _STATUS_ MM:SS I/O-RATE DDD:HH:MM:SS _TOTAL-I/O_ 6D50 33 RF 1 Y ONLINE 04:17 2 000:15:25:15 409,986 6D50 3E RF 1 Y ONLINE 04:18 2 000:15:25:15 281,568 END OF DISPLAY

EMCQL00I SRDF-HC DISPLAY FOR (47) #SQ LINK,RMT(6D50,01) CUU_ DIR RA P CONN _STATUS_ MM:SS I/O-RATE DDD:HH:MM:SS _TOTAL-I/O_ 6D50 31 RF 1 Y ONLINE 07:20 27 000:18:35:31 1,557,176 6D50 32 RE 1 Y ONLINE 07:16 0 000:18:35:43 29,709 6D50 3F RE 1 Y ONLINE 07:16 0 000:18:35:39 29,588 6D50 40 RF 1 Y ONLINE 07:19 10 000:18:35:31 727,387 END OF DISPLAY


SRDF Operations

3. Select an RDFGRP group number that is not already being used on both the local and the remote boxes. Use the #SQ RDFGRP,cuu command and the #SQ RDFGRP,RMT(cuu) command to see which numbers are being used.

EMCQR00I SRDF-HC DISPLAY FOR (48) #SQ RDFGRP,6D50 MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 01 Y F 32 000187990132 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 10 Y F 05 000187990132 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO END OF DISPLAY

EMCMN00I SRDF-HC : (49) #SQ RDFGRP,RMT(6D50,01) EMCQR00I SRDF-HC DISPLAY FOR (49) #SQ RDFGRP,RMT(6D50,01) 375 MY SERIAL # MY MICROCODE ------------ ------------ 000187990132 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 05 Y F 10 000000006185 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 11 Y I 10 000187990175 5670-73 G(R1>R2) GIGEB2C STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 12 Y I 13 000187990171 5670-71 G(R1>R2) GIGEC2D STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 32 Y F 01 000000006185 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO END OF DISPLAY

4. Select a label name (any 8 characters) and build the command.

#SC RDFGRP,cuu,lclrdfgrp,ADD,LDIR(##),RDIR(##),RSER(############),RGRP(##),LABEL(XXXXXXXX)

Or, from the displays above:

EMCMN00I SRDF-HC : (17) #SC RDFGRP,6D50,14,ADD,LDIR(33),RDIR(31),RSER(000187990132),RGRP(17),LABEL(MSF71) EMCGM07I COMMAND COMPLETED (CMD:17) EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:17)

Creating an RDF group 387

SRDF Operations

5. Build the RDF group on multiple directors:

#SC RDFGRP,cuu,lclrdfgrp,ADD,LDIR(##,##),RDIR(##,##),RSER(############),RGRP(##),LABEL(XXXXXXXX)

EMCMN00I SRDF-HC : (55) #SC RDFGRP,6D50,14,ADD,LDIR(33,3E),RDIR(31,40),RGRP(17),RSER(000187990132),LABEL(MSF71) EMCGM07I COMMAND COMPLETED (CMD:55) EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:55)

6. Issue #SQ RDFGRP,cuu to see the newly created group:

EMCMN00I SRDF-HC : (50) #SQ RDFGRP,6D50 EMCQR00I SRDF-HC DISPLAY FOR (50) #SQ RDFGRP,6D50 859 MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 01 Y F 32 000187990132 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 10 Y F 05 000187990132 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 14 Y F 17 000187990132 5671-00 G(R1>R2) MSF71 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO END OF DISPLAY

EMCQR00I SRDF-HC DISPLAY FOR (51) #SQ RDFGRP,RMT(6D50,01) 867 MY SERIAL # MY MICROCODE ------------ ------------ 000187990132 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 05 Y F 10 000000006185 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 11 Y I 10 000187990175 5670-73 G(R1>R2) GIGEB2C STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 12 Y I 13 000187990171 5670-71 G(R1>R2) GIGEC2D STATIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 17 Y F 14 000000006185 5671-00 G(R1>R2) MSF71 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO 32 Y F 01 000000006185 5671-00 G(R1>R2) RDFDVGROUP STATIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO END OF DISPLAY


SRDF Operations

Modifying an RDF groupYou can modify, add, or delete director numbers.

1. Issue command #SQ RDFGRP,cuu,RA(#).

EMCQR00I SRDF-HC DISPLAY FOR (57) #SQ RDFGRP,6D50,RA(23) MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 23 Y F 23 000187990132 5671-00 G(R1>R2) MSF712 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ----------------

33 30 02 5006048800060A52000000000008FBF8000000000002C538 000000000008FBF8000000000002C538

END OF DISPLAY

2. Issue the #SC RDFGRP command with the MODIFY action to add another director to the group.

EMCMN00I SRDF-HC : (58) #SC RDFGRP,6D50,23,MODIFY,LDIR(+3E),RDIR(+40)EMCGM07I COMMAND COMPLETED (CMD:58) EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:58)

3. Issue the #SQ RDFGRP,cuu,RA(xx) command to see the change. Note that the other side director number is one less than what is actually specified.

EMCQR00I SRDF-HC DISPLAY FOR (59) #SQ RDFGRP,6D50,RA(23) MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 23 Y F 23 000187990132 5671-00 G(R1>R2) MSF712 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ----------------

33 30 02 5006048800060A5200000000000DAE200000000000035280 3F 02 000000000002934800000000000105C8

00000000001041680000000000045848

3E 3F 02 5006048800060A5D00000000000189E800000000000080D0 30 02 00000000000105680000000000008888

0000000000028F500000000000010958 END OF DISPLAY

Modifying an RDF group 389

SRDF Operations

4. You can also remove director numbers by issuing the #SC RDFGRP command with the MODIFY action.

EMCMN00I SRDF-HC : (60) #SC RDFGRP,6D50,23,MODIFY,LDIR(-3E),RDIR(-40) EMCGM07I COMMAND COMPLETED (CMD:60) EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:60) EMCMN00I SRDF-HC : (61) #SQ RDFGRP,6D50,RA(23) EMCQR00I SRDF-HC DISPLAY FOR (61) #SQ RDFGRP,6D50,RA(23) 754 MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-00 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO ---------- ------- ---------------------- ---------------- 23 Y F 23 000187990132 5671-00 G(R1>R2) MSF712 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ----------------

33 30 02 5006048800060A52000000000010C9E00000000000035A80 000000000010C9E00000000000035A80

END OF DISPLAY

5. SRDF batch can be set up to run this as needed as follows.

//EMCSRDF EXEC PGM=EMCSRDF //STEPLIB DD DSN=YOUR.SRDF.LINKLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * #SQ RDFGRP,6D50 #SC RDFGRP,6D50,17,ADD,LDIR(33),RDIR(31),RSER(000187990132), - LABEL(MSF71),RGRP(14) #SQ RDFGRP,6D50 #SQ V,6D50


SRDF Operations

Performing Cascaded SRDF operationsThis example demonstrates how to perform Cascaded SRDF operations. The environment in this scenario is as follows:

Note: There is no required order for the creation of synchronous and asynchronous RDF groups. Your displays may vary from those shown in this example.

1. Issue the #SC RDFGRP command with the ADD action to create an RDF group between site A and site B.

EMCMN00I SRDF-HC : (16) &SC RDFGRP,9E00,04,ADD,LDIR(28,38),RDIR(28,38),LABEL(TSTCAS1),RSER(000190100849),RGRP(44)

EMCGM07I COMMAND COMPLETED (CMD:16) EMCGM40I COMMAND HAS FINISHED FOR BOX 000190103387 (CMD:16)

EMCMN00I SRDF-HC : (31) &SQ RDFGRP,9E00,RA(04) EMCQR00I SRDF-HC DISPLAY FOR (31) &SQ RDFGRP,9E00,RA(04) 131 MY SERIAL # MY MICROCODE ------------ ------------ 000190103387 5773-43 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- 04 Y F 44 000190100849 5773-43 G(R1>R2) TSTCAS1 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ---------------- 28 37 02 5006048AD52FD6C7 0000000000DF8548 00000000012BAF18 27 02 0000000000BAAF50 000000000125E680 00000000019A3498 0000000002519598 38 37 02 5006048AD52FD6D7 00000000009CE198 00000000012AE000 27 02 0000000000914580 00000000012E4B00 00000000012E2718 0000000002592B00 END OF DISPLAY

Site A Site B Site C

9E00 Symmetrix serial# 000190103387

4200Symmetrix serial # 000190100849

9A00 Symmetrix serial# 000190300344

Performing Cascaded SRDF operations 391

SRDF Operations

2. Issue the #SC RDFGRP command with the ADD action to create an RDF group between site B and site C.

EMCMN00I SRDF-HC : (4) &SC RDFGRP,RMT(9E00,04),54,ADD,LDIR(28),RDIR(40),LABEL(TSTCAS2),RSER(000190300344),RGRP(64)

EMCGM07I COMMAND COMPLETED (CMD:4) EMCGM40I COMMAND HAS FINISHED FOR BOX 000190103387 (CMD:4)

EMCMN00I SRDF-HC : (24) &SQ RDFGRP,RMT(9E00,04),RA(54) EMCQR00I SRDF-HC DISPLAY FOR (24) &SQ RDFGRP,RMT(9E00,04),RA(54) 871 MY SERIAL # MY MICROCODE ------------ ------------ 000190100849 5773-43 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- 54 Y F 64 000190300344 5772-83 G(R1>R2) TSTCAS2 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO MY DIR# OS RA# ST -----MY WWN----- ----IN COUNT---- ---OUT COUNT---- ------- ------ -- ---------------- ---------------- ---------------- 28 3F 02 5006048AD52D5C47 0000000000030298 00000000000080E8 0000000000030298 00000000000080E8 END OF DISPLAY

3. Create pairs from site A to site B.

EMCMN00I SRDF-HC : (26) &SQ VOL,9E00,8,50 EMCQV00I SRDF-HC DISPLAY FOR (26) &SQ VOL,9E00,8,50 053 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E30 30 0050 OFFLIN 3339 OFFL 0 R/W 9E31 31 0051 OFFLIN 3339 OFFL 0 R/W 9E32 32 0052 OFFLIN 3339 OFFL 0 R/W 9E33 33 0053 OFFLIN 3339 OFFL 0 R/W 9E34 34 0054 OFFLIN 3339 OFFL 0 R/W 9E35 35 0055 OFFLIN 3339 OFFL 0 R/W 9E36 36 0056 OFFLIN 3339 OFFL 0 R/W 9E37 37 0057 OFFLIN 3339 OFFL 0 R/W END OF DISPLAY EMCMN00I SRDF-HC : (27) &SQ VOL,RMT(9E00,04),8,B0 EMCQV00I SRDF-HC DISPLAY FOR (27) &SQ VOL,RMT(9E00,04),8,B0 057 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4290 90 00B0 OFFLIN 3339 OFFL 0 R/W 4291 91 00B1 OFFLIN 3339 OFFL 0 R/W 4292 92 00B2 OFFLIN 3339 OFFL 0 R/W 4293 93 00B3 OFFLIN 3339 OFFL 0 R/W 4294 94 00B4 OFFLIN 3339 OFFL 0 R/W 4295 95 00B5 OFFLIN 3339 OFFL 0 R/W 4296 96 00B6 OFFLIN 3339 OFFL 0 R/W 4297 97 00B7 OFFLIN 3339 OFFL 0 R/W END OF DISPLAY


SRDF Operations

EMCMN00I SRDF-HC : (29) &SC VOL,LCL(9E00,04),CREATEPAIR,50-57,B0 EMCGM40I COMMAND HAS FINISHED FOR BOX 000190103387 (CMD:29) EMCGM41I REQUESTED DEVICES 118 0050-0057 EMCGM42I ELIGIBLE DEVICES 119 0050-0057 EMCGM43I COMPLETED DEVICES 120 0050-0057 EMCGM07I COMMAND COMPLETED (CMD:29)

EMCMN00I SRDF-HC : (32) &SQ VOL,9E00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (32) &SQ VOL,9E00,RA(04) 139 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E30 30 0050 00B0 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 10,453 79 9E31 31 0051 00B1 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 2,320 95 9E32 32 0052 00B2 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 785 98 9E33 33 0053 00B3 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 8,953 82 9E34 34 0054 00B4 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 8,981 82 9E35 35 0055 00B5 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 5,121 89 9E36 36 0056 00B6 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 2,719 94 9E37 37 0057 00B7 04 OFFLIN 3339 OFFL 0 R/W-SY R1 0 5,369 89 END OF DISPLAY EMCMN00I SRDF-HC : (33) &SQ VOL,RMT(9E00,04),RA(44) EMCQV00I SRDF-HC DISPLAY FOR (33) &SQ VOL,RMT(9E00,04),RA(44) 142 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4290 90 00B0 0050 44 OFFLIN 3339 OFFL 0 N/R R2 0 6,238 87 4291 91 00B1 0051 44 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4292 92 00B2 0052 44 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4293 93 00B3 0053 44 OFFLIN 3339 OFFL 0 N/R R2 0 4,497 91 4294 94 00B4 0054 44 OFFLIN 3339 OFFL 0 N/R R2 0 5,269 89 4295 95 00B5 0055 44 OFFLIN 3339 OFFL 0 N/R R2 0 1,531 96 4296 96 00B6 0056 44 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4297 97 00B7 0057 44 OFFLIN 3339 OFFL 0 N/R R2 0 823 98 END OF DISPLAY

4. Create pairs from site B to site C using the wrong mode (that is, a mode other than ADCOPY-DISK). The EMCCV50I message indicates the incorrect mode was specified.

EMCMN00I SRDF-HC : (34) &SC VOL,RMT(9E00,04,54),CREATEPAIR,B0-B7,A0 EMCCV50I CREATEPAIR 00B0-00A0(0008) R1 OF R21 IN WRONG RDF MODE 000190100849/00B0/00B0 EMCGM10I COMMAND ABORTED (CMD:34)

Performing Cascaded SRDF operations 393

SRDF Operations

5. Create pairs from site B to site C with ADCOPY-DISK mode.

EMCMN00I SRDF-HC : (35) &SC VOL,RMT(9E00,04,54),CREATEPAIR(ADCOPY-DISK),B0-B7,A0 EMCGM40I COMMAND HAS FINISHED FOR BOX 000190100849 (CMD:35) EMCGM41I REQUESTED DEVICES 158 00B0-00B7 EMCGM42I ELIGIBLE DEVICES 159 00B0-00B7 EMCGM43I COMPLETED DEVICES 160 00B0-00B7 EMCGM07I COMMAND COMPLETED (CMD:35) EMCMN00I SRDF-HC : (36) &SQ VOL,RMT(9E00,04),8,B0 EMCQV00I SRDF-HC DISPLAY FOR (36) &SQ VOL,RMT(9E00,04),8,B0 251 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4290 90 00B0 0050 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A0 54 OFFLIN 3339 OFFL 0 CAS-AD L1 31,340 37 4291 91 00B1 0051 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A1 54 OFFLIN 3339 OFFL 0 CAS-AD L1 32,416 35 4292 92 00B2 0052 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A2 54 OFFLIN 3339 OFFL 0 CAS-AD L1 33,228 33 4293 93 00B3 0053 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A3 54 OFFLIN 3339 OFFL 0 CAS-AD L1 33,893 32 4294 94 00B4 0054 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A4 54 OFFLIN 3339 OFFL 0 CAS-AD L1 0 ** 4295 95 00B5 0055 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A5 54 OFFLIN 3339 OFFL 0 CAS-AD L1 0 ** 4296 96 00B6 0056 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A6 54 OFFLIN 3339 OFFL 0 CAS-AD L1 0 ** 4297 97 00B7 0057 44 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 00A7 54 OFFLIN 3339 OFFL 0 CAS-AD L1 0 ** END OF DISPLAY

EMCMN00I SRDF-HC : (37) &SQ VOL,RMT(9E00,04.54),8,A0 EMCQV00I SRDF-HC DISPLAY FOR (37) &SQ VOL,RMT(9E00,04.54),8,A0 279 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9A80 80 00A0 00B0 64 OFFLIN 3339 OFFL 0 N/R R2 0 26,668 46 9A81 81 00A1 00B1 64 OFFLIN 3339 OFFL 0 N/R R2 0 28,855 42 9A82 82 00A2 00B2 64 OFFLIN 3339 OFFL 0 N/R L2 0 29,955 40 9A83 83 00A3 00B3 64 OFFLIN 3339 OFFL 0 N/R L2 0 29,819 40 9A84 84 00A4 00B4 64 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 9A85 85 00A5 00B5 64 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 9A86 86 00A6 00B6 64 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** 9A87 87 00A7 00B7 64 OFFLIN 3339 OFFL 0 N/R L2 0 0 ** END OF DISPLAY


SRDF Operations

Performing Cascaded SRDF operations (diskless)Starting with SRDF Host Component V7.0, new actions available with the SC VOL command allow you to manage 3-site Cascaded SRDF operations with a single command. These SC VOL command actions are:

◆ CASCRE - creates a cascaded configuration

◆ CASSUSP - suspends pairs in a cascaded configuration

◆ CASRSUM - resumes pairs in a cascaded configuration

◆ CASDEL - terminates relationships in a cascaded configuration

◆ CASSWAP - performs SRDF personality swap on both device pairs

For a diskless devices, these CAS actions must be used to manage the environment. For non-diskless devices, the single CREATEPAIR, DELETEPAIR, and SWAP actions may be used, but the CAS actions make the management easier.

Note: The SC VOL CAS actions must be issued from either site A or site C. There is no remote support for the CAS actions.

1. The CASCRE action will build the 3-site Cascaded SRDF environment. Specify the two RDF groups in the cascaded configuration, and the Symmetrix device numbers in all three arrays:

SC VOL,LCL(cuu,ra1,ra2),CASCRE,adev#1-adev#2,bdev#1,cdev#1

Where:

◆ ra1 is the RDF group between the site A array and the site B array

◆ ra2 is the RDF group between the site B array and the site C array

◆ adev#1-adev#2 is a contiguous range of devices in the site A array

◆ bdev#1 is the starting device number of a range of contiguous devices in the site B array

◆ cdev#1 is the starting device number of a range of contiguous devices in the site C array


SRDF Operations

Moving dynamic SRDF pairsThis example demonstrates how to move dynamic SRDF device pairs using the #SC VOL command with the MOVEPAIR action. This command allows movement of devices between SRDF groups without full resynchronization.

Note: If a device pair is in a consistency group, it can not be moved out of the group, even though the consistency group is tripped (that is, in the TNR state). In this case, an error message similar to the following will be issued and the consistency group must be disabled:

SRDF-HC : (14) &SC VOL,LCL(9E20,49),MOVEPAIR,40,4AMOVEPAIR 0040-0040(0001) DEVICE IN CGROUP 000190103387/0041/0050 (CMD:14) COMMAND ABORTED (CMD:14)

The #SC VOL MOVEPAIR command syntax is as follows:

SC VOL,LCL(gggg,from-RDF-group),MOVEPAIR,dev-range,to-RDF-groupSC VOL,RMT(gggg,hop-list,from-RDF-group),MOVEPAIR,dev-range,to-RDF-group

In the procedure described in the following steps, device 35 is moved from group 49 to group 4A.

1. The following #SQ VOL display illustrates the receiving R1 SRDF/A group 4A (no device 35 exists).

EMCQV00I SRDF-HC DISPLAY FOR (41) &SQ VOL,9E00,RA(4A) 272 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E10 10 0030 0030 4A UAC00G 3339 ONPV 0 R/W-AS A1 0 0 ** 9E11 11 0031 0031 4A UAC00H 3339 ONPV 0 R/W-AS A1 0 0 ** ???? ?? 090B 090B 4A OFFLIN 1113 N/A 0 R/W-AS L1 0 0 ** ???? ?? 090C 090C 4A OFFLIN 1113 N/A 0 R/W-AS L1 0 0 ** ???? ?? 090D 090D 4A OFFLIN 1113 N/A 0 R/W-AS L1 0 0 ** END OF DISPLAY

Moving dynamic SRDF pairs 403

SRDF Operations

2. The following #SQ VOL display illustrates the receiving R2 SRDF/A group 0A (no device 35 exists).

EMCMN00I SRDF-HC : (42) &SQ VOL,4200,RA(0A) EMCQV00I SRDF-HC DISPLAY FOR (42) &SQ VOL,4200,RA(0A) 276 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4210 10 0030 0030 0A OFFLIN 3339 OFFL 0 N/R A2 0 0 ** 4211 11 0031 0031 0A OFFLIN 3339 OFFL 0 N/R A2 0 0 ** 4213 13 0033 0033 0A OFFLIN 3339 OFFL 0 N/R A2 0 0 ** ???? ?? 090B 090B 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** ???? ?? 090C 090C 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** ???? ?? 090D 090D 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** END OF DISPLAY

3. As shown in the following display, #SQ SRDFA receiving group 4A is active. It needs to be made inactive.

EMCMN00I SRDF-HC : (43) &SQ SRDFA,LCL(9E00,4A) EMCQR00I SRDF-HC DISPLAY FOR (43) &SQ SRDFA,LCL(9E00,4A) 280 MY SERIAL # MY MICROCODE ------------ ------------ 000190103387 5773-46 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- 4A Y F 0A 000190100849 5773-46 G(R1>R2) SRDFA ACTIVE MFAC2ADA DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO ---------------------------------------------------------------------- PRIMARY SIDE: CYCLE NUMBER 3 MIN CYCLE TIME 30 SECONDARY CONSISTENT ( Y ) TOLERANCE ( N ) CAPTURE CYCLE SIZE 0 TRANSMIT CYCLE SIZE 0 AVERAGE CYCLE TIME 61 AVERAGE CYCLE SIZE 0 TIME SINCE LAST CYCLE SWITCH 1 DURATION OF LAST CYCLE 31 MAX THROTTLE TIME 0 MAX CACHE PERCENTAGE 94 HA WRITES 976,240 RPTD HA WRITES 861,065 HA DUP. SLOTS 1,617 SECONDARY DELAY 32 LAST CYCLE SIZE 0 DROP PRIORITY 33 CLEANUP RUNNING ( N ) MSC WINDOW IS OPEN ( N ) SRDF/A TRANSMIT IDLE ( Y ) SRDF/A DSE ACTIVE ( N ) MSC ACTIVE ( N ) ---------------------------------------------------------------------- END OF DISPLAY

4. The following error will be returned if the #SC VOL command with the MOVEPAIR action is issued to a target RDF group that is in SRDF/A mode:

EMCMN00I SRDF-HC : (17) &SC VOL,LCL(9E00,49),MOVEPAIR,30,4A EMCCV6FE MOVEPAIR denied, SRDF/A active on target RDF group 4A (CMD:17) EMCGM10I COMMAND ABORTED (CMD:17)


SRDF Operations

5. Stop SRDF/A by issuing the #SC SRDFA command with the PENDDROP action.

EMCMN00I SRDF-HC : (49) &SC SRDFA,LCL(9E00,4A),PENDDROP EMCCR10I STARTING WAIT FOR SRDF/A CYCLE SWITCH (CMD:49) EMCCR11I END OF WAIT FOR SRDF/A CYCLE SWITCH (CMD:49) EMCGM07I COMMAND COMPLETED (CMD:49) EMCGM40I COMMAND HAS FINISHED FOR BOX 000190103387 (CMD:49) EMCMN00I SRDF-HC : (50) &SQ SRDFA,LCL(9E00,4A) EMCQR06E QUERY FOR SRDF/A - SRDF/A NOT FOUND (CMD:50)

EMCMN00I SRDF-HC : (53) &SQ SRDFA,LCL(4200,0A) EMCQR06E QUERY FOR SRDF/A - SRDF/A NOT FOUND (CMD:53)

6. The following #SQ VOL display shows the receiving group 4A R1 side after the PENDDROP operation.

EMCMN00I SRDF-HC : (51) &SQ VOL,9E00,RA(4A) EMCQV00I SRDF-HC DISPLAY FOR (51) &SQ VOL,9E00,RA(4A) 375 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E10 10 0030 0030 4A UAC00G 3339 ONPV 0 TNR-SY R1 0 0 ** 9E11 11 0031 0031 4A UAC00H 3339 ONPV 0 TNR-SY R1 0 0 ** ???? ?? 090B 090B 4A OFFLIN 1113 N/A 0 TNR-SY L1 0 0 ** ???? ?? 090C 090C 4A OFFLIN 1113 N/A 0 TNR-SY L1 0 0 ** ???? ?? 090D 090D 4A OFFLIN 1113 N/A 0 TNR-SY L1 0 0 ** END OF DISPLAY

7. The following #SQ VOL display shows the receiving group 0A R2 side after the PENDDROP operation.

EMCMN00I SRDF-HC : (52) &SQ VOL,4200,RA(0A) EMCQV00I SRDF-HC DISPLAY FOR (52) &SQ VOL,4200,RA(0A) 378 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4210 10 0030 0030 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4211 11 0031 0031 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4213 13 0033 0033 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** ???? ?? 090B 090B 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** ???? ?? 090C 090C 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** ???? ?? 090D 090D 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** END OF DISPLAY

8. The following #SQ VOL display shows the device to be moved (group 49 device 35) from the R1 side.

EMCQV00I SRDF-HC DISPLAY FOR (46) &SQ VOL,9E00,RA(49) 291 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E12 12 0032 0032 49 UAC00I 3339 ONPV 0 R/W-SY R1 0 0 ** 9E13 13 0033 0033 49 UAC00J 3339 ONPV 0 TNR-AD R1 0 0 ** 9E14 14 0034 0034 49 UAC00K 3339 ONPV 0 TNR-AD R1 0 0 ** 9E15 15 0035 0035 49 UAC00L 3339 ONPV 0 TNR-SY R1 0 0 ** 9E16 16 0036 0036 49 UAC00M 3339 ONPV 0 TNR-SY R1 0 0 **


SRDF Operations

12. The following #SQ VOL display screens show receiving groups 49 and 09 with device 35 removed after the MOVEPAIR operation. The Symmetrix device number is no longer associated with the source RDF groups.

EMCMN00I SRDF-HC : (57) &SQ VOL,9E00,RA(49) EMCQV00I SRDF-HC DISPLAY FOR (57) &SQ VOL,9E00,RA(49) 412 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E12 12 0032 0032 49 UAC00I 3339 ONPV 0 R/W-SY R1 0 0 ** 9E13 13 0033 0033 49 UAC00J 3339 ONPV 0 TNR-AD R1 0 0 ** 9E14 14 0034 0034 49 UAC00K 3339 ONPV 0 TNR-AD R1 0 0 ** 9E16 16 0036 0036 49 UAC00M 3339 ONPV 0 TNR-SY R1 0 0 ** 9E17 17 0037 0037 49 UAC00N 3339 ONPV 0 TNR-SY R1 0 0 ** 9E18 18 0038 0038 49 UAC00O 3339 ONPV 0 TNR-SY R1 0 0 **

EMCMN00I SRDF-HC : (58) &SQ VOL,4200,RA(09) EMCQV00I SRDF-HC DISPLAY FOR (58) &SQ VOL,4200,RA(09) 418 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4212 12 0032 0032 09 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4214 14 0034 0034 09 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4216 16 0036 0036 09 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4217 17 0037 0037 09 OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4218 18 0038 0038 09 OFFLIN 3339 OFFL 0 N/R R2 0 0 **

13. Issue the #SC VOL command with the RDF-RSUM action to the devices in the target RDF group.

EMCMN00I SRDF-HC : (59) &SC VOL,LCL(9E00,4A),RDF-RSUM,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 422 0020-002F,0032-0034,0036-090A,090E-14A7,14AA-14BF,14E0-155F, 1640-169F EMCCVAFI NO AVAILABLE LINKS FOR THE FOLLOWING DEVICES 423 0032-0034,0036-0057,0060-006F,00D0-00D7,0140-0152,0154-015F, 0170-0173,0178-017B,04D1-04D2,0909-090A,0E50-0E5F,14AA-14AF EMCGM40I COMMAND HAS FINISHED FOR BOX 000190103387 (CMD:59) EMCGM41I REQUESTED DEVICES 425 0030-0031,0035,090B-090D EMCGM42I ELIGIBLE DEVICES 426 0030-0031,0035,090B-090D EMCGM43I COMPLETED DEVICES 427 0030-0031,0035,090B-090D EMCGM07I COMMAND COMPLETED (CMD:59)

14. The following #SQ VOL display shows the target of the MOVEPAIR RDF group. The devices are resumed on the link.

EMCMN00I SRDF-HC : (60) &SQ VOL,9E00,RA(4A) EMCQV00I SRDF-HC DISPLAY FOR (60) &SQ VOL,9E00,RA(4A) 432 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 9E10 10 0030 0030 4A UAC00G 3339 ONPV 0 R/W-SY R1 0 0 ** 9E11 11 0031 0031 4A UAC00H 3339 ONPV 0 R/W-SY R1 0 0 ** 9E15 15 0035 0035 4A UAC00L 3339 ONPV 0 R/W-SY R1 0 0 ** ???? ?? 090B 090B 4A OFFLIN 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 090C 090C 4A OFFLIN 1113 N/A 0 R/W-SY L1 0 0 ** ???? ?? 090D 090D 4A OFFLIN 1113 N/A 0 R/W-SY L1 0 0 ** END OF DISPLAY


SRDF Operations

15. The following display illustrates the target of the MOVEPAIR RDF group on the secondary/R2 side.

EMCMN00I SRDF-HC : (61) &SQ VOL,4200,RA(0A) EMCQV00I SRDF-HC DISPLAY FOR (61) &SQ VOL,4200,RA(0A) 437 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 4210 10 0030 0030 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4211 11 0031 0031 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4213 13 0033 0033 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** 4215 15 0035 0035 0A OFFLIN 3339 OFFL 0 N/R R2 0 0 ** ???? ?? 090B 090B 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** ???? ?? 090C 090C 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** ???? ?? 090D 090D 0A OFFLIN 1113 N/A 0 N/R L2 0 0 ** END OF DISPLAY

16. Activate SRDF/A using the SC SRDFA command with the ACT action.

EMCMN00I SRDF-HC : (62) &SC SRDFA,LCL(9E00,4A),ACT EMCGM07I COMMAND COMPLETED (CMD:62) EMCGM40I COMMAND HAS FINISHED FOR BOX 000190103387 (CMD:62)

17. The following display illustrates SRDF/A has been activated.

EMCMN00I SRDF-HC : (63) &SQ SRDFA,LCL(9E00,4A) EMCQR00I SRDF-HC DISPLAY FOR (63) &SQ SRDFA,LCL(9E00,4A) 445 MY SERIAL # MY MICROCODE ------------ ------------ 000190103387 5773-46 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- 4A Y F 0A 000190100849 5773-46 G(R1>R2) SRDFA ACTIVE MFAC2ADA DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO ---------------------------------------------------------------------- PRIMARY SIDE: CYCLE NUMBER 1 MIN CYCLE TIME 30 SECONDARY CONSISTENT ( Y ) TOLERANCE ( N ) CAPTURE CYCLE SIZE 0 TRANSMIT CYCLE SIZE 0 AVERAGE CYCLE TIME 0 AVERAGE CYCLE SIZE 0 TIME SINCE LAST CYCLE SWITCH 25 DURATION OF LAST CYCLE 0 MAX THROTTLE TIME 0 MAX CACHE PERCENTAGE 94 HA WRITES 976,240 RPTD HA WRITES 861,065 HA DUP. SLOTS 1,617 SECONDARY DELAY 25 LAST CYCLE SIZE 0 DROP PRIORITY 33 CLEANUP RUNNING ( N ) MSC WINDOW IS OPEN ( N ) SRDF/A TRANSMIT IDLE ( Y ) SRDF/A DSE ACTIVE ( N ) MSC ACTIVE ( N ) ---------------------------------------------------------------------- END OF DISPLAY


SRDF Operations

Performing recovery in a diskless environmentThis section provides an example describing how to resynchronize R1<R2 changed tracks in a diskless environment.

Note: “Procedure 6: R1<R2 changed tracks resynchronization” on page 451 provides an example procedure for a non-diskless environment.

When running in a diskless cascaded environment, it is recommended that the SC VOL CASxxx command actions be used when possible. However, there are occasions when the CASxxx actions are not suitable. For instance, if the SC SRDFA,RMT(cuu,ra,ra),PENDDROP command is issued to drop the SRDF/A leg from site B to site C, and if ConGroup is running at site A, the CASRSUM action cannot be used to resume the environment. In this case, an error message will be issued stating that ConGroup is active in environment 1.

When I/O enters a diskless environment and the site B to site C leg is suspended, Enginuity will suspend the site A to site B leg in order to avoid overwhelming the cache at site B. With this in mind, the recovery procedures should be implemented to try to recover the site B to site C leg before the site A to site B leg.

Scenario 1After a failure at site A and with production work to begin at site C, run to write-enabled R2s, and then perform the recovery procedures as outlined in Chapter 6, “Recovery Procedures,”.

To run from R2s at site C:

1. Issue an SC VOL command to ready the R2 devices, if necessary.

EMCMN00I SRDF-HC : (34) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (34) &SQ VOL,8500,8,30 024 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8511 11 0031 0923 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8512 12 0032 0924 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8513 13 0033 0925 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8514 14 0034 0926 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8515 15 0035 0927 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8516 16 0036 0928 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** 8517 17 0037 0929 10 OFFLIN 1113 OFFL 0 N/R R2 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (35) &SC VOL,LCL(8500,10),RDY,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 027

Performing recovery in a diskless environment 409

SRDF Operations

0020-002F,0038-07A1,0822-0BA1,0BE2-0C21,0C42-0CF1,0CF6-0D19 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:35) EMCGM41I REQUESTED DEVICES 029 0030-0037 EMCGM42I ELIGIBLE DEVICES 030 0030-0037 EMCGM43I COMPLETED DEVICES 031 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:35) EMCMN00I SRDF-HC : (36) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (36) &SQ VOL,8500,8,30 035 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8511 11 0031 0923 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8512 12 0032 0924 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8513 13 0033 0925 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8514 14 0034 0926 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8515 15 0035 0927 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8516 16 0036 0928 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** 8517 17 0037 0929 10 OFFLIN 1113 OFFL 0 R/O R2 0 0 ** END OF DISPLAY

2. Make the devices R/W.

EMCMN00I SRDF-HC : (37) &SC VOL,LCL(8500,10),R/W,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 054 0020-002F,0038-07A1,0822-0BA1,0BE2-0C21,0C42-0CF1,0CF6-0D19 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:37) EMCGM41I REQUESTED DEVICES 056 0030-0037 EMCGM42I ELIGIBLE DEVICES 057 0030-0037 EMCGM43I COMPLETED DEVICES 058 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:37)EMCMN00I SRDF-HC : (39) &SQ VOL,8510,8 EMCQV00I SRDF-HC DISPLAY FOR (39) &SQ VOL,8510,8 086 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 R/W R2 0 0 ** 8511 11 0031 0923 10 UTH031 1113 ONPV 0 R/W R2 0 0 ** 8512 12 0032 0924 10 UTH032 1113 ONPV 0 R/W R2 0 0 ** 8513 13 0033 0925 10 UTH033 1113 ONPV 0 R/W R2 0 0 ** 8514 14 0034 0926 10 UTH034 1113 ONPV 0 R/W R2 0 0 ** 8515 15 0035 0927 10 UTH035 1113 ONPV 0 R/W R2 0 0 ** 8516 16 0036 0928 10 UTH036 1113 ONPV 0 R/W R2 0 0 ** 8517 17 0037 0929 10 UTH037 1113 ONPV 0 R/W R2 0 0 ** END OF DISPLAY


SRDF Operations

3. Perform tests/work. Invalid tracks begin to build up as indicated by the INVTRK field.

EMCMN00I SRDF-HC : (41) &SQ VOL,8510,8 EMCQV00I SRDF-HC DISPLAY FOR (41) &SQ VOL,8510,8 212 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 R/W R2 451 0 97 8511 11 0031 0923 10 UTH031 1113 ONPV 0 R/W R2 751 0 95 8512 12 0032 0924 10 UTH032 1113 ONPV 0 R/W R2 1351 0 91 8513 13 0033 0925 10 UTH033 1113 ONPV 0 R/W R2 1501 0 91 8514 14 0034 0926 10 UTH034 1113 ONPV 0 R/W R2 2251 0 86 8515 15 0035 0927 10 UTH035 1113 ONPV 0 R/W R2 301 0 98 8516 16 0036 0928 10 UTH036 1113 ONPV 0 R/W R2 376 0 97 8517 17 0037 0929 10 UTH037 1113 ONPV 0 R/W R2 226 0 98 END OF DISPLAY

4. When the failing site is back, ensure the R1 type devices are in the RDF-NRDY state.

EMCMN00I SRDF-HC : (42) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (42) &SQ VOL,RMT(8500,10),8,922 215 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 TNR-AW D1 7525 54 ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 TNR-AW D1 7504 55 ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 TNR-AW D1 7518 54 ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 TNR-AW D1 6168 63 ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 TNR-AW D1 6178 63 ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 TNR-AW D1 6170 63 ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 TNR-AW D1 6155 63 ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 TNR-AW D1 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (47) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (47) &SQ VOL,RMT(8500,10.23),8,30 283 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 TNR-SY R1 0 4501 73 8711 11 0031 0923 23 UTH031 1113 OFFL 0 TNR-SY R1 0 4501 73 8712 12 0032 0924 23 UTH032 1113 OFFL 0 TNR-SY R1 0 4501 73 8713 13 0033 0925 23 UTH033 1113 OFFL 0 TNR-SY R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 TNR-SY R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 TNR-SY R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 TNR-SY R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 TNR-SY R1 0 0 ** END OF DISPLAY


SRDF Operations

5. Issue an SC VOL multi-hop command to RDF-NRDY the devices at site A.

EMCMN00I SRDF-HC : (48) &SC VOL,RMT(8500,10.23),RDF-NRDY,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 287 0020-002F,0038-07A1,0822-0BA1,0BE2-0C41,0C46-0C5D EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600304 (CMD:48) EMCGM41I REQUESTED DEVICES 293 0030-0037 EMCGM42I ELIGIBLE DEVICES 294 0030-0037 EMCGM43I COMPLETED DEVICES 295 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:48) EMCMN00I SRDF-HC : (49) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (49) &SQ VOL,RMT(8500,10.23),8,30 299 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 RNR-SY R1 0 4501 73 8711 11 0031 0923 23 UTH031 1113 OFFL 0 RNR-SY R1 0 4501 73 8712 12 0032 0924 23 UTH032 1113 OFFL 0 RNR-SY R1 0 4501 73 8713 13 0033 0925 23 UTH033 1113 OFFL 0 RNR-SY R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 RNR-SY R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 RNR-SY R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 RNR-SY R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 RNR-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (50) &SC VOL,RMT(8500,10),RDF-NRDY,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 318 0020-07A1,0822-0921,092A-0BA1,0BE2-0C21,0C42-0C61,0C66-0C7D EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600312 (CMD:50) EMCGM41I REQUESTED DEVICES 320 0922-0929 EMCGM42I ELIGIBLE DEVICES 321 0922-0929 EMCGM43I COMPLETED DEVICES 322 0922-0929 EMCGM07I COMMAND COMPLETED (CMD:50) EMCMN00I SRDF-HC : (51) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (51) &SQ VOL,RMT(8500,10),8,922 326 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 RNR-AW D1 7525 54 ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 RNR-AW D1 7504 55 ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 RNR-AW D1 7518 54 ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 RNR-AW D1 6168 63 ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 RNR-AW D1 6178 63 ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 RNR-AW D1 6170 63 ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 RNR-AW D1 6155 63 ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 RNR-AW D1 0 ** END OF DISPLAY


SRDF Operations

6. Make the devices R/O before the synchronization process.

EMCMN00I SRDF-HC : (60) &SC VOL,8510-8517,R/O EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:60) EMCGM41I REQUESTED DEVICES 440 0030-0037 EMCGM42I ELIGIBLE DEVICES 441 0030-0037 EMCGM43I COMPLETED DEVICES 442 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:60) EMCMN00I SRDF-HC : (61) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (61) &SQ VOL,8500,8,30 447 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 R/O R2 451 0 97 8511 11 0031 0923 10 UTH031 1113 ONPV 0 R/O R2 751 0 95 8512 12 0032 0924 10 UTH032 1113 ONPV 0 R/O R2 1351 0 91 8513 13 0033 0925 10 UTH033 1113 ONPV 0 R/O R2 1501 0 91 8514 14 0034 0926 10 UTH034 1113 ONPV 0 R/O R2 2251 0 86 8515 15 0035 0927 10 UTH035 1113 ONPV 0 R/O R2 301 0 98 8516 16 0036 0928 10 UTH036 1113 ONPV 0 R/O R2 376 0 97 8517 17 0037 0929 10 UTH037 1113 ONPV 0 R/O R2 226 0 98 END OF DISPLAY

7. Issue an SC CNFG command to set the synchronization direction.

EMCMN00I SRDF-HC : (52) &SC CNFG,8500,SYNCH_DIRECTION,R1<R2 EMCGM07I COMMAND COMPLETED (CMD:52) EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:52) EMCMN00I SRDF-HC : (53) &SQ CNFG,8500 EMCGM11I SRDF-HC DISPLAY FOR (53) &SQ CNFG,8500 365 SERIAL NUMBER: 000192600313 MEM:24576 MB TYPE:2107 MODEL: VMAX-1 MICROCODE LEVEL: 5874-100 CONCURRENT DRDF: NO 3-DYN-MIRROR SWITCHED-RDF NO-AUTO-LINKS RDFGRP LINKS-OFF-ON-POWERUP LINKS-DOMINO: RDFGRP SYNCH_DIRECTION: R1<R2 LINK: LOCAL SSID(S): 0001 0002 0140 0141 0142 0143 0144 0145 0146 0147 8400 8401 8402 0321 DISK (DA) DIRECTORS: 007(07A) 008(08A) 009(09A) 00A(10A) 017(07B) 018(08B) 019(09B) 01A(10B) 027(07C) 028(08C) 029(09C) 02A(10C) 037(07D) 038(08D) 039(09D) 03A(10D) FICON (EF) DIRECTORS: 069(09G) 06A(10G) FIBRE CHANNEL ADAPTER (SF) DIRECTORS: 047(07E) 048(08E) 049(09E) 04A(10E) GIGE REMOTE (RE) DIRECTORS: 077(07H) 078(08H) FIBRE CHANNEL REMOTE (RF) DIRECTORS: 057(07F) 058(08F) 059(09F) 05A(10F) GIGE OPEN SYSTEMS (SE) DIRECTORS: 067(07G) 068(08G) END OF DISPLAY


SRDF Operations

8. Issue an SC VOL,RNG-REFRESH to refresh the R1 devices at site B. The command will work against the devices at the other side of RDF group 10.

EMCMN00I SRDF-HC : (55) &SC VOL,RMT(8500,10),RNG-REFRESH,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 385 0020-07A1,0822-0921,092A-0BA1,0BE2-0C21,0C42-0C61,0C66-0C7D EMCCV1DI PROCESSING RANGE COMMAND FOR DEVICE 0922 FOR 8 DEVICES (CMD:55) EMCCV1DI VERIFYING RANGE COMMAND FOR DEVICE 0922 FOR 8 DEVICES (CMD:55) EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600312 (CMD:55) EMCGM41I REQUESTED DEVICES 389 0922-0929 EMCGM42I ELIGIBLE DEVICES 390 0922-0929 EMCGM43I COMPLETED DEVICES 391 0922-0929 EMCGM07I COMMAND COMPLETED (CMD:55) EMCMN00I SRDF-HC : (56) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (56) &SQ VOL,RMT(8500,10),8,922 414 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 7525 0 54 0030 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 7504 0 55 0031 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 7518 0 54 0032 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 6168 0 63 0033 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 6178 0 63 0034 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 6170 0 63 0035 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 6155 0 63 0036 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 RNR-AW-R D1 0 ** END OF DISPLAY

9. Issue an SC VOL,RNG-RSUM command to RDF-resume the devices at site B.

EMCMN00I SRDF-HC : (70) &SC VOL,RMT(8500,10),RNG-RSUM,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 536 0020-07A1,0822-0921,092A-0BA1,0BE2-0C21,0C42-0C61,0C66-0C7D EMCCV1DI PROCESSING RANGE COMMAND FOR DEVICE 0922 FOR 8 DEVICES (CMD:70) EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600312 (CMD:70) EMCGM41I REQUESTED DEVICES 539 0922-0929 EMCGM42I ELIGIBLE DEVICES 540 0922-0929 EMCGM43I COMPLETED DEVICES 541 0922-0929 EMCGM07I COMMAND COMPLETED (CMD:70)


SRDF Operations

10. Issue an SC VOL,RNG-REFRESH to refresh the devices at site A.

EMCMN00I SRDF-HC : (73) &SC VOL,RMT(8500,10.23),RNG-REFRESH,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 556 0020-002F,0038-07A1,0822-0BA1,0BE2-0C41,0C46-0C5D EMCCV1DI PROCESSING RANGE COMMAND FOR DEVICE 0030 FOR 8 DEVICES (CMD:73) EMCCV1DI VERIFYING RANGE COMMAND FOR DEVICE 0030 FOR 8 DEVICES (CMD:73) EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600304 (CMD:73) EMCGM41I REQUESTED DEVICES 560 0030-0037 EMCGM42I ELIGIBLE DEVICES 561 0030-0037 EMCGM43I COMPLETED DEVICES 562 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:73) EMCMN00I SRDF-HC : (74) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (74) &SQ VOL,RMT(8500,10.23),8,30 567 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 RNR-SY-R R1 4501 0 73 8711 11 0031 0923 23 UTH031 1113 OFFL 0 RNR-SY-R R1 4501 0 73 8712 12 0032 0924 23 UTH032 1113 OFFL 0 RNR-SY-R R1 4501 0 73 8713 13 0033 0925 23 UTH033 1113 OFFL 0 RNR-SY-R R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 RNR-SY-R R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 RNR-SY-R R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 RNR-SY-R R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 RNR-SY-R R1 0 0 ** END OF DISPLAY

11. Issue an SC VOL,RNG-RSUM command to RDF-resume the devices at site A.

EMCMN00I SRDF-HC : (75) &SC VOL,RMT(8500,10.23),RNG-RSUM,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 570 0020-002F,0038-07A1,0822-0BA1,0BE2-0C41,0C46-0C5D EMCCV1DI PROCESSING RANGE COMMAND FOR DEVICE 0030 FOR 8 DEVICES (CMD:75) EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600304 (CMD:75) EMCGM41I REQUESTED DEVICES 574 0030-0037 EMCGM42I ELIGIBLE DEVICES 575 0030-0037 EMCGM43I COMPLETED DEVICES 576 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:75) EMCMN00I SRDF-HC : (76) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (76) &SQ VOL,8500,8,30 580 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 R/O R2 450 0 97 8511 11 0031 0923 10 UTH031 1113 ONPV 0 R/O R2 750 0 95 8512 12 0032 0924 10 UTH032 1113 ONPV 0 R/O R2 1350 0 91 8513 13 0033 0925 10 UTH033 1113 ONPV 0 R/O R2 1500 0 91 8514 14 0034 0926 10 UTH034 1113 ONPV 0 R/O R2 2250 0 86 8515 15 0035 0927 10 UTH035 1113 ONPV 0 R/O R2 300 0 98 8516 16 0036 0928 10 UTH036 1113 ONPV 0 R/O R2 375 0 97 8517 17 0037 0929 10 UTH037 1113 ONPV 0 R/O R2 0 0 ** END OF DISPLAY


SRDF Operations

EMCMN00I SRDF-HC : (77) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (77) &SQ VOL,RMT(8500,10),8,922 588 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 3092 0 81 0030 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 4456 0 73 0031 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 5526 0 66 0032 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 2113 0 87 0033 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 3913 0 76 0034 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 5185 0 69 0035 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 4743 0 71 0036 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 CAS-AW D1 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (78) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (78) &SQ VOL,RMT(8500,10.23),8,30 591 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 R/W-SY R1 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 R/W-SY R1 4065 0 75 8712 12 0032 0924 23 UTH032 1113 OFFL 0 R/W-SY R1 2391 0 85 8713 13 0033 0925 23 UTH033 1113 OFFL 0 R/W-SY R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 R/W-SY R1 3381 0 79 8715 15 0035 0927 23 UTH035 1113 OFFL 0 R/W-SY R1 4708 0 71 8716 16 0036 0928 23 UTH036 1113 OFFL 0 R/W-SY R1 4243 0 74 8717 17 0037 0929 23 UTH037 1113 OFFL 0 R/W-SY R1 0 0 ** END OF DISPLAY


SRDF Operations

12. The data from site C is synced to site A.

EMCMN00I SRDF-HC : (81) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (81) &SQ VOL,8500,8,30 624 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 R/O R2 0 0 ** 8511 11 0031 0923 10 UTH031 1113 ONPV 0 R/O R2 0 0 ** 8512 12 0032 0924 10 UTH032 1113 ONPV 0 R/O R2 0 0 ** 8513 13 0033 0925 10 UTH033 1113 ONPV 0 R/O R2 0 0 ** 8514 14 0034 0926 10 UTH034 1113 ONPV 0 R/O R2 0 0 ** 8515 15 0035 0927 10 UTH035 1113 ONPV 0 R/O R2 0 0 ** 8516 16 0036 0928 10 UTH036 1113 ONPV 0 R/O R2 0 0 ** 8517 17 0037 0929 10 UTH037 1113 ONPV 0 R/O R2 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (80) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (80) &SQ VOL,RMT(8500,10),8,922 621 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 CAS-AW D1 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (79) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (79) &SQ VOL,RMT(8500,10.23),8,30 618 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 R/W-SY R1 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 R/W-SY R1 0 0 ** 8712 12 0032 0924 23 UTH032 1113 OFFL 0 R/W-SY R1 0 0 ** 8713 13 0033 0925 23 UTH033 1113 OFFL 0 R/W-SY R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 R/W-SY R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 R/W-SY R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 R/W-SY R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 R/W-SY R1 0 0 ** END OF DISPLAY


SRDF Operations

Scenario 2In the event that a site is lost in a cascaded diskless environment, the SC VOL CASxxx command actions can be bypassed with the RCVRY option on the dynamic commands.

In this scenario, site A is lost due to a link outage and recovery actions are to take place at site C. Rather than write-enabling the R2, the environment can be swapped, so that writes happen at the R1. When the link is restored at site A, the other half of the environment can be swapped so that the data can sync "naturally", and then can be swapped back to normal function with the CASSWAP action.

1. The following output illustrates normal processing configuration from site A.

EMCMN00I SRDF-HC : (101) &SQ VOL,8700,8,30 EMCQV00I SRDF-HC DISPLAY FOR (101) &SQ VOL,8700,8,30 166 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 R/W-SY R1 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 R/W-SY R1 0 0 ** 8712 12 0032 0924 23 UTH032 1113 OFFL 0 R/W-SY R1 0 0 ** 8713 13 0033 0925 23 UTH033 1113 OFFL 0 R/W-SY R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 R/W-SY R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 R/W-SY R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 R/W-SY R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 R/W-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (102) &SQ VOL,RMT(8700,23),8,922 EMCQV00I SRDF-HC DISPLAY FOR (102) &SQ VOL,RMT(8700,23),8,922 169 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 CAS-AW D1 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (104) &SQ VOL,RMT(8700,23.10),8,30 EMCQV00I SRDF-HC DISPLAY FOR (104) &SQ VOL,RMT(8700,23.10),8,30 182 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 OFFL 0 N/R R2 0 0 ** 8511 11 0031 0923 10 UTH031 1113 OFFL 0 N/R R2 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 N/R R2 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 N/R R2 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 N/R R2 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 N/R R2 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 N/R R2 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 N/R R2 0 0 ** END OF DISPLAY


SRDF Operations

2. A link outage occurs at site A from Site C. Site A cannot be accessed remotely.

EMCMN00I SRDF-HC : (107) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (107) &SQ VOL,RMT(8500,10),8,922 204 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 CAS-AW D1 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (108) &SQ VOL,RMT(8500,10.23),8,30 EMCPC08I RAGROUP SPECIFIED DOES NOT EXIST (CMD:108)

3. Issue an SC VOL with the RDF-SUSP action to suspend the site B to site C leg.

EMCMN00I SRDF-HC : (110) &SC VOL,RMT(8500,10),RDF-SUSP,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 223 0020-02C1,0322-07A1,0822-0921,092A-0BA1,0BE2-0C21,0C42-0C61, 0C66-0C6A,0C6E-0C72,0C76-0C7D EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600312 (CMD:110) EMCGM41I REQUESTED DEVICES 225 0922-0929 EMCGM42I ELIGIBLE DEVICES 226 0922-0929 EMCGM43I COMPLETED DEVICES 227 0922-0929 EMCGM07I COMMAND COMPLETED (CMD:110) EMCMN00I SRDF-HC : (111) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (111) &SQ VOL,RMT(8500,10),8,922 236 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 TNR-AW D1 0 ** END OF DISPLAY


SRDF Operations

4. The following output shows the result of trying to personality swap in a diskless environment without using the composite actions.

EMCMN00I SRDF-HC : (112) &SC VOL,LCL(8500,10),SWAP,ALL EMCCM35I DRDF non-composite action, Rmt device diskless 239 0030-0037 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:112) EMCGM41I REQUESTED DEVICES 241 0030-0037 EMCCW56E No eligible devices found (CMD:112) EMCCWFEE Command failed (CMD:112)

5. Add the RCVRY option to the SC VOL,SWAP command to allow the swap in a diskless environment.

EMCMN00I SRDF-HC : (113) &SC VOL,LCL(8500,10),SWAP(RCVRY),ALL EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:113) EMCGM41I REQUESTED DEVICES 251 0030-0037 EMCGM42I ELIGIBLE DEVICES 252 0030-0037 EMCGM43I COMPLETED DEVICES 253 0030-0037 EMCGM07I COMMAND COMPLETED (CMD:113) EMCMN00I SRDF-HC : (114) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (114) &SQ VOL,8500,8,30 257 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 OFFL 0 TNR-SY R1 0 0 ** 8511 11 0031 0923 10 UTH031 1113 OFFL 0 TNR-SY R1 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 TNR-SY R1 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 TNR-SY R1 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 TNR-SY R1 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 TNR-SY R1 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 TNR-SY R1 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 TNR-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (115) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (115) &SQ VOL,RMT(8500,10),8,922 266 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 IL D2 0 ** END OF DISPLAY


SRDF Operations

6. Work can now continue to site C. When site A is restored, the other half of the environment can be swapped and resumed to allow data to flow naturally.

EMCMN00I SRDF-HC : (117) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (117) &SQ VOL,8500,8,30 303 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 TNR-SY R1 0 751 95 8511 11 0031 0923 10 UTH031 1113 OFFL 0 TNR-SY R1 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 TNR-SY R1 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 TNR-SY R1 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 TNR-SY R1 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 TNR-SY R1 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 TNR-SY R1 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 TNR-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (118) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (118) &SQ VOL,RMT(8500,10),8,922 310 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 IL D2 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 IL D2 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (124) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (124) &SQ VOL,RMT(8500,10.23),8,30 337 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 TNR-SY R1 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 TNR-SY R1 0 0 ** 8712 12 0032 0924 23 UTH032 1113 OFFL 0 TNR-SY R1 0 0 ** 8713 13 0033 0925 23 UTH033 1113 OFFL 0 TNR-SY R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 TNR-SY R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 TNR-SY R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 TNR-SY R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 TNR-SY R1 0 0 ** END OF DISPLAY


SRDF Operations

7. From the RDF group at the site B system, swap all of the devices on the RDF group going to site A. This will restore the diskless environment at site C.

EMCMN00I SRDF-HC : (126) &SC VOL,RMT(8500,10,23),SWAP(RCVRY,ADCOPY),ALL EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600312 (CMD:126) EMCGM41I REQUESTED DEVICES 359 0922-0929 EMCGM42I ELIGIBLE DEVICES 360 0922-0929 EMCGM43I COMPLETED DEVICES 361 0922-0929 EMCGM07I COMMAND COMPLETED (CMD:126) EMCMN00I SRDF-HC : (127) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (127) &SQ VOL,RMT(8500,10),8,922 366 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0030 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0031 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0032 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0033 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0034 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0035 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0036 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0037 10 ...... 1113 N/A 0 N/R D2 0 ** END OF DISPLAY

8. Issue an SC VOL command with the CARSUM action to restore the environment.

EMCMN00I SRDF-HC : (128) &SC VOL,LCL(8500,10),CASRSUM,ALL EMCGM47I Command environment 1 on box 000192600313 (CMD:128) EMCGM48I Requested devices 375 0030-0037 EMCGM49I Eligible devices 376 0030-0037 EMCGM4AI Completed devices 377 0030-0037 EMCGM47I Command environment 2 on box 000192600312 (CMD:128) EMCGM48I Requested devices 379 0922-0929 EMCGM49I Eligible devices 380 0922-0929 EMCGM4AI Completed devices 381 0922-0929 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:128) EMCGM07I COMMAND COMPLETED (CMD:128)


SRDF Operations

EMCMN00I SRDF-HC : (129) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (129) &SQ VOL,8500,8,30 388 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 R/W-SY R1 0 0 ** 8511 11 0031 0923 10 UTH031 1113 OFFL 0 R/W-SY R1 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 R/W-SY R1 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 R/W-SY R1 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 R/W-SY R1 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 R/W-SY R1 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 R/W-SY R1 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 R/W-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (130) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (130) &SQ VOL,RMT(8500,10),8,922 392 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0030 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0031 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0032 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0033 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0034 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0035 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0036 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 CAS-AW D1 0 0 ** 0037 10 ...... 1113 N/A 0 N/R D2 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (131) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (131) &SQ VOL,RMT(8500,10.23),8,30 397 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 N/R R2 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 N/R R2 0 0 ** 8712 12 0032 0924 23 UTH032 1113 OFFL 0 N/R R2 0 0 ** 8713 13 0033 0925 23 UTH033 1113 OFFL 0 N/R R2 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 N/R R2 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 N/R R2 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 N/R R2 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 N/R R2 0 0 ** END OF DISPLAY


SRDF Operations

9. When data has gone over, the environment can be suspended, and you can issue the CASSUSP and CASSWAP actions to restore processing at site A.

Note: It is strongly recommended to quiesce all I/O when the CASSWAP action is issued. The default processing will leave the R2 in a R/O and NRDY state, which will halt any I/O to the device that was previously the R1.

EMCMN00I SRDF-HC : (132) &SC VOL,LCL(8500,10),CASSUSP,ALL EMCGM47I Command environment 1 on box 000192600313 (CMD:132) EMCGM48I Requested devices 421 0030-0037 EMCGM49I Eligible devices 422 0030-0037 EMCGM4AI Completed devices 423 0030-0037 EMCGM47I Command environment 2 on box 000192600312 (CMD:132) EMCGM48I Requested devices 425 0922-0929 EMCGM49I Eligible devices 426 0922-0929 EMCGM4AI Completed devices 427 0922-0929 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:132) EMCGM07I COMMAND COMPLETED (CMD:132) EMCMN00I SRDF-HC : (133) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (133) &SQ VOL,8500,8,30 432 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 TNR-SY R1 0 0 ** 8511 11 0031 0923 10 UTH031 1113 OFFL 0 TNR-SY R1 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 TNR-SY R1 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 TNR-SY R1 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 TNR-SY R1 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 TNR-SY R1 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 TNR-SY R1 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 TNR-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (134) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (134) &SQ VOL,RMT(8500,10),8,922 438 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0030 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0031 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0032 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0033 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0034 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0035 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0036 10 ...... 1113 N/A 0 N/R D2 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 TNR-AW D1 0 0 ** 0037 10 ...... 1113 N/A 0 N/R D2 0 ** END OF DISPLAY


SRDF Operations

EMCMN00I SRDF-HC : (135) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (135) &SQ VOL,RMT(8500,10.23),8,30 441 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 N/R R2 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 N/R R2 0 0 ** 8712 12 0032 0924 23 UTH032 1113 OFFL 0 N/R R2 0 0 ** 8713 13 0033 0925 23 UTH033 1113 OFFL 0 N/R R2 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 N/R R2 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 N/R R2 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 N/R R2 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 N/R R2 0 0 ** END OF DISPLAY

EMCMN00I SRDF-HC : (141) &SC VOL,LCL(8500,10),CASSWAP,ALL EMCGM47I Command environment 1 on box 000192600313 (CMD:141) EMCGM48I Requested devices 489 0030-0037 EMCGM49I Eligible devices 490 0030-0037 EMCGM4AI Completed devices 491 0030-0037 EMCGM47I Command environment 2 on box 000192600312 (CMD:141) EMCGM48I Requested devices 493 0922-0929 EMCGM49I Eligible devices 494 0922-0929 EMCGM4AI Completed devices 495 0922-0929 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600313 (CMD:141) EMCGM07I COMMAND COMPLETED (CMD:141) EMCMN00I SRDF-HC : (142) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (142) &SQ VOL,8500,8,30 500 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 N/R R2 0 0 ** 8511 11 0031 0923 10 UTH031 1113 OFFL 0 N/R R2 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 N/R R2 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 N/R R2 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 N/R R2 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 N/R R2 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 N/R R2 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 N/R R2 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (143) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (143) &SQ VOL,RMT(8500,10),8,922 503 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 TNR-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 TNR-AW D1 0 ** END OF DISPLAY


SRDF Operations

EMCMN00I SRDF-HC : (144) &SQ VOL,RMT(8500,10.23),8,30 EMCQV00I SRDF-HC DISPLAY FOR (144) &SQ VOL,RMT(8500,10.23),8,30 506 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8710 10 0030 0922 23 UTH030 1113 OFFL 0 TNR-AW R1 0 0 ** 8711 11 0031 0923 23 UTH031 1113 OFFL 0 TNR-AW R1 0 0 ** 8712 12 0032 0924 23 UTH032 1113 OFFL 0 TNR-AW R1 0 0 ** 8713 13 0033 0925 23 UTH033 1113 OFFL 0 TNR-AW R1 0 0 ** 8714 14 0034 0926 23 UTH034 1113 OFFL 0 TNR-AW R1 0 0 ** 8715 15 0035 0927 23 UTH035 1113 OFFL 0 TNR-AW R1 0 0 ** 8716 16 0036 0928 23 UTH036 1113 OFFL 0 TNR-AW R1 0 0 ** 8717 17 0037 0929 23 UTH037 1113 OFFL 0 TNR-AW R1 0 0 ** END OF DISPLAY

10. Issue the SC VOL with the CASRSUM action from site C.

EMCMN00I SRDF-HC : (150) &SC VOL,RMT(8500,10.23),CASRSUM,ALL EMCGM47I Command environment 1 on box 000192600304 (CMD:150) EMCGM48I Requested devices 545 0030-0037 EMCGM49I Eligible devices 546 0030-0037 EMCGM4AI Completed devices 547 0030-0037 EMCGM47I Command environment 2 on box 000192600312 (CMD:150) EMCGM48I Requested devices 549 0922-0929 EMCGM49I Eligible devices 550 0922-0929 EMCGM4AI Completed devices 551 0922-0929 EMCGM40I COMMAND HAS FINISHED FOR BOX 000192600304 (CMD:150) EMCGM07I COMMAND COMPLETED (CMD:150) EMCMN00I SRDF-HC : (151) &SQ VOL,8500,8,30 EMCQV00I SRDF-HC DISPLAY FOR (151) &SQ VOL,8500,8,30 557 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 8510 10 0030 0922 10 UTH030 1113 ONPV 0 N/R R2 0 0 ** 8511 11 0031 0923 10 UTH031 1113 OFFL 0 N/R R2 0 0 ** 8512 12 0032 0924 10 UTH032 1113 OFFL 0 N/R R2 0 0 ** 8513 13 0033 0925 10 UTH033 1113 OFFL 0 N/R R2 0 0 ** 8514 14 0034 0926 10 UTH034 1113 OFFL 0 N/R R2 0 0 ** 8515 15 0035 0927 10 UTH035 1113 OFFL 0 N/R R2 0 0 ** 8516 16 0036 0928 10 UTH036 1113 OFFL 0 N/R R2 0 0 ** 8517 17 0037 0929 10 UTH037 1113 OFFL 0 N/R R2 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (152) &SQ VOL,RMT(8500,10),8,922 EMCQV00I SRDF-HC DISPLAY FOR (152) &SQ VOL,RMT(8500,10),8,922 560 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % ???? ?? 0922 0030 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0030 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0923 0031 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0031 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0924 0032 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0032 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0925 0033 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0033 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0926 0034 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0034 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0927 0035 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0035 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0928 0036 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0036 10 ...... 1113 N/A 0 CAS-AW D1 0 ** ???? ?? 0929 0037 23 ...... 1113 N/A 0 N/R D2 0 0 ** 0037 10 ...... 1113 N/A 0 CAS-AW D1 0 ** END OF DISPLAY

Recovery Procedures 427

6

This chapter provides information about performing recovery procedures in an SRDF environment. Topics include:

◆ Getting started .................................................................................. 428◆ Recovering using operational host ................................................ 429◆ Recovery procedure concepts and testing.................................... 432◆ Procedure 1: R2 read/write testing ............................................... 435◆ Procedure 2: Synchronization method selection ......................... 440◆ Procedure 3: R1>R2 full volume resynchronization ................... 443◆ Procedure 4: R1<R2 full volume resynchronization ................... 446◆ Procedure 5: R1>R2 changed tracks resynchronization ............. 449◆ Procedure 6: R1<R2 changed tracks resynchronization ............. 451◆ SRDF/A recovery scenarios ........................................................... 454◆ SRDF/A MSC recovery scenario ................................................... 456◆ SRDF/A MSC and SRDF/Star recovery considerations............ 458◆ SRDF Automated Recovery............................................................ 473

Recovery Procedures


Recovery Procedures

Getting startedBefore attempting any of the procedures in this chapter, review the following:

◆ Note that cuu refers to the z/OS device number of the device and dev# refers to the Symmetrix device number.

◆ The following Symmetrix configuration parameters must be specified:

Note: Contact your EMC Customer Support Engineer to verify parameters.

Resuming SRDF/A operationResuming SRDF/A involves planning. If you are going to use the SRDF/A target R2 disks for processing after an SRDF/A suspension caused by a DROP or PEND_DROP, follow the same procedures for resuming SRDF that are documented in this chapter.

Note: “SRDF/A recovery scenarios” on page 454 discusses SRDF/A recovery.

CAUTION!The specific recovery steps that are required are determined by your configuration, the specific nature of the outage, and any special circumstances that may exist. Always contact the EMC Customer Support Center for assistance in a recovery situation. EMC personnel are trained for proper handling of these situations. An incorrect action during the recovery process can result in data corruption. Concurrent SRDF configurations require special recovery considerations.

• Enable links domino? NO

• Prevent auto links recovery after all links failure? YES

• Force RAs links offline after power-up? YES

Recovering using operational host 429

Recovery Procedures

Recovering using operational hostThis section describes an example of procedures to be performed in an actual recovery situation.

The following site definitions are used throughout these procedures:

◆ Operational site — The host and Symmetrix system containing target (R2) volumes to be brought online.

◆ Nonoperational site — The host and Symmetrix system containing source (R1) volumes that experienced an outage.

Making the operational site availableTo write enable all target (R2) volumes to the host at the operational site, perform the following steps:

1. Disable the links by either disabling the remote link director (RLD) switches on both Symmetrix systems, disconnecting the link cables, or issuing the following command:

#SC LINKS,cuu,ALL,OFFLINE

2. Set all target (R2) volumes to a “ready” state to the operational host by issuing the following command:

#SC VOL,cuu,RDY,ALL

3. Write-enable all volumes on the operational Symmetrix system with an R2 designation by issuing the following command:

#SC VOL,cuu,R/W,ALL

Note: Any target (R2) volume configured with the Invalid Tracks Attribute (#SQ VOL command shows status xxx-xx-I) goes RNR (RDF - not ready) if the R1 partner device indicates R2 invalid tracks. Use the RDF-RDY action with the #SC VOL command to clear this not ready condition.

If the links are offline, you receive the EMCPC081I RAGROUP SPECIFIED DOES NOT EXIST message. However, the devices are changed to a read/write status. You can issue an SQ STATE message to confirm.

Note: “#SQ STATE” on page 278 provides additional information.


Recovery Procedures

4. Vary the devices online.

All volumes at the operational Symmetrix system are now available for I/O operations with the host at that site.

When non-operational site becomes availableWhen the host and Symmetrix system at the non-operational site are ready to be brought back online, perform the following steps:

Note: Remember that before read/write operations to the source (R1) volumes can be resumed, all target (R2) volumes must be set to read-only.

At the operational site, perform the following steps:

1. Stop I/O operations with the operational Symmetrix system, and vary devices offline from the operational host.

2. Make all target (R2) volumes on the operational Symmetrix system read only and optionally not ready to the operational host (as per the original configuration) by issuing the following command:

#SC VOL,cuu,R/O,ALL

and optionally:

#SC VOL,cuu,NRDY,ALL

3. Enable the remote link directors on the operational Symmetrix system by either enabling the RLD switches on both Symmetrix, connecting the link cables, or issuing the following command:

#SC LINK,cuu,ONLINE

At the site of the original outage (non-operational host and Symmetrix system), perform the following steps:

1. Disable the channel directors and RLDs on the non-operational Symmetrix system to prevent host I/O processing until ready for synchronization.

2. Reconnect the link cables if they were previously disconnected.

3. Power up the newly operational Symmetrix system.

Recovering using operational host 431

Recovery Procedures

Note: At this point, the EMC technician verifies that no invalid tracks exist, and that the Symmetrix system is ready for resynchronization. In concurrent SRDF configurations, special considerations apply. If both target (R2) devices have invalid tracks for their partner source (R1), manual intervention is required.

4. Enable the remote link directors.

The two Symmetrix systems begin synchronizing. When the links synchronize, the previously operational Symmetrix system begins copying its data to the newly operational Symmetrix system.

After synchronization begins, the newly operational Symmetrix can be made available for host I/O processing.

5. Enable the channel directors.

6. IPL the newly operational host system.

7. Vary the devices of the newly operational host system online, if necessary.

You can track the resynchronization process by issuing the following command:

#SQ VOL,cuu,INV_TRKS


Recovery Procedures

Recovery procedure concepts and testingIn a normal SRDF device relationship, the source (R1) device may be synchronized with its target (R2) device, or it may contain updated tracks, which the RLD has not yet sent to the target (R2) device (semi-synchronous or adaptive copy state). In addition, the target (R2) volume is in a read-only mode.

◆ R1>R2 resynchronization describes a process by which any updates to the target (R2) volume made during read/write testing are discarded, and updates made to the source (R1) volume during that same time are sent to the target (R2) volume.

◆ R1<R2 resynchronization describes a process by which any updates to the source (R1) volume made during read/write testing to the target (R2) volume are discarded, and updates made to the target (R2) volume are sent to the source (R1) volume.

Resynchronization control is a result of the SYNCH_DIRECTION setting, and the sequence of SRDF Host Component commands issued in the following procedure examples. SYNCH_DIRECTION is not saved in the Symmetrix array.

You can test recovery procedures by enabling write operations to the target (R2) volumes. The procedure examples in this section show how to do this task and how to resynchronize your SRDF pairs, and resume normal operations when testing is completed.

Note: In concurrent or cascaded SRDF configurations, special considerations apply. The examples in this chapter are designed to apply to only one of the partner (R2) devices at a time. If both partner devices (R2) have been updated, the partner (R2) whose changes are to be retained must be determined. The procedures are then to be executed completely for this partner (R2). At that time, the process to discard the other partner (R2) updates should be performed.

Recovery procedure concepts and testing 433

Recovery Procedures

SRDF command syntax considerationsThe example procedures listed below use the R1cuu and R2cuu form of command syntax. This requires the commands to be issued from a host that has addressability to the R1cuu or R2cuu device number. When issued to a R1cuu in a concurrent SRDF configuration, some command actions are performed to both R2 partner devices.

The LCL (cuup, rdfgroup#) command syntax may be substituted, using the rdfgroup#, to direct the command actions to the specific R2 partner device that is in that RDF group.

The RMT (cuup, mhlist, rdfgroup#) command syntax may be substituted, using the rdfgroup#, to direct command actions to a remote Symmetrix that does not have host addressability for R1cuu or R2cuu syntax.

Note: Chapter 5, “SRDF Operations,” provides examples illustrating usage of the LCL and RMT command syntax.

Examples

The following procedure examples are provided:

“Procedure 1: R2 read/write testing” page 435

“Procedure 2: Synchronization method selection” page 440

“Procedure 3: R1>R2 full volume resynchronization” page 443

“Procedure 4: R1<R2 full volume resynchronization” page 446

“Procedure 5: R1>R2 changed tracks resynchronization” page 449

“Procedure 6: R1<R2 changed tracks resynchronization” page 451


Recovery Procedures

ConventionsThe following conventions are used in these procedure examples:

◆ dev# = Symmetrix device number

◆ R1 = source volume

◆ R2 = target volume

◆ R1cuu = z/OS address of an R1 device

◆ R2cuu = z/OS address of a R2 device

◆ rdfgroup# = specifies the rdfgroup# through which you want to perform an operation. This must be a 1- or 2-digit (hex) value, representing the rdfgroup#. For concurrent SRDF configurations, rdfgroup# identifies the partner device for the operation to be performed.

Note: The LCL (cuup, rdfgroup#) or RMT (cuup, mhlist, rdfgroup#) syntax statements use the rdfgroup# to specify the correct partner device for concurrent and cascaded configurations. The RMT (cuup, mhlist, rdfgroup#) syntax is also used to reach a remote Symmetrix when host addressability is not available to the R1cuu or R2cuu.

Procedure 1: R2 read/write testing 435

Recovery Procedures

Procedure 1: R2 read/write testingBefore performing R2 read/write testing, you must:

◆ Synchronize the source (R1) and target (R2) volumes

◆ Suspend SRDF operations between the devices

◆ Make the devices ready

◆ Write enable the target (R2) volumes

Any source (R1) volumes configured in the Adaptive Copy mode may have a number of tracks (up to the value of the Adaptive Copy Skew) that have not been synchronized.

Note: To ensure complete synchronization prior to suspending SRDF operations, Adaptive Copy mode must be disabled, and all tracks allowed to synchronize. This synchronization can be verified with the #SQ ADC command. When all tracks have been synchronized, volumes return to their default mode (synchronous or semi-synchronous) and no longer list when the #SQ ADC command is run. Use the #SQ VOL command to verify that the volumes are in the synchronous or semi-synchronous mode prior to issuing the #SC VOL command with the RDF-SUSP action.

Perform the following steps:

1. Suspend SRDF operations for the pair(s) by issuing the following command at the host with access to the source (R1) volume(s):

#SC VOL,R1cuu,RDF-SUSP[,dev#|ALL]

Note: Any source (R1) volume configured with the Domino Attribute option goes RNR (volumes not ready for SRDF operations) when SRDF operations are suspended. To clear this not ready condition, you must disable the Domino Attribute option on those “not ready” volumes, and enable those devices for SRDF operation, using the RDF-RDY action with the #SC VOL command.

2. Make the target (R2) volume(s) ready to receive I/O from the host by issuing the following command at the host with access to the target (R2) volume(s):

#SC VOL,R2cuu,RDY[,dev#|ALL]


Recovery Procedures

3. Write enable the target (R2) volume(s) by issuing the following command at the host with access to the target (R2) volume(s):

#SC VOL,R2cuu,R/W[,dev#|ALL]

Note: Any target (R2) volume configured with the Invalid Tracks Attribute (#SQ VOL command shows status xxx-xx-I) goes RNR if the R1 partner device indicates R2 invalid tracks. Use the RDF-RDY action with the #SC VOL command to clear this not ready condition.

4. Vary the target (R2) volume(s) online to z/OS by issuing the following command at the host with access to the target (R2) volume(s):

V,R2cuu,ONLINE

Figure 33 is a representation of this procedure. Note that actions to be performed on the host with access to the source (R1) volume are shown in the boxes on the left, and actions to be performed on the host with access to the target (R2) volume are shown in the boxes to the right.


Recovery Procedures

Figure 33 R2 read/write testing

Suspend normal RDFoperations between the R1and R2 volumes.

#SC VOL, R1cuu ,RDF-SUSP

Make the R2 volume readyto accept I/O from the host

#SC VOL, R2cuu ,RDY

Write-enable the R2volume

#SC VOL, R2cuu ,R/W

Vary the R2 volume onlineto the (remote) host system

V R2cuu ,ONLINE

Submit jobs to read andwrite to the R2 volume

Many installations run with the R2volume set not ready to the host. Anyattempt to do I/O to the host in thismode, will result in an I/O error. Bymaking the R2 volume ready, you willenable the host to issue I/O request tothe device.

In order to suspend synchronization oftracks from the source to the targetdevice, issue a #SC VOL command withthe RDF-SUSP action from thehost with access to R1.

Enable the R2 volume for WRITEoperations.

Check for RNR status.

Now that the R2 volume is accessible tothe host, bring it online to MVS.

Perform your read/write testing. Duringthis process, the R2 volume willaccumulate R1 invalid tracks. If writeoperations are going on at this point onthe R1 side, the R1 volume willaccumulate R2 invalid tracks.

Go toProcedure:

2

When R2 read/write testing is complete,the R2 volume will be in a Read/Writestate, ready to the host, and will reflectR1 invalid tracks. During this processthe R1 volume has been available to itshost and may reflect R2 invalid tracks.Go to procedure 2 to determine theappropriate actions to resynchronize theRDF pair.

R1 R2Procedure 1

Perform pre-Synchronization

procedure?

No

Go to Pre-Synchronization

Procedure

Yes


Recovery Procedures

Presynchronization procedure R1<R2The #SC VOL command actions PREFRESH and PRE-RSUM provide a way to begin synchronizing an R1 from an R2 that is still R/W to a host. This option is useful when work needs to continue at the R2 site prior to moving the active workload back to the R1 site.

Performing a presynchronization procedure before the workload is restarted on the R1 can result in many of the tracks owed to the R1 from the R2 to already be synchronized when the R2 is made R/O. This reduces the number of I/Os that need to access the R/O R2 to resolve invalid tracks owed to the R1. The number of remaining tracks to synchronize can be determined with the #SQ VOL command. This information can be useful in determining when to move the workload to the R1 site.

Multiple cycles of commands are used to move the invalids owed the R1 from the R2. Each cycle of commands determines the invalid tracks that exist at the time the commands are executed. While this group of invalid tracks is moving from the R2 to the R1, new invalid tracks are accumulating on the R/W R2. Each command cycle determines the invalid tracks at that point in time. This probably includes tracks that have previously been moved. This is due to the continued write activity on the R2 where tracks may be written to multiple times during the presynchronization period.

Each command cycle progresses toward a lower total number of invalids. The invalid count does not reach zero unless the write activity on the R2 stops. After a relatively low number of invalids is achieved, the decision to stop the workload and make the R2 R/O can occur.

After the desired number of invalid tracks is achieved, the R2 workload is stopped. The R2 is placed in an R/O state and optionally not ready.

The R1 must not be used for work during the presynchronization procedure. This procedure is only valid for moving information from an active R2 to the nonoperational sites R1.

Note: Because the commands are usually issued from the operation host that the R/W R2s are attached to, the RMT formats of the commands are used in the examples.

The sequence of commands for each cycle are:


Recovery Procedures

Cycle 1:

Cycle 2:

Final Cycle:

Vary the target (R2) volume(s) offline, and make them read only, and optionally not ready by issuing the following command(s) at the host with access to the target (R2) volume(s):

#SC VOL,R2cuu,R/O[,dev#|ALL]

and optionally:

#SC VOL,R2cuu,NRDY[,dev#|ALL]

#SC CNFG,R2cuu,SYNCH_DIRECTION,R1<R2 Set synch_direction R1<R2

#SC VOL,RMT(R2cuu,rdfgroup#),RDF-NRDY[,dev#|ALL] Place the R1 into the RNR state

#SC VOL,RMT(R2cuu,rdfgroup#),PREFRESH[,dev#|ALL] Prepare to refresh from the updated R2 tracks

#SC VOL,RMT(R2cuu,rdfgroup#),PRE-RSUM[,dev#|ALL] Commence synchronization R1<R2

#SC CNFG,R2cuu, SYNCH_DIRECTION, R1<R2 Set synch_direction R1<R2

#SC VOL,RMT(R2cuu,rdfgroup#),RDF-NRDY[,dev#|ALL] Place the R1 into the RNR state

#SC VOL,RMT(R2cuu,rdfgroup#),PREFRESH[,dev#|ALL] Prepare to refresh from the updated R2 tracks

#SC VOL,RMT(R2cuu,rdfgroup#),PRE-RSUM[,dev#|ALL] Commence synchronization R1<R2


Recovery Procedures

Procedure 2: Synchronization method selection Select the appropriate procedure for resynchronization of the source (R1) and the target (R2), and resume normal operations. This procedure sets the target (R2) volume to the read-only mode and not ready for host access.

Note: The recovery procedure examples require that SRDF activity be suspended (RDF-SUSP) and the SRDF links be operational. The first step in Procedure 1 is to suspend SRDF operations using the #SC VOL,cuu,RDF-SUSP command. If the SRDF links have been physically disconnected (due to link failure or intentional action) prior to executing Step 1 to RDF-SUSP the volumes, an #SC VOL,cuu,RDF-SUSP,ALL command must be issued to suspend the volumes before the SRDF links are physically reconnected and before beginning the resynchronization processes of Procedure 2 and Procedures 3, 4, 5, or 6.


1. Vary the target (R2) volume(s) offline, and make them read only and optionally not ready by issuing the following command at the host with access to the target (R2) volume(s):

#SC VOL,R2cuu,R/O[,dev#|,ALL]

and optionally:

#SC VOL,R2cuu,NRDY[,dev#|,ALL]

2. Determine the invalid tracks of each source (R1) and target (R2) volume involved in R2 read/write testing by issuing the following command:

#SQ VOL,cuu,INV_TRKS

3. Choose your synchronization procedure from Table 23 on page 441, based on the state of the remotely mirrored pair and the desired scope of the synchronization (in other words, changed tracks or full volume).

Procedure 2: Synchronization method selection 441

Recovery Procedures

Note: If circumstances encountered during your testing prevent you from determining the correct procedure to follow, or if you encounter unexpected results, contact the EMC Customer Support Center for technical assistance.

Figure 34 is a representation of the previous procedure. Note that actions to be performed on the host with access to the source (R1) volume are shown in the boxes on the left, and actions to be performed on the host with access to the target (R2) volume are shown in the boxes to the right.

Table 23 Synchronization procedure selections

Scope

R1 indicates R2 invalid tracks

R2 indicates R1 invalid tracks Discard updates to Full volume Changed tracks

N N Procedure 3 Procedure 5

Y N NONE Procedure 3 Procedure 5

Y N R1 Procedure 4 Procedure 6

Y NONE/R1 Procedure 4 Procedure 6

Y R2 Procedure 3 Procedure 5


Recovery Procedures

Figure 34 Synchronization method

Procedure 3: R1>R2 full volume resynchronization 443

Recovery Procedures

Procedure 3: R1>R2 full volume resynchronization This procedure resynchronizes the SRDF pair after R2 read/write testing. Any updates to the target (R2) volume that were made after the RDF-SUSP action was performed are discarded, and any updates to the source (R1) volume are retained.

Note: See “SRDF command syntax considerations” on page 433 to determine if LCL (cuup, rdfgroup#) or RMT (cuup, mhlist, rdfgroup#) command syntax should be substituted for R1cuu or R2cuu syntax.


1. Set the current synchronization direction from source to target (R1 >R2) by issuing the following command at the host with access to the source (R1) volumes:

#SC CNFG,R1cuu,SYNCH_DIRECTION,R1>R2

and issuing the following command at the host with access to the target (R2) volumes:


2. Determine which target (R2) volumes have a non-zero R1 INV_TRKS value by issuing the following command at the host with access to the target (R2) volume(s):

#SQ VOL,R2cuu,INV_TRKS

3. For all target (R2) volumes with non-zero R1 INV_TRKS values, validate all invalid tracks for the source (R1) volume(s) on the target (R2) volume by issuing the following command at the host with access to the target (R2) volume:

#SC VOL,R2cuu,VALIDATE[,dev#|,ALL]

(dev# = target (R2) volume with an R1 INV_TRKS value greater than 0)

Note: If ALL was not the specified parameter, repeat step 3 for each target (R2) volume with a non-zero R1 INV_TRKS value for a source (R1) volume.


Recovery Procedures

4. Verify all target (R2) volumes have an R1 INV_TRKS value equal to 0 by issuing the following command at the host with access to the target (R2) volume(s):


5. For all source (R1) volumes whose target (R2) volume was write enabled and had an R1 INV_TRK value greater than 0 (prior to Step 2), invalidate all valid tracks for the target (R2) volume on the source (R1) volume by issuing the following command at the host with access to the source (R1) volume:

#SC VOL,R1cuu,INVALIDATE[,dev#|,ALL]

(dev# = source (R1) volume whose target (R2) volume had an R1 INV_TRKS value greater than 0)

When the Invalidate operation completes, the R2 invalid track count goes to maximum for the device, the TNR status disappears, and resynchronization begins.

SRDF Host Component monitors the process of invalidating all target tracks until complete.

6. Monitor the resynchronization process until complete by issuing the following command at the host with access the source (R1) volumes:


Figure 35 is a representation of this procedure. Note that actions to be performed on the host with access to the source (R1) volume are shown in the boxes on the left, and actions to be performed on the host with access to the target (R2) volume are shown in the boxes to the right.

Procedure 3: R1>R2 full volume resynchronization 445

Recovery Procedures

Figure 35 R1>R2 full volume resynchronization

From the host with access to the R2

volumes, either enter the Validate action

with the ALL option, or enter the Validate

action for each R2 volume with

accumulated R1 invalid tracks. This

command clears the invalid track

indicator


Recovery Procedures

Procedure 4: R1<R2 full volume resynchronization This procedure resynchronizes the SRDF pair after R2 read/write testing. Any updates to the R1 device that were made after the RDF-SUSP action was performed are discarded, and any updates to the R2 device are kept.

Note: With Enginuity level 5773 and earlier, you cannot use SRDF Host Component synchronization procedure examples 4 and 6 while TimeFinder/Clone or Clone Emulation restores are taking place. However, with Enginuity 5874 and later, you can use procedures 4 and 6 while Clone or Clone Emulation restores are taking place.



1. Set the current synchronization direction from target to source (R1<R2) by issuing the following command at the host with access to the source (R1) volumes:

#SC CNFG,R1cuu,SYNCH_DIRECTION,R1<R2



2. Vary the R1 device offline to z/OS by issuing the following command at the host with access to the source (R1) volumes:

V R1cuu,OFFLINE

3. Make the source (R1) device unavailable to the host by issuing the following command at the host with access to the source (R1) volumes:

#SC VOL,R1cuu,RDF-NRDY[,dev#|,ALL]

4. Determine which target (R2) volumes have a non-zero R1 INV_TRKS value by issuing the following command at the host with access to the target (R2) volumes:


Procedure 4: R1<R2 full volume resynchronization 447

Recovery Procedures

5. For all target (R2) volumes with non-zero R1 invalid tracks, set the R1 invalid track count to max by issuing the following command at the host with access to the target (R2) volume:

#SC VOL,R2cuu,INVALIDATE[,dev#|ALL]6. For all target (R2) volumes with non-zero R1 INV_TRKS values,

set R2 invalid tracks to zero and prepare the source (R1) volume for synchronization by issuing the following command at the host with access to the source (R1) volume:

#SC VOL,R1cuu,VALIDATE[,dev#|,ALL]

(dev# = source (R1) volume whose target (R2) volume has an R1 INV_TRKS value greater than 0)

Note: If ALL was not the specified parameter, repeat Step 5 for each source (R1) volume with a non-zero R2 INV_TRKS value for a target (R2) volume.

When the validate completes, the R1 invalid track count goes to maximum for the device, the TNR status disappears, and resynchronization begins.

7. If you are using Enginuity level 5x67 or earlier and if the devices are in the RNR state, make the source (R1) devices available to the host by issuing the following command:

#SC VOL,R1cuu,RDF-RDY[dev#|ALL]

Otherwise, proceed to step 8.

8. Vary the R1 device online to z/OS by issuing the following command at the host with access to the source (R1) volumes:

V R1cuu,online

Figure 36 on page 448 is a representation of this procedure. Note that actions to be performed on the host with access to the source (R1) volume are shown in the boxes on the left, and actions to be performed on the host with access to the target (R2) volume are shown in the boxes to the right.


Recovery Procedures

Figure 36 R1<R2 full volume resynchronization

Set the currentsynch_direction to R1<R2.#SC CNFG,R1cuu, SYNCH_DIRECTION, R1<R2

Vary the R1 device offlineto MVSV R1cuu,OFFLINE

In order to prevent allocation to theR1 device, vary it offline to MVS.

Use the #SC CNFG,cuu,SYNCH_DIRECTION,R1<R2command to set the currentsynchronization direction to R1<R2.

FromProcedure:

2

The R2 device is not ready andread/only. The R1 is RDF-SUSP

Determine which target(R2) volumes haveaccumulated R1 invalidtracks.#SQ VOL,R2cuu,INV_TRKS

From the host with access to the R2device, use the#SQ VOL,cuu,INV_TRKS commandto determine which R2 volumes haveaccumulated R1 invalid tracks.

For each R1 volume whosepartner device indicates R1invalid tracks set all R2tracks valid:#SC VOL,R1cuu,VALIDATE

From the host with acesss to the R1volumes, use the VALIDATE actionto set all R2 tracks valid andprepare the R1 device for re-synchfrom the R2. You may monitor theresynchronization process using the#SQ VOL command.

Make the R1 device notready to the host.#SC VOL,R1cuu,RDF-NRDY

From the Host with access to the R1device, make the R1 device RDF-NRDY. Any attempt to issue an I/Orequest to the device will result in anintervention required status.

Vary the R1 device onlineto MVSV R1cuu,ONLINE

DONE

The R1 device can be brought backonline to MVS.

Procedure 4:R1 R2

For each R2 volume thatindicates R1 invalid tracks,set all R1 tracks invalid.#SC VOL,R2cuu, INVALIDATE

From the host with access to the R2device, use the#SQ VOL,cuu,INVALIDATEcommand to flag all R1 tracks invalid.

Set the currentsynch_direction to R1<R2.#SC CNFG,R2cuu, SYNCH_DIRECTION, R1<R2

Make the R1 available tothe host.#SC VOL,R1cuu,RDF-RDY

Once resynchronization has started,make the R1 device ready for accessfrom the host.

Procedure 5: R1>R2 changed tracks resynchronization 449

Recovery Procedures

Procedure 5: R1>R2 changed tracks resynchronizationAny updates to the target (R2) volume that were made after the RDF-SUSP action was performed are discarded, and any updates to the source (R1) volume are retained.



1. Set the current synchronization direction from source to target (R1>R2) by issuing the following command at the host with access to the source (R1) volumes:




2. Determine which target (R2) volumes have a non-zero R1 INV_TRKS value by issuing the following command at the host with access to the target (R2) volumes:


3. Flag any tracks that were updated on the R2 as valid on the R1 and invalid on the R2 by issuing the following command at the host with access to the target (R2) volumes:

#SC VOL,R2cuu,REFRESH[,dev#|,ALL]

4. Resume SRDF operation by issuing the following command at the host with access to the target (R2) volumes:

#SC VOL,R2cuu,RFR-RSUM[,dev#|,ALL]

Note: Only the tracks that were updated during R2 read/write testing are copied from R1>R2.




Recovery Procedures

Figure 37 is represents this procedure. Actions to be performed on the host with access to the source (R1) volume are shown in the boxes on the left, and actions to be performed on the host with access to the target (R2) volume are shown in the boxes to the right.

Figure 37 R1>R2 changed tracks resynchronization

Note: Figure 37 shows R1>R2 resynchronization procedures when executed entirely by commands on the R2 side. As a safety mechanism, the procedure sets the synch_direction at the CNFG level on the R1 side to NONE because no commands are going to be executed on the R1 side.

Procedure 5:

Use the #SC CNFG, cuu ,SYNCH_DIRECTION command to set the current synchronization direction.

Resume normal SRDF operations and commence synchronization

#SC VOL, R2cuu ,RFR-RSUM

The R2 tracks that are now flagged as invalid will be refreshed from the R1 device. Monitor the resynchronization process using the #SQ VOL command from the Host with access to the R1.

The R2 device is not ready and read/only. The R1 is RDF-SUSP

DONE The synchronization process is complete.

Determine which target (R2) volumes have invalid tracks.

#SQ VOL, R2cuu ,INV_TRKS

For each R2 volume with R1 invalid tracks, set the R1 tracks valid, and flag the corresponding R2 tracks invalid.

#SC VOL, R2cuu ,REFRESH

From the host with access to the R2 volume, use the #SQ VOL, cuu ,INV_TRKS command to determine which R2 volumes have accumulated R1 invalid tracks.

The REFRESH action causesany updated tracks on either of the SRDF partners to be flagged as invalid R2 tracks and valid R1 tracks. No transfer of data will occur at this time.

Set the current synch_direction to R1>R2.

#SC CNFG, R2cuu , SYNCH_DIRECTION, R1>R2

R1 R2

From Procedure:

2

Set the current synch_direction to NONE.

#SC CNFG, R1cuu , SYNCH_DIRECTION, NONE

Procedure 6: R1<R2 changed tracks resynchronization 451

Recovery Procedures

Procedure 6: R1<R2 changed tracks resynchronization This procedure resynchronizes the SRDF pair after R2 read/write testing. Any updates to the source (R1) volume that were made after the RDF-SUSP action was performed are discarded, and any updates to the target (R2) volume are retained.

Note: With Enginuity level 5773 and earlier, you cannot use SRDF Host Component synchronization procedure examples 4 and 6 while TimeFinder/Clone or Clone Emulation restores are taking place. However, with Enginuity 5874 and later, you can use procedures 4 and 6 while Clone or Clone Emulation restores are taking place.



1. Set the current synchronization direction from target to source (R1<R2) by issuing the following command at the host with access to the source (R1) volumes:




2. Vary the R1 devices offline.

3. Make the source (R1) device unavailable to the host by issuing the following command at the host with access to the source (R1) volumes:

#SC VOL,R1cuu,RDF-NRDY[,dev#|,ALL]

4. Determine which source (R1) volumes have a non-zero R2 INV_TRKS value by issuing the following command at the host with access to the source (R1) volumes, and determine which target (R2) volumes have a non-zero R1 INV_TRKS value by typing the following command at the host with access to the target (R2) volumes:



Recovery Procedures

5. Flag any tracks that were updated on the target (R2) volume as valid on the R2 and invalid on the R1 by issuing the following command at the host with access to the source (R1) volumes:

#SC VOL,R1cuu,REFRESH[,dev#|,ALL]6. Resume SRDF operation by issuing the following command at the

host with access to the source (R1) volumes:

#SC VOL,R1cuu,RFR-RSUM[,dev#|,ALL]

Note: Only the tracks that were updated during R2 read/write testing are copied from the R2 to the R1.

After resynchronization is started, you can vary the R1 devices online.



Figure 38 on page 453 is a representation of this procedure. Note that actions to be performed on the host with access to the source (R1) volume are shown in the boxes on the left, and actions to be performed on the host with access to the target (R2) volume are shown in the boxes to the right.

Procedure 6: R1<R2 changed tracks resynchronization 453

Recovery Procedures

Figure 38 R1<R2 changed tracks resynchronization

Procedure 6:

Use the #SC CNFG, cuu ,SYNCH_DIRECTION command to set the current synchronization direction.

Resume Normal SRDF operations:

#SC VOL, R1cuu ,RFR-RSUM

The R2 volume is not ready and read/ only. The R1 is RDF-SUSP.

DONE The synchronization process is complete.

Determine which target (R2) volumes have invalid tracks.


For each R1 volume with R2 invalid tracks or whose partner device indicates R1 invalid tracks, refresh updated tracks from the R2.

#SC VOL, R1cuu ,REFRESH

From the host with access to the R1 volume, use the #SQ VOL, R1cuu ,INV_TRKS command to determine which R1 volumes have accumulated R2 invalid tracks, and from the host with access to the R2 volume, use the #SQ VOL, R2cuu ,INV_TRKS command to determine which R2 volumes have accumulated R1 invalid tracks.

The REFRESH action causesany updated tracks on either of the SRDF partners to be flagged as invalid R1 tracks and valid R2 tracks. No transfer of data will occur at this time.

The R1 tracks that are now flagged as invalid will be refreshed from the R2 volume. Monitor the resynchronization process using the #SQ VOL command from the Host with access to the R1.

R1 R2

Determine which source (R1) volumes have invalid tracks.


From Procedure:

2

Set the current synch_direction to NONE.

#SC CNFG, R2cuu , SYNCH_DIRECTION, NONE

Set the current synch_direction to R1<R2.

#SC CNFG, R1cuu , SYNCH_DIRECTION, R1<R2

Make the R1 device not ready to the host. #SC VOL, R1cuu ,RDF-NRDY

From the Host with access to the R1 device, make the R1 device RDF- NRDY. Any attempt to issue an I/O request to the device will result in an intervention required status.

In order to prevent allocation to the R1 device, vary it offline to MVS.

Vary the R1 device offline to MVS. V R1cuu ,OFFLINE


Recovery Procedures

SRDF/A recovery scenariosThe following discusses SRDF/A recovery scenarios, including:

◆ Temporary link loss

◆ Permanent link loss

◆ Primary Symmetrix cache full condition

◆ Failback from R2

Temporary link loss

If SRDF/A suffers a temporary loss (<10 seconds) of all links, the SRDF/A state remains active and data continues to accumulate in cache. This may result in an elongated cycle, but the remote consistency is not compromised and the R1-R2 relationships is not suspended. You can configure the amount of time SRDF waits until it declares a link loss permanent (between 0 and 10 seconds).

Permanent link loss

If SRDF/A experiences a permanent link loss, SRDF/A drops all the devices on the link to “not ready” state. This results in all data in the inactive cycle being changed from “write pending” to “invalid” on the link for both the R1 and R2 devices. In addition, any new work that enters the Symmetrix storage subsystem results in tracks being marked “invalid.”

When the links are restored, normal SRDF recovery procedures are followed. The data is then resynchronized by sending over the invalid tracks as part of the SRDF/A cycles or through SRDF adaptive copy mode.

Normally, the data on the R2 volumes is consistent in SRDF/A, even when the links fail. However, the act of starting a resynchronization activity between the R1 and the R2 destroys the consistency of the R2 data until the resynchronization is completed.

For this reason, EMC recommends that you employ a method for preserving the data on the R2 volumes before commencing resynchronization. For example, you can do this using TimeFinder BCVs.

SRDF/A recovery scenarios 455

Recovery Procedures

Primary Symmetrix cache “full” conditionIt is possible that an imbalance may occur within SRDF/A between the incoming write I/O workload and the outgoing SRDF bandwidth so that the cache in the primary Symmetrix storage subsystem becomes “full.” The transmit and receive cycles consume all the available write cache in the Symmetrix storage subsystem.

In this situation, you have a choice as to how SRDF/A will behave:

◆ The Symmetrix storage subsystem can throttle the host at the speed of the links, and keep SRDF/A running, In this case the performance is equivalent to synchronous mode.

◆ The Symmetrix storage subsystem can throttle the host for a user-specified period of time. If the condition has not resolved itself at the expiration of this time, then SRDF/A is dropped. Running in MSC mode changes the maximum time to approximately 11 seconds to account for other Symmetrix in the MSC group.

The default behavior is to drop SRDF/A immediately when this condition occurs.

Failback from R2

If a disaster occurs on the primary site, the data on the R2 devices represents a dependent, write-consistent image of data that you can use to restart an environment with minimal data loss. After the primary site has been repaired, the process for returning to the R1 side uses exactly the same methods as are used for synchronous SRDF failback.

After the workload had been transferred back to the primary site hosts, you can activate SRDF/A and resume normal asynchronous mode protection.


Recovery Procedures

SRDF/A MSC recovery scenarioIn SRDF/A Multi-Session Consistency (MSC) mode, additional considerations exist for recovery. SRDF/A MSC coordinates multiple SRDF/A sessions running in multiple Symmetrix.

SRDF/A MSC is deactivated or dropped

If SRDF/A is deactivated or dropped while in Multi-Session mode, each R1-side Symmetrix storage subsystem starts the same cleanup process as in single session mode:

1. All cache slots belonging to both the transmit and capture cycles are discarded.

2. The corresponding tracks are marked invalid to the RDF mirror (“owed” to the R2 side).

Host software does not need to perform any special recovery on the R1-side Symmetrix storage subsystem participating in the SRDF/A Multi-Session group.

If SRDF/A is deactivated or dropped while in Multi-Session mode, each R2-side Symmetrix storage subsystem takes the following steps:

1. Finishes the restore of its apply cycle.

2. Discards its receive cycle if the receive cycle is not marked as complete.

Any R2-side Symmetrix storage subsystem that has a complete receive cycle puts the receive cycle “on hold” in cache, awaiting decision from the host software or inline user. This is done because the statuses of all the R2-side receive cycles for the R2-side Symmetrix storage subsystems participating in the Multi-Session Group must be considered before a decision can be made to commit or discard each one.

The host software must either discard (mark invalid, “owed” to the R1 side) or commit (force the restore of) the slots in each R2 receive cycle, based on the following rules.

Three different cases need to be considered when SRDF/A Multi-Session mode have been dropped when recovery is performed on the R2 side. This is where the host provided cycle tag and the list of all Symmetrix participating in the MSC group is used by SRDF/A MSC recovery software.

SRDF/A MSC recovery scenario 457

Recovery Procedures

These cases are:

1. All R2 receive cycles have the same tag, and all R2 receive cycles are complete.

2. All R2 receive cycles have the same tag, but one or more (but not all) R2 receive cycles are complete.

3. Apply cycle tags of some R2 Symmetrix storage subsystems match receive cycle tags of one or more other R2 Symmetrix storage subsystems (, not all R2 receive cycles were committed) and not all receive cycles may be complete.

If the SRDF links are operational on all Symmetrix pairs, this recovery is handled by the MSC host process.


Recovery Procedures

SRDF/A MSC and SRDF/Star recovery considerationsSRDF Host Component has a batch cleanup utility for performing recovery for SRDF/A MSC or SRDF/Star. You can run the utility on either the primary side or secondary side.

Table 24 describes the batch cleanup utilities delivered with SRDF Host Component.

It is necessary to run the batch cleanup utility when the MSC environment of EMCSCF cannot perform the automatic cleanup. This occurs when the SRDF link for at least one SRDF/A session in an MSC or Star group is not available at the time that SRDF/A dropped.

You can identify this situation by issuing the #SQ SRDFA command to the secondary side of all Symmetrix storage subsystems in the MSC or Star group. As shown in Figure 39 on page 459, if one or more Symmetrix storage subsystems have both the CLEANUP RUNNING and HOST INTERVENTION REQUIRED settings on, then you need to run the batch cleanup utility.

Table 24 SRDF Host Component utilities

Utility module name Module alias Location JCL example name

EHCMSCME SCFRDFME HC LINKLIB EHCMSCME

EHCMSCM6 SCFRDFM6 HC LINKLIB EHCMSCM6

SRDF/A MSC and SRDF/Star recovery considerations 459

Recovery Procedures

EMCMN00I SRDF-HC : (36) &SQ SRDFA,7800 EMCQR00I SRDF-HC DISPLAY FOR (36) &SQ SRDFA,7800 038 EMCMN00I SRDF-HC : (36) &SQ SRDFA,7800 EMCQR00I SRDF-HC DISPLAY FOR (36) &SQ SRDFA,7800 038 MY SERIAL # MY MICROCODE ------------ ------------ 000123401234 5771-84 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP ---------- ------- ---------------------- ---------------- ---------- 04 Y F 04 000000006228 5671-46 G(R1>R2) SRDFA I STAR MSF6K2UD1 DYNAMIC AUTO-LINKS-RECOVERY LINKS-DOMINO:NO (MSCPROD1) ---------------------------------------------------------------------- SECONDARY SIDE: CYCLE NUMBER 45,785 CYCLE SUSPENDED ( N ) RESTORE DONE ( Y ) RECEIVE CYCLE SIZE 0 APPLY CYCLE SIZE 0 AVERAGE CYCLE TIME 15 AVERAGE CYCLE SIZE 0 TIME SINCE LAST CYCLE SWITCH 135 DURATION OF LAST CYCLE 16 MAX THROTTLE TIME 0 MAX CACHE PERCENTAGE 94 TOTAL RESTORES 675,863 TOTAL MERGES 681 SECONDARY DELAY NOT ACTIVE DROP PRIORITY 9 CLEANUP RUNNING ( Y ) HOST INTERVENTION REQUIRED ( Y ) MSC ACTIVE ( Y ) ACTIVE SINCE 07/17/2006 15:33:17 RECEIVE TAG E0000000 00000090 APPLY TAG E0000000 0000008F GLOBAL CONSISTENCY ( Y ) STAR RECOVERY AVAILABLE ( Y ) STAR SRDFA AHEAD ( N ) STAR/S TARGET INCONSISTENT ( N ) ----------------------------------------------------------------------

Figure 39 #SQ SRDFA command issued to the secondary side

Utility recovery requirementsObserve the following requirements when running the batch cleanup utility:

◆ EMCSCF must be running.

◆ The links for all SRDF/A sessions must be up and available to run the utility from the primary side. If one or more links cannot be made available, or if you are running the utility after a loss of the source site, then you must run this utility from the secondary side.


Recovery Procedures

◆ Devices in the SRDF/A MSC group should not be in the EMCSCF exclude list. The devices discovered by EMCSCF are used to determine the accessibility of the R2 Symmetrix in the MSC group.

◆ The parameter required to perform the recovery is either the CUU or VOLSER of a device in a Symmetrix storage subsystem containing an SRDF/A session participating in an MSC or Star group. The code then locates all of the other SRDF/A sessions participating in the MSC or Star group and produces a report written to the RPTOUT DD (samples are listed below). Information about an MSC or Star group is kept in each Symmetrix that has SRDF/A RDF groups participating in the MSC or Star groups. This metadata is referred to as the box list and the scratch table area.

◆ You can address the SRDF/A sessions in the following ways:

• If you can run the batch cleanup utility from the primary side, you can address the entire MSC group across the link from the primary side.

• If you need to run the batch cleanup utility to the secondary side, you can address the entire MSC group from the secondary side.

If the utility cannot locate one or more SRDF/A sessions, then the utility is not able to complete the host intervention cleanup. When this occurs, the utility JCL gatekeeper parameter should be modified to run directly against each participating Symmetrix.


Recovery Procedures

Possible MSC group recovery casesThe SCFRDFME utility produces the B to C device pairing dataset, reports on cycle tags and other configuration information, and resolves cases 1, 2, and 3 at the SRDF/A target site.

Note: SCFRDFME does not clear SRDF/Star configuration information. It does execute the appropriate commit or discard actions to prepare the MSC or Star group for restart processing. This program can be run multiple times without affecting MSC device pairing information.

Both RDF group 1 and RDF group 2 reside in the same MSC group:

Tables 25 through 28 on the following pages list the R1 and R2 status for cases 1, 2, and 3.

Case 1: All R2 receive cycles have the same tag, and all R2 receive cycles are complete.

Case 2: All R2 receive cycles have the same tag, but one or more (but not all) R2 receive cycles are complete.

Case 3: Apply cycle tags of some R2 Symmetrix storage subsystems match receive cycle tags of one or more other R2 Symmetrix storage subsystems (that is, not all R2 receive cycles were committed) and not all receive cycles may be complete.

SRDF/A RDF group 1

R1 R2

Active Inactive Inactive Active

Capture Transmit Receive Apply

SRDF/A RDF group 2

R1 R2




Recovery Procedures

Table 25 Case 1 cycles

SRDF/A RDF group 1

R1 R2



CompleteRECEIVE TAG = E0000000000005D5

SRDF/A RDF group 2

R1 R2




Table 26 Case 2 cycles

SRDF/A RDF group 1

R1 R2



IncompleteRECEIVE TAG = E0000000000005D5

SRDF/A RDF group 2

R1 R2





Recovery Procedures

Or, the following:

Table 27 Case 3 cycles (option 1)

SRDF/A RDF group 1

R1 R2




SRDF/A RDF group 2

R1 R2




Table 28 Case 3 cycles (option 2)

SRDF/A RDF group 1

R1 R2



IncompleteRECEIVE TAG = E0000000000005D5

SRDF/A RDF group 2

R1 R2





Recovery Procedures

Figures 40 through 45 on the following pages illustrate the batch cleanup utility RPTOUT for each of these cases on both the primary and secondary sides.

“SCFRDFME report output” on page 470 describes the batch cleanup utility.

------------------------------------------------------------00000002 SRDFA SESSIONS IN MSC ------------------------------------------------------------000187790072/00 > 000187900699/00 000000006205/00 > 000187990175/00 ------------------------------------------------------------OUR SESSION IS RUNNING ON PRIMARY SIDE - 000000006205/00 FOUND SESSION = 000187790072/00 CUU= 2800 RDFGRP = 15 ------------------------------------------------------------000187790072/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 0000000000000033 APPLY TAG = 0000000000000032 ------------------------------------------------------------000000006205/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 0000000000000033 APPLY TAG = 0000000000000032 ------------------------------------------------------------CASE1 - COMMIT ALL CYCLES SRDFA SESSION = 000187790072/00 COMMIT RECEIVE CYCLE SRDFA SESSION = 000000006205/00 COMMIT RECEIVE CYCLE

Figure 40 Batch cleanup utility RPTOUT for case 1 from primary side


Recovery Procedures

------------------------------------------------------------00000002 SRDFA SESSIONS IN MSC ------------------------------------------------------------000187790072/00 > 000187900699/00 000000006205/00 > 000187990175/00 ------------------------------------------------------------OUR SESSION IS RUNNING ON SECONDARY SIDE - 000187990175/00 ------------------------------------------------------------FOUND SESSION = 000187900699/00 CUU= EE00 RDFGRP = 25 ------------------------------------------------------------000187900699/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 000000000000001E APPLY TAG = 000000000000001D ------------------------------------------------------------000187990175/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 000000000000001E APPLY TAG = 000000000000001D ------------------------------------------------------------CASE1 - COMMIT ALL CYCLES SRDFA SESSION = 000187900699/00 COMMIT RECEIVE CYCLE SRDFA SESSION = 000187990175/00 COMMIT RECEIVE CYCLE

Figure 41 Batch cleanup utility RPTOUT for case 1 from secondary side


Recovery Procedures

------------------------------------------------------------00000002 SRDFA SESSIONS IN MSC ------------------------------------------------------------000187790072/00 > 000187900699/00 000000006205/00 > 000187990175/00 OUR SESSION IS RUNNING ON PRIMARY SIDE - 000000006205/00------------------------------------------------------------ FOUND SESSION = 000187790072/00 CUU= 2800 RDFGRP = 15 ------------------------------------------------------------000187790072/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 000000000000000B APPLY TAG = 000000000000000A ------------------------------------------------------------000000006205/00 MSC IS ACTIVE APPLY CYCLE IS EMPTY RECEIVE TAG = 000000000000000B APPLY TAG = 000000000000000A ------------------------------------------------------------CASE2 - DISCARD ALL CYCLES SRDFA SESSION = 000187790072/00 DISCARD RECEIVE CYCLE



Recovery Procedures

------------------------------------------------------------00000002 SRDFA SESSIONS IN MSC ------------------------------------------------------------000187790072/00 > 000187900699/00 000000006205/00 > 000187990175/00 ------------------------------------------------------------OUR SESSION IS RUNNING ON SECONDARY SIDE - 000187990175/00 ------------------------------------------------------------FOUND SESSION = 000187900699/00 CUU= EE00 RDFGRP = 25 ------------------------------------------------------------000187900699/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 000000000000001A APPLY TAG = 0000000000000019 ------------------------------------------------------------000187990175/00 MSC IS ACTIVE APPLY CYCLE IS EMPTY RECEIVE TAG = 000000000000001A APPLY TAG = 0000000000000019 ------------------------------------------------------------CASE2 - DISCARD ALL CYCLES SRDFA SESSION = 000187900699/00 DISCARD RECEIVE CYCLE



Recovery Procedures

------------------------------------------------------------00000002 SRDFA SESSIONS IN MSC ------------------------------------------------------------000187790072/00 > 000187900699/00 000000006205/00 > 000187990175/00 ------------------------------------------------------------OUR SESSION IS RUNNING ON PRIMARY SIDE - 000000006205/00FOUND SESSION = 000187790072/00 CUU= 2800 RDFGRP = 15 ------------------------------------------------------------000187790072/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 0000000000000047 APPLY TAG = 0000000000000046 ------------------------------------------------------------000000006205/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 0000000000000046 APPLY TAG = 0000000000000045------------------------------------------------------------ CASE3 - NOT ALL BOXES HAVE THE SAME RECEIVE TAG SRDFA SESSION = 000187790072/00 HOST INTERVENTION REQUIRED SRDFA SESSION = 000187790072/00 INACTIVE TAG MATCH SRDFA SESSION = 000187790072/00 DISCARD RECEIVE CYCLE SRDFA SESSION = 000000006205/00 HOST INTERVENTION REQUIRED SRDFA SESSION = 000000006205/00 LOW INACTIVE TAG SRDFA SESSION = 000000006205/00 COMMIT RECEIVE CYCLE



Recovery Procedures

------------------------------------------------------------ 00000002 SRDFA SESSIONS IN MSC ------------------------------------------------------------000187790072/00 > 000187900699/00 000000006205/00 > 000187990175/00 ------------------------------------------------------------OUR SESSION IS RUNNING ON SECONDARY SIDE - 000187990175/00 ------------------------------------------------------------ FOUND SESSION = 000187900699/00 CUU= EE00 RDFGRP = 25 ------------------------------------------------------------000187900699/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 0000000000000008 APPLY TAG = 0000000000000007 ------------------------------------------------------------000187990175/00 MSC IS ACTIVE TRANSMIT CYCLE IS EMPTY APPLY CYCLE IS EMPTY HOST INTERVENTION REQUIRED RECEIVE TAG = 0000000000000007 APPLY TAG = 0000000000000006 ------------------------------------------------------------CASE3 - NOT ALL BOXES HAVE THE SAME RECEIVE TAG SRDFA SESSION = 000187900699/00 HOST INTERVENTION REQUIRED SRDFA SESSION = 000187900699/00 INACTIVE TAG MATCH SRDFA SESSION = 000187900699/00 DISCARD RECEIVE CYCLE SRDFA SESSION = 000187990175/00 HOST INTERVENTION REQUIRED SRDFA SESSION = 000187990175/00 LOW INACTIVE TAG SRDFA SESSION = 000187990175/00 COMMIT RECEIVE CYCLE



Recovery Procedures

SCFRDFME report outputThis section describes the SCFRDFME utility report output. The report output is displayed in the left column. The right column provides explanatory text relating to the report lines.

INITIALIZATION

SCF1315I MSC MODULE= EHCMSCME VER= V5.4.0 PATCH=SR54001

DEBUG ONMSC_GROUP_NAME=MSCPROD1CUU = 237E UCB ADDRESS = 021656C0

Debug option setting.MSC group name.Device number and UCB address specified in ME cleanup utility JCL parameter. This device is used as the gatekeeper to a Symmetrix to locate any MSC/Star environment through interrogation of all RDF groups in that Symmetrix.

DISCOVERY

RUNNING ON SITEC States the site where this ME cleanup utility is executing.

FOUND STAR SRDFA SCRATCH AREA FOR MSC_GROUP_NAME=MSCPROD1 RDFGRP = 20 RCV RDFGRP = 30

States MSC or SRDF/Star SRDF/A scratch area details found for an RDF group.

FOUND STAR J0 SCRATCH AREA FOR MSC_GROUP_NAME=MSCPROD1 RDFGRP = 10 RCV RDFGRP = 30

States SRDF/Star SYNC (J0) scratch area details found through the recovery RDF group.

VALID RDFGRP FOUND 20 Verification of the SRDF/A RDF group listed in the scratch area.

00000002 SRDFA SESSIONS IN MSC States the number of SRDF/A RDF groups that are defined to MSC/Star.

000187700899/20 > 000187751120/20 000187751229/20 > 000187751076/20

List of Symmetrix S/N and RDFGRP from mblist (multi-box list) for the SRDF/A RDF group.

OUR SESSION IS RUNNING ON SECONDARY SIDE - 000187751120/20

States the Symmetrix S/N where the ME cleanup utility JCL Parm device number is located.

00000002 J0 SESSIONS IN STAR States the number of SYNC RDF groups that are defined to Star.

000187700899/10 > 000187720744/10000187751229/10 > 000187721688/10

List of Symmetrix S/N and RDFGRP from mblist for the SYNC RDF group.

FOUND CU = 000187751076 Verification of the Symmetrix S/N of other local Symmetrix defined to MSC/Star from the mblist.

VALID RDFGRP FOUND 20 Verification of the SRDF/A RDF group listed in this box scratch area.

FOUND SESSION = 000187751076/20 CUU= 3000 RDFGRP = 20

States that there is a valid SRDF/A session (scratch area and mblist) on this Symmetrix S/N.


Recovery Procedures

ANALYSIS

REMOTE SAI ERROR CUU = 237E RDFGRP = 20 GROUP ERROR DUE TO LINKS UNAVAILABLE

States that the links are down to remote Symmetrix from the SRDF/A RDF group in this Symmetrix.

000187751120/20 1st local Symmetrix S/N and RDFGRP from mblist to be analyzed.

MSC IS ACTIVE States that MSC is active for this RDF group.

APPLY CYCLE IS EMPTY States that the apply cycle is empty for this RDF group.

RECEIVE TAG = E0000000000005D5 APPLY TAG = E0000000000005D4

Shows the MSC/Star cycle tags for this RDF group, including the flag byte ('E0').

REMOTE SAI ERROR CUU = 3000 RDFGRP = 20 GROUP ERROR DUE TO LINKS UNAVAILABLE

States that the links are down to remote Symmetrix from the SRDF/A RDF group in this Symmetrix.

000187751076/20 2nd local Symmetrix S/N and RDFGRP from MBLIST to be analyzed.

MSC IS ACTIVE States that MSC is active for this RDF group.

TRANSMIT CYCLE IS EMPTY States that the transmit cycle is empty for this RDF group.

APPLY CYCLE IS EMPTY States that the apply cycle is empty for this RDF group.

HOST INTERVENTION REQUIRED States that host-initiated MSC cleanup is required.

RECEIVE TAG = E0000000000005D5 APPLY TAG = E0000000000005D4

Shows the MSC/Star cycle tags for this RDF group, including the flag byte ('E0').

VALID RDFGRP FOUND 30 Verification of the SRDF/A recovery RDF group listed in this box scratch area.

VALID RDFGRP FOUND 30 Verification of the SRDF/A recovery RDF group listed in this box scratch area.

000187720744/ STAR J0 RDFGRP = 10 Star sync information.

SRDFA RCV RDFGRP = 30 J0 RCV RDFGRP = 30Recovery RDF group information in SRDF/A and SYNC(J0) target Symmetrix systems.

000187721688/ STAR J0 RDFGRP = 10 States sync information for Site A.

SRDFA RCV RDFGRP = 30 J0 RCV RDFGRP = 30Recovery RDFGRP information in SRDF/A and SYNC(J0) target Symmetrix systems.

CLEANUP

CASE2 - DISCARD ALL CYCLES States cleanup case information.

SRDFA SESSION = 000187751076/20 DISCARD RECEIVE CYCLE

Lists sessions (Symmetrix S/N and RDFGRP) that had action takenand what action was actually taken (commit or discard).Note: Both sessions are not listed - 2nd session Receive Delta set was empty.


Recovery Procedures

RECOVERY SUPPORT

DEVICE PAIRS TO CREATEPAIR FROM 000187751120 TO 000187720744 ON RDFGRP 30

Device pairing list header - Symmetrix S/N for CREATEPAIR source and target.

LOCAL DEVICE = 0000 REMOTE DEVICE = 0000LOCAL DEVICE = 0001 REMOTE DEVICE = 0001

Device pairing list for CREATEPAIR.

DEVICE PAIRS TO CREATEPAIR FROM 000187751076 TO 000187721688 ON RDFGRP 30

Device pairing list header - Symmetrix S/N for CREATEPAIR source and target.

LOCAL DEVICE = 0000 REMOTE DEVICE = 0000LOCAL DEVICE = 0001 REMOTE DEVICE = 0001

Device pairing list for CREATEPAIR.

OPEN FOR STARCNFG SUCCESSFUL# OF SESSIONS: 00000002WRITING $MSCRCV RECORD 00000000 00000000WRITING SESSION RECORD 00000001 00000001WRITING DEVICE RECORD 00000001 00000002WRITING SESSION RECORD 00000002 00000001WRITING DEVICE RECORD 00000002 00000002SAVSTRCF_XIT0

Diagnostic messages for device pairing list processing when //STARCNFG DD present.

SRDF Automated Recovery 473

Recovery Procedures

SRDF Automated RecoverySRDF Automated Recovery eliminates the need for external automation or manual intervention by automatically restoring SRDF/A to operational status following a planned or unplanned outage. You can configure the software to prompt you for authorization before proceeding with automated recovery.

SRDF Automated Recovery supports MSC (Multi-Session Consistency) environments. MSC provides consistency across multiple Symmetrix systems for SRDF/A groups. MSC is enabled by a Licensed Feature Code.

The primary MSC (with MSC_WEIGHT_FACTOR=0) performs the following functions:

◆ Detects that SRDF/A has dropped.

◆ Initiates the recovery automation sequence for each SRDF/A group in the MSC group. There is one independent sequence for each group.

◆ Waits for each of the recovery automation sequences to post completion to primary MSC.

◆ Performs an MSC restart.

Recovery automation tasks

The recovery automation sequence performs the following functions:

◆ If configured, preserves a consistent image of data at the remote site using TimeFinder/Mirror, based on policy defined in the SRDF Host Component initialization parameters. The TimeFinder/Mirror clone emulation facility can also be used.

• Enhances BCV management performance by exploiting the multi-attach feature of TimeFinder/Mirror. (Enginuity level 5x71 or later is required.) Multi-attach allows multiple device pairs to be attached on the same ESTABLISH or RE-ESTABLISH command syscalls.

• The output of the TimeFinder run will be written to the EMCTF file (if allocated): //EMCTF DD SYSOUT=*

◆ Validates that a user-specified minimum number of RDF directors are online.


Recovery Procedures

◆ Performs MSC cleanup.

◆ Automatically recovers SRDF/A at the RDF group level once the invalid track count has reached a user-specified level (default is 30000).

◆ Optionally, based on policy settings, reestablishes BCVs upon successful MSC restart.

The recovery automation can also be manually initiated. For example, it can be initiated following an F scfname,MSC,PENDDROP command or after being deferred when the PROMPT option is specified in the SRDFA_AUTO_RECOVER initialization parameter.

Tracking the automated recovery processSRDF Automated Recovery provides the ability to track the process using a LOCKDATA file to:

1. Know what recovery REXX EXEC is the next in the chain to be executed.

2. Know when the series of REXX EXECs in a recovery phase is complete.

3. Produce the summary of recovery steps and their individual return codes that appears in the SYSTSPRT of the recovery address space.

Each recovery action is uniquely identified by the date and time it started, the LPAR and started task ID of the recovery address space in which it is running, and the initial parameter string.

Under normal circumstances the LOCKDATA file is self-cleaning. The records are deleted when the summary that is written to SYSTSPRT is produced.

However, if a recovery step abends, the records are left in the file as a means of tracing which steps were complete or if a bad return code in a prior step may have contributed to the abend situation.

The following SAMPLIB member defines the LOCKDATA dataset:

EMC.SRDF.Vxxx.SAMPLIB(EHCGLOCK)


Recovery Procedures

Environment and system requirementsSRDF/A is supported by Symmetrix storage systems that are at Enginuity revision level 5670 and above.

The minimum software prerequisites needed to run automated recovery functionality are:

◆ SRDF Host Component for z/OS V5.5

◆ ResourcePak Base for z/OS V5.7

Restrictions◆ SRDF Automated Recovery does not support single-session

(non-MSC) SRDF/A environments.

◆ SRDF Automated Recovery does not support SRDF/S or SRDF/Star configurations.

◆ SRDF Automated Recovery does not run from secondary MSCs in a high-availability environment. It will run only from the primary (WEIGHT_FACTOR=0) MSC task.

◆ SRDF Host Component synchronization direction must be set to R1>R2 for all groups to be recovered.

User interfaceYou can configure SRDF Automated Recovery functionality using the following initialization statements:

◆ SRDFA_AUTO_RECOVER - enables/disables Automated Recovery.

◆ SRDFA_AUTO_RECOVER_MINDIR - specifies the minimum number of directors that must be online for the automation to begin execution.

◆ SRDFA_AUTO_RECOVER_ITRK - specifies the SRDF/A activation threshold.

◆ SRDFA_AUTO_RECOVER_BCV - specifies BCV management options.

◆ SRDFA_AUTO_RECOVER_PROC - allows you to change the name of the JCL recovery procedure (default EMCRCVRY).


Recovery Procedures

◆ MSC_INCLUDE_SESSION - includes the SRDF/A RDF group in the SRDF/A multi-session group. Within this statement, you can specify optional ITRK, MINDIR, BCV, and JOBNAME parameters to override the global values used by the corresponding SRDFA_AUTO_RECOVER statements. These overrides apply to the jobs submitted to recover the specific MSCgroup—they do not apply to the first auto recovery job that is submitted to perform validation and cleanup.

Note: The automated recovery process does not recognize any changes made to the initialization parameters. Once MSC is running (as noted by the “time of cycle switch” messages in the ResourcePak Base job log), those specific parameters will remain in effect until an MSC,REFRESH or MSC,DISABLE command is issued.

Chapter 3, “Configuration,” provides descriptions of these parameters.

Use the #SC RECOVER command to initiate SRDF Automated Recovery. “#SC RECOVER” on page 315 describes this command.

SRDF Automated Recovery procedureSRDF Automated Recovery executes automatically in response to an SRDF/A drop or via an operator command.

The recovery process consists of the following steps:

1. Validate that the environment is suitable for recovery automation to begin execution. All checks must complete successfully.

a. Obtain authorization to begin recovery automation if SRDFA_AUTO_RECOVER was set to PROMPT.

b. Ensure that the SRDF Host Component SYNCH_DIRECTION_ALLOWED initialization parameter is set to R1>R2 and SYNCH_DIRECTION_INIT is set to NONE.

Note: EMC recommends that the SYNCH_DIRECTION_INIT initialization parameter be set to NONE. However, if you set SYNCH_DIRECTION_INIT to R1>R2 rather than NONE, then skip step c.


Recovery Procedures

c. For RDF groups in the MSC environment, issue the #SC RDFGRP,cuu,ra,SYNCH_DIRECTION,R1>R2 command to set both sides of the group to the correct direction.

d. Check that SRDF links are available and the minimum number of SRDF directors specified in SRDFA_AUTO_RECOVER_MINDIR are operational.

A WTOR message is issued indicating that recovery operations have started. Link status will be continuously checked until links are available, at which point the message will be deleted automatically, or until the operator issues a cancel to the message.

2. Perform standard SRDF/A cleanup operations by executing EHCMSCME.

3. (Optional) Perform gold copy management.

If requested, a BCV copy of the R2 devices will be created according to the policies indicated in the SRDFA_AUTO_RECOVER_BCV startup option.

4. Create one address space per SRDF/A group for execution of REXX-based automation which will perform the following steps for each SRDF/A group:

a. Execute RNG-REFRESH and RNG-RSUM command sequences to resume SRDF operation.

b. Monitor SRDF R2 invalid tracks until the threshold set in SRDF_AUTO_RECOVER_ITRK is reached.

c. Once R2 invalid tracks have reached the specified level, activate SRDF/A.

5. In MSC environments, pass control back to the MSC task which will then activate MSC via an MSC RESTART.

6. (Optional) Perform gold copy management as specified in the SRDFA_AUTO_RECOVER_BCV post-recovery option.


Recovery Procedures

Resuming after an auto recovery failureIn the event that the recovery fails (for instance, if another link bounce occurs during the recovery process), resumption must be done manually.

If there is a link failure during auto recovery, the script will pause with a WTOR that indicates the failing SRDF Host Component command, as shown in the following example:

+EMCRX86E EMCMN00I SRDF-HC : (187) &SQ VOL,RMT(9566,01),RA(01) USER1 +EMCRX86E EMCPC10I ALL RDF LINKS ARE UNAVAILABLE FOR REQUESTED RAGROUP +(CMD:187) USER1 @97 EMCRX95R Reply CONTinue or CANcel

Before replying to the WTOR, determine the state of the devices for that particular script and take the appropriate actions. To restart the MSC process, you must do the following:

◆ Clear the host intervention indicator.

◆ Perform BCV management (if necessary).

◆ Confirm that the devices are ready on the link.

◆ Activate SRDF/A.

Complete the following steps to recover from a link failure:

1. Issue #SQ SRDFA,RMT(cuu,ra). Or, if that particular RDF group/link is down and there is another link to the remote box, either issue #SQ SRDFA,RMT(cuu,ra,ra-to-look-at) or issue #SQ SRDFA,RMT(cuu,ra,*). The wildcard "*" will display all of the RDF groups that have SRDF/A active (or host intervention).

2. If the host intervention indicator is set to 'Y' for any of the RDF groups in the MSC environment, run the EHCMSCME utility.


Recovery Procedures

3. If necessary, verify that the BCV management has taken place for each of the RDF groups. If the BCV management has not been done, take the appropriate steps to ESTABLISH or SPLIT as necessary. Query the BCVs to determine that they are in the correct state. Use #TF QUERY 1,RMT(cuu[,rdfgrp]),count[,symdv#]:

EMCMN00I SRDF-HC : (190) &TF QUERY 1,RMT(6C00,04),8,1E6 EMCVQ00I SRDF-HC DISPLAY FOR (190) &TF QUERY 1,RMT(6C00,04),8,1E6 354 BCVM046I *** EMC TIMEFINDER V5.5.0 (05) - SCF V05.07.00 (33) * BCVI018I (0000) QUERY 1,RMT(6C00,04),8,1E6 BCVM039I (0000) PROCESS INPUT STATEMENT BCVM004I QUERY STATUS THROUGH DEVICE 6C00, MICRO-CODE LEVEL 5X71 TYPE S ...BCV... ...STD... ACTION LAST CUU SYM# CUU SYM# ITRK-BCV ITRK-STD STATUS USED BCV EMUL #CYLS ---- 01E6R ---- 0090R 0 0 INUSE EST 01E6 3390 1113 ---- 01E7R ---- 0091R 0 0 INUSE EST 01E7 3390 1113 ---- 01E8R ---- 0092R 0 0 INUSE EST 01E8 3390 1113 ---- 01E9R ---- 0093R 0 0 INUSE EST 01E9 3390 1113 ---- 01EAR ---- 0094R 0 0 INUSE EST 01EA 3390 1113 ---- 01EBR ---- 0095R 0 0 INUSE EST 01EB 3390 1113 ---- 01ECR ---- 0090R 0 0 INUSE EST 01EC 3390 1113

4. Issue the appropriate #TF SPLIT 1,RMT(cuu,sym#bcv-sym#bcv[,rdfgrp]) or #TF RE-ESTABLISH 1,RMT(cuu,sym#bcv-sym#bcv[,rdfgrp]) command as needed for the BCV management requirements.

5. Issue the #SQ VOL,cuu,RA(grp) command for each RDF group in the MSC environment to determine the state of the devices.

a. If the devices are not ready on the link, and in synchronous mode, then they should be configured to ADCOPY-DISK mode:

EMCMN00I SRDF-HC : (3) &SQ VOL,6C00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (3) &SQ VOL,6C00,RA(04) 529 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D60 60 00A0 0090 04 EMC000 1113 ONPV 0 TNR-SY R1 0 0 ** 6D61 61 00A1 0091 04 EMC001 1113 ONPV 0 TNR-SY R1 0 0 ** 6D62 62 00A2 0092 04 EMC002 1113 OFFL 0 TNR-SY R1 0 0 ** 6D63 63 00A3 0093 04 EMC003 1113 ONPV 0 TNR-SY R1 0 0 ** 6D64 64 00A4 0094 04 EMC004 1113 ONPV 0 TNR-SY R1 0 0 ** 6D65 65 00A5 0095 04 EMC005 1113 ONPV 0 TNR-SY R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (4) &SC VOL,LCL(6C00,04),ADCOPY-DISK,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 535 0000-009F,00A6-00FF,0180-01EF,0210-027F,02B0-02CF,0330-035F, 03E2-06B9 EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:4) EMCGM41I REQUESTED DEVICES 537 00A0-00A5 EMCGM42I ELIGIBLE DEVICES 538 00A0-00A5 EMCGM43I COMPLETED DEVICES 539


Recovery Procedures

00A0-00A5 EMCGM07I COMMAND COMPLETED (CMD:4) EMCMN00I SRDF-HC : (5) &SQ VOL,6C00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (5) &SQ VOL,6C00,RA(04) 543 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D60 60 00A0 0090 04 EMC000 1113 ONPV 0 TNR-AD R1 0 0 ** 6D61 61 00A1 0091 04 EMC001 1113 ONPV 0 TNR-AD R1 0 0 ** 6D62 62 00A2 0092 04 EMC002 1113 OFFL 0 TNR-AD R1 0 0 ** 6D63 63 00A3 0093 04 EMC003 1113 ONPV 0 TNR-AD R1 0 0 ** 6D64 64 00A4 0094 04 EMC004 1113 ONPV 0 TNR-AD R1 0 0 ** 6D65 65 00A5 0095 04 EMC005 1113 ONPV 0 TNR-AD R1 0 0 ** END OF DISPLAY

b. If the devices are Target Not Ready (or not ready on the link), then the RDF-RSUM, RNG-REFRESH/RNG-RSUM process must be used:

EMCMN00I SRDF-HC : (5) &SQ VOL,6C00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (5) &SQ VOL,6C00,RA(04) 543 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D60 60 00A0 0090 04 EMC000 1113 ONPV 0 TNR-AD R1 0 0 ** 6D61 61 00A1 0091 04 EMC001 1113 ONPV 0 TNR-AD R1 0 0 ** 6D62 62 00A2 0092 04 EMC002 1113 OFFL 0 TNR-AD R1 0 0 ** 6D63 63 00A3 0093 04 EMC003 1113 ONPV 0 TNR-AD R1 0 0 ** 6D64 64 00A4 0094 04 EMC004 1113 ONPV 0 TNR-AD R1 0 0 ** 6D65 65 00A5 0095 04 EMC005 1113 ONPV 0 TNR-AD R1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (9) &SC VOL,LCL(6C00,04),RDF-RSUM,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 574 0000-009F,00A6-00FF,0180-01EF,0210-027F,02B0-02CF,0330-035F, 03E2-06B9 EMCCVAFI NO AVAILABLE LINKS FOR THE FOLLOWING DEVICES 575 0000-000D,0010-001B,0020-003F,0050-007F,008C-008F,0099,00F0-00F7, 0194-019D,01C0-01D3,0270-027F,02BD-02C2,0402-0507,0518-0541, 0546-0559,06A0-06A4 EMCCVCFE THE FOLLOWING DEVICES REQUIRE SPECIAL PROCESSING BEFORE RESUME 576 00A2 EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:9) EMCGM41I REQUESTED DEVICES 578 00A0-00A5 EMCGM42I ELIGIBLE DEVICES 579 00A0-00A5 EMCGM43I COMPLETED DEVICES 580 00A0-00A1,00A3-00A5 EMCGM07I COMMAND COMPLETED (CMD:9)

EMCMN00I SRDF-HC : (18) &SC VOL,RMT(6C00,04),RNG-REFRESH,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 647 0022-008F,0096-00F5,0108-0109,0170-0225,0238-0239,0240-282F, 2870-29D3 EMCCVE4E DEVICE 0090 PARTNER R1 IS NOT IN TNR STATUS (CMD:18) EMCCVE4E DEVICE 0091 PARTNER R1 IS NOT IN TNR STATUS (CMD:18) EMCCVE4E DEVICE 0093 PARTNER R1 IS NOT IN TNR STATUS (CMD:18) EMCCVE4E DEVICE 0094 PARTNER R1 IS NOT IN TNR STATUS (CMD:18) EMCCVE4E DEVICE 0095 PARTNER R1 IS NOT IN TNR STATUS (CMD:18) EMCCV1DI PROCESSING RANGE COMMAND FOR DEVICE 0092 FOR 1 DEVICES (CMD:18) EMCMN00I SRDF-HC : (19) &SQ VOL,RMT(6C00,04),RA(30) EMCGM40I COMMAND HAS FINISHED FOR BOX 000190300353 (CMD:18) EMCGM41I REQUESTED DEVICES 657 0090-0095 EMCGM42I ELIGIBLE DEVICES 658


Recovery Procedures

0092 EMCGM43I COMPLETED DEVICES 659 0092 EMCGM07I COMMAND COMPLETED (CMD:18) EMCQV00I SRDF-HC DISPLAY FOR (19) &SQ VOL,RMT(6C00,04),RA(30) 661 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % C450 50 0090 00A0 30 OFFLIN 1113 OFFL 0 R/O L2 0 0 ** C451 51 0091 00A1 30 OFFLIN 1113 OFFL 0 R/O L2 0 0 ** C452 52 0092 00A2 30 OFFLIN 1113 OFFL 0 R/O -R L2 0 0 ** C453 53 0093 00A3 30 OFFLIN 1113 OFFL 0 R/O L2 0 0 ** C454 54 0094 00A4 30 OFFLIN 1113 OFFL 0 R/O L2 0 0 ** C455 55 0095 00A5 30 OFFLIN 1113 OFFL 0 R/O L2 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (20) &SC VOL,RMT(6C00,04),RNG-RSUM,ALL EMCCV79I DEVICES IN RANGE ARE NOT IN SPECIFIED RDF GROUP: 664 0022-008F,0096-00F5,0108-0109,0170-0225,0238-0239,0240-282F, 2870-29D3 EMCCV1DI PROCESSING RANGE COMMAND FOR DEVICE 00A2 FOR 1 DEVICES (CMD:20) EMCGM40I COMMAND HAS FINISHED FOR BOX 000190300353 (CMD:20) EMCGM41I REQUESTED DEVICES 668 0090-0095 EMCGM42I ELIGIBLE DEVICES 669 0092 EMCGM43I COMPLETED DEVICES 670 0092 EMCGM07I COMMAND COMPLETED (CMD:20) EMCMN00I SRDF-HC : (21) &SQ VOL,6C00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (21) &SQ VOL,6C00,RA(04) 678 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D60 60 00A0 0090 04 EMC000 1113 ONPV 0 R/W-AD R1 0 0 ** 6D61 61 00A1 0091 04 EMC001 1113 ONPV 0 R/W-AD R1 0 0 ** 6D62 62 00A2 0092 04 EMC002 1113 OFFL 0 R/W-AD R1 0 0 ** 6D63 63 00A3 0093 04 EMC003 1113 ONPV 0 R/W-AD R1 0 0 ** 6D64 64 00A4 0094 04 EMC004 1113 ONPV 0 R/W-AD R1 0 0 ** 6D65 65 00A5 0095 04 EMC005 1113 ONPV 0 R/W-AD R1 0 0 ** END OF DISPLAY

6. Once the devices are ready on the link, activate SRDF/A:

EMCMN00I SRDF-HC : (22) &SC SRDFA,LCL(6C00,04),ACT EMCGM07I COMMAND COMPLETED (CMD:22) EMCGM40I COMMAND HAS FINISHED FOR BOX 000000006185 (CMD:22) EMCMN00I SRDF-HC : (23) &SQ VOL,6C00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (23) &SQ VOL,6C00,RA(04) 691 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D60 60 00A0 0090 04 EMC000 1113 ONPV 0 R/W-AS A1 0 0 ** 6D61 61 00A1 0091 04 EMC001 1113 ONPV 0 R/W-AS A1 0 0 ** 6D62 62 00A2 0092 04 EMC002 1113 OFFL 0 R/W-AS A1 0 0 ** 6D63 63 00A3 0093 04 EMC003 1113 ONPV 0 R/W-AS A1 0 0 ** 6D64 64 00A4 0094 04 EMC004 1113 ONPV 0 R/W-AS A1 0 0 ** 6D65 65 00A5 0095 04 EMC005 1113 ONPV 0 R/W-AS A1 0 0 ** END OF DISPLAY EMCMN00I SRDF-HC : (24) &SQ SRDFA,LCL(6C00,04) EMCQR00I SRDF-HC DISPLAY FOR (24) &SQ SRDFA,LCL(6C00,04) 694 MY SERIAL # MY MICROCODE ------------ ------------ 000000006185 5671-67 MY GRP ONL PC OS GRP OS SERIAL OS MICROCODE SYNCHDIR FEATURE ------ --- -- ------ ------------ ------------ -------- ------------ LABEL TYPE AUTO-LINKS-RECOVERY LINKS_DOMINO MSC_GROUP


Recovery Procedures

---------- ------- ---------------------- ---------------- ---------- 04 Y F 30 000190300353 5771-99 G(R1>R2) SRDFA ACTIVE EMCGRP04 DYNAMIC NO-AUTO-LINKS-RECOVERY LINKS-DOMINO:NO ---------------------------------------------------------------------- PRIMARY SIDE: CYCLE NUMBER 1 MIN CYCLE TIME 30 SECONDARY CONSISTENT ( Y ) TOLERANCE ( N ) CAPTURE CYCLE SIZE 0 TRANSMIT CYCLE SIZE 0 AVERAGE CYCLE TIME 0 AVERAGE CYCLE SIZE 0 TIME SINCE LAST CYCLE SWITCH 22 DURATION OF LAST CYCLE 0 MAX THROTTLE TIME 0 MAX CACHE PERCENTAGE 90 HA WRITES 1,495,244 RPTD HA WRITES 1,363,348 HA DUP. SLOTS 391 SECONDARY DELAY 22 LAST CYCLE SIZE 0 DROP PRIORITY 33 CLEANUP RUNNING ( N ) MSC WINDOW IS OPEN ( N ) SRDFA TRANSMIT IDLE ( Y ) SRDFA DSE ACTIVE ( N ) MSC ACTIVE ( N ) ---------------------------------------------------------------------- END OF DISPLAY

7. If the devices are ready on the link, and SRDF/A is active, then nothing needs to be done for that set of devices. Check the next RDF group:

EMCMN00I SRDF-HC : (181) &SQ VOL,6C00,RA(04) EMCQV00I SRDF-HC DISPLAY FOR (181) &SQ VOL,6C00,RA(04) 172 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SY SYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| % 6D60 60 00A0 0090 04 EMC001 1113 ONPV 0 R/W-AS A1 0 0 ** 6D61 61 00A1 0091 04 EMC002 1113 ONPV 0 R/W-AS A1 0 0 ** 6D62 62 00A2 0092 04 EMC003 1113 OFFL 0 R/W-AS A1 0 0 ** 6D63 63 00A3 0093 04 EMC004 1113 ONPV 0 R/W-AS A1 0 0 ** 6D64 64 00A4 0094 04 EMC005 1113 ONPV 0 R/W-AS A1 0 0 ** 6D65 65 00A5 0095 04 EMC006 1113 ONPV 0 R/W-AS A1 0 0 ** END OF DISPLAY

8. Once all of the RDF groups participating in the MSC environment have been made SRDF/A-active, issue the MSC RESTART command:

F MSFSCF8,MSC,RESTART SCF1390I MSC,RESTART SCF1391I MSC - RESTART COMMAND ACCEPTED. SCF1569I MSC - GROUP=MSFMSCAR STEAL LOCK AFTER = 120 MIN(S) SCF1435I MSC - GROUP=MSFMSCAR (6D00,04) FREEING SEL LOCKS SCF1435I MSC - GROUP=MSFMSCAR (9566,01) FREEING SEL LOCKS SCF1435I MSC - GROUP=MSFMSCAR (9A20,EA) FREEING SEL LOCKS SCF1426I MSC - GROUP=MSFMSCAR (6D00,04) GETTING SEL LOCKS

9. When global consistency has been reached, perform gold copy management as specified in the SRDFA_AUTO_RECOVER_BCV post-recovery option.

SC VOL Command Device Filtering 483

A

This appendix provides information about how the SC VOL command determines devices to be considered for processing. Topics include:

◆ Phase 1 filtering - determining devices for processing............... 484◆ Phase 2 filtering - validating devices ............................................ 486◆ Device processing ............................................................................ 487

SC VOL CommandDevice Filtering


SC VOL Command Device Filtering

Phase 1 filtering - determining devices for processingThis section describes the filtering process used to determine the set of devices to be considered for SC VOL command processing. The process starts with the set of all devices on the Symmetrix system identified by the gatekeeper/hop-list combination.

The filtering rules, each of which may remove devices from this set, are then successively applied. After all the rules have been applied, the remaining set of devices will be considered for processing.

Filtering rules

Note: In the following rule descriptions, the phrase 'devices <meeting certain conditions> are considered for processing' means that any devices not meeting those conditions will be removed from the set.

If ALL is specified for the device range, it is the same as if a numeric device range of 0000 to the maximum device number on the Symmetrix had been specified.

1. If an RDF group is specified (that is, LCL or RMT is used), only those devices in the specified range and also in the specified RDF group are considered for processing. If the specified range is ALL, then all devices in the specified RDF group are considered for processing.

2. If no RDF group is specified (neither LCL nor RMT is used), only devices in the specified range are considered for processing. If the specified range is ALL, then all devices on the Symmetrix array are considered for processing.

3. For certain commands applying only to R1s or R2s, devices with no mirror having the required SRDF personality are not considered for processing.

4. Power vault devices are not considered for processing.

5. If the FBA_ENABLE initialization parameter is not specified, FBA devices are not considered for processing. (If the FBA_ENABLE initialization parameter is specified, FBA devices are considered for processing if not otherwise excluded.)

Phase 1 filtering - determining devices for processing 485


Phase 1 completeAt the completion of the Phase 1 filtering process, the set of devices that will be considered for processing appears in the 'REQUESTED DEVICES' detail message if the COMMAND_DETAILS initialization parameter was specified. Any devices that were not considered for processing are treated as follows:

◆ Devices excluded because they did not belong to a specified/implied RDF group are listed in message EMCCV79I.

◆ Devices that were not considered for processing because they were FBA devices and FBA_ENABLE was not specified as an initialization parameter are not listed in any message.

If all devices have been eliminated from consideration, an error message such as EMCGM10I is issued (usually including the text 'COMMAND ABORTED') and command processing ends.

Comments

The intention of phase 1 filtering is to utilize a set of exclusion conditions not to be treated as errors, but just as a way to simplify specification of ranges of devices to be processed without having to deal with range gaps, device personalities, or the occurrence of device types desired by the command issuer (or system programmer) to be ignored.

Therefore, exclusion of a device during phase 1 filtering is treated neither as warranting an error nor a warning message. To do otherwise would undermine the purpose of phase 1 filtering.



Phase 2 filtering - validating devicesIf any devices have not been eliminated from consideration, a EMCGM41I or EMCGM48I message is issued listing the remaining devices. These remaining devices are then checked for eligibility based on device state and other considerations. This is known as validation. Devices that are determined to be eligible are listed in an EMCGM42I or EMCGM49I message. If a device fails to meet eligibility requirements, one of the following may take place:

◆ command processing may terminate immediately

◆ command processing may skip the device associated with the validation failure and continue with validation of the next device

After device validation, command processing may terminate if any devices have failed validation, or may continue on to processing of the eligible devices. The former results in an error return, the latter a warning. An example of the former is most dynamic RDF actions; an example of the latter is the exclusion of devices with an unacceptable sync direction.

If all devices were successfully validated, command processing continues on to device processing. If no devices were successfully validated, command processing terminates.

CommentsPhase 2 filtering may have either of two purposes, and two corresponding outcomes.

◆ If command processing will continue despite ineligibility of some devices, the filtering is essentially an extension of phase 1 filtering. However, in this case a warning condition is warranted.

◆ If command processing will terminate if any devices are found to be ineligible, an error condition is warranted.

Device processing 487


Device processingEligible devices are processed as required by the specified action. If an error is encountered, one of the following may take place:

◆ command processing may terminate immediately

◆ an attempt may be made to reverse all device changes, after which command processing terminates

◆ command processing may skip the device associated with the error and continue with the next device

When device processing is complete, an EMCGM43I or EMCGM4AI message is issued listing the devices that have been successfully processed. Depending upon the error handling, other messages may be issued listing devices for which errors were encountered.

Batch Interface 489

B

This appendix provides an overview of the SRDF Host Component batch interface. Topics include:

◆ Introduction ...................................................................................... 490◆ Example ............................................................................................. 493

Batch Interface


Batch Interface

IntroductionThe batch interface provides a mechanism to submit SRDF Host Component commands from a batch program and to retrieve the output from that command to a file. Output from the command is also echoed to the syslog, job log, and to the HCLOG file if active.

Details

The batch program, EMCSRDF, reads Host Component commands from SYSIN and displays output on the SYSPRINT file. The EMCSRDF batch program does not require APF authorization. Note that if the initialization parameters indicate that operator verification is required, a WTOR may be issued to the operator console, requesting confirmation for the requested action.

The LRECL for SYSIN can be up to 128 bytes. Commands on SYSIN start in column 1, and are entered in the same format as commands entered at the console.

You may continue a command onto multiple records by terminating a line with a (syntactically allowed) comma followed immediately by a hyphen (-). The continuation line must start in column 1.

The first byte(s) of the command must match the COMMAND_PREFIX setting for Host Component running on your system.

Commands are submitted one at a time, with each command waiting for the completion of the previous one. If a command fails, subsequent commands are flushed.

Sample JCL to run the batch utility appears in the SAMPLIB member EMCSRDF.

Support for the cqname= parameter is available for commands submitted either through the batch or the REXX interface.

◆ The #STOP command and the cqname= parameter are not supported from the batch interface.

◆ The #SC GLOBAL command is not supported for batch interface execution. #SC GLOBAL does not support the cqname= parameter and all commands issued through the batch interface now result in a cqname.

Introduction 491

Batch Interface

Note: “#SC GLOBAL” on page 301 provides more information.

The batch program, EMCSRDF, accepts a parameter on the EXEC statement as follows:

// EXEC PGM=EMCSRDF,PARM='cqname,failcode'

Where:

cqname

A default cqname to be applied to all commands in the input stream that do not have the cqname parameter coded.

failcode

The 1-byte failcode to be applied to all commands in the input stream that do not have the cqname parameter coded.

If cqname is coded in the PARM value, it must be from 1 to 15 alphanumeric characters, or a 1-byte value of asterisk (*). If failcode is coded, it must be one character, equal to P for purge or C for continue.

If PARM is omitted or if cqname is coded as an asterisk(*), EMCSRDF generates a default cqname for any command in the input stream that does not have cqname coded. The default name is

EMCdddhhmmssth

Where:

ddd

The current julian day of the year (0-366).

hhmmssth

A time stamp when the EMCSRDF program initiated.

If failcode is omitted, failcode defaults to blank.

The result of this additional support is that any command submitted to Host Component from the batch interface runs under a cqname. EMCSRDF submits all commands in the input stream to Host Component before checking for command completion. Command output is retrieved and printed to SYSPRINT as they are found to be complete.


Batch Interface

Note: Using the Host Component alias feature to create an alias for cqname is not supported by the batch interface.

For example, #SC VOL,G(MSFALL),SS,CQN (where cqn is aliased as cqname=msf) results in an error.

Example 493

Batch Interface

ExampleThe following example JCL invokes the batch utility to display Host Component global information as well as Symmetrix level and volume level information for the Symmetrix addressed by mainframe device number A046:

To run the sample, simply add a valid jobcard for your installation, and replace the mainframe device number in the #SQ commands with a valid mainframe device number for your installation.

The following shows output from the example:

//EMCSRDF JOB … //********************************************************************* //* * //* EMCSRDF: SAMPLE JCL TO RUN THE SRDF HOST COMPONENT BATCH UTILITY. * //* THIS PROGRAM READS COMMANDS FROM SYSIN AND DISPLAYS THE * //* COMMAND RESPONSE ON SYSPRINT. SRDF HOST COMPONENT MUST BE UP * //* AND RUNNING. * //* * //********************************************************************* //EMCSRDF EXEC PGM=EMCSRDF //STEPLIB DD DSN=EMC.SRDFHC.LINKLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * #SQ GLOBAL #SQ CNFG,A046 #SQ VOL,A046,10


Batch Interface

#SQ GLOBAL EMCQG00I SRDF-HC DISPLAY FOR (12) #SQ GLOBAL VERSION: 4.1.0 SYNCH_DIR_CURR: R1>R2 MSG_PROC: YES,512OPER_VERIFY: NONE SYNCH_DIR_ALWD: R1<>R2 LOG_DDNAM: HCLOG1CONFIG_FBA: ENABLED MAX_QUERY: 4000 MAX_CMDQ: 4095#SQ CNFG,A046 EMCGM11I SRDF-HC DISPLAY FOR (13) #SQ CNFG,A046 SERIAL NUMBER: 000184500193 MEM: 6,144 MB TYPE:3990 MODEL: 8430 MICROCODE LEVEL: 5566-27 LINKS-DOMINO: NO SYNCH_DIRECTION: GLOBAL LINK: LOCALSSID(S): A000 A001 A002 A003 A100 A101 A102 A103 0148 D01: DA D02: DA D03: RF D04: RF D05: SA D06: __ D07: __ D08: D09: __ D10: __ D11: __ D12: __ D13: EA D14: EA D15: DA D16: DAD17: DA D18: DA D19: RF D20: RF D21: SA D22: __ D23: __ D24: __D25: __ D26: __ D27: __ D28: __ D29: R1 D30: R1 D31: DA D32: DAD33: __ D34: __ D35: __ D36: __ D37: __ D38: __ D39: __ D40: __D41: __ D42: __ D43: __ D44: __ D45: __ D46: __ D47: __ D48: __D49: __ D50: __ D51: __ D52: __ D53: __ D54: __ D55: __ D56: __D57: __ D58: __ D59: __ D60: __ D61: __ D62: __ D63: __ D64: __END OF DISPLAY #SQ VOL,A046,10 EMCQV00I SRDF-HC DISPLAY FOR (14) #SQ VOL,A046,10 DV_ADDR| _SYM_ | |TOTAL|SYS |DCB|CNTLUNIT| | R1 | R2 |SYSYS CH|DEV RDEV GP|VOLSER| CYLS|STAT|OPN|STATUS |MR|INVTRK|INVTRK| %A046 46 0046 UGG046 1113 ONPV 0 R/W ML A047 47 0047 UGG047 1113 ONPV 0 R/W ML A048 48 0048 0048 00 UGG048 1113 ONPV 0 R/W-SY L1 0 0 **A049 49 0049 0049 00 UGG049 1113 ONPV 0 R/W-SY L1 0 0 **A04A 4A 004A 004A 00 UGG04A 1113 ONPV 0 R/W-SY L1 0 0 **A04B 4B 004B 004B 00 UGG04B 1113 ONPV 0 R/W-SY L1 0 0 **A04C 4C 004C 004C 01 UGG04C 1113 ONPV 0 R/W-SY B1 0 0 **A04D 4D 004D 004D 01 UGG04D 1113 ONPV 0 R/W-SY B1 0 0 **A04E 4E 004E 004E 01 UGG04E 1113 ONPV 0 R/W-SY B1 0 0 **A04F 4F 004F 004F 01 UGG04F 1113 ONPV 0 R/W-SY B1 0 0 **END OF DISPLAY

Director and Volume Status 495

C

This appendix describes the status of individual SRDF volumes and remote link directors, including their impact on the host, probable cause, and the actions required to return to a normal operating status. Topics include:

◆ Remote link director and the host ................................................. 496◆ SRDF volume statuses and the host .............................................. 497

Director and VolumeStatus


Director and Volume Status

Remote link director and the hostTable 29 provides an explanation of remote link director statuses and their relationship with the host.

Table 29 Link status and recovery

#SQ LINK

Host impact Probable cause Actions to return to normal statusCONN STATUS

Y ONLINE Normal status.

N ONLINE No synchronization can take place on this link; if all links are in this status, invalid R2 tracks accumulate on the source (R1) volume.

The link cables are physically disconnected, or the remote link director switch is offline, or an #SC LINK,cuu,dir#,OFFLINE command was issued for the remote partner Symmetrix.

Ensure that the cables are connected, and the remote link director switch is online. Issue an #SC LINK,cuu,dir#,ONLINE command at the remote partner Symmetrix, if necessary.

N OFFLINE No synchronization can take place on this link; if all links are in this status, invalid R2 tracks accumulate on the source (R1) volume.

An #SC LINK,cuu,dir#,OFFLINE command was issued for the local Symmetrix.

Issue an #SC Link,cuu,dir#,ONLINE command for the local Symmetrix.

SRDF volume statuses and the host 497


SRDF volume statuses and the hostTable 30 provides an explanation of SRDF volume statuses and their relationship with the host.

Table 30 Volume status and recovery

#SQ VOL

Host impact Probable cause Actions to return to normal statusCNTLUNIT STATUS

Device type

R/W-xx-x R1 Normal status.

R/O-xx-x R2 Normal R2 status.

The host may read from the target (R2) volume, but all host write I/O receive a Unit Check error (write disabled).

The default Symmetrix configuration status for target (R2) volumes.

An #SC VOL,cuu,R/O command was issued from the R2 host.

To set the target (R2) volume into recovery mode (host R/W), issue an #SC VOL,cuu,R/W command.

NR-xx-x R2 Optional R2 status.

The target (R2) volume does not come online during host IPL.

If an I/O is attempted, an intervention required status is returned.

A Symmetrix configuration option for target (R2) volumes.An #SC VOL,cuu,NRDY command was issued from the R2 host.

Issue an #SC VOL,cuu,RDY command.

R/W-xx-x R2 The host may write to the target (R2) volume.

An #SC VOL,cuu, R/W command was issued.

Issue an #SC VOL,cuu,R/O command.

LNR-xx-x R1 Link not ready, no synchronization occurs, R2 invalid tracks accumulate on the source (R1) volume.

The link is disabled (refer to Table 29 on page 496).

Issue an #SQ LINK,cuu command. Refer to Table 29 for recovery procedures.



TNR-xx-x R1 Target not ready, no synchronization occurs, R2 invalid tracks accumulate on the source (R1) volume.

An #SC VOL,cuu,RDF-SUSP command was issued from the R1 host, or under Enginuity 5x66 or higher, this may be caused when the links were up, SRDF operations were enabled, the target (R2) volume was read/write enabled, and a write was performed to the source (R1) volume.

Issue an #SC VOL,cuu,RDF-RSUM command, or if the cause is the target (R2) was R/W, set the target (R2) volume to read/only by entering an #SC VOL,cuu,R/O command, and follow the recovery procedures (starting with procedure 2) outlined in Chapter 6, “Recovery Procedures”.

RNR-xx-x R1 or R2

If I/O is attempted, an intervention required status is returned.

A device was operating in domino mode when the links or the SRDF partner failed, an #SC VOL,cuu,RDF-NRDY command was entered, or a target (R2) device went RNR due to the Invalid Track Attribute.

Ensure that the links and the partner device are ready, and issue an #SC VOL,cuu,RDF-RDY command.

UNR-xx-x User not ready. 1. A prior HOLD is on the BCV. There could be an active clone or snap to the device. Also, the status could be set by EMC Solutions Enabler symconfigure to manage access to the device.

2. A ConGroup-managed ECA-RDF window has closed with a UNR device state. Most commonly, ConGroup management of FBA devices.

1. Issue a CONFIG (TARGET(UNIT(device))READY(YES)RELEASE(YES) command from the TimeFinder/Clone Mainframe SNAP Facility.

2. Use the ECGCLEAN utility.

RWD-xx-x R1 Source volume is disabled to the link, no synchronization occurs, R2 invalid tracks accumulate on the source (R1) volume.

While the links were up and SRDF operations were enabled, and the target (R2) volume was read/write enabled, a write was performed to the source (R1) volume.

Set the target (R2) volume to read/only by entering an #SC VOL,cuu,R/O command, and resume normal SRDF operations from the source (R1) by entering an #SC VOL,cuu, RDF_WR_ENABLE command.

Note: If the R2 volume indicates R1 invalid tracks, you must RDF-SUSP the R1, and follow the recovery procedures (starting with procedure 2) outlined in Chapter 6, “Recovery Procedures.”

Table 30 Volume status and recovery (continued)

#SQ VOL

Host impact Probable cause Actions to return to normal statusCNTLUNIT STATUS

Device type

Enhancements 499

Cnvisible Body Tag

This appendix provides a comprehensive list of SRDF Host Component enhancements. The topic is:

◆ SRDF Host Component enhancements......................................... 500

Enhancements


Enhancements

SRDF Host Component enhancementsTable 31 lists SRDF Host Component enhancements introduced at each release.

Table 31 SRDF Host Component enhancements (page 1 of 12)

Release Enhancements

7.0 Support has been added for the 5874 Enginuity microcode level, including support for 128 directors and 250 RDF groups and virtualization of RAID architecture.

SRDF/ EDP (Extended Distance Protection) functionality has been added.

Composite command actions for Cascaded SRDF have been added to the SC VOL command.

Support has been added for dynamic ADD/DELETE of SRDF/A devices using the new CEXMPT (consistency exempt) option.

R22 device support has been added.

Large Open Systems volume and mainframe EAV support has been added to the SQ VOL and SQ MIRROR commands. Invalid track counts greater than 9999 are displayed in K up to 999K. Invalid track counts greater than 999K are displayed in M. In all cases 1K = 1024 and 1M = 1000*1K.

Support for displaying SE/SAE Open Systems host adapters has been added to the SQ CNFG command.

New filters have been added to the SQ VOL, SQ MIRROR, and SQ STATE commands.

5.6 Support has been added for the 5x73 Enginuity microcode level.

Support has been added for automated recovery within SRDF/A.

Support has been added for Cascaded SRDF operations.

MOVEPAIR action has been added for SC VOL command.

Support has been added for SRDF/A remote timestamps on the R2 device. SQ SRDFA SECONDARY TOD displays the approximate age of the last SRDF/A cycle that has been applied. For the age to be reported, the R1 side must also support this feature.

Documentation of the EMCMSGX_ON parameter statement has been removed from this release. This parameter will no longer be supported in future releases.

SRDF Host Component enhancements 501

Enhancements

5.5 Support has been added for the 5x72 Enginuity microcode level.

MSC support for the SRDF/A Transmit Idle state has been added.

MSC support of SRDF/A delta set extension pools has been added.

Support has been added for RAID 6 protected devices.

Host Component use of key 8 storage in CSA has been eliminated.

MSC VERBOSE message control has been added via the SCF1590I message, which is documented in the ResourcePak Base for z/OS Message and Code Guide.

MSC cleanup and reset utility EHCMSCM6 for SRDF/Star configurations will erase the BOXLIST, Scratch Area, and STAR indicator. To prevent this being run when it is not intended, a new WTOR has been added to confirm the erase action.

#SC BCV and #SQ BCV commands have been removed.

5.4 Device range support is implemented through the use of several new action parameters associated with the SC VOL command.

FBA Meta support within SRDF Host Component has been added. The SQ VOL command will only display the metahead information. The SC VOL command will act automatically on all the members in the meta device if the metahead is included in the command. SQ MIRROR will display the Meta head and all of the Meta members.

New state messages for SRDF/A with MSC have been added.

Issues warning that the #SC BCV and #SQ BCV commands will be removed in the next release of SRDF Host Component.

High availability support in MSC has been added.

Does not allow Tolerance Mode to be turned ON when MSC is active.

Adds the CGROUP API to prevent disabling of ConGroup protection in an SRDF/Star configuration.




Enhancements

5.4 Enhanced MSC utilities have been added. Previously the standalone utilities for MSC did not validate that they were APF authorized or that APF was available. This version validates that the program(s) are APF authorized and that SCF can be found. APF is the Authorized Program Facility of z/OS. The two utilities are used in conjunction with STAR implementations.

This version provides the option to VARY all devices in a group ONLINE/OFFLINE to all shared LPARs when SRDF Host Component issues a SC VOL, G(XXX) command.

Allows a usermod to suppress Symmetrix overrun EREP records. This feature provides the infrastructure to allow the user to install a usermod (that is, a user modification) to suppress Symmetrix Overrun records. Prevents overflowing of unwanted records.

5.3 Support has been added for 5x71 Enginuity level.

Support has been added for SRDF/Star

Support has been added for MSC redundancy.

Support has been added for Group Name Services.

5.2.1 Support has been added for controlling SRDF/A Multi-Session Consistency.

Support has been added to display GIGE statistics.

Support has been added for dynamic groups for GIGE directors

Support has been added for dynamic concurrent RDF devices.

Support has been added to display RAID 5 relationships.

5.2.0 Support has been added for controlling SRDF/A mode. Additionally, a monitor function is provided in EMCSCF.

Support has been added to SRDF Host Component for Unequal Size R1 and R2. This Symmetrix feature supports the establishment of an SRDF pair where the R1 device is smaller (fewer cylinders) than the R2 device. The devices must still be of the same emulation type, however. Resynchronization procedures are supported for sync-direction of R1>R2. Sync-direction R1<R2 is not supported.

Support has been added for dynamic RDF groups. This feature allows the creation, modification, and deletion of RDF groups.

Support of the Command Prefix Facility with up to an 8-character prefix.




Enhancements

5.1.0 Synchronize direction control at the RDF group level using SC SRDFGRP. Previously, Host Component changed personality of R1s and R2s only at the control unit level.

An enhanced #SQ CNFG command display lets customers and EMC employees verify Symmetrix configuration settings.

Adds support for the cqname parameter for commands submitted either through the batch or the REXX interface.

The EMCMSGX_ON parameter statement loads and enables a message exit.

Adds support of Remote Fibre Link statistics. Calculate % utilization similar to ESCON links. Enginuity level 5568 or higher.

References to MVS VOLSERs are now supported on many commands using VOL(vvvvvv) syntax.

5.0.0 Dynamic SRDF management (only available at Enginuity 5568 or higher).

Added support for IBM REXX language scripts and Host Component populated variables.

Added support for EMC Symmetrix Control Facility (EMCSCF).

Added the #TF command for direct pass-through of TimeFinder commands using native syntax.

ISPF interface provided for Host Component functions.

Message processing now supports a Log option.

Added sort by MVC CUU and VOLSER for device level Query commands.

4.2.0 Support added for concurrent SRDF. Enginuity 5567 or higher supports the ability for a single primary (source R1) volume to be remotely mirrored to two secondary (target R2) volumes concurrently. Concurrent SRDF is supported in both ESCON and Fibre Channel SRDF configurations. Commands have been enhanced to identify the secondary (target R2) device in both single and multihop configurations.

Support added for Switched SRDF. Enginuity 5x66 or higher support SRDF over Fibre Channel SRDF configurations. These configurations may involve switched fabrics. The RDF Group is used to identify the relationship between the primary (source R1) and secondary (target R2) devices on both dedicated or switch paths.

Enginuity 5567 or higher supports R1-R2 personality swap. Support added for R1-R2 personality swap with the addition of a SWAP action to #SC VOL command.




Enhancements

4.1.0 Defined Group support allows the definition of Groups that can be used on Query and configuration commands. Defined Groups allows one command to be issued to all devices that the command needs to be issued to.

Query Volume by state support allows a filter to be applied to the #SQ VOL command to retrieve only the devices that have the state requested. The list of states is long and is documented with the #SQ VOL command.

Query State support allows the viewing of the stacked statuses.This new query can be issued to see the complete status of the volumes. Refer to the #SQ STATE command.

Two new parameter values, (SAF,ANY) and (SAF,MASTER), have been added to the SECURITY_CONFIG initialization statement. When set to (SAF,ANY), the SAF interface is used unless from a console. If from a console, the command is allowed. When set to (SAF,MASTER), the SAF interface is used unless from a console. If from a console, the command is only allowed if console has master authority.

Dynamically build SSCT at MVS 5.2.0 and higher. If a SSCT is not found, one is built dynamically.

Support added for the maximum number of devices supported by Enginuity level 5x67.

INIT_VOLSER is a 6-character, user-defined, fill value for offline volumes. This value is used as the VOLSER for all OFFLINE devices.

The default starting device for a Remote command is the SRDF remote mirror.

The batch utility, EMCSRDF, submits commands from SYSIN to the Host Component and to retrieves command responses for display to SYSPRINT.

The edit macro, SRDFEDIT.CLIST, has been added as an installation enhancement.




Enhancements

4.0.0 MAX_ALIAS= initialization parameter added to specify the number of allowed ALIAS= initialization statements.

Added SHOW_COMMAND_SEQ#=YES|NO initialization parameter.

Support added for command queuing.

Command completion status checking. For all Host Component commands that change the status of a device, the device is checked to see that it successfully changed status. If so, the command terminates normally. Otherwise, the command is retried. After a predetermined number of unsuccessful retries, the command is failed and a message is issued.

If a #STOP command is entered and the command queues are not empty, an EMCMN99R message is issued. You may reply QUIESCE, IMMED, or CANCEL.

Dynamic Reconfiguration Volumes are noted by ‘DR’ in the ‘MR’ column of the #SQ VOL command display.

Consistency Group support:• The #SQ VOL,cuu,CGROUP command displays all devices that are in a consistency

group.• The #SC VOL,cuu,ADCOPY and #SC VOL,cuu,ADCOPY-DISK commands are

not allowed for a device in a consistency group.• The #SC VOL,cuu,RDF-SUSP and #SC VOL,cuu,RDF-RSUM commands are

not allowed for a device in a consistency group.• The #SC VOL,cuu,SUSP-CGRP command is not allowed for a device that is not in a

consistency group.




Enhancements

3.2.1 Full function support for Enginuity level through 5x65

Support added for 4096 devices on the #SQ/SC VOL RAID commands. New initialization parameter: MAX_QUERY=nnn - limits the maximum number of devices that can be displayed using a single #SQ VOL... command. This value defaults to 512. Starting device number is allowed to be specified for #SQ VOL command.

SMS Group support: G(smsgroupname) parameter available for #SC VOL and#SQ VOL commands.

Display and control devices across the links using RMT(cuu,ragroup#) (Enginuity 5x64 or higher).

Checkpoint to the Host Component scratch area (Enginuity 5x64 or higher).

Added the #SQ MIRROR command.

Added the #SQ RAID command.

Added the #SC VOL command action SUSP-CGRP for consistency group support.

Enhanced diagnostics using Symmetrix host initiated trace facility to log commands entered by user. (5x64 or higher).

Disabled Symmetrix Manager interface.

Added Userid and console id to HCLOG file.

3.1.1 Provided support for Symmetrix Enginuity level through 5x65 at the 5x64 functional level with up to 1024 logical volumes per supported Symmetrix.




Enhancements

3.1 Provided support for Symmetrix Enginuity level 5x64.

Added support for multi-tasking of SRDF commands to allow reconfiguration, display operations, and recovery testing procedures to be performed on multiple Symmetrix systems at the same time.

Symmetrix level synchronization direction: To enhance the multi-tasking support, the Host Component allows synchronization direction to be set at the Symmetrix level. “#SC CNFG” on page 299 provides more information.

Message labels: To enhance the multi-tasking support, the Host Component allows the option to add tags to command responses to identify to which Symmetrix they apply. Refer to the MESSAGE_LABELS initialization parameter.

Added option to have both commands and command responses to be logged to the HCLOG file. Refer to the HCLOG initialization parameter.

The #SQ VOL command output is now distinguished between TNR (target not ready) and LNR (link not ready).

The #SQ MSG command output has been enhanced to display a 4-digit year to provide for Year 2000 compliancy.

Added support for SIM exception code E454 to indicate that a volume with a long running channel program using suspend/resume logic (for example, a paging volume) has been automatically changed from synchronous mode to adaptive copy mode.

Added an option to allow SRDF Host component commands to change the operating characteristics of FBA volumes. Use the FBA_ENABLE initialization option and the #SC GLOBAL command actions FBA_ENABLE and FBA_DISABLE to control this option.

The #SQ CNFG command output now indicates the SRDF implementation used (LOCAL for campus solution or EXTENDED for extended distance solution).

The #SC SMMF and #SQ SMMF Time Finder commands have been renamed to the #SC BCV and #SQ BCV commands, respectively.

3.0.2 The #SC VOL,cuu,VALIDATE|INVALIDATE command actions are now available for all supported Enginuity levels and for all SRDF pairs, even if one or both devices are also locally mirrored or in a RAID group.

The output of the #SQ CNFG,cuu command has been enhanced to display up to eight SSIDS. The associated number of devices has been removed from the display. The#SQ SSID command output continues to display the number of devices detected for each SSID.




Enhancements

3.0.0 Added support for Symmetrix Enginuity level 5x63.

ISPF Interface: The TSO ISPF interface allows you to enter Host Component commands, and view the command responses from your TSO ISPF session.

The Symmetrix Time Finder facility: Provides the capability of dynamically establishing BCVs (Business Continuance Volumes) as mirror devices for existing primary devices. The #SQ SMMF command displays the current status of BCV volumes and connections. The #SC SMMF command is provided to establish the BCV connection, to split the connection, to reestablish the connection copying only the changed data on the primary device, and to restore partially or in total to the primary device from the BCV device.

Command Parameter Alias Facility: A facility has been provided for installation-defined aliases for all host component command parameters. This provides the capability to define abbreviated host component command parameters as well as to define names for commonly used device ranges.

SRDF Host Component Log File: An (optional) command log file is available to provide an audit trail of Host Component entered commands and the times they were entered. An optional secondary log file may also be specified, and a command is provided to switch logging from one log file to the other.

SMF Recording: An option is provided for SMF to record entered commands. The SMF record contains the source of the command, the userid and groupid used for security validation, and the text of the command before and after alias translation. This feature is activated and the SMF record number is specified using the “SMFREC=smf_record_number” initialization parameter.

Symmetrix Manager Interface: An interface is provided for the Symmetrix Manager product to send commands to and retrieve information from the Host Component. A version of the Symmetrix Manager, which is at a high enough level to support this feature, must be installed. The implementation of this feature is governed by the SYMMGR_INTERFACE initialization parameter.

The #SQ CNFG command output now provides the model of the Symmetrix unit, and also identifies EOS units. The display also indicates whether LINKS-DOMINO mode is in effect. The #SQ CNFG command has been enhanced to display up to 32 directors.

#SQ GLOBAL: The #SQ GLOBAL command now displays the ddname for the active Host Component log file.

#SQ LINK: A new keyword “,E” provides an extended display, which for each remote link director, displays its director group as well as the Symmetrix serial number, remote link director number, and director group on the partner Symmetrix unit.

The #SQ VOL command now identifies FBA devices.

The #SQ VOL command output has been enhanced to display the remote director group for each SRDF device as well as to indicate for which devices a validate or refresh command has been entered.




Enhancements

The #SC VOL command now allows for the specification of a range of devices. The range may be specified for the MVS CUU specification or for the Symmetrix device.

FBA devices are excluded from the effects of any #SC VOL command.

2.2.0 At Enginuity level 5062, two new #SC VOL command operands, REFRESH and RFR-RSUM, have been introduced to perform volume synchronization. When an SRDF pair is synchronized using REFRESH and RFR-RSUM, only the updated tracks are refreshed.

Service Information Messages (SIMs) as interpreted by the EMC9998W message are expanded into a more meaningful format. The output of the #SQ MSG command is similarly enhanced.

A new CNTLUNIT STATUS flag (RWD) has been added to indicate that SRDF operations were suspended because while the R2 device was in read/write mode, a write was attempted to the R1 volume. This status is reflected in the #SQ VOL command display for the R1 device. A new #SC VOL command operand, SRDF_WR_ENABLE, has been added to reset this status.

A new initialization parameter, EXCLUDE_DEVICE_RANGE, has been provided to exclude ranges of devices from SRDF Host Component processing.

2.1.0 Full user control of volume synchronization: R2 volume read/write testing recovery procedures have been enhanced to allow full control of the synchronization direction. This feature allows the user to specify resynchronization from the R1 volume(s) to the R2 volume(s) or from the R2 volume(s) to the R1 volume(s).

Improved ability to access remote volumes: It is now possible to suspend SRDF processing for a single SRDF pair to allow full Read/Write access to the R2 volume. In addition, the links no longer need to be brought offline to perform this function.

Support for Symmetrix Enginuity level 5062: The SRDF Host Component now supports level 5062 for up to 256 volumes per control unit. Level 5062 supports local mirroring on volumes that are also mirrored remotely. Volumes configured in this manner show a mirror type of L1 or L2 on the #SQ VOL command output display. All #SC VOL command actions are supported for L1 and L2 volumes except for VALIDATE and INVALIDATE.

Improved SRDF Link Control: All SRDF Links may be taken offline or online with a single #SC LINK,cuu,ALL,OFFLINE|ONLINE command. In addition, SRDF Host Component now allows taking the links offline when R2 volumes are in R/W status, or when R2 invalid tracks are detected.

Enhanced user control of Adaptive Copy: The ability has been added to control the relative rate of speed that the Symmetrix migrates updated tracks to the R2 volume when operating in the Adaptive Copy mode.

The RDFCNFG VSAM file has been added to provide the ability to save control information during subsystem operation for subsequent retrieval during a subsystem restart. (Note that this file is obsolete as of V5.0.)




Enhancements

Selectable Suppression of Confirmation Prompts: The OPERATOR_VERIFY initialization parameter has been added to allow the suppression of certain WTORs during configuration command processing.

New Subsystem-level Query Command: The #SQ GLOBAL command has been added to display subsystem-level status and parameter settings.

Message Table Customization: The MESSAGE_PROCESSING initialization parameter has been enhanced to accept an optional parameter, specifying the number of messages that may be retained in the message table.

The #SC VOL NADCOPY command action terminates Adaptive Copy mode of operation when the volume is in Adaptive Copy Disk mode or in Adaptive Copy Write Pending mode. The NADCOPY-DISK action is no longer supported.

The #SQ CNFG command output now displays the Symmetrix controller Enginuity patch level and patch date, and reports the ADC_MAX_SKEW value for controllers at level 5060.

The #SQ ADC command output now includes the Adaptive Copy rate.

The #SQ LINK command output now includes the remote adapter port count and physical port connection status.

2.0.3 Added support for 5061 Enginuity to support the expanded Adaptive Copy options AD (Adaptive Copy Disk mode) and AW (Adaptive Copy Write Pending mode). The #SC VOL command actions ADCOPY, NADCOPY, ADCOPY-DISK, and NADCOPY-DISK are supported.

The #SQ VOL command now displays a new status, TNR (Target Not Ready). This status displays when the SRDF pair is suspended (RDF-SUSP), or when all remote link adapters for the controller are offline or physically disconnected.

The #SC VOL,cuu,ADC-MAX,[dv#|ALL],value command sets the maximum Adaptive Copy Skew value for the device(s). This command is supported for Enginuity level 5061 or higher.

The #SQ ADC,cuu[,count|,ALL] command displays the Adaptive Copy Skew values for the specified device(s). Only Source (R1) devices in Adaptive Copy mode is displayed.

The #SC CNFG,cuu,ADCOPY_MAX_SKEW,count command replaces ADCOPY_MAX_ITRKS.

The #SQ CNFG command displays the Adaptive Copy Skew value, which reflects the maximum number of tracks to allow to be out of synchronization when in the Adaptive Copy mode. This value may range from 1 to 999,999. If the level is Enginuity 5061 or higher, ADCOPY: value displays as N/A.




Enhancements

2.0.1 Added a Dcopy dynamic flag.

Added the #SQ VOL,cuu,INV_TRK command option.

Added support for ALL option on the #SC VOL command actions VALIDATE and INVALIDATE.

Miscellaneous fixes and display format and message enhancements.

2.0.0 Included Data migration commands.

Added the #SC GLOBAL,SSID_REFRESH command.

Dynamic flags (except ADcopy).

Added SRDF suspend/resume flags commands.

Resync direction control commands.

Enginuity level validation (must be 5060 or higher).

Miscellaneous fixes and display format enhancement.




Enhancements


Glossary

This glossary contains terms related to the Symmetrix Remote Data Facility. Many of these terms are used in this guide.

Aadaptive copy disk

mode (AD)Symmetrix SRDF Adaptive copy disk mode is designed for bulk data transfer. Host write tasks accumulate on the primary volume rather than in global memory. A background process destages the write tasks to the corresponding secondary volume. When a skew value is reached, the primary volume reverts to its primary mode of operation, either synchronous or semi-synchronous, whichever is currently specified.

adaptive copy mode Symmetrix SRDF Adaptive copy modes facilitate data sharing and migration. These modes allow the primary and secondary volumes to be more than one I/O out of synchronization. The maximum number of I/Os that can be out of synchronization is known as the maximum skew value. The default value is equal to the entire logical volume. The maximum skew value for a volume can be set using the SRDF monitoring and control software.

adaptive copy writepending mode (AW)

With Symmetrix SRDF adaptive copy write pending mode, write tasks accumulate in global memory. A background process moves, or destages, the write-pending tasks to the primary volume and its corresponding secondary volume on the other side of the SRDF links.

When the maximum skew value is reached, the primary volume reverts to its primary mode of operation, either synchronous or semi-synchronous, whichever is currently specified. The device


Glossary

remains in the primary mode until the number of tracks to remotely copy becomes less than the maximum skew value. This mode is not supported for FICON or Enginuity 5772 and higher.

Application ProgramInterface (API)

A language and message format used by an application program to communicate with another program that provides services for it. APIs are usually implemented by writing function calls. Examples of APIs are the calls made by an application program to such programs as an operating system, messaging system, or database management system.

BBCV device A Symmetrix business continuance volume (BCV) that functions as a

mirrored media to a standard device for a protected storage environment.

BCV mirror BCV device upon establishing or reestablishing a BCV pair.

BCV pair A standard device and a BCV device that provide a protected storage environment.

bidirectional SRDF link If an SRDF group contains both primary and secondary volumes, write operations move data in both directions over the SRDF links for that group. This is called an SRDF bidirectional configuration.

business continuance An SRDF function that ensures business applications continue running despite possible disk failures.

business continuancevolume (BCV)

See “BCV device.”

Ccache Random access electronic storage used to retain frequently used data

from disk for faster access by the channel.

Cascaded SRDF A three-site SRDF replication configuration that provides a data recovery solution. This uses a device (R21) that is both and R2 to an R1 mirror and an R1 to an R2 mirror.

channel director The component in the Symmetrix subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.


Glossary

Concurrent SRDF Supports the ability for a single primary volume to be remotely mirrored to two secondary volumes concurrently. This feature is called concurrent SRDF and is supported in ESCON, Fibre Channel, and Gigabit Ethernet SRDF configurations. Concurrent SRDF requires that each remote mirror operate in the same primary mode, either both synchronous or both semi-synchronous, but allows either (or both) volumes to be placed into one of the adaptive copy modes.

consistency group A consistency group (CG, known as SRDF/CG) is a group comprised of primary SRDF devices, which have been enabled for remote point-in-time consistency. These SRDF consistency groups operate in unison to preserve the integrity and dependent-write consistency of a database distributed across multiple Symmetrix systems.

cycle time Time elapsed between SRDF/A cycle switch operations.

DDelta Set Extension

(DSE)Beginning with Enginuity version 5772, there is an additional option for managing the buffering of SRDF/A delta set data: SRDF/A Delta Set Extension (DSE). DSE provides a mechanism for augmenting the cache-based delta set buffering mechanism of SRDF/A with a disk-based buffering ability. This extended delta set buffering ability may allow SRDF/A to ride through larger or longer SRDF/A throughput imbalances than would be possible with cache-based delta set buffering alone.

destage The asynchronous write of new or updated data from cache to disk device.

device A uniquely addressable part of the Symmetrix subsystem that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry required to locate, read, and write data.

device address The hexadecimal value that uniquely defines a physical I/O device on a channel path in an MVS environment.

device number The value that logically identifies a disk device in a string.

diagnostics System level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking.


Glossary

director Component in the Symmetrix subsystem that allows Symmetrix to transfer data between the host channels and disk devices. See “channel director”and ”disk director.”

disk director The component in the Symmetrix subsystem that interfaces between cache and the disk devices.

domino attribute An optional feature for source volumes. When enabled, this feature causes a source volume to become not ready to its host and all I/O activity ceases with that volume if the target volume fails or a link failure occurs. When the fault condition is corrected, the user must manually make the source volume ready. This feature ensures that a remotely mirrored pair is always synchronized.

domino mode Symmetrix SRDF domino modes effectively stop all write operations to both source and target volumes if all mirrors of a source or target device fail or if any remote I/O can not be delivered to a target volume. If all SRDF links in a link group become unavailable, while such a shutdown temporarily halts production processing, domino modes can prevent data integrity exposure caused by rolling disasters.

dynamic sparing A Symmetrix feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all devices in the Symmetrix subsystem.

dynamic SRDFdevices

Dynamic SRDF functionality enables the user to create, delete, and swap SRDF pairs, using EMC host-based SRDF control software, while the Symmetrix system is in operation. Dynamic SRDF allows the user to create SRDF device pairs from non-SRDF devices, and then synchronize and manage them in the same way as static SRDF pairs.

dynamic SRDF group At Enginuity level 5669 or above, a user can dynamically create empty SRDF groups and dynamically associate the groups with Fibre Channel or GigE SRDF directors. Removing dynamic SRDF groups is also possible. Both of these operations are accomplished using EMC host-based SRDF control software. Dynamic SRDF groups created through this method are persistent through Symmetrix power on or IMPL.


Glossary

EEnginuity Enginuity is the operating environment for EMCs Symmetrix

Enterprise Storage Platforms. Enginuity provides functional services for both its host Symmetrix systems as well as for a large suite of EMC Storage Application software.

Ffast write In Symmetrix, a write operation at cache speed that does not require

immediate transfer of data to disk. The data is written directly to cache and is available for later destaging.

Ggatekeeper A small logical volume on a Symmetrix storage subsystem used to

pass commands from a host to the Symmetrix storage subsystem. Gatekeeper devices are configured on standard Symmetrix disks.

gigabyte (GB) 109 bytes.

GNS Group Name Service. GNS is the Symmetrix group definition sharing facility. GNS allows you to define a group of devices (and the controllers on which they reside) once, in one place, and then use that single definition across multiple EMC products on multiple platforms. That is, you can use group definitions created through GNS on a mainframe system with EMC software products running on open systems hosts.

GNS group A Group Name Service group. Each GNS group is a list of controllers and devices that reside on those controllers. The controllers and devices may reside on one Symmetrix storage subsystem or on different Symmetrix storage subsystems. If a GNS group spans more than one Symmetrix storage subsystem, each Symmetrix unit holds only its portion of that single definition.

Each group is a collection of controllers, and the devices that reside on those controllers. For groups that span Symmetrix storage subsystems, the definition is stored as a set of components on different Symmetrix storage subsystems. Each Symmetrix storage subsystem holds its portion of that single definition.


Glossary

Iidentifier (ID) A sequence of bits or characters that identifies a program, device,

controller, or system.

IML Initial microcode program loading.

invalid track An invalid track occurs when data is written to a disk track, and that data is not yet reflected on the partner device. The track on the partner device is said to be invalid. In the normal case where the source (R1) and target (R2) volumes are in communication and staying in synch, the updated track is passed to the target device and once it is written there, it is no longer invalid. If the source and target devices are not in communication for some reason, for instance, if the SRDF links are disabled, the invalid tracks build up over time. The R1 invalid track count can also be built up if the source (R1) volume is not ready to the host while the link is operational and data is being written to the source (R1) volume. Invalid tracks for the source (R1) volume may also be generated during R2 Read/Write testing. These may be cleared using the procedures outlined in “Recovery Procedures” on page 427.

invalid tracks attribute An attribute for target volumes. This attribute, when enabled, informs the host if a target volume did not complete synchronization with its source volume at the time of a second link failure.

invalidate Action for #SC VOL command that makes all tracks invalid for a target volume on a source volume.

I/O device An addressable input/output unit, such as a disk device.

Kkilobyte (KB) 1024 bytes.

known device A device that meets at least one of the following criteria and is not specified in the EXCLUDE_DEVICE_RANGE initialization statement:

• Found online during initialization

• Found online during an SC GLOBAL SSID_REFRESH

• Included in a Defined Group that was found online while processing a group command


Glossary

• Found because it was used as the z/OS device number in an INCLUDE_RAG initialization statement

• Found online or offline because it was used as the z/OS device number in an EXCLUDE_SYM initialization statement

Llink path A single ESCON light emitting diode (LED) fiber optic connection

between the two Symmetrix systems. A minimum of two to a maximum of eight links can exist between the two units.

local volume A Symmetrix logical volume that is not participating in SRDF operations. All CPUs attached to the Symmetrix may access it for read/write operations. It is available for local mirroring or dynamic sparing operations to the Symmetrix system in which it resides only.

logical volume A user-addressable unit of storage. In the Symmetrix subsystem, the user can define multiple logical volumes on a single physical disk device.

LPAR Logical partitioning, a system of splitting a mainframe computer‘s total resources into smaller units. The units essentially act as separate machines. Each unit can run with its own instance of the operating system and applications. The units, however, can communicate with each other.

Mmedia The disk surface on which data is stored.

megabyte (MB) 106 bytes.

MII Machine initiated interrupt.

mirroring The Symmetrix maintains two identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, Symmetrix automatically uses the other disk device.

mirrored pair A logical volume comprised of two physical devices with all data recorded twice, once on each device.


Glossary

multihop SRDF SRDF multihop topology allows you to daisy-chain three Symmetrix sites where a third site is providing business continuance backup to the remote RDF site. In a multihop scheme, the last site in the chain is two hops (SRDF links) away from the local or primary site.

Multi-SessionConsistency (MSC)

Beginning with Enginuity 5x71, SRDF/A is supported in configurations where there are multiple primary Symmetrix systems and/or multiple primary Symmetrix SRDF groups connected to multiple secondary Symmetrix systems and/or multiple secondary Symmetrix SRDF groups. This is referred to as SRDF/A Multi-Session Consistency (MSC). SRDF/A MSC configurations can also support mixed open systems and mainframe data controlled within the same SRDF/A MSC session.

PPDS Partitioned Dataset, a composite mainframe dataset that is much like

a directory in UNIX containing files, for example, source files. The members in a PDS are usually of the same type of data, for example, C language source files or header files.

physical ID Physical identification number of the Symmetrix director for EREP usage. This value automatically increments by one for each director installed in Symmetrix. This number must be unique in the mainframe system. It should be an even number. This number is referred to as the SCU_ID.

primary site The primary site is the site where the production workload is located. The primary site is typically the same as the primary DASD site.

primary DASD site The primary DASD site is the site where the source (R1) DASD is located. The primary DASD site is typically the same as the primary site.

promotion The process of moving data from a track on the disk device to cache. See also ”stage.”

RR1 See ”source volume (R1).”

R2 See ”target volume (R2).”


Glossary

R21 A dual-role SRDF R2/R1 device on the secondary site which acts as both an R2 to the primary site and an R1 to the tertiary site.

RA1 unit In an SRDF configuration, it is the primary data storage subsystem. It initiates many of the SRDF synchronization activities. An SRDF configuration must have at least one RA1 unit and one RA2 unit. See also ”RA2 unit.”

RA2 unit In an SRDF configuration, this subsystem maintains synchronization with the volumes it is paired with in the RA1 unit. It can serve as an RA1 unit during disaster recovery. An SRDF configuration must have at least one RA1 unit and one RA2 unit. See also ”RA1 unit.”

RAID Redundant array of independent disks.

RAID 5 A logical mirror configuration. In a RAID 5 mirror configuration, the data is written across multiple devices, with multiple stripes of data and one stripe of parity data being written in sets across all devices. The stripe containing the parity data is shifted across each device in the group. By spreading the parity evenly across all devices, I/O performance is increased. In the case of a disk failure, a stripe’s data can be reconstructed using the parity algorithm against the data in the available stripes.

read hit Data requested by the read operation is in cache.

read miss Data requested by the read operation is not in cache.

remote link director(RLD)

Each Symmetrix system requires a minimum of two up to a maximum of eight RLD directors, depending on the Symmetrix model in use. Each RLD manages two ESCON fiber link connections. Each RLD can perform a single I/O at a time to its paired RLD in the remote Symmetrix system.

Reserve Capacity SRDF/A Reserve Capacity enhances SRDF/A's ability to maintain an operational state when encountering network resource constraints that would have previously suspended SRDF/A operations. With SRDF/A Reserve Capacity functions enabled, additional resource allocation can be applied to address temporary workload peaks, periods of network congestion, or even transient network outages.


Glossary

SSAF Security access facility.

secondary site The secondary site is the site where the contingency or standby systems are located.

secondary DASD site The secondary DASD site is the site where the target (R2) DASD is located. The secondary DASD site will typically be the same as the secondary site.

semi-synchronousmode

An SRDF mode of operation that provides an asynchronous mode of operation. Applications are notified that an I/O (or I/O chain) is complete once the data is in the cache of the RA1 Symmetrix system. Any new data is then written to cache in the RA2 Symmetrix system. The RA2 Symmetrix system acknowledges receipt of the data once it is secure in its cache. If source tracks are pending transfer to a target volume and a second write is attempted to the source, Symmetrix disconnects (non immediate retry request), and waits for the pending track to transfer to the RA2 Symmetrix system.

single site workloadconfigurations

Single site workload configurations are configurations in which the primary site is the site where the production workload is located. See also “primary site.”

source volume (R1) A Symmetrix logical volume that is participating in SRDF operations. It resides in the “local” Symmetrix system. All CPUs attached to the Symmetrix may access a source volume for read/write operations. All writes to this volume are mirrored to a “remote” Symmetrix system. A source volume is not available for local mirroring operations.

SRDF Symmetrix Remote Data Facility. SRDF consists of the Enginuity and hardware required to support Symmetrix remote mirroring.

SRDF link One end-to-end SRDF connection between a given pair of Symmetrix systems.

SRDF/A SRDF/Asynchronous. SRDF/A provides a long-distance replication solution with minimal performance impact. SRDF/A provides a point-in-time image on the target (R2) device which is only slightly behind the source (R1) device. Data is transferred to a remote Symmetrix storage subsystem in predefined timed cycles called delta


Glossary

sets. This eliminates the redundancy of same track changes being transferred over the link.

SRDF/S SRDF/Synchronous. SRDF/S is a business continuance solution that maintains a real-time (synchronous) copy of data at the logical volume level in Symmetrix or Symmetrix DMX™ systems in the same or separate locations. The SRDF/S operation is transparent to the host operating system and host applications. It does not require additional host software for duplicating data on the participating Symmetrix units.

SRDF/Star SRDF/Star is a solution that operates in a concurrent SRDF configuration (A-to-B and A-to-C) where one remote mirror operates in SRDF/S mode (A-to-B) and the other remote mirror operates in SRDF/A mode (A-to-C). SRDF/Star provides for rapid reestablishment of cross-site protection in the event of primary site (A) failure.

Rather than a full resynchronization between sites B and C, SRDF/Star provides a differential B to C synchronization. This dramatically reduces the time required to remotely protect the new production site.

SRDF/Star also provides a mechanism to determine which site (B or C) has the most current data in the event of a rolling disaster that affects site A. When recovering from a primary site failure., users can choose:

◆ Which site to operate from

◆ Which site’s data to use

SSID Subsystem ID. For 3990 storage control emulations, this value identifies the physical components of a logical DASD subsystem. The SSID must be a unique number in the host system. It should be an even number and start on a zero boundary.

stage The process of writing data from a disk device to cache. See also “promotion”, “destage.”

storage control The component in the Symmetrix subsystem that connects Symmetrix to the host channels. It performs channel commands and communicates with the disk adapters and cache. See also ”channel director.”


Glossary

synchronous mode An SRDF mode of operation that ensures 100% synchronized mirroring between the two Symmetrix systems. This is a synchronous mode of operation. Applications are notified that an I/O (or I/O chain) is complete when the RA2 Symmetrix system acknowledges that the data has been secured in its cache.

Sysplex System complex. A processor complex which is formed by loosely coupling mainframe processors together into a single unit, using channel-to-channel adapters or ESCON or FICON fiber optic links.

Ttarget volume (R2) A Symmetrix logical volume that is participating in SRDF operations.

It resides in the “remote” Symmetrix system. It is paired with a source volume in the local Symmetrix system and receives all write data from its mirrored pair. This volume is not accessed by user applications during normal I/O operations. A target volume is not available for local mirroring or dynamic sparing operations.

Transmit Idle A Reserve Capacity enhancement to EMC's SRDF/A feature that provides the capability of dynamically and transparently extending the Capture, Transmit, and Receive phases of the SRDF/A cycle while masking the effects of an "all SRDF links lost" event. Without the SRDF/A Transmit Idle enhancement, an "all SRDF links lost" event would normally result in the abnormal termination of SRDF/A. The SRDF/A Transmit Idle enhancement has been specifically designed to prevent this event from occurring.

Vvalidate Action for #SC VOL command that makes all tracks for a source

volume valid on a target volume.

volume A general term referring to a storage device. In the Symmetrix subsystem, a volume corresponds to a single device visible to the host. In the context of host-based, volume manager software, a volume is a logical unit of disk storage that may comprise storage on one to many Symmetrix devices.


Aadaptive copy

ConGroup restriction 35displaying adaptive copy rate 180displaying skew values 180setting maximum skew value 327

ADC-MAX action 327ADCOPY action 327ADCOPY- DISK action 327ADCOPY_WP option 343, 349ADSRDF option 344

using 359ALIAS initialization parameter 93, 95, 134, 156,

157, 160alias statements, maximum number 121aliases, requirements 93ALLOW_CRPAIR_NOCOPY initialization

parameter 95APPEND_COMMAND=YES subparameter 145automated recovery 45Automated Recovery facility

SC RECOVER command 315SRDFA_AUTO_RECOVER parameter 156

automated recovery for SRDF 473automation products 25average cycle time 248

Bbatch interface 490BCV gold copy management 132, 157

CCA-ACF2 security package 25cache

installed, displaying 184limiting 42

capture cycle size 248capture tag 251Cascaded SRDF 30

creating an RDF set with CREATEPAIR 330removing device pairs with DELETEPAIR

331usage example 390, 394

CASCRE action 328, 343CASDEL action 328, 343CASRSUM action 329CASSUSP action 329CASSWAP action 329, 343CA-Top Secret security package 25CEXMPT COUNT 252CEXMPT option 345, 351# character 85cleanups 250command automation, SRDF Host Component

25command prefixes

defining 97registering 142

command queuing 28command syntax maps, how to read 176COMMAND_DETAILS initialization parameter

96COMMAND_PREFIX initialization parameter 97composite actions for Cascaded SRDF 52

Index


Index

concurrent RDF 30configuration commands

#SC CNFG command 299#SC GLOBAL command 301#SC LINK command 305#SC MSG command 306#SC RDFGRP command 307#SC RECOVER command 315#SC SRDFA command 316#SC VOL command 324TF command 363

configurations, SRDF/Star 48consistency exempt 47, 284consistency exempt devices 252, 259Consistency Group support 34consistency group, defined 34controller emulation type, displaying 184CREATEPAIR action 330, 331, 343cycle number 247

DDDname, displaying 196defined groups 68

examples 70excluding a range of Symmetrix units 102excluding devices 99excluding z/OS volumes 103including a list of z/OS devices 115including a list of z/OS volumes 117including an entire RA group 116including online and offline devices 106including R1 devices 108including R2 devices 109MVS Device Defined Groups 68rules for 68specifying a group name 111Symmetrix Device Defined Groups 68terminating the group definition 110

defining groups of Symmetrix devices 36DELETEPAIR action 331, 343delta set extension, query command 262delta set extension feature 43DIFFERENTIAL option 353directory type, displaying 184diskless R21 device 53DOMINO action 331

DSE feature 43DSEPOOL 43duration of last cycle 248dynamic exclude statements 103dynamic SRDF pairs, moving 402

EEAV support 36EHCMSCM6 458EHCMSCME 458EMCRCVRY procedure 160EMCRDF started task 85EMCSCF requirement 67EMCSCF test procedure 67EMCSRDF batch utility 36EMCTOOLS 26enhancements 499EXCLUDE_CUU initialization parameter 99EXCLUDE_DEVICE_RANGE initialization

parameter 100EXCLUDE_SYM initialization parameter 102EXCLUDE_VOL initialization parameter 103excluding a Symmetrix device 102Extended Distance Protection 53

FFBA devices 105FBA_ENABLE initialization parameter 105features

command completion status checking 34Consistency Group support 34ISPF 26remote Symmetrix query and config 34security 25

FILTER_KNOWN initialization parameter 106FILTER_ONLINE initialization parameter 107FILTER_R1 initialization parameter 108FILTER_R2 initialization parameter 109FORCE option 346

Gglobal sort order 112, 113group definition examples 70

MVS_GROUP 71SYM_GROUP 77


Index

GROUP_END initialization parameter 110GROUP_NAME initialization parameter 111GROUP_SORT_BY_MVSCUU initialization

parameter 113GROUP_SORT_BY_VOLSER initialization

parameter 112

HHCLOG dataset 27HCLOG initialization parameter 114HCLOGn datasets 114HDELETEPAIR action 332, 343HELP command 177HMOVEPAIR action 343hop, defined 34Host Component

initialization parameters 89initiating and terminating 85job log 27operating state, setting 301stopping 362

HSWAP action 333, 343

IIL 295IML, displaying total I/Os since last IML 200INCLUDE_CUU initialization parameter 115INCLUDE_RAG initialization parameter 116INCLUDE_VOL initialization parameter 117INIT_VOLSER initialization parameter 119initialization parameters 89

ALIAS 93, 95, 134, 156, 157, 160ALLOW_CRPAIR_NOCOPY 95COMMAND_DETAILS 96COMMAND_PREFIX 97EXCLUDE_CUU 99EXCLUDE_DEVICE_RANGE 100EXCLUDE_SYM 102EXCLUDE_VOL 103FBA_ENABLE 105FILTER_KNOWN 106FILTER_ONLINE 107FILTER_R1 108FILTER_R2 109GROUP_END 110GROUP_NAME 111

GROUP_SORT_BY_MVSCUU 113GROUP_SORT_BY_VOLSER 112HCLOG 114INCLUDE_CUU 115INCLUDE_RAG 116INCLUDE_VOL 117INT_VOLSER 119MAX_ALIAS 121MAX_COMMANDQ 122MAX_QUERY 123MESSAGE_LABELS 124MESSAGE_PROCESSING 125MSC_ACTIVATE_MS 126MSC_ALLOW_INCONSISTENT 127MSC_GROUP_END 129MSC_GROUP_NAME 130MSC_INCLUDE_SESSION 131MSC_STAR 136MSC_VALIDATION 137MSC_WEIGHT_FACTOR 138, 139, 171OPERATOR_VERIFY 140REGISTER_COMMAND_PREFIX 142SAF_CLASS 144SAF_PROFILE 145SECURITY_CONFIG 148SECURITY_QUERY 149SHOW_COMMAND_SEQ# 150SINGLE_CONCURRENT 151SMFREC 152SORT_BY_COMMAND 153SORT_BY_MVSCUU 154SORT_BY_VOLSER 155SRDFA_AUTO_RECOVER 156SRDFA_AUTO_RECOVER_BCV 157SRDFA_AUTO_RECOVER_ITRK 158SRDFA_AUTO_RECOVER_MINDIR 159SRDFA_AUTO_RECOVER_PROC 160SUBSYSTEM_NAME 161SYNCH_DIRECTION_ALLOWED 162SYNCH_DIRECTION_INIT 163USER_VERIFICATION 164USER_VERIFICATION_TIMEOUT 165VONOFF_BLOCKED 166VONOFF_OFF_ONLY 167VONOFF_ON_ONLY 168VONOFF_R1_ONLY 169VONOFF_STATUS_WAIT 171


Index

INT_VOLSER initialization parameter 119invalid track table, updating 342invalid tracks 281INVALIDATE action 334ISPF interface 26ITA action 334

JJCL recovery procedure, changing the name 160

LLCLISR2 option 354limiting cache 42link type, displaying 184Links Domino attribute 309Links Domino flag, setting 308LINKS-DOMINO mode 187, 240, 247, 265LOCKDATA file 474logical devices, displaying relationship with

physical devices 208

MMAX_ALIAS parameter 121MAX_COMMANDQ parameter 28, 122MAX_QUERY parameter 123maximum cache percentage 249maximum number of alias statements 121maximum number of displayed lines 123maximum number of queued commands 122maximum throttle time 249, 256message log, clearing 306message processing, displaying status of 196MESSAGE_LABELS initialization parameter 124MESSAGE_PROCESSING parameter 125messages, displaying 217minimum cycle time 247Mode Change feature 41MOVEPAIR action 334, 343MOVEPAIR, example 402moving dynamic SRDF pairs 402MSC recovery scenario 456MSC redundancy 138MSC_ACTIVATE_MS parameter 126MSC_ALLOW_INCONSISTENT parameter 127MSC_ALLOW_INCONSISTENT parameter 127

MSC_GROUP_END parameter 129MSC_GROUP_NAME parameter 130MSC_INCLUDE_SESSION parameter 131MSC_STAR parameter 136MSC_VALIDATION parameter 137MSC_WEIGHT_FACTOR parameter 138, 171MSC, multi session control 250multi-attach feature 473multihop remote configurations 34Multi-Session Consistency window 250multi-session definition 130MVS Device Defined Groups 68

NNADCOPY action 334NDOMINO action 335NITA action 335NOCOPY option 95, 355NOEXEC option 343nonoperational site 429NOSUSPEND option 355NRDY action 335

OOFFLINE action 335ONLINE action 335operational site 429OPERATOR_VERIFY parameter 140OPERATOR_VERIFY option 360OPERATOR_VERIFY setting, displaying 196

Pparameter settings, displaying 196parameter statements 89parity device, displaying 220, 223, 227physical devices, displaying relationship with

logical devices 208pool geometry 44PREFRESH action 336PRE-RSUM action 336Prevent Auto Links Recovery attribute 309primary side 247primary sites, Concurrent SRDF 56


Index

Qquery commands

#SQ ADC command 180#SQ CNFG command 184#SQ GLOBAL command 196#SQ LINK command 200#SQ LINK E command 203#SQ MIRROR command 208#SQ MSG command 217#SQ RAID command 220#SQ RAID10 command 231#SQ RAID5 command 223#SQ RAID6 command 227#SQ RDFGRP command 234#SQ SRDFA command 242#SQ SRDFA_DSE command 262#SQ SRDFA_VOL command 270#SQ SSID command 276#SQ STATE command 278#SQ VOL command 285

RR/O action 340R/W action 340R2 read/write testing 435R21 device 30, 53

removing pairings 331R22 devices 31, 58RACF security package 25RAGROUPs configuration, displaying 234RAID configuration, displaying 220, 223, 227RAID Virtual Architecture 38RAID, virtualizing 37RAID10 logical volume, displaying devices 231range support 338, 339, 340, 359RCVRY option 343, 357RDF_WR_ ENABLE action 337RDF-NRDY action 336RDF-RDY action 337RDF-RSUM action 337RDFSMFR 152RDF-SUSP action 337, 343RDY action 336recovery procedure, changing the name 160recovery procedures

link status 496

testing 432volume status 497

recovery utility 458requirements 459

redundancy,MSC 138REFCODE 218REFRESH action 338REGISTER_COMMAND_PREFIX parameter 142registering command prefixes 142remote link director, modifying the status of 305remote query and configuration 34resuming after an auto recovery failure 478resynchronization 432RFR-RSUM action 338RLDs, displaying port connection status 200RNG action codes 338, 339, 340, 359RNG actions 359RWD status, clearing 337

SSAF class name 144SAF interface 148SAF validation calls 145SAF_CLASS initialization parameter 144SAF_PROFILE initialization parameter 145#SC CNFG command 299#SC GLOBAL command 105, 301#SC LINK command 305#SC MSG command 306#SC RDFGRP command 32, 307#SC RECOVER command 315#SC SRDFA command 316SC VOL actions 327#SC VOL command 105, 324, 366SCF SAMPLIB member 36SCFRDFME 461secondary consistent 248, 254secondary delay 249secondary sites, Concurrent SRDF 56security 25SECURITY_CONFIG initialization parameter 148SECURITY_QUERY initialization parameter 149SEMI-SYNC action 340Service Information Messages (SIMs) 125, 217setting the synchronization direction 32SHOW_COMMAND_SEQ# parameter 150


Index

SINGLE_CONCURRENT parameter 151SMF records 152SMFREC initialization parameter 152SORT_BY_COMMAND parameter 153SORT_BY_MVSCUU initialization parameter 154SORT_BY_VOLSER initialization parameter 155#SQ ADC command 180#SQ CNFG command 184#SQ GLOBAL command 105, 196#SQ LINK command 200#SQ LINK E command 203#SQ MIRROR command 123, 208#SQ MSG command 217#SQ RAID command 220, 223, 227#SQ RAID10 command 231#SQ RAID5 command 223#SQ RAID6 command 227#SQ RDFGRP command 234#SQ SRDFA command 242#SQ SRDFA_DSE command 262#SQ SRDFA_VOL command 270#SQ SSID command 276#SQ STATE command 278#SQ VOL command 123, 285, 291, 292SRDF

displaying messages 217modifying status of volumes 324setting operational mode 324

SRDF Automated Recovery 45, 473procedure 476restrictions 475resuming after a failure 478SC RECOVER command 315

SRDF topologies 55SRDF/A, reporting age of last applied cycle 46SRDF/A transmit idle state 250SRDF/EDP 53SRDF/S to SRDF/A Mode Change 41SRDF/Star 50

configurations 48defining a definition 136validating device protection level 137

SRDFA A MSC 239, 246, 265SRDFA A STAR 239, 246, 265SRDFA ACTIVE 239, 246, 265SRDFA I MSC 239, 246, 265SRDFA I STAR 240, 246, 265

SRDFA INACT 239, 246, 265SRDFA_AUTO_RECOVER parameter 156SRDFA_AUTO_RECOVER_BCV parameter 157SRDFA_AUTO_RECOVER_ITRK parameter 158SRDFA_AUTO_RECOVER_MINDIR

parameter 159SRDFA_AUTO_RECOVER_PROC parameter 160SSIDs

displaying 184, 276displaying associated devices 276

stand-alone recovery utility 458requirements 459

STAR option 347STOP command 362SUBSYSTEM_NAME parameter 89, 161SWAP action 343swap operations 360Symmetrix

defining devices 36displaying microcode level 184displaying model number 184displaying serial number 184displaying status 184displaying volume status 285, 291, 292excluding devices from a controller 102setting operating state 299volume status, displaying 278

Symmetrix Device Defined Groups 68SYNC action 341synch direction, displaying 196SYNCH_DIRECTION setting 32SYNCH_DIRECTION_ALLOWED

parameter 162SYNCH_DIRECTION_INIT parameter 163synchronization

setting the direction 32starting 338, 340

SYSIN 36SYSPRINT 36

Ttertiary sites, Concurrent SRDF 56testing recovery procedures 432 to 453

performing R2 read/write testing 435 to 437resynchronize R1 greater than R2 443 to 445,

449 to 450


Index

resynchronize R1 less than R2 446 to 448, 451 to 453

selecting a synchronization method 440 to 442

TF command 64, 363tiered storage migration 37time lag reporting between R1 and R2 46TimeFinder

interface 64TF command 64

timeout 165TNR 295tolerance mode 248transmit cycle size 248Transmit Idle state 42

indicator 250turning on or off 319

transmit tag 252TSO ISPF interface 26tunable cache 42

Uuser defined groups, including only online

devices 107USER_VERIFICATION parameter 164USER_VERIFICATION_TIMEOUT

parameter 165

VVALIDATE action 342version, determining 196virtualized RAID 37VONOFF_BLOCKED parameter 166VONOFF_OFF_ONLY parameter 167VONOFF_ON_ONLY parameter 168VONOFF_R1_ONLY parameter 169VONOFF_R2_ONLY 170VONOFF_STATUS_WAIT parameter 171


Index

emc srdf host component for z/os - dell · emc corporation corporate headquarters: hopkinton, ma...

Documents