Contents

Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide PDF

1 of 248
1 of 248

Summary of Content for Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide PDF

October 2022

Rev 2.0.0

SRDF/TimeFinder Manager for IBM i Product Guide Version 10.0.0 and later

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Contents 3

Contents

Part I: SRDF/TimeFinder Manager Standard features

Chapter 1: Standard Features Introduction

Standard features description ............................................................................................................................... 19 Supported arrays and array features .................................................................................................................... 19

HYPERMAX OS and PowerMaxOS requirements ........................................................................................... 20 TimeFinder functionality ................................................................................................................................... 20 SRDF functionality ............................................................................................................................................ 22 Multiple SRDF configurations ........................................................................................................................... 23 Supported features for arrays running HYPERMAX os and PowerMaxOS ................................................... 23

Supported operations and configurations ............................................................................................................ 23 TimeFinder/Consistency Group ....................................................................................................................... 24

SRDF/TimeFinder terminology and restrictions .................................................................................................. 25 Terminology ....................................................................................................................................................... 25

Usage Restrictions ................................................................................................................................................ 25 User profile restriction ...................................................................................................................................... 25 Single instance restriction ................................................................................................................................ 26

Chapter 2: Configuration and Control Menus

Overview................................................................................................................................................................ 27 Navigating SRDF/TimeFinder Manager ............................................................................................................... 27 Accessing the main menu ..................................................................................................................................... 27 Dell EMC SRDF/TimeFinder Manager for IBM i main menu ............................................................................... 28 Control Menu......................................................................................................................................................... 29 Configuration by Image screen .............................................................................................................................. 31 Work with Associated Paths screen .................................................................................................................... 32 Disk Units screen................................................................................................................................................... 34 Running remote commands .................................................................................................................................. 39

Chapter 3: Operational Features, Settings, and Displays

Setting user-configurable preferences ................................................................................................................. 41 Controlling pop-up messages ............................................................................................................................ 41 Setting the restricted state wait time .............................................................................................................. 41 Controlling the SRDF/A Split wait time ........................................................................................................... 42 Viewing the current values in the FLSHCFG data area .................................................................................. 42 Resetting the lockbox password ...................................................................................................................... 43

Discovering array and host configuration details ................................................................................................ 43 Turning on the discovery process from the EMCCTL library ......................................................................... 43 Running the DISCOVER command................................................................................................................... 43 Turning off the Discovery Process .................................................................................................................. 44

Configuring node information ............................................................................................................................... 44 Accessing the node monitoring management facilities ................................................................................... 45 Adding a node ................................................................................................................................................... 46 Removing nodes ................................................................................................................................................ 46 Changing the Notify User parameter ............................................................................................................... 47 Controlling the monitoring of remote nodes ................................................................................................... 47

Configuring IFS files to support Solutions Enabler .............................................................................................. 47 Modifying the Solutions Enabler configuration files ........................................................................................ 48

Working with Solutions Enabler daemons ............................................................................................................ 48 Configuring daemons using the daemons options file ..................................................................................... 49

Working with the SYMAPI server ......................................................................................................................... 49 Configuring the SYMAPI server ....................................................................................................................... 50

4 Contents

Starting the SYMAPI Server............................................................................................................................. 50 Stopping the SYMAPI Server ............................................................................................................................ 51

Viewing version information .................................................................................................................................. 51

Chapter 4: Configuring the Environment

Configuration overview ......................................................................................................................................... 53 Configuring images................................................................................................................................................ 53

Adding ASPs to an image ................................................................................................................................. 53 Removing ASPs from an image ........................................................................................................................ 53

Configuring paths .................................................................................................................................................. 54 Predefined and user-defined paths.................................................................................................................. 54 Step Types ........................................................................................................................................................ 56

Working with paths ............................................................................................................................................... 56 Adding or creating paths .................................................................................................................................. 56 Removing or disassociating a path................................................................................................................... 59 Deleting a path .................................................................................................................................................. 60 Associating paths with an image ....................................................................................................................... 61

Configuring device pairs ....................................................................................................................................... 62 Pairing overview and rules for replication pairs ............................................................................................... 62 BCV device pairing ............................................................................................................................................ 63 TimeFinder/Clone device pairing ..................................................................................................................... 63 SnapVX device pairing ...................................................................................................................................... 63 Pairing devices .................................................................................................................................................. 63 Pairing Devices automatically ........................................................................................................................... 64 Pairing devices manually for BCV, Clone, or SnapVX devices........................................................................ 65 Viewing devices................................................................................................................................................. 67 Viewing mapping information ........................................................................................................................... 69 Viewing Disk Units in IBM i view ...................................................................................................................... 69 Displaying device details ................................................................................................................................... 69

Chapter 5: Controlling TimeFinder

Overview................................................................................................................................................................. 71 Establish/Re-establish BCV or Clone emulation pairs.......................................................................................... 71

Establish or re-establish BCV pairs ................................................................................................................... 71 Split BCV or Clone emulation pairs operation ...................................................................................................... 72

Restricted state and daemon jobs ................................................................................................................... 72 Split BCV pairs: Restricted state ..................................................................................................................... 73 Split BCV pairs: Hold jobs and job queues ....................................................................................................... 75 Split BCV pairs: Maintenance ........................................................................................................................... 76 TimeFinder Split: Split While Active ................................................................................................................. 76 Cancel BCV or Clone emulation pairs .............................................................................................................. 77

TimeFinder/Clone operations ............................................................................................................................... 78 Creating a Clone copy session ......................................................................................................................... 78 Activating a Clone copy session ....................................................................................................................... 78 Canceling or Terminating TimeFinder session ................................................................................................. 79

Canceling or terminating device pairs .................................................................................................................. 79 Unpairing BCV or Clone devices........................................................................................................................... 79

BCV device unpairing ........................................................................................................................................ 80 Clone device unpairing ...................................................................................................................................... 80

Recovering from a NotConsistent state .............................................................................................................. 80 TimeFinder/SnapVX operations ........................................................................................................................... 80

Establishing SnapVX session ............................................................................................................................ 80 Linking/Relinking Snapshots ............................................................................................................................ 85 Unlinking Snapshots.......................................................................................................................................... 86 Setting Time to Live ......................................................................................................................................... 86 Restoring Snapshots ......................................................................................................................................... 87 Terminating Snapshots ..................................................................................................................................... 87

Monitoring TimeFinder operations ....................................................................................................................... 87

Contents 5

Monitoring invalid and % copied tracks ........................................................................................................... 88 Automating TimeFinder operations ...................................................................................................................... 88

Chapter 6: Controlling SRDF

Overview................................................................................................................................................................. 91 RDF group or device compatibility .................................................................................................................... 91

Creating and controlling SRDF Groups ................................................................................................................. 91 Creating dynamic SRDF groups ....................................................................................................................... 92 Modifying dynamic SRDF groups (associated or dissociated local and remote director or port with RDF

group) ............................................................................................................................................................ 93 Removing dynamic SRDF groups ..................................................................................................................... 93

Setting the SRDF group attributes ...................................................................................................................... 93 Dynamic SRDF pairs .............................................................................................................................................. 96

Creating a device file ........................................................................................................................................ 96 Creating pairs .................................................................................................................................................... 96 Rules for dynamic concurrent SRDF pairing.................................................................................................... 97 Dynamic pairing restrictions ............................................................................................................................. 98 Deleting SRDF pairs .......................................................................................................................................... 98 Restrictions for deleting pairs .......................................................................................................................... 99 Deleting half pairs ............................................................................................................................................. 99

Setting modes of SRDF operation........................................................................................................................ 99 Consistency protection in SRDF/A mode...................................................................................................... 100 Enabling consistency protection .................................................................................................................... 100 Disabling consistency protection.................................................................................................................... 100

Establishing SRDF links ....................................................................................................................................... 100 Splitting or Suspending SRDF links operation .................................................................................................... 101

Splitting or Suspending SRDF links: Restricted state .................................................................................... 102 Suspend or Split SRDF links: Hold jobs and job queues ................................................................................. 103 Splitting or Suspending SRDF links: Maintenance mode .............................................................................. 105 Resuming SRDF operation ............................................................................................................................. 105

Controlling SRDF/Metro ..................................................................................................................................... 106 Setting up an SRDF/Metro configuration ..................................................................................................... 106 Removing an SRDF/Metro configuration ...................................................................................................... 106 Controlling witness and bias settings for SRDF/Metro ................................................................................ 106

Monitoring SRDF operations .............................................................................................................................. 109 Monitoring invalid and % copied tracks ......................................................................................................... 109

Recovering from NotConsistent SRDF state..................................................................................................... 109 Listing and monitoring SRDF groups .................................................................................................................. 109

Displaying SRDF group details ......................................................................................................................... 110 Performing dynamic SRDF personality swaps .................................................................................................... 110 Automating SRDF operations ............................................................................................................................... 111

Appendix A: Standard Features Commands Reference

Conventions.......................................................................................................................................................... 113 CRTDLTRDFP....................................................................................................................................................... 113 CRTNETCNFG...................................................................................................................................................... 115 CTLACT ................................................................................................................................................................ 116 CTLMASK ............................................................................................................................................................. 122 CTLRDFGRP......................................................................................................................................................... 123 CTLVWIT .............................................................................................................................................................. 127 DISCOVER ............................................................................................................................................................ 129 DISCOVERC ......................................................................................................................................................... 130 DSPVWIT .............................................................................................................................................................. 130 ENABLEDEV ......................................................................................................................................................... 130 ENDSTMSRV........................................................................................................................................................ 132 RELDEVLCK ......................................................................................................................................................... 132 RELDEVLCKC....................................................................................................................................................... 133 RTVSTMINF ......................................................................................................................................................... 133

6 Contents

SETBIAS ............................................................................................................................................................... 140 SETRDFGRP......................................................................................................................................................... 141 SETRDFMOD........................................................................................................................................................ 144 STMENDSBS ........................................................................................................................................................ 145 STMRMTCMD ...................................................................................................................................................... 146 STMSTRSBS ........................................................................................................................................................ 147 STORDAEMON .................................................................................................................................................... 147 STRSTMSRV ........................................................................................................................................................ 151

Appendix B: Symmetrix Integration Toolkit

Supported Solutions Enabler CLI commands ...................................................................................................... 153 Command line examples....................................................................................................................................... 153 Supporting documentation .................................................................................................................................. 154

Appendix C: Standard Features Messages

Appendix D: Miscellaneous Device Information

D910 device support (thin devices) .................................................................................................................... 175 Requirements and rules for D910 support ...................................................................................................... 175 Application impact............................................................................................................................................ 176 Performance impact ........................................................................................................................................ 176

Appendix E: Troubleshooting

Handling failed or non-reporting hardware resources ........................................................................................ 177 Error generated when running Discover command within SST ......................................................................... 177 Multipath reset ..................................................................................................................................................... 177 Error when running CRTSYMAPI or CRTSYMAPIC commands......................................................................... 178

Part II: SRDF/TimeFinder Manager Extended Features

Chapter 7: Extended Features Introduction

Extended features description ............................................................................................................................ 181 Independent ASP functionality ............................................................................................................................ 181

Two-node solution ........................................................................................................................................... 181 Three-node solution ......................................................................................................................................... 182 Four-node solution ........................................................................................................................................... 183

Chapter 8: Configuring for IASP Environment

Requirements ...................................................................................................................................................... 185 Cluster requirements ...................................................................................................................................... 185 IOA requirements ............................................................................................................................................ 185

Configuration procedures .................................................................................................................................... 186 Starting and stopping the server job .............................................................................................................. 186 Performing initial TimeFinder/SRDF operations............................................................................................. 187 Configuring an IASP image .............................................................................................................................. 188 Building or rebuilding the IOA file .................................................................................................................... 189 Making target devices visible to the DR or Backup nodes ............................................................................ 189

Configuring the environment for IASP ................................................................................................................ 189 Prepare cluster and IASP nodes..................................................................................................................... 190 Start the server............................................................................................................................................... 190 Configure paths .............................................................................................................................................. 190 Configure an IASP session............................................................................................................................... 191 Populate the IOAs for each node in the cluster ............................................................................................. 192 Post-configuration considerations .................................................................................................................. 193

Chapter 9: IASP-Supported Operations

Contents 7

IASP-supported operations................................................................................................................................. 195 Three-node planned failover (DR) and recovery solution ............................................................................. 195 Three-node failover and recovery (unplanned) solution ............................................................................... 196 Backup operations ........................................................................................................................................... 197 Restore operations .......................................................................................................................................... 198 Managing a four-node solution with a high availability node ........................................................................ 199 Source to source processing for IASPs ......................................................................................................... 200

SRDF/TimeFinder Manager IASP-specific menu options ................................................................................. 202 Establish/create, split/activate, link/relink, and cancel/terminate operations ........................................... 202 Adding or removing IOAs ................................................................................................................................ 204 Varying on and varying off IASP images locally............................................................................................. 205 Varying on and varying off IASP images remotely ........................................................................................ 205 Displaying an IASP configuration by ASP ...................................................................................................... 206 Removing image information .......................................................................................................................... 207

Performing IASP control actions ........................................................................................................................ 207 Performing IASP control actions on primary node ........................................................................................ 207 Performing IASP control actions on DR or backup node .............................................................................. 208 Performing SRDF or TimeFinder control actions on DR or backup node..................................................... 209 Preparing target HA node............................................................................................................................... 209 Performing SRDF control actions during DR on primary node ...................................................................... 211

Automated operations.......................................................................................................................................... 212 Failing over and failing back ............................................................................................................................ 212 Preparing the source or target nodes for backup .......................................................................................... 212

Appendix F: Non-Dell Procedures

Overview............................................................................................................................................................... 213 Displaying contents of a physical file on each node ........................................................................................... 213 Verifying IOA information..................................................................................................................................... 214

Appendix G: Extended Features Commands Reference

Conventions.......................................................................................................................................................... 215 ADDRMVIOA......................................................................................................................................................... 216 CRTNETCNFG...................................................................................................................................................... 217 CTLACT ................................................................................................................................................................ 217 CTLACTTGT ......................................................................................................................................................... 217 DISCOVER ........................................................................................................................................................... 222 DISCOVERC ........................................................................................................................................................ 223 ENDSTMSRV....................................................................................................................................................... 223 IASPCTL .............................................................................................................................................................. 223 IASPCTLC ............................................................................................................................................................ 227 IASPCTLHA ......................................................................................................................................................... 228 IASPFAILBK ......................................................................................................................................................... 229 IASPFAILOV.......................................................................................................................................................... 231 IASPFILE .............................................................................................................................................................. 233 IASPTFBCK.......................................................................................................................................................... 234 IASPTFEST .......................................................................................................................................................... 236 RELDEVLCK ........................................................................................................................................................ 238 RELDEVLCKC...................................................................................................................................................... 238 RTVSTMINF ........................................................................................................................................................ 238 SETRDFMOD....................................................................................................................................................... 238 SETRDFMODC .................................................................................................................................................... 238 SRDFDRCTL ........................................................................................................................................................ 239 STMRMTCMD ...................................................................................................................................................... 241 STRSTMSRV ........................................................................................................................................................ 241

8 Contents

Appendix H: Extended Features Messages

Glossary ............................................................................................................................................ 251

Figures 9

Figures

1 Multiple arrays single image .......................................................................................................................... 23 2 TimeFinder/CG ................................................................................................................................................... 24 3 Dell EMC SRDF/TimeFinder Manager for IBM i main menu ............................................................................ 28 4 Control Menu ...................................................................................................................................................... 29 5 Configuration by Image screen ........................................................................................................................... 31 6 Configuration by Image screen collapsed .................................................................................................... 32 7 Work with Associated Paths screen overview ............................................................................................ 33 8 Disk Units screen ................................................................................................................................................ 34 9 Disk Units IBM i View screen ............................................................................................................................. 34 10 Disk Units screen SVX type of step ............................................................................................................. 38 11 Display Data Area screen with FLSHCFG data area with default values ......................................................... 42 12 Run Discover Process (DISCOVER) screen ...................................................................................................... 44 13 The Display Node Information screen................................................................................................................ 45 14 Add Node Information Screen............................................................................................................................ 46 15 Control Dell EMC daemon proc (STORDAEMON) screen ............................................................................... 47 16 Create SYMAPISVR netconfg file (CRTNETCFG) screen ............................................................................... 50 17 Control Dell EMC daemon proc (STORDAEMON) screen ............................................................................... 51 18 Program Version Information screen ................................................................................................................. 52 19 Work with Available Paths screen ..................................................................................................................... 56 20 Work with Associated Paths screen add path ............................................................................................. 57 21 Paths not Associated with the Image screen.................................................................................................... 58 22 Paths Defined on the System screen ................................................................................................................ 58 23 New paths added to screens ............................................................................................................................. 59 24 Disassociating a Path screen ............................................................................................................................. 60 25 Deleting a Path Associated with an Image screen ............................................................................................ 60 26 Deleting a Path Not Associated with an Image screen..................................................................................... 61 27 Work with Associated Paths screen associating paths with image ............................................................ 61 28 TimeFinder Pairing Options screen .................................................................................................................... 64 29 Device File used for SnapVX .............................................................................................................................. 65 30 Disk Units screen with Pair option for device not paired ................................................................................. 65 31 Type of the target device screen ...................................................................................................................... 66 32 All STD/BCV devices of matching screen......................................................................................................... 66 33 Disk Units screen with device paired ................................................................................................................. 67 34 Disk Units screen Clone type of step ........................................................................................................... 68 35 Disk Units screen SnapVX type of step ....................................................................................................... 68 36 Mapping View screen ......................................................................................................................................... 69 37 Disk Units screen IBM i View ........................................................................................................................ 69 38 Disk Units Details screen for thin device ........................................................................................................... 70 39 Confirm Establish BCV pairs and CLONE emulation pairs screens .................................................................. 72 40 Split operation for BCV or Clone emulation pairs ............................................................................................. 73 41 STM End All Subsystem (STMENDSBS) screen .............................................................................................. 74 42 System not in restricted state screen ............................................................................................................... 74 43 Confirmation Window screen ............................................................................................................................. 75 44 Jobs Not on Hold and Job Queues Not on Hold screens ................................................................................. 76 45 Confirm Cancel BCV pairs and CLONE emulation session screens ................................................................. 77 46 EMC SRDF/TimeFinder Ctrl (CTLACT) screen create Clone session ....................................................... 78 47 Confirm Recreate CLONE copy session screens .............................................................................................. 78 48 Confirm Terminate CLONE Session .................................................................................................................. 79 49 Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen create SnapVX session ............................................ 81 50 Work with Associated Paths .............................................................................................................................. 82 51 Existing Snapshots screen ................................................................................................................................. 82 52 Work with Snapshots screen ............................................................................................................................. 83 53 Rename Snapshot screen................................................................................................................................... 83

10 Figures

54 Snapshot Details screen ..................................................................................................................................... 84 55 List of Snapshots screen.................................................................................................................................... 85 56 Link Option screen.............................................................................................................................................. 86 57 Set Time to Live screen ..................................................................................................................................... 87 58 Control Dynamic RDF Group (CTLRDFGRP) screen ........................................................................................ 92 59 Set SRDF Group (SETRDFGRP) screen ........................................................................................................... 94 60 Create/Delete RDF pairs with Control Action CREATE ............................................................................... 97 61 Create/Delete RDF pairs with Control Action DELETE .............................................................................. 98 62 Set SRDF Mode (SETRDFMOD) screen ........................................................................................................... 99 63 Split or Suspend SRDF links operation ............................................................................................................. 101 64 STM End All Subsystems (STMENDSBS) screen ........................................................................................... 102 65 System not in restricted state screen ............................................................................................................. 103 66 Confirmation Window screen ........................................................................................................................... 104 67 Jobs Not on Hold and Job Queues Not on Hold screens ............................................................................... 104 68 Confirm Resume Link screen ........................................................................................................................... 105 69 vWitness Control Action screen ...................................................................................................................... 107 70 Display vWitness Information ........................................................................................................................... 108 71 SRDF Metro Set Bias screen ........................................................................................................................... 108 72 List of the SRDF Groups screen ...................................................................................................................... 109 73 SRDF Group Information screen ....................................................................................................................... 110 74 Two-node cluster and two-node DR configuration ........................................................................................ 182 75 Three-node DR environment............................................................................................................................ 182 76 Four-node high availability setup ..................................................................................................................... 183 77 Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen ........................................................................................ 187 78 Configure IASP Session screen with configuration detail .............................................................................. 188 79 Configure IASP Session screen......................................................................................................................... 191 80 Source to source processing for IASPs ........................................................................................................... 200 81 Dell EMC IASP File Utility (IASPFILE) screen ................................................................................................. 207 82 Dell EMC Independent ASP Ctrl (IASPCTL) screen with ADDIOA action ..................................................... 208 83 Dell EMC SRDF/TimeFinder Control (CTLACTTGT) screen with CREATE action ....................................... 209 84 Dell EMC IASP HA Control (IASPCTLHA) screen........................................................................................... 210 85 Dell EMC SRDF DR Control (SRDFDRCTL) screen ......................................................................................... 211 86 Displaying the contents of a physical file ........................................................................................................ 213

Tables 11

Tables

1 HYPERMAX OS and PowerMaxOS requirements............................................................................................. 20 2 Predefined and user-defined configurations and paths.................................................................................... 54 3 Supported step types for SRDF and TimeFinder operations............................................................................ 56 4 Configuration actions for replication types ....................................................................................................... 62 5 Steps in the path and its associated action after personality swap ............................................................... 110

Preface 13

Preface

As part of an effort to improve its product lines, Dell Technologies periodically releases revisions of its software and hardware. Some functions that are described in this document are not supported by all versions of the software or hardware that are in use. The product release notes provide the most up-to-date information about product features.

Contact your Dell Technologies representative if a product does not function properly or does not function as described in this document.

NOTE: This document was accurate at publication time. New versions of this document might be released on the Dell Online Support site. Check the Dell Online Support site to ensure that you are using the latest version of this document.

Product information SRDF/TimeFinder Manager for IBM i is a set of utilities that provides an IBM i interface to PowerMax, VMAX All Flash, VMAX3, and VMAX arrays. The product contains a Remote Data Facility (SRDF) control facility and a TimeFinder control facility. See for more detail.

SRDF/TimeFinder Manager also provides extended features for the IBM Independent Auxiliary Storage Pools (IASP) functionality. There are also facilities to display and assign multiple TimeFinder BCV devices. See Extended features description for more detail.

Purpose This product guide shows how to:

Configure and use the SRDF/TimeFinder Manager for IBM i.

Use the IBM Independent Auxiliary Storage Pools (IASPs) which are a set of switchable or private auxiliary disk pools.

Audience This guide is for the IBM i security officer and operator, who control the SRDF and TimeFinder environment using IBM i host software.

Readers of this guide are expected to be familiar with the following:

IBM i operating environments

PowerMax, VMAX All Flash, VMAX3 Family, and VMAX Family arrays operating environment

SRDF and TimeFinder operation

Related documentation The following documents provide additional information about SRDF/TimeFinder Manager and Solutions Enabler:

Dell Solutions Enabler Release Notes Describes new features and any known limitations.

Dell Solutions Enabler Installation and Configuration Guide Provides host-specific installation instructions.

Dell Solutions Enabler CLI Reference Guide Documents the SYMCLI commands, daemons, error codes, and option file parameters provided with the Solutions Enabler main pages.

Dell Solutions Enabler SRDF Family CLI User Guide Shows how to configure and manage SRDF environments using SYMCLI commands.

Dell Solutions Enabler TimeFinder SnapVX CLI User Guide Shows how to configure and manage TimeFinder SnapVX environments using SYMCLI commands.

SRDF Interfamily Connectivity Information Defines the versions of PowerMaxOS, HYPERMAX OS, and Enginuity that make up valid configurations for SRDF remote replication.

Dell PowerMax Security Configuration Guide Describes how to configure PowerMax Family security settings.

Dell VMAX All Flash and VMAX 3 Security Configuration Guide Describes how to configure VMAX All Flash and VMAX Family security settings.

14 Preface

The following documents provide additional hardware platform information:

Dell PowerMax Product Guide Contains information relating to PowerMaxOS on the PowerMax and VMAX All Flash arrays.

Dell VMAX All Flash Product Guide Contains information that is related to the VMAX All Flash arrays.

Dell VMAX 3 Product Guide Contains information that is related to the VMAX3 arrays.

Dell PowerMaxOS 10.0.0.0 Release Notes Describes new features and any known limitations.

E-Lab Interoperability Navigator (ELN) Provides a web-based interoperability and solution search portal. You can find the ELN at https://elabnavigator.dell.com/eln/elnhome.

Typographical Conventions used in this document This document uses the following type style conventions:

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, and utilities URLs, pathnames, filenames, directory names, system names, links, groups, service keys, file systems, and

notifications

Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and main pages

Used in procedures for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus What the user selects, clicks, presses, or types

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 the command line User input variables

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

[ ] Square brackets enclose optional values.

| Vertical bar indicates alternate selections. The bar means or.

{ } Braces enclose content that the user must specify, such as x or y or z.

... Ellipses indicate nonessential information that is omitted from the example.

Preface 15

Where to get help Dell Technologies support, product, and licensing information can be obtained on Dell Online Support.

NOTE: To open a service request through Dell Online Support, you must have a valid support agreement. Contact your Dell Technologies sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Product information For documentation, release notes, software updates, or for information about Dell products, licensing, and service, go to Dell Online Support (registration required) at: https://dell.com/support/home.

Technical support Dell Technologies offers various support options.

Support by Product Dell Technologies offers consolidated, product-specific information about the Web at: https://dell.com/support/home.

The Support by Product web pages offers quick links to Documentation, White Papers, Advisories (such as frequently used Knowledgebase articles), and Downloads, as well as more dynamic content, such as presentations, discussion, relevant Customer Support Forum entries, and a link to Dell Live Chat.

Dell Technologies Live Chat Open a Chat or instant message session with a Dell Support Engineer.

e-Licensing support To activate your entitlements and obtain your license files, go to the Service Center on http://dell.com/support/home, as directed on your License Authorization Code (LAC) letter emailed to you.

For help with missing or incorrect entitlements after activation (that is, expected functionality remains unavailable because it is not licensed), contact your Dell Account Representative or Authorized Reseller.

For help with any errors applying license files through Solutions Enabler, contact the Dell Customer Support Center.

If you are missing a LAC letter, or require further instructions on activating your licenses through the Online Support site, contact Dell Technologies worldwide Licensing team at licensing@dell.com or call:

North America, Latin America, APJK, Australia, New Zealand: SVC4EMC (800-782-4362) and follow the voice prompts.

EMEA: +353 (0) 21 4879862 and follow the voice prompts.

Your comments Your suggestions help to continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

powermaxcontentfeedback@dell.com.

SRDF/TimeFinder Manager Standard features 17

I

SRDF/TimeFinder Manager Standard features

Part I of this product guide describes the menus, configuration for SRDF/TimeFinder Manager, and shows how to control TimeFinder and SRDF replication sessions. It contains the following chapters and appendixes:

Standard Features Introduction

Contains an overview of SRDF/TimeFinder Manager for IBM i and introduces the components that it supports for the SRDF family and TimeFinder family of replication solutions.

Configuration and Control Menus

Describes the SRDF/TimeFinder Manager configuration and control menus.

Operational Features, Settings, and Displays

Shows how to set up, maintain, and display the SRDF/TimeFinder Manager environment.

Configuring the Environment

Shows the configuration steps that allow for control of SRDF and TimeFinder replication environments with IBM i hosts.

Controlling TimeFinder

Shows how to control TimeFinder operations using the SRDF/TimeFinder Manager Control Menu.

Controlling SRDF

Shows how to control SRDF links, including how to enable and disable consistency protection for SRDF/A and set the RDF mode.

Standard Features Commands Reference

Contains reference information, syntax, and examples for control commands.

Symmetrix Integration Toolkit

Lists the supported Solutions Enabler CLI commands that are packaged with the SRDF/TimeFinder Manager software in the Integration Toolkit, and provides some examples.

Standard Features Messages

Lists the messages that SRDF/TimeFinder Manager components may produce.

Miscellaneous Device Information

Describes miscellaneous device information such as device pairing compatibility and variable LUN support.

Troubleshooting

Provides some troubleshooting information for SRDF/TimeFinder Manager.

Standard Features Introduction 19

1

Standard Features Introduction

This chapter provides an overview of SRDF/TimeFinder Manager for IBM i and introduces the components that it supports for the SRDF family and TimeFinder family of replication solutions.

This chapter also introduces the switchable Independent Auxiliary Storage Pool (IASP) functionality that SRDF/TimeFinder Manager provides for disaster recovery and backup operations in combined IBM i and array environments.

Topics:

Standard features description Supported arrays and array features Supported operations and configurations Load Source Mirroring SRDF/TimeFinder terminology and restrictions Usage Restrictions

Standard features description SRDF/TimeFinder Manager is a set of host-based utilities that provides an IBM i interface to Remote Data Facility (SRDF) and TimeFinder. You can use the SRDF/TimeFinder interface to configure and control SRDF or TimeFinder operations on PowerMax, VMAX All Flash, VMAX3, and VMAX arrays attached to IBM i hosts. Those operations are:

Run TimeFinder commands to establish and split TimeFinder BCV devices where BCVs are used for local mirroring, or are used as the source device in multihop replication solutions.

Create point-in-time copies of full volumes, or individual datasets using TimeFinder/Clone copy sessions.

Create logical point-in-time snapshots of images for:

Arrays running PowerMaxOS 10 (6079) using TimeFinder SnapVX.

Arrays running PowerMaxOS 5978 using TimeFinder SnapVX.

Arrays running HYPERMAX OS 5977 using TimeFinder SnapVX.

Run SRDF commands to perform establish and split operations for local replication solutions, or for extended-distance replication solutions, such as SRDF/Asynchronous (SRDF/A).

SRDF/TimeFinder Manager provides support for the IBM i host environment, such as multipath, boot from SAN, and independent ASP (IASP) functionality.

Supported arrays and array features SRDF/TimeFinder Manager is used in environments that contain PowerMax, VMAX All Flash, VMAX3, and VMAX arrays.

The following rules and requirements apply to VMAX 10K arrays and arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977:

D910 device emulation only. Emulation for 2107 devices is not available.

Thin devices only. Thick devices are not available.

Thin (bound) gatekeeper devices only.

NOTE: Meta devices are available on VMAX 10K arrays but not on arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977.

20 Standard Features Introduction

HYPERMAX OS and PowerMaxOS requirements The version of or HYPERMAX OS or PowerMaxOS that you need depends on the type of storage array:

TimeFinder functionality The TimeFinder family of local replication software allows users to nondisruptively create and manage point-in-time copies of data to allow operational processes, such as backup, reporting, and application testing to be performed independent of the source application, and to maximize service levels without impacting performance or availability.

TimeFinder technologies available on HYPERMAX OS or PowerMaxOS

TimeFinder SnapVX is the TimeFinder technology available on arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977. TimeFinder/Mirror and Clone commands can be run on PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977, but emulations use SnapVX as the underlying technology. When running emulation sessions, devices cannot be a SnapVX source or a link target. When devices are SnapVX sources or link targets they cannot be used for emulation sessions. TimeFinder/Snap sessions are not supported. There is no emulation for this local replication type.

TimeFinder SnapVX

SnapVX creates point-in-time copies directly in the Storage Resource Pool (SRP) of the source device, thus eliminating the concepts of target devices and source/target pairing. If point-in-time data is needed, linked targets are created. The maximum number of SnapVX snapshots for each source device is 256.

Storage Resource Pools

All point-in-time data that is saved in the SRP of the source device is limited by the TF_reserve_capacity as defined in the SRP. Once this limit is reached no more allocations are allowed for snapshot data. Point-in-time data is saved in the SRP using a shared allocation mechanism. For multiple snapshots that are saving the same tracks, only one track is saved in the SRP.

Snapshot identification

Snapshots have a user-supplied name. The same name may be used for multiple devices or multiple snapshots. For multiple snapshots a generation number is produced to differentiate point-in-time copies of the same name on the same devices. Snapshots and their associated generation numbers are ordered by a timestamp. The most recent snapshot is generation 0. Older snapshots are consecutive increasing positive numbers. As snapshots are established and terminated, the generation numbers are reassigned by snapshot timestamps so there are no gaps in the generation numbers.

The snapshot names are assigned by the user at the time that the snapshot is established. After that, snapshots are uniquely identified for subsequent commands by name, source device, and generation number. If the generation number is omitted, generation 0 is assumed. Snapshots are established on source devices only. The point-in-time copy data is saved in the SRP of the source device.

Snapshot Termination and Restore

Snapshots can only be terminated when there are no links. Snapshots may be set for automatic termination with an optional Time To Live setting specified in days. Snapshots automatically terminate when the Time to Live has expired (plus or minus 15 s), but only if there are no links. If the Time to Live has expired on a snapshot with one or more links, the snapshot is terminated when the last link has been unlinked. A specific date can also be entered. Both date and days must be in the range of 400 days. If no date or day is entered, it remains until manually deleted. A snapshot with an expiration day or date will not automatically expire if it is linked.

Table 1 HYPERMAX OS and PowerMaxOS requirements

Storage array Required version of HYPERMAX OS and PowerMaxOS

PowerMax Family PowerMaxOS 10 (6079)

VMAX All Flash Family PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977

VMAX3 Family HYPERMAX OS 5977

Standard Features Introduction 21

Restore to the original source device is supported and is differential by default. If the original source device is a link target of another snapshot, the link must be fully copied prior to the restore.

Failed Snapshots

A snapshot can fail if no more allocations can be made from the SRP for the snapshot or if a corruption occurs on the source device. To recover a Failed snapshot terminate and reestablish it.

Consistent Snapshots

By default all snapshots are consistent. Depending on the state of the devices at the time of the snapshot, Local ECA or SRDF/A is used to ensure that I/O is paused while the snapshot is created.

The following rules apply to the source devices, when the snapshot is created, in order to ensure that the snapshot is consistent:

A mixture of R1 and R2 devices is not allowed.

A mixture of R1 and non-RDF devices is allowed. The R1 devices can be a mixture of RW and NR on the RDF link.

A mixture of R2 and non-RDF devices is allowed if the R2 devices are NR on the RDF link.

A mixture of R1 and R21 devices is allowed if the R1->R21 is NR on the RDF link.

A mixture of R2 and R21 devices is allowed:

if the R1->R2 and the R1->R21 are all RW on the RDF link.

if the R1->R2 and the R1->R21 are all NR on the RDF link.

NOTE: When SnapVX is used remotely and there are several SRDF groups in the configuration, SRDF mode for the links should be synchronized or links should be split.

If the source devices do not meet these criteria, then the snapshot cannot be created.

Managing Point-in-time data

SnapVX defaults to only having the source device participating in the sessions. If point-in-time data is needed, the user creates one or more links from the snapshot session to one or more target devices. Links can be created in Copy mode for a permanent copy on the target device, or in NoCopy mode for temporary use. Linked point-in-time copies can be mapped to and made visible to a host. Point-in-time copies are identified by a user-supplied name and device.

In SRDF/TimeFinder Manager pairing is done from a device file.

Linking rules

The target device must be of equal size as or larger than the source device.

Maximum number of linked targets per source device is 1024.

Host writes to a linked target device do not change the point-in-time copy, so only the linked target device contains a modified point-in-time copy. To restore a modified point-in-time copy to the original source device, a snapshot from the target device must be established followed by a Copy mode link of that snapshot to the source device. When the copy is complete both the link and the target devices snapshot may be removed.

A relink command automatically unlinks an existing link to a snapshot and links to a new selected snapshot. When the relink is performed, the copy is differential between the original linked snapshot and the newly linked snapshot.

The relink command is also used to relink to the same snapshot. This has the effect of refreshing the point-in-time copy on the link target when it has been modified by host writes.

A link to a target that has a snapshot may not be removed until the link is fully copied. If the link is a NoCopy, it must first be changed to Copy and then removed when fully copied.

When a device is used as a link target, all its previous track allocations are deallocated. Any pre-existing data on the target is lost during a link or relink. When a link with Copy mode is issued and the data is fully copied; the point-in-time data remains on the target device when an unlink is issued.

When a link with NoCopy mode or Copy mode is issued, but the data is not fully copied, after the unlink the integrity of the data is uncertain.

Devices with persistent track allocations cannot be used as links targets.

22 Standard Features Introduction

Linked devices must have all tracks that are defined before being used as a source for another snapshot.

A link can fail if:

Allocations are no longer available from the SRP associated with the link device. If more space is added to the SRP, it may be possible to recover from a failed link. Otherwise, the link must be terminated and reestablished.

A corruption occurs on the link device, the failed link must be terminated and reestablished.

SRDF functionality Within the SRDF family of software, SRDF/TimeFinder Manager provides:

SRDF Cascaded replication

SRDF Extended Distance Protection (SRDF/EDP)

SRDF Reserve Capacity with Transmit Idle

SRSF/A Delta Set Extension (DSE)

SRDF/Synchronous (SRDF/S)

SRDF/Asynchronous (SRDF/A)

Concurrent SRDF/S

Concurrent SRDF/A

SRDF/A MultiCycle

SRDF/Metro

NOTE: SRDF/S and SRDF/A are two of the SRDF base products. Except where noted, SRDF/S and SRDF/A are called SRDF in this guide.

For detailed information about configuring SRDF for IBM i, see Controlling SRDF.

Ensuring data integrity

SRDF/TimeFinder Manager prevents suspension of the SRDF links under conditions that can result in inconsistent data on the target volumes.

Internal mechanisms on the array maintain the status of every track stored in the system. In an SRDF configuration, a track status is invalid until the data that is received from a host write request is written to both the source and target arrays.

In synchronous mode, the array responds to the host with access to the source (R1) device on a write operation only after the array containing the target (R2) device acknowledges that it has received and checked the data.

When the command to suspend the SRDF links are started, SRDF/TimeFinder Manager checks for invalid tracks. There should be little or no write activity from the host, because normal operation is to perform one of the following:

Bring the source IBM i host to a restricted state using the STMENDSBS command.

Hold all jobs and job queues before suspending SRDF links.

For IASP operations, vary off the ASP before a split operation.

NOTE: For V6R1 and higher, you can use the Change ASP Activity command (CHGASPACT) to quiesce an IASP if it is varied on and the split can be run without varying it off. The CHGASPACT command suspends initiations of new transactions and operations before a split operation, writes changes to auxiliary storage before the split and then resumes initiations of new transactions and operations after split.

These processes ensure that one or more target volumes contain a point-in-time frozen image that exactly matches the image of the source storage device at the time the links are suspended.

The SRDF Introduction contains information about SRDF link states, such as SyncInProg, Synchronized, and Split.

Standard Features Introduction 23

Multiple SRDF configurations System storage can span across multiple source arrays with a like number of target arrays providing mirror copies. SRDF/TimeFinder Manager ensures that the frozen image is consistent across all arrays before a Suspend or Split operation is performed. This ensures that no invalid tracks are present on any of the target arrays when the frozen image is created. Figure 1 shows a system where a single image spans two arrays.

.

Figure 1 Multiple arrays single image

Note that both source (R1) and target (R2) volumes that are shown in Figure 1 may also be part of a TimeFinder BCV pair (not shown).

Supported features for arrays running HYPERMAX OS and PowerMaxOS For SRDF/TimeFinder Manager, and IBM i operating system version 7.1.or higher with device type D910-099, automated FAST control is available on arrays that run PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977. The automated FAST handles all thin device binding and allocation, and manages the movement of application data across all the storage capacity defined in a Storage Resource Pool (SRP). Data movement is based on gathered performance data and a performance Service Level Priority (SLP) defined for the application.

Supported operations and configurations Because SRDF/TimeFinder Manager is an IBM i interface to array functionality, the following operations can be performed and configurations are supported:

Display and assign multiple TimeFinder BCV devices.

Run TimeFinder commands to establish and split TimeFinder BCV devices used in replication solutions that vary in complexity, such as where BCVs are used for local mirroring or are used as the source device in multihop replication solutions.

Run SRDF commands to suspend and resume SRDF Remote Link Directors and perform establish and split operations for local replication solutions or for extended-distance replication solutions, such as SRDF/A.

Use TimeFinder/Clone Emulation in configurations containing RAID 5/RAID 6-protected BCVs. The following devices do not take mirror positions of the standard device:

24 Standard Features Introduction

Standard devices that are paired with RAID 5/RAID 6-protected BCV devices.

Mixed-BCV configurations some BCV devices are RAID 5/RAID 6 protected, and some BCV devices are not RAID 5/RAID 6 protected.

RAID 5/RAID 6-protected BCVs used as R1 devices (BCV/R1).

Remote RAID 5/RAID 6-protected BCVs.

Create, activate, and re-create TimeFinder/Clone copy sessions for creating logical point-in-time snapshots of images for arrays.

Use IASPs to present a target device with an IASP image to another partition or host for business continuity (BC) processes.

Establish SnapVX snapshots and link point-in-time data to target devices if needed.

Concurrent RDF.

Multihop configurations that work with combinations of TimeFinder and SRDF.

TimeFinder/Consistency Group TimeFinder/Consistency Group (TimeFinder/CG) enables SRDF/TimeFinder Manager to split local or remote BCVs and clones images (Figure 2) while the source system is operational. This feature is called Split While Active (SPLITWA). CTLACT contains further details on SPLITWA.

Figure 2 TimeFinder/CG

TimeFinder/CG features are as follows:

Ensures that dependent-write consistency for all devices in the step that was selected through the SRDF/TimeFinder Manager menu or from the CTLACT command.

SPLITWA operations do not require that the IBM i host be in a restricted state or that Hold Jobs operation be performed.

The image that SPLITWA creates can be IPLd on another partition or host. Data in main memory at the time of the split is not available on the split image.

TimeFinder/CG prerequisites are as follows:

SRDF/TimeFinder Manager client and the controlling host must have a gatekeeper that is configured on each locally attached array. For detailed information about array gatekeeper management, see the Solutions Enabler Installation and Configuration Guide.

Standard Features Introduction 25

Separate license key, and the netcnfg file must be configured on the client using the CRTNETCNFG command. This ensures that correct information (node name, IP address, port, and security level) points to the remote server. Only nonsecure connections are supported for IBM i.

NOTE: When using this split type, the data in main memory is not included in the image. Only use SPLITWA when the host and applications are in a quiesced state. If that is unacceptable to your business needs, use other operating system functions like journaling and database commitment control to get an image up to the last transaction.

NOTE: When SPLITWA is used remotely and there are several SRDF groups in the configuration, SRDF mode for the links should be synchronized or links should be split.

SRDF/TimeFinder terminology and restrictions SRDF/TimeFinder Manager activates and provides access to the arrays preconfigured BCV, clone devices, SnapVX control operations, and SRDF link control. These operations are controlled using menu-driven interfaces or a command line interface.

SRDF/TimeFinder Manager concepts and terminology that is used in the menus and command line interface are described below.

Terminology SRDF/TimeFinder Manager uses the concept of an image as the high-level controlling object, and the concepts of paths and steps for representing how data on the source device gets copied to one or more target devices.

Images

An image is a set of auxiliary storage pools (ASPs) that can be operated on simultaneously. The types of images are as follows:

System image A combination of the system ASP and all user ASPs. SRDF/TimeFinder Manager represents a System image on screens as SYSTEM.

IASP image An image that contains the following:

A primary IASP and all secondary IASPs, if any, that are associated with the primary IASP group. The image name of the ASP group is the name of the primary IASP.

A user-defined file system (UDFS) IASP. The image name of the UDFS is the name of the disk pool of that UDFS.

SRDF/TimeFinder Manager Extended Features has more information about IASP functionality.

NON_CONFIG image A nonconfigured unit, or any user ASP that is not part of the SYSTEM image. SRDF/TimeFinder Manager does not control or process the devices in the NON_CONFIG image.

Paths and steps

SRDF/TimeFinder Manager uses the following concepts to configure, monitor, and control the array configuration:

A path consists of steps, which describe how data on devices of the source image gets to devices of the target image.

Each step is a description of the replication mechanism that is used to copy data from one device to another device.

SRDF/TimeFinder Manager supports paths containing up to five steps. Steps in the path are predefined and are identified by their position (one through five) in the path. Step numbers are used with control commands to identify which steps in a path are to be processed.

Example of paths and steps:

Configuration type BCV/R1 (STD BCV/R1 R2)

Path name BCVR1

Steps on path /BCV1/RDF1

Configuring paths has more information.

Usage Restrictions SRDF/TimeFinder Manager has the following usage restrictions.

26 Standard Features Introduction

User profile restriction SRDF/TimeFinder Manager must be installed under the QSECOFR user profile as follows:

All objects are owned by the security officer.

All users must belong to the *SECOFR user class and have *ALLOBJ, *JOBCTL, and *SERVICE special authority.

Users that do not belong to the *SECOFR user class with *ALLOBJ authority must have the following special authorities for the flowing objects to run SRDF/TimeFinder Manager menu options and commands:

QSYS/QCSTCTL(*SRVPGM) QSYS/QCSTCRG1(*SRVPGM) QSYS/QCSTCRG4(*SRVPGM)

To satisfy this requirement, system administrators must grant users *USE access to the above objects. The command EDTOBJAUT achieves this purpose.

Users need *IOSYSCFG and *JOBCTL authority in their user profile or inherited from a group that the user belongs to.

To use commands such as DISCOVER, STMENDSBS, and STMSTRSBS a user must belong to the QSECOFR class and have *ALLOBJ, *JOBCTL, and *SERVICE special authority either in their profile or inherited from a group the user belongs to.

Single instance restriction The Work with Images screen does not lock the SYMAPI database file, which allows multiple jobs to access SRDF/TimeFinder Manager screens simultaneously. In addition, the STATUS action does not lock the SYMAPI database file. However, the single instance restriction does apply to SRDF/TimeFinder Manager control actions, where only one control action can be run at a time.

Configuration and Control Menus 27

2

Configuration and Control Menus

This chapter describes the commonly used SRDF/TimeFinder Manager menus. It also introduces running SRDF/TimeFinder Manager commands from remote IBM systems.

Topics:

Overview Navigating SRDF/TimeFinder Manager Accessing the main menu Dell EMC SRDF/TimeFinder Manager for IBM i main menu Control Menu Configuration by Image screen Work with Associated Paths screen Disk Units screen Running remote commands

Overview The following screens, detailed in this chapter, are accessed from the main menu and are used to control SRDF/TimeFinder Manager actions:

Control Menu Performs control actions for all supported SRDF and TimeFinder operations and other system-control operations.

Configuration by Image screen Performs operations at the image and step level.

Work with Associated Paths screen Performs operations at the path level.

Disk Units screen Performs operations at the device level.

Navigating SRDF/TimeFinder Manager When working in SRDF/TimeFinder Manager screens, the following actions return to a previous screen or exit from SRDF/TimeFinder Manager screens:

Press F5 to refresh the information on SRDF/TimeFinder Manager screens.

Press F3 to return to the Configuration by Image screen.

Press F12 to display the previous screen.

Repeatedly press F3 or F12 until control returns to the IBM i main menu.

Accessing the main menu To access the Dell EMC SRDF/TimeFinder Manager for IBM i main menu:

1. On the source IBM i host, ensure that the product library EMCCTL is present in the library list by entering:

ADDLIBLE EMCCTL

NOTE: EMCCTL must be at the top of the library list to ensure proper execution of SRDF/TimeFinder Manager operations.

2. At the command prompt on the system console, enter:

GO MAINCTL

The Dell EMC SRDF/TimeFinder Manager for IBM i main menu (Figure 3) appears.

28 Configuration and Control Menus

Dell EMC SRDF/TimeFinder Manager for IBM i main menu The Dell EMC SRDF/TimeFinder Manager for IBM i main menu is an IBM i interface to access array functionality.

Figure 3 Dell EMC SRDF/TimeFinder Manager for IBM i main menu

Dell EMC SRDF/TimeFinder Manager for IBM i menu fields

1. Work with Images

Displays the Configuration by Image screen used to add or remove ASPs from images or display other screens that enable you to associate and work with paths. For more information:

Configuration by Image screen

2. Work with Paths

Displays the Work with Available Paths screen that enables you to add new paths to the path file. It also enables you to delete a path from the path file and from the image file if the path has configured steps. For more information:

Working with paths

3. Control Menu

Displays the Control Menu which contains options to execute SRDF, TimeFinder, or IASP control action commands, control SRDF groups, configure pools, and control other system level actions. For more information:

Control Menu

4. Version Information

Displays current program version information for SRDF/TimeFinder Manager software components. For more information:

Viewing version information.

10. Display Job Log

Displays the current job log.

This is an IBM ifunction; it is not documented in this guide.

90. Sign Off

Exits SRDF/TimeFinder Manager and signs off from the IBM i host.

Configuration and Control Menus 29

Control Menu Use the Control Menu to:

Perform SRDF, TimeFinder, or IASP control actions against devices in a step.

Control independent ASPs.

Discover arrays and host configuration detail.

Toggle the SRDF mode type.

Bring an IBM i host to a restricted state.

Start subsystems.

Control Daemons.

List SRDF groups.

Control Dynamic SRDF Groups.

Set SRDF groups.

Create and delete RDF pairs.

Create, delete, and display SRDF/Metro vWitness information.

Add and remove node information.

To access the Control Menu, select option 3. Control Menu from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu (Figure 3).

Figure 4 Control Menu

Control Menu fields

1. SRDF or TimeFinder Control

Displays the Dell EMC SRDF or TimeFinder Control (CTLACT) screen for controlling devices in an image, path, or step for SRDF and TimeFinder operations. For more information:

Controlling SRDF

Controlling TimeFinder

CTLACT

30 Configuration and Control Menus

2. Independent ASP Control

Displays the Dell EMC Independent ASP Control (IASPCTL) screen, for processing IASP control actions. For more information:

SRDF/TimeFinder Manager Extended Features

3. Run Discover

Displays the Run Discover Process (DISCOVER) screen, which executes the DISCOVER command. For more information:

Discovering array and host configuration details

DISCOVER

4. Set SRDF Mode

Displays the Set SRDF Mode (SETRDFMOD) screen for setting the SRDF mode (synchronous, asynchronous, or Adaptive Copy disk mode) to use for a selected image, path, or step. For more information:

SETRDFMOD

5. Bring system to a restricted state

Puts an IBM i host in a restricted state and ends the subsystems, except the subsystem running the Solutions Enabler daemon jobs. The two daemon jobs STORAPID and STORGNSD must be running to execute the control commands. For more information:

STMENDSBS

6. Start subsystems

Starts subsystems by executing the program defined in the SYSTEM value QSTRUPPGM. For more information:

STMSTRSBS

7. Control Daemons

Displays the Control Dell EMC daemon process (STORDAEMON) screen for starting or stopping the SYMAPI server from the client (target) IBM i host. For more information:

Working with Solutions Enabler daemons

9. List SRDF groups

Displays the List of the RDF Groups screen that lists all SRDF groups. It also shows the number of seconds that data on the R2 is behind the data on the R1 device and if the RDF group participates in a Star configuration. For more information:

Listing and monitoring SRDF groups

10. Control Dynamic RDF Groups

Displays the Control SRDF Groups screen for adding, modifying, and removing SRDF groups. For more information:

CTLRDFGRP

11. Set SRDF group

Displays the Set SRDF Group (SETRDFGRP) screen for controlling attribute settings for an RDF group. For more information:

SETRDFGRP

12. Create/Delete RDF Pairs

Displays the Create/Delete RDF Pairs (CRTDLTRDFP) screen for creating or deleting dynamic SRDF pairs. For more information:

CRTDLTRDFP

NOTE: See RDF group or device compatibility for more information on RDF group or device pairing.

13. Create/Delete vWitness info

Displays the vWitness Control Action (CTLVWIT) screen for adding, deleting, enabling, and disabling SRDF/Metro vWitness instances.

Maintain vWitness information

CTLVWIT

Configuration and Control Menus 31

14. Display vWitness info

Displays the Display vWitness Information (DSPVWIT) screen for viewing the SRDF/Metro vWitness information. For more information:

See View vWitness information and DSPVWIT

15. Add/Remove Node Information

Configure details of remote nodes, such as the back-up or disaster recovery node, so that they can be monitored and the operator alerted should any of them become unavailable.

Configuring node information

STORDAEMON

Configuration by Image screen Use the Configuration by Image screen to perform image and step level operations.

To access the Configuration by Image screen, select option 1. Work with Images from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu (Figure 3).

Figure 5 Configuration by Image screen

Press F10 to display the information at the image level (Figure 6).

32 Configuration and Control Menus

Figure 6 Configuration by Image screen collapsed

Press F10 again to display information at the ASP level (Figure 5).

Configuration by Image fields

Opt

Entry field for configuration action options.

Image

SYSTEM Displays the system ASP (ASP 1) and all basic user ASPs (2-32) configured on the system.

NAME Displays the name of the IASP image, when IASP images (ASPs 33-255) are present in the configuration.

NON_CONFIG Displays non-configured units (devices) and any user ASPs not part of the SYSTEM image.

ASP

ASP number.

# of Units

Total number of devices in the ASP or image, depending upon which screen appears.

Devices Type

Displays the device types in the configuration:

Symmetrix Contains only Symmetrix devices.

Non_Symmetrix Contains only non-Symmetrix devices.

Mixed Contains both Symmetrix and non-Symmetrix devices.

Work with Associated Paths screen Use the Work with Associated Paths screen to perform operations on paths.

To access Work with Associated Paths screen, select option 2=Work with Paths from the Configuration by Image screen (Figure 5).

Configuration and Control Menus 33

Figure 7 Work with Associated Paths screen overview

Work with Associated Paths fields

Opt

The entry field for configuration action options.

Path Name

The name of the path used to move data on devices of the source image to devices of the target image.

Step

The source or target type of step associated with the Path Name field.

Status

Identifies the status of the selected path.

NOTE: Possible step status for SnapVX:

NotConfigured step is not paired and no snapshots for source devices in the step exist.

NotPaired step is not paired and at least one snapshot for source devices in the step exists.

Established devices are paired, snapshots exist but are not linked. Step has snapshots, is paired, but not linked.

NoSnapshots step is paired and no snapshots for source devices in the step exist. If the step is paired, at least one snapshot for source devices in the step exists but target devices are not linked, the status of the first Snapshot would be presented. If snapshot has restores, the status would be Restored or RestoreInProg.

RestNotPaired step is not paired and source devices are restored.

Status of the link If target devices are linked.

Invalids/%Copied

The number of invalid tracks remaining during SRDF or TimeFinder/SnapVX synchronization operations, or percent of copy completion for TimeFinder/Clone operations.

Path/Snapshot

Description of steps in the path associated with the selected image. Snapshot name is displayed if target devices for the SVXn are linked to the snapshot, or source devices restored from the snapshot and target devices are not linked.

Gen

For SVXn step, if target devices are linked to the snapshot or source devices restored from the snapshot and target devices are not linked then the generation number is displayed.

34 Configuration and Control Menus

Disk Units screen Use the Disk Units screen to perform operations at the device level. The Disk Units screen can be displayed from either the array view or IBM i view.

To access the Disk Units screen, select option 5=Work with disk units for the desired step in the Work with Associated Paths screen (Figure 7).

The Disk Units screen for SnapVX type of step Figure 10 displays a different header than all other type of steps.

Figure 8 Disk Units screen

Figure 9 Disk Units IBM i View screen

Configuration and Control Menus 35

Disk Units screen fields: Array view

RDF mode

Type of SRDF/A mode for the RDF devices in a step. Possible values are:

N/A The device is not RDF capable.

Active The selected image is part of a SRDF/Metro configuration.

Synchronous The mode for the selected image is set to Synchronous.

Asynchronous The mode for the selected image is set to Asynchronous.

Metro The mode for the selected image is set to SRDF/Metro.

Adaptive Copy Disk Mode (ACDM) The mode for the selected image is set to ACDM.

Consistency Protection

Indicates whether or not consistency protection is enabled for SRDF/A. Possible values are:

N/A The device is not in SRDF/A mode.

Enabled The device is running in asynchronous mode and consistency protection is enabled.

Disabled The device is running in asynchronous mode and consistency protection is disabled.

Clone emulation

Indicates the clone for the step. Possible values are:

N/A The BCV clone emulation is not enabled for the step.

Enabled There are clone sessions for all pairs of BCV devices.

Mixed Not all BCV devices in the step are clone enabled.

BCV Configuration

Indicates the configuration type for the BCV device in a step. Possible values are:

N/A Not all devices in the BCV step are configured or the step type is not BCV.

Standard All BCV devices in the step for the selected path of the system image are configured as additional mirrors of a standard array device.

RAID5/6 The BCV devices in the step for the selected path of the system image are configured for RAID 5 or RAID 6 or both RAID 5 and RAID 6 protections.

Mixed Devices have mixed BCV protections Some devices are standard BCVs; some devices are RAID 5 and RAID 6-protected BCVs.

Target Type

Indicates the type of target device for a Clone (NCLn) step. Possible values are:

BCV All target devices are thick BCV devices.

Standard All target devices are standard thick devices.

Mixed Target devices are a mix of BCV, standard, and thin devices.

TDEV All target devices are standard thin devices.

BCV_TDEV All target devices are thin BCV devices.

TDEV RDF All target devices are RDF thin devices.

TDEV BCV/RDF All target devices are RDF BCV thin devices.

TDEV BCV/STD Target devices are a mix of standard and BCV Thin devices.

N/A This is not a Clone (NCLn) step.

Clone Type

Indicates the Clone type of Clone type of the step:

Regular Clone type is a normal type

Mixed Clone type is mixed.

N/A indicates other types of the step

OPT

Entry field for configuration action options.

36 Configuration and Control Menus

Unit #

Number assigned by the system to identify a specific disk.

0 Non-configured devices.

ASP

ASP number in the current configuration.

0 Non configured devices.

Source Device

Array device name of the source device.

Target Device

Array device name of the target device.

Source Symmetrix

Array serial number for the source device.

Target Symmetrix

Array serial number for the target devices (only if present). If BCV or Clone devices are present, the serial number is the same as the source array.

Status of the RDF pair

Status for the selected SRDF pair (if relevant). Possible values are:

N/A Device is not SRDF capable.

Consistent The R2 mirrors of SRDF/A devices are in a Consistent state, which signifies the normal state of operation for device pairs operating in asynchronous mode.

Failed Over R1 is Not Ready or Write Disabled, and the operation is failed over to the R2 device.

Invalid The default state when another RDF state applies, such as when the combination of R1, R2, and RDF link states and statuses do not match any other pair state. An Invalid status can occur if there is a problem at the disk director level.

Partitioned The SYMAPI is currently unable to communicate through the corresponding RDF path to the remote array. A Partitioned status may apply to devices within an RA group.

R1 UpdInProg The R1 is currently Not Ready or Write Disabled to the host. There are invalid local (R1) tracks on the source side and the link is Ready or Write Disabled.

R1 Updated The R1 is currently Not Ready or Write Disabled to the host. There are no local invalid tracks on the R1 side and the link is Ready or Write Disabled.

Synchronized The R1 and R2 are currently in a synchronized state and have identical data.

SyncInProg Synchronization is currently in progress between the R1 and the R2. There are existing invalid tracks between the two pairs and the logical link between both sides of an RDF pair is up. During an Establish operation, data is copied from the standard device to the RDF device until both devices contain identical data.

Split SRDF links were established and are currently split. The R1 and the R2 are currently Ready to their hosts, but the link is Not Ready or Write Disabled.

Suspended The RDF links have been suspended and are Not Ready or Write Disabled. If the R1 is Ready while the links are suspended, any I/O will accumulate as invalid tracks owed to the R2 device.

TransIdle The RDF group is operating in SRDF/A Transmit Idle mode. The SRDF/A session cannot push data in the transmit cycle across the link because the link is down.

Status for BCV or Clone enabled pair

Status for the selected BCV or Clone enabled pair (if relevant). Possible values are:

N/A Device is not paired.

Invalid If the device is a meta head, and the members are not in a consistent state, then the overall status of the meta device is mixed and invalid.

NeverEstab The BCV device was paired but never established with a standard or R2 device, or Cancel is executed against this device pair.

RestInProg When the restore action is executed, data is copied from the BCV or Clone to the standard device until both devices contain identical data.

Configuration and Control Menus 37

Restored The BCV or Clone enabled device and the standard device have identical data, although the data was originally on the BCV or Clone enabled device prior to being synchronized. Any changes to the standard device are also written to the BCV or Clone enabled device. The BCV or Clone enabled device is unavailable to the host for processing.

Split The BCV or Clone enabled device is completely separated, or split, from the standard devices allowing each device to be accessed separately by the host.

SplitBfrRes The split occurred when a BCV or Clone enabled device was being restored to a standard device. The BCV or Clone enabled device is separated from the standard device, although the standard is not completely synchronized. No restrictions.

SplitBfrSyn The split occurred when a BCV or Clone enabled device was synchronizing. The BCV or Clone enabled device is separated from the standard device although the BCV or Clone enabled device is not completely synchronized.

SplitInProg The BCV or Clone enabled devices are in the process of being separated or split from the standard devices.

SplitNoInc The BCV or Clone enabled devices are completely separated or split from the standard devices but cannot be incrementally established or restored. No restrictions.

Synchronized The BCV or Clone enabled devices and the standard device have identical data. Any changes to the standard device are also written to the BCV or Clone enabled device. When a step state is Synchronized, a Split operation can be performed. The BCV or Clone enabled device is unavailable to the host for processing.

SyncInProg Synchronization is currently in progress between the standard or R2 device and the target device.

Status for Clone pair

Status for the selected Clone device pair (if relevant). Possible values are:

Copied The entire device has been written to and is in a fully copied state.

CopyInProg When background copying, the state of the device pair is Copy In Progress. When the copy session is activated, background copying begins so that a full copy of the data will become available on the target device.

CopyOnAccess After activating the copy session, only those tracks that have been written to the source or written to/read from the target will be copied to the target device. A full data copy to the target device will not occur unless all of the device tracks are accessed or written to while participating in the active session.

CopyOnWrite Devices participating in the copy session have been activated. Data and pointers will be copied upon any first write to a track on the source device or any host write to the target device.

Created A copy session between a source device and a target device has been created.

CreateInProg A copy session between a source device and a target device is in progress.

Failed The copy session has failed because the log device pool is full.

Invalid Applies to a meta device only. The meta device states do not consistently match.

Not Created The target device is not actively participating in a copy session.

Precopy The precopy process keeps checking for new writes to be precopied to the target device until the copy session is activated. Once activated, the normal background copy mechanism starts and the precopy operation ends. Precopy can occur in the Created or Recreated state.

RestInProg Data restore to the specified target device is in progress.

Restored Data has been fully restored to the specified target device.

TermInProg The copy session between a source device and a virtual device is in the process of terminating.

Invalids /%Copied

The number of invalid tracks remaining during SRDF or TimeFinder synchronization operations, or percent of copy completion for TimeFinder/Clone operations.

Bias

SRDF/Metro configurations only: Indicates whether the source array is the bias side of a SRDF/Metro configuration. The field is blank when the source array is not on the bias side, contains S when the source array is the bias side, or contains T when the target array is the bias side.

Disk Units screen fields: IBM i view

Serial Number

IBM i serial number.

38 Configuration and Control Menus

Resource Name

IBM i resource name for the device.

Disk Type

The device type being emulated.

Disk Model

The model of the device being emulated.

I/O Adapter

The address of an adapter on an IOP.

I/O Bus

Address of a bus on an IOP.

Ctl

Address of a controller on an I/O bus.

Dev

Address of a storage device on a controller.

Figure 10 Disk Units screen SVX type of step

Disk Units screen fields for SVX type of step: Array view

Snapshot Name

Name of the SnapVX snapshot.

Generation

Identifies the point-in-time copy when multiple snapshots are made for the same name on the same devices.

OPT

Entry field for configuration action options.

Unit #

Number assigned by the system to identify a specific disk.

0 Non-configured devices.

ASP

ASP number in the current configuration.

Configuration and Control Menus 39

0 Non configured devices.

Source Device

Array device name of the source device.

Target Device

Array device name of the target device.

Source Symmetrix

Array serial number for the source device.

Target Symmetrix

Array serial number for the target devices (only if present). If target devices are present, the serial number is the same as the source array.

Status

Status for the SnapVX pair. Possible values are:

N/A Source device is not paired and not restored.

Linked Target device is linked to snapshot in NoCopy mode.

Copied Target device is linked to snapshot in Copy mode when it is 100% copied.

CopyInProg Target device is linked to snapshot in Copy mode and it is in transient state to Copied.

RestoreInProg Restore from snapshot to source device is in progress and source device is not paired.

Restored Source device is restored from the snapshot and source device is not paired.

NotLinked Target device is not linked to the snapshot.

Failed Link failed if no more allocations can be made from the SRP associated with the link device or if a corruption occurs on the link device.

Invalids/%Copied

Percent of the total device size that has been copied to the target when the COPY flag is set, or when the source device is restored from the snapshot.

Running remote commands For SRDF/TimeFinder Manager versions earlier than 8.0, preparing to run SRDF/TimeFinder Manager commands from a remote IBM system requires several configuration steps, including starting the REXEC server on both the local and remote system. In order to simplify using this feature, SRDF/TimeFinder Manager 8.0 and later uses the STMRMTCMD command and executes remote commands through the STM server.

See STMRMTCMD for more information on how to run the remote feature for STM commands.

Operational Features, Settings, and Displays 41

3

Operational Features, Settings, and Displays

Invisible Body T

This chapter shows how to set up, maintain, and display the SRDF/TimeFinder Manager environment.

Topics:

Setting user-configurable preferences Discovering array and host configuration details Configuring node information Configuring IFS files to support Solutions Enabler Working with Solutions Enabler daemons Working with the SYMAPI server Viewing version information

Setting user-configurable preferences SRDF/TimeFinder Manager has the following user-configurable preferences:

Suppress or allow pop-up messages. See Controlling pop-up messages for more information.

Set restricted state wait time. See Setting the restricted state wait time for more information.

Set the wait time value for SRDF/A. See Controlling the SRDF/A Split wait time for more information.

View values in the FLSHCFG data area. See Viewing the current values in the FLSHCFG data area for more information.

Reset the lockbox password. See Resetting the lockbox password for more information.

Controlling pop-up messages SRDF/TimeFinder Manager can determine how pop-up messages appear. For example, during BCV Split or SRDF Split/Suspend operations, pop-up messages or screens display when additional action is required to proceed with the operation.

Pop-up messages display by default. To suppress pop-up messages and screens, use the CHGDTAARA command to set the value in the DSPMSG data area in the EMCCTL library to one. When the value is set to one, all messages go into the job log during SRDF or TimeFinder operations, and no messages display even in interactive jobs. This only applies when the operation is initiated from the CTLACT command or option 1. SRDF or TimeFinder Control on the Control Menu.

To allow pop-up messages and screens, use the CHGDTAARA command to set the value in the DSPMSG data area in the EMCCTL library to zero.

The default is to allow pop-up messages and screens.

Setting the restricted state wait time SRDF/TimeFinder Manager provides an option on the Control Menu that sets the system to a restricted state. Depending on the configuration, the time it takes for a host to go into restricted state can vary. By default, SRDF/TimeFinder Manager waits 1800 seconds for control to return, after the action to bring the system to a restricted state is issued from the Control Menu. If the host cannot go into restricted state within the wait time, the option times out with error CTL0151. Use the WRKSBS command to verify the current status of the subsystems.

If additional restricted state wait time is required, use the CHGDTAARA command to set the appropriate value (in seconds) in the SBSWAIT data area in the EMCCTL library.

42 Operational Features, Settings, and Displays

Controlling the SRDF/A Split wait time In an SRDF/A configuration, during an SRDF Split/Suspend operation, the control program needs to wait at least two cycle times after the flush to ensure that all changes are made to the R2 devices, before the actual split occurs. This process usually takes two times the average SRDF/A cycle time, but could take longer depending upon the configuration. The control program waits for a maximum of 300 seconds (the default) before failing with an error.

SRDF/TimeFinder Manager can control the wait time for a Split/Suspend operation before failing with an error.

To control the Split wait time, set a value in the SRDFATIME data area using the CHGDTAARA command.

Viewing the current values in the FLSHCFG data area A preference can be set to view the current values in the FLSHCFG data area.

To view the current values in the FLSHCFG data area, use the following command. If necessary, change EMCCTL to the library containing the data area.

DSPDTAARA EMCCTL/FLSHCFG

The Display Data Area screen (Figure 11) appears:

Figure 11 Display Data Area screen with FLSHCFG data area with default values

You can modify three fields:

Suspend timeout (seconds) If the database Suspend operation does not complete within this time, the action defined in the following field occurs. The default value is 000060.

Timeout action End/Continue (E/C)

E (default value) When a suspend timeout occurs, an escape message is written in the joblog, the Suspend operation is terminated, and the SRDF/TimeFinder Manager Split operation is terminated.

C When a suspend timeout occurs, a diagnostic message is written in the joblog, the Suspend operation continues, and the SRDF/TimeFinder Manager operation continues.

NOTE: If the Suspend operation fails, an escape message is written in the joblog. If operation is successful, a completion message is written to the joblog. When C is specified in the data area check the Additional Message Information.

Option SUSPEND/FRCWRT (S/F)

When performing a SPLITWA action in the CTLACTTGT command, the value of this field determines which mode CTLACTTGT uses to run the CHGASPACT command:

S (default value) CHGASPACT runs in *SUSPEND mode.

F CHGASPACT runs in *FRCWRT mode.

To change values in this data area, use the CHGDTAARA command. For example:

Operational Features, Settings, and Displays 43

To change the Suspend timeout (seconds):

CHGDTAARA DTAARA(EMCCTL/FLSHCFG (40 6)) VALUE('nnnnnn')

To change Timeout Action End/Continue (E/C):

CHGDTAARA DTAARA(EMCCTL/FLSHCFG (90 1)) VALUE('E')

Resetting the lockbox password The lockbox password for array accessibility is set to the default (hostname@SELockbox1) when the CRTSYMAPI and CRTSYMAPIC commands are run during SRDF/TimeFinder Manager installation. The password can be changed by running the following SYMCLI command:

symcfg lockbox [password <Password>] reset ssv setpw [new_password <NewPassword>]

Discovering array and host configuration details The Discover function is used to perform the discovery process after changes to the host configuration or array configuration. However, by default, the SRDF/TimeFinder Manager Discover function is turned off and it does not automatically run the discovery process while viewing configuration details, performing control operations, or making configuration changes.

The discovery process is activated one of two ways:

Changing the discover data area value in the EMCCTL library default is set to discovery process off.

Using the DISCOVER command.

NOTE: The discovery process run from the DISCOVER command is independent of the setting in the EMCCTL library.

Turning on the discovery process from the EMCCTL library To turn on the discovery process, use the CHGDTAARA command to set the Discover data area in the EMCCTL library to one. The Discover function remains on and the discovery process runs until the value is set to zero.

Running the DISCOVER command The DISCOVER command performs a one-time discovery process, and does not enable automatic discovery. For subsequent configuration changes, unless the Discover data area value is set to one, the command must be run again to update configuration files.

Run the discovery process as follows:

1. Select option 3. Control Menu from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu (Figure 3).

2. Select option 3. Run Discover from the Control Menu to display the Run Discover Process (DISCOVER) screen (Figure 12).

44 Operational Features, Settings, and Displays

Figure 12 Run Discover Process (DISCOVER) screen

3. Enter the following required parameters:

a. Remove Symmetrix information:

*NO Do not remove old array data from the SYMAPI database. *NO is the default.

*YES Remove previously discovered array information that is no longer valid from the SYMAPI database.

CAUTION: When the RDF link is down, do not run DISCOVER with Remove Symmetrix information set to *YES. Doing so can remove relevant R2 information, such as BCV or Clone pairing for the array from the SYMAPI database.

b. Check IMAGE file:

*NO Do not verify information stored in the IMAGE file with current device information of the host. *NO is the default.

*YES Verify information stored in the IMAGE file with the current device information of the host and remove any old device information from the file.

4. Press Enter to start the discovery process.

Turning off the Discovery Process To turn off the discovery process, use the CHGDTAARA command to set the Discover data area in the EMCCTL library to zero.

Configuring node information SRDF/TimeFinder Manager can monitor remote nodes, for example those providing disaster recovery facilities. Should one of those nodes become unavailable, SRDF/TimeFinder Manager sends a message to the system operator of the IBM System i.

SRDF/TimeFinder Manager keeps a list of the nodes that it is to monitor. It also provides facilities to:

Access the management facilities for node monitoring

Add nodes to the list

Remove nodes from the list

Change the Notify User parameter

Display the list of nodes

Control the monitoring of the remote nodes

Operational Features, Settings, and Displays 45

Accessing the node monitoring management facilities To access the facilities for managing how SRDF/TimeFinder Manager monitors nodes:

1. Select option 3. Control Menu from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu (Figure 3).

2. Select option 15. Add/Remove Node from the Control Menu to display the Display Node Information (NODEDETAIL) screen (Figure 13).

Figure 13 The Display Node Information screen

For each node in the list, the screen shows:

The name of the node

The IP address of the node

An indication of whether the node is unavailable: Y shows that the node is unavailable while N shows that the node is available.

The date and time when the availability of the node was last checked.

46 Operational Features, Settings, and Displays

Adding a node To add a node to the list of monitored nodes:

1. Access the Display Node Information screen.

2. Press F6 to display the Add Node Information screen:

Figure 14 Add Node Information Screen

3. Enter values for the Node Name and Node IP parameters.

4. The Notify User parameter specifies whether the daemon periodically checks the node and notifies the user. Enter Y to enable periodic checking and notification of the node. Enter N for the daemon to check the node and notify the user only when the daemon starts up.

5. Press Enter.

The Display Node Information screen re-appears with the new entry included in the list.

Removing nodes To remove nodes from the list of monitored nodes:

1. Access the Display Node Information screen.

2. Enter 4 in the Opt column for each node to remove from the list.

3. Press Enter.

A confirmation screen appears:

Operational Features, Settings, and Displays 47

4. Type Y and press Enter.

Changing the Notify User parameter To change the setting of the Notify User parameter for one or more nodes:

1. Display the Access the Display Node information screen.

2. Enter 5 in the Opt column for each node to change the Notify parameter.

3. Press Enter.

Controlling the monitoring of remote nodes A daemon process called NODEDAEMON carries out the monitoring of remote nodes and recording their status. You can start and stop the daemon process:

1. Select option 3. Control Menu from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu.

2. Select option 7. Control Daemons from the Control Menu.

The Control Dell EMC daemon process (STORDAEMON) screen (Figure 15) appears.

Figure 15 Control Dell EMC daemon proc (STORDAEMON) screen

3. In the Daemon Action field enter STRNODEMON (to start the daemon) or ENDNODEMON (to stop the daemon).

4. Press Enter.

Configuring IFS files to support Solutions Enabler In order to support Solutions Enabler operations, the required files are installed to the IBM i Integrated File System (IFS) during SRDF/TimeFinder Manager installation. These files are installed in the following IFS directories:

/var/symapi/config Holds the Solutions Enabler configuration files, and an alias file that can be used to run CLIs in a QShell environment.

/usr/storapi/man/man1 Holds the help files for the CLIs.

/usr/storapi/locales/en Holds the error.properties file that enables error reporting in different languages.

48 Operational Features, Settings, and Displays

The installation of these Solutions Enabler files is performed by the CRTSYMAPI or CRTSYMAPIC program. When either of these programs are run, these files are restored from a save file in the EMCCTL or EMCCTLC library. The save files are called SYMAPICNFG, STORAPILOC and STORAPIMAN.

Modifying the Solutions Enabler configuration files Once installed the SYMAPICNFG files require some modification for Solutions Enabler to function properly.

Modifying the README configuration files

The following README files are templates can be renamed or copied to a file that does not include README in the file name. For example README.daemon_options file can be renamed to daemon_options.

/var/symapi/config/README.daemon_options The daemon_options file contains parameters that control the behavior of the various Solutions Enabler daemons. Each daemon reads this file at startup and applies any settings that apply. The daemon_options file is created by the CRTSYMAPI or CRTSYMAPIC program. For SRDF/TimeFinder Manager, the daemon options that control which subsystem the daemon is started in is set to the EMCCTL subsystem as a default. See Working with Solutions Enabler daemons more for information. The parameters in this file can be modified by the user.

/var/symapi/config/README.daemon_users The daemon_users file lists the local users that are authorized to control and, in some cases, make use of the various Solution Enabler daemons. The parameters in this file can be modified by the user.

/var/symapi/config/README.options This options file contains behavior parameters that can be set to critically change the default behavior of SYMCLI operations, SYMAPI calls, and their control actions. It can be used to set certain global restrictions as well as customize and streamline command line coding to the user-specific environment. The options file is being set by the CRTSYMAPI file.

NOTE: Altering these files is not a prerequisite for normal use, and changing parameters in these files should only be attempted by experienced SYMCLI or SYMAPI users. Changes to these files may cause unwanted feature restrictions, or may cause the array environment to stop functioning.

/var/symapi/config/README.netcnfg This network service file maps a service name to a remote server host node name and/or internet address, and to a port number, to provide a TCP/IP connection for executing remote SYMAPI functions. The NETCNFG file is created by the CRTNETCNFG command. This file can be modified to list more than one service by defining one unique system per line.

Modifying the QShell configuration files

The following files require modification to allow aliases to function in QShell:

/var/symapi/config/alias/profile This file is a template used to modify the /etc/profile file.

Copy the line from the /var/symapi/config/alias/profile file and paste it into the /etc/profile file. If /etc/profile does not exist then copy the profile file from the /.../alias directory to /etc directory.

To set this feature at the user level:

1. Copy the profile file from the /etc directory to the /home/<user directory>.

2. Change the profile file name in the user directory to .profile. (add period in front of profile).

/var/symapi/config/alias/qshrc This file holds setup information that is used by QShell. When running QShell, the /etc/profile file points to qshrc file to set the environmental values defined by this file.

1. Verify that the qshrc file points to the default library EMCCTL or EMCCTLC, by checking that the following two lines are set as shown below:

export PATH=$PATH:/QSYS.LIB/EMCCTL.LIB

liblist -af EMCCTL

2. If the lines in the qshrc file, shown above, do not point to the EMCCTL or EMCCTLC library, modify the lines accordingly.

Working with Solutions Enabler daemons The STORDAEMON command allows for SRDF/TimeFinder Manager to start, stop, and query the Solutions Enabler daemons. See STORDAEMON for details on using this command.

Operational Features, Settings, and Displays 49

The daemons that are managed are:

Storapid (Base) Provides centralized gatekeeper device management for all Solutions Enabler applications. It alleviates contention when there are limited gatekeeper resources available and also eliminates the need for every client to constantly select, open, lock, and ping for an available gatekeeper device for every online function.

Additionally, the base daemon monitors Symmetrix External Locks (SEL) and Device External Locks (DEL), and releases any locks held by a crashed application. The base daemon also eliminates the need for Solutions Enabler applications to run as root.

Storsrvd (Symapi) Provides the SYMAPI server, a multi-threaded program that listens for SYMAPI sessions and management requests initiated by the STORDAEMON command. The server also listens for management requests from the system operator console.

Storgnsd (GNS) Provides a global, distributed repository for DG and CG group definitions.

Configuring daemons using the daemons options file There is a daemon options file used to control daemon behavior. At startup each daemon reads this file and applies all relevant settings. In most cases the default settings are sufficient. However, there are four options available that are specific to IBM i. The file is located in the IFS directory /var/symapi/config and must be named daemon_options.

The options specific to IBM i are:

ibmi_jobq_name = <*JOBD> | jobq name An example jobq name is EMCCTL. If the jobq name is not set, the default *JOBD is used. When *JOBD is used the job description defined in the current user profile is used to determine the job queue name. The second option does not need to be set if the library of named job description is in the library list. If the second option is specified and the first option is set to *JOBD, the second value is ignored.

ibmi_jobq_lib_name = <*LIBL> | Library name An example library name is EMCCTL. If the Library name is not set, the default value *LIBL is used.

NOTE: For both of these options the name has a maximum character length of 10, and upper and lower case characters are allowed. If an option is longer than 10 characters an error message appears.

ibmi_allow_subsystem_start = | The default value is yes. If the daemon jobs are not started yet, this value is used to control automatic startup of the subsystem that is being used for the Solutions Enabler daemons. If the subsystem cannot be started, the daemon jobs do not start and an error message is generated.

Both Base and GNS daemon jobs are started when an SRDF/TimeFinder Manager or Solutions Enabler command is run on the host. By default SRDF/TimeFinder Manager uses the EMCCTL subsystem to run the daemon jobs. The subsystem defined (ibmi_jobq_name) in the daemon options file must be started manually if the daemon_option, ibmi_allow_subsystem_start,is set to no. If the daemon option, ibmi_allow_subsystem_start, is set to yes the subsystem and daemon jobs start automatically.

If you want the daemon jobs run in the QBATCH subsystem, in the daemon options file set the option as follows:

ibmi_jobq_name = qbatch

ibmi_jobq_lib_name = *libl

NOTE: Make sure that the subsystem and job queue entry is set to allow multiple jobs and multiple threads.

redirect_std_fds = enable | disable For IBM i, the default value for this option is enable. This option ensures that the standard output for the running daemon is not directed to the default spool file. This option does not need to be set in the daemon_options file if default is being used.

When this option is set to disable, a spool file is created and all the output for the running daemon job is directed to a spool file. The spool file can become large when running for an extended period of time. Eventually the file reaches its maximum allowable size and an informational message is generated. When the message appears, the daemon job halts and all SRDF/TimeFinder Manager operations are impacted until the user replies to the message.

NOTE: The daemon may stop running if this message is not replied to for a long period of time. If this happens, restart the deamon.

For more information on configuring Solutions Enabler daemons see the Solutions Enabler Installation and Configuration Guide.

Working with the SYMAPI server The SYMAPI server is required for SPLITWA operations, or to run remote CLI commands on the controlling host. The controlling host can either be another IBM i host or a Windows host which has access to the array. It must also have IP connectivity from the IBM i host where SRDF/TimeFinder Manager is installed.

50 Operational Features, Settings, and Displays

Configuring the SYMAPI server When TimeFinder/CG is used in the replication solution, the netcnfg file on the client host must be configured. The netcnfg file contains the IP address of the SYMAPI server.

Prior to configuring the netcnfg file:

1. Confirm IP connectivity to the controlling host.

2. Use the IBM i CFGTCP command, to add an entry to the local host table on the IBM i host where SRDF/TimeFinder Manager is installed. Enter Option 10.

Configure the netcnfg file on the client host as follows:

1. On the source IBM i host, run the following command:

CRTNETCNFG NODENAME (nodename) NETWADDR (ip address)

You can specify the node name, the IP address, or both items.

The Create SYMAPISVR netcnfg file (CRTNETCNFG) screen (see Figure 16) appears.

Figure 16 Create SYMAPISVR netconfg file (CRTNETCFG) screen

2. Enter the following information:

API Server Network address The network address or node name of the API server that was entered into the local host table in step 2 .

NOTE: When using a node name, make sure the node name also appears in the host table for the system or is listed in the DNS tables of the attached network.

SYMAPI Server Port Number The TCP/IP port number. The default value is 2707.

Security Level The security connection level for the server: DEFAULT, ANY, NONSECURE, or SECURE.

NOTE: A SECURE connection is not supported for IBM i hosts.

3. Press Enter.

An entry similar to the following is added to the netcnfg file:

SPLITWA_SERVICE - TCPIP - 10.123.456.789 2707 -

Starting the SYMAPI Server To start the SYMAPI Server:

Operational Features, Settings, and Displays 51

1. Select option 3. Control Menu from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu.

2. Select option 7. Control Daemons from the Control Menu.

The Control Dell EMC daemon proc (STORDAEMON) screen (Figure 17) appears.

Figure 17 Control Dell EMC daemon proc (STORDAEMON) screen

3. Enter the following information:

Daemon Action START

Daemon Name STORSRVD

STORSRVD Port number Default is 2707.

NOTE: STORDAEMON contains more information.

Stopping the SYMAPI Server To start the SYMAPI Server:

1. Select option 3. Control Menu from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu.

2. Select option 7. Control Daemons from the Control Menu.

The Control Dell EMC daemon proc (STORDAEMON) screen (Figure 17) appears.

3. Enter the following information:

Daemon Action SHUTDOWN

Daemon Name STORSRVD

NOTE: STORDAEMON contains more information.

Viewing version information To view the current program version information:

1. On the source IBM i host, display the Dell EMC SRDF/TimeFinder Manager for IBM i main menu. See Accessing the main menu.

2. Select option 4. Version Information.

52 Operational Features, Settings, and Displays

The Program Version Information screen (Figure 18) appears listing current program version information for the Base SRDF/TimeFinder Manager, I/O Driver, and SYMAPI.

NOTE: The Build Type field is populated depending on the type of release, for example: Internal, HotFix, Beta, or Release.

Figure 18 Program Version Information screen

NOTE: The version number of the operating environment appears on the Disk Units Details screen.

Configuring the Environment 53

4

Configuring the Environment

This chapter describes the configuration steps that enable SRDF/TimeFinder Manager to control SRDF and TimeFinder replication environments with IBM i hosts.

Topics:

Configuration overview Configuring images Configuring paths Working with paths Configuring device pairs

Configuration overview The initial configuration consists of:

Creating paths and associating paths with images

Pairing devices for TimeFinder environments

Configuring devices and device pools

If TimeFinder/CG is used in the replication solution, configure the netcnfg file on the client host as well. See Working with the SYMAPI server for a complete description of the procedure.

Carry out these configuration steps only once, after a new installation. However, if system storage resources are altered, such as when a new disk is added to an ASP using IBM i System Service Tools, repeat these configuration steps.

Configuring images The procedure for adding ASPs to an image or removing ASPs from an image is similar. This operation allows ASPs to participate or be excluded from control operations. The removed ASPs display in the NON_CONFIG image on the Symmetrix Configuration by Image screen.

Adding ASPs to an image To add ASPs to an image:

1. Select option 1. Work with Images on the Dell EMC SRDF/TimeFinder Manager for IBM i main menu to display the Symmetrix Configuration by Image screen.

2. On the Symmetrix Configuration by Image screen, enter one in the Opt column for the ASP in the NON_CONFIG image pool to be added to the SYSTEM image.

The Symmetrix Configuration by Image screen re-appears with the ASP removed from the NON_CONFIG image and added to the ASP list of the SYSTEM image.

Removing ASPs from an image To remove ASPs from an image:

1. On the Configuration by Image screen, enter 4 in the Opt column of the ASP to be removed from the SYSTEM image.

The Confirm Remove ASP from the image screen appears.

2. Enter Y to confirm the ASP removal from the SYSTEM image.

The Configuration by Image screen appears with the ASP added to the ASP list in the NON_CONFIG image pool.

54 Configuring the Environment

When an ASP is removed, the target image for that ASP may not be synchronized with the source standard devices. This feature adds flexibility to SRDF and TimeFinder operations. For example, for system configurations where one or more ASPs containing non-Symmetrix devices are permitted, allowing operations to continue for some ASPs while the ineligible ASPs are removed. Note that the SRDF link status for the image must be in an eligible state.

Configuring paths Paths can contain up to five steps. Steps in the path are defined during configuration and are identified by their positions (one through five) in the path. Step numbers are used with control commands to identify which steps in the path are to be processed (Table 2).

Each image can have multiple paths. With IASP images, only one step of a path can be presented to a target host at a time.

A path cannot be associated with an image (IBMIASP) that contains non-Symmetrix devices.

You cannot associate a path on the NON_CONFIG image.

You can display overall status for the path associated with an image and for each step in the path at any time during the configuration process. See the Work with Associated Paths screen for more information.

There are two types of paths:

Predefined paths See Table 2 for a list of the predefined paths.

Manually defined paths Use when data needs to be moved in a manner that is not defined in an existing path. Working with paths describes how to define a path.

An image that contains devices spread across multiple arrays must have the same configuration steps on all participating arrays.

Once a path has been configured, you can access the path by the image and path name to display full configuration details and separately control each step of the path. Controlling the path ensures that the replicated data gets from source devices to target devices according to the complexity of the replication solution.

Predefined and user-defined paths Use Table 2 as a guide when associating paths in the configuration process.

Steps in the path are shown in the user interface screens with a forward slash (/) separator between steps, which represents how data gets from the host source devices (STDs) to the target devices.

A step in the path is identified by its position (one through five) in the path as shown in this example:

Using YOURPATH3, the number of steps associated with the full path /BCV1/RDF1/BCV1/RDF1/BCV1 is 5:

/BCV1/RDF1/BCV1/RDF1/BCV1 1 2 3 4 5

If a step in any path contains the same source and target devices on the same source and target arrays, the step type is the same in all paths for this combination. Unique combinations of source and target devices require unique step types in all paths.

NOTE: When running on PowerMaxOS 10 (6079) using STM IBM i version 10.0, /BCVX and /CLNX paths receive an error message, The requested feature is not supported for this microcode or SYMAPI version. However, these are still fully supported on a PowerMaxOS versions lower than 6079 when using STM IBM i version 10.0.

Table 2 Predefined and user-defined configurations and paths

Configuration type Path name Steps in the path

Predefined configurations and paths

SRDF (STD/R1 R2) SRDF /RDF1

Cascaded SRDF CASCADRDF /RDF1/RDF1

Concurrent Cascaded SRDF CASCADRDF2 /RDF2/RDF1

Concurrent RDF SRDF2 /RDF2

Local BCV (STD BCV) LOCALBCV /BCV1

Configuring the Environment 55

Local Clone Emulation (STD BCV) LOCALCLN /CLN1

Local Clone (STD BCV or STD) LOCALNCL /NCL1

Local SnapVX (STD BCV or STD LOCALSVX /SVX1

Remote BCV (STD/R1 R2 BCV) REMOTEBCV /RDF1/BCV1

BCV/R1 (STD BCV/R1 R2) BCVR1 /BCV1/RDF1

BRBCV (STD BCV/R1 R2 BCV) BRBCV /BCV1/RDF1/BCV1

Remote Clone Emulation (STD/R1 R2 BCV) REMOTECLN /RDF1/CLN1

Remote Clone (STD/R1 R2 BCV or STD) REMOTENCL /RDF1/NCL1

Remote SnapVX (STD/R1 R2 BCV or STD) REMOTESVX /RDF1/SVX1

SRDF/Metro SRDFMETRO /RDFM1

Remote Mirror using SRDF/Metro METROBCV /RDFM1/BCV1

Remote Clone with emulation using SRDF/Metro METROCLN /RDFM1/CLN1

Remote native Clone using SRDF/Metro METRONCL /RDFM1/NCL1

Remote SnapVX using SRDF/Metro METROSVX /RDFM1/SVX1

User-defined configurations and paths

Multiple BCVs each with a unique path name and step MULT_BCV1 MULT_BCV2 MULT_BCV3 MULT_BCV4

/BCV1 /BCV2 /BCV3 /BCV4

Concurrent RDF (RDF1 and RDF2) requires two path names

CONC_SRDF1 CONC_SRDF2

/RDF1 /RDF2

Concurrent BCV (BCV1 and BCV2) with unique steps CONC_BCV1 CONC_BCV2

/BCV1 /BCV2

Multihop to third array:

(STD/R1 R2 BCV/R1 R2) (STD/R1 R2 BCV/R1 R2 BCV/R1) (STD BCV/R1 R2 BCV/R1 R2 BCV)

YOURPATH1 YOURPATH2 YOURPATH3

/RDF1/BCV1/RDF1 /RDF1/BCV1/RDF1/BCV1 /BCV1/RDF1/BCV1/RDF1/BCV1

Predefined configurations and paths

SRDF (STD/R1 R2) SRDF /RDF1

Cascaded SRDF CASCADRDF /RDF1/RDF1

Table 2 Predefined and user-defined configurations and paths

Configuration type Path name Steps in the path

56 Configuring the Environment

Step Types Table 3 lists step types and the number of replication copies that SRDF/TimeFinder Manager allows for each step.

Working with paths The following sections show how to work with paths.

Adding or creating paths A path must be created when data needs to be moved in a way that is not already defined.

If a step in any path contains the same source and target devices on the same source and target array, the step type should be the same for all paths. A unique combination of the source and target devices must have a unique step type in all the paths.

To add a path, do one of the following:

Option 1 - add path

On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 2. Work with Paths to display the Work with Available Paths screen (Figure 19).

Figure 19 Work with Available Paths screen

Table 3 Supported step types for SRDF and TimeFinder operations

Replication step type Number of replication copies allowed Description

RDFn n = 1 or 2 Data is replicated by SRDF. Concurrent RDF can have up to two target devices.

BCVnnnn Maximum number of TimeFinder copies allowed is limited by the version the arrays operating environment.

Data is replicated by TimeFinder/Mirror.

CLNnnnn Data is replicated by TimeFinder/Clone emulation.

NCLnnnn Data is replicated by TimeFinder/Clone.

NOTE: The PreCopy flag has been removed for /NCL paths for PowerMaxOS 10 (6079) and above.

SVXnnnn Data is replicated by TimeFinder/SnapVX.

Configuring the Environment 57

Option 2 - add path

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths on the Configuration by Image screen to display the Work with Associated Paths screen (Figure 20).

Figure 20 Work with Associated Paths screen add path

Option 3 - add path

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, (Figure 3) select option 1. Work with Images.

The Configuration by Image screen (Figure 5) appears.

2. Enter 8 (Associate path) in the Opt column of the image you want to associate a path with and press Enter.

The Paths not Associated with the Image screen (Figure 21) appears.

NOTE: A warning message appears when BCV and CLN paths are associated from the Paths not Associated with the Image screen when running on PowerMaxOS 10 (6079) and above. The path is still added, but these paths can only be associated on versions lower than PowerMaxOS 10 (6079) when using STM 10.0.

58 Configuring the Environment

Figure 21 Paths not Associated with the Image screen

3. From any of these screens press F6 (Add path).

The Paths defined on the System screen appears (Figure 22), which lists all the defined paths.

Figure 22 Paths Defined on the System screen

4. Provide the following information:

a. Enter Path Name Type the name associated with one or more steps to be used in the replication schema.

b. Enter Path Type the path to use to replicate data from a source device to a target device. See Working with paths for more information about paths.

Configuring the Environment 59

5. Press Enter to save the changes.

NOTE: When you press F6 (Add path) from the Work with Associated Paths screen, the new path is immediately associated with the image.

Figure 23 New paths added to screens

If additional paths are required, repeat step 1 through step 3.

Removing or disassociating a path To remove (disassociate) a path:

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Configuration by Image screen (Figure 5).

2. On the Configuration by Image screen, select option 2. Work with paths to display the Work with Associated Paths screen (Figure 19).

3. On the Work with Associated Paths screen, enter 4 in the Opt column of the path to be removed from the image file.

Depending on how the path is configured, the result is one of the following:

If the first step in a path is not configured, the path is disassociated from the image without warning.

If a path has configured steps, the Disassociating a Path screen (Figure 24) prompts to disassociate the selected path or cancel the operation.

If a path has a step in which a Clone is not terminated or a clone-enabled BCV is not canceled, the path cannot be disassociated.

User-defined

User-defined

60 Configuring the Environment

Figure 24 Disassociating a Path screen

4. Type Y and press Enter.

The Work with Associated Paths screen appears stating that the path name selected has been disassociated from the image.

SRDF/TimeFinder Manager does not delete disassociated paths. These paths remain available on the Paths not Associated with an Image screen for another association with the same image or a different image.

To permanently delete a disassociated path, follow the steps in Deleting a path.

Deleting a path Delete a path as follows:

1. On the Work with Available Paths screen (Figure 19), enter 4 in the Opt column of the path name to be removed.

Depending on the status of the path, the result is one of the following:

If the path is associated with any image, the Deleting a Path Associated with an Image screen appears a prompt to delete the path and all its pairing information or cancel (Figure 25).

Figure 25 Deleting a Path Associated with an Image screen

Configuring the Environment 61

If the path is not associated with any image, Figure 26 appears a message confirming path deletion.

Figure 26 Deleting a Path Not Associated with an Image screen

2. Type Y and press Enter.

The Work with Available Paths screen (Figure 19) appears with the selected path deleted.

Associating paths with an image The following steps describe how to associate paths with an image:

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, (Figure 3) select option 1. Work with Images.

The Configuration by Image screen (Figure 5) appears.

2. Enter 8 in the Opt column of the image you want to associate a path with and press Enter.

The Paths not Associated with the Image screen (Figure 21) appears. Enter option 1 in the Opt column of one or more names of the paths you want associated with the image, and press Enter.

SRDF/TimeFinder Manager associates all paths you selected and displays the Configuration by Image screen (Figure 5).

NOTE: A warning message appears when BCV and CLN paths are associated from the Paths not Associated with the Image screen when running on PowerMaxOS 10 (6079) and above. The path is still added, but these paths can be associated on versions lower than PowerMaxOS 10 (6079) when using STM version 10.0.

3. On the Configuration by Image screen, enter 2 in the Opt column of the image.

The Work with Associated Paths screen (Figure 27) appears, which contains all paths that have been associated with the image. In this example, the image is SYSTEM. Note that all ASPs in the image have the same paths available.

.

Figure 27 Work with Associated Paths screen associating paths with image

62 Configuring the Environment

Configuring device pairs After an image is selected, and a path is associated with the image, create pairs of all BCV or Clone devices used in the TimeFinder replication solution.

Pairing overview and rules for replication pairs The BCV device pairing algorithm attempts to prevent the selection of a BCV device that is on the same physical drive as one of the mirrors of the standard device. If a BCV has two mirrors, only the first mirror is checked.

To search for the optimal BCV pair, SRDF/TimeFinder Manager uses the following selection criteria by priority:

1. If a BCV exists, that was the last BCV paired and established with the current standard device, SRDF/TimeFinder Manager selects this BCV device first if the BCV is not on the same physical drive. If not, the search continues. The best BCV pair to use is a device with the same emulation or a compatible emulation as the standard device that is not on the same physical disk as any of its mirrors.

2. If SRDF/TimeFinder Manager cannot find a compatible BCV device that is not on the same disk as one of the mirrors, it performs the pairing sends an informational message CTL0083 to the job log. This message states the standard and BCV devices numbers.

3. If SRDF/TimeFinder Manager finds an optimal BCV device for a standard or R2 device, but this standard or R2 device was previously established with a different BCV device, it sends an informational message CTL0009 or CTL0083 to the job log The message states the standard device is now paired with the BCV device but was previously paired with a different BCV device.

Dynamic SRDF pairing is available from SRDF/TimeFinder Manager as Dynamic SRDF pairs describes.

Table 4 lists the configuration (pairing) action for each supported replication step type.

Table 4 Configuration actions for replication types (page 1 of 2)

Replication step type Description Configuration (pairing) action

RDF1 Single SRDF (SRDF/S or SRDF/A) available for the source devices for this step.

If pairing R1-R2 devices is predefined - no user action is required. See RDF group or device compatibility for more information on RDF group/device pairing.

RDF1, RDF2 Concurrent RDF If SRDF/TimeFinder Manager performs automatic RDF group selection, no user action is required.

NOTE: When a path is associated with the image in a Concurrent RDF configuration, SRDF/TimeFinder Manager picks the first group in the list for all devices that belong to the image and the same RDF group. For example, if R1 devices are in RDF group 0B and 0E, /RDF1 always picks RDF group 0B and /RDF2 will always pick 0E.

See RDF group or device compatibility for more information on RDF group/device pairing.

BCVnnnn TimeFinder/Mirror Requires device pairing: automatic or manual.

NOTE: The maximum number of TimeFinder copies allowed is limited by the version of PowerMaxOS or HYPERMAX OS.

Configuring the Environment 63

BCV device pairing BCV device pairing can be performed as follows:

Automatically When you are pairing by image, SRDF/TimeFinder Manager automatically makes selections as described in Pairing overview and rules for replication pairs. For example, when you perform BCV pairing, the Pair option attempts to find a matching available BCV device on the array and pairs the standard or R2 device with a BCV device for the specified image.

Using a device file with source and target device pairs - A text file containing pairs of source and target devices. See Creating a device file for more information.

Manually You can individually select the BCV device from the All STD/BCV Devices of Matching screen to pair with a standard device.

TimeFinder/Clone device pairing The source and target devices in a TimeFinder/Clone device pair can be either standard devices or BCV devices as long as they are all of the same size and type. Once it is activated, the copy can be instantly accessed by a target's host, even before the data is fully copied to the target device.

For target devices that are BCV devices, automatic pairing is performed. For standard target devices, either the name of the file containing these devices must be provided or manual pairing must be performed.

For TimeFinder/Clone emulation sessions, source devices can only be standard devices and target devices can only be BCV devices.

NOTE: Do not mix standard and BCV devices for TimeFinder/Clone (NCLn) step device pairing, if planning to use TimeFinder Consistency Group ECA (SPLITWA) splits. Use either standard or BCV devices for the entire group of devices.

SnapVX device pairing Copies are created directly in the Storage Resource Pool of the source device, so no target device needed except for Link, Relink and Unlink actions. Pairing for this step type can only be done from a device file. See Creating a device file for more information.

Pairing devices Devices can be paired using the following methods:

Automatic SRDF/TimeFinder Manager attempts pairing all devices in the image.

Manual each target is individually selected and paired.

CLNnnnn TimeFinder/Clone Requires device pairing: automatic or manual.

NOTE: The maximum number of TimeFinder copies allowed is limited by the version of PowerMaxOS or HYPERMAX OS.

NCLnnnn TimeFinder/Clone Requires device pairing: automatic or manual.

NOTE: The maximum number of TimeFinder copies allowed is limited by the version of PowerMaxOS or HYPERMAX OS.

SVXnnnn TimeFinder/SnapVX Copies are created directly in the Storage Resource Pool of the source device, no target device needed except for Link, Relink and Unlink actions. Pairing for the SVXn type of step is done only from a device file. Manual pairing at the device level is allowed.

NOTE: The maximum number of TimeFinder copies allowed is limited by the version of PowerMaxOS or HYPERMAX OS.

Table 4 Configuration actions for replication types (page 2 of 2)

64 Configuring the Environment

Using a device file with source and target device pairs - A text file containing pairs of source and target devices. See Creating a device file for more information.

NOTE: For SRDF pairing operations, static pairing occurs during initial array configuration, and dynamic pairing occurs while the array is in operation. For arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 only dynamic SRDF groups are supported. To support dynamic SRDF groups, the CTLRDFGRP (Control Dynamic RDF Group) command is available.

Pairing Devices automatically To set up device pairing:

1. On the Work with Associated Paths screen, enter 6 in the Opt column of the step of the associated path for the image. The TimeFinder Pairing Options screen appears (Figure 28).

Figure 28 TimeFinder Pairing Options screen

2. Enter Auto Pairing option as follows:

YES Automatic pairing is performed. For NCLn (TimeFinder/Clone) type of the step, target devices are chosen from available BCV devices.

NO Automatic pairing is not selected. The name of the device file containing pairs of source and target devices must be provided.

NOTE: See Creating a device file before entering a device file name.

For SnapVX, the Device File Used for SnapVX Pairing screen appears.

Configuring the Environment 65

Figure 29 Device File used for SnapVX

For TimeFinder/Mirror and TimeFinder/Clone when automatic pairing is selected, the devices are automatically configured by SRDF TimeFinder Manager. The Work with Associated Paths screen appears with the Status field updated (Figure 27).

Pairing devices manually for BCV, Clone, or SnapVX devices See Miscellaneous Device Information for a list of compatible devices. Perform device pairing as follows:

1. On the Disk Units screen enter 6 in the Opt column of the device (Figure 30).

NOTE: For the SnapVX type of step the Disk Unit screen contains different header information. (Figure 35).

Figure 30 Disk Units screen with Pair option for device not paired

For a step type of Clone and SnapVX, the Type of the target device screen appears (Figure 31).

66 Configuring the Environment

Figure 31 Type of the target device screen

2. Choose the target device type (Standard or BCV).

3. The All STD/BCV Devices of matching emulation screen appears (Figure 32).

Figure 32 All STD/BCV devices of matching screen

The All STD/BCV devices of matching screen displays a list of the STD/BCV devices that are of the same or compatible type as the source type.

4. Use Option 1=Pair with Standard for pairing devices.

The Disk Units screen appears with the device paired (Figure 33).

Configuring the Environment 67

Figure 33 Disk Units screen with device paired

Creating a device file

The device file contains pairs of source and target devices. It is a record file and the maximum record length is 40.

Device file rules are as follows:

Contains three columns, column one lists the array serial number, column two lists the source device name, and column three lists the target device name.

Each array serial number and corresponding device pair must be listed on a separate line in the device file with the data delimited by a space.

Comment lines are allowed and they must begin with the pound sign (#).

Device file resides in the library list.

The device file can be created using the following command:

CRTPF FILE(QGPL/file_name) RCDLEN(40)

Example device file

# PAIRING FOR CLONE STEP 000111222333 0179 0310 000111222333 0195 0334 000111222333 0181 0314

The format of the device file is the same for all TimeFinder technologies, including SnapVX. The only difference is the commented header description.

NOTE: The data in the device file can be amended using the IBM upddta commands. For more details on this command see the IBM web site.

Viewing devices This section shows how to view device information and device details.

Viewing device status and information

1. To view status and specific device information for a step, do one of the following:

On the Work with Associated Paths screen, enter option 5=Work with disk units in the OPT field, next to the step, and press Enter.

68 Configuring the Environment

On the Symmetrix Configuration by Image screen, enter option 5=Work with disk units on the image level or ASP level.

The Disk Units screen (Figure 34) displays all disks for this step of the associated path. Information for non-Symmetrix physical drives displays blank.

Figure 34 Disk Units screen Clone type of step

For the SnapVX type of step the Disk Unit screen contains different header information (Figure 35).

Figure 35 Disk Units screen SnapVX type of step

Configuring the Environment 69

Viewing mapping information To view mapping information (Figure 36) for all devices in the step (source and target), press F10=Symmetrix View.

Figure 36 Mapping View screen

Viewing Disk Units in IBM i view To display the Disk Units screen (Figure 37) showing source devices in the IBM i view, press F11.

Figure 37 Disk Units screen IBM i View

Press F11 to return to the Disk Units screen (Figure 34) in the view.

Displaying device details To display details for a device, from the Disk Units screen, enter option 5=Show details next to the device.

70 Configuring the Environment

The Disk Units Details screen appears. This screen displays details about the selected device. For thin devices the thin pool that the device is bound to is displayed, as shown in Figure 38.

Figure 38 Disk Units Details screen for thin device

Controlling TimeFinder 71

5

Controlling TimeFinder Invisible Body Tag

This chapter sets out the procedures for controlling TimeFinder operations using the SRDF/TimeFinder Manager Control Menu.

Topics:

Overview Establish/Re-establish BCV or Clone emulation pairs Split BCV or Clone emulation pairs operation TimeFinder/Clone operations Canceling or terminating device pairs Unpairing BCV or Clone devices TimeFinder/SnapVX operations Monitoring TimeFinder operations Automating TimeFinder operations

Overview SRDF/TimeFinder Manager relies on a specific sequence of operations to ensure that proper execution of TimeFinder control options. SRDF/TimeFinder Manager checks the configuration and operation considerations prior to executing any command that changes the state of a device or the system.

NOTE: SRDF/TimeFinder Manager does not perform a discover process automatically, which can take several minutes to run. After any change to the configuration of the host or array, turn on the discover function or run the DISCOVER command. See Discovering array and host configuration details for more information.

TimeFinder control operations are performed on images in which all devices are PowerMax, VMAX All Flash, VMX3, or VMAX array devices. Control operations are performed at the step level in the path for each image.

Establish/Re-establish BCV or Clone emulation pairs The Establish operation copies the contents of the standard device to the BCV device and performs the following tasks:

For a standard BCV, assign the BCV as the next available mirror of a standard array device.

Copy the entire contents of the standard array device to the BCV device.

If standard BCV devices are used in the BCVn step (established and split), and then used in the Clone emulation (CLNn) step, SRDF/TimeFinder Manager performs a full Establish.

The BCV device is unavailable to any host while the BCV device is in this established state.

After you establish BCV pairs, the array device automatically copies the data from its standard device mirrors to the newly assigned BCV device mirror. The array mirroring function also automatically writes to the BCV device all writes that occur on the standard device, while it is in the established pair state.

When you use Establish for BCV pairs that have been established previously (re-establishing a BCV pair), the array copies, to the BCV device, only those updates made to the standard device that occurred while the BCV pair was split.

Establish or re-establish BCV pairs 1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT)

screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the ESTABLISH control action.

72 Controlling TimeFinder

The EMC SRDF/TimeFinder Ctrl (CTLACT) screen appears with a Protected BCV Establish prompt.

4. Type *YES or *NO for the PROT_ESTAB parameter depending upon the configuration.

The Confirm Establish BCV pairs or the Confirm Establish CLONE emulation pairs screen (Figure 39) appears.

SRDF/TimeFinder Manager attempts to perform TimeFinder operations on all ASPs in the image. Remove any ASPs that are not eligible for the operation. For more information, see Removing ASPs from an image.

You can monitor the synchronization process through the array configuration and status option. See Monitoring invalid and % copied tracks for more information.

Figure 39 Confirm Establish BCV pairs and CLONE emulation pairs screens

5. Type Y to continue.

SRDF/TimeFinder Manager establishes the BCV or Clone emulation pairs.

Split BCV or Clone emulation pairs operation When a Split operation is issued on a step of the image, the Split occurs for all BCV devices or Clone emulation pairs in that step.

By default, SRDF/TimeFinder Manager performs an instant split, and checks to ensure that synchronization is complete between all specified standard and BCV mirrored pairs, or standard and Clone emulation pairs.

A check for complete synchronization ensures that the split pair contains an updated, consistent copy at the time of the termination. After the Split operation for the BCV or Clone emulation pairs completes, the host can resume operation with the standard array device. Figure 40 shows the Split BCV pairs or Split Clone emulation pairs operation.

Restricted state and daemon jobs When using split or activate you can hold all jobs, bring the system to a restricted state, use split while active, or do a maintenance split/activate. The hold jobs option holds all jobs and job queues in the system except for the daemon jobs Storapid and Storgnsd.

Additionally, choosing the restricted state option does not stop the subsystem where Storapid and Storgnsd are running. Other jobs that are running in that same subsystem are stopped using the STMENDSBS command. This command stops all subsystems.

During a split, The STMENDSBS command checks status of the subsystems for the restricted state. The split fails and you are asked to hold jobs when any of these conditions exist:

The required daemons are not running.

There are other jobs running in the subsystems where the daemon jobs are running.

There are subsystems running, other than the subsystems where the daemon jobs are running.

Controlling TimeFinder 73

Figure 40 Split operation for BCV or Clone emulation pairs

The following sections describe the TimeFinder operations.

Split BCV pairs: Restricted state This procedure uses the restricted state to ensure that I/O activity is halted before the BCV pair split. If you need to hold jobs and job queues rather than bring the system to a restricted state, see Split BCV pairs: Hold jobs and job queues.

The amount of time needed to move a host into the restricted state depends on the system configuration. By default, SRDF/TimeFinder Manager waits 1800 seconds for control to return, after issuing the command to bring the system to a restricted state. If additional time is required to bring the system to a restricted state, use the procedure Setting the restricted state wait time.

For IASP images, see SRDF/TimeFinder Manager Extended Features.

To split BCV pairs in a restricted state:

1. Bring the IBM i host to a restricted state:

a. Prepare for bringing the system to a restricted state, using internal procedures established by your company.

b. On the Control Menu, select option 5. Bring system to a restricted state.

The STM End Subsystem Confirmation screen appears.

NOTE: The system is normally set to the restricted state before the TimeFinder split is performed.

c. Press F10.

Start SRDF/TimeFinder Manager

Subsystems must be stopped

Yes Bring system to a restricted state

Split BCV pairs or Clone pairs

Start subsystems

Yes

No

No

Exit

Hold Jobs and job queues

Split BCV pairs

Release Jobs and Job Queues

Resume normal operations

Continue normal operations

Split devices

while active (SPLITWA)

Continue normal operations

Subsystems remain online

Hold Jobs and job

queues?

74 Controlling TimeFinder

The STM End All Subsystems (STMENDSBS) screen (Figure 41) appears.

Figure 41 STM End All Subsystem (STMENDSBS) screen

d. Enter options for How to End and Controlled end delay time, and press Enter.

After the End Subsystem operation completes, the Control Menu appears.

2. Split BCV pairs:

a. Select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

b. Provide the Image Name, Path Name, and Step Number.

c. Select the SPLIT control action.

The Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen reappears with a Split/Suspend Mode prompt.

d. Enter RESTRICTED for the SPLIT_MODE parameter.

SRDF/TimeFinder Manager checks if the system is in a restricted state. If not, SRDF/TimeFinder Manager asks if you want to hold jobs or job queues.

Figure 42 System not in restricted state screen

To continue operation in HOLD_JOBS mode, see Split BCV pairs: Hold jobs and job queues and take the appropriate action.

A message screen appears indicating that the Split BCV pairs operation has started.

SRDF/TimeFinder Manager attempts the Split BCV pairs operation on all ASPs in the image. ASPs that are not eligible for the operation must be removed. For more information, see Removing ASPs from an image.

3. Start subsystems:

a. On the Control Menu, select option 6. Start subsystems.

NOTE: Start subsystems does not power cycle the IBM i host or restart the operating system.

Start subsystems calls the program defined in the system value QSTRUPPGM. If additional start-up procedures are used, run them separately.

b. Resume normal operations on the source IBM i host.

Controlling TimeFinder 75

Split BCV pairs: Hold jobs and job queues This procedure holds jobs and job queues to ensure that I/O activity is halted prior to a TimeFinder Split operation.

NOTE: Daemon jobs are not put on hold.

CAUTION: System activity that results in a write operation can continue while jobs and job queues are on hold. For example, a restore job could have write operations continue while it is held. If you are not sure that the hold jobs and job queues option completely suspends write operations to the selected image, bring the system to a restricted state before doing a Split operation. See Split BCV pairs: Restricted state for more information.

To split BCV pairs with jobs and job queues on hold:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the SPLIT control action.

The Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen reappears with a Split/Suspend mode prompt.

4. Enter HOLD_JOBS for the SPLIT_MODE parameter.

NOTE: The BCV pair status for the image must be in an eligible state.

SRDF/TimeFinder Manager repeatedly attempts to put all jobs and job queues on hold, and then carries out the Split operation.

If one or more jobs or job queues remain active, the Confirmation Window screen (Figure 43) appears.

Figure 43 Confirmation Window screen

5. Select the appropriate option:

1 - Try again to hold Jobs/Queues SRDF/TimeFinder Manager repeatedly attempts to hold all jobs and job queues.

If jobs or job queues are not on hold, the Confirmation Window screen reappears.

2 - Continue Split/Suspend operation Accept that some jobs remain active and continue with the Split or Suspend operation.

CAUTION: Selecting Continue Split/Suspend operation acknowledges that some write activity can continue during the Split operation. If any writes occur to the specified ASP during the Split operation, the resulting copy is not valid.

3 - Abort Do not perform the Split or Suspend operation and return to the Control Menu.

5 - Display, what is not on HOLD Show a list of the jobs and job queues that SRDF/TimeFinder Manager cannot hold (Jobs Not on Hold and Job Queues Not on Hold screens).

76 Controlling TimeFinder

Figure 44 Jobs Not on Hold and Job Queues Not on Hold screens

6. Press F3 or Enter to return to the Confirmation screen (Figure 43).

After all jobs and job queues are successfully on hold, or you select option 2 - Continue Split/Suspend operation, SRDF/TimeFinder Manager performs the Split operation.

A message screen appears indicating that the Split BCV pairs operation has started.

After the Split operation completes, all jobs and job queues held by SRDF/TimeFinder Manager are released.

7. Optionally, use the Work with Associated Paths screen or the Disk Units screen to monitor and verify the change in BCV pair status. See Monitoring TimeFinder operations for more information.

8. Resume normal operation on the source IBM i host.

Split BCV pairs: Maintenance The Split operation in maintenance mode splits BCV pairs without interfering with the source host operations.

NOTE: This type of Split operation results in a BCV copy that is not usable as a backup. If you intend to use the BCV copy, use the RESTRICTED or HOLD_JOBS options.

Perform a Split operation in maintenance mode only when you need to IPL the secondary host with attached BCV devices. The secondary host cannot IPL while the BCVs are established with the standard devices. Therefore, perform a split before attempting an IPL.

To split BCV pairs for maintenance:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the SPLIT control action to perform.

The Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen reappears with a Split/Suspend mode prompt.

4. Enter MAINTENANCE for the SPLIT_MODE parameter.

The SRDF/TimeFinder Manager performs the Split operation without interfering with the source host operations.

TimeFinder Split: Split While Active Split While Active enables SRDF/TimeFinder Manager to split local/remote BCVs or Clone emulations, or Clone images while the source system is operational. A consistent split ensures dependent write consistency for all devices in the selected step.

The SYMAPI server jobs must be running on the source and controlling hosts before you run this option.

The netcnfg file must be configured on the client using the CRTNETCNFG command. This ensures that the correct information points to the remote server. IBM i systems support non-secure connections only. CRTNETCNFG has details of this command.

NOTE: Use caution when performing this type of split as the data in main memory is not included in the image. Use SPLITWA only when the host and applications are in a quiescent state. If that is unacceptable to your business needs, use other operating system functions like journaling and database commitment control to get an image current with the last transaction.

Controlling TimeFinder 77

To split BCV, Clone emulation, or Clone pairs while active:

Run the CTLACT command from the command line (see CTLACT).

NOTE: Since I/O is briefly being held for all devices, including the devices in the system ASP, the control action needs to be executed from a different host (see CTLACT).

Access the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen and select the appropriate control action:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Control (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number

3. Select the SPLIT/ACTIVATE control action to perform.

The EMC SRDF/TimeFinder Ctrl (CTLACT) screen reappears with a Split/Suspend mode prompt.

4. Enter SPLITWA for the SPLIT_MODE parameter.

The SRDF/TimeFinder Manager performs the Split while active operation without interfering with the source host operations.

Cancel BCV or Clone emulation pairs To cancel a BCV or Clone emulation pairing relationship:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the CANCEL control action.

The Confirm Cancel BCV pairs or the Confirm Cancel CLONE emulation screen (Figure 45) appears.

Figure 45 Confirm Cancel BCV pairs and CLONE emulation session screens

4. Type Y to continue.

The incremental relationship between the standard and the BCV volume is canceled and all record of track changes is removed. If the devices are clone-enabled BCVs, the clone sessions are terminated on the array.

NOTE: Repairing and establishing the same devices results in a full establish.

78 Controlling TimeFinder

TimeFinder/Clone operations The TimeFinder/Clone specific operations are Create/Recreate, Activate, and Terminate.

Creating a Clone copy session 1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Ctrl

(CTLACT) screen (Figure 73).

Figure 46 EMC SRDF/TimeFinder Ctrl (CTLACT) screen create Clone session

2. Provide the Image Name, Path Name, and Step Number.

3. Select the CREATE control action.

NOTE: For a list of all control action parameters, press F4 on the Control Action prompt.

4. Enter Clone options.

If a session previously was created and activated a confirmation screen appears (Figure 47) and recreate action is performed.

Figure 47 Confirm Recreate CLONE copy session screens

SRDF/TimeFinder Manager creates the Clone copy session and displays a completion message.

Activating a Clone copy session 1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Ctrl

(CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

Controlling TimeFinder 79

3. Select the ACTIVATE control action.

NOTE: For SPLIT_MODE, use the appropriate mode, see Split BCV or Clone emulation pairs operation.

SRDF/TimeFinder Manager activates the copy session and displays a completion message.

Canceling or Terminating TimeFinder session Depending upon the selected device type, use the Cancel/Terminate option to either:

Terminate a TimeFinder/Clone copy session.

Cancel an incremental relationship between a standard device and a BCV device that are currently a pair in the BCV set. If the devices are clone-enabled BCVs, the clone sessions are terminated on the array.

Terminating a Clone copy session

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the TERMINATE control action.

The Confirm Terminate CLONE session screen appears (Figure 48).

Figure 48 Confirm Terminate CLONE Session

4. Type Y to continue.

SRDF/TimeFinder Manager terminates the copy session and displays a completion message.

Canceling or terminating device pairs To cancel BCV device pairs or terminate Clone copy sessions:

From the Disk Units screen, type 8 (Cancel) in the OPT field next to the selected device pair.

To cancel multiple device pairs, type 8 (Cancel) next to each entry and the selected pairs are canceled at the same time.

After the Cancel operation, the status for BCVn or CLNn types of the step become NeverEstab, for NCLn types of the step become NotCreated. Any subsequent Establish/Create operation is a full Establish.

CAUTION: Run the Cancel operation before doing the unpairing operation on RAID 5/RAID 6 or mixed BCVs, clone-enabled devices, or clone devices. Not running the Cancel operation causes hanging Clone sessions to remain on the array.

Unpairing BCV or Clone devices Device unpairing makes BCV and Clone devices reusable.

To unpair devices, type 7 (Unpair) on the Work with Associated Paths screen next to the step to be unpaired or from the Disk Units screen next to the unit number of the source device.

To unpair multiple device pairs type 7 (Unpair) next to each entry and the selected pairs are unpaired at the same time.

80 Controlling TimeFinder

BCV device unpairing For a standard or R2 device paired with a BCV device, the unpair option on a device removes pairing information, for the specified image.

A BCV pair cannot be unpaired while the devices are in a Synchronized, Restored, SyncInProg, or RestInProg state. Prior to performing this operation, the pairs must be split and canceled.

If clone emulation is enabled for the BCV pair, cancel the relationship prior to unpairing. If the BCVs were established, the information about the previous standard/BCV relationship is stored in the SYMAPI database. To recover the information about the devices, the devices must be paired again.

Clone device unpairing For a standard or BCV device paired with a standard or BCV device, the unpair option on a device removes pairing information, for the specified image.

Clone device unpairing cannot be done unless they are in a NotCreated state. Prior to performing this operation, terminate the pairs.

Recovering from a NotConsistent state When BCV device pairs, in a step of an image, are at different states (for example one pair is in Synchronized state and another in Split state), the BCV status for that step of the image becomes NotConsistent.

To recover from a NotConsistent state:

For BCV or Clone emulation devices, perform the Establish operation on BCV or Clone emulation pairs.

The Establish operation on BCV or Clone emulation pairs checks the state of each device pair that belongs to each step of the image.

If the state is eligible for the Establish command, the operation starts for that device pair. Otherwise, the job log receives an error message providing the device numbers and their status information.

For Clone devices, perform a Create operation.

The Create operation checks the state of each device pair that belongs to each step of the image. If the state is eligible for the Create command, the operation starts for that device pair. Otherwise, the job log receives an error message providing the device numbers and their status information.

NOTE: Contact Dell Customer Support for assistance with bringing devices back into an eligible state.

TimeFinder/SnapVX operations TimeFinder/SnapVX specific operations are Establish, Link/Relink, Unlink, Set Copy Set NoCopy, Set TTL, Restore, Rename Snapshot, and Terminate.

Establishing SnapVX session A SnapVX session can be established from the Dell EMC SRDF or TimeFinder Control (CTLACT) screen, or with option 14 (Establish/Create) on the Work with Associated Paths screen. The Establish control action creates and activates a SnapVX session.

Controlling TimeFinder 81

Using the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen (Figure 49).

Figure 49 Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen create SnapVX session

2. Provide the Image Name, Path Name, and Step Number.

3. Select the ESTABLISH control action.

4. Enter the SnapVX Establish Mode: (the mode to use for the SnapVX Establish operation):

RESTRICTED System must be put in restricted state using the STMENDSBS command.

CONSISTENT No interference with the host operations. By default all snapshots are consistent.

NOTE: Use Consistent Establish with care, as the data in main memory is not included in the image. Use this only when the host and applications are in a quiescent state. If that is unacceptable to your business needs, use other operating system functions like journaling and database commitment control to get an image current with the last transaction.

HOLD_JOBS All jobs and job queues will be put on HOLD.

NOTE: To display a list of all control action parameters, press F4 on the Control Action prompt.

5. Type a Snapshot Name.

The name can be used for multiple devices and/or multiple snapshots. For multiple snapshots for the same device with the same name, a generation number (Gen) is used to differentiate between these point-in-time copies. Snapshots and generation numbers are time stamped and are listed from newest to oldest with Gen 0 being the most recent snapshot.

6. Optional: Enter the Time To Live (TTL) Sets the time when the snapshot is automatically terminated, and is specified in days from now (DAYS) or a future date can be set (DATE). The value in DAYS can be set from one to 400. The DATE value can be set to a date up to 400 days in the future from the time the ESTABLISH action occurs.

If a snapshot has TTL set and has one or more link targets, it is not terminated until links are unlinked. If the TTL value is not specified, the snapshot remains until it is manually terminated.

SRDF/TimeFinder Manager creates and activates the SnapVX session and displays the snapshot status as EstablishInProg while the copy is in progress. It then displays the status as Establish when the data is fully copied. Once established the snapshots are uniquely identified by name, Gen number, and source device for control actions.

82 Controlling TimeFinder

Using the Work with Associated Paths screen

1. On the EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

Figure 50 Work with Associated Paths

NOTE: If SVXn step is paired but no snapshots are established for the devices in the step, the status displays as NoSnapshots.

3. Enter 14 in the Opt column of a SnapVX type of step, to display the Existing Snapshots screen (Figure 51).

Figure 51 Existing Snapshots screen

4. Type a Snapshot Name.

The name can be used for multiple devices and/or multiple snapshots. For multiple snapshots for the same device with the same name, a generation number (Gen) is used to differentiate between these point-in-time copies. Snapshots and generation numbers are time stamped and are listed from newest to oldest with Gen 0 being the most recent snapshot.

5. Optionally, enter the Time To Live (TTL) Sets the time to when the snapshot is automatically terminated, and is specified in days from now (DAYS) or a future date can be set (DATE). The value in DAYS can be set from one to 400. The DATE value can be set to a date up to 400 days in the future from the time the ESTABLISH action occurs.

If a snapshot has TTL set and has one or more link targets, it is not terminated until links are unlinked. If the TTL value is not specified, the snapshot remains until it is manually terminated.

Controlling TimeFinder 83

SRDF/TimeFinder Manager creates and activates the SnapVX session and displays the snapshot status as EstablishInProg while the copy is in progress, and then displays the status as Establish when the data is fully copied.

Renaming a Snapshot

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 22 in the Opt column of a SnapVX type of step, to display the Work with Snapshots screen (Figure 52).

NOTE: The operations available from the Work with Snapshot screens, such as Link/Relink, Restore, Set TTL, Rename, and Terminate, are described in TimeFinder SnapVX.

Figure 52 Work with Snapshots screen

NOTE: If Snapshot has links, L appears in the Status field. If Snapshot has restores, R appears in the Status field. If snapshot has links and restores L/R appears in the status field.

4. Enter 7 in the Opt column of a snapshot to display the Rename snapshots screen (Figure 53).

Figure 53 Rename Snapshot screen

5. Type the New Snapshot Name.

Snapshot screens are updated with the new name.

84 Controlling TimeFinder

Displaying Snapshot details

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 22 in the Opt field of a SnapVX type of step, to display the Work with Snapshots screen (Figure 52).

4. Enter 5 in the Opt column of the snapshot to display the Snapshot Details screen.

Figure 54 Snapshot Details screen

Snapshot Details screen fields

Symmetrix

Symmetrix ID.

Snapshot

The user assigned name of the snapshot.

Gen

Generation number when there are multiple snapshots of the same name. Generation 0 is the most recent snapshot and the numbers increase for older point-in-time snapshots.

Timestamp

Time when snapshot was established.

Time to Live

The date and time when the snapshot will automatically be terminated (Time to Live feature requires auto-terminate to be the enabled state).

# Devices

Number of snapshot source devices.

Established

Number of the devices participating in the snapshot. This number will differ from the number of source devices only if of any of the devices is in a Failed or EstablishInProg state.

EstablishInProg

Number of the devices transitioning to Established state

Linked

Number of target devices linked to the snapshot in NoCopy mode.

CopyInProg

Number of the target devices linked to the snapshot in Copy mode transitioning to the Copied state.

Controlling TimeFinder 85

Copied

Number of the target devices linked to the snapshot in Copy mode when they are 100% copied.

Restored

Number of restores which are 100% restored for the snapshot.

RestoreInProg

Number of restores in transition for the snapshot.

Failed

Number of failed devices. Possible cause would be if a corruption occurs on any of the source devices.

Source Dev List of the source devices participated in the snapshot.

Status

The state of the source device is normally Established. EstablishInProg is a transition state. If a corruption occurs on device, the status would be Failed.

Tracks

The number of source tracks that have not yet been overwritten by the host.

Non Shared Tracks

The number of tracks uniquely allocated for this snapshots delta. This indicates the approximate number of tracks that will be returned to the SRP if this snapshot is terminated.

NOTE: The sum of the Established, EstablishInProg, and Failed fields should equal the number of the source devices.

Linking/Relinking Snapshots If the host needs an access to the snapshot data, target devices can be linked or relinked to the snapshot. A link presents the point-in-time data on target devices mapped to the host. A relink removes the current link to target devices and presents a different snapshot. The relink may also be used to relink to the same snapshot. This has the effect of refreshing the point-in-time copy on the link target when its been modified by host writes.

The links can be created in Copy mode for a permanent copy, when all the data is fully copied on the target device; or they can be created in NoCopy mode for temporary use.

NOTE: Previous track allocations are deallocated. Therefore, devices with persistent track allocations cannot be link targets.

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 20 in the Opt column of a SnapVX type of step, to display the List of Snapshots screen (Figure 55).

NOTE: Linking and Relinking operations can also be performed from the Work with Snapshots screen. .

Figure 55 List of Snapshots screen

86 Controlling TimeFinder

4. Enter 1 in the Opt column of a Snapshot Name, to display the Link Option screen (Figure 56).

NOTE: This does not appear in PowerMaxOS 10 (6079) and above.

Figure 56 Link Option screen

5. Select Link Type:

Y Creates a permanent copy when all data is fully copied to the link target.

N Creates a temporary copy. Point-in-time data is removed from the target device once the link is unlinked.

Viewing status of link/relink operation

From the Disk Units screen and Work with Associated Paths screen the status displays as CopyInProg while the copy is in progress, and then as Linked when the data is fully copied. If the link is performed in copy mode, the status displays as Copied.

Snapshot linking can also be performed from the EMC SRDF/TimeFinder Ctrl (CTLACT) screen using the Control Action LINK. (Figure 49).

Option 23 on the Work with Associated Paths screen (Figure 50) changes Link Mode, from NoCopy to Copy mode or from Copy to NoCopy, when the status of the step is Linked/CopyInProg/Copied.

Unlinking Snapshots Unlink all links before terminating a snapshot.

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 21 in the Opt column of a SnapVX type of step.

NOTE: Target devices can be unlinked if the status of the step is Linked or Copied.

The snapshot is unlinked from the target link. From the Work with Associated Paths screen the status of the SnapVX type of step displays as Established or Restored, if source devices are restored from snapshot.

Snapshot unlinking can also be performed from the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen using the Control Action UNLINK (Figure 49).

Setting Time to Live 1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the

Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 22 in the Opt column of a SnapVX type of step, to display the Work with Snapshots screen (Figure 52).

4. Enter 3 in the Opt column of a snapshot to display the Set Time To Live (Figure 53).

Controlling TimeFinder 87

Figure 57 Set Time to Live screen

5. Enter the Time to Live in days or date. If you do not supply a value, the Time to Live value is set to unlimited and the snapshot is kept until it is manually terminated.

Setting Time to Live can also be performed from the EMC SRDF/TimeFinder Ctrl (CTLACT) screen using the Control Action SET_TTL (Figure 49).

Restoring Snapshots 1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the

Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 22 in the Opt column of a SnapVX type of step, to display the Work with Snapshots screen (Figure 52).

4. Enter 2 in the Opt column of a snapshot to copy point-in-time data back to the original source device (Figure 53). The snapshot must be fully established to perform a restore.

NOTE: For System Image, a restore is not allowed for the first step.

A restore can also be performed from the Work with Associated Paths (Figure 50 screen, or by using the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen using the control action RESTORE (Figure 49).

Terminating Snapshots Snapshots can only be terminated if there are no links (see Unlinking Snapshots).

1. On the Dell EMC SRDF/TimeFinder Manager for IBM i main menu, select option 1. Work with Images to display the Symmetrix Configuration by Image screen (Figure 5).

2. Select option 2. Work with paths to display the Work with Associated Paths screen (Figure 50).

3. Enter 22 in the Opt column of a SnapVX type of step, to display the Work with Snapshots screen (Figure 52).

4. Enter 8 in the Opt column of the snapshot to be terminated.

NOTE: If Snapshot has restores, only restores would be terminated. Use Option 8 again to terminate a snapshot.

Snapshot termination can also be performed from the Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen using the Control Action TERMINATE. (Figure 49).

Monitoring TimeFinder operations You can monitor the TimeFinder operations at the step level from the Work with Associated Paths screen or at the device level through the Disk Units screen. These procedures are in Viewing devices.

88 Controlling TimeFinder

Monitoring invalid and % copied tracks The Disk Unit screen and the Work with Associated Paths screen each have a column labeled Invalids/%Copied.

For SRDF or TimeFinder synchronization, this column lists the number of invalid tracks remaining during the synchronization operation. On the Disk Units screen invalid track counts display at the device level, and on the Work with Associated Paths screen invalid track counts display by image.

For TimeFinder/Clone and TimeFinder SnapVX operations, this column represents the percentage of copied tracks.

NOTE: The invalid tracks information is accurate only while synchronization is in progress. The invalid track information is not accurate while devices are Split or Activated.

For TimeFinder/SnapVX, when the COPY flag is set or when the source device is restored from the snapshot, this field displays percent of the total device size that has been copied to the target.

Automating TimeFinder operations SRDF/TimeFinder Manager provides the option of incorporating TimeFinder control operations in customized CL programs. The CL command, CTLACT, includes the following TimeFinder control actions and parameters:

TimeFinder/BCV control actions are as follows:

ESTABLISH Establishes/re-establishes BCV or Clone emulation pairs for BCV control. SPLIT Splits BCV or Clone emulation pairs for BCV control.

CANCEL Cancels the existing TimeFinder device relationship.

STATUS Provides TimeFinder control status information.

TimeFinder/Clone control actions are as follows:

CREATE Creates or recreates a clone copy session that defines and sets up the cloning devices selected for the clone operation.

ACTIVATE Activates a clone copy session to make data instantly accessible to target host.

TERMINATE Terminates a clone copy session to remove holds on target devices and delete device pairing information from the array.

The following SPLIT_MODE parameter options are available for both the SPLIT command and the ACTIVATE command:

SPLIT_MODE(RESTRICTED) Splits BCV, Clone emulation. Activates Clone while the system is in a restricted state.

SPLIT_MODE(HOLD_JOBS) Holds all jobs and job queues before performing a Split or Activate control operation.

SPLIT_MODE(SPLITWA) Splits a local or remote BCV or Clone emulation. Activates Clone while the source system is operational.

SPLIT_MODE(MAINTENANCE) Splits BCV, Clone emulation. Activates Clone in maintenance mode (that is, no interference with host operations).

TimeFinder/SnapVX control actions are:

ESTABLISH Creates and activates a SnapVX snapshot. SnapVX Establish Mode can be set to:

RESTRICTED Put a system in the restricted state by using option 5 from the Control menu using Bring System to a Restricted State, or with the STMENDSBS command. This ensures that all subsystems and jobs are ended except for the daemon jobs and their corresponding subsystems.

CONSISTENT No interference with the host operations. By default all snapshots are consistent.

NOTE: Use Consistent Establish with care as the data in main memory is not included in the image. Use this only when the host and applications are in a quiescent state. If that is unacceptable to your business needs, use other operating system functions like journaling and database commitment control to get an image current with the last transaction.

HOLD_JOBS All jobs and job queues will be put on HOLD.

STATUS Provides control status information for the step in the associated path for the image. If status of the SVXn step is Linked, CopyInProg, Copied, Restored, RestoreInProg, RestNotPaired, or RestgNotPaired, the snapshot name and generation is provided. If Snapshot name and generation are specified, state of the specified snapshot is provided.

TERMINATE Removes an existing SnapVX snapshot.

LINK Presents the point-in-time data on target devices. If target devices are already linked, relink operation would be executed.

Controlling TimeFinder 89

RENAME Changes the snapshot name.

RESTORE Copies the point-in-time data from a snapshot back to the original source device.

NOTE: If snapshot has restores, only restores are terminated.

SET_TTL Sets a time to live for a snapshot as either number of days from now or a future date from now.

SETCOPY Changes the copy mode of a link to copy.

NOTE: SnapVX no longer supports SETCOPY when running on PowerMaxOS 10 (6079) using STM IBM i version 10.0. This is still supported when running on a lower PowerMaxOS versions using STM IBM i version 10.0.

SETNOCOPY Changes the copy mode of a link to nocopy.

NOTE: SnapVX no longer supports SETNOCOPY when running on PowerMaxOS 10 (6079) using STM IBM i version 10.0. This is still supported when running on a lower PowerMaxOS versions using STM IBM i version 10.0.

UNLINK Removes the current link to target devices.

Controlling SRDF 91

6

Controlling SRDF Invisible Body Tag

This chapter sets out the procedures to control SRDF links, including how to enable and disable consistency protection for SRDF/A and set the RDF mode.

Topics:

Overview Creating and controlling SRDF Groups Setting the SRDF group attributes Dynamic SRDF pairs Setting modes of SRDF operation Establishing SRDF links Splitting or Suspending SRDF links operation Controlling SRDF/Metro Monitoring SRDF operations Recovering from NotConsistent SRDF state Listing and monitoring SRDF groups Performing dynamic SRDF personality swaps Automating SRDF operations

Overview SRDF/TimeFinder Manager relies on a specific sequence of operations to ensure proper execution of SRDF control operations. SRDF/TimeFinder Manager checks the configuration and operation considerations prior to executing a command that could change a device or system state.

SRDF Control operations are performed at the step level in the path for each image. These operations can be performed on both static and dynamic SRDF configurations, where:

Static pairing occurs during initial array configuration

Dynamic pairing occurs while the array is in operation.

Static RDF groups and devices are not supported on arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977.

NOTE: SRDF/TimeFinder Manager does not perform a discover process automatically, which can take several minutes to run per operation. After changing the configuration of a host or array, turn on the discover function or use the DISCOVER command. Discovering array and host configuration details shows how to perform a discover operation.

RDF group or device compatibility SRDF/TimeFinder Manager supports only the following array replication configurations when creating RDF groups between PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 arrays:

PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 array PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 array

Creating and controlling SRDF Groups Before creating SRDF pairs, create dynamic SRDF groups. Use the CTLRDFGRP command to add, modify, or remove dynamic groups When adding dynamic SRDF groups, there are several parameters available that control the behavior of the group.

92 Controlling SRDF

Creating dynamic SRDF groups 1. On the Control Menu, select option 10. Control Dynamic SRDF Groups to display the Control Dynamic RDF Group

(CTLRDFGRP) screen (Figure 58).

Figure 58 Control Dynamic RDF Group (CTLRDFGRP) screen

2. Provide the following information for the selected image:

Control Action Enter ADD. (Create new RDF group)

Symmetrix ID The local array ID where this command is performed.

SRDF Group Label The RDF group label.

SRDF Group Number The RDF group number.

NOTE: For the ADD action specify both of the SRDF Group Label and SRDF Group Number parameters.

SRDF Metro Witness Group Specify a value of *YES if this is a witness group for SRDF/Metro.

There can be only one witness group between two arrays.

Director/Port Combination:

Director IDent The local array director ID, such as 1a, 1b and so on. Port Number The local array director port number. (0-31)

NOTE: For PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 RDF directors support up to 32 ports.

Remote Symmetrix ID Specifies remote array where this command is performed.

Remote RDF Group Number The remote RDF group number.

Remote Director/Port:

Director IDent The remote director ID, such as 1a, 1b and so on. Port Number The remote array director port number. (0-31)

NOTE: For PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 RDF directors support up to 32 ports.

Auto Link Recovery YES (default)

Remote Auto Link Recovery YES (default)

Link Limbo 10 (default)

NOTE: Link Limbo Only experienced SRDF users should use this option.

Specifies the local link limbo value which is the length of time for PowerMaxOS or HYPERMAX OS to wait, from the point of a link-down detection, prior to updating the link status as Down. If the link status is still sensed as Not Ready after the link limbo time expires, devices are marked Not Ready to the link. The link limbo range is zero to 120 seconds. The default time is 10 seconds. This option is used only with the ADD control action.

Remote Link Limbo 10 (default). Same as link limbo except performed on a remote array.

3. Press Enter.

Controlling SRDF 93

Modifying dynamic SRDF groups (associated or dissociated local and remote director or port with RDF group) You also use the Control Dynamic RDF Group (CTLRDFGRP) screen (Figure 58) to modify a dynamic group. When doing so, the following screen or command requirements and options are available:

Control Action

Symmetrix ID

SRDF Group Label

SRDF Group Number

NOTE: You can specify either SRDF Group Label or Group Number.

Actions for Modify Add or Remove associated/dissociated local and remote director/port with the RDF group

Director/Port Combination

Remote Director/Port

Removing dynamic SRDF groups You also use the Control Dynamic RDF Group (CTLRDFGRP) screen (Figure 58) to remove a dynamic group. You can remove only an empty dynamic group. To remove a SRDF/Metro Witness group, there must be no SRDF/Metro groups using that witness group or there must be an alternative witness available for the SRDF/Metro groups to use. Alternatively, you can use the List SRDF Groups screen (Figure 72) to remove a dynamic group.

When removing a dynamic group the following screen or command requirements and options are available:

Control Action

Symmetrix ID

SRDF Group Label

SRDF Group Number

NOTE: You can specify either SRDF Group Label or Group Number.

Use Sym Force Flag

Setting the SRDF group attributes SRDF group behavior can be controlled by setting group attributes, such as whether SRDF/A DSE is automatically activated, when a SRDF/A session is activated, and how SRDF/TimeFinder Manager should handle situations where the transmission link is idling.

NOTE: For arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 DSE autostart for SRDF groups is enabled by default.

Set the SRDF/A group as follows:

1. On the Control Menu, select option 11. Set RDF Group to display the Set SRDF Group (SETRDFGRP) screen (Figure 59).

94 Controlling SRDF

Figure 59 Set SRDF Group (SETRDFGRP) screen

2. Provide the following information:

Symmetrix ID The name of the array on which this command is performed.

NOTE: If you know the array ID, enter its name. Otherwise, press F4 to display a list of all local and remote arrays attached to the host.

SRDF Group Number The number of the RA group whose parameters should be modified.

DSE auto start Whether SRDF/A DSE is automatically activated when the SRDF/A session is activated for the group. Options are as follows:

ENABLE Automatically activates SRDF/A DSE when an SRDF/A session is activated for the group.

DISABLE Does not automatically activate SRDF/A DSE when an SRDF/A session is activated for the group.

*SAME Ignores the parameter during command processing or when ENABLE/DISABLE is specified and DSE auto start is already in the desired state.

NOTE: For arrays running HYPERMAX OS 5977, PowerMaxOS 5978, or PowerMaxOS 10 (6079), DSE autostart for SRDF groups is enabled by default.

DSE threshold Specifies the percentage of the array's write pending limit. DSE threshold is an optional parameter.

Groups with higher threshold values keep their data in cache longer at the expense of groups with lower values. Valid values range from 20 to 100. If nothing is specified, or an SRDF group already has a desired DSE threshold, SRDF/TimeFinder Manager ignores this parameter during command processing.

Transmit idle Specifies how SRDF/TimeFinder Manager should handle situations where the transmission link is idling. Options are as follows:

ENABLE Tolerates SRDF/A.

DISABLE Drops SRDF/A.

*SAME Ignores the parameter during command processing or when ENABLE or DISABLE is specified and Transmit Idle is already in the desired state.

Device-level Write Pacing Specifies whether SRDF/A device-level write pacing is automatically activated when SRDF/A session is activated for the group. Options are as follows:

ENABLE Automatically activate SRDF/A device-level write pacing when SRDF/A session is activated for the group.

DISABLE Do not automatically activate SRDF/A device-level write pacing when SRDF/A session is activated for the group.

*SAME Ignores the parameter during command processing, or when ENABLE or DISABLE is specified and SRDF/A device-level write pacing is already in the desired state. This is the default.

Write Pace Autostart Specifies whether the SRDF/A group-level write pacing feature is automatically enabled or disabled when an SRDF/A session is activated for the SRDF group. Options are as follows:

ENABLE Automatically activates SRDF/A group-level write pacing when an SRDF/A session is activated for the group.

Controlling SRDF 95

DISABLE Do not automatically activate SRDF/A group-level write pacing when an SRDF/A session is activated for the group.

*SAME Ignores the parameter during command processing, or when ENABLE or DISABLE is specified, and SRDF/A group-level write pacing is already in the desired state. This is the default.

NOTE: This cannot be run if both arrays are on HYPERMAX OS level 5977 and above.

Write Pace Delay Sets the maximum host I/O delay, in microseconds, that triggers SRDF/A write pacing. Valid values are between 1 and 1000000 micro-seconds. Write pacing delay is an optional parameter. The default value is 50000 micro-seconds.

If the write pace delay is not specified, or an SRDF group already has a desired write pacing delay, SRDF/TimeFinder Manager ignores this parameter during command processing.

NOTE: This cannot be run if both arrays are on HYPERMAX OS level 5977 and above.

Write Pace Threshold Sets the minimum percentage of the system write-pending cache at which the array begins pacing host write I/Os, for an SRDF group. Valid values are between one and 99. Write pacing threshold is an optional parameter. The default value is 60.

If the write pace threshold is not specified, or an SRDF group already has a desired write pacing threshold, SRDF/TimeFinder Manager ignores this parameter during command processing.

NOTE: This cannot be run if both arrays are on HYPERMAX OS level 5977 and above.

NOTE: SRDF/A group-level write pacing feature is available PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977. If you plan to swap the personalities of the R1 and R2 devices, configure the same SRDF/A write pacing values on both devices.

Hardware compression Specifies whether to enable or disable hardware compression for the SRDF group. Options are as follows:

ENABLE Enables hardware compression for the SRDF group.

DISABLE Disables hardware compression for the SRDF group.

*SAME Ignores the parameter during command processing, or when ENABLE or DISABLE is specified, and compression for the SRDF group is already in the desired state. This is the default.

Software compression Specifies whether to enable or disable software compression for the SRDF group. Options are as follows:

ENABLE Enables software compression for the SRDF group.

DISABLE Disables software compression for the SRDF group.

*SAME Ignores the parameter during command processing, or when ENABLE or DISABLE is specified, and compression for the SRDF group is already in the desired state. This is the default.

Compression minimizes the amount of data to be transmitted over an SRDF link.

Rules and restrictions for compression are as follows:

Software and hardware compression can be enabled on the R1 and R2 sides of the SRDF link, but the actual compression takes place on the side initiating the I/O, which is typically the R1 side. Since most I/O requests are initiated from the R1 side, make sure compression is enabled on this side.

Auto Link Recovery Specifies whether to use the Auto Link Recovery feature locally.

ENABLE Enables Auto Link Recovery.

DISABLE Disables Auto Link Recovery.

*SAME Ignores this parameter during command processing, if *SAME is specified, or if ENABLE or DISABLE is specified and Auto Link Recovery is in the desired state. This is the default.

Link Limbo Specifies the length of time to wait from the point of link-down detection before actually updating the link status as down. If the link status is still sensed as Not Ready after the link limbo time expires, devices are marked Not Ready to the link. If nothing is specified, Ignores the parameter during command processing, if *SAME is specified, or if RDF group already has a desired link limbo value. The link limbo range is zero to 120 seconds. The default time is 10 seconds.

NOTE: Only experienced SRDF users should use this option.

Both Sides Flag - Specifies whether changes should be applied only locally or both locally and remotely:

*YES Changes are applied locally and remotely.

NOTE: If the remote side cannot be reached and the flag is set to YES, the command fails.

*NO Changes are applied locally. This is the default.

96 Controlling SRDF

Dynamic SRDF pairs Before creating SRDF device pairs:

Determine the device pairings and create a device file that lists R1/R2 pairs. See Creating a device file for more information.

Review Dynamic pairing restrictions.

Creating a device file The device file is a record file and the maximum length of each record is 40.

Device file rules are as follows:

The file contains two columns, column one lists the source devices and column two lists the target devices.

Each device pair appears on a separate line separated by a space.

The file can include comment lines and they begin with the pound sign (#).

The device file resides in the library list.

Use the following command to create the device file:

CRTPF FILE(QGPL/file_name) RCDLEN(40)

Example device file

# PAIRING FIRST STEP OF CASCADING RDF 08C6 1167 08CA 116B 08CE 116F

NOTE: If creating concurrent SRDF pairs, see Rules for dynamic concurrent SRDF pairing.

Creating pairs Use the Create/Delete RDF pairs screen to create SRDF pairs. There are two ways to access this screen:

Through the Control Menu screen:

On the Control Menu screen select option 12. Create/Delete RDF Pairs to display the Create/Delete RDF pairs screen (Figure 60).

Using the CRTDLTRDFP command from the command prompt:

CRTDLTRDFP

The Create/Delete RDF pairs screen appears (Figure 60).

Controlling SRDF 97

Figure 60 Create/Delete RDF pairs with Control Action CREATE

Enter parameters (see Create or Delete RDF pairs screen parameters) and press Enter.

Upon execution of the CRTDLTRDFP command with the CREATE control action the following actions occur:

SRDF pairs become members of the specified RDF group.

Pairing information is added to the SYMAPI database file on the host.

Create or Delete RDF pairs screen parameters

The following are some of the screen parameter details:

Symmetrix ID Specifies the array associated with the devices listed in the first column of the device file.

SRDF Group Number Specifies the SRDF group number associated with the devices listed in the first column of the device file.

Device File Name Specifies the name of the device file that defines the SRDF pairs.

SRDF Metro Pairing Specify a value of *YES if this pair is a SRDF/Metro device pair.

SRDF Metro Mode Specify a value of A if the SRDF/Metro configuration uses Witness protection or a value of B if the pair uses Bias protection. This value is relevant only when SRDF Metro Pairing has a value of *YES.

RDF mode Sets device pair SRDF mode to synchronous (SYNC), asynchronous (ASYNC), adaptive copy disk mode (ACDM), or Metro.

Secondary Action options:

ESTABLISH (default option) Begins copying data to the invalidated targets, synchronizing the dynamic SRDF pairs, listed in the device file, once the SRDF pairs are created.

NOTE: When RDF Mode is ASYNC and the ESTABLISH option is selected, consistency protection is automatically enabled for the new device pair after executing a CREATE operation. Also, if the SRDF group for the new devices already contains devices, the CONS_EXEMPT (consistency exempt) flag is automatically enabled. The CONS_EXEMPT flag allows devices to be added to the SRDF group without affecting the state of the SRDF/A session, or requiring that other devices in the session be suspended. Consistency protection is automatically enabled for the new device pair if it is already enabled for other devices in the group.

INVALIDATER2 Marks the R2 devices in the device file list to be the invalidated target for a full device copy once the SRDF pairs are created.

RDF Type Indicates whether the device in the first column of the device file is an R1 or an R2 device.

Rules for dynamic concurrent SRDF pairing The following rules apply when creating dynamic concurrent SRDF pairs:

Remote BCVs that have been designated as dynamic SRDF devices are not supported.

The two SRDF mirrors of the concurrent device must be assigned to different RA groups.

98 Controlling SRDF

The concurrent dynamic SRDF, dynamic SRDF, and concurrent SRDF states must be enabled in the array configuration.

Two separate device files must be created when dynamically creating a second remote mirror using the CRTDLTRDFP command. One file lists the first set of R1/R2 device pairs, and the other device file lists the same R1 devices paired with different remote R2 devices. See Creating a device file for more information.

Dynamic pairing restrictions The CREATE option fails if any of the following apply:

The device is in one of the following BCV pair states: Synchronized, SyncInProg, Restored, RestoreInProg, or SplitInProg.

There is a background BCV split operation in progress.

Devices are in the back-end Not Ready state.

The type, size of the devices, configuration are not the same, such as IBM i which has specific pairing rules.

NOTE: For migration, larger R2 devices are allowed for D910 devices.

There are existing, local invalid tracks on either the local or remote device.

The SRDF group is in asynchronous mode and the devices being added are not the same SRDF type R1 or R2.

The SRDF group is in asynchronous mode with the SRDF links suspended and the ESTABLISH option is selected.

The SRDF group is enabled for SRDF consistency.

If the operation would result in more than 64K devices being supported by any RA associated with either of the RDF groups.

Deleting SRDF pairs 1. Before deleting SRDF pairs:

Determine the device pairs to be deleted and create a device file that lists R1/R2 pairs to be deleted. See Creating a device file for more information.

Review Restrictions for deleting pairs.

2. Navigate to the Create/Delete RDF pairs screen (Figure 61).

Steps to access this screen are the same as in creating RDF pairs. See Creating pairs for more information.

NOTE: Before executing a DELETE operation, ensure that the SRDF pairs are in a Split, Suspended, or FailedOver state. If the Use of Force Flag parameter is set to YES, the delete operation is attempted regardless of the state of the SRDF devices.

Figure 61 Create/Delete RDF pairs with Control Action DELETE

Controlling SRDF 99

3. Enter parameters (see Create or Delete RDF pairs screen parameters) and press Enter.

Upon execution of the CRTDLTRDFP command with the DELETE option, the following actions occur:

SRDF pairs are canceled.

Pairing information is removed from the array and the SYMAPI database.

Devices are changed to non-SRDF devices (except for concurrent SRDF pairs).

Restrictions for deleting pairs The DELETE operation fails if any of the following apply:

The device is in one of the following BCV pair states: Synchronized, SyncInProg, Restored, RestoreInProg, SplitInProg, Updated, or UpdateInProg.

There is a background BCV split operation in progress.

Devices are in the back-end Not Ready state.

There are existing local invalid tracks on either the local or remote device.

There are remote invalid tracks and the FORCE flag was not specified.

The links are not suspended.

Deleting half pairs If a delete operation for a SRDF device pair is initiated and the remote array has been replaced, or if the status of an SRDF pair is partitioned a confirmation screen appears.

NOTE: If running in SRDF asynchronous mode and consistency is enabled, the consistency is disabled and then delete half pair is performed.

Setting modes of SRDF operation SRDF modes of operation are SRDF/Synchronous (SYNC), SRDF/Asynchronous (ASYNC), adaptive copy disk mode (ACDM), and Metro.

To set the SRDF mode for a selected image, path:

1. On the Control Menu, select option 4. Set SRDF mode to display the Set SRDF Mode (SETRDFMOD) screen (Figure 62).

Figure 62 Set SRDF Mode (SETRDFMOD) screen

2. Provide the characteristics of the selected image:

Image Name The name of the image to perform a control action on.

Path Name The path name associated with the image on which to perform a control action.

Step Number The step number for which the control action is to be initiated.

100 Controlling SRDF

SRDF Mode Type The mode to use for SRDF operations. The options are:

SYNC enables SRDF/Synchronous mode.

ASYNC enables SRDF/Asynchronous mode.

ACDM enables adaptive copy disk mode.

METRO enables SRDF/Metro mode.

SRDF Metro Mode Specifies whether a SRDF/Metro configuration uses witness or bias protection. Enter A to use witness protection or B to use bias protection.

Set a value for this parameter only when the value of SRDF Mode Type is METRO.

3. Press Enter.

If you set the SRDF mode to METRO, and the protection mode to A (witness protection) you need to:

1. Create a witness group. See Creating dynamic SRDF groups for more information.

2. Suspend the SRDF link. See Splitting or Suspending SRDF links operation for more information.

3. Perform an establish control action on the link. See Establishing SRDF links for more information.

NOTE: For SRDF, do not use ACDM mode while creating the RDF or remote TimeFinder images during split as this is not supported. Instead, for SRDF, use SYNC or ASYNC mode.

You can also use the SETRDFMOD command from the command line. See SETRDFMOD for more information.

Consistency protection in SRDF/A mode In SRDF Asynchronous mode, consistency protection can be enabled or disabled for SRDF/A devices. When consistency protection is enabled, if data cannot be copied from the R1 to the R2, all devices in the group are made Not Ready on the link to preserve the R2 data consistency.

In Asynchronous mode, consistency protection is automatically enabled after the control action Resume or Establish is run. When the control action Split or Suspend is run, consistency protection is disabled and the Split or Suspend operation is performed. If consistency protection is enabled for the devices, consistency protection must be disabled before you attempt to change the mode from Asynchronous.

Enabling consistency protection To enable SRDF/A consistency protection:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the control action ENABLE.

A message appears indicating that the enable consistency protection operation started successfully.

Disabling consistency protection To disable SRDF/A consistency protection:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the control action DISABLE.

A message appears indicating that the disable consistency protection operation started successfully.

Establishing SRDF links To establish SRDF links:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

Controlling SRDF 101

2. Provide the Image Name, Path Name, and Step Number.

3. Select the control action ESTABLISH.

The Confirm Establish SRDF Link screen appears.

4. Type Y to continue.

SRDF/TimeFinder Manager updates SRDF device data and displays a message indicating that the Establish SRDF links processing initiated successfully.

Splitting or Suspending SRDF links operation Both the Split and Suspend operations require I/O to be suspended on the host to create a frozen image.

To suspend I/O on SRDF links so that you can create a frozen image for backup operations, break the SRDF links between source (R1) and target (R2) volumes. Figure 63 shows this operation.

Restricted state and daemon jobs

When using split or suspend the user can select to hold all jobs or bring the system to a restricted state. When selecting the hold jobs option, all jobs in the system are held except for the daemon jobs Storapid and Storgnsd.

Additionally, when selecting the restricted state option the subsystem where Storapid and Storgnsd are running is not ended. Other jobs that are running in that same subsystem are ended using the STMENDSBS command. This command ends all subsystems.

During a split, The STMENDSBS command checks status of the subsystems for the restricted state. The split fails and the user is asked to hold jobs, if either of the following conditions exist:

There are other jobs running in the subsystems where the daemon jobs are running.

There are subsystems running, other than the subsystems where the daemon jobs are running.

Figure 63 Split or Suspend SRDF links operation

The following sections describe the various modes for the Split/Suspend operation.

102 Controlling SRDF

Splitting or Suspending SRDF links: Restricted state This procedure uses the restricted state to ensure that I/O activity is halted before the SRDF link is suspended or split.

Depending on the configuration, the time it takes for a host to go into a restricted state can vary. By default, SRDF/TimeFinder Manager waits 1800 seconds for control to return, after issuing the command to bring the system to a restricted state. If additional time (in seconds) is required to bring the system to a restricted state, use the procedure Setting the restricted state wait time.

For IASP images, see SRDF/TimeFinder Manager Extended Features.

To split/suspend SRDF links in a restricted state:

1. Bring the IBM i host to a restricted state:

a. Prepare for bringing the system to a restricted state, using internal procedures established by your company.

b. On the Control Menu, select option 5. Bring system to a restricted state to display the STM End Subsystem Confirmation screen.

c. Press F10 to bring the IBM i host to a restricted state.

The STM End All Subsystems (STMENDSBS) screen (Figure 64) appears.

Figure 64 STM End All Subsystems (STMENDSBS) screen

d. Select options for How to end and Controlled end delay time, and press Enter.

After the End Subsystem operation completes, the Control Menu appears.

2. Split/suspend SRDF links:

a. From the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

b. Provide the Image Name, Path Name, and Step Number.

c. Select the SPLIT or SUSPEND control action.

d. The EMC SRDF/TimeFinder Control (CTLACT) screen reappears with a Split/Suspend Mode prompt.

e. Enter RESTRICTED for the SPLIT_MODE parameter.

SRDF/TimeFinder Manager checks to see if the system is in a restricted state. If the system is not in a restricted state, SRDF/TimeFinder Manager displays the Confirmation Window screen (Figure 66) asking if you want to hold jobs and job queues.

Controlling SRDF 103

Figure 65 System not in restricted state screen

To continue the operation in HOLD_JOBS mode, see Suspend or Split SRDF links: Hold jobs and job queues and take the appropriate action.

A message screen appears indicating that the Split SRDF links operation started successfully.

SRDF/TimeFinder Manager attempts to perform the SRDF links operation on all ASPs in the image. ASPs that are not eligible for the operation must be removed. See Removing ASPs from an image for more information.

3. Start subsystems:

a. On the Control Menu, select option 6. Start subsystems.

The Start Subsystems command resumes normal IBM i working processes from the IBM host restricted state.

NOTE: The start subsystems command checks to see if the daemon jobs are the only jobs running in their dedicated subsystems. If the system is not in a restricted state, or there are other jobs running besides the daemon jobs, a message appears. This command then brings the system into a true restricted state by ending all subsystems including daemon jobs. When this is complete, the controlling subsystem is started. This should start all the required subsystems and jobs, depending on what jobs are defined as auto start jobs and what is set as a startup program defined in the system value QSTRUP. If you use additional start-up procedures, run them separately. Start Subsystems does not power cycle the IBM i host or restart the OS/400 operating system.

b. Resume normal operations.

Suspend or Split SRDF links: Hold jobs and job queues The following procedure holds jobs and job queues to ensure that I/O activity is halted prior to the Split or Suspend SRDF links operation.

CAUTION: System activity that results in a write operation can continue while jobs and job queues are on hold. For example, a restore job could have write operations continue while it is held. If you are not sure that the hold job and job queues option completely suspend write operations to the selected image, bring the system to a restricted state before running a Split or Suspend operation. Splitting or Suspending SRDF links: Restricted state contains instructions on how to do this.

To split or suspend SRDF links with jobs and job queues on hold:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the SPLIT or SUSPEND control action.

The EMC SRDF/TimeFinder Ctrl (CTLACT) screen reappears with a Split/Suspend mode prompt.

4. Enter HOLD_JOBS for the SPLIT_MODE parameter.

NOTE: The SRDF link status for the image must be in an eligible state.

SRDF/TimeFinder Manager repeatedly attempts to put all jobs and job queues on hold and then executes the Split or Suspend operation.

104 Controlling SRDF

When one or more jobs or job queues remain active, SRDF/TimeFinder Manager displays the Confirmation Window screen (Figure 66).

Figure 66 Confirmation Window screen

5. Select the appropriate option:

1 - Try again to hold Jobs/Queues SRDF/TimeFinder Manager repeatedly attempts to hold all jobs and job queues.

If any job or job queues remain not on hold, the Confirmation screen reappears.

2 - Continue Split/Suspend operation Accept that some jobs remain active and continue with the Split or Suspend operation.

CAUTION: Selecting the Continue Split/Suspend operation acknowledges that some write activity can continue during the Split operation. If any writes occur to the specified ASP during the Split operation, the resulting copy is not valid.

3 - Abort Do not perform the Split or Suspend operation and return to the Control Menu.

5 - Display, what is not on HOLD Show a list of the jobs and job queues that SRDF/TimeFinder Manager cannot hold (Figure 67).

Figure 67 Jobs Not on Hold and Job Queues Not on Hold screens

6. Press F3 or Enter to return to the Confirmation Window screen.

After all jobs and job queues are successfully on hold, or if option 2 - Continue Split/Suspend operation is selected from the Confirmation Window screen, the Suspend or Split operation is performed. A message screen appears indicating that the Split or Suspend SRDF links operation started successfully.

After the Split or Suspend operation is complete, all jobs and job queues held by SRDF/TimeFinder Manager are released.

7. Use the Work with Associated Paths screen or the Disk Units screen to monitor and verify the change in links status.

Controlling SRDF 105

Splitting or Suspending SRDF links: Maintenance mode Performing a Suspend/Split operation in maintenance mode suspends or splits the SRDF links without interfering with the source host operations.

Unless you employ another method of suspending write operations, the Split or Suspend SRDF Links maintenance operation results in an R2 copy that is not usable.

NOTE: If you use an R2 copy in a simple SRDF R1/R2 configuration, perform a Split or Suspend with Restricted state or a Split or Suspend with HOLD_JOBS.

To suspend or split SRDF links in maintenance mode:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the SPLIT or SUSPEND control action.

The EMC SRDF/TimeFinder Ctrl (CTLACT) screen reappears with a Split/Suspend mode prompt.

4. Enter MAINTENANCE for the SPLIT_MODE parameter.

The Split SRDF links or Suspend SRDF links operation performs without interfering with the source host operations.

Resuming SRDF operation SRDF/TimeFinder Manager on the source IBM i host is used to restore SRDF operation by resuming the links between source (R1) and target (R2) volumes.

NOTE: The Resume SRDF links operation cannot be used when the SRDF links status is Split.

CAUTION: Resuming the SRDF links before backup is complete may result in unusable backup tapes or save files. Use the Work with Associated Paths screen or the Disk Units screen to monitor and verify the change in links status.

To resume SRDF links:

1. On the Control Menu, select option 1. SRDF or TimeFinder Control to display the EMC SRDF/TimeFinder Ctrl (CTLACT) screen.

2. Provide the Image Name, Path Name, and Step Number.

3. Select the control action RESUME.

The Confirm Resume Link screen (Figure 68) appears.

Figure 68 Confirm Resume Link screen

NOTE: Make sure that the R2 image is not in use on the target system before resuming the SRDF links. Backup can be performed only while the links are suspended or split (devices are only read/write accessible when they are split). Resuming links while backup is in progress has an unpredictable effect on the backup operation.

4. Type Y.

A message appears indicating that the Resume operation started successfully.

106 Controlling SRDF

Controlling SRDF/Metro This section shows how to set up and manage SRDF/Metro configurations within SRDF/TimeFinder Manager. The SRDF Introduction has information on SRDF/Metro and its capabilities.

Setting up an SRDF/Metro configuration To set up an SRDF/Metro configuration:

1. If the configuration is to use Array witness resilience, create a Witness group between each array in the SRDF/Metro configuration and the Witness array (see Creating dynamic SRDF groups).

2. If the configuration is to use vWitness resilience, create the vWitness instances on both arrays in the SRDF/Metro configuration (see Maintain vWitness information).

3. Create the SRDF groups on both SRDF/Metro arrays to hold the device pairs. See Creating dynamic SRDF groups for more information.

4. Add the device pairs to the SRDF groups specifying them as SRDF/Metro pairs and using witness or bias, as appropriate See Creating pairs for more information.

5. Once all the devices are in a steady state (Active/Active or Active/Bias) present the R2 devices to the IBM System i host using map and mask operations.

NOTE: SRDF/TimeFinder Manager can use only SRDF/Metro configurations created within SRDF/TimeFinder Manager. It cannot use SRDF/Metro configurations created by Solutions Enabler or Unisphere.

Removing an SRDF/Metro configuration To remove an SRDF/Metro configuration:

1. Suspend the SRDF link. See Splitting or Suspending SRDF links operation for more information.

2. Delete the SRDF pair. See Deleting SRDF pairs for more information.

3. (Optional) Delete the SRDF group. See Removing dynamic SRDF groups for more information.

Alternatively, you can keep the group for later reuse.

4. Make the R2 devices inaccessible to the host using unmap and unmask operations.

5. Enable the R2 devices using the ENABLEDEV command for future use. See ENABLEDEV for more information.

Controlling witness and bias settings for SRDF/Metro

Maintain vWitness information

Use the vWitness Control Action screen to maintain vWitness information. There are two ways to access this screen:

Through the Control Menu screen:

From the Control Menu screen, select option 13. Create/Delete vWitness Info to display the vWitness Control Action screen (Figure 69).

The CTLVWIT command from the command prompt:

CTLVWIT

The vWitness Control Action screen appears (Figure 69).

Controlling SRDF 107

Figure 69 vWitness Control Action screen

Provide the following information:

Symmetrix ID Enter the identifier of the storage array.

Witness Name Enter a name for the vWitness definition:

The name has up to 12 characters and starts with an alphabetic character.

The rest of the name can contain alphanumeric characters, underscores and hyphens.

Control Action Enter the required command:

ADD in addition, supply Symmetrix ID, Witness Name, and Location.

REMOVE in addition, supply Symmetrix ID and Witness Name.

ENABLE in addition, supply Symmetrix ID and Witness Name.

DISABLE in addition, supply Symmetrix ID, Witness Name, Use of Force flag (optional), and Use of Sym Force flag (optional).

Location Enter the IP address or fully-qualified DNS name of the system where the vWitness instance is installed.

Use of Force flag This applies only when disabling a vWitness instance. Enter *YES when the instance is in use and there is another witness (virtual or physical) that can take over.

Use of Sym Force flag This applies only when disabling a vWitness instance. Enter *YES when the instance is in use that there is no other witness (physical or virtual) to take over.

To modify a vWitness definition, disable it, remove it, add the new definition and enable that.

NOTE: vWitness instances are defined outside SRDF/TimeFinder Manager. However, add a vWitness definition using the CTLVWIT screen for each of those instances that you want to use in an SRDF/TimeFinder Manager SRDF/Metro configuration. The SRDF/Metro vWitness Configuration Guide shows how to manage vWitness instances.

View vWitness information

Use the Display vWitness Information screen to view vWitness definitions on a storage array. There are two ways to access the screen:

Through the Control Menu screen:

From the Control Menu screen select option 14. Display vWitness Info (Figure 70)

The DSPVWIT command:

DSPVWIT

108 Controlling SRDF

The Display vWitness Information appears (Figure 70)

Figure 70 Display vWitness Information

The screen shows the characteristics of the vWitness definitions that have been defined:

Symmetrix the identifier of the appropriate storage array.

vWitness Name the name of the vWitness definition.

Status the state of the definition.

Port the number of the IP port that the vWitness instance is using.

vWitness location the IP address of the vWitness instance.

Change the bias setting

A SRDF/Metro configuration can use bias to determine which array remains available to the host when there is a failure on the SRDF links. Use the SRDF Metro Set Bias screen (Figure 71) to define which array is on the bias side. Use the SETBIAS command to access this screen:

SETBIAS

Figure 71 SRDF Metro Set Bias screen

Provide the following information:

Symmetrix ID The identity of the storage array that is to become the R2 side.

SRDF Group Number The identity of the SRDF group on the storage array whose bias setting you want to change.

Device File Name The name of the file that contains the identities of devices whose bias setting you want to change.

Controlling SRDF 109

Set Bias which side of the pair is to become the bias side.

Monitoring SRDF operations You can monitor the SRDF operations at the step level on the Work with Associated Paths screen or at the device level through the Disk Units screen. See Viewing devices for more information.

Monitoring invalid and % copied tracks The Disk Unit screen and the Work with Associated Paths screen have a column labeled Invalids/%Copied.

For SRDF or TimeFinder synchronization, this column lists the number of invalid tracks remaining during the synchronization operation. On the Disk Units screen invalid track counts display at the device level, and on the Work with Associated Paths screen invalid track counts display by image.

For TimeFinder/Clone and TimeFinder/SnapVX operations, this column represents the percentage of copied tracks.

NOTE: The invalid tracks information is meaningful only while synchronization is in progress. The invalid track information is not accurate while SRDF links are Suspended or Split.

Recovering from NotConsistent SRDF state SRDF/TimeFinder Manager performs control actions only on images in which all devices are VMAX Family, VMAX All Flash, or PowerMax array devices.

When SRDF device pairs in an image are at different states, such as when one pair is in a Synchronized state and another in a Suspended state, the RDF status for the step of the image becomes NotConsistent. To recover from this situation, using SRDF/TimeFinder Manager, run the Resume SRDF links or Establish SRDF links operation.

The Resume SRDF links or Establish SRDF links control action examines all devices in the image and checks the state of each SRDF device pair that belongs to that image.

If the state is eligible for the Resume SRDF links or Establish SRDF links control action, the operation starts for that SRDF pair. Otherwise, SRDF/TimeFinder Manager issues an error message to the job log providing the device numbers and their status information.

NOTE: Contact the Dell Customer Support for assistance with bringing devices back into an eligible state.

Listing and monitoring SRDF groups On the Control Menu, select option 9. List SRDF groups.

The List of the SRDF Groups screen (Figure 72) appears, and displays the RDF groups for all attached arrays. For SRDF/A mode, this screen lists the number of seconds that the data on the R2 device is behind the data on the R1 device. This screen also appears if the group participates in the STAR configuration.

Figure 72 List of the SRDF Groups screen

110 Controlling SRDF

Displaying SRDF group details To display details for a SRDF group, on the List of SRDF Groups screen type 5 (Display the Group) next to the desired group.

The SRDF Group Information screen (Figure 73) appears showing information about the local group and remote group.

Figure 73 SRDF Group Information screen

The types that can populate the Group Type field are:

/Metro

Witness-Protected

Witness-Configured

Witness

Dynamic (default)

N/A

Performing dynamic SRDF personality swaps SRDF/TimeFinder Manager supports Dynamic SRDF. This section explains how to use SRDF/TimeFinder Manager, after using the Solutions Enabler CLI for personality swaps.

For more information on dynamic SRDF, see the Solutions Enabler SRDF CLI User Guide.

Dynamic personality SRDF (R2R1) swaps for the System image (*SYSBAS) must be performed through the Solutions Enabler CLI. After the swap, launch SRDF/TimeFinder Manager from the target host and use any remote devices (BCV, Clone, and SnapVX) as local devices. However, as Table 5 shows, depending on the step in the path, additional path association may be necessary.

Table 5 Steps in the path and its associated action after personality swap

Source Target Target status after swap Associated action after swap

/BCV1 /RDF1/BCV1

/RDF1/BCV1 /BCV1

Both pairs are associated No action required

/BCV1 /BCV1 NotConfigured No action required

/RDF1/BCV1 Does not exist Need to associate

/RDF1/BCV1 /RDF1/BCV1 NotConfigured No action required

/BCV1 Does not exist Need to associate

Controlling SRDF 111

Automating SRDF operations SRDF/TimeFinder Manager provides the option of incorporating SRDF control operations in your customized CL programs. The CL command, CTLACT, includes the following SRDF control options:

SRDF control actions:

ESTABLISH Establishes SRDF links for SRDF control.

RESUME Resumes SRDF links for SRDF control.

SUSPEND Suspends SRDF links for SRDF control.

SPLIT Splits SRDF links for SRDF control.

SPLIT_MODE(RESTRICTED) Splits/suspends SRDF links for SRDF control while the system is in a restricted state.

SPLIT_MODE(HOLD_JOBS) Holds all jobs and job queues before performing a Split or Suspend control operation.

SPLIT_MODE(MAINTENANCE) Splits/suspends SRDF links for SRDF control in maintenance mode (that is, no interference with host operations).

STATUS Provides SRDF control status information.

SRDF/Asynchronous control actions:

ENABLE Enables the consistency protection for SRDF/A devices.

DISABLE Disables the consistency protection for SRDF/A devices.

NOTE: Standard Features Commands Reference contains detailed command reference information.

Standard Features Commands Reference 113

A

Standard Features Commands Reference visible Body Tagefernce

This appendix provides reference information, syntax, and examples for control commands.

Topics:

Conventions CRTDLTRDFP CRTNETCNFG CTLACT CTLRDFGRP CTLVWIT DISCOVER DISCOVERC DSPVWIT ENABLEDEV ENDSTMSRV RELDEVLCK RELDEVLCKC RTVSTMINF SETBIAS SETRDFGRP SETRDFMOD STMENDSBS STMRMTCMD STMSTRSBS STORDAEMON STRSTMSRV

Conventions The descriptions of the commands in this appendix can contain the following sections:

Syntax Presents the syntax of the command. Variables that you specify are shown in italics. The optional parameters are indicated by brackets.

Description Describes the purpose and result of the command.

Required parameters Describes parameters that must be specified at the command line. Each description contains all possible values of the variable and states which, if any, of the values is the default. Variables that you must specify are shown in italics.

Optional parameters Describes parameters that can be included at the command line. Each description contains all possible values of the variable and states which, if any, of the values is the default. Variables that you can specify are shown in brackets.

Usage notes Presents specific points that you should keep in mind when using the command.

Examples Presents one or more examples of the command.

CRTDLTRDFP Creates or deletes SRDF pairs while the array is in operation.

114 Standard Features Commands Reference

Syntax

CRTDLTRDFP ACTION(CREATE|DELETE)

SYMID(sym_id)

GRPNUM(group_number)

FILENAME(device_file_name)

METROPAIR (*YES|*NO)

METROMODE (A|B)

[RDF_MODE(rdf_mode)]

[RDF_FLAG(ESTABLISH|INVALIDATER2)]

[RDF_TYPE(R1|R2)]

[FORCE_FLAG(*YES|*NO)]

Description

Creates or deletes SRDF pairs while the array is in operation. All devices running on arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 are reported as dynamic RDF-capable.

Required parameters

SYMID(sym_id)

The Symmetrix ID specified in this field is associated with the devices listed in the first column of the device file.

GRPNUM(group_number)

SRDF group Number. The group number specified in this field is associated with the devices listed in the first column of the device file. The group number size can be four digits.

FILENAME(device_file_name)

Name of the file that lists the designated device pairs.

ACTION(control_action)

Specifies the control operation to perform:

CREATE SRDF pairs become members of the specified RDF group. Pairing information is added to the SYMAPI database file on the host.

DELETE SRDF pairs are canceled and pairing information is removed from the array and the SYMAPI database. Devices are changed to non-SRDF devices (except for concurrent SRDF pairs).

METROPAIR(*YES|*NO)

Indicates whether the pair are in a SRDF/Metro configuration.

METROMODE(A|B)

Specifies the form of protection that a SRDF/Metro pair uses:

A The pair uses witness protection.

B The pair uses bias protection.

Include this parameter only when the value of METROPAIR is *YES.

Standard Features Commands Reference 115

Optional parameters

RDF_MODE(rdf_mode)

Sets device pair SRDF mode:

SYNC Synchronous (default)

ASYNC Asynchronous

ACDM Adaptive copy disk mode

METRO enables SRDF/METRO mode.

RDF_FLAG(ESTABLISH|INVALIDATER2)

Sets RDF copying options as follows:

ESTABLISH (default option) Once the SRDF pairs are created, begins copying data to the invalidated targets, synchronizing the dynamic SRDF pairs that are listed in the device file.

INVALIDATER2 Once the SRDF pairs are created, marks the R2 devices that are listed in the device file as the invalidated target for a full device copy.

RDF_TYPE(R1|R2)

Indicates whether the device in the first column of the device file is an R1 or an R2 device. R1 is the default.

FORCE_FLAG(*YES|*NO)

Indicates whether to use or not use the force flag during DELETE operation. *NO is the default.

CRTNETCNFG Creates the NETCNFG file and adds network services to the file.

Syntax

CRTNETCNFG NODENAME(node_name)

NETWADDR(ip_address)

SECLVL(DEFAULT|ANY|NONSECURE|SECURE)

PORTNBR(port_number)

Description

CRTNETCNFG creates the NETCNFG file in the /var/symapi/config directory and adds network services to the file. Specify either the node name or the IP address of the remote SYMAPI server. You cannot omit both of these parameters. In addition, the security level of the connection type is mandatory.

Required parameters

NODENAME(node_name)

The name of the remote SYMAPI server. NODENAME is required if the NETWADDR parameter has not been specified.

NOTE: When using a node name, make sure the node name is also entered into the host table of the system or is listed in the DNS tables of the attached network.

NETWADDR(ip_address)

The IP address of the remote SYMAPI server. NETWADDR is required if the NODENAME parameter has not been specified.

116 Standard Features Commands Reference

SECLVL(DEFAULT|ANY|NONSECURE|SECURE)

The security level for the connection type that the SYMAPI server is expecting to negotiate:

DEFAULT The SYMAPI client and server are initially configured to negotiate either secure or non-secure sessions. This is the default.

ANY Indicates that either secure or non-secure sessions are negotiated between the client and the server if the SSL (secure socket layer) capabilities do not agree and between supported and unsupported platforms.

NONSECURE Indicates that only non-secure sessions are negotiated between the client and the server. This level is intended as the last resort in situations where SSL cannot be used for some reason or is undesirable. NONSECURE can be useful in matters of performance and availability.

SECURE Indicates that only secure sessions are negotiated between the open host and the server. This level is intended in situations where SSL desirable.

NOTE: The SECURE option is not supported on the IBM i hosts.

PORTNBR(port_number)

The TCP/IP port number for the remote SYMAPI server.

The default value is 2707.

CTLACT Processes SRDF and TimeFinder control actions for one or all images (SYSTEM and IASP).

CAUTION: Do not use the CTLACT command with IASP images, except for initial IASP configuration. Instead, use the options on the Work with Associated Paths screen or the IASPCTL command. Using either these ensures that SRDF/TimeFinder Manager does rigorous error checking before executing the control actions against the IASPs. For more information, see IASPCTL.

Syntax

CTLACT IMAGE_NAME(image_name|*ALL)

PATH_NAME(path_name)

STEPNUM(step_number)

ACTION(control_action)

[SPLIT_MODE(RESTRICTED|HOLD_JOBS|SPLITWA|MAINTENANCE)]

[PROT_ESTAB(*YES|*NO)]

[SVX_MODE(CONSISTENT|HOLD_JOBS| RESTRICTED)]

[LINK_MODE(NOCOPY|COPY)]

[TTL_DAYS(1-400)]

[TTL_DATE(Date)]

Description

CTLACT processes the control action specified in the ACTION parameter for the IMAGE parameter, PATH parameter, and the STEPNUM parameter. If the specified control action is directed to any of the Suspended/Split SRDF links, Split BCV pairs, or Clone copy session, use the SPLIT_MODE parameter to specify which method to use to stop writes to the devices in the image.

If SnapVX Establish control action is specified, use the SVX_MODE parameter to specify which method to use when stopping writes to the devices in the image.

You can use CTLACT to control multiple images as long as all images use the same path and step number.

Standard Features Commands Reference 117

Required parameters

IMAGE_NAME(image_name|*ALL)

The name of the image (image_name) or *ALL to indicated all images.

PATH_NAME(path_name)

The path name associated with the image to be used in an SRDF or TimeFinder control operation.

STEPNUM(step_number)

The specific step number for which the control action is initiated in an SRDF or TimeFinder control operation.

Steps in the path are defined during configuration and are identified by their position (1 through 5) in the path.

ACTION(control_action)

Specifies which control operation to perform:

STATUS Provides SRDF, Clone, Clone emulation, BCV, or SnapVX control status information for the step in the associated path of the image. For SnapVX, if a snapshot name and generation are specified, the state of the specified snapshot is provided.

NOTE: If the status of the SnapVX step is Linked, CopyInProg, Copied, Restored, RestoreInProg, RestNotPaired, or RestgNotPaired an additional message is provided with the snapshot name and generation.

ESTABLISH Establishes SRDF links for SRDF control or establishes/re-establishes BCV or Clone emulation pairs for BCV control. When running in SRDF/A mode, consistency protection is automatically enabled after executing an ESTABLISH operation is executed.

SPLIT Splits SRDF links for SRDF control or splits BCV or Clone emulation pairs for TimeFinder control. When the system is running in SRDF/A mode and a SPLIT is executed, consistency protection is disabled and then the SPLIT operation is performed.

NOTE: For TimeFinder/Clone configurations, if the devices are in Restored state, use the SPLIT option to change the direction of the clone relationship (that is, the original source device becomes the source device for a future copy), which allows the use of the RECREATE command and normal processing continues.

RESUME Resumes SRDF links for SRDF control. When the system is running in SRDF/A mode, consistency protection is automatically enabled after a RESUME operation is executed.

SUSPEND Suspends SRDF links for SRDF control. When the system is running in SRDF/A mode and a SUSPEND is executed, the consistency protection is disabled and then the SUSPEND operation is performed.

ENABLE Enables the consistency protection for SRDF/A backed devices when running in SRDF/A mode. If data cannot be copied from the R1 to the R2, all devices in the group become Not Ready on the link to preserve the R2 data consistency.

NOTE: If devices are enabled for consistency group protection, the devices must be disabled before you can change the mode to Synchronous or initiate the SPLIT/SUSPEND operation.

DISABLE Disables the consistency protection for SRDF/A backed devices when running in SRDF asynchronous mode.

CREATE Creates or recreates a Clone copy session with devices in the image. For TimeFinder/Clone the state of the device pair is PreCopy. When the Create operation completes, the state changes to Created.

You must run CREATE before you activate the session, which has a shorter duration than an Establish operation.

ACTIVATE Activates a Clone copy session with the devices in the image. For TimeFinder/Clone, while the operation is in progress the state of the device pair is CopyInProg. Once the copy is complete, the state changes to Copied.

NOTE: The point-in-time copy becomes available after an ACTIVATE operation. Create must be done before you can activate a Clone copy session.

LINK Copies the SnapVX point-in-time data to the target device.

There are two types of links, NOCOPY (the default) or COPY. NOCOPY links do not retain point-in-time data once the link is removed and any previous target data is lost. Copy mode must be used in order for the linked target to retain data after the link is removed. When linking a snapshot, COPY or NOCOPY must be specified.

RELINK Removes the current SnapVX link to target devices and presents a different snapshot. The relink may also be used to relink to the same snapshot. This has the effect of refreshing the point-in-time copy on the link target if it has been modified by host writes.

118 Standard Features Commands Reference

UNLINK - Removes the current SnapVX link to target device(s).

RESTORE For SnapVX , copies the point-in-time data from a snapshot back to the original source device. The snapshot must be fully established to perform a restore. Restore action is not allowed for the first step for a System Image.

RENAME Changes the SnapVX snapshot name. Renames on the specified generation. If generation is not specified, then generation 0 is renamed.

SET TTL Sets a time to live for a SnapVX snapshot, from when TTL is set, in days or a date. The value in days can be set to any value between 1 and 400. The date value is a specified date up to 400 days in the future, from which a value in days is created, based on the difference between the specified absolute time and the host time when the action is performed. When the TTL expires the snapshot automatically terminates unless there are one or more links. Automatic termination takes place when the links are removed. If TTL is not set, the snapshot remains established until it is manually terminated.

SETCOPY - Changes the copy mode of a link to copy. Data is physically copied to the target devices. When the link is terminated the data is retained on the target.

NOTE: SnapVX no longer supports SETCOPY when running on PowerMaxOS 10 (6079) using STM IBM i version 10.0. This is still supported when running on a lower PowerMaxOS versions using STM IBM i version 10.0.

SETNOCOPY - Changes the copy mode of a link to NoCopy. Data is presented on the target devices, but not physically copied. When the link is terminated the data is not retained on the target.

NOTE: SnapVX no longer supports SETNOCOPY when running on PowerMaxOS 10 (6079) using STM IBM i version 10.0. This is still supported when running on a lower PowerMaxOS versions using STM IBM i version 10.0.

TERMINATE Stops the existing Clone copy session between the specified source and target devices in the image.

For SnapVX snapshot sessions, TERMINATE removes the snapshot. All links must be unlinked before terminating a snapshot.

NOTE: If a snapshot has restores, only the restored session is terminated.

CANCEL Cancels the existing internal session between the specified standard device and the BCV devices in the image.

Once the session is canceled, the corresponding BCV devices are placed in a SplitNoInc state, and the BCV pair can no longer be incrementally established or restored.

Run Cancel before you run an unpairing operation on Clone Enabled BCV devices. Not running Cancel causes hanging Clone sessions to remain on the array.

Restrictions for cascaded sessions:

Cascading from TimeFinder Clone emulation is not supported.

SPLIT_MODE(RESTRICTED|HOLD_JOBS|SPLITWA|MAINTENANCE)

The mode to use for a Suspend, Split, or Activate operation:

RESTRICTED Executes the operation when the system is in a restricted state. This is the default. System must be put in restricted state by using option 5 from the Control menu using Bring System to a Restricted State, or by using the STMENDSBS command. This ensures that all subsystems and jobs are ended except for the daemon jobs and their corresponding subsystems.

HOLD_JOBS Executes the operation after holding all jobs and job queues.

SPLITWA Executes the operation after holding I/Os on the array. Splits a local or remote BCV, Clone, Clone emulation, or Snap image while the source system is operational. The resulting image is consistent and holds data upon the last commit.

With TimeFinder/CG (SPLITWA) operations, you do not have to put the IBM i host in a restricted state or perform a hold jobs operation.

The SRDF/TimeFinder Manager client and the controlling host must have a gatekeeper configured on each locally attached array. For detailed information on array gatekeeper management, see the Solutions Enabler Installation and Configuration Guide.

On the client, the netcnfg file must be configured using the CRTNETCNFG command. This ensures that correct information, such as the node name, IP address, port, and security level points to the remote server. Only non-secure connections are supported for IBM i.

MAINTENANCE Splits or Suspends SRDF links, splits BCV pairs or activates a virtual copy session or Clone copy session in maintenance mode. That is, no interference with host operations.

Standard Features Commands Reference 119

PROT_ESTAB(*YES|*NO)

Performs a Protected or normal BCV Establish operation:

*YES Establish two mirrors of a BCV device to the standard device. When the split occurs, both mirrors are split simultaneously. This operation moves all mirrors of the locally mirrored BCV devices to join the mirrors of a standard device

*NO Perform a normal Establish operation for the BCV device. This is the default.

SVX_MODE(CONSISTENT|HOLD_JOBS| RESTRICTED)

The mode to use for the SnapVX Establish operation:

CONSISTENT Executes the operation in Consistent mode. That is, no interference with the host operations. This is the default.

CAUTION: Use caution when performing this Consistent Establish mode, as the data in main memory is not included in the image. Use this mode when the host and applications are in a quiescent state. If that is unacceptable to your business needs, use other operating system functions such as journaling and database commitment control to get an image current with the last transaction.

HOLD_JOBS Executes the operation after holding all jobs and job queues.

RESTRICTED Executes the operation when the system is in a restricted state. Put the system restricted state by using option 5 from the Control Menu using Bring System to a Restricted State, or by using the STMENDSBS command. This ensures that all subsystems and jobs are ended except for the daemon jobs and their corresponding subsystems.

SNAPVXNAME

The name of the Snapshot.

By default, IBM i commands convert names to the upper case. Put the name in quotes if you want it to be in the lower or mixed case.

NOTE: For ESTABLISH action SNAPVXNAME specifies the name for new snapshots. For all other control actions SNAPVXNAME specifies the name of the existing snapshots to be operated on. This parameter is required for all SnapVX control actions except STATUS where it is optional.

SNAPVXGEN

The Generation of the Snapshot. For all SnapVX control actions, except ESTABLISH, specifies the generation of the existing snapshots to be operated on. If set to zero, the most recent snapshot is used for the control action.

SNAPVXTTL

For ESTABLISH and SET_TTL SnapVX controls specifies a Time to Live:

DAYS -Specifies the time to live in days.

DATE - Specifies a date for the snapshot time to live.

If you do not specify a value, the Time to Live is unlimited and the Snapshot is kept until manually terminated.

N_SNPSHOT

The new name of the Snapshot. Used only for RENAME operations. By default, IBM i commands convert names to the upper case. If you want the name to be in the lower or mixed case, put the name in quotes.

LINK_MODE(NOCOPY|COPY)

The mode used for a LINK/RELINK SnapVX operation. Options are as follows:

NOCOPY The target does not retain point-in-time data once the link is removed, and any previous target data is lost. This is the default.

COPY Data is physically copied to the target devices. When the link is terminated the data is retained on the target.

TTL_DAYS

Time to Live in days. The value in days can be set to any value between 1 and 400.

TTL_DATE

120 Standard Features Commands Reference

Specifies a date for the snapshot time to live in the form MM/DD/YYYY (month/day/year) with reference to the host time. The specified date may be up to 400 days in the future.

Standard Features Commands Reference 121

Examples

TimeFinder

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LOCALBCV) STEPNUM(1) ACTION(STATUS) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LOCALBCV) STEPNUM(1) ACTION(ESTABLISH) PROT_ESTAB(*NO) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LOCALBCV) STEPNUM(1) ACTION(SPLIT) SPLIT_MODE(RESTRICTED) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LOCALBCV) STEPNUM(1) ACTION(SPLIT) SPLIT_MODE(SPLITWA)

TimeFinder/SnapVX -Action Establish with TTL days and date

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(ESTABLISH) SNAPVXNAME(END_OF_YEAR) SNAPVXTTL(DATE) TTL_DATE('02/15/2014')

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(ESTABLISH) SNAPVXNAME(END_OF_YEAR) SNAPVXTTL(DAYS) TTL_DAYS(25)

TimeFinder/SnapVX - Action Link

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(LINK) SNAPVXNAME(END_OF_YEAR) SNAPVXGEN(1))LINK_MODE(COPY)

TimeFinder/SnapVX - Action Set TTL days and date

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(SET_TTL) SNAPVXNAME(END_OF_YEAR) SNAPVXGEN(2) SNAPVXTTL(DAYS) TTL_DAYS(25)

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(SET_TTL) SNAPVXNAME(END_OF_YEAR) SNAPVXGEN(2) SNAPVXTTL(DATE) TTL_DATE('02/15/2014')

TimeFinder/SnapVX - Action Rename

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(RENAME) SNAPVXNAME('End_of_Quarter') SNAPVXGEN(1) N_SNPSHOT('End_of_Last_Quarter')

TimeFinder/SnapVX - Action Unlink

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(UNLINK)

TimeFinder/SnapVX - Action Terminate

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(TERMINATE) SNAPVXNAME('End_of_Quarter') SNAPVXGEN(2)

TimeFinder/SnapVX - Action Status for snapshot

122 Standard Features Commands Reference

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(STATUS) SNAPVXNAME(END_OF_YEAR) SNAPVXGEN(2)

TimeFinder/SnapVX - Action Status for step

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(LSNAPVX1) STEPNUM(1) ACTION(STATUS)

SRDF/S

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDF) STEPNUM(1) ACTION(STATUS) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDF) STEPNUM(1) ACTION(RESUME) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDF) STEPNUM(1) ACTION(SUSPEND) SPLIT_MODE(HOLD_JOBS) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDF) STEPNUM(1) ACTION(ESTABLISH) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDF) STEPNUM(1) ACTION(SPLIT) SPLIT_MODE(MAINTENANCE)

SRDF/A

CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDFA) STEPNUM(1) ACTION(ENABLE) CTLACT IMAGE_NAME(SYSTEM) PATH_NAME(SRDFA) STEPNUM(1) ACTION(DISABLE)

CTLMASK Creates and deletes masking views.

Syntax

CTLMASK SYMID(sym_id)

VIEWNAME(mask_view_name)

CTLACT(control_action)

STORAGEGRP(storage_group)

INITGRP(initiator_group)

PORTGRP(port_group)

Description

Creates masking views from pre-existing storage groups, initiator groups, and port groups. Also deletes previously created masking views.

Required parameters

SYMID(sym_id)

The name of the array on which to perform this command.

NOTE: If the array ID is known, enter its name. If the array ID is not known, press F4 to display a list of all local and remote arrays attached to the host.

VIEWNAME(mask_view_name)

Standard Features Commands Reference 123

The name of the masking view to create or delete.

CTLACT(control_action)

Specifies the control action to perform on the view:

CREATE creates a new masking view.

DELETE deletes an existing masking view.

STORAGEGRP (storage_group)

The name of the storage group to include in the new masking view.

INITGRP(initiator_group)

The name of the initiator group to include in the new masking view.

PORTGRP(port_group)

The name of the port group to include in the new masking view.

Usage notes

Include the STORAGEGRP, INITGRP, and PORTGRP parameters only when the control action is CREATE.

The storage group, initiator group, and port group must already exist to be able to create a new masking view.

Examples

Create

CTLMASK SYMID(000111222333) VIEWNAME(NEWVIEW) CTLACT(CREATE) STORAGEGRP(STGROUPA) INITGRP(INITGROUPB) PORTGRP(PORTGROUPC)

Delete

CTLMASK SYMID(000111222333) VIEWNAME(NEWVIEW) CTLACT(DELETE)

CTLRDFGRP The CTLRDFGRP command controls the dynamic RDF group.

Syntax

CTLRDFGRP ACTION (control_action)

SYMID(sym_id)

[METROWIT(*YES|*NO)]

[GRPLABEL (group_label)]

[GRPNUM (group_nmber)]

[MODIFY_ACT (modify_action)]

[SYM_FORCE(*YES|*NO)]

124 Standard Features Commands Reference

[DIRPORT((Dir1(Port1 Port2 )[(Dir2 (Port.)])

[RSYMID(sym_id)]

[RGRPNUM (group_nmber)]

[RDIRPORT((Dir1(Port1 Port2 )[(Dir2 (Port.)])

[AUTO_LINK(*YES|*NO)]

[RAUTOLINK(*YES|*NO)]

[LINK_LIMBO (0-120)]

[RLINKLIMBO (0-120)]

Required Parameters

ACTION(control action)

Specifies the control action to perform:

ADD Creates a new dynamic SRDF group.

MODIFY Modifies an existing dynamic SRDF group

NOTE: This action enables the local and remote director/port to be associated/dissociated with the RDF Group.

REMOVE Removes a dynamic SRDF group.

NOTE: You can remove (delete) an empty RDF group only.

SYMID(sym_id)

The name of the array on which this command is performed. If the array ID is known it can be entered. Otherwise, press F4 key to display a list of all local and remote arrays attached to the host.

Optional Parameters

METROWIT(*YES|*NO)

Indicates whether this group is a SRDF/Metro witness group. The default value is *NO.

There can be only one witness group between two arrays.

GRPLABEL(group_label)

Specifies a label for the dynamic SRDF group. By default, IBM i commands converts names to the upper case. Put the label in quotes if you want it to be in the lower or mixed case.

GRPNUM(group_number)

Specifies the SRDF (RA) group number. The group number size can be four digits.

NOTE: If using the ADD control action, specify both the group label and the group number. Otherwise, specify only one of the parameters.

MODIFY_ACT(modify_action)

Specifies which control action to perform. Options are as follows:

ADD Adds supporting SRDF directors to a dynamic SRDF group.

REMOVE Removes supporting RDF directors from a dynamic SRDF group.

SYM_FORCE(*YES|*NO)

Indicates whether to use the array force operation when normally it is rejected. This option is used only with REMOVE action. Removes one side of a dynamic SRDF group if the other side is not defined or is not accessible.

*YES Enables Sym Force.

Standard Features Commands Reference 125

*NO Disables Sym Force. This is the default.

NOTE: To enable SYM_FORCE, the parameter SYMAPI_ALLOW_RDF_SYMFORCE in the options file must be set to ENABLED.

CAUTION: Use care when applying SYM_FORCE, as data could be lost or corrupted. Use of this option is not recommended, except in extreme cases.

DIRPORT((Dir1(Port1 Port2 )[(Dir2 (Port.)])

Specifies local director/port combination. This option is used with the ADD and MODIFY control actions:

Director ID (Dir 1, Dir 2...) This is the list of the local array directors, such as, 1a, 1b, and so on.

Port Number (Port 1, Port 2...) This is the list of local array director ports.

NOTE: For PowerMaxOS 10 (6079) and PowerMaxOS 5978 the RDF director supports up to 32 ports.

The SYMCLI command symcfg can be used to display all available local director/port combinations. For example:

Addlible emcctl CALL PGM(SYMCFG) PARM('list' '-ra' 'all' '-sid' '000111222333')

RSYMID(sym_id)

The name of the remote array for adding new SRDF group. This option is used only with the ADD control action. If the array ID is known, the name could be entered. If the array ID is not known, press F4 to display a list of all local and remote arrays attached to the host.

RGRPNUM (group_nmber)

Specifies the SRDF group number for the remote array. This option is used only with the ADD control action.

RDIRPORT((Dir1(Port1 Port2 )[(Dir2 (Port.)])

Specifies remote director/port combination. This option is used with the ADD and MODIFY control actions. Options are:

Director ID (Dir 1, Dir 2...) This is the list of the remote array directors, such as, 1a, 1b and so on.

Port Number (Port 1, Port 2...) This is the list of remote array director ports.

NOTE: For PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 the RDF director supports up to 32 ports.

You can use the SYMCLI command symcfg to display all available remote director/port combinations. For example:

Addlible emcctl CALL PGM(SYMCFG) PARM('list' '-ra' 'all' '-sid' '000123456789')

AUTO_LINK(*YES|*NO)

Specifies whether to use the auto link recovery feature locally. This option is used only with ADD action.

*YES Enables local Auto Link Recovery. This is the default.

*NO Disables local Auto Link Recovery.

RAUTOLINK(*YES|*NO)

Specifies whether to use the auto link recovery feature remotely. This option is used only with ADD action.

*YES Enables remote Auto Link Recovery. This is the default.

*NO Disables remote Auto Link Recovery.

126 Standard Features Commands Reference

LINK_LIMBO (0-120)

NOTE: The option should only be used by experienced SRDF users.

Specifies the local link limbo value which is the length of time to wait, from the point of a link-down detection, prior to updating the link status as Down. If the link status is still sensed as Not Ready after the link limbo time expires, devices are marked Not Ready to the link. The link limbo range is zero to 120 seconds. The default time is 10 seconds. This option is used only with the ADD control action.

RLINK_LIMBO (0-120)

Specifies the remote link limbo value which is the length of time to wait, from the point of a link-down detection, prior to updating the link status as Down. If the link status is still sensed as Not Ready after the link limbo time expires, devices are marked Not Ready to the link. The link limbo range is 0-120 seconds. The default time is 10 seconds. This option is used only with the ADD control action.

Standard Features Commands Reference 127

Examples

Create new SRDF groups on local and remote arrays

CTLRDFGRP ACTION(ADD) SYMID(000111222333) GRPLABEL(GRP_20_21) GRPNUM(20) DIRPORT((7H (10 11)) (8H (8 9 10 11))) RSYMID(000222333444) RGRPNUM(21) RDIRPORT((8H (8 9)))

CTLRDFGRP ACTION(ADD) SYMID(000111222333) GRPLABEL(GRP_22_23) GRPNUM(22) DIRPORT((7H (10)) (8H (11))) RSYMID(000222333444) RGRPNUM(23) RDIRPORT((8H (8 9)))AUTO_LINK(*NO) R_AUTOLINK(*NO) LINK_LIMBO(20) RLINKLIMBO(20)

Modify SRDF groups

CTLRDFGRP ACTION(MODIFY) SYMID(000111222333) GRPNUM(20) MODIFY_ACT(ADD) DIRPORT((2F (10))) RDIRPORT((8F (10)))

CTLRDFGRP ACTION(MODIFY) SYMID(000111222333) GRPNUM(20) MODIFY_ACT(REMOVE) DIRPORT((8H (10 11)))

Remove SRDF groups from the Local array

CTLRDFGRP ACTION(REMOVE) SYMID(000111222333) GRPNUM(20)

Remove SRDF groups from the Remote array

CTLRDFGRP ACTION(REMOVE) SYMID(000222333444) GRPNUM(23)

Create a SRDF/Metro witness group

CTLRDFGRP ACTION(ADD) SYMID(000111222333) GRPLABEL(RKS_W) METROWIT(*YES) GRPNUM(4) DIRPORT((2F (27))) RSYMID(000222333444) RGRPNUM(18) RDIRPORT((7H (0)))

Create a SRDF/Metro group that uses bias

CTLRDFGRP ACTION(ADD) SYMID(000111222333) GRPLABEL(R1_B) GRPNUM(36) DIRPORT((2F (27))) RSYMID(000222333444) RGRPNUM(43) RDIRPORT((1G (26))) METROWIT(*NO)

CTLVWIT Manages SRDF/Metro vWitness definitions on a storage array. You can create, enable, disable, and remove definitions.

Syntax

CTLVWIT SYMID(sym_id)

WITNAME(witness_name)

ACTION(control_action)

128 Standard Features Commands Reference

[LOCATION(address)]

[FORCE_FLAG(*YES|*NO)]

[SYM_FORCE(*YES|*NO)]

Description

Manages the definitions of vWitness instances on a storage array. You can add a definition, enable a definition, disable a definition, and remove a definition.

Required parameters

SYMID(sym_id)

The name of the array on which this command is performed. If the array ID is known it can be entered. Otherwise, press F4 key to display a list of all local and remote arrays attached to the host.

WITNAME(witness_name)

A name for the vWitness definition. The name has up to 12 characters. The first character must be a letter; each of the remaining characters is a letter, digit, hyphen or underscore.

ACTION(control_action)

Specifies the control action to perform:

ADD Create a vWitness definition on the specified storage array.

ENABLE Make a previous disabled definition available for use once more.

DISABLE Suspend a definition from being used in a vWitness configuration.

REMOVE Remove a vWitness definition.

LOCATION (address)

The address of the vWitness instance that this definition references. Specify the instances IP address or its DNS name.

Optional parameters

FORCE_FLAG(*YES|*NO)

Use this option with the REMOVE control action only. Use a value of *YES if the selected vWitness instance is in use and there is another witness (physical or virtual) that can take over.

SYM_FORCE(YES|NO)

Use this parameter with the REMOVE control action only. Use a value of *YES when the selected vWitness instance is in use and there is no other witness (physical or virtual) to take over.

Standard Features Commands Reference 129

Examples

Create a vWitness definition on the storage array 000111222333

CTLVWIT SYMID(000111222333) WITNAME(TESTVWIT) ACTION(ADD) LOCATION(10.243.148.127)

Suspend (disable) the use of a vWitness definition

CTLVWIT SYMID(000111222333) WITNAME(TESTVWIT) ACTION(DISABLE) FORCE_FLAG(*NO) SYM_FORCE(*NO)

Enable the use of a previously suspended vWitness definition

CTLVWIT SYMID(000111222333) WITNAME(TESTVWIT) ACTION(ENABLE)

Remove a previously suspended vWitness definition

CTLVWIT SYMID(000111222333) WITNAME(TESTVWIT) ACTION(REMOVE)

DISCOVER Discovers new devices, removes old device information from the SYMAPI database, and updates the database with new information. This command also updates information in the IMAGE file.

Syntax

DISCOVER MODE(*NO|*YES)

CHECK(*NO|*YES)

Description

DISCOVER performs the discover process that is required when the configuration on the host or array changes. By default, information about all arrays visible at one time from this host remains in SYMAPI database until explicitly removed.

Required parameters

MODE(*NO|*YES)

*NO Do not remove old data from the SYMAPI database. This is the default value.

*YES Remove previously discovered array information from the SYMAPI database that is no longer valid (visible).

CHECK(*NO|*YES)

*NO Do not verify information stored in the IMAGE file with the current device information of the host or remove any old device information from the files. This is the default value.

*YES Verify the device information stored in the IMAGE file with the current device information of the host and remove any old device information from the files.

130 Standard Features Commands Reference

CAUTION: Do not run this command with mode *YES when the RDF link is down. Doing so can remove relevant R2 information, such as remote BCV pairing for the array, from the SYMAPI database. If this information is removed, it requires additional repair or reconfiguration to restore the array data. See Running the DISCOVER command for more information.

DISCOVERC Discovers new devices, removes old device information from the SYMAPI database, and updates the database with new information.

Syntax

DISCOVERC MODE(*NO|*YES)

Description

DISCOVERC performs the discover process on the target side that is required when the configuration on the host or array changes. By default, information about all arrays visible at some point from this host remains in SYMAPI database until explicitly removed.

Required parameters

MODE(*NO|*YES)

*NO Do not remove old data from the SYMAPI database. This is the default value.

*YES Remove previously discovered array information from the SYMAPI database that is no longer valid (visible).

CAUTION: Do not run this command with MODE *YES when the RDF link is down. Doing so can remove relevant R2 information. See Running the DISCOVER command for more information.

DSPVWIT Displays information on vWitness definitions.

Syntax

DSPVWIT

Description

Displays all the vWitness definitions defined in a SRDF/Metro configuration.

ENABLEDEV Enables devices following a delete pair operation.

NOTE: Always make the R2 devices inaccessible to the host using unmap and unmask operations before issuing ENABLEDEV. Otherwise, data loss may ocur.

Syntax

ENABLE DEV SYMID(sym_id)

Standard Features Commands Reference 131

FILENAME(file_name)

RDFTYPE (rdf_type)

SYM_FORCE(*YES|*NO)

Description

Following a delete pair operation, devices may be in the Not Ready state. ENABLEDEV makes those devices available once again.

Required parameters

SYMID(sym_id)

The name of the array on which this command is performed. Enter the array ID, if you know it. Otherwise, press F4 key to display a list of all local and remote arrays attached to the host.

FILENAME(file_name)

The name of the device file to use with the ENABLEDEV command. The file lists the devices to enable.

When creating the file, the following rules apply:

The file is a record file and the maximum record length is 40 characters.

The file contains a single column that lists the source devices.

List each device on a separate line.

Lines that begin with the pound sign (#) are comments.

The device file resides in the library list.

Example device file:

# Devices for ENABLEDEV command 009A 009E 009F

RDFTYPE(rdf_type)

The type of SRDF identity that the devices are to assume. The available values for this parameter are:

R1

R2

NOTE: Do not present re-enabled R2 devices to the source (R1) host system as unexpected results, including data loss, can occur.

SYM_FORCE(*YES|*NO)

Indicates whether to use the array force operation when normally it is rejected.

*YES Enables Sym Force.

*NO Disables Sym Force. This is the default.

NOTE: To enable SYM_FORCE, set the value of the SYMAPI_ALLOW_RDF_SYMFORCE parameter in the options file to ENABLED.

CAUTION: Use care when applying SYM_FORCE, as data could be lost or corrupted. Use of this option is not recommended, except in extreme cases.

132 Standard Features Commands Reference

Example

ENABLEDEV SYMID(000111222333) FILENAME(TESTFILE) RDFTYPE(R2) SYM_FORCE(*YES)

ENDSTMSRV Shuts down the SRDF/TimeFinder Manager server job.

Syntax

ENDSTMSRV PORTNUM(port_number)

Description

ENDSTMSRV ends the SRDF/TimeFinder Manager server job session on the node where this command executes. If you do not include the port number, the command uses a default of 8000.

Required parameter

PORTNUM(port_number)

The TCP/IP port number.

If you used a port number other than the default, use that port number on the primary node, backup node, and main partition.

RELDEVLCK Checks and releases device external locks (DEL) on an array for any image.

Syntax

RELDEVLCK IMAGENAME(image_name)

PATHNAME(path_name)

STEPNUM(step_number)

Description

RELDEVLCK checks for one or more SYMAPI device external locks (DEL) that were left on the array and attempts to release those locks using SYMAPI calls. Specify the image name, path name, and step number for the locks to be released.

Required parameters

IMAGENAME(image_name)

The name of the image for which you want to release the locks.

PATHNAME(path_name)

The path name associated with the image for which you want to release locks.

Standard Features Commands Reference 133

STEPNUM(step_number)

The step number associated with the path of the image for which you want to release locks.

NOTE: Steps in the path are defined during the configuration and are identified by their positions (one through five) in the path.

RELDEVLCKC Checks and releases device external locks (DEL) on an array for any image on the target side.

Syntax

RELDEVLCKC IMAGENAME(image_name)

PATHNAME(path_name)

STEPNUM(step_number)

Description

RELDEVLCKC checks for one or more SYMAPI device external locks (DEL) that were left on the array and attempts to release those locks using SYMAPI calls. Specify the image name, path name, and step number for the locks to be released.

Required parameters

IMAGENAME(image_name)

The name of the image for which you want to release the locks.

PATHNAME(path_name)

The path name associated with the image for which you want to release locks.

STEPNUM(step_number)

The step number associated with the path of the image for which you want to release locks.

RTVSTMINF Returns status information for the selected image, path, and step. It also returns SRDF/TimeFinder Manager, Solutions Enabler, and I/O driver and release level information. This command can only be run within an IBM i command language program. See Example command language program for an example command language program, and how to run the program.

NOTE: Some of the parameter return values are strings and others are decimal values. See Return parameters for more information.

Syntax

RTVSTMINF IMAGENAME(image_name)

PATHNAME(path_name)

STEPNUM(step_number)

NODENAME(node_name)

IASPSTS(&IASPSTS)

IOASTS(&IOASTS)

134 Standard Features Commands Reference

SYMSTS(&SYMSTS)

SYMSTSSTR(&SYMSTSSTR)

STEPTYPE(&STEPTYPE)

RDFTYPE(&RDFTYPE)

RDFMODE(&RDFMODE)

RDFACMODE(&RDFACMODE)

INVTRACKS(&INVTRACKS)

STMRELLVL(&STMRELLVL)

STMEDTLVL(&STMEDTLVL)

STMBLDLVL(&STMBLDLVL)

SERELLVL(&SERELLVL)

SEPCTHLVL(&SEPCTHLVL)

LBIORELLVL(&LBIORELLVL)

LBIOBLDLVL(&LBIOBLDLVL)

UCODE1(&UCODE1)...

UCODE5(&UCODE5)

[SRCORTGT (TGTDEV|SRCDEV)]

Required parameters

IMAGENAME(image_name)

The name of the image.

PATHNAME(path_name)

The path name associated with the image.

STEPNUM(step_number)

The step number associated with the path of the image.

NODENAME(node_name)

The node name where the operation is performed. Node name must be a cluster node name. The node name entered must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

NOTE: The special node name R21NOHST is changed to R21NONOD.

Optional parameters

SRCORTGT (TGTDEV|SRCDEV)

This parameter is used to differentiate between source or target in the event both images are located on the same node.

This can happen, for example, when an R2 and remote BCV image are used on the same node. Only specifying the node is not enough. If the IASP file does not have an entry where the source and target node is the same, this parameter is set to the default value (TGTDEV).

Standard Features Commands Reference 135

Return parameters

IASPSTS(&IASPSTS) decimal value(5 0)

Returns one of the following values for IASP status:

0 IASP status cannot be found.

1 IASP is varied off.

2 IASP is varied on.

3 IASP is active.

4 IASP is available

IOASTS(&IOASTS) decimal value(5 0)

Returns one of the following value for IOA status:

100 IOA is active.

101 IOA is not active.

102 IOA is in a mixed state.

103 IOA status not found.

SYMSTS(&SYMSTS)

Returns a decimal value for the array copy status or RDF link status.

CL var for SYMSTS (8 0)

Specifies the name of the CL variable that receives the Symmetrix link state. The state value depends on the step type. When the setup is not in a correct state a general status is provided to indicate what is wrong. The SYMSTSSTR is set to unknown.

NOTE: Values can be returned in string format using the return parameter SYMSTSSTR(&SYMSTSSTR).

Return values for SYMSTS are dependent on the STEPTYPE:

STEPTYPE is BCV (1) or CLN (2) decimal value (8 0):

00001000 - Never Established

00001001 - Sync in progress

00001002 - Synchronized

00001003 - Split in progress

00001004 - Split before sync

00001005 - Split

00001006 - Split no incremental

00001007 - Restore in progress

00001008 - Restored

00001009 - Split before restore

00001010 - State is invalid

00001011 - State not applicable

STEPTYPE is NCL (3) decimal value (8 0):

00010000 - State not applicable

00010001 - Copy in progress

00010002 - Copied

00010003 - Copy on access

00010004 - Invalid

00010005 - Create in progress

00010006 - Created

00010007 - Copy on write

00010008 - Restored

136 Standard Features Commands Reference

00010009 - Terminate in progress

00010010 - Restore in progress

00010011 - Failed

00010012 - Recreated

00010013 - Pre copy

00010014 - Split

STEPTYPE is RDF (5) decimal value (8 0):

00000100 - Invalid

00000101 - Sync in progress

00000102 - Synchronized

00000103 - Split

00000104 - Suspended

00000105 - Failed Over

00000106 - Partitioned

00000107 - R1 updated

00000108 - R1 update in progress

00000109 - Mixed

00000110 - State not Applicable

00000111 - Consistent

00000112 - Transmit idle

STEPTYPE is SVX (6) decimal value (8 0):

00100000 - State not applicable

00100001 - Establish in progress

00100002 - Establish (Copy on write)

00100003 - Restore in progress

00100004 - Restored

00100005 - Terminate in progress

00100006 - Linked no copy

00100007 - Linked copy in progress

00100008 - Link copied

00100009 - Snapshot failed

00100010 - Link force failed

STEPTYPE is SRDFM (7) decimal value (8 0):

01000113 Active Active

01000114 Active Bias

STEPTYPE is BCV (1), CLN (2), NCL (3), RDF (5), or SVX (6) decimal variable (8 0). The following values are the same for all step types:

0000061 - Configuration is not valid

0000062 - Step is not configured

0000063 - Step is not consistent

0000064 - Config changed, image file not up to date

0000065 - Not all devices are paired

0000066 - Not all devices are paired but source devices are restored

0000067 - All devices are paired and source devs are restored (temp status)

0000068 - All devices are paired and source devs are linked (temp status)

Standard Features Commands Reference 137

0000069 - Not all devices are paired but source devices are restore in prog.

STEPTYPE(&STEPTYPE)decimal value (5 0)

Returns one of the following values for the step type that is configured for an image.

0 Step type could not be determined.

1 BCV type devices (BCV).

2 Clone type devices (CLN).

3 Native clone devices (NCL).

5 RDF type devices (RDF).

6 SnapVX type devices (SVX).

7 SRDF/Metro (SRDFM)

RDFTYPE(&RDFTYPE) decimal value (5 0)

Returns one of the following values for the SRDF type for an image.

0 RDF type source devices is R1

1 RDF type source devices is R2

2 RDF type could not be determined.

RDFMODE(&RDFMODE) decimal value (5 0)

Returns one of the following values for the SRDF link status.

0 RDF mode synchronous

1 RDF mode semi synchronous

2 RDF mode adaptive copy

3 RDF mode mixed

4 RDF mode not applicable

5 RDF mode asynchronous

6 RDF mode is SRDF/Metro

RDFACMODE(&RDFACMODE) decimal value (5 0)

Returns one of the following values for the SRDF link adaptive copy status.

0 RDF AC Mode disabled

1 RDF AC Mode Write Pending Mode

2 RDF AC Mode Disk Mode

3 RDF AC Mode mixed Mode

4 RDF AC Mode is not applicable

INVTRACKS(&INVTRACKS)

Returns the value for the amount of invalid tracks or the percentage of data copied (16 characters).

123456789012 - number of invalid tracks

100% - percentage

INV_TR_NA - Invalid tracks could not be determined

STMRELLVL(&STMRELLVL)

Returns the value for the SRDF/TimeFinder Manager release level (five characters).

STMEDTLVL(&STMEDTLVL)

Returns the value for the SRDF/TimeFinder Manager edit level (five characters).

STMBLDLVL(&STMBLDLVL)

Returns the value for the SRDF/TimeFinder Manager build level (five characters).

SEREVLVL(&SEREVLVL)

Returns the value for Solutions Enabler release level (15 characters).

SEPTCLVL(&SEPTCLVL)

138 Standard Features Commands Reference

Returns the value for Solutions Enabler patch level (15 characters).

LBIORELLVL(&LBIORELLVL)

Returns the value for I/O driver LIBIO release level (six characters).

LBIOBLDLVL(&LBIOBLDLVL)

Returns the value for I/O driver LIBIO build level (five characters).

UCODE1(&UCOCDE1)...UCODE5(&UCOCDE5)

Returns the value for EMC array ID for up to five arrays (35 characters).

Example command language program

A program must be written to run the RTVSTMINF command, and to format the display for the information that the command returns. The following is an example program named TSTRTVINF:

PGM PARM(&IMGNAME &PATHNAME &STEPNUM &NODENAME + &SRCORTGT)

DCL VAR(&IMGNAME) TYPE(*CHAR) LEN(10) DCL VAR(&PATHNAME) TYPE(*CHAR) LEN(10) DCL VAR(&STEPNUM) TYPE(*CHAR) LEN(1) DCL VAR(&NODENAME) TYPE(*CHAR) LEN(8) DCL VAR(&SRCORTGT) TYPE(*CHAR) LEN(6) DCL VAR(&IASPSTS) TYPE(*DEC) LEN(5 0) DCL VAR(&IOASTS) TYPE(*DEC) LEN(5 0) DCL VAR(&STEPTYPE) TYPE(*DEC) LEN(5 0) DCL VAR(&SYMSTSSTR) TYPE(*CHAR) LEN(32) DCL VAR(&SYMSTS) TYPE(*DEC) LEN(8 0) DCL VAR(&RDFTYPE) TYPE(*DEC) LEN(5 0) DCL VAR(&RDFMODE) TYPE(*DEC) LEN(5 0) DCL VAR(&RDFACMODE) TYPE(*DEC) LEN(5 0) DCL VAR(&INVTRACKS) TYPE(*CHAR) LEN(12) DCL VAR(&STMRELLVL) TYPE(*CHAR) LEN(5) DCL VAR(&STMEDTLVL) TYPE(*CHAR) LEN(5) DCL VAR(&STMBLDLVL) TYPE(*CHAR) LEN(5) DCL VAR(&SERELLVL) TYPE(*CHAR) LEN(20) DCL VAR(&SEPTCHLVL) TYPE(*CHAR) LEN(20) DCL VAR(&LBIORELLVL) TYPE(*CHAR) LEN(6) DCL VAR(&LBIOBLDLVL) TYPE(*CHAR) LEN(5) DCL VAR(&UCODE1) TYPE(*CHAR) LEN(35) DCL VAR(&IASPSTSA) TYPE(*CHAR) LEN(10) DCL VAR(&IOASTSA) TYPE(*CHAR) LEN(10) DCL VAR(&STEPTYPEA) TYPE(*CHAR) LEN(10) DCL VAR(&SYMSTSA) TYPE(*CHAR) LEN(10) DCL VAR(&RDFTYPEA) TYPE(*CHAR) LEN(10) DCL VAR(&RDFMODEA) TYPE(*CHAR) LEN(10) DCL VAR(&RDFACMODEA) TYPE(*CHAR) LEN(10) DCL VAR(&UCODE1) TYPE(*CHAR) LEN(35) DCL VAR(&UCODE2) TYPE(*CHAR) LEN(35) DCL VAR(&UCODE3) TYPE(*CHAR) LEN(35) DCL VAR(&UCODE4) TYPE(*CHAR) LEN(35) DCL VAR(&UCODE5) TYPE(*CHAR) LEN(35)

RTVSTMINF IMAGENAME(&IMGNAME) PATHNAME(&PATHNAME) + STEPNUM(&STEPNUM) NODENAME(&NODENAME) + SRCORTGT(&SRCORTGT) IASPSTS(&IASPSTS) + IOASTS(&IOASTS) STEPTYPE(&STEPTYPE) + SYMSTS(&SYMSTS) SYMSTSSTR(&SYMSTSSTR) + RDFTYPE(&RDFTYPE) RDFMODE(&RDFMODE) + RDFACMODE(&RDFACMODE) + INVTRACKS(&INVTRACKS) + STMRELLVL(&STMRELLVL) + STMEDTLVL(&STMEDTLVL) + STMBLDLVL(&STMBLDLVL) SERELLVL(&SERELLVL) + SEPTCHLVL(&SEPTCHLVL) + LBIORELLVL(&LBIORELLVL) + LBIOBLDLVL(&LBIOBLDLVL) UCODE1(&UCODE1) + UCODE2(&UCODE2) UCODE3(&UCODE3) + UCODE4(&UCODE4) UCODE5(&UCODE5)

Standard Features Commands Reference 139

CHGVAR VAR(&IASPSTSA) VALUE(&IASPSTS) CHGVAR VAR(&IOASTSA) VALUE(&IOASTS) CHGVAR VAR(&STEPTYPEA) VALUE(&STEPTYPE) CHGVAR VAR(&SYMSTSA) VALUE(&SYMSTS) CHGVAR VAR(&RDFTYPEA) VALUE(&RDFTYPE) CHGVAR VAR(&RDFMODEA) VALUE(&RDFMODE) CHGVAR VAR(&RDFACMODEA) VALUE(&RDFACMODE)

SNDPGMMSG MSG('RESULTS STMVER:' *BCAT &STMRELLVL *BCAT + &STMEDTLVL *BCAT &STMBLDLVL) SNDPGMMSG MSG('RESULTS LIBIOV:' *BCAT &LBIORELLVL + *BCAT &LBIOBLDLVL) SNDPGMMSG MSG('RESULTS SE_VER:' *BCAT &SERELLVL *BCAT + &SEPTCHLVL) SNDPGMMSG MSG('RESULTS IOASTS:' *BCAT &IOASTSA) SNDPGMMSG MSG('RESULTS IASPSTS:' *BCAT &IASPSTSA) SNDPGMMSG MSG('RESULTS SYMSTS:' *BCAT &SYMSTSA) SNDPGMMSG MSG('RESULTS SYMSTSSTR:' *BCAT &SYMSTSSTR) SNDPGMMSG MSG('RESULTS STEPTYPE:' *BCAT &STEPTYPEA) SNDPGMMSG MSG('RESULTS RDFTYPE:' *BCAT &RDFTYPEA) SNDPGMMSG MSG('RESULTS RDFMODE:' *BCAT &RDFMODEA) SNDPGMMSG MSG('RESULTS RDFACMODE:' *BCAT &RDFACMODEA) SNDPGMMSG MSG('RESULTS INVTRACKS:' *BCAT &INVTRACKS) SNDPGMMSG MSG('RESULTS UCODE1:' *BCAT &UCODE1)

ENDPGM

Run example program (TSTRTVINF) from the IBM i command line

CALL PGM(TSTRTVINF) PARM(SANIBEL REMOTENCL '1' S3TESTQ SRCDEV)

RESULTS STMVER: 10.0 0 133 RESULTS LIBIOV: 4.4.02 15 RESULTS SE_VER: T10.0-2654 0.389 RESULTS IOASTS: 0000000100 RESULTS IASPSTS: 0000000001 RESULTS SYMSTS: 0000000103 RESULTS SYMSTSSTR: Split RESULTS STEPTYPE: 0000000005 RESULTS RDFTYPE: 0000000000 RESULTS RDFMODE: 0000000000 RESULTS RDFACMODE: 0000000000 RESULTS INVTRACKS: 23 RESULTS UCODE1: 000120000507 :6079

If the TSTRTVINF command fails, the following message returns:

Retrieve STM information failed.

NOTE: The output for this example program reports Enginuity version levels for one array. The Enginuity versions for up to five arrays can be reported.

It is not required to call for all parameters in the command line program. For example, to retrieve only the IOA status, the RTVSTMINF and SNDPGMMSG commands in the CL program are as follows:

For the RTVSTMINF command:

RTVSTMINF IMAGENAME(&IMGNAME) PATHNAME(&PATHNAME) STEPNUM(&STEPNUM) NODENAME (&NODENAME) IOASTS(&IOASTS)

For the SNDPGMMSG command:

SNDPGMMSG MSG('RESULTS IOASTS:' *BCAT &IOASTSA)

140 Standard Features Commands Reference

Display All Messages System: XYZ

Job . . : QPADEV0002, User . . : QSECOFR Number . . . : 193487

CALL PGM(TSTRTVINF) PARM(PRIM1 LOCALNCL '1' NODE124) Retrieve STM information completed.. RESULTS IOASTS: 0000000100 Bottom

Press Enter to continue.

F3=Exit F5=Refresh F12=Cancel F17=Top F18=Bottom

SETBIAS Switches the bias between a pair of devices in a SRDF/Metro configuration.

Syntax

SETBIAS SYMMID(sym_id)

GRPNUM(group_number)

FILENAME(file_name)

BIAS(R2)

Description

Defines which device in a SRDF/Metro pair is the bias side when the pair use bias protection. This command is available only when the air state is Active Bias.

Required parameters

SYMMID(sym_id)

The identity of the storage array on which to set the bias.

GRPNUM(group_number)

The identifty of the SRDF group that contains the relevant device pair. The group number size can be four digits.

FILENAME(file_name)

Specifies the name of the device file to use with the SETBIAS command. The file lists the devices to change the bias setting for.

When creating the file, the following rules apply:

The file is a record file and record length must not exceed 40.

The file contains two columns that lists the source device then target device.

List each device on a separate line.

Comment lines are allowed and they must begin with the pound sign (#).

The device file resides in the library list.

Standard Features Commands Reference 141

Example device file:

##Devices for SETBIAS BIAS(R2) command 009A 0088 009E 0089 009F 008a

BIAS(R2)

Defines the identity (R2) that each of the devices listed in the file adopts.

Example

SETBIAS SYMID(000197902224) GRPNUM(00) FILENAME(SRDF1) BIAS(R2)

SETRDFGRP Specifies the attribute settings for the RDF group.

NOTE: SETRDFGRP is currently limited to RDF/A attributes.

Syntax

SETRDFGRP SYMID(sym_id)

GRPNUM(group_number)

[POOLNAME(pool_name|NO_POOL|*SAME)]

[DSE(ENABLE|DISABLE|*SAME)]

[DSE_THOLD(percent)]

[TRNIDLE(ENABLE|DISABLE|*SAME)]

[DEVPACE(ENABLE|DISABLE|*SAME)]

[WRP_ASTART(ENABLE|DISABLE|*SAME)]

[WRP_DELAY(delay_time)]

[WRP_THOLD(percent)]

[HDW_COMPR(ENABLE|DISABLE|*SAME)]

[SFW_COMPR(ENABLE|DISABLE|*SAME)]

[AUTO_LINK(ENABLE|DISABLE|*SAME)]

[LINK_LIMBO (link_limbo_time|*SAME)]

[BOTH_SIDES(*YES|*NO)]

Description

SETRDFGRP manages the attribute settings for the RDF group, such as:

Whether SRDF/A DSE is automatically activated when an SRDF/A session is activated

How SRDF/TimeFinder Manager should handle situations where the transmission link is idling.

142 Standard Features Commands Reference

Required parameters

SYMID(sym_id)

The name of the array.

NOTE: If the array ID is known, enter its name. If the array ID is not known, press F4 to display a list of all local and remote arrays attached to the host.

GRPNUM(group_number)

The number of the RA group. The group number size can be four digits.

Optional parameters

DSE(ENABLE|DISABLE|*SAME)

Specifies whether SRDF/A DSE is automatically activated when an SRDF/A session is activated for the group. Options are as follows:

ENABLE Automatically activates SRDF/A DSE when an SRDF/A session is activated for the group.

DISABLE Does not automatically activate SRDF/A DSE when an SRDF/A session is activated for the group.

*SAME Ignores this parameter during command processing, or when ENABLE or DISABLE is specified, and DSE auto start is already in the desired state. This is the default.

NOTE: For arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 DSE autostart for SRDF/A groups is enabled by default.

DSE_THOLD(percent)

Specifies the percentage of the write pending limit of the DSE threshold.

Groups with higher threshold values keep their data in cache longer at the expense of groups with lower values. Valid values range from 20 to 100. If nothing is specified or the RDF group has a desired DSE threshold, SRDF/TimeFinder Manager ignores this parameter during command processing.

TRNIDLE(ENABLE|DISABLE|*SAME)

Specifies how to handle a situation where the transmission link is idling.

Transmit Idle, an SRDF/A Reserve Capacity feature, allows SRDF/A sessions to seamlessly tolerate a transient link failure. Transmit Idle provides an extra level of protection from sessions dropping when the RDF link cannot transmit data. When links associated with SRDF/A are unable to transmit data, the Transmit Idle state is activated.

Options are as follows:

ENABLE Tolerate SRDF/A.

DISABLE Drop SRDF/A.

*SAME Ignores this parameter during command processing, or when ENABLE or DISABLE is specified, and Transmit Idle is already in the desired state. This is the default.

DEVPACE(ENABLE|DISABLE|*SAME)

Specifies whether SRDF/A Device-level Write Pacing is automatically activated when an SRDF/A session is activated for the group:

ENABLE Automatically activates SRDF/A Device-level Write Pacing when an SRDF/A session is activated for the group.

DISABLE Do not automatically activate SRDF/A Device-level Write Pacing when an SRDF/A session is activated for the group.

*SAME Ignores this parameter during command processing, or when ENABLE or DISABLE is specified, and DSE device-level write pacing auto start is already in the desired state. This is the default.

WRP_ASTART(ENABLE|DISABLE|*SAME)

Standard Features Commands Reference 143

Specifies whether the SRDF/A group-level write pacing feature is automatically enabled or disabled when an SRDF/A session is activated for the SRDF group:

ENABLE Automatically activates SRDF/A Group-level Write Pacing when an SRDF/A session is activated for the group.

DISABLE Do not automatically activate SRDF/A Group-level Write Pacing when an SRDF/A session is activated for the group.

*SAME Ignores this parameter during command processing, or when ENABLE or DISABLE is specified, and SRDF/A group-level write pacing is already in the desired state. This is the default.

NOTE: This command cannot be run if both arrays are on HYPERMAX OS 5977 and above.

WRP_DELAY(delay_time)

Sets the maximum host I/O delay, in microseconds, that triggers SRDF/A write pacing. Valid values are between one and 1000000 micro-seconds. The default value is 50000 micro-seconds.

If the write pace delay is not specified, or an SRDF group already has a desired write pacing delay, SRDF/TimeFinder Manager ignores this parameter during command processing.

NOTE: This command cannot be run if both arrays are on HYPERMAX OS 5977 and above.

WRP_THOLD(percent)

Sets the minimum percentage of the system write-pending cache at which the array begins pacing host write I/Os, for an SRDF group. Valid values are between one and 99. The default value is 60.

If the write pace threshold is not specified, or an SRDF group already has a desired write pacing threshold, SRDF/TimeFinder Manager ignores this parameter during command processing.

NOTE: This command cannot be run if both arrays are on HYPERMAX OS level 5977 and above.

SRDF software and hardware compression.

Compression minimizes the amount of data to be transmitted over an SRDF link. Enabling hardware compression on GigE directors and software compression on Fibre and GigE directors using Solutions Enabler is available.

Rules and restrictions for compression are as follows:

Enabling hardware compression on Fibre directors is available.

Software and hardware compression can be enabled on the R1 and R2 sides of the SRDF link, but the actual compression takes place on the side initiating the I/O, which is typically the R1 side. Since most I/O requests are initiated from the R1 side, make sure compression is enabled on this side.

Software and hardware compression can only be set at the group level.

HDW_COMPR(ENABLE|DISABLE|*SAME)

Specifies whether to enable or disable hardware compression for the SRDF group:

ENABLE Enables hardware compression for the SRDF group.

DISABLE Disables hardware compression for the SRDF group.

*SAME Ignores this parameter during command processing, or when ENABLE or DISABLE is specified, and compression for the SRDF group is already in the desired state. This is the default.

SFW_COMPR(ENABLE|DISABLE|*SAME)

Specifies whether to enable or disable software compression for the SRDF group:

ENABLE Enables software compression for the SRDF group.

DISABLE Disables software compression for the SRDF group.

*SAME Ignores this parameter during command processing, or when ENABLE or DISABLE is specified, and compression for the SRDF group is already in the desired state. This is the default.

AUTO_LINK(ENABLE|DISABLE|*SAME)

Specifies whether to use the Auto Link Recovery feature locally.

ENABLE Enables Auto Link Recovery.

144 Standard Features Commands Reference

DISABLE Disables Auto Link Recovery.

*SAME Ignores this parameter during command processing, if *SAME is specified, or if ENABLE or DISABLE is specified and Auto Link Recovery is in the desired state. This is the default.

LINK_LIMBO (link_limbo_time|*SAME)

NOTE: The option should only be used by experienced SRDF users.

Specifies the length of time to wait from the point of link-down detection before actually updating the link status as down. If the link status is still sensed as Not Ready after the link limbo time expires, devices are marked Not Ready to the link. If nothing is specified, Ignores the parameter during command processing, if *SAME is specified, or if RDF group already has a desired link limbo value. The link limbo range is zero to 120 seconds. The default time is 10 seconds.

BOTH_SIDES(*YES|*NO)

Specifies whether changes should be applied only locally or both locally and remotely:

*YES Changes are applied locally and remotely.

NOTE: If the remote side cannot be reached and the flag is set to YES, the command fails.

*NO Changes are applied locally. This is the default.

Examples

SETRDFGRP SYMID(000123456789) GRPNUM(7B) DSE_THOLD(60) TRNIDLE(ENABLE) DEVPACE(ENABLE) WRPA_START(ENABLE) WRP_DELAY(60000) WRP_THOLD(70) HRDW_COMPR(ENABLE) SOFTW_COMPR(ENABLE) BOTH_SIDES(*YES)

SETRDFGRP SYMID(000123456789) GRPNUM(20) TRNIDLE(ENABLE) DEVPACE(ENABLE) WRP_ASTART(ENABLE) WRP_DELAY(60000) WRP_THOLD(70) HDW_COMPR(ENABLE) SFW_COMPR(ENABLE)

AUTO_LINK(ENABLE) LINK_LIMBO(20) BOTH_SIDES(*YES)

SETRDFMOD Sets the SRDF mode for a selected image.

Syntax

SETRDFMOD IMAGE_NAME(image_name)

PATH_NAME(path_name)

STEPNUM(step_number)

MODE_TYPE(SYNC|ASYNC|ACDM|METRO)

METROMODE(A|B)

Description

SETRFDMOD sets the SRDF mode (Synchronous, Asynchronous, Metro, and adaptive copy disk mode (ACDM)) for a selected image. The name of image name, path name, and the SRDF mode associated with the image are mandatory items.

Required parameters

IMAGE_NAME(image_name)

Specifies the name of the image.

Standard Features Commands Reference 145

PATH_NAME(path_name)

Specifies the name of the path for the image.

STEPNUM(step_number)

Specifies the step number.

Steps in the path are defined during configuration and are identified by their positions (1 through 5) in the path.

MODE_TYPE(SYNC|ASYNC|ACDM|METRO)

Specifies the SRDF mode.

CAUTION: Do not use ACDM mode for SRDF while creating RDF or remote TimeFinder images (split) using SRDF/TimeFinder Manager. This is not supported. Instead, use SYNC or ASYNC mode.

METROMODE(A|B)

This parameter is required only when the value of MODE_TYPE is METRO. The value of this parameter defines the protection mechanism that the SRDF/Metro configuration uses:

A Witness protection

B Bias protection

Examples

SETRDFMOD IMAGE_NAME(SYSTEM) PATH_NAME(SRDFA) STEPNUM(1) MODE_TYPE(SYNC) SETRDFMOD IMAGE_NAME(SYSTEM) PATH_NAME(SRDFA) STEPNUM(1) MODE_TYPE(ASYNC) SETRDFMOD IMAGE_NAME(SYSTEM) PATH_NAME(SRDFA) STEPNUM(1) MODE_TYPE(ACDM) SETRDFMOD IMAGE_NAME(SYSTEM) PATH_NAME(SRDFMETRO) STEPNUM(1) MODE_TYPE(METRO) METROMODE(A)

STMENDSBS Stops all running subsystems except for the subsystem where the daemon jobs are running.

Syntax

STMENDSBS OPTION(*CNTRLD|IMMED)

DELAY(0-99999 seconds|*NOLIMIT)

ENDSBSOPT(*DFT|*NOJOBLOG|*CHGPTY|*CHGTSL)

Description

STMENDSBS stops all running subsystems prior to splitting BCV devices or Clone pairs, or SRDF links.

You can run this command interactively or in batch mode

To run this command, you must have the *JOBCTL privilege in your user profile or in any of the group profiles that your account is associated with.

STMENDSBS waits for all subsystems and jobs to end. Once they have ended, STMENDSBS sends this message to QSYSOPR:

CTL240: System ended to semi-restricted condition.

If a subsystem or job does not complete for any reason, STMENDSBS does not continue and does not send this message to QSYSOPR.

When STMENDSBS completes in batch mode, the QCTL is in the ACTIVE state. When the command completes interactively the QCTL state is RSTD.

146 Standard Features Commands Reference

Required parameters

OPTION(*CNTRLD|*IMMED)

Specifies whether jobs in the subsystems are ended in a controlled manner or immediately.

DELAY(0-99999 seconds|*NOLIMIT)

Specifies the time delay for a controlled ending for running subsystems. The default value is *NOLIMIT.

ENDSBSOPT(*DFT|*NOJOBLOG|*CHGPTY|*CHGTSL)

Specifies the options available when ending the active subsystems. In most cases, specifying one of these options improves the performance of the ENDSBS command. This parameter has no effect on jobs that are already in the ending status.

*DFT The subsystems end with special ending option. This is the default value.

*NOJOBLOG No job logs are created for jobs that are ended. This includes subsystem monitor jobs and all user jobs in the subsystem.

*CHGPTY The CPU priority of jobs that are ending changes to a higher value (lower priority) and may take longer to finish. The remaining active jobs on the system may have better performance when *CHGPTY is specified. This option is ignored if the subsystem is ending controlled. However, if the DELAY time limit expires, this option takes effect immediately.

*CHGTSL The time slice of jobs that are ending is changed to a lower value and may take longer to finish. The remaining active jobs on the system may have better performance when *CHGTSL is specified. This option is ignored if the subsystem is ending controlled. However, if the DELAY time limit expires, this option takes effect immediately.

Examples

STMENDSBS OPTION(*CNTRLD) DELAY(*NOLIMIT)

STMRMTCMD Runs remote commands.

Syntax

STMRMTCMD CMD(stm command)

RMTNODENAME(nodename)

PORTNUM (8000|1-65535)

Description

STMRMTCMD command allows execution of commands, on a remote IBM system, through the STM server. The commands used with the STMRMTCMD command are limited to the SRDF/TimeFinder Manager commands that are available on the source or client system, and the following IBM i series commands:

APING

DSPASPSTS

PING

VRYCFG

VFYTCPCNN

WRKCFGSTS

Standard Features Commands Reference 147

Prior to running the STMRMTCMD command, the STM server must be running and configurations must be complete.

When the command completes a file is created that holds the results of the remote command. The file is located in the QGPL library and called RMTCMDOUTC at the client side and RMTCMDOUTS on the server side, and can have multiple members (SPL, SPL2, and so on) depending on the output.

See STRSTMSRV for starting the STM server.

Required parameters

STMRMTCMD CMD(stm command)

Specifies the SRDF/TimeFinder Manager command to run from the remote IBM i system.

RMTNODENAME(nodename)

Specifies the node name of the remote IBM i system.

PORTNUM(8000|1-65535)

Specifies the port number of the remote STM server. Default port is 8000.

STMSTRSBS Starts all subsystems.

Syntax

STMSTRSBS

Description

STMSTRSBS starts all subsystems after running the STMENDSBS command. The command checks to see if the daemon jobs are the only jobs active or if the system is in already in a restricted state. This command then brings the system into a true restricted state by ending all subsystems including the daemon jobs. When this is complete, the controlling subsystem is started. This starts all the required subsystems and jobs, depending on what jobs are defined as auto start jobs and what is set as a startup program defined in the system value QSTRUPPGM.

You can run this command interactively or in batch mode.

To run this command you must have the *JOBCTL privilege in your user profile or in any of the group profiles that you account is associated with.

STMSTRSBS calls a custom startup program when running in batch mode, as long as the STARTUPPGM data area is not blank. STMSTRSBS does not call a custom startup program when running interactively.

The custom startup program can be set up in the EMCCTL or STARTUPPGM data area in the EMCCTL library. The format of the STARTUPPGM data are is:

The first 10 characters contain the program name.

The next 10 characters contain the name of the library where the program is stored.

If this identification is entered incorrectly, STMSTRSBS fails.

Required parameters

None.

STORDAEMON Starts, stops, and queries Solutions Enabler daemons.

148 Standard Features Commands Reference

Syntax

STORDAEMON

ACTION(START|SHUTDOWN|STARTALL|SHUTDOWNALL|STRNODEMON| ENDNODEMON|LIST|SHOW|SHOWLOG)

DAEMONNAME(STORAPID|STORSRVD|STORGNSD)

PORTNBR(port_number between 1 and 65535)

LISTOPT(VERBOSE|RUNNING)

SHOWLOGOPT(number between 1 and 1000)

Description

Starts, stops, and queries the Solutions Enabler daemons:

Storapid (Base)

Storsrvd (Symapi server)

Storgnsd (GNS)

NOTE: See Working with Solutions Enabler daemons for daemon descriptions.

Required parameters

STORDAEMON ACTION(START|SHUTDOWN|SHUTDOWNALL|STRNODEMON|ENDNODEMON| LIST|SHOW|SHOWLOG)

Specifies which action to perform on the specified daemon:

START Starts the specified daemon.

SHUTDOWN Stops specified daemon.

STARTALL Starts all daemons controlled by this command.

STRNODEMON Starts the node monitor.

ENDNODEMON Stops the node monitor.

SHUTDOWNALL Stops all daemons controlled by this command.

LIST Lists all running daemons. See examples below for list type with LISTOPT set to RUNNING and VERBOSE.

SHOW Shows details for a specified daemon.

SHOWLOG Displays the lines from a daemon log file. The number of lines to display is specified by SHOWLOGOPT, starting with the most recently written lines.

DAEMONNAME(STORAPID|STORSRVD|STORGNSD)

Specifies the daemon on which to perform the action.

PORTNBR(port_number between 1 and 65535)

Sets the port number for daemon commands. The default is 2707.

LISTOPT(VERBOSE|RUNNING)

When running the LIST command, specifies what data to display.

VERBOSE Lists the details for all running daemon.

RUNNING Lists all running daemons, names only.

SHOWLOGOPT(number between 1 and 1000)

Standard Features Commands Reference 149

When running the SHOWLOG commands specifies the number of lines to display from a daemon log file, starting with the most recently written lines. The default is 10.

Examples

Start and stop a daemon

STORDAEMON ACTION(START) DAEMONNAME(STORAPID) PORTNBR(2707)

STORDAEMON ACTION(SHUTDOWN) DAEMONNAME(STORAPID)

Stop all daemons

STORDAEMON ACTION(SHUTDOWNALL)

Show the details of a daemon

STORDAEMON ACTION(SHOW) DAEMONNAME(STORAPID)

150 Standard Features Commands Reference

Daemon State : Running Daemon Start Time : Mon Dec 2 08:55:04 2013 Version : X8.0-1900 (0.353) Auto-Restart by Watchdog : Disabled

Total Number of Connections : 4 Number of Active Connections : 0 Total Number of Requests : 171 Gatekeeper Management : Gatekeeper (GK) Management State : Running GK Management Total open GKs : 0 GK Management open GKs highwater : 2 Allow PPath Native Devs as GKs : N/A MPGK Selection : conditional Unreachable Array Time Limit : 7 days Path Algorithm : QOS Alt. Path Algorithm : random Allow QOS Path Failover : Yes Force RDF Path Analysis : No Total File Descriptors : 22

Feature options : Parallel Discovery : Enabled Parallel Inquiry : Disabled Lock Information Export : Enabled Background Audit Logging : Disabled Background App Registration : Enabled

Config options : Resource Recovery Interval : 7 second(s) Parallel Discovery Max Threads : 6 Parallel Inquiry Max Threads : N/A Device Inquiry Timeout : N/A Background App Reg Interval : 900 second(s) Persistent DEL Recovery Interval : 60 second(s) SFS File Recovery Interval : N/A Maximum FDs allowed : N/A

QOS options : Dev Name Inquiry Interval : 15 minutes Rec. Dev Name Inq. Interval : 15 minutes Short Term Sync interval : 1 minute Short Term Sync Limit : 5 minutes Long Term Sync Interval : Disabled Short Term Backoff Interval : 15 minutes Short Term Backoff Limit : 1 hour Long Term Backoff Interval : 1 hour Long Term Backoff Limit : 1 day Min Ping Interval : 5 minutes Discovery Interval : 1 day Max GK Utilization (%) : 50

List all running daemons

STORDAEMON ACTION(LIST) LISTOPT(RUNNING)

Available Daemons ('[*]': Currently Running):

[*] storapid EMC Solutions Enabler Base Daemon [*] storgnsd EMC Solutions Enabler GNS Daemon

List all the running daemons

LISTOPT set to VERBOSE.

NOTE: This example output is abbreviated. The actual output lists all the parameters as shown in the output for SHOW action.

Standard Features Commands Reference 151

STORDAEMON ACTION(LIST) LISTOPT(VERBOSE)

[*] storapid EMC Solutions Enabler API Daemon ------------------ Daemon State : Running Daemon Start Time : Wed Nov 27 03:49:27 2013 Version : X8.0-1900 (0.353) Auto-Restart by Watchdog : Disabled

Total Number of Connections : 3 Number of Active Connections : 0 Total Number of Requests : 4 .......

[*] storgnsd EMC Solutions Enabler GNS Daemon ------------------ Daemon State : Running Daemon Start Time : Wed Nov 27 03:50:27 2013 Version : X8.0-1900 (0.353) Auto-Restart by Watchdog : Disabled

Total Number of Connections : 3 Number of Active Connections : 0 Total Number of Requests : 4 ......

Show the log file for the specified daemon

SHOWLOG option set to 10 lines.

STORDAEMON ACTION(SHOWLOG) DAEMONNAME(STORAPID)

The storapid daemon uses the following log files ('*' : most recently written): [*] /var/symapi/log/storapid.log0

/var/symapi/log/storapid.log1

Last 10 lines of log file:

[19825 -sync] Dec-02 10:02:14.044 : [dmnInqryCreateDeviceList()] Inquiry request received from gkmgt

[19825 -sync] Dec-02 10:02:14.861 : [dmnInqryCreateDeviceList()] Inquiry complete in 814.576 msec for gkmgt, 25 devices found

[19825 -sync] Dec-02 10:17:15.765 : [dmnInqryCreateDeviceList()] Inquiry request received from gkmgt

[19825 -sync] Dec-02 10:17:16.686 : [dmnInqryCreateDeviceList()] Inquiry complete in 913.256 msec for gkmgt, 25 devices found

[19825 -sync] Dec-02 10:32:17.590 : [dmnInqryCreateDeviceList()] Inquiry request received from gkmgt

[19825 -sync] Dec-02 10:32:18.409 : [dmnInqryCreateDeviceList()] Inquiry complete in 817.080 msec for gkmgt, 25 devices found

[19825 -sync] Dec-02 10:47:19.313 : [dmnInqryCreateDeviceList()] Inquiry request received from gkmgt

[19825 -sync] Dec-02 10:47:20.137 : [dmnInqryCreateDeviceList()] Inquiry complete in 821.808 msec for gkmgt, 25 devices found

[19825 -sync] Dec-02 11:02:21.042 : [dmnInqryCreateDeviceList()] Inquiry request received from gkmgt

[19825 -sync] Dec-02 11:02:21.858 : [dmnInqryCreateDeviceList()] Inquiry complete in 814.504 msec for gkmgt, 25 devices found

STRSTMSRV Starts the SRDF/TimeFinder Manager server job.

152 Standard Features Commands Reference

Syntax

STRSTMSRV

USERID(user_id)

PORTNUM(port_number)

JOBQ(job_queue)

CCSID(*CURRENT|*USRPRF|*SYSVAL|*HEX|1-65535)

Description

STRSTMSRV starts the job that runs the server job on the node on which the command executes. This command must be run on all nodes. If you do not supply a port number, the STRSTMSRV command uses the default of 8000.

If STRSTMSRV fails to start, use the NETSTAT option 3 (IPV4) or option 6 (IPV6) to ensure no communication jobs are using 8000. STMSERVER runs one job constantly; others are submitted and subsequently ended during operations.

Required parameters

USERID(user_id)

The user ID of the submitted job under which the server job runs. The default value is *CURRENT.

PORTNUM(port_number)

The TCP/IP port number. The default value is 8000. If you use a different port number, keep the port number consistent on all nodes participating in IASP operations.

JOBQ(job_queue)

The name of the job queue where the server job runs. The default value is *LIBL/EMCCTL.

CCSID(*CURRENT|*USRPRF|*SYSVAL|*HEX|1-65535)

The setting of the coded character set ID (CCSID) for the SRDF/TimeFinder Manager server job. The values are:

*CURRENT The CCSID specified for the job that is currently running is used.

*USRPRF The CCSID specified in the user profile where the submitted job initially runs is used.

*SYSVAL The CCSID specified in the system value QCCSID at the time the job is started is used.

*HEX The CCSID 65535 is used.

1-65535 Specify the CCSID.

Example

STRSTMSRV USERID(*CURRENT) PORTNUM(8000) JOBQ(*LIBL/EMCCTL)

Symmetrix Integration Toolkit 153

B

Symmetrix Integration Toolkit Invisible Body Tagefernce

This appendix lists the supported Solutions Enabler CLI commands that are packaged with the SRDF/TimeFinder Manager software in the Symmetrix Integration Toolkit, and provides some examples. These commands are run from the IBM i command line or Qshell.

Topics:

Supported Solutions Enabler CLI commands Command line examples Supporting documentation

Supported Solutions Enabler CLI commands A limited set of Solutions Enabler CLI commands are available on IBM i systems and are run from the IBM i command line or Qshell.

symaccess Perform auto-provisioning group operations on storage, initiator, and port groups. Also create and manage masking views.

symacl -unique Generate a unique 24-digit access ID for the host machine or operating node to the array. The -unique parameter is the only one you can use with the symacl command.

NOTE: When the command symacl is used on PowerMaxOS 5978 or PowerMax OS 10 (6079) and higher, an error appears that the feature is not supported.

symapierr Translate a SYMAPI return code to a string.

symcfg Discover arrays and display configuration information.

symcli Obtain a brief description of all commands in the Solutions Enabler Symmetrix Command Line Interface (SYMCLI).

symclone Perform TimeFinder/Clone operations on a device group, composite group, or devices listed in a device file.

symdev Perform operations on a specific device.

syminq Issue a SCSI INQUIRY command, and optionally a SCSI READ CAPACITY, on one or all devices. Also, obtain a list of the local host's HBAs.

symlmf [list|query] Reports license types and usage.

For more information on FAST technology and VLUN VP Migration, see the Solutions Enabler Array Controls and Management CLI Guide.

symrdf Perform control operations on SRDF device pairs in an R1/R2 configuration, and concurrent and cascaded SRDF configurations.

symsg Perform operations on storage groups located in a specified array.

symsnapvx Perform TimeFinder/SnapVX control, list, and verify operations on a device list, a list of ranges, a device group (DG), a composite group (CG), or a storage group (SG).

Command line examples The following example displays information about all front-end directors for the specified array using the symcfg command in both the IBM i command line and Qshell formats.

IBM i command line

From the IBM i command line, enter the setup commands:

154 Symmetrix Integration Toolkit

Addlible emcctl CALL PGM(SYMCFG) PARM(list '-SA' 'ALL' '-sid' '710')

Qshell

From the IBM i command line, enter the Qshell setup commands:

Addlible emcctl strqsh cd /qsys.lib/emcctl.lib

From the Qshell, enter:

symcfg.pgm list -SA ALL -sid 710

NOTE: There is a save file available called symapicnfg. This file is restored during installation and is called /var/symapi/config/alias/qshrc. This file holds aliases for the symcli's. To enable them follow the instructions in the header of both files.

Supporting documentation Details on command actions and parameters, options, and error codes for each supported command are in the Solutions Enabler CLI Reference Guide.

Help is also available using the -h parameter with the command. For example:

IBM i command line

CALL PGM(SYMCFG) PARM('-h')

Qshell

symcfg.pgm -h

Or when alias file is configured:

symcfg -h

Standard Features Messages 155

C

Standard Features Messages Invisible Body Tag

This appendix provides reference information about messages that SRDF/TimeFinder Manager components can generate, the reason for the message, and the recommended user action.

CTL0001

SYMAPI error &1 (&2).

Cause: SYMAPI detected an inconsistency.

Action: Refer to the EMC Solutions Enabler documentation.

CTL0002

System level error.

Cause: A call to a system function such as memory allocation failed.

Action: This may be a by-product of a serious system condition that needs attention. After resolving the system problem, the software should run normally, since no internal error caused this problem.

CTL0003

Step number &1 was not found for the path &2.

Cause: A user specified the wrong step number was for the selected path.

Action: Enter the appropriate step for the path and try the operation again.

CTL0004

Failure opening file.

Cause: The file is not found, the file is locked, or the user does not have authority to open the file. Refer to the job log for details.

Action: The failure depends on what the root cause is. Wait until the file is unlocked, change the authority, or take other appropriate action.

CTL0005

Error within Control program. Serious program problem. Contact EMC Customer Support.

Cause: Not specified, but a serious logic or memory problem occurred.

Action: Contact Dell EMC Customer Support.

CTL0006

Path &1 is not disassociated from the image &2.

Cause: The path associated with the selected image has configured steps. The user opted not to disassociate the path.

Action: This is an informational message; no user action is necessary.

CTL0007

Cannot show logical devices for device group &1.

Cause: SYMAPI reports numeric error &2 (&3 - error message description).

Action: Refer to the EMC Solutions Enabler documentation.

156 Standard Features Messages

CTL0008

Error running SYMAPI program.

Cause: SYMAPI reports numeric error &1 (&2 - error message description).

Action: Refer to the EMC Solutions Enabler documentation. If the documentation does not provide a solution to the problem, contact the Dell EMC Customer Support.

CTL0009

On Symmetrix &1 standard device &2 now is paired with BCV device &3.

Cause: The standard device was previously paired with BCV device &4, which is on the same physical disk as one of the mirrors of the standard device.

Action: Manually unpair the standard device and then pair it again.

CTL0010

No available unpaired BCV/SNAP devices.

Cause: There are no available BCV or Snap devices of the right model and capacity.

Action: Either free up the BCV or Snap devices by unpairing them from another use, or have the Dell Customer Support Engineer configure additional BCV or Snap devices within the array.

CTL0011

Cannot unpair BCV devices which are synchronized or in progress or unpaired.

Cause: An attempt was made to unpair devices for the step where devices are established or in progress.

Action: Use control options to split BCV pairs before trying this option. To change device pairing, you must first split the established pairs. If the devices are already unpaired, do nothing. If the devices are in a Synchronized or SyncInProg state, split the devices before making another attempt to unpair the devices.

CTL0012

On Symmetrix &1 standard device &2 is not paired.

Cause: There are no available BCV/Snap devices of the matching configuration.

Action: Make the appropriate device changes for the configuration.

CTL0036

User cancelled SRDF Links processing.

Cause: A user opted to cancel the SRDF links control action processing.

Action: This is an informational message; no user action is necessary.

CTL0037

Processing failed with SYMAPI error &1(&2).

Cause: An error occurred while processing a control action.

Action: Error number and description are provided. Either use this information to correct the problem, or contact Dell EMC Customer Support.

CTL0041

System is not in restricted state. Split control action cannot be run.

Cause: A Split control action can be run only when the system is in a restricted state.

Action: Refer to Split BCV pairs: Restricted state for information to bring a system to a Restricted state.

CTL0042

System is not in restricted state. Suspend SRDF links and action cannot be run.

Cause: A Suspend control action can be run only when the system is in a Restricted state.

Standard Features Messages 157

Action: Refer to Splitting or Suspending SRDF links: Restricted state for information to bring a system to a restricted state.

CTL0048

BCV device &1 attached to STD device &2 is in process of being Split.

Cause: The BCV device pair status is SplitInProg. An Establish control action cannot be performed on this pair.

Action: Wait until the Split operation completes and try the operation again.

CTL0049

Control action failed for device pair &1(S) and &2(B).

Cause: The control action &3 processing failed.

Action: Check the job log for errors.

CTL0050

Processing complete for device pair &1(S) and &2(B).

Cause: Control action &3 initiated successfully.

Action: This is an informational message; no user action is necessary.

CTL0051

Error with devices %s(S) and %s(T).

Cause: This device pair is in invalid state.

Action: Check the devices and their statuses.

CTL0052

Source device &1 has a Target device &2.

Cause: Synchronizing RDF pair is in progress or completed.

Action: Resume SRDF links can be run only when the RDF pair state is in the Suspended state. Establish SRDF links can be run only when the RDF pair state is in a Suspended or Split state.

CTL0053

Source device is &1 and Target device is &2.

Cause: This RDF pair state is in &3 state.

Action: Resume SRDF links can only be run when the links are in a Suspended state. Establish SRDF links can only be run when the links are in a Suspended or Split state.

CTL0055

Control action is initiated for the Image &1.

Cause: &2 control action initiated successfully.

Action: This is an informational message; no user action is necessary.

CTL0056

Standard device &1 (S) has a BCV device &2 (B).

Cause: Synchronizing this BCV pair is in progress or completed.

Action: This is an informational message; no user action is necessary.

CTL0057

User cancelled Establish/Re-establish BCV pairs processing.

Cause: A user opted to cancel the Establish/Re-establish BCV pairs control action processing at this time.

Action: This is an informational message; no user action is necessary.

158 Standard Features Messages

CTL0060

SRDF status for the &1 image is not in Synchronized state so the remote BCV operation may not present a current image of data.

Cause: The SRDF links are not synchronized at this time, so the remote BCV operation may not present a current copy of data on the remote BCV devices.

Action: Make sure that the SRDF links are synchronized to get a current image of data from R1 devices to R2 devices and remote BCV devices.

CTL0064

Error message &1 was received during the IBM i &2 API Call.

Cause: An error occurred while &2 API call was made on the IBM i host.

Action: See the job log for errors. Either use this information to correct the problem, or contact Dell EMC Customer Support.

CTL0076

User cancelled Establishing SRDF Links processing.

Cause: A user opted to cancel the Establish SRDF Links control action processing.

Action: This is an informational message; no user action is necessary.

CTL0077

Job not on Hold (User Name: &1, Job Name: &2, Job Number: &3).

Cause: The job could not be put on hold.

Action: This is an informational message; no user action is necessary.

CTL0078

Job Queue not on Hold (Job Queue Name: &1, Job Queue Library Name: &2).

Cause: The job could not be put on hold.

Action: This is an informational message; no user action is necessary.

CTL0081

Vary off failed for the Independent ASP &1.

Cause: Check the job log for errors.

Action: Make sure that no job is using the independent ASP and then retry the operation.

CTL0083

On Symmetrix &1 paired BCV &2 is on the same physical disk as one of the mirrors of the standard device &3.

Cause: No alternate matching BCV device was found on the separate disk.

Action: This informational message indicates that no user action is required, unless performance of the BCV synchronization needs improvement. Sometimes unpairing of other devices of similar emulation makes other candidates available for pairing. Contact Dell Customer Support if an array reconfiguration is required to reassign volumes or add new BCV devices.

CTL0084

Inconsistencies were detected in the configuration. The Discover command had not been run.

Cause: There is a disk with serial number &1 currently in the ASP &2 with unit number &3, but the configuration database contains ASP &4 with unit number &5.

Action: Run the DISCOVER command to refresh the configuration database.

CTL0085

Inconsistencies were detected in the configuration.

Standard Features Messages 159

Cause: There is a disk with serial number &1 currently in the ASP &2 with unit number &3, but the configuration database contains ASP &4 with unit number &5.

Action: See the job log for errors. Use this information to correct the problem or contact Dell Customer Support.

CTL0086

SymSync failed with error code 34.

Cause: SRDF/TimeFinder Manager cannot communicate with the array with serial number &1. The array could be offline (temporarily or permanently) or the gatekeeper device has been removed or changed.

Action: In case of permanently removed arrays or problems with gatekeeper devices, the configuration database should be refreshed. Run the DISCOVER command with option *YES.

CTL0087

Path &1 was not found for the image &2.

Cause: The wrong path name was specified.

Action: Enter the appropriate path and try the operation again.

CTL0088

Cannot remove device &1 from the device group &2.

Cause: SYMAPI reports numeric error &3 (&4 - error message description).

Action: Refer to the EMC Solutions Enabler documentation.

CTL0089

Cannot delete device group &1.

Cause: SYMAPI reports numeric error &3 (&4 - error message description).

Action: See the Solutions Enabler documentation.

CTL0090

File &1 does not exist.

Cause: The file does not exist in the system.

Action: Make sure that the installation process completed successfully.

CTL0091

Cannot connect to server on &1 with port number &2.

Cause: There are many possible causes for this error, such as the server name may be wrong, the port number may be wrong, and so on.

Action: Check the TCP/IP configuration.

CTL0092

Target IOA is still active.

Cause: Target IOA is still active, but should not be active for this control action.

Action: Remove the target IOA from the node and try the control action again.

CTL0094

Target devices cannot be presented to the host.

Cause: The target devices are already presented to the host.

Action: Remove the target devices from the host.

CTL0095

Target devices cannot be added because the link is synchronized or Synchronize in progress.

160 Standard Features Messages

Cause: Target devices cannot be added to a node if the devices in a Synchronized or SyncInProg state.

Action: Split the link before adding target devices.

CTL0096

IOA file &1 is empty, please rebuild it first.

Cause: The IOA file &1 contains no record(s).

Action: Rebuild the IOA file &1 before proceeding with the operation.

CTL0097

Error messages were issued during EMC control action &1 processing. Check the job log for details about errors.

Cause: Error messages were issued while processing the control action &1.

Action: See the job log for errors. Either use this information to correct the problem, or contact Dell Customer Support.

CTL0098

EMC control action &1 processing initiated successfully. Check the job log for details.

Cause: Control action &1 processing initiated successfully.

Action: This is an informational message; no user action is necessary.

CTL0099

Error messages were issued during EMC control action &1 processing. Check the job log for details about errors.

Cause: Error messages were issued while processing the control action &1.

Action: See the job log for errors. Either use this information to correct the problem, or contact Dell EMC Customer Support.

CTL0100

Socket operation failed, the failed operation is &1.

Cause: The socket operation failed.

Action: Check the TCP/IP configuration and job log.

CTL0104

Operation failed, please check job log for more detail.

Cause: The operation failed.

Action: Check the job log to view a detailed message and then take the appropriate action.

CTL0105

Hold jobs option can be used only when the program is running from the console in an interactive session.

Cause: The application is not running from the console.

Action: Try the operation again from the console.

CTL0106

Path &1 is not deleted from the path file.

Cause: A user opted not to delete the path at this time.

Action: This is an informational message; no user action is necessary.

CTL0107

Image &1 was not found.

Standard Features Messages 161

Cause: A user specified the wrong image name.

Action: Enter the appropriate image name and try the operation again.

CTL0108

ASP &1 was not found in the list of asps for the image &2.

Cause: Some errors occurred.

Action: Try the operation again.

CTL0109

Path &1 was not found in the list of path types.

Cause: A user specified a wrong path name.

Action: Enter the appropriate path and try the operation again.

CTL0110

Specified step number &1 is greater, than number of steps for path &2.

Cause: A user specified the wrong step number.

Action: Enter the appropriate step number and try the operation again.

CTL0111

Cannot add device &1 to the device group &2.

Cause: SYMAPI reports numeric error &3 (&4 - error message description).

Action: See the Solutions Enabler documentation.

CTL0112

Cannot create device group &1.

Cause: SYMAPI reports numeric error &2 (&3 - error message description).

Action: Refer to the EMC Solutions Enabler documentation.

CTL0121

Path &1 is invalid for image &2.

Cause: Not all source devices in the step &3 are RDF capable.

Action: Move ASPs containing one or more non-RDF capable devices to the NON_CONFIG image.

CTL0123

The &1 is &5 for the devices in the &2 image, &3 path, step number &4.

Cause: Control action processing initiated for the image &2.

Action: This is an informational message; no user action is necessary.

CTL0124

&1 processing failed for the &2 image, &3 path and step number &4.

Cause: Control action processing failed for the image &2.

Action: Check the errors in the job log. Contact the Dell EMC Customer Support if needed.

CTL0125

&1 processing initiated for the &2 image, &3 path and step number &4.

Cause: Control action processing initiated successfully for the image &2.

Action: This is an informational message; no user action is necessary.

162 Standard Features Messages

CTL0126

BCV devices are in Sync_in_progress/Restore_in_progress state or Synchronized/Restored for the &1 image, &2 path and step number &3.

Cause: A user tried to Establish the BCV devices, but the BCV state is Synchronized or SyncInProg for the &1 image.

Action: This is an informational message; no user action is necessary.

CTL0127

SPLIT control action cannot be run. Synchronizing/Restoring BCV pairs is in progress for the &1 image, &2 path and step number &3.

Cause: Control action Establish is in progress for the &1 image. The Split action cannot be run at this time.

Action: Wait until the BCV state becomes Synchronized and then try the Split control action.

CTL0128

BCV devices are already in the Split state for the &1 image, &2 path and step number &3.

Cause: A user tried to Split the BCV, but the devices are already in the Split state for the &1 image.

Action: BCV devices state must be Synchronized to run the Split BCV pairs option.

CTL0129

SRDF links are already Synchronized or Sync_in_progress state for the &1 image, &2 path and step number &3.

Cause: A user tried to Resume, Establish, or Restore the SRDF links, but the links are already in a Synchronized or SyncInProg state.

Action: This is an informational message; no user action is necessary.

CTL0130

SRDF links are already Suspended for the &1 image, &2 path and step number &3.

Cause: A user tried to Suspend the SRDF links, but the links are already in a Suspended state.

Action: SRDF links must be in a Synchronized state to run the Suspend SRDF links operation.

CTL0131

Split or Suspend SRDF Links cannot be run. SRDF links are in Sync_in_progress state for the &1 image, &2 path and step number &3.

Cause: The SRDF links are in SyncInProg state. Split or Suspend SRDF links action cannot be run at this time.

Action: Wait until the SRDF link state becomes Synchronized and then try the Split or Suspend control action.

CTL0132

SRDF links are already Split for the &1 image, &2 path and step number &3.

Cause: A user tried to Split the SRDF links, but the links are already in a Split state.

Action: The SRDF links must be in a Synchronized state to run the Split SRDF links option.

CTL0133

Resume SRDF Links cannot be run. SRDF links are in Split state for the &1 image, &2 path and step number &3.

Cause: The SRDF links are in a Split state. The Resume SRDF links control action cannot be run at this time.

Action: The SRDF links must be in a Suspended state to run the Resume SRDF links option.

CTL0134

The devices for the &1 image, &2 path and step number &3 are in ineligible state to perform the control action specified.

Standard Features Messages 163

Cause: Check the status of the devices on the Configuration screen.

Action: Change any configuration details needed. Make sure that the devices are in eligible state for the control action requested.

CTL0135

SNAP devices are not in eligible state to be created, status must be NotCreated.

Cause: It is most likely that the devices have not been paired with the Snap target devices.

Action: Pair the devices with the Snap target devices.

CTL0136

The &1 devices cannot be activated because they are being created.

Cause: The &1 devices cannot be activated because the devices are in the process of being created.

Action: Wait until the devices are created before activating them.

CTL0137

The &1 devices have already been activated.

Cause: The &1 devices have already been activated.

Action: This is an informational message; no user action is necessary.

CTL0138

The System is not in restricted state. The ACTIVATE control action cannot be run.

Cause: The system is not in a Restricted state.

Action: Put the system in a Restricted state and try the operation again.

CTL0139

Path &1 is not associated with the image &2.

Cause: The wrong path name was specified.

Action: Associate a path with the image first and then proceed with the operation.

CTL0140

For &1 image path &2 step &3 unit &4 source device is not known.

Cause: The target device for the previous step is unknown. The previous step is not configured.

Action: Check the configuration.

CTL0141

For &1 image path &2 and step &3 target device &4 is in ineligible state to be unpaired from standard device &5.

Cause: Target device is in &6 state.

Action: This is an informational message; no user action is necessary.

CTL0142

Not all devices in the &1 image are Symmetrix devices. Control actions can be performed only for images having Symmetrix devices.

Cause: &1 image has &2 type of devices.

Action: Move ASPs with non-Symmetrix devices to the NON_CONFIG image.

CTL0143

Additional time required to ensure SRDF/A consistent split.

Cause: Insufficient time was specified in the SRDFATIME data area to perform a consistent Split.

164 Standard Features Messages

Action: Increase the value in the SRDFATIME data area and try the Split operation again.

CTL0144

&1.

Cause: The load source mirror is in an ineligible state.

Action: From the Display Disk Configuration Status screen in SST, check the status of the disks and make appropriate changes.

CTL0145

&1 action failed for the &2 image, &3 path and step number &4.

Cause: A user tried the operation, but the load source is in the &5 state.

Action: From the Display Disk Configuration Status screen in SST, check the status of the disks and make appropriate changes.

CTL0146

Non-Symmetrix devices exist in the configuration.

Cause: The configuration contains devices that are not recognized by the array.

Action: Run the DISCOVER command to refresh the configuration database.

CTL0147

SNAP devices for step &1 and &2 path could not be paired.

Cause: Some or all source devices for the step are RAID 5 BCVs or RAID 6 BCVs and are clone enabled.

Action: This is an informational message; no user action is necessary.

CTL0148

User cancelled the Cancel BCV pairs processing.

Cause: A user opted to cancel the Cancel BCV pairs control action processing at this time.

Action: This is an informational message; no user action is necessary.

CTL0149

Devices for step &1 and &2 path could not be unpaired.

Cause: Some or all BCV devices for the step are RAID 5 BCVs or RAID 6 BCVs and are Clone enabled.

Action: The Cancel BCV pairs control action should be run first.

CTL0150

Devices in step &1 and &2 path for &3 image have a mixed BCV configuration.

Cause: Some BCV devices in the step are standard devices and some are RAID 5 or RAID 6 BCVs.

Action: This is an informational message; no user action is necessary.

CTL0151

System is not ended to restricted condition.

Cause: The system is not ended to the restricted condition in the allocated time.

Action: Use the WRKSBS command to check the status of the controlling subsystem and other subsystems.

CTL0152

Establish control action cannot be run.

Cause: All BCV devices are standard BCVs and there are one or more Clone enabled BCV devices.

Action: Use the Cancel option to remove the incremental relationship between standard devices and the split BCV devices.

Standard Features Messages 165

CTL0153

On Symmetrix &1 for the step &2 target device &3 is in ineligible state to be unpaired from standard device &4.

Cause: Target device is in &5 state.

Action: This is an informational message; no user action is necessary.

CTL0154

Cannot associate &1 device &2 with Composite Group &3.

Cause: The SYMAPI reports error &2(&3).

Action: Refer to the EMC Solutions Enabler documentation.

CTL0156

User cancelled the RDF Clear Consistency state processing.

Cause: A user opted to cancel the RDF Clear Consistency state control action processing.

Action: This is an informational message; no user action is necessary.

CTL0157

User cancelled the Disable SRDF ECA/MSC processing.

Cause: A user cancelled the Disable SRDF ECA/MSC control action processing.

Action: This is an informational message only. No user action is required.

CTL0158

Cannot create composite group &1.

Cause: The SYMAPI reports error &2(&3).

Action: Refer to the EMC Solutions Enabler documentation.

CTL0159

Cannot add device &1 to the composite group &2.

Cause: SYMAPI reports error &3(&4).

Action: Refer to the EMC Solutions Enabler documentation. 0214965511 0214923176

CTL0160

Cannot delete Composite Group &1.

Cause: The SYMAPI reports error &3(&4).

Action: Refer to the EMC Solutions Enabler documentation.

CTL0162

Split while active not completed for step &1 , &2 path and &3 image. SRDF Consistency state not enabled.

Cause: The SRDF Consistency state is not enabled while the SPLIT with SPLITWA option is selected.

Action: Either enable the RDF Consistency State with the CTLACT command (RDFCSENABLE) or use another option with the SPLIT control action (RESTRICTED, MAINTENANCE or HOLDJOBS).

CTL0163

Cannot use SPLITWA option for step that is greater than 2, unless if it is step 3 after cascading RDF.

Cause: Splitting with the SPLITWA option is unnecessary on steps greater than 2, unless it is a step 3 after cascading RDF. For example, a multihop configuration uses a remote BCV/R1 that must be split first to create a valid copy. A BCV/R1 does not have a step number greater than 2.

166 Standard Features Messages

CTL0164

Network address (NETWADDR) and node name (NODENAME) cannot be both empty. Specify either network address or node name.

Cause: User did not specify NETWADDR and/or NODENAME.

Action: Specify a network address or node name. When specifying both parameters, make sure they are unique.

CTL0165

SRDF ECA/MSC protection is not disabled.

Cause: SRDF ECA/MSC protection cannot be disabled because the consistency group does not exist.

Action: Enable the SRDF ECA/MSC protection by executing the CTLACT command with ECAENABLE option.

CTL0166

SRDF SPLITWA cannot be run.

Cause: The user selected the SPLITWA control action for an unsupported feature.

Action: Select a different split control action.

CTL0167

User cancelled the SN-ID Read/Clear action.

Cause: A user opted to cancel the SN-ID Read/Clear action processing.

Action: This is an Informational message. No action is necessary.

CTL0168

Path &1 is invalid for image &2.

Cause: There are RAID 6 devices in the step &3.

Action: Check the configuration.

CTL0169

Path &1 is invalid for image &2.

Cause: There are devices in the step &3 with the RDF group number greater than 64.

Action: Check the configuration.

CTL0170

User cancelled the Terminate SNAP pairs processing.

Cause: A user opted to cancel the Terminate the Snap pairs control action.

Action: This is an informational message; no action is required.

CTL0171

User cancelled Failover processing.

Cause: A user opted to cancel the Failover control action.

Action: This is an informational message; no action is required.

CTL0172

User cancelled Failback processing.

Cause: A user opted to cancel the Failback control action.

Action: This is an informational message; no action is required.

CTL0173

On the Symmetrix &1 changes are not done for the RDF group &2.

Standard Features Messages 167

Cause: Detected no changes from the current configuration.

Action: Informational message. No action is required.

CTL0174

SRDF mode for the &1 image is Adaptive Copy, so the remote BCV operation will not present a current image of data.

Cause: The SRDF links are in Adaptive Copy mode. Therefore, the remote BCV operation may not present a current copy of data on the remote BCV devices.

Action: Make sure that the SRDF links are in Synchronous or Asynchronous mode and the links are in Synchronized or Consistent state to get a current image of data from R1 devices to R2 devices and remote BCV devices.

CTL0176

SymSync failed for the Symmetrix with serial number &1.

Cause: SymSync failed with SYMAPI error &2(&3). Array could be removed temporally or permanently, or the gatekeeper device removed or changed.

Action: In case of permanently removed array or a problem with gatekeeper device, configuration database should be refreshed. Command Discover should be run with option *YES.

CTL0177

Option is not allowed for current version of the operation system.

Cause: This option is only allowed for the V6R1M0 operating system or higher.

Action: Only MAINTENANCE SPLIT/SUSPEND/ACTIVATE is allowed for an IASP image.

CTL0178

Devices are not Varied OFF. Option is not allowed for current version of the operating system.

Cause: This option is only allowed for the V6R1M0 operating system or higher.

Action: Vary off the devices.

CTL0179

Control action &1 will be processed.

Cause: The devices are neither unavailable nor online.

Action: This is an informational message; no user action is necessary.

CTL0180

Devices are not Varied OFF. Control action &1 failed.

Cause: This option is not allowed when devices are varied on.

Action: Vary off the devices.

CTL0181

Data area &1 not found. Default values used.

Cause: Default values have been used: Suspend timeout: &2 Timeout action: &3 Auto-resume timeout: &4.

Action: Contact Dell EMC Customer Support to obtain the &1 data area.

CTL0182

Access to ASP &1 is suspended.

Cause: Access to ASP &1 is suspended. New transactions cannot start until access is resumed. Transaction quiescing used &2 seconds. Operations quiescing used &3 seconds. Writes to disk used &4 seconds, for a total of &5 seconds.

Action: This is an informational message; no action is necessary.

168 Standard Features Messages

CTL0183

&1 Processing timed out after &2 seconds for ASP &3.

Cause: &1 Processing for ASP &3 did not complete within the Suspend Timeout value of &2 seconds.

Action: Change the Suspend Timeout value using the command &P CHGDTAARA (&5/&4 (40 6)) 'nnnnnn' where nnnnnn is the desired Suspend Timeout value in seconds, which must be six digits with leading zeros.

CTL0184

The command processing will continue for ASP &1.

Cause: The Timeout Action has been specified as Continue.

Action: Change the Timeout Action to end the operation on a timeout using the following command: CHGDTAARA (&3/&2 (90 1)) 'E'

CTL0185

The command processing has been ended for ASP &1

Cause: Refer to the messages previously listed. The Timeout Action has been specified as End.

Action: Change the Timeout Action to continue command processing on a timeout with the following command: CHGDTAARA (&3/&2 (90 1)) 'C'

CTL0186

Access to ASP &1 successfully resumed.

Cause: Access to ASP &1 is successfully resumed. Users may access data within the ASP.

Action: This is an informational message; no action is necessary.

CTL0187

Source IOA is still active.

Cause: The target IOA has not been removed from that node.

Action: Remove the target IOA from the node.

CTL0188

For &1 image path &2 step &3 not all source devices are reachable.

Cause: The Problems occur in the previous step.

Action: Check status of the previous step.

CTL0189

SRDF Failover operation failed.

Cause: SRDF Failover with Establish option is specified but these devices are not Dynamic SRDF devices.

Action: Use SRDF Failover with option *NO.

CTL0190

User cancelled the Recreate CLONE pairs processing.

Cause: User opted to cancel the Recreate CLONE pairs control action processing at this time.

Action: This is an informational message; no action is necessary.

CTL0191

User cancelled the Recreate SNAP pairs processing.

Cause: User opted to cancel the Recreate SNAP pairs control action processing at this time.

Action: Informational message. No action is necessary.

Standard Features Messages 169

CTL0192

User cancelled the Terminate CLONE pairs processing.

Cause: User opted to cancel the Terminate CLONE pairs control action processing at this time.

Action: Informational message. No action is necessary.

CTL0193

Path &1 is invalid for image &2.

Cause: Not all source devices in the step &3 are standard devices.

Action: You can change pairing for previous step.

CTL0194

SRDF Create/Delete pair operation failed.

Cause: Control action &1 operation is specified but devices listed in the Device File are not Dynamic SRDF devices.

Action: Use Dynamic RDF devices.

CTL0195

Path &1 is invalid for image &2 for current code level.

Cause: Path is valid for Enginuity 5876 or later.

Action: Informational message. No action is necessary.

CTL0196

Path &1 is invalid for image &2 for current code level.

Cause: Duplicate Snap is valid for Enginuity 5876 or later.

Action: Informational message. No action is necessary.

CTL0197

Device &1 on the Symmetrix &2 is a target device for TF/Clone Emulation session and cannot be used for pairing.

Cause: Target device is already in a Clone emulation session.

Action: Informational message. No action is necessary.

CTL0198

Device &1 on the Symmetrix &2 is a target device for TF/Clone session and cannot be used for pairing.

Cause: Target device is already in a Clone session.

Action: Informational message. No action is necessary.

CTL0199

Cannot use SPLITWA option for second step if first step is not RDF.

Cause: There is no use splitting with SPLITWA option on the second step, unless if it is step 2 after RDF.

Action: Use other split option with the selected step.

CTL0200

Symmetrix &1 does not have &2 license.

Cause: Array does not have requested license.

Action: Informational message. No action is necessary.

170 Standard Features Messages

CTL0201

Device &1 is not found on the Symmetrix &2 and cannot be used for pairing.

Cause: Target device is not found on the array.

Action: Informational message. Check the device file.

CTL0202

Device &1 on the Symmetrix &2 is &3 and cannot be used for pairing for this type of the step.

Cause: Target device has not valid configuration type.

Action: Informational message. Check the device file.

CTL0203

Device &1 on the Symmetrix &2 is in use, i.e. paired with another device and cannot be used for pairing.

Cause: Target device is already in use.

Action: Informational message. Check the device file.

CTL0204

SRDF type for source devices in this step is &1. The SRDF mode for the step is &2.

Cause: Additional status for RDF type of the step is provided.

Action: This is an informational message; no user action is necessary.

CTL0205

SRDF mode for the &1 image, &2 path and step number &3 is Adaptive Copy, so the Failover operation is not allowed.

Cause: Informs the user that the SRDF links are in Adaptive Copy mode.

Action: Make sure that the SRDF links are in Synchronous or Asynchronous mode.

CTL0206

Save pool &1, specified for create virtual copy sessions is not valid for image &2, path &3 and step number &4.

Cause: Not all arrays in the configuration have a specified save pool.

Action: You can call program wrk_pool (option 5 from the main screen) and check available save pools.

CTL0207

Operation to create virtual copy sessions cannot be executed for image &1, path &2 and step number &3.

Cause: Virtual copy session(s) already exists with &4 and &5 save pools.

Action: You can cancel existing sessions and create new ones with desired pool name.

CTL0208

Save pool &1, specified for create virtual copy sessions for image &2, path &3 and step number &4 will be ignored.

Cause: Virtual copy session(s) exists with &5 save pool name.

Action: You can specify correct pool name or cancel existing sessions and create new ones with desired pool name.

CTL0209

Path &1 is invalid for image &2.

Cause: VP Snap should be the last step in the path.

Action: This is an informational message; no user action is necessary.

Standard Features Messages 171

CTL0210

Create VP Snap control action cannot be run.

Cause: Some or all devices in previous step are clone enabled.

Action: This is an informational message; no user action is necessary.

CTL0211

Configuration change &1 for pool &2 is failed.

Cause: Configuration change processing failed for the specified pool.

Action: Check the errors in the symapi log. Contact the Dell EMC Customer Support if needed.

CTL0212

Configuration change &1 for pool &2 is successful.

Cause: Configuration change processing was successful for the specified pool.

Action: This is an informational message; no user action is necessary. Check symapi log for more details.

CTL0213

Configuration change &1 for pool &2 is successful. Termination of the configuration session failed.

Cause: Configuration change processing was successful for the specified pool.

Action: Check the errors in the symapi log. Contact the Dell EMC Customer Support if needed.

CTL0214

RTVSTMINF Error: &1

Cause: RTVSTMINF failed with an error

Action: Check joblog for earlier messages.

CTL0215

&1 cannot be run for the &2 image, &3 path and step number &4.

Cause: Multisession Consistency (MSC) for SRDF/A is enabled. This configuration is not supported.

Action: Change the configuration if needed. Contact the Dell EMC Customer Support if needed.

CTL0216

&1 cannot be run for the &2 image, &3 path and step number &4.

Cause: SRDF Enginuity Consistency Assist (RDF-ECA) for SRDF/S is enabled. This configuration is not supported.

Action: Change the configuration if needed. Contact the Dell EMC Customer Support if needed.

CTL0218

The devices for the &1 image, &2 path and step number &3 are in ineligible state to perform the control action specified.

Cause: Source devices for snap restore from clone/clone emulation target or VP snap restore from clone target are in invalid state.

Action: Change any configuration details needed. Make sure that the devices are in eligible state for the control action requested.

CTL0223

Not all devices in a range are &1 devices.

Cause: All devices in a range should be &1 devices.

Action: Check devices in a range.

172 Standard Features Messages

CTL0224

Not all devices in a file are &1 devices.

Cause: All devices in a file should be &1 devices.

Action: Check devices in a file.

CTL0225

Device &1(&2), specified in the range of devices is invalid for the control operation.

Cause: All devices in a range should be &3 devices.

Action: Check devices in a range.

CTL0226

Device &1(&2), specified in the device file is invalid for the control operation.

Cause: All devices in a file should be &3 devices.

Action: Check devices in a file.

CTL0227

There are no SNAP pools on the Symmetrix &1.

Cause: Array does not have SNAP pools.

Action: Check the configuration.

CTL0230

The System is not in restricted state. New Snapshots could not be ESTABLISHED.

Cause: The system is not in restricted state.

Action: Please put the system in restricted state and retry the operation.

CTL0231

The status of &1 (generation &2) snapshot from source devices of the step &3, path &4 and &5 image is &6. The timestamp is &7

Cause: Control action processing initiated for the image &5.

Action: Informational message. No action is necessary.

CTL0232

Snapshot is established from the &1 devices of the step. There are &2 devices in the step.

Cause: Additional status for the snapshot is provided.

Action: Informational message. No action is necessary.

CTL0233

&1 snapshot &2 generation &3.

Cause: Additional information for the step is provided.

Action: Informational message. No action is necessary.

CTL0234

Operation is not supported for current code level.

Cause: Operation is supported for microcode 5977 or higher.

Action: Informational message. No action is necessary.

CTL0235

Snapshot has links. Terminate snapshot is not allowed.

Standard Features Messages 173

Cause: Operation is not allowed.

Action: Informational message. No action is necessary.

CTL0236

There are no snapshots for the devices in the &1 image &2 path and step number &3.

Cause: No control operations except Establish are allowed.

Action: Informational message. No action is necessary.

CTL0237

There are no snapshots for the devices in the &1 image &2 path and step number &3 or devices for this step are not paired

Cause: Link target devices is not allowed.

Action: Informational message. No action is necessary.

CTL0238

There are no snapshots for the devices in the &1 image &2 path and step number &3 or devices for this step are already restored.

Cause: Restore operation is not allowed.

Action: Informational message. No action is necessary.

CTL0239

Status of the snapshot for the devices in the &1 image, &2 path and step number &3 is Restore in Progress. Terminate action cannot be run at this time.

Cause: Terminate snapshot is not allowed.

Action: Wait until the snapshot state becomes Restored and then try the Terminate control action.

CTL0240

System ended to a semi-restricted condition.

Cause: The STMSENDSBS command has run and completed successfully. The system is in a semi-restricted state and is available for maintenance activities.

CTL0241

Error found on CALL command Check STARTUPPGM data area for the configured startup program. Correct the error and press R to retry.

Cause: The command STMSTRSBS has ended in error. The program configured in the STARTUPPGM data area is in the wrong format or is not found. The STARTUPPGM must be configured as:

From the 1st position, the program name (up to 10 characters)

From the 11th position, the library name (up to 10 characters long)

CTL0242

Incorrect IP address hostname config found in NETCFNG file.

Cause: The SPLITWA action has ended in error. The NETCNFG file contains incorrect IP address/hostname configuration. Check the SPLITWA_SERVICE configuration in /var/symapi/config/netcnfg.

CTL0243

Warning: User Profile &1 is missing special authority.

Action: For more information on how to configure user profile please refer to the SRDF/TimeFinder Manager for IBM i Product Guide.

174 Standard Features Messages

CTL0244

Set Bias operation failed.

Cause: Control action &1 operation is specified bu the devices listed in the device file are not SRDF devices.

Recovery: Specify SRDF devices.

CTL0245

Error: Could not read data from NETCNFG file.

Cause: The NETCNFG file may be empty.

Recovery: Please check the NETCNFG file and run the CRTNETCNFG command to configure the NETCNFG file.

CTL0246

Path &1 associated with image, but requested feature is not supported.

Cause: This feature is not supported for this microcode or SYMAPI version.

Recovery: Please refer to the Release notes and Product Guide for details on supported features.

Miscellaneous Device Information 175

D

Miscellaneous Device Information Invisible Body Tag

This appendix lists miscellaneous device information such as device s and device pairing compatibility.

Topics:

D910 device support (thin devices)

D910 device support (thin devices) Solutions Enabler provide support for 512 byte block FBA D910-099 as thin devices. This allows users of Dell EMC SRDF/TimeFinder Manager for IBM i to take advantage of automated FAST which is available for arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS.

Requirements and rules for D910 support The rules and requirements for D910 device support are:

For VMAX 10K arrays, and arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977:

D910 device only. Emulation for 2107 devices is not supported.

Thin devices only. Thick or meta devices are not supported.

Thin (bound) gatekeeper devices only.

Server hardware must be POWER6 or higher.

POWER6 model systems firmware must be FW3.5.0 or later.

NOTE: There is no minimum firmware level for POWER7 systems.

Fibre Channel adapters must be Smart IOA Fibre Channel (IOPless) adapters FC5749, FC5774, FC5735, or future IBM i Fibre Channel adapters. Use of IOP-based adapters is not allowed.

IBM i operating system must be version 7.1 or later.

In a VIOS configuration that uses D910 devices with NPIV, the IBM i operating system must be version 7.1 or higher. Allows for pairing between like devices (same emulation type) for SRDF and TimeFinder replication.

Allows for SRDF/TimeFinder Manager support for thin gatekeepers.

When configuring D910 devices, the IBM i operating system must be version 7.1 or later, and the following minimum PTF levels must be applied to IBM i operating system:

7.1 requires a minimum CUM C2122610 (2122) MAY 14, 2012 (NPIV support is excluded)

7.1 requires a minimum of TECH REFRESH 4 (TR4) or CUM C2115710 (2115) May 17, 2012.

512-byte and 520-byte LUNs can reside on the same IBM i partition, and on the same fiber channel adapter.

For disk units formatted with 520 byte sectors, the 520 bytes in each sector consists of 512 bytes of data and 8 bytes of header information. The 8 bytes of header are used by the IBM i licensed internal code to self-identify the data in the page, and during recovery operations to rebuild the directories of permanent extents. A page of data consists of 8 sectors.

For disk units formatted with 512 byte sectors, the IBM i licensed internal code uses nine sectors for each page, since the physical sectors on a disk unit formatted with 512-byte sectors do not have room for an 8 byte header. The 9 sectors of the page consist of eight data sectors and one sector containing the eight headers for those data sectors (along with other control information). Since one of every nine sectors contains header and control information, the capacity usable for the client is approximately 11% smaller than the actual capacity of the logical unit.

176 Miscellaneous Device Information

Only LUN Model Number 099 (protected) is used. Other LUN models such as A01, A81, and 050 are not allowed.

NOTE: Since the LUNs report to the IBM i partition as a protected unit, the operating system will not allow system level mirroring to be used.

D910 device capacities (raw) can range from 3GB up to, but not including, 2TB.

NOTE: Once assigned, LUN capacities must remain constant, which is the case with any other storage attachment to IBM i (both 520 and 512). To change the capacity of a LUN, it must be removed from the configuration, destroyed, and recreated before adding it back into the partition's configuration.

D910 devices can be used in the System ASP, User ASPs and IASPs.

D910 devices can be used as an IBM i load source device. The minimum raw capacity for a D910 load source device is 20GB.

The SCSI FORMAT UNIT command is supported as the Add to ASP action requires that the LUN is zeroed.

D910 devices do not support SCSI Skip Read and Skip Write operations. Instead, IBM i sends aggregated data as several individual SCSI Read or Write commands. The 2107 device does support these operations.

Application impact Only the low level IBM i licensed internal code Storage Management layer of the operating system is directly impacted by the way the disk sectors are formatted. Applications, databases, and programs do not need any modifications to use disks that are formatted with 512-byte sectors.

Performance impact There is some additional data traffic through the I/O Adapter, because each page of data transfers 4608 bytes (9 * 512) instead of 4160 bytes (8 * 520). There is a very small amount of increased usage of the processors when the IBM i licensed internal code builds the header information into the 9th sector of the page.

Troubleshooting 177

E

Troubleshooting Invisible Body Tag

This appendix provides some troubleshooting information for SRDF/TimeFinder Manager. For information on backup, recovery, journaling, and journal management, see IBM documentation on the IBM website.

Topics:

Handling failed or non-reporting hardware resources Error generated when running Discover command within SST Multipath reset Error when running CRTSYMAPI or CRTSYMAPIC commands

Handling failed or non-reporting hardware resources In some cases, non-reporting or failed hardware resources for disk units can interfere with operation of SRDF/TimeFinder Manager. For example, you may be unable to group or pair some devices.

Non-reporting or failed hardware resources can appear on a system after a hardware reconfiguration. You should remove non-reporting or failed hardware resources for disk units before using SRDF/TimeFinder Manager. This can be accomplished after a grouping or pairing error has occurred.

Remove failed and non-reporting hardware resources for disk units as follows:

1. Sign on as the authorized user and issue the IBM i STRSST command to display the System Service Tools (SST) Main menu.

2. From SST, select option 1 to start a service tool.

3. Select option 7 to start the hardware service manager.

4. Select option 4 to list failed and non-reporting hardware resources.

5. Select option 4 next to each failed and non-reporting hardware resource to remove it.

See the IBM documentation for more information.

Error generated when running Discover command within SST On a host running IBM i 7.1 operating system, an error may occur when running the STM Discover command after removing a disk unit from an ASP using SST (rather than DST). To avoid this issue, it is recommended to completely exit the SST environment before running the Discover command.

Multipath reset Multipath Resetting can be used to stop error messaging due to a multipath missing connection. For example, a missing connection occurs when the image is loaded on a different hardware set.

Multipath resetting is done from the IBM SST (Service Tool).

From the IBM console:

1. Sign on to SST.

2. Select option 1. Start a Service Tool.

3. Select option 7, Hardware service manager.

4. Select option 1, Packaging hardware resources.

178 Troubleshooting

5. Select option 9 for the required Disk Unit System. Select option 7, Paths to multiple path disk, to check the status of the paths.

6. Press F14 to reset all the paths.

7. When prompted for confirmation, verify the information and press F10 to reset the paths.

When the reset is completed, a confirmation message is displayed at the end of the screen.

Error when running CRTSYMAPI or CRTSYMAPIC commands The error message Hostname not found may be generated when running the CRTSYMAPI or CRTSYMAPIC command.

To fix this issue, add the host name to the TCP domain information using the CHGTCPDMN command.

SRDF/TimeFinder Manager Extended Features 179

II

SRDF/TimeFinder Manager Extended Features

Part II of this product guide shows how to prepare and configure SRDF/TimeFinder Manager to support IASP use in a clustered environment. It contains the following chapters and appendixes:

Extended Features Introduction

Introduces the extended features, that SRDF/TimeFinder Manager for IBM i provides, to support IBM Independent Auxiliary Storage Pools (IASPs) functionality.

Configuring for IASP Environment

Explains how to prepare and configure SRDF/TimeFinder Manager to support IASP use in a clustered environment.

IASP-Supported Operations

Describes how to use the SRDF/TimeFinder Manager interface to perform IASP-supported operations when working with SRDF and TimeFinder (BCV or Clones) devices configured for multi-node backup and disaster recovery (DR) solutions.

Non-Dell Procedures

Provides guidelines when using IBM-related procedures.

Extended Features Commands Reference

Provides reference information, syntax, and examples for control commands.

Extended Features Messages

Provides reference information about messagesthat may display for the extended features components.

Extended Features Introduction 181

7

Extended Features Introduction

This chapter introduces the extended features of SRDF/TimeFinder Manager for IBM i that support IBM independent ASPs (IASPs) functionality.

Topics:

Extended features description Independent ASP functionality

Extended features description SRDF/TimeFinder Manager for IBM i Extended Features provide support for the IBM independent ASP (IASP) functionality. An IASP is a set of switchable or private auxiliary disk pools (up to 223) that can be brought online or offline on an IBM i host without affecting the rest of the system.

This support, when combined with SRDF/TimeFinder Manager for IBM i, enables you to control SRDF or TimeFinder operations on PowerMax, VMAX All Flash, VMAX3, and VMAX Family arrays attached to IBM i hosts as described in Standard features description. In addition, the extended features can use IASPs to present one or more target devices containing an IASP image to another host for business continuance (BC) processes.

Extended features control operations can be performed two ways:

From the SRDF/TimeFinder Manager menu-driven interface.

From the command line using SRDF/TimeFinder Manager commands and associated IBM i commands.

Independent ASP functionality SRDF/TimeFinder Manager supports two-node, three-node and four-node solutions for performing disaster recovery (DR) and normal operations on a backup node using IASP images in a combined IBM i and PowerMax, VMAX All Flash, VMAX3, and VMAX array environment for business continuance (BC) operations.

SRDF/TimeFinder Manager supports Multipath operations for IASP.

Depending on the disaster recover (DR) solution, IASP operations can be performed on several different IBM i systems. IASP operations are similar for a two and three-node solution.

Two-node solution A two-node solution (Figure 74) can be used for disaster recovery or backup services.

182 Extended Features Introduction

Figure 74 Two-node cluster and two-node DR configuration

Three-node solution In a three-node solution (Figure 75), disaster recovery and backup services are provided simultaneously as follows:

One node serves as primary node.

One node serves as a DR node.

One backup node is configured with remote BCVs or clone devices for backing up an IASP image.

Figure 75 Three-node DR environment

STD

BCV

IBM i Cluster and Device Domain

iASP A

iASP A

Node 1 (IASP A Primary)

Normal operation

Node 2 (IASP A Backup)

TCP/IP

IBM i Cluster and Device Domain

Node 1 (IASP A Primary)

Primary failover to DR node

Node 2 (IASP A Backup assumes the role of Node 1 IASP A Primary)

TCP/IP

R1

RMTBCV

R2

IBM i Cluster and Device Domain

IASP A

IASP A

IASP A

Node 1 (IASP A Primary)

Normal operation

Node 2 (IASP A DR)

Node 3 (IASP A Backup)

SRDF/S for campus or SRDF/A for long distance

TCP/IP

IBM i Cluster and Device Domain

Node 1 (IASP A Primary)

Primary failover to DR node

Node 2 (IASP A DR assumes the role of Node 1 IASP Primary)

Node 3 (IASP A Backup)

TCP/IP

ICO-IMG-000304

Extended Features Introduction 183

Four-node solution A four-node solution (Figure 76) can be used for disaster recovery, high availability (HA), and backup services as follows:

One node serves as a primary node.

One node serves as an HA node.

One node serves as a DR node.

One node serves as a backup node.

Figure 76 Four-node high availability setup

The function of the HA node is to take over for the primary node in case of a failure of the primary node.

NOTE: Throughout this guide, the word backup refers to IASP operations (backup, application testing, and load balancing) that are performed on a backup node.

Some of the operations that you can perform on an IASP image are:

Establish/create Establish SRDF links, establish BCV or clone emulation devices, create a TimeFinder/Clone copy session.

Split/activate Split SRDF links, split BCV or clone emulation devices, or activate a TimeFinder/Clone copy session.

Cancel/terminate Terminate a TimeFinder/Clone copy session or cancel a BCV or clone emulation pairs.

Create logical point-in-time snapshots of images for arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 using TimeFinder SnapVX.

NOTE: TimeFinder SnapVX is supported only on arrays running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977.

Add one or more IOAs to all nodes, or remove one or more IOAs from all nodes participating in the replication solution.

Rebuild the IOA information file for source and target IOAs.

NOTE: IASP Vary on/Vary off operations are performed through IBM commands. IASP-Supported Operations contains greater detail.

R1

IBM i Cluster and Device Domain

iASP A

iASP A

Node 1 (IASP A Primary)

Normal operation

TCP/IP

HA take over ICO-IMG-000305 new

R2

BCV

Node 1B (IASP A HA)

Node 2 (IASP A DR)

Node 3 (IASP A Backup)

Node 1 (IASP A Primary)

TCP/IP Node 1B (IASP A HA)

Node 2 (IASP A DR)

Node 3 (IASP A Backup)

iASP A

Configuring for IASP Environment 185

8

Configuring for IASP Environment Invisible Body Tag

This chapter shows how to prepare and configure SRDF/TimeFinder Manager to support IASP use in a clustered environment.

Topics:

Requirements Configuration procedures Configuring the environment for IASP

Requirements The prerequisites for using an IASP and its image with SRDF/TimeFinder Manager are:

All IBM software is installed and operational. Refer to the Dell EMC SRDF/TimeFinder Manager for IBM i Release Notes for a complete list of requirements.

The latest IBM IASP and cluster PTFs, CUMs, or any other required PTFs have been applied. Refer to the IBM product documentation.

SRDF/TimeFinder Manager is installed on the primary and HA nodes, and SRDF/TimeFinder Manager Client is installed on the Disaster Recovery and backup nodes. The Dell EMC SRDF/TimeFinder Manager for IBM i Release Notes show how to install SRDF/TimeFinder Manager.

SRDF/TimeFinder Manager operations from the DR node require a gatekeeper device configured on the target array and the DR node.

Cluster requirements The following are requirements for clusters:

The cluster must be set up for IASP use according to IBM specifications. Create one or more secondary IASP pools, as necessary.

The backup node must be the last node in the backup order.

If clustering is configured through System i Navigator or IBM systems Director Navigator, the Service Tools Server must be configured and the port name as-sts is unblocked and enabled. Refer to the IBM product documentation for more information.

IOA requirements The following are requirements for IOAs:

When using IASPs, check that no two primary ASP groups share the same IOA. Primary and secondary IASPs are operated on simultaneously.

All devices in each IASP group (or its image) must be on dedicated IOAs.

No devices on the IOA can be part of a User ASP or System ASP (ASPs 1-32).

An IASP image cannot share an IOA with another IASP image.

A gatekeeper device cannot be presented to an IOA that contains an IASP image.

186 Configuring for IASP Environment

Configuration procedures The following sections show how to configure the SRDF/TimeFinder Manager environment to support IASPs in a multi-node environment:

Starting and stopping the server job

Building or rebuilding the IOA file

Making target devices visible to the DR or Backup nodes

Performing initial TimeFinder/SRDF operations

These sections are intended to be used as a reference for the section Configuring the environment for IASP.

Starting and stopping the server job The SRDF/TimeFinder Manager server job, which runs in the EMCCTL subsystem (the default), must be running on all participating nodes. Depending on the request type received, the server job can perform tasks such as:

Adding and removing IOAs

Running a system command on the node

Generating IOA files on all nodes

Updating the IASP configuration files on the nodes

Prior to starting the SRDF/TimeFinder Manager server job, the following conditions are required:

TCP/IP must be active on all nodes.

The appropriate EMCCTL or EMCCTLC library must be in the library list.

See the Dell EMC SRDF/TimeFinder Manager for IBM i Release Notes for more information about adding libraries.

The subsystem job EMCCTL must be started as follows:

STRSBS SBSD(EMCCTL)

NOTE: If another subsystem other than the default EMCCTL is used, start that subsystem.

Starting the server job

To start the server job on each node, enter the following STRSTMSRV command:

STRSTMSRV USERID(*CURRENT) PORTNUM(8000) JOBQ(*LIBL/EMCCTL)

USERID The parameter that submits the job under the user ID that issues the command. The default is *CURRENT.

This is the user ID that was created and is used to run SRDF/TimeFinder Manager.

All other nodes can use the user profile that has *IOSYSCFG, *JOBCTL, and *SERVICE special authority and *USE access to the following *SRVPGM objects in QSYS:

QCSTCTL

QCSTCRG1

QCSTCRG4

For the server job STMSERVER, if the EMCCTL subsystem is not used, check that more than one job is allowed to run in that subsystem.

PORTNUM The port used for TCP/IP communications.

The default port number is 8000. If you use a port number other than 8000, make sure the port number is the same on the primary node, HA node, backup node, and DR node.

JOBQ The subsystem where you want the STRSTMSRV server job to run. The default is *LIBL/EMCCTL.

If you use a different subsystem, enter that job queue name associated with the subsystem, for example:

jobq(*libl/<jobqname>)

Configuring for IASP Environment 187

Stopping the server job

To stop the SRDF/TimeFinder server job, from the command line, enter the ENDSTMSRV command. Supply the port number that was specified in the STRSTMSRV command on the primary, backup, and DR nodes. For example:

ENDSTMSRV PORTNUM(8000)

The default port number is 8000.

Performing initial TimeFinder/SRDF operations When configuring SRDF/TimeFinder Manager, perform initial SRDF or TimeFinder operations, such as Establish/Split, Create/Activate, or Link on the devices when IASP images are present in the configuration.

To perform SRDF or TimeFinder operations on an IASP image:

1. From the command line, enter the CTLACT command and press F4 to prompt.

The EMC SRDF/TimeFinder Ctrl (CTLACT) screen (Figure 77) appears.

Figure 77 Dell EMC SRDF/TimeFinder Ctrl (CTLACT) screen

At this point in the configuration process, the IOA file for the target devices has not been built, and SRDF/TimeFinder Manager cannot perform its validation check. Therefore, make sure target devices are not visible to the DR node or backup node.

2. Enter the following information:

Image Name The name of the image on which to perform a control action.

Path Name The path name associated with the image on which to perform a control action.

Step Number The specific step number for which the control action is to be initiated.

Control Action The SRDF or TimeFinder control action to be performed.

3. After the IASP image is synchronized, created, or for snapshots, established:

a. Vary off the source devices.

b. Re-enter the CTLACT command with the same IASP name and image name.

c. Set Control Action to SPLIT or ACTIVATE, or for SnapVX, LINK.

d. Set Split/Suspend Mode to MAINTENANCE.

See CTLACT for more information on the CTLACT command. See Controlling TimeFinder and Controlling SRDF for more information on Establish/Create, Split/Activate/Link and other SRDF and TimeFinder control operations.

188 Configuring for IASP Environment

Once SRDF/TimeFinder Manager is configured for IASP use, you can use the Work with Associated Paths screen (3.) to perform ESTABLISH/CREATE and SPLIT/ACTIVATE and SnapVX operations.

Configuring an IASP image Before using IASPs in an SRDF/TimeFinder Manager environment, you must configure one or more IASP images as needed for the replication solution.

NOTE: To configure an IASP image, a valid copy of the IASP image must first be presented to the selected target node. Use the CTLACT command to do this. For SRDF, BCV, or CLONE type of step, carry out a Split/Activate action for this image to be visible at the target side. For SnapVX type of step, carry out a Link action on the image. See Performing initial TimeFinder/SRDF operations for using the CTLACT command. Once this is done a valid image is present at the target side and the IOA's can be presented to this node using the ADDIOA command described in Making target devices visible to the DR or Backup nodes.

To configure an IASP image:

1. Select option 1. Work with Images from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu.

The Symmetrix Configuration by Image screen appears.

2. Select option 2. Work with paths from the Symmetrix Configuration by Image screen.

3. The Work with Associated Paths screen appears.

4. Enter 16 in the Opt column of the step associated with the path.

The Configure IASP Session screen (Figure 78) appears.

5. Enter the following information:

Target Node The name of the target node for this step. The node name entered must be part of the cluster that is configured on this system. If this is not the case, a message appears indicating that the node cannot be found.

NOTE: The cluster node name can be found by running DSPCLUINF command. This command also displays the node IP address.

Port Number The TCP/IP port that the SRDF/TimeFinder Manager server job uses for communications. The default is 8000.

Figure 78 Configure IASP Session screen with configuration detail

NOTE: SRDF/TimeFinder Manager checks the validity of the information supplied and then sends the information to all nodes currently configured. If the node name is not part of the configured cluster, a message appears at the bottom of the screen indicating that the node name is not part of the configured cluster on this system.

Configuring for IASP Environment 189

6. Repeat steps two through five for each IASP image that you plan to use for SRDF/TimeFinder Manager.

NOTE: If the server job on any node is unavailable at the time of the request, the IASP configuration process fails. If this occurs, the IASPS file on the primary node and the IASPS file on other nodes are not updated.

Allowing multiple TimeFinder IASP copies to share the same IOAs on a single host

To allow for this feature, each IASP copy needs to be presented to the target node making it possible to control each copy individually.

From the Work with Associated Path screen use Option 16, or use the IASPCTL command with CONFIG control action to create an entry that is written to the configuration file for each copy. A CONFIG action must be run for each copy on the host, and during the configuration process the other copies that share the IOA must be offline.

NOTE: When the IOA is shared between multiple TimeFinder copies, or when R2 and backup devices are sharing IOA's, be aware that if the IOA is enabled for one copy it is active at the same time for the other copy. For example, when trying to terminate a Clone session for one copy the IOA needs to be inactive. If needed, use the CTLACT command to terminate one copy while keeping the IOA active.

NOTE: IASP commands should be the primary commands used after initial configuration as it has all the checks and balances. You could have Clone active. If you have another Clone you want to present, you remove the IOA, then use SYMACCESS to present the second set of Clone devices. Also, only one copy can be presented at any time, so make sure that access to the devices is only to one set of devices. You can do this with the CLI command SYMACCESS.

Building or rebuilding the IOA file When the IASP configuration is run, a rebuild action is automatically performed. As each IASP session is configured, the IOA files are also copied to the appropriate nodes.

However, IOA files must be current. SRDF/TimeFinder Manager depends on information stored in the files such as error checking or IOA status, prior to performing any operations against an IASP image. As a result, if the IOA files need to be reconfigured, the REBUILDIOA operation may need to be run as a separate action.

CAUTION: Failure to rebuild and maintain current IOA files may result in critical data loss and/or system crash.

To rebuild the IOA file, use the IASPCTL command. In the following example, the IASPCTL command adds an entry into the ISRCIOA file, and rebuilds the IOA file for the IASP image (PIASP2) associated with a path name of REMOTEBCV.

IASPCTL IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(1) ACTION(REBUILDIOA) NODENAME(NODE1) IASPCTL IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(2) ACTION(REBUILDIOA) NODENAME(NODE2)

NOTE: The REBUILDIOA control action can also be run from the Dell EMC Independent ASP Control (IASPCTL) screen. See Executing IASP control actions on primary node for more information on executing actions from this screen.

Making target devices visible to the DR or Backup nodes There are many ways to make target devices visible to the backup node, for example:

With the storage devices online, after the Split operation is complete, connect the cables to the backup node.

Use the ADDRMVIOA command to add I/O resources. See ADDRMVIOA.

Do not present target devices until the first Split operation completes. After making the target devices visible to the DR or backup node, rebuild the IOA file for the target devices. Building or rebuilding the IOA file describes this procedure.

Configuring the environment for IASP Configuring the SRDF/TimeFinder Manager environment to support IASP use in a multi-node environment, requires using a combination of IBM commands, SRDF/TimeFinder Manager commands, and screen options.

The following sections show how to configure the IASP environment (SRDF/S or SRDF/A with remote BCVs):

Prepare cluster and IASP nodes

Start the server

Configure paths

Configure an IASP session

190 Configuring for IASP Environment

Populate the IOAs for each node in the cluster

Post-configuration considerations

NOTE: In the IASP View by ASP screen, IOAs that are removed from an IASP configuration display a Not Active status, and IOAs that are added to an IASP configuration display an Active status. When there are secondary IASPs included in the configuration and the ADDRMVIOA command is being used, the primary and all secondary IASPs must be specified with the corresponding IOAs in the command. See ADDRMVIOA for more details.

Prepare cluster and IASP nodes After creating all cluster nodes, start the cluster node on each node as follows:

STRCLUNOD CLUSTER(CLUSTERNAME) NODE(NODENAME)

1. Create IASP device domains.

2. On the DR node (R2) and backup node (RMTBCV):

a. Using the ADDRMVIOA command, make sure the IASP IOAs for the DR and backup nodes are removed. See ADDRMVIOA for more information on the ADDRMVIOA command.

b. Make sure the IOAs are active on the primary node.

Start the server 1. On the primary node (R1) and HA node, add EMCCTL to the library list.

2. On the DR and backup (RMTBCV) nodes, add EMCCTLC to the library list.

3. Make sure TCP/IP is active on all nodes.

4. Start the subsystem job EMCCTL, or start another available subsystem. If you use a subsystem other than the default EMCCTL, start that subsystem first:

STRSBS SBSD(EMCCTL)

5. Start the SRDF/TimeFinder Manager server job (STRSTMSRV) on all nodes in the cluster:

EMCCTL/STRSTMSRV USERID(*CURRENT) PORTNUM(8000) JOBQ(*LIBL/EMCCTL) EMCCTLC/STRSTMSRV USERID(*CURRENT) PORTNUM(8000) JOBQ(*LIBL/EMCCTL)

If you started a different subsystem job in step 4, enter the jobq name associated with the subsystem, for example:

jobq(*libl/<jobq name>)

Starting and stopping the server job shows how to start the SRDF/TimeFinder Manager server job using STRSTMSRV.

Configure paths 1. Call the following program:

CALL PGM(EMCCTL/CRTSYMAPI)

2. From the EMCCTL main menu, start SRDF/TimeFinder Manager:

GO MAINCTL

Dell EMC SRDF/TimeFinder Manager for IBM i main menu shows how to access the SRDF/TimeFinder Manager Main menu.

3. Select option 1. Work with images.

The Symmetrix Configuration by Image screen appears.

4. Scroll down to the IASP image name and enter 8 in the Opt column for that image.

The Paths not Associated with the Image screen appears.

5. For a three-node configuration, enter 1 in the Opt column of the REMOTEBCV /RDF1/BCV1 path, and press Enter. For all other configurations, enter 1 in the Opt column of the appropriate path, and press Enter.

The Symmetrix Configuration by Image screen appears.

See Configuration by Image screen for more information on accessing the Symmetrix Configuration by Image screen.

6. Enter 2 in the Opt column of the IASP image.

Configuring for IASP Environment 191

The Work with Associated Paths screen appears.

NOTE: SRDF devices are automatically associated.

7. Enter 6 in the Opt column of the BCV1 step.

The remote BCVs are associated with the R2 devices.

8. From the command line, use CTLACT to establish the BCVs and synchronize the RDF devices as needed. Performing initial TimeFinder/SRDF operations contains greater detail.

9. Make sure that IOA is active.

10. Split RDF devices and remote BCVs using CTLACT. Split BCV pairs: Maintenance shows how to carry out a maintenance split.

Configure an IASP session To configure the IASP session:

1. For the RDF1 step, select option 1. Work with Images from the Dell EMC SRDF/TimeFinder Manager for IBM i main menu to display the Symmetrix Configuration by Image.

2. Select option 2. Work with paths from the Symmetrix Configuration by Image screen to display the Work with Associated Paths screen.

3. From the Work with Associated Paths screen, enter 16 in the Opt column of the step associated with the path.

The Configure IASP Session screen (Figure 79) appears.

Figure 79 Configure IASP Session screen

4. Enter the appropriate information for the DR node and the server port number.

NOTE: The node name entered must be part of the cluster that is configured on this system. If this is not the case, a message appears indicating that the node cannot be found.

5. For the BCV1 step, repeat steps one through four, and enter the appropriate information for the backup node in the Configure IASP Session screen.

The above steps populate the EMCCTLC/IASPs physical file on the backup node. Configuring an IASP image describes this procedure.

6. On the primary node, enter:

192 Configuring for IASP Environment

DSPPFM EMCCTL/IASPS

7. On the DR and backup nodes, enter:

DSPPFM EMCCTLC/IASPS

The Display Physical File Member screen appears. Steps six and seven verify that the IASP configuration file has been successfully propagated to the appropriate nodes.

See Displaying contents of a physical file on each node for more information.

The CONFIG action automatically performs a REBUILDIOA operation. As each IASP session is configured, the IOA files are also copied to the appropriate nodes.

However, IOA files must be current. SRDF/TimeFinder Manager depends on information stored in the files such as error checking or IOA status, prior to performing any operations against an IASP image. As a result, if the IOA files need to be reconfigured, the REBUILDIOA operation may need to be run as a separate action.

Populate the IOAs for each node in the cluster These configuration steps are used only when issuing a REBUILIOA as a separate operation from a CONFIG operation.

The IOAs for each node must be presented to the system. The primary node IOAs are presented first followed by the backup and DR nodes.

Perform the following steps on the primary node:

1. Issue the following command for SRDF setup:

EMCCTL/IASPCTL IMAGENAME(IASPNAME)PATHNAME(REMOTEBCV) STEPNUM(1) ACTION(REBUILDIOA)NODENAME(PRIMARYNODENAME)

NOTE: STEPNUM(1) denotes the SRDF step.

See Building or rebuilding the IOA file for an example command to rebuild the IOA file.

NOTE: To rebuild primary node IOA file, you can also issue the IASPCTL which displays the EMC Independent ASP Control (IASPCTL) screen. See Executing IASP control actions on primary node for more information on using this screen.

2. Ensure that all pairs in the path are in a split state.

3. Perform the following steps on the DR node:

a. Add the IOA to the DR node using the ADDRMVIOA command.

b. For SRDF setup, issue the following commands:

EMCCTLC/IASPCTLC IMAGENAME(IASPNAME) PATHNAME(REMOTEBCV) STEPNUM(1) ACTION(REBUILDIOA)NODENAME(DRNODENAME)

4. Perform the following steps on the backup node:

a. Add the IOA to the backup node using the ADDRMVIOA command.

b. When rebuilding the IOA in general, the IOAs only need to be added to the node where changes have occurred and of course split. They do not have to be varied on. They can remain added and varied on after the rebuild. You can decide based on what is correct for your system.

c. For BCV setup, issue the following commands:

EMCCTLC/IASPCTLC IMAGENAME(IASPNAME) PATHNAME(REMOTEBCV) STEPNUM(2)ACTION(REBUILDIOA)NODENAME(BACKUPNODENAME)

NOTE: STEPNUM(2) denotes the BCV step.

5. Remove the IOA from the backup node using the ADDRMVIOA command. See ADDRMVIOA for more information.

6. Verify the IOA location information on all nodes by viewing the physical file (ISRCIOA file) in the EMCCTL and EMCCTLC libraries.

7. On the primary node, verify the IASP setup from SRDF/TimeFinder Manager as follows:

a. From the Work with Associated Paths screen, run the IASP view option against the step of the IASP.

b. View and verify the IASP information from the IASP view by ASP screen.

8. Add the IOA back to the primary node using the IASPCTL command, and then vary on the IASP using the IBM commands.

Configuring for IASP Environment 193

Post-configuration considerations After SRDF/TimeFinder Manager is configured for IASP support, make a list of the hardware configurations, such as partitions and IOA bus and slot location information, for all nodes. If a disaster occurs, having this information readily accessible makes the DR go more smoothly.

IASP-Supported Operations 195

9

IASP-Supported Operations Invisible Body Tag

This chapter shows how to use the SRDF/TimeFinder Manager interface to perform IASP-supported operations when working with SRDF and TimeFinder (BCV, Clones, or SnapVX) devices configured for multi-node backup and disaster recovery (DR) solutions.

Topics:

IASP-supported operations SRDF/TimeFinder Manager IASP-specific menu options Executing IASP control actions Automated operations

NOTE: This chapter covers the use of IASP in the SRDF/TimeFinder Manager environment only. It does not provide details on how to perform IBM-specific operations, except where necessary. For information on IASPs, see the IBM documentation.

IASP-supported operations The following sections show how to perform operations, such as disaster recovery (planned downtime and unplanned DR) and backup, in SRDF/TimeFinder Manager configured for IASP support:

Three-node planned failover (downtime) operations on the primary node. See Three-node planned failover (DR) and recovery solution.

Unplanned disaster recovery. See Three-node failover and recovery (unplanned) solution.

Routine backup operation. See Backup operations.

Switch to high availability node. See Managing a four-node solution with a high availability node.

See Configuring the environment for IASP to ensure all cluster requirements are met. Many operations, such as failover and recovery processes, use a combination of commands (SRDF/TimeFinder Manager, Operations Navigator, or IBM i) and System Service Tools (SST) functions.

The DR and recovery operations detailed below require IASP images to be varied on or off. See Varying on and varying off IASP images locally.

Three-node planned failover (DR) and recovery solution This section shows how to recover from a planned primary node downtime in a three-node environment. The following rules apply to this recovery solution:

The primary node is where the IASP source devices (R1 devices) reside.

The DR node is the node that takes over when the primary node fails or is taken offline.

The backup node acts as the secondary owner for an IASP image. This node is configured with remote BCV, Clones, or SnapVX for backing up an IASP image.

CAUTION: All tasks for a planned downtime must be completed as defined by the chosen failover process. Any deviation from this process may result in a system crash or possible data loss.

To do a three-node planned recovery:

1. End IASP operations using the internal procedures established at your site.

2. Vary off the source IASP image, using the IBM VRYCFG command issued from a source host.

3. Remove the source IOA from the primary node using the IASPCTL command. See IASPCTL.

4. R2 devices should not be split or available on the DR node. They should be synchronized.

5. Do one of the following:

196 IASP-Supported Operations

If the primary node is available, from the primary node, perform a failover using the SRDFDRCTL command with the Establish option.

If the primary node is not available, run the CTLACTTGT command on the DR node and perform a failover with the ESTABLISH option to the target.

NOTE: Use the ESTABLISH/RESTORE option only with dynamic SRDF. This performs a dynamic directional swap of the replication and establish the R1 and R2 devices.

See SRDFDRCTL and CTLACTTGT.

6. Add the IOAs for target devices to the DR node, using SRDF/TimeFinder Manager.

See IASPCTL (if the primary node is available) or IASPCTLC (if the primary node is down).

7. Vary on the IASP image on the DR node, using the IBM VRYCFG command from the DR node.

8. Verify the data, using IBM commands.

Refer to the IBM documentation for more information.

When the primary node is ready to resume normal operations:

1. Vary off the IASP image on the DR node, using the IBM VRYCFG command from the DR node.

2. Remove IOAs from the DR node.

See Adding or removing IOAs.

3. The R2 devices should not be split or available on the DR node. They should be synchronized.

4. Do one of the following:

If the primary node is available, and it is a dynamic SRDF configuration, on the primary node, run the SRDFDRCTL command using the FAILOVER control action with the Establish option.

See SRDFDRCTL.

If the primary node is available, and it is not a dynamic SRDF configuration, perform a FAILBACK.

If the primary node is not available, and it is a dynamic SRDF configuration, on the DR node, run the CTLACTTGT command with the FAILOVER control action and the ESTABLISH option. Otherwise, perform a FAILBACK.

The CTLACTTGT command with the FAILOVER/FAILBACK control action performs all the steps listed as action items when the primary node is down.

See CTLACTTGT.

5. Check status of the cluster. See the IBM documentation for more information.

6. Add IOAs for the source devices on the primary node.

See IASPCTL, if primary node is available, and IASPCTLC, if the primary node is down.

7. Vary on the source IASP image on the primary node, using the IBM VRYCFG command.

Three-node failover and recovery (unplanned) solution This section shows how to recover from a primary node failure in a three-node environment. The following rules apply to this recovery scenario:

The primary node is where the IASP source devices (R1s) reside.

The DR node is the node that takes over when the primary node fails or is taken offline.

The backup node acts as the secondary owner for an IASP image. This node is configured with remote BCV, Clones, or SnapVX for backing up an IASP image.

To recover from a primary node failure in a three-node environment:

1. If the primary node is down:

a. Run the CTLACTTGT command on the DR node using the FAILOVER control action with the Establish option.

b. If the SRDF links are not available, run the CTLACTTGT command on the DR node with the FAILOVER *NO option.

NOTE: Use the Establish/Restore option only with dynamic SRDF. Establish performs a dynamic directional swap of the replication and establishes the R1 and R2 devices. For static SRDF configurations, use FAILOVER with *NO.

See CTLACTTGT.

2. Add IOA for target devices on the DR node, using the IASPCTLC command. See IASPCTLC.

IASP-Supported Operations 197

3. Vary on the IASP image on the DR node using the IBM VRYCFG command.

4. Verify the data, using IBM commands.

See the IBM documentation.

To resume normal operations:

1. Vary off the target IASP image on the DR node using the IBM VRYCFG command.

2. Remove the target IOA from the DR node using the IASPCTLC command. See IASPCTLC.

3. On the DR node, with dynamic SRDF, run the CTLACTTGT command with the FAILOVER control action and the ESTABLISH option.

On the DR node, without dynamic SRDF, perform a FAILBACK.

If a FAILOVER with option *NO was performed in step 1 , run the CTLACTTGT command with FAILBACK. See CTLACTTGT.

4. Verify the primary node is available to resume normal operations. See the IBM documentation.

5. If not already done, add EMCCTL to the library list, and run the STRSTMSRV command to start the SRDF/TimeFinder Manager Server. See STRSTMSRV.

6. Make sure the source IASP devices are available to the host. If not, add IOAs for the source devices to the primary node. See IASPCTL.

7. Check status of the cluster. See the IBM documentation for more information.

8. Vary on the source IASP on the primary node, using the IBM VRYCFG command.

9. Verify the data.

See the IBM documentation for more information.

Backup operations This section shows how to do routine backup operations in a three-node IASP environment.

The following rules apply to backup operations:

The primary node is where the IASP source devices (R1s) reside.

The DR node is the node that takes over when the primary node fails or is taken offline.

The backup node acts as the secondary owner for an IASP image. This node is configured with remote BCV, Clones, or SnapVX for backing up an IASP image.

If necessary, perform an IPL of the host. You do not need to restore any IASP data updates from this copy.

Managing remote TimeFinder devices from the DR for backup operations

When planned or unplanned DR events occur, and the primary node is unavailable, use the CTLACTTGT command on the DR node to control remote TimeFinder devices on the backup node.

Do the following (starting at either step 1 or 2), for backup operations, depending upon the availability of the primary node:

1. On the DR node, split the remote BCV devices to make them available for backup:

If the IASP is varied off, use the CTLACTTGT command to perform a maintenance split.

If IASP is varied on use the CTLACTTGT command with the CHG_ASP_ACT quiesce option for the split. This option uses the Change ASP Activity CL command (CHGASPACT) to quiesce IASP data for the split. See CTLACTTGT for more information.

2. Vary on the source IASP image if it is still varied off.

3. Add IOA for target (remote BCV) devices to the backup node. See Adding or removing IOAs for more information.

4. Vary on the IASP copy for the backup node.

5. Run the backup on the IASP data using the procedure established by your company.

6. Vary off the IASP image for the backup node using the IBM VRYCFG command issued from the backup node.

7. Remove IOA for target (remote BCV) devices from the backup node. See Adding or removing IOAs for more information.

8. Establish the remote BCV devices.

9. IPL the backup node in preparation for the next backup operation.

198 IASP-Supported Operations

This step is needed only if an error occurs when varying on the IASP copy of the backup node.

Managing remote SnapVX devices from the DR node for backup operations

When planned or unplanned DR events occur, and the primary node is unavailable, use the CTLACTTGT command on the DR node to control Remote SnapVX devices on the backup node.

Do the following (starting at either step one or two), for backup operations, depending upon the availability of the primary node:

1. Establish a snapshot on the DR node for backup availability:

If the IASP is varied off, use the CTLACTTGT command to perform a consistent establish of a snapshot.

If IASP is varied on, use the CTLACTTGT command with the CHG_ASP_ACT quiesce option for the establish. This option uses the Change ASP activity CL command (CHGASPACT) to quiesce IASP data for the establish. See CTLACTTGT for more information.

2. When the snapshot is established use CTLACTTGT on the DR node for the LINK snapshot operation. This makes the data available on the devices attached to the target node for the selected snapshot. To link a different snapshot to the target devices, use the LINK/RELINK action.

NOTE: If creating multiple snapshots over a period of time, use the link command to present each snapshot to the target node and create backups of all snapshots.

3. Add IOA for target (remote SnapVX) devices to the backup node. See Adding or removing IOAs for more information.

4. Vary on the IASP copy for the backup node.

5. Run the backup on the IASP data using the procedure established by your company.

6. Vary off the IASP image for the backup node using the IBM VRYCFG command issued from the backup node.

7. Remove IOA for target (remote SnapVX) from the backup node. See Adding or removing IOAs for more information.

8. To link a different snapshot to the target devices, use the LINK/RELINK action.

Restore operations This section shows how to do routine restore operations in a three-node IASP environment. The following rules apply to restore operations:

The primary node is where the IASP source devices (R1s) reside.

The DR node is the node that takes over when the primary node fails or is taken offline.

The backup node acts as the secondary owner for an IASP image. This node is configured with remote BCV, Clones, or SnapVX for backing up an IASP image. If necessary, perform an IPL of the host.

Managing remote SnapVX devices from the backup node for restore operations

1. On the primary node use the IASPCTL command or menu option to perform a consistent Establish to create a snapshot for step two (SVX1).

SRDF/TimeFinder Manager uses the Change ASP Activity CL command (CHGASPACT) to quiesce IASP data for the establish snapshot operation if the IASP is active, otherwise it uses maintenance. See IASPCTL for more information.

2. When the snapshot is established, use the IASPCTL command or menu option to link the snapshot using Copy Mode. This makes the data available on the target devices for the selected snapshot (SVX1 step two).

3. Add IOA for target devices (SVX1 step two) to the backup node. See Adding or removing IOAs for more information.

4. Vary on the IASP copy on the backup node (SVX1 step two).

5. Create some data on the IASP copy, this data is restored and available later on the R1 devices of the IASP copy.

6. Vary off the IASP copy for the backup node using the IBM VRYCFG command.

7. Remove IOA for the target devices (SVX1 step two) from the backup node. See Adding or removing IOAs for more information.

8. Create a dummy path named <DUMMY>. You can choose the name for this path.

For a remote snapshot, the path should be /RDF1/SVX1/SVX2 for recovery purposes only.

IASP-Supported Operations 199

9. Pair step three (SVX2) with R2 devices (step one - RDF1 for a remote snapshot) using a file. See SnapVX device pairing for more information.

NOTE: It will be the opposite pairings of, in case of remote, step two (SVX1) . For example, if step two (SVX1) was device 0001 to 0002, step three (SVX2) would be 0002 to 0001.

10. On the primary node use the CTLACT command to perform a consistent Establish to create a snapshot for step three (SVX2).

11. On the primary node use the IASPCTL command to split step one (RDF1 is for a remote snapshot).

12. When the snapshot (SVX2) is established, use the CTLACT command to link the snapshot with Copy mode to the target devices.

NOTE: SVX2 is step three for a remote snapshot.

13. When the snapshot (SVX2) is 100% copied, use the CTLACT command to restore step two.

14. When the restore is fully copied, use the CTLACT command to unlink the snapshot from the target devices.

NOTE: SVX2 is step three for a remote snapshot.

NOTE: Steps 15 -17 are needed only when the user decides to verify that the data was restored to the R2 devices, in preparation for restoring this data to the primary node devices.

15. Add IOA for target R2 devices (RDF1 step 1) to the DR node. See Adding or removing IOAs for more information.

16. Vary on the IASP copy on the DR node for step one (RDF1). When satisfied the data is correct for restore, vary off the IASP copy on the DR node.

17. Remove IOA for target R2 devices (RDF1 step one) from the DR node. See Adding or removing IOAs for more information.

18. On the primary node use the SRDFDRCTL command to execute a failback for step one (RDF1). See SRDFDRCTL for more information.

19. Add IOA for R1 devices (RDF1 step one) to the primary node. See Adding or removing IOAs for more information.

20. Vary on the IASP copy on the primary node for step one (RDF1) and verify data is restored.

Managing a four-node solution with a high availability node This section shows how to switch to the high availability node.

Steps one through five need to be done only at initial setup or after a configuration change.

To switch to the high availability node:

1. On the primary node, vary off the IASP using the IBM VRYCFG command.

If the primary node has failed, go to step five. Otherwise, proceed to step two.

2. Remove the source IOA from the primary node using the IASPCTL command.

See IASPCTL for more information.

3. Start the STM servers on the primary and HA nodes in the configuration.

See STRSTMSRV for more information.

4. On the primary node, run the IASPCTLHA command using the control action CFGHAIASP.

See IASPCTLHA for more information.

5. End the STM server on the primary node using the ENDSTMSRV command.

See ENDSTMSRV for more information.

6. Using DST/SST (service tools), make sure that the IOAs are added to the HA machine and they are reporting in. If they are not added or reporting, use the ADDRMVIOA command for initial setup to add the IOAs to the HA machine. After the initial setup use the IASPCTL command to add IOAs.

7. On the HA node, run the IASPCTLHA command with the control action SWHAIASP.

Make sure the STM server is up and running on the HA, DR, and backup nodes.

8. On the HA node, vary on the IASP using the IBM VRYCFG command.

Continue normal operations on the HA node.

200 IASP-Supported Operations

To switch back to the primary node from the HA node:

1. On the HA node, vary off the IASP using the IBM VRYCFG command.

2. Remove the source IOA from the HA node using the IASPCTL command.

See IASPCTL for more information.

3. Start the STM server on the primary and HA node.

See STRSTMSRV for more information.

4. On the HA node, run the IASPCTLHA command using the control action CFGHAIASP. Use the primary node as the target node.

5. End the STM server on the HA node using the ENDSTMSRV command.

See ENDSTMSRV for more information.

6. Add the source IOA to the primary node using the IASPCTL or ADDRMVIOA command. See ADDRMVIOA or IASPCTL for more information.

7. On the primary node, run the IASPCTLHA command with the control action SWHAIASP.

See IASPCTLHA for more information.

Make sure the STM server is up and running on the primary, DR, and backup nodes.

8. On the primary node, vary on the IASP using the IBM VRYCFG command.

9. Continue normal operations on the primary node.

Source to source processing for IASPs SRDF/TimeFinder Manager for IBM i 10.0.0 and later contains a facility for updating an IASP from a SnapVX snapshot without using a RESTORE operation. The architecture of such a configuration is like this:

Figure 80 Source to source processing for IASPs

Operational overview

The overall operation of the source to source configuration is:

IASP-Supported Operations 201

1. Applications on the PROD-Node create and process data on IASP1.

2. A point-in-time snapshot of IASP1 is taken using the path LOCALSVX.

3. The snapshot is linked and varied online to the SAVE-Node.

4. Applications on the SAVE-Node copies process the data on this IASP1. The applications create modified data that needs porting back to PROD-Node.

5. The modified data on the IASP1 snapshot is copied to IASP2.

6. A point-in-time snapshot of IASP2 is taken using the path LOCALSVX.

7. The snapshot is linked and varied online to the PROD-Node.

8. The PROD-Node can now access the modified data on IASP2 snapshot and integrate that with the data on IASP1.

Configuring IASP1 on PROD-Node

This section summarizes the steps to configure IASP1 on the PROD-Node. Configuring an IASP image contains details of how to configure an IASP image.

1. On the PROD-Node:

1. Use ADDRMVIOA to ADDIOA for IASP1 to PROD-Node.

2. Establish the snapshot for IASP1 using path LOCALSVX.

3. Link the IASP1 snapshot using path LOCALSVX.

2. On the SAVE-Node:

Use ADDRMVIOA to ADDIOA for IASP1 to SAVE-Node.

3. On the PROD-Node:

1. On the Work with Associated Path screen, use Option 16 to point IASP1 with path LOCALSVX at SAVE-NODE.

2. On the Work with Associated Path screen, use Option 17 with path LOCALSVX to remove the IOA for IASP1 from the SAVE-Node.

3. With the IASPCTL command, use REMOVEIOA to remove the IOA associated with the LOCALSVX path for IASP1 on the PROD-Node.

Configuring IASP2 on SAVE-Node

This section summarizes the steps to configure IASP2 on the SAVE-Node.

1. On the SAVE-Node:

1. Use ADDRMVIOA to ADDIOA for IASP2 to SAVE-Node.

2. Establish the snapshot for IASP2 using path LOCALSVX.

3. Link the IASP2 snapshot using path LOCALSVX.

2. On the PROD-Node:

Use ADDRMVIOA to ADDIOA for IASP2 to PROD-Node.

3. On the SAVE-Node:

1. On the Work with Associated Path screen, use Option 16 to point IASP2 with path LOCALSVX at PROD-NODE.

2. On the Work with Associated Path screen, use Option 17 with path LOCALSVX to remove the IOA for IASP2 from the PROD-Node.

3. With the IASPCTL command, use REMOVEIOA to remove the IOA associated with the LOCALSVX path for IASP2 on the SAVE-Node.

Processing cycle

Once the two IASPs are configured the daily processing cycle is:

1. On the PROD-Node, enter:

IASPCTL IMAGENAME(IASP1) PATHNAME(LOCALSVX) STEPNUM(1) ACTION(ADDIOA) NODENAME(PROD-Node)

2. Vary IASP1 online on the PROD-Node.

202 IASP-Supported Operations

Leave it online for the entire production cycle. The applications on PROD-Node can now create and process data on IASP1.

3. Establish a snapshot of IASP1 with path LOCALSVX using SnapVX.

4. Link the snapshot of IASP1 with path LOCALSVX.

5. Use Option 17 on the Work with Associated Paths screen to add an IOA to the SAVE-Node.

6. On the SAVE-Node:

a. Vary IASP1 online.

b. Enter:

IASPCTL IMAGENAME(IASP2) PATHNAME(LOCALSVX) STEPNUM(1) ACTION(ADDIOA) NODENAME(SAVE-Node) c. Vary IASP2 online.

Leave it onlne for the entire production cycle. The application on SAVE-Node can now process the data on IASP2.

d. Establish a snapshot of IASP2 with path LOCALSVX using SnapVX.

e. Use Option 17 on the Work with Associate Paths screen to add an IOA to the PROD-Node.

f. Vary IASP1 offline.

7. On the PROD-Node:

a. Use Option 18 on the Work with Associated Paths screen to remove the IOA for IASP1 with path LOCALSVX.

b. Use Option 21 on the Work with Associated Paths screen to unlink the snapshot for IASP1.

c. Vary IASP2 online and process its data.

d. Once data processing is complete, vary IASP2 offline.

8. On the SAVE_Node:

a. Use Option 18 on the Work with Associated Paths screen to remove the IOA for IASP2 with path LOCALSVX from the PROD-Node.

b. Use Option 21 on the Work with Associated Paths screen to unlink the snapshot for IASP2.

SRDF/TimeFinder Manager IASP-specific menu options The following sections describe the menu options you use when working with IASP images and SRDF and TimeFinder devices.

Establish/create, split/activate, link/relink, and cancel/terminate operations.

Adding or removing IOAs

Varying on and varying off IASP images locally

Varying on and varying off IASP images remotely

Displaying an IASP configuration by ASP

Removing image information

Establish/create, split/activate, link/relink, and cancel/terminate operations With SRDF/TimeFinder Manager, you can perform Establish/Create, Split/Activate, Link/Relink, work with snapshots, change Link Mode, Restore, and Cancel/Terminate operations on devices the following ways:

Executing the IASPCTL command from the command line or through the Control Menu. See Executing IASP control actions and IASPCTL for more information.

From the Work with Associated Paths screen screen, as described in the following sections.

An IASP pair always consists of a source device and its target device. After an IASP image is configured and initialized, the target device contains no data.

IASP-Supported Operations 203

After an Establish/Create operation is performed on an IASP pair, the IASP target device is synchronized with the IASP source device. The target device contains an identical copy of the data from the source device, which is valid until a Split or Activate process begins. The data on the target device can be accessed after the Split or Activate operation completes successfully.

NOTE: With SnapVX a target device can only be used after Link command is performed. A Link command with the Copy option copies the data to the target devices. Links can be created in Copy mode for a permanent copy on the target device, or in NoCopy mode for temporary use. With NoCopy mode, an Unlink command removes the data from the target device.

Establish/create

To perform an Establish/Create operation from a screen, from the Work with Associated Paths screen, enter 14 in the Opt column of the step for the associated IASP image.

The Establish Operations screen appears for you to complete the operation.

The establish operation for SnapVX creates and activates a snapshot of the selected image, path and step. When the source IASP is online a CHG_ASP_ACT is done to flush the memory to the disks.

CAUTION: In normal operations, make sure the server job is running on all nodes before you issue an Establish or Create command. Failure to do so may cause unpredictable results.

Split/activate

To perform a Split/Activate operation, from the Work with Associated Paths screen, type 15 (Split/Activate) next to the step of the associated IASP image.

Link/Relink

From the Work with Associated Paths screen, enter 20 in the Opt column of the step for the associated IASP image.

The List of Snapshots screen appears for you to complete the operation. There you can select the snapshot that you want to select for the Link/Relink operation.

NOTE: Link/relink operations can also be performed from the Work with Shapshots screen. Enter 1 in the Opt column of the desired snapshot.

Unlink

From the Work with Associated Paths screen, enter 21 in the Opt column of the step for the associated IASP image.

This removes a link that exists to the target devices. To complete the operation the target IOA's connected to these devices need to removed first.

Work with snapshots

From the Work with Associated Paths screen, enter 22 in the Opt column of the step for the associated IASP image.

The Work with Snapshots screen appears for selecting the following available options for the snapshots listed: 1 (Link/Relink), 2 (Restore), 3 (Set TTL), 5 (Show details), 7 (Rename), and 8 (Terminate).

Change Link Mode

The change link mode changes the link mode of the linked snapshot to Copy or NoCopy. In Copy mode, the data is copied to the target devices, and when the snapshot is unlinked the data remains on the target devices. In NoCopy mode, when the snapshot is unlinked the data is removed from the target devices.

To perform a Change Link Mode operation, from the Work with Associated Paths screen, enter 23 in the Opt column of the step for the associated IASP image.

NOTE: Option 23 is not available on PowerMax 10 (6079).

Restore

From the Work with Associated Paths screen, enter 24 in the Opt column of the step for the associated IASP image.

204 IASP-Supported Operations

The List of Snapshots screen appears for selecting the snapshot for the Restore operation.

NOTE: Restore operations can also be performed from the Work with Shapshots screen. Enter 2 in the Opt column of the desired snapshot.

Cancel/terminate

Depending upon the selected device type, you use the Cancel/Terminate option to perform either of the following:

Cancel an incremental relationship between a standard device and a BCV device that are currently a pair in the BCV set. If the devices are clone-enabled BCVs, the clone sessions are terminated on the array.

Terminate a TimeFinder/Clone copy session.

To cancel or terminate a BCV or Clone relationship, from the Work with Associated Paths screen, enter 19 in the Opt column of the step of the configured path.

The Work with Associated Paths screen reappears with the status for the device changed to NeverEstab or NotCreated. SRDF/TimeFinder Manager displays a confirmation message.

NOTE: Terminate SnapVX snapshots can only be done from the Work with Snapshots screen.

Adding or removing IOAs All disk units within a primary IASP and secondary IASP are operated on as one automatic operation.

NOTE: The ADDRMVIOA command does not physically add or remove the IOA from the system (LPAR), it enables or disables the IOA. Removal or addition of an IOA from the system or LPAR is performed from the Hardware Management Console.

Rules and restrictions for adding or removing IOAs

The following rules apply to adding and removing IOAs in normal operations:

When adding IOAs:

The IOA cannot be active on any node when the SRDF link is in sync or a BCV is established.

Target IOAs cannot be added if the devices are Established.

After an IOA is added, all disk units belonging to that IOA are presented to the node, and the selected image can be varied on for user access.

The target and source devices cannot be simultaneously presented to the same node after the addition. Otherwise, the operation fails when an attempt to add another copy of the same IASP image is presented.

When removing IOAs:

The respective image must be varied off.

If using the ADDRMVIOA command to remove IOAs, the primary and secondary IASPs must be specified in the command. Specifying only the primary IASP removes only the resources for the primary IASP. See ADDRMVIOA for more details.

After an IOA is removed, all disk units are removed from the configuration, and the data on those disks cannot be accessed.

Adding or removing IOAs on the primary node

To add or remove IOAs on the primary node use one of the following:

IASPCTL on the primary node. See IASPCTL for more information.

IASPCTLC on the target DR or backup node. See IASPCTLC for more information.

See ADDRMVIOA for more information on adding or removing IOAs.

NOTE: For hosts running V6R1 or higher, when varying on an IASP on a different system with a different amount of fiber connections to the IASP devices, the vary on goes through DASD checks to detect if all paths can be reestablished. To avoid a longer vary on time, a multi-path reset executes after the ADDIOA is completed and the devices have reported back in.

IASP-Supported Operations 205

Adding or removing IOAs on the DR or backup nodes

To add or remove IOAs on a DR or backup node, from the Work with Associated Paths screen, enter 17 to add IOA or 18 to remove IOA in the OPT column of the step associated with the path. You can also use the IASPCTL and IASPCTLC commands.

The Work with Associated Paths screen reappears.

NOTE: In a three-node remote BCV configuration, when options 17 or 18 are entered on the RDF1 step, the IOAs are added to or removed from the DR node. When options 17 or 18 are entered on the BCV1 step, the IOAs are added to or removed from the backup node. There is no interim screen that appears. The operation automatically occurs.

Varying on and varying off IASP images locally To vary on and vary off IASP images locally, use the following VRYCFG IBM i command with STATUS set to *ON or *OFF:

VRYCFG CFGOBJ(IASP832) CFGTYPE(*DEV) STATUS(*ON) VRYCFG CFGOBJ(IASP832) CFGTYPE(*DEV) STATUS(*OFF)

Varying on and varying off IASP images remotely

Using the REXEC server

To vary on an IASP image:

1. Start the *REXEC server on the target (STRTCPSRV *REXEC).

2. Enter the following:

RUNRMTCMD CMD('VRYCFG CFGOBJ(IASP832) CFGTYPE(*DEV) STATUS(*ON)') RMTLOCNAME('10.xxx.xxx.xxx' *IP) RMTUSER(QSECOFR) RMTPWD(XXXX)

To vary off an IASP image:

1. Start the *REXEC server on the target (STRTCPSRV *REXEC).

2. Enter the following:

RUNRMTCMD CMD('VRYCFG CFGOBJ(IASP832) CFGTYPE(*DEV) STATUS(*OFF)') RMTLOCNAME('10.xxx.xxx.xx' *IP) RMTUSER(QSECOFR) RMTPWD(XXXX)

Using the STM server

To vary on an IASP image:

1. Start the STM server. See STRSTMSRV for more information.

2. Enter the following:

STMRMTCMD CMD('VRYCFG CFGOBJ(IASP832) CFGTYPE(*DEV) STATUS(*ON)') RMTNODNAME(nodexyz) PORTNUM(8000)

To vary off an IASP image:

1. Start the STM server. See STRSTMSRV for more information.

2. Enter the following:

STMRMTCMD CMD('VRYCFG CFGOBJ(IASP832) CFGTYPE(*DEV) STATUS(*OFF)') RMTNODNAME(nodexyz) PORTNUM(8000)

206 IASP-Supported Operations

Displaying an IASP configuration by ASP To display configuration details of an IASP image by ASP:

1. On the Work with Associated Paths screen, enter 11 in the Opt column of the step of the IASP image.

The IASP View by ASP screen appears displaying the IASP view for the selected image and its associated path.

Note that only the step you selected (source and target) displays.

IASP View by ASP screen fields

Image

The name of the IASP image.

Path

The name of the path used to move data on devices of the source image to devices of the target image.

Step number

The description of how data is copied, the number of steps in the path identified by its position one to five, from source devices to target devices, such as 1, 2, 3, 4, and 5.

Step type

The replication step type for the device, such as BCVn, RDFn, CLNn, NCLn, or SVXn.

Opt

Entry field for configuration action options. This field is reserved for future use.

ASP

ASP number.

# of Units

The total number of devices in the ASP.

SRCIOA Status

Active The IOA is present in the configuration for the selected IASP.

Not active The IOA is not present in the configuration for the selected IASP.

TGTIOA Status

Active The IOA is present in the configuration for the selected IASP.

Not active The IOA is not present in the configuration for the selected IASP.

SRCDEV Status

Any status that IBM i presents. The IBM WRKCFGSTS command contains greater detail.

TGTDEV Status

Any status that IBM i presents. The IBM WRKCFGSTS command contains greater detail.

IASP-Supported Operations 207

Removing image information Use the IASPFILE command to remove image information from the IASPs and ISRCIOA files:

1. On the command line enter IASPFILE.

The Dell EMC IASP File Utility (IASPFILE) screen appears (Figure 81).

Figure 81 Dell EMC IASP File Utility (IASPFILE) screen

2. Enter the control action RMVIASPIMG.

3. Enter data in the Image Name field.

4. Enter the information for the Path Name field for the image, or enter *ALL for all paths of the image entered in step 3 .

NOTE: To remove image information, run the command from each node in the DR setup.

Performing IASP control actions Control actions are performed against devices in an IASP environment for SRDF, TimeFinder, TimeFinder/Clone, and TimeFinder SnapVX operations:

On the primary node, use the IASPCTL command from either the SRDF/TimeFinder Manager interface or the command line.

On the backup or DR node, use the IASPCTLC, and CTLACTTGT command from the command line.

Performing IASP control actions on primary node To perform IASP control actions on the primary node:

1. On the Dell EMC SRDF/TimeFinder Manager main menu, select option 3. Control Menu.

2. Select option 2. Independent IASP Control.

You can also run the IASPCTL command from the command line.

208 IASP-Supported Operations

The Dell EMC Independent ASP Ctrl (IASPCTL) screen (Figure 82) appears.

Figure 82 Dell EMC Independent ASP Ctrl (IASPCTL) screen with ADDIOA action

3. Provide the following information:

Image Name The name of the image on which to perform a control action.

Path Name The path name associated with the image on which to perform a control action.

Step Number The step number on which the control action operates.

Control Action The IASP control action to be performed.

To display a list of all control action parameters, press F4 on the Control Action prompt (Figure 82) and the Specify Value for Parameter Action screen appears. See IASPCTL for more information on the control action parameters.

4. Enter the desired control action, and press Enter.

The Dell EMC Independent ASP Cntrl (IASPCTL) screen appears with the selected IASP control parameters.

Depending on the control action chosen, the IASPCTL screen may appear with other required parameters.

5. Enter additional parameters as needed.

See IASPCTL for more information on additional control parameters.

Performing IASP control actions on DR or backup node 1. On the command line, run the IASPCTLC command.

The Dell EMC Independent ASP Ctrl (IASPCTLC) screen appears.

2. Provide the following information:

Image Name The name of the image on which to perform a control action.

Path Name The path name associated with the image on which to perform a control action.

Step Number The step number on which the control action operates.

To display a list of the node names in cluster, see Performing IASP control actions on primary node.

Control Action The IASP control action you want to perform.

To display a list of all control action parameters, press F4 on the Control Action prompt and the Specify Value for Parameter Action screen appears.

See IASPCTLC for more information on the control action parameters.

IASP-Supported Operations 209

3. Enter the desired choice for the Control Action field, and press Enter.

The Dell EMC Independent ASP Ctrl (IASPCTLC) screen appears with the IASP control parameters.

Node Name Parameter used in conjunction with the control action REBUILDIOA when the configuration file needs to be rebuilt for a node and to specify where the operation must be performed. This parameter is also used for STATUS, ADDIOA, REMOVEIOA, and FORCEADD.

The node name you provide must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

NOTE: The cluster node name can be found by running DSPCLUINF command. This command also displays the node IP address.

See IASPCTLC for more information on additional control action parameters.

Performing SRDF or TimeFinder control actions on DR or backup node 1. On the command line, run the CTLACTTGT command.

The Dell EMC SRDF/TimeFinder Ctrl (CTLACTTGT) screen (Figure 83) appears.

Figure 83 Dell EMC SRDF/TimeFinder Control (CTLACTTGT) screen with CREATE action

2. Enter the following information:

Image Name The name of the image to be used in an SRDF or TimeFinder control operation. Use this command for IASPs images only.

Path Name The name of the path for the image to be used in an SRDF or TimeFinder operation.

Step Number The step number for which the control action is initiated in an SRDF or TimeFinder operation.

Control Action The SRDF or TimeFinder control action to perform on the IASP image. See CTLACTTGT for a list of control actions.

3. If executing SnapVX operations additional parameters are required. See CTLACTTGT for more information.

Preparing target HA node The IASPCTLHA command pushes configuration files to the specified target HA node and prepares the node to assume the role of the primary node.

To push configuration files and prepare the target HA node for a primary take over:

210 IASP-Supported Operations

1. Ensure that EMCCTL is installed on the primary and the HA node and that the SRDF/TimeFinder Manager Server is started on all nodes.

2. Vary off the IASP that is connected to the production node. Only one path can be active at any time. When switching from the primary to the HA node, make sure that the path to the primary node is removed and the path to HA node is active.

You can perform this through the fiber switch or using the FA ports that have a path to both the production and HA node devices. See the example setup in Figure 76.

3. On the primary node, execute the IASPCTLHA command.

The Dell EMC IASP HA Control (IASPCTLHA) screen (Figure 84) appears.

Figure 84 Dell EMC IASP HA Control (IASPCTLHA) screen

4. Provide the following information:

Control HA Action Enter CFGHAIASP.

Image Name Specifies which IASP image configuration files to push to the HA node. Use this command for IASP images only.

*ALL Specifies configuration files for all IASP images to be pushed to the HA node. This is the default.

Name Name of the IASP image to be pushed to the HA node.

+ for more values Allows for multiple IASP image configuration files to be pushed to the HA node.

Target HA Node The name of the target HA node.

The node name entered must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

NOTE: The cluster node name can be found by running DSPCLUINF command. This command also displays the node IP address.

Port Number Port number for HA node. Default is 8000. If using a different port number, keep the port number consistent on all nodes participating in IASP operations.

5. With the server ended on the Primary node and the path added to the HA node, run IASPCTLHA with the SWHAIASP control action on the HA node. This performs a REBUILDIOA operation on the HA node as well.

The HA system is now ready to perform normal STM operations.

6. IASP should be varied off the HA node and IOA removed from the HA node.

7. To get to the original configuration, run IASPCTLHA with action CFGHAIASP on the HA machine, and then select the production host as the target node. On the production node, run IASPCTLHA with control action SWHAIASP.

IASP-Supported Operations 211

8. After running CFGHAIASP on HA node, end the server on the HA node, add IOA to the primary node and then run SWHAIASP.

If a rebuild of the primary node is necessary, follow the normal configuration steps. Running the SWHAIASP on the primary node rebuilds the IOA on the primary and pushes the files to other DR and backup nodes.

When returning to the primary node from the HA node, or when going to the HA node from the primary node (if the IASPCTLHA command with CFGHAIASP control action was run at least once on both nodes during initial configuration) and no configuration changes occurred, you do not need to run IASPCTLHA (CFGHAIASP) or IASPCTLHA (SWHAIASP) on the required nodes. You only need to run IASPCTLHA with RSTHAIASP on the node taking control of the configuration (primary or HA node).

NOTE: When using RSTHAIASP on a node, you do not need to issue the STRSTMSRV command on that node. One action of the RSTHAIASP command is to start the server.

Performing SRDF control actions during DR on primary node 1. On the command line, run the SRDFDRCTL command.

The Dell EMC SRDF DR Control (SRDFDRCTL) screen (Figure 124) appears.

Figure 85 Dell EMC SRDF DR Control (SRDFDRCTL) screen

2. Provide the following information:

Image Name The name of the image to be used in an SRDF control operation.

Path Name The name of the path for the image to be used in an SRDF operation.

Step Number The step number that the control action affects in an SRDF operation.

Control Action The SRDF control action to perform on the IASP image:

FAILOVER Switches data processing from the source (R1) side to the target (R2) side. When running in SRDF asynchronous mode and a FAILOVER is executed, the consistency protection is disabled and then the FAILOVER operation is performed. With dynamic RDF, if ESTABLISH/RESTORE is specified, devices are failed over, swapped and then re-established. In SRDF asynchronous mode, consistency protection is automatically enabled after executing an ESTABLISH/RESTORE.

FAILBACK Performs a source (R1) device takeover when you are ready to resume normal SRDF operations by initiating read/write operations on the source (R1) devices, and stopping read/write operations on the target (R2) devices. The target (R2) devices become read-only to their local hosts while the source (R1) devices are read/write enabled to their local hosts.

RESTORE Restores data from SRDF R2 data devices back to source devices.

3. Enter the optional control action parameter, if appropriate:

212 IASP-Supported Operations

Option for Failover *NO, ESTABLISH, RESTORE. *NO is the default.

SRDFDRCTL describes this optional parameter and its actions.

Automated operations Use the following commands to perform select IASP operations that are typically run using multiple manual steps. These commands have combined the manual steps into a single process to improve ease-of-use of SRDF/TimeFinder Manager.

Other batch process type commands are available besides the commands described below, and source code is provided in the install library file called QCLSRC.

Failing over and failing back In addition to the multi-step recovery procedures described in this chapter, there are two commands that can run in batch mode and perform all the steps for a failover or failback of IASP images. The commands are as follows and are run from the DR node:

IASPFAILOV Performs the failover to the DR node.

IASPFAILBK Performs the failback to the primary node.

NOTE: When the initial command IASPFAILOV is used with the option parameter set to ESTABLISH or RESTORE the command IASPFAILOV needs to be run again on the DR node to get back to the original state. When the option parameter *NO is used on the initial IASPFAILOV command the IASPFAILBK command needs to be run to get back to the original state.

When these commands are run, a screen appears. After the required parameters are entered, the system then performs all the necessary steps to complete the IASP failover or failback. These commands can also be run from the command line. When running from the command line, a confirmation screen appears and asks if you want to continue with the operation. For more details on these commands, see IASPFAILOV and IASPFAILBK.

The IASPFAILOV and IASPFAILBK commands are typically used if no additional user intervention is required for the failover or failback operations. If there are situations where user-supplied setup scripts need to be run or the DR machine requires changes before the IASP is varied on, then the multi-step procedures that follow should be used. However, the SRDF/TimeFinder Manager scripts used to run these commands can be modified to add user-specific actions. See Modifying the script for the IASPFAILOV command and Modifying the script for the IASPFAILBK command for more information.

NOTE: IASPFAILOV and IASPFAILBK commands are not available in Cascaded SRDF configurations.

Preparing the source or target nodes for backup There are two commands used to prepare the source and target nodes for TimeFinder backup, as well as restore operations of IASP images. The commands are as follows and are run from the target node:

IASPTFBCK Prepares the source and target nodes for a TimeFinder backup operations.

IASPTFEST Prepares source and target to go back to original state prior to issuing the IASPTFBCK command.

RTVSTMINF is used within the two scripts to return status information for the selected image, path and step. It also returns SRDF/TimeFinder Manager, Solutions Enabler, and I/O driver release level information.

For more details on these commands, see IASPTFBCK, IASPTFEST, and RTVSTMINF.

Non-Dell Procedures 213

F

Non-Dell Procedures Invisible Body Tag

This appendix provides guidelines when using IBM-related procedures.

Topics:

Overview Displaying contents of a physical file on each node Verifying IOA information

Overview During setup, configuration, or recovering from a disaster, there are occasions when you use IBM commands, perform DST or SST procedures, or use other third-party software. The sections that follow describe those procedures.

See the IBM documentation for more information about IBM i and IASPs

Displaying contents of a physical file on each node To display the contents of the physical file IASP on each node, on any node, type:

DSPPFM EMCCTLC/IASPS

The Display Physical File Member screen (Figure 86) appears.

Figure 86 Displaying the contents of a physical file

Display Physical File fields example

IASPBCV

IASP device

LOCALNCL

Configured path for the SRDF image

1

Step number

PRIMNODE

Primary node name

SRCNODE

Source node for this step

TGTNODE

Target node for this step

214 Non-Dell Procedures

1

Source node LPAR ID

3

Target node LPAR ID

1234567

System serial number for the source node

1234567

System serial number for the target node

IASPBCV

IASP name

33

ASP number

8000

Port number of the SRDF/TimeFinder Manager server

Verifying IOA information To verify IOA information stored in the physical file ISRCIOA on any node, use the Display Physical File Member screen.

To verify one or more IOA serial numbers:

1. On the command line, type the following command:

DSPPFM EMCCTL/ISRCIOA

The Display Physical File Member screen or DSPPFM EMCCTLC/ISRCIOA on a DR or backup node appears. The screen shows the slot number, bus number, resource name, ASP number, and system serial number for each IOA.

2. If necessary, verify the slot number and bus number:

DSPHDWRSC TYPE(*STG) OUTPUT(*PRINT)

Extended Features Commands Reference 215

G

Extended Features Commands Reference Invisible Body Tag

This appendix provides reference information about the control commands.

Topics:

Conventions ADDRMVIOA CRTNETCNFG CTLACT CTLACTTGT DISCOVER DISCOVERC ENDSTMSRV IASPCTL IASPCTLC IASPCTLHA IASPFAILBK IASPFAILOV IASPFILE IASPTFBCK IASPTFEST RELDEVLCK RELDEVLCKC RTVSTMINF SETRDFMOD SETRDFMODC SRDFDRCTL STMRMTCMD STRSTMSRV

Conventions The descriptions of the commands in this appendix can contain the following sections:

Syntax Presents the syntax of the command. Variables that you specify are shown in italics. Optional parameters are indicated by brackets.

Description Describes the purpose and result of the command.

Required parameters Describes one or more parameters that must be specified at the command line. Each description contains all possible values of the variable and states which, if any, of the values is the default. Variables that you must specify are shown in italics.

Optional parameters Describes one or more parameters that can be included at the command line. Each description contains all possible values of the variable and states which, if any, of the values is the default. Variables that you can specify are shown in brackets [ ].

Usage notes Presents specific points that you should keep in mind when using the command.

Examples Presents examples of how to invoke the command.

216 Extended Features Commands Reference

ADDRMVIOA Adds or removes the IOAs for a selected IASP.

NOTE: The ADDRMVIOA command does not physically add or remove the IOA from the system (LPAR), it enables or disables the IOA. Removal or addition of an IOA from the system or LPAR is performed from the Hardware Management Console.

Syntax

ADDRMVIOA ACTION(ADDIOA|REMOVEIOA)

IASPRESC((iasp_name_1(ioa_resource_name_1, ioa_resource_name_2)) (iasp_name_2(ioa_resource_name_1, ioa_resource_name_2)))

Description

Adds or removes the IOAs for a selected IASP. Run this command on the node where the IOAs are added or removed.

The ADDRMVIOA command can be used to add an IOA even if SRDF/TimeFinder Manager is not yet configured.

This command can be executed from the command line with the required parameters, as shown in the example below, or the command ADDRMVIOA can be entered without parameters and the Dell EMC Add/Remove IOA screen appears (Figure 96).

Required parameters

ACTION(ADDIOA|REMOVEIOA)

Add or remove command

IASPRESC((iasp_name_1(ioa_resource_name_1 ioa_resource_name_2)) (iasp_name_2(ioa_resource_name_1 ioa_resource_name_2)))

IASP name and IOA resource name. Up to 256 ASPs can be added, and up to 128 IOAs can be added for each ASP.

NOTE: The IOA resource name can be found in the ISRCIOA file or by using the System Service Tools (SST).

IASPRESC((primary_iasp_name(ioa_res_name_Prim_1 ioa_res_name__Prim_2)) (secondary_iasp_name_1(ioa_res_name_Sec1_1 ioa_res_name_Sec1_2)) (secondary_iasp_name_2(ioa_res_name_Sec2_1 ioa_res_name_Sec2_2)))

Primary and secondary IASP names, and primary and secondary IOA resource names.

NOTE: When the add or remove command is run on a primary IASP that has secondary IASPs, the secondary IASPs must to be entered into the same command.

Extended Features Commands Reference 217

Examples

Add single and multiple IOAs to IASP images

ADDRMVIOA ACTION(ADDIOA) IASPRESC((IASP1(IAO1)) (IASP2(IOA1 IOA2)))

Add primary and secondary IOAs to IASP images

ADDRMVIOA ACTION(ADDIOA) IASPRESC((primIASP(primIOA1 primIOA2)) (sec1IASP(sec1IOA1 sec1IOA2)) (sec2ASP(sec2IOA1 sec2IOA2)))

CRTNETCNFG Creates the NETCNFG file and adds network services to the file.

See CRTNETCNFG for more information.

CTLACT Processes SRDF and TimeFinder control actions for one or all images (SYSTEM and IASP).

See CTLACT for more information.

CTLACTTGT Processes SRDF or TimeFinder control actions for IASP images on the target side.

Syntax

CTLACTTGT IMAGE_NAME(image_name|*ALL)

PATH_NAME(path_name)

STEPNUM(step_number)

ACTION(control_action)

[SPLIT_MODE(CHG_ASP_ACT|SPLITWA|MAINTENANCE)]

[PROT_ESTAB(*YES|*NO)]

[SVX_MODE(CHG_ASP_ACT|CONSISTENT)]

[SNAPVXNAME(snapshot_name)]

[SNAPVXGEN(snapshot_generation)]

[SNAPVXTTL(DAYS|DATE)]

[N_SNPSHOT(new_snapshot_name)]

[LINK_MODE(NOCOPY|COPY)]

[TTL_DAYS(1-400)]

[TTL_DATE(Date)]

218 Extended Features Commands Reference

Description

CTLACTTGT processes SRDF or TimeFinder control actions for IASP images on the target side.

All control commands executed on the DR or backup node use the image file built on the primary node and sent to the corresponding node. The PATH_NAME and STEPNUM parameters should use the path name and step used on the primary node for corresponding devices. For example, if the path REMOTEBCV /RDF1/BCV1 exists in the image file, use the path name REMOTEBCV and step number two to execute TimeFinder control operations on the DR node.

Required parameters

IMAGE_NAME(image_name|*ALL)

The name of the image (image_name) or *ALL to indicated all images.

PATH_NAME(path_name)

The path name associated with the image to be used in an SRDF or TimeFinder control operation.

STEPNUM(step_number)

The specific step number for which the control action operates on in an SRDF or TimeFinder control operation.

Steps in the path are defined during configuration and are identified by their position (one through five) in the path.

ACTION(control_action)

Specifies the control operation to perform:

STATUS Provides SRDF, Clone, Clone emulation, or BCV control status information for the step in the associated path of the image. For SnapVX, if snapshot name and generation are specified, the state of the specified snapshot is provided.

NOTE: If the status of the SnapVX step is Linked, CopyInProg, Copied, Restored, RestoreInProg, RestNotPaired, or RestgNotPaired an additional message is provided with the snapshot name and generation.

ESTABLISH Establishes SRDF links for SRDF control or establishes/re-establishes BCV or Clone emulation pairs for BCV control. When running in SRDF/A mode, consistency protection is automatically enabled after executing an ESTABLISH operation is executed.

For SnapVX type of step, ESTABLISH creates and activates a SnapVX snapshot session.

SPLIT Splits SRDF links for SRDF control or splits BCV or Clone emulation pairs for TimeFinder control. When the system is running in SRDF/A mode and a SPLIT is executed, consistency protection is disabled and then the SPLIT operation is performed.

NOTE: For TimeFinder/Clone configurations, if the devices are in Restored state, use the SPLIT option to change the direction of the clone relationship (that is, the original source device becomes the source device for a future copy), which allows the use of the RECREATE command and normal processing continues.

FAILOVER Switches data processing from the source (R1) side to the target (R2) side. If the source (R1) is operational, FAILOVER suspends I/O traffic on the RDF links, and write disables the devices on the source (R1) side to their hosts, and then write enables the devices on the target side to their local hosts. When running in SRDF asynchronous mode and a FAILOVER is executed, the consistency protection is disabled and then the FAILOVER operation occurs.

With dynamic RDF, when you specify the ESTABLISH option, devices failover, swap, and then re-establish. In SRDF/A mode, consistency protection is automatically enabled after an ESTABLISH operation executes. For arrays or dynamic volumes, Dell recommends FAILOVER with the ESTABLISH option which swaps personality (the R1 devices become R2 devices and the R2 devices become R1 devices) and then starts the synchronization.

For dynamic RDF, if the RESTORE option is specified, devices failover, swap and then re-establish. Invalid tracks on the new R2 side (originally the R1 side) are restored to the new R1 side (formerly the R2 side).

When running in SRDF asynchronous mode, consistency protection is automatically enabled after executing a RESTORE operation.

Extended Features Commands Reference 219

FAILBACK Performs a fail back, or source (R1) device takeover, when you are ready to resume normal SRDF operations by initiating read/write operations on the source (R1) devices, and stopping read/write operations on the target (R2) devices. The target (R2) devices become read-only to their local hosts while the source (R1) devices are read/write enabled to their local hosts. In SRDF/A mode, consistency protection is enabled after a FAILBACK operation executes.

R2RW Enables the R2 read/write, enables R2 mirror write, and enables the target (R2) devices to their local hosts.

If the source (R1) is operational, R2RW suspends I/O traffic on the RDF links. Then, R2RW write enables the devices on the target side to their local hosts.

In SRDF asynchronous mode, when an R2RW executes, the consistency protection is disabled, and then the read/write enable R2 mirror operation is performed.

SUSPEND Suspends SRDF links for SRDF control. When the system is running in SRDF/A mode and a SUSPEND is executed, the consistency protection is disabled and then the SUSPEND operation is performed.

ENABLE Enables the consistency protection for SRDF/A backed devices when running in SRDF/A mode. If data cannot be copied from the R1 to the R2, all devices in the group are made Not Ready on the link to preserve the R2 data consistency.

NOTE: If devices are enabled for consistency group protection, the devices must be disabled before you change the mode to Synchronous or initiate the SPLIT/SUSPEND operation.

DISABLE Disables the consistency protection for SRDF/A backed devices when running in SRDF asynchronous mode.

CREATE Creates or recreates a Clone copy session with devices in the image. For TimeFinder/Clone the state of the device pair is PreCopy. When the Create operation completes, the state changes to Created.

NOTE: PreCopy is not available when running PowerMax 10 (6079).

Run CREATE before you activate the session, which has a shorter duration than an Establish operation.

ACTIVATE Activates a Clone copy session with the devices in the image. For TimeFinder/Clone, while the operation is in progress the state of the device pair is CopyInProg. Once the copy is complete, the state changes to Copied.

NOTE: CopyInProg is not available when running PowerMax 10 (6079) and above.

NOTE: The point-in-time copy becomes available after an ACTIVATE operation. Create must be done before you can activate a Clone copy session.

LINK Copies the SnapVX point-in-time data to the target device.

There are two types of links, NOCOPY (the default) or COPY. NOCOPY links do not retain point-in-time data once the link is removed and any previous target data is lost. Copy mode must be used in order for the linked target to retain data after the link is removed. When linking a snapshot, COPY or NOCOPY must be specified.

UNLINK - Removes the current SnapVX link to target devices.

RESTORE Restores data from target TimeFinder replication devices or from SRDF R2 data devices back to source devices or other devices. This can be a full or incremental restore operation.

The following behavior and rules apply to the restore operation for the different TimeFinder replication devices:

TimeFinder/Mirror and TimeFinder /Clone Emulation

A full restore operation copies the entire contents of the BCV device to the standard device. For an incremental restore process, the BCV device copies only the new data to the standard device that was written to the BCV device while the BCV pair was split. Any changed tracks on the standard device are also overwritten with the data on the corresponding tracks of the BCV device. This process is useful for porting an application that was tested on the BCV device, to the standard device. The restore process is complete when the standard device and the BCV device contain identical data.

The BCV device is not available to the host while it is assigned as a BCV mirror on a standard device. However, any new data written to the standard device is copied to the BCV device while the BCV pair exists.

When using native TimeFinder/Mirror and a BCV device is used to restore a point-in-time copy to the standard device, the point-in-time copy on the BCV device is modified if the host writes to the standard device during the restore operation. The -protected option used on the restore operation preserves the point-in-time stored on the BCV. When using mode, a protected restore operation is always in effect.

To continue normal operations, the BCV pairs should be split.

220 Extended Features Commands Reference

TimeFinder/Clone

The restore operation copies target data to another device (full restore), or back to the original source device (incremental restore). For a full restore, the original session terminates and a copy session to the target of the restore operation begins. For an incremental restore operation, the original session copy direction reverses, and changed data is copied from the target device to the source device. To support the restore operation, the session must be in a Copied state.

Use the SPLIT command to split a clone device pair that is in the Restored state. This command changes the direction of the clone relationship (that is, the original source device becomes the source device for a future copy), which allows the use of the recreate command. TimeFinder/Clone supports the SPLIT command.

TimeFinder/SnapVX

The restore operation copies the point-in-time data from a snapshot back to the original source device. The snapshot must be fully established to perform a restore.

SRDF restore operation rules and restrictions

The new data, that was updated on the target (R2) device while the SRDF pair was split, is copied to the source (R1) device. Any changed tracks on the source (R1) device are refreshed from the corresponding tracks on the target (R2) device. After the restore operation has successfully completed, the SRDF pairs synchronize. You can use the RTVSTMINF command to confirm that the SRDF pairs are in a Synchronized state.

NOTE: The CTLACTTGT and IASPCTLC commands using control action STATUS can be used to confirm the status of SRDF pairs.

When an incremental restore is initiated for each specified SRDF pair in a device file:

The source (R1) device is write disabled for the local hosts.

The target (R2) device is write disabled for the local hosts.

Data traffic is suspended on the SRDF links.

The invalid tracks on the source (R1) device are refreshed with the changed tracks on the target (R2) side. The R1 and R2 track tables are merged.

Traffic is resumed on the SRDF links.

The source (R1) device is read/write enabled for the local hosts.

The SRDF pair is in the Synchronized state when the source (R1) device and the target (R2) device contain identical data.

The incremental restore operation is rejected if the target has invalid local (R2) tracks.

NOTE: When running in SRDF asynchronous mode, consistency protection is automatically enabled after executing a RESTORE operation.

RENAME Changes the SnapVX snapshot name of a specified generation. If you do not specify a generation, the control operation renames generation 0.

SET TTL Sets a time to live (TTL) for a SnapVX snapshot, from when TTL is set, in days or a date. The value in days can be set to a value between 1 and 400. The date value is a specified date up to 400 days in the future, from which a value in days is created, based on the difference between the specified absolute time and the host time when the action is performed. When the TTL expires the snapshot automatically terminates unless there are one or more links. Automatic termination takes place when the links are removed. If TTL is not set, the snapshot remains established until it is manually terminated.

SETCOPY - Changes the copy mode of a link to copy. Data is physically copied to the target devices. When the link is terminated the data is retained on the target.

NOTE: SnapVX no longer supports SETCOPY when running on PowerMaxOS 10 (6079) using STM IBM i version 10.0. This is still supported when running on versions lower than PowerMaxOS 10 (6079) using STM IBM i version 10.0.

SETNOCOPY - Changes the copy mode of a link to NoCopy. Data is presented on the target devices, but not physically copied. When the link is terminated the data is not retained on the target.

NOTE: SnapVX no longer supports SETNOCOPY when running on PowerMaxOS 10 (6079) using STM IBM i version 10.0. This is still supported when running on versions lower than PowerMaxOS 10 (6079) using STM IBM i version 10.0.

TERMINATE Stops the Clone copy session between the specified source and target devices in the image.

For SnapVX snapshot sessions, TERMINATE removes the snapshot. All links must be unlinked before terminating a snapshot.

NOTE: If a snapshot has restores, only the restored session is terminated.

Extended Features Commands Reference 221

CANCEL Cancels the existing internal session between the specified standard device and the BCV devices in the image.

Once the session is cancelled, the corresponding BCV devices are placed in a SplitNoInc state, and the BCV pair can no longer be incrementally established or restored.

Use Cancel before performing an unpairing operation on Clone Enabled BCV devices. Failure to run Cancel causes hanging Clone sessions to remain on the array.

Restrictions for cascaded sessions:

Cascading from TimeFinder Clone emulation is not supported.

Restrictions for incremental restore operation until the restore data copy is complete

One of the existing sessions may be the target of a differential Recreate or incremental Establish operation.

No new session can be created using another Create or full Establish command.

SPLIT_MODE(CHG_ASP_ACT|SPLITWA|MAINTENANCE)

Specifies method for stopping writes to the devices in the image. The options are:

CHG_ASP_ACT Executes the operation after suspending initiation of new transactions and operations.

NOTE: The Change ASP Activity CL command (CHGASPACT) is used for hosts running V6R1M0 or higher. The selected IASP image that uses the command is quiesced at the start of new commitment control transactions, new database change operations, and new Integrated File System (IFS) change operations. The command suspends initiation of new transactions and operations before the split, writes changes to auxiliary storage, and resumes initiations of new transactions and operations after the split.

SPLITWA Executes the operation after holding I/Os on the array. Splits a local or remote BCV, Clone, or Clone emulation while the source system is operational. The resulting image is consistent and holds data upon the last commit.

With TimeFinder/CG (SPLITWA) operations, you do not have to set the IBM i host in a restricted state or perform a hold jobs operation.

The SRDF/TimeFinder Manager client and the controlling host must have a gatekeeper configured on each locally attached array. For detailed information on array gatekeeper management, see the Solutions Enabler Installation and Configuration Guide.

On the client, the netcnfg file must be configured using the CRTNETCNFG command. This ensures that correct information (node name, IP address, port, and security level) points to the remote server. Only non-secure connections are supported for IBM i.

NOTE: When using this split type, the data in main memory is not included in the image. Only use SPLITWA when the host and applications are in a quiescent state. If this is not suitable for your business needs, use other operating system functions such as journaling and database commitment control to create an image that includes the last transaction. When SPLITWA is used remotely and there are several SRDF groups in the configuration, SRDF mode for the links should be synchronized or links should be split.

MAINTENANCE Splits or Suspends SRDF links, splits BCV pairs or activates a virtual copy session or Clone copy session in maintenance mode (that is, no interference with host operations).

PROT_ESTAB(*YES|*NO)

Performs a Protected or normal BCV Establish operation:

*YES Establish two mirrors of a BCV device to the standard device. When the split occurs, both mirrors are split simultaneously. This operation moves all mirrors of the locally mirrored BCV devices to join the mirrors of a standard device

*NO Perform a normal Establish operation for the BCV device. This is the default.

SVX_MODE(CHG_ASP_ACT|CONSISTENT)

The mode to use for the SnapVX Establish operation:

CHG_ASP_ACT Executes the operation after suspending initiation of new transactions and operations.

CONSISTENT Executes the operation in Consistent mode (that is, no interference with the host operations). This is the default.

222 Extended Features Commands Reference

CAUTION: Use caution when using this Consistent Establish mode, as the data in main memory is not included in the image. Use this only when the host and applications are in a quiescent state. If that is unacceptable to your business needs, use other operating system functions such as journaling and database commitment control to obtain an image current with the last transaction.

SNAPVXNAME

The name of the Snapshot.

NOTE: For ESTABLISH action SNAPVXNAME specifies the name for new snapshots. For all other control actions SNAPVXNAME specifies the name of the existing snapshots to be operated on. This parameter is required for all SnapVX control actions except STATUS where it is optional.

SNAPVXGEN

The Generation of the Snapshot. For all SnapVX control actions, except ESTABLISH, specifies the generation of the existing snapshots to be operated on. If set to zero, the most recent snapshot is used for the control action.

SNAPVXTTL

For ESTABLISH and SET_TTL SnapVX controls specifies a Time to Live. The possible values are:

DAYS -Specifies the time to live in days.

DATE - Specifies a date for the snapshot time to live.

If you do not specify a value, the Time to Live is set to unlimited and the Snapshot is kept until manually terminated.

LINK_MODE(NOCOPY|COPY)

The mode used for a LINK SnapVX operation. Options are as follows:

NOCOPY The target does not retain point-in-time data once the link is removed, and any previous target data is lost. This is the default.

COPY Data is physically copied to the target devices. When the link is terminated the data is retained on the target.

TTL_DAYS

Time to Live in days. The value in days can be set to any value between 1 and 400.

TTL_DATE

Specifies a date for the snapshot time to live in the form MM/DD/YYYY (month/day/year) with reference to the host time. The specified date may be up to 400 days in the future.

Examples

CTLACTTGT IMAGE_NAME (DISKPOOL) PATH_NAME(REMOTEBCV) STEPNUM(1)ACTION(FAILOVER) OPTION(ESTABLISH)

CTLACTTGT IMAGE_NAME(IASP1) PATH_NAME(SRDF) STEPNUM(1) ACTION(SWAP)REFRESH(R1)

CTLACTTGT IMAGE_NAME(IASP1) PATH_NAME(REMOTEBCV) STEPNUM(2)ACTION(SPLIT) SPLIT_MODE(SPLITWA)

For control action command examples for TimeFinder/SnapVX, see the examples section in CTLACT. Replace CTLACT with CTLACTTGT.

DISCOVER Discovers new devices, removes old device information from the SYMAPI database, and updates the database with new information. This command also updates information in the IMAGE file and controls checking and clearing of serial number IDs for all devices.

See DISCOVER for more information.

Extended Features Commands Reference 223

DISCOVERC Discovers new devices, removes old device information from the SYMAPI database, and updates the database with new information. DISCOVERC performs the discover process on the target side that is required when the configuration on the host or array changes.

See DISCOVERC for more information.

ENDSTMSRV Shuts down the SRDF/TimeFinder Manager server job.

See ENDSTMSRV for more information.

IASPCTL Performs IASP control functions on the primary node or HA node.

Syntax

IASPCTL IMAGENAME(Image_name)

PATHNAME(Path_name)

STEPNUM(Step_number)

ACTION(Control_action)

NODENAME(Node)

SRCORTGT (TGTDEV|SRCDEV)

[PROT_ESTAB(*YES|*NO)]

[TGTNAME(Node_name)]

[PORTNUM(port_number)]

[SNAPVXNAME(snapshot_name)]

[SNAPVXGEN(snapshot_generation)]

[SNAPVXTTL(DAYS|DATE)]

[N_SNPSHOT(new_snapshot_name)]

[LINK_MODE(NOCOPY|COPY)]

[TTL_DAYS(1-400)]

Description

IASPCTL performs the control action specified on the devices associated with the path of the selected IASP image.

Required parameters

IMAGENAME(Image_name)

The name of the image on which to perform a control action.

PATHNAME(Path_name)

224 Extended Features Commands Reference

The path name associated with the image to be used in an SRDF or TimeFinder control operation.

STEPNUM(Step_number)

The specific step number for which the control action is initiated in an SRDF or TimeFinder control operation.

ACTION(control_action)

The control action to perform:

ESTABLISH Establishes SRDF links for SRDF control or establishes/re-establishes BCV pairs for BCV control. When the system is running in SRDF asynchronous mode, consistency protection is automatically enabled after executing an ESTABLISH operation.

For SnapVX type of step, ESTABLISH creates and activates a SnapVX snapshot session.

SPLIT Splits SRDF links for SRDF control or splits BCV pairs for TimeFinder control. When the system is running in SRDF asynchronous mode and a SPLIT executes, the consistency protection is disabled and then the Split operation is performed. For TimeFinder/Clone configurations, if the devices are in Restored state, use the SPLIT option to change the direction of the clone relationship (that is, the original source device becomes the source device for a future copy), which allows the use of the RECREATE command and normal processing continues.

On the primary node, when performing a split operation follow these steps:

Varied off

- Use the IASPCTL command to perform a maintenance split.

Varied on

- Use the IASPCTL command for the split. SRDF/TimeFinder Manager uses the Change ASP Activity CL command (CHGASPACT) to quiesce IASP data for the split.

ADDIOA Adds one or more IOAs with target TimeFinder replication devices to the backup node.

CAUTION: When varying on an IASP on a different system with different number of fiber connections to the IASP devices, the vary on goes through DASD checks to detect if all paths can be reestablished. To avoid a longer vary on time, a multi-path reset executes automatically after the ADDIOA completes and the devices have reported back in.

FORCEADD Adds the IOA to the target host when the SRDF link is in a partitioned or transmit idle state when the regular ADDIOA control action fails, or when the source STM Server is not available. The message that appears when the regular add fails indicates this as well.

REMOVEIOA Removes one or more IOAs with target devices from the backup node.

REBUILDIOA Rebuilds the IOA file with IOA configuration information (slot number, bus number, and system serial number for the IOA). The rebuild action automatically runs with a CONFIG action.

CREATE Creates or recreates a Clone copy session with devices in the image. For TimeFinder/Clone the state of the device pair is PreCopy. When the Create operation completes, the state changes to Created.

NOTE: CREATE must be executed before you activate the session, which has a shorter duration than an ESTABLISH operation.

See Usage notes for more information.

NOTE: PreCopy is not available when running PowerMax 10 (6079).

ACTIVATE Activates a Clone copy session with the devices in the image. For TimeFinder/Clone, while the operation is in progress the state of the device pair is CopyInProg. Once the copy is complete, the state changes to Copied.

NOTE: CopyInProg is not available when running PowerMax 10 (6079) and above.

When performing an ACTIVATE operation on the primary node, use these steps:

Varied off

- Use the IASPCTL command to perform the ACTIVATE operation.

Varied on

- Use the IASPCTL command to perform the ACTIVATE operation. SRDF/TimeFinder Manager uses the Change ASP Activity CL command (CHGASPACT) to quiesce IASP data for the split.

RESTORE Restores data from target devices back to source devices or other devices. This can be a full or incremental restore operation. See CTLACTTGT for details on the behavior and rules that apply to the restore operation for TimeFinder replication devices.

TERMINATE Stops the existing Clone copy session between the specified source and target devices in the image.

Extended Features Commands Reference 225

For SnapVX snapshot sessions, Terminate removes the snapshot. All links must be unlinked before terminating a snapshot.

NOTE: If a snapshot has restores, only the restored session is terminated.

CANCEL Cancels the existing internal session between the specified standard device and the BCV devices in the image.

Once the session is cancelled, the corresponding BCV devices are placed in the SplitNoInc state, and the BCV pair can no longer be incrementally established or restored. CANCEL must be executed before you perform an unpairing operation on RAID 5/RAID 6 or mixed BCV devices. Failure to run CANCEL causes hanging Clone sessions to remain on the array.

LINK Copies the SnapVX point-in-time data to a target device.

There are two types of links, NOCOPY (the default) or COPY. NOCOPY links do not retain point-in-time data once the link is removed and any previous target data is lost. Use copy mode so that the linked target retains data after the link is removed. When linking a snapshot, COPY or NOCOPY must be specified.

NOTE: NOCOPY is not available when running PowerMax 10 (6079).

RELINK Removes the current SnapVX link to target devices and presents a different snapshot. The relink may also be used to relink to the same snapshot. This has the effect of refreshing the point-in-time copy on the link target if it has been modified by host writes.

UNLINK - Removes the current SnapVX link to target devices.

RENAME Changes the SnapVX snapshot name. Renames on the specified generation. If generation is not specified, then generation 0 is renamed.

SET TTL Sets a time to live (TTL) for a SnapVX snapshot, from when TTL is set, in days or a date. The value in days can be set to a value between 1 and 400. The date value is a specified date up to 400 days in the future, from which a value in days is created, based on the difference between the specified absolute time and the host time when the action is performed. When the TTL expires the snapshot terminates unless there are one or more links. Automatic termination occurs when the links are removed. If TTL is not specified, the snapshot remains established until it is manually terminated.

STATUS Retrieves link status, IOA status, and device status for the specified device. For SnapVX, if snapshot name and generation are specified then the state of the generation is provided.

CONFIG Configure IASP operation and writes data to the IASP file. Also rebuilds the IOA file.

SETCOPY Changes the copy mode of a link to copy.

NOTE: SETCOPY is not available when running PowerMax 10 (6079) and above.

SETNOCOPY Changes the copy mode of a link to nocopy.

NOTE: SETNOCOPY is not available when running PowerMax 10 (6079) and above.

UNLINK Removes the current link to target devices.

NODENAME(Node)

The parameter used in conjunction with the control action REBUILDIOA when the configuration file needs to be rebuilt for a node and to specify where the operation must be performed. This parameter is also used for STATUS, ADDIOA, REMOVEIOA, and FORCEADD. The node name entered must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

SRCORTGT (TGTDEV|SRCDEV)

This parameter is used in conjunction with the control actions ADDIOA, REMOVEIOA, STATUS, and FORCEADD to differentiate between source or target operations when both images are located on the same node. This parameter is only shown when both images are on the same node.

For example, if an R2 and remote BCV image are being used on the same node, only specifying the node is not enough. If the IASP file does not have an entry where the source and target node is the same, this parameter is set to the default value (TGTDEV).

It is required when the source and target node are the same in the IASPs file. This can be the case when using remote BCV's where the R2's and the BCV's are presented to the same host.

This parameter is available only when this is the case, in all other cases this parameter is available and has the default value TGTDEV.

For any other control actions, this parameter is set to default and does not have an effect.

226 Extended Features Commands Reference

Restrictions for cascaded sessions:

Cascading from TimeFinder Clone emulation is not supported.

Restrictions for incremental restore operation until the restore data copy is complete

One of the existing sessions may be the target of a differential Recreate or incremental Establish operation.

No new session can be created using another Create or full Establish command.

PROT_ESTAB(*YES|*NO)

Performs protected BCV ESTABLISH/RESTORE operation:

*YES Establishes two mirrors of a BCV device to the standard device. When the Split operation occurs, both mirrors are split simultaneously. This operation moves all mirrors of the locally mirrored BCV devices to join the mirrors of a standard device.

NOTE: Use the *YES parameter only when protected BCVs are in the configuration.

*NO Performs a normal Establish operation for the BCV device. This is the default.

NOTE: When using native TimeFinder/Mirror and a BCV device is used to restore a point-in-time copy to the standard device, the point-in-time copy on the BCV device is modified if the host writes to the standard device during the restore operation. The protected option used on the restore operation preserves the point-in-time stored on the BCV. When using mode, a protected restore operation is always in effect.

TGTNAME(Node_name)

The target name location to where the configuration of the selected step for this IASP is being set. The node name entered must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

PORTNUM(port_number)

The TCP/IP port number.

The default value is 8000. If you used a port number other than the default, use that port number on the primary node, backup node, and main partition.

Examples

Split the IASP image (PIASP2)

Associated path name is (REMOTEBCV) on the primary node.

IASPCTL IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(1) ACTION(SPLIT)

Establish the IASP image (PIASP2)

Associated path name is (REMOTEBCV) on the primary node.

IASPCTL IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(2) ACTION(ESTABLISH) PROT_ESTAB(*NO)

Rebuild IOA files on target devices for the IASP image (PIASP2) on the backup node

IASPCTL IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(2) ACTION(REBUILDIOA) NODENAME(NODE)

For control action command examples for TimeFinder/SnapVX, see the examples section for CTLACT. Replace CTLACT with IASPCTL.

Extended Features Commands Reference 227

IASPCTLC Performs IASP control functions on the backup node or DR node.

Syntax

IASPCTLC IMAGENAME(Image_name)

PATHNAME(Path_name)

STEPNUM(Step_number)

ACTION(Control_action)

NODENAME(Node)

SRCORTGT (TGTDEV|SRCDEV)

Description

IASPCTLC performs the control action specified on the devices associated with the path of the selected IASP image.

All control commands executed on the DR or backup node use the image file built on the primary node and sent to the corresponding node. The path and step parameters should use the path name and step used on the primary node for corresponding devices.

When adding and removing I/O in an unplanned disaster recovery situation, you cannot verify whether:

The target IASP image is varied on or varied off on the backup node before the IOA removal.

The target device IOA has not been presented to any node before adding the IOA.

Required parameters

IMAGENAME(Image_name)

The name of the image on which to perform a control action.

PATHNAME(Path_name)

The path name associated with the image to be used in an SRDF or TimeFinder control operation.

STEPNUM(Step_number)

The specific step number for which the control action is initiated in an SRDF or TimeFinder control operation.

ACTION(Control_action)

Specifies the control action to perform:

STATUS Retrieves link status, IOA status, and device status for the specified device.

ADDIOA Adds IOA(s) with source or target devices to the primary node, backup node, or DR node.

CAUTION: For hosts running V6R1 and higher, when you vary on an IASP on a different system with a different number of fiber connections to the IASP devices, the vary on goes through DASD checks to detect if all paths can be reestablished. To avoid a longer vary on time, a multi-path reset executes automatically after the ADDIOA is completed and the devices have reported back in.

FORCEADD Adds IOAs to the target host when the SRDF link is in a partitioned or transmit idle state when the regular ADDIOA control action fails, or when the source STM Server is not available. The message that appears when the regular add fails indicates this as well.

REMOVEIOA Removes IOAs with source or target devices from the primary node, backup node, or DR node.

REBUILDIOA Rebuilds the IOA file with IOA configuration information (slot number, bus number, and system serial number for the IOA). The rebuild action automatically runs with a CONFIG action.

228 Extended Features Commands Reference

NODENAME(Node)

The parameter used in conjunction with the control action REBUILDIOA when the configuration file needs to be rebuilt for a node and the node where the operation must be performed must be varied on or off. This parameter is also used for STATUS, ADDIOA, REMOVEIOA, and FORCEADD. The node name entered must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

SRCORTGT (TGTDEV|SRCDEV)

This parameter is used in conjunction with control actions ADDIOA, REMOVEIOA, STATUS, and FORCEADD to be able to differentiate between source or target operations in case both images are located on the same node. This parameter is available only when both images are on the same node.

This can be the case if, for example, an R2 and remote BCV image are used on the same node. Only specifying the node is not enough in this case. If the IASP file does not have an entry where the source and target node is the same, this parameter is set to the default value (TGTDEV).

For any other control actions this parameter is set to default and has no effect.

Examples

Add IOAs to the IASP image (PIASP2) with target devices to the backup node

IASPCTLC IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(2) ACTION(ADDIOA) NODENAME(NODE)

Rebuild the IOA file for the IASP image (PIASP2)

IASPCTLC IMAGENAME(PIASP2) PATHNAME(REMOTEBCV) STEPNUM(1) ACTION(REBUILDIOA) NODENAME(NODE)

IASPCTLHA Pushes configuration files to the selected target HA host and prepares this host to act as the primary host.

Syntax

IASPCTLHA

ACTION(Control_action)

IMAGENAME(image_name1 image_name2...image_name(n)|*ALL)

TGTNAME(node)

PORTNUM(port_number)

Description

IASPCTLHA pushes configuration files to the selected target HA host and prepares this host to act as the primary host.

Using IASPCTLHA with the control action SWHAIASP rebuilds the IOA file for step 1 on a primary or HA node then pushes the files to the other DR or backup nodes. It is used during original configuration steps on the HA node then when returning to the primary node. After that is only needed when there are configuration changes.

Control action CFGHAIASP is typically used on the primary node, while the control action SWHAIASP is typically used on the HA node.

Extended Features Commands Reference 229

RSTHAIASP is run on the primary node and HA node after the original configuration process is complete to restore original configuration files, and pushes configuration files to target nodes in the cluster, as defined in the IASP file.

NOTE: When RSTHAIASP is used on a node, you do not need to run the STRSTMSRV command. RSTHAIASP automatically restarts the server.

Required parameters

ACTION(Control_action)

Specifies the control action to perform:

CFGHAIASP Makes copies of the original configuration files, then pushes configuration files to the selected target HA node.

SWHAIASP Switches configuration files on the HA node so that this node acts as the primary node. It pushes the updated configuration files to target nodes in the cluster, as defined in the IASP file, and performs a rebuild of the IOAs for all steps 1 in the configuration.

RSTHAIASP Restores the original configuration files to the primary node or HA node that were saved during the CFGHAIASP action.

IMAGENAME(Image_name1... imagename(n))|*ALL))

Specifies which IASP image configuration files to push to the HA node. The command should be used only for IASP images. Use *ALL for all images. This is the default.

TGTNAME(node)

The HA node where the configuration files must be sent. The node name entered must be part of the cluster that is configured on this system. If this is not the case a message appears indicating that the node cannot be found.

PORTNUM(Port_number)

The TCP/IP port number.

The default value is 8000. If you use a different port number, keep the port number consistent on all nodes participating in IASP operations.

Examples

IASPCTLHA IMAGENAME(IASP1 IASP2 IASP3) TGTNAME(HANODE) PORTNUM(8000) ACTION(CFGHAIASP) IASPCTLHA IMAGENAME(*ALL) TGTNAME(HANODE) PORTNUM(8000) ACTION(CFGHAIASP)

IASPFAILBK Performs a failback of IASP images from the DR node to the primary node in one step, and is used when IASPFAILOV command is used with OPTION *NO.

The IASPFAILBK command is typically used if no additional user intervention is required for the failback operation. If there are situations where user setup scripts need to be run or the DR machine requires changes before the IASP is varied off, you can use the multi-step failback procedure (see IASP-supported operations). However, you can modify the script used to run this command to add user-specific actions. See Modifying the script for the IASPFAILBK command for instructions on modifying the script.

Syntax

IASPFAILBK

IMAGE_NAME(Image_name)

PATH_NAME(Path_name)

230 Extended Features Commands Reference

STEPNUM(Step_number)

Description

IASPFAILBK performs a failback on IASP images from the DR node to the primary node. After the required parameters are entered, the system then performs all the necessary steps to complete the IASP failback. See Command execution steps for a description of the command steps.

IASPFAILBK command must be performed from the backup node.

You can enter the command, with the required parameters, on the command line as shown in the example below. If you enter the command without parameters, the IASP Fail Back Procedure screen appears.

Required parameters

IMAGENAME(Image_name)

The name of the IASP image to be used in a failback operation.

PATHNAME(Path_name)

The path name associated with an IASP image to be used in a failback operation.

STEPNUM(Step_number)

The specific step number for which the control action is initiated in a failback operation.

Examples

IASPFAILBK IMAGENAME(P1IASP2) PATHNAME(REMOTEBCV) STEPNUM(1)

NOTE: When running IASPFAILBK from the command line, a confirmation screen appears and asks if you want to continue with the operation.

Command execution steps

The IASPFAILBK command does the following:

1. Checks the IASP files for valid input and configuration.

2. Checks the local IASP status to ensure it is offline.

3. Checks the SRDF status to ensure it is in failed over state.

4. Checks that the remote system is active.

5. Checks the remote IASP status to ensure it is offline.

6. Removes the IOAs for both the source and target IASP.

7. Carries out the failback operation.

8. Once failback is complete, adds an IOA for the user-selected IASP and step number on the primary node.

9. Varies on the user-selected IASP image on the primary node.

Extended Features Commands Reference 231

Modifying the script for the IASPFAILBK command

User-specific actions can be included in the IASPFAILBK command by editing the script that generates the failback command, as follows:

NOTE: In the EMCCTLC client library there is a Source Physical File called QCLSRC that contains the scripts needed for the failback operation, COMPILE.CLP and IASPFAILBK.CLLE.

1. Locate the IASPFAILBK.CLLE script and make desired changes to the script.

2. Compile the COMPILE.CLP script as follows:

CRTCLPGM PGM(EMCCTLC/COMPILE) SRCFILE(EMCCTLC/QCLSRC)

3. Execute the COMPILE program as follows:

CALL COMPILE PARM(<SRCLIB> <TGTLIB> <RELEASE>)

Where:

SRCLIB is the library where the IASPUTIL module and the QCLSRC file are located. Both files are located in the EMCCTLC library.

TGTLIB is the library where the compiled programs will be located.

RELEASE is the earliest operating system release level the program is allowed to run on.

Running the COMPILE program generates the user-modified IASPFAILOV, IASPFAILBK, IASPTFBCK, and IASPTFEST commands and programs.

NOTE: The COMPILE.CLP can be also be edited and compiled (as shown in step 2).

IASPFAILOV Performs a failover of IASP images from the primary node to the DR node in one step. To go back to the original state, run IASPFAILOV again on the DR node. When OPTION *NO is used the first time to do a failover, run the IASPFAILBK command to go back to the original state.

The IASPFAILOV command is typically used if no additional user intervention is required for the failover operation. If there are situations where user setup scripts need to be run, or the DR machine requires changes before the IASP is varied on, use the multi-step failover procedure (see IASP-supported operations). However, you can modify the script used to run this command to add user-specific actions. See Modifying the script for the IASPFAILOV command for instructions on modifying the script.

Syntax

IASPFAILOV

IMAGE_NAME(Image_name)

PATH_NAME(Path_name)

STEPNUM(Step_number)

[OPTION(*NO|ESTABLISH|RESTORE)]

Description

IASPFAILOV performs a failover of IASP images from the primary node to the DR node. After the required parameters are entered, the system then performs all the necessary steps to complete the IASP failover. See Command execution steps for a description of the command steps.

Run the IASPFAILOV command from the DR node.

You can enter the command from the command line with the required parameters, as shown in the example below. If you enter the command without parameters, the IASP fail over Procedure screen appears (Figure 103).

232 Extended Features Commands Reference

Required parameters

IMAGE_NAME(Image_name)

The name of the IASP image to be used in a failover operation.

PATH_NAME(Path_name)

The path name associated with an IASP image to be used in a failover operation.

STEPNUM(Step_number)

The specific step number for which the control action is initiated in a failover operation.

Optional parameters

OPTION(*NO|ESTABLISH|RESTORE)

Controls the failover operation:

*NO Devices are left in the failed over state. This is the default.

ESTABLISH With dynamic SRDF, the specified devices are failed over, swapped and then re-established. In SRDF asynchronous mode, consistency protection is automatically enabled after an ESTABLISH operation executes.

RESTORE same as the ESTABLISH option except that after the swap, invalid tracks on the new R2 side (the original R1 side) are restored on the new R1 side (the original R2 side).

Examples

IASPFAILOV IMAGENAME(P1IASP2) PATHNAME(REMOTEBCV) STEPNUM(1) OPTION(*NO)

NOTE: When running IASPFAILOV from the command line, a confirmation screen appears that asks if you want to continue with the operation.

Command execution steps

The IASPFAILOV command does the following:

1. Checks the IASP files for valid input and configuration.

2. Checks the local IASP status to ensure it is offline.

3. Checks the SRDF status to ensure it is synchronized.

4. Checks that the remote system is active.

5. Checks the remote IASP status to ensure it is offline.

6. Removes the IOAs for both the source and target IASP.

7. Carries out the failover operation.

8. Once failover is complete, adds an IOA for the user-selected IASP and step number.

9. Varies on the user-selected IASP image on the DR node.

Modifying the script for the IASPFAILOV command

You can add user-specific actions to the IASPFAILOV command by editing the script that generates the command, as follows:

NOTE: In the EMCCTLC client library there is a Source Physical File called QCLSRC that contains the scripts needed for the failback operation, COMPILE.CLP and IASPFAILOV.CLLE.

1. Locate the IASPFAILOV.CLLE script and make desired changes to the script.

2. Compile the COMPILE.CLP script as follows:

Extended Features Commands Reference 233

CRTCLPGM PGM(EMCCTLC/COMPILE) SRCFILE(EMCCTLC/QCLSRC)

3. Execute the COMPILE program as follows:

CALL COMPILE PARM(<SRCLIB> <TGTLIB> <RELEASE>)

Where:

SRCLIB is the library where the IASPUTIL module and the QCLSRC file are located. Both files are located in the EMCCTLC library.

TGTLIB is the library where the compiled programs are located.

RELEASE is the earliest operating system release level the program can run on.

Running the COMPILE program generates the user-modified IASPFAILOV, IASPFAILBK, IASPTFBCK, and IASPTFEST commands and programs.

NOTE: The COMPILE.CLP can be also be edited and compiled (as shown in step 2 ).

IASPFILE Removes image information.

Syntax

IASPFILE

ACTION(Control_action)

IMAGENAME(image_name)

[PATHNAME(pathname|*ALL)]

Description

IASPFILE removes image information from the IASPs and ISRCIOA files for a specified image.

To remove image information run the command from each node in the DR setup.

Required parameters

ACTION(Control_action)

Specifies the control action to perform:

RMVIASPIMG removes image information.

IMAGENAME(image_name)

The name of the image.

Optional parameters

PATHNAME(path_name|*ALL)

The name of the path associated with the image specified in the IMAGENAME parameter. Use *ALL to specify all paths of the image specified in the IMAGENAME parameter.

234 Extended Features Commands Reference

Examples

IASPFILE ACTION(RMVIASPIMG) IMAGENAME(IASPIMAGE) PATHNAME(*ALL)

IASPTFBCK Prepares the source and target node for TimeFinder backup operations on IASPs.

IASPTFBCK

IMAGE_NAME(Image_name)

PATH_NAME(Path_name)

STEPNUM(Step_number)

[SNAPVX(*YES|*NO)]

SPLIT_MODE(CHG_ASP_ACT|SPLITWA|MAINTENANCE)

[SNAPVXNAME(snapshot_name)]

[SNAPVXGEN(snapshot_generation)]

[SNAPVXTTL(DAYS|DATE)]

[LINK_MODE(NOCOPY|COPY)]

[TTL_DAYS(1-400)]

[TTL_DATE(Date)]

Description

Prepares the source and target node for TimeFinder backup operations on IASPs. After the required parameters are entered, the system performs all the necessary steps to prepare the source and target nodes for backup. See Command execution steps for a description of the command steps.

The IASPTFBCK command must be executed from the target node, and the STM server must be running.

Required parameters

IMAGE_NAME(Image_name)

The name of the IASP image to be used in a backup operation.

PATH_NAME(Path_name)

The path name associated with an IASP image to be used in a backup operation.

STEPNUM(Step_number)

The specific step number for which the control action is initiated in a backup operation.

SPLIT_MODE(CHG_ASP_ACT|SPLITWA|MAINTENANCE)

Specifies the method for stopping writes to the devices in the image:

Extended Features Commands Reference 235

CHG_ASP_ACT Executes the operation after suspending initiation of new transactions and operations.

NOTE: The selected IASP image that uses the Change ASP Activity CL command (CHGASPACT) is quiesced at the start of new commitment control transactions, new database change operations, and new Integrated File System (IFS) change operations. The command suspends initiation of new transactions and operations before the split, writes changes to auxiliary storage, and resumes initiations of new transactions and operations after the split.

SPLITWA - Executes the operation after holding I/Os on the array. It splits a local or remote BCV or Clone image while the source system is operational. The resulting image is consistent and holds data upon the last commit.

With TimeFinder/CG (SPLITWA) operations, you do not have to put the selected IASP in the quiesced state.

SRDF/TimeFinder Manager client (the DR node) and the controlling host must have a gatekeeper configured on each locally attached array. When using the same controlling host for Primary and DR nodes, the controlling host must have additional gatekeeper device configured on each remotely attached array (local to the DR node). For detailed information on array gatekeeper management, see the Solutions Enabler Installation and Configuration Guide.

NOTE: On the client, the netcnfg file must be configured using the CRTNETCNFG command. This ensures that correct information (node name, IP address, port, and security level) points to the remote server. Only non-secure connections are supported for IBM i.

NOTE: When using this split type, the data in main memory is not included in the image. Only use SPLITWA when the host and applications are in a quiescent state. If this is not suitable for your business needs, use other operating system functions such as journaling and database commitment control to create an image that includes the last transaction.

MAINTENANCE Splits or suspends SRDF links or split BCV pairs or activates a virtual copy session or Clone copy session in maintenance mode (that is, no interference with host operations).

Optional parameters

SNAPVX

Controls whether the system displays values of the parameters relating to SnapVX to the user. Set the value to *YES to display the values. The default value is *NO.

SNAPVXNAME

The name of the Snapshot.

SNAPVXGEN

The Generation of the Snapshot. For all SnapVX control actions, except ESTABLISH, specifies the generation of the existing snapshots to be operated on. If no generation is set, the most recent snapshot is used for the control action.

SNAPVXTTL

The Time to Live for the Snapshot. The possible values are:

DAYS -Specifies the time to live in days.

DATE - Specifies a date for the snapshot time to live.

If you do not specify a value, the Time to Live is set to unlimited and the Snapshot is kept until manually terminated.

LINK_MODE(NOCOPY|COPY)

The mode used for a LINK SnapVX operation. Options are as follows:

NOCOPY The target does not retain point-in-time data once the link is removed, and any previous target data is lost. This is the default.

NOTE: NOCOPY is not available when running PowerMax 10 (6079).

COPY Data is physically copied to the target devices. When the link is terminated the data is retained on the target.

TTL_DAYS

Time to Live in days. The value in days can be set to any value between 1 and 400.

TTL_DATE

236 Extended Features Commands Reference

Specifies a date for the snapshot time to live in the form MM/DD/YYYY (month/day/year) with reference to the host time. The specified date may be up to 400 days in the future.

Examples

You can enter the command from the command line with the required parameters, as shown in the example below. If you enter the command without parameters, the IASP TimeFinder Backup Procedure screen appears (Figure 104).

IASPTFBCK IMAGE_NAME(P1IASP2) PATH_NAME(REMOTEBCV) STEPNUM(2)SPLIT_MODE(SPLITWA)

Command execution steps

1. Checks the IASP files for valid input and configuration.

2. Checks the local IASP status to ensure it is offline.

3. Checks that the source system is up.

4. Checks that the link status is Synchonized, Precopy or Recreated.

5. Checks for SnapVX.

6. Carries out the Split/Activate control action.

7. Adds the target IOAs and varies on the target node.

8. Removes the IOAs for the IASP from the source system.

Modifying the script for the IASPTFBCK command

You can add user-specific actions to the IASPTFBCK command by editing the script that generates the command, as follows:

NOTE: In the EMCCTLC client library, there is a Source Physical File called QCLSRC that contains the scripts needed for the failback operation, COMPILE.CLP and IASPTFBCK.CLLE.

1. Locate the IASPTFBCK.CLLE script and make desired changes to the script.

2. Compile the COMPILE.CLP script:

CRTCLPGM PGM(EMCCTLC/COMPILE) SRCFILE(EMCCTLC/QCLSRC)

3. Execute the COMPILE program:

CALL COMPILE PARM(<SRCLIB> <TGTLIB> <RELEASE>)

Where:

SRCLIB is the library where the IASPUTIL module and the QCLSRC file are located. Both files are located in the EMCCTLC library.

TGTLIB is the library where the compiled programs are located.

RELEASE is the earliest operating system release level the program can run on.

Running the COMPILE program generates the user-modified IASPFAILBK, IASPTFBCK, and IASPTFEST commands and programs.

4. The COMPILE.CLP can be also be edited and compiled (as shown in step 2 ).

IASPTFEST Prepares the source and target to go back to original state prior to running the IASPTFBCK operation.

IASPTFEST

IMAGE_NAME(Image_name)

PATH_NAME(Path_name)

Extended Features Commands Reference 237

STEPNUM(Step_number)

Description

Prepares the source and target to go back to original state prior to running the IASPTFBCK operation. After the required parameters are entered, the system then performs all the necessary steps to prepare the source and target nodes for restore. See Command execution steps for a description of the command steps.

Run the IASPTFEST command from the target node.

Required parameters

IMAGE_NAME(Image_name)

The name of the IASP image to be used in a restore operation.

PATH_NAME(Path_name)

The path name associated with an IASP image to be used in a restore operation.

STEPNUM(Step_number)

The specific step number for which the control action is initiated in a restore operation.

Examples

You can enter the command can be executed from the command line with the required parameters, as shown in the example below. If you enter the command without parameters, the IASP TimeFinder restore Procedure screen appears (Figure 102).

IASPTFEST IMAGE_NAME(P1IASP2) PATH_NAME(REMOTEBCV) STEPNUM(2)

Command execution steps

1. Checks the IASP files for valid input and configuration.

2. Checks that the local IASP status is offline.

3. Checks that the source system is up.

4. Removes the IOAs for the IASP from the target system.

5. Carries out an ESTABLISH/CREATE control action.

6. Carries out ADDIOA on the source node.

7. Varies on the source IASP.

Modifying the script for the IASPTFEST command

You can add user-specific actions to the IASPTFEST command by editing the script that generates the command, as follows:

NOTE: In the EMCCTLC client library there is a Source Physical File called QCLSRC that contains the scripts needed for the failback operation, COMPILE.CLP and IASPTFEST.CLLE.

1. Locate the IASPTFEST.CLLE script and make desired changes to the script.

2. Compile the COMPILE.CLP script:

CRTCLPGM PGM(EMCCTLC/COMPILE) SRCFILE(EMCCTLC/QCLSRC)

3. Execute the COMPILE program:

CALL COMPILE PARM(<SRCLIB> <TGTLIB> <RELEASE>)

Where:

238 Extended Features Commands Reference

SRCLIB is the library where the IASPUTIL module and the QCLSRC file are located. Both files are located in the EMCCTLC library.

TGTLIB is the library where the compiled programs will be located.

RELEASE is the earliest operating system release level the program is allowed to run on.

Running the COMPILE program generates the user-modified IASPFAILBK, IASPTFBCK, and IASPTFEST commands and programs.

4. The COMPILE.CLP can be also be edited and compiled (as shown in step 2 ).

RELDEVLCK Checks and releases device external locks (DEL) on an array for any image.

See RELDEVLCK for more information.

RELDEVLCKC Checks and releases device external locks (DEL) on an array for any image on the target side.

See RELDEVLCKC for more information.

RTVSTMINF Returns status information for the selected image, path, and step. It also returns SRDF/TimeFinder Manager, Solutions Enabler, and I/O driver and release level information.

See RTVSTMINF for more information.

SETRDFMOD Sets the SRDF mode for a selected image.

See SETRDFMOD for more information.

SETRDFMODC Sets the SRDF mode for a selected image on the target side.

Syntax

SETRDFMODC IMAGE_NAME(image_name)

PATH_NAME(path_name)

STEPNUM(step_number)

MODE_TYPE(SYNC|ASYNC|ACDM|METRO)

Description

SETRFDMODC sets the SRDF mode (synchronous, asynchronous, adaptive copy disk mode (ACDM)), for a selected image on the target side only. You must specify the image name, path name, and the SRDF mode associated with the image.

All control commands executed on the DR or backup node use the image file built on the primary node and sent to the corresponding node. The path and step parameters should use the path name and step used on the primary node for corresponding devices.

Extended Features Commands Reference 239

Required parameters

IMAGE_NAME(image_name)

The name of the image to be used in an SRDF control operation.

PATH_NAME(path_name)

The name of the path for the image to be used in an SRDF operation.

STEPNUM(step_number)

The specific step number for which the control action is initiated in an SRDF control operation.

MODE_TYPE(SYNC|ASYNC|ACDM)

The parameter that sets the SRDF mode for a selected image to synchronous, asynchronous, or adaptive copy disk mode.

CAUTION: Do not use ACDM mode for SRDF while creating RDF or remote TimeFinder images (split) using SRDF/TimeFinder Manager. This is not supported. Instead, use Sync or Async mode.

Examples

SETRDFMODC IMAGE_NAME(PIASP2) PATH_NAME(SRDFA) STEPNUM(1) MODE_TYPE(SYNC) SETRDFMODC IMAGE_NAME(PIASP2) PATH_NAME(SRDFA) STEPNUM(1) MODE_TYPE(ASYNC) SETRDFMODC IMAGE_NAME(PIASP2) PATH_NAME(SRDFA) STEPNUM(1) MODE_TYPE(ACDM)

SRDFDRCTL Processes SRDF control actions for IASP images on the source host during disaster recovery situations.

Syntax

SRDFDRCTL IMAGE_NAME(Image_name)

PATH_NAME(Path_name)

STEPNUM(Step_number)

ACTION(Control_action)

[option(*NO|ESTABLISH|RESTORE)]

Description

SRDFDRCTL processes SRDF control actions for IASP images on the target (R2) side.

Required parameters

IMAGE_NAME(Image_name)

The name of the IASP image to be used in an SRDF control operation.

PATH_NAME(Path_name)

The path name associated with an IASP image to be used in an SRDF operation.

STEPNUM(Step_number)

240 Extended Features Commands Reference

The specific step number for which the control action is initiated in an SRDF operation.

ACTION(Control_action)

Specifies the control action to perform:

FAILOVER Switches data processing from the source (R1) side to the target (R2) side. If the source (R1) is operational, FAILOVER suspends I/O traffic on the RDF links and write disables devices on the source (R1) side to their hosts. FAILOVER then write enables the devices on the target side to their local hosts. When running in SRDF asynchronous mode and a FAILOVER is executed, the consistency protection is disabled and then the FAILOVER operation is performed.

With dynamic RDF, when you specify the ESTABLISH option, devices failover, swap, and then re-establish.

NOTE: With control action FAILOVER with the ESTABLISH option or the RESTORE flag is set, and the R2 mirror of the SRDF pair are on an array running PowerMaxOS 10 (6079), PowerMaxOS 5978, or HYPERMAX OS 5977 the RDF mode is automatically set to Adaptive Copy Disk

In SRDF/A mode, consistency protection is automatically enabled after an ESTABLISH operation executes.

For dynamic RDF, if option RESTORE is specified, devices failover, swap and then re-establish. Invalid tracks on the new R2 side (originally the R1 side) are restored to the new R1 side (formerly the R2 side).

When running in SRDF asynchronous mode, consistency protection is automatically enabled after executing an RESTORE operation.

FAILBACK Performs a source (R1) device takeover when you are ready to resume normal SRDF operations by initiating read/write operations on the source (R1) devices, and stopping read/write operations on the target (R2) devices. The target (R2) devices become read-only to their local hosts while the source (R1) devices are read/write enabled to their local hosts.

NOTE: In SRDF/A mode, consistency protection is automatically enabled after a FAILBACK operation executes.

NOTE: FAILBACK is only used if FAILOVER *NO was previously issued.

RESTORE Restores data from SRDF R2 data devices back to source devices.

The new data, that was updated on the target (R2) device while the SRDF pair was split, is copied to the source (R1) device. Any changed tracks on the source (R1) device are refreshed from the corresponding tracks on the target (R2) device. After the restore operation has successfully completed, the SRDF pairs synchronize. The RTVSMINF command can be used to confirm that the SRDF pairs are in a Synchronized state.

NOTE: The CLACT and IASPCTL commands using control action STATUS or the Work with Associated Paths screen can be used to confirm the status of SRDF pairs.

When an incremental restore is initiated for each specified SRDF pair in a device file:

The source (R1) device is write disabled for the local hosts.

The target (R2) device is write disabled for the local hosts.

Data traffic is suspended on the SRDF links.

The invalid tracks on the source (R1) device are refreshed with the changed tracks on the target (R2) side. The R1 and R2 track tables are merged.

Traffic is resumed on the SRDF links.

The source (R1) device is read/write enabled for the local hosts.

The SRDF pair is in the Synchronized state when the source (R1) device and the target (R2) device contain identical data.

The incremental restore operation will be rejected if the target has invalid local (R2) tracks.

NOTE: In SRDF/A mode, consistency protection is automatically enabled after a RESTORE operation executes.

Option(*NO|ESTABLISH|RESTORE)

Controls the failover operation:

*NO Devices are left in the failed over state. This is the default.

ESTABLISH With dynamic SRDF, the specified devices are failed over, swapped and then re-established. When running in SRDF asynchronous mode, consistency protection is automatically enabled after executing an ESTABLISH operation.

RESTORE Same as the ESTABLISH option except that after the swap, invalid tracks on the new R2 side (the original R1 side) are restored on the new R1 side (the original R2 side).

Extended Features Commands Reference 241

Examples

SRDFDRCTL IMAGE_NAME(DISKPOOL) PATH_NAME(REMOTEBCV) STEPNUM(1) ACTION(FAILOVER) OPTION(ESTABLISH)

STMRMTCMD Runs remote commands.

See STMRMTCMD for more information.

STRSTMSRV Starts the SRDF/TimeFinder Manager server job.

See STRSTMSRVfor more information.

Extended Features Messages 243

H

Extended Features Messages Invisible Body Tag

This appendix provides reference information about messagesthat may display for the extended features components, the reason for the message, and the recommended user action. See Standard Features Messages for messages that may display for standard feature components.

IAP0001

Application is waiting for synchronization to finish.

Cause: SRDF/TimeFinder Manager is waiting for device synchronization to complete.

Action: This is an informational message; no user action is necessary.

IAP0002

Application is waiting for split to finish.

Cause: SRDF/TimeFinder Manager is waiting for a Split operation to complete.

Action: This is an informational message; no user action is necessary.

IAP0003

Operation is not supported, please check product guide.

Cause: The attempted operation is not supported with IASP images.

Action: Refer to the appropriate section in this guide.

IAP0004

Operation failed, please use option #16 to configure the primary IASP.

Cause: The attempted operation on the primary IASP failed.

Action: Reconfigure the primary IASP and try the operation again.

IAP0005

ASP number in IASP file does not match ASP number generated by operating system, there might be an IASP system setup error.

Cause: The check to verify the IASP number returned an IASP number mismatch.

Action: Refer to the MATRMD section in the IBM documentation for details and take the following steps to verify the status of the IASP. Use SST to verify that all IOAs have been successfully added to the system and the devices are active.

If all devices in the IASP are active, use WRKCFGSTS CFGTYPE(*DEV) CFGD(IASP name) to verify the IASP status. If this was an ADDIOA operation, and the IOAs are on the system and the devices are active, continue with the VARYON of the IASP. If the IASP status is 'AVAILABLE', normal IASP operations can continue.

IAP0006

Failure opening ISRCIOA file with member &1 on node &2.

Cause: ISRCIOA file with member &1 was not found or was not able to be opened.

Action: Make sure that correct image name is used or that the product installation is completed successfully.

IAP0007

No IOAs of the target devices are found in file ISRCIOA.

244 Extended Features Messages

Cause: The IOA serial numbers of the target devices are not present in the ISRCIOA file.

Action: Rebuild the target device IOA file as documented in Building or rebuilding the IOA file.

IAP0008

The device SYMAPI status must be Synchronized/Created before a Split/Activate can occur.

Cause: An attempt was made to Split or Activate a device before the device has been synchronized or created.

Action: Correct the mistake and then attempt the Split or Activate operation again.

IAP0009

ISRCIOA file with member &1 on node &2 has no records.

Cause: ISRCIOA file with member &1 has no records. Make sure that the configuration process completed correctly.

Action: Rebuild the IOA file for both source devices and target devices as documented in Building or rebuilding the IOA file.

IAP0010

Application is locating disk units.

Cause: Missing disk units appear in the selected IASP.

Action: Wait until all missing disk units report for the selected IASP.

IAP0011

Missing disk units are detected in IASP prior to varying on the IASP.

Cause: Not all missing disk units report in the IASP image.

Action: Reset one or more IOAs to recover them. If the problem persists, IPL the host.

IAP0012

Devices need to be varied off before removal.

Cause: One or more selected devices must be varied off before removal.

Action: Vary off the selected devices.

IAP0013

Missing disk units are detected in IASP prior to varying on IASP.

Cause: Not all missing disk units report in the IASP image.

Action: Complete adding one or more IOAs before varying on the IOAs. If ADDIOA has been completed, try resetting the IOAs to recover the IASP devices. If the problem persists, IPL the host.

IAP0014

Devices must be varied on before rebuilding ISRCIOA file.

Cause: The selected devices are varied off.

Action: Vary on the devices to make them available.

IAP0015

File IASPS does not exist.

Cause: The file IASPs does not exist for the configuration.

Action: Make sure the installation completed successfully.

IAP0016

Cannot locate IASPS record to be sent.

Cause: The record for the selected IASP does not exist.

Action: Reconfigure the selected IASP.

Extended Features Messages 245

IAP0017

Socket communication failed, the operation is SEND.

Cause: The socket communication failed for the SEND operation.

Action: Check the TCP/IP configuration and hardware.

IAP0018

Socket communication failed, the operation is RECEIVE.

Cause: The socket communication failed for the RECEIVE operation.

Action: Check the TCP/IP configuration and hardware.

IAP0019

&1 finished successfully, please check job log for detail.

Cause: The operation finished successfully.

Action: This is an informational message; no user action is necessary.

IAP0020

&1.

Cause: This is the result of a specific action that is determined when the operation occurs.

Action: The corrective action to take, if any, depends on the operation performed. Most often this is an informational message; no user action is necessary.

IAP0021

&1.

Cause: This is the result of a specific action that is determined when the operation occurs.

Action: The corrective action to take, if any, depends on the operation performed. Most often this is an informational message; no user action is necessary.

IAP0022

Range of port number does not include value entered, or parameter entered for the port number must be numeric

Cause: The value specified for the port number must be a numeric value that is greater than or equal to 1 or less than or equal to 65535.

Action: Enter a numeric value that is within the specified range.

IAP0023

RESTORE action not allowed for path with R21 configured.

Cause: Path has R21 configured and cannot be used to do a restore.

Action: Select correct path and try again.

IAP0024

Parameter NODENAME required.

Cause: A required parameter was not specified.

Action: Enter a value for parameter NODENAME.

IAP0025

Parameter TGTNAME required.

Cause: A required parameter was not specified.

Action: Enter a value for parameter TGTNAME.

246 Extended Features Messages

IAP0026

Node with name &2 not found in cluster.

Cause: Node name entered cannot be found in list of nodes that are configured in the cluster on this system.

Action: Enter a valid node name or add the node to the cluster and try again.

IAP0027

Cluster information could not be retrieved.

Cause: Cluster information could not be retrieved.

Action: Check if a cluster is configured correctly on this system. Cluster information is collected into a user space before processing. Check if user space CLUINFO is created in library SYMAPI.

IAP0029

Node name &1 not found in IASP file.

Cause: Node name &1 cannot be found in IASP file for selected image &2 path &3 and step

Action: Make sure that configuration is completed correctly and the IASP file contains the correct node name for the selected image path and step that is used.

IAP0030

&1 Node name &2 not valid for this control action.

Cause: &1 Node name &2 cannot be used or is not valid for this control action.

Action: Make sure that node name &2 is valid for selected control action.

IAP0031

Failure opening IASPS file on node &1.

Cause: IASPS file was not found or was not able to be opened.

IAP0032

IASPS file on node &1 has no records.

Cause: IASPS file has no records. Make sure that the configuration process completed correctly.

IAP0033

Record read from IASPS file for selected image/path/step does not contain correct data.

Cause: Expected amount of data read from IASPS file did not match required data length.

Action: Make sure that the configuration process (option #16) completed correctly for selected image. Check if there is an entry for this image in the IASP file.

IAP0034

Previous step is not configured. Previous step &4 not found in IASP file for image &1 path &2.

Cause: Previous step &4 need to be configured first before using configuring step &3

Action: Make sure that the configuration process (option #16, or IASPCTL with option CONFIG) completed correctly for step &4 before attempting to configure step &3.

IAP0035

IASP status on node &1 could not be retrieved.

Action: Check joblog for details.

IAP0036

IASP &1 on node &2 with path &3 step &4 is not eligible for control action &5.

Cause: Selected control action cannot be used with this path.

Extended Features Messages 247

Action: Use a different control action with this path type.

IAP0037

&1 IOA(s) connected to IASP &2 and path &3 step &4 on node &5 are still active.

Cause: IOAs for selected IASP &2 are still active.

Action: In order to complete this control action, the IOAs need to be deactivated (removed) first.

IAP0038

&1 IOA(s) connected to IASP &2 and path &3 step &4 on node &5 are already deactivated (removed).

Cause: IOAs for selected IASP &1 are already deactivated (removed).

IAP0039

&1 IOA(s) connected to IASP &2 and path &3, step &4 on node &5 are already activated (added).

Cause: IOAs for selected IASP &1 are already activated (added).

IAP0040

IOA(s) connected to IASP &1 and path &2 step &3 on node &4 are not in the same state.

Cause: IOAs for selected IASP &1 are not in the same state.

Action: Use SST to check the state of the IOAs that are connected to this IASP.

IAP0041

One or more of the IOA(s) for IASP &1 and path &2 step &3 on node &4 is not dedicated.

Cause: To be able to activate or deactivate IOAs connected to this IASP &1, it is required that the IOAs are NOT shared between ASPs.

Action: Use SST to check the state of the IOAs that are connected to this IASP. Change configuration of the IOAs and retry.

IAP0042

Could not find any IOA configured for IASP &1 and path &2 step &3 on node &4.

Cause: IOAs for selected IASP &1 could not be found.

Action: Make sure that the configuration was completed correctly. Use SST to check the state of the IOAs that are connected to this IASP.

IAP0043

Could not detect status of the IOAs configured for IASP &1 and path &2 step &3 on node &4.

Cause: Status IOAs for selected IASP &1 could not be retrieved.

Action: Make sure that the configuration was completed correctly. Use SST to check the state of the IOAs that are connected to this IASP.

IAP0044

IASP &1 has IOAs activated for other path &2 step &3 on node &4.

Cause: IASP &1 has IOAs active for paths that have same image and target node.

Action: Make sure that IASP &1 is only presented once to the node. Use SST to check the state of the IOAs that are connected to this IASP.

IAP0045

HA IASP Operation &1 failed. Selected node name &2 is equal to local node name.

Cause: Selected node name &2 that is going to act as the HA node is equal to local node name.

Action: Use a different node name for the HA node. Change input and try again.

248 Extended Features Messages

IAP0046

The STM Server job on the Primary node &2 is still active during HA IASP operation &1.

Cause: The STM Server job on primary node &2 as defined in the IASP file is still active.

Action: Stop the STM Server job on the primary node &2 and try again.

IAP0047

HA IASP operation &1 failed.

Cause: Command &2 failed.

Action: Check joblog for details.

IAP0048

Disk management operation failed for IASP &1 on node &2.

Cause: Maybe a SST session is already active on the selected node.

Action: End all SST sessions, IBM i Access sessions and any other programs that have access to DASD management tools and try again.

IAP0049

STM Server on node &1 with port number &2 not ended.

Action: Check joblog for details.

IAP0050

STM Server with port number &1 ended.

IAP0051

Data queue not found.

Cause: API &1 failed with message id &2.

Action: Check joblog on remote node for details.

IAP0052

Data queue read failed.

Cause: API &1 returned no data.

Action: Check job log on remote node for details.

IAP0053

User space not created.

Cause: API QUSCRTUS failed with message id &1.

Action: Check job log on remote node for details.

IAP0054

User space pointer not resolved.

Cause: API &1 failed with message id &2.

Action: Check job log on remote node for details.

IAP0055

Spawn process failed. Path to program : &1. Cause: &2

Action: Check job log on remote node for details.

Extended Features Messages 249

IAP0056

Command failed with message id &1. Command: &2

Action: Check job log for details.

IAP0057

Spool file info not found.

Cause: API &1 failed with message id &2.

Action: Check joblog on remote node for details.

IAP0058

Remote command work file &1 open failed.

Cause: &2

Action: Check job log on remote node for details.

IAP0059

Spool file information not received.

Cause: Number of spool files received from STM server is 0.

Action: Check job log on remote node for details.

IAP0060

Remote command failed with message id &1. Command: &4.

Action: Check file &2 on this node or check joblog for job &3 on remote node for details.

IAP0061

Job information not found.

Action: Check job log on remote node for details.

IAP0062

Failure opening PATH file on node &1.

Cause: PATH file was not found or was not able to be opened.

IAP0063

Path &1 was not found for the iasp image &2.

Cause: Path name could not be found in list.

Action: Enter appropriate path name or check if configuration completed correctly and try operation again.

IAP0064

Step number &1 was not found for the path &2 and image &3.

Cause: Step number could not be found in list.

Action: Enter appropriate step or check if configuration completed correctly and try operation again.

IAP0065

Snapshot name is not valid.

Action: Provide a valid snapshot name and try the operation again.

250 Extended Features Messages

IAP0066

Snapshot generation value is not valid.

Action: Provide a valid value for the generation option and try the operation again

IAP0067

Snapshot time to live (TTL) value is not valid.

Action: Provide a valid time to live value and try the operation again.

IAP0068

New snapshot name is not valid.

Action: Provide a valid new snapshot name and try the operation again.'

IAP0069

Invalid date specified.

Cause: A date is not in the required format of MM/DD/YYYY, with reference to the current node date.

Action: Provide a date in the required format that is up to 400 days in the future from the current node date and try the operation again.

IAP0070

Remote command not allowed to run. Command: &1.

Cause: Commands allowed to run are all commands included in the STM product library. Also the following IBM commands can be run through the STM server: PING, APING, DSPASPSTS, VRYCFG, VFYTCPCNN, and WRKCFGSTS.

Action: Either change the command or use the REXEC server to execute the unsupported commands

IAP9897

Command &1 failed. Recovery.............: Check joblog for details

Cause: The command &1 failed to complete.

Action: Check the job log for cause.

IAP9898

Command &1 finished successfully.

Cause: Notification that the command &1 completed successfully.

Action: Informational message. No action is necessary.

Glossary 251

Glossary

This glossary contains terms related to business continuance operations and disk storage subsystems as they relate to Dell EMC SRDF/TimeFinder Manager for IBM i and Dell storage arrays.

A adapter

Card that provides the physical interface between the director and disk devices, director and serial channels (Serial adapter).

ASPs

Individual disks (storage units) or sets of disks reserved for particular objects (such as libraries). ASPs help organize data to limit the impact of storage-device failures and reduce recovery time. ASPs can be used to isolate those objects to facilitate backup and recovery.

B backup node

The partition or host that is the secondary owner for a particular IASP. The backup node has target devices connected to it.

BCV devices

Standard array devices with special attributes that allow the devices to independently support applications and processes. BCVs are active production images that are logically or physically separate from the production volumes with no reliance on the production host, thus providing protection from physical or logical corruption. Once the BCV task is complete, the volume can be resynchronized with the production volume, reassigned to another production volume, or maintained as is for another task. See also standard devices

BCV mirror

A standard device mirror (one of M2, M3, or M4) assigned to the BCV device upon establishing or re-establishing a BCV pair. See also establish re-establish and BCV pair.

BCV pair

Consists of a standard device and a BCV device attached together.

business continuance (BC) processes

Processes that allow customers to access and manage instant copies of standard devices. See also establish, re-establish, and Split.

business continuance volume (BCV)

See BCV devices.

C cache

Random access electronic storage used to retain frequently used data from disk for faster access by the channel.

cache slot

Unit of cache equivalent to one track.

channel director

The component in the array subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.

concurrent established BCV pair

The relationship that establishes two BCV devices as concurrent mirrors of a single standard device that allows two synchronized copies of the standard data to be created simultaneously.

252 Glossary

consistency group

A composite group is a user-defined group of devices that can span multiple arrays and, if needed, provide consistency protection. When an SRDF composite group is enabled for consistency protection, it is known as an SRDF consistency group. Consistency means that the devices within the group act in unison to preserve dependent-write consistency of a database that may be distributed across multiple arrays or multiple SRDF groups within a single. (A device group can be used for consistency protection if the group of devices is within a single SRDF group in a single array.)

CRG (Cluster Resource group)

A Cluster resource group is a a set or grouping of cluster resources that are used to manage events that occur in a high availability environment.

D DA

Disk Adapter. See disk director.

data availability

Access to any and all user data by the application.

DATA device

A device that holds the actual storage space for the data written to a thin device. DATA devices are located in a thin pool.

define BCV pair

The process of identifying a BCV device and a standard device to be established.

delayed fast write

No existence of room in cache for the data presented by the write operation.

dependent-write I/O

An I/O that cannot be issued until a related predecessor I/O has completed. Most applications have embedded dependent-write logic to ensure data integrity in the event of a failure in the host or server processor, software, storage subsystem, or if an environmental power failure occurs.

dependent-write consistency

Dependent-write consistency is a data state where data integrity is guaranteed by dependent-write I/Os embedded in application logic. Database management systems are examples of applications that utilize the dependent-write consistency strategy.

destage

The asynchronous write of new or updated data from cache to disk device.

device

A uniquely addressable part of the array 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

A hexadecimal value that uniquely defines a physical I/O device on a channel path. A SCSI address consists of a Target ID and a Logical Unit Number (LUN).

device number

The value that logically identifies a disk device in a string.

Direct access storage device (DASD)

Most commonly known as a magnetic disk device.

director

The component in the array subsystem that allows the array to transfer data between the host channels and disk devices. See also channel director and disk director.

Glossary 253

disaster recovery

The process of restoring a previous copy of the data and applying logs or other necessary processes to that copy to bring it to a known point of consistency.

disaster recovery (DR) node

The node that takes over when the primary node fails in a three-node solution.

disk director

The component in the array subsystem that interfaces between cache and the disk devices.

disk pool

An auxiliary storage pool (ASP) of disks only. See also ASPs.

DR node

See disaster recovery (DR) node.

DSS

Decision Support Systems. Database software used to support management decision making. Database data is extracted and analyzed, but not modified.

dual-Initiator

An array feature that automatically creates a backup data path to the disk devices serviced directly by a disk director if that disk director or the disk management hardware for those devices fails.

dynamic sparing

An array feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all non mirrored devices in the array subsystem.

dynamic SRDF pairing

The process of creating or deleting SRDF pairs while the array is in operation. Once created, these RDF pairs can be synchronized and managed the same as static RDF pairs that are paired during initial array configuration.

E EA

ESCON Adapter.

establish

A Business Continuance process which assigns a BCV device as the next available mirror of a standard device.

established

The BCV pair condition where the BCV device and standard device are synchronized and functioning as an array mirror. A BCV pair is established by the BCV commands establish and re-establish.

F fast-wide SCSI channel director

The component in the array subsystem that interfaces between host SCSI channels and data storage. It transfers data between the channel and cache.

FC

Fibre Channel. See Fibre Channel director.

Fibre Channel director

The component in the array subsystem that interfaces between the host fibre channel interface and data storage. A Fibre Channel Director transfers data between the channel and cache.

254 Glossary

G gatekeeper

A small logical volume used to pass SCSI commands from a host to the array.

H head and disk assembly (HDA)

A field replaceable unit in the array subsystem containing the disk and actuator.

hyper-volume extension

The ability to define more than one logical volume on a single physical disk device making use of its full formatted capacity. These logical volumes are user-selectable in size. The minimum volume size is one cylinder and the maximum size depends on the disk device capacity and the mode selected.

I IASP

An independent disk pool, or independent auxiliary storage pool (ASP). An IASP is a collection of disks that can be brought online or taken offline independently from the remainder of the systems storage, which includes the system ASP, user ASPs, and other independent disk pools. An IASP can be either:

Switchable among multiple systems in a clustered environment. Privately connected to a single server.

identifier (ID)

A sequence of bits or characters that identifies a program, device, controller, or system.

IFS

Integrated File System.

image

The ASP set that can be operated on simultaneously.

image types

There are several image types (UDFS IASP or an image containing primary and all secondary IASPs that belong to the same ASP group). See also System image and UDFS.

IML

Initial microcode program loading.

incremental establish

A time-saving operation similar to an Establish. The source (R1) device copies to the target (R2) device only the new data that was updated on the source R1 device while the SRDF pair was split. Any changed tracks on the target (R2) device are also refreshed from the corresponding tracks on the source (R1) device. The R2 device is write disabled to the target host.

independent auxiliary storage pool

See IASP.

instant split

A method of splitting a BCV that improves the performance of a typical split operation by performing a quick foreground BCV split, which reduces the time the application needs to be frozen and is shorter than using a regular Split.

I/O device

An addressable input/output unit, such as a disk device.

K Kilobyte (K)

1024 bytes.

Glossary 255

L least recently used algorithm (LRU)

The algorithm used to identify and make cache space available by removing the least recently used data.

logical partition

A subset of a single IBM i host that contains resources (processors, memory, and input/output devices). A logical partition operates as an independent system. When hardware requirements are met, multiple logical partitions can exist within a system.

logical volume

A user-addressable unit of storage. In the array subsystem, the user can define multiple logical volumes on a single physical disk device. Logical volumes can reside on an SRDF-enabled array, but do not participate in SRDF activity. Local volumes are typically protected either by local mirroring, RAID-S, or a dynamic spare.

LPAR

A function of the OS/400 licensed program that enables the creation of logical partitions.

M media

The disk surface on which data is stored.

meta device

A logical device that spans multiple physical devices, which are concatenated to create larger devices. A meta device consists of a meta head and its member devices. The meta head is the first device in the meta device sequence and is responsible for receiving all incoming commands. It also identifies the entire meta device. When an incoming command for the metahead is processed, the array determines which meta device member should execute the command. Meta head devices can be added to a device group, however, a meta member cannot be added to a device group. This holds true for both standard and BCV devices. In an SRDF configuration, you can create meta devices for both primary and secondary volumes.

MII

Machine Initiated Interrupt.

Mirroring

The array maintains identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, the array automatically uses the other disk devices.

Mirrored pair

A logical volume comprised of two or more physical devices with all data recorded on each device.

P point of consistency

A point in time to which data can be restored and recovered or restarted and maintain integrity for all data and applications.

primary LPAR

The partition identifier (0) on an IBM i host.

primary node

The partition or host that is the primary owner for a particular IASP.

private ASP

A private independent ASP that is owned by a single system or a single logical partition. See also ASPs

promotion

The process of moving data from a track on the disk device to cache. See also stage

256 Glossary

protected BCV establish

The process of moving all mirrors of locally-mirrored BCV devices to join the mirrors of a standard device.

Q query

A command that reports the state of all BCV devices in the system.

R R1

See source volume (R1).

R2

See target volume (R2).

RA

RLD Adapter. See SRDF remote link director.

RAID

Redundant Array of Independent Disks.

RDF/A DSE pool

A collection of SAVE devices used for SRDF/A DSE. Also called RDF/A DSE Save Pool or RDF/A DSE Save Device Pool.

read hit

Data requested by the read operation is in cache.

read miss

Data requested by the read operation is not in cache.

re-establish

A BC process which reassigns a BCV device as the next available mirror of the standard device with which it was previously paired. The BCV mirror is updated with the data that was written to the standard device during the period that the BCV pair was split. The data that was written to the BCV device during the split is overwritten by data from the standard device.

restore

The process that reinstates a prior copy of the data.

rolling disaster

A series of events that lead up to a complete disaster. For example, the loss of a communication link occurs prior to a site failure. Most disasters are rolling disasters; their duration may be only milliseconds or up to hours.

S SA

SCSI Adapter. See fast-wide SCSI channel director.

scrubbing

The background process of reading, checking the error correction bits, and writing corrected data back to the source.

source image of an IASP

The set of the standard/R1 devices in a particular IASP.

Glossary 257

source volume (R1)

A logical volume that is participating in SRDF operations. It resides in the local array. All CPUs attached to the array may access a source volume for read/write operations. All writes to this primary source volume are mirrored (copied to a secondary target volume) in another array, which can be remote. A source volume is not available for local mirroring or dynamic sparing operations.

Split

A Business Continuance process that removes the BCV mirror from the existing BCV pair and assigns the BCV mirror back to its original device address. The BCV device then holds an instant copy of the data from the standard device.

source image of IASP

A set of standard/R1 devices in a particular IASP. See also ASPs

SRDF

Symmetrix Remote Data Facility. SRDF consists of the microcode and hardware required to support remote mirroring.

SRDF/Asynchronous mode

A combination of hardware and software that extends the capability of SRDF to support Asynchronous Ordered Writes that ensures a consistent copy of data for remote replication over unlimited distances, for a variety of uses. SRDF/A inherits all the advantages of SRDF/Synchronous (SRDF/S).

SRDF/A DSE

SRDF/A Delta Set Extension

SRDF remote link director

The Remote Link Director (RLD) is a 2-port, serial-channel director microcode configured as the link between the two arrays in a Symmetrix Remote Data Facility (SRDF) configuration.

stage

The process of writing data from a disk device to cache. See promotion and destage.

standard devices

Devices configured for normal array operation under a desired protection method (such as RAID 1, RAID 5, RAID 6, RAID-S, SRDF).

switchable IASP

An independent ASP that can switch between two separate IBM i hosts or separate LPARs. See also ASPs.

System ASP

An auxiliary storage pool consisting of system programs and system data. See also ASPs

System image

A combination of the system ASP and all user ASPs. SRDF/TimeFinder Manager references a System image as SYSTEM on its screens.

T target image of an IASP

A set of BCV/R2 devices comprising a mirror copy of an IASP. See also ASPs

target volume (R2)

A Logical volume that is participating in SRDF operations. It resides in the remote array. This secondary target volume is paired with a primary source volume in the local array 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.

TimeFinder

A business continuance solution that allows customers to use special devices (BCVs, Clones, and VDEVs) that contain copies of devices while the standard devices are on-line for regular array operation.

258 Glossary

U UDFS

See user defined file system (UDFS).

user defined file system (UDFS)

The user-defined file system that you create and manage. This file system resides on the auxiliary storage pool (ASP) or independent auxiliary storage pool (IASP) of your choice.

V validate

The action that makes all tracks for a source volume valid on a target volume.

vary off

The process of making an IASP image unavailable for its intended (normal) use. All primary and secondary disk pools in the IASP vary off together.

vary on

The process of making an IASP image available for its intended (normal) use. All primary and secondary disk pools in the IASP vary on together.

virtual device

A host-accessible device containing track-level location information (pointers), which indicate where the copy session data is located in the physical storage. Virtual devices consume minimal physical disk storage, as they store only the address pointers to the data stored on the source device.

Virtual Provisioning

Commonly known as thin p

Manualsnet FAQs

If you want to find out how the SRDF Dell works, you can view and download the Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide on the Manualsnet website.

Yes, we have the Product Guide for Dell SRDF as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Product Guide should include all the details that are needed to use a Dell SRDF. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell SRDF TimeFinder Manager IBM i 10.0.0 Storage Product Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.