Dell EMC GDDR · The name of the SCF started task. job-id The job ID. jobname The 8-character name of the JCL job. lpar-name The 4-character name of the logical partition (LPAR)

DELL EMC CONFIDENTIALDRAFT

Dell EMC GDDRVersion 5.2

Message Guide REV 13

GDDR 5.2 Message Guide

DELL EMC CONFIDENTIAL DRAFT

Copyright © 2001-2020 Dell Inc. or its subsidiaries. All Rights Reserved.

Published May 2020

Dell 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”. DELL 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 DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Published in the USA.

Dell EMCHopkinton, Massachusetts 01748-91031-508-1000 In North America 1-866-464-7381www.DellEMC.com

PREFACE
As part of an effort to improve its product lines, Dell EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information about product features.

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

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

AudienceThis document is part of the GDDR (Tape) documentation set, and is intended for use by GDDR (Tape) systems administrators and computer operators.

Message text formatGDDR messages are formatted as follows:

◆ If the default subsystem name of 'GDDR' is used:

message-id message-text

◆ if a custom subsystem name (not 'GDDR') is used:

message-id subsystem-name message-text

Where:

◆ message-id is the message ID.

◆ subsystem-name is the GDDR subsystem name for the originating GDDR instance.

◆ message-text is the text documented in this GDDR Message Guide.

What are GDDB messagesGDDB messages are WTORs signaling that a GDDR script is waiting for an action to complete. When GDDR observes completion of the action, it automatically reply to the WTOR. No operator action is required.

Related documentationThe following documents provide information about GDDR and GDDR Tape:

◆ GDDR (Tape) Product Guide for your configuration

◆ GDDR (Tape) Release Notes

GDDR 5.2 Message Guide I

Preface


The following documents provide information about Mainframe Enablers:

◆ Mainframe Enablers Release Notes

◆ Mainframe Enablers Installation and Customization Guide

◆ Mainframe Enablers Message Guide

◆ ResourcePak Base for z/OS Product Guide

◆ SRDF Host Component for z/OS Product Guide

◆ AutoSwap for z/OS Product Guide

◆ Consistency Groups for z/OS Product Guide

◆ TimeFinder SnapVX and zDP Product Guide

◆ TimeFinder/Clone Mainframe Snap Facility Product Guide

◆ TimeFinder/Mirror for z/OS Product Guide

◆ TimeFinder Utility for z/OS Product Guide

The following document provides information about DLm:

◆ Dell EMC Disk Library for mainframe (DLm)

Conventions used in this document Dell EMC uses the following type style conventions in this document:

Common variablesMessage texts may contain the following variables:

ccuu

The z/OS device number.

Italic Used for: Titles of publications referenced in text Emphasis, for example, a new term

Courier Used for: Command syntax and parameters System output, such as messages

Courier bold Used for user input, for example: Reply CONT.

Courier italic Used for variables in command/parameter syntax and messages, for example: DISPLAY ccuu

Courier underline Underline indicates the default value, for example: YES|NO

< > Angle brackets enclose variables or explanatory text when it includes multiple words, for example: <list of device numbers>

[ ] Square brackets enclose optional values, for example: DISPLAY [DETAIL]

| Vertical bar indicates alternate selections (the bar means “or”), for example: RUN|NORUN

{ } Braces are used together with the vertical bar (|) to indicate the start and end of alternate selections, for example: {DEV symdv#|CUU ccuu}

... Ellipses indicate nonessential information omitted from the example

II GDDR 5.2 Message Guide

Preface


cngrp

The name of the consistency group (8 characters).

cpc-name

The name of the Central Processing Complex (CPC).

c-system-name

The name of the GDDR control system (C-system).

ddname

The DD statement in the JCL.

dir#

The SRDF link director number, a hexadecimal value x’01’ through x’80’.

dsname

The dataset name.

gk

The z/OS device number (CUU) of the gatekeeper device.

emcscf

The name of the SCF started task.

job-id

The job ID.

jobname

The 8-character name of the JCL job.

lpar-name

The 4-character name of the logical partition (LPAR).

message-id

The message ID.

message-text

Variable message text.

mscgrp

The MSC group name (defined using the MSC_GROUP_NAME initialization parameter in SRDF Host Component).

object-id

The object ID.

p-system-name

The name of the GDDR production system (P-system).

reason

The reason description.

GDDR 5.2 Message Guide III

Preface


rc

The return code.

rs

The reason code.

script-name

The name of the GDDR script.

site-id

The ID of a GDDR site.

srdfgrp

The SRDF group number (a hexadecimal value in the range x'00' through x'F9').

swapgrp

The name of the swap group.

symdv#

The PowerMax/VMAX device number (6-digit for ResourcePak Base, SRDF Host Component, Consistency Groups, AutoSwap, zDP; 8-digit for TimeFinder).

symm-serial

The 12-digit Dell EMC storage system serial number separated with a hyphen (ccccccc-ccccc).

symmserial

The 12-digit Dell EMC storage system serial number listed without a hyphen (cccccccccccc).

system-name

The system name.

variable_name

The name of the variable.

vdg_name

The name of the zDP Versioned Data Group.

userid

The user ID.

ucbaddr

The UCB address of the device (8 digits).

IV GDDR 5.2 Message Guide

Preface


Where to get help

Product information

For information about Dell EMC products, licensing, and service, go to www.dellemc.com (registration required).

Technical support

To access the Dell EMC Online Support web site, go to www.dell.com/support and search for your product. You will be redirected to the product support page, offering quick links to Documentation, Downloads, Advisories, and Knowledgebase for your product. The product support page also provides a link to the Service Center where you can create a service request, manage your service requests, and contact Dell EMC Customer Support either through Dell EMC Live Chat or using other options.

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

eLicensing support

To activate your entitlements and obtain your license files, visit the Service Center as directed on your License Authorization Code (LAC) letter emailed to you.

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

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

If you are missing a LAC letter, or require further instructions on activating your licenses through the Online Support site, contact Dell EMC worldwide licensing team at [email protected] or call:

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

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

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

[email protected]

GDDR 5.2 Message Guide V

Preface


VI GDDR 5.2 Message Guide

CONTENTS

Chapter 1 Automated GDDR WTORs (GDDB) 59

GDDB011I 59

GDDB012I 59

GDDB013I 59

GDDB014I 59

GDDB015I 60

GDDB016I 60

GDDB017I 60

GDDB018I 60

GDDB020I 60

GDDB021I 61

GDDB022I 61

GDDB023I 61

GDDB024I 61

GDDB025I 61

GDDB026I 61

GDDB027I 62

GDDB028I 62

GDDB029I 62

GDDB030I 62

GDDB040I 62

GDDB041I 63

GDDB042I 63

GDDB043I 63

GDDB044I 64

GDDB045I 64

GDDB046I 64

GDDB047I 64

3GDDR 5.2 Message Guide

GDDB048I 64

GDDB049I 65

GDDB050I 65

GDDB051I 65

GDDB052I 66

GDDB060I 66

GDDB061I 66

GDDB062I 66

GDDB063I 67

GDDB102I 67

GDDB106I 67

GDDB107I 68

GDDB109I 68

GDDB112I 68

GDDB113I 68

GDDB124I 69

GDDB126I 69

GDDB128I | GDDB128W 69

GDDB200I 69

GDDB862I 70

Chapter 2 HMC-Related Messages (GDDH) 71

GDDH001I 71

GDDH002I 71

GDDH004E 71

GDDH005I 71

GDDH006I 71

GDDH007E 71

GDDH008I 72

GDDH009E 72

GDDH010I 72

GDDH011E 72

GDDH012E 72

GDDH013E 73

GDDH014E 73


GDDH015E 73

GDDH016E 73

GDDH017E 73

GDDH018E 73

GDDH019E 74

GDDH020I 74

GDDH021I 74

GDDH022E 74

GDDH023E 74

GDDH024E 75

GDDH030I 75

GDDH032E 75

GDDH033E 76

GDDH034E 76

GDDH035E 76

GDDH036E 76

GDDH037E 77

GDDH038E 77

GDDH039E 77

GDDH040E 78

GDDH041E 78

GDDH042E 78

GDDH043E 78

GDDH044E 79

GDDH045E 79

GDDH046E 79

GDDH047E 79

GDDH048E 80

GDDH049E 80

GDDH050E 80

GDDH051E 80

GDDH052E 80

GDDH053E 81

GDDH054E 81


GDDH055E 81

GDDH056E 81

GDDH057I 82

GDDH058E 82

GDDH059E 82

GDDH060E 82

GDDH061I 83

GDDH062I 83

GDDH063I 83

GDDH064I 83

GDDH065I 83

GDDH066I 84

GDDH067I 84

GDDH068I 84

GDDH069I 84

GDDH070I 84

GDDH071I 84

GDDH072I 85

GDDH073I 85

GDDH074E 85

GDDH075E 85

GDDH076E 85

GDDH077E 86

GDDH078E 86

GDDH079E 86

GDDH080E 86

GDDH081E 86

GDDH082E 87

GDDH083E 87

GDDH084E 87

GDDH085E 87

GDDH086W 88

GDDH087E 88

GDDH088E 88


GDDH089E 88

GDDH090E 88

GDDH091E 89

GDDH092W 89

GDDH093E 89

GDDH094E 89

GDDH095E 89

GDDH096E 90

GDDH097W 90

GDDH098E 90

GDDH099E 90

GDDH100E 90

GDDH100I 91

GDDH101E 91

GDDH101I 91

GDDH102E 91

GDDH103E 91

GDDH103I 92

GDDH104E 92

GDDH104I 92

GDDH105I 92

GDDH105W 93

GDDH106E 93

GDDH106I 93

GDDH107E 93

GDDH107I 93

GDDH108E 94

GDDH108W 94

GDDH109E 94

GDDH109W 94

GDDH110E 95

GDDH110W 95

GDDH111E 95

GDDH111I 95


GDDH112E 96

GDDH113E 96

GDDH200I 96

GDDH998E 96

GDDHMC1I 97

Chapter 3 ISPF Interface Messages (GDDI) 98

GDDI002E 98

GDDI003E 98

GDDI004E 98

GDDI005E 98

GDDI006E 98

GDDI009E 99

GDDI010E 99

GDDI010I 99

GDDI011E 99

GDDI011I 100

GDDI015I 100

GDDI018W 100

GDDI019I 100

GDDI020E 100

GDDI021E 101

GDDI022E 101

GDDI024E 101

GDDI025I 101

GDDI026E 101

GDDI027E 102

GDDI028I 102

GDDI029E 102

GDDI030E 102

GDDI035I 102

GDDI036E 103

GDDI037I 103

GDDI039I 103

GDDI041E 103


GDDI042E 104

GDDI043I 104

GDDI045I 104

GDDI046E 104

GDDI048E 104

GDDI057I 104

GDDI058E 105

GDDI059I 105

GDDI060E 105

GDDI061E 105

GDDI065E 105

GDDI066E 106

GDDI067I 106

GDDI070E 106

GDDI070W 106

GDDI073I 107

GDDI074I 107

GDDI075E 107

GDDI077I 107

GDDI078I 107

GDDI086E 108

GDDI087E 108

GDDI088E 108

GDDI089E 108

GDDI091I 109

GDDI092I 109

GDDI094E 109

GDDI095E 109

GDDI098I 110

GDDI100I 110

GDDI101I 110

GDDI102E 110

GDDI105E 110

GDDI106E 111


GDDI107I 111

GDDI109E 111

GDDI110I 111

GDDI111I 111

GDDI113I 112

GDDI114I 112

GDDI115E 112

GDDI116I 112

GDDI117E 112

GDDI118I 113

GDDI121I 113

GDDI124E 113

GDDI126E 113

GDDI128I 113

GDDI129I 114

GDDI135E 114

GDDI136E 114

GDDI139E 114

GDDI145I 115

GDDI146I 115

GDDI147I 115

GDDI150I 115

GDDI151E 115

GDDI153E 116

GDDI154E 116

GDDI157E 116

GDDI158E 116

GDDI159E 116

GDDI160E 116

GDDI161E 117

GDDI162E 117

GDDI163I 117

GDDI164E 117

GDDI165E 117


GDDI166I 118

GDDI167E 118

GDDI168E 118

GDDI169E 118

GDDI170E 119

GDDI171E 119

GDDI172I 119

GDDI173E 119

GDDI174E 119

GDDI175E 120

GDDI176E 120

GDDI177E 120

GDDI179E 120

GDDI180I 120

GDDI181E 121

GDDI181W 121

GDDI182E 121

GDDI201E 122

GDDI202E 122

GDDI203I 122

GDDI205I 122

GDDI205W 122

GDDI206E 123

GDDI206I 123

GDDI220E 123

GDDI221E 124

GDDI222E 124

GDDI361E 124

GDDI365W 124

GDDI366W 124

GDDI367W 125

GDDI370W 125

GDDI371W 125

GDDI372W 125


GDDI373E 125

GDDI374E 126

GDDI375W 126

GDDI376E 126

GDDI377W 126

GDDI378E 127

GDDI379E 127

GDDI380E 127

GDDI381E 127

GDDI382E 127

GDDI383E 127

GDDI384E 128

GDDI387E 128

GDDI387I 128

GDDI388E 129

GDDI389E 129

GDDI390E 129

GDDI391E 129

GDDI392I 130

GDDI393E 130

GDDI394E 130

GDDI901I 130

GDDI902I 130

GDDI996E 130

GDDI997E 131

GDDI998E 131

GDDI999E 131

GDDI999I 132

Chapter 4 GDDRMAIN Messages (GDDM) 133

GDDM000I 133

GDDM001E 133

GDDM002I 133

GDDM003W 133

GDDM004W 133


GDDM005W 134

GDDM006E 134

GDDM007I 134

GDDM008W 134

GDDM009E 134

GDDM010I 135

GDDM011I 135

GDDM012I 135

GDDM013E 135

GDDM014W 136

GDDM015E 136

GDDM016I 136

GDDM017I 136

GDDM018I 137

GDDM019W 137

GDDM020I 137

GDDM021W 137

GDDM022W 137

GDDM023I 137

GDDM024E 138

GDDM025I 138

GDDM026I 138

GDDM027I 138

GDDM028E 138

GDDM029W 139

GDDM030W 139

GDDM031E 139

GDDM032I 140

GDDM033W 140

GDDM034E 140

GDDM035E 140

GDDM036E 141

GDDM037E 141

GDDM038E 141


GDDM039I 141

GDDM040E 141

GDDM042W 142

GDDM043E 142

GDDM044E 142

GDDM045W 142

GDDM046W 142

GDDM047W 143

GDDM049I 143

GDDM04IE 143

GDDM052E 143

GDDM053I 143

GDDM054A 144

GDDM055I 144

GDDM056A 144

GDDM057I 144

GDDM058W 144

GDDM059E 145

GDDM060E 145

GDDM061I 145

GDDM062I 145

GDDM063E 145

GDDM064E 146

GDDM065E 146

GDDM066I 146

GDDM067E 146

GDDM068I 147

GDDM069E 147

GDDM071I 147

GDDM072I 147

GDDM073I 147

GDDM074I 148

GDDM075E 148

GDDM076E 148


GDDM077E 149

GDDM080E | GDDM080W 149

GDDM081I 149

GDDM082I 149

GDDM083I 149

GDDM084I 150

GDDM088I 150

GDDM089I 150

GDDM090E 150

GDDM091E 150

GDDM092E 151

GDDM093E 151

GDDM094E 151

GDDM095E 151

GDDM100E 151

GDDM101E 152

GDDM102E 152

GDDM103W 152

GDDM104E 152

GDDM105E 152

GDDM106E 152

GDDM107E 153

GDDM108E 153

GDDM109E 153

GDDM110E 153

GDDM111E 154

GDDM112E 154

GDDM113E 154

GDDM114E 154

GDDM115E 154

GDDM116E 155

GDDM117E 155

GDDM118E 155

GDDM119E 155


GDDM120E 155

GDDM121E 156

GDDM122E 156

GDDM123A 156

GDDM124I 156

GDDM125W 157

GDDM126E 157

GDDM127I 157

GDDM128I 157

GDDM129E 158

GDDM130I 158

GDDM131E 158

GDDM132W 158

GDDM133E 159

GDDM134E 159

GDDM135E 159

GDDM136E 159

GDDM137E 159

GDDM138E 160

GDDM139E 160

GDDM140I 160

GDDM141E 160

GDDM142I 161

GDDM143W 161

GDDM144W 161

GDDM145I 161

GDDM146E 162

GDDM147E 162

GDDM148E 162

GDDM149I 162

GDDM150E 163

GDDM151E 163

GDDM152E 163

GDDM153I 163


GDDM154A 163

GDDM155I 164

GDDM156E 164

GDDM157W 165

GDDM158I 165

GDDM159I 165

GDDM160I 165

GDDM161W 166

GDDM162E 166

GDDM163E 166

GDDM164E 166

GDDM165E 166

GDDM166E 167

GDDM167E 167

GDDM168E 167

GDDM169E 167

GDDM170W 167

GDDM171W 168

GDDM172W 168

GDDM175E 168

GDDM176E 168

GDDM177E 169

GDDM178E 169

GDDM179W 169

GDDM180I 169

GDDM181E 169

GDDM182W 170

GDDM183W 170

GDDM185E 170

GDDM187W 171

GDDM188E 171

GDDM189E 171

GDDM190E 171

GDDM191E 172


GDDM192I 172

GDDM193E 172

GDDM194E 172

GDDM195E 172

GDDM196E 173

GDDM197E 173

GDDM198E 173

GDDM199E 173

GDDM200W 174

GDDM201I 174

GDDM202W 174

GDDM203E 174

GDDM204W 174

GDDM205I 175

GDDM206A 175

GDDM207E 176

GDDM208W 176

GDDM209W 176

GDDM210E 176

GDDM211W 176

GDDM212W 177

GDDM213I 177

GDDM214I 177

GDDM217E 178

GDDM218I 178

GDDM220I 178

GDDM221I 178

GDDM222E 178

GDDM223I 179

GDDM228I 179

GDDM229I 179

GDDM230I 179

GDDM231I 179

GDDM232W 180


GDDM240E 180

GDDM241E 180

GDDM242E 180

GDDM243E 180

GDDM245E 181

GDDM246E 181

GDDM247I 181

GDDM248I 181

GDDM250W 181

GDDM251I 182

GDDM252A 182

GDDM253I 182

GDDM254E 183

GDDM255A 183

GDDM256E 184

GDDM257I 184

GDDM258E 184

GDDM259E 184

GDDM260E 184

GDDM261E 184

GDDM262E 185

GDDM263E 185

GDDM264E 185

GDDM265E 185

GDDM266I 186

GDDM267I 186

GDDM268E 186

GDDM269E 186

GDDM270E 186

GDDM271W 187

GDDM272I 187

GDDM273W 187

GDDM274I 188

GDDM275I 188


GDDM276E 188

GDDM277E 188

GDDM278I 188

GDDM279E 189

GDDM280I 189

GDDM281W 190

GDDM282E 190

GDDM283I 190

GDDM284I 190

GDDM285E 190

GDDM286I 191

GDDM287E 191

GDDM288W 191

GDDM289E 192

GDDM290E 192

GDDM291E 192

GDDM292E 192

GDDM293E 193

GDDM294I 193

GDDM295E 193

GDDM296E 193

GDDM297E 194

GDDM298I 194

GDDM299E 194

GDDM300I 194

GDDM301I 195

GDDM302E 195

GDDM302W 195

GDDM303I 196

GDDM310I 196

GDDM315W 197

GDDM400E 197

GDDM410E 197

GDDM411E 197


GDDM420E 198

GDDM421E 198

GDDM422W 198

GDDM430I 198

GDDM500I 199

GDDM502W 199

GDDM503E 200

GDDM504I 200

GDDM505I 200

GDDM506I 200

GDDM600E 200

GDDM600I 201

GDDM601I 201

GDDM602E 201

GDDM603E 201

GDDM604I 201

GDDM605I 201

GDDM606I 202

GDDM607I 202

GDDM608E 202

GDDM610I 202

GDDM611E 202

GDDM612E 203

GDDM613E 203

GDDM614E 203

GDDM620I 204

GDDM621I 204

GDDM622I 204

GDDM630E 204

GDDM640E 204

GDDM641E 205

GDDM642E 205

GDDM643E 205

GDDM644E 205


GDDM645E 205

GDDM646E 206

GDDM647E 206

GDDM648E 206

GDDM649E 206

GDDM650E 207

GDDM651E 207

GDDM652E 207

GDDM653E 207

GDDM699I 208

GDDM700A 208

GDDM701I 208

GDDM702I 208

GDDM703I 208

GDDM705E 209

GDDM992E 209

GDDM993E 209

GDDM998E 209

Chapter 5 WTORs Requiring Operator Action (GDDO) 210

GDDO001I 210

GDDO002A 210

GDDO003I 210

GDDO004A 210

GDDO005I 211

GDDO006A 211

GDDO007I 212

GDDO008A 212

GDDO009I 213

GDDO010A 213

GDDO011I 213

GDDO012A 214

GDDO013I 214

GDDO014A 214

GDDO015I 215


GDDO016A 215

GDDO017I 215

GDDO018A 216

GDDO019I 216

GDDO020A 216

GDDO021I 216

GDDO022A 217

GDDO023I 217

GDDO024A 217

GDDO025I 218

GDDO026A 218

GDDO027I 218

GDDO028A 219

GDDO029I 219

GDDO030A 219

GDDO031I 219

GDDO032A 220

GDDO033I 220

GDDO034A 220

GDDO035I 221

GDDO036A 221

GDDO037I 221

GDDO038A 221

GDDO039I 222

GDDO040A 222

GDDO041I 222

GDDO042A 223

GDDO043I 223

GDDO044A 223

GDDO045I 223

GDDO046A 224

GDDO047I 224

GDDO048A 224

GDDO049I 224


GDDO050A 225

GDDO051I 225

GDDO052A 225

GDDO053I 225

GDDO054A 226

GDDO055I 226

GDDO056A 226

GDDO057I 227

GDDO058A 227

GDDO059I 227

GDDO061I 228

GDDO062A 228

GDDO063I 228

GDDO064A 229

GDDO065I 229

GDDO066A 229

GDDO067I 229

GDDO068A 230

GDDO069I 230

GDDO070A 230

GDDO071I 230

GDDO072A 231

GDDO073I 231

GDDO074A 231

GDDO075I 231

GDDO076A 232

GDDO077I 232

GDDO078A 232

GDDO079I 233

GDDO080A 233

GDDO081I 233

GDDO082A 234

GDDO083I 234

GDDO084A 234


GDDO085I 234

GDDO086A 235

GDDO087I 235

GDDO088A 235

GDDO089I 236

GDDO090A 236

GDDO091I 236

GDDO092A 236

GDDO093I 236

GDDO094A 237

GDDO095I 237

GDDO096A 237

GDDO097I 237

GDDO098A 238

GDDO099I 238

GDDO100A 238

GDDO101I 238

GDDO102A 239

GDDO103I 239

GDDO104A 239

GDDO105I 239

GDDO106A 240

GDDO107I 240

GDDO108A 240

GDDO109I 240

GDDO110A 241

GDDO111I 241

GDDO112A 241

GDDO113I 241

GDDO114A 242

GDDO115I 242

GDDO116A 242

GDDO117I 242

GDDO118A 243


GDDO119I 243

GDDO120A 243

GDDO121I 244

GDDO122A 244

GDDO123I 244

GDDO124A 245

GDDO125I 245

GDDO126A 245

GDDO127I 245

GDDO128A 246

GDDO129I 246

GDDO130A 246

GDDO131I 246

GDDO132A 246

GDDO133I 247

GDDO134A 247

GDDO135A 247

GDDO137I 248

GDDO138A 248

GDDO140I 248

GDDO141A 248

GDDO143I 249

GDDO144A 249

GDDO145I 249

GDDO147I 249

GDDO148A 250

GDDO150I 250

GDDO151A 250

GDDO152I 251

GDDO153A 251

GDDO154I 251

GDDO155A 252

GDDO156I 252

GDDO157A 252


GDDO160I 252

GDDO161A 253

GDDO166I 253

GDDO167A 253

GDDO168I 253

GDDO169A 254

GDDO170I 254

GDDO171A 254

GDDO172I 255

GDDO173A 255

GDDO174I 255

GDDO175A 256

GDDO180I 256

GDDO181A 256

Chapter 6 GDDR Parameter Messages (GDDP) 258

GDDP001I 258

GDDP004E 258

GDDP034I 258

GDDP038E 258

GDDP107I 259

GDDP108I 259

GDDP110I 259

GDDP150E 259

GDDP151E 260

GDDP152E 260

GDDP153E 260

GDDP154E 260

GDDP187I 261

GDDP300E 261

GDDP301W 261

GDDP302I 261

GDDP303W 261

GDDP304I 261

GDDP305E 262


GDDP306W 262

GDDP307E 262

GDDP308I 262

GDDP309I 262

GDDP310I 262

GDDP311I 263

GDDP312I 263

GDDP313I 263

GDDP314I 263

GDDP315I 263

GDDP316I 263

GDDP317E 264

GDDP318E 264

GDDP319I 264

GDDP320I 264

GDDP321I 265

GDDP322E 265

GDDP323W 265

GDDP324I 265

GDDP325E 265

GDDP326E 266

GDDP327W 266

GDDP328I 266

GDDP329E 266

GDDP330E 266

GDDP331W 267

GDDP332E 267

GDDP333W 267

GDDP334I 267

GDDP335I 267

GDDP336I 268

GDDP337I 268

GDDP338W 268

GDDP339I 268


GDDP340E 268

GDDP341E 268

GDDP342E 269

GDDP343E | GDDP343W 269

GDDP348E 269

GDDP349I 269

GDDP350W 269

GDDP351E 270

GDDP352I 270

GDDP353E 270

GDDP354E 270

GDDP355E 271

GDDP399E 271

GDDP400E 271

GDDP401I 277

GDDP402I 277

GDDP403E 278

GDDP404I 278

GDDP405E 278

GDDP406E 278

GDDP407E 279

GDDP408E 279

GDDP410I 279

GDDP411I 279

GDDP412I 279

GDDP415I 283

GDDP415W 283

GDDP416I 284

GDDP417I 284

GDDP418I 284

GDDP419I 285

GDDP420E 285

GDDP421W 289

GDDP422I 290


GDDP430I 290

GDDP431I 290

GDDP432I 291

GDDP435I 291

GDDP436I 292

GDDP437I 292

GDDP438I 292

GDDP440I 293

GDDP441I 293

GDDP442E 294

GDDP443E 294

GDDP444I 295

GDDP445I 295

GDDP446I 295

GDDP447E 295

GDDP447I 296

GDDP448E 298

GDDP449W 299

GDDP450I 299

GDDP451I 299

GDDP452I 300

GDDP453E 300

GDDP460I 300

GDDP461I 301

GDDP462I 301

GDDP470I 303

GDDP471E 303

GDDP472I 303

GDDP473I 304

GDDP474I 304

GDDP475I 304

GDDP476I 304

GDDP477I 306

GDDP478I 306


GDDP479I 306

GDDP480I 306

GDDP481I 306

GDDP482I 307

GDDP483I 307

GDDP484I 307

GDDP485I 307

GDDP486E 308

GDDP487I 308

GDDP488I 308

GDDP489I 308

GDDP490I 309

GDDP491I 309

GDDP492I 309

GDDP998E 309

Chapter 7 GDDR Command Queue Messages (GDDQ) 310

GDDQ003E 310

GDDQ220E 310

GDDQ221E 310

GDDQ222I 310

GDDQ223E 311

GDDQ224E 311

GDDQ225E 311

GDDQ226W 311

GDDQ227I 311

GDDQ228I 312

Chapter 8 General GDDR Messages (GDDR) 313

GDDR000I 313

GDDR001E 313

GDDR002E 313

GDDR003E 313

GDDR004E 314

GDDR005E 314

GDDR006E 314


GDDR007I 314

GDDR008I 315

GDDR009I 315

GDDR011I 315

GDDR013E 315

GDDR014I 316

GDDR015E 316

GDDR015I 316

GDDR016I 316

GDDR018W 317

GDDR019E 317

GDDR023E 317

GDDR031E 317

GDDR034A 317

GDDR034E 318

GDDR041E | GDDR041I 318

GDDR042E 318

GDDR043E 318

GDDR049E 319

GDDR050E 319

GDDR051I 319

GDDR052I 319

GDDR053I 320

GDDR054I 320

GDDR055I 320

GDDR056I 320

GDDR057I 320

GDDR058I 321

GDDR071E 321

GDDR072E 321

GDDR073E 321

GDDR074E 322

GDDR090E 322

GDDR101E 322


GDDR104I 322

GDDR106W 323

GDDR107W 323

GDDR109W 323

GDDR115I 323

GDDR116I 324

GDDR117I 324

GDDR119E 324

GDDR120E 324

GDDR121I 324

GDDR122E 324

GDDR123A 325

GDDR123W 325

GDDR124A 325

GDDR124E 326

GDDR124I 326

GDDR125W 326

GDDR126I 326

GDDR127A 327

GDDR127E 327

GDDR128I 327

GDDR129I 327

GDDR130I 328

GDDR131E 328

GDDR132I 328

GDDR133E 328

GDDR133W 328

GDDR134I 329

GDDR135E 329

GDDR135I 329

GDDR136E 329

GDDR157E 329

GDDR158E 330

GDDR160E 330


GDDR161E 331

GDDR162E 331

GDDR163I 331

GDDR164E 331

GDDR165I 332

GDDR166E 332

GDDR195I 332

GDDR196W 332

GDDR199I 332

GDDR200E 333

GDDR202E 333

GDDR210E 333

GDDR211E 333

GDDR250E 334

GDDR251E 334

GDDR252E 334

GDDR253E 334

GDDR254E 334

GDDR270E 335

GDDR271E 335

GDDR272E 335

GDDR280E 335

GDDR281E | GDDR281W 335

GDDR300I 336

GDDR301I 336

GDDR309E 336

GDDR311I 336

GDDR312I 337

GDDR313I 337

GDDR315I 337

GDDR316I 337

GDDR317E 337

GDDR318I 338

GDDR319I 338


GDDR322E 338

GDDR323I 339

GDDR325I 339

GDDR326I 339

GDDR327I 339

GDDR328I 339

GDDR329I 340

GDDR330E 340

GDDR331I 340

GDDR332I 341

GDDR333I 341

GDDR334W 341

GDDR335W 341

GDDR336I 342

GDDR337E 342

GDDR344E 342

GDDR348E 343

GDDR349I 343

GDDR350E 343

GDDR351E 343

GDDR352E 343

GDDR353I 344

GDDR354E 344

GDDR355E 344

GDDR356E 344

GDDR357I 345

GDDR358I 345

GDDR359I 345

GDDR360E 345

GDDR361E 346

GDDR363I 346

GDDR364I 346

GDDR365E 346

GDDR367E 346


GDDR368I 347

GDDR369I 347

GDDR370A 347

GDDR370I 347

GDDR370W 348

GDDR371E 348

GDDR372W 348

GDDR373I 348

GDDR374I 348

GDDR375I 349

GDDR376I 349

GDDR377I 349

GDDR378I 349

GDDR380I 349

GDDR381I 350

GDDR382I 350

GDDR383I 350

GDDR386A 350

GDDR386E 350

GDDR387W 350

GDDR388E 351

GDDR389E 351

GDDR390E 351

GDDR391I 351

GDDR392E 352

GDDR393E 352

GDDR394E 352

GDDR395E 352

GDDR396E 353

GDDR397E 353

GDDR398E 353

GDDR400E 353

GDDR401E 354

GDDR402I 354


GDDR411E 354

GDDR412E 354

GDDR413E 354

GDDR414E 355

GDDR451I 355

GDDR452E 355

GDDR453I 355

GDDR454E 356

GDDR455E 356

GDDR510E 356

GDDR522I 356

GDDR530E 356

GDDR531E 357

GDDR532I 357

GDDR533I 357

GDDR534E 357

GDDR535E 357

GDDR536E 358

GDDR537E 358

GDDR538E 359

GDDR539E 359

GDDR540I 359

GDDR541I 359

GDDR542E 359

GDDR543E 360

GDDR544E 360

GDDR545E 360

GDDR546E 361

GDDR547E 361

GDDR548E 361

GDDR588E 361

GDDR592I 362

GDDR608W 362

GDDR610E 362


GDDR610I 362

GDDR611I 362

GDDR612I 363

GDDR614I 363

GDDR615E 363

GDDR615I 363

GDDR616E 363

GDDR617A 364

GDDR617E 364

GDDR618E 364

GDDR619E 364

GDDR620E 365

GDDR621E 365

GDDR622I 365

GDDR625I 365

GDDR626I 366

GDDR627I 366

GDDR628E 366

GDDR629I 366

GDDR630I 366

GDDR632I 367

GDDR636I 367

GDDR637I 367

GDDR638E 367

GDDR639I 368

GDDR641I 368

GDDR642I 368

GDDR643I 368

GDDR644I 368

GDDR645I 369

GDDR646I 369

GDDR647I 369

GDDR648I 369

GDDR649E 370


GDDR650W 370

GDDR652E 370

GDDR653W 370

GDDR654I 371

GDDR655E 371

GDDR656I 371

GDDR657I 371

GDDR658E 372

GDDR659I 372

GDDR661I 372

GDDR662I 372

GDDR663E 373

GDDR664I 373

GDDR665I 373

GDDR667I 373

GDDR668I 373

GDDR669I 374

GDDR670I 374

GDDR671I 374

GDDR672I 374

GDDR673I 374

GDDR674I 374

GDDR675E 375

GDDR677I 375

GDDR678I 375

GDDR679E 375

GDDR680E 375

GDDR684I 376

GDDR685I 376

GDDR687I 376

GDDR688I 376

GDDR689I 377

GDDR690I 377

GDDR691I 377


GDDR692I 377

GDDR693I 377

GDDR694I 378

GDDR695I 378

GDDR696E 378

GDDR696I 378

GDDR697I 378

GDDR697W 379

GDDR698I 379

GDDR700E 379

GDDR700W 379

GDDR701E 379

GDDR702E 380

GDDR703I 380

GDDR704I 380

GDDR705I 380

GDDR706I 381

GDDR707I 381

GDDR709E 381

GDDR709I 381

GDDR710I 381

GDDR711I 382

GDDR712I 382

GDDR713I 382

GDDR715I 382

GDDR717I 382

GDDR718I 383

GDDR719I 383

GDDR721I 383

GDDR722I 383

GDDR724I 384

GDDR725I 384

GDDR727I 384

GDDR727W 384


GDDR728E 384

GDDR729I 385

GDDR730I 385

GDDR731I 385

GDDR732E 385

GDDR734I 385

GDDR735I 386

GDDR736I 386

GDDR737I 386

GDDR738I 386

GDDR739I 386

GDDR740I 387

GDDR741I 387

GDDR742I 387

GDDR743I 387

GDDR749I 387

GDDR750I 388

GDDR751I 388

GDDR752I 388

GDDR753I 388

GDDR754E 389

GDDR754I 389

GDDR755E 389

GDDR756E 389

GDDR757W 389

GDDR759W 390

GDDR768W 390

GDDR769W 391

GDDR770W 391

GDDR771W 391

GDDR772I 391

GDDR773W 391

GDDR774W 392

GDDR775W 392


GDDR776E 392

GDDR776I 392

GDDR777W 393

GDDR778W 393

GDDR779I 393

GDDR786E 393

GDDR793W 394

GDDR800E 394

GDDR801E 394

GDDR802E 395

GDDR803I 395

GDDR804E 395

GDDR805E 395

GDDR809I 395

GDDR815I 396

GDDR816I 396

GDDR817I 396

GDDR818I 396

GDDR822I 399

GDDR823I 399

GDDR831I 399

GDDR832W 400

GDDR833W 400

GDDR837E 400

GDDR838I 400

GDDR839I 400

GDDR840E 400

GDDR841E 401

GDDR842I 401

GDDR843I 401

GDDR844E 401

GDDR845E 401

GDDR846E 402

GDDR847E 402


GDDR848E 402

GDDR849E 402

GDDR850I 402

GDDR852I 402

GDDR853I 403

GDDR854I 403

GDDR855I 403

GDDR856E 403

GDDR857E 404

GDDR858I 404

GDDR859I 404

GDDR860E 404

GDDR861A 404

GDDR862I 405

GDDR863W 405

GDDR864E 405

GDDR865A 406

GDDR866A 406

GDDR866E 406

GDDR869I 406

GDDR870A 407

GDDR871I 407

GDDR874I 407

GDDR875A 408

GDDR876E 408

GDDR877W 408

GDDR878I 408

GDDR880E 409

GDDR881E 409

GDDR882E 409

GDDR883E 410

GDDR884E 410

GDDR885E 410

GDDR886E 411


GDDR887I 411

GDDR888I 411

GDDR889I 411

GDDR890E 411

GDDR891E 412

GDDR892E 412

GDDR893E 412

GDDR894E 412

GDDR895E 412

GDDR896E 413

GDDR901E 413

GDDR902I 413

GDDR903E 413

GDDR904I 414

GDDR906E 414

GDDR907I 414

GDDR908I 414

GDDR909W 414

GDDR913I 415

GDDR914I 415

GDDR915I 415

GDDR916E | GDDR916I 415

GDDR917E 416

GDDR918W 416

GDDR919E 417

GDDR920E 417

GDDR921E 417

GDDR922E 417

GDDR924W 417

GDDR925I 418

GDDR926E 418

GDDR927E 422

GDDR928E 422

GDDR929I 422


GDDR930E 422

GDDR931I 422

GDDR932I 422

GDDR933E 423

GDDR934E 423

GDDR935I 423

GDDR936I 423

GDDR937E 424

GDDR941E 424

GDDR942E 424

GDDR943W 425

GDDR944W 425

GDDR945W 425

GDDR961I 425

GDDR962E 426

GDDR963W 426

GDDR964I 426

GDDR965E 426

GDDR966I 427

GDDR967E 427

GDDR968E 427

GDDR969E 427

GDDR970E 428

GDDR971W 428

GDDR972W 428

GDDR973W 428

GDDR974I 429

GDDR975W 429

GDDR976E 429

GDDR977I 430

GDDR978W 430

GDDR979I 430

GDDR980W 430

GDDR981W 430


GDDR982I 431

GDDR983E 431

GDDR991E 431

GDDR992E 431

GDDR993I 435

GDDR994E 435

GDDR995I 435

GDDR996E 435

GDDR997E 436

GDDR998E 436

GDDR998F 436

GDDR998G 437

GDDR999A 437

GDDR999I 437

GDDRUXM3 437

GDDRUXM4 437

Chapter 9 GDDR EVM and HBM Messages (GDDS) 439

GDDS001I 439

GDDS002I 439

GDDS003I 439

GDDS004I 439

GDDS005I 439

GDDS006W 440

GDDS007E 440

GDDS008I 440

GDDS009I 441

GDDS010I 441

GDDS011I 441

GDDS012I 441

GDDS013I 441

GDDS014I 442

GDDS015W 442

GDDS016I 442

GDDS017I 442


GDDS018I 442

GDDS019I 443

GDDS020E 443

GDDS021I 443

GDDS022I 443

GDDS023I 443

GDDS024I 444

GDDS025W 444

GDDS026I 444

GDDS027E 444

GDDS027W 444

GDDS028W 445

GDDS029I 445

GDDS030I 445

GDDS031I 445

GDDS032I 446

GDDS033I 446

GDDS034I 446

GDDS035I 446

GDDS036I 446

GDDS037I 446

GDDS038I 447

GDDS039W 447

GDDS040I 447

GDDS041I 447

GDDS042I 447

GDDS043I 448

GDDS044I 448

GDDS045I 448

GDDS046I 448

GDDS047E 448

GDDS048I 449

GDDS049E 449

GDDS050E 449


GDDS050I 449

GDDS051E 450

GDDS051I 450

GDDS052E 450

GDDS053E 450

GDDS054E 450

GDDS055E 451

GDDS056I 451

GDDS057E 451

GDDS058E 451

GDDS059E 451

GDDS060W 452

GDDS061E 452

GDDS062E 452

GDDS063E 452

GDDS064I 452

GDDS065I 453

GDDS066I 453

GDDS067I 453

GDDS068I 453

GDDS069I 453

GDDS070W 454

GDDS071I 454

GDDS073E 454

GDDS074W 454

GDDS075I 454

GDDS075W 455

GDDS079W 455

GDDS081I 455

GDDS096E 455

GDDS122I 456

GDDS123I 456

GDDS124I 456

GDDS125I 456


GDDS126I 456

GDDS127I 457

GDDS128I 457

GDDS129I 457

GDDS130I 457

GDDS131I 457

GDDS132I 458

GDDS134I 458

GDDS135I 458

GDDS136W 458

GDDS137W 458

GDDS138E 459

GDDS140E 459

GDDS141I 459

GDDS142E 459

GDDS143I 459

GDDS144E 460

GDDS145I 460

GDDS146I 460

GDDS147W 460

GDDS148I 460

GDDS149W 461

GDDS150I 461

GDDS151E 461

GDDS152E 461

GDDS153I 462

GDDS154E 462

GDDS155I 462

GDDS156I 462

GDDS157I 463

GDDS158W 463

GDDS159W 463

GDDS160I 463

GDDS161I 463


GDDS162I 464

GDDS163I 464

GDDS164I 464

GDDS167E 464

GDDS168E 465

GDDS169E 465

GDDS201E 465

GDDS202E 465

GDDS203E 465

GDDS204W 466

GDDS205E 466

GDDS206I 466

GDDS207E 466

GDDS208E 467

GDDS209I 467

GDDS210I 467

GDDS211I 467

GDDS212E 467

GDDS213I 467

GDDS214I 468

GDDS215E 468

GDDS216E 468

GDDS217E 468

GDDS218E 468

GDDS219W 468

GDDS220E 469

GDDS221E 469

GDDS222E 469

GDDS223E 469

GDDS224E 470

GDDS225E 470

GDDS227E |GDDS227W 470

GDDS228E | GDDS228W 471





GDDS232E 472

GDDS232W 472



GDDS235I 473

GDDS236E 473

GDDS237I 474

GDDS250W 474

GDDS251W 474

GDDS252I 475

GDDS253I 475

GDDS254I 475

GDDS255E 475

GDDS256I 475

GDDS258W 476

GDDS259W 476

GDDS260I 476

GDDS261E 477

GDDS262E 477

GDDS263E 477

GDDS264E 477

GDDS265I 478

GDDS266E 478

GDDS267E 478

GDDS268E 479

GDDS903I 479

GDDS904E 479

GDDS998E 479

Chapter 10 GDDR Tape Messages (GDDT) 481

GDDT001E 481

GDDT002E 481

GDDT010I 481


GDDT011I 481

GDDT012E 481

GDDT013E 481

GDDT014W 482

GDDT016W 482

GDDT017W 482

GDDT018E 482

GDDT019I 482

GDDT020W 483

GDDT021I 483

GDDT025E 483

GDDT026E 483

GDDT030E 483

GDDT030W 484

GDDT031I 484

GDDT040E 484

GDDT043E 484

GDDT050E 484

GDDT059A 485

GDDT060I 485

GDDT061W 485

GDDT062I 485

GDDT063A 486

GDDT064E 486

GDDT080E 486

GDDT081E 486

GDDT081I 487

GDDT081W 487

GDDT085W 487

GDDT086W 487

GDDT087I 487

GDDT090W 488

GDDT091W 488

GDDT101I 488


GDDT200I 488

Chapter 11 GDDR Utility Messages (GDDU) 489

GDDUBG0E 489

GDDUBG1I 489

GDDUBG2E 489

GDDUBG3I 489

GDDUBG4I 490

GDDUC01I 490

GDDUC02I 490

GDDUC03I 491

GDDUC10E 492

GDDUC11E 493

GDDUC12E 493

GDDUC13E 493

GDDUC14E 493

GDDUC15E 493

GDDUC16E 494

GDDUC17E 494

GDDUC18E 494

GDDUC19W 494

GDDUC20W 495

GDDUEX0E 495

GDDUEX1W 495

GDDUEX2W 495

GDDUEX3W 495

GDDUEX4I 496

GDDUG00I 496

GDDUG01E 496

GDDUG02E 496

GDDUG03E 496

GDDUG04E 497

GDDUG05E 497

GDDUG06E 497

GDDUG07E 497


GDDUG08E 497

GDDUG09E 497

GDDUG10I 498

GDDUG13I 498

GDDUG14I 498

GDDUG15I 498

GDDUG16I 498

GDDUG17I 499

GDDUG18I 499

GDDUG19I 499

GDDUG20I 499

GDDUG21I 499

GDDUG25W 499

GDDUG27I 500

GDDUG28I 500

GDDUG29I 500

GDDUG30I 501

GDDUG31I 501

GDDUG32E 501

GDDUG32I 501

GDDUG32W 502

GDDUG33I 502

GDDUG34I 502

GDDUG35I 503

GDDUG37I 503

GDDUG38I 503

GDDUG39I 504

GDDUG40I 504

GDDUG41I 504

GDDUG42I 504

GDDUG43E 505

GDDUG44E 505

GDDUG45E 505

GDDUG46E 505


GDDUG47E 505

GDDUG48E 505

GDDUG49E 506

GDDUG50A 506

GDDUG51I 506

GDDUG52I 506

GDDUG53I 506

GDDUG54I 507

GDDUG55I 507

GDDUG56E 507

GDDUG57E 507

GDDUG58E 507

GDDUG59E 508

GDDUG60I 508

GDDUG61I 508

GDDUG62E 508

GDDUG63E 508

GDDUG64E 509

GDDUG65E 509

GDDUG66E 509

GDDUG67E 509

GDDUG68E 509

GDDUG69W 510

GDDUG70W 510

GDDUG71W 510

GDDUG72W 510

GDDUG73W 510

GDDUG74W 510

GDDUG75E 511

GDDUG76E 511

GDDUG77E 511

GDDUG78E 511

GDDUG79E 511

GDDUG80E 512


GDDUG81E 512

GDDUG82E 512

GDDUG83E 512

GDDUG84E 512

GDDUG85E 512

GDDUG86E 513

GDDUG87E 513

GDDUG88E 513

GDDUG89E 513

GDDUG90E 513

GDDUG90I 513

GDDUG90W 514

GDDUG91E 514

GDDUG92E 514

GDDUG93E 514

GDDUG94E 514

GDDUG95E 514

GDDUG96E 515

GDDUG97E 515

GDDUG98E 515

GDDUG99E 515

GDDUM011E 515

GDDUM01A 515

GDDUM02I 516

GDDUM03I 516

GDDUM04I 516

GDDUM05I 516

GDDUM06A 516

GDDUM07I 517

GDDUM08I 517

GDDUM09E 517

GDDUM10E 517

GDDUM12E 517

GDDUM13E 518


GDDUM14E 518

GDDUM15E 518

GDDUM16E 518

GDDUM17E 518

GDDUM18E 519

GDDUM19E 519

GDDUM20I 519

GDDUM21I 519

GDDUM22I 519

GDDUM23I 520

GDDUM25E 520

GDDUM26E 520

GDDUM30I 520

GDDUM31E 520

GDDUM32E 521

GDDUM40I 521

GDDUM41E 521

GDDUM42E 521

GDDUM43E 521

GDDUM44E 522

GDDUM45E 522

GDDUM46E 522

GDDUM47E 522

GDDUM48E 522

GDDUM49E 523

GDDUM50A 523

GDDUM51I 523

GDDUM52I 523

GDDUM53A 524

GDDUM54I 524

GDDUM55I 524

GDDUM56A 524

GDDUM57I 524

GDDUM58A 525


GDDUM59I 525

GDDUM60A 525

GDDUM61I 525

GDDUM62I 525

GDDUM99E 526

Chapter 12 GDDR User Exit Messages (GDDX) 527

GDDX101I 527

GDDX102E 527

GDDX103I 527

GDDX105E 527

GDDX106E 527

GDDX108E 527

GDDX191I 528

GDDX192A 528

GDDX201I 528

GDDX202E 528

GDDX203I 528

GDDX205E 529

GDDX206E 529

GDDX208E 529

GDDX209I 529

GDDX291I 529

GDDX292A 530

Chapter 13 GDDR zDP Messages (GDDZ) 531

GDDZD00I 531

GDDZD01W 531

GDDZD02I 531

GDDZD03I 531

GDDZD04E 532

GDDZD05W 533

GDDZD06I 533

GDDZD07I 533

GDDZD08I 533


CHAPTER 1 Automated GDDR WTORs (GDDB) GDDB011I

Cause This message is issued by the Handle ConGroup Groups script function. The message ishandled by message rule CGRP095E. Action None.

GDDB012I

Cause This message is issued by the Handle ConGroup Groups script function. The message ishandled by message rules CGRP093E, CGRP150E, and CGRP609I. Action None.

GDDB013I

Cause This message is issued by the Handle ConGroup Groups script function. The message ishandled by message rule CGRP603I.ALL-CONGROUPS is an internal lock that serializes many global operations to ensureConGroup integrity. It is used only if you set ConGroup MODE parameter to MULTI, whichallows two or more ConGroups to communicate. If you use the default MODE value ofSINGLE that prevents two or more ConGroups from communicating, ConGroup does notuse ALL-CONGROUPS. Action None.

GDDB014I

Cause This message is issued by the Handle ConGroup Groups script function. Message rulesCGRP150E, CGRP200I, CGRP201E, CGRP202E, CGRP518E, CGRS210E, and CGRS600Whandle this message. Action

GDDR Waiting for ConGroup to disable group cngrp. Please reply(Yes/Cancel).

GDDR Waiting for ConGroup to enable group cngrp. Please reply(Yes/Cancel).

GDDR Waiting for ConGroup to release ALL-CONGROUPS lock. Pleasereply (Yes/Cancel).

GDDR Waiting for ConGroup to refresh CONGROUP cngrp. Please reply(Yes/Cancel).


None. GDDB015I

Cause GDDR has issued a ConGroup RESUME command, and is not waiting for the indicatedgroup to become enabled. GDDR is waiting for one the following messages to signal success or failure of theRESUME command: CGRP005E, CGRP015E, CGRP150E, CGRP285E, CGRP609I. Whenone of these messages is seen, the GDDB015I WTOR is automatically deleted by GDDR. Action None.

GDDB016I

Cause This message is issued by the Handle ConGroup Groups script function. Action None.

GDDB017I

Cause This message is issued by the Planned DASD Swap to R2 script function. Message rulesCGRS144E and CGRS292I handle this message. Action None.

GDDB018I

Cause This message is issued by the Planned DASD Swap To R2 script function. Message rulesCGRS039E and CGRS201E handle GDDB018I. Action None.

GDDB020I

Cause This message is issued by the Perform ConGroup Startup script function. Action

GDDR Waiting for ConGroup to resume group cngrp. Please reply(Yes/Cancel).

GDDR Waiting for ConGroup to Takeover ownership. Please reply (Yes/Cancel).

GDDR Waiting for validate of group swapgrp to complete. Pleasereply (Yes/Cancel).

GDDR Waiting for swap of group swapgrp to complete. Please reply(Yes/Cancel).

GDDR Waiting for ConGroup to Start CONGROUPcongroup_stc_name Please reply (Yes/Cancel).


None. GDDB021I

Cause This message is issued by the Perform ConGroup Trip script function. Action Do not reply to this WTOR. A GDDR message interception rule will reply automatically.

GDDB022I

Cause This message is issued by the Planned SRDF/A Stop/Restart script function. Action None.

GDDB023I

Cause This message is issued by the Start MSC/STAR script function. The message is handledby message rule SCF1320I. Action None.

GDDB024I

Cause This message is issued by the Start MSC/STAR script function.The message is handled by message rules EMCB0AE, EMCB0DE, EMCB31E, EMCMB40E,EMCMB51E, EMCMB59E, EMCMN98E, SCF1306E, SCF1325E, SCF1342I, SCF1394E,SCF1438E, SCF1439E, SCF1440E, SCF1449E, SCF1483E, SCF1484E, SCF1488E,SCF1491E, SCF1492E,SCF1493E, SCF1495E, SCF1510E, SCF1525I, SCF1542E, SCF1543E,SCF1544E, SCF1546E.EMC* is a preface used on SRDF Host Component messages. SCF is a prefix used onResourcePak Base messages. Action None.

GDDB025I

Cause The Issue MSC command script function issues this message. The message is handled bya message rule. Action None.

GDDR Waiting for ConGroup to trip. Please reply (Yes/Cancel).

GDDR Waiting for MSC PENDDROP. Please reply (Yes/Cancel).

GDDR Waiting for MSC task to Enable. Please reply (Yes/Cancel).

GDDR Waiting for MSC group mscgrp to Enable. Please reply(Yes/Cancel).

GDDR Waiting for MSC to action. Please reply (Yes/Cancel).


GDDB026I

Cause GDDR processing requires additional time for the referenced group to be deleted. Action Reply 'Yes' to proceed normally.

GDDB027I

Cause GDDR processing requires additional time for the SDDF list utility to complete. Action This WTOR will be deleted by GDDR when appropriate. You can reply Yes/Cancel if thereis a problem.

GDDB028I

Cause GDDR processing requires additional time for the SDDF cleanup utility to complete. Action This WTOR will be deleted by GDDR when appropriate. You can reply Yes/Cancel if thereis a problem.

GDDB029I

Cause GDDR is waiting for message SCF1525I to indicate that Star recovery is available. Action Do not reply to this WTOR. A GDDR message interception rule will reply automatically.

GDDB030I

Cause GDDR has issued a F emcscf,DEV,REFRESH command and is now waiting for thecommand to complete. This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDR Waiting for delete of group group_name to complete. Pleasereply (Yes/Cancel).

GDDR Waiting for SDDF list utility to complete. Please reply(Yes/Cancel).

GDDR Waiting for SDDF cleanup utility to complete. Please reply(Yes/Cancel).

GDDR Waiting for MSC Star Recovery Available. Please reply(Yes/Cancel).

GDDR Waiting for DEV,REFRESH command to complete. Please reply(Yes/Cancel)


GDDB040I

Cause GDDR has issued the listed command and is now waiting for the command to complete. This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB041I

Cause GDDR has issued the indicated command and is now waiting for the command tocomplete. This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB042I


GDDB043I

Cause GDDR has issued the listed command and is now waiting for the command to complete. This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDR

GDDR Waiting for MSC,DEACT to complete for group mscgrp. Pleasereply (Yes/Cancel).

GDDR Waiting for MSC,DEACTREFRESH to complete for group mscgrp.Please Reply (Yes/Cancel).

GDDR Waiting for MSC,DISABLE to complete for group mscgrp. PleaseReply (Yes/Cancel).

GDDR Waiting for MSC,ENABLE to complete for group mscgrp. PleaseReply (Yes/Cancel).


fails to notice the completion, you can reply Yes to allow the script to continue. GDDB044I


GDDB045I


GDDB046I


GDDB047I


GDDR Waiting for MSC,PENDDROP to complete for group mscgrp. PleaseReply (Yes/Cancel).

GDDR Waiting for PARM_REFRESH to complete for group mscgrp. PleaseReply (Yes/Cancel).

GDDR Waiting for MSC,REFRESH to complete for group mscgrp. PleaseReply (Yes/Cancel).

GDDR Waiting for MSC,RESTART to complete for group mscgrp. PleaseReply (Yes/Cancel).


GDDB048I


GDDB049I


GDDB050I


GDDB051I

Cause GDDR has issued the indicated command and is now waiting for the command tocomplete. This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not notice

GDDR Waiting for MSC,RESTARTTOSEC to complete for group mscgrp.Please Reply (Yes/Cancel).

GDDR Waiting for MSC,TAKEOVER (Planned) to complete for groupmscgrp. Please Reply (Yes/Cancel).

GDDR Waiting for MSC,TAKEOVER (Unplanned) to complete for groupmscgrp. Please Reply (Yes/Cancel).

GDDR Waiting for MSC,SWITCH to complete for group mscgrp. PleaseReply (Yes/Cancel).


this, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB052I


GDDB060I

Cause GDDR has received a request for an MSC command, but found the indicated group to bein a CLEANUP state. GDDR waits for the group to have a dropped state, before decidingwhether or not the command will be issued. (See message GDDR818I for a list of MSC group states recognized by GDDR.) This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB061I

Cause GDDR has received a request for an MSC command, but found the indicated group to bein a PDROPIP state. GDDR waits for the group to have a PENDDROP state, beforedeciding whether or not the command will be issued. (See message GDDR818I for a list of MSC group states recognized by GDDR.) This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB062I

Cause GDDR has received a request for an MSC command, but found the indicated group to be

GDDR Waiting for MSC,RESTARTTOZERO to complete for group mscgrp.Please Reply (Yes/Cancel).

GDDR Waiting for MSC group mscgrp to have DROPPED state. PleaseReply (Yes/Cancel).

GDDR Waiting for MSC group mscgrp to have PENDDROP state. PleaseReply (Yes/Cancel).

GDDR Waiting for MSC group mscgrp to have DEACT state. PleaseReply (Yes/Cancel).


●

●

●

●

in a DEACTIP state. GDDR waits for the group to have a DEACT state, before decidingwhether or not the command will be issued. (See message GDDR818I for a list of MSC group states recognized by GDDR.) This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB063I

Cause GDDR has received a request for an MSC command, but found the indicated group to bein a DISIP state. GDDR waits for the group to have a DISABLED (or NOTFOUND) state,before deciding whether or not the command will be issued. (See message GDDR818I for a list of MSC group states recognized by GDDR.) This WTOR disappears automatically when the command is seen to complete. Action If the command takes an inordinate amount of time, or fails, and GDDR does not noticethis, you can reply Cancel to stop the script. If the command has completed but GDDRfails to notice the completion, you can reply Yes to allow the script to continue.

GDDB102I

Cause During script processing, an execution of the MSC group cleanup utility (SCFRDFM6,SCFRDFM9, SCFRDFME) is required. This execution requires confirmation. The scriptwaits until:

A response is entered.

The WTOR times out.If a positive response is received, the MSC group cleanup utility is executed. If a negativeresponse is detected, an error code is generated and the script fails. If the WTOR timesout, the result is as if a negative response was entered. Action Determine whether confirmation is appropriate. If so, answer Yes; otherwise No.

GDDB106I

Cause A Test IPL at DC3 operation requires confirmation. The processor waits until:


The WTOR times out.If a positive response is detected, the Test IPL at DC3 operation proceeds. If a negativeresponse is detected, the operation fails; if the operation is being requested by a script, anerror code is generated and the script fails. If the WTOR times out, the result is as if a

GDDR Waiting for MSC group mscgrp to have DISABLED state. PleaseReply (Yes/Cancel).

GDDR Please Confirm Run of {SCFRDFM6|SCFRDFM9|SCFRDFME} Utility(Yes/No)

GDDR Please Confirm Test IPL of system_name at DC3 (Yes/No)


●

●

●

●

●

●

negative response was entered. Action Determine whether confirmation is appropriate. If so, answer Yes; otherwise answer No.

GDDB107I

Cause An IPL operation requires confirmation. The processor waits until:


The WTOR times out.If a positive response is detected, the IPL operation proceeds. If a negative response isdetected, the IPL operation fails. If the IPL operation is being requested by a script, anerror code is generated and the script fails. If the WTOR times out, the result is as if anegative response was entered. Action Determine whether confirmation is appropriate. If so, respond Yes; otherwise respond No.

GDDB109I

Cause An LPAR ACTIVATE or DEACTIVATE operation requires confirmation. The GDDRprocessor waits until:


The WTOR times out.If a positive response is detected, the LPAR ACTIVATE or DEACTIVATE operationproceeds. If a negative response is detected, the operation fails. If the operation is beingrequested by a script, an error code is generated and the script fails. If the WTOR timesout, the result is as if a negative response was entered. Action Determine whether confirmation is appropriate. If so, answer Yes; otherwise answer No.

GDDB112I

Cause A Start MVS Business Workload script requires confirmation. The script waits until:


The WTOR times out.If a positive response is detected, the script executes. If a negative response is detected,the script terminates. If the WTOR times out, the result is the same as if a negativeresponse was entered. Action If confirmation is appropriate, answer Yes; otherwise, answer No.

GDDB113I

Cause

GDDR Please Confirm IPL of system-name at site-id (Yes/No)

GDDR Please Confirm {ACTIVATE|DEACTIVATE} of lpar-name (Yes/No)

GDDR Please Reconfirm Start of MVS Business Workload (Yes/No)

GDDR Please Confirm Abandon DC1 and DC2 (Yes/No)


●

●

●

●

●

●

An IPL of Failed System script requires confirmation. The script waits until:


The WTOR times out.If a positive response is detected, the script executes. If a negative response is detected,the script does not run. If the WTOR times out, the result is the same as if the negativeresponse was entered. Action If confirmation is appropriate, answer Yes; otherwise, answer No.

GDDB124I

Cause A CAX site swap script requires confirmation to run. (Preceding messages describe theaction in further detail.) The script waits until:


The WTOR times out.If a positive response is received, a reconfirmation will be required (GDDB126I). If anegative response is detected, the script does not run. If the WTOR times out, the result isas if the negative response was entered. Action If confirmation is appropriate, answer Yes; otherwise, answer No.

GDDB126I

Cause A CAX site swap script requires a second confirmation to run. (Preceding messagesdescribe the action in further detail.) The script waits until:


The WTOR times out.If a positive response is detected, the script executes. If a negative response is detected,the script does not run. If the WTOR times out, the result is as if the negative responsewas entered. Action If confirmation is appropriate, answer Yes; otherwise, answer No.

GDDB128I | GDDB128W

Cause Site DC3 is ahead of site DC2 in processing. The DC3 data is more current. This WTORmessage is issued so that you can specify which set of data you want to use in anupcoming CREATEPAIR command. The GDDB128W WTOR message is followed by the confirmation WTO message GDDB128I. Action To use the DC3 site data in the upcoming CREATEPAIR command, answer Yes. To use theDC2 site data in the upcoming CREATEPAIR command, answer No.

GDDR Please Confirm Run of SWAPSITEn (Yes/No)

GDDR Please Re-Confirm Run of SWAPSITEn (Yes/No)GDDR Confirmation ===>

GDDR site DC3 ahead of DC2. Please confirm that DC3 data will beused (Yes/No)


●

●

GDDB200I

Cause The end of a test IPL requires confirmation. The script waits until:


The WTOR times out.If a positive response is detected, the script executes. If a negative response is detected,the script does not run. If the WTOR times out, the result is as if the negative responsewas entered. Action If confirmation is appropriate, answer Yes; otherwise, answer No.

GDDB862I

Cause A script or script step requires confirmation before starting the next script action.Usually, such a message is issued only for an action that alters the configuration.(Messages follow that describe the action in further detail.) The script waits until aresponse is entered or the WTOR times out. If the WTOR times out, the result is the sameas if the negative response was entered. Action If confirmation is appropriate, answer Yes; otherwise, answer No.

GDDR Please confirm end of test IPL at site-id (Yes/No)

GDDR Please confirm actionGDDR Confirmation ===>


CHAPTER 2 HMC-Related Messages (GDDH) GDDH001I

Cause IPL parameters not found for initiating IPL the system on the primary site. Action None.

GDDH002I

Cause GDDR did not find a user-specified value for the HMC_TIMEOUT parameter for the sitewhere the current script is running. Action If the default value for 25000 milliseconds is not adequate for your configuration, addHMC_TIMEOUT.DCn parameters matching your requirements.

GDDH004E

Cause No LPAR parameters are defined to GDDR. Action Define the LPAR parameter for all production systems.

GDDH005I

Cause The GDDR HMC Interface module retrieved the indicated SNMP object ID for a CPC or anLPAR. Action None.

GDDH006I

Cause This message shows the object ID. Action None.

IPL parms not found

GDDR Missing HMC Timeout. Defaulted to 25000

GDDR no lpars found

GDDR {CPC|LPAR} oid = object-id

GDDR returning {CPC|LPAR} oid = object-id


GDDH007E

Cause The HMC interface could not retrieve information from the Hardware ManagementConsole (HMC). Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support site for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center.Ensure that you have all relevant job documentation available.

GDDH008I

Cause This message shows the detected status. Action None.

GDDH009E

Cause The HMC interface could not retrieve information from the HMC console. Action Try the script again.

GDDH010I

Cause This message indicates the GDDR status timeout. Action Try the script again.

GDDH011E

Cause The HMC interface failed while trying to retrieve this information. Action Fix the problem and try again.

GDDH012E

Cause Internal error.

GDDR could not retrieve oid

GDDR desired status detected, status=status

GDDR could not get lpar status

GDDR timed out waiting for desired status

GDDR could not get cpc,lpar names for objectid object-id

GDDR could not locate system for lpar


Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center.Ensure that you have all relevant job documentation available.

GDDH013E

Cause The HMC ophminit call failed. Action Consult the IBM HMC redbook documentation for the cause of the error.

GDDH014E

Cause Processor cpc is not defined to HMC. Action Ensure that the correct CPU name is used in the LPAR parameters.

GDDH015E

Cause Problem with parameters or with HMC. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDH016E

Cause The indicated LPAR is not defined to HMC. Action Ensure that the correct LPAR name is used in the LPAR parameters.

GDDH017E

Cause There is a problem with parameters or with HMC. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR HMC initialization failed, rc=rc

GDDR CPC processor_name could not be found

GDDR Error retrieving CPC object id

GDDR LPAR lpar-name could not be found

GDDR error retrieving lpar object id


GDDH018E

Cause Real_CBU is not set. Action Set Real_CBU in the Define Managed CPCs panel.

GDDH019E

Cause Internal error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDH020I

Cause This message shows the GDDR status. Action None.

GDDH021I

Cause This message shows the HMC object attribute. Action None.

GDDH022E

Cause HMCWAAPI returned a non-zero RC for the indicated action and LPAR. Action Consult the IBM Manual, zOS Application Programming Interfaces, SB10-7030-14,Appendix C. API return codes, to determine the cause of the failure.

GDDH023E

Cause The error shown in this message occurred while retrieving status, after GDDR issued an

GDDR RealCbu not set for an ACTIVATE_CBU action

GDDR get_attribute failed reason

GDDR status = status

GDDR attribute value for hmc_object is hmc_attribute

GDDR HMC action action failed for lpar lpar-name, rc=rc

GDDR HMC failed to get attribute for object hmc_object


●

●

●

●

●

●

●

●

●

●

●

●

●

●

HMC command with RC=0. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDH024E

Cause Internal error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDH030I

Cause An HMC status call requested information about the indicated LPAR and the HMC statusis reported as hmc-status.Possible HMC statuses are:

OPERATING

NO POWER

NOT OPERATING

NOT ACTIVATED

EXCEPTIONS

STATUS CHECK

POWERSAVE

LINK NOT ACTIVE

SERVICE

SERIOUSALERT

ALERT

ENVALERT

SERVICE REQUIRED

DEGRADED Action If the status is other than 'Operating', determine the cause, correct the conditions andretry. See causes for the status states of an image object, [lpar] in the Hardware ObjectStatus Summary in the IBM Tivoli System Automation for z/OS Messages and Codes document, SC34-2574-02.

GDDH032E

GDDR Invalid parameter parameter_name passed to program_name

GDDR status of lpar = lpar-name found to be hmc-status

GDDR Invalid command parameters for program_name. Command: commandStopmessage: message


●

●

●

●

Cause Internal error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDH033E

Cause This is a GDDR internal error. The EINVAL return code indicates that the length supplied tothe runtime function __getuserid does not allow enough storage in the string to retrievethe MVS user ID. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH034E

Cause This is a GDDR internal error regarding the use of the runtime function __getuserid. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH035E

Cause This is a GDDR internal error. The EINVAL return code indicates that one of the followingerrors was detected:

Access_type specified is undefined.

Userid was not 1 to 8 characters in length.

Security_class was not 1 to 8 characters in length.

Entity_name was not 1 to 246 characters in length. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH036E

__getuserid RC = rc (EINVAL), reason code: rs

__getuserid RC = rc (Undefined), reason code: rs

__check_resource_auth_np RC = rc (EINVAL), reason code: rs

__check_resource_auth_np RC = rc (EMVSERR), reason code: rs


●

●

●

●

●

●

●

●

●

Cause This is a GDDR internal error. The EMVSERR return code indicates that an MVS internal orenvironmental error occurred. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH037E

Cause This is a GDDR internal error. The EMVSSAF2ERR return code indicates that one of thefollowing errors was detected:

Received an unexpected return code for the security product.

The security product detected an error in the input parameters.

An internal error occurred in the security product. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH038E

Cause This is a GDDR internal error. The ENOSYS return code indicates that one of the followingerrors was detected:

No security product is installed on the system.

The security product does not have support for this function. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH039E

Cause This is a GDDR internal error. The ESRCH return code indicates that one of the followingerrors was detected:

No mapping exists between a UUID and Userid.

The resource specified is not defined to the security product.

The DCEUUIDS class is not active.

The userid is not defined to the security product. Action Search the Knowledgebase on the Dell EMC Online Support website for applicable

__check_resource_auth_np RC = rc (EMVSSAF2ERR), reason code: rs

__check_resource_auth_np RC = rc (ENOSYS), reason code: rs

__check_resource_auth_np RC = rc (ESRCH), reason code: rs


●

●

●

solutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH040E

Cause This may be a GDDR internal error. It may also be due in incorrect GDDR installation. TheEPERM return code indicates that one of the following errors was detected:

The caller is not permitted to use this service.

Do not have the access_type specified to the resource.

Not permitted in address spaces where a load from an unauthorized library has been

performed. Action Ensure that the GDDR load library containing the GDDRC002 executable is authorized.Also ensure that the facility class resource GDDR.HMC.LISTOBJECTS has been setupcorrectly and authorized users has been specified. If unable to correct this problem, search the Knowledgebase on the Dell EMC OnlineSupport website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant documentation available.

GDDH041E

Cause This is a GDDR internal error. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH042E

Cause Your use of the GDDR Discovery function has been rejected. Refer to a previous messagethat will provide the reason for this rejection. Action A preceding message should indicate why the HMC Discovery request failed. If this is asecurity issue, refer to the GDDR Product Guide for your configuration on how to grantthe HMC Discovery privilege, or else, search the Knowledgebase on the Dell EMC OnlineSupport website for applicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant documentation available.

GDDH043E

__check_resource_auth_np RC = rc (EPERM), reason code: rs

__check_resource_auth_np RC = rc (Undefined), reason code: rs

Request to Access GDDR Resource gddrc002 Rejected

Missing or invalid parm passed to gddrc002



GDDH044E


GDDH045E

Cause The IBM HMC function failed. Refer to the IBM Manual, zOS Application ProgrammingInterfaces, SB10-7030-11, Appendix C. API return codes for an explanation of the returncode. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH046E


GDDH047E

Cause The IBM HMC function failed. Refer to the IBM Manual, zOS Application ProgrammingInterfaces, SB10-7030-11, Appendix C. API return codes for an explanation of the returncode. Action Search the Knowledgebase on the Dell EMC Online Support website for applicable

osname_parm Failed

Error in main:1:HwmcaGet call RC = rc

Error allocating %ld bytes for an HwmcaGet call

Error in HwmcaTerminate call return code=rc


solutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH048E


GDDH049E


GDDH050E


GDDH051E


GDDH052E

Error in HwmcaInitialize call return code=rc

Error errorno converting octet string

Error allocating temporary string buffer

Error allocating number-bytes bytes for an HwmcaGet call



GDDH053E


GDDH054E


GDDH055E

Cause Use of the GDDRC008 resource has been rejected. Refer to a previous message that willprovide the reason for this rejection. Action A preceding message should indicate why this request failed. If this is a security issue,refer to the GDDR Product Guide for your configuration on how to grant the GDDRC008privilege. Otherwise, search the Knowledgebase on the Dell EMC Online Support websitefor applicable solutions relating to this message ID. If you cannot determine and correctthe problem, contact the Dell EMC Customer Support Center for technical assistance.Make sure you have all relevant documentation available.

GDDH056E

Cause This is a GDDR internal error.

Error in get: HwmcaGet call rc = rc

Error allocating temporary string buffer

Missing or invalid parm passed to gddrc008

Request to Access GDDR Resource gddrc008 Rejected

__osname() Failed


Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH057I

Cause This message states that the GDDR option has been set to use the HMC Direct Initializeoption. This option instructs the HwmcaInitialize call to use a proprietary TCP/IP socketslevel protocol to perform the HwmcaInitialize, rather than using the SNMP protocol. Specifying Direct Initialize is highly recommended when a firewall exists between theConsole and the API application. This is because the socket used for the HwmcaInitializecall is also used to send event to the API application. Since this socket connection targetsa specific port on the Console (port 3161), it is very straight forward to define a rule in thefirewall that allows connections to this port on the Console. If this flag is not specified, theConsole will attempt to establish a socket connection to a socket created when the APIapplication called the HwmcaInitialize routine. Since the port number for this socket is notfixed, it is very difficult to define a firewall rule to allow this connection from the Consoleback to the API application. Action None.

GDDH058E

Cause The IBM HMC function failed. Refer to the IBM Manual, zOS Application ProgrammingInterfaces, SB10-7030-11, Appendix C. API return codes, for an explanation of the returncode. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH059E


GDDH060E

HwmcaInitialize call will use HWMCA_DIRECT_INITIALIZE.

Error in HwmcaCommand call return code = rc

Error in HwmcaTerminate call return code = rc



GDDH061I

Cause The HMC function has been successfully completed. Action None.

GDDH062I

Cause This message states host the HMC command will be directed to. Action None.

GDDH063I

Cause This message states what community name is used. Action No action required.Community name changes can be made in the Define HMC Community Names panel.

GDDH064I

Cause This message indicates what socket was used. Action None.

GDDH065I

Cause This message shows what snmp ulInetAddr was used. Action

Error in HwmcaInitialize call return code = rc

HwmcaInitialize call was successful

HwmcaInitialize target host = host

HwmcaInitialize target community name = name

HwmcaInitialize socket = socket

HwmcaInitialize agent Internet address = address


None. GDDH066I

Cause This message shows that the HMC function has been successfully completed. Action None.

GDDH067I

Cause This message shows what socket was used. Action None.

GDDH068I

Cause This message indicates the agent's Internet address. Action None.

GDDH069I

Cause This message shows the HMC IP address. Action None.

GDDH070I

Cause This message is used in conjunction with message GDDH069I to state what CPC imagewas used. Action None.

GDDH071I

Cause This message is used in conjunction with message GDDH069I to state what HMCcommand was used. Action

HWMCA_SEND_OPSYS_COMMAND request was successful

HwmcaTerminate socket = socket

HwmcaTerminate agent Internet address = address

gddrc008 hmc-ip-address

cpc-image-id

command


None. GDDH072I

Cause This message is used in conjunction with message GDDH069I to state what communityname was used. Action None.

GDDH073I

Cause This message is used in conjunction with message GDDH069I to state what HMC timeoutwas used. Action No action required.HMC timeouts can be changed using the GDDR - Define Managed HMCs panel.

GDDH074E


GDDH075E

Cause Use of the GDDRC00M resource has been rejected. Refer to a previous message that willprovide the reason for this rejection. Action A preceding message should indicate why this request failed. If this is a security issue,refer to the GDDR Product Guide for your configuration on how to grant the GDDRC00Mprivilege. Otherwise, search the Knowledgebase on the Dell EMC Online Support websitefor applicable solutions relating to this message ID. If you cannot determine and correctthe problem, contact the Dell EMC Customer Support Center for technical assistance.Make sure you have all relevant documentation available.

GDDH076E

Cause This message is used in conjunction with message GDDH075E stating the class that was

-c community-name (default=system id)

-t timeout (default= default-timeout)

Error: Invalid or improper Number of Arguments

Error: Request to Access GDDR resource GDDRC00M Rejected.

Error: Class: class-name


used. Action See action for the GDDH075E message.

GDDH077E

Cause This message is used in conjunction with message GDDH075E stating the profile that wasused. Action See action for message GDDH075E.

GDDH078E


GDDH079E


GDDH080E


GDDH081E

Cause This is a GDDR internal error.

Error: Profile: profile-name

Error: __osname() Failed

Error: mutexattr_init for main thread

Error: mutex_init for main thread failed

Error: mutexattr_settype for main thread


Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH082E


GDDH083E


GDDH084E

Cause The IBM HMC Command function failed. Refer to the IBM Manual, zOS ApplicationProgramming Interfaces, SB10-7030-11, Appendix C. API return codes, for an explanationof the return code. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH085E

Cause This is a GDDR internal error. A previous message should specify the reason for this error. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure you

Error: iconv_open Error

Error: HwmcaInitialize Call RC = rc

Error: Console Activate return code = rc

Error: Failed to issue command


have all relevant documentation available. GDDH086W

Cause This is an internal GDDR warning specifying that an internal table has wrapped. Action No action required.

GDDH087E


GDDH088E


GDDH089E


GDDH090E

Cause This is a GDDR internal error. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,

Warning: GDDR Event Buffer Array has wrapped. count = count

Error: Buffer too Small, ulBytesNeeded= bytes

Error: pthread_attr_init for msg failed

Error: pthread_attr_setsynctype for msg failed.

Error: pthread_attr_setdetachstate for msg failed


contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH091E


GDDH092W

Cause This warning indicates that GDDRC00M failed to create a thread and it will retry. Action None.

GDDH093E


GDDH094E

Cause This is a GDDR internal error Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH095E

Cause The IBM HMC function failed. Refer to the IBM Manual, z0S Application ProgrammingInterfaces, SB10-7030-11, Appendix C. API return codes, for an explanation of the return

Error: pthread_attr_getstackstate for msg failed

Warning: GDDR pthread_create for msg failed, Retrying

Error: GDDR pthread_create for failed on Retry

Error: GDDR pthread_create for msg failed on arrayElement=element-name

Error: HwmcaWaitEvent Call RC= rc


code. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH096E


GDDH097W

Cause This warning message indicates that GDDR is retrying the HMC function. Action None.

GDDH098E

Cause This is a GDDR internal error or a problem with your network. Action Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant documentation available.

GDDH099E


GDDH100E

Error: Expected message not found

Warning: Retrying HwmcaWaitEvent Call

Error: Data Receive problem. Investigate Network.

Error: HwmcaInitialize(2) Call RC= rc



GDDH100I

Cause GDDR reports a successful operation against the indicated GDDR supported interface. Action None.

GDDH101E


GDDH101I

Cause The GDDR Load Profile Management utility reports success updating either the loadaddress or the load parameter for the indicated system, as well as the new values. Action None.

GDDH102E


GDDH103E

Error: HwmcaCommand(2) call return code = rc

GDDR type Interface event

Error: pthread_attr_init for cmd Error

GDDRLPRF HMC Load Profile type update successful for system-name

Error: pthread_attr_setsynctype for cmd Error



GDDH103I

Cause The GDDR Load Profile Management utility reports success updating either the loadaddress or the load parameter for the indicated system. Action None.

GDDH104E


GDDH104I

Cause The GDDR Load Profile Management utility reports the discovered values for the loadaddress and load parameter from the indicated source (Global Variable, HMC Profile,Running System). Action None.

GDDH105I

Cause The GDDR Load Profile Management utility reports either MATCH or MISMATCH for thecomparisons it was able to perform.This message is issued as I-level for a MATCH and as E-level for a MISMATCH. It isfollowed by message GDDH104I, showing the discovered values. Action For a MATCH, no action is required.If a MISMATCH is found for one or more comparisons, investigate whether GDDR globalvariables or an HMC load activation profile need to be updated. Also search the

Error: pthread_attr_setdetachstate for cmd Error.

*GDDRLPRF Updating HMC Load Profile for system system-name *

Error: pthread_attr_getstackstate for cmd Error.

GDDRLPRF source type value

GDDRLPRF Residence Address/Load Parameter ---> {MATCH|MISMATCH}


GDDRLPRF job log for message GDDH111I which may signal that a system was brought upon the wrong site.

GDDH105W

Cause This warning message indicates that the named function failed and GDDR is retrying it. Action None.

GDDH106E


GDDH106I

Cause The GDDR Load Profile Management utility is starting the comparisons between GDDRglobal variables and information to be discovered in the HMC load activation profiledefined to GDDR for the indicated system. Action None.

GDDH107E


GDDH107I

Cause

Warning: GDDR pthread_create for cmd failed, Retrying

Error: GDDR pthread_create for cmd failed on Retry.

* GDDRLPRF Validating HMC Load Activation Profile for System system-name*

*------------------------------------------------------------------------*

Error: GDDR pthread_create for cmd failed. RC= rc

GDDRLPRF will not compare against HMC-stored Profiles.Reason: reason


●

●

The GDDR Load Profile Management utility explains why it will not be comparing theGDDR IPL global variables against the information stored in the HMC load activationprofile.Possible reasons are:

GDDR LOADPROF variable not found for a system

BCPii interface issues Action None.If it is desired that GDDRLPRF does include the affected system in live HMC comparisons,then either define a GDDR LOADPROF variable using the GDDR Parameter Wizard, oraddress the reported BCPii interface issue. Check the GDDRLPRF or GDDRWORK job logsfor GDDH* messages.

GDDH108E


GDDH108W

Cause The GDDR Load Profile Management utility reports that it has not been able to query arunning system for IPL information. As a result, GDDR global variables will not becompared against the indicated running system. The most likely cause for this message isthat GDDRMAIN is not running on the indicated system. Action Check whether GDDRMAIN is running on the indicated system. If the problem persistswith GDDRMAIN running on the indicated system, check for communication issuesbetween the system running the GDDRLPRF utility and the indicated system orauthorization issues.

GDDH109E


GDDH109W

Error: GDDR Unknown Data type Returned : data-type

GDDRLPRF unable to obtain live IPL Information from system system-name

Error: Allocating pszOctetString String Buffer.


Cause The GDDR Load Profile Management utility reports that it has not been able to query arunning system for CURRENT IPL information. As a result, the GDDR global variables willbe compared against the ORIGINAL values, which could explain incorrect MATCH orMISMATCH being reported.CURRENT IPL information may be different from ORIGINAL IPL information in GDDRAutoSwap configurations, if IPL and/or IODF device are part of the AutoSwap group, anda swap occurred while the system was running. This could be the result of communicationissues between the system running GDDRLPRF and the indicated system, resulting inincomplete output returned from the MVS 'D IPLINFO' command used to obtainCURRENT IPL information. Action Rerun GDDRLPRF. If the problem persists, contact Dell EMC Customer Support. Keep theGDDRLPRF job log available.

GDDH110E


GDDH110W

Cause The GDDR Load Profile Management utility reports that it will not be doing any validations. Action Check the GDDRLPRF log for message GDDH107I or GDDH108W.

GDDH111E


GDDH111I

GDDRLPRF may use ORIGINAL instead of CURRENT IPL and IODFaddresses for system system-name

Error: pthread_mutex_lock for msg processing failed.

GDDRLPRF will not perform any IPL information validation forsystem system-name

Error: pthread_mutex_unlock for msg processing failed.

GDDRLPRF System system- name is using type device from the wrongsite


Cause The GDDR Load Profile Management utility has found a MISMATCH between GDDR globalvariables and the IPL or IODF device currently used by the indicated system.This message is shown as additional information for message GDDH105I. Action Inspect GDDR global variables, ensuring they are correct. Alternatively, research why theindicated system has been recently IPL'd from the wrong site in an AutoSwapconfiguration.

GDDH112E


GDDH113E

Cause This is a GDDR internal error. Action Search the Knowledgebase on the Dell EMC Online Support site for applicable solutionsrelating to this message ID. If you cannot determine and correct the problem, contact theDell EMC Customer Support Center for technical assistance. Make sure you have allrelevant documentation available.

GDDH200I

Cause GDDRHMCB encountered a retryable error and has been redriven in an effort to completethe indicated HMC action. The number of retries remaining is also indicated. Action None.

GDDH998E

Cause The indicated module experienced an error interfacing with the indicated GDDR supportedinterface. The message identifies the issuing GDDR module and provides diagnosticinformation. Action Consult the documentation for the indicated interface. If the problem persists, contactDell EMC Customer Support.

Error: Converting Octet String.

Error: Program terminated by the GDDRTERM console message.

Redriving GDDRHMCB0 action (retries remaining: number_of_retries)

GDDR interface-type Interface Error. Diagnostic informationfollows:module diagnostic-information


Keep the following items available:- Script and (or) GDDRWORK job logs- A copy of GDDRPARM- A recent backup of GDDR global variables

GDDHMC1I

Cause A message with the message ID as shown in the message was intercepted on the HMCconsole of the indicated CPC and LPAR. The message occurred at the date and timeshown. The second line contains the text of the original message. This message isgenerated on the system running the GDDR IPL Assist Monitor and is forwarded to everyC-system. This is strictly informational. Any processing of this message (such as a reply) has alreadybeen done on the system where the original message was intercepted. Action None.

message-id on cpc-name,lpar-name at date time


CHAPTER 3 ISPF Interface Messages (GDDI) GDDI002E

Cause You are not authorized by your site's user authorization rules to access the panel or optiondisplayed. Action Contact a security administrator to obtain the necessary authorization.

GDDI003E

Cause During initial environment checking, a GDDR processor determined that the GDDRautomation flag is off. Because the processor cannot continue unless the GDDRautomation flag is on, the processor terminates, and the previous panel is displayed again. Action If appropriate, set the GDDR automation flag on. Then, reinitiate the desired process.

GDDI004E

Cause During initial environment checking, a GDDR processor determined that it was not runningon a GDDR C-system. Because the processor may run only on a C-system, the processorterminates and the previous panel is displayed again. Action Log in to a C-system to perform the function.

GDDI005E

Cause During initial environment checking, a GDDR processor determined that it was not runningon the GDDR master C-system. Because the processor may run only on the master C-system, the processor terminates and the previous panel is displayed again. Action Log in to the master C-system to perform the function.

GDDI006E

Cause

User userid not authorized to panel-option

GDDR unable to continue, GDDR automation is off

GDDR {function|processor} can only run on a C-System

GDDR {function|processor} can only run on the master C-System

GDDR Unable to continue, not running on DC3 C-System


●

●

During initial environment checking, a GDDR processor determined that it was not runningon the GDDR site DC3 C-system. Because the processor may run only on the site DC3 C-system, the processor terminates and the previous panel is displayed again. Action Log in to the site DC3 C-system to perform the function.

GDDI009E

Cause While editing Trace, Debug, Message options in the GDDR ISPF user interface, youentered a TRC, DBG, or MSG command with an invalid second operand (not ALL or A). Action Correct the last command entered and re-issue the corrected command.

GDDI010E

Cause An edit of a parameter work dataset is in progress on the indicated dataset by theindicated TSO user on the indicated C-system at the indicated site. The edit was startedon the indicated date at the indicated time. The comment text indicate more details aboutthe error:

WARNING: Same dataset name being used!

Rev Action You cannot go into edit for any parameter work dataset until the indicated TSO user doesan Activate on the indicated parameter dataset on the indicated C-system at the indicatedsite.

GDDI010I

Cause An edit of a parameter work dataset is in progress on the indicated dataset by theindicated TSO user on the indicated C-system at the indicated site. The edit was startedon the indicated date at the indicated time.This message exists in 2 formats, one to indicate an edit is in progress, the second,showing only the dataset name, to indicate the edit is no longer in progress. Action None.

GDDI011E

Cause

Invalid option option

Edit in progress on dsname by userid on c-system at site-id yyyy/mm/dd hh:mm:ss comment

Format 1:

Edit in progress on dsname by userid on c-system at site-idyyyy/mm/dd hh:mm:ss. commentFormat 2:

Edit in progress on dsname was reset

Last Activated Parm Data set was not specified to GDDPPACT


An error occurred while running the post-activation program. The name of the lastactivated parm dat set was not passed. Action Check the JCL to make sure it specifies the LAPD dataset name in the parm field.

GDDI011I

Cause During GDDR parameter activation, the last activated parameter dataset has been updatedto the indicated dataset name. This message is issued by the GDDPPACT post-activationprogram to show that a copy has been made of the work dataset. Action None.

GDDI015I

Cause A request was made to view the CBU groups defined to GDDR in the Site CBU ProcessorList panel. However, there are no CBU groups defined. Action None required. To define CBU groups, refer to you HMC configuration and specify CBUprocessors in the Site.LPAR parameter.

GDDI018W

Cause This message appears when a selection on the Update GDDR Device Configurationselection menu was made, but no parameters exist in the selected category. Action None.

GDDI019I

Cause This message appears when a numbered parameter entry has been deleted. The remainingparameters of the type that was deleted are resequenced. Action None.

GDDI020E

Cause The value specified for a parameter of the indicated type is not valid for this type ofparameter. Action

Last Activated Parm Data set has been updated to dsname

No CBU definitions found

No entries in selected category found

Delete successful

Value value [for parameter_type ] not valid


●

●

Correct the value entered. If necessary, use the CANCEL command to back out all enteredchanges.

GDDI021E

Cause An attempt was made on the Script JCL Parameters panel to modify the JCL parametersfor jobs submitted internally from GDDR, but there is no valid SRDF Host Componentprefix defined. There must be a valid SRDF Host Component prefix defined to successfullycomplete GDDR batch processing. The SRDF Host Component prefix identifies the HostComponent job to process GDDR SRDF commands. Action Define a valid SRDF Host Component prefix on the Script JCL Parameters panel.

GDDI022E

Cause The value entered for the indicated parameter is a duplicate of an existing parameter ofthe same type. Action Correct the entered value. If necessary, use the CANCEL command to back out allentered changes.

GDDI024E

Cause This message appears when an unsuccessful attempt has been made to add or update alist that is the value of a list-valued GDDR parameter either:

A new numbered GDDR parameter entry

A list entry.The previous panel is displayed again. This message is issued when a TBADD request hasbeen issued to a keyed table that was previously determined not to contain a row whosekey matches the key of the row being added. Action Consult the ISPF Services Guide to determine the meaning of and suggested response tothe specific TBADD return code. Obtain system programming assistance to resolve thisproblem, if necessary.

GDDI025I

Cause This message appears when PF3 is pressed while processing an Add or Update operation.The list of existing parameter values on which the operation was initiated is displayed againwith no changes. Action None.

Host Component prefix required

A parameter parameter-description with value parameter-value already exists

{Add|Update} failed, rc=rc

{Add|Update} cancelled


GDDI026E

Cause The backup member name selected for restore was not found in the dataset. The restoreoperation cannot continue. Action Exit from the GDDR dialog. Then enter GDDR again and attempt to perform the restoreoperation.

GDDI027E

Cause The backup member name selected for restore could not be accessed because of a severeerror. The restore operation cannot continue. Action Determine the meaning of the indicated return code, whose meaning can be found in ISPFServices Guide under the ‘LMMFIND’ service description.

GDDI028I

Cause The backup member name selected for restore could not be accessed due to a severeerror. The restore operation cannot continue. Action Determine the meaning of the indicated return code. You can find the meaning in ISPFServices Guide under the LMMFIND service description.

GDDI029E

Cause When specifying a parameter backup dataset name for a restore, you may not specify amember name. GDDR will list the members for that dataset for you to select one. Action Specify the backup dataset name with no member name.

GDDI030E

Cause While processing the option to restore parameters, GDDR has been unable to allocate thedataset specified as containing the backups. A different backup dataset name is required. Action Specify the backup dataset name again.

GDDI035I

Backup member member_name not found

Access failed for backup member member_name, rc = rc

Restore processing complete from backup member member_name

Member not allowed

Unable to allocate file containing backups


●

●

●

Cause The Manage GDDR Internal Command Queue option has been selected. No queueelements were found, but information about the command queue parameters is displayed.This is a normal result when no script is running. Action None.

GDDI036E

Cause A request has been made for a backup of the GDDR configuration variables and thebackup has failed for the cause specified in the return code. In addition, a TSO messagestating the problem may have been issued just before GDDI036E was received. Action Identify the reason for the backup failure using the return code listed in the GDDI036Emessage string and (if present) the TSO message. If you are unable to resolve theproblem, contact the Dell EMC Customer Support Center.

GDDI037I

Cause A request has been made to backup the GDDR configuration variables and the backup wassuccessful. This message includes:

The number of parameters backed up

The number of records written to the backup dataset

The name of the backup member that was created Action None.

GDDI039I

Cause This message appears when PF3 is pressed while an insert operation is being processed.The list of existing parameter values on which an insert operation was initiated is displayedagain with no changes. Action None.

GDDI041E

Cause You have specified an invalid sort request on the Manage Internal Command Queue panel. Action Correct the sort request by specifying a valid sort option and press Enter to process. See

No queue elements found

Backup failed, rc = rc

Backed up parameter_number parameters, record_number records,into member backup member

Insert cancelled

Invalid sort request


the GDDR Product Guide for your configuration for information about valid sort options onthe Manage Internal Command Queue panel.

GDDI042E

Cause An invalid select code was entered on a list. Further processing of entered select codes issuppressed, and the list is displayed again. Action Enter only select codes chosen from those listed in the header section of the panel.

GDDI043I

Cause No GNS groups are defined on the system or in GDDR. Action None.

GDDI045I

Cause Parameter keyword updates have been performed successfully. Action None.

GDDI046E

Cause The keyword abbreviation specified when adding a new parameter keyword entry isalready in use. The Add panel is displayed again. Action Specify a new keyword abbreviation that differs from any existing keyword abbreviation.

GDDI048E

Cause The option specified is not among the currently available options. Action Specify a valid option or press PF3 to exit.

GDDI057I

Cause

Invalid select code select_code

No GNS groups found

Parameter keyword update(s) complete

Abbreviation keyword_abbreviation already in use for keywordkeyword

Invalid option option

Automation has been set {ON|OFF}


This message states that automation has been set either on or off. Action None.

GDDI058E

Cause A request was made to browse the dataset with the indicated dsname that is specified asthe value of a GDDR parameter. The browse request failed for the reason indicated.Further processing of entered select codes is suppressed, and the list of parameters isdisplayed again. Action Correct the problem indicated by the failure reason.

GDDI059I

Cause A job has been submitted to configure the couple datasets or rebuild the CF structures atthe site previously specified. The GDDR Actions Menu is displayed again. Action None.

GDDI060E

Cause Message GDDI060E is issued from the GDDR Select Script to Run panel when the usersubmits a script and enters an incorrect value for the Specify call override changes for thisscript? field. Action Specify Y or N for this field.

GDDI061E

Cause In specifying options for couple dataset configuration, you have specified a script typeoption which is neither P (for planned scripts) nor U (for unplanned scripts). The ScriptSysplex Options panel is displayed again. Action Specify either P or U.

GDDI065E

Cause

Dataset dsname { has no data | member error | has no members | isVSAM | is in use | not found | browse failed, rc = rc }

Couple dataset configuration job submittedor

CF Structure rebuild job submitted

You must choose either Y or N

You must choose either planned or unplanned scripts

Dataset dsname not found


●

●

●

A dataset name was entered when parameter load processing requested specification of arequired dataset, which may be:

A PROCLIB

An ISPF file tailoring skeleton library

A global variable backup datasetHowever, the dataset was not found. The dataset name entry panel is displayed again. Action Specify a valid dataset name.

GDDI066E

Cause A request was made to edit or browse either the dataset specified as the alternateparameter dataset or one of the listed members. The request failed for the reasonindicated. The panel to load GDDR parameters is displayed again. Action If necessary, correct the problem indicated by the failure reason.

GDDI067I

Cause A GDDR parameter value was successfully saved. The message may indicate that savedvalues were broadcast to the other C-systems as well. The previous panel is displayedagain. Action None.

GDDI070E

Cause The user entered an invalid site ID for either the primary or the alternate couple datasetsor for CF structure relocation on either the Manage Couple Datasets panel or the ManageCF Structures panel. Action For the indicated sysplex object type, specify one of the listed sites. Valid sites are thosein the primary region. In configurations without AutoSwap, only the primary DASD site isvalid. In a SQAR configuration, sites in the secondary region are valid after one of the RDRscripts has run and made SRDF/S available in that region.

GDDI070W

Dataset [or member] {invalid or empty|in use|not found}

Format 1:MsgLevel/Debug/Trace values savedFormat 2:System Exclude list changes savedFormat 3:Production system values updated successfully

sysplex-object Couple DS site must be one of site-idsor

CF Structure location site must be one of site-ids

Globals not found, initialization will be required


Cause The parameter load processor has determined that no global variables exist, and hasconsequently indicated that initialization is required. Action After completing parameter load selection, specify Y in the ‘replace all current parametervalues’ option field on the panel used to confirm GDDR parameter load.If this situation is unexpected, do not proceed with the parameter load and attempt todetermine why no global variables were found. It is possible, for example, that parameterload was performed on another C-system, but the MSF connection to the current systemprevented propagation of the global variables to the current C-system.

GDDI073I

Cause Confirmation was not received for submission of the parameter load job. The ParameterManagement Options Menu panel is displayed again. Action None.

GDDI074I

Cause Enter was pressed on the Confirm GDDR Parameter Load panel and the parameter loadjob has been submitted successfully. The Parameter Management Options panel isdisplayed again. Action None.

GDDI075E

Cause Enter was pressed on the Confirm GDDR Parameter Load panel validation, but theparameter load job submit failed with the indicated return code. The ParameterManagement Options Menu panel is displayed again. Action Determine the reason for the submit failure. It is possible that the job statement is invalid.If the job submission was rejected by a system exit, there may be an SMF record indicatingthe reason for the rejection. There may be an explanatory message in the system log. Inany case, correct the error and reattempt the parameter load.

GDDI077I

Cause A selection presentation was ended when CANCEL was entered or PF3 was pressed. Noselection was returned. The panel from which the selection was requested is displayedagain. Action None.

Update not confirmed, cancelled

Parameter load job submitted

Submit of parameter load job failed, rc = rc

Selection cancelled


GDDI078I

Cause A request was made to view script status, but script status is not available for any scripts.The GDDR Primary Options Menu panel is displayed again. Action None.

GDDI086E

Cause The system on which you are requesting the script submit function was the master C-system when the request was initially entered; but, it is not the master C-system now. TheGDDR Primary Options Menu panel is displayed again. Action To run a script, log in to the master C-system. The name of the master C-system appearsat the right of the GDDR Primary Options Menu panel.

GDDI087E

Cause The script submit function has been requested, but no scripts are eligible in the currentconfiguration. The GDDR Primary Options Menu panel is displayed again. Action To be eligible for submission, a script must be applicable to both the parameter definedconfiguration and to the current configuration state. An instance of the formerrequirement is that a script specific to BCVs cannot run if TimeFinder/Mirror is notinstalled. An instance of the latter requirement is that a script specific to site DC3 cannotbe run if the link to DC3 is down. Begin to diagnose the cause of the problem. For example,check the links between the sites, determine the primary DASD site, or check the status ofSRDF/Star and SRDF/A.

GDDI088E

Cause This message appears on a GDDR panel, usually but not always, a selection panel, whenthe value entered consists of the initial characters of more than one command or optionvalid on the panel. The panel is displayed again. Action Enter the full command or option name, or include sufficient additional characters to allowa unique match with the desired option or command available on the panel.

GDDI089E

Status unavailable for any script

Current system is no longer master C-System, {cannot runscripts|cannot perform CBU actions}

No eligible scripts found for selection, check configuration andstate.

{Command|Option} <command or option string> ambiguous

Only one script may be selected


●

●

●

Cause More than one script has been selected with select command S on the list of scriptsdisplayed. Because only one planned script may run at a time, selection of more than one isnot allowed. The script selection list is displayed again. Action Select only one script for submission.

GDDI091I

Cause A request was made on the Specify Default Script Call Overrides panel to perform aparameter load. However, the user decided not to save the updates. This message alertsyou to that fact. Action None.

GDDI092I

Cause The script submission was cancelled and the GDDR Primary Options Menu panel isredisplayed. Action None.

GDDI094E

Cause Before presenting the script submit selection list, GDDR attempted to obtain the SRDFHost Component command prefix needed for proper script operation from the SRDF HostComponent control member. However, the control member could not be accessed for thereason indicated.

If the reason is not defined, the appropriate Host_Component.CntlMem

parameter may have been omitted from the parameter file.

If the reason is unavailable, the control file may currently be in use.

If the reason is invalid, the control file may have been corrupted or may have been

specified incorrectly. Action Determine the cause of the error and correct it. Depending on the cause, you may attemptto have the control file released, rebuild the control file, or respecify the GDDRHost_Component.CntlMem parameter.

GDDI095E

Cause No systems at the indicated site were found with IPL or IPLBCVS global variables whichwere not also on the System Exclude list. The excluded systems appear on the Define

Call Override value changes discarded

Script submit cancelled as requested

Host Component control file {not defined|unavailable|invalid }

No eligible systems found to IPL at site-id


Managed Systems panel as "Manage Workload=NO". Action Confirm that systems which were expected to be IPLed have IPL or IPLBCVS parametersfor the site shown and that they are not specified as 'Manage Workload=NO" on theDefine Managed Systems panel.

GDDI098I

Cause No changes were made to a GDDR list of entities. The display ends and the previous panelis displayed again. Action None.

GDDI100I

Cause While processing a system exclude list view/update request, a request was made to add asystem to the list. However, the system is not eligible for the indicated reason. The systemexclude list is displayed again. Action None.

GDDI101I

Cause This message appears when Enter has been pressed by no option or command has beenentered on the panel. This does not indicate an error, but is simply a reminder. Action Enter one of the options shown on the panel or a TSO command, and press Enter. Youmay also press PF3 to return to the next higher level panel.

GDDI102E

Cause This message appears when the unrecognized or unsupported command shown in themessage has been entered. Action Enter one of the options shown on the panel or a TSO command, and press Enter. Youmay also press PF3 to return to the next higher level panel.

GDDI105E

Cause You have entered an invalid value in the Backup consistency field of the Manage GDDR

entry_list_type not changed

System system-name {already in exclude list|is a C-System|notdefined}

Enter option

Unrecognized {command|option|parameter} <command or option string>

Invalid option for Backup consistency: option


Parameter Backups panel. Action Correct the invalid value. For information about valid values, see the GDDR Product Guidefor your configuration.

GDDI106E

Cause This message appears when an invalid value for a GDDR parameter has been entered. Action Correct the entered value.

GDDI107I

Cause This message notes the number (if any) of entries that were removed from the list. Action None.

GDDI109E

Cause No default SCF suffix has been defined. An SCF suffix is necessary for GDDR to identifywhat SCF job to use for its operations. Action You can define an SCF suffix in the Script JCL Parameters panel. You can identify whichSCF prefix to specify by locating the SCF job JCL DD that begins with //SCF$ andspecifying the rest of the name. For example, if the SCF job had the following DDstatement you would specify GDD for the SCF suffix.//SCF$GDD DD DUMMY

GDDI110I

Cause The indicated command directed by HMC to the indicated system has completedsuccessfully. The Perform HMC LPAR Actions panel is displayed again. Action None.

GDDI111I

Cause The indicated command directed by HMC to the indicated system was not successful. ThePerform HMC LPAR Actions panel is displayed again. Action

Invalid program name

{No entries|One entry|number entries} removed

Default SCF suffix cannot be blank- must identify SCF commandprocessor

GDDR command of system system-name completed successfully

GDDR command of system system-name failed, rc = rc


Determine the reason for the failure. GDDI113I

Cause While selecting a GDDR parameter backup member for a restore operation, PF3 waspressed or END was entered. The restore operation is cancelled and the ParameterManagement Options Menu panel is displayed again. Action None.

GDDI114I

Cause The indicated command was to be directed by HMC to the indicated system, butconfirmation was not received. The Perform HMC LPAR Actions panel is displayed again. Action None.

GDDI115E

Cause A LOAD or LOAD CLEAR action was requested for the indicated system. However, no loadparameters are associated with the system, so the action cannot be performed. ThePerform HMC LPAR Actions panel is displayed again. Action Select LOAD or LOAD CLEAR actions only for systems for which load parameters aredefined. If necessary, define load parameters for the indicated system by means of the‘IPL.’ parameter. This parameter is described in the GDDR Product Guide for yourconfiguration.

GDDI116I

Cause The requested script has been submitted successfully following confirmation of therequest. Action None.

GDDI117E

Cause A request was made to discover HMC objects at the sites configured in GDDR. However,no sites were found. The previous panel is displayed again. Action

Parameter restore cancelled

GDDR command of system system-name cancelled, confirmation notreceived

No IPL parameters defined for system system-name

Script submitted successfully

HMC objects unavailable, no sites defined


Determine why no sites were found. Sites are configured in GDDR with the site-id.C.System.Systemid parameters.

GDDI118I

Cause The MsgLevel/Debug/Trace output level list for the indicate user is being presented forview or update. This message is issued initially and, after a user ID switch has beenrequested, by means of the USER command or by overtyping of the associated user ID onthe panel. Action None.

GDDI121I

Cause A request was made for information about the planned script most recently submitted, butno information is available. This is not an error condition, although it can only occur if noplanned script has been submitted since the last parameter initialization load. Action None.

GDDI124E

Cause A request was made to perform GDDR AutoSwap group list updates. The primary orsecondary list must be selected for update, which is done by entering P or S respective.However, the response entered was neither of these values. The selection panel isdisplayed again. Action Enter a valid response.

GDDI126E

Cause On the Define Managed CPCs panel, an invalid selection value was specified. Action Specify one of the listed options, or press PF3 to exit.

GDDI128I

Cause This message appears when PF3 is pressed on a panel displayed in an update request. Thepanel on which the update request was made is displayed again with no changes to eitherdisplayed or nondisplayed GDDR values.

Setting message levels for GDDR programs running under useriduserid

No last-submitted script information available

Unrecognized action, enter P or S

Invalid ADD request

No change[s] made


Action None.

GDDI129I

Cause This message appears when PF3 is pressed on a panel following an update request whenone or more values have been changed. The display on which the update operation wasinitiated is displayed again, showing unchanged values. Action None.

GDDI135E

Cause You have specified a member for a backup dataset and should only specify the datasetthat will contain the member. GDDR will build the member name based upon a schemebeginning with year, day of year, hour, and minute in the form: YDDDHHMMWhere Y is an alpha value representing the last day of the year

DDD = Day of the year.HH = Current hour, (24-hour value), in local time.MM = Current minute in local time. Action Specify the backup dataset name with no member name.

GDDI136E

Cause GDDR was unable to allocate the backup dataset. Action Determine why GDDR was unable to allocate the backup dataset. Review the job log andSYSLOG for errors. Search the Knowledgebase on the Dell EMC Online Support websitefor applicable solutions relating to this message ID. If you cannot determine and correctthe problem, contact the Dell EMC Customer Support Center for technical assistance.Make sure you have all relevant job documentation available.

value_description unchanged

Member not allowed

If the year ends in the value displayed is

0 Z

1 A

2 B

3 C

4 D

5 E

6 F

7 G

8 H

9 I

Unable to allocate backup dataset dsname rc = rc


GDDI139E

Cause In the Script JCL Parameters panel, GDDR was unable to include the specified SurrogateUser ID into the JCL above. This is due to either the JOBCARD statement on which an oldUSER=clause has been specified cannot fit the new USER=specification, (there is amaximum of 71 bytes for each JOB card), or there is no continuation for the jobcard toinclude the USER=specification. Action Change the JOB card statement that contains the USER=specification to allow more roomfor the Surrogate User ID or allow for the USER=specification to be placed on ancontinuated JOBCARD statement.

GDDI145I

Cause GDDR is refreshing the GDDR message table. Action None.

GDDI146I

Cause GDDR has refreshed the GDDR message table. Action None.

GDDI147I

Cause This message indicates a change in GDDR state and requires the user to reselect a script. Action None.

GDDI150I

Cause This message states that on the Transfer Master C-System panel, you had requested totransfer the master C-system to another C-system. However, in the subsequent GDDRMove Confirmation popup panel, you chose not to perform this function. Action None.

GDDI151E

Unable to include USER into JOB card statement

Refreshing GDDRMSG Table

GDDRMSG Table refreshed

GDDR state has changed, please reselect script

Transfer cancelled


Cause On the Transfer Master C-System panel, you had requested to transfer the master C-system to another C-system. However the transfer failed. Action Contact the Dell EMC Customer Support Center for technical assistance.

GDDI153E

Cause The backup request was cancelled by the user. Action None.

GDDI154E

Cause The user attempted to change GDDR automation from ON to OFF or from OFF to ONwhile either a planned or unplanned script was in progress. This is not allowed. Action Wait or take appropriate action for GDDR scripts, planned or unplanned, to completebefore attempting to turn GDDR automation on or off.

GDDI157E

Cause The first line of the JCL on this panel must contain a jobcard but does not. Action Specify a jobcard on the first line of the JCL and press Enter .

GDDI158E

Cause You have specified an invalid jobcard on the first line of the JCL on this panel. Action Correct the jobcard and press Enter .

GDDI159E

Cause The left-most characters of the jobname in your jobcard does not match the jobnameprefix that has been setup by your system administrator. Action Correct the jobname to conform to the jobname prefix and press Enter.

Transfer failed, rc = rc

Backup request cancelled

{Planned|Unplanned} script in progress, Automation may not bechanged.

No jobcard specified.

Invalid jobcard specified: jobcard

Invalid jobname: jobname, must match Jobname Prefix: jobname


GDDI160E

Cause A Surrogate User ID has been specified in the Script JCL Parameters panel with theEnforce option set to Yes. The specified jobcard statement does not specify thatSurrogate User ID. Action Change the User ID on the jobcard to the Surrogate User ID. You can find the SurrogateUser ID value on the Script JCL Parameters panel.

GDDI161E

Cause A Surrogate User ID has been specified in the Script JCL Parameters panel with theEnforce option set to Yes. The specified jobcard statement does not contain aUSER=clause. Action Modify the jobcard to include a USER=clause, specifying the Surrogate User ID.

GDDI162E

Cause The User ID you specified on the jobcard does not match the Surrogate User ID and theEnforce option has been specified. Action Change the User ID on the jobcard to the Surrogate User ID and press Enter .

GDDI163I

Cause The selected parameter backup member was deleted as requested. Action None.

GDDI164E

Cause The selected parameter backup member was not deleted. Refer to the accompanyingreturn code. Action Correct the condition indicated by the return code and request the action again.

GDDI165E

Invalid Job User ID: userid-parm, does not match Surrogate UserID: userid-parm

Invalid Jobcard- User clause must be specified and match SurrogateUser ID:

Invalid Jobcard - User clause must match Surrogate User ID: userid

Member backup-member-name deleted

Failed to delete member backup-member-name (RC=rc)


Cause A duplicate backup member name was found in the parameter backup dataset. Action Request the backup again. A different backup member name will be created, avoidingmember name duplication.

GDDI166I

Cause END or RETURN or CANCEL pressed before selecting a backup member name on theSelect Parameter Input Dataset panel. Action None.

GDDI167E

Cause You have selected Option S, Run GDDR scripts from the GDDR Primary Options Menupanel. You cannot run GDDR scripts prior to supplying an SRDF Host Component prefix. This is because the SRDF Host Component prefix is required for any of the scripts youmight run. Action Specify the SRDF Host Component prefix on the Script JCL Parameters panel. Thenselect Option S, Run GDDR Scripts on the GDDR Primary Options Menu panel again.

GDDI168E

Cause You are attempting to run a GDDR script from the Select Script to Run panel, but thescript is not allowed to run at this time. The Status field has a text starting with *, giving areason for this.A common cause for this message is a change in the state of the GDDR-plex occurringbetween the time the user accesses this panel and the time the script is selected to run. Insuch case, user accesses the panel showing a blank Status field for the script at that time.After the script is selected the Status field will be updated if the GDDR state has changed. Action Run a different GDDR script, or take other corrective actions to address the problemindicated in the Status field.

GDDI169E

Cause The jobname in your jobcard does not match the jobname built by GDDR when theJobname Prefix that has been setup by your system along with the Enforce option. Action

Please wait 1 minute before taking the next backup

No GDDR Parameter Load input dataset selected

Error- A Host Component Prefix must be specified on Script JCLparameters panel prior to running scripts

Script not selectable, please check Status field

Invalid jobname: jobname must match Jobname: enforced_jobname


Correct the jobname value to the enforced_jobname value . GDDI170E

Cause User attempted to exit from the Select Parameter Input Dataset panel with a backupmember selected, however no parameter wizard work dataset was provided. Action Either supply a work dataset name to be populated with initial parameter values for editingwhen you exit the Select Parameter Input Dataset panel, or unselect the selected backupmember if you want to exit the panel without preparing a work dataset.

GDDI171E

Cause User attempted to exit from the Select Parameter Input Dataset panel with a backupmember selected, however no description for the intended parameter change wasprovided. Action Either supply brief description of the parameter changes when you exit the SelectParameter Input Dataset panel, or unselect the selected backup member if you want toexit the panel without preparing a work dataset.

GDDI172I

Cause The indicated parameter backup member will be used to populated the work dataset inpreparation for intended changes. Action None.

GDDI173E

Cause The global variable level field on the primary global variable display panel has beenovertyped with a new level. The new level does not start with GLOBAL.GDDR. Action Enter a correct value for the level or navigate using the S line command.

GDDI174E

Cause A single node delete (line command 6) was issued, but the node against which thecommand was issued is not a variable. The node is actually an intermediate node with

Please either unselect backup-member-name or provide a workdataset name

Please either unselect backup-member-name or provide a descriptionfor this Parameter Load

Member backup-member-name selected as GDDR Parameter Load Input

Invalid level

Nothing to delete


subnodes and no value. Action None.

GDDI175E

Cause A display was requested by overtyping the level field, but there are no global variablesunder that level. Action None.

GDDI176E

Cause The parameter wizard work dataset was unavailable. Refer to the accompanying returncode to assist you with your analysis. Action Ensure the specified parameter wizard work dataset has been pre-allocated. MemberGDDRABDS in hlq.GDDRvrm.SAMPLIB contains JCL to assist you with this task.

GDDI177E

Cause An error occurred during the update of the parameter wizard work dataset. Refer to theaccompanying return code to assist you with your analysis. Action Correct the condition indicated by the return code and save the updates your desired onthe parameter wizard panel again.

GDDI179E

Cause You are attempting to prepare a work dataset. However, the dataset name you entered inthe work dataset field conflicts either with the name of the parameter input dataset, whichis the dataset name entered for input on this ISPF panel, or it conflicts with the lastactivated parameter dataset (LAPD), which is the dataset name used by GDDR to saveparameters at the time of a parameter activation. Action Correct the name of the dataset in the Parameter Load work-dataset field and re-issue thePREPARE command.

GDDI180I

Cause

No variables at this level

Work dataset allocation failed. (RC=rc)

Failed to add member &member-name&. (RC=rc)

Work Dataset cannot be the same as the [parameter input|LastActivated parameter] dataset

Work Dataset prepared for Initial GDDR Parameter Load


●

●

●

●

●

1.

2.

1.

The parameter wizard work dataset has been populated with the contents of the selectedparameter backup member. Action None.

GDDI181E

Cause The message is accompanied by a return code and a reason.Possible reasons are:

1. Failed to obtain consistency - increase retry The parameter backup job was processing and consistency was requested. A GDDRvariable change occurred during the backup processing. As a result, GDDR rejectsthe backup request, after retrying up to nine times to obtain consistency. Likelycauses for GDDR variable updates are:

GDDR EVM/message interception rule activity (event detection)

GDDR script activity

GDDR ISPF usage other than performing the backup request.

2. Fatal problem - please check related messages A fatal error occurred during the backup process.

Action For reason 1, increase the number of retries (up to 9 retries can be requested).For reason 2, review accompanying messages to help diagnose the problem. Contact DellEMC Customer Support for further assistance.

GDDI181W

Cause The message is accompanied by a return code and a reason. Possible reasons are:

Update occurred during backup - ignored The parameter backup job was processing and consistency was not requested.

A global variable change occurred during the backup

processing. This update may or may not be included in the backup dataset. As a result, thebackup will possibly not reflect the status of the GDDR variables at any single pointin time.

Action If you want to enforce backup consistency specify the appropriate Consistency option onthe Manage GDDR Parameter Backups panel. If not, you can ignore this message.

GDDI182E

Cause You are attempting to enter the Select Parameter Input Dataset panel from the ParameterManagement Options Menu panel (M;P). However:

No global variable backup dataset has been defined yet for the current C-system

GDDR failed to create Parameter Backup (RC=rc) reason

GDDR Parameter Backup created with rc=rc, rsn=reason

No Global Variable Backup dataset specified.


2.

(this can happen right after installation of GDDR and before the first parameter set

activation).

Your GDDR user profile does not specify a global variable backup data.This message is displayed at the same time with the Change GDDR ISPF Profile VariableValues panel (P), where you can enter the name of the global variable backup dataset tobe used. Action Enter the name of a global variable backup dataset, next to the prompt "Global variablebackup ===>" and press PF3 to save the setting. Once done, the Select Parameter InputDataset panel is displayed, as originally requested.

GDDI201E

Cause A request to sort the GDDR command queue elements listed in the display has named aninvalid sort key. Consult the GDDR Product Guide for your configuration to obtain fullinformation about valid sort keys. Action Reenter the sort request specifying a valid sort key.

GDDI202E

Cause You cannot transfer the master C-system unless the GDDR Automation flag is set to ON. Action In the GDDR Primary Options Menu panel, issue the command GDDR ON to set the GDDRAutomation flag to ON. Afterwards, if you would like to turn automation back OFF, issuethe GDDR OFF command.

GDDI203I

Cause This message states that the transfer of the master C-system has been successfullycompleted. Action None.

GDDI205I

Cause This message shows that no updates have been made to the production systems. Action None.

GDDI205W

Invalid sort key sort_key

Master C-System transfer may not take place while Automation is ON

Transfer Successful

Production system parameter values unchanged


Cause The GDDR Parameter Load, GDDRGF04, has issued a message that the parameter can beupdated online. Action None.

GDDI206E

Cause This message appears when GDDR parameters have been updated, but the update of thespecified GDDR parameter file failed (for the reason specified in the displayed returncode). Action Find the meaning of the displayed return code in the ISPF Services Guide under the ‘Edit’service description. (The code is returned by ISPF edit.) If necessary, correct the dsnameand member name to specify the correct parameter file or specify the ‘Update parameterfile also?’ option as N.

GDDI206I

Cause No changes were made to a GDDR list of entities. The display ends and the previous panelis displayed again. Action None.

GDDI220E

Cause An unexpected return code was given by GDDRQFCN. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center for

parameter_value is an online parameter

Parameter file not updated, rc = rc

Message text can be one of the following:

Parameter broadcast set not changed●

Call Override defaults unchanged●

Site CBU processor list unchanged●

MsgLevel/Debug/Trace values unchanged●

HMC Community Names unchanged●

Swap group list unchanged●

System Exclude list unchanged●

Call Override values unchanged●

Background job values not changed●

Parameter file not changed●

Production system parameter values unchanged●

Error from GDDRQFCN LIST - rc


technical assistance. Make sure you have all relevant job documentation available. GDDI221E

Cause An unexpected return code was given by GDDRQFCN DELETE. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDI222E

Cause A request was made to delete a command queue element, but the command queue haschanged since the original list was generated. Action Exit the Internal Command Queue and reenter to get an updated list of command queueelements.

GDDI361E

Cause GDDR was unable to update the MsgLevel/Debug/Trace listed on the specified system. Action Ensure that your communication to the reference system is active. This can be verified byusing the F GDDRMAIN,COMM command. Check the list of systems and IP addresses andports displayed to be sure the list is complete and all system IP addresses are correct.Contact the Dell EMC Customer Support Center if you are unable to resolve this.

GDDI365W

Cause You have invoked the Perform HMC LPAR Actions panel. In your installation, HMC actionshave been secured by user ID and you are not authorized to perform HMC actions on anyLPAR. Action Contact your security administrator and request to be authorized to perform HMC actionson the desired LPARs.

GDDI366W

Cause The HMC LPAR action panel was selected, but no LPARs are listed because all relevant

Error deleting command queue element, rc = rc

Command queue has changed. Refresh list and retry

Unable to update MsgLevel/Debug/Trace list on system_id, rc =return_code

You are not authorized for HMC actions on any LPAR

No LPARs listed (HMC Bypass specification)


systems are specified with HMC bypass. Action None.

GDDI367W

Cause The HMC LPAR action panel was selected, but no LPARs are listed because all relevantsystems are specified with HMC bypass except those which you are not authorized tomanipulate. Action None.

GDDI370W

Cause There are no variables defined in the indicated member of the parameter work dataset. Onan initial parameter load, this is normal. Action None required. However, if there should be existing parameters in the member,investigation may be needed.

GDDI371W

Cause There are no sysplexes defined. This may be expected or not, depending on theconfiguration. Action If sysplexes should be defined, associate systems with a sysplex; if not, skip this panel.

GDDI372W

Cause On the Define Managed Couple Datasets panel (1/2), NO was specified for all coupledataset types for all sysplexes defined to GDDR. As a result, no couple dataset parameterscan be defined on panel Define Managed Couple Datasets (2/2). Action If the intention is not to allow GDDR to manage couple datasets, simply proceed to thenext panel. If GDDR should manage couple datasets of certain types, press PF5 to returnto the previous parameter definition panel, and specify Yes for at least one couple datasettype, and for at least one sysplex.

GDDI373E

You are not authorized for HMC actions on any non-HMCBYPASS LPAR

Nothing to load from member

No sysplexes defined, please either assign systems to a sysplex orproceed to the next panel

GDDR management not selected for any type of Couple dataset. Please select a type on the previous panel or proceed to the nextpanel


●

●

●

●

Cause The indicated parameter is not valid for the reason stated. Action Correct the value on the panel and retry.

GDDI374E

Cause The value shown is invalid for the field name in which it was entered. The description textgives information indicating what may be wrong with the value entered.The substitutions for field-name are:

IPL parms

SDDF clean

call override

NON STAR management option Action Correct the entry.

GDDI375W

Cause During a partial parameter set activattion, there were no updates found in the workdataset. Action Verify that contents of the parameter load work dataset specified in the Select ParameterInput Dataset panel contains at least one member which begins with the letter A throughY. Ensure that the parameter load work dataset is the same dataset which was specified inthe Select Parameter Input Dataset panel when the 'Prepare' action, 'Prepare WorkDataset for Parameter Load' was completed. Correct these conditions if they exist andrepeat the parameter edit, validate and activate steps.

GDDI376E

Cause During a parameter set activate, the backup taken before the activation is performedfailed with the indicated return code. The option to ignore backup failure was not set. Theparameter set activation (parameter load) is not done. Action Correct the cause of the backup failure or specify Ignore Backup Failure: Yes on theActivate GDDR Parameter Set panel. Retry the parameter load.

GDDI377W

Cause The parameter set validation or activation failed. Review the output of the parameter setvalidation or activation job to determine the reason for the failure.

Invalid data for item - reason

Invalid field-name - description value

No changes found

Back up failed, rc = rc, parameter set activate canceled

Command Queue Clear failed, rc = rc


Action Try to clear the command queue using the GDDRXCMD batch utility, as described in theGDDR Product Guide for your configuration. If unable to clear it, contact Dell EMCCustomer Support.

GDDI378E

Cause The GDDR Command Queue Clear action failed with the indicated return code. Action Correct the indicated problems and retry.

GDDI379E

Cause The combined output of the parameter manipulation panels could not be allocated orwritten. The return code from the failure is shown in the message text. Action Correct the cause of the problem and retry.

GDDI380E

Cause The name field has an invalid value. Action Supply a correct value.

GDDI381E

Cause Retry was indicated for consistency, but the format was invalid. The format is eitherRETRY(number) or RETRY=number. Action Supply a correctly formatted value for consistency.

GDDI382E


GDDI383E

Parm type failed, return code = rc

Unable to action parm output, rc = rc

Invalid field

Invalid Consistency; retry format is Retry(number) or Retry=number

Invalid Consistency; retry format is Retry(number).


●

●

●

●

●

●

●

●

●

●

●

●

●


GDDI384E

Cause The Perform Health Check ISPF program encountered an internal error. reason describesthe error and error code. Action If you cannot correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant documentation available.

GDDI387E

Cause The parameter validation or activation panel was entered. The status of any previousparameter validation or activation is displayed. Possible values for message parametersare:

status

job submitted

job started

job waiting for WTOR

completed - RC=rc

unknown GDDRSTOK RC=rc

unknown TOKVALUE=value

jobinf - (FOREground) or

(Job jjjjjjjj J#######)

(Job jjjjjjjj J####### submitted yyyy/mm/dd hh:mm:ss), where

jjjjjjjj is a jobname and J####### is the JES job number for the job.

cmt - No edits allowed until activation completes or

ACT RESET

Use ACT FORCE to start another activation Action If a BACKground job was submitted and displayed as submitted, check that the job is notheld (if so, release), otherwise delayed; no initiators, for example.If the status displayed is job waiting for WTOR, a REPLY operator command needsto be issued to the outstanding WTOR issued by the indicated job.If the status displayed is unknown GDDRSTOK RC=rc or is displayed as unknownTOKVALUE=value, contact Dell EMC Customer Support.If the status of the activation or validation is displayed as completed, you can use theVIEW command to browse the output log of the validation or activation run.

GDDI387I

Invalid Consistency; retry format is Retry=number.

Internal error, reason: reason

Parm {validation|activation}, status, jobinf, cmt


●

●

●

●

Cause The parameter validation or activation panel was entered. The status of any previousparameter validation or activation is displayed. The values substituted for status and jobinf are:status

job submitted

job started

job waiting for WTOR

completed - RC=rc Action If a BACKGROUND job was submitted and shows it has not yet started: check that the jobis not held (if so release), or otherwise delayed; no initiators, for example.If the status displayed is job waiting for WTOR, a REPLY operator command needsto be issued to the outstanding WTOR issued by the indicated job.If the status displayed is unknown GDDRSTOK RC=rc or is displayed as unknownTOKVALUE=value, contact the Dell EMC Customer Support Center for assistance.

GDDI388E

Cause Validation for the dataset type listed in the message failed. error-message describes theerror.The validation for this dataset type must exist, be able to be allocated, and must be PDSformat. Action Correct the error and try again.

GDDI389E

Cause Validation of the Default SCF suffix has failed because one or more characters specified isinvalid. Validation SCF suffix characters are either alphanumeric or national ($, #, @)characters. Action Correct the error and try again.

GDDI390E Cause Action Correct the error and try again.

GDDI391E

Cause A request was made to abandon a script, but the associated lock is not held. The scriptcannot be abandoned.

Parm {Validation|Activation} status jobinf

dataset-type error: error-message

Default SCF suffix Must be composed of alphanumeric and/ornational characters

Unable to abandon - lock not held


Action To abandon the script, contact the Dell EMC Customer Support Center.

GDDI392I

Cause A request was made to abandon a script, and the abandon process has completed withouterror. Action None.

GDDI393E

Cause A request was made to abandon a script, but the abandon process failed for the reasonindicated. Action Correct the problem shown by the reason and retry the abandon. If the problem cannot becorrected, contact the Dell EMC Customer Support Center.

GDDI394E

Cause The command queue could not be cleared on one or more C-systems. Commands may stillbe in progress. Action Wait for any active commands to complete, and retry. Contact Dell EMC CustomerSupport if the problem persists.

GDDI901I

Cause No changes to the existing values were detected. Action None.

GDDI902I

Cause Changes to the existing values were detected and saved. Action None.

GDDI996E

Script was successfully abandoned

Abandon failed: reason

Command queue could not be cleared everywhere (GDDRXCLQ RC rc)

Diagnostics settings unchanged

Diagnostics settings updated


●

●

●

●

Cause Invocation of the command queue interface program failed and the indicated messagewas retrieved. Command queue display processing is terminated, and the previous panel isdisplayed. Action Using the message text, attempt to resolve the problem. Among steps you might take,check to make sure that:

The library containing GDDR load modules is APF-authorized.

GDDRICQU has been included in the authorized called program list in the

SYS1.PARMLIB IKJTSOxx member.If unable to resolve the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDI997E

Cause Invocation of the command queue interface program failed with the indicated return code,but no system error message could be retrieved. Manage Internal Command Queue panelprocessing is terminated, and the previous panel is displayed. Action Check to make sure that:

The library containing GDDR load modules is APF-authorized.

GDDRICQU has been included in the authorized called program list in the

SYS1.PARMLIB IKJTSOxx member.If unable to resolve the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDI998E

Cause A program error has occurred in a GDDR program. The program name, error code andprogram line number are given. If source is available, the program source line is shown in asecond message line. The program returns the error code to its caller. The callerdetermines the appropriate action to take, and issues indicative messages. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDI999E

Cause An error has occurred which appears to be a GDDR program error.

msg

Error encountered invoking command queue interface program, rc rc

GDDR gddr_program trapped an error, rc rc, in lineline_no:[SOURCELINE(source_line)]

INTERNAL ERROR: CALL TECH SUPPORT-ID = error_identifier


Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDI999I

Cause You attempted to delete the only remaining entry in the list. This is not allowed. Action None.

Last (or only) entry cannot be deleted


CHAPTER 4 GDDRMAIN Messages (GDDM) GDDM000I

Cause This message ID is reserved for diagnostic messages The message text is variable. Action None.

GDDM001E

Cause An error has occurred on an operation to the DIV dataset used by the GVT subtask ofGDDRMAIN. The message gives the return and reason codes from the operation. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM002I

Cause A task is beginning initialization. Action None.

GDDM003W

Cause The GVT subtask of GDDRMAIN attempted to do a hot start, but found that the dataspace did not contain any data. This is normal on the initial start of GVT when GDDRMAINis started. Action None.

GDDM004W

Cause The indicated activity is attempting to set the update lock but was unable to do so. Thismessage indicates that the attempt to get the lock is being retried.

message-text

Error on DIV action Return code rc Reason code rs

task initialization beginning

Data space not initialized, hot start impossible

activity retrying update lock


●

●

●

Action None.

GDDM005W

Cause The indicated activity has attempted to get the update lock but was unable to do so. Thismessage is preceded by instances of message GDDM004W. The activity is forcing thelock. Action Typically no action is necessary. However, if this situation occurs frequently, contact theDell EMC Customer Support Center.

GDDM006E

Cause The indicated structure (data space or DIV) has been analyzed and found to be unsound. The message gives a code indicating the exact nature of the failure. As a result of thisfailure, the indicated action cannot be taken. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM007I

Cause This message indicates the type of start the GVT subtask of GDDRMAIN is doing. Possible start values are:

HOT means that the GVT subtask has restarted with data already in the global

variable data space

WARM means that the data (if any) in the data space was not usable, but the data

space is being reloaded from the DIV

COLD means that neither the data space not DIV contain usable data and both are

being initialized. Action None.

GDDM008W

Cause The GVT subtask of GDDRMAIN attempted to do a warm start, but found that the DIVdataset did not contain any data. This is normal on the initial start of GVT after the DIVhas been defined or redefined. Action None.

activity forcing update lock

structure corrupted (code), action

start in progress

DIV dataset not initialized, warm start impossible


GDDM009E

Cause During initialization of the GVT subtask of GDDRMAIN, the GVT subtask was unable towrite to the DIV dataset. The GVT task terminates. Action This message is preceded by either message GDDM013E or GDDM015E which give thecause of the error. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for technical assistance. Make sure you have all relevant jobdocumentation available.

GDDM010I

Cause This message is issued during GDDRMAIN initialization to indicate the Workload AssistMonitor (WLAM) is fully initialized and ready for use. Action None.

GDDM011I

Cause The indicated activity is beginning shutdown processing. Action None.

GDDM012I

Cause The indicated activity has completed shutdown processing. Action None.

GDDM013E

Cause The storage used for global variables has exceeded the capacity of the DIV and thestorage cannot be written to the DIV. Action Stop the GVT subtask; but do NOT stop GDDRMAIN. At your earliest convenience, stopall GDDR processing (EVM, HBM, scripts, on-line updates, and so forth) and run theGDDRGVX utility with DSPSAVE. Define a new DIV dataset with larger capacity and reprothe output dataset of GDDRGVX to it. Then either change the GDDRMAIN JCL to point tothe new DIV dataset and restart GDDRMAIN or stop GDDRMAIN, rename the old DIVdataset to something else, rename the new DIV dataset to the name of the old DIV, and

Unable to write DIV dataset, terminating

WorkLoad Assist Monitor (WLAM) Initialization complete

activity Shutdown beginning

activity Shutdown complete

DIV dataset allocated capacity exceeded, DIV not written


restart GDDRMAIN.Alternatively (and preferably), if you have defined the DIV to GDDRMAIN via theGDDRPARM file, stop the GVT subtask of GDDRMAIN. Then define a new DIV datasetwith larger capacity and repro the existing DIV into the new one. Modify the GDDRPARMfile to point to the new DIV dataset and restart the GVT subtask. There is no need tointerrupt any GDDR processing to do this.

GDDM014W

Cause The storage used for global variables has exceeded the threshold (80%) of the capacity ofthe DIV. Action None is required. However, you should consider enlarging the DIV dataset at your earliestconvenience. To enlarge the DIV, stop all GDDR processing (EVM, HBM, scripts, on-lineupdates, etc.) and stop GDDRMAIN. Define a new DIV dataset with larger capacity andIDCAMS REPRO the old DIV dataset into it. Then either change the GDDRMAIN JCL topoint to the new DIV dataset and restart GDDRMAIN or rename the old DIV dataset tosomething else, rename the new DIV dataset to the name of the old DIV, and restartGDDRMAIN.Alternatively (and preferably), if you have defined the DIV to GDDRMAIN via theGDDRPARM file, stop the GVT subtask of GDDRMAIN. Then define a new DIV datasetwith larger capacity and IDCAMS REPRO the existing DIV into the new one. Modify theGDDRPARM file to point to the new DIV dataset and restart the GVT subtask. There is noneed to interrupt any GDDR processing to do this.

GDDM015E

Cause An error has occurred writing to the DIV dataset. The message gives the return code andreason code from the DIV SAVE operation. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM016I

Cause An abend has occurred in a routine holding or using a lock. The lock has been released bythe ESTAE exit routine. Action None.

GDDM017I

Cause An abend has occurred in the GVT subtask of GDDRMAIN and the ESTAE exit routine isattempting to write out to the DIV dataset before the subtask terminates.

DIV Utilization is utilization%

Error writing DIV, return code rc, reason code rs

lock released by task recovery routine

Emergency DIV write beginning


Action None.

GDDM018I

Cause An abend has occurred in the GVT subtask of GDDRMAIN and the ESTAE exit routine hascompleted writing out the DIV to the extent that it can do so. Action None.

GDDM019W

Cause GDDRMAIN is shutting down and has posted the indicated subtask to end, but it has notended within one minute. GDDRMAIN will allow each subtask up to two minutes to end. Action None.

GDDM020I

Cause GDDRMAIN is shutting down and has posted subtasks to end, but they have not endedwithin two minutes. GDDRMAIN will proceed with shutdown and detach the subtasks. Action None.

GDDM021W

Cause GDDRMAIN is shutting down and either the GVT subtask was not active when shutdownbegan or the GVT subtask was unable to write the DIV dataset. This message will befollowed by message GDDM054A. Action None.

GDDM022W

Cause The indicated GDDRMAIN subtask has ended unexpectedly. The subtask may or may notbe restarted by GDDRMAIN. Action None, but if GDDRMAIN does not restart the subtask, you may do so with an operatorcommand, as described in the GDDR Product Guide for your configuration.

GDDM023I

Emergency DIV write complete

Subtask task not ended

task Shutdown Proceeding

DIV dataset not written

Subtask task ended unexpectedly


Cause The indicated GDDRMAIN subtask has ended and been restarted automatically. Thesubtask may have ended due to abnormal conditions or because of a START or RESTARToperator command. Action None.

GDDM024E

Cause GDDRMAIN attempted to restart the indicated subtask, but encountered an error on theattach. The message gives the return and reason codes from the attach. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM025I

Cause The indicated subtask of GDDRMAIN ended and was not automatically restarted, eitherbecause it had reached the automatic restart limit (3 times in 5 minutes) or because it wasstopped with an operator command. Action None.

GDDM026I

Cause An abend has occurred and the ESTAE exit routine to GDDRMAIN has received control. Subtasks will be ended and an attempt will be made to write out the DIV. Action None.

GDDM027I

Cause Processing of the GDDRMAIN ESTAE exit is complete. Action None.

GDDM028E

Cause

Subtask task restarted

Error on restart of subtask task, return code rc, reason code rs

Subtask task not restarted

GDDRMAIN Emergency shutdown beginning

GDDRMAIN Emergency shutdown complete

GDDRGVT Failed to Initialize


The GVT subtask of GDDRMAIN failed to initialize. Global variables may be available (seemessages issued to GVT prior to this message), but updates to the variables will not besaved to the DIV. Action None.

GDDM029W

Cause GDDRMAIN was unable to create a token used to signal subtask EVM/HBM to stop. When GDDRMAIN attempts to stop EVM/HBM (either as a result of operator commandor on shutdown), it will not be able to signal it to stop. EVM/HBM will either have to becancelled or if shutdown is involved, it will be stopped when its shutdown times out. Action None.

GDDM030W

Cause An operator command was entered which is not valid. Action Correct the command and retry.

GDDM031E

Cause The indicated z/OS service returned an error. The message gives the return and reasoncodes.If the service is IKJEFTSR, a reason code of 00000038 means that the named function isnot in the AUTHTSF TSO parameters or the library containing the module is notauthorized. Other IKJEFTSR return and reason codes can be found in the IBMdocumentation for TSO programming services.

Unable to create subtask-name token

Command not recognized


Error on z/OS-service, return code rc, reason code rs●

Error on @EMCSRV CGTRIP: RC rc, RS rs [(reason-description)]●

Error on EMCSAI function_id, return code rc, EMCRC emcrc,

EMCRS emcrs, EMCRCX emcrcx

●

Error on IKJEFTSR function_id, return code rc, reason

code rs, abend code abend-code

●

Abend in module-name, code abend-code, reason reason●

Error on BCPii request, return code rc●

Error on BCPii request, for CPC cpc-name, return code rc●

Error on BCPii request, for LPAR lpar-name, return code rc●

Error on BCPii request, for subfunction subfunction, for

LPAR lpar-name, return code rc

●

Error on BCPii request, for CPC cpc-name and LPAR lpar-name,

return code rc

●


●

●

●

●

●

●

●

●

●

●

●

●

If the service is EMCSAI, a return code of 28 indicates that SCF is not active or the SCFconnector DD is incorrect. If the service is CGTRIP, reason description is displayed for known combinations of reasonand return codes as follows:

RC 8, RS 2 - no devices defined to ConGroup

RC 8, RS 3 - RDF-ECA syscall error

RC 8, RS 4 - suspend syscall error

RC 8, RS 5 - timeout waiting for trip to complete

RC 8, RS 9 - SAF authentication failure

RC 8, RS 11 - RDF-ECA window timeout

RC 8, RS 12 - trip aborted due to RESET command

RC 8, RS 13 - batch API process timeout

RC 8, RS 14 - non-trip related error

RC 16 - ConGroup not active

RC -1 - SCF not active

RC -16843010 - SRV PC interface not available

Action Contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant job documentation available.

GDDM032I

Cause The indicated GDDR module created a dataspace. The message gives the dataset nameand token-id of the dataspace. The ALET is the token associated with the dataspace and isassigned by z/OS when the dataspace is created. Action None.

GDDM033W

Cause The indicated subtask has not completed initialization after 2 minutes. GDDR will detachthe subtask. Action Determine the reason for the failure to initialize and restart the subtask.

GDDM034E

Cause A subtask manipulation operator command was entered, but the name of the subtask inthe command was not valid. Action Correct the operator command and retry.

Dataspace dsname created by module-name, ALET=token-id

Subtask task stalled. Detaching

Subtask not found


GDDM035E

Cause A subtask manipulation operator command to stop, restart, or cancel a subtask wasentered, but the subtask is not running. Action Cancel the operator command and retry.

GDDM036E

Cause A subtask manipulation operator command to start a subtask was entered, but the subtaskis already running. Action Correct the operator command and retry.

GDDM037E

Cause A subtask manipulation operator command was entered, but the name of the subtask inthe command was not present. Action Correct the operator command and retry.

GDDM038E

Cause A subtask manipulation operator command was entered, but the name of the subtask inthe command was not valid. Action Correct the operator command and retry.

GDDM039I

Cause A z/OS STOP command was issued for GDDRMAIN. Shutdown processing will beginforthwith. Action None.

GDDM040E

Cause

Subtask not running

Subtask already running

No subtask name supplied

Invalid subtask name

Stop command received

GDDRVAL unable to obtain update lock


The GDDRVAL function was called to update global variables, but the routine was unableto obtain the update lock. No update was done. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM042W

Cause The indicated lock is being locked, but the use count is not zero. The routine waits untilthe use count is 0. Action None.

GDDM043E

Cause The indicated lock is being locked, but the use count is not zero and has not gone to zeroduring the wait period. Action None.

GDDM044E

Cause An attempt is being made to increment the use count of the indicated lock, but the lock isset and has not cleared during the wait period. Action None.

GDDM045W

Cause An attempt is being made to unlock the indicated lock, but it was not locked. Thisindicates a logic error or a lock that was forced. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM046W

Cause An attempt is being made to decrement the use count of the indicated lock, but the usecount was found to be negative. This indicates a logic error or a lock that was forced.

lock lock, waiting for use count

lock lock, timeout waiting for use count

lock lock, timeout waiting for lock

lock lock, unlock and not locked

lock lock, use count negative


Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM047W

Cause An attempt is being made to decrement the use count of the indicated lock, but the usecount was found to be zero. This indicates a logic error or a lock that was forced. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM049I

Cause During a reindex of the global variables, it was determined that the index needed to bewidened. Action None.

GDDM04IE

Cause The GDDRVAL function was called to update global variables, but the routine was unableto obtain any storage in the global variable data space. No update was done. Action If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDM052E

Cause A reindex operation failed. This indicates a logic error or index lock failure. Action If you cannot correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDM053I

Cause A TASKS console command was entered. This is the response listing each subtask of

lock lock, use count zero

Density changed to density

GDDRVAL global variable storage space exhausted

Reindex failure

Subtask Statustask-name status rc


GDDRMAIN and its status. If the status is ended, the return code is also given. Action None.

GDDM054A

Cause A shutdown of GDDRMAIN has completed without the GVT subtask writing out the DIV. This WTOR affords you an opportunity to save the contents of the global variable dataspace if you wish/need to do so. Action You may run GDDSPSAV from hlq.GDDRvrm.SAMPLIB to save the data space to asequential file. When you have either run this job or decided that you do not need to runit, reply with any character to allow GDDRMAIN to end.

GDDM055I

Cause A console command was entered to cancel a subtask of GDDRMAIN. The subtask hasbeen cancelled. Action None.

GDDM056A

Cause The indicated type of start for the GVT subtask of GDDRMAIN is being requested. Thetype of start will either be WARM or COLD. This message is preceded by messageGDDM006E which indicates why a HOT (if the message says WARM) or WARM (if themessage says COLD) cannot be done. Action You may reply E or END to cause the GVT subtask to end without taking any action. Thisis appropriate if you think you can affect some repair which will remove the cause ofmessage GDDM006E. If not, you can reply W or WARM, if the message says WARM, or Cor COLD, if the message says COLD. If the message says WARM and you reply W, thecontents of the global variable data space will be replaced from the DIV dataset. If themessage says COLD and you reply C, the data space and DIV will be reinitialized and allexisting global variables will be deleted.

GDDM057I

Cause The GVT subtask of GDDRMAIN is attempting to determine the capacity of the DIVdataset. While it does this, message IEC070I will probably appear multiple times. This isnot an error and the IEC070I messages should be ignored. Action Ignore the IEC0701 messages.

Reply anything to terminate GDDRMAIN

Subtask task canceled

Confirm start start

DIV access beginning, expect IEC070I messages


GDDM058W

Cause The indicated lock has been set for over 5 seconds. The lock may be "stuck". Action Use the GDDRGVX utility or the LOCK command to investigate and if necessary, free thelock manually. Refer to the GDDR Product Guide for your configuration.

GDDM059E

Cause During validation of the global variable data space, the GVT subtask found an error withthe variable at the indicated address. This message is followed by message GDDM006Egiving the nature of the problem. Action If you cannot correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDM060E

Cause A LOCK command was issued, but the name of the lock was invalid or the requested actionwas invalid. Action Correct the command and retry.

GDDM061I

Cause A LOCK command was issued, and the requested lock status is displayed. If the status isSET or PENDING, a second line is displayed with the job name and ID of the locker and theelapsed time since the lock was set. If the status is IN USE or PENDING, a second/thirdline is displayed giving the elapsed time since the last change in the shared lock. Action None.

GDDM062I

Cause A LOCK command was issued with CLEAR and the indicated lock has been cleared. Action None.

Exclusive lock lock may be stuck

Global Variable error at address

Invalid lock lock

lock, lock is status Set by jobname (jobid) ss.th seconds ago Last change in use ss.th seconds ago

lock lock cleared


GDDM063E

Cause A subtask manipulation operator command to stop or cancel a subtask was entered, butthe subtask may not be stopped. Action None.

GDDM064E

Cause A start command (or job submission) was issued to start GDDRMAIN, but GDDRMAIN wasalready active. The message gives the GDDR instance and the jobname and jobid of theGDDRMAIN task which is already active. Action None.

GDDM065E

Cause The indicated parameter for the indicated system and GDDR instance was not found inthe GDDRPARM file. Action Supply the parameter and retry.

GDDM066I

Cause The DIV dataset used by GDDRMAIN was allocated with a DD statement in theGDDRMAIN JCL. This means that the GVT subtask will not be able to deallocate the DIVin the event that should be desirable (such as handling the situation when the DIV fills upor is close to filling up). Action None. If you want to retain the ability to deallocate the DIV so that it can be enlarged in a non-disruptive fashion, remove the DD statement from GDDRMAIN and use the GDDRPARMfile to convey the DIV dataset name to GDDRMAIN.

GDDM067E

Cause A service was requested which requires the GDDRMAIN job to be running, but theGDDRMAIN address space was not active. Action

Subtask not stoppable

GDDRMAIN already active for system-name, Job jobname (jobid)

No parameter-name parm found for system system-name, GDDR gddr-instance

DIV Pre-allocated

GDDRMAIN not active


●

●

●

●

Start the GDDRMAIN started task and retry. GDDM068I

Cause A service was requested (such as global variable access) which requires that theGDDRMAIN started task created a data space. GDDRMAIN was started without a dataspace, hence the service request cannot be completed. Action Restart GDDRMAIN with a data space.

GDDM069E

Cause SCF is not running, or the nnnn in your SCF$nnnn DD DUMMY does not match your SCFsubsystem name. Action Start SCF, or correct the nnnn in your SCFnnnn DD DUMMY to match your SCFsubsystem name, and retry. The default SCF subsystem name is 'EMC', in which case theSCF$nnnn DD DUMMY is optional.

GDDM071I

Cause This message lists the applied PTFs for the specified module. The PTF list is in the form of3-digit numbers separated by commas. If no PTFs are applied, 'none' is indicated. Action None.

GDDM072I

Cause This message indicates the maintenance level of the address space where the messagewas issued, including the following:

GDDR version

The highest PTF number amongst all load modules

The latest build date amongst all load modules

CRC of maintenance level of all load modules Action None.

GDDM073I

No Data Space available

SCF is not active

module, affected PTFs: ptflist

GDDR maintenance level: version highest_ptf (latest_date) [CRCcrc]

GDDR maintenance level {upgraded|downgraded} from prev_versionprev_highest_ptf (prev_latest_date) to curr_versioncurr_highest_ptf (curr_latest_date)


●

●

●

●

●

●

●

●

●

●

●

●

Cause GDDRMAIN had previously been running since the system was last IPLed, and amaintenance level upgrade or downgrade was detected. The message text includes thefollowing:

Previous GDDR version

Previous highest PTF number

Previous latest build date

Current GDDR version

Current highest PTF number

Current latest build date Action None.

GDDM074I

Cause The maintenance level of the address space where the message was issued matches thatof GDDRMAIN. This is expected. Action None.

GDDM075E

Cause A GDDR maintenance level mismatch was detected between the address space where themessage was issued and the GDDRMAIN address space. The message text includes thefollowing:

The GDDR version for this address space

The highest PTF number for this address space

The latest build date for this address space

The GDDR version for the GDDRMAIN address space

The highest PTF number for the GDDRMAIN address space

The latest build date for the GDDRMAIN address space Action Determine the correct maintenance level, and ensure all GDDR address spaces are runningwith the correct libraries and have been recycled since maintenance was last applied. Ifany GDDR libraries have been added to LNKLST, LLA must be refreshed when GDDRmaintenance is applied. In addition, if any GDDR modules have been added to LPA, thosemodules must also be refreshed. To determine the mismatching module(s), compare themodule-level maintenance report (message GDDUG33I) in SYSPRINT betweenGDDRMAIN and the address space where the GDDM075E message was issued.

GDDM076E

GDDR maintenance level matches GDDRMAIN address space

GDDR Maintenance level mismatch - addr_space_versionaddr_space_highest_ptf (addr_space_latest_date) vs. GDDRMAIN:gddrmain_version gddrmain_highest_ptf (gddrmain_latest_date)

GDDR version mismatch - addr_space_version addr_space_highest_ptf(addr_space_latest_date) vs. GDDRMAIN: gddrmain_version


●

●

●

●

●

●

Cause A GDDR version mismatch was detected between the address space where the messagewas issued and the GDDRMAIN address space. The message text includes the following:

The GDDR version for this address space

The highest PTF number for this address space

The latest build date for this address space

The GDDR version for the GDDRMAIN address space

The highest PTF number for the GDDRMAIN address space

The latest build date for the GDDRMAIN address space Action Determine the correct maintenance level, and ensure all GDDR address spaces are runningwith the correct libraries and have been recycled since maintenance was last applied.

GDDM077E

Cause A GDDR maintenance level mismatch was detected between the address space where themessage was issued and the GDDRMAIN address space. This message follows messageGDDM075E or GDDM076E. Action Determine the correct maintenance level, and ensure all GDDR address spaces are runningwith the correct libraries and have been recycled since maintenance was last applied.

GDDM080E | GDDM080W

Cause The indicated DD statement was not found in the JCL. Action Add the indicated DD statement to the appropriate JCL, and retry.

GDDM081I

Cause GDDRMAIN debugging has been enabled (ON) or disabled (OFF). Action None.

GDDM082I

Cause GDDRMAIN tracing has been enabled (ON) or disabled (OFF). Action None.

gddrmain_highest_ptf (gddrmain_latest_date)

**** Results are unpredictable, resolve maintenance level mismatchand retry ****

ddname DD statement not found

Debugging set to {ON|OFF}

Tracing set to {ON|OFF}


GDDM083I

Cause GDDRMAIN verbose messaging has been enabled (ON) or disabled (OFF). Action None.

GDDM084I

Cause Syscall tracking in GDDR scripts has been enabled (ON) or disabled (OFF). Action None.

GDDM088I

Cause The GDDRMAIN trace setting has been saved, or it has been restored to the previouslysaved value, as specified in the message. Action None.

GDDM089I

Cause The GDDR trace has been reset by initializing the pointers in GDDR data space 2 to thebeginning of the trace buffer. The pointers before and after the operation are indicated inparentheses for diagnostic purposes. Action None.

GDDM090E

Cause A RELOAD command was issued, but a previous reload is still in progress. The inactive setof interface modules appear to still be in use. Diagnostic information is provided for DellEMC use. Action Reissue the command. Contact Dell EMC ?ustomer ?upport if the problem persists.The RELOAD command may be issued with the force option to circumvent this error;however, this could result in abend(s) if in fact the previously loaded modules are still inuse.

GDDM091E

Verbose messaging set to {ON|OFF}

Syscall tracking set to {ON|OFF}

Trace setting {saved|restored}

GDDR Trace buffer pointers reset (old_pointers -> new_pointers)

Reload already in progress (gddrpcr1-dword/gddrpcr2-dword)


Cause A null command was entered. Action Correct and reissue the command.

GDDM092E

Cause Command options were specified without a command verb. Action Correct and reissue the command.

GDDM093E

Cause The specified parameters are mutually exclusive. Action Correct and resubmit the command or job.

GDDM094E

Cause The specified parameter or combination of parameters is invalid. Action Correct and resubmit the command or job.

GDDM095E

Cause The specified command is missing the action to perform. Action Correct and reissue the command.

GDDM100E

Cause GDDR initialization detected a mismatch on the IP address for the local system. The IPaddress you specified in COMM or DRTCOMM statements in the GDDRPARM file for thesystem do not match the IP address returned by the TCP/IP GETHOSTID function. Action For the indicated system, either change a COMM record for that system in theGDDRPARM file or supply an additional COMM statement for the system that uses the IPaddress returned by GETHOSTID, as shown in the message. You will need to make this

No command specified

Command verb not specified

parameter and parameter are mutually exclusive

Parameters ignored: parameters

command command action not specified

GDDRPARM COMM Record for system IP addr ip-address mismatches IPaddr ip-address from GETHOSTID


change to the GDDRPARM file on each of your systems, then restart the GDDRMAINCOMM task on each system in order to make the change effective.

GDDM101E

Cause At initialization of the COMM subtask of GDDRMAIN, no COMM parameter was found inthe GDDRPARM file for the current system. Action Add the COMM parameter and restart the communications subtask.

GDDM102E

Cause At initialization of the COMM subtask of GDDRMAIN, the TCP/IP service was found to beunavailable. Action Make TCP/IP available to GDDRMAIN and restart the COMM subtask.

GDDM103W

Cause The communications subtask of GDDRMAIN received a connection request from anunknown IP address and port. The connection is rejected. Action None, but you may want to investigate the origin of the connection request.

GDDM104E

Cause The attempt to send a unit of work to a remote system or site failed. The messageidentifies the TCP/IP function and error code. Action Investigate why the TCP/IP failure occurred and take corrective action.

GDDM105E

Cause The function was unable to obtain a control block for a unit of work to be sent to a C-System. The function fails. Action If you cannot correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

No COMM parm found for system system-name, GDDR gddr-instance

TCP/IP not available

Connection attempt from unknown host, IP address nnn.nnn.nnn.nnn,port nnnn

Error on work SEND to {system-name | site-id} function function-id, code error-code

Unable to obtain work control block


GDDM106E

Cause An internal error has occurred in the module indicated in the message. Processing of themodule is terminated. Action If you cannot correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDM107E

Cause In loading the table of message IDs to be intercepted by GDDRMAIN, it was discoveredthat the entries in the table are out of order. This prevents the table from being loaded. The message interception subtask will not be able to intercept messages of interest in thiscase. Action When a new message table load module (GDDRMMSG) is received, install it in the GDDRsteplib and restart the MCSOPER subtask of GDDRMAIN. Contact the Dell EMCCustomer Support Center for assistance.

GDDM108E

Cause In loading either the table of message IDs to be intercepted by GDDRMAIN or the table ofmessage texts, it was discovered that the table is larger than the area reserved for thetable by GDDRMAIN. The table cannot be loaded. This means that either messageinterception will not be active or message text will not be able to be retrieved. Action If a new table load module (GDDRMTXT or GDDRMMSG) is received, install it in theGDDR steplib and restart the MCSOPER subtask of GDDRMAIN or retry the message textload. Otherwise, a restart of GDDRMAIN may be required if the size of the table area hasto be increased. Contact the Dell EMC Customer Support Center for assistance.

GDDM109E

Cause A response to a request was received by GDDRMAIN from another system, but theresponse is not valid. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM110E

Cause

Internal error in module-name

Message entries out of order

table-name table is larger then table area

Invalid response received

Invalid IP address or socket for system system-name, GDDR GDDR-instance


●

●

●

The GDDRPARM file contains an invalid COMM statement for the indicated system andGDDR instance or none is present when one is required. Action Correct the GDDRPARM file and restart the COMM subtask of GDDRMAIN.

GDDM111E

Cause During message interception, a message descriptor block (MDB) of unrecognized typewas encountered. Processing of the message is terminated. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM112E

Cause During message interception, the indicated message could not be processed for thereason given. Reasons could be one of the following:

NO WORK BLOCK AVAILBLE

NO DATA BLOCK AVAILBLE

EXCESSIVE MDBS Action Contact Dell EMC Customer Support.

GDDM113E

Cause During initialization of a GDDRMAIN worker task, the work queue for the indicated workfunction code could not be located. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM114E

Cause During processing of a work request, the indicated worker task received a unit of workwhose work function code is not supported by the worker. The unit of work is discarded. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM115E

Cause During processing of the indicated message, the message processing routine generatedthe indicated return code indicating processing was not successful. This message may be

Unknown MDB type (MDB-type) encountered, message discarded

Unable to process message message-id: reason

Unable to locate work queue for work code work-code

Worker worker-name received unsupported work code work-code

Error processing message message-id, return code rc


●

●

●

●

●

●

●

●

followed by GDDM116E and GDDM117E if additional information is available. Action Contact Dell EMC Customer Support.

GDDM116E

Cause See message GDDM115E. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM117E

Cause See message GDDM115E. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM118E

Cause The indicated worker received a work block which is invalid for the reason stated. Thereason could be one of the following:

NO MESSAGE ID

INVALID MESSAGE ID

NO COMMAND

INVALID ARGUMENTS

NO WORK ID

INVALID WORK ID

NO INPUT DATA

NO MODULE NAME Action Contact the Dell EMC Customer Support Center for assistance.

GDDM119E

Cause The function was unable to obtain a data block for a unit of work to be sent to a C-system. The function fails. Action Contact Dell EMC Customer Support.

GDDM120E

Error error1 error2

Error error1

Worker worker-name received invalid work block - reason-description

Unable to obtain work data block


Cause An address space started by GDDRMAIN was unable to retrieve the address spaceparameter which should be passed to it by GDDRMAIN. The address space terminates.This can be caused by manually starting a GDDR address space (such as GDDREVM,GDDRHBM, or GDDRWORK) manually instead of via GDDRMAIN command. Action If the problem was not caused by manually starting a GDDR address space, contact theDell EMC Customer Support Center for assistance.

GDDM121E

Cause A worker started to execute REXX execs under the TMP was unable to open the SYSTSINDD for output. The worker terminates. Action Make sure the SYSTSIN DD in the GDDRWORK proc is allocated to a dataset which canbe opened for output by GDDRMWXR. If you are unable to correct the problem, contactthe Dell EMC Customer Support Center for assistance.

GDDM122E

Cause A work request with the indicated code could not locate a work queue for that code. Thework request is terminated. Action If this message occurs before message GDDM010I, GDDRMAIN Initialization complete, itcan safely be ignored. In all other cases, contact the Dell EMC Customer Support Centerfor technical assistance. Make sure you have all relevant job documentation available.

GDDM123A

Cause A work request to run a REXX exec has exceeded the time allotted to it to finish. You maychoose to continue to wait for completion or terminate the wait. This WTOR is issued inconjunction with message GDDM124I. Action Reply with a number of minutes to continue waiting or reply 0 to stop waiting andterminate. If you enter a non-zero number of minutes and the exec still has notterminated, you will receive this message again.

GDDM124I

Cause A work request to run a REXX exec has exceeded the time allotted to it to finish. If

Unable to obtain valid address space parm

Unable to open SYSTSIN for output

Unable to find worker for work code work-request-code

Enter number of minutes to wait (0 to end now)

main Remote command command to site-id timed out. (no-of-retries) Running for hh:mm:ss.th in worker worker-name To continue to wait, enter a number of minutes To stop waiting, enter 0


●

●

●

execution of the exec has begun, the time it has been in execution and the name of theworker running it are displayed. This message is issued in conjunction with WTORGDDM123A. Note that the second line may or may not appear in the message, dependingon whether or not the work has begun execution. Action Reply to GDDM123A.

GDDM125W

Cause A WORKER parameter in the GDDRPARM file was found which is invalid. The parameterstatement is displayed in the message and is ignored by the WORKMGR subtask ofGDDRMAIN. Action Correct the parameter statement and restart the WORKMGR task.

GDDM126E

Cause During WORKMGR initialization, a worker of unknown type was encountered and couldnot be started. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM127I

Cause A COMM console command was entered. This is the response listing each system withwhich GDDRMAIN can communicate. The display shows each system name, site if thesystem is a C-system, the IP address (in the form of nnn.nnn.nnn.nnn for IPv4 and nnn.nnn.nnn.nnn.nnn.nnn.nnn.nnn for IPv6) and port (in the form of nnnn), and the lasttime that communication occurred with the system.If a COMM, system command was entered, detail is shown of all communications data forthat system.In the detail lines:

DRT indicates the data is from a DRTCOMM statement.

COM indicates the data is from the first encountered COMM statement for that

system.

ALT indicates the data is from a subsequently encountered COMM statement.Both send and receive IP addresses are shown. For DRT systems, the site and time of lastcommunication are also shown. Action None.

Invalid parm ignored - invalid-worker-parameter

Unknown worker type

Communications StatusSys system-name (site-id), IP ip-address,port Lastmm/dd/yy hh:mm:ss.thSys system-name , IP ip-address,port Last mm/dd/yy hh:mm:ss.thDRT site-id IP ip-address,port Last mm/dd/yy hh:mm:ss.thSend ip-address, Recv ip-addressSys system-name not found


GDDM128I

Cause A WORKER console command was entered. This is the response listing each worker typewith subtask or address space indicator (S/A), number of such workers active, and theminimum and maximum number. For each worker type with active workers, an additionalline is displayed for each active worker showing its name and status (INITING, WAITING,or RUNNING). If the worker type is address space (A), the worker job name and job ID arealso shown. Action None.

GDDM129E

Cause A WORKER console command was entered. The command was invalid for one of thefollowing reasons: The worker name was invalid or non-existent. The last operand(MIN/MAX) was not valid (must be 1 or more). Action Correct the command and retry.

GDDM130I

Cause A MESSAGES console command was entered. This is the response listing each message IDwith enabled or disabled indicator (E/D), number of interceptions (I) and date/time of lastinterception, and number of times the message was processed (P) and date/time it waslast processed. Action None.

GDDM131E

Cause A MESSAGES console command was entered. The command was invalid for one of thefollowing reasons: The message ID was invalid or non-existent. The last operand(ENABLE/DISABLE) was not valid. Action Correct the command and retry.

GDDM132W

Worker Status worker-subtask-type Type INT | ext, Act nnn, Min nnn, Max nnnName worker-name Status worker-status - jobname (jobid)

Invalid WORKER command

Message Statusmsgid (E | D) I:intercept-countlast-intercept-time, P:processed-countlast-processed-time

Invalid MESSAGES command


●

Cause A worker task ended unexpectedly, causing the work manager to reset the minimumnumber of such workers to 1. Action None required, but you should investigate why the worker ended and take correctiveaction.

GDDM133E

Cause GDDRMAIN was unable to load the message text (GDDRMTXT). The return code givesthe reason.Values for the return code include:

8 — Internal error in GDDRLTXT (the loaded message count did not match count in

load module). Action Investigate why the message text could not be loaded.

GDDM134E

Cause A subtask cancel operator command was entered, but a stop command for the subtaskhad not been previously entered. Action You must issue a stop command for a subtask before you can enter a cancel command. Issue a stop command and if that is not productive, reissue the cancel command.

GDDM135E

Cause GDDR software tried to issue a message with the ID given in the message, but the textwas not found. Up to the first three text substitutions specified are also displayed. Action Try to reload the message text to see if that resolves the problem. If not, contact the DellEMC Customer Support Center for assistance.

GDDM136E

Cause GDDR software tried to issue a message but did not pass a message ID. This is an internalerror in the GDDR software. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM137E

Worker worker-subtask-name ended, minimum reset to 1

Unable to reload message text, return code rc

Subtask not previously stopped

MESSAGE ID message-id NOT FOUND; text-string1,text-string2,text-string3

GDDRMSGT ERROR - NO MESSAGE ID PASSED


Cause GDDR software tried to issue a message but the message text retrieval routine wasunable to establish an ESTAE. This is probably an environmental error. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM138E

Cause GDDR software tried to issue a message but the message text retrieval routine wasunable to locate the message text and was unable to load the message text. This isprobably an environmental error. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM139E

Cause The indicated command was entered, but included an operand which is invalid for thecommand. Action The command was not executed. Correct the command and retry it.

GDDM140I

Cause An MPARM console command was entered. This is the response listing each system withwhich GDDRMAIN can possibly communicate. The display shows each system name, theidentifier of the GDDRPARM data in use, the identifier of the contents of the GDDRPARMfile, and whether or not the system has found different GDDRPARM data from othersystems. If GDDRMAIN cannot communicate with the system, the Unable tocommunicate text is displayed. Action None.

GDDM141E

Cause An MPARM,CHECK console command was entered or GDDRMAIN was attempting toautomatically reset consistency, but consistency could not be set for the reasons given. Action Use the MPARM and COMM commands to identify the problem and correct the

GDDRMSGT ERROR - UNABLE TO ESTABLISH ESTAE

GDDRMSGT ERROR - NO MESSAGE TEXT AVAILABLE

Invalid operand on command command

Format 1:

Consistency Status Sys system : MPARM current-gddrparm-file,Dataset dsname, Subsys subsystem Consistency {Y|N}Format 2:

Consistency Status Sys system : ******Unable to communicate******

Inconsistency detected, reason1 reason2 reason3


●

●

GDDRPARM file or the GDDR subsystem on the offending system. Then retry thecommand.

GDDM142I

Cause Consistency has been reset either locally or globally (meaning on all available systems),either because an MPARM,CHECK command was entered or because GDDRMAIN hasdetected that consistency has been achieved. Action None.

GDDM143W

Cause Inconsistency between the system on which this message is issued and the indicatedsystem has been detected. Either there is an inconsistency in GDDRPARM or GDDRsubsystem usage. This is a serious situation which impacts the ability of GDDRMAIN tocommunicate with all C-systems and production systems. Action Determine the cause of the inconsistency.

If the cause is differing GDDRPARM data, propagate a valid GDDRPARM file to all

systems and restart the COMM subtask in all instances of GDDRMAIN.

If the cause is differing GDDR subsystem usage, change the JCL used to run

GDDRMAIN so that all system use the same GDDR subsystem. The GDDR subsystem

is indicated by a GDD$nnnn DD statement, where nnnn is the GDDR subsystem

name. GDDM144W

Cause A difference has been detected between the contents of the GDDRPARM file and thevalues in use by the COMM subtask of GDDRMAIN. Action If the difference is because a new GDDRPARM file is in the process of being propagatedbut has not yet been activated, ignore the message. Otherwise, either restore thecontents of the GDDRPARM file from another system so that the dataset will be in synchwith the data being used or restart the COMM subtask so it will load the data from theGDDRPARM file. You can use the MPARM command to determine the GDDRPARMcontents compared with that of other systems.

GDDM145I

Cause A BROADCAST command was issued, and as a result the command operand has beensent to the indicated system. Note that this does not mean that the command wasreceived and processed on that system, only that it was sent. If GDDRMAIN or the COMM

Consistency set {locally|globally}

Inconsistency detected with system system-name

GDDRPARM file does not match data in use by GDDRMAIN

Command sent to system system-name


●

●

subtask is down on that system, the command will not be received or executed. Also, inrare circumstances, other conditions could prevent the command from being executed onthe remote system. Action None.

GDDM146E

Cause A BROADCAST command was issued, and an error occurred sending the command to theindicated system. The text gives the reason:

Unable to get Work Block

Unable to get Data BlockBoth of these indicate that sufficient resources to send the command were not available. Action Retry the command. If the problem persists, contact the Dell EMC Customer SupportCenter for assistance.

GDDM147E

Cause A BROADCAST command was issued, but no systems were found which matched thesystems to be sent to. Action Use the COMM or MPARM command to display a list of valid systems. The systemspecified must be one of those or a valid site or one of the following:* - send to all GDDR managed systems*C - send to all C-systems*P - send to all P-systems*1 - send to all GDDR systems, this system first*X - send to all GDDR systems except this system*Z - send to all GDDR systems, this system last

GDDM148E

Cause During the initialization of the COMM subtask of GDDRMAIN, two systems were found tohave the same IP address. Action Correct the IP address specification in the GDDRPARM file and restart the COMMsubtask.

GDDM149I

Cause GDDRMAIN is about to issue the indicated z/OS console command. The command isbeing issued either as a result of a message interception or because it was requested by a

Unable to send command to system system-name: reason

No matching systems found

Duplicate IP addresses for systems system1 and system2

Issuing command for {system system-name|message message-id} Jobjobname (job-id)


job. If the command is the result of message interception, the message ID which causedthe command is shown, along with the job name and ID of the message issuer. If thecommand is the result of a job (script) request or a broadcast command from GDDRMAINon another system, the originating system, job name and ID are shown. Action None.

GDDM150E

Cause The WORKMGR subtask has detected that the indicated worker type has failedrepeatedly in a short period of time. This means that the worker cannot execute andtherefore, GDDRMAIN will not be able to perform some work requested of it. GDDRMAINis therefore in a degraded state and this problem must be corrected as soon as possible. Action Correct the issues causing the worker to fail and reset the minimum and maximum for itusing the WORKER command.

GDDM151E

Cause A request to run work at the indicated destination (site ID or system), cannot be satisfiedbecause there are no workers of the indicated type at that location. Action Determine why there are no workers at the destination, correct the problem so that aworker is available, and retry.

GDDM152E

Cause A request is being made to add an element to the GDDR command queue by user. However, there are elements on the queue which belong to CMDQ-owner. This is notallowed. Only one process may have elements on the command queue at one time. Action Clear the command queue. You can use the Manage GDDR Internal Command Queue panelto display and delete command queue elements, or you can use the GDDRXCMD programto clear the queue.

GDDM153I

Cause During HBM initialization, a conflict in master C-system definition has been discovered. HBM stops EVM since it is also impacted by this condition. Action None.

Worker worker-subtask-type has repeatedly failed, maximum reset to0

No worker-name at {site-id|system-name}

Command queue conflict: CMDQ-owner has elements on the queue, usertrying to add

EVM stopped by HBM due to Master C conflict


●

●

●

●

●

GDDM154A

Cause During HBM initialization, a conflict in master C-system definition has been discovered andpreviously displayed in message GDDM157W. The user is being asked to resolve theconflict by entering the site which is the correct master C-system.The question being asked is which site is in fact serving as the master at this moment, notwhere the desired master should be. If the master C-system goes down and a mastertakeover occurs on another system, this message will probably appear when the originalmaster is restarted. In that case, you would enter the site which took over the master role,not the site which was the original master. Action Reply with the site of the correct master (DCn) or STOP to terminate HBM with nofurther action. The site you select must think that it is the master or the reply will berejected.

GDDM155I

Cause During HBM initialization, a conflict in master C-system definition has been discovered.HBM had previously stopped EVM (see message GDDM153I) and has now restarted EVMsince the conflict has been resolved. Action None.

GDDM156E

Cause During EVM or HBM initialization, a conflict in master C-system definition has beendiscovered. The conflict cannot be resolved for the reason given and the task is ending.Possible reasons are:

CURRENT MASTER C SYSTEM NOT DEFINED ON THIS SYSTEM: The system

where EVM or HBM is running does not have the master C-system defined. This

most likely means that EVM or HBM was started before a parameter load was done.

MORE THAN ONE MASTER C SYSTEM DEFINED: This applies to EVM only. If the

C-systems do not agree on who is the master C, EVM will not start and does not

attempt to resolve the conflict (HBM will attempt to resolve it).

ERROR UPDATING BROADCAST SET: The broadcast set of variables (state of

GDDR) was obtained from the master, but there was an error updating those

variables on the local system.

MORE THAN ONE MASTER AND NO REPLY TO WTOR: WTOR GDDM154A was

issued, but there was no response within 10 minutes and the conflict still exists.

MORE THAN ONE MASTER AND THIS SYSTEM IS NOT MASTER: The system

where HBM is running does not think it is the master C, but the other systems do not

agree on who the master is.

Reply with site which should be the Master (STOP to terminate HBM)

EVM restarted by HBM after Master C conflict resolution

subtask-name ending, reason


●

●

MORE THAN TWO MASTER C SYSTEMS DEFINED: There are more than two

different opinions of which system is the master C.

UNABLE TO GET BROADCAST SET FROM MASTER: A selection was made for a

master, but there was an error getting the broadcast set of variables (state of

GDDR) from that master. Action If appropriate, resolve the master C-system conflict by manipulation of each system andrestart HBM/EVM.If the error was UNABLE TO GET BROADCAST SET FROM MASTER, ensure that thereare free GDDWGV workers on the master C-system.If the error was ERROR UPDATING BROADCAST SET, contact Dell EMC CustomerSupport.

GDDM157W

Cause During EVM or HBM initialization, a conflict in master C-system definition has beendiscovered. The message lists each site (site ID and system), along with the system whichthat site thinks is the master C-system. Action If message GDDM154A or GDDM158I is not issued after this message, you need to takeaction to resolve the conflict.

GDDM158I

Cause During EVM or HBM initialization, a conflict in master C-system definition has beendiscovered. The conflict has been resolved by setting the master C on the current systemto the value indicated. Action None.

GDDM159I

Cause During EVM or HBM initialization, the set of global variables which describe the state ofGDDR is being retrieved from the master C-system. This may take a few seconds. Action None.

GDDM160I

Cause During EVM or HBM initialization, the set of global variables which describe the state ofGDDR has been successfully retrieved from the master C-system.

Inconsistent Master C system values:Site site-id (system): Master is master-C-system-name

Master C system set to system-name

Retrieving broadcast set from system-name

Broadcast set retrieved from system-name


Action None.

GDDM161W

Cause Degraded mode has been set on or off at the indicated system (which is the C-system atthe indicated site). Previously issued messages should indicate why this action wastaken. Action Investigate why this action was taken and possibly take corrective action.

GDDM162E

Cause An attempt was made to set degraded mode on or off on the indicated system (which isthe C-system for the indicated site). However, degraded mode could not be changed.This is generally because communication could not be accomplished with the indicatedsystem because it is down or GDDRMAIN is not running. Action Investigate why degraded mode could not be changed. If the system is down orGDDRMAIN is down on that system, no action is generally necessary.

GDDM163E

Cause A request to issue a z/OS console command was made, but the command could not beissued because the GDDR console name was not set. The console name is set by theMCSOPER subtask of GDDRMAIN. Action Determine if the MCSOPER subtask is active. If it is not active, start it. If it will not remainactive, or if the problem persists when MSCOPER is active, contact the Dell EMCCustomer Support Center for assistance.

GDDM164E

Cause During HBM initialization, HBM determined that EVM should be stopped. However, HBMis unable to issue the command to stop EVM because the GDDR console name is notset.Setting the GDDRMAIN console name is the responsibility of the MCSOPER subtask. Action Manually stop EVM as soon as possible. Restart EVM when HBM initialization issuccessful. Investigate why the GDDR console name is not set: Determine if theMCSOPER subtask is active. If it is not active, start it. If it will not remain active, or if theproblem persists when MSCOPER is active, contact the Dell EMC Customer SupportCenter for assistance.

GDDM165E

Degraded mode set {on|off} at system-name (site-id)

Unable to set degraded mode {on|off} at system-name (site-id)

Unable to issue command, Console name not set

HBM unable to stop EVM, Console name not set


Cause During MISC initialization, STORAGE OBTAIN for GDDRPARM DCB failed. Unable to loadHMC Interface information into Data Space 2. Action Restart the MISC task via MODIFY to GDDRMAIN.

GDDM166E

Cause During MISC initialization, the open for DDname GDDRPARM failed. DCB failed. Unable toload HMC Interface information into Data Space 2. Action Check the GDDRPARM file and restart the MISC task via the MODIFY command.

GDDM167E

Cause During MISC initialization, a GDDRPARM CPC record was read which contains a site IDdifferent from DC1, DC2, or DC3. Action Correct the GDDRPARM CPC statement and restart the MISC task via MODIFY.

GDDM168E

Cause During MISC initialization, a GDDRPARM CPC record was read which contains a CPCname whose total length (netid + '.' nau) is greater than the maximum allowable of 17characters. Action Correct the GDDRPARM CPC record and restart the MISC task via MODIFY.

GDDM169E

Cause During MISC initialization, a GDDRPARM CPC record was read which contains an HMCmethod other than BCPii or HWMCAAPI, which is invalid. Action Correct the GDDRPARM CPC record and restart the MISC task via MODIFY.

GDDM170W

GDDRMAIN MISC Task unable to obtain storage for GDDRPARM DCB.Return code=rc

GDDRMAIN MISC Task unable to open GDDRPARM DD for input. Returncode =rc

GDDRMAIN MISC GDDRPARM Input CPC record contains an invalid SiteID of site-id

GDDRMAIN MISC GDDRPARM Input CPC record contains a CPC Namegreater than 17 characters

GDDRMAIN MISC GDDRPARM Input CPC record contains an invalid HMCmethod of invalid-method-value


Cause During initialization of the MCSOPER subtask of GDDRMAIN, the MCSOCART subtaskcould not be attached. Message GDDM031E will have been issued giving details on thefailure to attach the subtask. Action None required. However, be aware that while GDDR can still issue console commands, theresponses to those commands will not be available. You can try to restart the MCSOPERsubtask to remedy the situation. If the problem persists, contact the Dell EMC CustomerSupport Center for technical assistance.

GDDM171W

Cause A command response was intercepted which could not be returned to the command issuerin its entirety. The reason could be excessive number of lines or excessive total messagelength. The command response will be truncated. GDDR processing of the command response will be incomplete because the completeresponse could not be made available. Action None.

GDDM172W

Cause During processing of SYMM statements in the GDDRPARM file by the WORKMGRsubtask of GDDRMAIN, a storage system was found which is connected via SRDF to thestorage system specified in the parameters. However, the indicated storage system is notspecified in the parameters. Action None required. The storage system indicated in the message will not be used by GDDR. Ifit should be used, update the GDDRPARM file to include it and restart WORKMGR.

GDDM175E

Cause During processing of SYMM statements in the GDDRPARM file by the WORKMGRsubtask of GDDRMAIN, the list of SRDF groups for the indicated storage system could notbe obtained. This should be preceded by a GDDM031E message giving the details of thefailure. Action No device workers will be started by WORKMGR because of this error, but WORKMGRinitialization will continue. Correct the GDDRPARM file and restart WORKMGR.

GDDM176E

Cause During processing of SYMM statements in the GDDRPARM file by the WORKMGR

Unable to attach MCSOCART, command responses will not be available

Unable to process entire command response, reason

Symm symm-serial not found in GDDRPARM

Unable to obtain complete list of RDF groups for symm symm_serial

Invalid SYMM statement: reason


subtask of GDDRMAIN, an invalid SYMM statement was detected. The message explainsthe error. For information about SYMM statement syntax, see the GDDR Product Guidefor your configuration. No device workers will be started by WORKMGR because of this error, but WORKMGRinitialization will continue. Action Correct the GDDRPARM file and restart WORKMGR.

GDDM177E

Cause During processing of GDDRPARM statements, an error was detected on a statement. Thestatement in error is displayed as the second line of the message. Action Take the action indicated by the message which follows giving the error.

GDDM178E

Cause During processing of a device request by the GDDRMAIN device worker, an erroroccurred. The possible reasons are: unable to find gatekeeper target or storage systemnot found. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM179W

Cause Errors occurred on GDDRPARM SYMM statements or there were no SYMM statements inthe GDDRPARM file. As a result, WORKMGR will not start any device workers. Action Correct the GDDRPARM statements and restart WORKMGR.

GDDM180I

Cause A BR (broadcast with response) command was entered. The message consists of multiplelines showing the response received (if any) from each system to which the command wassent. A response beginning with ">Error" indicates that there was an error sending thecommand to the system or an error in sending the response back to this system. Action None.

Error on GDDRMPARM statement: parameter-statement

Unable to process device request: reason

No device workers started, reason

BR Command Responses: system-name response: system-name did not respond >Error: error-description response-description


GDDM181E

Cause The GDDR Event Monitor or GDDR Hearbeat Monitor timed out trying to obtain thebroadcast set from the master C-system. The monitor waits one minute and retries. Ifafter fifteen retries the broadcast set cannot be obtained, monitor initialization fails witherror message GDDM156E.

Action Ensure that GDDRMAIN is active on the master C-system, including at least one GDDWGVworker. Also ensure that it is able to communicate with the C-system where the erroroccurred. The F GDDRMAIN,WORKER command may be used to display the active workers, and theF GDDRMAIN,CHecKup SYStems command may be used to identify any communicationissues between C-systems.

GDDM182W

Cause GDDRMAIN attempts to perform registration on each storage system located at the sitewhere GDDRMAIN is running. The request to register on the indicated storage systemcould not be done for the reason given. Action If the problem persists, contact the Dell EMC Customer Support Center for assistance.

GDDM183W

Cause The GDDR License Feature Code (LFC) could not be determined. The message gives thereturn and reason codes from the SCF license check service.

Action None required, but you should be aware that GDDR will check the license feature code andin future releases of SCF, this could cause GDDRMAIN to stop running if the LFC is notpresent.

GDDM185E

Timeout occurred retrieving broadcast set from master-c-system -waiting 1 minute before retrying (retry_num/15)

Unable to register GDDR on symm-serial: reason

Cannot determine GDDR license status (return-code reason-code)License code check for feature failed (return-code reason-code)

Return code Reason code Description

4 95 SCF is not active or the SCF connector DD is incorrect.

4 69 SCF possibly has not completed initialization.

4 71 The feature does not have a valid license key in SCF.

4 99 SCF is back-level and does not support the LFC feature.

8 68 The indicated feature does not require a license.

GDDR Console failure: reason


●

●

Cause The MCSOPER subtask of GDDRMAIN has received notification that its software consolehas been suspended. The message gives an explanation of the problem:

CONSOLE DATA SPACE EXHAUSTEDThe data space used to contain messages for the GDDRMAIN console has reachedcapacity.

CONSOLE QUEUE DEPTH REACHED Action If MCSOPER restarts, check for console messages of interest to GDDR which may nothave been intercepted. Manual processing may be required. If MCSOPER is not restarted,contact the Dell EMC Customer Support Center for assistance.

GDDM187W

Cause During processing of SYMM statements from the GDDRPARM file, configuration data forthe indicated storage system could not be obtained. Action There is apparently no one-hop path from any storage system at the site where thismessage occurred to the indicated storage system. If that is the case, no action isrequired, but the indicated storage system cannot be used by GDDR from this site.

GDDM188E

Cause GDDRWMGR issued ATTACH of GDDRMWXR rather than ASCRE to run subtask workerfor Command Queue PGM type. Passed address of WSCB may be bad as verify of EPNMin WSCB failed. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM189E

Cause Device action is being taken, and an unknown token has been returned from GDDRADEV. Action Contact the Dell EMC Customer Support Center for assistance.

GDDM190E

Cause Device action is being taken, but no submitted device actions are actually in execution.This probably indicates an unusual condition in the device workers in GDDRMAIN. Action Investigate the status of the device workers (GDDWDV) in GDDRMAIN. If there is acorrectable problem with them, correct it and rerun the script. If that is not possible,

Unable to obtain configuration data for Symmetrix symm-serial

Could not verify the Work Status Control Block passed via ATTACHof GDDRMWXR

Unknown token token-id returned

No device actions executing, cancelling all requests


contact the Dell EMC Customer Support Center for assistance. GDDM191E

Cause Device action is being taken, but the indicated command did not complete in a reasonabletime period. This indicates something is hindering the completion of the command. Action Investigate the status of the device workers (GDDWDV) in GDDRMAIN. See if there is anyindication in GDDRMAIN why the command is not completing. If not, contact the Dell EMCCustomer Support Center for assistance.

GDDM192I

Cause Device action is being taken, but the indicated command is being cancelled. This messageprovides a record of the non-completion of the command. Action Previous messages should indicate the reason for the cancellation.

GDDM193E

Cause Device action is being taken, but the indicated command did not succeed in placing thedevice into the desired state. The message gives the device number, the gatekeeper, andthe SRDF group involved. Action Determine why the action failed, correct the conditions and rerun the script. Or, manuallycomplete the action and rerun the script skipping the failing step. If the reason for thefailure cannot be determined, contact the Dell EMC Customer Support Center forassistance.

GDDM194E

Cause During MISC processing, a GDDRPARM master C-system record was read and acorresponding CPC/NETID record was not found in the GDDRPARM file. This message isissued by GDDRMTIM. Action A valid CPC record of the NETID type should be added to the GDDRPARM file and then aRESTART MISC performed to rebuild the CPC DS2 structures.

GDDM195E

Command number nnnnn timed out

Command number nnnnn cancelled

GDDRADEV command failed for device symdv#, gatekeeper gk, rdfgroup srdfgrp

*ERROR* GDDRPARM CPC/NETID record missing for CSYSSITE C System c-system-name.

*ERROR* BCPii Connectivity verification for C System c-system-nameto cpc-name has failed - RC(rc)


Cause During MISC processing, a GDDRPARM CPC record was found that specified BCPiiconnectivity for a C-system to a CPC. An attempt to verify that connectivity failed withthe specified return code information. This message is issued by GDDRMTIM. Action Verify that BCPii is available on the system GDDRMAIN is started on, that all requiredfacility classes have been defined, and that the CPC name is a fully qualified NETID.NAUformat CPC name as required by BCPii for connectivity requests.

GDDM196E

Cause During MISC processing, a load for one of the BCPii Service routines (HWICONN,HWIDISC) has failed. This is a serious error and could represent an attempt to run BCPii on a z/OS systemunable to process BCPii requests (that is, a system pre z/OS 1.11 or z/OS 1.10 without anAPAR required for BCPii support). Action Verify that z/OS is able to process BCPii requests.

GDDM197E

Cause During MISC processing, a fourth C-system CSYSSITE record has been encountered.Anything past three records is ignored and this error message is generated. Action Correct grouping of CSYSSITE records in the GDDRPARM file.

GDDM198E

Cause During MISC processing, an unknown BCPii error has occurred that requires research toidentify the problem. Action Check the job log and SYSLOG for any diagnostic messages that might help pinpoint theBCPii error encountered. Search the Knowledgebase on the Dell EMC Online Supportwebsite for applicable solutions relating to this message ID. If you cannot determine andcorrect the problem, contact the Dell EMC Customer Support Center for assistance. Makesure you have all relevant job documentation available.

GDDM199E

Cause During MISC processing, a GDDRPARM CPC record was found that specified BCPii

*ERROR* Unable to load BCPii routine {HWICONN | HWIDISC}. Couldnot verify BCPii connectivity

*ERROR* Too many C System CSYSSITE records are found in GDDRPARM:system at site-id.

*ERROR* An unknown error has been encountered in the RESTART MISCprocessing.

*ERROR* BCPii Disconnect verification for C System c-system-nameto cpc-name has failed - RC(rc)


connectivity for a C-system to a CPC. An attempt was made to verify that connectivitywas able to connect but then failed during disconnect processing. See return codeinformation. This message is issued by GDDRMTIM. Action Verify that BCPii is available on the system GDDRMAIN is started on, that all requiredfacility classes have been defined, and that the CPC name is a fully qualified NETID.NAUformat CPC name as required by BCPii for connectivity requests.

GDDM200W

Cause The indicated storage system serial number appears in the GDDRPARM file but has nohome site specified. Action Update GDDRPARM specification so that every storage system has a home site specified.

GDDM201I

Cause The indicated message ID (WTOR) was responded to from the console indicated in themessage. If that console is the software console of GDDRMAIN, "(GDDRMAIN)" isappended to the message. In that case, it means the WTOR was automatically replied toby GDDRMAIN, as opposed to manually replied to by other means. Action None.

GDDM202W

Cause Module GDDRPSYN was run to synchronize all parallel steps but no parallel process IDscould be found. Processing continues, but this condition should not occur and may indicate that parallelprocessing data has been destroyed. Action None.

GDDM203E

Cause Module GDDRPSYN was run to synchronize the indicated parallel process, but thatprocess is not defined. Processing stops. Action Determine why the requested parallel process ID is not found and take steps to restore it.

GDDM204W

Symmetrix symm-serial has no home site

Reply to message message-id made from console console-name[(GDDRMAIN)]

No Parallel id found

Parallel id nnnnnnnn is not defined


●

●

●

●

●

●

●

●

●

●

Cause Module GDDRPSYN was run to synchronize parallel processes, but the status of theindicated process is invalid. The current status is displayed. Processing continues. Parallel process status is updated as the work progresses, so thiscondition may correct itself. Action If the problem persists, the status will have to be investigated and manually changed.

GDDM205I

Cause The status of parallel processes is displayed.Status can be one of the following formats:

Submitted mm/dd/yyyy hh:mm:ss.th sss system

Received mm/dd/yyyy hh:mm:ss.th sss system worker wrkjid

Running mm/dd/yyyy hh:mm:ss.th sss system worker wrkjid

Completed nn mm/dd/yyyy hh:mm:ss.th sss system worker wrkjidWhere:

mm/dd/yyyy is the date the status was set.

hh:mm:ss.th is the time the status was set.

sss is the site to which the work was submitted.

system is the system to which the work was submitted (may or may not be present

for Submitted).

worker is the jobname of the worker which set the stat.

wrkjid is the jobid of the worker which set the status.The date and time and following data may display on a second line under the parallel id. Ifthe parallel id has subqueues associated with it, the subqueues are displayed following thestatus of the overall parallel task. Subqueue work can have an additional status of Queued,meaning the work has not begun execution.Subqueue work status information includes date and time and not site, system, worker orworker jobid. Action None.

GDDM206A

Cause Module GDDRPSYN was run to synchronize parallel processes. Not all processes arecomplete. Message GDDM205I has previously displayed the status of the work. Tocontinue to wait, do not reply. If no reply is made, parallel work continues to be monitored and will end when all work hascompleted. If a reply is made, the appropriate action will be taken. Action Possible replies are:

Parallel id nnnnnnnn has invalid status - status

Parallel status: nnnnnnnn - parallel-id-status parallel-id-status Sub subqueue - subqueue-status

Waiting for parallel work to complete


●

●

●

●

Q - Quit waiting and end with non-zero return code. This will cause script processing

to end at this point.

Z - Quit waiting and end with zero return code. This will cause script processing to

continue.

R - Resubmit any work which shows completed in error.

Rnnnnnnnn - resubmit the work with the given ID, without regard to the current

status of the work. GDDM207E

Cause Parallel work is being submitted, but an error occurred creating the variable whichcontains the information needed to identify that work. Action Contact the Dell EMC Customer Support Center.

GDDM208W

Cause Parallel work with the indicated ID has been submitted, but an error occurred updating thevariable which tracks its status. The status variable is updated every time the status changes, so this condition maycorrect itself. Action If the problem persists, a manual update may be required.

GDDM209W

Cause This message occurs in combination with GDDM208W. This message shows what thestatus would have been updated to. Action See message GDDM208W.

GDDM210E

Cause The parallel ID passed is invalid for the reason stated. Action Contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant job documentation available.

Unable to create INFO variable for parallel id nnnnnnnn

Unable to update status of parallel id nnnnnnnn on site-id

Status of nnnnnnnn is parallel-process-status

Invalid parallel id - no subqueue id: nnnnnnnnor

Invalid parallel id - subqueue not allowed: nnnnnnnnor

Invalid parallel id - no subqueues found: nnnnnnnn


●

●

●

●

GDDM211W

Cause In response to message GDDM154A, the operator entered a site which is not the mostrecent site to assume the master C-System role. This could mean that the other master C-System candidate is in fact performing the master role. This message is followed by WTORGDDO135A. Action Respond to WTOR GDDO135A.

GDDM212W

Cause The indicated task timed out (5 seconds) waiting for its counter which indicates cross-memory posts in progress to clear (go to zero). This could be because some previous postof this task did not complete its processing. Action If the message occurs frequently, contact Dell EMC Customer Support.

GDDM213I

Cause A BCPII command was entered to GDDRMAIN to display the status of the GDDR IPLAssist Monitor (GIAM). The monitor is not active for the indicated reason:

MISC Subtask not found GIAM runs as a subtask of the MISC subtask in GDDRMAIN. The MISC subtask wasnot found.

MISC Subtask not active GIAM runs as a subtask of the MISC subtask in GDDRMAIN. The MISC subtask is notrunning.

No CPC definitions for this system There are no CPC statements in the GDDRPARM file which specify BCPii and thissystem.

GDDR IPL Assist Monitor not active (completion code) The MISCBCPS subtask of the MISC task has terminated with the completion codeshown.

Action None.

GDDM214I

Cause A BCPII command was entered to GDDRMAIN to display the status of BCPii message scansubtasks. These tasks run as subtasks of the MISCBCPS subtask of MISC. For eachmessage scan subtask, the task name is shown along with the CPC specification it is using.The subtask status is also shown (either ACTIVE or ENDED (completion code)).

*** WARNING *** Master site selected is not the most current

Task task-name timed out waiting for post counter to clear (valuevalue)

GDDR IPL Assist Monitor not active: reason

BCPii Message Scan Subtasks: task-name: cpc-name - status


Action None.

GDDM217E

Cause No systems were found defined to GDDR. TCP/IP and/or the GDDRMAIN COMM subtaskmay not be active. Action Ensure all GDDR systems are properly defined in the GDDRPARM file using the COMMstatement.Ensure TCP/IP and the GDDRMAIN COMM subtask are active.To start COMM, recycle GDDRMAIN or use the following command: F GDDRMAIN,STARTCOMM.

GDDM218I

Cause The indicated module was loaded into dynamic LPA from the indicated concatenation(STEPLIB or LNKLST). Action None.

GDDM220I

Cause The indicated message was intercepted on the indicated system and is being processed(on the system where the GDDM220I message is displayed) according to the rules ineffect for that message. The originating job name and/or job ID may also be indicated.After the message, in parentheses or on the next line, is a description of the action takenin response to the message (for example, executing REXX GDDRM480). Action None.

GDDM221I

Cause The indicated message was intercepted on the indicated system and is being forwarded tothe indicated destination (all C-systems, all P-systems, master C-system). The originatingjob name and/or job ID may also be indicated. Action None.

GDDM222E

No GDDR systems found (ensure GDDRMAIN COMM subtask is active)

module loaded into dynamic LPA from {LNKLST|STEPLIB}

Processing message-id from jobname (job-id) on site-id, system-name (action)

Forwarding message-id from jobname (job-id), on site system todestination

Job jobname (job-id) has GDD$nnnn DD but is using SCF subsystem


Cause A message was intercepted from the indicated address space.The address space is using our GDDR subsystem, however it is not using the same SCFsubsystem as GDDRMAIN. Action Correct the SCF$ DD in the JCL for the indicated address space, and recycle that addressspace, if appropriate.

GDDM223I

Cause The indicated message was intercepted on the indicated system.The originating job name and/or job ID may also be indicated. This message would normallybe processed or forwarded, but in this case the issuer does not affinity with our GDDRinstance. At the end of the GDDM223I message in parentheses is the reason (i.e.,name/token mismatch, GDD$ DD mismatch, SCF$ DD mismatch).This is a verbose message and is only issued if verbose messaging is enabled. This can bedone using GDDRMAIN EXEC PARM=VERBose or command F GDDRMAIN,seTVERBose=ON. Action None.

GDDM228I

Cause SCF is not active. Action Start the SCF task.

GDDM229I

Cause GDDR is using the indicated SCF job name, job ID, and subsystem, which has just started. Action None.

GDDM230I

Cause SCF has not yet completed initialization. Action None.

GDDM231I

name mmmm

Ignoring msgid from jobname (job-id) on site system (reason)

Waiting for SCF to start

SCF scf-version job scf-jobname (job-id) subsystem scf-subsystemstarted

Waiting for SCF to complete initialization


Cause GDDR is using the indicated SCF job name, job ID, and subsystem, which is active and fullyinitialized. Action None.

GDDM232W

Cause The SCF task used by GDDR terminated unexpectedly. Action Correct any issues indicated in the SCF job log, and restart the SCF task.

GDDM240E

Cause An error occurred routing a GDDR work control block. Action Ensure that GDDRMAIN is active, including the COMM and WORKMGR subtasks and therequired workers.

GDDM241E

Cause A GDDR work request timed out. Action Ensure that GDDRMAIN is active, including the COMM and WORKMGR subtasks and therequired workers.

GDDM242E

Cause A STOP worker command was issued for the indicated worker, but the worker is busywaiting for the indicated function. Action Wait for the indicated function to complete. If necessary and appropriate, reissue theSTOP command with the FORCE parameter to interrupt and stop the worker immediately.This should only be done under the direction of Dell EMC Customer Support.

GDDM243E

Cause A CANCEL worker command was issued for the indicated worker, but STOP with FORCE

SCF scf-version job scf-jobname (job-id) subsystem scf-subsystemis active and initialized

SCF task terminated unexpectedly

Error routing work control block (rc/rs)

Work request timed out

Worker worker-name is busy waiting for function function

STOP with FORCE must be attempted for worker worker-name beforeCANCEL


has not been attempted. The CANCEL command may only be used under direction of DellEMC Customer Support as a last resort to cancel the worker unconditionally. Action Issue the STOP command for the indicated worker. If the worker is busy, reissue theSTOP command with the FORCE parameter to interrupt and stop the worker immediately.Note that the FORCE parameter should only be used under guidance of Dell EMCCustomer Support.

GDDM245E

Cause An error occurred reading the indicated GDDR global variable. Action Ensure that GDDRMAIN is active and initialized and that the GVT subtask is active.

GDDM246E

Cause The indicated value for the indicated GDDR global variable is not in a valid format. Action Contact Dell EMC Customer Support if the problem persists.

GDDM247I

Cause The indicated GDDR worker subtask is starting. Action None required. If necessary, issue the F GDDRMAIN,WORKER command to see the statusof GDDR worker.

GDDM248I

Cause The indicated GDDR worker subtask is stopping. Action If necessary, issue the F GDDRMAIN,WORKER command to see the status of GDDRworkers.

GDDM250W

Cause When submitting a GDDR script, a parameter was specified that requires a secondparameter to also be provided. This message is a warning that the second parameter hasnot yet been specified. Action

Error reading global variable gv-name (rc/rs)

Global variable name value value is invalid

Starting worker worker-name

Stopping worker worker-name

Warning: Parameter parameter1 requires parameter2 is alsospecified.


Enter the additional required parameter(s) or reply CANCEL to message GDDM252A toterminate script processing.

GDDM251I

Cause A command (SCRIPT, GVB, RDFREFR) was entered via MODIFY to GDDRMAIN or a scripthas been automatically submitted (such as by HBM or EVM or MISC for global variablebackup). GDDRMAIN has submitted a unit of work to a worker to accomplish this task.Expect messages and/or WTORs from a worker as a result.SCRIPT and GVB commands result in work being submitted to a GDDWXR worker. TheRDFREFR command results in work being submitted to a GDDWDV worker. Action None.

GDDM252A

Cause A script command was entered via modify to GDDRMAIN. Information about the scriptparameters is being requested.This WTOR will be repeated until END or CANCEL or some keyword implying those actionsis entered. Action The response consists of one or more keywords and/or keyword=value. If more than onekeyword is entered, separate with commas. Some keywords can be abbreviated. If akeyword can be abbreviated, the word is shown as xxxx(yyy). This means that xxxx is theminimum amount of the keyword which can be specified. Any additional or all yyy characters can optionally be specified.For a description of valid keywords, refer to the GDDR Product Guide for yourconfiguration.Enter parameters as appropriate. The WTOR will time out after 10 minutes, and the scriptsubmission process will terminate (as if CANCEL had been specified) if no reply is made.

GDDM253I


Script command work submitted●

Script work submitted●

Global Variable Backup work submitted●

RDF link map refresh work submitted●

Enter script parameters for script-name or END or CANCEL

Script script-name parameters: SITE - site-id SYSTEM - system-name PRISWAP - primary-swap-group SECSWAP - secondary-swap-group CALLOVER - call-override USER - userid PARM - parm-value SDDFCLN - sddf-clean-option NONSTAR - nonstar-devs-option ALLOWHMC - hmc-options HMCPRIM - hmc-primary-option


●

Cause END has been entered or implied in response to message GDDM252A. The currentsettings of the script generation/submission parameters are displayed. This message isfollowed by message GDDM255A unless AUTO is in effect. Action None.

GDDM254E

Cause Only one script command can be in progress at a time. This indicates that a secondSCRIPT command was issued while the first was still active. Action Wait until the current script command (and resultant script, if any) is finished and tryagain.

GDDM255A

Cause END has been entered or implied in response to message GDDM252A. This message ispreceded by message GDDM253I showing the current script generation/submissionparameters.If the parameters are correct, and if you wish to proceed with script generation andsubmission, enter Y; if you wish to modify some parameters, enter N; if you wish toabandon this process, enter CANCEL. Action Enter either Y or N or CANCEL.Resultant actions are:

Y - script generation proceeds

HMCSECN - hmc-secondary-option HMCWTOR - hmc-wtor-option HMCLOADC - hmc-loadclear-option TESTBCV1 - test-bcv-dc1-option TESTBCV2 - test-bcv-dc2-option TESTBCV3 - test-bcv-dc3-option TESTBCV4 - test-bcv-dc4-option EXTBCV - use-external-bcv-option BCVGROUPS - bcvgroups-option SELSYS - selsys-option ALTPARMS - use-alternate-hmc-parms-option DRTPARMS - use-disaster-recovery-test-hmc-parms-option BGCLONE - use-background-TimeFinder-clone-option ZDPPAUSE - zdp-pause-option ZDPRESUME - zdp-resume-option SELPROF - tape-profile-name TAPEONLY - tape-only-option VMAXONLY - vmax-only-option 1SIDE - single-side-option 1REGION - single-region-option RRSKIP - rerun-skip SUBMIT - submit-option JCLSAVE - jclsave-option

GDDR Script command already in progress

Confirm script script-name generation (Y/N/CANCEL)


●

●

N - message GDDM252A is reissued

CANCEL - Script processing ends immediately. GDDM256E

Cause A WTOR issued concerning script generation (in response to a script command beingentered) has timed out. The script generation/submission process terminates. Action Reenter the script command if you still wish to take this action.

GDDM257I

Cause CANCEL was entered in response to a script generation/submission WTOR. The scriptgeneration/submission process ends. Action None.

GDDM258E

Cause The worker has received a work block for a script command. However, the work block isnot correct. This indicates an inconsistency between the CONSOLE subtask ofGDDRMAIN and the script submission processor running in the GDDWXR worker. Action If the problem persists, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have all relevant job documentation available.

GDDM259E

Cause A script command was entered with a script name (first parameter after SCRIPT in thecommand) which is invalid. Typically, this means that the script name is too long (over 8characters). Action Reenter the command with a valid script name.

GDDM260E

Cause A response to message GDDM252A contains a keyword which is not recognized. Action Respond to GDDM252A with a valid keyword. SCRIPT command keywords are describedin the GDDR Product Guide for your configuration.

GDDR Script command for script-name timed out

GDDR Script command for script-name cancelled

Script command processor received invalid work block

Script command has invalid script name

Keyword keyword not recognized


GDDM261E

Cause A response to message GDDM252A contains a keyword which either does not have a valuewhen a value is required, or has an invalid value. Action Respond to GDDM252A with a valid keyword/value string. SCRIPT command keywordsare described in the GDDR Product Guide for your configuration.

GDDM262E

Cause During processing of a LOAD parameter, a circular data set reference has been found. Thiscan occur if a data set to be loaded contains a parameter to load itself, or if a it contains aload of another data set which then contains a load of the original data set. Any of thistype of condition would cause a loop and is therefore not allowed. Action Remove the LOAD parameters from the data set you wish to load, or change the data setreferences so they are no longer circular.

GDDM263E

Cause The indicated dataset cannot be opened. This could occur in processing any parameterwhich specifies a dataset name. Processing of the indicated dataset ends. If this occurs during job submission, no job willbe submitted. Action Examine the SYSLOG for any related messages and determine why the dataset cannot beopened.

GDDM264E

Cause The indicated dataset cannot be allocated. This could occur in processing any parameterwhich specifies a dataset name. This message is preceded by message GDDM031E givingthe specifics of the dynamic allocation error. Action Examine the dynamic allocation return codes in message GDDM031E and determine whythe dataset cannot be allocated. The most common reason would be that the dataset doesnot exist or is not cataloged.

GDDM265E

Cause An I/O error has occurred on the indicated dataset. The most common reason would be

Missing or invalid value for keyword

Dataset dsname already used

Dataset dsname cannot be opened

Dataset dsname cannot be allocated

I/O Error on dsname


that the dataset has DCB characteristics which are incompatible with the script commandprocess. The I/O activity is terminated. Action If this was the result of a LOAD or SAVE operation, the operation is probably incompleteand you should verify the parameters or data set contents. If this message occurs duringthe actual job submission, the job will probably be truncated.

GDDM266I

Cause The requested script has been generated and submitted. The message gives the job nameand job ID. If the job name cannot be determined or if the job ID is not returned by JES,the fields will contain ????????. The script submission via operator command process is ended. Action None.

GDDM267I

Cause The processing for the script command has ended. If a script was submitted, messageGDDM266I will have been issued. If it was not issued, no job was submitted. The scriptgeneration/submission process ends. Action None.

GDDM268E

Cause The JCLSAVE parameter was specified with a value of a dataset name without membername. Member name is required. Action Correct the parameter and retry or omit the parameter.

GDDM269E

Cause An abend occurred in script command processing. Refer to previous messages to ascertainthe nature of the problem. Script command processing ends. Action Correct the problems which caused the abend and retry.

GDDM270E

Cause The dataset specified on the indicated script command keyword does not have the proper

Script script submitted, JOB jobname (jobid)

GDDR Script command for script ended

JCLSAVE requires member name

GDDR Script command for script abended

Data set specified for keyword is not dsorg


●

●

●

●

●

●

●

●

●

●

dataset organization. Proper organization by keyword is as follows:

LOAD - sequential

SAVE - sequential

JCLSUB - sequential

JCLSAVE - partitionedSequential means a sequential (PS) data set or partitioned dataset and member.Partitioned means a partitioned dataset (with member specified also). Action Correct the problems.

GDDM271W

Cause A resource shortage has prevented the indicated action from being taken.The possible values for resource are:

WORK BLOCK - work control blocks

DATA BLOCK - data blocks used with work control blocksThe possible values for action are:

BROADCAST GLOBAL VARIABLE - the value of a global variable changed, but this

system was unable to broadcast the new value to other C-systems.

CHECK C SYSTEMS DIRECTLY - the heartbeat monitor is unable to get status of

other C-systems directly from the other C-systems.

SUBMIT GDD2U09A - the heartbeat monitor is unable to submit script GDD2U09A

(used only in 2-site AutoSwap configurations)

CHECK C SYSTEMS INDIRECTLY - the heartbeat monitor is unable to get status

of C-systems that it cannot contact directly. This would be done via relay from C-

systems which can be contacted directly. Action Contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant job documentation available.

GDDM272I

Cause In response to a GVB command to GDDRMAIN, the global variable backup frequencysetting has been changed to the displayed value.For information about possible frequency values, see the description of the GVB commandin the GDDR Product Guide for your configuration. Action None.

GDDM273W

Cause In response to a GVB command to GDDRMAIN, the global variable backup frequencysetting entered is the setting already in effect. Therefore, no change was made.

resource shortage; Unable to action

Global Variable Backup setting changed to frequency-setting

Global Variable Backup setting entered is already in effect


●

●

●

●

Action None.

GDDM274I

Cause In response to a GVB command to GDDRMAIN, the MISC subtask of GDDRMAIN has beenposted to submit a backup of the global variables. Action None.

GDDM275I

Cause In response to a GVB command to GDDRMAIN, the setting for global variable backup isdisplayed.For information about possible frequency settings, see the GDDR Product Guide for yourconfiguration. Action None.

GDDM276E

Cause In response to a GVB command to GDDRMAIN, the command entered was invalid for thereason shown. The acceptable formats of the command are one of the following:

GVB=NOW

GVB=NONE

GVB=*(hhmm)

GVB=dd(hhmm)Where hhmm is the time of day to run the backup and dd is the first two letters of the dayof the week on which to run the backup. Action Correct the command and retry.

GDDM277E

Cause In response to a GVB command to GDDRMAIN, the MSCB control block for the MISCsubtask of GDDRMAIN could not be located. MISC submits the global variable backup andis required for such backup. Action Contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant job documentation available.

GDDM278I

MISC subtask posted for immediate global variable backup

Global Variable backup setting is frequency-value

GVB command invalid - reason

Unable to locate MSCB for MISC


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

Cause A global variable backup which was scheduled via the GVB command or parameter toGDDRMAIN cannot be submitted because a script is in progress. The backup is postponedfor one hour and will be retried. There is no limit to the number of postponements whichmay occur. Action If you want to run the backup despite a script being in progress, enter the GDDRMAINconsole command 'GVB=NOW'. This will run a backup immediately and cause the nextscheduled backup to occur at its normal time.

GDDM279E

Cause A DLM command was entered, but DLM is not configured on this system. Action Configure DLM and retry.

GDDM280I

Cause A GDDRMAIN DLM command was entered. The status of each DLm system defined toGDDR is displayed. Where:

site-id is the site where the DLm system is located.

dlm-name is the name of the DLm system.

dlm-type can be one of the following: M for a master system and S for a

subordinate system.

ip-address is the DLm system IP address.

port is the DLm system port number.

status can be one of the following:

ALIVE - The DLm system appears to be functioning correctly.

DEAD(1) - There is a problem with VG8-1.

DEAD(2) - There is a problem with VG8-2.

DEAD(12) - There is a problem with both VG8-1 and VG8-2.

DEAD(C) - Unable to communicate with the DLm system.

DEAD(T) - Communication to the DLm system timed out (no response).

DEAD(P) - There was a protocol error in DLm communication.

DEAD(?) - An unknown error occurred.

statuscode provides error details when the DLm status is DEAD. The status code

from the heartbeat request is displayed, if one is returned. If the status code line is

not displayed, it means none was returned (this is the case for an invalid IP

Scheduled Global Variable Backup postponed one hour

DLM command invalid - DLM not configured

DLM statussite-id DLM (dlm-name,dlm-type,IP ip-address,port) Status status Statuscode statuscode site-id DLM (dlm-name,dlm-type,IP ip-address,port) Status status [Statuscode statuscode] DLM Abort Status: abort-status


●

address/port or a timeout). If the status code line is displayed but the code is null, it

means the returned status code was null. This is not indicative of an error.

abort-status is the DLm abort status (ON or OFF). If the DLm abort status is ON,

no DLm steps are executed in scripts. Action None.

GDDM281W

Cause An error has occurred trying to post an address space. This may or may not represent aproblem. At times, work may be performed and the requester ends unexpectedly beforethe work completes, resulting in this condition. Action If the message occurs often/repeatedly, the cause should be investigated.

GDDM282E

Cause A DLM,RESET command was entered, but the request to reset the DLM Abort conditioncould not be processed for the reason given. Action Retry the request. If the error persists, contact the Dell EMC Customer Support Centerfor assistance.

GDDM283I

Cause A DLM,RESET or DLM,SET,ABORT command was entered and the request to reset or setthe DLM Abort condition was sent to each C-system. Action None.

GDDM284I

Cause DLM is configured and the DLM ABORT flag is ON or OFF. If the DLM ABORT flag is ON,DLM steps will be bypassed. Action None.

GDDM285E

Cause A MESSAGE parameter in the GDDRPARM file specified that the named message ID

POST error, code error-code reason reason

Unable to broadcast DLM abort reset, reason

DLM abort {reset|set} broadcast to all C-Systems

DLM ABORT Flag is {ON|OFF}

No space to add message message-id


●

●

●

●

●

●

should be added to the GDDRMAIN message interception table. However, there isinsufficient space in the data space message interception table area to add the entry. Action Contact Dell EMC Customer Support.

GDDM286I

Cause The current status of User Message Automation (ON or OFF) is displayed. If the status isOFF, no user message automation intercepts will be acted upon. If the status isUNDEFINED, it means that no user message intercepts have been defined. In that case,user message automation is off and cannot be turned on. Action None.

GDDM287E

Cause During communications processing in GDDRMAIN, the TCP/IP applications programminginterface module could not be loaded. Therefore, no TCP/IP action could be taken. Action Ensure the TCP/IP API module is available to GDDRMAIN.

GDDM288W

Cause During GDDR console message interception, a message was intercepted with the indicatedmessage ID.There are multiple GDDRs active on the system, and the message must be associated withone of them. However, the message issuer could not be associated with any active GDDRfor the reason shown.Possible reasons are:

ABEND IN GDDRGAFF - abend_code/rs The GDDR routine GDDRGAFF abended. The abend code and reason code areshown. If the abend is xxAC7000 and the reason code is 00080001, the issuingaddress space has probably terminated.

IEAMSCHD FAILURE - rc The scheduling of the GDDR SRB routine failed. The return code (in hex) from theIEAMSCHD service is shown.

ISSUER HAS NO AFFINITY The issuing address space has neither GDDR affinity nor SCF affinity.

ISSUER VALIDATION FAILED ASID - asid The data provided with the message about the issuing address space ASID is notvalid.

ISSUER VALIDATION FAILED JOBID - job-id The data provided with the message about the issuing address space job ID is notvalid.

ISSUER VALIDATION FAILED JOBNAME - jobname The data provided with the message about the issuing address space job name is not

User Message Automation is {on|off}

Unable to load TCP/IP API processing module

Unable to determine GDDR affinity for message-id, reason


●

●

●

●

valid.

NO ASID OF ISSUER PROVIDED No data about the issuing address space was provided.

NO SRB ROUTINE LOADED The GDDR SRB routine (GDDRSRB1) was not loaded during GDDRMAIN initialization.See if any error messages were issued when GDDRMAIN initialized.

SRB FAILURE - comp/rc/rs The GDDR SRB routine failed. See the IEAMSCHD documentation from IBM for anexplanation of the fields (which are all displayed in hex).

UNABLE TO LOCATE ASCB OF ISSUERThe issuing address space ASID could not be associated with a currently active addressspace. Most likely this means the issuing address space has terminated. Action Depending on the message, it may be necessary to contact Dell EMC Customer Support. Ifthe message is critical to GDDR processing, be aware that the message was notprocessed.

GDDM289E

Cause During GDDRMAIN initialization, it was discovered that another GDDRMAIN is alreadyactive and using the same SCF subsystem as this GDDRMAIN. This is not allowed.The message indicates the GDDR "subsystem" name of the GDDRMAIN which is using thesame SCF. Action Specify a distinct SCF for each GDDRMAIN. Change the JCL used to run GDDRMAIN tospecify that subsystem in an SCF$ DD statement.

GDDM290E

Cause During GDDRMAIN initialization, it was discovered that another GDDRMAIN is alreadyactive on this system and this system is a managed system (not a C-system). This is notallowed. Only one GDDRMAIN may be active on a managed system. Action Do not attempt to start more than one GDDRMAIN on a managed system.

GDDM291E

Cause During GDDRMAIN initialization, it was discovered that another GDDRMAIN is alreadyactive on this system and either this GDDR or another has no SCF connector DD (anSCF$xxxx DD DUMMY to connect it to a specific SCF). When multiple GDDRs are active,each one must have an SCF connector DD and each GDDR must connect to a differentSCF. Action Specify SCF$ connector DDs in all GDDRMAIN procedures.

GDDR subsystem subsystem is using the same SCF as this GDDRsubsystem

Multiple GDDR subsystems not allowed on managed systems

Multiple GDDR subsystems active and subsystem has no SCF connectorDD


●

●

●

GDDM292E

Cause During GDDREVM or GDDRWORK initialization, it was discovered that an SCF$nnnn connector DD is already allocated, but the SCF subsystem name (nnnn) is not the SCFsubsystem in use by GDDRMAIN. The job (GDDREVM or GDDRWORK) cannot continueusing a different SCF than that in use by GDDRMAIN. Action Remove any SCF$ connector DD from the GDDREVM or GDDRWORK procedures. Thenecessary SCF connector DD will be dynamically allocated.

GDDM293E

Cause A MSGS console command was issued to enable the indicated message ID. However, thedefinition of the message processing was in error and the message cannot be enabled. Action Correct the message definition and reload the message table with the UMA command.

GDDM294I

Cause MSG statements in the GDDRPARM file have added the indicated message ID to consolemessage interception. However, the FORWARD and PROCESS attributes wereincomplete. The FORWARD attribute has been adjusted as indicated. Action None.

GDDM295E

Cause MSG statements in the GDDRPARM file have added the indicated message ID to consolemessage interception. However, the FORWARD and PROCESS attributes wereincompatible. The message is disabled and cannot be enabled.Consistency requirements are:

FORWARD=TOPSYS requires PROCESS=ONPSYS

FORWARD=TOCSYS requires PROCESS=ONCSYS

FORWARD=TOMAST requires PROCESS=ONCSYS or PROCESS=MASTONLY Action Correct the MSG statements in the GDDRPARM file for the message ID and reload themessage interception table by using the UMA command.

GDDM296E

Cause

SCF$nnnn allocated - inconsistent SCF subsystem

Message message-id cannot be enabled

Forwarding for message message-id set to forwarding_value

Inconsistent FORWARD/PROCESS for message-id - Permanently disabled

Unable to convert system system-name to IPV4 address


Due to a mixture of IPV4 and IPV6 addresses for GDDR systems, the COMM subtask ofGDDRMAIN attempts to convert all addresses to IPV4. However, the indicated systemcannot be converted. COMM is unable to initialize and no TCP/IP communication will beavailable on this system. Action Convert TCP/IP addresses so that all use either IPV4 or IPV6 (no mixture) and restartCOMM.

GDDM297E

Cause A FIXPERT command was issued to GDDRMAIN to change the setting (on or off) of theresiliency expert, but there was an error setting the relevant global variable(GLOBAL.GDDR.PARM.RDF0.FIX).The global variable is unmodified. The current setting of the resiliency expert will bedisplayed. Action Retry the command.Check the GDDRMAIN joblog for other error messages signaling issues with global variableupdates, such as authorization failures, DIV-size issues, lock issues and so on. If theproblem persists, contact Dell EMC Customer Support. Keep the GDDRMAIN job log aswell as a printout of GDDRMAIN trace data and syslog available.As a workaround, you can use the Manage GDDR System Variables panel to manuallyupdate the variable.

GDDM298I

Cause A FIXPERT command was issued to GDDRMAIN to display or change the setting (on oroff) of the resiliency expert. The current setting (ON or OFF) is displayed. Action None.

GDDM299E

Cause The indicated feature (for example, a command, parameter, or utility) is unsupported on amanaged system (P-system). Action Resubmit the command or job on a C-system.

GDDM300I

Cause

Unable to set Resiliency Expert, return code rc

Resiliency Expert is {ON|OFF}

feature invalid on managed system

Resiliency Execution Expert is OFFResiliency Execution Expert is ONREE Fix Limit = fix_limitREE Fix RDF Limit = srdf_limitREE Fix SYMM Limit = symm_limit


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

Resiliency Execution Expert global variable values modify command FIXPERT set to ON orOFF.When executing a GDDR script, the Execution Expert will take corrective actions whenstate errors occur to resolve issues without operation intervention. Once the limits arereached and the execution function cannot be resolved, the error will be returned in thescript.The Fix Limits are the maximum retries before exhausting attempts on resolving an issue.If the issue is resolved, then the fix limit attempt counter is reset to zero.The attempt counter is counting consecutive errors before failures. Action Modify command FIXPERT set to ON or OFF.

GDDM301I

Cause A MASTER console command was issued to GDDRMAIN. In response, the current settingof the master C-system for this system is displayed. If the master is not set or there is anerror retrieving the global variable, the value *Unknown will be shown. Action None.

GDDM302E

Cause The specified gatekeeper device is not accessible. The device is in an invalid state.Possible reason code values are:

01 - UCBID specifies a non-standard ID

02 - UCFLA specifies an invalid state

03 - UCFLB specifies an invalid state

04 - UCBMIHTI specifies an invalid state

05 - UCBHOTIO specifies an invalid state

06 - UCBMIHFG specifies an invalid state


08 - UCBLPM specifies an invalid state

09 - UCB not found

10 - UCB not valid

11 - UCB prefix not found

20 - I/O error occurred

32 - No paths

72 - I/O timeout occurred

99 - API error occurredThe reason text in parentheses provides more detail about the error. Action Correct the state of the device, or select a different gatekeeper device. Issuing MVScommands DS QD and DS P for the inaccessible device may provide more information asto what is the problem.

Current Master C System is system

Gatekeeper device is not accessible - CUU ccuu, UCB@ ucbaddr, RS rs (reason)


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

GDDM302W

Cause The specified gatekeeper device is not accessible. This may or may not indicate a problem,depending on the expected state of the device.Possible reason code values are as follows:

1 - UCBID specifies a non-standard ID

2 - UCFLA specifies an invalid state

3 - UCFLB specifies an invalid state

4 - UCBMIHTI specifies an invalid state

5 - UCBHOTIO specifies an invalid state



8 - UCBLPM specifies an invalid state

9 - UCB not found

10 - UCB not valid

11 - UCB prefix not found

20 - I/O error occurred

32 - No paths

72 - I/O timeout occurred

99 - API error occurredThe reason text in parentheses provides more detail about the error. Action If you believe the indicated gatekeeper device should be accessible at this time, correctthe state of the device. Issuing MVS commands DS QD and DS P for the inaccessibledevice may provide more information as to what is the problem.

GDDM303I

Cause The indicated DD name was dynamically allocated using the indicated allocationparameters. The allocation parameters are shown in the same format that would bespecified on a DD statement in JCL. Action Add the indicated DD to the JCL using the indicated parameters.

GDDM310I

Cause A Global Variable Backup (GVB) was scheduled as a result of the GVB EXEC parameter ora GVB modify command.This message indicates the exact date and time the next global variable backup will beperformed. For a reoccurring schedule, this message is issued each time the next backupis scheduled.

Gatekeeper device is not accessible - CUU ccuu UCB@ ucbaddr, RSrs (reason)

ddname DD allocated as alloc-parms

Next Global Variable Backup scheduled for date at time


Action If the scheduled global variable backup is unwanted, update the schedule using the GVBcommand. The global variable backup schedule can be cancelled as follows: FGDDRMAIN,GVB=NONE.

GDDM315W

Cause The indicated planned or unplanned script was active at the time a global variable backupwas scheduled. If the script is still active at the scheduled time, the backup will bepostponed one hour at a time, until the script is complete. Action None. To run a global variable backup despite a script being in progress, issue the followingcommand to perform a backup immediately, so that the next scheduled backup will occurat its normal time: F GDDRMAIN,GVB=NOW.

GDDM400E

Cause A Snap API error occurred. This message indicates the function code and return codes, aswell as other diagnostic information. Action Contact Dell EMC Customer Support.

GDDM410E

Cause The last Clone operation failed for the specified source and target device. This messageincludes the source and target PowerMax/VMAX device numbers, as well as diagnosticinformation, including the last operation code, last operation status, and the elapsed timein seconds since the last operation. Action Contact Dell EMC Customer Support.

GDDM411E

Cause An unknown Clone state was detected for the specified source and target device. Thismessage includes the source and target PowerMax/VMAX device numbers, as well asdiagnostic information, including the last operation code, last operation status, and theelapsed time in seconds since the last operation. Action

script-type script script-name is active, which could cause GlobalVariable Backup to be postponed

Snap API error occurred - Function code function, RC rc, RCXrcx,(syscall-id/syscall-rc/io-rc)

Clone error detected - Source source-symdv#, Target target-symdv#,LastOp oper-code, Status oper-status, Seconds ago elapsed-time

Clone unknown state detected - Source source-symdv#, Targettarget-symdv#, LastOp oper-code, Status oper-status, Seconds agoelapsed-time


●

Contact Dell EMC Customer Support. GDDM420E

Cause The last SnapVX operation failed for the specified source and target device. This messageincludes the source and target PowerMax/VMAX device numbers, as well as diagnosticinformation, including the last operation code, last operation status, reason code, and theelapsed time in seconds since the last operation. Action Contact Dell EMC Customer Support.

GDDM421E

Cause An unknown SnapVX state was detected for the specified source and target device. Thismessage includes the source and target PowerMax/VMAX device numbers, as well asdiagnostic information, including the last operation code, last operation status, and theelapsed time in seconds since the last operation. Action Contact Dell EMC Customer Support.

GDDM422W

Cause A SnapVX hard link was found for the specified source and target device. This messageincludes the source and target PowerMax/VMAX device numbers, as well as diagnosticinformation, including the current state, last operation code, last operation status, and theelapsed time in seconds since the last operation. Action Contact Dell EMC Customer Support.

GDDM430I

Cause This message indicates that GDDR found no VDGs defined on the system. Action Review your zDP and GDDR configuration to decide whether you need to take correctiveaction.

If your configuration has 2 sites in the same region, GDDR allows both of those sites

to have zDP active for DASD at both sites. Examples are DC1 and DC2 in SRDF/Star,

SnapVX error detected - Source source-symdv#, Target target-symdv#, LastOp oper-code, Status oper-status, Reason reason-code,Seconds ago elapsed-time

SnapVX unknown state detected - Source source-symdv#, Targettarget-symdv#, LastOp oper-code, Status oper-status, Seconds agoelapsed-time

SnapVX hard link found - Source source-symdv#, Target target-symdv#, State oper-state, LastOp oper-code, Status oper-status,Seconds ago elapsed-time

No VDGs are defined on this system


●

●

DC1 and DC2 in SRDF/SQAR, and DC3 and DC4 in SRDF/SQAR. In such a case, the

GDDR script will attempt to pause VDGs at both sites twice, once for each C-system

that could have zDP active, in which case this message is expected on one of those

systems and can be ignored.

Another possibility is that you have erroneously configured GDDR to manage zDP for

a DASD site that you do not wish to protect with VDGs. In that case, use the Define

Configuration Features panel (M;P;C;F) to disable VDG management for that site.

If zDP has no VDGs defined, no further action is needed. GDDM500I

Cause BCPii diagnostic messages have been requested. This message provides detailedinformation from the BCPii call. Action None.

GDDM502W

Cause The GDDR IPL Assist Monitor (GIAM) attempts to connect to all LPARs on the CPCs it ismonitoring. The connection to the indicated LPAR failed with the BCPii return code asshown. The return code is a return code from HWICONN. Consult the appropriate IBMdocumentation for the meaning of the return code.

BCPII Diagnostic Function Trace: functionBCPii R15 Contents : r15BCPii Return Code : rcBCPii Input Token value : tkiBCPii Output Token value : tkoBCPii Connect Type : type 1=CPC 2=Img 3=Cap 6=LoadBCPii Connection Value : valueBCPii Connection Value @ : cvalueBCPii Diagnostics Display : diagBCPii Issued Command Type : command-type 1=Act 2=Deact8=Reset 12=Cmd 13=LoadBCPii Command Parameter @ : parmBCPii Event Action Type : action-type 1=Add 2=DeleteBCPii Event Identifier : idBCPii Event Exit Mode : mode 1=TaskBCPii Event ENF Task Addr : addrBCPii Event Parameters : parmsBCPii List Types : list-typesBCPii List Number Returnd : returned-numberBCPii List Returned Addr : returned-addrBCPii List Returned Leng : returned-lengthBCPii List Returned Data : returned-dataBCPii Query Structure Ptr : qystrBCPii Query Structure Num : qynumBCPii Set Type to Change : sttypBCPii Set Type Value Ptr : stptrBCPii Set Type Value : stvalBCPii Set Type Value Leng : stlen

Unable to connect to LPAR lpar-name on CPC cpc-name, rc rc


Monitoring continues (if requested) with other LPARs. Action If the LPAR is one that GIAM should be able to monitor, investigate the error and correct itand restart the appropriate MISCBSnn subtask of GDDRMAIN. If the LPAR is not one thatGIAM should be able to monitor, no action is needed.

GDDM503E

Cause The GDDR IPL Assist Monitor (GIAM) attempts to connect to all LPARs on the CPCs it ismonitoring. Either no LPARS were able to be located or connection to all LPARs that werelocated failed. This message should have been preceded by message GDDM031E orGDDM502W giving an explanation for the problem. Action Correct the problem(s) indicated by GDDM031E or GDDM502W and restart theappropriate MISCBSnn subtask of GDDRMAIN.

GDDM504I

Cause An unexpected BCPii event was detected for the indicated CPC name and image name (ifapplicable). The event type and subtype are also indicated. Action None.

GDDM505I

Cause The indicated BCPii command completed with the indicated return code for the indicatedCPC and image (if applicable). Action None.

GDDM506I

Cause The indicated BCPii message was detected for the indicated CPC and image (ifapplicable). The date and time the message was issued are also indicated. Action None.

GDDM600E

Unable to find or connect to any LPARs on CPC cpc-name

Ignoring BCPii event type event-type subtype event-subtype forcpc-name, image-name

BCPii command command completed with RC rc for cpc-name, image-name

Processing BCPii message message-id issued on date at time forcpc-name,cpc-image

gddrparm_statement


Cause This message is used to echo unsupported or erroneous GDDRPARM statements. Action See supporting messages.

GDDM600I

Cause This message is used to echo GDDRPARM statements. Action None.

GDDM601I

Cause The tape profile dataset for the indicated site has been set to the indicated value. Action None.

GDDM602E

Cause A GDDR Tape license requires a TAPEPROF statement in GDDRPARM for all sites wherethere is a C-system. Action Correct and reissue the command.Add a TAPEPROF statement to the GDDRPARM file for the indicated site as follows:TAPEPROF site GDDR tape-profile-dsnameRestart GDDRMAIN, or issue F GDDRMAIN,PARM_REFRESH to reread the GDDRPARMfile.

GDDM603E

Cause A GDDR Tape License Feature Code (LFC) was found in the SCF initialization (SCFINI)file, but it was ignored, as one or more required GDDRPARM statements were not found. Action See supporting messages.

GDDM604I

Cause The indicated GDDR licenses are active. Action None.

gddrparm_statement

Tape profile dataset name for site set to dsname

TAPEPROF statement statement requires full missing for site site

GDDR Tape license ignored

Licenses set: licenses


GDDM605I

Cause The indicated GDDR licenses that were previously active have been removed. Action None.

GDDM606I

Cause The TAPEONLY parameter was specified; therefore, GDDR is running with a GDDR Tapelicense only. Action None.

GDDM607I

Cause The VMAXONLY parameter was specified; therefore GDDR is running with a GDDR(VMAX) license only. Action None.

GDDM608E

Cause There are no active GDDR licenses. Action Ensure the appropriate GDDR License Feature Codes (LFCs) are included in the SCFinitialization (SCFINI) file. Preceding messages may provide information as to the reasonfor the error.

GDDM610I

Cause This GDDR instance is a C-system enabled for GDDR C-system multi-tenancy and cantherefore run concurrently with other C-systems on the same z/OS system. Action None.

Licenses removed: licenses

TAPEONLY specified, running with GDDR Tape license only

VMAXONLY specified, running with GDDR (VMAX) license only

No active GDDR licenses

Multi-GDDR is enabled for subsystem this_subsystemOther GDDR instances active on system:- subsystem_1- subsystem_2- . . . .- subsystem_n


GDDM611E

Cause One or more other C-systems that are enabled for GDDR C-system multi-tenancy areactive on the indicated z/OS system. This GDDR instance is not enabled for GDDR C-system multi-tenancy and cannot run concurrently with any other GDDR instance on thesame z/OS system. Action Enable GDDR C-system multi-tenancy for this subsystem using the MULTI statement inGDDRPARM, for example:MULTI * ssys ENABLEWhere ssys is the GDDR subsystem name.Issue command F GDDRMAIN,PARM_REFRESH or recycle GDDRMAIN on all systems inthe affected GDDR-plex to enable GDDR C-system multi-tenancy.

GDDM612E

Cause One or more C-systems are active on the indicated z/OS system. This GDDR instance is aP-system and cannot run concurrently with any other GDDR instance on the same z/OSsystem. Action Choose a different z/OS system for this GDDR instance.

GDDM613E

Cause A P-system is active on the indicated z/OS system. P-systems cannot run concurrentlywith any other GDDR instance on the same z/OS system. Action Choose a different z/OS system for this GDDR instance.

GDDM614E

Cause Another C-system that is not enabled for GDDR C-system multi-tenancy is active on theindicated z/OS system. The indicated subsystem cannot run concurrently with any other

Multi-GDDR is disabled for subsystem this_subsystemOther GDDR instances active on system:- subsystem_1- subsystem_2- . . . .- subsystem_n

This subsystem (this_subsystem) is a P-system, multi-GDDR notsupportedOther GDDR instances active on system:- subsystem_1- subsystem_2- . . . .- subsystem_n

P-system subsystem is active on system, multi-GDDR not supported

Multi-GDDR is disabled for subsystem subsystem active on system


GDDR instance on the same z/OS system. Action Enable GDDR C-system multi-tenancy for the indicated subsystem using the MULTIstatement in GDDRPARM, for example:MULTI * ssys ENABLEWhere ssys is the GDDR subsystem name.Issue command F GDDRMAIN,PARM_REFRESH or recycle GDDRMAIN on all systems inthe affected GDDR-plex to enable GDDR C-system multi-tenancy.

GDDM620I

Cause Given the configured site combination (i.e., SITE statements in GDDRPARM), licenses,and GDDR global variables, the indicated configuration type was detected. Action None.

GDDM621I

Cause The indicated sites and corresponding regions were defined via the SITE statement inGDDRPARM. Action None.

GDDM622I

Cause The indicated MSC groups were defined via the MSCGROUP statement in GDDRPARM. Action None.

GDDM630E

Cause The indicated GDDRPARM statement was specified an excessive number of times. Action Remove any duplicate or superfluous GDDRPARM statements. Restart GDDRMAIN, orissue the F GDDRMAIN,PARM_REFRESH command to reread the GDDRPARM file.

GDDM640E

Cause A GDDRPARM statement was found specifying an invalid site. Action

Configuration type detected: config_type

Sites defined: site (region region), site (region region), ...

MSC groups defined: mscgrp, mscgrp, ...

Excessive parameter-name statements specified

Site site is invalid


Correct the erroneous GDDRPARM statement. Restart GDDRMAIN, or issue the FGDDRMAIN,PARM_REFRESH command to reread the GDDRPARM file.

GDDM641E

Cause Multiple SITE statements were found in the GDDRPARM file for the indicated site. Eachsite in the configuration may only be defined once. Action Correct or remove the erroneous SITE statement, as appropriate. Restart GDDRMAIN, orissue the F GDDRMAIN,PARM_REFRESH command to reread the GDDRPARM file.

GDDM642E

Cause One or more GDDRPARM statements (such as CPC, CSYSSITE, DRTCOMM,MSCGROUP, SYMM, TAPEPROF) were found referencing the indicated site. However,the indicated site does not have a matching SITE statement. Action Correct the GDDRPARM statement or statements specifying the indicated site, or add aSITE statement for that site, for example:SITE DC1 GDDR REGION(1)Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM643E

Cause At least two valid SITE statements were not found in the GDDRPARM file. Action Ensure that at least two valid SITE statements are specified in GDDRPARM. RestartGDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM644E

Cause A SITE statement was not found in the GDDRPARM file for the indicated site at theindicated region. The indicated site must be defined in the indicated region. Action Add a SITE statement for the indicated site in the indicated region.For example, if the message states Site DC1 in region 1 must be configured,add:SITE DC1 GDDR REGION(1)Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM645E

Multiple SITE statements found for site site

SITE statement not found for site site

At least two sites must be configured

Site site in region region must be configured


Cause A SITE statement was found in the GDDRPARM file for the indicated site, but it does notspecify the indicated region. The indicated site, if configured, must be in the indicatedregion. Action Correct the SITE statement for the indicated site to specify the indicated region.For example, if the message states Site DC2 must be in region 1, add:SITE DC2 GDDR REGION(1)Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM646E

Cause No SITE statement was found in GDDRPARM for site DC4, or it does not specify region 2If DC2 is configured, then DC4 must defined be in region 2. Action Add or correct the SITE statement for DC4, for example:SITE DC4 GDDR REGION(2)Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM647E

Cause No SITE statement was found in GDDRPARM for site DC4, or it does not specify region 3.If DC2 is not configured, then DC4 must be defined in region 3. Action Add or correct the SITE statement for DC4, for example:SITE DC4 GDDR REGION(3)Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM648E

Cause A SITE statement was found in GDDRPARM for site DC4 but not for site DC3. If DC4 isconfigured, then DC3 must also be configured. Action Ensure that a SITE statement is specified for DC3, for example:SITE DC3 GDDR REGION(2)Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM649E

Cause

Site site must be in region region

Site DC4 must be in region 2 if site DC2 is configured

Site DC4 must be in region 3 if site DC2 is not configured

Site DC3 must be configured if site DC4 is configured

SYMM statement not found for site site


No SYMM statements were found for the indicated site. If the "GDDR" license is present,there must be at least one PowerMax or VMAX system defined for each configured site. Action Ensure that a SYMM statement is specified for the indicated site:SYMM DC1(H) GDDR 000123456789,1000-1010Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM650E

Cause One or more MSCGROUP statements were found in GDDRPARM. However, theconfiguration type (derived from the SITE statements in GDDRPARM) does not supportSRDF/A. Action Remove all MSCGROUP statements, or correct the specified SITE statements to ensurethe resulting configuration supports SRDF/A, as appropriate. Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM651E

Cause No MSCGROUP statement was found in the GDDRPARM file for the indicated site pair inthe indicated direction. The configuration type (derived from the SITE statements inGDDRPARM) requires an MSC group definition for the indicated site pair in the indicateddirection. Action Add an MSCGROUP statement for the indicated site pair in the indicated direction.Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM652E

Cause Multiple MSCGROUP statements were found in the GDDRPARM file for the indicated sitepair in the indicated direction. Only one MSC group may be defined per site pair perdirection. Action Ensure that there is only one MSCGROUP statement per site pair per direction.Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM653E

Cause Multiple MSCGROUP statements were found in the GDDRPARM file specifying the

MSCGROUP statements valid only for configs containing SRDF/A

No MSCGROUP statement found for DCn->DCm

Multiple MSCGROUP statements found for DCn->DCm

Duplicate MSC group name mscgrp found, config_type requires uniqueMSC group names


indicated MSC group name. The indicated configuration type requires all unique MSCgroup names. Action Correct the MSCGROUP statements to ensure that all MSC group names are unique.Restart GDDRMAIN, or issue the F GDDRMAIN,PARM_REFRESH command to reread theGDDRPARM file.

GDDM699I

Cause A GDDR PARM_REFRESH was initiated either programmatically or by command, andprocessing is complete. Action None.

GDDM700A

Cause A mismatch was detected between two or more active systems in the GDDR-plex thatmust be resolved for GDDR to function properly. Action Determine which system(s) are in error (see multiline message GDDUC03I). If the systemwhere the WTOR is issued is in error, reply CANcel, resolve the mismatch, and restartGDDRMAIN. If a remote system is in error, resolve the mismatch and restart GDDRMAINon that system, then reply Retry to redrive cross system validation. See documentationfor preceding error message(s) for more information, specifically GDDUC16E, GDDUC17E,GDDUC18E, or GDDUG49E.

GDDM701I

Cause A WTOR was issued, and the operator replied CONTinue. GDDRMAIN will proceed withinitialization. Action None.

GDDM702I

Cause A WTOR was issued, and the operator replied Retry. GDDRMAIN will redrive cross-systemvalidation. Action None.

GDDM703I

GDDR PARM_REFRESH complete

{License|Subsystem name|Version|Compatibility level} mismatchdetected (reply CONTinue, Retry, or CANcel)

Operator replied CONTinue proceeding

Operator replied Retry redriving cross-system validation


Cause A WTOR was issued, and the operator replied CANcel. GDDRMAIN will terminate. Action None.

GDDM705E

Cause A WTOR was issued, and an invalid response was received. See the message text of theWTOR for the valid responses. Action Respond using one of the responses listed in the message text of the WTOR.

GDDM992E

Cause The indicated feature (for example, a command, parameter, or utility) requires a GDDRTape license. Action Contact Dell EMC Customer Support.

GDDM993E

Cause The indicated feature (for example, a command, parameter, or utility) requires a GDDR(VMAX) license. Action Contact Dell EMC Customer Support.

GDDM998E

Cause An internal error occurred. Action Contact Dell EMC Customer Support if the problem persists.

Operator replied CANcel terminating

Invalid WTOR response: response

feature requires a full GDDR Tape license

feature requires GDDR (VMAX) license

variable-text


CHAPTER 5 WTORs Requiring Operator Action (GDDO) GDDO001I

Cause GDDR is requesting operator permission to run the indicated utility with the indicatedgatekeeper and MSC group. This message is followed by message GDDO002A whichrequires operator response. Action None.

GDDO002A

Cause GDDR is requesting operator permission to run the indicated utility. This message ispreceded by message GDDO001I giving more details. Action Reply Y or N.

GDDO003I

Cause GDDR is requesting (or re-requesting) operator permission to resume workload at theindicated site after an unplanned swap. This message is followed by message GDDO004Awhich requires operator response. Action None.

GDDO004A

GDDR Confirmation ===>******************************************** ** Please Confirm Run of util Using... ** Gatekeeper Device: dev# ** MSC Group: mscgrp ** ********************************************

Please Confirm Run of util Utility (Yes/No):

GDDR Confirmation ===> ******************************************** ** Please [Re-]Confirm Start of ** *** MVS Business Workload *** ** from New Primary DASD Site : site-id ** ********************************************


●

●

Cause GDDR is requesting operator permission to resume workload after an unplanned swap.This message is preceded by message GDDO003I giving more details. Action Reply Y or N.

GDDO005I

Cause One of the following:

GDDR is requesting operator permission to IPL a system at the indicated site using

the stated load address and IPL parameter.

GDDR is informing the user of such action (without a subsequent WTOR requesting

permission).If permission is requested, this message will be followed by message GDDO006A whichrequires an operator response. Action None.

Please Confirm Start of MVS Business Workload (Yes/No):

Format 1:

GDDR Confirmation ===>*********************************************** ** *** Please Confirm IPL at site-id ** Current primary DASD site site-id ** ** Target system : system ** CEC : cpc-name ** LPAR : lpar-name ** ** Load address : load-address ** Load parameters: load-parms ** ***********************************************

Format 2:

HMC Action ===>*********************************************** ** Performing ipl-action at site-id ** Current primary DASD site site-id ** ** Target system : system ** CEC : cpc-name ** LPAR : lpar-name ** ** Load address : load-address ** Load parameters: load-parms ** ***********************************************


●

●

GDDO006A

Cause GDDR is requesting operator permission to IPL a system. The IPL may be a Test IPL ornot, as indicated in the message. This message is preceded by message GDDO005I givingmore details. Action Reply Y or N.

GDDO007I


GDDR is requesting operator permission to reset-clear a system at the indicated site.


permission).The LPAR and CEC involved are also shown in the message.If permission is requested, this message is followed by message GDDO008A whichrequires operator response. Action None.

GDDO008A

Please Confirm [Test] IPL of system at site (Yes/No):

Format 1:

GDDR Confirmation ===>********************************************* ** Please confirm RESET_CLEAR at site-id ** ** Target system : system-name ** CPC : cpc-name ** LPAR : lpar-name ** *********************************************

Format 2:

HMC Action ===> ********************************************* ** Performing RESET_CLEAR at site-id ** ** Target system : system-name ** CPC : cpc-name ** LPAR : lpar-name ** *********************************************


Cause GDDR is requesting operator permission to reset-clear a system. This message is precededby message GDDO007I giving more details. Action Reply Y or N.

GDDO009I

Cause GDDR is requesting operator permission to take the indicated action against the indicated system at the indicated site. The LPAR and CEC involved are also shown in the message.This message is followed by message GDDO010A which requires operator response. Action None.

GDDO010A

Cause GDDR is requesting operator permission to take the indicated action against the indicated system. This message is preceded by message GDDO009I giving more details. Action Reply Y or N.

GDDO011I

Please Confirm RESET_CLEAR of system-name at site-id (Yes/No):

GDDR Confirmation ===>********************************************* ** Please confirm action at site-id ** ** Target system : system-name ** CEC : cpc-name ** LPAR : lpar-name ** *********************************************

Please Confirm action of system-name (Yes/No):

Format 1:

GDDR Confirmation ===> ******************************************* * * * Please confirm action at site-id * * * * Target system : system-name * * CEC : cpc-name * * LPAR : lpar-name * * * *******************************************

Format 2:

HMC Action ===> *******************************************


●

●


GDDR is requesting operator permission to take the indicated action on the indicated

system at the indicated site.


permission).The LPAR and CEC involved are also shown in the message.If permission is requested, this message is followed by message GDDO012A which requiresoperator response. Action None.

GDDO012A

Cause GDDR is requesting operator permission to take the indicated action against the indicatedsystem. This message is preceded by message GDDO011I giving more details. Action Reply Y or N.

GDDO013I

Cause GDDR is requesting operator permission to take the indicated action against the indicated CEC at the indicated site. This message is followed by message GDDO014A which requiresoperator response. Action None.

GDDO014A

* * * Performing action at site-id * * * * Target system : system-name * * CEC : cpc-name * * LPAR : lpar-name * * * *******************************************

Please Confirm action of system-name (Yes/No):

GDDR Confirmation ===> ******************************************** ** Please confirm action of ** ** Processor : cpc-name ** ** Site : site-id ** ** ********************************************


Cause GDDR is requesting operator permission to take the indicated action against the indicated CEC at the indicated site. This message is preceded by message GDDO013I giving moredetails. Action Reply Y or N.

GDDO015I

Cause GDDR is requesting operator confirmation that an RDR (regional disaster) has occurredand that the indicated sites have been lost. This message is followed by messageGDDO016A which requires operator response. Action None.

GDDO016A

Cause GDDR is requesting operator confirmation that an RDR (regional disaster) has occurredand that the indicated sites have been lost. This message is preceded by messageGDDO015I giving more details. Action Reply Y or N.

GDDO017I

Please Confirm action of cpc-name at site-id (Yes/No):

GDDR Confirmation ===>************************************************ ** * * * R D R D e t e c t e d * * * ** * * * R D R D e t e c t e d * * * ** ** Please Confirm Loss of site-id ** ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ************************************************

Please Confirm Loss of site-id (Yes/No):

GDDR Confirmation ===> *********************************************** * * * * * * R D R R e c o v e r y * * * * * * * * R D R R e c o v e r y * * * * * * * GDDR Now Ready to Begin Recovery @ site-id * * * * Seek Management Approval Before Replying * * Seek Management Approval Before Replying * * *


Cause GDDR is requesting operator permission to begin RDR (regional disaster) recovery at theindicated site. This message is followed by message GDDO018A which requires operatorresponse. Action None.

GDDO018A

Cause GDDR is requesting operator permission to begin RDR (regional disaster) recovery at theindicated site. This message is preceded by message GDDO017I giving more details. Action Reply Y or N.

GDDO019I

Cause GDDR is requesting operator permission to transfer the master C-system role from theindicated old (current) master to the new master. The reason for the transfer is alsoshown. This message is followed by message GDDO020A which requires operatorresponse. Action None.

GDDO020A

Cause GDDR is requesting operator permission to transfer the master C-system role. Thismessage is preceded by message GDDO019I giving more details. Action Reply Y or N.

GDDO021I

***********************************************

Please Confirm Ready to Begin Recovery @ site-id (Yes/No):

GDDR Confirmation ===>********************************************** ** Please Confirm Master C-System Transfer ** ** From System : old-master ** to System : new-master ** Reason : reason ** **********************************************

Please Confirm Transfer Master Function (Yes/No):

GDDR Confirmation ===>*******************************************


Cause GDDR is requesting operator confirmation that the indicated C-system at the indicatedsite is in fact dead. This message is followed by message GDDO022A which requiresoperator response. Action None.

GDDO022A

Cause GDDR is requesting operator confirmation that the indicated C-system is in fact dead. Thismessage is preceded by message GDDO021I giving more details. Action Reply Y or N.

GDDO023I

Cause GDDR is requesting operator permission to run script GDDRPAAB. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO024A which requires operator response. Action None.

GDDO024A

Cause GDDR is requesting operator permission to run script GDDRPAAB. This message ispreceded by message GDDO023I giving more details. Action

* * * Please Confirm that GDDR... * * * * C-System: c-system * * is DEAD at Site: site-id * * * *******************************************

Please Confirm C-System c-system is DEAD (Yes/No):

GDDR Confirmation ===>*************************************************** ** *** Prepare to Abandon Primary Region *** ** Abandon Site(s) site-ids ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [Script is being Re-Run] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************

Please Confirm Management Approval (Yes/No):


Reply Y or N. GDDO025I

Cause GDDR is requesting operator permission to run script GDDRPA0A, GDD2PA0A, orGDD2P14A. If the script is being rerun, "Script is being Re-Run" is shown. This message isfollowed by message GDDO026A which requires operator response. Action None.

GDDO026A

Cause GDDR is requesting operator permission to run or rerun script GDDRPA0A, GDD2PA0A, orGDD2P14A. This message is preceded by message GDDO025I giving more details. Action Reply Y or N.

GDDO027I

GDDR Confirmation ===> ************************************************** * * * Please Confirm * * Resume replication after loss of site-id * * [Script is being Re-Run] * * Source Site: site-id * * Target Site: site-id * * * **************************************************

Please Confirm Resume replication after loss of site-id (Yes/No):

Format 1:

GDDR Confirmation ===> ************************************************** * * * Please Confirm * * Restart Single System * * * * For Failed System system-name * * * **************************************************

Format 2:

GDDR Confirmation ===> ************************************************** * * * Please Confirm * * Restart System at Alternate Location * * * * For Failed System system-name * * *


Cause GDDR is requesting operator permission to run script GDDRPA03 (format 1) orGDDRPA04 (format 2). This message is followed by message GDDO028A which requiresoperator response. Action None.

GDDO028A

Cause GDDR is requesting operator permission to run script GDDRPA03 or GDDRPA04. Thismessage is preceded by message GDDO027I giving more details. Action Reply Y or N.

GDDO029I

Cause GDDR is requesting operator permission to run script GDDRPA05. This message isfollowed by message GDDO030A which requires operator response. Action None.

GDDO030A

Cause GDDR is requesting operator permission to run script GDDRPA05. This message ispreceded by message GDDO029I giving more details. Action Reply Y or N.

GDDO031I

**************************************************

Please Confirm Restart Single System (Yes/No):

or

Please Confirm Restart System at Alternate Location (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please Confirm Business Application ** Re-Start in Secondary Region ** MUST Only be run with Management ** Approval ** ***************************************************

Please Confirm Business Restart in secondary region (Yes/No):

GDDR Confirmation ===>**************************************************



GDDO032A


GDDO033I


GDDO034A

Cause GDDR is requesting operator permission to run script GDDRPA07. This message is

* ** R D R R E C O V E R Y ** Please Confirm Business Application ** Re-Start in Secondary Region ** with SRDF/A to site-id ** MUST Only be run with Management ** Approval ***************************************************


GDDR Confirmation ===>*************************************************** Warning Warning Warning Warning ** ** L D R R E C O V E R Y ** Please Confirm Business Application ** Re-Start in secondary region ** ** *** POSSIBLE DATA LOSS *** ** ** Current Primary DASD Site: site-id ** Current site-role DASD Site: site-id ** ** MUST Only be run with Management ** Approval ***************************************************



preceded by message GDDO033I giving more details. Action Reply Y or N.

GDDO035I

Cause GDDR is requesting operator permission to run script GDD2P18A. This message is followedby message GDDO036A which requires operator response. Action None.

GDDO036A

Cause GDDR is requesting operator permission to run script GDD2P18A. This message ispreceded by message GDDO035I giving more details. Action Reply Y or N.

GDDO037I

Cause GDDR is requesting operator permission to run script GDDRPA21. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO038A which requires operator response. Action None.

GDDO038A

GDDR Confirmation ===> ************************************************** * * * Please Confirm Restart Processing After * * Site Swap * * * * Current Primary DASD Site: site-id * * Current site-role DASD Site: site-id * * * **************************************************

Please Confirm Restart Processing After Site Swap (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please Confirm ** Swap DASD from site-id to site-id ** [(Script is being Re-Run at step step)] ** Source Site: site-id ** Target Site: site-id ** ***************************************************

Please Confirm Swap DASD from site-id to site-id (Yes/No):



GDDO039I


GDDO040A

Cause GDDR is requesting operator permission to run script GDDRPA25.This message is preceded by message GDDO039I giving more details. Action Reply Y or N.

GDDO041I

Cause GDDR is requesting operator permission to run script GDDRPA23. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO042A which requires an operator response. Action

GDDR Confirmation ===>*************************************************** ** Please Confirm DASD SITE SWAP - FAST ** [Script is being Re-Run] ** ** Source Site: site-id ** ** Target Site: site-id ** ** ***************************************************

Please Confirm DASD SITE SWAP - FAST (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please Confirm Resume ConGroup ** ** [Script is being Re-Run] ** ** Secondary DASD Site: site-id ** ***************************************************


None. GDDO042A


GDDO043I

Cause GDDR is requesting operator permission to run script GDDRPA27. The target system isdisplayed if this is the initial run of the script. If this is not the initial run, the target systemis not displayed and "Script is being Re-Run" is shown. This message is followed bymessage GDDO044A which requires operator response. Action None.

GDDO044A


GDDO045I

Cause GDDR is requesting operator permission to run script GDDRPA28. If the script is being

Please Confirm Resume ConGroup (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please Confirm ** Perform test IPL from R2s at site-id ** Target System: system-name ** [Script is being Re-Run] ***************************************************

Please Confirm Perform test IPL from R2s at site-id (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please Confirm ** Resume SRDF/A after test IPL at site-id ** Normal SRDF/A Operations after Test in ** Secondary Region ** [Script is being Re-Run] ** ***************************************************


rerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO046A which requires operator response. Action None.

GDDO046A


GDDO047I

Cause GDDR is requesting operator permission to run script GDDRPA29, GDDRPF29, orGDDRPM29. If the script is being rerun, "Script is being Re-Run" is shown. This messageis followed by message GDDO048A which requires operator response. Action None.

GDDO048A

Cause GDDR is requesting operator permission to run script GDDRPA29, GDDRPF29, orGDDRPM29. This message is preceded by message GDDO047I giving more details. Action Reply Y or N.

GDDO049I

Please Confirm Resume SRDF/A after test IPL at site-id (Yes/No):

GDDR Confirmation ===>************************************************** * * * Please Confirm * * Resume SRDF/A (config-type) * * [Script is being Re-Run] * * Source Site: site-id * * Target Site: site-ids * * * **************************************************

Please Confirm Resume SRDF/A (config-type) to site-ids (Yes/No):

GDDR Confirmation ===> ************************************************** * Please Confirm * * Swap production from site-id to site-id * * Planned Swap * * [Script is being Re-Run] * * from Source Site: site-id * * to Target Site: site-id * * *



GDDO050A


GDDO051I


GDDO052A


GDDO053I

**************************************************

Please Confirm Swap production from site-id to site-id (Yes/No):

GDDR Confirmation ===> ************************************************** * Please Confirm * * Swap production from site-id to site-id - FAST * * Planned Swap * * [Script is being Re-Run] * * from Source Site: site-id * * to Target Site: site-id * * * **************************************************

Please Confirm Swap production from site-id to site-id - FAST(Yes/No):

GDDR Confirmation ===>**************************************************


Cause GDDR is requesting operator permission to run script GDD2P01A. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO054A which requires operator response. Action None.

GDDO054A


GDDO055I


GDDO056A

* ** Please Confirm ** Perform test IPL from BCVs at site-id ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [Script is being Re-Run] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************


18234-11:23:06 GDDO055I GDD2 GDDR Confirmation ===> **************************************************1* * * Please Confirm * * Resume after test IPL from BCVs at site-id * * * * Current Primary DASD Site: site-id * * Current Secondary DASD Site: site-id * * [Script is being Re-Run] * * Seek Management Approval Before Replying * * Seek Management Approval Before Replying * * * **************************************************




GDDO057I


GDDO058A


GDDO059I

GDDR Confirmation ===> ************************************************** * * * Please Confirm * * Perform test IPL from R2s at site-id * * * * At Site: site-id * * [Script is Being Re-Run] * * * * Seek Management Approval Before Replying * * Seek Management Approval Before Replying * * * **************************************************


GDDR Confirmation ===> ************************************************** * * * *** Prepare to Abandon DC1 *** * * *** Prepare to Abandon DC1 *** * * * * Current Primary DASD Site: site-id * * Current Secondary DASD Site: site-id * * [Script is Being Re-Run] * * * * Seek Management Approval Before Replying * * Seek Management Approval Before Replying * * * **************************************************



GDDO061I


GDDO062A

Cause GDDR is requesting operator permission to run script GDD2P15A. This message ispreceded by message GDDO061I giving more details. Action Reply Y or N

GDDO063I

Cause GDDR is requesting operator permission to run script GDD2P16A. If the script is being

GDDR Confirmation ===> ************************************************** * * * Please confirm BCV Re-Establish * * [Script is Being Re-Run] * * * * at Site: site-id * * * **************************************************

Please Confirm BCV Re-Establish (Yes/No):

GDDR Confirmation ===> ************************************************** * * * Please Confirm * * Resume after test IPL from R2s at site-id * * * * Current Primary DASD Site: site-id * * Current Secondary DASD Site: site-id * * [Script is being Re-Run] * * Seek Management Approval Before Replying * * Seek Management Approval Before Replying * * * **************************************************


rerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO064A which requires operator response. Action None.

GDDO064A


GDDO065I


GDDO066A


GDDO067I


GDDR Confirmation ===>*************************************************** ** *** Prepare to Abandon DC2 *** ** *** Prepare to Abandon DC2 *** ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [Script is being Re-Run] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************


GDDR Confirmation ===>*************************************************** Please Confirm Run of SWAPSITEn... ** *** Un-Planned CAX Swap *** ** [Script is being Re-Run] ** *


Cause GDDR is requesting operator permission to run script GDDRUP31. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO068A which requires operator response. Action None.

GDDO068A

Cause GDDR is requesting operator permission to run script GDDRUP31. This message ispreceded by message GDDO067I giving more details. Action Reply Y or N.

GDDO069I

Cause GDDR is requesting operator permission to run script GDD2U09A. This message isfollowed by message GDDO070A which requires operator response. Action None.

GDDO070A

Cause GDDR is requesting operator permission to run script GDD2U09A. This message ispreceded by message GDDO069I giving more details. Action Reply Y or N.

GDDO071I

* from Source Site: site-id ** to Target Site: site-id ** ***************************************************

Please Confirm Run of SWAPSITEn (Yes/No):

GDDR Confirmation ===> ************************************************** * * * Please Confirm Business Workload Shutdown * * * * On Old Primary Site: site-id * * * * Reason: Unplanned SWAP * * * **************************************************

Please Confirm Business Workload Shutdown (Yes/No):

GDDR Confirmation ===>


Cause GDDR is requesting operator permission to run script GDD2U10A. This message is followedby message GDDO072A which requires operator response. Action None.

GDDO072A


GDDO073I


GDDO074A


************************************************** * Warning Warning Warning Warning * * * * *** Restart at secondary after * * *** Unplanned loss of primary * * * * Please Confirm the Running * * of this Script. * **************************************************


GDDR Confirmation ===>*************************************************** Warning Warning Warning Warning ** ** *** SRDF/A was DOWN at the ** Time of the Unplanned SWAP ** ** Please Confirm the Running ** of this Script. ***************************************************



GDDO075I


GDDO076A


GDDO077I


GDDR Confirmation ===>*************************************************** Warning Warning Warning Warning ** ** *** Restart at secondary after ** *** Unplanned loss of primary ** ** *** POSSIBLE DATA LOSS ** ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************


GDDR Confirmation ===>*************************************************** ** *** Reconfigure to concurrent SRDF *** ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [(Script is being Re-Run at step step)] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************


GDDO078A


GDDO079I


GDDO080A


GDDO081I


GDDR Confirmation ===>*************************************************** ** *** Reconfigure to cascaded SRDF *** ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [Script is being Re-Run] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************


GDDR Confirmation ===>*************************************************** ** *** Reconfig to concurrent SRDF with Site Move ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [(Script is being Re-Run at step step)] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying *



GDDO082A


GDDO083I

Cause GDDR is requesting operator permission to run script GDDRUP41. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO084A which requires operator response. Action None.

GDDO084A

Cause GDDR is requesting operator permission to run script GDDRUP41. This message ispreceded by message GDDO083I giving more details. Action Reply Y or N.

GDDO085I

* ***************************************************


GDDR Confirmation ===>*************************************************** ** *** Unplanned Recovery after loss of ** *** Secondary Site ** ** Current Primary DASD Site: site-id ** Current Secondary DASD Site: site-id ** [Script is being Re-Run] ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************



Cause GDDR is requesting operator permission to run script GDDRMMSC. If the script is beingrerun, "Script is being Re-Run" is shown. This message is followed by messageGDDO086A which requires operator response. Action None.

GDDO086A

Cause GDDR is requesting operator permission to run script GDDRMMSC. This message ispreceded by message GDDO085I giving more details. Action Reply Y or N.

GDDO087I

Cause GDDR is requesting operator permission to run the indicated planned or unplanned script.This message is followed by message GDDO088A which requires operator response. Action None.

GDDO088A

Cause GDDR is requesting operator permission to run the indicated script. This message ispreceded by message GDDO087I giving more details. Action

GDDR Confirmation ===>************************************************** * * * *** Move MSC Control function to site-id * * * * Current Primary DASD Site: site-id * * Current Secondary DASD Site: site-id * * [Script is being Re-Run] * * Seek Management Approval Before Replying * * Seek Management Approval Before Replying * * * **************************************************


GDDR Confirmation ===>******************************************************* ** Please Confirm Run of {Planned|Unplanned} Script ** script-name ** *******************************************************

Please Confirm Run of script-name (Yes/No):


Reply Y or N. GDDO089I

Cause GDDR is alerting the operator that a ConGroup trip has occurred. The situation needs tobe investigated and resolved. This message is followed by message GDDO090A whichrequires operator response. Action None.

GDDO090A

Cause GDDR is alerting the operator to an unplanned ConGroup Trip. This message is precededby message GDDO089I giving more details. Action Once the situation has been resolved, press any key to reply.

GDDO091I

Cause GDDR is alerting the operator that a missing heartbeat has been detected. Some possiblereasons are listed in the message. The situation needs to be investigated and resolved.This message is followed by message GDDO092A which requires operator response. Action None.

GDDO092A

Cause GDDR is alerting the operator to an unplanned missing heartbeat. This message ispreceded by message GDDO091I giving more details. Action Once the situation has been resolved, press any key to reply.

GDDO093I

GDDR Unplanned Event ===>ConGroup Trip detected...Identify cause of ConGroup Trip and resume ConGroupor make determination to manually abandon site

Reply to unplanned ConGroup Trip warning

GDDR Unplanned Event ===>Missing Heartbeat detected - possible reasons:>C-System has failed but the site is ok>C-System site has failed>C-System has no connectionsIdentify reason and take appropriate action

Reply to unplanned Missing Heartbeat warning

GDDR Unplanned Event ===>SRDF/A failure detected


Cause GDDR is alerting the operator that an SRDF/A failure has occurred (that is, that SRDF/Ais not active). The situation needs to be investigated and resolved. This message isfollowed by message GDDO094A which requires operator response. Action None.

GDDO094A

Cause GDDR is alerting the operator to an unplanned SRDF/A outage. This message is precededby message GDDO093I giving more details. Action Once the situation has been resolved, press any key to reply.

GDDO095I

Cause GDDR is alerting the operator that an unplanned AutoSwap operation has occurred. Thesituation needs to be investigated and resolved. This message is followed by messageGDDO096A which requires operator response. Action None.

GDDO096A

Cause GDDR is alerting the operator to an unplanned AutoSwap event. This message is precededby message GDDO095I giving more details. Action Once the situation has been resolved, press any key to reply.

GDDO097I

Cause The execution of a script has detected that the SRDF replicated data at the indicatedremote site is more recent than the data at the local site. If script execution is allowed toproceed, it is possible that data will be lost. This message is followed by messageGDDO098A which requires operator response. Action

Identify cause of SRDF/A failure and resume SRDF/Aor make determination to manually abandon site.

Reply to unplanned SRDF/A failure warning

GDDR Unplanned Event ===>AutoSwap detectedIdentify cause of AutoSwap and take appropriate action

Reply to unplanned AutoSwap warning

GDDR Confirmation ===>REMOTE site site-id has more recent data.Please confirm execution of script script-name:script-descriptionfrom LOCAL site site-id


None. GDDO098A

Cause GDDR is requesting operator confirmation that the execution of the described script cancontinue, despite possible data loss. This message is preceded by message GDDO097Igiving more details. Action If the script is to be allowed to continue, reply Y; if not, reply N.

GDDO099I

Cause The execution of a script has detected that the differential data replication ability will belost if the script proceeds. This message is followed by message GDDO100A whichrequires operator response. Action None.

GDDO100A

Cause GDDR is requesting operator confirmation that the execution of the described script cancontinue, despite loss of differential data replication capability. This message is precededby message GDDO099I giving more details. Action If the script is to be allowed to continue, reply Y; if not, reply N.

GDDO101I

Cause The execution of script GDD2U13A is being reconfirmed. There is a possibility of data lossif the script continues. This message is followed by message GDDO102A which requires

Please confirm script-name (Yes/No)

GDDR Warning ===>B-C Differential Capability LossDetermine if script should proceed or not

Reply Y to proceed, N to halt

GDDR Confirmation ===>*************************************************** Warning Warning Warning Warning ** ** *** Restart at secondary after *** ** *** Unplanned loss of primary *** ** ** *** POSSIBLE DATA LOSS *** ** ** Seek Management Approval Before Replying ** Seek Management Approval Before Replying ** ***************************************************


operator response. Action None.

GDDO102A

Cause GDDR is requesting operator confirmation that the execution of script GDD2U13A cancontinue, despite the possibility of data loss. This message is preceded by messageGDDO101I giving more details. Action If the script is to be allowed to continue, reply Y; if not, reply N.

GDDO103I

Cause The execution of script GDDRPA07 is being reconfirmed. There is a possibility of data lossif the script continues. This message is followed by message GDDO104A which requiresoperator response. Action None.

GDDO104A

Cause GDDR is requesting operator confirmation that the execution of script GDDRPA07 cancontinue, despite the possibility of data loss. This message is preceded by messageGDDO103I giving more details. Action If the script is to be allowed to continue, reply Y; if not, reply N.

GDDO105I

Please Re-confirm Run of GDD2U13A (Yes/No):

GDDR Confirmation ===>*************************************************** Warning Warning Warning Warning** L D R R E C O V E R Y* Please Confirm Business Application* Re-Start in Secondary Region* *** POSSIBLE DATA LOSS** Current Primary DASD Site: site-id* Current Secondary DASD Site: site-id** MUST Only be run with Management* Approval***************************************************

Please Re-confirm Run of GDDRPA07 (Yes/No):



Cause The execution of SDDFLIST is being verified. The message indicates whether or not SDDFsession cleanup appears complete. This message is followed by message GDDO106A whichrequires operator response. Action None.

GDDO106A

Cause GDDR is requesting operator confirmation that the execution of SDDFLIST should occur orbe bypassed. This message is preceded by message GDDO105I giving more details. Action If the SDDFLIST should be run, reply Y; if not, reply N.

GDDO107I

Cause The execution of SDDF cleanup is being verified. The check for Star was bypassed by useroption. This message is followed by message GDDO108A which requires operatorresponse. Action None.

GDDO108A

Cause GDDR is requesting operator confirmation that the execution of SDDF cleanup shouldoccur or not or that a check for Star should be performed. This message is preceded bymessage GDDO107I giving more details. Action If the SDDF cleanup should be run, reply P; if not, reply S; if the Star check should bedone, reply C.

GDDO109I

Please confirm run of SDDF LISTSDDF Session Cleanup appears statusReply YES to verify Cleanup with SDDFLISTReply NO to skip verification, ...... and allow script-name to continue.... and proceed to the Retry confirmation

Please confirm run of SDDF LIST (Yes/No):

GDDR Confirmation ===>Please confirm SDDF CLEANUP>>>>>>>WARNING <<<<>>>> WARNING <<<<<<<STAR Check is SUPPRESSED by user option>>>>>>>WARNING <<<<>>>> WARNING <<<<<<<Reply CHECK to perform STAR CheckReply PROCEED to continue SDDF CLEANUPReply STOP to STOP script-name

Please confirm SDDF CLEANUP (Check/Proceed/Stop):



Cause The execution of SDDF cleanup is being verified. The check for Star is enabled. Thismessage is followed by message GDDO110A which requires operator response. Action None.

GDDO110A

Cause GDDR is requesting operator confirmation that the execution of SDDF cleanup shouldoccur. This message is preceded by message GDDO109I giving more details. Action If the SDDF cleanup should be run, reply P; if not, reply S.

GDDO111I

Cause The execution of couple dataset realignment is being verified. This message is followed bymessage GDDO112A which requires operator response. If the script is being rerun, rerun-msg will contain "(Script is being Re-Run)", otherwise it will be blank. Action None.

GDDO112A

Cause GDDR is requesting operator confirmation that the execution of couple datasetrealignment should occur. This message is preceded by message GDDO111I giving moredetails. Action If the couple dataset realignment should run, reply Y; if not, reply N.

GDDO113I

Cause

Please confirm SDDF CLEANUPSTAR check is enabledReply PROCEED to continue SDDF CLEANUPReply STOP to STOP script-name

Please confirm SDDF CLEANUP /Proceed/Stop:

GDDR Confirmation ===>Couple Dataset RealignmentPassed Sites: site-id1,site-id2,RunType: Planned | UnplannedCurrent Primary DASD Site: cpdsite-idCurrent Secondary DASD Site: csdsite-idrerun-msg

Please Confirm Couple Dataset Realignment (Yes/No):

GDDR Confirmation ===>Please Confirm SRDF Dynamic DeviceReconfigurationrerun_msg


GDDR is requesting operator permission to dynamically add or delete devices from theSRDF configuration. If the script is being rerun, rerun_msg will contain "(Script is beingRe-Run)", otherwise it will be blank. This message is followed by message GDDO114Awhich requires operator response. Action None.

GDDO114A

Cause GDDR is requesting operator permission to run the script GDDRPEDD to dynamically addor delete devices to the SRDF configuration. This message is preceded by messageGDDO113I giving more details. Action Reply Y or N.

GDDO115I

Cause GDDR is requesting operator confirmation that the devices at the site shown have beenvaried offline. Action None.

GDDO116A

Cause GDDR is requesting operator confirmation that the devices at the site shown have beenvaried offline. This message is preceded by message GDDO115I. Action If the devices are offline, reply Y. If the devices are not offline, put them offline and thenreply Y. If the devices cannot be put offline, reply N and the script will stop at this point.

GDDO117I

Please Confirm Run of GDDRPEDD (Yes/No):

GDDR Confirmation ===>*************************************************** ** L D R R E C O V E R Y ** Please Confirm Old R1 devices at ** site-id ** are offline ** ***************************************************

Please confirm old R1 devices are offline (Yes/No):

GDDR Warning ===>*************************************************** ** DATA IN THIS REGION IS NOT THE MOST CURRENT ** ** If you proceed with recovery in this region *


Cause GDDR is requesting operator confirmation that recovery is being attempted in thesecondary region when the most current data is in the primary region. Action None. See message GDDO118A.

GDDO118A

Cause GDDR is requesting operator confirmation that recovery will be attempted in thesecondary region even though the primary region has the most current data. This messageis preceded by message GDDO117I. Action If you wish to proceed with this recovery, reply Y. If you wish to take some other action,reply N. If you reply N (or do not reply), the submitted script will fail script generation andno further action will be taken.

GDDO119I

Cause GDDR is requesting operator confirmation that recovery is being attempted in thesecondary region at a site in that region which does not have the most current data. Action None.

GDDO120A

Cause GDDR is requesting operator confirmation that recovery will be attempted at the indicatedsite even though that site does not have the most current data. This message is precededby message GDDO119I. Action If you wish to proceed with this recovery, reply Y. If you wish to take some other action,reply N. If you reply N (or do not reply), the submitted script will fail script generation and

* you will be prompted again to indicate which ** region's data you wish to use for recovery. ** ***************************************************

Proceed with script in this region? (Yes/No):

GDDR Warning ===>********************************************************* ** DATA AT site-id IS NOT THE MOST CURRENT IN REGION ** ** If you proceed with recovery at site-id ** you will be prompted again to indicate which ** site data you wish to use for recovery. ** *********************************************************

Proceed with script at site-id? (Yes/No):


no further action will be taken. GDDO121I

Cause GDDR is requesting operator decision on whether to attempt to use the most current datafor recovery or not. The message indicates the site where the recovery script is about torun. Action None. See message GDDO122A.

GDDO122A

Cause GDDR is requesting an operator decision on whether to attempt to use the most currentdata for recovery. This message is preceded by message GDDO121I. Action If you wish to attempt to use the most current data, reply Y. If you wish to discard themost current data, reply N. If no reply is made, Y is assumed.Replying Y provides recovery using the most recent data, but will delay host restart untilafter the required storage system track table updates have completed. Replying N allowsfor an earlier host restart, but uses less recent data, and causes the most recent data tobe overwritten with older data from the local site where the recovery script is about torun.

GDDO123I

Cause

GDDR Warning ===>****************************************************** ** RECOVERY AT site-id WHERE DATA IS NOT CURRENT ** ({Most current data is in other region | ** Most current data is in other region: site-id | ** Most current data is at site-id in this region| **Most current data is at other site in this region})** Direct GDDR whether or not to keep the most ** current data. Recovery using the most current ** data reduces data loss but delays Host start. ********* Replying N risks more data loss *****************************************************************

Attempt to keep the most current data (site-id)? (Yes/No):

GDDR Confirmation ===> ***************************************************** * Please Confirm Resume after LDR Test at site-id * * * * *** DATA CREATED DURING TEST *** * * *** WILL BE LOST *** * * * * MUST Only be run with * * Management Approval * *****************************************************


GDDR is requesting operator permission to run script GDDRPA08. This message isfollowed by message GDDO124A which requires operator response. Action None.

GDDO124A


GDDO125I


GDDO126A

Cause GDDR is requesting operator permission to run script GDDRPA60. This message ispreceeded by message GDDO125I giving more details. Action Reply Y or N.

GDDO127I

Cause GDDR is requesting operator permission to run script GDDRPA65. This message isfollowed by message GDDO128A which requires operator response.

Please Confirm Resume after LDR Test at site-id (Yes/No):

GDDR Confirmation ===>*************************************************** Please Confirm Abandon of site site-id ** ** MUST Only be run with ** Management Approval ***************************************************

Please Confirm Abandon of site site-id (Yes/No):

GDDR Confirmation ===>*************************************************** Please Confirm Resumption of site site-id ** ** MUST Only be run with ** Management Approval ***************************************************


Action None.

GDDO128A


GDDO129I

Cause GDDR is requesting operator verification of the listed ConGroup Dynamic ADD or DELETEcommand. This message is followed by message GDDO130A which requires operatorresponse. Action None.

GDDO130A

Cause GDDR is requesting operator verification of the CG Dynamic ADD or Delete commandlisted in the preceding GDDO129I message. Action Reply Y or N.

GDDO131I

Cause GDDR is alerting the operator that at least one DLM has not responded to a heartbeatrequest. This causes the DLM event to be set. The situation needs to be investigated andresolved. The status of each DLM can be displayed with the GDDRMAIN DLM command.This message is followed by message GDDO132A which requires operator response. Action None.

Please Confirm Resumption of site site-id (Yes/No):

CG Dynamic Device ADD | DELETE Timeout

Please verify: command-parms Reply Y to allow the script to continue Reply N to stop the script

Please Confirm CG Dynamic Device ADD | DELETE success (Yes/No):

GDDR Unplanned Event ===>DLM Missing Heartbeat detected>>Identify cause of DLM Heartbeat>failure and take appropriate action>


GDDO132A

Cause GDDR is alerting the operator to a missing DLM heartbeat event. This message ispreceeded by message GDDO131I giving more details. Action Once the situation has been resolved, reply anything to so indicate.

GDDO133I

Cause GDDR is requesting operator confirmation that recovery is being attempted in thesecondary region when the most current data is in the primary region. Action None. See message GDDO134A.

GDDO134A

Cause GDDR is requesting operator confirmation that recovery will be attempted in thesecondary region even though the primary region has the most current data. This messageis preceded by message GDDO133I. Action If you wish to proceed with this recovery, reply Y. If you reply Y, it is possible that themost current data will be lost. If you wish to take some other action, reply N. If you reply N(or do not reply), the submitted script will fail script generation and no further action willbe taken.

GDDO135A

Cause GDDR is requesting operator confirmation that the site entered in response to WTORGDDM154A should in fact be used as the master C-System. Message GDDM211W wasissued before this WTOR indicating that there is reason to be concerned that the reply toGDDM154A was not the correct choice. Action If you wish to proceed with the site entered, reply Y.If you wish to choose a different site, reply N.THINK CAREFULLY BEFORE RESPONDING, as using the wrong site could cause GDDRstate variables to be regressed and to no longer be accurate.

Reply to missing DLM heartbeat warning

GDDR Warning ===>

DATA IN THIS REGION IS NOT THE MOST CURRENT

If you proceed with recovery in this region you risk loss ofdata.

Proceed with script in this region? (Yes/No):

Please confirm site selection (Yes/No)


If you do not reply to this confirmation, the WTOR will time out and HBM initialization willfail.

GDDO137I

Cause GDDR is requesting operator confirmation that the alternate SYSRES volume should beused for the upcoming IPL or TEST IPL of the indicated system at the indicated site. Themessage identifies both alternate and normal SYSRES volumes and associated loadparameters. This message is followed by message GDDO138A which requires an operatorresponse. Action None.

GDDO138A

Cause GDDR is requesting operator confirmation that the Alternate System Residence volumeshould be used for the upcoming IPL or test IPL of the indicated system at the indicatedsite. This message is preceded by message GDDO137I which provides more details. Action Reply Y to use the Alternate or N to use the Normal SYSRES volume.

GDDO140I

Cause The execution of CF structure rebuild is being verified. This message is followed bymessage GDDO141A which requires an operator response. Action None.

GDDR Confirmation ===>*** Please Confirm IPL at site -idPerforming parm-ipl at site-idCurrent primary DASD site primary-dasd-site

Target system : system-nameCEC : cpc-name LPAR : lpar-nameALT address : alt-addressALT parameters: alt-parms

Load address : load-addressLoad parameters: load-parms

Please Confirm using ALT IPL parms for ipl of system-name at site-id (Yes/No)

GDDR Confirmation ===>CF Structure RebuildPassed Site: site-idRunType: msg-typeCurrent Primary DASD Site: cpdsCurrent Secondary DASD Site: csds(Script is being Re-Run)


GDDO141A

Cause GDDR is requesting operator confirmation that the execution of CF structure rebuildshould occur.This message is preceded by message GDDO140I giving more details. Action If the CF Structure rebuild should run, reply Y; if not, reply N.

GDDO143I

Cause GDDR is requesting operator to confirm the DLm EFSMOVE function was disabled on theDLm at the indicated site prior to submitting this D/R test script.This message is followed by message GDDO144A which requires operator response. Action None.

GDDO144A

Cause GDDR is requesting operator to verify EFSMOVE has been disabled on the DLm where theD/R test script is about to be run.This message is preceded by message GDDO143I giving more details. Action Reply Y or N.

GDDO145I

Cause GDDR is requesting operator permission to run script GDDRPA46. If the script is beingrerun, Script is being Re-Run is shown. This message is followed by messageGDDO146A which requires operator response. Action None.

Please Confirm CF Structure Rebuild (Yes/No)

GDDR Confirmation ===>*************************************************** Please Confirm ** EFSMOVE has been disabled at site-id * * ***************************************************

Please Confirm EFSMOVE is disabled (Yes/No)

GDDR Confirmation ===>***************************************************** Please Confirm ** Perform SWITCHOVER from site-id to site-id* * [Script is being Re-Run] * * *****************************************************


GDDO147I

Cause GDDR is requesting operator permission to run script GDDRPA47. If the script is beingrerun, Script is being Re-Run is shown. This message is followed by messageGDDO148A which requires operator response. Action None.

GDDO148A

Cause GDDR is requesting operator permission to run script GDDRPA47.This message is preceded by message GDDO147I giving more details. Action Reply Y or N.

GDDO150I

Cause GDDR is requesting operator permission to perform the HMC ACTIVATE on the CF LPARsat the indicated site. This message is followed by WTOR GDDO151A which requiresoperator response. Action None.

GDDO151A

Cause GDDR is requesting operator confirmation that the HMC ACTIVATE of CF LPARs at theindicated site should occur. This message is preceded by message GDDO150I giving moredetails.

GDDR Confirmation ===>***************************************************** Please Confirm ** Perform SWITCHBACK from site-id to site-id* * [Script is being Re-Run] * * *****************************************************

Please Confirm Run of SWITCHBACK (Yes/No):

GDDR Confirmation ===> ************************************************** * * * Please confirm ACTIVATE of site-id CF LPARs * * * *** system-name (site-id) * *** system-name (site-id) * * * **************************************************

Please Confirm ACTIVATE of site-id CF LPARs (Yes/No):


Action If the CF LPARs should be ACTIVATED, reply Y; if not, reply N.

GDDO152I

Cause GDDR is requesting operator permission to perform the HMC ACTIVATE and, if allowed bythe Allow LOAD CLEAR when Activating LPARs in Scripts call override, LOAD CLEARactions on the listed systems at the indicated site and IPL priority. This message isfollowed by WTOR GDDO153A which requires operator response. Action None.

GDDO153A

Cause GDDR is requesting operator confirmation that the HMC ACTIVATE and, if allowed, LOADCLEAR actions should be performed on the systems of the indicated site and IPL priority.This message is preceded by message GDDO152I giving more details. Action If the HMC actions should occur, reply Y; if not, reply N.

GDDO154I

Cause GDDR is requesting operator permission to perform the HMC RESET CLEAR and

GDDR Confirmation ===> Please confirm ACTIVATE and LOAD CLEAR of site-id systems Priority priority-value *** system-nameor

GDDR Confirmation ===> Please confirm ACTIVATE

of site-id systems Priority priority-value *** system-name

Please Confirm ACTIVATE [and LOAD CLEAR] of site-id systemspriority-value (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please confirm RESET CLEAR and DEACTIVATE ** of site-id systems ** ** Priority priority-value ** **** system-name (site-id) ** ***************************************************


DEACTIVATE actions on the listed systems at the indicated site and IPL priority. Thismessage is followed by WTOR GDDO155A which requires operator response. Action None.

GDDO155A

Cause GDDR is requesting operator confirmation that the HMC RESET CLEAR and DEACTIVATEactions should be performed on the systems of the indicated site and IPL priority. Thismessage is preceded by message GDDO154I giving more details. Action If the HMC actions should occur, reply Y; if not, reply N.

GDDO156I

Cause GDDR is requesting operator permission to perform the HMC DEACTIVATE on the listedCF LPARs at the indicated site. This message is followed by WTOR GDDO157A whichrequires operator response. Action None.

GDDO157A

Cause GDDR is requesting operator confirmation that the HMC DEACTIVATE of CF LPARs at theindicated site should occur. This message is preceded by message GDDO156I giving moredetails. Action If the CF LPARs should be DEACTIVATED, reply Y; if not, reply N.

GDDO160I

Please Confirm RESET CLEAR and DEACTIVATE of site-id systemspriority-value (Yes/No)

GDDR Confirmation ===> ************************************************** * * * Please confirm DEACTIVATE of site-id CF LPARs* * * *** system-name (site-id) * *** system-name (site-id) * * * **************************************************

Please Confirm DEACTIVATE of site-id CF LPARs (Yes/No):

GDDR Confirmation ===>*************************************************** ** Please Confirm ** Resume replication after loss of site-id ** [Script is being Re-Run] *


Cause GDDR is requesting operator permission to run script GDD2PA0A in a 2-site SRDF/Aconfiguration. If the script is being rerun, "Script is being Re-Run" is shown. This messageis followed by message GDDO161A which requires operator response. Action None.

GDDO161A

Cause GDDR is requesting operator permission to run or rerun script GDD2PA0A in a 2-siteSRDF/A configuration. This message is preceded by message GDDO160I giving moredetails. Action Reply Y or N.

GDDO166I

Cause GDDR is requesting operator permission to run script GDDRPBCR. This message isfollowed by message GDDO167A which requires operator response. Action None.

GDDO167A

Cause GDDR is requesting operator permission to run script GDDRPBCR. This script requiresmanagement approval. This message is preceded by message GDDO166I giving moredetails. Action Reply Y or N.

GDDO168I

* Source Site: site-id ** Target Site: site-id ** ***************************************************

Please Confirm Resume replication after loss of site-id (Yes/No)

GDDR Confirmation ===>*************************************************** ** Please Confirm Restore BCVs at site-id ** ** *** DATA WILL BE LOST *** ** *** on SRDF devices at selected site *** ** ** *** Management approval required! *** ***************************************************

Please Confirm Restore of BCVs at site-id (Yes/No):


Cause GDDR is warning for the second time about the planned BCV Restore operation in scriptGDDRPBCR.This message is followed by message GDDO169A which requires operator response. Action None.

GDDO169A

Cause GDDR is requesting operator re-confirmation to run script GDDRPBCR. This scriptrequires management approval.This message is preceded by message GDDO168I giving more details. Action Reply Y or N.

GDDO170I

Cause GDDR is requesting operator permission to run script GDDRPBCR.This message is followed by message GDDO171A which requires operator response. Action None.

GDDO171A

Cause GDDR is requesting operator permission to run script GDDRPBCR. This script requiresmanagement approval.This message is preceded by message GDDO170I giving more details.

GDDR Confirmation ===>*************************************************** *** WARNING WARNING WARNING WARNING *** ** Please Reconfirm Restore BCVs at site-id ** ** *** This BCV RESTORE operation will *** ** *** DESTROY ALL DATA *** ** *** on SRDF devices at selected site *** ** ** *** Management approval required! *** ***************************************************

Please Reconfirm Restore of BCVs at site-id (Yes/No):

GDDR Confirmation ===>*************************************************** *** FINAL WARNING! FINAL WARNING! *** ** Please Confirm Restore BCVs at site-id ** *** GDDR is not responsible for the *** ** *** consequences of BCV restore actions. *** ** *** Reply N is the LAST chance to avoid *** ** *** irreparable DATA LOSS which could *** ** *** put your company out of business! *** ***************************************************

Please Confirm DATA LOSS at site-id (Yes/No):


Action Reply Y or N.

GDDO172I

Cause The GDDR BCV Restore module has discovered non-GDDR SRDF groups for GDDR-managed devices. GDDR cannot guarantee data integrity in such configurations.This message is followed by message GDDO173A which requires operator response. Action None.

GDDO173A

Cause GDDR is requesting operator permission to continue the GDDR BCV Restore script, afternon-GDDR SRDF groups have been found.This message is preceded by message GDDO172I giving more details. Action Reply Y or N. Obtain management approval before allowing the script to continue. Thedevices for which non-GDDR SRDF groups were found, are listed in message GDDR545E.Verify that no data push is occurring from those non-GDDR SRDF groups.

GDDO174I

Cause The GDDR BCV Restore module has discovered a more recent and complete set of non-GDDR BCVs for the GDDR-managed SRDF devices. A data analysis should be done todecide whether GDDR should do the restore using the older GDDR-managed BCVs or amanual restore should be done using the more recent non-GDDR BCVs.This message is followed by message GDDO175A which requires operator response. Action

GDDR Confirmation ===>*************************************************** *** WARNING! WARNING! *** ** *** NON-GDDR RA groups found for *** ** *** GDDR-managed SRDF devices at site-id *** ** *** Reply N to stop this script. *** ** *** Reply Y to continue the script with *** ** *** potential loss of DATA INTEGRITY. *** ** *** Management approval required! *** ***************************************************

Please Confirm DATA INTEGRITY LOSS at site-id (Yes/No):

GDDR Confirmation ===>*************************************************** *** WARNING! WARNING! *** ** *** More recent NON-GDDR BCVs found for *** ** *** GDDR-managed SRDF devices at site-id *** ** *** Reply N to stop this script. *** ** *** Reply Y to continue the script using *** ** *** the older GDDR managed BCVs *** ** *** Management approval required! *** ***************************************************


●

●

●

None. GDDO175A

Cause GDDR is requesting operator permission to use the GDDR-managed BCVs for a restoreoperation, after module GDDRPBCR has discovered that a more recent and complete setof non-GDDR-managed BCVs exists for the SRDF devices which are the target of theplanned Restore.This message is preceded by message GDDO170I giving more details. Action Reply Y or N. Obtain management approval before allowing the script to continue.The decision about which set of BCV devices to use, should be made after an analysis ofthe data on each set.

Reply N stops the script. This allows for a manual restore using the non-GDDR BCVs.

Reply Y allows the script to continue, using the GDDR-managed BCVs. It might be

desirable to define the more recent BCV devices to GDDR, if it is found those have

the best data. GDDO180I

Cause GDDR has detected the DLM ABORT flag is set and is requesting permission to executethe script bypassing all DLM-related operations.This message is followed by message GDD0181A which requires operator response. Action None.

GDDO181A

Cause GDDR is requesting operator permission to execute the script bypassing all DLM-relatedoperations. GDDR has detected the DLM ABORT flag is set, indicating DLM commands willlikely be rejected. The remainder of the script may be executed, but all DLM-relatedoperations will be bypassed.This message is preceded by message GDDO180I giving more details. Action Reply Y or N.

Reply N to stop the script. This allows you to investigate and resolve the DLM

problem prior to resubmitting the script.

Please Confirm usage of GDDR BCVs for Restore at site-id (Yes/No):

GDDR Confirmation ===>******************************************* ** ** WARNING - DLM ABORT Flag is ON ** ** ** Please confirm script execution ** that bypasses DLM processing ** *******************************************

Please Confirm bypass of DLM steps in script (Yes/No):


● Reply Y allows the script to continue; however, all DLM-related script processes will

be bypassed.


●

●

CHAPTER 6 GDDR Parameter Messages (GDDP) GDDP001I

Cause Indicates the time and date the parameter processing run began. Action None.

GDDP004E

Cause This message, issued only during batch parameter load, indicates that the initializationoption is not in effect and GDDR is not able to determine the master C-system. However,parameter load processing can only take place on the master C-system unless theinitialization option is in effect. Therefore, parameter load processing is terminated. Action Either run the job on the master C-system or specify the initialization option, asappropriate. Submit the parameter load again.

GDDP034I

Cause Parameter load processing has completed validation and any necessary parametergeneration successfully and is about to back up the existing parameters. The secondmessage indicates the name of the dataset into which the backup member will be saved,and the third message indicates the name of the backup member. The format of the backup member name is Vmmmmddd, indicating the date the backupwas started as follows:

mmmm - The number of minutes since midnight.

ddd - The day number in the current year.

Action None.

GDDP038E

Parameter processing beginning at hh:mm on mmmmmmmm dd, yyyy

Unable to determine master C-System

Beginning backup of GDDR parameters.or

Using backup dataset backup_dsname Backup member backup_memberwill be createdor

Backup member backup_member will be created


Cause This message indicates that parameter backup has failed. One or more previous messagesindicate the reason for the failure. Parameter load processing is terminated. Action Determine the reason for the error from the previous error message(s). Correct the errorand resubmit the parameter load job.

GDDP107I

Cause This message occurs within the specification report and heads the list of componentswhose component type is component_type. Action If necessary, scan this part of the report to determine whether the listed specifications areas you expected.

GDDP108I

Cause This message occurs within the specification report and identifies a component that wasvalidly specified. You can determine whether the listed component is expected. Action None.

GDDP110I

Cause This message identifies the associations that have been established during batchparameter load processing by values specified by user environment parameter statements. Action None.

GDDP150E

Global variable backup terminating

component_type(s)

component_name

C-System c-system-name -> Site site-id (P)

SMF id smf_id -> System c-system-name (P)

System p-system-name -> Site site-id (P)

System p-system-name -> Contingency system cont-system-name (P)

System c-system-name -> SMF id smf_id (P)

System p-system-name -> SMF id smf_id (P)

Site site-id -> C-System c-system-name (P)

Site site-id -> HMC IP address nnn.nnn.nnn.nnn (P)

Contingency system cont-system-name -> System p-system-name (P)


Cause A scan of associations for a system determined that a contingency system associated withthe system is a C-system, an invalid condition. This message appears in the hierarchydisplay. Upon completion of validation, parameter load processing is terminated. Action Remove or correct the parameter statement(s) causing the error and submit theparameter load job again.

GDDP151E

Cause A scan of associations for a system determined that a contingency system associated withthe system is the system itself: an invalid condition. This message appears in the hierarchydisplay. Upon completion of validation, parameter load processing is terminated. Action Remove or correct the parameter statement(s) causing the error and submit theparameter load job again.

GDDP152E

Cause A scan of associations for a system identified multiple contingency systems associatedwith the system: an invalid condition. This message appears in the hierarchy display. Uponcompletion of validation, parameter load processing is terminated. Action Remove or correct the parameter statement(s) causing the error and submit theparameter load job again.

GDDP153E

Cause A scan of associations for a system found no contingency system associated with thesystem, an invalid condition. This message appears in the hierarchy display. Uponcompletion of validation, parameter load processing is terminated. Action Remove or correct the parameter statement(s) causing the error and submit theparameter load job again.

GDDP154E

Cause A SITE.ssssssss=DC3 statement has been detected where ssssssss is not the C-system atDC3. (GDDR does not support production systems at DC3.) Upon completion of validation,parameter load processing is terminated.

Error: Contingency system cont-system-name for system system-name is a C-System

Error: Contingency system for system system-name is the samesystem

Error: Multiple contingency systems found for system system-name

Error: No contingency system for system system-name

Error: Invalid non-C-System at DC3


Action Remove or correct the parameter statement causing the error and submit the parameterload job again.

GDDP187I

Cause This message states whether the input parameters are being ready from the input streamor from a dataset. Action None.

GDDP300E

Cause An invalid value was entered for the field description returned in the message. Action Correct the value to match one of the valid values suggested in the message text.

GDDP301W

Cause Consistency(Ignore) was used for a GDDR parameter backup, and therefore updates toparameters while the backup was running (if any) have been ignored. Action None.

GDDP302I

Cause Consistency(Retry=number) was used for a GDDR parameter backup, updates toparameters occurred during the backup, and therefore the backup is being retried. Action None.

GDDP303W

Cause Consistency(Cancel) was used for a GDDR parameter backup and updates to theparameters occurred during the backup. Therefore the backup was cancelled. Action None.

GDDP304I

Parameter input from {input stream|dataset}

Value value invalid for field: suggested-value

Updates during backup ignored

Retrying backup

Cancelling backup


Cause A successful GDDR parameter backup has been done. The message gives the number oflines written to the output DD name given in the message. Action None.

GDDP305E

Cause The indicated parameter was not specified. The parameter is required. Action Specify a value for the indicated parameter.

GDDP306W

Cause The indicated parameter was not specified. The parameter is optional. The value shown inthe message was assigned. Action None.

GDDP307E

Cause The indicated combination of parameters is invalid. Action Correct one or both of the parameters shown to make them compatible.

GDDP308I

Cause Displays the consistency setting in effect for this parameter set activate. Action None.

GDDP309I

Cause Parameter set activation displays information stored in the backup data. This message isreissued multiple times with the actual backup information. Action None.

GDDP310I

Backup successful, lines lines written to ddname.

parameter not specified

parameter not specified, value assumed

parm1 invalid with parm2

Consistency = value

Information from backup data:


Cause Shows each variable and its value. The first line gives the variable name, the second(which starts with " =") gives the value. Action None.

GDDP311I

Cause Parameter set activation displays the number of global variables found in the input. Action None.

GDDP312I

Cause Parameter set activation (parameter load) is beginning the process of modifying the inputvariables. Action None.

GDDP313I

Cause During parameter set activation, an uninitialized variable was found and deleted it. Thevariable is shown in the message. Action None.

GDDP314I

Cause Parameter set activation has renamed the variable listed first to the name given in themessage. Action None.

GDDP315I

Cause Parameter set activation has reset the indicated variable type to the indicated value. Action None.

variable_name=value

Input # globals = count

Start of modification of input variables:

Deleted uninitialized variable variable_name

Renamed variable oldname to newname

Reset type variable name to value


GDDP316I

Cause Parameter set activation has deleted the indicated variable type from the input set ofvariables. Note that this does not mean that the variable has been deleted, only that it isnot being used from the input. Action None.

GDDP317E

Cause Parameter set activation has detected an error on the indicated input variable with valueas shown.reason is explanatory text explaining the problem and variable is the name of this or arequired related variable. Action Correct the input as indicated.

GDDP318E

Cause Parameter set validation or activation processing has detected errors in the input data andthe parameter set activation will not be done. Action Correct the input and retry the parameter set activation.

GDDP319I

Cause Parameter set activation processing has completed the modification of the input based onthe selected Activation options. Action None.

GDDP320I

Cause Parameter set activation processing has completed input modification and the number of

Deleted type variable name

Error on variable name (value value)This message is followed by another instance of GDDP317E which gives the description ofthe error. The second message has one of these forms:

Invalid name; reason Invalid value; reason●

Requires existence of variable variable●

Unable to determine default for variable; reason●

Validation errors occurred - exiting

End of modification of input variables

Final # globals = count


inputs after modification is as shown. Action None.

GDDP321I

Cause This is a continuation of message GDDP320I, showing the number of removals andadditions to the input set. Action None.

GDDP322E

Cause The system on which parameter set activate is running (indicated in the message) is notdefined as a C-system in the input or existing parameters. Action Run parameter set activation on a C-system.

GDDP323W

Cause Activation processing must normally run on the targeted master C-system. (The systemtargeted to be the master C-system after successful activation. This is determined by theCURRMAST.C=value in the C01ROLES member of the parameter work dataset beingactivated). If this message is followed by messages GDDP324E-326E, then activationprocessing will not run on this system with the given parameters. Action Change the parameters or run activation on the targeted master C-system.

GDDP324I

Cause This message is issued at end of a run of the GDDRGVRL program used in parametervalidation and activation to indicate the program has ended. This message identifies thesystem on which the program ran, the date and time the program ended, and the elapsedtime for the run of the program. Action None.

GDDP325E

Cause

Removed rem globals, added add globals

This system (system-name) is not in the list of C-systems

This system (system-name) is not the master C-System

Parmload ended on system system-name, current-date, hh:mm:ss,elapsed hh:mm:ss

Connectivity to master C-system (system-name) available. Parmload must be run on the master C-system.


Activation processing is not running on the targeted master C-system. (The systemtargeted to be the master C-system after successful activation. This is determined by theCURRMAST.C=value in the C01ROLES member of the parameter work dataset beingactivated.) Connectivity to the targeted master C-system is available. Action Run activation processing on the targeted master C-system or change the activationprocessing options.

GDDP326E

Cause Parameter set activation is running on a system other than the targeted master C-system.(The system targeted to be the master C-system after successful activation. This isdetermined by the CURRMAST.C=value in the C01ROLES member of the parameter workdataset being activated). There is no connectivity to the targeted master C-system. OnlyActivate option 'Propagate to other C-Systems: NO' is valid in this situation. Action Correct the activation options and retry.

GDDP327W

Cause Connectivity to the indicated C-system is not available. Action Investigate why connectivity is not available and correct if possible.

GDDP328I

Cause During parameter load, the parameter input has been verified, but UPDATE(N) wasspecified, so the actual parameter load is not performed. This is the normal occurrence forparameter validation as opposed to parameter activation. Action None.

GDDP329E

Cause During parameter load, it was determined that a script is in progress (not necessarilyrunning, but in progress). A full parameter load cannot be done while a script is inprogress. Action Allow the script in progress to complete and retry the parameter load.

GDDP330E

Propagate = YES invalid on non-master C-system with noconnectivity to master C-system.

No connectivity to system

UPDATE(N), actual load bypassed

FULL restore cannot be run while a script is in progress.


Cause During parameter load, it was determined that a script is in progress (not necessarilyrunning, but in progress). Events cannot be reset while a script is in progress. Action Allow the script in progress to complete and retry the parameter load or change theparameter load to not reset events (use events(asis) or events(noupdate)).

GDDP331W

Cause The dataset information of the dataset containing the parameter input could not beobtained. Action None.

GDDP332E

Cause The enforcement of consistency during a parameter load could not be accomplished. Action Correct the problem causing the inability to activate the consistency exit or change the'Enforce consistency' activation option.

GDDP333W

Cause The enforcement of consistency during a parameter load could not be accomplished. Action Correct the problem causing the inability to activate the consistency exit or change the'Enforce consistency' activation option.

GDDP334I

Cause The indicated number of variables were deleted on the indicated system. Action None.

GDDP335I

Cause The number of variables matching the indicated variable name were deleted on theindicated system.

Events cannot be updated while a script is in progress.

Unable to obtain input file information

Unable to set consistency exit on site site-id, terminating.

Unable to set consistency exit on site site-id, consistency notguaranteed.

count variables deleted on system-name

count stem.** variables deleted on system-name


Action None.

GDDP336I

Cause The indicated variable with indicated value was added on the indicated system. Action None.

GDDP337I

Cause The indicated variable was updated to the indicated value on the indicated system. Action None.

GDDP338W

Cause Updates to global variables were done by processes other than activation processing whileactivation was running. Action Investigate the updates and if necessary, rerun the activation.

GDDP339I

Cause The indicated variable has been added to the input set of variables with the indicatedvalue. Action None.

GDDP340E

Cause The indicated variable is required to be present in the input, but is not present. Action Add the variable or remove the reason that its presence is required.

GDDP341E

Cause

Added name=value on system-name

Updated name=value on system-name

Global variable update(s) occurred on site site-id during partialparm load

Added variable variable_name, value 'value'

===>Error: Required variable variable_name not found in input

Variable variable_name is specified more than once in the input


●

●

The indicated variable was specified more than once in the input. Action Remove the duplicate occurrences.

GDDP342E

Cause The indicated variable is not present in the input and is not currently defined. It isrequired. Action Define the indicated variable.

GDDP343E | GDDP343W

Cause During parameter backup or load, an update to a global variable occurred which was notdone by the backup or load process. The message specifies the variable and the action,which may be BLOCKED or OCCURRED. Action Determine why the variable update was occurring at this time and take action to prevent itif necessary.

GDDP348E

Cause Parameter activation is being attempted with type set to PARTIAL and state variableupdate set to NOUPDATE. However, the value of the CONGROUP name for DC1 and (or)DC2 is being changed and the change cannot be made on this type of update for thereason stated. Possible reason descriptions and their related causes are:

script is in execution - A planned or unplanned script execution is in

progress

current primary DASD site not DC1 or DC2 - The current primary DASD

site must be at either DC1 or DC2. Action Either do not change the values of DC1/DC2 CONGROUP names or change the conditionnoted.

GDDP349I

Cause The GDDR parameter load program displays the number of variables on each system as itcompletes loading variables to that system. The system is identified in the message by itsSMF ID. Action None.

Global variable variable_name not defined and not in input

Update of variable_name {OCCURRED|BLOCKED}

PARMS.DCn.CONGROUP cannot be updated, reason

GDDR count variables on system smf_id


GDDP350W

Cause On a FULL load with reset of event variables and propagation of globals to all C-systems, amismatch in the count of variables between systems has been detected. The messagegives the SMF IDs of the systems and the count on each system. The message isrepeated for every pair of systems with different counts. If this message occurs, thereturn code from the parameter load will be 4 or higher. Action None required; however, you may wish to investigate why the counts are different. A fullload with reset and propagate should result in exactly the same number of variables on allC-systems unless some other process is updating the variables while the parameter load isrunning.

GDDP351E

Cause GDDR parameter load or backup experienced a failure deactivating the consistency exit,GDDREXG1xxxx, where xxxx is the GDDR subsystem name, typically 'GDDR'. The errorcode is given in the message. Action Manually deactivate the exit with the z/OS SETPROG command, as described in theGDDR Product Guide for your configuration.

GDDP352I

Cause GDDR parameter load has issued a command to start or stop either EVM or HBM at theindicated site. Both must not be running while a FULL parameter load or RESET of statevariables is in progress. Action None.

GDDP353E

Cause GDDR parameter load has issued commands to stop EVM and HBM on each C-system tobe affected by the parameter activation, but either or both are still active on some C-system. Action Investigate which systems are still running EVM and/or HBM. Previous instances ofmessage GDDP352I will show which tasks on which systems were found active. Takesteps to stop EVM and HBM on all systems which are relevant to the parameter activationand retry the activation.

GDDR system smfid1 has count1 variables, system smfid2 hascount2 variables.

Deactivation of consistency exit failed on site site-id, returncode rc

{EVM|HBM) {start|stop} at site site-id

Unable to stop {EVM|HBM} on all affected C-Systems


●

●

●

●

●

GDDP354E

Cause GDDR parameter load is attempting to check whether or not EVM and HBM are up at theindicated site, but the site is not responding. The site was checked earlier in the parameterload and was connectivity was present, but it has now been lost. Action Investigate why the system running the parameter load can no longer communicate withthe indicated site. Reestablish communication or adjust the value of PROPAGATE andretry the parameter load.

GDDP355E

Cause GDDR parameter load is running with PROPAGATE(N), but has found that either EVM orHBM or both are active on another C-system. Parameter load stops. Action Either do not use PROPAGATE(N), ensure that the system on which parameter load isrunning cannot communicate with other C-systems, or ensure that EVM and HBM are notrunning on other C-systems with which this system can communicate.

GDDP399E

Cause The listed module was invoked with invalid arguments. The message indicates whichargument is invalid or missing. Action Correct the arguments and rerun the module.If you do not control the arguments, contact Dell EMC Customer Support. Keep thefollowing information available:

Script and/or GDDRWORK job logs

A copy of GDDRPARM

A recent backup of GDDR global variables GDDP400E

Cause The GDDR Automated Configuration Check for DASD utility (GDDRACCD) detected theindicated problem during the internal validation phase.Possible reasons indicated in this message are:

2, 3 or 4 C-systems required. Sitelist: site-list GDDR supports configurations with 2, 3, or 4 sites and C-systems. Insufficient or toomany CSYSSITE parameters are found in ACDDPARM.

3-Site config requires both DC2 and DC3. Site list: site-list ACDDPARM has 3 CSYSSITE parameters, but either DC2 or DC3, or both, aremissing.

Connectivity to site-id lost; parmload cancelled

EVM/HBM found active at site site-id; parmload cancelled

module-name reason

Validation error: reason


●

●

●

●

●

●

●

●

●

●

●

●

ACDDPARM not allocated. GDDRACDD requires the ACDDPARM DD to be pre-allocated, unless it is run withGLOBALS(CHECK).

Automated Configuration Check not supported at site-id (not a

configured site). GDDRACCD detected it is running at a site which is not defined to GDDR. This isprobably a parameter error.

Both sites DC2 and DC3 must have storage defined. Sitelist:

site-list from ACDDPARM GDDRPARM A 3-site configuration is being defined and no SYMM parameters are found for eitherDC2 or DC3 or both. GDDRACDD will flag this as a configuration error and setDCN.Unplanned.CFG=1 if it was called with GLOBALS(CHECK).

CSYSSITE site-id has no SYMM in [ACDDPARM] [GDDRPARM] Every site which has a C-system must also have a SYMM parameter. GDDRACDD willflag this as a configuration error and set DCN.Unplanned.CFG=1 if it was called withGLOBALS(CHECK).

C-System site site-id from GDDRPARM is not known in

CONFIG.SITELIST: list GDDRACDD was called with GLOBALS(CHECK) and found that theCONFIG.SITELIST variable does not contain the listed site-id which is defined in theGDDRPARM file. GDDRACDD will flag this as a configuration error and setDCN.Unplanned.CFG=1. Either correct the GDDRPARM file or the global variable.This will require GDDR parameter activation.

Current system: system-name not defined in CSYSLIST: list GDDRACDD can only run on one of the systems listed in CSYSSITE parameters inACDDPARM.

DC1 is a required site. Sitelist: site-list No CSYSSITE parameter is found for DC1.

DC3 not supported as Primary DASD Site A CONFIG argument was specified, referencing DC3 as the primary DASD site, in a3-site configuration. This is not supported.

DC4 must have storage defined. Site list: site-list from

ACDDPARM GDDRPARM A 4-site configuration is being defined and no SYMM parameter is found referencingDC4 GDDRACDD will flag this as a configuration error and setDCN.Unplanned.CFG=1 if it was called with GLOBALS(CHECK).

Different number of RDF.DEVICES parameters for site pair site1

-site2 versus site2-site1 GDDRACDD was called with GLOBALS(CHECK) and found that the number ofRDF.DEVICES parameters for the listed site pair is different from the number ofparameters for the mirror site pair. GDDRACDD will flag this as a configuration errorand set DCN.Unplanned.CFG=1. Rerun GDDRACDD without the GLOBALS(CHECK)argument, to discover your DASD configuration and perform a parameter ACTIVATE.

Different number of SQAR ra-groups DC1-DC3 (count) versus DC2-

DC4 (count) In a 4-site configuration, the number of SRDF groups for the DC1-DC3 site pairshould be the same as the number of SRDF groups for the DC2-DC4 site pair.

Different number of STAR ra-groups DC3-DC1 (count) versus DC3-

DC2 (count) In a 3-site configuration, the number of SRDF groups for the DC3-DC1 site pairshould be the same as the number of SRDF groups for the DC3-DC2 site pair.


●

●

●

●

●

●

●

●

●

●

●

●

●

●

Discovery Path path for Symmetrix symmserial is not functional

at point part A path to be used for discovery of the listed storage system is found not functional asof a certain point. A path exists of a local gatekeeper address, optionally followed bya list of SRDF groups, in the form gk.srdfgrp.srdfgrp... The part that is not functionalis the last node of the path listed as part in the message. Most likely causes are agatekeeper which has suddenly lost channels or an SRDF group that went suddenlyoffline.

Discovery path path locates Symmetrix symmserial. Expected to

find symmserial A PATH parameter in ACDDPARM is found to point to a different storage system.

Duplicate definition for Symmetrix Unit symmserial at Site

site-id The listed storage system serial number occurs on more than one ACDDPARMSYMM parameter.

Duplicate definition of C-System site site-id Two CSYSSITE parameters are found specifying the same site for a different C-system.

Duplicate definition of C-System system-name Two CSYSSITE parameters are found specifying the same C-system name.

Duplicate usage of gatekeeper gk at site site-id in [GDDRPARM]

[ACDDPARM] Any gatekeeper address to be used by GDDR must be unique within a site. Differentsites are allowed to use the same gatekeeper addresses.

Expected two serial numbers on line. Found: text A VGROUP parameter in ACDDPARM does not specify the two storage systemsrequired to define the group.

Failed to open ACDDPARM (mode) with RC=rc GDDRACDD attempted to open the ACDDPARM dataset, but failed with theindicated EXECIO return code.

Gatekeeper gk in site1-site2 parameter value is not known in

any site1 SYMM parameter in GDDRPARM An RDF.DEVICES parameter is found using a gatekeeper which is not known on anyGDDRPARM SYMM parameter for the listed site. GDDRACDD will flag this as aconfiguration error and set DCN.Unplanned.CFG=1. To correct the global variable,rerun GDDRACDD without the GLOBALS(CHECK) argument and perform GDDRparameter activation. To correct the SYMM parameter, follow the instructions in theGDDR Product Guide for your configuration.

Gatekeeper gk unknown at site site-id on line A PATH parameter in ACDDPARM uses a gatekeeper address not found in anygatekeeper pool for any storage system at the listed site.

GDDRACDD not supported at site-id (not a configured site) GDDRACDD detected it is running at a site which is not defined to GDDR. Probablythis is due to a parameter error.

GDDRMAIN not active. Please rerun with COMP(Y). GDDRACDD found GDDRMAIN to be not active. GDDRACDD can run withoutGDDRMAIN services if the COMP(Y) argument is specified.

GDDRPFX must be length 4. The GDDRPFX argument is specified. It must be 4 characters long.

GENERATE type type on line conflicts with INCLUDE type type


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

for group srdfgrp A GENERATE parameter specifies a type which is different from the type specifiedon the INCLUDE parameter for one of its groups.

GK gk on line does not locate a Symmetrix at site-id An INCLUDE or a GENERATE parameter specifies a gatekeeper address and a site,but the gatekeeper does not locate a storage system at the indicated site.

Group srdfgrp in discovery path path for Symmetrix symmserial

does not exist in Symmetrix symmserial A PATH parameter in ACDDPARM uses an SRDF group not found in the indicatedstorage system.

Group srdfgrp in discovery path path for Symmetrix symmserial

is OFFLINE in Symmetrix symmserial A PATH parameter in ACDDPARM uses an SRDF group which is found to be offline inthe listed storage system.

INCLUDE of virtual group srdfgrp on line not allowed.

(GENERATE parameters only). An INCLUDE parameter references a virtual group. This is only allowed onGENERATE parameters.

Inclusion of srdfgrp as type on line conflicts with with

earlier inclusion as type Two INCLUDE parameters reference the same SRDF group but specify a differentinclusion-type.

Invalid character char in ra-group srdfgrp on line. Expected

one of "0123456789ABCDEF". A VGROUP parameter in ACDDPARM references an invalid SRDF group number.

Invalid char char in ra-group srdfgrp on line An INCLUDE or a GENERATE parameter references an SRDF group which is invalidfor the reason indicated.

Invalid external ra-group srdfgrp on line.

Connects DC1 to DC2 Symmetrix systems, symmserial and

symmserial


symmserial.

Invalid ra-group srdfgrp on line. Must be 2 chars long A VGROUP parameter in ACDDPARM references an invalid SRDF group number.

Invalid ra-group srdfgrp on line.

Must be length 2

Not found in Symmetrix symmserial at site

Connects to unknown Symmetrix symmserial

Connects to same-site Symmmetrix symmserial

Connects DC1 to DC4 Symmetrixes, symmserial and symmserial


symmserial

Connects to ra-group srdfgrp in serial.

Asymmetrical ra-groups are not currently supported with

GDDR.


●

●

●

●

●

●

●

●

●

●

●

●

●

●

Invalid type (not E or I) on line An INCLUDE or a GENERATE parameter specifies a type different from E(external) or I (internal)

Invalid ra-group srdfgrp on line. Should connect site-id to

DC1 or DC2, not site-id A GENERATE parameter in a 4-site configuration specifies an SRDF group that doesnot connect the listed site (DC3 or DC4) to either DC1 or DC2.

Invalid ra-groups srdfgrp,srdfgrp on line. Both connect site-

id to site-id A GENERATE parameter in a 4-site configuration specifies an SRDF group pair bothof which connect the same site pair (DC3/4 to DC1/2).

Invalid sitenumber ([not numeric] [>4] [<1]) in line The ACDDPARM SYMM parameter listed in the message references a site ID which isinvalid for the indicated reason.

Invalid site on line. Expected one of list A GENERATE parameter references an invalid site. In 3-site configurations, only DC3is valid. In 4-site configurations, only DC3 and DC4 are valid.

Larger number of SQAR ra-groups site1-site2 (count) versus

site3-site1 (count) in Symmetrix symmserial at site1 In a 4-site configuration, the number of SRDF groups for the DC1-DC2 and DC3-DC4site pairs must be smaller than the number of ASYNC SRDF groups in the samestorage system.

No GK Pool defined for Symmetrix symmserial (gk) at Site site-

id No SYMM parameter is found listing gatekeeper addresses for the listed storagesystem.

No INCLUDE parameters found in ACDDPARM ACDDPARM must have at least one INCLUDE parameter. Every SRDF group forwhich RDF.DEVICES parameters are expected must have an INCLUDE or aGENERATE parameter.

No includes connect Symmetrixes for site-pair site-site No INCLUDE or GENERATE parameter is found referencing an SRDF group from theindicated site pair.

No includes refer to Symmetrix symmserial at site-id No INCLUDE or GENERATE parameter is found referencing an SRDF group from theindicated storage system.

No parameters in ACDDPARM GDDRACDD found the dataset pointed to by ACDDPARM to contain no recognizableparameters. For information about valid ACDDPARM parameters, see the GDDRProduct Guide for your configuration.

No RDF.DEVICES parameters for site pair site-site GDDRACDD was called with GLOBALS(CHECK) and found no RDF.DEVICESparameters for a required site pair. GDDRACDD will flag this as a configuration errorand set DCN.Unplanned.CFG=1. Rerun GDDRACDD without the GLOBALS(CHECK)argument, to discover your DASD configuration and perform a parameter ACTIVATE.

One of srdfgrp and srdfgrp on line requires an INCLUDE A GENERATE parameter has a pair of SRDF groups, none of which have an INCLUDEparameter

One of symmserial1 symmserial2 on line must be located at DC3.

Found site1 and site2. Only one of symmserial1 serial2 on line must be located at DC3. In 3-site


●

●

●

●

●

●

●

●

●

●

configurations, one and only one of the specified storage systems must be located atDC3.

is required. Sitelist: site-list ACDDPARM should have a CSYSSITE parameter for DC2 or DC3, or both.

One of sites DC2, DC3 must have storage defined. Sitelist:

site-list from [ACDDPARM] [GDDRPARM] No SYMM parameters are found for DC2 or DC3. GDDRACDD will flag this as aconfiguration error and set DCN.Unplanned.CFG=1 if it was called withGLOBALS(CHECK).

Only one of srdfgrp,srdfgrp is allowed to be virtual on line A GENERATE parameter has a pair of SRDF groups both of are virtual groups.

Parameter n for site1-site2 is not a mirror image of

parameter-value GDDRACDD was called with GLOBALS(CHECK) and found that an RDF.DEVICESparameters for the listed site pair is not the mirror image of the same numberedparameter for the mirror site pair. The message lists the parameter value.GDDRACDD will flag this as a configuration error and set DCN.Unplanned.CFG=1.Rerun GDDRACDD without the GLOBALS(CHECK) argument, to discover your DASDconfiguration and perform a parameter ACTIVATE.

Parameter n for site1-site2 is of a different type than

parameter-value GDDRACDD was called with GLOBALS(CHECK) and found that an RDF.DEVICESparameters for the listed site pair is of a different type than the same numberedparameter for the mirror site pair. The message lists the parameter value. Type refersto the Internal (0) and External (1) RDF.DEVICES parameter types. GDDRACDD willflag this as a configuration error and set DCN.Unplanned.CFG=1. Rerun GDDRACDDwithout the GLOBALS(CHECK) argument, to discover your DASD configuration andperform a parameter ACTIVATE.

Parameter not defined: parameter. A GDDR parameter essential to GDDRACCD was not found in the global variables.Follow GDDR installation instructions, including activation of parameters. IfGDDRACDD is running with GLOBALS(CHECK) it will flag this as a configurationerror and set DCN.Unplanned.CFG=1.

RA-group srdfgrp in site1-site2 parameter value does not exist

in Symmetrix symmserial at site1 An RDF.DEVICES parameter is found using an SRDF group which does not exist inthe storage system located by the listed parameter. GDDRACDD will flag this as aconfiguration error and set DCN.Unplanned.CFG=1. Rerun GDDRACDD without theGLOBALS(CHECK) argument and perform a parameter Activate.

Ra-groups on line must be specified as pairs A GENERATE parameter does not properly format its list of SRDF groups as pairs(..,..),(..,..),....

{Running in compatibility mode|Running while GDDRMAIN is down}

but global variable validation is requested The indicated condition is detected when GDDRACDD is invoked with theGLOBALS(CHECK) argument. Either correct the condition or rerun without theGLOBALS(CHECK) argument.

{Running in compatibility mode|Running while GDDRMAIN is down}

but there are no [CSYSSITE] [SYMM] parameters in ACDDPARM. The indicated condition is detected which requires the presence of CSYSSITE andSYMM parameters in ACDDPARM. Either correct the condition or add the missingparameters.


●

●

●

●

●

●

●

●

●

●

Site DC1 must have storage defined. Sitelist: site-list No ACDDPARM SYMM parameter is found referencing DC1. GDDRACDD will flag thisas a configuration error and set DCN.Unplanned.CFG=1 if it was called withGLOBALS(CHECK).

Site DC4 is required in a 4-Site config. Site list: site-list ACDDPARM has 4 CSYSSITE parameters, but DC4 is missing.

Too many sites in SYMM-list in [ACDDPARM] [GDDRPARM] The maximum number of sites referenced in SYMM parameters is equal to thenumber of C-systems plus 1. GDDRACDD will flag this as a configuration error and setDCN.Unplanned.CFG=1 if it was called with GLOBALS(CHECK).

Virtual group must connect DC1-DC4 or DC2-DC3. Found site1-

site2 on line In 4-site configurations, a virtual group is only allowed on the "cross-hair"connections.

Virtual group srdfgrp cannot be an existing group in

symmserial on line A VGROUP parameter in ACDDPARM tried to define a group which does exist in theindicated storage system.

Unable to determine a Discovery path for Symmetrix symmserial

. Please specify a path in ACDDPARM The automatic path selection algorithm in GDDRACDD was unable to find a discoverypath for the listed storage system.

Unknown Site referenced on line A PATH parameter in ACDDPARM references a site for which no SYMM parameter isfound.

Unknown Site site-id specified as CPDS A CONFIG argument was specified, referencing a site ID for which no SYMMparameter is found.

Unknown Symmetrix symmserial on line A VGROUP parameter in ACDDPARM referenced a storage system serial number forwhich no SYMM parameter was found.

Unknown Symmetrix serial number referenced on line A PATH parameter in ACDDPARM references a storage system for which no SYMMparameter is found.

Action Depending on the reason indicated, correct your GDDR parameters, or run GDDRACCDwhere supported. References to RDF.DEVICES can be replaced with DLM.DEVICES ifGDDRACDD is run with the DLM(Y) argument.

GDDP401I

Cause GDDR Automated Configuration Check - DASD found no errors during the verification ofthe indicated device range in the specified storage system. Action None.

GDDP402I

Site: site-id, Symm: symmserial, GK-RAG: gk-srdfgrp, Range:symdv#1-symdv#2, verified OK


●

●

Cause GDDR Automated Configuration Discovery DASD reports on the discovery of the storagesystems defined on SYMM parameters. The message appears in 2 formats:

Format 1 simply announces the start of the discovery process.

Format 2 reports the completion of the discovery for the indicated storage system at

the indicated site, and shows the amount of subpool 132 storage used. Action None.

GDDP403E

Cause GDDR Automated Configuration Check - DASD found that the indicatedPowerMax/VMAX device number, defined to GDDR, does not exist in the indicatedstorage system. Action Correct the GDDR RDF.DEVICES parameters or have the storage system configurationadapted to the GDDR parameters.

GDDP404I

Cause GDDR Automated Configuration Check - DASD found no errors during the verification ofthe indicated device range in the indicated storage system. Action None.

GDDP405E

Cause GDDR Automated Configuration Check - DASD found different SRDF groups than the onegroup defined to GDDR for the indicated device in the indicated storage system. Action Correct GDDR RDF.DEVICES parameters to match the storage system configuration, orchange the configuration to match the GDDR parameters.

GDDP406E

Cause

Format 1:

Beginning Discovery of Symmetrix unitsFormat 2:

Site: site-id Symm: symmserial SP132 usage: virtual-storage-bytes

Site: site-id Symm: symmserial GK-RAG: gk-srdfgrp Device:symdv# not configured.

Site: site-id Symmetrix: symmserial GK-RAG: gk-srdfgrp Range:symdv#1-symdv#2 verified OK.

Site: site-id Symm: symmserial GK-RAG: gk-srdfgrp Device:symdv# Expected group: srdfgrp Found: srdfgrp

Site: site-id Symm: symmserial GK-RAG: gk-srdfgrp Device:symdv# Expected groups: srdfgrp Found: srdfgrp


GDDR Automated Configuration Check - DASD found different SRDF groups than thosedefined to GDDR for the indicated device in the indicated storage system. Action Correct GDDR RDF.DEVICES parameters to match the storage system configuration, orchange the storage system configuration to match the GDDR parameters.

GDDP407E

Cause GDDR Automated Configuration Check - DASD found a different SRDF device personalitythan expected based on configuration and topology information in current GDDRparameters. (R1/R2) Action Correct GDDR RDF.DEVICES parameters to match the storage system configuration, orchange the configuration to match the GDDR parameters.

GDDP408E

Cause GDDR Automated Configuration Check - DASD found a device at DC3 with more than oneSRDF group configured. One of the groups is an external group. Although external groupsare supported on all SRDF legs of a GDDR configuration, these groups are not allowed tobe configured with a second SRDF group on the same devices at DC3. Action Remove one of the SRDF relationships at DC3 for devices defined as external to GDDR, orupdate the GDDR parameters to define these devices as belonging to the SRDF/Starenvironment in an R22 configuration.

GDDP410I

Cause This is a separator line identifying site and storage system for the PowerMax/VMAXdevice ranges report that follows. Action None.

GDDP411I

Cause This is the title line for the PowerMax/VMAX device range report, generated at the end ofthe GDDR Automated Configuration Check - DASD. Action

GDDP412I

Site: site-id Symm: symmserial GK-RAG: gk-srdfgrp Device: symdv#Expected srdftype Found: srdftype

Site: DC3 Symm: symmserial, GK: gk, Device: symdv#, Found morethan 1 ra-group srdfgrp, with external group(s): srdfgrp

Site: site-id - Device ranges in Symm: symmserial (level) GK: gk

LDEV-HDEV-COUNT-HTM-MBR- CYLS -MR- RDF-RDFGROUPS

ldev-hdev-count-htm-mbr- cyls -mr- srdf-srdfgroups


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

Cause This message is used to display details lines of the GDDR Automated Configuration Check- DASD report.The following columns are reported in the GDDP412I messages:

ldev - Starting PowerMax/VMAX device number for the discovered device range in

the storage system identified by message GDDP410I. These are the “local” devices,

as seen from the perspective of that storage system.

hdev - Ending PowerMax/VMAX device number for the discovered device range in

the storage system identified by message GDDP410I. These are the “local” devices,

as seen from the perspective of that storage system.

count - The number of PowerMax/VMAX devices in the reported range. For FBA

meta devices, this includes both the meta heads and the meta member devices in this

range.

htm - The local device type, reported as three flags:

h denotes the host type, which can be:

C for CKD devices

F for FBA devices

A for AS/400 devices

S for special devices. The following special devices are recognized:

SVC: VCMDB devices

SIB: Internal BCV devices

SWO: WORM devices

SFI: Symmetrix File-system devices

SVA: Symmetrix Vaulting devices

SDU: Dummy devices

STH: Thin Backend devices

t denotes the TimeFinder type, which can be:

B for BCV devices

S for standard devices

m denotes the meta type, which can be:

H for meta heads

M for meta members

- for non-meta devicesFor FBA meta devices, an 'FSH' or 'FBH' range typically includes meta headsand meta members.

mbr - For meta-devices, this is the number of PowerMax/VMAX devices making up

each meta device. This number includes the meta head. Reported as '---' for non-

meta devices.

mr - The number of cylinders per device. For meta head devices, this is the total

number of cylinders summed over all devices in the meta. For meta members, this is

the number of cylinders per member.

cyls - The RAID type, which can be:

--: device has no local protection

-0: RAID-0 device (striping, not a protection level really)


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

-5: RAID-5 device (can be 3+1 or 7+1)

-6: RAID-6 device (can be 6+2 or 14+2)

-1: RAID-1 device (local mirroring)

10: RAID-10 deviceFor RAID-10, also known as CKD meta devices (striped by definition), if they areRAID-1, it is shown as '-1', not '10'.

srdf - The local (that is, in the PowerMax/VMAX system being discovered) SRDF

personality of the devices in the reported range. It is reported as follows:

----: not an SRDF device

R1--: R1 device

R2--: R2 device

R11-: Concurrent SRDF device, R1 in both reported SRDF groups.

R12-: R21 device which is R1 in first RA-group, R2 in second SRDF group

R21-: R21 device which is R2 in first RA-group, R1 in second SRDF group

R22-: R22 device

srdfgroups - Because of the RDFGROUPS portion, the GDDP412I message can be

spread over 2 lines. There will be 1 line per SRDF group to which the reported device

range belongs. The SRDF groups are always listed in ascending order. The RDFGROUPS portion of the GDDP412I message consists of 7 fields, separatedby '/':nn/ceutc/sambd/urni/tttttttt/sssssssss/ldev-hdev

nn - 2-digit SRDF group number.

ceutc - This field reflects the ConGroup status, reported as 5 flags:

c for ConGroup flag, which can be:

C: ConGroup flag

-: No ConGroup flag

e for ECA flag, which can be:

E: ECA flag

-: No ECA flag

u for UNR-on-Timeout flag, which can be:

U: UNR-on-Timeout flag

-: No UNR-on-Timeout flag

t indicates whether ConGroup trip occurred:

T: ConGroup trip occurred

-: No ConGroup trip occurred

c represents the ECA window status, which can be:

O: ECA window is open

C: ECA window is closed normally

T: ECA window is closed due to a timeout

samdb - This field reflects the SRDF status/mode, reported as 5 flags:

s for SRDF replication status, which can be:

T: The devices are TNR

-: The devices are not TNR

a shows if SRDF/A is active:


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

A: SRDF/A is active

-: SRDF/A is not active

m indicates the MSC mode as follows:

-: Not in MSC mode

0: The MSC cycle tag

8: The MSC cycle tag

C: The MSC cycle tag

E: The MSC cycle tag

F: The MSC cycle tag

d indicates the Adaptive Copy Disk mode status, which can be:

D: ADCOPY-DISK mode

-: Not in ADCOPY-DISK mode

b indicates the Link-Blocked status:

B: Link-Blocked

-: No Link-Blocked

urni - This field reflects the host availability status, reported as 4 flags:

u for the UNR status:

U: UNR

-: Not UNR

r for the RNR status:

R: RNR

-: No RNR

n for the NR status:

N: Not ready

R: Read-only

W: Write-enabled

i for the ITA attribute:

I: ITA

-: No ITA

tttttttt - This field has different meanings for SRDF/S versus SRDF/A devices:

For SRDF/S devices, this is the ConGroup hash code.

For SRDF/A devices, this is the MSC group name.

sssssssss - The PowerMax/VMAX serial number on the other side of this SRDF

group.

ldev-hdev - Starting and ending PowerMax/VMAX device numbers at the other

side of this SRDF group.For GDDR-managed SRDF groups only, the RDFGROUPS field can be appended with thefollowing additional columns:

T: The SRDF group type indicator that shows inclusion type for included SRDF

groups:

I: This is an internal GDDR-managed group with regular DASD devices.

E: This is an external GDDR-managed group with regular DASD devices.

ID: This is an internal GDDR-managed group with DLM backend devices.

ED (not currently used): This is an external GDDR-managed group with DLM


●

●

●

●

●

●

●

●

●

●

backend devices.The first GDDP412I message for a device can have 3 additional columns, showing BCVinformation in 3 fields under the G, T and I headers (GOLD set, TEST set, Ignored). This isstate information about BCV devices associated with the GDDR-managed SRDF devicerange listed in this GDDP412I message.The following format is used: (xG) (xT) (nn):

(xG): Provides information about the GOLD set BCVs, blank if none requested.

(xT): Provides information about the TEST set BCVs, blank if none requested.

(nn): A numeric value in the I column, indicates how many additional BCV devices

are found associated with the listed SRDF devices, on top of the BCVs defined to

GDDR. These additional BCV devices are ignored by GDDR. This field is blank if no

not-requested BCVs are found.These fields are shown as spaces if there is no relevant information.If BCV devices are requested in the GOLD or TEST sets, they can have the followingvalues:

!G or !T: A BCV was requested in the indicated set, but none is found.

-G or -T: A BCV was requested, found associated, but is currently SPLIT.

>G or >T: A BCV was requested, found associated, and attached due to a (RE-)

ESTABLISH.

<G or <T: A BCV was requested, found associated, and attached due to a RESTORE.

?G or ?T: A BCV was requested, found associated, but GDDRACDD cannot determine

the state of the BCVs. Action None.

GDDP415I

Cause This message is issued by various GDDR modules to show relevant input. This includescommand line arguments, input parameters, and configuration variables. Action None.

GDDP415W

Cause These messages are issued by GDDR Automated Configuration Discovery for DASD utilityto draw attention to non-fatal issues related to the command line arguments and inputparameters.The following conditions are identified:

The following lines in ACDDPARM were ignored: - Lists lines in the

input parameters which were not recognized. Review this and remove these lines or

convert them to a recognized GDDRACDD parameter.

GENERATE parameters ignored with 2-site configurations - A

GENERATE parameter is found but the configuration being defined has only 2 sites in

SYMM parameters.

message-text

message-text


●

●

●

●

ALIGN was specified or defaulted, but an asymmetrical

configuration was discovered. Generated RDF.DEVICES parameters

may not be aligned - This message is issued at the completion of storage

systems to explain why RDF.DEVICES are not aligned on the expected boundaries.

Failed to open ddname (mode) with RC=rc - GDDRACDD attempted to

open the indicated optional ddname, but failed with the indicated EXECIO return

code. Action See guidance for each condition above.

GDDP416I

Cause These messages are issued by GDDR Automated Configuration Check - DASD and GDDRAutomated Configuration Discovery - DASD to show summary information for discoveredstorage systems. Action None.

GDDP417I

Cause These messages are issued by GDDR Automated Configuration Discovery DASD to showsummary SRDF group information. The messages come in 2 sections:

List of SRDF groups linking GDDR-managed storage systems - Lists all SRDF groups

between storage systems for which a SYMM parameter is found, organized by site

pair. For each group, an indication is given of its inclusion type (Internal,

External, or None). Offline groups are marked as <<< OFFLINE <<<. Virtual

groups are marked - VIRTUAL. Groups connecting same site storage systems are

marked - ignored.

Unique GDDR SRDF groups by site pair and type - Lists all included SRDF groups.

First the internal groups, then the external groups. For each type, the list is organized

by site pair. Action None.

GDDP418I

Cause These messages are issued by GDDR Automated Configuration Discovery DASD to showCREATEPAIR commands that can be used to create the GDDR-managed environment.The commands are organized by group type (Internal/External) and by site pair. Thecommands are listed in both directions assuming they will be only be issued in onedirection. The user is free to choose a direction, e.g. based on availability of channelconnectivity to the storage systems at one site and not the opposite site in a site pair.

message-text

message-text

message-text


●

●

●

●

GDDRACDD provides guidance on the usage of the LCLISR1/LCLISR2 commandparameters, based on the CONFIG argument. Action None.

GDDP419I

Cause These messages are issued by GDDR Automated Configuration Discovery DASD to showthe RDF.DEVICES parameters which were generated for the discovered configuration.The parameters are organized by group type (internal or external) and by site pair. Action None.

GDDP420E

Cause GDDR Automated Configuration Check - DASD found configuration errors. These can bemismatches between GDDR parameters and the real storage system configuration, oroutright storage system configuration issues. References to RDF.DEVICES can bereplaced with DLM.DEVICES if GDDRACDD is run with the DLM(Y) argument.The following errors are identified:

All devices paired DCm-DC3 in group srdfgrp in Symmetrix

symmserial should be paired DCn-DC3 in the same group. Found

srdfgrp and srdfgrp - (DCm =DC1 or DC2. DCn is the other site). In a 3-site

configuration, devices are found to be protected on the DCm-DC3 and DCn-DC3

legs, but there is more than one DCn-DC3 group for the indicated DCm-DC3 SRDF

group. This is an invalid 3-site configuration. GDDRACDD sets RC=16 for this

condition. Delete device pairs from the unwanted group and create device pairs in the

wanted group.

Device pairs discovered for groups srdfgrp and srdfgrp in

Symmetrix symmserial at site-id. - In a 4-site configuration, both groups

associated in a GENERATE parameter are found to have device pairs. (If there is no

GENERATE parameter for this group then a group was associated by the discovery

process.) This is not supported. GDDRACDD sets RC=16 for this condition. Delete

device pairs in all groups spanning site pairs DC1-DC4 and DC2-DC3.

Device pairs discovered for site-id-site-id group srdfgrp in

Symmetrix symmserial. - In a 4-site configuration, device pairs are found in

the indicated SRDF group which spans the indicated site pair, which is one of DC1-

DC4 or D2-DC3. This is an invalid 4-site configuration. GDDRACDD sets RC=16 for

this condition. Delete device pairs from the unwanted group.

Device range symdv#-symdv# in Symmetrix symmserial is

paired DCm-DC3 but not DCn-DC3, and no GENERATE parameter for

srdfgrp. - In a 3-site configuration, the indicated device range is found to be

protected on the DCm-DC3 leg, but not on the DCn-DC3 leg. This requires the

message-text

Error: description


●

●

●

●

●

●

presence of a GENERATE parameter for the indicated SRDF group but none was

specified. GDDRACDD sets RC=8 for this condition. Create device pairs for the

missing leg or add a GENERATE parameter associating the indicated SRDF group

with a group on the DCn-DC3 leg that has device pairs. Alternatively, rerun

GDDRACDD with FORCE, which may succeed in creating an incomplete set of

RDF.DEVICES parameters.

Device symdv# in Symmetrix symmserial at site-id is paired

with device symdv# in Symmetrix symmserial at site-id, but the

remote device is unpaired in group srdfgrp. - GDDRACDD has

discovered a half-delete situation and is unable to generate RDF.DEVICES

parameters. GDDRACDD sets RC=16 for this condition. Correct the indicated device

pairing error.


with device symdv# in Symmetrix symmserial at site-id, but the

remote device is paired with symdv# in srdfgrp. - GDDRACDD has

discovered an error in device pairing and is unable to generate RDF.DEVICES

parameters. GDDRACDD sets RC=16 for this condition. Correct the indicated device

pairing error.

Device symdv# is defined to GDDR in range symdv#-symdv#, but

could not be found in ra-group srdfgrp in Symmetrix symmserial

at site-id. - The listed device is defined to GDDR but does not exist in the

indicated SRDF group. GDDRACDD sets RC=8 for this condition. GDDRACDD will

flag this as a configuration error and set DCN.Unplanned.CFG=1. Rerun GDDRACDD

without the GLOBALS(CHECK) argument and perform a GDDR parameter activation.

Alternatively CREATEPAIR the listed devices to adapt the configuration to the

existing GDDR parameters.

Device symdv# is type1 in ra-group srdfgrp in Symmetrix

symmserial at site-id. Expected type2. - The listed device was

expected to be of type R1 or R2 but was found to be of the opposite type.

GDDRACDD sets RC=8 for this condition. GDDRACDD will flag this as a configuration

error and set DCN.Unplanned.CFG=1. Rerun GDDRACDD without the

GLOBALS(CHECK) argument and perform GDDR parameter activation. Alternatively

SWAP or HSWAP the listed devices to adapt the configuration to the existing GDDR

parameters.

Devices symdv#-symdv# in ra-group srdfgrp in Symmetrix

symmserial at site-id are not defined to GDDR.- The indicated

SRDF group is defined to GDDR, but the listed devices are discovered in the storage

system, but are not defined to GDDR. GDDRACDD sets RC=8 for this condition.

GDDRACDD will flag this as a configuration error and set DCN.Unplanned.CFG=1.

Rerun GDDRACDD without the GLOBALS(CHECK) argument and perform GDDR

parameter activation. Alternatively DELETEPAIR the listed devices to adapt the

configuration to the existing GDDR parameters.

Different device pairs discovered for groups srdfgrp and


●

●

●

●

●

srdfgrp in Symmetrix symmserial at site-id. - In a 3-site

configuration, both indicated groups, associated either by a GENERATE parameter or

by the discovery process have some device pairs, but some devices are paired in only

one of the groups. This is not a valid 3-site configuration. GDDRACDD sets RC=8 for

this condition. Create complete sets of device pairs in both groups. Or: delete all

existing device pairs from one of the groups and add a GENERATE parameter for it.

Alternatively, rerun GDDRACDD with FORCE, which may succeed in creating a

complete or incomplete set of RDF.DEVICES parameters.

Expected Link-Block not found for devices symdv#-symdv# in ra-

group srdfgrp in Symmetrix symmserial at site-id. - In a 3-site or

4-site configuration, the listed device range was not found to be Link-Blocked

although it should be, according to GDDR configuration information. GDDRACDD

sets RC=8 for this condition. GDDRACDD will flag this as a configuration error and

set DCN.Unplanned.CFG=1 .

Expected rdf-type type1 for devices symdv#-symdv# in ra-group

srdfgrp in Symmetrix symmserial at site-id. Found type2. - The

listed devices are found to be of type R1 or R2 in the indicated SRDF group, but

should be of the opposite type according to current GDDR global variables.

GDDRACDD sets RC=8 for this condition. GDDRACDD will flag this as a configuration

error and set DCN.Unplanned.CFG=1 Rerun GDDRACDD without the

GLOBALS(CHECK) argument and perform GDDR parameter activation. Alternatively

SWAP or HSWAP the listed devices to adapt the configuration to the existing GDDR

parameters.

Invalid SRDF/Star configuration: site-id-site-id device range

symdv#-symdv# in Symmetrix symmserial has no site-id-site-id

protection. - In a 3-site configuration, a device is found to be SRDF protected

on a DCm-DC3 leg, but not on the DC1-DC2 leg. This is an invalid Star configuration.

GDDRACDD sets RC=16 for this condition. Create device pairing in such a way that

all SRDF/A devices also have SRDF/S protection.

No device pairs discovered for site-id-site-id group srdfgrp

in Symmetrix symmserial at site-id. - In a 2-site or 4-site

configuration, the indicated SRDF group spans the indicated site pair which must

have device pairs configured to make a valid configuration. GDDRACDD sets RC=8

for this condition. Create device pairs in the indicated SRDF group. Alternatively,

rerun GDDRACDD with FORCE, which may succeed in creating an incomplete set of



in Symmetrix symmserial at site-id and associated group

srdfgrp. - In a 3-site configuration, the indicated SRDF group spans the

indicated site pair which must have device pairs configured to make a valid

configuration, unless there is a useable other group associated with it in a

GENERATE parameter. There is a GENERATE parameter for the indicated group but

the associated group also has no device pairs. GDDRACDD sets RC=8 for this


●

●

●

●

●

●

●

condition. Create device pairs in at least one of the associated groups. Alternatively,

rerun GDDRACDD with FORCE, which may succeed in creating an incomplete set of



in Symmetrix symmserial at site-id and no other group

associated in a GENERATE parameter. - In a 3-site configuration, the

indicated SRDF group spans the indicated site pair which must have device pairs

configured to make a valid configuration, unless there is a useable other group

associated with it in a GENERATE parameter. GDDRACDD sets RC=8 for this

condition. Create device pairs in the indicated SRDF group, or rerun GDDRACDD

with an appropriate GENERATE parameter for this group. Alternatively, rerun

GDDRACDD with FORCE, which may succeed in creating an incomplete set of


Replication for device symdv# RA(srdfgrp) in Symmetrix

symmserial at site-id does not form a triplet quadruplet.


with symdv# in Symmetrix symmserial. - In a 3- or 4-site configuration, a

device is found to be SRDF protected on all required legs, but the last leg does not

point back to the device of origin. GDDRACDD sets RC=16 for this condition. Create

device pairing in such a way that a closed triplet (in 3-site configurations) or

quadruplet (in 4-site configurations) is created for all GDDR-managed devices.

Required site-id-site-id replication not found for device

symdv# RA(srfdgrp) in Symmetrix symmserial at site-id. Check

device symdv# in Symmetrix symmserial at site-id. - In a 3- or 4-

site configuration a required SRDF protection was not found for the indicated device.

The error occurred on the SRDF hop indicated by the second device indicated in the

message. GDDRACDD sets RC=16 for this condition. Provide SRDF protection on all

SRDF legs required in the configuration.

Site pair site-id-site-id has device pairs in some groups, but

group srdfgrp in Symmetrix symmserial at site-id has no device

pairs. - In a 3-site configuration, the indicated SRDF group spans the indicated

site pair and has no device pairs, while other groups for the same site pair do have

device pairs. This is not a valid 3-site configuration. GDDRACDD sets RC=8 for this

condition. Create device pairs in the indicated group. Alternatively, rerun GDDRACDD

with FORCE, which may succeed in creating a complete or incomplete set of


Site: site-id Symm: symmserial Meta-member: symdv# has

different ra-groups than head symdv# (mbr-groups versus head-

groups) - Contact Dell EMC Customer Support.


different RAID-level than head symdv# (mbr-level versus head-

level) - Contact Dell EMC Customer Support.



●

●

●

●

●

●

different RDFtype than head symdv# (mbr-type versus head-type

) - Contact Dell EMC Customer Support.

Unable to generate site-id-site-id device pair for range

symdv#-symdv# in Symmetrix symmserial (GK gk) at site-id.

Found ra-group srdfgrp for range symdv#-symdv# in Symmetrix

symmserial (GK gk) at site-id. Expected ra-group srdfgrp. -

In a 3- or 4-site configuration, GDDRACDD is unable to create an RDF.DEVICES

parameter as requested through a GENERATE parameter. Some devices did have

device pairing allowing parameter generation, but other devices are found to be

protected in a different SRDF group. GDDRACDD sets RC=16 for this condition.

Delete device pairing in the unwanted group and create it in the wanted group.

Unable to generate site-id-site-id device pair for range

symdv#-symdv# in Symmetrix symmserial (GK gk) at site-id. No

site-id-site-id ra-group found for range symdv#-symdv# in

Symmetrix symmserial (GK gk) at site-id. (Groups found:

srdfgrp-list). - In a 3- or 4-site configuration, GDDRACDD is unable to create

an RDF.DEVICES parameter as requested through a GENERATE parameter. The

message identifies which element if missing from the configuration as well as the

groups found for the device range. GDDRACDD sets RC=16 for this condition. Create

the missing device pairing.

Unexpected Link-Block found for devices symdv#-symdv# in ra-

group srdfgrp in Symmetrix symmserial at site-id. - In a 3-site or

4-site configuration, the listed device range was found to be Link-Blocked although it

should not be, according to GDDR configuration information. GDDRACDD sets RC=8

for this condition. GDDRACDD will flag this as a configuration error and set

DCN.Unplanned.CFG=1 . Action See above for each condition indicated.

GDDP421W

Cause GDDR Automated Configuration Discovery - DASD utility (GDDRACDD) found a conditionwhich might either result in incorrect RDF.DEVICES parameters or cause issues duringGDDR scripts.The following conditions are identified:


different RDF-mirror flags than head symdv# (mbr-flags versus

head-flags) - Contact Dell EMC Customer Support.


different ADCOPY flag than head symdv# (mbr-flag versus head-

flag) - Contact Dell EMC Customer Support.


different CG flags than head symdv# (mbr-flag versus head-flag

Warning: message-text


●

●

●

●

●

●

●

●

●

●

) - Contact Dell EMC Customer Support.

Site: site-id Symm: symmserial GK: gk RA: srdfgrp. - NON-GDDR

group rag found for GDDR-managed device range. This could cause GDDR script

issues when R21 devices could be created while the non-GDDR group is not in

ADCOPY-DISK mode.For information about other conditions that can be reported in message GDDP421W, seethe description of the GDDRACDD utility output in the GDDR Product Guide for yourconfiguration. Action See above for each condition indicated.

GDDP422I

Cause These messages are issued by GDDR Automated Configuration Discovery DASD to showFBA meta device information in GDDR-managed SRDF groups. The listing is organized bygroup type (internal or external) and by site pair. Action None.

GDDP430I

Cause This is the title message for this report. It indicates whether the report will list directorsonly for GDDR-managed SRDF groups or for all SRDF groups in storage systems known toGDDR. The message shows the Mainframe Enablers version and the site where the reportutility is running. Action None.

GDDP431I

Cause This is the SRDF group entry in the SRDF group-oriented section of the GDDR SRDFDirectors overview report. The following information is shown:

srdf-type - The type of SRDF group being reported:

I - Internal, consistency protected group

E - External group

N - Non-GDDR group

site-id - Site at one end of the SRDF group

gk - GDDR system home-site gatekeeper

symmserial - Storage system serial number at one end

(level) - Operating environment level (major) of that storage system

srdfgrp - SRDF group number at one end

message-text

GDDR SRDF Directors overview for {GDDR|ALL} ra-groups - mfe-version running at site-id

(srdf-type) site-id gk symmserial (level) srdfgrp -{OFF|ONL}-srdfgrp symmserial (level) gk site-id [*]


●

●

●

●

●

●

●

●

●

●

●

●

●

●

{OFF|ONL} - The SRDF group state (offline or online). If a group is offline, it will be

called out by an '*' at the end of the line.

srdfgrp - The SRDF group number at other end

symmserial - Storage system serial number at other end

(level) - Operating environment level (major) of that storage system. Will be shown

as ---- if unable to determine.

gk - GDDR system other end home-site gatekeeper. Will be shown as ---- for non-

GDDR systems.

site-id - The site at other end of the SRDF group. Can be shown as UNK for non-

GDDR SRDF groups.

* - when present, an * indicates an offline SRDF group. Action None.

GDDP432I

Cause This is the director entry in the SRDF group oriented section of the GDDR SRDF Directorsoverview report.This message is presented as two halves, each half showing information for directors atone end of the SRDF group listed previously with a GDDP431I message. There is one lineper director used by the SRDF group. If the number of directors used at one end is smallerthan what is used at the other end, additional entries at that end are shown as: -- --- ------ -------.The following information is shown for each director.

The director number in hex

The director type: F for Fibre channel or E for GigE.

ONL(Y/N) indicates whether the director is online or not. If a director is 'DD' this is

shown as --DD--.

CONN(Y/N):

Y: director has at least one port connected

N: director has no ports connected

error-flag - When present, an * calls out any director at either side which is either

offline, or 'DD' or has no ports connected. Action None.

GDDP435I

Cause This is the site entry in the director-oriented section of the GDDR SRDF Directorsoverview report. It indicates the site where the storage systems identified in laterGDDP436I messages are located.Can be shown as 'UNK' for storage systems not known to GDDR but connected to aGDDR-managed system by any SRDF group.

dir# (type) ONL(Y/N) CONN(Y/N) dir# (type) ONL(Y/N) CONN(Y/N)error-flag

Site: site-id


●

●

●

●

●

●

●

●

●

●

●

Action None.

GDDP436I

Cause This is the storage system entry in the director-oriented section of the GDDR SRDFDirectors overview report. It identifies the storage system at the site indicated in theprevious GDDP435I message, where the SRDF groups in later GDDP437I and GDDP438Imessages are configured.The following information is shown:

Storage system serial number

Operating environment level (major), shown as ---- if unable to determine

GDDR system home site gatekeeper

The gatekeeper and up to 2 SRDF groups used to build a path for the report utility to

reach this storage system Action None.

GDDP437I

Cause This is the director entry in the director-oriented section of the GDDR SRDF Directorsoverview report. It identifies the director number used by the SRDF groups from laterGDDP438I messages.The following information is shown:

The director number in hex

The director type: F for Fibre channel or E for GigE.

ONL(Y|N) indicates whether the director is online or not. If a director is 'DD', this is

shown as --DD--.

CONN(Y|N):

Y: director has at least one port connected.

N: director has no ports connected

error-flag - When present, an * calls out any director at either side which is either

offline, or 'DD' or has no ports connected. Action None.

GDDP438I

Cause This is the SRDF groups listing in the director-oriented section of the GDDR SRDFDirectors overview report. It lists SRDF groups, by type, used by the director identified inan earlier GDDP437I message.The following information is shown:

Symmetrix: symmserial (level) - GK: gk Path:gk[.srdfgrp[.srdfgrp]]

Director: dir# (type) ONL(Y|N), CONN(Y|N) error-flag

RA-groups: (type) srdfgrp-list


●

●

●

●

●

●

●

●

●

type - Type of SRDF groups being listed:

I - Internal, consistency protected groups

E - External groups

N - Non-GDDR groups

srdfgrp-list - Blank-separated list of SRDF groups of the indicated type, using the

director indicated in an earlier GDDP437I message. Action None.

GDDP440I

Cause The GDDR SDDF Session verification utility is starting with a run of verifications. Themessage indicates the run number and the number of scheduled runs. Action None.

GDDP441I

Cause The GDDR SDDF Session verification utility has completed a run of verifications with thereturn code indicated in the message.Possible return code values are:

0 - All GDDR-managed devices have the expected number of SDDF sessions in an

appropriate state. No action is required.

4 - During a run which is not the last run, one or more devices were found with

unchanged SDDF session time stamps. If this occurs on the last run, the return code

will be 16. No immediate action is required. Check the return code on the last run. If

necessary, increase the Interval argument. Note that this is normal when SRDF/A

has stopped or slowed cycle switching. The recommendation is to do only one run if

SRDF/A is known to have stopped cycle switching.

8 - No discovery path was found from the site where the utility runs, to one of the

storage systems managed by GDDR. A GDDR-managed SRDF group, which would be

affected by a CREATEPAIR or RESUMEPAIR DIFFERENTIAL operation in GDDR

scripts, was found offline. Run the utility at a site with channel attachment to one of

the sites affected by SDDF sessions. Ensure there is at least one online SRDF group

to each storage system at the other site. Make sure all GDDR-managed SRDF groups

required for a CREATEPAIR or RESUMEPAIR DIFFERENTIAL operation are online.

12 - One or more devices were found with more than the expected number of

sessions, or with sessions for which GDDR is unable to determine the last action or

the state of the last action. If this occurs on the last run, investigate the cause of the

SDDF session issues, as reported by message GDDP448E. This situation may be

transient during MSC activation. If the problem persists after allegedly successful

GDDRSDDF Starting SDDF session verification, run nnnn of nnnn

GDDRSDDF Completed SDDF session verification with RC=rc, run nnnnof nnnn


●

MSC activation, contact Dell EMC Customer Support. Keep the SRDF Host

Component and ResourcePak Base logs available, as well as the GDDRSDDF utility

joblog.

16 - One or more devices were found to be at risk for a Full PUSH or an unusually

large differential on the next CREATEPAIR or RESUMEPAIR DIFFERENTIAL

operation. Possible causes are the absence of SDDF sessions for a device on either

site, an invalid session state, or a lack of change in the SDDF session time stamps.

This situation may be transient during MSC Activation. It may be necessary to run

the utility with a larger interval argument. If the problem persists after allegedly

successful MSC activation, contact Dell EMC Customer Support. Keep the SRDF

Host Component and ResourcePak Base logs available, as well as the GDDRSDDF

utility joblog. The affected devices will be called out in the GDDRSDDF utility joblog

with a GDDP448E or GDDP449W message. Note that return code 16 can occur when

the utility is run with D(Y) at a time when MSC is performing normal cycle switching

and SDDF rotations. Do not use D(Y) under these circumstances, as the estimated

differential will be very inaccurate, at best. This can also occur when running the

utility with N > 1, at a time when SRDF/A is known to be dropped. In this situation,

SDDF session time stamps are not expected to change, so the utility should be run

with N(1). Action See above per return code.

GDDP442E

Cause The GDDR SDDF Session verification utility was invoked with invalid arguments. Action Review the GDDRSDDF documentation and usage instructions in hlq.GDDRnnn.SAMPLIB(GDDRSDDF). Correct the arguments and resubmit the job.

GDDP443E

Cause The GDDR SDDF Session verification utility could not find a usable path from the sitewhere the utility runs to the listed storage system. Alternatively, the utility found a GDDR-managed group in an OFFLINE state. Action If a storage system cannot be discovered, GDDRSDDF skips SDDF session verification forthe listed storage system, and proceeds with verification of SDDF sessions in otherstorage systems. Dell EMC recommends running the GDDRSDDF utility from a site whichis channel attached to one of the sites affected by SDDF sessions. Ensure there is anonline SRDF group for each remote storage system expected to have SDDF sessions.If a GDDR-managed group is found OFFLINE, discovery may succeed for all storagesystems, but nevertheless, the issue should be addressed immediately. Investigate why aGDDR-managed group is OFFLINE and if possible bring it online before running any

GDDRSDDF Validation error: text

GDDRSDDF Found ra-group srdfgrp OFFLINE in Symmetrix symmserial atsite-id


●

●

●

●

●

●

●

●

●

●

●

scripts.Search the GDDR Event Monitor job log for messages resulting from its regular SRDFgroup check. (GDDR649E, GDDR650W, GDDR652E, GDDR653W, GDDR655E).

GDDP444I

Cause This is the header for the SDDF Session detail report produced by the GDDR SDDFSession Utility showing the current run and the total number of runs. Action None.

GDDP445I

Cause This is a section header in the SDDF Session detail report dedicated to the listed GDDR-managed SRDF group. The header lists the SRDF group as the central field, andinformation about the storage systems it connects to the left and right.For each side, the following information is provided:

Storage system serial number

Operating environment level (major) of the storage system

Any gatekeeper defined to GDDR at the home site of the storage system

Home site of the storage system

The site role. which can be SiteA, SiteB, SiteC, or SiteDPossible site roles on the left side:

Concurrent SRDF/Star: SiteB

Cascaded SRDF/Star: SiteA

SRDF/SQAR: SiteCPossible site roles on the right side:

Concurrent SRDF/Star: SiteC

Cascaded SRDF/Star: SiteC

SRDF/SQAR: SiteD Action None.

GDDP446I

Cause This is the column header for message GDDP447I which follows. Action None.

GDDP447E

GDDRSDDF SDDF Session information for GDDR managed devices (nnnn /nnnn)

Symmetrix symmserial (level - gk - site-id - site-role),<-- RAsrdfgrp --> Symmetrix symmserial (level - gk - site-id - site-role)

Device CYLS ID Action State Time stamp [Remark]


●

●

Cause The GDDR SDDF Session verification utility found devices with invalid SDDF sessions. Themessage identifies the reason why a session is considered invalid.Alternatively, the utility found devices at risk for a Full PUSH or an unusually largedifferential at the next CREATEPAIR or RESUMEPAIR DIFFERENTIAL. Action To avoid unnecessary Full PUSH warnings, observe the following guidelines:

When SRDF/A is dropped, run the utility with N(1)

The utility should only be run with D(Y) when there is no MSC cycle switching or

SDDF session activity expectedReview SRDF Host Component and ResourcePak Base job logs for messages indicating anMSC software or configuration issue. Contact the Dell EMC Customer Support Center fortechnical assistance.

GDDP447I

Cause This message provides detailed SDDF session information for a GDDR-managed SRDF

Format 1:

Found count SDDF sessions for device symdv# in Symmetrixsymmserial, at site-id, Expected countFormat 2:

Full PUSH risk for device symdv#, in Symmetrix symmserial, atsite-idFormat 3:

Invalid cylinder count cyl-count, for SDDF session session-id, fordevice symdv#, in Symmetrix symmserial, at site-id, Expectedexpected-cyl-countFormat 4:

Invalid cylinder count cyl-count, for SDDF session session-id fordevice symm-dev in Symmetrix symm-serial, at site-id, Not numericFormat 5:

Invalid session-ID session-id for device symdv# in Symmetrixsymmserial at site-id, Expected one of session-id1, session-id2,session-id3, session-idnFormat 6:

Last SDDF action action failed, for device symdv# in Symmetrixsymmserial, at site-id. Session: session-idFormat 7:

No Active SDDF Session found for device symdv# in Symmetrixsymmserial at site-idFormat 8:

Unable to determine last SDDF action for device symdv#, inSymmetrix symmserial, at site-id. Session: session-idFormat 9:

Unable to determine last SDDF action state for device symdv# inSymmetrix symmserial, at site-id. Session: session-idFormat 10:

Unexpected last SDDF action action for device symdv# in Symmetrixsymmserial at site-id

symdv#1 cyl-count1 session-id1 action1 state1 timestamp1remark symdv#2 cyl-count2 id2 action2 state2 timestamp2


●

●

●

●

●

●

●

●

●

●

●

●

device pair.This message has a left and a right side, as explained for message GDDP445I. In themiddle, there is a remark text providing information which may affect the nextCREATEPAIR or RESUMEPAIR DIFFERENTIAL operation for the device pair.There is one GDDP447I message per device per SDDF session.For each session, the following information is provided:

PowerMax/VMAX device number

The number of cylinders reported by the session

The 4-character session ID

The last SDDF action performed on the session, abbreviated to 6 characters. Possible

actions are: NONE, SET, RESET, REGIST, CLOSE, ACTIVATE, DEACTIVATE. ??? is

shown when GDDR is unable to determine which action was performed.

The state of the last action. Possible states are: INPROGRESS, FINISHED, FAILED.

??? is shown when GDDR is unable to determine the state of the last action.

The time of the last action in the YYYYMMDDHHMMSS format. This does not

correspond to any MVS time. The only use of the time stamp field is verification that

it changes over time, as is expected during normal MSC software activity at sites

with 2 SDDF sessions. When comparing time stamps, the utility ignores the last digit.

Remark is shared among sessions of the listed device pair. It can have a single

comment, applicable to both sides, or can have a left-aligned and/or right-aligned

comment, applicable to the left or right side device respectively, or both. The remark

column should be blank. Possible remarks are:

Offline - The GDDR-managed SRDF group is offline. The utility calls out the

affected SRDF groups with message GDDP443E. Vary the group online.The following comments can occur left-aligned, right-aligned, or both, indicating aproblem with the SDDF sessions on the indicated side of the report.

(n) - Indicates the expected number of SDDF sessions, if the utility finds a

different number of sessions. In case a session is found missing, the report fields

are shown as a series of '-'. Review the SCF job log and the GDDR Event

Monitor job log for messages indicating an MSC software or configuration issue.

The utility job log will call out these devices with a GDDP448E message.

??? - Indicates that there is at least one SDDF session on the affected side for

which GDDR is unable to determine either the last SDDF action or the state of

the last SDDF action. Review the SCF job log and the GDDR Event Monitor job

log for messages indicating an MSC software or configuration issue. The utility

job log will call out these devices with a GDDP448E message.

ACT - Indicates that there is at least one SDDF session on the affected side

where the last SDDF action is not Activate, Deactivate or Reset. Review the

SCF job log and the GDDR Event Monitor job log for messages indicating an

MSC software or configuration issue. The utility job log will call out these

devices with a GDDP448E message.

CYL - Indicates that there is at least one SDDF session on the affected side with

an incorrect cylinder count. Review the SCF job log and the GDDR Event

Monitor job log for messages indicating an MSC software or configuration issue.


●

●

●

●

The utility job log will call out these devices with a GDDP448E message.

FAIL - Indicates that there is at least one SDDF session on the affected side

for which the last SDDF action has a FAILED state. Review the SCF job log and

the GDDR Event Monitor job log for messages indicating an MSC software or

configuration issue. The utility job log will call out these devices with a

GDDP448E message.

ID - Indicates that there is at least one session with an invalid session ID. The

utility verifies that all GDDR-managed devices in any given storage system share

the same set of sessions, when looking at the last 2 digits of the session IDs.

Review the SCF job log and the GDDR Event Monitor job log for messages

indicating an MSC Software or configuration issue. The utility job log will call

out these devices with a GDDP448E message.

INA - The INA comment indicates that there are no SDDF sessions on the

affected side where the last SDDF action is ACTIVATE, although at least one

such session is expected. Review the SCF job log and the GDDR Event Monitor

job log for messages indicating an MSC software or configuration issue. The

utility job log will call out these devices with a GDDP448E message.

UNCH - The SDDF session time stamps for the device on this run did not

change compared to the first run.If this problem persists on the last run, it

might be due to a too short Interval argument. Review the SCF job log and the

GDDR Event Monitor job log for messages indicating an MSC software or

configuration issue. The utility job log will call out these devices with a

GDDP449W message.The utility job log will call out these devices with a GDDP449W message.If this problem persists on the last run, the devices are at risk for a full push and will becalled out with a GDDR448E message. If SRDF/A is known to be dropped, run the utilitywith N(1). Action Take appropriate action depending on the values shown.

GDDP448E

Format 1:

Found count SDDF sessions for device symdv# in Symmetrixsymmserial, at site-id, Expected countFormat 2:

Full PUSH risk for device symdv#, in Symmetrix symmserial, atsite-idFormat 3:

Invalid cylinder count count, for SDDF session session-id, fordevice symdv#, in Symmetrix symmserial, at site-id, Expected countFormat 4:

Invalid cylinder count count, for SDDF session session-id fordevice symdv# in Symmetrix symmserial, at site-id, Not numericFormat 5:

Invalid session-ID session-id for device symdv# in Symmetrixsymmserial at site-id, Expected one of session-id1, session-id2,..., session-idn


Cause The GDDR SDDF Session verification utility found devices with invalid SDDF sessions. Themessage identifies the reason why a session is considered invalid.Alternatively, the utility found devices at risk for a Full PUSH or an unusually largedifferential at the next CREATEPAIR or RESUMEPAIR DIFFERENTIAL. To avoidunnecessary Full PUSH warnings, when SRDF/A is dropped, run the utility with N(1). Theutility should only be run with D(Y) when there is no MSC cycle switching or SDDF sessionactivity expected. Action Review SRDF Host Component and ResourcePak Base job logs for messages indicating anMSC software or configuration issue. Contact the Dell EMC Customer Support Center fortechnical assistance.

GDDP449W

Cause The GDDR SDDF Session verification utility found devices for which the SDDF sessiontime stamps did not change compared to the first run. This could be because the utility Interval size is too small. Another cause is running theutility with N>1 when SRDF/A is dropped. Action If the problem persists, review SRDF Host Component and ResourcePak Base job logs formessages indicating an MSC software or configuration issue. Contact the Dell EMCCustomer Support Center for technical assistance.

GDDP450I

Cause This is the header for the SDDF Session Differential report produced by the GDDR SDDFSession Utility showing the current run and the total number of runs. Action None.

Format 6:

Last SDDF action action failed, for device symdv# in Symmetrixsymmserial, at site-id. Session: session-idFormat 7:

No Active SDDF Session found for device symdv# in Symmetrixsymmserial at site-idFormat 8:

Unable to determine last SDDF action for device symdv#, inSymmetrix symmserial, at site-id. Session: session-idFormat 9:

Unable to determine last SDDF action state for device symdv# inSymmetrix symmserial, at site-id. Session: session-idFormat 10:

Unexpected last SDDF action action for device symdv# in Symmetrixsymmserial at site-id

Unchanged SDDF Session Time stamps for device symdv#, in Symmetrixsymmserial, at site-id

GDDRSDDF SDDF Differential information for GDDR managed devices(nnnn / nnnn)


●

●

●

●

GDDP451I


GDDP452I

Cause This message provides detailed SDDF Session Differential information for a GDDR-managed SRDF device pair.This message has a left and a right side, as explained for message GDDP445I. In themiddle, there is a Differential column. If applicable, this estimate of the size of thedifferential between the R1 and R2 device, is the result of a combination of the tracksflagged in Active SDDF sessions on both sides.For each session, the following information is provided:

PowerMax/VMAX device number

The number of cylinders reported by the session

The 4-character session ID

The number of tracks flagged in the session.The SDDF Differential information report is produced only when the utility is run withD(Y). Both the Tracks and Differential columns will have inaccurate numbers if the utility isrun with D(Y) when MSC is performing its normal cycle switching and SDDF rotationactivities. Action None.

GDDP453E

Cause During this run of the GDDRSDDF utility, the listed number of devices are considered to beat risk for a Full PUSH on the next CREATEPAIR or RESUMEPAIR DIFFERENTIALoperation. Action Identify the devices at risk by searching for GDDP448E and GDDP449W messages. If thismessage is seen after a good MSC activation, review SRDF Host Component andResourcePak Base job logs for messages indicating an MSC software or configurationissue. Contact the Dell EMC Customer Support Center for technical assistance.To avoid unnecessary Full PUSH warnings, observe the following guidelines:When SRDF/A is dropped, run the utility with N(1).The utility should only be run with D(Y) when there is no MSC cycle switching or SDDFsession activity expected.

GDDP460I

Device CYLS ID Tracks Differential Device CYLS ID Tracks

symdv#1 cyl-count1 session-id1 track-count1 diff-count symdv#2 cyl-count2 session-id2 track-count2

GDDRSDDF considers count devices at risk for a Full PUSH

Site: site-id - GDDR BCV Device ranges in Symmetrix: symm-serial


●

●

●

●

●

●

●

●

●

●

●

●

●

Cause This is a header message for the BCV report produced by GDDRACDD in the TFLISTdataset. The message shows the site, storage system serial number and operatingenvironment major level and gatekeeper, to identify the storage system to which the BCVdevices listed in subsequent GDDP4662I messages belong. Action None.

GDDP461I


GDDP462I

Cause This message provides BCV details.The following columns are shown in Format 1:

bcv: PowerMax/VMAX device number of the BCV device (TimeFinder target device)

std: PowerMax/VMAX device number of the STD device (TimeFinder source device)

lastbcv: The last BCV to be attached to the listed STD device

hosttype: Host type (C for CKD, F for FBA)

status: BCV-STD pair status:

SPLIT: not currently attached

ESTABLISH: currently attached as result of a RE-ESTABLISH or ESTABLISH

command

RESTORE: currently attached as result of a FULL or INCREMENTAL RESTORE

command

sddf: SDDF session ID

int: The STD device is SRDF-paired in an internal GDDR SRDF group

ext: The STD device is SRDF-paired in an external GDDR SRDF group

gold: A GOLD set BCV is requested for the STD device. The GOLD column can be

shown as:

spaces: No BCV of the affected set is requested

GK: gk

Format 1:

BCV - STD - LBCV -H- STATUS -SDDF-INT-EXT-GOLD-TEST-IMPLEMENTATIONFormat 2:

BCV - STD -LAST SNAPSHOT NAME -H- STATUS - SNID -INT-EXT-GOLD-TEST-IMPLEMENTATION

Format 1:

bcv - std - lastbcv - hosttype - status --sddf-int-ext-gold-test-implementationFormat 2:

bcv - std -lastsnapshotname - hosttype - status - snapshotid -int-ext-gold-test-implementation


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

WARN: GDDRACDD should issue a warning message when it finds no BCV for the

affected set

ERR: GDDRACDD should issue an error message when it finds no BCV for the

affected set

test: A TEST set BCV is requested for the STD device. The TEST column can be

shown as:



affected set


affected set

implementation: Shows the pairing method:

MIRR: Indicates that legacy TimeFinder/Mirror with Clone emulation was

used

CLON: Indicates that MF SNAP TF Clone was used (SNAP VOLUME

TARGET())

SNVX: snapshotname: Indicates that targetless SnapVX was used and

shows the snapshot name.The following columns are shown in Format 2:

bcv: PowerMax/VMAX device number of the BCV device (TimeFinder target device)

std: PowerMax/VMAX device number of the STD device (TimeFinder source device)

lastsnapshotname: The name of the last snapshot for the listed STD device

hosttype: Host type (C for CKD, F for FBA)

status: BCV-STD pair status:

SPLIT: not currently attached

ESTABLISH: currently attached as result of a RE-ESTABLISH or ESTABLISH

command

RESTORE: currently attached as result of a FULL or INCREMENTAL RESTORE

command

LINKED: the listed BCV device is currently linked to the listed STD device, using

the snapshot name indicated in the IMPLEMENTATION column

LINKEDR: the listed BCV device is currently linked to the listed STD device with

the RESTORE option, using the snapshot name indicated in the

IMPLEMENTATION column

snapshotid: The snapshot ID

int: The STD device is SRDF-paired in an internal GDDR SRDF group

ext: The STD device is SRDF-paired in an external GDDR SRDF group

gold: A GOLD set BCV is requested for the STD device. The GOLD column can be

shown as:



affected set



●

●

●

●

●

●

●

●

affected set

test: A TEST set BCV is requested for the STD device. The TEST column can be

shown as:



affected set


affected set

implementation: Shows the pairing method:

MIRR: Indicates that legacy TimeFinder/Mirror with Clone emulation was used

CLON: Indicates that MF SNAP TF Clone was used (SNAP VOLUME TARGET())

SNVX: snapshotname: Indicates that targetless SnapVX was used and shows

the snapshot name. Action Review the contents of this message and change GDDRACDD parameters if necessary.Refer to the GDDR Product Guide for your configuration for detailed GDDRACDD usageinstructions with regards to the TimeFinder parameters.

GDDP470I

Cause The GDDR Invalid Track Monitor has completed a run and has found that the statedresynchronization targets have not been reached, or the requested number of runs has notcompleted. GDDRMINV is now waiting a user-specified number of minutes beforeperforming the next Invalid Track query. Action None.

GDDP471E

Cause The low-level GDDR Invalid Track Monitor module GDDRMINV was invoked with invalidarguments. GDDRMINV is not intended to be invoked directly by the end user. Thepreferred method is to use SAMPLIB(GDDRMIN0).This message is also used by the GDDRMIN0 batch interface to signal incorrectarguments. Action If you invoked GDDRMINV, correct the arguments. If you used GDDRMIN0, refer to theinstructions in SAMPLIB(GDDRMIN0). If the error persists, contact Dell EMC CustomerSupport. Keep the complete GDDRMIN0 job log available.

GDDP472I

Cause The GDDR Invalid Track Monitor begins a new cycle of Invalid Track queries. The message

GDDRMINV waiting minutes minutes before the next check

Invalid GDDRMINV arguments: arguments

GDDRMINV Starting Invalid Track monitor run run-number of run-count


●

●

●

●

●

●

●

●

●

provides a run-number as well as the total number of expected runs. When waiting for aspecified resynchronization goal, a total of 99999 is shown, but the monitor will exit whenthe goal is reached. Action None.

GDDP473I

Cause The GDDR Invalid Track Monitor found the indicated number of devices with invalid tracksduring this run. Action None.

GDDP474I

Cause The GDDR Invalid Track Monitor has completed a run of invalid track queries with theindicated return code:

RC=0: No objects have more than expected invalid tracks

RC=8: Some objects have more than expected invalid tracks.

RC=12: Maximum Stall exceeded while waiting for a specified resynchronization goal. Action If this is not the last run, this message can be considered purely informational.If RC=8, use other messages to monitor progress of the resynchronization.If RC=8 on the last run, investigate why some volumes did not complete synchronization.A few possible causes are:

Insufficient number of runs specified.

Insufficient interval size specified.

Resynchronization could simply not be expected to complete in the allotted time.

A competing workload caused resynchronization to be slower than expected.

A HW event reduced the bandwidth available for resynchronization.

An external event or a SW command caused resynchronization to stop (such as CG

Trip, SRDF/A drop, ADCOPY-DISK volumes).If RC=12, refer to RC=8, or allow for a longer Stall period.

GDDP475I

Cause The GDDR Invalid Track Monitor reports date and time for the Invalid Track Report thatfollows. Action None.

GDDP476I

GDDRMINV found count devices with invalid tracks

GDDRMINV Invalid Track Monitor RC=rc run run-number of run-count

Invalid Track Report - Date: date time

This message lists the following column names in a single row:


●

●

●

●

●

●

●

Cause This is a header message for the Invalid Track Report that follows.This report has the following columns:

Site: This is the site for the physical location of a monitored storage system.

Symmetrix: Storage system serial number in nnnnnnnnn-nnnnn format.

RA: The SRDF group of the monitored devices. If the Invalid Track Monitor is invoked

for local invalid tracks, the SRDF group is shown as “NN” (literal 'NN').

Device(s): Either one device or a range of devices for which invalid tracks are

being monitored in the listed SRDF group.

Invalid Tracks: The number of invalid tracks for the listed object at the time of

the last query.

Tracks/s: Tracks resynchronized during the last interval. The value is shown as N/A

on the first interval. The value can be negative. This can happen if new invalid tracks

are being created faster than the current speed of resynchronization for the affected

object.

ETA: Estimated Time of Arrival. Shown as hhhh:mm:ss. This is the time that needs to

elapse at the current resynchronization speed, for the number of monitored invalid

tracks to go down to 0. The value is shown as N/A on the first interval. ETA is shown

as 9999:59:59 when the speed is <=0.The resynchronization speed is calculated based on the difference in the number of invalidtracks on the current query and on the previous query. Some inaccuracy in thiscalculation, and in the ETA based on it, is to be expected, more so as the GDDRMINVinterval is larger. If the interval is 10 minutes, and an object moved 6000 tracks in the firstminute of the current interval, the speed will be reported as 10 tracks per second, where infact 100 tracks per second were moved.The amount of detail provided by the report depends on the wait option specified toGDDRMINV. See instructions in SAMPLIB(GDDRMIN0) for details about the wait option.The report will only show objects with a non-zero invalid track count.Provided detail by wait option:- Fixed # of runs specified: (=no wait option)Shows full detail including device level.- Resynchronization goal specifiedSITE: Shows only summary records per site. The Symmetrix, RA and Device(s) columnsare blank.SYMMETRIX: Shows only summary records per site and per storage system. The RA andDevice(s) columns are blank.RAGROUP: Shows only summary records per site, storage system, SRDF group. TheDevice(s) column is blank.RANGE: Shows full detail at the device range level, as well as summary records per site,storage system, and SRDF group.DEVICE: Shows full detail at the device level, as well as summary records per site, storagesystem, SRDF group and range.

Site●

Symmetrix●

RA●

Device(s)●

Invalid Tracks●

Tracks/s●

ETA●


Action None.

GDDP477I

Cause This is the Site-level summary record of the Invalid Track Report, showing the currentnumber of monitored invalid tracks for the entire site, as well as the currentresynchronization speed and ETA. Action None.

GDDP478I

Cause This is the storage system-level summary record of the Invalid Track Report, showing thecurrent number of monitored invalid tracks for the entire storage system, as well as thecurrent resynchronization speed and ETA. Action None.

GDDP479I

Cause This is the SRDF group-level summary record of the Invalid Track Report, showing thecurrent number of monitored invalid tracks for the entire SRDF group, as well as thecurrent resynchronization speed and ETA. Action None.

GDDP480I

Cause This is the device range-level summary record of the Invalid Track Report, showing thecurrent number of monitored invalid tracks for the device range, as well as the currentresynchronization speed and ETA. Action None.

GDDP481I

site-id track-count resync-speed eta

site-id symm-serial

track-count resync-speed eta

site-id symm-serial srdfgrptrack-count resync-speed eta

site-id symm-serial srdfgrp rangetrack-count resync-speed eta

site-id symm-serial srdfgrp symdv#

track-count resync-speed eta


Cause This is the Device-level record of the Invalid Track Report, showing the current number ofmonitored invalid tracks for the device, as well as the current resynchronization speed andETA. Action None.

GDDP482I

Cause This is the header for the stalled items report that follows. This report calls out thoseobjects for which the speed of resynchronization was negative or zero. Action Investigate why the listed items are not synching up.

GDDP483I

Cause This message lists an item which did not synch up during the last interval. Action Investigate why the listed items are not synching up.

GDDP484I

Cause The GDDR Invalid Track Monitor was invoked with a resynchronization goal, and is waitingfor all objects of the chosen type to reach a number of monitored invalid tracks which islower than the specified number.At least one object did not reach the goal. The message is followed by GDDP485I,identifying the object causing GDDRMINV to continue to wait. Action None.

GDDP485I

GDDRMINV The following items did not make progress during thecurrent interval:


Site site-id - count Invalid Tracks (was: count)●

Site site-id Symmetrix symm-serial - count Invalid Tracks

(was: count)

●

Site site-id Symmetrix symm-serial RA srdfgrp - count Invalid

Tracks (was: count)

●

Site site-id Symmetrix symm-serial RA srdfgrp Range symdv#-

symdv# - count Invalid Tracks (was: count)

●

Site site-id Symmetrix symm-serial RA srdfgrp Device symdv# -

count Invalid Tracks (was: count)

●

GDDRMINV Continuing to wait, reason:

object


●

●

●

Cause This message identifies the object causing the GDDR Invalid Track Monitor to continuewaiting. This can be a site, a storage system, an SRDF group, a device range or a device.The listed object can and will probably change over several runs of the monitor as objectsreach the specified goal. Action If necessary, query the status of the listed object, especially if the object is also listed inthe stalled items report.

GDDP486E

Cause The GDDR Invalid Track Monitor was invoked specifying a resynchronization goal, as wellas a maximum allowed number of intervals without resynchronization progress. (Thedefault for the Maximum Stall option is 5 intervals.)GDDRMINV will stop monitoring, with RC=12. Action Investigate why resynchronization has stalled, or allow for a longer stall period.

GDDP487I

Cause The GDDR Invalid Track Monitor batch interface is about to exit and is reporting anyinvalid tracks remaining on monitored device ranges. Action Investigate why resynchronization did not complete by the time GDDRMIN0 ends. Referto message GDDP474I for guidance.

GDDP488I

Cause This is the header for the Final Invalid Track Counts report that follows. Action None.

GDDP489I

Cause This is the detail line of the Final Invalid Track Counts report. The following columns arepresent:

site-id: Physical location of the queried storage system.

symm-serial: Storage system serial number, followed by the path used to query the

system. (Format: gatekeeper or gatekeeper.srdfgrp).

srdfgrp: The SRDF group to which the reported device range belongs. Shown as NN

GDDRMINV has detected a Stall condition for count consecutiveintervals

GDDRMIN0 Final Invalid Track counts

Site Symmetrix RA Devices Invalid Tracks

---- ----------------------- ---- ----------------- ------------------

site-id symm-serial srdfgrp device-range track-count


●

●

(literal) if a query for local invalid tracks was done.

device-range: Range of devices that was queried. Only ranges with a non-zero count

are listed.

track-count: Number of invalid tracks that remains when the monitor is about to exit. Action None.

GDDP490I

Cause The GDDR Invalid Track monitor is about to exit, because GDDRMINV has reported a stallcondition. Action Refer to message GDDP486E for guidance.

GDDP491I

Cause The GDDR Invalid Track Monitor is about to exit. It was invoked with specification of aresynchronization goal, and the goal was reached. Action None.

GDDP492I

Cause The GDDR Invalid Track Monitor is about to exit. All invalid tracks have been synched up. Action None.

GDDP998E

Cause An error has occurred which appears to be a GDDR program error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support site for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDRMINV reports that resynchronization is no longer progressing

GDDRMINV reports that all objects reached their resynchronizationgoal

GDDRMINV reports no remaining invalid tracks

INTERNAL ERROR: CALL TECH SUPPORT -ID = error_identifier


●

●

●

●

●

●

●

CHAPTER 7 GDDR Command Queue Messages (GDDQ) GDDQ003E

Cause This is an error message issued by GDDRF255 stating that the GDDR SSVT address couldnot be found. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDQ220E

Cause An action to modify the GDDR command queue was requested, but the requestor does nothold the command queue lock.Possible reasons include:

requester does not own ENQ

no ENQs matching QNAME qname found

no ENQs matching RNAME rname found

GDDRSSVT not found

GDDRWSCB not found

GQSCAN error: RC rc RS rs

GDDRQFCN RC rc Action Do not attempt actions such as clearing the command queue when an action script isrunning. If that is not the problem, contact customer support.

GDDQ221E

Cause An action to modify the GDDR command queue was requested, or an action script wasinitiated, but the command queue lock was not available. Action Wait until the indicated job completes and try the operation again.

GDDQ222I

GDDR SSVT address could not be obtained (failing-module {RC rc |RS rs})

GDDR command queue lock not held (reason)

Unable to obtain command queue lock, held by jobname

block for subsystem at address (length length) released


Cause The storage as shown has been freed. Action None.

GDDQ223E

Cause The indicated program cannot successfully execute unless it has APF authorization. Action Determine why APF authorization has been lost for this program and correct the problem.Run the job again.

GDDQ224E

Cause There are multiple GDDR subsystems defined on this system and it is unclear which oneshould be used. Insert a GDD$nnnn DD in the JCL, where nnnn is the name of the GDDRsubsystem to use. Action Run the job again.

GDDQ225E

Cause Program GDDRSSVI is attempting to initialize the indicated GDDR subsystem, but italready exists and PARM=NEW was specified. Action Specify PARM=REINIT if you wish to initialize the subsystem again. If you were unawarethe subsystem was already initialized, continue processing.

GDDQ226W

Cause GDDRWORK is processing a unit of work and cannot obtain the command queue lock. Theaddress space which holds the lock is displayed. This may or may not represent a problem,depending on the circumstances. If the message occurs on the master C-system, itprobably means that a script or other function is running which is holding the lock. Thistypically is not a problem. If the message occurs on a non-master C-system, it is a causefor concern and could indicate that the command queue is being manipulated via ISPFpanels or some other means. If the lock cannot be obtained and the work being run requires the use of the commandqueue, the work will fail. Action If the message occurs on a non-master C-system, investigate why the lock is not available.

GDDQ227I

Program program_name is not authorized

Unable to determine Subsystem name

Subsystem subsystem_name exists but PARM=NEW specified

Unable to obtain command queue lock (held by job), continuing


●

●

●

●

●

●

Cause This message indicates the job name, job ID, and subsystem name for the GDDRMAINaddress space, as well as the address of the GDDR subsystem vector table for Dell EMCuse. Action None.

GDDQ228I

Cause The command queue lock was not obtained. This is not indicative of a problem.Reason text is shown in parentheses for Dell EMC use. Possible reasons are as follows:

RERUN = Z

HMC REXX

at originating site

on originating system

originating site/sys are blank

held by lock_holder Action None.

Job job-name (job-id) using GDDR subsystem subsystem (SSVT atssvt-address)

GDDR command queue lock not obtained (reason)


CHAPTER 8 General GDDR Messages (GDDR) GDDR000I

Cause This message ID is reserved for diagnostic messaging. The message text is variable. Action None.

GDDR001E

Cause This indicates a GDDR internal error. An internal error code is generated and the currentscript is unsuccessful. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR002E

Cause A request to identify the file tailoring or procedure libraries specified by the ISPF skeletondataset or JCL dataset GDDR parameters failed because none was found. The processorcannot continue unless at least one file tailoring library is found. An internal error code isgenerated and the current script is unsuccessful. Action Perform a noninitialization parameter load specifying at least one file tailoring or procedurelibrary. Be sure to include the file tailoring library distributed as part of GDDR, or a copy ofthis library. (The distributed library has low-level index ISPSLIB.) Then submit the scriptagain.

GDDR003E

Cause During initial environment checking, a GDDR processor determined that the GDDRautomation flag is off. The processor, however, is prohibited from proceeding unless theGDDR automation flag is set. Consequently, the processor returns an error code and therunning script is unsuccessful. This message usually appears either while a script isstarting or restarting, but may be issued at any point during execution of a script if theautomation flag is clear.

message-text

GDDR Invalid argument parameter_string

No {file tailoring|procedure} library defined for GDDR

GDDR unable to continue, GDDR automation is off


Action If appropriate, set the GDDR automation flag. Then start the script again.

GDDR004E

Cause During initial environment checking, a GDDR processor determined that it was not runningon a GDDR C-system. The processor, however, is prohibited from running except on a C-system. Consequently, the processor returns an error code and the running script isunsuccessful. GDDR scripts are never intended to run on a system other than the GDDR master C-system. (It is possible that a master C-system transfer can occur during execution of aGDDR script; such scripts are permitted to complete on the C-system which is no longerthe master C-system). Action If the processor is running under a GDDR script, ensure that the script runs on the masterC-system.

GDDR005E

Cause During initial environment checking, a GDDR processor determined that it was not runningon the GDDR master C-system. However, the processor may run only on the master C-system. Consequently, the processor returns an error code and the running script isunsuccessful. GDDR scripts are never intended to run on a system other than the GDDR master C-system. Action If the processor was running within a GDDR script, arrange for the script to run on themaster C-system.

GDDR006E

Cause During initial environment checking for the current script, GDDR has determined that itwas not running on a site at the secondary region. However, the script may run only on asite at the secondary region. An error code is generated and the current script isunsuccessful. Action Ensure that the script is run on a C-system at the secondary region.

GDDR007I

Cause During script job initialization, GDDR has put the indicated call override string into effect.If this is a planned script job, the call override string is that specified by the scriptsubmitter. If this is an unplanned script, the call override string is the GDDR default. Action

GDDR {function|processor} can only run on a C-System

GDDR {function|processor} can only run on the master C-System

GDDR Unable to continue, not running in secondary region

GDDR Using call override string override


None. GDDR008I

Cause During script job initialization, the script processor has obtained the indicated SRDF HostComponent for z/OS command prefix into effect. If this is a planned script job, thecommand prefix was set by the submitter on the Specify Parameters For Script Rerunpanel. If this is an unplanned script job, the command prefix was set on the Script JCLParameters panel. Action None.

GDDR009I

Cause This message notifies the operator of an event which is not handled by GDDR. Themessage does not time out, but remains outstanding until the operator replies. After theoperator replies, the operations group has the responsibility to assess the event anddetermine how it is to be handled. Action None.

GDDR011I

Cause The current script notifies the operator of an event which is not handled by GDDR. Themessage does not time out, but remains outstanding until the operator replies. After theoperator has replied, it is the responsibility of the operations group to assess the event anddetermine how it is to be handled. Action None.

GDDR013E

Cause An SRDF Host Component command in the GDDR command queue has completed, andGDDR was unable to free the command element. The task number corresponds to thenumber of the command shown in a previous GDDR672I message. If the failure to free theelement occurred because the command was unsuccessful, the return code shown is thatreturned by the command. Otherwise, the return code indicates a system error. In eithercase, an internal error code is generated and the running script is unsuccessful Action If the error is due to a command failure, identify the SRDF Host Component command thatencountered the error by matching the task number in this message with the commandnumber in a previous GDDR672I message. Correct the problem and submit the script

GDDR Using Host Component command prefix xxxxxxxx

GDDR Running warning-only script for event event

GDDR text not configured, bypassing {wait for consistency |$$ MSCcleanup | $$}

GDDR Command running under task task_number unsuccessful, rc rc,command element not freed


again.If the error is due to any other reason, however, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have the SYSLOG, the job log, and allrelevant job documentation available.

GDDR014I

Cause GDDR014I displays variable messages indicating a failure from the exit driver(GDDRXDRV). On return from the exit, the exit driver pulls anything on the external dataqueue (placed there by the exit itself or as a result of trying to execute the exit) anddisplays it using GDDR014I. The text is the content of the edq line and is not modified inany way by GDDRXDRV. Action If the message text is ALLOCATION OF EXTERNAL DATA QUEUE FAILED, RC=rc,validate that the GDDR TSO user region size is sufficient. Increase the TSO user regionsize on the user’s TSO LOGON parameters to 2096K or the maximum allowed for theLPAR. Contact the Dell EMC Customer Support center for assistance with this and othermessages.

GDDR015E

Cause An SRDF Host Component command to retrieve device information in the GDDR commandqueue has failed. The command return code is given. The task number corresponds to thenumber of the command shown in a previous GDDR672I message. An internal command isgenerated and the running script is unsuccessful Action Identify the SRDF Host Component command that encountered the error by matching thetask number in this message with the command number in a previous GDDR672I message.Correct the problem and submit the script again.

GDDR015I

Cause This message always follows GDDR019E to list the SRDF Host Component API commandthat failed. Action None.

GDDR016I

Cause This message indicates a gatekeeper-device-storage system combination that will beprocessed by ECGUTIL.The Consistency Groups for z/OS Product Guide provides more information aboutECGUTIL.

message-text

GDDR FC03_task:task_number RC=rc

GDDR Detected Host Component message id message-id

GDDR Gatekeeper UCB(gk) SYMM_DEV#(symdv#) forController=symmserial


●

●

●

Action None.

GDDR018W

Cause The SRDF Host Component has completed processing for a command, and has indicated:

The number of devices designated by the command to be acted upon

The number of devices among these that were eligible for the requested action

The number of devices among these for which processing successfully completedThese three numbers were not all equal. This may represent a processing error. Action Determine whether an error actually occurred. If so, take appropriate action.

GDDR019E

Cause The SRDF Host Component API command shown has failed. The ID of the primary SRDFHost Component error message is shown. The processor returns an error code and therunning script is unsuccessful. Action Determine the proper action to take by finding the SRDF Host Component message andtaking the recommended action. Then, submit the script again.

GDDR023E

Cause The current script step attempted to obtain a list of system names to process. If the siteID is present, the system names were required from only that site; otherwise, the systemnames were required from all sites. An error code is generated and the running script isunsuccessful. Action Check your SITE parameters, and make sure your systems are defined properly.

GDDR031E

Cause An attempt was made to run a script before another script had completed. An internalerror code is generated and the script exits immediately. Action Wait until the current script completes successfully before attempting to run a new script.

GDDR034A

GDDR Device count mismatch, req=#requested, elig=#eligible,comp=#completed

Command ’command’ has failed GDDR detected Host Component messageid message-id

GDDR System list could not be obtained for site site-id

GDDR Script script_processor must complete before runningscript_processor


Cause While validating the initial environment for running a planned script, GDDR has determinedthat communication to a remote C-system is currently unavailable. It is not normally safeto run a planned script in this situation, because the remote and local C-systems may losesynchronization. However, when the remote C-system is unavailable because of a site orsystem failure, it may be necessary to allow the script to run. Action Reply Yes to allow the script to run, Cancel to cause the script to terminate immediately.

GDDR034E

Cause The number of SRDF/S GNS groups, as specified in parameters derived from the valuesin the Define SRDF/S GNS Groups panel, is not the same as the number of SRDF/Sgatekeepers, as specified by parameters derived from the values in the Define SRDFDevice Ranges panel. Action Consult the GDDR Product Guide for your configuration for assistance with specifying therequired values in the Define SRDF/S GSN Groups panel and the Define SRDF DeviceRanges panel.

GDDR041E | GDDR041I

Cause While waiting for SRDF/A consistency, GDDR determined that the SRDF/A cycle numberhad not changed. If this has happened through two SRDF/A cycle intervals, GDDRassumes that SRDF/A will not achieve consistency. An internal error code is generatedand the current script is unsuccessful. Action Determine the reason that SRDF/A is not cycling. Correct the problem and submit thescript job again.

GDDR042E

Cause An SRDF Host Component command was issued by means of the API, but no output wasreturned. Action Attempt to determine the reason that no records were returned.

GDDR043E

Cause The indicated GDDR program is unable to continue processing for the indicated reason.

GDDR Should script script_processor be allowed to run? Pleasereply (Yes/Cancel)

GDDR Number of SRDF/S gatekeepers (nn) does not equal the numberof SRDF/S GNS groups (nn)

GDDR SRDF/A no longer cycling: current cycle number=nnn, startcycle number=nnn.

GDDR No records returned from api_function call

GDDR program-name unable to continue. Reason: reason


●

●

●

●

●

●

●

Examples of reasons include:

Planned script script-name is in progress

Unplanned script script-name is in progress

GDDR Command queue is not empty Action Take corrective actions to address the reason indicated by the message text.

GDDR049E

Cause Module GDDRRDF0 was unable to determine which gatekeeper/SRDF group combinationto use to generate a correct SRDF Host Component command for a remote action fromthe site where the gatekeeper device is located, to the site where the devices acted upon(action site). The device type can be specified as STAR or Non-STAR (SRDF/A or non-SRDF/A). The indicated storage object consists of a gatekeeper at the action site and adevice range linked to that gatekeeper. This error is usually caused when GDDRparameters incorrectly define SRDF devices. Action Verify your GDDR parameters related to SRDF devices, and correct them if needed. Ifnecessary, contact Dell EMC Customer Support for assistance.

GDDR050E

Cause During preparation for SRDF/A-related script processing, no parameters specifyingSRDF/A gatekeepers were found. These parameters have the format JA_ACT_GK.site-id.*. An internal error code is generated and the current script is unsuccessful. This messagecan appear while:

Preparing for SRDF/A R1 device special processing

Bringing up SRDF/A

Waiting for SRDF/A consistency

Performing SCFRDFM6, SCFRDFM9 or SCFRDFME cleanup Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Thensubmit the script job again. If the problem persists and the parameters appear to havebeen loaded correctly, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR051I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed. Action None.

GDDR No matching device-type parameters found for storage-object-name

GDDR No SRDF/A gatekeepers for site site-id are defined

GDDR Host Component prefix prefix


GDDR052I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed. Action None.

GDDR053I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed and acts as a header to message GDDR053I that alwaysimmediately follows this message. Action None.

GDDR054I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed. There will be as many consecutive GDDR054I messages asneeded to display the job statement used for the batch script job submission. Action None.

GDDR055I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed, and acts as a header to message GDDR056I that alwaysimmediately follows this message. Action None.

GDDR056I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed. There will be as many consecutive GDDR056I messages asneeded to display the procedure libraries in use through the JCLLIB Order=statement. Action None.

GDDR057I

GDDR SCF suffix suffix

GDDR Job statement:

GDDR text

GDDR Procedure libraries:

GDDR text


Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed, and acts as a header to message GDDR058I that alwaysimmediately follows this message. Action None.

GDDR058I

Cause This message is displayed during script executions to provide troubleshooting informationin the event it is needed. There will be as many consecutive GDDR058I messages asneeded to display the ISPSLIB file tailoring libraries used for the batch script jobsubmission. Action None.

GDDR071E

Cause The required STAR configuration gatekeeper address is missing from the startupparameters. Action Notify your GDDR administrator. If you are the GDDR administrator and need helpdiagnosing the problem, contact the Dell EMC Customer Support Center.

GDDR072E

Cause During preparation for SRDF/S-related script processing, no parameters specifyingSRDF/S gatekeepers were found. These parameters have the format J0_GK.site-id.*. Aninternal error code is generated and the current script is unsuccessful. Some situations inwhich this message can appear are during preparation for SRDF group-based half-swapSRDF Host Component processing or for performing special processing for SRDF/S R1devices. Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Then,submit the script job again. If the problem persists and the parameters appear to havebeen loaded correctly, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR073E

Cause During preparation for performing an SRDF/S personality swap, no parameters specifying

GDDR File tailoring libraries:

GDDR text

GDDR GDDRSTAR parameter parameter is not defined

GDDR No SRDF/S gatekeepers for site site-id are defined

GDDR No SRDF/S devices for site site-id are defined


SRDF/S devices were found for the indicated site. An internal error code is generated andthe current script is unsuccessful. Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Thensubmit the script job again. If the problem persists and the parameters appear to havebeen loaded correctly, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR074E

Cause During preparation for cleaning ConGroup devices, no parameters specifying SRDF/SGNS groups were found for the indicated site. These parameters have the format GNS.site-id.LCL.J0. An internal error code is generated and the current script is unsuccessful. Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Thensubmit the script job again. If the problem persists and the parameters appear to havebeen loaded correctly, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR090E


GDDR101E

Cause ISPF was found not to be active for a GDDR script using the AUTOCBU feature. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR104I

GDDR No SRDF/S GNS groups for site site-id are defined

GDDR Unknown caller specified confirmation_id, unable to continue

GDDR ISPF services are not available in this address space,exiting.

GDDR No AUTOCBU parms defined for Site site-id, exiting


Cause This message states that no AUTOCBU parameters exist for the indicated site. Action None.

GDDR106W

Cause In a GDDR script with an Automatic CBU Activation step, it was found that there areAUTOCBU entries defined in the Script AUTOCBU Options panel, but an HMC Bypassspecified for the same site, in the Define Managed LPARs panel, indicates that HMCactions are not allowed. The Automatic CBU Activation script step ends with RC=0. Action Depending on your requirements, change the entries in the Script AUTOCBU Optionspanel or eliminate the HMC Bypass entry in the Define Managed LPARs panel to avoidgetting this warning message or do nothing if you accept this message.

GDDR107W

Cause In a GDDR script with an Automatic CBU Activation step, it was found that there areAUTOCBU entries defined in the Script AUTOCBU Options panel, but an HMC Bypass isspecified for the same site in the Define Managed LPARs panel, indicates that HMCactions are not allowed for one or more LPARs running on the CPC specified on theAUTOCBU parameter. The Automatic CBU Activation script step continues other CPC's. Action Depending on your requirements, change the entries in the Script AUTOCBU Optionspanel or eliminate the HMC Bypass entry in the Define Managed LPARs panel to avoidgetting this warning message or do nothing if you accept this message.

GDDR109W

Cause In a GDDR script with an Automatic CBU Activation step, it was found that there areAUTOCBU entries defined in the Script AUTOCBU Options panel, but HMC Bypass isspecified for the same site in the Define Managed LPARs panel, therefore; no CBU actionscan be performed. The Automatic CBU Activation script step ends with RC=0. Action Depending on your requirements, change the entries in the Script AUTOCBU Optionspanel or eliminate the HMC Bypass entry in the Define Managed LPARs panel. to avoidgetting this warning message or do nothing if you accept this message.

GDDR115I

Cause

GDDR Automatic CBU Activation disabled by HMC Bypass at Site site-id

GDDR Automatic CBU Activation disabled for CPC processor_name atSite site-id (HMC Bypass or LPAR lpar-name )

GDDR ALL AUTOCBU CPCs at Site site-id are excluded by theHMC_Bypass specification

GDDR SDDF Cleanup Status for script-name


This message shows progress in the cleanup of SRDF/Star SDDF sessions. Action None.

GDDR116I

Cause This message shows progress in the listing of SRDF/Star SDDF sessions. Action None.

GDDR117I

Cause GDDR parameters indicate that the GDDR STAR SDDF Cleanup feature should be used.The SDDF Cleanup action is now being started for the listed site and gatekeeper. Action None.

GDDR119E

Cause This error message indicates the GDDRCL00 has found a STAR tag (E or F) on at leastone of the SRDF/A SRDF groups, and exits immediately with RC=16. Action Iinvestigate why STAR Recovery was active at the time GDDRCL00 was running. ContactDell EMC Customer Support for further assistance.

GDDR120E

Cause There was a problem retrieving SRDF group object information through the API. Action Review the job log and SCF job log for related error messages. Contact Dell EMCCustomer Support for further assistance.

GDDR121I

Cause GDDR processing is waiting the indicated number of seconds for the indicated activity tocomplete. An example of activity is MSC cleanup after the SCFRDFM9 utility has beenexecuted. Action None.

GDDR SDDF List Status for script-name

GDDR Invoking SDDF Cleanup for site-id,gk

GDDR MSC Cycle tag tag found. Exiting.

GDDR Get RDFGRP for site-id,gk,srdfgrp RC=rc

GDDR Waiting seconds seconds for activity to complete


●

●

●

●

GDDR122E

Cause During script processing, GDDR attempted to vary DLM tape drives offline. The driveshave not gone offline and processing is halted. Action Determine why drives are not offline and take them offline. Then resubmit the script.

GDDR123A

Cause This message appears only if the current script has the override that specifies ConGroupStop/Start and if GDDR message interception rules have not received (within the 5minute interval allowed in the ConGroup startup and shut down programs):

The CGRP800I message, indicating that ConGroup has shut down on the GDDR

managed production systems

The CGRP611I message indicating, that ConGroup startup has completedWhen ConGroup tasks on all GDDR managed production systems have been shut down orstarted, GDDR script processing will continue. Action This message does not appear if GDDR message interception rules and the z/OS ConsoleMonitor are functioning. If the message appears, the operator response is:

Y or Yes to allow the script to continue, after confirming that the ConGroup tasks are

in the expected status (either stopped or started)

C or Cancel to stop the script.The shutdown message is created by GF08. The startup message is created by GF09.Neither message is formatted using GS0D; that is, both messages are formatted fromliterals in the source code.

GDDR123W

Cause During script processing, GDDR sent a command to DLM and received a status code ofABORT in response. The script will not attempt any further DLM actions but will continue. Action Determine why the DLM returned ABORT and take the appropriate corrective action.

GDDR124A

Cause During script processing, it has been determined that data at the first indicated site ismore current/recent than the data at the second indicated site. If the script proceeds,data from the secondary region will be used, whether it is the most current or not. Action

GDDR timed out waiting for DLM tape drives to go offline.

GDDR Waiting for ConGroup to {shutdown|startup}, please confirm(Yes/Cancel)

GDDR received ABORT from DLM

GDDR site site-id ahead of site site-id, Please confirm thatsecondary region data will be used (Yes/Cancel)


Reply Y to continue and use data from the secondary region; reply C to use data from theother named site.

GDDR124E

Cause A script has been selected to execute, but cannot execute because the SRDF replication inthe secondary region is ahead of replication at the indicated site. Action Correct the SRDF replication problems (restart replication) and resubmit the script.

GDDR124I

Cause A script has been selected to execute, and it has been determined that the replicated dataat the secondary region is NOT more current than the local data. Script executioncontinues. Action None.

GDDR125W

Cause During script processing, GDDR sent a command to DLM and received a status code ofABORT in response. While the abort status remains, all DLM script steps will be skippedbut the script will continue. Action Determine why the DLM returned ABORT and take the appropriate corrective action.

GDDR126I

Cause Script processing is waiting for DLM tape drives to go offline. These messages show whichdrives remain online and what job (if any) they are allocated to.If the drive is allocated, at least the address space ID (ASID) will be displayed; if possible,the jobname and jobid will also be displayed, but if they cannot be determined, they will bedisplayed as ?s.A form of this message also indicates when certain DLM tape drive information cannot beobtained from a system. Action

Secondary region ahead of site-id,Script script-name (script-description) is not allowed to run.Please consult ConGroup messages.

GDDR LOCAL site site-id has more recent data than remote sitesite-id .script-name (script-description) proceeding.

GDDR skipping DLM step due to ABORT

Drive ccuu on system-name is online and not allocatedor

Drive ccuu on system-name allocated by jobname (job-id) ASID asidor

Unable to get online drive information from system-name


None. This message may be followed by GDDR127A, unless the maximum wait time has alreadyelapsed. You may want to use the information in this message to investigate why drivesare not going offline. Also, if a failure to get DLM tape drive information was indicated,manual action may be needed to vary drives on the indicated systems.

GDDR127A

Cause Script processing is waiting for DLM tape drives to go offline. Message GDDR126I hasdisplayed which drives remain online and what job (if any) they are allocated to.You can interrupt the wait for drives to go offline if you so choose by replying to thisWTOR. Action Reply C to cause the wait for drives to go offline to end and the script to continueprocessing with the next step; reply X to cause the script to end or reply F to cause VARYOFFLINE FORCE.Any other reply will cause a wait for 15 seconds after which the drives will be recheckedfor offline status.The WTOR waits for a reply for 15 seconds. If no reply is received, the drives will beimmediately rechecked for offline status.

GDDR127E

Cause A GDDR script issued a WTOR which timed out after the number of seconds specified inthe WTOR Wait Time parameter. The WTOR Wait Retries value in the Specify GDDRTuning Values panel allows a number of retries, but the script has exceeded this number(indicated in the message). Action Check why the action GDDR is waiting on is taking longer than WTOR_WAIT_INTERVAL.If required and possible, increase the WTOR Wait Time parameter.

GDDR128I

Cause UP31 Ran DC2 to DC1. Action Run the manual DLMDR Cleanup.

GDDR129I

Cause Script GDD2P17A completed. This message provides notification of DLm start at therecovery site. Action

Reply C to stop waiting and continue script, X to end script, or Fto VARY OFFLINE FORCE

GDDR WTOR retries exhausted (nn)

GDDR UNPLANNED Event Run Cleanup. See Primus EMC306646 forinstructions.

CKD Disk READY at recovery site - Starting DLm Startup there


None. GDDR130I

Cause VG8ACT / CFGSWAP,PROD has been successfully processed.GDDR-managed tape drives are ready. Action None.

GDDR131E

Cause Command VTEDEVSTATUS,QUIECE failed, active tape jobs still running. GDDR managedtape drives cannot be taken offline. Action Cancel or vary tape drives, offline, force. If 'force' is used on vary offline, the tape drivewill be boxed.If a boxed tape drive is controlled by a tape management system, the drive will remain inthe A-BOX state.Unless the tape management system is taken down, the VARY devnum,ONLINE,UNCONDcommand must be used to return the tape drive to the online state.

GDDR132I

Cause This message lists the GDDR-managed tape drives to be varied offline. Action None.

GDDR133E

Cause While performing a device status check, GDDR has determined that the indicated devicehas a nonzero track count. Action Rerun the script after devices have had time to synchronize.

GDDR133W

Cause GDDR is attempting to automatically update or verify FICON serial numbers for theindicated DLm, but is unable to obtain such from the DLm. Action

GDDR Managed Tape Drives are ready for processing

GDDR Managed Tape Drives CANNOT QUIESCE, active tape jobs stillprocessing

GDDR Managed Tape Drives to be varied offline if requested

GDDR invalid_track_count {R1|R2} invalids on symm device symdv#

Unable to obtain FICON serial numbers for site-id DLM at ip-address port port


If the condition persists, investigate why the serial numbers cannot be retrieved from theDLm. If the serial numbers in the GDDR global variable are correct, no action is required. Ifthey are not correct, you can manually correct them.

GDDR134I

Cause GDDR has updated the indicated global variable with FICON serial numbers for theindicated DLM. The serial numbers are different from what was previously saved in thevariable. Action None.

GDDR135E

Cause While performing a device status check, GDDR has determined that the indicated devicehas the indicated mirror type. Action Examine previous script log for possible causes. Issue commands SWAP or CREATEPAIRto change the device MR type to expected state.

GDDR135I

Cause Script processing has temporarily suspended the DLm heartbeat monitor during swap orrecovery processing. When the DLm swap or recovery completes, the script will explicitlyresume the heartbeat monitor. Should the script fail for any reason, heartbeat monitoringwill automatically resume at the date and time shown in the message. Action None.

GDDR136E

Cause While performing a device status check, GDDR has determined that the indicated mirrorfor the indicated device was in NOT-READY status. Action Issue a SRDF Host Component RDY or RDF-RDY command for this device.

GDDR157E

Cause

Global variable variable (site-id DLM at ip-address port port)updated

GDDR Found mirror type mirror_type on device symdv#

DLm heartbeat monitoring suspended at all sites until xxxor

DLm heartbeat monitoring resumed at all sites

GDDR Found {M1|M2|M3|M4} Not-ready on device symdv# (gk)

CPC Swap not allowed: reason


●

●

●

●

●

●

●

●

●

●

A CPC swap has been requested, but cannot be performed for the reason given in themessage. Possible reasons include:

Inconsistent location of recoverable systems - All systems on the

CPC to be swapped must at their home location or all must be at their alternate

location.

Inconsistent location of systems on recovery CPC - The systems

on the CPC to be swapped to must all be at their home location or all must be at their

alternate location.

Inconsistent recovery CPCs - The recoverable systems on the CPC to be

swapped to recover to more than one CPC.

No recoverable systems on this CPC - The input CPC does not have any

recoverable systems.

Recovery CPC systems do not recover to this CPC - The recoverable

systems on the CPC to be swapped to do not recover to the input CPC.

Recovery defined to more than one CPC - The recoverable systems on

this CPC recover to more than one CPC. Action If the failure is one of state (inconsistent location, for example), correct the states via thePerform HMC LPAR Actions panel and retry. If the failure is one not related to state, CPCswap cannot be performed. However, you can still move systems to alternate locations viathe Perform HMC LPAR Actions panel.

GDDR158E

Cause A CPC swap has been requested and started, but an error has been encountered. Themessage describes the error. If an error occurs swapping a system or loading a non-recovery-enabled system, the process continues in an attempt to swap/load as manysystems as possible. In all cases, this message will be preceded by messages related to thefailure, and those messages will give the detail on the problem.

Unable to stop workload at site site-id

Error swapping system system-name The error occurred starting a recoverable system at the destination CPC.

Error loading system system-name The error occurred starting a system which does not have recovery defined, butwhich was running in an LPAR on the destination CPC into which a recoverablesystem was loaded. An attempt was made to load this system into the LPAR vacatedby the recovered system.

Unable to start workload at site site-id Action Correct the problem which caused the failure and rerun the process, or manually correctthe issues.

GDDR160E

Cause

CPC Swap Error: reason, rc=rc

GDDR Failing system system-name is not a valid C-System


The GDDR Heartbeat Monitor has determined that a C-system is no longer alive. However,the dead C-system processor has been unable to verify that the system identified by theGDDR Heartbeat Monitor is in fact a C-system. No further dead C-system processing isdone. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDR161E

Cause GDDR was unable to determine the set of C-systems because a necessary GDDRparameter could not be located. No further dead C- system processing is done. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR162E

Cause Because of an error identified in a previous message, GDDR was unable to ascertainwhether the failing system is a C-system. No further attempt at dead C-systemprocessing will be done. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR163I

Cause Dead C-system processing has ended. Previous messages indicate whether a problemexists. Action None.

GDDR164E

Cause A C-system has failed, but the C-system was not the master C-system. No master C-system transfer operation is necessary. GDDR may attempt to restart the failed C-system.This message is issued from an OSF server.

GDDR List of eligible master C-Systems unavailable

GDDR Unable to confirm that failing system system-name is a C-System

GDDR Dead C-System processing complete

GDDR Failing system system-name not the master C-System


Action None

GDDR165I

Cause As part of dead C-system processing, Dell EMC AutoSwap ownership has been transferredfrom the old primary DASD site to the new primary DASD site. Action None.

GDDR166E

Cause The system on which a GDDR script is running is not a system configured in GDDR. To bepart of the GDDR configuration, the system must have been assigned a GDDR site with aGDDR SITE parameter. These parameters have the format SITE.system-name. An internalerror code is generated and the current script is unsuccessful. Action If the system on which the script is running is the correct system, ensure that the GDDRparameters are loaded correctly and submit the script job again. Otherwise, ensure thatsubmitted script jobs always run on the system on which they are submitted.

GDDR195I

Cause In preparing to wait for invalid tracks to become synchronized (that is, for invalid trackcounts to become zero), GDDR has identified count number of gatekeeper-SRDF grouppairs, each of which will be used for an #SQ VOL command issued when checking R1device status. The indicated site is either the primary DASD site or, if a site swap script isissuing the message, the site that is to become the primary DASD site. The pairs arederived from entries in the Define SRDF Device Ranges panel. Action None.

GDDR196W

Cause After waiting for invalid tracks to become synchronized (i.e., for invalid track counts tobecome zero), GDDR has determined that nonzero invalid track counts remain. GDDRwaits, and checks the invalid track counts again. The tests will be applied to devices asdescribed in the GDDR195I message. Action None.

GDDR199I

GDDR AutoSwap ownership transfer complete

GDDR Current system system-name is not in the GDDR configuration

GDDR count {SRDF/S|SRDF/A} gatekeepers found for site-id

GDDR Some {SRDF/S|SRDF/A} devices not synched up, retrying(attempt nnn)


Cause As part of a site swap operation, an updated SRDF Host Component parameter member isbeing copied. The indicated program name is used for the copy. Action None.

GDDR200E


GDDR202E

Cause During preparation for issuing an SRDF group-based SRDF Host Component command, noparameters specifying SRDF/A gatekeepers were found. These parameters have theformat JA_ACT_GK.site-id.*. An internal error code is generated and the current script isunsuccessful. Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Then,submit the script job again.If the problem persists and the parameters appear to have been loaded correctly, contactthe Dell EMC Customer Support Center for technical assistance. Make sure you have theSYSLOG, the job log, and all relevant job documentation available.

GDDR210E

Cause During preparation for checking that devices have become synchronized, GDDR hasdiscovered that no parameters specifying gatekeeper-SRDF group pairs were found. Aninternal error code is generated and the current script is unsuccessful. Action If the required parameters have not been specified in the Define SRDF Device Rangespanel, supply the needed SRDF device ranges, and perform a parameter set activationwith the Partial keyword. Then, submit the script job again.If the problem persists and the parameters appear to have been loaded correctly, contactthe Dell EMC Customer Support Center for technical assistance. Make sure you have theSYSLOG, the job log, and all relevant job documentation available.

GDDR211E

GDDR Using program program_name as IEBGENER utility

GDDR Unable to continue, SRDF/HC command command is not supported

GDDR No SRDF/A gatekeeper parameters for site site-id are defined

GDDR No gatekeeper parameters for site site-id with RDF typesrdftype are defined


Cause The SRDF directors are inoperative. The script terminates. Action Check the links with the SRDF Host Component command #SQ LINK. Issue the SRDFHost Component command #SC LINK, dir#, ONLINE.

GDDR250E

Cause During HMC command processing by GDDR scripts, no eligible LPARs for the action werefound for the given site. Action Notify your GDDR administrator. This is usually a configuration issue where the LPARsassociated with a site are not properly defined. If you are the GDDR administrator andneed help diagnosing the problem, contact the Dell EMC Customer Support Center. Makesure you have all relevant job documentation available.

GDDR251E

Cause The Hardware Management Console (HMC) interface API failed on a LOAD CLEARoperation. Action Check your LOAD parameters, and make sure the HMC API is configured properly.

GDDR252E

Cause WTOR timed out. Action Rerun the script and respond to the WTOR.

GDDR253E

Cause The Hardware Management Console (HMC) interface API failed while issuing a functionagainst the system. Action Make sure the HMC API is installed properly.

GDDR254E

Cause

GDDR Device symdv# (RDFGRP srdfgrp) has invalid status status,unable to continue

GDDR No LPARs found

GDDR LOAD CLEAR on system system-name had failed

GDDR Issue_HWMCA_Commands timed out waiting for an operator reply

GDDR function pm system (system-name) failed

GDDR Action {ACTIVATE|DEACTIVATE} on system system-name failed


The Hardware Management Console (HMC) interface API failed while activating ordeactivating CBU. Action Make sure the HMC interface is installed properly.

GDDR270E

Cause While attempting to propagate one or more GDDR parameters to a remote C-system, theGDDR C-system communication manager has failed to detect a response from theindicated C-system. Processing continues. Action None.

GDDR271E

Cause GDDR is beginning propagation of the GDDR-defined set of parameters that must matchon all C-systems. Before doing so, GDDR has checked to ensure that the master C-systemknown to the remote C-system is the same as the master C-system known to the local C-system, and found that these are not the same. Propagation then proceeds. Action None.

GDDR272E

Cause During a broadcast to update and synchronization of the GDDR global variables across theC-systems an inconsistent configuration has been detected and the certainty of masterversus subordinate C-systems is now questionable. In order to prevent a serious disaster,updates to synchronize the GDDR global variables across C-systems is disallowed. Action Notify your GDDR administrator immediately. Check the active GDDR systemconfiguration and correct it. If you are the GDDR administrator and need help diagnosingthe problem, contact the Dell EMC Customer Support Center.

GDDR280E

Cause When determining which production systems to restart after a site swap or DASD siteswap, GDDR found no system at the new site other than the C-system. An internal errorcode is generated and the current script is unsuccessful. Action Determine why no production systems were found at the new site.

GDDR281E | GDDR281W

GDDR Found no active remote C-Systems to broadcast to

GDDR Remote system system-name has incorrect master C-Systemsystem-name instead of system-name

GDDR System system-name not permitted to update parameters onsystem-name

GDDR Found no active remote systems to start


Cause GDDR is beginning propagation of the GDDR-defined set of parameters that must matchon all C-systems. Before doing so, GDDR has checked to ensure that the master C-systemknown to the remote C-system is the same as the master C-system known to the local C-system, and found that these are not the same. Propagation then proceeds. Action None.

GDDR300I

Cause The indicated command on the GDDR command queue has been selected for processing.The internal task number, which can be used to correlate subsequent command statusmessages with the command, is also shown. Action None.

GDDR301I

Cause The SRDF Host Component command issued by GDDR using the listed GDDR commandqueue element number has finished with the indicated return code. Action For non-zero return codes, contact Dell EMC Customer Support. Keep the joblog andrelevant GDDRWORK logs, SRDF Host Component log and SCF trace.

GDDR309E

Cause A request was made to process the GDDR command queue, but the queue was found to beempty. The second line of the message shows when and by whom the queue was clearedor shows that it was never used. Action Use the information from the second line to determine how and when the command queuewas cleared. If script processing is involved, manual steps will have to be taken to eitherrecreate the necessary command queue elements or bypass the script step which is tryingto use the queue.

GDDR311I

Cause Upon completion of processing for the listed GDDR command queue element, GDDR freesthe command queue element storage at the listed address for the listed length.

GDDR Found no active remote systems to close down

(xxxx) HC Cmd=command

(xxxx) Command finished, return code rc

GDDR command queue is emptyCleared by jobname (job-id) at date timeQueue was never used

GDDR (xxxx) Released CQE @ address L(length) RC(rc).


Action None.

GDDR312I

Cause A command element has been created for the indicated SRDF Host Componentcommand. Action None.

GDDR313I

Cause A command from the GDDR command queue has completed processing. The messageindicates the command number, whether the command used the dynamic API (DYN) ornot (NDY), the return code from EMCSRDFR and the time spent in EMCSRDFR (fordynamic) or the time spent in EMCSRDFR and waiting for the command to complete (fornon-dynamic). This information may be useful if a problem occurs processing an SRDFHost Component command. Action None.

GDDR315I

Cause This message is generated when GDDR interfaces with other Dell EMC products such asSRDF Host Component and SCF. This message does not indicate any problem. However,if a GDDR problem exists, this message will be useful in analyzing the problem by the DellEMC Customer Support Center. Action If you contact the Dell EMC Customer Support Center for technical assistance for a batchjob, include all job related information. If this information message has been issued byGDDR, it will be included in the job log and no further action is required.

GDDR316I

Cause During processing of a command on the GDDR command queue, diagnostic informationinvolving the SRDF Host Component REXX API is displayed. This information may beuseful if a problem occurs processing a SRDF Host Component command. Action None.

GDDR (xxxx) Task Attached Successfully.

FC EMCSRDF_RC gave RC rc.or

EMCSRDF_CMD_RC=rc Seconds=sss.nnnnnnn.or

(cmd#) (DYN|NDY) EMCSRDFR RC=rc, Seconds=sss.nnnnnn.

(location_parm) Call to function_parm gave RC rc

(seq#) Queue_Element @ address save IRXINIT-P @ address)


●

●

●

●

GDDR317E

Cause The command queue processing ENQ could not be obtained. The most likely explanation isthat SRDF Host Component commands are currently in progress in the command queueworker.The resource name as well as the RC from the ENQ macro are indicated in the message.Possible return codes (in hex) and their meanings are as follows:

4 - The resource is not immediately available.

8 - A previous request for control of the resource has been made by the same task.

The task already has control of the resource.

14 - A previous request for control of the resource has been made by the same task.

The task does not have control of the resource.

18 - Environmental error. The limit for the number of concurrent resource requests

has been reached. Retry the request. If the problem persists, consult your system

programmer, who might be able to tune the system so that the limit is no longer

exceeded.For diagnostic purposes, this message is followed by multi-line message GDDUG27I, listingall GDDR ENQs currently held or waiting to be held and their owners. This should revealthe owner of the ENQ indicated in the GDDR317E message. Action Wait for the commands on the queue to complete, and retry. The F GDDRMAIN,CHecKupCMDQ DETail command may be used to monitor the command queue.Contact Dell EMC Customer Support if the problem persists.

GDDR318I

Cause GDDR command queue processing is finishing up with the listed command queue element. Action None.

GDDR319I

Cause The GDDR command queue lock was obtained or released, as indicated in the message. Action None.

GDDR322E

Cause A ConGroup command has been issued during script processing. However, the commandwas unsuccessful. Possible reasons for the failure include:

GDDT SRDF HC commands are in progress - ENQ for resource failedwith RC rc

GDDR (xxxx) Exiting ...

Command queue lock {obtained|released}

GDDR ConGroup function_name function failed, rc rc (text)


●

●

●

A ConGroup-related condition such as locked devices

A failure in the WTOR process (such as a timeout)

A system errorIn all these cases, an internal error code is generated and the current script isunsuccessful. Action Determine the cause of the failure and take corrective action. It may be sufficient tomanually enter ConGroup commands or to manually reply to GDDR WTORs. Then, submitthe script job again.

GDDR323I

Cause During processing of a command on the GDDR command queue, diagnostic informationinvolving the SRDF Host Component REXX API is displayed. This information may beuseful if a problem occurs while processing a SRDF Host Component command. Action None.

GDDR325I

Cause During processing of a command on the GDDR command queue, diagnostic informationinvolving the SRDF Host Component REXX API is displayed. This information may beuseful if a problem occurs while processing an SRDF Host Component command. Action None.

GDDR326I

Cause During processing of a command on the GDDR command queue, diagnostic informationinvolving the SRDF Host Component REXX API is displayed. This information may beuseful if a problem occurs processing an SRDF Host Component command. Action None.

GDDR327I


(command) PCRQB RC (rc) RE ('reason') REX ('rexx-string')

(command) varLen(nnnnn)

(command) varValue=variable

(command) Function=function_id SHVRET(return-code)SHVVALL=(variable)


●

●

●

●

●

●

●

GDDR328I


GDDR329I


GDDR330E

Cause An attempt was made to transfer the master C-system function, but the attempt failedbecause both non-master C-systems are marked as “not alive.” The master C-systemfunction is not transferred. An internal error code is generated and the current script isunsuccessful. Action Examine preceding messages to determine the reason for GDDR inability to transfer themaster C-system function. If a site is unavailable, manual recovery many be required.

GDDR331I

Cause A check of the state of DASD devices has failed. The message gives the gatekeeper,possibly the SRDF group, and the devices which failed. The particular check being made isindicated by the check description:

01 - device is expected to have at least 1 available mirror

02 - device is expected to have all mirrors ready

03 - device is expected to be an R2

04 - device is expected to be an R1

05 - device is expected to have an available mirror

06 - mirror is expected to be ready

07 - mirror is expected to be not readytoken-id indicates the number of the device parameter from which this device(s) wasobtained. It may also contain additional text as follows:

(command), EMCSRDFR returns count lines.

(command), Task using ENVBLOCK @ address

GDDR Unable to transfer master C-System, staying at system-name

(token-id) Device Check (check-description) Failed.GK(gk[,srdfgrp]) SymmDev(symdv#).


●

●

●

●

●

●

●

MIRROR NOT FOUND: The device does not have a mirror in the requested SRDF

group.

DEVICE DOES NOT EXIST: There is no such device in the storage system.

DEVICE NOT R1: The test requires that the device is an R1, but it is not.

META IN CKD RANGE. A meta device was found in a CKD device range.

NO META DATA FOR HEAD: A meta head was found, but it has no members.

UNABLE TO GET META DATA: An error occurred getting the list of meta members.

CKD/FBA MIX: A device range contained both CKD and FBA devices.All of these conditions mean that it was not possible to carry out the requested check. Ingeneral, these conditions indicate that the GDDR SRDF device parameters are incorrect. Action If the message indicates a condition caused by a parameter error, correct the parametersand retry. If not, the check may succeed if retried (for example, a mirror may notimmediately be ready after a swap, but may become ready after a short time). Dependingon why the check was being done, it may be retried automatically; if so, and if the checksubsequently succeeds, no action is necessary. If the check is not retried or is retried andcontinues to fail, you may need to investigate the status of the device with SRDF HostComponent commands and correct issues as needed.

GDDR332I

Cause The status of commands on the GDDR command queue is displayed. The message showsthe number of active commands (those currently being executed or awaiting execution),the number of completed commands, and the total number on the queue. Action None.

GDDR333I

Cause The GDDR command queue has been cleared at the indicated site. Action None.

GDDR334W

Cause An attempt was made to clear the command queue at the indicated site. However, theattempt did not succeed. The command queue has not been cleared. The return codeshown in the message is the return code from GDDRXCMD if the site is the local site orthe return code from the submission of work to a remote site. Action If the command queue needs to be cleared, you can use the Manage Internal CommandQueue panel to view and delete command queue elements, or you can use the GDDRCommand Queue utility (GDDRXCMD) program to clear the queue on the respective C-systems.

GDDR Cmds Active=count, Complete=count Total=count

GDDR Command Queue cleared at site site-id

Error clearing GDDR command queue at site site-id rc = rc


●

●

GDDR335W

Cause An attempt was made to clear the command queue at the indicated site. However, theattempt did not succeed for the reason given. The command queue has not beencleared. Reasons are as follows:

GDDRMAIN not active - Unable to communicate with GDDRMAIN on the remote

system.

No available worker - No worker available on the remote system to run the

command queue clear. Action If the command queue needs to be cleared, you can use the Manage Internal CommandQueue panel to view and delete command queue elements, or you can use the GDDR Command Queue utility (GDDRXCMD) to clear the queue on the respective C-systems.

GDDR336I

Cause Work was submitted to the indicated site to clear the command queue on that site. Thesubmitting code does not wait to see if the clear was successful. Action None required; however, you might wish to check if the command queue clear wassuccessful on the remote system. Check the output of GDDRWORK jobs on the remotesystem.

GDDR337E

Cause During dynamic device add or delete processing, devices have been added or deleted andnow the PARMS.RDF.DEVICES variables must be updated to reflect the changes.However, in order to do this, all C-systems must be up so that the variables can beupdated on all C-systems. Action Determine why the indicated C-system is down, ensure that all C-systems are up and thatGDDRMAIN is running on all, and resubmit the script.

GDDR344E

Cause GDDR0SMF has issued a message stating that it was called with an invalid, (empty),parameter list. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer Support

GDDR Command Queue not cleared at site site-id reason

GDDR Command Queue clear submitted to site site-id

At least one C-system (c-system-name) is down; RDF.DEVICES cannotbe updated

No Parameters Specified by Caller


Center for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR348E

Cause This message indicates that an execution parameter or a program argument is not valid forthe program to which it was passed. The parameter in error and possibly an explanation ofthe problem with its value may be displayed. Action If this message occurs due to program execution via JCL, refer to the documentation forthe program being executed, correct the PARM in the JCL and retry. If this messageoccurs as the result of executing a REXX program or script step, contact the Dell EMCCustomer Support Center for assistance.

GDDR349I

Cause The Hardware Management Console object ID for the indicated LPAR or system has beensaved in a GDDR parameter. Processing continues. Action None.

GDDR350E

Cause While performing HMC discovery, GDDR issued a USS call which encountered an error.This message is followed by one or more instances of message GDDR351E, giving the textof an output line returned by the call A nonzero error code is generated and the currentscript is unsuccessful. Action Resolve the problem using the messages that follow. Then submit the script again.

GDDR351E

Cause While performing HMC discovery at the indicated site, GDDR issued a USS commandwhich encountered an error. This GDDR message includes a message returned from theUSS command. One instance of this message occurs for each error message returnedfrom the USS command. Action None.

GDDR352E

Missing or invalid parmInvalid parm: parameter-valueArgument argument is not valid for program pgm-name

GDDR Saved ObjectID hmc-object-id for {system system-name|LPARlpar-name}

GDDR USS call returned rc = rc, output follows

GDDR > error_message


Cause During preparation for HMC discovery, no parameters specifying LPARs at the indicatedsite were found. These parameters have the format site-id.LPAR.*. An internal error codeis generated and the current script is unsuccessful. Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Then,submit the script job again. If the problem persists and the parameters appear to have been loaded correctly, contactthe Dell EMC Customer Support Center for technical assistance. Make sure you have allrelevant job documentation available.

GDDR353I

Cause While performing HMC discovery, GDDR issued a USS call which has returned a time-outreturn code. A return code of zero is being substituted for the USS return code. Action None.

GDDR354E

Cause USS command timed out attempting HMC discovery from primary network path and isattempting to retry from alternate network path Action If the retry succeeds, notify your GDDR administrator to determine if the GDDR timeoutvalue needs to be increased or if there is a problem with the your HMC configuration. Ifthe retry fails, contact your GDDR administrator immediately.

GDDR355E

Cause An error occurred invoking the SRDF Host Component REXX API output formattermodule. The error code returned and command on whose behalf the invocation was beingattempted are given. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR356E

Cause

GDDR Found no LPAR parameters for site site-id

GDDR USS call timed out, altering return code to zero

GDDR Retrying HMC discovery using hmc-object-id after rc rc fromsite site-id

GDDR EMCSRDFC returned rc rc for function api-command

GDDR ADDRESS LINKMVS for module-name failed, rc = rc, functionfunction-id


An error occurred invoking the indicated module through the LINKMVS environment. Thefunction on whose behalf the invocation was being made is given. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR357I

Cause While performing HMC discovery at the indicated site, GDDR has determined the LPAR-system pairs that will be managed. This message is the header for the list of pairs, and isone instance of message GDDR358I for each distinct LPAR-system pair. Processingcontinues. Additional information regarding the means by which these pairs are created isfound in the description of the LPAR GDDR parameter in the GDDR Product Guide foryour configuration. Action None.

GDDR358I

Cause While performing HMC discovery at the indicated site, GDDR has determined the LPAR-system pairs that will be managed. One instance of this message for each distinct LPAR-system pair. Processing continues. You can find additional information about how thesepairs are created in the description of the LPAR GDDR parameter in the GDDR ProductGuide for your configuration. Action None.

GDDR359I

Cause As part of performing HMC discovery at the indicated site, GDDR has requested a list ofall objects at the site. The list was returned, and GDDR is about to is about to extract HMCobject specifications from the list. Processing continues. Action None.

GDDR360E

Cause While performing HMC discovery, GDDR encountered an error invoking a USS command.No output was returned. If the USS return code indicated a time-out, message GDDR353Iwill be issued and a return code of zero set. Otherwise the USS return code is used as thereturn code. If the internal error code is not zero, the current script is unsuccessful. Action

GDDR Managing the following LPAR-system pairs for site site-id

GDDR > lpar-name : system-name

GDDR Checking for HMC objects at site site-id

GDDR USS call returned rc rc, no output available


Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR361E

Cause While performing HMC discovery, Dell EMC GDDR has issued a USS call which returnedcode zero. However, the error message indicated was returned. A nonzero error code isgenerated and the current script is unsuccessful. Action Resolve the problem indicated by the error message. Then submit the script again.

GDDR363I

Cause An HMC (Hardware Management Console) action is being taken or a command is beingissued by means of HMC. The IP address in use for the HMC console through which theaction is taken or command issued is given, together with the site ID of the site at whichthe HMC console is defined. Processing continues. Action None.

GDDR364I

Cause An HMC (Hardware Management Console) action is being taken or a command is beingissued by means of HMC. This message indicates the optional parameters being passedwith the command. Processing continues. Action None.

GDDR365E

Cause While performing HMC (Hardware Management Console) discovery, GDDR detected aUSS command timeout. No output was returned. If the USS return code indicated a time-out, message GDDR353I will be issued and a return code of zero set. Otherwise the USSreturn code is used as the return code. If the internal error code is not zero, the currentscript is unsuccessful. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR USS call returned message error_message

GDDR Using site-id HMC IP address ip-address

GDDR Using HMC optional parameters parameters

GDDR USS call timed out, no output available


GDDR367E

Cause While performing HMC discovery at the indicated site, GDDR has identified an invalidvalue in object descriptor output returned from a previously issued USS command.Processing continues. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR368I

Cause While performing HMC (Hardware Management Console) discovery at the indicated site,GDDR has discovered the indicated object. Processing continues. Action None.

GDDR369I

Cause While performing HMC (Hardware Management Console) discovery, GDDR identified anLPAR-system pair and attempted to locate an HMC object associated with that pair. Themessage indicates whether or not an associated HMC object was found. Failure to find anassociated object is not an error. Processing continues. Action None.

GDDR370A

Cause Requested operator confirmation denied, Script processing terminates with an error. Action Ensure that the reason for denying the request was valid. Because no other planned scriptmay run until the current script completes, it is necessary to ultimately allow the request.

GDDR370I

Cause (When preceded by message GDDR370A.) A script needed to perform a master C-systemfunction transfer in order to complete. However, the operator denied the request. Scriptprocessing terminates with an error.

GDDR >>> Bypassing invalid HMC component_type name(component_name)

GDDR > {lpar-name|system-name|hmc-object-id}

GDDR HMC object for {lpar-name|system-name} {found|not found}

GDDR Operator confirmation not obtained

GDDR C-System master function transfer aborted


●

●

●

Action Ensure that the reason for denying the transfer request were valid. Since no other plannedscript may run until the current script completes, it is necessary to ultimately allow thetransfer request.

GDDR370W

Cause When the GDDR Heartbeat Monitor starts, it verifies that the master C-system is runningin the correct location, and if not, it transfers it to the correct location. However, thattransfer was not done for the reason given. Possible reasons include:

Planned script in progress

Unplanned script in progress

Operator confirmation not received Action If that situation is not remedied (such as by the completion of a script), take action tomove the master C-system to the correct location at the appropriate time.

GDDR371E

Cause While GDDR issued the indicated command, and then issued a WTOR to wait for amessage indicating the end of command processing. Either a CANCEL reply was entered,or the WTOR timed out. An internal error code is generated and the current script isunsuccessful. Action Determine the reason for the unsuccessful complete. Take appropriate corrective actionand start the script again.

GDDR372W

Cause During initial environment checking, a GDDR processing routine determined that it wasrunning on a C-system that is not the master C-system. This is normally not permitted forthe processing routine that is executing. Because MSC high availability is in effect,however, processing is allowed to continue. Action None.

GDDR373I

Cause Normal status progress message during GDDR broadcast global variables function. Action None.

Master C not transferred to new-c-system from old-c-systemReason - reason

GDDR MSC msc_command command did not complete successfully

GDDR Function function may only run on the master C-System. MSCHigh Availability override

GDDR Broadcasting gv_name = gv_value


GDDR374I

Cause The broadcast global variable function is performed on behalf of a GDDR messageinterception rule. This shows the action being performed. Action None.

GDDR375I


GDDR376I


GDDR377I


GDDR378I


GDDR380I

Cause Normal status progress message during GDDR broadcast global variables function. Action

GDDR -> gv_name set to gv_value at site-id

GDDR Var name: gv_name

GDDR Var val: gv_value

GDDR Broadcasting values for GDDR broadcast set

GDDR Broadcasting new heartbeat for c-system-name

GDDR Setting <site-id>-Heartbeat-Missing indicator ON/OFF


None. GDDR381I


GDDR382I


GDDR383I


GDDR386A

Cause This non-scrollable message is issued by GDDR message rule EMCMB14E. In SRDF/Starwith AutoSwap configurations, the most likely cause is that the device is offline. Action Investigate the reason why the MSV address indicated in message EMCMB14E is notacceptable as a gatekeeper device for the indicated MSC group and correct the problem.If this message occurs during a GDDR script, resubmit the script after the gatekeeperissue has been resolved.

GDDR386E

Cause There was an abend due to an internal GDDR error for a particular message code. You canfind the original reason why this message code was issued by locating the message in thethis document with an ID of “GDD” followed by the message ID specified in the message-id. Action Contact Dell EMC Customer Support to resolve the GDDR386E message problem. Referto the identifier of the original message for information about what caused this problem.

GDDR Setting <system-name>-Planned-IPL indicator ON/OFF for sitesite-id

GDDR Setting run variable gv_name for script script-name to rc

GDDR Setting site-id state to state_value

GDDR *** WARNING *** MSC Activation failure *** on system-name

ABEND WHILE PROCESSING MESSAGE ID: message-id


GDDR387W

Cause No variables for the indicated action (ADD or DEL) were found for the indicated site pair. In general, this message should not occur, since if there are no such variables, the stepshould not have been included in the script. However, there may be extenuatingcircumstances such that this is not an error. Action Investigate and correct the problem.

GDDR388E

Cause In dynamic device manipulation, indicates if the specified device in the specified storagesystem is in an SRDF group. This message indicates that the device is either in a GDDR-used SRDF group when itshould be in a staging group or is in a staging SRDF group when it should be in aproduction SRDF group. Action Investigate why the device is in the wrong group, correct it, and rerun.

GDDR389E

Cause A console command was issued, but no response to the command was received. Aresponse was expected. Action Investigate the command in the syslog and determine why a response was not received.Correct the problem and retry or contact the Dell EMC Customer Support Center forassistance.

GDDR390E

Cause A console command was issued, but the response did not indicate that the command wassuccessful. The command response is displayed as subsequent lines of this message. If acommand response is not available, an alternate format is used, referring the user to theResourcePak Base (SCF) joblog. Action Determine why the command failed, correct the conditions that caused it to fail, and retry.

GDDR391I

Cause

No dynamic device action variables found for site-ids

Device symdv# in Symm symm-serial is [not] in RDF group srdfgrp

No command response received

Command failed, command response follows:orCommand failed, please check SCF joblog

Command succeeded


●

●

●

●

●

●

●

A console command was issued, and the response indicates that the command wassuccessful. Action None.

GDDR392E

Cause An attempt was made to issue a console command, but the command submission failedwith the return code indicated.Possible return codes are:

8 - error in MGCRE 99 - GDDR console name not set

104 - no date block available for command response

108 - MCSOCART subtask (of MCSOPER in GDDRMAIN) not running

112 - Timeout waiting for worker response. Note that this is not a timeout waiting for

command response. Action If possible, correct the condition which caused the error and retry.

GDDR393E

Cause The indicated MSC group is defined in the GDDR parameters, but is not known to the SCFconnected to GDDR. Action Determine the cause of the problem. Possibilities include:

GDDR is not connected to the correct instance of SCF .

The GDDR parameters are in error.

The MSC/SCF definition is incorrect.Correct the problem and retry.

GDDR394E

Cause The system on which this message was issued is not the current ConGroup owner. Thissystem must be the ConGroup owner for the action to proceed. Action If necessary, transfer ConGroup ownership to the current system and retry.

GDDR395E

Cause The indicated device (in the storage system referenced by the gatekeeper in parenthesis)is ConGroup-protected in the indicated SRDF staging group.

Command submission failed, return code rc

MSC Group mscgrp not known to SCF

This system not ConGroup owner

site-id device symdv# (gk) is ConGroup protected in staging groupsrdfgrp


●

●

Action Remove ConGroup protection from the device and retry.

GDDR396E

Cause The indicated device (in the storage system referenced by the gatekeeper and SRDFgroup in parenthesis) is in the TNR (Target Not Ready) state. Action Make the target device SRDF Ready and retry.

GDDR397E

Cause The indicated device (in the storage system referenced by the gatekeeper and SRDFgroup in parenthesis) timed out waiting for invalid tracks to synchronize (go to zero). Action Determine the reason that invalid tracks did not go to zero, correct the problem, and retry.

GDDR398E

Cause A timeout occurred while waiting for a dynamic device action (MSC ADDDEV or DELDEV)to begin or complete for the SRDF/A session identified by the MSC group name, gatekeeper, and SRDF group. Action For a timeout waiting for the action to begin:

Check the SCF (ResourcePak Base) job log for messages related to other ADDDEV

or DELDEV MSC activity.For a timeout waiting for the action to complete:

Perform dynamic device actions with fewer devices in a single SRDF group affected,

or increase the GDDR WTOR Wait Time and/or WTOR Wait Retries tuning

parameters. When re-running the Dynamic Device Add script, do NOT skip the failing

step, unless you have verified that all MSC device ADD/DEL actions have completed. GDDR400E

Cause A call has been made to GDDRINFO to retrieve the HMC method to use with respect totarget CPC. GDDRINFO was unable to identify a local method or another system capableof taking care of the request on this system's behalf. Discovery continues usingHWMCAAPI (OPS) as the HMC method. Action Examine the CPC parameters in GDDRPARM to ensure a method is specified for the

Device symdv# (gk,srdfgrp) found in TNR state

Device symdv# (gk,srdfgrp) timed out waiting for synchronization

Timeout waiting for MSC {ADDDEV|DELDEV} to {begin|complete} formscgrp, gk, srdfgrp

Cannot determine HMC method for cpc-name from c-system-nameHWMCAAPI used


source C-system to HMC manage the target CPC or that another system can be used tosatisfy the HMC management request. HWMCAAPI (OPS) becomes the default.

GDDR401E

Cause A call has been made to GDDRINFO to retrieve the HMC method to use with respect totarget CPC. No information at all was returned from GDDRINFO, indicating the call failed. Action Examine the GDDRWORK (XRnn/XHnn) tasks on the local or remote C-Systems todetermine why the GDDRINFO call from HMC Discovery failed. Record any ISPFinformation displayed. Discovery continues using HWMCAAPI (OPS) as the HMC method.

GDDR402I

Cause This message specifies the name of the system on which the processor identified in theprevious GDDR727W message is running. Processing continues. Action None.

GDDR411E

Cause While checking for SRDF/S R1 devices requiring special processing, the indicated R1device was found to have invalid tracks but was not in TNR status. Because SRDF/S R1devices are always synchronized with their paired R2 devices, an invalid track conditionrepresents a serious problem. Action Investigate device synchronization problem with Dell EMC INlines. After synchronization isachieved, rerun the script.

GDDR412E

Cause A GDDR script is waiting for SRDF data synchronization to complete, and is monitoringinvalid tracks on GDDR managed devices. During this monitoring, a device was detectedwith an unexpected device type in the indicated SRDF group. The message shows theexpected device type, R1 or R2, and the discovered device type. Action Review the job log and SYSLOG for errors. Look for failures in an R1-R2 Swap of Half-Swap step in the current or earlier script run. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

ERROR setting HMC method for cpc-name from c-system-name HWMCAAPIused

GDDR Running on system-name, master C-System is c-system-name

GDDR Device symdv# in RDF group srdfgrp has status status withcount R2 invalids

GDDR Device symdv# in RDF group srdfgrp not an expected-dev-type,has MR of mirror


GDDR413E

Cause A preceding step has left this R1 device with the unexpected status of -R. Possibly aprevious SRDF Host Component REFRESH command issued to an R2 device was followedby a SWAP. Action Examine the previous script log for possible causes Issue an RFR-RSUM or RNG-RSUMto clear the -R flag after verifying the correct synchronization direction through the SQRDFGRP or SQ CNFG commands.

GDDR414E

Cause The gatekeeper could not be found for upcoming REFRESH and/or RDF-RSUMcommands, possibly due to incorrect SRDF device ranges specified during the parameterload. Action Verify and reload correct SRDF devices using the Define SRDF Device Ranges panel, andperform a parameter set Activate with the Partial keyword.

GDDR451I

Cause While checking for invalid tracks on SRDF/S devices during a site swap, none were found.Processing continues. Action None.

GDDR452E

Cause While checking for invalid tracks on SRDF/S devices during a site swap, one or moredevices were found with invalid tracks. A nonzero error code is generated and the currentscript is unsuccessful. Action Determine the reason for the existence of invalid tracks on SRDF/S devices. Thisrepresents an SRDF error condition which must be corrected. After the condition iscorrected, submit the script job again.

GDDR453I

Cause Indicates the number of contiguous device ranges found having at least one device in TNRstatus.

GDDR Device symdv# in RDF group srdfgrp has refresh flag ON,status

GDDR Gatekeeper device could not be determined

GDDR Found no devices with invalid tracks

GDDR Found {nnn devices|1 device} with invalid tracks

Found count range[s] in TNR-status


Additional messages will be issued, identifying the device ranges and showing commandsbeing issued against these devices to remove the TNR status. Action None.

GDDR454E

Cause This message indicates the total number of devices with invalid tracks found during thecheck. Action Determine the cause of the invalid tracks. Additional debug information is included in theoutput.

GDDR455E

Cause The indicated ConGroup command failed with the listed error message. Action Look up the indicated ConGroup message ID in the Mainframe Enablers Message Guide.Correct the problem and resubmit the script.

GDDR510E

Cause While validating the state for the cleanup and resumption of SRDF/A, GDDR hasdetermined that SRDF/A is not yet ended. An error code is generated and the script isunsuccessful. Action Run the Resume SRDF/A script only when SRDF/A is down.

GDDR522I

Cause This is an informational message stating what community name will be used for HMCactions. Action None.

GDDR530E

Cause During preparation for checking the status of SRDF/S or SRDF/A devices, no parametersspecifying device ranges were found for the indicated site. An internal error code isgenerated and the current script is unsuccessful.

GDDR Found a total of count devices with invalid tracks

ConGroup command command failed, refer to message message-id

GDDR Script can only be run when SRDF/A has stopped

GDDR Will use HMC community community-name

GDDR Found no GDDRSTAR {SRDF/A|SRDF/S} parameters for site site-id


Action If the required parameters have not been specified in the parameter load input file, createneeded parameter statements and run a parameter load job without initialization. Thensubmit the script job again. If the problem persists and the parameters appear to havebeen loaded correctly, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR531E

Cause An attempt was made to run a GDDR BCV Restore against the Primary DASD Site. This isnot supported. Action Select a different site as target for the BCV Restore.

GDDR532I

Cause While validating the environment for a GDDR-controlled BCV Restore operation, R2devices are found at the target site.The message also identifies the SRDF source site. Action None.

GDDR533I

Cause While validating the environment for a GDDR-controlled BCV Restore operation, aResynch-in-progress indicator was found.The message identifies source and target site. Action None.

GDDR534E

Cause While validating the environment for a GDDR-controlled BCV Restore operation, aResynch-in-progress indicator was found for more than one SRDF source site to theselected target site.This is an unexpected condition. GDDR only runs one resynchronization script at a time. Action Contact Dell EMC Customer Support to clear the unwanted Resynch-in-progressindicator.

GDDR535E

GDDRPBCR not allowed at the Primary DASD Site, exiting

GDDRPBCR found R2 devices at target-site (<- source-site)

GDDRPBCR found a Resynch-in-progress indicator for source-site ->target-site

GDDRPBCR found a dual Resynch-in-progress indicator for site-id


●

●

Cause While validating the environment for a GDDR-controlled BCV Restore operation,GDDRPBCR found no indication that the data on the GDDR-managed SRDF devices isbad. No GDDR Resynch-in-progress indicators were found, and no local invalid trackswere found.Alternatively, some or all of the local devices were found not to be R2 for any of the pairedsites.GDDR does not allow an automated BCV Restore in these circumstances. Action Verify the data on the GDDR-managed SRDF devices as well as on the BCV devices.Contact Dell EMC Customer Support to either perform a BCV Restore outside of GDDR orto abandon the BCV Restore script.

GDDR536E

Cause While validating the environment for a GDDR-controlled BCV Restore operation either atDC1 or at DC2 in an SRDF/Star configuration, GDDRPBCR did not find a GDDR Resynch-in-progress indicator. Because SRDF/A devices can be a subset of SRDF/S devices,GDDRPBCR cannot determine which devices need a BCV Restore, and exits.An automated BCV Restore is not currently possible in this situation. Action Contact Dell EMC Customer Support to either perform a BCV Restore outside of GDDR orto abandon the BCV Restore script.

GDDR537E

Cause While validating the environment for a GDDR-controlled BCV Restore operation,GDDRPBCR tried to check the BCV devices for local invalid tracks, but got an unexpectedreturn code from GDDRMIN0, or a positive indication that some BCVs have local invalidtracks, and exits. Action

If the message indicates local invalid tracks were found, contact Dell EMC Customer

Support to investigate the cause of the local invalid tracks on the BCV devices, and

possibly remediate the problem. Caution is required when attempting a BCV Restore after the problem is fixed. It isrecommended to review the data on the affected BCV before continuing. The bestcourse of action might be to abandon the BCV Restore script.

If the message indicates an unexpected return code from GDDRMIN0, check the job

log for messages from the GDDR Invalid Track monitor. This could be an internal

GDDRPBCR found no indication of an ongoing resynchronization tosite-id. BCV Restore not allowedor

GDDRPBCR found site site-id not pure R2 for any paired site. BCVRestore not allowed

GDDRPBCR unable to determine which devices need a BCV Restore

Some BCV devices at site-id have Local Invalid Tracksor

RC=rc from GDDRMIN0 while attempting to query BCVs at site-id forLocal Invalid Tracks


error. In that case, also contact Dell EMC Customer Support and provide the job log. GDDR538E

Cause While validating the environment for a GDDR-controlled BCV Restore operation,GDDRPBCR found that some of the BCVs required for the BCV Restore are not in a SPLITstate, and exits. Action Best course of action is probably to abandon the GDDRPBCR script. Although it might bepossible to SPLIT the BCVs at this time, they are not at all guaranteed to form aconsistent restartable image with the BCVs SPLIT earlier.

GDDR539E

Cause While validating the environment for a GDDR-controlled BCV Restore operation,GDDRPBCR found the BCV devices do not form a complete set for the SRDF devices towhich they would be restored, and exits. Action Best course of action is probably to abandon the GDDRPBCR script. Although it might bepossible to pair BCVs to the devices that miss them, this is not guaranteed to create aconsistent restartable image.

GDDR540I

Cause The requested BCV Restore operation has completed successfully. Action None.

GDDR541I

Cause After a successful BCV Restore, GDDRPBCR has cleared the Resynch-in-progressindicator, so that the DR-script can now be run. Action None.

GDDR542E

GDDRPBCR found some BCV devices at site-id not SPLIT

GDDRPBCR found some GDDR managed SRDF devices at site-id with nopaired BCV device

GDDRPBCR BCV Restore at site-id complete

GDDRPBCR Resynch-in-progress indicator source-site -> target-sitecleared

GDDRPBCR failed to clear local invalid tracks at site-idor

RC=rc from GDDRMIN0 while attempting to verify local invalidtracks at site-id


Cause After a successful BCV Restore, GDDRPBCR tried to check the GDDR-managed SRDFdevices for local invalid tracks, but either received an unexpected return code fromGDDRMIN0 or a positive indication that some devices still have local invalid tracks. Action If the message indicates local invalid tracks are found, contact Dell EMC CustomerSupport to investigate the cause.If the message indicates an unexpected return code from GDDRMIN0, check the job logfor messages from the GDDR Invalid Track monitor. This could be an internal error. In thatcase, also contact Dell EMC Customer Support and provide the job log.

GDDR543E

Cause A GDDR BCV Restore script was run, but the call override for simulated BCV managementwas selected.Since all validations in the GDDR BCV restore script have been done successfully, there isa good chance that an actual BCV Restore is needed before a DR script should beattempted. The script does not clear any Resynch-in-progress indicators, ensuring that noDR scripts are selectable. Action Either rerun the script with real BCV management selected or contact Dell EMC CustomerSupport to abandon the GDDRPBCR script.

GDDR544E

Cause During validation of the environment for a GDDR-controlled BCV Restore, GDDRPBCRfound non-GDDR SRDF groups for some GDDR-managed SRDF devices. GDDR does notmonitor these groups, so it becomes user responsibility to ensure that resynchronizationoperations on these non-GDDR SRDF groups do not cause data integrity issues during alater DR restart at this site.Alternatively, GDDRPBCR found that the storage system at the other end of a GDDR-managed SRDF group, was not the one defined to GDDR. This is not supported, andGDDRPBCR exits. Action Refer to message GDDR545E for a list of devices for which non-GDDR SRDF groups or anunexpected paired storage system were found.For the first format of this message, reply to WTOR GDDO173A to either stop or continuethe script.

GDDR545E

Cause This message lists a device for which a non-GDDR SRDF group or an unexpected pairedstorage system was found during a GDDR BCV Restore script.

GDDRPBCR SIMULATED the Restore of BCVs at site-id

GDDRPBCR found NON-GDDR ra groups for the following devices:or

GDDRPBCR found unexpected paired Symmetrix for the followingdevices:

symmserial symdv# srdfgrpsymmserial symdv# serials


The message identifies the storage system serial number, the device number and theSRDF groups for the device, or the expected and the unexpected paired storage systemserial number.The non-GDDR SRDF group or the unexpected paired storage system has an "!" appendedto it. Action See message GDDR544E.If the message shows ONLY SRDF groups with "!" appended, the device is not paired in aGDDR-managed SRDF group. This is a serious configuration issue, and the BCV Restorescript should probably be abandoned.

GDDR546E

Cause The GDDR BCV Restore script was started, but GDDR has no BCV devices defined for theselected site. Action Contact Dell EMC Customer Support to abandon the GDDRPBCR script, or select adifferent target site for the script.

GDDR547E

Cause This message identifies BCV devices which are not in a SPLIT state. BCV Restore is notpossible at this time. Action See message GDDR538E.

GDDR548E

Cause This message identifies GDDR-managed SRDF devices for which no paired BCV devicewas found. BCV Restore is not possible at this time. Action See message GDDR539E.

GDDR588E

Cause During a script controlled test IPL the target site was not found in the configured eligiblesite list for this action. Action Verify your configuration and ensure the target and the configuration are correct. If youstill can not determine what is wrong and how to correct it, contact the Dell EMCCustomer Support Center for help.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentation

GDDRPBCR Unable to continue: NO BCVs defined at site-name

GDDRPBCR Symmetrix: symmserial BCV: symdv# State: state

GDDRPBCR found no BCV paired with device symdv# in Symmetrixsymmserial

GDDR Specified site site is not a configured site


available. GDDR592I

Cause A query (local or remote) has been done to determine if SRDF/A is active or not. Themessage shows the path and SRDF group which were interrogated, as well as other SRDFinformation. The status (active or not active) is shown. If the status is not active, the C-Ahead field shows 0 meaning 'No' or 1, meaning 'Yes', and the Cycle TOD shows the lasttime that SRDF/A was active on this SRDF group. If MSC is not active on this SRDFgroup, the Rcv Tag will be shown as all dashes (-), and C-Ahead and Host InterventionRequired will be shown as "N/A".In 2-site SRDF/A configurations, C-Ahead will always be shown as "N/A". Action If the status is not active, you may need to take action to resume SRDF/A if it is needed.

GDDR608W

Cause A GDDR-managed system running in a sysplex is seen as inoperative on XCF. Action Wait for the accompanying WTOR GDDR870A and reply to it appropriately.

GDDR610E

Cause This is issued after RESET_CLEAR or LOAD_CLEAR. If successful, set ‘planned IPL’indicator on. Action None.

GDDR610I

Cause The specified action was successfully performed on the specified system. Action None.

GDDR611I

Cause After RESET_CLEAR or LOAD_CLEAR. If successful, set ‘planned IPL’ indicator on.

{LCL|RMT} Query for RDF group srdfgrp using gk gk:SRDF/A is [NOT] active, Cycle # = cycle#, Rcv Tag = receive_tagC-ahead = {0|2|N/A}, Cycle TOD mm/dd/yyyy hh:mm:ssHost Intervention Required {NO|YES|N/A}

GDDR XCF Detected inoperative system system-name at site site-id

GDDR {Reset Clear|Load Clear} of system system-name {wassuccessful|failed}

GDDR hmc_action on system system-name was successful

GDDR command command completed with rc = rc


Action None.

GDDR612I

Cause This message indicates that GDDR has issued a command to an Dell EMC subsystem andthen has issued a WTOR. GDDR will now wait for a message rule to be triggered when thesubsystem issues a completion command, either successful or unsuccessful. The messagerule will reply to the WTOR. Action None.

GDDR614I

Cause Existing coupling facility datasets do not match the expected datasets. Action None.

GDDR615E

Cause A GDDR program did not receive any output from a command. The message provides thename and the return code from the program that issued the command. The associatedGDDR script step fails. Action Search the GDDR script job log, the syslog and the OSF server job log for related errormessages to determine why the program did not get any output. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID. If you cannot determine and correct the problem, contact the DellEMC Customer Support Center for technical assistance. Make sure you have all relevantjob documentation available.

GDDR615I

Cause The indicated program, invoked during HMC processing, did not return output. The returncode is set to 99. Action None.

GDDR616E

Cause The GDDR Couple Dataset Management function issued a D XCF,COUPLE command but

GDDR action command issued, now waiting for completion

GDDR cf {A|P} COUPLE DSN should be dsname on system system-name

GDDR program_name returned no output, rc = rc

GDDR hmc_c_program returned no output, rc = rc

GDDR program_name did not return IXC358I message.


did not get the expected IXC358I message. The associated GDDR script step fails. Action Search the GDDR script joblog, the syslog and the OSF-server joblog for related errormessages to determine why the program did not get the expected output. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR617A

Cause This message indicates that the script has terminated because no reply was received to aWTOR issued within the script. The run variable for the script step within which theWTOR was issued is set to indicate that the script step ended with return code 12. Action If necessary, restart the script and be certain to issue appropriate replies in a timelymanner. If the WTOR wait time is too short, modify the WTOR Wait Time value in theSpecify GDDR Tuning Values panel.

GDDR617E

Cause This message indicates that an unexpected return code was received from the WTORroutine. Processing continues. Action None.

GDDR618E

Cause A GDDR WTOR request for an operator response was unanswered within the timespecified by the WTOR Wait Time value in the Specify GDDR Tuning Values panel.GDDRprocessing is halted. Action Resubmit the script if the requested action is to be completed. If the WTOR wait time istoo short, modify the WTOR Wait Time value.

GDDR619E

Cause A GDDR program issued a command but did not receive all the expected output. The nameof the program is indicated in the message, along with number to help in debugging. Action Search the GDDR script joblog, the syslog and the OSF-server joblog for related error

GDDR Reply not received within designated wait interval, operationcancelled

GDDR Detected error in reply to WTOR in program_name, rc = rc

GDDR Reply not received within designated time, operationcancelled

GDDR program_name output was truncated. (case n)


messages to determine why the program did not get the expected output. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID. If you cannot determine and correct the problem, contact the DellEMC Customer Support Center for technical assistance. Make sure you have all relevantjob documentation available.

GDDR620E

Cause The GDDR Couple Dataset Management function issued a D XCF,COUPLE command, butthe output of the command showed neither primary nor alternate couple dataset name forthe indicated type. The Couple Dataset Management script step fails. Action Search the GDDR script joblog, the syslog and the OSF-server joblog for related errormessages to determine why the program did not get the expected output. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR621E

Cause The request to realign Primary and Alternate Couple datasets is rejected because bothdataset names provided to GDDR for usage in the current context are the same. Action Review the Couple Dataset names at the Define Managed Couple Datasets panel, andcorrect them. GDDR requires four different dataset names for each type of CoupleDataset. The Define Managed Couple Datasets panel provides information about how eachof these datasets is used by GDDR.

GDDR622I

Cause This message indicates that the necessary environment for the running or resumption ofthe indicated script has completed successfully. Processing continues. Action None.

GDDR625I

Cause This message indicates the system name of a system obtained during a call to identify allsystems at a specified site that are accessible. Processing continues.

GDDR program_name returned neither Primary nor Alternatecouple_type Couple Dataset name.

GDDR Couple DS Realignment rejected: Primary and Alternate Datasetnames must not be the same.

GDDR A valid environment exists, OK to {run|resume} scriptscript_processor

GDDR Added system system-name for site site-id to system list


Action None.

GDDR626I

Cause GDDR is adding the specified couple dataset as an alternate couple dataset of thespecified type on the specified system. Action None.

GDDR627I

Cause GDDR is switching to the specified couple dataset as the new primary couple dataset ofthe specified type on the specified system. Action None.

GDDR628E

Cause A GDDR program did not receive required output from a command. The message identifiesthe required output, the command text, the object to which the command applies and thesystem where the command was issued. The associated script steps fails. Action Search the GDDR script job log, the syslog and the OSF server job log for related errormessages to determine why the program did not get the expected output. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID. If you cannot determine and correct the problem, contact the DellEMC Customer Support Center for technical assistance. Make sure you have all relevantjob documentation available.

GDDR629I

Cause The GDDR event monitor is already handling an RDR event. No additional action isrequired. Action None.

GDDR630I

GDDR Adding dsname as new couple_type A-Couple Dataset on systemsystem-name

GDDR Switching to dsname as new couple_type P-Couple Dataset onsystem system-name

GDDR Required message-id not found for command command for object-name on system system-name

GDDR Already handling RDR event, further action bypassed

GDDR Expected message-id not found for command command for object-name on system system-name


Cause A GDDR program did not receive expected output from a command. The messageidentifies the expected output, the command text, the object to which the commandapplies and the system where the command was issued. The associated script stepcontinues processing. Action None if the GDDR script continues normally as expected. If a failure is associated with thismessage, search the GDDR script job log, the syslog and the OSF-server job log forrelated error messages to determine why the program did not get the expected output.Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for technical assistance. Make sure youhave all relevant job documentation available.

GDDR632I

Cause The SRDF Host Component API command shown has failed or aborted. The ID of theprimary SRDF Host Component error message is shown. An internal error code is set to99. Action Determine the proper action to take by finding the explanation of the SRDF HostComponent message.

GDDR636I

Cause The master C-system transfer function, while determining which C-system could becomethe new master C-system, removed the indicated C-system from consideration because itappears not be accessible to the current C-system. The remaining C-system is checkednext. Action None .

GDDR637I

Cause The transfer of the master C-system function has completed successfully. Action None.

GDDR638E

Cause The transfer of the master C-system function has terminated because of an error. Themaster C-system function remains at the site where it was running. Action Examine earlier messages to identify the cause of the problem. Correct the problems and

GDDR API function api-function completed with rc r?

GDDR Candidate C-System system-name at site site-id dead, skipping

GDDR Master C-System transfer successful

GDDR Master C-System transfer failed with rc rc


restart the process which was attempting to transfer the master C-system function. GDDR639I

Cause The named process has completed. The return code is provided. Action None.

GDDR641I

Cause During recovery processing, GDDR is waiting for session consistency before continuingthe recovery script. Action Reply S to stop waiting and continue processing without waiting for consistency. ReplyX to cancel the recovery process. Any other reply results in continuing the wait forconsistency.

GDDR642I

Cause Both remote C-systems are accessible from the current C-system. Action None .

GDDR643I

Cause The indicated couple dataset type is not defined for the indicated system in the GDDRparameters. Action If you do not need the GDDR Couple Dataset Management function for the indicatedcouple dataset type, no action is required.

GDDR644I


GDDR Completed script-name with rc r c at Site site-id●

GDDR Completed script-name with rc rc for System system-name●

GDDR Function Status ===> GDDR Function function(program-name)

Completed In nnnn Seconds With Return code rc

●

Completed step nn of nn in count Seconds●

GDDR Parameter broadcast completed with rc rc●

GDDR Completed function with rc rc●

GDDR Continue waiting for SRDF/A session consistency, currentcycle number = nnn, start cycle number = nnn

GDDR Currently running in degraded mode at site-id

GDDR {Primary|Alternate} couple_type CPL type not defined forsystem-name, skipping


Cause The GDDR Event Monitor has decided that GDDR Degraded mode cannot be set OFF atthis time, for the reason indicated. Action Fix the problem indicated in the reason. Possible reasons include an MHB event for a site,GDDRPARM inconsistency, a GDDR subtask not being available. The Perform HealthCheck panel lists all C-systems, and will also show the reason for degraded mode. Checkthe Consistency field, look for unplanned events, review GDDRMAIN status on the listedC-systems. If a C-system shows a Degraded GDDRMAIN state, that will cause Degradedmode. Issue the "D" (details) line command against the affected system. A pop-up willshow the active subtasks.If the problem is that one of the GDDRMAIN subtasks is not started, review theGDDRMAIN job log for error messages and address the issues reported. Try to start themissing subtasks. If this fails, contact Dell EMC Customer Support. Keep the GDDREVMand GDDRMAIN job logs available.For Star-HA and SQAR configurations, a serious problem in the MSC High Availabilitystatus will also cause Degraded mode. Check the GDDR Event Monitor job log foradditional error messages and address the issues reported in those messages. Ifnecessary, contact Dell EMC Customer S upport. Keep the GDDREVM and SCF job logsavailable from both HA sites available.

GDDR645I

Cause This message indicates that GDDR does not run in Degraded mode any longer. Action None.

GDDR646I

Cause This message informs on deactivation completion and shows the return code. Action None.

GDDR647I

Cause This message reports GDDR normal mode. Action None.

GDDR648I

Cause

GDDR Degraded mode not eligible for reset at this timeGDDR Reason: reason

GDDR Degraded mode has been set OFF

GDDR Deactivate for LPAR lpar-name completed with rc rc

GDDR Operating in normal mode

Wait for {Consistency|Synchronization}? Reply (S)top waiting andcontinue script, or (X)Cancel script


The script in execution is waiting for SRDF/A consistency or track synchronization to beachieved. This WTOR provides a method to escape the wait without having to cancel thescript. Action Do not respond to this WTOR unless you wish to stop waiting for SRDF/A consistency ortrack synchronization. The WTOR will be automatically deleted if consistency is achieved.

GDDR649E

Cause The indicated SRDF group on the indicated storage system is either offline or has nofunctioning director. That is, all directors associated with the SRDF group are either notfunctioning, offline, or disconnected. Action Investigate why the SRDF group is not functional and take action to make it functional.Any GDDR action which uses the SRDF group will fail until this condition is corrected.

GDDR650W

Cause The indicated director on the indicated storage system is not operational for the indicatedreason. Reasons could be Dead, No ports, or Offline. Action Investigate why the director is not functional and if appropriate, take action to make itfunctional. If all directors which serve an SRDF group are not functional, the SRDF groupwill be non-functional and message GDDR649E will occur. However, the SRDF group willbe functional if it has at least one functional director.

GDDR652E

Cause The C-system at the indicated site is found to have no usable gatekeeper devices for theindicated storage system, which is expected to be directly channel attached at theindicated site. The site ID of the storage system can be the same site as that of the C-system, or, in AutoSwap configurations, a different site in the same region. Action Review the RDF.DEVICES parameters and GDDRPARM SYMM parameters for usage ofappropriate gatekeeper devices. If the parameters are found to be correct, verify thestatus of the gatekeeper devices. This message can signal a loss of paths from one site toanother site in the same region in an AutoSwap configuration, or a loss of paths from a C-system to one or more storage systems at its own site.

GDDR653W

GDDR RDF Group srdfgrp on symmserial GK: gk at site-id is notfunctional

GDDR Director nn for RDF group srdfgrp on symmserial GK: gk atsite-id is not functional reason

GDDR C-System at site-id has no useable Gatekeeper devices forSymmetrix symmserial at site-id2

GDDR C-System at site-id has no useable connections to Symmetrixsymmserial at site-id2


●

●

Cause The C-system at the indicated site is found to have no usable connections to the indicatedstorage system at a different site, which is not expected to be directly channel attached. Action Review the status of SRDF groups connecting the site of the GDDR C-system to the siteof the specified storage system. If the SRDF groups are operational, refer to the actionslisted for message GDDR652E.

GDDR654I

Cause ECGUTIL has returned the indicated return code. If the return code is greater than 4, aninternal error code is generated and the script will fail. Otherwise the script step willcomplete successfully. Action If the return code is greater than 4, examine the output for ECGUTIL error messagesdescribing the problem.

GDDR655E

Cause The C-system at the indicated site was unable to update the SRDF topology map. Themost likely cause for this is that the C-system at the indicated site has no usablegatekeepers for one or more storage systems at its own site. If that is the case, there willbe additional symptoms:

The RDF event will be ON for each site pair involving the indicated site.

GDDREVM at the master C-system will set to Degraded mode because there are no

device workers started at the indicated site. Action Review GDDRMAIN startup messages at the named site for errors related to SYMMparameters and correct any reported errors. There could be IODF issues, or otherhardware issues preventing the C-system from accessing the affected storage system.See actions for GDDR652E for other possibilities.

GDDR656I

Cause GDDR has set the C-system at DC3 as the new C-system. Processing continues. Action None.

GDDR657I

GDDR ECGUTIL returned rc rc

GDDR C-System at site-id failed to update the SRDF Topology Mapfor the GDDR managed configuration

GDDR Forced dc3-c-system-name as the new master C-System


GDDR Found count devices that require special processing●

GDDR Found count Symmetrix controllers●

GDDR Found count dev_type devices for action processing●


●

Cause The indicated number of objects will be processed. This may also indicate that no devicesrequiring special processing were found. Action None.

GDDR658E

Cause This message indicates that GDDR was unable to obtain objects of the indicated type dueto a previously indicated error. The following describe the possible objects:

Storage systemsThis error is the result of a processing failure, not because GDDR parameters have beenomitted. An error code is generated and the current script fails. Action Examine previous messages to determine a possible reason for the failure to find theindicated objects. Otherwise, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR659I

Cause The GDDR SRDF group check program is reporting the gatekeeper it uses to access theindicated storage system at the indicated site.The indicated gatekeeper is either an MVS address, or an MVS address and an SRDFgroup, separated by a ".". Action None.

GDDR661I

Cause The HMC command shown has is about to be issued. Processing continues. Action None.

GDDR662I

Cause A GDDRMAIN worker is reporting either the start or end of a unit of work. The messagegives the module executed and the requesting system and job. Action

GDDR Found count DC3 Lpar parameters to process●

GDDR Found no devices requiring special processing●

GDDR Unable to retrieve found_objects_description

GDDR Using gatekeeper gk[.srdfgrp] for RDF group check onSymmetrix symmserial, at site site-id.

GDDR USS command: hmc-action

status of module-name from System system-name, Job jobname (job-id)


None. GDDR663E

Cause A script has been submitted for execution. However, the GDDR state (the event variables)is not the same as it was when the script was executed. Therefore, the generated scriptmay no longer be correct for the current environment. Action If you still need to execute the script in light of the changed environment, resubmit thescript via the ISPF panels or the script command.

GDDR664I

Cause A script has been submitted for execution. It appears that script generation should waitlong enough for another EVM cycle to occur to get a more accurate value for the currentstate. This wait is an attempt to avoid the condition reported in message GDDR663E. Thescript will wait the indicated number of seconds and continue. Action None.

GDDR665I

Cause During script rerun, systems that had already been LOADed, can be ignored. Action None.

GDDR667I

Cause A GDDR script is waiting for SRDF data synchronization to complete, and invalid trackswere found on the indicated GDDR-managed device, in the indicated SRDF group.Between parentheses, either a percentage or a gatekeeper address is shown. Thisgatekeeper address identifies the storage system. Action None.

GDDR668I

Cause The TimeFinder batch utility is about to be invoked to perform the current BCV function.Processing continues. Action

State change since script generation; script must be regenerated

Verifying configuration state in seconds seconds

GDDR Ignoring previous successful Load Clear of system-name

GDDR Invalid tracks found on device symdv# in RDF group srdfgrp({gk|nnn})

GDDR Invoking TimeFinder batch utility for group group_name


None. GDDR669I

Cause GDDR is issuing the indicated action on the indicated system. Action None.

GDDR670I

Cause The SRDF Host Component API command shown is about to be issued. Processingcontinues. Action None.

GDDR671I

Cause During a GDDR script, the listed action is performed on the devices listed in the message. Action None.

GDDR672I

Cause This message informs that GDDR has issued a request to initiate a ConGroup trip. Action None.

GDDR673I

Cause After operator confirmation, this message is issued to indicate that the LOAD_CLEARoperation is being initiated on the indicated system. The message provides the loadaddress and the load parameters. Action None.

GDDR674I

GDDR Issuing function for cpc system-name at site site-id or

GDDR Issuing function function on system system-name

GDDR Issuing command command

GDDR action - Devices symdv#s

GDDR Request to trip ConGroup has been issued

GDDR Issuing load for system system-name using load_addr /load_parm


Cause During script processing GDDR had to wait for SRDF/A consistency. This has now beenachieved. Script processing continues. Action None .

GDDR675E

Cause An HMC action was requested, but the indicated load parameters were not found for theindicated system at the indicated site. The parameter that was not found isGLOBAL.GDDR.PARMS.iplparms.system.site. The parameter must be present for theaction to occur. Action Update your parameters and try again.

GDDR677I

Cause The global variable GLOBAL.GDDR.DIAGNOSTICS.HMC_SIMULATE is set to one (1),indicating that HMC actions should be simulated instead of performed. Action None.

GDDR678I

Cause GDDR has issued a RESET CLEAR of the specified system. Action None.

GDDR679E

Cause Recovery was attempted for a lost system at $DC1 or $DC2, indicated by site-id. GDDRhas detected an AutoSwap event has begun, but has not completed, and as a result theload-address is considered inaccessible at this time.The values of $DC1 or $DC2 may contain site names assigned by the customer if the sitenames have been customized using the Define GDDR User Labels panel. Action Retry system recovery when the swap event has been completed or cleared.

GDDR SRDF/A session consistency achieved: current cycle number =nnn, start cycle number= nnn

GDDR No iplparms parms found for system-name at site site-id

GDDR HMC simulate mode: simulating hmc-action for system-name (hmc-object-id)

GDDR Issuing Reset Clear of system system-name (hmc-object-id)GDDR uss_command

GDDR Swap event incomplete after 120 seconds. Unable to IPLsystem-name at site-id at this time.


GDDR680E

Cause The BCV parameter shown (with its value also displayed) cannot be used because no pathcould be found to the storage system (represented by the combination of the gatekeeperunit address in the parameter value and the site in the parameter name) from the site atwhich the routine is running. Action Correct the BCV parameter and retry the failing operation.

GDDR684I

Cause The indicated cleanup utility returned the indicated return code for the indicated MSCgroup and gatekeeper. An error code is generated and the script terminatesunsuccessfully. Action Examine additional output messages to determine the cause of the problem. When youhave corrected the problem, submit the script job again.

GDDR685I

Cause During an attempt to transfer the master C-system to another site, it was discovered thatthe master C-system was already running at that site. Action None.

GDDR687I

Cause The indicated utility gave a non-zero return code. GDDR overrides this return code, andthe script step will have RC=0. Action None.

GDDR688I

Cause A GDDR script includes a step to manage BCV devices at a certain site, using gatekeepersdetermined by the indicated swap group. However, the GDDR parameters do not defineBCV devices for that site and swap group combination. Action Determine the requirement for BCV management at the affected site in the current script.

No path found for BCV parm site-id, value gk

GDDR {M6|M9} returned rc rc for group mscgrp on gatekeeper gk

GDDR New master location site-id already running master function

GDDR overriding rc rc from utility-name. Case processingsuccessful.

GDDR No BCV definitions for swap group swapgrp are defined


If BCV management is required, perform a PARTIAL parameter activation withEVENT(NOUPDATE) and CLEARQ(NO) adding BCV definitions for that site and indicatedswap group. Then rerun the script. If BCV management is not required, simply skip thefailing step on the script rerun.To prevent this issue from re-occurring, either change call overrides (14, 18, 19, or 20) soGDDR does not attempt to manage BCVs at this site, or define BCV devices in the GDDRparameters as required.

GDDR689I

Cause Displays the gatekeeper and MSC group name being used for the ME utility. Action None.

GDDR690I

Cause The states monitored by the GDDR event monitor have not changed during its mostrecent cycle. The current state-value is shown as a 21-byte string, representing thefollowing event values: cax, sra, ncx, eca, rdr, cgd, cgt, c>b, str, msf_DC1, msf_DC2,msf_DC3, mhb_DC1, mhb_DC2, mhb_DC3, mxs_DC1, mxs_DC2, mxs_DC3, mim_DC1,mim_DC2, mim_DC3 Action None.

GDDR691I

Cause A RESET CLEAR of all non-C DC3 systems was requested. Action None .

GDDR692I

Cause GDDR has determined that special processing is required for the indicated device, and isabout to perform REFRESH followed by RFR-RSUM for the device. The SRDF group andgatekeeper that will be specified in the commands are given. Processing continues. Action None.

GDDR693I

Running SCFRDFME with Gatekeeper Device: gk MSC Group: mscgrp

GDDR No state change state_value (nnnnnnnnnnnnnnnnnnnnn) sincelast cycle

GDDR Now processing for LPAR {lpar-name|system-name}

GDDR Processing symm device symdv# in RDF group srdfgrp usinggatekeeper gk

GDDR Now processing system message from system-name


Cause GDDR is currently processing a system message from the indicated system. Action None.

GDDR694I

Cause An RDR event has occurred in the primary region and operator response to messageGDDO018A has indicated that RDR recovery should proceed in the secondary region. Action None.

GDDR695I

Cause The GDDR Event Monitor sets the GDDR state at the named site siteid to the valueshown. See GDDR690I for an explanation of state-value. Action None.

GDDR696E

Cause A GDDR action to be taken as part of script processing required operator confirmation,and a WTOR was issued to allow the operator to confirm the action. However, thereceived reply failed to confirm the action. An internal error code is generated and thescript is unsuccessful. Action If the reply was made in error, restart the script and ensure that the action is confirmedfor the rerun. If the WTOR timed out because no reply was received within the WTOR waitinterval, restart the script and ensure that the action is confirmed within the time allowed,defined by the current value of GDDR parameter WTOR Wait Time.

GDDR696I

Cause The message records the reply the operator entered in response to a WTOR from GDDR.The reply is such that operations will continue. Action None.

GDDR697I

GDDR Confirmation received for recovery in the{secondary|tertiary} region after RDR event

GDDR Setting state at site-id to state-value

GDDR Operator replied oper_reply for action, operation cancelled

GDDR Operator replied reply_text continuing

GDDR Overriding {M6|M9|ME} return code because MSC_GROUP_NAME notfound


Cause TimeFinder/Mirror, EMCTF, has returned return code 4. This represents a non-seriouscondition; the return code is converted to zero. Processing continues.This message appears in test mode only. Action None.

GDDR697W

Cause ECGUTIL has returned return code 4. This represents a non-serious condition; the returncode is converted to zero. Processing continues. Action None.

GDDR698I

Cause An RDR event for the primary region has been confirmed by operator response to messageGDDO016A. RDR processing continues. Action None

GDDR700E

Cause An BCV restore was attempted, but is not currently allowed for the listed site. Action Refer to message GDDR701E for recommended actions.

GDDR700W

Cause GDDRAUTH encountered a failure when utilizing the TSO Service Facility or a GDDRprogram that is authorized using the TSF. Action Ensure that your IKJTSO00 member has been updated correctly. The GDDR ProductGuide for your configuration provides instructions for doing this. If this does not resolvethe problem, contact Dell EMC Customer Support.

GDDR701E

Cause This message explains why a BCV Restore is not allowed.GDDR requires certain validations of the configuration to take place before it allows thecontent of GDDR-managed SRDF devices to be overwritten by a BCV Restore.

GDDR ECGUTIL return code overridden

GDDR Loss of primary region (RDR event) has been confirmed

GDDR BCV Restore at site-id not allowed

TSF FAILURE R15: r15 RC rc RSN: rs ABND: abend-code

GDDR Validation of object failed or was not done


●

●

●

●

●

●

The GDDRPBCR script performs the following validations before it invokes the GDDR BCVmanagement module, and message GDDR701E will list one or more of these, as shownbelow:

Local SRDF devices A BCV Restore is only allowed if there are reasons to suspect that the SRDF devicesare not useable for a business restart at a DR site.GDDR therefore requires that:

Devices at the local site are R2

Devices at the local site have local invalid tracks, or a Resynch-in-progress

indicator is active for the local site.

BCV local invalid tracksIf GDDR finds local invalid tracks on the BCV devices at the local site, a BCV Restorecannot be allowed.

STD-BCV pair states GDDR requires all BCV devices at the local site to be in a SPLIT state.

BCV set completeness GDDR requires that ALL GDDR-managed SRDF devices at the local site have anassociated BCV device.

Action A BCV Restore should only be done using the GDDRPBCR script.

GDDR702E

Cause An error occurred in a script that must be corrected before proceeding Action Do not rerun the script. Contact Dell EMC Customer Support.

GDDR703I

Cause The rerun control process has determined that the current script was previously startedand should be restarted from the beginning. Action None

GDDR704I

Cause A previous run of the script included a successful execution of this step, whichconsequently need not be repeated. Action None.

GDDR705I

GDDR error

GDDR Rerun state checker forcing restart of script_processor

GDDR Rerun state checker allowing bypass of script_step, lastreturn code was script_step_return_code

GDDR Rerun state checker has initialized run_variable_name


Cause The specified run variable has been initialized at the start of processing of a script or ascript step. The value assigned will cause rerun of the specified script step, or allow rerunof the script, should the script or script step be interrupted before successful completion.Processing continues. Action None.

GDDR706I

Cause The step failed on the previous run of the script and will need to be attempted again. Action None.

GDDR707I

Cause This message indicates the list of managed system names defined to GDDR for theindicated site. This includes all systems listed on the Define Managed systems wizardpanel, except HMC Only systems. Processing continues. Action None.

GDDR709E

Cause A script was selected for execution, but cannot run for the reason given. Action None.

GDDR709I

Cause This message informs that the planned action script can run only when GDDR operates innormal mode. Action None.

GDDR710I

GDDR Rerun state checker forcing rerun of script_step, last returncode was script_step_return_code

GDDR No Production Systems defined at site site-id GDDR Returning system list list_of_system_names for site site-id

GDDR Current planned script cannot run in degraded modeor

GDDR Current planned script cannot run while script script-name isrunning

GDDR Running of planned script permitted in normal mode

GDDR Reset Clear for LPAR lpar-name-system-name completed RC=rc


Cause A GDDR HMC request to perform on LPAR RESET CLEAR completed. Action None.

GDDR711I

Cause The current script has invoked a step to wait for SRDF/A session consistency. Thisrequires keeping track of the SRDF/A cycle number that is consequently saved tocompare with the subsequent cycle number values . Action None .

GDDR712I

Cause A GDDR script step took no actions on BCV devices, for the reason indicated.Example: Some script steps are aimed exclusively at TEST-set BCV devices, with noallowance to switch to GOLD-set BCV devices. If the configuration has globally disabledusage of TEST-set BCVs, this message will be issued. Action Examine the listed reason. If BCV action is required at this point in the script, address thelisted item.

GDDR713I

Cause GDDR has determined that the previous execution of the user exit resulted in a non-zeroreturn code, and therefore the exit should be called again. Action None.

GDDR715I

Cause The indicated command is about to be issued through HMC on the indicated system. Action None.

GDDR717I

Cause The transfer of the master C-system is being initiated for the indicated reason.

GDDR Saved current cycle number=nnn

GDDR Performed no BCV management. Reason: reason

GDDR Invoking exit exit_name last return code was rc

GDDR Sending command command to system system-name

GDDR Initiating master C-System transfer from site-id reasonreason


Action None.

GDDR718I

Cause As part of a site swap operation, an updated SRDF Host Component parameter member isbeing copied. The source and target members are indicated. Action None.

GDDR719I

Cause While determining whether SRDF/A special processing is required, invalid tracks weredetected on a locally mirrored R1 device with TNR status. The invalid track percentage isgiven. GDDR will schedule special processing for the device. Processing continues. Action None.

GDDR721I

Cause GDDR is initiating an action as indicated. Action None.

GDDR722I

GDDR Source member member copied into target member member

GDDR Special processing required for device symdv#, foundwith status status (nn)


GDDR Starting function function●

GDDR Starting function at Site site-id●

GDDR Starting function for System system-name●

GDDR Starting function to action commands●

GDDR Starting function for Site site-id●

GDDR Starting function with command action●

GDDR Starting function with sites site-id1 and site-id2●

GDDR Starting function on secondary C-System c-system-name●

GDDR Starting function for command action with CPC cpc-name at

Site site-id

●

GDDR Starting function for command action at Site site-id●

GDDR Starting function for command action at System system-

name

●

GDDR Starting function for command action at Lpar lpar-name●

GDDR Starting function action for {site-id|system} excluding

C-System c-system-name

●


Cause The GDDR state changed as indicated. Action None

GDDR724I

Cause HMC Discovery is connecting to site-id using the specified HMC method, BCPII orHWMCAAPI, to return site information. Action None.

GDDR725I

Cause HMC log scanner (GDDRC009) should be terminated . Action None .

GDDR727I

Cause While performing the Couple Dataset Management function, GDDR found that theindicated system is using the Primary or Alternate couple dataset indicated in themessage. The dataset is in agreement with values supplied by the Define Managed CoupleDatasets panel for this system, so the Couple Dataset Management function does need torealign this couple dataset. Action None.

GDDR727W

Cause The used couple datasets are not as expected by GDDR. GDDR will switch to the correctdatasets. Action None.

GDDR728E

Cause

GDDR State changed from GDDR_state1 to GDDR_state2

GDDR HMC Communication with site-id using {BCPII | HWMCAAPI}

GDDR Posting scanner with Stop command

GDDR System system-name found using correct {A|P}-Couple dsname

GDDR System system-name found using incorrect {A|P}-Couple couple_dataset

GDDR WTOR timed out after wtor_wait_time waiting for operatorreply


No reply to a WTOR issued by GDDR was received within the wait time interval indicated.No action is taken and an internal error code is generated. Action None.

GDDR729I

Cause The call to TimeFinder/Mirror specified in preceding message GDDR668I has ended withthe indicated return code. If the return code is not zero, an internal error code isgenerated and the script is unsuccessful. Otherwise, processing continues. Action If the return code is zero, none. Otherwise, examine the SYSOUT output file for messagesthat indicate the problem. Take appropriate steps to correct the problem and restart thescript.

GDDR730I

Cause Transfer of the master C-system function must be accompanied by transfer of AutoSwapownership in order to allow AutoSwap-related commands to succeed in subsequent scriptprocessing. This message indicates that GDDR is issuing a command to transfer AutoSwapownership to the new master C-system whose name, SMF ID, and site are indicated. Action None.

GDDR731I

Cause The indicated system has been changed to use the indicated (A or P) couple datasets asalternates. Action None.

GDDR732E

Cause Internal error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR734I

GDDR TimeFinder batch utility for group group_name ended, rc = rc

GDDR Transferring AutoSwap ownership to c-system-name (smf-id) atsite site-id

GDDR System system-name using {A|P}-Couple couple_dataset asalternate

GDDR Unrecognized parameter passed action_parameter


Cause Informational summary message indicating that GDDR found the couple datasets of theindicated type, to be in line with the values supplied by the Define Managed CoupleDatasets panel for the named system. Action None.

GDDR735I

Cause GDDR is beginning to propagate the GDDR-defined set of parameters that must match onall C-systems in order for GDDR to function correctly from the master C-system to theindicated remote C-system. Action None.

GDDR736I

Cause This message reports successful alignment of the couple datasets on the indicatedsystem. Action None.

GDDR737I

Cause An SRDF Host Component API function is being invoked as described in a separatemessage. This message indicates the gatekeeper address and the PowerMax/VMAXdevice range being used. (The device range is converted to a pair consisting of a startingdevice number and a device count for the API call.) Processing continues. Action None.

GDDR738I

Cause GDDR is using the indicated group name for the indicated utility. Action None.

GDDR739I

GDDR couple_type Couple Datasets were already aligned on systemsystem-name

GDDR Updating GDDR broadcast set on system remote-c-system-name

GDDR Successfully aligned couple_type Couple Datasets on systemsystem-name

GDDR Using gatekeeper gk RDFGRP srdfgrp for API callor

GDDR Using gatekeeper gk for range dev_range on API call

GDDR Using MSC group name mscgrp for {M6|M9|ME} utility


Cause The indicated action has taken place on the indicated remote system. Action None.

GDDR740I

Cause The indicated gatekeeper device is being used for the indicated utility. Action None.

GDDR741I

Cause GDDR is unable to communicate with the indicated site. Action None.

GDDR742I

Cause A script is waiting for SRDF/A session consistency and has just completed a checkindicating that consistency has not yet been achieved. An additional wait is about to beperformed. Action None.

GDDR743I

Cause While performing the Couple Dataset Management function, GDDR has issued PSWITCHand/or ACOUPLE commands, and verified that couple datasets of the indicated type havebeen switched in agreement with the values supplied by the Define Managed CoupleDatasets panel for the indicated system. Action None.

GDDR749I

GDDR variable_name set to value at remote-c-system-nameor

GDDR Heartbeat for site-id set to value at remote-c-system-nameor

GDDR Set variable_description at remote-c-system-name

GDDR Using gatekeeper address gk for {M6|M9|ME} utility

GDDR Waited for count seconds for all systems at site site-id tobecome active, skipping

GDDR Waiting for wait_time seconds before next check

GDDR Successfully verified realignment of couple_type CoupleDatasets on system system-name


Cause GDDR will perform the indicated operation on the indicated LPAR. Action None.

GDDR750I

Cause While performing the Couple Dataset Management function, GDDR found that theindicated system is using the Alternate couple dataset indicated in the message. Thedataset, of the datasets supplied by the Define Managed Couple Datasets panel for thissystem, is specified to be the Primary couple dataset. GDDR switches to the correct couple dataset. Action None.

GDDR751I

Cause The information given in the message (IP address or community name) is being used forhardware management console access. Action None.

GDDR752I

Cause This information message shows the HMC Optional parameters used by GDDR. Thisincludes the Community name, the HMC Timeout value and the Debug setting to be usedby the GDDR program communicating to the HMC. Action None.

GDDR753I

Cause This message shows the time, in seconds, that the GDDR script will wait for the HMC

GDDR Issuing {Reset Clear|Deactivate} for LPAR lpar-name-system-name

GDDR System system-name found using P-couple dsname as alternate


GDDR Will use HMC IP address hmc_ip_address●

GDDR Will use HMC community hmc_community●

GDDR Will use HMC community value from current system

hmc_community

●

GDDR Will use HMC community hmc_community for System system-

name

●

GDDR will use HMC optional parms parameter_list

GDDR will use USSCMD timeout value nn


interface program to return. Action None.

GDDR754E

Cause The GDDR Couple Dataset Management or the Coupling Facility Structure managementfunction was invoked for the indicated system, but GDDR found no Site and Systementries for this system. The Couple Dataset Management function terminates for thissystem. Action Correct the GDDR parameters. Either remove Site and System entries in the DefineManaged Systems panel for this system or add a SITE.system-name parameter.

GDDR754I

Cause A TimeFinder/Mirror BCV operation will not take place because no BCVs were specifiedfor the indicated swap group. Processing continues. Action None .

GDDR755E

Cause An error has occurred which appears to be a GDDR program error. The error identifier canbe utilized by Dell EMC Customer Support to diagnose and resolve the error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR756E

Cause The GDDR Couple Dataset Management or the Coupling Facility Structure managementfunction was invoked for the indicated site, but GDDR found no entry in the DefineManaged HMCs panel for this site. The function terminates. Action Correct the GDDR parameters. Either remove the entry from the Define Managed CoupleDatasets panel or the Define Managed CF Structures panel for this site or add an entry forthe site in the Define Managed HMCs panel and re-load the parameter set.

GDDR757W

GDDR Site not defined for system system-name

GDDR bcv_action found no GDDRPARM for swap group swapgrp

GDDR function_name trapped an error. RC=rc in line nn : nn

GDDR HMC IP address not defined for site site-id


●

●

●

●

●

●

●

●

●

●

●

Cause While determining whether SRDF/A special processing is required, invalid tracks weredetected on a locally mirrored R1 device. GDDR will now check whether the R1 devices isin TNR status, and if so will issue message GDDR719I and schedule special processing forthe device. Processing continues. Action None.

GDDR759W

Cause A preceding command completed with rc=04 (warning). Where command can be any ofthe following:

ADCOPY

HDELETEPAIR

RDF-RSUM

RDFSUSP

READONLY

READWRITE

READY

RNG-REFRESH

RNG-RSUM

SQ VOL

SYNCDIR

Action None.

GDDR768W

Cause A device has invalid tracks. The message identifies the device, the SRDF group (or local),and the number of invalid tracks. These message occur while script processing is waitingfor invalid tracks to synch up. The second and third forms indicate this type of activity andthe number of invalid tracks should decline as this message is reissued. The first form ofthe message indicates that the device is in adaptive copy mode and therefore the invalidtracks will not synch up. Action

GDDR Warning: devicesymdv# R1:r1_invalid_tracks R2:r2_invalid_tracks invalids (nn%)

GDDR Warning: Return code override on command

This rc=04 condition is considered nonfatal and is being reset to rc=0.

Format 1:

GDDR Device symdv# (RDFGRP srdfgrp) has count R2 invalids andADCOPY Disk mode, leavingFormat 2:

GDDR Device symdv# (RDFGRP srdfgrp) has count R2 invalids,retryingFormat 3:

GDDR Device symdv# has count local invalids retrying


For the second and third forms of the message, no action is required unless the number ofinvalid tracks is not decreasing over time. For the first form of the message, determinewhy the device is in adaptive copy mode, make corrections and retry.

GDDR769W

Cause While attempting to propagate one or more GDDR parameters to a remote C-system, theGDDR C-system communication manager has failed to detect a response from theindicated remote C-system. Processing continues, but one or more GDDR parameters maybe unsynchronized across the GDDR C-systems. Action Check to see that the indicated remote C-system is up and that it has communication withother C-systems.

GDDR770W

Cause A system is in the exclude list, couple dataset and CF Structure processing for this systemis unnecessary. Action None.

GDDR771W

Cause The GDDR event monitor has transferred the master C-system function to the referencedsite because a regional disaster has occurred. Action None.

GDDR772I

Cause GDDR has confirmed that communication to the indicated system is active. Action None.

GDDR773W

Cause The Coupling Facility structure management function was invoked for the named site.GDDR found Coupling Facility names defined for the indicated system, however thissystem is not defined at the indicated site. GDDR skips CF Structure management for this

GDDR Bypassing system-name as not really alive

GDDR GDDR System system-name in exclude list, skipping [Coupledataset] [CF Structure] processing

GDDR Forced site-id C-System system-name as master. Reason: RDR

GDDR communication to system-name is active

GDDR System system-name not defined for site site-id , skipping CFStructure processing


●

●

system. Action Correct the GDDR parameters. Either define the indicated system using Site and Systementries in the Define Managed LPARs panel, or remove the Coupling Facility names for thissystem from the Define Managed CF Structures panel.

GDDR774W

Cause Communication is not available. GDDR will try again. Action None.

GDDR775W

Cause An error has occurred while attempting to access a remote system. Action Determine the connection status of the remote system to the system on which thismessage appeared. Ensure that the remote system connection status is active, thatremote commands are authorized, and that a command was not rejected due to lack ofauthorization.

GDDR776E

Cause A request to transfer the master C-system function to a new site was received. However,the site does not appear to be available: either the GDDRMAIN MSTAT communicationtest indicated that the proposed site could not be contacted or the Missing Heartbeatindicator is on for the desired site. The request is rejected. If the master C-systemfunction transfer request was issued by a script, the script will end with an error.reason-description can be one of the following:

MHB - Missing Heartbeat indicator is on

MSTAT - Failed GDDRMAIN MSTAT test Action Determine why the C-system to which the master C-system function is to be transferredis unavailable. If the reason shown in the message is MHB, it may be that the GDDR Heartbeat Monitor has not yet cleared the missing heartbeat indicator even though thesystem is available. When the problem is resolved, restart the script.

GDDR776I

Cause A request to transfer the master C-system function to a new site was received. Thevalidation routine indicates that the C-system at the target site is available. Processingcontinues.

GDDR communication to system system-name unavailable, bypassing

GDDR No command output returned from system-name

GDDR Proposed new owning site site-id is dead reason, owner cannotbe changed

GDDR Proposed new owning site site-id alive


●

●

●

●

Action None.

GDDR777W

Cause While preparing for the indicated sysplex management function, GDDR found coupledatasets or Coupling Facility Names for the indicated system, but this system is a C-system. The function continues, but skips processing for this system. Action Correct the GDDR parameters.

GDDR778W

Cause The indicated sysplex management function was invoked for the indicated system,however the Bypass HMC field on Define Managed LPARs panel indicates HMC actionsare to be bypassed for associated LPAR name. Action Depending on your requirements, adjust the GDDR parameters, or do nothing.

GDDR779I

Cause GDDR is finished with the Message Scanner and it is stopping it. Action None.

GDDR786E

Cause This message is issued by the GDDR Event Monitor each time a GDDR event changesstate (OFF to ON, or ON to OFF).For the MSC-HA event, the following possible state descriptions apply:

UNKNOWN: The GDDR Event Monitor is unable to determine HA status. Contact Dell

EMC Customer Support and keep the GDDREVM joblog available.

AVAILABLE: A primary MSC server is running on a GDDR C-system, and a secondary

MSC server on another GDDR C-system is either active or has at least a correct

MSC group definition, so that it can be started and perform a takeover, should the

primary MSC server fail.

UNAVAILABLE: MSC High Availability is currently not available. It is recommended to

execute script GDDRPA36 to start a secondary MSC server on a GDDR C-system.

TRIGGERED: An active secondary MSC server has detected a TakeOver Threshold

GDDR System system-name is a C-System, skipping [Coupledataset][CF Structure] processing

GDDR System system-name , LPAR lpar-name is in HMC Bypass list forSite site-id , skipping [CF Structure][Couple Dataset] processing

GDDR stopping message_scanner at Site site

GDDR event Event State Changed old_state to new_state


●

●

Exceeded condition. The GDDR Event Manager analyzes the situation and takes one

of two actions:

Submits the GDDRUP35 script to have the secondary MSC server take over as

primary (if the analysis confirms that the primary MSC server is down), or

Issues the MSC,TKRESET command to bring the secondary MSC server out of

the Threshold Exceeded condition (if the analysis shows that the primary MSC

server is still active). In this case, a new GDDR786E message is issued signaling

that the MSC-HA event changed from TRIGGERED to AVAILABLE. Also, the

MSC Takeover counter is reset to 0, and starts incrementing again with each

MSC cycle that the secondary MSC server performs an MSC cycle switch.GDDR ships with a message rule to intercept the GDDR786E message and forward it to allmanaged systems where GDDRMAIN is running, thus enabling GDDR event notification onmanaged systems. By default, this message rule is enabled. To disable this message rule,you can add an MSG parameter in the GDDRPARM file. For more information about howto customize GDDR message interception, see the GDDR Product Guide for yourconfiguration. Action Review the GDDR Product Guide for your configuration for information about the reportedevent. If the event is unexpected, take appropriate action to have the event cleared, forexample, by running the appropriate GDDR script.

GDDR793W

Cause GDDR has found that MSC is currently disabled. The MSC option has been forced toDEACTREFRESH. Processing continues. Action None.

GDDR800E

Cause GDDRDAP3 received an invalid parameter list. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDR801E

Cause GDDRDAP3 received an invalid parameter list. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center for

GDDR MSC disabled, Start command modified to DEACTREFRESH

GDDR Invalid parameter length parameter_length

GDDR Invalid parameter format


assistance. Make sure you have all relevant job documentation available. GDDR802E

Cause GDDRDAP4 did not receive an SRDF Host Component prefix. Ensure that you havespecified the SRDF Host Component prefix. The current SRDF Host Component prefixcan be viewed on the Script JCL Parameters panel. It can also be specified with theCOMMAND_PREFIX parameter in the SRDF Host Component parameter dataset, which isspecified in the Define Dell EMC Mainframe Enabler STCs panel. Action Specify an SRDF Host Component prefix using one of the methods described above. Ifthe problem persists, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR803I

Cause This message shows the SRDF Host Component prefix used. Action None.

GDDR804E

Cause This message is issued by GDDRDAP4 when SRDF Host Component has issued anunexpected RDDF error, SRDF_DRDFRTN_MESSAGE. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR805E

Cause This message is issued by GDDRDAP4 when SRDF Host Component has issued anunexpected RDDF error, SRDF_DRDFRTN_MESSAGE. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.

GDDR809I

No command prefix passed

Using command prefix host_component_prefix

(rc) Reason=rs

(rc) EMCSRDF_DRDFRS=rs

GDDR MAXCMDS Updated, New value new_value(old_value)


●

●

●

●

●

Cause This message lists the new maximum commands supported. Action None.

GDDR815I

Cause Either an MSC,REFRESH or MSC,DEACTREFRESH command was requested, but GDDRfound the MSC Environment to be DISABLED. GDDR issues an MSC,ENABLE commandinstead. Or an MSC,DEACTREFRESH command was issued but GDDR found the indicatedgroup to be in an inactive state. GDDR issues an MSC,REFRESH command instead. Action None.

GDDR816I

Cause An MSC command was requested for the group identified in the message, but GDDRfound the group to be in a transitional state at the time of the request. GDDR waits up to 5minutes for the group to get into a known state. If the group gets into a known state,GDDR will proceed with the command. If not, the current process ends with RC=4. Action None.

GDDR817I

Cause The MSC command identified in the message was requested, but GDDR found theindicated MSC group already in the desired state. GDDR issues no command. Action None.

GDDR818I

Cause This message shows detailed information about the current state of the indicated MSCgroup is displayed.The message consists of a series of blank separated words, with the following meanings:

Word 1: MSC environment state, shown as one of:

DISABLED - MSC environment does not exist

ENABLED - MSC environment exists but no groups defined

MULTI - > 1 group defined to MSC

SINGLE - 1 group is defined to MSCApplies to all configurations.

command command replaced with new-command for group mscgrp

Waiting up to 5 minutes for initial state for group mscgrp

Desired MSC state detected for command command. No action requiredfor group mscgrp

MSC State for mscgroup: mscstate


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

Word 2: MSC group state, shown as one of:

???? - none of the below apply

ACTIVE - group is MSC active and cycling SRDF/A

CLEANUP - SRDF/A drop occurred, MSC cleanup running

CLNERR - An error occurred during cleanup processing

DEACTIP - MSC,DEACT command in progress

DEACT - MSC,DEACT command has completed

DISABLED - DISABLE command has completed

DISIP - DISABLE in progress

DROPPED - SRDF/A drop occurred, MSC cleanup complete

INITIAL - group has been defined but not activated

NOTFOUND - group is not defined to MSC

PDROPIP - MSC,PENDDROP command in progress

PENDDROP - MSC,PENDDROP command completed

SWITCHED - MSC,SWITCH command completed

SWITCHIP - MSC,SWITCH command in progress

TIMEOUT - DISABLE processing had a timeoutApplies to all configurations.

Word 3: MSC server role, shown as one of:

???? - None of the below apply

ERROR - WF=0 but no Primary SMFID, or WF=2 but Primary SMFID =local

SMFID

NOTFOUND - group is not defined to MSC

ORPHAN - ACTIVE/PENDDROP Secondary. Primary unknown

PRIMARY - Primary MSC Server

SECONDARY - Secondary MSC Server

SECONDARY_TO - Secondary has observed Primary failure (ready for unplanned

TakeOver)Applies to HA configurations.

Word 4: SMFID, shown as one of:

???? - Primary MSC server SMFID unknown

ssss - SMFID of the Primary MSC serverApplies to HA configurations.

Word 5: MSC mode, shown as one of:

???? - group is not defined to MSC

MSC - group is running in MSC mode

SQARA - group is running as SQAR A-C leg

SQARB - group is running as SQAR B-D leg

STAR - group is running in Star mode

STAR1 - group is running as Star-A A-C leg

STAR2 - group is running as Star-A A-D leg

STARFIRE - group is running in Star with AutoSwap modeto all configurations.

Word 6: Star topology, shown as one of:


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

???? - group is not STAR and not STARFIRE

CASCADED - Cascaded data flow

CONCURRENT - Concurrent data flowApplies to Star configurations.

Word 7: MSC initialization status, shown as one of:

???? - group is not defined to MSC

CG_DISABLED - Cycle Tag F

FC01 - All boxes Ready

FC02 - All boxes Recorded

FC03 - All boxes Active

INIT_ERROR - Initialization error occurred

MSC_CONSISTENT - Cycle Tag C

NOT_STARTED - group is inactive

RECOVERY_AVAILABLE - Cycle Tag E

VAL_ERROR - Validation error occurred

VAL_IP - Validation is in progressApplies during MSC Initialization.

Word 8: ConGroup name, shown as one of:

???? - group is not STAR, STARFIRE, or SQAR

gggggggg - ConGroup name associated with this MSCGROUPApplies to STAR and SQAR configurations

Word 9: MSC-CG listeners state, shown as one of:

NNN - not STAR, STARFIRE, or SQAR or no listeners registered

Y.. - CG Connect listener registered

.Y. - CG Stop listener registered

..Y - CG State listener registeredApplies to STAR and SQAR configurations

Word 10: MSC Takeover command status, shown as one of:

NOT_STARTED - No Takeover command was issued

ERROR - An error occurred during Takeover

COMPLETE - Takeover command complete

STARTED - A Takeover command was issuedApplies to HA configurations.

Word 11: MSC Takeover progress, shown as one of:

???? - Takeover not started

Y........ - Group Active Flag

.Y....... - Group MSC Active flag

..Y...... - Session Active flag

...Y..... - STAR / SQAR mode active

....Y.... - STARFIRE / SQAR active

.....Y... - CG Connect listener registered

......Y.. - CG Stop listener registered

.......Y. - CG State listener registered

........T - Cycle Tag (first byte)Applies to HA configurations.


●

●

●

●

●

●

●

●

●

●

Word 12: SQAR partner msc group name, shown as one of:

???? - group is not SQAR

gggggggg - name of the other msc group in a SQAR configurationApplies to SQAR configurations.

Word 13: frozen (Secondary Frozen/THAW processing):

???? - none of the below apply

THAWERR - THAW command had an error

THAWED - THAW command completed OK

THAWIP - THAW command accepted

THAWCMD - THAW command issued

FROZEN - Secondary MSC server detected frozen sessionsApplies to SQAR configurations.

Action None.

GDDR822I

Cause An error was trapped while processing a request to propagate a value for a single GDDRparameter to a remote C-system. Message GDDR755E was issued previously describingthe error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR823I

Cause An error was trapped while processing a request to propagate a value for a single GDDRparameter to a remote C-system. Message GDDR755E was issued previously describingthe error. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance.

GDDR831I

Cause A master C-system transfer function has completed successfully. The reason for thetransfer can be determined from previously issued messages. Action Determine the condition that caused the C-system transfer. If a site or a C-system has

GDDR Parameter name: parameter_name

GDDR Parameter value: parameter_value

GDDR Master function has been transferred from system-name1 tosystem-name2


failed, take appropriate recovery steps. GDDR832W

Cause The master C-system transfer processor has determined that it is inappropriate totransfer the parameters to the new master C-system because that system was alreadyrunning as a master C-system. This situation can occur if the system from which themaster function is being transferred lost the path to the master C-system and declareditself the master C-system. Action None.

GDDR833W

Cause An action has been initiated through the Hardware Management Console. GDDR nowwaits the indicated interval for the action to complete. Action See subsequent messages for the result of the action.

GDDR837E

Cause During a ConGroup Takeover, the current ConGroup owner could not be determined. Action You may be running a level of Mainframe Enablers which does not support retrieving theConGroup owner. If so, the action cannot be done. If not, contact the Dell EMC CustomerSupport Center for assistance.

GDDR838I

Cause The SMF ID of the current ConGroup owner is displayed. Action None.

GDDR839I

Cause GDDR is about to begin waiting for the indicated ConGroup or MSC action to complete.The ConGroup or MSC name may or may not be displayed, depending on the action. Action None.

GDDR840E

GDDR has skipped propagate of the parameter list

GDDR About to wait count seconds for system hmc-action to complete

Unable to determine ConGroup Owner SMFID

Current ConGroup Owner: smfid

GDDR Waiting for {ConGroup cngrp|MSC group mscgrp} action


Cause The indicated ConGroup or MSC (as indicated) action failed. Action Consult the indicated job log to determine the reason for the failure. Correct the problemand retry the operation.

GDDR841E

Cause GDDR has timed out waiting for the indicated action by either ConGroup or MSC tocomplete. The ConGroup or MSC name may or may not be displayed depending on theaction. Action Consult the ConGroup or SCF logs to determine the reason for the timeout. Correct theproblem and retry the operation.

GDDR842I

Cause The current state of the indicated MSC group is displayed. Action None.

GDDR843I

Cause The action is skipped because the script is being rerun and the local MSC server is alreadynot the primary server. Action None.

GDDR844E

Cause The system should be the primary MSC server or in a DEACT state, but it is not. Action Investigate the current state of the system in the MSC server role (previously displayedwith GDDR842I) and correct it.

GDDR845E

Cause

{ConGroup|MSC} action failed. See jobname joblog.

Timeout waiting for {ConGroup cngrp|MSC group mscgrp} action

MSC State for mscgrp: state

DEACT,RETAIN skipped on rerun. system-name is not the Primary MSCServer

system-name is not the Primary MSC Server and not in a DEACTstatus

Unexpected MSC State for mscgrp: state


The indicated MSC group is in an unexpected state. The state is displayed. Action Investigate the current state of the MSC group and correct it. Then retry the operation.

GDDR846E

Cause The primary or secondary (as indicated) MSC server on the indicated system is notdefined in Star mode or not defined with a ConGroup with AutoSwap eXtension(STAR_CAX). STAR_CAX mode is required for STAR-HA. Action Investigate the current state of the MSC group and correct it. Then retry the operation.

GDDR847E

Cause The primary or secondary (as indicated) MSC server on the indicated system is definedwith a different ConGroup name than the one defined in GDDR parameters. Action Investigate the current state of the MSC group and correct it or correct the GDDRConGroup. Then retry the operation.

GDDR848E

Cause SRDF/A is not active in the indicated MSC group. Action Investigate the current state of the MSC group and correct it. Then retry the operation.

GDDR849E

Cause The current role of the MSC server is not compatible with the requested action (plannedor unplanned). The requested action cannot be performed. Action -

GDDR850I

Cause The event monitor has detected an unplanned swap in progress. It does not take actionuntil the swap is complete. Action None.

{Primary|Secondary} MSC Server (system-name) not in STAR_CAX mode

{Primary|Secondary} MSC Server (system-name) ConGroup (cngrp) isnot the GDDR ConGroup (gddr-cngrp)

SRDF/A drop in MSC group mscgrp

Invalid role (PRIMARY|SECONDARY) for {planned|unplanned} action

GDDR CAX event in progress, waiting for unplanned swap


GDDR852I

Cause The event monitor has detected that the current secondary site is dead, which indicates alocal disaster (LDR) has occurred. Action Investigate the cause of the outage at the secondary site.

GDDR853I

Cause The event monitor at the primary site has detected a local disaster (LDR), which indicatesthat recovery at the secondary site is no longer available. Action Investigate the cause of the outage at the primary site.

GDDR854I

Cause The event monitor at a site other than the primary site has detected a local disaster(LDR), which indicates that recovery at the secondary site is no longer available. Action Investigate the cause of the outage at the referenced site.

GDDR855I

Cause An RDR event (regional disaster) has been detected. If this message occurs in the primaryregion, then the secondary region has suffered the disaster; if this message occurs in thesecondary region, then the primary region has suffered the disaster and further messagesand action should be expected to deal with the situation. Action If action is needed, further messages will occur.

GDDR856E

Cause A Star-HA (High Availability) takeover is attempted while the takeover threshold is notexceeded. This could indicate that the primary MSC server is still active. If this happens inthe planned Star-HA takeover script, GDDR tries to ensure that the primary MSC server iseither not available or is in a DEACT state. During this verification, GDDRMAIN was foundnot running at the indicated site. Action

GDDR Loss of primary site site-id (LDR event) has been detected

GDDR Loss of primary DASD site site-id (LDR event) has beendetected

GDDR Loss of site site-id (LDR event) has been detected

GDDR Event Monitor has detected an RDR event

Unable to determine Primary MSC Server state at site-id (GDDRMAINnot running)


Planned Star-HA takeover requires that GDDRMAIN is running both at $DC1 and at $DC2.Start GDDRMAIN at the named site and re-run the script.

GDDR857E

Cause A Star-HA (High Availability) takeover is attempted while the takeover threshold is notexceeded. This could indicate that the primary MSC server is still active. If this happens inthe planned Star-HA takeover script, GDDR tries to ensure that the primary MSC server iseither not available or is in a DEACT state. During this verification, the primary MSC serverwas found in an Active state, at the indicated site. The same logic applies when aRESTARTTOSEC is attempted when the local MSC server is not in a DEACT state. GDDRwill then determine the state at the other site which must be Active. Action Review the script joblog and the SCF-log to determine why the primary MSC server wasnot deactivated prior to a Star-HA takeover attempt, or why a primary MSC server is notactive when a RESTARTTOSEC is attempted.

GDDR858I

Cause GDDR has issued a WTOR. The operator entered an unacceptable reply. Action Reply YES or NO.

GDDR859I

Cause GDDR has issued a WTOR. The operator entered an unacceptable reply. Action Enter one of the listed reply options.

GDDR860E

Cause A preceding SC SRDFA(),ACTIVATE command has failed due to possible devices in TNRstatus. Action Examine the preceding script log for possible causes. Also, examine HCLOG and issue theSRDF Host Component SQ VOL command on suspected devices and check their status. Ifyou find TNR status, issue the SRDF Host Component SC VOL,RDF-RSUM command andthen reissue the failed SC SRDFA(),ACTIVATE command.

GDDR861A

Primary MSC server is MSC-state at site-id

GDDR Invalid reply, YES or NO required, try again.

GDDR Invalid reply, enter one of listed optionsor

Invalid reply. Try again...

GDDR SRDF/A not active, start SRDF/A and retry

Please Re-Confirm Run of SWAPSITEN(Yes/No):


Cause Message ID GDDR861A precedes a variety of WTOR messages requesting specificresponses. The requested responses will confirm that GDDR is to take some action.Additional information may be provided by GDDR862I messages preceding this message. Action If a response is indicated, perform the action which is consistent with your policies foractions performed by GDDR. If the messages provide information with no responserequested, no action is needed.

GDDR862I

Cause This message precedes a variety of WTOR messages which inform you of specificconditions or which request responses to choices presented. Action If a response is indicated, perform the action which is consistent with your policies foractions assisted by or performed by GDDR. If the messages provide information with noresponse requested, no action is needed.

GDDR863W

Cause SRDF/A was found in the indicated state (Active, Inactive or Suspended) for the indicatedgatekeeper and SRDF group. Action If the reported state is unexpected, review logs from the affected script, the GDDR EventMonitor, or from SCF for errors. The suspended state can be ignored if it is transient; thatis, it does not occur on two consecutive GDDREVM SRDF/A checks. For example, this canhappen when a TimeFinder Consistent SPLIT is run on the SRDF/A R2 side.Search the Knowledgebase on the Dell EMC Online Support website for applicablesolutions relating to this message ID. If you cannot determine and correct the problem,contact the Dell EMC Customer Support Center for assistance. Make sure you have allrelevant job documentation available.

GDDR864E

or

Please Confirm C-System system-name is DEAD (Yes/No):or

Please Reply RETRY or CONTINUE Please Confirm ACTIVATE of system-name (Yes/No):

GDDR CONFIRMATION ===>************************************************ WARNING WARNING WARNING WARNING ** ** *** SRDF/A was Down at the ** Time of the Unplanned Swap ** ** Please Re-Confirm the Running ** of this Script. ************************************************

GDDR SRDF/A is {active|inactive|suspended} on GK gk RDF GRPsrdfgrp


●

●

●

●

●

●

Cause The indicated storage system has no local gatekeepers at the indicated site. A localgatekeepers is one which does not use an SRDF group. The requested function cannot continue. This is most likely a failure to define allgatekeepers for a storage system at all sites in an AutoSwap environment. Action Ensure that all gatekeepers are defined as appropriate.

GDDR865A

Cause This is an action message that requires an operator response when GDDR detects thatthe indicated system has failed. Action Reply with system ID to request that GDDR IPL the failed system, or I (ignore) to donothing.

GDDR866A

Cause The indicated ConGroup action has been initiated by means of a Modify command directedto the ConGroup started task. The message requires a reply, which will be provided by amessage rule triggered when ConGroup issues its own message in response to thecommand that was issued.action can be:

disable group group_name

enable group group_name

refresh CONGROUP groups

release ALL-CONGROUPS lock

resume group group_name

takeover ownership

Action If the WTOR times out, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have the SYSLOG, the job log, and all relevant jobdocumentation available.

GDDR866E

Cause No working path to the indicated storage system could be found. The requested functioncannot continue. Action Ensure that at least one path that is defined to GDDR to the indicated storage system isfunctional and retry.

GDDR869I

Symm symm-serial has no local gatekeepers at site-id

GDDR Enter desired Option...SYS system_id , SYSSITEn or I:

GDDR Waiting for ConGroup to action. Please reply (Yes/Cancel)

GDDR responds automatically to this message.

Unable to access Symm symmserial: no path available


●

●

●

●

●

●

●

●

Cause GDDR software has detected that the indicated CPC has failed. Various options are listedfor recovery by GDDR, including no recovery at all. This message is followed by messageGDDR875A which requires an operator response. Action None.

GDDR870A

Cause GDDR software has detected that the system named has failed and GDDR is attempting torecover the system (via script GDDRUP03). This WTOR presents the choices which canbe selected. Not all choices listed below are available in all cases. The message lists onlythe choices which may be entered.

IPL:system - IPL the system in the LPAR in which it was running.

SYSRESET - RESET CLEAR the system and leave it down.

SYSRECOV - Recover the system on its recovery LPAR.

SYSSITEn - IPL the contingency system for the failed system.

I - Ignore the event and take no action.This WTOR is preceded by message GDDR869I. Action Select the appropriate choice and reply to the WTOR.

GDDR871I

Cause A missing heartbeat has been detected. The possible reasons for the missing heartbeatare:

The C-system has failed, but the C-system site is alright.

The C-system site has failed.

The C-system has no connections. Action Identify the reason and take appropriate action. If you cannot determine and correct theproblem, Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. Contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR874I

GDDR Unplanned Event ===>

GDDR CPC cpc-name has failed at site site-id.

You have the following choices...

Reply RECOVER - GDDR to recover systems on alternate CPC.Reply NORMAL - GDDR to restart systems individually.Reply Ignore - GDDR to do nothing.

Enter desired option... option

GDDR Unplanned event ===> 737


●

●

●

Cause A script step has completed. The description of the script step, the execution time of thestep, and the return code returned by the script step processor are provided. If the returncode is zero, script processing continues normally. Otherwise, the script run variable is setto the script step return code and the script job terminates. Action If the script step return code is zero, no action is required. Otherwise, determine thereason for the nonzero return code, correct the problem, and restart the script.

GDDR875A

Cause GDDR software has detected a possible CEC failure in a CEC which can be recovered toan alternate CEC. The choices for recovery are as follows:

RECOVER recover the LPARs to their alternate CEC.

NORMAL recover the LPARs in place.

IGNORE ignore the event and take no action.This WTOR is preceded by message GDDR869I. Action Select the appropriate choice and reply to the WTOR.

GDDR876E

Cause During the process of waiting for Star High Availability to be available, it was detected thatthe primary MSC server has stopped. Star-HA will not be available until the primary andsecondary MSC servers are functional. Action Consult the SCF joblog to determine why the primary MSC server has stopped. Takecorrective action and retry.

GDDR877W

Cause During the process of waiting for Star High Availability to be available, Star availability wasachieved, but Star-HA was not. The script terminates. Action Determine why Star-HA is not available (consult the SCF joblog on the primary andsecondary MSC server sites). Make Star-HA available and retry.

GDDR878I

Cause During the process of waiting for Star High Availability to be available, Star availability wasachieved, but Star-HA was not. The script waits up to five SRDF/A cycles for Star-HA tobe available.

GDDR Function function completed in count secs with rc rc

Enter desired option for CEC cec-name ...RECOVER, NORMAL, IGNORE

Primary MSC Server stopped. Check SCF joblog

Timeout waiting for Star-HA

Waiting for Star-HA


●

●

●

●

●

●

●

●

●

●

●

●

Action None.

GDDR880E

Cause The MSC command identified in the message was requested, but was rejected becausethe indicated group is not in an appropriate state. The message provides one of thefollowing reasons:

MSC TAKEOVER in progress

Invalid state: state [ or role: role]

MSC Server not ACTIVE at site-id

MSC Server at site-id not PRIMARY and FORCE not specified

RC=rc waiting for SRDF/A drop and Cleanup to complete

RC=rc waiting for PENDDROP to complete

RC=rc waiting for DEACT to complete

RC=rc waiting for DISABLE to complete

MSC Environment DISABLED

Invalid MSC-MODE: mode

Invalid Congroup name: name. Expected: name Action Identify the reason why the group is in the indicated state. Either wait for the group to getin the appropriate state or correct the problem causing the group to be in the listed state.Check the SCF log and the GDDR script joblog for additional error messages.

GDDR881E

Cause The MSC command identified in the message was issued, but while waiting for thecommand to complete, GDDR either found the indicated group in an inappropriate state ortoo much time passed for the command to complete. For a list of states, see messageGDDR818I. Action Identify the reason why the group is in the indicated state. Correct the problem causingthe group to be in the listed state. Check the SCF log and the GDDR script joblog foradditional error messages. If a timeout occurred, you may have to adjust the GDDR WTORWait Interval parameter or the WTOR Retries parameter.

GDDR882E

Cause The MSC command identified in the message was issued, but while waiting for thecommand to complete, GDDR detected a problem during MSC initialization. The problem isone of the following:

VAL_ERROR - indicates an SRDF Host Component validation error

command command rejected for group mscgrp. Reason: reason

msc-status waiting for command command to complete for groupmscgrp

MSC Initialization error error-description waiting for commandcommand to complete for group mscgrp


●

●

INIT_ERROR - validation error during MSC start

CG_DISABLED - Star/SQAR only, ConGroup got disabled Action Identify the reason why the group is in the indicated state. Correct the problem causingthe group to be in the listed state. Check the SCF log and the GDDR script joblog foradditional error messages.

GDDR883E

Cause MSC was activated, but the activated configuration deviates from what GDDR expected.The message further identifies the mismatch as follows:

See message GDDR818I for further explanation of mode and role. This message is followedby GDDR884E identifying the MSC command and group name affected. Action Verify the contents of the SITxxxxx members in the dataset identified on the Define DellEMC Mainframe Enabler STCs panel (M;P;H;E).

GDDR884E

Cause The MSC command identified in the message was issued, but while waiting for thecommand to complete, GDDR detected that the activated configuration for the indicatedgroup deviates from the expected configuration. Refer to the preceding GDDR883Emessage for details. Action Refer to the preceding GDDR883E message.

GDDR885E

MSC Configuration mismatch. Expected: configuration. Found:configuration

Expected Found

MSC,PRIMARY mode,role

STAR, role mode,role

STARFIRE, role mode,role

SQARA, role mode,role

SQARB, role mode,role

STARA1, role mode,role

STARA2, role mode,role

STAR, CONCURRENT STAR,CASCADED

STAR, CASCADED STAR, CONCURRENT

STARFIRE, CONCURRENT STARFIRE, CASCADED

STARFIRE, CASCADED STARFIRE, CONCURRENT

ConGroup name: gggggggg ConGroup name: hhhhhhhh

MSC Configuration mismatch detected, waiting for command commandto complete for group mscgrp


Cause An MSC,TAKEOVER command was issued for the indicated group but an error occurredduring takeover. Action Review the SCF log for additional error messages.

GDDR886E

Cause No working path to the indicated storage system could be found. The requested functioncannot continue. Action Ensure that at least one path that is defined to GDDR to the indicated storage system isfunctional and retry.

GDDR887I

Cause Waiting for an MSC group to have a certain state was bypassed because with the currentMSC initialization status, there is no guarantee that the group will reach that state. For thelist of group states, refer to message GDDR818I. Action Identify the reason why MSC has the current initialization status. Check the SCF andSRDF Host Component logs for any error messages.

GDDR888I

Cause The ConGroup task on the specified system has shut down successfully. Action None.

GDDR889I

Cause A restart of ConGroup on the indicated system has completed. Action None

GDDR890E

Cause The restart of ConGroup on the indicated system has failed.

MSC TAKEOVER error detected for group mscgrp

Unable to access Symm symm-serial: no path available

Bypassing wait for state state, as MSC initialization status isstatus

GDDR ConGroup shutdown on system-name is complete

GDDR ConGroup startup on system-name is complete

GDDR ConGroup startup on system-name failed, STC name =congroup_name rc = rc


Action Determine the cause of the failure, correct the problem, and resubmit the script that wasrunning when this error occurred.

GDDR891E

Cause The indicated system was not found in the GLOBAL.GDDR.PARMS.site.LPAR.system-name parameters. Action Correct the parameters to include the system and try the process again.

GDDR892E

Cause An attempt to activate the HMC console as an MVS console has failed with the returncode shown. Action Determine the cause of the failure and correct the problem. Then restart the script whichwas running when this problem occurred.

GDDR893E

Cause An attempt to stop the ConGroup task has failed with the return code shown. Action Determine the cause of the failure and correct the problem. Then restart the script whichwas running when this problem occurred.

GDDR894E

Cause The Couple Dataset Management function issued a display command for the indicatedCouple DS type. The command captured output for a different Couple DS Type. Action Search the GDDR script job log and the syslog for related error messages to determinewhy the program did not get the expected output. Search the Knowledgebase on the DellEMC Online Support website for applicable solutions relating to this message ID. If youcannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR895E

GDDR LPAR definition for system system-name not found

GDDR HMC console activation failed, rc = rc

GDDR ConGroup shutdown on system-name failed, STC name = stc_name rc = rc

GDDR couple_type Couple Dataset mismatch detected. (case n)

GDDR {The Primary|The Alternate|Both} cpl_type Couple Dataset{s}could not be changed on system system-name


Cause When verifying the result of Couple Dataset Management on the indicated system, GDDRfound that the couple datasets are not in agreement with the values supplied by the DefineManaged Couple Datasets panel. Action Search the GDDR script job log and the syslog for related error messages. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID. If you cannot determine and correct the problem, contact the DellEMC Customer Support Center for technical assistance. Make sure you have all relevantjob documentation available.

GDDR896E

Cause While verifying status of the couple datasets GDDR intends to switch to, the namedcouple dataset type was found to have a status of >BEING REMOVED<. If the affectedcouple dataset is the intended Primary, the Couple Dataset Management function endswith an error. If it is the intended Alternate, the function will attempt to switch thePrimary. Action Search the GDDR script job log and the syslog for related error messages. Search theKnowledgebase on the Dell EMC Online Support website for applicable solutions relatingto this message ID. If you cannot determine and correct the problem, contact the DellEMC Customer Support Center for technical assistance. Make sure you have all relevantjob documentation available.

GDDR901E

Cause The indicated ISPF service has issued a nonzero return code. Action Consult the appropriate ISPF documentation to identify the cause of the error and correctit.

GDDR902I

Cause A non-zero return code was received on the submit of a script from the GDDR EventMonitor or GDDR Heartbeat Monitor. This message is followed by a set ofGDDR913I messages which contain the messages issued by the submit command. Action Determine why the submit has failed and correct the problem.

GDDR903E

Cause

GDDR {The Primary|The Alternate|Both} cpl_type Couple Dataset[s]had status >BEING REMOVED< on system system-name

GDDR Error in TSO/ISPF function function, data = data

GDDR System error messages:

Unable to ascertain configuration in text for configurationvariable variable


The global variables GLOBAL.GDDR.CONFIG.NUMSITES and/orGLOBAL.GDDR.CONFIG.SITELIST are not initialized. Action Correct the parameters and reload them.

GDDR904I

Cause An error occurred on the submit of a script from GDDR Event Monitor or GDDR HeartbeatMonitor. No error messages were produced. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR906E

Cause A script was submitted by GDDR Event Monitor or GDDR Heartbeat Monitor, but no jobinformation messages were returned. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR907I

Cause A script was submitted by GDDR Event Monitor or GDDR Heartbeat Monitor. Jobinformation was returned and is displayed in a series of GDDR908I messages which followthis message. Action None.

GDDR908I

Cause See message GDDR907I. Action None.

GDDR909W

Cause

No system error messages available

GDDR Script job stream unavailable, rc = rc

GDDR Script job stream:

message-text

Job submission had the following problem: reason


●

●

●

●

There was a problem with JCL that caused a problem with submission. The reason describes the submission problem. The job may not have successfully been submitted. Action Correct the cause of the submission problem and if necessary submit the job again.

GDDR913I

Cause See message GDDR902I. Action None.

GDDR914I

Cause An event was detected by GDDR for which GDDR does not provide facilities for automatedhandling, and which consequently must be handled by manual facilities appropriate to theevent. If CGT appears in the message, a ConGroup trip has occurred; if MHB appears inthe message, a missing heartbeat event has occurred, which may indicate that GDDRHeartbeat Monitor started task has failed and must be restarted.A job has been submitted to ensure that the operator takes note of this condition. This jobwill issue one of the following WTOR messages repeatedly until an operator enters a validreply.

GDDO090A Reply to unplanned ConGroup Trip warning

GDDO092A Reply to unplanned Missing Heartbeat warning

GDDO094A Reply to unplanned SRDF/A failure warning

GDDO096A Reply to unplanned AutoSwap warning Action Reply to the WTOR message that is issued following this message. Take the appropriateaction for the event that occurred.

GDDR915I

Cause The couple datasets for the indicated system are being operated on. Action None.

GDDR916E | GDDR916I

Cause The indicated GDDR HMC interface program ended with the indicated non-zero returncode. Action If the message class is I, this message may indicate a normal situation. No action isnecessary.

message-text

GDDR Running warning-only script for non-handled-GDDR-event event

GDDR Fixing couple datasets for site site-id system system-name

GDDR program_name rc=rc


●

●

●

●

●

●

If the message class is E, the message may indicate a problem. Review the job log andSYSLOG for related error messages, especially GDDR917E. Search the Knowledgebase onthe Dell EMC Online Support website for applicable solutions relating to this message ID. Ifyou cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR917E

Cause The indicated GDDR HMC interface program provided the diagnostic information shown inthe message:

Environmental error. Please check log for additional messages.

- This is an internal error. Search the GDDR script job log and the syslog for related

error messages. Search the Knowledgebase on the Dell EMC Online Support website

for applicable solutions relating to this message ID. If you cannot determine and

correct the problem, contact the Dell EMC Customer Support Center for technical

assistance. Make sure you have all relevant job documentation available.

Expected message msgtext not found. - If this causes the GDDR script to

fail, search the job log, syslog and OSF server job log for related error messages.

Search the Knowledgebase on the Dell EMC Online Support website for applicable

solutions relating to this message ID. If you cannot determine and correct the

problem, contact the Dell EMC Customer Support Center for technical assistance.

Make sure you have all relevant job documentation available.

HWMCAAPI call RC=rc - Use the IBM API documentation to determine the

cause of the error.

Not authorized to use program_name - Check the syslog for security

warnings to determine which resource the user running the indicated GDDR HMC

interface program is not authorized for. Refer to the GDDR Product Guide for your

configuration for a checklist to make sure all required authorizations are in place.

Stopped by GDDRTERM message. - This is caused by an intentional issuing of

the GDDRTERM message, which is not part of normal GDDR functioning.

USS timeout waiting for hmc_c_program to return. - The indicated

GDDR HMC interface program did not return in the time specified in message

GDDR753I. Action Take action based on the provided diagnostic information.

GDDR918W

Cause The couple datasets have not been switched. Action Consult the SYSLOG for any errors that indicate why the couple datasets cannot beswitched. Search the Knowledgebase on the Dell EMC Online Support website for

GDDR program_name Diagnostic information: diagnostic_information

GDDR Couple dataset could not be changed for system system-name


applicable solutions relating to this message ID. If you cannot determine and correct theproblem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR919E

Cause An attempt to issue a command in the USS environment failed. Action Examine the return code for any information about why the command failed. Consult theSYSLOG for any errors that indicate why the command failed. Search the Knowledgebaseon the Dell EMC Online Support website for applicable solutions relating to this messageID. If you cannot determine and correct the problem, contact the Dell EMC CustomerSupport Center for technical assistance. Make sure you have all relevant jobdocumentation available.

GDDR920E

Cause A request has been made to restart a system using its contingency system, but nocontingency system is defined for the failing system. Action Define a contingency system and reload GDDR parameters.

GDDR921E

Cause A request has been made to verify the state of BCVs at the site given in the message, butthe BCV in the message is not in the desired state. Action Correct the BCV state with TimeFinder and rerun the job.

GDDR922E

Cause A request has been made to verify the state of BCVs at the site given in the message, butthe BCV in the message was not present in the TimeFinder Query command output. Action Verify that the device is in fact a BCV and that the gatekeeper and SRDF group definedfor it are correct; if not, correct the parameters and reload them, then rerun the job. If thedevice is a BCV, contact customer support.

GDDR924W

Cause

GDDR USSCMD failed in text rc = rc

No contingency system defined for system failing_system

site BCV device from swap group swapgrp not state

site BCV device from swap group swapgrp not found in TimeFinderQuery

Rerun script not found; new script generated


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

A request was made to rerun an action script, but the previously generated script was notfound. A new script is generated. Action None.

GDDR925I

Cause Generation of the requested action script has begun. Action None.

GDDR926E

Cause An error occurred during the generation of the script. The message gives the return codeand reason code, as well as the name of the rule which generated the error. In general,return codes have the following meaning:

4 - operator confirmation was not received

13 - the requested script is incompatible with the configuration

14 - the requested script is incompatible with the current state

99 - an internal consistency error occurred.Specific return code/reason code combinations are:

13/5 - script is valid only in a configuration which includes DC3

13/6 - script is valid only in a 2 site configuration

13/7 - script is valid only in a Star configuration

13/8 - script is valid only in a Star with AutoSwap configuration

13/9 - script is valid only in a Star High Availability configuration

13/10 - GDD2P17A was not the last-run script (GDD2P18A can only be run if the

previously run planned script was GDD2P17A.)

13/11 - script is not valid in 2 site Star

13/12 - script can only run on the master C-system

13/13 - script can only run in a 2 site Star configuration

13/21 - script is valid only in an AutoSwap configuration

13/23 - script is invalid in a 2 site configuration

13/24 - script is valid only in a 4 site configuration

13/25 - script is not valid in a 4 site configuration

13/41 - script cannot specify SCPRM in current configuration

13/42 - script must specify SCPRM in current configuration

13/43 - site specified is not valid in this configuration

13/51 - script is valid only in a cascaded Star configuration

13/53 - script is valid only in a cascaded Star with AutoSwap configuration

13/54 - script is not valid in cascaded 2 or 3 site Star configuration

13/121 - only allowed at secondary DASD site

Beginning Generation of Script

Script Generation Error: rc-rs (script-rule) explanation


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

13/122 - only allowed at primary DASD site

13/253 - script is valid only in a cascaded configuration

13/292 - script is valid only in a concurrent configuration

13/360 - only allowed on primary MSC server

13/368 - only allowed to run at DC3

13/369 - not allowed to run at DC3

13/403 - no transaction ID (A script which requires a transaction ID was requested,

but no transaction ID was supplied)

13/501 - requires SNAP Target Devices

13/992 - requires a GDDR Tape for VNX & DD License

13/993 - requires a GDDR (VMAX) License

13/2002 - script is valid only in 3 site Star, 2 site concurrent Star, or 2 site SRDF/S

configurations

13/2014 - script is valid only in 2 site Star or 2 site SRDF/S configurations

13/2017 - script is valid only in non-AutoSwap configurations (2 or 3 site)

13/3009 - script is valid only in a 2 site AutoSwap configuration

13/3010 - script is valid only in a 2 site ConGroup configuration

13/3011 - the LDR event is not on for the current primary DASD site

13/3012 - script is valid only in a 2 site SRDF/A configuration

13/3013 - script is valid only in a 2 site SRDF/S configuration

13/3031 - script is valid only in a Star with AutoSwap configuration

13/3041 - script is valid only in a cascaded Star configuration

13/4001 - the last unplanned script is not appropriate

13/4002 - GDDRPF29 should be run instead of GDDRPM29

13/4003 - the script should not be executed again

13/4004 - previous run script is not OK

13/4100 - GDDRPM29 in Secondary region is only allowed on the SQAR SRDF/A leg

which was activated earlier by a GDDRPA06 or GDDRPA07 script (ctds-case)


which was activated earlier by a GDDRPA06 or GDDRPA07 script (cqds-case)

13/4102 - GDDRPM29 in Primary region is only allowed on the SQAR SRDF/A leg A-

>C after UP31/U13A ran

14/4 - the SRA event is on (SRDF/A is down)

14/5 - the RDF event is on

14/6 - the MSC event is on

14/7 - the LDR event is not on for DC2

14/8 - the STR event is on

14/9 - the CFG event is on

14/10 - GDD2P17A was not the last-run script (GDD2P18A can only be run if the

previously run planned script was GDD2P17A.)

14/11 - the LDR event is not on for DC1 (GDDRPA07, with primary site =DC2, or

cascaded data-flow, is only allowed if there is an LDR event for DC1)

14/12 - data precedence is not appropriate for the script (Some scripts require that


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

the most current data be at particular sites or that one site has more current data

than another site or that data at certain sites is usable.)

14/13 - the requested protection preference (global variables containing

PROTECTION.PREFERENCE) cannot be accomplished in the current state. Either

change the appropriate global variable or change the state or run another script.

14/14 - the DLM event is on

14/15 - SRDF/A is active or SRDF/A status cannot be determined

14/16 - SRDF/A is currently in a SUSPENDED state

14/17 - the MST event is on

14/18 - the DLM event is off for the source site

14/28 - the SRA event is off (SRDF/A is up)

14/29 - the STR event is off (Star or SQAR available)

14/71 - the LDR event is on for DC1




14/80 - script requires GDDRMAIN at primary DASD site

14/81 - script requires GDDRMAIN at secondary DASD site

14/82 - script requires GDDRMAIN at tertiary DASD site

14/83 - script requires GDDRMAIN at quaternary DASD site

14/121 - only allowed at secondary DASD site

14/211 - the C>> event is on (DC3 is ahead)

14/254 - cascading is not active

14/255 - the Star-HA state is not valid

14/292 - the CGT event is on (a ConGroup trip has occurred)

14/359 - only allowed on secondary MSC server

14/360 - only allowed on primary MSC server

14/361 - only allowed on ConGroup owner site

14/368 - only allowed to run at DC3

14/369 - not allowed to run at DC3

14/401 - no dynamic device data (A script which requires dynamic device data was

requested, but no data was present)

14/402 - invalid dynamic device data (A script which requires dynamic device data

was requested, but the data was invalid)

14/403 - no transaction ID (A script which requires a transaction ID was requested,

but no transaction ID was supplied)

14/423 - a CAX event has occurred or is in progress (an AutoSwap event has

occurred or is occurring)

14/800 - requires a GDDR tape profile

14/990 - the MHB event is on for the current secondary DASD site (MHB is missing

heartbeat)

14/991 - an unplanned script is currently running

14/992 - requires a GDDR Tape for VNX & DD License


●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

14/993 - requires a GDDR (VMAX) License

14/994 - ConGroup verify is in progress

14/996 - degraded mode is on

14/997 - MSF event is on

14/998 - a different planned script is in progress (a different script than the one

requested)

14/999 - a planned script is in progress

14/2001 - the site passed to the script is not the current primary DASD site

14/2005 - the current primary site does not match the current primary DASD site

14/2014 - the RDF and CGT events are not both on (RDF is replication, CGT is

ConGroup trip)

14/2911 - the ECA event is on (Enginuity Consistency Assist)

14/2912 - the CGD event is on (ConGroup drop)

14/3009 - the CAX and CGT events are on (CAX is an AutoSwap event, CGT is

ConGroup trip)

14/3010 - the LDR event is not on (LDR is local disaster recovery)

14/3011 - the LDR event is not on for the current secondary DASD site

14/3012 - the RDR event is not on (RDR is regional disaster recovery)

14/3013 - DC3 is down

14/3014 - the LDR event is not on for the current primary DASD site

14/3015 - the RDF event is not on for the selected site

14/3031 - the CAX event is not on (AutoSwap event)

14/3032 - a CAX event has completed successfully

14/3112 - the MSC event is not on

14/3141 - the CGT event is not on (ConGroup trip)

14/4001 - the last unplanned script is not appropriate

14/4002 - GDDRPF29 should be run instead of GDDRPM29

14/4003 - the script should not be executed again

14/4004 - previous run script is not OK

14/4012 - the storage systems at primary and/or secondary site are not accessible


which was activated earlier by a GDDRPA06 or GDDRPA07 script (ctds-case)


which was activated earlier by a GDDRPA06 or GDDRPA07 script (cqds-case)

14/4102 - GDDRPM29 in primary region is only allowed on the SQAR SRDF/A leg A-

>C after UP31/U13A ran

14/4110 - the BCV management call override for the selected site is not 1.

14/4111 - resynch-in-progress targets selected site

14/4112 - local invalid tracks at selected site Action The action depends on the return code:

4 - Retry if appropriate

13 - The requested script cannot be run in your configuration. Request a different


●

●

script. If you believe the script is valid for your configuration, contact the Dell EMC

Customer Support Center for assistance.

14 - The requested script cannot be run in your current state. Wait until the state

changes or take action to change the state and retry.

99 - Contact the Dell EMC Customer Support Center. GDDR927E

Cause The generation of the requested action script resulted in a script with no steps. Action Contact Dell EMC Customer Support.

GDDR928E

Cause A manually loaded action script is being rerun, but the script was not found. Action Ensure the script was loaded correctly and try again. If the problem is not resolved,contact customer support.

GDDR929I

Cause The execution of the action script is beginning. Action None.

GDDR930E

Cause The indicated global variable is not initialized. Action The variable is required for the current action. Get the appropriate value for the variableand reload parameters. Rerun the job.

GDDR931I

Cause HMC action has been bypassed for the indicated site and LPAR because of theHMC.BYPASS parameter. Action None.

Script Generation Error: no steps

Rerun script not found

Beginning Execution of Generated Script

Global variable variable not initialized

HMC action bypassed for site site-id, lpar lpar-name


●

●

●

GDDR932I

Cause During GDDR processing, a request to split or establish the BCVs at the site indicated wasignored because the BCVs were not found in the requested state at the start of GDDRprocessing. Action None.

GDDR933E

Cause The script to be executed is associated with a transaction ID. This generally indicates thatthe script originated from EzSM. The transaction ID passed with the script does not matchthe transaction ID lock, so the script cannot be executed. Action This can occur when processing scripts submitted from EzSM. The script with thetransaction ID in the lock must be either completed or abandoned before another scriptwith a different transaction ID can be run. Refer to the EzSM documentation. Also, youcan abandon the original script from the GDDR script submission panel.

GDDR934E

Cause The GDDR BCV state verification utility found an unexpected state for the listed devices.The message identifies the site, the storage system, device range, and nature of theproblem.This can be the result of a user error on invocation of the utility, incorrect GDDRdefinitions, unexpected actions causing BCV's to be in an unexpected state. Action Possible actions are:

Use EMCTF to correct the state of the BCV.

Add BCV definitions for GDDR-managed STD devices listed as missing a paired BCV.

Correct the arguments passed to the utility. Instructions are provided in gddrhlq

.SAMPLIB(GDDRTF00). GDDR935I

Cause GDDR is about to allocate the dataset from where the script will be executed. Themessage identifies the dataset name. Action Look for message GDDR936I when the script ends, signaling that the dataset wassuccessfully deleted.

Request to {SPLIT|ESTABLISH} BCVs at site site-id ignored becauseBCVs were not originally in that state

Script not allowed - transaction id mismatch

GDDR TARGET verification failed: text

GDDR allocating script dataset:GDDR dsname


GDDR936I

Cause GDDR has successfully deleted the dataset from where the script was run. This message should occur every time a script ends with a zero or non-zero RC. Action If this message does not occur, look for message GDDR937E signaling problems duringallocation, writing or deletion of the script dataset.

GDDR937E

Cause GDDR failed to perform the listed action on the script dataset, with the indicated returncode. Action Look for accompanying TSO messages for more information. This message is issued whenGDDR fails to allocate the script dataset, or write the script to the script dataset. In suchcase, script processing is terminated.This message is also issued when GDDR fails to delete the script dataset after the scripthas ended. In this case, GDDR attempts to empty the dataset. If this fails an additionalGDDR937E message is issued. The script job is then allowed to terminate normally.If this message is issued for a failure to delete or empty the script dataset, identify thescript dataset name using message GDDR935I which was issued at the start of the script,and delete it. Once a script has ended, either normally or abnormally, GDDR has no furtheruse for the script dataset.When canceling a GDDR script, script dataset delete processing is bypassed, requiringmanual deletion.

GDDR941E

Cause During the verification of the results of CF Structure management GDDR received anIXC391I message on the indicated system. CF structure management is stopped with anerror. Action Search the GDDR script joblog, syslog and the OSF Server joblog for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. If you cannot determine and correct theproblem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR942E

Cause During the verification of the results of CF structure management for the indicated

GDDR Deleted script dataset:GDDR dsname

GDDR Failed to action the script dataset RC = rc

GDDR Rebuild of CF structures stopped for system system-name.Check log for IXC391I message

GDDR Rebuild of CF structures stopped for system system-name. CFRMActive Policy is empty on this system.


system, GDDR found that the CFRM Active Policy was empty. CF structure managementis stopped with an error. Action Search the GDDR script job log, syslog and the OSF server job log for related errormessages. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for technical assistance. Make sure you have all relevant jobdocumentation available.

GDDR943W

Cause During verification of CF Structure management results, GDDR received an IXC360Imessage indicating that no structures match the structure listed in the GDDR943Wmessage. GDDR retries verification up to 5 times and then stops CF structuremanagement for this system with error message GDDR976E. Action Search the GDDR script job log, SYSLOG and the OSF server job log for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. If you cannot determine and correct theproblem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR944W

Cause During verification of CF Structure management results, GDDR received an IXC360Imessage indicating that the named structure was NOT ALLOCATED. GDDR retriesverification up to 5 times and then stops CF Structure management for this system witherror message GDDR976E. Action Search the GDDR script joblog, syslog and the OSF Server joblog for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR945W

Cause During verification of CF Structure management results, GDDR did not receive an IXC360Imessage showing the indicated structure. GDDR retries verification up to 5 times and thenstops CF structure management for this system with error message GDDR976E. Action Search the GDDR script job log, SYSLOG and the OSF Server job log for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. If you cannot determine and correct theproblem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR CF Structure structure_name not matched on verify [retrying(n/5)] [retries exhausted]

GDDR CF Structure structure_name not allocated on verify

GDDR CF Structure structure not found on verify


GDDR961I

Cause This message reports fixing of CF structures for the indicated system and site. Action None.

GDDR962E

Cause Internal error. During the set-up phase of CF Structure management, GDDR detects thatnot all required internal structures have been created to manage all the systems eligible forCF Structure management. The CF Structure management function stops. Action Search the GDDR script joblog, syslog and the OSF Server joblog for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR963W

Cause Status progression message for CF structure management on the indicated system. Action None.

GDDR964I

Cause This message reports successful rebuild of CF structures on the indicated system. Action None.

GDDR965E

Cause The GDDR CF structure management function failed on the named system with theindicated return code. Other messages will provide more detailed information. Action Search the GDDR script job log, syslog and the OSF server job log for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. If you cannot determine and correct the

GDDR Fixing CF Structures for system system-name at site site-id

GDDR Did not initiate CF Structure management for all validsystems ( nn / mm )

GDDR Rebuild of CF structures on system-name : status

GDDR Rebuild of CF structures on system-name succeeded.

GDDR Rebuild of CF structures on system-name failed with RC rc


problem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR966I

Cause Summary information message. Action None.

GDDR967E

Cause GDDR CF structure management failed to complete the rebuild of all CF structures in thetime specified by the CF Rebuild Timeout value in the Script Sysplex Options panel. Action Because GDDR will not rebuild CF structures unnecessarily, it is possible that submittingthe job again will correct the issue. If possible and required, increase the value of the CFRebuild Timeout value in the Script Sysplex Options panel, Activate the parameter set withthe Partial keyword, and submit the job again.In all other cases, search the GDDR script joblog, syslog and the OSF Server joblog forrelated error messages. Search the Knowledgebase on the Dell EMC Online Supportwebsite for applicable solutions relating to this message ID. If you cannot determine andcorrect the problem, contact the Dell EMC Customer Support Center for technicalassistance. Make sure you have all relevant job documentation available.

GDDR968E

Cause This message provides additional information when GDDR967E was issued. It is issuedonce per system where CF structure management was not completed at the time of thetimeout. Action See action for GDDR967E.

GDDR969E

Cause During the initial checks for CF structure management GDDR received an IXC391Imessage on the indicated system. CF structure management is bypassed for this system. Action If you do not need CF structure management for this system, remove the Couple FacilityStructure names from the Define Managed CF Structures panel for this system.In all other cases, search the GDDR script job log, syslog and the OSF server job log forrelated error messages. Search the Knowledgebase on the Dell EMC Online Supportwebsite for applicable solutions relating to this message ID. If you cannot determine andcorrect the problem, contact the Dell EMC Customer Support Center for technical

GDDR Rebuild of CF structures succeeded

GDDR Rebuild of CF structures timeout

GDDR Rebuild of CF structures incomplete on system-name

GDDR Rebuild of CF structures bypassed for system system-name.Check log for IXC391I message.


assistance. Make sure you have all relevant job documentation available. GDDR970E

Cause During the initial checks for CF structure management on the indicated system, GDDRfound that the CFRM Active Policy was empty. CF structure management is bypassed forthis system. Action If you do not need CF structure management for this system, remove the Couple FacilityStructure names from the Define Managed CF Structures panel for this system. In allother cases, search the GDDR script job log, syslog and the OSF server job log for relatederror messages. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for technical assistance. Make sure you have all relevant jobdocumentation available.

GDDR971W

Cause During initial checks for CF structure management of the indicated structure on theindicated system, GDDR received an IXC360I message indicating that no structures matchthe structure indicated in the GDDR971W message. CF structure management is bypassedfor this structure. Action If you do not need CF structure management for this structure, remove the related CoupleFacility Structure names from the Define Managed CF Structures panel. In all other cases,search the GDDR script job log, syslog and the OSF server job log for related errormessages. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for technical assistance. Make sure you have all relevant jobdocumentation available.

GDDR972W

Cause During the initial checks for CF structure management of the indicated structure on the indicated system, GDDR received an IXC360I message indicating that the indicatedstructure was 'NOT ALLOCATED'. CF structure management is bypassed for thisstructure. This message may be due to the relative timing of system and applicationsrestart versus the GDDR CF Structure management. Action If you do not need CF structure management for this structure, remove the related CoupleFacility Structure names from the Define Managed CF Structures panel. If the messageappears to be due to timing, restart the CF Structure management function after thebusiness applications are completely restarted. In all other cases, search the GDDR scriptjob log, syslog and the OSF server job log for related error messages. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center fortechnical assistance. Make sure you have all relevant job documentation available.

GDDR Rebuild of CF structures bypassed for system system-name.CFRM Active Policy is empty on this system.

GDDR Rebuild of structure_name bypassed for system system-name.(not allocated)


GDDR973W

Cause During the initial checks for CF structure management of the indicated structure on theindicated system, GDDR did not receive an IXC360I message showing the indicatedstructure. CF Structure management is bypassed for the indicated structure. Action If you do not need CF structure management for this structure, remove the related CoupleFacility Structure names from the Define Managed CF Structures panel. In all other cases,search the GDDR script job log, syslog and the OSF server job log for related errormessages. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for technical assistance. Make sure you have all relevant jobdocumentation available.

GDDR974I

Cause During the initial checks for CF structure management on the indicated system, GDDRfound the indicated structure already located in the indicated CF, which matches therelated Couple Facility Structure names from the Define Managed CF Structures panel. Action None.

GDDR975W

Cause During the initial checks for CF structure management on the indicated system, GDDRfound the indicated structure already located in the indicated CF, which does not matchthe related Couple Facility Structure names from the Define Managed CF Structurespanel. GDDR will attempt to rebuild the structure in one of the Coupling Facilities specifiedon the related Couple Facility Structure names. Action None.

GDDR976E

Cause GDDR CF structure management failed to rebuild the indicated CF structure on theindicated system with the return code shown in the message. Action Search the GDDR script job log, syslog and the OSF server job log for related errormessages. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for technical assistance. Make sure you have all relevant job

GDDR Rebuild of structure_name bypassed for system system-name.(not found)

GDDR found CF Structure structure_name in correct CF(cf_name) onsystem system-name

GDDR found CF Structure structure_name in incorrect CF(cf_name) onsystem system-name

GDDR Rebuild of structure_name failed on system system-name. RC(rc )


documentation available. GDDR977I

Cause This message signals that GDDR CF structure management is about to begin the rebuild ofthe indicated CF structure on the indicated system. Action None.

GDDR978W

Cause During the verification of the results of CF Structure management, GDDR found that theindicated CF structure was still in its original location. GDDR will verify up to 5 times. Action None, unless the message shows that retries are exhausted. In that case, search theGDDR script job log, SYSLOG and the OSF Server job log for related error messages. Ifyou cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR979I

Cause This message reports successful rebuild of the indicated structure. Action None.

GDDR980W

Cause During verification of the results of CF structure management for the indicated structure,GDDR found that the structure was moved from its original location, but not to one of theCoupling Facilities specified on the related Couple Facility Structure names. Action Verify that the Couple Facility Structure names from the Define Managed CF Structurespanel specify a CF which is likely to be eligible to hold the indicated CF structure. Searchthe GDDR script job log, SYSLOG and the OSF Server job log for related error messages.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR981W

GDDR Rebuilding structure_name on system-name

GDDR CF Structure structure_name was not moved on verify -[retrying. (n/5)][retries exhausted.]

GDDR Successfully rebuilt structure_name in CF: cf_name

GDDR New CF (cf_name) for structure_name does not match GDDRparameters.

GDDR {CF Structure|Couple Dataset} processing bypassed. Reason =


●

●

●

●

●

Cause The indicated GDDR function detected that GDDR parameter values were set so that thefunction should not run. Action Depending on the required functionality, ignore this message, or change the indicatedparameter to an appropriate value.

GDDR982I

Cause GDDR did not attempt to rebuild the indicated CF structure, after the initial displaycommand. The return code indicates the reason for this decision, as follows:

RC(4): NO STRUCTURES MATCH THE SPECIFIED CRITERIA

RC(5): strname NOT ALLOCATED

RC(6): strname not found as an ACTIVE STRUCTURE

RC(8): D XCF command did not return an IXC360I message

RC(12): D XCF command did not return any output Action Search the syslog, the job log and the OSF server log for related messages to guide acourse of action if needed. Verify that the Couple Facility Structure names from theDefine Managed CF Structures panel, specify correct CF Structure names.

GDDR983E

Cause GDDR received message IXC367I indicating that the SETXCF REBUILD command for theindicated CF structure was rejected for the reason indicated. The GDDR CF structuremanagement step ends with RC=20. Action Search the GDDR script job log, syslog and the OSF server job log for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. If you cannot determine and correct theproblem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR991E

Cause This is a diagnostic message for Dell EMC use. Action None.

GDDR992E

reason

GDDR Rebuild of structure_name bypassed on system system-name.RC(rc)

GDDR Rebuild of structure_name rejected on system system-name.Reason: reason

message-text

Format 1:


Cause For Format 1: The worker that was assigned to this GDDR work request was stopped with force. Thework request could not be completed. A dump of the associated work control block isdisplayed following the message for Dell EMC use. For Format 2: An error has occurred in a GDDR function. This line indicates the calling program, ifapplicable.The error numbers are :899 - The GDDR SSVT could not be located. This generally means that GDDRMAIN hasnot been started on this system. Start GDDRMAIN and retry.898 - A GDDR work control block could not be obtained. Contact the Dell EMC CustomerSupport Center.897 - A GDDR work data block could not be obtained. Contact the Dell EMC CustomerSupport Center.849 - A work request timed out with no response. This may indicate that the remotesystem is down or that GDDRMAIN is down on that system. It could also be caused by acommunications outage between this system and the remote system. Investigate andremedy the situation and retry.848 - Internal error. Contact the Dell EMC Customer Support Center.847 - Internal error. Contact the Dell EMC Customer Support Center.846 - An error occurred in a TCP/IP service. The message gives the name of the serviceand the error code. If the relevant TCP/IP documentation does not give some possibleremedy, contact the Dell EMC Customer Support Center for assistance.845 - Internal error. Contact the Dell EMC Customer Support Center.844 - Internal error. Contact the Dell EMC Customer Support Center.843 - Work is being requested at a remote site, but there is no worker of the named typeat the named site/system. Therefore, the work cannot be run. Take the necessary steps torun workers of the indicated type on the indicated system or site.842 - An error was returned from a function run on a remote site/system. The messagegives the function, the error code, and the remote site/system. You may need to examinethe GDDR992E message on the remote system for more details. The error code from theremote system is one of the error codes documented in this message.841 - A Data block returned via MWCB has an invalid type. Internal error. Contact the DellEMC Customer Support Center.799 - Internal error. Contact the Dell EMC Customer Support Center.798 - Internal error. Contact the Dell EMC Customer Support Center.797 - Internal error. Contact the Dell EMC Customer Support Center.796 - Internal error. Contact the Dell EMC Customer Support Center.795 - The gatekeeper being used is not valid. This may indicate an error in the GDDRparameters.794 - The device number being used is not valid. This may indicate an error in the GDDRparameters.793 - The SRDF group number being used is not valid. This may indicate an error in theGDDR parameters.792 - Internal error. Contact the Dell EMC Customer Support Center.791 - Internal error. Contact the Dell EMC Customer Support Center.790 - Internal error. Contact the Dell EMC Customer Support Center.789 - Internal error. Contact the Dell EMC Customer Support Center.749 - Internal error. Contact the Dell EMC Customer Support Center.748 - Internal error. Contact the Dell EMC Customer Support Center.699 - Internal error. Contact the Dell EMC Customer Support Center.698 - Internal error. Contact the Dell EMC Customer Support Center.697 - If the function giving the error is GDDRADEV, then the gatekeeper is not defined in

Error 995 in program: Worker was stopped with forceFormat 2:Caller: calling_program


the SYMM parameters of GDDRMAIN. This is generally a mismatch between GDDRparameters and the GDDRPARM contents. If the function giving the error is GDDRQDEV,then the gatekeeper is not usable. The error should be preceded by a GDDM031E messagewith an EMCSAI error code. Refer to the GDDM031E message for the particular reasonwhy the gatekeeper is not usable.696 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.695 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.694 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.693 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.692 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.691 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.690 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.689 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.688 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.687 - Error from GDDRSSYS. Refer to an immediately preceding GDDM031E message forGDDRSSYS giving the error codes. This generally indicates that GDDRMAIN has neverbeen started on this system.686 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.685 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.683 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.682 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.681 - Error from EMCSAI. Refer to an immediately preceding GDDM031E message forEMCSAI giving the error codes.680 - Internal error. Contact the Dell EMC Customer Support Center.602 - Constants eyecatcher for baseless operation doesn't verify. Contact the Dell EMCCustomer Support Center.601 - Request was disallowed by system security. Check your SAF profile definitions.590 - Internal error. Contact the Dell EMC Customer Support Center.591 - The SRDF group was not found. This may be an error in the GDDR deviceparameters.592 - Internal error. Contact the Dell EMC Customer Support Center.593 - Internal error. Contact the Dell EMC Customer Support Center.594 - Internal error. Contact the Dell EMC Customer Support Center.580 - Internal error. Contact the Dell EMC Customer Support Center.581 - Internal error. Contact the Dell EMC Customer Support Center.582 - Internal error. Contact the Dell EMC Customer Support Center.583 - Device error. This error code is preceded by a GDDM031E message giving the exacterror.584 - Unable to complete request. This error code is preceded by another GDDR992Emessage giving the reason the request could not be completed.570 - Internal error. Contact the Dell EMC Customer Support Center.571 - The global variable data space is exhausted. Contact the Dell EMC CustomerSupport Center.572 - The global variable update was disallowed by a consistency exit. Consistency exitsare enabled by parameter load if consistency is requested. If a parameter load is running,


wait and retry once the parameter load has completed. If no parameter load is running, youmay have to manually deactivate the exit. Manually deactivate the exit with the z/OSSETPROG command, as described in the GDDR Product Guide for your configuration.573 - Generally, this means that GDDRMAIN is not running.560 - Internal error. Contact the Dell EMC Customer Support Center.550 - Internal error. Contact the Dell EMC Customer Support Center.540 - BCPII - A Disconnect Request has failed. The return code, reason code and abendcode from the call to the TSO Service Facility are all listed in this message.539 - BCPII - A Connection Request has failed. The return code, reason code and abendcode from the call to the TSO Service Facility are all listed in this message.538 - BCPII - ACTIVATION Force type parameter is invalid537 - BCPII - ACTIVATION w/ Profile is missing the Profile536 - BCPII - System Reset IPL Token XML Data @ Missing535 - BCPII - System Reset IPL Token Force Type Invalid534 - BCPII - System Reset IPL Token Force Type Missing533 - BCPII - System Reset IPL Token Request Type Invalid532 - BCPII - System Reset IPL Token Request Type Missing531 - BCPII - Temp Capacity Upgrade XML Data @ Missing530 - BCPII - Temp Capacity Upgrade Request Type Invalid529 - BCPII - Temp Capacity Upgrade Request Type Missing528 - BCPII - LOAD Request Force Type Invalid527 - BCPII - LOAD Request Parameter Must accompany LOAD @526 - BCPII - MVS Command Missing525 - BCPII - MVS Command Priority Invalid524 - BCPII - MVS Command Priority Missing523 - BCPII - System Reset Force Type Invalid522 - BCPII - System Reset Request Type Invalid521 - BCPII - System Reset Request Type Missing520 - BCPII - Reserve Application Name Length Invalid519 - BCPII - Reserve Application Name Missing518 - BCPII - Reserve Request Type Invalid517 - BCPII - Reserve Request Type Missing516 - BCPII - Profile Imp/Exp Area Indicator Invalid515 - BCPII - Profile Imp/Exp Area Indicator Missing514 - BCPII - Profile Imp/Exp Request Type Invalid513 - BCPII - Profile Imp/Exp Request Type Missing512 - BCPII - On/Off Capacity On Demand Missing Order #511 - BCPII - On/Off Capacity On Demand Invalid Req Type510 - BCPII - On/Off Capacity On Demand Missing Req Type509 - BCPII - Capacity Backup Invalid Activation Type508 - BCPII - Capacity Backup Missing Activation Type507 - BCPII - Capacity Backup Invalid Request Type506 - BCPII - Capacity Backup Missing Request Type505 - BCPII - Hardware Message Delete TimeStamp Missing504 - BCPII - Hardware Message Request Type Invalid503 - BCPII - Hardware Message Request Missing Type502 - BCPII - Deactivation Force type is invalid501 - BCPII - Activation Force type is invalid500 - BCPII - Command Request to BCPII is invalid539 - BCPII - An HMC Connect request failed. The return code, reason code, and abendcode from the TSO Service Facility are indicated in the message. The return code is theresult of a call to HWICONN. The HWICONN return codes can be found in the z/OS MVSProgramming: Callable Services for High-Level Languages manual.540 - BCPII - An HMC Disconnect request failed. The return code, reason code, and abendcode from the TSO Service Facility are indicated in the message. The return code is theresult of a call to HWIDISC. The HWIDISC return codes can be found in the z/OS MVSProgramming: Callable Services for High-Level Languages manual.541 - BCPII - A List HMC request failed. The return code, reason code, and abend code


●

●

●

from the TSO Service Facility are indicated in the message. The return code is the resultof a call to HWILIST. The HWILIST return codes can be found in the z/OS MVSProgramming: Callable Services for High-Level Languages manual. Action For Format 1: If the work request is PowerMax or VMAX-related, investigate the problem.Resubmit the failed script, rerunning or skipping the failed step as appropriate. ContactDell EMC Customer Support if the problem persists. For Format 2: Refer to error code in first line of the GDDR992E message.

GDDR993I

Cause This is a diagnostic message for Dell EMC use indicating that an attempt was made to freea work block twice. This is a transient issue and should not cause any lasting effects. Themessage includes a dump of the affected work block. Action Contact Dell EMC Customer Support if the issue persists.

GDDR994E

Cause The indicated GDDR program returned the error message shown. Action Search the GDDR script job log, syslog and the OSF server job log for related errormessages. Search the Knowledgebase on the Dell EMC Online Support website forapplicable solutions relating to this message ID. If you cannot determine and correct theproblem, contact the Dell EMC Customer Support Center for technical assistance. Makesure you have all relevant job documentation available.

GDDR995I

Cause Used as a highlighter for messages, to separate messages, and draw attention to them. Action None.

GDDR996E

Cause The GDDRMAIN PC interface is not available for the requested GDDR subsystem. EitherGDDRMAIN is not active for that subsystem, or the GDD$nnnn DD DUMMY statement inyour JCL does not specify the correct GDDR subsystem name (nnnn).The following table explains reason codes for the user abends:

U0806-01 - GDDRMAIN PC interface not available

U0806-02 - No active GDDRPCR module found

U0806-03 - Requested PC routine not found

Work block double free attempted

GDDR program_name returned the following message: message-text.

***********************************************************

GDDRMAIN PC interface not available


For reason code 1: The GDDRMAIN PC interface is not available for the requested GDDRsubsystem. Either GDDRMAIN is not active for that subsystem, or it has not completedinitialization. This abend is accompanied by message 'GDDR996E GDDRMAIN PC interfacenot available'. Ensure GDDRMAIN is active for the requested GDDR subsystem, and retry.Contact Dell EMC Customer Support if the problem persists. For reason code 2: No active PC interface module was found. Issue the FGDDRMAIN,RELOAD command to reload the PC interface module. An inactive copy willbe freed, if applicable, and a new copy will be loaded and marked active. There are up totwo copies in memory at any given time; one should be active and the other should beinactive. Contact Dell EMC Customer Support if the problem persists. For reason code 3: The requested PC routine was not found. Ensure all GDDR addressspaces are at the same maintenance level. Check all GDDR job logs for GDDM075E orGDDM076E errors. If necessary, correct the JCL and/or recycle the down-level addressspaces. Contact Dell EMC Customer Support if the problem persists. Action Start GDDRMAIN for the requested GDDR subsystem, or correct the GDD$xxxx DDDUMMY statement in the JCL, and retry.

GDDR997E

Cause An error occurred that may indicate an environmental issue. This message includes adescription of the error, as well as diagnostic information for Dell EMC use. Action Contact Dell EMC Customer Support if the issue persists. Note that TCP/IP errors whileIPLing systems or restarting GDDR tasks are expected and can be ignored.

GDDR998E

Cause Format 1: An error has occurred which appears to be a GDDR program error. The erroridentifier can be utilized by Dell EMC Customer Support to diagnose and resolve the error.Format 2 is produced by GDDRGVRL to signal missing required parameters.Format 3: A logic error was detected. Action Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support website for applicable solutions relating to this message ID.In case of missing SYMM parameters, review the SYMM statements in the GDDRPARMfile, make corrections if necessary, and restart GDDRMAIN.For format 3, check the accompanying GDDR998G message for troubleshooting.If you cannot determine and correct the problem, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have all relevant job documentationavailable.

GDDR998F

message-text

Format 1:

INTERNAL ERROR: CALL TECH SUPPORT - ID = error_identifierFormat 2:

No SYMM parameters define DC1 gatekeepers for Symmetrix symm-serialFormat 3:

GDDR INTERNAL ERROR: Diagnostic Information follows:


Cause A logic error was detected.GDDR998F is an alternative message format of GDDR998E. Action Check the accompanying GDDR998G message for troubleshooting. Contact Dell EMCCustomer Service for assistance.

GDDR998G

Cause A GDDR internal logic error was detected. Action Contact Dell EMC Customer Service for assistance.

GDDR999A

Cause If a return code of four (4) is received from the SC_SRDFA,LCL(gk), ACT command,SRDF/A is refreshed and the command is tried again. Action None.

GDDR999I

Cause In reaction to a CGRP999I message, signaling a status change for consistency groupsand/or SDAS, GDDR provides a translation of the reported statuses to readable form. Action None.

GDDRUXM3

Cause Distributed workload is to be started or stopped. This message is issued either as a WTOor a WTOR, depending on whether or not acknowledgement is needed that the start orstop has completed. Action If the message is issued as a WTOR, reply anything to indicate that the workload has beenstarted or stopped. If the message is a WTO, no action is required.

GDDRUXM4

GDDR INTERNAL ERROR: Diagnostic Information follows:

diagnostic-information

GDDR Allowing device table synchronization, rerunning SRDF/Aactivate

CG State [ cg_state_text ] SDAS State [ sdas_state_text ]

primary-site-id/secondary-site-id/{swap|LDR}:{Start|Stop} Distributed System Workload

primary-site-id/secondary-site-id/{swap|LDR}:{Start|Stop} Distributed System Workload


Cause Distributed workload is to be started or stopped. This message is issued either as a WTOor a WTOR, depending on whether or not acknowledgement is needed that the start orstop has completed. Action If the message is issued as a WTOR, reply anything to indicate that the workload has beenstarted or stopped. If the message is a WTO, no action is required.


CHAPTER 9 GDDR EVM and HBM Messages (GDDS) GDDS001I

Cause The indicated GDDR monitor is starting. The starting timestamp is given. Processingcontinues. Action None.

GDDS002I

Cause The indicated GDDR monitor is starting. The starting timestamp is given. Processingcontinues. Action None.

GDDS003I

Cause The indicated GDDR monitor is running on the indicated C-system. The master C-systemis indicated. Processing continues. Action None.

GDDS004I

Cause The indicated monitor, once initialization is completed, will wait the specified number ofseconds between status checks. For the Event Monitor, this value can be modified bymeans of parameter Event.Monitor.Interval. For the Heartbeat Monitor, this value can bemodified by means of the Event Monitor Interval value in the Specify GDDR Tuning Valuespanel. Processing continues. Action None.

GDDS005I

GDDR {Event Monitor|Heartbeat Monitor} starting on date at time

GDDR {Event Monitor|Heartbeat Monitor} version is date_time

GDDR {Event Monitor|Heartbeat Monitor} running on system-name,master C-System is system-name

GDDR {Event Monitor|Heartbeat Monitor} using wakeup interval ofnnn seconds

GDDR Event Monitor using message level nnn


●

●

●

Cause This message indicates that the Event Monitor message processing will include messagesat or below the indicate message level. This has no effect on error messages, which arenever suppressed. Processing continues. Action None.

GDDS006W

Cause The indicated monitor started task has completed with the indicated return code.However, both the Event Monitor and the Heartbeat Monitor must remain running on eachC-system in order for GDDR to function properly. Possible reasons for intentionallyterminating a monitor started task include bringing down the C-system on which themonitor is running for an IPL, changing the GDDR configuration by removing the C-systemon which the monitor is running, or stopping and restarting the monitor started task inorder to run an upgraded version of the monitor. Action Determine the reason for started task termination. Regardless of the return code, unlessthe indicated monitor was intentionally stopped for one of the reasons described above,examine the SYSTSPRT and JESJOBLG messages for indications of an error. When theproblem has been corrected, restart the indicated monitor.

GDDS007E

Cause The system on which the Heartbeat Monitor is running is not a known C-system. GDDRmonitors are designed to run only on C-systems. The monitor terminates. Action If the monitor was started on an incorrect system, no response is necessary as long as aninstance of the monitor is running on each configured C-system. However, if the monitorwas started on a system that was intended to be a configured C-system, check the mostrecent GDDR parameter load job and the current values of pertinent GDDR parameters.These parameters are the following:

GLOBAL.GDDR.DC1.C.System.Systemid

GLOBAL.GDDR.DC2.C.System.Systemid

GLOBAL.GDDR.DC3.C.System.SystemidIf the indicated current system name is not the value of one of these parameters, do notstart the monitor on this system. Otherwise, contact the Dell EMC Customer SupportCenter for technical assistance. Make sure you have the SYSLOG, the job log, and allrelevant job documentation available.

GDDS008I

Cause The Heartbeat Monitor will consider the possibility that a remote Heartbeat Monitor is notactive if the specified number of seconds elapses with no heartbeat (Heartbeat Monitor

GDDR {Event Monitor|Heartbeat Monitor} completed with rc rc

GDDR Current system system-name not a valid C-System, HeartbeatMonitor terminating

GDDR Heartbeat Monitor using missing heartbeat interval ofnnn seconds


timestamp) received from the remote Heartbeat Monitor. Processing continues. This valuecan be modified by means of the Heartbeat Monitor Interval in the Specify GDDR TuningValues panel. This parameter is described in the GDDR Product Guide for yourconfiguration. Action None.

GDDS009I

Cause The Heartbeat Monitor will declare a remote Heartbeat Monitor dead if the specifiednumber of missing heartbeat intervals pass with no heartbeat (Heartbeat Monitortimestamp) received from the remote Heartbeat Monitor. Processing continues. This valuecan be modified by means of the Missing Heartbeat Threshold in the Specify GDDR TuningValues panel. This parameter is described in the GDDR Product Guide for yourconfiguration. Action None.

GDDS010I

Cause The Heartbeat Monitor is about to announce to other C-systems that the current site isactive. It does so by setting the GDDR ‘alive’ indicator for the site at which it is running.Processing continues. Action None.

GDDS011I

Cause The system on which the Event Monitor is running is the master C-system. Unplannedscripts can therefore be submitted by the Event Monitor. Action None.

GDDS012I

Cause The system on which the Event Monitor is running is not or is no longer the master C-system. Unplanned scripts can therefore not be submitted by the Event Monitor. Action None.

GDDS013I

GDDR Heartbeat Monitor using missing heartbeat threshold of nnn

GDDR notifying remote sites that current site site-id is alive

GDDR Running on the master C-System, unplanned scripts available

GDDR Not on the master C-System, unplanned scripts unavailable

GDDR Unplanned scripts are now available


Cause The system on which the Event Monitor is running has become the master C-system dueto a master C-system function transfer. Unplanned scripts can therefore now besubmitted by the Event Monitor. Action None.

GDDS014I

Cause The system on which the Event Monitor is running is no longer the master C-system dueto a master C-system function transfer. Unplanned scripts can therefore not be submittedby the Event Monitor. Action None.

GDDS015W

Cause A GDDR script of the indicated type is executing and unplanned scripts cannot besubmitted for execution. Action None.

GDDS016I

Cause A GDDR script of the indicated type is executing and unplanned scripts can now besubmitted. Action None.

GDDS017I

Cause An unplanned script has been successfully submitted, as indicated by a previous message.Unplanned scripts can therefore no longer be submitted by the Event Monitor until theunplanned script just submitted has completed successfully. Action None.

GDDS018I

Cause As part of periodic state variable checking, the Event Monitor is examining the event-related state variables that pertain to the indicated site.

GDDR Unplanned scripts are unavailable

GDDR type script executing, unplanned scripts unavailable

GDDR type script executing, unplanned scripts now available

GDDR Unplanned scripts are now unavailable

GDDR Event Monitor checking events for site site-id


Action None.

GDDS019I

Cause As part of periodic state variable checking, the Event Monitor is examining the indicatedevent-related state variable. The variable applies to the site indicated in the most recentlyissued GDDS018I message. Action None.

GDDS020E

Cause As part of periodic state variable checking, the Event Monitor is examining the indicatedevent-related state variable. The variable applies to the site indicated in the most recentlyissued GDDS018I message. An internal error code is generated and the Event Monitorterminates. Action Verify that the system on which the Event Monitor was running is a valid C-system.Ensure that Site and System entries in the Define Managed Systems panel have beenspecified for the system. After the problem is corrected, restart the Event Monitor.

GDDS021I

Cause When submitting an unplanned script, the Event Monitor builds the job stream inaccordance with certain GDDR parameter values. This message is followed by a list ofthese values. Action None.

GDDS022I

Cause The Event Monitor or Heartbeat Monitor has been dispatched following a wait interval.The dispatch date and time is indicated. The GDDR state will now be checked, and ifnecessary appropriate actions will be taken. Action None.

GDDS023I

Cause

GDDR Event Monitor processing var_name

GDDR Event Monitor running on system with no GDDR site defined

GDDR Unplanned script jobs will use the following values

GDDR - - - - - - <dispatch date and time> - - - - - - - - - - -

GDDR Master C-System change from system-name to system-name hasbeen detected


The Event Monitor or Heartbeat Monitor has determined that the current master C-system is different from the master C-system during the previous dispatch. The GDDRstate will now be checked, and if necessary appropriate actions will be taken. Action None.

GDDS024I

Cause The Event Monitor has determined that it is running on the current master C-system andshould therefore handle GDDR events. Processing continues. Action None.

GDDS025W

Cause The Event Monitor has determined that the missing heartbeat event has occurred on thecurrent system. The Heartbeat Monitor may have experienced a system error. Action Verify that the Heartbeat Monitor is running and has not encountered an error. Thencheck whether a problem has prevented update of the heartbeat on the current system.Take whatever corrective action may be required. If necessary, stop and restart theHeartbeat Monitor on the current system.

GDDS026I

Cause The Event Monitor has determined that it is not running on the current master C-systemand should therefore not handle GDDR events. Processing continues. Action None.

GDDS027E

Cause When a GDDR planned script is not running, this message is issued every GDDR EventMonitor cycle for each unplanned event which was detected during this or any previousGDDR Event Monitor cycle and has not been cleared yet. Action This message indicates the GDDR Event Monitor has detected an event which requiresaction on the part of the GDDR user to clear. In some cases, a GDDR unplanned scriptsequence will be presented to the operator for confirmation.To determine action to be taken, refer to the listing of monitored events provided in theGDDR Product Guide for your configuration.

GDDR Running on master C-System, will handle events

GDDR Warning: Missing Heartbeat and C-System-Alive events both onor

GDDR Warning: Check Heartbeat Monitor on this system

GDDR Not running on master C-System, will not handle events

GDDR Error: Event event-id detected, value event-description


GDDS027W

Cause When a GDDR Planned script is not running, GDDS027E is issued every EVM cycle foreach unplanned event which was detected during this or any previous EVM cycle and hasnot been cleared yet. Action The GDDS027E message indicates the Event Monitor has detected an event whichrequires action on the part of the GDDR user to clear. In some cases a GDDR unplannedscript sequence will be presented to the operator for confirmation.To determine action to be taken, refer to the listing of monitored events provided in theGDDR Product Guide for your configuration.

GDDS028W

Cause The Event Monitor has detected an AutoSwap event. GDDR notes the event, but will takeno action until the swap is complete. Action None.

GDDS029I

Cause The Event Monitor reports Expected Events list. Expected events are Active eventscaused by current GDDR actions.This list is expanded and reduced over the course of a GDDR action, and will be empty atthe end of the GDDR action or shortly thereafter.There will be no GDDR786E message for these events, and no GDDRWARN job will besubmitted. Action None.

GDDS030I

Cause The indicated program or GDDR component is waiting for GDDRMAIN to be fullyinitialized. Action None.

GDDS031I

Cause The Event Monitor is scanning the exception event types listed. Subsequent messageswill indicate whether any occurred.

GDDR Warning: Event event-id detected, value event_value

GDDR Skipping partial CAX event, value var_value

GDDR Expected Events: list-of-events

program-name waiting for GDDRMAIN initialization

GDDR Checking event list event_list


Action None.

GDDS032I

Cause The Event Monitor is checking whether the current event scanning the exception eventtypes listed. Subsequent messages will indicate whether any occurred. Action None.

GDDS033I

Cause The Event Monitor is checking whether the current event scanning the exception eventtypes listed. Subsequent messages indicate whether any occurred. Action None.

GDDS034I

Cause The Event Monitor is scanning the exception event types listed. Subsequent messagesindicate whether any occurred. Action None.

GDDS035I

Cause The handling status for the indicated event has not changed. Processing continues. Action None.

GDDS036I

Cause The Event Monitor has completed handling the indicated event. Processing continues. Action None.

GDDS037I

Cause

GDDR Matched event event_name ( modifier )

GDDR Checking handling indicator indicator_name

GDDR No longer handling event_name [ at site-id ]

GDDR No change to event_name [ at site-id ]

GDDR Reset event handling for event_name [ at site-id ]

GDDR No exception events for site site-id detected this cycle


●

●

●

The Event Monitor is scanning the exception event types listed. Subsequent messages willindicate whether any occurred. Action None.

GDDS038I

Cause The Event Monitor detected the indicated exception event. Action None.

GDDS039W

Cause The Event Monitor has determined that the missing heartbeat event has occurred at leastone site. The ‘degraded’ indicator is set on and processing continues. Action None.

GDDS040I

Cause An event of interest was detected by the Event Monitor. However, the Event Monitor isnot running on the master C-system, and consequently does not handle this event.Processing continues. Action None.

GDDS041I

Cause A missing heartbeat event was detected by the Event Monitor. Because the EventMonitor is running on the master C-system, it will handle this event. Processing continues. Action None.

GDDS042I

Cause An exception event was detected by the Event Monitor. Exception events that may bereported are:

CAX - AutoSwap swap

NCX - No channels available

HBM - Missing heartbeat

GDDR Exception event NCX for swap group group_name

GDDR Operating in degraded mode due to MHB event at site-id

GDDR event event ignored on non-master C-System system-name

GDDR event event at site-id being handled

GDDR event event detected at site-id


●

●

●

●

CGD - ConGroup disabled

SRA - SRDF/A link down

RDR - Regional Disaster

CGT - ConGroup tripA subsequent message will indicate whether this event will be handled or will be ignored onthe current system. Action None.

GDDS043I

Cause The state variable for the indicated event at the indicated site has been set off. Processingcontinues. Action None.

GDDS044I

Cause The Event Monitor has completed handling the indicated event. Action None.

GDDS045I

Cause The indicated event cannot be reset because one or more instances is still being handled.An instance of an event can be site-specific or system-specific. Processing continues. Action None.

GDDS046I

Cause No event that would indicate an SRDF/S problem has been detected by the EventMonitor. Processing continues. Action None.

GDDS047E

Cause An SRDF Links failure event has been detected. The GDDR Event Monitor continues bychecking whether other error conditions exists.

GDDR Event event reset for site site-id

GDDR No longer handling event event [ at site-id ]

GDDR Event event not eligible for reset at site site-id

GDDR SRDF/S analysis detected no problem

GDDR SRDF/S analysis detected an RDF Links failure


●

●

●

●

●

●

●

Action None.

GDDS048I

Cause An exception event has been previously detected. Exception event descriptions whichmay be reported are:

CAX - AutoSwap swap

NCX - No channels available

HBM - missing heartbeat

CGD - ConGroup disabled

SRA - SRDF/A link down

RDR - Regional Disaster

CGT - ConGroup trip Action None.

GDDS049E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script. The name of the dataset containing the generated job is given, togetherwith the return code. The TSO Command Reference may provide information on themeaning of the return code. Action Determine the reason for the failure. If necessary and possible, submit the script jobmanually.

GDDS050E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script as described in a previous GDDS049E message. The messages returnedby the SUBMIT command follow this message. Action None.

GDDS050I

Cause The specified task was just started. This is a herald message indicating the compile dateand time, GDDR version, and PTF level of the specified module.The eyecatcher format is as follows:<module>-<date>-<time>-GDDR<version>-<ptflevel> Action

GDDR Already handling event

GDDR Script submit from dsname failed, rc = rc

GDDR Script submit error messages follow

GDDR task starting - eyecatcher


None. GDDS051E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script, as described in message GDDS049E. This message includes the text ofan error message issued in response to the TSO SUBMIT command. Action Use this message to determine the reason for the failure. If necessary and possible,submit the script job manually.

GDDS051I

Cause This message lists the applied PTFs for the specified module. The PTF list is in the form of3-digit numbers separated by commas. If no PTFs are applied, 'none' is indicated. Action None.

GDDS052E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script as described in a previous GDDS049E message. However, no errormessages were generated by the SUBMIT command. The Event Monitor will attempt toprovide the job stream that was to have been submitted. Action None.

GDDS053E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script as described in a previous GDDS048I message. The Event Monitor wasunable to provide the job stream that was to have been submitted. Action None.

GDDS054E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script as described in a previous GDDS048I message. The Event Monitor wasable to access the job stream that was to have been submitted. Subsequent GDDS055Ewill provide job stream records, if any.

GDDR > error_message

GDDR module PTFs applied: ptflist

GDDR No script submit error messages available

GDDR Script job stream unavailable

GDDR Script job stream follows


Action None.

GDDS055E

Cause The Event Monitor received a nonzero return code while attempting to submit anunplanned script, as described in message GDDS048I. This message includes the text of astatement in the script job stream that was being submitted. Action Use this message to determine the reason for the failure. If necessary and possible,submit the script job manually.

GDDS056I

Cause The Event Monitor received a zero return code submitting an unplanned script. The nameof the script and the dataset containing the generated job are given. It will not be possiblefor another unplanned script to be submitted until this script completes. Action Ensure that the script job has begun to execute. If it has not, check that an initiator isavailable for the script job. Also ensure that the operator confirmation message for scriptappears on the console, and issue an appropriate confirmation reply.

GDDS057E

Cause The Event Monitor has determined that at least one global value necessary to submitunplanned scripts is not valid. The reason for this is indicated in the failure description. Ifthis message appears during initialization, the Event Monitor issues messageGDDS058E and terminates. Otherwise the Event Monitor issues message GDDS059E andcontinues execution without submitting the unplanned script. Action Correct the error indicated in the message. If the Event Monitor has terminated due tothis error, restart the Event Monitor. If the unplanned script was not submitted, submitthe script job manually if necessary.

GDDS058E

Cause The Event Monitor has determined that at least one global values necessary to submitunplanned scripts is not valid. The reason for this is indicated in a previousGDDS057E message. The Event Monitor continues execution without submitting theunplanned script. Action Correct the error indicated in the message. Submit the script job manually if necessaryand possible.

GDDR > job_stream_record

GDDR Script script-name submitted from dsname

GDDR Global verify failed, failure_description

GDDR Script submit cancelled


GDDS059E

Cause Because a global value necessary to submit unplanned scripts is not valid, as indicated in aprevious GDDS057E message, the Event Monitor is terminating. Action Correct the error indicated in the previous GDDS057E message and restart the EventMonitor.

GDDS060W

Cause The Event Monitor has determined that a missing heartbeat state variable for theindicated C-system has been set on. The Event Monitor continues by attempting todetermine whether other state variables have been set. Action None.

GDDS061E

Cause The Event Monitor has detected a failure of the indicated system, but has determined thatthe failure is not a site-wide failure. Action None.

GDDS062E

Cause The Event Monitor has detected a site failure at the indicated site. The failure involves oneor systems at the indicated site. Action None.

GDDS063E

Cause The Event Monitor has detected system failures due to a site failure at the site indicatedby the previous GDDS062E message. The number of failed systems is indicated. Action None.

GDDS064I

GDDR Event Monitor terminating

GDDR Missing C-System heartbeat detected at site site-id

GDDR Detected system system-name failure at site site-id

GDDR Detected a site failure at site site-id

GDDR Found nnn of nnn MXS events DEAD, nnn of nnn MIM events DEAD

GDDR {Planned|Unplanned} script script-name is running


Cause The Event Monitor has determined that the indicated script is running. Action None.

GDDS065I

Cause The Event Monitor has determined that no unplanned script is running. Action None.

GDDS066I

Cause The Event Monitor has detected a planned event, such as an IPL, for the indicated systemat the indicated site. Action None.

GDDS067I

Cause While performing a periodic state check, the Event Monitor has detected no plannedevents for the indicated site. Action None.

GDDS068I

Cause While performing a periodic state check, the Event Monitor has determined that allsystem-specific events or group-specific events at a site have been cleared. The eventindicator for the site is therefore cleared. Action None.

GDDS069I

Cause While performing a periodic state check, the Event Monitor has determined that not allsystem-specific events or group-specific events at a site have been cleared. The eventindicator for the site is therefore not eligible to be cleared. Action

GDDR No {planned|unplanned} script is running

GDDR Planned event event_name at site site-id for system system-name

GDDR No planned events for site site-id detected this cycle

GDDR Event event_name reset to 0 for site site-id

GDDR Event event_name not eligible for reset at site site-id


None. GDDS070W

Cause The value of the indicated parameter was invalid. The default value will be used instead.Processing continues. Action Correct the invalid value. If desired, stop and restart the currently executing monitor topick up the new parameter value.

GDDS071I

Cause As part of periodic housekeeping, the Heartbeat Monitor is about to test whether accessto the remote C-system(s) is available. Subsequent messages indicate the results of thetest. Processing continues. Action None.

GDDS073E

Cause The Event Monitor was unable to determine whether automation is ON or OFF. Theautomation flag must be accessible for GDDR operation. The Event Monitor terminates. Action Determine the reason for this error. The Event Monitor may be running on the wrongsystem, or may be connected to the wrong SCF subsystem ID. Alternatively, theparameter database may have been corrupted. After taking the appropriate correctiveaction, restart the Event Monitor.

GDDS074W

Cause The Event Monitor has determined that automation is OFF. When automation is set toOFF, no event handling is performed. Action Ensure that this is the desired automation setting. If necessary, set automation ON.

GDDR Heartbeat Monitor missing heartbeat interval parameter_valueinvalid, reverting to default valueor

GDDR Heartbeat Monitor missing heartbeat threshold parameter_valueinvalid, reverting to default valueor

GDDR {Event Monitor|Heartbeat Monitor} wakeup intervalparameter_value invalid, reverting to default value

GDDR Heartbeat Monitor verifying remote C-System access

GDDR Event Monitor unable to access automation flag, exiting

GDDR Warning: because Automation is set to off, no event handlingis in effect


GDDS075I

Cause The Event Monitor has determined that the automation setting has changed as indicatedby the message. This can be accomplished via option A on the Administration PrimaryOption Menu. Action None.

GDDS075W

Cause The Event Monitor has determined that the automation setting has changed as indicatedby the message. Action Ensure that this is a desired change. If necessary, change the automation setting. Thiscan be accomplished via option A on the Administration Primary Option Menu.

GDDS079W

Cause The GDDR Event Monitor has detected event event which occurred at site site-id. Action Refer to the discussion of unplanned event management in the GDDR Product Guide foryour configuration for detailed information about the referenced event.Reply Y to GDDR WTOR prompts if desirable to enable the GDDR managed recovery forthe event, otherwise reply N.

GDDS081I

Cause Conditions are such that EVM would like to submit an unplanned script, but cannot do soeither because another script is currently in execution or because a SPLIT BRAINcondition has been detected (see message GDDS221E). Action None.

GDDS096E

Cause The submission of a GDDR script has been cancelled due to a conflict within the current

GDDR Automation has been set ON this cycle

GDDR Warning: Automation has been set OFF this cycle

GDDR Exception event event at site site-id

GDDR Bypassing script script-name submit, SPLIT BRAIN conditiondetectedor

GDDR Bypassing script script-name submit, a script is currentlyactive

GDDR Script submit cancelled


configuration or operating environment. Action See the preceding messages. Correct the configuration or environmental conflict andresubmit the script.

GDDS122I

Cause While performing a periodic state check, the Heartbeat Monitor has determined that noheartbeat has been received from the remote Heartbeat Monitor running at the indicatedsite for the indicated number of seconds beyond the missing heartbeat interval indicate inmessage GDDS008I. The Heartbeat Monitor determines whether the situation warrantsdeclaring the remote Heartbeat Monitor dead, taking several factors into account.Subsequent messages will indicate what action, if any, the Heartbeat Monitor will take. Action None.

GDDS123I

Cause The Heartbeat Monitor has determined that the heartbeat from the indicated remote siteis being received indirectly through the Heartbeat Monitor at the third site but not directlyfrom the indicate site. The link between the current system and the remote C-system atthe indicated site may be unavailable. Action Determine whether a link has failed between the current system and the remote C-systemat the indicated site.

GDDS124I

Cause The Heartbeat Monitor has determined that the heartbeat from the indicated remote siteis missing. However this condition has been detected previously. Action None.

GDDS125I

Cause The Heartbeat Monitor has determined that an IPL is scheduled for the C-System onwhich the failed remote Heartbeat Monitor was running. No further action is required. Action None.

GDDS126I

GDDR Site site-id heartbeat overdue by nnn seconds

GDDR Site site-id heartbeat still being updated via remote site

GDDR Site site-id previously declared dead, waiting for heartbeatresumption

GDDR Not setting missing heartbeat indicator at site site-id, IPLalready scheduled for system-name


Cause The Heartbeat Monitor has set the missing heartbeat event indicator for the indicated site.This will be detected by the Event Monitor and cause appropriate action. Action None.

GDDS127I

Cause The Heartbeat Monitor has set the planned IPL indicator for the C-system on which thefailed remote Heartbeat Monitor was running. If an IPL is necessary, GDDR will perform it.If the remote Heartbeat Monitor can be restarted, however, this indicator will be reset andno C-system IPL will take place. Action None.

GDDS128I

Cause After setting the planned IPL indicator for the C-system on which the failed remoteHeartbeat Monitor was running, the Heartbeat Monitor has propagated this indicator tothe remaining remote C-systems. Action None.

GDDS129I

Cause After having previously marked the heartbeat for a remote site as missing, the HeartbeatMonitor has now detected an updated heartbeat from the remote site. To ensureconsistency, all remote Heartbeat Monitors are notified that the current system HeartbeatMonitor is alive. Action None.

GDDS130I

Cause As part of actions to indicate that the current C-system is alive, the Heartbeat Monitorhas reset the planned IPL indicator for the C-system. Processing continues. Action None.

GDDS131I

GDDR Missing heartbeat indicator has been set for site site-id

GDDR Planned IPL indicator has been set for system system-name

GDDR Planned IPL indicator has been propagated

GDDR Heartbeat for site site-id has resumed, system system-name

GDDR Planned IPL indicator has been reset for system system-name

GDDR Reset planned IPL indicator has been propagated


Cause After resetting the planned IPL indicator for the current C-system, the Heartbeat Monitorhas propagated this indicator to the remaining remote C-systems. Action None.

GDDS132I

Cause The heartbeat of the current Heartbeat Monitor, the heartbeat that will be propagated toa remote Heartbeat Monitor indirectly through the third C-system, has been directed tothe C-system having the indicated system name. Processing continues. Action None.

GDDS134I

Cause The Heartbeat Monitor has determined that the heartbeat of the indicated remote site isnot being updated directly, but only by means of the heartbeat. The link between thecurrent system and the remote site is identified as having failed. Processing continues. Action None.

GDDS135I

Cause The Heartbeat Monitor has determined that the heartbeat of the indicated remote site isbeing received directly but not by means of the heartbeat. The link between the tworemote sites is identified as having failed. Processing continues. Action None.

GDDS136W

Cause The heartbeat of the indicated site has not been received since midnight. Processingcontinues. Action None.

GDDS137W

Cause

GDDR Heartbeat for site-id has set to Heartbeat at system-name

GDDR site-id not updating heartbeat directly, setting LNK.site-id_site-id event

GDDR site-id heartbeat not arriving via remote site, settingLNK.site-id_site-id event

GDDR Heartbeat not received from site-id today

GDDR site-id Heartbeat not being updated


The heartbeat of the indicated site has not changed. Processing continues. Action None.

GDDS138E

Cause The Heartbeat Monitor was unable to establish access to a remote C-system beforeupdating the current system’s heartbeat at the indicated system. This message is followedby GDDS139E. If running, the Heartbeat Monitor at the third site will detect this failureand issue a corresponding message. Action Determine the reason for the error and correct it.

GDDS140E

Cause The Heartbeat Monitor encountered an error updating the current system's heartbeat atthe indicated system. This message is followed by GDDS139E. If running, the HeartbeatMonitor at the third site will detect this failure and issue a corresponding message. Action Determine the reason for the error and correct it.

GDDS141I

Cause The Heartbeat Monitor is beginning its initialization process. Subsequent messagesindicate success or failure or the various steps involved. Action None.

GDDS142E

Cause During initialization the Heartbeat Monitor attempted to notify other sites that the site onwhich it is running is alive. However the notification was not successful. Precedingmessages may indicate details of the failure. Initialization proceeds. Action Determine the reason for the notification failure, which may represent a condition handledby GDDR or a software-related error condition. Appropriate responses may range fromtaking no action to contacting Dell EMC Customer Support.

GDDS143I

GDDR Error propagating Heartbeat to system-name, unable to accessremote system

GDDR Error propagating Heartbeat to system-name, unable to updateremote system

GDDR Heartbeat Monitor beginning initialization

GDDR Notification failed, rc = rc

GDDR Resetting site-id_Heartbeat_Missing indicator


Cause During initialization, the Heartbeat Monitor is setting the ‘missing heartbeat’ eventindicator to a ‘false’ value, announcing that the heartbeat for the site on which it is runningis not missing. Initialization proceeds. Action None.

GDDS144E

Cause During initialization, the Heartbeat Monitor attempted to set the ‘missing heartbeat’ eventindicator to a ‘false’ value. However, the operation was not successful. Precedingmessages may indicate details of the failure. Initialization proceeds. Action Determine the reason for the failure, which may represent a condition handled by GDDR ora software-related error condition. Appropriate responses may range from taking no actionto contacting Dell EMC Customer Support.

GDDS145I

Cause The Heartbeat Monitor has determined that the GDDR master C-system is at thesecondary GDDR site, the usual location for the master C-system. Processing continues. Action None.

GDDS146I

Cause The Heartbeat Monitor has determined that it is perform initialization on the master C-system. Consequently, it will attempt to broadcast the parameter set to all remote C-systems. Processing continues. Action None.

GDDS147W

Cause The Heartbeat Monitor has determined that the master C-system is not at the expectedsite for the current environment. Subsequent messages indicate possible action theHeartbeat Monitor may take if the master C-system is at the expected location.Processing continues. Action None.

GDDS148I

GDDR Reset failed, rc = rc

GDDR Master C-System system-name is at secondary site site-id

GDDR Initializing on master C-System, broadcasting GDDR parameters

GDDR Master C-System system-name is at site-id, not at correctsite site-id


●

●

Cause The Heartbeat Monitor has determined that the master C-system is not at the secondaryGDDR site, the normal site for the GDDR master C-system. GDDR options are set to forcea transfer of the C-system master function to the usual site when this is detected, and thetransfer will now be initiated. Subsequent messages will indicate the success or failure ofthe transfer. Processing continues. Action None.

GDDS149W

Cause The Heartbeat Monitor normally backs up the GDDR parameters before broadcasting theparameters to remote C-systems. However, no dataset has been defined to contain thebackup, so the backup is skipped. Processing continues. Action If backups are desired in the future, a dataset to contain parameter backups should beallocated and specified as the GDDR parameter BACKUP_DSNAME.system-name.Backups may also be initiated manually with Manage GDDR Parameter Backups asdescribed in the GDDR Product Guide for your configuration.

GDDS150I

Cause Before broadcasting the GDDR parameters, the Heartbeat Monitor creates a backup ofthe parameters. The second line of the message indicates the name of the dataset intowhich the backup member will be saved, and the third line indicates the name of thebackup member. This format of the backup member name is Vmmmmddd, indicating thedate and time the backup was started as follows:

ddd - The day number in the current year.

mmmm - The number of minutes since midnight. Action None.

GDDS151E

Cause GDDR global variable backup routine GDDRGVBB could not get an exclusive ENQ on thebackup dataset immediately, most likely because another backup is in progress against thedataset. The job or TSO user that is trying to get the ENQ will wait for the ENQ. Action When the waiting job or TSO user can get exclusive use, it will issue message GDDS151I toindicate the wait is over, and the global variable backup will proceed.

GDDS152E

GDDR Scheduling transfer of C-System master function to site site-id

GDDR No backup dataset defined, GDDR parameter backup skipped

GDDR Beginning backup of GDDR parametersGDDR Using backup dataset backup_dsnameGDDR Backup member member_name will be created

GDDR Waiting for ENQ GDDRBKUP dsn=dsname


●

Cause The Heartbeat Monitor normally backs up the GDDR parameters before broadcasting theparameters to remote C-systems. However, an error was encountered as described by oneor more prior messages, so the backup is skipped. Processing continues. Action Determine the problem encountered by examining previous messages. If desired, you caninitiate backups manually using the Manage GDDR Parameter Backups panel.

GDDS153I

Cause The Heartbeat Monitor was unable to allocate the dataset specified for GDDR to use tocontain a parameter backup. The message contains an error message that was issued bythe system for the allocation failure. Action Utilize the message to ascertain the cause of the error.

GDDS154E

Cause The parameter backup process encountered an error before broadcasting the parametersto remote C-systems. The return code occurred during an EXECIO operation. The backupis skipped. Processing continues.Possible return code values include:

893 - Typically reflects a "queue full" condition, caused by the presence of a large

number of GDDR system variables of type "RUN", "RUND" or "SCRIPT" on the C-

system where the GDDR parameter backup is being performed. Action For return code 893, use the "Manage GDDR System Variables" panel line commands "D"or "Z" as applicable to delete unnecessary variables. RUND variables can always bedeleted. RUN and SCRIPT variables can be deleted, unless a planned or unplanned script isin process. In that case do not delete variables named "GLOBAL.GDDR.RUN.script-name"or "GLOBAL.GDDR.SCRIPT.script-name".Error codes for EXECIO are found in the TSO REXX Reference Manual. If desired, oncethe problem is corrected, you may initiate a backup manually by using the Manage GDDRParameter Backups panel.

GDDS155I

Cause The Heartbeat Monitor has successfully created a parameter backup. The number ofrecords written to the parameter backup dataset and the number of parameters whosevalues were backed up are given. Processing continues. Action None.

GDDR Global Variable Backup will not be taken

GDDR -> error_message

GDDR Write to backup dataset failed, rc = rc

GDDR nnn records written to backup for nnn parameters GDDR Globalvariable backup complete


GDDS156I

Cause The Event Monitor has extracted the sites for which events will be handled from theGDDR parameters. The list of sites is given. Processing continues. Action None.

GDDS157I

Cause The Event Monitor has completed the current wait interval and is checking for anychanges in GDDR-related status. Subsequent messages will indicate the results of thischeck. Processing continues. Action None.

GDDS158W

Cause The Event Monitor has determined that the GDDR configuration state indicator, which isnormally the same at all configured sites, differs for the indicated sites. The states at eachof the different sites will be shown in one or more subsequent messages. Action None.

GDDS159W

Cause The Event Monitor has determined that the GDDR configuration state indicator, which isnormally the same at all configured sites, differs for the indicated sites. This messagegives the differing state indicators for the sites. Action None.

GDDS160I

Cause The Event Monitor has determined that the state indicate for the indicated site on thecurrent C-system is null. This is an abnormal condition. Action Determine why the state of the indicated site is unavailable. The state indicator isinitialized when the GDDR parameters are initially loaded, and are never deleted by GDDR.

GDDS161I

GDDR Event Monitor configured for sites site_list

GDDR Beginning Event Monitor state check

GDDR State deviation found between site-id and site-id

GDDR site-id state: state site-id state state

GDDR site-id state unavailable


Cause This message indicates the setting of the state indicator for the indicated site on thecurrent C-system. This will be compared with the state indicators for other sites on thecurrent C-system. Action None.

GDDS162I

Cause This message indicates that an event indicate is ON. The message is displayed once foreach event indicator set on during the current state check cycle. If the event indicator isrelated to a specific site, the site ID is given. The number in the message is the positionwithin the state indicator of the event. Action None.

GDDS163I

Cause The Event Monitor determined that no exception events of the indicated type were set ONat the indicate site for the current state check cycle. Action None.

GDDS164I

Cause The GDDR event monitor is displaying the current state. The exceptions are displayed ifthey are currently set. The form of the second line of the message is dependent onwhether or not the site being reported is the site at which this is running; if so, the firstform is used, otherwise, the second form is used. Action None.

GDDS167E

Cause A GDDR process required a value for the SRDF Host Component prefix and found no valuefor it in GDDR global variables. Action Use the Script JCL Parameters panel to provide a value in the SRDF Host Component

GDDR site-id state is state

GDDR nn event_name [at site-id]

GDDR Found no event_name exception events for site site-id

GDDR Event Monitor StateGDDR Site site-id (c-system-name) reports the following status:GDDR Site site-id (c-system-name) reports the following status:nn event-descr

GDDR Global verify failed, Host Component prefix is Null or notspecified.


●

●

●

●

prefix field for each C-system. Then perform a GDDR parameter set validation andactivation.

GDDS168E

Cause A GDDR process required a value for the SRDF Host Component prefix and found no valuefor it in GDDR global variables. Action Use the Script JCL Parameters panel to provide a value in the SRDF Host Componentprefix field for each C-system.

GDDS169E

Cause The GDDR Global Variable Backup module GDDRGVBB incurred an error due to a returncode from module GDDRENQ.The return code can be reported as:

8 : this is the return code from module GDDRCMD



other Action For other return codes, review the job log and SYSLOG for errors. Search theKnowledgebase on the EMC Online Support website for applicable solutions relating tothis message ID. If you cannot determine and correct the problem, contact the Dell EMCCustomer Support Center for assistance. Make sure you have all relevant jobdocumentation available.

GDDS201E

Cause The ConGroup owner system (SMF ID shown in the message) is not a C-system in theprimary region. Star HA is not functional. Action Move the ConGroup owner to the appropriate C-system.

GDDS202E

Cause The ConGroup owner, primary MSC server, or secondary MSC server (as indicated in themessage) is not the same on the C-systems in the primary region. Star HA is notfunctional. Action Take the necessary action to make the indicated item consistent in the primary region.

GDDR Global verify failed, Host Component prefix is Null or notspecified

ENQ for GDDRBKUP dsn=dsname failed - RC=rc

ConGroup owner (smfid) not in primary region

{ConGroup owner|MSC Primary Server|MSC Secondary Server}inconsistent in primary region


●

●

●

●

GDDS203E

Cause The ConGroup name reported by MSC does not match the ConGroup name which GDDRbelieves to be active. Star HA is not functional. Action Take the necessary action to ensure that GDDR is aware of the correct ConGroup.If the ConGroup name is GDDR ConGroup name, check the following:

SCF is active

EVM has the correct SCF connector DD

MSC is active (EVM will have issued message GDDS027E and set the

Unplanned.MSC event if MSC is not active)

ConGroup is active GDDS204W

Cause The MSC server is in an unexpected state (not PRIMARY or SECONDARY). The messageshows the current role. Star HA is not functional. Action Take the necessary action to correct the role of the MSC server on this system.

GDDS205E

Cause The current SRDF state is not Star with AutoSwap. Star HA is not functional. Action Take the necessary action to correct the SRDF state.

GDDS206I

Cause The current MSC server role of the C-system is displayed. Action None.

GDDS207E

Cause Neither DC1 nor DC2 are aware of the primary or secondary (as indicated) MSC server.Star HA is not functional. Action

Star ConGroup name name does not match GDDR ConGroup name gddr-name

Unexpected role for MSC server: {Primary|Secondary}

Star HA only supported with Star + AutoSwap

GDDR C-System c-system-name is {defined|running} as{primary|secondary} MSC Server

No {Primary|Secondary} MSC server


Take the necessary action to make the C-system at either DC1 or DC2 the primary orsecondary MSC server.

GDDS208E

Cause The current primary MSC server is not a C-system in the primary region. Star HA is notfunctional. Action Take the necessary action to make a C-system in the primary region the primary MSCserver.

GDDS209I

Cause The indicated action (Star HA Takeover or Verification of MSC-CG integration) is beingpostponed because a ConGroup transition is occurring. Star HA analysis will be suspended for two Event Monitor cycles to give time for thetransition to complete. After that time, Star HA analysis will resume. Action None.

GDDS210I

Cause A Star HA takeover is either in progress or will be initiated. Action None.

GDDS211I

Cause MSC is reporting an unexpected status. Action None.

GDDS212E

Cause MSC is reporting that an error has occurred. Star HA is not functional. Action Consult the SCF job logs, determine the cause of the problem, and take corrective action.

GDDS213I

Primary MSC Server SMF id not in primary region

action postponed due to ConGroup transient state

SRDF/Star HA Threshold exceeded

Unexpected MSC status: status

MSC error. Please see SCF joblog in primary region

Takeover is complete


Cause Star-HA MSC takeover is complete. Action None.

GDDS214I

Cause The primary MSC server is displaying its status. Action None.

GDDS215E

Cause The primary MSC server is not the ConGroup owner. This condition can be transient,during MSC takeover scripts. Action If this situation persists, investigate why this condition exists and remedy it by moving theprimary MSC server to the ConGroup owner site or by moving the ConGroup owner to theprimary MSC server site.

GDDS216E

Cause The MSC status indicates that the ConGroup connect flag is not set. Action Take appropriate action to correct the condition.

GDDS217E

Cause The MSC status indicates that the ConGroup stop listener is not registered. Action Take appropriate action to correct the condition.

GDDS218E

Cause The MSC status indicates that the ConGroup state listener is not registered. Action Review Mainframe Enablers logs (SCF, SRDF Host Component, ConGroup) to determinewhy MSC unregistered the ConGroup state listener.

GDDS219W

MSC Primary server status: status

Primary MSC Server is not the ConGroup owner

SRDF/Star ConGroup Connect flag not set

SRDF/Star ConGroup Stop listener not registered

SRDF/Star ConGroup State listener not registered


Cause The Star HA analysis has been skipped for this Event Monitor cycle because the CGDevent is on. Action If the situation persists, action may be necessary to remedy the CGD event.

GDDS220E

Cause The Star HA analysis has found the indicated SMF ID to have both the primary andsecondary MSC server function for the indicated MSC group. Action Verify SRDF Host Component and GDDR parameters defining the SRDF/Star HAconfiguration, ensure that proper MSC group names and weight factors are used in theprimary region.

GDDS221E

Cause A "split brain" condition has been detected between sites in the primary region, based onthe detection of the indicated event at one site but not at the other. If the condition isresolved, message GDDS222E will be issued. Action Submission of unplanned scripts by EVM is suppressed while this condition remains true.Investigate why one site has detected an event and the other has not (loss of connectivityis typically at the root of this problem) and take corrective action.

GDDS222E

Cause A "split brain" condition previously reported by message GDDS221E is no longer in effect.Note: This is an "E" level message so that it will appear in the EVM joblog and syslog. Action Submission of unplanned scripts by EVM (suppressed when this condition was detected)is now possible.

GDDS223E

Cause The GDDR Event Monitor found the indicated C-system to be primary/secondary for theSQAR A group, and to have the opposite role for the SQAR B group. Action This is usually a temporary situation while an MSC,TAKEOVER is being processed. If the

MSC and CG analysis skipped due to CGD event

smfid1 identified as both Primary and Secondary MSC Server for MSCgroup mscgrp

site-pair SPLIT BRAIN detected: Site site-id reports event butSite site-id does not.

site-pair SPLIT BRAIN condition cleared

C-system c-system-name is msc-role for SQARA group and msc-rolefor SQARB group


●

●

●

●

●

●

●

message persists, verify the SCF log for error messages relevant to TAKEOVERprocessing.

GDDS224E

Cause The GDDR Event Monitor found the SQAR A group to have a different primary MSCserver SMFID than the SQAR B group. This is usually a temporary situation while an MSC,TAKEOVER is being processed. Action If the message persists, verify the SCF log for error messages relevant to TAKEOVERprocessing.

GDDS225E

Cause The GDDR Event Monitor set the MSC and/or STR event, because when reviewing MSCconfiguration data, it found an unexpected condition.GDDR and/or Mainframe Enablers software setup and configuration errors are mostfrequently the cause of this. Examples are:

The ConGroup name defined to MSC Star does not match the one defined to GDDR.

The user defined a concurrent SRDF/Star configuration to GDDR, but a cascaded

SRDF/Star configuration in SRDF Host Component parameters.

ConGroup is disabled in a Star configuration.

A Star configuration is defined to GDDR, but MSC reports MSC mode.

In a pair of SQAR-associated groups, MSC has different associated group names

than those defined to GDDR.

In a pair of SQAR-associated groups, the SQARA and SQARB groups report a

different primary MSC server SMFID.

Another common cause is that the MSC group has not been initialized sufficiently, or

took an error during initialization. Action This message is intended to provide an explanation why the GDDR Event Monitor set theMSC and/or STR events. Review the reason provided in the message and take correctiveactions. If necessary, review SRDF Host Component and/or SCF job logs for additionalerror messages.

GDDS227E |GDDS227W

Cause The GDDR Event Monitor reported a delay in MSC software activity for the indicated MSCgroup. The reported MSC Post Timestamp is older than 2 times MSC_CYCLE_TARGETseconds. This message is issued as a W-level message when a GDDR script is running.This message indicates a problem in the MSC software as opposed to external factors, forexample, bandwidth constraints which could explain delays in MSC Cycle Switching and

Primary MSC Server SMFID is smf-id for SQARA group and smf-id forSQARB group

GDDR MSC analysis: text

GDDR MSC Activity for group mscgrp, delayed - YYYYMMDDHHMMSShh -count seconds ago


MSC SDDF Reset Activity.Note that during MSC state transitions, messages about unexpected TOD values can beignored, as long as they only occur for one to three EVM intervals. Action Review the SCF job log for additional error messages or abends in MSC.

GDDS228E | GDDS228W

Cause The GDDR Event Monitor reports a return to normal MSC software activity for theindicated MSC group.Note that during MSC state transitions, messages about unexpected TOD values can beignored, as long as they only occur for one to three EVM intervals. This message is issued as a W-level message when a GDDR script is running. Action None.

GDDS229E | GDDS229W

Cause The GDDR Event Monitor reports a delay in MSC cycle switching for the indicated MSCgroup. The reported MSC cycle TOD is older than x times MSC_CYCLE_TARGETseconds. The value of x is the EVM MSC Cycle Threshold, as specified on the SpecifyGDDR Tuning Values panel of the GDDR Parameter Wizard. This message is expected to occur during GDDR planned site or region swap scripts, andinforms you of the amount of time between the stop and restart of MSC protection. Notethat this message is issued as a W-level message when a GDDR script is running. Action Review the SCF job log for additional error messages signaling transfer or restore delaysfor the indicated MSC group, or a planned or unplanned SRDF/A drop. Check the EVM joblog for message GDDS227E signaling an MSC software issue which could explain the MSCcycle switch delay.If there are no apparent problems, and this message is unwanted, you may need to specifya higher value for the EVM MSC Cycle Threshold.

GDDS230E | GDDS230W

Cause The GDDR Event Monitor reports a return to normal for the MSC Cycle Switching for theindicated MSC group. Note that this message is issued as a W-level message when a GDDR script is running. Action None.

GDDS231E | GDDS231W

GDDR MSC Activity for group mscgrp, on time - YYYYMMDDHHMMSShh -count seconds ago

GDDR MSC Cycle Switch for group mscgrp delayed - YYYYMMDDHHMMSShh- count seconds ago

GDDR MSC Cycle Switch for group mscgrp, on time - YYYYMMDDHHMMSShh- count seconds ago

GDDR MSC SDDF Reset for group mscgrp delayed - YYYYMMDDHHMMSShh -


Cause The GDDR Event Monitor reports a delay in MSC SDDF Resets for the indicated MSCgroup. The reported MSC SDDF RESET TOD is more than the indicated number of MSCcycles ago. The value of count is the EVM MSC SDDF Cycle Threshold, as specified on theSpecify GDDR Tuning Values panel of the GDDR Parameter Wizard. This message signals that, although MSC cycle switching is still ongoing (at a normal orreduced rate), there is an additional issue affecting SDDF Reset activity. If SDDF Resetactivity is delayed, the SRDF/Star or SRDF/SQAR differential size is growing and this maycause longer than normal resynchronization after a CREATEPAIR/RESUMEPAIRdifferential operation.Note that this message is issued as a W-level message when a GDDR script is running. Action Review the SCF job log for additional error messages signaling errors in SDDF resets forthe indicated MSC group. Check the EVM job log for message GDDS227E signaling anMSC software issue which could explain the MSC SDDF reset delay.If there are no apparent problems, and this message is unwanted, it may be necessary tospecify a higher value for the EVM MSC SDDF Cycle Threshold.

GDDS232E

Cause The GDDR Event Monitor reports a return to normal for the MSC SDDF resets for theindicated MSC group, in terms of the number of MSC cycle switches between SDDFresets. Note that this message is issued as a W-level message when a GDDR script is running. Action None.

GDDS232W

Cause The GDDR Event Monitor reports a delay in MSC SDDF resets for the indicated MSCgroup when a GDDR script is running. The reported MSC SDDF RESET TOD is more than count MSC cycles ago. The value of count is the EVM MSC SDDF Cycle Threshold, asspecified on the Specify GDDR Tuning Values panel of the GDDR Parameter Wizard. This message signals that, although MSC cycle switching is still ongoing (at a normal orreduced rate), there is an additional issue affecting SDDF reset activity. If SDDF resetactivity is delayed, the SRDF/Star or SRDF/SQAR differential size is growing, and thismay cause longer than normal resynchronization after a CREATEPAIR/RESUMEPAIRDIFFERENTIAL operation. Action Review the SCF job log for additional error messages signaling errors in SDDF resets forthe indicated MSC group. Check the EVM job log for message GDDS227E signaling anMSC software issue which could explain the MSC SDDF reset delay.If there are no apparent problems, and this message is unwanted, it may be necessary tospecify a higher value for the EVM MSC SDDF Cycle Threshold.

GDDS233E | GDDS233W

count cycles ago

GDDR MSC SDDF Reset for group mscgrp on time - YYYYMMDDHHMMSShh -count cycles ago

GDDR MSC SDDF Reset for group mscgrp delayed - YYYYMMDDHHMMSShh -count cycles ago


Cause The GDDR Event Monitor reports a delay in MSC SDDF resets for the indicated MSCgroup. The reported MSC SDDF RESET TOD is more than count seconds ago. The valueof count is the EVM MSC SDDF Time Threshold, as specified on the Specify GDDR TuningValues panel of GDDR Parameter Wizard.This message is expected to occur during GDDR planned site or region swap scripts, andinforms the user of the amount of time that SDDF sessions are accumulating invalidtracks.If SDDF reset activity is delayed, the SRDF/Star or SRDF/SQAR differential size isgrowing, and this may cause longer than normal resynchronization after aCREATEPAIR/RESUMEPAIR DIFFERENTIAL operation.Note that this message is issued as a W-level message when a GDDR script is running. Action Review the SCF job log for additional error messages signaling errors in SDDF resets forthe indicated MSC group, transfer or restore delays for the indicated MSC group, or aplanned or unplanned SRDF/A drop. If MSC cycle switching is delayed, SDDF resets arealso delayed.Check the EVM job log for message GDDS227E signaling an MSC software issue whichcould explain the delay. If there are no apparent problems, and this message is unwanted, it may be necessary tospecify a higher value for the EVM MSC SDDF Time Threshold.

GDDS234E | GDDS234W

Cause The GDDR Event Monitor reports a return to normal for the MSC SDDF resets for theindicated MSC group, in terms of the elapsed time between SDDF resets. Note that this message is issued as a W-level message when a GDDR script is running. Action None.

GDDS235I

Cause The GDDR Event Monitor reports a change in an MSC Activity Monitor parameter (forexample, MSC Activity Monitor status, MSC Cycle Switch Monitor threshold, MSC SDDFReset Monitor cycle threshold, MSC SDDF Reset Monitor time threshold). Action None.

GDDS236E

Cause There is a discrepancy between the master C-system reported by the indicated site andthe master C-system reported by this site. If the master C-system conflict cannot beresolved automatically, the MST event is set. The event is cleared when the conflict is

GDDR MSC SDDF Reset for group mscgrp delayed - YYYYMMDDHHMMSShh -count seconds ago

GDDR MSC SDDF Reset for group mscgrp ontime - YYYYMMDDHHMMSShh -count seconds ago

GDDR MSC monitor changed from old-value to new-value

GDDR Master C-system conflict - other-site reports their-master-c,this site reports our-master-c


●

●

●

●

resolved. Action Where possible, the master C-system conflict is resolved automatically. If the MST eventis set, the conflict must be resolved manually, as follows:

On the GDDR Primary Options Menu, select option M (GDDR Setup and

Maintenance), then use option T(Transfer Master C-System) to transfer the master

C-system to the proper place.

Restart EVM and HBM on the non-master C-systems to retrieve the broadcast set of

GDDR global variables from the master. This can be done using the following

commands:

F GDDRMAIN,RESTART EVM

F GDDRMAIN,RESTART HBM GDDS237I

Cause There is a discrepancy between the master C-system reported by this site and the masterC-system reported by all of the other sites in the configuration. This site complies with therest, and EVM is restarted to retrieve the broadcast set of GDDR global variables,resolving the master C-system conflict. Action None.

GDDS250W

Cause The GDDR Event Monitor on a secondary MSC server has detected that MSC signals thepossible loss of the primary MSC server for the indicated MSC group. However, the GDDREvent Monitor has found the primary MSC server to be in an Active state, and has issuedthe MSC,TKRESET command on the secondary MSC server, to avoid unnecessarytakeover processing. Action Review the SCF log on the secondary and primary MSC servers for messages related tounexpected conditions in MSC software, or SRDF/A.If you do not want the GDDR Event monitor to perform TKRESET actions, you cansuppress this behavior by specifying N for the 'EVM MSC TKRESET processing' field onthe Specify GDDR Tuning Values panel (M;P;O;T).

GDDS251W

Cause The GDDR Event Monitor on a secondary MSC server has detected that SRDF/A sessionsfor the indicated MSC group are frozen as a result of a ConGroup trip, in a concurrentSRDF/Star with AutoSwap, or SRDF/SQAR configuration. If the primary MSC server isfound inactive, the GDDR Event monitor might proceed to perform MSC,THAWprocessing. Action

GDDR Automatically resolving master C-System conflict, EVM willrestart

GDDR Issued MSC,TKRESET command for MSC group mscgrp

GDDR detected frozen SRDF/A sessions for MSC group mscgrp


If the primary MSC server is in an active state, it is expected to perform the requiredTHAW processing and the message will no longer be issued.If the primary MSC server is not active, and the GDDR Event Monitor further finds thatthere is a ConGroup trip, and there is no split-brain situation, it will issue the MSC,THAWcommand on a secondary MSC server.If you do not want the GDDR Event Monitor to perform MSC,THAW actions, you cansuppress this behavior by specifying N for the 'EVM MSC THAW processing' field on theSpecify GDDR Tuning Values panel (M;P;O;T).

GDDS252I

Cause The GDDR Event Monitor on a secondary MSC server has detected that SRDF/A sessionsfor the indicated MSC group are frozen as a result of a ConGroup trip, in a concurrentSRDF/Star with AutoSwap, or SRDF/SQAR configuration. The GDDR Event Monitor hasreacted to this by issuing the MSC,THAW command to ensure continued SRDF/Areplication, with active SDDF sessions at the SRDF/A R2 site, and C-ahead indication. Action If you do not want the GDDR Event Monitor to perform THAW actions, you can suppressthis behavior by specifying N for the 'EVM MSC THAW processing' field on the 'SpecifyGDDR Tuning Values' panel (M;P;O;T).

GDDS253I

Cause The GDDR Event Monitor has reacted to an SRDF/A frozen condition with an MSC,THAWcommand. This message reports that MSC has accepted the command. Action Look for more messages reporting progress or completion of MSC,THAW processing:GDDS254I, GDDS255E, GDDS256I.

GDDS254I

Cause The GDDR Event Monitor has reacted to an SRDF/A frozen condition with an MSC,THAWcommand. This message reports that MSC,THAW processing is ongoing as planned. Action Look for more messages reporting completion of MSC,THAW processing: GDDS255E,GDDS256I.

GDDS255E

Cause The GDDR Event Monitor has reacted to an SRDF/A frozen condition with an MSC,THAWcommand. This message reports that MSC,THAW processing has encountered an error. Action Review the SCF log for error messages regarding MSC,THAW processing. If necessary,contact Dell EMC Customer Support.

GDDR MSC,THAW command issued for MC group mscgrp

GDDR MSC,THAW command accepted for MSC group mscgrp

GDDR MSC,THAW command in progress for MSC group mscgrp

GDDR MSC,THAW error for MSC group mscgrp


●

GDDS256I

Cause The GDDR Event Monitor has reacted to an SRDF/A frozen condition with an MSC,THAWcommand. This message reports that MSC,THAW processing has completed successfully.At this point the frozen SRDF/A sessions should be cycle switching again, the SDDFsessions at the SRDF/A R2-site should be active and an R2-side SRDF/A query shouldshow the C-ahead indicator. Action None.

GDDS258W

Cause The GDDR Event Monitor has reacted to an SRDF/A frozen condition with an MSC,THAWcommand. This message reports that MSC has not yet accepted the command. Action This should be a short-lived situation. The next GDDR Event Monitor cycle, MSC,THAWcommand processing should be underway, as reported by messages GDDS253I,GDDS254I, GDDS255E or GDDS256I. If the problem persists for more than a few GDDREvent Monitor cycles, review the SCF log for MSC messages regarding an MSC,THAWcommand rejection. If necessary, contact Dell EMC Support.

GDDS259W

Cause The GDDR Event Monitor has detected a condition to which it would have responded witheither an MSC,THAW or an MSC,TKRESET command. However, the user has suppressedthis behavior. Action Review the Specify GDDR Tuning Values panel (M;P;O;T). If you want to allowMSC,THAW and/or MSC,TKRESET actions by the GDDR Event Monitor, restore fields'EVM MSC TKRESET processing' and/or 'EVM MSC THAW processing' to their defaultvalue of Y.It is recommended to leave these values at their defaults, to avoid unnecessary takeoverprocessing or unnecessary SRDF/A drops respectively.

GDDS260I

Cause The GDDR Event Monitor reports that the first site has more recent data than the secondsite. This message is issued by EVM in the secondary or tertiary region, as part of theregional disaster detection logic, in configurations with more than one SRDF/A leg, likeSRDF/SQAR and SRDF/Star-A.This message is only issued when the following conditions are met:

All storage systems at both recovery sites are accessible.

GDDR MSC,THAW command completed for MSC group mscgrp

GDDR Waiting for MSC,THAW command for MSC group mscgrp to beaccepted

GDDR MSC command for MSC group mscgrp suppressed, user preference

GDDR Site site1 has more recent data than Site site2


● All SRDF groups within each site have the same SRDF/A and MSC state.Message GDDS265I provides additional information about data currency and SRDF groupstate at each potential recovery site. Action Use this to determine at which site you want to perform Regional Disaster Recovery, or todirect the GDDR recovery script to use KEEPR2 processing when running at the oppositerecovery site.

GDDS261E

Cause The GDDR Event Monitor has encountered an error trying to access one or more storagesystems at the indicated site. The site is excluded from data currency determination, andmessage GDDS260I will not be issued. Action Verify availability of gatekeeper devices and FICON channel connectivity from the sitewhere EVM runs to the indicated site. Verify GDDRPARM for configuration errors.Look for messages GDDS262E, GDDS263E or GDDS264E for additional details.

GDDS262E

Cause A path could not be determined from the local site to the indicated storage system at theindicated site. Action

GDDS263E

Cause The GDDR Event Monitor found an unexpected storage system serial number at the listedgatekeeper. Action Check the GDDRPARM file for configuration errors.

GDDS264E

Cause The GDDR Event Monitor found the indicated storage system at the listed siteinaccessible using the listed gatekeeper from the second listed site (where EVM runs).

GDDR Symmetrix access errors at site, site excluded

GDDR Unable to determine path from Site site1 to Symmetrix symm-serial at Site site2

Check the GDDRPARM file for configuration errors. Issue the F GDDRMAIN,GATEKcommand to view and validate all gatekeepers that are defined to GDDR at the site wherethe command is issued.

GDDR Found Symmetrix serial symm-serial1 using GateKeeper gk fromSite site. Expected serial symm-serial2

GDDR Symmetrix serial symm-serial at Site site1 is inaccessibleusing GateKeeper gk from Site site2


●

●

●

●

●

Action Verify that the indicated gatekeeper is accessible from the site where EVM runs. Checkthe GDDRPARM file for configuration errors.

GDDS265I

Cause The GDDR Event Monitor reports SRDF/A Cycle TOD for each SRDF group on the listedleg of the configuration. For each group, the R2-side storage system is listed, the SRDFgroup number, the Cycle TOD in yyyy/mm/dd hh:mm:ss format, and the SRDF groupstate.Possible SRDF group state values are as follows:

Active: SRDF/A is active in single session mode.

MSC-Act: SRDF/A is active with MSC.

IntReq: SRDF/A is under control of MSC and shows Host Intervention Required.

Inact-MSC: SRDF/A has dropped under control of MSC.

Inactive: SRDF/A has dropped in single-session mode. Action This message helps decide which site has most recent data in Regional Disaster scenarios.Expected SRDF group states in a real Regional Disaster scenario in a GDDR configurationare IntReq and Inact-MSC. MSC-Act should be a transient state in this situation. Inthese states, the reported timestamps are expected to be the same within each site andcan be used to determine which site has most recent data. Active or Inactive stateindicates that SRDF/A is not under control of MSC, and global consistency is notguaranteed in these cases. If the state is Active, then the SRDF/A cycle TOD is a movingtarget, changing with each SRDF/A cycle switch. The same is true for MSC-Act outside ofthe Regional Disaster scenario.In all cases where SRDF/A is seen in single session mode, Regional Disaster Recoveryshould not be attempted prior to manual inspection of the data.This is generally true in any case where message GDDS260I is not issued after theGDDS265I messages.

GDDS266E

Cause The GDDR Event Monitor has found some SRDF/A sessions active and other inactive atthe listed site. Data currency for the site will not be determined, and message GDDS260Iwill not be issued. Action See message GDDS265I for a detailed report of all SRDF/A sessions and follow theguidelines for that message.

GDDS267E

Cause The GDDR Event Monitor has found some SRDF/A sessions under control of MSC andothers in single-session mode. Data currency for the site will not be determined, and

GDDR SRDF/A Cycle TOD site1 <- site2GDDR Symmetrix RDFGroup Timestamp State GDDR symm-serial srdfgrptime status

GDDR Mixed SRDF/A State for Site site. Site excluded

GDDR Mixed MSC State for Site site. Site excluded


message GDDS260I will not be issued. Action See message GDDS265I for a detailed report of all SRDF/A sessions and follow theguidelines for that message.

GDDS268E

Cause The GDDR Event Monitor has detected that different SRDF/A sessions at the listed siteare inactive but show different SRDF/A cycle TOD values.GDDR Event Monitor will use the oldest value for a possible comparison with the otherrecovery site. Action See message GDDS265I for a detailed report of all SRDF/A sessions and follow theguidelines provided for that message.

GDDS903I

Cause The Event Monitor detected the indicated exception event. Action None.

GDDS904E

Cause The system on which the Event Monitor is running is associated with a site that is not inthe current GDDR configuration. The Event Monitor terminates. Action Ensure that the system on which the Event Monitor was started is the intended systemfor your configuration. Then verify that the site, associated with the system by means ofSite and System entries in the Define Managed Systems panel, is also associated with thesystem by means of a System Name entry in the Define C-Systems panel. Correct theproblem and reload the GDDR parameters. Then perform required tasks as described inthe GDDR Product Guide for your configuration.

GDDS998E

Cause A program error has occurred in a GDDR monitor program. The program name, error codeand program line number are given. If available, the program line itself is shown. Theprogram returns the error code to its caller. The caller determines the appropriate actionto taken, and issues indicative messages. Action

GDDR Different SRDF/A cycle TOD values at Site siteGDDR Oldest: time1GDDR Newest: time2GDDR Using oldest value for Site site

GDDR Exception event NCX for swap group swapgrp

GDDR Event Monitor running on a C-System not currently configured

GDDR gddr_program trapped an error. RC=error_code in lineline_no:[SOURCELINE(source_line)]


Review the job log and SYSLOG for errors. Search the Knowledgebase on the Dell EMCOnline Support site for applicable solutions relating to this message ID. If you cannotdetermine and correct the problem, contact the Dell EMC Customer Support Center forassistance. Make sure you have all relevant job documentation available.


CHAPTER 10 GDDR Tape Messages (GDDT) GDDT001E

Cause The parameter value shown is invalid. Processing has been terminated. Action Correct the parameter value and rerun the task.

GDDT002E

Cause A DLMAUT command failed. Processing has been terminated. Action Review the message log for DLm command messages. Correct the failure and resubmit theprocess.

GDDT010I

Cause The profile name shown is currently being verified for valid parameter values. Action None.

GDDT011I

Cause The profile name shown has passed parameter validation. Action None.

GDDT012E

Cause The indicated profile contains an invalid or undefined value as shown in text. Action Correct the offending value and rerun the task.

GDDT013E

Invalid parameter value specified expl - processing terminated

DLMAUT command command failed - processing terminated

Validating Profile profile

Profile profile passed parameter validation

Profile profile specifies an invalid text


Cause The group profile name references a Workload Management Profile (WMP) that containsinvalid parameter values. Action Refer to preceding messages for the WMP. Correct the invalid WMP parameter valuesand rerun validation.

GDDT014W

Cause The Tape Profile shown is either missing a description entry or has a description but noparameter member was found. Action Edit the Tape Profile to provide the missing description or parameters and rerun validation.

GDDT016W

Cause The profile name has a missing or invalid value for the parameter name shown. Action If the profile name will be used in scripts where the parameter is required, edit the tapeprofile to provide the missing parameters or correct invalid parameters and rerunvalidation.

GDDT017W

Cause One or more tape profiles have optional parameters that are missing or have invalid values. The parameters indicated are optional, depending on the intended use of the tape profile.For example, a warning may be issued that the snapshot suffix or source DLm DRTESTconfiguration was not specified. If the tape profile will not be used for Disaster Recoverytesting, this warning may be ignored. If the tape profile is ever used for a DisasterRecovery test the testing process will fail. Action See the preceding GDDT012W messages.

GDDT018E

Cause One or more tape profiles contained invalid parameter values. Action Refer to preceding messages. Correct the invalid parameters indicated an rerun validation.

GDDT019I

Group Profile group_profile references invalid Workload Profilemember_profile

Profile profile description

Profile profile is missing or specifies an invalid parameter-name

One or more Profiles have missing or invalid parameters

Profile validation failed


Cause All of the selected tape profiles have successfully passed parameter validation. Action None.

GDDT020W

Cause The source data for the Workload Management Profile is not currently located at the sitespecified. This profile has been removed from further processing. Action Correct the problem and retry.

GDDT021I

Cause The Workload Management Profile shown is included in this execution of the script orbatch utility. Action None.

GDDT025E

Cause None of the Workload Management Profiles specified have their replication source data atthe site specified. Processing terminates. Action Resubmit the process at the site where the primary source data is located.

GDDT026E

Cause A DLm processing function was called but the necessary RUN variables could not befound. Action Ensure the Load Profiles module (GDDDLCLP) ran successfully prior to the failing step.

GDDT030E

Cause The Workload Management Profile(s) indicated contain attributes that conflict with eachother. This may occur when a group profile specifies multiple individual WMPs where theindividual WMPs specify different DLm production configurations to activate. Action

All Profiles validated successfully

Profile profile is not primary at site-id - not processed

Profile profile is included in this execution

No Workload Management Profiles are currently primary at site-id

No Tape Profile RUN variables found. Processing terminated

Error - Mixed attribute are specified in Profile(s) profile


●

●

●

●

Review the attributes of the WMPs and proceed as follows:

Modify the individual WMPs to create a consistent group, or

Modify the group profile to include only compatible WMPs.Resubmit the process specifying the updated profile.

GDDT030W

Cause The Workload Management Profile(s) indicated contain attributes that conflict with eachother. For example, a group profile specifies multiple individual WMPs where the individualWMPs specify different values for the Force option when activating a productionconfiguration.The parameter indicated is ignored for all profiles included in the current execution. Action Review the attributes of the WMPs and proceed as follows:

Modify the individual WMPs to create a consistent group, or

Modify the group profile to include only compatible WMPs.Resubmit the process specifying the updated profile.

GDDT031I

Cause The Workload Management Profile indicates the current DLm command should not beissued for the workload it describes The relevant DLm command has not been generatedor issued and processing continues.. Action None.

GDDT040E

Cause A Workload Management Profile has been selected, but GDDR failed to allocate theTAPEPROF dataset identified in the message, which is the dataset defined on theTAPEPROF parameter for the current site in GDDRPARM. Action Verify that the correct TAPEPROF dataset is defined in GDDRPARM. Make sure thedataset exists and is cataloged on the current system.

GDDT043E

Cause The indicated NED could not be translated to a z/OS address on the indicated LPAR. Action -

GDDT050E

Warning - Mixed attribute are specified in Profile(s) profile

Command bypassed for Profile profile due to parameter values

Failed to allocate TAPEPROF Dataset dsname

Unable to resolve NED ned-id to a z/OS address on lpar-name


●

●

●

●

●

●

Cause The process was unable to find any RUN variables describing the Workload ManagementProfile (WMP) attributes. Action Check preceding messages for reasons the selected profile(s) may have been excludedfrom processing. Possible reasons a WMP may be excluded are:

The WMP specifies a DLm name that has not been defined.

The Workload source data is not at the site where the process was submitted.

The selected WMPs do not specify the activation of the same DLm configuration.Correct any issues indicated and resubmit the process.

GDDT059A

Cause The VTECFGSWAP command to activate or remove a DLm configuration requires theFORCE option to complete. Action Reply F to re-issue the VTECFGSWAP command one time with the FORCE option. ReplyC to continue without re-issuing the command.

GDDT060I

Cause The DLm tape devices for the Workload Management Profile are now in the desiredONLINE/OFFLINE state to the LPAR shown. Action None.

GDDT061W

Cause The tape device address or range of addresses failed to come OFFLINE on the LPARshown. Action This message is followed by WTOR message GDDR127A, which provides the followingoptions:

Continue the script leaving these devices in their current state

Terminate the script until the drives can be manually taken offline, at which time the

script may be restarted

Have the current script issue a VARY OFFLINE FORCE and continue processingReply to message GDDR127A.

GDDT062I

No Workload Profile RUN variables found. Processing terminated.

VTECFGSWAP requires FORCE option. Reply F to re-issue the swapwith FORCE, C to continue.

DLm tape devices are now state to LPAR lpar-name

Tape device(s) device_list have failed to come state on LPAR lpar-name


●

●

Cause GDDR is unable to bring a tape device, range of devices or SMS storage group into thedesired state (for example, online or offline) and is asking the console operator to do so atthis time. Action This message is followed by WTOR message GDDT063A, which provides the followingoptions:

Continue the script leaving these devices in their current state.

Terminate the script until the drives can be manually taken offline, at which time the

script may be restarted.Reply to message GDDT063A.

GDDT063A

Cause GDDR is unable to bring a tape device, range of devices or SMS storage group into thedesired state. Message GDDT062I has displayed the resource, desired state and system. Action Reply C to cause the script to continue with the resource in its current state, whether therequested operator action has been taken or not.Reply X to cause the script to end.The WTOR waits for a reply for 2 minutes. If no reply is received the script will continue.

GDDT064E

Cause GDDR is unable to convert the tape device Node Element Descriptor (NED) to thecorresponding z/OS device address on the indicated host system. This usually occurswhen all paths to the device are offline or the device is BOXed. Action Bring the device to the desired online/offline state and reply C to message GDDT063A tocontinue the script. Reply X to message GDDT063A to cause the script to end.

GDDT080E

Cause The DLm Health Check function is currently suspended. This normally occurs if there is asite swap or recovery in progress.The date and time Health Check function will automatically resume is given in yyyddd@hhmmssht format. Action After the date and time indicated in the message, resubmit the Health Check.

GDDT081E

Vary the following resource state on LPAR lpar-name

device-numbers

Reply C when ready to continue the script, X to end the script

Unable to resolve NED ned to a z/OS address on lpar-name

DLm Health Check is suspended until time - processing terminated

Health Check results for DLm name at site


Cause One or more of the DLm Health Check tests has failed for he DLm name at the site shown.This message can be up to 25 lines long. If more lines are needed, additional GDDT081Emessages will list the remaining errors. Action Correct the DLm issues indicated and rerun the Health Check.

GDDT081I

Cause The DLm Health Check tests have passed for the DLm name at the site shown Action None.

GDDT081W

Cause The DLm name at the site shown has one or more components in maintenance mode. Action If necessary, remove the listed components from maintenance mode and rerun the healthcheck.

GDDT085W

Cause The tape profile shown does not specify a value for the parameter indicated. Processingcontinues with the next profile, if any. Action Update the indicated tape profile to specify the missing parameter values and rerun HealthCheck.

GDDT086W

Cause The replication status of the tape library shown is in an abnormal state. Action Investigate the cause of the abnormal replication state and take corrective actions ifnecessary.

GDDT087I

Cause All tape libraries on the indicated DLm located at the site shown are replicatingsuccessfully.

Health Check results for DLm name at site

DLm name at site has the following components in Maintenance Mode

Profile profile has no parameter specified. Profile skipped.

Tapelib tape-library on DLm dlm-name shows replication status ofstatus

All tapelibs at dlm-name at site are replicating successfully


Action None.

GDDT090W

Cause A DLm command response contained a warning or informational message that may impactfuture script functionality. The DLm message text is displayed in the GDDT091W thatfollow. Action See GDDT091W messages to determine if any immediate action is required.

GDDT091W

Cause A DLm command response contained a warning or informational message that may impactfuture script functionality. This message echoes the DLm command response messagetext. Action Refer to the DLm User Guide to determine if any immediate action is required.

GDDT101I

Cause This progress message is issued periodically when a GDDR script step is waiting for theDLm tapelib replication to synchronize between sites. Once the percentage shown reaches90% or greater the GDDR script resumes processing. Action None.

GDDT200I

Cause The swap or recovery of the DLm tape environment has reached the point whereapplications may be started while clean up activities for the DLm at the former site areexecuting. Action None.

Warning - the following DLm message was detected:

message-text

n% of the tapelib data has been synchronized

GDDR Script Status*************************************************** Applications may be restarted at site ** while cleanup runs on the DLm at rcvysite ***************************************************


CHAPTER 11 GDDR Utility Messages (GDDU) GDDUBG0E

Cause The GDDR BCVGROUP validation utility has identified a problem in the content of theBCVGROUP dataset. Action Correct the problem and run the utility again.

GDDUBG1I

Cause The GDDR BCVGROUP validation utility has successfully validated the content of theBCVGROUP dataset. Action None.

GDDUBG2E

Cause The GDDR BCVGROUP validation utility was called in the context of a GDD2P01A (Test-IPL from BCVs) script where the user has indicated to use the BCVGROUP feature.After successful validation of BCVGROUP content, the utility will send the resultingPARMS.BCVGDEVS global variables to the remote site identified in the message. It willfirst delete then load these global variables. The utility only does this when it findsGDDRMAIN in good working order on the remote site. In such case, the BCV managementsteps in the script will be done on the remote site and PARMS.BCVGDEVS are required onthat site.This message is issued when a problem occurs while trying to perform these remote globalvariables updates. This can happen when GDDRMAIN on the remote site is unexpectedlyterminated after the utility has verified GDDRMAIN status. Action If possible, restart GDDRMAIN on the remote site. If GDDRMAIN cannot be restarted onthe remote site, resubmit the script. The utility will then only create thePARMS.BCVGDEVS variables locally and the script will run the BCV management stepslocally as well.

GDDUBG3I

GDDR BCVGROUP Validation error:GDDR text

GDDR BCVGROUP Validation completed successfully

GDDR BCVGROUP Utility failed to action PARMS.BCVGDEVS on sitesite-id

GDDR BCVGROUP Utility has successfully loaded PARMS.BCVGDEVS onsite site-id


Cause The GDDR BCVGROUP validation utility was called in the context of a GDD2P01A (Test-IPL from BCVs) script where the user has indicated to use the BCVGROUP feature. Aftersuccessful validation of BCVGROUP content, the utility has successfully created therequired PARMS.BCVGDEVS global variables on the remote site identified in the message. Action None.

GDDUBG4I

Cause The GDDR BCVGROUP validation utility lists the contents of the BCVGROUP dataset. Action None.

GDDUC01I

Cause This message is part of a CHECKUP report produced with the CHECKUP command. Formore information, see the description of the CHECKUP command in the GDDR ProductGuide for your configuration. Action None.

GDDUC02I

GDDR BCVGROUP Dataset Contents:GDDR text

Health check information----------------------------------------------------------------- Active events : active_events_list Expected events : expected_events_list Degraded mode : {Yes|No} Star-HA : {0|1} Consistency : {Yes|No} DLM abort : {0|1}-----------------------------------------------------------------

Format 1:

Command queue

----------------------------------------------------------------------

Status Owner Count Active Max

------ -------- ------ ------ ------

status jobname count active max

----------------------------------------------------------------------

Format 2:

Command queue

----------------------------------------------------------------------

Status Owner Count Active Max



GDDUC03I

------ -------- ------ ------ ------

status jobname count active max

Commands:

command

Act: {Y|N} Done: {Y|N} RC: rc Added: date time Script: job_name

Format 1:

System status

----------------------------------------------------------------------

Site: site System: sys Type: type [(master)] Subsys: subsys

IP: ip_address Port: port

Status: system_status Last comm: date time

Maint level: ver highest_ptf (latest_date) Compat level: compat

Licenses: licenses_list Config type: configuration_type

System events: system_level_events_list

---------------------------------------------------------------------

Format 2:

System status

----------------------------------------------------------------------

Site System Type Status Last communicated

---- -------- ---- ------------------------------- -----------------

site [*]sys type system_status date time

. . .

----------------------------------------------------------------------

* Master C-system

Format 3:

Site: site System: sys Type: type [(master)] Subsys: subsys

IP: ip_address Port: port



GDDUC10E

Status: system_status Last comm: date time

Maint level: ver highest_ptf (latest_date) Compat level: compat

Licenses: licenses_list Config type: configuration_type

System events: system_level_events_list

Main task: job_name (job_id) ASID asid

Subtask Description Act

------- ----------------- ---

COMM Communications {Y|N}

CONSOLE Console commands {Y|N}

GVT Global variable {Y|N}

EVM Event monitor {Y|N}

HBM Heartbeat monitor {Y|N}

MCSOPER MCSOPER console {Y|N}

MISC Miscellaneous {Y|N}

WORKMGR Work manager {Y|N}

Worker Description Min Max Act

------ ------------------- --- --- ---

GDDWCM Console message min max act

GDDWCO Command min max act

GDDWCX User msg automation min max act

GDDWDV Device min max act

GDDWGV Global variable min max act

GDDWST Status min max act

GDDWXH HMC min max act

GDDWXQ Command queue min max act

GDDWXR REXX min max act

---------------------------------------------------------------------


●

●

●

●

Cause One or more unexpected events were detected. These events are indicated with anasterisk in the list of 'Active events' in the preceding report (message ID GDDUC01I). Action Investigate and resolve the events indicated in the report, as appropriate. See the GDDRProduct Guide for information about specific events.

GDDUC11E

Cause Degraded mode is set due to one or more of the following conditions being met:

A C-system has a Missing Heartbeat event (MHB).

GDDRMAIN is not running on a C-system.

A GDDRMAIN subtask or worker is not running on a C-system.

A GDDRPARM (MPARM) inconsistency was detected. Action Investigate the cause of degraded mode and resolve as appropriate.

GDDUC12E

Cause A discrepancy in the GDDRPARM (MPARM) file was found between GDDR systems. Thiscauses degraded mode to be set. Action Use the F GDDRMAIN,MPARM command to display the GDDRPARM checksums for eachsystem, and resolve any discrepancies in the GDDRPARM files, as appropriate. The FGDDRMAIN,MPARM,CHECK command can be used force GDDRPARM resynchronizationacross all systems once the discrepancy has been resolved.

GDDUC13E

Cause The specified number of C-systems defined to GDDR are accessible but are in a degradedstate (i.e., one or more essential workers or subtasks are not active). Action Investigate and resolve the problem as appropriate.

GDDUC14E

Cause The specified number of P-systems defined to GDDR are accessible but are in a degradedstate (that is, one or more essential workers or subtasks are not active). Action Investigate and resolve the problem as appropriate.

count unexpected events detected

Degraded mode is set

GDDRPARM inconsistency detected

count C-systems are accessible but are in a degraded state

count P-systems are accessible but are in a degraded state


GDDUC15E

Cause A configuration mismatch was detected between two or more active C-systems in theGDDR-plex. Action If a GDDRPARM inconsistency was also detected, resolve any discrepancies in theGDDRPARM files, as appropriate. Otherwise, use the GDDR Parameter Wizard to correctthe configuration.

GDDUC16E

Cause A GDDR subsystem name mismatch was detected between two or more active systems inthe GDDR-plex. Action Ensure the GDD$xxxx DD DUMMY (where xxxx is the GDDR subsystem name) in theGDDRMAIN JCL is consistent across all systems in the GDDR-plex. Correct the system(s)that are in error, and restart GDDRMAIN.

GDDUC17E

Cause A compatibility level mismatch was detected between two or more active systems in theGDDR-plex. They are at a maintenance level that is incompatible with one another. Action Ensure the GDDRMAIN address space on each system is running with the correct libraries.Upgrade the down-level system(s), and restart GDDRMAIN, as appropriate.

GDDUC18E

Cause A GDDR version mismatch was detected between two or more active systems in theGDDR-plex. Action Ensure the GDDRMAIN address space on each system is running with the correct libraries.Upgrade the down-level system(s), and restart GDDRMAIN, as appropriate.

GDDUC19W

Cause A GDDR maintenance level mismatch was detected between two or more active systemsin the GDDR-plex. Action Ensure the GDDRMAIN address space on each system is running with the correct libraries.

Configuration mismatch detected

Subsystem name mismatch detected

Compatibility level mismatch detected

Version mismatch detected

Maintenance level mismatch detected


Upgrade the down-level system(s), and restart GDDRMAIN, as appropriate. GDDUC20W

Cause One or more active events were detected. These events are listed under 'Active events' inthe preceding report (message ID GDDUC01I). This may or may not indicate a problem,depending on the expected state of the configuration. Action Investigate and resolve the events listed in the report, as appropriate. See the GDDRProduct Guide for information about specific events.

GDDUEX0E

Cause Wrong parameters have been passed for the Expected Events Utility. This is a GDDRinternal code issue. Action Contact the Dell EMC Customer Support Center for assistance, and keep the job logavailable.

GDDUEX1W

Cause The Expected Events Utility was asked to stop expecting an event that was not expectedat the moment. Action Report this issue to Dell EMC Customer Support.

GDDUEX2W

Cause Cleanup of empty expected events list occurred. Action None.

GDDUEX3W

Cause Expected event list is empty. Action

count active events detected


No action was specified.●

No events were specified.●

Action is unavailable: action●

Event is unavailable: event●

Attempt to remove not expected event: event

No Expected Events found.

Expected Event List is empty.


None. GDDUEX4I

Cause Expected Events Utility reporting. Action None.

GDDUG00I

Cause This message ID is reserved for tracing and diagnostic messages. The message text isvariable. Action None.

GDDUG01E

Cause The specified storage system serial number is not in a valid format. The serial number mustbe 12 digits, with an optional dash after the 7th digit (i.e., nnnnnnnnnnnn,nnnnnnn-nnnnn). Action Correct the storage system serial number, and try again.

GDDUG02E

Cause SCF is not running, or the xxxx in your SCF$nnnn DD DUMMY does not match your SCFsubsystem name. Action Start SCF, or correct the nnnn in your SCF$nnnn DD DUMMY to match your SCFsubsystem name, and retry. The default SCF subsystem name is 'EMC', in which case theSCF$nnnn DD DUMMY is optional.

GDDUG03E

Cause The SymmAPI version is less than 7.6, while it should be 7.6 or later.

Expected Events were updated with: event-listor

Specified Events removed. New value: event-listor

Expected Events were cleaned successfully.or

Current Event list: event-list

message_text

Controller serial number symm-serial is invalid

SCF is not active

API version must be 7.6 or above


Action Upgrade Mainframe Enablers to version 7.6 or later and retry.

GDDUG04E

Cause GDDRMAIN is not active, or a GDD$nnnn DD DUMMY statement was specified in the JCLand nnnn does not match the subsystem name used by GDDRMAIN. Action Start GDDRMAIN, or correct the nnnn in your GDD$nnnn DD DUMMY statement to matchthe subsystem name used by GDDRMAIN, and retry. The default GDDR subsystem name is'GDDR', in which case the GDD$nnnn DD DUMMY statement is optional.

GDDUG05E

Cause No gatekeepers are defined to GDDR. Action Ensure gatekeepers are defined in the GDDRPARM file and that a parameter load has beendone, and retry.

GDDUG06E

Cause No GDDR gatekeepers were found matching the specified criteria. Action Ensure gatekeepers are defined to GDDR, or correct the site and/or controller filters, andretry.

GDDUG07E

Cause One or more inaccessible gatekeeper devices were found. Action Correct the issue with the device(s). See the Status of the device(s) in the body of thereport for more information.

GDDUG08E

Cause The Auto_UnBoX option was specified, but one or more devices could not be unboxed. Action The FoRCe option can be used to force unboxing of devices when it normally would not beallowed (for example, the device is online or pending offline). There is no guarantee adevice can be unboxed, but the usual validation will be bypassed. See the MVS SystemCommands manual for more information on correcting boxed conditions.

GDDRMAIN is not active for subsystem subsystem-name

No GDDR gatekeepers found

No matching GDDR gatekeepers found

count inaccessible gatekeeper devices found

count gatekeeper devices could not be unboxed


GDDUG09E

Cause The Auto_UnBoX option was specified, but one or more devices could not be unboxed, asGDDRMCMD is not APF-authorized. APF authorization is required to perform pathmanagement. Action APF-authorize GDDRMCMD and retry. GDDRMCMD must be added to the IKJTSOparameter file under AUTHPGM.

GDDUG10I

Cause This is a report header line indicating the command and options as interpreted byGDDRMCMD, including any default options. Action None.

GDDUG13I

Cause This is a report header line indicating the SCF version. Action None.

GDDUG14I

Cause This is a report header line indicating the SCF subsystem name, the default being 'EMC'. Action None.

GDDUG15I

Cause This is a report header line indicating the GDDR version. Action None.

GDDUG16I

Cause This is a report header line indicating the GDDR subsystem name, the default being

count gatekeeper devices could not be unboxed, not APF authorized

Command : command

SCF version : scf_version

SCF subsystem name : scf_subsystem_name

GDDR version : gddr_version

GDDR subsystem name : gddr_subsystem_name


'GDDR'. Action None.

GDDUG17I

Cause This is a report header line indicating the list of applied PTFs. Action None.

GDDUG18I

Cause This is a report header line indicating the site where GDDRMCMD is running. Action None.

GDDUG19I

Cause This is a report header line indicating the name of the system where GDDRMCMD isrunning. Action None.

GDDUG20I

Cause This is a report header line indicating the date and time when GDDRMCMD is run. Action None.

GDDUG21I

Cause This is a report header line indicating the active GDDR licenses. Action None.

GDDUG25W

Cause The specified number of GDDR-managed SRDF/A groups are in the Transmit Idle state.

GDDRMCMD PTFs applied : ptf_list

Running at site : site-id

Running on system : system-name

Date and time : date time

Licenses : licenses

count SRDF/A groups are in transmit idle status


Action Investigate and resolve the problem as appropriate.

GDDUG27I

Cause This message shows the ENQ report produced with the ENQ command. For moreinformation, see the description of the ENQ command in the GDDR Product Guide for yourconfiguration. Action None.

GDDUG28I

Cause This message shows the GDDR subsystem information. For more information, see thedescription of the SUBSYS command in the GDDR Product Guide for your configuration. Action None.

GDDUG29I

Cause

GDDR ENQs

-------------------------------------------------------------------

Resource name System Job name ASID Control Status

------------------------- -------- -------- ---- --------- ------

major_name.minor_name sysname jobname asid {Exclusive|Share}{Own|Wait}

. . .

-------------------------------------------------------------------

GDDR subsystem information

----------------------------------------------------------------------

Ssys Type Act Mul Com Maint level Config type Licenses

---- ---- --- --- --- -------------- --------------- ---------------

ssys {C|P}sys {Y|N} {Y|N} compat maint_lvl cfg_type licenses

. . .

----------------------------------------------------------------------

REGION limits and usage--------------------------------------------- Limit Allocated % Alloc ------- --------- ------- Above the line above_lim above_alc above_%_alc Below the line below_lim below_alc below_%_alc---------------------------------------------


This message shows the REGION report produced with the REGION command. For moreinformation, see the description of the REGION command in the GDDR Product Guide foryour configuration. Action None.

GDDUG30I

Cause This message displays GDDR license information. For more information, see thedescription of the LICENSE command in the GDDR Product Guide for your configuration. Action None.

GDDUG31I

Cause This message shows the SUMMARY report produced with the SUMMARY command. Formore information, see the description of the SUMMARY command in the GDDR ProductGuide for your configuration. Action None.

GDDUG32E

Cause This line is part of the body of the report. The indicated GDDR gatekeeper is notaccessible. Action Resolve the issue with the device. See the Status column for the reason the device is notaccessible. If the device is boxed, the Auto_UnBoX option may be used to unbox it.

GDDUG32I

License information--------------------------------------------- T Site System Licenses - ---- -------- --------------------------- type site system licenses [(rsn)] . . .---------------------------------------------

Summary information------------------------------------------------- System : system_name (desc) Site : site [(desc)] GDDR version : ver high_ptf (date) GDDR subsystem name : gddr_subsystem_name SCF version : ver (high_ptf) API version : ver (high_ptf) SCF subsystem name : scf_subsystem_name Licenses : licenses-------------------------------------------------

gatekeeper_ccuu site system_serial_number system_microcode_level status


Cause This message displays the GATEK report produced with the GATEK command. Forexplanation of fields, see the description of the GATEK command in the GDDR ProductGuide for your configuration. Action None.

GDDUG32W

Cause This line is part of the body of the report. The indicated GDDR gatekeeper is accessiblebut is online and/or allocated, which is not recommended. Action Ensure the device is no longer in use by any applications, and vary it offline to prevent anyfuture allocations. This should be done with caution.

GDDUG33I

Cause This message shows the MAINTENANCE COMPOSITE report produced with theMAINTENANCE command. For more information, see the description of theMAINTENANCE command in the GDDR Product Guide for your configuration. Action None.

GDDUG34I

Gatekeeper information------------------------------------------------- Site Controller Path Status ---- ------------- ------- ------------------- site serial# gk [.rag] path_status . . .-------------------------------------------------

gatekeeper_ccuu site system_serial_number system_microcode_level status

Module-level maintenance------------------------------------ Appl Date Ver Level ---- -------- --- ------- GDDR date ver hi_ptf Module Date Ver Level -------- -------- --- ------- module date ver hi_ptf . . .------------------------------------

Discovered topology-------------------------------------------------------------------- Site Controller uCode ___________Other side___________ ---- ------------- -------- RAG RAG Site Controller uCode --- --- ---- ------------- -------- site serial# ucode rag rag site serial# ucode


Cause This message shows the TOPOLOGY report produced with the TOPOLOGY command. Formore information, see the description of the TOPOLOGY command in the GDDR ProductGuide for your configuration. Action None.

GDDUG35I

Cause This message shows the SYSTEMS report produced with the SYSTEMS command. Formore information, see the description of the SYSTEMS command in the GDDR ProductGuide for your configuration. Action None.

GDDUG37I

Cause This message shows the CONFIG report produced with the CONFIG command. For moreinformation, see the description of the CONFIG command in the GDDR Product Guide foryour configuration. Action None.

GDDUG38I

. . .--------------------------------------------------------------------

System information-------------------------------------------------------- T Site System IP Address Port Status - ---- -------- ------------------------- ----- ------ t site [*]sys ip_address port status . . .--------------------------------------------------------* Master C-system

Configuration information ---------------------------------------------------------------------- Config type : configuration_type Config mode : configuration_mode GDDR-managed RDF groups: Site x (DCm) repl_type Site y (DCn) Typ Status ============ -------- ============ --- --------------- symmserial srdfgrp->srdfgrp symmserial {INT|EXT|DLM} srdfgrp_status . . . ----------------------------------------------------------------------

CSECT-level maintenance------------------------------------------------- Appl Date Ver Level ---- -------- --- ------- GDDR date ver hi_ptf


Cause This message shows the MAINTENANCE DETAIL report produced with theMAINTENANCE command. For more information, see the description of theMAINTENANCE command in the GDDR Product Guide for your configuration. Action None.

GDDUG39I

Cause This message shows the MAINTENANCE LOADMOD report produced with theMAINTENANCE command. For more information, see the description of theMAINTENANCE command in the GDDR Product Guide for your configuration. Action None.

GDDUG40I

Cause The Auto_UnBoX option was specified, and one or more devices were successfullyunboxed. Action None.

GDDUG41I

Cause This message indicates that a planned script is currently active. Action None.

Module Date Ver Level -------- -------- --- ------- module date ver hi_ptf

CSECT Date Time Project Level -------- -------- ----- ------- ------- csect date time appl ptf . . .-------------------------------------------------

Selected module maintenance----------------------------------------------- Module Date Ver Level -------- -------- --- ------- module date ver hi_ptf

CSECT Date Time Project Level -------- -------- ----- ------- ------- csect date time appl ptf . . .-----------------------------------------------

count gatekeeper devices successfully unboxed

Planned script script-name active


GDDUG42I

Cause This message indicates that an unplanned script is currently active. Action None.

GDDUG43E

Cause The specified number of GDDR-managed SRDF groups do not exist. Action Investigate and resolve the problem as appropriate.

GDDUG44E

Cause The specified number of GDDR-managed SRDF groups are offline. Action Investigate and resolve the problem as appropriate.

GDDUG45E

Cause The specified number of GDDR-managed SRDF groups indicate an incorrect Star/SQARmode. Action Investigate and resolve the problem as appropriate.

GDDUG46E

Cause The specified number of GDDR-managed SRDF groups indicate an incorrect cycle tagmode. Action Investigate and resolve the problem as appropriate.

GDDUG47E

Cause The specified number of C-systems defined to GDDR are inaccessible. Action Investigate and resolve the problem as appropriate.

Unplanned script script-name active

count RDF groups do not exist

count RDF groups are offline

count RDF groups indicate an incorrect mode

count RDF groups indicate an incorrect cycle tag mode

count C-systems are inaccessible


GDDUG48E

Cause The specified number of P-systems defined to GDDR are inaccessible. Action Investigate and resolve the problem as appropriate.

GDDUG49E

Cause A license mismatch was detected between one or more active GDDR systems. Action Ensure the GDDR License Feature Codes (LFCs) in the SCF initialization (SCFINI) file areconsistent on each system. If not, on the necessary system(s), correct the SCFINI file,issue F scfname,INI REFRESH to update the licenses, and retry.

GDDUG50A

Cause The Auto_UnBoX option was specified with the PRompt option, and the indicated GDDRgatekeeper device is boxed. Action Reply Yes to unbox the device, No to skip the device, Cancel to terminate GDDGATEK, orNOPRompt to suppress all subsequent prompts and unbox all devices.

GDDUG51I

Cause The Auto_UnBoX option was specified with the PRompt option. The indicated GDDRgatekeeper device is boxed. The operator replied Yes to the prompt, therefore GDDGATEKis attempting to unbox the device. Action None.

GDDUG52I

Cause The Auto_UnBoX option was specified with the PRompt option. One or more GDDRgatekeeper devices are boxed. The operator replied NOPRompt to the WTOR; therefore,GDDGATEK will suppress subsequent prompts and attempt to unbox all devices. Action None.

count P-systems are inaccessible

License mismatch detected

Unbox gatekeeper device ccuu on controller symm-serial at site-id?(Reply Yes, No, Cancel, or NOPRompt)

Operator replied Yes - Unboxing gatekeeper device ccuu oncontroller symm-serial at site-id

Operator replied NOPRompt - Unboxing all gatekeeper deviceswithout prompts


GDDUG53I

Cause The Auto_UnBoX option was specified with the PRompt option. The indicated GDDRgatekeeper device is boxed. The operator replied No to the prompt; therefore GDDGATEKwill not attempt to unbox the device. Action None.

GDDUG54I

Cause The Auto_UnBoX option was specified with the PRompt option. One or more GDDRgatekeeper devices are boxed. The operator replied Cancel to the prompt; thereforeprocessing will be terminated and subsequent devices will not be unboxed. Action None.

GDDUG55I

Cause GDDR maintenance information was registered successfully with SYR on one or morestorage systems defined to SCF, including the application name (GDDR), GDDR version,highest PTF number, latest build date, API version, and system name. Action None.

GDDUG56E

Cause No GDDR subsystems, either active or inactive, were found on the system where thecommand was run. The system may have been recently IPLed. Action Start at least one GDDRMAIN instance, if appropriate, and reissue the command.

GDDUG57E

Cause The SUBSYS command was issued, and no GDDR subsystems were found matching therequested criteria. Action Ensure at least one GDDRMAIN instance is active on that system, or adjust any filters(e.g.,ACTIVE), and reissue the command.

Operator replied No - Gatekeeper device ccuu on controller symm-serial at site-id not unboxed

Operator replied Cancel - Processing terminated

Registration successful

No GDDR subsystems found

No matching GDDR subsystems found


GDDUG58E

Cause An MSC group name is not defined to GDDR for the indicated site pair. Action Ensure MSC group names are defined in your GDDRPARM file (MPARM) as necessary foryour configuration. This is done using the MSCGROUP statement. For a 2-site SRDF/Aconfiguration, the definitions would look something like this:MSCGROUP DC1->DC3 GDDR MSCGRP1 MSCGROUP DC3->DC1 GDDR MSCGRP1

GDDUG59E

Cause The indicated SymmAPI call failed. Diagnostic information is provided for Dell EMC use. Action Contact Dell EMC Customer Support if the problem persists.

GDDUG60I

Cause This line bounds the top and bottom of a "flower box". Action None.

GDDUG61I

Cause This line is the body of a "flower box". It contains the GDDGATEK module eyecatcher,indicating the assembly date/time, GDDR version, and build (e.g., PTF number). Action None.

GDDUG62E

Cause The GDDR maintenance level could not be registered with SYR because SCF is not activeor no storage systems were found defined to SCF. Action Ensure SCF is active and at least one storage system is defined. Ensure the SCF$nnnn DDDUMMY in the JCL contains the correct SCF subsystem name, if applicable.

MSC group name not found for site pair DCn->DCm

api_function API call failed – R15 emcsai_rc RC emcrc RS emcrs RCXemcrcx CUU ccuu UCB@ ucbaddr Hoplist hoplist

******************************************************************

* <module_name>-<assembly_date>-<assembly_time>-GDDR<gddr_version>-<build> *

Registration failed because SCF is not active or no controllerswere found


GDDUG63E

Cause GDDRMCMD must be APF-authorized for the requested function. Action Ensure the library where GDDRMCMD resides is APF-authorized and GDDRMCMD isincluded in the IKJTSO parameter file under AUTHPGM.

GDDUG64E

Cause The GDDRPARM file could not be opened. Action Ensure the dataset specified on the GDDRPARM DD statement is accessible.

GDDUG65E

Cause The SCF subsystem name used by the address space where the command is running doesnot match the SCF subsystem name used by GDDRMAIN. Action Ensure the SCF$nnnn DD DUMMY in the JCL matches that in the GDDRMAIN JCL. Thedefault SCF subsystem name is 'EMC', in which case the SCF$nnnn DD DUMMY isoptional.

GDDUG66E

Cause No GDDR License Feature Codes (LFCs) were found in the SCF initialization (SCFINI) file. Action Update the SCFINI file to include at least one GDDR License Feature Code (LFC), issue F emcscf,INI REFRESH, then restart GDDRMAIN or issue F GDDRMAIN,PARM_REFRESH.

GDDUG67E

Cause Presence of GDDR license feature codes (LFCs) in the SCF initialization file could not bedetermined. Action Ensure that SCF has completed initialization or recycle SCF, and retry. Contact Dell EMCCustomer Support if the problem persists.

GDDUG68E

Not APF authorized

Open failed for GDDRPARM file

SCF subsystem name scf-subsystem-name does not match GDDRMAIN SCFsubsystem name gddrmain-scf-subsystem-name

No GDDR License Feature Codes (LFCs) found in SCFINI file

GDDR licenses could not be determined


Cause An unsupported GDDR Tape configuration was detected. Action Ensure a valid configuration is defined to GDDR.

GDDUG69W

Cause Action Ensure a valid configuration is defined to GDDR. If no configuration is expected to bedefined to GDDR at this time, this message can be ignored.

GDDUG70W

Cause One or more GDDR gatekeeper devices were found to be online. Action Ensure the devices are not in use by any applications, and vary the devices offline. Thisshould be done with caution.

GDDUG71W

Cause One or more GDDR gatekeeper devices were found to be allocated. Action Ensure the devices are no longer in use by any applications, and vary them offline toprevent any future allocations. This should be done with caution.

GDDUG72W

Cause The specified number of GDDR managed SRDF/A groups indicate site C ahead of site B. Action Investigate and resolve the problem as appropriate.

GDDUG73W

Cause The specified number of GDDR managed SRDF/A groups indicate intervention required. Action Investigate and resolve the problem as appropriate.

GDDUG74W

Unsupported GDDR Tape configuration

No configuration defined to GDDR

count online gatekeeper devices found

count allocated gatekeeper devices found

count SRDF/A groups indicate site C ahead of site B

count SRDF/A groups indicate intervention required


Cause The specified number of external SRDF groups indicate MSC active. Action Investigate and resolve the problem as appropriate.

GDDUG75E

Cause The level of the operating environment for the specified storage system is too low. Action Update the operating environment and/or hardware, if necessary and appropriate.

GDDUG76E

Cause The GQSCAN service failed with the indicated return and reason codes for the indicatedENQ major name. Action See the GQSCAN return and reason codes in the z/OS MVS Assembler ServicesReference manual for more information. Contact Dell EMC Customer Support if theproblem persists.

GDDUG77E

Cause The specified number of recovery groups indicate SRDF/A active. Action Investigate and resolve the problem as appropriate.

GDDUG78E

Cause The address of GDDR data space 2 could not be determined. Action Ensure GDDRMAIN is active and has completed initialization. If the issue persists, restartGDDRMAIN.

GDDUG79E

Cause The GDDR subsystem name could not be determined. Action Ensure a GDD$nnnn DD DUMMY statement is specified in the JCL, where nnnn matches

count external RDF groups indicate MSC active

Microcode level for controller symmserial is too low (level), mustbe at least 5x70

GQSCAN failed with RC rc RS rs for QNAME enq_major_name

count recovery groups indicate SRDF/A active

GDDR data space 2 is not available

GDDR subsystem name could not be determined


the GDDR subsystem name used by GDDRMAIN. GDDUG80E

Cause Both the SITE and ConTRoLler filters were specified. GDDR gatekeepers were found onthe specified storage system, but the storage system does not reside at the specified site. Action Remove the SITE and/or ConTRoLler filter, or change the SITE filter to the site where thespecified system resides, as indicated in the message.

GDDUG81E

Cause The Auto_UnBoX option was specified with the PRompt option, and one or more GDDRgatekeeper devices are boxed. A WTOR was issued, and an invalid response was received.Valid responses are Yes, No, Cancel, or NOPRompt. Action Reply Yes to unbox the device, No to skip the device, Cancel to terminate GDDGATEK, orNOPRompt to suppress all subsequent prompts and unbox all devices.

GDDUG82E

Cause One or more non-functional paths were found. Action Correct the issue with the path(s). See the Status of the path(s) in the body of the reportfor more information.

GDDUG83E

Cause No GDDR discovered storage systems were found. Action Ensure the GDDR-managed storage systems are correctly defined in the GDDRPARM file.

GDDUG84E

Cause No GDDR discovered storage systems were found matching the requested criteria. Action Adjust any filters (for example, SITE, CTRL) and reissue the command.

GDDUG85E

Controller storage-system-filter is at site, not site-filter

Invalid WTOR response: wtor_response

count non-functional paths found

No GDDR controllers found

No matching GDDR controllers found

No GDDR systems found


Cause No systems were found defined to GDDR. Action Ensure the GDDR C-systems and P-systems are correctly defined in the GDDRPARM file.

GDDUG86E

Cause No systems defined to GDDR were found matching the requested criteria. Action Adjust any filters (e.g., SITE) and reissue the command.

GDDUG87E

Cause An error occurred reading the specified global variable name. Action Contact Dell EMC Customer Support if the problem persists.

GDDUG88E

Cause A storage system with the indicated gatekeeper device was not found at the indicated site. Action Ensure the indicated gatekeeper device is defined correctly in the GDDRPARM file.

GDDUG89E

Cause An unsupported configuration was detected. Action Ensure a valid configuration is defined to GDDR.

GDDUG90E

Cause The requested command found one or more objects in an invalid state (RC 8), or a severeerror occurred causing GDDRMCMD to fail unexpectedly (RC 12). Action See preceding error message(s).

GDDUG90I

Cause

No matching GDDR systems found

Error reading GDDR global variable variable_name

Controller at site-id with gatekeeper device ccuu not found

Unsupported configuration (reason)

GDDRMCMD ended with RC {8|12}

GDDRMCMD ended with RC 0


The requested command completed successfully. Action None.

GDDUG90W

Cause The requested command found one or more objects in an unexpected state. Action See preceding warning message(s).

GDDUG91E

Cause The specified number of GDDR managed SRDF/A groups indicate SRDF/A not active. Action Investigate and resolve the problem as appropriate.

GDDUG92E

Cause The specified number of GDDR managed SRDF/A groups indicate MSC not active. Action Investigate and resolve the problem as appropriate.

GDDUG93E

Cause The specified number of GDDR managed SRDF/A groups indicate a delay in SRDF/A cycleswitching. Action Investigate and resolve the problem as appropriate.

GDDUG94E

Cause The specified number of GDDR managed SRDF/A groups indicate Star/SQAR recoverynot available. Action Investigate and resolve the problem as appropriate.

GDDUG95E

Cause

GDDRMCMD ended with RC 4

count SRDF/A groups indicate SRDF/A not active

count SRDF/A groups indicate MSC not active

count SRDF/A groups indicate a delay in cycle switching

count SRDF/A groups indicate recovery not available

count SRDF/A groups indicate remote inconsistent


The specified number of GDDR managed SRDF/A groups indicate remote inconsistent. Action Investigate and resolve the problem as appropriate.

GDDUG96E

Cause The specified number of GDDR-managed SRDF/A groups indicate no global consistency. Action Investigate and resolve the problem as appropriate.

GDDUG97E

Cause The specified number of SRDF/S groups indicate SRDF/A active. Action Investigate and resolve the problem as appropriate.

GDDUG98E

Cause A command was issued programmatically, and a result field was provided, but the resultfield is too small. Action Contact Dell EMC Customer Support if the problem persists.

GDDUG99E

Cause Internal error occurred. Message text is variable. Action Contact the Dell EMC Customer Support Center if the problem persists.

GDDUM011E

Cause The indicated site is not defined to GDDR. Action Ensure that the indicated site has a matching SITE statement in GDDRPARM and therewere no errors during GDDRMAIN initialization.

GDDUM01A

count SRDF/A groups indicate no global consistency

count SRDF/S groups indicate SRDF/A active

Result field must be at least n bytes

message-text

Site site-id is not defined to GDDR

Clear box info for site-id controller symmserial RDF groupsrdfgrp? (Reply Yes, No, Cancel, or NOPRompt)


Cause This is a WTOR issued for each eligible SRDF group when GDDMSCFX is run with theCLEAR and PROMPT options. The indicated SRDF group is eligible for clear. Action Reply Y (or YES) to clear storage system information for the indicated SRDF group. ReplyN (or NO) to bypass the indicated SRDF group. Reply C (or CANCEL) to terminateprocessing. Reply NOPR (or NOPROMPT) to clear storage system information for theindicated SRDF group and all remaining groups without further prompting.

GDDUM02I

Cause The operator replied Yes to WTOR GDDUM01A. Storage system information will becleared for the indicated SRDF group. Action None.

GDDUM03I

Cause The operator replied NOPRompt to WTOR GDDUM01A, GDDUM06A, or GDDUM50A. Allremaining SRDF groups will be processed without additional prompts. Action None.

GDDUM04I

Cause The operator replied No to WTOR GDDUM01A. Storage system information will not becleared for the indicated SRDF group. Action None.

GDDUM05I

Cause The operator replied Cancel to WTOR GDDUM01A, GDDUM06A, or GDDUM50A.Processing will be terminated. Action None.

GDDUM06A

Operator replied Yes - Clearing box info for site-id controllersymmserial RDF group srdfgrp

Operator replied NOPRompt - Proceeding without prompts

Operator replied No - Box info not cleared for site-id controllersymmserial RDF group srdfgrp

Operator replied Cancel - Processing terminated

Drop SRDF/A for site-id controller symmserial RDF group srdfgrp?(Reply Yes, No, Cancel, or NOPRompt)


Cause This is a WTOR issued for each eligible SRDF group when GDDMSCFX is run with theDROP and PROMPT options. The indicated SRDF group is eligible to be dropped. Action Reply Y (or YES) to drop SRDF/A for the indicated SRDF group. Reply N (or NO) tobypass the indicated SRDF group. Reply C (or CANCEL) to terminate processing. ReplyNOPR (or NOPROMPT) to drop SRDF/A for the indicated SRDF group and all remaininggroups without further prompting.

GDDUM07I

Cause The operator replied Yes to WTOR GDDUM06A. SRDF/A will be dropped for the indicatedSRDF group. Action None.

GDDUM08I

Cause The operator replied No to WTOR GDDUM06A. SRDF/A will not be dropped for theindicated SRDF group. Action None.

GDDUM09E

Cause An invalid response to WTOR GDDUM01A, GDDUM06A, GDDUM50A, GDDUM60A,GDDUM56A, or GDDUM58A was received. Action Reply to the WTOR with Yes, No, Cancel, or NOPRompt, as appropriate.

GDDUM10E

Cause The indicated storage system is not defined to GDDR. Action Ensure the indicated storage system has a matching SYMM statement in GDDRPARM andthere were no errors discovering that storage system during GDDRMAIN initialization.

GDDUM12E

Cause

Operator replied Yes - Dropping SRDF/A for site-id controllersymmserial RDF group srdfgrp

Operator replied No - SRDF/A not dropped for site-id controllersymmserial RDF group srdfgrp

Invalid WTOR response: response

Controller symmserial is not defined to GDDR

No scratch areas found for site {A|B|C|D}


No MSC scratch areas were found referencing the indicated site for the requested MSCgroup name. Action Ensure the requested MSC group name and starting storage system serial number werespecified correctly.

GDDUM13E

Cause No MSC scratch areas referencing the indicated MSC group were found on the specifiedstorage system. Action If GDDR is not available, ensure that the requested MSC group name and the serialnumber of the starting storage system were specified correctly. Contact Dell EMCCustomer Support if the problem persists.

GDDUM14E

Cause GDDR is not available, and the CONTROLLER parameter was not specified. If GDDR isnot available, a starting storage system serial number must be specified. Action Specify a starting storage system serial number via the CONTROLLER parameter, andresubmit the job. This storage system may be local or remote to the system whereGDDMSCFX is running.

GDDUM15E

Cause A SITE filter was specified that is not in a supported format. Action Correct the SITE filter specification following instructions in the GDDR Product Guide foryour configuration.

GDDUM16E

Cause No MSC scratch area was found matching the indicated MSC group for the indicatedSRDF group on the indicated storage system. This could be caused by stale storagesystem information. Action Ensure the requested MSC group name and starting storage system serial number werespecified correctly. If appropriate, run GDDMSCFX with the CLEAR option to clear anystale storage system information.

No scratch areas matching MSC group name mscgrp found oncontroller symmserial

Starting controller serial number not specified

Invalid SITE filter specified

No scratch area matching MSC group name mscgrp found for RDF groupsrdfgrp on controller symmserial


GDDUM17E

Cause The RESOLVE option was specified in combination with the DROP option. The RESOLVEphase was bypassed because an error occurred during the DROP phase. Action See preceding error messages.

GDDUM18E

Cause The CLEAR option was specified in combination with the DROP and/or RESOLVE options.The CLEAR phase was bypassed because an error occurred during the DROP or RESOLVEphase, as indicated. Action See preceding error messages.

GDDUM19E

Cause GDDR is not available, and the MSCGROUP parameter was not specified. If GDDR is not available, an MSC group name must be specified in order to identify theconfiguration. Action Specify an MSC group name via the MSCGROUP parameter, and resubmit the job.

GDDUM20I

Cause SRDF/A has been dropped for the indicated SRDF group. Action None.

GDDUM21I

Cause The drop phase was bypassed because no SRDF groups were found with SRDF/A active. Action None.

GDDUM22I

Cause

RESOLVE bypassed, as phase n (DROP) failed

CLEAR bypassed, as phase n ({DROP|RESOLVE}) failed

MSC group name not specified

SRDF/A dropped for site-id controller symmserial RDF group srdfgrp

Drop bypassed, no RDF groups found with SRDF/A active

Drop bypassed, no eligible RDF groups found


The drop phase was bypassed because no eligible SRDF groups were found. Action Rerun GDDMSCFX with the FORCE option to drop all groups unconditionally, ifappropriate.

GDDUM23I

Cause SRDF/A was not dropped for the indicated SRDF group, as SRDF/A is not active. Action None.

GDDUM25E

Cause No groups were dropped because one or more expected SRDF/S groups have SRDF/Aactive. Action Rerun GDDMSCFX with the FORCE option to drop all groups unconditionally, ifappropriate.

GDDUM26E

Cause No groups were dropped because one or more expected recovery groups have SRDF/Aactive. Action Rerun GDDMSCFX with the FORCE option to drop all groups unconditionally, ifappropriate.

GDDUM30I

Cause No stale storage system information was found, so cleanup was bypassed. Action Consider using the FORCE option (with SIMULATE on the first run) to clear storagesystem information for all SRDF groups in the configuration regardless of whether staleinformation was found.

GDDUM31E

Cause Clear could not be performed because one or more SRDF groups have SRDF/A active.

site controller symmserial RDF group srdfgrp is already in thedesired state

Drop is prohibited, as one or more expected SRDF/S groups haveSRDF/A active

Drop is prohibited, as one or more expected recovery groups haveSRDF/A active

Cleanup bypassed, no stale box information found

Clear is prohibited, as one or more RDF groups have SRDF/A active


Action If appropriate, run GDDMSCFX with the DROP option to drop SRDF/A. Note that usingthe DROP option will stop replication.

GDDUM32E

Cause Clear could not be performed, as one or more SRDF groups have the Host InterventionRequired flag set. Action If appropriate, run GDDMSCFX with the RESOLVE option to commit or discard theSRDF/A cycles and clear the Host Intervention Required flag.

GDDUM40I

Cause SRDF/A cycle resolution was bypassed because no SRDF groups were found with hostintervention required. Action None.

GDDUM41E

Cause The GDDMSCFX utility was run with the CONTROLLER parameter specified incombination with the RESOLVE option when GDDR was available. However, theCONTROLLER filter is not supported for RESOLVE because GDDMSCFX needs todiscover all SRDF groups in the MSC group. Action Remove the CONTROLLER filter and resubmit the job, if appropriate.

GDDUM42E

Cause SRDF/A cycle resolution could not be performed because one or more SRDF groups inthe requested MSC group have SRDF/A active. Action If appropriate, run GDDMSCFX with the DROP option to drop all SRDF/A groups.

GDDUM43E

Cause

Clear is prohibited, as one or more RDF groups have hostintervention required

Cycle resolution bypassed, no RDF groups found with hostintervention required

CONTROLLER filter is not supported for RESOLVE

Cycle resolution is prohibited, as one or more RDF groups haveSRDF/A active

Cycle resolution is prohibited, as one or more RDF groups have R1cleanup running


SRDF/A cycle resolution could not be performed because one or more SRDF groups inthe requested MSC group have R1 cleanup running. Action Wait for R1 cleanup to complete, and rerun the utility. Contact Dell EMC CustomerSupport if the condition persists.

GDDUM44E

Cause SRDF/A cycle resolution could not be performed because one or more SRDF groups inthe requested MSC group have R2 restore in progress. Action Wait for R2 restore to complete, and rerun the utility. Contact Dell EMC CustomerSupport if the condition persists.

GDDUM45E

Cause SRDF/A cycle resolution could not be performed because an error occurred querying oneor more SRDF groups. Action Contact Dell EMC Customer Support if the problem persists.

GDDUM46E

Cause The indicated Receive cycle tag is not within 1 of the indicated Apply cycle tag for theindicated MSC group. Therefore the Receive cycles cannot be resolved. This couldindicate a possible data consistency issue. Action Contact Dell EMC Customer Support.

GDDUM47E

Cause The Receive cycle tag matches the Apply cycle tag for the specified SRDF group,indicating that the Receive cycle has already been committed, but the Host InterventionRequired (HIR) flag is set for that group. This is an unexpected condition. Action Contact Dell EMC Customer Support.

GDDUM48E

Cycle resolution is prohibited, as one or more RDF groups have R2restore in progress

Cycle resolution is prohibited, as the required box information isnot accessible

Receive cycle cycle_tag is not within 1 of Apply cycle cycle_tagfor MSC group mscgrp

Receive cycle for symmserial/srdfgrp is already committed, but HIRis set


Cause The Receive cycle tag for the first SRDF group does not match the Receive cycle tag orApply cycle tag for the second SRDF group in the same MSC group. Therefore theReceive cycles cannot be resolved. This could indicate a possible data consistency issue. Action Contact Dell EMC Customer Support.

GDDUM49E

Cause The indicated cycle tag was found to be incomplete for some SRDF groups but alreadycommitted for other SRDF groups in the indicated MSC group. Therefore the Receivecycles cannot be resolved. This could indicate a possible data consistency issue. Action Contact Dell EMC Customer Support.

GDDUM50A

Cause This is a WTOR issued for each eligible SRDF group when GDDMSCFX is run with theRESOLVE and PROMPT options. The Receive cycle for the indicated SRDF group will becommitted. Action Reply Y (or YES) to commit the Receive cycle for the indicated SRDF group. Reply N (orNO) to bypass the indicated SRDF group. Reply C (or CANCEL) to terminate processing.Reply NOPR (or NOPROMPT) to commit the Receive cycle for the indicated SRDF groupand process all remaining groups without further prompts.

GDDUM51I

Cause The operator replied Yes to WTOR GDDUM50A. The Receive cycle will be committed forthe indicated SRDF group. Action None.

GDDUM52I

Cause The operator replied No to WTOR GDDUM50A. The Receive cycle will not be committedfor the indicated SRDF group. Action

Receive cycle for symmserial/srdfgrp does not match Receive cycleor Apply cycle for symmserial/srdfgrp

Receive cycle cycle_tag is incomplete for some RDF groups inmscgrp but has already been committed for others

Commit Receive cycle for site-id controller symmserial RDF groupsrdfgrp? (Reply Yes, No, Cancel, or NOPRompt)

Operator replied Yes - Committing Receive cycle for site-id controller symmserial RDF group srdfgrp

Operator replied No - Receive cycle not committed for site-id controller symmserial RDF group srdfgrp


None. GDDUM53A

Cause This is a WTOR issued for each eligible SRDF group when GDDMSCFX is run with theRESOLVE and PROMPT options. The Receive cycle for the indicated SRDF group will bediscarded. Action Reply Y (or YES) to discard the Receive cycle for the indicated SRDF group. Reply N (orNO) to bypass the indicated SRDF group. Reply C (or CANCEL) to terminate processing.Reply NOPR (or NOPROMPT) to discard the Receive cycle for the indicated SRDF groupand process all remaining groups without further prompts.

GDDUM54I

Cause The operator replied Yes to WTOR GDDUM50A. The Receive cycle will be discarded forthe indicated SRDF group. Action None.

GDDUM55I

Cause The operator replied No to WTOR GDDUM50A. The Receive cycle will not be discardedfor the indicated SRDF group. Action None.

GDDUM56A

Cause GDDMSCFX was run with the RESOLVE option, and one or more SRDF groups have R1cleanup in progress. Action Reply Y (or YES) to ignore R1 cleanup and continue processing (not recommended). ReplyN (or NO) to terminate processing.

GDDUM57I

Cause

Discard Receive cycle for site-id controller symmserial RDFgroup srdfgrp? (Reply Yes, No, Cancel, or NOPRompt)

Operator replied Yes - Discarding Receive cycle for site-id controller symmserial RDF group srdfgrp

Operator replied No - Receive cycle not discarded for site-id controller symmserial RDF group srdfgrp

R1 cleanup is in progress - Proceed with SRDF/A cycle resolution?(Reply Yes or No)

Operator replied Yes – R1 cleanup bypassed


The operator replied Yes to WTOR GDDUM56A. R1 cleanup is ignored, and processingcontinues. Action None.

GDDUM58A

Cause GDDMSCFX was run with the RESOLVE option, and one or more SRDF groups have R2restore in progress. Action Reply Y (or YES) to ignore R2 restore and continue processing (not recommended). ReplyN (or NO) to terminate processing.

GDDUM59I

Cause The operator replied Yes to WTOR GDDUM58A. R2 restore is ignored, and processingcontinues. Action None.

GDDUM60A

Cause GDDMSCFX was run with the RESOLVE option, and an error occurred processing anSRDF group. See messages in SYSPRINT for more information about the indicated error. Action Reply Y (or YES) to bypass the error and continue processing the remaining SRDF groups(not recommended). Reply N (or NO) to terminate processing.

GDDUM61I

Cause The operator replied Yes to WTOR GDDUM60A. This indicated error is bypassed, andprocessing continues. Action None.

GDDUM62I

Cause The operator replied No to WTOR GDDUM60A, GDDUM56A, or GDDUM58A. Processing

R2 restore is in progress - Proceed with SRDF/A cycle resolution?(Reply Yes or No)

Operator replied Yes – R2 restore bypassed

Bypass error error_description for site controller symmserial RDFgroup srdfgrp? (Reply Yes or No)

Operator replied Yes - Error error_description bypassed for site-id controller symmserial RDF group srdfgrp

Operator replied No – Processing terminated


is terminated. Action None.

GDDUM99E

Cause An internal error occurred. Action Contact Dell EMC Customer Support if the problem persists.

message-text


CHAPTER 12 GDDR User Exit Messages (GDDX) GDDX101I

Cause A workload stop/start exit is beginning execution. Action None.

GDDX102E

Cause The workload stop/start WTO was issued via the HMC, but an error occurred. The returncode is shown. The WTO will be attempted via other means (via a system console). Action None.

GDDX103I

Cause The workload stop/start WTO will be issued via the HMC using the IP address shown. Action None.

GDDX105E

Cause The workload stop/start WTOR was not responded to within the time limit. The workloadstop/start step ends with a non-zero return code. Action None.

GDDX106E

Cause The workload stop/start WTOR encountered an error. The return code is displayed. Theworkload stop/start step ends with a non-zero return code. Action None.

GDDR Starting gddr-function for System system-name.

HMC Command to system system-name failed, rc=rc

GDDR will use HMC IP address nnn.nnn.nnn.nnn

Confirmation WTOR timed out, exiting

Confirmation WTOR had an error (RC=rc)


GDDX108E

Cause The workload stop/start user exit encountered an error. The failing line number isdisplayed along with the return code of the failure. Action If the return code is one caused by an environmental factor, modify the environment andretry. Otherwise, contact the Dell EMC Customer Support Center for assistance.

GDDX191I

Cause Workload is to be started or stopped (as indicated). If acknowledgement is needed thatworkload has indeed started or stopped, a subsequent WTOR will be issued (seeGDDX192A/GDDX292A). If you would like this message to be forwarded to all productionsystems (it will occur on a C-System) so that automation can trigger some action on theproduction system, enable messages GDDX191I and GDDX291I in GDDRMAIN via theMSGS console command. Action None.

GDDX192A

Cause Workload is to be started or stopped as indicated. Action Reply (anything) when all workload has been started or stopped.

GDDX201I

Cause A workload stop/start exit is beginning execution. Action None.

GDDX202E

Cause The workload stop/start WTO was issued via the HMC, but an error occurred. The returncode is shown. The WTO will be attempted via other means (via a system console). Action None.

GDDX203I

GDDR pgm-name (system-name) Trapped an Error. RC=(rc) in linennnnn: primary-site-id

{Start|Stop} production workload on system-name

Reply when workload {Start|Stop} on all production systems

GDDR Starting gddr-function for System system-name.

HMC Command to system system-name failed, rc=rc


Cause The workload stop/start WTO will be issued via the HMC using the IP address shown. Action None.

GDDX205E

Cause The workload stop/start WTOR was not responded to within the time limit. The workloadstop/start step ends with a non-zero return code. Action None.

GDDX206E

Cause The workload stop/start WTOR encountered an error. The return code is displayed. Theworkload stop/start step ends with a non-zero return code. Action None.

GDDX208E

Cause The workload stop/start user exit encountered an error. The failing line number isdisplayed along with the return code of the failure. Action If the return code is one caused by an environmental factor, modify the environment andretry. Otherwise, contact the Dell EMC Customer Support Center for assistance.

GDDX209I

Cause The workload stop/start user exit has completed. The return code is displayed. Action None.

GDDX291I

Cause Workload is to be started or stopped (as indicated). If acknowledgement is needed thatworkload has indeed started or stopped, a subsequent WTOR will be issued (seeGDDX192A/GDDX292A). If you would like this message to be forwarded to all production

GDDR will use HMC IP address nnn.nnn.nnn.nnn

Confirmation WTOR timed out, exiting

Confirmation WTOR had an error (RC=rc)

GDDR pgm-name (system-name) Trapped an Error. RC=(rc) in linennnnn: primary-site-id

GDDR Completed gddr-function with RC=(rc).

{Start|Stop} production workload on system-name


systems (it will occur on a C-System) so that automation can trigger some action on theproduction system, enable messages GDDX191I and GDDX291I in GDDRMAIN via theMSGS console command. Action None.

GDDX292A

Cause Workload is to be started or stopped as indicated. Action Reply (anything) when all workload has been started or stopped.

Reply when workload {Start|Stop} on all production systems


CHAPTER 13 GDDR zDP Messages (GDDZ) GDDZD00I

Cause The specified VDG has changed its state as indicated in the message.Additionally, this message may report a group GDDR wanted to START, but was foundSTOPped because it reached the VDG cycle limit from its definition. This is treated as asuccessful activation. Action None.

GDDZD01W

Cause GDDR timed out while waiting for the specified VDGs to become PAUSEd, ACTIVE orinitialized. Action Consider increasing the MFEOPTS.VDG.PAUSE.TIMEOUT orMFEOPTS.VDG.RESUME.TIMEOUT value for paused/active error respectively beforererunning the script. If that does not address the problem, report this issue to Dell EMCCustomer Support.

GDDZD02I

Cause The specified VDG cannot be activated. Action None.

GDDZD03I

Cause


GDDR VDG vdg_name is now PAUSEd●

GDDR VDG vdg_name is now ACTIVE●

GDDR VDG vdg_name has STOPped due to Cycle limit●

GDDR VDG vdg_name has STOPped●

GDDR Timed out during wait for the following VDG to {becomepaused|become active|initialize}:vdg_name

GDDR Skip VDG vdg_name - already ACTIVEor

GDDR Skip VDG vdg_name - not defined on this zDP server

GDDR No action performed. Reason: reason


●

●

●

●

●

●

●

Either the call overrides do not request VDG PAUSE/RELDLOCK and/or RESUME/STARTactions, or they do request these actions, but the script did not perform them for theindicated reason. Reasons can be:

GDDR zDP Pause & RELDLOCK option not configured - The call

overrides to not request PAUSE/RELDLOCK actions. You can ignore this message if

you do not use zDP against GDDR-managed devices.

GDDR zDP Resume & Start option not configured - The call overrides

to not request START/RESUME actions. You can ignore this message if you do not

use zDP against GDDR-managed devices.

No script variables found for script-name - Contact Dell EMC

Customer Support and keep the complete job log available.

No sites affected by script script-name - This reason can be reported

for PAUSE/RELDLOCK actions, if the script has no steps requiring such actions. This

form of the message can be ignored.

No VDGs PAUSED by this script and no VDGs defined for START -

This reason can be reported for RESUME/START actions, if the script did not

perform any PAUSE or RELDLOCK actions and you have not defined any VDGs for

sites affected by the script on the GDDR Parameter Wizard "Define GDDR Managed

VDG Names" panel. This form of the message can be ignored unless you want GDDR

to always ensure some VDGs are made active at the end of affected scripts. In that

case, use the GDDR Parameter Wizard "Define GDDR Managed VDG Names" panel.

zDP Management not configured - This means that on the GDDR Parameter

Wizard "Define Configuration Features" panel the zDP Management option is not

selected for any site. In such case, message GDDZD03I can be avoided by not

selecting the Perform zDP PAUSE and RELDLOCK actions or the Perform zDP

RESUME and START actions options on the GDDR Parameter Wizard "Define

Default Call Overrides" panel.

zDP Management not configured for sites sites - This reason can

be reported for PAUSE/RELDLOCK actions, if a script is found to have steps which

could suffer from device locks caused by zDP at the listed sites, but GDDR is not

configured for zDP management at those sites. If you do not use zDP against GDDR

managed SRDF devices at the listed sites, you can ignore this message. If you have

active VDGs against GDDR managed SRDF devices at the listed sites, Dell EMC

recommends configuring GDDR for zDP management at those sites. Action Depending on the listed reason, further investigation may be warranted.

GDDZD04E

Cause The specified VDG encountered initialization error during start or stopped with non-zeroRC.

GDDR VDG vdg_name encountered an initialization erroror

GDDR VDG vdg_name has STOPped with non-zero RC


Action Report this issue to Dell EMC Customer Support.

GDDZD05W

Cause The specified VDG has stopped while GDDR waited for it to become active but zDPsuggests that this was a normal operation (i.e., a manually issued STOP command). Action Review the system and ResourcePak Base logs to find a reason why VGD has stopped. Ifthe reason for the VDG to become STOPped is not clear, report this issue to Dell EMCTechnical Support.

GDDZD06I

Cause zDP processing indicated in message was completed with RC specified. Action If RC > 0, the GDDZD08I message section will follow with details.

GDDZD07I

Cause VDG processing indicated in message was completed at the specified site. Following arethe processed VDG names. Action None.

GDDZD08I

Cause If GDDZD06I indicated a non-zero RC, this message lists forwarded warning/errormessages from the indicated zDP site. Action

GDDR VDG vdg_name has STOPped unexpectedly

GDDR Completed zDP PAUSE/RELDLOCK for Site dasd-site at Site zdp-site with RC=rcor

GDDR Completed zDP RESUME/START at Site zdp-site with RC=rc

GDDR {PAUSEd/RELDLOCKed | STARTEd/RESUMEd} [no] VDGs at Site site-id [:]GDDR vdg_name

GDDR ===> Warning/Error messages from zDP PAUSE/RELDLOCK for Sitedasd-site at Site zdp-site :...GDDR <=== Warning/Error messages endor

GDDR ===> Warning/Error messages from zDP RESUME/START at Sitezdp-site : ...GDDR <=== Warning/Error messages end


Consult messages listed inside this message for further details.


Documents

Dell EMC GDDR · The name of the SCF started task. job-id The job ID. jobname The 8-character name of the JCL job. lpar-name The 4-character name of the logical partition (LPAR)