emc mainframe enablers resourcepak base for z/os · pdf fileemc® mainframe enablers...

EMC® Mainframe EnablersResourcePak® Base for z/OSVersion 7.6

Product GuideREV 04

ResourcePak Base for z/OS Version 7.6 Product Guide2

Copyright © 2001-2015 EMC Corporation. All rights reserved. Published in the USA.

Published October, 2015

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

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.

CONTENTS

Preface

Revision History

Chapter 1 Overview

Mainframe Enablers and ResourcePak Base ................................................ 26Activating ResourcePak Base ................................................................ 26

Introduction to ResourcePak Base ............................................................... 26 ResourcePak Base features ......................................................................... 28

Cross-system communication ............................................................... 28Automatic notification of configuration changes to MFE applications .... 28Nondisruptive SymmAPI-MF refreshes ................................................... 28Capacity and DSE Spillover Time monitors............................................. 29SRDF/A monitor .................................................................................... 29SRDF/A Write Pacing monitor ................................................................ 29Controller naming ................................................................................. 30Group Name Services support ............................................................... 30Pool management ................................................................................. 30SRDF/AR resiliency................................................................................ 30SRDF/A multi-session consistency ........................................................ 30SWAP services ...................................................................................... 31Recovery services.................................................................................. 31SAF security .......................................................................................... 31Thin CKD space reclamation .................................................................. 31Thin gatekeeper support ....................................................................... 31VP Compression.................................................................................... 32

Fully Automated Storage Tiering (FAST)........................................................ 34What is FAST?........................................................................................ 34FAST Overview....................................................................................... 35FAST VP overview .................................................................................. 39

Federated Tiered Storage (FTS) .................................................................... 45eDisks................................................................................................... 46Geometry limited devices ...................................................................... 47

zBoost PAV Optimizer.................................................................................. 48

Chapter 2 Running EMCSCF

Initiation and termination commands ......................................................... 50Starting EMCSCF services ...................................................................... 50Stopping EMCSCF services .................................................................... 51

Implementing the EMCSCF started task ....................................................... 52 Additional datasets..................................................................................... 53

GRS considerations for use of the SCFLOG and SCFTRACE datasets ....... 53 EMCSCF termination utility .......................................................................... 55

Job step return codes ............................................................................ 55 Running multiple copies of EMCSCF ............................................................ 56

ResourcePak Base for z/OS Version 7.6 Product Guide 3

Contents

Chapter 3 Configuration File and Initialization Parameters

Creating a configuration file ........................................................................ 58 Sample SCFINI file....................................................................................... 59 Initialization parameters ............................................................................. 60

SCF.ASY.MONITOR................................................................................. 66SCF.ASY.POLL.INTERVAL ........................................................................ 66SCF.ASY.SECONDARY_DELAY................................................................. 66SCF.ASY.SMF.POLL ................................................................................ 67SCF.ASY.SMF.RECORD ........................................................................... 67SCF.ASY.USEREXIT................................................................................. 67SCF.CNTRL.EXCLUDE.LIST ...................................................................... 68SCF.CNTRL.INCLUDE.LIST ....................................................................... 68SCF.CSC.ACTIVE .................................................................................... 68SCF.CSC[.<cntrl#>|RMT].ACTIVEPOLL ....................................................... 69SCF.CSC[.<cntrl#>]. ATTNACTIVE.............................................................. 69SCF.CSC[.<cntrl#>].ATTNPATHGRP ........................................................... 70SCF.CSC[.<cntrl#>|RMT].EXPIRECYCLE ..................................................... 71SCF.CSC.GATEKEEPER.LIST .................................................................... 72SCF.CSC.GATEKEEPER.<cntrl#>.LIST ........................................................ 72SCF.CSC[.<cntrl#>|RMT].IDLEPOLL ........................................................... 73SCF.CSC.INSTANCE................................................................................ 74SCF.CSC[.<cntrl#>|RMT].MITPERIOD ........................................................ 75SCF.CSC.REFORMAT............................................................................... 76SCF.CSC[.<cntrl#>|RMT].SELTIMEOUT ...................................................... 76SCF.CSC[.<cntrl#>|RMT].VERBOSE ........................................................... 77SCF.DAS.ACTIVE .................................................................................... 78SCF.DEV.ATTR.HRO.INCLUDE.LIST .......................................................... 79SCF.DEV.ATTR.HRO.EXCLUDE.LIST.......................................................... 80SCF.DEV.EXCLUDE.LIST.......................................................................... 80SCF.DEV.INCLUDE.LIST .......................................................................... 81SCF.DEV.MULTSS=YES|NO..................................................................... 81SCF.DEV.OPTIMIZE.ENABLE.................................................................... 82SCF.DEV.OPTIMIZE.PAV ......................................................................... 82SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST ................................................... 83SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST.................................................... 83SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST .................................................. 84SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST ................................................. 84SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE ............................................. 85SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL ............................................ 85SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU .................................................. 86SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT............................................ 86SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX ........................................................ 87SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ ............................................... 87SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE.............................................. 88SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST .................................... 88SCF.DEV.OPTIMIZE.PAV.TRACK.MIN ....................................................... 89SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ .............................................. 89SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE ............................................. 90SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST ................................... 90SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST....................................... 91SCF.DEV.OPTIMIZE.SMF.RECID............................................................... 92SCF.DEV.OPTIMIZE.VERBOSE ................................................................. 92SCF.DEV.WAITINT................................................................................... 93SCF.DSE.LIST......................................................................................... 93SCF.DSE.xx.LIST .................................................................................... 93

4 ResourcePak Base for z/OS Version 7.6 Product Guide

Contents

SCF.DSE.<cntrl#>.LIST = ENAble | DISable............................................... 94SCF.DSE.<cntrl#>.LIST = GATEkeeper=ccuu ............................................ 94SCF.DSE.<cntrl#>.xx.LIST ........................................................................ 95SCF.DSE.<cntrl#>.poolname.xx.LIST........................................................ 95SCF.DSE.WARNING ................................................................................ 95SCF.DSE.MINOR..................................................................................... 96SCF.DSE.MAJOR..................................................................................... 96SCF.GATEKEEPER.LIST............................................................................ 96SCF.GATEKEEPER.<cntrl#>.LIST ............................................................... 97SCF.GNS.ACTIVE .................................................................................... 97SCF.GNS.WAITINT .................................................................................. 98SCF.INI.COMMAND.MAX ........................................................................ 98SCF.INI.CPFX.......................................................................................... 98SCF.INI.CPFX.DD .................................................................................... 99SCF.INI.SCOPE....................................................................................... 99SCF.LFC.LCODES.LIST .......................................................................... 100SCF.LOG.CYLINDER .............................................................................. 100SCF.LOG.DATACLAS ............................................................................. 101SCF.LOG.MGMTCLAS ........................................................................... 101SCF.LOG.RETAIN.COUNT ...................................................................... 101SCF.LOG.RETAIN.DAYS......................................................................... 102SCF.LOG.STORCLAS............................................................................. 102SCF.LOG.TRACKS.PRI ........................................................................... 102SCF.LOG.TRACKS.SEC .......................................................................... 103SCF.MSC.ADCOPY.ONDROP ................................................................. 103SCF.MSC.AUTO.RECOVER.RETRY .......................................................... 103SCF.MSC.CYCLE.TIME.WARN ................................................................ 104SCF.MSC.ENABLE ................................................................................ 104SCF.MSC.GTFUSR.RECID ...................................................................... 105SCF.MSC.GTFUSR.TRACE...................................................................... 105SCF.MSC.MAX.LOCK.WAIT.................................................................... 106SCF.MSC.PAVO.................................................................................... 106SCF.MSC.OVERWRITE........................................................................... 106SCF.MSC.SDDFQ.TODA ....................................................................... 107SCF.MSC.SDDFQ.TOMF ........................................................................ 107SCF.MSC.SDDFQ.TOOS ........................................................................ 108SCF.MSC.VERBOSE.............................................................................. 109SCF.PDVHC.WAITINT ............................................................................ 109SCF.REG.MAX.CONTROLLER.ERRORS.................................................... 109SCF.REG.MAX.ERRORS......................................................................... 110SCF.REG.WAITINT................................................................................. 110SCF.SDV.LIST....................................................................................... 110SCF.SDV.<cntrl#>.LIST .......................................................................... 111SCF.SDV.<cntrl#>.LIST = GATEkeeper=ccuu .......................................... 111SCF.SDV.xx.LIST .................................................................................. 112SCF.SDV.<cntrl#>.xx.LIST ...................................................................... 112SCF.SDV.<cntrl#>.poolname.xx.LIST ..................................................... 112SCF.SNAP.NOTIFY_POLLING ................................................................. 113SCF.SNAP.NOTIFY_POLLTIME ............................................................... 113SCF.SRV.GSM.ACTIVE .......................................................................... 113SCF.SRV.GSM.INTERVAL ...................................................................... 114SCF.SS.AUTO.RECOVER ....................................................................... 114SCF.SS.AUTO.RECOVER.ser#.rdfg#=option .......................................... 114SCF.SS.AUTO.RECOVER.BCV= BCV(startup_option,post_recovery_option) ............................................... 115


Contents

SCF.SS.AUTO.RECOVER.BCV.ser#.rdfg#=BCV(startup_option,post_recovery_option) ............................................... 116SCF.SS.AUTO.RECOVER.ITRK=itrk......................................................... 116SCF.SS.AUTO.RECOVER.ITRK.ser#=itrk................................................. 117SCF.SS.AUTO.RECOVER.JOBNAME=jobname........................................ 117SCF.SS.AUTO.RECOVER.JOBNAME.ser#=jobname ................................ 118SCF.SS.AUTO.RECOVER.LPAR=id ......................................................... 118SCF.SS.AUTO.RECOVER.MINDIR=##..................................................... 119SCF.SS.AUTO.RECOVER.MINDIR.ser#=## ............................................. 119SCF.SS.AUTO.RECOVER.PREFIX=hccpfx................................................ 120SCF.SS.AUTO.RECOVER.PROC=procname ............................................ 120SCF.THN.LIST....................................................................................... 121SCF.THN.<cntrl#>.LIST .......................................................................... 121SCF.THN.<cntrl#>.LIST = GATEkeeper=ccuu .......................................... 122SCF.THN.xx.LIST .................................................................................. 122SCF.THN.<cntrl#>.xx.LIST ...................................................................... 122SCF.THN.<cntrl#>.poolname.xx.LIST...................................................... 123SCF.TRACE.COMPRESS ........................................................................ 123SCF.TRACE.CYLINDER........................................................................... 123SCF.TRACE.DATACLAS.......................................................................... 124SCF.TRACE.FLUSH.AT ........................................................................... 124SCF.TRACE.MEGS (default) .................................................................. 124SCF.TRACE.MGMTCLAS ........................................................................ 125SCF.TRACE.RETAIN.COUNT ................................................................... 125SCF.TRACE.RETAIN.DAYS...................................................................... 125SCF.TRACE.STORCLAS.......................................................................... 126SCF.TRACE.TRACKS.PRI ........................................................................ 126SCF.TRACE.TRACKS.SEC....................................................................... 126SCF.TRU.DEBUG................................................................................... 127SCF.TRU.DEV.EXCLUDE.LIST ................................................................. 127SCF.TRU.DEV.INCLUDE.LIST ................................................................. 127SCF.TRU.ENABLE ................................................................................. 128SCF.TRU.RECLAIM.DSFACTOR............................................................... 128SCF.TRU.RECLAIM.DSPREFIX ................................................................ 128SCF.TRU.RECLAIM.METHOD ................................................................. 129SCF.TRU.RECLAIM.PGMNAME............................................................... 129SCF.TRU.RECLAIM.POST.TYPE .............................................................. 130SCF.TRU.SCRATCH.POST.TYPE.............................................................. 130SCF.TRU.RECLAIM.POST.PCT ................................................................ 130SCF.TRU.SCRATCH.POST.PCT ............................................................... 130SCF.TRU.RECLAIM.POST.MIN................................................................ 130SCF.TRU.SCRATCH.POST.MIN............................................................... 130SCF.TRU.RECLAIM.POST.MAX............................................................... 130SCF.TRU.SCRATCH.POST.MAX .............................................................. 130SCF.TRU.RECLAIM.SCRATCH.WAIT ........................................................ 131SCF.TRU.RECLAIM.STCNAME ................................................................ 131SCF.TRU.RECLAIM.STRESS.MONITOR ................................................... 132SCF.TRU.RECLAIM.STRESS.WAIT........................................................... 132SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT............................................... 132SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT .................................................. 133SCF.TRU.RECLAIM.SYSVTOC.WAIT ........................................................ 133SCF.TRU.RECLAIM.TIMELIMIT.LIST ........................................................ 134SCF.TRU.RECLAIM.TASK.LIMIT .............................................................. 134SCF.TRU.SCAN.PGMNAME.................................................................... 134SCF.TRU.SCAN.STCNAME..................................................................... 135


Contents

SCF.TRU.SCAN.TASK.LIMIT ................................................................... 135SCF.TRU.SCRATCH.RECLAIM................................................................. 135SCF.TRU.THICKR1 ................................................................................ 136SCF.WORK.HLQ.................................................................................... 136SCF.WORK.UNIT................................................................................... 137SCF.WORK.VOLSER.............................................................................. 137SCF.WPA.EXCLUDE.CNTRL.................................................................... 137SCF.WPA.INCLUDE.CNTRL .................................................................... 138SCF.WPA.MONITOR.............................................................................. 139SCF.WPA.MSGLEVEL ............................................................................ 139SCF.WPA.POLL.INTERVAL ..................................................................... 139SCF.WPA.SMF...................................................................................... 140SCF.WPA.SMF.FILTER ........................................................................... 140SCF.WPA.SMF.RECORD ........................................................................ 141SCF.WPA.STYPES................................................................................. 141

Chapter 4 Command Reference

Command syntax and conventions............................................................ 144Syntax conventions............................................................................. 144

Customer tasks and command types......................................................... 145 Initialization commands............................................................................ 147

INI,REFRESH ........................................................................................ 147INI,RELOAD ......................................................................................... 147INI,SHUTDOWN ................................................................................... 148

eLicensing management commands.......................................................... 149ELM,LIST,CONTROLLER ........................................................................ 149ELM,QUERY,CONTROLLER .................................................................... 152

Cross-system communication commands.................................................. 154CSC,DISPLAY,HOSTS ........................................................................... 154CSC,DISPLAY,LISTENER........................................................................ 158CSC,REFRESH ...................................................................................... 160

Device commands..................................................................................... 161DEV,CH,CNTRL..................................................................................... 161DEV,DISPLAY ....................................................................................... 161DEV,REFRESH ...................................................................................... 171DEV,RESCAN ....................................................................................... 172DEV,STATUS ........................................................................................ 172DEV,UNPIN .......................................................................................... 173

zBoost PAV Optimizer commands.............................................................. 175Syntax conventions............................................................................. 175DEV,OPTIMIZE ENABLE ........................................................................ 175DEV,OPTIMIZE DISABLE ....................................................................... 175DEV,OPTIMIZE DISPLAY CONSISTENCY ................................................. 175DEV,OPTIMIZE DISPLAY DEVICE............................................................ 176DEV,OPTIMIZE DISPLAY EVENTS........................................................... 177DEV,OPTIMIZE DISPLAY SSID ............................................................... 178DEV,OPTIMIZE DISPLAY SUMMARY....................................................... 179DEV,OPTIMIZE LOG EVENTS ................................................................. 179DEV,OPTIMIZE RESET ........................................................................... 180DEV,OPTIMIZE RESUME ....................................................................... 180DEV,OPTIMIZE SUSPEND...................................................................... 181

Group Name Services commands.............................................................. 182GNS,FORMAT....................................................................................... 182GNS,LIST ............................................................................................. 182


Contents

GNS,REFRESH...................................................................................... 184GNS,REVERT........................................................................................ 184

General Pool Management commands ...................................................... 185GPM pool commands .......................................................................... 185GPM device commands ....................................................................... 186ADD .................................................................................................... 188ALLOCATE............................................................................................ 192BIND ................................................................................................... 196COMPRESS.......................................................................................... 201CREATE................................................................................................ 206DECOMPRESS...................................................................................... 210DELETE................................................................................................ 214DISABLE .............................................................................................. 216DISPLAY .............................................................................................. 220DRAIN ................................................................................................. 229ENABLE ............................................................................................... 233HALTTASK............................................................................................ 236HDRAIN ............................................................................................... 240MOVE.................................................................................................. 244PERSIST OFF ........................................................................................ 249POOLATTR ........................................................................................... 253QUERY {parameter}.............................................................................. 259QUERY display field descriptions......................................................... 270QUERY display examples..................................................................... 275REBALANCE ......................................................................................... 285REBIND ............................................................................................... 289REMOVE.............................................................................................. 293RENAME .............................................................................................. 296UNBIND............................................................................................... 299USR_NRDY .......................................................................................... 303USR_RDY............................................................................................. 306

Recovery services commands.................................................................... 309REC,QUERYDEVICELOCK ...................................................................... 309REC,RELEASEDEVICELOCK.................................................................... 310

SRDF/AR: Symmetrix Automated Replication commands ........................... 311SAR,PAUSE.......................................................................................... 311SAR,START .......................................................................................... 312SAR,RESTART....................................................................................... 312SAR,STOP............................................................................................ 312

SRV SYSBUSY commands.......................................................................... 314SRV,SYSBUSY,HELP............................................................................. 314SRV,SYSBUSY,DISPLAY........................................................................ 314SRV,SYSBUSY,DECREMENT.................................................................. 314SRV.SYSBUSY,RESET ........................................................................... 315

SRDF/A Multi-Session Consistency commands .......................................... 316MSC,ADDDEV ...................................................................................... 316MSC,DEACT ......................................................................................... 317MSC,DEACTREFRESH ........................................................................... 318MSC,DEACTRESTART............................................................................ 320MSC,DEACTRESTARTTOSEC.................................................................. 321MSC,DEACTRESTARTTOZERO ............................................................... 322MSC,DELDEV ....................................................................................... 323MSC,DISABLE ...................................................................................... 324MSC,DISPLAY ...................................................................................... 325MSC,ENABLE ....................................................................................... 326


Contents

MSC,PENDDROP.................................................................................. 326MSC,RECOVER..................................................................................... 329MSC,REFRESH ..................................................................................... 329MSC,RESTART...................................................................................... 331MSC,RESTARTTOSEC............................................................................ 332MSC,RESTARTTOZERO ......................................................................... 333MSC,TAKEOVER ................................................................................... 333MSC,VERBOSE .................................................................................... 334

SRDF/A Monitor operator commands ........................................................ 336ASY,DISABLE ....................................................................................... 336ASY,DISPLAY ....................................................................................... 336ASY,ENABLE ........................................................................................ 337ASY,REFRESH ...................................................................................... 337ASY,SSAR,DISABLE.............................................................................. 338ASY,SSAR,ENABLE............................................................................... 338ASY,RECOVER,SRDFA........................................................................... 338

DSE Monitor operator commands .............................................................. 339DSE,DISABLE....................................................................................... 339DSE,DISPLAY ....................................................................................... 340DSE,ENABLE........................................................................................ 340DSE,REFRESH ...................................................................................... 341

SDV Monitor operator commands.............................................................. 342SDV,DISABLE....................................................................................... 342SDV,DISPLAY....................................................................................... 342SDV,ENABLE........................................................................................ 343SDV,REFRESH ...................................................................................... 344

THN Monitor operator commands.............................................................. 345THN,DISABLE....................................................................................... 345THN,DISPLAY....................................................................................... 345THN,ENABLE........................................................................................ 346THN,REFRESH ...................................................................................... 347

TRU monitor operator commands .............................................................. 348TRU,HELP ............................................................................................ 348TRU,DISPLAY ....................................................................................... 348TRU, DISPLAY, DEVICE ......................................................................... 349TRU,HOLD ........................................................................................... 350TRU,RECLAIM....................................................................................... 350TRU,REFRESH ...................................................................................... 351TRU,RELEASE....................................................................................... 351TRU,SCAN............................................................................................ 351TRU,START........................................................................................... 352TRU,STOP ............................................................................................ 353

Chapter 5 Naming Controllers and validating paths

Overview................................................................................................... 356 Defining a controller name ........................................................................ 356

ESFCTLNM JCL ..................................................................................... 356 Displaying the controller name.................................................................. 357 Validating paths to a controller.................................................................. 357

ESFCHNU1 Input cards ........................................................................ 357ESFCHNU1 JCL ..................................................................................... 357ESFCHNU1 RETURN CODES .................................................................. 358


Contents

Chapter 6 Using the Group Name Services Facility

Overview................................................................................................... 360Before using GNS ................................................................................ 360

GNS group types ....................................................................................... 361 EMCGROUP JCL.......................................................................................... 362 GNS batch commands reference................................................................ 363

Command overview............................................................................. 363Batch syntax usage ............................................................................. 364DEFINE COMPLEMENT.......................................................................... 364DEFINE GROUP .................................................................................... 365DEFINE ENTERPRISE [RDF1|RDF2] GROUP.............................................. 370DEFINE GROUP FOR GCOPYBCV............................................................ 371DEFINE GROUP FOR SARPOOL .............................................................. 372DELETE GROUP .................................................................................... 372DISPLAY GROUP .................................................................................. 372LIST GROUP......................................................................................... 373REMOVE FROM GROUP ........................................................................ 373RENAME GROUP .................................................................................. 374

Working with groups ................................................................................. 375Defining groups................................................................................... 375Displaying SRDF groups....................................................................... 379Displaying groups ............................................................................... 380Listing groups ..................................................................................... 381Deleting groups................................................................................... 381Renaming groups ................................................................................ 382Defining SRDF/AR device replacement pools ....................................... 382

GNS reason codes..................................................................................... 384

Chapter 7 Managing Devices and Pools

Configuring Virtual Provisioning ................................................................ 386 Managing devices in pool storage ............................................................. 386

Planning for pool device use ............................................................... 387Pool Device Geometry ......................................................................... 388SRDF/A DSE Pools ............................................................................... 388Limitations.......................................................................................... 388

General Pool Management commands ...................................................... 390GPM pool commands .......................................................................... 390GPM device commands ....................................................................... 391Prior version CONFIGPOOL batch commands ....................................... 391

Running GPM in batch mode ..................................................................... 392Sample JCL job stream ........................................................................ 392Return codes....................................................................................... 393Conditional processing ....................................................................... 393Conditional processing examples........................................................ 396

GPM command examples.......................................................................... 397Creating a VP in a Symmetrix System................................................... 397Pool management example ................................................................. 402MOVE with REBIND example................................................................ 408DRAIN process example ...................................................................... 409REBALANCE process example .............................................................. 411VP compression examples .................................................................. 413

Suggested VP compression command sequence ....................................... 418


Contents

Chapter 8 Monitoring Pool Usage

Monitor functions ..................................................................................... 420Monitoring and alerts .......................................................................... 420

Using a User Exit with the SCF Pool Capacity Monitors ............................... 421 Syntax conventions................................................................................... 423 Save Device Capacity monitor syntax......................................................... 423

General ............................................................................................... 423Global interval .................................................................................... 423Controller ............................................................................................ 426Controller interval ............................................................................... 426Pool interval........................................................................................ 427

Thin Pool Capacity Monitor syntax............................................................. 428General ............................................................................................... 428Global interval .................................................................................... 428Controller ............................................................................................ 430Controller interval ............................................................................... 431Pool interval........................................................................................ 431

DSE Capacity monitor syntax ..................................................................... 432General ............................................................................................... 432Global interval .................................................................................... 432Controller ............................................................................................ 435Controller interval ............................................................................... 435Pool interval........................................................................................ 436

DSE Spillover Time monitor syntax ............................................................ 437 Thin CKD space reclamation ...................................................................... 438

Running TRU as a started task ............................................................. 439TRU SCAN utility .................................................................................. 440TRU RECLAIM utility ............................................................................. 440Limitations.......................................................................................... 441

Thin Pool Capacity Monitor examples ........................................................ 442Example of SCF initialization parameters............................................. 442Example of THN monitor for a specific Symmetrix system .................... 443Example of global THN monitor ........................................................... 443

Chapter 9 Monitoring SRDF/A and Write Pacing

Overview................................................................................................... 446SRDF/A Write Pacing ........................................................................... 446SRDF/A Single Session Auto Recovery operations................................ 448SRDF/A Monitor startup process.......................................................... 450SRDF/A Monitor polling steps.............................................................. 450

SRDF/A and WPA Monitor initialization parameters ................................... 452 Optional user exit...................................................................................... 453 SRDF/A and WPA Monitor SMF records ...................................................... 453

Chapter 10 Using the QoS Utility

Overview................................................................................................... 458Security interface ................................................................................ 459

Symmetrix Priority Control ......................................................................... 459 Dynamic Cache Partitioning....................................................................... 459 QoS control statements............................................................................. 460

Conventions........................................................................................ 460 QoS copy priority statements .................................................................... 461

DISPCPYP/DISPDEV............................................................................. 461


Contents

SETCPYP/SETDEVCP ............................................................................ 463QOSGET .............................................................................................. 465QOSSET .............................................................................................. 467QOSRESET........................................................................................... 470

SPC control statements ............................................................................. 472DISPSPC.............................................................................................. 472DISPDEVP / DISPDEV........................................................................... 473SETDEVP / SETDEV .............................................................................. 474SETDIR / SETSPC ................................................................................. 475

DCP control statements............................................................................. 477DISPCCFG............................................................................................ 477DISPCDEV or DISPCDVG/ DISPCDV....................................................... 478DISPCGRP ........................................................................................... 479DISPCGEN ........................................................................................... 480DISPCUSE............................................................................................ 480SETCACHE ........................................................................................... 481SETCPADD........................................................................................... 482SETCPDEL............................................................................................ 484SETCPMOD.......................................................................................... 485SETCPMRP........................................................................................... 486SETCPMVD/SETCPMV .......................................................................... 487

Mixed RDF mode commands ..................................................................... 489MRDFDISP WEIGHTS ............................................................................ 489MRDFDISP DEFAULTS........................................................................... 490MRDFDISP RDFSTATS........................................................................... 491MRDFSET POLICY ................................................................................. 492MRDFSET WEIGHTS.............................................................................. 493MRDFSET RESET .................................................................................. 494

Miscellaneous control statements............................................................. 495EXIT..................................................................................................... 495WAIT ## .............................................................................................. 495

QoS examples........................................................................................... 496SPC functionality................................................................................. 496DCP functionality................................................................................. 498LRU functionality ................................................................................. 500MRDF functionality .............................................................................. 502

QoS error and event messages.................................................................. 503

Chapter 11 zBoost PAV Optimizer

Introduction.............................................................................................. 506Restrictions......................................................................................... 507

Getting started.......................................................................................... 508Security............................................................................................... 508Configuring zBoost PAV Optimizer ....................................................... 508

Optimizing I/Os ........................................................................................ 510Summary of operations ....................................................................... 510Operation modes ................................................................................ 511Selecting devices ................................................................................ 512Limiting optimization by started task/job ............................................ 512Limiting optimization by tracks ........................................................... 513Controlling number of splits/constituent I/Os ..................................... 513Setting quiesce points ........................................................................ 514Consistency support ........................................................................... 515

SMF recording........................................................................................... 516


Contents

Overview............................................................................................. 516SMF record types................................................................................. 516SMF record format............................................................................... 516STATS record fields ............................................................................. 519SMF reporting utility ............................................................................ 525

Chapter 12 EMC ChangeTracker for z/OS

Introduction to the EMC ChangeTracker utility............................................ 530ChangeTracker Collector...................................................................... 530ChangeTracker Reporter ...................................................................... 531

ChangeTracker Collector ............................................................................ 532JCL ...................................................................................................... 533

ChangeTracker Collector parameters.......................................................... 533CYCLE.................................................................................................. 534DEVICE_LIST........................................................................................ 534HLQ..................................................................................................... 536LOG# (LOGNUM).................................................................................. 537MODE.................................................................................................. 537PALLOC ............................................................................................... 538SALLOC ............................................................................................... 538SMS_GROUP ....................................................................................... 538VOLSER|VOLUME................................................................................. 539VTOC................................................................................................... 539Developing a CONFIG file..................................................................... 540

ChangeTracker Collector commands .......................................................... 541DISPLAY ALL ........................................................................................ 541DISPLAY CYCLE.................................................................................... 542DISPLAY DEVICE .................................................................................. 542DISPLAY LOG ....................................................................................... 543HELP ................................................................................................... 543LOG#................................................................................................... 543LOGSWAP............................................................................................ 544STOP................................................................................................... 544VOLSER ............................................................................................... 545

Storage estimates for ChangeTracker Collector disk output ........................ 546 ChangeTracker Reporter ............................................................................ 547

Dumping VTOCs .................................................................................. 547JCL ...................................................................................................... 547

ChangeTracker Reporter parameters .......................................................... 548DATE ................................................................................................... 548DEVICE_LIST (syntax for ccuu and volser) ............................................ 549DEVICE_LIST (syntax for Symmetrix device numbers) ........................... 550INTERVAL ............................................................................................ 551MODE.................................................................................................. 552RA_COUNT .......................................................................................... 552RA_KBS............................................................................................... 552REPORTS ............................................................................................. 553RESYNCH_TIME ................................................................................... 554SMS_GROUP ....................................................................................... 555SYM_SERIAL........................................................................................ 555TOD..................................................................................................... 556

Reports ..................................................................................................... 557Report parameters .............................................................................. 557Symmetrix summary report ................................................................. 559


Contents

Volume summary report ...................................................................... 560Dataset summary report ...................................................................... 561

Interval statistics file................................................................................. 562 EMC ChangeTracker error and event messages .......................................... 563

Chapter 13 EMC Disk Compare for z/OS

Introduction to EMC Disk Compare ............................................................ 566Before you begin ................................................................................. 566Using Disk Compare ............................................................................ 566

Disk Compare usage and JCL ..................................................................... 567 EMC Disk Compare error and event messages ........................................... 571

Appendix A SCF Codes and cascaded message displays

SCF abend codes ...................................................................................... 574 SAICALL error codes .................................................................................. 577 Group Name Services reason codes .......................................................... 578 MSC message displays for cascaded SRDF configurations ......................... 580

Appendix B Resetting FBA channel paths and devices

The ESFFUCBC Utility ................................................................................. 582Example JCL ........................................................................................ 582

Appendix C Enhancements

ResourcePak Base release enhancements................................................. 584


Title Page

FIGURES

1 z/OS SymmAPI architecture......................................................................................... 272 Sample Symmetrix system - before FAST configuration ................................................ 353 FAST configuration example ........................................................................................ 364 Complex FAST configuration example.......................................................................... 385 FAST VP configuration example ................................................................................... 416 FAST VP complicated configuration example ............................................................... 437 FTS configuration ........................................................................................................ 458 Example JCL ................................................................................................................ 529 Symmetrix summary report........................................................................................ 55910 Volume summary report ............................................................................................ 56011 Dataset summary report ............................................................................................ 561


Figures


Title Page

TABLES

1 FAST version differences ............................................................................................. 342 Job step return codes .................................................................................................. 553 Initialization parameters and default values................................................................ 604 Customer tasks and command types......................................................................... 1455 DISPLAY field descriptions ........................................................................................ 2246 QUERY display field descriptions............................................................................... 2707 JCL required for ESCTLNM .......................................................................................... 3568 Input cards for ESFCHNU1 utility................................................................................ 3579 JCL required for ESFCHNU1 ........................................................................................ 35710 Return codes for ESFCHNU1 ...................................................................................... 35811 JCL required for EMCGROUP....................................................................................... 36212 GNS batch commands............................................................................................... 36313 Parameters Passed to User Exit from Pool Capacity Monitors..................................... 42214 SRDF/A Monitor initialization parameters.................................................................. 45215 SRDF/A Single Session Auto Recovery parameters..................................................... 45316 SMF record fields ...................................................................................................... 45317 QoS feature availability ............................................................................................. 45818 General operations.................................................................................................... 51019 Logging and messaging operations ........................................................................... 51020 Defining scope of optimization.................................................................................. 51121 Controlling resource utilization.................................................................................. 51122 Section 1 — zHPF PAV optimization parameters......................................................... 51923 Section 2 — Basic monitoring zHPF counts ................................................................ 52024 Section 3 — PAV optimization passive zHPF counters ................................................ 52125 Section 4 — PAV optimization active monitoring zHPF counters ................................. 52126 Section 5 — PAV optimization zHPF skip processing by parameters ........................... 52327 Section 6 — PAV optimization zHPF skip processing.................................................. 52328 Section 7 — PAV optimization logging event stats ..................................................... 52429 Interval statistics file record fields............................................................................. 56230 SCF abend codes....................................................................................................... 57431 SAICALL error codes .................................................................................................. 57732 SAICALL error codes - EMCRC..................................................................................... 57733 SAICALL error codes - ESFCTLNM ............................................................................... 57734 GNS reason codes..................................................................................................... 57835 ResourcePak Base enhancements............................................................................. 584


Tableses


PREFACE

As part of an effort to improve its product lines, 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 on product features.

Contact your 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 EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document.

AudienceThis document is intended for the host system administrator, system programmer, or operator who will be involved in managing or operating the Symmetrix storage system.

Related documentationThe following EMC publications provide additional information

◆ Mainframe Enablers Release Notes

◆ Mainframe Enablers Installation and Customization Guide

◆ Mainframe Enablers Message Guide

◆ AutoSwap for z/OS Product Guide

◆ Consistency Group for z/OS Product Guide

◆ REXX Interface Programmer’s Reference Guide

◆ SRDF Host Component for z/OS Product Guide

◆ Symmetrix® Remote Data Facility (SRDF) for VMAX ™40K, VMAX™ 20K/VMAX™, DMX ™ Series Product Guide

◆ Symmetrix TimeFinder® for VMAX 40K, VMAX 20K/VMAX Series Product Guide

◆ TimeFinder/Clone Mainframe Snap Facility Product Guide

◆ TimeFinder Mirror for z/OS Product Guide

◆ TimeFinder Utility for z/OS Product Guide

Conventions used in this document EMC uses the following conventions for special notices:

CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.


Preface

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

IMPORTANT

An important notice contains information essential to software or hardware operation.

Typographical conventions

EMC uses the following type style conventions in this document:

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

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

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

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

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

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

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

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

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

outside of running text

Courier bold Used for specific user input, such as commands

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

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

[ ] Square brackets enclose optional values

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

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

... Ellipses indicate nonessential information omitted from the example


Preface

Where to get helpEMC support, product, and licensing information can be obtained on the EMC Online Support site as described next.

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

Product information

For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Online Support site (registration required) at:

https://support.EMC.com

Technical support

EMC offers a variety of support options.

Support by Product — EMC offers consolidated, product-specific information on the Web at:

https://support.EMC.com/products

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

EMC Live Chat — Open a Chat or instant message session with an EMC Support Engineer.

eLicensing support

To activate your entitlements and obtain your Symmetrix license files, visit the Service Center on https://support.EMC.com, 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 EMC Account Representative or Authorized Reseller.

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

If you are missing a LAC letter, or require further instructions on activating your licenses through the Online Support site, contact EMC's 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.


http://support.EMC.com

https://support.EMC.com/products

http://support.EMC.com

Preface

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]


REVISION HISTORY

Revision Changes

01 Initial release of ResourcePak Base for z/OS version 7.6 Product Guide

02 • Added information on predefined SSN table entries not allowed• Added the VERBOSE parameter to Pool Management commands• Enhanced the WAIT parameter description for Pool Management commands• Enhanced the description of QoS MRDF functionality examples

03 • Added a description of SCF.INI.COMMAND.MAX• Changed the SCF.THN.LIST default value to Enable• Added a note to SCF.TRU.RECLAIM.STCNAME and SCF.TRU.SCAN.STCNAME to

add the procedure to PROCLIB• Added information about the typical value for the RA_KBS parameter of

EMC ChangeTracker

04 Added zBoost TM PAV Optimizer, including:• The zBoost PAV Optimizer chapter• ResourcePak Base initialization parameters related to zBoost PAV Optimizer in

the “Configuration File and Initialization Parameters” chapter• zBoost PAV Optimizer operator commands in the “Command Reference”

chapter


Revision History


CHAPTER 1Overview

This chapter provides an overview of EMC ResourcePak Base for z/OS.

◆ Mainframe Enablers and ResourcePak Base ............................................................ 26◆ Introduction to ResourcePak Base ........................................................................... 26◆ ResourcePak Base features ..................................................................................... 28◆ Fully Automated Storage Tiering (FAST).................................................................... 34◆ Federated Tiered Storage (FTS) ................................................................................ 45◆ zBoost PAV Optimizer.............................................................................................. 48

Overview 25

Overview

Mainframe Enablers and ResourcePak BaseEMC® ResourcePak® Base is a component of the Mainframe Enablers. The Mainframe Enablers are a group of software components that can aid you in monitoring and managing your storage. The components listed below are distributed and installed as a single package. This combined packaging simplifies installation and maintenance, and provides assurance of component compatibility.

◆ ResourcePak Base for z/OS

◆ Consistency Groups for z/OS

◆ SRDF® Host Component for z/OS

◆ TimeFinder®/Clone Mainframe Snap Facility

◆ TimeFinder/Mirror for z/OS

◆ TimeFinder Utility

When you install the Mainframe Enablers, you install the software for all of these components.

Activating ResourcePak Base

Follow the steps outlined in the Mainframe Enablers Installation and Customization Guide to install and activate ResourcePak Base.

For V7.6, ResourcePak Base initialization processing no longer allows pre-definition of SSN table entries via PARMLIB or MVS commands. Ensure that you do not add ResourcePak Base entries to the IEFSSN table for the LPAR via the PARMLIB or SETSSI command. Normally, EMC software dynamically creates an entry in the IEFSSN table via the IEFSSI macro.

Introduction to ResourcePak BaseResourcePak Base for z/OS is a software facility that makes communication more efficient between mainframe-based applications, provided by EMC or independent software vendors (ISVs), and one or more Symmetrix® storage systems. ResourcePak Base is designed to improve performance and simplify the use of mainframe-based Symmetrix applications.

ResourcePak Base delivers the following benefits:

◆ Ensures orderly installation and usage of other EMC and ISV partner provided products.

◆ Facilitates automatic interprogram communication.

◆ Avoids unnecessary Initial Program Load (IPL) events.

◆ Interfaces to commercially available tools, such as the REXX scripting language.

◆ Serves as a gateway to virtually all EMC platform-specific software, such as SRDF and TimeFinder family products.


Overview

ResourcePak Base includes the feature known as the EMC Symmetrix Control Facility (EMCSCF), which is the heart of ResourcePak Base. EMCSCF runs as a persistent address space and subsystem on z/OS hosts. It provides a uniform interface for EMC and ISV software products, where all products are using the same interface at the same feature/function level.

As shown in Figure 1, EMCSCF makes calls through the I/O Supervisor (IOS) to the Enginuity™ operating environment for Symmetrix devices.

Figure 1 z/OS SymmAPI architecture

ResourcePak Base is the delivery mechanism for the EMC Symmetrix Applications Programming Interface for z/OS (SymmAPI™-MF). It provides a central point of control by giving software a persistent address space on the mainframe for Symmetrix functions that perform tasks such as the following:

◆ Maintaining an active repository of information about EMC Symmetrix devices attached to z/OS environments and making that information available to other EMC or ISV-provided products.

◆ Performing automation functions.

◆ Inter-LPAR (logical partition) communication through the Symmetrix storage system. ResourcePak Base facilitates interprogram communication through a persistent address space on the host. This means that programs are not statically linked, but can be linked dynamically, thus making software installation quicker and easier.

◆ Insulating host applications from differences in the Enginuity operating environment of the Symmetrix system at different release levels. For example, the number of Symmetrix logical devices supported changes between one level of Enginuity and another. ResourcePak Base masks this difference so that host applications do not have to change.

ResourcePak Base for z/OS is a prerequisite for EMC mainframe applications such as TimeFinder Product Set for z/OS or SRDF Host Component for z/OS and is included with these products. You normally receive ResourcePak Base automatically when you order EMC mainframe applications such as the TimeFinder/Mirror or SRDF Host Component for z/OS (which you receive when ordering SRDF/S, SRDF/A, or SRDF/DM products).

EMCSFC

(ResourcePak Base)

• EMCSAI• SNAPAPI• Automation :

• Metadata:• Config Info

• Device Status• Event Monitor

EMC or ISV DevelopedProducts (e.g.,TimeFinder, SRDF Host Component)

Program Calls IOS

SymmetrixDevices

•SWAP

Introduction to ResourcePak Base 27

Overview

ResourcePak Base featuresResourcePak Base provides the following functionality with EMCSCF:

◆ Cross-system communication

◆ Automatic notfication of controller configuration changes to other Mainframe Enablers (MFE) applications, such as ConGroup.

◆ Nondisruptive API refreshes

◆ Save Device Capacity, DSE Capacity, Thin Device Capacity, DSE Spillover Time, SRDF/A and SRDF/A Write Pacing monitors

◆ Controller naming

◆ Group Name Services support

◆ Pool management

◆ SRDF/AR (Automated Replication)

◆ SRDF Asynchronous mode (SRDF/A) with Multi-Session Consistency

◆ SWAP services

◆ Recovery services

◆ SAF security

◆ Thin CKD space reclamation

◆ Thin gatekeeper support

◆ VP (thin device) compression/decompression

Cross-system communication

Inter-LPAR communication is handled by the EMCSCF cross-system communication (CSC) component. CSC uses locally and remotely connected Symmetrix systems to facilitate communications between LPARs. Several EMC Symmetrix mainframe applications use CSC to handle inter-LPAR communications.

Automatic notification of configuration changes to MFE applications

EMCSCF can automate the asynchronous notification of controller configuration changes to another MFE application, such as ConGroup, that supports the receipt of this data. When a configuration change occurs for at least one controller included in SCF, the information is broadcast in pre-determined intervals. The information can include the discovery of a new controller, the removal of an existing controller, the change in microcode level of a controller, the discovery of new devices, the removal of existing devices, the occurrence of a UCB swap, or a combination of these events.

Nondisruptive SymmAPI-MF refreshes

EMCSCF allows the SymmAPI-MF to be refreshed non-disruptively. EMCSCF does not need to be stopped and restarted to refresh the SymmAPI. Refreshing SymmAPI-MF also has no impact on applications that use the SymmAPI-MF such as SRDF Host Component or TimeFinder.


Overview

Note: Since the SymmAPI-MF is now persistent, simply stopping and restarting EMCSCF does not replace the SymmAPI-MF environment, unless you perform shutdown by issuing: F emcscf,INI,SHUTDOWN (emcscf is used as the name of EMCSCF started task throughout this manual). “Stopping EMCSCF services” on page 51 gives more information.

Capacity and DSE Spillover Time monitorsEMCSCF is a long-running task that provides a useful environment for automation and monitoring functions. Some EMC automation and monitoring tasks are indirectly invoked, such as TimeFinder initiation and control of Symmetrix Automated Replication or the Notify option of TimeFinder/Snap for z/OS.

ResourcePak base provides Save Device Capacity, DSE Capacity, Thin Device Capacity and DSE Spillover Time monitors that are run independently of other products. These EMCSCF monitor functions provide a way to:

◆ Automatically check space consumption thresholds

◆ Trigger an automated response that is tailored to the specific needs of the installation

SRDF/A monitorThe SRDF/A monitor in ResourcePak Base is designed to:

◆ Find EMC Symmetrix controllers that are running SRDF/A.

◆ Collect and write SMF data about those controllers.

◆ Optionally, invoke SRDF/A Single Session Auto Recovery procedures to recover a dropped single-session SRDF/A group.01

After you install ResourcePak Base, you can start up the SRDF/A monitor as a subtask of EMCSCF.

SRDF/A Write Pacing monitor

SRDF/A Write Pacing provides a method of extending the availability of SRDF/A, preventing conditions that could result in cache overflow.

The Write Pacing monitor exposes the user to relevant information regarding pacing activities within the Symmetrix. Pacing activities are collected at the group and device level.

The monitoring is performed on the controllers and RDF groups specified by the user. The level of detail (group and/or device level) is also selected by the user. The data that can be collected and reported on by the monitor includes:

◆ Changes in the ARMED state by device.

◆ Total paced delay by device.

◆ Total paced track count by device.

◆ Changes in the ENABLED/SUPPORTED/ARMED/PACED state for the group.

◆ Total paced delay for the group.

ResourcePak Base features 29

Overview

◆ Total paced track count for the group

The data collected by the monitor is presented in a similar manner as the current ASY monitor; as formatted messages, alerts and/or written SMF records.

Controller namingResourcePak Base provides the ability to assign a unique name to an EMC controller. The name can be up to 64 characters and is case-sensitive.

Group Name Services supportResourcePak Base includes support for Symmetrix Group Name Services (GNS). GNS allows you to define a device group once, and then use that single definition across multiple EMC products on multiple platforms. This means that you can use a device group defined through GNS with both mainframe and open systems based EMC applications. GNS also allows you to define group names for volumes that can then be operated upon by various other commands.

Pool managementResourcePak Base provides a set of General Pool Management (GPM) commands that can be executed online or in batch mode. Pool devices are a predefined set of devices that provide a pool of physical space. Pool devices are not host-accessible.

The GPM commands allow you to manage SNAPPOOLs, DSEPOOLs or THINPOOLs using the MODIFY command interface or using batch statements.

ResourcePak Base allows you to create thin pools (also called Virtual Pools) which could then be populated with thin data devices; it also allows the removal of any or all of the devices as well as the deletion of the pool itself. Supported by Enginuity level 5875 and higher, ResourcePak Base provides management of thin pools through the use of the BIND, UNBIND, and RENAME functions.

SRDF/AR resiliency SRDF/AR can recover from internal failures without manual intervention. Device replacement pools for SRDF/AR (or SARPOOLs) are provided to prevent SRDF/AR from halting due to device failure. In effect, a SARPOOL is a group of devices that are unused until SRDF/AR needs one of them.

SRDF/A multi-session consistencySRDF/A multi-session consistency (MSC) is a task in EMCSCF that ensures remote R2 consistency across multiple Symmetrix systems running SRDF/A. It provides the following:

◆ Coordination of SRDF/A cycle switches across systems.

◆ Up to 24 SRDF groups in a multi-session group.

◆ Up to eight MSC groups per SCF instance can be active concurrently. A new MSCGroup parameter is used with commands for multiple MSC group operations.

◆ One SRDF/A session per Symmetrix, one SRDF/A group per Symmetrix when using Enginuity level 5x70. With Enginuity level 5x71 and higher, the SRDF/A groups are dynamic and are not limited to one per Symmetrix system.

◆ ENABLE, DISPLAY, DISABLE, REFRESH, and RESTART group commands.


Overview

SWAP servicesResourcePak Base deploys a SWAP service in EMCSCF. It is used by AutoSwap for planned outages with the ConGroup Continuous Availability Extensions (CAX).

Recovery servicesRecovery services commands allow you to perform recovery on local or remote devices.

SAF securityThe EMCSAFI security interface uses z/OS SAF calls (RACROUTE) to request authorization to use resources. The security interface provides additional security checks for environments where multiple groups of users are using different devices in a single controller. EMC mainframe applications that support specifying the internal or Symmetrix device now check to ensure that devices are logically available for use only by an authorized user.

Thin CKD space reclamationStarting with ResourcePak Base version 7.4, and Enginuity level 5876 or higher, EMCSCF provides a Thin space reclamation (TRU) environment that records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the Symmetrix free track pool.

TRU provides a batch program that performs the following steps:

1. Scans the VTOC for available tracks in the volume freespace and updates the SDDF session information.

2. Analyzes the volume freespace and SDDF session information, and then performs the clearing of the tracks.

Monitoring occurs whether or not the thin device has the PREALLOCATE device level attribute, but does not occur if the thin device has the PERSIST device level attribute set.

Note: If a device was initially included and then subsequently excluded from TRU, the device is marked for no monitoring. However, until SCF is cycled the device remains allocated to TRU and monitoring of the device can be started by the TRU,START command. Refer to “TRU,START” on page 352 for a description of this command.

Thin gatekeeper support

Prior to Enginuity level 5876, thin devices (FBA or CKD) were not supported as gatekeepers. With Mainframe Enablers V7.4 and Enginuity level 5876 thin gatekeepers, both FBA and CKD are now supported.

The devices do not have to be bound and FBA devices must be addressable to z/OS to be used as gatekeepers.

Note: Binding establishes a relationship between a thin device and a thin device pool where host apparent writes to the thin device result in actual writes to one or more devices in the thin pool. This arrangement is known as thin provisioning.


Overview

VP Compression

Starting with Enginuity level 5876, thin device data can be manually compressed to save storage space and then decompressed when needed for active use.

VP Compression support also allows configuration, management, and reporting on the compression state for thin devices using the General Pool Management DISPLAY and QUERY THINDEV commands.

Note: EMC recommends that VP Compression should be only used against idle data and not against medium or greater workloads. Although VP Compression does support reads and writes against an active workload, it affects the performance of the entire controller.

Additionally, auto-compression (keeping volumes compressed) can only be obtained through use of FAST. With the exception an occasional backup to tape, it is best to fully decompress data before accessing it.

EMC suggests the following uses of manual compression (not FAST):

◆ Archiving old user accounts

◆ End of quarter information processing activity (DECOMPRESS-process-COMPRESS)

EMC does not suggested using manual compression (not FAST) for processing low cost/low performance active data.

How VP Compression works Enginuity allows data that is compressed to be both read and written by decompressing the data when needed into space that is reserved in the thin pool containing the compressed thin device allocations. To reserve this space and enable allocations, a thin pool must be enabled for compression. When compression is no longer desired for allocations in a pool, the compression capability can be disabled.

A read of a compressed track temporarily decompresses the track into temporary storage maintained in the pool. Writes always write the decompressed allocations on the thin device. The device can be manually compressed at any time. Decompression happens upon the user's request or when the data is written to. There is no automatic re-compression after a write.

Once a pool is enabled for compression, a background process runs to reserve storage in the pool that is used to temporarily decompress data. No compression of allocations in this pool can occur until this process completes.

A pool should not be enabled for compression unless there are active data devices with free space in the pool. If there is not enough space on active data devices in the pool to reserve space for temporary decompressions, the pool is not fully enabled for compression. Instead the pool waits for free space to complete the enable process.

Only after additional data devices are added and/or made active in the pool and there is enough room for the reserve space can the pool become fully enabled. When free space is made available, the pool becomes fully enabled the next time the Enginuity microcode checks for enabling pools, which is approximately every 15 minutes. To avoid this wait, ensure there are active data devices with free space in the pool before enabling compression.


Overview

When compression is disabled, the reserved storage in the pool is returned to the pool only after all compressed allocations are decompressed. This is not done automatically when compression is disabled for a pool. This must be done manually. Compression will not be fully disabled for a pool until all compressed thin devices bound to that pool are decompressed.

Due to the reserve space necessary for temporary decompressions, data devices remain allocated and cannot be removed from the pool until compression is fully disabled.

Compression is disabled by default and must be enabled manually before thin devices bound to that pool can be compressed. Compression cannot be fully disabled unless the data devices are active.

When choosing to compress a device, only allocations that have been written are compressed. Any allocations that were created during the bind or allocate processing that have not been written are reclaimed during the compression process. So, when a compressed device is decompressed, these allocations will no longer exist, and after decompression, the allocated tracks will not match the original allocated track count for the thin device.

Note: The zero reclaim that runs as part of the compression process will deallocate standard record-zero tracks, but will not scratch deleted datasets that do not yet contain standard record-zero tracks. In order to reclaim these tracks and avoid compressing deleted datasets, the Thin Reclaim Utility (TRU) should be run against a thin device before compressing that device. Only TRU scratches deleted datasets, so TRU must be run for space reclamation.

The fact that unwritten allocations can be reclaimed imposes a restriction that persistent allocations cannot be compressed, since they are not allowed to be reclaimed automatically. Any allocations that are not written are reclaimed during compression, if the tracks are not marked persistent. By making the allocations persistent, the allocated tracks are maintained and no compression can occur. In order to compress a thin device that has persistent allocations, the persistent attribute must first be removed, allowing compression and reclamation to occur. The compression process will not fail, but will have no effect on thin devices if they are allocated and have the persistent attribute set.

Compression of allocations for a thin device is a background task. Once the compression request is accepted, the thin device will have a background task associated with it that performs the compression for that device. While this task is running, no other background task, like allocate or reclaim, can be run against the thin device.

If a thin device containing allocations in multiple pools is compressed, the MFE compression function compresses all allocations in the pools where they reside. By default, no data is moved. Alternatively, we provide an option to move all allocations for the device to the pool where the device is currently bound to before compressing those allocations. If this option is used, all allocations for the device reside in the bound pool after compression is complete. This applies to decompression, as well. By default, the MFE decompression function decompresses all allocations in the pools where they reside. EMC also provides an option to move all allocations for the device to the pool where the device is currently bound to before decompressing those allocations. If this option is used, all allocations for the device reside in the bound pool after decompression is complete.


Overview

Fully Automated Storage Tiering (FAST)

Note: Mainframe Enablers version 7.4 and Enginuity level 5876 or higher support both FAST and FAST for Virtual Pools (VP). However, configuration is initiated and controlled using EMC Solution Enablers software version 7.4 or higher, running on host systems such as UNIX, Windows, or Open VMS.

What is FAST?

Fully Automated Storage Tiering (FAST) is Symmetrix software that runs background algorithms to continuously analyze the utilization (busy rate) of the Symmetrix system devices. The FAST controller processes the algorithm data, and generates plans for moving and swapping data volumes to fine tune performance and reduce costs. FAST can move the most-used data to the fastest (and most expensive) storage, such as Enterprise Flash Drives (EFD), the least-used data to the slowest (and least expensive) storage, such as SATA, while maintaining the remaining data on Fibre Channel (FC) drives, based on user-defined Symmetrix tiers and FAST policies. The objective of tiered storage is to minimize the cost of storage, while improving or maintaining performance, by putting the right data, on the right Symmetrix tier, at the right time.

Mainframe Enablers V7.4 with Enginuity 5876 introduces Federated Tiered Storage (FTS), which allows the virtualization of external storage as an external disk (eDisk). Adding the eDisk to the Symmetrix system makes its capacity available to the system as an external spindle. The order for fastest to slowest tiers is: EFD, FC, SATA, external.

There are two FAST products: FAST and FAST for virtual pools (FAST VP). The differences between these two versions are highlighted in Table 1.

Using EMC Solutions Enabler software, FAST can be set to move/swap data automatically or with user approval. All three drive technologies (EFD, FC, and SATA), or external (eDisks), are not required in the Symmetrix system to use FAST; it can also work between two technologies.

Table 1 FAST version differences

FAST FAST VP

Requires Solutions Enabler 7.1 or higher Requires Solutions Enabler 7.4 or higher for CKD support

Requires Enginuity 5874 Requires Enginuity 5875 or higher

Supports standard devices Supports thin devices

Supports FBA and CKD device emulations Supports FBA device emulationEnginuity 5876 supports thin CKD 3390 and thin iSeries 512 devices

Disk group provisioning (DP) tiers: contain disk groups

Virtual pool (VP) tiers: contain thin pools

DP modes: Auto Approve and User Approve VP modes: Auto Approve or None

User visible data movement plans and history No plans or history generated

Federated Stored Storage (eDisks) not supported

Supports Federated Stored Storage (eDisks) with Enginuity 5876


Overview

Note: Refer to to EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide for detailed information on configuring FAST and FAST VP.

FAST Overview

Note: FAST (disk group provisioning, or DP) supports standard devices and requires EMC Solutions Enabler V7.1 and higher. FAST VP (Virtual Pools) supports thin devices and requires Solutions Enabler V7.4 or higher for CKD support.

The primary goal of FAST is to share the Symmetrix disks (of varying technologies and drive speeds) among the applications so that the response time improves for the most critical applications, while the non-critical applications maintain an average response time. The response time is dependent on the FAST policies that are created.

The following example uses a Symmetrix system with the simple configuration shown in Figure 2.

Figure 2 Sample Symmetrix system - before FAST configuration

In this Symmetrix system, there are four disk groups and four applications using their storage. Flash disks are in disk group 1, Fibre Channel 15 K disks are divided into two disk groups: 2 and 3. The remaining disks are SATA, in disk group 4. All four applications use a set of these devices.

Fully Automated Storage Tiering (FAST) 35

Overview

In this example, the user wants to share flash drives between three of the most important applications, ASSET MANAGEMENT, FINANCIAL DATA MANAGEMENT, and SALES MANAGEMENT. The user also wants to make sure that the HUMAN RESOURCE database does not use any of the flash space.

Figure 3 on page 36 shows the completed FAST configuration. The text after the figure explains each step taken during the configuration.

Figure 3 FAST configuration example

To build the configuration shown in Figure 3, the following actions are taken:

Tiers The following Symmetrix tiers are configured:

• PrimeTier — With RAID 5 (3 +1) protection, Flash technology, and disk group 1.• WorkTier — With RAID 5 (7+1) protection, Fibre Channel technology, and disk

groups 2 and 3.• ArchiveTier — With RAID 6 (14+2) protection, SATA technology, and disk group 4.

Policies The following FAST policies are set:

• EXCHANGE POLICY — PrimeTier 50%, WorkTier 50%• FINANCE DATA POLICY — PrimeTier 50%, WorkTier 50%• SALES POLICY — PrimeTier 20%, WorkTier 40%, ArchiveTier 40%• HR POLICY — WorkTier 25%, ArchiveTier 100%


Overview

Storage groups The following storage groups, containing the devices used by their corresponding applications, are created:

• ASSET_MANAGEMENT• FINANCIAL_DATA_MANAGEMENT• SALES_MANAGEMENT• HUMAN_RESOURCES

Associations After the storage group is created, it can be associated with the respective FAST policy, as follows:

• ASSET_MANAGEMENT— ASSETPOLICY• FINANCE_DATA_MANAGEMENT — FINANCEDATAPOLICY• SALES_MANAGEMENT — SALESPOLICY• HUMAN_RESOURCES— HRPOLICY

The association tells the FAST controller that it should optimize the performance of the storage group and also specifies the upper limits of the resources it should use to optimize performance of the devices.

For example, in the association of SALES_MANAGEMENT — SALESPOLICY:

The FAST controller can place up to 20% of devices in the OraSales storage group on PrimeTier, up to 40% of the devices on WorkTier, and up to 40% of devices on ArchiveTier.

The capacity in a policy is specified as a percentage of the storage group, and the percentages in the policy must add up to at least 100%, but can be more than 100%. If the percentages add up to more than 100% (example HRDBPolicy), that means the FAST controller has some flexibility, or head room in one or more tiers, and can judiciously place the devices in the tiers deemed best suited. The percentages are only a way to limit the use of an expensive tier by the FAST controller. If there are many hot devices in the storage group, the percentage of the Flash tier can be set so that this storage group does not use all the Flash disk space at the expense of the other storage groups.

Within a FAST policy, the limit for a tier determines how many devices from an associated storage group (as a percentage of total SG logical capacity) are allowed to reside on the tier. The demand for a storage group on a tier is the physical raw capacity that the devices will need on the tier if the storage group was to occupy its full quota of space on the tier. The total demand for a tier is the sum of demands for all storage groups associated with the tier:

◆ 50% of the storage group FINANCE_DATA_MANAGEMENT, that is 1 TB of logical space or 1 TB worth of RAID 5 (3+1) devices, can be on PrimeTier. Therefore, FINANCE_DATA_MANAGEMENT can occupy approximately 1.33 TB (1 * 4/3) of raw space on this tier.

◆ 50% of ASSET_MANAGEMENT can be on PrimeTier that is 0.5 TB of RAID 5 (3+1) devices or 0.66TB of raw space.

◆ 20% of SALES_MANAGEMENT can be on flash, that is 0.4 TB of RAID 5 (3+1) or 0.53 TB of raw space.

Therefore, the total demand on the tier is approximately 2.52 TB, however the tier only has 1TB of raw space. Such configurations are legal; it only means that the storage groups are competing for the resources in this tier.


Overview

In such cases, the priority of the storage group decides which group gets to use the resource. The user needs to specify the priority of the storage group at time of policy association. As application priorities change, these priorities can be modified.

Note: Setting the storage group priority is explained in the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide.

Standard configurationexample 2

Figure 4 provides another example of a more complex FAST configuration with overlapping tiers and multiple storage groups.

Figure 4 Complex FAST configuration example

The configuration shown in Figure 4 shows three Finance applications, each with its own storage group associated with policy FINANCEDATA. It also includes two sales database applications (SALESMEN and SALES_PROGRAMS) associated with DBPolicy.

The user has partitioned the EFD (flash) disk groups into two groups: disk group 1, and disk group 2. PrimeDBTier only includes disk group 2 and PrimeTier only includes disk group 1.

Note: See the Solutions Enabler Symmetrix Array Controls CLI V7.4 Product Guide for a detailed explanation on managing tiers, policies, storage groups and associations.


Overview

FAST VP overview

Note: FAST VP supports virtual pools and requires Solutions Enabler 7.4 or higher for CKD support.

FAST VP builds incrementally upon the functionality of FAST, adding support for thin devices and sub-LUN data movement. FAST moves application data at the volume (LUN) level. Entire devices are promoted or demoted between tiers based on overall device performance. FAST VP adds finer granularities of performance measurement and data movement. The data from a single thin device under FAST control can be spread across multiple tiers. The FAST controller is free to relocate individual sub-extents of a thin device, based on performance data gathered at the extent level.

Note: A FAST VP extent is 480 thin device extents (5760 tracks, or 360 MB). The FAST VP sub-extent is 10 thin device extents (120 tracks, or 7680 KB ). A FAST VP thin device extent is 1 track group (12 tracks, or 768 KB).

Virtual poolsFAST VP uses the concept of virtual pools. A thin pool contains thin devices of identical emulation and protection type, all of which reside on disks of the same technology type and speed. Thin devices have no storage allocated to them when they are created; rather storage is allocated on-demand from a "bound" thin pool. The first write to a location in a thin device results in space being allocated on a DATA device from the bound pool.

With FAST VP, the data for a thin device may reside in its bound pool and potentially in one or more other pools. The role of thin pools in FAST VP is analogous to the role of disk groups in FAST. Both comprise the back-end storage available to devices under FAST control.

VP tiersFAST VP uses a virtual pool (VP) tier: a set of thin pools. A VP tier has a disk technology type and a protection type. To be a member of a VP tier, a thin pool must contain only DATA devices that reside on the tier technology type and match the tier protection type.

FTS supportMainframe Enablers V7.4 running Enginuity 5876 introduces Federated Tiered Storage (FTS). This feature virtualizes external storage as an external disk (eDisk). Adding the eDisk to the Symmetrix system makes its capacity available to the system as an external spindle.

The EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide provides additional information about FTS.

FAST VP supports tiers of externally provisioned VP pools. Encapsulated devices are not supported. There is no support for externally provisioned or encapsulated devices with FAST. The support for FAST VP is explained below:

◆ Tiers — You can create VP tiers, which can contain externally provisioned pools. The external tiers can only contain VP pools configured with externally provisioned DATA devices.


Overview

There will be no technology type for the external tiers. External tiers are treated as the slowest, performance wise, technology tiers. The new order for fast to slow tiers is EFD, FC, SATA, and external tiers.

◆ Policy — You can add external tiers to a FAST VP policy.

◆ Association — Once a policy with an external tier is part of the association, data from the associated storage group can move to/from the external tier without any restriction.

FAST policiesA FAST policy is a set of one to three DP tiers or one to three VP tiers, but not a combination of both DP and VP tiers. Policies define a limit for each tier in the policy. This limit determines how much data from a storage group associated with the policy is allowed to reside on the tier.

Storage groups are sets of devices. Storage groups define the devices used by specific applications. Storage groups are associated with FAST policies, and all of the devices in the storage group come under FAST control. The FAST controller can move these devices (or data from the devices) between tiers in the associated policy.

A storage group associated with a FAST policy may contain standard devices and thin devices, but the FAST controller will only act on the devices that match the type of tier contained in the associated policy. For example, if the policy contains thin tiers, then the FAST controller will only act on the thin devices in the associated storage group.

Simple exampleFigure 5 on page 41 shows a simple FAST configuration in a virtual provisioned environment. The storage group SQLServer is associated with the FAST Policy DBThinPolicy. SQLServer contains 300 GB of thin devices.


Overview

Figure 5 FAST VP configuration example

The following Symmetrix thin tiers were configured:

Tiers • EFD_R5_VPTier — With RAID 5 (3+1) protection, Flash technology, and thin pool EFD_R5_POOL. This tier contains a single pool, EFD_R5_POOL, which contains 50 GB of RAID-5 (3+1) DATA devices.

• FC_R6_VPTier — With RAID 6 (6+2) protection, Fibre Channel technology, and thin pool FC_R6_POOL.

• SATA_R6_VPTier — With RAID 6 (6+2) protection, SATA technology, and thin pool SATA_R6_POOL.

Storage group The SQLServer storage group contains 300 GB logical capacity, but only 60 GB of the 300 GB total logical size of SQLServer is actually allocated.

Policy The DB_VP_Policy is set as follows:

• EFD_R5_VPTier — 10%

• FC_R6_VPTier — 40%

• SATA_R6_VPTier — 50%

Storage Group Thin Tiers FAST Policy

10%

100%

FINANCEPOOL1 (220 GB)RAID-5 (3+1) on FC 15k


Finance_VPTierRAID-5 (3+1) on FC

Finance2010500 GB Total

400 GB Thin Logical200 GB Thin Allocated

100 GB (Standard )

200 GB (Thin)

200 GB (Thin)

bound

bound

EFD_R5_POOL (50 GB)RAID-5 (3+1) on EFD

EFD_R5_VPTierRAID-5 (3+1) on EFD


Overview

This means up to 10% of the allocated capacity of thin devices in SQLServer can reside in EFD_R5_VPTier, and up to 40% and 50% can reside in FC_R6_VPTier and SATA_R6_VPTier respectively.

Thin pools ◆ EFD_R5_POOL contains 50 GB of RAID-5(3+1) DATA devices and belongs to EFD_R5_VPTier.

◆ FC_R6_POOL contains 110 GB of RAID-6(6+2) DATA devices. 100 GB of thin devices from SQLServer are bound to FC_R6_POOL, meaning the initial allocations for those devices will be made in FC_R6_POOL. The FC_R6_POOL belongs to FC_R6_VPTier.

◆ SATA_R6_POOL contains 220 GB of RAID-6(6+2) DATA devices. 200 GB of thin devices from SQLServer are bound to SATA_R6_POOL. The SATA_R6_POOL belongs to the SATA_R6_VPTier.

Assuming the initial allocations all occurred in FC_R6_POOL, FAST could promote up to 6 GB of this allocated data to EFD_R5_VPTier and demote up to 30 GB to SATA_R6_VPTier, leaving up to 24 GB on FC_R6_VPTier.


Overview

Complex exampleFigure 6 shows a more complicated FAST configuration in an environment mixing disk group (DP) tiers and virtual pool (VP) tiers. The storage group Finance2010 is associated with the FAST Policy Finance_VP_Policy.

Figure 6 FAST VP complicated configuration example

Tiers The following Symmetrix VP tiers were configured:

• EFD_R5_VPTier — With RAID 5 (3+1) protection, Flash technology, and thin pool EFD_R5_POOL. This tier contains a single pool, EFD_R5_POOL, which contains 50 GB of RAID-5 (3+1) DATA devices.

• Finance_VPTier — With two pools: FINANCEPOOL1 and FINANCEPOOL2, each containing 220 GB of RAID-5 (3+1) DATA devices. 200 GB of thin devices from Finance2010 are bound to each of FINANCEPOOL1 and FINANCEPOOL2.

Storage group Finance2010 contains 400 GB of thin devices and 100 GB of standard devices. Although Finance2010 contains both thin and standard devices (for masking purposes), FAST will only manage the thin devices in the storage group, because the associated policy contains virtual pool tiers. Only the allocated capacity of the thin devices will be counted when determining the compliance of the storage group with the limits in the associated FAST Policy.

Storage Group Thin Tiers FAST Policy

10%

100%



Finance_VPTierRAID-5 (3+1) on FC

Finance2010500 GB Total

400 GB Thin Logical200 GB Thin Allocated

100 GB (Standard )

200 GB (Thin)

200 GB (Thin)

bound

bound

EFD_R5_POOL (50 GB)RAID-5 (3+1) on EFD

EFD_R5_VPTierRAID-5 (3+1) on EFD


Overview

Policy The limit for EFD_R5_VPTier in Finance_VP_Policy is 10%, and the limit for Finance_VPTier is 100%. All initial allocations for Thin Devices in Finance2010 will come from Finance_VPTier, because all the devices are bound to one of the pools in Finance_VPTier. Because the limit for Finance_VPTier is 100%, FAST is allowed to leave all of the allocated tracks on Finance_VPTier. However, if the performance statistics indicate some of the allocated tracks are busy, FAST may promote up to 10% of the allocated tracks to EFD_R5_VPTier.

Note that EFD_R5_VPTier is shared between Finance_VP_Policy and DB_VP_Policy from Figure 5 on page 41. If all of 300 GB of thin devices in the storage group SQLServer became fully allocated, FAST could relocate 10% or 30 GB of this data to EFD_R5_VPTier. If all 400 GB of thin devices in Finance2010 became fully allocated, then FAST could relocate 10% or 40 GB of this data to EFD_R5_VPTier. In this situation, up to 70 GB of data is allowed to reside on EFD_R5_VPTier, which only has 50 GB of capacity. Finance2010 and SQLServer would be competing for a shared resource, capacity in an EFD tier, and FAST would use a user-defined priority for each storage group to resolve which one gets the resource.

Note: See the Solutions Enabler Symmetrix Array Controls CLI V7.4 Product Guide for a detailed explanation of managing tiers, policies, and storage groups.


Overview

Federated Tiered Storage (FTS)

Note: FTS is supported on Symmetrix VMAX 20K/VMAX Series and Symmetrix VMAX 40K Series systems with Mainframe Enablers V7.4 and Enginuity 5876 and higher.

Federated Tiered Storage (FTS) gives you the ability to attach external storage to a Symmetrix system. Attaching external storage allows you to use physical disk space on existing systems while gaining access to Symmetrix features such as local replication, remote replication, storage tiering, data management, and data migration. In addition, FTS simplifies the management of federated multi-vendor or EMC storage systems.

Figure 7 shows the configuration of the network, storage systems, and application hosts using FTS. For additional details about configuring FTS, refer to the EMC Symmetrix Federated Tiered Storage (FTS) Technical Notes.

Figure 7 FTS configuration

IMPORTANT

Mainframe Enablers cannot create, configure, or remove FTS devices. You can perform these operations by using the Solutions Enabler SYMCLI. The “Federated Tiered Storage” chapter in the Solutions Enabler Symmetrix Array Controls CLI V7.4 Product Guide explains how to configure and manage FTS using the SYMCLI.

After you have configured the FTS devices, you can use the Mainframe Enablers SRDF Host Component query (SQ) commands to display and control devices that are externally provisioned. You can use the Host Component configure (SC) commands to manipulate FTS externally provisioned volumes just as traditional volumes are controlled (subject to licensing requirements).

Federated Tiered Storage (FTS) 45

Overview

eDisks

When you attach external storage to a Symmetrix system, FTS virtualizes an external system’s SCSI logical units as Symmetrix disks called eDisks. eDisks have two modes of operation:

◆ Encapsulation — Allows you to preserve existing data on external systems and access it through Symmetrix devices. These devices are called encapsulated devices.

◆ External Provisioning — Allows you to use external storage as raw capacity for new Symmetrix devices. These devices are called externally provisioned devices. Existing data on the external devices is deleted when they are externally provisioned.

The following restrictions apply to eDisks:

• Can only be unprotected devices. The RAID protection scheme of eDisks is dependent on the external system.

• Cannot be AS400, CKD, or gatekeeper devices.

• Cannot be used as VAULT, SFS, or ACLX devices.

EncapsulationEncapsulation has two modes of operation:

◆ Encapsulation for disk group provisioning (DP encapsulation) — The eDisk is encapsulated and exported from the Symmetrix system as disk group provisioned devices.

◆ Encapsulation for virtual provisioning (VP encapsulation) — The eDisk is encapsulated and exported from the Symmetrix system as thin devices.

In either case, Enginuity automatically creates the necessary Symmetrix devices. If the eDisk is larger than the maximum Symmetrix device size or the configured minimum auto meta size, Enginuity creates multiple Symmetrix devices to account for the full size of the eDisk. These Symmetrix devices are concatenated into a single concatenated meta device to allow access to the complete volume of data available from the eDisk.

External provisioningWhen you virtualize an eDisk for external provisioning, you can then create Symmetrix devices from the external disk group and present the storage to users. You can also use this storage to create a new FAST VP tier. See “FAST VP overview” on page 39 for additional details.

Mainframe Enablers allows you to display and control devices that are externally provisioned. The output of the SRDF Host Component query commands identify FTS devices as well as DX directors. The Host Component configure commands allow you to manipulate FTS externally provisioned volumes just as traditional volumes are controlled (subject to licensing requirements). The SRDF Host Component for z/OS Product Guide provides details on using the query commands to identify externally provisioned devices.

The following operations are supported for externally provisioned devices:

◆ Creating a TimeFinder/Snap session

◆ Creating any other native TimeFinder/Clone session

◆ Creating a TimeFinder/Clone emulation session


Overview

◆ Creating, deleting, swapping and moving RDF pairs. SRDF cascaded (CAS) commands may be used to create cascaded sets that include externally provisioned devices.

Note that FTS volumes may be mixed with non-FTS volumes in the same SRDF group. There are no restrictions regarding placing these volumes in a group that supports SRDF/A or SRDF/Star operations.

Geometry limited devices

Encapsulated devices that have a Symmetrix cylinder size larger than the reported user-defined geometry size are considered geometry limited. The following restrictions apply to geometry-limited devices:

• Does not support TimeFinder/Snap or TimeFinder/Mirror. Can only be used as source devices for TimeFinder/Clone operations. The rules for operations to larger target devices apply. See the TimeFinder/Clone Mainframe Snap Facility Product Guide for details about copying data from a source device to a larger target device.

If the devices are meta devices, the following requirements must be met:

– The number of meta members on the source device and the target device must be the same.

– For each of the source device and target device meta members, the Symmetrix cylinder size must be the same.

• Can only be used as R1 devices for SRDF operations. The rules for operations to larger R2 devices apply. See the SRDF Host Component for z/OS Product Guide for details about copying data from an R1 device to a larger R2 device. Does not support SRDF/AR.

If the devices are meta devices, the following requirements must be met:

– The number of meta members on the device that contains the R1 and the device that contains the R2 must be the same.

– For each of the meta members on the device that contains the R1 and the device that contains the R2, the Symmetrix cylinder size must be the same.

• Cannot be expanded, dissolved, converted, or used as the target of a VLUN migration.

• Thin devices cannot be unbound or rebound from their pool, and their space cannot be reclaimed.

• Thin pools created during encapsulation cannot have data devices added to them unless the addition is the result of encapsulating external storage.

• Thin pools cannot be added to tiers.

Federated Tiered Storage (FTS) 47

Overview

zBoost PAV OptimizerzBoostTM PAV Optimizer improves the performance of zHPF multi-track I/Os by systematically lowering response time resulting in reduced job elapsed time. This is achieved by splitting multi-track I/Os into multiple smaller “constituent I/Os” and executing them in parallel on alias devices by using the Compatible Parallel Access Volume (COMPAV) facility of the VMAX system.

You determine when zBoost PAV Optimizer gets invoked by specifying one or more of the following:

◆ z/OS device number or range◆ Volser or volser mask◆ SMS storage group name◆ Application (started task or batch job name)

After zBoost PAV Optimizer is enabled, you can control the amount of resources consumed, such as the minimum and maximum number of constituent I/Os allowed. In addition, you can monitor the alias consumption by zBoost PAV Optimizer and adjust its activity accordingly so as to not impact overall I/O throughput at the system and LCU level.

Besides normal operation mode called Active mode, zBoost PAV Optimizer provides two additional modes intended for planning and analysis: Passive mode and Monitor mode.

zBoost PAV Optimizer can write SMF records that detail its operation, such as the number of I/Os operated on, the number of constituent I/Os produced, the channel and SAP resource used.

Chapter 11, “zBoost PAV Optimizer,” provides a detailed description of zBoost PAV Optimizer functionality.


CHAPTER 2Running EMCSCF

This chapter describes how to start and stop the EMC Symmetrix Control Facility (EMCSCF).

◆ Initiation and termination commands...................................................................... 50◆ Implementing the EMCSCF started task ................................................................... 52◆ Additional datasets................................................................................................. 53◆ EMCSCF termination utility ...................................................................................... 55◆ Running multiple copies of EMCSCF ........................................................................ 56

Running EMCSCF 49

Running EMCSCF

Initiation and termination commandsThis section describes the commands used to start and stop the EMC Symmetrix Control Facility (EMCSCF).

Prior to using EMCSCF, you need to install EMC Mainframe Enablers and enable the EMCSCF software. The installation and enabling process is described in the EMC Mainframe Enablers Installation and Configuration Guide.

IMPORTANT

Services for many EMC z/OS products are provided by EMCSCF. EMC recommends leaving EMCSCF active at all times.

Starting EMCSCF services

To start EMCSCF:

◆ Type the following command at a console:

S EMCSCF[,REUSASID=YES]

Where:

• EMCSCF is the name of the EMCSCF started task, normally EMCSCF.

• REUSASID=YES is an optional parameter on the z/OS Start command. To avoid permanent loss of ASIDs during the life of an IPL, you should use REUSASID=YES on your start commands for ResourcePak Base.

Note: The z/OS level on your system must be 1.9 or higher and running on a z/990 or higher. DIAG must include REUSASID(YES) (use D DIAG to check, and SET DIAG=R1 to set to YES). You should contact your Systems Programmer to discuss whether this is available for use.

Customize and copy the EMCSCF procedure (member EMCSCF in the SCF SAMPLIB library) to a system PROCLIB that is used for started task START commands. When Consistency Group is installed and started with SUB=MSTR, then EMCSCF should also be started with SUB=MSTR. The EMCSCF procedure must be copied to a SYS1.PROCLIB procedure library concatenation when EMCSCF is to be started with SUB=MSTR.

When EMCSCF is started with SUB=MSTR, SRDF/AR processes cannot be defined with MSGOPT(SYSOUT(ddname)) parameters. MSGOPT(WTO) should be used.

Note: If an error occurs during startup and you receive an abend code, refer to “SCF abend codes” in the EMC Mainframe Enablers Message Guide. This section lists the abend codes that can be generated by EMCSCF and describes the action to take for each.


Running EMCSCF

Stopping EMCSCF services

To stop EMCSCF:

1. Type the following command at a console:

P EMCSCF

Where EMCSCF is the name of the SCF started task.

P EMCSCF shuts down the SCF address space, but leaves the SYMMAPI-MF in global memory.

Note that the following active environments can prevent SCF from shutting down:

• SAR (SRDF/AR) • MSC

2. If the MSC environment is active, before you can shut down ResourcePak Base, you must type the following command:

F EMCSCF,MSC,DISABLE

Note: “SRDF/A Multi-Session Consistency commands” on page 316 provides information about the running MSC in High Availability mode.

3. If SRDF/AR is active, before you can shut down ResourcePak Base, you must enter:

F EMCSCF,SAR,STOP,process_name

Note: “SRDF/AR: Symmetrix Automated Replication commands” on page 311 provides information about the SRDF/AR commands.

4. To shut down the SCF address space and release all resources held by SCF, type the following command:

F EMCSCF,INI,SHUTDOWN

Where EMCSCF is the name of the SCF started task.

This command forces the termination of SCF and the release of all resources held by SCF.

Initiation and termination commands 51

Running EMCSCF

Implementing the EMCSCF started taskResourcePak Base is intended to be run as a started task and should be started automatically when you perform an IPL on the system. Shut down ResourcePak Base only when the system is shut down.

Note: Implement the EMCSCF started task to run with a performance attributes/resource class that is equivalent to that used by system started tasks, generally above batch processing. This prevents elongation, or in extreme cases, failure of EMCSCF processes, such as device discovery and TimeFinder SRDF/AR processes.

//EMCSCF EXEC PGM=SCFMAIN,TIME=1440,REGION=0M//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SCFINI DD DISP=SHR,DSN=EMC.EMCSCF.INI//SYSABEND DD SYSOUT=*

Figure 8 Example JCL

These statements have the following meanings:

◆ EXEC

The main entry program is SCFMAIN. TIME=1440 is recommended for long running tasks. The region size should be more than four (4) megabytes. REGION=0M allows the address space to allocate virtual memory as required. REGION=0M is the preferred setting.

◆ STEPLIB

The ResourcePak Base load modules must be installed into an APF authorized dataset. The STEPLIB dataset is optional. If the ResourcePak Base load modules are installed into a linklisted dataset, then the STEPLIB DD statement is not needed.

◆ SCFINI

SCFINI is the ResourcePak Base initialization file. The SCFINI DD statement must point to a dataset containing SCF initialization statements. The SCFINI DD statement does not allow concatenation.

Note: “Initialization parameters” on page 60 describes the specific contents of this dataset.

◆ SYSABEND

This DD statement is optional, but recommended.


Running EMCSCF

Additional datasetsResourcePak Base automatically creates the following datasets while running:

◆ A log file

The log file automatically records critical events (such as address space initialization, address space termination, and all console messages) in a text format.

◆ A dynamic trace file

The dynamic trace file records programmatic events as they occur. This trace file is useful for problem solving.

The name and location of these datasets is determined by the SCFINI initialization parameters.

Note: “Initialization parameters” on page 60 describes these parameters.

Both the log file and the dynamic trace file may expand as much as the system allows. After either the log file or the dynamic trace file is full, ResourcePak Base takes the following steps:

1. Closes the log file or dynamic trace file.

2. Allocates and opens a new log file or dynamic trace file.

Note: In normal operation, the log file is closed and reallocated each day at midnight.

“SCF.WORK.HLQ” on page 136 describes the format of the SCF LOG and SCF TRACE dataset names.

GRS considerations for use of the SCFLOG and SCFTRACE datasets

An ENQ Reserve lockout can occur for resource SYSIGGV2 during dynamic allocation of SCFTRACE or SCFLOG datasets if IBM rules for GRS EXCLusion RNL are not followed for catalogs and SYSIGGV2 resources.

Please see the following IBM doc for more information:

◆ Information apar II14297

◆ MVS Planning: GRS

◆ DFSMS: Managing Catalogs

The ENQ lockout that occurs is:

◆ LPAR1 ENQ'S on SYSIGGV2 with minor name of scflog or scftrace dsname AND Reserves the CATALOG volume.

◆ LPAR2 ENQ'S on SYSIGGV2 with minor name of usercat dsname AND waits for SYNCHRES because LPAR1 has reserved the CATALOG volume.

◆ LPAR1 ENQ's on SYSIGGV2 with minor name of usercat dsname AND waits because LPAR2 holds this resource.

This is an ENQ Reserve lockout.

Additional datasets 53

Running EMCSCF

Here is an example of the required RNL defs:

RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSIGGV2) RNAME('ICFCAT.TS2CAT.SFTWRE') RNLDEF RNL(EXCL) TYPE(PATTERN) QNAME(SYSIGGV2) RNAME('????-44-??????ICFCAT.TS2CAT.SFTWRE.....-44-......’)

The PATTERN type RNAME consists of a total of 88 bytes:

◆ 44 bytes for dsname pattern, and

◆ 44 bytes for catalog name pattern.

The number of padded “?”'s is 44 for the dsname pattern, and the catalog name is padded with blanks (represented by “...”) to complete a total of 44 bytes.


Running EMCSCF

EMCSCF termination utilityResourcePak Base has an SCF termination utility, SCFTM31A. You can find this utility in the load library where all SCF modules are placed. (The JCL is located in SCF.SAMPLIB as member SCFUTL01.) Invoke SCFTM31A to terminate an active SCF global environment when the SCF address space is not active.

Such a situation would occur when you terminate the SCF address space by issuing:

P EMCSCF

but do not issue:

F EMCSCF,INI,SHUTDOWN

The SCF global environment is still active, and jobs using SYMMAPI-MF routines can still run.

To then terminate the active global environment when the SCF address space is not active, you must run SCFTM31A with PARM=”TERMSCF' as follows:

// EXEC PGM=SCFTM31A,PARM=’TERMSCF’//SCF$nnnn DD DUMMY

Where nnnn is the name of SCF subsystem.

If the SCF address space abends, you must run SCFTM31A with PARM=’CLEANSCF’ as follows:

// EXEC PGM=SCFTM31A,PARM=’CLEANSCF’//SCF$nnnn DD DUMMY

To simplify SCF cleanup, you can set up the JCL for SCF as a 2-step job:

//STEP1 EXEC PGM=SCFMAIN….

//STEP2 EXEC PGM=SCFTM31A,PARM=’CLEANSCF’,COND=ONLY//SCF$nnnn DD DUMMY

Where nnnn is the name of the SCF subsystem.

Job step return codes

Table 2 lists the possible termination utility return codes.

Table 2 Job step return codes

Code Meaning

0 The requested action was performed and the utility completed normally.

Abend code 1069

The utility was not able to find the SCF requested. Please verify that the DDNAME SCF$nnnn references the SCF you require.

EMCSCF termination utility 55

Running EMCSCF

Running multiple copies of EMCSCFYou can run multiple instances of EMCSCF as separate z/OS subsystems. This is useful for testing new versions of EMCSCF or EMCSCF-enabled products.

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

//SCF$nnnn DD DUMMY

Where nnnn defines this instance of EMCSCF as a unique z/OS subsystem. The same DD statement can then be used in any task for which you want to use this copy of EMCSCF.

For example:

Testing Version 7.0.0 of EMCSCF (note the DD statement with SCF$V700)

//EMCSCF EXEC PGM=SCFMAIN,TIME=1440,REGION=0M//STEPLIB DD DISP=SHR,DSN=DS-PREFIX.LINKLIB//SCFINI DD DISP=SHR,DSN=EMC.EMCSCF.INI//SYSABEND DD SYSOUT=*//SCF$V700 DD DUMMY

Add a connection DD statement for any task you want to use this instance of EMCSCF.

For example, if you want TimeFinder to use this version of EMCSCF, you would add the DD statement to the TimeFinder JCL:

//SAMPLE EXEC PGM=EMCTF//SYSOUT DD SYSOUT=A//STEPLIB DD DISP=SHR,DSN=DS-PREFIX.LINKLIB//SCF$V700 DD DUMMY //SYSIN DD *


CHAPTER 3Configuration File and Initialization Parameters

This chapter describes the initialization parameters available in the ResourcePak Base configuration file.

◆ Creating a configuration file .................................................................................... 58◆ Sample SCFINI file................................................................................................... 59◆ Initialization parameters ......................................................................................... 60

Configuration File and Initialization Parameters 57

Configuration File and Initialization Parameters

Creating a configuration fileBefore using ResourcePak Base, you need to create a configuration file containing your customized initialization parameter settings. SCFINI is the ResourcePak Base configuration file that contains the EMCSCF initialization parameters.

EMCSCF initialization parameters are specified as a series of parameter specifications in the following format:

<keyword> = <value>

◆ The keyword must begin in column 1.

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

◆ Each record in the SCFINI dataset must begin on a separate line in the configuration file.

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

For example:

SCF.LOG.RETAIN.COU-NT=10

Will result in SCF.LOG.RETAIN.COUNT=10 being processed.

◆ Comment records are allowed and are indicated with an asterisk (*) in column 1.

◆ To add a comment on a parameter line, use the format /* comment */.

◆ The dataset referenced in SCFINI may or may not be under SMS control as defined in the installation. Therefore, the DATACLAS, STORCLAS, and MGTCLAS entries may not be required.

After the SCFINI file is processed during the SCF startup procedure, SCF will read startup parameters from logical PARMLIB member SCFINI00. If member SCFINI00 is not found, normal processing will continue.

If SCFINI00 is found, the SCFINI parameters located in that library are appended to or replace the parameters that were read in from the SCFINI DD statement. The parameters located in SCFINI00 are appended when they are presented as a list, for example, SCF.DEV.EXCLUDE.LIST. When a parameter in SCFINI00 is not a .LIST file, then it will replace an existing parameter. You can place any startup parameters in the logical PARMLIB member SCFINI00. Comments are only allowed in the last line of the member. RACF READ authority is required to read the logical PARMLIB. The logical PARMLIB definitions on an LPAR can be verified with the z/OS command D PARMLIB.



Sample SCFINI fileYou can use the following sample as a basis for your own SCFINI by:

◆ Changing existing initialization parameters in the sample file to meet your needs.

◆ Adding new initialization parameters to the file.

As indicated in this SCFINI example, the initialization parameters are displayed as comments to be used as sample parameters. Before using this file, remove the asterisks (*) and edit the parameters to match your configuration.

*************************************************** * * ALL OF THE STARTUP PARAMETERS BELOW ARE SHOWN * AS COMMENTS TO BE USED AS SAMPLE PARAMETERS. * * REMOVE THE "*" AND EDIT THE PARAMETERS TO MATCH * YOUR CONFIGURATION. * * NOTE: PARAMETERS SHOULD BEGIN IN COLUMN 1 * *************************************************** *SCF.WORK.HLQ=SCFSERVE *SCF.LOG.RETAIN.COUNT=10 *SCF.LOG.RETAIN.DAYS=10 *SCF.LOG.STORCLAS=STORCLAS *SCF.LOG.DATACLAS=DATACLAS *SCF.LOG.MGMTCLAS=MGMTCLAS *SCF.LOG.TRACKS.PRI=10 *SCF.LOG.TRACKS.SEC=50 *SCF.TRACE.MEGS=1 *SCF.TRACE.RETAIN.COUNT=10 *SCF.TRACE.RETAIN.DAYS=10 *SCF.TRACE.DATACLAS=DATACLAS *SCF.TRACE.MGMTCLAS=MGMTCLAS *SCF.TRACE.STORCLAS=STORCLAS *SCF.WORK.UNIT=SYSDA *SCF.WORK.VOLSER=VOLSER *SCF.DEV.EXCLUDE.LIST=CUU1-CUU2 *SCF.DEV.INCLUDE.LIST=CUU3-CUU4 ******* CROSS SYSTEM COMMUNICATIONS ******** *SCF.CSC.ACTIVE=YES *SCF.CSC.GATEKEEPER.LIST=CUU5 *SCF.CSC.GATEKEEPER.01175.LIST=00AC *SCF.CSC.ACTIVEPOLL=10 *SCF.CSC.IDLEPOLL=5

Note: You can also find a sample SCFINI file in SCF.SAMPLIB

Sample SCFINI file 59


Initialization parametersInitialization parameters and their default values are listed in the following table.

Table 3 Initialization parameters and default values

Initialization parameter Default value

“SCF.ASY.MONITOR” on page 66 DISable

“SCF.ASY.POLL.INTERVAL” on page 66 5

“SCF.ASY.SECONDARY_DELAY” on page 66 120

“SCF.ASY.SMF.POLL” on page 67 6

“SCF.ASY.SMF.RECORD” on page 67 None

“SCF.ASY.USEREXIT” on page 67 None

“SCF.CNTRL.EXCLUDE.LIST” on page 68 None

“SCF.CNTRL.INCLUDE.LIST” on page 68 None

“SCF.CSC.ACTIVE” on page 68 NO

“SCF.CSC[.<cntrl#>|RMT].ACTIVEPOLL” on page 69 5 (.5 seconds) for local controllers 10 (1 second) for remote controllers

“SCF.CSC[.<cntrl#>]. ATTNACTIVE” on page 69 YES

“SCF.CSC[.<cntrl#>].ATTNPATHGRP” on page 70 NO

“SCF.CSC[.<cntrl#>|RMT].EXPIRECYCLE” on page 71 20

“SCF.CSC.GATEKEEPER.LIST” on page 72 Available general gatekeepers specified by SCF.GATEKEEPER.LIST. If none of these are available, then CSC uses any MVS devices set by SCF.DEV.EXCLUDE and SCF.DEV.INCLUDE.Offline devices are chosen in preference to online devices.

“SCF.CSC.GATEKEEPER.<cntrl#>.LIST” on page 72 None

“SCF.CSC[.<cntrl#>|RMT].IDLEPOLL” on page 73 5 seconds for local controllers 10 seconds for remote controllers

“SCF.CSC.INSTANCE” on page 74 0

“SCF.CSC[.<cntrl#>|RMT].MITPERIOD” on page 75 30

“SCF.CSC.REFORMAT” on page 76 NO

“SCF.CSC[.<cntrl#>|RMT].SELTIMEOUT” on page 76 60

“SCF.CSC[.<cntrl#>|RMT].VERBOSE” on page 77 NO

“SCF.DAS.ACTIVE” on page 78 NO

“SCF.DEV.ATTR.HRO.INCLUDE.LIST” on page 79 None

“SCF.DEV.ATTR.HRO.EXCLUDE.LIST” on page 80 None

“SCF.DEV.EXCLUDE.LIST” on page 80 None

“SCF.DEV.INCLUDE.LIST” on page 81 None



“SCF.DEV.MULTSS=YES|NO” on page 81 NO

“SCF.DEV.OPTIMIZE.ENABLE” on page 82 NO

“SCF.DEV.OPTIMIZE.PAV” on page 82 NO

“SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST” on page 83 None

“SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST” on page 83 None

“SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST” on page 84 None

“SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST” on page 84 Job names supplied in SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST

“SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE” on page 85 None

“SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL” on page 85 None

“SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU” on page 86 None

“SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT” on page 86 None

“SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX” on page 87 None

“SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ” on page 87 2

“SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE” on page 88 2

“SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST” on page 88 None

“SCF.DEV.OPTIMIZE.PAV.TRACK.MIN” on page 89 None

“SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ” on page 89 0

“SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE” on page 90 0

“SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST” on page 90 None

“SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST” on page 91 None

“SCF.DEV.OPTIMIZE.SMF.RECID” on page 92 NO

“SCF.DEV.OPTIMIZE.VERBOSE” on page 92 NO

“SCF.DEV.WAITINT” on page 93 60

“SCF.DSE.LIST” on page 93 DISable

“SCF.DSE.xx.LIST” on page 93 None

“SCF.DSE.<cntrl#>.LIST = ENAble | DISable” on page 94 None

“SCF.DSE.<cntrl#>.LIST = GATEkeeper=ccuu” on page 94 None

“SCF.DSE.<cntrl#>.xx.LIST” on page 95 None

“SCF.DSE.<cntrl#>.poolname.xx.LIST” on page 95 None

“SCF.DSE.WARNING” on page 95 None

“SCF.DSE.MINOR” on page 96 None

“SCF.DSE.MAJOR” on page 96 None



Initialization parameters 61


“SCF.GATEKEEPER.LIST” on page 96 None

“SCF.GATEKEEPER.<cntrl#>.LIST” on page 97 None

“SCF.GNS.ACTIVE” on page 97 NO

“SCF.GNS.WAITINT” on page 98 1800

“SCF.INI.COMMAND.MAX” on page 98 255

“SCF.INI.CPFX” on page 98 None

“SCF.INI.CPFX.DD” on page 99 NO (not activated)

“SCF.INI.SCOPE” on page 99 SYSPLEX

“SCF.LFC.LCODES.LIST” on page 100 None

“SCF.LOG.CYLINDER” on page 100 No

“SCF.LOG.DATACLAS” on page 101 None

“SCF.LOG.MGMTCLAS” on page 101 None

“SCF.LOG.RETAIN.COUNT” on page 101 10

“SCF.LOG.RETAIN.DAYS” on page 102 10

“SCF.LOG.STORCLAS” on page 102 None

“SCF.LOG.TRACKS.PRI” on page 102 10

“SCF.LOG.TRACKS.SEC” on page 103 50

“SCF.MSC.ADCOPY.ONDROP” on page 103 NO

“SCF.MSC.AUTO.RECOVER.RETRY” on page 103 None

“SCF.MSC.CYCLE.TIME.WARN” on page 104 60

“SCF.MSC.ENABLE” on page 104 NO

“SCF.MSC.GTFUSR.RECID” on page 105 100 (hex)

“SCF.MSC.GTFUSR.TRACE” on page 105 NO

“SCF.MSC.SDDFQ.TODA” on page 107 64

“SCF.MSC.MAX.LOCK.WAIT” on page 106 1

“SCF.MSC.OVERWRITE” on page 106 NO

“SCF.MSC.PAVO” on page 106 NO

“SCF.MSC.SDDFQ.TODA” on page 107 None

“SCF.MSC.SDDFQ.TODA” on page 107 NO

“SCF.MSC.SDDFQ.TOMF” on page 107 NO

“SCF.MSC.SDDFQ.TOOS” on page 108 NO

“SCF.MSC.VERBOSE” on page 109 NO

“SCF.PDVHC.WAITINT” on page 109 30





“SCF.REG.MAX.CONTROLLER.ERRORS” on page 109 3

“SCF.REG.MAX.ERRORS” on page 110 9

“SCF.REG.WAITINT” on page 110 30

“SCF.SDV.LIST” on page 110 DISable

“SCF.SDV.<cntrl#>.xx.LIST” on page 112 DISable

“SCF.SDV.<cntrl#>.LIST = GATEkeeper=ccuu” on page 111 None

“SCF.SDV.xx.LIST” on page 112 None

“SCF.SDV.<cntrl#>.xx.LIST” on page 112 None

“SCF.SDV.<cntrl#>.poolname.xx.LIST” on page 112 None

“SCF.SNAP.NOTIFY_POLLING” on page 113 1

“SCF.SNAP.NOTIFY_POLLTIME” on page 113 1

“SCF.SRV.GSM.ACTIVE” on page 113 YES

“SCF.SRV.GSM.INTERVAL” on page 114 15

“SCF.SS.AUTO.RECOVER” on page 114 None

“SCF.SS.AUTO.RECOVER.ser#.rdfg#=option” on page 114 None

“SCF.SS.AUTO.RECOVER.BCV= BCV (startup_option,post_recovery_option)” on page 115

None

“SCF.SS.AUTO.RECOVER.BCV.ser#.rdfg#=BCV (startup_option,post_recovery_option)” on page 116

None

“SCF.SS.AUTO.RECOVER.ITRK=itrk” on page 116 None

“SCF.SS.AUTO.RECOVER.ITRK.ser#=itrk” on page 117 None

“SCF.SS.AUTO.RECOVER.JOBNAME=jobname” on page 117 None

“SCF.SS.AUTO.RECOVER.JOBNAME.ser#=jobname” on page 118

None

“SCF.SS.AUTO.RECOVER.LPAR=id” on page 118 None

“SCF.SS.AUTO.RECOVER.MINDIR=##” on page 119 None

“SCF.SS.AUTO.RECOVER.MINDIR.ser#=##” on page 119 None

“SCF.SS.AUTO.RECOVER.PREFIX=hccpfx” on page 120 None

“SCF.SS.AUTO.RECOVER.PROC=procname” on page 120 None

“SCF.THN.LIST” on page 121 ENAble

“SCF.THN.<cntrl#>.LIST” on page 121 None

“SCF.THN.<cntrl#>.LIST = GATEkeeper=ccuu” on page 122 None

“SCF.THN.xx.LIST” on page 122 None

“SCF.THN.<cntrl#>.xx.LIST” on page 122 None





“SCF.THN.<cntrl#>.poolname.xx.LIST” on page 123 None

“SCF.TRACE.COMPRESS” on page 123 NO

“SCF.TRACE.CYLINDER” on page 123 No

“SCF.TRACE.DATACLAS” on page 124 None

“SCF.TRACE.FLUSH.AT” on page 124 75

“SCF.TRACE.MEGS (default)” on page 124 1

“SCF.TRACE.MGMTCLAS” on page 125 None

“SCF.TRACE.RETAIN.COUNT” on page 125 10

“SCF.TRACE.RETAIN.DAYS” on page 125 10

“SCF.TRACE.STORCLAS” on page 126 None

“SCF.TRACE.TRACKS.PRI” on page 126 None

“SCF.TRACE.TRACKS.SEC” on page 126 None

“SCF.TRU.DEBUG” on page 127 NO

“SCF.TRU.DEV.EXCLUDE.LIST” on page 127 None

“SCF.TRU.DEV.INCLUDE.LIST” on page 127 None

“SCF.TRU.ENABLE” on page 128 YES

“SCF.TRU.RECLAIM.DSFACTOR” on page 128 1000

“SCF.TRU.RECLAIM.DSPREFIX” on page 128 EMC.RECLAIM

“SCF.TRU.RECLAIM.METHOD” on page 129 1

“SCF.TRU.RECLAIM.PGMNAME” on page 129 ESFTRURC

“SCF.TRU.RECLAIM.POST.MAX” on page 130 9,999,999

“SCF.TRU.RECLAIM.POST.MIN” on page 130 100

“SCF.TRU.RECLAIM.POST.PCT” on page 130 50

“SCF.TRU.RECLAIM.POST.TYPE” on page 130 FREESPACE

“SCF.TRU.RECLAIM.SCRATCH.WAIT” on page 131 0

“SCF.TRU.RECLAIM.STCNAME” on page 131 None

“SCF.TRU.RECLAIM.STRESS.MONITOR” on page 132 YES

“SCF.TRU.RECLAIM.STRESS.WAIT” on page 132 5

“SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT” on page 132 30 seconds (3000)

“SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT” on page 133 150

“SCF.TRU.RECLAIM.SYSVTOC.WAIT” on page 133 30 seconds (3000)

“SCF.TRU.RECLAIM.TIMELIMIT.LIST” on page 134 None

“SCF.TRU.RECLAIM.TASK.LIMIT” on page 134 10





The following section provides complete descriptions of the initialization parameters.

“SCF.TRU.SCAN.PGMNAME” on page 134 None

“SCF.TRU.SCAN.STCNAME” on page 135 None

“SCF.TRU.SCAN.TASK.LIMIT” on page 135 10

“SCF.TRU.SCRATCH.POST.MAX” on page 130 9,999,999

“SCF.TRU.SCRATCH.POST.MIN” on page 130 100

“SCF.TRU.SCRATCH.POST.PCT” on page 130 50

“SCF.TRU.SCRATCH.POST.TYPE” on page 130 FREESPACE

“SCF.TRU.SCRATCH.RECLAIM” on page 135 20

“SCF.TRU.THICKR1” on page 136 YES

“SCF.WORK.HLQ” on page 136 SCFSERVE

“SCF.WORK.UNIT” on page 137 SYSDA

“SCF.WORK.VOLSER” on page 137 None

“SCF.WPA.EXCLUDE.CNTRL” on page 137 None

“SCF.WPA.INCLUDE.CNTRL” on page 138 All groups on all controllers

“SCF.WPA.MONITOR” on page 139 DISABLE

“SCF.WPA.MSGLEVEL” on page 139 BASIC

“SCF.WPA.POLL.INTERVAL” on page 139 5 minutes

“SCF.WPA.SMF” on page 140 DISABLE

“SCF.WPA.SMF.FILTER” on page 140 No filtering is performed. All data records are written to SMF and displayed in theinformational statistics messages.

“SCF.WPA.SMF.RECORD” on page 141 None

“SCF.WPA.STYPES” on page 141 ALL





SCF.ASY.MONITOR

DescriptionIf enabled, SCF.ASY.MONITOR causes the SRDF/A monitor to actively monitor any SRDF/A sessions. If this parameter is disabled, the SRDF/A monitor starts, but then becomes inactive, waiting for commands.

Possible valuesENAble | DISable

DefaultDISable

Example

SCF.ASY.MONITOR=ENA

SCF.ASY.POLL.INTERVAL

DescriptionSCF.ASY.POLL.INTERVAL specifies the time (in minutes) between polls of controller status.

Possible values1 to 60

Default5

Example

SCF.ASY.POLL.INTERVAL=4

SCF.ASY.SECONDARY_DELAY

DescriptionSCF.ASY.SECONDARY_DELAY specifies the threshold (in seconds) that the secondary delay must be equal to or greater than.


Default120

Example

SCF.ASY.SECONDARY_DELAY=180



SCF.ASY.SMF.POLL

DescriptionSCF.ASY.SMF.POLL specifies a multiplier value to use when calculating how often to record SMF INTERVAL records. The multiplier uses the value of SCF.ASY.POLL.INTERVAL to make the calculation.

For example, if the SCF.ASY.POLL.INTERVAL value is 5 (minutes) and the SCF.ASY.SMF.POLL value is 3, then the SRDF/A monitor obtains and writes the SMF INTERVAL every 15 minutes.


Default6

Example

SCF.ASY.SMF.POLL=3

SCF.ASY.SMF.RECORD

DescriptionSCF.ASY.SMF.RECORD specifies the number of an SMF record to write about controllers that are running SRDF/A. If you do not specify SCF.ASY.SMF.RECORD, then the SRDF/A monitor does not write any SMF records.


Example

SCF.ASY.SMF.RECORD=255

SCF.ASY.USEREXIT

DescriptionSCF.ASY.USEREXIT specifies the name of a User Exit to link to in the event of a changed state. If you do not specify SCF.ASY.USEREXIT, the SRDF/A Monitor does not call a User Exit.

Note: EMC does not supply a user exit. You must supply the user exit. However, EMC does provide a sample in SCF.SAMPLIB. The name of this user exit is SCFRDFAX.

Possible valuesUp to eight alphanumeric characters



Example

SCF.ASY.USEREXIT=SRDFAUX

SCF.CNTRL.EXCLUDE.LIST

DescriptionSCF.CNTRL.EXCLUDE.LIST excludes all of the devices for the specified controllers. You can specify this parameter repeatedly to exclude the desired number of devices.

Possible values12-character controller IDs, or the value ALL

Note: You must enter the full 12-character value. Controller exclude lists always override device include lists.

Example

SCF.CNTRL.EXCLUDE.LIST=000000006205,000000004010

SCF.CNTRL.INCLUDE.LIST

DescriptionSCF.CNTRL.INCLUDE.LIST is only valid when the SCF.CNTRL.EXCLUDE.LIST=ALL parameter is used, and includes all of the devices for the specified controllers. You can specify this parameter repeatedly to include the desired number of devices.

Possible values 12-character controller IDs

Note: You must enter the full 12-character value. Controller include lists always override controller exclude lists.

ExampleSCF.CNTRL.INCLUDE.LIST=000195601010

SCF.CSC.ACTIVE

DescriptionWhen set to YES, SCF.CSC.ACTIVE activates the SCF Cross System Communication component (CSC).

Possible valuesYES | NO

DefaultNO



Example

SCF.CSC.ACTIVE=YES

SCF.CSC[.<cntrl#>|RMT].ACTIVEPOLL

Description SCF.CSC.ACTIVEPOLL defines the active polling period. The polling period is the time that the CSC component uses to verify the control records within the Symmetrix controller. The active polling period is applied when the CSC component is waiting for responses for outstanding requests, or when new work is being received from other registered hosts in a predetermined active domain period.

Valid options are:

Note: Not specifying [.<cntrl#>|RMT] is preferred as this allows all controllers to use the same parameter value.

Possible values A number that represents a unit of 1/10th of a second. The number must be less than the idle poll period.

Note: Remote controllers will use a value of 2*SCF.CSC.ACTIVEPOLL if a more specific keyword is not specified.

Default 5 (.5 seconds) for local controllers, 10 (1 second) for remote controllers

Example

SCF.CSC.ACTIVEPOLL=4

SCF.CSC[.<cntrl#>]. ATTNACTIVE

Description SCF.CSC. ATTNACTIVE =YES indicates that CSC can use the Enginuity attention feature for host notification. This allows messages to be processed quicker and more efficiently. When YES is specified, CSC will perform a self-test on startup and after a CSC,REFRESH to ensure that the attention interface processing is working correctly. If the self-test fails, then messages are issued and CSC will return to the ATTNACTIVE=NO state.

SCF.CSC.ATTNACTIVE=NO indicates that CSC will use the polling values (IDLEPOLL and ACTIVEPOLL) for host notification.

cntrl# Refers to a specific controller ID such that the specified polling period refers to that controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits. For a remote controller, cntrl# overrides RMT for the same keyword.

RMT Indicates all remotely connected controllers.



cntrl# refers to a specific controller ID such that this setting specifies that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.

To activate a different value for ATTNACTIVE, issue the SCF INI,REFRESH operator command.

Note: The SCF.CSC.ATTNACTIVE parameter requires Enginuity level 5875 or higher.

Possible values YES | NO

Default YES

Example SCF.CSC.ATTNACTIVE=YES

SCF.CSC[.<cntrl#>].ATTNPATHGRP

Description SCF.CSC.ATTNPATHGRP=YES indicates that CSC can establish a pathgroup to its offline gatekeeper if there are no other online devices to the Symmetrix controller that supports the CSC attention interface. Message SCF0659W is displayed as a VERBOSE message to indicate that no online device could be located and the gatekeeper pathgroup has been established, as follows:

SCF0659W CSC (0001234-00567) ATTENTION INTERFACE PATHGROUP TO GATEKEEPER ESTABLISHED

Note: If VERBOSE=NO is specified or defaulted, the above message will not display.

After the gatekeeper pathgroup is established, a self-test is performed by CSC to ensure that the attention interface is working correctly.

SCF.CSC.ATTNPATHGRP=NO indicates that CSC is not permitted to establish a pathgroup to its offline gatekeeper if there are no other online devices to the Symmetrix controller. In this instance, CSC on this host will not receive attention messages from other hosts and will rely on the IDLE and ACTIVE polling periods for retrieving cross-system messages.

CSC will display the following message during its self-test to indicate that attention processing is not active:

SCF0659W CSC (0001926-00291) ATTENTION INTERFACE SELF TEST FAILED DUE TO NO ONLINE DEVICES

cntrl# refers to a specific controller ID such that this setting specifies that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.



To activate a different value for ATTNPATHGRP, issue the SCF INI,REFRESH operator command followed by a CSC,REFRESH operator command.

Note: The SCF.CSC.ATTNPATHGRP parameter requires Enginuity level 5875 or higher.


Default NO

Example

SCF.CSC.ATTNPATHGRP=YES

SCF.CSC[.<cntrl#>|RMT].EXPIRECYCLE

DescriptionSCF.CSC.EXPIRECYCLE enables you to specify a selective timeout cycle to recognize that a host is missing. A cycle is the time period you select with the IDLEPOLL parameter. When a host has not been seen for the specified number of cycles, it is eligible to be removed (unregistered) from the CSC component. “SCF.CSC[.<cntrl#>|RMT].MITPERIOD” on page 75 provides more details.

For example, SCF.CSC.EXPIRECYCLE=5 will cause the host to be eligible for removal after 5 cycles of inactivity. For a SCF.CSC.IDLEPOLL=5 value, this would be a 25 second period.

Valid options are:



Note: If you specify a value less than 5, then 5 will be used. If you specify a value greater than 30, then 30 will be used. If you specify a value of zero or do not specify SCF.CSC.EXPIRECYCLE, then 20 is used.

Default20

cntrl# Refers to a specific controller ID such that the specified timeout value refers to that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.

For a remote controller, cntrl# overrides RMT for the same keyword.




Example

SCF.CSC.EXPIRECYCLE=15

SCF.CSC.GATEKEEPER.LIST

DescriptionSCF.CSC.GATEKEEPER.LIST allows preferred z/OS devices to be chosen for communication to the SCF-accessible Symmetrix controllers by the CSC component. If a suitable z/OS device cannot be located on this list, then the general EMCSCF gatekeeepers as specified by SCF.GATEKEEPER.LIST (see page 96) will be used. If a general EMCSCF gatekeeper cannot be located, then all devices for the Symmetrix controller become candidates. In this instance, offline devices are chosen in preference to online devices.

If you specify a list of Symmetrix device numbers for a controller using the alternate form SCF.CSC.GATEKEEPER.<cntrl#>.LIST (see page 72), the SCF.CSC.GATEKEEPER.LIST is not processed for this controller.

CSC gatekeeper devices are reprocessed whenever the CSC,REFRESH operator command is entered. If the gatekeeper list is changed, then issue the INI,REFRESH operator command before you issue the CSC,REFRESH command.

Possible valuesz/OS device numbers and ranges of z/OS device numbers

DefaultAvailable general gatekeepers specified by SCF.GATEKEEPER.LIST. If none of these are available, then CSC uses any MVS devices set by SCF.DEV.EXCLUDE and SCF.DEV.INCLUDE. Offline devices are chosen in preference to online devices.

Example

SCF.CSC.GATEKEEPER.LIST=A04A

SCF.CSC.GATEKEEPER.<cntrl#>.LIST

DescriptionSCF.CSC.GATEKEEPER.<cntrl#>.LIST is an alternate form of specifying gatekeeper devices to SCF.CSC.GATEKEEPER.LIST. SCF.CSC.GATEKEEPER.<cntrl#>.LIST allows you to choose specific Symmetrix devices, and no others, for each Symmetrix controller.

You can specify the Symmetrix controller (cntrl#) with either the 5-digit or 12-digit Symmetrix controller ID. (Use the 12-digit ID when multiple controllers use the same last 5 digits.) If a gatekeeper device cannot be located on this list, then the CSC component retries at intervals until one of the listed devices becomes available.

Note: Use of the full 12-digit Symmetrix controller ID is recommended.

CSC gatekeeper devices are reprocessed whenever you enter the CSC,REFRESH operator command. If the gatekeeper list changes, then issue the INI,REFRESH operator command before you issue the CSC,REFRESH command.



Possible valuesSymmetrix device numbers and ranges of Symmetrix device numbers

DefaultNone

Example

SCF.CSC.GATEKEEPER.000184500309.LIST=0000-0002

Or, specify the following if the last 5 digits of the ID are not used by another controller:

SCF.CSC.GATEKEEPER.00309.LIST=0000-0002

SCF.CSC[.<cntrl#>|RMT].IDLEPOLL

DescriptionSCF.CSC.IDLEPOLL specifies the idle polling period (in seconds). The idle polling period is applied when the CSC component has no outstanding work and the predetermined active polling domain is no longer active. Take care with this parameter, as it determines the worst-case response time for CSC requests. If you notice elongated response times for CSC requests, then you should reduce this value.

Note that you must restart SCF to activate a change to the parameter options.

Valid options are:



Note: Remote controllers will use a value of 2*SCF.CSC.IDLEPOLL if a more specific keyword is not specified.

Default5 seconds for local controllers, 10 seconds for remote controllers

Example

SCF.CSC.IDLEPOLL=4

cntrl# Refers to a specific controller ID such that the specified idle polling period refers to that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.





SCF.CSC.INSTANCE

DescriptionSCF.CSC.INSTANCE allows Cross System Communication (CSC) isolation among multiple instances of SCF. CSC uses this value to determine the set of SCF address spaces that participate in a communication request from an EMC product, for example, AutoSwap, z/OS Migrator, ConGroup, etc.

Only SCF instances with the same SCF.CSC.INSTANCE value process a communication request. Examples of how this parameter can be used is to isolate multiple SCF instances of a product, or for testing new versions of a product without interfering with the production instance.

The CSC,DISPLAY HOSTS operator command can be used to display the set of CSC instances.

In the following example, there is only 1 SCF active on this set of LPARs that is using SCF.CSC.INSTANCE=22 as shown by the SET.

SCF0663I CSC DIS HOSTS SCF0660I CSC HOST DISPLAY CONTROLLER SERIAL NUMBER : 0001957-00225 (01) HOST COUNT : 1 ------------HOST------------- --REGISTRATION--- PROCESS RESP NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME CTRL SET -1-- --------2-------- -3- -4 --------5-------- ------- ---- -6- X11A 011A3F94209800DE 73MA 3 10/10/11 21:32:47 000.011 01 022 SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED

In the following example, when issuing the DISPLAY,HOSTS command to another SCF on the same X11A LPAR, there are 2 SCF address spaces on 2 different LPARs running with the same SCF.CSC.INSTANCE=42. This limits the various applications running against these SCFs to communicating to only these SCFs. If z/OS migrator is started with a connector (SCF$nnnn DD DUMMY) to these SCFs, it will not see or communicate with another SCF.

SCF0663I CSC DIS HOSTS SCF0660I CSC HOST DISPLAY CONTROLLER SERIAL NUMBER : 0001957-00080 (01) 0001957-00196 (02) HOST COUNT : 2 ------------HOST------------- --REGISTRATION--- PROCESS RESP NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME CTRL SET -1-- --------2-------- -3- -4 --------5-------- ------- ---- -6- X11A 011A3F94209800DF 74MA 5 10/13/11 16:47:19 000.018 01 042 X11B 011B3F94209800D1 74MA 5 10/13/11 16:49:35 000.054 02 042 SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED

All of the active SCF.CSC.INSTANCE may be displayed using the CSC,DISPLAY HOSTS ALLSETS operator command

SCF0663I CSC DIS HOSTS SCF0660I CSC DISPLAY HOSTS ALLSETS CONTROLLER SERIAL NUMBER : 0001957-00080 (01) 0001957-00196 (02) HOST COUNT : 7 ------------HOST------------- --REGISTRATION--- PROCESS RESP NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME CTRL SET -1-- --------2-------- -3- -4 --------5-------- ------- ---- -6- X11A 011A3F9420980092 74MA 5 10/10/11 21:32:47 000.011 01 000 X11A 011A3F94209800DE 74MA 5 10/10/11 21:32:47 000.011 01 022 X11A 011A3F94209800DF 74MA 5 10/13/11 16:47:19 000.018 01 042



X11B 011B3F94209800D1 74MA 5 10/13/11 16:49:35 000.054 02 000 X11B 011B3F94209800D1 74MA 5 10/13/11 16:49:35 000.054 02 042 X11E 011E3F9420980045 74M 5 10/13/11 18:43:31 000.648 01 000X11F 011F3F9420980076 74M 5 10/14/11 10:12:30 003.106 02 000SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED

If an expected application has not joined the configuration, we recommend you check the SCF.CSC.INSTANCE parameter or the CSC displays as an initial step to discover the reason.


Default 0

ExampleSCF.CSC.INSTANCE=25

SCF.CSC[.<cntrl#>|RMT].MITPERIOD

DescriptionSCF.CSC.MITPERIOD specifies a missing interval timing (MIT) period. During each MIT period, the CSC component reads the currently registered host to determine if there has been any activity from the host since the last MIT period. If a host has not been seen for five of that host’s IDLEPOLL periods, then CSC issues the SCF0645W message. If a host has not been seen for the number of periods defined by SCF.CSC.EXPIRECYCLE, then the host is eligible to be removed from the CSC component.

Note: Message SCF0645W in the EMC Mainframe Enablers Message Guide provides more information.

If you specify a value less than 10, then 10 is used. If you specify a value greater than 60, then 60 is used. If you specify a value of zero, or do not specify a value, then the default of 30 is used.

Valid options are:


cntrl# Refers to a specific controller ID such that the specified MIT period refers to that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.






Default30

Example

SCF.CSC.MITPERIOD=25

SCF.CSC.REFORMAT

DescriptionSCF.CSC.REFORMAT instructs the CSC component to reformat the communication area used by the CSC in the Symmetrix system. If there are registered systems using the communication area, then this value is ignored.

Note: You should only use this command when requested by EMC Customer Support.

Possible valuesALL | NO

DefaultNO

Example

SCF.CSC.REFORMAT=ALL

SCF.CSC[.<cntrl#>|RMT].SELTIMEOUT

DescriptionSCF.CSC.SELTIMEOUT specifies the timeout period (in seconds) used to release the Cross System Component Symmetrix system.

Note: Do not change this value unless instructed by EMC Customer Support.

Valid options are:


cntrl# Refers to a specific controller ID so that the specified timeout period refers to that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.





Possible valuesA number that represents units of seconds. The minimum value is 10.

Default60

Example

SCF.CSC.SELTIMEOUT=55

SCF.CSC[.<cntrl#>|RMT].VERBOSE

DescriptionSCF.CSC.VERBOSE=NO limits the display of CSC messages to only indicate conditions that may require investigation. The following messages are not issued, or are issued at a reduced frequency, when SCF.CSC.VERBOSE=NO:

• SCF0603W and SCF0604E are only displayed a single time when the condition is detected and after each CSC, REFRESH command is entered.

• SCF0615I

• SCF0630E

• SCF0643W is issued only when the CSC lock hold time reaches half the SCF.CSC.SELTIMEOUT value rather than after 10 seconds.

• SCF0645W

• SCF0659I

• SCF0690I

• SCF0695I

Valid options are:



DefaultNO

Example

SCF.CSC.VERBOSE=NO

cntrl# Refers to a specific controller ID such that this setting refers to that specific controller only. cntrl# can be either the full 12 characters or just the last 5 characters of the Symmetrix controller ID. Use the 12-digit ID when multiple controllers use the same last 5 digits.





SCF.DAS.ACTIVE

DescriptionWhen set to YES, the SCF.DAS.ACTIVE parameter activates AutoSwap within the SCF address space allowing for products that rely on this EMC feature.

SCF.DAS.ACTIVE results in the automatic startup of the SCF Cross System Communications component (CSC), as Autoswap relies on CSC for its own internal communications. Since CSC can also be initiated through the SCF.CSC.ACTIVE parameter, having both INI parameters is not a problem.

Note: Although, withSCF.DAS.ACTIVE set to YES, you do not need the SCF.CSC.ACTIVE parameter.

In addition, DAS and CSC can also be started automatically through the EMC License Feature Code (LFC) interface.

As of version 4.2, z/OS Migrator requires the SCF.DAS.ACTIVE entry in the SCF INI parameter file when any of the configured Migrator groups conclude with a UCB SWAP. Refer to the z/OS Migrator 4.2 Product Guide for more information on volume groups that include SWAP as a completion option.

If there is any question as to whether Autoswap and/or CSC are running under your SCF task, look for the following messages in your SCF task log:

SCF0301I SCF.DAS.ACTIVE=YESSCFS175I AutoSwap Initialization complete. SCFS285W AutoSwap waiting for EMCSCF Cross System CommunicationSCFS226I AutoSwap has initialized with EMCSCF Cross System

Communication

Either of the following commands can be issued as a MODIFY against running the SCF task (scftask) to verify Autoswap and/or CSC availability to reliant tasks:

F scftask DAS DISPLAY- Displays default/global Autoswap parameters via SCFS163I

F scftask,CSC DISPLAY - Display all known CSC hosts active under z/OS system via SCF0660I

This base version of Autoswap should not be confused with the Autoswap that runs as part of EMC Consistency Groups (CONGROUP). That version runs within ConGroup and is not available for use by other products.


DefaultNO

ExampleSCF.DAS.ACTIVE=YES



SCF.DEV.ATTR.HRO.INCLUDE.LIST

DescriptionSCF.DEV.ATTR.HRO.INCLUDE.LIST specifies the devices to be managed by the Host Read Only (HRO) feature. You can specify this parameter repeatedly to include all of the desired devices.

Changes to SCF.DEV.ATTR.HRO.INCLUDE.LIST are processed using the INI,REFRESH command.

When in an AutoSwap group, the HRO-included devices that will be validated by AutoSwap are as follows:

Note: Any deviation from these will result in a group validation warning or error.

◆ If the HRO-included device specifies an online AutoSwap FROM device, then a similar HRO include should be specified for the TO device.

Deviation will result in a warning indicating that the FROM device UCB will not be swapped during an AutoSwap swap.

◆ If the HRO-included device specifies an AutoSwap TO device and there is no HRO include for the FROM device, then the FROM device must be offline.

Deviation results in an error indicating that the HRO attributes are not consistent. This is to prevent applications that were writing to the FROM device being blocked from writing to the TO device following the AutoSwap swap.

◆ If the AutoSwap TO device is online, then a corresponding HRO included device should be specified. AutoSwap must also have the AllowOnlineToDevice group option.

Deviation will result in an error indicating that the TO device must have a HRO attribute.

AutoSwap follows the following rules when swapping HRO-included devices:

◆ If the TO device is online, then no UCB swap will result. The TO device will remain online following the swap and will remain HRO.

◆ If the FROM device is online and both the FROM and TO device are HRO-included devices, then the UCB swap will take place. The TO device will be online and HRO following the swap

◆ If the FROM device is online and there is no corresponding HRO include statement for the TO device then the UCBs will not be swapped. The FROM device will remain online.

In this case, the state of the FROM device following AutoSwap processing depends on the AutoSwap ChangeSourceDevice (CSD) specification:

• If CSD indicates (or defaults) to one of the NRDY states, then the FROM device will become not ready to the host and any read or write accesses to the device will result in an intervention required condition. If the NRDY state is removed (for example using SRDF Host Component), then the device retains the HRO attribute.

• If CSD indicates that the FROM devices should be NONRDY, then the FROM device remains HRO. This does not apply to CAX groups.



Possible valuesz/OS device numbers (cuus) and/or ranges of z/OS device numbers. The device number applies to all subchannel sets such that the corresponding special devices in alternate subchannel sets is also included. For example, A000 will also include any special devices in 0A000, 1A000, and so forth.

DefaultNone

Example

SCF.DEV.ATTR.HRO.INCLUDE.LIST=A000-A049,A056

SCF.DEV.ATTR.HRO.EXCLUDE.LIST

DescriptionSCF.DEV.ATTR.HRO.EXCLUDE.LIST specifies devices previously included by SCF.DEV.ATTR.HRO.INCLUDE.LIST but which are to be excluded from management by the Host Read Only (HRO) feature. You can specify this parameter repeatedly to exclude all of the desired devices.

Changes to SCF.DEV.ATTR.HRO.EXCLUDE.LIST are processed using the INI,REFRESH command.

Possible valuesz/OS device numbers (cuus) and/or ranges of z/OS device numbers. The device number applies to all subchannel sets such that the corresponding special devices in alternate subchannel sets is also included. For example, A000 will also include any special devices in 0A000, 1A000, and so forth.

DefaultNone

ExampleThe following two statements are the equivalent of the example under SCF.DEV.ATTR.HRO.INCLUDE.LIST:

SCF.DEV.ATTR.HRO.INCLUDE.LIST=A000-A056

SCF.DEV.ATTR.HRO.EXCLUDE.LIST=A04A-A055

SCF.DEV.EXCLUDE.LIST

DescriptionSCF.DEV.EXCLUDE.LIST specifies the devices that are not accessed by SCF. You can specify this parameter repeatedly to exclude the desired number of devices. To activate a new value, perform an INI,REFRESH followed by a DEV,REFRESH.

Possible valuesz/OS device numbers (cuus) and/or ranges of z/OS device numbers



DefaultNone

Example

SCF.DEV.EXCLUDE.LIST=A000-A049,A056

SCF.DEV.INCLUDE.LIST

DescriptionSCF.DEV.INCLUDE.LIST includes the devices that were excluded by SCF.DEV.EXCLUDE.LIST. You can specify this parameter repeatedly to include the desired number of devices.

Note: Include device lists always override exclude device lists. It does not matter where the SCF.DEV.INCLUDE.LIST statement appears.

Possible valuesz/OS device numbers (cuus) and/or ranges of z/OS device numbers

DefaultNone

Example

SCF.DEV.INCLUDE.LIST=A047

SCF.DEV.MULTSS=YES|NO

Description SCF.DEV.MULTSS=YES indicates that SCF will discover and use special devices in the alternate subchannel set. This setting is required if using AutoSwap to swap between like device numbers in alternate subchannel sets.

SCF.DEV.MULTSS=NO indicates that SCF will only discover the normal base devices in the currently active subchannel set.

SCF must be restarted to activate a change in value.


Default NO

Example

SCF.DEV.MULTSS=YES



SCF.DEV.OPTIMIZE.ENABLE

DescriptionEnables (YES) or disables (NO) zBoost PAV Optimizer.

The DEV,OPTIMIZE ENABLE (page 175) and DEV,OPTIMIZE DISABLE (page 175) commands may be used to subsequently change the enablement state.

When SCF.DEV.OPTIMIZE.ENABLE is set to NO, other zBoost PAV Optimizer parameters are not validated.

Note: z/OS must be level 1.13 or higher to use SCF.DEV.OPTIMIZE.ENABLE=YES.

Possible valuesYES|NO

Default NO

ExampleSCF.DEV.OPTIMIZE.ENABLE=YES

SCF.DEV.OPTIMIZE.PAV

DescriptionDetermines the operation mode of zBoost PAV Optimizer:

◆ YES — Activates zBoost PAV Optimizer for both read and write operations.

◆ NO — Disables zBoost PAV Optimizer.

◆ READ (or R) — Activates zBoost PAV Optimizer for read channel programs only.

◆ WRITE (or W) — Activates zBoost PAV Optimizer for write channel programs only.

◆ PASSIVE (or PAS) — Puts zBoost PAV Optimizer in Passive mode.

Note: “Operation modes” on page 511 describes the Passive mode.

◆ MONITOR (or MON) — Puts zBoost PAV Optimizer in Monitor mode.

Note: “Operation modes” on page 511 describes the Monitor mode.

Possible valuesYES|NO|Read|Write|PASsive|MONitor

Default NO



ExampleSCF.DEV.OPTIMIZE.PAV=R

SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST

DescriptionExcludes devices from selections made with prior zBoost PAV Optimizer INCLUDE statements (SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST, SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST, SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST, and SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST).

Note: “Selecting devices” on page 512 discusses device selection for zBoost PAV Optimizer.

This parameter may be specified multiple times to build up a composite list.

Possible valuesA list of comma-separated values, each of which is either an individual CUU or a range of CUUs specified as ccuu[-ccuu]. The maximum CUU value is FFFF.

Default None. No devices are excluded from processing.

ExampleSCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST=0000-0100

SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST

DescriptionSelects the devices on which zBoost PAV Optimizer operates by specifying their CUUs.



Note: Devices may be excluded from this list by using the SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST parameter.

Possible valuesA list of comma-separated values, each of which is either an individual CUU or a range of CUUs specified as ccuu[-ccuu]. The maximum CUU value is FFFF.



Default None. No devices are included by default.

ExampleSCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST=E200,E300-E450,E500SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST=A123,FFEE-FFFF

SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST

DescriptionLimits zBoost PAV Optimizer processing to specific started tasks or jobs. Only specified started tasks or jobs are eligible for optimization.

Note: “Limiting optimization by started task/job” on page 512 discusses started task/job limitation.


Possible valuesA comma-separated list of started task or job names. Wildcarding is not supported.

Default None. All started tasks and jobs are subject to optimization.

ExampleSCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST=DB2PRD,PLBATCH

SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST

Defines a list of job name prefixes eligible for zBoost PAV Optimizer processing.

Note: “Limiting optimization by started task/job” on page 512 discusses started task/job limitation.

This parameter may be specified multiple times to further modify the list.

Duplicates and less generic prefixes are removed from the list. For example, specifying SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST=DB2,PL3, PL allows a match to job names DB2, DB2AAA, DB2BBB, PL, PL1, and so on. “PL3” is removed from the resultant list because “PL” is more generic, and message SCF4382I is issued to indicate the removal.

Possible valuesA list of comma-separated values, each up to 8 characters.

Default Job names supplied in SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST. If SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST is not specified, no job name filtering is performed.



ExampleSCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST=MYJOB

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE

DescriptionDefines the quiesce point for the number of constituent I/Os active for the same base device.

Note: “Setting quiesce points” on page 514 discusses setting quiesce points.

The value cannot exceed the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL and/or SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU parameter value (if specified).

Possible values0-256. “0” is the same as specifying no value.

Default None.

ExampleTo allow zBoost PAV Optimizer to create up to 16 active constituent I/Os on each base device:

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE=16

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL

DescriptionDefines the quiesce point for the number of globally active constituent I/Os.


Possible valuesAny whole number starting from 0 (zero). “0” is the same as specifying no value.

Default None.

ExampleTo allow zBoost PAV Optimizer to create up to 5000 active constituent I/Os:

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL=5000



SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU

DescriptionDefines the quiesce point for the number of constituent I/Os active for the same LCU.


The value cannot exceed the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL parameter value (if specified).


Default None.

ExampleTo allow zBoost PAV Optimizer to create up to 34 active constituent I/Os on each LCU:

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU=34

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT

DescriptionDefines the LCU quiesce point as a percentage of configured HyperPAV alias devices for each LCU.


The resultant value is set for each LCU and can be different depending on how many HyperPAV configured aliases are defined to the LCU. Once the value is calculated, the operation of this value is similar to SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.

Note: For non-HyperPAV LCUs, the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT parameter value is ignored and the value set in the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU parameter is used.

If the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT parameter value exceeds the global value set with the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL parameter, then the global value dictates resource usage.


Default None.



ExampleTo allow zBoost PAV Optimizer to create up to 16 active constituent I/Os on an LCU with 32 configured HyperPAV alias devices:

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT=50

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX

DescriptionSets a default value to be used as the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ and/or SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE value when one or both of these parameters are not specified.

Note: “Controlling number of splits/constituent I/Os” on page 513 discusses use of SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX, SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ, and SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE parameters.

Possible values1-256. Specifying 0 (zero) is the same as not specifying the value at all.

Default None.

ExampleTo allow a maximum of 9 channel programs when the maximum allowed value is not specified separately for read and write operations with SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ and/or SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE:

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX=9

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ

DescriptionDefines the maximum number of splits/constituent channel programs created by zBoost PAV Optimizer for read operations.

Note: “Controlling number of splits/constituent I/Os” on page 513 discusses how to control the number of splits.

If not specified, the value set with the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX parameter is used.

Possible values0-256

A value of 0 can be used to split by the number of tracks; that is, each split will be of a single track.



Default 2

ExampleTo let zBoost PAV Optimizer create a maximum of 3 constituent channel programs for read operations:

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ=3

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE

DescriptionDefines the maximum number of splits/constituent channel programs created by zBoost PAV Optimizer for write operations.

Note: “Controlling number of splits/constituent I/Os” on page 513 discusses how to control the number of splits.

If not specified, the value set with the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX parameter is used.

Possible values0-256

A value of 0 can be used to split by the number of tracks; that is, each split will be of a single track.

Default 2

ExampleTo let zBoost PAV Optimizer create a maximum of 4 constituent channel programs for write operations:

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE=4

SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST

DescriptionSelects the devices on which zBoost PAV Optimizer operates by specifying the name of the SMS storage group that contains the devices.






Possible valuesA list of comma-separated SMS group names

Default None. No devices are included by default.

ExampleSCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST=PRODGRP,PLGROUP

SCF.DEV.OPTIMIZE.PAV.TRACK.MIN

DescriptionSets a default value to be used as the SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ and/or SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE value when one or both of these parameters is not specified.

Note: “Limiting optimization by tracks” on page 513 discusses use of SCF.DEV.OPTIMIZE.PAV.TRACK.MIN, SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ, and SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE parameters.

Possible values1-1000. A value greater than 1000 will result in a value of 1000 being used. Specifying 0 (zero) is the same as not specifying the value at all.

Default None.

ExampleSCF.DEV.OPTIMIZE.PAV.TRACK.MIN=5

SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ

DescriptionDefines the minimum number of tracks before PAV optimization is considered on read channel programs.

Note: “Limiting optimization by tracks” on page 513 discusses limitation by the number of tracks.

If not specified, the value set with the SCF.DEV.OPTIMIZE.PAV.TRACK.MIN parameter is used.



Possible values0-1000. A value greater than 1000 will result in a value of 1000 being used.

Default 0 (no minimum track number)

ExampleSCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ=5

SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE

DescriptionDefines the minimum number of tracks before PAV optimization is considered on write channel programs.

Note: “Limiting optimization by tracks” on page 513 discusses limitation by the number of tracks.

If not specified, the value set with the SCF.DEV.OPTIMIZE.PAV.TRACK.MIN parameter is used.

Possible values0-1000. A value greater than 1000 will result in a value of 1000 being used.

Default 0 (no minimum track number)

ExampleSCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE=5

SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST

DescriptionSelects the volumes on which zBoost PAV Optimizer operates by applying a volser mask.






Possible valuesA volume mask or a comma-separated list of volume masks. Each mask may contain “?” characters to signify positions for which any character will match or “*” to indicate 0-n positions of match.

Default None. No volsers are included by default.

Example◆ To include volumes PAL001, PAL002 but not PAL1 or PAL2:

SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST=PAL???

Note: “PAL???” matches only 6-character values starting with “PAL” but does not match a shorter value because 6 characters are specified for the mask.

◆ To include volumes PAL001, PAL002 and also PAL1, PAL2, and PAL:

SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST=PAL*

Note: “PAL*” matches any value starting with “PAL”, including “PAL” itself.

◆ To include volumes DJJ, DJJ100, DBJ2 but not DJB, DJ:

SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST=D?J*

SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST

DescriptionSelects the volumes on which zBoost PAV Optimizer operates by listing specific volsers.


Use of SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST allows the specification of individual volsers containing characters that would otherwise be considered mask characters.



Possible valuesA volser or a comma-separated list of volsers

Default None. No volsers are included by default.

ExampleSCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST=PAL1



SCF.DEV.OPTIMIZE.SMF.RECID

DescriptionDetermines whether SMF processing is to be performed and, if so, the SMF record ID.

◆ NO — No SMF recording takes place. You may also specify “OFF” or “0” (zero).

◆ smf_record_id — Specify an SMF record ID in the range from 128 to 255.

Since the default SMF RECID for the SMF reporting utility is 203, if you specify 203 for SCF.DEV.OPTIMIZE.SMF.RECID then you do not have to specify the RECID control statement in the report utility.

Note: “SMF recording” on page 516 describes SMF recording for zBoost PAV Optimizer.

Possible valuesNO|smf_record_id

Default NO

ExampleSCF.DEV.OPTIMIZE.SMF.RECID=130

SCF.DEV.OPTIMIZE.VERBOSE

DescriptionEnables or disables display of certain zBoost PAV Optimizer messages.

◆ When set to YES, additional information messages are displayed on the console at startup and following configuration changes. For example, one SCF4356I message will be issued on the console for each device eligible for PAV optimization.

◆ When set to NO, the verbose messages are not displayed on the console (but still appear in the SCFLOG).

For example, the routine startup messages will be reduced to something like:

SCF4358I DEV OPTIMIZE.PAV updated 0, set 12082, reset 0, state changed 0 devices

Note: Summary and exception messages appear on the console regardless of the SCF.DEV.OPTIMIZE.VERBOSE setting.


Default NO



ExampleSCF.DEV.OPTIMIZE.VERBOSE=YES

SCF.DEV.WAITINT

DescriptionSCF.DEV.WAITINT specifies the device discovery check interval (in minutes).


Default60

Example

SCF.DEV.WAITINT=45

SCF.DSE.LIST

DescriptionThis general purpose statement allows you to enable or disable the DSE Capacity monitor. The DSE Capacity monitor periodically examines the consumed capacity of the DSEPOOL used by SRDF/A.

Note: If the DSE Capacity monitor is disabled, it will not monitor anything. However, it will respond to commands. In particular, if a request is made to enable the monitor, it will respond to the request and activate. If disabled, the monitor will enter a 12-hour wait period and then immediately enter another 12-hour wait.


DefaultDISable

Example

SCF.DSE.LIST=ENABLE

SCF.DSE.xx.LIST

DescriptionThis global interval statement provides a default setting for interval monitoring.

The xx represents the threshold interval to which the parameters apply. This value must start at 01 and increase by one for each separate interval. Gaps are not permitted in the sequence.



Refer to “Save Device Capacity monitor syntax” on page 423 for an explanation of all the available parameters that can apply to this parameter.

DefaultNone

Example

SCF.DSE.01.LIST = PERCENT=(0,10)SCF.DSE.01.LIST = DURATION=60SCF.DSE.01.LIST = ACTION=NONESCF.DSE.01.LIST = FREQUENCY=NONE

SCF.DSE.<cntrl#>.LIST = ENAble | DISable

DescriptionThis controller statement allows the DSE Capacity monitor to be enabled on individual controllers. Valid options are:

Note: If the monitor is disabled, it will not monitor anything. However, it will respond to commands. In particular, if a request is made to enable the monitor, it will respond to the request and activate. If disabled, the monitor will enter a 12-hour wait period and then immediately enter another 12-hour wait.


DefaultNone

Example

SCF.DSE.18771.LIST = DIS

SCF.DSE.<cntrl#>.LIST = GATEkeeper=ccuu

DescriptionThe controller statement allows the DSE Capacity monitor to use a special gatekeeper device.

DefaultNone

<cntrl#> Specifies the 5- or 12-digit Symmetrix serial number used to find the gatekeeper device. You can use the 5-digit serial number when the last 5 digits are not duplicated with another controller. Specify the full 12-digit serial number when multiple controllers have the same last 5 digits.




Example

SCF.DSE.18771.LIST = GATE=42F1

SCF.DSE.<cntrl#>.xx.LIST

DescriptionThe controller interval statements provide the interval setting for individual controllers.

DefaultNone

Example

SCF.DSE.18771.01.LIST = PERCENT=(0,10)SCF.DSE.18771.01.LIST = DURATION=10SCF.DSE.18771.01.LIST = ACTION=MES(GOOD)SCF.DSE.18771.01.LIST = FREQUENCY=ONCE

SCF.DSE.<cntrl#>.poolname.xx.LIST

DescriptionThe pool interval statements provide the interval setting for individual pools within a controller.

DefaultNone

Example

SCF.DSE.18771.TESTPOOL.01.LIST = PERCENT=(0,10)SCF.DSE.18771.TESTPOOL.01.LIST = DURATION=10SCF.DSE.18771.TESTPOOL.01.LIST = ACTION=(DSE1)SCF.DSE.18771.TESTPOOL.01.LIST = FREQUENCY=REPEAT

SCF.DSE.WARNING

DescriptionSCF.DSE.WARNING specifies the threshold value, in number of minutes, to issue an alert that DSE spillover has been occurring. Valid values are 02 to 720 inclusive.

DefaultNone

Example

SCF.DSE.WARNING = 20



SCF.DSE.MINOR

DescriptionSCF.DSE.MINOR specifies the threshold value, in number of minutes, to issue an alert that DSE spillover has been occurring. Valid values are 02 to 720 inclusive. This value must exceed the value of SCF.DSE.WARNING.

DefaultNone

Example

SCF.DSE.MINOR = 40

SCF.DSE.MAJOR

DescriptionSCF.DSE.MAJOR specifies the threshold value, in number of minutes, to issue an alert that DSE spillover has been occurring. Valid values are 02 to 720 inclusive. This value must exceed the value of SCF.DSE.MINOR.

DefaultNone

Example

SCF.DSE.MAJOR = 60

SCF.GATEKEEPER.LIST

DescriptionSCF.GATEKEEPER.LIST allows you to define gatekeepers to SCF.

SCF will choose one of the user-defined gatekeepers. If SCF determines that a device it has chosen to use as a gatekeeper is inappropriate (for example, if it is busy or invalid), it will issue a message indicating the device was not used. SCF will then attempt to select another gatekeeper from the list. If SCF determines that the suggested gatekeepers are not usable, then SCF will select the first usable device from the first ssid on the controller.

If the user does not provide any gatekeepers, then SCF will default to the first device discovered for the controller.

Possible valuesz/OS device numbers (cuus)

Default

None

Example

SCF.GATEKEEPER.LIST=A02A



SCF.GATEKEEPER.<cntrl#>.LIST

DescriptionSCF.GATEKEEPER.<cntrl#>.LIST is an alternate form of specifying gatekeeper devices to SCF. The SCF.GATEKEEPER.<cntrl#>.LIST parameter allows you to choose specific Symmetrix devices for a specific Symmetrix controller.

Note: If both forms of gatekeeper definition are used, then the device lists will be merged.

You can specify the Symmetrix controller with either the 5-digit or 12-digit Symmetrix controller ID. (Use the 12-digit ID when multiple controllers use the same last 5 digits.) If a gatekeeper device cannot be located from the gatekeeper list, then SCF will select the first usable device from the first ssid on the controller. If the user does not provide any gatekeepers for a controller, then SCF will default to the first device discovered for the controller.

Gatekeeper devices are reprocessed whenever you enter the DEV,REFRESH[,GATEKEEPERS] command. If the gatekeeper list changes, then issue the INI,REFRESH operator command before you issue the DEV,REFRESH[,GATEKEEPERS] command.

Possible valuesSymmetrix device numbers

DefaultNone

Example

SCF.GATEKEEPER.011203211419.LIST=0000

SCF.GNS.ACTIVE

DescriptionSCF.GNS.ACTIVE specifies whether the Group Name Services (GNS) is active. If you set SCF.GNS.ACTIVE to NO or do not specify SCF.GNS.ACTIVE, GNS does not start. If you set SCF.GNS.ACTIVE to YES, GNS is active.

Note: If you set SCF.GNS.ACTIVE to YES, set SCF.CSC.ACTIVE to YES also. “SCF.CSC.ACTIVE” on page 68 describes this parameter.


DefaultNO

Example

SCF.GNS.ACTIVE=YES



SCF.GNS.WAITINT

DescriptionSCF.GNS.WAITINT specifies the number of seconds between automatic refresh of in-memory GNS tables.

Note: If in a mixed environment that contains both open systems and mainframe groups, EMC recommends a periodic refresh.


Default1800

Example

SCF.GNS.WAITINT=2000

SCF.INI.COMMAND.MAX

DescriptionSets the maximum number of concurrent operator commands that can be accepted by SCF before displaying the SCF0330E message.


Default255

Example

SCF.INI.COMMAND.MAX=1000

SCF.INI.CPFX

DescriptionThe Command Prefix Facility (CPF) for SCF allows you to define and control subsystem and other command prefixes for use in a sysplex. You can enter SCF commands using CPF rather than using the MODIFY command. For example, if the CPF name is @123, then the command F scf,INI,RELOAD can be entered as @123 INI,RELOAD.

SCF.INI.CPFX=name specifies the command prefix for SCF where name is a character string up to 8 characters.

Possible values1 to 8 characters; characters can be:



◆ Any uppercase letters A through Z, or lowercase letters a through z

◆ Any numeric values 0 through 9

◆ National characters; @ $ # (Characters that can be represented as hexadecimal values X'7C', X'5B', and X'7B', respectively)

◆ Special characters; / ( ) * & + - = ¢ < | ! ; % _ ? : >

Note: If one or more special characters is used in the name, then the name must be enclosed in single quotes.

DefaultCommand Prefix Facility (CPF)

//SCF$nnnn DD DUMMY, nnnn will become the default CPF other than value SCF$EMC. IF you want EMC as the CPF then SCF.INI.CPFX=EMC must be found in the SCF INI file.

ExampleSCF.INI.CPFX=@123

SCF.INI.CPFX.DD

DescriptionAllows Default Command Prefix Facility (CPF) to be activated.

DefaultNO (Command Prefix Facility is not activated)

Note: See “SCF.INI.CPFX” on page 98 for more information.

ExampleSCF.INI.CPFX.DD=YES (to activate)

SCF.INI.SCOPE

DescriptionWhen the SCF.INI.CPFX parameter is used to define a command prefix, the SCF.INI.SCOPE parameter specifies the range of systems to which a command with this prefix can be routed for execution. The values are:

◆ SYSPLEX - the command issued can be routed to another system in the sysplex for execution. If SCOPE is not specified, this is the default.

◆ SYSTEM - the command issued will execute in the system LPAR on which the command is entered.



Possible valuesSYSTEM|SYSPLEX

DefaultSYSPLEX

ExampleSCF.INI.SCOPE=SYSPLEX

SCF.LFC.LCODES.LIST

DescriptionSCF.LFC.LCODES.LIST specifies the Licensed Feature Code(s) for optional product capabilities.

For Symmetrix systems running Enginuity 5875 or higher, Mainframe Enablers introduces support for Electronic Licensing (eLicensing). With the introduction of eLicensing, Symmetrix licensing is moving from a host-based model to a Symmetrix-based model, with the majority of licenses now being stored in a feature registration database on the Symmetrix system. However, there are still a number of Symmetrix licenses that remain host-based.

For these remaining host-based licenses and for Symmetrix systems running Enginuity level 5874 or lower, EMCSCF manages licensed feature codes (LFCs) to enable separately chargeable features in EMC software. These features require an LFC to be provided during the installation and customization of EMCSCF. The EMC Mainframe Enablers Installation and Customization Guide lists the LFCs for the Mainframe Enablers components.

Possible valuesLicensed Feature Code(s)

DefaultNone

Example

SCF.LFC.LCODES.LIST=xxxx-xxxx-xxxx-xxxx

SCF.LOG.CYLINDER

DescriptionThis parameter overrides the SCF.LOG.TRACKS.PRI and the SCF.LOG.TRACKS.SEC parameters to allocate in cylinders instead of tracks.

Possible Values Yes/No



DefaultNo

ExampleSCF.LOG.CYLINDER=Y

SCF.LOG.DATACLAS

DescriptionSCF.LOG.DATACLAS specifies the SMS data class name to be used when allocating the SCF log file.

Possible values1 to 8 characters

DefaultNone

Example

SCF.LOG.DATACLAS=PATLOAD

SCF.LOG.MGMTCLAS

DescriptionSCF.LOG.MGMTCLAS specifies the SMS management class name to be used when allocating the SCF log file.


DefaultNone

Example

SCF.LOG.MGMTCLAS=FILETRIM

SCF.LOG.RETAIN.COUNT

DescriptionSCF.LOG.RETAIN.COUNT specifies the number of SCF log files to retain.




Default10

Example

SCF.LOG.RETAIN.COUNT=20

SCF.LOG.RETAIN.DAYS

DescriptionSCF.LOG.RETAIN.DAYS specifies the number of days to retain an SCF log file.


Default10

Example

SCF.LOG.RETAIN.DAYS=30

SCF.LOG.STORCLAS

DescriptionSCF.LOG.STORCLAS specifies the SMS storage class name to be used when allocating the SCF log file.


DefaultNone

Example

SCF.LOG.STORCLAS=LOGTERM

SCF.LOG.TRACKS.PRI

DescriptionSCF.LOG.TRACKS.PRI specifies the primary allocation (in tracks) used to create the SCF log file.


Default10



Example

SCF.LOG.TRACKS.PRI=12

SCF.LOG.TRACKS.SEC

DescriptionSCF.LOG.TRACKS.SEC specifies the secondary allocation (in tracks) used to create the SCF log file.


Default50

Example

SCF.LOG.TRACKS.SEC=45

SCF.MSC.ADCOPY.ONDROP

Description SCF.MSC.ADCOPY.ONDROP set to YES indicates that MSC will issue the following command to each SRDF group in the MSC group after an SRDF/A failure:

SC VOL,LCL(DDDD,RA#),ADCOPY-DISK,ALL,CQNAME=MSC_GROUP

Where DDDD is the MSC gatekeeper device, RA# is the SRDF group, and MSC_GROUP is the first eight bytes of the MSC group name.


Default NO

Example

SCF.MSC.ADCOPY.ONDROP=YES

SCF.MSC.AUTO.RECOVER.RETRY

Description When Auto Recovery Retry is enabled, the status of each SRDF/A Group is checked at the completion of the Phase 1 recovery jobs. If the retry limit has not been reached, Auto Recovery is re-run for each inactive Group.

This enhancement is enabled with the following SCF Initialization parameter:

SCF.MSC.AUTO.RECOVER.RETRY=n



Where n equals values from 0-9 (0 disables Auto Recovery retry).

Possible values 0-9 (An invalid value results in a limit of 1.)

Default No default value

ExampleSCF.MSC.AUTO.RECOVER.RETRY=5

SCF.MSC.CYCLE.TIME.WARN

DescriptionSCF.MSC.CYCLE.TIME.WARN specifies the interval at which the system will issue a warning message. The interval can be set from 5 minutes to 60 minutes. If the time since the last cycle switch exceeds the specified value, message SCF1591W is issued. This message will be issued as many as 24 times.

Note: The detection of this delay in cycle time is checked in the same routine that is checking if SRDF/A is active for each SRDF group. This means the check is only performed approximately every 30 seconds in a situation where some SRDF groups cannot cycle switch.


Default60

Example

SCF.MSC.CYCLE.TIME.WARN=10

SCF.MSC.ENABLE

DescriptionSCF.MSC.ENABLE set to YES activates the MSC environment. The MSC environment controls the SRDF/A cycle switching from the host when SRDF Host Component creates an SRDF/A MSC group.

SCF.MSC.ENABLE set to NO suppresses MSC environment activation.

Note: If YES is specified, MSC must be disabled to shut down SCF.




DefaultNO

Example

SCF.MSC.ENABLE=YES

SCF.MSC.GTFUSR.RECID

DescriptionThis parameter is used to specify the GTF USR record number when SCF.MSC.GTFUSR.TRACE is set to YES.

Note: This value is also specified in the GTF USRP field.

Possible values0 - 3FF (hex)

Default100 (hex)

ExampleSCF.MSC.GTFUSR.RECID=128

SCF.MSC.GTFUSR.TRACE

DescriptionWhen this parameter is set to YES, GTF USR tracing is enabled. The GTF (Generalized Trace Facility) is a service aid for recording and diagnosing system and program problems.

Note: Collection of GTF user records also requires GTF to be active with the TRACE=USRP and USRP=(nnn) parameters specified.


DefaultNO

ExampleSCF.MSC.GTFUSR.TRACE=YES



SCF.MSC.MAX.LOCK.WAIT

DescriptionWhen running MSC with high availability, and when not sharing system enqueues, the Symmetrix level lock that is received to update certain structures can be stolen since it takes longer than one minute to initialize the SDDF structures. This parameter allows you to change the default time to hold the lock from 1 minute to a value between 1 and 720 minutes.


Default1

Example

SCF.MSC.MAX.LOCK.WAIT=30

SCF.MSC.PAVO

DescriptionEnables (YES) or disables (NO) zBoost PAV Optimizer support for MSC.

Note: “zBoost PAV Optimizer” on page 505 discusses zBoost PAV Optimizer.

When zBoost PAV Optimizer support is enabled, each R1 controller in the MSC configuration (5876 and higher with zBoost) will be messaged internally before and after the cycle switch to suspend/resume zBoost PAV Optimizer write optimization.


DefaultNO

Example

SCF.MSC.PAVO=YES

SCF.MSC.OVERWRITE

DescriptionIf SCF.MSC.OVERWRITE is set to YES, the MSC overwrite logic will allow MSC to overwrite scratch areas and multi-box lists. This allows MSC or SRDF/Star to start when valid data is found in these areas.



If valid scratch data is found, message SCF147AR is returned to allow you to overwrite the area.

◆ A reply of ALL will delete each of the scratch areas found for all of the SRDF groups participating in the MSC sessions.

◆ A reply of YES will delete only the SRDF group currently displayed in the message.

◆ A reply of NONE will bypass the overwrite and stop the start-up process.

Once the scratch area data has been completed, message SCF147BR is returned to allow you to overwrite the data in the multi-box lists in a similar manner.


DefaultNO

Example

SCF.MSC.OVERWRITE=YES

SCF.MSC.SDDFQ.TODA

Description If SCF.MSC.SDDFQ.TODA is set to YES, then the code will look for patch 30489 (released at Enginuity 5671.51.58 and higher) on SRDF/Star site A, site B, and site C. If the patch is not present on all three Symmetrix systems, the code will issue message SCF1565W. If the patch is present on all three Symmetrix systems, then remote SDDF queries will be run to the disk adapter(s).


DefaultNO

Example

SCF.MSC.SDDFQ.TODA=YES

SCF.MSC.SDDFQ.TOMF

Description If this parameter is set to YES, then the code will look for mainframe host adapter(s). If none are present, the code will issue message SCF1566W. If any are found, remote SDDF queries will be run to the mainframe host adapter(s).




DefaultNO

Example

SCF.MSC.SDDFQ.TOMF=YES

More informationRefer to the note on page 107.

SCF.MSC.SDDFQ.TOOS

Description If this parameter is set to YES, then the code will look for open system host adapter(s). If none are present, the code will issue message SCF1567W. If any are found, remote SDDF queries will be run to the open system host adapter(s).


DefaultNO

Example

SCF.MSC.SDDFQ.TOOS=YES

More informationRefer to the note on page 107.

Comments on use of the SCF.MSC.SDDFQ.TODA, .TOMF, and .TOOS parametersThe SCF.MSC.SDDFQ.TODA, SCF.MSC.SDDFQ.TOMF, and SCF.MSC.SDDFQ.TOOS parameters are mutually exclusive, but are examined in this sequence. Once one parameter is found true, then the others are ignored. If none of these parameters are found, then remote SDDF queries will run on the remote RDF director (RA).

SCF.MSC.SDDFQ.TODA, SCF.MSC.SDDFQ.TOMF, and SCF.MSC.SDDFQ.TOOS specify where to direct remote SDDF query requests for MSC SRDF/Star processing. For compatibility, the default setting is to direct the remote SDDF queries to the RAs. Directing the queries to other directors will reduce the impact on non-MSC SRDF/Star RDF processing.

An initial recommendation is to specify TODA when running with the necessary Enginuity level (see the “SCF.MSC.SDDFQ.TODA” parameter). When TODA is not possible, then specify either TOMF for mainframe or TOOS for open systems. The specified setting must be valid for all Symmetrix systems in the MSC session.



SCF.MSC.VERBOSE

DescriptionSCF.MSC.VERBOSE=YES enables the display of MSC/Star process status messages. These messages are intended for reference when diagnosing a processing problem, and are not intended for customer tracking or message automation. If you set SCF.MSC.VERBOSE to NO, the display of these messages is not enabled.

Note: Set this parameter only when requested by EMC Customer Support.


Default NO

SCF.PDVHC.WAITINT

DescriptionSCF.PDVHC.WAITINT specifies the health checker wait interval (in minutes). This interval determines how often the health checker task will check all the devices in the SARPOOLs. You can initiate the health checker task at any time by issuing the REFRESH command, which forces the system to perform health checking immediately.


Default30

Example

SCF.PDVHC.WAITINT=120

SCF.REG.MAX.CONTROLLER.ERRORS

DescriptionSCF.REG.MAX.CONTROLLER.ERRORS specifies the maximum allowable number of controller errors. When this value is reached, registration is disabled for the controller.


Default3



Example

SCF.REG.MAX.CONTROLLER.ERRORS=300

SCF.REG.MAX.ERRORS

DescriptionSCF.REG.MAX.ERRORS specifies the maximum allowable number of total errors. When this value is reached, registration is disabled.


Default9

Example

SCF.REG.MAX.ERRORS=300

SCF.REG.WAITINT

DescriptionSCF.REG.WAITINT specifies the registration check wait interval (in minutes).


Default30

Example

SCF.REG.WAITINT=10

SCF.SDV.LIST

DescriptionThis general purpose statement allows you to enable or disable the Save Device Capacity monitor. The monitor periodically examines the consumed capacity of the SNAPPOOL used by TimeFinder/Snap with the VDEV feature enabled.

Note: If the Save Device Capacity monitor is disabled, it will not monitor anything. However, it will respond to commands. In particular, if a request is made to enable the monitor, it will respond to the request and activate. If disabled, the monitor will enter a 12-hour wait period and then immediately enter another 12-hour wait.




DefaultDISable

Example

SCF.SDV.LIST=ENABLE

SCF.SDV.<cntrl#>.LIST

DescriptionThis controller statement allows the Save Device Capacity monitor to be enabled or disabled on individual controllers.

Note: If the monitor is disabled, it will not monitor anything. However, it will respond to commands. In particular, if a request is made to enable the monitor, it will respond to the request and activate. If disabled, the monitor will enter a 12-hour wait and then immediately enter another 12-hour wait.


DefaultDISable

Example

SCF.SDV.18773 = ENABLE

SCF.SDV.<cntrl#>.LIST = GATEkeeper=ccuu

DescriptionThis controller statement allows the Save Device Capacity monitor to use a special gatekeeper device.


DefaultNone

Example

SCF.SDV.18773.LIST = GATE=423F



SCF.SDV.xx.LIST

DescriptionThis statement provides a default setting for interval monitoring.

DefaultNone

Example

SCF.SDV.01.LIST = PERCENT=(0,50)SCF.SDV.01.LIST = DURATION=10SCF.SDV.01.LIST = ACTION=MESSAGE(GOOD)SCF.SDV.01.LIST = FREQUENCY=NONE

SCF.SDV.<cntrl#>.xx.LIST


DefaultNone

Example

SCF.SDV.18771.02.LIST = PERCENT=(25,50)SCF.SDV.18771.02.LIST = DURATION=10 SCF.SDV.18771.02.LIST = ACTION=(SAVEDEV1)SCF.SDV.18771.02.LIST = FREQUENCY=REPEAT

SCF.SDV.<cntrl#>.poolname.xx.LIST


DefaultNone

Example

SCF.SDV.18771.SAVEPOOL.03.LIST = PERCENT=(50,75)SCF.SDV.18771.SAVEPOOL.03.LIST = DURATION=5SCF.SDV.18771.SAVEPOOL.03.LIST = ACTION=MES(FIFTY)SCF.SDV.18771.SAVEPOOL.03.LIST = FREQUENCY=REPEAT



SCF.SNAP.NOTIFY_POLLING

DescriptionThis statement specifies the amount of time (in seconds) that the SNAP monitor waits between scans to see if SNAP requests have finished when the NOTIFY option was used in the request. Shorter intervals will result quicker notification at the cost of more I/O.


Default1

Example

SCF.SNAP.NOTIFY_POLLING=900

SCF.SNAP.NOTIFY_POLLTIME

DescriptionThis statement allows you to specify the delay, in seconds, between notification polls.

Default1

Example

SCF.SNAP.NOTIFY_POLLTIME=60

More informationThe NOTIFYwhencomplete parameter in the EMC TimeFinder/Clone Mainframe Snap Facility Product Guide provides additional information.

SCF.SRV.GSM.ACTIVE

DescriptionEnables Global State Management (GSM), where EMCSCF notifies other Mainframe Enabler applications, such as ConGroup, when a configuration change has occurred for the specified controller. Either the controller was newly discovered, its microcode level has changed, new devices were discovered, existing devices were removed, a UCB swap occurred, or a combination of these events.


DefaultYES



Example

SCF.SRV.GSM.ACTIVE=NO

SCF.SRV.GSM.INTERVAL

DescriptionWhen Global State Management (GSM) is enabled, the interval value sets the number of seconds for EMCSCF to notify other Mainframe Enablers applications, such as ConGroup, of a configuration change to a specified controller.

Possible valuesNumber of seconds

Default15

Example

SCF.SRV.GSM.INTERNAL=20

SCF.SS.AUTO.RECOVER

DescriptionIf SCF.SS.AUTO.RECOVER is enabled, the ASY monitor will initiate auto recovery for single session SRDF/A groups that have changed state from active to inactive. If ENABLE(MANUAL) is specified, the ASY monitor will detect the active to inactive state change but recovery will not be initiated. In this case, you must initiate the recovery procedure manually.

Possible valuesENABLE[(MANUAL)]|DISABLE

DefaultNone

Example

SCF.SS.AUTO.RECOVER=ENABLE

SCF.SS.AUTO.RECOVER.ser#.rdfg#=option

Description This optional parameter allow you to specify the control unit (ser#) and SRDF group (rdfg#) to be automatically recovered. Only the indicated SRDF group will be recovered. If you want to recover multiple SRDF groups, you must specify each group in a separate parameter statement. If this parameter is not used, then all single session SRDF/A groups will be automatically recovered.



Possible values ser#

A 12-digit Symmetrix serial number.

rdfg#

Specifies an SRDF group number. Valid values are 0 to F9 (hex).

option

Y — This group can be recovered. All other values will be ignored.

Default None

Example

SCF.SS.AUTO.RECOVER.000192600262.B9=Y

SCF.SS.AUTO.RECOVER.BCV= BCV(startup_option,post_recovery_option)

DescriptionThis required parameter specifies BCV gold copy management options for all control units.

Note: This parameter is only required if SCF.SS.AUTO.RECOVER=ENABLE.

Possible valuesstartup_option

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

• NONE — BCV management will be bypassed for this phase.

• ESTablish — Results in a new PiT (point-in-time) copy on the BCVs. If a BCV is not attached to an R2, a BCV is re-established. If a relationship does not exist, BCV processing cannot be done and an error message is issued. After all the BCVs are attached, they will be split.

post_recovery_option

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


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

DefaultNone



Example

SCF.SS.AUTO.RECOVER.BCV=BCV(EST,EST)

SCF.SS.AUTO.RECOVER.BCV.ser#.rdfg#=BCV(startup_option,post_recovery_option)

DescriptionThis optional parameter overrides the global parameter and specifies BCV gold copy management options for one particular SRDF group.

Possible valuesser#

A 12-digit Symmetrix serial number.

rdfg#

Specifies the SRDF group. Valid values are 0 to F9 (hex).

startup_option

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


• ESTablish — Results in a new PiT (point-in-time) copy on the BCVs. If a BCV is not attached to an R2, a BCV is re-established. If a relationship does not exist, BCV processing cannot be done and an error message is issued. After all the BCVs are attached, they will be split.

post_recovery_option

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


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

DefaultNone

Example

SCF.SS.AUTO.RECOVER.BCV.000190300344.3=BCV(EST,EST)

SCF.SS.AUTO.RECOVER.ITRK=itrk

DescriptionThis is a global parameter that is set for all control units. This required parameter indicates the number of outstanding R2 invalid tracks on the R1 side that the recovery automation uses as a trigger point for activating SRDF/A for this session, where the value of itrk is multiplied bt 1000.




Possible valuesitrk

Specifies the invalid track count. Valid values are 1-99999.

DefaultThe default setting is 30 (which represents 30 x 1000 = 30,000).

Example

SCF.SS.AUTO.RECOVER.ITRK=500

SCF.SS.AUTO.RECOVER.ITRK.ser#=itrk

DescriptionThis optional parameter applies only to the control unit specified by ser#. It indicates the number of outstanding R2 invalid tracks on the R1 side that the recovery automation uses as a trigger point for activating SRDF/A for this session, where the value of itrk is the number of tracks. This parameter will override the “SCF.SS.AUTO.RECOVER.ITRK=itrk” global parameter.

Possible valuesser#

Is a 12-digit Symmetrix serial number.

itrk

Specifies the invalid track count. Valid values are 1-99999.

DefaultNone

Example

SCF.SS.AUTO.RECOVER.ITRK.000190300344=2000

SCF.SS.AUTO.RECOVER.JOBNAME=jobname

DescriptionThis required parameter specifies the jobname to be used when the auto recovery is initiated.


Possible valuesjobname



Is a user-defined name.

DefaultNone

Example

SCF.SS.AUTO.RECOVER.JOBNAME=SSARJOB

SCF.SS.AUTO.RECOVER.JOBNAME.ser#=jobname

DescriptionThis optional parameter overrides the global parameter and specifies the jobname to be used for a particular control unit when the auto recovery is initiated.

Possible valuesser#


jobname

Is a user-defined name.

DefaultNone

Example

SCF.SS.AUTO.RECOVER.JOBNAME.000190300344=UNITJOB

SCF.SS.AUTO.RECOVER.LPAR=id

DescriptionThis required parameter should be used in all SCF initialization files and will ensure that SRDF/A Single Session Auto Recovery is only enabled on a single LPAR matching this variable. This parameter ensures that multiple SCF systems do not start auto recovery.


Possible values id

Indicates the unique LPAR ID for the system that will be responsible for running the recoveries.

DefaultNone



Example

SCF.SS.AUTO.RECOVER.LPAR=X118

SCF.SS.AUTO.RECOVER.MINDIR=##

DescriptionThis required parameter indicates the number of directors that must be online for all control units.


Possible values##

Indicates the minimum director count. Valid values are 1-255.

DefaultNone

Example

SCF.SS.AUTO.RECOVER.MINDIR=1

SCF.SS.AUTO.RECOVER.MINDIR.ser#=##

DescriptionThis optional parameter indicates the number of directors that must be online for the control unit specified by ser#. This parameter will override the global parameter, “SCF.SS.AUTO.RECOVER.MINDIR=##”.

Possible valuesser#


##

Indicates the minimum director count. Valid values are 1-255.

DefaultNone

Example

SCF.SS.AUTO.RECOVER.MINDIR.000190300344=2



SCF.SS.AUTO.RECOVER.PREFIX=hccpfx

DescriptionThis required parameter allows you to specify the SRDF Host Component command prefix to be used by the auto recovery job.


Possible valueshccpfx

Indicates the SRDF Host Component command prefix, in single quotes.

DefaultNone

Example

SCF.SS.AUTO.RECOVER.PREFIX='OCT'

SCF.SS.AUTO.RECOVER.PROC=procname

DescriptionThis required parameter allows you to change the name of the JCL recovery procedure.


Possible valuesprocname

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

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

DefaultNone

Example

SCF.SS.AUTO.RECOVER.PROC=EMCRCVRY



SCF.THN.LIST

DescriptionThis general purpose statement allows you to enable or disable the Thin Pool Capacity Monitor. The monitor periodically examines the consumed capacity of the thin pools.

The Thin Pool Capacity Monitor is enabled by default.

Note: If the Thin Pool Capacity Monitor is disabled, it will not monitor anything. However, it will respond to commands. In particular, if a request is made to enable the monitor, it will respond to the request and activate. If disabled, the monitor will enter a 12-hour wait period and then immediately enter another 12-hour wait.


DefaultENAble

Example

SCF.THN.LIST=ENABLE

SCF.THN.<cntrl#>.LIST

DescriptionThis controller statement allows the Thin Pool Capacity Monitor to be enabled or disabled on individual controllers.

Note: If the monitor is disabled, it will not monitor anything. However, it will respond to commands. In particular, if a request is made to enable the monitor, it will respond to the request and activate. If disabled, the monitor will enter a 12-hour wait and then immediately enter another 12-hour wait.


DefaultNone

Example

SCF.THN.18773.LIST=ENABLE



SCF.THN.<cntrl#>.LIST = GATEkeeper=ccuu

DescriptionThis controller statement allows the Thin Pool Capacity Monitor to use a special gatekeeper device.


DefaultNone

Example

SCF.THN.18773.LIST = GATE=423F

SCF.THN.xx.LIST

DescriptionThis statement provides a default setting for interval monitoring.

DefaultNone

Example

SCF.THN.01.LIST = PERCENT=(0,50)SCF.THN.01.LIST = DURATION=10SCF.THN.01.LIST = ACTION=MESSAGE(GOOD)SCF.THN.01.LIST = FREQUENCY=NONE

SCF.THN.<cntrl#>.xx.LIST


DefaultNone

Example

SCF.THN.18771.02.LIST = PERCENT=(25,50)SCF.THN.18771.02.LIST = DURATION=10 SCF.THN.18771.02.LIST = ACTION=(SAVEDEV1)SCF.THN.18771.02.LIST = FREQUENCY=REPEAT



SCF.THN.<cntrl#>.poolname.xx.LIST


DefaultNone

Example

SCF.THN.18771.SAVEPOOL.03.LIST = PERCENT=(50,75)SCF.THN.18771.SAVEPOOL.03.LIST = DURATION=5SCF.THN.18771.SAVEPOOL.03.LIST = ACTION=MES(FIFTY)SCF.THN.18771.SAVEPOOL.03.LIST = FREQUENCY=REPEAT

SCF.TRACE.COMPRESS

DescriptionSCF.TRACE.COMPRESS specifies whether or not the trace file is to be compressed.


DefaultNO

Example

SCF.TRACE.COMPRESS=YES

SCF.TRACE.CYLINDER

Description This parameter overrides the SCF.TRACE.TRACKS.PRI and the SCF.TRACE.TRACKS.SEC parameters to allocate in cylinders instead of tracks.

Possible Values Yes/No

DefaultNo

ExampleSCF.TRACE.CYLINDER=Y



SCF.TRACE.DATACLAS

DescriptionSCF.TRACE.DATACLAS specifies the SMS data class name to be used when allocating the SCF TRACE file.


DefaultNone

Example

SCF.TRACE.DATACLAS=SCFTRACE

SCF.TRACE.FLUSH.AT

DescriptionSCF.TRACE.FLUSH.AT specifies the point at which the trace writer will be posted to flush the trace buffer to the SCF TRACE file. The default point is 75% full.

Possible values30 to 90 percent

Default75

Example

SCF.TRACE.FLUSH.AT=50

SCF.TRACE.MEGS (default)

DescriptionSCF.TRACE.MEGS specifies the amount of space (in megabytes) used to create the SCF TRACE file. This will be used for the primary and secondary amounts. MEGS is then converted to TRACKS for allocations.

Note: MEGS is the total allocation including 16 extents. If MEGS and TRACKS are both present in SCFINI file, MEGS overrides TRACKS.


Default1



Example

SCF.TRACE.MEGS=2

SCF.TRACE.MGMTCLAS

DescriptionSCF.TRACE.MGMTCLAS specifies the SMS management class name to be used when allocating the SCF TRACE file.


DefaultNone

Example

SCF.TRACE.MGMTCLAS=MGMTRACE

SCF.TRACE.RETAIN.COUNT

DescriptionSCF.TRACE.RETAIN.COUNT specifies the number of SCF TRACE files to retain.


Default10

Example

SCF.TRACE.RETAINCOUNT=12

SCF.TRACE.RETAIN.DAYS

DescriptionSCF.TRACE.RETAIN.DAYS specifies the number of days to retain a SCF TRACE file.


Default10

Example

SCF.TRACE.RETAIN.DAYS=30



SCF.TRACE.STORCLAS

DescriptionSCF.TRACE.STORCLAS specifies the SMS storage class name to be used when allocating the SCF TRACE file.


DefaultNone

Example

SCF.TRACE.STORCLAS=FOOBAR

SCF.TRACE.TRACKS.PRI

Description SCF.TRACE.TRACKS.PRI specifies the primary allocation (in tracks) used to create the SCF TRACE file.

Possible values 1 to 9999

DefaultNone.

Example SCF.TRACE.TRACKS.PRI=12

SCF.TRACE.TRACKS.SEC

Description SCF.TRACE.TRACKS.SEC specifies the secondary allocation (in tracks) used to create the SCF Trace file.


Default None.

Example SCF.TRACE.TRACKS.SEC=45



SCF.TRU.DEBUG

Description SCF.TRU.DEBUG turns on debugging messages.

Possible values YES|NO

Default NO

Example

SCF.TRU.DEBUG=YES

SCF.TRU.DEV.EXCLUDE.LIST

Description SCF.TRU.DEV.EXCLUDE.LIST excludes certain devices from the SCF TRU Monitor task.

Possible values Possible values are device CCUUs that are defined to SCF. Multiple devices and multiple device ranges may be specified. Multiples statement may be specified and they will be concatenated together.

Default None.

Example

SCF.TRU.DEV.EXCLUDE.LIST=0000-A000,B000-C000SCF.TRU.DEV.EXCLUDE.LIST=1234,2345-3456,4567

SCF.TRU.DEV.INCLUDE.LIST

Description SCF.TRU.DEV.INCLUDE.LIST includes certain devices to be monitored by the SCF TRU Monitor task.

Possible values Possible values are device CCUUs that are defined to SCF. Multiple devices and multiple device ranges may be specified. Multiples statement may be specified and they will be concatenated together.

Default None.



Example

SCF.TRU.DEV.INCLUDE.LIST=0000-A000,B000-C000SCF.TRU.DEV.INCLUDE.LIST=1234,2345-3456,4567

SCF.TRU.ENABLE

Description SCF.TRU.ENABLE allows you to enable or disable TRU and the SCF TRU monitor task.

Possible values YES|NO

Default YES

Example

SCF.TRU.ENABLE=NO

SCF.TRU.RECLAIM.DSFACTOR

Description SCF.TRU.RECLAIM.DSFACTOR provides a size factor when allocating the temporary dataset for reclaim processing. For space that is track managed, this is the maximum number of cylinders that are allocated to a temporary dataset. For space that is cylinder managed, this is the number of CMS allocation units (21 cylinders each) that are allocated to a temporary dataset.

Possible values 1 to 999,999

Default: 1000

Example

SCF.TRU.RECLAIM.DSFACTOR=500

SCF.TRU.RECLAIM.DSPREFIX

Description SCF.TRU.RECLAIM.DSPREFIX identifies the dataset prefix that is used when a temporary dataset is allocated on a volume for reclaim purposes.



Possible values Possible values are limited to a 26-character name. The name should observe standard z/OS dataset naming conventions and be appended with a sequence number. The name should be allowed in the customer environment RACF rules. The dataset is not opened or closed, but allocated to the task and freed.

Default EMC.RECLAIM

Example

SCF.TRU.RECLAIM.DSPREFIX=EMC.RECLAIM

Note: If the prefix is EMC.RECLAIM, the generated name format is EMC.RECLAIM.RCvolser.#0000001

SCF.TRU.RECLAIM.METHOD

Description SCF.TRU.RECLAM.METHOD specifies the order of reclaiming tracks. Three options are available:

1. From the beginning of a volume to the end of a volume.

2. From the end of a volume to the beginning of a volume.

3. From the largest segment to the smallest segment.

Possible values 1, 2, or 3

Default 1

Example

SCF.TRU.RECLAIM.METHOD=1

SCF.TRU.RECLAIM.PGMNAME

Description SCF.TRU.RECLAIM.PGMNAME provides an alternative program name to be attached in SCF to perform RECLAIM processing for a device.

Possible values Possible values include any 8-character program name.

Default ESFTRURC



Example

SCF.TRU.RECLAIM.PGMNAME=ESFTRURC

SCF.TRU.RECLAIM.POST.TYPE SCF.TRU.SCRATCH.POST.TYPE

SCF.TRU.RECLAIM.POST.PCT SCF.TRU.SCRATCH.POST.PCT

SCF.TRU.RECLAIM.POST.MIN SCF.TRU.SCRATCH.POST.MIN

SCF.TRU.RECLAIM.POST.MAX SCF.TRU.SCRATCH.POST.MAX

DescriptionThese four pairs of parameters are interrelated. One set of four for RECLAIM and the other for SCRATCH. They are used for notification of the SCF monitor task and to determine what and how the post value is determined.

For scratch and reclaim activity, a key point is when to schedule the reclaim job. The trigger point is based on either the total size of the device (DEVICESIZE) or the amount of freespace initially available on the device (FREESPACE). The device size is a static value, determined when the thin device begins monitored by the TRU monitor. The freespace is also determine when the thin device begins monitored (it must be online), and also each time the RECLAIM utility is run. The actual value is based on a percentage of either the device size or the freespace. There is also a mininum number and maximum number of tracks that is allowed when the percentage is calculated.

Possible values and defaultsSCF.TRU.RECLAIM.POST.TYPE=FREESPACE | DEVICESIZE , default is FREESPACESCF.TRU.SCRATCH.POST.TYPE=FREESPACE | DEVICESIZE , default is FREESPACE

SCF.TRU.RECLAIM.POST.PCT=0 to 100, default is 50SCF.TRU.SCRATCH.POST.PCT=0 to 100, default is 50

SCF.TRU.RECLAIM.POST.MIN=0 to 9,999,999, default is 100SCF.TRU.SCRATCH.POST.MIN=0 to 9,999,999, default is 100

SCF.TRU.RECLAIM.POST.MAX=0 to 9,999,999, default is 9,999,999SCF.TRU.SCRATCH.POST.MAX=0 to 9,999,999, default is 9,999,999

Examples

SCF.TRU.RECLAIM.POST.TYPE=DEVICESIZE SCF.TRU.SCRATCH.POST.TYPE=DEVICESIZE

SCF.TRU.RECLAIM.POST.PCT=65SCF.TRU.SCRATCH.POST.PCT=65



SCF.TRU.RECLAIM.POST.MIN=500SCF.TRU.SCRATCH.POST.MIN=500

SCF.TRU.RECLAIM.POST.MAX=750000SCF.TRU.SCRATCH.POST.MAX=750000

SCF.TRU.RECLAIM.SCRATCH.WAIT

Description SCF.TRU.RECLAIM.SCRATCH.WAIT identifies the amount of time after a dataset scratch has occurred before RECLAIM processing is to start.

Possible values Possible values are specified in units of 1/100 seconds. The minimum value is 0 and the maximum value is one hour (360,000).

Default 0

Example

SCF.TRU.RECLAIM.SCRATCH.WAIT=100

This causes a minimum one second wait before starting RECLAIM processing.

SCF.TRU.RECLAIM.SCRATCH.WAIT=6000

This causes a minimum one minute wait before starting RECLAIM processing.

SCF.TRU.RECLAIM.STCNAME

Description SCF.TRU.RECLAIM.STCNAME identifies an STCNAME that is used for executing the RECLAIM program. When an STCNAME is present, all RECLAIM processing occurs as separate started tasks, and not by attaching the task locally in SCF.

Note: To use STCNAME, add the corresponding procedure to your PROCLIB. “Running TRU as a started task” on page 439 provides additional information.

Possible values Possible values include any 8-character procedure name. If no name is specified, RECLAIM processing occurs by attaching the process within the SCF address space.

Default None.

Example

SCF.TRU.RECLAIM.STCNAME=BAPTRCLM



SCF.TRU.RECLAIM.STRESS.MONITOR

Description If set to yes, all reclaim erases accept a code from the Symmetrix indicating whether the erases are causing stress in the box. If stress is encountered, the erase I/O activity is paced. A delay is introduced between the issuance of each erase I/O. The maximum time between I/O's is controlled by the parameter SCF.TRU.RECLAIM.STRESS.WAIT.


DefaultYES

Example

SCF.TRU.RECLAIM.STRESS.MONITOR=NO

SCF.TRU.RECLAIM.STRESS.WAIT

DescriptionThis is the maximum amount of wait time (in minutes) between RECLAIM erase I/O operations. Initially, there is no delay between I/O operations. But if stress monitoring is enabled, and the Symmetrix is in a stress condition, reclaim erase I/O operations introduce a delay between each I/O, and the delay grows the longer that the box is in stress.

Possible values0 to 60 (minutes)

Default5 (minutes)

Example

SCF.TRU.RECLAIM.STRESS.WAIT=15

SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT

Description SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT identifies the maximum amount of time that the RECLAIM task is to hold the SYSVTOC RESERVE during processing.

Possible values Possible values are specified in units of 1/100 seconds. The minimum value is zero (ignore) and the maximum value is 3 minutes (18000).



Default 30 seconds (3000).

Example

SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT=6000

This limits the hold time to 1 minute.

SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT

Description SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT identifies the maximum segment size (contiguous freespace) that is considered to be processed while holding the SYSVTOC RESERVE. If a segment is found smaller than this value, it is processed while holding the SYSVTOC RESERVE (which causes the RESERVE to be held longer than otherwise). If a segment is found that is larger than this value, it is processed using the temporary dataset method.

Possible values 0 to 999,999

Default 150

Example

SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT=30

This limits the segment size to 2 cylinders.

SCF.TRU.RECLAIM.SYSVTOC.WAIT

Description SCF.TRU.RECLAIM.SYSVTOC.WAIT identifies the amount of time to elapse after releasing the SYSVTOC RESERVE, before attempting to acquire the SYSVTOC RESERVE again.

Possible values Possible values are specified in units of 1/100 seconds. The minimum value is zero and the maximum value is 5 minutes (30000).

Default 30 seconds (3000)

Example

SCF.TRU.RECLAIM.SYSVTOC.WAIT=6000

This sets a wait time of 1 minute.



SCF.TRU.RECLAIM.TIMELIMIT.LIST

Description SCF.TRU.RECLAIM.TIMELIMIT.LIST identifies time restrictions for running the RECLAIM process. If specified, RECLAIM processing only occurs during the time limits specified. Multiple ranges may be specified.

Possible values Values are specified as a series of 4-digit values: 2-digit for hours and 2-digit for minutes.

Default None.

Example

SCF.TRU.RECLAIM.TIMELIMIT.LIST= 0200-0400,0800-1200,1300-1500,1800-1900,2200-2300

SCF.TRU.RECLAIM.TASK.LIMIT

Description SCF.TRU.RECLAIM.TASK.LIMIT specifies a maximum number of RECLAIM tasks that are run simultaneously.


Default 10

Example

SCF.TRU.RECLAIM.TASK.LIMIT=15

SCF.TRU.SCAN.PGMNAME

Description SCF.TRU.SCAN.PGMNAME provides an alternative program name to be attached in SCF to perform SCAN processing for a device.

Possible values Possible values include any 8-character program name.

Default None.

Example

SCF.TRU.SCAN.PGMNAME=ESFTRURC



SCF.TRU.SCAN.STCNAME

Description SCF.TRU.SCAN.STCNAME identifies a STCNAME that is to be used for executing the SCAN program. When an STCNAME is present, all SCAN processing occur s as separate started tasks, and not by attaching the task locally in SCF.

Note: To use STCNAME, add the corresponding procedure to your PROCLIB. “Running TRU as a started task” on page 439 provides additional information.

Possible values Possible values include any 8-character procedure name. If no name is specified, SCAN processing occurs by attaching the process within the SCF address space.

Default None.

Example SCF.TRU.SCAN.STCNAME=BAPTSCAN

SCF.TRU.SCAN.TASK.LIMIT

Description SCF.TRU.SCAN.TASK.LIMIT specifies a maximum number of SCAN tasks that run simultaneously.


Default 10

Example SCF.TRU.SCAN.TASK.LIMIT=15

SCF.TRU.SCRATCH.RECLAIM

Description SCF.TRU.SCRATCH.RECLAIM specifies the maximum size of an extent that can be automatically reclaimed during execution of the scratch exit.

Possible values 0 to 999,999 Tracks

Default 20 Tracks

Example SCF.TRU.SCRATCH.RECLAIM=15



SCF.TRU.THICKR1

DescriptionEnables support for thick R1 scanning of devices.

This parameter provides the following:

◆ Support for thin reclaim processing on thick to thin SRDF.

◆ Monitors a thick R1 device only if a related thin R2 device is NOT bound with the PERSIST option.

◆ Supports reclaim processing in SRDF/S and SRDF/A modes in all SRDF topologies:

• Concurrent

• Cascaded

• Four site

◆ Enables reclaim processing on thin devices in Thick to Thin RDF relationship

Possible values YES or NO.

Default YES

ExampleSCF.TRU.THICKR1=YES

SCF.WORK.HLQ

DescriptionSCF.WORK.HLQ specifies the high level qualifier to be used when creating the SCF LOG and SCF TRACE files. The format of the dataset names is as follows:

hlq.type.id.Ddate.Ttime

Where:

hlq = SCF.WORK.HLQ

type = LOG or TRACE

id = 8 character SMF ID padded with ‘$’

Ddate = yyyyddd – allocation Julian date

Ttime = hhmmss – allocation time


DefaultSCFSERVE



ExampleSCF.WORK.HLQ=SCFSERVE

SCF.WORK.UNIT

DescriptionSCF.WORK.UNIT specifies the unit name to be used when allocating the SCF LOG and SCF TRACE files.


DefaultSYSDA

Example

SCF.WORK.UNIT=SYSDA

SCF.WORK.VOLSER

DescriptionSCF.WORK.VOLSER specifies the VOLSER to be used when allocating the SCF LOG and SCF TRACE files.


DefaultNone

Example

SCF.WORK.VOLSER=DISK01

SCF.WPA.EXCLUDE.CNTRL

DescriptionAllows the SRDF/A Write Pacing monitor to be EXCLUDED for individual controllers and groups. Exclude parameters are processed after includes, and therefore exclude parameters are always honored.

Syntax for single exclude statements:

SCF.WPA.EXCLUDE.CNTRL=nnnnnnnnnnnn(gg,gg,…)

Syntax for multiple exclude statements :

SCF.WPA.EXCLUDE.CNTRL.LIST=



Possible valuesSRDF group numbers separated by commas

or

ALL, which specifies all the SRDF groups on the controller.

DefaultNone

Example

SCF.WPA.EXCLUDE.CNTRL=000190300344(05,08,1E,F0)

Examples for multiple statements

SCF.WPA.EXCLUDE.CNTRL.LIST=000192603872(05,08,1E,F0) SCF.WPA.EXCLUDE.CNTRL.LIST=000194901031(ALL)

SCF.WPA.INCLUDE.CNTRL

DescriptionAllows the SRDF/A Write Pacing monitor to be activated by individual controllers. Once one of these statements is discovered, then only controllers explicitly included are monitored. Include parameters are processed before excludes, so excludes parameters override includes parameters.

Syntax:

SCF.WPA.INCLUDE.CNTRL = nnnnnnnnnnnn(gg,gg,…)

If you want to enter multiple include statements add .LIST to the end of the .CNTRL. For example:

SCF.WPA.INCLUDE.CNTRL.LIST=

Possible valuesSRDF group numbers separated by commas

or

ALL, which specifies all the SRDF groups on the controller.

DefaultAll groups on all controllers are included.

Example

SCF.WPA.INCLUDE.CNTRL=000190300344(05,08,1E,F0)

Examples for multiple statements

SCF.WPA.INCLUDE.CNTRL.LIST=000192603872(05,08,1E,F0) SCF.WPA.INCLUDE.CNTRL.LIST=000194901031(ALL)



SCF.WPA.MONITOR

DescriptionIf enabled, SCF.WPA.MONITOR causes the SRDF/A Write Pacing monitor to actively monitor any SRDF/A sessions with pacing activated. If this parameter is disabled, the SRDF/A Write Pacing monitor will not start. To start the monitor, you need to add this parameter to the SCF initialization file and restart SCF.


DefaultDISable

Example

SCF.WPA.MONITOR=ENA

SCF.WPA.MSGLEVEL

DescriptionControls what type of messages are written to the console by the WTO interface. The types of messages are specified as a comma-separated list.

Possible valuesALERTS — High priority pacing related messages.

BASIC — Initialization and basic processing (cannot be turned off).

INCEXC — Messages indicating current excludes/includes in effect.

STATE — Pacing state change messages. Group going from paced to not paced, and so forth.

STATUS — WPA monitor status messages.

DefaultBASIC

Example

SCF.WPA.MSGLEVEL=ALERTS,INCEXC

SCF.WPA.POLL.INTERVAL

DescriptionSCF.WPA.POLL.INTERVAL specifies the interval setting for individual controllers for the Write Pacing monitor.

Possible values.1 to 60 minutes (Values available in tenths of a minute to a maximum of 60 minutes.)



Default5 minutes

Example

SCF.WPA.POLL.INTERVAL=.1

SCF.WPA.SMF

Explanation SCF.WPA.SMF indicates whether or not to write SMF records.

Possible values ENABLE | DISABLE

DefaultDISABLE

Example

SCF.WPA.SMF=ENABLE

SCF.WPA.SMF.FILTER

Description SCF.WPA.SMF.FILTER filters out data records from being recorded to SMF.

Possible values NOZERO — Data records with all zero statistics are not recorded to SMF or displayed in the informational statistics messages.

NOINACTIVE — Data records whose pacing state flags are all off are not recorded to SMF or displayed in the informational statistics messages. It should be noted that even when no data records remain after NOINACTIVE processing is performed, that the header record for the Symmetrix being monitored will still be written to SMF.

Note: Even when no data records remain after NOZERO or NOINACTIVE processing is performed, the header record for the monitored Symmetrix system is still written to SMF.

NOUNCHANGED —Data records whose pacing state flags and statistics numbers that haven't changed since the last polling interval are not recorded to SMF or displayed in the informational statistics messages.

Note: Unlike the NOZERO and NOINACTIVE processing, when no data records remain after NOUNCHANGED processing is performed, no header record for the Symmetrix system is written to SMF.



Default No filtering is performed. All data records are written to SMF and displayed in the informational statistics messages.

Example

SCF.WPA.SMF.FILTER=NOZERO,NOUNCHANGED

SCF.WPA.SMF.RECORD

Explanation SCF.WPA.SMF.RECORD specifies the number of an SMF record to use when writing statistics about controllers that are being monitored. If you do not specify SCF.WPA.SMF.RECORD, the monitor will use the SCF.ASY.SMF.RECORD value if one was specified. If an SMF record type cannot be determined, the Write Pacing monitor does not write any SMF records.


DefaultNone

Example

SCF.WPA.SMF.RECORD=150

SCF.WPA.STYPES

Explanation Specifies the types of statistics records to record — group statistics, device statistics, or all statistics.

Possible values GROUP

Record group statistics.

DEVICE

Record device statistics.

ALL

Record group and device statistics.

Default ALL

Example

SCF.WPA.STYPES=GROUP


CHAPTER 4Command Reference

This chapter describes the commands used by the ResourcePak Base functions documented in subsequent chapters.

◆ Command syntax and conventions........................................................................ 144◆ Customer tasks and command types..................................................................... 145◆ Initialization commands........................................................................................ 147◆ eLicensing management commands...................................................................... 149◆ Cross-system communication commands.............................................................. 154◆ Device commands................................................................................................. 161◆ zBoost PAV Optimizer commands.......................................................................... 175◆ Group Name Services commands.......................................................................... 182◆ General Pool Management commands .................................................................. 185◆ Recovery services commands................................................................................ 309◆ SRDF/AR: Symmetrix Automated Replication commands ....................................... 311◆ SRDF/A Multi-Session Consistency commands ...................................................... 316◆ SRDF/A Monitor operator commands .................................................................... 336◆ DSE Monitor operator commands .......................................................................... 339◆ SDV Monitor operator commands.......................................................................... 342◆ THN Monitor operator commands.......................................................................... 345◆ TRU monitor operator commands .......................................................................... 348

Command Reference 143

Command Reference

Command syntax and conventionsThis chapter describes the commands supported by ResourcePak Base. Commands are issued in the following format:

F EMCSCF,command type,command

Where:

EMCSCF

Specifies the jobname.

command type

Specifies the type of command, or environment, as shown in Table 4 on page 145.

Note: The value specified in the SCF.INI.CPFX initialization parameter can also be used to issue these commands. “SCF.INI.CPFX” on page 98 provides details on use of this parameter.

command

Specifies a ResourcePak Base command.

Syntax conventions

The commands in this chapter follow these syntax conventions:

◆ Keywords appear in uppercase (for example, ALL). They must be spelled exactly as shown.

◆ Variables appear in lowercase and italics (for example, emcscf) . They represent user-supplied names or values in the syntax.

Note: emcscf is used as the name of EMCSCF started task throughout this manual.

◆ Square brackets [ ] indicate an optional entry (for example, ,DEV,REFRESH[,GATEKeepers])

◆ The vertical bar| indicates alternative argument values (for example, count|ALL).

◆ Curly brackets {} are used to group a series of alternative values that can be used with a single keyword, for example: GNS,LIST{[,SER#,nnnnnnnnnnnn]|[,GROUP,gggggggggg]}

◆ Aside from the square and curly brackets and the vertical bar characters, you must type all other characters that are shown in the syntax statements.

◆ Default values are indicated by an underline. For example, if the parameter has the following option, (YES|NO), the underlined NO indicates the default value.


Command Reference

Customer tasks and command typesThe following is a table that provides a brief description of customer tasks and the command type that address these tasks.

Table 4 Customer tasks and command types

Command Type Description Refer to...

INI The initialization commands allow you to perform the following tasks:• Reread the initialization file.• Refresh the SymmAPI-MF when while SCF is up and running.• Reverse SymmAPI-MF termination.

page 147

ELM The Electronic Licensing (eLicensing) commands support the EMC electronic licensing feature. These commands are valid for Symmetrix systems running Enginuity 5875 or higher.

page 149

CSC The cross-system communication (CSC) commands display information about each registered host or each registered listener, and also allow you to update gatekeeper information.

page 154

DEV The device commands allow you to obtain device information. page 161

DEV,OPTIMIZE zBoostTM PAV Optimizer commands. page 175

GNS The GNS commands allow you to perform the following tasks:• Display the contents of the scratch area.• Force a communications scratch area to be GNS-compatible.• Display the names of all groups defined on all the Symmetrix systems

known to this SCF.• Refresh the contents of the internal in-memory GNS tables.• Revert the specified communications scratch area from a GNS-compatible

state to an earlier, non GNS-compatible state.

page 182

GPM GPM commands allow you to manage virtual (VP) pools and pool devices from either batch or online modes.

page 185

REC The recovery services commands allow you to perform a recovery on local or remote devices.

page 309

SAR The Symmetrix Automated Replication (SRDF/AR) commands allow you to control the SRDF/AR process, to ensure data consistency across geographic distances.

page 311

SRV Commands for controlling the SYSBUSY condition within the SRV environment for EMCSCF.

page 314

MSC The SRDF/A Multi-Session Consistency (MSC) commands allow you to query and control the MSC process, to ensure remote R2 consistency across multiple Symmetrix systems running SRDF/A.

page 316

ASY The SRDF/A Monitor commands are designed to control the SRDF/A Monitor. page 336

DSE The DSE monitor commands are designed to control the DSE monitor. page 339

Customer tasks and command types 145

Command Reference

SDV The SDV Monitor commands are designed to control the SDV Monitor. page 342

THN The Thin Pool (THN) Monitor commands are designed to control the THN Monitor.

page 345

TRU The Thin space reclamation (TRU) commands provide an environment that records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the Symmetrix free track pool.

page 348

Table 4 Customer tasks and command types

Command Type Description Refer to...


Command Reference

Initialization commandsThe initialization commands allow you to perform the following tasks:

◆ Reread the initialization file

◆ Refresh the SymmAPI-MF when while SCF is up and running

◆ Reverse SymmAPI-MF termination

INI,REFRESH

Specifies that the initialization file is to be reread and the variable values stored. No additional initialization processing is performed.

Syntax

F emcscf,INI,REFRESH

ParametersNone.

ExampleF EMCSCF,INI,REFRESH SCF0321I INI,REFRESH SCF.GATEKEEPER.LIST=426E-426F SCF.GATEKEEPER.LIST=C100 .. (Lists complete SCFINIxx member) .SCF0301I SCF.CSC.GATEKEEPER.03115.LIST=00B0 SCF0301I SCF.CSC.GATEKEEPER.03011.LIST=00AF SCF0301I SCF.CSC.ACTIVEPOLL=5 SCF0301I SCF.CSC.IDLEPOLL=5 SCF0322I INI REFRESH COMMAND COMPLETED.

INI,RELOAD

Allows a refresh of the SymmAPI-MF environment while SCF is up and running. It can be issued any time independent of the applications using SymmAPI-MF routines. As a result, new code will be loaded and all subsequent calls to the SymmAPI-MF routines will use the new code.

Syntax

F emcscf,INI,RELOAD

ParametersNone.

ExampleF EMCSCF,INI,RELOAD SCF0321I INI,RELOAD SCF2023I SCFGBLSN MODULE FOUND, LFC WAS SPECIFIED, SNAP V5.7 ACTIVE SCF2004I SCFGBLCD AT 970E6000 IS TO BE REPLACED SCF2005I CURRENT LOCK IS 8000000040000000 SCF2004I SCFGBLSN AT 16634000 IS TO BE REPLACED

Initialization commands 147

Command Reference

SCF2006I SCFGBLCD REPLACED. NEW ADDRESS 97433000 SCF2005I CURRENT LOCK IS 4000000080000000 SCF2006I SCFGBLSN REPLACED. NEW ADDRESS 15FCE000 SCF2011I MODULE SCFGBLCD RELOADED SCF2011I MODULE SCFGBLSN RELOADED SCF0322I INI RELOAD COMMAND COMPLETED.

INI,SHUTDOWN

Results in the complete termination of SymmAPI-MF after you issue a subsequent command P emcscf to stop EMCSCF.

Note: IBM routines store extent information about load libraries when they are opened. This information is retained for the duration of use of the libraries. Multiple cycles of updating the load library containing SymmAPI-MF and using the RELOAD EMCSCF command cause LOAD failures if the load library has expanded. The expanded SymmAPI-MF library now has new extents not recorded by the IBM routines at open time. If library expansion occurs, issue a F emcscf,INI,SHUTDOWN command (so that EMCSCF terminates the persistent SymmAPI-MF at shutdown). Restarting EMCSCF automatically reloads SymmAPI-MF.

If you need to terminate SymmAPI-MF when EMCSCF is NOT running, such as when you are installing a new version of ResourcePak Base, you can find a batch utility to terminate SymmAPI-MF in SCF.SAMPLIB as member SCFUTL01. “EMCSCF termination utility” on page 55 provides details.

Syntax

F emcscf,INI,SHUTDOWN

ParametersNone.

ExampleF EMCSCF,INI,SHUTDOWNSCF0321I INI,SHUTDOWN SCF0322I INI SHUTDOWN COMMAND COMPLETED. SCFS237I AutoSwap has shutdown, RC=00000000. SCFS126I Shutdown NORMAL accepted from CN(unknown). SCF4018I FLS - Flash still has 0 active requests. Waiting for active

requests to complete.SCF2501I PDVHC - Pooled Devices maintenance task ending SCF0890I SCFGNST - GNS task is terminating. SCF1212I ASY - ESFASY ENDED SCF1102I DSE MONITOR DSEPOOL TASK ENDED ESFMNDSE 10/05/07 07.49 ENDED SCF1202I ASY MONITOR TASK ENDED SCF1102I SDV MONITOR SNAPPOOL TASK ENDED SCF1302I MSC - TASK ENDED SCF1312I MSC - SCFMSC ENDED SCF4002I EMC Flash Feature has been disabled. SCF0012I SUBSYSTEM INTERFACE DEACTIVATED SCF2002I TERMINATING GLOBAL SCF ENVIRONMENT SCF2012I WAITING FOR SRB TO COMPLETE CLEANUP SCF2003I GLOBAL SCF ENVIRONMENT TERMINATED EMCSCF LR#SCF SCFMAIN 0000 025683 0 0 IEF404I EMCSCF - ENDED - TIME=11.12.40


Command Reference

eLicensing management commandsFor Symmetrix systems running Enginuity 5875 or higher, ResourcePak Base provides support for Electronic Licensing (eLicensing).

With the release of Enginuity level 5876, Mainframe Enablers is introducing support for Symmetrix-based license bundles. A license bundle is a single license that enables multiple features. For Symmetrix systems running versions of Enginuity level 5875, Mainframe Enablers continues to support individual Symmetrix-based licenses.

Note: The Mainframe Enablers Installation and Customization Guide provides details about eLicensing.

ELM,LIST,CONTROLLER

Lists all the eLicensing features or bundles included in the Symmetrix system identified in the CONTROLLER field. When you list from a system with Enginuity level 5875 or lower, a report displays individual feature licenses. For systems with Enginuity level 5876 or higher, a report displays licensed bundles.

Syntax

F emcscf,ELM,List,CONTROLLER|CNTRL(id)

Parameters

CONTROLLER|CNTRL(id)

id specifies a DASD controller. The value can be any of the following:

• Either the full 12-digit Symmetrix serial number or just the last 5 digits of the number. (Use the 12-digit ID when multiple controllers use the same last 5 digits.)

• A wildcard character. You can use the following characters:

* To match one or more characters

? or % To match exactly one character in this position.

The following table shows wildcard examples for CONTROLLER.

Specified value Symmetrix serial number Match?

*00193 000192600193 Y

*1926* 000192600193 Y

00192*193 000192600193 N

000192%%???? 000192600193 Y

*192%%0???? 000192600193 N

0001926002?? 000192600193 Y

000192%%0???? 000192600193 Y

00*192* 000192600193 Y

eLicensing management commands 149

Command Reference

Examples

Note: The Mainframe Enablers Installation and Customization Guide describes the fields in these command displays.

Example 1 When you issue ELM,LIST,CONTROLLER from a Symmetrix system running Enginuity level 5875 or lower, a report similar to the following displays the individual feature licenses:

SCF0341I ELM,LIST,CNTRL(00215) SCF5005I Report for (Local) Controller follows Symmetrix ID : 000192600215 Activation ID: 1234567 Issue Date : 02/16/2011 Capacity Expiration Install Feature Name Act Type Licensed Date Date -------------------- ----- ------------- -------- ---------- ----------SYMM_VMAX_ARRAY P-IND R-TB-Non-Sata 20 - 02/16/2011 R-TB-Sata 10 SYMM_VMAX_TF_CLONE P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_TF_SNAP P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF_S P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF_A P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF_STAR P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_DCP P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SPC P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_OPTIMIZER P-IND R-TB-Non-Sata 3 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_FAST P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_FAST_VP P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_ORS_DM P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SMC P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 Legend: Act(ivation Type): E-IND = Evaluation Individual P-IND = Permanent Individual P-ENT = Permanent Enterprise Agreement


Command Reference

Example 2 When you issue ELM,LIST,CONTROLLER from a Symmetrix system running Enginuity level 5876 or higher, a report similar to the following displays the licensed bundles:

SCF5005I Report for (Remote) Controller follows 473 Symmetrix ID : 000195600140 Issue Date : 04/04/2012 Activation Capacity Install Feature Name Type ID Type Licensed Date -------------------- ----- ---------- ------------- -------- ----------SYMM_VMAX_ENGINUITY P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 SYMM_VMAX_FAST_TIERI P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 SYMM_VMAX_SRDF_REPLI P-IND UNKNOWN 0 00/00/0000SYMM_VMAX_TIMEFINDER P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 SYMM_VMAX_SRDF_STAR P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 Legend: Act(ivation Type): E-IND = Evaluation Individual P-IND = Permanent Individual P-ENT = Permanent Enterprise Agreement P-LTD = Permanent Limited

Output field descriptionsThe following explains the output for the ELM,LIST,CONTROLLER command:

◆ Act(ivation): Whether the feature's license is P(ermanent) or an E(valuation) copy. Evaluation licenses include an Expiration Date for reporting purposes only; the product title can still be used. Permanent licenses can be assigned to Ind(ividual) Symmetrix systems or to all the Symmetrix systems in the Ent(erprise).

◆ Capacity Licensed: The maximum quantity of data for which the functionality of the software is licensed to use, in Terabytes.

◆ Capacity Type: Qualifies the capacity licensed. Possible values are:

• R-TB-Non-SATA: Indicates that the capacity licensed applies to the raw capacity of all devices on the system, excluding SATA.

• R-TB-SATA: Indicates that the capacity licensed applies to the raw capacity of all SATA devices on the system.

• REG-TB: Indicates that the capacity licensed applies to the registered capacity of the Symmetrix system.

◆ Capacity Units: The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

◆ Days Until Expr: For an Evaluation license, this field displays the number of days until expiration. For a Permanent license, this field displays a hyphen (-). This field only applies to SPA.

◆ Expiration Date: For an Evaluation license, this field displays the expiration date. For a Permanent license, this field displays a hyphen (-).

◆ Feature Name: The name of the licensed feature.

◆ Install Date: The date the license was installed.

◆ Lic(ense) Type: The type of license.

◆ SymmID: The Symmetrix system to which the license is applied.


Command Reference

ELM,QUERY,CONTROLLER

Displays the current eLicensing usage report as stored on the Symmetrix system defined by the CONTROLLER field. This usage report is updated only once a day. Any licensing changes since the previous generation of the report will not be included in the ELM,QUERY command output.

Note: This command is available with z/OS V1R8 and higher. If you are running z/OS V1R7 and lower, you will receive an ELM LIST CONTROLLER report in place of the ELM QUERY CONTROLLER command.

Syntax

F emcscf,ELM,Query,CONTROLLER|CNTRL(id)

Parameters


id specifies a DASD controller. The value can be any of the following:

• Either the full 12-digit Symmetrix serial number or just the last 5 digits of the number. (Use the 12-digit ID when multiple controllers use the same last 5 digits.)

• A wildcard character. You can use the following characters:

* To match one or more characters

? or % To match exactly one character in this position.

The following table shows wildcard examples for CONTROLLER.

Examples

Note: The Mainframe Enablers Installation and Customization Guide describes the fields in this command display.

Specified value Symmetrix serial number Match?

*00193 000192600193 Y

*1926* 000192600193 Y

00192*193 000192600193 N

000192%%???? 000192600193 Y

*192%%0???? 000192600193 N

0001926002?? 000192600193 Y

000192%%0???? 000192600193 Y

00*192* 000192600193 Y


Command Reference

Example 1 When you issue ELM,QUERY,CONTROLLER from a Symmetrix VMAX 10K system, a report similar to the following displays the individual feature licenses:

SCF0341I ELM,QUERY,CNTRL(00215) SCF5005I Report for (Local) Controller follows Symmetrix ID : 000192600215 Activation ID: 1234567 Issue Date : 9/4/2010 Capacity ------------------------------- Feature Name Act Type Licensed Usage -------------------- ----- ------------- -------- -------- SYMM_ARRAY ENT R-TB-non-SATA 60 50.4 R-TB-SATA 40 0.0 SYMM_TF_CLONE ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_TF_SNAP ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_SRDF_S ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_SRDF_A ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_SRDF_STAR ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_DCP R-TB-non-SATA 5 50.4 R-TB-SATA 5 0.0 SYMM_SPC ENT R-TB-non-SATA 5 50.4 R-TB-SATA 4 0.0 SYMM_OPTIMIZER ENT R-TB-non-SATA 5 50.4 R-TB-SATA 0 0.0 SYMM_FAST ENT REG-TB 50 0.0 SYMM_FAST_VP ENT REG-TB 5 0.0 SYMM_SRDF ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_RP MAN REG-TB 0 0.0 Legend: Act(ivation Type): ENT = Entitlement MAN = Manual Override USE = In Use

Example 2 When you issue ELM,QUERY,CONTROLLER from a Symmetrix VMAX 40K system, a report similar to the following displays the licensed bundles:

SCF0341I ELM,QUERY,CNTRL(00397) SCF5005I Report for (Local) Controller follows Symmetrix ID : 000195700397Issue Date : 12/18/2011 Capacity -------------------------------Feature Name Act Type Licensed Usage --------------------------- ---- ------------- -------- --------SYMM_VMAX_ENGINUITY ENT R-TB-Non-SATA 100 100.0 R-TB-SATA 500 500.0SYMM_VMAX_FAST_TIERING ENT REG-TB 100 16.1. . .SYMM_VMAX_SRDF_REPLICATION ENT REG-TB 100 25.1SYMM_VMAX_TIMEFINDER ENT R-TB-Non-SATA 100 100.0 R-TB-SATA 500 500.0

Legend: Act(ivation Type): ENT = Entitlement MAN = Manual Override USE = In Use


Command Reference

Cross-system communication commandsThe cross-system communication (CSC) commands display information about each registered host or each registered listener. They also allow you to update gatekeeper information.

CSC,DISPLAY,HOSTS

Displays information about each registered host.

Syntax

F emcscf,CSC,DISplay,HOSTs,options

ParametersValid options are:

ALLSETS

Display all of the active CSC instances. Refer to “SCF.CSC.INSTANCE” on page 74.

CONTROLLER/CNTRL(ALL|id)

ALL produces a controller-by-controller display that shows all the hosts using each controller.

id specifies a DASD controller. You can specify the Symmetrix controller with either the 5-digit or 12-digit Symmetrix controller ID. If a 12-digit value is used, it must include a dash between the first 7 digits and the last 5 digits (for example, 1234567-12345). Use the 12-digit ID when multiple controllers use the same last 5 digits. Leading zeros are not required.


For example, you can specify either:

F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(0001845-00309)or

F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(1845-309)

In addition, if the last 5 digits in the above examples are not duplicated with another controller, you can simply specify the following:

F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(00309)or

F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(309)

SORT(column)

Sort the indicated output column as follows:

1. Sort by host name (column 1 in the display)

2. Sort by host ID (column 2)

3. Sort by VRM (column 3)

4. Sort by heartbeat (column 4)


Command Reference

5. Sort by registration date (column 5)

The default is to sort by host name.

TIMEOUT(seconds)

Specifies a timeout value between 10 and 120 seconds for the DISPLAY HOSTS request. The default value is 20 seconds.

During the display command, all active CSC hosts are pinged to see if they are active. The timeout value is used to terminate the request after a reasonable amount of time.

ExamplesThe SCF0660I message description in the EMC Mainframe Enablers Message Guide describes the fields displayed in the following examples.

Example 1 The following example displays the result of issuing the command without specifying a controller ID. CSC,DISPLAY,HOSTS produces a single display for all hosts participating in the CSC complex.

F EMCSCF,CSC,DISPLAY,HOSTS SCF0663I CSC,DISPLAY,HOSTS SCF0660I CSC HOST DISPLAY 294 CONTROLLER SERIAL NUMBER : 0001903-00344 (01) 0001926-00143 (02) 0001926-00312 (03) 0001926-00075 (04) 0001926-01173 (05) 0000000-06205 (06) 0001926-00290 (07) 0001903-00352 (08) 0001926-00291 (09) 0001846-00058 (10) 0001903-00341 (11) 0001926-00215 (12) 0001926-00209 (13) 0001926-00261 (14) 0001926-00296 (15) 0001926-00262 (16) HOST COUNT : 45 ------------HOST------------- --REGISTRATION--- PROCESS RESPNAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME CTRL-1-- --------2-------- -3- -4 --------5-------- ------- ----ER2 0108E94320980007 72M 5 06/24/10 14:52:59 000.872 01 X00B 010BE943209800CF 72M 5 06/24/10 17:17:23 000.360 02 X00B 010BE943209800CC 72M 3 06/24/10 08:49:55 000.362 03 X00C 010CE943209800D1 72M 5 06/24/10 17:29:24 000.358 04 X00C 010CE94320980088 72M 5 06/21/10 15:52:15 000.357 05 X00C 010CE94320980029 70M 5 06/24/10 17:35:08 000.358 06 X00D 010DE943209800C9 72M 3 06/22/10 16:09:17 000.355 03 X00D 010DE94320980091 70M 3 06/23/10 12:37:33 000.360 02 X00F 010FE94320980028 72M 3 06/24/10 13:39:59 000.358 06 X002 0102E94320980022 72MA 5 06/24/10 17:27:33 000.874 01 ... X114 01143F94209800C6 58M 3 06/23/10 15:54:16 000.874 01 X115 01153F94209800B1 70M 5 06/21/10 14:18:33 000.883 03SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED

Cross-system communication commands 155

Command Reference

Example 2 The following example produces a controller-by-controller display showing all the hosts using each controller.

SCF0663I CSC,D H CNTRL(ALL) SCF0660I CSC HOST DISPLAY 163 CONTROLLER SERIAL NUMBER : 0001874-00578 GATEKEEPER MVS DEVICE : F700 SYM DEVICE : 0100 HOST COUNT : 26 ------------HOST------------ --REGISTRATION--- PROCESS NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME -1-- --------2------- -3- -4 --------5-------- ------- X02 010235DE2096006D 580M 5 12/18/07 17:38:28 001.195 X02 010235DE2096008B 580M 5 12/10/07 15:51:55 001.195 ......SCF0660I CSC HOST DISPLAY 164 CONTROLLER SERIAL NUMBER : 0001926-00143 GATEKEEPER MVS DEVICE : 5100 SYM DEVICE : 0020 HOST COUNT : 8 ------------HOST------------ --REGISTRATION--- PROCESS NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME -1-- --------2------- -3- -4 --------5-------- ------- X02 010235DE2096008B 580M 5 12/13/07 23:38:07 001.226 X04 010435DE20960030 580M 5 12/19/07 20:14:36 000.151 ......SCF0660I CSC HOST DISPLAY 165 CONTROLLER SERIAL NUMBER : 0000000-03187 GATEKEEPER MVS DEVICE : 3400 SYM DEVICE : 0000 HOST COUNT : 15 ------------HOST------------ --REGISTRATION--- PROCESS NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME -1-- --------2------- -3- -4 --------5-------- ------- X02 010235DE2096008B 580M 5 11/20/07 14:40:58 001.309 X03 010335DE20960053 580M 5 12/13/07 14:13:18 001.584 X03 010335DE20960060 560M 5 12/07/07 21:43:42 002.088 ......SCF0660I CSC HOST DISPLAY 166 CONTROLLER SERIAL NUMBER : 0001903-00352 GATEKEEPER MVS DEVICE : 2F00 SYM DEVICE : 0060 HOST COUNT : 16 ------------HOST------------ --REGISTRATION--- PROCESS NAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME -1-- --------2------- -3- -4 --------5-------- ------- X02 010235DE2096006D 580M 5 12/18/07 17:38:28 001.630 X02 010235DE2096008B 580M 5 11/20/07 14:40:57 001.630 .........


Command Reference

Example 3 The following example displays registered hosts for a specified controller ID.

F EMCSCF,CSC,DIS,HOSTS,CNTRL(0001903-00097) SCF0663I CSC,DIS,HOSTS,CNTRL(0001903-00097) SCF0660I CSC HOST DISPLAY 937 CONTROLLER SERIAL NUMBER : 0001903-00097 GATEKEEPER MVS DEVICE : DEA3 SYM DEVICE : 00D3 HOST COUNT : 25 ------------HOST------------ --REGISTRATION--- PROCESSNAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME -1-- --------2------- -3- -4 --------5-------- -------X03 010335DE2096005C 580M 5 11/06/07 22:08:59 003.580X03 010335DE2096005F 580M 4 11/05/07 22:40:00 003.581X04 010435DE20960062 580M 5 11/05/07 19:53:53 005.060X05 010535DE2096004F 580M 5 10/15/07 20:50:04 005.060X05 010535DE2096005F 580M 4 11/05/07 20:02:25 002.040X1D 011D358E20960058 570M 5 11/07/07 12:29:24 004.056X1D 011D358E2096006B 580M 5 11/07/07 14:30:54 000.030X1E 011E358E20960092 580M 3 10/31/07 18:59:30 002.544X1E 011E358E20960181 570M 5 11/05/07 13:55:52 003.581X1E 011E358E20960139 580M 5 10/31/07 19:03:41 002.040X11C 011C358E20960067 580M 5 09/26/07 14:20:15 000.532X11C 011C358E20960087 580M 2 11/05/07 19:52:25 001.537X18 0118358E2096004A 570M 5 10/26/07 19:00:31 001.537 SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED

Example 4 The following example displays registered hosts sorted by the host ID value.

F EMCSCF,CSC,DISPLAY,HOSTS,SORT(2) SCF0663I CSC,DISPLAY,HOSTS,SORT(2) SCF0660I CSC HOST DISPLAY 943 CONTROLLER SERIAL NUMBER : 0001879-90132 (01) 0001903-00341 (02) 0000000-05520 (03) 0001901-00849 (04) 0001903-00344 (05) 0001903-00353 (06) 0001000-06121 (07) 0001845-01324 (08) 0001874-00578 (09) HOST COUNT : 29 ------------HOST------------ --REGISTRATION--- PROCESS RESPNAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME CTRL-1-- --------2------- -3- -4 --------5-------- ------- ----X02 010235DE2096006D 580M 5 10/30/07 13:13:15 000.597 01 X03 010335DE2096005C 580M 5 11/06/07 22:08:59 001.051 02 X03 010335DE2096005F 580M 4 11/05/07 22:40:00 000.537 03 X04 010435DE2096001F 580M 5 10/29/07 13:11:32 002.268 01 X04 010435DE2096002A 580M 4 11/06/07 21:31:27 000.567 04 X04 010435DE2096002F 580M 5 10/30/07 18:30:22 001.694 05 X04 010435DE20960045 580M 5 11/05/07 17:09:31 000.547 02 X04 010435DE20960053 580M 5 11/05/07 21:36:23 001.448 06 X04 010435DE20960062 580M 5 11/05/07 19:53:53 000.567 04 X05 010535DE2096001E 580M 4 10/30/07 20:37:59 000.567 04 X05 010535DE2096004F 580M 5 10/15/07 20:50:04 000.586 07 X05 010535DE20960050 580M 5 10/17/07 19:50:11 001.064 08 X05 010535DE2096005F 580M 4 11/05/07 20:02:25 000.565 09SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED


Command Reference

Example 5 The following example displays registered hosts with a timeout value of 20 seconds specified.

F EMCSCF,CSC,DISPLAY,HOSTS,TIMEOUT(20) SCF0663I CSC,DISPLAY,HOSTS,TIMEOUT(20) SCF0660I CSC HOST DISPLAY 956 CONTROLLER SERIAL NUMBER : 0001903-00341 (01) 0001901-00849 (02) 0000000-05520 (03) 0001903-00344 (04) 0001879-00699 (05) 0001825-00978 (06) 0001874-00578 (07) 0001903-00338 (08) HOST COUNT : 28 ------------HOST------------ --REGISTRATION--- PROCESS RESPNAME IDENTIFIER VRM HB MM/DD/YY HH:MM:SS TIME CTRL-1-- --------2------- -3- -4 --------5-------- ------- ----X02 010235DE2096006D 580M 5 10/30/07 13:13:15 000.559 01 X03 010335DE2096005C 580M 5 11/06/07 22:08:59 000.550 02 X03 010335DE2096005F 580M 4 11/05/07 22:40:00 000.560 03 X04 010435DE2096002A 580M 4 11/06/07 21:31:27 000.087 04 X04 010435DE2096002F 580M 5 10/30/07 18:30:22 000.586 05 X04 010435DE20960045 580M 5 11/05/07 17:09:31 001.563 01 X04 010435DE20960053 580M 5 11/05/07 21:36:23 000.640 06 X04 010435DE20960062 580M 5 11/05/07 19:53:53 001.576 07 X04 010435DE2096001F 580M 5 10/30/07 18:42:08 000.550 02 X05 010535DE2096001E 580M 4 10/30/07 20:37:59 000.560 04 X05 010535DE20960050 580M 5 10/17/07 19:50:11 001.565 08SCF0668I CSC DISPLAY HOSTS COMMAND COMPLETED

CSC,DISPLAY,LISTENER

Displays information about each registered listener.

Note: Listeners are added by EMC and other vendor code to support particular functions which are to be processed through the CSC. Use of the CSC,DISPLAY,LISTENERS command may be requested by EMC technical support.

Syntax

F emcscf,CSC,DISplay,LISTENer,options



Specifies a DASD controller. You can specify the Symmetrix controller with either the 5-digit or 12-digit Symmetrix controller ID. If a 12-digit value is used, it must include a dash between the first 7 digits and the last 5 digits (for example, 1234567-12345). Use the 12-digit ID when multiple controllers use the same last 5 digits. Leading zeros are not required.



Command Reference

For example, you can specify either:

F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(0001845-00309)or

F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(1845-309)

In addition, if the last 5 digits in the above examples are not duplicated with another controller, you can simply specify the following:

F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(00309)or

F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(309)

ExampleThe following example displays registered CSC listeners by controller ID.

Note: The SCF0664I message description in the EMC Mainframe Enablers Message Guide describes the fields displayed in this example.

F EMCSCF,CSC,DIS,LISTENER,CNTRL(0001903-00097) SCF0663I CSC,DIS,LISTENER,CNTRL(0001903-00097) SCF0664I CSC LISTENER DISPLAY 734 CONTROLLER SERIAL NUMBER : 0001903-00097 CODE DIAGNAME ASID REGISTRATION LISTENER TYPE REQCOUNT ATTRIBUTES MM/DD/YY HH:MM:SS DUPCOUNT ---- -------- ---- -------- -------- -------- ---- -------- ---------- 001 PING 006B 11/07/07 14:30:55 SCFCHC01 RTN 4 ALL 3 002 MROUTE 006B 11/07/07 14:30:55 SCFCHC02 RTN 0 ALL 003 HOSTREG 006B 11/07/07 14:30:55 SCFCHC03 RTN 22 ALL 004 HOSTUREG 006B 11/07/07 14:30:55 SCFCHC04 RTN 23 ALL 005 DEVSERV 006B 11/07/07 14:30:55 SCFCHC05 RTN 0 ALL 006 S/GNS 006B 11/07/07 14:31:03 1972D2A8 ECB 0 ALL 007 SCFCMD 006B 11/07/07 14:30:55 SCFCHC07 RTN 0 ALL 107 NACT NREG ???????? ??? 13 109 AutoSwap 006B 11/07/07 14:31:03 197CC830 ECB 2 ALL/NTFY 114 NACT NREG ???????? ??? 1 127 NACT NREG ???????? ??? 11 134 NACT NREG ???????? ??? 5 169 NACT NREG ???????? ??? 28 SCF0668I CSC DISPLAY LISTENERS COMMAND COMPLETED


Command Reference

CSC,REFRESH

Specifies either:

◆ That CSC should be activated if SCF.CSC.ACTIVE=YES has been set in the SCFINI startup parameter file

◆ That all controllers with CSC active should re-evaluate the gatekeeper device

If a GATEKEEPER list change has been made in the SCFINI startup parameter file, then issue the INI,REFRESH operator command before you issue the CSC,REFRESH command.

Note: “SCF.CSC.ACTIVE” on page 68 and “SCF.CSC.GATEKEEPER.LIST” on page 72 provide more information.

Syntax

F emcscf,CSC,REFResh

ParametersNone.

Example

Note: The SCF0652I message description in the EMC Mainframe Enablers Message Guide describes the fields displayed in this example.

F EMCSCF,CSC,REFRESH SCF0663I CSC,REFRESH SCF0666I CSC REFRESH SCHEDULED FOR 32 CONTROLLERS SCF0652I CSC (0001903-00353) AREA:00010000/00030000, GATEKEEPER:C400(SYMM07/5X71/00000/F8) SCF0652I CSC (0001901-03011) AREA:00010000/00030000, GATEKEEPER:386F(SYMM07/5X73/00000/F8) SCF0652I CSC (0000000-05520) AREA:00010000/00030000, GATEKEEPER:4B01(SYMM05/5X68/00000/80) SCF0652I CSC (0000000-06183) AREA:00010000/00030000, GATEKEEPER:D601(SYMM06/5X71/00000/F8) SCF0652I CSC (0000000-06185) AREA:00010000/00030000, GATEKEEPER:6F91(SYMM06/5X71/00000/F8) SCF0652I CSC (0001879-00699) AREA:00010000/00030000, GATEKEEPER:EE01(SYMM06/5X71/00000/F8) SCF0652I CSC (0001901-03115) AREA:00010000/00030000, GATEKEEPER:E470(SYMM07/5X73/00000/F8) ...etc


Command Reference

Device commandsThe device commands allow you to obtain device information.

DEV,CH,CNTRL

Indicates if a specified Enginuity patch has been applied to a controller.

Syntax

F emcscf,DEV,CH,CNTRL(nnnnnnn-nnnnn)ppppp

F emcscf,DEV,CH,CONTROLLER(nnnnnnn-nnnnn)ppppp

Parameters

nnnnnnn-nnnnn

Specifies a DASD controller. Can be either the full 12-digit Symmetrix serial number or just the last 5 digits of the number. (Use the 12-digit ID when multiple controllers use the same last 5 digits.)


ppppp

Specifies the Enginuity patch number.

ExampleF EMCSCF,DEV,CH,CONTROLLER(0001901-03115) 31536 SCF0341I DEV,CH,CONTROLLER(0001901-03115) 31536 SCF0363I Patch 31536 has been applied. SCF0356I DEVICE CHECKPATCH COMMAND COMPLETED.

DEV,DISPLAY

Allows you to display device information.

Syntax

F emcscf,DEV,DISplay,options



Specifies a DASD controller. id can be either the full 12-digit Symmetrix serial number or just the last 5 digits of the number. (Use the 12-digit ID when multiple controllers use the same last 5 digits.) “Example 1” on page 164 provides additional information.


CNAME(name)

Specifies the assigned controller name. If the name contains blanks, enclose the name in quotation marks. “Example 3” on page 165 provides additional information.

Device commands 161

Command Reference

Note: Chapter 5, “Naming Controllers and validating paths,” describes how to assign unique controller names.

DEVice(id1[-id2])[VOL][ATTR|ONLYATTR][TRU]

Specifies a DASD device (id1) or range of devices (id2). For ResourcePak Base V7.3 and higher, this value may be either 4 or 5 digits. For earlier versions, this must be a 4-digit value. See “Multiple subchannel device sets” on page 162 for more information.

VOL

If VOL is specified, it will force an I/O to an offline device to read the volser.

ATTR

The ATTR and ONLYATTR options allow you to view the host attributes of z/OS devices, including the Host Read Only (HRO) attribute.

ATTR generates the existing DEV,DIS DEV display plus the host attributes for the requested devices.

ONLYATTR

ONLYATTR generates the existing DEV,DIS DEV display plus the host attributes for the requested devices; however, all devices with no host attributes are omitted. Only devices with at least one host attribute are displayed.

“Example 6” on page 167 provides an example using the ATTR option. “Example 7” on page 167 shows the use of the ONLYATTR option.

TRU

The addition of TRU to the end of the regular device display causes additional lines to be displayed for each device, containing recent time and count fields. Refer to “TRU monitor operator commands” on page 348 for more information on the TRU commands.

Multiple subchannel device sets — Starting with ResourcePak Base V7.3, the DEV(id) value can be a 5-digit device number in the standard form sdddd. If s is specified, then this is an explicit request for a device from that subchannel set. A value of 4 digits or less will result in the active device (in the base subchannel set) being displayed.

“Example 4” on page 166 provides an example using standard 4-digit addressing. “Example 5” on page 166 shows the use of alternate subchannel set 5-digit addressing.

As of version 7.3, both AutoSwap and ConGroup support IBM multiple subchannel addressing. The multiple subchannel feature allows application addressable devices to remain in 4-digit device range (0000-FFFF) and yet at the same time allow system addressable devices to be accessed outside this range, using a subchannel of 0-3 added to the device address range.

For example, an application addressable device of 1234 with a subchannel set number of 0, would be 01234, and the complete address range for other devices in subchannel set 0 would be 00000-0FFFF. In most cases, devices in the base (or active) subchannel set are usually considered as 4-digit devices.


Command Reference

A subchannel set of 1, which is beyond the base subchannel set, provides a system addressable range of 10000-1FFFF. For example, device 1234 in subchannel set 1 would be 11234.

To specify a z/OS device number when multiple subchannel set feature is active, use sdddd.

Where:

s = indicates the subchannel set

dddd = indicates the 4-digit device number

Note: To set the option to use multiple subchannel addressing, refer to “SCF.DEV.MULTSS=YES|NO” on page 81.

REMOTE

Specifies controllers that can only be found across an RDF connection. For ResourcePak Base V7.3 and higher, command output has been modified to include the subchannel set number, if the SCF initialization parameter SCF.DEV.MULTSS=YES, or if the subchannel set number is non-zero, or if the device is SPECIAL. “Example 14” on page 170 provides additional information.

SSID(id)

Specifies an SSID. For ResourcePak Base V7.3 and higher, command output has been modified to include the subchannel set number, if the SCF initialization parameter SCF.DEV.MULTSS=YES, or if the subchannel set number is non-zero, or if the device is SPECIAL. “Example 9” on page 167 provides additional information.

SUMmary

Specifies a summary display of the controller at startup. It also displays remote controllers discovered as many as 2 hops away. A remote controller is one to which SCF does not have a local CCUU connection. “Example 10” on page 168 provides additional information.

Note: If you exclude devices from SCF, then SCF may still discover the controller. SCF may then treat it as a remote controller if there are active SRDF connections to it from a controller that SCF views as a locally-attached controller.

TOPOlogy

Displays a list of the controllers discovered by SCF. For ResourcePak Base V7.3 and higher, command output has been modified to include the subchannel set number, if the SCF initialization parameter SCF.DEV.MULTSS=YES, or if the subchannel set number is non-zero, or if the device is SPECIAL. “Example 13” on page 169 provides additional information.

VOLume(vvvvvv)

Specifies a volume. “Example 11” on page 169 provides additional information.

Device commands 163

Command Reference

ExamplesExample 1 The following example shows the output from DEV, DISplay, CNTRL(nnnnnnn-nnnnn)

issued from a Symmetrix VMAX 20K system. The output indicates the Enginuity major and minor levels, specifies the DARE (Data at Rest Encryption) setting, lists features available with eLicensing, and provides information about the gatekeepers defined on the controller and which gatekeeper is currently in use by SCF.

Note: The DARE setting and eLicensing features display only with Enginuity level 5875 or higher.

SCF0341I DEV DIS CONTROLLER(00192600291) SCF0421I CNTRL NAME=A controller SCF0428I Emulating 2107 - 00000000AAWH.SCF0444I Controller type is VMAX20K SCF0448I Configuration CRC is X'DE1C84C7' (changes: add = 1, delete = 0, swap = 0)SCF0449I Last configuration change occurred at 15.54.17 on 02/05/2013SCF0439I DARE is ON SCF0440I Features available on 000192600291SCF0441I SYMM_VMAX_ARRAY SCF0441I SYMM_VMAX_TF_CLONE SCF0441I SYMM_VMAX_TF_SNAP SCF0441I SYMM_VMAX_SRDF_S SCF0441I SYMM_VMAX_SRDF_A SCF0441I SYMM_VMAX_SRDF_STARSCF0441I SYMM_VMAX_DCP SCF0441I SYMM_VMAX_SPC SCF0441I SYMM_VMAX_OPTIMIZERSCF0441I SYMM_VMAX_FAST SCF0441I SYMM_VMAX_FAST_VP SCF0441I SYMM_VMAX_SRDF SCF0360I CONTROLLER 0001926-00291 HAS 1 SUBSYSTEMS AND IS AT MCLEVEL 5875.156 SCF0345I - 8A00 SCF4011I CONTROLLER 0001926-00291 is currently using CCUU 8A70 as its SCF

gatekeeper.SCF0357I CONTROLLER 0001926-00291 HAS 1439 PATHS TO OTHER CONTROLLERS SCF0359I MHOP RMT CNTRL MC SCF0358I 0001 000192600291 5875.156 SCF0358I 0002 000000006185 5671.082..SCF0356I DEVICE DISPLAY CNTRL COMMAND COMPLETED.

Note: If you issue this command from a Symmetrix VMAX 40K system, the license bundles are listed, rather than the individual features and the SCF0444I message indicates it is a VMAX 40K system, “SCF0444I Controller type is VMAX40K .”


Command Reference

Example 2 When a Symmetrix VMAX™ Series with Enginuity level 5874 or higher emulates an IBM 2107, it externally represents the serial number as an alphanumeric serial number in order to be compatible with IBM command output. This example shows output from a DEV,DISplay,CNTRL command with an alphanumeric serial number.

Note: Internally, Symmetrix VMAX Series systems retain a numeric serial number for IBM 2107 emulations. Correlation between the numeric and alphanumeric serial numbers is handled within Enginuity.

/F emcscf,DEV DIS CNTRL(0AAWH)SCF0341I DEV DIS CNTRL(0AAWH) SCF0421I CNTRL NAME=NEW_YORK_PROD01SCF0428I Emulating 2107 - 00000000AAWH.SCF0444I Controller type is VMAX20K SCF0448I Configuration CRC is X'DE1C84C7' (changes: add = 1, delete = 0, swap = 0)SCF0449I Last configuration change occurred at 15.54.17 on 02/05/2013SCF0439I DARE is ONSCF0440I Features available on 000192600291SCF0441I SYMM_VMAX_ARRAYSCF0441I SYMM_VMAX_TF_CLONESCF0441I SYMM_VMAX_TF_SNAPSCF0441I SYMM_VMAX_SRDF_SSCF0441I SYMM_VMAX_SRDF_ASCF0441I SYMM_VMAX_SRDF_STARSCF0441I SYMM_VMAX_DCPSCF0441I SYMM_VMAX_SPCSCF0441I SYMM_VMAX_OPTIMIZERSCF0441I SYMM_VMAX_FASTSCF0441I SYMM_VMAX_FAST_VPSCF0441I SYMM_VMAX_SRDSCF0360I CONTROLLER 0001926-00291 HAS 2 SUBSYSTEMS AND IS AT MCLEVEL 5874.103 SCF0345I - 8A00 8A01 SCF4011I CONTROLLER 0001926-00291 is currently using CCUU 8A00 as its SCF

gatekeeper. SCF0357I CONTROLLER 0001926-00291 HAS 12 PATHS TO OTHER CONTROLLERS SCF0359I MHOP RMT CNTRL MC SCF0358I 00FF 000190300353 5773.134 SCF0358I 07FF 000192600296 5874.103 SCF0358I 1AFF 000192600143 5874.103 SCF0358I 1FFF 000192600143 5874.103 SCF0358I 2EFF 000192600296 5874.103 SCF0358I 2FFF 000192600296 5874.103 SCF0358I 54FF 000192600261 5874.103 SCF0358I 73FF 000192600143 5874.103 SCF0358I 74FF 000192600261 5874.103 SCF0358I 83FF 000192600143 5874.103 SCF0358I 84FF 000192600261 5874.103 SCF0358I E0FF 000192600261 5874.103 SCF0356I DEVICE DISPLAY CNTRL COMMAND COMPLETED.

Example 3 The following example shows the output from DEV,DISplay,CNAME:

F EMCSCF,DEV,DIS,CNAME(UMB) SCF0341I DEV,DIS,CNAME(UMB) SCF0421I CNTRL NAME=UMBSCF0444I Controller type is 2000P-M2SCF0448I Configuration CRC is X'DBDD12DC' (changes: add = 1, delete = 1, swap = 0)SCF0449I Last configuration change occurred at 16.12.41 on 02/05/2013SCF0360I CONTROLLER 0001879-90175 HAS 2 SUBSYSTEMS AND IS AT MCLEVEL 5671.060SCF0345I - 9400 9401 SCF4010I CONTROLLER 0001879-90175 has EMC-FLASH enabled SCF4300I CONTROLLER 0001879-90175 is missing one or more of the following required FLASH patches.

Device commands 165

Command Reference

SCF4011I CONTROLLER 0001879-90175 is currently using CCUU 9400 as its SCF gatekeeper. SCF0357I CONTROLLER 0001879-90175 HAS 9 PATHS TO OTHER CONTROLLERS SCF0359I MHOP RMT CNTRL MC SCF0358I 00FF 000187900699 5671.060 SCF0358I 01FF 000187900699 5671.060 SCF0358I 02FF 000187900699 5671.060 SCF0358I 05FF 000187900699 5671.060 SCF0358I 10FF 000187900699 5671.060 SCF0358I 19FF 000187900699 5671.060 SCF0358I 20FF 000187900699 5671.060 SCF0358I 25FF 000187900699 5671.060 SCF0358I 3FFF 000187900699 5671.060 SCF0356I DEVICE DISPLAY CNTRL COMMAND COMPLETED.

Example 4 The following example displays the output from DEV, DISplay, DEVice(ccuu). The display identifies the following: CCUU, volser if known, last known status; manufacturer, controller ID, SSID, symdev. The display may also include optional lss and cuaddr data following the symdev.

F EMCSCF,DEV,DIS,DEV(DE10) SCF0341I DEV,DIS,DEV(DE10) SCF0350I DE10(USK272) ONLINE EMC-000190300097-DE00-0272-00-10SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Example 5 The following example displays the output from DEV, DISplay, DEVice(ccuu) when displaying a device using the multiple subchannel addressing feature. The rules for displaying a device as full 5-digit value are as follows:

◆ The SCF INI parameter SCF.DEV.MULTSS=YES is specified

◆ Or, the subchannel set number of the active device is non-zero

◆ Or, the device is marked as special, that is, the device is in an alternate subchannel.

If SCF.DEV.MULTSS=YES is specified, the DEV DIS DEV command will always include the subchannel set number:

SCF0341I DEV DIS DEVICE(4910-4912) SCF0350I 04910( ) OFFLINE EMC-000192600262-F850-0DC0-01-10SCF0350I 04911( ) OFFLINE EMC-000192600262-F850-0DC1-01-11SCF0350I 04912( ) OFFLINE EMC-000192600262-F850-0DC2-01-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

The output of the DEV DIS DEV command will always include the subchannel set number if you implicitly specify a subchannel set number in the command. An additional state is displayed for SPECIAL devices as shown below where the device is located in an alternate subchannel set. For example:

SCF0341I DEV DIS DEVICE(04910-04912) SCF0350I 04910( ) OFFLINE EMC-000192600262-F850-0DC0-01-10SCF0350I 04911( ) OFFLINE EMC-000192600262-F850-0DC1-01-11SCF0350I 04912( ) OFFLINE EMC-000192600262-F850-0DC2-01-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED. SCF0341I DEV DIS DEVICE(14910-14912) SCF0350I 14910( ) SPECIAL EMC-000192600261-4850-0810-02-10SCF0350I 14911( ) SPECIAL EMC-000192600261-4850-0811-02-11SCF0350I 14912( ) SPECIAL EMC-000192600261-4850-0812-02-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.


Command Reference

If the SCF initialization parameter is set to SCF.DEV.MULTSS=NO, if the device is not special and the subchannel set number is equal to zero, and the subchannel set number is not implicitly specified in the command, the display will appear as it did previously, for example:

SCF0341I DEV DIS DEVICE(4910-4912) SCF0350I 4910( ) OFFLINE EMC-000192600262-F850-0DC0-01-10SCF0350I 4911( ) OFFLINE EMC-000192600262-F850-0DC1-01-11SCF0350I 4912( ) OFFLINE EMC-000192600262-F850-0DC2-01-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Example 6 The following example displays the output from DEV, DISplay, DEVice command with the ATTR option specified.

SCF0341I DEV DIS DEV(5100-5103) ATTR SCF0350I 05100( ) OFFLINE EMC-000192600143-5100-0028-00-00 NO DEVICE ATTRIBUTESSCF0350I 05101( ) OFFLINE EMC-000192600143-5100-0029-00-01 NO DEVICE ATTRIBUTESSCF0350I 05102( ) OFFLINE EMC-000192600143-5100-002A-00-02 NO DEVICE ATTRIBUTESSCF0350I 05103( ) OFFLINE EMC-000192600143-5100-002B-00-03 HOST READ ONLY SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

SCF0341I DEV DIS DEV(6E40-6E43) ATTR SCF0350I 06E40( ) OFFLINE EMC-000000006185-6C02-0180-02-40 NO DEVICE ATTRIBUTES SCF0350I 06E41( ) OFFLINE EMC-000000006185-6C02-0181-02-41 NO DEVICE ATTRIBUTES SCF0350I 06E42(U6A182) ONLINE EMC-000000006185-6C02-0182-02-42 HOST READ ONLY (PL52)SCF0350I 06E43( ) OFFLINE EMC-000000006185-6C02-0183-02-43 NO DEVICE ATTRIBUTES SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Example 7 The following example displays the output from DEV, DISplay, DEVice command with the ONLYATTR option specified. Note that any devices with no host attributes are omitted from the display.

SCF0341I DEV DIS DEV(5100-5103) ONLYATTR SCF0350I 05103( ) OFFLINE EMC-000192600143-5100-002B-00-03 HOST READ ONLYSCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

SCF0341I DEV DIS DEV(6E40-6E43) ONLYATTR SCF0350I 06E42(U6A182) ONLINE EMC-000000006185-6C02-0182-02-42 HOST READ ONLY (PL52)SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Example 8 The following example displays a DASD range of devices.

F EMCSCF,DEV,DIS,DEV(DE7C-DE7F) SCF0341I DEV,DIS,DEV(DE7C-DE7F) SCF0350I DE7C(USK09C) ONLINE EMC-000190300097-DE00-009C-00-7C SCF0350I DE7D(USK09D) ONLINE EMC-000190300097-DE00-009D-00-7D SCF0350I DE7E(USK09E) ONLINE EMC-000190300097-DE00-009E-00-7E SCF0350I DE7F(USK09F) ONLINE EMC-000190300097-DE00-009F-00-7F SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Example 9 The following example displays an SSID and lists each device defined in that SSID:

F EMCSCF,DEV,DIS,SSID(CB00) SCF0341I DEV,DIS,SSID(CB00) SCF0347I CONTROLLER 0001903-00353, SSID CB00 HAS 224 DEVICES SCF0348I - C600(OFLINE) C601(OFLINE) C602(OFLINE) C603(OFLINE)SCF0348I - C604(OFLINE) C605(OFLINE) C606(OFLINE) C607(OFLINE)SCF0348I - C608(OFLINE) C609(OFLINE) C60A(OFLINE) C60B(OFLINE)SCF0348I - C60C(OFLINE) C60D(OFLINE) C60E(OFLINE) C60F(OFLINE)SCF0348I - C610(OFLINE) C611(OFLINE) C612(OFLINE) C613(OFLINE)SCF0348I - C614(OFLINE) C615(OFLINE) C616(OFLINE) C617(OFLINE)..

Device commands 167

Command Reference

.SCF0348I - C6DC(OFLINE) C6DD(OFLINE) C6DE(OFLINE) C6DF(OFLINE) SCF0356I DEVICE DISPLAY SSID COMMAND COMPLETED.

For ResourcePak Base V7.3 and higher, command output as a result of the DEV DIS SSID (ssid) command has been modified to include the subchannel set number, if the SCF initialization parameter SCF.DEV.MULTSS=YES, or if the subchannel set number is non-zero, or if the device is SPECIAL. For example:

SCF0341I DEV DIS SSID(F850) SCF0347I CONTROLLER 0001926-00262, SSID F850 HAS 8 DEVICES SCF0348I - 04900(UTBDB0) 04901(OFLINE) 04902(OFLINE) 04903(OFLINE)SCF0348I - 04904(OFLINE) 04905(OFLINE) 04906(OFLINE) 04907(OFLINE)SCF0356I DEVICE DISPLAY SSID COMMAND COMPLETED.SCF0341I DEV DIS SSID(4850) SCF0347I CONTROLLER 0001926-00261, SSID 4850 HAS 8 DEVICES SCF0348I - 14900(*SPEC*) 14901(*SPEC*) 14902(*SPEC*) 14903(*SPEC*)SCF0348I - 14904(*SPEC*) 14905(*SPEC*) 14906(*SPEC*) 14907(*SPEC*)SCF0356I DEVICE DISPLAY SSID COMMAND COMPLETED.

An additional state is displayed for SPECIAL devices (displayed as *SPEC*) as shown above where the device is located in an alternate subchannel set.

Example 10 The following example displays the output from DEV, DISplay, SUM. For each Symmetrix system SCF discovers, the command output indicates the DARE setting for the system, provides a summary of controllers and SSIDs along with a count of the devices for each SSID, and displays the available eLicensing features:

Note: The DARE (Data at Rest Encryption) setting and eLicensing features only display with Enginuity level 5875 or higher.

SCF0341I DEV DIS SUM SCF0421I CNTRL NAME=A controller SCF0428I Emulating 2107 - 00000000AAWH.SCF0444I Controller type is VMAX20K SCF0439I DARE is ON SCF0402I SER# 0001926-00291, SSID 8A00 HAS 3 DEVICES IN SPLIT 0 (AAAWH) SCF0450I Microcode level is 5875.156SCF0448I Configuration CRC is X'DE1C84C7' (changes: add = 1, delete = 0, swap = 0)SCF0449I Last configuration change occurred at 15.54.17 on 02/05/2013SCF0439I DARE is ONSCF0440I Features available on 000192600291SCF0441I SYMM_VMAX_ARRAY SCF0441I SYMM_VMAX_TF_CLONE SCF0441I SYMM_VMAX_TF_SNAP SCF0441I SYMM_VMAX_SRDF_S SCF0441I SYMM_VMAX_SRDF_A SCF0441I SYMM_VMAX_SRDF_STARSCF0441I SYMM_VMAX_DCP SCF0441I SYMM_VMAX_SPC SCF0441I SYMM_VMAX_OPTIMIZERSCF0441I SYMM_VMAX_FAST SCF0441I SYMM_VMAX_FAST_VP SCF0441I SYMM_VMAX_SRDF SCF0421I CNTRL NAME=Another controller SCF0428I Emulating 2107 - 00000000AAWP. SCF0444I Controller type is VMAX-1SCF0439I DARE is OFF SCF0402I SER# 0001926-00296, SSID 5500 HAS 39 DEVICES IN SPLIT 0 (AAAWP)SCF0450I Microcode level is 5875.249SCF0448I Configuration CRC is X'E6B8968D' (changes: add = 1, delete = 0, swap = 2)SCF0449I Last configuration change occurred at 17.34.29 on 02/05/2013


Command Reference

SCF0439I DARE is OFFSCF0440I Features available on 000192600296SCF0441I SYMM_VMAX_ARRAY SCF0441I SYMM_VMAX_TF_CLONE SCF0441I SYMM_VMAX_TF_SNAP SCF0441I SYMM_VMAX_SRDF_S SCF0441I SYMM_VMAX_SRDF_A SCF0441I SYMM_VMAX_SRDF

Note: If you issue this command from a Symmetrix VMAX 40K system, the license bundles are listed, rather than the individual features, and the SCF0444I message indicates it is a VMAX 40K system.

Example 11 The following example displays the output from DEV, DISplay, DEVice(ccuu), VOL. The display identifies the volser of the offline device.

SCF0341I DEV,DIS,DEV(0600),VOL SCF0350I 0600(U6J000) OFFLINE EMC-000000006140-DA00-0000-00-00 SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Example 12 The following example displays a DASD device by VOLSER and identifies the controller, SSID, manufacturer, and last known status:

F EMCSCF,DEV,DIS,VOL(USK274) SCF0341I DEV,DIS,VOL(USK274) SCF0350I DE12(USK274) ONLINE EMC-000190300097-DE00-0274-00-12 SCF0356I DEVICE DISPLAY VOLUME COMMAND COMPLETED.

Example 13 The following example shows the output from DEV, DISplay, TOPOlogy:

F EMCSCF,DEV,DIS,TOPOLOGY SCF0341I DEV,DIS,TOPOLOGY SCF0358I LCL SERIAL# MC CCUU MHOP ------ REMOTE SCF0358I 000190300044 5772.083 0C00 23FF 000190103389 5773.034SCF0358I ---------------- SCF0358I 26FF 000000006110 5671.066SCF0358I -------------------------------- SCF0358I 000190300097 5772.083 DE5F 00FF 000190300338 5772.083SCF0358I ---------------- SCF0358I 01FF 000190300338 5772.083SCF0358I ---------------- SCF0358I 02FF 000190300338 5772.083SCF0358I ---------------- SCF0358I 03FF 000190300338 5772.083SCF0358I ---------------- SCF0358I 04FF 000190300338 5772.083SCF0356I DEVICE DISPLAY TOPOLOGY COMMAND COMPLETED.

For ResourcePak Base V7.3 and higher, command output as a result of the DEV DIS TOPOLOGY command has been modified to include the subchannel set number, if the SCF initialization parameter SCF.DEV.MULTSS=YES, or if the subchannel set number is non-zero, or if the device is SPECIAL. For example:

SCF0341I DEV DIS TOPOLOGY SCF0358I LCL SERIAL# MC CCUU MHOP ------ REMOTE SCF0358I 000192600143 5874.248 05100 00FF 000192600143 5874.248SCF0358I ---------------- SCF0358I 01FF 000192600143 5874.248SCF0358I ---------------- SCF0358I 0305 000190300353 5773.163SCF0358I 0306 000190300353 5773.163

Device commands 169

Command Reference

SCF0358I 0307 000190300353 5773.163SCF0358I 0309 000190300354 5771.112SCF0358I 030F 000192600296 5875.161SCF0358I -------------------------------- SCF0356I DEVICE DISPLAY TOPOLOGY COMMAND COMPLETED.

The fields in the above examples have the following meanings:

◆ LCL SERIAL#

The serial number of the controller that is attached to the LPAR.

◆ MC

The Enginuity microcode level.

◆ CCUU

The z/OS device number used as the SCF gatekeeper for the channel-attached device.

◆ MHOP

The multi-hop path for the remote device. (A value of FF indicates this hop is not used.)

◆ REMOTE

The serial number of the EMC controller on the other end of the multi-hop path and the Enginuity level it is running. The controller is remote since it can be accessed over the multi-hop path.

Example 14 The following example shows the output from DEV, DISplay, REMOTE:

F TV9SCF,DEV,DIS,REMOTE SCF0341I DEV,DIS,REMOTE SCF0358I RMT SERIAL# MC CUU UCB@ MHOP ------SCF0358I 000184501716 5568.068 E400 027CD2E8 0AFFSCF0358I ----------------SCF0358I E400 027CD2E8 0BFFSCF0358I ----------------SCF0358I 000185701724 5568.068 1113 0217A9C8 00FFSCF0358I ----------------SCF0358I 000187990072 5670.099 8000 024C9698 19FFSCF0358I --------------SCF0358I E400 027CD2E8 17FFSCF0358I ----------------SCF0358I 000190100509 5772.059 F800 02895A68 01FFSCF0358I ----------------SCF0358I 000190300342 5773.060 0600 021364C8 02FFSCF0358I ----------------SCF0358I 0600 021364C8 0EFFSCF0358I --------------SCF0358I 3400 0228A218 03FFSCF0358I ----------------SCF0356I DEVICE DISPLAY REMOTE COMMAND COMPLETED.

For ResourcePak Base V7.3 and higher, command output as a result of the DEV DIS REMOTE command has been modified to include the subchannel set number, if the SCF initialization parameter SCF.DEV.MULTSS=YES, or if the subchannel set number is non-zero, or if the device is SPECIAL. For example:

SCF0341I DEV DIS REMOTE SCF0358I RMT SERIAL# MC CCUU UCB@ MHOP ------SCF0358I 000000006185 5671.082 04800 022E82D0 0002 SCF0358I 04800 022E82D0 0027


Command Reference

SCF0358I 04800 022E82D0 002F SCF0358I 04800 022E82D0 003D SCF0358I ---------------- SCF0356I DEVICE DISPLAY REMOTE COMMAND COMPLETED.

The fields in the above examples have the following meanings:

◆ RMT SERIAL#

The serial number of the remote controller.

◆ MC

The Enginuity microcode level.

◆ CCUU

The z/OS device number used as the SCF gatekeeper for the non channel-attached device.

◆ UCB@

The UCB address of the ccuu.

◆ MHOP

The multi-hop path for the remote device. (A value of FF indicates this hop is not used.)

DEV,REFRESH

Queries each of the specified DASD devices with one or more physical I/Os. This can take from seconds to several minutes.

This command can be used after adding new devices to a Symmetrix system for a rediscovery of all Symmetrix devices.

Note: EMC recommend customers issue a DEV REFRESH when the Enginuity level code has been upgraded to a higher version, for example going from 5875 to 5876.

Syntax

F emcscf,DEV,REFRESH[,GATEKeepers]

Parameters

GATEKeepers

Refreshes and revalidates the current gatekeeper devices. Typically, you would issue this command after you issue an INI REFRESH command to re-read the SCF control file.

Note: “INI,REFRESH” on page 147 provides more information about INI REFRESH.

Device commands 171

Command Reference

ExampleThe following example shows the messages written after you issue DEV, REFRESH, GATEKEEPERS.

F EMCSCF,DEV,REFRESH,GATEKSCF0341I DEV,REFRESH,GATEK SCF0342I DEVICE REFRESH COMMAND ACCEPTED. SCF0417I REFRESH COMPLETE.

DEV,RESCAN

Compares the cached list of devices to the system’s list of devices and adds new devices to the internal tables.

This command is faster than the DEV,REFRESH command, but it does not revalidate devices in the SCF tables. It is recommended that this command be used to refresh controller names.

Syntax

F emcscf,DEV,RESCAN

ParametersNone.

ExampleF EMCSCF,DEV,RESCANSCF0341I DEV,RESCAN SCF0342I DEVICE RESCAN COMMAND ACCEPTED. SCF0413I RESCAN COMPLETE.

DEV,STATUS

Shows where SCF is situated in the discovery process by displaying information about devices that have already been processed.

Note: Only use this command when requested by EMC Customer Support. It is intended for debugging purposes to determine the status of the discovery operation.

Syntax

F emcscf,DEV,STATUS

ParametersNone.

ExampleF EMCSCF,DEV,STATUS SCF0341I DEV,STATUS SCF0071I REFRESH/RESCAN STARTED AT 1431 GMT - TIMER POPPED AT 1430 GMT 614 GOOD CCUU, UCB@ 000050CD 0237A170| UCBS 00003E0D NTO FAIL 00000B7F BAD CCUU, UCB@ 00004AFF 023534A0| EXC CCUU, UCB@ 00004EFF 0236CE30 TMEOUT CCUU,UCB@ 00000000 00000000| CURR CCUU, UCB@ 000050CE 0237A1F8 TIMEOUT COUNT 00000000 |DEVS ADDED 0000285B SCF0356I DEVICE Status of Discovery COMMAND COMPLETED.


Command Reference

Note: After discovery, these numbers will remain static until a new device refresh/rescan is started.

The fields in the above example have the following meaning:

◆ GOOD CCUU,UCB@

The CCUU and the UCB address of the last device that passed validation.

◆ UCBS

The count of UCBS processed.

◆ NTO FAIL

The count of devices that failed validation checks for a reason other than a timeout.

◆ BAD CCUU,UCB@

The last device that failed a validation check.

◆ EXC CCUU,UCB@

The last device processed that was explicitly excluded from SCF processing.

◆ TMEOUT CCUU,UCB@

The last device that failed validation because I/O to the device received a timeout result.

◆ CURR CCUU,UCB@

The device SCFDEVIC was processing when the STATUS request was made.

◆ TIMEOUT COUNT

The count of devices that received a timeout result during discovery.

◆ DEVS ADDED

The count of devices that passed validation and were added to the SCF device cache.

DEV,UNPIN

With V7.2 or higher, ResourcePak Base (SCF) honors dynamic activation of IODF configuration statements. SCF no longer needs to be stopped and restarted to capture the newly added or deleted devices.

DEV,UNPIN allows you to unpin the gatekeeper devices so an IODF ACTIVATE can be performed without stopping SCF or forcing you to choose another gatekeeper. After SCF issues this command, message SCF0434I is returned to indicate that the device is no longer pinned.

Once any devices in the list to be deleted by the IODF ACTIVATE command are unpinned, the IODF ACTIVATE can be reattempted. Once successful, a full rediscovery of the devices known to the SCF is done and all control blocks are rebuilt. All gatekeepers are verified and/or reassigned to a new device.

Syntax

F emcscf,DEV,UNPIN,options

Device commands 173

Command Reference



Specifies a DASD controller. The value can be either the full 12-digit Symmetrix serial number or just the last 5 digits of the number. (Use the 12-digit ID when multiple controllers use the same last 5 digits.)


ExampleF SCFJOBID, DEV,UNPIN,CNTRL(000192600291)


Command Reference

zBoost PAV Optimizer commands

Syntax conventions

Refer to “Command syntax and conventions” on page 144.

In all zBoost PAV Optimizer commands:

◆ The “DEV,OPTIMIZE” keyword can be spelled as “DEV,PAVO”. For example, you can type “DEV,PAVO ENABLE” instead of “DEV,OPTIMIZE ENABLE.”

◆ emcscf is the name of the SCF started task.

DEV,OPTIMIZE ENABLE

Enables zBoost PAV Optimizer.

Syntax

F emcscf,DEV,OPTIMIZE ENABLE

DEV,OPTIMIZE DISABLE

Disables zBoost PAV Optimizer.

Syntax

F emcscf,DEV,OPTIMIZE DISABLE

DEV,OPTIMIZE DISPLAY CONSISTENCY

Displays global consistency status.

Syntax

F emcscf,DEV,OPTIMIZE Display CONSISTENCY

ExampleF emcscf,DEV,OPTIMIZE DISPLAY CONSISTENCY

SCF4303I DEV,OPTIMIZE DISPLAY CONSISTENCY SCF4375I OPTIMIZE DISPLAY CONSISTENCY: 590 PAV Optimizer processing is currently resumed at 07/16/15 14:02:07 Type Status Suspend Last Suspend Last Resume Counter DD/MM/YY HH:MM:SS DD/MM/YY HH:MM:SS-------- --------- ------- ----------------- -----------------ConGroup Resumed 0 07/16/15 14:01:16 07/16/15 14:01:21MSC Resumed 0 07/16/15 14:02:07 07/16/15 14:02:07ECATF Resumed 0 07/16/15 13:29:50 07/16/15 13:30:50Operator Resumed 0 07/16/15 13:34:41 07/16/15 13:41:24ECASnap Resumed 0 07/16/15 13:30:50 07/16/15 13:31:10SCF0356I DEVICE Optimization COMMAND COMPLETED.

zBoost PAV Optimizer commands 175

Command Reference

DEV,OPTIMIZE DISPLAY DEVICE

Displays device-oriented zBoost PAV Optimizer statistics.

Syntax

F emcscf,DEV,OPTIMIZE Display DEVICE(cuu[-cuu])|ALLSUMMARY|EVENTSFILTer [OPTimized|SKIPped]

Parameters

cuu[-cuu]|ALL

Displays statistics for a single device or a range of devices specified with the CUU(s). ALL displays statistics for all devices.

FILTer [OPTimized|SKIPped]

Limits the devices displayed to only those which have had optimized I/O (OPTimized) or for which optimization has been skipped (SKIPped).

SUMMARY|EVENTS

Determines the type of statistics to be displayed:

• SUMMARY — (Default) Displays observed counts for the device(s).

• EVENTS — Displays the current event counts for each device.

ExampleExample 1 F emcscf,DEV,OPTIMIZE DISPLAY DEVICE 5218-5219

SCF4303I DEV ,PAVO DIS DEV 5218-5219 SCF4373I OPTIMIZE DISPLAY DEVICE SUMMARY: Unit SSID Type Optimized Skipped Track Split Min Max Min Max ---- ---- -------------- --------- --------- ----- ----- ----- ----- 5218 5101 Read PAVO 2079 0 4 9 4 8 Write PAVO 359233 9097 50 50 16 16 Write SUSPEND --------- 27672 ----- ----- ----- ----- Constituent IO 5760208 0 ----- ----- ----- ----- 5219 5101 Read PAVO 0 0 0 0 0 0 Write PAVO 677 1238 2 8 2 8 Write SUSPEND --------- 1908 ----- ----- ----- ----- Constituent IO 2554 0 ----- ----- ----- ----- Devices processed : 2 SCF0356I DEVICE Optimization COMMAND COMPLETED.

Example 2 F emcscf,DEV,OPTIMIZE DISPLAY DEVICE (4D00-4D02) EVENTS

SCF4303I DEV,OPTIMIZE DISPLAY DEVICE (4D00-4D07) EVENTSSCF4373I OPTIMIZE DISPLAY DEVICE EVENTS: Unit SSID Event Type Count ---- ---- ------------------- --------- 4D00 4D03 Read Logged 10 Read 22 4D01 4D03 Read Logged 10 Read 8 4D02 4D03 Read Logged 10


Command Reference

Example 3 F emcscf,DEV,DIS DEV ALL FILT

SCF4373I OPTIMIZE DISPLAY DEVICE SUMMARY: Unit SSID Type Optimized Skipped Track Split Min Max Min Max ---- ---- -------------- --------- --------- ----- ----- ----- ----- 5218 5101 Read PAVO 0 0 0 0 0 0 Write PAVO 20000 0 50 50 16 16 Write Suspend --------- 1234 ----- ----- ----- ----- Constituent IO 320000 0 ----- ----- ----- ----- Devices processed : 1

DEV,OPTIMIZE DISPLAY EVENTS

Displays non-zero event counters.

Syntax

F emcscf,DEV,OPTIMIZE Display EVENTS

ExampleF emcscf,DEV,OPTIMIZE DISPLAY EVENTS

SCF4303I DEV,OPTIMIZE DISPLAY EVENTS SCF4372I OPTIMIZE DISPLAY GLOBAL EVENTS: Event Type Count ------------------- --------- Non-specific Logged 0 Non-specific 0 Read Logged 845 Read 505107 Write Logged 0 Write 0 Build Error Logged 0 I/O Error Logged 34


Command Reference

DEV,OPTIMIZE DISPLAY SSID

Displays SSID-oriented zBoost PAV Optimizer statistics.

Syntax

F emcscf,DEV,OPTIMIZE Display SSID(ssid[-ssid])|ALLSUMMARY|EVENTS

Parameters

ssid[-ssid]|ALL

Displays statistics for a single SSID or a range of SSIDs. ALL displays statistics for all SSIDs.

SUMMARY|EVENTS

Determines the type of statistics to be displayed:

• SUMMARY — (Default) Displays observed counts for the SSID(s).

• EVENTS — Displays the current event counts for each SSID.

ExampleExample 1 F emcscf,DEV,OPTIMIZE DISPLAY SSID ALL

SCF4303I DEV,OPTIMIZE DISPLAY SSID ALL SCF4374I OPTIMIZE DISPLAY SSID SUMMARY: +-----------------------------------+ | PAV Base/Alias usage |---------------------------------+-------------------------+---------+ SSID Controller Devs Alias | Constituent I/O |PerIO Max| HPAV Qpt| Total Collision |Uniq Dup | ---- ------------- ---- ---- ---+------------ ------------+---- ----+ 5100 0001949-01172 1 0 ---| 0 0|---- 0|**ALIAS not configured | 0 0| 0 0| 5101 0001949-01172 14 0 ---| 2884875 2|---- 2| | 4802227 0| 2 0| 8F00 0001926-04059 64 0 ---| 0 0|---- 0| | 0 0| 0 0| BBBC 0001903-00353 64 0 ---| 0 0|---- 0| | 0 0| 0 0|SSIDs processed : 4

Example 2 F emcscf,DEV,OPTIMIZE DISPLAY SSID ALL EVENTS

SCF4303I DEV,OPTIMIZE DISPLAY SSID ALL EVENTS SCF4374I OPTIMIZE DISPLAY SSID EVENTS: SSID Event Type Count ---- ------------------- --------- 4D03 Read Logged 519 Read 381673 I/O Error Logged 20 4E03 Read Logged 326 Read 123434 I/O Error Logged 14 SSIDs processed : 2


Command Reference

DEV,OPTIMIZE DISPLAY SUMMARY

Displays zBoost PAV Optimizer configuration parameters.

Syntax

F emcscf,DEV,OPTIMIZE Display SUMMARY

ExampleF emcscf,DEV,OPTIMIZE DISPLAY SUMMARY

SCF4372I OPTIMIZE DISPLAY GLOBAL SUMMARY: SMF recording is ON, record ID is 203 Last SMF interval was on 08/27/15 at 10:30:00 PAV Optimization is ON PAV Optimization parameters in effect ------------------------------------- SCF.DEV.OPTIMIZE.VERBOSE=NO SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL=1000 SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE=0 SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU=0 SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT=80 SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ=0 SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE=0 SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ=8 SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE=2 xxxxSCF.DEV.OPTIMIZE.PAV.JOBNAME list: Jobname Match count -------- ------------ IMCKAY1C 0 PALIOPL 959974 PALIOPL2 960865 SCF.DEV.OPTIMIZE.PAV.JOBPREFIX list: Jobname Match count -------- ------------ BBBBBBB 0 I 0 PAL 2189113 PL 0

DEV,OPTIMIZE LOG EVENTS

Indicates to zBoost PAV Optimizer which event numbers should be logged.

Note: Use this command under the direction of EMC support personnel only.

Syntax

F emcscf,DEV,OPTIMIZE LOG EVENTSNONE|event#[-event#][ON|OFF]

Parameters

event#[-event#]

Specifies the single event or range of events to be affected by the command.

NONE

Turns off zBoost PAV Optimizer event logging.


Command Reference

ON|OFF

Enables or disables logging of the specified event or events.

ExampleTo make zBoost PAV Optimizer log event number 43:

F emcscf,DEV,OPTIMIZE LOG EVENTS 43 ON

DEV,OPTIMIZE RESET

Resets all or selected zBoost PAV Optimizer statistics counters.

Note: During the RESET processing, optimization is temporarily quiesced which could take up to 25 seconds to complete (depending on I/O activity). If there is still active I/O after the 25 seconds, the RESET command will fail and optimization will be allowed to continue unless the FORCE option is specified.

Syntax

F emcscf,DEV,OPTIMIZE RESETFULL|EVENTS|JOBNAMELIST[FORCE]

Parameters

EVENTS

Resets event counters.

FORCE

Forces a reset regardless of whether or not there is active I/O.

FULL

(Default) Resets all counters.

Note: The DEV,PAVO RESET FULL command also causes zBoost PAV Optimizer SMF records to be written immediately before the statistics are reset.

JOBNAMELIST

Resets jobname counters.

ExampleF emcscf,DEV,OPTIMIZE RESET FULL

DEV,OPTIMIZE RESUME

Resumes zBoost PAV Optimizer write processing if there are no other (non-operator) consistency suspends outstanding.

Syntax

F emcscf,DEV,OPTIMIZE RESUME


Command Reference

ExampleF emcscf,DEV,OPTIMIZE RESUME

SCF4381I OPTIMIZE RESUME: RESUME initiated through 5 controllers PAV Optimizer processing is currently resumed at 08/27/15 13:40:32 Type Status Suspend Last Suspend Last Resume Counter DD/MM/YY HH:MM:SS DD/MM/YY HH:MM:SS-------- --------- ------- ----------------- -----------------ConGroup Resumed 0 08/26/15 17:31:48 08/26/15 17:31:58MSC Resumed 0 08/25/15 17:30:21 08/25/15 17:30:21ECA Resumed 0 08/27/15 12:40:02 08/27/15 12:40:03Operator Resumed 0 08/27/15 13:32:51 08/27/15 13:40:32

DEV,OPTIMIZE SUSPEND

Suspends zBoost PAV Optimizer write processing.

The SUSPEND command affects every currently active zBoost PAV Optimizer across all LPARs with connectivity to the same Symmetrix systems. zBoost PAV Optimizer will not optimize write-oriented channel programs until a corresponding RESUME command is issued.

Note: The SUSPEND command only affects active EMCSCF. If an EMCSCF is started after this SUSPEND command is issued, then another SUSPEND command will be required to suspend its write processing.

Syntax

F emcscf,DEV,OPTIMIZE SUSPEND

ExampleF emcscf,DEV,OPTIMIZE SUSPEND

SCF4380I OPTIMIZE SUSPEND: SUSPEND initiated through 5 controllers PAV Optimizer processing is currently suspended at 08/27/15 13:31:00 Suspend window is set to never expire Type Status Suspend Last Suspend Last Resume Counter DD/MM/YY HH:MM:SS DD/MM/YY HH:MM:SS -------- --------- ------- ----------------- ----------------- ConGroup Resumed 0 08/26/15 17:31:48 08/26/15 17:31:58 MSC Resumed 0 08/25/15 17:30:21 08/25/15 17:30:21 ECA Resumed 0 08/27/15 12:40:02 08/27/15 12:40:03 Operator Suspended 1 08/27/15 13:31:00 08/26/15 17:32:17


Command Reference

Group Name Services commandsThe GNS commands allow you to perform the following tasks:

◆ Display the contents of the scratch area

◆ Force a communications scratch area to be GNS-compatible

◆ Display the names of all groups defined on all the Symmetrix systems known to this SCF

◆ Refresh the contents of the internal in-memory GNS tables

◆ Revert the specified communications scratch area from a GNS-compatible state to an earlier, non GNS-compatible state

GNS,FORMAT

Forces the communications scratch area to be GNS-compatible. This command eradicates all group information on the controller.

Syntax

F emcscf,GNS,FORMAT,SER#,nnnnnnnnnnnn

Parameters

SER#,nnnnnnnnnnnn

Valid Symmetrix 12-digit number.

ExampleF EMCSCF,GNS,FORMAT,SER#,000190103115 SCF0321I GNS,FORMAT,SER#,000190103115 SCF0878I GNS COMMAND accepted. SCF0890I FORMAT OF 000190103115 WAS SUCCESSFUL.

GNS,LIST

Displays the names of the groups defined on the Symmetrix systems known to this SCF.

Syntax

F emcscf,GNS,LIST{[,SER#,nnnnnnnnnnnn]|[,GROUP,gggggggggg]}

Parameters

SER#,nnnnnnnnnnnn


GROUP,gggggggggg

Valid GNS group name less than or equal to 65 characters.


Command Reference

ExamplesExample 1 The following example the names of all groups defined on all Symmetrix systems known to

this SCF.

F EMCSCF,GNS,LIST SCF0321I GNS,LIST SCF0878I GNS COMMAND accepted. SCF0890I ******** BEGIN GNS GROUP DISPLAY ********* SCF0890I GNS GROUPS ON CTLR# 000000006140 FOLLOW SCF0890I "DC1_CKD_RGRP_02_JA" SCF0890I "DC1_CKD_RGRP_09_J0" SCF0890I "EDP_U6J_GK" SCF0890I "EDP_U6J_RA2A" SCF0890I "EDP_U6J_RA2B" SCF0890I "EDP_U6J_RA2C" SCF0890I GNS GROUPS ON CTLR# 000000006185 FOLLOW SCF0890I "AMSYNC_U6A1" SCF0890I "AMU6A1G" SCF0890I "LRGRP08" SCF0890I "MSFARGK" SCF0890I ******** END OF GNS DISPLAY *********

Example 2 The following example displays the names of all groups defined on the specified Symmetrix system known to this SCF.

GNS,LIST,SER#=000192600262 GNS COMMAND accepted. ******** BEGIN GNS GROUP DISPLAY *********GNS GROUPS ON CTLR# 000192600262 FOLLOW "BSTEST1" "CRBSCF" "MPASCFG" "MSFUTB10" "MSFUTB80" "MSFUTB81" "MSFUTB90" "MSFUTBC0" ******** END OF GNS DISPLAY *********

Example 3 The following example displays all Symmetrix systems known to this SCF that contain the specified GNS group.

GNS,LIST,GROUP=MENOTU GNS COMMAND accepted. ******** BEGIN GNS GROUP DISPLAY ********* GNS GROUPS ON REMOTE CTLR# 000192600291 FOLLOW"MENOTU" GNS GROUPS ON REMOTE CTLR# 000192600296 FOLLOW"MENOTU" ******** END OF GNS DISPLAY *********

Group Name Services commands 183

Command Reference

GNS,REFRESH

Refreshes the contents of the internal in-memory GNS tables and rebuilds the remote controller list.

Note: A GNS,REFRESH should be done immediately after a DEV,REFRESH has completed.

Syntax

F emcscf,GNS,REFRESH

ParametersNone.

ExampleF EMCSCF,GNS,REFRESHSCF0321I GNS,REFRESH SCF0878I GNS COMMAND accepted. SCF0890I GNS, Refresh request has completed.

GNS,REVERT

Reverts the specified communications scratch area from a GNS-compatible state to an earlier non-GNS-compatible state.

Syntax

F emcscf,GNS,REVERT,SER#,nnnnnnnnnnnn

Parameters

SER#,nnnnnnnnnnnn


ExampleF EMCSCF,GNS,REVERT,SER#,000190103115 SCF0321I GNS,REVERT,SER#,000190103115 SCF0878I GNS COMMAND accepted. SCF0890I 000190103115 HAS BEEN REVERTED SUCCESSFULLY.


Command Reference

General Pool Management commandsGPM commands for VP pool and device management can be executed in either online or batch mode, as follows:

◆ In batch mode, GPM commands can be executed by the program ESFGPMBT. Refer to “Running GPM in batch mode” on page 392 for more information.

◆ For online mode, you can:

– Use the z/OS MODIFY command. The syntax is:

F <scfjobname>,GPM,<action><parameters>

– Or, take advantage of the Command Prefix Facility (CPF) for SCF where you can enter SCF commands using CPF rather than using the MODIFY command. For example, if the CPF name is @123, then the command:

F scf,GPM,ADD LCL(UNIT(3800) DEV(28E) POOL (EMCCKDVP)

can be entered as:

@123 GPM,ADD LCL(UNIT(3800) DEV(28E) POOL (EMCCKDVP)

Refer to Chapter 3, “Configuration File and Initialization Parameters,” for more information on the SCF.INI.CPFX initialization parameter and ResourcePak Base configuration file.

◆ You can use the DEBUG keyword to generate command-level diagnostic information that does not affect the outcome of the command. This diagnostic information is written to module-specific DDs DBUGPMBT, DBUGPMCM, and DBUGPMSD. To avoid unnecessary overhead, specify this option only when requested by technical support and only on the commands for which diagnostics are requested.

To generate diagnostics for select commands only, specify the DEBUG keyword on the selected commands, and do not specify PARM=DEBUG on the batch JCL EXEC statement.

For examples Note: For examples of GPM commands and displays, refer to “GPM command examples” on page 397.

Note: Many GPM commands are executed on the Symmetrix system as background tasks, and may continue to run when control is returned after issuing the command. Use the QUERY TASKS command to view active tasks.

GPM pool commands

GPM pool-oriented commands include:

“CREATE” on page 206 Create a thin, DSE or snap pool.

“DELETE” on page 214 Delete an empty pool.

“DISPLAY” on page 220 Display pool information.

“POOLATTR” on page 253 Specify pool-level attributes.

“REBALANCE” on page 285 Initiate leveling allocated tracks within a pool.

“RENAME” on page 296 Change the name of a pool.

General Pool Management commands 185

Command Reference

GPM device commandsGPM device-oriented commands include:

GPM command examplesIn addition to some of the examples provided in this section, refer to “GPM command examples” on page 397 for a full description of all the steps required to create a VP in a Symmetrix system and to manage pool usage.

“ADD” on page 188 Add one or more back-end devices to a pool.

“ALLOCATE” on page 192 Allocate tracks to prepare thin device(s) in a pool.

“BIND” on page 196 Bind one or more thin devices to a thin pool.

“COMPRESS” on page 201 Compress data for one or more thin devices.

“DECOMPRESS” on page 210 Decompress data for one or more thin devices.

“DISABLE” on page 216 Change the status of one or more pool devices from active to inactive.

“DRAIN” on page 229 Initiate reassignment of allocated tracks to other devices within the pool.

“ENABLE” on page 233 Change the status of one or more devices from inactive to active.

“HALTTASK” on page 236 Halt background task for thin devices.

“HDRAIN” on page 240 Halt draining activity of devices.

“MOVE” on page 244 Move allocations for thin device(s) to the pool where they are currently bound.

“PERSIST OFF” on page 249 Turn off persistence for all tracks allocated for the specified thin device or devices.

“QUERY {parameter}” on page 259 Display information about device entities.

“REBIND” on page 289 Change the pool to which a thin device is bound.

“REMOVE” on page 293 Remove an inactive device from a pool.

“UNBIND” on page 299 Unbind one or more thin devices from a pool.

“USR_NRDY” on page 303 Change device’s control unit status to user-not-ready.

“USR_RDY” on page 306 Change device’s control unit status to user-ready.


Command Reference

GPM online helpIn addition to the descriptions of the commands in this manual, you can generate a help list of available GPM commands:

General command help F <scfjobname>,GPM,HELPAvailable GPM actions:ADD - Add data or save devices to a poolALLOCATE - Allocate tracks to prepare thin device(s) in a pool.BIND - Associate a thin device with a poolCREATE - Create a new device poolCOMPRESS - Compress data on one or more thin devicesDECOMPRESS - Decompress data on one or more thin devicesDELETE - Delete a device poolDISABLE - Set pool devices unavailable for new allocationsDISPLAY - List pools or pool devicesDRAIN - Reassign allocated tracks to other pool devicesENABLE - Set pool devices available for new allocationsHALTTASK - Stop background task for thin devicesHDRAIN - Halt a DRAIN operation that is in progressMOVE - Move thin device allocations between poolsPERSIST OFF - Reset persistent attribute for all tracks allocated for

0the specified thin devicesPOOLATTR 0 - Set pool attributes such as alert thresholds QUERY - Display pool-related information about devicesREBALANCE - Initiate leveling for a set of pool devicesREBIND - Bind devices to a pool, keep existing allocationsREMOVE - Remove unallocated, inactive devices from a poolRENAME - Change the name of a device poolUNBIND - Disassociate a thin device from a device poolUSR_NRDY - Change device control unit status to user-not-readyUSR_RDY - Change device control unit status to user-ready

For help for any of the above actions, enter: Specific command help F <scfjobnm>,GPM,HELP <action>

GPM command complete


Command Reference

ADDDescription

ADD assigns one or more back-end (data or save) devices to a pool. The device(s) may be set as active and immediately available for track allocation, or may be left as inactive and remain unavailable for track allocation until changed to active by an ENABLE action.

A device to be added to a pool must be compatible with the pool type and with any devices already in the pool. Compatibility requirements include:

◆ A device to be added to a thin pool must be a data device.

◆ A device to be added to a DSE or snap pool must be a save device.

◆ When a device is added to a pool that already contains one or more devices, the new device must have the same emulation and protection type as the device(s) already in the pool. Additionally, a device added to a thin pool on a Symmetrix system at Enginuity level 5875 or higher must have the same storage class and speed as the device(s) already in the pool.

A device that is already assigned to a pool may be assigned to a different pool by means of the ADD action only when:

◆ The device is inactive.

◆ No tracks are already allocated on the device.

ADD will fail completely when:

◆ The specified pool cannot be found.

◆ A valid pool name is not supplied (via the POOL parameter).

◆ A valid gatekeeper is not supplied (via the LOCAL or REMOTE parameter).

◆ A valid device or range of devices is not supplied (via the DEV parameter).

◆ The specified pool is empty and devices in the specified device range have conflicting emulation.

◆ ADD validation fails for a device and SKIP has not been specified.

ADD will fail for a device when:

◆ The device belongs to another pool and has allocated tracks.

◆ The device belongs to another pool and is active.

◆ The target pool characteristics do not match the device characteristics.


Command Reference

SyntaxADD {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)

PATH(xx.xx.xx.xx)[CONTROLLER([xxxxxxx-]xxxxx)])

POOL(poolname)DEV(device|range|list)[ACTIVE][SKIP][NOEXEC][DEBUG][VERBOSE]

Parameters

{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))

Identifies a gatekeeper in the local Symmetrix that allows access to devices in that local Symmetrix system. Values can be:

Note: One of the following must be present: UNIT, VOLume, or DDNAME. UNIT and VOLume can be specified together, or DDNAME may be used instead.

{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname) PATH(xx.xx.xx.xx) [CONTROLLER([xxxxxxx-]xxxxx)])

Identifies a gatekeeper in the local Symmetrix unit that allows access to devices in a remote Symmetrix unit. Values can be:

UNIT Specifies the unit address of the gatekeeper.

VOLume Specifies the volser of the gatekeeper.

DDNAME Identifies the DD statement that refers to the gatekeeper.




PATH Specifies the path to reach the Symmetrix system where the devices to be added to the pool reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.

Note: PATH is known as a 'hop list' in Host Component commands.

CONTROLLER Optional. Verifies that the correct Symmetrix is reached through the SRDF group path. Either a 5-digit (xxxxx) or a 12-digit (xxxxxxx-xxxxx) serial number may be specified. (Use the 12-digit ID when multiple controllers use the same last 5 digits.)



Command Reference


POOL(poolname)

This required parameter specifies the pool to which the specified devices are to be added.

Poolname can be up to 12 characters long. The name may include uppercase alphabetic characters, numbers, spaces, underscores (_), and hyphens (-). The first and last characters may not be underscores or hyphens. If the name includes any hyphens or spaces you must enclose the name in apostrophes.

DEV(device|range|list)This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be added to the specified pool.

[ACTIVE]This optional parameter sets the state of devices being added to the pool as eligible to be assigned allocated tracks. If not specified, the devices being added to the pool are initially inactive (ineligible to be assigned allocated tracks). Devices ineligible for allocations may be made eligible for allocations by means of the ENABLE action.

[SKIP]This optional parameter allows ineligible devices to be skipped rather than terminating the action. If a pool is empty, however, and the range of devices to be added to the pool includes devices that may not be in the same pool due to any of the compatibility requirements, SKIP is ignored and no devices are added to the pool.

[NOEXEC]

This optional parameter causes syntax checking to be performed without the actual execution of the command. The command only checks for proper syntax. If the syntax is correct, the command completes successfully. If a syntax error is found, the command fails.

Note: Adding NOEXEC to a command means the command is not executed. The command only checks for proper syntax.

[DEBUG]

This optional parameter generates command-level diagnostic information that does not affect the outcome of the command. This diagnostic information is written to the module-specific DDs DBUGPMBT, DBUGPMCM, DBUGPMSD, and DBUGPMSS. To avoid unnecessary overhead, specify this option only when requested by EMC technical support and only on the commands for which diagnostics are requested.

Note: To generate diagnostics for select commands only, use this parameter, and do not specify PARM=DEBUG on the batch JCL EXEC statement.


Command Reference

[VERBOSE]

This optional parameter enables verbose messaging. These messages typically indicate the status of the requested operation for the requested devices or pool. These additional messages are written to the GPMPRINT DD in batch mode or to the SCF log in online mode.

Note: This parameter does not affect the outcome of the command.


Command Reference

ALLOCATEALLOCATE causes physical (data device) tracks to be allocated to back all logical (thin device) tracks for each thin device specified. Without using ALLOCATE, physical tracks are allocated on data devices only when data is written to the thin device.

ALLOCATE will fail completely when:





◆ The specified pool is not a thin pool.

◆ The specified pool is the default pool.

◆ ALLOCATE validation fails for a device and SKIP has not been specified.

◆ A number of unallocated data devices are in the thin pool and the user attempts to allocate the same number of thin devices bound to the pool. The thin devices should be the same size due to the meta data required for the thin data devices mappings.

ALLOCATE will fail for a device when:

◆ The device is not a thin device.

◆ The specified pool does not have available tracks to allocate for the new device. (Expect 1% to 3% of overhead for thin device meta data.)

◆ The specified pool does not have any devices assigned and active.

◆ The device is an FBA Meta member whose head device is not in the specified device range.

SyntaxALLOCATE {LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[PERSIST][SKIP][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]

Parameter







Command Reference





POOL(poolname)

This required parameter specifies the name of the pool in which the tracks for the specified thin device(s) are to be allocated.

DEV(device|range|list)

This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be allocated.

[PERSIST]

This optional parameter indicates that allocated tracks are assigned the persistent attribute. Allocated tracks having the persistent attribute are not freed until the thin device they are backing has been unbound from the pool containing the data device on which the tracks are allocated.

[SKIP]

This optional parameter may be specified to allow ineligible devices to be skipped rather than terminating the action.




PATH Specifies the path to reach the Symmetrix system where the pool device is to be allocated. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[NOEXEC]



[DEBUG]



[WAIT(value,WARN|ERROR)]

This optional parameter will attempt to wait until all Symmetrix tasks associated with the command are complete before returning control to the batch job (in batch mode) or user (in online mode).

Adding the WAIT parameter to a command does not guarantee that all associated Symmetrix tasks are complete when the command finishes. It is possible that a particular task may take longer than the maximum wait time to complete, at which time a warning or error message indicating that the task is still running is displayed, depending on whether WARN or ERROR (or neither) is specified. If this occurs, you should verify the completion of the task(s) using the appropriate QUERY command.

• For thin device status, use QUERY THINDEV.

• For data device status, use QUERY DATADEV.

• For save device status, use QUERY SAVEDEV.

• For pool status, use QUERY POOLS (the resulting report is equivalent to DISPLAY with no explicit pool name).

The WAIT parameter takes two optional sub-parameters. One, both, or neither sub-parameter may be specified. A numeric value between 0 and 1440 minutes (one day) may be specified to override the maximum wait time. The default value is 100 minutes.

Additionally, the WARN or ERROR keyword may be specified.

WARN indicates that a warning message should be displayed, and the command should end with RC = 4, if one or more tasks takes longer than the maximum wait time to complete.

ERROR indicates that an error message should be displayed, and the command should end with RC = 8, if one or more tasks takes longer than the maximum wait time to complete. In either case, if this occurs, the user should verify completion of


Command Reference

the task(s) using one of the QUERY commands described above. If neither WARN nor ERROR is specified and an explicit wait value is specified, the default will be FAIL.

If neither WARN nor ERROR is specified and no explicit wait value is specified, the default will be WARN.

[VERBOSE]




Command Reference

BIND

DescriptionBIND establishes a relationship between one or more thin devices to a thin pool. The host’s “apparent writes” to the thin device results in “actual writes” to one or more data devices in the thin pool. This arrangement known as thin provisioning.

The tracks to which the data is actually written are known as allocated tracks.

BIND will fail completely when:







◆ BIND validation fails for a device and SKIP has not been specified.

BIND will fail for a device when:


◆ The device's emulation mode does not match the pool emulation mode.

◆ The specified pool does not have available tracks to allocate for the new device.

◆ The specified pool does not have any data devices assigned and active.


◆ Binding that device would cause the oversubscription rate (for Enginuity levels 5874 and higher) of the pool to exceed the maximum oversubscription rate of the pool set the by the user.

Oversubscription rate applies to thin pools only. The actual oversubscription rate (ActO) and maximum oversubscription rate (MaxO) is shown for each thin pool on the pool list DISPLAY report. Oversubscription rate is the ratio of bound thin device tracks to active data device tracks for a thin pool. It is calculated by dividing the total number of tracks on thin devices bound to the pool by the total number of tracks on active data devices in the pool, as follows:

Oversubscription rate = total tracks on bound thin devices ÷ total tracks on active data devices

An oversubscription rate less than 1 means the number of bound thin device tracks is less than the number of active data device tracks. In other words, the pool is “under-subscribed”. This is the safest situation because given its current state the pool cannot reach 100% used.


Command Reference

An oversubscription rate of 1 means the number of bound thin device tracks and active data device tracks for the pool are equal. In other words, the pool is “fully subscribed” or “fully provisioned”. If all thin devices bound to the pool are filled to their capacity, the pool is 100% used.

An oversubscription rate greater than 1 means the number of bound thin device tracks is greater than the number of active data device tracks for the pool. In other words, the pool is “over-subscribed”. The percent used for the pool must be carefully monitored. As the pool fills up, more data devices may need to be added to the pool and enabled so the pool does not reach 100% used. For an over-subscribed thin pool, even if the thin devices bound to the pool are not filled to their capacity, it is possible that the pool itself could reach 100% used.

Note: Actual oversubscription rate (ActO) and maximum oversubscription rate (MaxO) are ratios and are shown as whole numbers, not percentages. For the actual oversubscription rate, some rounding may occur.

SyntaxBIND {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[PREALLOC][PERSIST][SKIP][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]

Parameters





Identifies a gatekeeper in the local Symmetrix unit that allows access to devices in a remote Symmetrix unit.





Command Reference

Values can be:


POOL(poolname)

This required parameter specifies the pool to which the specified devices are to be bound.


This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be bound to the specified pool.

[PREALLOC]

This optional parameter indicates that physical (data device) tracks are to be allocated at the time the bind is performed to back all logical (thin device) tracks on each device being bound. If this parameter is not specified, physical tracks are allocated on data devices only when data is written to the thin device.

[PERSIST]

This optional parameter indicates that allocated tracks are to be assigned the persistent attribute. Allocated tracks having the persistent attribute are not freed until the thin device they are backing has been unbound from the pool of the data device on which the tracks are allocated.

This parameter is valid only if PREALLOC is specified.

[SKIP]

This optional parameter allows ineligible devices to be skipped rather than terminating the action.




PATH Specifies the path to reach the Symmetrix system where the devices to be bound to the pool reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[NOEXEC]



[DEBUG]













ERROR indicates that an error message should be displayed, and the command should end with RC = 8, if one or more tasks takes longer than the maximum wait time to complete. In either case, if this occurs, the user should verify completion of


Command Reference

the task(s) using one of the QUERY commands described above. If neither WARN nor ERROR is specified and an explicit wait value is specified, the default will be FAIL.


[VERBOSE]




Command Reference

COMPRESS

DescriptionCOMPRESS is used to compress the data in one or more thin devices. This command requires MFE version 7.5 along with Enginuity level 5876.

Compression is disabled by default. You must first enable compression for the pool and only then can you actually compress a thin device in the pool.

Before thin devices bound to a pool can be compressed, you need to:

1. Issue the POOLATTR command with the COMPRESSION(ENABLE) parameter.

2. Issue the COMPRESS command.

Compression is a background task that precludes other background tasks from running (such as reclaim or allocation)

Note: Compression is not supported for devices bound with the PERSIST attribute.

When compressing a device, only allocations that have been written are compressed. Any allocations that were created during the bind or allocate processing that have not been written are reclaimed during the compression process, meaning these allocations will no longer exist. After decompression, the allocated tracks will not match the original allocated track count for the thin device.

Note: The zero reclaim that runs as part of the compression process will deallocate standard record-zero tracks but will not scratch deleted datasets that do not yet contain standard record-zero tracks. To reclaim these tracks and avoid compressing deleted datasets, the Thin Reclaim Utility (TRU) should run against a thin device before compressing that device. Only TRU scratches deleted datasets, so TRU must be run for space reclamation.

The fact that unwritten allocations can be reclaimed imposes a restriction that persistent allocations cannot be compressed, since they are not allowed to be reclaimed automatically. Any allocations that are not written are reclaimed during compression if the tracks are not marked persistent. By making the allocations persistent, the allocated tracks are maintained and no compression can occur. In order to compress a thin device that has persistent allocations, the persistent attribute must first be removed, allowing compression and reclamation to occur. Compression will not fail, but will have no effect, on thin devices if they are allocated and have the persistent attribute set.

Compression of allocations for a thin device is a background task. Once the compression request is accepted, the thin device will have a background task associated with it that performs the compression for that device. While this task is running, no other background task, like allocate or reclaim, can run against the thin device.

If a thin device containing allocations in multiple pools is compressed, all allocations are compressed in the pools where they reside. By default, no data is moved. Alternatively, the MOVE parameter can be used to move all allocations for the device to the pool where the device is currently bound to before compressing those allocations. If this option is used, all allocations for the device reside in the bound pool after compression is complete.


Command Reference

A thin device can be manually compressed at any time. Decompression happens if the user issues the DECOMPRESS command against the device, or when the data is written to the device. There is no automatic re-compression after a write.

Compress will FAIL completely when:







◆ Compression is not enabled for the specified pool.

◆ Validation for COMPRESS fails for a device and SKIP has not been specified.

Compress will FAIL for a device when:


◆ The device is not bound to the specified pool.

◆ The data devices that contain the allocated tracks are not active.

◆ The device is an FBA meta member whose head device is not in the specified device range.

Recommendations

EMC has the following recommendations for using compression:

◆ Since compression impacts performance, compression should be used against very idle data. EMC does not recommend running medium or greater workloads against it.

◆ Auto-compression (keeping volumes compressed) can only be obtained through the use of FAST.

◆ With the exception of an occasional backup to tape, EMC recommends fully decompressing data before accessing it.

◆ EMC suggests using manual compression (not FAST) for:

• Archiving old user accounts.

• Decompress-use-recompress end of quarter activity.

• For use with data-at-rest.

SyntaxCOMPRESS{LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)PATH(xx.xx.xx.xx)CONTROLLER(xxxxxxx[-xxxxx]))DEV(device|range|list)POOL(poolname)[MOVE][SKIP][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]


Command Reference

Parameters








This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be compressed.

POOL(poolname)

This required parameter specifies the pool where the devices are bound.












Command Reference

[MOVE]

By default, if a thin device containing allocations in multiple pools is compressed, all allocations are compressed in the pools where they reside. If this optional parameter is specified, all allocations for the device are moved to the pool where the device is currently bound to before compressing those allocations. If this option is used, all allocations for the device reside in the bound pool after compression is complete.

[SKIP]


[NOEXEC]



[DEBUG]











Command Reference




ERROR indicates that an error message should be displayed, and the command should end with RC = 8, if one or more tasks takes longer than the maximum wait time to complete. In either case, if this occurs, the user should verify completion of the task(s) using one of the QUERY commands described above. If neither WARN nor ERROR is specified and an explicit wait value is specified, the default will be FAIL.


[VERBOSE]




Command Reference

CREATE

DescriptionCREATE is used to create a new pool. The types SNAPPOOL, DSEPOOL and THINPOOL are supported.

The maximum number of pools that can be defined on a Symmetrix system is governed by the following limitations:

◆ On a Symmetrix system running Enginuity level 5x71, users can create up to 255 snap pools.

◆ On a Symmetrix system running Enginuity level 5772, users can create both SNAP and DSE pools. A total of 255 pools is allowed.

◆ On a Symmetrix system running Enginuity level 5773, users can create SNAP, DSE, and thin pools. The thin pools are limited to FBA devices. A total of 510 pools is allowed (a total combination of 255 SNAP and/or DSE pools, and 255 THINPOOLS).

◆ On a Symmetrix system running Enginuity level 5876, users can create SNAP, DSE, and THINPOOLS. Thin pools support both CKD and FBA devices but not in the same pool. A total of 510 user-defined pools is allowed on each Symmetrix system (a combination of all user-defined SNAP, DSE, and THINPOOLS).

CREATE will fail completely when:

◆ The specified pool name does not adhere to pool name requirements.

◆ A pool of the same name already exists on the Symmetrix system.



◆ A valid pool type is not supplied (via the TYPE parameter).

◆ The maximum number of pools already exists on the Symmetrix system.

◆ The request specifies TYPE(THINPOOL) and the maximum number of pools of type THINPOOL already exist on the Symmetrix system.

◆ The request specifies TYPE(SNAPPOOL) or TYPE(DSEPOOL) and the maximum number of pools of either type SNAPPOOL or type DSEPOOL already exist on the Symmetrix system.

Note: EMC suggests that the pool name does not contain embedded spaces, if the pool will be monitored using the THIN, SAVE, or DSE pool capacity monitor.


Command Reference

Syntax CREATE{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


POOL(poolname)TYPE(THINPOOL|DSEPOOL|SNAPPOOL)[{MAXOSUB|MAXO}(maximum_oversubscription_ratio)][NOEXEC][DEBUG][VERBOSE]

Parameters













PATH Specifies the path to reach the Symmetrix system where the pool is to be created. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

POOL(poolname)

This required parameter specifies the pool to be created.


TYPE(SNAPPOOL|DSEPOOL|THINPOOL)

This required parameter identifies the usage for the pool. This parameter is required. Valid values are SNAPPOOL, DSEPOOL, or THINPOOL.

[{MAXOSUB|MAXO}(maximum_oversubscription_ratio)]

This optional parameter specifies the maximum ratio of the host-apparent capacity of all thin devices bound to the pool to the physical capacity of all active data devices in the pool. Omit the MAXOSUB parameter to indicate that no maximum exists. This is the default setting.

MAXOSUB (maximum oversubscription rate (for Enginuity levels 5874 and higher)) is a ratio and is interpreted as a whole number, not a percentage.

The actual oversubscription rate (ActO) and maximum oversubscription rate (MaxO) is shown for each listed thin pool on the QUERY POOLS (or pool list DISPLAY) report.

Oversubscription rate is the ratio of bound thin device tracks to active data device tracks for a thin pool. It is calculated by dividing the total number of tracks on thin devices bound to the pool by the total number of tracks on active data devices in the pool, as follows:


An oversubscription rate less than 1 means the number of bound thin device tracks is less than the number of active data device tracks. In other words, the pool is "under-subscribed". This is the safest situation because given its current state the pool cannot reach 100% used.

An oversubscription rate of 1 means the number of bound thin device tracks and active data device tracks for the pool are equal. In other words, the pool is "fully subscribed" or "fully provisioned". If all thin devices bound to the pool are filled to their capacity, the pool is 100% used.

An oversubscription rate greater than 1 means the number of bound thin device tracks is greater than the number of active data device tracks for the pool. In other words, the pool is "over-subscribed". The percent used for the pool must be carefully monitored. As the pool fills up, more data devices may need to be added to the pool and enabled so the pool does not reach 100% used. For an over-subscribed thin pool, even if the thin devices bound to the pool are not filled to their capacity, it is possible that the pool itself could reach 100% used.

Note: This parameter is valid only for thin pools. Specifying a value can affect the result of the BIND, REBIND, MOVE (with REBIND option), DRAIN, or DISABLE commands. The range of possible values for MAXOSUB is 0 to 65,534. Omit the


Command Reference

MAXOSUB parameter to indicate that no maximum exists - this is the default. If MAXOSUB is set to zero, all BIND, REBIND, MOVE (with REBIND option), DRAIN, and DISABLE requests will fail.

[NOEXEC]



[DEBUG]



[VERBOSE]




Command Reference

DECOMPRESS

DescriptionDECOMPRESS is used to decompress the data in one or more thin devices.

If a thin device containing allocations in multiple pools is decompressed, all allocations are decompressed in the pools where they reside. By default, no data is moved. Alternatively, the MOVE parameter can be used to move all allocations for the device to the pool where the device is currently bound to before decompressing those allocations. If this option is used, all allocations for the device reside in the bound pool after decompression is complete.

Refer to “COMPRESS” on page 201 for more information on compression of thin devices.

Decompress will FAIL completely when:







◆ Compression is not enabled for the specified pool.

◆ Validation for DECOMPRESS fails for a device and SKIP has not been specified.

Decompress will FAIL for a device when:


◆ The device is not bound to the specified pool.



SyntaxDECOMPRESS{LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)PATH(xx.xx.xx.xx)CONTROLLER(xxxxxxx[-xxxxx]))DEV(device|range|list)POOL(poolname)[MOVE][SKIP][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]


Command Reference

Parameters








This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be decompressed.

POOL(poolname)

This required parameter specifies the pool where the devices are bound.












Command Reference

[MOVE]

By default, if a thin device containing allocations in multiple pools is decompressed, all allocations are decompressed in the pools where they reside. If this optional parameter is specified, all allocations for the device are moved to the pool where the device is currently bound to before decompressing those allocations. If this option is used, all allocations for the device reside in the bound pool after decompression is complete.

[SKIP]


[NOEXEC]



[DEBUG]











Command Reference






[VERBOSE]




Command Reference

DELETE

DELETE removes a pool from a Symmetrix system.

Note: To be eligible for deletion, a pool must be empty.

DELETE will fail completely when:


◆ The specified pool is not empty.



SyntaxDELETE{LOCAL|LCL}(UNIT(device)| VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


POOL(poolname)[NOEXEC][DEBUG][VERBOSE]

Parameter













Command Reference


POOL(poolname)

This required parameter specifies the pool to be deleted.

[NOEXEC]



[DEBUG]



[VERBOSE]



PATH Specifies the path to reach the Symmetrix system where the pool to be deleted resides. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

DISABLE

DescriptionDISABLE changes the status of one or more devices from active to inactive and makes the devices unavailable for allocation. Subsequent actions requiring allocation within the pool to which the device(s) are assigned cannot result in allocation of tracks on the deactivated device(s). Tracks already allocated on the device(s) remain allocated, however.

DISABLE will fail completely when:

◆ A pool name is provided but the specified pool cannot be found.




◆ DISABLE validation fails for a device and SKIP has not been specified.

DISABLE will fail for a device when:

◆ A pool name was provided and the device is not in the specified pool.


◆ A pool is enabled for compression and the DISABLE command is issued for the last active data device. While a pool is enabled for compression, there must be at least one active data device in the pool.

◆ Disabling that device would cause the pool to be greater than 90% used. Percent used is calculated using the number of used and free tracks on active devices in the pool as follows:

Percent used = (used tracks on active devices * 100) / (used + free tracks on active devices)

◆ Disabling that device would cause the oversubscription rate (for Enginuity levels 5874 and higher) of the pool to exceed the maximum oversubscription rate of the pool set the by the user.





Command Reference




SyntaxDISABLE{LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


DEV(device|range|list)[POOL(poolname)][SKIP][NOEXEC][DEBUG][VERBOSE]

Parameters













Command Reference



This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be disabled.

POOL(poolname)

This required parameter specifies the pool where the specified devices are to be disabled.

[SKIP]

This optional parameter allows ineligible devices to be skipped rather than terminating the action. It may be used in conjunction with the POOL parameter to allow specification of a device range that includes both active devices in the specified pool and other devices that do not satisfy these requirements.

[NOEXEC]



[DEBUG]


PATH Specifies the path to reach the Symmetrix system where the devices to be disabled within the pool reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference


[VERBOSE]




Command Reference

DISPLAY

DescriptionDISPLAY allows you to list selected pools or list all available pools

When no pool name or pool name mask is specified, all available pools are displayed. When a pool name mask is specified, only pools with names that match the mask are displayed.

If a specific pool is named, the command displays the devices in the pool. An optional device range may be specified to limit the display of devices in the pool.

DISPLAY will fail completely when a valid gatekeeper is not supplied (via the LOCAL or REMOTE parameter).

Note: EMC suggests that the DISPLAY command should only be used to display the list of pools and devices should always be queried using the QUERY command.

SyntaxDISPLAY{LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


[POOL(poolname)][TYPE(SNAPPOOL|DSEPOOL|THINPOOL)]DEV(device|range|list)[ACTIVE][NOEXEC][DEBUG][VERBOSE]

Parameters








Command Reference




[POOL(poolname)]

This optional parameter specifies the pools for information display. If specified, either a mask or an explicit pool name is allowed.

If a mask is specified, the pools whose names match the mask are displayed. A pool name matches the mask when the initial characters of the pool name match the characters of the mask preceding the asterisk.

If POOLNAME is not specified, then a summary of all pools with the MAXO, ACTO, and %-Used is added to the display output

Note: A mask consists of a string whose final character is an asterisk.

TYPE(SNAPPOOL|DSEPOOL|THINPOOL)

This optional parameter identifies the usage for the pool. Valid values are SNAPPOOL, DSEPOOL, or THINPOOL.


This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be displayed. It is allowed only if an explicit pool name (not a mask) is specified.




PATH Specifies the path to reach the Symmetrix system where the pool to be displayed resides. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[ACTIVE]

This optional parameter is only meaningful when an explicit pool name is specified, and the devices in the pool are active. If it is not specified, all devices in the pool are listed.

[NOEXEC]



[DEBUG]



[VERBOSE]



DISPLAY Examples

Example 1

When neither a pool name nor a pool name mask is specified, all pools are displayed.

EMCU500I DISPLAY LCL(UNIT(2101)) EMCU010I Pools on Controller 0001956-00057 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 S EMCU012I MFSQAR1 0001 T Avail 3390 SATA 7200 70 80 3 1 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 1 95 N Dis->EnaEMCU012I JCPTCKDPOOL1 0003 T Avail 3390 SATA 7200 70 80 0 0 N DisabledEMCU012I MFDSE1 0004 D Avail 3390 FIBRE 15K 70 80 0 N EMCU012I JCPTCKDPOOL2 0005 T Avail ? 30 90 0 0 0 N DisabledEMCU012I MFCKD4 0006 T Avail 3390 FIBRE 15K 70 90 1 84 N Ena->DisEMCU012I DTTHINFBA1 0007 T Avail FBA FIBRE 15K 25 99 4 3 0 N DisabledEMCU012I MSFSNAP 0008 S Avail 3390 SATA 7200 70 80 0 N EMCU012I MSFBCV 0009 T Avail 3390 SATA 7200 70 90 1 84 Y DisabledEMCU012I MFTEST 000A T Avail 3390 SATA 7200 70 80 200 4 2 N EnabledEMCU012I STORRECLAIM 000B T Avail FBA SATA 7200 70 80 2 0 N DisabledEMCU012I DTTHINPOOL1 000C T Avail 3390 FIBRE 15K 25 99 1 0 1 N EnabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete


Command Reference

Example 2

When a pool type is specified, only the pools matching that type are displayed.

EMCU500I DISPLAY TYPE(THINPOOL) LCL(UNIT(2101)) EMCU010I Pools on Controller 0001956-00057 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I MFSQAR1 0001 T Avail 3390 SATA 7200 70 80 3 1 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 1 95 N Dis->EnaEMCU012I JCPTCKDPOOL1 0003 T Avail 3390 SATA 7200 70 80 0 0 N DisabledEMCU012I JCPTCKDPOOL2 0005 T Avail ? 30 90 0 0 0 N DisabledEMCU012I MFCKD4 0006 T Avail 3390 FIBRE 15K 70 90 1 84 N Ena->DisEMCU012I DTTHINFBA1 0007 T Avail FBA FIBRE 15K 25 99 4 3 0 N DisabledEMCU012I MSFBCV 0009 T Avail 3390 SATA 7200 70 90 1 84 Y DisabledEMCU012I MFTEST 000A T Avail 3390 SATA 7200 70 80 200 4 2 N EnabledEMCU012I STORRECLAIM 000B T Avail FBA SATA 7200 70 80 2 0 N DisabledEMCU012I DTTHINPOOL1 000C T Avail 3390 FIBRE 15K 25 99 1 0 1 N EnabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

Example 3

When a pool name mask is specified, only pools whose names match the specified mask are displayed.

EMCU500I DISPLAY LCL(UNIT(2101)) POOL(MF*) EMCU010I Pools on Controller 0001956-00057 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I MFSQAR1 0001 T Avail 3390 SATA 7200 70 80 3 1 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 1 95 N Dis->EnaEMCU012I MFDSE1 0004 D Avail 3390 FIBRE 15K 70 80 0 N EMCU012I MFCKD4 0006 T Avail 3390 FIBRE 15K 70 90 1 84 N Ena->DisEMCU012I MFTEST 000A T Avail 3390 SATA 7200 70 80 200 4 2 N EnabledEMCU001I GPM command complete

Example 4

When a pool name mask and pool type are specified, only pools of the specified type whose names match the specified mask are displayed.

EMCU500I DISPLAY TYPE(THINPOOL) LCL(UNIT(2101)) POOL(MF*) EMCU010I Pools on Controller 0001956-00057 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I MFSQAR1 0001 T Avail 3390 SATA 7200 70 80 3 1 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 1 95 N Dis->EnaEMCU012I MFCKD4 0006 T Avail 3390 FIBRE 15K 70 90 1 84 N Ena->DisEMCU012I MFTEST 000A T Avail 3390 SATA 7200 70 80 200 4 2 N EnabledEMCU001I GPM command complete


Command Reference

DISPLAY field descriptions

The following table lists the field descriptions for the DISPLAY command, which include the display heading fields from either message EMCU011I or EMCU014I.

Table 5 DISPLAY field descriptions

Field Description

EMCU011I message heading fields

Serial number The serial number of Symmetrix system where the listed pools reside.

API version The version of EMCSCF that was accessed to obtain pool information.

Pool name The name of the pool.

Id An internal pool identifier, used for diagnostic purposes.

Typ The pool type defining the use for which the pool is intended:

T (Thin)— Devices assigned to the pool contain data backing thin devices that are bound to the pool.

S (Snap)— Devices assigned to the pool contain data involved in a TimeFinder Snap operation.

D (DSE)— Devices assigned to the pool contain SRDF/A spill data for SRDF/A sessions when DSE is active and the DSE threshold has been exceeded.

Emul The device emulation associated with the pool, 3390, FBA or none:

3390—3390 device emulation

FBA—FBA device emulation

?—No device emulation is established for the pool because no devices are assigned to the pool. If this appears, all device related fields for the pool are blank.

This field is blank for the default pools.

Stat The status of the pool. The value is one of the following:

Avail — The pool's devices may accept track allocations.

Full — The pool is full and cannot accept additional track allocations.

Undef — The status is unknown.



Command Reference

Class Identifies the storage class of devices in the pool.

FIBRE — devices in the pool use fibre channel technology

EXT — EXT devices

FLASH — devices in the pool are flash devices

SATA — SATA devices

This field is blank if no devices are assigned to the pool and for the default pools.

This appears only for non empty thin pools on Symmetrix systems at Enginuity level 5774 or higher.

Speed The speed of devices in the pool;

7200— 7200 RPM

10K—10K RPM

15K— 15K RPM

FLASH

This field is blank if no devices are assigned to the pool.

This appears only for thin pools on Symmetrix systems at Enginuity level 5774 or higher.

Alarms This shows the warning and alert threshold values in effect for the pool. When pool space utilization reaches either value or goes below either value, processors are notified and may issue appropriate messages or take other action.

MaxO This gives the maximum oversubscription ratio (for Enginuity levels 5874 and higher) permitted for the pool. A request to bind or rebind a device to the pool, or a request to deactivate or drain an active pool device, is rejected if the ratio of the potential track allocation requirements of devices bound to the pool to the total size of enabled pool devices exceeds this value.

This field is blank if oversubscription checking does not apply to the pool.

Note: Maximum oversubscription rate (MaxO) is a ratio and is shown as a whole number, not a percentage.


Field Description


Command Reference

ActO This shows the actual oversubscription ratio (for Enginuity levels 5874 and higher) of the pool.




An oversubscription rate of 1 means the number of bound thin device tracks and active data device tracks for the pool are equal. In other words, the pool is “fully-subscribed” or “fully-provisioned”. If all thin devices bound to the pool are filled to their capacity, the pool will be at 100% used.


Note: Actual oversubscription rate (ActO) is a ratio and is shown as a whole number, not a percentage. Some rounding may occur.

%-Used This shows the percentage used for the pool. This is calculated by dividing the total number of used tracks for all active data devices in the pool by the total number of used and free tracks for all active data devices in the pool.


Field Description


Command Reference

Reb This shows whether or not the pool is currently rebalancing the used tracks amongst the active devices in the pool. The possible values are as follows:

Y — Pool is currently in the process of rebalancing

N —Pool is not currently in the process of rebalancing

If a pool does not indicate that it is rebalancing immediately after issuing a REBALANCE command, follow up with a subsequent DISPLAY. It may take a moment for the rebalancing operation to begin.

Depending on the VARIANCE specified on the REBALANCE command and the number of used tracks on the active devices in the pool, the rebalancing operation may complete very quickly.

Compress This column shows the compression state of the thin pool. The possible values are:

Dis=>Ena — Pool is enabling for compression.Ena=>Dis — Pool is disabling for compression.Enabled — Pool is enabled for compression.Disabled — Pool is disabled for compression.

EMCU014I message heading fields

Device Indicates the Symmetrix device number.

Emul The device emulation associated with the pool, 3390, FBA or none:

3390—3390 device emulation

FBA—FBA device emulation

?—No device emulation is established for the pool because no devices are assigned to the pool. If this appears, all device related fields for the pool are blank.


State The state of the listed pool device. Values include:

Undef — The state of the pool device is unknown.Act — The pool device is active.Inact — The pool device is inactive.Drain — The pool device is draining.Prot —The pool device cannot be drained because it owns protected tracks.Wait — The pool device is waiting for free space in the pool in order to finish draining.

Alloc Indicates the total number of allocated tracks.


Field Description


Command Reference

Note: EMCU014I is used for both the DISPLAY and the QUERY ALLOC/ALLALLOCS commands. Not all fields are displayed for each command.

Note: For examples of GPM command displays, refer to “GPM command examples” on page 397.

Used Indicates the total number of used tracks.

Shared Indicates the total number of shared tracks.

Persist indicates the total number of allocated tracks with the persistent attribute set.

Pool Indicates the pool that the device is bound to (QUERY ALLOCS) or the pool that contains the allocations (QUERY ALLOC ALLALLOCS).


Field Description


Command Reference

DRAIN

DescriptionDRAIN initiates a process where allocated tracks on a pool device are moved to other devices in the pool. During the drain process, new allocations are not made on the device. When the drain process is complete, the device is set inactive to prevent new allocations on the device.

DRAIN will fail completely when:




DRAIN will fail for a device when:

◆ Insufficient tracks are available on the remaining devices in the pool to contain the data on the device (FAST policies can come into play in ascertaining insufficiency, as well as maximum oversubscription ratios).

◆ No other devices in the device's pool are active.

◆ The device is participating in a pool management task, such as rebalancing.


◆ A pool name was provided and the device is not in the specified pool.

◆ A pool name was provided but the specified pool cannot be found.

◆ Since DRAIN results in the requested devices being set inactive, draining of a device will not be allowed if by disabling that device the pool would be greater than 90% used. Percent used is calculated using the number of used and free tracks on active devices in the pool as follows:

Percent used = (used tracks on active devices * 100) / (used + free tracks on active devices)

◆ Draining that device would cause more than 20% of the devices in the pool to start draining on a single DRAIN command.

◆ Since DRAIN results in the requested devices being set inactive, draining of a device will not be allowed if by disabling that device the oversubscription rate (for Enginuity levels 5874 and higher) of the pool would exceed the maximum oversubscription rate of the pool set the by the user.




Command Reference





SyntaxDRAIN {LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[SKIP][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]

Parameters








Command Reference





This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be drained from the specified pool.

POOL(poolname)

This required parameter specifies the pool where the devices are to be drained reside.

[SKIP]

This optional parameter allows ineligible devices to be skipped rather than terminating the action. It allows specification of a device range that includes both devices in the specified pool that are currently draining and other devices.

[NOEXEC]






PATH Specifies the path to reach the Symmetrix system where the devices to be drained within the pool reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[DEBUG]















[VERBOSE]


Command Reference



ENABLE

DescriptionENABLE changes the status of one or more devices from inactive to active and makes the devices available for allocation. Subsequent actions requiring allocation within the pool where the device(s) are assigned may result in allocation of tracks on the activated device(s). For a thin pool, such an activity could consist of a host-apparent update to a device bound to the pool. For a DSE pool, such an activity could consist of an overflow of cache by an SRDF/A session on which DSE is active.

ENABLE will fail completely when:

◆ The ENABLE validation fails for a device and SKIP has not been specified.




ENABLE will fail for a device when:

◆ The device is in the draining state.

◆ The device is participating in a pool management background task, such as rebalancing.


◆ A pool name was specified and the device is not in the specified pool.

Note: If a device within the specified device range is already active, it is not considered ineligible, but is skipped whether or not the SKIP parameter has been specified.

SyntaxENABLE {LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[SKIP][NOEXEC][DEBUG][VERBOSE]


Command Reference

Parameters








This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be activated.

POOL(poolname)

This required parameter specifies the intended pool where the devices that are activated reside.







PATH Specifies the path to reach the Symmetrix system where the devices to be activated reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[SKIP]

This optional parameter allows ineligible devices to be skipped rather than terminating the action. It may be used in conjunction with the POOL parameter to allow specification of a device range that includes both inactive devices to the specified pool and other devices that do not satisfy these requirements.

[NOEXEC]



[DEBUG]



[VERBOSE]




Command Reference

HALTTASK

DescriptionHALTTASK stops a background task currently in progress for the specified thin device(s). On the QUERY THINDEV display, the Task column shows the most recent thin device-oriented task for each listed thin device, and the Status column shows the current status of that task. If a thin device task shows a Status of 'Active', the HALTTASK command can be used to stop that task, at which time its Status will change to 'Halted'.

For example, Zero Reclaim can affect performance on the Symmetrix. If a thin device shows Reclaim Active, the HALTTASK command can be used to stop Zero Reclaim, at which time the thin device will show Reclaim Halted. If a Reclaim task is halted, it will resume where it left off the next time a Zero Reclaim is started. Zero Reclaim is an important process and cannot be skipped entirely.

Note: HALTTASK changes the Status for the specified thin device(s) to 'Halted' regardless of the current Status. If the task is still running at the time the HALTTASK command is issued, the task will recognize the 'Halted' Status and will stop running. If the task has already completed, the Status will still be set to 'Halted', but it will have no effect.

HALTTASK will fail completely when:

◆ A valid gatekeeper is not supplied (via the local or remote parameter).

◆ A valid device or range of devices is not supplied (via the dev parameter.)




◆ Validation for HALTTASK fails for a device and skip has not been specified.

HALTTASK will fail for a device when:



SyntaxHALTTASK{LOCAL|LCL}(UNIT (device) | VOL(volser) | DDNAME(ddname))|{REMOTE|RMT}(UNIT (device) | VOL(volser) | DDNAME(ddname)




Command Reference

Parameters







DEV(device|range|list)This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, for which a current process is to be halted.

POOL(poolname)This required parameter specifies the intended pool where the operation is to be halted.







PATH Specifies the path to reach the Symmetrix system where the devices to be drained reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[SKIP]


[NOEXEC]This optional parameter causes syntax checking to be performed without the actual execution of the command. The command only checks for proper syntax. If the syntax is correct, the command completes successfully. If a syntax error is found, the command fails.


[DEBUG]This optional parameter generates command-level diagnostic information that does not affect the outcome of the command. This diagnostic information is written to the module-specific DDs DBUGPMBT, DBUGPMCM, DBUGPMSD, and DBUGPMSS. To avoid unnecessary overhead, specify this option only when requested by EMC technical support and only on the commands for which diagnostics are requested.


[WAIT(value,WARN|ERROR)]This optional parameter will attempt to wait until all Symmetrix tasks associated with the command are complete before returning control to the batch job (in batch mode) or user (in online mode).









Command Reference




[VERBOSE]




Command Reference

HDRAIN

DescriptionHDRAIN halts the process of a pool device reassigning its allocated tracks to other available devices in the same pool (draining). All devices that are actively draining when HDRAIN is issued are set as active. If any devices are inactive and are not draining (or have finished draining), they are identified as incomplete and remain inactive. If this situation arises, the ENABLE command must be issued for these devices to set them active before they can be used. All devices that are active and not draining after the HDRAIN are identified as complete.

HDRAIN will fail completely when:





◆ The HDRAIN validation fails for a device and SKIP has not been specified.

HDRAIN will fail for a device when:


◆ The device is not in the specified pool.

◆ The device is not currently draining and is inactive (all devices that are active and not draining after the HDRAIN are identified as complete).

SyntaxHDRAIN {LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)



Parameters







Command Reference






This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, for which a current drain process is to be terminated.

POOL(poolname)

This required parameter specifies the intended pool where the drain operation is to be halted.

[SKIP]


[NOEXEC]





PATH Specifies the path to reach the Symmetrix system where the devices to be drained reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference


[DEBUG]
















Command Reference

[VERBOSE]




Command Reference

MOVE

DescriptionThe MOVE command moves existing allocations for the requested thin devices from a source pool (as specified on the SRCPOOL parameter) to a target pool (as specified on the POOL parameter), without the loss of data.

If the REBIND parameter is not specified, the MOVE command moves existing allocations from a pool where the thin device(s) were previously bound (as specified on the SRCPOOL parameter) to the pool where the thin device(s) are currently bound (as specified on the POOL parameter). All tracks allocated for the devices in the source pool will be moved to the pool where the devices are currently bound. The devices must already have been rebound to the new POOL using the REBIND command before the MOVE command, with the REBIND parameter, can be used.

If the REBIND parameter is specified on the MOVE command, the thin devices are first rebound to the target pool, as specified on the POOL parameter, and then all tracks allocated for the devices in the source pool, as specified on the SRCPOOL parameter, are moved to the target pool where the devices are now bound.

MOVE will fail completely when:

◆ The specified pool is not found.

◆ A valid target pool name is not supplied (via the POOL parameter).

◆ A valid source pool name is not supplied (via the SRCPOOL parameter).





◆ The MOVE validation fails for a device and SKIP has not been specified.

MOVE will fail for a device when:

◆ The device is not currently bound to a pool.


◆ The specified thin device is compressed and the target pool is not enabled for compression. In order to MOVE a compressed thin device, the target pool must be enabled for compression.

◆ If the REBIND option is specified, MOVE of a device will not be allowed if by rebinding that device the oversubscription rate (for Enginuity levels 5874 and higher) of the target pool would exceed the maximum oversubscription rate of the pool set the by the user.

Oversubscription rate applies to thin pools only. The actual oversubscription rate (ActO) and maximum oversubscription rate (MaxO) is shown for each thin pool on the pool list DISPLAY report. Oversubscription rate is the ratio of bound thin device tracks


Command Reference

to active data device tracks for a thin pool. It is calculated by dividing the total number of tracks on thin devices bound to the pool by the total number of tracks on active data devices in the pool, as follows:






SyntaxMOVE {LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)SOURCEPOOL(poolname)[REBIND][SKIP][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]

Parameters







Command Reference






This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, where a move process is to be performed.

POOL(poolname)

This required parameter specifies the name of the pool where the device(s) are currently bound, and to where the allocations are moved.

SOURCEPOOL(pool-name)

This required parameter names the pool where the device(s) were previously bound, and from where the allocations are moved.

[REBIND]

This optional parameter specifies that the thin devices are first rebound to the target pool, specified on the POOL parameter, before the existing allocations are moved from the source pool, specified on the SRCPOOL parameter, to the target pool. This parameter allows the rebind and move to be executed using a single command. The result is equivalent to separately doing the REBIND command followed by the MOVE command without the REBIND parameter.




PATH Specifies the path to reach the Symmetrix system where the pool resides. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[SKIP]


[NOEXEC]



[DEBUG]













Command Reference




[VERBOSE]




Command Reference

PERSIST OFF

DescriptionPERSIST OFF causes the persistent attribute to be reset for all tracks allocated for the specified thin devices, allowing the tracks to be freed without the thin devices being unbound. As a result, any and all persistent allocated tracks are no longer persistent.

Allocated tracks that have the persistent attribute turned off are not freed until the thin device they are backing has been unbound from the pool containing the data device on which the tracks are allocated.

Note: PERSIST ON is unsupported. To allocate and mark all tracks persistent for the specified thin devices, you must use the ALLOCATE command along with the PERSIST parameter.

PERSIST OFF will fail completely if:







◆ PERSIST OFF validation fails for a device and SKIP has not been specified.

PERSIST OFF will fail for a device if:




SyntaxPERSIST OFF {LOCAL|LCL}(UNIT(device)|VOL(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOL(volser)|DDNAME(ddname)

PATH(xx.xx.xx.xx)CONTROLLER(xxxxxxx[-xxxxx]))



Command Reference

Parameters







POOL(poolname)

This required parameter specifies the name of the pool containing the tracks for the specified thin device(s) for which the persistent attribute is to be removed.


This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, for which the persistent attribute for all allocated tracks will be removed.












Command Reference

[SKIP]

This optional parameter may be specified to allow ineligible devices to be skipped rather than terminating the action.

[NOEXEC]



[DEBUG]














Command Reference



[VERBOSE]




Command Reference

POOLATTR

DescriptionPOOLATTR is used to specify values that apply to the pool as a whole.

Alert thresholds

Alert thresholds apply only to thin pools. Two thresholds are available, a warning or low alert and a critical or high alert. Each threshold is a value between 25 and 99, representing a percentage of the available tracks in the pool. For each threshold type (warning or critical), when the percentage of available tracks allocated has reached the threshold value, the corresponding alert is set.

Maximum oversubscription ratio

Maximum oversubscription ratio applies only to thin pools. It specifies the maximum ratio of the host-apparent capacity of all thin devices bound to the pool to the physical capacity of all active data devices in the pool. Omit the MAXOSUB parameter to indicate that no maximum exists. This is the default setting.

Compression state

Compression state applies only to thin pools. The compression state identifies whether or not compression is enabled or disabled for the specified thin pool. To enable allocations in a pool to be compressed and reserve space in the pool for decompression, a pool must be enabled for compression. Compression is disabled by default and must be enabled manually before thin devices bound to that pool can be compressed.

Once a pool is enabled for compression, a background process runs to reserve storage in the pool that is used to temporarily decompress data. No compression of allocations in this pool can occur until this process completes. A pool should not be enabled for compression unless there are active data devices with free space in the pool. If there is not enough space on active data devices in the pool to reserve space for temporary decompressions, the pool will not be fully enabled for compression. Instead the pool will wait for free space to complete the enable process. Only after additional data devices are added and/or made active in the pool and there is enough room for the reserve space can the pool become fully enabled. When free space is made available, the pool will become fully enabled the next time the microcode checks for enabling pools, which is approximately every 15 minutes. To avoid this wait, ensure there are active data devices with free space in the pool before enabling compression.

When compression is no longer desired for allocations in a pool, the compression capability of a pool can be disabled. When compression is disabled for a pool, the reserved storage is returned to the pool only after all compressed allocations are decompressed. This is not done automatically when compression is disabled for a pool, and must be done manually using the DECOMPRESS command. Compression will not be fully disabled for a pool until all compressed thin devices bound to that pool are decompressed.

Due to the reserve space necessary for temporary decompressions, data devices will remain allocated and cannot be removed from the pool until compression is fully disabled. Compression cannot be fully disabled unless the data devices are active. Otherwise, when the devices are made active, compression will become fully disabled for the pool the next


Command Reference

time the microcode checks for disabling pools, which is approximately every 15 minutes. To avoid this wait, ensure the data devices containing the reserve space are active before disabling compression.

POOLATTR will fail when:


◆ A valid pool name is not supplied (via the POOL parameter.)


◆ Both critical and warning threshold values are supplied and the value specified for the critical threshold does not exceed the value specified for the warning threshold (valid ranges are 25 to 99%).

◆ A critical threshold value is supplied, no warning threshold value is supplied, and the value specified for the critical threshold does not exceed the current warning threshold value.

◆ A warning threshold value is supplied, no critical threshold value is supplied, and the value specified for the warning threshold is not less than the current critical threshold value.

◆ A maximum oversubscription ratio is specified and is not within the range 0 to 65,534.

◆ The WARN parameter is specified, but the specified pool is not a thin pool.

◆ The CRIT parameter is specified, but the specified pool is not a thin pool.

◆ The MAXOSUB parameter is specified, but the specified pool is not a thin pool.

◆ The COMPRESSION parameter is specified, but the specified pool is not a thin pool.

◆ The COMPRESSION parameter is specified with a value other than ENABLE or DISABLE.

SyntaxPOOLATTR{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


POOL(poolname)[WARN(warning-value)][CRIT(critical-value)][{MAXOSUB|MAXO}(maximum_oversubscription_ratio)][COMPRESSION(ENABLE|DISABLE)][NOEXEC][DEBUG][VERBOSE]


Command Reference

Parameters







POOL(poolname)

This required parameter specifies the pool where the specified value(s) are applied.

[WARN(warning-value)]

This parameter specifies the percentage of available tracks allocated, which, when reached from below or passed from above, triggers a warning alert. The warning value may be a numeric value from 25 to 98, and must be less than the default critical value or the critical value specified in the same command. The default value for WARN is 70 percent. If WARN is specified without CRIT, the default critical value of 80 is used.












Command Reference

[CRIT(critical-value)]

This parameter specifies the percentage of available tracks allocated, which, when reached from below or passed from above, triggers a critical alert. The critical value may be a numeric value from 26 to 99, and must be greater than the default warning value or the warning value specified in the same command. The default value for CRIT is 80 percent. If CRIT is specified without WARN, the default warning value of 70 is used.

[{MAXOSUB|MAXO}(maximum_oversubscription_ratio)]

This optional parameter specifies the maximum ratio of the host-apparent capacity of all thin devices bound to the pool to the physical capacity of all active data devices in the pool. Omit the MAXOSUB parameter to indicate that no maximum exists. This is the default setting.

MAXOSUB (maximum oversubscription rate (for Enginuity levels 5874 and higher)) is a ratio and is interpreted as a whole number, not a percentage.

The actual oversubscription rate (ActO) and maximum oversubscription rate (MaxO) is shown for each listed thin pool on the QUERY POOLS (or pool list DISPLAY) report.



An oversubscription rate less than 1 means the number of bound thin device tracks is less than the number of active data device tracks. In other words, the pool is "under-subscribed". This is the safest situation because given its current state the pool cannot reach 100% used.

An oversubscription rate of 1 means the number of bound thin device tracks and active data device tracks for the pool are equal. In other words, the pool is "fully subscribed" or "fully provisioned". If all thin devices bound to the pool are filled to their capacity, the pool is 100% used.

An oversubscription rate greater than 1 means the number of bound thin device tracks is greater than the number of active data device tracks for the pool. In other words, the pool is "over-subscribed". The percent used for the pool must be carefully monitored. As the pool fills up, more data devices may need to be added to the pool and enabled so the pool does not reach 100% used. For an over-subscribed thin pool, even if the thin devices bound to the pool are not filled to their capacity, it is possible that the pool itself could reach 100% used.

Note: This parameter is valid only for thin pools. Specifying a value can affect the result of the BIND, REBIND, MOVE (with REBIND option), DRAIN, or DISABLE commands. The range of possible values for MAXOSUB is 0 to 65,534. Omit the MAXOSUB parameter to indicate that no maximum exists - this is the default. If MAXOSUB is set to zero, all BIND, REBIND, MOVE (with REBIND option), DRAIN, and DISABLE requests will fail.


Command Reference

[COMPRESSION(ENABLE|DISABLE)]

Specifies whether or not compression IS enabled for the specified thin pool. The possible values for the COMPRESSION parameter are:

• ENABLE – Enables device compression for the pool and reserves space for decompression. Does not actually perform the compression on the data.

A pool should not be enabled for compression unless there are active data devices with free space in the pool. If there is not enough space on active data devices in the pool to reserve space for temporary decompressions, the pool will not be fully enabled for compression.

The POOLATTR command will not fail, but instead the pool will wait for free space to complete the enable process. Only after additional data devices are added and/or made active in the pool and there is enough room for the reserve space can the pool become fully enabled. When free space is made available, the pool will become fully enabled the next time the microcode checks for enabling pools, which is approximately every 15 minutes. To avoid this wait, ensure there are active data devices with free space in the pool before enabling compression.

• DISABLE – Disables device compression for the pool. Does not allow decompression. This is the default parameter value.

Compression cannot be fully disabled unless the data devices are active. Otherwise, when the devices are made active, compression will become fully disabled for the pool the next time the microcode checks for disabling pools, which is approximately every 15 minutes. To avoid this wait, ensure the data devices containing the reserve space are active before disabling compression.

Refer to “COMPRESS” on page 201 for a more complete explanation of the steps to compress data on a thin device.

[NOEXEC]



[DEBUG]




Command Reference

[VERBOSE]




Command Reference

QUERY {parameter}

DescriptionQUERY returns information about objects connected with pool management and thin provisioning. Such information includes the status of devices pertaining to pools in a Symmetrix system (either devices eligible to contain data or thin devices), the characteristics of storage tiers, or background tasks.

For device queries that do include the TIERS parameter, all other filtering parameters are ignored.

For device queries that do not include the TIERS parameter, one or more filters may be specified to limit the devices returned accordingly. When more than one filter is specified, only devices meeting all the filter criteria are returned.

EMC suggests that for information on specific devices, the QUERY command should be used with the following suggested parameters:

◆ QUERY DATADEV — To query data devices (thin pool devices).

◆ QUERY SAVEDEV — To query save devices (SNAP and DSE pool devices).

◆ QUERY POOLDEV — To query data and save devices (thin, SNAP, and DSE pool devices).

Note: EMC suggests that the DISPLAY command should only be used to display the list of pools and devices should always be queried using the QUERY command.

QUERY will fail completely when:


◆ A valid query type is not specified (using the ALLOC, ALLALLOC, DATADEV, SAVEDEV, POOLDEV, THINDEV, POOLS, TASKS, or TIERS keyword).

◆ The specified device or range of devices does not exist on the Symmetrix.


◆ The POOLS, TASKS, or TIERS keyword is specified with the DEV parameter.

SyntaxSyntax for the queries that include the POOLS parameter:

QUERY POOLS{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname) PATH(xx.xx.xx.xx) [CONTROLLER([xxxxxxx-]xxxxx)])[POOL(poolname)][NOEXEC][DEBUG][VERBOSE]


Command Reference

Syntax for queries that include the TASKS parameter:

QUERY {TASKS}{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[NOEXEC][POOL(poolname)][VERBOSE]

Syntax for queries that include the TIERS parameter:

QUERY {TIERS}{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[NOEXEC][VERBOSE]

Syntax for device queries that do not include the TASK or TIERS parameter are shown in the following syntax descriptions.

QUERY ALLOC{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[POOL(poolname)]DEV(device|range|list)[NOEXEC][DEBUG][VERBOSE]

QUERY ALLALLOCS{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[POOL(poolname)]DEV(device|range|list)[NOEXEC][DEBUG][VERBOSE]

QUERY DATADEV{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[POOL(poolname)]DEV(device|range|list)[CKD][FBA][SUMMARY][NOEXEC][DEBUG][VERBOSE]


Command Reference

QUERY SAVEDEV {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[POOL(poolname)]DEV(device|range|list)[CKD][FBA][SUMMARY][NOEXEC][DEBUG][VERBOSE]

QUERY POOLDEV{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname) PATH(xx.xx.xx.xx) [CONTROLLER([xxxxxxx-]xxxxx)])[POOL(poolname)]DEV(device|range|list)[CKD][FBA][SUMMARY][NOEXEC][DEBUG][VERBOSE]

QUERY THINDEV {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


[POOL(poolname)]DEV(device|range|list)[BOUND][UNBOUND][CKD][FBA][SUMMARY][NOEXEC][DEBUG][VERBOSE]

Parameters

POOLS

This optional parameter allows you to list all or only selected pools on the Symmetrix system.

When no pool name or pool name mask is specified, all available pools are listed. When a mask is specified, only pools with names that match the mask are listed. If an explicit pool name is specified, only that pool is listed. Since this query is not device-related, a device or range of devices may not be specified.

The list of pools returned by QUERY POOLS is equivalent to the list of pools returned by DISPLAY. The main difference between the two commands is the behavior when an explicit pool name is specified. QUERY POOLS lists pools only, whereas DISPLAY lists pools or devices depending on the presence of a pool name. On the QUERY POOLS command, if an explicit pool name is specified, the body of the report includes a single line containing information about that pool. On the DISPLAY command, if an


Command Reference

explicit pool name is specified, the devices in that pool are listed instead. For descriptions of the fields returned by QUERY POOLS, refer to “DISPLAY field descriptions” on page 224.

TASKS

This optional parameter requests information regarding certain active thin provisioning background tasks running on the Symmetrix system, for example REBALANCE processing. If a pool name is supplied using the POOL parameter, only tasks for the specified pool are displayed.

TIERS

This optional parameter requests information regarding FAST storage tiers on the Symmetrix system.

Note: The TIERS parameter cannot be used in conjunction with any of the following parameters: POOL, DEVICE, UNBOUND, CKD, FBA or SUMMARY.

ALLOC

Displays data device allocations backing thin devices.

When the device class modifier ALLOC is specified, thin devices are returned according to the following guidelines:

• If both POOL and DEV are omitted, all thin devices on the Symmetrix system are displayed whether or not bound to any pool.

• If POOL is specified and DEV is omitted, thin devices on the Symmetrix system are displayed if bound to the specified pool, unless the ALLALLOCS parameter is specified. When ALLALLOCS is specified, thin devices on the Symmetrix system are displayed if they contain allocations in the specified pool, however, they are not required to be bound to the pool.

• If POOL is omitted and DEV is specified, thin devices on the Symmetrix system are displayed if within the range specified.

• If both POOL and DEV are specified, thin devices on the Symmetrix system are displayed only if they are within the specified range and bound to the specified pool.

ALLALLOCS

QUERY ALLALLOCS displays data device allocations backing the requested thin device(s) by pool. When QUERY ALLALLOCS is issued without the POOL parameter, all allocations in all pools are shown, even if the thin devices have allocations in multiple pools. When specified with the POOL parameter, only the allocations in the specified pool are shown, and allocations in all other pools are omitted. QUERY ALLALLOCS shows all allocations matching the specified criteria, despite which pool the devices are currently bound.

Note: QUERY ALLALLOCS should be used to see exactly in what pool thin device allocations reside. QUERY ALLOC shows the total number of allocations and other totals for the requested thin device(s).


Command Reference

When the device class modifier ALLALLOCS is specified, thin devices are returned according to the following guidelines:

• If both POOL and DEV are omitted, all thin devices on the Symmetrix system are displayed whether or not bound to any pool.

• If POOL is specified and DEV is omitted, thin devices on the Symmetrix system are displayed only if they contain allocations in the specified pool; however, they are not required to be bound to the pool.

• If POOL is omitted and DEV is specified, thin devices on the Symmetrix system are displayed if within the range specified.

• If both POOL and DEV are specified, thin devices on the Symmetrix system are displayed only if they are within the specified range and contain allocations in the specified pool; however, they are not required to be bound to the pool.

DATADEV

If the device class modifier DATADEV is specified, devices that are eligible to be assigned via ADD to pools of type THINPOOL (known as data devices) are returned according to the following guidelines:

• If no pool name is specified, or if a pool name mask is specified, each report line includes the pool name and pool type to which the device is assigned.

• If a pool name is specified, data devices on the Symmetrix system are displayed only if assigned to the specified pool or to a pool matching the specified pool name mask.

QUERY DATADEV,SAVEDEV or POOLDEV

display Prot and Statuscolumn values

• The display for QUERY DATADEV, SAVDEV, and POOLDEV adds the Prot and Status columns, which describe the device protection type and drain status. These columns are displayed whether or not a supplied pool name is part of the query.

Values for the Prot column include:

Values for the Status column include:

Prot value Description

RD0 RAID-0

RD1 RAID-1

RD5 3+1 RAID-5 3+1 (3 data members +1 parity member)

RD5 7+1 RAID-5 7+1 (7 data members +1 parity member)

RD6 6+2 RAID-6 6+2 (6 data members + 2 parity members)

RD6 14+2 RAID-6 14+2 (14 data members + 2 parity members)

Status value Description

blank Device is not draining.

DRAINING Device is draining.

WAITING Device is waiting for free space in the pool to complete draining.

PROT-TRK Device cannot be drained because it owns protected tracks.


Command Reference

SAVEDEV

If the device class modifier SAVEDEV is specified, devices that are eligible to be assigned via ADD to pools of type SAVEDEV or pools of type DSEPOOL (known as save devices) are returned according to the following guidelines:

• If POOL is omitted, all save devices on the Symmetrix system are displayed whether in the default pool or in an assigned pool.

• If POOL is specified, save devices on the Symmetrix system are displayed only if assigned to the specified pool or to a pool matching the specified pool name mask.

• The display for QUERY SAVEDEV adds the Prot and Status columns, which describe the device protection type and drain status. These columns are displayed whether or not a supplied pool name is part of the query. Refer to “QUERY DATADEV, SAVEDEV or POOLDEV display Prot and Status column values” on page 263.

POOLDEV

QUERY POOLDEV displays both data devices and save devices. The display is equivalent to the QUERY DATADEV and QUERY SAVEDEV displays, but both device types are returned. When the device class modifier POOLDEV is specified, data devices and save devices are returned according to the following guidelines:

• If POOL is omitted, all data devices and save devices on the Symmetrix system are displayed whether in the default pool or in an assigned pool.

• If POOL is specified, data devices and save devices on the Symmetrix system are displayed only if assigned to the specified pool or to a pool matching the specified pool name mask.

• The display for QUERY POOLDEV adds the Prot and Status columns, which describe the device protection type and drain status. These columns are displayed whether or not a supplied pool name is part of the query. Refer to “QUERY DATADEV, SAVEDEV or POOLDEV display Prot and Status column values” on page 263.

Note: EMC suggests that QUERY be used to query devices in a pool. QUERY DATADEV can be used to query devices in a thin pool, QUERY SAVEDEV can be used to query devices in a DSE pool or Snap pool, and alternatively QUERY POOLDEV can be used to query devices in any pool. EMC suggests that DISPLAY only be used to display the list of pools and devices always be queried using QUERY.

THINDEV

This optional parameter requests information regarding device characteristics for thin devices. If specified, thin devices are returned according to the following guidelines:

• If POOL is omitted, all thin devices on the Symmetrix system are displayed within the device range, if specified, whether or not bound to any pool.

• If POOL is specified, bound thin devices on the Symmetrix system are displayed within the device range, if specified, only if bound to the specified pool or to a pool matching the specified pool name mask. If the UNBOUND parameter is specified, thin devices that are not bound to any pool are displayed as well; if UNBOUND is not specified, UNBOUND devices are not displayed.


Command Reference

QUERY THINDEV displaycolumn TYP values

• The display for QUERY THINDEV adds the TYP column, which describes the device type in relation to the replication. This column is displayed whether or not a supplied pool name is part of the query. Values include:

Typ values Description

XR XRC device

R1 R1 device

R2 R2 device

BC BCV device

B1 BCV R1 device

B2 BCV R2 device

BS BCV and local replication source device

BT BCV and local replication target device

PR PPRC device

P1 PPRC R1 device

P2 PPRC R2 device

R11 RDF R11 device

R21 RDF R21 device

R22 RDF R22 device

SS Snap source

S1 Snap source R1

S11 Snap source R11

S2 Snap source R2

S22 Snap source R22

T1 Snap target R1

T11 Snap target R11

T2 Snap target R2

T22 Snap target R22

ST Snap target

VD Virtual device


Command Reference

QUERY THINDEV displaycolumns for compression

states

• The display for QUERY THINDEV adds the following columns to display thin device-oriented task status. Values include:

An example of the QUERY display with the added TYP and thin device-oriented task status columns is shown below:

EMCU500I QUERY THINDEV LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU184I Thin Devices on 0001956-00057 Bound to Pool DTTHINPOOL1 API Ver: 7.50EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000090 2168 3390 UOD090 Y N 1113 R1 Y Compress DoneEMCU110I 00000091 2169 3390 UOD091 Y N 1113 Y Compress Done EMCU110I 00000092 216A 3390 ****** Y N 1113 R1 N Decompress DoneEMCU110I 00000093 216B 3390 ****** Y N 1113 N Bind DoneEMCU071I Device Totals: CKD Bound: 00004 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 66780 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete

Thin device-oriented task status

columns Description

COM Shows the thin device-oriented task status.Possible values include:

Y = Thin device has compressed allocations.N = Thin device has no compressed allocations.

Task This column shows the last thin device-oriented task that was executed for the thin device or the most current phase of that task if applicable. Possible values include:

Bind = BINDBind Map = BIND mapping poolBind Fmt = BIND formatting cylindersBind Hdr = BIND initializing headerBind Alloc = BIND allocating space in poolUnbind = UNBINDUnbd Dealc = UNBIND deallocating space in poolUnbd Unmap = UNBIND unmapping poolAllocate = ALLOCATEMove = MOVEMove Waits = MOVE is waiting for free space to continueCompress = COMPRESSDecompress = DECOMPRESSReclaim = Zero ReclaimPersistOff = PERSIST OFFUnknown = unknown applicationStart Err = task failed to startUndef Err = undefined error

Status This column shows the status of the last thin device-oriented task executed for the thin device. Possible values include:

Active = task is activeHalted = task is haltedError = task ended in errorDone = task is complete


Command Reference







[POOL(poolname)]

This optional parameter specifies the pool(s) for which device information is requested. If specified, either a mask or an explicit pool name is allowed.

If a mask is specified, all pools whose names match the mask and which have the implied pool type are selected. A mask consists of a string whose final character is an asterisk. A pool name matches the mask if the initial characters of the pool name match the characters of the mask preceding the asterisk. If an explicit pool name is specified, only the named pool is selected, if it exists and if its type equals the implied pool type.







PATH Specifies the path to reach the Symmetrix system where the devices to be queried reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

In either case:

• If THINDEV is specified, only devices bound to selected thin pools are listed.

• If SAVEDEV is specified, only devices assigned to selected DSE and snap pools are listed

• If DATADEV is specified, only devices assigned to selected thin pools are listed.

Example:

QUERY THINDEV (LCL(UNIT(8A00)) POOL(ABC*)


This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be queried from the specified pool.

[BOUND]

This optional parameter applies only when QUERY THINDEV is specified. When specified, only bound devices matching the specified criteria are listed. If specified in conjunction with the POOL parameter, it has no effect, since the POOL parameter implies that only thin devices bound to the selected pool(s) will be listed.

[UNBOUND]

This optional parameter applies only when QUERY THINDEV is specified, and is only applicable in conjunction with the POOL parameter. When specified in conjunction with the POOL parameter, unbound thin devices are listed in addition to the devices bound to the selected pools. If not specified, unbound devices are not listed if the POOL parameter is specified. When specified without the POOL parameter, only unbound thin devices are listed.

[CKD]

This optional parameter causes only CKD device information to be displayed. When this parameter is specified, summary data is generated only for CKD devices, if any. This parameter may not be specified if the FBA parameter is specified.

[FBA]

This optional parameter causes only the FBA device information to be displayed. When this parameter is specified, summary data is generated only for FBA devices, if any. This parameter may not be specified if the CKD parameter is specified.

[SUMMARY]

This optional parameter causes omission of device detail lines and generates summary information only. The information supplied depends upon the device class modifier as follows:

• QUERY THINDEV—device totals and track totals for bound CKD devices, unbound CKD devices, bound FBA devices, and unbound FBA devices.

• QUERY DATADEV—aggregate counts of free and allocated tracks and the percentage of tracks used for each emulation type having a non-zero aggregate count.


Command Reference

• QUERY SAVEDEV—aggregate counts of free and allocated tracks and the percentage of tracks used for each emulation type having a non-zero aggregate count.

Note: Track totals greater than 9 digits (approximately 4.3 billion) are scaled to 9 digits or less using the following suffixes: M for millions (mega), G for billions (giga), T for trillions (tera), P for quadrillions (peta), and E for quintillions (exa).

[NOEXEC]



[DEBUG]



[VERBOSE]




Command Reference

QUERY display field descriptions

The following table gives a brief description of the QUERY display field descriptions and the command parameters that determine when these fields are displayed.

Table 6 QUERY display field descriptions

Field Description Displayed with these QUERY command parameters

Header

Serial number The serial number of the Symmetrix system where the listed pools reside.

ALLOC, DATADEV, SAVEDEV, POOLDEV, THINDEV, TASKS

Pool name The name of the device pool specified in the command. ALLOC, DATADEV, SAVEDEV, POOLDEV, THINDEV

API version The version of EMCSCF that was accessed to obtain device information.

ALLOC, DATADEV, SAVEDEV, POOLDEV, THINDEV, TASKS

Detail line columns

Device# Symmetrix device number of the device described on the detail line.

DATADEV, SAVEDEV, POOLDEV, ALLOC, ALLALLOCS

CUU MVS device number or **** if device not mapped to MVS CUU. THINDEV

Task The hexadecimal task identifier. TASKS

Emul Device emulation: 3380, 3390 or FBA.Note: For THINDEV it could also be FBAh (meta head) or FBAm (meta member), and not 3380 emulation.

DATADEV, SAVEDEV, POOLDEV, THINDEV

Volser The volser of the device; otherwise ****** THINDEV

Bound to The pool where the device is currently bound. If not currently bound, the value is *Unbound*.

THINDEV

Rdy Y = device is in ready state, N = device is not in ready state. THINDEV

S/E Y = device is space-efficient, N = device is not space-efficient. THINDEV

A/I The pool status of the device equals A if active, I if inactive, with an asterisk appended if the device is in not-ready state.

DATADEV, SAVEDEV, POOLDEV

Alloc For QUERY ALLOC, the total number of allocated tracks for the listed thin device, from the host point-of-view. For QUERY ALLALLOCS, the number of allocated tracks residing in the listed pool for the listed thin device, from the host point-of-view. This count is unchanged by compression. The actual number of allocated data device tracks backing a compressed thin device can be calculated by subtracting the Compress count (number of tracks saved by compression) from the Alloc count.

ALLOC, ALLALLOCS

Used For QUERY DATADEV, QUERY SAVEDEV, and QUERY POOLDEV, the number of used tracks (containing data) on the listed device.For QUERY ALLOC, the total number of used tracks (allocated and written to) for the listed thin device, from the host point-of-view. This count is unrelated to compression.

DATADEV, SAVEDEV, POOLDEV, ALLOC

Shared The number of shared data device tracks backing the listed device.

ALLOC


Command Reference

Persist The number of data device tracks backing the listed device and having the persistent attribute.

ALLOC

Compress The number of tracks saved by compression for the listed thin device. If the device is not compressed, the number of tracks saved by compression will be zero.

ALLOC, ALLALLOCS

Pool The pool where the device is currently bound (or for QUERY ALLALLOCS, the pool where the allocations reside), if no pool name was specified in the command. If not currently bound, the value is *Unbound*.Note: For TASKS parameter, the name of the device pool acted on by the task. This does not appear if a pool name was specified in the command.

ALLALLOCS, TASKS

Bound Pool The pool where the device is currently bound, if no pool name was specified in the command.

ALLOC

Free Number of unallocated tracks on the device. DATADEV, SAVEDEV, POOLDEV

Pool name The pool to which the device currently belongs. DATADEV, SAVEDEV, POOLDEV

Type Thin or blank if currently assigned to the default pool.Note: For the TASKs parameter, this field identifies the type of task represented by the entry: Rebalance, Move.

DATADEV, SAVEDEV, POOLDEV, TASKS

Class Device storage class, if available. DATADEV, SAVEDEV, POOLDEV

Speed Device speed, if available. DATADEV, SAVEDEV, POOLDEV

Prot Values:RD0 — RAID-0RD1 — RAID-1RD5 3+1 — RAID-5 3+1 (3 data members +1 parity member)RD5 7+1 — RAID-5 7+1 (7 data members +1 parity member)RD6 6+2 — RAID-6 6+2 (6 data members + 2 parity members)RD6 14+2 — RAID-6 14+2 (14 data members + 2 parity members)


Status (for pool device)

Values:blank — Device is not draining.DRAINING — Device is draining.WAITING — Device is waiting for free space in the pool to complete draining.PROT-TRK — Device cannot be drained because it owns protected tracks.


State Task state: Boot, Inact, Idle, Init, Busy, Scan, Move, Wait, Done. TASKS

Status(for thin device task)

Task status: Paused, Completed, Executing, Killed, RscLocked, Queued, Error.

TASKS

Max Delta For rebalance tasks only, the target maximum difference in device utilization percentage between the maximum and minimum device utilizations among the participating devices.

TASKS




Command Reference

Detail line columns for THINIDEV parameter only

Typ XR — XRC deviceR1 — R1 deviceR2 — R2 deviceBC — BCV deviceB1 — BCV R1 deviceB2 — BCV R2 deviceBS — BCV and local replication source deviceBT — BCV and local replication target devicePR — PPRC deviceP1 — PPRC R1 deviceP2 — PPRC R2 deviceR11 — RDF R11 deviceR21 — RDF R21 deviceR22 — RDF R22 deviceSS — Snap source S1 — Snap source R1S11 — Snap source R11S2 — Snap source R2S22 — Snap source R22T1 — Snap target R1T11 — Snap target R11T2 — Snap target R2T22 — Snap target R22ST — Snap targetVD — Virtual device

THINDEV

COM Shows the thin device-oriented task status.Possible values include:

Y = Thin device has compressed allocations.N = Thin device has no compressed allocations.

THINDEV




Command Reference

Task This column shows the last thin device-oriented task that was executed for the thin device or the most current phase of that task if applicable. Possible values include:

Bind = BINDBind Map = BIND mapping poolBind Fmt = BIND formatting cylindersBind Hdr = BIND initializing headerBind Alloc = BIND allocating space in poolUnbind = UNBINDUnbd Dealc = UNBIND deallocating space in poolUnbd Unmap = UNBIND unmapping poolAllocate = ALLOCATEMove = MOVEMove Waits = MOVE is waiting for free space to continueCompress = COMPRESSDecompress = DECOMPRESSReclaim = Zero ReclaimPersistOff = PERSIST OFFUnknown = unknown applicationStart Err = task failed to startUndef Err = undefined error

THINDEV

Status This column shows the status of the last thin device-oriented task executed for the thin device. Possible values include:

Active = task is activeHalted = task is haltedError = task ended in errorDone = task is complete

THINDEV

Summary lines

Emul Device emulation: 3380, 3390 or FBA. DATADEV, SAVEDEV, POOLDEV

Used tracks Total allocated tracks on devices listed.



Free tracks Total un-allocated tracks on devices listed.






Command Reference

%-Used Percentage of allocated tracks out of the total tracks of the devices listed. For a list of all devices in a pool, this can provide an indication of whether a pool utilization alert threshold has been or may be reached.


Device Totals Summary line containing device totals for bound CKD devices, unbound CKD devices, bound FBA devices, and unbound FBA devices.

THINDEV

Track Totals Summary line containing track totals for bound CKD devices, unbound CKD devices, bound FBA devices, and unbound FBA devices.


THINDEV




Command Reference

QUERY display examples

The following are some examples of the different QUERY action command displays.

QUERY ALLOC display examplesHere are four examples of QUERY ALLOC commands with pool names unspecified and specified.

Example 1

When no pool name or device range is specified, the display includes all bound thin devices on the Symmetrix. The name of the pool to which a device is bound (or *Unbound* if not bound) is shown on the device detail line.

EMCU500I QUERY ALLOC LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Used Shared Persist Compress Bound Pool EMCU015I 00000090 16788 105 0 0 16260 DTTHINPOOL1EMCU015I 00000091 16788 105 0 0 16260 DTTHINPOOL1EMCU015I 00000092 120 105 0 0 108 DTTHINPOOL1EMCU015I 00000093 120 105 0 0 0 DTTHINPOOL1EMCU015I 000000D8 6744 6627 0 0 0 MFCKD1 EMCU015I 000000D9 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DA 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DB 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DC 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DD 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DE 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DF 4320 4290 0 0 0 MFCKD1 EMCU015I 000000E0 7320 7179 0 0 0 MFCKD1 EMCU015I 000000E1 7320 7153 0 0 0 MFCKD1 EMCU015I 000000E2 7320 7151 0 0 0 MFCKD1 EMCU015I 000000E3 7320 7151 0 0 0 MFCKD1 EMCU015I 000000E4 7320 7143 0 0 0 MFCKD1 EMCU015I 000000E5 7320 7141 0 0 0 MFCKD1 EMCU015I 000000E6 7320 7120 0 0 0 MFCKD1 EMCU015I 000000E7 7320 7158 0 0 0 MFCKD1 EMCU015I 000000E8 4320 4290 0 0 0 MFCKD1 EMCU015I 000000E9 4320 4177 0 0 0 MFCKD1 EMCU015I 000000EA 4320 4135 0 0 0 MFCKD1 EMCU015I 000000EB 4320 4149 0 0 0 MFCKD1 EMCU015I 000000EC 4320 4290 0 0 0 MFCKD1 EMCU015I 000000ED 4764 4740 0 0 0 MFCKD1 EMCU015I 000000EE 4320 4290 0 0 0 MFCKD1 EMCU015I 000000EF 4764 4740 0 0 0 MFCKD1 EMCU015I 00000100 120 105 0 0 0 MFSQAR1 EMCU015I 00000101 120 105 0 0 0 MFSQAR1 EMCU015I 00000102 120 105 0 0 0 MFSQAR1 EMCU015I 00000103 120 105 0 0 0 MFSQAR1 EMCU015I 00000104 120 105 0 0 0 MFSQAR1 EMCU015I 00000105 120 105 0 0 0 MFSQAR1 EMCU015I 00000106 120 105 0 0 0 MFSQAR1 EMCU015I 00000107 120 105 0 0 0 MFSQAR1 EMCU015I 0000010F 120 45 0 0 0 MFCKD1 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.


Command Reference

Example 2

When no pool name is specified but a device range is specified, the display includes only thin devices in the specified device range. The name of the pool to which a device is bound (or *Unbound* if not bound) is shown on the device detail line.

EMCU500I QUERY ALLOC DEV(0090-00DF) LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Used Shared Persist Compress Bound Pool EMCU015I 00000090 16788 105 0 0 16260 DTTHINPOOL1EMCU015I 00000091 16788 105 0 0 16260 DTTHINPOOL1EMCU015I 00000092 120 105 0 0 108 DTTHINPOOL1EMCU015I 00000093 120 105 0 0 0 DTTHINPOOL1EMCU015I 000000D8 6744 6627 0 0 0 MFCKD1 EMCU015I 000000D9 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DA 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DB 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DC 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DD 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DE 4320 4290 0 0 0 MFCKD1 EMCU015I 000000DF 4320 4290 0 0 0 MFCKD1 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Example 3

When an explicit thin pool name is specified and no device range is specified, the display includes all devices bound to the specified pool. The pool name is included in the report header and is not shown in the report device lines.

EMCU500I QUERY ALLOC LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Used Shared Persist Compress EMCU015I 00000090 16788 105 0 0 16260 EMCU015I 00000091 16788 105 0 0 16260 EMCU015I 00000092 120 105 0 0 108 EMCU015I 00000093 120 105 0 0 0 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Example 4

When both an explicit thin pool name and a device range are specified, the display includes only thin devices both bound to the specified pool and in the specified device range.

EMCU500I QUERY ALLOC DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Used Shared Persist Compress EMCU015I 00000091 16788 105 0 0 16260 EMCU015I 00000092 120 105 0 0 108 EMCU015I 00000093 120 105 0 0 0 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.


Command Reference

QUERY ALLALLOCS When QUERY ALLALLOCS is issued without the POOL parameter, all allocations in all pools are shown, even if the thin devices have allocations in multiple pools. When specified with the POOL parameter, only the allocations in the specified pool are shown, and allocations in all other pools are omitted.

QUERY ALLALLOCS shows all allocations matching the specified criteria, despite which pool the devices are currently bound. QUERY ALLALLOCS lists only thin devices.

Here are some examples using the QUERY ALLALLOCS command.

Example 1

When no pool name or device range is specified, the display includes all bound thin devices on the Symmetrix. The name of the pool where the corresponding allocations reside is shown on each device detail line.

Notice that thin device 92 has multiple device detail lines because it has allocations in 3 different pools, DTTHINPOOL1, DTTHINPOOL2, and DTTHINPOOL3. Only the allocations in DTTHINPOOL1 are compressed, which is apparent because the number of tracks saved by compression in DTTHINPOOL2 and DTTHINPOOL3 is 0.

EMCU500I QUERY ALLALLOCS LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Compress Pool EMCU015I 00000090 16788 16260 DTTHINPOOL1EMCU015I 00000091 16788 16260 DTTHINPOOL1EMCU015I 00000092 120 108 DTTHINPOOL1EMCU015I 00000092 336 0 DTTHINPOOL2EMCU015I 00000092 216 0 DTTHINPOOL3EMCU015I 00000093 120 0 DTTHINPOOL1EMCU015I 000000D8 6744 0 MFCKD1 EMCU015I 000000D9 4320 0 MFCKD1 EMCU015I 000000DA 4320 0 MFCKD1 EMCU015I 000000DB 4320 0 MFCKD1 EMCU015I 000000DC 4320 0 MFCKD1 EMCU015I 000000DD 4320 0 MFCKD1 EMCU015I 000000DE 4320 0 MFCKD1 EMCU015I 000000DF 4320 0 MFCKD1 EMCU015I 000000E0 7320 0 MFCKD1 EMCU015I 000000E1 7320 0 MFCKD1 EMCU015I 000000E2 7320 0 MFCKD1 EMCU015I 000000E3 7320 0 MFCKD1 EMCU015I 000000E4 7320 0 MFCKD1 EMCU015I 000000E5 7320 0 MFCKD1 EMCU015I 000000E6 7320 0 MFCKD1 EMCU015I 000000E7 7320 0 MFCKD1 EMCU015I 000000E8 4320 0 MFCKD1 EMCU015I 000000E9 4320 0 MFCKD1 EMCU015I 000000EA 4320 0 MFCKD1 EMCU015I 000000EB 4320 0 MFCKD1 EMCU015I 000000EC 4320 0 MFCKD1 EMCU015I 000000ED 4764 0 MFCKD1 EMCU015I 000000EE 4320 0 MFCKD1 EMCU015I 000000EF 4764 0 MFCKD1 EMCU015I 00000100 120 0 MFSQAR1 EMCU015I 00000101 120 0 MFSQAR1 EMCU015I 00000102 120 0 MFSQAR1 EMCU015I 00000103 120 0 MFSQAR1 EMCU015I 00000104 120 0 MFSQAR1 EMCU015I 00000105 120 0 MFSQAR1 EMCU015I 00000106 120 0 MFSQAR1 EMCU015I 00000107 120 0 MFSQAR1


Command Reference

EMCU015I 0000010F 120 0 MFCKD1 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Example 2

When no pool name is specified but a device range is specified, the display includes only thin devices in the specified device range. The name of the pool where the corresponding allocations reside is shown on each device detail line.

EMCU500I QUERY ALLALLOCS DEV(0090-00DF) LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Compress Pool EMCU015I 00000090 16788 16260 DTTHINPOOL1EMCU015I 00000091 16788 16260 DTTHINPOOL1EMCU015I 00000092 120 108 DTTHINPOOL1EMCU015I 00000092 336 0 DTTHINPOOL2EMCU015I 00000092 216 0 DTTHINPOOL3EMCU015I 00000093 120 0 DTTHINPOOL1EMCU015I 000000D8 6744 0 MFCKD1 EMCU015I 000000D9 4320 0 MFCKD1 EMCU015I 000000DA 4320 0 MFCKD1 EMCU015I 000000DB 4320 0 MFCKD1 EMCU015I 000000DC 4320 0 MFCKD1 EMCU015I 000000DD 4320 0 MFCKD1 EMCU015I 000000DE 4320 0 MFCKD1 EMCU015I 000000DF 4320 0 MFCKD1 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Example 3

When an explicit thin pool name is specified and no device range is specified, the display includes all devices that have allocations residing in the specified pool. The pool name is included in the report header and is not shown in the device detail lines.

EMCU500I QUERY ALLALLOCS LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Compress EMCU015I 00000090 16788 16260 EMCU015I 00000091 16788 16260 EMCU015I 00000092 120 108 EMCU015I 00000093 120 0 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Example 4

When both an explicit thin pool name and a device range are specified, the display includes only thin devices in the specified device range that have allocations residing in the specified pool. The pool name is included in the report header and is not shown in the device detail lines.

EMCU500I QUERY ALLALLOCS DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc Compress EMCU015I 00000091 16788 16260 EMCU015I 00000092 120 108 EMCU015I 00000093 120 0 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.


Command Reference

QUERY DATADEV display examplesHere are five examples, three of QUERY DATADEV where no explicit pool name is specified and two where the name is specified.

Example 1

When no pool name or pool name mask is specified, all data devices are displayed.

EMCU500I QUERY DATADEV LCL(UNIT(2101))EMCU184I Data Devices on 0001956-00057 API Ver: 7.50EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I StatusEMCU063I 00000128 3390 0 16680 DF_DDEV_POOL SATA 7200 RD6 6+2 IEMCU063I 00000129 3390 0 16680 DF_DDEV_POOL SATA 7200 RD6 6+2 I. . .EMCU063I 0000014A 3390 10032 6648 MFCKD1 Thin FIBRE 15K RD6 6+2 I DRAININGEMCU063I 0000014B 3390 10056 6624 MFCKD1 Thin FIBRE 15K RD6 6+2 I DRAININGEMCU063I 0000014C 3390 10044 6636 MFCKD1 Thin FIBRE 15K RD6 6+2 I DRAINING. . .EMCU063I 00000BD1 3390 0 50064 DF_DDEV_POOL SATA 7200 RD5 7+1 IEMCU063I 00000BD2 3390 0 50064 DF_DDEV_POOL SATA 7200 RD5 7+1 IEMCU063I 00000BD3 3390 0 50064 .NOPOOL. FIBRE 15K RD5 7+1 IEMCU063I 00000BD4 3390 0 50064 .NOPOOL. FIBRE 15K RD5 7+1 IEMCU063I 00000BD5 3390 0 50064 .NOPOOL. FIBRE 15K RD5 7+1 I

Example 2

When no pool name or pool name mask is specified, all data devices are displayed. If an optional device range is specified, the display includes only data devices in the specified device range.

QUERY DATADEV LCL(UNIT(5500)) DEV(FE4-FEB)EMCU060I Data Devices on 0001926-04124 API Ver 7.50EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I StatusEMCU063I 00000FE4 3390 0 16680 DF_DDEV_POOL FIBRE 15K RD5 7+1 IEMCU063I 00000FE5 3390 0 16680 DF_DDEV_POOL FIBRE 15K RD5 7+1 IEMCU063I 00000FE6 3390 0 16680 DF_DDEV_POOL FIBRE 15K RD5 7+1 IEMCU063I 00000FE7 3390 0 16680 DF_DDEV_POOL SATA 7200 RD6 6+2 IEMCU063I 00000FE8 3390 0 16680 DF_DDEV_POOL SATA 7200 RD6 6+2 IEMCU063I 00000FE9 3390 16680 0 MSFCKD1 Thin FIBRE 15K RD6 6+2 A PROT-TRKEMCU063I 00000FEA 3390 12 16668 MSFCKD1 Thin FIBRE 15K RD6 6+2 I DRAININGEMCU063I 00000FEB 3390 12 16668 MSFCKD1 Thin FIBRE 15K RD6 6+2 I DRAININGEMCU064I Totals:EMCU064I For 3390: 16704 used tracks, 116736 free tracks, 12% usedEMCU001I GPM command complete


Command Reference

Example 3

When a pool name or pool name mask is specified, only data devices in pools matching the pool name or pool name mask are displayed.

QUERY DATADEV LCL(UNIT(5500)) POOL(J*)EMCU060I Data Devices on 0001926-04124 API Ver 7.50EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I StatusEMCU063I 00001193 FBA 5460 132624 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 00001194 FBA 5484 132600 JASONASRU Thin FIBRE 15K RD5 3+1 A EMCU063I 00001195 FBA 5484 132600 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 00001196 FBA 5424 132660 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 00001197 FBA 5424 132660 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 00001198 FBA 5436 132648 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 00001199 FBA 5448 132636 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 0000119A FBA 5424 132660 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 0000119B FBA 5424 132660 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 0000119C FBA 5448 132636 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 0000119D FBA 5424 132660 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 0000119E FBA 5424 132660 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 0000119F FBA 5436 132648 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 000011A0 FBA 5484 132600 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 000011A1 FBA 5472 132612 JASONASRU Thin FIBRE 15K RD5 3+1 AEMCU063I 000012AD 3390 0 16680 JDSTHINPOOL1 Thin SATA 7200 RD1 IEMCU063I 000012AE 3390 0 16680 JDSTHINPOOL1 Thin SATA 7200 RD1 IEMCU064I Totals:EMCU064I For 3390: 89136 used tracks, 2979984 free tracks, 2% usedEMCU064I For FBA : 479640 used tracks, 49218600 free tracks, 0% usedEMCU001I GPM command complete

Note: A pool name of “.NOPOOL.”, in any device-oriented QUERY display, means the device is currently not in any pool. The device was previously removed from a user pool and has not yet been added to a new pool.

Example 4

When a pool name is specified within the command, the pool name is included only in the report header and is not shown in the device-specific lines of the report. The pool status of each device is shown as well.

QUERY DATADEV LCL(UNIT(5500)) POOL(MSFCKD1EMCU184I Data Devices on 0001926-04124 in Pool MSFCKD1 API Ver 7.50EMCU061I Device# Emul A/I Used Free Class Speed Prot 0 StatusEMCU063I 00000FE9 3390 A 16680 0 FIBRE 15K RD6 6+2EMCU063I 00000FEA 3390 A 12 16668 FIBRE 15K RD6 6+2EMCU063I 00000FEB 3390 A 12 16668 FIBRE 15K RD6 6+2EMCU063I 00000FEC 3390 I 24 16656 FIBRE 15K RD6 6+2 DRAININGEMCU063I 00000FED 3390 A 24 16656 FIBRE 15K RD6 6+2EMCU063I 00000FEE 3390 A 12 16668 FIBRE 15K RD6 6+2EMCU063I 00000FEF 3390 I 24 16656 FIBRE 15K RD6 6+2 DRAININGEMCU064I Totals:EMCU064I For 3390: 16788 used tracks, 99972 free tracks, 14% usedEMCU001I GPM command complete

Note: An asterisk next to the device status in the A/I column ( A* or I*) means the device is not ready (for example, user not ready, device not ready, etc.). The application that made the device not ready must be used to make the device ready again.


Command Reference

Example 5

When a pool name is specified, the pool name is included in the report header and is not shown in the report device lines. The pool status of each device is shown as well. If an optional device range is specified, devices are listed only if within the specified device range and in the specified thin pool.

QUERY DATADEV LCL(UNIT(5500)) POOL(MSFCKD1) DEV(FEA-FEB)EMCU184I Data Devices on 0001926-04124 in Pool MSFCKD1 API Ver 7.50EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 00000FEA 3390 A 12 16668 FIBRE 15K RD6 6+2EMCU063I 00000FEB 3390 A 12 16668 FIBRE 15K RD6 6+2EMCU064I Totals:EMCU064I For 3390: 24 used tracks, 33336 free tracks, 0% used

EMCU001I GPM command complete

QUERY SAVEDEV display examplesHere are four examples, two of QUERY SAVEDEV when no explicit pool name is specified, one where a poolname mask is specified, and one where the name is specified.

Example 1

When no pool name is specified, all save devices are displayed.

QUERY SAVEDEV LOCAL(UNIT(5500))EMCU060I Save Devices on 0001926-04124 API Ver 7.50EMCU061I Device# Emul Used Free Pool Name Type Tech Speed Prot A/I StatusEMCU063I 00000840 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 000AEMCU063I 00000841 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 AEMCU063I 00000842 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 AEMCU063I 00000843 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 AEMCU063I 00000844 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 AEMCU063I 00000845 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 A. . . . . . . . . . . . . . .EMCU063I 0000087F 3390 0 16695 DEFAULT_POOL Snap FIBRE 15K RD1 AEMCU063I 00000B8C 3390 0 3940020 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 00001210 FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 00001211 FBA 0 138075 DEFAULT_POOL Snap FIBRE 15K RD1 AEMCU063I 00001212 FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 00001213 FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 00001214 FBA 0 982695 DEFAULT_POOL Snap SATA 7200 RD1 A. . . . . . . . . . . . . . .EMCU064I Totals:EMCU064I For 3390: 0 used tracks, 5008500 free tracks, 0% usedEMCU064I For FBA : 0 used tracks, 3622290 free tracks, 0% usedEMCU001I GPM command complete

Example 2

When no pool name is specified, but an optional device range is specified, the display includes only save devices in the specified device range.

QUERY SAVEDEV LOCAL(UNIT(5500)) DEV(1218-1220)EMCU060I Save Devices on 0001926-04124 API Ver 7.50EMCU061I Device# Emul Used Free Pool Name Type Tech Speed Prot A/I StatusEMCU063I 00001218 FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 00001219 FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 0000121A FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 0000121B FBA 0 138075 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 0000121F FBA 0 982695 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU063I 00001220 FBA 0 982695 DEFAULT_POOL Snap SATA 7200 RD1 AEMCU064I Totals:EMCU064I For FBA : 0 used tracks, 2517690 free tracks, 0% usedEMCU001I GPM command complete


Command Reference

Example 3

When a pool name mask is specified with an optional device ranges specified, devices are included only if in a pool matching the mask and within the specified device range.

QUERY SAVEDEV LOCAL(UNIT(9000)) POOL(MSF*) DEV(5E2-5EA)EMCU060I Save Devices on 0001926-02840 API Ver 7.50EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I StatusEMCU063I 000005E2 3390 24 16671 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E3 3390 24 16671 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E4 3390 36 16659 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E5 3390 24 16671 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E6 3390 36 16659 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E7 3390 24 16671 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E8 3390 12 16683 MSFUTDSNAP1 Snap SATA 7200 RD1 I DRAININGEMCU063I 000005E9 3390 1248 15447 MSFUTDSNAP1 Snap SATA 7200 RD1 AEMCU063I 000005EA 3390 1236 15459 MSFUTDSNAP1 Snap SATA 7200 RD1 AEMCU001I GPM command complete

Example 4

When a pool name is specified, the pool name is included in the report header and is not shown in the report device lines. If an optional device range is specified, only devices within the specified device range are included in the display.

QUERY SAVEDEV LCL(UNIT(9000)) POOL(MSFUTDSNAP1) DEV(5E2-5EA)EMCU184I Save Devices on 0001926-02840 in Pool MSFUTDSNAP1 API Ver 7.50EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 000005E2 3390 I 24 16671 SATA 7200 RD1 DRAININGEMCU063I 000005E3 3390 I 24 16671 SATA 7200 RD1 DRAININGEMCU063I 000005E4 3390 I 36 16659 SATA 7200 RD1 DRAININGEMCU063I 000005E5 3390 I 24 16671 SATA 7200 RD1 DRAININGEMCU063I 000005E6 3390 I 36 16659 SATA 7200 RD1 DRAININGEMCU063I 000005E7 3390 I 24 16671 SATA 7200 RD1 DRAININGEMCU063I 000005E8 3390 I 12 16683 SATA 7200 RD1 DRAININGEMCU063I 000005E9 3390 A 1248 15447 SATA 7200 RD1EMCU063I 000005EA 3390 A 1236 15459 SATA 7200 RD1EMCU064I Totals:EMCU064I For 3390: 2664 used tracks, 147591 free tracks, 2% usedEMCU001I GPM command complete

QUERY TASKS display examplesHere are three examples, one of QUERY TASKS when no explicit pool name is specified one when a pool name mask is specified and and one when the name is specified.

Example 1

When no pool name is specified, the display includes all background tasks on the Symmetrix system.

QUERY TASKS LCL(UNIT(1000)) Tasks on Controller 0001926-05093 API Ver: 7.50Task Type State Status MaxDelta Pool 0200 Rebalance Boot Completed 10 SHARE_ITCFK 0201 Rebalance Boot Completed 10 SHAREB_ITCFK 0202 Rebalance Boot Completed 25 SHARE_ITCFK 0203 Rebalance Boot Completed 25 SHAREB_ITCFK


Command Reference

Example 2

When a pool name mask is specified, the display includes all background tasks on the Symmetrix system whose target pool name matches the mask.

QUERY TASKS LCL(UNIT(1000)) POOL(SHARE_ITCFK) Tasks on Controller 0001926-05093 for Pool SHARE_ITCFK API Ver: 7.50Task Type State Status MaxDelta 0200 Rebalance Boot Completed 10 0202 Rebalance Boot Completed 25 0204 Rebalance Boot Completed 50 0228 Rebalance Boot Completed 50 022A Rebalance Boot Completed 25 022C Rebalance Boot Completed 50 022D Rebalance Boot Completed 25 022E Rebalance Boot Completed 25 022F Rebalance Boot Completed 25 0230 Rebalance Boot Completed 25

Example 3

When an explicit pool name is specified, the display includes background tasks acting on the specified pool.

QUERY TASKS LCL(UNIT(1000)) POOL(SHARE*) Tasks on Controller 0001926-05093 API Ver: 7.50Task Type State Status MaxDelta Pool 0200 Rebalance Boot Completed 10 SHARE_ITCFK 0201 Rebalance Boot Completed 10 SHAREB_ITCFK 0202 Rebalance Boot Completed 25 SHARE_ITCFK 0203 Rebalance Boot Completed 25 SHAREB_ITCFK

QUERY THINDEV display examplesHere are four examples, three of QUERY THINDEV when no explicit pool name is specified and two where the name is specified.

Example 1

When no pool name or pool name mask is specified and no device range is specified, all thin devices are displayed. Each report line includes the pool name and type to which the device is bound (or *Unbound* ).

EMCU500I QUERY THINDEV LCL(UNIT(2101)) EMCU184I Thin Devices on 0001956-00057 API Ver: 7.50EMCU108I Device# CUU Emul Volser Bound To Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000028 2100 3390 ****** MSFSTD N N 1113 SS N Bind DoneEMCU110I 00000029 2101 3390 ****** MSFSTD N N 1113 SS N Bind Done EMCU110I 0000002A 2102 3390 ****** MSFSTD Y N 1113 Y Compress Done . . .EMCU110I 000000DF **** 3390 ****** MFCKD1 Y N 1113 N Bind DoneEMCU110I 000000E0 **** 3390 ****** MFCKD1 Y N 1113 R2 N Bind Done EMCU110I 000000E1 **** 3390 ****** MFCKD1 Y N 1113 R2 N Bind Done . . . EMCU110I 00000106 **** 3390 ****** MFSQAR1 Y N 1113 R21 N Bind Done EMCU110I 00000107 **** 3390 ****** MFSQAR1 Y N 1113 R21 N Bind Done EMCU110I 00000108 **** 3390 ****** *Unbound N N 1113 N Unbind Done . . .EMCU110I 00000229 21B1 3390 ****** MSFBCV N N 1113 BT N Bind Done EMCU110I 0000022A 21B2 3390 ****** *Unbound N N 1113 BC N Unbind Done . . .EMCU110I 00000C1A **** FBA ****** STORRECLAIM Y N 8739 R1 N Bind Done EMCU110I 00000C1B **** FBA ****** STORRECLAIM Y N 8739 R1 N Bind Done EMCU110I 00000C1C **** FBA ****** STORRECLAIM Y N 8739 Y Compress Done EMCU110I 00000C1D **** FBA ****** STORRECLAIM Y N 8739 Y Compress Done EMCU110I 00000C1E **** FBA ****** STORRECLAIM Y N 8739 Y Compress Done EMCU110I 00000C1F **** FBA ****** STORRECLAIM Y N 8739 Y Compress Done EMCU110I 00000C21 **** FBA ****** *Unbound N N 2185 NEMCU110I 00000C25 **** FBA ****** *Unbound N N 10923 N EMCU071I Device Totals: CKD Bound: 16 Unbound: 792 FBA Bound: 0 Unbound: 564EMCU071I Track Totals: CKD Bound: 267120 Unbound: 44609040 FBA Bound: 0 Unbound: 73797000EMCU001I GPM command complete


Command Reference

Example 2

When no pool name or pool name mask is specified but a device range is specified, the display includes only thin devices in the specified device range.

EMCU500I QUERY THINDEV DEV(0090-0093) LCL(UNIT(2101)) EMCU184I Thin Devices on 0001956-00057 API Ver: 7.50EMCU108I Device# CUU Emul Volser Bound To Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000090 2168 3390 UOD090 DTTHINPOOL1 Y N 1113 Y Compress DoneEMCU110I 00000091 2169 3390 UOD091 DTTHINPOOL1 Y N 1113 Y Compress DoneEMCU110I 00000092 216A 3390 ****** DTTHINPOOL1 Y N 1113 N Decompress DoneEMCU110I 00000093 216B 3390 ****** DTTHINPOOL1 Y N 1113 N Bind DoneEMCU071I Device Totals: CKD Bound: 4 Unbound: 000000 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 66780 Unbound: 000000 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete

Example 3

When an explicit thin pool name is specified and no device range is specified, the display includes all devices bound to the specified pool. The pool name is included in the report header and is not shown in the report device lines.

EMCU500I QUERY THINDEV LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU184I Thin Devices on 0001956-00057 Bound to Pool DTTHINPOOL1 API Ver: 7.50EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000090 2168 3390 UOD090 Y N 1113 Y Compress DoneEMCU110I 00000091 2169 3390 UOD091 Y N 1113 Y Compress Done EMCU110I 00000092 216A 3390 ****** Y N 1113 N Decompress DoneEMCU110I 00000093 216B 3390 ****** Y N 1113 N Bind DoneEMCU071I Device Totals: CKD Bound: 4 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 66780 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete

Example 4

When both an explicit thin pool name and a device range are specified, the display includes only thin devices both bound to the specified pool and in the specified device range.

EMCU500I QUERY THINDEV DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU184I Thin Devices on 0001956-00057 Bound to Pool DTTHINPOOL1 API Ver: 7.50EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000091 2169 3390 UOD091 Y N 1113 Y Compress DoneEMCU110I 00000092 216A 3390 ****** Y N 1113 N Decompress DoneEMCU110I 00000093 216B 3390 ****** Y N 1113 N Bind DoneEMCU071I Device Totals: CKD Bound: 3 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 50085 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.


Command Reference

REBALANCE

DescriptionREBALANCE is used to initiate a rebalancing action against the devices in a thin pool. Previously set pool attributes may be allowed to govern the rebalancing operation, or you can specifiy new parameters that only apply to the current operation.

Rebalancing moves tracks among devices so as to approximately equalize the percentage of allocated tracks on all active devices in the pool.

Note: Inactive devices do not participate in rebalancing operations.

The active devices are considered balanced and the operation complete when, among these devices, the percentages of tracks allocated on any two devices do not differ by more than one percent more than the specified or default variance value.

REBALANCE will fail completely when:





SyntaxREBALANCE{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


POOL(poolname)[VARIANCE(variance-value)][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]

Parameters








Command Reference




POOL(poolname)

This required parameter specifies the pool where the devices are rebalanced.

VARIANCE(variance)

This optional parameter specifies the goal to be achieved by the rebalancing operation, the maximum difference in usage between the most heavily utilized and the least heavily utilized data devices based on current device usage statistics. The usage of a data device is an aggregate of the usage of the extents assigned to the device. The range is 1 - 50% and the default variance is 1%.

[NOEXEC]






PATH Specifies the path to reach the Symmetrix system where the devices are to be rebalanced. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[DEBUG]
















Command Reference

[VERBOSE]




Command Reference

REBIND

DescriptionREBIND allows you to change the pool where a thin device is bound without loss of data. The tracks allocated to the device in the source pool are retained. Following completion of the rebind action, subsequent track allocations are made from the target pool.

Note: Because the source pool is not specified, but is determined from the device, specification of a range of devices in the command can bind devices currently bound to different pools to a single pool.

REBIND will fail completely when:







◆ The REBIND validation fails for a device and SKIP has not been specified.

REBIND will fail for a device when:

◆ The device is not currently bound to a pool.

◆ The characteristics of the device to be rebound are not compatible with the characteristics of the specified pool.


◆ Rebinding that device would cause the oversubscription rate (for Enginuity levels 5874 and higher) of the target pool to exceed the maximum oversubscription rate of the pool set the by the user.





Command Reference




SyntaxREBIND{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)



Parameters












Command Reference



This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be rebound.

POOL(pool-name)

This required parameter specifies the name of the pool where the device(s) are rebound.

[SKIP]

This optional parameter allows ineligible devices to be skipped, rather than terminating the action. It allows specification of a device range that includes both inactive bound devices whose device characteristics are compatible with the specified pool and other devices.

[NOEXEC]



[DEBUG]



PATH Specifies the path to reach the Symmetrix system where the devices are rebound. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference














[VERBOSE]




Command Reference

REMOVE

DescriptionREMOVE removes one or more back-end (data or save) devices from a pool. The device(s) must in an inactive state and may not have allocated tracks.

REMOVE will fail completely when:

◆ A pool is specified and the specified pool cannot be found.




◆ The REMOVE validation fails for a device and SKIP has not been specified.

REMOVE will fail for a device when:

◆ A pool is specified and the device is not in the specified pool.

◆ The device has allocated tracks.

◆ The device is active.

SyntaxREMOVE{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


POOL(poolname)DEV(device|range|list)[SKIP][NOEXEC][DEBUG][VERBOSE]

Parameters








Command Reference




POOL

This required parameter specifies the pool where the specified devices are removed.


This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be removed from the specified pool.

[SKIP]

This optional parameter allowS ineligible devices to be skipped rather than terminating the action. It can be used in conjunction with the POOL parameter to allow specification of a device range that includes both inactive devices with no allocated tracks bound to the specified pool and other devices that do not satisfy these requirements.

[NOEXEC]






PATH Specifies the path to reach the Symmetrix system from where the devices are to be removed. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[DEBUG]



[VERBOSE]




Command Reference

RENAME

DescriptionRENAME changes the external (user-recognized) name of a pool. Other pool attributes, the devices assigned to the pool, their state and their allocations remain unchanged.

RENAME will fail completely when:


◆ A valid existing pool name is not supplied (via the POOL parameter).

◆ A valid new pool name is not supplied (via the NEWNAME parameter).

◆ The specified new pool name does not adhere to pool name requirements.

◆ A pool of the same name as the specified new pool name already exists on the Symmetrix system.



SyntaxRENAME{LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


POOL(current-pool-name)NEWNAME(new-pool-name)[NOEXEC][DEBUG][VERBOSE]

Parameters











Command Reference


POOL(current-pool-name)

This required parameter specifies the current name of the pool to be renamed.


NEWNAME(new-pool-name)

This required parameter specifies the new name of the pool. Refer to the poolname description described for the POOL (current-pool-name) parameter.

[NOEXEC]



[DEBUG]





PATH Specifies the path to reach the Symmetrix system where the pool to be renamed resides. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[VERBOSE]




Command Reference

UNBIND

DescriptionUNBIND terminates the relationship between a thin device and the pool to which it is bound. Any tracks allocated to devices in the pool on behalf of a device being unbound are freed.

Using this command results in data loss for the devices being unbound. Please ensure that the data is no longer needed for these devices before using this command.

UNBIND will fail completely when:




◆ The UNBIND validation fails for a device and SKIP has not been specified.



UNBIND will fail for a device when:

◆ The device is not bound to the specified pool .

◆ The device is both mapped and in a ready state.


◆ The device is online to any host.

◆ The device is a Snap source or target device.

◆ The device is in an RDF relationship.

◆ The device is in a PPRC relationship.

◆ The device has an XRC session.

SyntaxUNBIND {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[SKIP][NOCHKO][NOEXEC][DEBUG][WAIT(value,WARN|ERROR))][VERBOSE]


Command Reference

Parameters








This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, to be unbound from the specified pool.

POOL(poolname)

This required parameter specifies the name of the pool from which the specified thin devices are to be unbound.







PATH Specifies the path to reach the Symmetrix system where the devices are to be unbound. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[SKIP]

This optional parameter allows ineligible devices to be skipped rather than terminating the action. It can be used in conjunction with the POOL parameter to specify a device range that includes thin unready devices bound to the specified pool and other devices that do not meet these requirements.

[NOCHKO]

This optional parameter causes devices with online paths to be processed, when they would otherwise be declared ineligible for the action.

[NOEXEC]



[DEBUG]











Command Reference






[VERBOSE]




Command Reference

USR_NRDY

DescriptionThis action corresponds to the Host Component SC VOL USR_NRDY action. It sets the control unit status of a device to user-not-ready. This allows a thin device to be unbound.

USR_NRDY will fail completely when

◆ The USR_NRDY validation fails for a device and SKIP has not been specified.



USR_NRDY will fail for a device if:

◆ The device is not a thin bound device.

◆ A pool was specified and the device is not a thin device bound to that pool.


◆ The device is online to any host.

SyntaxUSR_NRDY {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[SKIP][NOCHKO][NOEXEC][DEBUG][VERBOSE]

Parameters








Command Reference





This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, where the control unit status is set to user not ready.

POOL(poolname)

This optional parameter specifies the name of the pool where devices are bound in order to be eligible for processing.

SKIP


[NOCHKO]

This optional parameter causes devices with online paths to be processed, when they would otherwise be declared ineligible for the action.

[NOEXEC]





PATH Specifies the path to reach the Symmetrix system where the devices to be set reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference


[DEBUG]



[VERBOSE]




Command Reference

USR_RDY

DescriptionThis action corresponds to the Host Component SC VOL USR_RDY action. It sets the control unit status of a device to user-ready. This allows a thin bound device to be set active.

USR_RDY will fail completely when

◆ The USR_RDY validation fails for a device and SKIP has not been specified.



USR_RDY will fail for a device if:

◆ The device is not a thin bound device.

◆ A pool was specified and the device is not a thin device bound to that pool.


SyntaxUSR_RDY {LOCAL|LCL}(UNIT(device)|VOLume(volser)|DDNAME(ddname))|{REMOTE|RMT}(UNIT(device)|VOLume(volser)|DDNAME(ddname)


DEV(device|range|list)POOL(poolname)[SKIP][NOEXEC][DEBUG][VERBOSE]

Parameters








Command Reference





This parameter specifies the Symmetrix device number, range of Symmetrix device numbers separated by a dash, or list of Symmetrix device numbers and/or ranges separated by commas, where the control unit status is set to user ready.

POOL(poolname)

This optional parameter specifies the name of the pool where devices are bound in order to be eligible for processing.

[SKIP]


[NOEXEC]






PATH Specifies the path to reach the Symmetrix system where the devices to be set reside. The value can be a single SRDF group or a list of up to eight group identifiers, separated by periods.





Command Reference

[DEBUG]



[VERBOSE]




Command Reference

Recovery services commandsThe recovery services commands allow you to perform recovery on local or remote devices.

REC,QUERYDEVICELOCK

Queries and displays the current device lock setting.

Syntax

F emcscf,REC,QRYDLOCK,lockname,cuu[,count][,LCL,symdv#|,RMT,symdv#,rdfgroup|RMT(symdv#,rdfgroup)]

Note: RMT(symdv#,rdfgroup) is the preferred syntax for the remote parameter.

Parameters

lockname

Valid lockname keywords are TF, SNAP, and COPY.

cuu

Specifies the z/OS device number.

count

Specifies the number of devices (consecutive, starting with the cuu). count is required if LCL or RMT is specified.

LCL

Specifies that the action affects local devices specified by the Symmetrix device number (sym#bcv and sym#std).

symdv#

Specifies the Symmetrix device number. This must be a 4-digit value.

RMT

Specifies that the establish affects remote devices in an SRDF configuration.

rdfgroup

Specifies the SRDF group through which you want to perform a remote operation. This must be a 1 or 2-digit value representing the SRDF group.

ExampleF EMCSCF,REC,QRYDLOCK,TF,DE20,3,RMT,1CC,06 SCF0721I REC,QRYDLOCK,TF,DE20,3,RMT,1CC,06 SCF0723I REC DEVICE 01CC IS LOCKED, LOCKID X'0299304B', DURATION 271SCF0723I REC DEVICE 01CD IS LOCKED, LOCKID X'0299304B', DURATION 271SCF0723I REC DEVICE 01CE IS LOCKED, LOCKID X'0299304B', DURATION 271SCF0726I REC COMPLETED

The following example shows the RMT format using a multi-hop list:

F EMCSCF,REC,QRYDLOCK,TF,3090,1,RMT(0090,1.4.5)

Recovery services commands 309

Command Reference

REC,RELEASEDEVICELOCK

Releases the device lock.

Syntax

F emcscf,REC,RELDLOCK,lockname,cuu[,count][,LCL,symdv#|,RMT,symdv#,rdfgroup|RMT(symdv#,rdfgroup)]

Note: RMT(symdv#,rdfgroup) is the preferred syntax for the remote parameter.

Parameters

lockname

Valid lockname keywords are TF, SNAP, and COPY.

cuu


count

Specifies the number of devices (consecutive, starting with the cuu). count is required if LCL or RMT is specified.

LCL

Specifies that the action affects local devices specified by the Symmetrix device number (sym#bcv and sym#std).

symdv#

Specifies the Symmetrix device number. This must be a 4-digit value.

RMT

Specifies that the establish affects remote devices in an SRDF configuration.

rdfgroup

Specifies the SRDF group through which you want to perform a remote operation. This must be a 1 or 2-digit value representing the SRDF group.

ExampleF EMCSCF,REC,RELDLOCK,TF,DE20,3,RMT,1CC,06 SCF0721I REC,RELDLOCK,TF,DE20,3,RMT,1CC,06 SCF0723I REC DEVICE 01CC IS RELEASED, LOCKID X'0299304B', DURATION 273SCF0723I REC DEVICE 01CD IS RELEASED, LOCKID X'0299304B', DURATION 273SCF0723I REC DEVICE 01CE IS RELEASED, LOCKID X'0299304B', DURATION 273

SCF0726I REC COMPLETED


Command Reference

SRDF/AR: Symmetrix Automated Replication commandsThe Symmetrix Automated Replication (SRDF/AR) commands allow you to control the SRDF/AR process. SRDF/AR allows you to ensure data consistency across geographic distances.

SAR,PAUSE

The PAUSE command causes a SRDF/AR process to pause and issue the following message:

*nn BCVA058A Process process_name, Paused in Step nn (reason)- reply CONTinue or CANcel

An Immediate Pause will occur just before the next API call. A Step-level Pause will occur before the next API call for the desired step.

Either type of pause will be deferred during the Consistent Split phase to prevent impacting the Consistent Split, possibly causing a loss of consistency for the affected cycle. For example, an Immediate Pause issued during the Consistent Split phase of Step 02 will be deferred until the Consistent Split processing has completed (Step 03).

You can schedule a pause to take effect for a step in the SRDF/AR process by specifying that step number with the PAUSE command.

Note: The EMC TimeFinder/Mirror for z/OS Product Guide provides more information about SRDF/AR.

Syntax

F emcscf,SAR,PAUSE{(step#)},process_name

Parameters

step#

The step number.

process_name

The name of the SRDF/AR process.

Example

F EMCSCF,SAR,PAUSE(2),LRSAR1 SCF0701I SAR,PAUSE(2),LRSAR1 <PAG 8 |UIC 540 |IO/S 0 |IOP 0 |CPU 3 > 92 BCVA058A Process LRSAR1, Paused in Step 02 (request) - reply CONTinue or CANcel

SRDF/AR: Symmetrix Automated Replication commands 311

Command Reference

SAR,START

Starts the SRDF/AR process process_name.

Syntax

F emcscf,SAR,START,process_name

Parameters

process_name


ExampleF EMCSCF,SAR,START,LRSAR1SCF0701I SAR,START,LRSAR1 SCF0702I SAR START COMMAND ACCEPTED. SCF0710I SAR PROCESS LRSAR1 STARTED

SAR,RESTART

Restarts the SRDF/AR process process_name.

Syntax

F emcscf,SAR,RESTART,process_name

Parameters

process_name


ExampleF EMCSCF,SAR,RESTART,LRSAR1 SCF0701I SAR,RESTART,LRSAR1 SCF0702I SAR RESTART COMMAND ACCEPTED.SCF0710I SAR PROCESS LRSAR1 STARTED

SAR,STOP

Stops the SRDF/AR process process_name.

You can schedule a stop to take effect for a step in the SRDF/AR process by specifying that step number on the STOP.

Note: The EMC TimeFinder/Mirror for z/OS Product Guide provides more information about SRDF/AR.

Syntax

F emcscf,SAR,STOP,process_name,stop_type

Parameters

process_name



Command Reference

stop_type

Valid types are:

ExampleF EMCSCF,SAR,STOP,LRSAR1,IMMED SCF0701I SAR,STOP,LRSAR1,IMMED BCVA042I Process LRSAR1 interrupted (STOP IMMED) SCF0711I SAR PROCESS LRSAR1 ENDED

NORMAL Stop the specified process at the completion of the current cycle.

STEP Stop the specified process at the completion of the current step.

For a stop_type of STEP, an optional step number can be specified:

STEP{(step#)}

FORCE Stop the specified process unconditionally.

IMMEDiate Stop the specified process immediately.

SRDF/AR: Symmetrix Automated Replication commands 313

Command Reference

SRV SYSBUSY commandsThe SRV SYSBUSY commands are used to control the SYSBUSY condition within the SRV environment for EMCSCF.

SRV,SYSBUSY,HELP

Displays the help information for the SRV,SYSBUSY command.

Syntax

F scftaskname,SRV,SysBusy,HELP

Parameters None.

Example F EMCSCF,SYSBUSY,HELPSRV,SYSBUSY - Provides external control for SYSBUSY.........

SRV,SYSBUSY,DISPLAY

Displays the number of external applications that currently require SCF to remain active.

Syntax

F scftaskname,SRV,SysBusy,DISplay

Parameters None.

Example F EMCSCF,SYSBUSY,DISPLAYSRV environment has 2 active task(s)

SRV,SYSBUSY,DECREMENT

Decrements the number of external applications that currently require SCF to remain active.

Syntax

F scftaskname,SRV,SysBusy,DECRement

Parameters None.

Example F EMCSCF,SYSBUSY,DECREMENTSRV active task count changed from 2 to 1


Command Reference

SRV.SYSBUSY,RESET

Resets the number of external applications that currently require SCF to remain active.

Syntax

F scftaskname,SRV,SysBusy,RESet

Parameters None.

Example F EMCSCF,SYSBUSY,RESETSRV active task count changed from 2 to 0

SRV SYSBUSY commands 315

Command Reference

SRDF/A Multi-Session Consistency commandsSRDF/A multi-session consistency (MSC) is an environment in EMCSCF that ensures remote R2 consistency across multiple Symmetrix systems running SRDF/A. The SRDF/A Multi-Session Consistency (MSC) commands allow you to query and control the MSC process.

SRDF/A sessions can be grouped together as a single entity called an MSC group. Starting with SRDF Host Component V7.2, you can define up to eight MSC groups with the MSC_GROUP_NAME parameter. If you enable the SCF MSC environment by setting SCF.MSC.ENABLE=YES or issuing F emcscf,MSC ENABLE, the MSC parameters are validated during SRDF Host Component initialization. The parameters can also be validated as the result of issuing a Host Component #SC GLOBAL PARM_REFRESH command.

If an MSC error is detected during validation, the MSC definition will remain, but MSC will not be allowed to start until the error is corrected and an #SC GLOBAL PARM_REFRESH is issued. If you have defined two or more MSC groups, none of them will automatically start. You must start each MSC group individually using the #SC GLOBAL PARM_REFRESH command.

Once the MSC groups are active, all processing is under the control of the SCF MSC environment and no further interaction is required with SRDF Host Component.

MSC,ADDDEV

Use this command to explicitly initiate SRDF/Star dynamic device add operations.

Note: MSC,ADDDEV will be deferred if an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC ADDDEV [,SESSion(ccuu,[sync_ra,]async_ra)][,MSCGroup(msc_group)]

Parameters

SESSion

Optional. When this command is issued without the SESSion parameter, MSC will initiate device add processing for all MSC sessions (a session is specified by the SRDF Host Component MSC_INCLUDE_SESSION statement). When SESSion is specified, add processing is initiated for that session only, where:

• ccuu specifies the z/OS device number.

• sync_ra (optional) specifies the synchronous SRDF group in cascaded MSC/Star environments.

• async_ra specifies the asynchronous SRDF group. The SRDF group number is a one- or two-digit hex value.

MSCGroup

Optional. Use this parameter to specify multiple MSC groups, where msc_group specifies the group. You can specify up to 8 groups, one at a time.


Command Reference

ExampleF EMCSCF,MSC,ADDDEV,SESS(850F,F0)SCF1390I MSC,ADDDEV,SESS(850F,F0) SCF1391I MSC - ADD COMMAND ACCEPTED. SCF15CCI MSC - GROUP=EMC_STAR (850F,F0) Add processing initiatedSCF15CFI MSC - GROUP=EMC_STAR (850F,F0) Adding device (02B2/01B2/0180)SCF15CFI MSC - GROUP=EMC_STAR (850F,F0) Adding device (02B3/01B3/0181)SCF15CFI MSC - GROUP=EMC_STAR (850F,F0) Adding device (02B4/01B4/0182)SCF15CDI MSC - GROUP=EMC_STAR (850F,F0) Add processing completed

MSC,DEACT

This command causes one MSC server in a high availability MSC environment to deactivate itself. That is, the MSC server will no longer be associated (or do cycle switching) with the MSC groups. However, the other MSC servers will continue to be associated with the MSC groups.

If you issue this command and no other MSC server exists that is cycle switching for the MSC groups, you can have SRDF groups in MSC but no server that is cycle switching.

Note: MSC,DEACT is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACT[,MSCGroup(msc_group|*)][,RETAIN]

Parameters

MSCGroup

Optional. Use this parameter to specify multiple MSC groups to deactivate, where:

• msc_group specifies the group to deactivate. You can specify up to 8 groups, one at a time.

• * (asterisk) deactivates all the defined MSC groups.

RETAIN

Optional. For a planned failover, an MSC DEACT command can be issued to deactivate the primary MSC server. Since this action removes the control blocks, you cannot restart MSC without first issuing an SRDF Host Component GLOBAL PARM_REFRESH command. However, if you specify the RETAIN parameter with MSC DEACT, MSC can be restarted as a secondary server via a RESTARTTOSEC command.

Note: The primary server is the server running with MSC_WEIGHT_FACTOR = 0. The secondary server runs on a different LPAR from the primary server at the primary site (site A).

SRDF/A Multi-Session Consistency commands 317

Command Reference

ExamplesExample 1 F EMCSCF,MSC,DEACT

SCF1390I MSC,DEACT SCF1391I MSC - DEACT COMMAND ACCEPTED. 59 SCF1471R MSC - GROUP=LRMSC NO OTHER SERVER FOUND - CONTINUE,

DISABLE, OR CANCEL R 59,CONTINUE IEE600I REPLY TO 59 IS;CONTINUE SCF1572I MSC - GROUP=LRMSC DEACT CONTINUES SCF1435I MSC - GROUP=LRMSC (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC (DE2F,70) FREEING SEL LOCKS SCF1376I MSC - GROUP=LRMSC (DE2E,06) SYMMETRIX TASK EDED SCF1376I MSC - GROUP=LRMSC (DE2F,70) SYMMETRIX TASK ENDED SCF1435I MSC - GROUP=LRMSC (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC (DE2F,70) FREEING SEL LOCKS SCF1333I MSC - GROUP=LRMSC MOTHER TASK ENDED SCF1321I MSC - TASK DISABLED

Example 2

SCF1390I MSC,DEACT,MSCG(PROD_MSC2) *56 SCF1471R MSC - GROUP=PROD_MSC2 NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCEL SCF1391I MSC - DEACT COMMAND ACCEPTED. R 56,CONTINUE SCF1572I MSC - GROUP=PROD_MSC2 DEACT CONTINUES SCF15AAI MSC - GROUP=PROD_MSC2 DEACT complete

MSC,DEACTREFRESH

Use this command when you want to stop this MSC server from cycle switching and make the server ready for another MSC group.

This command is similar to the REFRESH command except that it performs an F SCFNAME,MSC,DEACT instead of an F SCFNAME,MSC,DISABLE.

Note: MSC,DEACTREFRESH is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTREFresh[,MSCGroup(msc_group|*)]

Parameters

MSCGroup

Optional. Use this parameter to specify multiple MSC groups, where:

• msc_group specifies the group. You can specify up to 8 groups, one at a time.

• * (asterisk) selects all the defined MSC groups.


Command Reference

ExamplesExample 1

F EMCSCF,MSC,DEACTREFRESH SCF1390I MSC,DEACTREFRESH SCF1391I MSC - DEACTREFRESH COMMAND ACCEPTED. 20 SCF1471R MSC - GROUP=LRMSC..................NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCELR 20,CONTINUE SCF1572I MSC - GROUP=LRMSC.................... DEACTREFRESH CONTINUES SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1376I MSC - GROUP=LRMSC.................... (DE2E,06) SYMMETRIX TASK ENDED SCF1376I MSC - GROUP=LRMSC.................... (DE2F,70) SYMMETRIX TASK ENDED SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1333I MSC - GROUP=LRMSC.................... MOTHER TASK ENDED SCF1321I MSC - TASK DISABLED SCF1320I MSC - TASK ENABLED

Example 2 This example specifies an MSC group. Note that after the command completes, the MSC group definition is removed.

SCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=2 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 ACTIVE MSC(CAS) WF=2 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I DB_ACCT_LVMSC3 ACTIVE MSC WF=2 SCF1601I (82DF,E1) 0001926-00215 0001926-00290 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=2 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete SCF1390I MSC,DEACTREFRESH,MSCG(DB_ACCT_LVMSC3) SCF1391I MSC - DEACTREFRESH COMMAND ACCEPTED. *05 SCF1471R MSC - GROUP=DB_ACCT_LVMSC3 NO OTHER SERVER FOUND - CON R 05,CONTINUE SCF1572I MSC - GROUP=DB_ACCT_LVMSC3 DEACTREFRESH CONTINUES SCF15AAI MSC - GROUP=DB_ACCT_LVMSC3 DEACT complete SCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=2 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 ACTIVE MSC(CAS) WF=2 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=2 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete


Command Reference

MSC,DEACTRESTART

Use this command when you want to stop this MSC server from cycle switching and then restart cycle switching for the same MSC group.

This command is similar to the RESTART command except that it performs an F SCFNAME,MSC,DEACT instead of an F SCFNAME,MSC,DISABLE.

Note: MSC,DEACTRESTART is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTREStart[,MSCGroup(msc_group)]

Parameters

MSCGroup


Examples

Example 1F EMCSCF,MSC,DEACTRESTARTSCF1390I MSC,DEACTRESTART SCF1391I MSC - DEACTRESTART COMMAND ACCEPTED. 45 SCF1471R MSC - GROUP=LRMSC.................... NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCELR 45,CONTINUE SCF1572I MSC - GROUP=LRMSC.................... DEACTRESTART CONTINUES SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1376I MSC - GROUP=LRMSC.................... (DE2F,70) SYMMETRIX TASK ENDED SCF1376I MSC - GROUP=LRMSC.................... (DE2E,06) SYMMETRIX TASK ENDED SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1333I MSC - GROUP=LRMSC.................... MOTHER TASK ENDED SCF1321I MSC - TASK DISABLED SCF1320I MSC - TASK ENABLED SCF1304I MSC - SRDF HC POST SCF1568I MSC - GROUP=LRMSC.................... WEIGHT FACTOR = 0 SCF1335E MSC - GROUP=LRMSC.................... MOTHER TASK STARTED SCF1328I MSC - GROUP=LRMSC.................... (DE2E,06) SRDFA ACTIVE SCF1326I MSC - GROUP=LRMSC.................... (DE2E,06) SERIAL = 000190300097 SCF1328I MSC - GROUP=LRMSC.................... (DE2F,70) SRDFA ACTIVE ETC ETC


Command Reference

Example 2F EMCSCF,MSC,DEACTRESTART,MSCG(TEST_MSC1) SCF1390I MSC,DEACTRESTART,MSCG(TEST_MSC1) 66 SCF1471R MSC - GROUP=TEST_MSC1 NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCELSCF1391I MSC - DEACTRESTART COMMAND ACCEPTED. R 66,CONTINUE SCF1572I MSC - GROUP=TEST_MSC1 DEACTRESTART CONTINUES SCF1571I MSC - GROUP=EMC_STAR CYCLE SWITCH BACK LEVEL SCF15AAI MSC - GROUP=TEST_MSC1 DEACT completeSCF15AAI MSC - GROUP=TEST_MSC1 DEACT complete SCF1304I MSC - SRDF HC POST SCF1323I MSC - ALLOW OVERWRITE OF SCRATCH AREA AND BOXLIST SCF1322I MSC - AUTO RECOVERY ENABLED SCF1568I MSC - GROUP=TEST_MSC1 WEIGHT FACTOR = 2 SCF1366I MSC - GROUP=TEST_MSC1 (855F,F1,52) Remote Cycle SwitchingSCF1366I MSC - GROUP=TEST_MSC1 (7A4F,80,09) Remote Cycle SwitchingSCF1569I MSC - GROUP=TEST_MSC1 STEAL LOCK AFTER = 2 MIN(S) SCF1452I MSC - GROUP=TEST_MSC1 (855F,F1,52) EXISTING DEFINITION MATCHSCF1452I MSC - GROUP=TEST_MSC1 (7A4F,80,09) EXISTING DEFINITION MATCHSCF1451I MSC - GROUP=TEST_MSC1 EXISTING DEFINITION MATCH SCF1342I MSC - GROUP=TEST_MSC1 PROCESS_FC03-ALL BOXES ACTIVE SCF1564I MSC - GROUP=TEST_MSC1 TIME OF DAY FOR CYCLE 0000000D IS 12:31:40.33

MSC,DEACTRESTARTTOSEC

Use this command to restart the previous primary server as a secondary server, running with MSC_WEIGHT_FACTOR = 2.

Syntax

F emcscf,MSC,DEACTRESTARTTOSEC[,MSCGroup(msc_group)]

Parameters

MSCGroup


Note: MSC,DEACTRESTARTTOSEC is not allowed while an MSC,TAKEOVER operation is in progress.

ExampleSCF1390I MSC,DEACTRESTARTTOSEC,MSCG(EMC_STAR)SCF1391I MSC - DEACTRESTARTTOSEC COMMAND ACCEPTED.*78 SCF1471R MSC - GROUP=EMC_STAR NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCELR 78,CONTINUESCF1572I MSC - GROUP=EMC_STAR DEACTRESTARTTOSEC CONTINUESSCF15AAI MSC - GROUP=EMC_STAR DEACT completeSCF1323I MSC - ALLOW OVERWRITE OF SCRATCH AREA AND BOXLISTSCF1316I MSC - STAR SDDF QUERY TO DASCF1568I MSC - GROUP=EMC_STAR WEIGHT FACTOR = 2SCF1569I MSC - GROUP=EMC_STAR STEAL LOCK AFTER = 5 MIN(S)SCF1452I MSC - GROUP=EMC_STAR (08503,7A) EXISTING DEFINITION MATCHSCF1452I MSC - GROUP=EMC_STAR (08504,7C) EXISTING DEFINITION MATCHSCF1452I MSC - GROUP=EMC_STAR (08505,7E) EXISTING DEFINITION MATCHSCF1451I MSC - GROUP=EMC_STAR EXISTING DEFINITION MATCH


Command Reference

SCF1342I MSC - GROUP=EMC_STAR PROCESS_FC03-ALL BOXES ACTIVESCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 0000022B IS 11:23:30.62SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 0000022C IS 11:23:47.00SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 0000022D IS 11:24:04.01

MSC,DEACTRESTARTTOZERO

Use this command to allow the MSC server running at MSC_WEIGHT_FACTOR > 0 to be deactivated and restarted with MSC_WEIGHT_FACTOR = 0. In an SRDF/Star environment, the SDDF work will be taken over by this server.

Note: This command should only be used when there is not another MSC server running at MSC_WEIGHT_FACTOR = 0.

Note: MSC,DEACTRESTARTTOZERO is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTRESTARTTOZERO[,MSCGroup(msc_group)]

Parameters

MSCGroup


ExamplesExample 1

F EMCSCF,MSC,DEACTRESTARTTOZEROSCF1390I MSC,DEACTRESTARTTOZERO SCF1391I MSC - DEACTRESTARTTOZERO COMMAND ACCEPTED. 51 SCF1471R MSC - GROUP=LRMSC.................... NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCELR 51,CONTINUE SCF1572I MSC - GROUP=LRMSC.................... DEACTRESTARTZERO CONTINUES SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1376I MSC - GROUP=LRMSC.................... (DE2E,06) SYMMETRIX TASK ENDED SCF1376I MSC - GROUP=LRMSC.................... (DE2F,70) SYMMETRIX TASK ENDED SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1333I MSC - GROUP=LRMSC.................... MOTHER TASK ENDED SCF1321I MSC - TASK DISABLED SCF1320I MSC - TASK ENABLED SCF1304I MSC - SRDF HC POST SCF1568I MSC - GROUP=LRMSC.................... WEIGHT FACTOR = 0 SCF1335E MSC - GROUP=LRMSC.................... MOTHER TASK STARTED SCF1328I MSC - GROUP=LRMSC.................... (DE2E,06) SRDFA ACTIVE SCF1326I MSC - GROUP=LRMSC.................... (DE2E,06) SERIAL = 000190300097SCF1328I MSC - GROUP=LRMSC.................... (DE2F,70) SRDFA ACTIVE SCF1569I MSC - GROUP=LRMSC.................... STEAL LOCK AFTER = 120 MIN(S) SCF1326I MSC - GROUP=LRMSC.................... (DE2F,70) SERIAL = 000190300097ETC ETC

Example 2

F EMCSCF,MSC,DEACTRESTARTTOZERO,MSCG(TEST_MSC1)


Command Reference

SCF1390I MSC,DEACTRESTARTTOZERO,MSCG(TEST_MSC1) SCF1391I MSC - DEACTRESTARTTOZERO COMMAND ACCEPTED. 68 SCF1471R MSC - GROUP=TEST_MSC1 NO OTHER SERVER FOUND - CONTINUE, DISABLE, OR CANCELSCF1564I MSC - GROUP=TEST_MSC1 TIME OF DAY FOR CYCLE 00000018 I S 12:36:42.05R 68,CONTINUE SCF1572I MSC - GROUP=TEST_MSC1 DEACTRESTARTZERO CONTINUES SCF1571I MSC - GROUP=DB_ACCT_LVMSC3 CYCLE SWITCH BACK LEVEL SCF1571I MSC - GROUP=EMC_STAR CYCLE SWITCH BACK LEVEL SCF15AAI MSC - GROUP=TEST_MSC1 DEACT complete SCF1304I MSC - SRDF HC POST SCF1323I MSC - ALLOW OVERWRITE OF SCRATCH AREA AND BOXLIST SCF1322I MSC - AUTO RECOVERY ENABLED SCF1568I MSC - GROUP=TEST_MSC1 WEIGHT FACTOR = 0 SCF1366I MSC - GROUP=TEST_MSC1 (855F,F1,52) Remote Cycle SwitchingSCF1366I MSC - GROUP=TEST_MSC1 (7A4F,80,09) Remote Cycle SwitchingSCF1569I MSC - GROUP=TEST_MSC1 STEAL LOCK AFTER = 2 MIN(S) SCF1452I MSC - GROUP=TEST_MSC1 (855F,F1,52) EXISTING DEFINITION MATCHSCF1452I MSC - GROUP=TEST_MSC1 (7A4F,80,09) EXISTING DEFINITION MATCHSCF1451I MSC - GROUP=TEST_MSC1 EXISTING DEFINITION MATCH SCF1342I MSC - GROUP=TEST_MSC1 PROCESS_FC03-ALL BOXES ACTIVE SCF1564I MSC - GROUP=TEST_MSC1 TIME OF DAY FOR CYCLE 00000019 IS 12:37:25.17

MSC,DELDEV

Use this command to explicitly initiate SRDF/Star dynamic device delete operations.

When you issue an MSC,DELDEV command, a search for deleted devices is initiated, either for all MSC SRDF groups or a specific SRDF group. Any deleted devices are found by comparing the current SRDF/Star configuration to the configuration that existed prior to the last successful deletion of devices. If no deleted devices are found, message SCF15D2I is issued and the delete processing terminates.

Note: MSC,DELDEV will be deferred if an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC DELDEV [,SESSion(ccuu,[sync_ra,]async_ra)][,MSCGroup(msc_group)]

Parameters

SESSion

Optional. When this command is issued without this SESSion parameter, MSC will initiate device delete processing for all MSC sessions (a session is specified by the SRDF Host Component MSC_INCLUDE_SESSION statement). When SESSion is specified, delete processing is initiated for that session only, where:

• ccuu specifies the z/OS device number.

• sync_ra (optional) specifies the synchronous SRDF group in cascaded MSC/Star environments.

• async_ra specifies the asynchronous SRDF group. The SRDF group number is a one- or two-digit hex value.

MSCGroup



Command Reference

ExampleF EMCSCF,MSC,DELDEV,SESS(850F,F0)SCF1390I MSC,DELDEV,SESS(850F,F0) SCF1391I MSC - DEL COMMAND ACCEPTED. SCF15CCI MSC - GROUP=EMC_STAR (850F,F0) Delete processing initiatedSCF15CFI MSC - GROUP=EMC_STAR (850F,F0) Deleting device (02B2/01B2/0180)SCF15CFI MSC - GROUP=EMC_STAR (850F,F0) Deleting device (02B3/01B3/0181)SCF15CFI MSC - GROUP=EMC_STAR (850F,F0) Deleting device (02B4/01B4/0182)SCF15CDI MSC - GROUP=EMC_STAR (850F,F0) Delete processing completed

MSC,DISABLE

Use this command to disable the MSC environment. When disabled, no SRDF Host Component MSC group definition will be processed. This is equivalent to the SCF.MSC.ENABLE=NO initialization parameter.

When multiple MSC groups are defined, an MSC,DISABLE for a specific MSC group will not delete the MSC definition. An MSC,DISABLE for all groups will delete the definition as well as disable the MSC environment.

Note: MSC,DISABLE is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DISAble[,MSCGroup(msc_group|*)]

Parameters

MSCGroup


• msc_group specifies the group to disable. You can specify up to 8 groups, one at a time.

• * (asterisk) disables all the defined MSC groups.

ExamplesExample 1 F EMCSCF,MSC,DISABLE

SCF1390I MSC,DISABLE SCF1391I MSC - DISABLE COMMAND ACCEPTED.SCF1321I MSC - TASK DISABLED

Example 2 This example specifies an MSC group to disable. Note that the MSC group definition is not deleted.

F EMCSCF,MSC,DISPLAYSCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=0 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 ACTIVE MSC(CAS) WF=0 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I DB_ACCT_LVMSC3 ACTIVE MSC WF=0 SCF1601I (82DF,E1) 0001926-00215 0001926-00290 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=0 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete


Command Reference

F EMCSCF,MSC,DISABLE,MSCG(DB_ACCT_LVMSC3) SCF1390I MSC,DISABLE,MSCG(DB_ACCT_LVMSC3) SCF1391I MSC - DISABLE COMMAND ACCEPTED. SCF1569I MSC - GROUP=DB_ACCT_LVMSC3 STEAL LOCK AFTER = 2 MIN(S)SCF15AAI MSC - GROUP=DB_ACCT_LVMSC3 DISABLE complete SCF15F4I MSC - Processing for DISABLE command complete

F EMCSCF,MSC,DISPLAY SCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=0 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 ACTIVE MSC(CAS) WF=0 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I DB_ACCT_LVMSC3 INACTIVE MSC WF=0 SCF1601I (82DF,E1) 0001926-00215 0001926-00290 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=0 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete

MSC,DISPLAY

Use this command to display the status of the MSC environment.

The MSC DISPLAY command displays additional information for each active MSC group when the MSC environment is enabled. This applies to MSC groups that are currently in an Active, Inactive, Deact, or Penddrop state.

Syntax

F emcscf,MSC,DISPLAY

ParametersNone.

ExampleF EMCSCF,MSC,DISPLAYSCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=0 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 PENDDROP MSC(CAS) WF=0 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I DB_ACCT_LVMSC3 ACTIVE MSC WF=0 SCF1601I (82DF,E1) 0001926-00215 0001926-00290 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=0 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete

Comments regarding SQARFor the MSC DISPLAY command, "SQAR" is now displayed for SQAR MSC groups. The Primary SQAR group, MSCGA (the A-C leg) is the ConGroup managed group and displays the ConGroup name.


Command Reference

The session information is similar to SRDF/Star; the first RDF group (displayed just after the gatekeeper) is the asynchronous group, the next RDF group is the recovery group, and the RDF group after the "/" is the synchronous group for the Primary SQAR (the synchronous link is A to B).

Because the configuration is “square”, rather than adding the serial numbers of the recovery R2 controller to each session, the R2 serial number displayed for the Primary SQAR is the R2 recovery controller for the partner session and vice versa.

The serial numbers are in the same sequence as MSC, except for the Primary SQAR, the third serial number represents the synchronous R2 controller.

SCF1390I MSC DISPLAYSCF1391I MSC - DISPLAY COMMAND ACCEPTED.SCF1320I MSC - TASK ENABLEDSCF1600I MSCGA INACTIVE SQAR WF=0 CGRPASCF1601I (03BBE,58),(49)/48 0001957-00086 0001957-00080 0001957-00079SCF1600I MSCGB INACTIVE SQAR WF=0SCF1601I (038BE,59),(48) 0001957-00079 0001956-00057SCF1602I MSC Display complete

MSC,ENABLE

Use this command to enable the MSC environment. MSC waits for a MSC group definition from SRDF Host Component. This is equivalent to the SCF.MSC.ENABLE=YES initialization parameter.

Syntax

F emcscf,MSC,ENAble

ParametersNone.

ExampleF EMCSCF,MSC,ENABLE SCF1390I MSC,ENABLE SCF1391I MSC - ENABLE COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED

MSC,PENDDROP

When this command is issued, it will wait until the end of the next cycle switch (the first) and issue an SRDF/A PENDDROP to each SRDF group in the MSC group. On the next cycle switch (the second), the code will perform the cycle switch and immediately drop. On the next+1 cycle switch (the third), the MSC server will determine that the SRDF groups in the MSC group are no longer SRDF/A active, thus invoking the DROP policy and perform cleanup.

Since all SRDF groups completed an SRDF/A PENDDROP, no R2 invalid tracks will be owed to the R1 after the MSC cleanup runs and then RDF-RSUM may be used instead of REFRESH / RFR-RSUM.

This command is similar to the SC SRDFA,DDDD,PEND_DROP command in the SRDF Host Component product, except the command is performed for all SRDF groups in the MSC groups.


Command Reference

Note: MSC,PENDDROP is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,PENDDrop[,MSCGroup(msc_group|*)]

Parameters

MSCGroup




ExamplesExample 1

F EMCSCF,MSC,PENDDROPMSC,PENDDROPSCF1391I MSC - PENDDROP COMMAND ACCEPTED.SCF1345I MSC - GROUP=LRMSC MOTHER TASK FUNCTION TIMERSCF1343I MSC - GROUP=LRMSC PROCESS_FC04-TIME FOR SWITCHSCF1382I MSC - GROUP=LRMSC (DE2F,70) PROCESS_FC04-CAN WE SWITCH?SCF1382I MSC - GROUP=LRMSC (DE2E,06) PROCESS_FC04-CAN WE SWITCH?SCF1344I MSC - GROUP=LRMSC PROCESS_FC05-ALL BOXES CAN SWITCHSCF1383I MSC - GROUP=LRMSC (DE2E,06) PROCESS_FC05-OPEN AND SWITCHSCF1383I MSC - GROUP=LRMSC (DE2F,70) PROCESS_FC05-OPEN AND SWITCHSCF1346I MSC - GROUP=LRMSC PROCESS_FC06-ALL BOXES OPENED WINDOW AND CYCLE SWITCHEDSCF1564I MSC - GROUP=LRMSC TIME OF DAY FOR CYCLE 00000003 IS 12:19:53.06SCF1384I MSC - GROUP=LRMSC (DE2E,06) PROCESS_FC06-CLOSE WINDOWSCF1384I MSC - GROUP=LRMSC (DE2F,70) PROCESS_FC06-CLOSE WINDOWSCF1521I MSC - GROUP=LRMSC (DE2F,70) PERFORM PEND_DROPSCF1521I MSC - GROUP=LRMSC (DE2E,06) PERFORM PEND_DROPSCF1347I MSC - GROUP=LRMSC PROCESS_FC07-ALL BOXES CLOSED WINDOWSCF1328I MSC - GROUP=LRMSC (DE2E,06) SRDFA ACTIVESCF1454I MSC - GROUP=LRMSC NEXT WAKE UP AT X'12245200'SCF1345I MSC - GROUP=LRMSC MOTHER TASK FUNCTION TIMERSCF1343I MSC - GROUP=LRMSC PROCESS_FC04-TIME FOR SWITCHSCF1382I MSC - GROUP=LRMSC (DE2E,06) PROCESS_FC04-CAN WE SWITCH?SCF1382I MSC - GROUP=LRMSC (DE2F,70) PROCESS_FC04-CAN WE SWITCH?SCF1344I MSC - GROUP=LRMSC PROCESS_FC05-ALL BOXES CAN SWITCHSCF1383I MSC - GROUP=LRMSC (DE2E,06) PROCESS_FC05-OPEN AND SWITCHSCF1383I MSC - GROUP=LRMSC (DE2F,70) PROCESS_FC05-OPEN AND SWITCHSCF1564I MSC - GROUP=LRMSC PROCESS_FC06-ALL BOXES OPENED WINDOW AND CYCLE SWITCHEDSCF1564I MSC - GROUP=LRMSC TIME OF DAY FOR CYCLE 00000004 IS 12:24:53.06SCF1384I MSC - GROUP=LRMSC (DE2E,06) PROCESS_FC06-CLOSE WINDOWSCF1384I MSC - GROUP=LRMSC (DE2F,70) PROCESS_FC06-CLOSE WINDOWSCF1347I MSC - GROUP=LRMSC PROCESS_FC07-ALL BOXES CLOSED WINDOWSCF1329I MSC - GROUP=LRMSC (DE2E,06) SRDFA INACTIVE

Example 2

F EMCSCF,MSC,PENDDROP,MSCG(PROD_MSC2)SCF1390I MSC,PENDDROP,MSCG(PROD_MSC2) SCF1391I MSC - PENDDROP COMMAND ACCEPTED. SCF1564I MSC - GROUP=PROD_MSC2 TIME OF DAY FOR CYCLE 00000040 IS 10:31:10.01SCF1564I MSC - GROUP=PROD_MSC2 TIME OF DAY FOR CYCLE 00000041 IS 10:31:10.01SCF1330E MSC - GROUP=PROD_MSC2 (8917,6C,F1) SRDFA NOT PRIMARY SIDESCF1463E MSC - GROUP=PROD_MSC2 (8917,6C,F1) SRDFA IS NOT ACTIVE4SCF1405E MSC - GROUP=PROD_MSC2 (8917,6C,F1) HOST CLEANUP INVOKEDSCF1406I MSC - GROUP=PROD_MSC2 HOST CLEANUP IS RUNNING


Command Reference

SCF1463E MSC - GROUP=PROD_MSC2 (8917,6C,F1) SRDFA IS NOT ACTIVE4SCF1414I MSC - GROUP=PROD_MSC2 HOST CLEANUP - PHASE2 IS RUNNING SCF1411I MSC - GROUP=PROD_MSC2 HOST CLEANUP CASE2 RUNNING SCF1409I MSC - GROUP=PROD_MSC2 (8917,6C,F1) PROCESS_FC10-DISCARD INACTIVE CYCLESCF1413I MSC - GROUP=PROD_MSC2 HOST CLEANUP IS FINISHED SCF15AAI MSC - GROUP=PROD_MSC2 PENDDROP complete SCF1594I MSC - GROUP=PROD_MSC2 Auto Recovery bypassed due to PENDDROP


Command Reference

MSC,RECOVER

You can use this command to initiate SRDF Automated Recovery for MSC environments only. SRDF Automated Recovery is a utility to monitor and perform automated recovery of SRDF/A environments. It eliminates the need for external automation or manual intervention by automatically restoring SRDF/A to operational status following a planned or unplanned outage. You can configure the software to prompt you for authorization before proceeding with automated recovery.

Syntax formats

F emcscf,MSC,RECOVER[,MSCGroup(msc_group)]

[,NOBCV]

Parameters

MSCGroup


NOBCV

Disables BCV management for this recovery event only.

Note: While this command remains available in ResourcePak Base product, EMC recommends that you use the Host Component #SC RECOVER command described in the EMC Mainframe Enablers SRDF Host Component for z/OS Product Guide to perform automated recoveries.

MSC,REFRESH

Use this command when you want to discard an existing MSC group definition and start a different MSC group definition. To send the new MSC group definition, you need to either start SRDF Host Component or perform an #SC GLOBAL,PARM_REFRESH with the definition in the SRDF Host Component initialization parameters.

When issued to a Primary MSC Server, this command is equivalent to an F SCF,MSC DISABLE followed by an F SCF,MSC ENABLE.

When issued to a Secondary MSC Server, this command is equivalent to an F SCF,MSC DEACT followed by an F SCF,MSC ENABLE.

Note: MSC,REFRESH is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,REFresh[,MSCGroup(msc_group|*)]

Parameters

MSCGroup




Command Reference


ExamplesExample 1

F EMCSCF,MSC,REFRESHSCF1390I MSC,REFRESH SCF1391I MSC - REFRESH COMMAND ACCEPTED. SCF1569I MSC - GROUP=LRMSC.................... STEAL LOCK AFTER = 120 MIN(S) SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1426I MSC - GROUP=LRMSC.................... (DE2E,06) GETTING SEL LOCKS SCF1427I MSC - GROUP=LRMSC.................... (DE2E,06) GOT LOCAL SEL LOCK SCF1428I MSC - GROUP=LRMSC.................... (DE2E,06) GOT REMOTE SEL LOCK SCF1426I MSC - GROUP=LRMSC.................... (DE2F,70) GETTING SEL LOCKS SCF1427I MSC - GROUP=LRMSC.................... (DE2F,70) GOT LOCAL SEL LOCK SCF1428I MSC - GROUP=LRMSC.................... (DE2F,70) GOT REMOTE SEL LOCK SCF1436I MSC - GROUP=LRMSC.................... OBTAINED ALL SEL LOCKS SCF1376I MSC - GROUP=LRMSC.................... (DE2E,06) SYMMETRIX TASK ENDED SCF1376I MSC - GROUP=LRMSC.................... (DE2F,70) SYMMETRIX TASK ENDED SCF1435I MSC - GROUP=LRMSC.................... (DE2E,06) FREEING SEL LOCKS SCF1430I MSC - GROUP=LRMSC.................... (DE2E,06) LOCAL SEL LOCK FREED SCF1433I MSC - GROUP=LRMSC.................... (DE2E,06) REMOTE SEL LOCK FREEDSCF1435I MSC - GROUP=LRMSC.................... (DE2F,70) FREEING SEL LOCKS SCF1333I MSC - GROUP=LRMSC.................... MOTHER TASK ENDED SCF1321I MSC - TASK DISABLED SCF1320I MSC - TASK ENABLED

Example 2 This example specifies an MSC group. Note that the MSC group definition is deleted.

F EMCSCF,MSC,DISPLAYSCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=0 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 ACTIVE MSC(CAS) WF=0 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I DB_ACCT_LVMSC3 ACTIVE MSC WF=0 SCF1601I (82DF,E1) 0001926-00215 0001926-00290 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=0 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete

F EMCSCF,MSC,REFRESH,MSCG(DB_ACCT_LVMSC3)SCF1390I MSC,REFRESH,MSCG(DB_ACCT_LVMSC3) SCF1391I MSC - REFRESH COMMAND ACCEPTED. SCF1569I MSC - GROUP=DB_ACCT_LVMSC3 STEAL LOCK AFTER = 2 MIN(S) SCF15AAI MSC - GROUP=DB_ACCT_LVMSC3 DISABLE complete

F EMCSCF,MSC,DISPLAYSCF1390I MSC,DISPLAY SCF1391I MSC - DISPLAY COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED SCF1600I TEST_MSC1 INACTIVE MSC(CAS) WF=0 SCF1601I (855F,F1,52) 0001926-00313 0001926-00304 0001926-00312 SCF1601I (7A4F,80,09) 0001926-00290 0001926-00215 0001926-00261 SCF1600I PROD_MSC2 ACTIVE MSC(CAS) WF=0 SCF1601I (8917,6C,F1) 0001926-00312 0001926-00313 0001926-00304 SCF1600I EMC_STAR ACTIVE STAR(CAS) WF=0 CGRPLV SCF1601I (851F,F2,54),(2E) 0001926-00313 0001926-00304 0001926-00312 SCF1602I MSC Display complete


Command Reference

MSC,RESTART

This command can only be used after you have previously started MSC successfully (that is, you have successfully received a valid MSC group definition from SRDF Host Component). Use this command when you want to save the existing MSC group definition and start it running in MSC again.

This is the equivalent of issuing F SCFNAME,MSC,DISABLE, followed by F SCFNAME,MSC,ENABLE, followed by a #SC GLOBAL,PARM_REFRESH (without issuing a PARM_REFRESH in SRDF Host Component).

Note: MSC,RESTART is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,RESTART[,MSCGroup(msc_group)]

Parameters

MSCGroup


ExamplesExample 1

F EMCSCF,MSC,RESTART SCF1390I MSC,RESTART SCF1391I MSC - RESTART COMMAND ACCEPTED. SCF1435I MSC - GROUP=LRMSC (DE2E,06) FREEING SEL LOCKS SCF1435I MSC - GROUP=LRMSC (DE2F,70) FREEING SEL LOCKS SCF1569I MSC - GROUP=LRMSC STEAL LOCK AFTER = 120 MIN(S) SCF1426I MSC - GROUP=LRMSC (DE2E,06) GETTING SEL LOCKS SCF1427I MSC - GROUP=LRMSC (DE2E,06) GOT LOCAL SEL LOCK SCF1428I MSC - GROUP=LRMSC (DE2E,06) GOT REMOTE SEL LOCK SCF1426I MSC - GROUP=LRMSC (DE2F,70) GETTING SEL LOCKS SCF1427I MSC - GROUP=LRMSC (DE2F,70) GOT LOCAL SEL LOCK SCF1428I MSC - GROUP=LRMSC (DE2F,70) GOT REMOTE SEL LOCK SCF1436I MSC - GROUP=LRMSC OBTAINED ALL SEL LOCKS SCF1376I MSC - GROUP=LRMSC (DE2E,06) SYMMETRIX TASK ENDED SCF1376I MSC - GROUP=LRMSC (DE2F,70) SYMMETRIX TASK ENDED SCF1435I MSC - GROUP=LRMSC (DE2E,06) FREEING SEL LOCKS SCF1430I MSC - GROUP=LRMSC (DE2E,06) LOCAL SEL LOCK FREED SCF1433I MSC - GROUP=LRMSC (DE2E,06) REMOTE SEL LOCK FREED SCF1435I MSC - GROUP=LRMSC (DE2F,70) FREEING SEL LOCKS SCF1333I MSC - GROUP=LRMSC MOTHER TASK ENDED SCF1321I MSC - TASK DISABLED SCF1320I MSC - TASK ENABLED SCF1304I MSC - SRDF HC POST SCF1568I MSC - GROUP=LRMSC WEIGHT FACTOR = 0 SCF1335E MSC - GROUP=LRMSC MOTHER TASK STARTED SCF1328I MSC - GROUP=LRMSC (DE2E,06) SRDFA ACTIVE SCF1326I MSC - GROUP=LRMSC (DE2E,06) SERIAL = 000190300097 SCF1328I MSC - GROUP=LRMSC (DE2F,70) SRDFA ACTIVE SCF1569I MSC - GROUP=LRMSC STEAL LOCK AFTER = 120 MIN(S) SCF1326I MSC - GROUP=LRMSC (DE2F,70) SERIAL = 000190300097 SCF1426I MSC - GROUP=LRMSC (DE2E,06) GETTING SEL LOCK ETC ETC


Command Reference

Example 2

F EMCSCF,MSC,RESTART,MSCG(PROD_MSC2)SCF1390I MSC,RESTART,MSCG(PROD_MSC2) SCF1391I MSC - RESTART COMMAND ACCEPTED. SCF1569I MSC - GROUP=PROD_MSC2 STEAL LOCK AFTER = 2 MIN(S) SCF15AAI MSC - GROUP=PROD_MSC2 DISABLE complete SCF1304I MSC - SRDF HC POST SCF1323I MSC - ALLOW OVERWRITE OF SCRATCH AREA AND BOXLIST SCF1322I MSC - AUTO RECOVERY ENABLED SCF1568I MSC - GROUP=PROD_MSC2 WEIGHT FACTOR = 0 SCF1366I MSC - GROUP=PROD_MSC2 (8917,6C,F1) Remote Cycle SwitchingSCF1569I MSC - GROUP=PROD_MSC2 STEAL LOCK AFTER = 2 MIN(S) SCF1342I MSC - GROUP=PROD_MSC2 PROCESS_FC03-ALL BOXES ACTIVE SCF1523I MSC - GROUP=PROD_MSC2 GLOBAL CONSISTENCY HAS BEEN ACHIEVEDSCF1564I MSC - GROUP=PROD_MSC2 TIME OF DAY FOR CYCLE 00000001 I S 09:59:40.01SCF1564I MSC - GROUP=PROD_MSC2 TIME OF DAY FOR CYCLE 00000002 I S 10:00:10.01

MSC,RESTARTTOSEC

After a planned failover, this command can be issued to restart the previous primary server as a secondary server, running with MSC_WEIGHT_FACTOR = 2.

Syntax

F emcscf,MSC,RESTARTTOSEC[,MSCGroup(msc_group)]

Parameters

MSCGroup


Note: MSC,RESTARTTOSEC is not allowed while an MSC,TAKEOVER operation is in progress.

ExampleF EMCSCF,MSC,RESTARTTOSEC,MSCG(EMC_STAR)SCF1390I MSC,RESTARTTOSEC,MSCG(EMC_STAR)SCF1391I MSC - RESTARTTOSEC COMMAND ACCEPTED.SCF1323I MSC - ALLOW OVERWRITE OF SCRATCH AREA AND BOXLIST SCF1568I MSC - GROUP=EMC_STAR WEIGHT FACTOR = 2SCF1569I MSC - GROUP=EMC_STAR STEAL LOCK AFTER = 5 MIN(S)SCF1452I MSC - GROUP=EMC_STAR (850F,F0) EXISTING DEFINITION MATCHSCF15C7W MSC - GROUP=EMC_STAR (850F,F1) Gatekeeper ENQ in-useSCF1452I MSC - GROUP=EMC_STAR (850F,F1) EXISTING DEFINITION MATCHSCF1451I MSC - GROUP=EMC_STAR EXISTING DEFINITION MATCH SCF1342I MSC - GROUP=EMC_STAR PROCESS_FC03-ALL BOXES ACTIVE SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000014 IS 10:21:25.34


Command Reference

MSC,RESTARTTOZERO

Use this command to start MSC as a Primary Server. This is useful if the MSC Group was not defined with MSC_WEIGHT_FACTOR=0, or after a failed DeactRestartToZero command (if DeactRestartToZero fails, any type of Deact command is denied due to the "inactive" status of the MSC Group).

Syntax

F emcscf,MSC,RESTARTTOZERO[,MSCGroup(msc_group)]

Parameters

MSCGroup


Note: MSC,RESTARTTOZERO is not allowed while an MSC,TAKEOVER operation is in progress.

ExampleSCF1390I MSC,RESTARTTOZERO,MSCG(EMC_STAR) SCF1391I MSC - RESTARTTOZERO COMMAND ACCEPTED. SCF1323I MSC - ALLOW OVERWRITE OF SCRATCH AREA AND BOXLIST SCF1316I MSC - STAR SDDF QUERY TO DA SCF1568I MSC - GROUP=EMC_STAR WEIGHT FACTOR = 0 SCF1569I MSC - GROUP=EMC_STAR STEAL LOCK AFTER = 5 MIN(S) SCF1452I MSC - GROUP=EMC_STAR (08503,7A) EXISTING DEFINITION MATCHSCF1452I MSC - GROUP=EMC_STAR (08504,7C) EXISTING DEFINITION MATCHSCF1452I MSC - GROUP=EMC_STAR (08505,7E) EXISTING DEFINITION MATCHSCF1451I MSC - GROUP=EMC_STAR EXISTING DEFINITION MATCH SCF1342I MSC - GROUP=EMC_STAR PROCESS_FC03-ALL BOXES ACTIVE SCF1562I MSC - GROUP=EMC_STAR (08505,7E) SER= 000195700225 CYCLE SWITCH DELAY - TRANSMITSCF1562I MSC - GROUP=EMC_STAR (08503,7A) SER= 000195700225 CYCLE SWITCH DELAY - TRANSMITSCF1562I MSC - GROUP=EMC_STAR (08504,7C) SER= 000195700225 CYCLE SWITCH DELAY - TRANSMITSCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000305 IS 12:19:08.53SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000306 IS 12:19:23.01SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000307 IS 12:19:38.01

MSC,TAKEOVER

Initiates a takeover of the SRDF/Star environment from a secondary server. Upon completion, MSC will be registered to ConGroup and will have assumed control of the SRDF/Star SDDF sessions.

A ConGroup MOVEOWNER command must be successfully performed before issuing the MSC,TAKEOVER command.

Syntax

F emcscf,MSC,TAKEOVER[,MSCGroup(msc_group)]

Parameters

msc_group

msc_group specifies the group.


Command Reference

ExampleF EMCSCF,MSC,TAKEOVER,MSCG(EMC_STAR)SCF1390I MSC,TAKEOVER,MSCG(EMC_STAR)SCF1391I MSC - TAKEOVER COMMAND ACCEPTED. SCF15ABI MSC - GROUP=EMC_STAR TAKEOVER processing initiatedSCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000013 IS 08:55:02.00SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000014 IS 08:55:23.00SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000015 IS 08:55:44.00SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000016 IS 08:56:05.00SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000017 IS 08:56:26.00SCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE 00000018 IS 08:56:47.00SCF1525I MSC - GROUP=EMC_STAR STAR RECOVERY IS NOW AVAILABLESCF15CAI MSC - GROUP=EMC_STAR TAKEOVER processing completed

MSC,VERBOSE

This command enables or disables features for debugging the MSC environment. This command is equivalent to the SCF.MSC.VERBOSE=YES initialization parameter.

Note: Only use this command when requested by EMC Customer Support.

Syntax

F emcscf,MSC,VERBOSE,ON|OFF[,MSCGroup(msc_group|*)]

Parameters

MSCGroup




ON

Enables the display of MSC/Star process status messages. These messages are intended for reference when diagnosing a processing problem, and are not intended for customer tracking or message automation.

OFF

Disables the display of process status messages.

ExamplesExample 1 F EMCSCF,MSC,VERBOSE,ON

SCF1390I MSC,VERBOSE,ON SCF1391I MSC - VERBOSE COMMAND ACCEPTED.

Example 2

F EMCSCF,MSC,VERBOSE,ON,MSCG(EMC_STAR) SCF1390I MSC,VERBOSE,ON,MSCG(EMC_STAR) SCF1391I MSC - VERBOSE COMMAND ACCEPTED. SCF1345I MSC - GROUP=EMC_STAR MOTHER TASK FUNCTION TIMERSCF1343I MSC - GROUP=EMC_STAR PROCESS_FC04-TIME FOR SWITCHSCF1382I MSC - GROUP=EMC_STAR (851F,F2,54) PROCESS_FC04-CAN WE SWITCH?SCF1344I MSC - GROUP=EMC_STAR PROCESS_FC05-ALL BOXES CAN SWITCH


Command Reference

SCF1383I MSC - GROUP=EMC_STAR (851F,F2,54) PROCESS_FC05-OPEN AND SWITCHSCF1346I MSC - GROUP=EMC_STAR PROCESS_FC06-ALL BOXES OPENED WINDOW AND CYCLE SWITCHEDSCF1564I MSC - GROUP=EMC_STAR TIME OF DAY FOR CYCLE00000071 IS 09:54:10.01


Command Reference

SRDF/A Monitor operator commandsThe SRDF/A Monitor commands are designed to control the SRDF/A Monitor.

ASY,DISABLE

Disables the SRDF/A Monitor.

Syntax

F emcscf,ASY,DISABLE

ParametersNone.

ExampleF EMCSCF,ASY,DISABLE SCF1290I ASY,DISABLE SCF1291I ASY DISABLE COMMAND ACCEPTED. SCF1221I ASY MONITOR TASK DISABLED

ASY,DISPLAY

Displays the current status and options of the SRDF/A Monitor. When a gatekeeper and SRDF group is supplied, the command will display the status and options of the specified group.

Syntax

F emcscf,ASY,DISPLAY[(ccuu,#rdfgroup)]

Parameters

ccuu


#rdfgroup

Specifies the SRDF group you want to display. This must be a 1 or 2-digit (hex) value representing the SRDF group.

ExampleF EMCSCF,ASY,DISPLAY SCF1290I ASY,DISPLAY SCF1291I ASY DISPLAY COMMAND ACCEPTED. SCF1220I ASY MONITOR TASK ENABLED


Command Reference

ASY,ENABLE

Enables the SRDF/A Monitor, if you had previously disabled the SRDF/A Monitor with the ASY,DISABLE command.

Note: To enable the SRDF/A Monitor when the task has not yet started, you need to set the initialization parameter, SCF.ASY.MONITOR to ENABLE, and then issue an ASY,REFRESH command.

Syntax

F emcscf,ASY,ENABLE

ParametersNone.

ExampleF EMCSCF,ASY,ENABLE SCF1290I ASY,ENABLE SCF1291I ASY ENABLE COMMAND ACCEPTED.SCF1220I ASY MONITOR TASK ENABLED

ASY,REFRESH

Refreshes the initialization parameters for the SRDF/A Monitor.

Note: If SRDF/A Single Session Auto Recovery is enabled and an auto recovery session is active, the monitor cannot be refreshed.

Note: An INI,REFRESH command is required before the issuing a monitor REFRESH, when changes have been made to the monitor parameters.

Syntax

F emcscf,ASY,REFRESH

ParametersNone.

ExampleF EMCSCF,INI,REFRESH SCF0321I INI,REFRESH SCF0322I INI REFRESH COMMAND COMPLETED.F EMCSCF,ASY,REFRESHSCF1290I ASY,REFRESH SCF1291I ASY REFRESH COMMAND ACCEPTED. SCF1220I ASY MONITOR TASK ENABLED

SRDF/A Monitor operator commands 337

Command Reference

ASY,SSAR,DISABLE

Disables the SRDF/A Single Session Auto Recovery feature of the SRDF/A Monitor.

Note: SRDF/A Single Session Auto Recovery cannot be disabled if an auto recovery session is active.

Syntax

F emcscf,ASY,SSAR,DISABLE

ParametersNone.

Example F EMCSCF,ASY,SSAR,DISABLE

ASY,SSAR,ENABLE

Enables the SRDF/A Single Session Auto Recovery feature of the SRDF/A Monitor.

Syntax

F emcscf,ASY,SSAR,ENABLE

ParametersNone.

Example F EMCSCF,ASY,SSAR,ENABLE

ASY,RECOVER,SRDFA

Initiates the SRDF/A Single Session Auto Recovery session for the specified group. Recovery will be attempted if:

◆ The group is not MSC-managed.

◆ The group is not active.

◆ The group number matches the group number in the specified statement.

Note: This command should only be issued for a single session SRDF/A group that is inactive.

Syntax

F emcscf,ASY,RECOVER,SRDFA(ccuu,#rdfgroup){,NOBCV}

Parameters

ccuu



Command Reference

#rdfgroup

Specifies the SRDF group through which you want to perform a SRDF/A Single Session Auto Recovery operation. This must be a 1 or 2-digit (hex) value representing the SRDF group.

NOBCV

Disables BCV management for this recovery event only.

Example F EMCSCF,ASY,RECOVER,SRDFA(F800,B9)

DSE Monitor operator commandsThe DSE monitor commands are designed to control the DSE monitor.

DSE,DISABLE

Disables the DSE monitor. The DISABLE command will stop monitoring everything if no controller is specified.


Syntax

F emcscf,DSE,DISABLE,options


CONTROLLER/CNTRL(id)

Optional. Specifies a DASD controller. You can specify the Symmetrix controller with either the 5-digit or 12-digit Symmetrix controller ID. If a 12-digit value is used, it must include a dash between the first 7 digits and the last 5 digits (for example, 1234567-12345). Use the 12-digit ID when multiple controllers use the same last 5 digits. Leading zeros are not required.


ExampleF EMCSCF,DSE,DISABLESCF1190I DSE,DISABLE SCF1121I DSE MONITOR DSEPOOL TASK DISABLED SCF1191I DSE COMMAND ACCEPTED.

DSE Monitor operator commands 339

Command Reference

DSE,DISPLAY

The DISPLAY command shows the default DSE monitor settings (if GLOBAL is specified), the settings for a controller, or the settings for a specified controller pool.

Syntax

F emcscf,DSE,DISPLAY,options


GLOBAL

Shows the default settings for the DSE monitor.




POOLNAME(xx..xx)

Optional. Specifies the controller pool.

ExampleF EMCSCF,DSE,DISPLAY,GLOBALSCF1101I DSE,DISPLAY,GLOBALSCF1130I DSE GLOBAL INTERVAL 04, PERCENT=(10,80)

DSE,ENABLE

Enables the DSE monitor. The ENABLE command will start monitoring everything if no controller is specified or monitor a specific controller, if specified.

Syntax

F emcscf,DSE,ENABLE,options






Command Reference

ExampleF EMCSCF,DSE,ENABLESCF1190I DSE,ENABLE SCF1191I DSE COMMAND ACCEPTED. SCF1120I DSE MONITOR DSEPOOL TASK ENABLED

DSE,REFRESH

Refreshes the initialization parameters for the DSE monitor. If there are changes, they must first be reloaded and then reprocessed.


Syntax

F emcscf,DSE,REFRESH

ParametersNone.

ExampleF EMCSCF,INI,REFRESH SCF0321I INI,REFRESH SCF0322I INI REFRESH COMMAND COMPLETED.F EMCSCF,DSE,REFRESH SCF1190I DSE,REFRESH SCF1191I DSE COMMAND ACCEPTED.SCF1125I DSE - INI PARAMETERS LOADED

DSE Monitor operator commands 341

Command Reference

SDV Monitor operator commandsThe SDV Monitor commands are designed to control the SDV Monitor.

SDV,DISABLE

Disables the SDV Monitor. The DISABLE command will stop monitoring everything if no controller is specified.


Syntax

F emcscf,SDV,DISABLE,options





ExampleF EMCSCF,SDV,DISABLE SCF1190I SDV,DISABLE SCF1191I SDV COMMAND ACCEPTED. SCF1121I SDV MONITOR SNAPPOOL TASK DISABLED

SDV,DISPLAY

The DISPLAY command shows the default SDV monitor settings (if GLOBAL is specified), the settings for a controller, or the settings for a specified controller pool.

Syntax

F emcscf,SDV,DISPLAY,options


GLOBAL

Shows the default settings for the SDV monitor.


Command Reference




POOLNAME(xx..xx)

Optional. Specifies the controller pool.

ExampleF EMCSCF,SDV,DISPLAY,GLOBALSCF1101I SDV,DISPLAY,GLOBALSCF1130I SDV GLOBAL INTERVAL 04, PERCENT=(10,80)

SDV,ENABLE

Enables the SDV Monitor. The ENABLE command will start monitoring everything if no controller is specified or monitor a specific controller, if specified.

Syntax

F emcscf,SDV,ENABLE,options





ExampleF EMCSCF,SDV,ENABLE SCF1190I SDV,ENABLE SCF1191I SDV COMMAND ACCEPTED. SCF1120I SDV MONITOR SNAPPOOL TASK ENABLED

SDV Monitor operator commands 343

Command Reference

SDV,REFRESH

Refreshes the initialization parameters for the SDV Monitor. If there are changes, they must first be reloaded and then reprocessed.


Syntax

F emcscf,SDV,REFRESH

ParametersNone.

ExampleF EMCSCF,INI,REFRESH SCF0321I INI,REFRESH SCF0322I INI REFRESH COMMAND COMPLETED.F EMCSCF,SDV,REFRESH SCF1190I SDV,REFRESH SCF1191I SDV COMMAND ACCEPTED.SCF1125I SDV - INI PARAMETERS LOADED


Command Reference

THN Monitor operator commandsThe Thin Pool (THN) Monitor commands are designed to control the THN Monitor.

Note: Refer to “Thin Pool Capacity Monitor examples” on page 442 for examples on using the THN monitor.

THN,DISABLE

Disables the THN Monitor. The DISABLE command will stop monitoring everything if no controller is specified.


Syntax

F emcscf,THN,DISABLE,options





ExampleF EMCSCF,THN,DISABLESCF1190I THN,DISABLE SCF1121I THN MONITOR THINPOOL TASK DISABLED SCF1191I THN COMMAND ACCEPTED.

THN,DISPLAY

The DISPLAY command shows the default THN monitor settings (if GLOBAL is specified), the settings for a controller, or the settings for a specified controller pool.

Syntax

F emcscf,THN,DISPLAY,options

THN Monitor operator commands 345

Command Reference


GLOBAL

Shows the default settings for the THN monitor.




POOLNAME(xx..xx)

Optional. Specifies the controller pool and displays the devices in the pool. An optional device range may be specified to limit the display of devices in the pool.

ExampleF EMCSCF,THN,DISPLAY,GLOBALSCF1101I THN,DISPLAY,GLOBALSCF1130I THN GLOBAL INTERVAL 04, PERCENT=(10,80)

THN,ENABLE

Enables the THN Monitor. The ENABLE command will start monitoring everything if no controller is specified or monitor a specific controller, if specified.

Syntax

F emcscf,THN,ENABLE,options





ExampleF EMCSCF,THN,ENABLE SCF1190I THN,ENABLE SCF1120I THN MONITOR THINPOOL TASK ENABLED SCF1191I THN COMMAND ACCEPTED.


Command Reference

THN,REFRESH

Refreshes the initialization parameters for the THN Monitor. If there are changes, they must first be reloaded and then reprocessed.


Syntax

F emcscf,THN,REFRESH

ParametersNone.

ExampleF EMCSCF,INI,REFRESH SCF0321I INI,REFRESH SCF0322I INI REFRESH COMMAND COMPLETED.F EMCSCF,THN,REFRESHSCF1190I THN,REFRESH SCF1191I THN COMMAND ACCEPTED.SCF1125I THN - INI PARAMETERS LOADED

THN Monitor operator commands 347

Command Reference

TRU monitor operator commandsStarting with ResourcePak Base version 7.4, and Enginuity level 5876 or higher, EMCSCF provides a Thin space reclamation (TRU) environment that records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the Symmetrix free track pool.

The following are the TRU monitor commands.

TRU,HELP

Display a short list of the valid TRU commands.

Syntax

F scfname,TRU,HELP

ParametersNone.

ExampleF EMCSCF,TRU,HELP SCF5480I TRU TRU,HELP SCF5492I TRU COMMANDS ARE: SCF5493I TRU DISPLAY DISPLAY TRU INFORMATION SCF5493I TRU DISPLAY,DEVICE,CCUU -CCUU DISPLAY TRU DEVICE INFORMATION SCF5493I TRU HELP SHOW VALID TRU COMMANDS SCF5493I TRU HOLD,CCUU -CCUU STOP SCHEDULING RECLAIM ON DEVICE(S) SCF5493I TRU RECLAIM,CCUU -CCUU SCHEDULE RECLAIM FOR DEVICE(S) SCF5493I TRU REFRESH REPROCESS INI AND REBUILD DEVICE TABLES SCF5493I TRU RELEASE,CCUU -CCUU ALLOW SCHEDULING OF RECLAIM FOR DEVICE(S) SCF5493I TRU SCAN,CCUU -CCUU SCHEDULE SCAN FOR DEVICE(S)SCF5493I TRU START,CCUU -CCUU ALLOW MONITORING OF DEVICE(S) SCF5493I TRU STOP,CCUU -CCUU STOP MONITORING OF DEVICE(S) SCF5481I TRU HELP COMMAND ACCEPTED

TRU,DISPLAY

Display the TRU environment information. This includes most of the current settings.

Syntax

F scfname,TRU,DISPLAY

ParametersNone.

ExampleF EMCSCF,TRU,DISPLAYSCF5480I TRU TRU,DISPLAY SCF5490I TRU ENVIRONMENT INFORMATION DISPLAY SCF5491I TRU HEADER AT: 26D8B1B8 SIZE: 000200 VERSION: 00 SCF5491I TRU SCAN HAS BEEN RUN 3 TIMES SCF5491I TRU ACTIVE SCAN TASK COUNT IS 0 SCF5491I TRU SCAN TASK LIMIT IS 10 SIMULTANEOUS TASKS SCF5491I TRU SCAN PGMNAME IS ESFTRURC


Command Reference

SCF5491I TRU RECLAIM HAS BEEN RUN 3 TIMES SCF5491I TRU ACTIVE RECLAIM TASK COUNT IS 0 SCF5491I TRU RECLAIM TASK LIMIT IS 10 SIMULTANEOUS TASKS SCF5491I TRU RECLAIM PGMNAME IS ESFTRURC SCF5491I TRU RECLAIM DATASET FACTOR IS 1000 SCF5491I TRU SCRATCH EXIT AUTO-RECLAIM IS ENABLED WHEN EXTENT IS SMALLER THAN 20 TRACKSSCF5491I TRU WAIT TIME AFTER SCRATCH DISABLED SCF5491I TRU SCHEDULE RECLAIM ONLY WHEN DEVICE BUSY IS DISABLED SCF5491I TRU SCHEDULE RECLAIM ONLY WHEN CHANNEL BUSY IS DISABLED SCF5491I TRU SCHEDULE RECLAIM ONLY WHEN CPU BUSY IS DISABLED SCF5491I TRU SYSVTOC SERIALIZATION FOR RECLAIM IS DISABLED SCF5491I TRU SYSVTOC SERIALIZATION MAX HOLD TIME IS ENABLED - 30.00 SECONDSSCF5491I TRU SYSVTOC SERIALIZATION MIN WAIT TIME IS ENABLED - 30.00 SECONDSSCF5491I TRU RECLAIM TIME OF DAY LIMITS ARE NOT ENABLED SCF5498I TRU ENVIRONMENT INFORMATION DISPLAY COMPLETE SCF5481I TRU DISPLAY COMMAND ACCEPTED

TRU, DISPLAY, DEVICE

Display the TRU environment information and additional information for the devices indicated.

Syntax

F scfname,TRU,DISplay,DEVice,ccuu[-ccuu]

Parameters

ccuu[-ccuu]

z/OS device number or range of devices.

ExampleF EMCSCF,TRU,DISPLAY,DEVICE,845C SCF5480I TRU TRU,DISPLAY,DEVICE,845C SCF5490I TRU ENVIRONMENT INFORMATION DISPLAY SCF5491I TRU HEADER AT: 26D872C0 SIZE: 000200 VERSION: 00 SCF5491I TRU SCAN HAS BEEN RUN 5 TIMES SCF5491I TRU ACTIVE SCAN TASK COUNT IS 0 SCF5491I TRU SCAN TASK LIMIT IS 10 SIMULTANEOUS TASKS SCF5491I TRU SCAN PGMNAME IS ESFTRURC SCF5491I TRU RECLAIM HAS BEEN RUN 5 TIMES SCF5491I TRU ACTIVE RECLAIM TASK COUNT IS 0 SCF5491I TRU RECLAIM TASK LIMIT IS 10 SIMULTANEOUS TASKS SCF5491I TRU RECLAIM STCNAME IS LVTRCLM SCF5491I TRU RECLAIM DATASET FACTOR IS 1000 SCF5491I TRU SCRATCH EXIT AUTO-RECLAIM IS ENABLED WHEN EXTENT IS SMALLER THAN 20 TRACKS SCF5491I TRU WAIT TIME AFTER SCRATCH ENABLED - 6000 SECONDS SCF5491I TRU SCHEDULE RECLAIM ONLY WHEN DEVICE BUSY IS DISABLED SCF5491I TRU SCHEDULE RECLAIM ONLY WHEN CHANNEL BUSY IS DISABLED SCF5491I TRU SCHEDULE RECLAIM ONLY WHEN CPU BUSY IS DISABLED SCF5491I TRU SYSVTOC SERIALIZATION FOR RECLAIM IS DISABLED SCF5491I TRU SYSVTOC SERIALIZATION MAX HOLD TIME IS ENABLED - 30.00 SECONDS SCF5491I TRU SYSVTOC SERIALIZATION MIN WAIT TIME IS ENABLED - 30.00 SECONDS SCF5491I TRU RECLAIM TIME OF DAY LIMITS ARE NOT ENABLED SCF5495I TRU ENVIRONMENT DEVICE LIST DISPLAY SCF5496I TRU DEVICE AT: 26D834D8 SIZE: 0000C0 VERSION: 00 SCF5496I TRU CCUU: 845C UCB@: 024E5108 SERNO: 000195700225 SYMDV#: 00000744 SCF5496I TRU MCODE: 5076 SDDF: DA9404FA FLAGS: C4000000 CYL#: 00000459SCF5496I TRU MONITORING ACTIVE SCF5496I TRU LAST SCRATCH: 00:00:00.00 00/00/0000 SCF5496I TRU LAST SCAN: 12:08:24.31 02/16/2012 SCF5496I TRU LAST RECLAIM: 12:08:55.09 02/16/2012

TRU monitor operator commands 349

Command Reference

SCF5496I TRU SCRATCH - TOTAL: 0 RECENT: 000000 0 POST: 250 SCF5496I TRU EXTENT - TOTAL: 0 RECENT: 000000 0 POST: 500 SCF5496I TRU TRACK 00- TOTAL: 0 RECENT: 000000 0 POST: 130 SCF5496I TRU RECLAIM - TOTAL: 16680 RECENT: 16680 POST: 130 SCF5496I TRU SCAN 000- TOTAL: 16680 RECENT: 16680 POST: 130 SCF5496I TRU SCRRECL - TOTAL: 0 RECENT: 00000 0 POST: 130 SCF5498I TRU ENVIRONMENT INFORMATION DISPLAY COMPLETE SCF5481I TRU RELEASE COMMAND ACCEPTED

TRU,HOLD

Prevent scheduling of automatic RECLAIM activities for the devices.

Note: TRU,HOLD does not prevent a user’s manual attempts to run reclaim process.

Syntax

F scfname,TRU,HOLd,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


ExampleF EMCSCF,TRU,HOLD,845C SCF5480I TRU TRU,HOLD,845C SCF5487I TRU DEVICE 845C HAS SCHEDULED HOLD SCF5481I TRU HOLD COMMAND ACCEPTED SCF5417I TRU HOLD COMMAND COMPLETED

TRU,RECLAIM

Immediately schedule RECLAIM processing for the devices.

Syntax

F scfname,TRU,REClaim,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


ExampleF EMCSCF,TRU,RECLAIM,845CSCF5480I TRU TRU,RECLAIM,845C SCF5487I TRU DEVICE 845C HAS SCHEDULED RECLAIM SCF5481I TRU RECLAIM COMMAND ACCEPTED S TRKRCLM,CCUU=845C,TYPE=RECLAIM SCF5413I TRU RECLAIM STARTED TASK STARTED ON DEVICE 845C - S TRKRCLM,CCUU=845CSCF5417I TRU RECLAIM COMMAND COMPLETED


Command Reference

TRU,REFRESH

Rescan the SCF device list and ensure that the TRU tables are up to date.

Syntax

F scfname,TRU,REFRESH

ParametersNone.

ExampleF EMCSCF,TRU,REFRESH SCF5480I TRU TRU,REFRESH SCF5481I TRU REFRESH COMMAND ACCEPTED SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.DSPREFIX ASSIGNED VALUE OF EMC. RECLAIMSCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.SCRATCH.WAIT ASSIGNED VALUE OF 6000SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.STCNAME ASSIGNED VALUE OF TRKRCLM SCF5417I TRU REFRESH COMMAND COMPLETED

TRU,RELEASE

Reverse the HOLD. Allow scheduling of SCAN or RECLAIM activities for the devices.

Syntax

F scfname,TRU,RELease,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


ExampleF EMCSCF,TRU,RELEASE,845C SCF5480I TRU TRU,RELEASE,845C SCF5487I TRU DEVICE 845C HAS SCHEDULED RELEASE SCF5417I TRU RELEASE COMMAND COMPLETED SCF5481I TRU RELEASE COMMAND ACCEPTED

TRU,SCAN

Immediately schedule SCAN processing for the devices.

Syntax

F scfname,TRU,SCAn,ccuu[-ccuu]

Parameters

ccuu[-ccuu]



Command Reference

ExampleF EMCSCF,TRU,SCAN,DEV,F432 SCF5480I TRU TRU,SCAN,DEV,F432 SCF5487I TRU DEVICE F432 HAS SCHEDULED SCAN SCF5414I TRU SCAN ATTACHED TASK STARTED ON DEVICE F432 SCF5481I TRU SCAN COMMAND ACCEPTED SCF5417I TRU SCAN COMMAND COMPLETED - F432 EMCSCFV6 SCF5450I ESFTRURC ENTERED, V760-SYS SSCF 03/06/13 19.18 EMCSCFV6 SCF5459I-*F432*-PROCESSING DEVICE: F432 - VOLSER: IB4D5F, DEVICE HAS 1113 CYLINDERS EMCSCFV6 SCF5452I-*F432*-ASSIGNED TO SCF VV6 EMCSCFV6 SCF5453I-*F432*-SYSVTOC RESERVE MAX HOLD TIME = 30.00 SECONDS EMCSCFV6 SCF5454I-*F432*-SYSVTOC RESERVE AVG WAIT TIME = 30.00 SECONDS EMCSCFV6 SCF5455I-*F432*-RECLAIM METHOD = BEGINNING TO END EMCSCFV6 SCF5474I-*F432*-DEVICE SCAN EMCSCFV6 SCF5447I-*F432*-SYSVTOC RESERVE ACQUIRED ON DEVICE IB4D5F EMCSCFV6 SCF5448I-*F432*-SYSVTOC RESERVE RELEASED ON DEVICE IB4D5F EMCSCFV6 SCF5457I-*F432*-SCAN PASS# 1 HAS PROCESSED 2 SEGMENTS INVOLVING 14819 TRACKS EMCSCFV6 SCF5441I-*F432*-SCAN PROCESSED 14819 TRACKS 000039E3, 00001CF1 - SCF MONITOR NOTIFIED EMCSCFV6 SCF5451I-*F432*-ESFTRURC EXITED, RC=00000000 SCF5415I TRU SCAN ATTACHED TASK COMPLETED ON DEVICE F432, COMPLETION CODE= 00000000

TRU,START

Reverse the STOP. Start monitoring appropriate devices. If the SDDF session does not exist, create it and schedule the SCAN of the device.

Note: If a device was initially included and then subsequently excluded from TRU, the device is marked for no monitoring. However, until SCF is cycled the device remains allocated to TRU and monitoring of the device can be started by the TRU,START command.

Syntax

F scfname,TRU,STArt,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


ExampleF EMCSCF,TRU,START,845C-845F SCF5480I TRU TRU,START,845C-845F SCF5487I TRU DEVICE 845C HAS SCHEDULED START SCF5487I TRU DEVICE 845D HAS SCHEDULED START SCF5487I TRU DEVICE 845E HAS SCHEDULED START SCF5487I TRU DEVICE 845F HAS SCHEDULED START SCF5481I TRU START COMMAND ACCEPTED SCF5417I TRU START COMMAND COMPLETED SCF5414I TRU SCAN ATTACHED TASK STARTED ON DEVICE 845C SCF5417I TRU START COMMAND COMPLETED SCF5414I TRU SCAN ATTACHED TASK STARTED ON DEVICE 845D SCF5417I TRU START COMMAND COMPLETED SCF5414I TRU SCAN ATTACHED TASK STARTED ON DEVICE 845E SCF5417I TRU START COMMAND COMPLETED SCF5414I TRU SCAN ATTACHED TASK STARTED ON DEVICE 845F


Command Reference

TRU,STOP

Stop monitoring the devices. Remove the SDDF session.

Syntax

F scfname,TRU,STOp,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


ExampleF EMCSCF,TRU,STOP,845C-845FSCF5480I TRU TRU,STOP,845C-845F SCF5487I TRU DEVICE 845C HAS SCHEDULED STOP SCF5487I TRU DEVICE 845D HAS SCHEDULED STOP SCF5487I TRU DEVICE 845E HAS SCHEDULED STOP SCF5487I TRU DEVICE 845F HAS SCHEDULED STOP SCF5481I TRU STOP COMMAND ACCEPTED SCF5417I TRU STOP COMMAND COMPLETED SCF5417I TRU STOP COMMAND COMPLETED SCF5417I TRU STOP COMMAND COMPLETED SCF5417I TRU STOP COMMAND COMPLETED


Command Reference


CHAPTER 5Naming Controllers and validating paths

This chapter discusses EMC controller naming functionality and the utility to validate paths.

◆ Overview............................................................................................................... 356◆ Defining a controller name .................................................................................... 356◆ Displaying the controller name .............................................................................. 357

Naming Controllers and validating paths 355

Naming Controllers and validating paths

OverviewResourcePak Base provides the ability to assign a unique name to an EMC controller. The name can be up to 64 characters and is case-sensitive. If you include blanks in the name, then the name must be enclosed in quotes when you define it. All names shorter than 64 bytes will be considered to be blank-filled.

All controllers at Enginuity level 5668 or higher are eligible to be named.

To further ensure proper functioning, ResourcePak Base also provides the ability to validate all of the paths that connect to the same controller to identify crossed cabling that would put devices in two SSIDs of the same split.

Defining a controller nameUse the ESFCTLNM batch utility to assign a controller name. Before SCF can recognize the new controller name, it must run a DEV,RESCAN to discover the new controller name. The batch utility will post the instance of SCF through which it defined the name to do the rescan. Upon completion of the rescan, the new controller name will be available for use. If there are additional SCFs running within your environment, the new name will not become immediately available for use until the periodic device rescan is scheduled or a manual DEV,RESCAN is initiated.

ESFCTLNM JCL

The JCL required to run the ESFCTLNM utility is shown in Table 7.

The following example assigns the name “Production Site A” to a controller:

//STEP1 EXEC PGM=ESFCTLNM//STEPLIB DD DISP=SHR,DSN=EMC.SCF.LOADLIB//SCF$nnnn DD DUMMY//SYSPRINT DD SYSOUT=*//SYSIN DD *ASSIGN NAME "Production Site A" -TO CNTRL(000187431136)/*

Table 7 JCL required for ESCTLNM

JCL statements Definition

//JS10 EXEC PGM=ESFCTLNM The program name

//SCF$nnnn DD DUMMY Specifies the SCF subsystem

//SYSPRINT DD SYSOUT=* The standard output DD where all syntax errors and processing messages will be written

//SYSIN DD *ASSIGN NAME "nnnnnnnnnnnn" -TO CNTRL(ssssssssssss)

Assign name nnnnnnnnnnnn, up to 64 characters to controller serial number ssssssssssss (requires all 12 digits)



Displaying the controller nameTo display names for all controllers, use DEV DIS SUM. The controller name will appear as part of the summary display.

To display a controller name for a particular controller, use DEV DIS CNTRL(nnnnnnnnnnnn).

“DEV,DISPLAY” on page 161 describes how to use this command.

Validating paths to a controllerESFCHNU1 is a batch utility that walks each path associated with the ccuu and validate that all of the paths connected to the same controller. Use this utility to identify crossed cabling that would put devices in two SSIDs of the same split.

This identifies where devices are connected on two channels that returning different results. This utility is mainly used in labs where reconfigurationsare a normal task.

ESFCHNU1 Input cards

The input cards required to run the ESFCHNU1 utility is shown in Table 8.

ESFCHNU1 JCL

The JCL required to run the ESFCHNU1 utility is shown in Table 9.

Table 8 Input cards for ESFCHNU1 utility

Input cards Definition

ALL Scans all CCUUs on the lpar .

CCUU=nnnn,nnnn,nnnn,... Scans individual devices.Maximum number of devices at one time is 500 per ccuu card.

Table 9 JCL required for ESFCHNU1


//JS10 EXEC PGM=ESFCHNU1 Establishes the program name.

//SYSOUT dd sysout=* Specifies the parse output.

//SYSOUT2 dd sysout=* Specifies the results from the path check.

//SYSIN DD * File for input cards.

Displaying the controller name 357


ESFCHNU1 RETURN CODES

Return codes for ESFCHNU1 include:

Table 10 Return codes for ESFCHNU1

Return codes Definition

R15=800R0 = 100R0 = 2

OPEN FAILED00INPUT DATASET00OUTPUT DATASET

R15 = 1200R0 = 3

EIOBBLD FAILED


CHAPTER 6Using the Group Name Services Facility

This chapter discusses the Group Name Services (GNS) facility.

◆ Overview............................................................................................................... 360◆ GNS group types ................................................................................................... 361◆ EMCGROUP JCL...................................................................................................... 362◆ GNS batch commands reference............................................................................ 363◆ Working with groups ............................................................................................. 375◆ GNS reason codes................................................................................................. 384

Using the Group Name Services Facility 359

Using the Group Name Services Facility

OverviewGroup Name Services (GNS) is the Symmetrix group definition sharing facility. GNS allows you to define a group once, in one place, and then use that single definition across multiple EMC products on multiple platforms. You can use group definitions created through GNS on a mainframe system with EMC software products running on open systems hosts.

Each group is a collection of controllers and the devices that reside on those controllers. For groups that span Symmetrix systems, the definition is stored as a set of components on different Symmetrix systems. Each Symmetrix system holds its portion of that single definition.

Group definitions are maintained through the EMCGROUP batch utility. EMCGROUP allows you to perform the following tasks:

◆ Define groups

◆ List groups

◆ Display groups

◆ Rename groups

◆ Delete groups

◆ Define SRDF/AR device replacement pools (SARPOOLs)

Before using GNS

After you install ResourcePak Base, but before you use GNS, you must take the following steps:

◆ Set the SCF.GNS.ACTIVE parameter to YES.

“SCF.GNS.ACTIVE” on page 97 describes this parameter.

◆ Review the current value of SCF.GNS.WAITINT.

“SCF.GNS.WAITINT” on page 98 describes this parameter.



GNS group typesThe DEFINE GROUP, DEFINE ENTERPRISE [RDF1|RDF2] GROUP, and DEFINE GROUP FOR SARPOOL commands allow you to define the following device groups:

NON-ENTERPRISE group

The NON-ENTERPRISE group allows all types of devices. This is also referred to as a mainframe-only group.

NON-RDF ENTERPRISE group

The NON-RDF ENTERPRISE group does not allow the inclusion of RDF devices, but does allow the inclusion of BCV, FBA meta (head device only), and CKD meta (head device only) devices. The NON-RDF ENTERPRISE group rejects the following device types:

◆ SAVEDEV◆ COVD◆ SFS ◆ DRV ◆ R1◆ R2 ◆ VCMDB ◆ POWERVAULT

All other device types are allowed.

ENTERPRISE RDF1 group

All devices in this group must be R1. Only the head of a meta device will be included. R1 BCV devices are allowed. The ENTERPRISE R1 group rejects the following types:

◆ SAVEDEV ◆ COVD ◆ SFS ◆ DRV◆ R2◆ non-RDF ◆ VCMDB◆ POWERVAULT


ENTERPRISE RDF2 group

All devices in this group must be R2. Only the head of a meta device is included. R2 BCV devices are allowed. The ENTERPRISE R2 group rejects the following types:

◆ SAVEDEV◆ COVD◆ SFS ◆ DRV◆ R1◆ non-RDF◆ VCMDB◆ POWERVAULT


GNS group types 361


SARPOOL group

This group allows all device types with one exception — it only allows the inclusion of the head device of a meta set.

EMCGROUP JCLThe JCL required to run the EMCGROUP utility is shown in Table 11.

Example//JOBNAME JOB (),,,//JS10 EXEC PGM=EMCGROUP//SYSPRINT DD SYSOUT=A,LRECL=121,RECFM=FBA//REPORT DD SYSOUT=A,LRECL=121,RECFM=FBA//SCF$nnnn DD DUMMY//SYSIN DD *DEFINE GROUP 'UNIQUE NAME FOR THIS GROUP' - INCLUDE VOL (UPDRO1,UPDRO2,UPDRO4, - UPDR07,UPDR09) /*

Table 11 JCL required for EMCGROUP


//JOB A standard job card

//JS10 EXEC PGM=EMCGROUP The program name

//SYSPRINT DD SYSOUT=* The standard output DD where all syntax errors and processing messages will be writtenLRECL=133,RECFM=FBA

//REPORT DD Location of DISPLAY and LIST outputLRECL=133,RECFM=FBA

//SCF$nnnn Specifies the SCF subsystem where nnnn defines the instance of SCF to connect to.DD DUMMY



GNS batch commands referenceThe following sections present reference information about the GNS batch commands.

Command overview

Table 12 shows the GNS batch commands and their options.

Table 12 GNS batch commands

Command Options

DEFINE COMPLEMENT FOR GROUP basename NEWname compname

DEFINE GROUP nameDEFINE ENTERPRISE [RDF1|RDF2|ANY] GROUP name

DEFINE GROUP name FOR GCOPYBCV

DEFINE GROUP name FOR SARPOOL

INCLUDE VOLUMES = volser|mask|list

INCLUDE SMS STORAGE GROUP = name|list

[options]

INCLUDE DEVICE SYM = ser#,(symm#|list|range)

INCLUDE DEVICE CCUU = ccuu|list|range

INCLUDE RDF GROUP = ser#,(INClude=rdfgroup,...)INCLUDE RDF GROUP = ser#,((LCL=rdfgroup,RECovery=rdfgroup),...)INCLUDE RDF GROUP = ser#,(PROtect=rdfgroup,...)INCLUDE RDF GROUP = ser#,(LCL=rdfgroup,...)INCLUDE RDF GROUP = ser#,((ASYNCra=rdfgroup[,RECovery=rdfgroup],SYNCra=rdfgroup),...)

Note: GNS groups containing SYNCra, ASYNCra, and/or RECovery RA groups are intended for MSC use only and are not compatible for use with other EMC applications (e.g. Consistency Group). This type of GNS group represents an MSC definition only and cannot be expanded into devices when displayed by GNS or SRDF Host Component.

EXCLUDE DEVICE SYM = ser#,(symm#list|range)

EXCLUDE DEVICE CCUU = ccuu|list|range

EXCLUDE VOLUMES = volser|mask|list

DYNAMIC|STATIC

EXTEND

DELETE GROUP name

DISPLAY GROUP name XPANDRAG

LIST GROUP

REMOVE FROM GROUP name DEVICE SYMM = ser#,(symm#|list|range)

RENAME GROUP name NEWNAME name

GNS batch commands reference 363


Batch syntax usage

You can terminate the GNS batch commands at the end of a line, or you may continue them onto a new line by placing a blank followed by a dash after the last character on a line.

Note: GNS supports input data records greater than 72 characters in length and will parse all characters on an input line as data. Do not put sequence numbers on the input data as the sequence numbers will be parsed as data and will cause syntax errors.

DEFINE COMPLEMENT

The DEFINE COMPLEMENT command allows you to define a complement group to an existing GNS group. A GNS complement group is based on an existing GNS group and contains only those devices which are in an SRDF relationship to devices in the existing GNS group.

Note: Complement groups are a feature of EMC Consistency Group for z/OS. The EMC Consistency Group for z/OS Product Guide provides more information.

Syntax

DEFINE COMPLEMENT FOR GROUP basegroup NEWname compgroup

Parameters

basegroup

The name of the GNS group for which you want to define a complement. The name can be from 1 to 65 alphanumeric characters long.

compgroup

The name you want to give the complement group.

Note: Place quotes around the names if they contain blanks or special characters.

CommentsThe complement group is created based on the base group at a point in time. After the complement group is created, it is treated as a normal GNS group. It is not linked back to the group from which it was created. Changes to the base group after the complement group is defined do not change the complement group.

The SRDF relationship upon which a complement group is based may be any SRDF relationship, not just a synchronous (SRDF/S) relationship. The relationship may be from R1 to R2 or from R2 to R1.

Concurrent SRDF relationships are handled correctly if the base group is defined through RDF GROUP. If the base group membership contains R1 devices included specifically by device address and these devices are in a concurrent SRDF relationship, then devices on both links are included, unless the LIMIT parameter overrides the membership in the base group.



Example GNS group BASEGROUP is defined as follows:

DEFINE GROUP ‘BASEGROUP’ - INCLUDE RDF GROUP = 000184600309,(INC=00) - INCLUDE DEVICE SYMM = 000184600309,(011E)

SRDF group 00 is linked to controller 000545454545 and SRDF group 01 is the group on the other side that points back at 000184600309. The device that was explicitly included, 011E, is a non-RDF device.

To create a complement of this group, use the following syntax:

DEFINE COMPLEMENT GROUP ‘BASEGROUP’ NEW ‘OTHER’

The result of this operation is a new group created on Symmetrix number 000545454545 named OTHER. That new group contains an SRDF group INC=01.

The device 011E that was included in the BASEGROUP is dropped because it does not have a remote mirror.

DEFINE GROUP

The DEFINE GROUP command allows you to define a GNS group.

Syntax

DEFINE GROUP name [options]

Parameters

name

The group name that uniquely identifies the collection. The name can be from 1 to 65 alphanumeric characters long.

Note: Place quotes around the group name if it contains blanks or special characters.

options

A series of optional values that further define the group. Options can include:

• INCLUDE VOLUMES = volser|mask|list

Include the specified volumes in the group. You can identify the volumes by VOLSER, mask or a volume list. A mask is a partial name terminated with an asterisk (for example VOL0*).

Note: Use of masks is only valid on the INCLUDE VOLUMES and EXCLUDE VOLUMES options.

A volume list is a series of volumes enclosed in left and right parentheses with individual volumes separated by commas, for example, (VOL001,VOL002,VOL003).

• INCLUDE SMS STORAGE GROUP = SMS name| list



Include the specified SMS storage group(s) in this group. If you include a list of SMS storage groups, enclose the list in left and right parentheses and separate each SMS storage group with commas and no spaces.

The individual members of the SMS group are discovered and stored within this definition.

Note: At definition time, the Symmetrix system referenced must be online, or the definition fails. If only defining with “INCLUDE VOLUMES =”, a minimum of one volume must be online for the group to be defined.

• INCLUDE DEVICE SYM = ser#,(symm#|list|range)

Include the specified devices in the name group. When specifying the serial number, enter the full 12-digits with no dashes.

You can list the devices by:

– The Symmetrix device number

– A list of Symmetrix device numbers separated by commas

– A range of Symmetrix device numbers (two device numbers separated from each other by a dash)

Note: If you use a device number range, the devices in the range specified by the beginning and end devices must be contiguous. That is, all devices implicit in the range must be valid. If there is a device missing between the beginning and ending values, the definition is rejected.

• INCLUDE DEVICE CCUU = ccuu|list|range

Include the specified devices in the name group. You can list the devices by:

– CCUU

– A list of CCUUs

– A range of CCUUs (two CCUUs separated by a dash)

Separate each entry with a comma.

Note: If the CCUU is invalid, the definition is rejected. If you use a CCUU range, the devices in the range specified by the beginning and end devices must be contiguous. That is, all devices implicit in the range must be valid. If there is a device missing between the beginning and ending values, the definition is rejected.

For example:

INCLUDE DEVICE CCUU=8A70-8A74

Defining groups by SRDF group — ResourcePak Base provides the ability to define groups by SRDF group. Defining by SRDF group is a better method than defining groups by lists of devices because it simplifies processes when the configuration changes.



Definition of groups by SRDF group is recommended for users of Consistency Group for z/OS (ConGroup) because it simplifies changing the members of a consistency group as application needs change. All that is required is a ConGroup REFRESH after any change in the definition of an RDF group.

SRDF group data types — The following five syntax examples describe how to store different SRDF group data types within GNS.

1. To include all devices for the SRDF group, use the following syntax:

INCLUDE RDF GROUP = ser#,(INClude=rdfgroup,...)

This is a request to include all of the devices for the SRDF group. For example, when Consistency Group sees this data type, it will expand the membership of the SRDF group, include all of the devices that are members of the SRDF group, and protect both legs of any concurrent SRDF groups. GNS will not expand the group by default. To see the devices that will be included in the group, use the new XPANDRAG parameter in the DISPLAY GROUP command.

Note: When Consistency Group sees this limiting statement, it will only generate a SYMGROUP statement for the specified SRDF group. The LIMit/PROtect statement will not automatically generate the list of devices that compose the GNS group. The list of devices, if required, needs to be explicitly specified. SRDF Host Component will honor this SRDF group type by limiting its actions to the leg that corresponds to the SRDF group identified by this statement.

2. To define the SRDF/A leg and its recovery group, use the following syntax:

INCLUDE RDF GROUP = ser#,(…,(LCL=rdfgroup,RECovery=rdfgroup),…)

This is a definition of the SRDF/A leg and its recovery group in an SRDF/Star configuration. GNS will never expand the device membership of SRDF groups contained within this structure.

Note: This GNS group type is intended for MSC use only and is not compatible for use with other EMC applications (e.g., Consistency Group). It represents an MSC definition only and cannot be expanded into devices when displayed by GNS or SRDF Host Component.



3. To define the synchronous SRDF group for remote cycle switching in an SRDF/Star configuration, use the following syntax:

INCLUDE RDF GROUP = ser#,((ASYNCra=rdfgroup[,RECovery=rdfgroup],SYNCra=rdfgroup),...)

Where:

ASYNCra specifies the asynchronous (SRDF/A) SRDF group for the Site B -> Site C leg.

RECovery specifies the recovery group. This parameter is optional.

SYNCra specifies the synchronous (SRDF/S) SRDF group for the Site A -> Site B leg.

For example:

EMCP001I DEFINE GROUP 'RAOBANG' - EMCP001I INCLUDE RDF GROUP = 000190100849,((ASYNCRA=01,REC=17,SYNCRA=F0)) - EMCP001I INCLUDE RDF GROUP = 000190100849,((ASYNCRA=04,SYNCRA=17)) EGRP010I Parse complete for statement # 2

Note: This GNS group type is intended for MSC use only and is not compatible for use with other EMC applications (e.g., Consistency Group). It represents an MSC definition only and cannot be expanded into devices when displayed by GNS or SRDF Host Component.

4. To identify the leg of a concurrent set to which actions are limited, use the following syntax:

INCLUDE RDF GROUP = ser#,(PROtect=rdfgroup,…)

This syntax is intended to identify the leg of a concurrent set that you want to limit actions to. The alias for PROtect is LIMit.

Note: When Consistency Group sees this limiting statement, it will generate a SYMGROUP statement for the specified SRDF group. The LIMit/PROtect statement will not affect the list of devices that compose the GNS group. SRDF Host Component will honor this SRDF group type by limiting its actions to the R2s on the other side of the leg that corresponds to the SRDF group specified by this statement.

5. To include all of the devices for the SRDF group, but limit actions to just the mirrors on this leg, use the following syntax:

INCLUDE RDF GROUP = ser#,(LCL=rdfgroup,…)

This is a request to include all of the devices for the SRDF group, but to limit actions to just the mirrors on this leg. For example, when ConGroup sees this data type, it will expand the membership of the SRDF group, include all of the devices that are members of the SRDF group, and protect only the mirrors on the specified leg. GNS will not expand the group by default.

To see the devices that will be included in the group, use the XPANDRAG parameter in the DISPLAY GROUP command. If you want to get the SRDF group's devices returned, then the expand flag must be set. This syntax gives you the same result as if you had coded both an INC=, and a LIM= statement.

Note: Consistency Group always sets the XPANDRAG flag.



• EXCLUDE DEVICE SYM = ser#,(symm#|list|range)

Exclude the specified devices from the group. To specify the devices, include the serial number of the Symmetrix system containing the devices followed by a comma. Then, include the devices enclosed in parentheses.

Note: When specifying the serial number, enter the full 12-digits with no dashes.


– The Symmetrix device number

– A list of Symmetrix device numbers separated by commas

– A range of Symmetrix device numbers (two numbers separated from each other by a dash)

Note: The exclusion is applied at definition time and never affects inclusion by SRDF group.

• EXCLUDE DEVICE CCUU = ccuu|list|range

Exclude the specified devices from the name group.



– CCUU

– A list of CCUUs

– A range of CCUUs (two serial numbers separated by a dash)

Separate each entry with a comma.

Note: If the CCUU is invalid, the definition is rejected. If you use a CCUU range, the devices in the range specified by the beginning and end devices must be contiguous. That is, all devices implicit in the range must be valid. If there is a device missing between the beginning and ending values, the definition is rejected.

• EXCLUDE VOLUMES = volser|mask|list

Exclude the specified volumes from the group. You can identify the volumes by VOLSER, mask, or a list of VOLSERs.


A mask is a partial name terminated with an asterisk (for example VOL0*). Use of masks is only valid on the INCLUDE VOLUMES and EXCLUDE VOLUMES options.



If you include a list of VOLSERs, enclose the list in left and right parentheses and separate each VOLSER with commas and no spaces.

• DYNAMIC | STATIC

When you specify DYNAMIC, the group membership is resolved at definition time and then once again at display/access time. Any new devices that are found at this time are added into the data that is displayed.

When you specify STATIC, the group membership is only resolved at definition time. This is the default setting.

Note that you cannot change the DYNAMIC or STATIC setting after the initial definition.

• EXTEND

Adds the devices listed in other options (for example: INCLUDE VOLUMES, INCLUDE SMS STORAGE GROUP, INCLUDE DEVICE SYMM, and INCLUDE DEVICE CCUU) with the DEFINE GROUP command to the group specified in name.

If the group does not exist, DEFINE GROUP defines it and adds all specified devices. If the group does exist, DEFINE GROUP adds the devices specified to the group.

DEFINE ENTERPRISE [RDF1|RDF2] GROUP

The DEFINE ENTERPRISE GROUP command allows you to create groups that are also compatible with open systems devices. ENTERPRISE groups can be standard, RDF1, RDF2, or a mix of device types. These groups must conform to the open systems definition rules as follows:

◆ A standard group must not contain any RDF devices.

◆ An ENTERPRISE RDF1 group can be defined with devices that are the R1 or concurrent R11 devices.

◆ An ENTERPRISE RDF2 group can be defined with devices that are the R2 or concurrent R22 devices.

◆ An ENTERPRISE ANY group can contain a mix of RDF1 and RDF2 device types.

When you define an ENTERPRISE group, the ENTERPRISE validation rules will be applied to the definition. A violation of these rules may cause the DEFINE action to be rejected.

Note: Under some circumstances, GNS may reject devices and continue with the definition. In these cases, you will receive a return code 4, an appropriate reason code, and a list of devices that have been dropped. ENTERPRISE Groups cannot be extended.

Syntax

DEFINE ENTERPRISE [RDF1|RDF2|ANY] GROUP name [options]

ParametersRDF1

Specifies R1 and concurrent R11 devices.



RDF2

Specifies R2 and concurrent R22 devices.

ANY

ANY can contain a mix of RDF1 and RDF2 device types.

Note: The ANY group type pertains to ResourcePak Base V7.2 and higher, and if used with versions lower than 7.2, an error message stating “Unknown” or “Invalid” group type is generated.

name

The name of the GNS group. The name can be from 1 to 65 alphanumeric characters long.


options

The options are identical to those used by the DEFINE GROUP command. “DEFINE GROUP” on page 365 describes this command.

DEFINE GROUP FOR GCOPYBCV

The DEFINE GROUP FOR GCOPYBCV command allows you to define a GNS Gold Copy BCV Group. Only BCV devices may be included in a Gold Copy BCV Group. More BCVs can be added to an existing Gold Copy BCV Group by issuing a subsequent DEFINE command for that group and specifying the EXTEND parameter.

When a Gold Copy BCV Group is supplied to Gold Copy, the group is utilized as follows:

◆ If a STD has a relationship with a BCV and a Gold Copy BCV Group was specified, the group is checked. If the BCV is not in the group and a suitable BCV is not found, an error is returned.

◆ If a STD has a relationship with multiple BCVs and a Gold Copy BCV Group was specified, the group is checked. If the first (lowest) BCV is in the group, it will be used, otherwise if none of the BCVs are in the group and a suitable BCV is not found, an error is returned.

SyntaxDEFINE GROUP name FOR GCOPYBCV [options]

Note: The options for Gold Copy BCV Groups are identical to those on the DEFINE GROUP command. “DEFINE GROUP” on page 365 describes this command and the options available.




DEFINE GROUP FOR SARPOOL

The DEFINE GROUP FOR SARPOOL command allows you to define a GNS group. The devices defined in this group will be locked and reserved for use by the SRDF/AR pooling feature.

Syntax

DEFINE GROUP name FOR SARPOOL[options]

Note that SARPOOL group names are limited to 55 characters. Otherwise, the options are identical to those used by the DEFINE GROUP command. “DEFINE GROUP” on page 365 describes this command.


DELETE GROUP

The DELETE GROUP command allows you to delete a GNS group.

Syntax

DELETE GROUP name

Parametersname

The name of the GNS group to delete. The name can be from 1 to 65 alphanumeric characters.


DISPLAY GROUP

The DISPLAY GROUP command allows you to display the contents of a GNS group.

Syntax

DISPLAY GROUP name XPANDRAG

Parameters

name

The group name that uniquely identifies the collection. The name can be from 1 to 65 alphanumeric characters.


XPANDRAG

This optional parameter must follow immediately after the group name. It expands the SRDF group to show the devices that belong to the SRDF group(s) included within the definition.



LIST GROUP

The LIST GROUP command allows you to list all currently defined groups.

For syntax and examples, refer to “GNS,LIST” on page 182.

REMOVE FROM GROUP

The REMOVE FROM GROUP command allows you to remove devices from a group.

Syntax

REMOVE FROM GROUP name DEVICE SYMM = ser#,(symm#|list|range)

Parameters

name

The current group name. The name can be from 1 to 65 alphanumeric characters.


DEVICE SYMM = ser#,(symm#|list|range)

Include the specified devices in the name group. To specify the devices, include the serial number of the Symmetrix system containing the devices followed by a comma. Then, include the devices enclosed in parentheses.

Note: When specifying the serial number, enter the full 12-digits with no dashes.


• The Symmetrix serial number

• A list of Symmetrix serial numbers separated by commas

• A range of serial numbers (two serial numbers separated from each other by a dash)

Note: If you use a serial number range, the devices in the range specified by the beginning and end devices must be contiguous. That is, all devices implicit in the range must be valid. If there is a device missing between the beginning and ending values, the definition is rejected.



RENAME GROUP

The RENAME GROUP command allows you to rename the group you specify.

Syntax

RENAME GROUP name NEWNAME newname

Parametersname

The current group name. The name can be from 1 to 65 alphanumeric characters.

newname

The new group name you want to assign. The name can be from 1 to 65 alphanumeric characters.

Note: Place quotes around the group names if they contain blanks or special characters.



Working with groupsThe following sections discuss how to work with groups.

Defining groups

This section includes samples used to create groups.

Defining a group by volumeThe following sections show an example of a DEFINE GROUP job stream defining a group by volume and the resulting SYSPRINT output.

Example

//USERJOB JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB04846//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * DEFINE GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’ - INCLUDE VOLUMES = U*/*

SYSPRINT

EGRP010I PARSING STATEMENT # 1 EMCP001I DEFINE GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’ - EMCP001I INCLUDE VOL (U*)

EGRP010I PARSE complete. 1 statement parsed.********************************************************************************

EGRP020I Begin Executing Statement # 1 EGRP090I DEFINE OF GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’ COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 1

********************************************************************************

Defining a group by Symmetrix deviceThe following sections show an example of a DEFINE GROUP job stream defining the group by Symmetrix devices and the resulting SYSPRINT output and report.

Example

//DEFINE2 JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB07640//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * DEFINE GROUP 'Sample Define by Device' - INCLUDE DEVICE SYMM = 000187790034,(2B,3C) DISPLAY GROUP 'Sample Define by Device'

SYSPRINT

EGRP010I PARSING STATEMENT # 1

Working with groups 375


EMCP001I DEFINE GROUP 'Sample Define by Device' - EMCP001I INCLUDE DEVICE SYMM = 000187790034,(2B,3C)

EMCP001I DISPLAY GROUP 'Sample Define by Device' EGRP010I PARSE complete. 2 statements parsed.******************************************************** EGRP020I Begin Executing Statement # 1 EGRP090I DEFINE OF GROUP 'Sample Define by Device' COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 1 EGRP020I Begin Executing Statement # 2 EGRP120I DISPLAY OF GROUP 'Sample Define by Device' COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 2 ********************************************************

Report

1 GNS Display Request Output PAGE 001 DEFINE GROUP 'Sample Define by Device' - INCLUDE DEVICE SYMM = 000187790034,(002B, 003C)

Defining Gold Copy BCV Groups The following is a simple example of defining a Gold Copy BCV Group (some devices in the range could not be added because they are not BCVs).

Example

EMCP001I DEFINE GROUP 'DTGCOPYBCV' FOR GCOPYBCV -EMCP001I INCLUDE DEVICE SYMM = 000195700080,(0400-043F) EGRP010I Parse complete for statement # 1

EGRP020I Begin Executing Statement # 1 EGRP090I DEFINE OF GROUP 'DTGCOPYBCV' COMPLETED WITH RETURN CODE: 4-31 REASON 31 = A DEVICE HAS INCORRECT TYPE FOR GROUP. Validating controller 000195700080 against Gold Copy BCV rules The following devices are standard devices and cannot be added to a Gold Copy BCV Group: 0400 0401 0402 0403 0404 0405 0406 0407 0408 0409 040A 040B 040C 040D 040E 040F 0410 0411 0412 0413 0414 0415 0416 0417 0419 041A 041B 041C 041D 041E 041F 0420 0421 0422 0423 0424 0425 0426 0427 0428 0429 042A 042B 042C 042D 042E 042F EGRP021I Processing Ended For Statement # 1

The following is an example of displaying the resulting Gold Copy BCV Group (only the BCV devices were successfully added).

Example

EMCP001I DISPLAY GROUP 'DTGCOPYBCV'EGRP010I Parse complete for statement # 1

GNS Display Request Output 10/16/2012 11:52:55 PAGE 001 DEFINE GROUP 'DTGCOPYBCV' - FOR GCOPYBCV -* PARTICIPATING CONTROLLER = 000195700080 INCLUDE DEVICE SYMM = 000195700080,(0430-043F)



Defining SRDF groupsThe following section shows an example of DEFINE GROUP using the INCLUDE RDF GROUP option to create SRDF groups, and the resulting SYSPRINT output and report.

Example

//USERJOB JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB06732//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * DELETE GROUP 'INCGRP04U6A' DEFINE GROUP 'INCGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(INCLUDE=04) ==> if concurrent, ConGroup

will protect both, DELETE GROUP 'INCGRP0BU6A' will expand devices DEFINE GROUP 'INCGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(INCLUDE=0B) DELETE GROUP 'LCLGRP04U6A' DEFINE GROUP 'LCLGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(LCL=04) ==> if concurrent, will only

use leg defined, DELETE GROUP 'LCLGRP0BU6A' will expand devices DEFINE GROUP 'LCLGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(LCL=0B) DELETE GROUP 'PROGRP04U6A' DEFINE GROUP 'PROGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(LIMIT=04) ==> will only generate

"symgroup" stmt, won't DELETE GROUP 'PROGRP0BU6A' expand devices DEFINE GROUP 'PROGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(LIMIT=0B)

SYSPRINT

EMCP001I DELETE GROUP 'INCGRP04U6A'EGRP010I Parse complete for statement # 1

EMCP001I DEFINE GROUP 'INCGRP04U6A' -EMCP001I INCLUDE RDF GROUP = 000000006185,(INCLUDE=04)EGRP010I Parse complete for statement # 2

EMCP001I DELETE GROUP 'INCGRP0BU6A'EGRP010I Parse complete for statement # 3

EMCP001I DEFINE GROUP 'INCGRP0BU6A' -EMCP001I INCLUDE RDF GROUP = 000000006185,(INCLUDE=0B)EGRP010I Parse complete for statement # 4

EMCP001I DELETE GROUP 'LCLGRP04U6A'EGRP010I Parse complete for statement # 5

EMCP001I DEFINE GROUP 'LCLGRP04U6A' -EMCP001I INCLUDE RDF GROUP = 000000006185,(LCL=04)EGRP010I Parse complete for statement # 6

EMCP001I DELETE GROUP 'LCLGRP0BU6A'EGRP010I Parse complete for statement # 7EMCP001I DEFINE GROUP 'LCLGRP0BU6A' -EMCP001I INCLUDE RDF GROUP = 000000006185,(LCL=0B)EGRP010I Parse complete for statement # 8



EMCP001I DELETE GROUP 'PROGRP04U6A'EGRP010I Parse complete for statement # 9

EMCP001I DEFINE GROUP 'PROGRP04U6A' -EMCP001I INCLUDE RDF GROUP = 000000006185,(LIMIT=04)EGRP010I Parse complete for statement # 10

EMCP001I DELETE GROUP 'PROGRP0BU6A'EGRP010I Parse complete for statement # 11

EMCP001I DEFINE GROUP 'PROGRP0BU6A' -EMCP001I INCLUDE RDF GROUP = 000000006185,(LIMIT=0B)EGRP010I Parse complete for statement # 12

EGRP010I PARSE complete. 12 statements parsed.********************************************************************

EGRP020I Begin Executing Statement # 1EGRP100I DELETE OF GROUP 'INCGRP04U6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 1

EGRP020I Begin Executing Statement # 2EGRP090I DEFINE OF GROUP 'INCGRP04U6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 2

EGRP020I Begin Executing Statement # 3EGRP100I DELETE OF GROUP 'INCGRP0BU6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 3

EGRP020I Begin Executing Statement # 4EGRP090I DEFINE OF GROUP 'INCGRP0BU6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 4

EGRP020I Begin Executing Statement # 5EGRP100I DELETE OF GROUP 'LCLGRP04U6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 5

EGRP020I Begin Executing Statement # 6EGRP090I DEFINE OF GROUP 'LCLGRP04U6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 6

EGRP020I Begin Executing Statement # 7EGRP100I DELETE OF GROUP 'LCLGRP0BU6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 7

EGRP020I Begin Executing Statement # 8EGRP090I DEFINE OF GROUP 'LCLGRP0BU6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 8

EGRP020I Begin Executing Statement # 9



EGRP100I DELETE OF GROUP 'PROGRP04U6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 9

EGRP020I Begin Executing Statement # 10EGRP090I DEFINE OF GROUP 'PROGRP04U6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 10

EGRP020I Begin Executing Statement # 11EGRP100I DELETE OF GROUP 'PROGRP0BU6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 11

EGRP020I Begin Executing Statement # 12EGRP090I DEFINE OF GROUP 'PROGRP0BU6A' COMPLETED WITH RETURN CODE: 0-0 REASON 0 = OKEGRP021I Processing Ended For Statement # 12

Displaying SRDF groups

The following section shows an example of DISPLAY GROUP with the XPANDRAG option to display SRDF groups, and the resulting report.

Example

//USERJOB JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB06733//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * DISPLAY GROUP 'INCGRP04U6A' XPANDRAG DISPLAY GROUP 'INCGRP0BU6A' XPANDRAG DISPLAY GROUP 'LCLGRP04U6A' XPANDRAG DISPLAY GROUP 'LCLGRP0BU6A' XPANDRAG DISPLAY GROUP 'PROGRP04U6A' XPANDRAG DISPLAY GROUP 'PROGRP0BU6A' XPANDRAG

Report

GNS Display Request Output PAGE 001

DEFINE GROUP 'INCGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(INC=04) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(00A0-00A4, 01D0-01D4, - 0546, 054B, 0550, 0555, 055A)

DEFINE GROUP 'INCGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(INC=0B) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(00A1-00A4, 01D0-01D4, - 0238, 0546, 054B, 0550, 0555, 055A)

DEFINE GROUP 'LCLGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(LCL=04) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(00A0-00A4, 01D0-01D4, -



0546, 054B, 0550, 0555, 055A)

DEFINE GROUP 'LCLGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(LCL=0B) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(00A1-00A4, 01D0-01D4, - 0238, 0546, 054B, 0550, 0555, 055A)

DEFINE GROUP 'PROGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(LIM=04) -* PARTICIPATING CONTROLLER = 000000006185

DEFINE GROUP 'PROGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(LIM=0B) -* PARTICIPATING CONTROLLER = 000000006185

Displaying groups

The following sections show an example of DISPLAY GROUP, and the resulting SYSPRINT output and report.

Example

//USERJOB JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB04847//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * DISPLAY GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’/*

SYSPRINT

EGRP010I PARSING STATEMENT # 1 EMCP001I DISPLAY GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’

EGRP010I PARSE complete. 1 statement parsed.********************************************************************************

EGRP020I Begin Executing Statement # 1 EGRP120I DISPLAY OF GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’ COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 1

********************************************************************************

Report

1 GNS Display Request Output PAGE 001

DEFINE GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’ - INCLUDE VOLSER = U* - * PARTICIPATING CONTROLLER = 000184500120 * PARTICIPATING CONTROLLER = 000187790072 * PARTICIPATING CONTROLLER = 000187790034 * PARTICIPATING CONTROLLER = 000184600058 * PARTICIPATING CONTROLLER = 000184600045 INCLUDE DEVICE SYMM = 000184600045,(0004-0005, 0012, 0014-0015, - 0024-0025, 0034-0035, 00A4-00A5, 00B4-00B5, 00C4-00C5, - 00D4-00D5, 0122, 012A, 0162, 016A, 0224-0225, 0234-0237, - 0242, 024A, 0254-0255, 0264-0265, 02D2, 0312, 031A, - 0344-0345) - INCLUDE DEVICE SYMM = 000184600058,(0004-0005, 0008, 0013-0015, - 0024-0025, 00E4-00E5, 00F4-00F5, 0104-0105, 0114-0115, -



01A2, 01AA, 01E2, 01EA, 0224-0225, 0234-0235, 0242, - 024A, 0254-0255, 0264-0265, 02D2, 0332, 033A) - INCLUDE DEVICE SYMM = 000184500120,(0006, 001E-0021, 005B-005F) - INCLUDE DEVICE SYMM = 000187790034,(001A-001B, 002A-002B, - 0042-0043, 032C-032D, 036C-036D) - INCLUDE DEVICE SYMM = 000187790072,(0080)

Listing groups

The following sections show an example of LIST GROUP and the resulting SYSPRINT output and report.

Example

//USERJOB JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB04840//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * LIST GROUP/*

SYSPRINT

EGRP010I PARSING STATEMENT # 1 EMCP001I LIST GROUP EGRP010I PARSE complete. 1 statement parsed.******************************************************** EGRP020I Begin Executing Statement # 1 EGRP120I LIST GROUP COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 1 ********************************************************

Report

1

Groups on Controller = 000184500120 ’MULTIPLE VOLSER’ Groups on Controller = 000182503028 ’JOINT UNIX MAINFRAME’ ’PPPNT UNIX MAINFRAME’ ’PPPOND MAINFRAME GROUP’ ’SECOND MAINFRAME GROUP’ ’THIRD MAINFRAME GROUP’ Groups on Controller = 000187790072 ’MULTIPLE VOLSER’

Deleting groups

The following sections show an example of DELETE GROUP and the resulting SYSPRINT output.

Example

//USER JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB04839//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*



//SYSOUT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * DELETE GROUP ’Record_#_7’/*

SYSPRINT

1 EGRP010I PARSING STATEMENT # 1 EMCP001I DELETE GROUP ’Record_#_7’

EGRP010I PARSE complete. 1 statement parsed. *****************************************************************************

EGRP020I Begin Executing Statement # 1 EGRP100I DELETE OF GROUP ’Record_#_7’ COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 1

*****************************************************************************

Renaming groups

The following sections show an example of RENAME GROUP and the resulting SYSPRINT output.

Example

//RENAME JOB (EMC),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID JOB03828//JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//REPORT DD SYSOUT=*//SCF$nnnn DD DUMMY//SYSIN DD * RENAME GROUP 'Sample Define by VolumeS' - NEWNAME 'Sample new group renamed from old'

SYSPRINT

EGRP010I PARSING STATEMENT # 1 EMCP001I RENAME GROUP 'Sample Define by VolumeS' - EMCP001I NEWNAME 'Sample new group renamed from old' EGRP010I PARSE complete. 1 statement parsed.******************************************************** EGRP020I Begin Executing Statement # 1 EGRP110I RENAME OF GROUP 'Sample Define by VolumeS' TO 'Sample new group renamed from old' COMPLETED WITH RETURN CODE: 0-0 EGRP021I Processing Ended For Statement # 1 ********************************************************

Defining SRDF/AR device replacement pools

EMC SRDF/Automated Replication (SRDF/AR) is an automation solution that uses both SRDF and TimeFinder to provide a periodic asynchronous replication of a restartable data image. SRDF/AR is a continuously running service. However, if a physical drive on the Symmetrix system goes bad, SRDF/AR will immediately halt when a request fails and cannot resume until the device is replaced.



Device replacement pools for SRDF/AR (or SARPOOLs) are provided to prevent SRDF/AR from halting due to device failure. In effect, SARPOOLs are simply a group of devices that are unused until SRDF/AR needs one of them.

For each SARPOOL, GNS allows you to define and name a group where the devices are located on different Symmetrix systems. You can add and delete devices from the group as events happen.

The following steps illustrate the process:

1. Define a group of devices as a SARPOOL and give this group a name.

The group must consist of unused devices of the same type as the devices in the SRDF/AR configuration. This group should include devices on all the Symmetrix systems in the SRDF/AR configuration.

2. Start SRDF/AR.

3. SRDF/AR receives a failure because a device has malfunctioned. It needs to replace the device with a device from the SARPOOL.

SRDF/AR looks in the SARPOOL for a device on that Symmetrix system that has the same characteristics as the failed device. If it finds a matching device, it removes the replacement device from the SARPOOL and gives it to SRDF/AR. The failed device is moved to the "pending" pool, an internally generated SARPOOL.

4. SRDF/AR takes the replacement device, performs the necessary resynchronization, and continues.

SARPOOL health checkerThere is an additional component in the process — the SARPOOL health checker. The health checker is an SCF task that periodically checks all the devices in both the SARPOOL and the pending pool.

When a device fails on a Symmetrix system, it is moved to the pending pool. Periodically the health checker checks all the devices in the pending pool, and when a device becomes usable again (typically after it has been replaced), it is moved back to the SARPOOL.

The health checker also checks the SARPOOL to make sure that the devices in the pool are healthy. If it finds a failed device, it moves the device to the pending pool. This ensures that SRDF/AR is not issued a bad device.

Defining a SARPOOLTo define a pool of devices for SRDF/AR, use the EMCGROUP batch utility and the SARPOOL keyword.

Example

DEFINE GROUP PROD_SAR FOR SARPOOL - INCLUDE DEVICE SYMM = 000184600045,(0004,0005)

The "FOR SARPOOL" clause designates this pool as a special pool exclusively for use with SRDF/AR. If this clause is not used, SRDF/AR will not be able to use it and the health checker will not maintain it. “DEFINE GROUP FOR SARPOOL” on page 372 describes this command.



The SARPOOL definition only allows you to define the group using Symmetrix device numbers. The SARPOOL should contain spare devices from all the Symmetrix systems in which SRDF/AR is used.

Example

DEFINE GROUP PROD_SAR FOR SARPOOL EXTEND - INCLUDE DEVICE SYMM = 000184600045,(0004,0005) - INCLUDE DEVICE SYMM = 000184600182,(0088,0089) - INCLUDE DEVICE SYMM = 000184600671,(1360-136F) - INCLUDE DEVICE SYMM = 000184600926,(0120-0127,0450-045F,0880,0882) - INCLUDE DEVICE SYMM = 000184600123,(2340-235F,2C10-2C3F)

A device can be defined in only one SARPOOL. The TimeFinder (TF) device lock is received for the devices in a SARPOOL. If a device is locked by some other application, you will not be able to add it to the SARPOOL and messages will inform you of that situation.

Note: “Recovery services commands” on page 309 describes commands to query and free TimeFinder device locks.

The "pending" pool name for the SARPOOL is defined as the pool name with _PNDREP (pending repair or replacement) appended to the name. For example, if the SARPOOL name is PROD_SAR, then another SARPOOL with the name PROD_SAR_PNDREP will be generated as needed. This group can be displayed, changed, etc. by the GNS batch utility.

Observe the following rules when defining SRDF/AR device pools:

◆ Devices can only be replaced by devices in the same Symmetrix system.

◆ For static RDF pairs, define only the R1 device in the SARPOOL. When an R1 or R2 device fails, the R1/R2 pair will be replaced by another pair from the pool.

◆ When a device in a dynamic RDF pair fails, only that device will be replaced.

GNS reason codesGroup Name Services can return errors in the form of reason codes. Refer to “Group Name Services reason codes” on page 578.


CHAPTER 7Managing Devices and Pools

Invisible Body Tag

This chapter describes how to manage pools and devices using the General Pool Management environment.

◆ Configuring Virtual Provisioning ............................................................................ 386◆ Managing devices in pool storage ......................................................................... 386◆ General Pool Management commands .................................................................. 390◆ Running GPM in batch mode ................................................................................. 392◆ GPM command examples...................................................................................... 397

◆ Creating a VP in a Symmetrix System ............................................................. 397◆ Pool management example ........................................................................... 402◆ MOVE with REBIND example .......................................................................... 408◆ DRAIN process example................................................................................. 409◆ REBALANCE process example ........................................................................ 411◆ VP compression examples ............................................................................. 413

◆ Suggested VP compression command sequence .................................................. 418

Managing Devices and Pools 385

Managing Devices and Pools

Configuring Virtual ProvisioningSymmetrix Virtual Provisioning™ (VP) provides for the separation of physical storage devices from storage devices as perceived by the host systems. The actual physical storage is not perceived by the host. This separation allows alterations in the physical storage to occur without causing changes which affect the hosts. The result is nondisruptive provisioning. Virtual Provisioning provides the ability to define to the host servers an apparent disk configuration that is far larger than current needs. It may be possible to provision an amount of storage for applications which will last the life of the applications themselves. This means applications need to be disrupted much less frequently to make changes or add storage.

Virtual Provisioning also simplifies the choices of which volumes to use for which files. Whether these choices are made by people or software, the choices will be less often restricted by limited space. Wide striping allows the data to be spread evenly across a broad pool. It allows all data in an application group, known in this case as a thin pool (also called a Virtual Pool), to be spread fairly evenly across all the drives supporting that group. This balancing of the workload across physical devices can translate into improved performance. It can reduce queuing and smooth out response times. It also reduces performance management effort.

The Virtual Provisioning feature introduces three new concepts: thin devices, data devices, and thin pools. Thin devices (also called thin VP devices) can be created with an inflated capacity, because the actual storage space for the data written to the thin devices is on the data devices. In this way, when additional storage is needed, more data devices can be added to the thin pool.

Managing devices in pool storageResourcePak Base provides a set of General Pool Management (GPM) commands that can be executed online or in batch mode. Devices in pool storage are a predefined set of devices that provide a pool of physical space.

Devices within a pool are not host-accessible, and include the following:

◆ Unassigned Save devices

◆ Unassigned Data devices

◆ SNAPPOOL devices

Virtual devices (VDEVs) are used by TimeFinder/Clone Mainframe Snap Facility. VDEVs make use of SNAPPOOL devices to store pre-update images of tracks changed on the source device or new writes to the virtual devices. This results in replicas that are space-efficient (that is, they consume less real space than their sources).

◆ DSEPOOL devices

SRDF/A DSEPOOL (Delta Set Extension) devices provide space to save devices when the cache resources in an SRDF/A source Symmetrix system reach the SRDF/A limit. This extra space permits SRDF/A to keep running during transient problems such as temporary link loss.



◆ THINPOOL devices

THINPOOL devices are data devices that provide the actual storage for virtual provisioning.

Unassigned Save devices may be assigned as SNAPPOOL or DSEPOOL devices. Conversely, these devices can be drained and returned to the default pool.

Multiple SNAPPOOLs or DSEPOOLs can be created to isolate workloads. This alleviates contention for device space among several users and lessens the possibility of a single pool consuming all the available space.

Note: SNAP pools are available starting with Enginuity level 5x71. DSE pools are available starting with Enginuity level 5772. Thinpools are available with Enginuity level 5773 for FBA devices only. Enginuity level 5876 ,and higher, supports THINPOOLs for both FBA and CKD devices.

Planning for pool device use

When a pool is created, it is created as either a SNAPPOOL, a DSEPOOL, or a THINPOOL. These pools consist of save devices or data devices which are specifically configured to be used for pools. These devices are not host-accessible, but do consume Symmetrix device numbers.

Two special pools, DEFAULT_POOL and DF_DDEV_POOL, contain devices that have not been assigned to any named pools and are available for SNAPPOOL, DSEPOOL, and THINPOOL operations. The devices in DEFAULT_POOL and DF_DDEV_POOL can be either enabled or disabled.

◆ Save devices that do not belong to any pool or that belong to the DEFAULT_POOL are available to be added to an existing SNAPPOOL or DSEPOOL. Once they are enabled, save devices in a pool are available for use.

◆ Data devices that do not belong to any pool or that belong to the DF_DDEV_POOL are available to be added to an existing THINPOOL. Once they are enabled, data devices in a pool are available for use.

Save devices can be removed from a SNAPPOOL or DSEPOOL and data devices can be removed from a THINPOOL, but the devices must first be "drained" and disabled. Drained devices will become inactive within their pool and can then be moved out of the pool to be available for other pools.

Pool statistics and alerting mechanisms can be monitored. EMC provides a monitor function within ResourcePak Base that advises you when you are reaching predetermined thresholds within the save pools. The monitor functionality is described in Chapter 8, “Monitoring Pool Usage.” User exits can be created based on your site-specific policies.

Managing devices in pool storage 387


Pool Device Geometry

A device to be added to a thin, DSE, or Snap pool must be compatible with the pool type and with any devices already in the pool. Compatibility requirements include:

◆ A device to be added to a thin pool must be a data device.

◆ A device to be added to a DSE or Snap pool must be a save device.

◆ A device to be added to a pool that already contains one or more devices must have the same emulation type and protection type as the devices already in the pool. Additionally, a device to be added to a pool on a Symmetrix system at Enginuity level 5875 and higher must have the same storage class (for example, Fibre or SATA) and drive speed as the device(s) already in the pool.

SRDF/A DSE Pools

Devices within an SRDF/A DSE pool must have the same emulation, track size, and number of cylinders as their associated source device. They must also meet the requirements defined in “Pool Device Geometry.”

If an enterprise SRDF/A implementation contains both FBA and 3390 (CKD) devices, two DSE pools should be configured, one for FBA devices and one for 3390 devices.

A single SRDF/A DSE pool can be associated (shared) with multiple SRDF/A groups.

A single SRDF/A group can have a maximum of four SRDF/A DSE pools associated with it. For example, each pool can have a different device type; there can be one FBA, one 3390 (CKD), one 3380 (CKD), and one AS400 (iSeries) pool associated with a single group.

Limitations

For ResourcePak Base version 7.4 and higher, the following limitations apply.

Device creationCreating virtual, or thin devices (TDEVs and TDATs) is provided using EMC SymmWin, SMC, or the Solutions Enabler SYMCONFIGURE command. Mainframe Enablers cannot create virtual devices.

FAST and FAST VP controlsFAST and FAST VP controls for CKD are provided using EMC SMC or Solution Enabler SYMFAST command. Mainframe Enabler does not provide FAST or FAST VP control management.

FBA Meta handling limitationsWhen an FBA Meta head is encountered in the specified device range of a GPM command, all associated FBA Meta members are automatically included. The member devices are validated according to the same rules applying to the head device.

When an FBA Meta member is encountered in the specified device range of a GPM command, it is bypassed. Subsequently, the member is validated as part of an FBA Meta group. At the completion of device validation, any FBA Meta members that were not validated as part of an FBA Meta group will cause the action to fail unless SKIP was specified.



If any FBA Meta members are added to the devices processed, the added devices are listed in a message indicating this.

Binding limitationThere is a certain amount of meta data overhead for thin data device mapping to a pool. Due to this overhead, you cannot fully provision a number of devices to a pool and expect to bind each device. In a fully provisioned pool, the number of devices you can bind is lower than the number of devices you have preallocated to the pool.

Binding limitation = slightly less than the number of devices preallocated to the pool.

Managing devices in pool storage 389


General Pool Management commandsGPM commands for VP pool and device management can be executed in either online or batch mode, as follows:

◆ In batch mode, GPM commands can be executed by the program ESFGPMBT.

◆ For online mode, you can:

– Use the z/OS MODIFY command. The syntax is:

F <scfjobname>,GPM,<action> <parameters>

– Or, take advantage of the Command Prefix Facility (CPF) for SCF where you can enter SCF commands using CPF rather than using the MODIFY command. For example, if the CPF name is @123, then the command:

F scf,GPM,ADD LCL(UNIT(3800) DEV(28E) POOL (EMCCKDVP)

can be entered as:

@123 GPM,ADD LCL(UNIT(3800) DEV(28E) POOL (EMCCKDVP)

Refer to Chapter 3, “Configuration File and Initialization Parameters,” for more information on the SCF.INI.CPFX initialization parameter and ResourcePak Base configuration file.

◆ You can use the DEBUG keyword to generate command-level diagnostic information that does not affect the outcome of the command. This diagnostic information is written to module-specific DDs DBUGPMBT, DBUGPMCM, and DBUGPMSD. To avoid unnecessary overhead, specify this option only when requested by technical support and only on the commands for which diagnostics are requested.

To generate diagnostics for select commands only, specify the DEBUG keyword on the selected commands, and do not specify PARM=DEBUG on the batch JCL EXEC statement.

Note: For examples of GPM commands and displays, refer to “GPM command examples” on page 397.

Note: Many GPM commands are executed on the Symmetrix system as background tasks, and may continue to run when control is returned after issuing the command. Use the QUERY TASKS command to view active tasks.

GPM pool commands

GPM pool-oriented commands include:

“CREATE” on page 206 Create a thin, DSE or Snap pool.

“DELETE” on page 214 Delete an empty pool.

“DISPLAY” on page 220 Display pool information.

“POOLATTR” on page 253 Specify pool-level attributes.

“REBALANCE” on page 285 Initiate leveling allocated tracks within a pool.

“RENAME” on page 296 Change the name of a pool.



GPM device commands

GPM device-oriented commands include:

Prior version CONFIGPOOL batch commands

Prior to version 7.4, pool management consisted only of a batch utility and a set of CONFIGPOOL commands. While these command have been replaced by the GPM commands, ResourcePak Base version 7.4 and higher will continue to recognize and support these previous commands and keywords.

However, EMC recommends that you eventually replace these commands with the new GPM commands to take advantage of their flexibility and recognized support.

“ADD” on page 188 Add one or more back-end devices to a pool.

“ALLOCATE” on page 192 Allocate tracks to prepare thin device(s) in a pool.

“BIND” on page 196 Bind one or more thin devices to a thin pool.

“COMPRESS” on page 201 Compress data for one or more thin devices.

“DECOMPRESS” on page 210 Decompress data for one or more thin devices.

“DISABLE” on page 216 Change the status of one or more pool devices from active to inactive.

“DRAIN” on page 229 Initiate reassignment of allocated tracks to other devices within the pool.

“ENABLE” on page 233 Change the status of one or more devices from inactive to active.

“HALTTASK” on page 236 Halt background task for thin devices.

“HDRAIN” on page 240 Halt draining activity of devices.

“MOVE” on page 244 Move allocations for thin device(s) to the pool where they are currently bound.

“PERSIST OFF” on page 249 Turn off persistence for all tracks allocated for the specified thin device or devices.

“QUERY {parameter}” on page 259 Display information about device entities.

“REBIND” on page 289 Change the pool to which a thin device is bound.

“REMOVE” on page 293 Remove an inactive device from a pool.

“UNBIND” on page 299 Unbind one or more thin devices from a pool.

“USR_NRDY” on page 303 Change device’s control unit status to user-not-ready.

“USR_RDY” on page 306 Change device’s control unit status to user-ready.



Running GPM in batch modeThis section describes the following topics for running GPM commands in batch mode:

◆ Sample JCL job stream

◆ Return codes

◆ Conditional processing

Sample JCL job stream

The following is a sample JCL job stream:

//jobname JOB job-statement-parameters//stepname EXEC PGM=ESFGPMBT,REGION=0M//STEPLIB DD DISP=SHR,DSN=load-library-dsname//SCF$NNNN DD DUMMY//GPMPRINT DD SYSOUT=*//GPMINPUT DD * one or more GPM commands, each beginning with a new statement

Notes on the sample batch JCL:

◆ The GPMINPUT DD statement defines the file containing the command(s) to be processed, either as a SYSIN file as shown, or a dataset containing 80-byte records. Any record with a asterisk in position 1 is treated as a comment and skipped, however, comment records are listed in the output file. Except for conditional processing commands (“Conditional processing” on page 393), a command may be continued on the next record by placing a hyphen as the last non-blank character on the record.

◆ The GPMPRINT DD statement specifies the output from the commands, either a SYSOUT file as shown or a sequential dataset or PDS member. This file also includes an echo of each input record including comments.

◆ The region size must be more than four megabytes. REGION=0M allows the address space to allocate virtual memory as required. REGION=0M is the preferred setting and should be specified on the JOB and/or EXEC statements.

◆ "PARM=DEBUG may be added to the EXEC statement to generate diagnostic information for all commands and does not affect the outcome of the commands. This diagnostic information is written to module-specific DDs DBUGPMBT, DBUGPMCM, and DBUGPMSD. Since this option generates diagnostics for all commands, it can generate a very large amount of output.

To avoid unnecessary overhead, specify this option only when requested by technical support. To generate diagnostics for select commands only, specify the DEBUG keyword on the commands for which diagnostics are requested, and do not specify PARM=DEBUG on the EXEC statement.



Return codes

The return code from a job step that invokes pool management services is the highest return code from among all commands that were processed. The following return codes are produced by commands under the indicated conditions:

0 The command is considered successful because one of the following applies:

– If a device oriented action was requested, the command was successful for all requested devices.

– If a device-oriented action was requested, some devices were not eligible for processing but SKIP was specified and all eligible devices were successfully processed.

– Eligible devices were being processed in the background and the action had neither completed nor failed for one or more devices after the designated number of poll requests was issued but the remaining devices were successfully processed.

– Eligible devices were being processed in the background; the action had neither completed nor failed for all eligible devices after the designated number of poll requests was issued.

4 No processing error occurred, but no devices were successfully processed

– No eligible devices were found

8 A processing error occurred

– For a device-oriented action, the action failed for one or more eligible devices, although some devices may have been processed successfully.

– For an action that is not device-oriented, the action failed.

Conditional processing

By default, when multiple commands are found in the batch input file, command processing continues when each executed command returns a zero return code. When a non-zero return code is encountered, the remaining commands are skipped. In either case, the return code from the job step in which the commands are executed is the maximum return code from the executed commands.

This behavior can be modified by means of conditional processing. To facilitate conditional processing, the maximum return code among all previously processed commands and the return code from the most recently executed command are retained. These values are updated as each command completes. Conditional processing control statements are provided in the batch input stream to allow control of the execution of commands based upon these values. The conditional processing control statements are IF, ELSE, ENDIF and RESET.

The unit of conditional processing is the IF/ENDIF range, which consists of an IF statement and a corresponding ENDIF statement, together with a set of commands and an optional ELSE statement, appear in the input stream. The logic flow follows these rules:

◆ When an IF statement is encountered, it is evaluated. If the condition on the statement is true, the following commands are processed until the next conditional processing statement is encountered.

Running GPM in batch mode 393


◆ When the condition on the statement is not true, the following commands are skipped until the next conditional processing statement is encountered.

◆ When an ELSE statement is found and the preceding IF statement condition was not satisfied, the commands between the ELSE and the ENDIF statement are processed.

There can be any number of commands between an IF statement and the corresponding ELSE or ENDIF statement, and between an ELSE statement and the corresponding ENDIF statement. All such commands are subject to the condition code value at the time the IF statement was processed, even if the value of the applicable condition code has been changed by one of the intervening commands.

If the EXIT keyword is specified on the IF statement, no IF/ENDIF range is established and no ENDIF statement is required. Instead, the condition on the IF statement is evaluated and input stream processing terminates when the value is true.

The following are the specifications of the conditional processing statements. Since the statements work in conjunction with each other, the examples are shown after all syntax descriptions.

The IF statementIF cctype relation compval [EXIT]

When LASTCC is specified, if the return code from the most recently executed command prior to encountering this statement satisfies the specified condition, all following commands until the next ELSE or ENDIF statement are attempted.

cctype The condition code type defines the value that is compared with the specified compare value:

LASTCC The condition code to use in the compare is the return code from the most recently processed command.

MAXCC The condition code to use in the compare is the maximum of the return codes from all previously processed commands.

relation Indicates the relation to use in the comparison:

= Test the compare value with the condition code value for equality.

> Test whether the condition code value is greater than the compare value.

< Test whether the condition code value is less than the compare value.

compval The value to compare with the conditional code value using the specified relation. Values can be 0, 4 or 8.

[EXIT] This parameter indicates that the condition specified in the statement is to be evaluated, and if true, the remainder of the command stream is to be flushed. When this parameter is specified, no corresponding ENDIF statement is required and no corresponding ELSE statement may be specified.



When MAXCC is specified, if the maximum return code from commands processed prior to encountering this statement is zero, all following commands until the next ELSE or ENDIF statement are attempted.

The ELSE statementELSE[EXIT]If the condition on the most recent IF statement was true, the following commands are skipped until the next ENDIF statement. If the condition was not true, the following commands are attempted until the next ENDIF statement .

The ENDIF statementENDIF

This statement terminates the IF/ENDIF range. If the maximum return code from commands that are processed prior to this statement is zero (0), then following commands are attempted. If the value is not zero, the following commands are skipped until a conditional processing IF statement is encountered or the end of the input stream is reached.

The RESET statementRESET { LASTCC | MAXCC }

This statement controls the last and maximum current values that are tested to determine whether to process the next command. The RESET statement may be placed anywhere within the batch input stream, and any number of RESET statements may be included.

[EXIT] This parameter indicates that the condition specified on the corresponding IF statement is to be evaluated, and if false, the remainder of the command stream is to be flushed.

LASTCC If specified, conditional processing behavior for the next command is as if the previous command had returned zero. This does not affect the current maximum return code (MAXCC) value, however.

MAXCC If specified, conditional processing behavior for the next command proceeds as if all previous commands had returned to zero. This statement can be used to cause the batch job step to return a zero condition code regardless of the results of the individual batch stream commands executed.

Note: If you specify RESET MAXCC, you do not need to specify RESET LASTCC.

Running GPM in batch mode 395


Conditional processing examples

These examples are not intended to demonstrate specific commands, which can be any of the valid GPM commands, but to illustrate the various conditional processing structures.

Basic IF/ELSE/ENDIFDRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(040-045) RESET LASTCCDRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1200-12FF) IF MAXCC = 0 REMOVE LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1041) REMOVE LCL(UNIT(5500)) POOL(THINPOOL3) DEV(1200-12FF)ELSE DISPLAY LCL(UNIT(5500)) POOL(THINPOOL2) DISPLAY LCL(UNIT(5500)) POOL(THINPOOL3)ENDIF

Using IF with EXIT optionDRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045) IF MAXCC = 0 EXIT REMOVE LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045)

Using IF/ELSE/ENDIF with EXIT optionDRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045) IF LASTCC > 0 REMOVE LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045) DRAIN LCL(UNIT(5500)) POOL(THINPOOL3) DEV(1200-12FF)ELSE EXITENDIF



GPM command examplesThe following section provides examples of how to use the GPM commands.

The examples provided use the console interface, however the commands will also work in batch mode.

Note: Refer to “General Pool Management commands” on page 185 for a description of each available GPM command.

Creating a VP in a Symmetrix System

The following steps illustrate how to create a Virtual Pool (VP) in a Symmetrix system using the GPM commands.

1. DISPLAY all of the pools in a Symmetrix systemEMCU500I DISPLAY LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: 7.50EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD3 0001 T Avail 3390 FIBRE 10K 70 96 1 34 EnabledEMCU012I RECLAIM_TEST 0002 T Avail 3390 FIBRE 10K 70 80 2 29 DisabledEMCU012I STCM_TCKD_00 0003 T Avail 3390 FIBRE 15K 70 80 0 32 DisabledEMCU012I STCM_TCKD_01 0004 T Avail 3390 FIBRE 15K 70 80 1 34 DisabledEMCU012I STCM_TCKD_02 0005 T Avail 3390 SATA 7200 70 80 3 40 DisabledEMCU012I STCM_TCKD_03 0006 T Avail ? 70 80 0 0 DisabledEMCU012I EGJDSEPOOL 0007 D Avail ? 70 80 0 0 DisabledEMCU012I MF1233 0008 T Avail 3390 FIBRE 10K 70 80 1 34 DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY.EMCU008I END OF COMMANDS FILE REACHED

Note: Type S = Snap pools (SAVEDEVs)Type T = Thin pools (TDATs)Type D = DSE pools(DSE DEVs)

2. CREATE a pool EMCU500I CREATE LCL(UNIT(3800)) POOL(EMCCKDVP) TYPE(THINPOOL) EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED

3. DISPLAY pools EMCU500I DISPLAY LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: 7.50EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD3 0001 T Avail 3390 FIBRE 10K 70 96 1 34 EnabledEMCU012I RECLAIM_TEST 0002 T Avail 3390 FIBRE 10K 70 80 2 29 DisabledEMCU012I STCM_TCKD_00 0003 T Avail 3390 FIBRE 15K 70 80 0 32 DisabledEMCU012I STCM_TCKD_01 0004 T Avail 3390 FIBRE 15K 70 80 1 34 DisabledEMCU012I STCM_TCKD_02 0005 T Avail 3390 SATA 7200 70 80 3 40 DisabledEMCU012I STCM_TCKD_03 0006 T Avail ? 70 80 0 0 DisabledEMCU012I EGJDSEPOOL 0007 D Avail ? 70 80 0 0 DisabledEMCU012I MF1233 0008 T Avail 3390 FIBRE 10K 70 80 1 34 DisabledEMCU012I EMCCKDVP 0009 T Avail ? 70 80 0 0 DisabledEMCU012I DF_DDEV_POOL 0100 T

GPM command examples 397


EMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY.EMCU008I END OF COMMANDS FILE REACHED

4. QUERY DATADEV to find available devicesEMCU500I QUERY DATADEV LCL(UNIT(3800)) EMCU184I Data Devices on 0001957-00079 API Ver: 7.50 EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I Status EMCU063I 00000260 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 IEMCU063I 00000261 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 I EMCU063I 00000262 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 IEMCU063I 00000263 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 IEMCU063I 00000264 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 I EMCU063I 00000265 3390 12 16668 RECLAIM_TEST Thin 0FIBRE 10K RAID1 IEMCU063I 00000266 3390 12 16668 RECLAIM_TEST Thin 0FIBRE 10K RAID1 IEMCU063I 00000271 3390 0 16680 MFCKD3 Thin FIBRE 10K RAID1 I EMCU063I 00000272 3390 13920 2760 MFCKD3 Thin FIBRE 10K RAID1 IEMCU063I 0000028A 3390 DF_DDEV_POOL FIBRE 10K RAID1 IEMCU063I 0000028B 3390 DF_DDEV_POOL FIBRE 10K RAID1 I EMCU063I 0000028C 3390 DF_DDEV_POOL FIBRE 15K RAID1 I EMCU063I 0000028D 3390 DF_DDEV_POOL FIBRE 15K RAID1 I EMCU063I 0000028E 3390 DF_DDEV_POOL FIBRE 15K RAID1 I EMCU063I 0000028F 3390 DF_DDEV_POOL FIBRE 15K RAID1 IEMCU063I 00000290 3390 DF_DDEV_POOL FLASH 15K RAID1 I EMCU063I 00000291 3390 DF_DDEV_POOL FLASH 15K RAID1 I EMCU063I 00000292 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 I EMCU063I 00000293 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 I EMCU063I 00000294 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 I EMCU063I 00000295 3390 12 16668 RECLAIM_TEST Thin FIBRE 10K RAID1 I

5. ADD data devices (TDAT) to a poolEMCU500I QUERY DATADEV LCL(UNIT(3800)) EMCU184I Data Devices on 0001957-00079 API Ver: 7.50 EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I StatusEMCU063I 0000028C 3390 DF_DDEV_POOL FIBRE SATA 15K RD1 0I EMCU063I 0000028D 3390 DF_DDEV_POOL FIBRE SATA 15K RD1 0I

EMCU500I ADD LCL(UNIT(3800)) DEV(28C-28D) POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 028C-028D EMCU00AI Eligible devices EMCU00AI 028C-028D EMCU00BI Completed devices EMCU00BI 028C-028D EMCU002I GPM command successful

Note: Notice the result of trying to add devices of mixed class:

EMCU500I QUERY DATADEV LCL(UNIT(3800)) DEV(290-291) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) DEV(290-291) EMCU184I Data Devices on 0001957-00079 API Ver: 7.50 EMCU061I Device# Emul Used Free Pool Name Type Class 0Speed Prot A/I Status EMCU063I 00000290 3390 DF_DDEV_POOL FLASH FLASH 07200 RD1 0I EMCU063I 00000291 3390 DF_DDEV_POOL FLASH FLASH 7200 RD1 0I EMCU064I Totals: EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% used EMCU001I GPM command complete EMCU500I ADD LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(290-291) EMCP001I GPM ADD LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(290-291) EMCU009I Requested devices EMCU009I 0290-0291 EMCU533E Devices do not match class and/or speed of existing pool devices EMCU533E 0290-0291 EMCU004W No eligible devices found

Note: Notice the result of trying to add devices of mixed speed.

EMCU500I QUERY DATADEV LCL(UNIT(3800)) DEV(28A-28B) EMCU184I Data Devices on 0001957-00079 API Ver: 7.50 EMCU061I Device# Emul Used Free Pool Name Type Class Speed Prot A/I Status EMCU063I 0000028A 3390 DF_DDEV_POOL FIBRE SATA 10K RD1 0I EMCU063I 0000028B 3390 DF_DDEV_POOL FIBRE SATA 10K RD1 0IEMCU064I Totals:



EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

EMCU500I ADD LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28A-28B) EMCU009I Requested devices EMCU009I 028A-028B EMCU533E Devices do not match class and/or speed of existing pool devices EMCU533E 028A-028B EMCU004W No eligible devices found EMCU008I END OF COMMANDS FILE REACHED.

Note: Notice the result of trying to add devices of mixed raid protection.

EMCU063I 0000122E 3390 DF_DDEV_POOL FIBRE SATA 10K RD6 EMCU063I 0000122F 3390 DF_DDEV_POOL FIBRE SATA 10K RD6 EMCU063I 00001230 3390 DF_DDEV_POOL FIBRE SATA 10K RD6 EMCU063I 00001231 3390 DF_DDEV_POOL FIBRE SATA 10K RD6 EMCU063I 00001232 3390 DF_DDEV_POOL FIBRE SATA 10K RD6EMCU063I 00001233 3390 DF_DDEV_POOL FIBRE SATA 10K RD6 EMCU064I Totals:

EMCU500I ADD LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(122E) EMCP001I GPM ADD LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(122E) EMCU009I Requested devices EMCU009I 122E EMCU53EE Devices are of mixed protection types or do not match pool protection type EMCU53EE 122E EMCU003E GPM command failed

6. QUERY DATADEV to see data devices in the poolEMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP)EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 7.50EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 0000028C 3390 I 0 16680 FIBRE 15K RD1EMCU063I 0000028D 3390 I 0 16680 FIBRE 15K RD1EMCU064I Totals:EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% usedEMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY.EMCU008I END OF COMMANDS FILE REACHED.

7. QUERY THINDEV for available thin devicesEMCU500I QRY THIND LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QRY THIND LCL UNIT 3A00 POOL MFCKD1 EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task Status EMCU110I 00000161 3A71 3390 ****** Y N 1113 R1 N Bind0000Done EMCU110I 00000162 3A72 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000163 3A73 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000164 3A74 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000165 3A75 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000166 3A76 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000167 3A77 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000187 3A97 3390 SYM187 Y N 1113 N Bind Done EMCU110I 00000E30 3B00 3390 ****** Y N 1113 R1 Y Bind Done EMCU110I 00000E31 3B01 3390 MF3B01 Y N 1113 R1 Y Bind Done EMCU110I 00000E32 3B02 3390 MF3B02 Y N 1113 R1 Y Bind Done EMCU110I 00000E33 3B03 3390 MF3B03 Y N 1113 R1 Y Bind Done EMCU110I 00000E34 3B04 3390 MF3B04 Y N 1113 R1 Y Bind Done EMCU110I 00000E35 3B05 3390 MF3B05 Y N 1113 R1 Y Bind Done EMCU110I 00000E36 3B06 3390 MF3B06 Y N 1113 R1 Y Bind Done EMCU110I 00000E37 3B07 3390 MF3B07 Y N 1113 R1 Y Bind Done EMCU110I 00000E38 3B08 3390 MF3B08 Y N 1113 R1 Y Bind Done EMCU071I Device Totals: CKD Bound: 17 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 283815 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete

Note: Refer to “QUERY THINDEV display examples” on page 283 for an explanation of the TYP column that is added to a QUERY THINDEV display.

8. ENABLE data devices in poolEMCU500I ENABLE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28C-28D) EMCU009I Requested devices EMCU009I 028C-028D EMCU00AI Eligible devices EMCU00AI 028C-028D



EMCU00BI Completed devices EMCU00BI 028C-028D EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

8a. There is also an ACTIVE parameter on ADD to ENABLE data devices in pool.EMCU500I ADD LCL(UNIT(3800)) DEV(2BA) ACTIVE POOL(EMCCKDVP) EMCP001I GPM ADD LCL(UNIT(3800)) DEV(2BA) ACTIVE POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 02BA EMCU00AI Eligible devices EMCU00AI 02BA EMCU00BI Completed devices EMCU00BI 02BA EMCU002I GPM command successful EMCU002I GPM command successful EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028C 3390 Act 8328 8352 EMCU015I 0000028D 3390 Act 8448 8232 EMCU015I 000002BA 3390 Act 0 16680 EMCU001I GPM command complete

9. QUERY DATADEV to see data devices in the poolEMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 7.50 EMCU061I Device# Emul A/I Used Free 0Class Speed Prot StatusEMCU063I 0000028C 3390 A 0 16680 FIBRE 0000015K RD1EMCU063I 0000028D 3390 A 0 16680 FIBRE 0000015K RD1 EMCU064I Totals: EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

10. BIND thin devices to the pool EMCU500I BIND LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(170) EMCU009I Requested devices EMCU009I 0170 EMCU00AI Eligible devices EMCU00AI 0170 EMCU00BI Completed devices EMCU00BI 0170 EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

Note: Notice the result of the BIND attempt prior to the ENABLE command making the data devices ACTIVE.

EMCU500I BIND LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(170) EMCU009I Requested devices EMCU009I 0170 EMCU00AI Eligible devices EMCU00AI 0170 EMCU139E No available data devices in pool EMCCKDVP EMCU003E GPM command failed EMCU008I END OF COMMANDS FILE REACHED.

11. QUERY data and thin devicesEMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP)EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 7.50EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 0000028C 3390 A 60 16620 FIBRE 15K RD1



EMCU063I 0000028D 3390 A 60 16620 FIBRE 15K RD1EMCU064I Totals:EMCU064I 3390: 120 used tracks, 33240 free tracks, 0% usedEMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY.EMCU008I END OF COMMANDS FILE REACHED

EMCU500I QUERY THINDEV LCL(UNIT(3800)) DEV(170)EMCU184I Thin Devices on 0001957-00079 API Ver: 7.50EMCU500I QRY THIND LCL UNIT 3A00 POOL MFCKD1EMCP001I GPM QRY THIND LCL UNIT 3A00 POOL MFCKD1EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000160 3A70 3390 ****** Y N 1113 R1 N Bind DoneEMCU071I Device Totals: CKD Bound: 1 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 16695 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY.EMCU008I END OF COMMANDS FILE REACHED.




Pool management example

The following steps illustrate how to manage pools using the GPM commands.

1. ADD data device to a poolEMCU500I ADD LCL(UNIT(3800)) DEV(28E) POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 028E EMCU00AI Eligible devices EMCU00AI 028E EMCU00BI Completed devices EMCU00BI 028E EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

2. ENABLE the deviceEMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028C 3390 Act 4032 12648 EMCU015I 0000028D 3390 Act 4032 12648 EMCU015I 0000028E 3390 Inact 0 16680 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

EMCU500I ENABLE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E) EMCU009I Requested devices EMCU009I 028E EMCU00AI Eligible devices EMCU00AI 028E EMCU00BI Completed devices EMCU00BI 028E EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY.

EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028C 3390 Act 4032 12648 EMCU015I 0000028D 3390 Act 4032 12648 EMCU015I 0000028E 3390 Act 0 16680 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

3. REBALANCE and DISPLAY poolEMCU500I REBALANCE LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028C 3390 Act 2520 14160 EMCU015I 0000028D 3390 Act 2760 13920 EMCU015I 0000028E 3390 Act 2784 13896 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.



4. QUERY data devicesEMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot A/I Status EMCU063I 0000028C 3390 A 2520 14160 FIBRE 15K RD1 EMCU063I 0000028D 3390 A 2760 13920 FIBRE 15K RD1 EMCU063I 0000028E 3390 A 2784 13896 FIBRE 15K RD1 EMCU064I Totals: EMCU064I 3390: 8064 used tracks, 41976 free tracks, 16% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

5. DRAIN device and DISPLAY poolEMCU500I DRAIN LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E) EMCU009I Requested devices EMCU009I 028E EMCU00AI Eligible devices EMCU00AI 028E EMCU00BI Completed devices EMCU00BI 028E EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028C 3390 Act 3912 12768 EMCU015I 0000028D 3390 Act 4152 12528 EMCU015I 0000028E 3390 Inact 0 16680 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

6. REMOVE device and DISPLAY poolEMCU500I REMOVE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E) EMCU009I Requested devices EMCU009I 028E EMCU00AI Eligible devices EMCU00AI 028E EMCU00BI Completed devices EMCU00BI 028E EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028C 3390 Act 3912 12768 EMCU015I 0000028D 3390 Act 4152 12528 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY. EMCU008I END OF COMMANDS FILE REACHED.

7. CREATE and DISPLAY new pool (using SCF command)F EMCSCF,GPM,CREATE LCL(UNIT(3800)) POOL(EMCCKDVP2) TYPE(THINPOOL) EMCU500I CREATE LCL(UNIT(3800)) POOL(EMCCKDVP2) TYPE(THINPOOL) EMCP001I GPM CREATE LCL(UNIT(3800)) POOL(EMCCKDVP2) TYPE(THINPOOL) EMCU002I GPM command successful EMCU500I DISPLAY LCL(UNIT(3800)) EMCP001I GPM DISPLAY LCL(UNIT(3800)) EMCU010I Pools on Controller 0001957-00079 API Ver: 7.50EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I RECLAIM_TEST 0001 T Avail 3390 FIBRE 10K 70 80 34 Ena=>Dis EMCU012I EMCCKDVP 0002 T Avail 3390 FIBRE 10K 70 80 29 Ena=>Dis EMCU012I EMCCKDVP2 0003 T Avail ? 70 80 19 Ena=>Dis EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete



EMCU500I DISPLAY LCL(UNIT(3800))EMCP001I GPM DISPLAY LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: 7.50EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I RECLAIM_TEST 0001 T Avail 3390 FIBRE 10K 70 80 1 34 EnabledEMCU012I EMCCKDVP 0002 T Avail 3390 FIBRE 10K 70 80 1 29 DisabledEMCU012I EMCCKDVP2 0003 T Avail ? 70 80 0 0 DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete.

8. QUERY data devices (using SCF command)F EMCSCF,GPM QUERY DATADEV LCL(UNIT(3800)) DEV(280-287) EMCU500I QUERY DATADEV LCL(UNIT(3800)) DEV(280-287) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) DEV(280-287) EMCU184I Data Devices on 0001957-00079 API Ver: 7.50 EMCU061I Device# Emul Used Free Pool Name 000Type Class Speed Prot --A/I Status EMCU063I 00000280 3390 DF_DDEV_POOL SATA 7200 RD1 IEMCU063I 00000281 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU063I 00000282 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU063I 00000283 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU063I 00000284 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU063I 00000285 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU063I 00000286 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU063I 00000287 3390 DF_DDEV_POOL SATA 7200 RD1 I EMCU064I Totals: EMCU064I 3390: 0 used tracks, 133440 free tracks, 0% used EMCU001I GPM command complete

9. ADD data devices to the new pool and DISPLAY poolEMCU500I ADD LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCP001I GPM ADD LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCU009I Requested devices EMCU009I 0280-0283 EMCU00AI Eligible devices EMCU00AI 0280-0283 EMCU00BI Completed devices EMCU00BI 0280-0283 EMCU002I GPM command successful EMCU500I DISPLAY LCL(UNIT(3800)) EMCP001I GPM DISPLAY LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: 7.50EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I RECLAIM_TEST 0001 T Avail 3390 FIBRE 10K 70 80 1 34 EnabledEMCU012I EMCCKDVP 0002 T Avail 3390 FIBRE 10K 70 80 1 29 DisabledEMCU012I EMCCKDVP2 0003 T Avail 3390 SATA 7200 70 80 0 0 DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete

10. ENABLE data devices in the new pool and DISPLAY poolEMCU500I ENABLE LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCP001I GPM ENABLE LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCU009I Requested devices EMCU009I 0280-0283 EMCU00AI Eligible devices EMCU00AI 0280-0283 EMCU00BI Completed devices EMCU00BI 0280-0283 EMCU002I GPM command successful

EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP2) EMCP001I GPM DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP2) EMCU013I Devices in Thin Pool EMCCKDVP2 on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 00000280 3390 Act 0 16680 EMCU015I 00000281 3390 Act 0 16680 EMCU015I 00000282 3390 Act 0 16680 EMCU015I 00000283 3390 Act 0 16680 EMCU001I GPM command complete



11. REBIND thin device to new pool.EMCU500I REBIND LCL(UNIT(3800)) DEV(170) POOL(EMCCKDVP2) EMCP001I GPM REBIND LCL(UNIT(3800)) DEV(170) POOL(EMCCKDVP2) EMCU009I Requested devices EMCU009I 0170 EMCU00AI Eligible devices EMCU00AI 0170 EMCU00BI Completed devices EMCU00BI 0170 EMCU002I GPM command successful

12. QUERY THINDEV and DATADEVEMCU500I QUERY THINDEV LCL(UNIT(3800)) DEV(170) EMCP001I GPM QUERY THINDEV LCL(UNIT(3800)) DEV(170) EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000170 3A70 3390 ****** Y N 1113 R1 N Bind DoneEMCU071I Device Totals: CKD Bound: 1 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 16695 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete


EMCU500I QUERY DATADEV LCL(UNIT(3800)) DEV(280-283) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) DEV(280-283) EMCU184I Data Devices on 0001957-00079 API Ver: 7.50 EMCU061I Device# Emul Used Free Pool Name 0Type Class Speed Prot 00A/I StatusEMCU063I 00000280 3390 0 16680 EMCCKDVP2 Thin SATA000000720000 RD1 I EMCU063I 00000281 3390 0 16680 EMCCKDVP2 Thin 0SATA 7200 RD1 IEMCU063I 00000282 3390 0 16680 EMCCKDVP2 Thin SATA 7200 RD1 IEMCU063I 00000283 3390 0 16680 EMCCKDVP2 Thin SATA 7200 RD1 IEMCU064I Totals: EMCU064I 3390: 0 used tracks, 66720 free tracks, 0% used EMCU001I GPM command complete

13. DISPLAY old and new pools after updates following REBINDEMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU013I Devices in Thin Pool EMCCKDVP on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 0000028A 3390 Act 4032 12648 EMCU015I 0000028B 3390 Act 4032 12648 EMCU001I GPM command complete

EMCU500I DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP2) EMCP001I GPM DISPLAY LCL(UNIT(3800)) POOL(EMCCKDVP2) EMCU013I Devices in Thin Pool EMCCKDVP2 on 0001957-00079 API Ver: 7.50 EMCU014I Device# Emul State Used Free EMCU015I 00000280 3390 Act 1896 14784 EMCU015I 00000281 3390 Act 1824 14856 EMCU015I 00000282 3390 Act 1896 14784 EMCU015I 00000283 3390 Act 1884 14796 EMCU001I GPM command complete

14. Prepare for unbind by making thin device USR-NRDYEMCU500I USR-NRDY LCL(UNIT(3800)) DEV(170) EMCP001I GPM USR-NRDY LCL(UNIT(3800)) DEV(170) EMCU009I Requested devices EMCU009I 0170 EMCU00AI Eligible devices EMCU00AI 0170 EMCU00BI Completed devices EMCU00BI 0170 EMCU002I GPM command successful



EMCU500I QUERY THINDEV LCL(UNIT(3800)) DEV(170) EMCP001I GPM QUERY THINDEV LCL(UNIT(3800)) DEV(170) EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000170 3A70 3390 ****** Y N 1113 R1 N Bind DoneEMCU071I Device Totals: CKD Bound: 1 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 16695 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete


15. UNBIND thin deviceEMCU500I UNBIND LCL(UNIT(3800)) POOL(EMCCKDVP2) DEV(170) EMCP001I GPM UNBIND LCL(UNIT(3800)) POOL(EMCCKDVP2) DEV(170) EMCU009I Requested devices EMCU009I 0170 EMCU00AI Eligible devices EMCU00AI 0170 EMCU00DI Completed devices EMCU00DI 0170 EMCU002I GPM command successful

EMCU500I QUERY THINDEV LCL(UNIT(3800)) DEV(170) EMCP001I GPM QUERY THINDEV LCL(UNIT(3800)) DEV(170) EMCU184I Thin Devices on 0001957-00079 API Ver: 7.50 EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com 0Task StatusEMCU110I 00000160 3A70 3390 ****** Y N 1113 R1 N Bind DoneEMCU071I Device Totals: CKD Bound: 1 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 16695 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete


16. QUERY DATADEV in poolsEMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP2) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP2) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP2 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 00000280 3390 A 0 16680 SATA 7200 RD1 0EMCU063I 00000281 3390 A 0 16680 SATA 7200 RD1 0 EMCU063I 00000282 3390 A 0 16680 SATA 7200 RD1 0 EMCU063I 00000283 3390 A 0 16680 SATA 7200 RD1 0 EMCU064I Totals: EMCU064I 3390: 0 used tracks, 66720 free tracks, 0% used EMCU001I GPM command complete

EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 0000028A 3390 A 0 16680 FIBRE 10K RD1 0 EMCU063I 0000028B 3390 A 0 16680 FIBRE 10K RD1 0EMCU064I Totals: EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% used EMCU001I GPM command complete

17. DISABLE data devices and QUERY DATADEV EMCU500I DISABLE LCL(UNIT(3800)) DEV(28A-28B) POOL(EMCCKDVP) EMCP001I GPM DISABLE LCL(UNIT(3800)) DEV(28A-28B) POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 028A-028B EMCU00AI Eligible devices EMCU00AI 028A-028B EMCU00BI Completed devices EMCU00BI 028A-028B EMCU002I GPM command successful

EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 7.50



EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 0000028A 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 0000028B 3390 I 0 16680 FIBRE 10K RD1 EMCU064I Totals: EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% used EMCU001I GPM command complete

18. REMOVE data devices from poolEMCU500I REMOVE LCL(UNIT(3800)) DEV(28A-28B) POOL(EMCCKDVP) EMCP001I GPM REMOVE LCL(UNIT(3800)) DEV(28A-28B) POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 028A-028B EMCU00AI Eligible devices EMCU00AI 028A-028B EMCU00BI Completed devices EMCU00BI 028A-028B EMCU002I GPM command successful

EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU701W No devices in pool EMCCKDVP EMCU003E GPM command failed

19. DELETE poolEMCU500I DELETE LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM DELETE LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU002I GPM command successful

EMCU500I DISPLAY LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: 7.50EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD3 0001 T Avail 3390 FIBRE 10K 70 96 1 34 EnabledEMCU012I RECLAIM_TEST 0002 T Avail 3390 FIBRE 10K 70 80 2 29 DisabledEMCU012I STCM_TCKD_00 0003 T Avail 3390 FIBRE 15K 70 80 0 32 DisabledEMCU012I STCM_TCKD_01 0004 T Avail 3390 FIBRE 15K 70 80 1 34 DisabledEMCU012I STCM_TCKD_02 0005 T Avail 3390 SATA 7200 70 80 3 40 DisabledEMCU012I STCM_TCKD_03 0006 T Avail ? 70 80 0 0 DisabledEMCU012I EGJDSEPOOL 0007 D Avail ? 70 80 0 0 DisabledEMCU012I MF1233 0008 T Avail 3390 FIBRE 10K 70 80 1 34 DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY.EMCU008I END OF COMMANDS FILE REACHED.



MOVE with REBIND example

The following example illustrates how to use the MOVE command with the REBIND parameter.

1. MOVE with REBIND parameterEMCU500I MOVE DEV(0090-0093) REBIND LCL(UNIT(2101)) POOL(DTTHINPOOL2) -EMCU500I SRCPOOL(DTTHINPOOL1) EMCU009I Requested devices EMCU009I 0090-0093 EMCU00AI Eligible devices EMCU00AI 0090-0093 EMCU00BI Completed devices EMCU00BI 0090-0093 EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY.

2. QUERY to verify devices are reboundEMCU500I QUERY THINDEV LCL(UNIT(2101)) POOL(DTTHINPOOL2)EMCU184I Thin Devices on 0001956-00057 Bound to Pool DTTHINPOOL2 API Ver: 7.40EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task StatusEMCU110I 00000090 2168 3390 ****** Y N 1113 N Move DoneEMCU110I 00000091 2169 3390 ****** Y N 1113 N Move DoneEMCU110I 00000092 216A 3390 ****** Y N 1113 N Move DoneEMCU110I 00000093 216B 3390 ****** Y N 1113 N Move DoneEMCU071I Device Totals: CKD Bound: 4 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 66780 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY..

3. QUERY to verify allocations were moved:EMCU500I QUERY ALLALLOCS LCL(UNIT(2101)) POOL(DTTHINPOOL2)EMCU060I Thin Allocations on 0001956-00057 API Ver: 7.50EMCU014I Device Alloc CompressEMCU014I 00000090 16788 0EMCU014I 00000091 16788 0EMCU014I 00000092 16788 0EMCU014I 00000093 16788 0EMCU001I GPM command completeEMCU006I COMMAND PROCESSED SUCCESSFULLY..



DRAIN process example

The following example illustrates the steps in a drain process.

1. Select the data devices to DRAIN.Display the data devices in the pool using QUERY DATADEV and identify the devices to be drained.

EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 00000140 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000141 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000142 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000143 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000144 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000145 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000146 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000147 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000148 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000149 3390 A 48 16200 SATA 7200 RD1 EMCU064I Totals: EMCU064I 3390: 480 used tracks, 166320 free tracks, 0% used EMCU064I Act : 480 used tracks, 166320 free tracks, 0% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

2. DRAIN the data devices.Issue the DRAIN command for the selected data devices.

EMCU500I DRAIN DEV(0140-0148) LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU009I Requested devicesEMCU009I 0140-0148EMCU00AI Eligible devices EMCU00AI 0140-0148 EMCU00CI Accepted devices EMCU00CI 0140-0148 EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY.

3. Check the status of the DRAIN using QUERY DATADEV:While the DRAIN is in progress, the draining data devices show DRAINING in the Status column of the QUERY DATADEV display. The DRAIN process also makes the draining devices inactive, as evident in the A/I column of the QUERY DATADEV display. Due to the way the DRAIN process works, the drained tracks are copied first to the non-draining active data device(s) before being removed from the drained data devices, as apparent in the QUERY DATADEV display below.

EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 00000140 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000141 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000142 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000143 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000144 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000145 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000146 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000147 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000148 3390 I 48 16632 SATA 7200 RD1 DRAININGEMCU063I 00000149 3390 A 480 16200 SATA 7200 RD1 EMCU064I Totals: EMCU064I 3390: 912 used tracks, 165888 free tracks, 0% used EMCU064I Act : 480 used tracks, 16200 free tracks, 2% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.



When the DRAIN is complete, the data devices no longer show DRAINING in the Status column of the QUERY DATADEV display. As an effect of the DRAIN process, the Used track count for all drained devices will be zero. The drained devices are also left inactive, as evident in the A/I column of the QUERY DATADEV display.

EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2) EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 00000140 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000141 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000142 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000143 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000144 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000145 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000146 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000147 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000148 3390 I 0 16680 SATA 7200 RD1 EMCU063I 00000149 3390 A 480 16200 SATA 7200 RD1 EMCU064I Totals: EMCU064I 3390: 480 used tracks, 166320 free tracks, 0% used EMCU064I Act : 480 used tracks, 16200 free tracks, 2% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.



REBALANCE process example

The following example illustrates the steps in a rebalance process.

1. Enable the data devices Enable the data devices, since the data devices you wish to REBALANCE need to be active to participate in the REBALANCE process.

EMCU500I ENABLE DEV(0140-0149) LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU009I Requested devices EMCU009I 0140-0149 EMCU00AI Eligible devices EMCU00AI 0140-0149 EMCU00BI Completed devices EMCU00BI 0140-0149 EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY.

2. REBALANCE the poolEMCU500I REBALANCE LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU002I GPM command successful EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Note: The optional VARIANCE parameter can be used to specify the goal for the rebalancing operation, which is the maximum difference in usage between the most heavily utilized and least heavily utilized active data device in the pool based on current device usage statistics. The range is 1 - 50%, and the default variance is 1%. Since the above example does not specify the VARIANCE parameter, the default variance of 1% is used. Using a variance of 1% means the maximum difference in usage between all active data devices in the pool after the REBALANCE process is complete will be 1%.

3. Use QUERY TASKS to check the statusUse QUERY TASKS to check the status of the REBALANCE background task on the Symmetrix system. The task with the highest task ID in the Task column is the most current. The QUERY TASKS display wraps around so the most current task may not necessarily be at the bottom of the list.

While the REBALANCE task is in progress, the Rebalance task will show Executing in the Status column.

EMCU500I QUERY TASKS LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU010I Tasks on Controller 0001956-00057 for Pool JCPTCKDPOOL2 API Ver: 7.50EMCU011I Task Type State Status MaxDelta EMCU011I 037C Rebalance Boot Completed 1 EMCU011I 037D Rebalance Boot Completed 1 EMCU011I 037E Rebalance Boot Executing 1 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

When the REBALANCE task is complete, the Rebalance task will show “Completed” in the Status column.

EMCU500I QUERY TASKS LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU010I Tasks on Controller 0001956-00057 for Pool JCPTCKDPOOL2 API Ver: 7.50EMCU011I Task Type State Status MaxDelta EMCU011I 037C Rebalance Boot Completed 1 EMCU011I 037D Rebalance Boot Completed 1 EMCU011I 037E Rebalance Boot Completed 1 EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.



4. Use DISPLAY to check the status of the pool listYou can also use the pool list DISPLAY command to check the rebalance status for each listed pool. Status values include:

◆ 'Y' in the Reb column indicates that the pool is currently rebalancing,

◆ 'N' in the Reb column indicates that the pool is not currently rebalancing.

Note: If a pool does not indicate that it is rebalancing immediately after issuing a REBALANCE command, follow up with a subsequent pool list DISPLAY. It may take a moment for the rebalancing operation to begin. Also, depending on the VARIANCE specified and the number of used tracks on the active devices in the pool, the rebalancing operation may complete very quickly and may be hard to catch in progress on the pool list DISPLAY. Alternatively, you can use QUERY TASKS to check the status of the pool's most recent rebalance task (which will have the highest task ID) to clearly see whether it is 'Executing' or 'Completed'.

In the example, Pool JCPTCKDPOOL2 shows a 'Y' in the Reb column when the rebalancing operation is in progress.

EMCU500I DISPLAY LCL(UNIT(2101))EMCU010I Pools on Controller 0001956-00057 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 S EMCU012I MFFBASTD 0001 T Avail FBA FIBRE 15K 70 80 1 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 1 95 N DisabledEMCU012I MFFBABCV 0003 T Avail FBA FIBRE 15K 70 80 1 0 N DisabledEMCU012I DTTHINPOOL1 0004 T Avail 3390 FIBRE 15K 70 80 0 0 N Enabled EMCU012I JCPTCKDPOOL2 0005 T Avail 3390 SATA 7200 70 80 1 0 Y DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

Pool JCPTCKDPOOL2 shows an 'N' in the Reb column when the rebalancing operation is complete.

EMCU500I DISPLAY LCL(UNIT(2101))EMCU010I Pools on Controller 0001956-00057 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 S EMCU012I MFFBASTD 0001 T Avail FBA FIBRE 15K 70 80 1 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 1 95 N DisabledEMCU012I MFFBABCV 0003 T Avail FBA FIBRE 15K 70 80 1 0 N DisabledEMCU012I DTTHINPOOL1 0004 T Avail 3390 FIBRE 15K 70 80 0 0 N Enabled EMCU012I JCPTCKDPOOL2 0005 T Avail 3390 SATA 7200 70 80 1 0 N DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

5. Use QUERY DATADEV to check the resultUse QUERY DATADEV to check the result of the REBALANCE operation and ensure that the allocations (in the Used column) have been distributed amongst the active data devices in the pool.

EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 00000140 3390 A 36 16644 SATA 7200 RD1 EMCU063I 00000141 3390 A 60 16620 SATA 7200 RD1 EMCU063I 00000142 3390 A 72 16680 SATA 7200 RD1 EMCU063I 00000143 3390 A 24 16656 SATA 7200 RD1 EMCU063I 00000144 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000145 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000146 3390 A 12 16668 SATA 7200 RD1



EMCU063I 00000147 3390 A 48 16632 SATA 7200 RD1 EMCU063I 00000148 3390 A 60 16620 SATA 7200 RD1 EMCU063I 00000149 3390 A 72 16536 SATA 7200 RD1 EMCU064I Totals: EMCU064I 3390: 480 used tracks, 166320 free tracks, 0% used EMCU064I Act : 480 used tracks, 166320 free tracks, 0% used EMCU001I GPM command complete EMCU006I COMMAND PROCESSED SUCCESSFULLY.

VP compression examples

The following examples illustrates the steps to implement VP compression.

1. Pool MFCKD1 is not enabled for compression.EMCU500I DISPLAY LCL UNIT 3A00 EMCP001I GPM DISPLAY LCL UNIT 3A00 EMCU010I Pools on Controller 0001957-00086 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 00070 80 1 31 Disabled EMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 00070 080 2 1 Disabled EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

2. None of the thin devices in the pool are currently compressed.EMCU500I QUERY THINDEV LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QUERY THINDEV LCL UNIT 3A00 POOL MFCKD1 EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task Status EMCU110I 00000160 3A70 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000161 3A71 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000162 3A72 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000163 3A73 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000164 3A74 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000165 3A75 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000166 3A76 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000167 3A77 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000187 3A97 3390 SYM187 Y N 1113 N Bind Done EMCU110I 00000E30 3B00 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000E31 3B01 3390 MF3B01 Y N 1113 R1 N Bind Done EMCU110I 00000E32 3B02 3390 MF3B02 Y N 1113 R1 N Bind Done EMCU110I 00000E33 3B03 3390 MF3B03 Y N 1113 R1 N Bind Done EMCU110I 00000E34 3B04 3390 MF3B04 Y N 1113 R1 N Bind Done EMCU110I 00000E35 3B05 3390 MF3B05 Y N 1113 R1 N Bind Done EMCU110I 00000E36 3B06 3390 MF3B06 Y N 1113 R1 N Bind Done EMCU110I 00000E37 3B07 3390 MF3B07 Y N 1113 R1 N Bind Done EMCU110I 00000E38 3B08 3390 MF3B08 Y N 1113 R1 N Bind Done EMCU110I 00000E39 3B09 3390 MF3B09 Y N 1113 R1 N Bind Done EMCU110I 00000E3A 3B0A 3390 MF3B0A Y N 1113 R1 N Bind Done EMCU110I 00000E3B 3B0B 3390 MF3B0B Y N 1113 R1 N Bind Done EMCU110I 00000E3C 3B0C 3390 MF3B0C Y N 1113 R1 N Bind Done EMCU110I 00000E3D 3B0D 3390 MF3B0D Y N 1113 R1 N Bind Done EMCU110I 00000E3E 3B0E 3390 MF3B0E Y N 1113 R1 N Bind Done EMCU110I 00000E3F 3B0F 3390 MF3B0F Y N 1113 R1 N Bind Done EMCU071I Device Totals: CKD Bound: 25 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 417375 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete

3. Data devices in the pool currently contain only non-compressed data.EMCU500I QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 EMCU184I Data Devices on 0001957-00086 in Pool MFCKD1 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 00000281 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 00000282 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 00000283 3390 A 5424 11256 FIBRE 10K RD1 EMCU063I 00000284 3390 A 5304 11376 FIBRE 10K RD1 EMCU063I 00000285 3390 A 5400 11280 FIBRE 10K RD1 EMCU063I 00000286 3390 A 5400 11280 FIBRE 10K RD1 EMCU063I 00000287 3390 A 5304 11376 FIBRE 10K RD1 EMCU063I 00000288 3390 A 5220 11460 FIBRE 10K RD1 EMCU063I 00000289 3390 A 5388 11292 FIBRE 10K RD1



EMCU063I 0000028A 3390 A 5304 11376 FIBRE 10K RD1 EMCU063I 0000028B 3390 A 5496 11184 FIBRE 10K RD1 EMCU063I 0000028C 3390 A 5376 11304 FIBRE 10K RD1 EMCU063I 0000028D 3390 A 5292 11388 FIBRE 10K RD1 EMCU063I 0000028E 3390 A 5412 11268 FIBRE 10K RD1 EMCU063I 0000028F 3390 A 5376 11304 FIBRE 10K RD1 EMCU063I 00000290 3390 A 5412 11268 FIBRE 10K RD1 EMCU063I 00000291 3390 A 5412 11268 FIBRE 10K RD1 EMCU063I 00000292 3390 A 5292 11388 FIBRE 10K RD1 EMCU063I 00000293 3390 A 5328 11352 FIBRE 10K RD1 EMCU063I 00000294 3390 A 5340 11340 FIBRE 10K RD1 EMCU063I 00000295 3390 A 5400 11280 FIBRE 10K RD1 EMCU063I 00000296 3390 A 5364 11316 FIBRE 10K RD1 EMCU063I 00000297 3390 A 5448 11232 FIBRE 10K RD1 EMCU064I Totals: EMCU064I 3390: 112692 used tracks, 270948 free tracks, 29% used EMCU064I Act : 112692 used tracks, 237588 free tracks, 32% used EMCU001I GPM command complete

4. Enable the pool attribute to allow compression for thin devices bound to the pool.EMCU500I POOLATTR LCL UNIT 3A00 COMPRESSION(ENABLE) POOL MFCKD1 EMCP001I GPM POOLATTR LCL UNIT 3A00 COMPRESSION(ENABLE) POOL MFCKD1 EMCU002I GPM command successful

5. The pool is now enabled, and thin devices bound to the pool can be compressed.EMCU500I DISPLAY LCL UNIT 3A00 EMCP001I GPM DISPLAY LCL UNIT 3A00 EMCU010I Pools on Controller 0001957-00086 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 070 80 1 32 Enabled EMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 070 80 2 1 Disabled EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

6. Compress the thin devices bound to the pool.EMCU500I COMPRESS LCL UNIT 3A00 POOL MFCKD1 DEV E30-E3F EMCP001I GPM COMPRESS LCL UNIT 3A00 POOL MFCKD1 DEV E30-E3F EMCU009I Requested devices EMCU009I 0E30-0E3F EMCU00AI Eligible devices EMCU00AI 0E30-0E3F EMCU00BI Completed devices EMCU00BI 0E30-0E3F EMCU002I GPM command successful

7. The compressed thin devices are now identified as having compressed allocations in the thin device display.EMCU500I QUERY THINDEV LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QUERY THINDEV LCL UNIT 3A00 POOL MFCKD1 EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task Status EMCU110I 00000160 3A70 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000161 3A71 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000162 3A72 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000163 3A73 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000164 3A74 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000165 3A75 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000166 3A76 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000167 3A77 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000187 3A97 3390 SYM187 Y N 1113 N Bind Done EMCU110I 00000E30 3B00 3390 ****** Y N 1113 R1 Y Compress Done EMCU110I 00000E31 3B01 3390 MF3B01 Y N 1113 R1 Y Compress Done EMCU110I 00000E32 3B02 3390 MF3B02 Y N 1113 R1 Y Compress Done EMCU110I 00000E33 3B03 3390 MF3B03 Y N 1113 R1 Y Compress Done EMCU110I 00000E34 3B04 3390 MF3B04 Y N 1113 R1 Y Compress Done EMCU110I 00000E35 3B05 3390 MF3B05 Y N 1113 R1 Y Compress Done EMCU110I 00000E36 3B06 3390 MF3B06 Y N 1113 R1 Y Compress Done EMCU110I 00000E37 3B07 3390 MF3B07 Y N 1113 R1 Y Compress Done



EMCU110I 00000E38 3B08 3390 MF3B08 Y N 1113 R1 Y Compress Done EMCU110I 00000E39 3B09 3390 MF3B09 Y N 1113 R1 Y Compress Done EMCU110I 00000E3A 3B0A 3390 MF3B0A Y N 1113 R1 Y Compress Done EMCU110I 00000E3B 3B0B 3390 MF3B0B Y N 1113 R1 Y Compress Done EMCU110I 00000E3C 3B0C 3390 MF3B0C Y N 1113 R1 Y Compress Done EMCU110I 00000E3D 3B0D 3390 MF3B0D Y N 1113 R1 Y Compress Done EMCU110I 00000E3E 3B0E 3390 MF3B0E Y N 1113 R1 Y Compress Done EMCU110I 00000E3F 3B0F 3390 MF3B0F Y N 1113 R1 Y Compress Done EMCU071I Device Totals: CKD Bound: 19 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU071I Track Totals: CKD Bound: 317205 Unbound: 0 FBA Bound: 0 Unbound: 0EMCU001I GPM command complete

8. The pool is now identified as being enabled for compression on the pool list display, and the percent used for active devices has gone down to 2%.EMCU500I DISPLAY LCL UNIT 3A00 EMCP001I GPM DISPLAY LCL UNIT 3A00 EMCU010I Pools on Controller 0001957-00086 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I MFCKD1 0001 T Avail 3390 FIBRE 0010K 70 80 1 2 Enabled EMCU012I MFTEST 0002 T Avail 3390 FIBRE 0010K 70 80 2 1 Disabled EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

EMCU500I QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 SUM EMCP001I GPM QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 SUM EMCU064I Totals: EMCU064I 3390: 9528 used tracks, 374112 free tracks, 2% used EMCU064I Act : 9528 used tracks, 340752 free tracks, 2% used EMCU001I GPM command complete

9. The data devices in the pool show less used tracks now that some of the bound thin devices are compressed.EMCU500I QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 EMCU184I Data Devices on 0001957-00086 in Pool MFCKD1 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 00000281 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 00000282 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 00000283 3390 A 456 16224 FIBRE 10K RD1 EMCU063I 00000284 3390 A 480 16200 FIBRE 10K RD1 EMCU063I 00000285 3390 A 468 16212 FIBRE 10K RD1 EMCU063I 00000286 3390 A 468 16212 FIBRE 10K RD1 EMCU063I 00000287 3390 A 420 16260 FIBRE 10K RD1 EMCU063I 00000288 3390 A 384 16296 FIBRE 10K RD1 EMCU063I 00000289 3390 A 480 16200 FIBRE 10K RD1 EMCU063I 0000028A 3390 A 408 16272 FIBRE 10K RD1 EMCU063I 0000028B 3390 A 504 16176 FIBRE 10K RD1 EMCU063I 0000028C 3390 A 468 16212 FIBRE 10K RD1 EMCU063I 0000028D 3390 A 396 16284 FIBRE 10K RD1 EMCU063I 0000028E 3390 A 468 16212 FIBRE 10K RD1 EMCU063I 0000028F 3390 A 456 16224 FIBRE 10K RD1 EMCU063I 00000290 3390 A 492 16188 FIBRE 10K RD1 EMCU063I 00000291 3390 A 492 16188 FIBRE 10K RD1 EMCU063I 00000292 3390 A 444 16236 FIBRE 10K RD1 EMCU063I 00000293 3390 A 444 16236 FIBRE 10K RD1 EMCU063I 00000294 3390 A 468 16212 FIBRE 10K RD1 EMCU063I 00000295 3390 A 456 16224 FIBRE 10K RD1 EMCU063I 00000296 3390 A 456 16224 FIBRE 10K RD1 EMCU063I 00000297 3390 A 420 16260 FIBRE 10K RD1 EMCU064I Totals: EMCU064I 3390: 9528 used tracks, 374112 free tracks, 2% used EMCU064I Act : 9528 used tracks, 340752 free tracks, 2% used EMCU001I GPM command complete

10. Decompress the thin devices that were previously compressed.EMCU500I DECOMPRESS LCL UNIT 3A00 POOL MFCKD1 DEV E30-E3F EMCP001I GPM DECOMPRESS LCL UNIT 3A00 POOL MFCKD1 DEV E30-E3F EMCU009I Requested devices EMCU009I 0E30-0E3F EMCU00AI Eligible devices EMCU00AI 0E30-0E3F



EMCU00BI Completed devices EMCU00BI 0E30-0E3F EMCU002I GPM command successful

11. The thin devices are no longer indicated as being compressed.EMCU500I QUERY THIND LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QUERY THIND LCL UNIT 3A00 POOL MFCKD1 EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 7.50 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Com Task Status EMCU110I 00000160 3A70 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000161 3A71 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000162 3A72 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000163 3A73 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000164 3A74 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000165 3A75 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000166 3A76 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000167 3A77 3390 ****** Y N 1113 R1 N Bind Done EMCU110I 00000187 3A97 3390 SYM187 Y N 1113 N Bind Done EMCU110I 00000E30 3B00 3390 ****** Y N 1113 R1 N Decompress Done EMCU110I 00000E31 3B01 3390 MF3B01 Y N 1113 R1 N Decompress Done EMCU110I 00000E32 3B02 3390 MF3B02 Y N 1113 R1 N Decompress Done EMCU110I 00000E33 3B03 3390 MF3B03 Y N 1113 R1 N Decompress Done EMCU110I 00000E34 3B04 3390 MF3B04 Y N 1113 R1 N Decompress Done EMCU110I 00000E35 3B05 3390 MF3B05 Y N 1113 R1 N Decompress Done EMCU110I 00000E36 3B06 3390 MF3B06 Y N 1113 R1 N Decompress Done EMCU110I 00000E37 3B07 3390 MF3B07 Y N 1113 R1 N Decompress Done EMCU110I 00000E38 3B08 3390 MF3B08 Y N 1113 R1 N Decompress Done EMCU110I 00000E39 3B09 3390 MF3B09 Y N 1113 R1 N Decompress Done EMCU110I 00000E3A 3B0A 3390 MF3B0A Y N 1113 R1 N Decompress Done EMCU110I 00000E3B 3B0B 3390 MF3B0B Y N 1113 R1 N Decompress Done EMCU110I 00000E3C 3B0C 3390 MF3B0C Y N 1113 R1 N Decompress Done EMCU110I 00000E3D 3B0D 3390 MF3B0D Y N 1113 R1 N Decompress Done EMCU110I 00000E3E 3B0E 3390 MF3B0E Y N 1113 R1 N Decompress Done EMCU110I 00000E3F 3B0F 3390 MF3B0F Y N 1113 R1 N Decompress Done EMCU001I GPM command complete

12. Data devices in the pool now show a greater number of used tracks now that the compressed thin devices have been decompressed.EMCU500I QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 EMCU184I Data Devices on 0001957-00086 in Pool MFCKD1 API Ver: 7.50 EMCU061I Device# Emul A/I Used Free Class Speed Prot Status EMCU063I 00000281 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 00000282 3390 I 0 16680 FIBRE 10K RD1 EMCU063I 00000283 3390 A 5424 11256 FIBRE 10K RD1 EMCU063I 00000284 3390 A 5304 11376 FIBRE 10K RD1 EMCU063I 00000285 3390 A 5400 11280 FIBRE 10K RD1 EMCU063I 00000286 3390 A 5400 11280 FIBRE 10K RD1 EMCU063I 00000287 3390 A 5304 11376 FIBRE 10K RD1 EMCU063I 00000288 3390 A 5220 11460 FIBRE 10K RD1 EMCU063I 00000289 3390 A 5388 11292 FIBRE 10K RD1 EMCU063I 0000028A 3390 A 5304 11376 FIBRE 10K RD1 EMCU063I 0000028B 3390 A 5496 11184 FIBRE 10K RD1 EMCU063I 0000028C 3390 A 5376 11304 FIBRE 10K RD1 EMCU063I 0000028D 3390 A 5292 11388 FIBRE 10K RD1 EMCU063I 0000028E 3390 A 5412 11268 FIBRE 10K RD1 EMCU063I 0000028F 3390 A 5376 11304 FIBRE 10K RD1 EMCU063I 00000290 3390 A 5412 11268 FIBRE 10K RD1 EMCU063I 00000291 3390 A 5412 11268 FIBRE 10K RD1 EMCU063I 00000292 3390 A 5292 11388 FIBRE 10K RD1 EMCU063I 00000293 3390 A 5328 11352 FIBRE 10K RD1 EMCU063I 00000294 3390 A 5340 11340 FIBRE 10K RD1 EMCU063I 00000295 3390 A 5400 11280 FIBRE 10K RD1 EMCU063I 00000296 3390 A 5364 11316 FIBRE 10K RD1 EMCU063I 00000297 3390 A 5448 11232 FIBRE 10K RD1 EMCU064I Totals: EMCU064I 3390: 112692 used tracks, 270948 free tracks, 29% used EMCU064I Act : 112692 used tracks, 237588 free tracks, 32% used EMCU001I GPM command complete



13. The pool shows a greater percent used now that the compressed thin devices have been decompressed.EMCU500I QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 SUM EMCP001I GPM QUERY DATADEV LCL UNIT 3A00 POOL MFCKD1 SUM EMCU064I Totals: EMCU064I 3390: 112692 used tracks, 270948 free tracks, 29% used EMCU064I Act : 112692 used tracks, 237588 free tracks, 32% used EMCU001I GPM command complete

EMCU500I DISPLAY LCL UNIT 3A00 EMCP001I GPM DISPLAY LCL UNIT 3A00 EMCU010I Pools on Controller 0001957-00086 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 70 80 1 32 Enabled EMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 70 80 2 1 Disabled EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

14. Disable compression for the pool, which deallocates the reserve space used for temporary decompression (as long as all thin devices bound to the pool no longer contain compressed allocations) and prevents thin devices bound to the pool from being compressed.EMCU500I POOLATTR COMPRESS(DISABLE) LCL UNIT 3A00 POOL MFCKD1 EMCP001I GPM POOLATTR COMPRESS(DISABLE) LCL UNIT 3A00 POOL MFCKD1 EMCU002I GPM command successful

15. The pool list display shows that the compression capability of the pool is in the process of disabling.EMCU002I GPM command successful EMCU500I DISPLAY LCL UNIT 3A00 EMCP001I GPM DISPLAY LCL UNIT 3A00 EMCU010I Pools on Controller 0001957-00086 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I MFCKD1 0001 T Avail 3390 FIBRE 0010K 70 80 1 32 Ena=>Dis EMCU012I MFTEST 0002 T Avail 3390 FIBRE 0010K 70 80 2 1 Disabled EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

16. Moments later, compression is now fully disabled for the pool.EMCU500I DISPLAY LCL UNIT 3A00 EMCP001I GPM DISPLAY LCL UNIT 3A00 EMCU010I Pools on Controller 0001957-00086 API Ver: 7.50 EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Compress EMCU012I DEFAULT_POOL 0000 S EMCU012I MFCKD1 0001 T Avail 3390 FIBRE 0010K 70 80 1 32 Disabled EMCU012I MFTEST 0002 T Avail 3390 FIBRE 0010K 70 80 2 1 Disabled EMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete



Suggested VP compression command sequence The following is a suggested command sequence for integrating VP compression into your existing GPM command sequence. This basic sequence illustrates only one suggested order on how to use the commands.

To create a thin pool and compress thin devices:

1. CREATE thin pool.

2. ADD data devices.

3. ENABLE data devices.

4. POOLATTR COMPRESSION(ENABLE) to enable compression for pool.

5. Wait for pool to enable for compression (see pool list DISPLAY).

6. BIND thin devices.

7. USR_RDY thin devices.

8. COMPRESS thin devices.

To decompress thin devices and delete thin pools:

1. DECOMPRESS thin devices.

2. USR_NRDY thin devices.

3. UNBIND thin devices.

4. POOLATTR COMPRESSION(DISABLE) to disable compression for pool.

5. Wait for pool to disable for compression (see pool list DISPLAY).

6. DISABLE data devices.

7. REMOVE data devices.

8. DELETE thin pool.


CHAPTER 8Monitoring Pool Usage

This chapter describes the Save Device Capacity, Thin Device Capacity, DSE Capacity, and DSE Spillover Time monitors, along with the Thin CKD space reclamation environment.

◆ Monitor functions.................................................................................................. 420◆ Using a User Exit with the SCF Pool Capacity Monitors ........................................... 421◆ Syntax conventions............................................................................................... 423◆ Save Device Capacity monitor syntax..................................................................... 423◆ Thin Pool Capacity Monitor syntax......................................................................... 428◆ DSE Capacity monitor syntax ................................................................................. 432◆ DSE Spillover Time monitor syntax ........................................................................ 437◆ Thin CKD space reclamation .................................................................................. 438◆ Thin Pool Capacity Monitor examples .................................................................... 442

◆ Example of SCF initialization parameters................................................. 442◆ Example of THN monitor for a specific Symmetrix system ........................ 443◆ Example of global THN monitor ............................................................... 443

Monitoring Pool Usage 419

Monitoring Pool Usage

Monitor functionsEMCSCF is a long-running task that provides a useful environment for automation and monitoring functions. Other EMC automation and monitoring tasks are also indirectly invoked, such as TimeFinder initiation and control of Symmetrix Automated Replication or the Notify option of TimeFinder/Snap for z/OS.

Some monitor functions need to run independently of other products. This chapter describes those monitors — the Save Device, DSE, Thin Device and Spillover Time monitors.

Save devices are a predefined set of devices that provide a pool of physical space. Save devices are not host-accessible. They are used with VDEVs (virtual devices), DSEPOOL (Delta Set Extension pool) and Thin devices as follows:

◆ VDEVs make use of SNAPPOOL devices to store pre-update images of tracks changed on the source device or new writes to the virtual devices. As specific virtual device sessions are terminated, the space associated with them is returned to free space in the save device pools.

◆ A DSEPOOL (Delta Set Extension) is used to extend the cache available for an SRDF/A group. This extra space permits SRDF/A to keep running during transient problems such as temporary link loss.

If an SRDF/A group has DSE active and the DSE threshold is exceeded, then the amount of cache available for SRDF/A has reached the limit. Once this threshold is exceeded, the Symmetrix system will move some of the cache slots onto these DSEPOOL devices. On each SRDF/A cycle switch, these DSEPOOL tracks may or may not have to be returned to cache. Only on the Transmit and Restore cycles does the data have to be recovered from the DSEPOOL and placed into cache so that they can be transmitted or restored.

◆ Thin devices have no storage allocated to them when they are created; rather storage is allocated on-demand from a "bound" thin pool. The first write to a location in a thin device results in space being allocated on a DATA device from the bound pool.

Note: Chapter 7, “Managing Devices and Pools,” describes device pool functionality.

Monitoring and alerts

Save device pool space is a valuable resource. SNAPPOOLs , DSEPOOLs and THINPOOLs utilize the following monitoring and alerting methods.

Capacity monitoring Three monitors allow you to perform capacity monitoring:

◆ The Save Device Capacity monitor periodically examines the consumed capacity of the SNAPPOOL used by TimeFinder/Snap with VDEV functionality enabled.

◆ The Thin Pool Capacity Monitor periodically examines the used capacity of thin pools.

◆ The DSE Capacity monitor periodically examines the consumed capacity of the DSEPOOL used by SRDF/A.



These monitors automatically check space consumption thresholds and trigger an automated response that is tailored to the specific needs of the installation. The response can take the following actions:

◆ Notify appropriate operational personnel

◆ Identify high consuming virtual device snap jobs (Save Device Capacity monitor only)

◆ Stop virtual device snaps based on local criteria (Save Device Capacity monitor only)

◆ Perform whatever you determine to be the best response to particular threshold levels of save device usage

If you enable devices on more than one Symmetrix system, you can perform the monitoring on:

◆ A global level

◆ A control unit level

◆ Both a global and control unit level

You can specify multiple thresholds of space consumption in the Save Device and DSE Capacity monitors. When the percentage of space consumption reaches a specified range, the appropriate action is performed.

Actions may do nothing, may issue a message, or may invoke an exit action you specify. Messages can have an eight-character, user-supplied string that is appended to the message text so that you can implement customized alerts to drive customer automation.

Spillover monitoring ResourcePak Base provides an additional alert monitor to indicate that DSE spillover has been occurring for a specified time interval. The DSE Spillover Time monitor reports the length of time that spillover been happening, independent of the percentage of space consumption. This monitoring is performed automatically on all locally connected Symmetrix systems.

If the specified time interval is exceeded, ResourcePak Base issues a message to indicate the spillover event has exceeded the threshold time value.You may specify up to three time durations at which you wish messages to be issued. “SCF.DSE.WARNING”, “SCF.DSE.MINOR”, and “SCF.DSE.MAJOR” on page 96 describe how to set these threshold time values.

If you specify no threshold time values, then no monitoring is done. If you specify valid values, an SCF message will be issued for any locally connected Symmetrix that has a spillover duration equal to the entered value. ResourcePak Base will also issue a message to indicate when the spillover value returns to zero for the Symmetrix system.

Using a User Exit with the SCF Pool Capacity MonitorsMember TSDVEXIT in SCF.SAMPLIB is a sample user exit for the optional user exit that can be called by the device capacity monitors. There is a link-edited version of this sample user exit in SCF.LINKLIB also called TSDVEXIT. There is a DSECT called @MNUEXIT provided in SCF.SAMPLIB, as well. This sample includes the structure of the information that is passed to the user exit. The member name containing the mapping macro is ESFUXPRM. On entry to the user exit, register 1 contains the address of a parameter list. The first

Using a User Exit with the SCF Pool Capacity Monitors 421


parameter (offset zero from register 1), is the address of the area containing the information passed to the user exit from the pool capacity monitor. The fields contained within this area are presented in Table 13, “Parameters Passed to User Exit from Pool Capacity Monitors,”

Table 13 Parameters Passed to User Exit from Pool Capacity Monitors

Field Description

MNUEYE Eyecatcher containing C'@MNUEXIT'

MNULEN Total length of parameter area

MNUVER Current version of parameter area

MNUTYPEMNUTYPE_SNAPPOOL MNUTYPE_DSEPOOL MNUTYPE_THINPOOL

Type of device pool - SNAP pool- DSE pool- THIN pool

MNUPCT Current percentage used for the pool

MNUUCB@ UCB address of gatekeeper device

MNUSER12 Serial number of controller

MNUUSER User storage kept by SCF

MNUPOOL Name of pool

MNUPOOL# ID number of pool

MNUPCNT Total number of devices in the pool

MNUPFREE Total free tracks on active devices in the pool

MNUPUSED Total used tracks on active devices in the pool

MNUSEQ# Sequence number of current interval

MNURNGLO Low range value of current interval

MNURNGHI High range value of current interval

MNUDURTN Current interval duration in minutes

MNUXITNM Name of user exit

MNUDURS Current interval duration in seconds

MNUPPOOL# Prior number of devices in the pool

MNUPPOOLF Prior free tracks on active devices in the pool

MNUPPOOLU Prior used tracks on active devices in the pool

MNUPPOOL$ Prior percentage used for the pool



Syntax conventionsThe following notes apply to the syntax for capacity monitors:

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

◆ Required keywords and symbols are shown in upper case.

◆ User-supplied information is shown in lower case italics.

Save Device Capacity monitor syntaxThe Save Device Capacity monitor utilizes the following initialization parameter statement types:

◆ General

◆ Global interval

◆ Controller

◆ Controller interval

◆ Pool interval

General

The SCF.SDV.LIST general purpose statement allows you to enable or disable the Save Device Capacity monitor.

FormatSCF.SDV.LIST=ENAble|DISable

Global interval

The SCF.SDV.xx.LIST global interval statement allows you to specify a default setting for interval monitoring.

FormatSCF.SDV.xx.LIST=[PERcent=(low[,high])|DURation=min| [ACTION=NONE|MESsage(userappendstring)|STOPVDEV|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]

Note: The xx in the variable name is the threshold interval to which the parameters apply. This value must start at 01 and increase by one for each separate interval. Gaps are not permitted in the sequence.

Where:

xx

Specifies a value from 01 through a max of 99.

low

Specifies a percent value from 0 through 100.

Syntax conventions 423


high


dur

Specifies the duration time in minutes. You may enter values from 1 to 1440. The default value is 720 (12 minutes).

ACTION

Specifies one of the following:

NONE

No action.

MESsage

Specifies an alphanumeric value. Special characters are not permitted. The message string is limited to 8 characters.

STOPVDEV

Stops virtual device snaps.

USEREXIT(exitname)

Specifies the name of a User Exit module link. The module name is limited to 8 characters, must meet module naming standards, and must reside in a library where EMCSCF has access.

Note: EMC provides a sample user exit in SCF.SAMPLIB and a link-edited version of the sample user exit in SCF.LINKLIB. The name of this sample use exit is TSDVEXIT. You may also supply your own user exit. On entry to the user exit, register 1 contains the address of a parameter list. The first parameter (offset zero from register 1), is the address of an area containing information passed to the user exit from the pool capacity monitor. This area can be mapped using DSECT @MNUEXIT provided in SCF.SAMPLIB. The member name containing the mapping macro is ESFUXPRM.

Refer to “Using a User Exit with the SCF Pool Capacity Monitors” on page 421 for information on using the USEREXIT parameter.

FREQuency

Specifies the number of times the ACTION is to be performed while the current interval remains current. FREQUENCY=NONE specifies to ignore the ACTION. FREQUENCY=ONCE specifies to perform the ACTION once. FREQUENCY=REPEAT specifies to REPEAT the ACTION.

Note that ONCE and REPEAT only apply if the same interval is encountered more than once in succession, where each interval is a definition of percentage full. For example, you could have one interval of PERCENT=(0,100). You could have two intervals of PERCENT=(0,80) and PERCENT=(81,100). Each interval has a "duration" which is the time to elapse until the pool percentage is obtained again.



For instance, when the monitor starts, if the pool is empty, it would select the interval with percent=0. That interval has an action, duration and frequency. Unless frequency is NONE, the action is performed each time that interval is selected again. The duration would be how long to wait before checking the pool again (poll time).

ExampleSCF.SDV.01.LIST = PERCENT=(0,80)SCF.SDV.01.LIST = DURATION=10SCF.SDV.01.LIST = ACTION=NONESCF.SDV.02.LIST = PERCENT=(80,90)SCF.SDV.02.LIST = DURATION=5SCF.SDV.02.LIST = ACTION=MESSAGE(message)SCF.SDV.02.LIST = FREQUENCY=REPEATSCF.SDV.03.LIST = PERCENT=(90,100)SCF.SDV.03.LIST = DURATION=1SCF.SDV.03.LIST = ACTION=USEREXIT(MYEXIT)SCF.SDV.03.LIST = FREQUENCY=ONCE

If the percent value overlaps two ranges (in this example, a value of 80), the higher range action is performed.

The above example specifies three intervals that are selected by the percentage of pool in use. In this case, as long as the pool is less than 80% full, no action is to be taken. It will check again in 10 minutes.

Once the pool reaches 80%-89% full, a message will be issued every 5 minutes.

If the pool reaches 90%-100% full, a user exit will be called once and checked every minute. If the pool drops back to 80%-89%, then the messages will start again every 5 minutes. If it drops below 80% full, then the monitor stops issuing messages and only checks every 10 minutes.

Note that if the pool reaches 95%, the monitor will call the user exit once. Then if another interval is selected (for example, 50%) and it again reaches the 90%-100% interval, the user exit will be called again.

Note: If the percent value does not fall into the ranges specified in the interval thresholds, then the polling interval returns to the default value of 12 hours. That is, despite the percentage being used, the monitor will not “wake up” again for 12 hours to interrogate the pools or controllers. Message SCF1141E will display if gaps are found in the intervals.

Interval number Percent Duration Action Frequency

01 0 - 80 10 minutes None

02 80 - 90 5 minutes Issue message Each time

03 90 - 100 1 minute Call user exit Once

Save Device Capacity monitor syntax 425


Controller

The controller statement allows specification of parameters regarding individual controllers such as whether it is enabled or not and whether a special gatekeeper device should be used.

FormatSCF.SDV.<cntrl#>.LIST = ENAble | DISableSCF.SDV.<cntrl#>.LIST = GATEkeeper=ccuu

Where:

<cntrl#>

Specifies the 5- or 12-digit Symmetrix serial number used to find the gatekeeper device. You can use the 5-digit serial number when the last 5 digits are not duplicated with another controller. Specify the full 12-digit serial number when multiple controllers have the same last 5 digits.


ccuu

Specifies the z/OS device number used as the SCF gatekeeper for the channel-attached device.

Controller interval

The controller interval statements provide the interval setting for individual controllers.

FormatSCF.SDV.<cntrl#>.xx.LIST=[PERcent=(low[,high])|DURation=min|[ACTION=NONE|MESsage(userappendstring)|STOPVDEV|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]

Note: The format is identical to the global interval, except that the variable name contains the 5- or 12-digit controller serial number.

ExampleSCF.SDV.18771.01.LIST = PERCENT=(0,80)SCF.SDV.18771.01.LIST = DURATION=10SCF.SDV.18771.01.LIST = ACTION=MES(PROC1)



Pool interval

The pool interval statements provide the interval setting for individual pools within a controller.

Format SCF.SDV.<cntrl#>.poolname.xx.LIST=[PERcent=(low[,high])|DURation=min|[ACTION=NONE|MESsage(userappendstring)|STOPVDEV|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]

Note: The format is identical to the controller interval, except that the pool name follows the 5- or 12-digit controller serial number.

ExampleSCF.SDV.18771.DEFAULT_POOL.01.LIST = PERCENT=(0,80)SCF.SDV.18771.DEFAULT_POOL.01.LIST = DURATION=10SCF.SDV.18771.DEFAULT_POOL.01.LIST = ACTION=MES(PROC1)

Note: Though creating a pool with embedded spaces in the name is not recommended, if there are any embedded spaces in the pool name, they must be changed to underscores when specifying the name in the pool interval statement.

Save Device Capacity monitor syntax 427


Thin Pool Capacity Monitor syntaxThe Thin Pool Capacity Monitor utilizes the following initialization parameter statement types:

◆ General

◆ Global interval

◆ Controller


◆ Pool interval

Note: Refer to “Thin Pool Capacity Monitor examples” on page 442 for examples of using the THN monitor.

General

The SCF.THN.LIST general purpose statement allows you to enable or disable the Thin Pool Capacity Monitor.

FormatSCF.THN.LIST=ENAble|DISable

Global interval

The SCF.THN.xx.LIST global interval statement allows you to specify a default setting for interval monitoring.

FormatSCF.THN.xx.LIST=[PERcent=(low[,high])|DURation=min|[ACTION=NONE|MESsage(userappendstring)|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]


Where:

xx


low


highSpecifies a percent value from 0 through 100.



durSpecifies the duration time in minutes. You may enter values from 1 to 1440. The default value is 720 (12 hours).

ACTIONSpecifies one of the following:

NONE

No action.

MESsage


USEREXIT(exitname)




FREQuencySpecifies the number of times the ACTION is to be performed while the current interval remains current. FREQUENCY=NONE specifies to ignore the ACTION. FREQUENCY=ONCE specifies to perform the ACTION once. FREQUENCY=REPEAT specifies to REPEAT the ACTION.

Note that ONCE and REPEAT only apply if the same interval is encountered more than once in succession, where each interval is a definition of percentage full. For example, you could have one interval of PERCENT=(0,100). You could have two intervals of PERCENT=(0,80) and PERCENT=(81,100). Each interval has a “duration” which is the time to elapse until the pool percentage is obtained again.


ExampleSCF.THN.01.LIST = PERCENT=(0,80)SCF.THN.01.LIST = DURATION=10SCF.THN.01.LIST = ACTION=NONESCF.THN.02.LIST = PERCENT=(80,90)SCF.THN.02.LIST = DURATION=5

Thin Pool Capacity Monitor syntax 429


SCF.THN.02.LIST = ACTION=MESSAGE(message)SCF.THN.02.LIST = FREQUENCY=REPEATSCF.THN.03.LIST = PERCENT=(90,100)SCF.THN.03.LIST = DURATION=1SCF.THN.03.LIST = ACTION=USEREXIT(MYEXIT)SCF.THN.03.LIST = FREQUENCY=ONCE

If the percent value overlaps two ranges (in this example, a value of 80), the higher range action is performed.

The above example specifies three intervals that are selected by the percentage of pool in use. In this case, as long as the pool is less than 80% full, no action is to be taken. It will check again in 10 minutes.

Once the pool reaches 80%-89% full, a message will be issued every 5 minutes.

If the pool reaches 90%-100% full, a user exit will be called once and checked every minute. If the pool drops back to 80%-89%, then the messages will start again every 5 minutes. If it drops below 80% full, then the monitor stops issuing messages and only checks every 10 minutes.



Controller


FormatSCF.THN.<cntrl#>.LIST = ENAble | DISableSCF.THN.<cntrl#>.LIST = GATEkeeper=ccuuWhere:

<cntrl#>



01 0 - 80 10 minutes None

02 80 - 90 5 minutes Issue message Each time

03 90 - 100 1 minute Call user exit Once




ccuu


Controller interval


FormatSCF.THN.<cntrl#>.xx.LIST=[PERcent=(low[,high])|DURation=min|[ACTION=NONE|MESsage(userappendstring)|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]


ExampleSCF.THN.18771.01.LIST = PERCENT=(0,80)SCF.THN.18771.01.LIST = DURATION=10SCF.THN.18771.01.LIST = ACTION=MES(PROC1)

Pool interval


Format SCF.THN.<cntrl#>.poolname.xx.LIST=[PERcent=(low[,high])|DURation=min|[ACTION=NONE|MESsage(userappendstring)|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]


ExampleSCF.THN.18771.DEFAULT_POOL.01.LIST = PERCENT=(0,80)SCF.THN.18771.DEFAULT_POOL.01.LIST = DURATION=10SCF.THN.18771.DEFAULT_POOL.01.LIST = ACTION=MES(PROC1)


Thin Pool Capacity Monitor syntax 431


DSE Capacity monitor syntaxBeginning with Enginuity 5772, you can activate and deactivate the SRDF/A Delta Set Extension (DSE) feature. The DSE feature extends the cache space available for an SRDF/A session by off-loading some or all of its cycle data from cache to preconfigured DSEPOOL devices which are similar to SAVE device pools. This extra space permits SRDF/A to keep running during transient problems such as temporary link loss.

This feature can be controlled using the SCF.DSE statements described in this seciton. You can name the SRDF/A DSE pool, identify the pool device emulation type, specify the percentage of the Symmetrix array’s write pending limit, and specify whether SRDF/A DSE is automatically enabled when an SRDF/A session is activated for the group.

The DSE Capacity monitor utilizes the following initialization parameter statement types:

◆ General

◆ Global interval

◆ Controller


◆ Pool interval

General

The SCF.DSE.LIST general purpose statement allows you to enable or disable the DSE Capacity monitor.

Format

SCF.DSE.LIST = ENAble | DISable

Global interval

The SCF.DSE.xx.LIST global interval statement provides a default setting for interval monitoring.

FormatSCF.DSE.xx.LIST=[PERcent=(low[,high])|DURation=seconds| [ACTION=NONE|MESsage(userappendstring)|STOPVDEV|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]


Where:

xx




low


high


dur

Specifies the duration time in seconds. You may enter values from 1 to 86400. The default value is 43200 (12 hours).

ACTION

Specifies one of the following:

NONE

No action.

MESsage


USEREXIT(exitname)




FREQuency

Specifies the number of times the ACTION is to be performed while the current interval remains current. FREQUENCY=NONE specifies to ignore the ACTION. FREQUENCY=ONCE specifies to perform the ACTION once. FREQUENCY=REPEAT specifies to REPEAT the ACTION.

Note that ONCE and REPEAT only apply if the same interval is encountered more than once in succession, where each interval is a definition of percentage full. For example, you could have one interval of PERCENT=(0,100). You could have two intervals of PERCENT=(0,80) and PERCENT=(81,100). Each interval has a "duration" which is the time to elapse until the pool percentage is obtained again.

DSE Capacity monitor syntax 433



ExampleSCF.DSE.01.LIST = PERCENT=(0,80)SCF.DSE.01.LIST = DURATION=10SCF.DSE.01.LIST = ACTION=NONESCF.DSE.02.LIST = PERCENT=(80,90)SCF.DSE.02.LIST = DURATION=5SCF.DSE.02.LIST = ACTION=MESSAGE(message)SCF.DSE.02.LIST = FREQUENCY=REPEATSCF.DSE.03.LIST = PERCENT=(90,100)SCF.DSE.03.LIST = DURATION=1SCF.DSE.03.LIST = ACTION=USEREXIT(MYEXIT)SCF.DSE.03.LIST = FREQUENCY=ONCE

If the percent value overlaps two ranges (in this example, a value of 80), the higher range action is performed. The above example specifies three intervals that are selected by the percentage of pool in use. In this case, as long as the pool is less than 80% full, no action is to be taken. It will check again in 10 seconds. Once the pool reaches 80%-89% full, a message will be issued every 5 seconds.

If the pool reaches 90%-100% full, a user exit will be called once and checked every second. If the pool drops back to 80%-89%, then the messages will start again every 5 seconds. If it drops below 80% full, then the monitor stops issuing messages and only checks every 10 seconds.




01 0 - 80 10 seconds None

02 80 - 90 5 seconds Issue message Each time

03 90 - 100 1 second Call user exit Once



Controller


FormatSCF.DSE.<cntrl#>.LIST=ENAble|DISableSCF.DSE.<cntrl#>.LIST=GATEkeeper=ccuu

Where:

<cntrl#>



ccuu


Controller interval


FormatSCF.DSE.<cntrl#>.xx.LIST=[PERcent=(low[,high])|DURation=min| [ACTION=NONE|MESsage(userappendstring)|STOPVDEV|USEREXIT(exitname)]|FREQuency=[NONE|ONCE|REPEAT]]


ExampleSCF.DSE.18771.01.LIST = PERCENT=(0,80)SCF.DSE.18771.01.LIST = DURATION=10SCF.DSE.18771.01.LIST = ACTION=MES(PROC1)

DSE Capacity monitor syntax 435


DSE Spillover Time monitor syntaxYou can specify multiple time thresholds to report DSE pool spillover has been occurring. The following SCF initialization parameters allow you to specify up to three time durations at which you wish messages to be issued:

◆ SCF.DSE.WARNING

Specifies the threshold value, in number of minutes, to issue an alert that DSE spillover has been occurring. Valid values are 02 to 720.

◆ SCF.DSE.MINOR

Specifies the threshold value, in number of minutes, to issue an alert that DSE spillover has been occurring. Valid values are 02 to 720. This value must exceed the value of SCF.DSE.WARNING.

◆ SCF.DSE.MAJOR

Specifies the threshold value, in number of minutes, to issue an alert that DSE spillover has been occurring. Valid values are 02 to 720. This value must exceed the value of SCF.DSE.MINOR.

For example:

SCF.DSE.WARNING=30SCF.DSE.MINOR=90SCF.DSE.MAJOR=270

DSE Spillover Time monitor syntax 437


Thin CKD space reclamationStarting with ResourcePak Base version 7.4, and Enginuity level 5876 or higher, EMCSCF provides a Thin space reclamation (TRU) environment that records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the Symmetrix free track pool.

Initialization of the EMCSCF TRU monitor subtask begins by creating a control block in common storage used for TRU communications and anchoring the TRU device table. The subtask then reads the EMCSCF INI parameters that apply to the TRU environment. The EMCSCF devices are scanned, and any thin devices found are matched against the TRU include/exclude list. Thin devices with the PERSIST attribute can be found in the device list, but are not be monitored.

Note: The TRU monitor only monitors devices that have been included with the SCF.TRU.DEV.INCLUDE.LIST statement. If you wish for all thin devices to be monitored, you can simply specify "SCF.TRU.DEV.INCLUDE.LIST=0000-FFFF”. The TRU monitor then determines which devices are thin and should be monitored.

The mainline of the EMCSCF TRU monitor subtask consists of waiting and scheduling work. Whenever the task wakes up, it scans the TRU device table to see if any devices have needs. Most needs result in scheduling the SCAN or the RECLAIM utility. But other activities include handling new device BIND or old device UNBIND or processing of commands like HOLD/RELEASE or START/STOP.

The scheduling of the SCAN or RECLAIM utility is the main purpose of this monitor subtask. You can control how these utilities are scheduled. As mentioned above, one way is to run the utilities from the EMCSCF TRU Monitor Subtask. The other is to submit these utilities as a zOS Started Task, which can be initiated as a batch job and run outside of the EMCSCF environment.

The general TRU process includes the following steps:

1. EMCSCF discovers and monitors TDEVs that are not bound with the PERSIST attribute.

2. The EMC z/OS SCRATCH exit (or SCAN utility )identifies and marks the tracks that are eligible for reclamation.

3. EMCSCF periodically updates (with the RECLAIM utility) the list of tracks containing no user records. This update can also be performed by an optional on-demand batch utility.

4. The Enginuity Zero Space Reclaim process runs on the Symmetrix system as a background task and reclaims tracks with no user records on CKD volumes.

IMPORTANT

The Symmetrix system does not start looking for tracks until the RECLAIM utility runs. The RECLAIM utility is simply erasing tracks identified by either the SCRATCH exit or the SCAN utility, and starts the background task in the Symmetrix system. The SCRATCH exit can directly mark tracks for reclaim, saving time and work in the RECLAIM utility, or it can identify the tracks in the SDDF session for later processing by the RECLAIM utility



Space reclamation requires:

◆ A locally attached Symmetrix volume

◆ And EMC recommends an indexed VTOC. Without it, temporary dataset processing does not occur, and the pool space size may not reflect a correct usage percentage.)

Refer to “Initialization parameters” on page 60 for information regarding the TRU initialization parameters in the EMCSCF configuration file, and to “TRU monitor operator commands” on page 348 for information regarding the TRU commands.

Running TRU as a started task

The following provides two sample JCL procedures for initiating the TRU monitor utility as a started task to perform SCAN and RECLAIM tasks in batch mode.

Reclaim procedure //RECLAIM PROC CCUU=,TYPE=RECLAIM//ESFTRURC EXEC PGM=ESFTRURC,PARM='&TYPE,&CCUU'//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SCF$nnn DD DUMMY//SYSABEND DD SYSOUT=*//ESFTRURC DD SYSOUT=*

Scan procedure //SCAN PROC CCUU=,TYPE=SCAN//ESFTRURC EXEC PGM=ESFTRURC,PARM='&TYPE,&CCUU'//STEPLIB DD DISP=SHR,DSN=ds-prefix.LINKLIB//SYSABEND DD SYSOUT=*//SCF$nnn DD DUMMY//ESFTRURC DD SYSOUT=*

The RECLAIM activity has the most impact on other device activity. Using the TRU initialization parameters, EMC recommends the following options:

◆ Limit the number of RECLAIM tasks that can be run simultaneously.

◆ Limit the time-of-day operations.

◆ Limit the scratch exit related wait time.

◆ Allow the TRU monitor to schedule the SCAN and RECLAIM tasks as started tasks (specify STCNAME) and do not run them as subtasks in SCF.

The idea is that if a user batch job scratches a dataset, a new dataset may be allocated in its place. So there is a wait time available which allows the new user allocation to occur before we attempt to reclaim the space.

Note: SCAN and RECLAIM can also be submitted as user-initiated batch jobs.

Thin CKD space reclamation 439


TRU SCAN utility

The TRU SCAN utility accepts the following three parameters:

◆ SCAN (the operation name)

◆ The device CCUU

◆ The keyword DEBUG

The device may be online or offline and a VTOC Index is recommended. The device must also be channel-attached and have a CCUU available. Non-channel or remotely-attached devices cannot be processed by the utility. The utility must be run in an LPAR with EMCSCF and the TRU environment active.

The device must be a thin device that is being monitored by the EMCSCF TRU Monitor Subtask and have a TRU SDDF session.

Processing of the SCAN begins by obtaining the SYSVTOC RESERVE on the device. Next the VTOC freespace information is obtained. Then each entry in the freespace list is applied to the TRU SDDF session. When the SYSVTOC RESERVE is released the process is complete.

The TRU SCAN utility may be run as part of a user-specified BATCH JOB in order to schedule the reclaim activity to fit into the customer schedule. This may be necessary if the device is being used on other LPARs and not being monitored there.

Typically, the SCAN utility only runs for a few seconds on a volume.

Note: If there is an issue and debug output is requested from EMC, specify the keyword DEBUG as parameter #3 on the execute statement.

TRU RECLAIM utility

The TRU RECLAIM utility accepts two the following three parameters:

◆ RECLAIM (the operation name)

◆ The device CCUU

◆ The keyword DEBUG

The device may be online or offline, and a VTOC Index is recommended. The device must also be channel attached and have a CCUU available. Non-channel or remotely-attached devices cannot be processed by the utility. The utility must be run in an LPAR with EMCSCF and the TRU environment active.

The device must be a thin device that is being monitored by the SCF TRU Monitor Subtask and have a TRU SDDF session.

The RECLAIM utility operates in a series of passes. For each pass, it obtains the SYSVTOC RESERVE, performs some work, and releases the SYSVTOC RESERVE before starting over.

Each pass processes as much as feasible while holding the SYSVTOC RESERVE. For idle devices, this may be a lot, for busy devices, this may be very little. For online devices, after the reserve processing is performed, it attempts to allocate a temporary dataset over space that is to be erased and performs a portion of the erase activity outside of the time while holding the SYSVTOC RESERVE.



Devices that are offline to an LPAR are still supported, but for offline devices, reclaim processing does not use a temporary dataset method the way it does for online devices, and takes place while holding the SYSVTOC RESERVE.

The TRU RECLAIM utility may be run as part of a user-specified BATCH JOB in order to schedule the reclaim activity to fit into the customer schedule.

As processing of a dataset is completed, the dataset is scratched and processing continues with the next dataset. The size of each dataset is limited to (1) 1000 cylinders or (2) 21,000 cylinders if in EAV CMS space. The size factor may be changed via an SCF INI parameter. The default factor is 1000 meaning 1000 cylinders in TMS space and 1000*21 cylinders in CMS space.

Note: If there is an issue and debug output is requested from EMC, specify the keyword DEBUG as parameter #3 on the execute statement.

Limitations

TRU limitations include:

◆ The z/OS Scratch Exit should be run on all LPARs attached to the Symmetrix in order to capture and record the scratch activity. If it is not running on a LPAR that is scratching datasets on thin devices, the space is not automatically reclaimed by this implementation.

◆ At any point in time, it is possible for the z/OS VTOC free space map, the SDDF session information, and the Symmetrix thin device allocation map to all reflect different information. This in inherent in the implementation. In a quiesced, steady state, they should show very much the same, if not identical, information. The z/OS VTOC free space map is the known allocation of space. But it does not indicate which tracks have been written to and are allocated. The SDDF session only reflects tracks that have not been processed by the SCF subtask. Depending on user options, there may always be some tracks not processed. The Symmetrix thin device allocation map shows which tracks have been written to, and has no knowledge of which tracks have been allocated and unused.

◆ Due to allocation and SMF recording, when running the RECLAIM function as a subtask of SCF, the temporary dataset method is not used.

◆ It is recommended that RECLAIM be setup to run as a started task in order to limit the amount of time a volume is RESERVED and the overall impact on SCF processing.

◆ Reclaim will not occur while a device has either active clone, snap, or virtual sessions.

Thin CKD space reclamation 441


Thin Pool Capacity Monitor examplesThe following three examples illustrate the use of the Thin Device Capacity (THN) monitor.

Example of SCF initialization parameters

The following example is a symmetrix system that has two pools defined. The THN monitor can monitor each pool separately. If the pools do not exist when ResourcePak Base has started, a THN,REFRESH command should be issued for the monitor to begin polling.

The SCF ini parms for monitoring two pools might look something like the following.

SCF.THN.00057.LIST=ENA SCF.THN.00057.LIST=GATE=2101 *SCF.THN.00057.MFCKD1.01.LIST=PERCENT(01,20) SCF.THN.00057.MFCKD1.01.LIST=DURATION=20 SCF.THN.00057.MFCKD1.01.LIST=ACTION=MES(LOWLOWXX) SCF.THN.00057.MFCKD1.01.LIST=FREQUENCY=REPEAT SCF.THN.00057.MFCKD1.02.LIST=PERCENT(21,65) SCF.THN.00057.MFCKD1.02.LIST=DURATION=05 SCF.THN.00057.MFCKD1.02.LIST=ACTION=MES(LOWMEDXX) SCF.THN.00057.MFCKD1.02.LIST=FREQUENCY=REPEAT SCF.THN.00057.MFCKD1.03.LIST=PERCENT(66,99) SCF.THN.00057.MFCKD1.03.LIST=DURATION=05 SCF.THN.00057.MFCKD1.03.LIST=ACTION=MES(FIXINGX) SCF.THN.00057.MFCKD1.03.LIST=FREQUENCY=REPEAT * SCF.THN.00057.MSFSTD.01.LIST=PERCENT(01,40) SCF.THN.00057.MSFSTD.01.LIST=DURATION=20 SCF.THN.00057.MSFSTD.01.LIST=ACTION=MES(LOWPRIOR) SCF.THN.00057.MSFSTD.01.LIST=FREQUENCY=REPEAT SCF.THN.00057.MSFSTD.02.LIST=PERCENT(41,75) SCF.THN.00057.MSFSTD.02.LIST=DURATION=05 SCF.THN.00057.MSFSTD.02.LIST=ACTION=MES(MEDIUMXX) SCF.THN.00057.MSFSTD.02.LIST=FREQUENCY=REPEAT SCF.THN.00057.MSFSTD.03.LIST=PERCENT(76,90) SCF.THN.00057.MSFSTD.03.LIST=DURATION=05 SCF.THN.00057.MSFSTD.03.LIST=ACTION=MES(HIGHXXX) SCF.THN.00057.MSFSTD.03.LIST=FREQUENCY=REPEAT *

Result of the above parameters.

SCF1161I THN POOL 0001956-00057 - MFCKD1 IS AT 3% UTILIZATION OF THINPOOL SPACE - LOWLOWXX SCF1161I THN POOL 0001956-00057 - MSFSTD IS AT 40% UTILIZATION OF THINPOOL SPACE - LOWPRIOR



Example of THN monitor for a specific Symmetrix system

The following is an example of the THN monitor designating a specific Symmetrix system.

SCF.THN.00086.LIST=ENA SCF.THN.00086.LIST=GATE=3A0F *SCF.THN.00086.01.LIST=PERCENT=(01,40) SCF.THN.00086.01.LIST=DURATION=20 /* COMMENT */ SCF.THN.00086.01.LIST=ACTION=MES(THINALRT) SCF.THN.00086.01.LIST=FREQUENCY=REPEAT SCF.THN.00086.02.LIST=PERCENT=(41,75) SCF.THN.00086.02.LIST=DURATION=05 /* COMMENT */ SCF.THN.00086.02.LIST=ACTION=MES(THINURGT) SCF.THN.00086.02.LIST=FREQUENCY=REPEAT SCF.THN.00086.03.LIST=PERCENT=(76,90) SCF.THN.00086.03.LIST=DURATION=05 /* COMMENT */ SCF.THN.00086.03.LIST=ACTION=MES(THINARG) SCF.THN.00086.03.LIST=FREQUENCY=REPEAT *


SCF1160I THN CONTROLLER 0001957-00086 IS AT 9% UTILIZATION OF THINPOOL SPACE ( 0 3390- 9 FBA- 0) - THINALRT

Example of global THN monitor

The following is an example of a global THN monitor.

SCF.THN.LIST=ENA SCF.THN.01.LIST=PERCENT(01,40) *SCF.THN.01.LIST=DURATION=20 SCF.THN.01.LIST=ACTION=MES(LOWPRIOR) SCF.THN.01.LIST=FREQUENCY=REPEAT SCF.THN.02.LIST=PERCENT(41,75) SCF.THN.02.LIST=DURATION=05 SCF.THN.02.LIST=ACTION=MES(MEDIUMPR) SCF.THN.02.LIST=FREQUENCY=REPEAT SCF.THN.03.LIST=PERCENT(76,90) SCF.THN.03.LIST=DURATION=05 SCF.THN.03.LIST=ACTION=MES(CRITICL) SCF.THN.03.LIST=FREQUENCY=REPEAT *


SCF1125I THN -- INI PARAMETERS LOADED SCF1160I THN CONTROLLER 0001956-00057 IS AT 2% UTILIZATION OF THINPOOL SPACE ( 0 3390- 2 FBA- 0) - LOWPRIOR SCF1160I THN CONTROLLER 0001957-00079 IS AT 9% UTILIZATION OF THINPOOL SPACE ( 0 3390- 9 FBA- 0) - LOWPRIOR SCF1160I THN CONTROLLER 0001957-00086 IS AT 9% UTILIZATION OF THINPOOL SPACE ( 0 3390- 9 FBA- 0) - LOWPRIOR SCF1160I THN CONTROLLER 0001956-00123 IS AT 39% UTILIZATION OF THINPOOL SPACE ( 0 3390- 39 FBA- 3) - LOWPRIOR SCF1160I THN CONTROLLER 0001926-02840 IS AT 10% UTILIZATION OF THINPOOL SPACE ( 0 3390- 0 FBA- 10) - LOWPRIOR SCF1160I THN CONTROLLER 0001926-04123 IS AT 3% UTILIZATION OF THINPOOL SPACE ( 0 3390- 3 FBA- 0) -

Thin Pool Capacity Monitor examples 443


LOWPRIOR SCF1160I THN CONTROLLER 0001926-04124 IS AT 7% UTILIZATION OF THINPOOL SPACE ( 0 3390- 0 FBA- 7) - LOWPRIOR


CHAPTER 9Monitoring SRDF/A and Write Pacing

This chapter describes how to use the SRDF/A and Write Pacing monitors.

◆ Overview............................................................................................................... 446◆ SRDF/A and WPA Monitor initialization parameters ............................................... 452◆ Optional user exit.................................................................................................. 453◆ SRDF/A and WPA Monitor SMF records .................................................................. 453

Monitoring SRDF/A and Write Pacing 445

Monitoring SRDF/A and Write Pacing

OverviewResourcePak Base provides SRDF/A and Write Pacing monitors to perform the following functions:

◆ Find EMC Symmetrix controllers that are running SRDF/A

◆ Collect and write SMF data about those controllers

◆ Expose relevant information regarding SRDF/A Write Pacing activities within the Symmetrix. Pacing activities are collected at the group and device level.

◆ Optionally, invoke “SRDF/A Single Session Auto Recovery operations” on page 448 to recover a dropped single-session.

After you have installed ResourcePak Base, if the SRDF/A and WPA Monitors have been enabled, they will start up as subtasks of SCF.

Note: The SCF environment name is ASY for the SRDF/A monitor, and WPA for the Write Pacing monitor.

SRDF/A Write Pacing

SRDF/A Write Pacing provides the a method of extending the availability of SRDF/A, which provides you with the abililty to prevent conditions that can result in cache overflow.

The WPA monitor exposes relevant information regarding pacing activities within the Symmetrix system. Pacing activities are collected at both the group and device level.

You can specify which controllers and SRDF groups are monitored. The level of detail, whether on the group and/or the device level, is also done according to what you specify.

The data that can be collected and reported on by the monitor includes:

◆ Changes in the ARMED state by device.

◆ Total paced delay by device.

◆ Total paced track count by device.

◆ Changes in the ENABLED/SUPPORTED/ARMED/PACED state for the group.

◆ Total paced delay for the group.

◆ Total paced track count for the group.

The data collected by the monitor is presented in the same manner as the current SRDF/A monitor information, as alerts and/or written SMF records.

LimitationsLimitations of the WPA monitor include:

◆ Monitoring is only captured on local controllers. Monitoring is performed on the SRDF group level by controller, and on the device level by SRDF group and by controller.

◆ Monitor state and count messages are only captured on the group level, but device level statistics can be specified for recording to SMF.

◆ Enginuity release 5876 or higher is required.



SRDF/A Write Pacing Monitor OperationThe WPA monitor is a logical extension of the existing SRDF/A monitor , but it is also a separate environment of the ResourcePak Base.

The WPA monitor records SRDF/A write pacing statistics to SMF. Currently, there are no alerts or any other functions other than writing SMF records.

The WPA monitor uses the SMF record type specified in the SCF initialization parameters. If omitted in the SCF initialization parameters, it defaults to the SMF record type used by the SRDF/A monitor.

Refer to the description of the #SQ SRDFA_WP_VOL command in the EMC SRDF Host Component for z/OS Product Guide for an example and a description of the display information.

Message functionality

Messaging functionality provides the following information:

◆ State change

◆ Status

◆ Include and exclude processing

Control of the messages is provided via the SCF.WPA.MSGLEVEL initialization parm. This allows you to specify the messages you want to see by including message level categories as a comma separated list on this parameter. WPA messages are included with all the other Mainframe Enablers messages and can be found in the EMC Mainframe Enablers Message Guide.

Include and Exclude processing

Controlling what Symmetrix systems are monitored by the WPA monitors is accomplished through the use or omission of the SCF.WPA.EXCLUDE.CNTRL{.LIST} and SCF.WPA.INCLUDE.CNTRL{.LIST} initialization parameters.

The logic of how the WPA monitor processes and interprets these parameters is described in the following 11 steps:

Include/excludeprocessing steps 1 to 3

1. If there are no EXCLUDE or INCLUDE statements in the SCF INI parameter file then no exclude or include structures are built for filtering and the logic skips to the “Standard monitoring cycle steps 4 to 11” on page 448, starting with step 4 .

2. If there are INCLUDE or EXCLUDES parameters in the SCF INI parm file, they are parsed and validated. Statements failing validation are ignored. Those passing validation are then used to build exclude and include structures. These structures are built using the controller serial numbers as the logical keys.

3. The exclude and include structures are scanned for duplicate serial number keys. The excludes are scanned first. The lists of excluded SRDF groups of structures with duplicate keys are combined and the duplicates are eliminated. The same process is performed for the include structures.

If there are both include and exclude structures, then exclude and include structures are scanned for duplicate serial number keys. Exclude and include structures with duplicate serial number keys are combined and any SRDF groups in the include list that are also in the exclude list are eliminated.

Overview 447


Standard monitoringcycle steps 4 to 11

For each monitoring cycle the following steps are always performed.

4. The monitor obtains a list of all local Symmetrix systems known to SCF.

5. From the list of controllers the monitor eliminates all controllers that are not at Enginuity level 5876 or higher.

6. If there are excludes structures, the list of controllers is trimmed by eliminating any that have all SRDF groups excluded.

7. All controllers in the list are queried to report on group level pacing statistics or on device pacing statistics.

8. Pacing statistics data records are filtered out according to the SCF.WPA.SMF.FILTER, if specified in the SCF INI file.

9. After any SCF.WPA.SMF.FILTER specified processing, exclude and include filtering of pacing statistics data records is performed. Excludes are processed first followed by includes.

10. The pacing statistics data records remaining after all filtering is performed are used to generate monitoring messages as specified by any SCF.WPA.MSGLEVEL parameter found in the SCF INI file.

11. If SMF recording was requested then all the pacing statistics data records are written to SMF.

SRDF/A Single Session Auto Recovery operations

Starting with ResourcePak Base V7.2, you can enable automatic recovery for SRDF/A single sessions without MSC. You define SRDF/A Single Session Auto Recovery settings in the SCF initialization parameters and control the process with the SRDF/A Monitor. You can also use the SRDF Host Component SC RECOVER command to initiate recovery.

Note: The SRDF/A Monitor is integrated in the ASY monitor. To enable the SRDF/A Monitor when the task has not yet started, you need to set the initialization parameter, SCF.ASY.MONITOR to ENABLE, and then issue an ASY,REFRESH command.

The sample EMCRCVRY procedure included in the SAMPLE file can be used for SRDF/A Single Session Auto Recovery.

Using the SRDF/A Monitor

When the drop of an SRDF/A group is detected and SRDF/A Single Session Auto Recovery is enabled, the auto recovery procedure will be initiated. The SRDF/A Monitor will recover a non-MSC managed SRDF/A group when a state change from active to inactive is detected.

When the SRDF/A Monitor is enabled, it detects SRDF/A group state changes and the current state is determined and retained. If you disable the SRDF/A Monitor, the current state is not retained.

If a group is inactive when the SRDF/A Monitor is enabled, SRDF/A Single Session Auto Recovery will not begin for the group. In this case you must manually recover the group using the ASY,RECOVER,SRDFA command.

The SRDF/A Monitor accepts the ASY,SSAR,ENABLE, ASY,SSAR,DISABLE and ASY,RECOVER,SRDFA commands to control or manually recover groups.



Limitations

When the SRDF/A monitor is used to initiate SRDF/A Single Session Auto Recovery procedures, the following restrictions apply.

◆ To avoid running multiple recoveries for the same group, only one instance of SCF should control the recovery process. No cross-LPAR communication is supported. This applies to SCFs that share controllers.

◆ SRDF/A Single Session Auto Recovery only applies to the primary side (R1). If multiple SCFs have SRDF/A Single Session Auto Recovery enabled and a managed group drops, both instances of SCF will try to recover it. Use group specification and the LPAR designator parameters to prevent this. Unpredictable results can occur if multiple recovery jobs run for the same group.

◆ All controllers must be locally attached.

◆ BCV management (gold copy) requires a valid TimeFinder relationship for each partner R2 STD device (an Established or Split BCV) and must be made prior to invoking SRDF/A Single Session Auto Recovery.

◆ PENDDROP and other purposeful drops of SRDF/A (such as PENDDEACT, DEACT-TO-ADCOPY, DEACT-TO-ADCOPY-DISK, or CONS_DEACT) will be recovered. To avoid this behavior, disable SRDF/A Single Session Auto Recovery, be sure the group is not specified for recovery, or use the SCF.SS.AUTO.RECOVER=ENABLE(MANUAL) parameter to control manual recoveries.

Defining the initialization parameters

The following items describe how to define the SRDF/A Single Session Auto Recovery initialization parameters described in Chapter 3, “Configuration File and Initialization Parameters.”

◆ You can designate specific groups for recovery using the SCF.SS.AUTO.RECOVER.ser#.rdfg#=option parameter. Once a single group is designated to be recovered, only the specified group or groups will be recovered. If no specific group is designated, then all dropped SRDF/A groups will be recovered. This includes groups of FBA devices. For more information, see the SRDF Host Component CONFIG_FBA option.

◆ Global parameters are used at the group level for any and all groups that do not have corresponding values defined. Missing required global parameters will produce a message and SRDF/A Single Session Auto Recovery will not enable.

◆ You can use the SCF.SS.AUTO.RECOVER.LPAR parameter to ensure that SRDF/A Single Session Auto Recovery is only enabled on a single LPAR.

◆ BCV Phase 1 and 2 processing is supported. You can specify BCV options at the group controller and/or group level using the SCF.SS.AUTO.RECOVER.BCV initialization parameters.

◆ When making a change to the ASY parameters in the SCF initialization file you must execute an INI,REFRESH and an ASY,REFRESH before the parameters will be in effect.

◆ The ASY DISABLE and REFRESH commands are not allowed while SRDF/A Single Session Auto Recovery sessions exist.

Overview 449


SRDF/A Monitor startup process

When SCF starts, it checks to make sure that the SRDF/A Monitor is currently enabled through the SCF.ASY.MONITOR initialization parameter.

Note: “SCF.ASY.MONITOR” on page 66 provides more information.

If enabled, the SRDF/A Monitor takes the following steps:

1. The SRDF/A Monitor queries the locally attached Symmetrix controllers to determine if any SRDF/A sessions exist, either on the primary side or on the secondary side.

2. The SRDF/A Monitor takes one of the following steps:

• If the SRDF/A Monitor finds no SRDF/A sessions, it suspends for the period of time specified by the SCF.ASY.POLL.INTERVAL initialization parameter. When that time expires, the SRDF/A Monitor returns to step 1.

• If the SRDF/A Monitor finds SRDF/A sessions, it performs the operations described in “SRDF/A Monitor polling steps” on page 450. Then the SRDF/A Monitor suspends for the period of time specified by the SCF.ASY.POLL.INTERVAL parameter. When that time expires, the SRDF/A Monitor returns to step 1.

SRDF/A Monitor polling steps

Each time the SRDF/A Monitor finds an SRDF/A session when it polls, the SRDF/A Monitor performs the following steps:

1. If the SCF.ASY.SMF.RECORD initialization parameter is set, the SRDF/A Monitor writes SMF records, including:

• INTERVAL

• ACTIVITY

Depending on the value of the SCF.ASY.SMF.POLL initialization parameter, the SRDF/A Monitor writes an INTERVAL record every n polling periods.

Note: “SCF.ASY.SMF.POLL” on page 67 provides more information.

2. If SCF.SS.AUTO.RECOVERY is enabled and MANUAL is not specified, the monitor will attempt to recover all single-session SRDF/A groups if the following conditions are met:

• The groups are not MSC-managed.

• The group are SRDF/A groups.

• The group state has changed from active to inactive.

Note: “SCF.SS.AUTO.RECOVER” on page 114 provides more information.

In addition, if SCF.SS.AUTO.RECOVERY is enabled and one of more SCF.SS.AUTO.RECOVER.ser#.rdfg#=option statements are also specified, the monitor will attempt to recover the specified SRDF/A group if the following conditions are met:

• The group is not MSC-managed.



• The group is an SRDF/A group.

• The group is not active.

• The group number matches the group number in the specified statement.

Note: “SCF.SS.AUTO.RECOVER.ser#.rdfg#=option” on page 114 provides more information.

3. Checks primary side SRDF/A sessions for change of status.

The SRDF/A Monitor calls and passes data to a User Exit routine1 if one of the following occurs:

– An SRDF/A session changed from ACTIVE to INACTIVE or from INACTIVE to ACTIVE.

– Tolerance Mode changes from ON to OFF or from OFF to ON.

– The calculated Secondary Delay is greater than or equal to the Secondary Delay Threshold value you specified in the SCF.ASY.SECONDARY.DELAY initialization parameter.

4. Determines whether you have issued a shutdown.

If the SRDF/A Monitor detects a shutdown command, and there are no active single-session recovery sessions, then it terminates.

If there are active sessions, the SRDF/A Monitor continues the polling process. SCF cannot be shut down while an active single-session auto recovery operation is in process. The recovery job must complete or be cancelled prior to SCF being shut down.

5. The SRDF/A Monitor suspends for the period of time specified in the SCF.ASY.POLL.INTERVAL initialization parameter.

1. Specify the User Exit routine through the SCF.ASY. initialization parameter. If you do not specify a User Exit routine, no User Exit is called when the SRDF/A Monitor detects a change in activity.

Overview 451


SRDF/A and WPA Monitor initialization parametersSpecify the initialization parameters as a series of statements in the following format:

keyword = value

Note: The keyword must begin in column 1. An asterisk (*) in column 1 denotes a comment.

Save the initialization parameter statements as a member of the same parameter library you use for ResourcePak Base. This parameter library must be pointed to by the SCFINI DD statement of the EMCSCF procedure.

Table 14 summarizes the initialization parameters associated with the SRDF Host Component and the Write Pacing monitor:

Table 14 SRDF/A Monitor initialization parameters

Parameter Required/optional Default setting

“SCF.ASY.MONITOR” on page 66 Required DISABLE

“SCF.ASY.POLL.INTERVAL” on page 66 Required 5

“SCF.ASY.SECONDARY_DELAY” on page 66 Required 120 (seconds)

“SCF.ASY.SMF.POLL” on page 67 Required 6

“SCF.ASY.SMF.RECORD” on page 67 Optional None

“SCF.ASY.MONITOR” on page 66 Optional None

“SCF.WPA.EXCLUDE.CNTRL” on page 137 Optional None

“SCF.WPA.INCLUDE.CNTRL” on page 138 Optional None

“SCF.WPA.MONITOR” on page 139 Required DISABLE

“SCF.WPA.MSGLEVEL” on page 139 Optional BASIC

“SCF.WPA.POLL.INTERVAL” on page 139 Optional 5 or same as SCF.ASY.SMF.POLL.INTERVAL

“SCF.WPA.SMF” on page 140 Optional OFF

“SCF.WPA.SMF.FILTER” on page 140 Optional No filtering. All data records are recorded, even if the data is all zeroes.

“SCF.WPA.SMF.RECORD” on page 141 Optional Nullor same as SCF.ASY.SMF.RECORD if it exists, and SMF recording will not take place.

“SCF.WPA.STYPES” on page 141 Optional All types



Table 15 summarizes the initialization parameters associated with SRDF/A Single Session Auto Recovery:

Optional user exitMember SCFRDFAX in SCF.SAMPLIB is a sample user exit for the optional user exit that is called when the state of an SRDF/A session changes. This sample includes the structure of the information that is passed to the user exit.

SRDF/A and WPA Monitor SMF recordsMacro members SRDFAUX1 and @RDFASMF in SCF.SAMPLIB define the structure of the SMF records. Both macros must be specified. SRDF/A and WPA uses SMF records to record state information that is useful for both ongoing operations and for diagnosing trouble situations. The records supported by EMC for mainframe SRDF/A installations are presented in Table 16. The data applies to an individual SRDF/A group.

Table 15 SRDF/A Single Session Auto Recovery parameters

Parameter Required/optional

“SCF.SS.AUTO.RECOVER” on page 114 Required

“SCF.SS.AUTO.RECOVER.ser#.rdfg#=option” on page 114 Optional

“SCF.SS.AUTO.RECOVER.BCV= BCV (startup_option,post_recovery_option)” on page 115

Required

“SCF.SS.AUTO.RECOVER.BCV.ser#.rdfg#=BCV (startup_option,post_recovery_option)” on page 116

Optional

“SCF.SS.AUTO.RECOVER.ITRK=itrk” on page 116 Required

“SCF.SS.AUTO.RECOVER.ITRK.ser#=itrk” on page 117 Optional

“SCF.SS.AUTO.RECOVER.JOBNAME=jobname” on page 117 Required

“SCF.SS.AUTO.RECOVER.JOBNAME.ser#=jobname” on page 118 Optional

“SCF.SS.AUTO.RECOVER.LPAR=id” on page 118 Required

“SCF.SS.AUTO.RECOVER.MINDIR=##” on page 119 Required

“SCF.SS.AUTO.RECOVER.MINDIR.ser#=##” on page 119 Optional

“SCF.SS.AUTO.RECOVER.PREFIX=hccpfx” on page 120 Required

“SCF.SS.AUTO.RECOVER.PROC=procname” on page 120 Required

Table 16 SMF record fields (page 1 of 4)

Field Description

SRDFAUX1_MISC_FLAGS Four flag bytes

SRDFAUX1_MISC_FLAG1 NULL

SRDFAUX1_MISC_FLAG2 NULL

SRDFAUX1_MISC_FLAG3 Flag byte 3

Optional user exit 453


• SRDFAUX1_TOLERANCE_MODE B'00000001' TOLERANCE MODE ON SRDF/A will tolerate inconsistency of the R2 side and will not perform an SRDF/A drop to preserve consistency.

• SRDFAUX1_CLEANUP_RUNNING B'00000010' CLEANUP RUNNING The SRDF/A cleanup process is active on the R2 side.

• SRDFAUX1_MS_HOST_MANAGED_CONSISTENCY B'00000100' HOST MANAGED CONSISTENCY IS ACTIVEHost Managed Consistency is the initial name for Multi-Session Consistency (MSC). This indicates that this SRDF/A group is managed by MSC.

• SRDFAUX1_MS_WINDOW_OPEN B'00001000' SRDF/A WINDOW OPEN The SRDF/A ‘window’, used to form consistency in SRDF/A MSC environments, was open at the time of the query. (This is available only from the R1 side.)

• SRDFAUX1_ARMED_TO_FREEZE B'01000000' THIS SESSION IS ARMED TO FREEZE This applies to SRDF/Star environments only. This setting indicates that, if a write I/O cannot be written to the R2 on the SRDF/S leg of a concurrent R1, the THIS SESSION IS FROZEN flag below will be set before writing the I/O to the R2 on the SRDF/A leg. The flag indicates that this behavior, called armed to freeze, is enabled for this SRDF/A group. (This is available only from the R1 side.)

• SRDFAUX1_FROZEN B'10000000' THIS SESSION IS FROZENThis indicates that a write I//O could not be successfully propagated to the R2 on the SRDF/S leg of a concurrent R1, resulting in a ConGroup trip. SRDF/Star host software detects this condition and takes appropriate action. (This is available only from the R1 side.)

SRDFAUX1_MISC_FLAG4 Flag Byte 4:

• SRDFAUX1_REMOTE_IS_CONSISTENT B'00000001' RMT IS CONSISTENT Indicates the R2 side data is dependent write consistent. (This is available only from the R1 side.)

• SRDFAUX1_REMOTE_IS_INCONSISTENT B'00000010' RMT IS INCONSISTENTIndicates the R2 side data is not dependent write consistent. (This is available only from the R1 side.)

• SRDFAUX1_R1_GROUP B'00000100' THIS IS R1 GROUPThis data was collected from the R1 side.

• SRDFAUX1_R2_GROUP B'00001000' THIS IS R2 GROUPThis data was collected from the R2 side.

• SRDFAUX1_SESSION_IS_ACTIVE B'00010000' SRDFA ACTIVESRDF/A is in an active state.

• SRDFAUX1_R2_RESTORE_FINISHED B'00100000' R2 RESTORE FINISHEDThe R2 side switch from the RECEIVE cycle to the APPLY cycle has completed. (This is available only from the R2 side.)

• SRDFAUX1_R2_PURE_READY_STATE B'01000000' PURE READY STATE ONThe RDY/NRDY state of the R1 devices with regard to the SRDF link will be retained by the Enginuity microcode. Used by open systems host software only. (This is available only from the R1 side.)


Field Description



• SRDFAUX1_R2_SUSPENDED_STATE B'10000000' SRDFA SUSPENDED STATEThe cycle switch process on the R2 side has been suspended. This is done as part of remote consistent split processing. (This is available only from the R2 side.)

SRDFAUX1_ACTIVE_CYCLE_SIZE When issued to the R1 (flag byte 4= B'…..1..'): capture cycle size in number of slots.When issued to the R2 (flag byte 4= B'….1…'): apply cycle size in number of slots.

SRDFAUX1_INACTIVE_CYCLE_SIZE When issued to the R1 (flag byte 4= B'…..1..'): transmit cycle size in number of slots.When issued to the R2 (flag byte 4= B'….1…'): receive cycle size in number of slots.

SRDFAUX1_OLD_TIME_SINCE_LAST_CYCLE Number of seconds since last cycle switch for Enginuity 5670.

SRDFAUX1_TIME_DURATION_LAST_CYCLE Time in seconds from the moment the last capture cycle began until it became the transmit cycle.

SRDFAUX1_CURRENT_CYCLE_NUMBER When issued to the R1, the cycle number of the capture cycle.When issued to the R2, the cycle number of the receive cycle.

SRDFAUX1_MAX_THROTTLE_TIME Amount of time in seconds Enginuity will throttle host I/O before dropping due to resource constraints. Note that if this is x’FFFF’ the host will be throttled indefinitely.

SRDFAUX1_MINIMAL_CYCLE_LENGTH The Enginuity target cycle time for this SRDF/A group. This does not apply to active MSC environments.

SRDFAUX1_MAX_CACHE_USAGE The percentage of the system write pending limit at which SRDF/A will drop.

SRDFAUX1_SYNC_MODE Current state of an active SRDF/A mode change request. See “SRDFAUX1_CON_DEACT_STATE” below. This does not apply to MSC environments.

SRDFAUX1_RDFGRP_MASK This field specifies SRDF groups in SRDF/A operations for Enginuity level 5x70 and 5x71. This is a mask of 8 bytes where x’00000000 00000001’ is SRDF group 0 and x’80000000 00000000’ is SRDF group 63. For Enginuity level 5x72 and higher, “SRDFAUX1_SF1_RDFGRP” is used.

SRDFAUX1_SF1_RDFGRP For Enginuity level 5x72 and higher, this field contains the SRDF group number of the SRDF/A group. For Enginuity levels 5x70 and 5x71, the original field “SRDFAUX1_RDFGRP_MASK” is used.

SRDFAUX1_LAST_CYCLE_SIZE Size of last capture cycle in number of slots.

SRDFAUX1_MS_TURNON_TAG Time and date the last time MSC mode was activated in format MMDDYYYY HHMMSSHT.

SRDFAUX1_MS_TURNOFF_TAG Time and date the last time MSC mode was de-activated in format MMDDYYYY HHMMSSHT.

SRDFAUX1_TIME_SINCE_LAST_CYCLE Number of seconds since the last cycle switch

SRDFAUX1_CONSISTENCY_EXEMPT_CNT Number of volumes in SRDF/A ‘consistency exempt’ status. (This is only available if the R2 side is consistent.)

SRDFAUX1_AVERAGE_CYCLE_TIME Average cycle time in seconds over the last 16 cycles.

SRDFAUX1_AVERAGE_CYCLE_SIZE Average cycle size in slots over the last 16 cycles.


Field Description

SRDF/A and WPA Monitor SMF records 455


SRDFAUX1_TOTAL_HA_WRITES Total number of tracks written by the host adapters on the R1 side to this SRDF/A group. This is a counter that wraps. (This is available only from the R1 side.)

SRDFAUX1_TOTAL_HA_REPEAT_WRITES Total number of times slots were rewritten within the same capture cycle. (This is available only from the R1 side.)

SRDFAUX1_TOTAL_HA_DUPLICATE_SLOT Number of times slots in the transmit cycle were re-written and had to be duplicated to service the incoming write. This is a counter that wraps. (This is available only from the R1 side.)

SRDFAUX1_TOTAL_DA_RESTORE Number of slots marked write pending by the DAs. (This is available only from the R2 side.)

SRDFAUX1_TOTAL_DA_MERGE Number of slots that had to be ‘merged’ by the DA. A merge operation is performed when a slot being marked write pending by the SDFDF/A restore process is already locally write pending. (This is available only from the R2 side).

SRDFAUX1_LAST_RESTORE_DURATION Duration in seconds of the last cycle switch process on the R2 side. Also known as the ‘restore’ process.

SRDFAUX1_AVG_RESTORE_TIME Duration in seconds on average over the last 16 restores on the R2 side. (This is available only from the R2 side.)

SRDFAUX1_SUSPEND_RESUME_TOKEN Value of the token created when the R2 side cycle switch was suspended as part of a consistent split operation. This token is used by host software for the resume operation. (This is available only from the R2 side.)

SRDFAUX1_CON_DEACT_STATE Value indicating the state of an SRDF/A mode switch to SRDF/S. 0=NO STATE, 1=DEACT STARTED, 2=DEACT GOOD, 3=DEACT ALMOST DONE. This is used by host software and does not apply to MSC environments.

SRDFAUX1_LAST_CON_DEACT_STATUS Value indicating the status of a consistent deactivation request. 0=NOT IN PROGRESS, 1=IN PROGRESS, 2=SUCCESSFUL, 3=FAILED

SRDFAUX1_DROP_PRIORITY Drop priority in the Enginuity associated with this SRDF/A group.

SRDFAUX1_HIGH_WATER_MARK The maximum number of write pending slots this SRDF/A group has seen since the last power cycle.

SRDFAUX1_STAR_MODE Value indicating the SRDF/Star mode for this SRDF/A group. 0=NOT STAR, 1=STAR, 2=STAR RECOVERY

SRDFAUX1_CONS_DEACT_CYCLE_NUMBER The cycle number at which an SRDF/A group undergoing a consistent deactivation will move to consistent deact state 2. This is only valid when in consistent deact state 1. This is used by host software and does not apply to MSC environments.


Field Description


CHAPTER 10Using the QoS UtilityInvisible Body Tag

This chapter describes the Quality of Service (QoS) Utility for z/OS and how to manage dynamic cache partitions in your Symmetrix system.

◆ Overview............................................................................................................... 458◆ Symmetrix Priority Control ..................................................................................... 459◆ Dynamic Cache Partitioning................................................................................... 459◆ QoS control statements......................................................................................... 460◆ QoS copy priority statements ................................................................................ 461◆ SPC control statements ......................................................................................... 472◆ DCP control statements......................................................................................... 477◆ Mixed RDF mode commands ................................................................................. 489◆ Miscellaneous control statements......................................................................... 495◆ QoS examples....................................................................................................... 496◆ QoS error and event messages.............................................................................. 503

Using the QoS Utility 457

Using the QoS Utility

OverviewThe EMC Quality of Service (QoS) Utility for z/OS allows you to customize certain priorities of the Symmetrix system on a logical-volume basis. QoS allows you more flexibility in managing your Symmetrix system’s performance. By increasing the response time for specific copy operations on selected devices or groups, you can increase the overall performance of the other Symmetrix devices.

The QoS Utility allows you to define and set various values on a logical volume level. These values can affect performance and resource use within the Symmetrix system. For example, QoS enables you to differentiate the amount of Symmetrix global memory committed to various end-user applications, and thus improve performance.

Originally, Symmetrix global memory was a resource that was allocated as a single memory allocation of fixed size. Symmetrix global memory could not be subdivided. However, the Enginuity operating environment evolved and allowed Symmetrix global memory to be subdivided into least recently used segments (LRUs) of equal size. This subdivision reduces lock contention on global memory accesses and has the potential of improving system performance for the systems that support the feature.

Note: Enginuity levels 5x71 and higher do not support control of LRUs.

Three additional features, Symmetrix Priority Control (SPC) and Dynamic Cache Partitioning (DCP) are available with Enginuity levels 5772 to 5875, and Mixed SRDF mode (MRDF) is available for Enginuity level 5876 and higher. Symmetrix Priority Control provides a mechanism to determine which device’s I/O should receive priority service when the Symmetrix system is very busy. Dynamic Cache Partitioning provides the ability to define and manage up to eight different cache partitions (16 DCPs for Enginuity level 5876 and higher) and associate devices as members of a particular partition. MRDF allows you to balance the workload on primary devices (R1s), using MRDF commands with the capability of setting and displaying the values of the mixed RDF modes on a director. The Symmetrix director can now handle a mix of synchronous and asynchronous I/O workloads requiring service at the same time.

As the Enginuity operating environment has evolved, EMC has offered several mechanisms to control Quality of Service. It is important to understand which controls are available for your use with the Enginuity level in your system. Table 17 indicates feature availability for various Enginuity levels.

Table 17 QoS feature availability

Enginuity level LRU SPC DCP MRDF

5568 Yes No No No

5669 Yes No No No

5670 Yes No No No

5x71 No No No No

5x72 - 5x75 No Yes (optional) Yes (optional) No

5x76 and higher No Yes (optional) Yes (optional) Yes (optional)



IMPORTANT

Take care when setting various QoS options because they can have an adverse effect on performance and resource use.

You can run QoS only against the following controller types: 3880, 3990, 2105, and 2107.

Make sure you add EMCQOS to the AUTHPGM and AUTHTSF lists in your SYS1.PARMLIB(IKJTSOxx) member. The Mainframe Enablers Installation and Customization Guide describes this process. “QoS control statements” on page 460 describes the statements that control this feature.

Security interface

The EMC Quality of Service Utility for z/OS uses SAF calls to validate access to resources. This feature is turned on by default. To turn this feature off, refer to the EMCSAFI Security Interface chapter in the EMC Mainframe Enablers Installation and Customization Guide. The source code for the SAF interface routine is provided in the SCF SAMPLIB so that you can tailor it to your specific needs.

Symmetrix Priority ControlSymmetrix Priority Control (SPC) is a licensed feature available as an option in Enginuity 5772 and higher. SPC provides a mechanism to differentiate how I/O requests for included devices are handled in busy or heavily shared Symmetrix systems. Setting device SPC values determines which device’s I/O should receive priority service when the Symmetrix is very busy. In unstressed environments, there may be no noticeable impact.

SPC is enabled at the director level in the Symmetrix system. Any directors not referenced in the SETDIR command are reset and do not invoke device priorities. Devices are set with a value between 1 (highest priority) and 16 (lowest priority). Lower values receive priority handling in stressed conditions.

Note: Only standard or BCV devices are supported in this release.

“SPC control statements” on page 472 describes the statements that control this feature.

Dynamic Cache PartitioningDynamic Cache Partitioning (DCP) is a licensed feature available as an option in Enginuity 5772 and higher. DCP provides the ability to define up to eight different cache partitions (16 DCPs for Enginuity level 5876 and higher) and associate devices as members of a particular partition. The partitions are not static and allow you to specify minimum and maximum sizes.

To dynamically manage the needs of each partition, you can specify periods at which partitions can donate to one another. This allows busy partitions to receive cache donations from less busy partitions, up to their specified maximum. The minimum values prevent a partition from being starved for cache resources. As with current cache thresholds, write pending limits and destage priority can be set at the partition level.

Symmetrix Priority Control 459


Note: For SRDF/A, all the devices in the SRDF group must be in the same cache partition. If not, the request to activate SRDF/A will be rejected.

Any attempt to include a new device pair in an SRDF group on which an active SRDF/A session exists will be rejected if either device of the pair is in a different cache partition group from that of the devices already in the SRDF/A group.

“DCP control statements” on page 477 describes the statements that control this feature.

QoS control statementsWhen QoS initializes, it requires that you specify the following DD statements in the JCL.

The following DD statements are optional:

Note: You can specify control statements for any valid EMC device. The device online/offline status does not prevent the control options from taking effect. If the device is in an unpredictable state, you may receive an error message. When you specify a range of devices, the range you choose must represent contiguous Symmetrix devices and must be within the same Symmetrix system.

Conventions

The following conventions are used to illustrate the control statement format:

◆ Control statements in a fixed-space font are configuration keywords or fixed parameters. Unless otherwise noted, you must enter all statements in UPPERCASE.

◆ Statements in italicized text are user-supplied keywords.

◆ Statements enclosed in [square brackets] are optional and do not have to be specified.

QOSINPUT DD Control statements are read from here. QoS opens the DD with the following attributes:

DSORG=PS,LRECL=80

SYSPRINT DD QoS writes command parsing information and error messages into this DD. QoS opens the DD with the following attributes:

DSORG=PS,RECFM=F,LRECL=133

QOSPRINT DD QoS writes the report output into this DD. QoS opens the DD with the following attributes:

DSORG=PS,RECFM=F,LRECL=133

QoS command output will go to this DD if specified; otherwise, command output will go to the SYSPRINT DD.



◆ Statements separated by a logical OR character or vertical bar (|) are members of a list of parameters. The keyword must specify one of the values in the list or, if allowed, you must provide a parameter.

◆ You must enter all control statements and parameters completely. Unless otherwise indicated, there are no abbreviations.

◆ You can comment out control statements using an asterisk (*) in column 1 and these statements can span multiple lines.

QoS copy priority statementsThis section describes the QoS copy priority statements.

Note: With Enginuity level 5875 and higher, the copy priority settings are supported for VLUNs that controls the priority for copies between mirrors of a single device. Also with Enginuity level 5875 and higher, BCV copy priorities have been discontinued because BCV copies are now accomplished with CLONE operations. To set the copy priority values for BCV devices, you must now used the SNPP copy priority parameter. You can set the copy priority for each device. Supported copy types are RDFP(#), SERP(#), SNPP(#), and VLUN(#).

DISPCPYP/DISPDEV

DescriptionUse the DISPCPYP/DISPDEV command pair to retrieve the current copy priority settings for a logical volume. You can specify up to 32 DISPCPYP statements.

Note: The DISPCPYP statement requires Enginuity level 5875 or higher.

“DISPCPYP example” on page 500 provides an example report displaying copy priority settings for a logical volume.

Note: With ResourcePak Base V7.4 and higher, the DISPCPYP command allows you to specify Symmetrix devices by SRDF group or ALL. The DISPDEV command allows you to filter the results to include or exclude devices based on group priorities. In addition, you can now identify the Symmetrix system for the selected devices by specifying its serial number.

This is a command pair. The following usage rules apply:

◆ You must execute DISPCPYP and DISPDEV together so that DISPCPYP indicates the devices to act upon, and DISPDEV indicates the gatekeeper on which to run. The commands must be coded in this order, or you will receive an error.

◆ When coding multiple DISPCPYP statements, you cannot mix Symmetrix device numbers and CUUs. If these values are mixed, you will receive an error. Also, the device numbers or CUUs must be in sequential order for them all to be processed.

QoS copy priority statements 461


Syntax DISPCPYP { CUU(cuu[-cuu]) | symdev#[-symdev#] | RA(ragrp) | ALL }DISPDEV { LCL(cuu) | RMT(cuu,hoplist) | SER(symser#) } [,[NOT(] [SNPP(#)] [,RDFP(#)] [,SERP(#)] [,VLUN(#)] [)]]

Where:

ALLReturns results for all Symmetrix devices.

CUU Specifies which unit or range of units will be affected. Specify either a single Control Unit Address (CUA) or a range of CUAs. The first and last devices in the range of devices are checked to validate that they are in the same Symmetrix system.

Note: Any range of units you specify must be contiguous CUUs. You receive an error message if a CUU within the range does not exist.

When you specify RMT or LCL, this parameter represents your gatekeeper device. Gatekeeper devices can be online or offline, as long as a valid path is available to the Symmetrix system that you are referencing.

cuusSpecifies any device on a controller for a local (LCL) or remote operation (RMT). For a RMT operation, you must specify the SRDF group (ragrp).

hoplistThe multi-hop path for the remote device.

LCLSpecifies that the actions affect the Symmetrix device numbers of the local configuration.

[,[NOT(] [SNPP(#)] [,RDFP(#)] [,SERP(#)] [,VLUN(#)] [)]]

These optional parameters allow you to filter the results to include or exclude (using the NOT operator) one or several of the following copy types:

• SNPP — Snap copies• RDFP — Remote Data Facility copies• SERP — Service copies• VLUN — Virtual logic unit volume copies

RA(ragrp)Specifies the SRDF group containing the devices on which you want to perform the operation. This must be a two-digit value from 00 to F9 representing the SRDF group.

RMT Specifies that the action affects a remote device in an SRDF configuration.

SER(symser)Specifies a Symmetrix 12-digit serial number.

symmdev#(-symmdev#)Specifies either a single Symmetrix device or a range of devices.



SETCPYP/SETDEVCP

DescriptionUse the SETCPYP/SETDEVCP commands to set the copy priority settings for a logical volume. You can specify up to 32 SETCPYP statements.

Note: The SETCPYP statement requires Enginuity level 5875 or higher.

This is a command pair. The following usage rules apply:

◆ You must execute SETCPYP and SETDEVCP together so that SETCPYP indicates the devices to act upon, and SETDEVCP indicates the gatekeeper on which to run. The commands must be coded in this order, or you will receive an error.

◆ When coding multiple SETCPYP statements, you cannot mix Symmetrix device numbers and CUUs. If these values are mixed, you will receive an error. Also, the device numbers or CUUs must be in sequential order for them all to be processed.

Note: With ResourcePak Base V7.4 and higher, the SETCPYP command allows you to specify Symmetrix devices by SRDF group. The SETDEVCP command allows you to identify the Symmetrix system for the selected devices by specifying its serial number.

SyntaxSETCPYP { CUU(cuu[-cuu]) | symdev#[-symdev#] | RA(ragrp)}SETDEVCP { LCL(cuu) | RMT(cuus,hoplist) | SER(symser#)} [,RDFP(nn|URGent)] [,SERP(nn|URGent)] [,SNPP(nn|URGent)] [,VLUN(nn|URGent)]|[RESET]

IMPORTANT

Use the priority value of URGent with caution. Urgent devices will be selected more frequently. Defining a device as urgent can potentially adversely affect performance. Be sure to change the QOS value of URGent back to a normal QOS value after the copy session is finished.

Where:

CUU

Specifies which unit or range of units will be affected. Specify either a single Control Unit Address (CUA) or a range of CUAs. The first and last devices in the range of devices are checked to validate that they are in the same Symmetrix system.





cuus

Specifies any device on a controller for a local (LCL) or remote operation (RMT). For a RMT operation, you must specify the SRDF group (ragrp).

hoplist

The multi-hop path for the remote device.

LCL

Indicates that the actions affect the Symmetrix device numbers of the local configuration.

RA(ragrp)

Specifies the SRDF group containing the devices on which you want to perform the operation. This must be a two-digit value from 00 to F9 representing the SRDF group.

RDFP

Determines the priority for Remote Data Facility copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are 0 through 16 or URGent.

RESET

Resets the current settings for a logical volume. All priorities are set to the default value of 0.

RMT

Indicates that the action affects a remote device in an SRDF configuration.

SER(symser)

Specifies a Symmetrix 12-digit serial number.

SERP

Determines the priority for Service copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are 0 through 16 or URGent.

SNPP

Determines the priority for Snap copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are 0 through 16 or URGent.

symmdev#(-symmdev#)

Specifies either a single Symmetrix device or a range of devices.

VLUN

Determines the priority for virtual logical unit volume copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are 0 through 16 or URGent.



QOSGET

DescriptionUse QOSGET to retrieve the current settings for a logical volume.

Note: With ResourcePak Base V7.4 and higher, you can now specify Symmetrix devices by SRDF group or ALL, and you can identify the Symmetrix system for the selected devices by specifying its serial number. You can also filter the results to include or exclude devices based on group priorities.

Syntax QOSGET { CUU=cuu {-cuu | ,RA(ragrp) | ,ALL} | RMT(cuu,{ symdev#[-symdev#] | RA(ragrp) | ALL} ,hoplist) | LCL(cuu,{ symdev#[-symdev#] | RA(ragrp) | ALL}) | SER(symser#,{symdev#[-symdev# | RA(ragrp) | ALL})

} [,[NOT(] [SNPP(nn)] [,RDFP(nn)] [,SERP(nn)] [,BCVP(#)][)]]

Where:

ALL

Returns results for all Symmetrix devices.

CUU




cuus

Specifies any device on a controller for a local (LCL) or remote operation (RMT). For a RMT operation, you must specify the SRDF group (ragrp).

hoplist

The multi-hop path for the remote device. For example, use the following to specify three hops from the source (group 0) through SRDF group 1 on the Symmetrix at Site B and then SRDF group 2 on the Symmetrix at Site C:

0.1.2

LCL

Specifies that the actions affect the Symmetrix device numbers of the local configuration.



[,[NOT(] [SNPP(#)] [,RDFP(#)] [,SERP(#)] [,VLUN(#)] [)]]

These optional parameters allow you to filter the results to include or exclude (using the NOT operator) one or several of the following copy types:

• SNPP — Snap copies• RDFP — Remote Data Facility copies• SERP — Service copies• VLUN — Virtual logic unit volume copies

RA(ragrp)


RDFP

Determines the priority for Remote Data Facility copies. For nn, specify the priority, where 0 represents the highest priority. Valid values are 0 through 16 or URGent.

RMT

Specifies that the action affects a remote device in an SRDF configuration.

SER(symser)


SERP

Determines the priority for Service copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are 0 through 16 or URGent.

SNPP

Determines the priority for Snap copies. For nn, specify the priority, where 0 represents the highest priority. Valid values are 0 through 16 or URGent.

symmdev#(-symmdev#)


VLUN

Determines the priority for virtual logical unit volume copies. For nn, specify the priority, where 0 represents the highest priority. Valid values are 0 through 16 or URGent.

Restrictions◆ For Enginuity versions issued before 5x69, you receive an error message if you specify

more than 2000 devices.

◆ For Enginuity level 5x69 or higher, there is no limit to the number of devices you can specify. With this Enginuity level 5875 or higher, you can also use the DISPCPYP statement to display the copy priority settings.

Example The following QOSGET statement returns the current settings for a single device and a range of devices:

QOSGET CUU=B300QOSGET CUU=B310-B320



QOSSET

DescriptionUse QOSSET to set Logical Volume, Priority options, and LRU options. Input to this statement is one or both of the following:

◆ One or more of the priorities

◆ The LRU sub statement

Note: The QOSSET statement does not support VLUN.

These values take effect immediately and can have adverse effects on the performance of the Symmetrix system. After you set these values, QoS retains them across an IML of the Symmetrix system. Each value that is not specified is set to the default value. For example, if you want to change the BCVP value, but keep any values previously specified, you must respecify all previously defined values.

Note: With ResourcePak Base V7.4 and higher, QOSSET allows you to specify Symmetrix devices by SRDF group and to identify the Symmetrix system for the selected devices by specifying its serial number.

SyntaxQOSSET { CUU=cuu {-cuu | ,RA(ragrp)} | RMT(cuu,{ symdev#[-symdev#] | RA(ragrp)} ,hoplist) | LCL(cuu,{ symdev#[-symdev#] | RA(ragrp)}) | SER(symser#,{ symdev#[-symdev#] | RA(ragrp)}) } [,RDFP=nn] [,BCVP=nn] [,SERP=nn] [,SNPP=nn] [,LRU=(LRU#,…,LRU#)] [,LRUNAME=(group_name)]


Where:

CUU

Determines which unit or range of units will be affected. Specify either a single Control Unit Address (CUA) or a range of CUAs. The first and last device in the range are checked to make sure that they are in the same Symmetrix system.





cuus

Specifies any device on a controller for a local (LCL) or remote operation (RMT). For an RMT operation, you must specify the SRDF group (ragrp).

hoplist


0.1.2

LCL


RA(ragrp)


RMT

Specifies that the action affects remote devices in an SRDF configuration.

SER(symser)


symmdev#(-symmdev#)


RDFP

Determines the priority for Remote Data Facility copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are as follows:

BCVP

Determines the priority for business continuance volume copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are as follows:

SERP

Determines the copy pace during mirror operations. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are as follows:

Enginuity level nn values

5x71 and lower 0 through 10

5772 and higher 0 through 16



5772 and 5773 0 through 16

5774 and higher No effect






SNPP

Determines the priority for SNAP copies. For nn, specify the priority, where 0 represents the highest priority. Valid values for nn are as follows:

LRU

The LRU substatement associates the devices specified by CUU with a single LRU or a set of LRUs. For LRU#, specify a list of values from zero through 15 depending on which LRU(s) the logical volume will participate in.


LRUNAME

Associates the devices specified with an LRU group. Specify one of the groups provided by your EMC customer engineer when your Symmetrix system was configured.


Restrictions◆ QOSSET automatically sets the RAID 10 member devices if the head device is set.

◆ For Enginuity level 5875 or higher, QOSSET is tolerated, but does not allow use of the VLUN and URGENT options. With Enginuity level 5875 or higher, you can use the SETCPYP statement to set the copy priority settings while using the new options.

ExampleThe following QOSSET statements will set various settings for a single device and a range of devices:

◆ The following statement sets the priority levels for a single device:

QOSSET CUU=B300,RDFP=1,BCVP=3,SERP=4

◆ The following statement assigns a single device to LRU 0-8:

QOSSET CUU=B300,LRU=(0,1,2,3,4,5,6,7,8)

◆ The following statement sets the priority levels and assigns a range of devices to LRU 0-15:

QOSSET CUU=B300-B301,RDFP=1,BCVP=3,SERP=4,LRU=(0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)






QOSRESET

DescriptionUse QOSRESET to reset the current settings for a logical volume.

All priorities are set to the default value of 0. The LRU assignment for the logical volume is also returned to its default value, which assigns the logical volume to all available LRUs.

Note: With ResourcePak Base V7.4 and higher, QOSRESET allows you to specify Symmetrix devices by SRDF group and to identify the Symmetrix system for the selected devices by specifying its serial number.

Syntax QOSRESET { CUU=cuu {-cuu | ,RA(ragrp)} | RMT(cuu,{ symdev#[-symdev#] | RA(ragrp)} ,hoplist) | LCL(cuu,{ symdev#[-symdev#] | RA(ragrp)}) | SER(symser#,{ symdev#[-symdev#] | RA(ragrp)}) }

Where:

CUU

Specifies which unit or range of units will be affected. Specify either a single Control Unit Address (CUA) or a range of CUAs. The first and last devices in the range of devices are checked to make sure that they are in the same Symmetrix system. Individual address ranges of CUUs are bound by the SSID definition.



cuus


hoplist


0.1.2

LCL


RMT




RA(ragrp)

Specifies the SRDF group through which you want to perform the remote operation. This must be a one or two-digit value representing the SRDF group.

SER(symser)


symmdev#(-symmdev#)


RestrictionsThe QOSRESET command automatically sets the RAID 10 member devices if the head device is set.

For Enginuity level 5875, this statement is tolerated.

ExampleThe following QOSRESET statement returns all settings for a single device and a range of devices to their default values:

QOSRESET CUU=B300QOSRESET CUU=B310-B320



SPC control statementsSymmetrix Priority Control provides a mechanism to differentiate how I/O requests for included devices are handled in Symmetrix systems. SPC statements consist of a prepare and an activate statement for the control statements. For example, enabling SPC on directors 1,3,4,5 can be specified several ways:

Prepare statements

◆ SETDIR 1

◆ SETDIR 3-5

Activate statement

◆ SETSPC LCL(cuus) where cuus is the gatekeeper device

DISPSPC

DescriptionDisplays the Symmetrix Priority Control settings for the specified gatekeeper.

Syntax DISPSPC LCL(cuus) | RMT (cuus,ragrp)

cuus

Specifies any device on a controller for a local or remote operation (RMT). For a RMT operation, you must specify the SRDF group (ragrp).

LCL

Specifies the gatekeeper device of the local configuration.

ragrp


For multi-hop remote configurations, ragrp can be a single SRDF group or a list of up to four hops delineated by periods. For example, use the following to specify three hops from the source (group 0) through SRDF group 1 on the Symmetrix at Site B and then SRDF group 2 on the Symmetrix at Site C:

0.1.2

RMT




DISPDEVP / DISPDEV

DescriptionDisplays current device priority. You can specify up to 32 DISPDEVP statements.

Note: This is a command pair. They must be executed together such that DISPDEVP indicates the devices to act upon, and DISPDEV indicates the gatekeeper on which to run. “SPC functionality” on page 496 provides an example showing command pair usage.

SyntaxDISPDEVP CUU(cuus [-cuus]) | sdev [-sdev]DISPDEV LCL(cuus) | RMT (cuus,ragrp)

Where:

CUU




cuus


LCL


ragrp



0.1.2

RMT


sdev


SPC control statements 473


SETDEVP / SETDEV

DescriptionSets device priorities. Assigns an SPC value to a device or a range of devices. The device must be a valid standard or BCV device. Values are 1 to 16. When SPC is enabled for a director, all device I/O through that director defaults to 1. You can specify up to 32 SETDEVP statements.

Note: This is a command pair. They must be executed together so that SETDEVP indicates the devices to act upon, and SETDEV indicates the gatekeeper on which to run. “SPC functionality” on page 496 provides an example showing command pair usage.

SyntaxSETDEVP CUU(cuus[-cuus]) | sdev [-sdev],spcvalue | ,META | SCKDSETDEV LCL(cuus) | RMT(cuus,ragrp)

Where:

CUU




cuus


LCL


META

Use this option to set the priority on the META head device. You cannot specify a range with this option.

ragrp



0.1.2



RMT


SCKD

Use this option to set the priority on striped CKD head device. You cannot specify a range with this option.

sdev


spcvalue

Specifies the SPC value between 1 and 16.

RestrictionsYou must have the proper security authorization to use this command.

SETDIR / SETSPC

DescriptionEnables or disables Symmetrix Priority Control (SPC) on the specified host attached directors. The inclusion or exclusion of a director determines whether SPC is enabled or disabled. If a director does not exist, or is offline, it will be enabled when it becomes available.

Note: SETDIR and SETSPC are a command pair. SETDIR indicates the devices to act upon, and SETSPC indicates the gatekeeper on which to run. However, SETSPC can be used alone to initialize or reset SPC. “SPC functionality” on page 496 provides an example showing command pair usage.

SyntaxSETDIR #,#-# | RESETSETSPC LCL(cuus) | RMT(cuus, ragrp)

or

SETSPC LCL(cuus) | RMT(cuus, ragrp),INIT|RESET

Note: When INIT or RESET is used with the SETSPC command, the SETDIR command cannot be used.

Where:

# #-#

Indicates the directors that will be enabled. Unspecified directors are disabled. Valid values are 1 to 128. A maximum of 4 directors and/or ranges can be specified per SETDIR statement.

When SETDIR is used to set the directors, multiple SETDIR statements can be specified.

SPC control statements 475


cuus

Specifies any device on a controller for a local or remote operation (RMT). For RMT, you must specify the SRDF group (ragrp).

INIT|RESET

INIT - Initializes Symmetrix Priority Control and returns it to a disabled state with all values initialized to the system default.

RESET - Resets the Global Statistic Update Time to the default value of 0 seconds, which will disable automatic updates. All directors will be Symmetrix Priority Control disabled.

LCL


ragrp



0.1.2

RESET

Disables SPC on all the directors.

RMT





DCP control statementsThis section describes the Dynamic Cache Partition (DCP) statements.

DISPCCFG

DescriptionDisplays the cache partition configuration for the specified gatekeeper.

Syntax DISPCCFG LCL(cuus) | RMT (cuus,ragrp), ID(#) | ALL

Where:

ALL

Returns data for all cache group partitions.

cuus


ID

The partition identifier. The value can range from 0 to 7 (0 to 15 for Enginuity level 5876 or higher).

LCL


ragrp



0.1.2

RMT


DCP control statements 477


DISPCDEV or DISPCDVG/ DISPCDV

DescriptionDisplays the cache partition group in which the device resides. You can specify up to 32 DISPCDEV statements.

Note: This is a command pair. They must be executed together such that DISPCDEV or DISPCVG indicates the devices to act upon, and DISPCDV indicates the gatekeeper on which to run. “DCP functionality” on page 498 provides an example showing command pair usage.

SyntaxDISPCDEV CUU(cuus [-cuus]) | sdev [-sdev]

or

DISPCDVG RDFG(#)DISPCDV LCL(cuus) | RMT (cuus,ragrp)

Where:

CUU


Any range of units you specify must be continguous CUUs. If a CUU within a range does not exist, an error message is displayed. When you specify RMT or LCL, this parameter represents your gatekeeper device. Gatekeeper devices can be online or offline, if a valid path is available to the Symmetrix system you are referencing.

cuus


LCL


ragrp



0.1.2



RDFG(#)

# specifies the SRDF group.

Note: This statement cannot be specified with DISPCDEV. Only 1 SRDF group can be coded.

RMT


sdev


DISPCGRP

DescriptionDisplays the devices in the specified group ID.

If the partition is not specified, the default ID(0) is used.

SyntaxDISPCGRP LCL(cuus) | RMT (cuus,ragrp),ID(#)

Where:

cuus


ID(#)

The partition identifier. The value can range from 0 to 7 (0 to 15 for Enginuity level 5876 or higher). The default value is 0.

LCL


ragrp



0.1.2

RMT




DISPCGEN

DescriptionDisplays general cache partition information.

SyntaxDISPCGEN LCL(cuus) | RMT(cuus,ragrp)

Where:

cuus


LCL


ragrp



0.1.2

RMT


DISPCUSE

DescriptionDisplays dynamic cache partition utilization information.

SyntaxDISPCUSE LCL(cuus) | RMT (cuus,ragrp), ID(#) | ALL

Where:

ALL

Returns data for all cache group partitions.

cuus


ID




LCL


ragrp



0.1.2

RMT


SETCACHE

DescriptionInitializes, disables, or enables Dynamic Cache Partitioning (DCP).

SyntaxSETCACHE LCL(cuus) | RMT (cuus,ragrp), INIT | ENABLE |ENABLE(ANALYSIS) | DISABLE

Where:

cuus


DISABLE

Disables cache partitioning.

ENABLE

Enables cache partitioning.

ENABLE(ANALYSIS)

Analysis mode allows for the allocation of partitions and movement of devices to partitions. DCP is not fully enabled in this mode. Various counters and usage values are maintained without the full effect of DCP being enabled. “DISPCUSE” on page 480 provides additional information. Analysis mode can be enabled only if all cache partitions are completely flexible, that is:

MINCACHE = 0 MAXCACHE = 100 AGE= 0

Partition 0 must be modified to have AGE(0). Be sure to specify all other parameters exactly as they are currently defined since only AGE can be modified.

After enabling analysis mode, DCP must be enabled before any changes take effect.



Note: When you complete your analysis mode of operation, disable cache partitioning and modify or delete and recalculate your cache partitions to reflect the values calculated as a result of the analysis. Do not disable analysis mode while cache partitioning is enabled. This will allow cache partitioning to operate as normal, but with partitions set for analysis mode. Always disable cache partitioning and redefine your partitions after using analysis mode.

INIT

Initializes cache partitioning.

Note: Use caution when using this command. If you execute an INIT while DCP is active, it will cause a disable to be executed automatically. All devices will be returned to the default partition and any defined partitions will be deleted.

LCL


ragrp



0.1.2

RMT



SETCPADD

DescriptionCreates a Dynamic Cache Partition (DCP).

SyntaxSETCPADD LCL(cuus) | RMT(cuus,ragrp),ID(#),TCACHE(target%),MINCACHE(min%),MAXCACHE(max%),AGE(seconds),WP(wp%),CPNAME(partitionname),XRCP

Where:

AGE

The minimum number of seconds before cache can be donated to another partition. The maximum allowable value is 268435455.



CPNAME

The 31-character alphanumeric name. No embedded blanks or special characters except underscore "_" are allowed. The name cannot begin or end with an underscore.

cuus


ID


LCL


MAXCACHE

The maximum cache allocation allowed for the partition as a percentage of total cache. The value cannot be less than the target or minimum cache allocation.

MINCACHE

The minimum cache allocation for the partition as a percentage of total cache. The value cannot be greater than the target cache allocation.

ragrp



0.1.2

RMT


TCACHE

The target cache allocation for the partition as a percentage of total cache. The value can be between 10 and 90%.

WP

The write pending limit for the partition. The value can be between 40% and 80%.

XRCP

Flags this partition as reserved for XRC. No devices can be added to this partition. If you define an XRC partition, you do not need to use SETCPMRP XRCP(ENABLE,#) unless SETCPMRP XRCP(DISABLE) was issued.




SETCPDEL

DescriptionDeletes a Dynamic Cache Partition (DCP). Any devices in this partition will moved to the default partition.

SyntaxSETCPDEL LCL(cuus) | RMT(cuus,ragrp),ID(#)

Where:

cuus


ID


LCL


ragrp



0.1.2

RMT





SETCPMOD

DescriptionModifies a Dynamic Cache Partition (DCP).

SyntaxSETCPMOD LCL(cuus) | RMT(cuus,ragrp),ID(#),TCACHE(target%),MINCACHE(min%),MAXCACHE(max%),AGE(seconds),WP(wp%),CPNAME(partitionname)

Where:

AGE

The minimum number of seconds before cache can be donated to another partition.

CPNAME

The 31-character alphanumeric name. No embedded blanks or special characters except underscore "_" are allowed. The name cannot begin or end with an underscore.

cuus


ID


LCL


MAXCACHE

The maximum cache allocation allowed for the partition as a percentage of total cache. The value cannot be less than the target or minimum cache allocation.

MINCACHE

The minimum cache allocation for the partition as a percentage of total cache. The value cannot be greater than the target cache allocation.

ragrp



0.1.2

RMT




TCACHE

The target cache allocation for the partition as a percentage of total cache. The value can be between 10 and 90%.

WP

The write pending limit for the partition. The value can be between 40% and 80%.


SETCPMRP

DescriptionModify DCP runtime parameters.

SyntaxSETCPMRP LCL(cuus) | RMT(cuus,ragrp),XRCP(ENABLE,# | DISABLE) | ANALYSIS(ENABLE | DISABLE)

Where:

cuus


LCL


ragrp



0.1.2

RMT


ANALYSIS ENABLE

Enables DCP in analysis mode. Analyzes and generates only statistics. ENABLE will return an error if SETCACHE ENABLE(ANALYSIS) was not issued.

ANALYSIS DISABLE

Disables DCP analysis mode.



XRCP ENABLE,#

Enables the specified partition to be used for XRC processing. This command is only valid if SETCPADD was not issued with the XRCP option or after a XRCP(DISABLE) has been issued.

XRCP DISABLE

Prevents DCP from using the defined XRC partition.

SETCPMVD/SETCPMV

DescriptionMoves devices from the group in which they currently reside to the specified group. You can specify up to 32 SETCPMVD statements.

This is a command pair. They must be executed together such that SETCPMVD indicates the devices to act upon, and SETCPMV indicates the gatekeeper on which to run. “DCP functionality” on page 498 provides an example showing command pair usage.

Note: Devices within an SRDF/A group cannot be moved individually. You must use the RDFG option and move the whole group.

SyntaxSETCPMVD CUU(cuus [-cuus]) | sdev[-sdev] | POOL(pool_name)SETCPMV LCL(cuus) | RMT (cuus,ragrp),ID(#)

SETCPMVD RDFG(rdfg)SETCPMV LCL(cuus) | RMT (cuus,ragrp),ID(#),TYPE(RDFG)

SETCPMVD CUU(cuus) | sdevSETCPMV LCL(cuus) | RMT (cuus,ragrp),ID(#),TYPE(META | SCKD)

Where:

CUU




cuus


ID

Indicates the partition identifier. The value can range from 0 to 7 (0 to 15 for Enginuity level 5876 or higher).



LCL


POOL(poolname)

Specifies the pool name to be moved. Every device in the pool will be moved. THIN, SNAP, and DSE pools are supported. The poolname can be up to 12 characters long. The name may include uppercase alphabetic characters, numbers, spaces, underscores (_), and hyphens (-). The first and last characters may not be underscores or hyphens. If the name includes any hyphens or spaces you must enclose the name in apostrophes.

ragrp



0.1.2

RMT


sdev


TYPE

Specifies the type of devices to be moved. If the range of devices you are trying to move contains any of the following types: SRDF/A, META, or SCKD, then you must use the TYPE parameter.

• META

Move all members in a meta definition. You must specify the meta head device.

• RDFG

Move all the devices in the specified SRDF group. SRDF/A devices cannot be moved individually and must be moved as a group. If you specify this option, it must be specified on both the SETCPMVD and SETCPMV statements.

• SCKD

Move striped CKD devices.

Example

SETCPMVD POOL(myPool)SETCPMV LCL(c400),ID(5)




Mixed RDF mode commandsStarting with Enginuity level 5876 and Mainframe Enablers version 7.4, the Symmetrix SRDF director (RA) can now handle a mix of synchronous and asynchronous I/O workloads requiring service at the same time.

Supporting mixed SRDF modes on an RA allows you to make load-sharing between synchronous and asynchronous IOs, and copies on the RA more efficient and fair. The selection policy to enable mixed mode workload sharing is enabled by default on all the Symmetrix directors. “Workload based re-distribution examples” on page 502 provides more information.

The default weights (percentage values) that directors are assigned when they are brought online are:

◆ Synch—70%

◆ Asynch— 20%

◆ Copies —10%

You can set these weights to different percentages.

The feature is supported on both Fiber and GigE SRDF directors, but balances the workload only on the primary devices (R1). The feature is backward compatible and is functional even when connected to a Symmetrix system executing lower Enginuity code levels.

The following commands provide QOS with the capability of setting and displaying the values of the mixed RDF modes on an SRDF director.

Note: To avoid potential discrepancies between setting new modes and displaying previous states, EMC recommends using a WAIT command between any MRDFSET and MRDFDISP commands to allow time to display the actual mixed RDF mode state.

MRDFDISP WEIGHTS

DescriptionQueries and reports the current active selection policy and the CPU weights (percentages) assigned to the workloads on all RAs.

Syntax MRDFDISp Weights{LCL(cuus)|RMT(cuus,hoplist)}[,RADir(##)]

Where:

LCL


cuus

Specifies any device on a controller for a local (LCL) or remote operation (RMT).

RMT


Mixed RDF mode commands 489


hoplist


RADIR(##)

Specifies the SRDF director number in hex in the range of x'01' through x'80'.

ExampleEMCP001I MRDFDISP WEIGHT LCL(3A01) Current selection policy for Symm serial:000195700086 Director # POLICY Sync CPU% A-Sync CPU% Copies CPU% ---------- --------- --------- ---------- ----------- 47 LEGACY 70 20 10 56 LEGACY 20 50 30 57 LEGACY 70 20 10 59 LEGACY 70 20 10 END OF MRDFDISP WEIGHT STATEMENT

MRDFDISP DEFAULTS

DescriptionQueries and reports the default policy and CPU weights (percentages, values) on all SRDF directors.

SyntaxMRDFDISp Defaults {LCL(cuus)|RMT(cuus,hoplist)}

Where:

LCL


cuus

Specifies a device on the local controller.

RMT


hoplist


ExampleEMCP001I MRDFDISP DEFAULTS LCL(3A01) Current Default values for Symm serial:000195700086 POLICY Sync CPU% A-Sync CPU% Copies CPU% ------ --------- ----------- ----------- LEGACY 70 20 10 END OF MRDFDISP WEIGHT STATEMENT



MRDFDISP RDFSTATS

DescriptionReports the statistical information specific to this feature for the SRDF group passed in the parameter of the syscall. If no director is specified, all SRDF directors for the Symmetrix system are returned.

SyntaxMRDFDISp RDFstats {LCL (cuus)|RMT(cuus,hoplist)}[,RADir(##)]

Where:

LCL


cuus


RMT


hoplist


RADir(##)


ExampleEMCP001I MRDFDISP RDFSTATS LCL(3A01) Mixed Mode RDF Stats for Symm Serial:000195700086 RADir SYNC WRITES SIZE(KB) ----- ---------- ---------- 0047 0 0 ASYNC WRITES SIZE(KB) ---------- ---------- 0 0 COPIES WRITES SIZE(KB) ----------- ---------- 0 0



MRDFSET POLICY

DescriptionSwitches from one selection policy to another on all the SRDF directors on the Symmetrix system.

SyntaxMRDFSET POLICY {LCL(cuus)|RMT(cuus,hoplist)},{LEGACY|WEIGHTED)

Where:

LCL


cuus


RMT


hoplist


LEGACY

Specifies the older selection policy where asynchronous workload(s) are preferred over synchronous workloads.

WEIGHTED

Specifies the selection policy for servicing host IOs, asynchronous IOs and copies by giving higher preference to synchronous IOs over asynchronous IOs and copies, and giving higher preference to asynchronous IOs over copies.

ExampleEMCP001I MRDFSET POLICY LCL(3A01),WEIGHTED Mixed Mode Policy for Symm Serial: 000195700086 has been set to:

WEIGHTED END OF MRDFSET POLICY STATEMENT



MRDFSET WEIGHTS

DescriptionChanges the CPU distribution ratio among workload classes. The SYNC, ASYNC, and COPIES values must have a combined value of 100, and none of the values can be 0.

SyntaxMRDFSET Weights {LCL(cuus)|RMT(cuus,hoplist)},{RADir(##)|Defaults},Sync(value),Async(value),Copies(value)

Where:

LCL


cuus


RMT


hoplist


RADir(##)


Defaults

Specifies the weights are to be established for all SRDF directors when the system is brought online.

Sync (value)

Specifies the director CPU percentage (weight) that the Synchronous SRDF workloads receive. Value equals a decimal value between 1 and 98, and the values of SYNC, ASYNC, and Copies must equal 100. The default value is 70.

Async (value)

Specifies the director CPU percentage (weight) that the Asynchronous SRDF workloads receive. Value equals a decimal value between 1 and 98, and the values of SYNC, ASYNC, and Copies must equal 100. The default value is 20.

Copies (value)

Specifies the director CPU percentage (weight) that the Host Copies workloads receive. Value equals a decimal value between 1 and 98, and the values of SYNC, ASYNC, and Copies must equal 100. The default value is 10.



ExampleEMCP001I MRDFSET WEIGHTS

LCL(3A01),RADIR(56),SYNC(30),ASYNC(50),COPIES(20) Mixed mode CPU weight for symm serial:000195700086 has been set to:(SYNC=30,ASYNC=50,COPIES=20) for RADIR=56

END OF MRDFSET WEIGHT STATEMENT

MRDFSET RESET

DescriptionResets the system level or director level CPU values back to default values.

When the DEFAULTS keyword is used the system level defaults are reset back to the coded (factory) value. When RADIR(##) is specified, the CPU weights are reset back to the system level default.

SyntaxMRDFSET RESet {LCL(cuus)|RMT(cuus,hoplist)},{RADir(##)|Defaults}

Where:

LCL


cuus


RMT


hoplist


RADir(##)


Defaults

Specifies the weights are to be established for all SRDF directors when the system is brought online.

ExampleEMCP001I MRDFSET RESET LCL(3A01),RADIR(59) Mixed mode Reset to box level defaults for RADIR=59 for Symm serial: 000195700086 END OF MRDFSET RESET STATEMENT



Miscellaneous control statementsThis section describes other control statements.

EXIT

DescriptionCauses the procedure to exit prior to executing the next statement.

Syntax

EXIT

WAIT ##

DescriptionCauses the procedure to wait before executing the next statement. Use the wait statement to delay the execution of the next SPC, DCP or MRDF set and query statements

Syntax

WAIT ##

Where:

## is the number of seconds to wait. The maximum allowable value is 600.

Miscellaneous control statements 495


QoS examples

SPC functionality

The following example illustrates SPC functionality. This JCL was used to generate the second sample report in “DISPSPC examples” on page 496.

//jobname JOB (1000),'accnt','pgmmrname',CLASS=A,MSGCLASS=X //QOS EXEC PGM=EMCQOS,REGION=4M //STEPLIB DD DISP=SHR,DSN=ds-scf-prefix.LINKLIB //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD DUMMY //SCF$nnnn DD DUMMY //SYSOUT DD SYSOUT=* //QOSINPUT DD * DISPSPC LCL(9A00) SETDIR RESET SETSPC LCL(9A00) SETDIR 1-64 SETSPC LCL(9A00) DISPDEVP CUU(9A00-9A0F) DISPDEV LCL(9A00) SETDEVP CUU(9A00),1 SETDEVP CUU(9A01-9A04),5 SETDEVP CUU(9A04-9A9F),9 SETDEVP CUU(9B9C-9BAB),16F SETDEV LCL(9A00)

DISPSPC examplesExample 1 In the following example, none of the directors have been set for SPC.

Symmetrix Quality of Service Configuration Information Serial Number: 000190300344 Model Number: 07 MicroCode Level: 57720033 SAI Version: 570 Symmetrix Quality of Service Display SPC Request General Control Settings ------------------------------------------------------------------------------ Update Priority Directors ....... Not Set Update SPC Priority ............. Not Set Update Device Priority .......... Not Set Update Read Device Priority ..... Not Set Directors Updating .............. 0000000000020000 Directors Not Found ............. 0000000000000000 Enabled Directors -------------------------------------------------------------------------------------

1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12:13: 14: 15: 16:17: 18: 19: 20:21: 22: 23: 24:25: 26: 27: 28:29: 30: 31: 32:33: 34: 35: 36:37: 38: 39: 40:41: 42: 43: 44:45: 46: 47: 48:49: 50: 51: 52:53: 54: 55: 56:57: 58: 59: 60:61: 62: 63: 64:



Example 2 In this example, all of the directors have been set, using the commands:

SETDIR 1-64SETSPC LCL(9A00)

Serial Number: 000190300344 Model Number: 07 MicroCode Level: 57720033 SAI Version: 570 Symmetrix Quality of Service Display SPC Request General Control Settings ------------------------------------------------------------------------------ Update Priority Directors ....... Not Set Update SPC Priority ............. Not Set Update Device Priority .......... Set Update Read Device Priority ..... Set Directors Updating .............. 0000000000000000 Directors Not Found ............. 3FFC3FFC3FFC3FFC Enabled Directors ------------------------------------------------------------------------------------- D01: Enabled D02: Enabled D03: Enabled D04: Enabled D05: Enabled D06: Enabled D07: Enabled D08: Enabled D09: Enabled D10: Enabled D11: Enabled D12: Enabled D13: Enabled D14: Enabled D15: Enabled D16: Enabled D17: Enabled D18: Enabled D19: Enabled D20: Enabled D21: Enabled D22: Enabled D23: Enabled D24: Enabled D25: Enabled D26: Enabled D27: Enabled D28: Enabled D29: Enabled D30: Enabled D31: Enabled D32: Enabled D33: Enabled D34: Enabled D35: Enabled D36: Enabled D37: Enabled D38: Enabled D39: Enabled D40: Enabled D41: Enabled D42: Enabled D43: Enabled D44: Enabled D45: Enabled D46: Enabled D47: Enabled D48: Enabled D49: Enabled D50: Enabled D51: Enabled D52: Enabled D53: Enabled D54: Enabled D55: Enabled D56: Enabled D57: Enabled D58: Enabled D59: Enabled D60: Enabled D61: Enabled D62: Enabled D63: Enabled D64: Enabled QOS1026I Job Completion Status R15_Rc: 00000000 Parse_Rc: 00000000 PRc: 00000000 SRc: 00000000

QoS examples 497


DCP functionality

The following JCL illustrates DCP functionality.

//QOS EXEC PGM=EMCQOS,REGION=4M//STEPLIB DD DISP=SHR,DSN=ds-scf-prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD DUMMY//SCF$nnnn DD DUMMY//SYSOUT DD SYSOUT=*//QOSINPUT DD *DISPCCFG LCL(DE00),ALL display the whole boxDISPCCFG LCL(DE00),ID(0) display partition id 0 (default)DISPCCFG LCL(DE00),ID(5) display partition id 5SETCACHE LCL(DE00),INIT remove all partitions back to defaultSETCPADD LCL(DE00),ID(1),TCACHE(14),MINCACHE(10),MAXCACHE(19),create partition id 1AGE(1000),WP(45),CPNAME(MFCP1)SETCPMVD CUU(DE10-DE12)SETCPMV LCL(DE00),ID(1) move device DE10-DE12 to partition id 1SETCPMVD RDFG(F1)SETCPMV LCL(DE00),ID(1),TYPE(RDFG)*SETCPMVD 0050SETCPMV LCL(DE00),ID(1),TYPE(META)*SETCPMVD 0060SETCPMV LCL(DE00),ID(1),TYPE(SCKD)SETCACHE LCL(DE00),ENABLE enable the new configuration//

DISPCCFG exampleThe following example report illustrates cache configuration parameters for the entire Symmetrix system.

EMCP001I DISPCCFG LCL(DE00) 1SYSTEM=X1E Symmetrix Quality of Service Report 0Symmetrix Quality of Service Configuration Information Serial Number: 000190300097 Model Number: 07 MicroCode Level: 57720033 SAI Version: 570 Symmetrix Quality of Service Cache Configuration Parameters

Group Id ............... 0Group Name ............. Default Write Pending Limit .... 80Target Cache Allocation 80Minimum Cache Allocation 0Maximum Cache Allocation 100Slot Donation Time ..... 300Destage Priority ....... 1

Group Id ............... 5Group Name ............. AA-AAAA AAAAAA Write Pending Limit .... 69Target Cache Allocation 20Minimum Cache Allocation 16Maximum Cache Allocation 25Slot Donation Time ..... 4095Destage Priority ....... 1



DISPCUSE exampleThe following example report illustrates cache partition utilization parameters for the entire Symmetrix system.

EMCP001I DISPCUSE LCL(DE00) Symmetrix Quality of Service Cache Usage Parameters

Group Id ............... 0Group Name ............. DefaultWrite Pending Limit .... 80Target Cache Allocation 80Minimum Cache Allocation 0 Maximum Cache Allocation 100Slot Donation Time ..... 300Destage Priority ....... 1 # of Slots Being Used .. 20290% of Slots Being Used .. 100Number of Devices ...... 670

Group Id ............... 5Group Name ............. AA-AAAA AAAAAA Write Pending Limit .... 69Target Cache Allocation 20Minimum Cache Allocation 16Maximum Cache Allocation 25Slot Donation Time ..... 4095Destage Priority ....... 1# of Slots Being Used .. 0% of Slots Being Used .. 0Number of Devices ...... 20

DISPCDEV exampleThe following example report displays the cache group to which the device is assigned.

EMCP001I DISPCDEV 30-3F EMCP001I DISPCDV LCL(DE00) Symmetrix Quality of Service Cache Device Group Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp 0030 07 0031 07 0032 07 0033 07 0034 07 0035 07 0036 07 0037 07 0038 07 0039 07 003A 07 003B 07 003C 07 003D 07 003E 07 003F 07 0000 00 0000 00 0000 00 0000 00

DISPCDVG exampleThe following example report displays the cache group devices for the specified SRDF group.

EMCP001I DISPCDVG RDFG(F1) EMCP001I DISPCDV RMT(DE00,4) Symmetrix Quality of Service Cache Device Group RDF Group - F1 Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp 0049 07 004A 07 004B 07 004C 07 004D 07 004E 07 004F 07 0000 00 0000 00 0000 00

DISPCGRP exampleThe following example report displays the cache group devices for the specified cache group.

EMCP001I DISPCGRP LCL(DE00),ID(7) Symmetrix Quality of Service Cache Group Devices Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp Dev Grp 0030 07 0031 07 0032 07 0033 07 0034 07 0035 07 0036 07 0037 07 0038 07 0039 07 003A 07 003B 07 003C 07 003D 07 003E 07 003F 07 0048 07 0050 07 0051 07 0052 07 0053 07 0054 07 0055 07 0056 07 0057 07 00C0 07 00C1 07 00C2 07 00C3 07 0282 07 0283 07 0284 07 0285 07 0292 07 0293 07 0294 07 0295 07 0000 00 0000 00 0000 00

QoS examples 499


DISPCPYP exampleThe following example report displays current copy priority settings for a logical volume.

SYSTEM=X11D Symmetrix Quality of Service Report 10:18:54 09/15/2010 PAGE 1 0Symmetrix Quality of Service Configuration Information Serial Number: 000192600215 Model Number: 08 Enginuity Level: 58750079 SAI Version: 720 Symmetrix Quality of Service Display Copy Priority Request LV RDF VLUN SERV SNAP LV RDF VLUN SERV SNAP LV RDF VLUN SERV SNAP ---------------------------------------------------------------------------------------------------- 000002E8 07 14 08 11 000002E9 07 14 08 11 000002EA 07 14 08 11 000002EB 07 14 08 11 000002EC 07 14 08 11 000002ED 07 14 08 11 000002EE 07 14 08 11 000002EF 07 14 08 11 000002F0 07 14 08 11 000002F1 07 14 08 11 000002F2 07 14 08 11 000002F3 07 14 08 11 000002F4 07 14 08 11 000002F5 07 14 08 11 000002F6 07 14 08 11 000002F7 07 14 08 11

LRU functionality

The following JCL illustrates LRU functionality in the Quality of Service Utility. This JCL was used to generate the sample report in “QOSPRINT DD example” on page 501.


//Jobname JOB (1000),CLASS=A/*JOBPARM LINES=999999 //* EMCQOS must be in an authorized dataset. //QOS EXEC PGM=EMCQOS //STEPLIB DD DISP=SHR,DSN=Dataset.Where.EMCQOS.IS//SYSUDUMP DD SYSOUT=* //SYSIN DD DUMMY //SYSOUT DD SYSOUT=* //*//SYSPRINT DD SYSOUT=* //SCF$EMC DD DUMMY EMC or your SCF Suffix //* Required for control statements //QOSINPUT DD * * Get the current QOS settings for a range of devices.QOSGET CUU=B300-B301 * Set the values for a range of devices. QOSSET CUU=B300-B301,RDFP=1,BCVP=3,SERP=4,LRU=(0,1,2,3)* Get the current QOS settings for a range of devices.QOSGET CUU=B300-B301 * Get the current QOS settings for a single device. QOSGET CUU=B3FF* Set the values for a single device. QOSSET CUU=B3FF,RDFP=10,BCVP=10,SERP=10,LRU=(0)* Get the current QOS settings for a single device.QOSGET CUU=B3FF* Reset the QOS settings for a range of devices.QOSRESET CUU=B300-B301* Reset the QOS settings for a single device.QOSRESET CUU=B3FF/*//



SYSPRINT DD exampleSample output from the SYSPRINT DD statement is shown below. Parsing messages and QoS application messages are written to this DD statement. Input commands are echoed to this dataset.

QOSPRINT DD exampleIf QOSPRINT is not specified, this output will go to SYSPRINT. An example QOSPRINT report is shown below.

Note: You can find a sample report in the QOS130.SYSPRINT dataset.

Symmetrix Quality of Service Configuration Information Serial Number: 000000006205 Model Number: 06 MicroCode Level: 56700099 SAI Version: 570 Number of LRUs: 1 Number of LRU Slots: 407,446 Number of Volumes: 04A2 LRU Usage Array: 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% 6% Symmetrix Quality of Service Get Settings Request LV BCV RDF Service SNAP LRU Mask ------------------------------------------------------------------------------------------0018 00 00 00 00 0001 Symmetrix Quality of Service LRU Masks

...1 - LRU 0

...2 - LRU 1

...4 - LRU 2

...8 - LRU 3

..1. - LRU 4

..2. - LRU 5

..4. - LRU 6

..8. - LRU 7

.1.. - LRU 8

.2.. - LRU 9

.4.. - LRU 10

.8.. - LRU 111... - LRU 122... - LRU 134... - LRU 148... - LRU 15


When you interpret the sample report shown above, you should be aware of the following:

◆ Values are in hexadecimal, except for the serial number, model number, and Enginuity level.

◆ The LRU Mask fields are bit mask fields. The definition for the mask values is provided at the end of the report.

EMCP001I QOSRESET CUU=3018-3019EMCP001I QOSSET CUU=3018-3019,RDFP=1,BCVP=3,SERP=4,EMCP001I LRU=(0,1,2,3)EMCP001I QOSGET CUU=3018-3019EMCP001I QOSRESET CUU=3018-3019EMCP001I QOSSET CUU=3018,RDFP=10,BCVP=10,SERP=10,EMCP001I LRU=(0)EMCP001I QOSGET CUU=3018-3019EMCP001I QOSRESET CUU=3018-3019EMCP001I QOSGET CUU=3018-3019QOS1026I Job Completion Status. R15_Rc: 00000000 Parse_Rc: 00000000 PRc: 00000000 SRc: 00000000

QoS examples 501


◆ The report is self-describing. Additional definitions are as follows:

• # of LRUs — The number of LRUs defined through SymmWin (a maximum of 16) for Symmetrix systems.

• # of LRU Slots — The total number of slots for all LRUs.

• LRU Usage Array — The percentage of LRU slots assigned to each defined LRU.

• LRU Mask — These mask bytes define which LRU the Logical Volume is assigned to. If LRU Mask is ‘0000’ the Logical Volume has not been initialized to an LRU.

• LRU Name — The name of the LRU, as originally defined for your system.

Note: When you enter a RESET command, the LRU assignment is set to the maximum amount of LRUs defined. If four LRUs are defined, as shown in on the previous page, the default value for LRU Mask will be 000F.

MRDF functionality

Workload based re-distribution examplesWhen one or more of the workload types are not active, the QoS values automatically adjust so that the RDF director is always capable of operating at 100%.

Workload types are polled for, and in the absence of one or more workload types, the workload distribution values are automatically re-distributed to the types of SRDF replication that are active.

The following three examples illustrate the redistribution values:

Example 1 The default values are set at 70, 20, 10. However there is only SRDF/A and Adaptive copy workload active. Since there is a 2:1 ratio between the SRDF/A and adaptive copy settings, the QoS values automatically adjust to 66.6.for SRDF/A and 33.3 for Adaptive copy.

Example 2 The default values are set at 70, 20, 10. However, there is only SRDF/S and Adaptive copy workload active. Since there is a 3.5:1 ratio between the SRDF/S and adaptive copy settings, the QoS values automatically adjust to 78 for SRDF/S and 22 for Adaptive copy.

Example 3 Custom QOS values have been set at 60, 30, 10. The only active workload is Adaptive copy. The adaptive copy workload will consume 100% of the RDF CPU.

When multiple RDF groups exist on an RDF director, each active RDF group shares an equal percentage of the available CPU resource (within their QoS parameters). In other words, if there were 2 RDF groups running SRDF/S in example 2 above, each would get 39% of the RDF CPU.

As workload types start and stop, the RA QoS values adjust accordingly.



SYSPRINT DD exampleSample output from the SYSPRINT DD statement is shown below. Parsing messages and QoS application messages are written to this DD statement. Input commands are echoed to this dataset.

EMCQOS - V740-REL-SQOS740 EMCP001I MRDFDISP WEIGHTS LCL(3A01) QOS1026I Job Completion Status R15_Rc: 00000000 Parse_Rc: 00000000 PRc: 00000000 SRc: 00000000

MRDFOUT DD exampleAn example MRDFOUT report is shown below.

EMCP001I MRDFDISP WEIGHTS LCL(3A01)

Current selection policy for Symm serial:000195700086

Director # POLICY Sync CPU% A-Sync CPU% Copies CPU% ---------- --------- --------- ----------- ----------- 47 WEIGHTED 70 20 10 56 WEIGHTED 20 50 30 57 WEIGHTED 70 20 10 59 WEIGHTED 70 20 10

END OF MRDFDISP WEIGHT STATEMENT

Note: If you are sending the output to a dataset, use DISP=MOD to capture all commands from one job.

QoS error and event messagesYou can find an explanation of EMC Quality of Service error event messages and a list of the messages that EMC Quality of Service can generate in the EMC Mainframe Enablers Message Guide.

QoS error and event messages 503

CHAPTER 11zBoost PAV Optimizer

This chapter covers the following topics:

◆ Introduction.......................................................................................................... 506◆ Getting started...................................................................................................... 508◆ Optimizing I/Os .................................................................................................... 510◆ SMF recording ....................................................................................................... 516

zBoost PAV Optimizer 505

zBoost PAV Optimizer

IntroductionzBoostTM PAV Optimizer improves the performance of zHPF multi-track I/Os by systematically lowering response time resulting in reduced job elapsed time. This is achieved by splitting multi-track I/Os into multiple smaller “constituent I/Os” and executing them in parallel on alias devices by using the Compatible Parallel Access Volume (COMPAV) facility of the VMAX system.

You determine when zBoost PAV Optimizer gets invoked by specifying one or more of the following:

◆ z/OS device number or range◆ Volser or volser mask◆ SMS storage group name◆ Application (started task or batch job name)

“Selecting devices” on page 512, “Limiting optimization by started task/job” on page 512, and “Limiting optimization by tracks” on page 513 describe how to control the optimization scope for zBoost PAV Optimizer.

After zBoost PAV Optimizer is enabled, you can control the amount of resources consumed, such as the minimum and maximum number of constituent I/Os allowed. In addition, you can monitor the alias consumption by zBoost PAV Optimizer and adjust its activity accordingly so as to not impact overall I/O throughput at the system and LCU level. “Controlling number of splits/constituent I/Os” on page 513 and “Setting quiesce points” on page 514 discuss the resource utilization controls.

Besides normal operation mode called Active mode, zBoost PAV Optimizer provides two additional modes intended for planning and analysis: Passive mode and Monitor mode. “Operation modes” on page 511 provides further details on zBoost PAV Optimizer modes.

zBoost PAV Optimizer can write SMF records that detail its operation, such as the number of I/Os operated on, the number of constituent I/Os produced, the channel and System Assist Processor (SAP) resource used. “SMF recording” on page 516 describes SMF records generated by zBoost PAV Optimizer.

Note: Refer to Mainframe Enablers component Service Notes for latest information and documentation updates related to zBoost PAV Optimizer integration. Service notes files (Service_Notes_SSCF760.txt, Service_Notes_SCGP760.txt, Service_Notes_SSNP760.txt, Service_Notes_STFX760.txt) are included with MFE maintenance in the MFE760_Fixes.zip file and are also viewable as text files on https://support.emc.com.



Restrictions

zBoost PAV Optimizer restrictions are as follows:

◆ z/OS V1.13 or higher is required.

◆ z/OS zHPF must be turned on (SETIOS ZHPF=YES).

◆ The minimum Enginuity level is 5876 with zBoostTM.

◆ zBoost PAV Optimizer processes devices in the active subchannel set only. 3390D devices will only be selected for processing if they are in the active subchannel set, such as after an AutoSwap event.

◆ Although not necessary for PAV optimization to be performed, HyperPAV aliases should be defined to included devices. Dynamic and static PAV aliases do not provide the necessary sharing among the base devices to take full advantage of PAV optimization.

Introduction 507


Getting started

Security

zBoost PAV Optimizer commands are authorized using SAF resource EMC.ADMIN.CMD.DEV.OPTIMIZE in class XFACILIT. For display commands (DISPLAY), read access is required. For active commands (ENABLE, DISABLE, SUSPEND, RESUME, RESET), update access is required.

For more information, refer to the description of the EMCSAFI Security Interface in the Mainframe Enablers Installation and Customization Guide.

Configuring zBoost PAV Optimizer

After installation of ResourcePak Base, enable and configure zBoost PAV Optimizer using the SCF initialization parameters described in “Configuration File and Initialization Parameters” on page 57.

The zBoost PAV Optimizer initialization parameters fall into three categories:

◆ Enablement parameters

◆ Selection parameters

◆ Resource utilization parameters

Enablement parametersEnablement parameters specify global activation values for zBoost PAV Optimizer. With enablement parameters, you can:

◆ Enable or disable zBoost PAV Optimizer

◆ Select zBoost PAV Optimizer operation mode and channel programs (read or write) to be optimized

◆ Set up SMF recording

◆ Enable verbose messaging

The enablement parameters are as follows:

◆ SCF.DEV.OPTIMIZE.ENABLE

◆ SCF.DEV.OPTIMIZE.PAV

◆ SCF.DEV.OPTIMIZE.SMF.RECID

◆ SCF.DEV.OPTIMIZE.VERBOSE

Selection parametersSelection parameters allow you to select devices and I/Os on which zBoost PAV Optimizer operates. Selection parameters include:

◆ Parameters that specify the devices to monitor:

• SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST

• SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST



• SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST

• SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST

• SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST

If no further selection parameters are specified, then any I/O to this set of devices will be a candidate for optimization subject only to the natural defaults for any parameters that have them.

◆ Parameters that limit optimization to only certain started tasks/batch jobs:

• SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST

• SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST

◆ Parameters that limit optimization to I/Os with a specified minimum number of tracks:

• SCF.DEV.OPTIMIZE.PAV.TRACK.MIN

• SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ

• SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE

The READ and WRITE parameters allow you to specify different values for read and write operations. Each READ or WRITE parameter has its own default value. However, the unqualified parameter may be used to change the default for either or both of the related parameters if it is not explicitly assigned a value.

Resource utilization parametersResource utilization parameters define how many system resources are used by zBoost PAV Optimizer.

The resource utilization parameters are as follows:

◆ Parameters that define the maximum number of splits (constituent I/Os):

• SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX

• SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ

• SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE

The READ and WRITE parameters allow you to specify different values for read and write operations. Each READ or WRITE parameter has its own default value. However, the unqualified parameter may be used to change the default for either or both of the related parameters if it is not explicitly assigned a value.

◆ Parameters that limit the number of active constituent I/Os, thus limiting resource utilization by zBoost PAV Optimizer:

• SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL

• SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU

• SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT

• SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE

Getting started 509


Optimizing I/Os

Summary of operations

Table 18 lists general zBoost PAV Optimizer operations.

Table 20 lists zBoost PAV Optimizer logging and messaging operations.

Table 18 General operations

Operation Control

Enable/disable zBoost PAV Optimizer SCF.DEV.OPTIMIZE.ENABLE initialization parameterDEV,OPTIMIZE ENABLE commandDEV,OPTIMIZE DISABLE command

Set zBoost PAV Optimizer operation mode SCF.DEV.OPTIMIZE.PAV initialization parameter

View zBoost PAV Optimizer configuration parameters

DEV,OPTIMIZE DISPLAY SUMMARY command

Suspend zBoost PAV Optimizer processing DEV,OPTIMIZE SUSPEND command

Resume zBoost PAV Optimizer processing DEV,OPTIMIZE RESUME command

Table 19 Logging and messaging operations

Operation Control

Enable SMF recording and set SMF record ID SCF.DEV.OPTIMIZE.SMF.RECID initialization parameter

Configure zBoost PAV Optimizer event logging DEV,OPTIMIZE LOG EVENTS command

Enable/disable verbose messaging SCF.DEV.OPTIMIZE.VERBOSE initialization parameter

View zBoost PAV Optimizer statistics DEV,OPTIMIZE DISPLAY SSID commandDEV,OPTIMIZE DISPLAY DEVICE commandDEV,OPTIMIZE DISPLAY EVENTS command

Reset zBoost PAV Optimizer statistics counters DEV,OPTIMIZE RESET command



Table 20 lists zBoost PAV Optimizer operations for defining the scope of optimization.

Table 21 lists zBoost PAV Optimizer operations for controlling resource utilization.

Operation modes

zBoost PAV Optimizer can run in the following modes:

◆ Active — This is normal operation mode. zBoost PAV Optimizer analyses channel programs and parallelizes multi-track I/Os. You can select whether read, write or both operations are optimized.

To run zBoost PAV Optimizer in Active mode, set the YES, Read, or Write value for the SCF.DEV.OPTIMIZE.PAV initialization parameter described on page 82.

◆ Passive — This mode is intended for planning and analysis. zBoost PAV Optimizer does all its normal analysis of channel programs and reports on what it would do if active. It analyzes multi-track channel programs and updates statistics that represent what it would have done if active without actually affecting the existing channel programs.

To run zBoost PAV Optimizer in Passive mode, set the PASsive for the SCF.DEV.OPTIMIZE.PAV initialization parameter described on page 82.

Table 20 Defining scope of optimization

Operation Control

Select devices for optimization SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST initialization parameterSCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST initialization parameterSCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST initialization parameterSCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST initialization parameterSCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST initialization parameter

Limit optimization by started task/batch job SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST initialization parameterSCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST initialization parameter

Limit optimization by number of tracks SCF.DEV.OPTIMIZE.PAV.TRACK.MIN initialization parameterSCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ initialization parameterSCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE initialization parameter

Table 21 Controlling resource utilization

Operation Control

Set maximum number of splits SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX initialization parameterSCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ initialization parameterSCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE initialization parameter

Set quiesce points SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL initialization parameterSCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU initialization parameterSCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT initialization parameterSCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE initialization parameter

Optimizing I/Os 511


◆ Monitor — This mode is intended for planning and analysis. zBoost PAV Optimizer collects statistics on zHPF channel program characteristics without doing any further analysis.

To run zBoost PAV Optimizer in Monitor mode, set the MONitor value for the SCF.DEV.OPTIMIZE.PAV initialization parameter described on page 82.

Selecting devices

You can select devices to be monitored by zBoost PAV Optimizer by making the following specifications:

◆ CUUs with the SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST parameter described on page 83

◆ Specific volsers with the SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST parameter described on page 91

◆ Volsers by mask with the SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST parameter described on page 90

◆ Volsers by SMS storage group with the SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST parameter described on page 88

The actual devices monitored are the union of all devices selected via any of these parameters.

Note: Devices to be included for zBoost PAV Optimizer must also be defined as SCF-accessible devices using the SCF.DEV.INCLUDE.LIST parameter described on page 81.

To eliminate specific devices, specify the CUUs of the devices to be excluded using the SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST parameter described on page 83.

If no further selection parameters are specified, then any I/O to this set of devices is a candidate for optimization subject only to the natural defaults for any parameters that have them.

Address/name resolutionzBoost PAV Optimizer resolves the z/OS device numbers (CUUs) whenever an INI,REFRESH command is performed or an SCF configuration change is detected. Volsers are resolved to CUUs for online devices only whenever an INI,REFRESH command is performed or an SCF configuration change is detected. SMS group names are resolved whenever an INI,REFRESH is performed, an SCF configuration change is detected, or if the SMS configuration is changed.

The volser and SMS storage group inclusion is reevaluated every hour to include or exclude any devices affected by changes. To force immediate reevaluation, issue the INI,REFRESH command as described in “INI,REFRESH” on page 147.

Limiting optimization by started task/job

Optimization may be limited to only certain started tasks or batch jobs by specifying their name or names via the SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST parameter described on page 84 or the SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST parameter described on page 84.



The names in SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST are used as the primary match list. If a name match cannot be found, then the list specified in the SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST parameter described on page 84 is searched. When a name matches both, a value in SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST and SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST, the counters maintained and displayed using the DEV,OPTIMIZE DISPLAY SUMMARY command (described in “DEV,OPTIMIZE DISPLAY SUMMARY” on page 179) will reflect the match on SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST only.

Limiting optimization by tracks

You can limit optimization to I/Os with a minimum number of tracks.

To do this, set the SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ parameter described on page 89 for read operations and the SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE parameter described on page 90 for write operations.

You can also define a value that will be assigned to these parameters if either or both of them are not specified. To do this, set the SCF.DEV.OPTIMIZE.TRACK.MIN parameter as described on page 89.

The SCF.DEV.OPTIMIZE.PAV.TRACK.MIN value is not validated because it is not a control value in its own right. Once SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ and/or SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE parameter inherits a value from SCF.DEV.OPTIMIZE.PAV.TRACK.MIN, that value will be validated against the allowed range for that parameter and processed accordingly.

Note: If SCF.DEV.OPTIMIZE.TRACK.MIN is set to 0 (zero), it is the same as not specifying it at all. In this case, the other two parameters would still have their normal defaults.

Controlling number of splits/constituent I/Os

You can define the maximum number of splits/constituent channel programs that zBoost PAV Optimizer creates during optimization.

To do this, set the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ parameter described on page 87 for read operations and the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE parameter described on page 88 for write operations.

You can also define a value that will be assigned to these parameters if either or both of them are not specified. To do this, set the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX parameter as described on page 87.

The SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX value is not validated because it is not a control value in its own right. Once SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ and/or SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE parameter inherits a value from SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX, that value will be validated against the allowed range for that parameter and processed accordingly.

Note: If SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX is set to 0 (zero), it is the same as not specifying it at all. In this case, the other two parameters would still have their normal defaults.

Optimizing I/Os 513


Setting quiesce points

Quiesce points limit the number of active splits/constituent I/Os, thus limiting resource utilization by zBoost PAV Optimizer.

For example, if a quiesce point of 34 is specified, zBoost PAV Optimizer will quiesce while the number of requests is above 34. The active I/Os must be at or below 34 before any new PAV optimization is performed.

Quiesce points may be set at the following levels:

◆ Globally — The global quiesce point limits resource utilization for all zBoost PAV Optimizer requests associated with the owning SCF address space.

To set the global quiesce point, use the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL parameter described on page 85.

◆ For an LCU — The LCU quiesce point limits resource utilization for all zBoost PAV Optimizer requests associated with the owning SCF address space on the same LCU. It can be used to limit the number of PAV aliases used.

To set the LCU quiesce point, use the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU parameter described on page 86.

You can also define the LCU quiesce point as a percentage of configured HyperPAV alias devices for each LCU. To do so, use the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT parameter described on page 86.

◆ For a device — The device quiesce point limits resource utilization for all zBoost PAV Optimizer requests associated with the owning SCF address space on the same base device. They can be used to limit the number of PAV aliases used by any base device.

To set the device quiesce point, use the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE parameter described on page 85.

The quiesce point values are checked at the initiation of split processing for each I/O and will allow the optimization to proceed if the quiesce point has not been reached. If this value is reached during the splitting of a particular I/O, then the splitting will continue for that I/O.

If no quiesce point values are specified, then the resource limitations are implicitly defined by the number of I/O requests that z/OS (IOS) can start to included base devices and their available alias devices. zBoost PAV Optimizer only performs processing on I/Os that have been selected for processing by IOS. For instance, if only a single base is included for zBoost PAV Optimizer and there are 20 configured alias devices, then the maximum number of active constituent I/Os will be 21. In this instance, the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX value will dictate the total constituent I/Os created for the active requests for the device.

The number of skipped optimization channel programs due to the quiesce points being reached can be displayed using the DEV,OPTIMIZE DISPLAY DEVICE ALL FILTER SKIPPED command, as described in “DEV,OPTIMIZE DISPLAY DEVICE” on page 176. The skipped column under the type “Constituent I/O” is the number skipped due to the quiesce points being reached.



Consistency support

By design, zBoost PAV Optimizer does not return successful completion of an original I/O on a source volume to the application until all its constituent I/Os are complete.

It should be noted, however, that it is possible during a consistency operation (MSC cycle switch, ECA-TF or ECA-RDF event) that only a subset of the constituent I/Os making up an original I/O could be completed on the TimeFinder or SRDF replica (for example, an SRDF/A transmit cycle, a TimeFinder target volume, or an SRDF/S R2 device).

To prevent this “partial completion” of an I/O on a TimeFinder or SRDF replica, zBoost PAV Optimizer provides the ability to suspend and resume write I/O splitting around consistency events.

The solutions outlined below are designed to minimize or eliminate this “partially completed” I/O condition during consistency formation operations.

IMPORTANT

It is a requirement that all consistency operations against data being operated on by zBoost PAV Optimizer be initiated and controlled from z/OS.

Products that require integration with zBoost PAV Optimizer to suspend and resume write I/O splitting include:

◆ SRDF/A MSC

Use the SCF.MSC.PAVO initialization parameter described on page 106 to enable zBoost PAV Optimizer support for MSC environment.

◆ ConGroup

Use the PAVO configuration parameter of ConGroup to enable zBoost PAV Optimizer support for ConGroup.

◆ SRDF/AR

◆ ECA events (Consistent Split/Snap)

◆ TimeFinder/Mirror (Consistent Split/Remote Consistent Split/Multi-Hop Consistent Split)

◆ TimeFinder/Clone and TimeFinder/Snap (Activate Consistent, TF/Consistency Group)

◆ ISVs products initiating consistency technology operations

Note: Refer to Mainframe Enablers component Service Notes for latest information and documentation updates related to zBoost PAV Optimizer integration. Service notes files (Service_Notes_SSCF760.txt, Service_Notes_SCGP760.txt, Service_Notes_SSNP760.txt, Service_Notes_STFX760.txt) are included with MFE maintenance in the MFE760_Fixes.zip file and are also viewable as text files on https://support.emc.com.

The integration is provided through the use of attention interrupts and automatically initiated by participating applications.

Note: IBM Copy Services operations (PPRC, XRC, Flashcopy) are supported with zBoost PAV Optimizer, but there is possibility of partially completed I/Os on target devices.

You can also manually suppress write I/O splitting by using the SUSPEND and RESUME commands (described on page 180 and page 181). A manual suspend will affect all LPARs with active EMCSCF environments and will remain in effect until a RESUME command cancels it.

Optimizing I/Os 515


SMF recording

Overview

zBoost PAV Optimizer can write SMF records to document its monitor and optimization data. This data is a collection of counts of various types. SMF recording will take place every SMF interval as indicated by user-defined z/OS parameters.

To enable SMF recording by zBoost PAV Optimizer, specify a unique SMF record ID in the SCF.DEV.OPTIMIZE.SMF.RECID initialization parameter described on page 92.

With the SMF reporting utility described in “SMF reporting utility” on page 525, information from the SMF records can be extracted to a comma-separated values (.csv) file suitable for processing as a spreadsheet.

SMF record types

zBoost PAV Optimizer writes SMF records of the following types:

◆ STATS — Provides zBoost PAV Optimizer statistics. STATS records can be of the following subtypes:

• A GLOBAL record documents global counts.

• An SSID record provides summary statistics per SSID.

• A DEVICE record provides statistics per each monitored device.

◆ JOBS — Documents the number of I/Os found matching each started task/job name and prefix specified (if any). This additional SMF record is written when monitoring by started tasks or jobs is enabled using the SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST parameter described on page 84 or the SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST parameter described on page 84.

◆ EVENTS — Documents occurrence of various monitor events for diagnostic purposes.

For each SMF interval (ENF 37), zBoost PAV Optimizer writes one STATS GLOBAL record, one STATS SSID record for each SSID, one STATS DEVICE record for each processed device, and one EVENTS record. When enabled, one JOBS record is additionally written.

Note: The DEV,PAVO RESET FULL command described on page 180 also causes the same set of SMF records to be written immediately before the statistics are reset.

SMF record format

STATS recordThe STATS record consists of a standard SMF header followed by a variable number of sections, currently 7 (seven). Depending on the mode, any number of these sections could be null.

◆ zHPF PAV optimization parameters

◆ Basic monitoring zHPF statistics

◆ zBoost PAV Optimizer passive monitoring zHPF statistics



◆ zBoost PAV Optimizer active monitoring zHPF statistics

◆ PAV optimization zHPF skip processing by parameters

◆ PAV optimization zHPF skip processing

◆ zBoost PAV Optimizer logging event statistics

Each section consists of a descriptive header followed by an array of data element IDs and an array of data fields. The header documents the number of fields and the size of each ID field. An ID field consists of one byte defining the length of the corresponding data field followed by a numeric field ID in the remaining byte(s).

Note: Only fields with non-null values are recorded. If all data fields were null, then the record would consist of only the headers.

The STATS record layout is as follows:

SRXHSMF DSECT , * * STANDARD SMF RECORD HEADER * SRXHSMF_LEN DS H * RECORD LENGTH SRXHSMF_SEG DS H * SEGMENT DESCRIPTOR (ALWAYS 0) SRXHSMF_FLG DS XL1 * SYSTEM INDICATOR SRXHSMF_RTY DS XL1 * SMF RECORD NUMBER SRXHSMF_TME DS XL4 * TIME IN 100THS OF A SECOND SRXHSMF_DTE DS XL4 * DATE IN PACK DECIMAL - 0CYYDDDF SRXHSMF_SID DS XL4 * SYSTEM ID * * SUBTYPE IDENTIFIER * SRXHSMF_SSI DS XL4 * SUBSYSTEM ID SRXHSMF_STY DS XL2 * SUBTYPE (USES X'00'-X'01') SRXHSMF_STY_GBL EQU 0 Global data SRXHSMF_STY_SSID EQU 1 SSID Data SRXHSMF_STY_DEV EQU 21 Device data SRXHSMF_STY_JOB EQU 3 JOBNAME counts SRXHSMF_STY_EVT EQU 4 Event record DS 4H DS 0D SRXHSMF_HDR_LEN EQU *-SRXHSMF * LENGTH OF RECORD HEADER * * Descriptive Header - Version, section count, OFF/LEN/CNT fields * SRXHSMF_DATA_HDR DS 0H * Data Header SRXHSMF_HDR_LENGTH DS H * Length of this header SRXHSMF_VERSION DS X * Record Version SRXHSMF_VERSION# EQU 1 Current version SRXHSMF_IDENT DS 0XL9 * Device identifier if STY=1 SRXHSMF_SCCUU DS XL3 * ssccuu Device number SRXHSMF_SYM# DS XL4 * Symm dev number SRXHSMF_MCOD DS XL2 * microcode level SRXHSMF_SECTION_CNT DS H * Number of sections (currently 7) SRXHSMF_RESERVED DS XL6 * SRXHSMF_SECTIONS DS 0F * First section descriptor SRXHSMF_DSLN EQU *-SRXHSMF * Header length * * DSECT for the section descriptors * SRXHSMFS DSECT , SRXHSMFS_OFF DS H * Offset of section SRXHSMFS_LEN DS H * Length of section SRXHSMFS_DSLN EQU *-SRXHSMFS * Section descriptor length

SMF recording 517


* * DSECT for the section headers * * Each section contains a header followed by two arrays, * one of field lengths and ID's and one of values. * The section header indicates the offset of each of the two * arrays, length of the field ID array element, and the count * of entries. Lengths of data array elements are variable * and are defined by the length associated with each field ID. * SRXHSMFH DSECT , SRXHSMFH_LENGTH DS H * Section length SRXHSMFH_SECTION DS CL20 * Section Name * CL20'Configuration Parms ' * CL20'zHPF Basic Stats ' * CL20'Passive Mon stats ' * CL20'Active Mon Stats ' * CL20'Passive Skip Stats ' * CL20'Active Skip Stats ' * CL20'Logging Event Stats ' SRXHSMFH_COUNT DS H * Number of fields SRXHSMFH_ID_OFF DS H * Offset within section of ID's SRXHSMFH_ID_LEN DS H * Length of each ID field SRXHSMFH_DATA_OFF DS H * Offset within section of Data DS H * Reserved SRXHSMFH_DSLN EQU *-SRXHSMFH * Section header length

JOBS recordThe JOBS record has a single section descriptor but no section header. The section consists of the following structure:

SRXJOBN DSECT , SRXJOBN_EYE DC CL4'SJOB' * EYE-CATCHER SRXJOBN_SP DC AL1 * SUBPOOL USED FOR THIS STORAGE SRXJOBN_LEN DC AL3(SRXJOBN_SIZE) * LENGTH OF THIS BLOCK SRXJOBN_VER DC AL1(SRXJOBN_VER_CURR) * VERSION OF THIS BLOCK SRXJOBN_VER_CURR EQU 0 * . CURRENT VERSION SRXJOBN_CBF1 DC XL1'00' * FLAGS DC AL2(0) * RESERVED SRXJOBN_FLAGS DS 0F Flags. SRXJOBN_FLAG1 DS X Flag 1 SRXJOBN_FLAG2 DS X Flag 2 SRXJOBN_FLAG3 DS X Flag 3 SRXJOBN_VERSION DS X Data area version SRXJOBN_V1 EQU 0 . Version 1 SRXJOBN_VERSION_CURR EQU SRXJOBN_V1 . Current version SRXJOBN_TOD DS D Creation/reset TOD SRXJOBN_COUNT DS F Count of jobnames in list DS 0D *---------------------------------------------------------------------

** Jobname entry list **---------------------------------------------------------------------

*SRXJOBN_LIST DS 0CL24 Jobname list SRXJOBN_JOBNAME DS CL8 . Jobname SRXJOBN_JOBNAME_LN DS X . Jobname length-1 DS XL6 . Available SRXJOBN_IND DS X . Indicator SRXJOBN_IND_PFX EQU X'01' . JOBPREFIX entry SRXJOBN_MATCHCNT DS D . Match count

Note: Both JOBNAME and JOBPREFIX entries appear within a single list.



EVENTS recordThe EVENTS record has one section descriptor and the section has a standard section header. However, for this section, the ID_LEN is 1 and the ID array is simply an array of one-byte EVENT numbers. The data for each event is a structure of the following form:

SRXHEVT_FUNC_LIST DS 0D SRXHEVT_FUNC_LIST_TOD_L DS D TOD of last event logged SRXHEVT_FUNC_LIST_TOD_U DS D TOD of last event not loggedSRXHEVT_FUNC_LIST_CNT_L DS F Count of events logged SRXHEVT_FUNC_LIST_CNT_U DS F Count of events not logged SRXHEVT_FUNC_LIST_DEV DS XL2 Device CUU of last event DS XL6 Reserved DS 0D SRXHEVT_FUNC_LIST_SIZE EQU *-SRXHEVT_FUNC_LIST

STATS record fields

Note: In the following tables, the Title column shows the heading of the column used for the field in the .csv file generated from the STATS record.

Table 22 Section 1 — zHPF PAV optimization parameters

Source Field Name Ln ID# Title Description

SRXHCPS_FCX_PAVO_QUIPOINT_GBL 4 1 QPT_GBL Quiesce point for all active requests. Applies to READ and WRITE requests across all devices. No new requests will be considered for this system once this count is reached. 0 = no maximum count.

SRXHCPS_FCX_PAVO_QUIPOINT_DEV 4 2 QPT_DEV Quiesce point for device active requests. Applies to READ and WRITE requests for the same device. No new requests will be considered for this device once this count is reached. 0 = no maximum count.

SRXHCPS_FCX_PAVO_QUIPOINT_LCU 4 3 QPT_LCU Quiesce point for LCU active requests. Applies to READ and WRITE requests for the same LCU. No new requests will be considered for this LCU once this count is reached. 0 = no maximum count.

SRXHCPS_FCX_PAVO_QUIPOINT_LCUP 4 4 QPT_LCUP Quiesce point for LCU active requests for HyperPAV devices when a PCT value was specified in SRXHCPS_FCX_PAVO_QUIPOINT_PCT. Applies to READ and WRITE requests for the same LCU. No new requests will be considered for this LCU once this count is reached. 0 = no maximum count.

Note: This value is only set in LCU entries.

SRXHCPS_FCX_PAVO_QUIPOINT_PCT 4 5 QPT_PCT Quiesce point for LCU active requests as a percentage of those configured to the LCU. This value is used to calculate SRXHCPS_FCX_PAVO_QUIPOINT_LCUP which will be used instead of SRXHCPS_FCX_PAVO_QUIPOINT_LCU for HyperPAV devices.

SRXHCPS_FCX_PAVO_MIN_TRK#_R_I 4 6 MINTRK_R Minimum track count for optimization of READs.0 = no minimum count.

SRXHCPS_FCX_PAVO_MIN_TRK#_W_I 4 7 MINTRK_W Minimum track count for optimization of WRITEs.0 = no minimum count.

SMF recording 519


SRXHCPS_FCX_PAVO_MAX_SPLIT_R_ 4 8 MAXSPL_R Maximum number of optimized splits for READs.0 = no maximum number.

SRXHCPS_FCX_PAVO_MAX_SPLIT_W_ 4 9 MAXSPL_W Maximum number of optimized splits for WRITEs.0 = no maximum number.

SRXHCPS_FCX_PAVO_MIN_IOPRTY_R 4 10 MINIOP_R Minimum I/O priority for READs. 0 = no minimum priority.

SRXHCPS_FCX_PAVO_MIN_IOPRTY_W 4 11 MINIOP_W Minimum I/O priority for WRITEs. 0 = no minimum priority.

Table 22 Section 1 — zHPF PAV optimization parameters

Table 23 Section 2 — Basic monitoring zHPF counts


SRXHCPS_FCX_INIT_TOD_GBL 8 20 TOD_GBL Global area init TOD – STCK format

SRXHCPS_FCX_INIT_TOD_DEV 8 21 INIT_TODDEV Device area init TOD

SRXHCPS_FCX_INIT_TOD_SSID 8 22 INIT_TODSSID SSID/LCU area init TOD

SRXHCPS_FCX_TOT_ALL 8 23 TOT_ALL Total CPsa (TCW&CCW)

SRXHCPS_FCX_TOT_ZHPF 8 24 TOT_ZHPF Total zHPF CPs

SRXHCPS_FCX_TCCB_TIDA 8 25 TCCB_TIDA TCCB defined by TIDA

SRXHCPS_FCX_TCOB 8 26 TCOB TCOB CPs

SRXHCPS_FCX_ERP_REDRIVE 8 27 ERP_REDRIVE ERP redrives

SRXHCPS_FCX_RD 8 28 RD Read CPs

SRXHCPS_FCX_RD_BYTE 8 29 RD_BYTE Read byte count

SRXHCPS_FCX_WR 8 30 WR Write CPs

SRXHCPS_FCX_WR_BYTE 8 31 WR_BYTE Write byte count

SRXHCPS_FCX_BIDI 8 32 BIDI BiDi CPs

SRXHCPS_FCX_BIDI_RD_BYTE 8 33 BIDI_RD_BYT BiDi read byte count

SRXHCPS_FCX_BIDI_WR_BYTE 8 34 BIDI_WR_BYT BiDi write byte count

SRXHCPS_FCX_BASE 8 35 BASE Base CPs

SRXHCPS_FCX_BASE_RD 8 36 BASE_RD Base read CPs

SRXHCPS_FCX_BASE_RD_BYTE 8 37 BASE_RD_BYT Base read byte count

SRXHCPS_FCX_BASE_WR 8 38 BASE_WR Base write CPs

SRXHCPS_FCX_BASE_WR_BYTE 8 39 BASE_WR_BYT Base write byte count

SRXHCPS_FCX_TCAX 8 40 TCAX TCAX CPs

SRXHCPS_FCX_TCAX_RD 8 41 TCAX_RD TCAX read CPs

SRXHCPS_FCX_TCAX_RD_BYTE 8 42 TCAX_RD_BYT TCAX read byte count

SRXHCPS_FCX_TCAX_WR 8 43 TCAX_WR TCAX write CPs



SRXHCPS_FCX_TCAX_WR_BYTE 8 44 TCAX_WR_BYT TCAX write byte count

SRXHCPS_FCX_OTHER 8 45 OTHER Other CPs – not TTE or base

SRXHCPS_FCX_OTHER_RD 8 46 OTHER_RD Other read CPs

SRXHCPS_FCX_OTHER_RD_BYTE 8 47 OTHER_RD_BYTE

Other read byte count

SRXHCPS_FCX_OTHER_WR 8 48 OTHER_WR Other write CPs

SRXHCPS_FCX_OTHER_WR_BYTE 8 49 OTHER_WR_BYT

Other write byte count

a. CP stands for Channel Program.

Table 23 Section 2 — Basic monitoring zHPF counts

Table 24 Section 3 — PAV optimization passive zHPF counters


SRXHCPS_FCX_PAVO_TRK_MIN_R 4 80 TRK_MIN_R Track count minimum - read

SRXHCPS_FCX_PAVO_TRK_MAX_R 4 81 TRK_MAX_R Track count maximum - read

SRXHCPS_FCX_PAVO_TRK_MIN_W 4 82 TRK_MIN_W Track count minimum - write

SRXHCPS_FCX_PAVO_TRK_MAX_W 4 83 TRK_MAX_W Track count maximum - write

SRXHCPS_FCX_PAVO_IOP_LOW 8 84 IOP_LOW Less than F8 I/O priority

SRXHCPS_FCX_PAVO_IOP_F8 8 85 IOP_F8 F8 I/O priority

SRXHCPS_FCX_PAVO_IOP_F9 8 86 IOP_F9 F9 I/O priority

SRXHCPS_FCX_PAVO_IOP_FA 8 87 IOP_FA FA I/O priority

SRXHCPS_FCX_PAVO_IOP_FB 8 88 IOP_FB FB I/O priority

SRXHCPS_FCX_PAVO_IOP_FC 8 89 IOP_FC FC I/O priority

SRXHCPS_FCX_PAVO_IOP_FD 8 90 IOP_FD FD I/O priority

SRXHCPS_FCX_PAVO_IOP_FE 8 91 IOP_FE FE I/O priority

SRXHCPS_FCX_PAVO_IOP_FF 8 92 IOP_FF FF I/O priority

Table 25 Section 4 — PAV optimization active monitoring zHPF counters


SRXHCPS_FCX_PAVO 8 100 PAVO Optimized CPs

SRXHCPS_FCX_PAVO_RD 8 101 RD Optimized read CPs

SRXHCPS_FCX_PAVO_RD_ILRL 8 102 RD_ILRL Optimized read CPs containing ILRL

SRXHCPS_FCX_PAVO_WR 8 103 WR Optimized write CPs

SRXHCPS_FCX_PAVO_WR_ILRL 8 104 WR_ILRL Optimized write CPs containing ILRL

SRXHCPS_FCX_PAVO_ERROR 8 105 ERROR Count of optimized CPs completed in error

SMF recording 521


SRXHCPS_FCX_PAVO_NORMAL 8 106 NORMAL Count of optimized CPs completed normally

SRXHCPS_FCX_PAVO_REDRIVE 8 126 REDRIVE Count of optimized CPs redriven by zBoost PAV Optimizer

SRXHCPS_FCX_PAVO_STARTIO 8 107 STARTIO Count of CPs STARTIO issued i.e number of IORQs started or constituent I/Os

SRXHCPS_FCX_PAVO_BASE_IO 8 108 BASE_IO Constituent CPs started on base UCB

SRXHCPS_FCX_PAVO_BASE_DUP_IO 8 109 BASE_DUP_IO Constituent CPs started on the same base UCB for same owning IO

SRXHCPS_FCX_PAVO_ALIAS_IO 8 110 ALIAS_IO Constituent CPs started on alias UCB

SRXHCPS_FCX_PAVO_ALIAS_DUP_IO 8 111 ALIAS_DUP_IO Constituent CPs started on the same alias UCB for same owning IO

SRXHCPS_FCX_PAVO_SPLIT_MIN_R 4 112 SPLIT_MIN_R Split minimum - read

SRXHCPS_FCX_PAVO_SPLIT_MAX_R 4 113 SPLIT_MAX_R Split maximum - read

SRXHCPS_FCX_PAVO_SPLIT_MIN_W 4 114 SPLIT_MIN_W Split minimum - write

SRXHCPS_FCX_PAVO_SPLIT_MAX_W 4 115 SPLIT_MAX_W Split maximum - write

SRXHCPS_FCX_PAVO_ALIAS_MAX 4 116 ALIAS_MAX Maximum unique ALIAS used for same owning I/O

SRXHCPS_FCX_PAVO_ALIAS_DUP_MAX 4 117 ALIAS_DUP_MX

Maximum duplicate ALIAS used for same owning I/O

SRXHCPS_FCX_PAVO_BASE_MAX 4 118 BASE_MAX Maximum started on base for same owning I/O

SRXHCPS_FCX_PAVO_IORQ_ALC 8 119 IORQ_ALC Allocated IORQ

SRXHCPS_FCX_PAVO_IORQ_USE 4 120 IORQ_USE In-use IORQ

SRXHCPS_FCX_PAVO_IORQ_MAX 4 121 IORQ_MAX Maximum concurrent IORQ

SRXHCPS_FCX_PAVO_IO64_ALC 8 122 IO64_ALC Allocated IO64

SRXHCPS_FCX_PAVO_IO64_USE 4 123 IO64_USE In-use IO64

SRXHCPS_FCX_PAVO_IO64_MAX 4 124 IO64_MAX Maximum concurrent IO64

SRXHCPS_FCX_PAVO_ERP_REDRIVE 4 125 ERP_REDRIVE Total redrive count due to ERP

SRXHCPS_FCX_PAVO_ALIAS_MISS_IO 4 127 ALIAS_MISS_IO

Expected ALIAS I/O that was not driven to ALIAS devices. Reset in DEV and LCU when ALIAS IO is detected.

SRXHCPS_FCX_PAVO_ALIAS_MISS_TOD 8 128 ALIAS_MISS_TOD

TOD when ALIAS starvation first hit the MISS_IO_THRESH value. Only set in DEV and LCU entry.

SRXHCPS_FCX_PAVO_ALIAS_WARN_TOD 8 129 ALIAS_WARN_TOD

TOD when ALIAS starvation warning will be broadcast. Only set in LCU entry.

Table 25 Section 4 — PAV optimization active monitoring zHPF counters



Table 26 Section 5 — PAV optimization zHPF skip processing by parameters


SRXHCPS_FCX_PAVO_SKIP_RD 8 160 SKIP_RD Count of optimized CPs skipped due to READ not enabled

SRXHCPS_FCX_PAVO_SKIP_WR 8 161 SKIP_WR Count of optimized CPs skipped due to WRITE not enabled

SRXHCPS_FCX_PAVO_SKIP_MTR 8 162 SKIP_MTR Count of optimized CPs skipped due to not meeting minimum READ track count

SRXHCPS_FCX_PAVO_SKIP_MTW 8 163 SKIP_MTW Count of optimized CPs skipped due to not meeting minimum WRITE track count

SRXHCPS_FCX_PAVO_SKIP_IOPR 8 164 SKIP_IOPR Count of optimized CPs skipped due to READ I/O priority too low

SRXHCPS_FCX_PAVO_SKIP_IOPW 8 165 SKIP_IOPW Count of optimized CPs skipped due to WRITE I/O priority too low

SRXHCPS_FCX_PAVO_SKIP_JOBNR 8 166 SKIP_JOBNR Count of optimized CPs skipped due to READ started task name not matched

SRXHCPS_FCX_PAVO_SKIP_JOBNW 8 167 SKIP_JOBNW Count of optimized CPs skipped due to WRITE started task name not matched

SRXHCPS_FCX_PAVO_SKIP_QPG 4 168 SKIP_QPG Count of optimized CPs skipped due to reaching global quiesce point

SRXHCPS_FCX_PAVO_SKIP_QPD 4 169 SKIP_QPD Count of optimized CPs skipped due to reaching device quiesce point

SRXHCPS_FCX_PAVO_SKIP_QPL 4 170 SKIP_QPL Count of optimized CPs skipped due to reaching LCU quiesce point

SRXHCPS_FCX_PAVO_SKIP_CON 8 171 SKIP_CON Count of optimized CPs skipped due to consistency SUSPEND.

Table 27 Section 6 — PAV optimization zHPF skip processing


SRXHCPS_FCX_PAVO_SKIP_IORQ 4 200 SKIP_IORQ Count of optimized CPs skipped due IORQ build issue

SRXHCPS_FCX_PAVO_SKIP_IO64 4 201 SKIP_IO64 Count of optimized CPs skipped due 64 bit resource shortage

SRXHCPS_FCX_PAVO_SKIP_TIDA_R 4 202 SKIP_TIDA_R Count of optimized CPs skipped due TIDA resource shortage for READ

SRXHCPS_FCX_PAVO_SKIP_TIDA_W 4 203 SKIP_TIDA_W Count of optimized CPs skipped due TIDA resource shortage for WRITE

SRXHCPS_FCX_PAVO_SKIP_COB 4 204 SKIP_COB Count of optimized CPs skipped due COB area exhaustion

SRXHCPS_FCX_PAVO_SKIP_NS 8 205 SKIP_NS Count of optimized CPs skipped due unsupported DCW command

SRXHCPS_FCX_PAVO_SKIP_NSR 8 206 SKIP_NSR Count of optimized CPs skipped due unsupported READ

SMF recording 523


Note: _LOGREC fields are count events that are logged (to LOGREC). _EVENT fields count events that are not logged (to LOGREC), e.g. _LOGREC entries hit the logging thresholds in RXHCPS_FCX_PAVO_LOGREC_L or EVENT logging is not active.

SRXHCPS_FCX_PAVO_SKIP_NSW 8 207 SKIP_NSW Count of optimized CPs skipped due unsupported WRITE

SRXHCPS_FCX_PAVO_SKIP_ICR 8 208 SKIP_ICR Count of optimized CPs skipped due READ parameters incompatible (complex READ)

SRXHCPS_FCX_PAVO_SKIP_ICW 8 209 SKIP_ICW Count of optimized CPs skipped due WRITE parameters incompatible (complex WRITE)

SRXHCPS_FCX_PAVO_SKIP_ICG 8 210 SKIP_ICG Count of optimized CPs skipped due parameters incompatible (complex generic)

SRXHCPS_FCX_PAVO_SKIP_STR 8 211 SKIP_STR Count of optimized CPs skipped due single track READ

SRXHCPS_FCX_PAVO_SKIP_STW 8 212 SKIP_STW Count of optimized CPs skipped due single track WRITE

Table 27 Section 6 — PAV optimization zHPF skip processing

Table 28 Section 7 — PAV optimization logging event stats


SRXHCPS_FCX_PAVO_LOGREC 4 220 LOGREC Logged generic events

SRXHCPS_FCX_PAVO_EVENT 4 221 EVENT Not logged generic events

SRXHCPS_FCX_PAVO_LOGREC_R 4 222 LOGREC_R Logged read events

SRXHCPS_FCX_PAVO_EVENT_R 4 223 EVENT_R Not logged read events

SRXHCPS_FCX_PAVO_LOGREC_W 4 224 LOGREC_W Logged write events

SRXHCPS_FCX_PAVO_EVENT_W 4 225 EVENT_W Not logged write events

SRXHCPS_FCX_PAVO_LOGREC_P 4 226 LOGREC_P Logged events for permanent errors detected in build (no IO issued)

SRXHCPS_FCX_PAVO_LOGREC_PI 4 227 LOGREC_PI Logged events for permanent errors detected in build (IO issued)



SMF reporting utility

Use the SMF reporting utility provided with zBoost PAV Optimizer to produce a comma-separated values (.csv) file that contains information from zBoost PAV Optimizer SMF records. This file can be transferred to a Windows system using FTP and processed as a spreadsheet.

Note: “Output file format” on page 528 describes the format of the utility output file.

Run the utility as shown in “Sample JCL” on page 525. You can filter data to be extracted to the .csv file using control statements listed in “Control statements” on page 526.

Sample JCL//STEP1 EXEC PGM=IFASMFDP //DUMPIN DD DSN=SYS1.smfid.MAN1,DISP=SHR //DUMPOUT DD DSN=userid.SMF.lpar.@yymmdd, // UNIT=SYSALLDA,SPACE=(CYL,(5,5)), // DCB=(RECFM=VBS,LRECL=27994,BLKSIZE=27998), // DISP=(NEW,CATLG) //SYSPRINT DD SYSOUT=* //SYSIN DD * INDD(DUMPIN,OPTIONS(DUMP)) OUTDD(DUMPOUT,TYPE(203)) /* //GENER EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=userid.SMF.lpar.@yymmdd, // DCB=(RECFM=VBS,LRECL=27994,BLKSIZE=27998), // DISP=SHR //SYSUT2 DD DSN=&&SMF, // DCB=(RECFM=V,LRECL=27994), // UNIT=SYSALLDA,SPACE=(CYL,(20,10)), // DISP=(,PASS) //SYSIN DD DUMMY //* //ESFHSMFV EXEC PGM=ESFHSMFV,PARM=DIFF //STEPLIB DD DSN=userid.LINKLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=&&SMF,DISP=(OLD,DELETE) //SYSUT2 DD [email protected], // DCB=(RECFM=FB,LRECL=1440,BLKSIZE=14400), // UNIT=SYSALLDA,SPACE=(CYL,(20,10)), // DISP=(,CATLG) //SYSIN DD * Optional control statements/*

SMF recording 525


Control statements

Note: All control statements are optional.

DIFF Specifies whether each row should represent the accumulated data or the difference between the current and prior interval values.

The syntax is as follows:

DIFF=YES|NO

Where:

NO

(Default) Each row represents the accumulated data.

YES

Each row represents the difference between the current and prior interval values.

Note: The DIFF parameter overrides PARM=DIFF if specified.

RECID Specifies the SMF record ID.


RECID=record_id

Where:

record_id

The ID of the SMF record. The default value is 203.

The record_id should agree with the value of the SCF.DEV.OPTIMIZE.SMF.RECID initialization parameter described on page 92.

SCFID Limits processing to input collected by a specific SCF instance, if the input was collected by more than one SCF instance.

If not specified, the first encountered SCF instance is selected for processing, with the SCF instance value indicated in the output.


SCFID=scfid

Where:

scfid

The ID of the SCF subsystem.

SECTIONS Lists SMF record sections to be extracted to the .csv file.


SECTIONS=section-list



Where:

section-list

Specify one or more of the following values separated by commas:

ALL

(Default) Includes all reported items.

BASIC

Basic zHPF counts.

CONFIG

The configuration values.

EVENTS

Counts of various events encountered.

MONACT

I/Os optimized in Active mode.

MONPASS

I/Os examined in Passive mode.

SKIPACT

I/Os not optimized for various reasons.

SKIPPASS

I/Os excluded for various reasons in Passive mode.

SMFSID Limits the reported data to a specific LPAR when the input stream contains data from more than one LPAR.

If not specified, the first encountered LPAR is selected for reporting, with the LPAR value indicated in the output.


SMFSID=smfid

TYPE Determines the type of SMF records to be extracted to the .csv file.

Note: “SMF record types” on page 516 describes the SMF record types.


TYPE={STATS|stats-type-list}|JOBS|EVENTS

Where:

EVENTS

Extracts and formats only EVENTS records.

JOBS

Extracts and formats only JOBS records.

SMF recording 527


STATS

Extracts and formats only STATS records of all the three subtypes (GLOBAL, SSID, DEVICE).

stats-type-list

Extracts and formats only STATS records of the specified subtype or subtypes. Possible values are:

GLOBAL

Selects global records.

SSID

Selects SSID-specific records.

DEVICE

Selects device-specific records.

You can specify any combination of GLOBAL, SSID, and DEVICE separated by commas.

IMPORTANT

You can only specify STATS (or any combination of the STATS subtypes), or JOBS, or EVENTS. When attempting to specify two of the major types together, a message is issued and only STATS, JOBS, or EVENTS are produced in that priority order.

Output file formatIn the .csv file produced by the SMF reporting utility, each row contains the values for a particular record with the column cells containing the individual data items.

◆ For STATS records, each row represents the content of one SMF record, all fields either for global statistics, an SSID, or a device for one SMF interval.

◆ For JOBS records, after the time stamp and SMFID columns, the columns correspond to the defined started task and prefix names and the rows give the counts recorded in each interval record. For each period of consistent JOBNAME and JOBPREFIX values, a heading row precedes the data with JOBPREFIX values distinguished by having an asterisk appended.

◆ For EVENTS records, each row contains the data for one event type encountered for each SMF interval.

Tables in “STATS record fields” on page 519 show correspondence between the .csv file column headings and SMF record fields.


CHAPTER 12EMC ChangeTracker for z/OS

This chapter describes the EMC ChangeTracker utility for z/OS.

◆ Introduction to the EMC ChangeTracker utility........................................................ 530◆ ChangeTracker Collector ........................................................................................ 532◆ ChangeTracker Collector parameters...................................................................... 533◆ ChangeTracker Collector commands ...................................................................... 541◆ Storage estimates for ChangeTracker Collector disk output .................................... 546◆ ChangeTracker Reporter ........................................................................................ 547◆ ChangeTracker Reporter parameters ...................................................................... 548◆ Reports ................................................................................................................. 557◆ Interval statistics file............................................................................................. 562◆ EMC ChangeTracker error and event messages ...................................................... 563

EMC ChangeTracker for z/OS 529

EMC ChangeTracker for z/OS

Introduction to the EMC ChangeTracker utilityThe EMC ChangeTracker utility allows you to monitor and update activity on Symmetrix devices. ChangeTracker enables you to determine the number of tracks that have been accessed during the interval since the last monitoring.

Having accurate track change information is important when you size SRDF connectivity requirements. You need to know the speed and number of connections you require from your service provider for an effective SRDF implementation. ChangeTracker helps you determine this important information.

Having accurate track change information is also important in determining TimeFinder resynchronization times. You can use track changes as information to help you set the time needed for various synchronizing and resynchronizing activities to conclude.

ChangeTracker is an enterprise solution. With ChangeTracker, you can specify gatekeeper and Symmetrix device numbers. The devices that the device numbers refer to can be in either FBA or CKD format. ChangeTracker can observe both open systems and mainframe volumes, and also allows you to track changes to offline devices.

ChangeTracker consists of two components:

◆ The ChangeTracker Collector gathers update activity statistics

◆ The ChangeTracker Reporter analyzes the data and formats the update activity data into useful reports

ChangeTracker Collector

The ChangeTracker Collector runs first. ChangeTracker Collector runs as either as a started task or as a long running job. ChangeTracker Collector uses input parameters to determine which devices to monitor. Then, it writes the data it collects to a z/OS dataset.

At specified intervals, ChangeTracker Collector determines which tracks on the specified devices have been accessed. ChangeTracker Collector then saves that track information for use later by the ChangeTracker Reporter.

The ChangeTracker Collector works using Symmetrix-specific features. It gathers information about accessed tracks internally by the Symmetrix system, using Symmetrix device numbers.

With Enginuity level 5875 or higher, ChangeTracker Collector uses the following modes for gathering information:

◆ Write mode (default) — collects data on all write updates to the device.

◆ Read mode — collects data on read operations.

◆ Read/write mode — collects data on both read and write operations.

◆ Read-miss mode — collects reads that are not from cache.

Note: With Enginuity levels lower than 5875, ChangeTracker Collector only collects data on writes.

Note that a device can only be collected by one collector at a time.



Any action that swaps logical devices invalidates the relationship of logical address and Symmetrix device number. This results in messages CTRK011E and CTRK012E. When diagnosing this error, determine if a swap action was performed on the CUU identified in the messages.

Note: The EMC Mainframe Enablers Message Guide describes CTRK011E and CGRK012E.

ChangeTracker Reporter

Using the data created by the ChangeTracker Collector, the ChangeTracker Reporter presents the data in a meaningful format. ChangeTracker Reporter can generate reports showing the track accesses over a period of time on:

◆ The Symmetrix level

◆ The volume level

◆ The dataset level

You may find this information useful for making decisions regarding system configuration data throughput.

Note: Read/write mode cannot be reported separately by reads and writes.

Introduction to the EMC ChangeTracker utility 531


ChangeTracker CollectorChangeTracker Collector gathers track information from Symmetrix devices. ChangeTracker Collector runs as a started task or long-running job over a period of time, gathering data at specified intervals in log datasets.

The collected data shows which tracks were accessed during the interval since the last collection. ChangeTracker Collector then writes the change data to a mainframe dataset for later use by the ChangeTracker Reporter.

Note: ChangeTracker Collector does not collect VTOC information for any offline, remote, or devices that are only identified by local or remote Symmetrix device numbers (LCL (cuu, symdev#) and RMT (cuu, symdev#)). In such cases, no dataset level reports are possible.

The log dataset name is in the following format:

HLQ.CHGTRKER.Dyyyyddd.LOG#nnnn

where:

HLQ

Indicates the high-level qualifier under which the log dataset is stored.

CHGTRKER

Is the string CHGTRKER.

yyyyddd

Is the Julian date with a four-digit year.

nnnn

Is a sequence number.

Each time you close one log dataset and open another, ChangeTracker increments the sequence number so that the new log dataset receives a number one larger than the number assigned to the now closed log dataset.

You can use the LOG# command to assign a specific sequence number to a log dataset.

Note: “LOG# (LOGNUM)” on page 537 describes this command.

The collected data shows which tracks were accessed during the last time interval. ChangeTracker Collector then writes the changed or accessed meta data to a mainframe dataset for later use by ChangeTracker Reporter.



JCL

The following example JCL can run the ChangeTracker Collector.

Note: Refer to the SAMPLIB member included with your kit for the latest sample. All SAMPLIB members for ResourcePak Base are distributed in the MFEvrm SAMPLIB (SMP/E DDNAME: EMCSAMP).

BROWSE DSN=DS-PREFIX.MFEvrm.SAMPLIB(EMCCTR1) // JOBCARD //* //* SAMPLE CHANGETRACKER COLLECTER JCL //* //CTRKCOLL EXEC PGM=CTRKCOLL //STEPLIB DD DSN=DS-PREFIX.LINKLIB,DISP=SHR //SYSUDUMP DD SYSOUT=X //CONFIG DD * DEVICE_LIST=DEV#-DEV# DEVICE_LIST=VOLSER,VOLSER* CYCLE=0 HLQ=EMCCTR PALLOC=5 SALLOC=5 VOLSER=VOLID LOG#=300 //

IMPORTANT

The z/OS load library must be an APF-authorized dataset.

where:

DS_PREFIX

Is the dataset name prefix you used to install the EMC Mainframe Enablers.

ChangeTracker Collector parametersTo run, ChangeTracker Collector requires the following information:

◆ The devices for which to collect data and the collection mode

◆ How often to collect the data

◆ Where to write the data

You supply this input through configuration parameters read from the CONFIG DD statement. The configuration parameters are in the following format:

Keyword = value

◆ The keyword must begin in column one.

◆ An asterisk in column one denotes a comment line.

◆ The keyword statements should be saved as a member of a parameter library which is pointed to by the CONFIG DD statement of the ChangeTracker started task JCL.

The following sections describe the ChangeTracker Collector configuration parameters.

ChangeTracker Collector parameters 533


CYCLE

Description

Specifies how often ChangeTracker Collector should collect data.

Syntax

CYCLE=nn[,SEC|,MIN|,HR]

where:

nn

Specifies how often (in seconds, minutes, or hours) ChangeTracker Collector should collect data.

,SEC|,MIN|,HR

Indicates whether the number specified by nn represents seconds, minutes, or hours. If you do not specify a value, the unit for nn defaults to minutes (MIN).

Note: The maximum cycle time is two hours (120 minutes, 7200 seconds). Cycle times shorter than one minute are not recommended for multiple devices over extended periods of time. Recommended cycle times range from three to ten minutes. Allowing a cycle time of zero results in 30 second cycles for compatibility with prior versions of ChangeTracker.

Example

DEVICE_LIST

Description

Defines all the devices from which to collect statistics. There may be one or more DEVICE_LIST parameters in a configuration file. The parameter values for this statement can consist of any of the following:

◆ Symmetrix device numbers

◆ A range of Symmetrix device numbers

◆ Gatekeepers

◆ z/OS volsers

◆ Mainframe ccuu

◆ A range of ccuus

Values are separated by commas and ranges specified by hyphens; for example, 280-28F. You can mix device numbers and volsers in the same statement.

To specify a cycle time of: type:

10 minutes CYCLE=10

1 hour CYCLE=1,HR

90 seconds CYCLE=90,SEC



Local entry syntax

For a local entry, a DEVICE_LIST entry has the following syntax:

LCL(cuu,dev#1[-dev#2][,...])where:

cuu

When you specify LCL, this parameter represents your gatekeeper device.

dev#1

Specifies the lower (or only) Symmetrix unit number on the Symmetrix controller. Unit numbers are specified in hexadecimal.

dev#2

Specifies the upper Symmetrix unit number on the Symmetrix controller.

Local entry examples

DEVICE_LIST=200-27F,290,B000-B007DEVICE_LIST=900,901,90A,DB2001,DB2002

In addition to device numbers and volsers, you can also specify a volser mask. The volser mask designates that any device with a volser that matches the significant characters in the mask should be included.

For example, the following adds all the devices whose first three characters begin with EMC:

DEVICE_LIST=EMC*

The mask character (*) can be used after any number of characters.

For example:

DEVICE_LIST=X*,QW*,EMC*,ABCO*,CDE01*

Like the other DEVICE_LIST parameters, volser wildcards can be mixed with the other device specifiers.

For example:

DEVICE_LIST=200,300-310,EMC001,QWS*,APX9*

Remote entry syntax

For remote support through an RDF Symmetrix controller, a DEVICE_LIST entry has the following syntax:

RMT(cuu,dev#1[-dev#2][,rdfgroup])

where:

cuu

Specifies the channel address of an attached Symmetrix system. When you specify RMT, this parameter represents your gatekeeper device.



dev#1

Specifies the lower (or only) Symmetrix unit number on the remote Symmetrix controller. Unit numbers are specified in hexadecimal.

dev#2

Specifies the upper Symmetrix unit number on the remote Symmetrix controller.

rdfgroup

Specifies the remote SRDF group or remote multi-hop routing. Each entry is two hexadecimal digits separated by a period. If you do not specify rdfgroup, the default path for the specified Symmetrix cuu is located and printed on the system log.

For ChangeTracker Reporter, rdfgroup is a required field if devices are selected with the RMT(cuu... parameter. Remote devices may be selected by Symmetrix serial number as well as with the RMT(cuu... parameter.

Remote entry examples

The following instructs ChangeTracker to collect statistics on the device 4B7 on the remote controller. Channel programs access cuu=3024 on the local system to find the default SRDF group.

RMT(3024,4B7)

In the following example, the Symmetrix at cuu 1EF0 is used to gain access to devices 0300 through 03FF using the multi hop path(s) 00, 07, and 04 respectively:

RMT(1EF0,0300-03FF,00.07.04)

HLQ

Description

HLQ specifies the first qualifier for the log dataset that will be dynamically allocated and contain the ChangeTracker data.

Note: “ChangeTracker Collector” on page 530 describes the ChangeTracker log dataset.

Syntax

HLQ=HLQ_name

where:

HLQ_name

The first (high level) qualifier for the log dataset.

Example

HLQ=APX



LOG# (LOGNUM)

Description

LOG# (LOGNUM) specifies the starting dataset sequence number that will be used when constructing a dataset name for the ChangeTracker dataset. Each subsequent allocation of a new ChangeTracker dataset increases the sequence number by one.

Syntax

LOG#|LOGNUM=number

where:

number

The starting dataset sequence number. If you do not specify LOG#, ChangeTracker uses the default value of one (1).

Example

LOG#=10

MODE

Description

MODE specifies the operation type for which the ChangeTracker Collector will collect data. Note that a device can only be collected by one collector at a time.

Note: Enginuity level 5875 or higher is required for use with the MODE parameter.

Syntax

MODE=WRITE (W) MODE=READ (R)MODE=READ/WRITE (RW)MODE=READ-MISS (RM)

Write mode is the default setting. Write mode will be defaulted for all controllers prior to Enginuity level 5875.

Example

MODE=W



PALLOC

Description

PALLOC sets a number that specifies the primary space allocation of the ChangeTracker dataset, in cylinders.

Syntax

PALLOC=allocation

where:

allocation

The primary space allocation of the ChangeTracker dataset in cylinders. If you do not specify a PALLOC value, ChangeTracker uses a default PALLOC value of 20.

Example

PALLOC=20

SALLOC

Description

SALLOC sets a number that specifies the secondary space allocation of the ChangeTracker dataset, in cylinders.

Syntax

SALLOC=allocation

where:

allocation

The secondary space allocation of the ChangeTracker dataset in cylinders. If you do not specify a SALLOC value, ChangeTracker uses a default value of ten (10).

Example

SALLOC=10

SMS_GROUP

Description

SMS_GROUP specifies that ChangeTracker statistics should be collected from all devices belonging to the specified SMS group.

Syntax

SMS_GROUP=SMSGROUP

where:



SMSGROUP

The SMS group from which you want to collect statistics.

Example

SMS_GROUP=SMSTEST

VOLSER|VOLUME

Description

VOLSER|VOLUME specifies the volser where the ChangeTracker dataset will be allocated.

Syntax

VOLSER|VOLUME = volser

where:

volser

The volser where the ChangeTracker dataset will be allocated.

Example

VOLSER=TJX001

VTOC

Description

VTOC specifies when (if at all) to dump the VTOC to the ChangeTracker Collector dataset. A dataset report by the ChangeTracker Reporter requires knowledge of each volume’s datasets. Adding VTOC data to the Collector dataset allows the Reporter to give a dataset report.


Note: “Dataset summary report” on page 561 describes how to dump VTOC data.

Syntax

VTOC=param

where:

param

One of the following:

START

Dump the VTOC at Collector start-up.



STOP

Dump the VTOC when the Collector shuts down.

BOTH

(Default) Dump the VTOC at start-up and shut down.

NONE

Do not dump the VTOC during this Collector run.

ONLY

Dump the VTOC to the Collector dataset, and then terminate.

Example

VTOC=STOP

Developing a CONFIG file

The following is a sample of a CONFIG file:

DEVICE_LIST=100-11F,8800-88FFDEVICE_LIST=PLO1*,900,910CYCLE=10HLQ=TRVWMODE=WPALLOC=50SALLOC=20VOLSER=EMC200

This CONFIG file specifies the following:

◆ ChangeTracker collects data from all the specified devices six times every hour, or every ten minutes.

◆ The first dataset to be allocated will have the dataset name of TRVW.CHGTRKER.D2009821.LOG#0001, assuming it starts running on August 21, 2009.

◆ The dataset will be allocated on volser EMC200.

◆ The dataset will have a primary allocation of 50 cylinders.

◆ The dataset will have a secondary allocation of 20 cylinders.



ChangeTracker Collector commandsThe interface to the ChangeTracker Collector uses the z/OS MODIFY and STOP commands: F and P respectively.

To end the ChangeTracker Collector job, issue the STOP command with the jobname. For example, to stop a ChangeTracker job with the jobname EMCCTRK, issue:

P EMCCTRK

The ChangeTracker task also contains display and control commands that are issued through the MODIFY command in the form:

F EMCCTRK,command parameter 1 [,parameter 2 [,parameter n]]

where:

command

A ChangeTracker Collector command.

parameter 1 [,parameter 2 [,parameter n]]

One or more command parameters.

Note: “ChangeTracker Collector parameters” on page 533 describes the valid ChangeTracker Collector parameters.

The following sections describe the ChangeTracker Collector commands.

DISPLAY ALL

Description

The DISPLAY ALL command displays a summary listing of the collector attributes.

Syntax

DIS[PLAY] ALL

Example

DIS ALLCVT @ 16400F08 DEV @ 16400EB0 # DEVS = 2 PALLOC = 5 SALLOC = 5 VOL = UTG00C CYCLE = 600 SECONDS, # CYCLES = 1, MODE = WLOG DSN = ARXX2.CHGTRKER.D2003255.LOG#0100

ChangeTracker Collector commands 541


DISPLAY CYCLE

Description

The DISPLAY CYCLE command displays the current cycle time interval. The maximum CYCLE time is two hours.

Note: “CYCLE” on page 534 how to specify the CYCLE time.

Syntax

DIS[PLAY] CYC[LE]

Example

DIS CYCLECYCLE = 5 MIN, # CYCLES = 8, MODE = W

DISPLAY DEVICE

Description

The DISPLAY DEVICE command displays device information about the ChangeTracker Collector task on the operator console.

Syntax

DIS[PLAY] DEV[ICE] [CUU|VOLSER]

where:

No device specification

Displays all the devices that the ChangeTracker task is collecting data for. The display shows each device with its CUU number and volser.

CUU|VOLSER

The CUU or volser of the device you want to display.

Examples

Without a device specification, ChangeTracker Collector displays information about all devices:

DIS DEV 022A SYB02A 022B SYB02B 022C SYB02C 022D SYB02D 022E SYB02E 022F SYB02F 0230 SYB030 0231 SYB031 0232 SYB032 0233 SYB033 0234 SYB034 0235 SYB035 0251 SYB041 0252 SYB042 0253 SYB043 0254 SYB044 0255 SYB045 0256 SYB046 0257 SYB047 0258 SYB048 0259 SYB049 025A SYB04A 025B SYB04B 025C SYB04C



When you specify a device, it may be either an mainframe cuu number or a volser. The command:

DIS DEV 233

or:

DIS DEV SYB033

produces the following output:

DISPLAY LOG

Description

The DISPLAY LOG command displays the current log sequence number.

Syntax

DIS[PLAY] LOG

Example

DIS LOGLOG DSN = MFLYNN1.CHGTRKER.D1998364.LOG#0013

HELP

Description

The HELP command displays short explanations for each command.

Syntax

HELP

LOG#

Description

The LOG# command resets the log sequence number for the ChangeTracker dataset. The next ChangeTracker dataset gets allocated using the specified number n when forming the dataset name.

Syntax

LOG# n

LOGNum n

where:

DIS DEV 233 CUU=0233 VOL=SYB033 #CYLS=1113 SYMMDEV#=0033 SER#=000182600427 UCB @ 00F1A850 CTLR=3990-E9 DEVICE=3390-02



nThe number you want to assign.

Comments

The next time a ChangeTracker dataset is allocated, either by a LOGSwap command or otherwise, it has LOG#0200 as the last qualifier in the dataset name.

Example

LOG# 200

LOGSWAP

Description

The LOGSWAP command causes the current ChangeTracker Collector dataset to be closed and a new one to be allocated.

Syntax

LOGS[WAP]

Comments

The new ChangeTracker Collector dataset will have its log sequence number incremented so that the sequence number is one more than the file that was just closed.

When LOGSWAP is issued, the VTOCs are extracted before the logs are swapped unless VTOC=NONE is specified.

STOP

Description

The STOP command terminates the ChangeTracker Collector task.

Syntax

STOP

Comments

You can also use the z/OS STOP (P) command to terminate the ChangeTracker Collector task.



VOLSER

Description

Changes the volume used to allocate the ChangeTracker Collector log dataset.

Syntax

VOLSER volser

Where:

volser

The volume serial number.



Storage estimates for ChangeTracker Collector disk output Rather than saving the status of all tracks during each cycle, ChangeTracker Collector only saves the identity of tracks that have been accessed. Therefore, the amount of disk storage needed is dependant on the number of tracks that were altered during each cycle.

While this number varies, EMC estimates that the amount written for each disk volume to be less than 250-bytes per cycle. You could compute necessary storage as follows:

Storage = 250 * device_count * minutes / cycle_time

For example, if data were to be collected for 64 devices for 12 hours (720 minutes) with a cycle time of two minutes, the estimated amount of disk storage would be (250 * 64 * 720) / 2. This is about six million bytes of storage (about 115 tracks on a 3390 device).



ChangeTracker ReporterAfter the ChangeTracker Collector has finished gathering statistics for the devices, you can use the ChangeTracker Reporter to analyze these statistics and produce reports showing track usage:

◆ On a Symmetrix level◆ On a volume level◆ On a dataset level

The types of reports desired and the parameters used for the reports are supplied through keyword parameters in data read from the CONFIG DD statement.

Dumping VTOCsIn the ChangeTracker Collector, the process of dumping the online VTOCs for dataset reporting is optional. You can dump VTOCs at a later time when problem volumes have been identified and the VTOC information concatenated with the Change Track information.


JCLThe following sample JCL can run the ChangeTracker Reporter:


BROWSE DSN=DS-PREFIX.MFEvrm.SAMPLIB(EMCCTR2)

// JOBCARD //* //* SAMPLE CHANGETRACKER REPORTING JCL //* //CTRKREPT EXEC PGM=CTRKREPT //STEPLIB DD DSN=DS-PREFIX.LINKLIB,DISP=SHR //ISTATS DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SORTIN DD DISP=SHR,DSN=EMCCTR.CHGTRKER.DXXXXXXX.LOG##### //SORTOUT DD DSN=&&SORTWK,DISP=(,PASS), // UNIT=SYSDA,SPACE=(CYL,(50,10)) //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //CONFIG DD * DEVICE_LIST=DEV#=DEV# DEVICE_LIST=VOLSER,VOLSER* SYM_SERIAL=############ SMS_GROUP=######## RA_CNT=4 RA_KBS=1000 *RESYNCH_TIME=90 REPORTS=SYMMETRIX,VOLSER,DATASET DATE=(11152000,11152000) TOD=(1300,1359) //* where:

DS_PREFIXIs the dataset name prefix you used to install the EMC Mainframe Enablers.

ChangeTracker Reporter 547


ChangeTracker Reporter parametersTo run, the ChangeTracker Reporter requires the following parameter types:

◆ Device parameters

To select devices on which to report, use one or more of the following parameters:

DEVICE_LISTSMS_GROUPSYM_SERIAL

Any parameters values you specify are reflected in the echo of the control cards at the beginning of a report.

Note: If none of these parameters are present, the ChangeTracker Reporter uses all data from the ChangeTracker Collector.

◆ Mode parameter (requires Enginuity level 5875 or higher)

◆ Time and calculation parameters

◆ Report specification parameters

As with the ChangeTracker Collector, you supply input through keyword parameters in data read from the CONFIG DD statement. The keyword parameters must be in the following format:

keyword = value

The keyword must begin in column one.

An asterisk in column one denotes a comment line.

The keyword statements should be saved as a member of a parameter library which is pointed to by the CONFIG DD statement of the ChangeTracker started task JCL.

The following sections describe the ChangeTracker Reporter parameters:

DATE

Description

DATE specifies the days on which to include statistics for the reports.

Syntax

DATE=(mmddyyyy,mmddyyyy) or (mmddyyyy-mmddyyyy)

where:

mmddyyyy,mmddyyyy (or mmddyyyy-mmddyyyy)

Designate the beginning and end of the date span for the report. If you specify only one date, that date is used for both the beginning and end date; that is, data samples only from that date are included.



CommentsThe time parameters specify the time period during which you want to collect data. You can report on any time period within that collection period by using the DATE and TOD keywords.

DEVICE_LIST (syntax for ccuu and volser)

Description

DEVICE_LIST defines all the devices from which to report statistics after collection. There may be one or more DEVICE_LIST parameters in a configuration file.

Syntax

DEVICE_LIST=device spec[, device spec[,...]]

where:

device spec

Specifies the device or devices from which to report statistics after collection. A device specification can consist of:

• Mainframe ccuu

• A range of ccuus

• z/OS volsers

Values are separated by commas and ranges are specified by hyphens. For example, 1280-128F. You may intersperse device numbers and volsers in the same statement.

For example:

DEVICE_LIST=1200-127F,3290,B000-B007DEVICE_LIST=900,901,90A,DB2001,DB2002

In addition to device numbers and volsers, a volser mask can be specified, designating that any device with a volser that matches the significant characters in the mask should be included.

Examples

The following adds all the devices whose first three characters begin with EMC:

DEVICE_LIST=EMC*

The mask character (*) can be used after any number of characters, for example:

DEVICE_LIST=X*,QW*,EMC*,ABCO*,CDE01*

Like the other DEVICE_LIST parameters, volser wildcards can be mixed with the other device specifiers, for example:

DEVICE_LIST=200,300-310,EMC001,QWS*,APX9*

ChangeTracker Reporter parameters 549


DEVICE_LIST (syntax for Symmetrix device numbers)

Description

DEVICE_LIST defines all the devices from which to report statistics after collection. There may be one or more DEVICE_LIST parameters in a configuration file. The parameter values for this statement can consist of any of the following:

◆ Symmetrix device numbers

◆ A range of Symmetrix device numbers

◆ Gatekeepers

Values are separated by commas and ranges specified by hyphens; for example, 280-28F.

Local entry syntax

For a local entry, a DEVICE_LIST entry has the following syntax:

LCL(cuu,dev#1[-dev#2][,...])where:

cuuWhen you specify LCL, this parameter represents your gatekeeper device.

dev#1 Specifies the lower (or only) Symmetrix unit number on the Symmetrix controller. Unit numbers are specified in hexadecimal.

dev#2 Specifies the upper Symmetrix unit number on the Symmetrix controller.

Remote entry syntax

For remote support through an RDF Symmetrix controller, a DEVICE_LIST entry has the following syntax:

RMT(cuu,dev#1[-dev#2])

where:

cuuSpecifies the channel address of an attached Symmetrix system. When you specify RMT, this parameter represents your gatekeeper device.

dev#1 Specifies the lower (or only) Symmetrix unit number on the remote Symmetrix controller. Unit numbers are specified in hexadecimal.

dev#2 Specifies the upper Symmetrix unit number on the remote Symmetrix controller.

Examples

The following example instructs ChangeTracker to collect statistics on the device 4B7 on the remote controller. Channel programs access cuu=3024 on the local system to find the default SRDF group.

RMT(3024,4B7)



In the following example, the Symmetrix system at cuu 1EF0 is used to gain access to devices 0300 through 03FF on the remote controller.

RMT(1EF0,0300-03FF)

INTERVAL

Description

Specifies the interval to be used for interval statistics (defined in “Interval statistics file” on page 562).

Syntax

INTERVAL=nn[,MIN|,HR[,SEC]]

where:

nn

Specifies the interval for interval statistics. If not specified, INTERVAL defaults to 60 minutes.

,MIN|,HR|,SEC

Indicates whether the number specified by nn represents minutes (MIN), hours (HR), or seconds. If not specified, nn defaults to minutes.

Example

The INTERVAL time should be a multiple of the CYCLE time used by the ChangeTracker Collector. Otherwise, the interval statistics may be skewed. For example, if you specify CYCLE=40 (minutes) for the Collector and INTERVAL=60 for the ChangeTracker Reporter, some intervals would have two cycles and some intervals would only have one cycle. Recommended interval times are 1, 2, 4, or 8 hours.

Note: “CYCLE” on page 534 presents information about the Collector CYCLE parameter.

To specify an interval of: type:

30 minutes INTERVAL=30

2 hours INTERVAL=2,HRS



MODE

Description

MODE specifies the type of reports that will be generated for the data gathered by the ChangeTracker Collector.

Note: Any data collected that is not equal to the specified MODE will be bypassed.

Syntax

MODE=WRITE (W) MODE=READ (R)MODE=READ/WRITE (RW)MODE=READ-MISS (RM)

Write mode is the default setting.

Example

MODE=W

RA_COUNT

Description

RA_COUNT specifies the number of Remote Adapters (RA) on the Symmetrix system.

Syntax

RA_COUNT=number

where:

number

Indicates the number of remote adapters on the Symmetrix system.

Comments

The calculation parameters, RA_COUNT, RA_KBS and RESYNCH_TIME, assist in configuring an RDF environment. After you specify two of these keywords, the ChangeTracker Reporter calculates the third and displays the results in the Symmetrix summary report.

Example

RA_COUNT=2

RA_KBS

Description

RA_KBS specifies the speed, in kilobytes per second, of the communications link between the local RA and the remote RA.

A typical value for this parameter ranges from 512 to 8000 KB per second.



Syntax

RA_KBS=kbs_speed

where:

kbs_speed

Indicates the speed of the communications line.

Comments


Example

RA_KBS=1000

REPORTS

Description

REPORTS specifies the reports that are to be generated. You can specify any combination of the SYMMETRIX, VOLUME, or DATASET report types.

Syntax

REPORTS=SYMMETRIX,VOLUME,DATASET,SKIP_ZERO

where:

SYMMETRIX

Shows data for each Symmetrix controller.

VOLUME

Breaks the Symmetrix summary report down into individual volumes, showing the changes made to each volume.

DATASET

Breaks each volume down to all its datasets and shows the number of changes to each dataset.

SKIP_ZERO

Specifies to bypass printing lines that do not have any tracks accessed on the dataset and volume reports.

Example

REPORTS=DATASET,SKIP_ZERO,SYMMETRIX



RESYNCH_TIME

Description

RESYNCH_TIME specifies the time requirement for devices to resynchronize after an outage.

Syntax

RESYNCH_TIME=hh:mmRESYNCH_TIME=mmmm

where:

hhIndicates the hours.

mmIndicates the minutes. If there is no colon present, the Reporter assumes the time is in minutes.

Comments


Examples

RESYNCH_TIME=2:30RESYNCH_TIME=120

Suppose a site has a business requirement mandating that a resynchronization should take no more than two hours and a user wants to configure its RDF environment to satisfy that requirement. In addition, suppose that the site currently has one RA and wants to determine if that is adequate.

When you specify RESYNCH_TIME and RA_COUNT, the ChangeTracker Reporter calculates the speed of the telecommunications lines required to meet those objectives and displays it in the Symmetrix summary report.

RESYNCH_TIME=2:00RA_COUNT=1

Suppose the speed of the telecommunications lines is 1000 and the site now has two RAs. The user can utilize this information to determine the time necessary for resynchronization.

R_KBS=1000RA_COUNT=2



SMS_GROUP

Description

SMS_GROUP specifies that ChangeTracker reports should include data from all devices belonging to the specified SMS group.

Syntax

SMS_GROUP=group

where:

group

Specifies the SMS group whose devices you want to include.

Example

SMS_GROUP=SMSTEST

SYM_SERIAL

Description

SYM_SERIAL specifies that reports should include data from the specified Symmetrix controller. Only one SYM_SERIAL keyword is allowed.

Syntax

SYM_SERIAL=serial_no[,serial_no[,....]]

where:

serial_no

Specifies the serial number of the Symmetrix controller. The serial number is a 12-digit number that you can obtain from the Symmetrix summary report. To specify multiple serial numbers on the same line, use a comma to separate the serial numbers; for example:

SYM_SERIAL=001122334455,554433221100

Example

SYM_SERIAL=000182600427



TOD

Description

Specifies the time of day for which to include statistics for the reports.

Syntax

TOD=(hhmm,hhmm) or (hhmm-hhmm)[,BOTH]

where:

hhmm

Is the time in hours and minutes that designates the beginning and end of the time span for the report.

BOTH

Is a literal that only has meaning if you specify both TOD and DATE. DATE and TOD are treated as an AND condition. That is, the Reporter only select records if both DATE and TOD conditions are satisfied.

CommentsThe time parameters specify the time period during which you want to collect data. You can report on any time period within that collection period by using the DATE and TOD keywords.

Example

In the following example, only records between 10:00 and 14:00 on the specified dates (03-February-2008 through 07-February-2008) will be selected. A record written at 4:30 on 05-February-2008 will not be selected.

DATE=(02032008,02072008)TOD=(1000,1400)

If the BOTH option was specified, as in the following:

DATE=(02032008,02072008)TOD=(1000,1400),BOTH

then both the DATE and TOD parameters will be considered as a starting date/time and an ending date/time, which means a record written at 04:30 on 05-February-2008 will be selected.



ReportsThe ChangeTracker Reporter produces reports from the data gathered by the ChangeTracker Collector. The following types of reports are available:

◆ Summary report

◆ Symmetrix summary report

◆ Volume summary report

◆ Dataset report

Report parameters

The REPORTS parameter specifies the reports that are to be generated. There are four options:

◆ Symmetrix summary report — This short report shows data for each Symmetrix controller.

◆ Volume summary report — This report breaks the Symmetrix summary report down into individual volumes, showing the changes made to each volume.

◆ Dataset summary report — This report breaks each volume down to all its datasets and shows the number of changes to each dataset. Dataset summary requires VTOC information which must be dumped with the ChangeTracker Collector, VTOC parameter.

◆ SKIP_ZERO — This option specifies to bypass printing lines that do not have any tracks accessed on the dataset and volume reports.

For example:

REPORTS=SYMMETRIX,VOLUME,SKIP_ZERO

Summary report

The Summary report is always produced and contains:

◆ Collector summary

◆ Reporter summary

Collector summary

The Collector summary shows details about the data in the ChangeTracker dataset generated by the Collector including the time frame, number of cycles, and cycle time.

A sample Collector summary is shown below:

LPAR: B26Start 11/09/2008 18:49:37 End: 11/09/2008 19:35:01 Cycle Time: 1 minute Number of Cycles: 35

The fields in this report have the following meaning:

◆ LPAR — The name of the LPAR on which the Collector ran.

◆ Start — The date and time the Collector took the first sample.

◆ End — The date and time the Collector took the last sample.

Reports 557


◆ Cycle Time — The time interval between samples.

◆ Number of Cycles — The total number of samples that the Collector gathered.

Reporter summary

The Reporter summary shows the parameters that are effective during this report. For example, the ChangeTracker dataset may contain data for 200 devices over a 12-hour time period, but the reporter can report on a subset of those devices over a shorter time period if desired.

The following is a sample Reporter summary:

Reporter Summary: Report Date & Time: 08/31/2010 10:38:31 Parms: Device List=RMT(861F,410-41F,F0) 9A80-9A8F UTH84* UTH85* 8560-856F UTHA4E,UTHA4F,UTHA50,UTHA51,UTHA52,UTHA5 SMS Group = SG6 RA Count=2 RA KBS=512 Resynch Time=000:00 Collector Mode=READ/WRITE (RW) Reports=SYMMETRIX,VOLSER,(Skip Zero Tracks Changed Lines) Date=(08022010,08312010) Time=(0600,1900)

The fields in this report have the following meanings:

◆ Report Date & Time — The time when the Reporter job was run.

◆ Parms — All the parameters in effect for the reports. Valid values are:

• Device List — Displays the devices that were requested to include in the reports.

• Symm Serial # — Displays the specific Symmetrix for which to generate reports. Report shows every Symmetrix from which data was collected; none were specified in the example.

• RA Count — Shows the number of RAs that will be used to calculate resynch time.

• RA KBS — Shows the speed of the telecommunications lines that will be used to calculate resynch time.

• Resynch Time — Was not specified. It will be calculated.

• Collector Mode — Reports the specified mode. The default mode is Write (W). If the specified mode does not match the Collector mode, a message is printed in the dataset.

• Reports — Displays the reports that will be generated.

• Date — Displays the dates for which samples will be filtered from the Collector dataset. In this case, no date was specified, so all samples will be used for the reports.

• Time — Displays the times that samples will be filtered from the Collector dataset. In this case, no time was specified, so all samples will be used for the reports.



Symmetrix summary report

The Symmetrix summary report shows the track usage for each Symmetrix system over a specified period of time. Figure 9 shows a sample Symmetrix summary report:

11/11/08 ChangeTracker Symmetrix SummaryFrom 11/09/08 18:49 To: 11/09/08 19:35 MODE = WSymmetrix Volume Total Per Bndwth SyncSerial# Count Cylinders Tracks Cycle % Trks RAs (KBS) Time--------- ------ --------- ------- ------- ------ ---- ----- -----000182600427 6 6678 33611 0 33 4 1000 00:07000182600472 5 5565 59950 0 71 4 1000 00:13

Figure 9 Symmetrix summary report


◆ From and To — Show the dates/times specified in the DATE and TOD parameters. If no DATE and TOD keywords are present in the CONFIG file, the ChangeTracker Reporter uses all the ChangeTracker Collector dataset records and displays the ChangeTracker Collector start and end times here.

◆ Mode — Indicates the specified mode.

◆ Symmetrix Serial# — The serial number of the Symmetrix controller.

◆ Volume Count — The number of volumes included in this report that are part of the specified Symmetrix system.

◆ Total Cylinders — The total number of cylinders for those volumes. ChangeTracker can support Extended Address Volume (EAV) devices (up to 262,668 cylinders in size), provided there is underlying support for them by the mainframe operating system.

◆ Tracks — The number of tracks that have been accessed during the reporting period on those volumes.

◆ Per Cycle — The average of the total number of tracks that have been accessed during the reporting period on those volumes divided by the number of cycles.

◆ % Trks — The percentage of tracks that have been accessed during the reporting period on those volumes.

◆ The last three columns display either the specified value from the CONFIG file, or the value the Reporter calculated using the other two values.

◆ RAs — The number of Remote Adapters (RA).

◆ Bndwth(KBS) — The bandwidth per RA in kilobytes per second.

◆ Sync Time — The elapsed time it would take to resynchronize the changed tracks.

Note: The last statement displays how many cycles were included in this report given the time frame specified.

Reports 559


Volume summary report

The Volume summary report takes the Symmetrix statistics and breaks them down to a volume level. Figure 10 on page 560 shows a sample Volume summary report.

08/31/2010 ChangeTracker Volume Summary From: 08/31/2010 06:00 To: 08/31/2010 16:00 MODE=RW Symmetrix Per Serial# Volser Emul Cyls DSN's Tracks %Trks Cycle ------------ ------ ---- ------ ------ ------- ----- ------- 000190300344 USKA80 3390 3339 7 9398 18 2575 000190300344 USKA81 3390 3339 9 9365 18 2576 000190300344 USKA82 3390 3339 3 10477 20 2716 000190300344 USKA83 3390 3339 10 9313 18 2572 000190300344 USKA84 3390 3339 8 8229 16 2497 000190300344 USKA85 3390 3339 4 9286 18 2573 000190300344 USKA86 3390 3339 7 9325 18 2574 000190300344 USKA87 3390 3339 9 9362 18 2574 000190300344 USKA88 3390 10017 2 9795 6 2441 000190300344 USKA89 3390 10017 3 9792 6 2440 000192600313 $R041A 3390 958 15 13035 90 1312000192600313 $R041B 3390 958 17 13057 90 1336000192600313 $R041C 3390 958 13 12964 90 1304000192600313 $R041D 3390 958 21 13070 90 1334000192600313 $R041E 3390 958 6 12798 89 1246000192600313 $R041F 3390 958 10 12677 88 1204

Figure 10 Volume summary report

The fields in this report have the following meanings:

◆ From and To — The dates and times specified in the DATE and TOD parameters. If no DATE and TOD keywords are present in the CONFIG file, the reporter uses all the Collector dataset records and displays the Collector start and end times here.


◆ Symmetrix Serial# — The serial number of the Symmetrix controller.

Note: You can also find the Symmetrix serial numbers in the joblog of the ChangeTracker Collector.

◆ Volser — The volser of the device being reported on.

• For offline volumes, where the volume serial number cannot be determined, the volser is given as $Ccuuu ($C followed by the two-byte hexadecimal cuuu address converted to printable characters).

• For remote Symmetrix devices on remote controllers, the volser is shown as $Ruuuu, where uuuu represents the hexadecimal unit number within a Symmetrix controller.

• F* with a hexadecimal symm device number (F*uuuu) indicates that the device is acquired through a local gatekeeper, or it is a local FBA device.

◆ Emul — The emulation type of the device.

◆ Cyls — The number of cylinders on the device.



Note: ChangeTracker can support EAV devices (up to 262,668 cylinders in size), provided there is underlying support for them by the mainframe operating system.

◆ DSN's — The number of datasets that had tracks accessed during the reporting time frame. If DATASET is not included in the REPORT parameters, this value will be zero.

◆ Tracks — The number of tracks that were accessed on the device during the reporting time frame.

◆ % Trks — The percentage of tracks on the device that were accessed during the reporting time frame.

◆ Per Cycle — The average number of tracks on the device that were accessed per cycle. This figure is not the number of tracks accessed divided by the number of samples. It is derived by counting the number of track changes for every cycle and calculating the average.

Note: The last statement displays how many cycles were included in this report given the time frame specified.

Dataset summary report

The Dataset summary report takes the volume statistics and breaks them down to a dataset level. Figure 11 shows a sample Dataset summary report.

09/16/2008 ChangeTracker Dataset Summary (OTTCL1) 14:53:29From: 08/06/2008 10:21 To: 08/06/2008 10:25 MODE = W Create Dataset Name Date Cyls Exts Tracks %Trks Volser ---------------------------- ---------- ------ ---- ------- ----- ------ EMCTST.VVV2.INSTLIB 04/11/2006 3 1 31 68 OTTCL1 EMCTST.OSVVV8.LOADLIB 02/16/2006 264 1 264 6 OTTCL1 EMCTST.OSVVV8.CMDLOAD 02/16/2006 287 1 0 0 OTTCL1

Figure 11 Dataset summary report


◆ The name of the volume is displayed in the report title.

◆ From and To — The dates and times specified in the DATE and TOD parameters. If no DATE and TOD keywords are present in the CONFIG file, then the Reporter uses all the Collector dataset records and displays the Collector start and end times here.


◆ Dataset Name — The name of the dataset being reported. If a dataset has an asterisk (*) before its name, the dataset was created after the Collector was run.

◆ Create Date — The date the dataset was created.

◆ Cyls — The number of cylinders allocated to the dataset on this volume.

◆ Exts — The number of extents the dataset has.

◆ Tracks —The number of tracks that were accessed on the dataset during the reporting time frame.

Reports 561


◆ %Trks — The percentage of tracks on the dataset that were accessed during the reporting time frame.

Note: The last statement displays how many cycles were included in this report during the time frame specified.

Interval statistics fileTo help you better understand the frequency of track access, ChangeTracker creates an interval statistics file to show the track-access count, by intervals.

The ChangeTracker Reporter writes the volume/Symmetrix interval statistics to the file with the DDName=ISTATS. This is a variable-length file with LRECEL=256,RECFM=VB. The following are example JCL statements:

//ISTATS DD DISP=disp,DSN=interval.statistics.file

or

//ISTATS DD SYSOUT=X

ChangeTracker writes several records for each INTERVAL (“INTERVAL” on page 551 describes INTERVAL.). For each interval, ChangeTracker can display:

◆ Statistics for each volume or Symmetrix system

◆ Statistics summarized for all Symmetrix systems

Table 29 shows the fields in each record.

Table 29 Interval statistics file record fields (page 1 of 2)

Field Explanation

Symmetrix serial number

This is a 12-character value. If this is a summary record of all Symmetrix data collected, then this field will display $ALL$ALL$ALL, and the volume field will display $ALL$$.

Volume serial number This is a six-character value. For records that are a summary of an entire Symmetrix system, the Symmetrix serial number will be valid, but this field will display $ALL$. For devices that were offline when the ChangeTracker Collector was running, the 6-byte volser is displayed as *cuuu* where cuuu represents the device channel/unit address.

Beginning Date The date at the beginning of an interval. This is an eight character value (yyyymmdd). For example, 20080802 signifies 02-Aug-2008.

Beginning time The time at the beginning of the interval. This is a four-character value (hhmm). For example, if INTERVAL is 60 minutes and this field displays 1400, then this record represents statistics for the period from 14:00 (2 P.M.) to 15:00 (3 P.M.) on the specified date.

Track number The number of tracks accessed during the current interval.



By examining the information in these fields, you can visualize trends in update rates. You can determine whether new tracks are being accessed or whether the same tracks are repeatedly accessed each interval.

EMC ChangeTracker error and event messagesAn explanation of EMC ChangeTracker error and event messages is provided in the EMC Mainframe Enablers Message Guide.

Two-interval track update number

The number of tracks accessed during the current interval as well as the previous interval. This field is always equal to, or higher than the previous field. For example, if this field is 00006031 and the previous field is 00004118, it means that 4118 tracks were accessed in the current interval and that 6031 tracks were accessed in the most recent two intervals. By subtracting these two fields, it can be determined that 1913 (6013 - 4118) tracks were accessed in the previous interval, but were not updated in the current interval.

Three-interval track update number

The number of tracks accessed during the most recent three intervals.

Four-interval track update number

The number of tracks accessed during the most recent four intervals.

Five-interval track update number

The number of tracks accessed during the most recent five intervals.

Six-interval track update number

The number of tracks accessed during the most recent six intervals.

Seven-interval track update number

The number of tracks accessed during the most recent seven intervals.

Eight-interval track update number

The number of tracks accessed during the most recent eight intervals.

Updated tracks since midnight

The number of tracks accessed since midnight of the current date.

Total number of updated tracks

The number of tracks accessed. It is never reset to zero.

Table 29 Interval statistics file record fields (continued) (page 2 of 2)

Field Explanation

EMC ChangeTracker error and event messages 563

CHAPTER 13EMC Disk Compare for z/OS

This chapter describes the EMC Disk Compare utility for z/OS.

◆ Introduction to EMC Disk Compare ........................................................................ 566◆ Disk Compare usage and JCL ................................................................................. 567◆ EMC Disk Compare error and event messages ....................................................... 571

EMC Disk Compare for z/OS 565

EMC Disk Compare for z/OS

Introduction to EMC Disk Compare The EMC Disk Compare utility allows you to compare allocated tracks on pairs of logical disk volumes at the physical level. It has been enhanced to support comparison of devices multiple hops away in an SRDF configuration. Disk Compare is implemented as a batch process and uses the z/OS device number of the respective devices being compared, the number of pairs of devices to compare, the number of cylinders to be validated, and a cylinder skip option which defines the number of cylinders to skip, plus one cylinder to process.

The Disk Compare batch process has the following parameters:

Disk Compare reads the VTOC of the specified devices and determines the location of the allocated tracks (including the VTOC itself). Disk Compare bypasses tracks that are not allocated.

You will find that the ability to make this comparison is useful in an SRDF and/or TimeFinder environment, as it allows you to verify the data integrity of the primary and secondary device.

Before you begin

Before you use Disk Compare, take the following steps:

◆ Verify that there is at least one online path to each device.

◆ Stop all update activity on the devices you want to compare.

Note: The devices you compare can be either online or offline.

Using Disk Compare

After you take the steps outlined in the previous section, you are ready to use Disk Compare. When using Disk Compare, you can take any of the following steps:

◆ Compare multiple devices at the same time. You can analyze the allocated tracks on up to 32 pair of logical disk volumes concurrently.

◆ Specify the number of cylinders you want to compare.

CUU1 Mainframe cuu address.

CUU2 z/OS device number.

CYLCHK The number of cylinders to be validated.

CYLSKIP The number of cylinders to skip plus one cylinder to process.

CYLSKIP is a process frequency. For example, if you set CYLSKIP to 5, Disk Compare processes 1 cylinder and skips 4.

NUMDEV The number of pairs of devices to compare.

TME The time in seconds to wait before displaying the DCOMP33I status message.

CL The number of cycles to wait before displaying the DCOMP33I status message.



◆ Specify a cylinder skip count.

Disk Compare reports all miss-compares and errors on a pair of volumes until it has detected a user-specified number of miss-compared tracks (see next paragraph). At that point, Disk Compare terminates. If you are comparing multiple pairs of devices, and any device compare pair fails, the remaining device pairs will continue to be processed.

Note: The default number of miss-compares is five (5). To override the default number of miss-compares per pair, specify “ERR=nnn,” at the beginning of the PARM field. “nnn” is a one, two, or three digit number in the range of 1-254. If “255” is specified, EMCDSKC will not cease execution until the entire volume has been read. For example, PARM=’ERR=17,31B4,51B4’ will compare device 31B4 with device 51B4, but will not stop until 17 errors have been encountered.

Disk Compare usage and JCLTo execute the Disk Compare utility, EMC suggests that you use the following sample JCL.


BROWSE ds_prefix.MFEvrm.SAMPLIB(EMCDC)

//jobname JOB jobcard_parameters//* //DISKCOMP PROC CUU1=,CUU2=,CYLCHK=99999,CYLSKIP=0,NUMDEV=1//DISKCOMP EXEC PGM=EMCDSKC,REGION=6M,// PARM='&CUU1,&CUU2,&CYLCHK,&CYLSKIP,&NUMDEV,'//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB// PEND//COPMARE1 EXEC DISKCOMP, ... parameters//SYSPRINT DD SYSOUT=class

where:

CUU1=

The value of CUU1 can be:

ppp|pppp|VOLSER|RMT(ccuu,RA#,RA#/SYMDEV#)where:

ppp|pppp Is a mainframe cuu address, either online or offline.

VOLSER Is a 6-character z/OS volume serial number of an online disk volume.

RMT(ccuu,RA#,RA#/SYMDEV#)The minimum that you may specify is RMT(ccuu), in which case it will find the R2.

Note: If CUU1 is specified as a RMT, then CUU2 has to be RMT as well.

Disk Compare usage and JCL 567


CUU2=

The value of CUU2 can be:

sss|ssss|RMT |RMT(,RA#,RA#/SYMDEV#)sss|ssss is the z/OS device address, which can include optional RAs (SRDF groups) connected to a SYMDEV, or two SYMDEVs in a cascaded configuration. The RMT will find the R2, whether cascaded or not.

For example:

RMT(,01,21/A940)

Note: You cannot use volsers for the CUU2 field.

For remote comparisons across the link between two Symmetrix systems, specify RMT. If you specify RMT, the second device is considered to be the Symmetrix remote associated with the device CUU1.

If you have multiple remote devices, and want to use a specific SRDF group, specify the SRDF group with:

RMT(,RA#[[/SYMDEV#[,][[RA#[/SYMDEV#]]])

where:

RA#

Is a 2-byte hex representation of the SRDF group; for example: RMT(,F2).

/SYMDEV#

Is a 4-byte hex representation of the Symmetrix device. Multiple groups and devices can be specified. The Symmetrix device will be considered to be on the last RA controller. For example, RMT(,02/006F) will be the Symmetrix device one hop away. RMT(,02/006F,3E) or RMT(,02,3E/006F) will be the Symmetrix device two hops away.

(,RA#[[/SYMDEV#[,][[RA#[/SYMDEV#]]])

Is an expression that represents a "cascaded" approach to compare images two hops away. Only the last Symmetrix device will be honored.

Note: If the device is concurrent RDF, and no SRDF group is specified, DiskCompare will use the first SRDF group encountered.

Note: If the SYMDEV number is missing, DiskCompare uses the last SYMDEV number in the expression.

CYLCHK=

The value of CYLCHK can be:

1-9999999

This specifies a one-to-seven-character decimal number. This value indicates the number of cylinders to be validated starting from the first.



If you specify more cylinders than exist on the volume, Disk Compare reduces the number of cylinders to the size of the volume. If you set CYLCHK to 0, the whole volume is compared.

CYLSKIP=

The value of CYLSKIP can be:

1-9999999|ALLOC

where:

1-9999999

Is a decimal number. This value indicates the following:

number of cylinders to skip + one cylinder to process

For example, if you set CYLSKIP to 8, Disk Compare processes 1 cylinder and skips 7. If you set CYLSKIP to 10, Disk Compare processes 1 cylinder and skips 9.

The default value is one, meaning “process every cylinder.” If you set CYLSKIP to zero (0), Disk Compare also uses the default value of one.

Note: CYLSKIP=99 or CLYSKIP=999 are special cases. When you use either of these values, Disk Compare sets the skip count to zero (that is, every cylinder is compared), but sets the error count to 99. Disk Compare allows up to 99 missed compares before stopping. Normally, Disk Compare stops after five miss-compares.

ALLOC

If you specify a CYLSKIP value of ALLOC, Disk Compare compares all allocated cylinders.

If you set CYLSKIP > CYLCHK, only the first cylinder is compared.

NUMDEV=

The value of NUMDEV can be:

1 - 32

A one- or two-character decimal number. This value indicates the number of pairs of devices to compare. The minimum is 1 and the maximum is 32.

If you specify the following:

CUU1=0D00,CUUS=0E00,NUMDEV=2

then, 0D00 is compared to 0E00 and 0D01 is compared to 0E01.

You should not specify NUMDEV if CUU1 is a volser. Disk Compare increments the mainframe CUU address, not the mainframe volume serial number for multiple compares.

If you set NUMDEV to greater than 32, Disk Compare will reset the value to 32, which is the maximum number of pairs of devices that can be compared at one time.

Disk Compare usage and JCL 569


TME

The time in seconds to wait before displaying the DCOMP33I status message. The minimum value is 1 and the maximum is 86400. If you set TME to 0, Disk Compare uses the default value of 120 seconds. If you set TME to a value greater than 86400, Disk Compare uses the maximum value of 86400.

CL

The number of cycles to wait before displaying the DCOMP33I status message. The minimum value is 0 and the maximum is 10000. If you set CL to 0, Disk Compare uses the default value of 200 cycles. If you set CL to a value greater than 10000, Disk Compare uses the maximum value of 10000.

ds_prefix

The dataset name prefix you used to install ResourcePak Base.

parameters

The Disk Compare values you specified.

SYSPRINT DD SYSOUT=class

Because Disk Compare messages are in DDname=SYSPRINT, this DD card is necessary.

ExamplesThe following example compares the device on CUU=3074 with the device on CUU=4074:

//EXEC DISKCOMP,CUU1=3074,CUU2=4074

The following example compares device 3005 to device 5440; however, only every 8th cylinder is compared:

//COMPARE EXEC DISKCOMP,CUU1=3005,CUU2=5440,CYLSKIP=8

The following example compares device 3005 to the remote device associated with device 3005:

//COMPARE EXEC DISKCOMP,CUU1=3005,CUU2=RMT

The following example compares all allocated tracks on device 4077 with those same tracks on device 7734:

//COMPARE EXEC DISKCOMP,CUU1=4077,CUU2=7734,CYLSKIP=ALLOC

If the fourth parameter is CYLSKIP=ALLOC, all allocated tracks are compared. Disk Compare reads the VTOC of the first device and determines the location of allocated tracks (including the VTOC itself). Tracks that are not allocated are bypassed.



Cascaded examples The following examples illustrate four versions of the same cascaded disk compare between a local and two remote SYMDEVs.

Note: Please note that in a cascaded configuration, only the last SYMDEV number is used. Each of the examples identifies the final target SYMDEV as 3005, whether explicitly stated or not.

EMC Disk Compare error and event messagesThe EMC Disk Compare Error and Event messages are listed in the EMC Mainframe Enablers Message Guide.

Example 1 ccu1=4077,RMT(,07/3005,17)

Example 2 ccu1=4077,RMT(,07,17/3005)

Example 3 ccu1=4077,RMT(,07/3005,17/3005)

Example 4 ccu1=4077,RMT(,07/1234,17/3005)

EMC Disk Compare error and event messages 571

APPENDIX ASCF Codes and cascaded message displays

This appendix provides a comprehensive list of codes that can be issued by SCF, as well as a description of the MSC message displays for cascaded SRDF configurations.

◆ SCF abend codes .................................................................................................. 574◆ SAICALL error codes .............................................................................................. 577◆ Group Name Services reason codes ...................................................................... 578◆ MSC message displays for cascaded SRDF configurations ..................................... 580

SCF Codes and cascaded message displays 573

SCF Codes and cascaded message displays

SCF abend codesTable 30 describes the abend codes that can be issued by SCF.

Table 30 SCF abend codes (page 1 of 4)

Abend Module Reason User action

0900 SCFMAIN The system name in the startup parameters exceeds the maximum count of 4 characters.

Correct the startup parameters and submit the job again.

0901 SCFMAIN An SCF using the same 4-character name is already active.

If another SCF is active, there is no action. If no other SCF is active, run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

0902 SCFMAIN Not authorized. Authorize all libraries in steplib concatenation.

1001 SCFIN12 $envblock is corrupted. Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the joblog from the SCF startup, and the SASTRACE file.

1001 FC04 Internal logic error while attempting to free the R5BCVWA control block.

Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the SCF job log, and the SCF trace and SCF log files.

1002 SCFIN12 Attach failed for SCFEMGR. Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the joblog from the SCF startup, and the SASTRACE file.

1006 SCFIN12 Parm length exceeds 125 characters. Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the joblog from the SCF startup, and the SASTRACE file.

1032 SCFIN51 Extract STOKEN failed. The subsystem table may be corrupted.

Run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1033 SCFIN99 Extract STOKEN failed. The subsystem table may be corrupted.


1034 SCFMAIN Create Token failed; the SCF token already exists. Another SCF may be active or an earlier shutdown may have failed.

If no other SCF is active, run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1036 SCFPCKFISCFPCCHC

Unable to get addressability to the SCF server address space.

Make sure that SCF is active and has completed startup. Check the SCF$nnnn dd card and validate that it points to the correct SCF. This may also happen if SCF is in the process of terminating.

1037 SCFPCKFISCFPCCHC

Unable to terminate connectivity to the SCF address space.

Check if the SCF address space has terminated. You may need to run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1038 SCFPCSCN Unable to get addressability to the SCF server address space.


1039 SCFPCSCN Unable to terminate connectivity to the SCF address space




1040 SCFZ$TRF Unable to get addressability to the SCF server address space.


1041 SCFZ$TRF Unable to terminate connectivity to the SCF address space.


1050 SCFPDVHCSCFMSCSCFDASSCFWTOWSCFTFASCFLSCF01SCFCHCSCFDEVICSCFGNSTSCFLOGW

Invalid TSB address passed in at startup.


1051 SCFPDVHCSCFMSCSCFDASSCFWTOWSCFTFASCFLSCF01SCFCHCSCFDEVICSCFGNSTSCFLOGW

Unable to find TSB. Run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1052 SCFTRCW Invalid TSB address passed in at startup.


1053 SCFTRCW Unable to find TSB. Run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1054 SCFZTIMR Invalid TSB address passed in at startup.


1055 SCFZTIMR Unable to find TSB. Run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1060 SCFIN01 Initialization failed to complete cleanly. This abend is accompanied by a message. Review the message. Take the appropriate corrective action and restart SCF.

1061 SCFIN01 The $SASECSA is corrupted. Unable to validate SCF environment.


1062 SCFIN01 The API PC routine is missing. Global modules sets are corrupted.

The PC routine for the API failed to load. Correct the issue that caused the load failure and restart SCF.

1063 SCFIN51 The $SASECSA is corrupted. Run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1064 SCFTM31ASCFIN51

There is an inconsistency in the $SASECSA API sets.


1065 SCFIN51 There is an inconsistency in the $SASECSA API sets.




SCF abend codes 575


1066 SCFIN31ASCFPCUCM

The $SASECSA is corrupted. Run the SCF global environment cleanup utility SAMPLIB(SCFUTL01).

1067 SCFPCUCM Logic error in incrementing use count. Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the SCF job log, and the SCF trace and SCF log files.

1068 SCFPCUCM Logic error in decrementing use count. Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the SCF job log, and the SCF trace and SCF log files.

1069 SCFPCUCM Logic error. Unknown SCF version. Contact the EMC Customer Support Center for technical assistance. Make sure you have the dump, the SCF job log, and the SCF trace and SCF log files.

1070 SCFIN31A The $SASECSA is the wrong version. You probably brought up a different version of SCF without properly shutting down the running copy of SCF.


1071 SCFTM31BSCFLOG

Invalid SCF name. Correct the SCF$nnnn dd card and submit the job again.

1072 SCFDEVIC EMCSAI returned RC=28, subsystem not found. SCF is not authorized. This may be caused by a missing module in the steplib concatenation. The module may have been loaded from a unauthorized library in the linklist.

Authorize all libraries in steplib concatenation. Verify that the latest set of maintenance was applied. Check the product release directory on the EMC support zone website for the latest product maintenance and service information. To retrieve these files, log in to EMC support zone and follow the path Support > Downloads and Patches.

1086 SCFTRCW Dataset allocation failed. This abend is accompanied by message SCF0913. It is caused by missing parameters in the SCFINI file. Review the parameters required for defining the SCF log file. Update the SCFINI file and restart SCF.

1087 SCFTRCW Open of the SCF log dataset failed. This is caused by missing parameters in the SCFINI file. Review the parameters required for defining the SCF log file. Update the SCFINI file and restart SCF.

1088 SCFTRCW Re-open of the SCF log dataset failed.

1089 SCFTRCW Re-open of the SCF log dataset failed.

1096 SCFLOGW Dataset allocation failed. This abend is accompanied by message SCF0913. It is caused by missing parameters in the SCFINI file. Review the parameters required for defining the SCF log file. Update the SCFINI file and restart SCF.

1097 SCFLOGW Open of the SCF log dataset failed. This is caused by missing parameters in the SCFINI file. Review the parameters required for defining the SCF log file. Update the SCFINI file and restart SCF.

1098 SCFLOGW Re-open of the SCF log dataset failed.

1099 SCFLOGW Re-open of the SCF log dataset failed.

1101 SCFTM31A There is an inconsistency in the $SASECSA. Unable to validate SCF environment.


1200 SCFPCCPF Invalid $SASECSA is passed to SCFPCCPF.

Internal error.





SAICALL error codesTable 31 through Table 33 list SAICALL error codes:

1201 SCFPCCPF Invalid CPFB is passed to SCFPCCPF Internal error.

1202 SCFPCCPF Unable to connect to server address space.

Activate SCF address space.

2005 SCFIN31A Failed to set up the cross-memory environment.




Table 31 SAICALL error codes

Register Description

R0 EMCRC and EMCRS

R1 Address of object

R15 Return Codes as displayed in Hex:00: OK04: Bad parameter area08: FC01 MCLINVLD on0C: Invalid BCV request0F: FIND_DISK device not found14: CONFIG_DISK director number bad18: User area passed is not large enough

Table 32 SAICALL error codes - EMCRC

EMCRC Description

00 Request successful

04 EMCSAII failed validation

08 EMCSAIO failed validation

0C Request unsuccessful

0F ESTAE received control

14 I/O failed, EMCRS is the STARTIO RC

18 BCV specific

1C SDDF specific

Table 33 SAICALL error codes - ESFCTLNM

Return code Description

04 EMCSAII failed validation

08 EMCSAIO failed validation

12 Request unsuccessful (see EMCRS)

SAICALL error codes 577


Group Name Services reason codesTable 34 describes the Group Name Services (GNS) reason codes.

16 ESTAE received control

20 I/O failed, RS is the STARTIO RC

24 BCV specific

28 SDDF specific

32 ECA specific

36 DLOK specific (device lock)

40 LOCK specific (Symmetric lock)

44 SYSC8133 specific

48 GNS specific

52 FC20 specific

56 Failed RACF check

60 SCFSCRRW/FC22 specific

Table 33 SAICALL error codes - ESFCTLNM

Return code Description

Table 34 GNS reason codes (page 1 of 2)

Code Reason

00 OK

02 PC ROUTINE ABENDED

03 REQUEST IS NOT VALID

04 GROUP NAME WAS NOT SUPPLIED

05 INVALID @EMCGRP VERSION ID

06 INSUFFICIENT STORAGE IN SCF SERVER

07 PC ROUTINE ABENDED

08 GROUP NOT FOUND

09 CONTROLLER NOT FOUND

10 GRAM AREA IS FULL

11 I/O ERROR

12 GNS IS NOT SUPPORTED BY CONTROLLER: nnnnn

13 GNS HAS NOT COMPLETED INIT. TRY LATER

14 GROUP BEING EXTENDED IS NOT A SAR POOL

15 DEVICE LOCK QUERY REQUEST FAILED



16 DEVICE LOCK OBTAIN REQUEST FAILED

18 GROUP BEING EXTENDED IS NOT A GOLD COPY BCV GROUP

21 NO DEVICES/CONTROLLERS ON REQUEST

24 GROUP ALREADY EXISTS

25 EXCEEDED MAX CONTROLLER COUNT OF 128

26 EXCEEDED MAX DEV COUNT PER CONTROLLER

27 DEVICE # EXCEEDED HIGHEST # ON CONTROLLER

28 DEVICE IS LOCKED WITH TF DEVICE LOCK

29 ONLY META HEAD SHOULD BE DEFINED

30 UPDATES ONLY ALLOWED AGAINST AN MVS GROUP

31 GROUP MAY DEFINE R1 OR R2, NOT BOTH

32 DEFINITION VIOLATES ENTERPRISE RULES

33 CAN'T EXTEND AN ENTERPRISE GROUP

36 NOTHING TO COMPLEMENT

38 UNSUPPORTED REQUEST

42 ERROR ENCOUNTERED DURING DELETE

60 OUTPUT BUFFER WAS NOT SUPPLIED

61 OUTPUT BUFFER IS TOO SMALL

80 NEWNAME WAS NOT SUPPLIED

84 GROUP RENAME FAILED

9999 SCF MAY NOT BE ACTIVE

Table 34 GNS reason codes (page 2 of 2)

Code Reason

Group Name Services reason codes 579


MSC message displays for cascaded SRDF configurationsIf remote cycle switching is active, SCF messages for MSC will display with an additional sync_ra field when running with a Cascaded SRDF configuration.

MSC - GROUP=msc_group_name (ccuu,[sync_ra,]async_ra)

Where:

msc_group_name

The name specified in the MSC_GROUP_NAME initialization parameter in SRDF Host Component.

ccuu

The gatekeeper device specified in the MSC_INCLUDE_SESSION initialization parameter for this group.

[sync_ra,]

A local RDF group for the synchronous leg when in a Cascaded SRDF configuration.

async_ra

A local SRDF/A RDF group in SRDF/A MSC and SRDF/Star configurations, and is a remote asynchronous RDF group when in a Cascaded SRDF configuration.


APPENDIX BResetting FBA channel paths and devices

This appendix provides a description of the ESFFUCBC batch utility (formerly named FBACHK) for resetting the Symmetrix system when the mainframe host is no longer able to see channel paths and devices.

◆ The ESFFUCBC Utility ............................................................................................. 582

Resetting FBA channel paths and devices 581

Resetting FBA channel paths and devices

The ESFFUCBC UtilityWhen the Mainframe Enablers product needs to communicate with a Symmetrix controller with fixed-block architecture (FBA) devices, a channel is required for communication.

FBA devices are defined to the mainframe as physical devices in an offline status, and this device definition also provides the channel definition so the MFE can communicate with these FBA devices.

During operation, if FBA devices are varied online and paths are removed from these devices, it is not possible to resolve problems with the FBA devices UCB's and/or sub channels using host software commands.

The ESFFUCBC utility (formerly named FBACHK) is a load module that runs on a mainframe host and resolves issues with FBA device host control blocks as well as validating the Symmetrix configuration for the FBA devices. The utility resets the Symmetrix system when the mainframe host is no longer able to see paths and devices.

Use the ESFFUCBC batch utility program when:

◆ A path goes offline, and you cannot bring it back online.

◆ You want to verify that a volume is an FBA device on a Symmetrix controller.

◆ You want to verify whether the Enginuity operating environment is at the correct level.

Note: When the ESFFUCBC utility is executed, MFE SCF must be active.

Example JCL

The following is an example of JCL to execute the utility:

000001 // JOBCARD 000002 //* 000003 //* CUU=DEVNO /* SPECIFY DEVICE NUMBER OF THE CONTROL UNIT*/ 000004 //* OPT=OPTION /* SPECIFY =VERIFY OR =FIXUCB */ 000005 //* 000006 //ESFFUCBC EXEC PGM=ESFFUCBC,PARM='&CUU,&OPT' 000007 //STEPLIB DD DISP=SHR,DSN=DS-PREFIX.LINKLIB 000008 //SYSPRINT DD SYSOUT=* 000009 //SCF$XXXX DD DUMMY

Where:

&CUU — Is a 3or 4 byte device ccuu ID

&OPT — options:

• VERIFY — Validates that the ccuu is addressable to the Mainframe host.

Note: If the UCB is not valid, the ESFFUCBC utility returns the FBAU0004E error message. Refer to the Mainframe Enablers Messages Guide.

• FIXUCB — Tests whether the UCB is valid and moves the UCB path installed mask (UCBPIM) to the UCB logical path mask (UCBLPM).

Note: Output from the ESFFUCBC utility goes to the JES message log for the job.


APPENDIX CEnhancements

This appendix provides a comprehensive list of ResourcePak Base enhancements for each released version.

◆ ResourcePak Base release enhancements ............................................................. 584

Enhancements 583

Enhancements

ResourcePak Base release enhancementsTable 35 provides a list of the enhancements introduced at each release.

Table 35 ResourcePak Base enhancements (page 1 of 5)

Release Enhancements

7.6 MFE asynchronous notification of host software is a new service that can notify other MFE components about a configuration change, if the other services are running the subtask that listens for this notification. There are two new SCF initialization parameters for this feature: SCF.SRV.GSM.ACTIVATE, and SCF.SRV.GSM.INTERNAL.

7.5 Thin Reclaim Utility (TRU) has been enhanced to support thin reclamation on thick to thin SRDF processing. A new SCF INI Parameter, SCF.TRU.THICKR1=YES|NO enables support for thick R1 scanning of devices. The default value is YES. This parameter enables reclaim processing on thin devices in thick to thin SRDF relationships, supports reclaim processing in SRDF/S and SRDF/A modes in all SRDF topologies, and monitors a thick R1 device only when any related thin R2 device is NOT bound with PERSIST.

General Pool Management now supports VP Compression with two new commands, COMPRESS and DECOMPRESS, and one new parameter for the POOLATTR command (COMPRESSON (ENABLE)) that enables compression for thin devices.

The output displays for GPM commands DISPLAY and QUERY THINDEV have been updated to reflect compression information.

eLicensing (ELM) has been updated to reflect product suites for VMAX 20K and VMAX 40K, along with individual unbundled features where applicable.


Enhancements

7.4 eLicensing support for Symmetrix-based license bundles. A license bundle is a single license that enables multiple features.

Symmetrix Virtual Provisioning™ (VP) provides for the separation of physical storage devices from storage devices as perceived by the host systems. The actual physical storage is not perceived by the host. This separation allows alterations in the physical storage to occur without causing changes which affect the hosts. The result is nondisruptive provisioning.

General Pool Management (GPM) is an updated component for ResourcePak Base V7.4. Prior to V7.4, pool management consisted only of a batch utility and a set of CONFIGPOOL commands. The new GPM commands for VP pool and device management can be excecuted in either online or batch mode.

Starting with Enginuity level 5876 or higher, EMCSCF provides a Thin space reclamation (TRU) environment that records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the Symmetrix free track pool.

A new Thin Pool Capacity Monitor periodically examines the consumed capacity of the SNAPPOOL used by TimeFinder/Snap with VDEV functionality enabled.

A new SRDF/A Write Pacing monitor provides a method of extending the availability of SRDF/A, preventing conditions that canresult in cache overflow. The Write Pacing monitor exposes the user to relevant information regarding pacing activities within the Symmetrix. Pacing activities are collected at the group and device level.

Thin gatekeeper support , for both FBA and CKD devices. The devices do not have to be bound and FBA devices must be addressable to z/OS to be used as gatekeepers. Enginuity level 5876 is required.

The Symmetrix director can now handle a mix of synchronous and asynchronous I/O workloads requiring service at the same time. Mixed SRDF modes allow you to balance the workload on primary devices (R1s). New MRDF commands provide the QOS Utility with the capability of setting and displaying the values of the mixed RDF modes on a director.

DiskCompare can now perform remote compares between source and target devices when all Symmetrix systems are Enginuity level 5876. For lower Enginuity levels, the previous compare method is utilized.

Several QOS commands now provide the ability to specify Symmetrix devices by SRDF group and can filter the results to include or exclude devices based on group priorities. In addition, you can now specify the serial number of the Symmetrix for the selected devices.

Dynamic Cache Partition pool management is now provided with the QOS utility. QOS provides the ability to move all devices in specified pool to a DCP with a single SETCPMVD command.

Includes the application of accumulated maintenance enhancements.



ResourcePak Base release enhancements 585

Enhancements

7.3 Support for EMCTOOLS has been removed. This support is now provided in EMC z/OS Storage Manager (EzSM).

ResourcePak Base V7.3 no longer includes EMC Stored Procedure Executive (EMCSPE) support.

New ELM LIST CONTROLLER and ELM QUERY CONTROLLER commands support the ELM environment. Also, the DEV DISPLAY SUMMARY and DEV DISPLAY CONTROLLER commands now display the status of each of the features for eLicensing.

Host Read Only (HRO) support had been added. New SCF.DEV.ATTR.HRO.INCLUDE.LIST and SCF.DEV.ATTR.HRO.EXCLUDE.LIST initialization parameters enforce read-only status regardless of the physical capability of the devices.

Support for multiple subchannel addressing has been added. The new SCF.DEV.MULTSS initialization parameter supports this feature.

Support for SRDF/Star dynamic device add and delete operations has been added. MSC ADDDEV initiates dynamic device add operations and MSC DELDEV initiates dynamic device delete operations.

Support for SRDF/Star high availability (HA) operations has been added. A new MSC,TAKEOVER command initiates a takeover of the SRDF/Star environment from a secondary server.

7.2 Support for multiple MSC groups per SCF has been added.

e-Licensing information has been added.

Thin pool management has been added - BIND, UNBIND, and RENAME functionality.

Dynamic IODF discovery has been added.

DARE (Data at Rest Encryption) information has been added to the DEVICE DISPLAY SUMMARY and DEVICE DISPLAY CNTRL command displays.

Disk Compare now supports remote devices for cascaded devices multiple hops away.

New alerting capability to report on DSE spillover has been added.

QOS now provides the ability to set the copy priority for each device.

Support for Enginuity version 5875 has been added.

7.0 Support for z/OS V1.10 has been added.


The SCF.MSC.OVERWRITE initialization parameter has been added.

The SETDIR command now supports up to 128 directors

5.8.0 Support for z/OS V1.9 has been added.

SFCTLNM batch utility to assign a controller name has been added.





Enhancements

5.7.0 Support for z/OS V1.8 has been added.

Support for EMCQOS has been added.

Generalized SNAPPOOL and DSEPOOL management has been added.


Log file timestamp adjustment for leap seconds has been added.

5.6.0 ISPF Changes: • EMCTOOLS allows you to set variables on a global basis. This avoids the need for

each user to set every variable. • New REXX sample programs which illustrate how to use each function supported

by the Host Component REXX API.

Support for Compatible Flash.

Support for VARY ONLINE/OFFLINE multi-LPAR functionality within SCF for use by SRDF Host Component for z/OS.

Support for group complement definition.

Support for Group Name Services (GNS) within SCF.

Enterprise group definition.

Support for user-defined gatekeeper.

Support for SCF discovery of remote controllers up to two hops away.

5.5.0 Support for SRDF/A Monitor via an ISPF interface.

Support for Group Name Services for enterprise deployments.

Additional monitoring of SavePool extensions associated with SNAP Virtual Devices.

Support for 5x71 Enginuity features.

5.4.0 Interface for starting, stopping, and controlling the actions of the S/DAS utility with ResourcePak Base commands.

The SRDF/A Monitor added as a component of ResourcePak base and included in the SCF library. The SRDF/A Monitor is designed to:• Find EMC Symmetrix controllers that are running SRDF/A. • Collect and write SMF data about those controllers.

Support for Symmetrix Group Name Services. GNS allows users to define a device group once, and then use that single definition across multiple EMC products.

SRDF/A Multiple Session consistency automation added. This feature allows multiple SRDF/A sessions, hence multiple Symmetrix systems running in SRDF/A mode to be consistent as a group at the remote replication site.



ResourcePak Base release enhancements 587

Enhancements

5.3.0 Licensed Feature Code management added to SCF to support optional capabilities of other EMC mainframe products and Symmetrix features.

Support to refresh the API routines without interrupting executing jobs using EMC or ISV applications that use the API. This is useful when maintenance has been applied to the API and allows updating the running copy nondisruptively.

Support to shut down and restart EMCSCF without interrupting executing jobs using EMC or ISV applications that use the API.

5.2.0 Version number adjusted to match related EMC OS/390 and z/OS software product offerings.

Addition of Cross System Communication (CSC) to assist with multiple LPAR coordination.

Common SAMPLIB for all EMC OS/390 and z/OS software product offerings. Provides an improved maintenance process and centralized all sample JCL, programs, and examples.

Common ISPF library structure for all EMC OS/390 and z/OS software products providing ISPF interfaces. This includes a command CLIST and common gateway ISPF panel.

1.1.1 Support for Enginuity 5x68, EMC SRDF Host Component V5.0.0, RAID10 and Dynamic SRDF features.

1.1.0 Support for EMC TimeFinder V5.1.0.

Support for EMCSNAP asynchronous NOTIFY feature.

Addition of the Recovery Services Environment (REC).

1.0.0 Initial release of product.


