EMC GDDR for SRDF/S with ConGroup Product Guide · PDF fileUsing OPSVIEW facilities for EMC GDDR administration ..... 159 Ensuring MSF connections between C-Systems

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

EMC® GDDR for SRDF®/S with ConGroupVersion 3.1

Product GuideP/N 300-009-934

REV A01

EMC GDDR Product Guide 2

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

Published September, 2009

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

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

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

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

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

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

Contents

Preface.................................................................................................................................................... 13

Chapter 1 Product Overview What is EMC GDDR?............................................................................................. 18 Major features.......................................................................................................... 19

Situational awareness ..................................................................................... 19Survivor recognition ........................................................................................ 19Restart coordination ......................................................................................... 19Additional capabilities..................................................................................... 20Types of environment ...................................................................................... 20

Supported business continuity configurations................................................... 21SRDF/S with ConGroup configuration ........................................................ 21

The EMC GDDR Complex .................................................................................... 23 EMC GDDR fundamentals.................................................................................... 24

Control systems ................................................................................................ 24Workload location ............................................................................................ 24Managed workloads......................................................................................... 25External workloads .......................................................................................... 25Excluded systems ............................................................................................. 25HMC-only systems........................................................................................... 25EMC GDDR processes ..................................................................................... 26

EMC GDDR components....................................................................................... 27Parameters ......................................................................................................... 27User interface .................................................................................................... 27Events ................................................................................................................. 27Monitors............................................................................................................. 27Message rules .................................................................................................... 28

EMC GDDR supported scripts ............................................................................. 29Planned event management............................................................................ 29Unplanned event management ...................................................................... 30Resumption after planned or unplanned outages....................................... 30

Parameter wizard: Telling EMC GDDR what to manage ................................. 31

Chapter 2 Installing EMC GDDR Preinstallation tasks................................................................................................ 34

Mainframe environment requirements ......................................................... 34Minimum software requirements .................................................................. 34Minimum hardware requirements ................................................................ 35


Contents

DASD support ................................................................................................... 35 Installation procedure............................................................................................. 36

Before you begin ............................................................................................... 36Gather EMC GDDR installation information ............................................... 37Install EMC GDDR............................................................................................ 38Run the installation jobs................................................................................... 43

Post-installation tasks ............................................................................................. 43

Chapter 3 Integrating EMC GDDR Overview .................................................................................................................. 46 Update system parameter files.............................................................................. 47 Authorize the EMC Consistency Group started task to use the trip API ....... 50 Perform ConGroup configuration ........................................................................ 51 Perform ConGroup Started Task automated startup......................................... 52 Specify EMC GDDR security................................................................................. 54

EMC GDDR RACF functional groups ........................................................... 54Summary of RACF permissions ..................................................................... 54EMC GDDR user interface security................................................................ 56RACF authorization for OMVS....................................................................... 58RACF authorization for HMC LPAR actions................................................ 58Mainframe Enablers EMCSAFI security interface authorization .............. 59

Install EMC GDDR C-System started procedures.............................................. 60Define GDDR data in virtual datasets ........................................................... 61Customize EMC z/OS Console Monitor started procedures..................... 61Customize member GDDRPROC................................................................... 62Allocate the parameter backup dataset and your parameter wizard work dataset....................................................................................................... 62

Customize CA-OPS/MVS for EMC GDDR ........................................................ 64Step 1: Include EMC GDDR libraries in OPSVIEW REXX exec ................. 64Step 2: Merge CA-OPS/MVS user applications (optional)......................... 64Step 3: Make EMC GDDR AOF rules available to CA-OPS/MVS ............ 65Step 4: Set REXX and TSO transaction limits in the CA-OPS/MVS OPSMAIN parameters ..................................................................................... 66Step 5: Enable SMF Support in CA-OPS/MVS............................................. 66Step 6: Change CA-OPS/MVS access rules .................................................. 67Step 7: Customize EMC GDDR user exit 7 (optional) ................................. 67Step 8: Update CA-OPS/MVS started procedure OPSOSF........................ 67Step 9: Update the UNIX system service directory...................................... 68Step 10: Define the EMC GDDR monitoring started tasks to CA-OPS/MVS SSM .......................................................................................... 68Step 11: Update CA-OPS/MVS CCI parameters.......................................... 69Step 12: Apply CA-OPSMVS Usermod ......................................................... 69

Modify CA-OPS/MVS to use the GDDRMSG table .......................................... 70 Configure EMC GDDR........................................................................................... 71

Step 1: Customize the GDDR invocation REXX exec .................................. 71Step 2: Collect and review input parameter information............................ 71Step 3: Update your personal GDDR ISPF profile ....................................... 72Step 4: Define initial parameters..................................................................... 73Step 5: Configure the EMC GDDR HMC interface ...................................... 76Step 6: Modify EMC GDDR user exits (optional)......................................... 78

EMC GDDR Product Guide4

Contents

Chapter 4 Using EMC GDDR Online Facilities Primary Options Menu .......................................................................................... 80 Option P: Profile—Update Personal GDDR ISPF Profile ................................. 82 Option M: Maintenance—GDDR Setup and Maintenance .............................. 84

Option P: Manage GDDR Parameters ........................................................... 85Option D: Message, Debug and Trace Options.......................................... 135Option Q: Manage GDDR Internal Command Queue.............................. 136Option H: Perform HMC Discovery............................................................ 136Option R: Refresh GDDR Message Table.................................................... 137Option S: Manage GDDR System Variables............................................... 138

Option G: GDDR Config—View GDDR Configuration.................................. 141 Option R: Roles—Manage Site Roles ................................................................. 142 Option C: Checkup—Perform Pre-script Checkup ......................................... 143

Health Check monitoring.............................................................................. 144Health Check monitoring exception notification....................................... 144Additional pre-script environment checks ................................................. 145

Option S: Scripts—Run GDDR Scripts .............................................................. 148 Option T: Timing—View GDDR Script Statistics ............................................. 150 Option A: Actions—Perform GDDR Actions ................................................... 152

Option H: Perform HMC Discovery............................................................ 152Option L: Perform HMC LPAR Actions ..................................................... 154Option CBU: Perform HMC CBU actions................................................... 156Option S: Manage Couple Datasets ............................................................. 156

Option O: OPS—Access CA-OPS/MVS............................................................ 158 Using OPSVIEW facilities for EMC GDDR administration ........................... 159

Ensuring MSF connections between C-Systems ........................................ 159

Chapter 5 Performing Script Operations Running scripts ..................................................................................................... 162

Call overrides .................................................................................................. 165Rerunning a script .......................................................................................... 166WTOR messages ............................................................................................. 166

Planned script operations.................................................................................... 167Abandon Site DC1 (site swap)...................................................................... 167Restart production at DC2 after site swap.................................................. 167Perform test IPL from BCVs at DC2 ............................................................ 167Perform test IPL from R2s at DC2................................................................ 167

Unplanned script operations............................................................................... 168Recover after loss of DC1 (LDR)................................................................... 168Resume replication after loss of DC1........................................................... 168

Resumption operations........................................................................................ 169Resume after test IPL from BCVs at DC2.................................................... 169Resume after test IPL from R2s at DC2 ....................................................... 169Resume replication after link failure ........................................................... 169

Chapter 6 Handling Unplanned Events Introduction........................................................................................................... 172 Consistency group trips....................................................................................... 173 Local disaster operations ..................................................................................... 174

Confirm loss of DC1....................................................................................... 174 System failure operations .................................................................................... 175

EMC GDDR C-System failure....................................................................... 175Production system failure ............................................................................. 176

EMC GDDR Master Function transfer............................................................... 178


Contents

Chapter 7 Performing Maintenance Procedures Setting up a new EMC GDDR C-System ........................................................... 180 Renaming an existing EMC GDDR C-System .................................................. 182 Adding a new production system or sysplex to EMC GDDR........................ 183 Changing the Consistency Group name............................................................ 184 Adding new RDF groups to EMC GDDR.......................................................... 185 Adding new devices to EMC GDDR.................................................................. 187 Removing an RDF group from EMC GDDR control ....................................... 188 Removing devices from EMC GDDR control ................................................... 189 Removing a system or a sysplex from EMC GDDR......................................... 190 Special cases ........................................................................................................... 191

Non-LOGR couple datasets .......................................................................... 191

Chapter 8 Using the Audit Monitoring Facility Overview ................................................................................................................ 194

Global variable changes ................................................................................. 194Messages........................................................................................................... 194State changes.................................................................................................... 194CA-OPS/MVS environment changes .......................................................... 194

Implementation tasks ........................................................................................... 195Message logging implementation................................................................. 195GDDR SAY and state monitoring implementation ................................... 195Global variable monitoring implementation .............................................. 195

EMC GDDR audit monitoring SMF extract and report JCL ........................... 196SMF audit data flow ....................................................................................... 196Sample output ................................................................................................. 196

CA-OPS/MVS environment monitoring........................................................... 197AOFEVENT segment...................................................................................... 197SMFRULEDISABLE segment........................................................................ 197OSFTERM segment......................................................................................... 197Summary section............................................................................................. 197

Chapter 9 Troubleshooting Detecting and resolving problems...................................................................... 200 Using the GDDRXCMD batch utility ................................................................. 201

To print the current queue............................................................................. 201To clear the current queue ............................................................................. 201

Appendix A EMC GDDR User ExitsUser exit programming considerations .............................................................. 204

Sample procedure ........................................................................................... 204Built-in routines available to exits ................................................................ 204

Exit specifications .................................................................................................. 206GDDRUX01...................................................................................................... 206GDDRUX02...................................................................................................... 206GDDRUX03...................................................................................................... 207GDDRUX04...................................................................................................... 207GDDRUX05...................................................................................................... 207GDDRUX06...................................................................................................... 208GDDRUX07...................................................................................................... 209


Contents

Appendix B EMC GDDR z/OS Console Monitor Introduction ........................................................................................................... 212 z/OS Console Monitor — GDDRPBAL ............................................................ 213 z/OS operator console commands..................................................................... 214 BAL command processor — BALC.................................................................... 215

BAL CSC ports ................................................................................................ 216CSC RTokens................................................................................................... 216

Appendix C Using GDDRMAIN and the Heartbeat Monitor Starting/Stopping GDDRMAIN ........................................................................ 218

Stop command (P) .......................................................................................... 218Modify command (F) ..................................................................................... 218

GDDRMAIN EXEC parameters ......................................................................... 220GDDRGVX utility ................................................................................................. 221

DSPLIST ........................................................................................................... 221DIVLIST ........................................................................................................... 221DSPSAVE......................................................................................................... 221RELOAD .......................................................................................................... 221

EMC GDDR system variable integrity and access ........................................... 222Index lock......................................................................................................... 222Update lock...................................................................................................... 223

Starting/Stopping the Heartbeat Monitor ........................................................ 224

Glossary ............................................................................................................................................... 225


Contents


Title Page

Figures

1 SRDF/S with ConGroup environment .............................................................................. 222 EMC GDDR Complex ........................................................................................................... 233 EMC JCL customization utility ........................................................................................... 414 EMC JCL customization utility completed panel ............................................................. 425 Primary Options Menu ......................................................................................................... 806 Change GDDR ISPF Profile Variable Values panel ......................................................... 827 Setup and Maintenance Menu ............................................................................................ 848 Parameter Management Options Menu ............................................................................ 859 Select Parameter input dataset for parameter review ..................................................... 8610 Reviewer's version of the Parameter Management Options Menu ............................... 8711 Manage GDDR Parameter Backups panel ........................................................................ 8812 Select Dataset for GDDR Parameter Backup ..................................................................... 9013 Select Parameter Input Dataset panel ................................................................................ 9114 Prepare Work Dataset for Parameter Load confirmation panel .................................... 9315 Prepare Work Dataset status panel .................................................................................... 9316 Parameter Management Options Menu with parameter load input selection ............ 9417 Define Configuration Basics panel ..................................................................................... 9518 Define Configuration Features panel 1 .............................................................................. 9619 Define GDDR Configuration Features panel 2 ................................................................. 9620 Define C-Systems panel ....................................................................................................... 9721 Define GDDR Datasets panel .............................................................................................. 9922 Define Site Roles and Groups panel ................................................................................. 10023 Define Storage Objects panel ............................................................................................. 10124 Define SRDF Device Ranges panel ................................................................................... 10125 Define SRDF/S GNS Groups ............................................................................................ 10326 Define TimeFinder Device Ranges panel ........................................................................ 10427 Define SDDF Clean Utility Gatekeepers panel ............................................................... 10528 Define Host Objects panel .................................................................................................. 10629 Define Managed Systems panel ........................................................................................ 10730 Define Managed LPARs panel .......................................................................................... 10931 Define Managed CPCs panel ............................................................................................. 11132 Define IPL Parameters panel ............................................................................................. 11233 Define Managed HMCs panel ........................................................................................... 11334 Define HMC Community Names panel .......................................................................... 11435 Define Managed Couple Datasets panel 1 of 2 ............................................................... 11536 Define Managed Couple Datasets panel 2 of 2 ............................................................... 11637 Define Managed CF Structures panel 1 of 2 .................................................................... 11738 Define Managed CF Structures panel 2 of 2 .................................................................... 11839 Define External Workloads panel ..................................................................................... 11940 Define EMC MF Enablers STCs panel .............................................................................. 120


Figures

Title Page

41 Specify GDDR Options panel ............................................................................................ 12142 Specify Default Script Call Overrides panel .................................................................... 12243 Script Sysplex Options panel ............................................................................................. 12344 Script AUTOCBU Options panel ....................................................................................... 12445 Script JCL Parameters panel .............................................................................................. 12546 Utility Parameters panel ..................................................................................................... 12747 Messaging and SMF Options panel .................................................................................. 12848 Tuning Values panel ........................................................................................................... 13049 Validate GDDR Parameter Set panel ................................................................................ 13150 Activate GDDR Parameter Set panel ................................................................................ 13351 Set Output Message Levels by Program panel ............................................................... 13552 Add Program to MsgLevel/Debug/Trace List panel .................................................... 13553 Manage GDDR Internal Command Queue panel ........................................................... 13654 HMC object discovery panel .............................................................................................. 13655 HMC Discovery Results panel ........................................................................................... 13756 Message table refresh indicator ......................................................................................... 13757 Manage GDDR System Variables panel 1 ........................................................................ 13858 Manage GDDR System Variables panel 2 ........................................................................ 13959 Manage GDDR System Variables panel 3 ........................................................................ 13960 Manage GDDR System Variables - Detail panel 1 .......................................................... 14061 Manage GDDR System Variables - Detail panel 2 .......................................................... 14062 View GDDR Configuration panel ..................................................................................... 14163 Manage Site Roles panel ..................................................................................................... 14264 Master C-System Transfer panel ....................................................................................... 14265 Perform Health Check panel .............................................................................................. 14366 Consistency group status display output ........................................................................ 14667 Select Script to Run panel ................................................................................................... 14868 Script Selection for Status panel ........................................................................................ 15069 GDDR Actions Menu .......................................................................................................... 15270 HMC object discovery panel .............................................................................................. 15271 HMC Discovery Results panel ........................................................................................... 15372 Perform HMC LPAR Actions panel .................................................................................. 15473 Perform CBU Actions panel ............................................................................................... 15674 Manage Couple Datasets panel ......................................................................................... 15675 CA-OPS/MVS OPSVIEW Primary Options panel ......................................................... 15876 Specify Parameters for Initial Script Run panel .............................................................. 16277 Specify Call Overrides panel (screen 1 of 2) .................................................................... 16378 Specify Call Overrides panel (screen 2 of 2) .................................................................... 16379 Confirm Job Submission panel .......................................................................................... 164


Title Page

Tables

1 Mainframe environment requirements .............................................................................. 342 Minimum hardware requirements ..................................................................................... 353 Installation tasks .................................................................................................................... 364 RIMLIB library contents ....................................................................................................... 405 RACF functional groups ...................................................................................................... 546 RACF permissions ................................................................................................................ 547 RACF permissions, OPERCMDS class ............................................................................... 568 Summary of GDDR ISPF RACF permissions .................................................................... 569 Defining Managed Couple Datasets ................................................................................ 11610 Monitoring events ............................................................................................................... 14411 EMC GDDR call overrides ................................................................................................. 16512 Possible lock states .............................................................................................................. 222


Tables


Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

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

Audience This document is part of the EMC Geographically Dispersed Disaster Restart (EMC GDDR) documentation set, and is intended for use by EMC GDDR systems administrators and computer operators.

This document describes the basic concepts of EMC Geographically Dispersed Disaster Restart (EMC GDDR), how to install it, and how to implement its major features and facilities.

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

◆ IBM z/OS operating environments

◆ IBM parallel sysplex

◆ Unicenter CA-OPS/MVS

◆ EMC software products: SRDF, ResourcePak Base, Consistency Group, and AutoSwap

Relateddocumentation

Related documents include:

◆ EMC GDDR Release Notes

◆ EMC GDDR Message and Code Guide

◆ EMC Mainframe Enablers Installation and Customization Guide

◆ EMC ResourcePak Base for z/OS Product Guide

◆ EMC Symmetrix SRDF Host Component for z/OS Product Guide

◆ EMC Symmetrix Remote Data Facility Product Guide

◆ EMC AutoSwap Product Guide

◆ EMC Consistency Group for z/OS Product Guide


Preface

◆ EMC TimeFinder/Mirror for z/OS Product Guide

◆ EMC TimeFinder/Clone Mainframe SNAP Facility Product Guide

◆ EMC REXX Interface Programmer’s Reference Guide

◆ Unicenter CA-OPS/MVS for EMC Geographically Dispersed Disaster Restart Documentation CD

Conventions used inthis document

EMC uses the following conventions for special notices.

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

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

IMPORTANT!An important notice contains information essential to operation of the software. The important notice applies only to software.

EMC GDDR — This document uses the acronym EMC GDDR in place of full product name, EMC Geographically Dispersed Disaster Restart.

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

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

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

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

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

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

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

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

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

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)


Preface

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

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

http://Powerlink.EMC.com

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

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

[email protected]

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

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

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

[ ] Square brackets enclose optional values

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

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

... Ellipses indicate nonessential information omitted from the example


http://powerlink.emc.com

Preface


1Invisible Body Tag

This chapter presents an overview of EMC GDDR and its capabilities.

◆ What is EMC GDDR? .................................................................................................... 18◆ Major features ................................................................................................................. 19◆ Supported business continuity configurations .......................................................... 21◆ The EMC GDDR Complex............................................................................................ 23◆ EMC GDDR fundamentals ........................................................................................... 24◆ EMC GDDR components .............................................................................................. 27◆ EMC GDDR supported scripts..................................................................................... 29◆ Parameter wizard: Telling EMC GDDR what to manage......................................... 31

Product Overview

Product Overview 17

Product Overview

What is EMC GDDR?EMC® Geographically Dispersed Disaster Restart (EMC GDDR) is a mainframe software product that automates business recovery following both planned outages and disaster situations, including the total loss of a data center. EMC GDDR achieves this goal by providing monitoring, automation and quality controls to the functionality of many EMC and third-party hardware and software products required for business restart.

Because EMC GDDR restarts production systems following disasters, it does not reside on the same servers that it is seeking to protect. EMC GDDR resides on separate logical partitions (LPARs) from the host servers that run your application workloads.

You install EMC GDDR on a control LPAR at each site. Each EMC GDDR node is aware of the other EMC GDDR nodes through network connections between each site. This awareness allows EMC GDDR to:

◆ Detect disasters

◆ Identify survivors

To achieve the task of business restart, EMC GDDR automation extends well beyond the disk level and into the host operating system level. It is at this level that sufficient controls and access to third party software and hardware products exist to enable EMC to provide automated recovery capabilities.

EMC GDDR’s main activities include:

◆ Managing planned site swaps (workload and DASD) between the primary and secondary sites.

◆ Active monitoring of the managed environment and responding to exception conditions.


Product Overview

Major featuresEMC GDDR successfully undertakes these activities by exploiting the following major features:

◆ Situational awareness

◆ Survivor recognition

Situational awareness

EMC GDDR can distinguish normal operational disruptions from disasters and respond accordingly. For example, EMC GDDR is able to distinguish between network outages (SRDF link drop) and real disasters. This awareness is achieved by periodic exchange of dual-direction heartbeats between the EMC GDDR LPARs.

Survivor recognitionEMC GDDR can determine which sites and systems have survived a disaster. Unlike the foundation technologies (such as TimeFinder®/Mirror or TimeFinder/Clone Mainframe SNAP Facility), EMC GDDR has built-in intelligence to monitor other EMC GDDR systems. EMC GDDR constantly checks for disaster situations and constantly ensures that other GDDR systems are “healthy.” This checking allows EMC GDDR to recognize, and act on, potential disaster situations, even if only one EMC GDDR system survives.

“Split brain” problems associated with cluster technologies are avoided through operator prompts. Upon the initial recognition stage, EMC GDDR issues messages to the operator console seeking confirmation of the event and, further, confirmation of restart actions required.

Restart coordinationIf a primary site disaster occurs, the EMC GDDR Master C-System located at the secondary site will execute the recovery. The EMC GDDR Master C-System operates in a Master Owner/ No-Owner role for other EMC GDDR control LPARs.

Changes to EMC GDDR configuration information can only be made on the EMC GDDR Master Control System (C-System). EMC GDDR propagates these changes to the subordinate EMC GDDR systems using the CA-OPS/MVS MSF (multi-system facility) inter-system communications feature.

Restart procedures following disasters are coordinated from the EMC GDDR Master C-System.

EMC GDDR coordinates and executes predetermined processes to:

◆ Restart the enterprise at the desired surviving site in the event of a disaster

◆ Automate a planned site swap

Major features 19

Product Overview

Additional capabilities

As part of the planned site swap process and as part of the recovery process after an unplanned site swap, EMC GDDR can optionally perform the following tasks:

◆ Trigger stopping or starting distributed workloads

◆ Trigger stopping or starting z/OS workloads

Types of environment

EMC GDDR can manage environments that are comprised of the following elements:

◆ Multiple z/OS systems

◆ Multiple sysplexes

◆ Multiple Symmetrix® controllers

◆ Intermix of CKD and FBA/FBAM DASD and BCVs


Product Overview

Supported business continuity configurationsEMC GDDR is available in the following configurations:

SRDF/S with ConGroup — The 2-site SRDF/S with ConGroup configuration provides disaster restart capabilities at site DC2.

SRDF/S with AutoSwap — The 2-site SRDF/S with AutoSwap configuration provides for near-continuous availability through device failover between DC1 and DC2.

SRDF/A — The 2-site SRDF/A configuration provides disaster restart capabilities at site DC3.

SRDF/Star — The 3-site SRDF/Star configuration provides disaster restart capabilities at either DC2 or DC3. Concurrent and Cascaded SRDF support further minimize the DC3 recovery time objective.

SRDF/Star with AutoSwap — The 3-site SRDF/Star with AutoSwap configuration provides for near-continuous availability through device failover between DC1 and DC2 as well as disaster restart capabilities at DC3. Concurrent and Cascaded SRDF support further minimize the DC3 recovery time objective.

EMC GDDR has been designed to be customized to operate in any of these configurations. EMC GDDR functionality is controlled by a parameter library. During EMC GDDR implementation, this parameter library is customized to reflect:

◆ The prerequisite software stack

◆ The desired data center topology (two-site versus three-site, synchronous or asynchronous). The data centers are referred to as sites DC1 and DC2. Usage of these data center sites is described in “Sites DC1 and DC2” on page 23.

EMC GDDR is able to control multiple sysplexes from a single control LPAR.

This document discusses the EMC GDDR SRDF/S with ConGroup configuration. Documentation for other EMC GDDR configurations is available on the EMC Powerlink website at:

http://Powerlink.EMC.com

SRDF/S with ConGroup configuration

The 2-site SRDF/S with ConGroup configuration provides disaster restart capabilities at site DC2.

Figure 1 on page 22 illustrates EMC GDDR operation in the SRDF/S with Consistency Group environment.

Supported business continuity configurations 21


Product Overview

Figure 1 SRDF/S with ConGroup environment

As Figure 1 shows, the relationship between the DC1 and DC2 sites is maintained through SRDF/S replication of primary disk images at DC1 to DC2. Both open systems (FBA) and mainframe (CKD) disk images can be replicated.

Figure 1 shows the two EMC GDDR C-Systems with their heartbeat communication paths, separate from the production disk and computer facilities. Each of the DC1 and DC2 production z/OS LPARs has EMC Consistency Group (ConGroup) software installed.

EMC GDDR does not have a requirement to “freeze” I/O to obtain a point of consistency. SRDF/S and ConGroup provide the mechanism. At the point that EMC GDDR receives notification of an unplanned or failure event, a point of consistency is already achieved through these foundation technologies.

In this environment, EMC GDDR can do the following:

◆ Manage planned site swaps

◆ Restart processing at the secondary site following unplanned primary site events

◆ Perform standard operational tasks:

• IPL, system reset, activate, deactivate

• Trigger stop/start of business workloads

◆ Actively monitor for unplanned/failure events

• Sites

• Systems

• Loss of SRDF/S

• ConGroup trip

• Inter-site communication failure

GDDR heartbeat communication

Active Escon/Ficon channels

Active SRDF links

Standby Escon/Ficon channels

R1

EMCGDDR

R2

EMCGDDR

DC2DC1

SRDF/S

SYM-002226

ConGroup ConGroup


Product Overview

The EMC GDDR ComplexAn EMC GDDR Complex consists of EMC GDDR Control Systems (C-Systems), the z/OS and open systems hosts, and EMC Symmetrix storage systems which support an organization's mission-critical workload.

Each GDDR Complex can manage one consistency group. A consistency group is a named group of source (R1) volumes managed by the EMC Consistency Group (ConGroup) application as a unit. The volumes can be on multiple Symmetrix units.

Figure 2 depicts a logical view of a typical EMC GDDR Complex.

Figure 2 EMC GDDR Complex

The following are brief descriptions of the components that comprise a GDDR Complex:

BCVs — BCVs (Business Continuance Volumes) can be supported at each of the sites. They may be established at the DC2 site and split at the DC1 site.

Note: The EMC TimeFinder/Mirror for z/OS Product Guide provides more information about BCVs and about the establish and split operations.

C1 and C2 — C1 and C2 are the EMC GDDR Control LPARs (or C-Systems) at each of the sites.

Primary site — The primary site is the site where the production workload is located.

Primary DASD site — The primary DASD (direct access storage device) site is the site where the source (R1) DASD is located. The primary DASD site is the same as the primary site.

Secondary site — The secondary site is the site where the contingency or stand by systems are located.

Secondary DASD site — The secondary DASD site is the site where the target (R2) DASD is located. The secondary DASD site is the same as the secondary site.

Sites DC1 and DC2 — Sites DC1 and DC2 are the primary and secondary data centers of critical production applications and data. DC1 is the primary site, with SRDF/S data replication to the secondary site, DC2. These sites are considered fully equivalent for strategic production applications, connected with highly redundant direct network links. At all times, all production data is replicated synchronously between the two sites.

Sysplexes — A system processing complex. A single GDDR complex supports multiple sysplexes.

LocalR2

BCV

Primary site

DC1 DC2

Secondary site

C1 C2

Master C

SYM-002219

Sysplex #n

Sysplex #2

Sysplex #1

SRDF/S

Sysplex #n

Sysplex #2

Sysplex #1

BCV

R1Local

The EMC GDDR Complex 23

Product Overview

EMC GDDR fundamentalsThis section discusses:

◆ Control systems

◆ Workload location

◆ Managed workloads

◆ EMC GDDR processes

Control systemsThe EMC GDDR control systems are more commonly referred to as EMC GDDR C-Systems. One EMC GDDR C-System is located at each site (DC1 and DC2).

C-Systems can be configured in monoplex mode or as standalone systems. Each EMC GDDR C-System runs in monoplex mode from local DASD. EMC suggests that you locate the C-System DASD on separate controllers from the production DASD. Because the EMC software applications run from local C-System volumes, this separation ensures that the C-Systems are not affected by any events that may impact the availability of the managed systems.

The main functions of a EMC GDDR C-System are to:

◆ Control the recovery after an outage

◆ Control a planned site swap

EMC GDDR C-Systems do not run any production workload.

One of the C-Systems is the Master C-System. During normal operations, the Master C-System is the central control point for all EMC GDDR activities. The Master C-System is located at the primary DASD site. In the event of the loss of the primary DASD site, EMC GDDR transfers the Master C-System to the secondary site, for completion of the restart coordination.

Some EMC GDDR functions can only be carried out by the Master C-System, for example:

◆ Running planned processes

◆ Updating EMC GDDR parameters

All EMC GDDR C-Systems are potential candidates to takeover as the Master C-System.

Workload locationIn an EMC GDDR Complex, the business or production workload runs at a single site; that is, one side of the sysplex. This is the same location as the primary DASD site.

Production systemA production system is a system that normally runs the site’s production workload and updates the primary DASD. Production systems are located at the same location as the primary DASD.


Product Overview

Contingency or standby systemA contingency or standby system is a system that normally provides a hot backup to a production system. A contingency system:

◆ Is in the same sysplex as its production system partner

◆ Is IPLed, but runs no business workload

Contingency or standby systems are typically located at the same location as the secondary DASD.

Note: Subsequent references to the term “production system” in this document refer to both production systems and contingency systems.

Managed systemsAny production or contingency/standby system defined to EMC GDDR is known as an EMC GDDR managed system.

Managed workloads

EMC GDDR can trigger the stop and restart of production workloads on:

◆ z/OS systems

◆ Distributed systems

External workloadsExternal workloads run in mainframe systems which do not have their DASD in the managed Symmetrix units.

EMC GDDR can coordinate Stop and Start of the workload on these "non-managed" mainframe systems with the workload Stop and Start for managed systems.

Excluded systemsEMC GDDR can be configured to exclude certain systems from workload management, although these systems have their DASD in the managed Symmetrix units.

HMC-only systemsEMC GDDR can be configured to limit IPL and CBU actions for certain systems to the online interface. No other actions or automation are performed for these systems.

EMC GDDR fundamentals 25

Product Overview

EMC GDDR processes

An EMC GDDR process is a predetermined sequence of function calls. Generally one function call corresponds to one action. An EMC GDDR process is started by calling EMC GDDR provided routines, either from a batch job or as a result of specific messages being issued.

There are two types of EMC GDDR processes:

Planned process

An EMC GDDR planned process is initiated through the EMC GDDR interface to perform a planned task.

Unplanned process/takeover process

The EMC GDDR unplanned process or takeover process can only be initiated following an error that results in a possible takeover situation. Takeover processes are initiated as a result of certain messages being issued or specific events occurring.

The messages or events that trigger an unplanned or takeover process can originate on any system, either a C-System or a production system. They only take place on the current Master C-System.

They are invoked following operator confirmation of any of the following types of failure or loss:

◆ Sites

◆ DASD

◆ Systems

◆ Loss of SRDF link

◆ Loss of host channels

Process restartThe return codes from the function calls that make up an EMC GDDR process are saved in CA-OPS/MVS global variables. For functions that issue EMC SRDF Host Component commands, the return code of the commands are also saved. If multiple commands are issued from one function, the return codes from each command are saved in CA-OPS/MVS global variables.

After the cause of the original failure has been identified and resolved, the EMC GDDR process can be rerun. EMC GDDR uses the saved return codes to establish the point of restart; that is, the point of the previous failure. This ensures that no modifications to the supplied EMC GDDR process jobs are required in order to rerun after a failure.


Product Overview

EMC GDDR componentsEMC GDDR is comprised of a number of components:

◆ Parameters

◆ User interface

◆ Events

◆ Monitors

◆ Message rules

ParametersEMC GDDR parameters define the environment and configuration that it manages. The parameters can modify the sequence of function calls that is an EMC GDDR process.

User interfaceThe EMC GDDR user interface is an ISPF application. It is available only on EMC GDDR C-Systems.

EventsAn EMC GDDR event is a change in state of a component part of the environment that EMC GDDR is actively monitoring. Examples of EMC GDDR events include:

◆ CGT — ConGroup trip has occurred/state change

◆ CGD — ConGroup group is disabled/state change

◆ MHB — missing C-System heartbeat

The event can have a state of either TRUE or FALSE. If the event has a state of TRUE, it has occurred or is currently occurring. If the event has a state of FALSE, it is no longer occurring.

An event that is TRUE is considered an exception.

EMC GDDR events are used by the GDDR event monitor and GDDR processes to determine environment state. A change in state can then:

◆ Request operator confirmation of the event and present the relevant actions

◆ Prevent a planned process from running

MonitorsThere are three monitors on each EMC GDDR C-System:

◆ The EMC GDDR event monitor

◆ The EMC GDDR heartbeat monitor

◆ The optional EMC GDDR audit monitor

EMC GDDR components 27

Product Overview

Event monitorThe EMC GDDR event monitor runs on each C-System and is used to analyze event state changes in which EMC GDDR is interested. On detecting the occurrence of selected events, the event monitor determines what action to take and prompts operators with the appropriate choices.

For example: EMC GDDR detects that a production system has failed and prompts the operators with the following options:

◆ IPL:ssss — EMC GDDR to restart ssss at current location DCn.

◆ SYSSITEn — EMC GDDR to start business applications at site DCn.

◆ SYSRESET — EMC GDDR to system reset ssss at site DCn only.

◆ Ignore — EMC GDDR to do nothing.

Heartbeat monitorThe EMC GDDR heartbeat monitor aids the event monitor in determining the status of the EMC GDDR managed environment. The lack of a heartbeat from a particular C-System is used to determine the state of a C-System and the site.

Audit monitorThe EMC GDDR audit monitor captures and externalizes data that EMC GDDR automation uses for business continuance processing (BCP) decision criteria and operations. This data includes dates and times of parameter load and backup jobs, global variable updates, override usage, and state changes relevant to EMC GDDR managed systems and storage.

Message rulesEMC GDDR is supplied with AOF (Automated Operations Facility) message rules to be installed only on the GDDR C-Systems. These rules are disabled as shipped by EMC to allow for operations training and familiarity before the message handling is automated. EMC GDDR does not operate properly if all these message rules are not enabled on all C-systems.

Note: The EMC GDDR Message and Code Guide contains more information about EMC GDDR messages.

The AOF message rules have two primary functions:

◆ To detect events that EMC GDDR is interested in and set the appropriate EMC GDDR event TRUE or FALSE.

◆ To detect events that EMC GDDR processes have to wait for (WTOR), and reply as to the success or failure of the waited for event. This will determine if an EMC GDDR process proceeds or terminates.

EMC GDDR uses the EMC ResourcePak Base Cross System Communication (CSC) facility to route message traffic to production systems. You or EMC service personnel can use the arrival of a message at the target production system to trigger an automation rule (for example in IBM Tivoli NetView or BMC Control-M). Such rules can be used to start or shut down workloads on the appropriate systems, even though they do not run CA-OPS/MVS.

DYNAPI interfaceThe EMC GDDR interface to EMC DYNAPI allows EMC GDDR to run dynamic SRDF commands in parallel.


Product Overview

EMC GDDR supported scriptsEMC GDDR provides a number of scripts that allow you to perform any of the following actions:

◆ Planned event management

◆ Unplanned event management

◆ Resumption after planned or unplanned outages

Planned event management

Operations personnel can handle planned event management scenarios by running any of the following scripts.

Note: DC1 and DC2 represent the current primary DASD site or current secondary DASD site. When these representations are shown in italic type in script titles, this indicates the values are interchangeable. The descriptions assume that DC1 is the Primary DASD site and Primary site at the beginning of the script.

Abandon Site DC1 (site swap)

◆ Stops the business workload at the primary DASD site

◆ Waits for the stop of all business applications

◆ Resets clear all production systems managed by EMC GDDR

Restart production at DC2 after site swap

This script performs the following actions after the loss of the primary site:

◆ Attempts reset clear of all systems at the primary DASD site◆ Activates CBU (if required)

◆ Activates all needed LPARs, including CFs at the secondary DASD site◆ Creates a consistency point at the secondary DASD site◆ Prepares the SRDF environment◆ IPLs all needed production systems

Perform test IPL from BCVs at DC2

◆ Splits BCVs, makes them R/W

◆ Activates test LPARs using BCV volumes

◆ Starts test business workload, if applicable

Perform test IPL from R2s at DC2

◆ Confirms that SRDF/S has been stopped normally via a Congroup trip

◆ Activates LPARs using R2 volumes

◆ Starts test business workload, if applicable

EMC GDDR supported scripts 29

Product Overview

Unplanned event management

Operations personnel can manage unplanned events in one of two ways:

◆ The EMC GDDR Event Monitor prompts the operator for management confirmation of trigger events which indicate a site or DASD outage. The operator replies to the prompt in the affirmative and the GDDR recovery script is started.

◆ The operator may start the appropriate unplanned script and respond to prompts. The script initiates and validates that the state of the current host and storage environments matches the script prerequisites before proceeding.

Recover after loss of DC1 (LDR)

◆ Confirms that a ConGroup trip occurred

◆ Confirms that SRDF links failed

◆ Confirms that a local disaster (LDR) event occurred

◆ Shuts down applications at the primary site, if applicable

◆ Splits BCVs and conditions R2s at secondary site for restart

◆ Activates contingency systems

◆ Restarts applications

Resume replication after loss of DC1

◆ Confirms SRDF/S links are down

◆ Splits BCVs at the secondary site, if applicable

◆ Issues ConGroup cleanup and SRDF/S restart commands

◆ Reestablishes BCVs at the secondary site

Resumption after planned or unplanned outages

Operations personnel can resume operations after planned or unplanned outages by running any of the following scripts.

Resume after test IPL from BCVs at DC2

◆ Stops test business workload, if applicable

◆ Reset clears test LPARs

◆ Reestablishes the BCVs

Resume after test IPL from R2s at DC2

◆ Stops test business workload, if applicable

◆ Reset clears test LPARs

◆ Restarts SRDF/S to DC2

Resume replication after link failure

◆ Confirms SRDF/S links are down

◆ Stops ConGroup on all systems

◆ Splits BCVs at the secondary site, if applicable

◆ Issues ConGroup cleanup and restart commands

◆ Reestablishes BCVs at the secondary site


Product Overview

Parameter wizard: Telling EMC GDDR what to manageThe environment that EMC GDDR manages is described to EMC GDDR through a collection of common variables. The EMC GDDR parameter management wizard groups these variables in a series of ISPF panels, each backed by a member in a PDS. The variable groups include the following:

◆ Configuration-defining variables

These variables define the type of managed configuration, the C-systems, the initial role for each site, the consistency group names and the MSC group names.

◆ Storage object variables

These variables define the actual SRDF and TimeFinder devices, SRDF groups, GNS groups, and gatekeeper devices that form the configuration that EMC GDDR will manage.

◆ Host Object variables

These variables define the managed, external and HMC-only systems, and their LPARs, IPL-parameters and CPCs. Host object variables also define HMC-consoles, Sysplex objects and EMC Mainframe Enablers started tasks.

◆ GDDR option variables

These variables define user-selectable values for a variety of actions taken in the course of GDDR automation sequences. GDDR option variables also define site defaults for JCL and utilities used by GDDR, messaging and audit related options, and tuning values.

Parameter wizard: Telling EMC GDDR what to manage 31

Product Overview


2Invisible Body Tag

This chapter describes the EMC GDDR installation procedure.

◆ Preinstallation tasks ....................................................................................................... 34◆ Installation procedure.................................................................................................... 36◆ Post-installation tasks .................................................................................................... 43

Installing EMC GDDR

Installing EMC GDDR 33

Installing EMC GDDR

Preinstallation tasksBefore you begin installing EMC GDDR, review the hardware and software requirements listed below.

CAUTION!EMC GDDR is only to be installed on designated EMC GDDR Control Systems (C-Systems).

Mainframe environment requirements

The basic infrastructure must support SRDF/S with Congroup. In addition to this, EMC GDDR has the following specific infrastructure requirements:

◆ There must be network connectivity between all C-Systems.

◆ An HMC (Hardware Management Console) must be available at each site that can be accessed from each C-System (access to these HMCs can be protected by means of a private VLAN).

EMC GDDR has the mainframe environment requirements listed in Table 1. Before you install EMC GDDR, make sure your environment meets these requirements.

Minimum software requirementsThe minimum software prerequisites needed to run EMC GDDR 3.1 are as follows:

◆ z/OS

◆ IBM Hardware Management Console (HMC) API

◆ CA-OPS/MVS

◆ SRDF/Host Component

◆ ResourcePak Base

◆ Consistency Group

Note: The EMC GDDR Release Notes provide information regarding supported software release levels for the above items.

You can find installation procedures for the EMC software products in the EMC Mainframe Enablers Installation and Customization Guide.

Table 1 Mainframe environment requirements

Item Requirements

Processor hardware configuration Any system that supports current IBM mainframe operating systems

DASD hardware configuration Any supported Symmetrix DASD model at an Enginuity microcode level specified in the EMC GDDR Release Notes

Software Any currently supported IBM operating system


Installing EMC GDDR

Additional configuration requirementsSRDF/S with ConGroup — Please refer to the EMC SRDF Host Component for z/OS Product Guide for information on configuring an SRDF/S environment.

Minimum hardware requirements

Table 2 describes the recommended minimum processor and I/O configuration for an EMC GDDR C-System.

DASD support

EMC GDDR supports and can manage the following combinations of DASD in a single Enterprise Consistency Group:

◆ Single EMC Symmetrix controllers configured with any of the following:

• All CKD devices

• All FBA and FBA-META devices

• Any combination of CKD, FBA and FBA-META devices

◆ Multiple EMC Symmetrix controllers configured with any of the following:

• All CKD devices

• All FBA and FBA-META devices

• Any combination of CKD, FBA and FBA-META devices

Management and monitoring of both CKD and FBA/FBA-META devices is performed from the z/OS platform where the EMC GDDR application resides. From the EMC GDDR point of view, CKD and FBA/FBA-META Symmetrix devices are the same; that is, each is treated no differently than the other. They are all command targets of SRDF Host Component configuration commands using local, remote or GNS syntax.

EMC GDDR requires that if even only one device in an RDF group is defined to GDDR, then all devices in that group must be defined to GDDR. Most GDDR actions are directed at the RDF group level (although in some cases, GDDR will act on device ranges if that is appropriate).

EMC GDDR has no limitations on the number of EMC Symmetrix controllers/devices that can be managed. Any limitations are subject to restrictions in EMC hardware and software.

Table 2 Minimum hardware requirements

Item Requirements

Logical processors 1 (2 are recommended)

MSU 15 on a IBM 2084-306 (or equivalent)

Storage 512 MB

Logical paths to own local DASD devices 4

Logical paths to managed DASD devices 4

Preinstallation tasks 35

Installing EMC GDDR

Installation procedureThis section describes how to install EMC GDDR. The EMC GDDR installation kit is provided in two forms:

◆ As an electronic download from Powerlink®

◆ As a CD

CAUTION!Keep in mind that EMC GDDR is only to be installed on designated EMC GDDR Control Systems (C-Systems).

Before you begin

EMC GDDR is a user application under CA-OPS/MVS; therefore, CA-OPS/MVS and its prerequisite CA-Common Services must be installed before you can start the EMC GDDR installation process.

The procedure for the EMC GDDR installation is as follows for each EMC GDDR C-System:

Table 3 Installation tasks

Task Reference

1. Review pre-installation information “Preinstallation tasks” on page 34 and “Gather EMC GDDR installation information” on page 37

2. Install CA-Common Services Unicenter CA-OPS/MVS Event Management and Automation Getting Started a

3. Install CA/OPS/MVS Unicenter CA-OPS/MVS Event Management and Automation Getting Started

4. Install EMC GDDR “Install EMC GDDR” on page 38

5. Customize CA-OPS/MVS “Customize CA-OPS/MVS for EMC GDDR” on page 64b

a. This document is available on the Unicenter CA-OPS/MVS for EMC Geographically Dispersed Disaster Restart Documentation CD.

b. Refer to “Using OPSVIEW facilities for EMC GDDR administration” on page 159 for assistance with administration tasks that are performed using the CA-OPS/MVS - OPSVIEW Primary Options panel shown in Figure 75 on page 158.


Installing EMC GDDR

Gather EMC GDDR installation information

Before beginning the EMC GDDR installation, you need to gather information in preparation for the installation. Identify or decide upon the following items:

CLIST library and EDIT macro Determine a name for the edit macro created by the installation dialog. You also need to determine the name of a CLIST library where you can store the edit macro.

Product dataset name prefixChoose the dataset prefix you will use to install EMC GDDR. Names for the product datasets consist of a final qualifier, such as LINKLIB, and a dataset prefix. For example, if you choose a dataset prefix of EMC.GDDRvrm, the LINKLIB dataset will be named EMC.GDDRvrm.LINKLIB.

Ensure that you have RACF ALTER authority (or the equivalent from another security manager) for the datasets created with this dataset prefix.

Note: Throughout this guide, datasets created using this dataset prefix are referred to as if they had been created with the suggested value.The actual fmid for your installation may be different.

ResourcePak Base dataset name prefixSpecify the dataset name prefix you used when you install ResourcePak Base. EMC recommends that you use EMC.fmid if it agrees with your site standards.

SMP/E dataset name prefixChoose the name prefix for the SMP/E datasets into which you installed EMC GDDR. If you have installed another EMC product using SMP/E, you should install EMC GDDR into the same CSI.

If you are installing an EMC SMP/E maintained product for the first time, EMC recommends using “EMC.SMPE.”

SMP/E datasets volserChoose the disk volume onto which you will install the distribution libraries required by SMP/E. This may be the same volume you use for the product libraries. However, many customer sites prefer to keep SMP/E-related datasets on separate volumes from product libraries. An amount of space similar to that needed for the product libraries is required.

Install-to-disk volserDetermine the disk volume onto which you will install the target (that is, runtime) datasets. The space required is nominal. EMC suggests that you use EMC.fmid if it agrees with your site standards.

Disk unit nameDecide upon a disk unit name for the above volumes. For many users, “SYSDA” will suffice. However, use whatever generic or esoteric name your local standards require.

Installation procedure 37

Installing EMC GDDR

Install EMC GDDR

The EMC GDDR kit consists of a PDS containing TSO TRANSMIT images of files needed to perform an SMP/E indirect-library installation. This PDS is packaged on CD or as an electronic download from EMC Powerlink.

To install EMC GDDR on an EMC GDDR control system, take the following steps:

1. Load the TSO TRANSMIT file, GDDRvrm.XMITLIB, to the mainframe disk.

2. Run GDDRvrm.XMITLIB(#EXTRACT) to extract ds-prefix.RIMLIB and the SMP/E indirect libraries.

3. Customize the RIMLIB JCL.

4. Run the installation jobs.

5. Perform cleanup.

6. Apply maintenance updates.

The following sections describes these steps in more detail.

Load GDDRvrm.XMITFILE to disk1. Take one of the following steps:

• If you are installing EMC GDDR from a CD, complete the following steps:

a. Mount the CD on an open system host.

b. Allocate a working directory on the open system for the installation.

c. Copy the contents of the CD to the working directory.

• If you are installing EMC GDDR from an EMC Powerlink download, complete the following steps:

a. Log in to a privileged account on an open systems host (root on UNIX or administrator on Windows).

b. Allocate a working directory on the open system for the installation.

c. Log on to: http://Powerlink.EMC.com

d. Navigate to Support>Software Downloads and Licensing>Downloads E-I>Geographically Dispersed Disaster Restart (GDDR).

Note: If you are not able to access this location, you may not have registered your software or registered it incorrectly. Follow the prompts to register your software, correct your registration, or contact EMC in the event of a problem.

e. Click the product version you want to download. The product version consists of a zip file that contains the installation kit and the installation instructions.

f. Download the installation kit into the working directory.

2. If your current host is a Windows system, unzip the file in the working directory. If your current host is a UNIX system, unzip and untar the file into the working directory.

3. Locate GDDRvrm.XMITFILE.

This file is in TSO TRANSMIT format and contains a flattened copy of GDDRvrm.XMITLIB, a PDS that holds other TRANSMIT images, the JCL to extract them, and necessary SMP/E installation files.



Installing EMC GDDR

4. On the target mainframe, allocate a file to which you can FTP GDDRvrm.XMITFILE.

Use the dataset name prefix you intend to use for product installation. The final qualifier must be XMITFILE. For example, if you intend to install the product with a dataset name prefix of EMC.SGDCvrm, name the file EMC.SGDCvrm.XMITFILE.

Allocate the dataset with the following characteristics:

LRECL=80

BLKSIZE=3120

DSORG=PS

SPACE=(CYL,(13,2))

Note: The SPACE parameter assumes that you are allocating the dataset on a 3390 device.

5. FTP the file to the mainframe in binary format.

Your FTP session may look something like the following:

ftp hostname

(username and password prompts)

cd ..

25 “’’” is working directory name prefix

binary

200 Representation type is image

put GDDRvrm.XMITFILE EMC.GDDRvrm.XMITFILE

6. Use TSO RECEIVE to receive the file into a PDS.

The PDS is created by the RECEIVE command and does not have to be pre allocated. However, you must specify a dataset name using the DA[taset] parameter or the file will be allocated using your TSO prefix (usually your logonid). The dataset name specified must have the final qualifier of XMITLIB.

For example:

receive indataset(‘EMC.GDDRvrm.XMITFILE’)INMR901I Dataset EMC.GDDRvrm.XMITLIB from userid on nodenameINMR906A Enter restore parameters or ‘DELETE’ or ‘END’ +da(‘EMC.GDDRvrm.XMITFILE’)

If you did not specify “DA(…)” as above, the dataset would be allocated as userid.XMITLIB.


Installing EMC GDDR

Run GDDRvrm.XMITLIB(#EXTRACT)Now run GDDRvrm.XMITLIB(#EXTRACT) to extract ds-preface.RIMLIB and the SMP/E indirect libraries. Take the following steps:

1. Edit the #EXTRACT member of the newly RECEIVED library.

You can edit the #EXTRACT job by running the SETUP REXX program you can find in the XMITLIB dataset. The SETUP REXX program prompts you for all of the information needed to edit the job.

If you wish to edit the job manually, make the following changes:

• Change the JOB card to one that conforms to your standards.

• Globally change ds-prefix to the dataset prefix of this library (which will be the dataset prefix for the product libraries).

• Globally change DVOL to the disk volser onto which you want to place the extracted libraries.

• Globally change DISK-UNIT to an esoteric unit name such as “SYSDA” that is appropriate for your site.

2. Submit #EXTRACT. Step completion codes should be 0, except for the DELETE step, which will have a step completion code of 8 unless the job is a rerun.

Customize the RIMLIB JCLThe RIMLIB library (<ds-prefix>.RIMLIB) is a PDS containing JCL to install the product. After you extract the RIMLIB PDS, you find that RIMLIB has the contents shown in Table 4.

Table 4 RIMLIB library contents

File Contents

#01ALLOC Allocate target and distribution libraries

#02DDDEF Add or replace product library DDDEFS to SMP/E CSI

#03RECEV SMP/E RECEIVE function into global zone

#04APPLY SMP/E APPLY function into target zone

#05ACCPT SMP/E ACCEPT product sysmods into distribution zone

#06CLEAN Deletes indirect libraries and DDDEFs used for them

#91HFS Allocate and MOUNT the HFS dataset used by OPS MVS

#92CMHFS Copy the USSEXEC modules to the HFS dataset and set the proper attributes of each module

#99MAINT SMP/E RECEIVE and APPLY service

GDRJCL REXX to customize the install process

GDRWIN1 ISPF panel used in REXX install process

SETUP REXX to simplify the customization process


Installing EMC GDDR

Complete the following steps to customize the installation JCL using the automated dialog:

1. Edit the RIMLIB library (ds-prefix.RIMLIB).

2. Locate the member named SETUP on the member selection list and type EX in the selection column next to it and press Enter.

Menu Functions Confirm Utilities Help ------------------------------------------------------------------------------ EDIT EMC.GDDRvrm.RIMLIB Row 00001 of 00013 Command ===> Scroll ===> CSR Name Prompt Size Created Changed ID _________ #01ALLOC 45 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #02DDDEF 51 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #03RECEV 22 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #04APPLY 22 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #05ACCPT 22 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #06CLEAN 53 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #91HFS 33 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #92CMHFS 48 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ #99MAINT 27 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ GDRJCL 206 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring_________ GDRWIN1 51 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstringex_______ SETUP 13 yyyy/mm/dd yyyy/mm/dd hh:mm:ss idstring **End**

Result: The panel shown in Figure 3 appears.

Figure 3 EMC JCL customization utility

3. Enter or change the following information on the panel shown in Figure 3 to customize your installation:

a. The CLIST library field is set by default to the name of the RIMLIB library. This field should contain the name of a library in which you want the edit macro created by this dialog to be stored.

The default value is fine for most users and need not be changed.

b. In the Edit macro name field, either:

– Accept the default name displayed.

or

– If necessary, change the name of the edit macro.

Note: Normally, you should not have to change the name.

+---------------------- EMC JCL Customization Utility ----------------------+ | COMMAND ==> _____________________________________________________________ | | | | Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. | | | | CLIST library ==> 'hlq.GDDRvrm.RIMLIB' | | Edit macro name ==> GDR | | Product dsname prefix ==> hlq.GDDRvrm | | Mainframe Enablers | | dsname prefix ==> hlq.MFEvrm | | SMP/E dsname prefix ==> EMC.SMPE | | SMP/E datasets volser ==> ______ | | Install-to disk volser==> ______ Disk unit name ==> SYSDA | | | | Enter your job card below ('%MEMBER%' will be replaced by member name): | | => //%MEMBER% JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1) | +---------------------------------------------------------------------------+


Installing EMC GDDR

Result: The edit macro is created in the CLIST library from the data entered on this panel and applied to all members of RIMLIB that start with a # character.

c. In the Product dsname prefix field, enter the dataset name prefix you want to use for the target datasets. EMC suggests hlq.GDDRvrm.

d. In the SMP/E dsname prefix field, enter the dataset name prefix of the SMP/E datasets into which you installed EMC GDDR.

For example, if you called the SMPSCDS dataset EMC.SMPE.SMPSCDS, enter EMC.SMPE.

e. In the SMP/E datasets volser field, enter the six-character volume serial number of the disk volume on which you want to allocate the SMP/E distribution libraries for EMC GDDR.

This volume may be the same as the volume you specify in the next step, or you may elect to keep these datasets on a separate volume.

f. In the Install-to disk volser field, enter the six-character volume serial number of the disk volume to which you want to install the EMC GDDR libraries.

g. In the Disk unit name field, you can specify an esoteric disk name that is appropriate to your site. SYSDA is the default, but you can overtype it with another esoteric disk name.

h. Enter a site-appropriate job card.

The job card is initially set to a value which may be suitable to many users. The first seven characters of the job name is set to your TSO userid, plus “X.”

You can set the job name to %MEMBER%. This causes the edit macro to set each job name equal to the JCL member name (that is, #01ALLOC, #02DDDEF, and so forth).

Do not use any parameter that contains an ampersand (&), such as NOTIFY=&SYSUID. An ampersand in the job card can cause edit macro errors.

Figure 4 shows an example of a completed panel as the user is about to press Enter and complete the dialog.

Figure 4 EMC JCL customization utility completed panel

4. When you are satisfied with your entries, type exec on the command line and press Enter.

+---------------------- EMC JCL Customization Utility ----------------------+ | COMMAND ==> _____________________________________________________________ | | | | Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. | | | | CLIST library ==> 'EMC.GDDR310.RIMLIB' | | Edit macro name ==> GDR | | Product dsname prefix ==> EMC.GDDR310 | | Mainframe Enablers | | dsname prefix ==> EMC.MFE700 | | SMP/E dsname prefix ==> EMC.SMPE | | SMP/E datasets volser ==> ______ | | Install-to disk volser==> AAP005 Disk unit name ==> SYSDA | | | | Enter your job card below ('%MEMBER%' will be replaced by member name): | | => //%MEMBER% JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1) | +---------------------------------------------------------------------------+


Installing EMC GDDR

Result: If the dialog completes successfully, you see something similar to the following:

BUILDING AN EDIT MACRO(GD) IN 'EMC.GDDRvrm.RIMLIB'PROCESSING MEMBER: #01ALLOCPROCESSING MEMBER: #02DDDEFPROCESSING MEMBER: #03RECEVPROCESSING MEMBER: #04APPLYPROCESSING MEMBER: #05ACCPTPROCESSING MEMBER: #06CLEANPROCESSING MEMBER: #91HFSPROCESSING MEMBER: #92CMHFSPROCESSING MEMBER: #99MAINT***

Run the installation jobsCarefully examine each job before you submit it to make sure that it was customized the way you intended.

Submit the customized jobs in the following order, making sure that each job completes successfully before submitting the next one:

1. #01ALLOC

2. #02DDDEF

3. #03RECEV

4. #04APPLY

You should expect completion codes of 0 (zero) for all jobs except for #02DDDEF, where 04 is acceptable if this is a new installation rather than an upgrade.

If your testing results are positive, run #05ACCPT to update the distribution libraries and zone. The #05ACCPT job completes with an RC=04. This is normal for the SMP/E ACCEPT process. You can ignore it.

SMP/E installation is now complete.

CleanupAfter you are satisfied that EMC GDDR is correctly installed and functioning properly, run the #06CLEAN job to delete datasets and DDDEFs used during the installation process that are no longer needed.

Apply maintenance updatesIf you have received maintenance cover letters from EMC or have instructions to apply maintenance from EMC support personnel, use the supplied job #99MAINT. This job receives and applies APARs and PTFs. This job may require further customization before you run it, depending on the nature of the maintenance.

Note: Do not attempt to apply maintenance until the EMC GDDR ACCEPT job has completed successfully and then only if instructed to do so by EMC Customer Service.

Post-installation tasksHaving completed the SMP/E installation steps, several more tasks remain to complete the installation of EMC GDDR. These tasks are described in detail in Chapter 3, ”Integrating EMC GDDR.”

Post-installation tasks 43

Installing EMC GDDR


3Invisible Body Tag

This chapter describes customization procedures for EMC GDDR.

◆ Overview ......................................................................................................................... 46◆ Update system parameter files..................................................................................... 47◆ Perform ConGroup Started Task automated startup................................................ 52◆ Specify EMC GDDR security........................................................................................ 54◆ Install EMC GDDR C-System started procedures..................................................... 60◆ Customize CA-OPS/MVS for EMC GDDR ............................................................... 64◆ Modify CA-OPS/MVS to use the GDDRMSG table ................................................. 70◆ Configure EMC GDDR.................................................................................................. 71

Integrating EMCGDDR

Integrating EMC GDDR 45

Integrating EMC GDDR

OverviewOnce you have completed the SMP/E installation steps, complete the tasks described in the following sections before using EMC GDDR:

◆ “Update system parameter files” on page 47

◆ “Perform ConGroup configuration” on page 51

◆ “Perform ConGroup Started Task automated startup” on page 52

◆ “Specify EMC GDDR security” on page 54

◆ “Install EMC GDDR C-System started procedures” on page 60

◆ “Customize CA-OPS/MVS for EMC GDDR” on page 64

◆ “Modify CA-OPS/MVS to use the GDDRMSG table” on page 70

◆ “Configure EMC GDDR” on page 71

CAUTION!These changes must be made on the EMC GDDR C-Systems ONLY.



Update system parameter filesPerform the following system parameter file updates:

HFS files and directories1. Customize and submit #91HFS RIMLIB job. This job allocates the Hierarchical

File System (HFS) and creates the GDDR USS directories.

2. Customize hlq.GDDRvrm.SAMPLIB(GDDRUSSC) by replacing 'hlq.GDDRvrm' with the high-level-qualifier of your site's USSEXEC library. Replace 'yourpath' with /gddr/usr, or the specific path for your USS executables.

3. Customize and submit the #92CMHFS RIMLIB job. This job copies the USS executables from the installation USSEXEC data set to the /usr/gddr directory created by step 1 above. On completion of the job, check that the p attribute has been added to the USS executables by listing the directory file contents - ls -l.

Note: #91HFS RIMLIB and #92CMHFS RIMLIB require appropriate user authorization to create root-level OMVS directories and to modify USS executable attributes. Refer to “RACF authorization for OMVS” on page 58 for assistance with this.

4. After #92CMHFS completes successfully, logon to the OMVS environment and issue the following commands:

su <===== sets super user authoritychmod 755 /usr/gddr/g* <===== sets access permissions for the HMC API programs

5. Repeat these commands on each C-system.

SYS1.PARMLIB( BPXPRMxx )◆ Add the following mount to the BPXPRMxx member of SYS1.PARMLIB:

Where ‘gddr_hfs_dataset_name’ is the name of the EMC GDDR HFS dataset allocated and filled during the installation process.

MOUNT FILESYSTEM(' gddr_hfs_dataset_name ') MOUNTPOINT('/usr/gddr') TYPE(HFS) MODE(RDWR)

Update system parameter files 47


SYS1.PARMLIB( IKJTSOxx )1. Check to make sure that the following entries exist in AUTHCMD and

AUTHPGM. Add any missing entries to the IKJTSOxx member of SYS1.PARMLIB.

2. Activate this change using an IPL or dynamically change by using the TSO PARMLIB UPDATE(xx) command.

APF authorization◆ APF-authorize the hlq.MFEvrm.LINKLIB, hlq.GDDRvrm.LINKLIB,

hlq.OPSvrm.LOAD, and hlq.OPSvrm.USSLOAD libraries. If you need assistance, follow the steps in the section “Provide APF Authorization for the Load Libraries”, in the CA-OPS/MVS Event Management and Automation Installation Guide.

To AUTHCMD add entries:SCFRDFME SCFRDFM6 EHCMSCM9SCFRDFM9EHCMSCMEEHCMSCM6GDDR1SMF

To AUTHPGM add entries:GDDFLISTGDDRDAP1 GDDRDAP3 GDDRXCMDGDDR1SMFGDDRSTATGDDRSSVIGDDRQFCNGDDRCGTPSCFRDFMEGDDRGVPSGDDRSTOK GDDRQRY5 SCFRDFM6 EHCMSCM9 EMCTF ECGCLEAN EHCMSCM6 EHCMSCME SCFRDFM9ECGUTIL

To AUTHTSF add entries:GDDR1SMFGDDRBALI

/* EMC ME utility /* EMC M6 utility /* EMC M9 utility/* EMC M9 utility/* EMC ME utility /* EMC M6 utility /* GDDR

/* SDDF list utility/* GDDR /* GDDR /* GDDR /* GDDR/* GDDR check for presence of an active task/* Initialize GDDR command queue /* Manipulate GDDR command queue /* GDDR - ConGroup communication /* EMC ME utility /* GDDR/* GDDR/* GDDR/* EMC M6 utility /* EMC M9 utility /* EMC TimeFinder Mirror /* EMC ConGroup cleanup utility/* EMC M6 MSC cleanup utility /* EMC ME MSC cleanup utility /* EMC M9 utility /* EMC ConGroup 6.4 cleanup utility

/* GDDR/* GDDR BAL interface

*/ +*/ +*/ +*/ +*/ +*/ +*/ +

*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +*/ +

*/ +*/ +



LINKLIST1. Add hlq.MFEvrm.LINKLIB,hlq.GDDRvrm.LINKLIB, hlq.OPSvrm.LOAD, and

hlq.OPSvrm.USSLOAD to the LINKLIST using one of the following methods:

• Add the following LNKLST entries in a PROGxx member:

or

• Add the following entries in a LNKLSTxx member:

where vrm is the current EMC GDDR version, release, modification identifier and vvvvvv is the volser where the hlq.GDDRvrm.LINKLIB dataset resides. The volser specification is only required if the dataset is not cataloged in the master catalog.

2. Replace hlq.GDDRvrm.LINKLIB with the dsname of the EMC GDDR LINKLIB SMP/E target library allocated and filled during the installation process. Activate this change using one of the following methods:

• IPL

• Issue the SET PROG=xx command

• Issue the SETPROG LINKLIST,ADD command

LNKLST ADD NAME(LNKLST) DSN(hlq.MFEvrm.LINKLIB)LNKLST ADD NAME(LNKLST) DSN(hlq.GDDRvrm.LINKLIB)LNKLST ADD NAME(LNKLST) DSN(hlq.OPSvrm.LOAD)LNKLST ADD NAME(LNKLST) DSN(hlq.OPSvrm.USSLOAD)

hlq.MFEvrm.LINKLIB(vvvvvv)hlq.GDDRvrm.LINKLIB(vvvvvv)hlq.OPSvrm.LOAD (vvvvvv)hlq.OPSvrm.USSLOAD (vvvvvv)

Update system parameter files 49


Authorize the EMC Consistency Group started task to use the trip APIEnsure that the user authorized to the ConGroup started tasks on the EMC GDDR C-Systems is also authorized with READ access to the EMC.CG.API.TRIP facility class.

The authorization commands are:

RDEFINE FACILITY EMC.CG.API.TRIP UACC(NONE)

PERMIT EMC.CG.API.TRIP CLASS(FACILITY) ID(uuuuuuu) ACCESS(READ)

Where uuuuuuu is the Userid assigned to the ConGroup STC on the C-systems at DC1 and DC2.

Note: Appendix A of the EMC Consistency Groups for z/OS Version 7.0 Product Guide provides detailed instructions.



Perform ConGroup configurationThe following configuration parameters apply to EMC GDDR installation in SRDF/S with ConGroup environments.

Unique ConGroup parameter members are required for DC1 and DC2:

◆ Within the ConGroup parameters for the DC1 C-System, specify the GLOBAL parameter, with OWNER equal to the SMFid of the DC1 C-System. This ConGroup parameter member will be used when the primary DASD site is DC1.

◆ Within the ConGroup parameters for the DC2 C-System, specify the GLOBAL parameter, with OWNER equal to the SMFid of the DC2 C-System. This ConGroup parameter member will be used when the primary DASD site is DC2.

◆ Within ConGroup parameters for both the DC1 and DC2 C-System, specify the MODE parameter with the MULTI keyword. Use of the MULTI keyword enables the use of an internal lock, ALL-CONGROUPS to serialize many global operations to ensure the integrity of ConGroup’s functionality.

The ConGroup configuration parameters must be the same for the EMC GDDR C-system at a site and all the GDDR-managed production systems at that same site.

Refer to the EMC Consistency Group for z/OS Product Guide for more information about these configuration parameters.

Syntax: GLOBAL=(OWNER=DC1 C-System SMFid)

Syntax: GLOBAL=(OWNER=DC2 C-System SMFid)

Syntax: MODE=MULTI

Perform ConGroup configuration 51


Perform ConGroup Started Task automated startupBy default, EMC GDDR does not perform ConGroup Stop/Start commands. The use of ConGroup Stop/Start commands is controlled by the Perform EMCCGRP Shutdown and Perform EMCCGRP Startup call overrides, which are available for certain scripts. When invoked, these call overrides stop or start the ConGroup started tasks running on all LPARs under EMC GDDR management; this includes C-Systems, production systems, and contingency systems.

Note: Table 11, “EMC GDDR call overrides,” on page 165 contains descriptions of the call overrides.

EMC GDDR allows some flexibility in the way you specify the location of the software parameters for the ConGroup STCs on each LPAR.

The //CONFIG member included in the ConGroup STC startup proc contains the ConGroup startup parameters which define the consistency group. The name for the //CONFIG member can be specified in two ways:

1. Hard-code the name within the startup JCL.

If the //CONFIG member name is hard-coded within the startup JCL, then any EMC GDDR script that starts ConGroup creates a ConGroup startup command string similar to the following:

S cgstcname

where:

cgstcname is the ConGroup proc name.

2. Use a procedure substitution variable called MBR to reference a PDS member name.

If the JCL procedure substitution variable MBR is used, then any EMC GDDR script that starts ConGroup creates a ConGroup startup command string similar to:

S cgstcname,MBR=cgrp_mbr

where:

cgstcname is the ConGroup proc name.

MBR is a JCL procedure substitution variable name required by EMC GDDR which must be defined in your JCL procedure. hlq.GDDRvrm.SAMPLIB(GDDRCGRP) shows the usage of this variable.

cgrp_mbr is the member name assigned to variable MBR to be substituted in the //CONFIG DD.

Determining which command string to use

In the Define Mainframe Enablers STCs panel shown in Figure 40 on page 120, the you can define the following parameters:

◆ System

The MVS system name of the system to which the statement applies.

◆ STC name

The started task name associated with Type = CG. GDDRCGRP is recommended, but you may select a name that matches your actual ConGroup procedure name cgstcname.



◆ Parameter dataset and member names

X(CGRPCAX6) are recommended, but you may specify a member name of your choosing that matches your actual cgrp_mbr member name. X is used as a DUMMY dataset name for Consistency Group parameters, as the actual dataset name is not relevant to constructing a ConGroup start command.

The EMC GDDR scripts will use the variables to determine which of the command strings to use.

◆ If System, CG, STC Name, and Parameter Dataset name are supplied in the Define EMC Mainframe Enablers STCs panel, then EMC GDDR uses this value and builds command string:

S cgstcname,MBR=cgrp_mbr

where:

cgrp_mbr is the value assigned to procedure variable MBR.

◆ If a parameter member name is not supplied for type=CG in the Define EMC Mainframe Enablers STCs panel, then the value of cgstcname is derived from the STC Name field associated with Type=CG, in the Define Mainframe Enablers STCs panel. EMC GDDR assumes that the // CONFIG DD member name value is hardcoded in the JCL procedure and builds the following command string:

S cgstcname

Note: The Define Mainframe Enablers STCs panel field descriptions following Figure 40 on page 120 provide detailed information regarding these parameters.

Perform ConGroup Started Task automated startup 53


Specify EMC GDDR securityThis section describes how to define the security environment required by EMC GDDR C-Systems.

EMC GDDR RACF functional groupsIt is recommended that the following RACF groups be defined to grant the appropriate access based upon job function.

Summary of RACF permissions

Table 6 provides an overview of the RACF profiles and permissions required to protect EMC GDDR resources.

Table 5 RACF functional groups

Functional group Description

GDDR$ADM For systems programmers who will install and configure EMC GDDR.For EMC GDDR administrators who will configure EMC GDDR.

GDDR$USR For operators and operations support staff who will operate EMC GDDR.

GDDR$REV For management or interested parties who require the EMC GDDR Parameter Review capability.

GDDR$STC For the EMC GDDR monitors, planned and unplanned processes.

Table 6 RACF permissions (1 of 2)

EMC GDDR resource owning group

EMC GDDR STC’s user group

EMC GDDR user group

EMC GDDR reviewer group

Admin/Sysprog user group

GDDR$ GDDR$STC GDDR$USR GDDR$REV GDDR$ADM

Dataset profilehlq.GDDRvrm..LINKLIBhlq.GDDRvrm..ISPMLIBhlq.GDDRvrm..OPSEXEChlq.GDDRvrm..ISPPLIBhlq.GDDRvrm..PROCLIBhlq.GDDRvrm..ISPSLIBhlq.GDDRvrm..PARMLIBhlq.GDDRvrm..GLOBAL.VARS.*hlq.GDDRvrm..*hlq.GDDRvrm..BKUPVARS.CNTL

Access needed--READ-READREADREADALTER-READ

Access needed-READREADREAD-READ---READ

Access needed-READREADREAD------

Access neededALTERALTERALTERALTERALTERALTERALTERALTERALTERALTER



◆ hlq is any dataset high level qualifier, if one is used.

◆ JES2node is the JES2 node name of the EMC GDDR C-System. The JES2 node name can be determined by issuing the JES2 console command $DNODE,OWNNODE=YES on the appropriate EMC GDDR C-System.

The output of the JES2 command is as follows:

$HASP826 NODE(1) $HASP826 NODE(1) NAME=MFSYS3,STATUS=(OWNNODE),AUTH=(DEVICE=YES,$HASP826 JOB=YES,NET=NO,SYSTEM=YES),TRANSMIT=BOTH, $HASP826 RECEIVE=BOTH,HOLD=NONE,PENCRYPT=NO, $HASP826 SIGNON=COMPAT,DIRECT=NO,ENDNODE=NO,REST=0, $HASP826 SENTREST=ACCEPT,COMPACT=0,LINE=0,LOGMODE=, $HASP826 LOGON=0,NETSRV=0,OWNNODE=YES, $HASP826 PASSWORD=(VERIFY=(NOTSET),SEND=(NOTSET)), $HASP826 PATHMGR=YES,PRIVATE=NO,SUBNET=,TRACE=YES

The actual JES2 node name is identified on the NAME=output statement.

◆ All EMC GDDR RACF non-generic profiles should have a universal access (UACC) of NONE.

Note: Members GDDCRACF and GDDPRACF in hlq.GDDRvrm.SAMPLIB list the RACF commands used for EMC GDDR. These commands are used to define all required EMC GDDR resources to RACF, and permit access to EMC GDDR resources.

GDDR$ GDDR$STC GDDR$USR GDDR$REV GDDR$ADM

FACILITY profileGDDR.CBU.ACTIVEGDDR.CBU.UNDOGDDR.HMC.LISTOBJECTSGDDR.HMC.GETMSGSGDDR.HMC.RESETCLEAR GDDR.HMC.LOAD GDDR.HMC.STARTSTOP GDDR.HMC.ACTIVATE GDDR.HMC.DEACTIVATE GDDR.HMC.SENDCMD

Access neededREADREADREADREADREADREADREADREADREADREAD


Access needed----------


TSOAUTH profileOPER

Access neededREAD

Access needed-

Access needed-

SURROGAT profileGDDR.SUBMIT

Access neededREAD

Access neededREAD

Access neededREAD

JESSPOOL profileJes2node.GDDR.*.*.*.*

Access needed-

Access neededREAD

Access neededALTER

Table 6 RACF permissions (2 of 2)


EMC GDDR STC’s user group

EMC GDDR user group

EMC GDDR reviewer group

Admin/Sysprog user group

Specify EMC GDDR security 55


OPERCMDS class resource definitions (optional)If command authorization checking is in place, refer to the following OPERCMDS class resource definitions in Table 7. Sample commands are supplied in &hlq.GDDR&vrm.SAMPLIB(GDDCRACF).

EMC GDDR user interface securityYou may choose to implement role-based access controls with EMC GDDR user interface facility profiles. Your site's security authorization product is used to control access to the entire EMC GDDR user interface, to selected menus, and to selected actions within menus.

Table 7 RACF permissions, OPERCMDS class


CLASS OPERCMDS Command/keyword GDDR$STC GDDR$USR GDDR$ADM

MVS.REPLY REPLY READ READ

MVS.MODIFY.STC.*.* MODIFY jobnameMODIFY jobname.idMODIFY id

UPDATE UPDATE -

Table 8 Summary of GDDR ISPF RACF permissions (1 of 2)

Facility profile Panel-ID[Function-Description]GDDR$ADMgroup

GDDR$USRgroup

GDDR$REV group

GDDRISPF.ACCESS GDDRPRIM [GDDR Primary Options Menu] READ READ READ

GDDRISPF.SETUP.* GDDRMNT0 [All Setup and Maintenance Actions]

GDDRISPF.SETUP.ACCESS GDDRMNT0 [Setup and Maintenance Submenus] READ READ

GDDRISPF.SETUP.PARMS.* Authorizes all Parameter Edit, Validate and Activate actions

GDDRISPF.SETUP.PARMS.ACCESS GDDRMNT0 [Perform GDDR Setup and Maintenance Functions]

READ READ READ

GDDRISPF.SETUP.PARMS.BACKUP GDDRPRM0 [Manage GDDR Parameter backups] READ

GDDRISPF.SETUP.PARMS.LOAD Authorizes Parameter Edit and Validation actionsGDDR0PRJ [Update personal GDDR ISPF Profile,Jobcards for your user]GDDRPRMI [Parameter Management Options Menu]GDDRPRM0 [Select Parameter Input Dataset]GDDRPRM0 [Define Configuration Basics]GDDRPRM0 [Define Storage objects]GDDRPRM0 [Define Host objects]GDDRPRM0 [Specify GDDR Options]GDDRPRM0 [Validate GDDR Parameter Set]

READ



Note: Member GDDIRACF in hlq.GDDRvrm.SAMPLIB list the RACF commands used for EMC GDDR ISPF permissions. These commands are optionally used to protect EMC GDDR functions.

Facility profile Panel-ID[Function-Description]GDDR$ADMgroup

GDDR$USRgroup

GDDR$REV group

GDDRISPF.SETUP.PARMS.REVIEW Authorizes Parameter Review actionsGDDRPRMI [Parameter Management Options Menu]GDDRPRM0 [Select Parameter Input Dataset]GDDRPRM0 [Define Configuration Basics]GDDRPRM0 [Define Storage objects]GDDRPRM0 [Define Host objects]GDDRPRM0 [Specify GDDR Options]

READ

GDDRISPF.SETUP.PARMS.ACTIVATE GDDRPRM0 [Activate GDDR Parameter Set] READ

GDDRISPF.SETUP.DEBUG GDDRMNT0 [Message, Debug and Trace options] READ READ

GDDRISPF.SETUP.QUEUE GDDRMNT0 [Manage GDDR Internal Command Queue]

READ

GDDRISPF.SETUP.DISCOVERHMC GDDRMNT0 [Perform HMC Discovery]GDDRACT0 [Perform HMC Discovery]

READ

GDDRISPF.SETUP.REFRESH GDDRMNT0 [Refresh GDDR Message Table] READ

GDDRISPF.SETUP.AUTO GDDRPRIM [GDDR ON / OFF Automation]GDDRMNT0 [GDDR ON / OFF Automation]

READ

GDDRISPF.SETUP.STATE GDDRMNT0 [Manage GDDR System variables] READ

GDDRISPF.SETUP.SITEROLES GDDRROLO [Manage Site Roles] READ

GDDRISPF.SCRIPTS.* Authorizes all Script management actions

GDDRISPF.SCRIPTS.CHECKUP GDDRPRIM [Perform pre-script checkup] READ READ

GDDRISPF.SCRIPTS.RUN.ACCESS GDDRPRIM [Run GDDR Scripts] READ

GDDRISPF.SCRIPTS.MANAGE.JCL GDDR0PRJ [Jobcards for your user] READ READ

GDDRISPF.SCRIPTS.VIEWSTATS GDDRPRIM [View GDDR Script Statistics] READ

GDDRISPF.VIEW.CONFIG GDDRPRIM [View GDDR configuration] READ READ

GDDRISPF.ACTIONS.* Authorizes all GDDR CBU, HMC and SYSPLEX actions

GDDRISPF.ACTIONS.ACCESS GDDRPRIM [Perform GDDR Actions] READ READ

GDDRISPF.ACTIONS.CBU.ACCESS GDDRACT0 [Perform HMC CBU actions] READ READ

GDDRISPF.ACTIONS.CBU.site.cpc Authorizes CBU actions by SITE and CPC READ READ

GDDRISPF.ACTIONS.HMC.ACCESS GDDRACT0 [Perform HMC LPAR actions] READ READ

GDDRISPF.ACTIONS.HMC.lpar_name Authorizes HMC actions by LPAR name READ READ

GDDRISPF.ACTIONS.SYSPLEX GDDRACT0 [Manage Couple Datasets] READ READ

GDDRISPF.OPS.ACCESS GDDRPRIM [Access CA-OPS/MVS] READ READ

Table 8 Summary of GDDR ISPF RACF permissions (2 of 2)



RACF authorization for OMVS

Use of the OMVS extended attribute command (extattr) requires authorization as described by the following RACF commands:

RDEFINE FACILITY BPX.FILEATTR.PROGCTL UACC(NONE)PERMIT BPX.FILEATTR.PROGCTL CLASS(FACILITY) ID(your-user-ID) ACCESS(READ)

Where your-user-ID is the ID of the installer. Access to this facility is needed to set the extended attributes on the gddrc* OMVS programs. This is completed at installation by the job in the #91HFS RIMLIB member.

Use of GDDR USS modules requires authorization described by the following RACF commands:

RDEFINE FACILITY BPX.SERVER UACC(NONE)PERMIT BPX.SERVER CLASS(FACILITY) ID(GDDR$USR) ACCESS(READ)

These commands are also included in the SAMPLIB(GDDCRACF) member.

RACF authorization for HMC LPAR actions

The facility profile GDDRISPF.ACTIONS.HMC.system_name provides for site-specific authorization of EMC GDDR LPAR processing. Authorization is enabled through the EMC GDDR panel “Option L: Perform HMC LPAR Actions” shown on page 154. Following your specification of GDDRISPF.ACTIONS.HMC facility profiles, the Perform HMC LPAR Actions panel will only list the system names for actions by authorized EMC GDDR users. Unprotected system names will display for any EMC GDDR user.

The value of system_name corresponds to the name found in the system field of the Define Managed LPARs panel shown on page 109. You can use generic or discrete system names in the facility profile.

The following rules apply to generic profile names, where valid generic characters are *, %, and **:

◆ Specify % in the profile name to match any single non-blank character (except a period) in the same position of the system ID name.

◆ Specify * or ** in the profile name to match more than one character in the same position of the system ID name.

The z/OS Security Server RACF Command Language Reference, SA22-7687, provides detailed descriptions and examples that illustrate how to specify generic profile names.

Note: The sample GDDRISPF.ACTIONS.HMC facility profile definition, supplied with hlq.GDDRvrm.SAMPLIB member GDDCRACF authorizes all systems to users who are connected to the GDDR$USR group.



Examples The following examples demonstrate the use of the GDDRISPF.ACTIONS.HMC facility profile:

Example 1 RDEFINE FACILITY GDDRISPF.ACTIONS.HMC.** UACC(NONE) OWNER(GDDR$ADM)PERMIT GDDRISPF.ACTIONS.HMC.ZOSESYS* CLASS(FACILITY) ACCESS(READ) ID(GDDR)

In the above example, the GDDR HMC LPAR Actions panel at a given EMC GDDR C-System will display all system names defined in the System field of the Define Managed LPARs panel that match the generic name 'ZOSESYS*' for all users connected to the group 'GDDR'. System names which do not match 'ZOSESYS*' are protected and will not be displayed on any GDDR HMC LPAR Actions panel.

Example 2 RDEFINE FACILITY GDDRISPF.ACTIONS.HMC.ZOSESYS1 UACC(NONE) OWNER(GDDR$ADM)PERMIT GDDRISPF.ACTIONS.HMC.ZOSESYS1 CLASS(FACILITY) ACCESS(READ) ID(SYSPGM1)

In the above example, the GDDR HMC LPAR Actions panel at a given EMC GDDR C-System will display only system name ZOSESYS1 for user SYSPGM1. All other systems defined in the System field of the Define Managed LPARs panel are not protected and therefore will be displayed on the GDDR HMC LPAR Actions panel.

Mainframe Enablers EMCSAFI security interface authorization

If you have protected access to Consistency Group and SRDF Host Component commands, authorize the GDDR userid and the GDDR$STC group with SAF profiles described in the Configuration chapters of the EMC Consistency Groups for z/OS Version 7.0 Product Guide and EMC SRDF Host Component for z/OS Version 7.0 Product Guide.

If TimeFinder/Mirror for z/OS and TimeFinder/Mirror clone emulation are in use and commands are protected, the GDDR userid and the GDR$STC group also require authorization.

Similarly, if devices to be managed by EMC GDDR have been protected using the EMCSAFI security interface of EMC ResourcePak Base for z/OS, authorization must be added for the GDDR userid and the GDDR$STC group.

The EMC Mainframe Enablers Installation and Configuration Guide provides information about the security interface and the class and resource names used.



Install EMC GDDR C-System started proceduresThe EMC GDDRMAIN, Heartbeat Monitor, and z/OS Console Monitor tasks must be started and remain running on the EMC GDDR C-Systems at all times. Before using EMC GDDR, you must customize these started procedures and make them available.

Note: Use automation to start the EMC GDDR procedures on the EMC GDDR C-Systems at system startup. No EMC GDDR or CA OPS/MVS started tasks are to be started SUB=MSTR.

1. Update members GDDRMAIN and GDDRHBM so that the following DD statements point to the datasets resulting from your SMP/E installation: OPSEXEC, ISPPLIB, ISPMLIB, ISPSLIB, and SYSTSIN.

2. Make the EMC GDDR started procedures available to the C-Systems by copying members GDDRMAIN, GDDRHBM, and GDDRPBAL from hlq.GDDRvrm.PROCLIB to SYS1.PROCLIB or equivalent library for started tasks.

3. Make the z/OS Console Monitor available on each GDDR-managed production system by copying member GDDRPBAL from hlq.GDDRvrm.PROCLIB to SYS1.PROCLIB or an equivalent library accessible to the production systems.

4. If you plan to use customized versions of GDDR user exits, concatenate your own OPSEXEC library containing your compiled user exits ahead of hlq.GDDRvrm.OPSEXEC.

Note: “User exit programming considerations” on page 204 provides more information.

5. Determine if the environment contains more than one instance of the Symmetrix Control Facility (SCF) started task.

The GDDRMAIN, GDDRPBAL and GDDRHBM started tasks and the CA-OPS/MVS OPSOSF started tasks must be associated with a specific SCF instance. This is accomplished by providing a //SCF$xxxx DD DUMMY statement in the started procedure of the SCF started task which will be the SCF instance that each of the GDDR started tasks and the OPSOSF started tasks are to have in common. The value substituted for xxxx is a user-supplied value that is unique to the SCF instance and the GDDR started procedures.

6. If the EMC Mainframe Enablers linklib dataset is not in the linklist concatenation, add it to the STEPLIB concatenation in each GDDRMAIN PROC member.



Define GDDR data in virtual datasets

You must define a DIV dataset for each C-system. For an example, see GDDIVDEF in hlq.GDDRvrm.SAMPLIB. The DIV dataset name is conveyed to GDDRMAIN as follows:

◆ Add a line to the GDDMPARM member of hlq.GDDRvrm.PARMLIB defining the DIV dataset name for the system and GDDR instance.

The format of the lines in GDDMPARM is as follows:

• Columns 1-8

The 8-character GVDIVDSN constant.

Note: Statements with an asterisk (*) in column 1 are comments and are ignored.

• Columns 10-17

The 8 character MVS system name of an EMC GDDR C-System which is specified using the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or equivalent parameter file. Note that this is not the SMF id of the system (although it could be the same).

• Columns 19-22

The 1-4 character left-justified name of the GDDR instance to which this applies. This supports multiple GDDR instances on a single C-System. This field will always contain GDDR.

• Columns 24-67

The left-justified dataset name of the DIV.

The GDDMPARM member and its PDS are pointed to by the GDDRPARM DD in the GDDRMAIN JCL.

Customize EMC z/OS Console Monitor started procedures

1. Edit the GDDRPBAL started procedure for each production system that requires monitoring:

a. Specify PSYS as the value in the PARM statement.

b. Change SCF$xxxx to the value shared by the GDDRMAIN and GDDRHBM started tasks.

c. Make the EMC GDDR GDDRPBAL message table available to the production systems by copying member GDDRMSGR from hlq.GDDRvrm.PARMLIB to SYS1.PARMLIB or an equivalent library for parameters.

d. Change the library name and member name referenced by the MESSAGES DD statement to be the library selected in step c and change the member name to GDDRMSGR.

Note: Use automation to start the EMC GDDR z/OS Console Monitor procedure on the EMC GDDR-managed production systems at system startup.

2. Edit the GDDRPBAL started procedure for each GDDR C-System:

a. Specify CSYS as the value in the PARM statement.

b. Change SCF$xxxx to the value shared by the GDDRMAIN and GDDRHBM started tasks.

Install EMC GDDR C-System started procedures 61


c. Make the EMC GDDR GDDRPBAL message table available to the C-Systems by copying member GDDRMSGC from hlq.GDDRvrm.PARMLIB to SYS1.PARMLIB or an equivalent library for parameters.

d. Change the library name and member name referenced by the MESSAGES DD statement to be the library selected in step c and change the member name to GDDRMSGC.

Note: Use automation to start the EMC GDDR z/OS Console Monitor procedure on the GDDR C-Systems at system startup.

Customize member GDDRPROCCustomize member GDDRPROC in hlq.GDDRvrm.PROCLIB used to run EMC GDDR scripts to your environment.

1. Update the STEPBLIB DD statement to include the following load libraries:

• hlq.GDDRvrm.LINKLIB resulting from your EMC GDDR SMP/E installation

• Your EMC Mainframe Enablers load library

• Your ISPF load library

• Your CA-OPS/MVS load library and USS load library

2. Make sure the following DD statements refer to the EMC GDDR datasets resulting from your GDDR SMP/E installation:

• OPSEXEC

• ISPPLIB

• ISPMLIB

• ISPSLIB

3. If you plan to use customized versions of GDDR User Exits, concatenate your own OPSEXEC library containing your compiled User Exits ahead of hlq.GDDRvrm.OPSEXEC.


Allocate the parameter backup dataset and your parameter wizard work dataset1. Allocate the dataset that will be used to contain backups of EMC GDDR

parameters.

Backups of EMC GDDR global variables are made when the following events occur:

• When you perform an Activate change to a parameter

• When the EMC GDDR Heartbeat Monitor starts

• When you complete Option B, Manage GDDR Parameter backups, from the Parameter Management Options menu

Note: EMC recommends the use of two parameter backup datasets—one for parameter management functions and the other for backups performed when the Heartbeat Monitor initializes.



2. Customize and run the job in member GDDRABDS in hlq.GDDRvrm.SAMPLIB. Ensure it has run successfully.

• The parameter backup dataset name to be used for parameter management functions is defined to EMC GDDR in your personal GDDR ISPF Profile, Option P on the GDDR Primary Options Menu. Refer to “Option P: Profile—Update Personal GDDR ISPF Profile” on page 82 for assistance.

• The parameter backup dataset to be used for Heartbeat Initialization backups is defined to EMC GDDR in the Define GDDR Datasets panel using the BKUPVARS field type. Refer to “Option D: Define GDDR Datasets” on page 99 for details.

• The parameter wizard work dataset for your userid is a PDS with the same attributes as a parameter backup dataset, which serves the purpose of a temporary store for EMC GDDR parameters in preparation of a GDDR parameter activation.

Install EMC GDDR C-System started procedures 63


Customize CA-OPS/MVS for EMC GDDRThis section describes updates that are required in order to make EMC GDDR available as a CA-OPS/MVS user application.

Step 1: Include EMC GDDR libraries in OPSVIEW REXX exec

Note: EMC recommends that you customize and use the provided sample EMC GDDR invocation REXX (GDDREXC) to access the GDDR Online facilities. This method provides immediate access to the GDDR Primary Option menu, while still allowing seamless access to all CA-OPS/MVS functions, as allowed by local security policies.

Instructions below are given for users who prefer to access EMC GDDR from the CA-OPS/MVS User Applications Menu.

EMC GDDR libraries must be added to the OPSVIEW startup REXX exec (often OPSVLBDF). Follow these guidelines:

◆ Include hlq.GDDRvrm.ISPMLIB as the first library in the OPSMLIB concatenation.

◆ Include hlq.GDDRvrm.ISPSLIB as the first library in the OPSSLIB concatenation.

◆ Include hlq.GDDRvrm.ISPPLIB as the first library in the OPSPLIB concatenation.

◆ Include hlq.OPS.vrm.USSLOAD in the OPSLLIB concatenation.

◆ Include hlq.GDDRvrm.OPSEXEC as the first library in the OPSEXEC concatenation.

◆ If you plan to use customized versions of EMC GDDR user exits, concatenate your own OPSEXEC library containing your compiled user exits ahead of GDDR.OPSEXEC.


◆ Add a GDDRSLIB DD statement pointing to the same datasets as the OPSSLIB concatenation.

◆ The hlq.GDDRvrm.LINKLIB library is not needed in the OPSLLIB concatenation, but must be included in the system linklist concatenation.

Step 2: Merge CA-OPS/MVS user applications (optional)Access to the EMC GDDR ISPF panels is enabled by the GDDR invocation REXX exec or by the addition of the GDDR application to your site's pre-existing CA-OPS/MVS installation. “Step 1: Customize the GDDR invocation REXX exec” provides direction if EMC GDDR and CA-OPS/MVS are being installed together. The following instructions apply in lieu of the use of the GDDR invocation REXX exec, where EMC GDDR is being installed in addition to pre-existing CA-OPS/MVS applications.

CA-OPS/MVS panel OPSUSER can be customized to provide access to EMC GDDR’s online facilities. If OPS/MVS is already in use in your environment, you will need to modify the OPSUSER panel to include the EMC GDDR application.

◆ Do this by adding the following EMC GDDR option:

nn,'PGM(OI) PARM(GDDISTRT GDDR oooo)

where oooo is a mandatory argument and is the CA-OPS/MVS SSID active on the current C-system



Step 3: Make EMC GDDR AOF rules available to CA-OPS/MVS

1. Update the CA-OPSMVS initialization parameters found in CAOPS.V116.OPS.CNTL with the distributed EMC GDDR rules found in hlq.GDDRvrm.AOFRULES. Update the parameters RULEPREFIX and RULESUFFIX with the required values.

Note: The initialization parameters are the PDS member used during OPSMAIN STC initialization (z/OS command: S OPSMAIN,M=OPSSPAxx, where xx represents the last 2 characters of the LPAR name). These are used to override default values used during CA/OPS execution. RULEPREFIX and RULESUFFIX are documented in the CA-OPS/MVS Getting Started Guide, pages 3-14 to 3-16.

EMC recommends setting RULEPREFIX and RULESUFFIX as follows:

RULEPREFIX= hlq.GDDRvrmRULESUFFIX= AOFRULES

CA-OPS/MVS will concatenate the two to dynamically allocate and open the rules file as hlq.GDDRvrm.AOFRULES.

The following is an example of OPSMAIN edited start JCL, where 00 points to SYS2.PARMLIB(OPSSPA00):

//OPSMAIN PROC SSID=OPSS, // MAINPRM=NONE, // MEMBER=00

The following is an example of member OPSSPA00:

T = OPSPRM_Set("OSFCHAR","!") T = OPSPRM_Set("ECFCHAR","?") T = OPSPRM_Set("RULEPREFIX","hlq.GDDRvrm") T = OPSPRM_Set("RULESUFFIX","AOFRULES") T = OPSPRM_Set("OSFMIN",4) T = OPSPRM_Set("OSFMAX",8) T = OPSPRM_Set("REXXMAXQUEUE","6000")

Copy CAOPS.V116.OPS.CNTL(member) to the system Parmlib member you want to contain the OPSMAIN start JCL initialization member.

2. Ensure messages necessary for comprehensive system event correlation are routed from managed production systems to C-Systems.

Refer to “Customize EMC z/OS Console Monitor started procedures” on page 61. The z/OS Console Monitor propagates messages associated with events of interest to the GDDR Event Monitor.

3. Enable the AOF rules as follows:

a. On the OPSVIEW Primary Menu (shown in Figure 75 on page 158), select 4 - Control and press Enter. On the next panels, select 5 - AOF Control and 1 - Control AOF Rules.

b. Configure the following fields on the AOF Control Entry panel:– Rule Set field - Leave blank to list all rule sets– Stats field - Enter N– System field - Enter *LOCAL*

c. After the information has been entered, the Rule Set List is displayed.

d. Use line command A to set the rule set to Autoenable.

e. Use line command E to enable the GDDR AOF rule set.

Customize CA-OPS/MVS for EMC GDDR 65


4. If your site uses Computer Associates TOP SECRET, copy hlq.GDDRvrm.SAMPLIB(GDDRSEC1) to your hlq.GDDRvrm.AOFRULES and re-enable AOFRULES.

5. Repeat steps 1-4 for each C-System.

Step 4: Set REXX and TSO transaction limits in the CA-OPS/MVS OPSMAIN parameters

1. Set the REXXMAXQUEUE parameter for the maximum number of lines that a REXX program can have in the external data queue for a given event.T = OPSPRM_Set("REXXMAXQUEUE","32768")

2. Set the OSFRUN and OSFCPU parameters to determine how long CA-OPS/MVS allows a TSO transaction to execute in an OSF TSO server. OSFRUN is an elapsed time limit; in comparison, the OSFCPU parameter limits execution time.

Together, OSFRUN and OSFCPU values correlate to the maximum elapsed time of tasks waiting for SRDF/Star recovery to be available. The initial recommended values for each are 12000 seconds, or 200 minutes. T = OPSPRM_Set("OSFCPU","12000")T = OPSPRM_Set("OSFRUN","12000")

3. Set the OSFWAIT parameter to determine the maximum time, in seconds, which a transaction can wait for input while in an OSF TSO server.

CA-OPS/MVS sets the server address space wait time limit based on the value of OSFWAIT. The operating system checks only every 100 seconds for any waiting address space that has exceeded the wait time limit. As a result, the exact time when an OSF TSO server is terminated is unpredictable. The initial recommended value is 12000 seconds.T = OPSPRM_Set("OSFWAIT","12000")

4. Set the OSFOUTLIM parameter to limit the number of console messages a transaction running under an OSF TSO server can produce. T = OPSPRM_Set("OSFOUTLIM","100000")

5. Repeat steps 1-4 for each C-System.

Note: For more information, refer to the CA-OPS/MVS Event Management and Automation Parameter Reference, Chapter 3, Parameters for Facilities.

Step 5: Enable SMF Support in CA-OPS/MVSThe EMC GDDR Audit Monitoring Function uses the SMF Support feature in CA-OPS/MVS.

◆ Specify that SMF support is required along with a user-selected SMF record number by including the following parameters in the OPSMAIN parameters defined for each C-System: T = OPSPRM_SET("INITSMF","YES") T = OPSPRM_SET("SMFRECORDNUMBER","nnn") T = OPSPRM('SET("SMFRULEDISABLE','YES')

Where nnn is a number from 128 to 254, selected from the site's available SMF user record types.

Note: Chapter 8, ”Using the Audit Monitoring Facility,” describes how to set monitoring and retention options.



Step 6: Change CA-OPS/MVS access rules

Change the CA-OPS/MVS access rules to allow EMC GDDR to update global variables and use the CA-OPS/MVS OPSCMD function and to allow CA-OPS/MVS OPSOSF address spaces to use the CA-OPS/MVS OPSWTO function.

◆ In your hlq.GDDRvrm.AOFRULES dataset, add the lines of code shown below to members GLOBAL, OPSCMD and OPSWTO, which create SEC event rules.

Note: In the sample code below, gddr_racf_userid is the RACF user ID under which the EMC GDDR started procedures and processes will run. opsosf_racf_userid is the RACF user ID under which the OPSOSF started procedure will run.

For the GLOBAL and OPSCMD member:IF userid = "gddr_racf_userid" THEN RETURN "ACCEPT"

For the OPSWTO member:IF userid = "gddr_racf_userid" THEN RETURN "ACCEPT"IF userid = "opsosf_racf_userid" THEN RETURN "ACCEPT"

Step 7: Customize EMC GDDR user exit 7 (optional) ◆ Customize user exit 7, if necessary, as described in Appendix A, “EMC GDDR

User Exits.” Then copy the customized exit to the appropriate AOFRULES dataset.

Step 8: Update CA-OPS/MVS started procedure OPSOSF

CAUTION!These changes to OPSOSF must only be made on the EMC GDDR C-Systems.

1. Ensure that the OPSOSF CA-OPS/MVS started procedures EXEC statement specifies REGION=0M.

//OPSOSF EXEC PGM=IKJEFT01,REGION=0M,DYNAMNBR=100,TIME=1439, // PARM='%OSFSTART'

2. To the OPSOSF CA-OPS/MVS started procedure, add the OPSEXEC ddname if not already used, specifying the following EMC GDDR SMP/E target library:

hlq.GDDRvrm.OPSEXEC

If there is already an OPSEXEC ddname, insert this library as the first library in the concatenation.

3. Add the following symbolic variables to the PROC statement of the OPSOSF started procedure. Assign the same hlq and vrm substitution values used in the GDDR started procedure.

//OPSOSF PROC SSID=, // USRPFX1='hlq.MFEvrm',// USRPFX6='hlq.GDDRvrm'



4. Insert the following EMC host software LINKLIBs in the STEPLIB DD concatenation of the OPSOSF started procedure after the hlq.OPSvrm.USSLOAD library.

// DD DISP=SHR,DSN=&USRPFX1..LINKLIB // DD DISP=SHR,DSN=&USRPFX6..LINKLIB

Note: Reuse the existing instruction to add the OPSEXEC ddname with hlq.GDDRvrm..OPSEXEC here.

5. Add the following DD statements after the existing SYSTSIN DD statement in the OPSOSF started procedure. Assign the same SCF suffix used in the GDDR started procedure.

//SCF$nnnn DD DUMMY //SYSOUT DD SYSOUT=*,OUTLIM=16677215 //EMCSRDFR DD SYSOUT=*,OUTLIM=16677215 //DBUGFC21 DD SYSOUT=*,OUTLIM=16677215 //EHCPCR02 DD SYSOUT=*,OUTLIM=16677215

Step 9: Update the UNIX system service directory1. Add the following directories to the PATH and LIBPATH statements to the

OPSUSS STC parameter file: These statements allow EMC GDDR to load and run the HMC interface:

/usr/gddr/usr/gddr/source (home for HMC API)

2. Activate this change by recycling the OPSUSS started procedures.

3. To run the EMC GDDR HMC programs directly from the OMVS shell, add the following directories to the PATH and LIBPATH statements in the /etc/profile file:/usr/gddr/usr/gddr/source

Below are statement examples to accomplish this:

PATH=$PATH:/usr/gddr/source:LIBPATH=$LIBPATH:/usr/gddr/source:

Step 10: Define the EMC GDDR monitoring started tasks to CA-OPS/MVS SSM

To ensure that the GDDRMAIN started task and the EMC GDDR Heartbeat Monitor started task (GDDRHBM) are kept running at all times on the GDDR C-Systems, put them under the control of CA-OPS/MVS SSM (System State Manager) as follows:

1. Create the STCTBL RDF table or modify the existing table so that only the following entries exist for the EMC GDDR started procedures:

Name/Jobname Desired_State Mode Type PREREQ

GDDRMAIN UP A GDDRMAIN JES2 TCPIP

GDDRHBM UP A GDDRHBM JES2 TCPIP

GDDRPBAL UP A GDDRPBAL EMC ResourcePak Base



2. Create the STCTBL_ACT RDF table or modify the existing table so that only the following entries exist for the EMC GDDR started procedures:

Use OPSVIEW Primary Option 2.6 - Relational Table Editor for RDF to create the tables if they do not exist. Create the STCTBL table with the STC STATEMAN table model and create the STCTBL_ACT table with the ACTION STATEMAN model. Refer to Chapter 11, “Using the Relational Data Framework, Table Management Operations,” in the Unicenter CA-OPS/MVS Event Management and Automation User Guide or contact your CA-OPS/MVS administrator for more assistance.

Step 11: Update CA-OPS/MVS CCI parameters◆ On each C-System, add the following entries for the new C-System to the

CA Event Notification/CCI parameter member CCIssssssss:

• NODE( …add appropriate parameters for the new C-System…)

• CONN,ssssssss

where ssssssss is the MSF ID or the MVS system name of the new C-System.

Step 12: Apply CA-OPSMVS Usermod

1. Apply CA-OPS/MVS Usermod found in hlq.GDDRvrm.SAMPLIB(GDDCAZ01). This increases the CA-OPS/MVS REXX workspace to 3MB.

2. Make this change on all C-Systems.

ACTION_CURRENT ACTION_DESIRED ACTION_RES_TYPE ACTION_TEXT

DOWN UP GDDRMAIN …START &JOBNAME

DOWN UP GDDRHBM …START &JOBNAME

UP DOWN GDDRMAIN …CANCEL &JOBNAME

UP DOWN GDDRHBM …CANCEL &JOBNAME

DOWN UP GDDRPBAL …START &JOBNAME

UP DOWN GDDRPBAL …CANCEL &JOBNAME



Modify CA-OPS/MVS to use the GDDRMSG tableExternal text resides in an EMC GDDR PARMLIB member called GDDRMSG. At execution time, the external text information is stored in a CA-OPS/MVS SQL table called GDDRMSG. The GDDRMSG table is created when external text is requested by EMC GDDR code and the GDDRMSG table does not yet exist.

EMC GDDR loads the GDDRMSG table using the EMC GDDR PARMLIB member GDDRMSG. As a result, the EMC GDDR PARMLIB PDS must be specified within the OPSMLIB DD in hlq.GDDRvrm.PROCLIB(GDDRPROC).

◆ Specify the skeletons that execute scripts. For example, the following are changes in SYS3.DEVELOP.PROCLIB(GDDRPROC):

//OPSMLIB DD DISP=SHR,DSN=&USRPFX6..PARMLIB

Note that the ISPMLIB DD requirement is only needed the first time that the CA-OPS/MVS GDDRMSG SQL table is built. This table will persist until it is deleted (CA-OPS/MVS Opsview, option 2.6) or until CA-OPS/MVS is recycled.

Note also that the GDDRMSG table is built in each CA-OPS/MVS environment. For example, if you have two C-Systems named SYS3 and SYS4, the table will be built on each one, as required. The EMC GDDR PARMLIB dataset must be accessible to each EMC GDDR C-System.

◆ You can make temporary changes to the external text using CA-OPS/MVS Opsview, option 2.6.

◆ You can make permanent changes to the GDDRMSG PARMLIB member and then incorporate them into the EMC GDDR execution environment by using Option R, Refresh GDDR Message Table, as shown in Figure 7, “Setup and Maintenance Menu,” on page 84.

IMPORTANT!After applying maintenance to the EMC GDDR software, in many cases it will be necessary to refresh the message table. Note that unless special precautions are taken, this will erase any temporary or "permanent" changes you may have made previously.

If you prefer to access EMC GDDR from the CA-OPS/MVS User Applications Menu, and have performed the related tasks described in “Step 1: Include EMC GDDR libraries in OPSVIEW REXX exec” on page 64, the following change in the OPSVIEW exec is also needed for support of the GDDRMSG table.

◆ Specify the exec that takes you to CA-OPS/MVS using TSO ISPF =6. For example, the following are changes in hlq.OPSvrm.SAMPLES(OPSVIEW):

"ALLOC FI(OPSMLIB) REUSE SHR DA('"usrpfx6".PARMLIB'" ,"'"prefix".OPSMLIB')"



Configure EMC GDDRUse the EMC GDDR online facilities to complete the tasks described in this section.

Note: Review the introductory procedures described in Chapter 4, ”Using EMC GDDR Online Facilities” prior to performing the tasks listed in this section.

Step 1: Customize the GDDR invocation REXX exec

◆ Customize the GDDR invocation REXX exec for your installation. A sample REXX exec is supplied in hlq.GDDRvrm.SAMPLIB, member GDDREXC.

◆ Set opssid to the CA-OPS/MVS SSID running on the C-system where GDDR will be started.

◆ Set opspfx to the initial qualifiers of your CA-OPS/MVS installation's dataset names.

◆ Set ggdrpfx to the initial qualifiers of your EMC GDDR installation's dataset names.

An extract from the sample GDDREXC member is shown below:

/**********************************************************************//* Initialize custom variables *//**********************************************************************/opssid = "OPSS" opspfx = "CAOPS.V116SP1." gddrpfx = "EMC.GDDR310."

Step 2: Collect and review input parameter information

◆ Make a step in your implementation plan to record your site-specific values for reference during parameter build process which is completed using the GDDR Parameter Management Options Menu shown in Figure 8 on page 85.

The Parameter Management Options Menu presents parameter input panels which conditionally prompt for required parameter values based on your particular disaster restart topography and EMC SRDF configuration. The systems, devices, and EMC GDDR options defined during the parameter input task specify how EMC GDDR handles conditions requiring the use of EMC recovery and business continuity facilities.

Configure EMC GDDR 71


Step 3: Update your personal GDDR ISPF profile

When you complete the EMC GDDR software installation, dependent software installation, and related user-authorization definitions, the GDDR Primary Options Menu displays:

Note: This panel may vary based on relevant user authorizations.

Before you can perform any GDDR Setup and Maintenance actions, you must populate your ISPF profile dataset with basic information.

1. On the GDDR Primary Options Menu, select Option P, Update Personal GDDR ISPF Profile.

The Change GDDR ISPF Profile Variable Values panel displays as follows:

2. Complete the panel fields as follows:

• GDDR Subsystem Name — No action required. This field defaults to GDDR and is not editable.

------------------------- GDDR - Primary Options Menu ------------------------ P rofile Update Personal GDDR ISPF Profile This System: Q311 M aintenance GDDR Setup and Maintenance This Site: *** O OPS Access CA-OPS/MVS Master-C: ******* Primary Site: *** Primary DASD: *** Automation: *** Planned script: None Unplanned script: None

EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to Terminate GDDR ISPF Option ===>

-------------- GDDR - Change GDDR ISPF Profile Variable Values ---------------- Command ===> GDDR Subsystem Name ===> GDDR JCL dataset ===> ISPF skeleton dataset ===> Global variable backup ===> Host Component prefix ===> Default SCF suffix ===> Jobcards for your user: // // // //

Press <F3> when ready Enter CANCEL to return without changing any profile variable values Enter CLEAR to set all values to null and exit Enter RESET to restore the values as they were upon entry



• JCL dataset — Specify the name of the PROCLIB dataset holding the GDDRPROC customized during the GDDR integration procedure “Customize member GDDRPROC” on page 62.

• ISPF skeleton dataset — Specify the name of a dataset containing the GDDR file tailoring skeletons created when you downloaded the install cartridge.

• Global variable backup — Specify the name of the parameter backup dataset to be used for parameter management functions, defined during the EMC GDDR integration procedure “Allocate the parameter backup dataset and your parameter wizard work dataset” on page 62.

• Host Component prefix — Specify a 1-8 character command prefix to be used for internal Host Component API commands.

• Default SCF suffix — Specify the suffix to be appended to 'SCF$' to form the DDname on a DD statements and associate these with the specified SCF subsystem.

• Jobcards — This field displays if you are authorized to activate parameter changes and to manage GDDR scripts. The JOBCARD information you enter here applies only to the current user and is used for parameter activate and script submission tasks.

For example:

===>//JOBNAME JOB (acct-number),gddr-job,CLASS=A,===>// MSGCLASS=A,USER=GDDR,NOTIFY=GDDR===>/*JOBPARM LINES=999999===>//*

3. Press F3 to save the changes and return to the GDDR Primary Options Menu.

Step 4: Define initial parametersThe EMC GDDR parameter management process uses an existing backup of parameter values as the starting point for subsequent updates. To facilitate the parameter customization associated with a new EMC GDDR implementation, initial parameter definitions are supplied in hlq.GDDRvrm.SAMPLIB, in member GDDRSYNC.

Note: Subsequent parameter changes will be applied to a copy of your parameters, created as a backup dataset at the time the existing parameters were applied, or any later time.

To perform an initial parameter activation:

1. Copy the GDDRSYNC member from hlq.GDDRvrm.SAMPLIB to the Global Variable Backup dataset you specified in the GDDR ISPF Profile Variable Values panel shown in Step 1 on page 72.

2. From the GDDR Primary Options Menu, select Option M, Setup and Maintenance, then select Option P, Manage GDDR Parameters.



Because there are no existing parameters, Option P displays a Select Parameter Input Dataset panel as follows:

The GDDRSYNC member you copied from hlq.GDDRvrm.SAMPLIB in step 1 is an initial parameter set that provides basic settings which will be customized for your disaster restart topology and EMC SRDF configuration.

The GDDRSYNC member has no identifying information within your EMC GDDR installation, therefore it is an unregistered parameter backup. The 'showall' command updates the Parameter Input Member Selection list with members which you have previously copied to your specified parameter input dataset.

3. Type showall on the command line of the Select Parameter Input Dataset panel to display the GDDRSYNC member.

4. To begin parameter definition with an initial parameter set, type S in the Action field associated with GDDRSYNC and press Enter.

The panel displays a message requesting that you provide a work dataset name and a parameter load description:

------------------- GDDR - Select Parameter Input Dataset ---- Row 1 to 1 of 1 Parameter input dataset ===> JABCDE1.GDDR310.PARMS Selected Member ===> Unselect? ===> N (Y/N) Parameter Load work-dataset ===> ____________________________________________ Parameter Load description ===> _______________________________________ Last used GDDR Parameter Source and description: - *** Unknown *** - - No description found - Select '--NONE--' or choose a different GDDR Parameter Load input dataset. Press <F3> to return to the Parameter Management Options Menu Line commands: S elect, U nselect, B rowse, E dit ----------------------- Parameter Input Member Selection ---------------------- Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ --NONE-- 09/05/27 11:04 JABCDE1 GDDR parameter load from scratch ******************************* Bottom of data ******************************** Command ===>showall

------------------ GDDR - Select Parameter Input Dataset ------ Row 1 to 2 of 2 Parameter input dataset ===> EMC.GDDR310.PARMS Selected Member ===> GDDRSYNC Unselect? ===> N (Y/N) Parameter Load work-dataset ===> EMC.GDDR310.PARMS.WORK______________________ Parameter Load description ===> _______________________________________ Last used GDDR Parameter Source and description: - *** Unknown *** - - No description found - Please provide a work-dataset name and a description for this Parameter load. Press <F3> to return to the Parameter Management Options Menu Line commands: S elect, U nselect, B rowse, E dit ----------------------- Parameter Input Member Selection ---------------------- Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ --NONE-- 09/05/27 11:13 JABCDE1 GDDR parameter load from scratch _ GDDRSYNC ******************************* Bottom of data ********************************



5. Supply a parameter load work dataset and parameter load description.

Enter the parameter load work dataset that was defined earlier in “Allocate the parameter backup dataset and your parameter wizard work dataset” on page 62. This dataset contains your 'work-in-process', enabling you to assemble a complete parameter set by saving your input data from each of the parameter definition panels, and returning to the task at a later time.

Note: The parameter input dataset and the parameter load work dataset must be two different datasets. This is because the contents of the parameter load work dataset are overwritten when exiting the Select Parameter Input Dataset panel in step 6.

6. Press F3 to exit.

Upon exiting from the Select Parameter Input Dataset panel, the work dataset is initialized with the contents of the GDDRSYNC member. Messages associated with the work dataset initialization are returned to your TSO session as follows:

7. Upon selection of the initial parameter backup member and completion of the work dataset initialization process, the Parameter Management Options Menu displays with the complete list of parameter load functions as follows:

OPS0996I Preparing Work Dataset OPS0996I OPS0996I Validating Input variables: OPS0996I ===> CONFIG OPS0996I OPS0996I Writing work members: OPS0996I OPS0996I ==== > A01FEATR OPS0996I ==== > A02CSYST OPS0996I ==== > A03GDDDS OPS0996I ==== > C01ROLES OPS0996I ==== > E01CNTRL OPS0996I ==== > E02GDDGK OPS0996I ==== > E03MSCGK OPS0996I ==== > E04SRDFD OPS0996I ==== > E05TFDEV OPS0996I ==== > E06SDDF0 OPS0996I ==== > E07GNS00 OPS0996I ==== > H01SYSTS OPS0996I ==== > H02LPARS OPS0996I ==== > H03CPC00 OPS0996I ==== > H04IPL00

------------------ GDDR - Parameter Management Options Menu -------------------- Option ===> B ackup Manage GDDR Parameter Backups This System: Q311 This Site: *** .---------- Parameter Load functions ----------. Master-C: ******** | I nput Select Parameter Input Dataset | Primary Site: *** | C onfig Define Configuration Features | Primary DASD: *** | S ites Define Site Roles and Groups | | D ASD Define Storage Objects | Automation: *** | H ost Define Host Objects | Planned script: None | O ptions Specify GDDR Options | Unplanned script: None | V alidate Validate GDDR Parameter Set | | A ctivate Activate GDDR Parameter Set | |______________________________________________| EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Setup and Maintenance Menu



You can complete customizing the contents of the parameter work dataset with your site-specific values using the Parameter Load functions on the Parameter Management Options Menu. This process is identical for an initial parameter customization or for any subsequent customization. “Option P: Manage GDDR Parameters” on page 85 provides details on this process.

Step 5: Configure the EMC GDDR HMC interface

Perform the following procedures to configure the EMC GDDR Hardware Management Console (HMC) interface:

◆ Establish system connectivity to HMC consoles

◆ Download and configure the HMC API DLL

◆ Add HMC console communities

◆ Specify HMC community names to EMC GDDR

◆ Link-edit the HMC API DLL

◆ Verify the EMC GDDR HMC interface

Establish system connectivity to HMC consolesEstablish that connectivity exists between each C-System and its HMC console. You may do so by attempting to ping the console from the C-System. Use the following procedure for each site.

1. Log on to TSO and enter READY mode.

2. Enter the following command:

ping ip-address

where ip-address is the IP address you specified as the value of the HMC.siteid EMC GDDR parameter for the site you are currently testing.

Download and configure the HMC API DLLPerform the following steps:

1. Download the z/OS DLL containing the C/C++ language HWMCA Management API. This executable can be downloaded from IBM Resource Link. At this site, go to Services, then navigate to the z/OS API page, and download HWMCAAPI.

2. FTP the HWMCAAPI DLL in binary to the /usr/gddr/source directory on all C-Systems.

3. Add the p attribute to HWMCAAPI using the following shell command:

extattr +p HWMCAAPI

For more information, see “RACF authorization for OMVS” on page 58.

4. Link edit the HWMCAAPI into hlq.OPSvrm.USSLOAD loadlib. JCL is provided by CA in hlq.CNTL(INSTHWMC). More information is located in the Unicenter CA-OPS/MVS Event Management and Automation Administrator Guide r11.6, "Initiate an Action through CPC and LPAR Names".



Add HMC console communitiesAdd communities on your HMC console to support the EMC GDDR connection. Perform the following steps:

1. Using an HMC administrator user ID, start the SNMP configuration task (under console actions in the views area of the console).

2. Each HMC console must have a community name defined to be used by each site’s C-System. Add community names using the following guidelines:

• Name is the community name. EMC GDDR uses the system name of the connecting C-System, set to lowercase, as the default community name when initializing a connection with an HMC console. To use a different HMC community name, use the procedure described in “Option C: Define HMC Community Names” on page 114 to specify the name to EMC GDDR.

• Address specifies the IP address of the C-System that will use the community name specified by Name.

• Network Mask should be 255.255.255.255

• Protocol must be UDP.

• Access Type must be Read/Write.

3. If necessary, reboot the HMC service for the HMC consoles whose community names were changed or added.

Note: The IBM System z Application Programming Interfaces Guide, SB10-7030-09, Chapter 6, "Configuring for the Data Exchange APIs," provides information to assist you with HMC or Support Element Settings configuration tasks.

Specify HMC community names to EMC GDDREMC GDDR’s HMC interface requires that the community name used by EMC GDDR matches the community name specified for the generation of HMC support.

If, when configuring the HMC console as described above, you specified a community different from the system name of the C-System at the site where the HMC console is defined, you must specify this community name to EMC GDDR. To do so, follow the procedure described in “Option C: Define HMC Community Names” on page 114.

Verify the EMC GDDR HMC interfaceTo verify that the preceding steps have been performed correctly, test EMC GDDR’s ability to access the HMC consoles by performing the procedure described in “Option H: Perform HMC Discovery” on page 136. This should complete successfully, and the C-System HMC consoles should appear in the display.

If an error occurs, review the HMC interface install procedure.



Step 6: Modify EMC GDDR user exits (optional)

EMC GDDR provides exit points that you may use to augment EMC GDDR facilities. Sample exits are provided in the hlq.GDDRvrm.SAMPLIB distribution library. You may modify these exits, or write your own, following the guidelines presented in Appendix A, “EMC GDDR User Exits.” The exit points are the following:

◆ GDDRUX01 is called from planned or unplanned event scripts at a point appropriate for starting production mainframe workloads.

◆ GDDRUX02 is called from planned or unplanned scripts at a point appropriate for shutting down production mainframe workloads.

◆ GDDRUX03 is called from planned or unplanned scripts at a point appropriate for starting distributed production workloads.

◆ GDDRUX04 is called from planned or unplanned scripts at a point appropriate for stopping distributed production workloads.

◆ GDDRUX05 is called each time an EMC GDDR message is about to be issued at a point appropriate for creating alerts such as an SNMP event.

◆ GDDRUX06 is invoked each time an EMC GDDR message is about to be issued. Using this exit, you may process the message in any of several ways, suppress it entirely, or suppress it and substitute a different message.

◆ GDDRUX07 is called from each message rule during the rule initialization phase, permitting you to allow or bar the enabling of each message rule.


4Invisible Body Tag

This chapter describes the EMC GDDR online interface.

◆ Primary Options Menu.................................................................................................. 80◆ Option P: Profile—Update Personal GDDR ISPF Profile ......................................... 82◆ Option M: Maintenance—GDDR Setup and Maintenance...................................... 84◆ Option G: GDDR Config—View GDDR Configuration ......................................... 141◆ Option R: Roles—Manage Site Roles ........................................................................ 142◆ Option C: Checkup—Perform Pre-script Checkup................................................. 143◆ Option S: Scripts—Run GDDR Scripts...................................................................... 148◆ Option T: Timing—View GDDR Script Statistics .................................................... 150◆ Option A: Actions—Perform GDDR Actions .......................................................... 152◆ Option O: OPS—Access CA-OPS/MVS ................................................................... 158◆ Using OPSVIEW facilities for EMC GDDR administration................................... 159

Using EMC GDDROnline Facilities

Using EMC GDDR Online Facilities 79

Using EMC GDDR Online Facilities

Primary Options MenuEMC GDDR online facilities permit z/OS system programmers to perform configuration and administration tasks and operators to perform operator functions. To use the EMC GDDR online facilities interface, invoke the GDDR invocation REXX exec which was customized in “Step 1: Customize the GDDR invocation REXX exec” on page 71.

The following panel appears:

Figure 5 Primary Options Menu

Control fieldsAt the right side of the panel, the GDDR Primary Options menu displays the current settings for several EMC GDDR control values.

Note: The fields described below also appear on a number of other EMC GDDR panels.

This SystemSpecifies the current system.

This SiteSpecifies the current site.

Master-CShows the name of the C-System that currently owns the EMC GDDR master function. In environments supported by cross-site host-DASD channels, the master C-System is located at the opposite site from the business applications. Where cross-site host-DASD channels are not available, the master C-System will be the C-System at the site where the business applications are hosted.Thus, if the business applications are running at site DC1, the master C-System will be the C-System at site DC1.

Most EMC GDDR actions are allowed only when logged onto the master C-System.

Primary SiteIndicates the site where the business applications are currently running.

GDDRPRIM ---------------- GDDR - Primary Options Menu ------------------------- Option ===> P rofile Update Personal GDDR ISPF Profile This System: SYS1 M aintenance GDDR Setup and Maintenance This Site: DC1 G DDR Config View GDDR Configuration Master-C: SYS1 R oles Manage Site Roles Primary Site: DC1 C heckup Perform Pre-script Checkup Primary DASD: DC1 S cripts Run GDDR Scripts T iming View GDDR Script Statistics Automation: ON A ctions Perform GDDR Actions Planned script: None O OPS Access CA-OPS/MVS Unplanned script: None EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to Terminate GDDR ISPF



Primary DASDIndicates the site at which the R1 DASD currently reside. Generally, the sites indicated by Primary Site and Primary DASD should be the same.

Automation Indicates the current availability of EMC GDDR automation functionality. You can change the automation state by typing GDDR ON or GDDR OFF in the Option line of the Primary Options Menu. The displayed value of the automation setting on the right of the panel reflects the change immediately.

Note: The GDDR ON/OFF command is valid only on the master C-System.

◆ When you specify GDDR OFF to turn EMC GDDR automation off, the EMC GDDR Event Monitor does not respond to events that would normally indicate a storage or system failure. Therefore, the OFF automation status should be used only when system availability may be impacted by scheduled maintenance activities.

After you enter GDDR OFF, messages similar to the following appear:

GDDR373I GDDR Broadcasting new value for AUTOMATION.FLAGGDDR739I GDDR -> Set GDDR Broadcasting new value for AUTOMATION.FLAG at SYS1GDDR739I GDDR -> Set GDDR Broadcasting new value for AUTOMATION.FLAG at SYS3

◆ When you specify GDDR ON to turn EMC GDDR automation on, EMC GDDR operators will be able to run both Planned and Unplanned scripts.

Planned ScriptIndicates which Planned script, if any, is currently in progress. A Planned script is considered to be in progress if it has been started but has not yet completed successfully; in this case, it is eligible for restart. If no Planned script is currently in progress, ‘None’ displays in this field.

Unplanned ScriptIndicates which Unplanned script, if any, is currently in progress. An Unplanned script is considered to be in progress if it has been started but has not yet completed successfully; in this case, it is eligible for restart. If no Unplanned script is currently in progress, ‘None’ displays in this field.

OptionsAt the left side of the panel, a series of options are listed. To invoke one of the following actions, enter the appropriate option on the command line and press Enter. These options are described in the following sections.

◆ “Option P: Profile—Update Personal GDDR ISPF Profile” on page 82

◆ “Option M: Maintenance—GDDR Setup and Maintenance” on page 84

◆ “Option G: GDDR Config—View GDDR Configuration” on page 141

◆ “Option R: Roles—Manage Site Roles” on page 142

◆ “Option C: Checkup—Perform Pre-script Checkup” on page 143

◆ “Option S: Scripts—Run GDDR Scripts” on page 148

◆ “Option T: Timing—View GDDR Script Statistics” on page 150

◆ “Option A: Actions—Perform GDDR Actions” on page 152

◆ “Option O: OPS—Access CA-OPS/MVS” on page 158

Primary Options Menu 81


Option P: Profile—Update Personal GDDR ISPF ProfileSpecify option P in the GDDR Primary Options menu (Figure 5 on page 80) to access the EMC GDDR ISPF profiles. The following panel appears:

Figure 6 Change GDDR ISPF Profile Variable Values panel

Use this panel to specify GDDR-related variables pertaining to your Userid.

Note: The GDDR Subsystem Name field is not enabled for editing in GDDR Version 3.1.

1. Specify the JCL dataset.

Type the name of the PROCLIB dataset holding the GDDRPROC customized during the GDDR integration procedure “Customize member GDDRPROC” on page 62.

2. Specify the ISPF skeleton dataset.

Type the name of a dataset containing the GDDR file tailoring skeletons created when you downloaded the install cartridge. This dataset is used to retrieve ISPF file tailoring skeletons for the parameter activation, when done in background mode and when scripts are submitted.

3. Specify the global variable backup.

Type the name of the parameter backup dataset to be used for parameter management functions, defined during the EMC GDDR integration procedure “Allocate the parameter backup dataset and your parameter wizard work dataset” on page 62.

Note: Whenever a dataset name is required, you must specify a fully-qualified dataset name. TSO prefixing does not apply to any dataset name specified within EMC GDDR.

4. Specify the Host Component prefix.

This is the prefix that will be used for internal SRDF Host Component API commands. The default value set by EMC GDDR is null, and must be replaced by a valid prefix during EMC GDDR customization.

-------------- GDDR - Change GDDR ISPF Profile Variable Values ---------------- Command ===> GDDR Subsystem Name ===> GDDR JCL dataset ===> ISPF skeleton dataset ===> Global variable backup ===> Host Component prefix ===> Default SCF suffix ===> Jobcards for your user: // // // // Press <F3> when ready Enter CANCEL to return without changing any profile variable values Enter CLEAR to set all values to null and exit Enter RESET to restore the values as they were upon entry



5. Specify the default SCF suffix.

This is the suffix appended to 'SCF$' to form the DDname on a DD statement in script jobs, the GDDRMAIN, Heartbeat monitor, z/OS Console Monitor, and CA OPS/MVS started tasks, associating these with an SCF subsystem. The default value set by EMC GDDR is "EMC" which is suitable only if you want EMC GDDR to connect to an SCF instance which either does not specify an SCF subsystem ID, or also specifies "EMC".

6. Enter jobcard information.

This field is displayed conditionally for EMC GDDR users who are authorized to activate parameter changes and to manage GDDR scripts. The jobcard information entered here applies only to the current user and is used for parameter activate and script submission tasks. For example:

===>//JOBNAME JOB (acct-number),gddr-job,CLASS=A,===>// MSGCLASS=A,USER=GDDR,NOTIFY=GDDR===>/*JOBPARM LINES=999999===>//*

7. Press F3 to save the values and return to the Primary Options Menu.

Option P: Profile—Update Personal GDDR ISPF Profile 83


Option M: Maintenance—GDDR Setup and MaintenanceSpecify option M on the GDDR Primary Options menu (Figure 5 on page 80) to access the EMC GDDR setup and maintenance functions. The following panel appears:

Figure 7 Setup and Maintenance Menu

The following sections describe the Setup and Maintenance Menu options:

◆ “Option P: Manage GDDR Parameters” on page 85

◆ “Option D: Message, Debug and Trace Options” on page 135

◆ “Option Q: Manage GDDR Internal Command Queue” on page 136

◆ “Option H: Perform HMC Discovery” on page 136

◆ “Option R: Refresh GDDR Message Table” on page 137

◆ “Option S: Manage GDDR System Variables” on page 138

---------------------- GDDR - Setup and Maintenance Menu ----------------------- Option ===> P arms Manage GDDR Parameters This System: SYS1 D ebug Message, Debug and Trace Options This Site: DC1 Q ueue Manage GDDR Internal Command Queue Master-C: SYS1 H MC Perform HMC Discovery Primary Site: DC1 R efresh Refresh GDDR Message Table Primary DASD: DC1 S ystem Manage GDDR System Variables Automation: ON Planned script: None Unplanned script: None EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Primary Options Menu



Option P: Manage GDDR Parameters

Specify option P in the Setup and Maintenance Menu (Figure 7 on page 84) to access the GDDR parameter management functions. The following panel appears:

Figure 8 Parameter Management Options Menu

Note: The options initially displayed in this panel may vary. The panel does not show options C,D,H,O,V,A until the actions described in "“To prepare to edit the current GDDR parameter set:” on page 90 are completed.

The menu options allow you to manage GDDR parameter backups and to perform various parameter definition functions.

Using the Parameter Load function panelsThe series of Parameter Load function panels enable you to display or define parameter values organized by object category. The panels are serialized using function keys as follows so that fields are presented in data dependency order:

◆ F5 returns you to the immediate preceding panel in the series.

◆ F6 takes you to the next panel in the series.

◆ F3 returns you to the menu panel for objects of the same type.

Each Parameter Load display and definition panel does the following:

◆ Displays values for named parameters from the selected parameter dataset member.

◆ Displays values which were saved at a previous Parameter Load panel.

If no value is supplied for a field by the selected parameter dataset member, the first time a value for that field is specified as panel input and saved to the Work dataset, the value is propagated to all succeeding panels which contain the same field.

Changes to field values in parameter display and definition panels are saved to your Work dataset when you type SAVE on the Command line of the panel. If after editing the values in the panel you wish to restore the original values displayed in the panel, type LOAD in the panel. If you have 'Saved' interim changes for values on the current panel, then the Load command restores the last saved values.

------------------- GDDR - Parameter Management Options Menu ------------------ Option ===> B ackup Manage GDDR Parameter backups This System: SYS2 This Site: DC1 .---------- Parameter Load functions ----------. Master-C: SYS2 | I nput Select Parameter Input Dataset | Primary Site: DC1 | C onfig Define Configuration basics | Primary DASD: DC1 | D ASD Define Storage objects | | H ost Define Host objects | Automation: ON | O ptions Specify GDDR Options | Planned script: None | V alidate Validate GDDR Parameter Set | Unplanned script: None | A ctivate Activate GDDR Parameter Set | |______________________________________________| EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Setup and Maintenance Menu

Option M: Maintenance—GDDR Setup and Maintenance 85


Note: Each panel in which you use the SAVE command will be utilized for a partial parameter activation, whether or not you performed changes on the panel.

The following sections describe the Parameter Management Menu functions:

◆ “Option B: Manage GDDR Parameter Backups” on page 88

◆ “Option I: Select Parameter Input Dataset” on page 91

◆ “Option C: Define Configuration Basics” on page 95

◆ “Option D: Define Storage Objects” on page 101

◆ “Option H: Define Host Objects” on page 106

◆ “Option O: Specify GDDR Options” on page 121

◆ “Option V: Validate GDDR Parameter Set” on page 131

◆ “Option A: Activate GDDR Parameter Set” on page 132

Using the EMC GDDR parameter review functionsEMC GDDR makes the current parameters available for review through the GDDR - Parameter Management Options Menu, without the Validate and Activate capabilities. For example, an audit of your disaster restart operations may include a review of GDDR parameters.The EMC GDDR parameters review capability enables a third-party reviewer to access a current parameter backup with no exposure from unwanted changes to the active parameter values.

Authority to use the GDDR parameters review capability is granted to members of the GDDR$REV RACF group with READ access to the GDDRISPF.ACCESS, GDDRISPF.SETUP.ACCESS, and the GDDRISPF.SETUP.PARMS.REVIEW facility profiles, as described in Table 8 on page 56. When authority has been granted, the GDDR Parameter Management Options Menu is displayed without the Validate and Activate Parameter Load functions as shown in Figure 10 on page 87.

The parameter review is performed by making a backup of the current parameters, using “Option B: Manage GDDR Parameter Backups” on page 88. The reviewer selects the backup member to be used to prepare the reviewer's parameter work dataset as shown in Figure 9 and described in detail in “Option I: Select Parameter Input Dataset” on page 91.

Figure 9 Select Parameter input dataset for parameter review

-------------------- GDDR - Select Parameter Input Dataset --- Row 1 to 6 of 12 Command ===> review Parameter input dataset ===> HLQ.GDDR310.BACKUP.PARMS Selected Member ===> I5LG1613 Unselect? ===> N (Y/N) Parameter Load work-dataset ===> HLQ.REVIEW.PARMS.WORK Parameter Load description ===> 09/09/30 DR Ops Review Last used GDDR Parameter Source and description: HLQ.GDDR310.BACKUP.PARMS(I5PG4124) on SYS1 Parameter Change @090926 (User RGHIJK1 09/09/26 14:30) Ready to start preparation of the work dataset. Press <F3> to proceed. Press <F3> to return to the Parameter Management Options Menu Line commands: S elect, U nselect, B rowse, E dit ----------------------- Parameter Input Member Selection ---------------------- Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ I5LG6613 09/09/30 16:16 RGHIJK1 Backup for DR Ops Review _ I5PG4125 09/09/26 14:30 RGHIJK1 A:Change control @090926 _ I5PG4124 09/09/26 14:30 RGHIJK1 B:Change control @090926 _ I5PE3024 09/08/22 16:19 PQRSTU1 A:Change control @090822 _ I5LG1928 09/08/22 16:19 PQRSTU1 B:Change control @090822 _ I5LG1852 09/07/25 16:16 OPQRST1 A:Change control @090725



Within the Select Parameter Input Dataset panel, after you select a backup member which will be used to populate your parameter work dataset, the following message appears:

Ready to start preparation of the work dataset. Press <F3> to proceed.

To display the reviewer's version of the GDDR - Parameter Management Options Menu, type review in the Command field of the Select Parameter Input Dataset panel, rather than pressing <F3> to proceed, as the message directs.

The reviewer's version of the Parameter Management Options Menu is displayed as shown in Figure 10.

Figure 10 Reviewer's version of the Parameter Management Options Menu

The Parameter load functions listed in the reviewer's version of the Parameter Management Options Menu display the parameter values of the current backup member. The parameters are described in the sections below.

◆ “Option C: Define Configuration Basics” on page 95

◆ “Option D: Define Storage Objects” on page 101

◆ “Option H: Define Host Objects” on page 106

◆ “Option O: Specify GDDR Options” on page 121

------------------- GDDR - Parameter Management Options Menu ------------------ Option ===> B ackup Manage GDDR Parameter backups This System: SYS3 This Site: DC2 .---------- Parameter Load functions ----------. Master-C: SYS3 | I nput Select Parameter Input Dataset | Primary Site: DC1 | C onfig Define Configuration basics | Primary DASD: DC1 | D ASD Define Storage objects | | H ost Define Host objects | Automation: ON | O ptions Specify GDDR Options | Planned script: None | | Unplanned script: None | | |______________________________________________| EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Setup and Maintenance Menu



Option B: Manage GDDR Parameter BackupsEMC GDDR automatically creates GDDR parameter backups before and after parameters are activated and during Heartbeat Monitor initialization. However, there may be other times when it is necessary to back up the EMC GDDR parameters. For example, you can create a backup to be used as input to your next parameter definition. The Manage GDDR Parameter Backups option allows you to do this.

When you specify option B in the Parameter Management Options Menu shown in Figure 8 on page 85, the following panel appears:

Figure 11 Manage GDDR Parameter Backups panel

The following fields are provided on the Manage GDDR Parameter Backups panel:

◆ Backup Dataset

The backup dataset name can be one of the following:

• The GDDR Variable backup dataset name specified in your GDDR ISPF Profile Variable Values panel shown in Figure 6 on page 82.

• The dataset name associated with the BKUPVARS dataset type in the Define GDDR Datasets panel shown in Figure 21 on page 99.

• Any PDS or PDSE dataset name you type in this field.

◆ Backup description

Use this field to describe the circumstances regarding the backup. When the member is created as a result of an Activate process, the description is prefixed with either b: or a:, indicating that the backup was taken before or after the activation processing started.

◆ Backup consistency

Use this field to enforce the consistency of the parameter set being backed up. EMC GDDR global variable backup consistency is enforced by dynamic creation of an authorization rule which protects global variables from updates in the time between the start and the completion of the backup.

------------------- GDDR - Manage GDDR Parameter Backups ---- Row 1 to 9 of 11 Command ===> B Backup Create new GDDR Parameter Backup Backup Dataset ===> JABCDE1.GDDR310.BACKUP.PARMS Backup description ===> __________________________________________ Backup consistency ===> Y (Y/N/1-9) Press <F3> to return to the GDDR Parameter Management Options Menu Line commands: B rowse, E dit, D elete, M odify description S elect for Parameter Load ------------------------------- Previous Backups ------------------------------ Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ I5PE3025 09/05/25 14:30 PQRSTU1 A:testing _ I5PE3024 09/05/25 14:30 PQRSTU1 B:testing _ I5LG1928 09/05/21 16:19 OPQRST1 B:ptw test _ I5LG1852 09/05/21 16:18 OPQRST1 B:ptw test _ I5LG1613 09/05/21 16:16 OPQRST1 B:ptw test _ I5LG1152 09/05/21 16:11 OPQRST1 B:ptw test _ I5LG0448 09/05/21 16:04 OPQRST1 B:ptw test _ I5JF4346 09/05/19 15:43 RGHIJK1 ******************************* Bottom of data ********************************



If your site prevents application manipulation of authorization rules, specify N to bypass the EMC GDDR backup consistency control, and manually quiesce EMC GDDR activity to prevent global variable changes during backup processing. Otherwise, specify Y to enable EMC GDDR backup consistency control, or 1 - 9 to indicate the number of retries to protect global variables before backup processing begins.

◆ Previous Backups

Parameter backup dataset members are used as input by the parameter definition process, and new members are created during Activate to capture a "Before" and "After" image of the existing parameters. In the example shown in Figure 11, there is a list of dataset members that had been created by previous parameter activations, where "B" indicates Before and "A" indicates After.

◆ Member

For either automatic or requested backups, the member name is generated automatically in the format Annnnnnn where Annnnnnn is an alphanumeric string which is generated by the EMC GDDR parameter backup processor. It encodes the time of the backup (including year, month, day, hour, minute, and second).

◆ Line commands

Line commands enable the following actions in the Action (Act) column in the Previous Backups member list:

• B Browse

Enter the ISPF browse mode for the dataset and member.

• D Delete

Delete the dataset member.

• E Edit

Enter ISPF edit mode for the dataset and member.

• M Modify the member description

Edit the parameter backup member description.

• S Select for Parameter Load

Select a member. The selected member is displayed in the Selected Member field of the Select Parameter Input Dataset shown in Figure 13 on page 91.

Using the parameter backup featureBackups of all parameters are automatically taken during Heartbeat Monitor initialization and as part of EMC GDDR parameter set Activation. A parameter backup is also taken when you specifically request a backup using option B on the EMC GDDR Parameter Management Options menu.

For the automatic backups, the dataset to which the backup is written is obtained from the Dataset Name field of the Define GDDR Datasets panel, dataset type of BKUPVARS. See Figure 21, “Define GDDR Datasets panel,” on page 99. For requested backups, the dataset name of dataset type BKUPVARS is presented as a default, but another backup dataset may be specified.



To create a new GDDR parameter backup:1. Specify option B Backup on the Parameter Management Options Menu (Figure 8

on page 85).

If the Global variable backup dataset name specified in your GDDR ISPF Profile variable values differs from the dataset associated with BKUPVARS in the Define GDDR Datasets panel shown in Figure 21 on page 99, then the Select Dataset for GDDR Parameter Backup panel shown in Figure 12 initially displays. This panel presents you with both datasets so you may choose the one to use for parameter backup:

Figure 12 Select Dataset for GDDR Parameter Backup

2. Select a dataset name and press Enter to proceed to the Manage GDDR Parameter Backups panel shown in Figure 11 on page 88.

3. Specify a dataset name in the Backup Dataset field.

4. Type B (Backup) in the command line in the Manage GDDR Parameter Backups panel and press Enter.

When the parameter backup processing completes, the following messages display:

To prepare to edit the current GDDR parameter set:The Manage GDDR Parameter Backups panel also lets you prepare to edit the current (most recent) GDDR parameter set. You do this when you select an existing member of the parameter backup dataset which is displayed.

1. Type S (Select) next to the desired member in the Previous Backups list displayed in the Manage GDDR Parameter Backups panel shown in Figure 11 on page 88 and press Enter.

2. The Select Parameter Input Dataset panel displays. Specify the panel options as described in “Option I: Select Parameter Input Dataset”.

------------- GDDR - Select Dataset for GDDR Parameter Backup ------------------ Command ===> Select a dataset name by entering < S > in the appropriate row _ From User Profile ===> JABCDE1.GDDR310.BACKUP.PARMS _ From GDDR Parameters ===> EMC.GDDR310.BACKUP.PARMS.SYS2 Press <Enter> to proceed to the Manage GDDR Parameter Backups panel Press <F3> to return to the GDDR Parameter Management Options Menu

GDDR721I GDDR Starting GDDR Global Variable Backup GDDP304I Backup successful, 503 lines written to PARMOUT GDDR639I GDDR Completed GDDR Global Variable Backup with rc 0 ***



Option I: Select Parameter Input DatasetWhen you specify option I in the Parameter Management Options Menu shown in Figure 8 on page 85, the following panel appears.

Figure 13 Select Parameter Input Dataset panel

The following fields are provided on the Select Parameter Input Dataset panel:

◆ Parameter Input Dataset

Specify the parameter backup dataset name. It can be one of the following:

• The Global Variable backup dataset name specified in your GDDR ISPF Profile Variable Values panel shown in Figure 6 on page 82.

• The dataset name associated with the BKUPVARS dataset type in the Define GDDR Datasets panel shown in Figure 21 on page 99.

• Any PDS or PDSE dataset name you type in this field.

◆ Selected Member (display only)

Indicates the currently selected backup member.

◆ Parameter Load Work-dataset

Enter the parameter load work dataset that was defined in “Allocate the parameter backup dataset and your parameter wizard work dataset” on page 62. This dataset contains your in-process work, enabling you to assemble a complete parameter set by saving your input data from each of the parameter definition panels, and returning to the task at a later time.

Note: The parameter input dataset and the parameter load work dataset must be two different datasets. This is because the contents of the parameter load work dataset are overwritten when exiting the Select Parameter Input Dataset panel.

◆ Parameter Load Description

Use this field to describe the circumstances regarding the parameter load or update. When the parameter backup member is created as a result of an Activate process, the description is prefixed with either b: or a:, indicating that the backup was taken before or after the activation processing started.

-------------------- GDDR - Select Parameter Input Dataset --- Row 1 to 4 of 4 Command ===> Parameter input dataset ===> HLQ.GDDR310.BACKUP.PARMS Selected Member ===> ________ Unselect? ===> N (Y/N) Parameter Load work-dataset ===> HLQ.GDDR310.PARMS.WORK Parameter Load description ===> Change control @090926 Last used GDDR Parameter Source and description: HLQ.GDDR310.BACKUP.PARMS(I5LG1852) on SYS1 A: Change control @090725 (User PQRSTU1 09/07/25 16:16) Press <F3> to return to the Parameter Management Options Menu Line commands: S elect, U nselect, B rowse, E dit ----------------------- Parameter Input Member Selection ---------------------- Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ I5PE3024 09/08/22 16:19 PQRSTU1 A: Change control @090822 _ I5LG1928 09/08/22 16:19 PQRSTU1 B: Change control @090822 _ I5LG1852 09/07/25 16:16 OPQRST1 A: Change control @090725 _ I5LG1613 09/07/25 16:16 OPQRST1 B: Change control @090725



◆ Last Used GDDR Parameter source and description

Indicates which work dataset or parameter backup dataset was used for the last Activate.

◆ Parameter Input Member Selection

Displays the current parameter members.

◆ Line commands

Line commands enable the following actions in the Action (Act) column in the Parameter Input Member Selection list:

• S Select Specify the Select command to display the Select Parameter Input Dataset panel for the dataset and member.

• U Unselect Specify the Unselect command to remove the member.

• B Browse Specify the Browse command to enter the ISPF browse mode for the member.

• E Edit Specify the Edit command to enter ISPF edit mode for the member.

Note: The parameter backup member information shown in the Select Parameter Input Dataset panel is maintained in GDDR variables for all parameter backups created by GDDR— either as an impromptu user backup, as a backup created before and after a parameter set activation, or as a backup created by the Heartbeat Monitor during initialization. These actions are referred to as registered backups.

Unregistered or outside parameter backup members may be copied into your backup dataset containing registered parameter backups to facilitate configuration of additional EMC GDDR complexes or reconfiguration of existing GDDR-managed environments. Unregistered parameter backup members are displayed when you enter the 'showall' command on the command line of the Select Parameter Input Dataset panel. The showall command updates the Parameter Input Member Selection list with members which you have previously copied to your specified parameter input dataset.



To edit the current GDDR parameter set:1. In the Select Parameter Input Dataset panel, press F3 to edit your GDDR

parameter set by copying the contents of the selected parameter backup member to your parameter work dataset.

This operation overwrites the contents of your parameter work dataset.

A confirmation panel similar to the following requests you to confirm the operation:

Figure 14 Prepare Work Dataset for Parameter Load confirmation panel

2. Enter CONTINUE to proceed and overwrite the contents of the work dataset with the selected member of the parameter input dataset.

A panel similar to the following displays the status of the operation:

Figure 15 Prepare Work Dataset status panel

-------------------- GDDR - Select Parameter Input Dataset -- Row 1 to 5 of 5 C +-----------------------------------------------------------------------+ | ---------- GDDR - Prepare Work Dataset for Parameter Load ---------- | | Command ===> | | | P | Warning: The contents of the work dataset will be erased. | | Selected Dataset : JABCDE1.GDDR310.PARMS.WORK | | | | Enter one of the following commands: | | <CONTINUE> to proceed and erase all members in work dataset. | | <CANCEL> to return to the Parameter Management Options Menu | | | R | | P | | L +-----------------------------------------------------------------------+ ----------------------- Parameter Input Member Selection ---------------------- Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ --NONE-- 09/06/02 09:07 JABCDE1 GDDR parameter load from scratch _ I5PE2318 09/05/25 14:23 PQRSTU1 SYS1: Still 2-Site SRDF/A _ I5CG2419 09/05/12 16:24 PQRSTU1 SYS1: 2-Site SRDF/A _ I5B41951 09/05/11 04:19 PQRSTU1 GDDR BU 01 _ I59B2428 09/05/09 11:24 PQRSTU1 SYS1: 2-Site SRDF/A ******************************* Bottom of data ********************************

------- ------------ GDDR - Select Parameter Input Dataset -- Row 1 to 5 of 5 C +-------------------------------------------------------------+ | --------- GDDR - Prepare Work Dataset - Status ------------ | | | | Validating Input variables: | (Y/N) P | ===> TEMPVAR | | ===> TIMEFINDER | | ===> USEROPT | | ===> UTILITY | | | | *** PLEASE WAIT *** | | | R | | eed. P | | L +-------------------------------------------------------------+ ----------------------- Parameter Input Member Selection ---------------------- Act Member Date Time Userid Description --- -------- -------- ----- -------- ------------------------------------------ _ --NONE-- 09/06/02 09:07 JABCDE1 GDDR parameter load from scratch _ I5PE2318 09/05/25 14:23 PQRSTU1 SYS1: Still 2-Site SRDF/A _ I5CG2419 09/05/12 16:24 PQRSTU1 SYS1: 2-Site SRDF/A _ I5B41951 09/05/11 04:19 PQRSTU1 GDDR BU 01 _ I59B2428 09/05/09 11:24 PQRSTU1 SYS1: 2-Site SRDF/A ******************************* Bottom of data ********************************



Following completion of the Prepare Work Dataset process, message GDDI172I confirms that your work dataset has been populated with the parameter dataset member you selected using Option I, Select Parameter Input dataset, as shown in Figure 13 on page 91.

The Parameter Management Options Menu redisplays:

Figure 16 Parameter Management Options Menu with parameter load input selection

To review the current GDDR parameter set:◆ Select any of the Parameter Load functions to view or change values which were

populated from the selected input parameter dataset member.

------------------- GDDR - Parameter Management Options Menu ------------------ B ackup Manage GDDR Parameter backups This System: SYS1 This Site: DC1 .---------- Parameter Load functions ----------. Master-C: SYS1 | I nput Select Parameter Input Dataset | Primary Site: DC1 | C onfig Define Configuration basics | Primary DASD: DC1 | D ASD Define Storage objects | | H ost Define Host objects | Automation: ON | O ptions Specify GDDR Options | Planned script: None | V alidate Validate GDDR Parameter Set | Unplanned script: None | A ctivate Activate GDDR Parameter Set | |______________________________________________| EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Pres +----------------------------------------------------------------+ | GDDI172I Member I6L13905 selected as GDDR Parameter Load Input | +----------------------------------------------------------------+ Option ===>



Option C: Define Configuration Basics

IMPORTANT!This series of Define Configuration Basics panels is used once during initial installation of EMC GDDR, and is unlikely to be used again. Most changes performed here will require a FULL parameter activation. The following changes can be done with a PARTIAL parameter activation:

- Option F: setting FBA Devices toY/N- Option D: changing dataset names

When you specify option C in the Parameter Management Options Menu shown in Figure 8 on page 85, the Define Configuration Basics panel appears:

Figure 17 Define Configuration Basics panel

Complete the following options listed in this panel to define your configuration:

◆ “Option F: Define Configuration Features” on page 96

◆ “Option C: Define C-Systems” on page 97

◆ “Option D: Define GDDR Datasets” on page 99

◆ “Option R: Define Site Roles and Groups” on page 100

IMPORTANT!As you complete each option panel, save your input to ensure that you can return to the task with no loss of data. If you attempt to exit a panel before a save has been completed, you are reminded with the following message:

You may have unsaved changes. Enter SAVE to save your work before exiting. Any other response will continue with your requested action.

------------------------- GDDR - Define Configuration Basics ------------------------- Option ===> F Define Configuration Features This System: SYS1 C Define C-Systems This Site: DC1 D Define GDDR Datasets Master-C: SYS1 R Define Site Roles and Groups Primary Site: DC1 Primary DASD: DC1 Automation: ON Planned script: None Unplanned script: None

Select an option and press <Enter> <F5> Parameter Management Options Menu <F6> Define Configuration Features Press <F3> to return to the GDDR Parameter Management Options Menu



Option F: Define Configuration FeaturesWhen you specify option F in the Define Configuration Basics panel, the following panel appears:

Figure 18 Define Configuration Features panel 1

The Site list field is populated from the parameter member GDDRSYNC or from the parameter backup you selected in the Select Parameter Input Dataset panel shown in Figure 13 on page 91. Ensure that the Site list field reflects correctly named sites for your EMC GDDR configuration, or make needed changes now. Valid values are DC1 and DC2.

An EMC GDDR site is a physical location, housing CPU or DASD or both, where:

◆ DC1 is part of all supported EMC GDDR configurations

◆ DC2 is a site connected to DC1 with SRDF/S

1. Press Enter to validate the site list.

The Define GDDR Configuration Features panel redisplays. It now contains Site Pair, Features, and Accepted Values fields populated with features from the sample parameters or the previous parameter backup, further modified based on the earlier site selection.

Figure 19 Define GDDR Configuration Features panel 2

2. If you changed any of the listed features, type Save on the command line and press Enter.

3. Press F6 to proceed to the Define C-Systems panel shown in Figure 20.

------------------- GDDR - Define GDDR Configuration Features ------------------- Option ===> Site list: DC 1 , DC 2 , DC _ , DC _ FBA Devices: N (Y/N) Fill in the required information. Press <Enter> to Validate. Press <F3> to return to the GDDR Define Configuration Basics Menu

------------- GDDR - Define GDDR Configuration features - 2-Sites -------------Command ===> Site list: DC1 DC2 FBA Devices: Y Press <F3> to return to the GDDR Define Configuration Basics Menu <F5> Define Configuration Basics Menu <F6> Define C-Systems Type <SAVE> to save, <LOAD> to restart from last saved values. To change a feature, overtype it with the new value. Site Pair Features Accepted Values ------ ------------ -------------------------------------- DC1-DC2 SRDF/S CONGROUP AUTOSWAP,CONGROUP



Option C: Define C-SystemsWhen you specify option C in the Define Configuration Basics panel shown in Figure 17 on page 95, the following panel appears:

Figure 20 Define C-Systems panel

1. Complete the required information in the System Name, MSFID, IPL parameters, Central Processor Complex (CPC) name, and LPAR fields.

• Site

Indicates the ID of the site location being specified. Site values are populated from the Site List in the Define GDDR Configuration Features panel. Valid values are DC1 or DC2. This field is not editable.

• System

The MVS system name of an EMC GDDR C-System which is specified using the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or equivalent parameter file.

• MSFID

The MSF ID of the CA-OPS/MVS copy at the C-System identified by System name.

• IPL Parameters

Specifies the IPL parameters that EMC GDDR may use to IPL the C-Systems at sites DC1 and DC2 in the following format:

ssss,iiiixxmn

Where

– ssss is the Sysres device address– iiii is the IODF device address– xx is the LOADxx member suffix– m is the IMSI Field– n is the IEANUC0n suffixYou can locate IPL parameters using the D IPLINFO MVS console command, as shown in the following sample output:

--------------------------- GDDR - Define C-Systems --------------------------- Option ===> Press <F3> to return to the GDDR Define Configuration Basics Menu <F5> Define Configuration Features <F6> Define GDDR Datasets Type <SAVE> to save, <LOAD> to restart from last saved values. System IPL Site Name MSFID Parameters CPC LPAR ---- -------- -------- --------------- -------- -------- DC1 T104 T104 7010 , 701099M1 C ZOSEC16 DC2 T103 T103 710A , 710A99M1 O ZOSEO01B



RESPONSE=SYSBIEE254I 21.14.59 IPLINFO DISPLAY 860SYSTEM IPLED AT 15.59.20 ON 02/02/2009RELEASE z/OS 01.10.00 LICENSE = z/OSeUSED LOAD02 IN SYS1.IPLPARM ON 0A26ARCHLVL = 2 MTLSHARE = NIEASYM LIST = B0IEASYS LIST = B0 (OP)IODF DEVICE 0A26IPL DEVICE 0A1D VOLUME RESB14

• CPC (Central Processor Complex)

Specify the name of the central processor where the C-System LPAR is defined.

• LPAR (Logical Partition)

Specify the name of the LPAR within which this system runs at the specified site.You can find the CPC and LPAR names using the D M=CPU MVS console command, as shown in the following sample output:

RESPONSE=SYSB IEE174I 20.59.34 DISPLAY M 781 PROCESSOR STATUS ID CPU SERIAL 0 02F94E2096 1 02F94E2096 2 02F94E2096 CPC ND = 002096.S07.IBM.83.00000008F94E CPC SI = 2096.N03.IBM.83.000000000008F94E CPC ID = 00 CPC NAME = C LP NAME = ZOSESYSB LP ID = 2 CSS ID = 0 MIF ID = 2 ONLINE - OFFLINE . DOES NOT EXIST W WLM-MANAGED N NOT AVAILABLE CPC ND CENTRAL PROCESSING COMPLEX NODE DESCRIPTOR CPC SI SYSTEM INFORMATION FROM STSI INSTRUCTION CPC ID CENTRAL PROCESSING COMPLEX IDENTIFIER CPC NAME CENTRAL PROCESSING COMPLEX NAME LP NAME LOGICAL PARTITION NAME

2. If you changed any values, type Save on the command line and press Enter.

3. Press F6 to proceed to the Define GDDR Datasets panel shown in Figure 21.



Option D: Define GDDR DatasetsWhen you specify option D in the Define Configuration Basics panel shown in Figure 17 on page 95, the following panel appears:

Figure 21 Define GDDR Datasets panel

1. Type Add in the Option field at the top of the panel to display a new line for entry of values.

2. Insert additional datasets by typing R (Repeat) in the command field to the left of an existing entry and overtyping the existing data.

3. Type D (Delete) in the command field to the left of an existing entry to remove it.

4. Complete the required information for each dataset type.

• BKUPVARS

Specify the name of the dataset into which the backups produced by EMC GDDR Heartbeat monitor initialization should be saved. This dataset was allocated during the procedure described in “Allocate the parameter backup dataset and your parameter wizard work dataset” on page 62.

• PROCLIB

Specify the name of the library on the C-Systems which contains the EMC GDDRPROC member. This library was selected during the procedure described in “Customize member GDDRPROC” on page 62.

• SKELETON

Specify the name of the GDDR ISPSLIB library that resulted from your SMP/E installation.

• Seq

Specify a sequence number for the dataset. The sequence number enables the Proclib and Skeleton libraries to be assigned sequentially across C-Systems.

5. If you made any changes, type Save on the command line and press Enter.

6. Press F6 to proceed to the Define Site Roles and Groups panel shown in Figure 22 on page 100.

------------------------ GDDR - Define GDDR Datasets ------------- Row 1 of 6 Option ===> Press <F3> to return to the GDDR Define Configuration Basics Menu <F5> Define C-systems <F6> Define Site Roles and Groups Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD C-system DS Type Seq Dataset Name --- -------- -------- --- -------------------------------------------- _ T103 BKUPVARS EMC.GDDR310.BKUPVARS.CNTL _ T104 BKUPVARS EMC.GDDR310.BKUPVARS.CNTL _ T103 PROCLIB 1 EMC.GDDR310.PROCLIB _ T104 PROCLIB 2 EMC.GDDR310.PROCLIB _ T103 SKELETON 1 EMC.GDDR310.ISPSLIB _ T104 SKELETON 2 EMC.GDDR310.ISPSLIB ******************************* Bottom of data ******************** ************



Option R: Define Site Roles and GroupsWhen you specify option R in the Define Configuration Basics panel shown in Figure 17 on page 95, the Define Site Roles and Groups panel appears.

Figure 22 Define Site Roles and Groups panel

The Define Site Roles and Groups panel defines your Consistency Group and MSC Group names as EMC GDDR global variables.

Note: In SRDF/S environments, MSC Group names are not used. This is indicated by the 'Not Applicable' note to the right of the MSC Group Name fields.

1. Complete the following fields in the panel:

• Primary DASD Site

Specify the site where the source (R1) DASD is located.

• Primary Site

Specify the site where the production workload is located.

• Consistency Group Name DC1

Specify the name of the managed consistency group when the Primary Site is DC1.

• Consistency Group Name DC2

Specify the name of the managed consistency group when the Primary Site is DC2.

Note: If the RESET option is specified during GDDR parameter activation, EMC GDDR will dynamically determine the correct Primary DASD site based on a discovery process of the managed configuration; this may override the value specified on this panel.


3. Press F6 to proceed to the Define Storage Objects panel shown in Figure 23.

--------------------- GDDR - Define Site Roles and Groups --------------------- Option ===> Press <F3> to return to the GDDR Define Configuration Basics Menu <F5> Define GDDR Datasets <F6> Define Storage Objects Type <SAVE> to save, <LOAD> to restart from last saved values. Enter the required information. Press <Enter> to Validate. Primary DASD Site: DC1 Select DC1 or DC2 Primary Site: DC1 Consistency Group Name DC1: ________ Consistency Group Name DC2: ________ MSC Group Name DC1: Not Applicable MSC Group Name DC2: MSC Group Name DC3: ******************************* Bottom of Data ******************************



Option D: Define Storage ObjectsWhen you specify option D in the Parameter Management Options Menu shown in Figure 8 on page 85, the Define Storage Objects panel appears:

Figure 23 Define Storage Objects panel

Complete the following options listed in this panel to define your configuration:

◆ “Option SR: Define SRDF Device Ranges” on page 101

◆ “Option GN: Define SRDF/S GNS Groups” on page 103

◆ “Option TF: Define TimeFinder Device Ranges” on page 104

◆ “Option SD: Define SDDF Gatekeepers” on page 105

Option SR: Define SRDF Device RangesWhen you specify option SR in the Define Storage Objects panel, the following panel appears:

Figure 24 Define SRDF Device Ranges panel

1. If the panel is not pre-populated with existing SRDF Device Range entries, type Add in the Command field at the top of the panel to display a new line for entry of SitePair and SRDF Device Range values.

2. Insert additional Site Pairs by typing R (Repeat) in the command field to the left of an existing SitePair.

----------------------- GDDR - Define Storage Objects ------------------------- Option ===> SR Define SRDF Device ranges This System: SYS1 GN Define SRDF/S GNS Groups This Site: DC1 TF Define TimeFinder Device ranges Master-C: SYS1 SD Define SDDF Gatekeepers Primary Site: DC1 Primary DASD: DC1 Automation: ON Planned script: None Unplanned script: None Select an option and press <Enter> <F5> Define Site Roles and Groups <F6> Define SRDF Device Ranges Press <F3> to return to the GDDR Parameter Management Options Menu

----------------------- GDDR - Define SRDF Device Ranges ----------------------Command ===> Press <F3> to return to the GDDR Define Storage objects Menu <F5> Define Storage Objects Menu <F6> Define SRDF/S GNS Groups Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD SitePair SRDF Device Range External --- ------- ----------------------------------- -------- _ DC1-DC2 gkd1,ra,dddd-eeee,ffff-gggg,ra,gkd2 NO _ DC2-DC1 gkd2,ra,dddd-eeee,ffff-gggg,ra,gkd1 NO ******************************* Bottom of data ********************************



3. Complete the fields as follows:

• SitePair

Specify the EMC GDDR SRDF replication pairs in the format:

DCm-DCn

Where m is the lower site number, and n is the higher site number. Valid pairings of DCm and DCn are DC1-DC2.

• SRDF Device Range

Specify contiguous Symmetrix device ranges which are common to the specified Site Pair in the format:

gkdm,ra,dddd-eeee,ffff-gggg,ra,gkdn

Where:

gkdm is aDCm SRDF gatekeeper

gkdn is a DCn SRDF gatekeeper

ra is an RA group spanning the specified site pair and to which the defined device ranges belong

dddd-eeee is a range of contiguous Symmetrix devices at site DCm

ffff-gggg is a range of contiguous Symmetrix devices at site DCn

Notes: 1. The 4-character gatekeeper masks, gkdm and gkdn, represent MVS volume addresses where the two left-most positions are used to uniquely identify the site DCm or DCn Symmetrix control unit where the volume [gatekeeper] resides. Therefore, the gatekeepers associated with the SRDF device ranges confer three pieces of information used in the processing of commands: the Site, the Symmetrix Control Unit at a Site, and the gatekeeper address. 2. The Symmetrix device number ranges at DCm and DCn must contain the same number of devices. 3. If a site is not configured with MVS systems, for example, DC2 in the diskless cascaded configuration, then dummy MVS addresses must be specified as gatekeeper devices for that site. This must be done so that the left-most two positions can be used to uniquely identify a Symmetrix storage unit at that site.

• External

The external device range flag does not apply to SRDF/S with ConGroup configurations.


5. Press F6 to proceed to the Define SRDF/S GNS Groups panel shown in Figure 25.



Option GN: Define SRDF/S GNS GroupsWhen you specify option GN in the Define Storage Objects panel shown in “Define Storage Objects panel” on page 101, the following panel appears:

Figure 25 Define SRDF/S GNS Groups

1. If the panel is not pre-populated with existing GNS group entries, type Add in the Command field at the top of the panel to display a new line for entry of Site, Symmetrix serial, RA group, and GNS group values.

2. Insert additional sites by entering R in the command field to the left of an existing entry and overtype the existing data.

3. Specify the following values:

• Site

Specify the site ID. This must match the primary DASD site for the GNS group name specified as the parameter value to be selected for use in a command. The Site must be DC1 or DC2.

• GNS-group

Specify the name of a GNS group that will be used with ECGUTIL commands originating at the specified Site.

• Symmetrix serial

Specify the 5-digit serial number of the Symmetrix control unit on which the devices belonging to the GNS group reside. This is used only when running ECGUTIL.

• RA-group

Specify the number of the RA group associated with the GNS group.

----------------------- GDDR - Define SRDF/S GNS Groups ------ Row 1 to 4 of 4 Command ===> Press <F3> to return to the GDDR Define Storage objects Menu <F5> Define SRDF Device Ranges <F6> Define TimeFinder Device Ranges Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat ------------------------------------------------------------------------------- _ Site: DC1 Symmetrix-serial: 01301 RA-group: 15 GNS-group: TI74_DC1_J0_DC2_RAG15 _ Site: DC1 Symmetrix-serial: 01301 RA-group: 25 GNS-group: TI74_DC1_J0_DC2_RAG25 _ Site: DC2 Symmetrix-serial: 01314 RA-group: 15 GNS-group: TI74_DC2_J0_DC1_RAG15 _ Site: DC2 Symmetrix-serial: 01314 RA-group: 25 GNS-group: TI74_DC2_J0_DC1_RAG25 ******************************* Bottom of data ********************************



Notes: EMC GDDR uses SRDF/S GNS-groups to drive the EMC Consistency Groups ECGUTIL utility. Two GNS groups per RA group, per Symmetrix serial number are required as follows:

– one defining devices in the direction DC1>DC2– one defining devices in the direction DC2>DC1These GNS groups must be created using the EMCGROUP utility. EMC recommends defining these groups by inclusion of an RA group. The number of SRDF/S RA groups at DC1 must be equal to the number of DC1 SRDF/S GNS-groups defined to GDDR; the same is true for DC2.

For example:

_ Site: DC1 Symmetrix-serial: 01301 RA-group: 15 GNS-group: TI74_DC1_J0_DC2_RAG15 _ Site: DC1 Symmetrix-serial: 01301 RA-group: 25 GNS-group: TI74_DC1_J0_DC2_RAG25 _ Site: DC2 Symmetrix-serial: 01314 RA-group: 15 GNS-group: TI74_DC2_J0_DC1_RAG15 _ Site: DC2 Symmetrix-serial: 01314 RA-group: 25 GNS-group: TI74_DC2_J0_DC1_RAG25


5. Press F6 to proceed to the Define TimeFinder Device Ranges panel shown in Figure 26.

Option TF: Define TimeFinder Device RangesWhen you specify option TF in the Define Storage Objects panel shown in “Define Storage Objects panel” on page 101, the following panel appears:

Figure 26 Define TimeFinder Device Ranges panel

1. If the panel is not pre-populated with existing TimeFinder Device Range entries, type Add in the Command field at the top of the panel to display a new line for entry of Site, ConGroup Name, and TimeFinder Device Range.

2. Insert additional Sites by entering R (Repeat) in the command field to the left of an existing entry and overtype the existing data.

-------------------- GDDR - Define TimeFinder Device Ranges Row 1 to 12 of 12 Command ===> Press <F3> to return to the GDDR Define Storage objects Menu <F5> Define SRDF/S GNS Groups <F6> Define SDDF Clean GateKeepers Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat ConGroup TimeFinder CMD Site Name Device Range --- ---- -------- ----------------- _ DC1 CG74TIGA AA1A,15,11F0-11F7 _ DC1 CG74TIGA AA1B,25,11F8-11FF _ DC1 CG74TIGB B21A,15,1208-120F _ DC1 CG74TIGB B21B,25,11F8-11FF _ DC1 CG74TIGB B218,15,11F0-11F7 _ DC1 CG74TIGB B219,25,1200-1207 _ DC2 CG74TIGA AA1A,15,11F0-11F7 _ DC2 CG74TIGA AA1B,25,11F8-11FF _ DC2 CG74TIGB B21A,15,11F0-11F7 _ DC2 CG74TIGB B21B,25,11F8-11FF _ DC2 CG74TIGB B218,15,1200-1207 _ DC2 CG74TIGB B219,25,1208-120F ******************************* Bottom of data ********************************



3. Complete the fields as follows:

• Site

Specify the site location of the BCV-devices being defined, either DC1, DC2, or DC3.

• ConGroup Name

The ConGroup Name field must specify the name of a consistency group defined to GDDR.

BCV devices at DC1 and DC2 require 2 definitions, one for the DC1 consistency group and another for the DC2 consistency group.

• TimeFinder Device Range

Specify contiguous Symmetrix device ranges which are common to the indicated site in the format:

gkdn,rdfgrp,dddd-eeee

gkdn is an MVS address for the site corresponding to the named Consistency group.

rdfgrp is the RDF group spanning gkdn to BCV-siteid.

dddd-eeee is the Symmetrix device number range of the BCVs being managed. It can be either a single Symmetrix device address or a range of addresses (the low address of the range followed by a hyphen and the high address of the range).


5. Press F6 to proceed to the Define SDDF Gatekeepers panel shown in Figure 27.

Option SD: Define SDDF GatekeepersWhen you specify option SD in the Define Storage Objects panel shown in Figure 23 on page 101, the following panel appears:

Figure 27 Define SDDF Clean Utility Gatekeepers panel

The SDDF Clean Utility GateKeeper parameters are not used in the SRDF/S with ConGroup configuration. Press F6 to proceed to the Define Host Objects panel.

----------------- GDDR - Define SDDF Clean Utility GateKeepers Row 1 to 3 of 3 Command ===> Press <F3> to return to the GDDR Define Storage objects Menu <F5> Define TimeFinder Device Ranges <F6> Define Host Objects Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Site GK --- ---- ---- ******************************* Bottom of data ********************************



Option H: Define Host ObjectsWhen you specify option H in the Parameter Management Options Menu shown in Figure 8 on page 85, the Define Host Objects panel appears:

Figure 28 Define Host Objects panel

Complete the following options listed in this panel to define your host objects configuration:

◆ “Option S: Define Managed Systems” on page 107

◆ “Option L: Define Managed LPARs” on page 109

◆ “Option P: Define Managed CPCs” on page 111

◆ “Option I: Define IPL Parameters” on page 112

◆ “Option H: Define Managed HMCs” on page 113

◆ “Option C: Define HMC Community Names” on page 114

◆ “Option D: Define Managed Couple Datasets” on page 115

◆ “Option CF: Define Managed CF Structures” on page 117

◆ “Option W: Define External Workloads” on page 119

◆ “Option E: Define EMC MF Enablers STCs” on page 120

----------------------- GDDR - Define Host Objects ------------------------- Option ===> S Define Managed Systems This System: SYS1 L Define Managed LPARs This Site: DC1 P Define Managed CPCs Master-C: SYS1 I Define IPL Parameters Primary Site: DC1 Primary DASD: DC1 H Define Managed HMCs C Define HMC Community Names Automation: ON Planned script: None D Define Managed Couple Datasets Unplanned script: None CF Define Managed CF Structures W Define External Workloads E Define EMC MF Enablers STCs Select an option and press <Enter> <F5> Define SDDF Clean Utility GateKeepers <F6> Define Managed Systems Press <F3> to return to the GDDR Parameter Management Options Menu



Option S: Define Managed SystemsWhen you specify option S in the Define Host Objects panel, the Define Managed Systems panel appears:

Figure 29 Define Managed Systems panel

Use the managed system parameters to define mainframe systems to EMC GDDR and indicate the extent to which they will be managed by EMC GDDR, either using the online interface or during automation sequences. Do not include C-systems here, as those have been defined to EMC GDDR earlier as described in “Option C: Define C-Systems” on page 97. Managed system parameters are defined for every EMC GDDR-managed production system to enable HMC functions and workload management.

1. If the panel is not pre-populated with existing entries, type Add in the Command field at the top of the panel to display a new line for field entry.

2. Insert additional sites by entering R (Repeat) in the command field to the left of an existing entry and overtype the existing data.

3. Complete the Define Managed System panel fields as follows:

• Site:Specify the ID of the site location being specified. It can have the value DC1 or DC2.

• SystemSpecify the z/OS system name of an EMC GDDR-managed production system which resides at the specified site. You can find the system name on the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or the equivalent parameter file.

• Sysplex (optional)When defining managed systems to EMC GDDR, specify a sysplex name for those systems where couple facility structure and couple facility dataset management actions are to be performed by GDDR.

Couple Facility dataset and structure management is controlled for planned and unplanned scripts by the Rebuild CF Dataset, Rebuild CF Structure, and the CF Rebuild Timeout fields described in “Option S: Script Sysplex Options” on page 123.

----------------------- GDDR - Define Managed Systems -------- Row 1 to 7 of 7 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Host Objects <F6> Define Managed LPARs Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat Contingency Manage HMC CMD Site System Sysplex System Workload Only --- --- -------- ------------- -------- -------- ---- _ DC1 PRD1 _____________ CNT1 YES NO _ DC1 TST1 _____________ TST2 YES NO _ DC1 TST2 _____________ TST1 YES NO _ DC2 CNT1 _____________ PRD1 YES NO _ DC1 TST5 _____________ ________ NO NO _ DC1 TST6 _____________ ________ NO NO _ DC2 TST3 N/A N/A NO YES ******************************* Bottom of data ********************************



The format of this field is: <name>,<type>, where:

– name is the name of the Sysplex to which the defined system belongs– type is either "PLEX", "MONO", or "NONE"This entry is used to simplify data entry on the Sysplex Object management related panels of the GDDR parameter wizard.

Note: For this release, the Sysplex Object Management features are enabled only for systems which have been defined here with <name>,"PLEX".

• Contingency System

Specify a system at a remote site on which production business applications can run if a primary production system fails. A contingency system should be given for each GDDR-managed production system running at DC1 or DC2.

This field may be left blank, as contingency systems are not required.

If specified, a contingency system for a system located at site DC1 must be located at site DC2. A contingency system for a system located at site DC2 must be located at site DC1.

• Manage Workload

Indicates whether EMC GDDR will trigger start/stop of the workload on the specified Site, System, Sysplex and Contingency System. Type YES to cause EMC GDDR to trigger the stop and start of applications when EMC GDDR takes planned or unplanned actions that impact the managed production systems.

• HMC Only

Indicates whether the specified system is external to the population of systems managed by EMC GDDR. HMC Only 'YES' Systems may be managed using the GDDR HMC LPAR Actions panel. Type YES to bypass EMC GDDR parameter validation for the specified system. Type NO to specify that the system is to be managed by EMC GDDR.


5. Press F6 to proceed to the Define Managed LPARs panel shown in Figure 30.



Option L: Define Managed LPARsWhen you specify option L in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 30 Define Managed LPARs panel

EMC GDDR HMC command requests are directed to HMC using the LPAR name and the processor name where the LPAR is defined. To enable HMC functions (IPL, CBU, and so forth), these variables must be defined for every GDDR-managed production system and GDDR C-System.



3. Complete the Define Managed LPAR panel fields as follows:

• Site

Indicates the ID of the site location being specified. Site values are populated from the Define Managed Systems panel. Valid values are DC1 or DC2.

• System

This field is populated from the System name supplied in the Define Managed Systems panel, one row per system, for the site which is the home site for that system.

Note: If the field has not been pre-filled, this is the z/OS system name of an EMC GDDR-managed production system or an EMC GDDR C-System which resides at the specified site. The name may be found on the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or the equivalent parameter file.

Add rows for each additional site housing a CPC where a populated system can be IPL'd.

• Central Processor Complex (CPC)

Specify the name of the central processor where the managed production LPAR is defined.

----------------------- GDDR - Define Managed LPARs ------- Row 1 to 9 of 9 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed Systems <F6> Define Managed CPCs Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Site System CPC LPAR Bypass HMC --- --- -------- -------- -------- ---------- _ DC1 PRD1 PRD1CPC LPARPRD1 NO _ DC1 TST1 TST1CPC LPARTST1 NO _ DC1 TST2 TST2CPC LPARTST2 YES _ DC1 TST5 TST5CPC LPARTST5 YES _ DC1 TST6 TST6CPC LPARTST6 YES _ DC2 CNT1 CNT1CPC LPARCNT1 NO _ DC2 TST3 TST3CPC LPARTST3 NO ******************************* Bottom of data ********************************



• Logical Partition (LPAR)

Specify the name of the LPAR within which this system runs at the specified site.

You can find the CPC and LPAR names using the D M=CPU MVS console command, as shown in the following sample output:

RESPONSE=SYSB IEE174I 20.59.34 DISPLAY M 781 PROCESSOR STATUS ID CPU SERIAL 0 02F94E2096 1 02F94E2096 2 02F94E2096 CPC ND = 002096.S07.IBM.83.00000008F94E CPC SI = 2096.N03.IBM.83.000000000008F94E CPC ID = 00 CPC NAME = C LP NAME = ZOSESYSB LP ID = 2 CSS ID = 0 MIF ID = 2 ONLINE - OFFLINE . DOES NOT EXIST W WLM-MANAGED N NOT AVAILABLE CPC ND CENTRAL PROCESSING COMPLEX NODE DESCRIPTOR CPC SI SYSTEM INFORMATION FROM STSI INSTRUCTION CPC ID CENTRAL PROCESSING COMPLEX IDENTIFIER CPC NAME CENTRAL PROCESSING COMPLEX NAME LP NAME LOGICAL PARTITION NAME

• Bypass HMC

Identifies the LPARs where hardware management console actions should be bypassed. When YES, this bypass affects all HMC actions for the specified LPARs. This includes Load, Reset, Activate, Deactivate, manual and automatic CBU Activate and Undo, Couple DS Realignment, and CF Structure Rebuild. Set this field to NO for EMC GDDR-managed LPARs.

If you set this field to * for any LPAR at site DCm, then on the next Save command, HMC Bypass will be in effect for ALL LPARs at site DCm. This is visible once you issue a LOAD after that Save.


5. Press F6 to proceed to the Define Managed CPCs panel shown in Figure 31.



Option P: Define Managed CPCsWhen you specify option P in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 31 Define Managed CPCs panel



3. Complete the Define Managed CPCs panel fields as follows:

• Site

Indicates the ID of the site location being specified. Valid values are DC1 or DC2.

• Central Processor Complex (CPC)

Indicates the name of the central processor where the managed production LPAR is defined. There are no limits on the number of CPC name entries per site.

• Capacity Backup (CBU)

Defines whether Capacity Backup Upgrade is enabled from the GDDR ISPF interface for the named CPC. Specify YES or NO. If YES is specified, CBU actions will be allowed using the GDDR ISPF interface.


5. Press F6 to proceed to the Define IPL Parameters panel shown in Figure 32.

-------------------------- GDDR - Define Managed CPCs -------- Row 1 to 7 of 7 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed LPARs <F6> Define IPL Parameters Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Site CPC CBU --- --- -------- --- _ DC1 PRD1CPC YES _ DC1 TST1CPC NO _ DC1 TST2CPC NO _ DC1 TST5CPC NO _ DC1 TST6CPC NO _ DC2 CNT1CPC YES _ DC2 TST3CPC NO ******************************* Bottom of data ********************************



Option I: Define IPL ParametersWhen you specify option I in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 32 Define IPL Parameters panel

The Define IPL parameters panel specifies the IPL parameters that EMC GDDR may use to IPL an EMC GDDR-managed production system at the primary DASD site. The following statements describe requirements for production systems and GDDR C-Systems:

◆ A production system can have an IPL parameter for each of sites DC1 and DC2. This is because the primary DASD can reside at either of these locations.

◆ A production system requires an IPL parameter for site DC1 and site DC2.



3. Complete the Define IPL Parameter panel fields as follows:

• Site

Indicates the ID of the site location being specified. Valid values are DC1 or DC2.

• System

This field is populated from the System name supplied in the Define Managed Systems panel, one row per system, for the site which is the home site for that system.

Note: If the field has not been pre-filled, this is the z/OS system name of an EMC GDDR-managed production system or an EMC GDDR C-System which resides at the specified site. The name may be found on the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or the equivalent parameter file.

Add rows for each additional site housing a CPC where a populated system can be IPL'd.

• STD RES IPL Parameters

• STD ALT IPL Parameters

• BCV IPL Parameters

------------------------- GDDR - Define IPL Parameters ------------ Row 1 of 6 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed CPCs <F6> Define Managed HMCs Type <SAVE> to save, <LOAD> restart from last saved values. Line commands: A dd, D elete, R epeat STD RES IPL STD ALT IPL BCV IPL HMC CMD Site System Parameters Parameters Parameters Only --- --- -------- ------------- ------------- ------------- --- _ DC1 T101 7070,707099M1 7080,708099M1 _____________ NO _ DC1 T102 707A,707A99M1 708A,708A99M1 _____________ NO _ DC2 T101 7170,717099M1 7180,718099M1 _____________ NO _ DC2 T102 717A,717A99M1 718A,718A99M1 _____________ NO ******************************** Bottom of data ********************************



In the format: ssss,iiiixxmn

Where

ssss is the Sysres device address

iiii is the IODF device address

xx is the LOADxx member suffix

m is the IMSI Field

n is the IEANUC0n suffix

• HMC Only

Indicates if the specified system is external to the population of systems managed by EMC GDDR. HMC Only 'YES' Systems may be managed using the GDDR HMC LPAR Actions panel. EMC GDDR parameter validation is bypassed for systems defined YES in the HMC Only field. This field is not editable.

You can locate IPL parameters using the D IPLINFO MVS console command, as shown in the following sample output:

RESPONSE=SYSB IEE254I 21.14.59 IPLINFO DISPLAY 860 SYSTEM IPLED AT 15.59.20 ON 02/02/2009 RELEASE z/OS 01.10.00 LICENSE = z/OSe USED LOAD02 IN SYS1.IPLPARM ON 0A26 ARCHLVL = 2 MTLSHARE = N IEASYM LIST = B0 IEASYS LIST = B0 (OP) IODF DEVICE 0A26 IPL DEVICE 0A1D VOLUME RESB14


5. Press F6 to proceed to the Define Managed HMCs panel shown in Figure 33.

Option H: Define Managed HMCsWhen you specify option H in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 33 Define Managed HMCs panel

1. Complete the Define Managed HMCs panel fields as follows:

• Site

Indicates the ID of the site location being specified. Valid values are DC1 or DC2. This field is not editable.

-------------------------- GDDR - Define Managed HMCs ------------- Row 1 of 2 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define IPL Parameters <F6> Define HMC Community Names Type <SAVE> to save, <LOAD> to restart from last saved values. Enter the required information. Press <Enter> to Validate. Site IP-address Timeout --- --------------- ----- DC1 nnn.nnn.nnn.nnn 25000 DC2 nnn.nnn.nnn.nnn 25000 ******************************* Bottom of data ********************************



• IP-address

Specify the IP address of the hardware management console located at the location specified by Site. EMC GDDR uses this IP-address to perform console operations at that site location.

Note: Only one HMC IP-Address parameter per Site is permitted. If a site is specified in the current configuration in the Define Managed Systems panel, then an HMC IP-Address must be present for that site.

• Timeout

Specify the maximum number of milliseconds a request to an HMC console at a specified site may remain outstanding before it is considered to have timed out. The maximum value you can specify is 99999; the minimum is 1. The default value is 25000.


3. Press F6 to proceed to the Define HMC Community Names panel shown in Figure 34.

Option C: Define HMC Community NamesWhen you specify option C in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 34 Define HMC Community Names panel



3. Complete the panel fields as follows:

• HMC Site

Indicates the ID of the site location being specified. Site values are populated from the Define Managed Systems panel. Valid values are DC1 or DC2.

• C-System

Indicates the system name of the C-System at the location specified by Site. C-System values are populated from the Define Managed Systems panel.

---------------------- GDDR - Define HMC Community Names ----- Row 1 to 6 of 6 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed HMCs <F6> Define Managed Couple DS (1/2) Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete HMC HMC CMD Site C-System Community Name --- --- -------- ---------------- _ DC1 Q31B t108 _ DC1 Q311 zoseq311 _ DC1 Q312 zoseq312 _ DC2 Q31B t108 _ DC2 Q311 zoseq311 _ DC2 Q312 zoseq312 ******************************* Bottom of data ********************************



• HMC Community Name

Specify a case-sensitive community name to be used to allow the named C-system access to the HMC on the indicated site. The default community name for each C-System/site combination is the system name in lowercase. If you provide a different community name, EMC GDDR uses the specified name in place of the default name when an LPAR initiates a command to the HMC console.

Note: The maximum length of the community name for the HMC is established by the HWMCA MAX COMMUNITY LEN parameter for the site. For more information, refer to the System z Application Programming Interfaces manual, SB10-7030-11, Data exchange APIs and commands API structures and definitions topic. The current maximum is 16 characters.


5. Press F6 to proceed to the Define Managed Couple Datasets panel shown in Figure 35.

Option D: Define Managed Couple DatasetsWhen you specify option D in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 35 Define Managed Couple Datasets panel 1 of 2

The use of Couple Datasets is dependent on the site's exploitation of sysplex architecture. If no managed production systems are part of a sysplex, the following message is returned upon opening this panel:

GDDI371W No sysplexes defined, please either assign systems to a sysplex or proceed to the next panel.

The fields in panel 1 of the Define Managed Couple Datasets option indicate the types of couple datasets that are used on a specified sysplex.

1. View, define, or modify the panel 1 fields as follows:

• Sysplex

Indicates the sysplex name, if applicable. Sysplex values are populated from the Define Managed Systems panel.

• Couple Dataset Types: ARM CFR LOGR SFM SYS WLM

Type YES or NO under each dataset type to indicate whether or not you want EMC GDDR to ensure correct couple dataset placement for that type during planned and unplanned site swap scripts for a specified sysplex.


----------------- GDDR - Define Managed Couple Datasets (1/2) Row 1 to 1 of 1 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define HMC Community Names <F6> Define Managed Couple DS (2/2) Type <SAVE> to save, <LOAD> to restart from last saved values. Indicate (Yes/No) for which types you want GDDR Couple Dataset management. Sysplex ARM CFR LOGR SFM SYS WLM -------- --- --- --- --- --- --- ******************************* Bottom of data ********************************



3. Press F6 to complete the couple dataset definitions as shown in the following panel:

Figure 36 Define Managed Couple Datasets panel 2 of 2

The fields in panel 2 of the Define Managed Couple Datasets option indicate the names of primary and alternate couple datasets of the specified type to be used on the systems belonging to the specified sysplex.

Note: Each couple dataset must be catalogued on all systems in the sysplex.

There must be a primary and an alternate couple dataset each sysplex, for each of the possible primary DASD sites, and for each couple dataset type being used.

EMC GDDR ensures that the primary couple datasets are located wherever the primary DASD currently resides. If the secondary DASD site is available, EMC GDDR ensures that an alternate couple dataset is used on the secondary DASD site.

Four lines display for each sysplex and managed type, one line for each dataset's role (P or A) for both sites DC1 and DC2. For each type and role within a sysplex, specify the dataset names that are cataloged at DC1 and DC2 as shown in Table 9:

---------------- GDDR - Define Managed Couple Datasets (2/2) ------------------ Option ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed Couple DS (1/2) <F6> Define Managed CF Structures Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Sysplex TYPE SITE ROLE Couple Dataset Name --- -------- ---- --- - -------------------------------------------- ******************************* Bottom of data ********************************

+----------------------------------------------------------------------------+ | No sysplexes defined, please either assign systems to a sysplex or proceed | | to the next panel. | +----------------------------------------------------------------------------+

Table 9 Defining Managed Couple Datasets

Sysplex TYPE SITE ROLE Couple Dataset Name

TESTPLX1 ARM DC1 P DSN1: used as Primary when DC1 is Primary and used as Alternate when DC1 is Secondary

A DSN3: used as Alternate when DC1 is Primary and DC2 is unavailable

DC2 P DSN2: used as Primary when DC2 is Primary and used as Alternate when DC2 is Secondary

A DSN4: used as Alternate when DC2 is Primary and DC1 is unavailable



1. View, define, or modify the fields displayed in panel 2 as follows:

• Sysplex

Indicates the sysplex name. Sysplex values are populated with the list of sysplexes which have at least one managed couple dataset type, as specified on panel 1.

• Type

Indicates the couple dataset type as specified on panel 1. Valid values are ARM, CFR, LOGR, SFM, SYS, or WLM.

• Site

Indicates the ID of the site location.

• Role

Indicates the role of the dataset. Valid values are P for primary or A for Alternate.

• Couple Dataset Name

Specify the dataset names that are cataloged at DC1 and DC2.


3. Press F6 to proceed to the Define Managed CF Structures panel shown in Figure 37.

Option CF: Define Managed CF StructuresWhen you specify option CF in the Define Host Objects panel shown in Figure 28 on page 106, the following panel series appear:

Figure 37 Define Managed CF Structures panel 1 of 2

--------------------- GDDR - Define Managed CF Structures -- Row 1 to 16 of 28 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed Couple DS (2/2) <F6> Define External Workloads Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Sysplex Structure Name CF-Site Eligible Coupling Facility Names --- -------- ---------------- --- ----------------------------------- _ PROD DSNDB2I_GBP0 DC1 C15 _ PROD DSNDB2I_GBP0 DC2 O15 _ PROD DSNDB2I_GBP14 DC1 C15 _ PROD DSNDB2I_GBP14 DC2 O15 _ PROD DSNDB2I_GBP32K DC1 C15 _ PROD DSNDB2I_GBP32K DC2 O15 _ PROD DSNDB2I_LOCK1 DC1 C15 _ PROD DSNDB2I_LOCK1 DC2 O15 _ PROD DSNDB2I_SCA DC1 C15 _ PROD DSNDB2I_SCA DC2 O15 _ PROD EOCP_RRS_STR_1 DC1 C15,O15 _ PROD EOCP_RRS_STR_1 DC2 O15,C15 _ PROD EOCP_RRS_STR_2 DC1 C15,O15 _ PROD EOCP_RRS_STR_2 DC2 O15,C15 _ PROD IEFAUTOS DC1 C15 _ PROD IEFAUTOS DC2 O15



Figure 38 Define Managed CF Structures panel 2 of 2

Note: If the EMC GDDR-managed production systems are not members of a sysplex, the following message is displayed in the panel:

No sysplexes defined, please either assign systems to a sysplex or proceed to the next panel.

EMC GDDR will issue Display XCF commands for the CF Structures identified in the Define Managed CF Structures panel and determine if they are currently located in the preferred couple facility. If a structure is found in a different couple facility than the one which is first in the list for the current primary DASD site, EMC GDDR will issue REBUILD commands and verify the results. Verification is repeated until all structures are located in one of the acceptable couple facilities.

Couple Facility structure management is controlled for planned and unplanned scripts by the Rebuild CF Structure and the CF Rebuild Timeout fields described in “Option S: Script Sysplex Options” on page 123.

1. View, define, or modify the panel fields as follows:

• Sysplex

Indicates the sysplex name, if applicable. Sysplex values are populated from the Define Managed Systems panel.

If the panel is not pre-populated with existing Sysplex name entries, type Add in the Command field at the top of the panel to display a new line for an entry. Insert additional Sysplex names by entering R in the command field to the left of an existing Sysplex entry.

• Structure Name

Provide a Couple Facility Structure name or names for each specified Sysplex using the following guidelines:

– Length: 1-16 characters – Position 1: Uppercase alphabetic – Positions 2-16: Uppercase alphabetic, numeric, or _, @, $, #

--------------------- GDDR - Define Managed CF Structures - Row 17 to 28 of 28 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed Couple DS (2/2) <F6> Define External Workloads Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Sysplex Structure Name CF-Site Eligible Coupling Facility Names --- -------- ---------------- --- ----------------------------------- _ PROD ISGLOCK DC1 C15 _ PROD ISGLOCK DC2 O15 _ PROD IXCLIST1 DC1 C15 _ PROD IXCLIST1 DC2 O15 _ PROD IXCLIST2 DC1 C15 _ PROD IXCLIST2 DC2 O15 _ PROD LOGREC DC1 C15 _ PROD LOGREC DC2 O15 _ PROD OPERLOG DC1 C15 _ PROD OPERLOG DC2 O15 _ PROD SYSZWLM_360E20 DC1 C15 _ PROD SYSZWLM_360E20 DC2 O15 ******************************* Bottom of data ********************************



• CF Site

The ID of the site location being specified. Site values are populated from the Define Managed Systems panel.

• Eligible Coupling Facility Names

Provide up to 4 Couple Facility names, delimited by commas, using the following guidelines:

– Length: 1-8 characters – Position 1: Uppercase alphabetic – Position 2-8: Uppercase alphabetic, numeric, or _, @, $, #


3. Press F6 to proceed to the Define External Workloads panel shown in Figure 39.

Option W: Define External WorkloadsExternal workloads are mainframe applications that are not hosted on EMC GDDR-managed production systems, and access storage outside of EMC GDDR-managed RDF groups. When EMC GDDR takes planned or unplanned actions that impact the managed production systems, it has the capability to trigger the stop or start of external workloads through a user-exit.

Note: The definition of external workloads is optional. If no external workloads are to be Stopped or Started in sequence with managed systems, press F6 to proceed to the Define EMC Mainframe Enablers Started Tasks panel.

When you specify option W in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 39 Define External Workloads panel

1. Type Add in the Command field at the top of the panel to display a new line for an entry.


• Site

Indicates the ID of the specified site location.

• System

Indicates the system names which host external workload requiring coordination with system actions performed by EMC GDDR.

----------------------- GDDR - Define External Workloads ----- Row 1 to 2 of 2 Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define Managed CF Structures <F6> Define EMC Mainframe Enablers STCs Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat CMD Site System --- --- -------- _ DC1 SYS8 _ DC2 SYSA ******************************* Bottom of data ********************************



Note: If you are using the user exits provided with EMC GDDR, then communication to the targeted systems requires the GDDRCBAL and GDDRPBAL started tasks to be up and running, while EMC GDDR parmlib member GDDRMSGC must include messages GDDX191I and GDDX291I.


4. Press F6 to proceed to the Define EMC MF Enablers STCs panel shown in Figure 40.

Option E: Define EMC MF Enablers STCsEMC GDDR uses information about the site's installation parameters to communicate with EMC Mainframe Enablers started tasks that reside on EMC GDDR-managed production systems and EMC GDDR C-Systems.

When you specify option E in the Define Host Objects panel shown in Figure 28 on page 106, the following panel appears:

Figure 40 Define EMC MF Enablers STCs panel

1. Type Add in the Command field at the top of the panel to display a new line for an entry.


• System

Indicates the z/OS system name of an EMC GDDR-managed production system or an EMC GDDR C-System which resides at the specified site. System Name values are populated from the Define Managed Systems panel.

• Type

Indicates the Mainframe Enablers application. Valid abbreviations are:

– SCF: Symmetrix Control Facility (ResourcePak Base)– RDF: SRDF Host Component – CG: Consistency Group

• STC Name

Provides the started task name associated with the specified Mainframe Enablers application type:

------------------- GDDR - Define EMC Mainframe Enablers STCs Row 1 to 7 of 10Command ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Define External Workloads <F6> Specify GDDR Options Type <SAVE> to save, <LOAD> to restart from last saved values. Line commands: A dd, D elete, R epeat STC SUB CMD System Type Name MSTR Parameter Dataset and Member(s) --- -------- ---- -------- ---- -------------------------------------------- _ CNT1 CG GDDRCGRP YES X CGPCFG09 _ PRD1 CG GDDRCGRP YES X CGPCFG09 _ Q311 CG GDDRCGRP NO X CGPCFG09 _ Q312 CG GDDRCGRP NO X CGPCFG09 ******************************* Bottom of data ********************************



– When the type is CG: Specifies the jobname of the ConGroup started task on a C-System, a production system, or a contingency system. The value of this parameter is used in MODIFY commands issued from within scripts running on the system to which the statement applies. It is also used to perform ConGroup Stop and Start commands if the corresponding call override is used.

• SUB MSTR

Indicates whether the started task runs as SUB=MSTR; that is, if it starts before JES2 is available. In accordance with the recommendation in the EMC Consistency Group for z/OS Product Guide, the Consistency Group and Symmetrix Control Facility started tasks must be started SUB=MSTR on EMC GDDR-managed hosts.

No started tasks need to be started SUB=MSTR on EMC GDDR C-Systems.

• Parameter Dataset and Member(s)

Provides the name of the partitioned dataset and members containing the customization parameters for the specified started task. This field does not apply to type = SCF. For type = CG, specify the dataset name as "X".

Note: “Install EMC GDDR C-System started procedures” on page 60 provides more information.


4. Press F6 to proceed to the Specify GDDR Options panel.

Option O: Specify GDDR OptionsWhen you specify option O in the Parameter Management Options Menu shown in Figure 8 on page 85, the Specify GDDR Options panel appears:

Figure 41 Specify GDDR Options panel

Complete the following options listed in this panel to define your site-specific script options:

◆ “Option O: Default Script Call Overrides” on page 122

◆ “Option S: Script Sysplex Options” on page 123

----------------------- GDDR - Specify GDDR Options ------------------------- Option ===> O Default Script Call Overrides This System: SYS1 S Script Sysplex Options This Site: DC1 A Script AUTOCBU Options Master-C: SYS1 J Script JCL Parameters Primary Site: DC1 U Utility Parameters Primary DASD: DC1 M Messaging and SMF Options T Tuning Values Automation: ON Planned script: None Unplanned script: None Select an option and press <Enter> <F5> Define EMC MF Enablers STCs <F6> Default Script Call Overrides Press <F3> to return to the GDDR Parameter Management Options Menu



◆ “Option A: Script AUTOCBU Options” on page 124

◆ “Option J: Script JCL Parameters” on page 125

◆ “Option U: Utility Parameters” on page 127

◆ “Option M: Messaging and SMF Options” on page 128

◆ “Option T: Tuning Values” on page 130

Option O: Default Script Call OverridesWhen you specify option O in the Specify GDDR Options panel, the following panel appears:

Figure 42 Specify Default Script Call Overrides panel

1. Overtype the default Y or N call override values to change the default overrides used by all scripts.

Table 11, “EMC GDDR call overrides,” on page 165 lists the possible call overrides and their meanings.

Note: GDDR BCV management is controlled using call overrides to program GDDRKF21. If you set call overrides to allow GDDR BCV management for a given site, it is assumed that BCVs are in the proper state prior to the script being started; therefore, you should not change BCV states in between scripts using non-GDDR actions.

With EMC GDDR Version 3.1, you must ensure that Call Overrides for BCV management at a given site are set to N, if no BCVs are defined to GDDR for that site.


3. Press F6 to proceed to the Script Sysplex Options panel.

---------------- GDDR - Specify Default Script Call Overrides ---------------- Option ===> Press <F3> to return to the GDDR Specify Options Menu <F5> Specify GDDR Options Menu <F6> Script Sysplex Options Type <SAVE> to save, <LOAD> to resume your work. Enter Y to call the function, N to NOT call the function. Call Program Function Description ---- -------- ---------------------------------------------------------- More: + Y GDDRDY01 Call DYNAPI Interface Y GDDRGF2P DYNAPI - Issue SRDF/S Commands Y GDDRKF0U DYNAPI - Half DeletePair DC3 and Old Primary Y GDDRKF0W DYNAPI - Create STAR SRDFA Pairs Y GDDRGF0J DYNAPI - Issue commands to JA RDF Group Y GDDRKF43 DYNAPI - Perform Personality Swap N GDDRKF0C Trigger Production Workload Stop N GDDRKF0I Trigger Production Workload Startup Y GDDRGF08 Use ConGroup Shutdown/Startup instead of Refresh

Y GDDRKF0E Transfer AutoSwap Ownership Y GDDRDY01 Transfer Master Function Ownership N GDDRKF21 Simulate BCV Actions N GDDRKF21 Manage BCVs at DC1 N GDDRKF21 Manage BCVs at DC2 N GDDRKF21 Manage BCVs at DC3 N GDDRCL00 Perform SDDF Session Cleanup N GDDRRDF0 Manage Non-STAR devices ******************************* Bottom of Data ******************************



Option S: Script Sysplex Options When you specify option S in the Specify GDDR Options panel shown in Figure 41 on page 121, the following panel appears:

Figure 43 Script Sysplex Options panel

1. Specify YES or NO for the following script management options for each site:

• Realign Couple Datasets

Specify whether Planned or Unplanned scripts should manage couple datasets when the primary DASD site is DCn. Further control is provided by the couple datasets defined in Option D, Define Managed Couple Datasets, as shown in Figure 36 on page 116 and the External field in the Define IPL Parameters panel as shown in Figure 32 on page 112.

– When Planned is YES: Automate the management of couple datasets as a part of planned script processing.

– When Unplanned is YES: Automate the management of couple datasets as a part of unplanned script processing.

• Rebuild CF Structures

Specify whether Planned or Unplanned scripts should manage Coupling Facility (CF) Structures at site DCn. Further control is provided by the PSTR.* parameters, and the System Exclude list.

– When Planned is YES: Automate the management of Coupling Facility Structures as a part of planned script processing.

– When Unplanned is YES: Automate the management of Coupling Facility Structures as a part of unplanned script processing.

• CF Rebuild Timeout

Specify the number of seconds to allow for the processing required to rebuild Coupling Facility structures. Valid values are 1-3600. The default value is 600.


3. Press F6 to proceed to the Script AUTOCBU Options panel.

---------------------- GDDR - Script Sysplex Options ------------------------ Option ===> Press <F3> to return to the GDDR Specify Options Menu <F5> Default Script Call Overrides <F6> Script AUTOCBU Options Type <SAVE> to save, <LOAD> to resume your work. Please indicate (Yes/No) GDDR Script Sysplex management options by Site. Realign Rebuild Couple Datasets CF Structures CF Rebuild Site Planned Unplanned Planned Unplanned Timeout ---- ------- --------- ------- --------- ------- DC1 NO NO NO NO 600 DC2 NO NO NO NO 600 DC3 NO? NO? NO NO 600 ******************************** Bottom of Data *******************************



Option A: Script AUTOCBU OptionsThe AUTOCBU Options allows script control of capacity backup activation by cpcname and site. The presence of this parameter invokes script automation to activate licensed processing capacity on specified central processing complexes (CPCs) at the recovery site specified by Site in preparation for restart of workload.

Operator control of capacity backup activation is performed using the Perform GDDR Actions menu. The option to cancel capacity backup following an activation is only available from the Perform HCM CBU Actions panel, using the Undo CBU option. “Option CBU: Perform HMC CBU actions” on page 156 provides more information.

When you specify option A in the Specify GDDR Options panel shown in Figure 41 on page 121, the following panel appears:

Figure 44 Script AUTOCBU Options panel

1. If the panel is not pre-populated with existing Site name and CPC entries, type Add in the Option field at the top of the panel to display a new line for an entry.


• Site

Indicates the ID of the site location being specified. Site values are populated from the Define Managed Systems panel.

• CPC

Indicates the Central Processor Complex name hosting the managed systems at the specified Site. The CPC names are populated from the Define Managed CPCs panel.

• Planned

Valid values are REAL, TEST, or NONE.

– When REAL, capacity backup licenses will be activated as a part of planned script processing.

– When TEST, capacity backup capacity will be simulated as part of planned script processing.

– When NONE, no capacity backup automation actions are performed. This is the default value.

----------------------- GDDR - Script AUTOCBU Options ------------ Row 1 of 3 Option ===> Press <F3> to return to the GDDR Define Host Objects Menu <F5> Script Sysplex Options <F6> Script JCL Parameters Type <SAVE> to save, <LOAD> to resume your work. Line commands: A dd, D elete Specify AUTOCBU Option for GDDR Scripts: CMD Site CPC Planned Unplanned --- ---- -------- ----- ----- _ DC1 C NONE NONE (REAL/TEST/NONE) _ DC2 O NONE NONE (REAL/TEST/NONE) ******************************* Bottom of data ********************************



• Unplanned

Valid values are REAL, TEST, or NONE.

– When REAL, capacity backup licenses will be activated as a part of unplanned script processing.

– When TEST, capacity backup capacity will be simulated as part of unplanned script processing.

– When NONE, no capacity backup automation actions are performed. This is the default value.


4. Press F6 to proceed to the Script JCL Parameters panel.

Option J: Script JCL ParametersGDDR Planned and Unplanned automation sequences run as MVS batch jobs. The Script JCL Parameters panel provides the customization required for those batch jobs to run successfully in your MVS environment. For GDDR scripts started internally by EMC GDDR, this panel is the only place where this information can be provided. The jobcard information can be overridden as part of the script submission started from the Select Script to Run panel as shown in “Option S: Scripts—Run GDDR Scripts” on page 148.

When you specify option J in the Specify GDDR Options panel shown in Figure 41 on page 121, the following panel appears:

Figure 45 Script JCL Parameters panel


• Site - C-System (display only)

Script JCL values are maintained for each C-System. Complete the values for the first displayed C-System, and scroll to the next C-System using F8.

• HC-Prefix

Specifies the prefix that will be used for SRDF Host Component API commands. The default value set by EMC GDDR is null, and must be replaced by a valid prefix during EMC GDDR customization.

------------------------ GDDR - Script JCL Parameters ------------- Row 1 of 3 Option ===> Press <F3> to return to the Specify GDDR Options Menu <F5> Script AUTOCBU Options <F6> Utility Parameters Type <SAVE> to save, <LOAD> to restart from last saved values. Enter the required information. Use <Up> or <Down> to scroll through C-Systems. Site: DC1 C-System: SYS4 HC-Prefix: # SCF-Suffix: V700 Work Unit: SYSALLDA Jobname Prefix: GDD Enforce: Y Work HLQ: ________ Surrogate User ID: ________ Enforce: N Enter jobcards: //GDDRUNPL JOB (ACCT-NUMBER),GDDR-JOB,CLASS=A, // MSGCLASS=A,USER=GDDR,NOTIFY=&SYSUID /*JOBPARM LINES=999999 //*



• SCF-Suffix

Specifies the suffix appended to 'SCF$' to form the DDname on a DD statement in unplanned script jobs and GDDRMAIN and the Console and Heartbeat monitors, associating these with an SCF subsystem. The default value set by EMC GDDR is "EMC" which is suitable only if you want EMC GDDR scripts to connect to an SCF instance which either does not specify an SCF subsystem ID, or also specifies "EMC".

• Work Unit

Indicates the user-specified device esoteric value that represents the storage device type to be used when EMC GDDR dynamically allocates temporary datasets. The default value is SYSALLDA.

Note: If you wish to change the default from SYSALLDA, ensure that the replacement device esoteric is not defined to z/OS using the 'VIO' attribute.

• Jobname Prefix and Enforce

Specifies a 3-character prefix that is used as the first three characters of EMC GDDR jobnames.

When you provide the jobname prefix and enter Y in the Enforce field, EMC GDDR internally-submitted jobs will use the jobname prefix specified in this panel. Any attempts to start a script from the Select Script to Run panel using a different jobname prefix will fail.

• Work HLQ

Specifies a dataset high-level-qualifier that is used for work datasets.

• Surrogate User ID and Enforce

Specifies the user ID that has been authorized to all of the resources required by EMC GDDR processes. EMC recommends specifying the user ID provided in the ADDUSER statement of the GDDCRACF C-System RACF definitions, as described in “Specify EMC GDDR security” on page 54.

When you provide the user ID and enter Y in the Enforce field, EMC GDDR internally-submitted jobs will use the surrogate user ID specified in this panel. Any attempts to start a script from the Select Script to Run panel using a different user ID will fail.

• Enter Jobcards

These fields specify the jobcards that will be used when a job is submitted internally by EMC GDDR.


3. Press F6 to proceed to the Utility Parameters panel.



Option U: Utility ParametersEMC GDDR script processing sometimes requires invoking external utilities, which have their own space allocation requirements and control settings. This is done using values supplied by the EMC GDDR Utility Parameters panel.

When you specify option U in the Specify GDDR Options panel shown in Figure 41 on page 121, the following panel appears:

Figure 46 Utility Parameters panel


• EMCGROUP Allocation Parameters

– SYSIN: Recommended allocation is TRACKS,1,1 – REPORT: Recommended allocation is CYLINDERS,1,1 – SYSPRINT: Recommended allocation is CYLINDERS,1,1

• EMCTF Parameters

– SYSIN: Recommended allocation is TRACKS,5,2 – SYSOUT: Recommended allocation is TRACKS,50,50 – MAXREQ: Recommended value is 20000

• RPTOUT Allocation Parameters

– SCFRDFME: Recommended allocation is TRACKS,5,2 – SCFRDFM6: Recommended allocation is TRACKS,5,2 – SCFRDFM9: Recommended allocation is TRACKS,5,2

• ECGUTIL Parameters:

– COMMAND: Recommended allocation is CYLINDERS,10,10– Number of Tasks: Recommended value is 22 – MSGLEVEL: Recommended value is 5

• Utility Names

– IEBGENER: IEBGENER – SDDF Cleanup: GDDFCLN1 – SDDF List: GDDFLIST

-------------------------- GDDR - Utility Parameters --------------------------Command ===> Press <F3> to return to the Specify GDDR Options Menu <F5> Script JCL Parameters <F6> Messaging and SMF Options Type <SAVE> to save, <LOAD> to restart from last saved values. Enter the required information. Press <Enter> to Validate. EMCGROUP Allocation Parameters EMCTF Parameters - SYSIN : TRACKS,1,1 - SYSIN : TRACKS,5,2 - REPORT : CYLINDERS,1,1 - SYSOUT : TRACKS,50,50 - SYSPRINT : CYLINDERS,1,1 - MAXREQ : 20000 RPTOUT Allocation Parameters ECGUTIL Parameters - SCFRDFME : TRACKS,5,2 - COMMAND allocation: CYLINDERS,10,10 - SCFRDFM6 : TRACKS,5,2 - Number of Tasks : 22 - SCFRDFM9 : TRACKS,5,2 - Message Level : 5 Utility Names HMC Optional settings - IEBGENER : IEBGENER - Use Direct Initialize : N - SDDF Cleanup : GDDFCLN1 - Security check on Discover : Y - SDDF List : GDDFLIST - Simulate HMC Actions : N ******************************** Bottom of Data *******************************



• HMC Optional settings:

– Use Direct Initialize: Enter Y or N.Direct Initialize is an HMC API option that directs HMC API communication to use port 3161. This option is useful for installations where a firewall exists between EMC GDDR and the HMC console. Specifying Y allows an installation to open a particular port (port 3161) in the firewall.

– Security check on Discover: Recommended value is Y. This is a customer preference with regards to daily usage. With regards to installing the product, suppressing the security check may be required to verify that the HMC setup steps are completed successfully.

– Simulate HMC Actions: Recommended value is N.The recommendation for Simulate HMC Actions is to leave this as N always, unless instructed by EMC Customer Service to change this setting.


3. Press F6 to proceed to the Messaging and SMF Options panel.

Option M: Messaging and SMF OptionsWhen you specify option M in the Specify GDDR Options panel shown in Figure 41 on page 121, the following panel appears:

Figure 47 Messaging and SMF Options panel


• SMF Starting Subrecord number

Specifies the SMF subrecord number to be assigned to SMF records produced by GDDR Audit Monitoring collection. The same subrecord number is used for records produced by all C-Systems. The default value is 2000.

• Log Options

Selection of any of the "Log" options enables writing of GDDR Audit Monitoring SMF records for occurrences of the specified message types.

----------------------- GDDR - Messaging and SMF Options ---------------------- Command ===> Press <F3> to return to the Specify GDDR Options Menu <F5> Utility Parameters <F6> GDDR Tuning Values Type <SAVE> to save, <LOAD> to restart from last saved values. Enter the required information. Press <Enter> to Validate. SMF Starting Subrecord Number: 2000 Logging options (Y/N) Log State Changes : N Log All Errors : N Log All Warnings : N Log All WTOs : N Debugging Output : N Log WTO Templates: ****E__________________________________________________ Include MSGID in messages issued via SAY : N Include Time in messages issued via SAY : N ******************************** Bottom of Data *******************************



– Log State Changes: Y or N indicates whether to log information describing EMC GDDR-managed system and storage state changes to the SMF recording dataset. The default value is N.

– Log all Errors: Y or N indicates whether to log all EMC GDDR messages with a suffix of ’E' in position 8 of the message ID. The default value is N.

– Log all Warnings: Y or N indicates whether to log all EMC GDDR WTO messages with a suffix of 'W' in position 8 of the message ID. The default value is N.

– Log all WTOs: Y or N indicates whether to log all EMC GDDR WTO messages. The default value is N.

– Debugging Output: Y or N indicates whether to log to log debug and trace information when debug and trace information has been requested by program name in “Option D: Message, Debug and Trace Options” on page 135. The default value is N.

• Log WTO Templates

This specifies up to 4 message ID masks or WTO templates for the purpose of selecting specific EMC GDDR messages, or ranges of messages, to be written to the GDDR Audit Monitoring SMF dataset.

The values are specified in the form x000y x000y x000y x000y, where:

– x is the mask character for the fourth position of the 8-character message ID.

– 000 are the mask characters for the fifth through seventh positions of the 8-character message ID.

– y is the mask character for the eighth position of the 8-character message ID.

– The '*' character can be used as a single-digit wildcard.When the determination is made whether or not to write a message to the SMF log, there must be a match of at least one of the message filters. A message that matches more than one clause is processed the same as a message that matches only one filter.

• Include MSGID in messages issued via SAY

Y or N indicates whether to include the 8-character message ID with messages generated from program SAY functions. SAY functions are foreground operations. The default value is N.

• Include Time in messages issued via SAY

Y or N indicates whether to include the system time in hh:mm:ss format with messages generated from program SAY functions. SAY functions are foreground operations. The default value is N.


3. Press F6 to proceed to the Tuning Values panel.



Option T: Tuning ValuesWhen you specify option T in the Specify GDDR Options panel shown in Figure 41 on page 121, the following panel appears:

Figure 48 Tuning Values panel

When the GDDR Tuning Values panel is initially displayed, all values are blank. When you press Enter, all fields are populated with the defaults.


• Event Monitor Interval

Specify the time, in seconds, that the event monitor on each C-System waits between successive checks of the various EMC GDDR event indicators. The value must be a number between 1 and 999. The default is 20 seconds.

• Heartbeat Monitor Interval

Specify the time, in seconds, that the heartbeat monitor on each C-System waits before setting and propagating its new heartbeat value. The value must be a number between 1 and 999. The default is 30 seconds.

• Missing Heartbeat Threshold

Specify the number of times a heartbeat monitor on a C-System will need to detect no change in the heartbeat value of another C-System, upon awakening from its own wait interval, before it will declare the other C-System dead. The value must be a number from 1 to 999. The default value is 10.

• WTOR Wait Time

Specify the number of seconds that an EMC GDDR script will wait for an operator reply to a WTOR it has issued. When the specified interval has expired, the WTOR is deleted and the script proceeds as if the operator had replied 'N' or 'CANCEL' depending upon the particular message.

This parameter is optional. If not specified, the default value of 600 is used, which is equivalent to 10 minutes.

• WTOR Wait Retries:

This field is not used for SRDF/S with ConGroup configurations.

--------------------- GDDR - Specify GDDR Tuning Values ----------------------- Option ===> Press <F3> to return to the GDDR Specify Options Menu <F5> Messaging and SMF Options <F6> Parameter Management Options Menu Type <SAVE> to save, <LOAD> to restart from last saved values. Enter the required information. Press <Enter> to Validate. Event Monitor Interval: 20 (1-999, seconds, default 20) Heartbeat Monitor Interval: 30 (1-999, seconds, default 30) Missing Heartbeat Threshold: 10 (1-999, HBM cycles, default 10) WTOR Wait Time: 600 (1-3600, seconds, default 600) WTOR Wait Retries: 0 (0-999, number, default 0) HMC Reset Clear Wait Time: 15 (1-99, seconds, default 15) HMC LPAR Activation Wait Time: 5 (1-99, seconds, default 5) TimeFinder RE-ESTABLISH Wait Time: 1440 (1-9999, minutes, default 1440) TimeFinder SPLIT Wait Time: 240 (1-9999, minutes, default 240) SCFRDFM9 Cleanup Wait Time: 60 (1-600, seconds, default 60) SRDF Resynchronization Wait Time: 10 (1-30, minutes, default 10) ******************************* Bottom of Data ******************************



• HMC Reset Clear Wait Time

Specify the number of seconds that the HMC LPAR Reset Clear command will wait for confirmation that the operation completed. The value must be a number between 1 and 99. The default is 15 seconds.

• HMC LPAR Activation Wait Time

Specify the number of seconds that the HMC LPAR Activation command will wait for confirmation that the operation completed. The value must be a number between 1 and 99. The default is 5 seconds.

• TimeFinder Re-Establish Wait Time

Specify the number of minutes that are used when TimeFinder Establish commands specify a WAIT parameter. The default is 1440 minutes.

• TimeFinder Split Wait Time

Specify the number of minutes that are used when TimeFinder Split commands specify a WAIT parameter. The default is 240 minutes.

• SCFRDFM9 Cleanup Wait Time

This field is not used for SRDF/S with ConGroup configurations.

• SRDF Resynchronization Wait Time

Specify the number of minutes that GDDR waits for invalids to synchronize. The value must be a number between 1 and 30. The default is 10 minutes.


3. Press F6 to return to the Parameter Management Options Menu.

Option V: Validate GDDR Parameter SetEMC GDDR parameter validation processing determines that your proposed changes to parameter values are consistent and relationally correct. The validation operations are similar to the activation operations described in “Option A: Activate GDDR Parameter Set” on page 132, but do not update any GDDR variables.

When you specify option V in the Parameter Management Options Menu shown in Figure 8 on page 85, the Validate GDDR Parameter Set panel appears:

Figure 49 Validate GDDR Parameter Set panel

Complete the options listed in this panel to validate your parameter set.

--------------------- GDDR - Validate GDDR Parameter Set --------------------- Option ===> Options below in effect for VALIDATION Specify Options for this Parameter Set Validation : Validation in Foreground or Background : FORE (FORE,BACK) Specify GDDR Parameter Load Type : _______ (PARTIAL,FULL) Specify GDDR State Variables Action : ________ (RESET, ASIS, NOUPDATE) Propagate to Other C-systems : ___ (YES/NO/TRY) Issue one of the following commands: SAVE : Save options above as the default for your userid CANCEL : <F3> return to the GDDR Parameter Management Options Menu VAL : Proceed with GDDR Parameter Validation using options above




• Validation in Foreground or Background

– FORE: Processing occurs in TSO foreground.– BACK: Processing occurs in background as a batch job. A panel is

displayed containing the jobcard and the PROCLIB and SKELETON libraries previously specified in your personal GDDR ISPF Profile. Modify these settings if needed and then press Enter.

• Specify GDDR Parameter Load Type

– PARTIAL: Validate only the changed work-pds members. There is one work-pds member per parameter definition panel. Validation does not include contents of other members

– FULL: Validate the entire set of GDDR parameters. This is the recommended setting.

• Specify GDDR State Variables Action

– RESET: Reset all state variables to a neutral (non-error) state. This is the recommended setting.

– ASIS: Set all state variables to the values found in the input.– NOUPDATE: Do not update any state variables. This option is invalid with

Parameter Load type "FULL".• Propagate to Other C-systems

– YES: Send the updates to other C-systems. If any other C-system cannot be contacted, the action will fail. This is the recommended setting.

– NO: Do not send the updates to other C-systems.– TRY: Try to send the updates to other C-systems, but if they cannot be

contacted, continue.2. After specifying the requested options, type the Save command to save your

validation options to your TSO profile.

3. Type VAL to validate the proposed parameter definitions, or CANCEL to return to the GDDR Parameter Management Options Menu.

If Background mode is selected, the following confirmation message displays:

GDDI116I Job for Parameter Validation submitted successfully

4. Following a successful validation, press F3 to return to the Parameter Management Options Menu.

Option A: Activate GDDR Parameter SetTo complete the parameter definition and load process, you need to activate the GDDR parameter set.

IMPORTANT!Parameters required by the GDDRMAIN Event Monitor (EVM) subtask and GDDR Heartbeat Monitor may be changed during parameter activate processing. For this reason, stop the EVM subtask and GDDR Heartbeat Monitor before you perform a GDDR parameter set activation. Restart the EVM and GDDR Heartbeat monitor after the activation completes. Refer to Appendix D, “Using GDDRMAIN and the Heartbeat Monitor,” for information needed to stop/start the Event Monitor subtask and the Heartbeat Monitor.



The parameter set activation process performs the following actions:

◆ If a Planned or Unplanned script is running, verifies that the script-job is not running.

◆ Locks variables for integrity and consistency on local system.

◆ Performs and implicit backup and validate before activation.

◆ Updates variables and propagates them to other C-systems, depending on the Activate panel setting.

◆ Performs an implicit backup after activation.

◆ Clears the command queue if requested.

◆ Releases the variables.

IMPORTANT!If you are running the parameter set activate batch job with CONSISTENCY(ENFORCE) and you cancel it after it has started the load, then you may need to disable the dynamic SEC rule GDDRGVRL using CA OPSVIEW. The same is true for a parameter backup job if you are running with any CONSISTENCY option other than IGNORE. For a parameter backup job, the SEC rule name is GDDRGVBU.

After ensuring that the Event Monitor and the Heartbeat Monitor have been stopped, specify option A in the Parameter Management Options Menu shown in Figure 8 on page 85. The Activate GDDR Parameter Set panel appears:

Figure 50 Activate GDDR Parameter Set panel

Complete the options listed in this panel to activate your parameter set.


• Validation in Foreground or Background

– FORE: Processing occurs in TSO foreground.– BACK: Processing occurs in background as a batch job. This is the

recommended setting. A panel is displayed containing the jobcard and the PROCLIB and SKELETON libraries previously specified in your personal GDDR ISPF Profile. Modify these settings if needed and then press Enter.

--------------------- GDDR - Activate GDDR Parameter Set --------------------- Option ===> Options below in effect for ACTIVATION Specify Options for this Parameter Set Activation : Activation in Foreground or Background : BACK (FORE,BACK) Specify GDDR Parameter Load Type : FULL (PARTIAL,FULL) Clear the GDDR Command Queue ? YES (YES/NO) Specify GDDR State Variables Action : RESET (RESET, ASIS, NOUPDATE) Propagate to Other C-systems : YES (YES/NO/TRY) Enforce consistency : RETRY=5_ (YES/NO/RETRY(1-5) Ignore Backup Failure : NO_ (YES/NO) Issue one of the following commands: SAVE : Save options above as the default for your userid CANCEL : <F3> return to the GDDR Parameter Management Options Menu ACT : Proceed with GDDR Parameter Activation using options above



• Specify GDDR Parameter Load Type

– PARTIAL: Activates only the changed work-pds members. There is one work-pds member per parameter definition panel. Activation does not include contents of other members

– FULL: Deletes all global variables and activates the entire EMC GDDR parameter set.. This is the recommended setting.

• Clear the GDDR Command Queue

– YES: The command queue is cleared if the parameter load is successful. Use this choice for a full parameter load. This is the recommended setting.

– NO: The command queue is not cleared. This choice may be appropriate for a partial parameter load.

Note: Clearing the command queue is only done on the local system.If the choice is to clear the command queue, please use the "Manage GDDR Internal Command Queue" panel shown in Figure 53 on page 136 to clear it on the other C-systems, or use the GDDRCLRQ job provided in hlq.GDDRvrm.SAMPLIB.

If no script is in progress, the recommendation is to clear the command queue. If a script is in progress, please consult EMC GDDR Solution Support.

• Specify GDDR State Variables Action– RESET: Reset all state variables to a neutral (non-error) state. This is the

recommended setting.– ASIS: Set all state variables to the values found in the input.– NOUPDATE: Do not update any state variables. This option is invalid with

Parameter Load type "FULL".• Propagate to Other C-systems

– YES: Send the updates to other C-systems. If any other C-system cannot be contacted, the action will fail. This is the recommended setting.

– NO: Do not send the updates to other C-systems.– TRY: Try to send the updates to other C-systems, but if they cannot be

contacted, continue.• Enforce consistency

– YES: Any updates to global variables other than by parameter activate will be blocked while the backup or parameter activate is in progress. This is the recommended setting.

– NO: Outside updates to globals will be ignored.– RETRY (1-5): If an outside update occurs while parameter backup is

running, the backup will be retried the indicated number of times.• Ignore Backup Failure

– YES: If the parameter backup which is done before the parameter load fails, the parameter load will continue.

– NO: If the parameter backup which is done before the parameter load fails, the parameter load will not be done. This is the recommended setting.

2. After specifying the requested options, type the SAVE command to save your activation options to your TSO profile.

3. Type ACT to activate the proposed parameter definitions, or CANCEL to return to the GDDR Parameter Management Options Menu.

4. If Background mode is selected, the following confirmation message displays:GDDI116I Job for Parameter Activation submitted successfully



Option D: Message, Debug and Trace Options

When you specify option D in the Setup and Maintenance menu shown in Figure 7 on page 84, the following panel appears:

Figure 51 Set Output Message Levels by Program panel

This panel enables you to individually customize message, debug, and trace settings for a selected Userid and GDDR module. The defaults for these options are the settings EMC recommends for your production environment. You may be asked to make changes to the defaults if diagnostic information is needed as a result of a question or problem.

Use the ADD command to make changes to the default settings. The following panel appears:

Figure 52 Add Program to MsgLevel/Debug/Trace List panel

This panel allows the program names provided by EMC Customer Service to be specified with the requested message level, debug, or trace flags.

If the program name is less than 8 characters, extend the name with "$" signs up to a length of 8 characters.

----------------- GDDR - Set Output Message Levels By Program ---- Option ===> Scroll ===> CSR This panel shows the message, debug and trace output levels in effect for user shown. Levels on each line apply to program on that line only, while levels in parentheses are defaults applying to any program not found in the list. You may change the defaults or the levels for specific programs by overtyping. Use ADD to add a new program to the list with initial output levels. Press <F3> to save changes and return to previous panel Press <F1> for a complete description of available actions on this panel Program Msg ( 1 ) Debug ( 0 ) Trace ( 0 ) For userid: JABCD1 - -------- --- ----- ----- HMC Simulation? N ( Y or N ) ******************************* Bottom of data ********************************

--------------- GDDR - Add Program to MsgLevel/Debug/Trace List ------ Command ===> Program ===> ________ MsgLevel ===> 1 Debug Level ===> 0 Trace Level ===> 0 Enter program name (required) You may overtype default message, debug and trace levels Press <Enter> when ready to add new program to the list and return Press <F3> to return without adding a program to the MDT list



Option Q: Manage GDDR Internal Command Queue

When you specify option Q in the Setup and Maintenance menu shown in Figure 7 on page 84, the following panel appears:

Figure 53 Manage GDDR Internal Command Queue panel

WARNING

The GDDR Manage Internal Command Queue panel provides the capability to alter EMC GDDR processing. EMC advises against use of this panel unless specifically directed by EMC GDDR Customer Support.

Option H: Perform HMC DiscoveryTo discover HMC objects accessible to EMC GDDR, specify option H from the Setup and Maintenance menu shown in Figure 7 on page 84. A ‘please wait’ pop-up dialog such as the following appears and HMC object discovery is activated:

Figure 54 HMC object discovery panel

--------------------- GDDR - Manage Internal Command Queue -- Row 1 to 2 of 2Option ===> Scroll ===> PAGE WARNING: Do not use unless instructed to do so by EMC GDDR Support Total elements: 2 Active elements: 0 Maximum active: 35 Entries listed in order by command number Press <F3> to return to the GDDR Primary Options Menu Sel No RetCode Script Created Updated --- -- ------- -------- ----------------- --------------------- _ 1 152 GDD2U13A 1030200806124148 1030200812511198 SC VOL,LCL(7138,09),HDELETEPAIR(STAR,FORCE),ALL _ 2 0 GDD2U13A 1030200812511095 1030200812511273 SC VOL,LCL(7138,07),HSWAP(FORCE,STAR),ALL

---------------------- GDDR - Setup and Maintenance Menu ----------------------- Option ===> P arms Manage GDDR Parameters This System: Q311 D ebug Message, Debug and Trace options This Site: DC1 Q ueue Manage GDDR Internal Command Queue Master-C: Q311 H MC Perform HMC Discovery Primary Site: DC1 R efresh Refresh GDDR Message Table Primary DASD: DC1 S ystem Man +------- Discovering HMC Objects ---------+ | | omation: ON | Discovering HMC objects at site DC1 | script: None | | script: None | *** PLEASE WAIT *** | | | +-----------------------------------------+ EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Primary Options Menu



When the discovery operation completes, an HMC Discovery Results panel containing a scrollable display such as the following appears:

Figure 55 HMC Discovery Results panel

When you are finished examining the results of the discovery operation, press F3 to return to the Setup and Maintenance menu shown in Figure 7 on page 84.

Option R: Refresh GDDR Message TableWhen you specify option R in the Setup and Maintenance menu shown in Figure 7 on page 84, the GDDRMSG table is refreshed and the message 'GDDRMSG Table refreshed' displays in the panel:

Figure 56 Message table refresh indicator

--------------- GDDR - HMC Discovery Results --- Row 1 of 203Command ===> Enter <F3> to return to the Setup and Maintenance Menu ---------------------------------------------------------------------------GDDR Starting function Discover_HMC_Objects GDDR Using HMC IP address nnn.nnn.nnn.nnn GDDR Using optional HMC parameters -t 010000 -d 01 GDDR is Managing these (LPAR:System) for DC1 > (SYS4:SYS4) > (Z03:Z03) GDDR Checking for HMC objects at site DC1 DEBUG: GDDRC222 userid=.GDDR. DEBUG: RACFrc = 0 > SYSA:MFSYSA:1.3.6.1.4.1.2.6.42.2.0.1557483691 > SYSB:NULL:1.3.6.1.4.1.2.6.42.2.0.2395771255 > SYSC:NULL:1.3.6.1.4.1.2.6.42.2.0.3611672446 > SYSD:NULL:1.3.6.1.4.1.2.6.42.2.0.270721535 > SYSX:NULL:1.3.6.1.4.1.2.6.42.2.0.72929334 > ZOSESYS5:SYS5:1.3.6.1.4.1.2.6.42.2.0.3650884883 > ZOSESYS6:SYS6:1.3.6.1.4.1.2.6.42.2.0.2876721856 > ZOSESYS8:SYS8:1.3.6.1.4.1.2.6.42.2.0.1319236966 > ZOSESYS9:SYS9:1.3.6.1.4.1.2.6.42.2.0.2629317818 > ZOSESYS0:SYS0:1.3.6.1.4.1.2.6.42.2.0.3998444393

---------------------- GDDR - Setup and Maintenance Menu ---------------------- Option ===> P arms Manage GDDR Parameters This System: SYS1 D ebug Message, Debug and Trace options This Site: DC1 Q ueue Manage GDDR Internal Command Queue Master-C: SYS1 H MC Perform HMC Discovery Primary Site: DC1 R efresh Refresh GDDR Message Table Primary DASD: DC1 S ystem Manage GDDR System variables Automation: ON Planned script: None Unplanned script: None EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to retur +----------------------------------+ | GDDI146I GDDRMSG Table refreshed | +----------------------------------+



Option S: Manage GDDR System Variables

EMC GDDR stores parameters that describe the environment as global GDDR System Variables. With the exception of this Manage GDDR System Variables panel, updating of GDDR System Variables is under the exclusive control of EMC GDDR.

WARNING

The GDDR Manage GDDR System Variables panel provides the capability to alter EMC GDDR processing. EMC advises against use of this panel unless specifically directed by EMC GDDR Solution Support.

To view and change the values that are used by EMC GDDR, specify option S in the Setup and Maintenance menu shown in Figure 7 on page 84. A Manage GDDR System Variables panel similar to the following displays:

Figure 57 Manage GDDR System Variables panel 1

View, define, or modify the panel fields as follows:

◆ Global variable level

Specifies the name of the global variable, including the stem name of 'GLOBAL.GDDR'.

◆ Add

Type Add in the Command line at the top of the panel to display the Create GDDR System Variable panel. This panel allows you to create new variables under the direction of EMC GDDR Solution Support.

◆ Node

Global variables may have a variable number of subnodes. The Node field displays information about subnodes, such as the number of subnodes and for the lowest level nodes, their value.

◆ Actn

For each node listed in the Node field, you can specify the following line commands in the Action field:

• S—Select

If there are subnodes to the specified node, specifying the Select command shows the next level subnode as shown in Figure 58 on page 139.

--------------------- GDDR - Manage GDDR System Variables ---- Row 1 to 4 of 4 Command ===> Scroll ===> CSR Global variable level: GLOBAL.GDDR. Use the <ADD> command to create a GDDR System Variable When finished, press <F3> to return to previous level or menu Line commands: S elect, V iew, Z Delete level, D elete item Actn Node Nodes Value ------------------------------------------------------------------------------ S RUN 78 _ RUND 76 _ SCRIPT 245 _ TEMPVAR 4 ******************************* Bottom of data ********************************



• V—View

Displays information about the creation, update, and last access for the global variable.

• Z—Delete level

Deletes of all variables at or under the level shown.

• D—Delete item

Deletes just the variable at the existing level.

In this example, the Select command is issued for the RUN node, which results in the next level subnode panel as follows:


In this example, a test scenario resulted in the failure of planned script GDDRPA42, Swap production from DC1 to DC2. The GDDRPA42 node is selected, resulting in the next level subnode panel display as follows:


In this example, after resolving the cause of the script failure, the EMC GDDR Solution Support representative selects the LASTSTEP node shown in Figure 59.

--------------------- GDDR - Manage GDDR System Variables ---- Row 1 to 1 of 1 Command ===> Scroll ===> CSR Global variable level: GLOBAL.GDDR.RUN. Use the <ADD> command to create a GDDR System Variable When finished, press <F3> to return to previous level or menu Line commands: S elect, V iew, Z Delete level, D elete item Actn Node Nodes Value ------------------------------------------------------------------------------ S GDDRPA42 78 ******************************* Bottom of data ********************************

--------------------- GDDR - Manage GDDR System Variables -- Row 1 to 13 of 77 Command ===> Scroll ===> CSR Global variable level: GLOBAL.GDDR.RUN.GDDRPA42 Use the <ADD> command to create a GDDR System Variable When finished, press <F3> to return to previous level or menu Line commands: S elect, V iew, Z Delete level, D elete item Actn Node Nodes Value ------------------------------------------------------------------------------ _ CALLOVER 0 01111110011010011111 _ GDDRCBU2 1 _ GDDRDY01_RUN_RD+ 1 _ GDDRDY01_RUN_

Scroll <Down> to the LASTSTEP variable

_ GDDRGFHS_DC1 _ GDDRXDRV_01_A _ GDDRXDRV_02_S _ GDDRXDRV_02_S _ GDDRXDRV_03_SYN+ 1 _ GDDRXDRV_04_SYN+ 1 S LASTSTEP 0 30



The Manage GDDR System Variables - Detail panel appears as shown in Figure 60. In this example, this panel indicates the value of GLOBAL.GDDR.RUN.GDDRPA42.LASTSTEP. The EMC GDDR Solution Support representative could edit the value by overtyping the Value field to be 1 greater than the current value. This change enables the script to be restarted at the step following the failing step.

Figure 60 Manage GDDR System Variables - Detail panel 1

The View command displays information about the creation, update, and last access for the global variable as shown in Figure 61.

Figure 61 Manage GDDR System Variables - Detail panel 2

+-----------------------------------------------------------------------------+ | ----------------- GDDR - Manage GDDR System Variables - Detail ------------ | | Command ===> | | More: | | Name: GLOBAL.GDDR.RUN.GDDRPA42.LASTSTEP | | | | | | | | Value: 30_______________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | +-----------------------------------------------------------------------------+

+-----------------------------------------------------------------------------+ | ----------------- GDDR - Manage GDDR System Variables - Detail ------------ | | Command ===> | | More: | | Value: 30_______________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________________________ | | _________________________________________________ | | Created 2009/06/28 13:44:06 by GDDRPA42 (Job GDDRPA42 ) | | Updated 31 times, last 2009/06/28 14:38:04 by GDDRPA42 ( GDDRPA42 ) | | Last accessed 2009/06/30 | +-----------------------------------------------------------------------------+



Option G: GDDR Config—View GDDR ConfigurationSpecify option G in the Primary Options menu (Figure 5 on page 80) to view your configuration settings. The following panel appears:

Figure 62 View GDDR Configuration panel

--------------------------- View GDDR Configuration ---------------- Command ===> Sites: DC1, DC2 Features: SRDF/S, No FBA Devices C-Systems: At DC1, C-System is SYS4 with MSF id SYS4 At DC2, C-System is SYS3 with MSF id SYS3 Press <F3> to return to the previous menu

Option G: GDDR Config—View GDDR Configuration 141


Option R: Roles—Manage Site RolesEMC GDDR script processing manages the location of the Master C-System, the AutoSwap Owner system, and the MSC Control site as part of normal operations. The Manage Site Roles panel is provided to address exception conditions such as preparing for a script restart.

Specify option R in the Primary Options menu (Figure 5 on page 80) to access the Manage Site Roles panel.

Note: The Manage Site Roles panel is displayed conditionally for users who are authorized to manage site roles.

Figure 63 Manage Site Roles panel

Select the desired transfer type by entering the abbreviation in the Option line, or typing S in the command field.

◆ MXFR: Transfer Master C-System function

Selecting the Transfer Master C-System function returns the following panel:

Figure 64 Master C-System Transfer panel

Based on the current EMC GDDR parameters, site DC1 is the Current Master C-System and is the recommended site for the Master C-System based on the parameters. No action is recommended. Press F3 to return to the Manage Site Roles panel.

-------------------------- GDDR - Manage Site Roles -------------------------- Option ===> MXFR Transfer Master-C system function This System: SYS1 MVAS Move AutoSwap owner Not Applicable This Site: DC1 MMSC Move MSC control function Not Applicable Master-C: SYS1 Primary Site: DC1 Primary DASD: DC1 Automation: ON Planned script: None Unplanned script: None Select an option and press <Enter> Press <F3> to exit

---------------------- GDDR - Master C-System Transfer ----------- Row 1 of 2 Option ===> Press <F3> to return to the Manage Site Roles panel Select a row to transfer the Master C-System to that site/system. CMD Site C-System MSF MHB Notes --- ---- -------- --- --- ------------------------------------------- _ DC1 SYS1 0 0 Current Master, Recommended Master, This sys _ DC2 SYS7 93 0 ******************************* Bottom of data ********************************



Option C: Checkup—Perform Pre-script CheckupSpecify option C in the Primary Options menu (Figure 5 on page 80) to invoke the EMC GDDR on-demand Health Check. A panel similar to the following displays the items that are validated.

WARNING

Selecting the Perform Pre-script Checkup option may lock up your terminal for several minutes. The time required for the initial status display will vary as a function of the number of systems in the configuration and the presence of communication issues.

Figure 65 Perform Health Check panel

The Perform Health Check panel returns the following information:

◆ Active Events

Indicates any exceptions to conditions monitored by the EMC GDDR Event monitor.

◆ Command Queue

Indicates the current command queue status and size. EMC GDDR uses an internal command queue to perform operations.

◆ System Communication Status

Specifies the systems that comprise your installation. This field lists the target system, the site where the system resides, and whether the specified system is a GDDR C-System (CSYS) or GDDR managed production system, (PSYS). A check is made of the inter-system communications that GDDR uses and the results are displayed in the status columns. Communication types are as follows:

• CSC Status

Indicates the CSC status. EMC GDDR uses the Cross System Communication (CSC) feature of the EMC ResourcePak Base for z/OS product to communicate information across LPARs.

------------------ GDDR - Perform Health Check -------------- Row 1 to 4 of 10Command ===> Scroll ===> CSR Active Events: CGD CGT ECA MSC SRA Command Queue Status Job Count Active Free Max ------- -------- ------ ------ ------ ------ In Use 1 0 0 35 System Communication Status: Target CSC MSF HMC Sel Site System Type Status Status Status --- ---- -------- ---- ------- -------- --------- _ DC3 Q31B CSYS Waiting Active Operating _ DC1 PRD1 PSYS Waiting n/a Error _ DC1 Q311 CSYS Waiting n/a n/a _ DC1 TST1 PSYS Waiting n/a Error

Option C: Checkup—Perform Pre-script Checkup 143


• MSF Status

Indicates the MSF status. EMC GDDR uses the CA-OPS/MVS Multi-System Facility (MSF) for maintaining consistent information across C-Systems.

• HMC Status

Indicates the HMC status.EMC GDDR uses the z/OS Hardware Management Console (HMC) to maintain and view its managed systems, issue operator commands, and to discover HMC objects.

Health Check monitoringThe GDDR Event monitor checks for the following storage and system environment events:

When the GDDR Event Monitor detects any of the events listed in Table 10, it issues the following message:

GDDS027W GDDR Warning: Event full_event_id detected, value event_value

For example:

GDDS027W GDDR Warning: Event GLOBAL.GDDR.DCN.Unplanned.C>> detected, value 1

Health Check monitoring exception notificationNotification of Health Check monitoring exceptions can easily be implemented using a number of third-party system management software products which perform event notification tasks. The EMC z/OS Storage Manager product (EzSM), offers event notification through its Alert Definitions capability.

The following is a brief description of the steps required within EzSM to configure an alert on the occurrence of a GDDR event exception:

1. Establish Notification Directory entries for individuals or groups that are to be notified when an exception occurs. These entries include:

• First and last name

• TSO ID

Table 10 Monitoring events

Event Description

CGD: Congroup Disable ConGroup has been disabled.

CGT: Congroup Trip ConGroup trip has occurred.

RDR: Regional Disaster DC1 outage has occurred.

ECA: Enginuity Consistency Assist Enginuity Consistency Assist has been disabled.

MSF: MSF Link Down The OPS MSF link to the LPAR, (indicated after the MSF value), is not available.

MHB: Missing Heartbeat One or more C-Systems has failed to issue a heartbeat in a specific time window.

LNK.DCnVDCn: RDF Link Down The RDF link between the specified sites is unavailable.

LDR: Local Disaster A single site outage has occurred.



• Email address

• Short Message Service (SMS) ID

2. Establish an Alert on the GDDS027W message ID.

When creating the Alert, the contact information for the individuals or groups who are to be notified must be in the Notification Directory.

Note: The Alert Definitions topic in the EMC z/OS Storage Manager Product Guide provides additional details.

Additional pre-script environment checks

Before you initiate any planned swap scenarios, EMC recommends that you make the following manual checks:

◆ Verify that ConGroup is active and enabled

The initial check is also performed automatically by EMC GDDR.

EMC recommends that you perform these checks manually before you run any EMC GDDR swap scripts to make sure that everything is active. The checks are designed to avoid possible problems later.

The following sections discuss these checks.

Verify that ConGroup is active and enabledEnter the following command from the EMC GDDR Master C-System:

F EMCCGRP,D C

where:

EMCCGRP

Is the name of the EMC Consistency Group for z/OS (ConGroup) started task.



Expected outputFigure 66 shows a sample of the expected output of this operation.

Figure 66 Consistency group status display output

02.16.42 STC02786 CGRP282I D C 033 033 *** Begin Display from system Q311 *** 033 GLOBAL SETTINGS: 033 COUPLEDS_ALLOWED=YES 033 DISABLE_AT_SHUTDOWN=ON 033 PAGEDEV_ALLOWED=YES 033 REMSPLIT_INTERVAL=10 033 RESUME_INTERVAL=10 033 SEMISYNC_ALLOWED=NO 033 SRDFCGP= CG74TIGB ENABLED ACTIVE 033 SYNCLINKFAILURE=NO 033 TRIPPABLE=YES 033 USE_RDF_ECA=YES 033 USE_FBA_NR_ON_TO=YES 033 POLLRATE=15 033 SUSPEND_FAILURE=RETRY SUSPEND_RETRY_TIMEOUT=30 033 Grp Hash=00001B37 033 This is an AutoSwap group 033 CTLR SER#=000192601314 58740145 033 +-----------------------------------------------------+ 033 | R1 | R1 |Volser|Rdf-| CG |Sync|InvT|RA GRP/Mirr| NR | 033 |Cuu |Dev#|or oth|1234|1234|1234|1234| 1 2 3 4|1234| 033 +-----------------------------------------------------+ 033 |B214|0064|TA2064|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B215|0065|TA2065|.A..|.E..|.S..|....|..|25|..|..|....| 033 |B220|0070|TA2078|.A..|.E..|.S..|....|..|25|..|..|....| 033 |B221|0071|TA2079|.A..|.E..|.S..|....|..|25|..|..|....| 033 |B222|0072|TA207A|.A..|.E..|.S..|....|..|25|..|..|....| 033 |B223|0073|TA207B|.A..|.E..|.S..|....|..|25|..|..|....| 033 |B230|0080|TA2088|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B231|0081|TA2089|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B232|0082|TA208A|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B233|0083|TA208B|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B238|0088|TA2070|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B239|0089|TA2071|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B23A|008A|TA2072|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B23B|008B|TA2073|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B23C|008C|TA2074|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B23D|008D|TA2075|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B23E|008E|TA2076|.A..|.E..|.S..|....|..|15|..|..|....| 033 |B23F|008F|TA2077|.A..|.E..|.S..|....|..|15|..|..|....| 033 |....|5F50|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F51|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F52|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F53|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F54|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F55|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F56|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F57|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F58|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F59|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F5A|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F5B|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F5C|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F5D|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F5E|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 |....|5F5F|......|.A..|.E..|.S..|....|..|25|..|..|....| 033 +-----------------------------------------------------+ 033 Group Summary: 033 +-----------------------------------------------------+ 033 | CG | CAX | RECA | TNR | Dev# | Invt | 033 +-----------------------------------------------------+ 033 ENABLED Y/DFINED Y/ARMED NONE 34 0 033 *** End Display from system



What to look forThe resulting display from the command issued previously will show the consistency group as Enabled and Active and each device in the consistency group must show as ARMeD and Enabled.

There is a problem if the group is not in the expected state or one or more devices are not in the expected state.

What to do if ConGroup is not active and enabled Take the following actions if any of the checks are fail:

◆ Report the problem to your z/OS systems programming support group.

◆ Do not start the swap.



Option S: Scripts—Run GDDR ScriptsWhen you specify option S in the Primary Options Menu shown in Figure 5 on page 80, a panel similar to the following displays:

Figure 67 Select Script to Run panel

The Select Script to Run panel is a dynamic display. It lists EMC GDDR scripts that are eligible to run under your configuration, and also specifies configuration information and scripts that are in progress, if any. Depending on the location of the primary site and primary DASD locations, the panel is customized to display valid choices. Scripts that you cannot use at your current site do not appear.

The scripts eligible to run are grouped in categories, with header rows indicating the category of scripts that follow. The following fields are provided on the Select Script to Run panel:

Configuration

This field indicates the features of your configuration that EMC GDDR takes into account when determining which scripts are eligible to run and hence which are present in the list of scripts displayed on your panel.

Scripts listed

For a header row, the scripts field contains a description of the category of scripts which follow. For a script row, this field contains a description of the script.

Status

This field is initially blank. When you have selected a script to run, the status field for the script row indicates the job name and number of the run request.

Commands

S – To request that a script be run or rerun, type S next to the row describing the script you want to run and press Enter.

----------------- GDDR - Select Script to Run ---------------- Row 1 to 11 of 11Command ===> Scroll ===> CSR Enter S next to script to run and press <Enter> Current Master: SYS3 Press <F3> to return to previous menu Primary Site: DC1 Press <F1> to view all available commands Primary DASD: DC1 Configuration: 2 SITES, SRDF/S CONGROUP Automation: ON Sel ----------------------- Scripts ---------------------- ----- Status ----- ============ Scripts for Planned Actions ============= _ Abandon Site DC1 (site swap) GDD2P17A _ Restart production at DC2 after site swap GDD2P18A _ Perform test IPL from BCVs at DC2 GDD2P01A _ Perform test IPL from R2s at DC2 GDD2P03A =========== Scripts for Unplanned Actions ============ _ Recover after loss of DC1 (LDR) GDD2U10A _ Resume replication after loss of DC1 GDD2PA0A Note: Conditional upon Last run script = GDD2U10A ============== Scripts for Resumption ================ _ Resume after test IPL from BCVs at DC2 GDD2P02A _ Resume after test IPL from R2s at DC2 GDD2P16A _ Resume replication after link failure GDD2P14A ******************************** Bottom of data *******************************



D – Use the Display Script Details command to return the program name for the script and the name of the script skeleton. Type D next to the row describing the script and press Enter.

Option S: Scripts—Run GDDR Scripts 149


Option T: Timing—View GDDR Script StatisticsWhen you specify option T in the Primary Options Menu shown in Figure 5 on page 80, the panel that appears depends on the current status of the selected script.

If a script is currently running, a panel similar to the following appears:

Figure 68 Script Selection for Status panel

Type S next to a script to select it for viewing:

◆ If the selected script is currently running, a panel similar to the following appears:

-------------- GDDR Operation - Script Selection for Status Vi Row 1 to 4 of 4 Option ===> Enter S next to a script to select it for viewing Press <F3> to return to Operator Primary Option Menu Last planned: Resume replication after link failure Last unplanned: (none) Script - ------------------------------------------------------------ _ GDD2P17A - Abandon Site DC1 (site swap) _ GDD2P18A - Restart production at DC2 after site swap S GDD2P14A - Resume replication after link failure Last planned ******************************* Bottom of data ********************************

------------------- View Script Step Results Row 1 to 7 of 37 Option ===> Script: GDD2P14A: Resume replication after link failure Initial: 11/20/2007 at 09:06:29.96 Iterations: 1 Maximum return code: 0 Last run started 11/20/2007 at 10:09:27.44 and still running Function Subfunction RC Step start/end Cnt -------- ------------------------- -- ---------------------- --- GDDRKF0A broadcast global variables 0 at at GDDRGF0L Prompt_Operators_4_Conf 0 at at GDDRKF0A Verify_SRDFS_Down GL at at GDDRGF08 Perform_EMCCGRP_Shutdown GL at at GDDRKF13 Clean_CG_Devices for R2's 0 at at GDDRGF0J source_site SYNCHDIR J0 GL at at GDDRKF21 0 at



◆ If a script is completed, a panel similar to the following appears:

------------------ View Script Step Results Row 30 to 37 of 37 Option ===> Script: GDD2P14A: Resume replication after link failure Initial: 11/19/2007 at 04:16:37.14 Iterations: 1 Maximum return code: 32 Last run started 11/19/2007 at 04:16:37.14 ended 11/19/2007 at 04:16:37.28 Function Subfunction RC Step start/end Cnt -------- ------------------------- -- ---------------------- --- GDDRGF4P 2_J0_RDFGRP_GNS 0 11/19/07 at 04:23:39.79 1 11/19/07 at 04:23:53.09 GDDRGF4P 2_J0_RDFGRP_GNS 0 11/19/07 at 04:23:53.78 1 11/19/07 at 04:23:58.11 GDDRKF0G Toggle_ConGroup_Groups 0 11/19/07 at 04:23:58.81 1 11/19/07 at 04:26:48.71 GDDRGF0G Refresh_ConGroup_Groups 0 11/19/07 at 04:26:49.40 1 11/19/07 at 04:29:46.31 GDDRGF09 Perform_EMCCGRP_Startup * 11/19/07 at 04:29:46.99 1 at GDDRKF21 Manage_BCVs RE-ESTABLISH * 11/19/07 at 04:29:47.80 1 at GDDRKF0A Propagate_Global_Variables * 11/19/07 at 04:29:49.59 1 at

Option T: Timing—View GDDR Script Statistics 151


Option A: Actions—Perform GDDR ActionsSpecify option A in the Primary Options Menu (Figure 5 on page 80) to access the GDDR Actions Menu:

Figure 69 GDDR Actions Menu

Option H: Perform HMC Discovery

To discover HMC objects accessible to EMC GDDR, specify option H from the GDDR Actions menu. A ‘please wait’ pop-up dialog such as the following appears and HMC object discovery is activated:

Figure 70 HMC object discovery panel

--------------------------- GDDR - Actions Menu ----------------------------- Option ===> H Perform HMC Discovery This System: SYS1 L Perform HMC LPAR Actions This Site: DC1 CBU Perform HMC CBU Actions Master-C: SYS1 S Manage Couple Datasets Primary Site: DC1 Primary DASD: DC1 Automation: ON Planned script: None Unplanned script: None EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Primary Options Menu

----------------------------- GDDR - Actions Menu ----------------------------- Option ===> H Perform HMC Discovery This System: SYS1 L Perform HMC LPAR actions This Site: DC1 CBU Perform HMC CBU actions Master-C: SYS1 S Manage Couple Datasets Primary Site: DC1 Primary DASD: DC1 +------- Discovering HMC Objects ---------+ | | omation: ON | Discovering HMC objects at site DC1 | script: None | | script: None | *** PLEASE WAIT *** | | | +-----------------------------------------+ EMC Geographically Dispersed Disaster Restart 03.01.00 Copyright © 2007-2009 EMC Corporation Select an option and press <Enter> Press <F3> to return to the GDDR Primary Options Menu



When the discovery operation completes, an HMC Discovery Results panel containing a scrollable display such as the following appears:

Figure 71 HMC Discovery Results panel

When you are finished examining the results of the discovery operation, press F3 to return to the GDDR Actions menu.

--------------- GDDR - HMC Discovery Results --- Row 1 of 203Command ===> Enter <F3> to return to the Actions Menu ---------------------------------------------------------------------------GDDR Starting function Discover_HMC_Objects GDDR Using HMC IP address nnn.nnn.nnn.nnn GDDR Using optional HMC parameters -t 010000 -d 01 GDDR is Managing these (LPAR:System) for DC1 > (SYS4:SYS4) > (Z03:Z03) GDDR Checking for HMC objects at site DC1 DEBUG: GDDRC222 userid=.GDDR. DEBUG: RACFrc = 0 > SYSA:MFSYSA:1.3.6.1.4.1.2.6.42.2.0.1557483691 > SYSB:NULL:1.3.6.1.4.1.2.6.42.2.0.2395771255 > SYSC:NULL:1.3.6.1.4.1.2.6.42.2.0.3611672446 > SYSD:NULL:1.3.6.1.4.1.2.6.42.2.0.270721535 > SYSX:NULL:1.3.6.1.4.1.2.6.42.2.0.72929334 > ZOSESYS5:SYS5:1.3.6.1.4.1.2.6.42.2.0.3650884883 > ZOSESYS6:SYS6:1.3.6.1.4.1.2.6.42.2.0.2876721856 > ZOSESYS8:SYS8:1.3.6.1.4.1.2.6.42.2.0.1319236966 > ZOSESYS9:SYS9:1.3.6.1.4.1.2.6.42.2.0.2629317818 > ZOSESYS0:SYS0:1.3.6.1.4.1.2.6.42.2.0.3998444393

Option A: Actions—Perform GDDR Actions 153


Option L: Perform HMC LPAR Actions

HMC actions are console operations affecting a processor, such as Load (IPL) or System Reset, or operations affecting an LPAR, such as Activate LPAR. When you select Option L - Perform HMC LPAR Actions from the GDDR Actions menu, you are presented with the following panel:

Figure 72 Perform HMC LPAR Actions panel

On the Perform HMC LPAR Actions panel, each row may show a load address and a load parameter or asterisks (the asterisks indicate that load addresses or parameters have not been defined for that LPAR). You may enter an action code on any row for a system-site combination. The action you enter will be taken against the system or the system’s LPAR using the site named on the selected row.

Field descriptionsThe values displayed in the HMC LPAR Actions panel are defined in the Define Managed Systems panel shown in Figure 29 on page 107 and the Define IPL Parameters panel shown in Figure 32 on page 112. The following informational fields are conditionally displayed on the HMC LPAR Actions panel for EMC GDDR users who are authorized to perform HMC actions:

Sel

Specify the action code for the action you want to perform for the system-site combination appearing on the row.

System

Indicates the name of the system associated with the table row.

Site

Identifies the site through which the action you specify will be taken against the system named on the row.

Load address

Contains the MVS device address of the load device if you specify an action which performs a Load as part of its operation (for example, Load-Clear).

Load parms

Contains the parameter used for the Load if you specify an action which performs a Load as part of its operation (for example, Load-Clear).

---------------------- GDDR - Perform HMC LPAR Actions ----------- Row 1 of 3 Command ===> Scroll ===> CSR These actions may be performed: Current Master: SYS3 A Activate Lpar Primary Site: DC1 D Deactivate Lpar Primary DASD: DC1 L Load Clear Automation: ON R Reset Clear Planned script: None P Stop Unplanned script: None S Start Q Query Lpar Type action to perform next to the desired system and site and press <Enter> When finished, press <F3> to return to the Operator Primary Options Menu Sel System Site Load Address Load Parm Message --- ------- ---- ------------ --------- ---------------------------------- _ SYS1 DC1 7040 704312M1 _ SYS4 DC1 7000 7004D1M1 _ SYS2 DC2 7050 704310M1 ******************************* Bottom of data ********************************



Message

This field is initially blank, but will show a status message if applicable.

Actions you can requestTo request an HMC action, enter the action code on the command line and press Enter.

Activate

To activate the LPAR of the selected system, type A next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by entering Y and pressing Enter, or cancel the request by pressing F3.

Deactivate

To deactivate the LPAR the selected system runs in, type D next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by typing Y and pressing Enter, or cancel the request by pressing F3.

Load Clear

To clear and load a selected system using the displayed load address and load parameters, type L next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by typing Y and pressing Enter, or cancel the request by pressing F3.

Reset Clear

To reset and clear a selected system, type R next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by typing Y and pressing Enter, or cancel the request by pressing F3.

Stop

To stop a selected system, type P next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by typing Y and pressing Enter, or cancel the request by pressing F3.

Start

To start a selected system, type S next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by typing Y and pressing Enter, or cancel the request by pressing F3.

Query

To query the LPAR of the selected system, type Q next to the selected system and press Enter. A confirmation pop-up will be displayed. Confirm the request by typing Y and pressing Enter, or cancel the request by pressing F3.



Option CBU: Perform HMC CBU actions

When you specify option CBU in the GDDR Actions menu, the following panel displays:

Figure 73 Perform CBU Actions panel

Each row represents a site with a processor enabled for CBU (Capacity Backup Upgrade) activation.

Type one of the following action codes next to the desired site/CPC pair:

◆ A to activate backup capacity on the specified processor (REAL mode)

◆ B to simulate the activation of backup capacity on the specified processor (TEST mode)

◆ C to undo or terminate actual backup capacity activation

◆ D to undo or terminate a simulation of backup capacity activation

Option S: Manage Couple Datasets

When you specify option S in the GDDR Actions menu, the following panel displays:

Figure 74 Manage Couple Datasets panel

In environments with geographically dispersed sysplexes supported by cross-site host-DASD channels, this function can be used to drive the process of checking the

-------------------------- GDDR - Perform CBU Actions ------------- Row 1 of 6 Command ===> Scroll ===> CSR Type one of the following action codes next to desired site/CPC pair A activate CBU in REAL mode B activate CBU in TEST mode C Undo CBU in REAL mode D Undo CBU in TEST mode When ready, press <Enter> to perform the action You may press <F3> to return to the Operator Primary Options Menu Sel Site CPC Message --- ---- -------- --------------------------------------------------- _ DC1 X0 _ DC1 X0 _ DC1 X1 ******************************* Bottom of data ********************************

------------------------ GDDR - Manage Couple Datasets ------------------------ Command ===> Specify the site for which couple datasets are to be configured. Site ===> _ Use 1 for site DC1, 2 for site DC2 Specify the type of script for which the couple datasets are intended. Script type ===> _ Use P for planned scripts, U for unplanned scripts Enter or change the job statement: //JABCDE1I JOB (0),'PARMVAL',MSGLEVEL=(1,1),CLASS=A,MSGCLASS=X, // NOTIFY=&SYSUID /*JOBPARM LINES=999999 // Press <Enter> when ready. Press <F3> to return without submitting job.



couple dataset configurations on all systems. Currently used couple datasets are compared against those specified in the panel shown in Figure 36, “Define Managed Couple Datasets panel 2 of 2,” on page 116. If discrepancies are found, SETXCF commands are issued to bring couple dataset usage in line with EMC GDDR parameter specifications.

Note: Site Swap scripts also include steps to align the couple datasets with managed couple dataset parameters. The Define Manage Couple Datasets panel provides the capability to adjust couple datasets when it is not suitable to run a Site Swap script.



Option O: OPS—Access CA-OPS/MVS

Note: Many installations provide option OPS on the TSO Primary Options menu for this purpose. Your installation may provide a different method for reaching the CA-OPS/MVS OPSVIEW Primary Options menu.

Figure 75 CA-OPS/MVS OPSVIEW Primary Options panel

Note: The ability to access CA-OPS/MVS from with the GDDR ISPF interface is subject to user authorization as described in “Specify EMC GDDR security” on page 54.

CA-OPS/MVS ------ SYS2 --- OPSVIEW Primary Options Menu ----- Subsystem OPSS Option ===> 0 Parms Set OPSVIEW and ISPF default values User ID - GDDUSR1 1 OPSLOG Browse OPSLOG Time - 12:08 2 Editors AOF Rules, REXX programs, SQL Tables Release - 11.6 3 Sys Cntl Display/Modify System Resources SP - 0 4 Control Control CA-OPS/MVS 5 Support Support and Bulletin Board information 6 Command Enter JES2/MVS/IMS/VM commands directly 7 Utilities Run CA-OPS/MVS Utilities A AutoMate Unicenter CA-AutoMate rules edit and control I ISPF Use ISPF/PDF services S SYSVIEW Unicenter CA-SYSVIEW T Tutorial Display information about OPSVIEW U User User-defined applications X Exit Exit OPSVIEW Unicenter CA-OPS/MVS Event Management and Automation Copyright © 2008 CA. All rights reserved. Press END or enter X to terminate OPSVIEW



Using OPSVIEW facilities for EMC GDDR administrationEMC GDDR is a CA-OPS/MVS user application. While it is not normally necessary, you will occasionally need to perform certain EMC GDDR administration functions through CA-OPS/MVS OPSVIEW. Overviews of the most important of these functions are given below. Additional details are available in the OPS-MVS Event Management and Automation - OPSVIEW User Guide included on the Unicenter CA-OPS/MVS Documentation CD.

For all the functions, it is assumed that you have reached the CA-OPS/MVS OPSVIEW Primary Options menu as shown in Figure 75 on page 158.

Ensuring MSF connections between C-SystemsSelect option 4 – Control on the OPSVIEW Primary Options menu and press Enter. Then, on the OPSVIEW Control menu that is displayed, select option 2 - MSF Control and press Enter to reach the OPSVIEW Multi-System Facility panel.

Using OPSVIEW facilities for EMC GDDR administration 159



5Invisible Body Tag

This chapter describes the scripts that you can run from the EMC GDDR Operator Interface.

◆ Running scripts............................................................................................................ 162◆ Planned script operations .......................................................................................... 167◆ Unplanned script operations ..................................................................................... 168◆ Resumption operations .............................................................................................. 169

Performing ScriptOperations

Performing Script Operations 161

Performing Script Operations

Running scriptsEMC GDDR allows you to run the following types of scripts:

◆ Planned actions

◆ Unplanned actions

◆ Resumption of actions

Take the following steps to use any of these scripts:

1. Navigate to the Select Script to Run panel as shown in “Option S: Scripts—Run GDDR Scripts” on page 148.

2. Select the script you want by typing S next to the script and pressing Enter.

Note: If another script is currently in progress, a message similar to the following appears on the Select Script to Run panel:

Script GDD2P14A is in progress. Only the script in progress may be submitted at this time.

3. If no script is in progress, the Specify Parameters for Initial Script Run panel appears:

Figure 76 Specify Parameters for Initial Script Run panel

4. You can then confirm or clear any of the call overrides that apply to this script by entering Y in "Specify call override changes for this script?”

--------------- GDDR - Specify Parameters For Initial Script Run --------------- Command ===> Selected script: Swap production from DC2 to DC1 Enter or change the job statement below: //* //* //* //*

Specify call override changes for this script? ===> N Enter Y or N Press <Enter> when ready to submit script job Press <F3> to return to menu without submitting job



A series of Specify Call Overrides panels similar to the following appears:

Figure 77 Specify Call Overrides panel (screen 1 of 2)

Figure 78 Specify Call Overrides panel (screen 2 of 2)

The Specify Call Overrides panel provides help information (accessed by pressing PF1) that describes the function of each program. Use PF3 to return to the Specify Call Overrides panel.

Note: All call overrides do not apply to all scripts. For any script you run, you normally see a subset of the possible call overrides.

You can overtype the default "Y" or "N" call override values for this script. (Table 11 on page 165 lists the possible call overrides and their meanings.)

Note: You can specify call overrides only once for each execution of a script. If a script terminates before completion, you can rerun the script (as discussed in “Rerunning a script” on page 166), but any changes you make to the call overrides will be ignored. However, when you execute the same script again after it successfully completes, you can specify call overrides for it.

----------- GDDR - Operations - Specify Call Overrides For Row 1 to 11 of 19 Script: Restart production at DC2 after site swap Current Master: SYS4For each row, you may change the call indicator: Primary Site: DC1 Enter Y to call the function Primary DASD: DC1 Enter N to not call the function Automation: ON When ready, press <F3> to continue the script submit process Enter CANCEL and press <Enter> to terminate the script submit process Call? Program Function ----- -------- ------------------------------------------------- Y GDDRDY01 Call DYNAPI Interface Y GDDRGF2P DYNAPI - Issue SRDF/S HSWAP Commands Y GDDRKF0U DYNAPI - Half_DeletePair_DC3_and_Old_Primary Y GDDRKF0W DYNAPI - Create Star SRDFA Pairs Y GDDRGF0J DYNAPI - Issue Commands To JA RDF Group Y GDDRKF43 DYNAPI - Perform Personality Swap Y GDDRGF08 Use ConGroup Shutdown/Startup instead of Refresh N GDDRKF0C Trigger Production System Shutdown N GDDRKF0I Trigger Production System Startup N GDDRKF21 (Scan Mode) - Manage_BCVs

------------ GDDR - Operations - Specify Call Overrides For Row 12 to 18 of 18 Script: Restart production at DC2 after site swap Current Master: SYS4For each row, you may change the call indicator: Primary Site: DC1 Enter Y to call the function Primary DASD: DC1 Enter N to not call the function Automation: ON When ready, press <F3> to continue the script submit process Enter CANCEL and press <Enter> to terminate the script submit process

Call? Program Function ----- -------- ------------------------------------------------- N GDDRTNG1 GDDRTNG1 Y GDDRKF0H Transfer Master Function Ownership N GDDRKF21 (DC1) - Manage_BCVs N GDDRKF21 (DC2) - Manage_BCVs N GDDRKF21 (DC3) - Manage_BCVs N GDDRCL00 Perform SDDF Session Cleanup N GDDRRDF0 Manage non-Star devices ******************************* Bottom of data ********************************

Running scripts 163


5. When you are finished, press F3 to return to the Specify Parameters for Initial Script Run panel. Then press Enter to continue.

Result: A pop-up similar to the following appears and you are prompted twice to confirm job submission.

Figure 79 Confirm Job Submission panel

6. At each prompt, reply Yes to confirm or No to terminate job submission.

Result: After EMC GDDR receives both confirmations, it submits the job to start the selected planned script. Upon starting, you are prompted (through WTOR) to confirm that you want to run the script.

7. Reply Yes to allow the script to continue or No to terminate the script.

+----------- Please Confirm Job Submission -----------+| Command ===> || || Abandon Site DC1 (site swap)........................|| || Please confirm submit of this script || || Submit script? ===> N Reply Y or N || |+-----------------------------------------------------+



Call overrides

Table 11 lists the call overrides that you may see when running a script. All call overrides do not apply to all scripts. For any script you run, you normally see a subset of the possible call overrides.

Table 11 EMC GDDR call overrides (1 of 2)

Program Function

GDDRDY01 Call_DYNAPI_Interface Performs “LOAD” or “RUN” request of SRDF Host Component commands to or from the GDDR command queue using Dynamic API function code FC01.

GDDRGF2P DYNAPI - ISSUE_COMMANDS_2_J0_RDFGRPAllows SRDF Host Component “HSWAP” command to devices on the synchronous SRDF link to be performed using DYNAPI rather than as a native SRDF Host Component command during unplanned script.

GDDRKF43 DYNAPI - Perform_Personality_Swap_GNSAllows SRDF Host Component “SWAP” command to devices on the synchronous SRDF link to be performed using DYNAPI rather than as a native SRDF Host Component command during planned GDDR scripts.

GDDRGF08 Perform_EMCCGRP_ShutdownPerforms shutdown of EMC Consistency Group STC on all LPARs. Choice of this option is mutually exclusive with that of “GDDRKF0G (Refresh) - HANDLE_CONGROUP_GROUPS.”

GDDRGF09 Perform_EMCCGRP_StartupPerforms startup of EMC Consistency Group STC on all LPARs. Restart will activate the new EMC Consistency Group as defined. by the current source (R1) devices in the ConGroup CONFIG DD. Choice of this option is mutually exclusive with that of “GDDRKF0G (Refresh) HANDLE_CONGROUP_GROUPS.”

GDDRKF0C TRIGGER_PRODUCTION_SYSTEM_SHUTDOWNCalls user exit GDDRXDRV to synchronously stop all production system application workloads.

GDDRKF0I TRIGGER_PRODUCTION_SYSTEM_STARTUPCalls user exit GDDRXDRV to asynchronously start all production system application workloads.

GDDRKF0G (Refresh) - HANDLE_CONGROUP_GROUPSPerforms “REFRESH” of EMC Consistency Group to activate the new consistency group as defined by the current source (R1) devices defined in the EMC Consistency Group CONFIG DD. Choice of this option is mutually exclusive with those of GDDRGF08 and GDDRGF09 - EMCCGRP Startup & Shutdown.

GDDRKF21 (Scan Mode) - Manage_BCVsPerform BCV actions in simulation mode.

GDDRTNG1 GDDRTNG1Generates an OPS/MVS alert and call GDDRXDRV exit with message.

Running scripts 165


Rerunning a scriptIf any step of a script completes with a nonzero return code, the script terminates. The reason for the failure must be investigated and resolved. You can find a description of the GDDR639I message you receive and the return codes that can accompany it in the EMC GDDR Message and Code Guide.

After the cause of the failure has been resolved, submit the script again. No JCL changes are required. EMC GDDR determines the correct step from which to resume scripting.

Depending on how the issue was resolved, it may be necessary to skip the failing step. Refer to page 139 for instructions on how to increase the value of the LASTSTEP variable associated with the failing script. The GDDR Solution Support team will assist you in making this decision and taking appropriate action.

WTOR messages

During execution of a script, EMC GDDR displays WTOR messages for each of the steps required to execute a site swap.

EMC GDDR is also supplied with automatic responses for GDDB-prefixed messages that your site can enable, but these are disabled as shipped by EMC to allow for operations training and familiarity before the message handling is automated. An operator reply is often required for GDDR-prefixed messages.

GDDRKF0H TRANSFER_MASTER_FUNCTION_OWNERSHIPAdd a step to Site Swap scripts to transfer the Master-C role to the appropriate site.

GDDRKF21 (DC1) - Manage_BCVsPerforms TimeFinder/Mirror action SPLIT or RE-ESTABLISH to BCVs at the site value passed to this routine. The TimeFinder/Mirror action is also specified by the caller. Set this to N if you do not have BCVs configured at DC1.

GDDRKF21 (DC2) - Manage_BCVsPerforms TimeFinder/Mirror action SPLIT or RE-ESTABLISH to BCVs at site DC2. The TimeFinder/Mirror action is also specified by the caller. Set this to N if you do not have BCVs configured at DC2.

Table 11 EMC GDDR call overrides (2 of 2)

Program Function



Planned script operationsThis section describes each planned script operation that you can run from the EMC GDDR Primary Options menu, Option S, Scripts, Run GDDR Scripts. You choose the script you want to run from the Scripts for Planned Actions list in the Select Script to Run panel.

Abandon Site DC1 (site swap)

Usage This script is used to shut down the single site workload at the primary site in preparation for the restart of processing at the secondary site.

Restrictions Before starting, the script verifies that the script is running from the Master C-System at the primary site. If these checks fail, the script terminates with a nonzero return code and error message GDDR639I. For details, refer to the EMC GDDR Message and Code Guide.

Restart production at DC2 after site swap

Usage This script is used to restart the single site workload after the 'Abandon Site DC1 (site swap)' script has completed successfully.

Restrictions The script can only start after the Master C-System has transferred from the original primary site to the secondary (new primary) site. The Master C-System function is automatically transferred when the 'Abandon Site DC1 (site swap)' script completes successfully. If these checks fail, the script terminates with a nonzero return code and error message GDDR639I. For details, refer to the EMC GDDR Message and Code Guide.

Perform test IPL from BCVs at DC2

Usage This script is used to IPL contingency systems at site DC2 using BCV devices.

Restrictions The script can only be run from the current Master C-System.

Perform test IPL from R2s at DC2

Usage This script is used to IPL contingency systems at site DC2 using R2 devices.

IMPORTANT!This test requires complete isolation of the DC2 site. For the duration of the test window, there are no contingency systems available should an actual disaster occur at DC1. It is recommended that the production workload at the DC1 site be shut down prior to conducting R2 testing at DC2.


Planned script operations 167


Unplanned script operationsThis section describes EMC GDDR unplanned script processes which are invoked by one of two methods:

◆ The EMC GDDR Event Monitor prompts the operator to request management confirmation of a trigger event or events which may indicate an outage before the script is permitted to start.

◆ The operator submits a script from the Unplanned Actions list in the Select Script to Run panel.

EMC GDDR validates the status of the current host and storage environment against script rules before the script is allowed to begin processing. The steps you need to take to run these scripts are described in “Running scripts” on page 162.

Recover after loss of DC1 (LDR)

Usage This script is used to restart the single site workload after the GDDR Event Monitor has detected a ConGroup trip and the GDDR Heartbeat Monitor has timed out. These events occurring concurrently are viewed by EMC GDDR as a local disaster.


Resume replication after loss of DC1

Usage This script is used to resume the SRDF/S link to the secondary site after a primary site disaster.

Restrictions The script appears in the 'Select Script to Run' panel of the current Master C-System after completion of the ‘Recover after loss of DC1 (LDR)’ script.

If the ‘Recover after loss of DC1 (LDR)’ script failed to complete the transfer of the Master C-System to the new primary site, complete the transfer using GDDR Primary Option Menu option R, Manage Site Roles>option MXFR, before starting this script.



Resumption operationsThis section describes each resumption script that you can run from the EMC GDDR Primary Options menu, Option S, Scripts, Run GDDR Scripts. You choose the script you want to run from the Scripts for Resumption list on the Select Script to Run panel. The steps you need to take to run these scripts are described in “Running scripts” on page 162.

Resume after test IPL from BCVs at DC2

Usage This script is used to reset clear contingency systems after a test at DC2.


The following precondition must also be met before running the script:

◆ All DC2 testing is complete.

Resume after test IPL from R2s at DC2

Usage This script is used to reset clear contingency systems after a test at DC2.



◆ All DC2 testing is complete.

Resume replication after link failure

Usage This script is used to restore the SRDF/S link after a loss of the link.



◆ The link service must be restored.

Resumption operations 169



6

This chapter discusses how to deal with unplanned events.

◆ Introduction ................................................................................................................. 172◆ Consistency group trips ............................................................................................. 173◆ Local disaster operations............................................................................................ 174◆ System failure operations........................................................................................... 175◆ EMC GDDR Master Function transfer ..................................................................... 178

Handling UnplannedEvents

Handling Unplanned Events 171

Handling Unplanned Events

IntroductionMore crucial to your enterprise than operations that can be handled by scripts are those tasks you need to undertake to handle unplanned events. This chapter describes some unplanned events you may need to deal with and the steps you need to take to deal with them. The events include:

◆ Consistency group trips

◆ Regional disaster operations

◆ System failure operations

◆ Master function transfer operations



Consistency group tripsThe following sections describe how EMC GDDR handles a consistency group trip and how the unplanned event should be handled by operations staff.

A consistency group trip is usually seen as a single independent unplanned event. However, in some disaster scenarios, a consistency group trip may indicate the start of a rolling disaster. In this case, the consistency group trip may not be seen on all systems or sites. For example, a consistency group trip is always seen by the primary DASD site, but will not be seen at the secondary site if the SRDF/S links are down.

Through EMC GDDR, you can reply to consistency group trips in any of the following ways:

◆ Abandon DC1 and restart the workload at DC2.

◆ Abandon DC2 and continue running at DC1.

◆ Have EMC GDDR do nothing and take no further action.

Before replying, check with your z/OS systems programming support group to confirm what to reply.

Note: The "Abandon" functions described below should be run if the ConGroup trip noticed by EMC GDDR is a disaster event at DC1.

Abandon DC1 and restart workload at DC2To have EMC GDDR initiate the transfer of the business workload from DC1 to DC2, and abandon DC1, reply:

R nn,ABANDONDC1

where:

nn

Is the WTOR ID number.

Abandon DC2 and continue running at DC1To have EMC GDDR abandon the managed systems at the DC2 site and continue with the business workload at the DC1 site, reply:

R nn,ABANDONDC2

where:

nn


Have EMC GDDR take no actionTo have EMC GDDR take no further action for the consistency group trip (that is, continue to run production at DC1 or DC2 without SRDF/S to DC1 or DC2), reply:

R nn,I

where:

nn


Consistency group trips 173


Local disaster operationsEMC GDDR declares a local disaster (LDR) when a Congroup trip (CGT) event occurs concurrently with a heartbeat timeout (HBM). A local disaster may occur as:

◆ The instantaneous loss of DC1 (primary site).

◆ A rolling disaster that eventually leads to the loss of the DC1 site.

In either case, a local disaster is only detected and reported by the EMC GDDR C-System running at the DC2 site.

Confirm loss of DC1

When the EMC GDDR C-System at DC2 detects the loss of the DC1 site, the following panel is displayed. You are requested to confirm the loss of DC1.

IMPORTANT!Reply only after you have management approval.

Note: The use of DC1 [DC2] indicates that the value is supplied for the primary site, whether it is DC1 or DC2.

A reply of No terminates the dialog. A reply of Yes displays a confirmation message on the system console (and in the SYSLOG). After you have confirmed the local disaster (LDR), EMC GDDR takes the following steps:

◆ Makes the C-System at DC2 the Master C-System.

◆ Attempts to RESET_CLEAR all z/OS systems at the DC1[DC2] site.

* * * L D R D e t e c t e d * * * * * * L D R D e t e c t e d * * * Please Confirm Loss of Site DC1[DC2] Seek Management Approval Before Replying Seek Management Approval Before Replying *nn Please Confirm Management Approval (Yes/No):



System failure operationsThe following section details how EMC GDDR handles individual system failures and how you should respond to the EMC GDDR prompts.

EMC GDDR distinguishes between the following types of systems:

◆ An EMC GDDR C-System.

◆ z/OS production systems.

EMC GDDR C-System failure

When EMC GDDR detects that a C-System has failed at a particular site, the following WTOR message is displayed on the system console:

This condition could be because of some type of disaster at DC1, but more likely, is caused by some type of network problem that has caused a C-System heartbeat timeout which has resulted in EMC GDDR declaring the C-System at DC1 "dead". Therefore, before replying, you must confirm the status of the EMC GDDR C-System that has been reported as failed.

EMC GDDR to restart sssss at current location DCnTo have EMC GDDR restart the failed C-System (at its present location), reply:

R nn,IPL:ssss

where:

nn


ssss

Is the z/OS system name of the failed GDDR C-System.

EMC GDDR performs a LOAD CLEAR on the failed system. You are prompted to confirm the load address and load parameters.

EMC GDDR to take no actionTo have EMC GDDR take no further action for the failed C-System, reply:

R nn,I

where:

nn


GDDR Unplanned Event ===> > GDDR Detects C-System SYS1 has Failed at Site DC1, > You have the following choices... > > Reply IPL:SYS1 - GDDR to restart SYS5 at Current Location DC1 > Ignore - GDDR to Do Nothing. > *nn Enter desired Option...IPL:SYS1 or I:

System failure operations 175


Production system failure

EMC GDDR declares a production system failure when the message 'IXC402D sysname LAST OPERATIVE AT hh:mm:ss. REPLY DOWN ' occurs on any EMC GDDR managed production system. The following WTOR message is displayed on the system console:

IMPORTANT!Before making any reply, confirm the status of the production system that has been reported as failed.

EMC GDDR to restart ssss at current location DCnTo have EMC GDDR restart the failed production (at its present location), reply:

R nn,IPL:ssss

where:

nn


ssss

Is the z/OS system name of the failed system.

EMC GDDR performs a LOAD CLEAR on the failed system. You are prompted to confirm the load address and load parameters.

EMC GDDR to move business applications to site DCnTo have EMC GDDR restart the business applications at the opposite site to the failed production system, reply:

R nn,SYSSITEn

where:

nn


EMC GDDR performs a RESET_CLEAR of the failed production system, then triggers the restart of the business applications on the system that is the contingency partner for the failed production system.

GDDR Unplanned Event ===> > > GDDR Detects Production System SYS2 has Failed at Site DC2, > You have the following choices... > > Reply IPL:SYS2 - GDDR to restart SYS2 at Current Location DC2 > SYSSITEn - GDDR to Start Business Apps at Site DC1 > SYSRESET - GDDR to System Reset SYS2 at Site DC2 Only. > Ignore - GDDR to Do Nothing. > *nn Enter desired Option...IPL:SYS2, SYSRESET, SYSSITEn or I:



EMC GDDR to system reset ssss at site DCn onlyTo have EMC GDDR do a system reset for the failed production system, reply:

R nn,SYSRESET

where:

nn


EMC GDDR performs a RESET_CLEAR of the failed system. It performs no other actions.

EMC GDDR to take no actionTo have EMC GDDR take no further action for the failed production system, reply:

R nn,I

where:

nn


System failure operations 177


EMC GDDR Master Function transferIf the EMC GDDR Heartbeat Monitor detects that the C-System that owns the Master Function is no longer updating its heartbeat and has been declared dead, EMC GDDR transfers Master Function ownership to another C-System.

Note: Appendix D, “Using GDDRMAIN and the Heartbeat Monitor,” provides more information about the EMC GDDR Heartbeat Monitor.

EMC GDDR issues the following message to the system console requesting confirmation of EMC GDDR Master Function ownership transfer:

IMPORTANT!Before replying, check with your z/OS systems programming support group to confirm what to reply.

EMC GDDR to transfer Master Function ownershipTo have EMC GDDR complete the transfer of Master Function ownership, reply:

R nn,yes

where:

nn


EMC GDDR to take no actionTo prevent EMC GDDR from transferring the Master Function ownership, reply:

R nn,no

where:

nn


GDDR Confirmation ===>

Please Confirm C -System Master Transfer

From System : SYS3 to System : SYS5

Reason: CSYSDEAD

* nn Please Confirm Transfer Master Function (Yes/No):


7Invisible Body Tag

This chapter describes various maintenance procedures for EMC GDDR.

◆ Setting up a new EMC GDDR C-System .................................................................. 180◆ Renaming an existing EMC GDDR C-System ......................................................... 182◆ Adding a new production system or sysplex to EMC GDDR............................... 183◆ Changing the Consistency Group name................................................................... 184◆ Adding new RDF groups to EMC GDDR................................................................. 185◆ Adding new devices to EMC GDDR......................................................................... 187◆ Removing an RDF group from EMC GDDR control .............................................. 188◆ Removing devices from EMC GDDR control .......................................................... 189◆ Removing a system or a sysplex from EMC GDDR................................................ 190

PerformingMaintenance

Procedures

Performing Maintenance Procedures 179

Performing Maintenance Procedures

Setting up a new EMC GDDR C-SystemComplete the following steps to set up a new EMC GDDR C-System:

1. Ensure that correct system software is installed:

a. Ensure that the operating system meets the requirements for running EMC GDDR.

b. Ensure that ResourcePak Base, Consistency Group, SRDF Host Component, and (optionally) TimeFinder are installed at required release and maintenance levels.

c. Ensure that CA-OPS/MVS is installed with separately-licensed CA-ENF/CCI MSF installed.

2. Include the new system in the HMC configuration:.

a. Using the ACSADMIN userid, logon to each HMC in DC1 and DC2 and follow the instructions for Configuring for the Data Exchange APIs as described in the IBM Manual zSeries Application Programming Interfaces (SB10-7030).

b. Specify the community name using the procedure described in “Option C: Define HMC Community Names” on page 114.

c. Make the IP-address of the C-System being set up known to the HMC. Ensure that a Dynamic Virtual IP Address (DVIPA) is not used1.

3. Update the Site, System name, MSFID, IPL Parameters CPC, and LPAR name using the Define C-Systems panel shown in Figure 20 on page 97.

4. Update Symmetrix Control Facility and Consistency Group started task names for the specified C-System name using the Define EMC MF Enablers STCs panel shown in Figure 40 on page 120.

5. Update CA-OPS/MVS MSF parameters. On each C-System, add an entry for the new C-System to the CA-OPS/MVS REXX dataset member MSFINIT:

6. Update CA-OPS/MVS CCI parameters. On each C-System, add the following entries for the new C-System to the CA Event Notification/CCI parameter member CCIssssssss.

7. Stop and start the OPSMAIN started tasks on each C-system.

1. Reference: "Networking on z/OS:Dynamic cross-system coupling" in the IBM z/OS basic skills information center.

Address “OPSCTL” “MSF DEFINE MSFID(ssssssss)”, “APPID(ssssssss) RETRY(300 120) CCI”

where “ssssssss” is the MSF ID or the MVS system name of the new C-System

NODE( …add appropriate parameters for the new C-System… )

CONN,ssssssss

where “ssssssss” is the MSF ID or the MVS system name of the new C-System



8. During an appropriate maintenance window, Validate and Activate the parameter changes using the procedures described in “Option V: Validate GDDR Parameter Set” on page 131 and “Option A: Activate GDDR Parameter Set” on page 132.

Specify the following Validate and Activate parameters:

Specify GDDR Parameter Load Type : FULL (PARTIAL,FULL)Specify GDDR State Variables Action : RESET (RESET, ASIS, NOUPDATE)Propagate to Other C-systems : YES (YES/NO/TRY)Clear the GDDR Command Queue ? YES (YES/NO)Enforce consistency : RETRY=5 (YES/NO/RETRY(1-5)Ignore Backup Failure : NO (YES/NO)

Setting up a new EMC GDDR C-System 181


Renaming an existing EMC GDDR C-SystemComplete the following steps to rename an existing EMC GDDR C-System:

1. Replace the old C System system name with the new C-System system name using the Define C-Systems panel shown in Figure 20 on page 97.

2. Update the MSFID, IPL Parameters, CPC and LPAR name as needed using the Define C-Systems panel shown in Figure 20 on page 97.

3. Replace the existing C-System system name for the Symmetrix Control Facility and Consistency Group started task names using the Define EMC MF Enablers STCs panel shown in Figure 40 on page 120.

4. Update CA-OPS/MVS MSF and CCI parameters by referring to Customize CA-OPS/MVS for EMC GDDR, “Step 11: Update CA-OPS/MVS CCI parameters” on page 69.




6. Stop and start the OPSMAIN started tasks on each C-system.



Adding a new production system or sysplex to EMC GDDRUse the procedure below when adding a new production system or sysplex to the Enterprise Consistency Group, and thereby placing them under the management of EMC GDDR.

Adding a new system to the Enterprise Consistency Group could also involve the addition of new DASD. If this is the case, after this step is complete, continue with the procedure described in “Adding new RDF groups to EMC GDDR” on page 185.

1. Ensure that ResourcePak Base and Consistency Group are set up using common parameter definitions already used by the other systems in the Enterprise Consistency Group.

2. Add the parameters describing the new system using the Parameter Management Options Menu, “Option H: Define Host Objects” on page 106.




4. Follow the steps for installing the EMC z/OS Console Monitor started procedures described in “Install EMC GDDR C-System started procedures” on page 60.

Adding a new production system or sysplex to EMC GDDR 183


Changing the Consistency Group nameTo change the name of the Consistency Group, you will need to change and load the BCV parameter statements that include that group name. To do so, perform the following steps:

1. Replace the old Consistency Group name using the Define Configuration Basics menu, “Option R: Define Site Roles and Groups” on page 100.

2. Update the Consistency Group name using the Define Storage Objects menu, “Option TF: Define TimeFinder Device Ranges” on page 104.




4. Load the updated parameters, following the procedure described in “Option P: Profile—Update Personal GDDR ISPF Profile” on page 82.

5. Update Consistency Group parameters on all systems to reflect the new Consistency Group name.

• ConGroup – SRDF_CONGROUP = new ConGroup name

6. Update RDF Manager parameter members to reflect the Consistency Group name.

• SITEDC1 – MSC_5773 = new ConGroup name

• SITEDC2 – MSC_5773 = new ConGroup name

7. Update the RDFPARM member associated with the RDF entry for affected C-Systems within the Define EMC Mainframe Enablers STCs panel, “Option E: Define EMC MF Enablers STCs” on page 120 with the new ConGroup name.

8. Recycle Consistency Group on all systems, and restart SRDF/S with ConGroup. This will pick up the changes to the RDF manager parameters.



Adding new RDF groups to EMC GDDRThis section describes how to add new DASD to an existing SRDF/S with ConGroup environment by adding one or more new RDF groups to EMC GDDR and including the new devices in the new RDF groups.

1. Ensure the following:

• The RDF groups have been defined.

• The SRDF/S createpairs have been done and the devices are synchronized.

Note: The procedure for defining dynamic RDF groups and creating device pairs is provided in the EMC SRDF Host Component for z/OS Product Guide.

2. Create new GNS groups by specifying the new RDF group with the EMCGROUP utility, or add the new RDF group to an existing enterprise GNS group.

Note: The procedure for creating or modifying GNS groups is found in the Group Name Service description in the EMC ResourcePak Base for z/OS Product Guide.

The GNS group(s) defined can be named according to the following convention:

GDDRn_ddd_xxxxx_RGRP_nn_J0

where:

For each new RDF group, two GNS groups must be defined: one for DC1 and one for DC2.

3. Add the GNS group(s) to ConGroup parameter members for each site.

Add the newly defined GNS groups with the following naming convention to the Consistency Group parameter member CGRPGDDR:

• GDDR1_ddd_xxxxx_RGRP_nn_J0

• GDDR2_ddd_xxxxx_RGRP_nn_J0

These must be added after the SRDF_CONGROUP statement of the relevant group definition.

4. Perform EMC GDDR parameter updates:

a. If any of the standard devices in the RDF groups being added are to have an associated BCV, add the necessary device ranges using the Define Storage Objects menu, “Option TF: Define TimeFinder Device Ranges” on page 104.

b. Add SRDF/S GNS group names using the Define Storage Objects menu, “Option GN: Define SRDF/S GNS Groups” on page 103 for the new GNS groups being added.

c. Add RDF group names using the Define Storage Objects menu, “Option SR: Define SRDF Device Ranges” on page 101.

n has the value 1 or 2, used to identify which group to use depending upon the location of the primary DASD, either DC1 or DC2.

ddd has the value CKD or FBA, depending upon what type of DASD is defined in the GNS group.

xxxxx is the last five (5) digits of the Symmetrix controller serial number.nn is the new RDF group.

Adding new RDF groups to EMC GDDR 185


d. Add SRDFS device ranges for all devices in the RDF groups being added using the Define Storage Objects menu, “Option SR: Define SRDF Device Ranges” on page 101.

5. Distribute the changed EMC parameter members to all systems participating in the SRDF/S with ConGroup environment.

6. Bring the new RDF group(s) into the live SRDF/S environment by reenabling ConGroup protection with a ConGroup REFRESH,FORCE command.






Adding new devices to EMC GDDRThis section describes how to add new DASD to an existing EMC GDDR environment by adding the devices to one or more existing RDF groups.

1. Stop the EMC GDDR Event Monitor and Heartbeat Monitor.

2. Disable ConGroup.

3. Create SRDF/S device pairs.

Add the new devices to one or more existing RDF groups using the #SC VOL CREATEPAIR command. Details on how to use this command can be found in the SRDF Host Component for z/OS Product Guide.

4. Make the following EMC GDDR parameter changes:

• If any of the standard devices being added are to have an associated BCV, create appropriate BCV device ranges for associated ConGroup devices using the Define Storage Objects menu, “Option TF: Define TimeFinder Device Ranges” on page 104.Add SRDFS device ranges for all devices being added and related gatekeepers using the Define Storage Objects menu, “Option SR: Define SRDF Device Ranges” on page 101.

5. Add the devices to the your existing EMC GDDR-protected GNS device groups.

6. Remove or update any SCF.DEV.EXCLUDE.LIST SCF initialization parameters which would exclude the devices you wish to add.

7. Issue an SCF,GNS,REFRESH command.

8. Re-enable ConGroup protection with a ConGroup REFRESH,FORCE command.




Adding new devices to EMC GDDR 187


Removing an RDF group from EMC GDDR controlComplete the following steps to remove an RDF group from EMC GDDR control:

1. Verify these prerequisites:

• Ensure that the RDF groups to be removed from the control of EMC GDDR have been removed from any relevant MSC GNS group.

• If the RDF groups are for SRDF/S devices, ensure that the SCFG( … ) parameters referencing the RDF groups being removed from EMC GDDR control have been removed from the CGRPxxx Consistency Group parameter member on all production systems and C-Systems.

• Ensure that references to the RDF groups being removed from the MSC group definitions in the MSC parameter members have been removed.

2. Make the following EMC GDDR parameter changes:

• Delete all BCV devices associated with the standard devices being removed using the Define Storage Objects menu, “Option TF: Define TimeFinder Device Ranges” on page 104.

• Delete all GNS group names that reference the RDF groups being removed using the Define Storage Objects menu, ““Option GN: Define SRDF/S GNS Groups” on page 103.

• Delete SRDFS device ranges for all devices in the RDF groups being removed, using the Define Storage Objects menu, ““Option SR: Define SRDF Device Ranges” on page 101.

3. Refresh the SRDF/S with ConGroup environment.

• Issue a ConGroup REFRESH,FORCE command to refresh the ConGroup definitions.

4. Restart SRDF/S with ConGroup protection.

Once successfully restarted, check to ensure that the RDF group(s) being deleted are no longer part of theConsistency and Swap groups.






Removing devices from EMC GDDR controlComplete the following steps to remove devices from EMC GDDR control.

Note: Ensure that the devices to be removed from the control of EMC GDDR are not gatekeeper devices.

1. Update your GNS device group definitions so they no longer include the devices being removed from EMC GDDR control.

If your GNS device groups are defined by RDF group inclusion, this will require additional steps:

a. Issue a ConGroup DISABLE command.

b. RDF-Suspend the SRDF/S devices being removed.

c. DELETEPAIR the SRDF/S devices being removed.

2. Issue a GNS,REFRESH command.

3. Issue a ConGroup REFRESH,FORCE command.

4. Restart SRDF/S with ConGroup.

5. Update EMC GDDR parameters:

• If any of the standard devices being removed have an associated BCV, remove the associated BCV devices or device ranges using the Define Storage Objects menu, “Option TF: Define TimeFinder Device Ranges” on page 104

• Remove the device ranges using the Define Storage Objects menu, “Option SR: Define SRDF Device Ranges” on page 101.




Removing devices from EMC GDDR control 189


Removing a system or a sysplex from EMC GDDR

Note: On the system or systems being removed, ensure that the ResourcePak Base and Consistency Group started procedures have been stopped and will no longer be used.

1. Delete the parameters describing the system(s) being removed using the Parameter Management Options Menu, “Option H: Define Host Objects” on page 106.






Special casesIn a SRDF/S with ConGroup environment, special consideration must be given to devices that are not being protected by Congroup, specifically volumes containing the following system data:

◆ Non-LOGR couple datasets

These datasets will be replicated to DC2 using SRDF Adaptive Copy mode, therefore they are not managed by the EMC GDDR restart process. These devices can be defined to EMC GDDR as external devices. “External” on page 102 provides more information.

Use of the "Perform test IPL from BCVs at DC2" script requires no manual actions. EMC GDDR will control the BCV SPLIT operations for volumes outside of EMC GDDR control.

Non-LOGR couple datasets ◆ All volumes containing non-LOGR couple datasets must be paired up (using an

adaptive copy RDF group defined specifically for this purpose) to appropriate R2 volumes and allowed to synch up. Once in synch, the pairs must be suspended.

This action must be carried out any time non-LOGR couple dataset volumes are added or moved in the configuration. Additionally, after any policy management the relevant couple datasets must be resynched with the corresponding volume(s) at R2 to ensure the latest changes will be available in the event of a regional disaster.

◆ Volumes used for couple datasets must be dedicated volumes, that is, they must contain no other system or user data.

Special cases 191



8Invisible Body Tag

This chapter describes the EMC GDDR Audit Monitoring Facility.

◆ Overview ....................................................................................................................... 194◆ Implementation tasks .................................................................................................. 195◆ EMC GDDR audit monitoring SMF extract and report JCL .................................. 196◆ CA-OPS/MVS environment monitoring.................................................................. 197

Using the AuditMonitoring Facility

Using the Audit Monitoring Facility 193

Using the Audit Monitoring Facility

OverviewThe EMC GDDR Audit Monitoring Facility supports the capture and externalizing of data that EMC GDDR automation uses for business continuance processing (BCP) decision criteria and operations. This data includes dates and times of parameter load and backup jobs, global variable updates, override usage, and state changes relevant to EMC GDDR-managed systems and storage.

The Audit Monitoring Facility leverages your existing investment in SMF data management and reporting methods by writing SMF records containing information that is of interest beyond the end of the discrete EMC GDDR operations.

Global variable changesUpdates to EMC GDDR Global variables are monitored and logged.

“Global variable monitoring implementation” on page 195 describes how to enable this feature.

MessagesEMC GDDR script processing and status WTO messages are selected based on installation options. Installation filters on the message IDs provide the flexibility to gather messages originated by EMC Symmetrix host software, in addition to EMC GDDR-specific messages.

“Message logging implementation” on page 195 explains how to select the messages to be logged.

State changesHost and storage environment state changes that occur as a result of EMC GDDR processing are monitored and retained in chronological order. A dynamic reference of these values can be found at the EMC GDDR State Variables panel, as shown in “Option V: Validate GDDR Parameter Set” on page 131.

“GDDR SAY and state monitoring implementation” on page 195 describes how to define State installation options.

CA-OPS/MVS environment changesCA-OPS/MVS changes for events that impact EMC GDDR operations are monitored using the CA-Common Services for z/OS (CCS) Automation Measurement Environment (AME).

“CA-OPS/MVS environment monitoring” on page 197 provides additional information. An overview of this functionality is also provided in the CA-OPS/MVS Event Management and Automation User Guide r11.6.



Implementation tasks

Message logging implementationThese include OPSREXX SAY messages as well as WTO messages. In addition, audit monitoring options support the selection of only Error and/or Warning messages. Up to four templates allow for single character message ID wildcards.

Note: The term SAY describes the messages that are issued by EMC GDDR in the course of its processing that is outputted to the batch TSO SYSTSPRT DD in lieu of issuing a WTO for the message. These messages are often the result of an EMC GDDR script process and have a message ID that is documented in the EMC GDDR Message and Code Guide.

The AOFRULES WTO selection program, GDDRSECW, for user-selection of messages produced by EMC GDDR operations. These are messages whose message ID begins with 'GDD'.

GDDR SAY and state monitoring implementationWhen an installation chooses to log all EMC GDDR WTO and SAY messages to the SMF log, monitoring of state messages may be redundant. However, if an installation chooses to not log informational WTO and Say messages, logging of additional state messages could be a valuable source of environment status information.

Global variable monitoring implementationGlobal variables are monitored by two AOFRules programs, GDDRSECG and GDDRSECX. Program GDDRSECG is delivered as hlq.GDDRvrm.SAMPLIB to allow for installation customization. Add the customized version of GDDRSECG to hlq.GDDRvrm.AOFRULES and enable the AOF Rules as described in “Step 3: Make EMC GDDR AOF rules available to CA-OPS/MVS” on page 65.

Implementation tasks 195


EMC GDDR audit monitoring SMF extract and report JCLA sample SMF record extract is delivered in hlq.GDDRvrm.SAMPLIB(GDDRSMFX). The dataset name fields must be customized as described below.

◆ DSN=<USER.SMF.LOG>, where USER.SMF.LOG is the SMF recording dataset (SYS1.MANx) for the host where the EMC GDDR C-System resides.

◆ DSN=<USER.GDDR.SMFLOG.DATASET>, where USER.GDDR.SMFLOG.DATASET is the sequential format reporting dataset.

Audit Monitoring report JCL is delivered in hlq.GDDRvrm.SAMPLIB(GDDSMFL). This utility copies the output of the extracted SMF records to a user-accessible dataset, and reports the contents of the dataset.

SMF audit data flow

SMF log records that are written by the audit feature have the following data flow:

1. They reside in the host system's SMF recording datasets, (for example, SYS1.MANx).

2. They are extracted from the SMF recording datasets into an EMC GDDR SMF log dataset by SAMPLIB(GDDRSMFX).

3. They are reported from the EMC GDDR SMF log dataset by SAMPLIB(GDDRSMFL).

Sample output

The following example shows output taken from Audit Monitoring records that were created during an EMC GDDR parameter load:

In the above example, messages are logged to indicate the start of the batch parameter load process. During approximately the same time interval, the parameter GLOBAL.GDDR.TESTAUTH is initialized with the value Y and then the parameter is deleted by user JABCD1 to illustrate the logging of global variable changes.

GDDR SMF Log Report Page: 1 Date Time Sys Subs Target Type SubType JobID Event ExecPgm UserID Group ------- ----------- ---- ---- -------- -------- -------- -------- -------- -------- -------- -------- 2008289 09:01:24.99 SYS3 State GDDRGF04 GDDR PARM LOAD STARTING

2008289 09:01:25.03 SYS3 Message GDDP001I GDDR BATCH PARAMETER PROCESSOR STARTING ON 09:19 AT OCTOBER 15, 2008

2008289 09:01:25.76 SYS3 OPSX SYS3X GLV Chg Update,, J0035979 GLV IKJEFT1A JABCD1 GDDR$ADM Name: GLOBAL.GDDR.TESTAUTH Old Value: GLOBAL.GDDR.TESTAUTH New Value: Y

2008289 09:01:25.77 SYS3 OPSX SYS3X GLV Sec 6-Delete J0035979 SEC IKJEFT1A JABCD1 GDDR$ADM GLOBAL.GDDR.TESTAUTH

2008289 09:01:25.79 SYS3 Message GDDP002I RUNNING ON SYSTEM SYS3 USING THESE OPTIONS:

2008289 09:01:25.83 SYS3 Message GDDP002I -> UPDATE, INIT, MSFBYPASS, MSGID

2008289 09:01:25.86 SYS3 Message GDDP006I INITIALIZATION REQUESTED, SYSTEM ELIGIBILITY TEST DEFERRED



CA-OPS/MVS environment monitoring

AOFEVENT segmentThe statistics reported in the AOFEVENT segment of the Automation Statistics report are accumulated throughout the life of a particular AOF rule. When the rule is disabled and the SMFRULEDISABLE parameter is set to YES, CA-OPS/MVS generates an SMF record that describes the life of the AOF rule. The AOFEVENT segment reports the data in this SMF record.

SMFRULEDISABLE segmentThis segment controls whether CA-OPS/MVS will write an SMF record when a rule, a rule set, or both are disabled.

OSFTERM segmentThe statistics reported in the OSFTERM segment of the Automation Statistics report are accumulated throughout the life of a particular OSF server. When the server is terminated, CA-OPS/MVS generates an SMF record that describes the life of the server. The OSFTERM segment reports the data in this SMF record.

Summary sectionThe statistics reported in the summary section of the Automation Statistics report are accumulated throughout the execution of CA-OPS/MVS. When CA-OPS/MVS is terminated, these statistics are totaled and written to an SMF record. The OPSSMF OPS/REXX function can also be used to write the cumulative summary records on demand, instead of upon product termination.

One reason to do this is when the SMF address space is terminated prior to the termination of CA-OPS/MVS. For more information on the OPSSMF function, see the CA-OPS/MVS Event Management and Automation Command and Function Reference, r11.6. The summary section reports the data in this SMF record.

Note: Additional information is available in the CA-OPS/MVS Event Management and Automation User Guide, r11.6, Chapter 21, Using the Automation Measurement Environment.

CA-OPS/MVS environment monitoring 197



9Invisible Body Tag

This chapter documents how to resolve problems you may encounter while running EMC GDDR scripts.

◆ Detecting and resolving problems............................................................................ 200◆ Using the GDDRXCMD batch utility ....................................................................... 201

Troubleshooting

Troubleshooting 199

Troubleshooting

Detecting and resolving problemsKeep the following points in mind:

◆ EMC GDDR scripts should always end with return code=0. This indicates that the desired action has been completed successfully.

◆ If an EMC GDDR script does not complete with return code=0, you need to identify the problem. First, examine the JOBLOG of the job that ran the script. Then, examine the SYSTSPRT and SYSPRINT DDs for any error messages and nonzero return codes.

◆ Look up EMC GDDR error messages in the EMC GDDR Message and Code Guide. Follow the actions recommended in that document.


Troubleshooting

Using the GDDRXCMD batch utilityAs part of troubleshooting or correcting EMC GDDR issues, you may need to print or clear the queue. To do so, use GDDRXCMD, a batch utility that can perform these tasks.

Customize examples below to your site's requirements.

To print the current queue//QPRINT EXEC PGM=GDDRXCMD,PARM=PRINT//SYSPRINT DD SYSOUT=*

The result will be a hexadecimal + character printout of the current records in the queue.

To clear the current queue //QCLEAR EXEC PGM=GDDRXCMD,PARM=BOTH//SYSPRINT DD SYSOUT=*

The job must end with RC=0. Run another print job to verify that the queue has indeed been cleared.

IMPORTANT!Only clear the queue if you have been advised to do so by EMC Customer Support.

Using the GDDRXCMD batch utility 201

Troubleshooting


AInvisible Body Tag

This appendix describes GDDR user exit routines.

◆ User exit programming considerations .................................................................... 204◆ Exit specifications......................................................................................................... 206

Appendix

C:Starti

ngand

Stopping

Workloads

Appendix

D:GDDR

UserExits

EMC GDDR User Exits

EMC GDDR User Exits 203

EMC GDDR User Exits

User exit programming considerationsUser exits must be written in OPS/REXX. Consult the OPS-MVS Event Management and Automation User Guide for information about differences between OPS/REXX and standard REXX.

In the exit descriptions that follow, all parameters are positional within a single REXX argument. That is, the arguments are accessed by a REXX instruction such as

parse arg parm1 parm2 . . .

Sample procedureAs an example, you can use one of the GDDRUXnn sources in hlq.gddrvrm.SAMPLIB to create your own version of one of the documented GDDR user exits. Place this source in a library of your choice.

To create a customized user exit:

1. Allocate an OPSEXEC dataset with the same attributes as opshlq.OPSEXEC, including the access authorizations.

2. In your OPSVIEW Primary Options menu, select option 2.4 and indicate the names of your source library and your OPSEXEC library. Press Enter.

3. From the member list of your source library, choose your modified user exit and enter the C (compile) line-command. This will create GDDRUXnn as a compiled REXX module in your OPSEXEC library.

Before you use your user exit for the first time:

1. Update the OPSEXEC DD concatenation to include your new OPSEXEC library as the first DATASET. This must be done in the following:

• OPSVIEW REXX exec

• OPSOSF STC jcl

• GDDRPROC member

• GDDRHBM and GDDREVM STC jcl

2. To start using your new OPSEXEC library, recycle GDDREVM, GDDRHBM, and your CA-OPS/MVS started tasks.

To update a user exit after its first usage, recompile your updated source into your custom OPSEXEC dataset.

Built-in routines available to exits

Exit routines may save and retain values across separate invocations using built-in routines as follows:

GDDRUXSVGDDRUXSV allows you to save a value in a specified durable variable, creating the variable if necessary.

Invocation format is:

call gddruxsv variable-name variable-value

The return code is found in REXX variable ‘result’. Any return code other than 0 indicates an error.


EMC GDDR User Exits

GDDRUXGVGDDRUXGV allows you to retrieve a value previously saved by GDDRUXSV.


call gddruxgv variable-name

The value is returned in REXX variable ‘result’. If no value is available, the ‘result’ variable is dropped and consequently becomes ‘RESULT’ when evaluated.

GDDRUXDVGDDRUXDV allows you to delete a durable variable previously created by GDDRUXSV.


call gddruxsv variable-name variable-value

The return code is found in REXX variable ‘result’. Any return code other than 0 indicates an error.

User exit programming considerations 205

EMC GDDR User Exits

Exit specifications

GDDRUX01This exit is called from Planned or Unplanned scripts at a point appropriate for starting production mainframe workloads. The exit must be named GDDRUX01.

Parameters 1. Mode:

• SYNCH — Caller will wait for result

• ASYNC — Caller will not wait for result

2. System id on which to start workload

3. Number of this system in the list of systems for which user exit 1 will be called

4. Number of systems in the list of systems for which user exit 1 will be called

Return code If zero, the exit will not be called on a script rerun. If non-zero, the exit will be called on a script rerun.

Example An example of how user exit 1 could be programmed is provided in the EMC GDDR SAMPLIB distribution library member GDDRUX01.

GDDRUX02This exit is called from Planned or Unplanned scripts at a point appropriate for stopping production mainframe workloads. The exit must be named GDDRUX02.

Parameters 1. Mode:



2. System id on which to stop workload

3. Number of this system in the list of systems for which user exit 2 will be called

4. Number of systems in the list of systems for which user exit 2 will be called




EMC GDDR User Exits

GDDRUX03

This exit is called from Planned or Unplanned scripts at a point appropriate for starting production open systems workloads. The exit must be named GDDRUX03.

Parameters 1. Mode:



2. Source (site moving from)

3. Target (site moving to)

4. Context (reason for call - values are swap, rdr, tdc3, ldr)



GDDRUX04

This exit is called from Planned or Unplanned scripts at a point appropriate for stopping production open systems workloads. The exit must be named GDDRUX04.

Parameters 1. Mode:



2. Source (site moving from)

3. Target (site moving to)

4. Context (reason for call–values are swap, rdr, tdc3, ldr)



GDDRUX05This exit is given control each time an EMC GDDR message is issued. This is an appropriate exit point to edit message content and/or create alerts. Alerts may be in the form of a message, SNMP event or any other form of alert. The exit must be named GDDRUX05.

Parameters 1. Date: format is DATE("S")

2. Time: format is TIME("N")

3. "M"

4. System smf id

5. Severity: format is numeric

6. Priority: format is numeric

Exit specifications 207

EMC GDDR User Exits

7. Axxx: xxx=asid in hex

8. "NONE..."

9. "NONE"

10. "N"

11. "N"

12. "ALERTAUT"

13. "GDDR"

14. "J"

15. "AUTOMATION ALERT :" msgid wto_text

Return code Not significant.


GDDRUX06

This exit receives control each time an EMC GDDR message is issued. Using this exit, you may process the message as described below, or you may suppress it entirely. The exit must be named GDDRUX06.

Parameters 1. Function: EMC GDDR function under which exit is being invoked

2. Msg id: message identification tag (8 characters alphanumeric)

3. Msg text: Text of message associated with message id

Return code The return code value determines EMC GDDR action for the message:


0 Take no action; the message is effectively suppressed

1 Issue message as a WTO

2 Issue message using the REXX ‘SAY’ function

4 Write message to SMF using the SMF record type specified by the value of parameter SMF_Record_Type

8 Call GDDRUX05 to generate an alert for this message


EMC GDDR User Exits

GDDRUX07

This exit is called when any GDDR AOF rule is enabled. This exit receives control during initialization and is passed the id of the message whose rule is being initialized. Using this exit, you may suppress enabling of the message rule. The default exit supplied allows rule enabling of all rules.

Parameters The id of the message to which the message rule is dedicated.

Return code

A default GDDRUX07, found in hlq.GDDRvrm.SAMPLIB, or any replacement you furnish, must be copied to the dataset where the EMC GDDR AOF rules reside.

CAUTION!If you provide a replacement for GDDRUX07, be aware that proper EMC GDDR functioning requires detection and handling of system messages. The only messages that you can safely not enable are those issued by products that are not present on your production systems.

0 Allow the message rule to be enabled

Other Do not enable the message rule

Exit specifications 209

EMC GDDR User Exits


BInvisible Body Tag

This appendix describes the EMC GDDR z/OS Console Monitor.

◆ Introduction .................................................................................................................. 212◆ z/OS Console Monitor — GDDRPBAL.................................................................... 213◆ z/OS operator console commands ............................................................................ 214◆ BAL command processor — BALC ........................................................................... 215

EMC GDDR z/OSConsole Monitor

EMC GDDR z/OS Console Monitor 211

EMC GDDR z/OS Console Monitor

IntroductionThe EMC GDDR z/OS Console Monitor propagates messages necessary for comprehensive system event correlation from production systems to C-Systems, and from C-Systems to production systems. The GDDRPBAL started procedure functions as a broadcast utility when messages of interest are detected on the system console of a monitored system. The same started procedure also functions as a listener utility. For example, when messages of interest are received from a monitored production system, the GDDRPBAL task may trigger an EMC GDDR response when the propagated message is received by a matching EMC GDDR AOF rule. The EMC GDDR supplied CA-OPS/MVS AOF rules can be found in the EMC GDDR library hlq.GDDRvrm.AOFRULES.

You must verify that GDDRPBAL started tasks are active on EMC GDDR managed production systems and EMC GDDR C-Systems when the EMC GDDR Event Monitor and Heartbeat Monitors are active.

Use of the EMC GDDR z/OS Console Monitor requires the following:

◆ SCF cross-system communication (CSC)

This technology allows for transfer of messages across SCF executions.

◆ z/OS multiple console support (MCS)

This technology allows for monitoring the z/OS console.

hlq.GDDRvrm.PARMLIB(GDDRMSGR) contains the message identifiers that are required to be routed from production systems to the EMC GDDR C-Systems. hlq.GDDRvrm.PARMLIB(GDDRMSGC) contains the message identifiers that may be routed from C-Systems to EMC GDDR managed production systems.



z/OS Console Monitor — GDDRPBALGDDRPBAL monitors z/OS console messages on both production systems and EMC GDDR C-Systems, depending upon whether the GDDRPBAL started procedure specifies a CSYS or a PSYS parameter.

A GDDRPBAL started procedure which specifies the PSYS parameter listens for message IDs identified in hlq.GDDRvrm.PARMLIB(GDDRMSGR) and routes the occurrences of these messages to EMC GDDR C-Systems. These message IDs are from production system applications having specific meanings for the GDDR Event Monitor.

Parameters

The following parameters are for use in the GDDRPBAL PROCLIB member EXEC statement:

◆ PSYS — causes a GDDRPBAL started task that is running on an EMC GDDR-managed production system to route messages to an EMC GDDR C-System.

◆ CSYS — causes a GDDRPBAL started task that is running on an EMC GDDR C-System to route messages to EMC GDDR-managed production systems.

Define message IDs

Message IDs that GDDRPBAL will monitor and broadcast are specified in a dataset referenced by the MESSAGES DD. The message dataset DCB is fixed length LRECL=80. The message IDs to be propagated are in positions 1-8 , one message ID per record.

GDDRPBAL also supports the DEBUG parameter, which must be specified in uppercase. When DEBUG is specified, GDDRPBAL will output debugging information to SYSOUT. Debug mode can be dynamically toggled by running the BALC utility with DEBUG or UNDEBUG, respectively or by an operator console command as described in “z/OS operator console commands” on page 214.

Sample debug output

GDDRPBAL DEBUG REQUESTED. DEBUG LOG STARTED. MESSAGE: GDDRBALC,DEBUG,SMCASID=X1E ,DATE=07199,TIME=10:00:71,DFARELS=03010600,IP=010.2

GDDRPBAL PROCESS COMMAND. MESSAGE: GDDRBALC,DEBUG,SMCASID=X1E ,DATE=07199,TIME=10:00:71,DFARELS=03010600,IP=010.243.150.134

GDDRPBAL DEBUG REQUESTED. DEBUG LOG STARTED. MESSAGE: GDDRBALC,DEBUG,SMCASID=X1E ,DATE=07199,TIME=10:00:71,DFARELS=03010600,IP=010.2

z/OS Console Monitor — GDDRPBAL 213


z/OS operator console commandsThe z/OS Console Monitor is controlled through operator console commands or through parameters processed by the BAL Command processor, BALC, a batch job.

Actions that are specified by operator console MODIFY commands are SHUTDOWN, DEBUG, and UNDEBUG. The operator console commands will perform the requested action on the CBAL or PBAL instance currently running on the LPAR where the command is submitted. CBAL and PBAL instances executing on other LPARs are unaffected. The syntax for these commands is:

/F GDDRCBAL,SHUTDOWN/F GDDRPBAL,DEBUG/F GDDRCBAL,UNDEBUG

The operator console STOP command will stop the CBAL or PBAL instance currently running on the LPAR where the command is submitted:

/P GDDRPBAL



BAL command processor — BALCCommands to GDDRPBAL jobs are issued by executing the batch utility called BALC. The command is specified in the PARM of the EXEC statement in the JCL. The following commands are supported:

◆ SHUTDOWN

Shut down all GDDRPBAL jobs. Specify keywords CSYS or PSYS to limit shutdown to the console monitor job on a C-System or production systems, respectively.

◆ DEBUG

Turn on debugging for all GDDRPBAL jobs.

◆ UNDEBUG

Turn off debugging for all GDDRPBAL jobs.

◆ UNLISTEN

Initialize BAL CSC ports 108 and 109. “BAL CSC ports” on page 216 provides more information.

The BALC utility can be run on any C-System or production system LPAR.

Command syntax

The following describes the syntax of the PARM value:

[DEBUG,]SHUTDOWN [CSYS/PSYS][DEBUG,]DEBUG[DEBUG,]UNDEBUG[DEBUG,]UNLISTEN RToken

Sample JCL

//GO EXEC PGM=GDDRBALC,PARM='DEBUG,SHUTDOWN PSYS'//STEPLIB DD DSN=GDDR.LINKLIB,DISP=SHR //SCF$RGR DD DUMMY

Sample output

13.15.46 J0014308 IRR010I USERID GDDRUSR IS ASSIGNED TO THIS JOB. 13.15.46 J0014308 ICH70001I GDDRUSR LAST ACCESS AT 13:15:41 ON TUESDAY, JULY 24, 2007 13.15.46 J0014308 $HASP373 BALQUIT STARTED - WLM INIT - SRVCLASS PRDBATHI - SYS SYS4 13.15.46 J0014308 IEF403I BALQUIT - STARTED - TIME=13.15.46 13.15.46 J0014308 GDDRBALC DOPARMS PARMS(CC1-66): DEBUG,SHUTDOWN CSYS 13.15.46 J0014308 GDDRBALC DOPARMS SHUTDOWN CSYS 13.15.47 J0014308 GDDRBALC INIT0200 IP: 010.243.150.128 13.15.47 J0014308 GDDRBALC SHUTDOWN MESSAGE BUILT. MSG: GDDRBALC,SHUTDOWN,SMCASID=SYS4

,DATE=07205,TIME=13:10:72,DF 13.15.47 J0014308 GDDRBALC CSYS BROADCAST COMPLETED. RTOKEN: 207918E800000000C0F15D40FCEE4E49 RC: 0 13.15.47 J0014308 GDDRBALC MAINEXIT RC: 0 13.15.47 J0014308 BALQUIT GO GDDRBALC 0000 8 0 0 13.15.47 J0014308 IEF404I BALQUIT - ENDED - TIME=13.15.47 13.15.47 J0014308 BALQUIT RC 0000 ET 00:00:00 IO 8 CP .0/ .0 13.15.47 J0014308 $HASP395 BALQUIT ENDED

BAL command processor — BALC 215


BAL CSC ports

The SCF cross-system communication capability of EMC ResourcePak Base is based on a numeric port value. For the EMC GDDR z/OS Console Monitor (Broadcast and Listener, BAL), the following have been registered:

◆ 108

GDDRPBAL instances using PARM=CSYS listen for new messages from this port. GDDRPBAL instances using PARM=PSYS send messages to this port.

◆ 109

GDDRPBAL instances using PARM=CSYS send messages to this port. GDDRPBAL instances using PARM=PSYS listen for new messages from this port.

CSC RTokensWhen the GDDRPBAL task begins to listen to a CSC port, an RToken is returned. This RToken must be freed prior to another Listener session with CSC on that LPAR for that port. GDDRPBAL has this functionality built into it for normal and abnormal terminations.

You can also reset the ports on a given LPAR with a console command. The following is an example of a reset of port 108:

F GDDRSCF,CSC,UNLISTEN CODE(108)

where GDDRSCF is the name of the Symmetrix Control Facility (SCF) started task pointed to by the //SCF$xxxx DD statement in the GDDRPBAL started task.


D

This appendix describes use of GDDRMAIN, DIV datasets, and the Heartbeat Monitor.

◆ Starting/Stopping GDDRMAIN............................................................................... 218◆ GDDRMAIN EXEC parameters ................................................................................ 220◆ GDDRGVX utility ....................................................................................................... 221◆ EMC GDDR system variable integrity and access ................................................. 222◆ Starting/Stopping the Heartbeat Monitor............................................................... 224

Using GDDRMAIN andthe Heartbeat Monitor

Using GDDRMAIN and the Heartbeat Monitor 217

Using GDDRMAIN and the Heartbeat Monitor

Starting/Stopping GDDRMAIN GDDRMAIN accepts the z/OS modify command (F) and stop command (P).

Stop command (P)To stop GDDRMAIN, issue a P GDDRMAIN (or use the current jobname, if different).

CAUTION!Do not cancel GDDRMAIN except in an emergency. Although GDDRMAIN has a TERM=YES ESTAE, actions by the ESTAE exit routine are limited when a cancel is used.

When a P command is issued, GDDRMAIN will stop all subtasks except GVT, then stop GVT. If GVT is not running or if it is unable to write the DIV for any reason, a WTOR will be issued to allow saving the data space if that is desired (see GDDRGVX DSPSAVE).

Modify command (F)

GDDRMAIN accepts modify commands in the form “F GDDRMAIN,verb operand”, where verb operand is one of the following:

◆ START◆ STOP◆ RESTART◆ CANCEL◆ TASKS◆ GVCTL◆ LOCK

Managing GDDRMAIN subtasks

START command

Use START to start a subtask which is not currently running. The syntax is “F GDDRMAIN,START name” where name is the name of the subtask. Issue the TASKS command to see the names of the subtasks.

STOP command

Use STOP to stop a subtask which is currently running. The syntax is “F GDDRMAIN,STOP name” where name is the name of the subtask. STOP will post the subtask to end, but if it does not end, you can use CANCEL to stop it.

RESTART command

Use RESTART to stop a subtask which is running and restart it immediately. The syntax is “F GDDRMAIN,RESTART name” where name is the name of the subtask. RESTART will post the subtask to end, but if it does not end, you can use CANCEL to stop it. If you use CANCEL, the automatic restart will not occur, but you can use START to restart the subtask.

CANCEL command

Use CANCEL to stop a subtask which is running. The syntax is “F GDDRMAIN,CANCEL name” where name is the name of the subtask. CANCEL does not post the task to end, but instead simply detaches it.



TASKS command

Use TASKS to display the status of each subtask. There are no operands. The syntax is “F GDDRMAIN,TASKS”. For each subtask, a line is displayed with the subtask name and its status, ACTIVE or ENDED. If the status is ENDED, the last return code from the subtask is displayed in parentheses after ENDED.

Administrator commands

GVCTL command

Use GVCTL to display or modify the value of GVCW. The syntax is “F GDDRMAIN,GVCTL” to display the value and “F GDDRMAIN,GVCTL n” to set the value to n. If a value is specified, it must be numeric. For either form, the value in GVCW is displayed, either the value which was present before the command if no operand is used, or the new value if a valid operand is specified.

LOCK command

Use LOCK to display or clear the index, or update locks, or both. The syntax is “F GDDRMAIN,LOCK” or “F GDDRMAIN,LOCK,lock-name” or “F GDDRMAIN,LOCK,lock-name,cmd” where lock-name is INDEX, UPDATE, or BOTH and cmd is DISPLAY or CLEAR. The default value for lock-name is BOTH and the default command is DISPLAY. The status of the requested lock will be displayed (CLEAR, SET, IN USE, PENDING, or BROKEN).

◆ If the status is SET, the job name and ID of the locker will be displayed along with the number of seconds since the lock was set.

◆ If the status is IN USE or PENDING, the number of seconds since the shared lock was changed will be displayed.

Refer to “EMC GDDR system variable integrity and access” on page 222 for lock descriptions, status definitions, and administrative considerations of the locks.

Starting/Stopping GDDRMAIN 219


GDDRMAIN EXEC parametersGDDRMAIN accepts the EXEC statement parameters listed below. The parameters may be specified in any order and any combination, separated by commas. The valid parameters are NOEVM and GVCTL(n).

NOEVM

The NOEVM parameter causes GDDRMAIN to initialize the EVM subtask, but not start it. This is useful if GDDRMAIN is being brought up to work on or correct some global variable problem which needs to be rectified prior to starting EVM.

GVCTL(n)

The GVCTL(n) parameter allows you to specify the initial value of GVCW. If you do not specify any value, the default value for GVCW is 2.



GDDRGVX utilityThe GDDRGVX utility program provides global variable analysis and management functions for the DIV dataset. Its functions are requested by the following parameters:

◆ DSPLIST

◆ DIVLIST

◆ DSPSAVE

◆ RELOAD

DSPLISTThe DSPLIST parameter produces a formatted list of the contents of the global variable data space.

DIVLIST The DIVLIST parameter produces a formatted list of the contents of the DIV. This parameter may only be used when GDDRMAIN is not active. The output format is identical to DSPLIST. The utility JCL requires a GDDRGVDS DD pointing to the DIV dataset.

DSPSAVE The DSPSAVE parameter copies the contents of the global variable data space to a sequential dataset. The dataset is pointed to by a //GVSAVE DD statement. The output dataset can be used by IDCAMS REPRO to populate a new DIV dataset.

RELOAD The RELOAD parameter copies global variables from an old DIV to a new DIV. The reason to use reload instead of IDCAMS REPRO is that reload will not copy deleted variables. Also, any "gas" in the DIV will be removed. To use the RELOAD parameter, GDDRMAIN must be running. The old DIV is pointed to by a //GDDRGVDS DD statement in the utility JCL, while the //GDDRGVDS DD statement in GDDRMAIN must be pointing to another (empty) DIV.

GDDRGVX utility 221


EMC GDDR system variable integrity and accessTwo locks are used when managing EMC GDDR system variable integrity: the index lock and the update lock. Both locks allow you to record, without serialization, when you are using the index or doing an update, and allow exclusive control by a single user when no use is in progress. If either lock becomes "stuck", it can have negative implications for global variable access.

The lock consists of two words; the first is the exclusive lock, the second is the shared lock. If both words are zero, the lock is completely open. This is the normal state. The lock words can have the combinations of values listed in Table 12.

You can display the locks with GDDRGVX DSPLIST. GDDRGVX DSPLIST displays the time when the exclusive lock was set, as well as the job which set it. There is no display of jobs which set the shared lock, but GDDRGVX DSPLIST indicates the last time the shared lock was changed. You can also use the LOCK command to display this information.

You can clear a stuck or broken lock by using the LOCK command.

Index lockThe index lock indicates that the global variable index is in use or is being rebuilt. If the index is being rebuilt, it cannot be used by anyone.

If the exclusive lock becomes stuck, no one will be able to use the index and performance will suffer greatly. However, no functions will fail. If the exclusive lock is set for more than 5 seconds and a task tries to use the index, a message is issued.

If the shared lock becomes stuck, the index will not be able to be rebuilt when it needs to be done and performance will suffer, but not as severely as a stuck exclusive lock. Again, no functions will fail. A message is issued if a reindex is desired but cannot be done because the shared lock is not zero. If this message occurs with any frequency, investigate and consider manually clearing the lock.

Table 12 Possible lock states

First word - exclusive value

Second word - shared value State

0 0 The lock is open. There is no shared or exclusive use of the resource.

0 positive value The resource is in use by one or more non-exclusive users. The shared value is the number of users. No one is requesting exclusive use.

1 positive value The resource is in use by one or more non-exclusive users, but one user is waiting for exclusive use. If the shared word does not go to zero within a very short period of time, the lock is stuck. This is referred to as 'shared lock stuck'.

1 1 The lock is locked, or set. One task has exclusive use of the resource and any other task which wants to use it must wait or take alternative action. If the exclusive word does not go to 0 within a very short period of time, the lock is stuck. This is referred to as 'exclusive lock stuck'.

other than 0 or 1 any value The lock is broken. The exclusive word should only have the value 0 or 1.

0 or 1 negative value The lock is broken. The shared word should only have non-negative values.



Update lock

The update lock is used (shared) when updates to global variables are made which change the structure of the data space. The exclusive lock is used by GVT when it writes the data space out to the DIV.

If the exclusive lock becomes stuck, no updates to global variables which require structural changes can be made (adding a new variable, changing a value to a longer value). If this occurs, requests will fail and messages will be issued.

If the shared lock becomes stuck, GVT will not be able to write the data space out to the DIV. However, if GVT is unable to obtain the update exclusive lock, it will force it (that is, set the lock words to 1,0) after some period of trying to obtain the lock. A stuck shared update lock will automatically be unstuck if GVT is active and if a DIV write needs to be done. Note that there is no impact of a stuck shared update lock except in these conditions.

EMC GDDR system variable integrity and access 223


Starting/Stopping the Heartbeat MonitorYou can normally manage the EMC GDDR Heartbeat Monitor (HBM) with the CA-OPS/MVS System State Manager (SSM). For details, refer to Customize CA-OPS/MVS for EMC GDDR, “Step 10: Define the EMC GDDR monitoring started tasks to CA-OPS/MVS SSM” on page 68.

However, if you should need to start these processes manually after they have been placed in a JES proclib, issue the MVS command:

S GDDRproc

If you should need to stop these processes manually after they have been placed in a JES proclib, issue the MVS command:

C GDDRproc

where:

proc

Stands for HBM.


This glossary contains terms related EMC GDDR and to disk storage subsystems.

AAPI Application Programming Interface, a set of routines that an application program

uses to request and execute tasks performed by a computer’s operating system.

BBCV Business Continuance Volume, a standard Symmetrix device with special attributes

that allow it to independently support applications and processes, such as backup operations, restore operations, decision support operations, and application testing. BCV devices are available through the EMC TimeFinder/Mirror software.

BCV device A standard Symmetrix device with special attributes that allow it to independently support applications and processes.

BCV mirror A standard device mirror (one of M2, M3, or M4) that is assigned to the BCV device upon establishing or re-establishing a BCV pair.

BCV pair A standard device and a BCV device attached together.

CC-System A EMC GDDR C-System is the controlling LPAR for each of the EMC GDDR sites.

The main functions of a EMC GDDR C-System are to:

◆ Control the recovery after an outage

◆ Control a planned site swap

The EMC GDDR C-Systems do not run any production workload.

C-System masterfunction

The C-System that is currently responsible for monitoring DASD status and DASD mirroring. It is also responsible for taking action when problems with DASD and DASD mirroring are detected.

C1 Abbreviation for EMC GDDR C-System at the DC1 site.



Glossary


Glossary

CA-OPS/MVS MSF CA-OPS/MVS Multi System Facility (MSF) provides communication between multiple CA-OPA/MVS copies running on different z/OS images.

cache Random access electronic storage used to retain frequently used data for faster access by the channel.

cache slot Unit of cache equivalent to one track.

Cascaded SRDF The ability for a remote volume of a synchronously mirrored pair to simultaneously be the local volume of an asynchronously mirrored pair. Data from a primary site is synchronously replicated to a secondary site, where the volume at the secondary site is the primary volume from which data is asynchronously replicated to a tertiary site.

channel director The component in the Symmetrix subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.

CKD Count-key-data, a data recording format employing self-defining record formats in which each record is represented by a count area that identifies the record and specifies its format, an optional key area that may be used to identify the data area contents, and a data area that contains the user data for the record. CKD can also refer to a set of channel commands that are accepted by a device that employs the CKD recording format.

Concurrent SRDF The ability for a single primary volume to be remotely mirrored to two secondary volumes concurrently. Concurrent SRDF requires that each remote mirror operate in the same primary mode, either both synchronous or both semi-synchronous, but allows either (or both) volumes to be placed into one of the adaptive copy modes.

ConGroup Short name for EMC Consistency Group for z/OS. An EMC mainframe application designed to ensure the consistency of the data remotely copied by the Symmetrix SRDF microcode feature in the event of a rolling disaster.

consistency group The consistency group is the key to ConGroup. The consistency group is a named group of source (R1) volumes that ConGroup treats as a unit. The volumes can be on multiple Symmetrix units and can include both mainframe and open systems devices.

When ConGroup detects any I/O to a volume in a consistency group that cannot communicate with its mirror, ConGroup suspends the remote mirroring for all volumes defined for that consistency group before completing the intercepted I/O, and returns control to the writing application. In this way, the ConGroup utility prevents dependent I/O from being issued by the application. This ensures the integrity and consistency of the data at the remote site.

DDASD Direct access storage device, a device that provides nonvolatile storage of computer

data and random access to that data.

data availability Access to any and all user data by the application.

dataset In a mainframe system, a collection of data in one of several prescribed arrangements and described by control information in the volume label or the catalog. A dataset may be equivalent to a file in some cases, as in physical sequential files, or several datasets may make up the components of a file.

DDNAME Data definition name, the logical name of a file within an application.


Glossary

delayed fast write There is no room in cache for the data presented by the write operation.

dependent write A write that is not issued by an application unless some prior I/O operation has completed. An example of a dependent write is a database update. When updating a database, a database management system (DBMS) takes the following steps:

1. The DBMS writes to the disk containing the transaction log.

2. The DBMS writes the data to the actual database dataset.

3. The DBMS writes again to the log volume to indicate that the database update was successfully made.

device A uniquely addressable part of the Symmetrix subsystem that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry required to locate, read, and write data.

device address The hexadecimal value that uniquely defines a physical I/O device on a channel path in an z/OS environment. See also “unit address.”

device number The value that logically identifies a disk device in a string.

diagnostics System level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking.

director The component in the Symmetrix subsystem that allows Symmetrix to transfer data between the host channels and disk devices. See also “channel director.”

disk director The component in the Symmetrix subsystem that interfaces between cache and the disk devices.

DSN Dataset name. A DSN consists of a series of dot-delimited qualifiers, each of which comprises a maximum of eight characters (for example, PAYROLL.DSN1.ESDS). A DSN has a maximum of 44 characters. When referencing the member of a partitioned dataset, the maximum length is 54 bytes, including 44 bytes for the name of the PDS, and up to eight bytes for the member name, enclosed in parentheses.

EEnginuity Enginuity is the operating environment for EMCs Symmetrix Enterprise Storage

Platforms. Enginuity provides functional services for both its host Symmetrix systems as well as for a large suite of EMC Storage Application software.

ESA Enterprise System Architecture (mainframe systems only).

ESCON Enterprise Systems Connection, a set of IBM and vendor products that connect mainframe computers with each other and with attached storage, locally attached workstations, and other devices using optical fiber technology and dynamically modifiable switches called ESCON directors.

ESCON director Device that provides a dynamic switching function and extended link path lengths (with XDF capability) when attaching an ESCON channel to a Symmetrix serial channel interface.

ESP Enterprise Storage Platform, the software for EMC Symmetrix storage subsystems. It allows storage of and access to mainframe and open systems data that is stored on the same Symmetrix storage subsystem.


Glossary

Ffast write In Symmetrix, a write operation at cache speed that does not require immediate

transfer of data to disk. The data is written directly to cache and is available for later destaging.

FB record Fixed block record, a fixed-length, blocked record in a mainframe dataset. The dataset can contain truncated (short) blocks.

FBA Fixed Block Architecture, a data record format that uses data blocks of fixed size. The blocks are addressed by block numbers relative to the beginning of the particular file. FBA is used by open systems computers while a different scheme, CKD, is used by mainframe computers.

FBAM Fixed Block Architecture, Meta-volume.

FICON Fibre Connectivity, a high-speed I/O interface for mainframe computer connections to storage devices. FICON channels increase I/O capacity to make them up to eight times as efficient as ESCON channels.

file In z/OS terminology, a file is an abstraction that represents a collection of data at the application level. In some cases, such as physical sequential files, a dataset and a file may be considered equivalent. In other cases, several datasets may be presented to the application as a single logical file. In a partitioned dataset, a subset of the dataset, called a member, is considered a file.

Ggatekeeper A small logical volume on a Symmetrix storage subsystem used to pass commands

from a host to the Symmetrix storage subsystem. Gatekeeper devices are configured on standard Symmetrix disks.

GDDR Acronym for Geographically Dispersed Disaster Restart.

GDDR Complex An EMC GDDR Complex is a two-site cluster of GDDR systems. Each GDDR Complex can manage one consistency group. See “ConGroup” and “consistency group.”

GDG Generation Data Group, a collection of physical sequential files that are logically related by their content, and usually represent a history of the data over some period of time. The group is created through use of administrative utilities, and individual datasets in the group called generation datasets (GDS) are created by running user programs.

GDS Generation Data Set, elements of a generation data group referred to by a GDG base name, followed by a number enclosed in parentheses. The number indicates the relative chronological position of each GDS.

GNS Group Name Service. GNS is the Symmetrix group definition sharing facility. GNS allows you to define a group of devices (and the controllers on which they reside) once, in one place, and then use that single definition across multiple EMC products on multiple platforms. That is, you can use group definitions created through GNS on a mainframe system with EMC software products running on open systems hosts.


Glossary

GNS group A Group Name Service group. Each GNS group is a list of controllers and devices that reside on those controllers. The controllers and devices may reside on one Symmetrix storage subsystem or on different Symmetrix storage subsystems. If a GNS group spans more than one Symmetrix storage subsystem, each Symmetrix unit holds only its portion of that single definition.

Each group is a collection of controllers, and the devices that reside on those controllers. For groups that span Symmetrix storage subsystems, the definition is stored as a set of components on different Symmetrix storage subsystems. Each Symmetrix storage subsystem holds its portion of that single definition.

gigabyte (GB) 109 bytes.

IID Identifier, a sequence of bits or characters that identifies a program, device, controller,

or system.

I/O device An addressable input/output unit, such as a disk device.

KK Kilobyte, 1024 bytes.

Llocal volume A Symmetrix logical volume that is not participating in SRDF operations. All CPUs

attached to the Symmetrix may access it for read/write operations. It is available for local mirroring or dynamic sparing operations to the Symmetrix unit in which it resides only.

logical volume A user-addressable unit of storage. In the Symmetrix subsystem, the user can define multiple logical volumes on a single physical disk device.

LPAR Logical partitioning, a system of splitting a mainframe computer‘s total resources into smaller units. The units essentially act as separate machines. Each unit can run with its own instance of the operating system and applications. The units, however, can communicate with each other.

MMB Megabyte, 106 bytes.

mirrored pair A logical volume with all data recorded twice, once on each of two different physical devices.

mirroring The Symmetrix maintains two identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, Symmetrix automatically uses the other disk device.

multi-site workloadconfiguration

In a multi-site workload configuration, the production workload runs at both the primary and secondary sites. See also “primary site” and “secondary site.”

MSC MSC (Multi-Session Consistency) is an EMC technology that provides consistency across multiple SRDF groups within the same Symmetrix subsystem or multiple Symmetrix subsystems.


Glossary

PPDS Partitioned Dataset, a composite mainframe dataset that is much like a directory in

UNIX containing files, for example, source files. The members in a PDS are usually of the same type of data, for example, C language source files or header files.

physical ID Physical identification number of the Symmetrix director for EREP usage. This value automatically increments by one for each director installed in Symmetrix. This number must be unique in the mainframe system. It should be an even number. This number is referred to as the SCU_ID.

primary site The primary site is the site where the production workload is located. The primary site is typically the same as the primary DASD site.

primary DASD site The primary DASD site is the site where the source (R1) DASD is located. The primary DASD site is typically the same as the primary site.

RR1 See “source volume (R1).”

R2 See “target volume (R2).”

R21 A dual-role SRDF R2/R1 device on the secondary site which acts as both an R2 to the primary site and an R1 to the tertiary site.

rolling disaster A rolling disaster is more common than an immediate catastrophic failure. A rolling disaster is a series of events happening over a period of time that lead to data corruption until a catastrophic failure finally occurs. Each rolling disaster is delimited by two fixed points: the time when the first failure occurs and the time when the disaster is complete. The period between these two times is the rolling disaster.

RPO Recovery Point Objective. The Recovery Point Objective is a point of consistency to which a user wants to recover or restart. It is measured in the amount of time from when the point of consistency was created or captured to the time the disaster occurred. This time equates to the acceptable amount of data loss.

Zero data loss (no loss of committed transactions from the time of the disaster) is the ideal goal, but the high cost of implementing such a solution must be weighed against the business impact and cost of a controlled data loss.

Some organizations like banks have zero data loss requirements. The data base transactions entered at one location must be replicated immediately to another location. This can have an impact on application performance when the two locations are far apart. On the other hand, keeping the two locations close to one another might not protect against a regional disaster like the power outages or hurricanes.

Defining the required RPO is usually a compromise between the needs of the business, the cost of the solution, and the risk of a particular event happening.

Ssecondary site The secondary site is the site where the contingency or standby systems are located.

secondary DASD site The secondary DASD site is the site where the target (R2) DASD is located. The secondary DASD site will typically be the same as the secondary site.


Glossary

single site workloadconfigurations

Single site workload configurations are configurations in which the primary site is the site where the production workload is located. See also “primary site.”

sites DC1 and DC2 Site DC1 and DC2 are the primary and secondary data centers for critical production applications and data. They are considered fully equivalent for strategic production applications, connected with highly redundant direct network links.

At all times, all production data is replicated synchronously between the two sites.

source volume (R1) A Symmetrix logical volume that is participating in SRDF operations. It resides in the “local” Symmetrix unit. All CPUs attached to the Symmetrix may access a source volume for read/write operations. All writes to this volume are mirrored to a “remote” Symmetrix unit. A source volume is not available for local mirroring operations. See also “target volume (R2).”

SRDF Symmetrix Remote Data Facility. SRDF consists of the microcode and hardware required to support Symmetrix remote mirroring.

SRDF/S SRDF/Synchronous. SRDF/S is a business continuance solution that maintains a real-time (synchronous) copy of data at the logical volume level in Symmetrix systems in the same or separate locations. The SRDF/S operation is transparent to the host operating system and host applications. It does not require additional host software for duplicating data on the participating Symmetrix units.

storage control unit The component in the Symmetrix subsystem that connects Symmetrix to the host channels. It performs channel commands and communicates with the disk directors and cache. See also “channel director.”

sysplex System complex. A processor complex which is formed by loosely coupling mainframe processors together into a single unit, using channel-to-channel adapters or ESCON or FICON fiber optic links.

system The word system or systems used in this guide refers to a z/OS image and all systems tasks and applications running in it.

Ttarget volume (R2) A Symmetrix logical volume that is participating in SRDF operations. It resides in the

“remote” Symmetrix unit. It is paired with a source volume in the local Symmetrix unit 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. See also “source volume (R1).”

trip The action ConGroup takes when it detects that one or more source (R1) devices in a consistency group cannot propagate data to their corresponding target (R2) devices. During a trip, ConGroup suspends all the source (R1) devices in the consistency group. This suspension ensures that:

• The data flow to the target (R2) side is halted.

• The data on the remote side of the configuration is consistent.

Uunit address The hexadecimal value that uniquely defines a physical I/O device on a channel path

in an MVS environment. See also “device address.”


Glossary

Vvolume A general term referring to a storage device. In the Symmetrix subsystem, a volume

corresponds to a single device visible to the host. In the context of host-based, volume manager software, a volume is a logical unit of disk storage that may comprise storage on one to many Symmetrix devices.


Documents

EMC GDDR for SRDF/S with ConGroup Product Guide · PDF fileUsing OPSVIEW facilities for EMC GDDR administration ..... 159 Ensuring MSF connections between C-Systems