dell · emc gddr product guide 3 preface

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

EMC® GDDR for SRDF®/AVersion 3.0

Product GuideP/N 300-006-605

REV A04

EMC GDDR Product Guide 2

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

Published January, 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.................................................................................................................................................... 11

Chapter 1 Installing EMC GDDR Introduction ............................................................................................................. 16 Pre-installation tasks .............................................................................................. 17

Mainframe environment requirements ......................................................... 17Minimum software requirements .................................................................. 17Minimum hardware requirements ................................................................ 18

Installation procedure ............................................................................................ 19Before you begin ............................................................................................... 19Gather EMC GDDR installation information ............................................... 20Install EMC GDDR ........................................................................................... 21Run the installation jobs .................................................................................. 26

Post-installation tasks............................................................................................. 27

Chapter 2 Integrating EMC GDDR Overview.................................................................................................................. 30 Update system parameter files ............................................................................. 31 Create parameter members for SRDF Host Component on C-Systems ......... 34 Specify EMC GDDR security ................................................................................ 35

EMC GDDR RACF functional groups........................................................... 35Summary of RACF permissions ..................................................................... 35RACF authorization for OMVS ...................................................................... 36RACF authorization for HMC LPAR actions ............................................... 36

Install EMC GDDR C-System started procedures ............................................. 38Allocate the parameter backup dataset ......................................................... 39Customize EMC z/OS Console Monitor started procedures .................... 39Customize member GDDRPROC .................................................................. 40

Customize CA-OPS/MVS for EMC GDDR ........................................................ 41Include EMC GDDR libraries in OPSVIEW REXX exec ............................. 41Make EMC GDDR AOF rules available to CA-OPS/MVS ........................ 41Set REXX and TSO transaction limits in the CA-OPS/MVS OPSMAIN parameters ......................................................................................................... 42Enable SMF Support in CA-OPS/MVS......................................................... 43Change CA-OPS/MVS access rules............................................................... 43Customize EMC GDDR user exit 7 (optional).............................................. 43Update CA-OPS/MVS started procedure OPSOSF .................................... 44Update the UNIX system service directory .................................................. 44


Define the EMC GDDR monitoring started tasks to CA-OPS/MVS SSM 45Merge CA-OPS/MVS user applications........................................................ 46Update CA-OPS/MVS CCI parameters ........................................................ 46

Modify CA-OPS/MVS to use the GDDRMSG table .......................................... 47 Configure EMC GDDR........................................................................................... 48

Prepare and load EMC GDDR parameters ................................................... 48Specify EMC GDDR job defaults .................................................................... 53Configure the EMC GDDR HMC interface................................................... 54Configuring multiple EMC GDDR parameter members (optional).......... 56Modifying EMC GDDR user exits (optional)................................................ 56

Chapter 3 Using EMC GDDR Online Facilities Introduction ............................................................................................................. 58 EMC GDDR administrator facilities..................................................................... 59

Option A — Automation: Toggle GDDR Automation On/Off ................. 61Option C — Config: View GDDR configuration.......................................... 62Option H — HMC: Manage HMC.................................................................. 63Option HA - HMC Actions: Perform HMC LPAR actions ......................... 65Option J — JobVals: View or change default job values ............................. 67Option M — MsgOut: Specify GDDR message output options................. 69Option P — Parms: Manage GDDR parameters .......................................... 70Option Q — Queue: Manage GDDR internal command queue ................ 93Option S — SMF: Manage SMF Logging Options ....................................... 94

EMC GDDR ISPF profiles ...................................................................................... 96 Using OPSVIEW facilities for EMC GDDR administration.............................. 97

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

Chapter 4 EMC GDDR Parameters Introduction ........................................................................................................... 100

User environment parameters ...................................................................... 100Performance and tuning parameters ........................................................... 100

Parameter statement processing ......................................................................... 101Components..................................................................................................... 101References and specifications........................................................................ 101Associations ..................................................................................................... 101Validation......................................................................................................... 102

Loading the parameters ....................................................................................... 103Validating the environment .......................................................................... 103Backing up existing global variables............................................................ 103Loading global variables................................................................................ 103

Parameter descriptions......................................................................................... 104 User environment parameters............................................................................. 105

AUTOCBU.U or P.siteid.central-processing-complex-name........................... 105BCV.siteid.MSC............................................................................................... 106BCV.DC1.ONLY.............................................................................................. 107BCV.DC3.ONLY.............................................................................................. 108CF_STRUCTURE.REBUILD .......................................................................... 109CONCAT.JCLLIB.system-name.seq............................................................. 110CONCAT.SKELS.system-name.seq ............................................................. 111CONT.system-name ....................................................................................... 112COUPLE_DS.REALIGN................................................................................. 113siteid.C.System.Systemid............................................................................... 114GDDR.CALL_OVERRIDE ............................................................................. 115

EMC GDDR Product Guide4

GDDR.CONFIG .............................................................................................. 116GDDRVAR_BACKUP.................................................................................... 117GNS.siteid.loc.jtype ........................................................................................ 118HMC.siteid ...................................................................................................... 119HMC_BYPASS.siteid...................................................................................... 120HostComponent_CntlDsn............................................................................. 121IPL.system-name.siteid.................................................................................. 122IPLBCVS.system-name.siteid ....................................................................... 124JA_ACT_GK.siteid.......................................................................................... 125siteid.LPAR.system-name ............................................................................. 126MSC_GROUPNAME.siteid........................................................................... 127MSFID.system-name ...................................................................................... 128PSTR.siteid.sysid.strname ............................................................................. 129ResourcePak_STC_Name.c-system-name................................................... 130RESUME_GK.DC3.......................................................................................... 131SITE.system-name .......................................................................................... 132SRDFA.Devices.siteid .................................................................................... 133sPLX.system-name.type.aorp.siteid............................................................. 134WTOR_RETRIES............................................................................................. 135WTOR_Wait_Interval .................................................................................... 136

Performance and tuning parameters ................................................................. 137CF_REBUILD_TIMEOUT.siteid ................................................................... 137ECGCLEAN.Task.Number ........................................................................... 138Event monitor state check interval............................................................... 139Seconds between GDDR heartbeats............................................................. 140HMC_Timeout.siteid ..................................................................................... 141Missing heartbeat interval............................................................................. 142Max missing heartbeat intervals .................................................................. 143

Audit monitoring parameters............................................................................. 144SMF.LOG ......................................................................................................... 144

Chapter 5 EMC GDDR Maintenance Procedures Setting up a new EMC GDDR C-System........................................................... 148 Renaming an existing EMC GDDR C-System .................................................. 150 Adding a new production system or sysplex to EMC GDDR ....................... 151 Changing the MSC group name ......................................................................... 153 Adding new RDF groups to EMC GDDR ......................................................... 154 Adding new devices to EMC GDDR ................................................................. 157 Removing an RDF group from EMC GDDR control ....................................... 158 Removing devices from EMC GDDR control................................................... 159 Removing a system or a sysplex from EMC GDDR ........................................ 160

EMC GDDR AOF rule set.............................................................................. 160Update CA-OPS/MVS MSF parameters..................................................... 160Update CA-OPS/MVS CCI parameters...................................................... 160

Special cases........................................................................................................... 161Page datasets .................................................................................................. 161Non-LOGR couple datasets ......................................................................... 161

Chapter 6 EMC GDDR Audit Monitoring Facility Overview................................................................................................................ 164

Global variable changes................................................................................. 164Messages .......................................................................................................... 164State changes ................................................................................................... 164


CA-OPS/MVS environment changes .......................................................... 164 Implementation tasks ........................................................................................... 165

Message logging implementation................................................................. 165GDDR SAY and state monitoring implementation ................................... 165Global variable monitoring implementation .............................................. 165

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

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

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

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

Exit specifications .................................................................................................. 172GDDRUX01...................................................................................................... 172GDDRUX02...................................................................................................... 172GDDRUX03...................................................................................................... 173GDDRUX04...................................................................................................... 173GDDRUX05...................................................................................................... 173GDDRUX06...................................................................................................... 174GDDRUX07...................................................................................................... 175

Appendix B Parameter Validation RulesSyntax rules ............................................................................................................ 178Parameter statements providing component specifications ........................... 179Consistency rules ................................................................................................... 180Completeness rules ............................................................................................... 181

Appendix C EMC GDDR z/OS Console Monitor Introduction ........................................................................................................... 184 z/OS Console Monitor — GDDRPBAL............................................................. 185 z/OS operator console commands ..................................................................... 186 BAL command processor — BALC .................................................................... 187

BAL CSC ports................................................................................................. 188CSC RTokens ................................................................................................... 188

Index ...................................................................................................................................................... 189


Title Page

Figures

1 EMC JCL customization utility ........................................................................................... 242 EMC JCL customization utility completed panel ............................................................. 253 EMC GDDR Administrator Primary Options menu ...................................................... 484 Parameter Management Options menu ............................................................................ 495 Specify GDDR ISPF Skeleton Dataset panel .................................................................... 496 Specify GDDR Procedure Library panel ............................................................................ 507 Specify GDDR Parameter Dataset panel .......................................................................... 508 Load GDDR Parameters panel ............................................................................................ 519 Parameter Member Edit Session panel .............................................................................. 5110 Confirm GDDR Parameter Load panel .............................................................................. 5211 CA-OPS/MVS OPSVIEW Primary Options panel ........................................................... 5812 GDDR Primary Options menu ............................................................................................ 5813 GDDR Administrator Primary Options panel .................................................................. 5914 View GDDR Configuration panel ....................................................................................... 6215 HMC Management Options panel ..................................................................................... 6316 HMC Discovery Results panel ............................................................................................ 6417 Specify HMC Community Names panel ........................................................................... 6418 Perform HMC LPAR Actions panel ................................................................................... 6519 View or Change Default Job Values panel ........................................................................ 6720 Set Output Message Levels by Program panel ................................................................. 6921 Add Program to MsgLevel/Debug/Trace List panel ..................................................... 6922 Parameter Management Options panel ............................................................................. 7023 Create GDDR Parameter Backup panel ............................................................................. 7124 Restore GDDR Parameters from Backup panel ................................................................ 7225 GDDR Parameter Backup Member Selection panel ......................................................... 7226 Modify GDDR Parameter Backup Member Information panel ..................................... 7327 Specify GDDR Parameter Dataset panel ........................................................................... 7428 Load GDDR Parameters panel ............................................................................................ 7429 Load GDDR Parameters Help panel .................................................................................. 7530 Confirm GDDR Parameter Load panel .............................................................................. 7631 GDDR Parameter Load Datasets panel .............................................................................. 7732 Select the C-System(s) where parameter changes are to be made ................................. 7933 View/Update GDDR Parameter Values panel ................................................................. 7934 View or Change GDDR Tuning Parameters panel (screen 1 of 2) ................................. 8035 View or Change GDDR Tuning Parameters panel (screen 2 of 2) ................................. 8036 View or Change Device Parameters panel (screen 1 of 2) ............................................... 8137 View or Change Device Parameters panel (screen 2 of 2) ............................................... 8138 View or Change Allocation Values panel (screen 1 of 2) ................................................ 8239 View or Change Allocation Values panel (screen 2 of 2) ................................................ 8240 View or Change Dataset Parameters panel (screen 1 of 3) .............................................. 83


Figures

41 View or Change Dataset Parameters panel (screen 2 of 3) .............................................. 8342 View or Change Dataset Parameters panel (screen 3 of 3) .............................................. 8443 View or Change HMC Parameters panel (screen 1 of 3) ................................................. 8544 View or Change HMC Parameters panel (screen 2 of 3) ................................................. 8545 View or Change HMC Parameters panel (screen 3 of 3) ................................................. 8646 View or Change GDDR GNS Parameters panel ............................................................... 8647 Specify Default Call Override panel ................................................................................... 8748 View GDDR User Options panel ......................................................................................... 8749 View/Update GDDR Component Lists panel .................................................................. 8850 System Exclude List panel .................................................................................................... 8851 Specify CBU Site pop-up display ........................................................................................ 8952 Site CBU Processor List panel .............................................................................................. 8953 HMC Bypass List Display panel .......................................................................................... 8954 Add LPAR Name to HMC Bypass List panel ................................................................... 9055 View GDDR State Values panel (screen 1 of 2) ................................................................. 9056 View GDDR State Values panel (screen 2 of 2) ................................................................. 9157 Manage GDDR Internal Command Queue panel ............................................................. 9358 View or Change SMF Logging Options panel .................................................................. 9459 Change GDDR ISPF Profile Variables panel ..................................................................... 96


Title Page

Tables

1 Mainframe environment requirements .............................................................................. 172 Minimum hardware requirements ..................................................................................... 183 Installation tasks .................................................................................................................... 194 RIMLIB library contents ....................................................................................................... 235 SRDF Host Component parameter members ................................................................... 346 RACF functional groups ...................................................................................................... 357 RACF permissions ................................................................................................................ 358 Parameter statements providing component specifications ......................................... 179


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.

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 Concepts and Facilities Guide

◆ EMC GDDR Operations Guide

◆ EMC GDDR Message and Code 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


Preface

◆ EMC Consistency Group for z/OS Product Guide

◆ 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 describes the EMC GDDR installation procedure. The topics are:

◆ Introduction .................................................................................................................... 16◆ Pre-installation tasks...................................................................................................... 17◆ Installation procedure.................................................................................................... 19◆ Post-installation tasks .................................................................................................... 27

Installing EMC GDDR

Installing EMC GDDR 15

Installing EMC GDDR

IntroductionThis guide 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.

Note: To improve readability, the term EMC GDDR is used throughout this guide in place of the full product name, EMC Geographically Dispersed Disaster Restart.

EMC GDDR is a mainframe software product that standardizes and automates business recovery following both planned outages and disasters, 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.

Refer to the EMC GDDR Concepts and Facilities Guide for a high-level view of EMC GDDR functionality.


Installing EMC GDDR

Pre-installation 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 requirementsEMC 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.0 are as follows:

◆ z/OS

◆ IBM Hardware Management Console (HMC) API

◆ CA-OPS/MVS

◆ SRDF®/Host Component

◆ ResourcePak® Base with SRDF/A multi-session consistency (MSC)

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 as follows:

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

If you want to install Read the installation description in

ResourcePak Base for z/OS EMC ResourcePak Base for z/OS Product Guide

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

TimeFinder®/Mirror for z/OS EMC TimeFinder/Mirror for z/OS Product Guide

TimeFinder/Clone Mainframe SNAP Facility EMC TimeFinder/Clone Mainframe SNAP Facility Product Guide

Pre-installation tasks 17

Installing EMC GDDR

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

Note: EMC GDDR is compatible with SRDF Automated Recovery functionality.

SRDF/A MSC has the following additional gatekeeper requirements:

◆ There must be one or more gatekeeper devices for each MSC-controlled RDF group. These gatekeeper devices must be in OS configuration as OFFLINE at IPL- as regular local devices (not BCV, SRDF, SAV, and so forth).

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

Table 2 Minimum hardware requirements

Item Requirements

Logical processors 2

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


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 beginEMC 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 “Pre-installation tasks” on page 17 and “Gather EMC GDDR installation information” on page 20

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 21

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

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 97 for assistance with administration tasks that are performed using the CA-OPS/MVS - OPSVIEW Primary Options panel shown in Figure 11 on page 58.

Installation procedure 19

Installing EMC GDDR

Gather EMC GDDR installation informationBefore 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.

EMC recommends that you use EMC.fmid if it agrees with your site standards.

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’s 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.


Installing EMC GDDR

Install EMC GDDRThe EMC GDDR kit consists of a PDS containing TSO TRANSMIT images of files needed to perform an SMP/E indirect-library installation on the project. This PDS is packaged as a TSO TRANSMIT file 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 Downloads and Patches. Then, click on your product.

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 you software, correct your registration, or contact EMC in the event of a problem.

Result: You see a page for the product you selected.

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.


http://powerlink.emc.com

Installing EMC GDDR

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.

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.

5. 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.

6. 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

7. 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 1 appears.

Figure 1 EMC JCL customization utility

3. Enter or change the following information on the panel shown in Figure 1 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 ==> ____________________________________________ Edit macro name ==> GDR Product dsname prefix ==> hlq.GDDRvrm Resource Pak Base dsname prefix ==> EMC.SSCFvrm SMP/E dsname prefix ==> EMC.SMPE SMP/E datasets volser ==> ______ Install-to disk volser==> ______ Disk unit name ==>


Installing EMC GDDR

Result: The edit macro is created in the CLIST or EXEC 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 EMC.fmid.

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 2 shows an example of a completed panel as the user is about to press Enter and complete the dialog.

Figure 2 EMC JCL customization utility completed panel

EMC JCL Customization Utility COMMAND ==> _____________________________________________________ Type EXEC on the command line and press ENTER to proceed, or PF3 to exit.

CLIST library ==> ____________________________________________ Edit macro name ==> GDR Product dsname prefix ==> hlq.GDDRvrm Resource Pak Base dsname prefix ==> EMC.SSCFvrm SMP/E dsname prefix ==> EMC.SMPE SMP/E datasets volser ==> ______ Install-to disk volser==> APP005 Disk unit name ==> SYSDA


Installing EMC GDDR

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

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 apply maintenance unless instructed to do so and, if instructed to do so, do not apply maintenance until after EMC GDDR is accepted.


Installing EMC GDDR

Post-installation tasksAfter the SMP/E installation of EMC GDDR is complete, you need to perform several tasks to complete the installation of EMC GDDR. These tasks are described in detail in Chapter 2, ”Integrating EMC GDDR.”

Post-installation tasks 27

Installing EMC GDDR


2Invisible Body Tag

This chapter describes customization procedures for EMC GDDR. The topics are:

◆ Overview ......................................................................................................................... 30◆ Update system parameter files..................................................................................... 31◆ Specify EMC GDDR security........................................................................................ 35◆ Install EMC GDDR C-System started procedures..................................................... 38◆ Customize CA-OPS/MVS for EMC GDDR ............................................................... 41◆ Modify CA-OPS/MVS to use the GDDRMSG table ................................................. 47◆ Configure EMC GDDR.................................................................................................. 48

Integrating EMCGDDR

Integrating EMC GDDR 29

Integrating EMC GDDR

OverviewOnce the contents of the distribution kit have been loaded, complete the steps described in the following sections before using EMC GDDR:

◆ “Update system parameter files” on page 31

◆ “Create parameter members for SRDF Host Component on C-Systems” on page 34

◆ “Specify EMC GDDR security” on page 35

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

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

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

◆ “Configure EMC GDDR” on page 48

Some of the steps involve customization of system components to allow EMC GDDR to run; others involve customization of EMC GDDR to reflect your configuration and your preferences.

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



Update system parameter filesThe following system parameter file updates are required.

HFS files and directories1. Allocate a Hierarchal File System (HFS) file for the USS executables and create the

GDDR USS directories. To do so, customize and submit the #91HFS RIMLIB JOB.

2. Copy the USS executables from the installation USSEXEC dataset to the /usr/gddr USS directory. Add the p attribute to all the USS executables. Add the a attribute to gddrc009 and gddrc00m. To do so, customize and submit the #92CMHFS RIMLIB JOB.

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 36 for assistance with this.

3. 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

4. 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 31


SYS1.PARMLIB( IKJTSOxx )Check to make sure that the following entries exist in AUTHCMD and AUTHPGM. Add any missing entries to the IKJTSOxx member of SYS1.PARMLIB:

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

APF authorizationAPF-authorize the 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:GDDRDAP1 GDDRDAP3 GDDRXCMDGDDR1SMFGDDRSTATGDDRSSVIGDDRQFCNGDDRCGTPSCFRDFME SCFRDFM6 EHCMSCM9 EMCTF ECGCLEAN EHCMSCM6 EHCMSCME SCFRDFM9ECGUTIL

To AUTHTSF add entries:GDDR1SMF

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

/* 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 /* 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

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

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

*/ +



LINKLISTAdd 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 (300).

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.

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.GDDRvrm.LINKLIB)LNKLST ADD NAME(LNKLST) DSN(hlq.OPSvrm.LOAD)LNKLST ADD NAME(LNKLST) DSN(hlq.OPSvrm.USSLOAD)

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

Update system parameter files 33


Create parameter members for SRDF Host Component on C-SystemsDuring planned and unplanned Swap scripts, EMC GDDR uses a utility named in the Utility.IEBGENER GDDR parameter to copy one of four parameter members over the currently used SRDF Host Component RDFPARM member (pointed to by HostComponent_CntlDsn.c-system-name).

The members with the names listed below must be created in the PDS pointed to by HostComponent_CntlDsn.c-system-name. These members contain complete and identical SRDF Host Component initialization parameters, but are different with respect to MSC group definition, as described in Table 5.

Note: For EMC GDDR, it is required that SRDF Host Component running on the C-Systems on DC1 and DC3 uses the same dataset name and member name on the RDFPARM DD statement.

Table 5 SRDF Host Component parameter members

Member Description

SITEUDC1 Used during a swap from DC3 to DC1. Defines an MSC group in MSC-only mode, with the R1 devices at DC1.

SITEUDC3 Used during a swap from DC1 to DC3. Defines an MSC group in MSC-only mode, with the R1 devices at DC3.



Specify EMC GDDR securityThis section details 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 permissionsTable 7 provides an overview of the RACF profiles and permissions required to protect EMC GDDR resources.

Table 6 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$STC For the EMC GDDR monitors, planned and unplanned processes.

Table 7 RACF permissions

EMC GDDR resource owning group

EMC GDDR STC’s user group

EMC GDDR user group

Admin/Sysprog user group

GDDR$ GDDR$STC GDDR$USR 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 neededALTERALTERALTERALTERALTERALTERALTERALTERALTERALTER

FACILITY profileGDDR.CBU.ACTIVEGDDR.CBU.UNDOGDDR.HMC.LISTOBJECTSGDDR.HMC.GETMSGSGDDR.HMC.ACTIONS.system id

Access neededREADREADREADREAD-



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

Specify EMC GDDR security 35


◆ 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 that JES2 command looks like this:

$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.

RACF authorization for OMVSUse 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 actionsThe facility profile GDDR.HMC.ACTIONS.system id provides for site-specific authorization of EMC GDDR LPAR processing. Authorization is enabled through the EMC GDDR panel “Option HA - HMC Actions: Perform HMC LPAR actions” shown on page 65. Following your specification of GDDR.HMC.ACTIONS facility profiles, the Perform HMC LPAR Actions panel will only list the system names (LPARs) for actions by authorized EMC GDDR users. Unprotected system names will be displayed for any EMC GDDR user.

The value of system id corresponds to the system name found in the IPL.system-name.siteid GDDR parameter statement described page 122. Generic or discrete system ID names may be used 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 GDDR.HMC.ACTIONS 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 GDDR.HMC.ACTIONS facility profile:

Example 1 RDEFINE FACILITY GDDR.HMC.ACTIONS.** UACC(NONE) OWNER(GDDR$ADM)

PERMIT GDDR.HMC.ACTIONS.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 systems defined by IPL.system-name.siteid 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 user's GDDR HMC LPAR Actions panel.

Example 2 RDEFINE FACILITY GDDR.HMC.ACTIONS.ZOSESYS1 UACC(NONE) OWNER(GDDR$ADM)

PERMIT GDDR.HMC.ACTIONS.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 by IPL.system-name.siteid are not protected and therefore will be displayed on the GDDR HMC LPAR Actions panel for any user.

Specify EMC GDDR security 37


Install EMC GDDR C-System started proceduresTo use EMC GDDR, the EMC GDDR Event Monitor, Heartbeat Monitor, and z/OS Console Monitor tasks must be started and must remain running on the EMC GDDR C-Systems at all times. You must customize these started procedures and make them available.

Note: It is recommended that automation be used to start the EMC GDDR procedures on the EMC GDDR C-Systems at system startup.

1. Update members GDDREVM 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 GDDREVM, 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 170 provides more information.

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

All of the GDDR monitoring 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 ResourcePak Base and SRDF Host Component linklib datasets are not in the linklist concatenation, add them to the STEPLIB concatenation in each GDDREVM PROC member.



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

parameters.

Backups of EMC GDDR global variables are made when EMC GDDR parameters are loaded, when the EMC GDDR Heartbeat Monitor starts, and when the EMC GDDR administrator procedure ‘Create GDDR Parameter Backup’ is invoked.

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

Note: Ensure that the EMC GDDR parameter GDDRVAR_BACKUP is set to the name of the dataset you allocate.

Customize EMC z/OS Console Monitor started procedures1. 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 GDDR monitoring started procedures.

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: It is recommended that automation be used to start the EMC GDDR z/OS Console Monitor procedure on the 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 GDDR monitoring started procedures.

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: It is recommended that automation be used to start the EMC GDDR z/OS Console Monitor procedure on the GDDR C-Systems at system startup.

Install EMC GDDR C-System started procedures 39


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 SRDF Host Component load library

• Your ResourcePak Base load library

• Your TimeFinder/Mirror load library, if you use TimeFinder/Mirror

• Your TimeFinder/Clone Mainframe SNAP Facility, if you use TFCMSF

• Your ISPF load library

• Your CA-OPS/MVS 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.




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.

Include EMC GDDR libraries in OPSVIEW REXX execEMC 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.

Make EMC GDDR AOF rules available to CA-OPS/MVS1. 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

Customize CA-OPS/MVS for EMC GDDR 41


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 39. 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 11 on page 58), 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 E to enable the GDDR AOF rule set.

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

Set REXX and TSO transaction limits in the CA-OPS/MVS OPSMAIN parameters1. The REXXMAXQUEUE parameter is 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. The OSFRUN and OSFCPU parameters 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. The OSFWAIT parameter sets 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. The OSFOUTLIM parameter limits 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.

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 6, ”EMC GDDR Audit Monitoring Facility,” describes how to set monitoring and retention options.

Change CA-OPS/MVS access rulesThe CA-OPS/MVS access rules must be changed to allow the following:

◆ EMC GDDR to update global variables and use the CA-OPS/MVS OPSCMD function

◆ 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.

GLOBAL and OPSCMD member

IF userid = "gddr_racf_userid" THEN RETURN "ACCEPT"

OPSWTO member

IF userid = "gddr_racf_userid" THEN RETURN "ACCEPT"IF userid = "opsosf_racf_userid" THEN RETURN "ACCEPT"

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.



Update CA-OPS/MVS started procedure OPSOSF

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

1. 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.

2. 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.SCGPvrm', // USRPFX2='hlq.SSCFvrm', // USRPFX4='hlq.SRDFvrm', // USRPFX6='hlq.GDDRvrm'

3. 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=&USRPFX2..LINKLIB // DD DISP=SHR,DSN=&USRPFX4..LINKLIB // DD DISP=SHR,DSN=&USRPFX6..LINKLIB

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

4. 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

Update the UNIX system service directoryAdd 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)

Activate this change by recycling the OPSUSS started procedures.



Note: 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:/gddr:/usr/gddr/source:LIBPATH=$LIBPATH:/usr/gddr:/usr/gddr/source:

Define the EMC GDDR monitoring started tasks to CA-OPS/MVS SSMTo ensure that the EMC GDDR Event Monitor started task (GDDREVM) and the EMC GDDR Heartbeat Monitor started task (GDDRHBM) are kept running at all times on the EMC 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:

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 table 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.

Name/Jobname Desired_State Mode Type PREREQ

GDDREVM UP A GDDREVM JES2 TCPIP

GDDRHBM UP A GDDRHBM JES2 TCPIP

GDDRPBAL UP A GDDRPBAL EMC ResourcePak Base

ACTION_CURRENT ACTION_DESIRED ACTION_RES_TYPE ACTION_TEXT

DOWN UP GDDREVM …START &JOBNAME

DOWN UP GDDRHBM …START &JOBNAME

UP DOWN GDDREVM …CANCEL &JOBNAME

UP DOWN GDDRHBM …CANCEL &JOBNAME

DOWN UP GDDRPBAL …START &JOBNAME

UP DOWN GDDRPBAL …CANCEL &JOBNAME



Merge CA-OPS/MVS user applicationsISPF panel OPSUSER, provided in installation dataset GDDR.ISPPLIB, provides access to EMC GDDR’s online facilities. If you already have user applications accessed through a panel of the same name, you will need to merge the two panels into one panel to provide access to the EMC GDDR online facilities as well as to your existing user applications.

If OPS/MVS is already in use in your environment, you will need to modify the OPSUSER panel to include the EMC GDDR application. You can do this by adding the following EMC GDDR options:

1,'PGM(OI) PARM(GDDROPS1)'

2,'PGM(OI) PARM(GDDROPO1)'

3,'PGM(OI) PARM(GDDRPROF)'

Update CA-OPS/MVS CCI parameters1. 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.

• NODE( …add appropriate parameters for the new system… )

• CONN, ssssssss


2. If CA-OPS/MVS is installed on the production systems, 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


• NODE( …add appropriate parameters for the new system… )

• CONN, ssssssss




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 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 the following items:

◆ The exec that takes you to CA-OPS/MVS using TSO ISPF =6. For example, the following are changes in CAOPS.OPS116T.SAMPLES(OPSVIEWX):

"ALLOC FI(OPSMLIB) REUSE SHR DA('"usrpfx0".PARMLIB'" , "'"usrpfx1".PARMLIB'" , "'"usrpfx2".PARMLIB'" , "'"usrpfx3".PARMLIB'" , "'"prefix".OPSMLIB')"

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

//OPSMLIB DD DISP=SHR,DSN=&USRPFX1..PARMLIB // DD DISP=SHR,DSN=&USRPFX2..PARMLIB // DD DISP=SHR,DSN=&USRPFX3..PARMLIB // DD DISP=SHR,DSN=&USRPFX4..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 2 LPARs named SYS3 and SYS4, the table will be built on each one, as required. The EMC GDDR PARMLIB dataset must be accessible to each LPAR that will execute EMC GDDR.

Temporary changes to the external text can be made using CA-OPS/MVS Opsview, option 2.6. Permanent changes can be made to the GDDRMSG PARMLIB member and then incorporated into the EMC GDDR execution environment by using Option 5, Refresh GDDR Message Table, as shown in Figure 22, “Parameter Management Options panel,” on page 70.

Modify CA-OPS/MVS to use the GDDRMSG table 47


Configure EMC GDDRThe remaining tasks to be completed before you may begin using EMC GDDR are performed using EMC GDDR online facilities. The task descriptions in this section consequently include references to the relevant online procedures.

Note: It is suggested that you review the introductory procedures described in Chapter 3, ”Using EMC GDDR Online Facilities” prior to performing the tasks listed in this section.

Prepare and load EMC GDDR parameters

IMPORTANT!Parameters required by the GDDR Event and Heartbeat monitors may be changed during parameter load processing. For this reason, the GDDR Event and Heartbeat monitors should be stopped before the batch parameter load job is run, and restarted following completion of the parameter load job.

Examine input parameter information The parameters described in Chapter 4, ”EMC GDDR Parameters,” control which systems and devices EMC GDDR is enabled to manage at your site. They will also specify how EMC GDDR handles conditions requiring the use of EMC recovery and business continuity facilities.

Note: Before continuing, carefully examine the parameters that you may specify and how they affect EMC GDDR processing.

Edit the parameter input file1. Reach the CA-OPS/MVS User Applications panel by following the procedure

described on page 58, and select option 1 to view the Administrator Options menu as shown in Figure 3.

Note that asterisks initially appear as the current EMC GDDR state values on the right. Once initialization is complete, subsequent display of this menu will include current state values.

Figure 3 EMC GDDR Administrator Primary Options menu

---------------- GDDR - Administrator Primary Options Menu ------------------Option ===> A Automation Toggle GDDR automation On/Off Current Master: SYS5 C Config View GDDR configuration Primary Site: DC1 H HMC Manage HMC Primary DASD: DC1 HA HMC Actions Perform HMC LPAR actions Automation: ON J JobVals View or change default job values Planned script: None M MsgOut Specify GDDR message output options Unplanned script: None P Parms Manage GDDR parameters Q Queue Manage GDDR internal command queue S SMF Manage SMF Logging Options Enter a GDDR administrator option and press <Enter> Press <F3> to return to CA-OPS/MVS user applications EMC Geographically Dispersed Disaster Restart 03.00.00 Copyright © 2007-2009 EMC Corporation



Note: Option S: Manage SMF Logging Options, a feature of the GDDR Audit Monitoring Facility, is an optional selection on the GDDR Administrator Primary Options menu. If no INITSMF parameter is included in the OPSVIEW parameter member, Option S: Manage SMF Logging Options, does not appear on the GDDR Administrator Primary Options menu.

2. To begin initial parameter customization and load, select option P, Manage GDDR parameters, and press Enter.

The Parameter Management Options menu shown in Figure 4 appears.

Figure 4 Parameter Management Options menu

3. Select option 3, Load GDDR Parameters via batch job.

The Specify GDDR ISPF Skeleton Dataset panel shown in Figure 5 appears.

Figure 5 Specify GDDR ISPF Skeleton Dataset panel

Note: You will initially be presented with several panels requiring you to enter the names of EMC GDDR datasets. These panels will no longer be required once the EMC GDDR parameters have been initialized.

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.

------------------- GDDR - Parameter Management Options Menu ------------------ Option ===> 1 Backup Create GDDR parameter backup 2 Restore Restore GDDR parameters from backup 3 Load Load GDDR parameters via batch job 4 Update Update GDDR parameters 5 Messages Refresh GDDR Message Table Enter a parameter management option and press <Enter> Press <F3> to return to the Administrator Primary Options Menu

----------- GDDR Administration - Specify GDDR ISPF Skeleton Dataset ----------Command ===> Specify the name of a dataset containing the GDDR file tailoring skeletons to use for initial parameter load. (This dataset often has the low-level qualifier 'ISPSLIB' or 'SKELS'.) Dataset name ===> ____________________________________________ Press <Enter> when ready. You may press <F3> to cancel the parameter load.

Configure EMC GDDR 49


4. Enter the name of the ISPSLIB dataset created when you downloaded the install cartridge, and press Enter.

The Specify GDDR Procedure Library panel shown in Figure 6 appears.

Figure 6 Specify GDDR Procedure Library panel

5. Enter the name of the PROCLIB dataset created when you downloaded the install cartridge and press Enter.

The Specify GDDR Parameter Dataset panel shown in Figure 7 appears.

Figure 7 Specify GDDR Parameter Dataset panel

6. Enter the name of the PARMLIB dataset created when you downloaded the install cartridge and press Enter.

------------- GDDR Administration - Specify GDDR Procedure Library ------------Command ===> Specify the name of a dataset containing the GDDR cataloged procedure GDDRPROC to use for initial parameter load. (This dataset often has the low-level qualifier 'PROCLIB'.) Dataset name ===> ___________________________________________ Press <Enter> when ready. You may press <F3> to cancel the parameter load.

------------- GDDR Administration - Specify GDDR Parameter Dataset ------------Command ===> Specify the name of a dataset containing one or more members that specify GDDR parameters. Dsname ===> ____________________________________________ Press <Enter> when ready. You may press <F3> to cancel the request.



A Load GDDR Parameters panel such as the example shown in Figure 8 appears.

Figure 8 Load GDDR Parameters panel

7. To edit any of the parameter members, type an E next to a member name and press Enter.

You will be placed into an edit session for parameter member GDDRMSC and view the panel shown in Figure 9.

Figure 9 Parameter Member Edit Session panel

8. Make changes to the parameter member to reflect your configuration and your installation preferences in accordance with decisions that were made in “Examine input parameter information ” on page 48.

9. When ready, save the member and end the edit session. You will be returned to the Load GDDR Parameters panel (Figure 8 on page 51).

Note: Supplied parameter member GDDRSAMP is a copy of GDDRMSC. It provides a base point for your parameter member changes.

------------- GDDR Administration - Load GDDR Parameters --- Row 1 to 5 of 5 Command ===> Scroll ===> CSR The following row commands may be entered: Current Master: SYS4 S Select a parameter member to load Primary Site: DC1 U Deselect a selected member Primary DASD: DC1 E Edit a parameter member Automation: ON Additional commands are available. Press <F1> to view a complete list. Enter parameter dataset ===> GDDR.GDDR300.PARMLIB Last initialization load from GDDR.GDDR300.PARMLIB(GDDRMSC) When ready, press <F3> to submit job to load specified or selected members Enter CANCEL to exit without loading any parameter members Sel Member Description Selected? --- -------- ------------------------------------------------- --------- _ GDDRMSC

ISREDDE2 GDDR.GDDR300.PARMLIB(GDDRMSC) - 01.08 Columns 00001 00072 Command ===> Scroll ===> PAGE ****** ***************************** Top of Data ****************************** 000001 ********************************************************************* 000002 ******* General Configuration ******* 000003 ********************************************************************* 000004 * Last updates 000005 * 000006 ********************************************************************* 000007 * Configuration characteristics * 000008 ********************************************************************* 000009 GDDR.CONFIG=2SITE,SRDFA 000010 ********************************************************************* 000011 * One or more datasets containing ISPF file tailoring skeletons * 000012 ********************************************************************* 000013 CONCAT.SKELS.T104.2=GDDR.GDDR300.ISPSLIB 000014 CONCAT.SKELS.T111.3=GDDR.GDDR300.ISPSLIB 000015 ********************************************************************* 000016 * One or more datasets containing GDDR cataloged procedures * 000017 ********************************************************************* 000018 CONCAT.JCLLIB.T104.2=GDDR.GDDR300.PROCLIB 000019 CONCAT.JCLLIB.T111.3=GDDR.GDDR300.PROCLIB



Run a test load of the updated parameter fileParameter load processing allows you to validate the parameter input you have prepared without performing any global variable updates. For the initial parameter load, this is highly recommended.

1. On the Load GDDR Parameters panel, select the member(s) to load and press PF3.

The Confirm GDDR Parameter Load panel appears as shown in Figure 10.

Figure 10 Confirm GDDR Parameter Load panel

2. On the Confirm GDDR Parameter Load panel, enter job statement information and specify Y or N for the following options:

• Should this load job replace all current parameter values?

• Should this load job run in test mode and do no updates?

• Should parameter update proceed even with MSF links down?

When you press Enter, the parameter load will be submitted.

3. When the job completes, examine the output, proceeding as follows:

a. Scan for the message “Parameter syntax checking successful". If not present, find all occurrences of “error”, correct the errors indicated, and resubmit the test load job. Otherwise, continue.

b. Scan for the message “Reference check successful”. If not present, find all occurrences of “error”, correct the errors indicated, and resubmit the test load job. Otherwise, continue.

c. Scan for the phrase “assigned default” to determine the default values that have been generated. Ensure these defaults are acceptable.

-------------- GDDR Administration - Confirm GDDR Parameter Load --------------Command ===> A GDDR parameter load job is being scheduled using the following members of dataset GDDR.PARMLIB GDDRMSC To complete job preparation, reply Y or N to each of the following. Should this load job replace all current parameter values? ===> N Should this load job run in test mode and do no updates? ===> Y Should parameter update proceed even with MSF links down? ===> N Enter or change the job statement //GDDRJOB1 JOB (0),'P',MSGLEVEL=(1,1),CLASS=S,MSGCLASS=J, // NOTIFY=GDDRUSR //* //* Press <Enter> when ready. Press <F3> to return without submitting job.



Load the EMC GDDR parametersWhen the parameter values are satisfactory and the validation run is successful, you are ready to perform your first load of the EMC GDDR parameters.

1. Reach the Load GDDR Parameters panel (shown in Figure 8 on page 51), enter the Load command, and press Enter as described above.

This time, however, on the Confirm GDDR Parameter Load panel you must specify the values indicated at the right for options below:

a. Should this load job replace all current parameter values? Y

b. Should this load job run in test mode and do no updates? N

c. Should parameter update proceed even with MSF links down? N

2. When you press Enter, the parameter load job will be submitted.

3. When the job completes, ensure that it did so with completion code 0. Then verify that the correct global variable values were assigned and that updates were successful on all C-Systems by finding the following message for each remote C-System:

GDDP022I Updates complete on MSF id msfid

Then look for the following messages at the end of the listing:

GDDP022I Updates complete on local systemGDDP135E Processing complete, rc = 0

If these messages are present, the parameter load has been successful. Otherwise, determine the reasons why not, correct any errors or environmental conditions, and rerun the parameter load job.

Specify EMC GDDR job defaultsSpecify the job default values to use for EMC GDDR jobs submitted internally by performing the procedure described in “Option J — JobVals: View or change default job values” on page 67.



Configure the EMC GDDR HMC interfacePerform 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 36.

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.5, "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 the 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 2: Specify HMC community names” on page 64 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 2: Specify HMC community names” on page 64.

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 “Option1: Discover HMC objects” on page 63. 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.



Configuring multiple EMC GDDR parameter members (optional)The EMC-supplied parameter GDDRMSC contains models for all the parameter statements. Since your initial parameter load will include all required parameter statements, as well as all optional parameter statements for which you require values different from the defaults, your initial parameter load procedure provides for editing only a single member.

For subsequent parameter load processing, you may choose to utilize the multiple-member feature. This feature allows you to keep parameter statements in different parameter library members, grouping parameters as you wish. Any number of members, any valid member names, and any distribution of parameters among the members are allowed.

To utilize this feature, create the members as needed from the member you used for your initial parameter load. When you perform subsequent parameter maintenance, enter the name of the dataset containing the members, with no members, in the ‘Enter parameter dataset ===>’ field on the Load GDDR Parameters panel (shown in Figure 8 on page 51) and follow the procedure described in “EMC GDDR ISPF profiles” on page 96.

Modifying 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.


3Invisible Body Tag

This chapter describes the EMC GDDR online facility interface. Topics are:

◆ Introduction .................................................................................................................... 58◆ EMC GDDR administrator facilities............................................................................ 59◆ EMC GDDR ISPF profiles ............................................................................................. 96◆ Using OPSVIEW facilities for EMC GDDR administration..................................... 97

Using EMC GDDROnline Facilities

Using EMC GDDR Online Facilities 57

Using EMC GDDR Online Facilities

IntroductionEMC 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, you first must access the CA-OPS/MVS OPSVIEW Primary Options menu shown in Figure 11.

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 11 CA-OPS/MVS OPSVIEW Primary Options panel

On the CA-OPS/MVS Primary Options menu, select option U – User-defined applications and press Enter to view the GDDR Primary Options menu shown in Figure 12.

Figure 12 GDDR Primary Options menu

Note: You may have other CA-OPS/MVS user applications in your system. If so, refer to “Merge CA-OPS/MVS user applications” on page 46 for information about how to integrate the GDDR primary options on the CA OPS/MVS User Applications panel.

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

------------------------ GDDR Primary Options Menu --------------------------- Option ===> 1 Admin Perform Administrator Functions 2 Oper Perform Operator Functions 3 Profile Update ISPF Profile Variables

Type an option number and press <Enter> Press <F3> to return to the OPSVIEW Primary Options Menu

EMC Geographically Dispersed Disaster Restart 03.00.00 Copyright © 2007-2009 EMC Corporation



EMC GDDR administrator facilitiesTo access the EMC GDDR administrator facilities, select option 1 – Perform Administrator Functions on the GDDR Primary Options menu (Figure 12 on page 58) and press Enter. When you select this option, the following panel appears:

Figure 13 GDDR Administrator Primary Options panel

Note: Option S, Manage SMF Logging Options, appears on the GDDR Administrator Primary Options Menu only when the CA-OPSMVS OPSVIEW parameters include INTSMF YES. EMC GDDR Audit Monitoring SMF Logging options can then be specified or modified online as described below.

Control fieldsAt the right side of the panel, the GDDR Administrator 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.

Current Master

Shows 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 administrator actions are allowed only when logged onto the master C-System.

Primary Site

Indicates on which site's CPUs the business applications are currently running.

Primary DASD

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


EMC GDDR administrator facilities 59


Automation

Indicates the current availability of EMC GDDR automation functionality. Automation can be set to either ON or OFF.

Planned script

Planned script indicates which Planned script, if any, is currently in progress. Note that 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’ is displayed in this field.

Unplanned script

Unplanned script indicates which Unplanned script, if any, is currently in progress. Note that 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’ is displayed in this field.

Administrator optionsAt the left side of the panel, a series of administrator 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 A — Automation: Toggle GDDR Automation On/Off

Note: This option is valid only on the master C-System.

When you select the EMC GDDR administrator option Toggle GDDR Automation On/Off, the ability of EMC GDDR operators to run Planned scripts is modified, changing to ON when it is currently OFF and changing to OFF when it is currently ON. The displayed value of the automation setting on the right of the panel reflects the change immediately.

When you set EMC GDDR automation ON, EMC GDDR operators will be able to run both Planned and Unplanned scripts. When you set 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 GDDR Automation status of OFF should be used only when system availability may be impacted by scheduled maintenance activities.

After entering option A, messages similar to the following appear:

GDDR373I GDDR Broadcasting new value for AUTOMATION.FLAG GDDR739I GDDR -> Set GDDR Broadcasting new value for AUTOMATION.FLAG at SYS1 GDDR739I GDDR -> Set GDDR Broadcasting new value for AUTOMATION.FLAG at SYS3

The Administrator Primary Options menu indicates the automation setting at the bottom of the display:


+----------------------------------------------------------------------------+ | Automation has been set OFF, planned/unplanned scripts are now unavailable | +----------------------------------------------------------------------------+



Option C — Config: View GDDR configurationWhen you select the EMC GDDR administrator option View GDDR configuration, the following panel appears:

Figure 14 View GDDR Configuration panel

---------------- GDDR Administration - View GDDR Configuration ---------------- Command ===> Sites: DC1, DC3 Features: SRDF/A, No FBA Devices C-Systems: At DC1, C-System is SYS4 with MSF id SYS4 At DC3, C-System is SYS1 with MSF id SYS1 Press <F3> to return to the previous menu



Option H — HMC: Manage HMCWhen you select the EMC GDDR administrator option Manage HMC, the following panel appears:

Figure 15 HMC Management Options panel

On the HMC Management Options menu, type an option number and press Enter. The options are described below.

Option1: Discover HMC objectsTo discover HMC objects accessible to EMC GDDR, specify option 1. When you do so, a ‘please wait’ pop-up dialog such as the following appears and HMC object discovery is activated:

-------------- GDDR Administration - HMC Management Options Menu -------------Option ===> 1 HMC objects Discover HMC objects Current Master: SYS3 2 Community names Specify HMC community names Primary Site: DC3 Primary DASD: DC3 Automation: ON Enter an HMC management option and press <Enter> Press <F3> to return to the Administrator Primary Options Menu

------------- GDDR Administration - HMC Management Options Menu ------------ Option ===> 1 1 HMC objects Discover HMC objects Current Master: SYS3 2 Community names Specify HMC community names Primary Site: DC3 Primary DASD: DC3 Automation: ON Enter an HMC mana +------- Discovering HMC Objects ---------+ Press <F3> to ret | | | Discovering HMC objects at site DC1 | | | | *** PLEASE WAIT *** | | | +-----------------------------------------+



When the discovery operation completes, you are presented with the HMC Discovery Results panel containing a scrollable display such as the following:

Figure 16 HMC Discovery Results panel

When you are finished examining the results of the discovery operation, press F3 to return to the HMC Management Options panel (Figure 15 on page 63).

Option 2: Specify HMC community namesTo specify the community names that EMC GDDR uses when establishing a session with an HMC console, specify option 2. The following panel appears:

Figure 17 Specify HMC Community Names panel

On the Specify HMC Community Names panel, you may enter the community names EMC GDDR is to use in place of the default, which for each system/site combination is the system name.

--------------- GDDR Administration - HMC Discovery Results --- Row 1 of 203Command ===> Enter <F3> to return to the HMC Management Options 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 Administration - Specify HMC Community Names -- Row 1 of 2 The HMC community name is used when an Lpar initiates an HMC session againstan HMC console. The default community name is the system name. To specify a different community name for a site and system, enter the namein the field for the site and system to which it applies. Press <F3> to return to the HMC Management Options menu.Press Enter to save all changed fields. System Site DC1 Site DC3 -------- -------- -------- SYS4 ________ ________ SYS1 ________ ________ ******************************* Bottom of data ********************************



Option HA - HMC Actions: Perform HMC LPAR actionsHMC 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 HA - HMC Actions: Perform HMC LPAR actions, you are presented with the following panel:

Figure 18 Perform HMC LPAR Actions panel

Note: “IPL.system-name.siteid” in the EMC GDDR Product Guide dicusses required parameters related to the Perform HMC LPAR Actions panel.

On the Perform HMC LPAR Actions panel, each row may show a load address and a load parm or asterisks (the asterisks indicate that load addresses or parms 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 following informational fields are provided on the panel:

Sel

This is the field in which you enter the action code for the action you want to perform for the system-site combination appearing on the row.

System

This field specifies the name of the system associated with the table row.

Site

This field identifies the site through which the action you specify will be taken against the system named on the row.

Load address

This field 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

This field 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 to 3 of 3 Command ===> Scroll ===> CSR These actions may be performed: Current Master: SYS5 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 --- ------- ---- ------------ --------- ---------------------------------- _ ZOSEO018 DC1 5F45 5F16S5M _ ZOSEO019 DC3 5F41 5F16S6M _ ZOSEQ313 DC3 *216 2051S2M



Message

This field is initially blank, but will show a status message if one is available.

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 J — JobVals: View or change default job valuesEMC GDDR sometimes submits jobs internally. Since there is no opportunity for a user to modify the job stream for such a job, the job stream must be customized beforehand. This is done using values applied by EMC GDDR at the time the job is submitted.

Note: This option must be performed as part of EMC GDDR customization following EMC GDDR installation.

To specify the values that will be used for jobs submitted internally by EMC GDDR, enter J on the command line and press Enter. The following panel appears:

Figure 19 View or Change Default Job Values panel

Field descriptions

Note: The fields described in this section should be set as part of the EMC GDDR installation process. Once set, they can be changed at any time afterward.

Enter or change the Job statement

These fields specify the job statement that will be used when a job is submitted internally by EMC GDDR. The values shown in the fields in Figure 19 are those initially set by EMC GDDR. The values that are presented to you reflect the most recent changes entered using this panel, and may be different.

Enter or change the SCF 4-character suffix

This is the suffix appended to ‘SCF$’ to form the DDname on a DD statement in unplanned script jobs and the Event and Heartbeat monitors, associating these with an SCF subsystem. The default value set by EMC GDDR is null, and must be replaced by a valid suffix during EMC GDDR customization.

Enter or change the Host Component prefix

This is the prefix that will be used for internal 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 Administration - Set Values for Internally Submitted Jobs ------ Command ===> Enter or change the job statement ===>//JOBNAME JOB (acct-number),gddr-job,CLASS=A, ===>// MSGCLASS=A,USER=GDDR,NOTIFY=GDDR ===>/*JOBPARM LINES=999999 ===>//* Enter or change the SCF 4-character suffix ===> V580 Enter or change the host component prefix ===> # Enter or change unit for temporary datasets ===> VIO Enter or change Surrogate User ID ===> _______ Enforce: _ Enter or change Jobname Prefix ===> ___ Enforce: _ Press <Enter> to save updates and return Press <F3> to return without saving updates



Enter or change the unit for temporary datasets

This is the user-specified device esoteric value that represents the storage device type to be used when EMC GDDR dynamically allocates temporary datasets.

Enter or change the surrogate User ID

This field allows the EMC GDDR administrator to specify 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 35.

Once the user ID has been provided, and Y has been entered in the Enforce field, EMC GDDR internally submitted jobs will use the surrogate user ID specified in this panel.

Enter or change the jobname prefix

This field allows the EMC GDDR administrator to specify a 3-character prefix that is used as the first three characters of internally submitted EMC GDDR jobnames.

Once the jobname prefix has been provided, and Y has been entered in the Enforce field, EMC GDDR internally submitted jobs will use the jobname prefix specified in this panel.

To save updates

Press Enter to save the values and return to the previous panel. Changes to the job statements made within this panel are validated. If errors in job statement syntax are found, the panel will be redisplayed with the error messages.

These job statements are propagated to Figure 30, “Confirm GDDR Parameter Load panel,” on page 76, and to the GDDR Operator Functions - Specify Parameters For Initial Script Run Panel shown in the EMC GDDR Operations Guide. If the Enforce flags are set, uses of the job statements by these panels are validated to contain the specified surrogate user ID and jobname prefix.



Option M — MsgOut: Specify GDDR message output optionsWhen you select EMC GDDR administrator option M, the following panel appears:

Figure 20 Set Output Message Levels by Program panel

This panel enables you to individually customize message, debug, and trace settings. 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 21 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.

------- GDDR Admin - 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 Administration - 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 P — Parms: Manage GDDR parametersWhen you select the EMC GDDR administrator option P, Manage GDDR parameters, the following panel appears:

Figure 22 Parameter Management Options panel

Specify the desired parameter management option and press Enter to continue.

Note: Appendix A in the EMC GDDR Operations Guide provides additional information about parameter backup and restore functionality.




Option 1: Create GDDR parameter backupEMC GDDR creates GDDR parameter backups when parameters are about to be loaded and during Heartbeat Monitor initialization. However, there may be other times when it is necessary to back up the EMC GDDR parameters. This option allows you to do so.

To back up EMC GDDR parameters, specify option 1. When you do so, a Create GDDR Parameter Backup panel such as the following displays:

Figure 23 Create GDDR Parameter Backup panel

Use this panel to specify the name of the dataset into which the backup should be saved. The dataset name specified as the value of EMC GDDR parameter ‘GDDRVAR_BACKUP’ is the default, but you may change the dataset name to any valid PDS or PDSE.

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.

When you press Enter, backup processing proceeds. When the backup has been saved, a message in the following format displays:

Backed up nnn parameters, nnnn records, into member name Vdddmmmm

Members of the GDDRVAR_BACKUP dataset are named xdddmmmm, where:

x is either

H: generated by manual backups and backups done when the EMC GDDR heartbeat monitor initializes

or

V: generated by batch parameter load processing.

ddd is the day number in the current year.

mmmm is the number of minutes since midnight.

----- GDDR Administration - Create GDDR Parameter Backup ------------- Command ===> Specify the name of a dataset to contain the backup Backup dataset ===> GDDR.GDDR300.BKUPVARS.CNTL Backup information ===> December 19, 2007 at 6:57pm Press <Enter> to create the backup You may press <F3> to cancel the request



Option 2: Restore GDDR parameters from backupTo restore GDDR parameters from backup, specify option 2. When you do so, a the following panel appears:

Figure 24 Restore GDDR Parameters from Backup panel

The Restore GDDR Parameters from Backup panel enables you to specify the dataset name of the global variable backup PDS. By default, this is the name contained in the GDDRVAR_BACKUP parameter.

When you press Enter to select a backup member to use for the restore, the following panel displays:

Figure 25 GDDR Parameter Backup Member Selection panel

You can enter the following row commands:

---------GDDR Administration - Restore GDDR Parameters From Backup ---------- Command ===> Specify the name of the dataset containing GDDR parameter backups Dataset containing backups ===> GDDR.GDDR300.BKUPVARS.CNTL Press <Enter> to select a backup member to use for the restore Press <F3> to cancel the request

-------------- GDDR - Parameter Backup Member Selection Row 43 to 56 of 94Command ===> Scroll ===> CSR Row commands you may enter: S - restore parameters from the selected backup member B - browse the selected backup member I - change backup member information WARNING: When you select a backup member for restore, all existing GDDR parameters are replaced on the current system. Press <F3> to return to the Parameter Management Options Menu Sel Member Backup information --- -------- ------------------------------------------------------- _ V1770490 _ V1770421 _ V1770390 _ V1751272 _ V1720437 _ H3230546 Operator JABCD1 request: November 18, 2008 at 5:46am _ H3220482 Heartbeat Monitor: November 17, 2008 at 8:02am _ H3210183 _ H3200733 _ H3200490

S Performs the restore of parameters from the selected backup member.

B Displays the parameter data in the selected backup member in browse mode.

I Presents the Modify GDDR Parameter Backup Member Information panel shown in Figure 26 on page 73.



This panel allows you to add or change the label for the selected backup member.

Figure 26 Modify GDDR Parameter Backup Member Information panel

----- Administration - Modify GDDR Parameter Backup Member Information ------Command ===> Overtype backup member information. Press <Enter> when ready. Information ===> ___Pre-5773 mcode migration backup - 26Dec08_________________ Press <F3> to return to backup member list without changing member information



Option 3: Load GDDR parameters via batch jobTo load GDDR parameters, specify option 3.

Note: After initialization, this option is valid only on the master C-System.

When you specify option 3, the next screen you see depends upon whether the dataset from whose members the EMC GDDR parameters are to be obtained has previously been specified.

If no such dataset has been previously specified (as when loading EMC GDDR parameters for the first time), or if the specified dataset is invalid or does not exist, you are presented with the Specify GDDR Parameter Dataset panel:

Figure 27 Specify GDDR Parameter Dataset panel

Type the name of an existing dataset and press Enter to proceed. Any dataset name is allowed. For your initial EMC GDDR configuration you may decide to customize the hlq.GDDRvrm.SAMPLIB distribution dataset member GDDRMSC.

After you have entered a valid dataset name, or if you previously specified a valid dataset name, you are presented with a Load GDDR Parameters panel:

Figure 28 Load GDDR Parameters panel

Note: On this panel, you may enter the Cancel command at any time to terminate parameter load processing and return to the Administrator Primary Options menu.

------------ GDDR Administration - Specify GDDR Parameter Dataset ----------Command ===> Specify the name of a dataset containing one or more members that specify GDDR parameters. Dsname ===> ____________________________________________ Press <Enter> when ready. You may press <F3> to cancel the request.

-------------- GDDR Administration - Load GDDR Parameters ---- Row 1 to 9 of 9 Command ===> Scroll ===> CSR The following row commands may be entered: Current Master: ZOSESYS4 S Select a parameter member to load Primary Site: DC1 U Deselect a selected member Primary DASD: DC1 E Edit a parameter member Automation: ON Additional commands are available. Press <F1> view a complete list. Enter parameter dataset ===> GDDR.GDDR300.PARMLIB

Last initialization load from GDDR.GDDR300.PARMLIB(GDDRMSC) When ready, press <F3> to submit job to load specified or selected members Enter CANCEL to exit without loading any parameter members Sel Member Description Selected? --- -------- ------------------------------------------------- --------- _ AUTOSWA0 _ CGRPCAX _ CGRP630 _ GDDREVMP _ GDDRHBMP _ GDDRPARB _ GDDRPARJ _ GDDRMSC _ GDDRPARO



Enter parameter dataset ===>

This value is the dsname of the dataset containing EMC GDDR parameter members. It may be the dataset name you entered previously on the Specify GDDR Parameter Dataset panel (Figure 27 on page 74) or the dataset name you entered previously on this panel.

You may change the dataset name specified in this field. When you do so, the existence, attributes, and availability of the dataset are checked. If any of these checks is unsuccessful, you are returned to the Specify GDDR Parameter Dataset panel where you will have an opportunity to specify a valid dataset name.

You may also include a member name with the dataset name in this field. Doing so allows you to initiate submit processing for the job to load the parameters specified in the member using the Load command on the Load GDDR Parameters panel.

You can press F1 to display a help panel that provides a complete list of commands you may enter:

Figure 29 Load GDDR Parameters Help panel

Loading parameters from a single memberTo load parameters from a single dataset member, enter the dataset name and member name in the Enter parameter dataset field. You may then use the following commands.

Edit

When you enter the Edit command, you are placed into ISPF edit for the dataset and member you specified in the Enter parameter dataset field.

Load

When you enter the Load command, load job setup is initiated with the dataset and member specified in the Enter parameter dataset field as the designated input.

The Load command is invalid if you have not specified both a dataset name and a member in the Enter parameter dataset field.

The following Row Commands are available to modify the parameter members in the GDDR Administration - Load GDDR Parameters panel:

S

To include a member as input, type S next to the name of the member you want to select and press Enter. The Status field will be set to ‘*Select’ for members you have selected, and the member will be included in the input for the parameter load job.

---------- GDDR Help Screen - Load GDDR Parameters ------------------- Command ===> These major commands may be entered: BROWSE Browse the dataset in the 'Enter parameter dataset' field CANCEL Return to the Administrator Primary Option menu EDIT Edit the dataset in the 'Enter parameter dataset' field LOAD Perform parameter process for the dataset and member named in the 'Enter parameter dataset' field These row commands may be entered: B Browse a parameter member D Assign a description for a parameter member E Edit a parameter member S Select a parameter member to load U Deselect a previously selected parameter member X Exclude a parameter member from the table



U

To remove the ‘*Select’ status from a currently selected member, type U next to the member or members you wish to deselect and press Enter. The ‘*Select’ status against the deselected member will no longer be displayed, and the member will not be included in the input for the parameter load job.

X

To remove a member name from the display, type X next to the member name you wish to remove and press Enter. The member name will no longer appear in the display (but it will not be removed from the dataset). If you remove a selected member name from the display, the member is automatically unselected.

E

To edit a dataset member, type E next to the name of the member to be edited and press Enter. You will be placed into an edit session for the member. The select status of the member is not changed when it is edited.

When you have completed member selection and editing, initiate load job setup by pressing F3. The following confirmation panel displays:

Figure 30 Confirm GDDR Parameter Load panel

Before pressing Enter to submit the parameter load job, specify these options:

◆ Should this load job replace all current parameter values?

Only option Y is valid. Partial parameter updates by batch processing are not supported. Therefore, the initialization option is always in effect. Existing global variables will be erased, including those which contain state configuration information. Consistency validation is performed against the parameter input only.

◆ Should this load job run in test mode and do no updates?

If you specify Y, parameters are read and validated as indicated but no global variable updates take place.

If you specify N, parameters are read and validated as indicated. After successful validation, global variable updates take place.

◆ Should alternate datasets be used for this parameter load?

------- GDDR Administration - Confirm GDDR Parameter Load ---------- Command ===> A GDDR parameter load job is being scheduled using the following members of dataset GDDR.GDDR300.PARMLIB GDDRMSC To complete job preparation, reply 'Y' or 'N' to each of the following: Should this load job replace all current parameter values? ===> Y Should this load job run in test mode and do no updates? ===> Y Should alternate datasets be used for this parameter load? ===> N Enter or change the job statement: //* //* //* //* Press <Enter> when ready. Press <F3> to return without submitting job.



Option N is the typical selection. This option lets the parameter load process use datasets specified by the CONCAT.JCLLIB, CONCAT.SKELS and GDDRVAR_BACKUP parameters defined in a previous parameter load. By default, the Global Variables are used.

Option Y lets you process the parameter load using datasets contained in the EMC GDDR user's personal GDDR ISPF profile, if those were previously entered in the Profile. One or more dataset names may be deselected when the GDDR Parameter Load Datasets panel, shown in Figure 31 on page 77 is displayed. The alternate dataset names are supplied using Option 3, Profile, in the GDDR Primary Options menu shown in Figure 12 on page 58 before beginning the parameter load process described in this section.

Using the command line

Control of the propagation of parameters to the remote C-Systems is available for each batch parameter load by using the MSFBYPASS command as follows on the Confirm GDDR Parameter Load panel command line:

◆ Command NOMSFB (Default)

Parameters are read and validated. If validation is successful, MSF accessibility to each C-System is checked. If any C-System is not accessible, no global variable updates take place. If all are accessible, global variable updates take place on each C-System.

◆ Command MSFB

Parameters are read and validated as indicated. If validation is successful, global variable updates take place on each accessible C-System.

Note: When the 'Enforce' options for jobname and surrogate user ID are selected on the View or Change Default Job Values panel shown in Figure 19 on page 67, changes to these values on the jobcard statements are not allowed here. When the parameter load job is submitted, basic jobcard validation is performed. Changes to the jobname or surrogate user ID, and edits on the remainder of the job statements which fail job initiation are rejected here. Correct any errors in the job statements and submit the parameter load job again.

When you complete the fields in the Confirm GDDR Parameter Load panel, press Enter to submit the parameter load job. The following panel appears:

Figure 31 GDDR Parameter Load Datasets panel

----------- GDDR Administration - GDDR Parameter Load Datasets ------------- Command ===> Specify whether to use the datasets in your ISPF profile for parameter load JCL library: GDDR.GDDR300.PROCLIB Use this JCL library? Y File tailoring skeleton library: GDDR.GDDR300.ISPSLIB Use this file tailoring skeleton library? Y Parameter backup library: GDDR.GDDR300.BKUPVARS.CNTL Use this parameter backup library? Y Enter option desired for each dataset. When ready, press <Enter> to continue. Press <F3> to terminate the parameter load process



The datasets shown in this panel are sourced from the Change GDDR ISPF Profile Variable Values panel, Option 3, Profile, in the GDDR Primary Options menu shown in Figure 12 on page 58.

You may deselect one or more dataset names to force the parameter load job to access these datasets from default dataset names defined by the CONCAT.JCLLIB, CONCAT.SKELS, or the GDDRVAR_BACKUP parameters.



Option 4: Update GDDR parametersWhen you select option 4, a pop-up message similar to the following appears in the Parameter Management Options menu:

Figure 32 Select the C-System(s) where parameter changes are to be made

Enter Y next to each C-System to be updated when parameter changes are made. When you press Enter, the View/Update GDDR Parameters panel appears:

Figure 33 View/Update GDDR Parameter Values panel

Type the desired parameter group option and press Enter to continue. The parameter options are described in the following sections.

--------------- GDDR - Parameter Management Options Menu ------------------ 1 Backup Create GDDR parameter backup 2 Restore Restore GDDR parameters from backup 3 Load +------ Specify C-Systems to be Updated -------+ 4 Update | | | Enter Y next to each C-System that will be | 5 Messages | updated when parameter changes are made. | | | Enter a parame | Site C-System | Press <F3> to | Y DC1 ZOSESYS1(Local) | | Y DC3 ZOSESYS3(Remote) | | | | | | Press <Enter> when ready, or <F3> to cancel | | | | | | Command ===> | +----------------------------------------------+ Option ===> 4

-------------- GDDR - View/Update GDDR Parameter Values ---------------- Option ===> 1 Tuning GDDR performance and tuning parameters 2 Devices Device-related parameters 3 Alloc Dataset allocation values 4 Datasets Dataset names 5 HMC HMC-related parameters 6 GNS GDDR-defined GNS groups 7 CallOver Call override settings 8 Options User options S Systems Configure GDDR Production systems Y Sysplex Sysplex related parameters L Lists Special-purpose component lists V State GDDR state variables (view only) Enter a parameter group selection number or letter and press <Enter> Press <F3> to return to the Administrator Primary Options Menu Enter CONFIG to view configuration information on any parameter display The source used for the last initialization parameter load was GDDR.GDDR300.PARMLIB(GDDRMSC)



Option 1: GDDR performance and tuning parametersTo modify EMC GDDR performance and tuning parameters, specify option 1. When you do so, a series of View or Change GDDR Tuning Parameters panels such as the following appear. Valid ranges are indicated for each parameter.

Figure 34 View or Change GDDR Tuning Parameters panel (screen 1 of 2)

Figure 35 View or Change GDDR Tuning Parameters panel (screen 2 of 2)

-- GDDR Administration - View or Change GDDR Tuning Paramete Row 1 to 16 of 23Command ===> Scroll ===> CSRYou may overtype a value to change it Enter row command R to reset a parameter to its default value When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Sel Value Description Range --- ------ ------------------------------------------ ----------------------_ 64 Max total queue commands Range 10-99 _ 35 Maximum concurrent queue commands Range 10-99 _ 22 Number of ECGUTIL subtasks Range 1-22 _ 20 Event monitor state check interval Range 1-999 _ 30 Seconds between GDDR heartbeats Range 1-999 _ 10 Maximum waits for ConGroup Shutdown Range 1-30 _ 20 Maximum waits for ConGroup startup Range 1-50 _ 61 Missing heartbeat interval Range 1-999 _ 11 Max missing heartbeat intervals Range 1-999 _ 60 Wait time for ConGroup shutdown Range 1-600 _ 10 Wait time for ConGroup startup Range 1-600 _ 15 Wait time for HMC reset/clear operations Range 1-99 _ 60 Wait time for SCFRDFM9 cleanup Range 1-600 _ 120 Min wait for OSF CG shutdown Range 1-999 _ 10 Maximum OSF loops Range 1-99 _ 900 Minimum OSFRUN value

-- GDDR Administration - View or Change GDDR Tuning Paramet Row 17 to 23 of 23 Command ===> Scroll ===> CSR You may overtype a value to change it Enter row command R to reset a parameter to its default value When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Sel Value Description Range --- ------ ------------------------------------------ ---------------------- _ 120 Minimum OSF wait value Range 1-999 _ 80 USS wait factor Range 1-999 _ 5 Wait time for activate/deactivate to finis Range 1-99 _ 240 Wait time for SPLIT to finish Range 1-999 _ 10 Wait time for invalids to synchronize Range 1-30 _ 5 Number of WTOR retries on timeout Range 0-999 _ 600 Default max WTOR time before timeout Range 1-3600 ******************************* Bottom of data ********************************



Option 2: Device-related parametersTo modify EMC GDDR device-related parameters, specify option 2. When you do so, a series of View or Change Device Parameters panels such as the following appear:

Figure 36 View or Change Device Parameters panel (screen 1 of 2)

Figure 37 View or Change Device Parameters panel (screen 2 of 2)

----- GDDR Administration - View or Change Device Parameters ---- Row 1 of 11 You may take these actions: Overtype a parameter value to change it Enter row command I to insert a parameter Enter row command D to delete a parameter When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel No Value Comment --- ------------------------------ ------------------------------------------ BCV.DC3.MSC BCVs _ 1 7040,38,02C0-034F,7040 Value format gggg,ra,dddd-dddd,uuuu BCV.DC3.ONLY BCVs accessed at site DC3 _ 1 7238,02C0-034F Value format dddd,dddd-dddd JA_ACT_GK.DC1 SRDF/A gatekeeper-RDF group association _ 1 7000,38 Value format gggg,ra JA_ACT_GK.DC3 SRDF/A gatekeeper-RDF group association _ 1 7238,38 Value format gggg,ra RESUME_GK.DC3 DC3-related gatekeeper _ 69FD SRDFA.DEVICES.DC1 SRDF/A device specifications

----- GDDR Administration - View or Change Device Parameters ---- Row 6 of 11 You may take these actions: Overtype a parameter value to change it Enter row command I to insert a parameter Enter row command D to delete a parameter When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel No Value Comment --- ------------------------------ ------------------------------------------ SRDFA.DEVICES.DC1 SRDF/A device specifications _ 1 7000,38,39,01F0-01FF Value format gggg,ra,ra,dddd-dddd _ 2 7000,38,39,0210-023F Value format gggg,ra,ra,dddd-dddd _ 3 7000,38,39,0240-027B Value format gggg,ra,ra,dddd-dddd SRDFA.DEVICES.DC3 SRDF/A device specifications _ 1 7000,38,39,01F0-01FF Value format gggg,ra,ra,dddd-dddd _ 2 7000,38,39,0210-023F Value format gggg,ra,ra,dddd-dddd _ 3 7000,38,39,0240-027B Value format gggg,ra,ra,dddd-dddd



Option 3: Dataset allocation valuesTo specify EMC GDDR dataset allocation values, specify option 3. When you do so, a series of View or Change Allocation Values panels such as the following appear:

Figure 38 View or Change Allocation Values panel (screen 1 of 2)

Figure 39 View or Change Allocation Values panel (screen 2 of 2)

Overtype parameter values to update them.

----- GDDR Administration - View or Change Allocation Values - Row 1 of 8 Command ===> Scroll ===> CSR You may overtype a value to change it. You may not add or delete options on this panel Use row command R to restore a parameter to its default When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel Value Comment --- ----------------------------- ------------------------------------------- ECGUTIL COMMAND alloc parms _ Unit: CYLINDERS Primary: 10 Secondary: 10 GDDGROUP REPORT alloc parms _ Unit: CYLINDERS Primary: 1 Secondary: 1 GDDGROUP SYSIN alloc parms _ Unit: TRACKS Primary: 1 Secondary: 1 GDDGROUP SYSPRINT alloc parms _ Unit: CYLINDERS Primary: 1 Secondary: 1 TimeFinder SYSIN alloc parms _ Unit: TRACKS Primary: 5 Secondary: 2 SCFRDFME RPTOUT alloc parms _ Unit: TRACKS Primary: 5 Secondary: 2 SCFRDFM6 RPTOUT alloc parms _ Unit: TRACKS Primary: 5 Secondary: 2

----- GDDR Administration - View or Change Allocation Values - Row 7 of 8 Command ===> Scroll ===> CSR You may overtype a value to change it. You may not add or delete options on this panel Use row command R to restore a parameter to its default When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel Value Comment --- ----------------------------- ------------------------------------------- SCFRDFM6 RPTOUT alloc parms _ Unit: TRACKS Primary: 5 Secondary: 2 SCFRDFM9 RPTOUT alloc parms _ Unit: TRACKS Primary: 5 Secondary: 2



Option 4: Dataset namesTo specify EMC GDDR dataset names, specify option 4. When you do so, a series of View or Change Dataset Parameters panels such as the following appear:

Figure 40 View or Change Dataset Parameters panel (screen 1 of 3)


----- GDDR Administration - View or Change Dataset Parameters --- Row 1 of 17 You may take these actions: Overtype a dataset name value of a parameter to change it Enter row command I to insert a numbered parameter, D to delete a parameter Enter row command E to edit a dataset, B to browse a dataset When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel No Dataset name Comment --- ----------------------------- ------------------------------------------- GDDR proclib concatenation at C-System SYS3 _ 1 GDDR.GDDR300.PROCLIB _ 2 GDDR.GDDR300.PROCLIB _ 3 GDDR.GDDR300.PROCLIB GDDR ISPF skeleton concatenation at C-System SYS3 _ 1 GDDR.GDDR300.ISPSLIB _ 2 GDDR.GDDR300.ISPSLIB _ 3 GDDR.GDDR300.ISPSLIB ConGroups control dataset name at System SYS1 _ X(CGRPCAX) ConGroups control dataset name at System SYS2 _ X(CGRPCAX) ConGroups control dataset name at System SYS3

----- GDDR Administration - View or Change Dataset Parameters --- Row 9 of 17 You may take these actions: Overtype a dataset name value of a parameter to change it Enter row command I to insert a numbered parameter, D to delete a parameter Enter row command E to edit a dataset, B to browse a dataset When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel No Dataset name Comment --- ----------------------------- ------------------------------------------ ConGroups control dataset name at System SYS3 _ X(CGRPCAX) ConGroups control dataset name at System SYS4 _ X(CGRPCAX) ConGroups control dataset name at System SYS1 _ X(CGRPCAX) GDDR variable save library at C-System SYS3 _ GDDR.GDDR300.BKUPVARS.CNTL GDDR variable save library at C-System SYS4 _ GDDR.GDDR300.BKUPVARS.CNTL GDDR variable save library at C-System SYS1 _ GDDR.GDDR300.BKUPVARS.CNTL Host Component control dataset name at System SYS3




----- GDDR Administration - View or Change Dataset Parameters --- Row 15 of 17 You may take these actions: Overtype a dataset name value of a parameter to change it Enter row command I to insert a numbered parameter, D to delete a parameter Enter row command E to edit a dataset, B to browse a dataset When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Parameter Description Sel No Dataset name Comment --- ----------------------------- ------------------------------------------- Host Component control dataset name at System SYS3 _ GDDR.GDDR300.PARMLIB(SRDFSTAR) Host Component control dataset name at System SYS4 _ GDDR.GDDR300.PARMLIB(SRDFSTAR) Host Component control dataset name at System SYS1 _ GDDR.GDDR300.PARMLIB(SRDFSTAR)



Option 5: HMC-related parameters

To specify HMC-related parameters, specify option 5. When you do so, a series of View or Change HMC Parameters panels such as the following appear:

Figure 43 View or Change HMC Parameters panel (screen 1 of 3)


------- GDDR Administration - View or Change HMC Parameters - Row 1 to 9 of 21 Command ===> Scroll ===> CSR Overtype a parameter value to change it When finished, press <F3> to return to the previous menu Parameter Description Sel Name/Value Comment --- ----------------------------- ------------------------------------------- AUTOCBU.P.DC1.CPC1 Automatic CBU Activation planned scripts NONE AUTOCBU.P.DC3.CPC3 Automatic CBU Activation planned scripts NONE AUTOCBU.U.DC1.CPC1 Automatic CBU Activation unplanned scripts NONE AUTOCBU.U.DC3.CPC3 Automatic CBU Activation unplanned scripts NONE HMC.DC1 HMC IP address nnn.nnn.nnn.nnn HMC.DC3 HMC IP address nnn.nnn.nnn.nnn HMC_BYPASS.DC1 HMC Bypass lpar list NONE HMC_BYPASS.DC3 HMC Bypass lpar list NONE HMC_TIMEOUT.DC1 HMC timeout value 25000 Value range is 1-99999

------- GDDR Administration - View or Change HMC Parameters Row 10 to 18 of 21 Command ===> Scroll ===> CSR Overtype a parameter value to change it When finished, press <F3> to return to the previous menu Parameter Description Sel Name/Value Comment --- ----------------------------- ------------------------------------------- HMC_TIMEOUT.DC3 HMC timeout value 25000 Value range is 1-99999 IPL.SYS1.DC1 IPL parameters 7070,707099M1 IPL.SYS1.DC3 IPL parameters 7270,727099M1 IPL.SYS2.DC1 IPL parameters 707A,707A99M1 IPL.SYS2.DC3 IPL parameters 727A,727A99M1 IPL.SYS3.DC1 IPL parameters 710A,710A99M1 IPL.SYS3.DC32 IPL parameters 710A,710A99M1 IPL.SYS4.DC1 IPL parameters 7010,701099M1 IPL.SYS5.DC1 IPL parameters 7210,721099M1




Option 6: GDDR-defined GNS groupsTo specify GDDR-defined GNS groups, specify option 6. When you do so, a View or Change GDDR GNS Parameters panel such as the following appears:

Figure 46 View or Change GDDR GNS Parameters panel

------- GDDR Administration - View or Change HMC Parameters Row 19 to 21 of 21 Command ===> Scroll ===> CSR Overtype a parameter value to change it When finished, press <F3> to return to the previous menu Parameter Description Sel Name/Value Comment --- ----------------------------- ------------------------------------------- IPL.SYS5.DC3 IPL parameters 7210,721099M1 IPLBCVS.SYS1.DC3 BCV IPL parameters 74F0,74F099M1 IPLBCVS.SYS2.DC3 BCV IPL parameters 74FA,74FA99M1

----- GDDR Administration - View or Change GDDR GNS Parameters -- Row 1 of 4 Command ===> Scroll ===> CSR You may take these actions: Enter major command BYSYM to view GNS groups associated with each Symmetrix Enter row command I to insert a GDDR GNS group specification Enter row command D to delete a GDDR GNS group specification Enter row command V to view the GNS group definition, if available When finished, press <F3> to go to the View/Update GDDR Parameter Values menu Sel No GNS group name --- -------------------------------------------------------------------------- GNS.DC1.LCL.JA GNS group _ 1 Name: DC1_JA_DC3 Symm: 00274 GNS.DC1.LCL.J0 GNS group _ 1 Name: DC1_J0_DC3 Symm: 00274



Option 7: Call override settingsTo specify call override settings, specify option 7. When you do so, the Specify Default Call Override panel appears:

Figure 47 Specify Default Call Override panel

Option 8: User optionsTo view user options, specify option 8. When you do so, a View GDDR User Options panel such as the following displays:

Figure 48 View GDDR User Options panel

------- GDDR Administration - Specify Default Call Overrid Row 1 to 16 of 16Command ===> For each row, you may change the call indicator: Enter Y to call the function Enter N to not call the function When ready, press <F3> to save the updated default call overrides Type CANCEL and press <Enter> to exit with no changes

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 N 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 N GDDRTNG1 GDDRTNG1 Y GDDRKF0E Transfer Autoswap Ownership Y GDDRKF0H Transfer Master Function Ownership Y GDDRKF21 (DC1) - Manage_BCVs Y GDDRKF21 (DC2) - Manage_BCVs Y GDDRKF21 (DC3) - Manage_BCVs

------ GDDR Administration - View GDDR User Options ---- Row 1 of 7 You may scroll up or down via <F7> and <F8> You may not add or delete options on this panel When finished, press <F3> to return to the previous menu Sel V Description Choice --- - --------------------------------------------- ------------------------ _ 1 Include message id's in batch output? 1 = Yes, 0 = No _ 0 Include time stamps in batch output? 1 = Yes, 0 = No _ 0 Do BCV split at new R1 site? 1 = Yes, 0 = No _ 1 Backup after online update? 1 = Yes, 0 = No _ 0 Confirm online parameter updates? 1 = Yes, 0 = No _ 2 ROUTCDE for GDDR WTO's Range 1-16



Option S: Configure GDDR production systemsWhen you select the EMC GDDR administrator option Configure GDDR production systems, the following message displays:

Production system parameter values unchanged

For the EMC GDDR SRDF/A configuration, there is an alternate method to configure production systems. “Adding a new production system or sysplex to EMC GDDR” on page 151 describes how to configure EMC GDDR-managed production systems.

Option Y: Sysplex related parametersOption Y, Sysplex related parameters, is not applicable to environments without cross-site host-DASD channels.

Option L: Special purpose component listsTo view or change GDDR component lists, specify option L. When you do so, a View/Update GDDR Component Lists panel such as the following appears:

Figure 49 View/Update GDDR Component Lists panel

Specify an option and press Enter to continue.

Option 1: System exclude list

If you specify option 1, System exclude list, the following panel appears:

Figure 50 System Exclude List panel

------------------- GDDR - View/Update GDDR Component Lists ------------------- Option ===> 1 SysExcl System exclude list 2 CBUProc CBU processor lists 3 HMCByps HMC Bypass lists Select a user-modifiable list by number and press <Enter> Press <F3> to return to the previous menu

---------- GDDR Administration - System Exclude List System Se Row 1 to 2 of 2 Option ===> Enter S next to a system name to select it - only one may be selected Press <F3> when to exit without making a selection Sel System Site --- -------- ---- _ ZOSESYS5 DC1 _ ZOSESYS6 DC3 ******************************* Bottom of data ********************************



Option 2: CBU processor lists

If you specify option 2, CBU processor lists, the following pop-up appears:

Figure 51 Specify CBU Site pop-up display

Type the number for the site whose HMC CBU processor list is to be updated and press Enter. A panel similar to the following appears:

Figure 52 Site CBU Processor List panel

Option 3: HMC bypass lists

If you specify option 3, HMC bypass lists, the following panel appears:

Figure 53 HMC Bypass List Display panel

---- Option ===> 2 1 SysExcl System exclude list +-------------- Specify CBU Site --------------+ | Command ===> | | | Select a user- | Enter the number for the site whose HMC CBU | Press <F3> to | processor list is to be updated. | | | | Site | | 1 DC1 | | 3 DC3 | | | | Press <Enter> when ready, or <F3> to cancel | | | | | +----------------------------------------------+

---------- GDDR Administration - Site DC1 CBU Processor List D Row 1 to 1 of 1 Option ===> Enter D next to a processor name to delete the processor name from the list Use the ADD command to add a new processor name to the list Press <F3> when finished Sel Processor --- -------- _ P003F32D ******************************* Bottom of data ********************************

--------- GDDR Administration - Site DCn HMC Bypass List Display ------------- Option ===>____ + Enter D next to an lpar name to delete the lpar name from the list Use the ADD command to add a new lpar name to the list Press <F3> when finished Sel Lpar --- --------



You can delete LPARs from the list or add new LPAR names. If you specify the ADD command, the following panel appears:

Figure 54 Add LPAR Name to HMC Bypass List panel

Option V: GDDR state variables (view only)To view GDDR state variables, specify option V. When you do so, a series of View GDDR State Values panels such as the following appear:

Figure 55 View GDDR State Values panel (screen 1 of 2)

----- GDDR Administration - Add Lpar Name to Site DCn HMC Bypass List --------- Command ===> ____ Lpar name ===> Enter lpar name and press <Enter> to add new lpar name to HMC Bypass list at site DCn Enter * as the ONLY lpar name to bypass HMC processing for all lpars at site DCn Press <F3> to return without changing the HMC Bypass list for site DCn

--------------- GDDR Administration - View GDDR State Values ---- Row 1 of 25 Command ===> Scroll ===> CSR You may scroll up or down via <F7> and <F8> You may not update, add or delete parameters on this panel When finished, press <F3> to return to the previous menu Parameter Value Description --------------------------- --------------------- -------------------------- CURRENT.PRIMARY.DASD.SITE DC1 Current primary dasd site CURRENT.PRIMARY.SITE DC1 Current primary site CURRENT.SECONDARY.DASD.SITE DC3 Current secondary dasd site CURRENT.SECONDARY.SITE DC3 Current secondary site CURRMAST.C SYS4 Current master C-System DCN.Degraded.Mode 0 Remote C-System unavailable DCN.Unplanned.C>> 0 Unplanned C>> DCN.Unplanned.CAX 0 Unplanned CAX swap DCN.Unplanned.CGD 0 Unplanned ConGroup trip DCN.Unplanned.CGT 0 Unplanned ConGroup trip DCN.Unplanned.ECA 0 Unplanned ECA DCN.Unplanned.ENV 0 Unplanned ENV DCN.Unplanned.LDR 0 Local DR DCN.Unplanned.LNK 1 Unplanned link failure



Figure 56 View GDDR State Values panel (screen 2 of 2)

--------------- GDDR Administration - View GDDR State Values ---- Row 16 of 25 Command ===> Scroll ===> CSR You may scroll up or down via <F7> and <F8> You may not update, add or delete parameters on this panel When finished, press <F3> to return to the previous menu Parameter Value Description --------------------------- --------------------- -------------------------- DCN.Unplanned.LNK.DC3vDC1 0 Unplanned LNK DC3vDC1 DCN.Unplanned.MSC 0 Unplanned MSC failure DCN.Unplanned.NCX 0 Unplanned NCX DCN.Unplanned.RDF 0 Unplanned RDF DCN.Unplanned.RDR 0 Remote DR DCN.Unplanned.SRA 0 Unplanned SRDF/A failure DCN.Unplanned.STR 0 Unplanned STR DC1.State 000000000000000000000 Site state DC2.State 000000000000000000000 Site state DC3.State 000000000000000000000 Site state



Option 5: Refresh GDDR message tableWhen you choose option 5 from the Parameter Options Management panel, the GDDRMSG table is refreshed and the message 'GDDRMSG Table refreshed' displays in the panel, as shown below.


+-------------------------+ | GDDRMSG Table refreshed | +-------------------------+



Option Q — Queue: Manage GDDR internal command queueWhen you select the EMC GDDR administrator option Manage GDDR internal command queue, the following panel appears:

Figure 57 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.

--------------------- 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 Administrator 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



Option S — SMF: Manage SMF Logging Options

Note: Option S, Manage SMF Logging Options, appears on the GDDR Administrator Primary Options Menu only when the CA-OPSMVS OPSVIEW parameters include INTSMF YES. EMC GDDR Audit Monitoring SMF Logging options can then be specified or modified online as described below.

When you select the EMC GDDR administrator option Manage SMF Logging Options, the following panel appears:

Figure 58 View or Change SMF Logging Options panel

Specify a starting SMF subrecord number and configure the EMC GDDR Audit Monitoring options to specify the type of data to be collected.

Field descriptions

SMF Record Number

This field displays the SMF record number specified in the CA-OPS/MVS parameter "SMFRECORDNUMBER,nnn", which is located in the OPSVIEW Parameter member.

Starting SubRec Number

This field specifies the value of the starting SMF subrecord number for EMC GDDR Audit Monitoring SMF records. If no value is specified, the default value of 2000 is used.

Logging Options

Selection of any of the "Log All" options enables writing of GDDR Audit Monitoring SMF records for occurrences of the specified message types.

Log State Changes — A value of Y enables writing of information describing EMC GDDR-managed system and storage state changes to the SMF recording dataset.

Log All Errors — A value of Y enables logging of all EMC GDDR messages with a suffix of ’E' in position 8 of the message ID.

Log All Warnings — A value of Y enables logging of all EMC GDDR messages with a suffix of 'W' in position 8 of the message ID.

Log All WTOs — A value of Y enables logging of all EMC GDDR messages.

----- GDDR Administration - View or Change SMF Logging Options ---------------Command ===> _________________________________________________________________ SMF Record Number: 254 Starting SubRec Number: 31000 Log Options (Y/N): Log State Changes: Y Log All Errors: Y Log All Warnings: Y Log All WTOs: Y Debugging Output: N Log WTO Templates: R721I X000N X000N X000N Note: Use Asterisk in template for single digit wildcard Example: R1**E = Log all WTOS beginning with 'GDDR1' and ending with 'E'



Debugging Output — A value of Y enables logging of diagnostic and trace output by program name that are triggered by the message output user options. These option settings are shown in “Option M — MsgOut: Specify GDDR message output options” on page 69.

Log WTO Templates

WTO Templates enable filtering of the EMC GDDR messages to be selected and written to GDDR Audit Monitoring SMF records. Positions 4 through 8 of the GDDR message IDs may be specified in any of the 4 filters in this field. An asterisk may be used as a wildcard character in one or more positions.



EMC GDDR ISPF profilesEMC GDDR ISPF profiles are accessed by selecting option 3 – Update personal GDDR ISPF profile variables on the GDDR Primary Options menu (Figure 12 on page 58) and pressing Enter. When you enter this option, the following panel appears:

Figure 59 Change GDDR ISPF Profile Variables panel

This panel is used to specify alternate dataset names to be stored in your ISPF profile for the following settings:

◆ JCL dataset

The dataset you specify in the JCL dataset field will be searched when 'Y' is the response to the question 'Should alternate datasets be used for this parameter load?' shown in Figure 30, “Confirm GDDR Parameter Load panel,” on page 76. This dataset is concatenated ahead of the dataset name specified in the CONCAT.JCLLIB.system-name.seq parameter.

◆ ISPF skeleton dataset

The dataset you specify in the ISPF skeleton dataset field will be concatenated ahead of the dataset name specified in the CONCAT.SKELS.system-name.seq parameter. It is used to retrieve ISPF file tailoring skeletons when scripts are submitted.

◆ Global variable backup

The dataset you specify in the Global variable backup dataset field will be used for the name of the next global variable backup dataset, if different than the dataset name specified by the GDDRVAR_BACKUP parameter. The alternate global variable backup dataset must be any valid PDS or PDSE.

◆ Host component prefix

The value you specify in the Host component prefix field will be used when Host Component commands are processed by user-submitted jobs and planned scripts.

◆ Default SCF suffix

The value you specify in the Default SCF suffix field will be used when user-submitted jobs and planned scripts require services provided by an instance of Symmetrix Control Facility (SCF).

--------- GDDR - Change GDDR ISPF Profile Variable Values ----------- Command ===> JCL dataset ===> ISPF skeleton dataset ===> Global variable backup ===> Host Component prefix ===> Default SCF suffix ===> 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



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 11 on page 58.

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 97

4Invisible Body Tag

This chapter describes the EMC GDDR parameters. Topics are:

◆ Introduction .................................................................................................................. 100◆ Parameter statement processing ................................................................................ 101◆ Loading the parameters .............................................................................................. 103◆ Parameter descriptions................................................................................................ 104◆ User environment parameters.................................................................................... 105◆ Performance and tuning parameters......................................................................... 137◆ Audit monitoring parameters .................................................................................... 144

EMC GDDRParameters

EMC GDDR Parameters 99

EMC GDDR Parameters

IntroductionEMC GDDR parameters are used to establish the EMC GDDR operating environment. They do so by furnishing the information used to create EMC GDDR CA-OPS/MVS global variables. The global variables are directly accessible by EMC GDDR programs.

EMC GDDR parameters are grouped into two categories—user environment parameters and performance and tuning parameters.

User environment parametersUser environment parameter statements reside in one or more members of a parameter library. As part of EMC GDDR customization, you edit parameter library members using the information provided in this chapter to customize the parameters for your environment. When you are ready to load the customized parameters, use the TSO procedure described in “EMC GDDR ISPF profiles” on page 96 to submit a batch job that will load the parameters. All the parameters, or only a subset of parameters, can be loaded in a single job.

Loading the EMC GDDR user environment parameters consists of reading the selected parameter library members, performing validation, and creating or updating the resulting global variables if validation is successful.

Parameters can be loaded with the initialization option. If initialization is specified, all existing EMC GDDR global variables are removed prior to creating the global variables resulting from the processed parameters. If initialization is not specified, the values of existing global variables are merged with the values of global variables that would be created or updated as a result of processing the EMC GDDR input parameters. In either case, the resulting set of global variables is validated for consistency and completeness before any global variables are added, removed, or changed.

Note: Any debug routines that have been added in the trace list are preserved.

Performance and tuning parameters These parameters govern the event monitoring behaviors and HMC initialization values. The parameters are maintained through the use of the GDDR Administrator Primary Options panel>Option P, Update GDDR parameters. With the exception of HMC initialization values, the parameters maintained through this panel are initialized by software default.


EMC GDDR Parameters

Parameter statement processingEMC GDDR parameter statements are keyword value assignments (that is, in the format keyword=value).

ComponentsIn processing parameter statements, EMC GDDR assigns special significance to certain types of named entities found in either parameter keywords or parameter values. These entities are called components. EMC GDDR recognizes the following types of components:

◆

◆ C-System

◆ Contingency system

◆ GNS group

◆ IP address

◆ LPAR

◆ MSF ID

◆ Site

◆ System

References and specificationsAn occurrence of a component name within a parameter statement is classified as either a specification or a reference. A specification defines the existence of a component, while a reference names a component for which a corresponding specification is expected to occur. For example, the statement

CONT.SYSA01=SYSB01

contains two references (system names SYSA01 and SYSB01), while the statement

DC1.C.System.Systemid=SYSC001

contains a reference (site DC1) and a specification (C-System SYSC001). During consistency checking, a test is made to ensure that for every reference a corresponding specification exists. During completeness checking, a test is made to ensure that every required specification exists.

AssociationsA parameter statement may include one or more component names in its keyword portion and a component name as its value as well. The occurrence of multiple component names in a parameter statement creates an association between component names. For example, the statement

SITE.MVSSYS1=DC1

would create an association between the system name MVSSYS1 and the site ID DC1.

Parameter statement processing 101

EMC GDDR Parameters

ValidationThe following types of validation are performed when parameters are loaded:

Syntax

◆ Parameter keywords must be in the format presented in this guide.

Note: The variable parts of parameter keywords are indicated in this guide as italicized lowercase text. However, you must enter the actual values as UPPERCASE text.

◆ When a parameter description in this guide indicates that a part of the parameter statement must be one of the listed component types, that part of the parameter must conform to the syntax rule applying to that component type.

The syntax rules for component names are found in “Syntax rules” on page 178.

Consistency

◆ Multiple occurrences of unique parameter keywords are not allowed.

◆ Mutually exclusive values are not both present, including the specification of multiple values where only one is allowed.

◆ Associations obtained from all parameter statements and existing global variables may not conflict with each other.

The rules for consistency are found in “Consistency rules” on page 180.

Completeness

◆ All required parameters must be present.

◆ All required associations must be present. For example, if a system name is specified, an associated site ID must also be specified.

◆ Parameters required due to the presence of other parameters must be present.

The rules for completeness are found in “Completeness rules” on page 181.


EMC GDDR Parameters

Loading the parameters

Validating the environmentThe syntax and validity of the parameters are checked; they will not be loaded unless the environment is valid.

No Planned or Unplanned scripts may be running. Additionally, if the run is not an initialization run, the system on which parameter processing takes place must be the master C-System and no changes to sites, C-Systems, or MSF ids of C-Systems are allowed. An initialization run, however, may take place on any C-System specified in the input parameters.

Backing up existing global variablesAfter the environment has been validated, it is necessary to back up existing global variables before loading the new parameters. The backup process creates a REXX exec that may be run to recreate global variables as they existed prior to the parameter update. The backup includes all existing EMC GDDR global variables, whether or not they are to be changed by the parameter load.

If no global variables exist, no backup is done.

Loading global variablesThe following steps are performed during global variable load:

◆ Any global variables for which the values are entered manually by the EMC GDDR administrator (rather than obtained through parameters) are saved.

The following is a list of messages that are associated with these variables. Each of the messages only appears when GDDRGF04 finds that the variable has been set.

GDDP130I Retaining global GLOBAL.GDDR.INTJOB.HCPFX GDDP130I Retaining global GLOBAL.GDDR.INTJOB.SCFSFX GDDP133I Retaining matches for GLOBAL.GDDR.JOBSTMT.* GDDP130I Retaining global GLOBAL.GDDR.Diagnostics.Debug GDDP130I Retaining global GLOBAL.GDDR.Diagnostics.Trace GDDP130I Retaining global GLOBAL.GDDR.Diagnostics.DebugLvl GDDP130I Retaining global GLOBAL.GDDR.Diagnostics.TraceLvl GDDP130I Retaining global GLOBAL.GDDR.Diagnostics.HMC_Simulate GDDP130I Retaining global GLOBAL.GDDR.Diagnostics.NoWorkload GDDP133I Retaining matches for GLOBAL.GDDR.HMC.COMMUNITY.*

◆ If initialization is in effect, all EMC GDDR global variables are deleted; otherwise, no delete is performed. The delete is applied to all MSF-connected systems.

◆ If initialization is in effect, global variables requiring initial values but not associated with parameters are created on the local system and each connected C-System.

◆ Global variables associated with the parameter input are updated. If initialization is not in effect, numbered variables are deleted first. Deletes and updates are applied to the local system and to each connected C-System.

◆ Global variables whose values are manually entered are written to the local system and to each connected C-System.

Loading the parameters 103

EMC GDDR Parameters

Parameter descriptionsThe variable parts of parameter keywords are indicated in this guide as italicized lowercase. However, you must enter the actual values as uppercase text.

Ellipses (…) indicate that the value is a list and that multiple names may be included.

If a parameter statement is indicated as required, the presence of the corresponding global variable satisfies this requirement if the initialization option is not specified. If initialization is specified; however, the parameter statement must be present in the input file.

A value must always be specified on a parameter statement. The string containing the value is non-positional; that is, blanks between the equal and the start of the string are allowed.

The type of a parameter governs the method by which one or more global variables are generated from it. These are the parameter types:

◆ A parameter is unique if its keyword does not contain a component name. Only one occurrence of such a parameter keyword may be present in the input. When a unique parameter is present in the input file, the corresponding global variable value is updated or created (if validation is successful).

◆ A parameter is associative if its keyword contains one or more component names and if, for a particular set of component names, only one occurrence of the parameter is permitted. When an associative parameter is present in the input file, the corresponding global variable value will be updated or created (if validation is successful).

◆ A parameter is numbered when (for a particular set of component names occurring in the keyword) multiple occurrences of the keyword may be present in the input file. The corresponding global variable names include sequence numbers beginning with 1 appended as a new level to form a compound name. In general, the sequence numbers are assigned by EMC GDDR. If the keyword of a numbered parameter includes a component name, the sequence numbers are assigned independently for different component names. The portion of the global variable name associated with a numbered parameter excluding the sequence number (and the period preceding it) is called the base portion of the global variable name. When a numbered parameter is encountered in the input file, a delete of all existing global variables with that base portion is performed prior to update or create of the global variables (if validation is successful).


EMC GDDR Parameters

User environment parametersThe parameters listed in this section are initialized from the GDDRMSC member during batch parameter loading.

AUTOCBU.U or P.siteid.central-processing-complex-nameThis parameter allows script control of capacity backup activation by cpcname and site. The presence of this parameter in the GDDRMSC member definition invokes script automation to activate licensed processing capacity on specified central processing complexes at the recovery site specified by siteid in preparation for restart of workload.

Operator control of capacity backup activation is performed using Option C, Perform CBU Actions, on the GDDR Operator Primary Options menu. The option to cancel capacity backup following an activation is only available from the Perform CBU Actions panel, using the Undo CBU option.

Planned and Unplanned site swap scripts exercise the Capacity Backup activation function in each of the following user-selected situations.

Source Initialized from GDDRMSC member at batch parameter load.

Syntax AUTOCBU.U.siteid.central-processing-complex-name=REAL or TEST or NONE

OR

AUTOCBU.P.siteid.central-processing-complex-name=REAL or TEST or NONE

VariablesU or P Uppercase 'U' indicates the parameter is

referenced for unplanned scripts. Uppercase 'P' indicates the parameter is referenced for planned scripts.

siteid The ID of the site location being specified. It can have the value DC1 or DC3.

central-processing-complex-name (cpcname)

The name of the central processor where the LPAR is defined.

REAL Capacity backup automation will activate available capacity.

TEST Capacity backup automation will simulate activation of available capacity.

NONE No capacity backup automation actions are performed. This is the default value.

User environment parameters 105

EMC GDDR Parameters

BCV.siteid.MSCThe BCV.siteid.MSC statement defines the BCV volumes associated with a particular range of standard devices at the site specified by siteid.


Syntax BCV.siteid.MSC=gatekeeper,rdfgrp,dev-range

Variables

Example The parameter statement

BCV.DC1.MSC=0700,02,0200-0207,0700

is used by the Dynamic Application Program Interface (DYNAPI) to generate commands such as the following:

SPLIT 1,LCL(0700,0200-0207),NOWAIT,INS(Y)

When RMT syntax is used, an RDF group is also used, as follows:

RE-ESTABLISH 1,RMT(0700,0200-0207,02),NOWAIT

Note: Any number of BCV.siteid.MSC statements may be included in the input file.

siteid This is the site location, either DC1 or DC3.gatekeeper The MVS address at the site opposite from BCV.siteid.rdfgrp The RDF group spanning gk-siteid to BCV-siteid.dev-range 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).


EMC GDDR Parameters

BCV.DC1.ONLYThe BCV.DC1.ONLY parameter statement defines the BCV volumes associated with a particular range of standard devices at site DC1. This statement comes into play only when site DC3 has become unavailable and thus when DC1 volume operations are performed locally.


Syntax BCV.DC1.ONLY=gatekeeper,dev-range

Literals

Variables

Example The parameter statement BCV.DC1.ONLY=A080,3020-30A0 could result in either of the following commands:

SPLIT 1,LCL(A080,3020-30A0),NOWAIT,INS(Y)

SPLIT 1,LCL(A080,3020-30A0),WAIT(240),CONSISTENT(GLOBAL(ECA))

Note: Any number of BCV.DC1.ONLY statements may be included in the input file.

DC1 The site ID of the BCVs to be managed.

ONLY The keyword ONLY.

gatekeeper The MVS address at DC1.

dev-range The Symmetrix device number range of the BCVs being managed. It can be either a single Symmetrix device address or, to specify a range of addresses, the low address of the range followed by a hyphen and the high address of the range.


EMC GDDR Parameters

BCV.DC3.ONLYThe BCV.DC3.ONLY parameter statement defines the BCV volumes associated with a particular range of standard devices at site DC3. This statement comes into play only when site DC1 has become unavailable and thus when DC3 volume operations are performed locally.


Syntax BCV.DC3.ONLY=gatekeeper,dev-range

Literals

Variables

Example The parameter statement BCV.DC3.ONLY=A080,3020-30A0 could result in either of the following commands:

SPLIT 1,LCL(A080,3020-30A0),NOWAIT,INS(Y)

SPLIT 1,LCL(A080,3020-30A0),WAIT(240),CONSISTENT(GLOBAL(ECA))

Note: Any number of BCV.DC3.ONLY statements may be included in the input file.

DC3 The site ID of the BCVs to be managed.

ONLY The keyword ONLY.

gatekeeper The MVS address at DC3.

dev-range The Symmetrix device number range of the BCVs being managed. It can be either a single Symmetrix device address or, to specify a range of addresses, the low address of the range followed by a hyphen and the high address of the range.


EMC GDDR Parameters

CF_STRUCTURE.REBUILDThis parameter specifies whether or not 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.

Note: EMC recommends that this feature be enabled by default for Planned Scripts only.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR Parameters> Option Y, Sysplex related parameters. Refer to “Option Y: Sysplex related parameters” on page 88.

Syntax CF_STRUCTURE.REBUILD = PLANNED/UNPLANNED/ALL/NONE

VariablesPLANNED Automate the management of Coupling Facility Structures as a

part of planned script processing.

UNPLANNED Automate the management of Coupling Facility Structures as a part of unplanned script processing.

ALL Automate the management of Coupling Facility Structures as a part of planned and unplanned script processing.

NONE Skip the management of Coupling Facility Structures as a part of script processing.


EMC GDDR Parameters

CONCAT.JCLLIB.system-name.seqThe CONCAT.JCLLIB.system-name.seq parameter specifies one of a set of libraries that will be searched for cataloged procedure GDDRPROC when scripts or parameter update jobs are submitted. The aggregate of CONCAT.JCLLIB.system-name.seq statements in the input stream must include consecutive sequence numbers beginning with 1. The numeric order of the sequence numbers indicates the search order.

The search is implemented using a JCLLIB statement in the submitted job. The maximum number of CONCAT.JCLLIB.system-name.seq parameter statements that may be included is equal to the maximum number of libraries that may be included in a JCLLIB statement in a job.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 4, Dataset names. Refer to “Option 4: Dataset names” on page 83. The replacement field name is 'GDDR proclib concatenation at C-System systemid'.

Syntax CONCAT.JCLLIB.system-name.seq=proclib-dsname

Variables

Example The following parameter statements, though not recommended, could be present in the input stream:

CONCAT.JCLLIB.SYS1.2=SYS2.TEST.PROCLIBCONCAT.JCLLIB.SYS1.03=SYS2.PROCLIBCONCAT.JCLLIB.SYS1.1=SYS1.PROCLIB

These statements would cause SYS1.PROCLIB to be searched first, SYS2.TEST.PROCLIB second and SYS2.PROCLIB last.

Note: Multiple CONCAT.JCLLIB.system-name.seq statements may be present in any order in the input stream, not necessarily in an order corresponding to the numeric sequence number order.

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

seq A sequence number whose significance and rules for use are described above.

proclib-dsname The dataset name of a procedure library to be used in the cataloged procedure search.


EMC GDDR Parameters

CONCAT.SKELS.system-name.seqThe CONCAT.SKELS.system-name.seq parameter specifies one of a set of libraries that will be searched for ISPF file tailoring skeletons when scripts or parameter update jobs are submitted. The aggregate of CONCAT.SKELS.system-name.seq statements in the input stream must include consecutive sequence numbers beginning with 1. The numeric order of the sequence numbers indicates the search order.

The search is implemented by means of the allocation to ddname ISPSLIB of a concatenation of the datasets prior to performing the file tailoring. The maximum number of CONCAT.SKELS.system-name.seq parameter statements that may be included is equal to the maximum number of libraries that may be specified in a TSO allocate command.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 4, Dataset names. Refer to “Option 4: Dataset names” on page 83. The replacement field name is 'GDDR ISPF skeleton concatenation at C-System systemid'.

Syntax CONCAT.SKELS.system-name.seq=skeleton-dsname

Variables

Example The following parameter statements, though not recommended, could be present in the input stream:

CONCAT.SKELS.SYS1.2=GDDR.V300.SKELSCONCAT.SKELS.SYS1.03=ISP.SISPSENUCONCAT.SKELS.SYS1.1=GDDR.V300.CUSTOM.SKELS

They would cause GDDR.V300.CUSTOM.SKELS to be searched first, GDDR.V300.SKELS second and ISP.SISPSENU last.

Note: Multiple CONCAT.SKELS.system-name.seq statements may be present in any order in the input stream, not necessarily in an order corresponding to the numeric sequence number order.

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

seq A sequence number whose significance and rules for use are described above.

skeleton-dsname The dataset name of an ISPF file tailoring skeleton library to be used in the search.


EMC GDDR Parameters

CONT.system-nameThe CONT.system-name parameter statement specifies a system on which production business applications can run if a primary production system fails. Such a backup system is known as a contingency system for the primary system. A contingency system should be specified for each production system running at DC1.

Note: There must be exactly one contingency system specified for each system that is not a C-System.

A contingency system for a system located at site DC1 must be located at site DC3. A contingency system for a system located at site DC3 must be located at site DC1.


Syntax CONT.system-name=contsys

Variablessystem-name The z/OS system name of the production system for which this

contingency system parameter is being defined.

contsys The z/OS system name of the contingency system that is partnered with production system system-name.


EMC GDDR Parameters

COUPLE_DS.REALIGNThis parameter specifies whether or not Planned or Unplanned scripts should manage couple datasets when the primary DASD site is DCn. Further control is provided by the (u)PLX.* parameters and the System Exclude list.

Note: EMC recommends that this feature be enabled by default for Planned Scripts only.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR Parameters> Option Y, Sysplex related parameters. Refer to “Option Y: Sysplex related parameters” on page 88.

Syntax COUPLE_DS.REALIGN = PLANNED/UNPLANNED/ALL/NONE

VariablesPLANNED Automate the management of couple datasets as a part of

planned script processing.

UNPLANNED Automate the management of couple datasets as a part of unplanned script processing.

ALL Automate the management of couple datasets as a part of planned and unplanned script processing.

NONE Skip the management of couple datasets as a part of script processing.


EMC GDDR Parameters

siteid.C.System.SystemidThe siteid.C.System.Systemid statement specifies that the site specified by siteid will participate in the EMC GDDR configuration, and specifies the system name of the C-System associated with that site.

Note: Only one siteid.C.System.Systemid statement for a particular site ID may be present in the input file.

Use the D SYMBOLS MVS system command and locate &SYSNAME in the output to determine which value to specify here. See the following sample output:

RESPONSE=SYSBIEA007I STATIC SYSTEM SYMBOL VALUES 856&SYSALVL. = "2"&SYSCLONE. = "B0"&SYSNAME. = "SYSB"&SYSPLEX. = "SYSPLEXB"&SYSR1. = "RESB14"&CATV1. = "CATB14"&JESAPP. = "JESB"&JESC1. = "CATB14"&JESC2. = "CATB14"&JESS1. = "JESB0"&RESV1. = "RESB14"&SYSID. = "SYSB"


Syntax siteid.C.System.Systemid=c-system-sysname

Variablessiteid The ID of the site location being specified. It can have the value

DC1 or DC3.

c-system-sysname The z/OS system name of the C-System being specified for the site identified by siteid.


EMC GDDR Parameters

GDDR.CALL_OVERRIDEThis parameter controls certain aspects of EMC GDDR functionality.

Note: EMC GDDR supports only one GDDR.CALL_OVERRIDE parameter statement.

WARNING

Aside from the modifiable positions described in this guide, do not modify the call override specification except as instructed by EMC technical personnel.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Update GDDR parameters>Option 7, Call override settings. Refer to “Option 7: Call override settings” on page 87. Call override changes are effective for any subsequent script submission unless the settings are changed again prior to script submission.

GDDR.CALL_OVERRIDE values may be modified immediately prior to submit of a particular script using the GDDR Operator Primary Options panel>Option S, Run GDDR scripts>Select parameters for initial script run, where the user may choose to modify call override settings. Changes are effective only for the duration of the current script.


EMC GDDR Parameters

GDDR.CONFIGThe GDDR.CONFIG parameter statement specifies major features of your configuration. Only one GDDR.CONFIG parameter statement may be present.

Note: When a script selection menu is displayed, only scripts applicable to a configuration, including features specified by the GDDR.CONFIG parameter, are presented for selection.


Syntax GDDR.CONFIG=numsites,features

Variablesnumsites This is a required specification, and indicates the number of sites which

will participate in the EMC GDDR configuration. numsites is specified as 2SITE.

features This consists of one or more of the following keywords, provided in any order, indicating that a corresponding feature is present:

SRDFA – SRDF/A is supported in your configuration

FBADEVS - FBA devices are present in your configuration


EMC GDDR Parameters

GDDRVAR_BACKUPThe GDDRVAR_BACKUP parameter statement specifies the name of a dataset into which backups of EMC GDDR global variables are saved. This dataset is allocated during the EMC GDDR configuration procedure. The userid under which the backup dataset is allocated must have update access authority to the dataset name.

Note: Only one GDDRVAR_BACKUP parameter statement may be present in the input file.

The backup dataset must be a PDSE (recommended) or a PDS. Periodic removal of unneeded members of this dataset is recommended. Members are added when the parameter update job is run and whenever the heartbeat monitor is started. You may also initiate an EMC GDDR global variable backup from the Backup option of the GDDR - Parameter Management Options Menu.

Member names of the backup dataset have the format Vdddmmmm or Hdddmmmm, where V indicates the member was created by the parameter update job, H indicates the member was created by a user-requested backup or by the heartbeat monitor, ddd is the day number within the current year, and mmmm is the minute number within the day at the time the backup begins.

Each global variable backup is a REXX exec which, if run, re-creates all EMC GDDR global variables that existed at the time the backup was created.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR Parameters>Option 4, Dataset names. Refer to “Option 4: Dataset names” on page 83. The replacement field name is 'GDDR variable save library at C-System systemid'.

The dataset referenced by GDDRVAR_BACKUP is allocated using SAMPLIB member GDDRABDS, described on “Prepare and load EMC GDDR parameters” on page 48.

Syntax GDDRVAR_BACKUP.c-system-name=dsname

Variablesc-system-name The MVS system name of the C-System to which the statement

applies.

dsname This value specifies a dsname of the EMC GDDR global variable backup dataset.

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.


EMC GDDR Parameters

GNS.siteid.loc.jtypeThe GNS.siteid.loc.jtype parameter statement defines a GNS group to be used on commands when the current environment and the command target location indicate a match with the parameter keyword.

Note: Local commands (loc=LCL) are targeted at the current R1s; remote commands (loc=RMT) are targeted at remote R2s at the DC3 site. The GNS group name must have already been defined using the EMCGROUP utility.

Any number of GNS.siteid.LCL.jtype statements may be included in the input file.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 6, GDDR-defined GNS groups. Refer to “Option 6: GDDR-defined GNS groups” on page 86. The name of the field in the panel is 'GNS group name'.

Syntax GNS.siteid.loc.jtype=gns-group-name,symm-serial-no,ra-group

Variables

Examples For parameter GNS.DC1.LCL.J0=gns-group,serial,rag, the following commands could be issued when the primary DASD site is DC1, the SRDF/S leg is to be used, and local devices of interest:

SQ VOL,SCFG(gns-group)SQ MIRROR,SCFG(gns-group)SC VOL,SCFG(gns-group),SWAP(ITRK,STAR)

siteid Specifies the site ID which must match the ID of the primary DASD site for the GNS group name specified as the parameter value to be selected for use in a command. The site ID must be DC1 or DC3.

loc Specifies the command keyword matching dependency on the command target location. When LCL, locally-targeted commands can be matched. When RMT, remotely-targeted commands can be matched, allowing the GNS group name specified as the parameter value to be selected for use in a command.

jtype Indicates whether the GNS group specified as the parameter value applies to the SRDF/S or SRDF/A leg. When J0, the keyword is matched when SRDF/S is wanted; when JA, the keyword is matched when SRDF/A is wanted.

gns-groupname Specifies the name of the GNS group that will be used in a command when keyword values described above are matched as indicated. The GNS group must be created using EMCGROUP.

symm-serial-no Specifies 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 ECGCLEAN.

ra-group Specifies the number of the RA group associated with the GNS group.


EMC GDDR Parameters

HMC.siteidThe HMC.siteid parameter identifies the IP address of the hardware management console located at the site location specified by siteid that EMC GDDR is to use to perform console operations at that site location.

Note: Only one HMC.DCn parameter statement per site is permitted.

If a site is specified in the current configuration using a siteid.C.System.Systemid parameter statement, then an HMC.siteid statement must be present for that site.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 5, HMC-related parameters. Refer to “Option 5: HMC-related parameters” on page 85. The replacement field name is 'HMC IP address at Site siteid'.

Syntax HMC.siteid=ip-address

Variablessiteid The ID of the site whose hardware management console has the IP

address specified as the parameter value.

ip-address The IP address of the hardware management console at the site identified by siteid.


EMC GDDR Parameters

HMC_BYPASS.siteidThis optional parameter identifies the LPARs by site (DCn) where hardware management console actions should be bypassed. This bypass affects all HMC actions for the specified Site or LPARs. This includes Load, Reset, Activate, Deactivate, manual and automatic CBU Activate and Undo, Couple DS Realignment and CF Structure Rebuild.

Either specify * or provide a comma-separated list of LPAR names up to the length of a single line in the GDDRMSC member.

Note: When coded, only one HMC_BYPASS parameter statement per site is permitted.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 5, HMC-related parameters. Refer to “Option 5: HMC-related parameters” on page 85. The field name is HMC_BYPASS.siteid.

Syntax HMC_BYPASS.siteid= [*] or [lpar-name,lpar-name,...] or NONE

Variablessiteid The ID of the site where hardware management console actions are to

be bypassed.

* Indicates that HMC actions are to be bypassed for all LPARs at siteid.

lpar-name The names of the LPARs that production systems run in at siteid. These names must match siteid.LPAR.system-name GDDR parameters for the site. The word 'NONE' may be used in place of lpar-name.


EMC GDDR Parameters

HostComponent_CntlDsnThe HostComponent_CntlDsn parameter statement specifies the name of a PDS [library] and the member name where the EMC SRDF Host Component for z/OS parameters are stored.

Note: Only one HostComponent_CntlDsn parameter statement may be present in the input file.

The allocation of this PDS is done as part of SRDF Host Component installation. Additional members used by EMC GDDR are added to this library during EMC GDDR installation.

Note: “Create parameter members for SRDF Host Component on C-Systems” on page 34 provides additional information.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 4, Dataset names. Refer to “Option 4: Dataset names” on page 83. The replacement field name is 'Host Component control dataset name at System systemid'.

Syntax HostComponent_CntlDsn.c-system-name=dsname(member)

Variablesc-system-name The MVS system name of the C-System to which the statement

applies.

dsname The library pointed to by the SRDF Host Component started task’s RDFPARM DD statement.

member The name of the PDS member containing the SRDF Host Component started task's parameters.


EMC GDDR Parameters

IPL.system-name.siteidThe IPL.system-name.siteid parameter statement specifies the IPL parameters that EMC GDDR may use to IPL an EMC GDDR-managed system at the primary DASD site.

A production system can have an IPL parameter for each of sites DC1 and DC3. This is because the primary DASD can reside at any of these locations.

◆ A production system requires an IPL parameter both for site DC1 and site DC3.

◆ A production system needs an IPL parameter for site DC3 only if it will actually be IPL’ed from DC3 DASD (that is, during a DC3 test or in the case of a disaster). The system name at DC3 must be identical to the system name at DC1.

◆ A C-System is never IPL'ed at any site other than the one where it normally resides. However, if you wish to use the HMC Action panel to perform actions on C-Systems, you need to code an IPL.system-name.siteid EMC GDDR parameter for DC1 and DC3, as shown in the examples below. Failure to do so will result in asterisks being displayed for the IPL parameters of a C-System, accompanied by the message "GDDH001I - IPL parms not found". You will be unable to perform actions on a C-System using the EMC GDDR HMC Action panel.

The following example shows IPL.system-name.siteid parameters for a C-System at DC3 for a user wishing to IPL this system using the EMC GDDR HMC Action panel:

IPL.ZOSESYS2.DC1=2168,2051S2MIPL.ZOSESYS2.DC3=2168,2051S2M

The following is a similar example of IPL.system-name.siteid parameters for a C-System at DC1:

IPL.ZOSESYS1.DC1=3108,2051s1m IPL.ZOSESYS1.DC3=3108,2051s1m

In the example above, ZOSESYS1 is the system-name of the C-System residing at DC1. The provided IPL parameters are identical in the two parameters coded for this system, since it will only ever be IPL'd at DC1.

Any number of IPL.system-name.siteid statements may appear in the input file.

Use the D IPLINFO MVS system command to view IPL parameters. From the example below, if the LPAR currently has its primary DASD on DC1, you would code:

IPL.SYSB.DC1=0A1D,0A2602mn

Where 0A1D is the Sysres device address0A26 is the IODF device address02 is the LOADxx member suffixm is the IMSI Fieldn is the IEANUC0n suffix

RESPONSE=SYSBIEE254I 21.14.59 IPLINFO DISPLAY 860SYSTEM IPLED AT 15.59.20 ON 02/02/2007RELEASE z/OS 01.04.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


EMC GDDR Parameters


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 5, HMC-related parameters. Refer to “Option 5: HMC-related parameters” on page 85. The panel field name is 'IPL parameters at System systemid and Site siteid'.

Syntax IPL.system-name.siteid=IPL-parameters

Variablessystem-name The system name of an EMC GDDR-managed system which,

when the primary DASD site matches the site ID specified by siteid, may be IPL’ed by EMC GDDR using the specified IPL parameters.

siteid The site ID which, when equal to the primary DASD site, enables the system specified by system-name to be IPL’ed by EMC GDDR using the specified IPL parameters.

IPL-parameters This consists of the IPL load address and load parameters, separated by a comma, to be used when the primary DASD site matches the site ID specified by siteid and the name of the system to be IPL’ed matches the system identified by system-name.


EMC GDDR Parameters

IPLBCVS.system-name.siteidThe IPLBCVS.system-name.siteid parameter statement specifies the IPL parameters that EMC GDDR may use to IPL an EMC GDDR-managed system using BCV data at the secondary DASD site. “IPL.system-name.siteid” on page 122 provides more details about using IPL parameters.

Any number of IPLBCVS.system-name.siteid statements may appear in the input file.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 5, HMC-related parameters. Refer to “Option 5: HMC-related parameters” on page 85. The panel field name is 'IPL parameters at System systemid and Site siteid'.

Syntax IPLBCVS.system-name.siteid=IPL-parameters

Variablessystem-name The system name of an EMC GDDR-managed system which,

when the primary DASD site matches the site ID specified by siteid, may be IPL’ed by EMC GDDR using the specified IPL parameters.

siteid The site ID which, when equal to the primary DASD site, enables the system specified by system-name to be IPL’ed by EMC GDDR using the specified IPL parameters.

IPL-parameters This consists of the IPL load address and load parameters, separated by a comma, to be used when the primary DASD site matches the site ID specified by siteid and the name of the system to be IPL’ed matches the system identified by system-name.


EMC GDDR Parameters

JA_ACT_GK.siteidThe JA_ACT_GK.siteid statement defines an RDF group and gatekeeper combination through which asynchronous device sessions may be managed by EMC GDDR.

Note: There is one parameter statement for each RDF group on each EMC Symmetrix DASD controller being managed by EMC GDDR. Any number of JA_ACT_GK. siteid statements can appear in the input file, but any particular siteid-rdfgrp combination can appear only once.

The Symmetrix controller can contain any combination of CKD, FBA, and FBA-META devices subject to EMC’s configuration rules and limitations.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Update GDDR parameters>Option 2, Device-related parameters. Refer to “Option 2: Device-related parameters” on page 81. The panel field name is JA_ACT_GK.siteid.

Syntax JA_ACT_GK.siteid=gatekeeper,rdfgrp

Variables

Example The parameter statement J0_GK.DC1=A080,1A could result in any of the following commands:

SC SRDFA,LCL(A080,1A),ACT

SC VOL,LCL(A080,1A),DELETEPAIR,(FORCE,STAR),ALL

siteid The ID of the current primary DASD site. It can have the value DC1 or DC3.

gatekeeper The gatekeeper address through which, together with the specified RDF group, devices participating in asynchronous SRDF relationships are accessed.

rdfgrp The RDF group to be used with the specified gatekeeper to access devices participating in asynchronous SRDF relationships.


EMC GDDR Parameters

siteid.LPAR.system-nameEMC 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), this variable must be defined for every production system and EMC GDDR C-System. The value is cpc_name,lpar_name. There are no limits on the number of sited.LPAR.system-name statements supported.

The LPAR and CBU names for a system can be found using the D M=CPU MVS system command, as shown in the following sample output:

RESPONSE=SYSBIEE174I 20.59.34 DISPLAY M 781PROCESSOR STATUSID CPU SERIAL0 + 02F94E20961 + 02F94E20962 + 02F94E2096

CPC ND = 002096.S07.IBM.83.00000008F94ECPC SI = 2096.N03.IBM.83.000000000008F94ECPC ID = 00CPC NAME = ZOSESYSBLP NAME = ZOSESYSB LP ID = 2CSS ID = 0MIF ID = 2

+ ONLINE - OFFLINE . DOES NOT EXIST W WLM-MANAGEDN NOT AVAILABLE

CPC ND CENTRAL PROCESSING COMPLEX NODE DESCRIPTORCPC SI SYSTEM INFORMATION FROM STSI INSTRUCTIONCPC ID CENTRAL PROCESSING COMPLEX IDENTIFIERCPC NAME CENTRAL PROCESSING COMPLEX NAMELP NAME LOGICAL PARTITION NAMELP ID LOGICAL PARTITION IDENTIFIERCSS ID CHANNEL SUBSYSTEM IDENTIFIERMIF ID MULTIPLE IMAGE FACILITY IMAGE IDENTIFIER


Syntax siteid.LPAR.system-name=central-processing-complex-name,LPAR-name

Variables

Example DC1.LPAR.PRODSYS1=ZOSESYS1,PRODLP1DC1.LPAR.PRODSYS1=ZOSESYS1,PRODLP2DC1.LPAR.PRODSYS1=ZOSESYS1,PRODLP3

siteid The ID of the site location being specified. It can have the value DC1 or DC3.

central-processing-complex-name The name of the central processor where the LPAR is defined.

LPAR-name The name of the LPAR that this system runs in at siteid.

system-name The z/OS system name of the EMC GDDR managed system that will reside in LPAR-name when at site siteid.


EMC GDDR Parameters

MSC_GROUPNAME.siteidThis parameter specifies the MSC group name in effect when the primary DASD site is the site specified by siteid.

The value of this parameter is passed to the M6, M9, and ME utilities, and it is used in EMC GDDR MSC refresh and SSID operations.


Syntax MSC_GROUPNAME.siteid=msc_groupname

Variablessiteid The site ID for which, when this site is the primary DASD site,

the MSC group name is being specified. The value must be either DC1 or DC3.

msc_groupname The MSC group name to use when the primary DASD site is the site specified by siteid.


EMC GDDR Parameters

MSFID.system-nameThis parameter specifies the ID of the MSF system associated with an EMC GDDR C-System or a production system managed by EMC GDDR for which CA-OPS/MVS is available.

Note: Each C-System or production system must have an associated MSF ID specified by an MSFID.system-name statement.

This statement furnishes the specification of the named MSF ID.


Syntax MSFID.system-name=msfid

Variablessystem-name The MVS system name of an EMC GDDR C-System or EMC

GDDR-managed production 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 or production system identified by system-name.


EMC GDDR Parameters

PSTR.siteid.sysid.strnameThe PSTR parameter defines a list of Coupling Facility names for the specified Coupling Facility Structure at site siteid and for system sysid.

During scripts which have a Coupling Facility Structure management step, processing verifies each defined structure is located in one of the named coupling facilities, and attempts to move the structure if required.


Syntax PSTR.siteid.sysid.strname=cfname1,cfname2,cfname3,..

Variables

Example

Related Information The IBM MVS System Commands reference provides the following rules for Couple Facility and Couple Facility Structure names:

Rules for Couple Facility names:

Length: 1-8 characters

Position 1: Uppercase alphabetic

Position 2-8: Uppercase alphabetic, numeric, or _, @, $, #

Rules for Couple Facility Structure names:

Length: 1-16 characters

Position 1: Uppercase alphabetic

Positions 2-16: Uppercase alphabetic, numeric, or _, @, $, #

siteid The site location of the MVS system being managed; it can have one of the following values: DC1 or DC3.

sysid The MVS system name of the system being managed by EMC GDDR, which is specified using the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or equivalent parameter file.

strname Couple Facility Structure name. “Related Information” below provides additional information.

cfname One or more Couple Facility names. “Related Information” below provides additional information.


EMC GDDR Parameters

ResourcePak_STC_Name.c-system-name This parameter specifies the jobname of the ResourcePak Base job or started task on a C-System.

Note: This parameter is required for each C-System, and may be specified only once per C-System.

The value of this parameter is used in MODIFY commands issued from within scripts running on the C-System to which the statement applies.


Syntax ResourcePak_STC_Name.c-system-name=jobname

Variables

Example ResourcePak_STC_Name.C114=EMCRSPK1

c-system-name The MVS system name of the C-System to which the statement applies.

jobname The jobname of the ResourcePak Base job or started task on the C-System to which the statement applies.


EMC GDDR Parameters

RESUME_GK.DC3This parameter specifies the gatekeeper to use to set DC3 R2 volumes to R/W for DC3 resumption scripts.


Syntax RESUME_GK.DC3=gatekeeper

Variables

Example RESUME_GK.DC3=0700

gatekeeper The gatekeeper to use to access R2 devices on DC3.


EMC GDDR Parameters

SITE.system-nameThis parameter specifies the site location of a system that is to be managed by EMC GDDR or that is to be an EMC GDDR C-System.

Note: There must be at least one system at each of sites DC1 and DC3that is not the C-System at that site. Thus, for siteids DC1 and DC3, there must be at least two parameter statements.

This statement furnishes the specification of the named siteid.


Syntax SITE.system-name=siteid

Variablessystem-name The MVS system name of the system being managed by EMC

GDDR, which is specified using the SYSNAME=system-name statement in SYS1.PARMLIB(IEASYS00) or equivalent parameter file.

siteid The site location of the MVS system being managed; it can have one of the following values: DC1 or DC3.


EMC GDDR Parameters

SRDFA.Devices.siteidThis parameter specifies the SRDF/A device ranges that are to be managed at site siteid.

Note: Any number of SRDFA.Devices.siteid statements may be included in the input file.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 2, Device-related parameters. Refer to “Option 2: Device-related parameters” on page 81. The panel field name is SRDFA.Devices.siteid.

Syntax SRDFA.Devices.siteid=gatekeeper,rdfgrp,recovery-rdfgrp,symm-dev-range

Variablessiteid The site location of the devices in the current range that are being

managed by EMC GDDR. It must be DC1 or DC3.

gatekeeper The gatekeeper to be used to control the SRDF/A status of the devices in the specified range.

rdfgrp The SRDF/A RDF group to be used.

recovery-rdfgrp The SRDF/A group in the remote controller at DC3, connecting DC3 to the secondary DASD site.

symm-dev-range The Symmetrix device number range of the SRDF/A devices.


EMC GDDR Parameters

sPLX.system-name.type.aorp.siteidThe sPLX.system-name.type.aorp.siteid statement specifies the name of a primary or alternate couple dataset to be used on a specified system when the primary DASD is located at a specified site.

Note: Each couple dataset must be catalogued on all systems in the sysplex.

There must be a primary and an alternate couple dataset statement for each system in the 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 used are located wherever the primary DASD currently resides.


Syntax sPLX.system-name.type.aorp.siteid=couple-dataset

Variabless The script type under which the specified couple dataset

should be used. Values may be null or U:

◆ If null, the couple dataset should be used when a Planned script is running.

◆ If U, the couple dataset should be used when an Unplanned script is running.

system-name The name of the system on which the specified couple dataset is to be used.

type The type of the specified couple dataset, one of the following:

◆ SYS

◆ ARM

◆ CFR

◆ LOG

◆ SFM

◆ WLM

Sysplex couple dataset type

Automatic Restart Manager couple dataset type

CFRM (Coupling Facility Resource Management) couple dataset type

LOGR couple dataset type

Sysplex Failure Management couple dataset type

Workload Manager couple dataset type

aorp This indicates whether the specified couple dataset is to be used as a primary or an alternate couple dataset. Values may be P or A:

◆ If P, it is used as a primary couple dataset.

◆ If A, it is used as an alternate couple dataset.

siteid The siteid which is compared with the current primary DASD site in determining whether the specified couple dataset is to be used. If the two are equal, the couple dataset is used; otherwise it is not.

couple-dataset The dataset name of the couple dataset of the specified type which will be used under the conditions indicated by the values specified in the parameter keyword.


EMC GDDR Parameters

WTOR_RETRIESThis optional parameter allows you to prolong the time EMC GDDR has to wait for a certain event.

The EMC GDDR WTOR module accept the RETRIES argument, which specifies the number of times to re-issue the same WTOR when intercepting a timeout condition. You can end the wait by replying negatively to the WTOR message. By default (WTOR_RETRIES=0) the WTOR will be issued just once, resulting in script termination with RC=32 if a timeout occurs.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, GDDR performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Number of WTOR retries on timeout'.

Syntax WTOR_RETRIES = nnn

Variablesnnn This must be a valid numeric value of 0 to 999. The default value is 0.


EMC GDDR Parameters

WTOR_Wait_IntervalThis parameter specifies 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 referenced by message GDDP082I during batch parameter load processing.

Note: At most, one WTOR_Wait_Interval parameter statement may be present in the input file.

This parameter is optional. If not specified, a default value of 600 is used, which is equivalent to 10 minutes.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, GDDR performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Default max WTOR time before timeout'.

Syntax WTOR_Wait_Interval=timeout-value

Variablestimeout-value This must be a valid numeric value between 1 and 3600. The default

value is 600.


EMC GDDR Parameters

Performance and tuning parametersThe parameters listed in this section are initialized from software-supplied defaults during parameter loading. You can change them using the GDDR Administrator Primary Options panel.

CF_REBUILD_TIMEOUT.siteidThis parameter determines the time allowed for rebuilding the managed Coupling Facility structures.

During this wait time, processing checks for completion about every 6 seconds or about 100 times for CF Structure rebuild completion.


Syntax CF_REBUILD_TIMEOUT.siteid=nnnn

Variablessiteid The site location of the MVS system being managed; it can have one

of the following values: DC1 or DC3.

nnnn The number of seconds to allow for the processing required to rebuild Coupling Facility structures. Value values are 1-3600. The default value is 600.

Performance and tuning parameters 137

EMC GDDR Parameters

ECGCLEAN.Task.NumberThe ECGCLEAN.Task.Number statement defines the number of subtasks that the ECGUTIL or ECGCLEAN utility will attach when cleaning ConGroup bits from devices. This parameter is referenced by message GDDP082I during batch parameter load processing.

The ECGCLEAN.Task.Number parameter statement is optional. If not specified, a default value of 22 will be assumed.

Source Initialized from software-supplied default at batch parameter load.

This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, Performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Number of ECGUTIL Subtasks'.

Syntax ECGCLEAN.Task.Number=nn

Variables

Example ECGCLEAN.Task.Number=12

nn A number from 1 to 22. Default is 22.


EMC GDDR Parameters

Event monitor state check intervalThe Event monitor state check interval parameter specifies the number of seconds the event monitor waits between successive checks of the various EMC GDDR event indicators. This parameter is referenced by message GDDP082I during batch parameter load processing.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, Performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Event monitor state check interval'.

Variablesnumber-of-seconds 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.


EMC GDDR Parameters

Seconds between GDDR heartbeatsThe Seconds between GDDR heartbeats parameter specifies the time in seconds between each heartbeat cycle of the heartbeat monitor. This parameter is referenced by message GDDP082I during batch parameter load processing.

Note: This parameter may be changed at any time. If this value is changed, the value must be changed on all C-Systems. The heartbeat monitor will recognize the change on the next heartbeat cycle without a recycle of the heartbeat monitor started task.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, GDDR performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Seconds between GDDR heartbeats'.

Variablesnumber-of-seconds 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.


EMC GDDR Parameters

HMC_Timeout.siteidThe HMC_Timeout.siteid parameter specifies the maximum number of milliseconds a request to an HMC console at a specified site may remain outstanding before it will be considered to have timed out. This parameter is referenced by message GDDP082I during batch parameter load processing.

When no response has been received by the specified time, an error return will be made to the requesting routine.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 5, HMC-related parameters. Refer to “Option 5: HMC-related parameters” on page 85. The replacement field name is 'HMC timeout value at Site siteid'.

Syntax HMC_Timeout.siteid=timeout-value

Variablessiteid The ID of the site to whose hardware management consoles the

specified time-out value applies.

timeout-value The maximum number of milliseconds that may elapse for a request to an HMC console at the specified site before the request is considered to have timed out. The maximum value that may be specified is 99999; the minimum is 1. The default value is 25000.


EMC GDDR Parameters

Missing heartbeat intervalThe Missing heartbeat interval parameter specifies the number of seconds that a C-System heartbeat can be late, as detected by the other C-Systems, before the other C-Systems start to consider it "dead". This parameter is referenced by message GDDP082I during batch parameter load processing.

Note: If this value is changed, the value must be changed on all C-Systems. The heartbeat monitor will recognize the change on the next heartbeat cycle without a recycle of the heartbeat monitor started task.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, GDDR performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Missing heartbeat interval'.

Variablesnumber-of-seconds 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 value is 30.


EMC GDDR Parameters

Max missing heartbeat intervalsThe Max missing heartbeat intervals parameter allows a heartbeat monitor to determine whether another C-System should be declared "dead". The determination is based upon a maximum number of times that a heartbeat monitor, upon awakening from its own wait interval, may detect an unchanged heartbeat value from that other C-System. This parameter is referenced by message GDDP082I during batch parameter load processing.

Note: If this value is changed, the value must be changed on all C-Systems. The heartbeat monitor will recognize the change on the next heartbeat cycle without a recycle of the heartbeat monitor started task.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option P, Manage GDDR parameters>Option 4, Update GDDR parameters>Option 1, GDDR performance and tuning parameters. Refer to “Option 1: GDDR performance and tuning parameters” on page 80. The panel field name is 'Max missing heartbeat intervals'.

Variablesnumber 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.


EMC GDDR Parameters

Audit monitoring parameters

SMF.LOGThis parameter furnishes the user's specification of the GDDR Audit Monitoring SMF collection options.

Note: Each C-System must have SMF collection enabled as an installation parameter within CA-OPS/MVS in order to produce GDDR Audit Monitoring SMF records. If CA-OPS/MVS doesn't support SMF logging on a C-System, use of the SMF.LOG parameter will result in an error in the batch parameter load job.


This parameter may be changed using the GDDR Administrator Primary Options panel>Option S, Manage SMF Logging Options. “Option S — SMF: Manage SMF Logging Options” on page 94' provides more information.

Syntax SMF.LOG=SR(nnnnn),LS(y/n),LE(y/n),LW(y/n),LA(y/n),D(y/n),WT(x000y,x000y,x000y,x000y)

Note: All clauses within the SMF.LOG parameter are optional.

VariablesSR(nnnnn) nnnnn is the SMF subrecord number to be assigned to SMF

records produced by GDDR Audit Monitoring collection. The same subrecords number is used for records produced by all C-Systems. The default value is 2000.

LS(y/n) Y or N indicates whether to log GDDR State changes. The default value is N.

LE(y/n) Y or N indicates whether to log Error WTO messages. The default value is N.

LW(y/n) Y or N indicates whether to log Warning WTO messages. The default value is N.

LA(y/n) Y or N indicates whether to log all WTO messages. The default value is N.

D(y/n) 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 Administrator Primary Options Menu Option M - Specify GDDR message output options. The default value is N.


EMC GDDR Parameters

WT(x000y,x000y,x000y,x000y)

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.

Where:

◆ x is the mask character for the 4th position of the 8-character message ID.

◆ 000 are the mask characters for the 5th through 7th positions of the 8-character message ID.

◆ y is the mask character for the 8th 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.

Audit monitoring parameters 145

EMC GDDR Parameters


5Invisible Body Tag

This chapter describes various maintenance procedures for EMC GDDR. Topics are:

◆ Setting up a new EMC GDDR C-System .................................................................. 148◆ Renaming an existing EMC GDDR C-System ......................................................... 150◆ Adding a new production system or sysplex to EMC GDDR............................... 151◆ Adding new RDF groups to EMC GDDR................................................................. 154◆ Adding new devices to EMC GDDR......................................................................... 157◆ Removing an RDF group from EMC GDDR control .............................................. 158◆ Removing devices from EMC GDDR control .......................................................... 159◆ Removing a system or a sysplex from EMC GDDR................................................ 160

EMC GDDRMaintenance

Procedures

EMC GDDR Maintenance Procedures 147

EMC GDDR 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, 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 DC3 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 J — JobVals: View or change default job values” on page 67.

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 EMC GDDR parameters:

• siteid.C.System.Systemid

• IPL.system-name.siteid

• MSFID.system-name

• ResourcePak_STC_Name.c-system-name

• SITE.system-name

• SYSNAME.msfid

4. Update CA-OPS/MVS MSF parameters:

a. On each C-System, add an entry for the new C-System to the CA-OPS/MVS REXX dataset member MSFINIT:

b. On each production system, add an entry for the new C-System to the CA-OPS/MVS REXX dataset member MSFINIT:

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





5. Update CA-OPS/MVS CCI parameters:

a. On each C-System, add the following entries for the new C-System to the CA Event Notification/CCI parameter member CCIssssssss.

b. On each production 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


NODE( …add appropriate parameters for the new system… )

CONN, ssssssss


Setting up a new EMC GDDR C-System 149


Renaming an existing EMC GDDR C-SystemComplete the following steps to rename an existing EMC GDDR C-System:

1. Perform the following EMC GDDR parameter changes

• Update parameter DCn.C.System.Systemid where DCn is the site of the C-System, replacing the old C-System name with the new C-System name.

• Add a parameter statement IPL.ssssssss.DCn for the new C-System name and delete the statement for the old C-System name.

• Update parameter MSFID.ssssssss where ssssssss is the old C-System name, replacing the old C-System name with the new C-System name.

• Add a SYSNAME.mmmm=ssssssss statement where ssssssss is the new C-System name and mmmm is the MSF ID of the C-System. Delete the SYSNAME.mmmm=ssssssss statement where ssssssss is the old C-System name and mmmm is the MSF ID. If the MSF ID has not changed, you may update the existing SYSNAME.mmmm statement, replacing the old C-System name with the new C-System name instead.

• Update the SITE.ssssssss statement where sssssssss is the old C-System name, replacing the old system name with the new C-System name.

• Update the ResourcePak_STC_Name.c-system-name parameter with the new name for the C-System.

• Add DCn.LPAR.ssssssss statements where ssssssss is the new C-System name and delete DCn.LPAR.ssssssss statements where ssssssss is the old C-System name.

2. Update CA-OPS/MVS MSF parameters.

3. Update CA-OPS/MVS CCI parameters.

4. Run a parameter load with initialization using the procedure described in ‘“EMC GDDR ISPF profiles” on page 96.



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.

1. Ensure that ResourcePak Base is set up using common parameter definitions already used by the other systems in the Enterprise Consistency Group.

2. Make the following EMC GDDR parameter changes:

• Add the following couple dataset parameters for the new production system(s):

– PLX.ssssssss.ttt.P.DCn– PLX.ssssssss.ttt.A.DCn– UPLX.ssssssss.ttt.P.DCn– UPLX.ssssssss.ttt.A.DCn

• Add the following IPL parameters for the new production system(s):

– IPL.ssssssss.DC1 statements are required for each new system– IPL.ssssssss.DC3 statements are only required if system ‘ssssssss’ is to be

available at DC3• Add MSFID.ssssssss statements for the new system(s).

• Add SITE.ssssssss statement(s) for the new system(s).

• Add DCn.LPAR.ssssssss statement(s) for the new system(s).

• Add CONT.system-name statement(s) for the new system(s).

• Update SYSNAME.mmmm statements for the new system(s).


4. If CA-OPS/MVS is available on the new production system:

a. Update CA-OPS/MVS MSF parameter hlq.ssssssss.REXX (MSFINIT) on each C-System, adding an entry for each new production system similar to the following:

b. On each new production system, add an entry for each C-System to the CA-OPS/MVS REXX dataset member MSFINIT. The entry should be similar to the following:

5. If CA-OPS/MVS is not available on the new production system, follow the steps for installing the EMC z/OS Console Monitor started procedures described in “Install EMC GDDR C-System started procedures” on page 38.


Where “ssssssss” is the MSF ID or the MVS system name of the new production system


Where “ssssssss” are the MSF ids or the MVS system name of each C-System

Adding a new production system or sysplex to EMC GDDR 151


6. Update the CA event notification parameter hlq.CA90.PPOPTION (CCIssssssss) on each C-System, adding an entry for each new production system similar to the following:

7. On the new production system, update the CA event notification parameter hlq.CA90.PPOPTION (CCIssssssss) adding the following entries for each C-System:

NODE( …add appropriate parameters for the new production system… )

CONN,ssssssss

Where “ssssssss” is the MSF ID or the MVS system name of the new production system

NODE( …add appropriate parameters for the C1 system… )NODE( …add appropriate parameters for the C3 system… )

CONN, C1CONN, C2CONN, C3

Where “C1” is the MSF ID or the MVS system name of the DC1 C-SystemWhere “C3” is the MSF ID or the MVS system name of the DC3 C-System



Changing the MSC group nameTo change the name of the MSC 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. Update ‘BCV.’ parameters that include the old MSC group name, replacing the old group name with the new group name.

2. Load the updated parameters, following the procedure described in “EMC GDDR ISPF profiles” on page 96.

3. Update MSC group parameters on all systems to reflect the new MSC group name.

4. Update RDF Manager parameter members to reflect the MSC group name.

• SITEDC1 – MSC_5773 = new MSC group name

• SITEDC3 – MSC_5773 = new MSC group name

5. Update the member referenced by the HostComponent_CntlDsn.c-system-name parameter:

• MSC_GROUP_NAME = new MSC group name

6. Bring the new RDF group(s) into the live SRDF/A environment by performing the following actions:

a. Stop the SRDF/A with MSC environment by entering the MSC,PENDDROP command.

b. Restart SRDF/A.

Changing the MSC group name 153


Adding new RDF groups to EMC GDDRThis section describes how to add new DASD to an existing SRDF/A 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/A 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_JA

where:

For each new RDF group, two GNS groups must be defined: one for DC1 and one for DC3.

3. Define or modify MSC GNS groups, or add gatekeeper and RDF groups in the RDF manager parameter members (SITEUDC1 and SITEUDC3) referenced in Step 5 on page 155.

Depending on whether you are adding a new controller or just new RDF group(s) in one or more existing controllers, you will need to define new MSC GNS groups or update existing MSC GNS group definitions:

• If adding new controllers, go to Step 4 on page 154.

• If adding new RDF groups to an existing controller, go to Step 6 on page 156.

4. If adding new controller(s):

If adding a new DASD controller(s) then the following types of MSC GNS groups will need to be defined:

• Gatekeeper

• RDF group

For each type, one GNS group is required for DC1 and one for DC3. Create the new GNS groups using the EMCGROUP utility. The EMC ResourcePak Base for z/OS Product Guide describes how to create GNS groups.

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 DC3.

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.



The GNS group(s) defined may adhere to the following naming convention:

c. Define MSC mode MSC GNS groups.

The following GNS groups must be defined for starting SRDF/A in MSC mode. These are the same as groups GDDRn_MSC_ddd_xxxxx_RAGRPn, except that they have no associated recovery RDF group in the GNS group definition:

– GDDR1_MSC_ddd_xxxxx_RAGRPn_NOSTAR– GDDR2_MSC_ddd_xxxxx_RAGRPn_NOSTAR

5. Add GNS group(s) to MSC parameter members.

Add the appropriate GNS group(s) to the RDF manager parameter members for each site:

a. SITEDC1

To the site DC1 RDF manager parameter member SITEDC1, when adding one or more new controller(s), add a new MSC session for each pair of MSC GNS groups using control statements such as the following:

MSC_INCLUDE_SESSION = SCFG(GDDR1_MSC_ddd_xxxxx_GKn, GDDR1_MSC_ddd_xxxxx_RAGRPn)

These must be added to the MSC_GROUP_NAME definition.

b. SITEDC3

To the site DC3 RDF manager parameter member SITEDC3, when adding one or more new controllers, add a new MSC session for each pair of MSC GNS groups using control statements such as the following:

MSC_INCLUDE_SESSION = SCFG(GDDR2_MSC_ddd_xxxxx_GKn, GDDR2_MSC_ddd_xxxxx_RAGRPn)


c. SITEUDC1

To the site DC1 RDF manager parameter member SITEUDC1, when running SRDF/A in MSC mode and adding one or more new controllers, add a new MSC session for each pair of MSC GNS groups using control statements such as the following:

MSC_INCLUDE_SESSION = SCFG(GDDR1_MSC_ddd_xxxxx_GKn, GDDR1_MSC_ddd_xxxxx_RAGRPn_NOSTAR)


GDDRn_MSC_ddd_xxxxx_GKn – for MSC GatekeepersGDDRn_MSC_ddd_xxxxx_RAGRPn – SRDF/Star ragroup pairsGDDRn_MSC_ddd_xxxxx_RAGRPn_NOSTAR – for MSC-only RDF groups

where:n – has the value 1 or 3, used to identify which group to use depending upon the location of the primary DASD, either DC1 or DC3ddd – has the value CKD or FBA, depending upon what type of DASD is defined in the GNS groupxxxxx - is the last five(5) digits of the Symmetrix Controller Serial Numbern – is a number, starting at 1

Adding new RDF groups to EMC GDDR 155


d. SITEUDC3

To the site DC3 RDF manager parameter member SITEUDC3, when running SRDF/A in MSC mode and adding one or more new controllers, add a new MSC session for each pair of MSC GNS groups using control statements such as the following:

MSC_INCLUDE_SESSION = SCFG(GDDR2_MSC_ddd_xxxxx_GKn, GDDR2_MSC_ddd_xxxxx_RAGRPn_NOSTAR)


6. If adding new RDF group(s) to an existing controller(s):

If adding one or more new RDF groups to an existing controller, existing MSC GNS groups will have to be extended to add the new RDF group(s) and to add the new gatekeeper devices.

a. Add the new RDF group(s) to the following GNS groups:

• GDDR1_MSC_ddd_xxxxx_RAGRPn• GDDR2_MSC_ddd_xxxxx_RAGRPn

b. Add the new MSC gatekeepers to the following MSC GNS groups:

• GDDR1_MSC_ddd_xxxxx_GKn• GDDR2_MSC_ddd_xxxxx_GKn

c. Add the new RDF group(s) for starting SRDF/A in MSC mode to the following GNS groups:

• GDDR1_MSC_ddd_xxxxx_RAGRPn_NOSTAR• GDDR2_MSC_ddd_xxxxx_RAGRPn_NOSTAR

7. 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 BCV. parameter statements.

b. Add GNS .siteid.loc.jtype parameters for the new GNS groups being added.

c. Add parameter statements for the J0 and JA gatekeepers that will be associated with the new RDF group(s).

d. Add SRDFA.Devices.siteid parameters for all devices in the RDF groups being added.

8. Distribute the changed EMC parameter members to all systems participating in the SRDF/A environment.

9. Bring the new RDF group(s) into the live SRDF/A environment by performing the following actions:

a. Stop the SRDF/A with MSC environment by entering the MSC,PENDDROP command.

b. Restart SRDF/A.

10. Run a parameter load with initialization using the procedure described in “EMC GDDR ISPF profiles” on page 96.



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. Stop SRDF/A with MSC by entering the MSC,REFRESH command.

3. Create SRDF/A 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.


• If any of the standard devices being added are to have an associated BCV, create appropriate BCV.DCn.MSC parameter statements in the EMC GDDR parameter member.

• Add the SRDFA.Devices.siteid parameter for each range of devices.

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. Restart SRDF/A.

9. Run a parameter load with initialization using the procedure described in “EMC GDDR ISPF profiles” on page 96.

Adding new devices to EMC GDDR 157


Removing an RDF group from EMC GDDR controlComplete the following steps to remove an RDF group from EMC GDDR control:

1. Ensure that the RDF groups to be removed from the control of EMC GDDR have been removed from any relevant MSC GNS group.


• Delete all BCV parameter statements that reference the standard devices being removed.

• Delete all GNS parameter statements that reference the RDF groups being removed.

• Delete all JA_ACT_GK.siteid parameter statements that reference the RDF groups being removed.

• Delete SRDFA.Devices.siteid parameters for all devices in the RDF group(s) being removed.

3. Stop the SRDF/A environment.

• Stop the environment by entering the MSC,PENDDROP command.

4. Restart SRDF/A protection.

Once successfully restarted, check to ensure that the RDF group(s) being deleted are no longer part of the MSCgroups.




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. Stop SRDF/A by entering the MSC,PENDDROP command.

2. Delete the SRDF/A relationships for the devices being removed.

3. Update your GNS device group definitions so they no longer include the devices being removed from EMC GDDR control.

4. Issue a GNS,REFRESH command.

5. Issue a ConGroup REFRESH,FORCE command.

6. Restart SRDF/A.

7. Update EMC GDDR parameters:

• If any of the standard devices being removed have an associated BCV, remove the associated ‘BCV.’ from the EMC GDDR parameter member.

• Remove the device ranges from the following parameter:

– SRDFA.Devices.siteid


Removing devices from EMC GDDR control 159


Removing a system or a sysplex from EMC GDDR

Note: On the system or systems being removed, ensure that the ResourcePak Basestarted procedures have been stopped and will no longer be used.

1. Delete the following parameter statements for the system(s) being removed:

• PLX.ssssssss.ttt.P.DCn

• PLX.ssssssss.ttt.A.DCn

• UPLX.ssssssss.ttt.P.DCn

• UPLX.ssssssss.ttt.A.DCn

2. Delete the IPL.ssssssss.DCn statements for the system(s) being removed.

3. Delete the MSFID.ssssssss statements for the system(s) being removed.

4. Delete the SITE.ssssssss statements for the system(s) being removed.

5. Delete the SYSNAME.mmmm statements for the system(s) being removed.

6. Update hlq.GDDRvrm.PARMLIB member GDDRLPAR to delete the DCn.LPAR.ssssssss statements for the system(s) being removed.

7. Remove the CONT.system-name parameter.

EMC GDDR AOF rule setThe EMC GDDR CA-OPS/MVS AOF rules must be disabled and deleted from the system(s) being removed.

Update CA-OPS/MVS MSF parameters

hlq.ssssssss.REXX ( MFSINIT )

On each C-System, from the CA-OPS/MVS REXX dataset member MSFINIT, delete the entries for each production system being removed.

On each production system being removed, from the CA-OPS/MVS REXX dataset member MSFINIT, delete the entry for each C-System.

Update CA-OPS/MVS CCI parameters

hlq.CA90.PPOPTION( CCIssssssss )

On each C-System, from the CA Event Notification/CCI parameter member CCIssssssss, delete the entries for each production system being removed.

On the each production system being removed, from the CA Event Notification/CCI parameter member CCIssssssss, delete the entries for each C-System.



Special casesIn an SRDF/A environment, special consideration must be given to devices that are not SRDF/A linked to DC3, specifically volumes containing the following system data:

◆ Page datasets

◆ Non-LOGR couple datasets

These datasets are replicated to DC3 using SRDF Adaptive Copy mode; therefore they are not managed by the EMC GDDR restart process. Manual actions to make them Ready and Read/Write Enabled are needed when tests are performed using the R2 devices at DC3.

Use of the "Perform test IPL from BCV’s at DC3" script requires no manual actions. EMC GDDR will control the BCV SPLIT operations for volumes outside of EMC GDDR control.

To avoid this problem, the following procedures needed to be adopted.

Page datasets ◆ All volumes containing page datasets must be paired up (using an adaptive copy

RDF group defined specifically for this purpose) to appropriate DC3 volumes and allowed to synch up. Once in synch, the pairs must be suspended. This action must be carried out any time paging volumes are added or moved in the configuration.

◆ Volumes used for page datasets must be dedicated volumes, that is, they must contain no other system or user data.

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 161

6Invisible Body Tag

This chapter describes the EMC GDDR Audit Monitoring Facility. Topics are:

◆ Overview ....................................................................................................................... 164◆ Implementation tasks .................................................................................................. 165◆ EMC GDDR audit monitoring SMF extract and report JCL .................................. 166◆ CA-OPS/MVS environment monitoring.................................................................. 167

EMC GDDR AuditMonitoring Facility

EMC GDDR Audit Monitoring Facility 163

EMC GDDR 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 165 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 165 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: GDDR state variables (view only)” on page 90.

“GDDR SAY and state monitoring implementation” on page 165 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 167 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 of “Make EMC GDDR AOF rules available to CA-OPS/MVS” on page 41.

Implementation tasks 165


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 flowSMF 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 outputThe 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 167

AInvisible Body Tag

This appendix describes user exit routines. Topics are:

◆ User exit programming considerations .................................................................... 170◆ Exit specifications......................................................................................................... 172

Appendix

C:Starti

ngand

Stopping

Workloads

Appendix

D:GDDR

UserExits

EMC GDDR User Exits

EMC GDDR User Exits 169

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, simply recompile your updated source into your custom OPSEXEC dataset.

Built-in routines available to exitsExit 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 171

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

GDDRUX03This 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)



GDDRUX04This 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 173

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.


GDDRUX06This 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

GDDRUX07This 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 175

EMC GDDR User Exits


BInvisible Body Tag

This appendix describes parameter validation rules. Topics are:

◆ Syntax rules ................................................................................................................... 178◆ Parameter statements providing component specifications.................................. 179◆ Consistency rules.......................................................................................................... 180◆ Completeness rules ...................................................................................................... 181

Appendix

D:GDDR

UserExits

Parameter ValidationRules

Parameter Validation Rules 177

Parameter Validation Rules

Syntax rules1. A couple dataset type must be one of the values ARM, CFR, LOG, SFM, SYS, or

WLM.

2. A dataset name must conform to the requirements of a valid MVS dataset name.

3. A GNS group name must have from 1 to 65 characters which are either alphanumeric or any special characters permitted in GNS group names. The first character may not be numeric.

4. An IP address must consist of four decimal numbers each having a value between 0 and 255 and separated from adjacent numbers by a period.

5. A job name must conform to the requirements of a valid MVS job name.

6. An MSF ID must conform to the requirements of a valid CA-OPS/MVS MSF ID.

7. A number must conform to the requirement listed below corresponding to its context:

• A global variable sequence number

• A number from 1 to 22 applying to task number

• A three-digit number applying to heartbeat monitor or event monitor processing

• An SMF record type from 128 to 255

• A one- to five-digit number applying to HMC processing

• A one- to four-digit number applying to WTOR requests

8. An SRDF specification must conform to the requirement listed below corresponding to its context:

a. <gkp>,<rdfgrp>,<start-lcl-dev>-<end-lcl-devaddr>,<start-rmt-dev>

b. <gkp>,<rdfgrp>,<start-lcl-dev>-<end-lcl-devaddr>,FBA

c. <gkp>

9. A system name must conform to the requirements for a SYSNAME value in SYS1.PARMLIB.

10. A site ID must be one of the values DC1 or DC3. In some contexts, not all of these are valid.

11. A character string must conform to the requirement listed below corresponding to its context:

• load parameter (ipl device address, comma, ipl parameter)

• 30-character call override value

• a job statement image



Parameter statements providing component specificationsTable 8 shows, for each component type, the parameter statements that provide a specification for that component type.

Table 8 Parameter statements providing component specifications

Component type Specification parameter statement

C-System site_id.C.System.Systemid=c_system-sysname

GNS group GNS.site_id.loc.jtype=gns_group_name

MSF ID MSFID.system_name=msf_id

System SITE.system_name=site_id

Site site_id.C.System.Systemid=c_system-sysname

Contingency system CONT.system_name=contingency_system_name

Parameter statements providing component specifications 179


Consistency rules1. If a site is not specified (on a siteid.C.System.Systemid statement), globals and

parameters incorporating siteids as references may not specify that site.

2. If a C-System name is not specified (on a siteid.C.System.Systemid statement), globals and parameters incorporating C-System names as references may not specify that C-System name.

3. The system names specified by SYSNAME.msfid statements must all be different.

4. If system-name is the value of SYSNAME.msfid, then msfid must be the value of MFSID.system-name.

5. The set of system names on SYSNAME statements must be the same as the set of system names on MSFID statements.

6. The set of MSF ids on MSFID statements must be the same as the set of MSF ids on SYSNAME statements.

7. The set of system names on SITE statements must be the same as the set of system names on SYSNAME statements and the set of system names on MSFID statements.

8. A contingency system on a CONT statement must be at DC1 or DC3. A system and its contingency system must reside at different sites. A system may be a contingency system for only one system.

9. The same sysplex name cannot occur at different sites.



Completeness rules1. At least one non-C-System (production system) must be specified at each of sites

DC1 and DC3.

2. Every GDDR-managed system must have a contingency system.

3. A production system <s> must have an IPL location at both DC1 and DC3 (that is, IPL.<s>.DC1 and IPL.<s>.DC3 are required).

4. Every C-System must have an HMC IP address defined.

Completeness rules 181

CInvisible Body Tag

This appendix describes the EMC GDDR z/OS Console Monitor. Topics are:

◆ Introduction .................................................................................................................. 184◆ z/OS Console Monitor — GDDRPBAL.................................................................... 185◆ z/OS operator console commands ............................................................................ 186◆ BAL command processor — BALC ........................................................................... 187

EMC GDDR z/OSConsole Monitor

EMC GDDR z/OS Console Monitor 183

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.

Note: A GDDRPBAL job with a PSYS parameter is required to be running on each EMC GDDR protected production system. A GDDRPBAL job with a CSYS parameter is required to be running on each EMC GDDR C-System.

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 186.

Sample debug outputGDDRPBAL DEBUG REQUESTED. DEBUG LOG STARTED. MESSAGE: GDDRBALC,DEBUG,SMCASID=X1E

,DATE=07199,TIME=10:00:71,DFARELS=03010600,IP=010.2GDDRPBAL 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 185


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 188 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 187


BAL CSC portsThe 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.


Index

AActivate command 66adding a new production system 151adding new RDF groups 154administrator facilities 59Administrator Primary Options menu 59alerts, creating 173#01ALLOC, mainframe installation kit 26allocating global variable backup dataset 39AOF rules 41, 160

suppressing 175#04APPLY, mainframe installation kit 26AUTHCMD 32AUTHPGM 32Automation flag 60

Bbacking up global variables 103backup dataset 117BCV volumes, defining 106BCV.DC1.ONLY parameter 107BCV.DC3.ONLY statement 107, 108BCV.siteid.MSC statement 106

CCA-OPS/MVS 41

AOF rules 41, 160changing access rules 43customizing 41merging user applications 46OPSVIEW facilities 97updating CCI parameters 46updating OPSMAIN and OPSOSF 44

CA-OPS/MVS OPSVIEW Primary Options Menu 58CF_Structure.Rebuild parameter 109, 113#06CLEAN, mainframe installation kit 26community names, specifying for HMC 64completeness

rules 181validation 102

component specifications 179components 101

CONCAT.JCLLIB.seq parameter 110CONCAT.SKELS.seq parameter 111configuring EMC GDDR 48configuring the EMC GDDR HMC interface 54consistency


CONT.system-name parameter 112contingency system, specifying 112Couple_DS.Realign parameter 113C-Systems 142

current master 59ensuring MSF connections 97renaming 150setting up a new system 148specifying security 35specifying the system name 114validating the environment 103

customizing GDDRPROC 40

DDASD, adding 157#02DDDEF, mainframe installation kit 26Deactivate command 66defining security environment 35device ranges, SRDF/A 133devices, adding to EMC GDDR 157devices, removing 159discover HMC objects 63

EECGCLEAN.Task.Number parameter 138ECGCLEAN.Task.Number statement 138Edit command 75EMC GDDR Administrator Primary Options menu 48EMC GDDR HMC interface, configuring 54EMC GDDR parameters, loading 48Event.Monitor.Interval statement 139existing C-System, renaming 150


Index

Ggatekeeper, defining 125GDDR 55, 63GDDR.Call_Override parameter 115GDDR.CONFIG parameter 116GDDR.VAR_BACKUP parameter 117GDDRPROC, customizing 40GDDRUX01 172GDDRUX02 172GDDRUX03 173GDDRUX04 173GDDRUX05 173GDDRUX06 174GDDRUX07 175GDDRUXDV 171GDDRUXGV 171GDDRUXSV 170GDDRvrm.XMITFILE 21GDDRvrm.XMITLIB 23global variable backup dataset, allocating 39global variables

backing up 71, 103GDDR.VARS parameter 117loading 103

GNS group, defining 118GNS.siteid.loc.jtype parameter 118

Hhardware requirements 18Heartbeat.Monitor.Interval parameter 140HFS files, allocating 31HMC 44, 63

initiating actions 65HMC API DLL, configuring 54HMC interface, configuring 54HMC object discovery 63HMC_Timeout.siteid parameter 141HMC.siteid parameter 119Host Component prefix 67HostComponent_CntlDsn parameter 121

IIKJTSOxx 32installation

mainframe environment requirements 17minimum processor and I/O configuration 18procedure 21software prerequisites 17

installing EMC GDDR started procedures 38IPL.system-name.siteid statement 122ISPF edit 75

JJA_ACT_GK.siteid statement 125JES2 36Job statement options 67

LLoad command 66, 75load device address 65loading EMC GDDR parameters 48, 74LPARs

activating and deactivating 66sited.LPAR.system-name parameter 126

Mmainframe environment requirements 17#99MAINT, mainframe installation kit 26Manage HMC option 62, 63, 69, 70, 79, 93, 94master C-System 59merging CA-OPS/MVS user applications 46messages, editing content 173minimum processor and I/O configuration 18minimum software prerequisites 17Missing.Heartbeat.Interval statement 142Missing.Heartbeat.Threshold parameter 143modifying user exits 56MSC_GROUPNAME.siteid parameter 127MSF connections 97MSFID.csystem-name parameter 128multiple EMC GDDR parameter members, configuring 56MVS device address 65

Nnon-LOGR couple datasets, considerations 161

Oonline facilities interface 58OPSMAIN, updating 44OPSOSF, updating 44OPSVIEW facilities 97

Ppage datasets, considerations 161parameter load processing 52parameter members for SRDF Host Component 34parameter statement processing 101

components 101references and specifications 101validation 102

parameter validation rules 177parameters

BCV.DC3.ONLY 107, 108BCV.siteid.MSC 106CF_Structure.Rebuild 109, 113CONCAT.JCLLIB.seq 110CONCAT.SKELS.seq 111CONT.system-name 112Couple_DS.Realign 113descriptions 104ECGCLEAN.Task.Number 138Event.Monitor.Interval 139GDDR.Call_Override 115GDDR.CONFIG 116GDDR.VAR_BACKUP 117


Index

GNS.siteid.loc.jtype 118Heartbeat.Monitor.Interval 140HMC_Timeout.siteid 141HMC.siteid 119HostComponet_CntlDsn 121IPL.system-name.siteid 122JA_ACT_GK.siteid 125loading 74, 103Missing.Heartbeat.Interval 142Missing.Heartbeat.Threshold 143MSC_GROUPNAME.siteid 127MSFID.csystem-name 128ResourcePak_STC_Name.c-system-name 130RESUME_GK.DC3 131SITE.system-name 132sited.LPAR.system-name 126siteid.C.System.Systemid 114sPLX.system-name.type.aorp.siteid 134SRDFA.Devices.siteid 133WTOR_Wait_Interval 144

Perform HMC Action panel 65Primary DASD setting 59Primary Options menu 48, 59Primary Site setting 59production system, adding 151

RRACF ALTER authority 20RACF functional groups 35RACF profiles and permissions 35RDF groups

adding 154defining 125removing 158

#03RECEV, mainframe installation kit 26reference 101removing devices 159removing RDF groups 158removing system or sysplex 160renaming C-Systems 150Reset Clear command 66ResourcePak_STC_Name.c-system-name parameter 130RESUME_GK.DC3 parameter 131RIMLIB JCL, customizing 23rules

completeness 181consistency 180syntax 178

SSCF suffix 67security environment, defining 35security, defining 35setting up a new system 148SITE.system-name parameter 132sited.LPAR.system-name statement 126siteid.C.System.Systemid parameter 114SMF.LOG parameter 144software prerequisites 17

specification 101Specify GDDR Parameter Dataset panel 74Specify HMC Community Names panel 64sPLX.system-name.type.aorp.siteid statement 134SRDF Host Component, parameter members 34SRDFA.Devices.siteid parameter 133Start command 66started procedures, installing 38starting production mainframe workloads 172starting production open-systems workloads 173Stop command 66stopping production mainframe workloads 172stopping production open-systems workloads 173syntax


SYS1.PARMLIB, updating 31sysplex

adding 151removing 160

system parameter file updates 31

UUnplanned scripts 61updating system parameter files 31user exit 7, customizing 43user exit programming considerations 170user exits, modifying 56

Vvalidating the environment 103validation 102

completeness 102consistency 102syntax 102

WWTOR_Wait_Interval parameter 144


Index


dell · emc gddr product guide 3 preface

Documents