EMC Mainframe Enablers ResourcePak Base for z/OS · Mainframe Enablers and ResourcePak Base ......

EMC® Mainframe EnablersResourcePak® Base for z/OSVersion 8.0

Product GuideREV 02

ResourcePak Base for z/OS Version 8.0 Product Guide2

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

Published June, 2016

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

Chapter 1 Overview

Mainframe Enablers and ResourcePak Base ................................................ 24Licensing .............................................................................................. 24

Introduction to ResourcePak Base ............................................................... 25VMAX environment features .................................................................. 25Storage pool features............................................................................ 27Local replication features ...................................................................... 28Remote replication features .................................................................. 29

Chapter 2 Getting Started

Post-installation.......................................................................................... 32Setting up security ................................................................................ 32Checking IEFSSN table .......................................................................... 32Initializing thin devices ......................................................................... 32Resetting storage pool MaxO to percentage........................................... 32

Configuring ResourcePak Base .................................................................... 33Creating the SCF initialization file .......................................................... 33Sample SCF initialization file ................................................................. 34PARMLIB(SCFINIxx)................................................................................ 35

ResourcePak Base initialization parameters ................................................ 36SRDF/A Monitor (ASY) ........................................................................... 43Controller specification (CNTRL) ............................................................ 46Cross-System Communication (CSC) ..................................................... 47AutoSwap (DAS).................................................................................... 55Device specification (DEV)..................................................................... 55zBoost PAV Optimizer (DEV.OPTIMIZE)................................................... 59Delta-Set Extension Pool Capacity Monitor (DSE)................................... 69Gatekeeper specification (GATEKEEPER) ................................................ 77Group Name Services (GNS) .................................................................. 78General Pool Management (GPM) .......................................................... 79SCF initialization (INI)............................................................................ 80Licensing (LFC) ...................................................................................... 82SCF log file (LOG)................................................................................... 83Multi-Session Consistency (MSC) .......................................................... 86Feature registration (REG)...................................................................... 92Snap Pool Capacity Monitor (SDV)......................................................... 93SNAP Monitor (SNAP) .......................................................................... 101Service task (SRV) ............................................................................... 102SRDF/A Single Session (SS) ................................................................ 103Thin Pool Capacity Monitor (THN) ........................................................ 110SCF tracing (TRACE) ............................................................................. 117Thin Reclamation Monitor (TRU) .......................................................... 121SCF log and trace file (WORK) .............................................................. 133SRDF/A Write Pacing Monitor (WPA) .................................................... 134

Running ResourcePak Base ....................................................................... 139Customizing the SCF started task ........................................................ 139

ResourcePak Base for z/OS Version 8.0 Product Guide 3

Contents

Starting SCF ........................................................................................ 140Running multiple SCF instances .......................................................... 141Stopping SCF ...................................................................................... 141SCF abend codes................................................................................. 144SAICALL error codes ............................................................................ 148SCF termination utility ......................................................................... 150Running AutoSwap in SCF address space ............................................ 151

Using ResourcePak Base commands ......................................................... 152Command format ................................................................................ 152Command types .................................................................................. 152

Chapter 3 Using Symmetrix Control Facility (SCF)

Introduction.............................................................................................. 158 Managing the VMAX environment.............................................................. 159

Summary of operations ....................................................................... 159Device discovery ................................................................................. 162Multiple subchannel addressing ......................................................... 163Dynamic activation of IODF configuration statements .......................... 163HRO-controlled devices in AutoSwap groups ....................................... 164Viewing licenses ................................................................................. 166Global State Management................................................................... 172Non-disruptive SymmAPI-MF refreshes ................................................ 173Command Prefix Facility ...................................................................... 173SCF log and trace files ......................................................................... 174SCF reports ......................................................................................... 176

Command reference .................................................................................. 186Syntax conventions............................................................................. 186DEV,CH,CNTRL..................................................................................... 187DEV,DISPLAY ....................................................................................... 188DEV,REFRESH ...................................................................................... 192DEV,RESCAN ....................................................................................... 193DEV,STATUS ........................................................................................ 193DEV,UNPIN .......................................................................................... 194ELM,LIST ............................................................................................. 195ELM,QUERY ......................................................................................... 196INI,REFRESH ........................................................................................ 197INI,RELOAD ......................................................................................... 197INI,SHUTDOWN ................................................................................... 198REC,QUERYDEVICELOCK ...................................................................... 199REC,RELEASEDEVICELOCK.................................................................... 201SRV,SYSBUSY,HELP............................................................................. 202SRV,SYSBUSY,DISPLAY........................................................................ 202SRV,SYSBUSY,DECREMENT.................................................................. 202SRV,SYSBUSY,RESET ........................................................................... 203

Chapter 4 Controlling Communications (CSC)

Introduction.............................................................................................. 206 Getting started.......................................................................................... 206

Configuring CSC .................................................................................. 206 Controlling communications...................................................................... 207

Summary of operations ....................................................................... 207Polling VMAX systems ......................................................................... 208Selecting gatekeepers......................................................................... 208

4 ResourcePak Base for z/OS Version 8.0 Product Guide

Contents

Polling hosts ....................................................................................... 209Enginuity Attention.............................................................................. 210Viewing hosts ..................................................................................... 211Working with multiple SCF instances ................................................... 214Viewing listeners................................................................................. 215Refreshing CSC information................................................................. 216Verbose messaging............................................................................. 216

Command reference .................................................................................. 217Syntax conventions............................................................................. 217CSC,DISPLAY,HOSTS ........................................................................... 217CSC,DISPLAY,LISTENER........................................................................ 219CSC,REFRESH ...................................................................................... 220

Chapter 5 Naming VMAX Systems (ESFCTLNM)


Running ESFCTLNM utility.................................................................... 222 Naming a VMAX system............................................................................. 222 Command reference .................................................................................. 223

Syntax conventions............................................................................. 223ASSIGN NAME ..................................................................................... 223

Chapter 6 Validating System Paths (ESFCHNU1)


Running ESFCHNU1 utility ................................................................... 226 Command reference .................................................................................. 227

Syntax conventions............................................................................. 227ALL...................................................................................................... 227CCUU .................................................................................................. 227

Return codes............................................................................................. 228

Chapter 7 Resetting FBA Paths and Devices (ESFFUCBC)


Running ESFFUCBC utility .................................................................... 231Sample JCL.......................................................................................... 231Parameters.......................................................................................... 231

Chapter 8 Managing Device Groups (GNS)


Configuring GNS.................................................................................. 235Running EMCGROUP batch utility ........................................................ 235

Managing GNS groups............................................................................... 236Summary of operations ....................................................................... 236Defining GNS groups ........................................................................... 237GNS group types ................................................................................. 238Open systems group support .............................................................. 241

Command reference: EMCGROUP batch utility ........................................... 242Overview............................................................................................. 242Syntax conventions............................................................................. 243


Contents

DEFINE COMPLEMENT.......................................................................... 243DEFINE GROUP .................................................................................... 244DEFINE ENTERPRISE GROUP ................................................................. 253DEFINE GROUP FOR GCOPYBCV............................................................ 254DELETE GROUP .................................................................................... 255DISPLAY GROUP .................................................................................. 256LIST GROUP......................................................................................... 258REMOVE FROM GROUP DEVICE ............................................................ 259REMOVE FROM GROUP RDF GROUP...................................................... 260RENAME GROUP .................................................................................. 261

Command reference: SCF GNS................................................................... 262Overview............................................................................................. 262Syntax conventions............................................................................. 262GNS,FORMAT....................................................................................... 262GNS,LIST ............................................................................................. 263GNS,REFRESH...................................................................................... 265GNS,REVERT........................................................................................ 265

GNS reason codes..................................................................................... 266

Chapter 9 Optimizing Performance (QoS)


Security prerequisites ......................................................................... 271Running the QoS utility........................................................................ 271

Copy priorities........................................................................................... 273Overview............................................................................................. 273Managing copy priorities..................................................................... 273

Dynamic Cache Partitioning (DCP) ............................................................. 274Overview............................................................................................. 274DCP analysis mode.............................................................................. 274Setting up DCP .................................................................................... 275Exploring cache partitions................................................................... 275Managing cache partitions .................................................................. 275DCP example....................................................................................... 276

Mixed SRDF Mode (MRDF) ......................................................................... 277Overview............................................................................................. 277Redistribution of CPU weights ............................................................. 278Managing MRDF policy and weights .................................................... 278

Symmetrix Priority Control (Enginuity 5876 and 5773)............................... 279Overview............................................................................................. 279Managing SPC priorities ...................................................................... 279SPC example ....................................................................................... 280

Command reference: Miscellaneous.......................................................... 281Syntax conventions............................................................................. 281EXIT..................................................................................................... 281WAIT ................................................................................................... 281

Command reference: DCP.......................................................................... 282Syntax conventions............................................................................. 282DISPCCFG............................................................................................ 282DISPCDEV/DISPCDVG and DISPCDV..................................................... 284DISPCGEN ........................................................................................... 286DISPCGRP ........................................................................................... 287DISPCUSE............................................................................................ 288SETCACHE ........................................................................................... 289


Contents

SETCPADD........................................................................................... 290SETCPDEL............................................................................................ 292SETCPMOD.......................................................................................... 293SETCPMRP........................................................................................... 295SETCPMVD and SETCPMV .................................................................... 296

Command reference: Copy priority............................................................. 298Syntax conventions............................................................................. 298DISPCPYP and DISPDEV....................................................................... 298QOSGET .............................................................................................. 300QOSRESET........................................................................................... 302QOSSET .............................................................................................. 304SETCPYP and SETDEVCP ...................................................................... 306

Command reference: SPC .......................................................................... 308Syntax conventions............................................................................. 308DISPDEVP and DISPDEV....................................................................... 308DISPSPC.............................................................................................. 309SETDEVP and SETDEV.......................................................................... 311SETDIR and SETSPC ............................................................................. 313

Command reference: MRDF ....................................................................... 315Syntax conventions............................................................................. 315MRDFDISP DEFAULTS........................................................................... 315MRDFDISP RDFSTATS........................................................................... 316MRDFDISP WEIGHTS ............................................................................ 317MRDFSET POLICY ................................................................................. 318MRDFSET RESET .................................................................................. 319MRDFSET WEIGHTS.............................................................................. 320

Chapter 10 Optimizing Multi-Track I/Os (zBoost PAV Optimizer)

Introduction.............................................................................................. 324Restrictions......................................................................................... 324

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

Optimizing I/Os ........................................................................................ 327Summary of operations ....................................................................... 327Operation modes ................................................................................ 329Selecting devices ................................................................................ 329Limiting optimization by started task/job ............................................ 330Limiting optimization by tracks ........................................................... 330Controlling number of splits/constituent I/Os ..................................... 331Setting quiesce points ........................................................................ 331Consistency support ........................................................................... 332

SMF recording........................................................................................... 334Overview............................................................................................. 334SMF record types................................................................................. 334SMF record format............................................................................... 335STATS record fields ............................................................................. 337SMF reporting utility ............................................................................ 343

Command reference .................................................................................. 347Syntax conventions............................................................................. 347DEV,OPTIMIZE ENABLE ........................................................................ 347DEV,OPTIMIZE DISABLE ....................................................................... 347DEV,OPTIMIZE DISPLAY CONSISTENCY ................................................. 347DEV,OPTIMIZE DISPLAY DEVICE............................................................ 348


Contents

DEV,OPTIMIZE DISPLAY EVENTS........................................................... 349DEV,OPTIMIZE DISPLAY SSID ............................................................... 349DEV,OPTIMIZE DISPLAY SUMMARY....................................................... 350DEV,OPTIMIZE LOG EVENTS ................................................................. 351DEV,OPTIMIZE RESET ........................................................................... 351DEV,OPTIMIZE RESUME ....................................................................... 352DEV,OPTIMIZE SUSPEND...................................................................... 353

Chapter 11 Monitoring Track Changes (ChangeTracker)


Prerequisites....................................................................................... 357Running ChangeTracker Collector ........................................................ 357ChangeTracker Collector sample JCL.................................................... 357ChangeTracker Collector configuration parameters.............................. 358ChangeTracker Collector sample CONFIG file ....................................... 364Running ChangeTracker Reporter......................................................... 364ChangeTracker Reporter sample JCL .................................................... 365ChangeTracker Reporter configuration parameters .............................. 366

Tracking changes with ChangeTracker Collector ......................................... 373Overview............................................................................................. 373Setting up change track collection....................................................... 374Selecting devices to track changes...................................................... 374Setting up ChangeTracker Collector log dataset................................... 374ChangeTracker Collector log dataset.................................................... 376Dumping VTOCs .................................................................................. 377Storage estimates for ChangeTracker Collector disk output ................. 377

Producing reports with ChangeTracker Reporter......................................... 378Overview............................................................................................. 378Setting up reports ............................................................................... 379Collector Summary report.................................................................... 379Reporter Summary report .................................................................... 380Symmetrix Summary report ................................................................. 381Volume Summary report...................................................................... 383Dataset Summary report...................................................................... 385Interval statistics file ........................................................................... 386

Command reference .................................................................................. 388Syntax conventions............................................................................. 388DISPLAY ALL ........................................................................................ 388DISPLAY CYCLE.................................................................................... 388DISPLAY DEVICE .................................................................................. 389DISPLAY LOG ....................................................................................... 389HELP ................................................................................................... 390LOG#................................................................................................... 390LOGSWAP............................................................................................ 390STOP................................................................................................... 390VOLSER ............................................................................................... 391

Chapter 12 Comparing Tracks (Disk Compare)


Prerequisites....................................................................................... 395Running Disk Compare ........................................................................ 395


Contents

Sample JCL.......................................................................................... 395Parameters.......................................................................................... 396

Comparing tracks ...................................................................................... 400Summary of operations ....................................................................... 400Examples ............................................................................................ 401

Chapter 13 Managing Storage Pools (GPM)

Introduction.............................................................................................. 406HYPERMAX OS 5977 and higher .......................................................... 406Enginuity 5876 and 5773.................................................................... 406

Getting started.......................................................................................... 407Configuring GPM ................................................................................. 407Executing GPM commands .................................................................. 407Running the ESFGPMBT utility ............................................................. 407ESFGPMBT conditional processing ...................................................... 408

Working with pools (HYPERMAX OS 5977 and higher) ............................... 410Storage groups.................................................................................... 410Storage resource pools ....................................................................... 410Service level objectives ....................................................................... 411Workload ............................................................................................ 412Disk group .......................................................................................... 413SRDF coordination............................................................................... 413Summary of operations ....................................................................... 413SRP-level alerts ................................................................................... 416

Working with pools (Enginuity 5876 and 5773) ......................................... 417Summary of operations ....................................................................... 417Creating/deleting pools ...................................................................... 420Adding/removing devices ................................................................... 433Allocating/reallocating tracks.............................................................. 437Moving allocations.............................................................................. 437Draining data or save devices.............................................................. 439Rebalancing pools .............................................................................. 441Compressing thin devices ................................................................... 444Halting thin device tasks ..................................................................... 453Pool-level alerts .................................................................................. 454

Queries (HYPERMAX OS 5977 and higher) ................................................. 455Storage Group Query ........................................................................... 455Storage Group (SG) Performance Statistics Query................................ 457Storage Resource Pool Query .............................................................. 458Service Level Objective Query.............................................................. 459Disk Group Query ................................................................................ 460Pool Query .......................................................................................... 461Thin Device Query ............................................................................... 462Thin Device Allocations Query ............................................................. 464Thin Device Allocations by Pool Query ................................................. 465Data Device Query............................................................................... 466

Queries (Enginuity 5876 and 5773)........................................................... 468FAST Tier Query ................................................................................... 468Pool Query .......................................................................................... 468Pool Device Query ............................................................................... 469Thin Device Query ............................................................................... 469Thin Device Allocations Query ............................................................. 472Thin Device Allocations by Pool Query ................................................. 475Data Device Query............................................................................... 477


Contents

Save Device Query .............................................................................. 480Rebalance Task Query ......................................................................... 482Report field summary .......................................................................... 483

Command reference (HYPERMAX OS 5977 and higher) .............................. 488Syntax conventions............................................................................. 488Common parameters........................................................................... 488ADD SYMSG ........................................................................................ 489ALLOCATE............................................................................................ 491CREATE SYMSG ................................................................................... 491DELETE SYMSG.................................................................................... 494HALTTASK............................................................................................ 495HELP ................................................................................................... 495PERSIST OFF ........................................................................................ 496QUERY ALLOC...................................................................................... 496QUERY ALLALLOCS .............................................................................. 498QUERY DATADEV ................................................................................. 500QUERY DISKGRP .................................................................................. 503QUERY POOLDEV ................................................................................. 504QUERY POOLS ..................................................................................... 504QUERY SAVEDEV ................................................................................. 504QUERY SLO.......................................................................................... 504QUERY SRP.......................................................................................... 506QUERY SYMSG..................................................................................... 507QUERY THINDEV .................................................................................. 510REMOVE SYMSG.................................................................................. 513RENAME POOL..................................................................................... 514RENAME SLO ....................................................................................... 514RENAME SYMSG .................................................................................. 516SET SRP............................................................................................... 518SET SYMSG ......................................................................................... 520USR_NRDY .......................................................................................... 522USR_RDY............................................................................................. 524

Command reference (Enginuity 5876 and 5773)........................................ 526Syntax conventions............................................................................. 526Common parameters........................................................................... 526ADD POOL ........................................................................................... 528ALLOCATE............................................................................................ 530BIND ................................................................................................... 532COMPRESS.......................................................................................... 534CREATE POOL ...................................................................................... 537DECOMPRESS...................................................................................... 539DELETE POOL....................................................................................... 541DISABLE .............................................................................................. 542DISPLAY .............................................................................................. 544DRAIN ................................................................................................. 546ENABLE ............................................................................................... 548HALTTASK............................................................................................ 550HDRAIN ............................................................................................... 552HELP ................................................................................................... 554MOVE.................................................................................................. 555PERSIST OFF ........................................................................................ 557POOLATTR ........................................................................................... 559QUERY ALLOC...................................................................................... 562QUERY ALLALLOCS .............................................................................. 563QUERY DATADEV ................................................................................. 565


Contents

QUERY POOLDEV ................................................................................. 566QUERY POOLS ..................................................................................... 568QUERY SAVEDEV ................................................................................. 569QUERY TASKS...................................................................................... 571QUERY TIERS ....................................................................................... 572QUERY THINDEV .................................................................................. 573REBALANCE ......................................................................................... 575REBIND ............................................................................................... 577REMOVE POOL..................................................................................... 579RENAME POOL..................................................................................... 580UNBIND............................................................................................... 582USR_NRDY .......................................................................................... 584USR_RDY............................................................................................. 586

Condition statements (ESFGPMBT) ............................................................ 588IF......................................................................................................... 588ELSE.................................................................................................... 589ENDIF .................................................................................................. 589RESET.................................................................................................. 589

Return codes (ESFGPMBT) ......................................................................... 590

Chapter 14 Monitoring Thin Pools (THN Monitor)


Configuring THN Monitor ..................................................................... 593Running THN Monitor .......................................................................... 593

Monitoring thin pools................................................................................ 594Summary of operations ....................................................................... 594Optional user exit................................................................................ 594Examples ............................................................................................ 595

Command reference .................................................................................. 600Syntax conventions............................................................................. 600THN,DISABLE....................................................................................... 600THN,DISPLAY....................................................................................... 601THN,ENABLE........................................................................................ 602THN,REFRESH ...................................................................................... 602

Chapter 15 Monitoring Snap Pools (SDV Monitor)


Configuring SDV Monitor ..................................................................... 605Running SDV Monitor .......................................................................... 605

Monitoring Snap pools.............................................................................. 606Summary of operations ....................................................................... 606Optional user exit................................................................................ 606Example.............................................................................................. 607

Command reference .................................................................................. 608Syntax conventions............................................................................. 608SDV,DISABLE....................................................................................... 608SDV,DISPLAY....................................................................................... 609SDV,ENABLE........................................................................................ 610SDV,REFRESH ...................................................................................... 610


Contents

Chapter 16 Monitoring DSE Pools (DSE Monitor)


Configuring DSE Monitor ..................................................................... 614Running DSE Monitor .......................................................................... 614

Monitoring DSE pools................................................................................ 615Summary of operations ....................................................................... 615Optional user exit................................................................................ 615Example.............................................................................................. 616

Command reference .................................................................................. 617Syntax conventions............................................................................. 617DSE,DISABLE....................................................................................... 617DSE,DISPLAY ....................................................................................... 618DSE,ENABLE........................................................................................ 619DSE,REFRESH ...................................................................................... 619

Chapter 17 Monitoring Space Reclamation (TRU Monitor)


Configuring the TRU Monitor................................................................ 622Running the TRU Monitor..................................................................... 623

Monitoring the TRU environment ............................................................... 624Summary of operations ....................................................................... 624Monitoring .......................................................................................... 626Monitored devices .............................................................................. 627Scanning............................................................................................. 628Reclaiming .......................................................................................... 629

Command reference .................................................................................. 631Syntax conventions............................................................................. 631TRU,HELP ............................................................................................ 631TRU,DISABLE ....................................................................................... 632TRU,DISPLAY ....................................................................................... 633TRU,DISPLAY,DEVICE ........................................................................... 634TRU,ENABLE ........................................................................................ 635TRU,HOLD ........................................................................................... 636TRU,RECLAIM....................................................................................... 636TRU,REFRESH ...................................................................................... 637TRU,RELEASE....................................................................................... 637TRU,SCAN............................................................................................ 638TRU,START........................................................................................... 639TRU,STOP ............................................................................................ 640

Chapter 18 Pool Monitor User Exit

Overview................................................................................................... 642 Sample user exit ....................................................................................... 642 Parameters passed to user exit ................................................................. 643

General information ............................................................................ 643Interval information............................................................................. 644Percentage used ................................................................................. 644Symmetrix system information ............................................................ 644Symmetrix system information from prior interval................................ 645Pool information ................................................................................. 645Pool information from prior interval ..................................................... 646


Contents

Chapter 19 Managing zDP Processes

Introduction.............................................................................................. 650 Running zDP processes ............................................................................. 650 Command reference .................................................................................. 651

Syntax conventions............................................................................. 651PAUSE................................................................................................. 651RELEASEDEVICELOCK .......................................................................... 651RESUME .............................................................................................. 652START.................................................................................................. 652STOP................................................................................................... 653

Chapter 20 Monitoring SRDF/A (SRDF/A Monitor)


Configuring SRDF/A Monitor ................................................................ 659Running SRDF/A Monitor ..................................................................... 659

Monitoring SRDF/A sessions ..................................................................... 660Summary of operations ....................................................................... 660Monitoring process ............................................................................. 662SRDF/A Single Session Auto Recovery ................................................. 664Optional user exit................................................................................ 665SMF record format............................................................................... 665

Command reference .................................................................................. 669Syntax conventions............................................................................. 669ASY,DISABLE ....................................................................................... 669ASY,DISPLAY ....................................................................................... 669ASY,ENABLE ........................................................................................ 670ASY,REFRESH ...................................................................................... 670ASY,SSAR,DISABLE.............................................................................. 671ASY,SSAR,ENABLE............................................................................... 671ASY,RECOVER,SRDFA........................................................................... 672

Chapter 21 Monitoring SRDF/A Write Pacing (WPA Monitor)

Introduction.............................................................................................. 674Limitations.......................................................................................... 674

Getting started.......................................................................................... 675Configuring SRDF/A Write Pacing Monitor............................................ 675Running SRDF/A Write Pacing Monitor ................................................. 675

Monitoring SRDF/A Write Pacing................................................................ 676Summary of operations ....................................................................... 676Monitoring process ............................................................................. 676SMF record format............................................................................... 677

Chapter 22 Managing SRDF/AR Processes

Introduction.............................................................................................. 680 Running SRDF/AR processes ..................................................................... 680 Command reference .................................................................................. 681

Syntax conventions............................................................................. 681SAR,PAUSE.......................................................................................... 681SAR,START .......................................................................................... 682SAR,RESTART....................................................................................... 682SAR,STOP............................................................................................ 683


Contents

Chapter 23 Managing SRDF/A MSC


Configuring MSC ................................................................................. 686 Controlling MSC environment .................................................................... 687

Enabling MSC environment of SCF....................................................... 687Basic operations ................................................................................. 687SRDF Automatic Recovery.................................................................... 688Tracing and messaging........................................................................ 688Miscellaneous..................................................................................... 688MSC messages for Cascaded SRDF...................................................... 689

Command reference .................................................................................. 690Syntax conventions............................................................................. 690MSC,ADDDEV ...................................................................................... 690MSC,DEACT ......................................................................................... 691MSC,DEACTREFRESH ........................................................................... 693MSC,DEACTRESTART............................................................................ 695MSC,DEACTRESTARTTOSEC.................................................................. 697MSC,DEACTRESTARTTOZERO ............................................................... 698MSC,DELDEV ....................................................................................... 700MSC,DISABLE ...................................................................................... 701MSC,DISPLAY ...................................................................................... 703MSC,ENABLE ....................................................................................... 704MSC,PENDDROP.................................................................................. 705MSC,RECOVER..................................................................................... 707MSC,REFRESH ..................................................................................... 708MSC,RESTART...................................................................................... 710MSC,RESTARTTOSEC............................................................................ 712MSC,RESTARTTOZERO ......................................................................... 713MSC,TAKEOVER ................................................................................... 714MSC,VERBOSE .................................................................................... 715


Title Page

FIGURES

1 z/OS SymmAPI architecture....................................................................................... 1582 Symmetrix Summary report ....................................................................................... 3813 Volume Summary report............................................................................................ 3834 Dataset Summary report............................................................................................ 385


Figures


Title Page

TABLES

1 Features and prefixes .................................................................................................. 362 Initialization parameter default values ........................................................................ 373 SCF abend codes....................................................................................................... 1444 SAICALL error codes .................................................................................................. 1485 SAICALL error codes — EMCRC................................................................................... 1486 SAICALL error codes — ESFCTLNM.............................................................................. 1487 SCFTM31A return codes ............................................................................................ 1518 ResourcePak Base features and associated command types ..................................... 1521 Managing devices ..................................................................................................... 1592 Licensing .................................................................................................................. 1593 SymmAPI-MF operations ........................................................................................... 1604 Managing external applications ................................................................................ 1605 Command Prefix Facility operations........................................................................... 1606 SCF log and trace files ............................................................................................... 1607 SCF log file ................................................................................................................ 1618 SCF trace file ............................................................................................................. 1619 ELM,LIST output fields under HYPERMAX OS 5977..................................................... 16710 ELM,LIST output fields under Enginuity 5876 or 5773................................................ 16811 ELM,QUERY output fields under HYPERMAX OS 5977................................................. 17012 ELM,QUERY output fields under Enginuity 5876 or 5773............................................ 17113 Basic operations ....................................................................................................... 20714 Timing operations ..................................................................................................... 20715 Enginuity Attention operations .................................................................................. 20716 ESFCHNU1 return codes ............................................................................................ 22817 GNS operations......................................................................................................... 23618 GNS batch commands............................................................................................... 24219 GNS reason codes..................................................................................................... 26620 Managing copy priorities ........................................................................................... 27321 Setting up DCP .......................................................................................................... 27522 Exploring cache partitions ......................................................................................... 27523 Managing cache partitions ........................................................................................ 27524 Managing MRDF policy and weights .......................................................................... 27825 Managing SPC priorities ............................................................................................ 27926 General operations.................................................................................................... 32727 Logging and messaging............................................................................................. 32728 Defining scope of optimization.................................................................................. 32829 Controlling resource utilization.................................................................................. 32830 Section 1 — zHPF PAV optimization parameters......................................................... 33731 Section 2 — Basic monitoring zHPF counts ................................................................ 33832 Section 3 — PAV optimization passive zHPF counters ................................................ 33933 Section 4 — PAV optimization active monitoring zHPF counters ................................. 34034 Section 5 — PAV optimization zHPF skip processing by parameters ........................... 34135 Section 6 — PAV optimization zHPF skip processing.................................................. 34236 Section 7 — PAV optimization logging event stats ..................................................... 34237 Setting up track change collection............................................................................. 37438 Selecting devices to track changes............................................................................ 37439 Setting up ChangeTracker Collector log dataset......................................................... 37440 Setting up reports ..................................................................................................... 37941 Interval statistics file fields ....................................................................................... 38642 Disk Compare operations .......................................................................................... 400


Tableses

1 SLO levels ................................................................................................................. 4112 Disk drive requirements ............................................................................................ 4123 Available workloads.................................................................................................. 4134 Storage group operations.......................................................................................... 4135 Storage resource pool operations.............................................................................. 4146 Thin pool operations ................................................................................................. 4147 SLO operations ......................................................................................................... 4148 Device operations ..................................................................................................... 4149 Track allocation operations ....................................................................................... 41410 Query commands ..................................................................................................... 41511 Command execution settings .................................................................................... 41512 Getting help ............................................................................................................. 41513 Pool operations......................................................................................................... 41714 Device operations ..................................................................................................... 41715 Thin device allocation operations.............................................................................. 41816 Thin device compression operations ......................................................................... 41817 Query commands ..................................................................................................... 41818 Command execution settings .................................................................................... 41919 Getting help ............................................................................................................. 41920 QUERY display field descriptions............................................................................... 48321 THN Monitor operations ............................................................................................ 59422 SDV Monitor operations ............................................................................................ 60623 DSE Monitor operations ............................................................................................ 61524 Basic TRU Monitor operations ................................................................................... 62425 Setting scanning options........................................................................................... 62426 Setting reclaiming options ........................................................................................ 62527 Setting scratch options ............................................................................................. 62528 Parameters for general information ........................................................................... 64329 Parameters for interval information ........................................................................... 64430 Parameters for percentage used................................................................................ 64431 Parameters for Symmetrix system information........................................................... 64432 Parameters for Symmetrix system information from prior interval .............................. 64533 Parameters for pool information................................................................................ 64534 Parameters for pool information................................................................................ 6461 zDP operations.......................................................................................................... 6501 SRDF/A Monitor initialization parameters.................................................................. 6592 SRDF/A Single Session Auto Recovery initialization parameters ................................ 6593 SRDF/A Monitor operations ....................................................................................... 6604 SRDF/A Single Session Auto Recovery operations...................................................... 6615 SMF record fields ...................................................................................................... 6656 SRDF/A Write Pacing Monitor initialization parameters.............................................. 6757 SRDF/A Write Pacing Monitor operations ................................................................... 6768 SRDF/AR operations .................................................................................................. 6809 Basic operations ....................................................................................................... 68710 SRDF Automated Recovery operations ....................................................................... 68811 Tracing and messaging operations ............................................................................ 68812 Miscellaneous MSC operations ................................................................................. 688


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 VMAX storage system.

CoverageThis documents describes ResourcePak Base for z/OS when used in the following VMAX operating environments supported by Mainframe Enablers 8.0:

◆ HYPERMAX OS 5977

◆ Enginuity 5876

◆ Enginuity 5773

Note: Refer to the ResourcePak Base for z/OS V7.6 Product Guide for information pertaining to other Enginuity levels.

Related documentationThe following documents provide additional information about Mainframe Enablers:

◆ Mainframe Enablers Release Notes

◆ Mainframe Enablers Installation and Customization Guide

◆ Mainframe Enablers Message Guide

◆ Consistency Groups for z/OS Product Guide

◆ ResourcePak Base for z/OS Product Guide

◆ SRDF Host Component for z/OS Product Guide

◆ TimeFinder SnapVX and zDP Product Guide

◆ TimeFinder/Clone Mainframe Snap Facility Product Guide

◆ TimeFinder Mirror for z/OS Product Guide

◆ TimeFinder Utility for z/OS Product Guide


Preface

The following documents provide additional information:

◆ EMC VMAX3 Family with HYPERMAX OS Product Guide— Documents the features and functions of the VMAX3 100K, 200K, and 400K arrays.

◆ EMC VMAX Family with Enginuity Product Guide — Documents the features and functions of the VMAX 10K, 20K, and 40K arrays.

◆ EMC VMAX 100K, 200K, and 400K with HYPERMAX OS Release Notes — Describe new features and any known limitations.

◆ EMC VMAX Family Viewer for Desktop and iPad® — Illustrates system hardware, incrementally scalable system configurations, and available host connectivity offered for VMAX arrays.

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

◆ SolVe Desktop — Provides links to documentation, procedures for common tasks, and connectivity information for 2-site and 3-site SRDF configurations. To download the SolVe Desktop tool, go to EMC Online Support at https://support.EMC.com and search for SolVe Desktop. Download the SolVe Desktop and load the VMAX Family and DMX procedure generator.

You need to authenticate (authorize) your SolVe Desktop. Once it is installed, please familiarize yourself with the information under Help tab.

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.

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

IMPORTANT

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


Preface

Typographical conventions

EMC uses the following type style conventions in this document:

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

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


http://support.EMC.com

Preface

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 VMAX license files, visit the Service Center on http://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.

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]


https://support.EMC.com/products

http://support.EMC.com

CHAPTER 1Overview

This chapter covers the following topics:

◆ Mainframe Enablers and ResourcePak Base ............................................................ 24◆ Introduction to ResourcePak Base ........................................................................... 25

Overview 23

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

◆ SRDF® Host Component for z/OS

◆ AutoSwap for z/OS

◆ Consistency Groups for z/OS

◆ TimeFinder SnapVX

◆ Data Protector for z Systems (zDPTM)1

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

Licensing

Refer to the following documents for information about licensing:


◆ VMAX3 Family with HYPERMAX OS VMAX 100K, VMAX 200K, and VMAX 400K Product Guide

◆ VMAX Family VMAX 10K, VMAX 20K, and VMAX 40K Product Guide

1. zDP requires TimeFinder SnapVX but is a separately licensed product.


Overview

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 VMAX® storage systems. ResourcePak Base is designed to improve performance and simplify the use of mainframe-based VMAX 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.

ResourcePak Base for z/OS is a prerequisite for EMC mainframe applications such as SRDF Host Component for z/OS.

VMAX environment features

Below is a summary of the key VMAX environment features available in ResourcePak Base. For complete information on the features, refer to Part 1, “VMAX ENVIRONMENT” on page 155 of this guide.

Cross-system communicationThe CSC (Cross-System Communication) component of SCF controls inter-LPAR communications. CSC uses locally and remotely connected VMAX systems to facilitate communications between LPARs. A number of EMC VMAX mainframe applications use CSC to handle inter-LPAR communications.

“Controlling Communications (CSC)” on page 205 provides more information.

Automatic notification of configuration changes to Mainframe Enablers applicationsResourcePak Base can automate the asynchronous notification of VMAX system configuration changes to another Mainframe Enablers application, such as ConGroup, that supports the receipt of this data.

Configuration changes can include discovery of a new VMAX system, removal of an existing system, changes in Enginuity and HYPERMAX OS versions, discovery of new devices, removal of existing devices, occurrence of a UCB swap, or a combination of these events.

Non-disruptive SymmAPI-MF refreshesResourcePak Base allows the EMC Symmetrix Applications Programming Interface for z/OS (SymmAPI™-MF) to be refreshed non-disruptively. ResourcePak Base 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.

Introduction to ResourcePak Base 25

Overview

SWAP servicesResourcePak Base deploys a SWAP service. It is used by AutoSwap for planned swaps and with the ConGroup AutoSwap Extension (CAX).

The AutoSwap for z/OS Product Guide describes AutoSwap. The Consistency Groups for z/OS Product Guide describes 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 VMAX device now check to ensure that devices are logically available for use only by an authorized user.

VMAX system namesResourcePak Base provides the ability to assign a unique name to a VMAX system using the ESFCTLNM utility.

“Naming VMAX Systems (ESFCTLNM)” on page 221 provides more information.

System path validationTo ensure proper functioning, ResourcePak Base provides the ability to validate all of the paths that connect to the same VMAX system to identify crossed cabling that would put devices in two SSIDs of the same split. Validation is done using the ESFCHNU1 utility.

“Validating System Paths (ESFCHNU1)” on page 225 provides more information.

FBA path resetThe ESFFUCBC utility (formerly named FBACHK) resets the VMAX system when the mainframe host is no longer able to see channel paths and devices.

“Resetting FBA Paths and Devices (ESFFUCBC)” on page 229 provides more information.

Group Name Services (GNS)GNS (Group Name Services) is the VMAX 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. GNS also allows you to define group names for volumes that can then be operated upon by various other commands.

“Managing Device Groups (GNS)” on page 233 provides more information.


Overview

Quality of Service (QoS)The Quality of Service (QoS) Utility allows you to customize certain priorities of the VMAX system on a logical-volume basis. QoS grants you more flexibility in managing your VMAX system performance. By increasing the response time for specific copy operations on selected devices or groups, you can increase the overall performance of the other VMAX devices.

“Optimizing Performance (QoS)” on page 269 provides more information.

Multi-track I/O optimizationzBoostTM 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.

“Optimizing Multi-Track I/Os (zBoost PAV Optimizer)” on page 323 provides more information.

Track monitoringThe ChangeTracker utility allows you to monitor and update activity on VMAX devices. ChangeTracker enables you to determine the number of tracks that have been accessed during the interval since the last monitoring.

“Monitoring Track Changes (ChangeTracker)” on page 355 provides more information.

Track comparisonThe Disk Compare utility compares tracks on pairs of logical disk volumes at the physical level. The utility supports comparison of devices multiple hops away in an SRDF configuration.

“Comparing Tracks (Disk Compare)” on page 393 provides more information.

Storage pool features

Below is a summary of the key storage pool features available in ResourcePak Base. For complete information on the features, refer to Part 2, “STORAGE POOLS” on page 403 of this guide.

General Pool Management (GPM)ResourcePak Base allows you to create and manage thin pools. The General Pool Management (GPM) facility of ResourcePak Base provides a set of online and batch commands to control thin pools.

For Enginuity 5876 and 5773, ResourcePak Base supports thin (virtual) pools, SNAP pools, and DSE pools. Starting with HYPERMAX OS 5977, it provides only a single pool type, thin pool, which can be used for virtual provisioning as well as Snap and SRDF/A spillover (DSE) operations.

“Managing Storage Pools (GPM)” on page 405 provides more information.


Overview

Thin Pool Capacity (THN) MonitorThe Thin Pool Capacity (THN) Monitor allows you to monitor thin pools.

Starting with HYPERMAX OS 5977, the thin pool is the only type of pool used for virtual provisioning. It replaces save pools, Snap pools, and DSE pools.

“Monitoring Thin Pools (THN Monitor)” on page 591 provides more information.

Snap Pool Capacity (SDV) MonitorThe Snap Pool Capacity (SDV) Monitor allows you to monitor Snap pools that contain save devices.

IMPORTANT

Starting with HYPERMAX OS 5977, save devices are no longer used.

“Monitoring Snap Pools (SDV Monitor)” on page 603 provides more information.

Delta Set Extension (DSE) Pool Capacity MonitorThe DSE Pool Capacity Monitor allows you to monitor DSE pools.

IMPORTANT

DSE pools are available under Enginuity 5876 and 5773. Starting with HYPERMAX OS 5977, DSE pools are no longer used.

“Monitoring DSE Pools (DSE Monitor)” on page 611 provides more information.

Thin Reclamation (TRU) MonitorThe TRU Monitor records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the VMAX free track pool.

Note: The TRU Monitor is available with Enginuity 5876 and HYPERMAX OS 5977.

“Monitoring Space Reclamation (TRU Monitor)” on page 621 provides more information.

Local replication features

zDPzDP (Data Protector for z Systems) is a z/OS-based solution that automates SnapVX snapshot creation/deletion. ResourcePak Base enables you to start and stop zDP run-time tasks, as described in “Managing zDP Processes” on page 649.

Note: zDP is available with HYPERMAX OS 5977. For complete information about zDP, refer to the TimeFinder SnapVX and zDP Product Guide.


Overview

Remote replication features

Below is a summary of the key SRDF (Symmetrix Remote Data Facility) features available in ResourcePak Base. For complete information on the features, refer to “Part 4” on page 655 of this guide.

SRDF/A MonitorThe SRDF/A Monitor is designed to monitor the state of SRDF/A groups in your environment.

“Monitoring SRDF/A (SRDF/A Monitor)” on page 657 provides more information.

SRDF/A Write Pacing (WPA) MonitorSRDF/A Write Pacing extends the availability of SRDF/A by enabling you to prevent conditions that can result in cache overflow.

The SRDF/A Write Pacing Monitor exposes relevant information regarding write pacing activities within the VMAX system. The data is collected at both the SRDF/A group and device level.

“Monitoring SRDF/A Write Pacing (WPA Monitor)” on page 673 provides more information.

SRDF/ARSRDF/AR (Symmetrix Remote Data Facility/Automated Replication) automates data copying across SRDF links to provide a logically consistent, restartable image of data at a remote (recovery) site in the event of a disaster at the production site.

“Managing SRDF/AR Processes” on page 679 provides more information.

SRDF/A MSCMSC (Multi-Session Consistency) is an environment in EMCSCF that ensures remote R2 consistency across multiple VMAX systems running SRDF/A.

“Managing SRDF/A MSC” on page 685 provides more information.


Overview


CHAPTER 2Getting Started


◆ Post-installation...................................................................................................... 32◆ Configuring ResourcePak Base ................................................................................ 33◆ ResourcePak Base initialization parameters ............................................................ 36◆ Running ResourcePak Base ................................................................................... 139◆ Using ResourcePak Base commands ..................................................................... 152

Getting Started 31

Getting Started

Post-installationBefore you begin using ResourcePak Base, review and complete the following post-installation activities:

◆ Setting up security

◆ Checking IEFSSN table

◆ Initializing thin devices

◆ Resetting storage pool MaxO to percentage

Setting up security

You must install the ResourcePak Base load modules into an APF-authorized dataset.

Either APF-authorize the ResourcePak Base LINKLIB library or copy the related load modules to an APF-authorized library. The library may be specified in the system linklist or copied to a linklist dataset.

Checking IEFSSN table

Ensure that you do not add ResourcePak Base entries to the IEFSSN table for the LPAR via PARMLIB or SETSSI command. Normally, EMC software dynamically creates an entry in the IEFSSN table via the IEFSSI macro.

Initializing thin devices

If you are using HYPERMAX OS 5977 and higher, initialize and label thin devices using ICKDSF INIT.

Under Enginuity 5876 or 5773, this manual operation is not needed.

Resetting storage pool MaxO to percentage

To have the maximum oversubscription rate displayed as percentages instead of ratios (which is the default behavior under HYPERMAX OS 5977 and higher), reset it to a percentage value using the POOLATTR command with the MAXOSUB parameter, as described in “POOLATTR” on page 559, for all pools with an existing maximum oversubscription rate set via General Pool Management (the MaxO value in the QUERY POOLS report).

For example, if the existing MaxO value is 1 (one-to-one subscription), it must be reset to the equivalent percentage value, which would be 100.

Note: “Oversubscription rate” on page 422 describes the oversubscription rate.


Getting Started

Configuring ResourcePak BaseBefore using ResourcePak Base, you have to create an initialization file containing your customized initialization parameter settings.

The initialization file is specified using the SCFINI DD statement of the SCF started task, as described in “Customizing the SCF started task” on page 139.

Creating the SCF initialization file

Generally, SCF initialization parameters are specified as a series of statements in the following format:

<keyword>=<value><keyword>=<value>...<keyword>=<value>

Note: If a parameter has a different syntax, it is provided in the parameter description in “ResourcePak Base initialization parameters” on page 36.

◆ For each parameter statement, the keyword begins in column 1.

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

◆ Each statement in the SCF initialization file begins on a separate line.

However, parameters that support a list of comma-delimited values may be continued across multiple lines. To continue one of one these parameters, ensure that the last non-blank character on the line you wish to continue is a comma, and start the subsequent line in column 1. Subsequent lines (starting with the character in column 1) will be appended to the preceding line after the comma to form the complete statement.

For example:

SCF.CSC.GATEKEEPER.LIST=2100,3100,4100

The text above results in SCF.CSC.GATEKEEPER.LIST=2100,3100,4100 being processed.

Parameters ending in .LIST may be specified an unlimited number of times. When a .LIST parameter is encountered that has already been processed in the configuration file, the values are concatenated into a single list.

For example:

SCF.DEV.INCLUDE.LIST=2000-21FFSCF.DEV.INCLUDE.LIST=3000-31FFSCF.DEV.INCLUDE.LIST=4000-41FF

The text above results in SCF.DEV.INCLUDE.LIST=2000-21FF,3000-31FF,4000-41FF being processed.

Configuring ResourcePak Base 33

Getting Started

◆ Comments are indicated by an asterisk (*) in column 1. To add a comment on a parameter line, use the format /* comment */.

Note: The SCF initialization file may or may not be under SMS control as defined in the installation. Therefore, the DATACLAS, STORCLAS, and MGTCLAS entries may not be required.

Sample SCF initialization file

You can find a sample SCF initialization file in SCF.SAMPLIB or use the following sample as a basis for your own file. You can change existing initialization parameters in the sample file to meet your needs and add new initialization parameters to the file.

The initialization parameters are displayed as comments. Before using this file, edit the parameters to match your configuration and remove the asterisks (*).

*************************************************** * * 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=0000AC *SCF.CSC.ACTIVEPOLL=10 *SCF.CSC.IDLEPOLL=5


Getting Started

PARMLIB(SCFINIxx)

After the SCF initialization file is processed during the SCF startup procedure, SCF reads startup parameters from the logical PARMLIB member SCFINIxx.

◆ If SCFINIxx is not found, normal processing continues.

◆ If SCFINIxx is found, the SCF initialization parameters stored in SCFINIxx are appended to or replace the parameters read from the SCFINI DD statement.

The parameters stored in SCFINIxx are appended when they are presented as a list (for example, SCF.DEV.EXCLUDE.LIST). When a parameter is not a .LIST entry, it replaces an existing parameter.

You can place any startup parameters in PARMLIB(SCFINIxx).

Comments are only allowed in the last line of the member.

Note: 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.

Configuring ResourcePak Base 35

Getting Started

ResourcePak Base initialization parametersResourcePak Base initialization parameters are specified in the SCF initialization file identified with the SCFINI DD statement in the SCF started task.

Note: “Creating the SCF initialization file” on page 33 describes the SCF initialization file.

Names of the initialization parameters have the following structure: SCF.prefix.keywords.

To help you navigate to parameters of a specific ResourcePak Base component or feature, Table 1 lists the components and the corresponding parameter prefixes.

Table 1 Features and prefixes

Prefix Component/Feature Parameters

ASY SRDF/A Monitor page 43

CNTRL Specification of VMAX systems page 46

CSC The Cross-System Communications (CSC) component page 47

DAS AutoSwap page 55

DEV Specification of devices page 55

DEV.OPTIMIZE zBoost PAV Optimizer page 59

DSE Delta Set Extension (DSE) Pool Capacity Monitor page 69

GATEKEEPER Specification of gatekeepers page 77

GNS Group Name Services (GNS) page 78

GPM General Pool Management (GPM) page 79

INI SCF initialization page 80

LFC Licensing page 82

LOG SCF log file page 83

MSC Multi-Session Consistency (MSC) page 86

REG Registration of VMAX systems page 92

SDV Snap Pool Capacity (SDV) Monitor page 93

SNAP SNAP Monitor page 101

SRV Service tasks page 102

SS SRDF/A Single Session page 103

THN Thin Pool Capacity (THN) Monitor page 110

TRACE SCF tracing page 117

TRU Thin Reclamation (TRU) Monitor page 121

WORK SCF log and trace files page 133

WPA SRDF/A Write Pacing Monitor page 134


Getting Started

Default valuesTable 2 lists the default values for the ResourcePak Base initialization parameters.

Table 2 Initialization parameter default values (page 1 of 6)

Initialization parameter Default value

SCF.ASY.MONITOR DISable

SCF.ASY.POLL.INTERVAL 5

SCF.ASY.SECONDARY_DELAY 120

SCF.ASY.SMF.POLL 6

SCF.ASY.SMF.RECORD None

SCF.ASY.USEREXIT None

SCF.CNTRL.EXCLUDE.LIST None

SCF.CNTRL.INCLUDE.LIST None

SCF.CSC.ACTIVE NO

SCF.CSC[.{SymmID|RMT}].ACTIVEPOLL 5 (.5 seconds) for local VMAX systems, 10 (1 second) for remote VMAX systems

SCF.CSC[.SymmID].ATTNACTIVE YES

SCF.CSC[.SymmID].ATTNPATHGRP NO

SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE 20

SCF.CSC.GATEKEEPER.LIST 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.SymmID.LIST None

SCF.CSC[.{SymmID|RMT}].IDLEPOLL 5 seconds for local VMAX systems, 10 seconds for remote VMAX systems

SCF.CSC.INSTANCE 0

SCF.CSC[.{SymmID|RMT}].MITPERIOD 30

SCF.CSC.REFORMAT NO

SCF.CSC[.{SymmID|RMT}].SELTIMEOUT 60

SCF.CSC[.{SymmID|RMT}].VERBOSE NO

SCF.DAS.ACTIVE NO

SCF.DEV.ATTR.HRO.EXCLUDE.LIST None

SCF.DEV.ATTR.HRO.INCLUDE.LIST None

SCF.DEV.EXCLUDE.LIST None

ResourcePak Base initialization parameters 37

Getting Started

SCF.DEV.INCLUDE.LIST None

SCF.DEV.MULTSS NO

SCF.DEV.WAITINT 60

SCF.DEV.OPTIMIZE.ENABLE NO

SCF.DEV.OPTIMIZE.PAV NO

SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST None

SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST None

SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST None

SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST Job names supplied in SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE None

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL None

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU None

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

SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX None

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

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

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

SCF.DEV.OPTIMIZE.PAV.TRACK.MIN None

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

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

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

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

SCF.DEV.OPTIMIZE.SMF.RECID NO

SCF.DEV.OPTIMIZE.VERBOSE NO

SCF.DSE.LIST DISable

SCF.DSE.xx.LIST None

SCF.DSE.SymmID.LIST None

SCF.DSE.SymmID.LIST=GATEkeeper=ccuu None

SCF.DSE.SymmID.xx.LIST None

SCF.DSE.SymmID.poolname.xx.LIST None

SCF.DSE.MAJOR None

SCF.DSE.MINOR None




Getting Started

SCF.DSE.WARNING None

SCF.GATEKEEPER.LIST None

SCF.GATEKEEPER.SymmID.LIST None

SCF.GNS.ACTIVE NO

SCF.GNS.WAITINT 7200

SCF.GPM.OSUB PERCENT

SCF.INI.COMMAND.MAX 255

SCF.INI.CPFX When //SCF$nnnn DD DUMMY is specified, nnnn becomes the default SCF commandprefix other than value SCF$EMC.

SCF.INI.CPFX.DD NO

SCF.INI.SCOPE SYSPLEX

SCF.LFC.LCODES.LIST None

SCF.LOG.CYLINDER No

SCF.LOG.DATACLAS None

SCF.LOG.MGMTCLAS None

SCF.LOG.RETAIN.COUNT 10

SCF.LOG.RETAIN.DAYS 10

SCF.LOG.STORCLAS None

SCF.LOG.TRACKS.PRI 10

SCF.LOG.TRACKS.SEC 50

SCF.MSC.ADCOPY.ONDROP NO

SCF.MSC.AUTO.RECOVER.RETRY None

SCF.MSC.CYCLE.TIME.WARN 60

SCF.MSC.ENABLE NO

SCF.MSC.GTFUSR.RECID 100 (hex)

SCF.MSC.GTFUSR.TRACE NO

SCF.MSC.MAX.LOCK.WAIT 1

SCF.MSC.OVERWRITE YES

SCF.MSC.PAVO NO

SCF.MSC.SDDFQ.TODA NO

SCF.MSC.SDDFQ.TOMF NO

SCF.MSC.SDDFQ.TOOS NO




Getting Started

SCF.MSC.VERBOSE NO

SCF.REG.MAX.ERRORS 9

SCF.REG.MAX.CONTROLLER.ERRORS 3

SCF.REG.WAITINT 30

SCF.SDV DISable

SCF.SDV.xx.LIST None

SCF.SDV.SymmID.LIST DISable

SCF.SDV.SymmID.LIST=GATEkeeper=ccuu None

SCF.SDV.SymmID.xx.LIST None

SCF.SDV.SymmID.poolname.xx.LIST None

SCF.SNAP.NOTIFY_POLLING 1

SCF.SNAP.NOTIFY_POLLTIME 1

SCF.SRV.GSM.ACTIVE YES

SCF.SRV.GSM.INTERVAL 15

SCF.SS.AUTO.RECOVER None

SCF.SS.AUTO.RECOVER.SymmID.srdfgrp None

SCF.SS.AUTO.RECOVER.BCV None

SCF.SS.AUTO.RECOVER.BCV.SymmID.srdfgrp None

SCF.SS.AUTO.RECOVER.ITRK 30

SCF.SS.AUTO.RECOVER.ITRK.SymmID None

SCF.SS.AUTO.RECOVER.JOBNAME None

SCF.SS.AUTO.RECOVER.JOBNAME.SymmID None

SCF.SS.AUTO.RECOVER.LPAR None

SCF.SS.AUTO.RECOVER.MINDIR 1

SCF.SS.AUTO.RECOVER.MINDIR.SymmID None

SCF.SS.AUTO.RECOVER.PREFIX None

SCF.SS.AUTO.RECOVER.PROC None

SCF.THN ENAble

SCF.THN.xx.LIST None

SCF.THN.SymmID.LIST DISable

SCF.THN.SymmID.LIST=GATEkeeper=ccuu None

SCF.THN.SymmID.xx.LIST None

SCF.THN.SymmID.poolname.xx.LIST None




Getting Started

SCF.TRACE.COMPRESS NO

SCF.TRACE.CYLINDER No

SCF.TRACE.DATACLAS None

SCF.TRACE.FLUSH.AT 75

SCF.TRACE.MEGS 1

SCF.TRACE.MGMTCLAS None

SCF.TRACE.RETAIN.COUNT 10

SCF.TRACE.RETAIN.DAYS 10

SCF.TRACE.STORCLAS None

SCF.TRACE.TRACKS.PRI None

SCF.TRACE.TRACKS.SEC None

SCF.TRU.DEBUG NO

SCF.TRU.DEV.EXCLUDE.LIST None

SCF.TRU.DEV.INCLUDE.LIST None

SCF.TRU.ENABLE YES

SCF.TRU.OFFLINE PROCESS

SCF.TRU.RECLAIM.DSFACTOR 1000

SCF.TRU.RECLAIM.DSPREFIX EMC.RECLAIM

SCF.TRU.RECLAIM.METHOD 1

SCF.TRU.RECLAIM.PGMNAME ESFTRURC

SCF.TRU.RECLAIM.POST.MAX 9999999

SCF.TRU.RECLAIM.POST.MIN 100

SCF.TRU.RECLAIM.POST.PCT 50

SCF.TRU.RECLAIM.POST.TYPE FREESPACE

SCF.TRU.RECLAIM.SCRATCH.WAIT 0

SCF.TRU.RECLAIM.STCNAME None

SCF.TRU.RECLAIM.STRESS.MONITOR YES

SCF.TRU.RECLAIM.STRESS.WAIT 5

SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT 3000 (30 seconds)

SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT 150

SCF.TRU.RECLAIM.SYSVTOC.WAIT 3000 (30 seconds)

SCF.TRU.RECLAIM.TIMELIMIT.LIST None

SCF.TRU.RECLAIM.TASK.LIMIT 10




Getting Started

SCF.TRU.SCAN.PGMNAME ESFTRURC

SCF.TRU.SCAN.STCNAME None

SCF.TRU.SCAN.TASK.LIMIT 10

SCF.TRU.SCRATCH.POST.MAX 9999999

SCF.TRU.SCRATCH.POST.MIN 100

SCF.TRU.SCRATCH.POST.PCT 50

SCF.TRU.SCRATCH.POST.TYPE FREESPACE

SCF.TRU.SCRATCH.RECLAIM 20

SCF.TRU.THICKR1 YES

SCF.WORK.HLQ SCFSERVE

SCF.WORK.UNIT SYSDA

SCF.WORK.VOLSER None

SCF.WPA.EXCLUDE.CNTRL[.LIST] None

SCF.WPA.INCLUDE.CNTRL[.LIST] All groups on all VMAX systems

SCF.WPA.MONITOR DISable

SCF.WPA.MSGLEVEL BASIC

SCF.WPA.POLL.INTERVAL 5 minutes

SCF.WPA.SMF DISABLE

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

SCF.WPA.SMF.RECORD None

SCF.WPA.STYPES ALL




Getting Started

SRDF/A Monitor (ASY)

SCF.ASY.MONITOREnables or disables the SRDF/A Monitor:

◆ When set to ENAble, the SRDF/A Monitor actively monitors SRDF/A sessions.

◆ When set to DISable, the SRDF/A Monitor starts, but then becomes inactive, waiting for commands.

Note: “Monitoring SRDF/A (SRDF/A Monitor)” on page 657 describes the SRDF/A Monitor.

After changing the parameter value, activate it by issuing the INI,REFRESH command described in “INI,REFRESH” on page 197 and the ASY,REFRESH command described in “ASY,REFRESH” on page 670.

Valid values

ENAble|DISable

Default

DISable

Example

SCF.ASY.MONITOR=ENA

SCF.ASY.POLL.INTERVALSets the time interval (in minutes) for the SRDF/A Monitor to poll the VMAX system status.



Valid values

1 to 60

Default

5

Example

SCF.ASY.POLL.INTERVAL=4


Getting Started

SCF.ASY.SECONDARY_DELAYSets the maximum duration of the secondary delay (in seconds) for the SRDF/A Monitor.



Valid values

60 to 3600

Default

120

Example

SCF.ASY.SECONDARY_DELAY=180

SCF.ASY.SMF.POLLDefines a multiplier value by which the value of the SCF.ASY.POLL.INTERVAL parameter is multiplied when calculating how often the SRDF/A Monitor writes SMF interval records.

For example, if the SCF.ASY.POLL.INTERVAL parameter is set to 5 and the SCF.ASY.SMF.POLL parameter is set to 3, the SRDF/A Monitor obtains and writes the SMF interval records every 5*3=15 minutes.

Note: “SMF record format” on page 665 describes the SRDF/A Monitor SMF records.


Valid values

1 to 24

Default

6

Example

SCF.ASY.SMF.POLL=3


Getting Started

SCF.ASY.SMF.RECORDDefines the number of an SMF record that the SRDF/A Monitor writes. If not specified, the SRDF/A Monitor does not write any SMF records.

Note: “SMF record format” on page 665 describes the SRDF/A Monitor SMF records.


Valid values

128 to 255

Default

None

Example

SCF.ASY.SMF.RECORD=255

SCF.ASY.USEREXITDefines the name of a user exit to link to in the event of a changed state. If not specified, the SRDF/A Monitor does not call any user exit.

Note: “Optional user exit” on page 665 describes SRDF/A Monitor user exits.


Valid values

Up to 8 alphanumeric characters

Default

None

Example

SCF.ASY.USEREXIT=SRDFAUX


Getting Started

Controller specification (CNTRL)

SCF.CNTRL.EXCLUDE.LISTExcludes all devices in the specified VMAX systems from processing.

You can specify a single value, a comma-separated list, a range of values separated by a hyphen, or use the keyword ALL to exclude all VMAX systems. You can also specify this parameter repeatedly to exclude multiple VMAX systems.

Note: This parameter overrides any existing device include lists.

Syntax

SCF.CNTRL.EXCLUDE.LIST=SymmID

SCF.CNTRL.EXCLUDE.LIST=SymmID,SymmID,...,SymmID

SCF.CNTRL.EXCLUDE.LIST=SymmID-SymmID

SCF.CNTRL.EXCLUDE.LIST=ALL

Where:

SymmID

A 12-character VMAX system serial number.

Default

None

Example

SCF.CNTRL.EXCLUDE.LIST=000000006205,000000004010

SCF.CNTRL.INCLUDE.LIST

IMPORTANT

SCF.CNTRL.INCLUDE.LIST is only valid when the SCF.CNTRL.EXCLUDE.LIST parameter is set to ALL.

Includes all devices in the specified VMAX systems into processing. You can specify this parameter repeatedly to include multiple VMAX systems.

Valid values

12-character VMAX system serial numbers

Note: This parameter overrides any existing VMAX system exclude lists.

Default

None

Example

SCF.CNTRL.INCLUDE.LIST=000195601010


Getting Started

Cross-System Communication (CSC)

SCF.CSC.ACTIVE Enables or disables the CSC (Cross-System Communications) component of SCF.

Note: “Controlling Communications (CSC)” on page 205 describes the CSC component.

Various products and features that require CSC to be active can override the SCF.CSC.ACTIVE=NO specification. This means that under certain conditions, CSC is activated automatically, forcing the setting to SCF.CSC.ACTIVE=YES.

Valid values

YES|NO

Default

NO

Example

SCF.CSC.ACTIVE=YES

SCF.CSC[.{SymmID|RMT}].ACTIVEPOLLDefines the active polling period for the CSC component of SCF. When SymmID or RMT is not specified, the parameter value applies to all VMAX systems.

Note: “Polling VMAX systems” on page 208 describes CSC polling periods.

SymmID

The serial number of the VMAX system to which the parameter value applies. This can be 12 characters or just the last 5 characters of the VMAX system serial number.

Note: Specify the 12-character number when multiple VMAX systems use the same last 5 characters.

For a remote VMAX system, SymmID overrides RMT.

RMT

Indicates that the parameter value applies to all remotely connected VMAX systems.

Note: EMC recommends not to specify [.{SymmID|RMT}] as this allows all VMAX systems to use the same parameter value.

Valid values

A number that represents a unit of 1/10th of a second. The number must be less than the idle polling period set with the SCF.CSC[.{SymmID|RMT}].IDLEPOLL parameter.

Note: Remote VMAX systems use a value of 2*SCF.CSC[.{SymmID|RMT}].ACTIVEPOLL if a more specific keyword is not specified.


Getting Started

Default

5 (.5 seconds) for local VMAX systems, 10 (1 second) for remote VMAX systems

Example

SCF.CSC.ACTIVEPOLL=4

SCF.CSC[.SymmID].ATTNACTIVE

IMPORTANT

The SCF.CSC[.SymmID].ATTNACTIVE parameter requires Enginuity 5876 or HYPERMAX OS 5977.

Enables or disables use of the Enginuity Attention feature for host notification. When SymmID is not specified, the parameter value applies to all VMAX systems.

Note: “Enginuity Attention” on page 210 describes the Enginuity Attention feature.

SymmID



After changing the parameter value, activate it by issuing the INI,REFRESH command described in “INI,REFRESH” on page 197.

Valid values

YES|NO

Default

YES

Example

SCF.CSC.ATTNACTIVE=YES

SCF.CSC[.SymmID].ATTNPATHGRP

IMPORTANT

The SCF.CSC[.SymmID].ATTNPATHGRP parameter requires Enginuity 5876 or HYPERMAX OS 5977.

Allows or disallows CSC to establish a pathgroup to its offline gatekeeper if there are no other online devices to the VMAX system that support the CSC Attention interface.

Note: “Establishing path groups” on page 210 describes how CSC establishes pathgroups.


Getting Started

SymmID



After changing the parameter value, activate it by issuing the INI,REFRESH command described in “INI,REFRESH” on page 197 and then the CSC,REFRESH command described in “CSC,REFRESH” on page 220.

Valid values

YES|NO

Default

NO

Example

SCF.CSC.ATTNPATHGRP=YES

SCF.CSC[.{SymmID|RMT}].EXPIRECYCLEDefines the number of inactivity cycles after which the host is eligible to be removed (unregistered) from CSC.

Note: “Polling hosts” on page 209 describes host polling functionality of CSC.

For example, SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE=5 causes the host to be eligible for removal after 5 inactivity cycles. With the 5-second idle polling period, this would be a 25 second period.

Note the following when specifying SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE parameter values:

◆ If you specify a value less than 5, then 5 is used.

◆ If you specify a value greater than 30, then 30 is used.

◆ If you specify a value of zero or do not specify any value, then 20 is used.

SymmID





Getting Started

RMT



Valid values

5 to 30

Default

20

Example

SCF.CSC.EXPIRECYCLE=15

SCF.CSC.GATEKEEPER.LISTLists gatekeepers for CSC communication to SCF-accessible VMAX systems.

Note: “Selecting gatekeepers” on page 208 describes CSC gatekeepers.

If you specify the SCF.CSC.GATEKEEPER.SymmID.LIST parameter for a VMAX system, the SCF.CSC.GATEKEEPER.LIST parameter is ignored for the VMAX system.


Valid values

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

Default

None

Example

SCF.CSC.GATEKEEPER.LIST=A04A

SCF.CSC.GATEKEEPER.SymmID.LISTLists gatekeepers for CSC communication to SCF-accessible VMAX systems. You can choose specific VMAX devices for each VMAX system.

If a gatekeeper device cannot be located on this list, then CSC retries at intervals until one of the listed devices becomes available.


Getting Started

SymmID




Valid values

VMAX device numbers and ranges of VMAX device numbers

Default

None

Example

SCF.CSC.GATEKEEPER.000184500309.LIST=000000-000002

Or, specify the following if the last 5 digits of the serial number are not used by another VMAX system:

SCF.CSC.GATEKEEPER.00309.LIST=000000-000002

SCF.CSC[.{SymmID|RMT}].IDLEPOLLSets the idle polling period (in seconds).

Note: “Polling VMAX systems” on page 208 describes CSC polling periods.

SCF.CSC[.{SymmID|RMT}].IDLEPOLL determines the worst-case response time for CSC requests. If you notice elongated response times for CSC requests, reduce this value.

After changing the parameter value, restart SCF to activate it.

SymmID




RMT




Getting Started

Valid values

0 to 127

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

Default

5 seconds for local VMAX systems, 10 seconds for remote VMAX systems

Example

SCF.CSC.IDLEPOLL=4

SCF.CSC.INSTANCEIdentifies the SCF instance used to process a communication request.

Note: “Working with multiple SCF instances” on page 214 describes using multiple SCF instances.

Valid values

0 to 255

Default

0

Example

SCF.CSC.INSTANCE=25

SCF.CSC[.{SymmID|RMT}].MITPERIODSets the Missing Interval Timing (MIT) period.

Note: “Polling hosts” on page 209 describes MIT periods.

Note the following when specifying SCF.CSC.EXPIRECYCLE parameter values:

◆ 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 any value, then 30 is used.

SymmID





Getting Started

RMT



Valid values

10 to 60

Default

30

Example

SCF.CSC.MITPERIOD=25

SCF.CSC.REFORMATInstructs CSC to reformat the communication area used by CSC in the VMAX system.

Note: “Controlling Communications (CSC)” on page 205 describes CSC.

If there are registered systems using the communication area, this parameter is ignored.

Use SCF.CSC.REFORMAT only when directed by EMC Customer Support.

Valid values

ALL|NO

Default

NO

Example

SCF.CSC.REFORMAT=ALL

SCF.CSC[.{SymmID|RMT}].SELTIMEOUTSets the timeout period (in seconds) before releasing the CSC VMAX system.

Note: “Controlling Communications (CSC)” on page 205 describes CSC.

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


Getting Started

SymmID




RMT



Valid valuesA number that represents seconds. The minimum value is 10.

Default60

ExampleSCF.CSC.SELTIMEOUT=55

SCF.CSC[.{SymmID|RMT}].VERBOSEEnables or disables the CSC verbose mode.

Note: “Verbose messaging” on page 216 describes the CSC verbose mode.

SymmID




RMT



Valid valuesYES|NO

DefaultNO

ExampleSCF.CSC.VERBOSE=NO


Getting Started

AutoSwap (DAS)

SCF.DAS.ACTIVEEnables or disables AutoSwap running within the SCF address space, which allows for products that rely on AutoSwap.

Note: “Running AutoSwap in SCF address space” on page 151 provides information on running AutoSwap within the SCF address space.

Note: As of version 4.2, z/OS Migrator requires the SCF.DAS.ACTIVE entry 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.

Valid values

YES|NO

Default

NO

Example

SCF.DAS.ACTIVE=YES

Device specification (DEV)

SCF.DEV.ATTR.HRO.EXCLUDE.LISTIdentifies devices to be excluded from the list of HRO-managed devices defined by the SCF.DEV.ATTR.HRO.INCLUDE.LIST parameter.

Note: “HRO-controlled devices in AutoSwap groups” on page 164 describes HRO-managed devices.

You can specify this parameter repeatedly to include all of the desired devices.


Valid values

z/OS device numbers and ranges of z/OS device numbers.

The z/OS device number applies to all subchannel sets so that the corresponding special devices in alternate subchannel sets are also excluded. For example, A000 also excludes any special devices in 0A000, 1A000, and so forth.

Default

None


Getting Started

Example

The following two statements are equivalent to SCF.DEV.ATTR.HRO.INCLUDE.LIST=A000-A049,A056:

SCF.DEV.ATTR.HRO.INCLUDE.LIST=A000-A056SCF.DEV.ATTR.HRO.EXCLUDE.LIST=A04A-A055

SCF.DEV.ATTR.HRO.INCLUDE.LISTIdentifies devices to be managed by the Host Read Only (HRO) feature.

Note: “HRO-controlled devices in AutoSwap groups” on page 164 describes HRO-managed devices.

You can specify this parameter repeatedly to include all of the required devices.


Valid values

z/OS device numbers and ranges of z/OS device numbers.

The z/OS device number applies to all subchannel sets so that the corresponding special devices in alternate subchannel sets are also included. For example, A000 also includes any special devices in 0A000, 1A000, and so forth.

Default

None

Example

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

SCF.DEV.EXCLUDE.LIST Identifies devices that are not accessed by SCF.

Note: “Using Symmetrix Control Facility (SCF)” on page 157 describes SCF.

You can specify this parameter repeatedly to exclude the required number of devices.

After changing the parameter value, activate it by issuing the INI,REFRESH command described in “INI,REFRESH” on page 197 and then the DEV,REFRESH command described in “DEV,REFRESH” on page 192.

Valid values


Default

None

Example

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


Getting Started

SCF.DEV.INCLUDE.LIST Identifies devices to be excluded from the list of devices defined by the SCF.DEV.EXCLUDE.LIST parameter.


You can specify this parameter repeatedly to include the required number of devices.

This parameter overrides any existing device exclude lists, no matter where the SCF.DEV.INCLUDE.LIST statement appears.

Valid values


Default

None

Example

SCF.DEV.INCLUDE.LIST=A047

SCF.DEV.MULTSS

IMPORTANT

This parameter is required when using AutoSwap to swap between similar device numbers in alternate subchannel sets.

Determines use of subchannel set devices by SCF.

◆ YES — SCF discovers and uses special devices in the alternate subchannel set.

◆ NO — SCF only discovers the normal base devices in the currently active subchannel set.


After changing the parameter value, activate it by restarting SCF.

Valid values

YES|NO

Default

NO

Example

SCF.DEV.MULTSS=YES


Getting Started

SCF.DEV.WAITINTSets the device discovery check interval (in minutes).

Note: “Device discovery” on page 162 describes SCF device discovery.

Valid values

1 to 1400

Default

60

Example

SCF.DEV.WAITINT=45


Getting Started

zBoost PAV Optimizer (DEV.OPTIMIZE)

SCF.DEV.OPTIMIZE.ENABLEEnables (YES) or disables (NO) zBoost PAV Optimizer.

The DEV,OPTIMIZE ENABLE and DEV,OPTIMIZE DISABLE commands (described in “DEV,OPTIMIZE ENABLE” on page 347 and “DEV,OPTIMIZE DISABLE” on page 347) 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.

Valid values

YES|NO

Default

NO

Example

SCF.DEV.OPTIMIZE.ENABLE=YES

SCF.DEV.OPTIMIZE.PAVDetermines 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 329 describes the Passive mode.

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

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

Valid values

YES|NO|Read|Write|PASsive|MONitor

Default

NO

Example

SCF.DEV.OPTIMIZE.PAV=R


Getting Started

SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LISTExcludes 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 329 discusses device selection for zBoost PAV Optimizer.

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

Valid values

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

Example

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

SCF.DEV.OPTIMIZE.PAV.INCLUDE.LISTSelects 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.

Valid values

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

Example

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


Getting Started

SCF.DEV.OPTIMIZE.PAV.JOBNAME.LISTLimits 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 330 discusses started task/job limitation.


Valid values

A comma-separated list of started task or job names. WIldcarding is not allowed.

Default

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

Example

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

SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LISTDefines a list of job name prefixes eligible for zBoost PAV Optimizer processing.

Note: “Limiting optimization by started task/job” on page 330 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.

Valid values

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

Example

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

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICEDefines the quiesce point for the number of constituent I/Os active for the same base device.

Note: “Setting quiesce points” on page 331 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).


Getting Started

Valid values

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

Default

None.

Example

To 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.GLOBALDefines the quiesce point for the number of globally active constituent I/Os.


Valid values

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

Default

None.

Example

To 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.LCUDefines 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).

Valid values


Default

None.

Example

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

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


Getting Started

SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCTDefines 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.

Valid values


Default

None.

Example

To 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.MAXSets 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 is not specified.

Note: “Controlling number of splits/constituent I/Os” on page 331 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.

Valid values

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

Default

None.


Getting Started

Example

To 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.READDefines 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 331 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.

Valid values

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

Example

To 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.WRITEDefines 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 331 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.

Valid values

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


Getting Started

Example

To 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.LISTSelects the devices on which zBoost PAV Optimizer operates by specifying the name of the SMS storage group that contains the devices.




Valid values

A list of comma-separated SMS group names

Default

None. No devices are included by default.

Example

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

SCF.DEV.OPTIMIZE.PAV.TRACK.MINSets 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 330 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.

Valid values

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

Example

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


Getting Started

SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READDefines the minimum number of tracks before PAV optimization is considered on read channel programs.

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

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

Valid values

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

Default

0 (no minimum track number)

Example

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

SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITEDefines the minimum number of tracks before PAV optimization is considered on write channel programs.

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

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

Valid values

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

Default

0 (no minimum track number)

Example

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

SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LISTSelects the volumes on which zBoost PAV Optimizer operates by applying a volser mask.



Getting Started



Valid values

A 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.LISTSelects 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.



Valid values

A volser or a comma-separated list of volsers

Default

None. No volsers are included by default.


Getting Started

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

SCF.DEV.OPTIMIZE.SMF.RECIDDetermines 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 334 describes SMF recording for zBoost PAV Optimizer.

Valid values

NO|smf_record_id

Default

NO

Example

SCF.DEV.OPTIMIZE.SMF.RECID=130

SCF.DEV.OPTIMIZE.VERBOSEEnables 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.

Valid values

YES|NO

Default

NO

Example

SCF.DEV.OPTIMIZE.VERBOSE=YES


Getting Started

Delta-Set Extension Pool Capacity Monitor (DSE)

SCF.DSE.LISTEnables or disables the DSE Monitor.

Note: “Monitoring DSE Pools (DSE Monitor)” on page 611 describes the DSE Monitor.

The DSE Monitor is enabled by default. To disable the DSE Monitor, specify DISABLE explicitly.

Valid values

ENAble|DISable

Default

ENAble

Example

SCF.DSE.LIST=DISable

SCF.DSE.xx.LISTProvides monitoring settings for the DSE Monitor.


The SCF.DSE.xx.LIST parameter is used to define settings for a global interval.

Syntax

SCF.DSE.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=seconds|[ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx

The number of the threshold interval to which other subparameters apply. Valid values are from 01 to 99. The parameter must start at 01 and increase by one for each interval. Gaps are not permitted in the sequence.

ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)

Determines the action performed within the interval:

NONE

No action.


Getting Started

MESsage(string)

Issues string. This is an alphanumeric value. Special characters are not permitted. The message string is limited to 8 characters.

STOPVDEV

Stops virtual device snaps.

USEREXIT(exit_name)

Specifies the name of a user exit module link.

Note: “Optional user exit” on page 615 describes using exits in the DSE Monitor.

The exit name is limited to 8 characters and must meets module naming standards. The module must reside in an SCF-accessible library.

DURation=seconds

The duration of time (in seconds). Valid values are from 1 to 86400. The default value is 43200 seconds (12 hours).

FREQuency={NONE|ONCE|REPEAT}

Sets the number of times to perform the action within the current interval:

NONE

The action is not performed (the ACTION statement is ignored).

ONCE

The action is performed only once.

REPEAT

The action is repeated.

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 DSE 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).

PERcent=(low_percent[,high_percent])

A pool usage percentage or range defined by the low_percent and/or high_percent values, each from 0 to 100.

Note: If the percentage value overlaps two ranges (in two separate intervals), the action set for the interval with a higher range is performed.


Getting Started

Example

SCF.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(GOOD)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

Note: For a detailed explanation of the example, refer to “Example” on page 616.

SCF.DSE.SymmID.LISTEnables or disables the DSE Monitor for a specific VMAX system.


SymmID



Valid values

ENAble|DISable

Default

None

Example

SCF.DSE.18771.LIST=DIS

SCF.DSE.SymmID.LIST=GATEkeeper=ccuuAllows the DSE Monitor to use a special gatekeeper device in the VMAX system.


SymmID



ccuu

The z/OS device number used as the SCF gatekeeper for the channel-attached device.


Getting Started

Valid values

z/OS device number

Default

None

Example

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

SCF.DSE.SymmID.xx.LISTProvides monitoring settings of the DSE Monitor for an individual VMAX system.


The VMAX system interval statements provide the interval setting for individual VMAX systems.

Syntax

SCF.DSE.SymmID.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=seconds|[ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx




NONE

No action.

MESsage(string)


STOPVDEV


USEREXIT(exit_name)




Getting Started


DURation=seconds




NONE


ONCE


REPEAT







SymmID



Example

SCF.DSE.18771.01.LIST = PERCENT=(0,80)SCF.DSE.18771.01.LIST = DURATION=10SCF.DSE.18771.01.LIST = ACTION=MES(PROC1)


Getting Started

SCF.DSE.SymmID.poolname.xx.LISTProvides monitoring settings of the DSE Monitor for an individual DSE pool within the VMAX system.


The pool interval statements provide the interval setting for individual pools within a VMAX system.

Syntax

SCF.DSE.SymmID.poolname.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=seconds|[ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx




NONE

No action.

MESsage(string)


STOPVDEV


USEREXIT(exit_name)




DURation=seconds





Getting Started

NONE


ONCE


REPEAT







SymmID



poolname

The name of the DSE pool to which the settings apply.

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.

Example

SCF.DSE.18771.DEFAULT_POOL.01.LIST = PERCENT=(0,80)SCF.DSE.18771.DEFAULT_POOL.01.LIST = DURATION=10SCF.DSE.18771.DEFAULT_POOL.01.LIST = ACTION=MES(PROC1)


Getting Started

SCF.DSE.MAJOR Sets the threshold, in number of minutes, to issue a major alert that DSE pool spillover has occurred. This value must exceed the value of the SCF.DSE.MINOR parameter.


Valid values

02 to 720

Default

None

Example

SCF.DSE.MAJOR=60

SCF.DSE.MINOR Sets the threshold, in number of minutes, to issue a minor alert that DSE pool spillover has occurred. This value must exceed the value of the SCF.DSE.WARNING parameter.


Valid values

02 to 720

Default

None

Example

SCF.DSE.MINOR=40

SCF.DSE.WARNING Sets the threshold, in number of minutes, to issue a warning that DSE pool spillover has occurred.


Valid values

02 to 720

Default

None

Example

SCF.DSE.WARNING=20


Getting Started

Gatekeeper specification (GATEKEEPER)

SCF.GATEKEEPER.LISTLists gatekeepers for SCF.

Note: “Selecting gatekeepers” on page 208 provides information on gatekeepers.

Valid values

z/OS device numbers

Default

None

Example

SCF.GATEKEEPER.LIST=A02A

SCF.GATEKEEPER.SymmID.LISTLists gatekeepers that SCF uses for a specific VMAX system.

Note: When the SCF.GATEKEEPER.SymmID.LIST parameter is specified together with the SCF.GATEKEEPER.LIST parameter, the lists of gatekeepers are merged.

SymmID



After changing the parameter value, activate it by issuing the INI,REFRESH command described in “INI,REFRESH” on page 197 and then the DEV,REFRESH[,GATEKEEPERS] command described in “DEV,REFRESH” on page 192.

Valid values

VMAX device numbers and ranges of VMAX device numbers

Default

None

Example

SCF.GATEKEEPER.011203211419.LIST=000002


Getting Started

Group Name Services (GNS)

SCF.GNS.ACTIVEEnables or disables Group Name Services (GNS).

Note: “Managing Device Groups (GNS)” on page 233 describes GNS.

If you set SCF.GNS.ACTIVE to YES, set SCF.CSC.ACTIVE to YES as well.

If you set SCF.GNS.ACTIVE to NO or do not specify SCF.GNS.ACTIVE, GNS does not start.

Valid values

YES|NO

Default

NO

Example

SCF.GNS.ACTIVE=YES

SCF.GNS.WAITINTSets the period (in seconds) to automatically refresh in-memory GNS tables.

Note: “Managing Device Groups (GNS)” on page 233 describes GNS.

EMC recommends a periodic refresh for mixed environments that contain both open systems and mainframe groups.

Valid values

1 to 99999999

Default

7200

Example

SCF.GNS.WAITINT=2000


Getting Started

General Pool Management (GPM)

SCF.GPM.OSUBDetermines whether to calculate, set, and interpret the storage pool oversubscription rate as a percentage or a ratio.

Note: “Oversubscription rate” on page 422 describes oversubscription rates.

This parameter affects the following values:

◆ The MAXOSUB (maximum oversubscription rate) parameter of the POOLATTR command

◆ The ActO (actual oversubscription rate) and MaxO (maximum oversubscription rate) values on the QUERY POOLS display

If SCF.GPM.OSUB=PERCENT (default) is used, the MAXOSUB (maximum oversubscription rate) parameter of the POOLATTR command is specified as a percentage, and ActO (actual oversubscription rate) and MaxO (maximum oversubscription rate) values in the QUERY POOLS display are shown as percentages.

If SCF.GPM.OSUB=RATIO is used, the MAXOSUB parameter of the POOLATTR command is specified as a ratio, and the ActO and MaxO values in the QUERY POOLS display are shown as ratios.

Do not use SCF.GPM.OSUB=RATIO, since it is not compatible with Solutions Enabler.

Valid values

PERCENT|RATIO

Default

PERCENT

Example

SCF.GPM.OSUB=PERCENT


Getting Started

SCF initialization (INI)

SCF.INI.COMMAND.MAXSets the maximum number of concurrent operator commands that can be accepted by SCF before displaying the SCF0330E message.

Valid values

1 to 10000

Default

255

Example

SCF.INI.COMMAND.MAX=1000

SCF.INI.CPFXSets the command prefix for SCF.

Note: “Command Prefix Facility” on page 173 describes command prefixes.

Valid values

1 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, enclose the name in single quotes.

Default

When //SCF$nnnn DD DUMMY is specified, nnnn becomes the default SCF command prefix other than value SCF$EMC. If you want “EMC” as the SCF command prefix, specify SCF.INI.CPFX=EMC in the SCF INI file.

Example

SCF.INI.CPFX=@123


Getting Started

SCF.INI.CPFX.DDEnables or disables Command Prefix Facility (CPF):

◆ YES — CPF is activated.

◆ NO — CPF is not activated.

Note: “Command Prefix Facility” on page 173 describes Command Prefix Facility.

Valid values

YES|NO

Default

NO

Example

SCF.INI.CPFX.DD=YES

SCF.INI.SCOPEDetermines whether a command with the SCF command prefix can be routed for execution to another system in the sysplex:

◆ SYSPLEX — The command can be routed to a system in the sysplex.

◆ SYSTEM — The command is executed in the system LPAR on which the command is issued.

Note: “Command Prefix Facility” on page 173 describes command prefixes.

If the SCF.INI.SCOPE parameter is not specified, the command can be routed to a system in the sysplex.

Valid values

SYSTEM|SYSPLEX

Default

SYSPLEX

Example

SCF.INI.SCOPE=SYSPLEX


Getting Started

Licensing (LFC)

SCF.LFC.LCODES.LIST Stores Licensed Feature Codes (LFC) for host-based licenses.

Note: Refer to the following documents for information about licenses: - Mainframe Enablers Installation and Customization Guide- VMAX3 Family with HYPERMAX OS VMAX100, VMAX200, VMAX400 Product Guide- VMAX Family VMAX 10K, 20K, 40K Product Guide

Valid values

Licensed Feature Codes

Default

None

Example

SCF.LFC.LCODES.LIST=xxxx-xxxx-xxxx-xxxx


Getting Started

SCF log file (LOG)

SCF.LOG.CYLINDERDetermines that space allocations for the SCF log file must be made using cylinders instead of tracks.

Note: “SCF log and trace files” on page 174 describes the SCF log file.

This parameter overrides the SCF.LOG.TRACKS.PRI and the SCF.LOG.TRACKS.SEC parameters.

Valid values

Yes|No

Default

No

Example

SCF.LOG.CYLINDER=Y

SCF.LOG.DATACLAS Defines the SMS data class name to be used when allocating the SCF log file.


Valid values

1 to 8 characters

Default

None

Example

SCF.LOG.DATACLAS=PATLOAD

SCF.LOG.MGMTCLASDefines the SMS management class name to be used when allocating the SCF log file.


Valid values

1 to 8 characters

Default

None


Getting Started

Example

SCF.LOG.MGMTCLAS=FILETRIM

SCF.LOG.RETAIN.COUNTSets the number of SCF log files to retain.


Valid values

1 to 9999

Default

10

Example

SCF.LOG.RETAIN.COUNT=20

SCF.LOG.RETAIN.DAYSSets the number of days to retain an SCF log file.


Valid values

1 to 9999

Default

10

Example

SCF.LOG.RETAIN.DAYS=30

SCF.LOG.STORCLAS Defines the SMS storage class name to be used when allocating the SCF log file.


Valid values

1 to 8 characters

Default

None

Example

SCF.LOG.STORCLAS=LOGTERM


Getting Started

SCF.LOG.TRACKS.PRI Sets the number of tracks to be primarily allocated for the SCF log file.


If the SCF.LOG.CYLINDER parameter is set to Yes, the allocation is made using cylinders instead of tracks.

Valid values

1 to 9999

Default

10

Example

SCF.LOG.TRACKS.PRI=12

SCF.LOG.TRACKS.SEC Sets the number of tracks to be secondarily allocated for the SCF log file.


If the SCF.LOG.CYLINDER parameter is set to Yes, the allocation is made using cylinders instead of tracks.

Valid values

1 to 9999

Default

50

Example

SCF.LOG.TRACKS.SEC=45


Getting Started

Multi-Session Consistency (MSC)

SCF.MSC.ADCOPY.ONDROPWhether to switch devices in the MSC group to the Adaptive Copy disk mode after an SRDF/A failure.

Note: “Managing SRDF/A MSC” on page 685 describes MSC.

When set to YES, the following SRDF Host Component command is issued to each SRDF group in the MSC group:

SC VOL,LCL(gatekeeper,srdfgrp),ADCOPY-DISK,ALL,CQNAME=mscgrp

Where:

◆ gatekeeper is the MSC gatekeeper device.

◆ srdfgrp is the SRDF group.

◆ mscgrp is the first eight bytes of the MSC group name.

Valid values

YES|NO

Default

NO

Example

SCF.MSC.ADCOPY.ONDROP=YES

SCF.MSC.AUTO.RECOVER.RETRYSets the number of retries for the SRDF Automated Recovery feature.

Note: The SRDF Host Component for z/OS Product Guide describes the SRDF Automated Recovery feature.

When SRDF Automated Recovery is enabled, the status of each SRDF/A group is checked at the completion of phase 1 recovery jobs. If the retry limit has not been reached, SRDF Automated Recovery is rerun for each inactive group.

Valid values

0-9

“0” disables Auto Recovery retry. An invalid value results in a limit of 1.

Default

None

Example

SCF.MSC.AUTO.RECOVER.RETRY=5


Getting Started

SCF.MSC.CYCLE.TIME.WARNSets the time interval (in minutes) to issue a warning message when checking for a delay in MSC cycle time.

Note: “Managing SRDF/A MSC” on page 685 describes MSC-related features of SCF.

If the time since the last cycle switch exceeds the specified value, the SCF1591W message 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.

Valid values

5 to 60

Default

60

Example

SCF.MSC.CYCLE.TIME.WARN=10

SCF.MSC.ENABLEEnables or disables MCS:

◆ YES — Activates the MSC environment.

◆ NO — Suppresses MSC environment activation.


Valid values

YES|NO

Default

NO

Example

SCF.MSC.ENABLE=YES

SCF.MSC.GTFUSR.RECIDDefines the GTF (Generalized Trace Facility) USR record number for GTF USR tracing enabled for MSC.

Note: “Tracing and messaging” on page 688 describes GTF USR tracing.

This value is also specified in the GTF USRP field.


Getting Started

Valid values

0 to 3FF (hex)

Default

100 (hex)

Example

SCF.MSC.GTFUSR.RECID=128

SCF.MSC.GTFUSR.TRACEEnables or disables GTF (Generalized Trace Facility) USR tracing for MSC.

Note: “Tracing and messaging” on page 688 describes GTF USR tracing.

Collection of GTF user records also requires GTF to be active with the TRACE=USRP and USRP=(nnn) parameters specified.

Valid values

YES|NO

Default

NO

Example

SCF.MSC.GTFUSR.TRACE=YES

SCF.MSC.MAX.LOCK.WAITSets the duration of holding a VMAX level lock for MSC.


When running MSC with high availability without sharing system enqueues, the VMAX level lock that is received to update certain structures can be stolen since it takes longer than one minute to initialize the SDDF structures. The SCF.MSC.MAX.LOCK.WAIT parameter allows you to change the default time to hold the lock.

Valid values

1 to 720

Default

1

Example

SCF.MSC.MAX.LOCK.WAIT=30


Getting Started

SCF.MSC.OVERWRITEWhether to overwrite MSC scratch areas and multi-box lists.


Overwriting scratch areas and multi-box lists allows MSC or SRDF/Star to start when valid data is found in these areas.

If valid scratch data is found, the SCF147AR message 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, the SCF147BR message is returned to allow you to overwrite the data in the multi-box lists in a similar manner.

Valid values

YES|NO

Default

YES

Example

SCF.MSC.OVERWRITE=NO

SCF.MSC.PAVOEnables (YES) or disables (NO) zBoost PAV Optimizer support for MSC.

Note: “Optimizing Multi-Track I/Os (zBoost PAV Optimizer)” on page 323 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.

Valid values

YES|NO

Default

NO

Example

SCF.MSC.PAVO=YES


Getting Started

SCF.MSC.SDDFQ.TODAEnables running remote SDDF queries on disk adapters in the MSC environment.


When set to YES, the system looks for patch 30489 on Site A, Site B, and Site C of the SRDF/Star configuration.

If the patch is present on all the three VMAX systems, then remote SDDF queries are run to the disk adapter(s). Otherwise, the SCF1565W message is issued.

Note: The 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 is found, remote SDDF queries are run on the remote SRDF director.EMC recommends using SCF.MSC.SDDFQ.TODA. When TODA is not possible, then specify either TOMF for mainframe or TOOS for open systems. The specified setting must be valid for all VMAX systems in the MSC session.

Valid values

YES|NO

Default

NO

ExampleSCF.MSC.SDDFQ.TODA=YES

SCF.MSC.SDDFQ.TOMFEnables running remote SDDF queries on mainframe host adapter(s) in the MSC environment.


When set to YES, then system looks for mainframe host adapter(s). If none are present, the SCF1566W message is issued. If any are found, remote SDDF queries are run to the mainframe host adapter(s).

Note: The 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 are run on the remote SRDF director.EMC recommends using SCF.MSC.SDDFQ.TODA. When TODA is not possible, then specify either TOMF for mainframe or TOOS for open systems. The specified setting must be valid for all VMAX systems in the MSC session.

Valid values

YES|NO

Default

NO


Getting Started

ExampleSCF.MSC.SDDFQ.TOMF=YES

SCF.MSC.SDDFQ.TOOSEnables running remote SDDF queries on open systems host adapter(s) in the MSC environment.


When set to YES, then system looks for open systems host adapter(s). If none are present, the SCF1567W message is issued. If any are found, remote SDDF queries are run to the mainframe host adapter(s).

Note: The 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 are run on the remote SRDF director.EMC recommends using SCF.MSC.SDDFQ.TODA. When TODA is not possible, then specify either TOMF for mainframe or TOOS for open systems. The specified setting must be valid for all VMAX systems in the MSC session.

Valid values

YES|NO

Default

NO

ExampleSCF.MSC.SDDFQ.TOOS=YES

SCF.MSC.VERBOSEEnables or disables output 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. Set this parameter only when requested by EMC Customer Support.


Valid values

YES|NO

Default

NO

ExampleSCF.MSC.VERBOSE=YES


Getting Started

Feature registration (REG)

SCF.REG.MAX.ERRORSSets the maximum allowable number of total errors for registration. When this value is reached, registration is disabled.

Valid values

1 to 9999

Default

9

Example

SCF.REG.MAX.ERRORS=300

SCF.REG.MAX.CONTROLLER.ERRORSSets the maximum allowable number of VMAX system errors for registration. When this value is reached, registration is disabled for the VMAX system.

Valid values

1 to 9999

Default

3

Example

SCF.REG.MAX.CONTROLLER.ERRORS=300

SCF.REG.WAITINTSets the registration check wait interval (in minutes).

Valid values

1 to 1400

Default

30

Example

SCF.REG.WAITINT=10


Getting Started

Snap Pool Capacity Monitor (SDV)

SCF.SDVEnables or disables the SDV Monitor.

IMPORTANT


Note: “Monitoring Snap Pools (SDV Monitor)” on page 603 describes the SDV Monitor.

The SDV Monitor is enabled by default. To disable the SDV Monitor, specify DISABLE explicitly.

Valid values

ENAble|DISable

Default

ENAable

Example

SCF.SDV=DISABLE

SCF.SDV.xx.LISTProvides monitoring settings for the SDV Monitor.

IMPORTANT



The SCF.SDV.xx.LIST parameter is used to define settings for a global interval.

Syntax

SCF.SDV.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=seconds|[ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx



Getting Started




DURation=minutes

The duration of time (in minutes). Valid values are from 1 to 1440. The default value is 720 minutes (12 hours).



NONE

No action.

MESsage(string)

Issues message_string. This is an alphanumeric value. Special characters are not permitted. The message string is limited to 8 characters.

STOPVDEV


USEREXIT(exit_name)


Note: “Optional user exit” on page 606 describes using exits in the SDV Monitor.




NONE


ONCE


REPEAT




Getting Started

For instance, when the SDV 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).

Example

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

Note: For a detailed explanation of the example, refer to “Example” on page 616.

SCF.SDV.SymmID.LISTEnables or disables the SDV Monitor for a specific VMAX system.

IMPORTANT



SymmID



Valid values

ENAble|DISable

Default

DISable

Example

SCF.SDV.18773.LIST=ENA


Getting Started

SCF.SDV.SymmID.LIST=GATEkeeper=ccuuAllows the SDV Monitor to use a special gatekeeper device in the VMAX system.

IMPORTANT



SymmID



ccuu

the z/OS device number used as the SCF gatekeeper for the channel-attached device.

Valid values

z/OS device number

Default

None

Example

SCF.SDV.18773.LIST=GATE=423F

SCF.SDV.SymmID.xx.LISTProvides monitoring settings of the SDV Monitor for an individual VMAX system.

IMPORTANT




Syntax

SCF.SDV.SymmID.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=minutes|[ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]


Getting Started

Where:

xx





DURation=minutes




NONE

No action.

MESsage(string)


STOPVDEV


USEREXIT(exit_name)






NONE


ONCE


REPEAT



Getting Started



SymmID



Example

SCF.SDV.18771.01.LIST = PERCENT=(0,80)SCF.SDV.18771.01.LIST = DURATION=10SCF.SDV.18771.01.LIST = ACTION=MES(PROC1)

SCF.SDV.SymmID.poolname.xx.LISTProvides monitoring settings of the SDV Monitor for an individual save device pool within the VMAX system.

IMPORTANT




Syntax

SCF.SDV.SymmID.poolname.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=minutes|[ACTION=NONE|MESsage(string)|STOPVDEV|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx



Getting Started




DURation=minutes




NONE

No action.

MESsage(string)


STOPVDEV


USEREXIT(exit_name)






NONE


ONCE


REPEAT




Getting Started


SymmID



poolname

The name of the save device pool to which the settings apply.


Example

SCF.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)


Getting Started

SNAP Monitor (SNAP)

SCF.SNAP.NOTIFY_POLLINGSets 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.

Note: The TimeFinder/Clone Mainframe Snap Facility Product Guide provides information on the SNAP functionality.

Valid values

1 to 21474836

Default

1

Example

SCF.SNAP.NOTIFY_POLLING=900

SCF.SNAP.NOTIFY_POLLTIMESets the delay, in seconds, between snap notification polls.

Note: The TimeFinder/Clone Mainframe Snap Facility Product Guide provides information on the SNAP functionality. See the description of the NOTIFYwhencomplete parameter.

Default

1

Example

SCF.SNAP.NOTIFY_POLLTIME=60


Getting Started

Service task (SRV)

SCF.SRV.GSM.ACTIVEEnables or disables Global State Management (GSM).

Note: “Global State Management” on page 172 describes the GSM functionality.

Valid values

YES|NO

Default

YES

Example

SCF.SRV.GSM.ACTIVE=NO

SCF.SRV.GSM.INTERVALSets the number of seconds for SCF for GSM to notify other Mainframe Enablers applications of a configuration change to a VMAX system.

Note: “Global State Management” on page 172 describes the GSM functionality.

This parameter is valid when the SCF.SRV.GSM.ACTIVE parameter is set to YES.

Default

15

Example

SCF.SRV.GSM.INTERNAL=20


Getting Started

SRDF/A Single Session (SS)

SCF.SS.AUTO.RECOVEREnables or disables the SRDF/A Single Session Auto Recovery feature and sets the auto-recovery mode for the SRDF/A Monitor.

Note: “SRDF/A Single Session Auto Recovery” on page 664 describes the SRDF/A Single Session Auto Recovery feature. “Monitoring SRDF/A (SRDF/A Monitor)” on page 657 describes the SRDF/A Monitor.

Syntax

SCF.SS.AUTO.RECOVER=ENABLE[(MANUAL)]|DISABLE

Where:

DISABLE

SRDF/A Single Session Auto Recovery is not used.

ENABLE

The SRDF/A Monitor initiates auto recovery for single-session SRDF/A groups that have changed state from active to inactive.

MANUAL

The SRDF/A Monitor detects the change of state from active to inactive but does not initiate auto recovery. The recovery procedure must be initiated manually.

Example

SCF.SS.AUTO.RECOVER=ENABLE

SCF.SS.AUTO.RECOVER.SymmID.srdfgrpIdentifies the VMAX system and SRDF group for the SRDF/A Single Session Auto Recovery feature.

Note: “SRDF/A Single Session Auto Recovery” on page 664 describes the SRDF/A Single Session Auto Recovery feature.

To recover multiple SRDF groups, specify each group in a separate statement.

If this parameter is not specified, all single-session SRDF/A groups are automatically recovered.

SymmID

The 12-character serial number of the VMAX system.

srdfgrp

The SRDF group number. Valid values are 0 to F9 (hex).

Valid values

Y (all other values are ignored)


Getting Started

Default

None

Example

SCF.SS.AUTO.RECOVER.000192600262.B9=Y

SCF.SS.AUTO.RECOVER.BCVSets BCV gold copy management options for the SRDF/A Monitor to be used for SRDF/A Auto Recovery. The options are applied to all VMAX systems.

Note: “SRDF/A Single Session Auto Recovery” on page 664 describes the SRDF/A Single Session Auto Recovery feature. “Monitoring SRDF/A (SRDF/A Monitor)” on page 657 describes the SRDF/A Monitor. The TimeFinder/Mirror for z/OS Product Guide describes BCVs.

This parameter is only required when the SCF.SS.AUTO.RECOVER parameter is set to ENABLE.

Syntax

SCF.SS.AUTO.RECOVER.BCV=BCV(start_option,end_option)

Where:

start_option

Defines behavior at the start of the gold copy management routine. Valid values are:

• NONE — BCV management is bypassed for this phase.

• ESTablish — Results in a new 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 BCVs are attached, they will be split.

end_option

Defines the desired state of the BCV relationships at the completion of the SRDF/A recovery operation. Valid values are:


• ESTablish — Results in a re-establish of all BCVs to the R2s.

Example

SCF.SS.AUTO.RECOVER.BCV=BCV(EST,EST)


Getting Started

SCF.SS.AUTO.RECOVER.BCV.SymmID.srdfgrpSets BCV gold copy management options for the SRDF/A Monitor to be used for SRDF/A Auto Recovery. The options are applied to the specified VMAX system and SRDF group.

Note: “SRDF/A Single Session Auto Recovery” on page 664 describes the SRDF/A Single Session Auto Recovery feature. “Monitoring SRDF/A (SRDF/A Monitor)” on page 657 describes the SRDF/A Monitor. The TimeFinder/Mirror for z/OS Product Guide describes BCVs.

SCF.SS.AUTO.RECOVERY.BCV.SymmID.srdfgrp overrides the SCF.SS.AUTO.RECOVERY.BCV parameter value for a particular SRDF group.

This parameter is only used when the SCF.SS.AUTO.RECOVER parameter is set to ENABLE.

Syntax

SCF.SS.AUTO.RECOVER.SymmID.srdfgrp=BCV(start_option,end_option)

Where:

SymmID


srdfgrp

The SRDF group number. Valid values are 0 to F9 (hex).

start_option

Defines behavior at the start of the gold copy management routine. Valid values are:


• ESTablish — Results in a new 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 BCVs are attached, they will be split.

end_option

Defines the desired state of the BCV relationships at the completion of the SRDF/A recovery operation. Valid values are:


• ESTablish — Results in a re-establish of all BCVs to the R2s.

Example

SCF.SS.AUTO.RECOVER.BCV.000190300344.3=BCV(EST,EST)

SCF.SS.AUTO.RECOVER.ITRKDetermines the number of outstanding R2 invalid tracks on the R1 side to activate SRDF/A for this session. This parameter applies to all VMAX systems.



Getting Started

The specified parameter value is multiplied by 1000.


Valid values

1-99999

Default

30 (which represents 30 x 1000 = 30,000)

Example

SCF.SS.AUTO.RECOVER.ITRK=500

SCF.SS.AUTO.RECOVER.ITRK.SymmIDDetermines the number of outstanding R2 invalid tracks on the R1 side to activate SRDF/A for this session. This parameter applies to the specified VMAX systems.


SCF.SS.AUTO.RECOVERY.ITRK.SymmID overrides the SCF.SS.AUTO.RECOVERY.ITRK parameter value for a particular VMAX system.

This parameter is only used when the SCF.SS.AUTO.RECOVER parameter is set to ENABLE.

SymmID


Valid values

1-99999

Default

None

Example

SCF.SS.AUTO.RECOVER.ITRK.000190300344=2000

SCF.SS.AUTO.RECOVER.JOBNAMEDefines the jobname to be used when SRDF/A Auto Recovery is initiated.



Default

None


Getting Started

Example

SCF.SS.AUTO.RECOVER.JOBNAME=SSARJOB

SCF.SS.AUTO.RECOVER.JOBNAME.SymmIDDefines the jobname to be used for the specified VMAX system when SRDF/A Auto Recovery is initiated.


SCF.SS.AUTO.RECOVERY.JOBNAME.SymmID overrides the SCF.SS.AUTO.RECOVERY.JOBNAME parameter value for a particular VMAX system.

SymmID


Default

None

Example

SCF.SS.AUTO.RECOVER.JOBNAME.000190300344=UNITJOB

SCF.SS.AUTO.RECOVER.LPARDetermines the unique LPAR ID for the SCF system to run the SRDF/A Auto Recovery procedure.


This parameter ensures that SRDF/A Single Session Auto Recovery is only enabled on a single LPAR. This prevents auto recovery started by multiple SCF systems.

IMPORTANT

Include SCF.SS.AUTO.RECOVER.LPAR in all SCF initialization files with the SRDF/A Monitor enabled.


Default

None

Example

SCF.SS.AUTO.RECOVER.LPAR=X118


Getting Started

SCF.SS.AUTO.RECOVER.MINDIRSets the minimum number of directors that must be online for all VMAX systems.



Valid values

1 to 128

Default

1

Example

SCF.SS.AUTO.RECOVER.MINDIR=10

SCF.SS.AUTO.RECOVER.MINDIR.SymmIDSets the minimum number of directors that must be online for the specified VMAX system.


SCF.SS.AUTO.RECOVERY.MINDIR.SymmID overrides the SCF.SS.AUTO.RECOVERY.MINDIR parameter value for a particular VMAX system.

SymmID


Valid values

1 to 128

Default

None

Example

SCF.SS.AUTO.RECOVER.MINDIR.000190300344=2

SCF.SS.AUTO.RECOVER.PREFIXDetermines the SRDF Host Component command prefix to be used by the SRDF/A Auto Recovery job.




Getting Started

Valid values

The SRDF Host Component command prefix in single quotes

Default

None

Example

SCF.SS.AUTO.RECOVER.PREFIX='OCT'

SCF.SS.AUTO.RECOVER.PROCDefines the name of the JCL procedure for SRDF/A Auto Recovery.



A sample EMCRCVRY procedure is included in the SAMPLE file.

Valid values

An EBCDIC name from 1 to 8 characters.

Default

None

Example

SCF.SS.AUTO.RECOVER.PROC=EMCRCVRY


Getting Started

Thin Pool Capacity Monitor (THN)

SCF.THNEnables or disables the THN Monitor.

Note: “Monitoring Thin Pools (THN Monitor)” on page 591 describes the THN Monitor.

The THN Monitor is enabled by default. To disable the THN Monitor, specify DISABLE explicitly.

Valid values

ENAble|DISable

Default

ENAble

Example

SCF.THN=DISABLE

SCF.THN.xx.LIST Provides monitoring settings for the THN Monitor.


The SCF.THN.xx.LIST parameter is used to define settings for a global interval.

Syntax

SCF.THN.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=minutes|[ACTION=NONE|MESsage(string)|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx





DURation=minutes



Getting Started

ACTION=NONE|MESsage(string)|USEREXIT(exitname)


NONE

No action.

MESsage(string)


USEREXIT(exit_name)


Note: “Optional user exit” on page 594 describes using exits in the THN Monitor.




NONE


ONCE


REPEAT



For instance, when the THN 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.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=5SCF.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

Note: For a detailed explanation of the example, refer to “Example 1” on page 595.


Getting Started

SCF.THN.SymmID.LISTEnables or disables the THN Monitor for a specific VMAX system.



SymmID



Valid values

ENAble|DISable

Default

DISable

Example

SCF.THN.18773.LIST=ENABLE

SCF.THN.SymmID.LIST=GATEkeeper=ccuuAllows the THN Monitor to use a special gatekeeper device in the VMAX system.


SymmID



ccuu

the z/OS device number used as the SCF gatekeeper for the channel-attached device.

Valid values

z/OS device number

Default

None

Example

SCF.THN.18773.LIST=GATE=423F


Getting Started

SCF.THN.SymmID.xx.LISTProvides monitoring settings of the THN Monitor for an individual VMAX system.



Syntax

SCF.THN.SymmID.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=minutes|[ACTION=NONE|MESsage(string)|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]

Where:

xx





DURation=minutes

The duration of time (in minutes). Valid values are from 1 to 1440. The default value is 720 seconds (12 hours).



NONE

No action.

MESsage(string)


USEREXIT(exit_name)





Getting Started



NONE


ONCE


REPEAT




SymmID



Example

SCF.THN.18771.01.LIST=PERCENT=(0,80)SCF.THN.18771.01.LIST=DURATION=10SCF.THN.18771.01.LIST=ACTION=MES(PROC1)

SCF.THN.SymmID.poolname.xx.LISTProvides monitoring settings of the THN Monitor for an individual thin pool within the VMAX system.



Syntax

SCF.THN.SymmID.poolname.xx.LIST=[{PERcent=(low_percent[,high_percent])|DURation=minutes|[ACTION=NONE|MESsage(string)|USEREXIT(exitname)]|[FREQuency={NONE|ONCE|REPEAT}]}]


Getting Started

Where:

xx





DURation=minutes

The duration of time (in minutes). Valid values are from 1 to 1440. The default value is 720 seconds (12 hours).



NONE

No action.

MESsage(string)


USEREXIT(exit_name)






NONE


ONCE


REPEAT



Getting Started



SymmID



poolname

The name of the thin device pool to which the settings apply.


Example

SCF.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)


Getting Started

SCF tracing (TRACE)

SCF.TRACE.COMPRESSDetermines whether to compress the SCF trace file.

Note: “SCF log and trace files” on page 174 describes the SCF trace file.

Valid values

YES|NO

Default

NO

Example

SCF.TRACE.COMPRESS=YES

SCF.TRACE.CYLINDERDetermines that space allocations for the SCF trace file must be made using cylinders instead of tracks.


This parameter overrides the SCF.TRACE.TRACKS.PRI and SCF.TRACE.TRACKS.SEC parameters.

Valid values

Yes|No

Default

No

Example

SCF.TRACE.CYLINDER=Y

SCF.TRACE.DATACLASDefines the SMS data class name to be used when allocating the SCF trace file.


Valid values

1 to 8 characters

Default

None


Getting Started

Example

SCF.TRACE.DATACLAS=SCFTRACE

SCF.TRACE.FLUSH.ATDetermines the trace buffer fill rate (as a percentage of the full size) at which the trace buffer is flushed to the SCF trace file.


Valid values

30 to 90

Default

75

Example

SCF.TRACE.FLUSH.AT=50

SCF.TRACE.MEGSDetermines the amount of space (in megabytes) used to create the SCF trace file.


The space, converted from megabytes into tracks, is used for primary and secondary allocations.

Note: SCF.TRACE.MEGS is the total allocation including 16 extents. If both SCF.TRACE.MEGS and SCF.TRACE.TRACKS are specified, SCF.TRACE.MEGS overrides SCF.TRACE.TRACKS.

Valid values

1 to 9999

Default

1

Example

SCF.TRACE.MEGS=2

SCF.TRACE.MGMTCLAS Defines the SMS management class name to be used when allocating the SCF trace file.



Getting Started

Valid values

1 to 8 characters

Default

None

Example

SCF.TRACE.MGMTCLAS=MGMTRACE

SCF.TRACE.RETAIN.COUNT Sets the number of SCF trace files to retain.


Valid values

1 to 9999

Default

10

Example

SCF.TRACE.RETAIN.COUNT=12

SCF.TRACE.RETAIN.DAYS Sets the number of days to retain an SCF trace file.


Valid values

1 to 9999

Default

10

Example

SCF.TRACE.RETAIN.DAYS=30

SCF.TRACE.STORCLAS Defines the SMS storage class name to be used when allocating the SCF trace file.


Valid values

1 to 8 characters


Getting Started

Default

None

Example

SCF.TRACE.STORCLAS=FOOBAR

SCF.TRACE.TRACKS.PRISets the number of tracks to be primarily allocated for the SCF trace file.


If the SCF.TRACE.CYLINDER parameter is set to Yes, the allocation is made using cylinders instead of tracks.

Valid values

1 to 9999

Default

None

Example

SCF.TRACE.TRACKS.PRI=12

SCF.TRACE.TRACKS.SECSets the number of tracks to be secondarily allocated for the SCF trace file.


If the SCF.TRACE.CYLINDER parameter is set to Yes, the allocation is made using cylinders instead of tracks.

Valid values

1 to 9999

Default

None

Example

SCF.TRACE.TRACKS.SEC=45


Getting Started

Thin Reclamation Monitor (TRU)

SCF.TRU.DEBUGEnables or disables debugging for the TRU Monitor.

Note: “Monitoring Space Reclamation (TRU Monitor)” on page 621 describes the TRU Monitor.

Valid values

YES|NO

Default

NO

Example

SCF.TRU.DEBUG=YES

SCF.TRU.DEV.EXCLUDE.LISTExcludes devices from the TRU Monitor.


Multiple devices and multiple device ranges may be specified. Multiples statement may be specified and they will be concatenated together.

Valid values

CCUUs defined to SCF

Default

None

Example

SCF.TRU.DEV.EXCLUDE.LIST=0000-A000,B000-C000SCF.TRU.DEV.EXCLUDE.LIST=1234,2345-3456,4567

SCF.TRU.DEV.INCLUDE.LISTLists devices to be monitored by the TRU Monitor.


Multiple devices and multiple device ranges may be specified. Multiples statement may be specified and they will be concatenated together.

Valid values

CCUUs defined to SCF


Getting Started

Default

None.

Example

SCF.TRU.DEV.INCLUDE.LIST=0000-A000,B000-C000SCF.TRU.DEV.INCLUDE.LIST=1234,2345-3456,4567

SCF.TRU.ENABLEEnables or disables TRU and the TRU Monitor.


Valid values

YES|NO

Default

YES

Example

SCF.TRU.ENABLE=NO

SCF.TRU.OFFLINEDetermines whether TRU processes devices that are offline to the LPAR on which TRU runs.

◆ If set to NOPROCESS, then a device that is offline to the LPAR is not processed by TRU.

◆ If set to PROCESS, then a device can be processed whether or not the device is offline.


Valid values

PROCESS|NOPROCESS

Default

PROCESS

Example

SCF.TRU.OFFLINE=NOPROCESS

SCF.TRU.RECLAIM.DSFACTORProvides a size factor when allocating the temporary dataset for reclaim processing.

◆ For track-managed space, this is the maximum number of cylinders allocated to a temporary dataset.


Getting Started

◆ For cylinder-managed space, this is the number of CMS allocation units (21 cylinders each) allocated to a temporary dataset.

Note: “Reclaiming” on page 629 describes TRU reclaim operations.

Valid values

1 to 999999

Default

1000

Example

SCF.TRU.RECLAIM.DSFACTOR=500

SCF.TRU.RECLAIM.DSPREFIXIdentifies the prefix for the temporary dataset allocated for reclaim purposes.


The prefix 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.

For example, if the prefix is EMC.RECLAIM, the generated name format is EMC.RECLAIM.RCvolser.#0000001.

Valid values

Up to 26 characters

Default

EMC.RECLAIM

Example

SCF.TRU.RECLAIM.DSPREFIX=EMC.RECLAIM

SCF.TRU.RECLAIM.METHODDetermines the order of reclaiming tracks:

◆ 1 — From the beginning of a volume to the end of the volume.

◆ 2 — From the end of a volume to the beginning of the volume.

◆ 3 — From the largest segment to the smallest segment.


Valid values

1|2|3


Getting Started

Default

1

Example

SCF.TRU.RECLAIM.METHOD=1

SCF.TRU.RECLAIM.PGMNAME Provides an alternative program name to be attached in SCF to perform TRU reclaim operations.


Valid values

Up to 8 characters

Default

ESFTRURC

Example

SCF.TRU.RECLAIM.PGMNAME=MYNAME2

SCF.TRU.RECLAIM.POST.MAX Sets the maximum number of tracks that is allowed when the space percentage is calculated for TRU reclaim operations.


Valid values

0 to 9999999

Default

9999999

Example

SCF.TRU.RECLAIM.POST.MAX=750000

SCF.TRU.RECLAIM.POST.MIN Sets the minimum number of tracks that is allowed when the space percentage is calculated for TRU reclaim operations.


Valid values

0 to the smaller value of 9999999 or the value in SCF.TRU.RECLAIM.POST.MAX. If this value is exceeded, then the default is used.


Getting Started

Default

The smaller value of 100 or the value in SCF.TRU.RECLAIM.POST.MAX.

Example

SCF.TRU.RECLAIM.POST.MIN=500

SCF.TRU.RECLAIM.POST.PCT Sets the space percentage for TRU reclaim operations.


Valid values

0 to 100

Default

50

Example

SCF.TRU.RECLAIM.POST.PCT=65

SCF.TRU.RECLAIM.POST.TYPEDetermines the type of space value on which the trigger point is based for reclaim operations:

◆ FREESPACE — The amount of free space initially available on the device, determined when the TRU Monitor starts monitoring the thin device (the device must be online), and also each time the RECLAIM utility runs.

◆ DEVICESIZE — The total size of the device, as determined when the TRU Monitor starts monitoring the thin device.


Valid values

FREESPACE|DEVICESIZE

Default

FREESPACE

Example

SCF.TRU.RECLAIM.POST.TYPE=DEVICESIZE


Getting Started

SCF.TRU.RECLAIM.SCRATCH.WAIT Defines the amount of time after a dataset scratch has occurred before starting reclaim operations.


The value is specified in units of 1/100 seconds. For example, a value of 100 causes a minimum one second wait.

Valid values

0 to 360000 (1 hour)

Default

0

Example

1. To set a minimum one second wait before starting reclaim processing:

SCF.TRU.RECLAIM.SCRATCH.WAIT=100

2. To set a minimum one minute wait before starting reclaim processing:

SCF.TRU.RECLAIM.SCRATCH.WAIT=6000

SCF.TRU.RECLAIM.STCNAME Sets the STC name that is used for executing the RECLAIM program.


When an STC name is specified, all reclaim processing occurs as separate started tasks, and not by attaching the task locally in SCF.

Note: To use the STC name, add the corresponding procedure to your PROCLIB. “Running the TRU Monitor” on page 623 provides additional information.

If no name is specified, reclaim is executed within the SCF address space.

Valid values

8-character procedure name

Default

None

Example

SCF.TRU.RECLAIM.STCNAME=BAPTRCLM


Getting Started

SCF.TRU.RECLAIM.STRESS.MONITOREnables or disables VMAX stress monitoring.

Note: “VMAX stress monitoring” on page 630 describes the stress monitoring functionality.

If set to YES, all reclaim erases accept a code from the VMAX indicating whether the erases are causing stress in the VMAX system.

Valid values

YES|NO

Default

YES

Example

SCF.TRU.RECLAIM.STRESS.MONITOR=NO

SCF.TRU.RECLAIM.STRESS.WAIT Defines the maximum amount of wait time (in minutes) between reclaim erase I/O operations when VMAX stress condition is discovered.

Note: “VMAX stress monitoring” on page 630 describes the stress monitoring functionality.

Valid values

0 to 60

Default

5

Example

SCF.TRU.RECLAIM.STRESS.WAIT=15

SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMITSets the maximum amount of time (in seconds) that the reclaim task is to hold the SYSVTOC RESERVE during processing.


The value is specified in units of 1/100 seconds. For example, a value of 6000 causes a 1-minute wait.

Valid values

0 to 18000

Default

3000 (30 seconds)


Getting Started

Example

To limit the hold time to one minute:

SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT=6000

SCF.TRU.RECLAIM.SYSVTOC.TRKLIMITSets the maximum segment size (contiguous free space) that is considered to be processed while holding the SYSVTOC RESERVE for reclaim operations:

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


Valid values

0 to 999999

Default

150

Example

To limit the segment size to 2 cylinders:

SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT=30

SCF.TRU.RECLAIM.SYSVTOC.WAITDetermines the amount of time to elapse after releasing the SYSVTOC RESERVE, before attempting to acquire the SYSVTOC RESERVE again, for reclaim operations.


The value is specified in units of 1/100 seconds. For example, a value of 6000 causes a 1-minute wait.

Valid values

0 to 30000

Default

3000 (30 seconds)

Example

To set a wait time of one minute:

SCF.TRU.RECLAIM.SYSVTOC.WAIT=6000


Getting Started

SCF.TRU.RECLAIM.TIMELIMIT.LISTSets time limits for running the reclaim process. If specified, reclaim processing only occurs during the time limits specified.


Values are specified as a series of 4-digit values: 2-digit for hours and 2-digit for minutes. You can specify multiple ranges.

Default

None

Example

SCF.TRU.RECLAIM.TIMELIMIT.LIST=0200-0400,0800-1200,1300-1500,1800-1900

SCF.TRU.RECLAIM.TASK.LIMIT Sets the maximum number of reclaim tasks that can run simultaneously.


Valid values

1 to 99

Default

10

Example

SCF.TRU.RECLAIM.TASK.LIMIT=15

SCF.TRU.SCAN.PGMNAME Provides an alternative program name to be attached in SCF to perform TRU scan operations.

Note: “Scanning” on page 628 describes scan operations.

Valid values

Up to 8 characters

Default

ESFTRURC

Example

SCF.TRU.SCAN.PGMNAME=MYNAME1


Getting Started

SCF.TRU.SCAN.STCNAME Sets STCNAME that is to be used for executing the SCAN program.


When an STCNAME is specified, all scan processing occurs as separate started tasks, and not by attaching the task locally in SCF.

Note: To use the STC name, add the corresponding procedure to your PROCLIB. “Running the TRU Monitor” on page 623 provides additional information.

If no name is specified, scan is executed within the SCF address space.

Valid values

8-character procedure name

Default

None

Example

SCF.TRU.SCAN.STCNAME=BAPTSCAN

SCF.TRU.SCAN.TASK.LIMITSets the maximum number of scan tasks that can run simultaneously.


Valid values

1 to 99

Default

10

Example

SCF.TRU.SCAN.TASK.LIMIT=15

SCF.TRU.SCRATCH.POST.MAX Sets the maximum number of tracks that is allowed when the space percentage is calculated for TRU scratch operations.

Note: “Monitoring Space Reclamation (TRU Monitor)” on page 621 describes scratch operations.

Valid values

0 to 9999999


Getting Started

Default

9999999

Example

SCF.TRU.SCRATCH.POST.MAX=750000

SCF.TRU.SCRATCH.POST.MIN Sets the minimum number of tracks that is allowed when the space percentage is calculated for TRU scratch operations.


Valid values

0 to the smaller value of 9999999 or the value in SCF.TRU.SCRATCH.POST.MAX. If this value is exceeded, then the default is used.

Default

The smaller value of 100 or the value in SCF.TRU.SCRATCH.POST.MAX.

Example

SCF.TRU.SCRATCH.POST.MIN=500

SCF.TRU.SCRATCH.POST.PCT Sets the space percentage for TRU scratch operations.


Valid values

0 to 100

Default

50

Example

SCF.TRU.SCRATCH.POST.PCT=65

SCF.TRU.SCRATCH.POST.TYPEDetermines the type of space value on which the trigger point is based for scratch operations:

◆ FREESPACE — The amount of free space initially available on the device, determined when the TRU Monitor starts monitoring the thin device (the device must be online), and also each time the reclaim procedure runs.


Getting Started

◆ DEVICESIZE — The total size of the device, as determined when the TRU Monitor starts monitoring the thin device.


Valid values

FREESPACE|DEVICESIZE

Default

FREESPACE

Example

SCF.TRU.SCRATCH.POST.TYPE=DEVICESIZE

SCF.TRU.SCRATCH.RECLAIMSets the maximum size (in tracks) of an extent that can be automatically reclaimed during execution of the scratch exit.

Note: “Monitoring Space Reclamation (TRU Monitor)” on page 621 describes reclaim operations.

Valid values

0 to 999999

Default

20

Example

SCF.TRU.SCRATCH.RECLAIM=15

SCF.TRU.THICKR1Enables support for thick R1 scanning of devices in the TRU environment.

Note: “Thick R1 processing” on page 628 describes support for thick R1 scanning.

Valid values

YES|NO

Default

YES

Example

SCF.TRU.THICKR1=YES


Getting Started

SCF log and trace file (WORK)

SCF.WORK.HLQSets the high-level qualifier to be used when creating the SCF log and trace files.

Note: “SCF log and trace files” on page 174 describes SCF log and trace files.

Valid values

1 to 8 characters

Default

SCFSERVE

Example

SCF.WORK.HLQ=SCFSERVE

SCF.WORK.UNIT Sets the unit name to be used when allocating the SCF log and trace files.


Valid values

1 to 8 characters

Default

SYSDA

Example

SCF.WORK.UNIT=SYSDA

SCF.WORK.VOLSER Determines the volser to be used when allocating the SCF log and trace files.


Valid values

1 to 6 characters

Default

None

Example

SCF.WORK.VOLSER=DISK01


Getting Started

SRDF/A Write Pacing Monitor (WPA)

SCF.WPA.EXCLUDE.CNTRL[.LIST]Excludes SRDF groups on the specified VMAX system from the WPA Monitor.

Note: “Monitoring SRDF/A Write Pacing (WPA Monitor)” on page 673 describes the WPA Monitor.

This parameter overrides the SCF.WPA.INCLUDE.CNTRL[.LIST] parameter.

Syntax

SCF.WPA.EXCLUDE.CNTRL[.LIST]=SymmID({<srdfgrp1,2,…,n>|ALL})

Where:

ALL

Excludes all SRDF groups on the specified VMAX system.

LIST

Add this keyword if you want to specify multiple exclude statements.

SymmID


srdfgrp1,2,...,n

The 2-character number of the SRDF group.

Example

To specify a single statement:

SCF.WPA.EXCLUDE.CNTRL=000190300344(05,08,1E,F0)

To specify multiple statements:

SCF.WPA.EXCLUDE.CNTRL.LIST=000192603872(05,08,1E,F0)SCF.WPA.EXCLUDE.CNTRL.LIST=000194901031(ALL)

SCF.WPA.INCLUDE.CNTRL[.LIST]Adds the specified VMAX systems and SRDF groups to the WPA Monitor.


This parameter can be overridden by the SCF.WPA.EXCLUDE.CTRL[.LIST] parameter.

Syntax

SCF.WPA.INCLUDE.CNTRL[.LIST]=SymmID({<srdfgrp1,2,…,n>|ALL})

Where:

ALL

Includes all SRDF groups on the specified VMAX system.


Getting Started

LIST

Add this keyword if you want to specify multiple include statements.

SymmID


srdfgrp1,2,...,n

The 2-character number of the SRDF group.

Example

To specify a single statement:

SCF.WPA.INCLUDE.CNTRL=000190300344(05,08,1E,F0)

To specify multiple statements:

SCF.WPA.INCLUDE.CNTRL.LIST=000192603872(05,08,1E,F0)SCF.WPA.INCLUDE.CNTRL.LIST=000194901031(ALL)

SCF.WPA.MONITOREnables or disables the WPA Monitor:

◆ When set to ENAble, the WPA Monitor actively monitors SRDF/A sessions with Write Pacing activated.

◆ When set to DISable, the WPA Monitor does not start.


After changing the parameter value, activate it by restarting SCF.

Valid values

ENAble|DISable

Default

DISable

Example

SCF.WPA.MONITOR=ENA

SCF.WPA.MSGLEVELDetermines types of WTO messages to be issued for the WPA Monitor.


The types are specified as a comma-separated list.

Syntax

SCF.WPA.MSGLEVEL=[ALERTS][,BASIC][,INCEXC][,STATE][,STATUS]


Getting Started

Where:

ALERTS

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 (for example, changing the state of a group from paced to not paced).

STATUS

WPA Monitor status messages.

Default

BASIC

Example

SCF.WPA.MSGLEVEL=ALERTS,INCEXC

SCF.WPA.POLL.INTERVALSets the polling interval for the WPA Monitor.


The value is specified in tenths of a minute to a maximum of 60 minutes.

Valid values

.1 to 60 minutes

Default

5 minutes

Example

SCF.WPA.POLL.INTERVAL=.1

SCF.WPA.SMFEnables or disables writing SMF records for the WPA Monitor.


Valid values

ENABLE|DISABLE


Getting Started

Default

DISABLE

Example

SCF.WPA.SMF=ENABLE

SCF.WPA.SMF.FILTERFilters out WPA Monitor data records from being recorded to SMF.


Valid values

NOINACTIVE

Data records whose pacing state flags are all off are not recorded to SMF or displayed in the informational statistics messages. Even when no data records remain after NOINACTIVE processing is performed, that the header record for the VMAX 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 VMAX system is still written to SMF.

NOUNCHANGED

Data records whose pacing state flags and statistics numbers that have not 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 VMAX system is written to SMF.

NOZERO

Data records with all zero statistics are not recorded to SMF or displayed in the informational statistics messages.

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


Getting Started

SCF.WPA.SMF.RECORDDetermines the number of an SMF record to be used by the WPA Monitor when writing statistics about VMAX systems that are being monitored.


If not specified, the WPA Monitor uses the value of the SCF.ASY.SMF.RECORD parameter (if specified). If the SMF record type cannot be determined, the WPA Monitor does not write any SMF records.

Valid values

128 to 255

Default

None

Example

SCF.WPA.SMF.RECORD=150

SCF.WPA.STYPESDetermines the type of statistics records to be written by the WPA Monitor:

◆ GROUP — Group statistics.

◆ DEVICE — Device statistics.

◆ ALL — Group and device statistics.


Valid values

GROUP|DEVICE|ALL

Default

ALL

Example

SCF.WPA.STYPES=GROUP


Getting Started

Running ResourcePak BaseResourcePak Base provides services for many EMC z/OS products through the Symmetrix Control Facility (SCF), which is the heart of ResourcePak Base.


EMC recommends having SCF active at all times.

SCF should be started automatically when you perform an IPL on the system. Shut down SCF only when the system is shut down.

Customizing the SCF started task

ResourcePak Base is intended to run as a started task. The sample started task for SCF is available in the EMCSCF member of the Mainframe Enablers SAMPLIB library.

Customize SAMPLIB(EMCSCF) according to your site requirements. “Sample JCL” on page 139 provides the necessary instructions.

When finished, copy the customized SAMPLIB(EMCSCF) member to a system PROCLIB that is used for started task START commands.

Note: Implement the SCF 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 SCF processes, such as device discovery and SRDF/AR processes.

Sample JCLThe JCL to run SCF is as follows:

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

Where:

◆ ds_prefix is the product dataset name prefix you specified during installation of Mainframe Enablers as described in the Mainframe Enablers Installation and Customization Guide.

◆ nnnn identifies this SCF instance as a unique z/OS subsystem. “Running multiple SCF instances” on page 141 provides further information.

EXEC parameters

PGM The main entry program is SCFMAIN.

TIME TIME=1440 is recommended for long-running tasks.

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

Running ResourcePak Base 139

Getting Started

DD statements

STEPLIB The STEPLIB dataset is optional. If the ResourcePak Base load modules are installed into a link-listed dataset, the STEPLIB DD statement is not needed.

SCFINI Points to a dataset containing SCF initialization statements. The SCFINI DD statement does not allow concatenation.

Note: “Creating the SCF initialization file” on page 33 describes the SCF initialization file.

SYSABEND The SYSABEND DD statement is optional, but recommended.

Starting SCF

To start SCF, type the following command at a console:

S emcscf[,REUSASID=YES][,SUB=MSTR]

Where:

◆ emcscf is the name of the SCF started task, normally EMCSCF.

◆ REUSASID=YES avoids permanent loss of ASIDs1 during the life of an IPL.

◆ SUB=MSTR enables you to swap page datasets, JES2 checkpoint datasets, or to use couple datasets. Refer to “Starting SCF with SUB=MSTR” on page 140 for additional information.

Note: If an error occurs during startup and you receive an abend code, refer to “SCF abend codes” on page 144.

Starting SCF with SUB=MSTRWhen SCF is started with the SUB=MSTR parameter:

◆ The SCF procedure must be copied to a SYS1.PROCLIB procedure library concatenation.

◆ SRDF/AR processes cannot be defined with the MSGOPT(SYSOUT(ddname)) parameter. MSGOPT(WTO) should be used.

Note: The TimeFinder Mirror for z/OS Product Guide describes SRDF/AR.

When ConGroup is installed and started with SUB=MSTR, then SCF should also be started with SUB=MSTR.

1. Address Space Identifier


Getting Started

Running multiple SCF instances

You can run multiple instances of SCF as separate z/OS subsystems. This is useful for testing new versions of SCF or SCF-enabled products.

To run multiple instances of SCF as separate z/OS subsystems, add the following DD statement to the SCF started task:

//SCF$nnnn DD DUMMY

Where:

◆ nnnn identifies this SCF instance as a unique z/OS subsystem. You can then use the same DD statement in any started task for which you want to use this SCF instance.

Note: Each running SCF instance should have a unique SCF.WORK.HLQ to prevent SCF from prematurely cleaning up existing log or trace datasets. “SCF.WORK.HLQ” on page 133 provides more information.

ExampleTo identify the current SCF instance as v700 and make TimeFinder use the newly-identified SCF instance v700:

1. Add the SCF$V700 DD statement to the SCF started task:

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

2. Add the SCF$V700 DD statement to the TimeFinder started task:

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

Stopping SCF

To stop SCF, perform the following steps:

◆ Step 1: Check SRDF/A Auto Recovery status

◆ Step 2: Shut down MSC

◆ Step 3: Shut down SRDF/AR

◆ Step 4: Shut down zDP

◆ Step 5: Shut down SCF


Getting Started

Step 1: Check SRDF/A Auto Recovery statusYou cannot shut down SCF while active SRDF/A Single-Session Auto Recovery is in process. The recovery job must complete or be canceled prior to SCF being shut down.

Note: “SRDF Automatic Recovery” on page 688 describes the SRDF/A Single-Session Auto Recovery feature.

Step 2: Shut down MSCCheck if the MSC environment is active and shut down MSC.

Note: “Managing SRDF/A MSC” on page 685 provides information on MSC.

If the SCF.MSC.ENABLE parameter is set to YES, MSC must be disabled to shut down SCF.

To shut down MSC, issue the following command:

F emcscf,MSC,DISABLE,MSCG(*)

Where:

◆ emcscf is the name of the SCF started task.

Note: “MSC,DISABLE” on page 701 describes the MSC,DISABLE command.

Step 3: Shut down SRDF/ARCheck if the SRDF/AR environment is active and shut down SRDF/AR.

Note: “Managing SRDF/AR Processes” on page 679 provides information on SRDF/AR.

To shut down SRDF/AR, issue the following command:

F emcscf,SAR,STOP,process_name

Where:


◆ process_name is the name of the SRDF/AR process.

Note: “SAR,STOP” on page 683 describes the SAR,STOP command.

Step 4: Shut down zDPCheck if the zDP environment is active and shut down z/DP.

Note: “Managing zDP Processes” on page 649 describes zDP.

To shut down Z/DP, issue the following command:

F emcscf,ZDP,DISABLE,vdg_name


Getting Started

Where:


◆ vdg_name is the name of the running VDG.

Step 5: Shut down SCFTo shut down SCF:

◆ To shut down the SCF address space, but leave SymmAPI-MF in global memory, issue the following command:

P emcscf

Where:

• emcscf is the name of the SCF started task.

◆ To shut down the SCF address space and release all resources held by SCF, issue the following command:

F emcscf,INI,SHUTDOWN

Where:

• emcscf is the name of the SCF started task.

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 SCF terminates the persistent SymmAPI-MF at shutdown). Restarting SCF automatically reloads SymmAPI-MF.

If SCF has not been shut down with INI,SHUTDOWN, or if it failed or otherwise did not shut down properly, use the SCFTM31A utility to terminate SCF. “SCF termination utility” on page 150 describes the SCFTM31A utility.


Getting Started

SCF abend codes

Table 3 describes the abend codes that can be issued by SCF.

Table 3 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 SCF$nnnn DD statement in the SCF start task JCL and resubmit the job. “Customizing the SCF started task” on page 139 describes the SCF start task parameters.

0901 SCFMAIN An SCF using the same 4-character system name is already active.

If another SCF instance is active, there is no action. If no other SCF instance is active, run the SCF termination utility, as described in “SCF termination utility” on page 150.

0902 SCFMAIN Not authorized. Authorize all libraries in the STEPLIB concatenation.

1001 SCFIN12 $envblock is corrupted. Contact EMC Customer Support for technical assistance. Ensure you have the dump, the job log from the SCF startup, and the SASTRACE file available.

1001 FC04 Internal logic error while attempting to free the R5BCVWA control block.

Contact EMC Customer Support for technical assistance. Ensure you have the dump, the SCF job log, and the SCF trace and SCF log files available.

1002 SCFIN12 Attach failed for SCFEMGR. Contact EMC Customer Support for technical assistance. Ensure you have the dump, the job log from the SCF startup, and the SASTRACE file available.

1006 SCFIN12 Parm length exceeds 125 characters. Contact EMC Customer Support for technical assistance. Ensure you have the dump, the job log from the SCF startup, and the SASTRACE file available.

1032 SCFIN51 Extract STOKEN failed. The subsystem table may be corrupted.

Run the SCF termination utility, as described in “SCF termination utility” on page 150.

1033 SCFIN99 Extract STOKEN failed. The subsystem table may be corrupted.


1034 SCFMAIN Create Token failed; the SCF token already exists. Another SCF instance may be active or an earlier shutdown may have failed.

If no other SCF instance is active, run the SCF termination utility, as described in “SCF termination utility” on page 150.

1036 SCFPCKFISCFPCCHC

Unable to get addressability to the SCF server address space.

Ensure that SCF is active and has completed startup. Ensure that the SCF$nnnn DD statement points to the correct SCF instance.

Note: “Running multiple SCF instances” on page 141 describes use of the SCF$nnnn DD statement.

This abend code may also be encountered 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. If not, run the SCF termination utility, as described in “SCF termination utility” on page 150.


Getting Started

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 termination utility, as described in “SCF termination utility” on page 150.

1052 SCFTRCW Invalid TSB address passed in at startup.


1053 SCFTRCW Unable to find TSB. Run the SCF termination utility, as described in “SCF termination utility” on page 150.

1054 SCFZTIMR Invalid TSB address passed in at startup.


1055 SCFZTIMR Unable to find TSB. Run the SCF termination utility, as described in “SCF termination utility” on page 150.




Getting Started

1060 SCFIN01 Initialization failed to complete cleanly. This abend code 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 the 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 termination utility, as described in “SCF termination utility” on page 150.

1064 SCFTM31ASCFIN51

There is inconsistency in the $SASECSA API sets.


1065 SCFIN51 There is inconsistency in the $SASECSA API sets.


1066 SCFIN31ASCFPCUCM

The $SASECSA is corrupted. Run the SCF termination utility, as described in “SCF termination utility” on page 150.

1067 SCFPCUCM Logic error in incrementing use count. Contact EMC Customer Support for technical assistance. Ensure you have the dump, the SCF job log, and the SCF trace and SCF log files available.

1068 SCFPCUCM Logic error in decrementing use count. Contact EMC Customer Support for technical assistance. Ensure you have the dump, the SCF job log, and the SCF trace and SCF log files available.

1069 SCFPCUCM Logic error. Unknown SCF version. Contact EMC Customer Support for technical assistance. Ensure you have the dump, the SCF job log, and the SCF trace and SCF log files available.

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 statement and resubmit the job.

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 maintenance update was applied. Check the product release directory on the EMC Online Support website for the latest product maintenance and service information and files.

1086 SCFTRCW Dataset allocation failed. This abend code is accompanied by message SCF0913. It is caused by missing parameters in the SCF initialization file. Review the parameters required for defining the SCF log file. Update the SCF initialization file and restart SCF.

Note: “Configuring ResourcePak Base” on page 33 describes the SCF initialization file, and “ResourcePak Base initialization parameters” on page 36 provides an overview of the parameters.




Getting Started

1087 SCFTRCW Open of the SCF log dataset failed. This is caused by missing parameters in the SCF initialization file. Review the parameters required for defining the SCF log file. Update the SCF initialization 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 SCF initialization file. Review the parameters required for defining the SCF log file. Update the SCF initialization file and restart SCF.


1097 SCFLOGW Open of the SCF log dataset failed. This is caused by missing parameters in the SCF initialization file. Review the parameters required for defining the SCF log file. Update the SCF initialization 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.

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.





Getting Started

SAICALL error codes

Table 4 through Table 6 list SAICALL error codes:

Table 4 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: Bad CONFIG_DISK director number18: User area passed is not large enough

Table 5 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 6 SAICALL error codes — ESFCTLNM

Return code Description

04 EMCSAII failed validation

08 EMCSAIO failed validation

12 Request unsuccessful (see EMCRS)

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 (VMAX lock)


Getting Started

44 SYSC8133 specific

48 GNS specific

52 FC20 specific

56 Failed RACF check

60 SCFSCRRW/FC22 specific

Table 6 SAICALL error codes — ESFCTLNM

Return code Description


Getting Started

SCF termination utility

Use the SCF termination utility SCFTM31A to terminate SCF when SCF has not been shut down with the INI,SHUTDOWN command, or if it failed or otherwise did not shut down properly.

SCFTM31A terminates 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”.

Note: “Stopping SCF” on page 141 describes steps required to shut down SCF.

You can find the SCFTM31A utility in the load library where all SCF modules are placed. The JCL for the utility is located in SCF.SAMPLIB as member SCFUTL01.

Running SCFTM31AThe JCL to run the SCFTM31A utility is as follows:

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

Where:

◆ nnnn is the name of the SCF subsystem.

◆ option can have the value TERMSCF or CLEANSCF, as described in “Termination options” on page 150.

Termination optionsThe following termination options are available:

◆ TERMSCF — Use this option if the SCF task was shut down with “P emcscf ” to clean up the persistent API.

◆ CLEANSCF — Use this option if the SCF task ended abnormally.

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.


Getting Started

Return codesTable 7 lists the SCFTM31A utility return codes.

Running AutoSwap in SCF address space

You can enable or disable AutoSwap running within the SCF address space, which allows for products that rely on AutoSwap. This operation mode of AutoSwap is referred to as Basic AutoSwap.

Do not confuse Basic AutoSwap with the AutoSwap that runs as part of ConGroup (CAX). CAX runs within ConGroup and is not available for use by other products.

Note: The AutoSwap for z/OS Product Guide describes AutoSwap and its operation modes.

To enable or disable Basic AutoSwap, use the SCF.DAS.ACTIVE initialization parameter, as described in “SCF.DAS.ACTIVE” on page 55.

Enabling results in automatic startup of the SCF Cross System Communications (CSC) component, as AutoSwap relies on CSC for its own internal communications. Since CSC can also be initiated through the SCF.CSC.ACTIVE parameter (described in “SCF.CSC.ACTIVE” on page 47), having both initialization parameters is not a problem. Although, with SCF.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.

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

You can verify AutoSwap and/or CSC availability to reliant tasks using one of the following commands:

F emcscf,DAS DISPLAY- Displays default/global AutoSwap parameters via the SCFS163I message. emcscf is the name of the SCF started task.

F emcscf,CSC DISPLAY - Display all known CSC hosts active under z/OS system via the SCF0660I message. emcscf is the name of the SCF started task.

Table 7 SCFTM31A return codes

Code Description

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

Abend code 1069

The utility was not able to find the SCF instance requested. Ensure that the SCF$nnnn DD statement points to the SCF instance you require.


Getting Started

Using ResourcePak Base commands

Command format

ResourcePak Base operator commands are issued in the following format:

F emcscf,command_type,command

Where:


◆ command_type specifies the type of command, or environment, as indicated in Table 8 on page 152.

Note: The value specified in the SCF.INI.CPFX initialization parameter can also be used to issue these commands, as described in “SCF.INI.CPFX” on page 80.

◆ command specifies a ResourcePak Base command.

Command types

Table 8 provides an overview of ResourcePak Base features and associated command types.

Note that some of the ResourcePak Base features are implemented as standalone functionality that does not have any associated command type. Also, some features do not provide any operator commands.

Table 8 ResourcePak Base features and associated command types (page 1 of 2)

Feature Command Type Command Reference

Basic SCF operator commands DEV (devices)ELM (licensing)INI (initialization)REC (recovery)SRV (services)

page 186

Cross-system communication (CSC) CSC page 217

VMAX system name assignment n/a page 223

VMAX system path validation n/a page 227

FBA path reset n/a n/a

Group Name Services (GNS), online mode GNS page 262

Group Name Services (GNS), batch mode n/a page 242

Quality of Service (QoS) n/a page 279

zBoost PAV Optimizer DEV,OPTIMIZE page 347

ChangeTracker n/a page 388

Disk Compare n/a page 401


Getting Started

General Pool Management (GPM) GPM or n/a page 488 for HYPERMAX OS 5977 and higherpage 526 for Enginuity 5876 and 5773

Thin Pool Capacity (THN) Monitor THN page 600

Snap Pool Capacity (SDV) Monitor SDV page 608

Delta Set Extension (DSE) Pool Capacity Monitor DSE page 617

Thin Reclamation (TRU) Monitor TRU page 631

zDP ZDP page 651

SRDF/A Monitor ASY page 669

SRDF/A Write Pacing (WPA) Monitor n/a n/a

SRDF/AR process management SAR page 681

SRDF/AR Multi-Session Consistency (MSC) MSC page 690

Table 8 ResourcePak Base features and associated command types (page 2 of 2)

Feature Command Type Command Reference

Using ResourcePak Base commands 153

Getting Started


PART 1

VMAX ENVIRONMENT

Part 1 describes ResourcePak Base features and components that you can use to manage your VMAX environment. This part contains the following chapters:

Chapter 3, “Using Symmetrix Control Facility (SCF),” provides information on the basic functionality of SCF.

Chapter 4, “Controlling Communications (CSC),” describes the SCF CSC component.

Chapter 5, “Naming VMAX Systems (ESFCTLNM),” describes how to assign a name to you VMAX system with the ESFCTLNM utility.

Chapter 6, “Validating System Paths (ESFCHNU1),” describes how to validate paths to VMAX systems using the ESFCHNU1 utility.

Chapter 7, “Resetting FBA Paths and Devices (ESFFUCBC),” introduces the ESFFUCBC utility that enables you to reset FBA paths and devices.

Chapter 8, “Managing Device Groups (GNS),” describes the ResourcePak Base Group Name Services facility.

Chapter 9, “Optimizing Performance (QoS),” describes tools that you can use to improve performance of your VMAX system.

Chapter 11, “Monitoring Track Changes (ChangeTracker),” describes how to monitor disk activity using ChangeTracker.

Chapter 12, “Comparing Tracks (Disk Compare),” introduces the Disk Compare tool that compares tracks on disk volumes.


CHAPTER 3Using Symmetrix Control Facility (SCF)


◆ Introduction.......................................................................................................... 158◆ Managing the VMAX environment.......................................................................... 159◆ Command reference .............................................................................................. 186

Using Symmetrix Control Facility (SCF) 157

Using Symmetrix Control Facility (SCF)

IntroductionThe Symmetrix Control Facility (SCF) is the heart of ResourcePak Base.

SCF 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, SCF makes calls through the I/O Supervisor (IOS) to the Enginuity/HYPERMAX OS operating environment for VMAX 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 VMAX functions that perform tasks such as the following:

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

◆ Performing automation functions.

◆ Facilitating inter-LPAR communication through the VMAX storage system. ResourcePak Base facilitates inter-program 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/HYPERMAX OS operating environment of the VMAX system at different release levels. For example, the number of VMAX logical devices supported changes between one level of operating environment and another. ResourcePak Base masks this difference so that host applications do not have to change.

Symmetrix ControlFacility (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

VMAXdevices

SWAP



Managing the VMAX environment

Summary of operations

VMAX systems and devicesTable 1 lists operations for managing devices.

LicensingTable 2 lists licensing operations.

Table 1 Managing devices

Operation Control

View information on VMAX systems and devices DEV,DISPLAY command

Check Enginuity/HYPERMAX OS patches DEV,CH,CNTRL command

Specify VMAX systems accessible by SCF • SCF.CNTRL.EXCLUDE.LIST initialization parameter• SCF.CNTRL.EXCLUDE.LIST initialization parameter

Set wait interval for VMAX system registration SCF.REG.WAITINT initialization parameter

Set maximum count of errors to unregister VMAX system

• SCF.REG.MAX.ERRORS initialization parameter• SCF.REG.MAX.CONTROLLER.ERRORS initialization

parameter

Specify devices accessible by SCF • SCF.DEV.EXCLUDE.LIST initialization parameter• SCF.DEV.INCLUDE.LIST initialization parameter

Specify devices for HRO (Host Read Only) feature • SCF.DEV.ATTR.HRO.EXCLUDE.LIST initialization parameter• SCF.DEV.ATTR.HRO.EXCLUDE.LIST initialization parameter

Specify gatekeepers • SCF.GATEKEEPER.LIST initialization parameter• SCF.GATEKEEPER.SymmID.LIST initialization parameter

Unpin gatekeeper devices DEV,UNPIN command

Use multiple subchannel addressing SCF.DEV.MULTSS initialization parameter

View device discovery status DEV,STATUS command

Set device discovery interval SCF.DEV.WAITINT initialization parameter

View device locks REC,QUERYDEVICELOCK command

Release device locks REC,RELEASEDEVICELOCK command

Refresh device information in system DEV,REFRESH command

Rescan and validate devices to SCF internal tables DEV,RESCAN command

Table 2 Licensing

Operation Control

Provide Licensed Feature Codes SCF.LFC.LCODES.LIST initialization parameter

View licensed features or bundles for VMAX system ELM,LIST command

View used licenses or bundles for VMAX system ELM,QUERY command

Managing the VMAX environment 159


SymmAPI-MFTable 3 lists SymmAPI-MF operations.

External applicationsTable 4 lists operations for managing external applications.

CommandsTable 5 lists Command Prefix Facility operations.

SCF log and trace filesTable 6 lists operations for managing SCF log and trace files.

Table 3 SymmAPI-MF operations

Operation Control

Reread the initialization file INI,REFRESH command

Refresh SymmAPI-MF without stopping SCF INI,RELOAD command

Terminate SymmAPI-MF INI,SHUTDOWN command

Table 4 Managing external applications

Operation Control

Enable or disable Global State Management (GSM) SCF.SRV.GSM.ACTIVE initialization parameter

View count of current SCF external applications SRV,SYSBUSY,DISPLAY command

Decrement count of current SCF external applications SRV,SYSBUSY,DECREMENT command

Reset count of current SCF external applications SRV,SYSBUSY,RESET command

Set notification interval SCF.SRV.GSM.INTERVAL initialization parameter

Table 5 Command Prefix Facility operations

Operation Control

Enable or disable Command Prefix Facility SCF.INI.CPFX.DD initialization parameter

Set command prefix for SCF SCF.INI.CPFX initialization parameter

Set command routing in sysplex SCF.INI.SCOPE initialization parameter

Set max number of concurrent commands SCF.INI.COMMAND.MAX initialization parameter

Table 6 SCF log and trace files

Operation Control

Set high-level qualifier for SCF log and trace files SCF.WORK.HLQ initialization parameter

Set volser for SCF log and trace files SCF.WORK.VOLSER initialization parameter

Set unit name for allocation of SCF log and trace files SCF.WORK.UNIT initialization parameter



SCF log file

Table 6 lists operations for managing the SCF log file.

SCF trace file

Table 6 lists operations for managing the SCF trace file.

Table 7 SCF log file

Operation Control

Set tracks for primary allocation of SCF log file SCF.LOG.TRACKS.PRI initialization parameter

Set tracks for secondary allocation of SCF log file SCF.LOG.TRACKS.SEC initialization parameter

Allocate in cylinders instead of tracks SCF.LOG.CYLINDER initialization parameter

Define SMS data class for SCF log file SCF.LOG.DATACLAS initialization parameter

Define SMS management class for SCF log file SCF.LOG.MGMTCLAS initialization parameter

Define SMS storage class for SCF log file SCF.LOG.STORCLAS initialization parameter

Set number of SCF log files to retain SCF.LOG.RETAIN.COUNT initialization parameter

Set number of days to retain SCF log file SCF.LOG.RETAIN.DAYS initialization parameter

Table 8 SCF trace file

Operation Control

Set amount of space for SCF trace file SCF.TRACE.MEGS initialization parameter

Set tracks for primary allocation of SCF trace file SCF.TRACE.TRACKS.PRI initialization parameter

Set tracks for secondary allocation of SCF trace file SCF.TRACE.TRACKS.SEC initialization parameter

Allocate in cylinders instead of tracks SCF.TRACE.CYLINDER initialization parameter

Define SMS data class for SCF trace file SCF.TRACE.DATACLAS initialization parameter

Define SMS management class for SCF trace file SCF.TRACE.MGMTCLAS initialization parameter

Define SMS storage class for SCF trace file SCF.TRACE.STORCLAS initialization parameter

Set number of SCF trace files to retain SCF.TRACE.RETAIN.COUNT initialization parameter

Set number of days to retain SCF trace file SCF.TRACE.RETAIN.DAYS initialization parameter

Whether to compress SCF trace file SCF.TRACE.COMPRESS initialization parameter

Set trace buffer fill rate to flush to SCF trace file SCF.TRACE.FLUSH.AT initialization parameter



Device discovery

SCF discovers VMAX devices with a predefined period.

To initiate discovery, use the DEV,REFRESH or DEV,RESCAN command, as described in “DEV,REFRESH” on page 192 and “DEV,RESCAN” on page 193.

Viewing discovery progressYou can use the DEV,STATUS command (described in “DEV,STATUS” on page 193) to view the discovery progress. This command displays information about devices that have already been processed. After discovery, these numbers will remain static until a new device refresh/rescan is started.

Below is an example of DEV,STATUS output:

F emcscf,DEV,STATUS

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

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.



Multiple subchannel addressing

The Multiple Subchannel Addressing feature allows application addressable devices to remain in 4-digit device range (0000-FFFF) and yet at the same time allows 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.

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 the Multiple Subchannel Addressing feature is active, use sdddd, where s indicates the subchannel set, and dddd = indicates the 4-digit device number.

You enable the Multiple Subchannel Addressing feature using the SCF.DEV.MULTSS initialization parameter described in “SCF.DEV.MULTSS” on page 57.

When this feature is enabled, z/OS devices numbers (CCUUs) are displayed as 5-digit device addresses.

Dynamic activation of IODF configuration statements

SCF honors dynamic activation of IODF1 configuration statements. You do not have to stop and restart SCF to capture the newly added or deleted devices.

You can unpin the gatekeeper devices so an IODF ACTIVATE can be performed without stopping SCF or forcing you to choose another gatekeeper. To unpin devices, use the DEV,UNPIN command described in “DEV,UNPIN” on page 194. After SCF issues this command, the SCF0434I message 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.

1. Input/Output Definition File



HRO-controlled devices in AutoSwap groups

AutoSwap validates and processed devices that are included in a swap group and controlled by the Host Read Only (HRO) feature according to the following rules:

Note: The AutoSwap for z/OS Product Guide describes AutoSwap and swap groups.

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

Note: You specify the HRO-included devices using the SCF.DEV.ATTR.HRO.INCLUDE.LIST and SCF.DEV.ATTR.HRO.EXCLUDE.LIST initialization parameters, as described in “SCF.DEV.ATTR.HRO.INCLUDE.LIST” on page 56 and “SCF.DEV.ATTR.HRO.EXCLUDE.LIST” on page 55.

Otherwise, a warning is issued, 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 specification for the FROM device, then the FROM device must be offline.

Otherwise, an error message is issued, 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.

Note: The AutoSwap for z/OS Product Guide describes the AllowOnlineToDevice option.

Otherwise, an error message is issued, indicating that the TO device must have a HRO attribute.

Swapping HRO-included devicesAutoSwap follows the following rules when swapping HRO-included devices:

◆ If the TO device is online, then no UCB swap is performed. The TO device remains online and HRO-controlled.

◆ If the FROM device is online and both the FROM and TO device are HRO-included devices, the UCB swap is performed. The TO device is online and HRO-controlled after the swap.

◆ If the FROM device is online and there is no corresponding HRO include statement for the TO device, the UCBs are not swapped. The FROM device remains 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 becomes Not Ready to the host and any read or write access to the device results in an intervention-required condition. If the NRDY state is removed (for example, through SRDF Host Component), then the device retains the HRO attribute.

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

Note: The Consistency Groups for z/OS Product Guide describes CAX groups.



Viewing licenses

Refer to the following documents for information about licenses:


◆ VMAX3 Family with HYPERMAX OS VMAX100, VMAX200, VMAX400 Product Guide

◆ VMAX Family VMAX 10K, 20K, 40K Product Guide

Listing licensesResourcePak Base enables you to view a list of licensed features or license suites using the ELM,LIST command, as described in “ELM,LIST” on page 195.

For each feature or suite, the following information is provided in the report:

◆ Name of the feature or suite

◆ Activation type and ID

◆ Capacity type and licensed capacity

◆ License installation date

When you issue ELM,LIST from a VMAX system running HYPERMAX OS 5977 or higher, a report similar to the following displays the licenses:

SCF0341I ELM LIST CNTRL(01585) SCF5005I Report for (Remote) Controller follows 738 Symmetrix ID : 000196701585 Issue Date : 01/11/2016 Activation Capacity Feature Name Type ID Type Licensed-------------------------------- ----- --------- ---------- --------D@RE P-IND 1 Usable-TB 1 Installed: 01/18/2016Fast_X P-IND 1 Usable-TB 1 Installed: 01/18/2016Foundation_Suite P-IND 1 Usable-TB 5 Installed: 01/18/2016ProtectPoint_Suite P-IND 1 Reg-TB 5 Installed: 01/18/2016Remote_Replication_Suite P-IND 1 Usable-TB 5 Installed: 01/18/2016SRDF_METRO P-IND 1 Usable-TB 5 Installed: 01/18/2016SRDF_Star P-IND 1 Usable-TB 5 Installed: 01/18/2016VMAX_OS P-IND 1 Usable-TB 5 Installed: 01/18/2016VMAX3_ZDP P-IND 1 Usable-TB 5 Installed: 01/18/2016 Legend: Activation Type: E-IND = Evaluation Individual P-IND = Permanent Individual P-ENT = Permanent Enterprise Agreement P-LTD = Permanent Limited

Table 9 describes the report fields.



Table 9 ELM,LIST output fields under HYPERMAX OS 5977

Field Description

Symmetrix ID

The serial number of the VMAX system to which the license is applied.

Issue Date The date the license was issued.

Feature Name

The name of the licensed feature or license suite.

Activation Type

The license activation type:• E-IND - Evaluation license assigned to an individual VMAX

system. Evaluation licenses include an expiration date for reporting purposes only; the product title can still be used.

• P-IND - Permanent license assigned to an individual VMAX system.

• P-ENT - Permanent license assigned to all the VMAX systems in the enterprise.

• P-LTD - Permanent limited license.

Activation ID

The license activation ID.

Capacity Type

The type of licensed capacity.

Capacity Licensed

The licensed capacity value, which is the maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

Installed: The date the license was installed.



When you issue ELM,LIST from a VMAX system running Enginuity 5876 or 5773, 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


Table 10 ELM,LIST output fields under Enginuity 5876 or 5773

Field Description

Symmetrix ID


Activation ID

The activation ID.


Feature Name

The name of the licensed feature.



Checking use of licensesYou can also check how the licenses are used with the ELM,QUERY command, as described in “ELM,QUERY” on page 196.

For each feature, the following information is provided in the report:

◆ Activation type

◆ Licensed capacity

◆ The amount of licensed capacity currently being used

Act The license type:• P-IND - Permanent license assigned to an individual VMAX

system.• P-ENT - Permanent license assigned to all the VMAX systems in

the enterprise.• E-IND - Evaluation license assigned to an individual VMAX

system. Evaluation licenses include an expiration date for reporting purposes only; the product title can still be used.

Capacity Type

The type of licensed capacity. Possible values include:• R-TB-Non-SATA - The licensed capacity applies to the raw

capacity of all devices on the system, excluding SATA.• R-TB-SATA - The licensed capacity applies to the raw capacity of

all SATA devices on the system.• REG-TB - The licensed capacity applies to the registered capacity

of the VMAX system.

Licensed The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

Expiration Date

For an evaluation license, this field displays the expiration date. For a permanent license, this field displays a hyphen (-).

Install Date

The date the license was installed.

Table 10 ELM,LIST output fields under Enginuity 5876 or 5773

Field Description



When you issue ELM,QUERY under HYPERMAX OS 5977 and higher, a report similar to the following displays the licensed features or license suites:

SCF0341I ELM QUERY CNTRL(01585) SCF5005I Report for (Remote) Controller follows 826 Symmetrix ID : 000196701585 Activation ID: N/A Issue Date : 1/11/2016 Capacity -------------------------------Feature Name Act Type Licensed Usage -------------------- ----- ------------- -------- --------Foundation_Suite ENT R-TB-Usable 5 419.8Remote_Replication_S ENT R-TB-Usable 5 419.8 REG-TB N/A 0.0SRDF_Star ENT R-TB-Usable 5 419.8 REG-TB N/A 0.0D@RE ENT R-TB-Usable Array 0.0Fast_X ENT R-TB-Usable Array -ProtectPoint_Suite ENT REG-TB 5 0.0VMAX_OS ENT R-TB-Usable 5 419.8 R-TB-EXTERNAL N/A 0.0SRDF_METRO ENT R-TB-Usable 5 419.8 REG-TB N/A 0.0VMAX3_ZDP ENT R-TB-Usable 5 419.8 REG-TB N/A 0.0Legend: Act(ivation Type): ENT = Entitlement MAN = Manual Override USE = In Use


Table 11 ELM,QUERY output fields under HYPERMAX OS 5977

Field Description

Symmetrix ID


Activation ID



Feature Name

The name of the licensed feature or license suite.

Act The activation type.• ENT - The bundle was activated through an entitlement.• MAN - The product title was manually activated by EMC.• USE - The bundle is activated because it was in use prior to

upgrading to an eLicensed system.

Note: Bundles activated because they were in use (USE) are not considered properly entitled, in which case you should contact EMC for proper entitlement.



When you issue ELM,QUERY under Enginuity 5876 and 5773, a report similar to the following displays the individual feature licenses:

SCF5005I Report for (Local) Controller followsSymmetrix ID : 000195700079Activation ID: N/A Issue Date : N/A Capacity ------------------------------- Feature Name Act Type Licensed Usage -------------------- ----- ------------- -------- -------- SYMM_VMAX_ENGINUITY MAN R-TB-Non-SATA 0 72.8 R-TB-SATA 0 40.0 SYMM_VMAX_TF_CLONE MAN REG-TB 0 4.8 SYMM_VMAX_TF_SNAP MAN REG-TB 0 0.3 SYMM_VMAX_SRDF_S MAN REG-TB 0 - SYMM_VMAX_SRDF_A MAN REG-TB 0 - SYMM_VMAX_SRDF_STAR MAN REG-TB 0 0.0 SYMM_VMAX_SRDF MAN REG-TB 0 3.7 SYMM_VMAX_SMC MAN R-TB-Non-SATA 0 72.8 R-TB-SATA 0 40.0 Legend: Act(ivation Type): ENT = Entitlement MAN = Manual Override USE = In Use


Capacity Type

The type of licensed capacity.

Capacity Licensed

The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

Capacity Usage

The amount of Capacity Licensed currently being used.

Table 11 ELM,QUERY output fields under HYPERMAX OS 5977

Field Description

Table 12 ELM,QUERY output fields under Enginuity 5876 or 5773

Field Description

Symmetrix ID


Activation ID



Feature Name

The name of the licensed feature.



Global State Management

Global State Management (GSM) allows SCF to automatically notify other Mainframe Enabler applications, such as ConGroup, when a configuration change has occurred for the specified VMAX system. When a configuration change occurs for at least one controller included in SCF, the information is broadcast in predetermined intervals.

The information can include the following:

◆ Discovery of a new VMAX system

◆ Removal of an existing VMAX system

◆ Change in Enginuity/HYPERMAX OS version of a VMAX system

◆ Discovery of new devices

◆ Removal of existing devices

◆ Occurrence of a UCB swap

◆ A combination of these events

Act The activation type:• ENT - The product title was activated through an entitlement.• MAN - The product title was manually activated by EMC.• USE - The product title is activated because it was in use prior to

upgrading to an eLicensed system.

Note: Product titles activated manually (MAN) or because they were in use (USE) are not considered properly entitled, in which case you should contact EMC for proper entitlement.

Capacity Type

The type of licensed capacity. Possible values include:• R-TB-Non-SATA - The licensed capacity applies to the raw

capacity of all devices on the system, excluding SATA.• R-TB-SATA - The licensed capacity applies to the raw capacity of

all SATA devices on the system.• REG-TB - The licensed capacity applies to the registered capacity

of the VMAX system.

Capacity Licensed

The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

Capacity Usage

The amount of Capacity Licensed currently being used.

Table 12 ELM,QUERY output fields under Enginuity 5876 or 5773

Field Description



Non-disruptive SymmAPI-MF refreshes

SCF allows the Symmetrix Application Programming Interface for mainframe (SymmAPI-MF) to be refreshed non-disruptively. SCF 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.

Since the SymmAPI-MF is persistent, simply stopping and restarting SCF does not replace the SymmAPI-MF environment, unless you perform a shutdown by issuing theF emcscf,INI,SHUTDOWN command, as described in “Step 5: Shut down SCF” on page 143.

Command Prefix Facility

The 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 command prefix is @123, then the command F SCF,INI,RELOAD can be entered as @123 INI,RELOAD.

When //SCF$nnnn DD DUMMY is specified, nnnn becomes the default SCF command prefix other than value SCF$EMC. If you want “EMC” as the SCF command prefix, specify SCF.INI.CPFX=EMC in the SCF INI file.



SCF log and trace files

SCF automatically creates the following datasets while running:

◆ A log file (SCFLOG)

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 (SCFTRACE)

The dynamic trace file records programmatic events as they occur. You can use this trace file for troubleshooting and diagnostics.

Log and trace file sizeBoth the log file and the dynamic trace file may grow in size as much as the system allows. After either the log file or the dynamic trace file is full, SCF 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: Normally, the log file is closed and reallocated each day at midnight.

You can specify the number of the SCF log files to be created using the SCF.LOG.RETAIN.COUNT initialization parameter, as described in “SCF.LOG.RETAIN.COUNT” on page 84. To set the retention period, use the SCF.LOG.RETAIN.DAYS initialization parameter described in “SCF.LOG.RETAIN.DAYS” on page 84.

For the SCF trace files, specify the file count using the SCF.TRACE.RETAIN.COUNT initialization parameter, as described in “SCF.TRACE.RETAIN.COUNT” on page 119 and set the retention period using the SCF.TRACE.RETAIN.COUNT initialization parameter, as described in “SCF.TRACE.RETAIN.DAYS” on page 119.

Log and trace file nameThe format of the SCF log and trace file names is as follows:

hlq.type.id.Ddate.Ttime

Where:

◆ hlq — The high-level qualifier set using the SCF.WORK.HLQ initialization parameter, as described in “SCF.WORK.HLQ” on page 133.

◆ type — The type of file. Valid values are LOG or TRACE.

◆ id — The 8-character SMF ID padded with ‘$’.

◆ date — The Julian date of allocation in the yyyyddd format.

◆ time — The time of allocation in the hhmmss format.



ENQ Reserve lockoutAn 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.

The following IBM documents provide more information:

◆ Information apar II14297

◆ MVS Planning: GRS

◆ DFSMS: Managing Catalogs

The ENQ lockout that occurs is:

◆ LPAR1 ENQ on SYSIGGV2 with minor name of SCFLOG or SCFTRACE dataset name and reserves the CATALOG volume.

◆ LPAR2 ENQ on SYSIGGV2 with minor name of USERCAT dataset name and waits for SYNCHRES because LPAR1 has reserved the CATALOG volume.

◆ LPAR1 ENQ on SYSIGGV2 with minor name of USERCAT dataset name and waits because LPAR2 holds this resource.

This is an ENQ Reserve lockout.

Here is an example of the required RNL definitions:

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 the dataset name pattern, and 44 bytes for catalog name pattern.

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



SCF reports

ResourcePak Base provides the following reports:

◆ Topology reports

◆ VMAX system report

◆ Subsystem report

◆ Device report

◆ Online device report

The reports can display 4- or 5-digit z/OS device numbers, as described in “Displaying 5-digit z/OS device numbers” on page 185.

Topology reportsThe Topology report lists all VMAX systems discovered by SCF.

To produce a Topology report, use the DEV,DISPLAY command with the TOPOLOGY parameter, as described in “DEV,DISPLAY” on page 188.

The output is similar to the following:

SCF0341I DEV DIS TOPOLOGY SCF0358I LCL SERIAL# MC CCUU MHOP ------ REMOTE SCF0358I 000192600143 5874.000 05100 00FF 000192600143 5874.248SCF0358I ---------------- SCF0358I 01FF 000192600143 5874.248SCF0358I ---------------- SCF0358I 0305 000190300353 5773.163SCF0358I 0306 000190300353 5773.163SCF0358I 0307 000190300353 5773.163SCF0358I 0309 000190300354 5771.112SCF0358I 030F 000192600296 5875.161SCF0358I -------------------------------- SCF0356I DEVICE DISPLAY TOPOLOGY COMMAND COMPLETED.

Displaying remote VMAX systems

You can display remote VMAX systems using the REMOTE parameter of the DEV,DISPLAY command, as described in “DEV,DISPLAY” on page 188.

The output is similar to the following:

SCF0341I DEV DIS REMOTE SCF0358I RMT SERIAL# MC CCUU UCB@ MHOP ------SCF0358I 000000006185 5671.082 04800 022E82D0 0002 SCF0358I 04800 022E82D0 0027 SCF0358I 04800 022E82D0 002F SCF0358I 04800 022E82D0 003D SCF0358I ---------------- SCF0356I DEVICE DISPLAY REMOTE COMMAND COMPLETED.



VMAX system reportThe VMAX system report provides the following information:

◆ VMAX system serial number, name, and type

◆ The date and time of the latest configuration change

◆ Whether the DARE (Data at Rest Encryption) feature is enabled

Note: This information is available under Enginuity 5876 and HYPERMAX OS 5977.

◆ The features or feature suites available with eLicensing

Note: This information is available under Enginuity 5876 and HYPERMAX OS 5977.

◆ Enginuity/HYPERMAX OS major and minor levels

◆ Gatekeeper information

◆ Listing of paths to other VMAX systems

To obtain a VMAX system report, use the DEV,DISPLAY command with the CONTROLLER or CNAME parameter, as described in “DEV,DISPLAY” on page 188.

The following example shows the output from the DEV,DIS,CNTRL(00192600291) command issued from a VMAX 20K system:

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 VMAX_ESSENTIALS_Pack SCF0441I LOCAL_REPLICATION_SuiteSCF0360I CONTROLLER 0001926-00291 HAS 1 SUBSYSTEMS AND IS AT MCLEVEL 5875.156 SCF0345I - 8A00 SCF4011I CONTROLLER 0001926-00291 is currently using CCUU 8A70, Symm device 00000034

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



IBM 2107 emulation

When a VMAX system with Enginuity 5876 or HYPERMAX OS 5977 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,DIS,CNTRL command with an alphanumeric serial number.

Note: Internally, VMAX Series systems retain a numeric serial number for IBM 2107 emulations. Correlation between the numeric and alphanumeric serial numbers is handled within Enginuity/HYPERMAX OS.

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 VMAX_ESSENTIALS_Pack SCF0441I LOCAL_REPLICATION_SuiteSCF0360I CONTROLLER 0001926-00291 HAS 2 SUBSYSTEMS AND IS AT MCLEVEL 5874.103 SCF0345I - 8A00 8A01 SCF4011I CONTROLLER 0001926-00291 is currently using CCUU 8A00, Symm device 000034

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.



Summary report

You can also produce a summary VMAX system report using the SUMmary parameter of the DEV,DISPLAY command. The summary report provides information on all VMAX systems discovered by SCF. The output is similar to the following:

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 5876.000SCF0448I 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 VMAX_ESSENTIALS_Pack SCF0441I LOCAL_REPLICATION_SuiteSCF0421I 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 5876.000SCF0448I Configuration CRC is X'E6B8968D' (changes: add = 1, delete = 0, swap = 2)SCF0449I Last configuration change occurred at 17.34.29 on 02/05/2013SCF0439I DARE is OFFSCF0440I Features available on 000192600296SCF0441I VMAX_ESSENTIALS_Pack SCF0441I LOCAL_REPLICATION_Suite

The command output includes remote VMAX systems discovered as many as 2 hops away. A remote VMAX system is one to which SCF does not have a local CCUU connection.

Note: If you exclude devices from SCF, then SCF may still discover the VMAX system. SCF may then treat it as a remote VMAX system if there are active SRDF connections to it from a system that SCF views as a locally-attached VMAX system.



Subsystem reportThe Subsystem report lists devices in the subsystem and their status.

To obtain a Subsystem report, use the DEV,DISPLAY command with the SSID parameter, as described in “DEV,DISPLAY” on page 188.

The following example shows the output for the specified SSID:

The following example displays an SSID and lists each device defined in that SSID:

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.

An additional state is displayed for SPECIAL devices (displayed as *SPEC*) as shown above where the device is located in an alternate subchannel set:

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.

Device reportThe Device report provides the following information:

◆ Device CCUU and volser

◆ Last known status of the device

◆ Device manufacturer

◆ Serial number of the VMAX system containing the device

◆ SSID

◆ VMAX device number

◆ Lss and cuaddr data following the VMAX device number (optionally)

To obtain a Device report, use the DEV,DISPLAY command with the DEV option, as described in “DEV,DISPLAY” on page 188.

The following example shows the output from the DEV,DIS,DEV(DE10) command:

SCF0341I DEV,DIS,DEV(DE10) SCF0350I DE10(USK272) ONLINE EMC-000190300097-DE00-000272-00-10SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.



Displaying device attributes

To display device attributes in the Device report, use the ATTR or ONLYATTR parameter of the DEV,DISPLAY command, as described in “DEV,DISPLAY” on page 188.

The following example shows the output with the ATTR parameter specified.

SCF0341I DEV DIS DEV(6E40-6E43) ATTR SCF0350I 06E40( ) OFFLINE EMC-000000006185-6C02-000180-02-40 NO DEVICE ATTRIBUTES SCF0350I 06E41( ) OFFLINE EMC-000000006185-6C02-000181-02-41 NO DEVICE ATTRIBUTES SCF0350I 06E42(U6A182) ONLINE EMC-000000006185-6C02-000182-02-42 HOST READ ONLY (PL52)SCF0350I 06E43( ) OFFLINE EMC-000000006185-6C02-000183-02-43 NO DEVICE ATTRIBUTES SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

The following example shows the output with the ONLYATTR parameter specified. Any devices with no host attributes are omitted from the display.

SCF0341I DEV DIS DEV(5100-5103) ONLYATTR SCF0350I 05103( ) OFFLINE EMC-000192600143-5100-00002B-00-03 HOST READ ONLYSCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

SCF0341I DEV DIS DEV(6E40-6E43) ONLYATTR SCF0350I 06E42(U6A182) ONLINE EMC-000000006185-6C02-000182-02-42 HOST READ ONLY (PL52)SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Displaying device volser

To display device volser in the Device report, use the VOLume parameter of the DEV,DISPLAY command, as described in “DEV,DISPLAY” on page 188.

The following example shows the output with the VOLume parameter specified.

SCF0341I DEV,DIS,DEV(0600),VOL SCF0350I 0600(U6J000) OFFLINE EMC-000000006140-DA00-000000-00-00 SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

Displaying volser devices

To display devices for the specified volser, use the VOLume parameter of the DEV,DISPLAY command, as described in “DEV,DISPLAY” on page 188, and specify the required volser.

The following example shows the output for volser USK274:

SCF0341I DEV,DIS,VOL(USK274) SCF0350I DE12(USK274) ONLINE EMC-000190300097-DE00-000274-00-12 SCF0356I DEVICE DISPLAY VOLUME COMMAND COMPLETED.



Online device reportThe Online Device report can be produced in the summary or detailed form:

Summary report

The summary report provides the following information for LPARs with online devices:

◆ SMFID

◆ CPU serial number

◆ Online device count

Only VMAX devices are examined for an online state. Where active, the CSC (Cross-System Communication) component of SCF is used to resolve the CPU serial number to an SMFID. If CSC cannot resolve an SMFID, the value 'Unkn' is displayed.

To obtain a summary Online Device report, use the DEV,DISPLAY command with the ONLine SUMmary options, as described in “DEV,DISPLAY” on page 188.

You can filter output by SMFID or CPU serial number, or both.

Note: For detailed explanation of report fields, refer to the description of message SCF0368I in the Mainframe Enablers Message Guide.

The following example shows the output from the DEV,DIS DEV 3810-3815 ONLINE SUMMARY command:

SCF0368I DEVICE ONLINE SUMMARY Host name CPU serial Device SMFID Online Count --------- ---------- ------------ N229 296A572964 3 Unkn 04AC972965 6 X006 0EAC972965 2 X114 14AC972965 3 --------- ---------- ------------ Online devices in range : 6 Offline devices in range : 0 SCF0366I Device totals - Requested: 6, Found: 6, Excluded: 0, Not

found: 0

Note: ‘Unkn’ indicates that CSC was unable to resolve the CPU serial number to an SMFID.

The following example shows the output from the DEV,DIS DEV 3810-3815 ONLINE SUMMARY FILTER SMFID N* command.

SCF0368I DEVICE ONLINE SUMMARY Host name CPU serial Device SMFID Online Count --------- ---------- ------------ N229 296A572964 3 --------- ---------- ------------ Excluded lines by filter : 3 Online devices in range : 6 Offline devices in range : 0SCF0366I Device totals - Requested: 6, Found: 6, Excluded: 0, Not

found: 0



The following example shows the output from the DEV,DIS DEV 3810-3815 ONLINE SUMMARY FILTER CPUID *2965* command.

SCF0368I DEVICE ONLINE SUMMARY Host name CPU serial Device SMFID Online Count --------- ---------- ------------ Unkn 04AC972965 6 X006 0EAC972965 2 X114 14AC972965 3 --------- ---------- ------------ Excluded lines by filter : 1 Online devices in range : 6 Offline devices in range : 0SCF0366I Device totals - Requested: 6, Found: 6, Excluded: 0, Not

found: 0

The following example shows the output from the DEV,DIS DEV 0000-2FFFF SUMMARY

SCF0368I DEVICE ONLINE SUMMARY 237 Host name CPU serial Device SMFID Online Count --------- ---------- ------------ L2G8 08F2C77490 3 L3W1 01F3E67490 64 L3W2 02F3E67490 64 L3W3 03F3E67490 64 L3W4 04F3E67490 64 N22A 2A6A572964 71 N22B 2B6A572964 242 N22C 2C6A572964 286 N229 296A572964 240 Unkn 0000000000 67 Unkn 03AC972965 3932 Unkn 03F8F87490 32 Unkn 04AC972965 2536 Unkn 04F8F87490 1 Unkn 05F8F87490 32 Unkn 06F8F87490 32 X00B 0FAC972965 6 X006 0EAC972965 148 X107 07AC972965 4 X11A 1AAC972965 4 X11B 1BAC972965 11 X113 13AC972965 71 X114 14AC972965 73 X117 17AC972965 1 X118 18AC972965 3 --------- ---------- ------------ Non-EMC devices skipped : 1451 Online devices in range : 5707 Offline devices in range : 6764 SCF0366I Device totals - Requested: 196608, Found: 13986, Excluded:

2733, Not found: 179889



Detailed report

The detailed report provides the following information for online devices:

◆ Device unit address (sccuu)

◆ VMAX system serial number


◆ Online host count

◆ Host name (SMFID)

◆ CPU serial number

By default, only VMAX devices are examined for an online state. You can include offline/non-EMC devices by specifying the ALLdevices option.

Where active, the CSC (Cross-System Communication) component of SCF is used to resolve the CPU serial number to an SMFID. If CSC cannot resolve an SMFID, the value 'Unkn' is displayed.

To obtain a detailed Online Device report, use the DEV,DISPLAY command with the ONLine DETail options, as described in “DEV,DISPLAY” on page 188.

You can filter output by SMFID or CPU serial number, or both. To display offline/non-EMC devices in the report, specify ALLdevices.

Note: For detailed explanation of report fields, refer to the description of message SCF0369I in the Mainframe Enablers Message Guide.

The following example shows the output from the DEV,DIS DEV 3810-3815 ONLINE DETAIL command:

SCF0369I DEVICE ONLINE DETAIL Unit Controller Symmdv# Host Host name CPU serial Online Count SMFID ----- ------------- -------- ------------ --------- ---------- 03810 0001967-01305 000040 3 Unkn 04AC972965 X114 14AC972965 N229 296A572964 03811 0001967-01305 000041 4 Unkn 04AC972965 X114 14AC972965 N229 296A572964 X006 0EAC972965 03812 0001967-01305 000042 4 Unkn 04AC972965 X114 14AC972965 N229 296A572964 X006 0EAC972965 03813 0001967-01305 000043 1 Unkn 04AC972965 03814 0001967-01305 000044 1 Unkn 04AC972965 03815 0001967-01305 000045 1 Unkn 04AC972965 ----- ------------- -------- ------------ --------- ---------- Online devices displayed: 6 Online devices in range : 6 Offline devices in range : 0 SCF0366I Device totals - Requested: 6, Found: 6, Excluded: 0, Not

found: 0

Note: ‘Unkn’ indicates that CSC was unable to resolve the CPU serial number to an SMFID.



The following example shows the output from the DEV,DIS DEV 3810-3815 ONLINE DETAIL FILTER SMFID N* command.

SCF0369I DEVICE ONLINE DETAIL Unit Controller Symmdv# Host Host name CPU serial Online Count SMFID ----- ------------- -------- ------------ --------- ---------- 03810 0001967-01305 000040 3 N229 296A572964 03811 0001967-01305 000041 4 N229 296A572964 03812 0001967-01305 000042 4 N229 296A572964 ----- ------------- -------- ------------ --------- ---------- Excluded lines by filter : 11 Online devices displayed: 3 Online devices in range : 6 Offline devices in range : 0SCF0366I Device totals - Requested: 6, Found: 6, Excluded: 0, Not

found: 0

Displaying 5-digit z/OS device numbersThe reports display 5-digit z/OS device numbers when either of the following conditions is present:

◆ The Multiple Subchannel Addressing feature is enabled using the SCF.DEV.MULTSS=YES initialization parameter described in “SCF.DEV.MULTSS” on page 57.

Note: “Multiple subchannel addressing” on page 163 describes the Multiple Subchannel Addressing feature.

The report output is similar to the following:

SCF0341I DEV DIS DEVICE(4910-4912) SCF0350I 04910( ) OFFLINE EMC-000192600262-F850-000DC0-01-10SCF0350I 04911( ) OFFLINE EMC-000192600262-F850-000DC1-01-11SCF0350I 04912( ) OFFLINE EMC-000192600262-F850-000DC2-01-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

◆ The subchannel set number of the active device is non-zero.

The report output always includes the subchannel set number if you implicitly specify a subchannel set number in the command.

SCF0341I DEV DIS DEVICE(04910-04912) SCF0350I 04910( ) OFFLINE EMC-000192600262-F850-000DC0-01-10SCF0350I 04911( ) OFFLINE EMC-000192600262-F850-000DC1-01-11SCF0350I 04912( ) OFFLINE EMC-000192600262-F850-000DC2-01-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.

◆ The device is marked as SPECIAL, that is, the device is in an alternate subchannel.

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(14910-14912) SCF0350I 14910( ) SPECIAL EMC-000192600261-4850-000810-02-10SCF0350I 14911( ) SPECIAL EMC-000192600261-4850-000811-02-11SCF0350I 14912( ) SPECIAL EMC-000192600261-4850-000812-02-12SCF0356I DEVICE DISPLAY DEVICE COMMAND COMPLETED.



Command reference

Syntax conventions

The commands follow these syntax conventions:

◆ Keywords appear in uppercase (for example, ALL). They must be spelled exactly as shown.

◆ For easy reference, command keywords are supplemented by lowercase letters to form a meaningful word (for example, CoNTROLler). When typing a command, use only CAPITALIZED characters of any keyword.

◆ 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 SCF 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: [{ATTR|ONLYATTR}]

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



DEV,CH,CNTRL

Indicates if the VMAX system has the specified Enginuity/HYPERMAX OS patch installed.

Syntax

F emcscf,DEV,CH,CoNTRoLler(SymmID)patch#

Parameters

CoNTRoLler(SymmID)

The VMAX system identified with its serial number.

You can specify either a 5-digit or 12-digit ID. If a 12-digit value is used, you can include an optional hyphen between the first 7 digits and the last 5 digits (for example, 1234567-12345). Use the 12-digit ID when multiple VMAX systems have the same last 5 digits.

Note: Use of the full 12-digit VMAX system serial number is recommended.

emcscf

The name of the SCF started task.

patch#

The 5-digit Enginuity/HYPERMAX OS 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.

Command reference 187


DEV,DISPLAY

Displays device information.

Note: “SCF reports” on page 176 describes the reports produced using the DEV,DISPLAY command.

Syntax

F emcscf,DEV,DISplay[,CoNTRoLler(SymmID)][,CNAME(name)][,DEVice sccuu[-sccuu] [VOL][{ATTR|ONLYATTR}][TRU]][,DEVice sccuu[-sccuu] ONLinezzzzz[{SUMmary|DETail [ALLdevices]}]zzzzz[FILTer zzzzzzzzzz{SMFidmask smfidmask [CPUidmask cpuidmask]|zzzzzzzzzzCPUidmask cpuidmask [SMFidmask smfidmask]}][,REMOTE][,SSID(ssid)][,SUMmary][,TOPOlogy][,VOLume(volser)]

Parameters

CoNTRoLler(SymmID)

The VMAX system identified with its serial number to be displayed in the VMAX system report.

Note: “VMAX system report” on page 177 describes the report.



CNAME(name)

The VMAX system identified by its name to be displayed in the VMAX system report.

Note: “VMAX system report” on page 177 describes the report. “Naming VMAX Systems (ESFCTLNM)” on page 221 describes how to assign names to VMAX systems.

If the name contains blanks, enclose the name in quotation marks.



DEVice sccuu[-sccuu][VOL][{ATTR|ONLYATTR}][TRU]

Specifies devices to be displayed in the device report.

Note: “Device report” on page 180 describes the device report.

sccuu[-sccuu]

A DASD device or range of devices. This value may be either 4 or 5 digits and may span subchannel sets.

Note: “Multiple subchannel addressing” on page 163 describes subchannel addressing.

VOL

Forces an I/O to an offline device to read the volser.

ATTR

Adds host attributes of z/OS devices, including the Host Read Only (HRO) attribute, to the display.

ONLYATTR

Adds host attributes of z/OS devices, including the Host Read Only (HRO) attribute, to the display and omits all devices that do not have host attributes.

TRU

Displays recent time and count fields for each displayed device.

DEVice sccuu[-sccuu] ONLinezzzzzzz[{SUMmary|DETail [ALLdevices]}]zzzzzzzzzz[FILTer zzzzzzzzzz{SMFidmask smfidmask [CPUidmask cpuidmask]|zzzzzzzzzzCPUidmask cpuidmask [SMFidmask smfidmask]}]

Displays the online device report.

Note: “Online device report” on page 182 describes the device report.

If neither SUMmary nor DETail is specified, a summary report is displayed, described in “Summary report” on page 182.

sccuu[-sccuu]

A DASD device or range of devices. This value may be either 4 or 5 digits and may span subchannel sets.

Note: “Multiple subchannel addressing” on page 163 describes subchannel addressing.



SUMmary

(Default) Displays the summary online device report, which lists LPARs (by SMFID/CPU serial number) that have the device range online.

Note: “Summary report” on page 182 describes the summary online device report.

DETail

Displays the detailed online device report, which lists devices and LPARs (by SMFID/CPU serial number) that have the VMAX device range online.

Note: “Detailed report” on page 184 describes the detailed online device report.

ALLdevices

Displays both online and offline/non-EMC devices in the detailed report.

Note: When specified together with SUMmary, the ALLdevices option is accepted but ignored.

FILTer zzzzz{SMFidmask smfidmask [CPUidmask cpuidmask]|zzzzzCPUidmask cpuidmask [SMFidmask smfidmask]}]

Filters devices to be displayed in the online device report.

You can filter by SMFID, by CPU ID, or by both.

Specify a subparameter mask as follows:

• '*' matches any number (including 0) of characters.• '?' matches a single character.

For example, ‘*P?’ matches PL, A3PA, 3PL but does not match PL1 or P.

SMFidmask smfidmask

Specify an SMFID mask (up to 4 characters).

Specify ‘UNKN’ as the smfidmask to match any unknown SMFIDs which can occur when CSC cannot resolve the host name.

Note: 'HOSTmask' is an alias of 'SMFidmask'.

CPUidmask cpuidmask

Specify a CPU serial number mask (up to 10 characters).

Note: 'SERialmask' is an alias of 'CPUidmask'.

emcscf




REMOTE

Lists VMAX systems that can only be found across an SRDF connection.

The command output includes 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.

Note: “Displaying remote VMAX systems” on page 176 describes the report.

SSID(ssid)

Displays devices for the specified SSID.


Note: “Subsystem report” on page 180 describes the SSID report.

SUMmary

Produces a summary display of the VMAX systems at startup.

Note: “Summary report” on page 179 describes the summary report.

TOPOlogy

Displays a list of the VMAX systems discovered by SCF.


Note: “Topology reports” on page 176 describes topology reports.

VOLume(volser)

Displays devices for the specified volser.

Note: If the name contains special characters, enclose the name in quotation marks.



DEV,REFRESH

Refreshes device information in the system.

SCF queries each of the specified DASD devices with one or more physical I/Os. This can take from seconds to several minutes.

The DEV,REFRESH command can be used after adding new devices to a VMAX system for a rediscovery of all VMAX devices.

Note: EMC recommends issuing a DEV,REFRESH command when Enginuity/HYPERMAX OS has been upgraded to a higher version, for example, from Enginuity 5876 to HYPERMAX OS 5977.

Syntax

F emcscf,DEV,REFRESH[,GATEKeepers]

Parameters

emcscf


GATEKeepers

Refreshes and revalidates the current gatekeeper devices.

Typically, you issue this command after issuing the INI,REFRESH command to re-read the SCF initialization parameters.

ExampleF 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 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 names of VMAX systems.

Syntax

F emcscf,DEV,RESCAN

Parameters

emcscf


ExampleF EMCSCF,DEV,RESCANSCF0341I DEV,RESCAN SCF0342I DEVICE RESCAN COMMAND ACCEPTED. SCF0413I RESCAN COMPLETE.

DEV,STATUS

Shows the device discovery progress by displaying information about devices that have already been processed.

Note: “Device discovery” on page 162 describes the fields in the device discovery report.

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

Parameters

emcscf


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.



DEV,UNPIN

Unpins gatekeeper devices so that you can proceed with IODF ACTIVATE command.

Note: “Dynamic activation of IODF configuration statements” on page 163 provides more information.

Syntax

F emcscf,DEV,UNPIN,CoNTRoLler(SymmID)

Parameters

CoNTRoLler(SymmID)




emcscf


ExampleF SCFJOBID,DEV,UNPIN,CNTRL(000192600291)



ELM,LIST

Lists all the eLicensed features (Enginuity 5773) or license suites (Enginuity 5876 and HYPERMAX OS 5977) included in the specified VMAX system.

Note: “Listing licenses” on page 166 provides information on listing licenses.

Syntax

F emcscf,ELM,List,CoNTRoLler(SymmID)

Parameters

CoNTRoLler(SymmID)


You can specify either a 5-digit or a 12-digit ID (with or without a hyphen between the first 7 digits and the last 5 digits). Use the 12-digit ID when multiple VMAX systems have the same last 5 digits.


You can also use the following wildcard characters:

* — To match one or more characters

? or % — To match exactly one character in this position.

The following table shows wildcard examples.

emcscf


ExampleSCF0341I ELM,LIST,CNTRL(00215)

Specified value VMAX serial number Match?

*00193 000192600193 Yes

*1926* 000192600193 Yes

00192*193 000192600193 No

000192%%???? 000192600193 Yes

*192%%0???? 000192600193 No

0001926002?? 000192600193 Yes

000192%%0???? 000192600193 Yes

00*192* 000192600193 Yes



ELM,QUERY

Displays the current eLicensing usage report as stored on the specified VMAX system. This usage report is updated only once a day. Any licensing changes since the previous generation of the report are not included in the command output.

Note: “Checking use of licenses” on page 169 provides information on checking used licenses.

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 report instead of the ELM,QUERY report.

Syntax

F emcscf,ELM,Query,CoNTRoLler(SymmID)

Parameters

CoNTRoLler(SymmID)


You can specify either a 5-digit or a 12-digit ID (with or without a hyphen between the first 7 digits and the last 5 digits). Use the 12-digit ID when multiple VMAX systems have the same last 5 digits.


You can also use the following wildcard characters:

* — To match one or more characters

? or % — To match exactly one character in this position.

The following table shows wildcard examples.

emcscf


Specified value VMAX serial number Match?

*00193 000192600193 Yes

*1926* 000192600193 Yes

00192*193 000192600193 No

000192%%???? 000192600193 Yes

*192%%0???? 000192600193 No

0001926002?? 000192600193 Yes

000192%%0???? 000192600193 Yes

00*192* 000192600193 Yes



INI,REFRESH

Rereads the SCF initialization file and stores the new values. No additional initialization processing is performed.

Syntax

F emcscf,INI,REFRESH

Parameters

emcscf


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=0000B0 SCF0301I SCF.CSC.GATEKEEPER.03011.LIST=0000AF SCF0301I SCF.CSC.ACTIVEPOLL=5 SCF0301I SCF.CSC.IDLEPOLL=5 SCF0322I INI REFRESH COMMAND COMPLETED.

INI,RELOAD

Refreshes the SymmAPI-MF environment while SCF is up and running.

The INI,RELOAD command can be issued any time, independent of the applications that use SymmAPI-MF routines. As a result, new code is loaded and all subsequent calls to the SymmAPI-MF routines use the new code.

Syntax

F emcscf,INI,RELOAD

Parameters

emcscf


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

Shuts down the SCF address space and release all resources held by SCF.

Note: “Stopping SCF” on page 141 describes the steps required to shut down SCF.

Syntax

F emcscf,INI,SHUTDOWN

Parameters

emcscf


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



REC,QUERYDEVICELOCK

Displays the current device lock setting.

Syntax

F emcscf,REC,QRYDLOCK|QUERYDEVICELOCK,lockname,cuu[,count][,{LCL,symdv#|RMT,symdv#,srdfgrp|RMT(symdv#,srdfgrp)}]

Note: RMT(symdv#,srdfgrp) is the preferred syntax for the RMT keyword.

Parameters

cuu[,count]

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. The value cannot exceed 2048.

emcscf


LCL

Specifies that the devices are on the local side of an SRDF configuration.

lockname

The lock name. Valid lockname keywords are TF, SNAP, MW, and COPY.

RMT

Specifies that the devices are on the remote side of an SRDF configuration.

srdfgrp

The SRDF group or the hop list for the RMT operation.

Each SRDF group is represented by a one- or two-digit value. You can specify a hop list of up to four SRDF groups separated by periods, for example:

nn.nn.nn.nn

symdv#

The device identified with its VMAX device number.



Example 1F EMCSCF,REC,QRYDLOCK,TF,DE20,3,RMT,1CC,06 SCF0721I REC,QRYDLOCK,TF,DE20,3,RMT,1CC,06 SCF0723I REC DEVICE 0001CC IS LOCKED, LOCKID X'0299304B', DURATION 271SCF0723I REC DEVICE 0001CD IS LOCKED, LOCKID X'0299304B', DURATION 271SCF0723I REC DEVICE 0001CE IS LOCKED, LOCKID X'0299304B', DURATION 271SCF0726I REC COMPLETED

Example 2The following example shows the RMT format using a multi-hop list:

F EMCSCF,REC,QRYDLOCK,TF,3090,1,RMT(000090,1.4.5)



REC,RELEASEDEVICELOCK

Releases the device lock.

Syntax

F emcscf,REC,RELDLOCK|RELEASEDEVICELOCK,lockname,cuu[,count][,{LCL,symdv#|,RMT,symdv#,srdfgrp|RMT(symdv#,srdfgrp)}]

Note: RMT(symdv#,srdfgrp) is the preferred syntax for the RMT keyword.

Parameters

cuu[,count]

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. The value cannot exceed 2048.

emcscf


LCL


lockname

The lock name. Valid lockname keywords are TF, SNAP, MW, and COPY.

RMT


srdfgrp



nn.nn.nn.nn

symdv#

The device identified with its VMAX device number.

ExampleF EMCSCF,REC,RELDLOCK,TF,DE20,3,RMT,1CC,06 SCF0721I REC,RELDLOCK,TF,DE20,3,RMT,1CC,06 SCF0723I REC DEVICE 0001CC IS RELEASED, LOCKID X'0299304B', DURATION 273SCF0723I REC DEVICE 0001CD IS RELEASED, LOCKID X'0299304B', DURATION 273SCF0723I REC DEVICE 0001CE IS RELEASED, LOCKID X'0299304B', DURATION 273

SCF0726I REC COMPLETED



SRV,SYSBUSY,HELP

Displays a list of SRV,SYSBUSY commands with brief descriptions.

Syntax

F emcscf,SRV,SysBusy,HELP

Parameters

emcscf


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 emcscf,SRV,SysBusy,DISplay

Parameters

emcscf


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 emcscf,SRV,SysBusy,DECRement

Parameters

emcscf


Example F EMCSCF,SYSBUSY,DECREMENTSRV active task count changed from 2 to 1



SRV,SYSBUSY,RESET

Resets the number of external applications that currently require SCF to remain active.

Syntax

F emcscf,SRV,SysBusy,RESet

Parameters

emcscf


Example F EMCSCF,SYSBUSY,RESETSRV active task count changed from 2 to 0


CHAPTER 4Controlling Communications (CSC)


◆ Introduction.......................................................................................................... 206◆ Getting started...................................................................................................... 206◆ Controlling communications.................................................................................. 207◆ Command reference .............................................................................................. 217

Controlling Communications (CSC) 205

Controlling Communications (CSC)

IntroductionThe CSC (Cross-System Communication) component of SCF controls inter-LPAR communications.

CSC uses locally and remotely connected VMAX systems to facilitate communications between LPARs. A number of EMC VMAX mainframe applications use CSC to handle inter-LPAR communications.

Getting started

Configuring CSC

After installation of ResourcePak Base, enable and configure CSC using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The CSC initialization parameters are as follows:

◆ SCF.CSC.ACTIVE

◆ SCF.CSC[.{SymmID|RMT}].ACTIVEPOLL

◆ SCF.CSC[.SymmID].ATTNACTIVE

◆ SCF.CSC[.SymmID].ATTNPATHGRP

◆ SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE

◆ SCF.CSC.GATEKEEPER.LIST

◆ SCF.CSC.GATEKEEPER.SymmID.LIST

◆ SCF.CSC[.{SymmID|RMT}].IDLEPOLL

◆ SCF.CSC.INSTANCE

◆ SCF.CSC[.{SymmID|RMT}].MITPERIOD

◆ SCF.CSC.REFORMAT

◆ SCF.CSC[.{SymmID|RMT}].SELTIMEOUT

◆ SCF.CSC[.{SymmID|RMT}].VERBOSE



Controlling communications


Basic operationsTable 13 lists basic CSC operations.

Setting up timingTable 14 lists timing operations.

Enginuity AttentionTable 15 lists operations for setting up the Enginuity Attention feature.

Table 13 Basic operations

Operation Control

Enable/disable CSC SCF.CSC.ACTIVE initialization parameter

Identify SCF instance SCF.CSC.INSTANCE initialization parameter

Specify gatekeepers • SCF.CSC.GATEKEEPER.LIST initialization parameter• SCF.CSC.GATEKEEPER.SymmID.LIST initialization parameter

View registered hosts CSC,DISPLAY,HOSTS command

View registered listeners CSC,DISPLAY,LISTENER command

Enable CSC verbose messaging SCF.CSC[.{SymmID|RMT}].VERBOSE initialization parameter

Refresh CSC information CSC,REFRESH command

Reformat CSC communication area SCF.CSC.REFORMAT initialization parameter

Table 14 Timing operations

Operation Control

Set active polling period SCF.CSC[.{SymmID|RMT}].ACTIVEPOLL initialization parameter

Sets idle polling period SCF.CSC[.{SymmID|RMT}].IDLEPOLL initialization parameter

Set count of inactivity cycles before unregistering host SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE initialization parameter

Set missing interval timing SCF.CSC[.{SymmID|RMT}].MITPERIOD initialization parameter

Set timeout before releasing VMAX system SCF.CSC[.{SymmID|RMT}].SELTIMEOUT initialization parameter

Table 15 Enginuity Attention operations

Operation Control

Enable/disable Enginuity Attention SCF.CSC[.SymmID].ATTNACTIVE initialization parameter

Whether to establish path to offline gatekeeper for Enginuity Attention

SCF.CSC[.SymmID].ATTNPATHGRP initialization parameter

Controlling communications 207


Polling VMAX systems

CSC polls VMAX systems to verify the control records.

You can control polling timing by setting two poll periods:

◆ The active polling period, which is applied when CSC is waiting for responses for outstanding requests, or when new work is being received from other registered hosts in a predetermined active domain period.

The active polling period is defined using the SCF.CSC[.{SymmID|RMT}].ACTIVEPOLL initialization parameter described in “SCF.CSC[.{SymmID|RMT}].ACTIVEPOLL” on page 47.

◆ The idle polling period, which is applied when CSC has no outstanding work and the predetermined active polling domain is no longer active.

The idle polling period is defined using the SCF.CSC[.{SymmID|RMT}].IDLEPOLL initialization parameter described in “SCF.CSC[.{SymmID|RMT}].IDLEPOLL” on page 51.

The active polling period must be less than the idle polling period.

Selecting gatekeepers

There are multiple ways to specify gatekeepers for CSC communications:

◆ Selecting preferred to-be-gatekeeper devices (suggestive specification)

◆ Defining particular devices as gatekeepers (absolute specification)

Selecting preferred to-be-gatekeeper devices You can specify a list of preferred z/OS devices using the SCF.CSC.GATEKEEPER.LIST initialization parameter described in “SCF.CSC.GATEKEEPER.LIST” on page 50.

If a suitable z/OS device cannot be located on this list, the general SCF gatekeepers specified by the SCF.GATEKEEPER.LIST initialization parameter are used.

If a general SCF gatekeeper cannot be located, then all devices for the VMAX system become candidates, taking into account the SCF.DEV.EXCLUDE and SCF.DEV.INCLUDE initialization parameters. In this case, offline devices are chosen in preference to online devices.

If the user does not provide any gatekeepers, SCF defaults to the first device discovered for the VMAX system.



Defining particular devices as gatekeepersYou can also specify a list of VMAX device numbers for a VMAX system using the SCF.CSC.GATEKEEPER[.SymmID].LIST initialization parameter (“SCF.CSC.GATEKEEPER.SymmID.LIST” on page 50).

Note: EMC recommends specifying gatekeepers with the SCF.CSC.GATEKEEPER[.SymmID].LIST initialization parameter when using AutoSwap.

If you use the SCF.CSC.GATEKEEPER[.SymmID].LIST initialization parameter to specify gatekeepers, the SCF.CSC.GATEKEEPER.LIST and SCF.GATEKEEPER.LIST parameters are ignored for this VMAX system.

When unable to locate a gatekeeper, the SCF0603W or SCF0603E message is issued at a regular interval until a gatekeeper is located.

Gatekeeper devices are reprocessed whenever you issue the DEV,REFRESH[,GATEKEEPERS] command. If the gatekeeper list changes, issue the INI,REFRESH command before you issue the DEV,REFRESH[,GATEKEEPERS] command.

Thin gatekeeper supportWith Enginuity 5876 and HYPERMAX OS 5977, you can use thin devices, both FBA and CKD, as the gatekeepers.

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

Polling hosts

CSC polls hosts as follows:

During each MIT (Missing Interval Timing) period, CSC 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 idle polling periods of that host, then CSC issues the SCF0645W message.

◆ If a host has not been seen for the duration of time called the expire cycle, then the host is eligible to be removed (unregistered) from CSC.

The expire cycle is defined using the SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE initialization parameter described in “SCF.CSC[.{SymmID|RMT}].EXPIRECYCLE” on page 49.



Enginuity Attention

CSC can use the Enginuity Attention feature for host notification. This allows messages to be processed quicker and more efficiently. CSC performs a self-test on startup and after a CSC,REFRESH to ensure that the attention interface is working properly. If the self-test fails, messages are issued and CSC returns to the attention-disabled state.

You can enable use of the Enginuity Attention feature using the SCF.CSC[.SymmID].ATTNACTIVE initialization parameter described in “SCF.CSC[.SymmID].ATTNACTIVE” on page 48.

If the Enginuity Attention feature is not enabled, CSC uses the active and idle polling periods for host notification.

Establishing path groupsCSC can establish a path group to its offline gatekeeper if there are no other online devices to the VMAX system that supports the CSC attention interface. After the gatekeeper path group is established, CSC performs a self-test to ensure that the attention interface is working properly.

This feature is enabled by setting the SCF.CSC[.SymmID].ATTNPATHGRP initialization parameter to YES, as described in “SCF.CSC[.SymmID].ATTNPATHGRP” on page 48.

The SCF0659W message is displayed to indicate that no online device could be located and the path group to the gatekeeper has been established.

Note: The SCF0659W message is displayed only when verbose messaging is enabled. “Verbose messaging” on page 216 describes verbose messaging.

if CSC is not permitted to establish a path group, CSC on the host does not receive attention messages from other hosts and relies on the active and idle polling periods for retrieving cross-system messages. CSC displays the SCF0659W message during its self-test stating that self-test failed due to absence of online devices.



Viewing hosts

You can view CSC hosts using the CSC,DISPLAY,HOSTS command described in “CSC,DISPLAY,HOSTS” on page 217. The command outputs the SCF0660I message described in the Mainframe Enablers Message Guide.

Viewing all hostsThe following example shows 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



Viewing hosts for each VMAX systemYou can list CSC hosts for each VMAX system using the CSC,DISPLAY,HOSTS command with the CNTRL(ALL) parameter, as described in “CSC,DISPLAY,HOSTS” on page 217. The output is similar to the following:

SCF0663I CSC,D H CNTRL(ALL) SCF0660I CSC HOST DISPLAY 163 CONTROLLER SERIAL NUMBER : 0001874-00578 GATEKEEPER MVS DEVICE : F700 SYM DEVICE : 000100 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 : 000020 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 : 000000 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 : 000060 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 .........



Viewing hosts for a VMAX systemYou can list CSC hosts for the specified VMAX system using the CSC,DISPLAY,HOSTS command with the CNTRL parameter, as described in “CSC,DISPLAY,HOSTS” on page 217. The output is similar to the following:

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 : 0000D3 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



Working with multiple SCF instances

CSC supports isolation among multiple SCF instances.

CSC determines the set of SCF address spaces that participate in a communication request from an EMC product (such as AutoSwap, z/OS Migrator, ConGroup, and so on) based on the value of the SCF.CSC.INSTANCE initialization parameter described in “SCF.CSC.INSTANCE” on page 52.

Only SCF instances with the same SCF.CSC.INSTANCE value process the communication request. This allows you to isolate multiple SCF instances of a product, for example, to test new versions of a product without interfering with the production instance.

IMPORTANT

If an expected application has not joined the configuration, first check the SCF.CSC.INSTANCE parameter and the CSC,DISPLAY,HOST command output to discover the reason.

Viewing SCF instancesYou can view SCF instances using the CSC,DISPLAY,HOSTS command described in “CSC,DISPLAY,HOSTS” on page 217. The command outputs the SCF0660I message described in the Mainframe Enablers Message Guide.

In the following example, there is only 1 SCF instance active on this set of LPARs that is using SCF instance #22, as shown in the SET column:

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 CSC,DISPLAY,HOSTS command to another SCF instance on the same LPAR X11A, there are 2 SCF address spaces on 2 different LPARs running with the same SCF instance #42. This limits the various applications running against these SCF instances to communicating to only these SCF instances. If, for example, z/OS Migrator is started connected to these SCF instances (through SCF$nnnn DD DUMMY), it does not see or communicate with another SCF instance.

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



Viewing all active SCF instances

All active SCF instances may be displayed using the CSC,DISPLAY,HOSTS command with the ALLSETS parameter, as described in “CSC,DISPLAY,HOSTS” on page 217. The output is similar to the following:

SCF0663I CSC DIS HOSTS SCF0660I CSC DISPLAY HOSTS ALLSETSCONTROLLER 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

For report fields, refer to the description of the SCF0660I message in the Mainframe Enablers Message Guide.

Viewing listeners

Listeners are added by EMC and other vendor code to support particular functions which are to be processed through CSC.

You can list all registered CSC listeners using the CSC,DISPLAY,LISTENER command, as described in “CSC,DISPLAY,LISTENER” on page 219. The output is similar to the following:

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




Refreshing CSC information

To refresh CSC information in the system, use the CSC,REFRESH command, as described in “CSC,REFRESH” on page 220. The output is similar to the following:

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)


Verbose messaging

Verbose messaging provides additional diagnostic information to help monitor the state of your system.

You can enable verbose messaging using the SCF.CSC[.{SymmID|RMT}].VERBOSE initialization parameter, as described in “SCF.CSC[.{SymmID|RMT}].VERBOSE” on page 54.

When disabled, only those CSC messages are displayed that indicate conditions for investigation. The following messages are not issued, or are issued at a reduced frequency:

• SCF0603W and SCF0604E are only displayed once when the condition is detected and after each CSC,REFRESH command is issued.

• SCF0615I

• SCF0630E

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

• SCF0645W

• SCF0659I

• SCF0690I

• SCF0695I



Command reference

Syntax conventions

Refer to “Syntax conventions” on page 186.

CSC,DISPLAY,HOSTS

Displays information about each registered host.

Note: “Viewing hosts” on page 211 provides more information on viewing hosts.

Note: The output of the CSC,DISPLAY,HOSTS command may vary depending on which VMAX systems have responded to the request. For details, refer to description of message SCF0660I in the Mainframe Enablers Message Guide.

Syntax

F emcscf,CSC,DISplay,HOSTs,[ALLSETS][CoNTRoLler({ALL|SymmID})][SORT(column)][TIMEOUT(seconds)]

Parameters

ALLSETS

Displays all active SCF instances.

Note: “Working with multiple SCF instances” on page 214 describes using multiple SCF instances.

CoNTRoLler({ALL|SymmID})

Displays information for specific VMAX systems.

ALL

Produces a system-by-system display that shows all the hosts using each VMAX system.

SymmID


You can specify either a 5-digit or 12-digit ID. If a 12-digit value is used, include a hyphen between the first 7 digits and the last 5 digits (for example, 1234567-12345). Use the 12-digit ID when multiple VMAX systems have the same last 5 digits. Leading zeros are not required.


emcscf




SORT(column#)

Sorts output by the specified column.

column#

Specify the number of the column:

1 (default) — Sort by host name

2— Sort by host ID

3— Sort by VRM

4— Sort by heartbeat

5— Sort by registration date

Note: Sort by VRM does not take into consideration the “A” suffix (which indicates attention on demand support).

TIMEOUT(seconds)

Sets a timeout value between 10 and 120 seconds for the CSC,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.

ExampleF EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(0001845-00309)F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(1845-309)F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(00309)F EMCSCF,CSC,DISPLAY,HOSTS,CNTRL(309)F EMCSCF,CSC,DISPLAY,HOSTS,TIMEOUT(20)F EMCSCF,CSC,DISPLAY,HOSTS,SORT(2)



CSC,DISPLAY,LISTENER

Displays information about each registered listener.

Note: “Viewing listeners” on page 215 provides more information on viewing listeners.

Syntax

F emcscf,CSC,DISplay,LISTENer,CoNTRoLler(SymmID)

Parameters

CoNTRoLler(SymmID)

Displays information for a specific VMAX system.

SymmID




emcscf


ExampleF EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(0001845-00309)F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(1845-309)F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(00309)F EMCSCF,CSC,DISPLAY,LISTENER,CNTRL(309)



CSC,REFRESH

Refreshes CSC information.

If the SCF.CSC.ACTIVE initialization parameter is set to YES, the CSC,REFRESH command activates CSC. All systems with active CSC re-evaluate the gatekeeper device.

If you changed the list of gatekeepers specified using SCF initialization parameters, then issue the INI,REFRESH command before using the CSC,REFRESH command. The CSC,REFRESH command is automatically performed following the INI,REFRESH command.

Note: “Refreshing CSC information” on page 216 provides more information on refreshing CSC information.

Syntax

F emcscf,CSC,REFResh

Parameters

emcscf


ExampleF EMCSCF,CSC,REFRESH


CHAPTER 5Naming VMAX Systems (ESFCTLNM)


◆ Introduction.......................................................................................................... 222◆ Getting started...................................................................................................... 222◆ Naming a VMAX system......................................................................................... 222◆ Command reference .............................................................................................. 223

Naming VMAX Systems (ESFCTLNM) 221

Naming VMAX Systems (ESFCTLNM)

IntroductionResourcePak Base enables you to manage VMAX systems by their names instead of serial numbers. To do this, use the ESFCTLNM utility provided with ResourcePak Base.

Getting started

Running ESFCTLNM utility

The ESFCTLNM utility runs as a batch job. The program name is ESFCTLNM.

The following is an example of JCL for the ESFCTLNM utility.

// jobcard //STEP1 EXEC PGM=ESFCTLNM//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLINB//SCF$nnnn DD DUMMY//SYSPRINT DD SYSOUT=*//SYSIN DD *

ESFCTLNM commands

/*

Where:

◆ jobcard is the job card according to your site standards.


◆ SCF$nnnn identifies the SCF subsystem used for the ESFCTLNM utility.

◆ ESFCTLNM commands are described in “Command reference” on page 223.

Naming a VMAX systemTo assign a name to your VMAX system:

1. Run the ESFCTLNM utility as described in “Running ESFCTLNM utility” on page 222. In the SYSIN DD, include the ASSIGN NAME command described in “ASSIGN NAME” on page 223 and specify a new unique name for your VMAX system.

2. Issue the DEV,RESCAN command of ResourcePak Base to discover the new name, as described in “DEV,RESCAN” on page 193.

The ESFCTLNM utility posts the SCF instance through which it defined the name to do the rescan. Upon completion of the rescan, the new name is available for use.

If there are additional SCF systems 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.

To display VMAX system names, use the DEV,DISPLAY command of ResourcePak Base, as described in “DEV,DISPLAY” on page 188.



Command reference

Syntax conventions


ASSIGN NAME

Assigns a name to the VMAX system.

Syntax

ASSIGN NAME “Symmname” TO CNTRL(SymmID)

Parameters

SymmID

The VMAX system identified with its 12-digit serial number.

Symmname

The name you want to assign to the VMAX system.

The name can be up to 64 characters and is case-sensitive. If you include blanks in the name, enclose the name in quotes. All names shorter than 64 bytes are considered blank-filled.

ExampleTo assign the name “Production Site A” to the VMAX system with serial number 000187431136:

ASSIGN NAME "Production Site A" -TO CNTRL(000187431136)


CHAPTER 6Validating System Paths (ESFCHNU1)


◆ Introduction.......................................................................................................... 226◆ Getting started...................................................................................................... 226◆ Command reference .............................................................................................. 227◆ Return codes......................................................................................................... 228

Validating System Paths (ESFCHNU1) 225

Validating System Paths (ESFCHNU1)

IntroductionTo ensure proper functioning, ResourcePak Base enables you to validate all of the paths that connect to the VMAX system and identify crossed cabling that would put devices in two SSIDs of the same split.

The validation is done with the ESFCHNU1 batch utility. The utility walks each path associated with the specified CCUUs and validate that all of the paths connect to the same VMAX system. This identifies where devices are connected on two channels thus returning different results.

Getting started

Running ESFCHNU1 utility

The ESFCHNU1 utility runs as a batch job. The program name is ESFCHNU1.

The following is an example of JCL for the ESFCHNU1 utility.

// jobcard //JS10 ddddEXEC PGM=ESFCHNU1//SYSOUT DDDD SYSOUT=*//SYSOUT2DDDD SYSOUT=*//SYSIN DD *

ESFCHNU1 commands

/*

Where:


◆ SYSOUT DD specifies the parse output.

◆ SYSOUT2 DD specifies path validation results.

◆ ESFCHNU1 commands are described in “Command reference” on page 227.



Command reference

Syntax conventions


ALL

Validates paths for all CCUUs on the LPAR.

Syntax

ALL

CCUU

Validates paths for the specified CCUUs.

The maximum number of devices at one time is 500 per CCUU statement.

Syntax

CCUU=ccuu,ccuu,...,ccuu

Parameters

ccuu

A devices identified with its CCUU.



Return codesReturn codes for the ESFCHNU1 utility are listed in Table 16.

Table 16 ESFCHNU1 return codes

Return codes Definition

R15=800R0 = 100R0 = 2

OPEN FAILED00INPUT DATASET00OUTPUT DATASET

R15 = 1200R0 = 3

EIOBBLD FAILED


CHAPTER 7Resetting FBA Paths and Devices (ESFFUCBC)


◆ Introduction.......................................................................................................... 230◆ Getting started...................................................................................................... 231

Resetting FBA Paths and Devices (ESFFUCBC) 229

Resetting FBA Paths and Devices (ESFFUCBC)

IntroductionThe ESFFUCBC utility (formerly named FBACHK) resets the VMAX system when the mainframe host is no longer able to see channel paths and devices.

When a Mainframe Enablers component needs to communicate with a VMAX system with fixed-block architecture (FBA) devices, a channel is required for communication.

FBA devices are defined to the host as physical devices in an offline status, and this device definition also provides the channel definition so that Mainframe Enablers can communicate with these FBA devices.

During operation, if FBA devices are brought online and paths are removed from these devices, it is not possible to resolve problems with the FBA devices UCBs and/or subchannels using host software commands.

The ESFFUCBC utility runs on the host and resolves issues with FBA device host control blocks, as well as validating the VMAX configuration for the FBA devices.

The ESFFUCBC utility operates in two modes:

◆ Validates that the CUU is addressable to the host and returns the FBAU0004E message when the device cannot be accessed by the host.

◆ Checks whether the UCB is valid and moves the UCB path installed mask (UCBPIM) to the UCB logical path mask (UCBLPM).

Use the ESFFUCBC utility in the following situations:

◆ A path goes offline, and you cannot bring it back online.

◆ You want to verify that a volume is an FBA device in a VMAX system.

◆ You want to verify that the Enginuity/HYPERMAX OS operating environment is at the correct release level.



Getting started

Running ESFFUCBC utility

The ESFFUCBC utility runs as a batch job.

IMPORTANT

The SCF task must be active when running the ESFFUCBC utility.

The program name is ESFFUCBC. Refer to “Sample JCL” on page 231 for a sample of ESFFUCBC JCL. “Parameters” on page 231 provides description of relevant parameters.

Output from the ESFFUCBC utility goes to the JES message log for the job.

Sample JCL

The following is an example of JCL for the ESFFUCBC utility.

// jobcard //* //* CUU=DEVNO /* SPECIFY DEVICE NUMBER OF THE CONTROL UNIT*/ //* OPT=OPTION /* SPECIFY =VERIFY OR =FIXUCB */ //* //ESFFUCBC EXEC PGM=ESFFUCBC,PARM='3A00,VERIFY' //STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB //SYSPRINT DD SYSOUT=* //SCF$nnnn DD DUMMY

Where:



◆ SCF$nnnn identifies the SCF subsystem used for the ESFFUCBC utility.

Parameters

&CUU A 3- or 4-byte CUU.

&OPT Specify one of the following:

◆ VERIFY — Validates that the CUU is addressable to the host.

◆ FIXUCB — Checks whether the UCB is valid and moves the UCB path installed mask (UCBPIM) to the UCB logical path mask (UCBLPM).

Getting started 231

CHAPTER 8Managing Device Groups (GNS)


◆ Introduction.......................................................................................................... 234◆ Getting started...................................................................................................... 235◆ Managing GNS groups........................................................................................... 236◆ Command reference: EMCGROUP batch utility ....................................................... 242◆ Command reference: SCF GNS............................................................................... 262◆ GNS reason codes................................................................................................. 266

Managing Device Groups (GNS) 233

Managing Device Groups (GNS)

IntroductionGNS (Group Name Services) is the VMAX 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. GNS also allows you to define group names for volumes that can then be operated upon by various other commands.

Each group is a collection of VMAX system and the devices that reside on those systems. For groups that span multiple systems, the definition is stored as a set of components on different VMAX systems, each of which holds its portion of the definition.

Group definitions are maintained through the EMCGROUP batch utility. EMCGROUP allows you to create, view, modify, rename, and delete groups. You can find a description of EMCGROUP batch utility commands in “Command reference: EMCGROUP batch utility” on page 242.

In addition to the EMCGROUP batch utility, you can use ResourcePak Base GNS commands to manage the GNS functionality. The GNS commands are listed in “Command reference: SCF GNS” on page 262.



Getting started

Configuring GNS

After installation of ResourcePak Base, enable and configure the GNS Facility using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The GNS Facility initialization parameters are:

◆ SCF.GNS.ACTIVE

◆ SCF.GNS.WAITINT

Running EMCGROUP batch utility

The EMCGROUP batch utility runs as a batch job. The program name is EMCGROUP.

The following is an example of JCL for the EMCGROUP batch utility.

// jobcard //JS10 EXEC PGM=EMCGROUP//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB//SYSPRINT DD SYSOUT=A,LRECL=121,RECFM=FBA//REPORT DD SYSOUT=A,LRECL=121,RECFM=FBA//SCF$nnnn DD DUMMY//SYSIN DD *

GNS commands

/*

Where:



◆ SCF$nnnn identifies the SCF subsystem used for the EMCGROUP batch utility.

◆ GNS commands are described in “Command reference: EMCGROUP batch utility” on page 242.

DD statementsThe following DD statements are required in the JCL:

SYSPRINT DD SYSOUT=*

The standard output DD where all syntax errors and processing messages will be written.

LRECL=133,RECFM=FBA

REPORT DD Location of DISPLAY and LIST output

LRECL=133,RECFM=FBA

Getting started 235


Managing GNS groups


Table 17 lists GNS operations.

Table 17 GNS operations

Operation Control

View list of GNS groups • GNS,LIST command of SCF• LIST GROUP command of the EMCGROUP batch utility

Create or change GNS group DEFINE GROUP command of the EMCGROUP batch utility

Create enterprise group DEFINE ENTERPRISE GROUP command of the EMCGROUP batch utility

Create or change Gold Copy BCV group DEFINE GROUP FOR GCOPYBCV command of the EMCGROUP batch utility

Create complement group DEFINE COMPLEMENT command of the EMCGROUP batch utility

View members of GNS group DISPLAY GROUP command of the EMCGROUP batch utility

Remove SRDF groups from GNS group REMOVE FROM GROUP RDF GROUP command of the EMCGROUP batch utility

Remove devices from GNS group REMOVE FROM GROUP DEVICE command of the EMCGROUP batch utility

Rename GNS group RENAME GROUP command of the EMCGROUP batch utility

Delete GNS group DELETE GROUP command of the EMCGROUP batch utility

Refresh GNS information in system GNS,REFRESH command of SCF

Delete GNS information from system GNS,FORMAT command of SCF



Defining GNS groups

You can define a GNS group based on the following:

◆ A list of devices identified by their CCUUs or VMAX device numbers

◆ A list of volumes identified by their volsers

◆ An SMS group

◆ An existing SRDF group

Defining GNS groups based on SRDF groupsDefining 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 Groups 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 SRDF group.

To define an GNS group based on an SRDF group, use the INCLUDE RDF GROUP parameter of the DEFINE GROUP command, as described in “DEFINE GROUP” on page 244.

Managing GNS groups 237


GNS group types

The following GNS group types are available:

◆ Non-enterprise groups

◆ Enterprise groups

◆ Gold Copy BCV groups

◆ Complement groups

Non-enterprise groupsA non-enterprise group can include all types of devices. It is also referred to as a mainframe-only group.

To create a non-enterprise group, use the DEFINE GROUP command of the EMCGROUP batch utility, as described in “DEFINE GROUP” on page 244.

Enterprise groupsAn enterprise group is compatible with open systems devices. The following types of enterprise groups are available:

◆ Non-SRDF — The group does not contain any SRDF devices. But it can include BCV, FBA meta (head device only), and CKD meta (head device only) devices.

The following device types are rejected:

• COVD• DRV • GUESTOS• POWERVAULT• R1• R2 • SAVEDEV• SFS • VCMDB

All other device types are allowed.

To create a non-SRDF enterprise group, use the DEFINE ENTERPRISE GROUP command of the EMCGROUP batch utility, as described in “DEFINE ENTERPRISE GROUP” on page 253.



◆ R1/Concurrent R11 — All devices in this group must be R1. Only the head of a meta device is included. R1 BCV devices are allowed.


• COVD • DRV• non-SRDF • POWERVAULT• R2• SAVEDEV • SFS • VCMDB


To create an R1/Concurrent R11 group, use the DEFINE ENTERPRISE GROUP command of the EMCGROUP batch utility with the RDF1 parameter, as described in “DEFINE ENTERPRISE GROUP” on page 253.

◆ R2/Concurrent R22 — All devices in this group must be R2. Only the head of a meta device is included. R2 BCV devices are allowed.


• COVD • DRV• non-SRDF • POWERVAULT• R1• SAVEDEV • SFS • VCMDB


To create an R2/Concurrent R22 group, use the DEFINE ENTERPRISE GROUP command of the EMCGROUP batch utility with the RDF2 parameter, as described in “DEFINE ENTERPRISE GROUP” on page 253.

Gold Copy BCV groupsOnly BCV devices may be included in a Gold Copy BCV Group.

To create a Gold Copy BCV group, use the DEFINE GROUP FOR GCOPYBCV command of the EMCGROUP batch utility, as described in “DEFINE GROUP FOR GCOPYBCV” on page 254.

A Gold Copy BCV group is used as follows:

◆ If an 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 an 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 is used, otherwise, if none of the BCVs are in the group and a suitable BCV is not found, an error is returned.



Complement groupsA complement GNS group contains only those devices that are in an SRDF relationship to devices in the existing GNS group.

Note: Complement groups are a feature of Consistency Groups for z/OS (ConGroup). The Consistency Groups for z/OS Product Guide provides more information.

To create a complement group, use the DEFINE COMPLEMENT command of the EMCGROUP batch utility, as described in “DEFINE COMPLEMENT” on page 243.

The complement group is created based on a GNS 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 base group from which it was created. Changes made 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 using the INCLUDE RDF GROUP keywords of the DEFINE GROUP command, as described in “Defining GNS groups based on SRDF groups” on page 237. 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 PROTECT parameter of the DEFINE GROUP command overrides the membership in the base group.

Example

Suppose GNS group BASEGROUP is defined as follows:

DEFINE GROUP ‘BASEGROUP’ - INCLUDE RDF GROUP = 000184600309,(INC=00) - INCLUDE DEVICE SYMM = 000184600309,(00011E)

Note: “DEFINE GROUP” on page 244 describes the DEFINE GROUP command.

SRDF group 00 is linked to VMAX system 000545454545 and SRDF group 01 is the group on the other side that points back at 000184600309. The device that was explicitly included, 00011E, is a non-SRDF device.

You can create a complement of this group by issuing the following command:

DEFINE COMPLEMENT GROUP ‘BASEGROUP’ NEW ‘OTHER’

Note: “DEFINE COMPLEMENT” on page 243 describes the DEFINE GROUP command.

The result of this operation is a new group created on VMAX number 000545454545 named OTHER. That new group contains an SRDF group INC=01.

The device 00011E that was included in the BASEGROUP is dropped because it does not have a remote mirror.



Open systems group support

You can view open systems composite and device groups using the DISPLAY GROUP (page 256) or LIST GROUP (page 256) command of the EMCGROUP batch utility. However, you cannot modify or delete open systems groups.

In the DISPLAY GROUP and LIST GROUP output, open systems groups are displayed as follows:

◆ The -OCG suffix indicates a composite group (supports multiple VMAX systems).

◆ The -ODG suffix indicates a device group (supports one VMAX system).

Note: Refer to the Solution Enabler Array Management CLI User Guide for information about open systems composite groups and device groups.



Command reference: EMCGROUP batch utility

Overview

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

Table 18 shows the GNS batch commands and their options.

Table 18 GNS batch commands (page 1 of 2)

Command Options

DEFINE COMPLEMENT FOR GROUP gnsgrp NEWname cmpgrp

DEFINE GROUP gnsgrpDEFINE ENTERPRISE [RDF1|RDF2|ANY] GROUP gnsgrp

DEFINE GROUP gnsgrp FOR GCOPY-BCV

INCLUDE VOLUMES = <volser name, mask, or list>

INCLUDE SMS STORAGE GROUP = <sms group name or list>

[options]

INCLUDE DEVICE SYM = SymmID,(<a symdv#, or symdv list or range>)

INCLUDE DEVICE CCUU =(<a ccuu, or ccuu list or range>)

INCLUDE RDF GROUP = SymmID,(INClude=srdfgrp,...)INCLUDE RDF GROUP = SymmID,((LCL=srdfgrp,RECovery=srdfgrp),...)INCLUDE RDF GROUP = SymmID,(PROtect=srdfgrp,...)INCLUDE RDF GROUP = SymmID,(LCL=srdfgrp,...)INCLUDE RDF GROUP = SymmID,((ASYNCra=srdfgrp[,RECovery=srdf-grp],SYNCra=srdfgrp),...)

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. ConGroup). This type of GNS group represents an MSC definition only and cannot be expanded into devices when dis-played by GNS or SRDF Host Component.

EXCLUDE DEVICE SYM = SymmID,(<a symdv#, or symdv list or range>)

EXCLUDE DEVICE CCUU = <a ccuu, or ccuu list or range>

EXCLUDE VOLUMES = <volser name, mask, or list>

DYNAMIC|STATIC

EXTEND

DELETE GROUP gnsgrp



Syntax conventions

For syntax conventions, refer to “Syntax conventions” on page 186.

You can terminate the EMCGROUP batch utility 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 parses all characters on an input line as data. Do not put sequence numbers on the input data, because the sequence numbers will be parsed as data and will cause syntax errors.

DEFINE COMPLEMENT

Defines a complement group based on an existing GNS group.

Note: “Complement groups” on page 240 describes complement groups.

Syntax

DEFINE COMPLEMENT FOR GROUP gnsgrp NEWname cmpgrp

Parameters

cmpgrp

The name of the complement group.

gnsgrp

The name of the GNS group for which you want to define a complement group. The name can be from 1 to 65 alphanumeric characters long.

Note: Place quotes around the names if they contain blanks or special characters.

ExampleDEFINE COMPLEMENT GROUP ‘BASEGROUP’ NEW ‘OTHER’

DISPLAY GROUP gnsgrp XPANDRAG

LIST GROUP

REMOVE FROM GROUP gnsgrp DEVICE SYMM = SymmID,(<a symdv#, or symdv list or range>) RDF GROUP = SymmID,(LCL=srdfgrp,...)

RENAME GROUP gnsgrp NEWNAME new_gnsgrp

Table 18 GNS batch commands (page 2 of 2)

Command Options

Command reference: EMCGROUP batch utility 243


DEFINE GROUP

Creates an GNS group or modifies an existing GNS group.

Note: “Command reference: EMCGROUP batch utility” on page 242 provides and overview of GNS group definitions. “GNS group types” on page 238 describes the available types of GNS groups.

Syntax

DEFINE GROUP gnsgrp [options]

Where options are as follows:

[DYNAMIC|STATIC]

[EXCLUDE DEVICE CCUU=ccuu_list]

[EXCLUDE DEVICE SYM=SymmID,(symdv#_list)]

[EXCLUDE VOLUMES=volser_list]

[EXTEND]

[INCLUDE DEVICE CCUU=(ccuu_list)]

[INCLUDE DEVICE SYM=SymmID,(symdv#_list)]

[INCLUDE RDF GROUP=SymmID,((ASYNCra=srdfgrp[,RECovery=srdfgrp],SYNCra=srdfgrp),...)]

[INCLUDE RDF GROUP=SymmID(INClude=srdfgrp)]

[INCLUDE RDF GROUP=SymmID,(LCL=srdfgrp),...]

[INCLUDE RDF GROUP=SymmID,(...,(LCL=srdfgrp, RECovery=srdfgrp),...]

[INCLUDE RDF GROUP=SymmID(PROtect=srdfgrp,...)]

[INCLUDE SMS STORAGE GROUP=sms_group_list]

[INCLUDE VOLUMES=volser_list]

Parameters

DYNAMIC|STATIC

Determines when the GNS group membership is resolved.

• STATIC — The GNS group membership is only resolved at definition time. This is the default setting.

• DYNAMIC — The GNS 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.

Note: You cannot change the DYNAMIC or STATIC setting after the initial definition.



EXCLUDE DEVICE CCUU=ccuu_list

Excludes the devices specified with their CCUUs from the GNS group.

You can specify a single device, a comma-separated list of devices, or a contiguous range with the first and last devices separated by a hyphen.

Note: The exclusion is applied at definition time and never affects inclusion by SRDF group.

EXCLUDE DEVICE SYM=SymmID,(symdv#_list)

Excludes the devices specified with their VMAX device numbers from the GNS group.

SymmID

The VMAX system identified with its 12-digit serial number. No hyphen is needed.

symdv#_list

The devices identified with their VMAX device numbers.



EXCLUDE VOLUMES=volser_list

Excludes the specified volumes from the GNS group.

You can specify a single volser, a comma-separated list of volsers enclosed in left and right parentheses (for example: (VOL001,VOL002,VOL003)), or a volser mask terminated with an asterisk (for example, VOL0*).


EXTEND

Adds the devices specified in the following parameters to the group named gnsgrp:

• INCLUDE VOLUMES

• INCLUDE DEVICE SYMM

• INCLUDE DEVICE CCUU

• INCLUDE SMS STORAGE GROUP

If the gnsgrp 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.



INCLUDE DEVICE CCUU=(ccuu_list)

Includes the devices specified with their CCUUs in the GNS group.


INCLUDE DEVICE SYM=SymmID,(symdv#_list)

Includes the devices specified with their VMAX device numbers in the GNS group.

SymmID


symdv#_list



INCLUDE RDF GROUP=SymmID,((ASYNCra=srdfgrp[,RECovery=srdfgrp],SYNCra=srdfgrp),...)

Includes the synchronous SRDF group contained in an SRDF/Star configuration into the GNS group.

Note: This GNS group type is intended for MSC use only and is not compatible for use with other EMC applications (e.g., ConGroup). It represents an MSC definition only and cannot be expanded into devices when displayed by GNS or SRDF Host Component.

SymmID


ASYNCra=srdfgrp

Identifies the asynchronous (SRDF/A) SRDF group for the Site B -> Site C leg.

RECovery=srdfgrp

Identifies the recovery group.

The alias for RECovery is RMT.

SYNCra=srdfgrp

Identifies the synchronous (SRDF/S) SRDF group for the Site A -> Site B leg.

For example:

DEFINE GROUP 'RAOBANG' - INCLUDE RDF GROUP = 000190100849,((ASYNCRA=01,REC=17,SYNCRA=F0)) - INCLUDE RDF GROUP = 000190100849,((ASYNCRA=04,SYNCRA=17))



INCLUDE RDF GROUP=SymmID(PROtect=srdfgrp,...)

Identifies the leg of a concurrent set to which actions are limited.

Note: When ConGroup sees this limiting statement, it will generate a SYMGROUP statement for the specified SRDF group. The 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.

The alias for PROtect is LIMit.

SymmID


srdfgrp

You can specify a single SRDF group or a comma-separated list of SRDF groups.

INCLUDE RDF GROUP=SymmID(INClude=srdfgrp)

Includes the SRDF group into the GNS group.

This is a request to include all of the devices for the SRDF group. For example, when ConGroup sees this data type, it expands the membership of the SRDF group, includes all of the devices that are members of the SRDF group, and protects 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 XPANDRAG parameter in the DISPLAY GROUP command.

Note: When ConGroup 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 honors this SRDF group type by limiting its actions to the leg that corresponds to the SRDF group identified by this statement.

SymmID


srdfgrp




INCLUDE RDF GROUP=SymmID,(LCL=srdfgrp,...

Includes all devices of the SRDF group into the GNS group, but limit actions to just the mirrors on this leg.

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: ConGroup always sets the XPANDRAG flag.

INCLUDE RDF GROUP=SymmID,(...,(LCL=srdfgrp, RECovery=srdfgrp),...

Includes the SRDF/A leg and its recovery group in an SRDF/Star configuration into the GNS group.

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., ConGroup). It represents an MSC definition only and cannot be expanded into devices when displayed by GNS or SRDF Host Component.

SymmID


srdfgrp




INCLUDE RDF GROUP=SymmID(PROtect=srdfgrp,...)

Identifies the leg of a concurrent set to which actions are limited.

Note: When ConGroup sees this limiting statement, it will generate a SYMGROUP statement for the specified SRDF group. The 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.

The alias for PROtect is LIMit.

SymmID


srdfgrp


INCLUDE SMS STORAGE GROUP=sms_group_list

Includes the specified SMS groups in the GNS group.

You can specify a single SMS group or a comma-separated list of SMS groups enclosed in left and right parentheses (with no spaces).

The individual members of the SMS group are discovered and stored within this definition.

Note: At definition time, the VMAX 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 VOLUMES=volser_list

Includes the specified volumes in the GNS group.

You can specify a single volser, a comma-separated list of volsers enclosed in left and right parentheses (for example: (VOL001,VOL002,VOL003)), or a volser mask terminated with an asterisk (for example, VOL0*).

gnsgrp

The name of the GNS group. 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.



Example 1DEFINE GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’ - INCLUDE VOLUMES=U*

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

********************************************************************

Example 2 DEFINE GROUP 'Sample Define by Device' - INCLUDE DEVICE SYMM=000187790034,(2B,3C) DISPLAY GROUP 'Sample Define by Device'

EGRP010I PARSING STATEMENT # 1 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 ********************************************************



Example 3DELETE 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)

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 # 9EGRP100I 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



DEFINE ENTERPRISE GROUP

Creates an enterprise group.

Note: “Enterprise groups” on page 238 describes enterprise groups.

When you define an ENTERPRISE group, the ENTERPRISE validation rules are 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 gnsgrp [options]

Parameters

ANY

Specifies that the GNS group can contain a mix of R1, concurrent R11, R2, and concurrent R22 device.

gnsgrp



options

The options are identical to those used by the DEFINE GROUP command, as described in “DEFINE GROUP” on page 244. One exception is that you cannot use the EXTEND keyword for an enterprise group.

RDF1

Adds R1 and concurrent R11 devices to the GNS group.

RDF2

Adds R2 and concurrent R22 devices to the GNS group.



DEFINE GROUP FOR GCOPYBCV

Creates a Gold Copy BCV group.

Note: “Gold Copy BCV groups” on page 239 describes Gold Copy BCV groups.

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.

Syntax

DEFINE GROUP gnsgrp FOR GCOPYBCV [options]

Parameters

gnsgrp



options

The options are identical to those used by the DEFINE GROUP command, as described in “DEFINE GROUP” on page 244.

ExampleDEFINE GROUP 'DTGCOPYBCV' FOR GCOPYBCVINCLUDE DEVICE SYMM = 000195700080,(000400-00043F)

EMCP001I DEFINE GROUP 'DTGCOPYBCV' FOR GCOPYBCV -EMCP001I INCLUDE DEVICE SYMM = 000195700080,(000400-00043F) 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:

000400 000401 000402 000403 000404 000405 000406 000407 000408000409 00040A 00040B 00040C 00040D 00040E 00040F 000410 000411000412 000413 000414 000415 000416 000417 000419 00041A 00041B00041C 00041D 00041E 00041F 000420 000421 000422 000423 000424000425 000426 000427 000428 000429 00042A 00042B 00042C 00042D00042E 00042F

EGRP021I Processing Ended For Statement # 1

Note: Some devices in the range could not be added because they are not BCVs.



DELETE GROUP

Deletes the GNS group.

Syntax

DELETE GROUP gnsgrp

Parameters

gnsgrp



ExampleDELETE GROUP ’Record_#_7’

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



DISPLAY GROUP

Displays members of the GNS group.

DISPLAY GROUP can also display open systems groups indicated as follows:

◆ The -OCG suffix indicates a composite group.

◆ The -ODG suffix indicates a device group.

Note: Refer to “Open systems group support” on page 241 for information about support of open systems groups.

Syntax

DISPLAY GROUP gnsgrp [XPANDRAG]

Parameters

gnsgrp



XPANDRAG

Expands the group to show the devices that belong to the SRDF group(s) included within the definition.

The XPANDRAGT keyword must follow immediately after the GNS group name.

Note: ConGroup always sets the XPANDRAG flag.

Example 1 DISPLAY GROUP ’MANUFACTURING PLANT #1764 TUPOLO MS’

SYSPRINTEGRP010I 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

*********************************************************************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,(000004-000005, 000012, 000014-000015, 000024-000025, 000034-000035, 0000A4-0000A5, 0000B4-0000B5, 0000C4-0000C5, 0000D4-0000D5, 000122, 00012A, 000162, 00016A, 000224-000225, 000234-000237, 000242, 00024A, 000254-000255, 000264-000265, 0002D2, 000312, 00031A, 000344-000345)

INCLUDE DEVICE SYMM = 000184600058,(000004-000005, 000008, 000013-000015, 000024-000025, 0000E4-0000E5, 0000F4-0000F5, 000104-000105, 000114-000115, 0001A2, 0001AA, 0001E2, 0001EA, 000224-000225, 000234-000235, 000242, 00024A, 000254-000255, 000264-000265, 0002D2, 000332, 00033A)

INCLUDE DEVICE SYMM = 000184500120,(000006, 00001E-000021, 00005B-00005F) INCLUDE DEVICE SYMM = 000187790034,(00001A-00001B, 00002A-00002B,

000042-000043, 00032C-00032D, 00036C-00036D) INCLUDE DEVICE SYMM = 000187790072,(000080)

Example 2 DISPLAY GROUP 'INCGRP04U6A' XPANDRAG DISPLAY GROUP 'INCGRP0BU6A' XPANDRAG DISPLAY GROUP 'LCLGRP04U6A' XPANDRAG DISPLAY GROUP 'LCLGRP0BU6A' XPANDRAG DISPLAY GROUP 'PROGRP04U6A' XPANDRAG DISPLAY GROUP 'PROGRP0BU6A' XPANDRAG

GNS Display Request Output PAGE 001

DEFINE GROUP 'INCGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(INC=04) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(0000A0-0000A4, -

0001D0-0001D4, 000546, 00054B, 000550, 000555, 00055A)

DEFINE GROUP 'INCGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(INC=0B) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(0000A1-0000A4, -

0001D0-0001D4, 000238, 000546, 00054B, 000550, 000555, 00055A)

DEFINE GROUP 'LCLGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(LCL=04) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(0000A0-0000A4, -

0001D0-0001D4, 000546, 00054B, 000550, 000555, 00055A)

DEFINE GROUP 'LCLGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(LCL=0B) -* PARTICIPATING CONTROLLER = 000000006185 INCLUDE DEVICE SYMM = 000000006185,(0000A1-0000A4, -

0001D0-0001D4, 000238, 000546, 00054B, 000550, 00555, 00055A)

DEFINE GROUP 'PROGRP04U6A' - INCLUDE RDF GROUP = 000000006185,(LIM=04) -* PARTICIPATING CONTROLLER = 000000006185

DEFINE GROUP 'PROGRP0BU6A' - INCLUDE RDF GROUP = 000000006185,(LIM=0B) -* PARTICIPATING CONTROLLER = 000000006185



LIST GROUP

Displays a list of all GNS groups.

LIST GROUP can also display open systems groups indicated as follows:

◆ The -OCG suffix indicates a composite group.

◆ The -ODG suffix indicates a device group.

Note: Refer to “Open systems group support” on page 241 for information about support of open systems groups.

Syntax

LIST GROUP [groupmask*]

Parameters

groupmask*

You can specify a group name mask using the asterisk (*) as the final character.

A mask consists of a string whose final character is an asterisk. A name matches the mask when the initial characters of the name match the characters of the mask preceding the asterisk.

ExampleLIST GROUP

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

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’



REMOVE FROM GROUP DEVICE

Removes devices from an GNS group.

Syntax

REMOVE FROM GROUP gnsgrp DEVICE SYMM=SymmID,(symdv#_list)

Parameters

gnsgrp



symdv#_list



SymmID




REMOVE FROM GROUP RDF GROUP

Removes the specified SRDF group or groups from an GNS group.

Syntax

REMOVE FROM GROUP gnsgrpRDF GROUP=SymmID,(LCL=srdfgrp,...)

Parameters

gnsgrp



RDF GROUP=SymmID,(LCL=srdfgrp,...)

Removes only SRDF mirrors on this SRDF/A leg from the GNS group.

SymmID

The VMAX system identified with its 12-digit serial number (no dash).

srdfgrp

SRDF group number. You can specify a single SRDF group or a comma-separated list of groups.

Note: Refer to “[INCLUDE RDF GROUP=SymmID,(LCL=srdfgrp),...]” on page 244 for additional details regarding this syntax form.



RENAME GROUP

Renames the GNS group.

Syntax

RENAME GROUP gnsgrp NEWNAME new_gnsgrp

Parameters

gnsgrp

The current name of the GNS group to be renamed. The name can be from 1 to 65 alphanumeric characters long.


new_gnsgrp

The new name of the GNS group. The name can be from 1 to 65 alphanumeric characters long.


ExampleRENAME GROUP 'Sample Define by VolumeS' - NEWNAME 'Sample new group renamed from old'

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



Command reference: SCF GNS

Overview

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

Syntax conventions


GNS,FORMAT

Under HYPERMAX OS 5977 and higher, the GNS,FORMAT command deletes the /SYMMAPI/GNS/MF directory, including all files contained in it, and recreates the directory.

The GNS,FORMAT command forces deletion of all mainframe GNS groups on the VMAX system. The deletion cannot be undone.

Under Enginuity 5876 and 5773, the GSN,FORMAT command forces the communications scratch area to be GNS-compatible. This command eradicates all group information on the VMAX system.

Syntax

F emcscf,GNS,FORMAT,SER#,SymmID

Parameters

emcscf


SER#,SymmID


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 GNS groups defined on the VMAX systems known to this SCF instance. You can choose one of the options:

◆ Display all GNS groups on all VMAX systems or on a particular VMAX system

◆ Display all VMAX systems that contain the specified GNS group

SyntaxF emcscf,GNS,LIST [{,SER#=SymmID|,GROUP=gnsgrp}]

Parametersemcscf


GROUP=gnsgrp

Valid GNS group name less than or equal to 65 characters.

Aliases for GROUP include GR, GRP, GRO, and GROU. You can use comma (,) instead of ‘=’.

SER#=SymmID


SER is an alias for SER#. You can use comma (,) instead of ‘=’.

Example1. To display all GNS groups on all VMAX systems known to this SCF instance:

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

Command reference: SCF GNS 263


2. To display all GNS groups on the VMAX system 000192600262:

F emcscf,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 *********

3. To find out which VMAX systems contain the GNS group “MENOTU”:

F emcscf,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 *********



GNS,REFRESH

Refreshes internal in-memory GNS tables and rebuilds the list of remote VMAX systems.

Note: Issue GNS,REFRESH immediately after completion of the DEV,REFRESH command. “DEV,REFRESH” on page 192 describes the DEV,REFRESH command.

Syntax

F emcscf,GNS,REFRESH

Parameters

emcscf


ExampleF emcscf,GNS,REFRESHSCF0321I GNS,REFRESH SCF0878I GNS COMMAND accepted. SCF0890I GNS, Refresh request has completed.

GNS,REVERT

Note: Under HYPERMAX OS 5977 and higher, the GNS,REVERT command is not supported.

Reverts the specified communications scratch area from a GNS-compatible state to an earlier non-GNS-compatible state.

Syntax

F emcscf,GNS,REVERT,SER#,SymmID

Parameters

emcscf


SER#,SymmID


ExampleF emcscf,GNS,REVERT,SER#,000190103115 SCF0321I GNS,REVERT,SER#,000190103115 SCF0878I GNS COMMAND accepted. SCF0890I 000190103115 HAS BEEN REVERTED SUCCESSFULLY.

Command reference: SCF GNS 265


GNS reason codesTable 19 describes the GNS reason codes.

Table 19 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

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 19 GNS reason codes (page 2 of 2)

Code Reason

GNS reason codes 267

CHAPTER 9Optimizing Performance (QoS)


◆ Introduction.......................................................................................................... 270◆ Getting started...................................................................................................... 271◆ Copy priorities....................................................................................................... 273◆ Dynamic Cache Partitioning (DCP) ......................................................................... 274◆ Mixed SRDF Mode (MRDF) ..................................................................................... 277◆ Symmetrix Priority Control (Enginuity 5876 and 5773)........................................... 279◆ Command reference: Miscellaneous...................................................................... 281◆ Command reference: DCP...................................................................................... 282◆ Command reference: Copy priority......................................................................... 298◆ Command reference: SPC ...................................................................................... 308◆ Command reference: MRDF ................................................................................... 315

Optimizing Performance (QoS) 269

Optimizing Performance (QoS)

IntroductionThe Quality of Service (QoS) Utility allows you to customize priorities of the VMAX system on a logical-volume basis. QoS provides flexibility in managing your VMAX system performance. By fine-tuning the response time for specific copy operations on selected devices or groups, you can increase the overall VMAX performance.

The QoS Utility allows you to define and set various priority values at a logical volume level. These values can affect performance and resource usage within the VMAX system. For example, QoS enables you to differentiate the amount of VMAX global memory committed to various end user applications and thus improve performance.

In addition to the basic functionality of copy priorities, three optional QoS features are available:

◆ Symmetrix Priority Control (SPC) provides a mechanism to determine which device I/O has priority service when the VMAX system is very busy.

◆ Dynamic Cache Partitioning (DCP) enables you to define and manage dynamic cache partitions and associate devices as members of a particular partition.

◆ Mixed SRDF Mode (MRDF) allows you to balance the workload on primary (R1) devices of an SRDF configuration, using MRDF commands with the capability of setting and displaying the values on a VMAX director that handles both synchronous and asynchronous I/O workloads.

Note: MRDF is not available with Enginuity 5773.

Take care when setting various QoS options. Improper QoS configuration may have an adverse effect on performance and resource usage.

Note: You can run QoS only against the following controller types: 3880, 3990, 2105, and 2107.



Getting started

Security prerequisites

Add the QoS Utility to the AUTHPGM and AUTHTSF lists in your SYS1.PARMLIB(IKJTSOxx) member, as described in the Mainframe Enablers Installation and Customization Guide.

The QoS Utility uses SAF calls to validate access to resources. This feature is enabled by default. To disable this feature, refer to the description of the EMCSAFI Security Interface in the 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.

Running the QoS utility

The program name for the QoS Utility is EMCQOS.

Sample JCLThe following is an example of JCL for the QoS Utility.

// jobcard //QOS EXEC PGM=EMCQOS,REGION=4M//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD DUMMY//SCF$nnnn DD DUMMY//SYSOUT DD SYSOUT=*//QOSINPUT DD *

QoS commands

//

Where:



◆ SCF$nnnn identifies the SCF subsystem used for the QoS Utility.

◆ QoS commands include the commands described in “Symmetrix Priority Control (Enginuity 5876 and 5773)” on page 279.

Getting started 271


DD statementsWhen QoS initializes, it requires that you specify the following DD statements in the JCL.

The following DD statements are optional:

QOSINPUT DD Control statements are read from this DD. 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 goes to this DD if specified; otherwise, command output goes to the SYSPRINT DD.



Copy priorities

Overview

The basic QoS functionality allows you to set priority values for different types of copying operations, such as:

◆ SRDF copies

◆ Snap copies

◆ Service copies. The settings are for copy pace during mirror operations.

◆ VLUN copies (Enginuity 5876). The copy priority settings are supported for VLUNs that controls the priority for copies between mirrors of a single device.

◆ BCV copies (Enginuity 5773). In Enginuity 5876 and HYPERMAX OS 5977, BCV copy priorities were discontinued because BCV copies are accomplished with CLONE operations. To set the copy priority values for BCV devices, use the SNPP copy priority parameter.

You can specify QoS 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 VMAX devices and must be within the same VMAX system.

Managing copy priorities

Table 20 lists operations for managing copy priorities.

Table 20 Managing copy priorities

Operation Control

View copy priorities • DISPCPYP and DISPDEV command pair (Enginuity 5876)• QOSGET command

Set copy priorities • SETCPYP and SETDEVCP command pair (Enginuity 5876)• QOSSET command

Reset all copy priorities to 0 • SETCPYP and SETDEVCP command pair, the RESET parameter (Enginuity 5876)

• QOSRESET command

Copy priorities 273


Dynamic Cache Partitioning (DCP)

Overview

DCP is a licensed feature available as an option.

DCP enables you to define up to 8 (Enginuity 5773) or 16 (Enginuity 5876) different cache partitions 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.

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 is rejected. Any attempt to include a new device pair in an SRDF group on which an active SRDF/A session exists is rejected if either device of the pair is in a different cache partition group than that of the devices already in the SRDF/A group.

DCP analysis mode

The DCP analysis mode allows for 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.

The analysis mode can be enabled only if all cache partitions are completely flexible, that is:

◆ The minimum cache allocation (MINCACHE) is set to 0% of total cache.

◆ The maximum cache allocation (MAXCACHE) is set to 100% of total cache.

◆ The minimum time (AGE) before donating cache to another partition is set to 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 the analysis mode, DCP must be enabled before any changes take effect.

In the analysis mode, the system analyzes and generates only statistics. Enabling the analysis mode returns an error if the SETCACHE ENABLE(ANALYSIS) command was not issued, as described in “SETCACHE” on page 289.

When you complete operation in the analysis mode, 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 allows cache partitioning to operate as normal, but with partitions set for analysis mode. Always disable cache partitioning and redefine your partitions after using the analysis mode.



Setting up DCP

Table 21 lists operations for setting up DCP.

Exploring cache partitions

Table 22 lists operations for exploring cache partitions.

Managing cache partitions

Table 23 lists operations for managing cache partitions.

Table 21 Setting up DCP

Operation Control

Enable or disable DCP SETCACHE command, ENABLE/DISABLE parameters

Initialize DCP SETCACHE command, INIT parameter

Modify DCP runtime parameters SETCPMRP command

Enable or disable DCP analysis mode SETCPMRP command, ANALYSIS parameter

Table 22 Exploring cache partitions

Operation Control

View cache partitions for gatekeeper DISPCCFG command

View cache partitions for device DISPCDEV/DISPCDVG and DISPCDV command pairs

View devices in cache partition DISPCGRP command

View general cache partition information DISPCGEN command

View cache partition utilization DISPCUSE command

Table 23 Managing cache partitions

Operation Control

Create cache partition SETCPADD command

Change cache partition SETCPMOD command

Move devices to cache partition SETCPMVD and SETCPMV command pair

Delete cache partition SETCPDEL command

Dynamic Cache Partitioning (DCP) 275


DCP example

The following JCL illustrates the DCP functionality.

//QOS EXEC PGM=EMCQOS,REGION=4M//STEPLIB DD DISP=SHR,DSN=ds_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 devices 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



Mixed SRDF Mode (MRDF)

Overview

MRDF is a licensed feature available as an option under Enginuity 5876 and HYPERMAX OS 5977.

MRDF allows you to implement load-sharing between synchronous and asynchronous I/Os on VMAX directors by applying one of the two servicing policies:

◆ Weighted policy — Servicing is based on CPU weights assigned to workload types on each of the VMAX directors.

The default CPU weights assigned to the VMAX directors when they are brought online are:

• Synchronous I/O — 70%

• Asynchronous I/O — 20%

• Copies —10%

You can set CPU weights to different percentages.

◆ Legacy policy — Servicing is done despite the weights. Asynchronous workloads are preferred over synchronous workloads.

MRDF is supported on both Fiber and GigE SRDF directors, but balances the workload only on the primary (R1) devices.

The feature is backward compatible and is functional even when connected to a VMAX system under lower Enginuity levels. 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 MRDF state.

Mixed SRDF Mode (MRDF) 277


Redistribution of CPU weights

When one or more of the workload types are not active, the CPU weights are automatically adjusted so that the SRDF 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 redistributed to the types of SRDF replication that are active.

Example 1 The default values are set at 70% (synchronous I/O), 20% (asynchronous I/O), and 10% (copies). 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 CPU weights are automatically adjusted to 66.6% for SRDF/A and 33.3% for Adaptive Copy.

Example 2 The default values are set at 70%, 20%, and 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 CPU weights are automatically adjusted to 78% for SRDF/S and 22% for Adaptive Copy.

Example 3 Custom CPU weights are set at 60%, 30%, and 10%. The only active workload is Adaptive Copy. The adaptive copy workload will be able to consume 100% of the SRDF CPU.

When multiple SRDF groups exist on an SRDF director, each active SRDF group shares an equal percentage of the available CPU resource (within their QOS settings). This means that if, for example, there were 2 SRDF groups running SRDF/S in example 2 above, each would get 39% of the SRDF CPU.

As workload types are started/stopped, the weights are adjusted accordingly.

Managing MRDF policy and weights

Table 24 lists operations for managing MRDF policy and weights.

Table 24 Managing MRDF policy and weights

Operation Control

View default policy and CPU weights MRDFDISP DEFAULTS command

View current policy and CPU weights for VMAX director

MRDFDISP WEIGHTS command

View workload type statistics on VMAX director

MRDFDISP RDFSTATS command

Set policy for VMAX directors MRDFSET POLICY command

Set CPU weights for workload types MRDFSET WEIGHTS command

Reset CPU weights to default values MRDFSET RESET command



Symmetrix Priority Control (Enginuity 5876 and 5773)

Overview

Symmetrix Priority Control (SPC) is a licensed feature available as an option under Enginuity 5876 and 5773.

Note: SPC is not available with HYPERMAX OS 5977.

SPC provides a mechanism to differentiate how I/O requests for included devices are handled in busy or heavily shared VMAX systems. Setting device SPC values determines which device I/O has priority service when the VMAX is very busy. In unstressed environments, there may be no noticeable impact.

SPC is enabled at the director level in the VMAX system. Any directors not explicitly included do not invoke SPC priorities. Devices are set with a value between 1 (highest priority) and 16 (lowest priority). Lower values receive priority handling in stressed conditions.

Managing SPC priorities

Table 25 lists operations for managing SPC priorities.

Table 25 Managing SPC priorities

Operation Control

Enable or disable SPC for a VMAX director SETDIR and SETSPC command pair (SETSPC is available under Enginuity 5876 and 5773)

View SPC priorities • DISPSPC command (Enginuity 5876 and 5773)• DISPDEVP and DISPDEV command pair (DISPDEVP is available

under Enginuity 5876 and 5773)

Set SPC priorities SETDEVP and SETDEV command pair (SETDEVP is available under Enginuity 5876 and 5773)

Symmetrix Priority Control (Enginuity 5876 and 5773) 279


SPC example

The following example illustrates the SPC functionality.

//QOS EXEC PGM=EMCQOS,REGION=4M //STEPLIB DD DISP=SHR,DSN=MYSCF.LINKLIB //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD DUMMY //SCF$1234 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)



Command reference: Miscellaneous

Syntax conventions


EXIT

Causes the procedure to exit prior to executing the next statement.

Syntax

EXIT

WAIT

Causes 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 nn

Parametersnn

The number of seconds to wait. The maximum allowable value is 600.

Command reference: Miscellaneous 281


Command reference: DCP

Note: “Dynamic Cache Partitioning (DCP)” on page 274 provides information about Dynamic Cache Partitioning.

Syntax conventions


DISPCCFG

Displays the cache partition configuration for the specified gatekeeper.

Syntax

DISPCCFG {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{ID(partition)|ALL}

Parameters

ALL

Displays data for all cache group partitions.

ID(partition)

The partition ID. Valid values are from 0 to 15. Under Enginuity 5773, the maximum possible value is 7.

LCL(gatekeeper)

Specifies that the devices are on the local side of an SRDF configuration, where gatekeeper is the gatekeeper device identified with its CUU.

Note: Gatekeeper devices can be online or offline, as long as a valid path is available to the referenced VMAX system.

RMT(gatekeeper,hoplist)

Specifies that the devices are on the remote side of an SRDF configuration, where gatekeeper is the gatekeeper device identified with its CUU and hoplist is up to four SRDF groups separated by periods, for example:

nn.nn.nn.nn



ExampleThe following example report illustrates cache configuration parameters for the entire VMAX 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: 57730000 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

Command reference: DCP 283


DISPCDEV/DISPCDVG and DISPCDV

These commands display the cache partition in which the device resides:

◆ The DISPCDEV statement identifies the VMAX devices to display. You can specify up to 32 DISPCDEV statements. The DISPCDVG statement identifies the SRDF group. You can specify either of these two statements.

◆ The DISPCDV statement determines the path to the local or remote side of an SRDF configuration.

Syntax

DISPCDEV {CUU(cuu[-cuu])|symdv#[-symdv#]}--or--DISPCDVG RDFG(srdfgrp)

DISPCDV {LCL(gatekeeper)|RMT(gatekeeper,hoplist)}

Parameters

CUU(cuu[-cuu])

Devices identified with their z/OS device numbers. You can specify a single device or a range. The first and last devices in the range are checked to ensure that they are in the same VMAX system. Any range must be contiguous. If a CUU within the range does not exist, you receive an error message.

LCL(gatekeeper)


Note: Gatekeeper devices can be online or offline, as long as a valid path is available to the VMAX system that you are referencing.

RDFG(srdfgrp)

Identifies an SRDF group. Only 1 SRDF group can be specified.



nn.nn.nn.nn


symdv#[-symdv#]

Devices identified with their VMAX device numbers. You can specify a single device or a range.



Example 1The following example 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 000030 07 000031 07 000032 07 000033 07 000034 07 000035 07 000036 07 000037 07 000038 07 000039 07 00003A 07 00003B 07 00003C 07 00003D 07 00003E 07 00003F 07 000000 00 000000 00 000000 00 000000 00

Example 2The following example 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 000049 07 00004A 07 00004B 07 00004C 07 00004D 07 00004E 07 00004F 07 000000 00 000000 00 000000 00



DISPCGEN

Displays general cache partition information.

Syntax

DISPCGEN {LCL(gatekeeper)|RMT(gatekeeper,hoplist)}

Parameters

LCL(gatekeeper)





nn.nn.nn.nn




DISPCGRP

Displays the devices in the specified cache partition.

If the partition is not specified, the default ID(0) is used.

Syntax

DISPCGRP {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition)

Parameters

ID(partition)

The partition ID. Valid values are from 0 to 15. The default value is 0.

Note: Under Enginuity 5773, the maximum possible value is 7.

LCL(gatekeeper)



RDFG(srdfgrp)




nn.nn.nn.nn


ExampleThe following example 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 000030 07 000031 07 000032 07 000033 07 000034 07 000035 07 000036 07 000037 07 000038 07 000039 07 00003A 07 00003B 07 00003C 07 00003D 07 00003E 07 00003F 07 000048 07 000050 07 000051 07 000052 07 000053 07 000054 07 000055 07 000056 07 000057 07 0000C0 07 0000C1 07 0000C2 07 0000C3 07 000282 07 000283 07 000284 07 000285 07 000292 07 000293 07 000294 07 000295 07 000000 00 000000 00 000000 00



DISPCUSE

Displays information on dynamic cache partition utilization.

Syntax

DISPCUSE {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{ID(partition)|ALL}

Parameters

ALL

Displays data for all cache group partitions.

ID(partition)


LCL(gatekeeper)





nn.nn.nn.nn


ExampleThe following example illustrates cache partition utilization parameters for the entire VMAX 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



SETCACHE

Initializes, disables, or enables Dynamic Cache Partitioning (DCP). You must have proper security authorization to use this command.

Syntax

SETCACHE {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{INIT|ENABLE[(ANALYSIS)]|DISABLE}

Parameters

DISABLE

Disables dynamic cache partitioning.

ENABLE[(ANALYSIS)]

Enables dynamic cache partitioning.

ANALYSIS

Enables dynamic cache partitioning in the analysis mode.

Note: “DCP analysis mode” on page 274 describes the analysis mode.

INIT

Initializes dynamic cache partitioning.

If you execute an INIT while DCP is active, it causes automatic disable action. All devices are returned to the default partition and any defined partitions are deleted.

LCL(gatekeeper)





nn.nn.nn.nn




SETCPADD

Creates a dynamic cache partition. You must have proper security authorization to use this command.

Syntax

SETCPADD {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition),TCACHE(target%),MINCACHE(min%),MAXCACHE(max%),AGE(seconds),WP(wp%),CPNAME(partitionname),XRCP

Parameters

AGE(seconds)

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 for the partition.

No embedded blanks or special characters except underscore (“_”) are allowed. The name cannot begin or end with an underscore.

ID(partition)


LCL(gatekeeper)



MAXCACHE(max%)

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(min%)

The minimum cache allocation for the partition as a percentage of total cache. The value cannot be greater than the target cache allocation.



nn.nn.nn.nn




TCACHE(target%)

The target cache allocation for the partition as a percentage of total cache. The value can be between 10 and 90%.

WP(wp%)

The write pending limit for the partition, represented with a percentage. 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) is issued.



SETCPDEL

Deletes a dynamic cache partition. Any devices in this partition are moved to the default partition. You must have proper security authorization to use this command.

Syntax

SETCPDEL {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition)

Parameters

ID(partition)


LCL(gatekeeper)





nn.nn.nn.nn




SETCPMOD

Modifies a dynamic cache partition. You must have proper security authorization to use this command.

Syntax

SETCPMOD {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition),TCACHE(target%),MINCACHE(min%),MAXCACHE(max%),AGE(seconds),WP(wp%),CPNAME(partitionname)

Parameters

AGE(seconds)

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 for the partition.

No embedded blanks or special characters except underscore “_” are allowed. The name cannot begin or end with an underscore.

ID(partition)


LCL(gatekeeper)



MAXCACHE(max%)

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(min%)

The minimum cache allocation for the partition as a percentage of total cache. The value cannot be greater than the target cache allocation.



nn.nn.nn.nn

Note: Gatekeeper devices can be online or offline, as long as a valid path is available to the REFERENCED VMAX system.



TCACHE(target%)

The target cache allocation for the partition as a percentage of total cache. The value can be between 10% and 90%.

WP(wp%)

The write pending limit for the partition, represented with a percentage. The value can be between 40% and 80%.



SETCPMRP

Modifies DCP runtime parameters.

Syntax

SETCPMRP {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{XRCP({ENABLE,partition|DISABLE})|ANALYSIS({ENABLE|DISABLE})}

Parameters

ANALYSIS({ENABLE|DISABLE})

Enables or disables the DCP analysis mode.

Note: ENABLE returns an error if SETCACHE ENABLE(ANALYSIS) was not issued.

LCL(gatekeeper)





nn.nn.nn.nn


XRCP({ENABLE,partition|DISABLE})

Enables or disables XRC processing for the specified partition.

Note: XRCP(ENABLE,partition) is only valid if SETCPADD was not issued with the XRCP option or after a XRCP(DISABLE) has been issued.



SETCPMVD and SETCPMV

This command pair moves devices to the specified partition:

◆ The SETCPMDV statement identifies VMAX devices to be moved.

◆ The SETCPMV statement determines the path to the local or remote side of an SRDF configuration and identifies the partition.

You can specify up to 32 SETCPMVD statements.

Note: Devices within an SRDF/A group cannot be moved individually. You must use the RDFG option and move the whole group.

You must have proper security authorization to use this command.

Syntax

SETCPMVD {CUU(cuu[-cuu])|symdv#[-symdv#]|POOL(poolname)}

SETCPMV {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition)

SETCPMVD RDFG(srdfgrp)

SETCPMV {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition),TYPE(RDFG)

SETCPMVD {CUU(cuu[-cuu])|symdv#[-symdv#]

SETCPMV {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},ID(partition),TYPE({META|SCKD})

Parameters

CUU(cuu[-cuu])


LCL(gatekeeper)





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.

RDFG(srdfgrp)




nn.nn.nn.nn


symdv#[-symdv#]


TYPE(RDFG)

Move all devices in the specified SRDF group.

If you specify this option, it must be specified on both the SETCPMVD and SETCPMV statements.

TYPE({META|SCKD})

Note: Starting with HYPERMAX OS 5977, the TYPE({META|SCKD}) option is not supported.

Specifies the type of devices to be moved:

• META — Moves all members in a meta definition. You must specify the meta head device.

• SCKD — Moves striped CKD devices.

Example

SETCPMVD POOL(myPool)SETCPMV LCL(c400),ID(5)



Command reference: Copy priority

Note: “Copy priorities” on page 273 provides information about copy priorities.

Syntax conventions


DISPCPYP and DISPDEV

This command pair displays the current copy priority settings:

◆ The DISPCPYP statement identifies the VMAX devices for which to display the copy priority settings.

◆ The DISPDEV statement determines the path to the local or remote side of an SRDF configuration and sets the required copy types.

You can specify up to 32 statements.

Each DISPCPYP statement followed by a DISPDEV statement. The commands must be coded in this order, or you receive an error.

When specifying multiple DISPCPYP statements, you cannot mix VMAX device numbers and CUUs. Otherwise, you receive an error. Also, the device numbers or CUUs must be in sequential order for them all to be processed.

Note: The DISPCPYP command requires Enginuity 5876 or higher.

Syntax

DISPCPYP {CUU(cuu[-cuu])|symdv#[-symdv#]|RA(srdfgrp)|ALL}

DISPDEV {LCL(gatekeeper)|RMT(gatekeeper,hoplist)|SER(symm#)}

[,[NOT(][SNPP(#)][,RDFP(#)][,SERP(#)][,VLUN(#)][)]]

Parameters

ALL

Displays the copy priority settings for all VMAX devices.

CUU(cuu[-cuu])


LCL(gatekeeper)





[,NOT(][,RDFP(#)][,SERP(#)][SNPP(#)][,VLUN(#)])]

Filter the results to include or exclude (using the NOT operator) one or more of the following copy types:

• RDFP — Remote Data Facility copies

• SERP — Service copies (copy pace during mirror operations)

• SNPP — Snap copies

• VLUN — Virtual logic unit volume copies

Note: VLUN is supported with Enginuity 5876 only.

RA(srdfgrp)

A two-digit value from 00 to F9 representing the SRDF group to display the copy priority settings.



nn.nn.nn.nn


SER(symm#)


symdv#[-symdv#]


ExampleThe following example 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: 58760000 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

Command reference: Copy priority 299


QOSGET

Displays the current copy priority settings.

Syntax

QOSGET

{

{CUU=cuu[-cuu]|RA(srdfgrp)|ALL}|

SER(symm#,{symdv#[-symdv#]|RA(srdfgrp)|ALL})|

LCL(gatekeeper,{symdv#[-symdv#]|RA(srdfgrp)|ALL})|

RMT(gatekeeper,{symdv#[-symdv#]|RA(srdfgrp)|ALL},hoplist)|

}

[,[NOT(][,BCVP(#)][,RDFP(#)][,SERP(#)][SNPP(#)][)]]

Parameters

ALL

Displays the copy priority settings for all VMAX devices.

CUU=cuu[-cuu]


LCL(gatekeeper)



[,[NOT(][,BCVP(#)][,RDFP(#)][,SERP(#)][SNPP(#)][)]]

Filter the results to include or exclude (using the NOT operator) one or more of the following copy types:

• BCV — BCV copies




RA(srdfgrp)

A two-digit value from 00 to F9 representing the SRDF group to display the copy priority settings.





nn.nn.nn.nn


SER(symm#)


symdv#[-symdv#]


Example QOSGET CUU=B300QOSGET CUU=B310-B320



QOSRESET

Resets the current copy priority settings to the default value of 0.

The QOSRESET command automatically resets the RAID 10 member devices if the head device is set.

Note: Under Enginuity 5876 and HYPERMAX OS 5977, the QOSRESET command is tolerated.

Syntax

QOSRESET

{

{CUU=cuu[-cuu]|RA(srdfgrp)}|

SER(symm#,{symdv#[-symdv#]|RA(srdfgrp)})|

LCL(gatekeeper,{symdv#[-symdv#]|RA(srdfgrp)})|

RMT(gatekeeper,{symdv#[-symdv#]|RA(srdfgrp)},hoplist)|

}

Parameters

CUU=cuu[-cuu]


LCL(gatekeeper)



RA(srdfgrp)

A two-digit value from 00 to F9 representing the SRDF group to set copy priority settings.



nn.nn.nn.nn




SER(symm#)


symdv#[-symdv#]


ExampleQOSRESET CUU=B300QOSRESET CUU=B310-B320



QOSSET

Sets the copy priority settings.

The priority settings take effect immediately. After you set the values, QoS retains them across an IML1 of the VMAX 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.

QOSSET automatically sets the RAID 10 member devices if the head device is set.

Note: Under Enginuity 5876 and HYPERMAX OS 5977, the QOSSET command is tolerated.

Syntax

QOSSET

{

{CUU=cuu[-cuu]|RA(srdfgrp)}|

SER(symm#,{symdv#[-symdv#]|RA(srdfgrp)})|

LCL(gatekeeper,{symdv#[-symdv#]|RA(srdfgrp)})|

RMT(gatekeeper,{symdv#[-symdv#]|RA(srdfgrp)},hoplist)|

}

[,copy_type=nn]

Parameters

copy_type=nn

Sets the priority for the selected copy type. You can specify several copy types (together with their priority values) separated with commas.

copy_type can be one or more of the following:

• BCVP — BCV copies




To specify the priority, replace nn with a value from 0 to 16, where 0 represents the highest priority (default).

1. Initial Memory Load



The valid values for the copy type are as follows:

CUU=cuu[-cuu]


LCL(gatekeeper)



RA(srdfgrp)




nn.nn.nn.nn


SER(symm#)


symdv#[-symdv#]


ExampleQOSSET CUU=B300,RDFP=1,BCVP=3,SERP=4

HYPERMAX OS 5977 and Enginuity 5876 Enginuity 5773

BCVP 0 through 16 0 through 16

RDFP No effect 0 through 16

SERP 0 through 16 0 through 16

SNPP 0 through 16 0 through 16



SETCPYP and SETDEVCP

This command pair sets copy priority settings:

◆ The SETCPYP statement identifies the VMAX devices for which to set copy priority settings.

◆ The SETDEVCP statement determines the path to the local or remote side of an SRDF configuration and sets the required copy types.


Each SETCPYP statement must be followed by a SETDEVCP statement. The commands must be coded in this order, or you receive an error.

When specifying multiple SETCPYP statements, you cannot mix VMAX device numbers and CUUs. If these values are mixed, you receive an error. Also, the device numbers or CUUs must be in sequential order for them all to be processed.

Note: The SETCPYP command requires Enginuity 5876 or higher.

Syntax

SETCPYP {CUU(cuu[-cuu]) | symdv#[-symdv#] | RA(srdfgrp)}

SETDEVCP {LCL(gatekeeper)|RMT(gatekeeper,hoplist)|SER(symm#)}

{[copy_type({nn|URGent})]|[RESET]}

Parameters

copy_type({nn|URGent})

Sets the priority or the URGent option for the selected copy type. You can specify more than one copy types (together with their priority values) separated with commas.

copy_type can be one or more of the following:




• VLUN — Virtual logic unit volume copies

Note: VLUN is supported with Enginuity 5876 only.

To specify the priority, replace nn with a value from 0 to 16, where 0 represents the highest priority (default), or specify the URGent priority.

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



CUU(cuu[-cuu])


LCL(gatekeeper)



RA(srdfgrp)


RESET

Sets all priorities to the default value of 0 for the specified devices.



nn.nn.nn.nn


SER(symm#)


symdv#[-symdv#]




Command reference: SPC

Note: “Symmetrix Priority Control (Enginuity 5876 and 5773)” on page 279 provides information about Symmetrix Priority Control.

Syntax conventions


DISPDEVP and DISPDEV

Note: Starting with HYPERMAX OS 5977, the DISPDEVP command is not supported.

This command pair displays the current priority settings:

◆ The DISPDEVP statement identifies the VMAX devices for which to display the priority settings.

◆ The DISPDEV statement determines the path to the local or remote side of an SRDF configuration.


Each DISPDEVP statement followed by a DISPDEV statement. The commands must be coded in this order, or you receive an error.

Syntax

DISPDEVP CUU(cuu[-cuu])|symdv#[-symdv#]

DISPDEV LCL(gatekeeper)|RMT(gatekeeper,hoplist)

Parameters

CUU(cuu[-cuu])


LCL(gatekeeper)





nn.nn.nn.nn




symdv#[-symdv#]


DISPSPC

Note: Starting with HYPERMAX OS 5977, the DISPSPC command is not supported.

Displays the Symmetrix Priority Control (SPC) settings for the specified gatekeeper.

Syntax

DISPSPC LCL(gatekeeper)|RMT(gatekeeper,hoplist)

Parameters

LCL(gatekeeper)





nn.nn.nn.nn


Command reference: SPC 309


ExampleIn 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: 57730000 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:



SETDEVP and SETDEV

Note: Starting with HYPERMAX OS 5977, the SETDEVP command is not supported.

Assigns an SPC priority to the specified devices.

◆ The SETDEVP statement identifies the VMAX devices for which to set a priority and provides the priority values.

◆ The SETDEV statement determines the path to the local or remote side of an SRDF configuration.

The device must be a valid STD or BCV device. 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.

Each SETDEVP statement must be followed by a SETDEV statement. The commands must be coded in this order, or you receive an error.

Note: You must have proper security authorization to use this command.

Syntax

SETDEVP CUU(cuu[-cuu])|symdv#[-symdv#],priority

[,META][SCKD]

SETDEV LCL(gatekeeper)|RMT(gatekeeper,hoplist)

Parameters

CUU(cuu[-cuu])


LCL(gatekeeper)



META

Use this option to set the priority on the META head device. You cannot specify a range with this option.

priority

The priority value. Valid values are from 1 to 16.





nn.nn.nn.nn


SCKD

Use this option to set the priority on striped CKD head device. You cannot specify a range with this option.

symdv#[-symdv#]




SETDIR and SETSPC

Note: Starting with HYPERMAX OS 5977, the SETSPC command is not supported.

This command pair enables 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.

When SETDIR is used to set the directors, multiple SETDIR statements can be specified.

SETSPC can be used alone to initialize or reset SPC. When INIT or RESET is used with the SETSPC command, the SETDIR command cannot be used.

Note: You must have proper security authorization to use this command.

Syntax

SETDIR #,#-#|RESET

SETSPC LCL(gatekeeper)|RMT(gatekeeper,hoplist)

--or--

SETSPC LCL(gatekeeper)|RMT(gatekeeper,hoplist),{INIT|RESET}

Parameters

#,#-#

Identifies directors to enable SPC. Unspecified directors are disabled. Valid values are 1 to 128. A maximum of 4 directors and/or ranges can be specified per SETDIR statement.

INIT|RESET

INIT initializes SPC 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 disables automatic updates. All directors are SPC-disabled.

LCL(gatekeeper)



RESET

Disables SPC on all the directors.





nn.nn.nn.nn


ExampleIn this example, all of the directors have been set:

SETDIR 1-64SETSPC LCL(9A00)

Serial Number: 000190300344 Model Number: 07 MicroCode Level: 57730000 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



Command reference: MRDF

Note: “Mixed SRDF Mode (MRDF)” on page 277 provides information about MRDF.

Syntax conventions


MRDFDISP DEFAULTS

Displays the default policy and CPU weights on all SRDF directors.

Syntax

MRDFDISp Defaults {LCL(gatekeeper)|RMT(gatekeeper,hoplist)}

Parameters

LCL(gatekeeper)





nn.nn.nn.nn


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

Command reference: MRDF 315


MRDFDISP RDFSTATS

Displays MRDF statistics for the SRDF group. If no director is specified, information on all SRDF directors for the VMAX system is displayed.

Syntax

MRDFDISp RDFstats {LCL(gatekeeper)|RMT(gatekeeper,hoplist)}[,RADir(director)]

Parameters

LCL(gatekeeper)



RADir(director)

The SRDF director number in hex in the range of x'01' through x'80'.



nn.nn.nn.nn


ExampleEMCP001I MRDFDISP RDFSTATS RMT(B160,5A)

Mixed Mode RDF Stats for Symm Serial:000196800914

[...]

RADir SYNC WRITES SIZE(KB) ----- ----------- -------- 71 212 M 1 G

ASYNC WRITES SIZE(KB) ------------ -------- 89 M 3 G

COPIES WRITES SIZE(KB) ------------- -------- 25 M 1 G

END OF MRDFDISP RDF STATS STATEMENT



MRDFDISP WEIGHTS

Displays the current active policy and the CPU weights assigned to the workloads on all VMAX directors.

Syntax

MRDFDISp Weights {LCL(gatekeeper)|RMT(gatekeeper,hoplist)}[,RADir(director)]

Parameters

LCL(gatekeeper)



RADir(director)




nn.nn.nn.nn


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



MRDFSET POLICY

Sets the MRDF policy for all SRDF directors on the VMAX system.

Syntax

MRDFSET POLICY{LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{LEGACY|WEIGHTED)

Where:

LCL(gatekeeper)



LEGACY

Sets the LEGACY policy.

RADir(director)




nn.nn.nn.nn


WEIGHTED

Sets the WEIGHTED policy.

ExampleEMCP001I MRDFSET POLICY LCL(3A01),WEIGHTED Mixed Mode Policy for Symm Serial: 000195700086 has been set to:

WEIGHTED END OF MRDFSET POLICY STATEMENT



MRDFSET RESET

Resets the system-level or director-level CPU weights 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.

Syntax

MRDFSET RESet {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{RADir(director)|Defaults}

Parameters

Defaults

Applies the weights to all SRDF directors when the system is brought online.

LCL(gatekeeper)



RADir(director)




nn.nn.nn.nn


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



MRDFSET WEIGHTS

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

Syntax

MRDFSET Weights {LCL(gatekeeper)|RMT(gatekeeper,hoplist)},{RADir(director)|Defaults},Sync(%),Async(%),Copies(%)

Parameters

Async(%)

The director CPU percentage (weight) for Asynchronous SRDF workloads.

You can specify a decimal value between 1 and 98. The default value is 20.

Note: The values of Sync, Async, and Copies parameters must equal 100.

Copies(%)

The director CPU percentage (weight) for Host Copies workloads.



Defaults

Applies the weights to all SRDF directors when the system is brought online.

LCL(gatekeeper)



RADir(director)




nn.nn.nn.nn




Sync(%)

The director CPU percentage (weight) for Synchronous SRDF workloads.



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


CHAPTER 10Optimizing Multi-Track I/Os (zBoost PAV Optimizer)


◆ Introduction.......................................................................................................... 324◆ Getting started...................................................................................................... 325◆ Optimizing I/Os .................................................................................................... 327◆ SMF recording ....................................................................................................... 334◆ Command reference .............................................................................................. 347

Optimizing Multi-Track I/Os (zBoost PAV Optimizer) 323

Optimizing Multi-Track I/Os (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 329, “Limiting optimization by started task/job” on page 330, and “Limiting optimization by tracks” on page 330 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 331 and “Setting quiesce points” on page 331 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 329 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 334 describes SMF records generated by zBoost PAV Optimizer.

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.



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 “ResourcePak Base initialization parameters” on page 36“.

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

Getting started 325


• 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



Optimizing I/Os


Table 26 lists general zBoost PAV Optimizer operations.

Table 28 lists zBoost PAV Optimizer logging and messaging operations.

Table 26 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 27 Logging and messaging

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

Optimizing I/Os 327


Table 28 lists zBoost PAV Optimizer operations for defining the scope of optimization.

Table 29 lists zBoost PAV Optimizer operations for controlling resource utilization.

Table 28 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 29 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



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 in “SCF.DEV.OPTIMIZE.PAV” on page 59.

◆ 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 in “SCF.DEV.OPTIMIZE.PAV” on page 59.

◆ 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 in “SCF.DEV.OPTIMIZE.PAV” on page 59.

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 in “SCF.DEV.OPTIMIZE.PAV.INCLUDE.LIST” on page 60

◆ Specific volsers with the SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST parameter described in “SCF.DEV.OPTIMIZE.PAV.VOLSER.INCLUDE.LIST” on page 67

◆ Volsers by mask with the SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST parameter described in “SCF.DEV.OPTIMIZE.PAV.VOLMASK.INCLUDE.LIST” on page 66

◆ Volsers by SMS storage group with the SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST parameter described in “SCF.DEV.OPTIMIZE.PAV.STORGRP.INCLUDE.LIST” on page 65

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 in “SCF.DEV.INCLUDE.LIST” on page 57.

To eliminate specific devices, specify the CUUs of the devices to be excluded using the SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST parameter described in “SCF.DEV.OPTIMIZE.PAV.EXCLUDE.LIST” on page 60.

Optimizing I/Os 329


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

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 in “SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST” on page 61 or SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST parameter described in “SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST” on page 61.

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 “SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST” on page 61 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 350) 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 in “SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.READ” on page 66 for read operations and the SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE parameter described in “SCF.DEV.OPTIMIZE.PAV.TRACK.MIN.WRITE” on page 66 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 in “SCF.DEV.OPTIMIZE.PAV.TRACK.MIN” on page 65.



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 in “SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.READ” on page 64 for read operations and the SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE parameter described in “SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX.WRITE” on page 64 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 in “SCF.DEV.OPTIMIZE.PAV.SPLIT.MAX” on page 63.

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.

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 in “SCF.DEV.OPTIMIZE.PAV.QUIPOINT.GLOBAL” on page 62.

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

Optimizing I/Os 331


To set the LCU quiesce point, use the SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU parameter described in “SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU” on page 62.

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 in “SCF.DEV.OPTIMIZE.PAV.QUIPOINT.LCU.PCT” on page 63.

◆ 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 in “SCF.DEV.OPTIMIZE.PAV.QUIPOINT.DEVICE” on page 61.

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 348. 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 PAV Optimizer to suspend and resume write I/O splitting include:

◆ SRDF/A MSC

Use the SCF.MSC.PAVO initialization parameter described in “SCF.MSC.PAVO” on page 89 to enable zBoost PAV Optimizer support for MSC environment.

◆ ConGroup

Use the PAVO configuration parameter of ConGroup described in the Consistency Groups for z/OS Product Guide 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

Such integration is provided through the use of attention interrupts and automatically initiated by participating applications.

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 in “DEV,OPTIMIZE SUSPEND” on page 353 and “DEV,OPTIMIZE RESUME” on page 352). A manual suspend will affect all LPARs with active Symmetrix Control Facility (SCF) environments and will remain in effect until a RESUME command cancels it.

Optimizing I/Os 333


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 in “SCF.DEV.OPTIMIZE.SMF.RECID” on page 68.

With the SMF reporting utility described in “SMF reporting utility” on page 343, 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 in “SCF.DEV.OPTIMIZE.PAV.JOBNAME.LIST” on page 61 or the SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST parameter described in “SCF.DEV.OPTIMIZE.PAV.JOBPREFIX.LIST” on page 61.

◆ 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 in “DEV,OPTIMIZE RESET” on page 351 also causes the same set of SMF records to be written immediately before the statistics are reset.



SMF record format

STATS recordThe SMF record consists of a standard SMF header followed 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

SMF recording 335


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 * * 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 30 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.

SMF recording 337


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.

SRXHCPS_FCX_PAVO_MAX_SPLIT_R_ 4 8 MAXSPL_R Maximum number of optimized splits for READs.0 = no maximum count.

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 30 Section 1 — zHPF PAV optimization parameters

Table 31 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 31 Section 2 — Basic monitoring zHPF counts

Table 32 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

SMF recording 339


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 32 Section 3 — PAV optimization passive zHPF counters

Table 33 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

SRXHCPS_FCX_PAVO_NORMAL 8 106 NORMAL Count of optimized CPs completed normally

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 IO 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 33 Section 4 — PAV optimization active monitoring zHPF counters

Table 34 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.

SMF recording 341


Table 35 Section 6 — PAV optimization zHPF skip processing


SRXHCPS_FCX_PAVO_SKIP_IORQ 4 200 SKIP_IORQ Count of optimized CPs skipped due to IORQ build issue

SRXHCPS_FCX_PAVO_SKIP_IO64 4 201 SKIP_IO64 Count of optimized CPs skipped due to 64 bit resource shortage

SRXHCPS_FCX_PAVO_SKIP_TIDA_R 4 202 SKIP_TIDA_R Count of optimized CPs skipped due to TIDA resource shortage for Read

SRXHCPS_FCX_PAVO_SKIP_TIDA_W 4 203 SKIP_TIDA_W Count of optimized CPs skipped due to TIDA resource shortage for WRITE

SRXHCPS_FCX_PAVO_SKIP_COB 4 204 SKIP_COB Count of optimized CPs skipped due to COB area exhaustion

SRXHCPS_FCX_PAVO_SKIP_NS 8 205 SKIP_NS Count of optimized CPs skipped due to unsupported DCW command

SRXHCPS_FCX_PAVO_SKIP_NSR 8 206 SKIP_NSR Count of optimized CPs skipped due to unsupported READ

SRXHCPS_FCX_PAVO_SKIP_NSW 8 207 SKIP_NSW Count of optimized CPs skipped due to unsupported WRITE

SRXHCPS_FCX_PAVO_SKIP_ICR 8 208 SKIP_ICR Count of optimized CPs skipped due to READ parameters incompatible (complex READ)

SRXHCPS_FCX_PAVO_SKIP_ICW 8 209 SKIP_ICW Count of optimized CPs skipped due to WRITE parameters incompatible (complex WRITE)

SRXHCPS_FCX_PAVO_SKIP_ICG 8 210 SKIP_ICG Count of optimized CPs skipped due to parameters incompatible (complex generic)

SRXHCPS_FCX_PAVO_SKIP_STR 8 211 SKIP_STR Count of optimized CPs skipped due to single track READ

SRXHCPS_FCX_PAVO_SKIP_STW 8 212 SKIP_STW Count of optimized CPs skipped due to single track WRITE

Table 36 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



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.

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 346 describes the format of the utility output file.

Run the utility as shown in “Sample JCL” on page 343. You can filter data to be extracted to the .csv file using control statements listed in “Control statements” on page 344.

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

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)

Table 36 Section 7 — PAV optimization logging event stats

SMF recording 343


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 in “SCF.DEV.OPTIMIZE.SMF.RECID” on page 68.

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

STATS

Extracts and formats only STATS records of all the three subtypes (GLOBAL, SSID, DEVICE).

SMF recording 345


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 337 show correspondence between the .csv file column headings and SMF record fields.



Command reference

Syntax conventions


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


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.



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



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

DEV,OPTIMIZE DISPLAY SSID

Displays SSID-oriented zBoost PAV Optimizer statistics.

Syntax

F emcscf,DEV,OPTIMIZE Display SSID(cuu[-cuu])|ALLSUMMARY|EVENTS

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.

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

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.

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.

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

ExampleF emcscf,DEV,OPTIMIZE RESUME

SCF4381I OPTIMIZE RESUME: RESUME initiated through 12 controllers: 0001926-01076 (8590) 0001926-04123 (8A02) 0001926-04124 (2D00) 0001949-01172 (5100) 0001957-00080 (3C01) 0001957-00086 (1E04) 0001967-01130 (6200) 0001967-01170 (AA00) 0001967-01175 (6500) 0001967-01305 (3801) 0001971-00060 (2300) 0001971-00061 (2500) PAV Optimizer processing is currently resumed at 09/25/15 15:12:25 Type Status Suspend Last Suspend Last Resume Counter DD/MM/YY HH:MM:SS DD/MM/YY HH:MM:SS-------- --------- ------- ----------------- -----------------ConGroup Resumed 0 09/25/15 15:04:30 09/25/15 15:04:46MSC Resumed 0 09/25/15 15:11:31 09/25/15 15:11:32ECATF -- Never suspended -- Operator Resumed 0 09/25/15 15:05:30 09/25/15 15:12:25ECASnap Resumed 0 09/25/15 15:05:11 09/25/15 15:05:15



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 12 controllers: 0001926-01076 (8590) 0001926-04123 (8A02) 0001926-04124 (2D00) 0001949-01172 (5100) 0001957-00080 (3C01) 0001957-00086 (1E04) 0001967-01130 (6200) 0001967-01170 (AA00) 0001967-01175 (6500) 0001967-01305 (3801) 0001971-00060 (2300) 0001971-00061 (2500) PAV Optimizer processing is currently suspended at 09/25/15 15:05:25 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 09/25/15 15:04:30 09/25/15 15:04:46 MSC Resumed 0 09/25/15 15:05:21 09/25/15 15:05:22 ECATF -- Never suspended -- Operator Suspended 1 09/25/15 15:05:25 09/25/15 14:36:19 ECASnap Resumed 0 09/25/15 15:05:11 09/25/15 15:05:15


CHAPTER 11Monitoring Track Changes (ChangeTracker)


◆ Introduction.......................................................................................................... 356◆ Getting started...................................................................................................... 357◆ Tracking changes with ChangeTracker Collector ..................................................... 373◆ Producing reports with ChangeTracker Reporter..................................................... 378◆ Command reference .............................................................................................. 388

Monitoring Track Changes (ChangeTracker) 355

Monitoring Track Changes (ChangeTracker)

IntroductionThe ChangeTracker utility allows you to monitor activity on VMAX 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 resynchronization times. You can use track changes to help you set the time needed for various synchronizing and resynchronizing activities.

ChangeTracker consists of two components:

◆ ChangeTracker Collector gathers statistics.

◆ ChangeTracker Reporter analyzes the data and formats it into useful reports. In addition, ChangeTracker Reporter can assist you in configuring your SRDF environment by calculating one of the three calculated parameters: number of remote adapters, communication speed, and resynchronization time, based on the values of the other two parameters.



Getting started

Prerequisites◆ The z/OS load library of ChangeTracker Collector must be an APF-authorized dataset.

◆ Estimate the available space to store collected information on changed tracks as described in “Storage estimates for ChangeTracker Collector disk output” on page 377.

Running ChangeTracker CollectorChangeTracker Collector runs as a started task or a long-running batch job.

The program name is CTRKCOLL. Refer to “ChangeTracker Collector sample JCL” on page 357 for a sample of ChangeTracker Collector JCL. “ChangeTracker Collector configuration parameters” on page 358 provides description of relevant parameters.

ChangeTracker Collector sample JCLThe following is an example of JCL for ChangeTracker Collector.

Note: Refer to the ResourcePak Base SAMPLIB(EMCCTR1) member included with your kit for the latest sample.

// jobcard //CTRKCOLL EXEC PGM=CTRKCOLL //STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB //CTRKLOG DD DISP=(NEW,CATLG,DELETE),DSN=ds_prefix.CTRKLOG, // SPACE=(CYL,(5,2)),UNIT=SYSDA //SCF$nnnn DD DUMMY //CONFIG DD *

configuration_parameters

//

Where:



◆ SCF$nnnn identifies the SCF subsystem used for Change Tracker.

◆ configuration_parameters are described in “ChangeTracker Collector configuration parameters” on page 358.

CTRKLOG DD statementThe optional CTRKLOG DD statement specifies the ChangeTracker Collector log dataset.

Note: “User-defined log dataset” on page 376 discusses requirements to the user-defined log dataset.

When CTRKLOG DD is specified, the HLQ, PALLOC, SALLOC, VOLUME|VOLSER parameters ignored.

Getting started 357


ChangeTracker Collector configuration parameters

ChangeTracker Collector configuration parameters are read from the CONFIG DD statement. The configuration parameters are in the following format:

keyword=value

◆ The keyword must begin in column 1.

◆ An asterisk in column 1 denotes a comment line.

Save the configuration parameter statements as a member of the parameter library which is referenced by the CONFIG DD statement of the ChangeTracker started task JCL.

CYCLE Determines how often ChangeTracker Collector collects data.

Recommended cycle times range from 3 to 10 minutes.

The maximum cycle time is 2 hours. Cycle times shorter than 1 minute are not recommended for multiple devices over extended periods of time. A cycle time of 0 results in 30 second cycles for compatibility with prior versions of ChangeTracker.


CYCLE=nn[{,SEC|,MIN|,HR}]

Where:

nn

The count of units of time that determines the period for data collection.

,SEC|,MIN|,HR

Identifies the unit of time:

• SEC for seconds

• MIN for minutes

• HR for hours

The default value is MIN (minutes). If you do not specify a value, the unit of time defaults to minutes.

For example:

To specify a cycle time of: Type:

10 minutes CYCLE=10

1 hour CYCLE=1,HR

90 seconds CYCLE=90,SEC



DEVICE_LIST Identifies devices from which to collect statistics.

You can specify one or more DEVICE_LIST statements. You can mix device numbers and volsers in the same statement.

Note: If you use asterisk (*) as the wildcard character in the DEVICE_LIST statement, all characters after the asterisk up to the next comma are ignored.


DEVICE_LIST=cuu_list|volser_list

DEVICE_LIST=LCL(gatekeeper,symdv#_range)

DEVICE_LIST=RMT(gatekeeper,symdv#_range[,hoplist])

DEVICE_LIST=RDFGRP(gatekeeper,srdfgrp)

Where:

cuu_list

List of devices identified by their z/OS device numbers. This can be a single value, a comma-separated list, or a range specified with a hyphen.

gatekeeper

The gatekeeper device identified with its CUU.

hoplist



nn.nn.nn.nn

If you do not specify hoplist, the default path for the specified gatekeeper is located and printed in the system log.

LCL


RDFGRP

Selects all devices on the VMAX system addressed via the gatekeeper CCUU which belongs to the assigned SRDF group.

RMT


srdfgrp

The SRDF group number on the VMAX system.

The SRDF group number can be represented by a one- or two-digit value. Hop list is not supported.

symdv#_range

Range of devices identified by their VMAX device numbers. This can be a single value or a range specified with a hyphen.

Getting started 359


volser_list

List of volumes identified by their volsers. This can be a single value or a comma-separated list. You can also specify a volser mask using the asterisk (*) as the wildcard character.

For example:

DEVICE_LIST=200-27F,290,B000-B007DEVICE_LIST=900,901,90A,DB2001,DB2002DEVICE_LIST=EMC*DEVICE_LIST=X*,QW*,EMC*,ABCO*,CDE01*DEVICE_LIST=200,300-310,EMC001,QWS*,APX9*DEVICE_LIST=RMT(3024,4B7)DEVICE_LIST=RMT(1EF0,0300-03FF,00.07.04)

HLQ The first qualifier for the automatically allocated ChangeTracker Collector log dataset.

Note: “ChangeTracker Collector log dataset” on page 376 describes the ChangeTracker Collector log dataset.

If the CTRKLOG DD statement is specified in the ChangeTracker Collector JCL, the HLQ parameter is ignored.

LOG#|LOGNUM Sets the starting dataset sequence number to be used when constructing a dataset name for the ChangeTracker Collector log dataset.


Each subsequent allocation of a new ChangeTracker Collector log dataset increases the sequence number by one.

Valid values are from 1 to 9999. If you do not specify LOG#|LOGNUM, ChangeTracker uses a default value of 1.

MAXCYCLE (Optional) Determines the number of cycles after which the ChangeTracker Collector job is automatically completed. For example, MAXCYCLE=72 specifies that the ChangeTracker Collector job should be completed after 72 cycles.

MODE Determines the type of operations analyzed by ChangeTracker Collector.

Note that a device can only be analyzed by one instance of ChangeTracker Collector at a time.

Valid values are:

◆ WRITE or W — For write operations. This is the default setting.

◆ READ or R — For read operations.

◆ READ/WRITE or RW — For read and write operations. In the read/write mode, read and write operations cannot be analyzed separately.

◆ READ_MISS or RM — For read-miss operations.

Note: Enginuity 5876 or HYPERMAX OS 5977 is required for using the MODE parameter. For Enginuity 5773, the WRITE mode is used.

Note: MODE=RW/R/RM is supported for CKD devices only.



PALLOC Sets the number of cylinders for primary space allocation of the aotumatically allocated ChangeTracker Collector log dataset.


If you do not specify the PALLOC parameter, ChangeTracker uses a default value of 20.

If the CTRKLOG DD statement is specified in the ChangeTracker Collector JCL, the PALLOC parameter is ignored.

SALLOC Sets the number of cylinders for secondary space allocation of the automatically allocated ChangeTracker Collector log dataset.


If you do not specify the SALLOC parameter, ChangeTracker uses a default value of 10.

If the CTRKLOG DD statement is specified in the ChangeTracker Collector JCL, the SALLOC parameter is ignored.

SCFG Identifies the GNS group from which you want to collect statistics.

Note: “Managing Device Groups (GNS)” on page 233 describes GNS groups.

When the SCFG parameter is specified, statistics is collected from all devices belonging to the specified GNS group.


SCFG(gnsgrp)

Where:

gnsgrp

The name of the GNS group.

Each GNS group name can be from 1 to 65 alphanumeric characters long. Each apostrophe, if used, reduces the maximum possible length of gnsgrp by 1.

Enclose the name in apostrophes if it includes any character that is neither an uppercase letter nor a numeric digit. If a GNS group name you use includes blank spaces, enclose it in double quotes:

SCFG("West Coast Stores")

However, be aware that even if the GNS group name is enclosed in apostrophes, non-alphanumeric characters or lowercase alphabetic characters may be translated to blanks or converted to uppercase when presented as input to ChangeTracker, possibly causing the GNS group not to be found or possibly resulting in processing of an unintended GNS group.

SMS_GROUP Identifies the SMS group from which you want to collect statistics.

When the SMS_GROUP parameter is specified, statistics is collected from all devices belonging to the specified SMS group.

Getting started 361


TOLERATE_ERRORS Sets ChangeTracker Collector behavior for devices that were skipped (for some reasons) when processing ChangeTracker Collector device selection parameters (DEVICE_LIST, SCFG, and SMS_GROUP). If skipping of a device is tolerated, normal processing continues. Otherwise, ChangeTracker Collector completes with return code 8.

Valid values are:

◆ ALL — Tolerate skipping of any devices specified in the DEVICE_LIST, SCFG, or SMS_GROUP parameter.

◆ [NO]CUU — Whether to tolerate skipping of devices listed with their CUUs in the DEVICE_LIST parameter: CUU — tolerate, NOCUU — do not tolerate.

◆ [NO]LCL — Whether to tolerate skipping of devices selected using the LCL keyword in the DEVICE_LIST parameter: LCL — tolerate, NOLCL — do not tolerate.

◆ NONE — Do not tolerate skipping of devices specified in the DEVICE_LIST, SCFG, or SMS_GROUP parameter.

◆ [NO]RDFG — Whether to tolerate skipping of devices selected using the RDFGRP keyword in the DEVICE_LIST parameter: RDFG — tolerate, NORDFG — do not tolerate.

◆ [NO]RMT — Whether to tolerate skipping of devices selected using the RMT keyword in the DEVICE_LIST parameter: RMT — tolerate, NORMT — do not tolerate.

◆ [NO]SCFG — Whether to tolerate skipping of devices selected using the SCFG parameter: SCFG — tolerate, NOSCFG — do not tolerate.

◆ [NO]SMSG — Whether to tolerate skipping of devices selected using the SMS_GROUP parameter: SMSG — tolerate, NOSMSG — do not tolerate.

◆ [NO]VOLSER — Whether to tolerate skipping of devices selected with volsers specified in the DEVICE_LIST parameter: VOLSER — tolerate, NOVOLSER — do not tolerate.

The default setting is TOLERATE_ERRORS=ALL,NOVOLSER,NOSMSG (tolerate all skipped devices except those specified using volsers in the DEVICE_LIST parameter and using an SMS group in the SMS_GROUP parameter).

The TOLERATE_ERRORS parameter can be specified multiple times, with every next statement redefining any previously specified or defaulted values.

For example:

◆ To tolerate skipping of devices specified with their CUUs or volsers in the DEVICE_LIST parameter:

TOLERATE_ERRORS=NONE,VOLSER,CUU

◆ To tolerate any skipped devices except those selected using volsers in the DEVICE_LIST parameter:

TOLERATE_ERRORS=ALL,NOVOLSER

◆ To tolerate skipping of devices selected using the RDFGRP keyword in the DEVICE_LIST parameter:

TOLERATE_ERRORS=NONE,RDFG



VOLSER|VOLUME Identifies the volser where the ChangeTracker Collector log dataset is automatically allocated.


If the CTRKLOG DD statement is specified in the ChangeTracker Collector JCL, the VOLSER|VOLUME parameter is ignored.

VTOC Determines when (if at all) to dump the VTOC to the ChangeTracker Collector log dataset.

Note: “Dumping VTOCs” on page 377 describes dumping the VTOC to the ChangeTracker Collector log dataset.

Valid values are:

◆ START — Dump the VTOC at ChangeTracker Collector startup.

◆ STOP — Dump the VTOC at ChangeTracker Collector shutdown.

◆ BOTH — Dump the VTOC at startup and shutdown. This is the default value.

◆ NONE — Do not dump the VTOC during this ChangeTracker Collector run.

◆ ONLY — Dump the VTOC to the ChangeTracker Collector log dataset and terminate.

Getting started 363


ChangeTracker Collector sample CONFIG file

The following is a sample CONFIG file of ChangeTracker Collector:

DEVICE_LIST=100-11F,8800-88FFDEVICE_LIST=PLO1*,900,910CYCLE=10HLQ=TRVWMODE=WPALLOC=50SALLOC=20VOLSER=EMC200

This CONFIG file specifies the following:

◆ ChangeTracker Collector collects data from all the specified devices every 10 minutes.

◆ The first dataset to be allocated has the name of TRVW.CHGTRKER.D2014001.LOG#0001, assuming that ChangeTracker Collector starts running on January 1, 2014.

◆ The dataset is allocated on volser EMC200.

◆ The dataset has primary allocation of 50 cylinders and secondary allocation of 20 cylinders.

Running ChangeTracker Reporter

ChangeTracker Reporter runs as a batch job.

The program name is CTRKREPT. Refer to “ChangeTracker Reporter sample JCL” on page 365 for a sample of ChangeTracker Reporter JCL. “ChangeTracker Reporter configuration parameters” on page 366 provides description of relevant parameters.



ChangeTracker Reporter sample JCL

The following is an example of JCL for ChangeTracker Reporter.

Note: Refer to the ResourcePak Base SAMPLIB(EMCCTR2) member included with your kit for the latest sample.

// jobcard //CTRKREPT EXEC PGM=CTRKREPT //STEPLIB DD DSN=ds_prefix.LINKLIB,DISP=SHR //ISTATS DD DISP=disp,DSN=interval_statistics_file//SYSUDUMP DD SYSOUT=* //SORTIN DD DISP=SHR,DSN=log_dataset//SORTOUT DD DSN=&&SORTWK,DISP=(,PASS), // UNIT=SYSDA,SPACE=(CYL,(50,10)) //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //CONFIG DD *

configuration_parameters

//

Where:


◆ log_dataset is the name of the ChangeTracker Collector log dataset described in “ChangeTracker Collector log dataset” on page 376.


◆ interval_statistics_file is the name of the interval statistics file described in “Interval statistics file” on page 386. This is a variable-length file with LRECL=256,RECFM=VB.

◆ configuration_parameters are described in “ChangeTracker Reporter configuration parameters” on page 366.

Getting started 365


ChangeTracker Reporter configuration parameters

ChangeTracker Reporter configuration parameters are 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.

Save the configuration parameter statements as a member of the parameter library which is referenced by the CONFIG DD statement of the ChangeTracker started task JCL.

DATE Determines the date or dates to include statistics in the reports.

Note: Use the DATE parameter together with the TOD parameter to identify exact time periods for your reports.


DATE=(mmddyyyy1,mmddyyyy2)

DATE=(mmddyyyy1-mmddyyyy2)

Where:

mmddyyyy1

The starting day of the period to include statistics.

When specified without mmddyyyy2, data on that day only is included in the reports.

mmddyyyy2

The ending day of the period to include statistics.



DEVICE_LIST Identifies devices for which to include statistics in the reports.

You can specify one or more DEVICE_LIST statements. You can mix device numbers and volsers in the same statement.

Note: Specifying DEVICE_LIST together with the SYM_SERIAL parameter results in an error message.

Note: If you use asterisk (*) as the wildcard character in the DEVICE_LIST statement, all characters after the asterisk up to the next comma are ignored.


DEVICE_LIST=cuu_list|volser_listDEVICE_LIST=LCL(gatekeeper,symdv#_range)

DEVICE_LIST=RMT(gatekeeper,symdv#_range[,hoplist])DEVICE_LIST=RDFGRP(gatekeeper,srdfgrp)

Where:

cuu_list

List of devices identified by their z/OS device numbers. This can be a single value, a comma-separated list, or a range specified with a hyphen.

gatekeeper


hoplist



nn.nn.nn.nn

If you do not specify hoplist, the default path for the specified gatekeeper is located and printed in the system log.

LCL


RDFGRP

Selects (from the ChangeTracker Collector log dataset) all devices collected with RDFGRP() or LCL() parameter with assigned gatekeeper CCUU which (devices) belong to the assigned SRDF group.

RMT


Getting started 367


srdfgrp

The SRDF group number on the VMAX system.

The SRDF group number can be represented by a one- or two-digit value. Hop list is not supported.

symdv#_range

Range of devices identified by their VMAX device numbers. This can be a single value or a range specified with a hyphen.

volser_list

List of volumes identified by their volsers. This can be a single value or a comma-separated list. You can also specify a volser mask using the asterisk (*) as the wildcard character.

For example:

DEVICE_LIST=900,901,90A,DB2001,DB2002DEVICE_LIST=X*,QW*,EMC*,ABCO*,CDE01*DEVICE_LIST=200,300-310,EMC001,QWS*,APX9*DEVICE_LIST=RMT(3024,4B7)

- Collects statistics on device 4B7 on the remote system. Channel programs access CUU=3024 on the local system to find the default SRDF group.

DEVICE_LIST=RMT(1EF0,0300-03FF,00.07.04)

- Uses VMAX system at CUU 1EF0 to gain access to devices 0300-03FF on the remote system.

INTERVAL Specifies the interval to be used for interval statistics.

Note: “Interval statistics file” on page 386 describes interval statistics.

The INTERVAL value must be a multiple of the CYCLE parameter value described in “CYCLE” on page 358, which is used by ChangeTracker Collector. Otherwise, the interval statistics may be skewed. For example, if you specify CYCLE=40 and INTERVAL=60, some intervals would have two cycles and some intervals would only have one cycle. Recommended interval times are 1, 2, 4, or 8 hours.

Any INTERVAL values less than 60 seconds are reset to 1 hour.


INTERVAL=nn[{,SEC|,MIN|,HR}]

Where:

nn

Sets the interval for interval statistics. If not specified, INTERVAL defaults to 60 minutes.



,SEC|,MIN|,HR

Identifies the unit of time:

• SEC for seconds

• MIN for minutes

• HR for hours

The default value is MIN (minutes). If you do not specify a value, the unit of time defaults to minutes.

For example:

MODE This legacy parameter is tolerated but ignored.

RA_COUNT Indicates the number of Remote Adapters (RA) on the VMAX system.

This value can be specified manually using the RA_COUNT keyword or calculated (and shown in the resulting reports) based on the RA_KBS and RESYNCH_TIME parameter values.

RA_KBS Indicates 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.

This value can be specified manually using the RA_KBS keyword or calculated (and shown in the resulting reports) based on the RA_COUNT and RESYNCH_TIME parameter values.

REPORTS Determines the type of report to be generated.

You can specify any combination of the available options separated by commas:

◆ SYMMETRIX — Produces the Symmetrix Summary report described in “Symmetrix Summary report” on page 381.

◆ VOLUME — Produces the Volume Summary report described in “Volume Summary report” on page 383.

◆ DATASET — Produces the Dataset Summary report described in “Dataset Summary report” on page 385.

Note: The Dataset Summary report requires VTOC information which must be dumped with the VTOC parameter of ChangeTracker Collector, as described in “VTOC” on page 363.

◆ SKIP_ZERO — Bypasses printing lines that do not have any accessed tracks in the dataset and volume reports.

For example:

REPORTS=DATASET,SKIP_ZERO,SYMMETRIX

To specify a cycle time of: Type:

30 minutes INTERVAL=30

2 hours INTERVAL=2,HR

Getting started 369


RESYNCH_TIME Indicates the time required for the devices to resynchronize after an outage.

This value can be specified manually using the RESYNCH_TIME keyword or calculated (and shown in the resulting reports) based on the RA_COUNT and RA_KBS parameter values.


RESYNCH_TIME=hh:mm

RESYNCH_TIME=mmmm

SCFG Identifies the GNS group from which you want to report statistics.

Note: “Managing Device Groups (GNS)” on page 233 describes GNS groups.

When the SCFG parameter is specified, statistics is reported from all devices belonging to the specified GNS group.


SCFG(gnsgrp)

Where:

gnsgrp

The name of the GNS group.

Each GNS group name can be from 1 to 65 alphanumeric characters long. Each apostrophe, if used, reduces the maximum possible length of gnsgrp by 1.

Enclose the name in apostrophes if it includes any character that is neither an uppercase letter nor a numeric digit. If a GNS group name you use includes blank spaces, enclose it in double quotes:

SCFG("West Coast Stores")

However, be aware that even if the GNS group name is enclosed in apostrophes, non-alphanumeric characters or lowercase alphabetic characters may be translated to blanks or converted to uppercase when presented as input to ChangeTracker, possibly causing the GNS group not to be found or possibly resulting in processing of an unintended GNS group.

SMS_GROUP Identifies the SMS group for which to include statistics in the reports.

When the SMS_GROUP parameter is specified, statistics is included for all devices belonging to the specified SMS group.

Note: Specifying SMS_GROUP together with the SYM_SERIAL parameter results in an error.

SYM_SERIAL Identifies the VMAX system or systems for which to include statistics in the reports.

When the SYM_SERIAL parameter is specified, statistics is included for all devices in the specified VMAX systems.

SYM_SERIAL accepts a comma-separated list of 12-digit VMAX system serial numbers. Only one SYM_SERIAL statement is allowed.

Note: Specifying SYM_SERIAL together with the DEVICE_LIST or SMS_GROUP parameters results in an error message.



For example:

SYM_SERIAL=001122334455,554433221100

TOD Determines the time of day for which to include statistics in the reports.

Note: Use the TOD parameter together with the DATE parameter to identify exact time periods for your reports.

You can set an interval to be applied on each of the selected dates (a daily period), or define the whole period covering all selected dates with the specified start time on the first date and end time on the last date.


TOD=(hhmm1,hhmm2)

TOD=(hhmm1-hhmm2)

TOD=(hhmm3,hhmm4),BOTH

TOD=(hhmm3-hhmm4),BOTH

Where:

hhmm1

The start time of the daily period to include. Statistics is included starting from this time on each of the dates specified using the DATE parameter.

hhmm2

The end time of the daily period to include. Statistics is included up to this time on each of the dates specified using the DATE parameter.

hhmm3

The start time of the whole period to include. Statistics is included starting from this time on the first of the dates specified using the DATE parameter.

hhmm4

The end time of the whole period to include. Statistics is included up to this time on the last of the dates specified using the DATE parameter.

BOTH

ChangeTracker Reporter only selects records if both DATE and TOD conditions are satisfied.

In the following example, all records between from 2-Feb-2014 10:00 till 7-Feb-2014 14:00 are selected:

DATE=(02022014,02072014)TOD=(1000,1400),BOTH

If the BOTH option was not specified, records written from 2-Feb-2014 till 7-Feb-2014 within the period from 10:00 till 14:00 on each day are selected:

DATE=(02022014,02072014)TOD=(1000,1400)

Getting started 371


ZDP (Optional) Enables or disables additional processing required for Data Protector for z Systems (zDP).


ZDP=Y

When ZDP is set to Y, the following additional processing occurs:

◆ Summary records $FBA$$ and $CKD$$ are added to the interval statistics file.

◆ The following ChangeTracker parameter values are used: RA_COUNT=1, RESYNCH_TIME=10, and RA_KBS=0. Any other values of these parameters are ignored.

When the ZDP parameter is not specified or set to any value other than “Y”, the additional processing is disabled (default).



Tracking changes with ChangeTracker Collector

Overview

ChangeTracker Collector gathers information about track changes from VMAX devices. ChangeTracker Collector runs over a period of time, gathering data at specified intervals, and determines which tracks on the specified devices have been accessed.

To run, ChangeTracker Collector requires the following information:

◆ The devices for which to collect data

◆ The data collection mode

◆ How often to collect the data

◆ Where to write the collected data

Under Enginuity 5876 and HYPERMAX OS 5977, ChangeTracker Collector uses the following data collection modes:

◆ Write mode (default) — Collects all write updates to the device.

◆ Read mode — Collects read operations.

◆ Read/write mode — Collects both read and write operations.

◆ Read-miss mode — Collects reads that are not from cache.

You can select the required mode using the MODE parameter of ChangeTracker Collector, as described in “MODE” on page 369.

Under Enginuity 5773, ChangeTracker Collector collects write operations only.

ChangeTracker Collector works using VMAX-specific features. It gathers information about accessed tracks internally by the VMAX system, using VMAX 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 supports EAV devices (up to 1182006 cylinders in size), provided that the mainframe operating system supports them.

A device can only be collected by one instance of ChangeTracker Collector at a time.

Note: Any action that swaps logical devices invalidates the relationship of the logical address and the VMAX device number. This results in messages CTRK011E and CTRK012E. When diagnosing this error, determine if a swap was performed on the CUU indicated in the messages.

Tracking changes with ChangeTracker Collector 373


Setting up change track collection

Table 37 lists operations for setting up the track change collection process.

Selecting devices to track changes

Table 38 lists operations for selecting devices to track changes.

Setting up ChangeTracker Collector log dataset

Table 39 lists operations for setting up the ChangeTracker Collector log dataset.

Table 37 Setting up track change collection

Operation Control

Determine type of operations to be collected MODE configuration parameter

Determine how often ChangeTracker Collector collects data CYCLE configuration parameter

Determine number of cycles to automatically complete ChangeTracker Collector job

MAXCYCLE configuration parameter

Determine whether and when to dump VTOC VTOC configuration parameter

View all ChangeTracker settings DISPLAY ALL command

View current cycle DISPLAY CYCLE command

View help on ChangeTracker Collector commands HELP command

Terminate ChangeTracker Collector STOP command

Table 38 Selecting devices to track changes

Operation Control

Specify devices to track changes DEVICE_LIST configuration parameter

Specify SMS group to track changes SMS_GROUP configuration parameter

Specify GNS group to track changes SCFG configuration parameter

View devices for which information is being collected DISPLAY DEVICE command

Set behavior for skipping of devices during device selection TOLERATE_ERRORS configuration parameter

Table 39 Setting up ChangeTracker Collector log dataset

Operation Control

View name of current ChangeTracker Collector log dataset DISPLAY LOG command

Start new ChangeTracker Collector log dataset LOGSWAP command

Set HLQ for ChangeTracker Collector log dataset HLQ configuration parameter

Set starting sequence number for ChangeTracker Collector log dataset LOG#|LOGNUM configuration parameter

Reset sequence number of ChangeTracker Collector log dataset LOG# command

Determine the volume to allocate ChangeTracker Collector log dataset VOLSER|VOLUME configuration parameterVOLSER command



Determine primary space allocation for ChangeTracker Collector log dataset

PALLOC configuration parameter

Determine secondary space allocation for ChangeTracker Collector log dataset

SALLOC configuration parameter

Write to user-defined log dataset CTRKLOG DD statement

Table 39 Setting up ChangeTracker Collector log dataset

Operation Control



ChangeTracker Collector log dataset

ChangeTracker Collector writes the collected data to the log dataset for later use by the ChangeTracker Reporter. The collected data shows which tracks were accessed during the interval since the last collection.

ChangeTracker allocates the log dataset automatically or uses the user-defined dataset specified with the CTRKLOG DD statement described in “CTRKLOG DD statement” on page 357.

Automatic log datasetThe name of the automatically allocated ChangeTracker Collector log dataset is in the following format:

hlq.CHGTRKER.Dyyyyddd.LOG#nnnn

Where:

hlq

The high-level qualifier under which the log dataset is stored. You can set the HLQ using the HLQ parameter of ChangeTracker Collector, as described in “HLQ” on page 360.

yyyyddd

The Julian date with a four-digit year.

nnnn

A sequence number. You can set the sequence number using the LOG#|LOGNUM parameter or the LOG# command of ChangeTracker Collector, as described in “LOG#|LOGNUM” on page 360 and “LOG#” on page 390, accordingly.

Each time you close one log dataset and open another, ChangeTracker increments the sequence number by one.

User-defined log datasetThe log dataset specified in the CTRKLOG DD statement must be allocated before ChangeTracker Collector runs.

The log dataset characteristics are as follows:

◆ Physical sequential organization

◆ Variable blocked record format

◆ Record length 27994

◆ Block size 27998

Note: When CTRKLOG DD is specified, the HLQ, PALLOC, SALLOC, VOLUME|VOLSER parameters ignored.



Dumping VTOCs

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

ChangeTracker Collector does not collect VTOC information for any offline, remote, or devices that are only identified by local or remote VMAX device numbers (using the LCL(gatekeeper, symdv#) and RMT(gatekeeper, symdv#) syntax pattern). In such cases, no dataset-level reports are available.

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 depends on the number of tracks that were modified 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 can calculate the necessary storage as follows:

Storage = 250 * device_count * minutes / cycle_time

For example, if data were to be collected for 64 devices during 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).



Producing reports with ChangeTracker Reporter

Overview

After ChangeTracker Collector has finished gathering statistics for the devices, you can use ChangeTracker Reporter to analyze the statistics and produce reports showing track usage at different levels.

ChangeTracker Reporter presents the collected information in a meaningful format. ChangeTracker Reporter can generate reports showing track access operations over a period of time at the following levels:

◆ The VMAX system level

◆ The volume level

◆ The dataset level

You may find this information useful for making decisions regarding system configuration data throughput.

The required types of reports and parameters used for the reports are specified through ChangeTracker Reporter parameters read from the CONFIG DD statement.

To run, ChangeTracker Reporter requires the following parameters:

◆ Device parameters

If none of device parameters are present, ChangeTracker Reporter uses all information collected by ChangeTracker Collector.

Any parameters values you specify are reflected in the echo of the control statements at the beginning of a report.

◆ Time and calculation parameters

◆ Report specification parameters

Note: “ChangeTracker Reporter configuration parameters” on page 366 describes ChangeTracker Reporter parameters.

The following reports are available:

◆ Collector Summary report

◆ Reporter Summary report

◆ Symmetrix Summary report

◆ Volume Summary report

◆ Dataset Summary report

The Collector Summary report and the Reporter Summary report are always produced. For the remaining three reports, you specify the required report type using the REPORTS parameter of ChangeTracker Reporter, as described in “REPORTS” on page 369.

In addition, ChangeTracker Reporter can also produce the interval statistics file described in “Interval statistics file” on page 386.



Setting up reports

Table 40 lists operations for setting up reports produced by ChangeTracker Reporter.

Collector Summary report

The Collector Summary report describes data contained in the ChangeTracker Collector log dataset, including the time frame, number of cycles, and cycle time.

A sample Collector Summary report 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 SMS Group = SG6 SCF Group = GNSLV4

Report fieldsThe Collector Summary report contains the following fields:

◆ LPAR — The name of the LPAR on which ChangeTracker Collector ran.

◆ Start — The date and time the ChangeTracker Collector took the first sample.

◆ End — The date and time the ChangeTracker Collector took the last sample.

◆ Cycle Time — The time interval between samples.

◆ Number of Cycles — The selected number of samples filtered from the ChangeTracker Collector log dataset according to DATE and TOD parameters of ChangeTracker Reporter, as described in “DATE” on page 366 and “TOD” on page 371.

◆ SMS Group — The name of the SMS group that ChangeTracker Reporter can potentially extract from the ChangeTracker Collector log dataset.

◆ SCF Group — The name of GNS group that ChangeTracker Reporter can potentially extract from the ChangeTracker Collector log dataset.

Table 40 Setting up reports

Operation Control

Select type of report to be produced REPORTS configuration parameter

Determine the dates and time to include in the report DATE configuration parameterTOD configuration parameter

Determine VMAX system to include in report SYM_SERIAL configuration parameter

Determine SMS group to include in report SMS_GROUP configuration parameter

Determine GNS group to include in report SCFG configuration parameter

Determine devices to include in report DEVICE_LIST configuration parameter

Set interval for interval statistics INTERVAL configuration parameter

Whether to include summary records $FBA$$ and $CKD$$ in the interval statistics file

INTERVAL configuration parameter

Producing reports with ChangeTracker Reporter 379


Reporter Summary report

The Reporter Summary report shows the effective parameters of ChangeTracker Reporter.

For example, the ChangeTracker Collector log dataset may contain data for 200 devices over a 12-hour time period, but ChangeTracker Reporter can report on a subset of those devices over a shorter time period if desired.

The following is a sample Reporter Summary report:

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) zzzzzzzzzzzInterval=3 hours Date=(08022010,08312010) Time=(0600,1900)

Report fieldsThe Reporter Summary report contains the following fields:

◆ Report Date & Time — The time when ChangeTracker Reporter job ran.

◆ Parms — All the parameters currently in effect for the reports. Valid values are:

• Device List — The devices that were requested to be included in the reports.

• Symm Serial # — The VMAX system for which to generate reports. The report shows every VMAX system from which data was collected.

• RA Count — The number of Remote Adapters (RA).

• RA KBS — The speed of the telecommunications lines.

• Resynch Time — The resynchronization time.

• Collector Mode — The data collection mode. The default mode is Write (W). If the specified mode does not match the ChangeTracker Collector mode, a message is printed in the dataset.

• Reports — Displays the reports to be generated.

• Date — The dates for which to take samples from the ChangeTracker Collector log dataset. If no date was specified, all samples are used for the reports.

• Time — The time to take samples from the ChangeTracker Collector dataset. If no time was specified, all samples are used for the reports.



Symmetrix Summary reportThe Symmetrix Summary report shows the track usage for each VMAX system over the specified period of time.

To produce the report, use the SYMMETRIX option of the REPORTS parameter of ChangeTracker Reporter, as described in “REPORTS” on page 369.

Figure 2 shows an example:

12/05/2013 C h a n g e T r a c k e r S y m m e t r i x S u m m a r y 05:37:27 From: 12/05/2013 01:30 To: 12/05/2013 19:30 Mode= W Symmetrix Volume Total Per BndWth Sync Serial# Count Cylinders Tracks Cycle %Trks RA's (KBS) Time------------ ------ ---------- ---------- ------- ----- ---- ------ -----000192602204 3 3339 2003 69 3 2 1000 000:00There are 58 cycles included in this report

Figure 2 Symmetrix Summary report

Report fieldsThe Symmetrix Summary report contains the following fields:

◆ From and To — The dates and times specified using the DATE and TOD parameters of ChangeTracker Reporter, as described in “DATE” on page 366 and “TOD” on page 371. If no DATE and TOD statements are specified, ChangeTracker Reporter uses all dataset records created by ChangeTracker Collector and displays the start and end times of ChangeTracker Collector.

◆ Mode — The data collection mode set in ChangeTracker Collector.

◆ Symmetrix Serial# — The serial number of the system.

◆ Volume Count — The number of volumes included in this report that are part of the specified system.

◆ Total Cylinders — The total number of cylinders for the indicated volumes.

◆ Tracks — The number of tracks that have been accessed during the reporting period on the indicated volumes.

◆ Per Cycle — The average of the total number of tracks that have been accessed during the reporting period on the indicated volumes divided by the number of cycles.

◆ % Trks — The percentage of tracks that have been accessed during the reporting period on the indicated volumes.

The next three columns display either the specified value of the corresponding ChangeTracker Reporter parameter, or the value calculated automatically 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.

“Calculated parameters” on page 382 describes calculated parameters of ChangeTracker Reporter.

The last statement displays how many cycles were included in this report given the time frame specified.



Calculated parametersChangeTracker Reporter can help you configure your SRDF environment by calculating one of the three calculated parameters based on the values of the other two parameters.

The calculated parameters are RA_COUNT, RA_KBS, and RESYNCH_TIME, described in “RA_COUNT” on page 369, “RA_KBS” on page 369, and “RESYNCH_TIME” on page 370 correspondingly.

After you specify two of these parameters, ChangeTracker Reporter calculates the third parameter value and displays it in the Symmetrix Summary report.

Example Suppose a site has a business requirement mandating that resynchronization should take no more than two hours and a user wants to configure the SRDF environment to satisfy this 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. Based on this information, you can determine the time necessary for resynchronization.

R_KBS=1000RA_COUNT=2



Volume Summary report

The Volume Summary report takes the VMAX statistics and breaks them down to the volume level.

To produce a Dataset Summary report, use the VOLUME option of the REPORTS parameter of ChangeTracker Reporter, as described in “REPORTS” on page 369.

Figure 3 shows an example of the Volume Summary report.

04/04/2014 ChangeTracker Volume SummaryFrom: 03/24/2014 15:23 To: 03/24/2014 15:31 Mode= RW Symmetrix Per Serial# Volser Emul Cyls DSN's Tracks %Trks Cycle Mode------------ ------ ---- ------ ------ ------- ----- ------- ----000190300344 USK250 3390 3339 0 0 0 0 W 000192604123 UTC056 3390 1113 0 1 0 0 RW000195700080 VSUV21 3390 1113 1 2 0 0 RW000195700080 VSUV22 3390 1113 1 2 0 0 RW000196700256 F*0088 3390 1113 0 0 0 0 W 000196700256 F*0089 3390 1113 0 0 0 0 W There are 8 cycles included in this report

Figure 3 Volume Summary report

Report fieldsThe Volume Summary report contains the following fields:


◆ Mode — The data collection mode set in ChangeTracker Collector.

◆ Symmetrix Serial# — The serial number of the system.

Note: You can also find system serial numbers in the ChangeTracker Collector job log.

◆ Volser — The volser of the device being reported on.

• For offline volumes, where the volser cannot be determined, the volser is displayed as -Ccuuu (that is, -C followed by the two-byte hexadecimal CUUU address converted to printable characters).

• For remote VMAX devices, the volser is shown as -Ruuuu, where uuuu represents the hexadecimal unit number within the remote VMAX system.

• F* with a hexadecimal VMAX 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.

◆ DSN's — The number of datasets that had tracks accessed during the reporting time frame. If the DATASET keyword is not included in the REPORT parameter, as described in “REPORTS” on page 369, this value is 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 value 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.

◆ Mode — This optional column lists the actual data collection mode for each device, if ChangeTracker Collector has changed the mode for some devices (as indicated by the CRTK005I message).

The last statement displays how many cycles were included in this report given the time frame specified.



Dataset Summary report

The Dataset Summary report breaks each volume down to all its datasets and shows the number of changes to each dataset.

To produce a Dataset Summary report, use the DATASET option of the REPORTS parameter of ChangeTracker Reporter, as described in “REPORTS” on page 369.

Note: The Dataset Summary report requires VTOC information which must be dumped with the VTOC parameter of ChangeTracker Collector.

Figure 4 shows an example of the Dataset Summary report.

09/16/2013 ChangeTracker Dataset Summary (OTTCL1) 14:53:29From: 08/06/2013 10:21 To: 08/06/2013 10:25 MODE = W Create Dataset Name Date Cyls Exts Tracks %Trks Volser ---------------------------- ---------- ------ ---- ------- ----- ------ EMCTST.VVV2.INSTLIB 04/11/2013 3 1 31 68 OTTCL1 EMCTST.OSVVV8.LOADLIB 02/16/2013 264 1 264 6 OTTCL1 EMCTST.OSVVV8.CMDLOAD 02/16/2013 287 1 0 0 OTTCL1

Figure 4 Dataset Summary report

Report fieldsThe Dataset Summary report contains the following fields:

◆ The name of the volume is displayed in the report title.


◆ Mode — The actual data collection mode for the device.

◆ Dataset Name — The name of the dataset being reported. If a dataset has an asterisk (*) before its name, the dataset was created after ChangeTracker Collector ran.

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

◆ %Trks — The percentage of tracks on the dataset that were accessed during the reporting time frame.

The last statement displays how many cycles were included in this report during the time frame specified.



Interval statistics file

To help you better understand the track access frequency, ChangeTracker creates an interval statistics file to show the track access count, by intervals.

The name and characteristics of the interval statistics file are determined using the ISTATS DD name, as described in “ChangeTracker Reporter sample JCL” on page 365.

For each interval determined using the INTERVAL parameter (described in “INTERVAL” on page 368), ChangeTracker can display:

◆ Statistics for each volume or VMAX system

◆ Statistics summarized for all VMAX systems

By examining this information, you can visualize trends in track access rates. You can determine whether new tracks are being accessed or whether the same tracks are repeatedly accessed each interval.

Record fieldsTable 41 describes the fields in the interval statistics file.

Table 41 Interval statistics file fields (page 1 of 2)

Field Explanation

Symmetrix serial number This is a 12-character value. If this is a summary record of all systems, this field displays $ALL$ALL$ALL, and the volume field displays $ALL$$.

Volume serial number This is a six-character value. For records that are a summary of an entire VMAX system, the serial number is valid, but this field displays $ALL$. For devices that were offline when 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 means 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, the 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.

Two-interval track update number

The number of tracks accessed during the current and the previous interval. This field value is always equal to, or higher than the value in the “Track number” field.For example, if this field is 00000000006031 and the “Track number” field is 00000000004118, 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.



zDP-enabled formatWhen the ZDP configuration parameter of ChangeTracker Reporter is set to Y:

◆ The interval statistics file contains additional summary records $FBA$$ and $CKD$$. These records show the statistics separately for FBA and CKD devices.

◆ Two additional columns are appended to summary records ($FBA$$, $CKD$$, and $ALL$$):

• Number of devices — a 14-digit device counter, and

• Microcode level — a 4-digit field for HYPERMAX OS or Enginuity level.

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.

Number of devices The number of devices.

Note: This field is appended to summary records if the ZDP parameter of ChangeTracker Reporter is set to Y.

Microcode level The HYPERMAX OS or Enginuity level.

Note: This field is appended to summary records if the ZDP parameter of ChangeTracker Reporter is set to Y.

Table 41 Interval statistics file fields (page 2 of 2)

Field Explanation



Command referenceTo issue a ChangeTracker Collector command, use the z/OS MODIFY command (F) as follows:

F collector_task,command parameter 1 [,parameter 2 [,parameter n]]

Where:

◆ collector_task is the name of the ChangeTracker started task, for example, EMCCTRK.

◆ command is the ChangeTracker Collector command.

◆ parameter1..n are the parameters of the ChangeTracker Collector command.

Syntax conventions


DISPLAY ALL

Displays a summary listing of the ChangeTracker Collector attributes.

Syntax

DISplay ALL

ExampleDIS 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

DISPLAY CYCLE

Displays the current cycle time interval.

Syntax

DISplay CYCle

ExampleDIS CYCLECYCLE = 5 MIN, # CYCLES = 8, MODE = W



DISPLAY DEVICE

Displays devices specified for ChangeTracker Collector.

When issued without parameters, the command displays all the devices that ChangeTracker Collector is collecting data for. The display shows each device with its CUU and volser.

Syntax

DISplay DEVice [{cuu|volser}]

Parameters

cuu

The CUU of the device you want to display.

volser

The volser of the device you want to display.

ExamplesWithout device specification, ChangeTracker Collector displays a list of 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, the command produces the following output:

DIS DEV 233 CUU=0233 VOL=SYB033 #CYLS=1113 SYMMDEV#=00000033 SER#=000182600427 UCB @ 00F1A850 CTLR=3990-E9 DEVICE=3390-02

DISPLAY LOG

Displays the name of the current ChangeTracker Collector log dataset.

Syntax

DISplay LOG

ExampleDIS LOGLOG DSN=MFLYNN1.CHGTRKER.D1998364.LOG#0013



HELP

Displays help information.

SyntaxHELP

LOG#

Resets the sequence number for the ChangeTracker Collector log dataset.

The next ChangeTracker Collector log dataset gets allocated using the specified number n when constructing the dataset name.

Note: The next time a ChangeTracker Collector log dataset is allocated, either by the LOGSWAP command or otherwise, it has LOG#0200 as the last qualifier in the dataset name.

Syntax

LOG# n

LOGNum n

Parameters

n

The number you want to assign.

LOGSWAP

Closes the current ChangeTracker Collector log dataset and allocates a new one.

The new ChangeTracker Collector log dataset has 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.

SyntaxLOGSwap

STOP

Terminates the ChangeTracker Collector started task.

Note: You can also use the z/OS STOP (P) command to terminate the ChangeTracker Collector started task.

SyntaxSTOP



VOLSER

Changes the volume used to allocate the ChangeTracker Collector log dataset.

Syntax

VOLSER volser

Parameters

volser

The volume serial number.


CHAPTER 12Comparing Tracks (Disk Compare)


◆ Introduction.......................................................................................................... 394◆ Getting started...................................................................................................... 395◆ Comparing tracks .................................................................................................. 400

Comparing Tracks (Disk Compare) 393

Comparing Tracks (Disk Compare)

IntroductionThe Disk Compare utility compares tracks on pairs of logical disk volumes at the physical level. The utility supports comparison of devices that are multiple hops away in an SRDF configuration.

When using Disk Compare, you can:

◆ Compare multiple devices at the same time. You can analyze all tracks on up to 32 pairs of logical disk volumes at the same time.

◆ Refine the scope of comparison by specifying the number of cylinders you want to compare, including the cylinder skip count.

Disk Compare reports all miss-compares and errors on a pair of volumes until it has detected a preset number of miss-compared tracks. At that point, Disk Compare terminates. If you are comparing multiple pairs of devices, and any device pair fails, the remaining device pairs continue to be processed.

The utility is able to perform remote comparisons in SRDF configurations that include two or three VMAX systems. This allows you to verify the data integrity of the primary (R1) and secondary (R2) device.



Getting started

Prerequisites

Before using Disk Compare, take the following steps:

◆ Verify that there is at least one online path to each device.

◆ Stop any update activities on the devices you want to compare.

Note: The devices you compare can be either online or offline.

Running Disk Compare

The Disk Compare utility runs as a batch job.

The program name is EMCDSKC. Refer to “Sample JCL” on page 395 for a sample of DiskCompare JCL. “Parameters” on page 396 provides description of relevant parameters.

Sample JCL

The following is an example of JCL for the Disk Compare utility.

Note: Refer to the ResourcePak Base SAMPLIB(EMCDC) member included with your kit for the latest sample.

// jobcard//DISKCOMP EXEC PGM=EMCDSKC,REGION=6M,// PARM='parameters'//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB//SCF$nnnn DD DUMMY //SYSPRINT DD SYSOUT=class

Where:


◆ parameters are described in “Parameters” on page 396.

◆ ds_prefix is the product dataset name prefix you specified during installation of Mainframe Enablers, as described in the Mainframe Enablers Installation and Customization Guide.

◆ SCF$nnnn identifies the SCF subsystem used for Disk Compare.

◆ SYSPRINT DD SYSOUT=class is necessary because Disk Compare messages are in the SYSPRINT DD.

Getting started 395


Parameters

Disk Compare parameters are specified in the following order:

[START,][ERROR,]CUU1,CUU2[,CYLCHK][,CYLSKIP][,NUMDEV][,TME][,CL]

IMPORTANT

Specify the optional and required parameters exactly in the order shown above.

CL The number of cycles to wait before displaying the DCOMP33I status message.

Valid values are from 0 to 10000. The default value is 200. 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.

The CL parameter is specified after the TME parameter. If CYLCHK, CYLSKIP, NUMDEV, TME parameters are not used, add default values of each parameter to PARM before specifying the CL parameter.

CUU1 The z/OS device number of the first device to compare.


CUU1={cuu|ccuu|volser| RMT(cuu1[,srdfgrp1[/symdv#],srdfgrp2[/symdv#]])}

Where:

cuu|ccuu

The 3- or 4-byte z/OS device number.

Note: The device can be either online or offline.

volser

The 6-character z/OS volume serial number.

Note: The volume must be online.

RMT(cuu1[,srdfgrp1[/symdv#][,srdfgrp2[/symdv#]]])

Allows to specify a remote device.

cuu1

The z/OS device number.

srdfgrp1

The 2-digit number of SRDF group 1.

srdfgrp2


symdv#

The VMAX device number.



If the SRDF group and VMAX device number is not specified, Disk Compare finds the R2 automatically.

Note: If CUU1 is specified using RMT, then CUU2 has to be RMT as well.

CUU2 The z/OS device number of the second device to compare.


CUU2={cuu|ccuu|RMT|RMT(,srdfgrp1[/symdv#][,srdfgrp2[/symdv#]])}

Where:

cuu|ccuu

The 3- or 4-byte z/OS device number.

Note: The device can be either online or offline.

RMT

When you specify this keyword, the second device to compare is considered to be the remote VMAX device associated with CUU1.

RMT(,srdfgrp1[/symdv#][,srdfgrp2[/symdv#]])

Allows to specify a remote device to compare images two hops away. Only the last VMAX device is honored.

srdfgrp1


Note: If the device is in a Concurrent SRDF configuration and no SRDF group is specified, DiskCompare uses the first SRDF group encountered.

srdfgrp2


symdv#

The VMAX device number.

The VMAX device is considered to be in the last SRDF group.

For example:

– RMT(,02/0000006F) specifies the VMAX device one hop away.

– RMT(,02/0000006F,3E) or RMT(,02,3E/00000012) specifies the VMAX device two hops away.

If the SRDF group and VMAX device number is not specified, Disk Compare finds the R2 automatically. If symdv# is missing, Disk Compare uses the last VMAX device number in the last specified SRDF group.

Note: If CUU1 is specified using RMT, then CUU2 has to be RMT as well.

Getting started 397


CYLCHK The count of cylinders to be compared, starting from the first one. Valid values are from 0 to 9999999. The default value is 9999999.

If you set CYLCHK to 0, the whole volume is compared.

If you specify more cylinders than exist on the volume, Disk Compare reduces the count of cylinders to the size of the volume.

CYLSKIP The count of cylinders to skip during processing plus one cylinder to process. For example, if you set CYLSKIP to 5, Disk Compare processes 1 cylinder and skips 4.


CYLSKIP={count|ALLOC}

Where:

ALLOC

Disk Compare compares all allocated cylinders.

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.

count

A decimal value from 0 to 99999, summing up the number of cylinders to be skipped and one cylinder to be processed.

The default value is 1, meaning that every cylinder is processed. If you set count to zero (0), Disk Compare also uses the default value of one.

When count is 99 or 999, 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 miss-compares before stopping.

Note: Normally, Disk Compare stops after 5 miss-compares.

When count is 9999, Disk Compare compares the whole volume with an unlimited error count.

Note: Normally, Disk Compare stops after 5 miss-compares.

Note: If you set CYLSKIP > CYLCHK, only the first cylinder is compared.When you specify the ERROR parameter, the CYLSKIP parameter is set to 0.



ERROR The number of miss-compares per device pair after which Disk Compare terminates.


{ERROR|ERR|E|ALLOW|A}=count

Where:

count

The number of miss-compares. Valid values are from 1 to 255. The default value is 5. When “255” is specified, Disk Compare does not terminate until the whole volume has been read.

The optional ERROR parameter is specified before all other parameters.

Note: When you specify the ERROR parameter, the CYLSKIP parameter is set to 0.

NUMDEV Sets the count of CUU1 and CUU2 device pairs to compare.

Disk Compare increments each CUU address of the device pair to calculate the next CUU1/CUU2 pair.

For example, if CUU1 is 0D00, CUU2 is 0E00 and NUMDEV is 2, Disk Compare compares 0D00 to 0E00 and then 0D01 to 0E01.

Do not use NUMDEV when CUU1 is a volser.

Valid values are from 1 to 32. The default value is 1. If you specify a value greater than 32, it is reset to 32.

START The number of the first cylinder to be compared.


{START|S|SCCHH}=n

Where:

n

The 8-character hex number representing the 28-bit 0cccCCCC address of the first cylinder to be compared. The default value is 0, meaning maximum cylinder count.

Note: The maximum value of the START parameter depends on the type of compared devices.

The optional START parameter is specified before the CUU1 parameter.

TME The time (in seconds) to wait before displaying the DCOMP33I status message.

Valid values are from 0 to 86400. The default value is 120. If you set TME to 0, Disk Compare uses the default value of 120. If you set TME to a value greater than 86400, Disk Compare uses the maximum value of 86400.

The TME parameter is specified after the NUMDEV parameter. If CYLCHK, CYLSKIP, NUMDEV parameters are not used, add default values of each parameter to PARM before specifying the TME parameter.

Getting started 399


Comparing tracks


Disk Compare operations are listed in Table 42.

Table 42 Disk Compare operations

Operation Control

Choose devices to be compared • CUU1 parameter• CUU2 parameter• NUMDEV parameter

Choose cylinders to be compared • CYLCHK parameter• CYLSKIP parameter• START parameter

Set maximum error count ERROR parameter

Set period to display status information • TME parameter• CL parameter



Examples

Local comparison examples1. To compare device 3074 to device 4074:

CUU1=3074,CUU2=4074

2. To compare every 8th cylinder on device 3005 and device 5440:

CUU1=3005,CUU2=5440,CYLSKIP=8

3. To compare all allocated tracks on device 4077 with same tracks on device 7734:

CUU1=4077,CUU2=7734,CYLSKIP=ALLOC

4. To compare device 0D00 to device 0E00 and then compare device 0D01 to device 0E01:

CUU1=0D00,CUU2=0E00,NUMDEV=2

5. To compare device 31B4 to device 51B4 and stop when 17 errors are encountered:

ERR=17,31B4,51B4

6. To compare all tracks on device 31B4 and 51B4, displaying the DCOMP33I status message when 400 cylinders are compared or every 120 seconds:

31B4,51B4,99999,0,1,120,400

7. To compare device 31B4 to device 51B4 and ignore all cylinders prior to cylinder 00000190:

S=00000190,31B4,51B4

8. To compare device 31B4 to device 51B4 and ignore all cylinders prior to cylinder 00000190, stopping when 17 errors are encountered:

E=17,S=00000190,31B4,51B4

Local to remote comparison examples9. To compare device 3005 to the remote R2 device associated with device 3005:

CUU1=3005,CUU2=RMT

10. The following examples illustrate four versions of the same cascaded disk compare between a local and a remote device.

CUU1=4077,CUU2=RMT(,07,17)CUU1=4077,CUU2=RMT(,07/000021B9,17)CUU1=4077,CUU2=RMT(,07,17/00003005)CUU1=4077,CUU2=RMT(,07/000021B9,17/00003005)

Note that only the last VMAX device number is used. Each of the examples identifies the final target VMAX device number as 3005, whether explicitly stated or not.

Comparing tracks 401


Remote to remote comparison examples11. To compare remote device 21B9 to remote device 3005:

CUU1=RMT(4077,07),CUU2=RMT(,07,17)CUU1=RMT(4077,07),CUU2=RMT(,07/000021B9,17)CUU1=RMT(4077,07),CUU2=RMT(,07,17/00003005)CUU1=RMT(4077,07/21B9),CUU2=RMT(,07/000021B9,17/00003005)


PART 2

STORAGE POOLS

Part 2 describes ResourcePak Base features and components that you can use to manage and monitor storage pools. This part contains the following chapters:

Chapter 13, “Managing Storage Pools (GPM),” enables you to manage and control storage pools under different versions of Enginuity/HYPERMAX OS.

Chapter 14, “Monitoring Thin Pools (THN Monitor),” describes how to monitor thin pools using the THN Monitor.

Chapter 15, “Monitoring Snap Pools (SDV Monitor),” describes how to monitor save devices using SDV Monitor under Enginuity 5876 and 5773.

Chapter 16, “Monitoring DSE Pools (DSE Monitor),” provides instructions on monitoring DSE pools with the DSE Monitor under Enginuity 5876 and 5773.

Chapter 17, “Monitoring Space Reclamation (TRU Monitor),” enables you to scan and reclaim space in the TRU environment.

403

CHAPTER 13Managing Storage Pools (GPM)


◆ Introduction.......................................................................................................... 406◆ Getting started...................................................................................................... 407◆ Working with pools (HYPERMAX OS 5977 and higher)............................................ 410◆ Working with pools (Enginuity 5876 and 5773) ..................................................... 417◆ Queries (HYPERMAX OS 5977 and higher) ............................................................. 455◆ Queries (Enginuity 5876 and 5773)....................................................................... 468◆ Command reference (HYPERMAX OS 5977 and higher) .......................................... 488◆ Command reference (Enginuity 5876 and 5773).................................................... 526◆ Condition statements (ESFGPMBT) ........................................................................ 588◆ Return codes (ESFGPMBT)..................................................................................... 590

Managing Storage Pools (GPM) 405

Managing Storage Pools (GPM)

IntroductionResourcePak Base allows you to create and manage storage pools. The General Pool Management (GPM) facility of ResourcePak Base provides a set of online and batch commands to control storage pools using the ESFGPMBT utility.

Under Enginuity 5876 or 5773, ResourcePak Base supports thin (virtual) pools, SNAP pools, and DSE pools. Starting with HYPERMAX OS 5977, it supports a single pool type, thin pool, which can be used for virtual provisioning, as well as Snap and SRDF/A spillover (DSE).

HYPERMAX OS 5977 and higher

Under HYPERMAX OS 5977 and higher, pool management is implemented using Fully Automated Storage Tiering (FAST) technology.

Note: The VMAX3 Family with HYPERMAX OS VMAX 100K, VMAX 200K, VMAX400K Product Guide describes FAST concepts and operations.

Thin pools are not user-managed. All VMAX systems are preconfigured in the factory and managed by FAST.

You do not need to bind thin devices to a particular thin pool. Instead, groups of thin devices, or storage groups (SGs), are associated with a Storage Resource Pool (SRP), which is a collection of disk groups that make up a FAST domain. In addition, storage groups are associated with a Service Level Objective (SLO) and workload that together define the performance objective for the thin devices in the storage group and the projected response time.

Pool management operations for HYPERMAX OS 5977 and higher are listed in “Working with pools (HYPERMAX OS 5977 and higher)” on page 410. You perform these operations using the commands described in “Command reference (HYPERMAX OS 5977 and higher)” on page 488.

“Queries (HYPERMAX OS 5977 and higher)” on page 455 provides a description and examples of pool management queries.

Enginuity 5876 and 5773

Under Enginuity 5876 and 5773, pool management is provided with the FAST Virtual Provisioning™ technology.

Note: EMC VMAX documentation describes FAST VP.

Pool management operations for Enginuity 5876 and 5773 are listed in “Working with pools (Enginuity 5876 and 5773)” on page 417. You perform these operations using the commands described in “Command reference (Enginuity 5876 and 5773)” on page 526.

“Queries (Enginuity 5876 and 5773)” on page 468 provides a description and examples of pool management queries.



Getting started

Configuring GPM

After installation of ResourcePak Base, configure GPM using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The parameter that specifies GPM initialization settings is SCF.GPM.OSUB described in “SCF.GPM.OSUB” on page 79.

Executing GPM commands

You can execute GPM commands in either online or batch mode as follows:

◆ In batch mode, GPM commands can be executed by the ESFGPMBT utility, as described in “Running the ESFGPMBT utility” on page 407. You can also use conditional processing statements described in “ESFGPMBT conditional processing” on page 408.

◆ For online mode, you can use the z/OS MODIFY command, as described in Using ResourcePak Base commands 152, or the SCF Command Prefix Facility (CPF) described in “Command Prefix Facility” on page 173. The command type is GPM.

Note: Many GPM commands are executed on the VMAX 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.

Running the ESFGPMBT utility

The ESFGPMBT utility runs as a batch job. The program name is ESFGPMBT.

The following is an example of JCL for the ESFGPMBT utility.

// jobcard //STEP1 EXEC PGM=ESFGPMBT,REGION=region//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB//SCF$nnnn DD DUMMY//GPMPRINT DD SYSOUT=*//GPMINPUT DD *

GPM commands

/*

Where:


◆ region is the region size. The region size must be more than 4 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.


◆ SCF$nnnn identifies the SCF subsystem used for the ESFGPMBT utility.

Getting started 407


◆ GPM commands are described in “Command reference (Enginuity 5876 and 5773)” on page 526. Each GPM command begins with a new statement.

DD statements

DEBUG parameterPARM=DEBUG may be added to the EXEC statement to generate diagnostic information for all commands. This parameter does not affect the outcome of the commands. The 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.

ESFGPMBT 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. Statements that control conditional processing are provided in the batch input stream. They are IF, ELSE, ENDIF, and RESET, as described in “Condition statements (ESFGPMBT)” on page 588.

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. The logic flow follows these rules:

◆ When an IF statement is encountered, it is evaluated.

GPMINPUT DD 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 (described in “Condition statements (ESFGPMBT)” on page 588), a command may be continued on the next record by placing a hyphen as the last non-blank character of the record.

GPMPRINT DD 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.



• If the condition on the IF statement is true, the following commands are processed until the next control statement is encountered.

• If the condition on the IF 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 statement 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.

ExamplesBasic IF/ELSE/ENDIF DRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(040-045)

RESET LASTCCDRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1200-12FF) IF MAXCC=0 REMOVE POOL LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1041) REMOVE POOL LCL(UNIT(5500)) POOL(THINPOOL3) DEV(1200-12FF)ELSE QUERY POOLS LCL(UNIT(5500)) POOL(THINPOOL2) QUERY POOLS LCL(UNIT(5500)) POOL(THINPOOL3)ENDIF

Using IF with EXIT option DRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045) IF MAXCC=0 EXIT REMOVE POOL LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045)

Using IF/ELSE/ENDIF withEXIT option

DRAIN LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045) IF LASTCC>0 REMOVE POOL LCL(UNIT(5500)) POOL(THINPOOL2) DEV(1040-1045) DRAIN LCL(UNIT(5500)) POOL(THINPOOL3) DEV(1200-12FF)ELSE EXITENDIF

Getting started 409


Working with pools (HYPERMAX OS 5977 and higher)

Storage groups

A storage group (SG) is a group of thin devices, the definition of which is stored on the VMAX system. A storage group is identified by its name.

“Managing storage groups” on page 413 lists available operations with storage groups.

A storage group may contain a maximum of 4096 devices in total.

FAST-managed SGA FAST-managed SG is a storage group that is explicitly associated with a storage resource pool and/or a service level objective.

All thin devices are associated with the default SRP for that emulation type unless they are included in a storage group with the SRP attribute explicitly set.

All thin devices are associated with the “Optimized” SLO unless they are included in a storage group with the SLO attribute explicitly set.

CKD storage group restrictionsStorage groups containing CKD devices are limited with regard to SLO and workload assignment:

◆ CKD storage groups are limited to OPTIMIZED, DIAMOND, and BRONZE SLO levels only.

◆ CKD storage groups do not have an associated workload. Attempts to assign any other SLO or any workload will be rejected with an appropriate message.

Storage resource pools

A Storage Resource Pool (SRP) is a collection of disk groups that make up a FAST domain. A storage resource pool is identified by its name and has a description.

SRP reserved capacityThe SRP reserved capacity is the percentage of the total SRP capacity that is reserved for host I/O. New snapshots cannot be created in the SRP if the percentage free for the SRP is less than or equal to this value. For example, if the reserved capacity is set to 20%, new snapshots can only be created if the SRP is less than 80% full.

You can set the reserved capacity for an SRP using the RESV_CAP parameter of the SET SRP command, as described in “SET SRP” on page 518.

SRDF/A DSE-enabled SRPA DSE-enabled SRP is a storage resource pool that can be used in SRDF/A DSE spillover.

There must always be only one SRP enabled for DSE at all times. Until DSE is enabled for another SRP, the default FBA SRP is used. If there is no default FBA SRP, the default CKD SRP is used.



Enabling DSE for an SRP automatically disables the previously enabled SRP. Disabling DSE for an SRP automatically re-enables the default FBA SRP, unless there is no default FBA SRP in which case the default CKD SRP will be enabled. If there is only one SRP on the VMAX system, DSE may not be disabled for that SRP.

You can allow or prohibit use of an SRP for the SRDF/A DSE spillover using the RSDFA_DSE parameter of the SET SRP command, as described in “SET SRP” on page 518.

Maximum SRDF/A DSE capacity The maximum SRDF/A DSE capacity is the maximum amount of space (in GBs) in the SRP that may be used for spillover at any given time. If SRDF/A DSE is enabled on the SRP and the total spilled data exceeds the maximum DSE capacity, then spillover will be stopped.

The maximum DSE capacity is not persistent if SRDF/A DSE is disabled for the SRP and then re-enabled.

When DSE is enabled for an SRP, the maximum DSE capacity is initially unlimited. With unlimited maximum DSE capacity, the amount of space in the SRP that may be used by spillover is not capped. The maximum DSE capacity remains unlimited unless it is changed using the DSE_MAX_CAP parameter of the SET SRP command, as described in “SET SRP” on page 518.

Service level objectives

A service level objective (SLO) determines the performance level for the thin devices in a storage group. The SLO, together with the workload, defines the projected response time for the storage group. A SLO is identified by its name and has a description.

You can associate a SLO with an SG using the SLO parameter of the SET SYMSG command described in “SET SYMSG” on page 520.

SLO levelsThe available SLO level depends on the licensing option and the drive types present on the VMAX system.

Available SLO levels are listed in Table 1.

Note: Table 1 uses base SLO names. Refer to “Customizing SLO names” on page 412 for information about SLO names.

Table 1 SLO levels

SLO Name Description

Diamond Emulates EFD performance.

Platinum Emulates performance between 15K drive and EFD.

Gold Emulates 15K drive performance.

Silver Emulates 10K drive performance.

Bronze Emulates 7.2K drive performance.

Optimized The system achieves optimal performance with available resources.

Working with pools (HYPERMAX OS 5977 and higher) 411


Note: CKD storage groups are limited to OPTIMIZED, DIAMOND, and BRONZE SLO levels only.

Disk type restrictionsSLOs restrictions based on the drive type are listed in Table 2. If the required drive types are not present, those SLOs are not displayed in the SLO report (described in “Service Level Objective Query” on page 459), but will be displayed if explicitly requested via the SLO filter.

Customizing SLO namesYou can customize SLO names to suit your environment using the RENAME SLO command described in “RENAME SLO” on page 514.

Once renamed, all commands other than RENAME SLO itself specifying a SLO name should use the new SLO name. However, the attributes of the renamed SLO remain the same as those associated with the original name and the original name is retained internally.

You can also revert an SLO to its original (base) name.

Note: Refer to “RENAME SLO” on page 514 for SLO naming rules.

Workload

Storage group workload determines the type of workload that is expected to run against the thin devices in the storage group. The workload, together with the SLO, defines the projected response time for the storage group. A workload is identified by its name.

You can associate a workload with a storage group using the WorkLoad parameter of the SET SYMSG command described in “SET SYMSG” on page 520.

Note: CKD storage groups do not have an associated workload. Attempts to assign any other SLO or any workload will be rejected with an appropriate message.

Table 2 Disk drive requirements

SLO Required Disk Type

Diamond EFD

Platinum EFD and (15K or 10K)

Gold EFD and (15K or 10K or 7.2K)

Silver EFD and (15K or 10K or 7.2K)

Bronze 7.2K and (15K or 10K)

Optimized Any



Available workloadsAvailable workloads are listed in Table 3.

Disk group

A disk group is a collection of physical disks on the VMAX system. A disk group is identified by its name.

SRDF coordination

SRDF coordination denotes the ability to send read statistics across an SRDF link from the R1s in a storage group to the R2s for use by FAST. This ensures that the FAST engine prioritizes the data on the R2 side similarly to the data on the R1 side in case of failover.


Managing storage groupsTable 4 lists operations for managing storage groups.

Table 3 Available workloads

Workload Description

OLTP Online Transaction Processing — optimal for small, random I/Os

OLTP_REP Online Transaction Processing with Replication — optimal for small, random I/Os plus local/remote replication

DSS Decision Support Systems — optimal for large, sequential I/Os

DSS_REP Decision Support Systems with Replication — optimal for large, sequential I/Os plus local/remote replication

Table 4 Storage group operations

Operation Control

Create storage group CREATE SYMSG command

Add thin devices to storage group ADD SYMSG command

Remove thin devices from storage group REMOVE SYMSG command

Associate SRP/SLO/workload with storage group SET SYMSG command

Rename storage group RENAME SYMSG command

Delete storage group DELETE SYMSG command



Managing storage resource poolsTable 5 lists operations for managing storage resource pools.

Managing thin poolsTable 6 lists operations for managing thin pools.

Managing SLOsTable 7 lists operations for managing SLOs.

Managing thin devicesTable 8 lists operations for managing thin devices.

Thin device allocationsTable 9 lists operations for track allocation.

Table 5 Storage resource pool operations

Operation Control

Set SRP reserved capacity SET SRP command, RESV_CAP parameter

Allow/prohibit use of SRP for SRDF/A DSE SET SRP command, RDFA_DSE parameter

Set maximum SRDF/A DSE capacity SET SRP command, DSE_MAX_CAP parameter

Table 6 Thin pool operations

Operation Control

Rename pool RENAME POOL command

Table 7 SLO operations

Operation Control

Customize SLO name RENAME SLO command

Revert to base SLO name RENAME SLO command, NEWSLONAME(BASENAME) parameter

Table 8 Device operations

Operation Control

Change thin device status to Ready USR_RDY command

Change thin device status to Not Ready USR_NRDY command

Halt thin device tasks HALTTASK command

Table 9 Track allocation operations

Operation Control

Pre-allocate all tracks for thin devices ALLOCATE command

Clear persistent attribute for thin devices PERSIST OFF command



Running queriesTable 10 lists operations for producing GPM queries.

Controlling command executionTable 11 lists command execution settings.

Getting helpTable 12 lists operations for getting help.

Table 10 Query commands

Operation Control

Storage Group Query QUERY SYMSG command

Storage Group Performance Statistics Query QUERY SYMSG command, STATS parameter

Storage Resource Pool Query QUERY SRP command

Service Level Objective Query QUERY SLO command

Disk Group Query QUERY DISKGRP command

Pool Query QUERY POOLS command

Thin Device Query QUERY THINDEV command

Thin Device Allocations Query QUERY ALLOC command

Thin Device Allocations by Pool Query QUERY ALLALLOCS command

Data Device Query QUERY DATADEV command

Table 11 Command execution settings

Operation Control

Enable debugging • DEBUG parameter of a command• DEBUG parameter of the ESFGPMBT utility

Check command syntax without execution NOEXEC parameter of a command

Skip ineligible devices SKIP parameter of a command

Set up conditional processing for batch execution • IF statement• ELSE statement• ENDIF statement• RESET statement

Table 12 Getting help

Operation Control

View supported GPM commands HELP command



SRP-level alerts

SRP-level alerts are written to the z/OS console and EREP in the form of IEA480E and IEA499E operator messages if the percentage full for a storage resource pool (SRP) exceeds a predefined alert threshold.

Alerts are triggered when the following thresholds are exceeded: 80%, 90%, 95%, 96%, 97%, 98%, 99%, and when the pool reaches 100% full.

IEA499E messageThe IEA499E attention message indicates that the percentage full for the specified SRP has exceeded a predefined threshold.

◆ The first item after the message ID indicates the z/OS device number (CUU) of the device where the notification was received.

◆ The second item indicates the volume serial of the device.

◆ The third item indicates the ID of the SRP whose threshold was exceeded.

◆ The fourth item indicates the subsystem ID (SSID) containing the device where the notification was received.

The message also indicates the percentage capacity remaining in the SRP. If the SRP is full, the message indicates “REPOSITORY VOLUME CAPACITY EXHAUSTED.”

In the following example, SRP with ID 0001 has exceeded a predefined threshold and has 10% capacity remaining:

*IEA499E 3E80,MF3E80,0001,3E00,002107.921.EMC.08.0000000RGKHK, 610 REPOSITORY VOLUME WARNING: AT 10% CAPACITY REMAINING

IEA480E messageThe IEA480E Service Information Message (SIM) with reference code 247C represents environmental error 047C indicating that the specified SRP has inactive or Not Ready devices. The second part of the reference code indicates the SRP ID.

The severity of the IEA480E message is “ACUTE.” The IEA480E message is logged every 8 hours for as long as the device remains inactive or Not Ready. If another device is made inactive or Not Ready, the message is logged again immediately.

In the following example, SRP with ID 0001 has inactive or Not Ready devices:

*IEA480E 9128,SCU,ACUTE ALERT,MT=2107,SER=0508-ABWWA, 028 REFCODE=247C-0001-0000,SENSE=00101000 283C8F00 11C00000 01018214 081A060E 9100247C 05100200 F1000000



Working with pools (Enginuity 5876 and 5773)


Managing poolsTable 13 lists operations for managing pools.

Managing devicesTable 14 lists operations for managing devices.

Table 13 Pool operations

Operation Control

Create pool CREATE POOL command

Add data or save devices to pool ADD POOL command

Remove data or save devices from pool REMOVE POOL command

Set pool attributes POOLATTR command

Rebalance pool REBALANCE command

Rename pool RENAME POOL command

Delete pool DELETE POOL command

Table 14 Device operations

Operation Control

Enable data or save devices in pool ENABLE command

Bind thin devices to pool BIND command

Bind already bound thin devices to different pool REBIND command

Unbind thin devices UNBIND command

Move allocations for thin devices MOVE command

Reassign allocated tracks to other data or save devices in pool

DRAIN command

Stop reassigning allocated tracks to other data or save devices in pool

HDRAIN command

Change thin device status to Ready USR_RDY command

Change thin device status to Not Ready USR_NRDY command

Disable data or save devices in pool DISABLE command

Halt thin device tasks HALTTASK command

Working with pools (Enginuity 5876 and 5773) 417


Thin device allocationTable 15 lists operations for thin device allocations.

Thin device compressionTable 16 lists operations for thin device compression.

Running queriesTable 19 lists operations for producing GPM queries.

Table 15 Thin device allocation operations

Operation Control

Allocate tracks to thin devices ALLOCATE command

Clear persistent attribute for thin devices PERSIST OFF command

Table 16 Thin device compression operations

Operation Control

Enable or disable compression for a pool POOLATTR command, COMPRESSION parameter

Compress thin devices COMPRESS command

Decompress thin devices DECOMPRESS command

Table 17 Query commands

Operation Control

FAST Tier Query QUERY TIERS command

Pool Query QUERY POOLS command

Pool Device Query QUERY POOLDEV command

Thin Device Query QUERY THINDEV command

Thin Device Allocations Query QUERY ALLOC command

Thin Device Allocations by Pool Query QUERY ALLALLOCS command

Data Device Query QUERY DATADEV command

Save Device Query QUERY SAVEDEV command

Rebalance Task Query QUERY TASKS command



Controlling command executionTable 18 lists command execution settings.

Getting helpTable 19 lists operations for getting help.

Table 18 Command execution settings

Operation Control

Enable debugging • DEBUG parameter of a command• DEBUG parameter of the ESFGPMBT utility

Check command syntax without execution NOEXEC parameter of a command

Enable verbose messaging VERBOSE parameter of a command

Set completion wait time WAIT[(waittime[,{WARN|ERROR}])] parameter of a command

Skip ineligible devices SKIP parameter of a command

Set up conditional processing for batch execution • IF statement• ELSE statement• ENDIF statement• RESET statement

Table 19 Getting help

Operation Control

View supported GPM commands HELP command



Creating/deleting pools

Pool and device typesWhen a pool is created, it is created as either a Snap pool, a DSE pool, or a thin pool.

Snap pools are available starting with Enginuity 5771. DSE pools are available starting with Enginuity 5772. Thin pools are available with Enginuity 5773 for FBA devices only. Enginuity 5876 and HYPERMAX OS 5977 support thin pools for both FBA and CKD devices.

These pools consist of save devices or data devices which are specifically configured to be used for pools. Devices in pool storage are a predefined set of devices that provide a pool of physical space. These devices are not host-accessible, but they have their VMAX device numbers.

Save devices can be removed from a Snap or DSE pool and data devices can be removed from a thin pool, but the devices must first be “drained” and disabled. Drained devices become inactive within their pool and can then be moved out of the pool to be available for other pools.

A pool can contain the following devices:

◆ Unassigned save devices

Unassigned save devices may be assigned as Snap or DSE pool devices. Conversely, these devices can be drained and returned to the default pool.

◆ Snap pool devices

Virtual devices (VDEVs) are used by TimeFinder/Clone Mainframe Snap Facility.

Note: The TimeFinder/Clone Mainframe Snap for z/OS Product Guide describes TimeFinder/Clone Mainframe Snap Facility.

VDEVs make use of Snap pool devices to store pre-update images of tracks changed on the source device or new writes to the virtual devices. This results in space-efficient replicas, which consume less real space than their sources.

◆ DSE devices

SRDF/A DSE (Delta Set Extension) devices provide space to save devices when the cache resources in an SRDF/A source VMAX system reach the SRDF/A limit. This extra space permits SRDF/A to keep running during transient problems such as temporary link loss.

Multiple Snap or DSE pools 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.



SRDF/A DSE pools

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

Pool device geometry

A data or save device to be added to a pool must be compatible with any data or save devices already in the pool. 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 data device added to a thin pool on a VMAX system under Enginuity 5876 must have the same storage class and speed as the data device(s) already in the pool.

A data or save device to be added to a pool must be compatible with the pool type:

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

Maximum number of pools

◆ With Enginuity 5773, you 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 thin pools).

◆ With Enginuity 5876, you can create Snap, DSE, and thin pools. 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 VMAX system (a combination of all user-defined Snap, DSE, and thin pools).



Special pools

Two special pools, DEFAULT_POOL and DF_DDEV_POOL, contain data or save devices that have not been assigned to any named pools and are available for Snap, DSE, and thin pool operations. The data or save 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 DEFAULT_POOL can be added to an existing Snap or DSE pool. 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 DF_DDEV_POOL can be added to an existing thin pool. Once they are enabled, data devices in a pool are available for use.

Pool alertsAlert thresholds apply only to thin pools.

Two thresholds are available, a warning or low alert and a critical or high alert. Each threshold represents 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 raised.

You can set the alert thresholds using the POOLATTR command described in “POOLATTR” on page 559.

Oversubscription rateOversubscription rate is the ratio of bound thin device tracks to active data device tracks for a thin pool, shown as a percentage. 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 100% 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 100% 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 100% 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 oversubscribed 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.

The actual oversubscription rate (ActO) and maximum oversubscription rate (MaxO) is shown for each thin pool on the pool list query.



Example 11. QUERY all of the pools in a VMAX system:

F EMCSCF,GPM,QUERY POOLS LCL(UNIT(3800))

EMCU500I QUERY POOLS LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD3 0001 T Avail 3390 FIBRE 10K 70 96 100 34 N EnabledEMCU012I RECLAIM_TEST 0002 T Avail 3390 FIBRE 10K 70 80 200 29 N DisabledEMCU012I STCM_TCKD_00 0003 T Avail 3390 FIBRE 15K 70 80 0 32 N DisabledEMCU012I STCM_TCKD_01 0004 T Avail 3390 FIBRE 15K 70 80 100 34 N DisabledEMCU012I STCM_TCKD_02 0005 T Avail 3390 SATA 7200 70 80 300 40 N DisabledEMCU012I STCM_TCKD_03 0006 T Avail ? 70 80 0 0 N DisabledEMCU012I EGJDSEPOOL 0007 D Avail ? 70 80 0 0 N DisabledEMCU012I MF1233 0008 T Avail 3390 FIBRE 10K 70 80 100 34 N DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete

Note: Type S = Snap pools (SAVEDEV)Type T = Thin pools (TDAT)Type D = DSE pools (DSE DEV)

2. CREATE POOL:

F EMCSCF,GPM,CREATE POOL(EMCCKDVP) LCL(UNIT(3800)) TYPE(THINPOOL)

EMCU500I CREATE POOL(EMCCKDVP) LCL(UNIT(3800)) TYPE(THINPOOL)EMCU002I GPM command successful

3. QUERY POOLS:


EMCU500I QUERY POOLS LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD3 0001 T Avail 3390 FIBRE 10K 70 96 100 34 N EnabledEMCU012I RECLAIM_TEST 0002 T Avail 3390 FIBRE 10K 70 80 200 29 N DisabledEMCU012I STCM_TCKD_00 0003 T Avail 3390 FIBRE 15K 70 80 0 32 N DisabledEMCU012I STCM_TCKD_01 0004 T Avail 3390 FIBRE 15K 70 80 100 34 N DisabledEMCU012I STCM_TCKD_02 0005 T Avail 3390 SATA 7200 70 80 300 40 N DisabledEMCU012I STCM_TCKD_03 0006 T Avail ? 70 80 0 0 N DisabledEMCU012I EGJDSEPOOL 0007 D Avail ? 70 80 0 0 N DisabledEMCU012I MF1233 0008 T Avail 3390 FIBRE 10K 70 80 100 34 N DisabledEMCU012I EMCCKDVP 0009 T Avail ? 70 80 0 0 N DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete



4. QUERY DATADEV to find available data devices:

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3800))

EMCU500I QUERY DATADEV LCL(UNIT(3800)) EMCU184I Data Devices on 0001957-00079 API Ver: 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 28C-28D to the pool:

F EMCSCF,GPM,ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28C-28D)

EMCU500I ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28C-28D)EMCU184I Data Devices on 0001957-00079 API Ver: 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

F EMCSCF,GPM,ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(290-291)

EMCU500I ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(290-291)EMCU009I Requested devices EMCU009I 0000028C-0000028D EMCU00AI Eligible devices EMCU00AI 0000028C-0000028D EMCU00BI Completed devices EMCU00BI 0000028C-0000028D EMCU002I GPM command successful

Note: Notice the result of trying to add data devices of mixed class.

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3800)) DEV(290-291)

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: EMCU061I Device# Emul Used Free Pool Name Type Class 0Speed Prot A/I Status EMCU063I 00000290 3390 DF_DDEV_POOL FLASH FLASH 07200RD1 0I EMCU063I 00000291 3390 DF_DDEV_POOL FLASH FLASH 7200RD1 0I EMCU064I Totals: EMCU064I 3390: 0 used tracks, 33360 free tracks, 0% used EMCU001I GPM command complete



F EMCSCF,GPM,ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(290-291)

EMCU500I ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(290-291) EMCP001I GPM ADD POOL LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(290-291) EMCU009I Requested devices EMCU009I 00000290-00000291 EMCU533E Devices do not match class and/or speed of existing pool devices EMCU533E 00000290-00000291 EMCU004W No eligible devices found

Note: Notice the result of trying to add devices of mixed speed.

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3800)) DEV(28A-28B)

EMCU500I QUERY DATADEV LCL(UNIT(3800)) DEV(28A-28B) EMCU184I Data Devices on 0001957-00079 API Ver: 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

F EMCSCF,GPM,ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28A-28B)

EMCU500I ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28A-28B) EMCU009I Requested devices EMCU009I 0000028A-0000028B EMCU533E Devices do not match class and/or speed of existing pool devices EMCU533E 0000028A-0000028B EMCU004W No eligible devices found

Note: Notice the result of trying to add data 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:

F EMCSCF,GPM,ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(122E)

EMCU500I ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(122E) EMCP001I GPM ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(122E) EMCU009I Requested devices EMCU009I 0000122E EMCU53EE Devices are of mixed protection types or do not match pool protection type EMCU53EE 0000122E EMCU003E GPM command failed

6. QUERY DATADEV to see data devices in the pool:

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP)

EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP)EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: EMCU061I 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 complete



7. QUERY THINDEV for available thin devices:

F EMCSCF,GPM,QUERY THINDEV LCL(UNIT(3A00)) POOL(MFCKD1)

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

8. ENABLE data devices in pool:

F EMCSCF,GPM, ENABLE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28C-28D)

EMCU500I ENABLE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28C-28D) EMCU009I Requested devices EMCU009I 0000028C-0000028D EMCU00AI Eligible devices EMCU00AI 0000028C-0000028D EMCU00BI Completed devices EMCU00BI 0000028C-0000028D EMCU002I GPM command successful

Note: There is also an ACTIVE parameter on ADD POOL to ENABLE data devices in pool.

F EMCSCF,GPM,ADD POOL(EMCCKDVP) ACTIVE LCL(UNIT(3800)) DEV(2BA)

EMCU500I ADD POOL(EMCCKDVP) ACTIVE LCL(UNIT(3800)) DEV(2BA)EMCP001I GPM ADD POOL LCL(UNIT(3800)) DEV(2BA) ACTIVE POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 000002BA EMCU00AI Eligible devices EMCU00AI 000002BA EMCU00BI Completed devices EMCU00BI 000002BA EMCU002I GPM command successful

9. QUERY DATADEV to see data devices in the pool and verify that they are Active:


EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 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



10. BIND thin devices to the pool:

F EMCSCF,GPM,BIND LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(170)

EMCU500I BIND LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(170) EMCU009I Requested devices EMCU009I 00000170 EMCU00AI Eligible devices EMCU00AI 00000170 EMCU00BI Completed devices EMCU00BI 00000170 EMCU002I GPM command successful

Note: Notice the result of the BIND attempt prior to the ENABLE command making the data devices ACTIVE.

F EMCSCF,GPM,BIND LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(170)

EMCU500I BIND LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(170) EMCU009I Requested devices EMCU009I 0000 0170 EMCU00AI Eligible devices EMCU00AI 00000170 EMCU139E No available data devices in pool EMCCKDVP EMCU003E GPM command failed

11. QUERY data and thin devices:


EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP)EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: EMCU061I Device# Emul A/I Used Free Class Speed Prot StatusEMCU063I 0000028C 3390 A 60 16620 FIBRE 15K RD1EMCU063I 0000028D 3390 A 60 16620 FIBRE 15K RD1EMCU064I Totals:EMCU064I 3390: 120 used tracks, 33240 free tracks, 0% usedEMCU001I GPM command complete

F EMCSCF,GPM,QUERY THINDEV LCL(UNIT(3800)) DEV(170)

EMCU500I QUERY THINDEV LCL(UNIT(3800)) DEV(170)EMCU184I Thin Devices on 0001957-00079 API Ver:


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: EMCU108I 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 complete



Example 21. CREATE POOL and QUERY POOLS to display the new pool:

F EMCSCF,GPM,CREATE POOL(EMCCKDVP2) LCL(UNIT(3800)) TYPE(THINPOOL) EMCU500I CREATE POOL(EMCCKDVP2) LCL(UNIT(3800)) TYPE(THINPOOL) EMCP001I GPM CREATE POOL(EMCCKDVP2) LCL(UNIT(3800)) TYPE(THINPOOL) EMCU002I GPM command successful


EMCU500I QUERY POOLS LCL(UNIT(3800))EMCP001I GPM QUERY POOLS LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I RECLAIM_TEST 0001 T Avail 3390 FIBRE 10K 70 80 100 34 N EnabledEMCU012I EMCCKDVP 0002 T Avail 3390 FIBRE 10K 70 80 100 29 N DisabledEMCU012I EMCCKDVP2 0003 T Avail ? 70 80 0 0 N DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete

2. QUERY data devices:


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: EMCU061I Device# Emul Used Free Pool Name 000Type Class Speed Prot --A/IStatus 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

3. ADD data devices to the new pool and QUERY POOLS to display the pool:

F EMCSCF,GPM,ADD POOL(EMCCKDVP2) LCL(UNIT(3800)) DEV(280-283)

EMCU500I ADD POOL(EMCCKDVP2) LCL(UNIT(3800)) DEV(280-283) EMCP001I GPM ADD POOL LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCU009I Requested devices EMCU009I 00000280-00000283 EMCU00AI Eligible devices EMCU00AI 00000280-00000283 EMCU00BI Completed devices EMCU00BI 00000280-00000283 EMCU002I GPM command successful


EMCU500I QUERY POOLS LCL(UNIT(3800)) EMCP001I GPM QUERY POOLS LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I RECLAIM_TEST 0001 T Avail 3390 FIBRE 10K 70 80 100 34 N EnabledEMCU012I EMCCKDVP 0002 T Avail 3390 FIBRE 10K 70 80 100 29 N DisabledEMCU012I EMCCKDVP2 0003 T Avail 3390 SATA 7200 70 80 0 0 N DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete



4. ENABLE data devices in the new pool:

F EMCSCF,GPM,ENABLE LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2)

EMCU500I ENABLE LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCP001I GPM ENABLE LCL(UNIT(3800)) DEV(280-283) POOL(EMCCKDVP2) EMCU009I Requested devices EMCU009I 00000280-00000283 EMCU00AI Eligible devices EMCU00AI 00000280-00000283 EMCU00BI Completed devices EMCU00BI 00000280-00000283 EMCU002I GPM command successful

Note: Use QUERY DATADEV to verify that the devices are Active.

5. REBIND thin device to the new pool:

F EMCSCF,GPM,REBIND LCL(UNIT(3800)) DEV(170) POOL(EMCCKDVP2)

EMCU500I REBIND LCL(UNIT(3800)) DEV(170) POOL(EMCCKDVP2) EMCP001I GPM REBIND LCL(UNIT(3800)) DEV(170) POOL(EMCCKDVP2) EMCU009I Requested devices EMCU009I 00000170 EMCU00AI Eligible devices EMCU00AI 00000170 EMCU00BI Completed devices EMCU00BI 00000170 EMCU002I GPM command successful

6. QUERY THINDEV and DATADEV:


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: 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: EMCU061I Device# Emul Used Free Pool Name 0Type Class Speed Prot 00A/I StatusEMCU063I 00000280 3390 0 16680 EMCCKDVP2 Thin SATA000000720000RD1I 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

Note: QUERY DATADEV for the new pool to display updates following REBIND.



7. Prepare for unbind by making thin device USR-NRDY:

F EMCSCF,GPM,USR-NRDY LCL(UNIT(3800)) DEV(170)

EMCU500I USR-NRDY LCL(UNIT(3800)) DEV(170) EMCP001I GPM USR-NRDY LCL(UNIT(3800)) DEV(170) EMCU009I Requested devices EMCU009I 00000170 EMCU00AI Eligible devices EMCU00AI 00000170 EMCU00BI Completed devices EMCU00BI 00000170 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: 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

8. UNBIND thin device:

F EMCSCF,GPM,UNBIND LCL(UNIT(3800)) POOL(EMCCKDVP2) DEV(170)

EMCU500I UNBIND LCL(UNIT(3800)) POOL(EMCCKDVP2) DEV(170) EMCP001I GPM UNBIND LCL(UNIT(3800)) POOL(EMCCKDVP2) DEV(170) EMCU009I Requested devices EMCU009I 00000170 EMCU00AI Eligible devices EMCU00AI 00000170 EMCU00DI Completed devices EMCU00DI 00000170 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: EMCU184I Thin Devices on 0001957-00086 Bound to Pool MFCKD1 API Ver: 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



9. QUERY DATADEV in pools:

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP2)

EMCU500I 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: EMCU061I Device# Emul A/I Used Free Class Speed ProtStatus 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: 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

10. DISABLE data devices and QUERY DATADEV:

F EMCSCF,GPM,DISABLE LCL(UNIT(3800)) DEV(28A-28B) POOL(EMCCKDVP)

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 0000028A-0000028B EMCU00AI Eligible devices EMCU00AI 0000028A-0000028B EMCU00BI Completed devices EMCU00BI 0000028A-0000028B 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: 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



11. Remove data devices from pool:

F EMCSCF,GPM,REMOVE POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28A-28B)

EMCU500I REMOVE POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28A-28B) EMCP001I GPM REMOVE POOL LCL(UNIT(3800)) DEV(28A-28B) POOL(EMCCKDVP) EMCU009I Requested devices EMCU009I 0000028A-0000028B EMCU00AI Eligible devices EMCU00AI 0000028A-0000028B EMCU00BI Completed devices EMCU00BI 0000028A-0000028B 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

12. DELETE POOL:

F EMCSCF,GPM,DELETE POOL LCL(UNIT(3800)) POOL(EMCCKDVP)

EMCU500I DELETE POOL LCL(UNIT(3800)) POOL(EMCCKDVP) EMCP001I GPM DELETE POOL LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU002I GPM command successful


EMCU500I QUERY POOLS LCL(UNIT(3800))EMCU010I Pools on Controller 0001957-00079 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD3 0001 T Avail 3390 FIBRE 10K 70 96 100 34 N EnabledEMCU012I RECLAIM_TEST 0002 T Avail 3390 FIBRE 10K 70 80 200 29 N DisabledEMCU012I STCM_TCKD_00 0003 T Avail 3390 FIBRE 15K 70 80 0 32 N DisabledEMCU012I STCM_TCKD_01 0004 T Avail 3390 FIBRE 15K 70 80 100 34 N DisabledEMCU012I STCM_TCKD_02 0005 T Avail 3390 SATA 7200 70 80 300 40 N DisabledEMCU012I STCM_TCKD_03 0006 T Avail ? 70 80 0 0 N DisabledEMCU012I EGJDSEPOOL 0007 D Avail ? 70 80 0 0 N DisabledEMCU012I MF1233 0008 T Avail 3390 FIBRE 10K 70 80 100 34 N DisabledEMCU012I DF_DDEV_POOL 0100 TEMCU001I GPM command complete



Adding/removing devices

Adding/removing data or save devicesYou add data or save devices to a pool using the ADD POOL command, as described in “ADD POOL” on page 528.

ADD POOL assigns one or more data or save devices to a pool. The data or save device(s) may be set as active and immediately available for track allocation, or may be left inactive and remain unavailable for track allocation until changed to active by an ENABLE command (described in “ENABLE” on page 548).

A data or save device to be added to a pool must be compatible with any devices already in the pool. When a data or save device is added to a pool that already contains one or more data or save devices, the new device must have the same emulation and protection type as the device(s) already in the pool. Additionally, a data device added to a thin pool on a VMAX system under Enginuity 5876 must have the same storage class and speed as the data device(s) already in the pool.

A device to be added to a pool must be compatible with the pool type:

◆ 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 data or save device that is already assigned to a pool may be assigned to a different pool by means of the ADD POOL command only when:

◆ The data or save device is inactive.

◆ No tracks are already allocated on the data or save device.

Enabling/disabling data or save devices

Enabling data or save devices

Enabling changes the status of one or more data or save devices from inactive to active and makes the devices available for allocation. You enable data or save devices using the ENABLE command described in “ENABLE” on page 548.

Subsequent actions requiring allocation within the pool where the data or save device(s) are assigned may result in allocation of tracks on the activated device(s). For a thin pool, such activity could consist of a host-apparent update to a thin device bound to the pool. For a DSE pool, it could be overflow of cache by an SRDF/A session on which DSE is active.

Disabling data or save devices

Disabling changes the status of one or more data or save devices from active to inactive and makes the devices unavailable for allocation. You disable data or save devices using the DISABLE command described in “DISABLE” on page 542.

Subsequent actions requiring allocation within the pool to which the data or save device(s) are assigned cannot result in allocation of tracks on the deactivated device(s). Tracks already allocated on the device(s) remain allocated.



Binding/unbinding thin devices

Binding thin devices

Binding establishes a relationship between one or more thin devices to a thin pool. The host “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.

You bind thin devices using the BIND command described in “BIND” on page 532.

To allow a bound thin device to be set active, change the thin device status to Ready using the USR_RDY command, as described in “USR_RDY” on page 586.

Unbinding thin devices

Unbinding terminates the relationship between a thin device and the pool to which it is bound. Any tracks allocated to thin devices in the pool on behalf of a thin device being unbound are freed.

You unbind thin devices using the UNBIND command described in “UNBIND” on page 582.

Unbinding results in data loss for the thin devices being unbound. Ensure that the data is no longer needed for these thin devices before unbinding.

Before unbinding a thin device, change the thin device status to Not Ready using the USR_NRDY command, as described in “USR_NRDY” on page 584.

Rebinding thin devices

Rebinding allows you to change the pool where a thin device is bound without loss of data. The tracks allocated to the thin device in the source thin pool are retained. Following completion of the rebind action, subsequent track allocations are made from the target thin pool.

You rebind thin devices using the REBIND command described in “REBIND” on page 577.

Note: Because the source thin pool is not specified, but is determined from the thin device, specification of a range of devices in the REBIND command can bind thin devices currently bound to different pools to a single pool.



Example1. Add data device to a pool:

F EMCSCF,GPM,ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28E)

EMCU500I ADD POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28E) EMCU009I Requested devices EMCU009I 0000028E EMCU00AI Eligible devices EMCU00AI 0000028E EMCU00BI Completed devices EMCU00BI 0000028E EMCU002I GPM command successful

2. ENABLE the data device:

F EMCSCF,GPM,ENABLE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E)

EMCU500I ENABLE LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E) EMCU009I Requested devices EMCU009I 0000028E EMCU00AI Eligible devices EMCU00AI 0000028E EMCU00BI Completed devices EMCU00BI 0000028E EMCU002I GPM command successful

Note: Use QUERY DATADEV to verify that the device has changed from Inactive to Active.

3. REBALANCE pool:

F EMCSCF,GPM, REBALANCE LCL(UNIT(3800)) POOL(EMCCKDVP)

EMCU500I REBALANCE LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU002I GPM command successful

4. QUERY data devices:


EMCU500I QUERY DATADEV LCL(UNIT(3800)) POOL(EMCCKDVP) EMCU184I Data Devices on 0001957-00079 in Pool EMCCKDVP API Ver: 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

5. DRAIN data device:

F EMCSCF,GPM,DRAIN LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E)

EMCU500I DRAIN LCL(UNIT(3800)) POOL(EMCCKDVP) DEV(28E) EMCU009I Requested devices EMCU009I 0000028E EMCU00AI Eligible devices EMCU00AI 0000028E EMCU00BI Completed devices EMCU00BI 0000028E EMCU002I GPM command successful

Note: Use QUERY DATADEV to verify that the device is Inactive.



6. Remove data device:

F EMCSCF,GPM,REMOVE POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28E)

EMCU500I REMOVE POOL(EMCCKDVP) LCL(UNIT(3800)) DEV(28E) EMCU009I Requested devices EMCU009I 0000028E EMCU00AI Eligible devices EMCU00AI 0000028E EMCU00BI Completed devices EMCU00BI 0000028E EMCU002I GPM command successful

Note: Use QUERY DATADEV to verify that the device has been removed.



Allocating/reallocating tracks

AllocationAllocation causes physical (data device) tracks to be allocated to back all logical (thin device) tracks for each thin device specified.

You allocate tracks using the ALLOCATE command, as described in “ALLOCATE” on page 530.

Without using ALLOCATE, physical tracks are allocated on data devices only when data is written to the thin device.

Persistent allocation

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

Resetting persistent attribute

You can reset the persistent attribute for all tracks allocated for the specified thin devices, allowing the tracks to be freed without the thin devices being unbound. To do this, use the PERSIST OFF command described in “PERSIST OFF” on page 557. 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: To allocate and mark all tracks persistent for the specified thin devices, use the ALLOCATE command with the PERSIST parameter, as described in “ALLOCATE” on page 530.

Moving allocations

You can move existing allocations for the requested thin devices from a source pool to a target pool without loss of data.

To move allocations, use the MOVE command described in “MOVE” on page 555.

The MOVE command moves existing allocations from a pool where the thin device(s) were previously bound to the pool where the thin device(s) are currently bound. All tracks allocated for the thin devices in the source pool are moved to the pool where the thin devices are currently bound. The thin devices must already have been rebound to the new pool using the REBIND command (described in “REBIND” on page 577) before the MOVE command, with the REBIND parameter, can be used.

Moving with rebindingIf the REBIND parameter is specified on the MOVE command, the thin devices are first rebound to the target pool, and then all tracks allocated for the thin devices in the source pool are moved to the target pool.



Movement with rebinding is not allowed if such rebinding causes the oversubscription rate (for Enginuity 5876) of the target pool to exceed the maximum oversubscription rate of the pool set the by the user.

Example1. MOVE with REBIND parameter:

F EMCSCF,GPM,MOVE DEV(0090-0093) REBIND LCL(UNIT(2101)) POOL(DTTHINPOOL2) SRCPOOL(DTTHINPOOL1)

EMCU500I MOVE DEV(0090-0093) REBIND LCL(UNIT(2101)) POOL(DTTHINPOOL2) -EMCU500I SRCPOOL(DTTHINPOOL1) EMCU009I Requested devices EMCU009I 00000090-00000093 EMCU00AI Eligible devices EMCU00AI 00000090-00000093 EMCU00BI Completed devices EMCU00BI 00000090-00000093 EMCU002I GPM command successful

2. QUERY to verify thin devices are rebound:

F EMCSCF,GPM,QUERY THINDEV LCL(UNIT(2101)) POOL(DTTHINPOOL2)

EMCU500I 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 complete

3. QUERY to verify allocations were moved:

F EMCSCF,GPM,QUERY ALLALLOCS LCL(UNIT(2101)) POOL(DTTHINPOOL2)

EMCU500I QUERY ALLALLOCS LCL(UNIT(2101)) POOL(DTTHINPOOL2)EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I Device Alloc CompressEMCU014I 00000090 16788 0EMCU014I 00000091 16788 0EMCU014I 00000092 16788 0EMCU014I 00000093 16788 0EMCU001I GPM command complete



Draining data or save devices

Draining initiates a process where allocated tracks on a data or save device in the pool are moved to other devices in the pool.

You drain data or save devices using the DRAIN command described in “DRAIN” on page 546.

During the drain process, new allocations are not made on the data or save device. When the drain process is complete, the data or save device is set inactive to prevent new allocations on the device.

You can halt the process of a data or save device in the pool reassigning its allocated tracks to other available devices in the same pool (draining) using the HDRAIN command described in “HDRAIN” on page 552.

All data or save devices that are actively draining when HDRAIN is issued are set as active. If any data or save 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 (described in “ENABLE” on page 548) must be issued for these devices to set them active before they can be used. All data or save devices that are active and not draining after the HDRAIN are identified as complete.

Example1. Display the data devices in the pool using QUERY DATADEV and identify the devices to

be drained:

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)

EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 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

2. DRAIN the data devices:

F EMCSCF,GPM,DRAIN DEV(0140-0148) LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)

EMCU500I DRAIN DEV(0140-0148) LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU009I Requested devicesEMCU009I 00000140-00000148EMCU00AI Eligible devices EMCU00AI 00000140-00000148 EMCU00CI Accepted devices EMCU00CI 00000140-00000148 EMCU002I GPM command successful



3. Check the status of the DRAIN using QUERY DATADEV:


EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 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

While the DRAIN is in progress, the draining data devices show DRAINING in the Status column of the QUERY DATADEV display.

Note: “QUERY DATADEV” on page 565 describes the QUERY DATADEV command.

The DRAIN process also makes the draining devices inactive, as shown 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 shown in the QUERY DATADEV display below.

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 data devices is zero. The drained data devices are also left inactive, as shown 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: 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



Rebalancing pools

Rebalancing moves tracks among data devices so as to approximately equalize the percentage of allocated tracks on all active data devices in the thin pool.

Note: Inactive data devices do not participate in rebalancing operations. You must enable data devices before rebalancing.

To rebalance a thin pool, use the REBALANCE command described in “REBALANCE” on page 575.

Rebalancing is made based on previously set pool attributes, or you can specify new parameters that only apply to the current operation.

Setting rebalancing goalYou can specify the rebalancing goal, 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. To set the goal, use the VARIANCE parameter of the REBALANCE command.

Checking rebalancing statusTo see the progress of the rebalancing operation, use the QUERY POOLS command described in “QUERY POOLS” on page 568.

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

If a pool does not indicate that it is rebalancing immediately after issuing a REBALANCE command, follow up with a subsequent pool list query. 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 data 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 the QUERY TASKS command described in “QUERY TASKS” on page 571 to check the status of the most recent rebalance task (the one with the highest task ID) of the pool to clearly see whether it is “Executing” or “Completed”.

The active data devices are considered balanced and the operation complete when, among these devices, the percentages of tracks allocated on any two data devices do not differ by more than one percent more than the specified or default variance value.

Example1. ENABLE the data devices:

F EMCSCF,GPM,ENABLE DEV(0140-0149) LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)

EMCU500I ENABLE DEV(0140-0149) LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU009I Requested devices EMCU009I 00000140-00000149 EMCU00AI Eligible devices EMCU00AI 00000140-00000149 EMCU00BI Completed devices EMCU00BI 00000140-00000149 EMCU002I GPM command successful



2. REBALANCE the pool:

F EMCSCF,GPM,REBALANCE LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)

EMCU500I REBALANCE LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU002I GPM command successful

3. QUERY TASKS to check the status:

While the REBALANCE task is in progress, the Rebalance task has “Executing” in the Status column.

F EMCSCF,GPM,QUERY TASKS LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)

EMCU500I QUERY TASKS LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU010I Tasks on Controller 0001956-00057 for Pool JCPTCKDPOOL2 API Ver: EMCU011I 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

When the REBALANCE task is complete, the Rebalance task has “Completed” in the Status column.

F EMCSCF,GPM,QUERY TASKS LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)

EMCU500I QUERY TASKS LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU010I Tasks on Controller 0001956-00057 for Pool JCPTCKDPOOL2 API Ver: EMCU011I 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

4. QUERY POOLS to check the status of the pool list.

In the example, pool JCPTCKDPOOL2 shows a 'Y' in the Reb column when the rebalancing operation is in progress:


EMCU500I QUERY POOLS LCL(UNIT(2101))EMCU010I Pools on Controller 0001956-00057 API Ver: 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 100 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 100 95 N DisabledEMCU012I MFFBABCV 0003 T Avail FBA FIBRE 15K 70 80 100 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 100 0 Y DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete



Pool JCPTCKDPOOL2 shows an 'N' in the Reb column when the rebalancing operation is complete:


EMCU500I QUERY POOLS LCL(UNIT(2101))EMCU010I Pools on Controller 0001956-00057 API Ver: 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 100 0 N DisabledEMCU012I MFCKD1 0002 T Avail 3390 SATA 7200 70 96 100 95 N DisabledEMCU012I MFFBABCV 0003 T Avail FBA FIBRE 15K 70 80 100 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 100 0 N DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

5. QUERY DATADEV to check the result:


EMCU500I QUERY DATADEV LCL(UNIT(2101)) POOL(JCPTCKDPOOL2)EMCU184I Data Devices on 0001956-00057 in Pool JCPTCKDPOOL2 API Ver: 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

6. The pool list display shows that the pool compression is being disabled:

F EMCSCF,GPM,QUERY POOLS LCL(UNIT(3A00))

EMCU500I QUERY POOLS LCL(UNIT(3A00)) EMCP001I GPM QUERY POOLS LCL(UNIT(3A00)) EMCU010I Pools on Controller 0001957-00086 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 70 80 100 32 N Ena=>DisEMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 70 80 100 1 N DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

7. Moments later, compression is now fully disabled for the pool:


EMCU500I QUERY POOLS LCL(UNIT(3A00)) EMCP001I GPM QUERY POOLS LCL(UNIT(3A00)) EMCU010I Pools on Controller 0001957-00086 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 70 80 100 32 N zDisabledEMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 70 80 100 1 N DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete



Compressing thin devices

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

Support for manual compression also allows configuration, management, and reporting on the compression state for thin devices.

Note: In addition to manual compression, automatic compression (keeping volumes compressed) can be obtained through use of Fully Automated Storage Tiering (FAST). EMC VMAX documentation describes FAST.

You can use manual compression, for example, to archive old user accounts, store and access end-of-period information (with the decompress-use-recompress cycle in the end of the period), or with data-at-rest.

Enabling compressionCompression is disabled by default.

You must first enable compression for the thin pool to reserve space and enable allocations, and only then can you actually compress a thin device in the pool.

To enable compression for a pool, use the COMPRESSION(ENABLE) parameter of the POOLATTR command, as described in “POOLATTR” on page 559.

Do not enable compression for a pool if there are active data devices with free space in the pool.

Once a pool is enabled for compression, a background process runs to reserve storage in the pool that is used to temporarily decompress data when the data is being accessed. No compression of allocations in this pool can occur until this process completes. 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.

The pool becomes fully enabled only after additional data devices are added and/or made active in the pool and there is enough room for the reserve space. When free space is made available, the pool will become fully enabled the next time Enginuity 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.



Compressing thin devicesA thin device can be manually compressed at any time. To compress data on one or more thin devices, use the COMPRESS command described in “COMPRESS” on page 534.

Note: Compression is not supported for thin devices bound using the BIND command with the PERSIST attribute, as described in “BIND” on page 532.

Compression is a background task that precludes other background tasks from running. Once the compression request is accepted, the thin device has 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.

When compressing a thin 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.

Zero reclaim

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, run the thin reclaim process against a thin device before compressing that device. Only TRU scratches deleted datasets, so TRU must be run for space reclamation.

Note: “Monitoring Space Reclamation (TRU Monitor)” on page 621 provides information on the thin reclaim process.

Compressing persistent allocations

Note: Persistent allocations are those having the PERSIST attribute. Such allocations can be created using the PERSIST parameter of the ALLOCATE command, as described in “ALLOCATE” on page 530.

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.



Compressing allocations in multiple pools

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 of the COMPRESS command described in “COMPRESS” on page 534 can be used to move all allocations for the thin device to the pool where the device is currently bound to before compressing those allocations. If this parameter is used, all allocations for the thin device reside in the bound pool after compression is complete.

Accessing compressed dataEnginuity allows data that is compressed to be both read and written.

Although compression does support reads and writes against an active workload, it affects the performance of the entire VMAX system. Use compression against very idle data only. Do not run medium or greater workloads against it.Do not use compression for processing low cost/low performance active data.

The data being read is temporarily decompressed into temporary storage that is reserved in the thin pool containing the compressed thin device allocations.

Note: You reserve this temporary storage by enabling compression for the pool using the COMPRESSION(ENABLE) parameter if the POOLATTR command, as described in “POOLATTR” on page 559.

Writes always write the decompressed allocations on the thin device. There is no automatic re-compression after a write.

With the exception an occasional backup to tape, it is best to fully decompress data before accessing it.

Decompressing thin devicesDecompression happens if you issue the DECOMPRESS command described in “DECOMPRESS” on page 539 against the thin device, or when the data is written to the device.

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 of the DECOMPRESS command can be used to move all allocations for the thin device to the pool where the thin device is currently bound to before decompressing those allocations. In this case, all allocations for the thin device reside in the bound pool after decompression is complete.



Disabling compressionWhen compression is no longer desired for allocations in a pool, the compression feature can be disabled.

Disabling compression for a pool deallocates the reserve space used for temporary decompression and prevents thin devices bound to the pool from being compressed.

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 described in “DECOMPRESS” on page 539. 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 data devices are made active, compression will become fully disabled for the pool the next time Enginuity 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.

Recommended command sequenceThe following is a suggested command sequence for integrating compression into your existing GPM 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 query).

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 query).

6. DISABLE data devices.

7. Remove data devices.

8. DELETE thin POOL.



Example1. Pool MFCKD1 is not enabled for compression:


EMCU500I QUERY POOLS LCL(UNIT(3A00)) EMCP001I GPM QUERY POOLS LCL(UNIT(3A00)) EMCU010I Pools on Controller 0001957-00086 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 70 80 100 31 N DisabledEMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 70 80 200 1 N DisabledEMCU012I 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: 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:

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3A00)) POOL(MFCKD1)

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

F EMCSCF,GPM,POOLATTR LCL(UNIT(3A00)) COMPRESSION(ENABLE) POOL(MFCKD1)

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 QUERY POOLS LCL(UNIT(3A00)) EMCP001I GPM QUERY POOLS LCL(UNIT(3A00)) EMCU010I Pools on Controller 0001957-00086 API Ver: EMCU011I Pool name Id Typ Stat Emul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MFCKD1 0001 T Avail 3390 FIBRE 10K 70 80 100 32 N EnabledEMCU012I MFTEST 0002 T Avail 3390 FIBRE 10K 70 80 200 1 N DisabledEMCU012I DF_DDEV_POOL 0100 T EMCU001I GPM command complete

6. Compress the thin devices bound to the pool:

F EMCSCF,GPM,COMPRESS LCL(UNIT(3A00)) POOL(MFCKD1) DEV(E30-E3F)

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 00000E30-00000E3F EMCU00AI Eligible devices EMCU00AI 00000E30-00000E3F EMCU00BI Completed devices EMCU00BI 00000E30-00000E3F 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: 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 data devices has gone down to 2%:



F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3A00)) POOL(MFCKD1) SUM

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:



10. DECOMPRESS the thin devices that were previously compressed:

F EMCSCF,GPM,DECOMPRESS LCL(UNIT(3A00)) POOL(MFCKD1) DEV(E30-E3F)

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 00000E30-00000E3F EMCU00AI Eligible devices EMCU00AI 00000E30-00000E3F EMCU00BI Completed devices EMCU00BI 00000E30-00000E3F EMCU002I GPM command successful



11. The thin devices are no longer indicated as 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: 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:





13. The pool shows a greater percent used now that the compressed thin devices have been decompressed:

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(3A00)) POOL(MFCKD1) SUM

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



14. Disable compression for the pool:

F EMCSCF,GPM,POOLATTR COMPRESS(DISABLE) LCL(UNIT(3A00)) POOL(MFCKD1)

EMCU500I POOLATTR COMPRESS(DISABLE) LCL(UNIT(3A00)) POOL(MFCKD1) EMCP001I GPM POOLATTR COMPRESS(DISABLE) LCL(UNIT(3A00)) POOL(MFCKD1) EMCU002I GPM command successful

Halting thin device tasks

You can halt thin device tasks that are currently running using the HALTTASK command described in “HALTTASK” on page 550.

HALTTASK stops a background task currently in progress for the specified thin devices. On the QUERY THINDEV display (obtained as described in “QUERY THINDEV” on page 573), 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.”

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.

For example, 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.



Pool-level alerts

For Enginuity 5876 and 5773, alerts are written to the z/OS console and EREP in the form of IEA480E and IEA499E operator messages if the percentage full for an oversubscribed pool exceeds a predefined alert threshold. User-defined thresholds can be set for individual pools using the POOLATTR command described in “POOLATTR” on page 559 with WARN and CRIT parameters.

In addition to the user-defined thresholds, alerts are also triggered when the following thresholds are exceeded: 80%, 90%, 95%, 96%, 97%, 98%, 99%, and when the pool reaches 100% full.

IEA499E messageThe IEA499E attention message indicates that the percentage full for the specified pool has exceeded a predefined threshold.

◆ The first item after the message ID indicates the z/OS device number (CUU) of the device where the notification was received.

◆ The second item indicates the volume serial of the device.

◆ The third item indicates the ID of the pool whose threshold was exceeded.

◆ The fourth item indicates the subsystem ID (SSID) containing the device where the notification was received.

The message also indicates the percentage capacity remaining in the pool. If the pool is full, the message indicates “REPOSITORY VOLUME CAPACITY EXHAUSTED.”

In the following example, pool with ID 0003 has exceeded a predefined threshold, is 96% full, and has 4% capacity remaining:

*IEA480E 3E82,SCU,SERIOUS ALERT,MT=2107,SER=0508-RGKHK, 615 REFCODE=2471-0003-0096,SENSE=00101000 823C8F00 11800000 03009614 084264A7 3E002471 05100200 F1000000

*IEA499E 3E80,MF3E80,0003,3E00,002107.921.EMC.08.0000000RGKHK, 610 REPOSITORY VOLUME WARNING: AT 04% CAPACITY REMAINING

IEA480E message, code 247CThe IEA480E Service Information Message (SIM) with reference code 247C represents environmental error 047C indicating that the specified SRP has inactive or Not Ready devices. The second part of the reference code indicates the pool ID. The third part indicates the VMAX device number of the inactive or Not Ready device

The severity of the IEA480E message is “ACUTE.” The IEA480E message is logged every 8 hours for as long as the device remains inactive or Not Ready. If another device is made inactive or Not Ready, the message is logged again immediately.

In the following example, VMAX device 0182 in pool 0005 is inactive or Not Ready :

*IEA480E 9128,SCU,ACUTE ALERT,MT=2107,SER=0508-ABWWA, 028 REFCODE=247C-0005-0182,SENSE=00101000 283C8F00 11C00000 01018214 081A060E 9100247C 05100200 F1000000



IEA480E message, code 2471The IEA480E Service Information Message (SIM) with reference code 2471 represents environmental error 0471 indicating that the percentage full for the specified pool has exceeded a predefined threshold. The second four digits of the reference code indicate the ID of the pool whose threshold was exceeded.

The severity of this message is “SERIOUS.” However, if the pool exceeds 98% full, the severity of the message changes to “ACUTE.”

Queries (HYPERMAX OS 5977 and higher)GPM queries provide information on storage pools, groups, and devices in your VMAX system.

GPM queries are made using the QUERY command with a keyword that represents the query type, such as SYMSG or THINDEV.

Storage Group Query

A Storage Group Query provides the following information for each storage group:

◆ Storage group name and ID

◆ Number of thin devices in the storage group

◆ Associated SRP, SLO, workload

◆ Whether the storage group is FAST-managed

◆ Emulation type: FBA, CKD, or “n/a” (if no devices are associated with the group)

◆ List of thin devices in the storage group

If no storage group or mask is specified, all groups are displayed.

You perform Storage Group Queries using the QUERY SYMSG command, as described in “QUERY SYMSG” on page 507.

Queries (HYPERMAX OS 5977 and higher) 455


Example

F EMCSCF,GPM,QUERY SYMSG LCL(UNIT(6401))

EMCU500I QUERY SYMSG LCL(UNIT(6401))EMCU200I Symmetrix Storage Groups on Controller 0001967-00257 API Ver: 8.00EMCU220I ----------------------------------------------------------------------- EMCU201I SG : KM_FBA2_3400 EMCU202I ID : 000A Device Count: 2 EMCU203I SRP : <none> FAST: N Emulation: FBA EMCU204I SLO : <none> Workload: <none> EMCU205I Devs : 00001782-00001783 EMCU220I ---------------------------------------------------------------------- EMCU201I SG : KM_CKD1_3400 EMCU202I ID : 000B Device Count: 2 EMCU203I SRP : SRP_1 (implied) FAST: Y Emulation: CKD EMCU204I SLO : Bronze Workload: <none> EMCU205I Devs : 000004C0-000004C1 eMCU220I ---------------------------------------------------------------------- EMCU201I SG : KM_EMPTY1_3400 EMCU202I ID : 000D Device Count: 0 EMCU203I SRP : SRP_1 FAST: Y Emulation: n/a EMCU204I SLO : Bronze Workload: <none> EMCU205I Devs : <none> EMCU220I ----------------------------------------------------------------------EMCU001I GPM command complete



Storage Group (SG) Performance Statistics Query

An SG Performance Statistics Query is used to calculate and display performance statistics for each storage group. Performance data is collected over a sample period. Once the sampling is complete, the report is displayed.

An SG Performance Statistics Query provides the following information for each storage group:

◆ Storage group name and ID

◆ Number of thin devices in the storage group

◆ Associated SRP, SLO, workload

◆ Whether the storage group is FAST-managed

◆ SRDF coordination state

◆ List of thin devices in the storage group

◆ Average response time

The average response time is a weighted average of the I/O time for all devices in the SG.

◆ Total number of read I/Os and total number of write I/Os

The I/O time starts when the VMAX receives the I/O and ends when the I/O completes and the status is sent back to the host. Only devices in the SG that receive I/O during the sample period will be involved in the calculation.

◆ Whether or not the SG is meeting its SLO, if applicable


You perform SG Performance Statistics Queries using the QUERY SYMSG command with the STATS parameter, as described in “QUERY SYMSG” on page 507.

Example

F EMCSCF,GPM,QUERY SYMSG STATS LCL(UNIT(6401))

EMCU500I QUERY SYMSG STATS LCL(UNIT(6401))EMCU985I Sampling performance data for 30 seconds EMCU200I Symmetrix Storage Groups on Controller 0001967-00257 API Ver: 8.00 EMCU220I -----------------------------------------------------------------------EMCU201I SG : DTSG1 EMCU202I ID : 0001 Device Count: 30 EMCU203I SRP : DEFAULT_SRP FAST: Y Emulation: FBAEMCU204I SLO : Diamond Workload: OLTP_REP EMCU221I Stats: Avg Resp (usec): 362 Reads : 211 EMCU222I SLO Met: Y Writes: 3140 EMCU205I Devs : 00000021-0000002F, 00000081-0000008F EMCU220I -----------------------------------------------------------------------EMCU001I GPM command complete



Storage Resource Pool Query

A Storage Resource Pool Query provides the following information for each storage resource pool:

◆ Storage resource pool name, ID, and description

◆ Whether the pool is the default SRP

◆ Whether the pool is the default SRP for CKD or FBA devices

◆ If SRP can be used for SRDF/A DSE and the maximum SRDF/A DSE capacity

◆ The SRP reserved capacity

In addition, the following track counts and percentages are shown, separately for CKD and FBA devices:

◆ Capacity

◆ Free tracks

◆ Allocated tracks

◆ Allocated tracks used by Snap

◆ allocated tracks used by spillover

◆ Percentage allocated

◆ Subscribed tracks

◆ Percentage subscribed

If no storage resource pool or mask is specified, all groups are displayed.

You perform Storage Resource Pool Queries using the QUERY SRP command, as described in “QUERY SRP” on page 506.

Example

F EMCSCF,GPM,QUERY SRP LCL(UNIT(6401))

EMCU500I QUERY SRP LCL(UNIT(6401)) EMCU206I Storage Resource Pools on Controller 0001967-00257 API Ver: 8.00 EMCU220I -----------------------------------------------------------------------------------------------EMCU207I SRP : DEFAULT_SRP EMCU208I ID : 0001 CKD Default: Y FBA Default: Y Resv Cap (%): 10 DSE: Y DSE Max Cap (GB): <none> EMCU209I Desc: <none> EMCU217I Emul Capacity (trk) Free (trk) Alc (trk) Snap (trk) DSE (trk) Alc (%) Sub (trk) Sub (%)EMCU218I ---- -------------- ---------- --------- ---------- --------- ------- --------- -------EMCU219I CKD 211.9M 211.9M 16695 0 0 1 74858490 36EMCU219I FBA 22430520 21920565 509955 0 0 3 10196025 46EMCU220I -----------------------------------------------------------------------------------------------EMCU001I GPM command complete



Service Level Objective Query

A Service Level Objective Query provides information about SLO/workload combinations.

If an SLO and/or workload is specified, only the matching SLO/workload combinations are displayed. If an SLO and/or workload is not specified, all SLO/workload combinations are displayed.

For each SLO/workload combination, the following information is provided:

◆ SLO name and ID

◆ SLO workload and description

◆ Approximate average response time

You perform Service Level Objective Queries using the QUERY SLO command, as described in “QUERY SLO” on page 504.

Example

F EMCSCF,GPM,QUERY SLO LCL(UNIT(6401))

EMCU500I QUERY SLO LCL(UNIT(6401)) EMCU210I Service Level Objectives on Controller 0001967-00257 API Ver: 8.00 EMCU220I

-----------------------------------------------------------------------------EMCU211I SLO : Optimized Workload: <none> EMCU212I ID : 0000 Approximate Average Response Time (usec): 78640 EMCU213I Desc: System will achieve optimal performance with available resources EMCU220I

-----------------------------------------------------------------------------EMCU211I SLO : Diamond Workload: OLTP EMCU212I ID : 0001 Approximate Average Response Time (usec): 840 EMCU213I Desc: Emulating EFD performance with small IO workloads similar to OLTP EMCU220I

-----------------------------------------------------------------------------EMCU211I SLO : Platinum Workload: OLTP EMCU212I ID : 0002 Approximate Average Response Time (usec): 3000 EMCU213I Desc: Emulating performance between 15K drive and EFD with small IO EMCU213I workloads similar to OLTP EMCU220I

-----------------------------------------------------------------------------EMCU211I SLO : Gold Workload: OLTP EMCU212I ID : 0003 Approximate Average Response Time (usec): 5040 EMCU213I Desc: Emulating 15K drive performance with small IO workloads similar to EMCU213I OLTP EMCU220I

-----------------------------------------------------------------------------EMCU211I SLO : Silver Workload: OLTP EMCU212I ID : 0004 Approximate Average Response Time (usec): 8040 EMCU213I Desc: Emulating 10K drive performance with small IO workloads similar to EMCU213I OLTP EMCU220I

-----------------------------------------------------------------------------EMCU211I SLO : Bronze Workload: OLTP EMCU212I ID : 0005 Approximate Average Response Time (usec): 14040 EMCU213I Desc: Emulating 7.2K drive performance with small IO workloads similar to EMCU213I OLTP EMCU220I

-----------------------------------------------------------------------------EMCU001I GPM command complete



Disk Group Query

A Disk Group Query provides information about disk groups.

If no disk group name or mask is specified, all disk groups are displayed.

For each disk group, the following information is provided:

◆ Disk group name and ID

◆ Name and description of the storage resource pool

◆ Drive class, speed, protection type, unformatted capacity

In addition, the following track counts and percentages are shown, separately for CKD and FBA devices:

◆ Capacity

◆ Free tracks

◆ Allocated tracks

◆ Allocated tracks used by Snap

◆ allocated tracks used by spillover

◆ Percentage allocated

You can filter the output by the storage resource pool.

You perform Disk Group Queries using the QUERY DISKGRP command, as described in “QUERY DISKGRP” on page 503.

Example

F EMCSCF,GPM,QUERY DISKGRP LCL(UNIT(6401))

EMCU500I QUERY DISKGRP LCL(UNIT(6401)) EMCU214I Disk Groups on Controller 0001967-00257 API Ver: 8.00 EMCU220I ------------------------------------------------------------------------------------EMCU215I Name: DISK_GROUP_001 SRP : DEFAULT_SRP EMCU216I ID : 0001 Class: FIBRE Speed: 10K Prot: RD1 Unformatted Capacity (GB): 600EMCU217I Emul Capacity (trk) Free (trk) Alc (trk) Snap (trk) DSE (trk) Alc (%) EMCU218I ---- -------------- ---------- --------- ---------- --------- ------- EMCU219I CKD 45204480 45204480 0 0 0 0 EMCU219I FBA 7691040 7691040 0 0 0 0 EMCU220I ------------------------------------------------------------------------------------EMCU215I Name: DISK_GROUP_002 SRP : DEFAULT_SRP EMCU216I ID : 0002 Class: SATA Speed: 7200 Prot: RD1 Unformatted Capacity (GB): 2000EMCU217I Emul Capacity (trk) Free (trk) Alc (trk) Snap (trk) DSE (trk) Alc (%) EMCU218I ---- -------------- ---------- --------- ---------- --------- ------- EMCU219I CKD 164.2M 164.2M 0 0 0 0 EMCU219I FBA 14364000 14364000 0 0 0 0 EMCU220I ------------------------------------------------------------------------------------EMCU215I Name: DISK_GROUP_003 SRP : DEFAULT_SRP EMCU216I ID : 0003 Class: FLASH Speed: FLASH Prot: RD1 Unformatted Capacity (GB): 200EMCU217I Emul Capacity (trk) Free (trk) Alc (trk) Snap (trk) DSE (trk) Alc (%) EMCU218I ---- -------------- ---------- --------- ---------- --------- ------- EMCU219I CKD 2574720 117720 2457000 0 0 96 EMCU219I FBA 375480 375480 0 0 0 0 EMCU220I ------------------------------------------------------------------------------------EMCU001I GPM command complete



Pool Query

A Pool Query lists all or only selected pools on the VMAX system. If an explicit pool name is specified, the body of the report includes a single line containing information about that pool.

A Pool Query report provides the following information:

◆ Pool name and ID

◆ Pool type and status

◆ Device emulation type, class, speed

◆ Used capacity (percentage)

◆ Total capacity (in tracks)

You perform Pool Queries using the QUERY POOLS command, as described in “QUERY POOLS” on page 504.

Example:


EMCU500I QUERY POOLS LCL(UNIT(6401)) EMCU010I Pools on Controller 0001967-00257 API Ver: 8.00EMCU011I Pool name Id Typ Stat Emul Class Speed %-Used Capacity EMCU012I DG1_CKD_PL 0001 T Avail 3390 FIBRE 10K 0 45204480 EMCU012I DG1_FBA_PL 0002 T Avail FBA FIBRE 10K 0 7691040 EMCU012I DG2_CKD_PL 0003 T Avail 3390 SATA 7200 0 164.2M EMCU012I DG2_FBA_PL 0004 T Avail FBA SATA 7200 0 14364000 EMCU012I DG3_CKD_PL 0005 T Avail 3390 FLASH FLASH 3 2574720 EMCU012I DG3_FBA_PL 0006 T Avail FBA FLASH FLASH 0 375480 EMCU001I GPM command complete



Thin Device Query

A Thin Device Query provides information on thin devices.

You can display detailed information for each of the devices or summary statistics.

For each device, the following information is provided:

◆ VMAX device number and CUU

◆ Device emulation type

◆ Volser

◆ Whether the device is Ready

◆ Whether the device is space-efficient

◆ Number of cylinders

◆ Type

◆ Task

◆ Task status

◆ The name of the storage resource pool

You can filter the output using the following criteria:

◆ Storage group

◆ Service Level Objective

◆ Workload

◆ Storage Resource Pool

◆ Device type (CKD or FBA)

You perform Thin Device Queries using the QUERY THINDEV command, as described in “QUERY THINDEV” on page 510.

The information is output in EMCU108I and EMCU110I messages. The message fields are described in the Mainframe Enablers Message Guide.



Example

F EMCSCF,GPM,QUERY THINDEV SYMSG(DTSG2) LCL(UNIT(6401))

EMCU500I QUERY THINDEV SYMSG(DTSG2) LCL(UNIT(6401)) EMCU184I Thin Devices on 0001967-00257 Matching SYMSG DTSG2 EMCU108I Device# CUU Emul Volser Rdy S/E Cyls Typ Task Status SRP Name EMCU110I 00000021 6411 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000022 6412 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000023 6413 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000024 6414 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000025 6415 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000026 6416 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000027 6417 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000028 6418 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000029 6419 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000002A 641A 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000002B 641B 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000002C 641C 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000002D 641D 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000002E 641E 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000002F 641F 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000071 6461 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000072 6462 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000073 6463 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000074 6464 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000075 6465 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000076 6466 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000077 6467 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000078 6468 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 00000079 6469 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000007A 646A 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000007B 646B 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000007C 646C 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000007D 646D 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000007E 646E 3390 ****** Y N 1113 DEFAULT_SRPEMCU110I 0000007F 646F 3390 ****** Y N 1113 DEFAULT_SRPEMCU071I Device Totals: CKD Bound: 30 Unbound: 0 FBA Bound: 0 Unbound: 0 EMCU071I Track Totals: CKD Bound: 500850 Unbound: 0 FBA Bound: 0 Unbound: 0 EMCU001I GPM command complete



Thin Device Allocations Query

The Thin Device Allocations Query provides information on track allocations for thin devices. It shows the total number of allocations and other totals for the requested thin devices.



◆ Number of allocated tracks

◆ Used capacity

◆ Number of shared data device tracks backing the device

◆ Whether device allocations are persistent



◆ Storage group


You perform Thin Device Allocations Queries using the QUERY ALLOC command, as described in “QUERY ALLOC” on page 496.

The information is output in EMCU060I, EMCU014I, and EMCU015I messages. Message fields are described in Mainframe Enablers Message Guide.

Example

F EMCSCF,GPM,QUERY ALLOC DEV(3F0-400) LCL(UNIT(6401))

EMCU500I QUERY ALLOC DEV(3F0-400) LCL(UNIT(6401))EMCU060I Thin Allocations on 0001967-00257 API Ver: 8.00EMCU014I Device# Alloc Used Shared Persist SRP Name EMCU015I 000003F0 0 0 0 N DEFAULT_SRP EMCU015I 000003F1 49182 0 0 Y DEFAULT_SRP EMCU015I 000003F2 49182 0 0 Y DEFAULT_SRP EMCU015I 000003F3 90 0 0 N DEFAULT_SRP EMCU015I 000003F4 90 0 0 N DEFAULT_SRP EMCU015I 000003F5 90 0 0 N DEFAULT_SRP EMCU015I 000003F6 90 0 0 N DEFAULT_SRP EMCU015I 000003F7 90 0 0 N DEFAULT_SRP EMCU015I 000003F8 90 0 0 N DEFAULT_SRP EMCU015I 000003F9 90 0 0 N DEFAULT_SRP EMCU015I 000003FA 90 0 0 N DEFAULT_SRP EMCU015I 000003FB 90 0 0 N DEFAULT_SRP EMCU015I 000003FC 90 0 0 N DEFAULT_SRP EMCU015I 000003FD 90 0 0 N DEFAULT_SRP EMCU015I 000003FE 90 0 0 N DEFAULT_SRP EMCU015I 000003FF 90 0 0 N DEFAULT_SRP EMCU015I 00000400 90 0 0 N DEFAULT_SRP EMCU001I GPM command complete



Thin Device Allocations by Pool Query

The Thin Device Allocations by Pool Query provides information on data device allocations backing the requested thin device(s) by thin pool. You can use the Thin Device Allocations by Pool Query to see exactly in what thin pool thin device allocations reside.


◆ Number of allocations

◆ Thin pool name


◆ Storage group

◆ Workload

◆ Service Level Objective

◆ Thin pool

You perform Thin Device Allocations by Pool Queries using the QUERY ALLALLOCS command, as described in “QUERY ALLALLOCS” on page 498.

The information is output in EMCU060I, EMCU014I, and EMCU015I messages. Message fields are described in the Mainframe Enablers Message Guide.

Example

F EMCSCF,GPM,QUERY ALLALLOCS LCL(UNIT(6401))

EMCU500I QUERY ALLALLOCS LCL(UNIT(6401))EMCU060I Thin Allocations on 0001967-00257 EMCU014I Device# Alloc Pool EMCU015I 00000613 30576 DG1_FBA_PLEMCU015I 00000613 31041 DG3_FBA_PLEMCU015I 00000615 38558 DG1_FBA_PLEMCU015I 00000615 39282 DG3_FBA_PLEMCU015I 00000616 52321 DG1_FBA_PLEMCU015I 00000616 51092 DG3_FBA_PLEMCU001I GPM command complete



Data Device Query

A Data Device Query provides information on data devices that are eligible to be added to a pool. You can display detailed information for each of the devices or summary statistics.




◆ Used capacity

◆ Free capacity

◆ Pool name

◆ The ID of the disk group

◆ Device class and speed

◆ Device RAID type

◆ Whether the device pool is active or inactive



◆ Storage group


◆ Disk group

◆ Device type (CKD or FBA)

You perform Data Device Queries using the QUERY DATADEV command, as described in “QUERY DATADEV” on page 500.

The information is output in EMCU061I and EMCU063I messages. Message fields are described in Mainframe Enablers Message Guide.



Example

F EMCSCF,GPM,QUERY DATADEV DEV(1FF2C-1FF3B) LCL(UNIT(6401))

EMCU500I QUERY DATADEV DEV(1FF2C-1FF3B) LCL(UNIT(6401)) EMCU184I Data Devices on 0001967-00257 EMCU061I Device# Emul Used Free Pool Name DGID Class Speed Prot A/I SRP Name EMCU063I 0001FF2C FBA 43104 50766 DG3_FBA_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF2D FBA 81518 12352 DG3_FBA_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF2E 3390 16049 198511 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF2F 3390 10948 203612 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF30 3390 16888 197672 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF31 3390 16026 198534 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF32 3390 33825 180735 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF33 3390 16803 197757 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF34 FBA 84239 9631 DG3_FBA_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF35 3390 10915 203645 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF36 3390 16852 197708 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF37 3390 16003 198557 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF38 FBA 42016 51854 DG3_FBA_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF39 3390 16789 197771 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF3A 3390 15957 198603 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU063I 0001FF3B 3390 10933 203627 DG3_CKD_PL 0003 FLASH FLASH RD1 A DEFAULT_SRPEMCU064I Totals: EMCU064I 3390: 197988 used tracks, 2376732 free tracks, 8% used EMCU064I FBA : 250877 used tracks, 124603 free tracks, 67% used EMCU064I Act : 448865 used tracks, 2501335 free tracks, 16% used EMCU001I GPM command complete



Queries (Enginuity 5876 and 5773)GPM queries provide information on storage tiers, pools, and devices in your VMAX system. GPM queries are made using the QUERY command with a keyword that represents the query type, such as TASKS or THINDEV.

FAST Tier Query

A FAST Tier Query provides information about storage tiers on the VMAX system. You perform FAST Tier Queries using the QUERY TIERS command, as described in “QUERY TIERS” on page 572.

Pool Query

A Pool Query lists all or only selected pools on the VMAX system. If an explicit pool name is specified, the body of the report includes a single line containing information about that pool.

A Pool Query report provides the following information:

◆ Pool name and ID

◆ Pool type and status

◆ Device emulation type, class, speed

◆ Number of alarms

◆ Maximum oversubscription rate

◆ Actual oversubscription rate

◆ Used capacity (percentage)

◆ Rebalancing status

◆ Compression state

You perform Pool Queries using the QUERY POOLS command, as described in “QUERY POOLS” on page 568.

Example


EMCU500I QUERY POOLS LCL(UNIT(5201))EMCU010I Pools on Controller 0001949-01172 API Ver: 8.00EMCU011I Pool name zzzId zzTyp zStat zEmul Class Speed Alarms MaxO ActO %-Used Reb CompressEMCU012I DEFAULT_POOL 0000 SEMCU012I MSFCKD1 zzzzz0001 T zzzAvail 3390 FIBRE 15K zz70 zzzz95 zz134 z91 zzzzN zzDisabledEMCU012I MFBCV zzzzzzz0002 T zzzAvail 3390 FIBRE 15Kzz 70 zzzz100 z101 z99 zzzzN zzDisabledEMCU012I DTTHINPOOL1z 0003 T zzzAvail 3390 FIBRE 15K zz25 zzzz99 zz100z 97 zzzzN zzDisabledEMCU012I MFBCVR5 zzzzz0004 T zzzAvail 3390 FIBRE 15K zz70 zzzz80 zz45 zz8zzzzzzN zzDisabledEMCU001I GPM command complete



Pool Device Query

A Pool Device Query displays both data devices and save devices.

If the pool name is omitted, all data devices and save devices on the VMAX system are displayed whether in the default pool or in an assigned pool.

If the pool name is specified, data devices and save devices on the VMAX system are displayed only if assigned to the specified pool or to a pool matching the specified pool name mask.

You perform Pool Device Queries using the QUERY POOLDEV command, as described in “QUERY POOLDEV” on page 566.

The information is output in EMCU061I and EMCU063I messages. Message fields are described in the Mainframe Enablers Message Guide.

Thin Device Query

A Thin Device Query provides information on thin devices.

If the pool name is omitted, all thin devices on the VMAX system are displayed within the device range, whether or not bound to any pool.

If the pool name is specified, bound thin devices on the VMAX system are displayed within the device range, 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.


◆ VMAX device number and CUU


◆ Volser

◆ The pool to which the device is bound

◆ Whether the device is Ready

◆ Whether the device is space-efficient

◆ Number of cylinders

◆ Type

◆ Com

◆ Task

◆ Task status


You perform Thin Device Queries using the QUERY THINDEV command, as described in “QUERY THINDEV” on page 573.


Queries (Enginuity 5876 and 5773) 469


Following 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 thin device is bound (or *Unbound* ).

F EMCSCF,GPM,QUERY THINDEV LCL(UNIT(2101))

EMCU500I QUERY THINDEV LCL(UNIT(2101)) EMCU184I Thin Devices on 0001956-00057 API Ver: EMCU108I Device# CUU Emul Volser Bound To Rdy S/E Cyls Typ Com Task Status EMCU110I 00000028 2100 3390 ****** MSFSTD N N 1113 SS N Bind Done EMCU110I 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 Done EMCU110I 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 N EMCU110I 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

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.

F EMCSCF,GPM,QUERY THINDEV DEV(0090-0093) LCL(UNIT(2101))

EMCU500I QUERY THINDEV DEV(0090-0093) LCL(UNIT(2101)) EMCU184I Thin Devices on 0001956-00057 API Ver: EMCU108I 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 thin devices bound to the specified pool. The pool name is included in the report header and is not shown in the report device lines.

F EMCSCF,GPM,QUERY THINDEV LCL(UNIT(2101)) POOL(DTTHINPOOL1)

EMCU500I QUERY THINDEV LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU184I Thin Devices on 0001956-00057 Bound to Pool DTTHINPOOL1 API Ver: EMCU108I 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.

F EMCSCF,GPM,QUERY THINDEV DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1)

EMCU500I QUERY THINDEV DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU184I Thin Devices on 0001956-00057 Bound to Pool DTTHINPOOL1 API Ver: EMCU108I 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



Thin Device Allocations Query

The Thin Device Allocations Query provides information on track allocations for thin devices. It shows the total number of allocations and other totals for the requested thin devices. You can limit the output to the required pool.



◆ Number of allocated tracks

◆ Used capacity

◆ Shared

◆ Count of persistent tracks

◆ Number of tracks saved by compression

◆ The bound pool

You perform Thin Device Allocations Queries using the QUERY ALLOC command, as described in “QUERY ALLOC” on page 562.


The following examples illustrate the use 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 VMAX system. The name of the pool to which a thin device is bound is shown on the device detail line.

F EMCSCF,GPM,QUERY ALLOC LCL(UNIT(2101))

EMCU500I QUERY ALLOC LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I 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



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 thin device is bound is shown on the device detail line.

F EMCSCF,GPM,QUERY ALLOC DEV(0090-00DF) LCL(UNIT(2101))

EMCU500I QUERY ALLOC DEV(0090-00DF) LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I 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

Example 3

When an explicit thin pool name is specified and no device range is specified, the display includes all thin devices bound to the specified pool. The pool name is included in the report header and is not shown in the report device lines.

F EMCSCF,GPM,QUERY ALLOC LCL(UNIT(2101)) POOL(DTTHINPOOL1)

EMCU500I QUERY ALLOC LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I 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

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.

F EMCSCF,GPM,QUERY ALLOC DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1)

EMCU500I QUERY ALLOC DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I 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



Thin Device Allocations by Pool Query

The Thin Device Allocations by Pool Query provides information on data device allocations backing the requested thin device(s) by pool. You can use the Thin device allocations by pool query to see exactly in what pool thin device allocations reside. You can limit the output to the required pool name. You perform Thin Device Allocations by Pool Queries using the QUERY ALLALLOCS command, as described in “QUERY ALLALLOCS” on page 498.


The following examples illustrate use of the QUERY ALLALLOCS command.

Example 1

When no pool name or device range is specified, the display includes all bound thin devices on the VMAX. 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.

Example 1

F EMCSCF,GPM,QUERY ALLALLOCS LCL(UNIT(2101))

EMCU500I QUERY ALLALLOCS LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I 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 EMCU001I GPM command complete



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.

F EMCSCF,GPM,QUERY ALLALLOCS DEV(0090-00DF) LCL(UNIT(2101))

EMCU500I QUERY ALLALLOCS DEV(0090-00DF) LCL(UNIT(2101)) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I 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

Example 3

When an explicit thin pool name is specified and no device range is specified, the display includes all thin 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.

F EMCSCF,GPM,QUERY ALLALLOCS LCL(UNIT(2101)) POOL(DTTHINPOOL1)

EMCU500I QUERY ALLALLOCS LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I Device Alloc Compress EMCU015I 00000090 16788 16260 EMCU015I 00000091 16788 16260 EMCU015I 00000092 120 108 EMCU015I 00000093 120 0 EMCU001I GPM command complete

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.

F EMCSCF,GPM,QUERY ALLALLOCS DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1)

EMCU500I QUERY ALLALLOCS DEV(0091-0093) LCL(UNIT(2101)) POOL(DTTHINPOOL1) EMCU060I Thin Allocations on 0001956-00057 API Ver: EMCU014I Device Alloc Compress EMCU015I 00000091 16788 16260 EMCU015I 00000092 120 108 EMCU015I 00000093 120 0 EMCU001I GPM command complete



Data Device Query

A Data Device Query provides information on data devices that are eligible to be added (via the ADD POOL command, as described in “ADD POOL” on page 528) to a thin pool.

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 data device is assigned.

If a pool name is specified, data devices on the VMAX system are displayed only if assigned to the specified pool or to a pool matching the specified pool name mask.




◆ Used capacity

◆ Free capacity

◆ Pool name and type

◆ Device class and speed

◆ Device RAID type

◆ Whether the device pool is active or inactive

◆ Status

You perform Data Device Queries using the QUERY DATADEV command, as described in “QUERY DATADEV” on page 500.


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

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(2101))

EMCU500I QUERY DATADEV LCL(UNIT(2101))EMCU184I Data Devices on 0001956-00057 API Ver: EMCU061I 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 a device range is specified, the display includes only data devices in the specified device range.

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(5500)) DEV(FE4-FEB)

EMCU500I QUERY DATADEV LCL(UNIT(5500)) DEV(FE4-FEB)EMCU060I Data Devices on 0001926-04124 API Ver EMCU061I 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

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.

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(5500)) POOL(J*)

EMCU500I QUERY DATADEV LCL(UNIT(5500)) POOL(J*)EMCU060I Data Devices on 0001926-04124 API Ver EMCU061I 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 data 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, 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 data device is shown as well.

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(5500)) POOL(MSFCKD1)

EMCU500I QUERY DATADEV LCL(UNIT(5500)) POOL(MSFCKD1)EMCU184I Data Devices on 0001926-04124 in Pool MSFCKD1 API Ver EMCU061I 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 data device is not ready (for example, user not ready, device not ready, and so on). The application that made the data device not ready must be used to make the device ready again.

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 data device is shown as well. If a device range is specified, devices are listed only if within the specified device range and in the specified thin pool.

F EMCSCF,GPM,QUERY DATADEV LCL(UNIT(5500)) POOL(MSFCKD1) DEV(FEA-FEB)

EMCU500I QUERY DATADEV LCL(UNIT(5500)) POOL(MSFCKD1) DEV(FEA-FEB)EMCU184I Data Devices on 0001926-04124 in Pool MSFCKD1 API Ver EMCU061I 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% usedEMCU001I GPM command complete



Save Device Query

A Save Device Query provides information on save devices that are eligible to be added (via the ADD POOL command, as described in “ADD POOL” on page 528) to a DSE or Snap pool.

If the pool name is omitted, all save devices on the VMAX system are displayed whether in the default pool or in an assigned pool.

If the pool name is specified, save devices on the VMAX system are displayed only if assigned to the specified pool or to a pool matching the specified pool name mask.

You perform Save Device Queries using the QUERY SAVEDEV command, as described in “QUERY SAVEDEV” on page 569.


Here are four examples, two of QUERY SAVEDEV when no explicit pool name is specified, one where a pool name mask is specified, and one where the name is specified.

Example 1

When no pool name is specified, all save devices are displayed.

F EMCSCF,GPM,QUERY SAVEDEV LOCAL(UNIT(5500))

EMCU500I QUERY SAVEDEV LOCAL(UNIT(5500))EMCU060I Save Devices on 0001926-04124 API Ver EMCU061I 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.

F EMCSCF,GPM,QUERY SAVEDEV LOCAL(UNIT(5500)) DEV(1218-1220)

EMCU500I QUERY SAVEDEV LOCAL(UNIT(5500)) DEV(1218-1220)EMCU060I Save Devices on 0001926-04124 API Ver EMCU061I 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

Example 3

When a pool name mask is specified with an optional device ranges specified, save devices are included only if in a pool matching the mask and within the specified device range.

F EMCSCF,GPM,QUERY SAVEDEV LOCAL(UNIT(9000)) POOL(MSF*) DEV(5E2-5EA)

EMCU500I QUERY SAVEDEV LOCAL(UNIT(9000)) POOL(MSF*) DEV(5E2-5EA)EMCU060I Save Devices on 0001926-02840 API Ver EMCU061I 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 a device range is specified, only save devices within the specified device range are included in the display.

F EMCSCF,GPM,QUERY SAVEDEV LCL(UNIT(9000)) POOL(MSFUTDSNAP1) DEV(5E2-5EA)

EMCU500I QUERY SAVEDEV LCL(UNIT(9000)) POOL(MSFUTDSNAP1) DEV(5E2-5EA)EMCU184I Save Devices on 0001926-02840 in Pool MSFUTDSNAP1 API Ver EMCU061I 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



Rebalance Task Query

A Rebalance Task Query provides information regarding certain active thin provisioning background tasks running on the VMAX system, for example, rebalancing.

If a pool name is specified, only tasks for the specified pool are displayed.

You perform Rebalance Task Queries using the QUERY TASKS command, as described in “QUERY TASKS” on page 571.

The information is output in EMCU010I and EMCU011I messages. Message fields are described in Mainframe Enablers Message Guide.

The QUERY TASKS display wraps around so the most current task may not necessarily be at the bottom of the list. The task with the highest task ID in the Task column is the most current.

Here are three examples, one of QUERY TASKS when no explicit pool name is specified one when a pool name mask is specified and one when the name is specified.

Example 1

When no pool name is specified, the display includes all background tasks on the VMAX system.

F EMCSCF,GPM,QUERY TASKS LCL(UNIT(1000))

Tasks on Controller 0001926-05093 API Ver: Task 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

Example 2

When a pool name mask is specified, the display includes all background tasks on the VMAX system whose target pool name matches the mask.

F EMCSCF,GPM,QUERY TASKS LCL(UNIT(1000)) POOL(SHARE_ITCFK)

Tasks on Controller 0001926-05093 for Pool SHARE_ITCFK API Ver: Task 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.

F EMCSCF,GPM,QUERY TASKS LCL(UNIT(1000)) POOL(SHARE*)

Tasks on Controller 0001926-05093 API Ver: Task 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



Report field summary

Table 20 provides a summary of the QUERY display fields depending on the query type.

Table 20 QUERY display field descriptions (page 1 of 5)

Field Description Query type

Header

Serial number The serial number of the VMAX 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 SCF that was accessed to obtain device information.

ALLOC, DATADEV, SAVEDEV, POOLDEV, THINDEV, TASKS

Detail line columns

Device# VMAX device number of the device described on the detail line.

DATADEV, SAVEDEV, POOLDEV, ALLOC, ALLALLOCS

CUU z/OS device number or **** if device not mapped to MVS CUU. THINDEV

Task The hexadecimal task identifier. TASKS

Emul Device emulation: 380, 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 the 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



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





Detail line columns for THINIDEV 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 — SRDF R11 deviceR21 — SRDF R21 deviceR22 — SRDF 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





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.

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


Free tracks Total unallocated tracks on devices listed.







%-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 (HYPERMAX OS 5977 and higher)

Syntax conventionsRefer to “Syntax conventions” on page 186.

Common parametersCoNTRoLler(SymmID)

Optional. The VMAX system identified by its serial number. Use this parameter to verify that the correct system is reached through the SRDF group path.

You can specify either a 5-digit or 12-digit 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 VMAX systems have the same last 5 digits. Leading zeros are not required.


DDNAME(ddname)

The DD statement that refers to the gatekeeper.

Note: When DDNAME is specified, you cannot use UNIT or VOLume.

DEBUG

Enables debugging mode.

IMPORTANT

Use DEBUG only under direction of EMC technical support.

The debugging information is written to the module-specific DDs DBUGPMBT, DBUGPMCM, DBUGPMSD, and DBUGPMSS.

Note: To generate diagnostics for a specific command only, use this parameter and do not specify PARM=DEBUG in the batch JCL EXEC statement.

DEV({symdv#|range|list})The devices identified by their VMAX device numbers.


LoCaL


NOEXEC

Checks command syntax without executing the command.

If the syntax is correct, the command completes successfully. If a syntax error is found, the command fails.



PATH(hoplist)

The path to the VMAX system represented by up to eight SRDF groups separated by periods, for example: nn.nn.nn.nn.

ReMoTe


SKIPSkips ineligible devices rather than terminating the action.

VOLume(volser)

The gatekeeper identified by the volser.

Note: When VOLume is specified, you can also specify UNIT, but not DDNAME.

UNIT(device)

The gatekeeper identified by its device number.

Note: When UNIT is specified, you can also specify VOLume, but not DDNAME.

ADD SYMSG

Adds thin devices to a storage group.

Note: “Storage groups” on page 410 describes storage groups. Note that a storage group may contain a maximum of 4096 devices in total.

SyntaxADD SYMSG(sg_name)

{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

DEV({symdv#|range|list})

[DEBUG]

[NOEXEC]

[SKIP]

ParametersCoNTRoLler(SymmID)

See “CoNTRoLler(SymmID)” on page 488.

DDNAME(ddname)

See “DDNAME(ddname)” on page 488.

DEBUG

See “DEBUG” on page 488.

Command reference (HYPERMAX OS 5977 and higher) 489



See “DEV({symdv#|range|list})” on page 488.

LoCal

See “LoCaL” on page 488.

NOEXEC

See “NOEXEC” on page 488.

PATH(hoplist)

See “PATH(hoplist)” on page 489.

ReMoTe

See “ReMoTe” on page 489.

SKIP

See “SKIP” on page 489.

SYMSG(sg_name)

The name of the storage group.

The name can be up to 64 characters long and may include uppercase alphabetic characters, numbers, underscores (_), and hyphens (-). The first and last characters must be alphanumeric. If the name includes any hyphens, enclose it in apostrophes.

VOLume(volser)

See “VOLume(volser)” on page 489.

UNIT(device)

See “UNIT(device)” on page 489.

Causes of failureADD SYMSG fails when:

◆ A valid storage group name is not specified (in the SYMSG parameter).

◆ A storage group with the specified name does not exist on the VMAX system.

◆ A valid VMAX device number, range of VMAX device numbers, or list of VMAX device numbers is not specified (in the DEV parameter).

◆ A valid gatekeeper is not specified (in the LoCaL or ReMoTe parameter).

◆ Validation fails for a device, and SKIP is not specified.

ADD SYMSG fails for a device when:

◆ The specified storage group is FAST-managed, and the device is already in another storage group that is FAST-managed.

◆ The specified storage group is FAST-managed and contains FBA devices, and the device is CKD.

◆ The specified storage group is FAST-managed and contains CKD devices, and the device is FBA.

◆ The specified storage group is FAST-managed, and the device is encapsulated.]

◆ The specified storage group is FAST-managed, has an SLO other than DIAMOND, BRONZE, or OPTIMIZED (or the equivalent customized SLO name) and the device is CKD.



ALLOCATE

Refer to “ALLOCATE” on page 530.

Under HYPERMAX OS 5977 and higher, the POOL parameter is not applicable.

CREATE SYMSG

Creates a storage group.

Note: “Storage groups” on page 410 describes storage groups.

In addition, you can add thin devices to the group, associate it with an SRP, SLO, and workload. Note that a storage group may contain a maximum of 4096 devices in total.

Syntax

CREATE SYMSG(sg_name)


[DEBUG]

[DEV({symdv#|range|list})]

[NOEXEC]

[SKIP]

[SLO({slo_name|NONE}]

[SRP({srp_name|NONE})]

[WorkLoad({workload_name|NONE})]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCal


NOEXEC




PATH(hoplist)


ReMoTe


SKIP


SLO({slo_name|NONE})

The name of the service level objective (SLO) to be associated with the storage group upon creation.

Note: “Service level objectives” on page 411 describes SLOs.


The name can be up to 32 characters long. The name may include uppercase alphabetic characters, numbers, underscores (_), and hyphens (-). The first and last characters must be alphanumeric. If the name includes any hyphens, enclose it in apostrophes.

NONE indicates that the storage group should not be explicitly associated with any SLO or workload. This is the default and need not be specified.

SRP({srp_name|NONE})

The name of the storage resource pool (SRP) to be associated with the storage group upon creation.

Note: “Storage resource pools” on page 410 describes SRPs.



NONE indicates that the storage group should not be explicitly associated with any SRP. This is the default and need not be specified.

SYMSG(sg_name)

The name of the storage group to be created.


VOLume(volser)




UNIT(device)


WorkLoad({workload_name|NONE})

Associates workload with the storage group.

Note: “Workload” on page 412 describes workloads.

This parameter is only valid when the SLO parameter is specified.

NONE

(Default) Associates no specific workload with the storage group.

workload_name

Associates the specified workload with the storage group.


Causes of failureCREATE SYMSG fails when:


◆ The specified storage group name does not adhere to requirements.

◆ A storage group with the specified name already exists on the VMAX system.


◆ The specified SRP does not exist.

◆ The specified SLO does not exist.

◆ The specified workload does not exist.

◆ The WorkLoad parameter is specified without the SLO parameter.

CREATE SYMSG fails for a device when:

◆ The specified storage group is FAST-managed (that is, the SRP and/or SLO parameter is specified), and the device is already in another storage group that is FAST-managed.

◆ The specified storage group is FAST-managed (that is, the SRP and/or SLO parameter is specified), and the device is encapsulated.



DELETE SYMSG

Deletes a storage group.


Syntax

DELETE SYMSG(sg_name)


[DEBUG]

[NOEXEC]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCal


NOEXEC


PATH(hoplist)


ReMoTe


SYMSG(sg_name)

The name of the storage group to be deleted.


VOLume(volser)


UNIT(device)




Causes of failureDELETE SYMSG fails when:

◆ A valid SG name is not specified (in the SYMSG parameter).

◆ An SG with the specified name does not exist on the VMAX system.


HALTTASK

Refer to “HALTTASK” on page 550.

HELP

Displays a list of available GPM commands or provides help information for the GPM command specified as the parameter.

Syntax

HELP [gpm_command]

Parameters

gpm_command

One of the following GPM commands:

• ADD SYMSG• ALLOCATE• CREATE SYMSG• DELETE SYMSG• HALTTASK• HELP• PERSIST OFF• QUERY ALLOC• QUERY ALLALLOCS• QUERY DATADEV• QUERY DISKGRP• QUERY POOLDEV• QUERY POOLS• QUERY SAVEDEV• QUERY SLO• QUERY SRP• QUERY THINDEV• REMOVE SYMSG• RENAME POOL• RENAME SLO• RENAME SYMSG• USR_NRDY• USR_RDY

ExampleHELP QUERY SRP



PERSIST OFF

Refer to “PERSIST OFF” on page 557.

Under HYPERMAX OS 5977 and higher, the POOL parameter is not applicable.

QUERY ALLOC

Displays information about the pool allocations, including the total number of allocations and other totals for the requested thin device.

Note: “Queries (Enginuity 5876 and 5773)” on page 468 describes the Thin Device Allocations Query.

Syntax

QUERY ALLOC{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]


[NOEXEC]

[SLO(slo_name)]

[SRP(srp_name)]

[SYMSG(sg_name)]

[WorkLoad(workload_name)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCal


NOEXEC


PATH(hoplist)




ReMoTe


SLO(slo_name)

The name of the Service Level Objective (SLO) to filter the displayed information by SLO.


Alternatively, you can specify a mask.

The SLO parameter is only valid when the SYMSG parameter is specified. SYMSG(*) can be used in conjunction with the SLO parameter to filter by devices in any storage group associated with the specified SLO.

SRP(srp_name)

The name of the Storage Resource Pool (SRP) for which associated thin devices are displayed.



SYMSG(sg_name)

The name of the storage group (SG) in which thin devices are displayed.



VOLume(volser)


UNIT(device)


WorkLoad(workload_name)

The name of the workload to filter the displayed information by workload.





The WorkLoad parameter is only valid when the SYMSG parameter is specified. SYMSG(*) can be used in conjunction with the WorkLoad parameter to filter by devices in any storage group associated with the specified workload.

Causes of failureQUERY ALLOC fails when:


◆ The specified device or range of devices does not exist on the VMAX system.

◆ A storage group name is specified that does not exist on the VMAX system.

◆ A Storage Resource Pool name is specified that does not exist on the VMAX system.

◆ A SLO name is specified that does not exist on the VMAX system.

◆ A workload name is specified that does not exist on the VMAX system.

QUERY ALLALLOCS

Displays data device allocations backing the requested thin devices by thin pool, showing exactly in what thin pool thin device allocations reside.

Note: “Thin Device Allocations by Pool Query” on page 465 describes the Thin Device Allocations by Pool Query.

Syntax

QUERY ALLALLOCS{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SLO(slo_name)]

[SYMSG(sg_name)]


Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCal


NOEXEC


PATH(hoplist)


POOL(poolname)

The thin pool for which allocations are displayed.

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.

Note: EMC recommends that the pool name does not contain embedded spaces to facilitate use of the poolname by different features of ResourcePak Base.


ReMoTe


SLO(slo_name)

The name of the Service Level Objective (SLO) to filter the displayed information by SLO.




SYMSG(sg_name)




VOLume(volser)


UNIT(device)









Causes of failureQUERY ALLALLOCS fails when:



◆ The specified thin pool cannot be found.




QUERY DATADEV

Displays information about data devices.

Note: “Data Device Query” on page 466 describes the Data Device Query.

Syntax

QUERY DATADEV{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[{CKD|FBA}]

[DEBUG]


[DISKGRP(disk_group_name)]

[NOEXEC]

[POOL(poolname)]

[SRP(srp_name)]

[SUMMARY]



Parameters

CKD|FBA

Determines the type of devices to display, CKD or FBA. When a type is specified, summary data is generated only for devices of that type, if any.

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




DISKGRP(disk_group_name)

The name of the disk group in which the data devices are displayed.

If the name includes any hyphens, enclose it in apostrophes.


LoCal


NOEXEC


PATH(hoplist)


POOL(poolname)

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.

ReMoTe


SRP(srp_name)

The name of the storage resource pool (SRP) in which data devices are displayed.





SUMMARY

Displays aggregate counts of free and allocated tracks and the percentage of tracks used for each emulation type having a non-zero aggregate count. Device detail lines are omitted.


VOLume(volser)


UNIT(device)


Causes of failureQUERY DATADEV fails when:





QUERY DISKGRP

Displays information about the disk group.

If no disk group or mask is specified, all disk groups are displayed.

Note: “Disk Group Query” on page 460 describes the Disk Group Query.

Syntax

QUERY DISKGRP{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[DISKGRP(disk_group_name)]

[NOEXEC]

[SRP(srp_name)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


DISKGRP(disk_group_name)

The name of the disk group to be displayed.



LoCal


NOEXEC


PATH(hoplist)


ReMoTe


SRP(srp_name)

The name of the storage resource pool (SRP) for which disk groups are displayed.





VOLume(volser)


UNIT(device)


Causes of failureQUERY DISKGRP fails when:

◆ The specified disk group name (in the DISKGRP parameter) does not exist on the VMAX system.

◆ The specified storage resource pool name (in the SRP parameter) does not exist on the VMAX system.

◆ A valid gatekeeper is not specified (in the LoCaL or ReMoTE parameter).

QUERY POOLDEV

Equivalent to the QUERY DATADEV command, since save devices are no longer used under HYPERMAX OS 5977 and higher. Refer to “QUERY DATADEV” on page 565.

QUERY POOLS

Refer to “QUERY POOLS” on page 568.

QUERY SAVEDEV

As there are no save devices in HYPERMAX OS 5977 and higher, the QUERY SAVEDEV command is automatically converted to a QUERY DATADEV command with the EMCU629I message displayed. Refer to “QUERY DATADEV” on page 500.

QUERY SLO

Displays information about the service level objective (SLO).

If an SLO and/or workload is specified, only the matching SLO/workload combinations are displayed.

If an SLO and/or workload is not specified, all SLO/workload combinations are displayed that are available on the VMAX system. If the required drive types are not present, those SLOs will be excluded from the QUERY SLO output but will be displayed if explicitly requested via the SLO filter.

Note: “Service Level Objective Query” on page 459 describes the Service Level Objective Query.



Syntax

QUERY SLO{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[NOEXEC]

[SLO(slo_name)]


Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCal


NOEXEC


PATH(hoplist)


ReMoTe


SLO(slo_name)

The name of the service level objective (SLO) to be displayed.



VOLume(volser)


UNIT(device)









Causes of failureQUERY SLO fails when:

◆ The specified SLO name (in the SLO parameter) does not exist on the VMAX system.


QUERY SRP

Displays information about the storage resource pool (SRP).

If no storage resource pool or mask is specified, all pools are displayed.

Note: “Storage Resource Pool Query” on page 458 describes the Storage Resource Pool Query.

Syntax

QUERY SRP{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[NOEXEC]

[SRP(srp_name)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCal


NOEXEC


PATH(hoplist)




ReMoTe


SRP(srp_name)

The name of the storage resource pool (SRP) to be displayed.



VOLume(volser)


UNIT(device)


Causes of failureQUERY SRP fails when:

◆ The specified storage resource pool name (in the SRP parameter) does not exist on the VMAX system.


QUERY SYMSG

Displays information about the storage group.


Note: “Storage Group Query” on page 455 describes the Storage Group Query. “Storage Group (SG) Performance Statistics Query” on page 457 describes the SG Performance Statistics Query.

Syntax

QUERY SYMSG{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[DEV({device|range|list})]

[NOEXEC]

[SLO(slo_name)]

[SRP(srp_name)]



[STATS[(sample_time)]]

[SYMSG(sg_name)]


Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


DEV({device|range|list})

Displays only those storage groups that contain the specified devices.

You can specify a VMAX device number, a range of VMAX device numbers separated by a dash, or a list of VMAX device numbers and/or ranges separated by commas.

LoCal


NOEXEC


PATH(hoplist)


ReMoTe


SLO(slo_name)

The name of the service level objective (SLO) to filter the displayed information by SLO.



SRP(srp_name)

The name of the storage resource pool (SRP) to filter the displayed information by SRP.





[STATS[(sample_time)]]

Produces the SG Performance Statistics Query report described in “Storage Group (SG) Performance Statistics Query” on page 457.

sample_time

Sets the sample time (in seconds) for collection of performance statistics. Valid values are from 1 to 3600 seconds (1 hour). The default value is 30 seconds.

SYMSG(sg_name)

The name of the storage group (SG) to be displayed.



VOLume(volser)


UNIT(device)






Causes of failureQUERY SYMSG fails when:

◆ The specified storage group name (in the SYMSG parameter) does not exist on the VMAX system.

◆ The STATS parameter is specified with a sample time that is not within the range of valid values.




QUERY THINDEV

Displays information about thin devices.

Note: “Thin Device Query” on page 462 describes the Thin Device Query.

Syntax

QUERY THINDEV{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[{CKD|FBA}]

[DEBUG]


[NOEXEC]

[SLO(slo_name)]

[SRP(srp_name)]

[SUMMARY]

[SYMSG(sg_name)]


Parameters

CKD|FBA

Determines the type of devices to display, CKD or FBA. When a type is specified, summary data is generated only for devices of that type (if any).

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCal


NOEXEC


PATH(hoplist)




ReMoTe


SLO(slo_name)

The name of the service level objective (SLO) to filter the displayed information by SLO.




SRP(srp_name)

The name of the Storage Resource Pool (SRP) for which associated thin devices are displayed.



SUMMARY

Displays device totals and track totals for bound CKD devices, unbound CKD devices, bound FBA devices, and unbound FBA devices. Device detail lines are omitted.


SYMSG(sg_name)




VOLume(volser)


UNIT(device)









Causes of failureQUERY THINDEV fails when:




◆ A Storage Resource Pool name is specified that does not exist on the VMAX system.





REMOVE SYMSG

Removes thin devices from a storage group.


Syntax

REMOVE SYMSG(sg_name){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[SKIP]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCal


NOEXEC


PATH(hoplist)


ReMoTe


SKIP


SYMSG(sg_name)

The name of the storage group (SG) from which the thin devices are removed.




VOLume(volser)


UNIT(device)


Causes of failureREMOVE SYMSG fails when:



◆ A valid VMAX device number, range of VMAX device numbers, or list of VMAX device numbers is not specified (in the DEV parameter).


◆ Validation fails for a device, and SKIP is not specified.

REMOVE SYMSG fails for a device when:

◆ The device is not in the specified storage group.

RENAME POOL

Refer to “RENAME POOL” on page 580.

RENAME SLO

Assigns a new external name to an SLO.

Note: “Customizing SLO names” on page 412 provides information about base and customized SLO names.

Syntax

RENAME SLO(base_slo_name)


NEWSLONAME(new_SLO_name|BASENAME)

[DEBUG]

[NOEXEC]

Parameters

BASENAME

Reverts the SLO to its base name.

CoNTRoLler(SymmID)




DDNAME(ddname)


DEBUG


LoCal


NEWSLONAME(new_slo_name)

The new name to be assigned to the SLO.

SLO names can be up to 32 characters long. The name may include uppercase alphabetic characters, numbers, underscores (_), and hyphens (-). The first and last characters must be alphanumeric. If the name includes any hyphens, it must be enclosed in apostrophes.

NOEXEC


PATH(hoplist)


ReMoTe


SLO(base_slo_name)

The base name of the SLO to be renamed. You can choose one of the following:

• DIAMOND

• PLATINUM

• GOLD

• SILVER

• BRONZE

• OPTIMIZED

Note: SLO identification is made via the inherent base name of the SLO (for example, DIAMOND, GOLD, and so on), regardless of whether the SLO had previously been renamed.

If the name includes any hyphens, it must be enclosed in apostrophes.

VOLume(volser)


UNIT(device)




Causes of failureRENAME SLO fails completely when:

◆ A valid SLO base name is not specified (in the SLO parameter).

◆ An SLO with the existing base name does not exist on the VMAX system.

◆ A valid new SLO name is not specified (in the NEWSLONAME parameter).

◆ The specified new SLO name does not adhere to requirements.

◆ An SLO with the new name specified already exists on the VMAX system.


RENAME SYMSG

Renames a storage group.


Syntax

RENAME SYMSG(sg_name){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

NEWSGNAME(newname)

[DEBUG]

[NOEXEC]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCal


NEWSGNAME(newname)

The new name to be assigned to the storage group.


NOEXEC




PATH(hoplist)


ReMoTe


SYMSG(sg_name)

The name of the existing storage group (SG) to be renamed.


VOLume(volser)


UNIT(device)


Causes of failureRENAME SYMSG fails when:

◆ A valid existing storage group name is not specified (in the SYMSG parameter).

◆ A storage group with the name specified does not exist on the VMAX system.

◆ A valid new storage group name is not specified (in the NEWSGNAME parameter).

◆ The specified new storage group name does not adhere to requirements.

◆ A storage group with the new name specified already exists on the VMAX system.




SET SRP

Enables or disables SRDF/A DSE and sets the SRP reserved capacity and the maximum SRDF/A DSE capacity for a storage resource pool (SRP).


Syntax

SET SRP(srp_name){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[DSE_MAX_CAP({n|NOLIMIT})]

[NOEXEC]

[RDFA_DSE({ENABLE|DISABLE})]

[RESV_CAP(nn)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


DSE_MAX_CAP({n|NOLIMIT})

The maximum SRDF/A DSE capacity.

Note: “Maximum SRDF/A DSE capacity” on page 411 describes the maximum SRDF/A DSE capacity.

Valid values are from 1 to 100000 gigabytes, or “NOLIMIT.” The default value is “NOLIMIT.”

LoCal


NOEXEC


PATH(hoplist)


ReMoTe




RESV_CAP(nn)

The SRP reserved capacity.

Note: “SRP reserved capacity” on page 410 describes the SRP reserved capacity.

Valid values are from 1 to 80%. The default value is 10%.

RDFA_DSE({ENABLE|DISABLE})

Allows or prohibits use of the storage resource pool for SRDF/A DSE.

Note: “SRDF/A DSE-enabled SRP” on page 410 describes enabling/disabling DSE for an SRP.

SRP(srp_name)

The name of the storage resource pool (SRP) whose attributes are set.


VOLume(volser)


UNIT(device)


Causes of failureSET SRP fails when:

◆ A valid SRP name is not specified (in the SRP parameter).

◆ An SRP with the specified name does not exist on the VMAX system.


◆ The specified SRP reserved capacity is not within the range of valid values.

◆ The specified maximum SRDF/A DSE capacity is not within the range of valid values.

◆ The maximum SRDF/A DSE capacity is specified, but the SRP is not enabled for DSE.

◆ You attempt to disable SRDF/A DSE for an SRP when there is only one SRP on the VMAX system.



SET SYMSG

Sets attributes for an existing storage group.


The attributes include:

◆ Associated Storage Resource Pool (SRP)

◆ Associated Service Level Objective (SLO)

◆ Associated workload

Syntax

SET SYMSG(sg_name){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[NOEXEC]

[SLO({slo_name|NONE})]

[SRP({srp_name|NONE})]

[WorkLoad({workload_name|NONE})]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCal


NOEXEC


PATH(hoplist)


ReMoTe


SLO({slo_name|NONE})

The name of the Service Level Objective (SLO) to be associated with the storage group.



Note: “Service level objectives” on page 411 describes SLOs.



NONE indicates that the storage group should not be explicitly associated with any SLO or workload. This can be used to remove the association with an SLO and workload if previously associated. If the SLO parameter is not specified, the associated SLO and workload will remain unchanged.

SRP({srp_name|NONE})

The name of the Storage Resource Pool (SRP) to be associated with the storage group.




NONE indicates that the storage group should not be explicitly associated with any SRP. This can be used to remove the association with an SRP if one was previously associated. If the SRP parameter is not specified, the associated SRP will remain unchanged.

SYMSG(sg_name)

The name of the storage group (SG) whose attributes are set.


VOLume(volser)


UNIT(device)


WorkLoad({workload_name|NONE})

Associates workload with the storage group.

Note: “Workload” on page 412 describes workloads.




NONE

(Default) Associates no specific workload with the storage group.

workload_name

Associates the specified workload with the storage group.


Causes of failureSET SYMSG fails when:




◆ The specified SRP does not exist.

◆ The specified SLO does not exist.

◆ The specified workload does not exist.

◆ The WorkLoad parameter is specified without the SLO parameter.

USR_NRDY

Refer to “USR_NRDY” on page 584.

Sets the Not Ready status for the thin device. This allows a thin device to be unbound.

Note: This action corresponds to the SC VOL USR_NRDY action of SRDF Host Component, as described in the SRDF Host Component for z/OS Product Guide.

Syntax

USR_NRDY{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOCHKO]

[NOEXEC]

[SKIP]

[VERBOSE]

Parameters

CoNTRoLler(SymmID)




DEBUG


DEV({symdv#|range|list}


DDNAME(ddname)


LoCaL


NOEXEC


PATH(hoplist)


NOCHKO

Enables processing of devices with online paths. Otherwise such devices are considered ineligible for the action.

ReMoTe


SKIP


VERBOSE

See “VERBOSE” on page 527.

VOLume(volser)


UNIT(device)


Causes of failureUSR_NRDY fails when:

◆ The USR_NRDY validation fails for a device and SKIP has not been specified.


◆ A valid device or range of devices is not specified (in the DEV parameter).

USR_NRDY fails for a device if:

◆ The device is not a thin bound device.

◆ The device is an FBA meta member whose head device is not in the specified device range.

◆ The device is online to any host.



USR_RDY

Sets the Ready status for the thin device. This allows a bound thin device to be set active.

Note: This action corresponds to the SC VOL USR_RDY action of SRDF Host Component, as described in the SRDF Host Component for z/OS Product Guide.

Syntax

USR_RDY{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[SKIP]

Parameters

CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NOEXEC


PATH(hoplist)


ReMoTe


SKIP


VOLume(volser)


UNIT(device)




Causes of failureUSR_RDY fails when:

◆ The USR_RDY validation fails for a device and SKIP has not been specified.



USR_RDY fails for a device if:





Command reference (Enginuity 5876 and 5773)

Syntax conventions


Common parameters

CoNTRoLler(SymmID)

Optional. The VMAX system identified by its serial number. Use this parameter to verify that the correct system is reached through the SRDF group path.

You can specify either a 5-digit or 12-digit 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 VMAX systems have the same last 5 digits. Leading zeros are not required.


DDNAME(ddname)

The DD statement that refers to the gatekeeper.

Note: When DDNAME is specified, you cannot use UNIT or VOLume.

DEBUG

Enables debugging mode.

IMPORTANT

Use DEBUG only under direction of EMC technical support.

The debugging information is written to the module-specific DDs DBUGPMBT, DBUGPMCM, DBUGPMSD, and DBUGPMSS.

Note: To generate diagnostics for a specific command only, use this parameter and do not specify PARM=DEBUG in the batch JCL EXEC statement.

DEV({symdv#|range|list})The devices identified by their VMAX device numbers.


LoCaL


NOEXEC

Checks command syntax without executing the command.

If the syntax is correct, the command completes successfully. If a syntax error is found, the command fails.



PATH(hoplist)

The path to the VMAX system represented by up to eight SRDF groups separated by periods, for example: nn.nn.nn.nn.

ReMoTe


SKIPSkips ineligible devices rather than terminating the action.

VERBOSE

Enables verbose messaging for the command being executed.

Verbose 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. This parameter must be specified on all commands, where verbose messaging is desired, and does not affect the outcome of the commands when it is specified.

This parameter must be specified on all commands where verbose messaging is desired.

VOLume(volser)

The gatekeeper identified by the volser.

Note: When VOLume is specified, you can also specify UNIT, but not DDNAME.

UNIT(device)

The gatekeeper identified by its device number.

Note: When UNIT is specified, you can also specify VOLume, but not DDNAME.

WAIT[(waittime[,{WARN|ERROR}])]

Waits until all VMAX 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 VMAX 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, verify the completion of the task(s) using the appropriate QUERY command:

• QUERY THINDEV for thin device status

• QUERY DATADEV for data device status

• QUERY SAVEDEV for save device status

• QUERY POOLS for pool status

If neither WARN nor ERROR is specified and an explicit wait value is specified, the default is ERROR. If neither WARN nor ERROR is specified and no explicit wait value is specified, the default is WARN.

Command reference (Enginuity 5876 and 5773) 527


waittime

Optionally allows the maximum wait time to be overridden. This is 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.

WARN

Displays a warning message and ends the command with RC=4, if one or more tasks takes longer than the maximum wait time to complete.

ERROR

Displays an error message and ends the command with RC=8, if one or more tasks takes longer than the maximum wait time to complete.

ADD POOL

Adds data or save devices to a pool.

Note: “Adding/removing devices” on page 433 describes adding data or save devices to pools.

Syntax

ADD POOL(poolname){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[ACTIVE]

[DEBUG]

[NOEXEC]

[SKIP]

Parameters

ACTIVESets the state of data or save devices being added to the pool as eligible to be assigned allocated tracks.

If not specified, the data or save 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 using the ENABLE command.

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG






LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool to which the data or save devices are added.



ReMoTe


SKIP


VOLume(volser)


UNIT(device)


Causes of failureADD POOL fails when:

◆ The specified pool cannot be found.

◆ A valid pool name is not specified (in the POOL parameter).



◆ The specified pool is empty and devices in the specified device range have conflicting emulation.

◆ ADD POOL validation fails for a device and SKIP has not been specified.

ADD POOL fails 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.



ALLOCATE

Allocates physical tracks to thin devices.

Note: “Allocating/reallocating tracks” on page 437 describes track allocation.

Without using ALLOCATE, physical tracks are allocated on data devices only when data is written to the thin device.

Syntax

ALLOCATE


POOL(poolname)


[DEBUG]

[NOEXEC]

[PERSIST]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)




PERSIST

Assigns the persistent attribute to the allocated tracks.

Note: “Persistent allocation” on page 437 describes persistent allocations.

POOL(poolname)

The pool in which the tracks for the specified thin devices are to be allocated.



ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)



See “WAIT[(waittime[,{WARN|ERROR}])]” on page 527.

Causes of failureALLOCATE fails when:



◆ A valid gatekeeper is not specified (in the LOCAL or REMOTE parameter).


◆ 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 fails 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 metadata.)

◆ The specified pool does not have any devices assigned and active.


BIND

Binds thin devices to a thin pool.

Note: “Binding/unbinding thin devices” on page 434 describes binding of thin devices.

BIND


POOL(poolname)


[DEBUG]

[NOEXEC]

[PERSIST]

[PREALLOC]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC




PATH(hoplist)


PERSIST

Assigns the persistent attribute to the allocated tracks.


POOL(poolname)

The pool to which the thin devices are to be bound.



PREALLOC

Indicates that physical tracks are to be allocated when binding is performed to back all logical (thin device) tracks on each thin 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.

ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)






Causes of failureBIND fails when:







◆ BIND validation fails for a device and SKIP has not been specified.

BIND fails for a device when:


◆ The device 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 5876) of the pool to exceed the maximum oversubscription rate of the pool set the by the user.

COMPRESS

Compresses data on one or more thin devices.

Note: “Compressing thin devices” on page 444 describes thin device compression.

IMPORTANT

This command requires Enginuity 5876.

Syntax

COMPRESS


POOL(poolname)


[DEBUG]

[NOEXEC]

[MOVE]

[SKIP]



[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


MOVE

Moves all allocations for the thin device to the pool where the thin device is currently bound to before compressing those allocations. This means that all allocations for the thin device reside in the bound pool after compression is complete.

Note: By default, if a thin device containing allocations in multiple pools is compressed, all allocations are compressed in the pools where they reside.

NOEXEC


PATH(hoplist)


POOL(poolname)

The pool to which the thin devices are bound.



SKIP


ReMoTe




VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureCOMPRESS fails when:







◆ Compression is not enabled for the specified pool.

◆ Validation for COMPRESS fails for a device and SKIP has not been specified.

COMPRESS fails for a device when:


◆ The device is not bound to the specified pool.

◆ The data devices that contain the allocated tracks are not active.




CREATE POOL

Creates a new pool.

Note: “Creating/deleting pools” on page 420 describes creating new pools.

Syntax

CREATE POOL(poolname)


TYPE({THINPOOL|DSEPOOL|SNAPPOOL})

[DEBUG]

[MAXOsub({max_ovrsubrate|NONE})]

[NOEXEC]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCaL


MAXOsub({max_ovrsubrate|NONE})

Sets the maximum oversubscription rate for all thin devices bound to the pool.


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. If set to zero, all BIND, REBIND, MOVE (with REBIND option), DRAIN, and DISABLE requests fail.

max_ovrsubrate

Specify the value from 0 to 65534.

NONE

Indicates that no maximum exists. This is the default value and need not be specified.

NOEXEC




PATH(hoplist)


POOL(poolname)

The name of the pool to be created.



ReMoTe


TYPE({SNAPPOOL|DSEPOOL|THINPOOL})

The type of the pool to be created.

Valid values are SNAPPOOL, DSEPOOL, or THINPOOL.

VOLume(volser)


UNIT(device)


Causes of failureCREATE POOL fails when:

◆ The specified pool name does not adhere to pool name requirements.

◆ A pool of the same name already exists on the VMAX system.



◆ A valid pool type is not specified (in the TYPE parameter).

◆ The maximum number of pools already exists on the VMAX system.

◆ The request specifies TYPE(THINPOOL) and the maximum number of pools of type THINPOOL already exist on the VMAX 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 VMAX system.



DECOMPRESS

Decompresses data on one or more thin devices.

Note: “Decompressing thin devices” on page 446 describes decompression of thin devices.

Syntax

DECOMPRESS


POOL(poolname)


[DEBUG]

[NOEXEC]

[MOVE]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


MOVE

Moves all allocations for the thin device to the pool where the thin device is currently bound to before decompressing those allocations. This means that all allocations for the thin device reside in the bound pool after decompression is complete.

Note: By default, if a thin device containing allocations in multiple pools is decompressed, all allocations are decompressed in the pools where they reside.



NOEXEC


PATH(hoplist)


POOL(poolname)




ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureDECOMPRESS fails when:

◆ A valid gatekeeper is not specified (in the LoCaL or ReMoTE parameter).






◆ Compression is not enabled for the specified pool.

◆ Validation for DECOMPRESS fails for a device and SKIP has not been specified.



DECOMPRESS fails for a device when:





DELETE POOL

Removes a pool from the VMAX system.

Note: To be eligible for deletion, a pool must be empty.

Syntax

DELETE POOL(poolname)


[DEBUG]

[NOEXEC]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The name of the pool to be deleted.





ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureDELETE POOL fails when:


◆ The specified pool is not empty.



DISABLE

Disables data or save devices in the pool.

Note: “Enabling/disabling data or save devices” on page 433 describes disabling of data or save devices.

Syntax

DISABLE{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)


[DEBUG]

[NOEXEC]

[SKIP]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)




DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool in which the specified data or save devices are to be disabled.



ReMoTe


SKIP


VOLume(volser)


UNIT(device)


Causes of failureDISABLE fails 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 fails 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 5876) of the pool to exceed the maximum oversubscription rate of the pool set the by the user.

DISPLAY

Displays pool information.

IMPORTANT

EMC suggests that DISPLAY is not used. To view pools, use the QUERY POOLS command described in “QUERY POOLS” on page 568. To view devices, use device type-specific QUERY commands, such as “QUERY DATADEV” on page 565 for data devices, “QUERY SAVEDEV” on page 569 for save devices, and “QUERY THINDEV” on page 573 for thin devices.

When no pool name or 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.

Note: A mask consists of a string whose final character is an asterisk. A pool name matches the mask when the initial characters of the pool name match the characters of the mask preceding the asterisk.

If a specific pool is named, the command displays the data or save devices in the pool. An optional device range may be specified to limit the display of devices in the pool.

Syntax

DISPLAY{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[ACTIVE]

[DEBUG]

[NOEXEC]



[POOL(poolname)]

[TYPE({SNAPPOOL|DSEPOOL|THINPOOL})]

Parameters

ACTIVE

This parameter is only meaningful when an explicit pool name is specified, and the data or save devices in the pool are active. If it is not specified, all data or save devices in the pool are listed.

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The name of the pool for which to display information.




ReMoTe


TYPE({SNAPPOOL|DSEPOOL|THINPOOL})

Determines the pool type.

Valid values are SNAPPOOL, DSEPOOL, or THINPOOL.



VOLume(volser)


UNIT(device)


Causes of failureDISPLAY fails when a valid gatekeeper is not specified (in the LoCaL or ReMoTe parameter).

DRAIN

Initiates the draining process for data or save devices in the pool.

Note: “Draining data or save devices” on page 439 describes the draining process.

Syntax

DRAIN{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)


[DEBUG]

[NOEXEC]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC




PATH(hoplist)


POOL(poolname)

The pool where the data or save devices to be drained reside.



ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureDRAIN fails when:




DRAIN fails 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 5876) of the pool would exceed the maximum oversubscription rate of the pool set the by the user.

ENABLEEnables data or save devices in the pool.

Note: “Enabling/disabling data or save devices” on page 433 describes enabling of data or save devices.

SyntaxENABLE


POOL(poolname)DEV({symdv#|range|list})[DEBUG][NOEXEC][SKIP]



DDNAME(ddname)


DEBUG




LoCaL




NOEXEC


PATH(hoplist)


POOL(poolname)

The pool in which data or save devices to be enabled reside.



ReMoTe


SKIP


VOLume(volser)


UNIT(device)


Causes for failureENABLE fails when:

◆ The ENABLE validation fails for a device and SKIP has not been specified.




ENABLE fails 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.



HALTTASK

Stops a background task currently in progress for the specified thin devices.

Note: “Halting thin device tasks” on page 453 describes halting of thin device tasks.

SyntaxHALTTASK



[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SKIP]

[VERBOSE]

[WAIT]



DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool where the task is halted.





ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureHALTTASK fails when:

◆ A valid gatekeeper is not specified (in the local or remote parameter).

◆ A valid device or range of devices is not specified (in the DEV parameter.)




◆ Validation for HALTTASK fails for a device and SKIP has not been specified.

HALTTASK fails for a device when:





HDRAINHalts the draining process.

Note: “Draining data or save devices” on page 439 describes the draining process.

SyntaxHDRAIN


POOL(poolname)


[DEBUG]

[NOEXEC]

[SKIP]

[VERBOSE]

[WAIT]



DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool where draining is halted.





ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureHDRAIN fails when:





◆ The HDRAIN validation fails for a device and SKIP has not been specified.

HDRAIN fails 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).



HELP

Displays a list of available GPM commands or provides help information for the GPM command specified as the parameter.

Syntax

HELP [gpm_command]

Parameters

gpm_command

One of the following GPM commands:

• ADD POOL• ALLOCATE• BIND• COMPRESS• CREATE POOL• DECOMPRESS• DELETE POOL• DISABLE• DRAIN• ENABLE• HALTTASK• HDRAIN• HELP• MOVE• PERSIST OFF• POOLATTR• QUERY ALLOC• QUERY ALLALLOCS• QUERY DATADEV• QUERY POOLDEV• QUERY POOLS• QUERY SAVEDEV• QUERY TASKS• QUERY TIERS• QUERY THINDEV• REBALANCE• REMOVE POOL• RENAME POOL• UNBIND• USR_NRDY• USR_RDY

ExampleHELP RENAME POOL



MOVE

Moves existing allocations for the thin devices from the source pool to the target pool.

Note: “Moving allocations” on page 437 describes moving of allocations.

Syntax

MOVE{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)


SOURCEPOOL(poolname)

[DEBUG]

[NOEXEC]

[REBIND]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool to which the thin devices are currently bound and from which allocations are moved.





REBIND

Indicates that the thin devices are first rebound to the target pool before the existing allocations are moved from the source pool 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.

ReMoTe


SKIP


SOURCEPOOL(poolname)

Identifies the source pool where the thin devices were previously bound, and from where the allocations are moved.

VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureMOVE fails when:

◆ The specified pool is not found.

◆ A valid target pool name is not specified (in the POOL parameter).

◆ A valid source pool name is not specified (in the SRCPOOL parameter).







◆ The MOVE validation fails for a device and SKIP has not been specified.

MOVE fails 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.

PERSIST OFF

Clears the persistent attribute from all tracks allocated for the specified thin devices.


Syntax

PERSIST OFF{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)


[DEBUG]

[NOEXEC]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC




PATH(hoplist)


POOL(poolname)

The pool that contains the tracks for the specified thin devices for which the persistent attribute is to be removed.



ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failurePERSIST OFF fails if:







◆ PERSIST OFF validation fails for a device and SKIP has not been specified.

PERSIST OFF fails for a device if:






POOLATTR

Sets attributes for an existing pool. The attributes include:

◆ The thresholds to trigger critical and warning alerts. “Pool alerts” on page 422 describes pool alerts.

◆ The maximum oversubscription rate. “Oversubscription rate” on page 422 describes the oversubscription rate.

◆ The compression state. “Compressing thin devices” on page 444 describes pool compression.

Syntax

POOOLATTR{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)

[COMPRESSION(ENABLE|DISABLE)]

[CRIT(critical-value)]

[DEBUG]

[MAXOsub({max_ovrsubrate|NONE})]

[NOEXEC]

[VERBOSE]

[WARN(warning-value)]

Parameters

COMPRESSION(ENABLE|DISABLE)

Enables or disables compression for the pool.

Note: “Compressing thin devices” on page 444 describes compression.

• ENABLE – Enables thin device compression for the pool and reserves space for decompression, as described in “Enabling compression” on page 444. Note that ENABLE does not actually perform compression.

• DISABLE – Disables thin device compression for the pool, as described in “Disabling compression” on page 447. This is the default value.

CoNTRoLler(SymmID)


CRIT(critical-value)

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

DEBUG


DDNAME(ddname)


LoCaL


MAXOsub({max_ovrsubrate|NONE})

Sets the maximum oversubscription rate for all thin devices bound to the pool.


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. If set to zero, all BIND, REBIND, MOVE (with REBIND option), DRAIN, and DISABLE requests fail.

max_ovrsubrate

Specify the value from 0 to 65534.

NONE

Indicates that no maximum exists. This is the default value.

NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which the specified attributes are set.



ReMoTe




VERBOSE


VOLume(volser)


UNIT(device)


WARN(warning-value)

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

Causes of failurePOOLATTR fails when:


◆ A valid pool name is not specified (in the POOL parameter.)


◆ Both critical and warning threshold values are specified 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 specified, no warning threshold value is specified, and the value specified for the critical threshold does not exceed the current warning threshold value.

◆ A warning threshold value is specified, no critical threshold value is specified, 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 65534.

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



QUERY ALLOC

Displays information about the pool allocations, including the total number of allocations and other totals for the requested thin device.

Note: “Rebalance Task Query” on page 482 describes the Thin Device Allocations Query.

Syntax

QUERY ALLOC{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[POOL(poolname)]

Parameters

CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which allocations are displayed.






ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureQUERY ALLOC fails when:




QUERY ALLALLOCS

Displays data device allocations backing the requested thin devices by pool, showing exactly in what pool thin device allocations reside.

Note: “Thin Device Allocations by Pool Query” on page 475 describes the Thin Device Allocations by Pool Query.

Syntax

QUERY ALLALLOCS{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[POOL(poolname)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG






LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which allocations are displayed.




ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureQUERY ALLALLOCS fails when:






QUERY DATADEV

Displays information about data devices.

Note: “Data Device Query” on page 477 describes the Data Device Query.

Syntax

QUERY DATADEV{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[{CKD|FBA}]

[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SUMMARY]

Parameters

CKD|FBA


CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which data devices are displayed.






ReMoTe


SUMMARY



VOLume(volser)


UNIT(device)


Causes of failureQUERY DATADEV fails when:




QUERY POOLDEV

Displays information about data or save devices in the pool.

Note: “Pool Device Query” on page 469 describes the Pool Device Query.

Syntax

QUERY POOLDEV{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}




[{CKD|FBA}]

[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SUMMARY]

Parameters

CKD|FBA


CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which data or save devices are displayed.




ReMoTe


SUMMARY

Displays device totals and track totals. Device detail lines are omitted.




VOLume(volser)


UNIT(device)


Causes of failureQUERY POOLDEV fails when:




QUERY POOLS

Displays information about the pool status.

Note: “Pool Query” on page 468 describes the Pool Query.

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.

Syntax

QUERY POOLS{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[DEBUG]

[NOEXEC]

[POOL(poolname)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which information is displayed.




ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureQUERY POOLS fails when:



QUERY SAVEDEV

Displays information about save devices.

Note: “Save Device Query” on page 480 describes the Save Device Query.

Syntax

QUERY SAVEDEV{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[{CKD|FBA}]



[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SUMMARY]

Parameters

CKD|FBA


CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which save devices are displayed.




ReMoTe


SUMMARY





VOLume(volser)


UNIT(device)


Causes of failureQUERY SAVEDEV fails when:




QUERY TASKS

Displays information about active thin provisioning background tasks running on the VMAX system.

Note: “Rebalance Task Query” on page 482 describes the Rebalance Task Query.

Syntax

QUERY TASKS{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[NOEXEC]

[POOL(poolname)]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


LoCaL


NOEXEC


PATH(hoplist)




POOL(poolname)

The pool for which tasks are displayed.




ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureQUERY TASKS fails when:



QUERY TIERS

Displays information about FAST storage tiers.

Note: “FAST Tier Query” on page 468 describes the FAST Tier Query.

Syntax

QUERY TIERS{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

[NOEXEC]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


LoCaL




NOEXEC


PATH(hoplist)


ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureQUERY TIERS fails when:


QUERY THINDEV

Displays information about thin devices.

Note: “Thin Device Query” on page 469 describes the Thin Device Query.

Syntax

QUERY THINDEV{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[BOUND]

[{CKD|FBA}]

[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SUMMARY]

[UNBOUND]

Parameters

BOUND

When this keyword is specified, only bound thin 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) are listed.



CKD|FBA


CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool for which thin devices are displayed.




ReMoTe


SUMMARY

Displays device totals and track totals for bound CKD devices, unbound CKD devices, bound FBA devices, and unbound FBA devices. Device detail lines are omitted.


VOLume(volser)




UNBOUND

When this keyword is specified, unbound thin devices are listed in addition to the thin devices bound to the selected pool(s).

This parameter applies only in conjunction with the POOL parameter. 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.

UNIT(device)


Causes of failureQUERY THINDEV fails when:




REBALANCE

Rebalances data devices in a pool.

Note: “Rebalancing pools” on page 441 describes rebalancing.

Syntax

REBALANCE{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)

[DEBUG]

[NOEXEC]

[VARIANCE(variance)]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG


LoCaL




NOEXEC


PATH(hoplist)


POOL(poolname)

The pool in which data devices are to be rebalanced.



ReMoTe


VARIANCE(variance)

Sets the rebalancing goal, that 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%. 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%.

VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureREBALANCE fails when:







REBIND

Rebinds already bound thin devices to a different pool.

Note: “Binding/unbinding thin devices” on page 434 describes rebinding of thin devices.

Syntax

REBIND{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)


[DEBUG]

[NOEXEC]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool where the thin devices are rebound.





ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureREBIND fails when:







◆ The REBIND validation fails for a device and SKIP has not been specified.

REBIND fails 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 5876) of the target pool to exceed the maximum oversubscription rate of the pool set the by the user.



REMOVE POOL

Removes data or save devices from the pool.

Note: The data or save device(s) must in an inactive state and may not have allocated tracks.

Syntax

REMOVE POOL(poolname){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[SKIP]

Parameters

CoNTRoLler(SymmID)


DDNAME(ddname)


DEBUG




LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)

The pool from which data or save devices are removed.





ReMoTe


SKIP


VOLume(volser)


UNIT(device)


Causes of failureREMOVE POOL fails when:

◆ A pool is specified and the specified pool cannot be found.




◆ The REMOVE POOL validation fails for a device and SKIP has not been specified.

REMOVE POOL fails 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.

RENAME POOL

Renames a pool.

Syntax

RENAME POOL(poolname){LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

NEWPOOL(newname)

[DEBUG]

[NOEXEC]

Parameters

CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NEWPOOL(newname)

The new name to be assigned to the thin pool.

NOEXEC


PATH(hoplist)


POOL(poolname)

The pool to be renamed.



ReMoTe


VOLume(volser)


UNIT(device)


Causes of failureRENAME POOL fails when:


◆ A valid existing pool name is not specified (in the POOL parameter).

◆ A valid new pool name is not specified (in 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 VMAX.





UNBIND

Unbinds thin devices from the pool.

Note: “Binding/unbinding thin devices” on page 434 describes unbinding of thin devices.

Using this command results in data loss for the thin devices being unbound. Ensure that the data is no longer needed for these devices before using this command.

Syntax

UNBIND{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}

POOL(poolname)


[DEBUG]

[NOCHKO]

[NOEXEC]

[SKIP]

[VERBOSE]

[WAIT]

Parameters

CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NOCHKO


NOEXEC




PATH(hoplist)


POOL(poolname)

The pool from which the thin devices are to be unbound.



ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)




Causes of failureUNBIND fails when:




◆ The UNBIND validation fails for a device and SKIP has not been specified.



UNBIND fails for a device when:


◆ The device is both mapped and in a ready state.




◆ The device is online to any host and NOCHKO has not been specified.

◆ The device is a Snap source or target device.

◆ The device is in an SRDF relationship.

◆ The device is in a PPRC relationship.

◆ The device has an XRC session.

USR_NRDY

Sets the Not Ready status for the thin device. This allows a thin device to be unbound.

Note: This action corresponds to the SC VOL USR_NRDY action of SRDF Host Component, as described in the SRDF Host Component for z/OS Product Guide.

Syntax

USR_NRDY{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOCHKO]

[NOEXEC]

[POOL(poolname)]

[SKIP]

[VERBOSE]

Parameters

CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NOEXEC




PATH(hoplist)


NOCHKO


POOL(poolname)




ReMoTe


SKIP


VERBOSE


VOLume(volser)


UNIT(device)


Causes of failureUSR_NRDY fails when:

◆ The USR_NRDY validation fails for a device and SKIP has not been specified.



USR_NRDY fails for a device if:


◆ A pool was specified and the device is not a thin device bound to that pool.


◆ The device is online to any host.



USR_RDY

Sets the Ready status for the thin device. This allows a bound thin device to be set active.

Note: This action corresponds to the SC VOL USR_RDY action of SRDF Host Component, as described in the SRDF Host Component for z/OS Product Guide.

Syntax

USR_RDY{LoCaL({UNIT(device)|VOLume(volser)|DDNAME(ddname)})|ReMoTe({UNIT(device)|VOLume(volser)|DDNAME(ddname)}PATH(hoplist) [CoNTRoLler(SymmID)])}


[DEBUG]

[NOEXEC]

[POOL(poolname)]

[SKIP]

Parameters

CoNTRoLler(SymmID)


DEBUG




DDNAME(ddname)


LoCaL


NOEXEC


PATH(hoplist)


POOL(poolname)






ReMoTe


SKIP


VOLume(volser)


UNIT(device)


Causes of failureUSR_RDY fails when

◆ The USR_RDY validation fails for a device and SKIP has not been specified.



USR_RDY fails for a device if:


◆ A pool was specified and the device is not a thin device bound to that pool.




Condition statements (ESFGPMBT)

IF

Tests a condition.

Syntax

IF {LASTCC|MAXCC} relation cmpvalue [EXIT]

Parameters

cmpvalue

The value to compare with the conditional code value using the specified relation. Values can be 0, 4, or 8.

EXIT

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.

LASTCC

The condition code to use in the compare is the return code from the most recently processed command.

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.

MAXCC

The condition code to use in the compare is the maximum of the return codes from all previously processed commands.

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.

relation

Indicates the relation to use in the comparison:

=

Tests the compare value with the condition code value for equality.

>

Tests whether the condition code value is greater than the compare value.

<

Tests whether the condition code value is less than the compare value.



ELSE

Provides an ELSE action. 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.

SyntaxELSE[EXIT]

Parameters[EXIT]

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.

ENDIF

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.

Syntax

ENDIF

RESET

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.

Syntax

RESET {LASTCC|MAXCC}

Parameters

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.

Condition statements (ESFGPMBT) 589


Return codes (ESFGPMBT)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.


CHAPTER 14Monitoring Thin Pools (THN Monitor)


◆ Introduction.......................................................................................................... 592◆ Getting started...................................................................................................... 593◆ Monitoring thin pools............................................................................................ 594◆ Command reference .............................................................................................. 600

Monitoring Thin Pools (THN Monitor) 591

Monitoring Thin Pools (THN Monitor)

IntroductionThe Thin Pool Capacity (THN) Monitor allows you to monitor thin pools.

Starting with HYPERMAX OS 5977, the thin pool is the only type of pool used for virtual provisioning. It replaces save pools, Snap pools, and DSE pools.

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 on a thin device results in space being allocated on a data device from the bound pool.

The THN Monitor periodically examines the consumed capacity of thin pools. It automatically checks user-defined space consumption thresholds and triggers an automated response that is tailored to the site requirements. You can specify multiple thresholds of space consumption. When the percentage of space consumption reaches the specified range, the appropriate action is taken.

The response can involve notifying appropriate operations personnel and performing whatever you determine to be the best response for each threshold level.

THN Monitor messages can have a use-supplied string (eight characters long) that is appended to the message text so that you can implement customized alerts to drive customer automation.

In addition to messages, the THN Monitor can call an user exit to perform a user-supplied procedure with a threshold is exceeded.



Getting started

Configuring THN Monitor

After installation of ResourcePak Base, configure the THN Monitor using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The THN Monitor initialization parameters are as follows:

◆ SCF.THN

◆ SCF.THN.xx.LIST

◆ SCF.THN.SymmID.LIST

◆ SCF.THN.SymmID.LIST=GATEkeeper=ccuu

◆ SCF.THN.SymmID.xx.LIST

◆ SCF.THN.SymmID.poolname.xx.LIST

Note: The THN Monitor is enabled by default.If the THN 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.

Running THN Monitor

The THN Monitor runs as a subtask of SCF. The SCF environment name for the THN Monitor is THN.

Getting started 593


Monitoring thin pools


Table 21 lists THN Monitor operations.

Optional user exit

You can specify a user exit for the THN Monitor to call when a threshold is exceeded.

“Pool Monitor User Exit” on page 641 provides information on using user exits.

“Example 5” on page 598 and “Example 6” on page 599 illustrate use of user exits.

Table 21 THN Monitor operations

Operation Control

Enable THN Monitor • THN,ENABLE command• SCF.THN initialization parameter• SCF.THN.SymmID.LIST initialization parameter

Set pool utilization thresholds and actions • SCF.THN.xx.LIST initialization parameter• SCF.THN.SymmID.xx.LIST initialization parameter• SCF.THN.SymmID.poolname.xx.LIST initialization

parameter

Identify gatekeeper for THN Monitor SCF.THN.SymmID.LIST=GATEkeeper=ccuu initialization parameter

Refresh THN Monitor initialization parameters THN,REFRESH command

View THN Monitor settings THN,DISPLAY command

Disable THN Monitor • THN,DISABLE command• SCF.THN initialization parameter• SCF.THN.SymmID.LIST initialization parameter



Examples

Example 1Consider the following example:

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

This example specifies the following values:

If the percent value overlaps two ranges (in this example, a value of 80), the higher range action is performed.

The 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 VMAX systems. 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

Monitoring thin pools 595


Example 2The following example covers a VMAX system that has two pools defined. The THN Monitor can monitor each pool separately. If the pools do not exist when SCF is started, you must issue the THN,REFRESH command for the monitor to begin polling.

The SCF initialization parameters for monitoring two pools might look as follows:

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

* The result is as follows:

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 3The following is an example of the THN Monitor designating a specific VMAX 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 *

The result is as follows:

SCF1160I THN CONTROLLER 0001957-00086 IS AT 9% UTILIZATION OF THINPOOL SPACE ( 0 3390- 9 FBA- 0) - THINALRT

Example 4The following is an example of a global THN Monitor.

SCF.THN=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 *

The result is as follows:

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) - LOWPRIOR SCF1160I THN CONTROLLER 0001926-04124 IS AT 7% UTILIZATION OF THINPOOL SPACE ( 0 3390- 0 FBA- 7) - LOWPRIOR



Example 5In the following example, three pool intervals are defined for pool DG3_CKD_PL on VMAX system 0001967-00257, each specifying the provided sample user exit, TSDVEXIT, as its action:

Note: “Sample user exit” on page 642 describes the sample user exit.

SCF.THN.00257.LIST=ENABLE SCF.THN.00257.LIST=GATE=640F

SCF.THN.00257.DG3_CKD_PL.01.LIST=PERCENT(00,33) SCF.THN.00257.DG3_CKD_PL.01.LIST=DURATION=60 SCF.THN.00257.DG3_CKD_PL.01.LIST=ACTION=USEREXIT(TSDVEXIT)SCF.THN.00257.DG3_CKD_PL.01.LIST=FREQUENCY=REPEAT SCF.THN.00257.DG3_CKD_PL.02.LIST=PERCENT(34,66) SCF.THN.00257.DG3_CKD_PL.02.LIST=DURATION=30 SCF.THN.00257.DG3_CKD_PL.02.LIST=ACTION=USEREXIT(TSDVEXIT)SCF.THN.00257.DG3_CKD_PL.02.LIST=FREQUENCY=REPEAT SCF.THN.00257.DG3_CKD_PL.03.LIST=PERCENT(67,100) SCF.THN.00257.DG3_CKD_PL.03.LIST=DURATION=10 SCF.THN.00257.DG3_CKD_PL.03.LIST=ACTION=USEREXIT(TSDVEXIT)SCF.THN.00257.DG3_CKD_PL.03.LIST=FREQUENCY=REPEAT

Note: The parameters SCF.THN.SymmID.LIST=ENABLE (described in “SCF.THN.SymmID.LIST” on page 112) and SCF.THN.SymmID.LIST=GATEkeeper=ccuu (described in “SCF.THN.SymmID.LIST=GATEkeeper=ccuu” on page 112) should only be specified once for each VMAX system.

If the percentage used for pool DG3_CKD_PL is within the range of 0 to 33, the action for interval 1 is triggered. In this case, the following report is displayed:

16.45.45 S0060860 TSDVEXIT 969 969 ---------------------------------------------------------- 969 Called by Monitor: THN 969 Pool : DG3_CKD_PL 969 Controller : 0001967-00257 969 Sequence Number : 1 969 Interval Low % : 0 969 High % : 33 969 Duration In Mins : 60 969 In Secs : 3600 969 ---------------------------------------------------------- 969 Current Previous 969 ------------------- ------------------- 969 Percent Used 26 25 969 Used Tracks 654130 628972 969 Free Tracks 1946510 1971668 969 Active Devices 48 48 969 ----------------------------------------------------------



Example 6In the following example, three VMAX system intervals are defined for VMAX system 0001967-00257, each specifying the provided sample user exit, TSDVEXIT, for its action:

Note: “Sample user exit” on page 642 describes the sample user exit.

SCF.THN.00257.LIST=ENABLE SCF.THN.00257.LIST=GATE=640F

SCF.THN.00257.01.LIST=PERCENT(00,33) SCF.THN.00257.01.LIST=DURATION=60 SCF.THN.00257.01.LIST=ACTION=USEREXIT(TSDVEXIT)SCF.THN.00257.01.LIST=FREQUENCY=REPEAT SCF.THN.00257.02.LIST=PERCENT(34,66) SCF.THN.00257.02.LIST=DURATION=30 SCF.THN.00257.02.LIST=ACTION=USEREXIT(TSDVEXIT)SCF.THN.00257.02.LIST=FREQUENCY=REPEAT SCF.THN.00257.03.LIST=PERCENT(67,100) SCF.THN.00257.03.LIST=DURATION=10 SCF.THN.00257.03.LIST=ACTION=USEREXIT(TSDVEXIT)SCF.THN.00257.03.LIST=FREQUENCY=REPEAT

Note: The parameters SCF.THN.SymmID.LIST=ENABLE (described in “SCF.THN.SymmID.LIST” on page 112) and SCF.THN.SymmID.LIST=GATEkeeper=ccuu (described in “SCF.THN.SymmID.LIST=GATEkeeper=ccuu” on page 112) should only be specified once for each VMAX system.

If the percentage used for pool DG3_CKD_PL is within the range of 0 to 33, the action for interval 1 is triggered. In this case, the following report is displayed:

16.45.45 S0060860 TSDVEXIT 968 968 ---------------------------------------------------------- 968 Called by Monitor: THN 968 Controller : 0001967-00257 968 Sequence Number : 1 968 Interval Low % : 0 968 High % : 33 968 Duration In Mins : 60 968 In Secs : 3600 968 ---------------------------------------------------------- 968 Current Previous 968 ------------------- ------------------- 968 3390 Percent Used 2 1 968 3390 Used Tracks 2745328 628972 968 3390 Free Tracks 209519312 211635668 968 3380 Percent Used 0 0 968 3380 Used Tracks 0 0 968 3380 Free Tracks 0 0 968 FBA Percent Used 2 2 968 FBA Used Tracks 387837 387526 968 FBA Free Tracks 81763 82074 968 ----------------------------------------------------------



Command reference

Syntax conventions


THN,DISABLE

Disables the THN Monitor.

If no VMAX system is specified, the THN,DISABLE command stops monitoring globally.

Note: If the THN 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.

Syntax

F emcscf,THN,DISABLE[,CoNTRoLler(SymmID)]

Parameters

CoNTRoLler(SymmID)




emcscf


ExampleF emcscf,THN,DISABLESCF1190I THN,DISABLE SCF1121I THN MONITOR THINPOOL TASK DISABLED SCF1191I THN COMMAND ACCEPTED.



THN,DISPLAY

Displays the THN Monitor settings.

Syntax

F emcscf,THN,DISPLAY,{GLOBAL|CoNTRoLler(SymmID) [POOLNAME(pool)]}

Parameters

CoNTRoLler(SymmID)

Displays THN Monitor settings for the VMAX system identified with its serial number.



emcscf


GLOBAL

Displays default settings for the THN Monitor.

POOLNAME(pool)

Displays THN Monitor settings for the specified pool.

The POOLNAME parameter can only be used when CoNTRoLler(SymmID) is specified in the command.

ExampleF emcscf,THN,DISPLAY,GLOBALSCF1190I THN DISPLAY GLOBAL SCF1191I THN COMMAND ACCEPTED. SCF1120I THN MONITOR THINPOOL TASK ENABLED SCF1130I THN -GLOBAL INTERVAL 1, PERCENT=( 0, 80) SCF1132I THN -- DURATION= 600 ACTION=NONE FREQUENCY=NONE SCF1130I THN -GLOBAL INTERVAL 2, PERCENT=( 80, 90) SCF1132I THN -- DURATION= 300 ACTION=MESSAGE FREQUENCY=REPEAT SCF1130I THN -GLOBAL INTERVAL 3, PERCENT=( 90, 95) SCF1132I THN -- DURATION= 120 ACTION=MESSAGE FREQUENCY=REPEAT SCF1130I THN -GLOBAL INTERVAL 4, PERCENT=( 95, 100) SCF1132I THN -- DURATION= 60 ACTION=MESSAGE FREQUENCY=REPEAT SCF1110I THN CONTROLLER 0001903-00353 AT MICROCODE LEVEL 5073 SCF1115I THN -- MICROCODE LEVEL NOT SUPPORTED SCF1111I THN -- DISABLED FROM PROCESSING SCF1110I THN CONTROLLER 0001926-01076 AT MICROCODE LEVEL 5076 SCF1112I THN -- LAST TIME CHECK: 12:18:00.41, NEXT TIME CHECK: 22:18:00.41 SCF1113I THN -- LAST PERCENT: 1 (THIN- 3390- 1 FBA- 0), CURRENT INTERVAL: 1SCF1114I THN -- GATEKEEPER DEVICE: 2700 SCF1122I THN -- USING GLOBAL INTERVAL LIST SCF1110I THN CONTROLLER 0001926-04123 AT MICROCODE LEVEL 5075 SCF1112I THN -- LAST TIME CHECK: 12:18:00.41, NEXT TIME CHECK: 22:18:00.41 SCF1113I THN -- LAST PERCENT: 10 (THIN- 3390- 1 FBA- 10), CURRENT INTERVAL: 1SCF1114I THN -- GATEKEEPER DEVICE: 2C00 SCF1122I THN -- USING GLOBAL INTERVAL LIST SCF1110I THN CONTROLLER 0001973-00007 AT MICROCODE LEVEL 5077 SCF1112I THN -- LAST TIME CHECK: 12:18:00.41, NEXT TIME CHECK: 22:18:00.41 SCF1113I THN -- LAST PERCENT: 0 (THIN- 3390- 0 FBA- 0), CURRENT INTERVAL: 1SCF1114I THN -- GATEKEEPER DEVICE: 4700 SCF1122I THN -- USING GLOBAL INTERVAL LIST



THN,ENABLE

Enables the THN Monitor globally or for the specified VMAX system.

Syntax

F emcscf,THN,ENABLE[,CoNTRoLler(SymmID)]

Parameters

CoNTRoLler(SymmID)




emcscf


ExampleF emcscf,THN,ENABLE SCF1190I THN,ENABLE SCF1120I THN MONITOR THINPOOL TASK ENABLED SCF1191I THN COMMAND ACCEPTED.

THN,REFRESH

Refreshes the initialization parameters for the THN Monitor. If there are changes in parameter values, they must first be reloaded and then reprocessed.

Note: Issue the SCF INI,REFRESH command before using the THN,REFRESH command.

Syntax

F emcscf,THN,REFRESH

Parameters

emcscf


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


CHAPTER 15Monitoring Snap Pools (SDV Monitor)


◆ Introduction.......................................................................................................... 604◆ Getting started...................................................................................................... 605◆ Monitoring Snap pools.......................................................................................... 606◆ Command reference .............................................................................................. 608

Monitoring Snap Pools (SDV Monitor) 603

Monitoring Snap Pools (SDV Monitor)

IntroductionThe Snap Pool Capacity (SDV) Monitor allows you to monitor Snap pools that contain save devices.

IMPORTANT

Starting with HYPERMAX OS 5977, save devices are no longer used. For more information about how HYPERMAX OS 5977 handles Snap pools, refer to the VMAX3 Family with HYPERMAX OS VMAX 100K, VMAX 200K, VMAX 400K Product Guide.

Information presented in this chapter is relevant for Enginuity 5876 and 5773. No additional warnings are included in the text.

Save devices are a predefined set of devices that provide a pool of physical space. Save devices are not host-accessible.

The SDV Monitor periodically examines the consumed capacity of the Snap pool used by TimeFinder/Mirror Mainframe Snap Facility with VDEV1 functionality enabled. VDEVs make use of Snap pool 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.

The SDV Monitor automatically checks user-defined space consumption thresholds and trigger an automated response that is tailored to the site requirements. You can specify multiple thresholds of space consumption. When the percentage of space consumption reaches the specified range, the appropriate action is taken.

The response can involve the following actions:

◆ Notify appropriate operations personnel

◆ Identify highly consuming virtual device snap jobs

◆ Stop virtual device snaps based on local criteria

◆ Perform whatever you determine to be the best response to each threshold level

SDV Monitor messages can have a use-supplied string (eight characters long) that is appended to the message text so that you can implement customized alerts to drive customer automation.

In addition to messages, the SDV Monitor can call an user exit to perform a user-supplied procedure with a threshold is exceeded.

1. Virtual Devices



Getting started

Configuring SDV Monitor

After installation of ResourcePak Base, enable and configure the SDV Monitor using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The SDV Monitor initialization parameters are as follows:

◆ SCF.SDV

◆ SCF.SDV.xx.LIST

◆ SCF.SDV.SymmID.LIST

◆ SCF.SDV.SymmID.LIST=GATEkeeper=ccuu

◆ SCF.SDV.SymmID.xx.LIST

◆ SCF.SDV.SymmID.poolname.xx.LIST

Note: The SDV Monitor is enabled by default.If the SDV Monitor is disabled, it does not monitor anything. However, it responds to commands. In particular, if a request is made to enable the SDV Monitor, it responds to the request and activates. When disabled, the SDV Monitor enters a 12-hour wait period and then immediately enter another 12-hour wait.

Running SDV Monitor

The SDV Monitor runs as a subtask of SCF. The SCF environment name for the SDV Monitor is SDV.

Getting started 605


Monitoring Snap pools


Table 22 lists SDV Monitor operations.

Optional user exit

You can specify a user exit for the SDV Monitor to call when a threshold is exceeded.


Table 22 SDV Monitor operations

Operation Control

Enable SDV Monitor • SDV,ENABLE command• SCF.SDV initialization parameter

• SCF.SDV.SymmID.LIST initialization parameter

Set pool utilization thresholds and actions • SCF.SDV.xx.LIST initialization parameter

• SCF.SDV.SymmID.xx.LIST initialization parameter

• SCF.SDV.SymmID.poolname.xx.LIST initialization parameter

Identify gatekeeper for SDV Monitor SCF.SDV.SymmID.LIST=GATEkeeper=ccuu initialization parameter

Refresh SDV Monitor initialization parameters SDV,REFRESH command

View SDV Monitor settings SDV,DISPLAY command

Disable SDV Monitor • SDV,DISABLE command• SCF.SDV initialization parameter

• SCF.SDV.SymmID.LIST initialization parameter



Example

Consider the following example:

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




01 0 - 80 10 minutes None

02 80 - 90 5 minutes Issue message Each time

03 90 - 100 1 minute Call user exit Once

Monitoring Snap pools 607


Command reference

Syntax conventions


SDV,DISABLE

Disables the SDV Monitor.

If no VMAX system is specified, the SDV,DISABLE command stops monitoring globally.

Note: If the SDV 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.

Syntax

F emcscf,SDV,DISABLE[,CoNTRoLler(SymmID)]

Parameters

CoNTRoLler(SymmID)




emcscf


ExampleF emcscf,SDV,DISABLE

SCF1190I SDV,DISABLE SCF1191I SDV COMMAND ACCEPTED. SCF1121I SDV MONITOR SNAPPOOL TASK DISABLED



SDV,DISPLAY

Displays the SDV Monitor settings.

Syntax

F emcscf,SDV,DISPLAY[,GLOBAL][,CoNTRoLler(SymmID)][POOLNAME(pool)]

Parameters

CoNTRoLler(SymmID)

Displays SDV Monitor settings for the VMAX system identified with its serial number.



emcscf


GLOBAL

Displays default settings for the SDV Monitor.

POOLNAME(pool)

Displays SDV Monitor settings for the specified pool.

ExampleF EMCSCF,SDV,DISPLAY,GLOBAL

SCF1190I SDV DISPLAY GLOBAL SCF1191I SDV COMMAND ACCEPTED. SCF1120I SDV MONITOR SNAPPOOL TASK ENABLED SCF1130I SDV -GLOBAL INTERVAL 1, PERCENT=( 0, 80) SCF1132I SDV -- DURATION= 600 ACTION=NONE FREQUENCY=NONE SCF1130I SDV -GLOBAL INTERVAL 2, PERCENT=( 80, 90) SCF1132I SDV -- DURATION= 300 ACTION=MESSAGE FREQUENCY=REPEAT SCF1130I SDV -GLOBAL INTERVAL 3, PERCENT=( 90, 95) SCF1132I SDV -- DURATION= 120 ACTION=MESSAGE FREQUENCY=REPEAT SCF1130I SDV -GLOBAL INTERVAL 4, PERCENT=( 95, 100) SCF1132I SDV -- DURATION= 60 ACTION=MESSAGE FREQUENCY=REPEAT SCF1110I SDV CONTROLLER 0001903-00353 AT MICROCODE LEVEL 5073 SCF1112I SDV -- LAST TIME CHECK: 12:18:00.41, NEXT TIME CHECK: 22:18:00.41 SCF1113I SDV -- LAST PERCENT: 3 (3380- 0 3390- 3 FBA- 0), CURRENT INTERVAL: 1SCF1114I SDV -- GATEKEEPER DEVICE: 7200 SCF1122I SDV -- USING GLOBAL INTERVAL LIST SCF1110I SDV CONTROLLER 0001903-00354 AT MICROCODE LEVEL 5071 SCF1118I SDV -- NO SNAPPOOL DEVICES DEFINED SCF1111I SDV -- DISABLED FROM PROCESSING SCF1110I SDV CONTROLLER 0001926-01076 AT MICROCODE LEVEL 5076 SCF1112I SDV -- LAST TIME CHECK: 12:18:00.41, NEXT TIME CHECK: 22:18:00.41 SCF1113I SDV -- LAST PERCENT: 1 (3380- 0 3390- 1 FBA- 0), CURRENT INTERVAL: 1SCF1114I SDV -- GATEKEEPER DEVICE: 2700 SCF1122I SDV -- USING GLOBAL INTERVAL LIST SCF1110I SDV CONTROLLER 0001926-04059 AT MICROCODE LEVEL 5074 SCF1112I SDV -- LAST TIME CHECK: 12:18:00.41, NEXT TIME CHECK: 22:18:00.41 SCF1113I SDV -- LAST PERCENT: 0 (3380- 0 3390- 0 FBA- 0), CURRENT INTERVAL: 1SCF1114I SDV -- GATEKEEPER DEVICE: 8F00 SCF1122I SDV -- USING GLOBAL INTERVAL LIST



SDV,ENABLE

Enables the SDV Monitor globally or for the specified VMAX system.

Syntax

F emcscf,SDV,ENABLE[,CoNTRoLler(SymmID)]

Parameters

CoNTRoLler(SymmID)




emcscf


ExampleF emcscf,SDV,ENABLE SCF1190I SDV,ENABLE SCF1191I SDV COMMAND ACCEPTED. SCF1120I SDV MONITOR SNAPPOOL TASK ENABLED

SDV,REFRESH

Refreshes the initialization parameters for the SDV Monitor. If there are changes in parameter values, they must first be reloaded and then reprocessed.

Note: Issue the SCF INI,REFRESH command before using the SDV,REFRESH command.

Syntax

F emcscf,SDV,REFRESH

Parameters

emcscf



F emcscf,SDV,REFRESH SCF1190I SDV,REFRESH SCF1191I SDV COMMAND ACCEPTED.SCF1125I SDV - INI PARAMETERS LOADED


CHAPTER 16Monitoring DSE Pools (DSE Monitor)


◆ Introduction.......................................................................................................... 612◆ Getting started...................................................................................................... 614◆ Monitoring DSE pools............................................................................................ 615◆ Command reference .............................................................................................. 617

Monitoring DSE Pools (DSE Monitor) 611

Monitoring DSE Pools (DSE Monitor)

IntroductionThe DSE Monitor allows you to monitor DSE (Delta Set Extension) pools.

IMPORTANT

DSE pools are available under Enginuity 5876 and 5773. Starting with HYPERMAX OS 5977, DSE pools are no longer used. For more information about how HYPERMAX OS 5977 handles DSE pools, refer to the VMAX3 Family with HYPERMAX OS VMAX 100K, VMAX 200K, VMAX 400K Product Guide.

Information presented in this chapter is relevant for Enginuity 5876 and 5773. No additional warnings are included in the text.

A DSE pool is used to extend the cache available for an SRDF/A group by offloading some or all of its cycle data from cache to preconfigured DSE devices. 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 VMAX system moves some of the cache slots onto these DSE pool devices. On each SRDF/A cycle switch, these DSE pool 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 DSE pool and placed into cache so that they can be transmitted or restored.

The DSE Monitor automatically checks user-defined space consumption thresholds and trigger an automated response that is tailored to the site requirements. You can specify multiple thresholds of space consumption. When the percentage of space consumption reaches a specified range, the appropriate action is taken.

The response can involve notifying appropriate operations personnel or performing whatever you determine to be the best response to each threshold level.

DSE Monitor messages can have a use-supplied string (eight characters long) that is appended to the message text so that you can implement customized alerts to drive customer automation.

In addition to messages, the DSE Monitor can call an user exit to perform a user-supplied procedure with a threshold is exceeded.



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

If you specify no threshold time values, then no monitoring is done. If you specify valid values, an SCF message is issued for any locally connected VMAX that has a spillover duration equal to the entered value. ResourcePak Base also issues a message to indicate when the spillover value returns to zero for the VMAX system.

Introduction 613


Getting started

Configuring DSE Monitor

After installation of ResourcePak Base, enable and configure the DSE Monitor using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The DSE Monitor initialization parameters are as follows:

◆ SCF.DSE.LIST

◆ SCF.DSE.xx.LIST

◆ SCF.DSE.SymmID.LIST

◆ SCF.DSE.SymmID.LIST=GATEkeeper=ccuu

◆ SCF.DSE.SymmID.xx.LIST

◆ SCF.DSE.SymmID.poolname.xx.LIST

◆ SCF.DSE.MAJOR

◆ SCF.DSE.MINOR

◆ SCF.DSE.WARNING

Note: The DSE Monitor is enabled by default.If the DSE 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.

Running DSE Monitor

The DSE Monitor runs as a subtask of SCF. The SCF environment name for the DSE Monitor is DSE.



Monitoring DSE pools


Table 23 lists DSE Monitor operations.

Optional user exit

You can specify a user exit for the DSE Monitor to call when a threshold is exceeded.


Table 23 DSE Monitor operations

Operation Control

Enable DSE Monitor • DSE,ENABLE command• SCF.DSE.LIST initialization parameter• SCF.DSE.SymmID.LIST initialization parameter

Set pool utilization thresholds and actions • SCF.DSE.xx.LIST initialization parameter• SCF.DSE.SymmID.xx.LIST initialization parameter• SCF.DSE.SymmID.poolname.xx.LIST initialization

parameter

Set DSE spillover thresholds • SCF.DSE.WARNING initialization parameter• SCF.DSE.MINOR initialization parameter• SCF.DSE.MAJOR initialization parameter

Identify gatekeeper for DSE Monitor SCF.DSE.SymmID.LIST=GATEkeeper=ccuu initialization parameter

Refresh DSE Monitor initialization parameters DSE,REFRESH command

View DSE Monitor settings DSE,DISPLAY command

Disable DSE Monitor • DSE,DISABLE command• SCF.DSE.LIST initialization parameter• SCF.DSE.SymmID.LIST initialization parameter

Monitoring DSE pools 615


Example

Consider the following example:

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



Command reference

Syntax conventions


DSE,DISABLE

Disables the DSE Monitor.

If no VMAX system is specified, The DSE,DISABLE command stops monitoring globally.

Note: If the DSE 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.

Syntax

F emcscf,DSE,DISABLE[,CoNTRoLler(SymmID)]

Parameters

CoNTRoLler(SymmID)




emcscf


ExampleF emcscf,DSE,DISABLE

SCF1190I DSE,DISABLE SCF1121I DSE MONITOR DSEPOOL TASK DISABLED SCF1191I DSE COMMAND ACCEPTED.



DSE,DISPLAY

Displays the DSE Monitor settings.

Syntax

F emcscf,DSE,DISPLAY[,GLOBAL][,CoNTRoLler(SymmID)][POOLNAME(pool)]

Parameters

CoNTRoLler(SymmID)

Displays DSE Monitor settings for the VMAX system identified with its serial number.



emcscf


GLOBAL

Displays default settings for the DSE Monitor.

POOLNAME(pool)

Displays DSE Monitor settings for the specified pool.

ExampleF emcscf,DSE,DISPLAY,GLOBAL

SCF1190I DSE DISPLAY GLOBAL SCF1191I DSE COMMAND ACCEPTED. SCF1120I DSE MONITOR DSEPOOL TASK ENABLED SCF1130I DSE -GLOBAL INTERVAL 1, PERCENT=( 0, 80) SCF1132I DSE -- DURATION= 10 ACTION=NONE FREQUENCY=NONE SCF1130I DSE -GLOBAL INTERVAL 2, PERCENT=( 80, 90) SCF1132I DSE -- DURATION= 5 ACTION=MESSAGE FREQUENCY=REPEAT SCF1130I DSE -GLOBAL INTERVAL 3, PERCENT=( 90, 95) SCF1132I DSE -- DURATION= 2 ACTION=MESSAGE FREQUENCY=REPEAT SCF1130I DSE -GLOBAL INTERVAL 4, PERCENT=( 95, 100) SCF1132I DSE -- DURATION= 1 ACTION=MESSAGE FREQUENCY=REPEAT SCF1110I DSE CONTROLLER 0001903-00353 AT MICROCODE LEVEL 5073 SCF1112I DSE -- LAST TIME CHECK: 14:45:44.89, NEXT TIME CHECK: 14:45:54.89 SCF1113I DSE -- LAST PERCENT: 0 (3380- 0 3390- 0 FBA- 0), CURRENT INTERVAL: 1SCF1114I DSE -- GATEKEEPER DEVICE: 7200 SCF1122I DSE -- USING GLOBAL INTERVAL LIST SCF1110I DSE CONTROLLER 0001903-00354 AT MICROCODE LEVEL 5071 SCF1115I DSE -- MICROCODE LEVEL NOT SUPPORTED SCF1111I DSE -- DISABLED FROM PROCESSING SCF1110I DSE CONTROLLER 0001926-01076 AT MICROCODE LEVEL 5076 SCF1119I DSE -- NO DSEPOOL POOLS DEFINED SCF1111I DSE -- DISABLED FROM PROCESSING SCF1110I DSE CONTROLLER 0001957-00086 AT MICROCODE LEVEL 5076 SCF1112I DSE -- LAST TIME CHECK: 14:45:44.89, NEXT TIME CHECK: 14:45:54.89 SCF1113I DSE -- LAST PERCENT: 0 (3380- 0 3390- 0 FBA- 0), CURRENT INTERVAL: 1SCF1114I DSE -- GATEKEEPER DEVICE: 3A00 SCF1122I DSE -- USING GLOBAL INTERVAL LIST



DSE,ENABLE

Enables the DSE Monitor globally or for the specified VMAX system.

Syntax

F emcscf,DSE,ENABLE[,CoNTRoLler(SymmID)]

Parameters

CoNTRoLler(SymmID)




emcscf


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 in parameter values, they must first be reloaded and then reprocessed.

Note: Issue the SCF INI,REFRESH command before using the DSE,REFRESH command.

Syntax

F emcscf,DSE,REFRESH

Parameters

emcscf



F emcscf,DSE,REFRESH SCF1190I DSE,REFRESH SCF1191I DSE COMMAND ACCEPTED.SCF1125I DSE - INI PARAMETERS LOADED


CHAPTER 17Monitoring Space Reclamation (TRU Monitor)


◆ Introduction.......................................................................................................... 622◆ Getting started...................................................................................................... 622◆ Monitoring the TRU environment ........................................................................... 624◆ Command reference .............................................................................................. 631

Monitoring Space Reclamation (TRU Monitor) 621

Monitoring Space Reclamation (TRU Monitor)

IntroductionThe TRU (Thin Reclaim Utility) Monitor records when a z/OS dataset is scratched on a thin device and allows the available track space to be returned to the VMAX free track pool.

Note: The TRU Monitor is available with Enginuity 5876 and HYPERMAX OS 5977.

The TRU Monitor scans the environment for unused tracks on thin CKD devices and reclaims tracks with no user records. For details, refer to “Monitoring” on page 626.

Getting started

Configuring the TRU Monitor

After installation of ResourcePak Base, enable and configure the TRU Monitor using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The TRU Monitor initialization parameters are as follows:

◆ SCF.TRU.DEBUG

◆ SCF.TRU.DEV.EXCLUDE.LIST

◆ SCF.TRU.DEV.INCLUDE.LIST

◆ SCF.TRU.ENABLE

◆ SCF.TRU.OFFLINE

◆ SCF.TRU.RECLAIM.DSFACTOR

◆ SCF.TRU.RECLAIM.DSPREFIX

◆ SCF.TRU.RECLAIM.METHOD

◆ SCF.TRU.RECLAIM.PGMNAME

◆ SCF.TRU.RECLAIM.POST.MAX

◆ SCF.TRU.RECLAIM.POST.MIN

◆ SCF.TRU.RECLAIM.POST.PCT

◆ SCF.TRU.RECLAIM.POST.TYPE

◆ SCF.TRU.RECLAIM.SCRATCH.WAIT

◆ SCF.TRU.RECLAIM.STCNAME

◆ SCF.TRU.RECLAIM.STRESS.MONITOR

◆ SCF.TRU.RECLAIM.STRESS.WAIT

◆ SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT

◆ SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT

◆ SCF.TRU.RECLAIM.SYSVTOC.WAIT

◆ SCF.TRU.RECLAIM.TIMELIMIT.LIST



◆ SCF.TRU.RECLAIM.TASK.LIMIT

◆ SCF.TRU.SCAN.PGMNAME

◆ SCF.TRU.SCAN.STCNAME

◆ SCF.TRU.SCAN.TASK.LIMIT

◆ SCF.TRU.SCRATCH.POST.MAX

◆ SCF.TRU.SCRATCH.POST.MIN

◆ SCF.TRU.SCRATCH.POST.PCT

◆ SCF.TRU.SCRATCH.POST.TYPE

◆ SCF.TRU.SCRATCH.RECLAIM

◆ SCF.TRU.THICKR1

Running the TRU Monitor

The TRU Monitor runs in an LPAR with SCF and the TRU environment active.

You can run the TRU Monitor as an SCF subtask, a separate started task, or a batch job. The program name is ESFTRURC. The JCL is as follows:

//MYSTEP PROC CCUU=ccuu,TYPE=type//ESFTRURC EXEC PGM=ESFTRURC,PARM='&TYPE,&CCUU'//STEPLIB DD DISP=SHR,DSN=ds_prefix.LINKLIB//SCF$nnnn DD DUMMY//SYSABEND DD SYSOUT=*//ESFTRURC DD SYSOUT=*

Where:

◆ ccuu identifies the device.

◆ type can be SCAN for scan operations described in “Scanning” on page 628 or RECLAIM for reclaim operations described in “Reclaiming” on page 629.


◆ SCF$nnnn identifies the SCF subsystem used for the TRU Monitor.

You can also use the keyword DEBUG as parameter #3 to enable the debugging mode.

Getting started 623


Monitoring the TRU environment


Basic operationsTable 24 lists basic TRU Monitor operations.

Setting scanning optionsTable 25 lists operations to set up the scanning process.

Table 24 Basic TRU Monitor operations

Operation Control

Enable or disable TRU Monitor TRU,ENABLE or TRU,DISABLE command

Enable or disable VMAX stress monitoring SCF.TRU.RECLAIM.STRESS.MONITOR initialization parameter

Specify devices to be monitored by TRU Monitor • SCF.TRU.DEV.INCLUDE.LIST initialization parameter• SCF.TRU.DEV.EXCLUDE.LIST initialization parameter

Whether to process offline devices SCF.TRU.OFFLINE initialization parameter

Start device monitoring TRU,START command

View TRU environment information TRU,DISPLAY command

View TRU device information TRU,DISPLAY,DEVICE command

Scan devices TRU,SCAN command

Reclaim devices TRU,RECLAIM command

Prevent automatic reclamation of specified devices TRU,HOLD command

Release specified devices for scanning or reclaiming TRU,RELEASE command

Stop device monitoring TRU,STOP command

Refresh TRU internal tables TRU,REFRESH command

Enable TRU Monitor debugging SCF.TRU.DEBUG initialization parameter

View list of TRU commands TRU,HELP command

Table 25 Setting scanning options

Operation Control

Identify program for scanning SCF.TRU.SCAN.PGMNAME initialization parameter

Set STCNAME to execute scanning as separate task SCF.TRU.SCAN.STCNAME initialization parameter

Set number of simultaneous scan tasks SCF.TRU.SCAN.TASK.LIMIT initialization parameter

Enable thick R1 scanning SCF.TRU.THICKR1 initialization parameter



Setting reclaiming optionsTable 26 lists operations to set up the reclaiming process.

Setting scratch optionsTable 27 lists scratch options.

Table 26 Setting reclaiming options

Operation Control

Identify program for reclaim processing SCF.TRU.RECLAIM.PGMNAME initialization parameter

Set STCNAME to execute reclaim as separate task SCF.TRU.RECLAIM.STCNAME initialization parameter

Set number of simultaneous reclaim tasks SCF.TRU.RECLAIM.TASK.LIMIT initialization parameter

Set time limits for reclaim processing SCF.TRU.RECLAIM.TIMELIMIT.LIST initialization parameter

Set prefix for temporary dataset allocation SCF.TRU.RECLAIM.DSPREFIX initialization parameter

Set size factor for temporary dataset allocation SCF.TRU.RECLAIM.DSFACTOR initialization parameter

Determine the wait time after dataset scratch SCF.TRU.RECLAIM.SCRATCH.WAIT initialization parameter

Determine track reclamation order SCF.TRU.RECLAIM.METHOD initialization parameter

Set max count of tracks for calculated space percentages

SCF.TRU.RECLAIM.POST.MAX initialization parameter

Set min count of tracks for calculated space percentages

SCF.TRU.RECLAIM.POST.MIN initialization parameter

Set space percentage SCF.TRU.RECLAIM.POST.PCT initialization parameter

Set space calculation basis SCF.TRU.RECLAIM.POST.TYPE initialization parameter

Set max time to hold SYSVTOC RESERVE during processing

SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT initialization parameter

Set max segment size while holding SYSVTOC RESERVE SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT initialization parameter

Set wait time between releasing and acquiring SYSVTOC RESERVE

SCF.TRU.RECLAIM.SYSVTOC.WAIT initialization parameter

Set max wait time between reclaim erase I/Os for stress monitoring

SCF.TRU.RECLAIM.STRESS.WAIT initialization parameter

Table 27 Setting scratch options

Operation Control

Set max count of tracks for calculated space percentages

SCF.TRU.SCRATCH.POST.MAX initialization parameter

Set min count of tracks for calculated space percentages

SCF.TRU.SCRATCH.POST.MIN initialization parameter

Set space percentage SCF.TRU.SCRATCH.POST.PCT initialization parameter

Set space calculation basis SCF.TRU.SCRATCH.POST.TYPE initialization parameter

Set max count of tracks in extent that can be automatically reclaimed

SCF.TRU.SCRATCH.RECLAIM initialization parameter

Monitoring the TRU environment 625


Monitoring

The TRU Monitor performs the following steps:

1. Creates a control block in common storage used for TRU communications and anchors the TRU device table.

2. Reads the SCF initialization parameters that apply to the TRU environment.

3. Discovers SCF devices. Any thin devices found are matched against the TRU include/exclude list.

Note: Refer to “Monitored devices” on page 627 for details on monitored devices.

The TRU Monitor identifies and marks the tracks that are eligible for reclamation.

4. If any devices have needs, schedules the relevant activity.

Most needs result in scheduling the scan (Step 5) or reclaim (Step 6) activity. But other activities include handling new device BIND or old device UNBIND or processing of commands like HOLD/RELEASE or START/STOP.

5. SCF, with the TRU Monitor, periodically updates the list of tracks containing no user records. You can also perform this update manually by running the TRU Monitor in the scan mode. The monitor scans the VTOC for available tracks in the volume free space and updates the SDDF session information. This is called TRU scanning.

Note: Refer to “Scanning” on page 628 for details.

6. Analyzes the volume free space and SDDF session information and clears the tracks. This is called TRU reclaiming. The Zero Space Reclaim process runs on the VMAX system as a background task and reclaims tracks with no user records on CKD volumes.

Note: Refer to “Reclaiming” on page 629 for details.

LimitationsAt any time, it is possible for the z/OS VTOC free space map, the SDDF session information, and the VMAX 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 settings, there may always be some tracks not processed. The VMAX thin device allocation map shows which tracks have been written to, and has no knowledge of which tracks have been allocated and unused.



Monitored devices

You specify the devices to be monitored using the SCF.TRU.DEV.INCLUDE.LIST and SCF.TRU.DEV.EXCLUDE.LIST initialization parameters described in “SCF.TRU.DEV.INCLUDE.LIST” on page 121 and “SCF.TRU.DEV.EXCLUDE.LIST” on page 121.

The TRU Monitor only monitors devices that have been included with the SCF.TRU.DEV.INCLUDE.LIST initialization parameter. If you want to monitor all thin devices, specify “SCF.TRU.DEV.INCLUDE.LIST=0000-FFFF”. The TRU Monitor then determines which devices are thin and are subject to be monitored.

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, as described in “TRU,START” on page 639.

Thin devices that have the PERSIST device-level attribute set are not monitored. Thin devices with the PERSIST attribute can be found in the device list, but are not be monitored.

Note: “BIND” on page 532 describes the BIND command and the PERSIST option.

Monitoring occurs regardless of whether the thin device has the PREALLOCATE device-level attribute.

Scanned/reclaimed devicesThe device to be scanned or reclaimed must be a thin device that is being monitored by the TRU Monitor and have a TRU SDDF session.

When scanning or reclaiming, 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.

Space reclamation requires:

◆ A locally attached VMAX volume

◆ An indexed VTOC (recommended). Without it, temporary dataset processing does not occur, and the pool space size may not reflect a correct usage percentage.

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.



Thick R1 processing

Note: This feature is available under Enginuity 5876 and 5773. Starting with HYPERMAX OS 5977, thick devices are no longer used.

The TRU Monitor can provide you with the following:

◆ Reclaim processing on thin devices in thick-to-thin SRDF relationship.

◆ Monitoring of a thick R1 device only if a related thin R2 device is NOT bound with the PERSIST option.

Note: “BIND” on page 532 describes the BIND command and the PERSIST option.

◆ Reclaim processing in the SRDF/S and SRDF/A modes in all SRDF topologies, including Concurrent SDRF, cascades, and four-site configurations.

To enable this feature, use the SCF.TRU.THICKR1 initialization parameter, as described in “SCF.TRU.THICKR1” on page 132.

Scanning

You can run the scan task as part of a specified batch job to schedule the reclaim activity to fit into your schedule. This may be necessary if the device is being used on other LPARs and is not being monitored there.

Typically, the scan task only runs for a few seconds on a volume.

Scanning processScanning includes the following steps:

1. Obtaining the SYSVTOC RESERVE on the device.

2. Obtaining the VTOC free space information.

3. Applying each entry in the free space list to the TRU SDDF session.

4. Releasing the SYSVTOC RESERVE.



Reclaiming

IMPORTANT

The VMAX system does not start looking for tracks until the reclaim operation runs. The reclaim task erases tracks identified by either the z/OS Scratch Exit or the scan process, and starts the background task in the VMAX system. The Scratch Exit can directly mark tracks for reclaim, saving time and work in the reclaim process, or it can identify the tracks in the SDDF session for later reclaim processing.

Reclaiming processReclaiming occurs in a series of passes. For each pass, the program 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 SYSVTOC 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.

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.

Recommended settings

The reclaim activity impacts other device activity. EMC recommends the following settings:

◆ Limit the number of reclaim tasks that can be run simultaneously. To do this, use the SCF.TRU.RECLAIM.TASK.LIMIT initialization parameter described in “SCF.TRU.RECLAIM.TASK.LIMIT” on page 129.

◆ Limit the time-of-day operations with the SCF.TRU.RECLAIM.TIMELIMIT.LIST initialization parameter described in “SCF.TRU.RECLAIM.TIMELIMIT.LIST” on page 129.

◆ Limit the Scratch Exit-related wait time using the SCF.TRU.RECLAIM.SCRATCH.WAIT initialization parameter described in “SCF.TRU.RECLAIM.SCRATCH.WAIT” on page 126.

If a user batch job scratches a dataset, a new dataset may be allocated in its place. The specified wait time allows any new user allocation to occur before the reclaim operation attempts to reclaim the space.

◆ Allow the TRU Monitor to schedule the scan and reclaim tasks as started tasks (but not SCF subtasks) in order to limit the amount of time a volume is RESERVED and the overall impact on SCF processing. To do this, specify the STCNAME using the SCF.TRU.SCAN.STCNAME initialization parameter described in “SCF.TRU.SCAN.STCNAME” on page 130.



VMAX stress monitoringThe TRU Monitor allows you to monitor VMAX stress conditions.

To enable this feature, use the SCF.TRU.RECLAIM.STRESS.MONITOR initialization parameter, as described in “SCF.TRU.RECLAIM.STRESS.MONITOR” on page 127.

When enabled, all reclaim erases accept a code from the VMAX system indicating whether the erases are causing stress in the VMAX. If stress is encountered, the erase I/O activity is paced. A delay is introduced between the issuance of each erase I/O, and the delay grows the longer that the VMAX system is in stress. The maximum time between I/O's is controlled by the SCF.TRU.RECLAIM.STRESS.WAIT parameter described in “SCF.TRU.RECLAIM.STRESS.WAIT” on page 127.

Limitations◆ The z/OS Scratch Exit should be run on all LPARs attached to the VMAX system in order

to capture and record scratch activities. If it is not running on a LPAR that is scratching datasets on thin devices, the space is not automatically reclaimed.

◆ Due to allocation and SMF recording, when running the reclaim function as a subtask of SCF, the temporary dataset method is not used.

◆ Reclaim will not occur while a device has either active Clone, Snap, or virtual sessions.



Command reference

Syntax conventions


TRU,HELP

Displays a list of valid TRU commands.

Syntax

F emcscf,TRU,HELP

Parameters

emcscf


ExampleF emcscf,TRU,HELP

SCF5492I TRU commands are: Command Action ---------------------------- ----------------------------------------- DISABLE Disable TRU processing DISPLAY Display TRU information DISPLAY DEVICE ccuu[-ccuu] Display TRU device information ENABLE Enable TRU processing HELP Show valid TRU COMMANDS HOLD ccuu[-ccuu] Stop scheduling reclaim on device(s) RECLAIM ccuu[-ccuu] Schedule reclaim for device(s) REFRESH Reprocess INI and rebuild device tables RELEASE ccuu[-ccuu] Allow scheduling of reclaim for device(s) SCAN ccuu[-ccuu] Schedule scan for device(s) START ccuu[-ccuu] Allow monitoring of device(s) STOP ccuu[-ccuu] Stop monitoring of device(s)



TRU,DISABLE

Disables the TRU environment.

Syntax

F emcscf,TRU,DISABLE

Parameters

emcscf


ExampleF emcscf,TRU,DISABLE

SCF5480I TRU TRU,DISABLE SCF5481I TRU DISABLE COMMAND ACCEPTED SCF5417I TRU DISABLE COMMAND COMPLETED

F emcscf,TRU,DISPLAY

SCF5480I TRU TRU DISPLAY SCF5490I TRU ENVIRONMENT INFORMATION DISPLAY SCF5491I TRU HEADER AT: 190C18E0 SIZE: 000200 VERSION: 00 SCF5491I TRU >> DEVICE PROCESSING DISABLED << SCF5491I TRU SCAN HAS BEEN RUN 0 TIMES SCF5491I TRU ACTIVE SCAN TASK COUNT IS 0 SCF5491I TRU SCAN TASK LIMIT IS 10 SIMULTANEOUS TASKS SCF5491I TRU SCAN PGMNAME IS SCF5491I TRU RECLAIM HAS BEEN RUN 0 TIMES SCF5491I TRU ACTIVE RECLAIM TASK COUNT IS 0 SCF5491I TRU RECLAIM TASK LIMIT IS 10 SIMULTANEOUS TASKS SCF5491I TRU RECLAIM PGMNAME IS SCF5491I TRU RECLAIM WORK DATASET PREFIX IS SCF5491I TRU RECLAIM DATASET FACTOR IS 1000 SCF5491I TRU RECLAIM POST AT 0% OF DEVICE SIZE SCF5491I TRU MINIMUM VALUE IS 0 TRACKS, MAXIMUM VALUE IS 0 TRACKS SCF5491I TRU SCRATCH POST AT 0% OF DEVICE SIZE SCF5491I TRU MINIMUM VALUE IS 0 TRACKS, MAXIMUM VALUE IS 0 TRACKS SCF5491I TRU SCRATCH EXIT AUTO-RECLAIM IS DISABLED SCF5491I TRU WAIT TIME AFTER SCRATCH DISABLED SCF5491I TRU SYSVTOC SERIALIZATION FOR RECLAIM IS DISABLED SCF5491I TRU SYSVTOC SERIALIZATION MAX HOLD TIME IS DISABLED SCF5491I TRU SYSVTOC SERIALIZATION MIN WAIT TIME IS DISABLED SCF5491I TRU STRESS MONITORING IS DISABLED SCF5491I TRU RECLAIM TIME OF DAY LIMITS ARE NOT ENABLED SCF5498I TRU ENVIRONMENT INFORMATION DISPLAY COMPLETE SCF5481I TRU DISPLAY COMMAND ACCEPTED



TRU,DISPLAY

Displays information on the TRU environment, including most of the current settings.

Syntax

F emcscf,TRU,DISPLAY

Parameters

emcscf


ExampleF emcscf,TRU,DISPLAY

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

Displays information on the TRU environment and properties for the specified devices.

Syntax

F emcscf,TRU,DISplay,DEVice,ccuu[-ccuu]

Parameters

ccuu[-ccuu]

A device identified with its z/OS device number or a range of devices.

emcscf


ExampleF emcscf,TRU,DISPLAY,DEVICE,845C

SCF5480I TRU TRU,DISPLAY,DEVICE,845C 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 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



TRU,ENABLE

Enables the TRU environment.

Syntax

F emcscf,TRU,ENABLE

Parameters

emcscf


ExampleF emcscf,TRU,ENABLE

SCF5480I TRU TRU ENABLE SCF5481I TRU ENABLE COMMAND ACCEPTED SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.DSFACTOR ASSIGNED VALUE OF 1000 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.DSPREFIX ASSIGNED VALUE OF EMC.RECLAIM SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.PGMNAME ASSIGNED VALUE OF ESFTRURC SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.POST.MAX ASSIGNED VALUE OF 9999999 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.POST.MIN ASSIGNED VALUE OF 100 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.POST.PCT ASSIGNED VALUE OF 50 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.POST.TYPE ASSIGNED VALUE OF FREESPACE SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.SCRATCH.WAIT ASSIGNED VALUE OF 0 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.STRESS.WAIT ASSIGNED VALUE OF 5 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.SYSCALL.DELAY ASSIGNED VALUE OF 16000 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.SYSVTOC.HOLDLIMIT ASSIGNED VALUE OF 3000 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.SYSVTOC.TRKLIMIT ASSIGNED VALUE OF 150 SCF5416I TRU INI VALUE FOR SCF.TRU.RECLAIM.TASK.LIMIT ASSIGNED VALUE OF 10 SCF5416I TRU INI VALUE FOR SCF.TRU.SCAN.PGMNAME ASSIGNED VALUE OF ESFTRURC SCF5416I TRU INI VALUE FOR SCF.TRU.SCAN.TASK.LIMIT ASSIGNED VALUE OF 10 SCF5416I TRU INI VALUE FOR SCF.TRU.SCRATCH.POST.MAX ASSIGNED VALUE OF 9999999 SCF5416I TRU INI VALUE FOR SCF.TRU.SCRATCH.POST.MIN ASSIGNED VALUE OF 100 SCF5416I TRU INI VALUE FOR SCF.TRU.SCRATCH.POST.PCT ASSIGNED VALUE OF 50 SCF5416I TRU INI VALUE FOR SCF.TRU.SCRATCH.POST.TYPE ASSIGNED VALUE OF FREESPACE SCF5416I TRU INI VALUE FOR SCF.TRU.SCRATCH.RECLAIM ASSIGNED VALUE OF 20 SCF5417I TRU ENABLE COMMAND COMPLETED



TRU,HOLD

Places a hold on the specified devices to prevent their automatic reclamation.

Note: TRU,HOLD does not prevent manual reclamation process.

Syntax

F emcscf,TRU,HOLd,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


emcscf


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

Reclaims the specified devices.

Syntax

F emcscf,TRU,REClaim,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


emcscf


ExampleF emcscf,TRU,RECLAIM,845C

SCF5480I 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



TRU,REFRESH

Rescans the SCF device list and ensures that the TRU tables are up-to-date.

Syntax

F emcscf,TRU,REFRESH

Parameters

emcscf


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

Releases the specified devices for scanning or reclaiming.

Syntax

F emcscf,TRU,RELease,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


emcscf


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

Scans the specified devices.

Syntax

F emcscf,TRU,SCAn,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


emcscf


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

Starts monitoring appropriate devices, creates the SDDF session (if none exists) and schedules scanning for the specified devices.

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 emcscf,TRU,STArt,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


emcscf


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



TRU,STOP

Stops monitoring the devices and removes the SDDF session.

Syntax

F emcscf,TRU,STOp,ccuu[-ccuu]

Parameters

ccuu[-ccuu]


emcscf


ExampleF emcscf,TRU,STOP,845C-845F

SCF5480I 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


CHAPTER 18Pool Monitor User Exit


◆ Overview............................................................................................................... 642◆ Sample user exit ................................................................................................... 642◆ Parameters passed to user exit ............................................................................. 643

Pool Monitor User Exit 641

Pool Monitor User Exit

OverviewYou can specify a user exit for the THN Monitor, SDV Monitor, and DSE Monitor to call when a threshold is exceeded.


Sample user exitEMC provides a sample user exit in SCF.SAMPLIB(TSDVEXIT) and a link-edited version of the sample user exit in SCF.LINKLIB(TSDVEXIT).

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 the area containing the information passed to the user exit from the monitor. This area can be mapped using DSECT @MNUEXIT provided in SCF.SAMPLIB. The member name containing the mapping macro is ESFUXPRM.



Parameters passed to user exitThe monitor can pass the following types of parameters to the user exit:

◆ General information

◆ Interval information

◆ Percentage used

◆ Symmetrix system information

◆ Symmetrix system information from prior interval

◆ Pool information

◆ Pool information from prior interval

These fields are defined in DSECT @MNUEXIT provided in member ESFUXPRM in SCF.SAMPLIB.

General information

Table 28 lists parameters for general information. These parameters are always returned.

Table 28 Parameters for general information

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

MNUUCB@ UCB address of gatekeeper device

MNUSER12 Symmetrix system serial number

MNUUSER User storage kept by SCF

Parameters passed to user exit 643


Interval information

Table 29 lists parameters for interval information. These parameters are always returned.

Percentage used

Table 30 lists parameters for percentage used. These parameters are always returned.

Symmetrix system information

Table 31 lists parameters for Symmetrix system information. These parameters are returned for Symmetrix system intervals only.

Table 29 Parameters for interval information

Field Description

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

Table 30 Parameters for percentage used

Field Description

MNUPCT Percentage used for Symmetrix system or pool

MNUPPCT Percentage used from prior interval

Table 31 Parameters for Symmetrix system information

Field Description

MNU3380$ Current 3380 used percentage

MNU3390$ Current 3390 used percentage

MNUFBA$ Current FBA used percentage

MNU3390# Number of 3390 pool devices

MNU3390# Number of FBA pool devices

MNU3380# Number of 3380 pool devices

MNU3380FR Free tracks for 3380 devices

MNU3380US Used tracks for 3380 devices

MNU3390FR Free tracks for 3390 devices

MNU3390US Used tracks for 3390 devices

MNUFBAFR Free tracks for FBA devices

MNUFBAUS Used tracks for FBA devices



Symmetrix system information from prior interval

Table 32 lists parameters for Symmetrix system information from the prior interval. These parameters are returned for Symmetrix system intervals only.

Pool information

Table 33 lists parameters for pool information. These parameters are returned for pool intervals only.

Table 32 Parameters for Symmetrix system information from prior interval

Field Description

MNUP3380# Prior number of 3380 devices

MNUP3380$ Prior 3380 used percentage

MNUP3390# Prior number of 3390 devices

MNUP3390$ Prior 3390 used percentage

MNUPFBA# Prior number of FBA devices

MNUPFBA$ Prior FBA used percentage

MNUP3380F Prior 3380 free tracks

MNUP3380U Prior 3380 used tracks

MNUP3390F Prior 3390 free tracks

MNUP3390U Prior 3390 used tracks

MNUPFBAF Prior FBA free tracks

MNUPFBAU Prior FBA used tracks

Table 33 Parameters for pool information

Field Description

MNUPOOL Name of pool

MNUPOOL# ID number of pool

MNUPCNT Total number of devices in the pool

MNUPFREE Total free tracks on active devices

MNUPUSED Total used tracks on active devices

Parameters passed to user exit 645


Pool information from prior interval

Table 34 lists parameters for pool information from prior interval. These parameters are returned for pool intervals only.

Table 34 Parameters for pool information

Field Description

MNUPPOOL# Prior number of devices in pool

MNUPPOOLF Prior free tracks on active devices

MNUPPOOLU Prior used tracks on active devices


PART 3

LOCAL REPLICATION

This part describes ResourcePak Base features and components pertaining to local replication. This part contains the following chapters:

Chapter 19, “Managing zDP Processes,” describes Data Protector for z Systems (zDP) controls that you can use to monitor and manage your zDP environment.

647

CHAPTER 19Managing zDP Processes


◆ Introduction.......................................................................................................... 650◆ Running zDP processes ......................................................................................... 650◆ Command reference .............................................................................................. 651

Managing zDP Processes 649

Managing zDP Processes

IntroductionzDP (Data Protector for z Systems) is a z/OS based solution that automates SnapVX snapshot creation/deletion. It provides a granular level of mainframe asset protection so that a processing error, malicious intent, or human error may not cause a data center outage. zDP utilizes the concept of snapshots of EMC VMAX source volumes that allow applications to restore data at a more granular level. This granularity provides point-in-time recovery for both database and non-database systems.

For complete information about zDP, refer to the TimeFinder SnapVX and zDP Product Guide.

ResourcePak Base enables you to start and stop zDP run-time tasks by issuing a corresponding command. For example, you may need to STOP or PAUSE the zDP VDG to allow running SymmWin Online Configuration Changes that directly affect the zDP VDG devices (such as changing the CKD mapping information for the devices).

Other zDP controls are described in the TimeFinder SnapVX and zDP Product Guide.

Running zDP processesTable 1 lists zDP operations available via SCF.

Table 1 zDP operations

Operation Control

Start zDP process START command

Pause zDP process PAUSE command

Release zDP device locks RELEASEDEVICELOCK command

Restart zDP process RESUME command

Stop zDP process STOP command



Command referenceYou can control zDP run-time tasks by using commands issued to SCF. Note that the run-time task module (EIPZDP) must be available to the SCF task in a STEPLIB or LINKLIST dataset.

Syntax conventions


PAUSE

This command pauses zDP execution at the end of a cycle. Before entering a wait state for a RESUME, the device locks are released for all VDG devices.

SyntaxF emcscf,ZDP,PAUSE vdg_name

Parameters

vdg_name

Specifies the VDG. vdg_name is case-sensitive, consisting of 1-15 alpha-numeric characters. Special characters dash (-) and underscore (_) are allowed. Enclose the VDG name in single quotes if it contains a dash. For example:

VDG'LVVDG-P3'

RELEASEDEVICELOCK

This command allows zDP to release any device locks.

RELEASEDEVICELOCK can be used to release the zDP device locks after a failure. After the zDP locks are released, issue a zDP START command to start the VDG.

SyntaxF emcscf,ZDP,RELEASEDEVICELOCK vdg_name

Note: Valid command abbreviations are RELDEVLOCK, RELDLOCK, and RELD.

Parameters

vdg_name


VDG'LVVDG-P3'



RESUME

This command resumes zDP execution by obtaining device locks and continuing with the next cycle.

SyntaxF emcscf,ZDP,RESUME vdg_name

Parameters

vdg_name


VDG'LVVDG-P3'

START

This command starts a zDP process to begin snapset capture mode. The START command performs the following functions:

◆ Runs checks against the zDP environment:

• RACF is checked to ensure users have the right to start zDP.

• The number of snapshots available on each source volume is counted and an informational message specifies how many snapsets can be created for the specified VDG.

◆ Creates point-in-time snapshots of the VDG volumes on a defined interval. zDP initiates the snapset creation based upon the criteria previously specified by the definition utility statements.

◆ Manages the removal of existing snapsets when the limit is reached, based upon the policy defined by TERMinate_POLICY(OLDEST|STOP).

The START command generates snapset names in the following snapset_id format:

VDGnamexxxxxxxxYYDDDHHMMtcccccrr

Where:

For example: VDGMYE.........160301627S00001..

SyntaxF emcscf,ZDP,START vdg_name

VDGnamexxxxxxxx Specifies the VDG name. If the name is less than 15 characters, it is padded with periods.

YYDDDHHMM Specifies the snapset creation time, where YYDDD is the Julian date, HH is hours (0-23), and MM is minutes (0-59).

t Indicates the snapset type, where S = Saved, and C = Cyclical Create.

ccccc Specifies the zDP-managed cycle number, 1-99999.

rr Reserved for future use.



Parameters

vdg_name


VDG'LVVDG-P3'

STOP

This command stops a zDP process.

SyntaxF emcscf,ZDP,STOP vdg_name

Parameters

vdg_name


VDG'LVVDG-P3'


PART 4

REMOTE REPLICATION

This part describes ResourcePak Base features and components that you can use to manage and monitor your SRDF environment. This part contains the following chapters:

Chapter 20, “Monitoring SRDF/A (SRDF/A Monitor),” describes how to monitor and recover SRDF/A sessions using the SRDF/A Monitor.

Chapter 21, “Monitoring SRDF/A Write Pacing (WPA Monitor),” describes the WPA Monitor that enables you to monitor SRDF/A Write Pacing.

Chapter 22, “Managing SRDF/AR Processes,” describes how to start and stop SRDF/Automated Replication (SRDF/AR) processes.

Chapter 23, “Managing SRDF/A MSC,” provides information on managing SRDF/A Multi-Session Consistency (MSC) groups.

655

CHAPTER 20Monitoring SRDF/A (SRDF/A Monitor)


◆ Introduction.......................................................................................................... 658◆ Getting started...................................................................................................... 659◆ Monitoring SRDF/A sessions ................................................................................. 660◆ Command reference .............................................................................................. 669

Monitoring SRDF/A (SRDF/A Monitor) 657

Monitoring SRDF/A (SRDF/A Monitor)

IntroductionThe SRDF/A Monitor is designed to monitor the state of SRDF/A groups in your environment.

The SRDF/A Monitor performs the following functions:

◆ Discovers VMAX systems that are running SRDF/A and monitors the state of the SRDF/A groups.

Note: The SRDF Host Component for z/OS User Product Guide provides information on SRDF/A.

◆ Collects and writes SMF data about those VMAX systems.

Note: “SMF record format” on page 665 describes the SMF records created by the SRDF/A Monitor.

◆ Optionally, calls a user exit to perform user-defined actions when a change in the SRDF/A group state is detected.

Note: “Optional user exit” on page 665 describes the optional user exit.

◆ Optionally, invokes SRDF/A automatic recovery procedures to recover a dropped SRDF/A session.

Note: “SRDF/A Single Session Auto Recovery” on page 664 provides information on the SRDF/A Single Session Auto Recovery feature.



Getting started

Configuring SRDF/A Monitor

After installation of ResourcePak Base, enable and configure the SRDF/A Monitor and the SRDF/A Single Session Auto Recovery feature using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

Table 1 summarizes the SRDF/A Monitor initialization parameters:

Table 2 summarizes the initialization parameters of SRDF/A Single Session Auto Recovery:

Running SRDF/A Monitor

The SRDF/A Monitor runs as a subtask of ResourcePak Base (SCF). The SCF environment name for the SRDF/A Monitor is ASY.

Table 1 SRDF/A Monitor initialization parameters

Parameter Required/Optional

SCF.ASY.MONITOR Required

SCF.ASY.POLL.INTERVAL Required

SCF.ASY.SECONDARY_DELAY Required

SCF.ASY.SMF.POLL Required

SCF.ASY.SMF.RECORD Optional

SCF.ASY.USEREXIT Optional

Table 2 SRDF/A Single Session Auto Recovery initialization parameters


SCF.SS.AUTO.RECOVER Required

SCF.SS.AUTO.RECOVER.SymmID.srdfgrp Optional

SCF.SS.AUTO.RECOVER.BCV Required

SCF.SS.AUTO.RECOVER.BCV.SymmID.srdfgrp Optional

SCF.SS.AUTO.RECOVER.ITRK Required

SCF.SS.AUTO.RECOVER.ITRK.SymmID Optional

SCF.SS.AUTO.RECOVER.JOBNAME Required

SCF.SS.AUTO.RECOVER.JOBNAME.SymmID Optional

SCF.SS.AUTO.RECOVER.LPAR Required

SCF.SS.AUTO.RECOVER.MINDIR Required

SCF.SS.AUTO.RECOVER.MINDIR.SymmID Optional

SCF.SS.AUTO.RECOVER.PREFIX Required

SCF.SS.AUTO.RECOVER.PROC Required

Getting started 659


Monitoring SRDF/A sessions


SRDF/A Monitor operationsTable 3 lists SRDF/A Monitor operations.

Table 3 SRDF/A Monitor operations

Operation Control

Enable SRDF/A Monitor • ASY,ENABLE command• SCF.ASY.MONITOR initialization parameter

Set SRDF/A Monitor polling interval SCF.ASY.POLL.INTERVAL initialization parameter

Set SRDF/A Monitor secondary delay SCF.ASY.SECONDARY_DELAY initialization parameter

Enable SMF recording SCF.ASY.SMF.RECORD initialization parameter

Set multiplier for interval SMF records SCF.ASY.SMF.POLL initialization parameter

Specify user exit called upon SRDF/A group state change

SCF.ASY.USEREXIT initialization parameter

Refresh SRDF/A Monitor parameters ASY,REFRESH command

View SRDF/A Monitor status and options ASY,DISPLAY command

Disable SRDF/A Monitor • ASY,DISABLE command• SCF.ASY.MONITOR initialization parameter



SRDF/A Single Session Auto Recovery operationsTable 4 lists SRDF/A Single Session Auto Recovery operations.

Table 4 SRDF/A Single Session Auto Recovery operations

Operation Control

Enable auto recovery • ASY,SSAR,ENABLE command• SCF.SS.AUTO.RECOVER initialization parameter• SCF.SS.AUTO.RECOVER.SymmID.srdfgrp initialization parameter

Use manual mode SCF.SS.AUTO.RECOVER initialization parameter, MANUAL parameter

Initiate auto recovery for an SRDF group ASY,RECOVER,SRDFA command

Set count of invalid R1/R2 tracks to activate SRDF/A for session

• SCF.SS.AUTO.RECOVER.ITRK initialization parameter• SCF.SS.AUTO.RECOVER.ITRK.SymmID initialization parameter

Set the minimum count of online directors • SCF.SS.AUTO.RECOVER.MINDIR initialization parameter• SCF.SS.AUTO.RECOVER.MINDIR.SymmID initialization parameter

Set BCV gold copy management options • SCF.SS.AUTO.RECOVER.BCV initialization parameter• SCF.SS.AUTO.RECOVER.BCV.SymmID.srdfgrp initialization parameter

Disable BCV gold copy management for single recovery event

ASY,RECOVER,SRDFA command, NOBCV parameter

Define JCL auto-recovery procedure name SCF.SS.AUTO.RECOVER.PROC initialization parameter

Define auto recovery procedure job name • SCF.SS.AUTO.RECOVER.JOBNAME initialization parameter• SCF.SS.AUTO.RECOVER.JOBNAME.SymmID initialization parameter

Determine LPAR to run auto recovery procedure SCF.SS.AUTO.RECOVER.LPAR initialization parameter

Determine SRDF Host Component prefix for auto recovery procedure

SCF.SS.AUTO.RECOVER.PREFIX initialization parameter

Disable auto recovery • ASY,SSAR,DISABLE command• SCF.SS.AUTO.RECOVER initialization parameter

Monitoring SRDF/A sessions 661


Monitoring process

The SRDF/A Monitor performs the following steps:

1. When enabled, the SRDF/A Monitor queries the locally attached VMAX systems to determine if any SRDF/A sessions exist, either on the primary or secondary side of the SRDF configuration.

• 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 described in “SCF.ASY.POLL.INTERVAL” on page 43. When this time expires, the SRDF/A Monitor repeats the query.

• If the SRDF/A Monitor finds SRDF/A sessions, it proceeds to Step 2.

2. If SMF recording is enabled, the SRDF/A Monitor writes SMF records, including INTERVAL and ACTIVITY.

Note: You enable SMF records using the SCF.ASY.SMF.RECORD parameter described in “SCF.ASY.SMF.RECORD” on page 45. “SMF record format” on page 665 describes the SMF record format used by the SRDF/A Monitor.

If interval records are enabled (using with the SCF.ASY.SMF.POLL parameter described in “SCF.ASY.SMF.POLL” on page 44), the SRDF/A Monitor writes an INTERVAL record with every n polling periods.

3. If the SRDF/A Single Session Auto Recovery feature is enabled without using the manual mode, the SRDF/A Monitor attempts to recover all single-session SRDF/A groups (including groups of FBA devices) when the following conditions are met:

• The groups are not MSC-managed.

• The groups are SRDF/A groups.

• The group state has changed from active to inactive.

Note: You enable the SRDF/A Single Session Auto Recovery feature using the SCF.SS.AUTO.RECOVER parameter described in “SCF.SS.AUTO.RECOVER” on page 103. The manual mode is turned on using the MANUAL option of this parameter. “SRDF/A Single Session Auto Recovery” on page 664 provides information on the SRDF/A Single Session Auto Recovery feature.

If you limited the scope of SRDF/A Single Session Auto Recovery to a specific VMAX system or SRDF group, the SRDF/A Monitor attempts to recover the specified groups.

Note: You can limit the scope of SRDF/A Single Session Auto Recovery using the SCF.SS.AUTO.RECOVER.SymmID.srdfgrp parameter described in “SCF.SS.AUTO.RECOVER.SymmID.srdfgrp” on page 103.

4. The SRDF/A Monitor checks primary-side SRDF/A sessions for change of status.

The SRDF/A Monitor calls the specified user exit and passes data to it if one of the following occurs:

– An SRDF/A session changed its state from active to inactive or from inactive to active.



– The tolerance mode changes its state from ON to OFF or from OFF to ON.

– The calculated secondary delay is greater than or equal to the maximum value set using the SCF.ASY.SECONDARY.DELAY parameter.

Note: “Optional user exit” on page 665 describes optional user exits. “SCF.ASY.SECONDARY_DELAY” on page 44 describes the SCF.ASY.SECONDARY.DELAY parameter.

5. The SRDF/A Monitor determines whether you have issued a shutdown command.

• If the SRDF/A Monitor detects a shutdown command and there are no active single-session recovery sessions, then the SRDF/A Monitor terminates.

• If there are active single-session recovery sessions, the SRDF/A Monitor continues the polling process.

◆ The SRDF/A Monitor suspends for the period of time specified in the SCF.ASY.POLL.INTERVAL parameter. When this time expires, the SRDF/A Monitor repeats the query process described in “Monitoring process” on page 662.

Note: “SCF.ASY.POLL.INTERVAL” on page 43 describes the SCF.ASY.POLL.INTERVAL parameter.



SRDF/A Single Session Auto Recovery

When the SRDF/A Monitor is enabled, it detects SRDF/A group state changes. The SRDF/A Monitor determines and retains the current state of the SRDF/A group.

Note: If you disable the SRDF/A Monitor, the current SRDF/A state is not retained.

When the state of a non-MSC-managed SRDF/A group changes from active to inactive and SRDF/A Single Session Auto Recovery is enabled, the SRDF/A Monitor initiates the automatic recovery procedure.

Auto recovery is done for SRDF groups specified using the SCF.SS.AUTO.RECOVER.SymmID.srdfgrp initialization parameter described in “SCF.SS.AUTO.RECOVER.SymmID.srdfgrp” on page 103. If no group is specified, then all dropped SRDF/A groups are recovered.

Note: The SRDF/A Monitor checks each VMAX system and SRDF group it finds and then searches the SCF initialization file for a definition existing for that system or group. If no matching definition exists, automatic recovery by SRDF group is not performed.

If a group is inactive when the SRDF/A Monitor is enabled, SRDF/A Single Session Auto Recovery is not run for the group. In this case, recover the group manually using the ASY,RECOVER,SRDFA command described in “ASY,RECOVER,SRDFA” on page 672.

SRDF/A Single Session Auto Recovery supports BCV Phase 1 and 2 processing. You can specify BCV options at the VMAX system level and/or group level using the SCF.SS.AUTO.RECOVER.BCV and SCF.SS.AUTO.RECOVER.BCV.SymmID.srdfgrp initialization parameters described in “SCF.SS.AUTO.RECOVER.BCV” on page 104 and “SCF.SS.AUTO.RECOVER.BCV.SymmID.srdfgrp” on page 105.

Limitations◆ All VMAX systems must be locally attached.

◆ 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 SCF instances that share VMAX systems.

◆ SRDF/A Single Session Auto Recovery only applies to the primary side (R1) of your SRDF configuration. If multiple SCF instances have SRDF/A Single Session Auto Recovery enabled and a managed group drops, all of the SCF instances will try to recover it, causing unpredictable results. To avoid this, use group and LPAR specification parameters.

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

Note: The TimeFinder/Mirror for z/OS Product Guide describes BCVs.



◆ 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, check that the group is not specified for recovery, or set the SCF.SS.AUTO.RECOVER parameter to ENABLE(MANUAL), as described in “SCF.SS.AUTO.RECOVER” on page 103.

Optional user exit

You can make the SRDF/A Monitor call a user exit when the SRDF/A Monitor detects a change in activity.

You specify the use exit using the SCF.ASY.USEREXIT parameter, as described in “SCF.ASY.USEREXIT” on page 45. If you do not specify a value, no user exit is called.

EMC does not provide a user exit. Supply your own user exit based on the SCFRDFAX member of SCF.SAMPLIB. Member SCFRDFAX in SCF.SAMPLIB is a sample user exit. This sample includes the structure of the information that is passed to the user exit.

SMF record format

Macro members SRDFAUX1 and @RDFASMF in SCF.SAMPLIB define the structure of the SMF records. Both macros must be specified.

The supported SMF records for an individual SRDF/A group are presented in Table 5.

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

• 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 ACTIVEIndicates 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 Enginuity/HYPERMAX OS. Used by open systems host software only. (This is available only from the R1 side.)

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


Field Description



SRDFAUX1_MAX_THROTTLE_TIME Amount of time in seconds Enginuity/HYPERMAX OS 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/HYPERMAX OS 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 For Enginuity 5773, 5876 and HYPERMAX OS 5977, SRDFAUX1_SF1_RDFGRP is used instead of this field.

SRDFAUX1_SF1_RDFGRP This field contains the SRDF group number of the SRDF/A group.

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

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


Field Description



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/HYPERMAX OS 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



Command reference

Syntax conventions


ASY,DISABLEDisables the SRDF/A Monitor.

Note: The ASY,DISABLE command is not allowed while SRDF/A Single Session Auto Recovery sessions exist.

Syntax

F emcscf,ASY,DISABLE

Parameters

emcscf


ExampleF emcscf,ASY,DISABLE SCF1290I ASY,DISABLE SCF1291I ASY DISABLE COMMAND ACCEPTED. SCF1221I ASY MONITOR TASK DISABLED

ASY,DISPLAYDisplays the current status and options of the SRDF/A Monitor.

When a gatekeeper and SRDF group are specified, the status and options of the specified group are also displayed.

Syntax

F emcscf,ASY,DISPLAY[(gatekeeper,srdfgrp)]

Parameters

emcscf


gatekeeper


srdfgrp

The SRDF group represented by a one- or two-digit hex value.

ExampleF emcscf,ASY,DISPLAY SCF1290I ASY,DISPLAY SCF1291I ASY DISPLAY COMMAND ACCEPTED. SCF1220I ASY MONITOR TASK ENABLED



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 ASY task has not yet started, use the SCF.ASY.MONITOR initialization parameter, as described in “SCF.ASY.MONITOR” on page 43.

Syntax

F emcscf,ASY,ENABLE

Parameters

emcscf


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.

IMPORTANT

Issue the INI,REFRESH command before using the ASY,REFRESH command.

Note: If SRDF/A Single Session Auto Recovery is enabled and an auto recovery session is active, the parameters cannot be refreshed.

Syntax

F emcscf,ASY,REFRESH

Parameters

emcscf



F emcscf,ASY,REFRESHSCF1290I ASY,REFRESH SCF1291I ASY REFRESH COMMAND ACCEPTED. SCF1220I ASY MONITOR TASK ENABLED



ASY,SSAR,DISABLEDisables the SRDF/A Single Session Auto Recovery feature of the SRDF/A Monitor.

Note: “SRDF/A Single Session Auto Recovery” on page 664 describes SRDF/A Single Session Auto Recovery.

SRDF/A Single Session Auto Recovery cannot be disabled if an auto recovery session is active.

Syntax F emcscf,ASY,SSAR,DISABLE

Parameters

emcscf


Example F EMCSCF,ASY,SSAR,DISABLE

ASY,SSAR,ENABLEEnables the SRDF/A Single Session Auto Recovery feature of the SRDF/A Monitor.

Note: “SRDF/A Single Session Auto Recovery” on page 664 describes SRDF/A Single Session Auto Recovery.

SyntaxF emcscf,ASY,SSAR,ENABLE

Parameters

emcscf


Example F EMCSCF,ASY,SSAR,ENABLE



ASY,RECOVER,SRDFA

Initiates the SRDF/A Single Session Auto Recovery session for the specified group.

Use this command only for a single-session SRDF/A group that is inactive.

Syntax F emcscf,ASY,RECOVER,SRDFA(gatekeeper,srdfgrp)[,NOBCV]

Parameters

emcscf


gatekeeper


NOBCV

Disables BCV management for this recovery event only.

srdfgrp

The SRDF group represented by a one- or two-digit hex value.

ExampleF EMCSCF,ASY,RECOVER,SRDFA(F800,B9)


CHAPTER 21Monitoring SRDF/A Write Pacing (WPA Monitor)


◆ Introduction.......................................................................................................... 674◆ Getting started...................................................................................................... 675◆ Monitoring SRDF/A Write Pacing............................................................................ 676

Monitoring SRDF/A Write Pacing (WPA Monitor) 673

Monitoring SRDF/A Write Pacing (WPA Monitor)

IntroductionSRDF/A Write Pacing extends the availability of SRDF/A by enabling you to prevent conditions that can result in cache overflow.

The SRDF/A Write Pacing Monitor exposes relevant information regarding write pacing activities within the VMAX system. The data is collected at the SRDF/A group level by VMAX system, and at the device level by SRDF group and by VMAX system.

The data that can be collected and reported 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 SRDF/A group

◆ Total paced delay for the SRDF/A group

◆ Total paced track count for the SRDF/A group

The SRDF/A Write Pacing Monitor writes the collected information in SMF records.

Limitations

◆ All VMAX systems must be locally attached.

◆ Enginuity 5876 or HYPERMAX OS 5977 is required.

◆ Monitor state and count messages are only captured at the group level, but device- level statistics can be set to be included in SMF records.



Getting started

Configuring SRDF/A Write Pacing Monitor

After installation of ResourcePak Base, enable and configure the SRDF/A Write Pacing Monitor using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

Table 6 summarizes the initialization parameters associated with the SRDF/A Write Pacing Monitor:

Running SRDF/A Write Pacing Monitor

The SRDF/A Write Pacing Monitor runs as a subtask of ResourcePak Base (SCF). The SCF environment name for the SRDF/A Write Pacing Monitor is WPA.

Table 6 SRDF/A Write Pacing Monitor initialization parameters


SCF.WPA.EXCLUDE.CNTRL[.LIST] Optional

SCF.WPA.INCLUDE.CNTRL[.LIST] Optional

SCF.WPA.MONITOR Required

SCF.WPA.MSGLEVEL Optional

SCF.WPA.POLL.INTERVAL Optional

SCF.WPA.SMF Optional

SCF.WPA.SMF.FILTER Optional

SCF.WPA.SMF.RECORD Optional

SCF.WPA.STYPES Optional

Getting started 675


Monitoring SRDF/A Write Pacing


Table 7 lists SRDF/A Write Pacing Monitor operations.

Monitoring process

For each monitoring cycle, the SRDF/A Write Pacing Monitor performs the following steps:

1. The SRDF/A Write Pacing Monitor obtains a list of all local VMAX systems known to SCF.

2. From the list of VMAX systems, the SRDF/A Write Pacing Monitor eliminates all VMAX systems that are not under Enginuity 5876 or HYPERMAX OS 5977.

3. If there are any exclude parameters, the list of VMAX systems is trimmed by eliminating any that have all SRDF groups excluded. Statements failing validation are ignored.

4. All VMAX systems in the list are queried to report the write pacing statistics at the group or device level.

5. The write pacing statistics is filtered according to the user-defined filters.

Note: You can specify filters using the SCF.WPA.SMF.FILTER initialization parameter described in “SCF.WPA.SMF.FILTER” on page 137.

6. The exclude and include filtering of write pacing statistics is performed. Excludes are processed first followed by includes.

7. Based on the remaining write pacing statistics, the SRDF/A Write Pacing Monitor generates messages as specified by the SCF.WPA.MSGLEVEL initialization parameter described in “SCF.WPA.MSGLEVEL” on page 135.

8. If SMF recording is enabled, the information is written to SMF.

Table 7 SRDF/A Write Pacing Monitor operations

Operation Control

Enable or disable SRDF/A Write Pacing Monitor SCF.WPA.MONITOR initialization parameter

Select VMAX systems and SRDF groups to be monitored

• SCF.WPA.INCLUDE.CNTRL[.LIST] initialization parameter• SCF.WPA.EXCLUDE.CNTRL[.LIST] initialization parameter

Set SRDF/A Write Pacing Monitor polling interval SCF.WPA.POLL.INTERVAL initialization parameter

Select SRDF/A Write Pacing Monitor statistic types SCF.WPA.STYPES initialization parameter

Determine WTO message types issued by SRDF/A Write Pacing Monitor

SCF.WPA.MSGLEVEL initialization parameter

Enable or disable SMF recording SCF.WPA.SMF initialization parameter

Determine SMF record number used by SRDF/A Write Pacing Monitor

SCF.WPA.SMF.RECORD initialization parameter

Set SMF record filters SCF.WPA.SMF.FILTER initialization parameter



SMF record format

The SRDF/A Write Pacing 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.

The structure of the SMF records created by the SRDF/A Write Pacing Monitor is the same as those of the SRDF/A Monitor. Refer to “SMF record format” on page 665.

Monitoring SRDF/A Write Pacing 677

CHAPTER 22Managing SRDF/AR Processes


◆ Introduction.......................................................................................................... 680◆ Running SRDF/AR processes ................................................................................. 680◆ Command reference .............................................................................................. 681

Managing SRDF/AR Processes 679

Managing SRDF/AR Processes

IntroductionSRDF/AR (Symmetrix Remote Data Facility/Automated Replication) automates data copying across SRDF links to provide a logically consistent, restartable image of data at a remote (recovery) site in the event of a disaster at the production site.

SRDF/AR automatically propagates the restartable image of data to the recovery site in a manner transparent to the host application or database. The result is a series of consecutive data consistency points that you can use as the basis for restarting host applications at the recovery site.

For complete information about SRDF/AR, refer to the TimeFinder/Mirror for z/OS Product Guide.

ResourcePak Base enables you to start and stop the SRDF/AR process. Other SRDF/AR controls are described in the TimeFinder/Mirror for z/OS Product Guide.

Running SRDF/AR processesTable 8 lists SRDF/AR operations available via SCF.

Table 8 SRDF/AR operations

Operation Control

Start SRDF/AR process SAR,START command

Pause SRDF/AR process SAR,PAUSE command

Restart SRDF/AR process SAR,RESTART command

Stop SRDF/AR process SAR,STOP command



Command reference

Syntax conventions


SAR,PAUSE

Pauses the process and issues the BCVA058A message.

If the step# value is specified, the pause occurs before the next API call for the step. When specified without the step# _value, the pause occurs just before the next API call.

Note: You can also use the MODIFY PAUSE command of TimeFinder/Mirror to pause a process. For more information, refer to the TimeFinder/Mirror for z/OS Product Guide.

Syntax

F emcscf,SAR,PAUSE{(step#)},process-name

Parameters

emcscf


process-name

The name of the process. The value cannot exceed 20 characters.

If a process with the specified name does not exist, the statement fails.

step#

The number of the step at which to pause the 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



SAR,START

Starts the process at the beginning of the cycle.

Note: You can also use the MODIFY START command of TimeFinder/Mirror to pause a process. For more information, refer to the TimeFinder/Mirror for z/OS Product Guide.

Syntax

F emcscf,SAR,START,process-name

Parameters

emcscf


process_name



ExampleF emcscf,SAR,START,LRSAR1SCF0701I SAR,START,LRSAR1 SCF0702I SAR START COMMAND ACCEPTED. SCF0710I SAR PROCESS LRSAR1 STARTED

SAR,RESTART

Restarts a stopped process.

The restart point is determined by the previous STOP command. If the STOP command contained the FORCE keyword, restart may not be possible.

Note: You can also use the MODIFY RESTART command of TimeFinder/Mirror to pause a process. For more information, refer to the TimeFinder/Mirror for z/OS Product Guide.

Syntax

F emcscf,SAR,RESTART,process-name

Parameters

emcscf


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

When specified without additional parameters, the process is stopped when the current cycle step completes.

Note: You can also use the MODIFY STOP command of TimeFinder/Mirror to pause a process. For more information, refer to the TimeFinder/Mirror for z/OS Product Guide.

Syntax

F emcscf,SAR,STOP,process-name,[({NORMAL|FORCE|IMMEDiate|STEP[(step#)]})]

Parameters

emcscf


FORCE

The process is stopped immediately, regardless of the cycle state.

IMMEDiate

The process is stopped immediately. The process must be active for the STOP to take effect.

NORMAL

(Default) The process is stopped at the normal end of the cycle.

process-name



STEP[(step#)]

Stops the process at the current step or at the step specified as step#, providing that the step has not yet occurred in the SRDF/AR cycle. Otherwise, the SRDF/AR cycle stops at the end of the current cycle.

For example:

• If you specify STOP(STEP(03)) and SRDF/AR is at step 2 in the SRDF/AR cycle, SRDF/AR stops at the end of step 3.

• If you specify STOP(STEP(03)) and SRDF/AR is at step 4 or higher in the SRDF/AR cycle, SRDF/AR stops at the end of the current cycle.

ExampleF emcscf,SAR,STOP,LRSAR1,IMMED SCF0701I SAR,STOP,LRSAR1,IMMED BCVA042I Process LRSAR1 interrupted (STOP IMMED) SCF0711I SAR PROCESS LRSAR1 ENDED


CHAPTER 23Managing SRDF/A MSC


◆ Introduction.......................................................................................................... 686◆ Getting started...................................................................................................... 686◆ Controlling MSC environment ................................................................................ 687◆ Command reference .............................................................................................. 690

Managing SRDF/A MSC 685

Managing SRDF/A MSC

IntroductionMSC (Multi-Session Consistency) is an environment in SCF that ensures remote R2 consistency across multiple VMAX systems running SRDF/A. It provides coordination of SRDF/A cycle switches across systems.

Note: The SRDF Host Component for z/OS Product Guide describes MSC.

SRDF/A sessions can be grouped together as a single entity called an MSC group. The MSC group is defined through SRDF Host Component.

Note: The SRDF Host Component for z/OS Product Guide describes SRDF Host Component.

An MSC group can include up to 24 SRDF groups, and up to eight MSC groups per SCF instance can be active simultaneously.

ResourcePak Base enables you to query and control the MSC process. Other MSC controls are described in the SRDF Host Component for z/OS Product Guide.

Getting started

Configuring MSC

After installation of ResourcePak Base, enable and configure MSC using the SCF initialization parameters described in “ResourcePak Base initialization parameters” on page 36.

The MSC initialization parameters are as follows:

◆ SCF.MSC.ADCOPY.ONDROP

◆ SCF.MSC.AUTO.RECOVER.RETRY

◆ SCF.MSC.CYCLE.TIME.WARN

◆ SCF.MSC.ENABLE

◆ SCF.MSC.GTFUSR.RECID

◆ SCF.MSC.GTFUSR.TRACE

◆ SCF.MSC.MAX.LOCK.WAIT

◆ SCF.MSC.OVERWRITE

◆ SCF.MSC.PAVO

◆ SCF.MSC.SDDFQ.TODA

◆ SCF.MSC.SDDFQ.TOMF

◆ SCF.MSC.SDDFQ.TOOS

◆ SCF.MSC.VERBOSE


Managing SRDF/A MSC

Controlling MSC environment

Enabling MSC environment of SCF

When you enable the MSC environment of SCF, the MSC parameters are validated during SRDF Host Component initialization. The parameters can also be validated as the result of issuing the SC GLOBAL PARM_REFRESH command of SRDF Host Component.

If an MSC error was detected during validation, MSC is not allowed to start until the error is corrected and the SC GLOBAL PARM_REFRESH command of SRDF Host Component is issued. If you defined two or more MSC groups, none of them starts automatically. 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.

Basic operations

Table 9 lists basic MSC operations.

Table 9 Basic operations

Operation Control

Enable MSC • MSC,ENABLE command• SCF.MSC.ENABLE initialization parameter

View MSC status MSC,DISPLAY command

Disable MSC MSC,DISABLE command

Initiate takeover MSC,TAKEOVER

Deactivate MSC servers • MSC,DEACT command• MSC,DEACTREFRESH command• MSC,DEACTRESTART command• MSC,DEACTRESTARTTOSEC command• MSC,DEACTRESTARTTOZERO command

Restart MSC server • MSC,RESTART command• MSC,RESTARTTOSEC command• MSC,RESTARTTOZERO command

Refresh MSC group definition MSC,REFRESH command

Initiate dynamic adding of SRDF/Star devices MSC,ADDDEV command

Initiate dynamic deletion of SRDF/Star devices MSC,DELDEV command

Pend drop MSC,PENDDROP command

Controlling MSC environment 687

Managing SRDF/A MSC

SRDF Automatic Recovery

Table 10 lists SRDF Automated Recovery operations.

Tracing and messaging

Table 11 lists tracing and messaging operations.

Miscellaneous

Table 12 lists miscellaneous MSC operations.

Table 10 SRDF Automated Recovery operations

Operation Control

Initiate SRDF Automated Recovery MSC,RECOVER command

Set number of retries for SRDF Automated Recovery SCF.MSC.AUTO.RECOVER.RETRY initialization parameter

Table 11 Tracing and messaging operations

Operation Control

Enable MSC verbose messaging • MSC,VERBOSE command• SCF.MSC.VERBOSE initialization parameter

Enable or disable GTF USR tracing SCF.MSC.GTFUSR.TRACE initialization parameter

Set GTF USR record number SCF.MSC.GTFUSR.RECID initialization parameter

Table 12 Miscellaneous MSC operations

Operation Control

Routing SDDF queries • SCF.MSC.SDDFQ.TODA initialization parameter

• SCF.MSC.SDDFQ.TOMF initialization parameter

• SCF.MSC.SDDFQ.TOOS initialization parameter

Enable/disable use of Adaptive Copy after SRDF/A failure

SCF.MSC.ADCOPY.ONDROP initialization parameter

Set timing for VMAX lock SCF.MSC.MAX.LOCK.WAIT initialization parameter

Set timing for cycle delay check SCF.MSC.CYCLE.TIME.WARN initialization parameter


Managing SRDF/A MSC

MSC messages for Cascaded SRDF

If remote cycle switching is active, SCF messages for MSC contain 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 SRDF group for the synchronous leg when in a Cascaded SRDF configuration.

async_ra

A local SRDF/A SRDF group in SRDF/A MSC and SRDF/Star configurations, and is a remote asynchronous SRDF group when in a Cascaded SRDF configuration.

Controlling MSC environment 689

Managing SRDF/A MSC

Command reference

Syntax conventions


MSC,ADDDEV

Explicitly initiates SRDF/Star dynamic device adding for all or specific MSC sessions and MSC groups.

Note: MSC,ADDDEV is deferred if an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,ADDDEV[,SESSion(gatekeeper,[sync_srdfgrp,]async_srdfgrp)][,MSCGroup(msc_group)]

Parameters

emcscf


MSCGroup(msc_group)

Limits processing to the specified MSC groups.

msc_group

The MSC group. You can specify up to 8 groups, one at a time.

SESSion(gatekeeper,[sync_srdfgrp,]async_srdfgrp)

Limits processing to the specified MSC session only.

gatekeeper

The gatekeeper device identified with its z/OS device number.

sync_srdfgrp

The SRDF group for the synchronous leg of a cascaded MSC/Star configuration.

async_srdfgrp

The SRDF group for the asynchronous leg of a cascaded MSC/Star configuration.

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


Managing SRDF/A MSC

MSC,DEACT

Deactivates one of MSC servers in a high-availability MSC environment.

The MSC server does not perform any cycle switching and is no longer associated with the MSC groups.

However, the other MSC servers continue to be associated with the MSC groups.

If you issue this command and no other MSC server exists that performs cycle switching for the MSC groups, you can have SRDF groups in MSC but no server that does 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

emcscf


MSCGroup({msc_group|*})


msc_group


*

Represents all MSC groups.

RETAIN

Indicates that the MSC server being deactivated can be further restarted as a secondary server.

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 the SC GLOBAL,PARM_REFRESH command of SRDF Host Component. However, if you specify the RETAIN parameter with the MSC,DEACT command, MSC can be restarted as a secondary server via the MSC,RESTARTTOSEC command.

Note: The primary server is the server running with MSC_WEIGHT_FACTOR=0, as described in the SRDF Host Component for z/OS Product Guide. The secondary server runs on a different LPAR from the primary server at the primary site (Site A).


Managing SRDF/A MSC

Example 1F 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 2SCF1390I 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


Managing SRDF/A MSC

MSC,DEACTREFRESH

Stops the MSC server from cycle switching and makes the server ready for another MSC group.

This command is similar to the MSC,REFRESH command except that it deactivates the server instead of disabling it.

Note: MSC,DEACTREFRESH is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTREFresh[,MSCGroup({msc_group|*})]

Parameters

emcscf




msc_group


*


Example 1F 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


Managing SRDF/A MSC

Example 2This 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


Managing SRDF/A MSC

MSC,DEACTRESTART

Stops the MSC server from cycle switching and restarts cycle switching for the same MSC group.

This command is similar to the MSC,RESTART command except that it deactivates the server instead of disabling it.

Note: MSC,DEACTRESTART is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTREStart[,MSCGroup({msc_group|*})]

Parameters

emcscf




msc_group


*


Example 1

F emcscf,MSC,DEACTRESTART

SCF1390I 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


Managing SRDF/A MSC

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


Managing SRDF/A MSC

MSC,DEACTRESTARTTOSEC

Restarts the previous primary MSC server as a secondary server, running with MSC_WEIGHT_FACTOR=2.

Note: The SRDF Host Component for z/OS Product Guide provides information on the MSC_WEIGHT_FACTOR parameter.

MSC,DEACTRESTARTTOSEC is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTRESTARTTOSEC[,MSCGroup(msc_group)]

Parameters

emcscf




msc_group


*


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


Managing SRDF/A MSC

MSC,DEACTRESTARTTOZERO

Deactivates the MSC server running at MSC_WEIGHT_FACTOR > 0 and restarts it with MSC_WEIGHT_FACTOR=0.

Note: The SRDF Host Component for z/OS Product Guide describes the MSC_WEIGHT_FACTOR parameter.

In an SRDF/Star environment, the server takes over SDDF work.

IMPORTANT

Use DEACTRESTARTTOZERRO when there is no other MSC server running at MSC_WEIGHT_FACTOR=0.

MSC,DEACTRESTARTTOZERO is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DEACTRESTARTTOZERO[,MSCGroup(msc_group)]

Parameters

emcscf


MSCGroup(msc_group)


msc_group


Example 1F 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


Managing SRDF/A MSC

Example 2F emcscf,MSC,DEACTRESTARTTOZERO,MSCG(TEST_MSC1)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


Managing SRDF/A MSC

MSC,DELDEV

Explicitly initiates SRDF/Star dynamic device deletion.

When you issue the MSC,DELDEV command, the system searches for deleted devices 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, the SCF15D2I message is issued and the deletion process terminates.

Note: MSC,DELDEV is deferred if an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,DELDEV[,SESSion(gatekeeper,[sync_srdfgrp,]async_srdfgrp)][,MSCGroup(msc_group)]

Parameters

emcscf


MSCGroup(msc_group)

Limits processing to the specified MSC group.

msc_group


SESSion(gatekeeper,[sync_srdfgrp,]async_srdfgrp)

Limits processing to the specified MSC session only.

gatekeeper

The gatekeeper device identified with its z/OS device number.

sync_srdfgrp

The SRDF group for the synchronous leg of a cascaded MSC/Star configuration.

async_srdfgrp

The SRDF group for the asynchronous leg of a cascaded MSC/Star configuration.

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


Managing SRDF/A MSC

MSC,DISABLE

Disables the MSC environment.

When disabled, no MSC group definitions of SRDF Host Component are processed.

Note: You can also use the SCF.MSC.ENABLE=NO initialization parameter to disable MSC.

When multiple MSC groups are defined, an MSC,DISABLE command for a specific MSC group does not delete the MSC definition. An MSC,DISABLE command for all groups deletes the definition and disables 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

emcscf




msc_group


*


Example 1F emcscf,MSC,DISABLE

SCF1390I MSC,DISABLE SCF1391I MSC - DISABLE COMMAND ACCEPTED.SCF1321I MSC - TASK DISABLED


Managing SRDF/A MSC

Example 2This 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 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


Managing SRDF/A MSC

MSC,DISPLAY

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

SyntaxF emcscf,MSC,DISPLAY

Parametersemcscf


Example 1F 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

Example 2SCF1390I 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

“SQAR” is displayed for SQAR MSC groups. The primary SQAR group, MSCGA (the A-C leg) is the ConGroup-managed group and displays the ConGroup name.

Note: The Consistency Groups for z/OS Product Guide describes consistency groups.

The session information is similar to SRDF/Star; the first SRDF group (displayed just after the gatekeeper) is the asynchronous group, the next SRDF group is the recovery group, and the SRDF 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 VMAX system to each session, the R2 serial number displayed for the primary SQAR is the R2 recovery system 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 system.


Managing SRDF/A MSC

MSC,ENABLE

Enables the MSC environment.

After enabling, MSC waits for a MSC group definition from SRDF Host Component.

Note: You can also use the SCF.MSC.ENABLE=YES initialization parameter to enable MSC.

Syntax

F emcscf,MSC,ENAble

Parameters

emcscf


ExampleF emcscf,MSC,ENABLE

SCF1390I MSC,ENABLE SCF1391I MSC - ENABLE COMMAND ACCEPTED. SCF1320I MSC - TASK ENABLED


Managing SRDF/A MSC

MSC,PENDDROP

Waits until the end of the next cycle switch (the first) and issues an SRDF/A PENDDROP command to each SRDF group in the MSC group.

On the next cycle switch (the second), the cycle switch is performed and an immediately drop follows. On the next+1 cycle switch (the third), the MSC server determines 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 are 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 of SRDF Host Component, except that the command is performed for all SRDF groups in the MSC groups.

Note: MSC,PENDDROP is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,PENDDrop[,MSCGroup({msc_group|*})]

Parameters

emcscf




msc_group


*



Managing SRDF/A MSC

Example 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 2F 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 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


Managing SRDF/A MSC

MSC,RECOVER

Initiates SRDF Automated Recovery for the MSC environment.

Note: The SRDF Host Component for z/OS Product Guide describes SRDF Automated Recovery. EMC recommends that you use the SC RECOVER command of SRDF Host Component to perform automated recoveries.

Syntax formats

F emcscf,MSC,RECOVER[,MSCGroup(msc_group)][,NOBCV]

Parameters

emcscf


MSCGroup(msc_group)


msc_group


NOBCV

Disables BCV management for this recovery event.

Note: The TimeFinder/Mirror for z/OS Product Guide describes BCVs.


Managing SRDF/A MSC

MSC,REFRESHDiscards an existing MSC group definition and starts a different definition.

◆ When issued to a primary MSC server, the MSC,REFRESH command is equivalent to disabling and enabling the MSC environment.

◆ When issued to a secondary MSC server, the MSC,REFRESH command is equivalent to deactivating and enabling the MSC environment.

To send the new MSC group definition, you need to either start SRDF Host Component or perform the SC GLOBAL,PARM_REFRESH command of SRDF Host Component with the definition specified in the SRDF Host Component initialization parameters.

Note: MSC,REFRESH is not allowed while an MSC,TAKEOVER operation is in progress.

SyntaxF emcscf,MSC,REFresh

[,MSCGroup({msc_group|*})]

Parametersemcscf




msc_group


*


Example 1F 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


Managing SRDF/A MSC

Example 2This 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 SCF1321I MSC - TASK DISABLED SCF1320I MSC - TASK ENABLED SCF15F4I MSC - Processing for REFRESH command 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


Managing SRDF/A MSC

MSC,RESTART

Restarts an existing MSC group definition.

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 the MSC,DISABLE followed by the MSC,ENABLE command followed by the SC GLOBAL,PARM_REFRESH command of SRDF Host Component (without issuing 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

emcscf


MSCGroup(msc_group)


msc_group



Managing SRDF/A MSC

Example 1F 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

Example 2F 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


Managing SRDF/A MSC

MSC,RESTARTTOSEC

Restarts the previous MSC server as the secondary server running at MSC_WEIGHT_FACTOR=2 after a planned failover.


MSC,RESTARTTOSEC is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,RESTARTTOSEC[,MSCGroup(msc_group)]

Parameters

emcscf


MSCGroup(msc_group)


msc_group


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


Managing SRDF/A MSC

MSC,RESTARTTOZERO

Starts MSC as a primary server.

This is useful if the MSC group was not defined with MSC_WEIGHT_FACTOR=0, or after a failed MSC,DEACTRESTARTTOZERO command (if the MSC,DEACTRESTARTTOZERO command fails, any type of deactivate command is denied due to the “inactive” status of the MSC group).


MSC,RESTARTTOZERO is not allowed while an MSC,TAKEOVER operation is in progress.

Syntax

F emcscf,MSC,RESTARTTOZERO[,MSCGroup(msc_group)]

Parameters

emcscf


MSCGroup(msc_group)


msc_group


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


Managing SRDF/A MSC

MSC,TAKEOVER

Initiates a takeover of the SRDF/Star environment from a secondary MSC server.

Upon completion, MSC is registered to ConGroup and assumes control of the SRDF/Star SDDF sessions.

Note: The Consistency Groups for z/OS Product Guide describes ConGroup.

The MOVEOWNER command of ConGroup must be successfully performed before issuing the MSC,TAKEOVER command.

Syntax

F emcscf,MSC,TAKEOVER[,MSCGroup(msc_group)]

Parameters

emcscf


MSCGroup(msc_group)


msc_group


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


Managing SRDF/A MSC

MSC,VERBOSEEnables or disables verbose messaging for the MSC environment.

Use this command only when requested by EMC Customer Support.

Note: You can also use the SCF.MSC.VERBOSE=YES initialization parameter to enable MSC verbose messaging.

SyntaxF emcscf,MSC,VERBOSE,

{ON|OFF}[,MSCGroup(msc_group|*)]

Parametersemcscf




msc_group


*


OFF

Disables MSC/Star verbose messaging.

ON

Enables MSC/Star verbose messaging.

Example 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 SWITCHSCF1383I 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


Managing SRDF/A MSC


EMC Mainframe Enablers ResourcePak Base for z/OS · Mainframe Enablers and ResourcePak Base ......

Documents

Transcript of EMC Mainframe Enablers ResourcePak Base for z/OS · Mainframe Enablers and ResourcePak Base ......