Shared Virtual Array Administrator - Oracle Help Center

Shared Virtual Array

for OS/390

Configuration and AdministrationPart Number: 311290512

Version: 3.1

Administrator

Revision:N

Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, docs.sun.com, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

The OPEN LOOK and Sun� Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun�s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun�s written license agreements.

U.S. Government Rights�Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tous droits réservés.

Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie qui est décrit dans ce document. En particulier, et sans la limitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à http://www.sun.com/patents et un ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l�utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l�autorisation préalable et écrite de Sun et de ses bailleurs de licence, s�il y en a.

Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l�Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d�autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, Java, AnswerBook2, docs.sun.com, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d�autres pays.

Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d�autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.

L�interface d�utilisation graphique OPEN LOOK et Sun� a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d�utilisation visuelle ou graphique pour l�industrie de l�informatique. Sun détient une license non exclusive de Xerox sur l�interface d�utilisation graphique Xerox, cette licence couvrant également les licenciées de Sun qui mettent en place l�interface d �utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

LA DOCUMENTATION EST FOURNIE "EN L�ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L�APTITUDE A UNE UTILISATION PARTICULIERE OU A L�ABSENCE DE CONTREFAÇON.

We welcome your feedback. Please contact the Global Learning Solutions Feedback System at:

[email protected]

or

Global Learning SolutionsSun Microsystems Inc.One StorageTek DriveLouisville, CO 80028-3256USA

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Dynamic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Deleted Data Space Release (DDSR) . . . . . . . . . . . . . . . . . . . . . . . . 1-1SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Functional Differences between Subsystems . . . . . . . . . . . . . . . . . . . . 1-2Before You Begin Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Chapter 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Configuration Terms and Concepts . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Forming Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Draining Drive Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Reporting on the Status of a Drain . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Peer-to-Peer Remote Copy (PPRC) . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

SVAA Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6z/VM Requirements for PPRC . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7SVAA Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Standard Peer-to-Peer Remote Copy (PPRC) . . . . . . . . . . . . . . . . . . . 2-7Power PPRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Bridge Device Definition Requirements . . . . . . . . . . . . . . . . . . . . . . 2-8Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Snap to Primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

PPRCfcn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11PowerPPRC Bridge Devices and SCSI Devices . . . . . . . . . . . . . . . . 2-11System Adapter IDentifier (SAID) Values . . . . . . . . . . . . . . . . . . . 2-11

| World Wide Node Name (WWNN) Values for FICON Cascaded Switch| Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

PPRC Remote SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11PPRC Remote SnapShot Operational Requirements . . . . . . . . . . . . . 2-12PPRC Remote SnapShot Operational Considerations . . . . . . . . . . . . 2-13Performing PPRC Remote SnapShots . . . . . . . . . . . . . . . . . . . . . 2-13

For More Information about PPRC . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Parallel Access Volume (PAV) Support . . . . . . . . . . . . . . . . . . . . . . 2-15

First-Time User Considerations for PAV . . . . . . . . . . . . . . . . . . . . 2-15PAV Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . 2-17HCD Base but V2Xf Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17HCD Alias but V2Xf Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Static and Dynamic PAV Device Management . . . . . . . . . . . . . . . . 2-19PAV Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Refreshing SVAA Feature or Device Mapping Status on MVS . . . . . . . . . 2-21FlexVolumes and Large Volumes . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

FlexVolume Operational Requirements . . . . . . . . . . . . . . . . . . . . . 2-22Large Volume Operational Requirements . . . . . . . . . . . . . . . . . . . 2-23

November, 2006 — PN 311290512, Rev. N Contents iii

SnapShot and PPRC Considerations for FlexVolumes and Large Volumes 2-23

Chapter 3. SVAA in the OS/390 Environment . . . . . . . . . . . . . . . . . 3-1SVAA Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

SVAA Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2SVAA Initialization Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Issuing Subcommands from TSO . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Issuing Subcommands in SVAA Batch Jobs or Macros . . . . . . . . . . . . 3-4

Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Chapter 4. Using Deleted Data Space Release . . . . . . . . . . . . . . . . . 4-1Deleted Data Space Release (DDSR) . . . . . . . . . . . . . . . . . . . . . . . . 4-2Dynamic DDSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3DDSR and the SVAA Address Space . . . . . . . . . . . . . . . . . . . . . . . . 4-4Interval DDSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5DDSR Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7DDSR Device Selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10DDSR SIMULATE Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Chapter 5. Using SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Methods of Duplicating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Conventional DASD Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Duplication Using SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Invoking SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Snapping Functional Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Snapping Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7VSAM Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Net Capacity Load Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Using Volume Preferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10SnapShot Volume Selection and PPRC . . . . . . . . . . . . . . . . . . . . . . 5-10

Non-SMS Managed Environment . . . . . . . . . . . . . . . . . . . . . . . . 5-12SMS-Managed Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

SnapShot and DFSMSdss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14DFSMSdss Restriction for SnapShot on V2X, V2X2, and V2Xf . . . . . . . 5-14

Chapter 6. SVAA Configuration Tasks: An Outline . . . . . . . . . . . . . . 6-1Altering Subsystem Global Characteristics . . . . . . . . . . . . . . . . . . . . . 6-2Altering Channel Interface Characteristics . . . . . . . . . . . . . . . . . . . . . 6-2

Altering a Parallel Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Altering an ESCON Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Altering a FICON Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Altering a SCSI I/O Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Altering a Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Configuring Functional Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Defining a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Altering Characteristics of a Functional Device . . . . . . . . . . . . . . . . . 6-6Changing the Partition of a Functional Device . . . . . . . . . . . . . . . . . 6-6Changing the Device Type of a Functional Device . . . . . . . . . . . . . . . 6-7Deleting a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Disabling a CKD Functional Device . . . . . . . . . . . . . . . . . . . . . . . . 6-9Disabling a SCSI Functional Device . . . . . . . . . . . . . . . . . . . . . . . 6-9

Defining Additional Privileged ECAM Devices . . . . . . . . . . . . . . . . . . 6-10

November, 2006 — PN 311290512, Rev. Niv SVAA Configuration and Administration

Reconfiguring Subsystem Disk Array Capacity . . . . . . . . . . . . . . . . . . 6-11Allocating Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Establishing the Test Partition's Disk Array Capacity . . . . . . . . . . . . . 6-12Forming Additional Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Moving Disk Array Capacity from Test Partition to Production . . . . . . . 6-13Removing the Test Partition's Disk Array Capacity . . . . . . . . . . . . . . 6-13Reconfiguring an Existing Array . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Displaying the Drive Module Configuration . . . . . . . . . . . . . . . . . . . . 6-15Starting a Drain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15Reporting on Drain Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

| Configuring V2Xf PPRC with Cascaded FICON Switches in a WWNN Domain 6-15

Chapter 7. Using the SVAA Panels . . . . . . . . . . . . . . . . . . . . . . . . 7-1Using the SVAA Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Using the Command or Option Field . . . . . . . . . . . . . . . . . . . . . . . 7-2Entering SVAA Subcommands in the Command or Option Field . . . . . . . 7-2Entering Values on the Panels . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Using the Panel Commands and Function Keys . . . . . . . . . . . . . . . . 7-3

SVAA Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Session Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Setting Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Specifying Report Titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Subsystem Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Subsystem Component Selection . . . . . . . . . . . . . . . . . . . . . . . . 7-11Subsystem Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Subsystem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14SSID Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Channel Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20Configuring a Parallel Channel . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Configuring an ESCON Channel . . . . . . . . . . . . . . . . . . . . . . . . 7-27Configuring a SCSI I/O Interface . . . . . . . . . . . . . . . . . . . . . . . . 7-29Configuring a Fibre Channel Interface . . . . . . . . . . . . . . . . . . . . . 7-31Configuring a FICON Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32

Functional Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35Inserting a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Replicating a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . 7-48Initializing a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Updating a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56Deleting a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61

Browsing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . 7-67Drive Module Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68

Displaying Drive Module Status . . . . . . . . . . . . . . . . . . . . . . . . . 7-70Allocating Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73Forming Test Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76Forming Production Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79Moving Test Partition into Production Partition . . . . . . . . . . . . . . . . 7-82Draining Drive Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85

Displaying Event Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88Drive Module Drain Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91Media Acceptance Test Status . . . . . . . . . . . . . . . . . . . . . . . . . 7-93Media Acceptance Test Detail Status . . . . . . . . . . . . . . . . . . . . . 7-94

Specifying SnapShot Subcommands . . . . . . . . . . . . . . . . . . . . . . . 7-96Selecting a SnapShot Subcommand . . . . . . . . . . . . . . . . . . . . . . 7-96Specifying the Snap Dataset Subcommand . . . . . . . . . . . . . . . . . . 7-97

November, 2006 — PN 311290512, Rev. N Contents v

Specifying the Snap Volume Subcommand . . . . . . . . . . . . . . . . . 7-101Specifying the PPRC Remote SnapShot Volume Subcommand . . . . . 7-104

Chapter 8. SVAA Subcommands and Commands . . . . . . . . . . . . . . . 8-1Subcommands of SIBBATCH and SIBADMIN . . . . . . . . . . . . . . . . . . . 8-5

Executing Commands from SIBADMIN . . . . . . . . . . . . . . . . . . . . . . 8-5Executing Commands from SIBBATCH . . . . . . . . . . . . . . . . . . . . . 8-6Executing Macros from SIBADMIN . . . . . . . . . . . . . . . . . . . . . . . . 8-6

System Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Rules for Entering Subcommands and Parameters . . . . . . . . . . . . . . . . 8-7

Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Wildcard Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Subcommand Continuation . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

Redirecting Subcommand Output . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Subcommand Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11ALLOCATE SPARES Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-12

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Examples of ALLOCATE SPARES . . . . . . . . . . . . . . . . . . . . . . . 8-13

ALTER CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Parallel Channel: Syntax and Subcommand Usage . . . . . . . . . . . . . 8-14ESCON or FICON Channel: Syntax and Subcommand Usage . . . . . . 8-15SCSI Bus or Fibre Channel: Syntax and Subcommand Usage . . . . . . 8-15Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Examples of ALTER CHANNEL . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

ALTER DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Examples of ALTER DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28

ALTER SUBSYSTEM Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-29Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Examples of ALTER SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . 8-35

ATTN DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Examples of ATTN DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

DEFINE DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Examples of DEFINE DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-47

DELETE DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Examples of DELETE DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-52

DISPLAY CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-53Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53Examples of DISPLAY CHANNEL . . . . . . . . . . . . . . . . . . . . . . . 8-54

DISPLAY DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-55Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-55Examples of DISPLAY DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-57

DISPLAY NCL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59Example of DISPLAY NCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59

DISPLAY RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-60Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-60Examples of DISPLAY RELEASE . . . . . . . . . . . . . . . . . . . . . . . . 8-61

DROP Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62

November, 2006 — PN 311290512, Rev. Nvi SVAA Configuration and Administration

DROP ECAMDEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62DROP NONICEBERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62

FORM ARRAY Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63Examples of FORM ARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-64

INITIALIZE DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-65Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-65Example of INITIALIZE DEVICE . . . . . . . . . . . . . . . . . . . . . . . . 8-67

LISTCFG CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-68Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68Examples of LISTCFG CHANNEL . . . . . . . . . . . . . . . . . . . . . . . 8-69

LISTCFG DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-70Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-70Examples of LISTCFG DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-73

LISTCFG DRIVEMODULE Subcommand . . . . . . . . . . . . . . . . . . . . . 8-75Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-75Examples of LISTCFG DRIVEMODULE . . . . . . . . . . . . . . . . . . . . 8-77

LISTCFG SUBSYSTEM Subcommand . . . . . . . . . . . . . . . . . . . . . . 8-78Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-79Example of LISTCFG SUBSYSTEM for non-V2Xf subsystems . . . . . . . 8-80Example of LISTCFG SUBSYSTEM for V2Xf subsystems . . . . . . . . . 8-85

Definitions of LISTCFG Report Headings . . . . . . . . . . . . . . . . . . . . 8-110MACRO Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-115MOVE TESTPARTITION Subcommand . . . . . . . . . . . . . . . . . . . . . 8-116

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-116Example of MOVE TESTPARTITION . . . . . . . . . . . . . . . . . . . . . 8-116

| PPRCOPY Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-117| PPRCopy ESTPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-117| Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118| PPRCopy DELPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-121| Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-122| PPRCopy QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-123| Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-123| Example of PPRC QUERY DEVICE Output . . . . . . . . . . . . . . . . . 8-124| Example of PPRC QUERY PATHS Output . . . . . . . . . . . . . . . . . 8-125| Definitions of PPRC QUERY Report Headings . . . . . . . . . . . . . . . 8-126

QUERY Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128QUERY CACHEREFRESHRATE . . . . . . . . . . . . . . . . . . . . . . . 8-128QUERY CASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-129QUERY CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-129QUERY CMDECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-130QUERY CONFIGPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-130QUERY DEBUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-130QUERY DESTINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-131QUERY DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-131QUERY DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-132QUERY ECAMDEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-132QUERY IMPEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-132QUERY JAVA_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-133QUERY LOGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-133QUERY MAXRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-133QUERY NONICEBERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-134QUERY PAGESIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-134QUERY PARMLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-134QUERY PROFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-135

November, 2006 — PN 311290512, Rev. N Contents vii

QUERY SERVERIDLETIME . . . . . . . . . . . . . . . . . . . . . . . . . . 8-135QUERY SERVERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-135QUERY SERVERPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SERVERSCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SIBHOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SIBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SSNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-137QUERY SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-137QUERY TITLEn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-137QUERY VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138QUERY VOLUMEPREFERENCING . . . . . . . . . . . . . . . . . . . . . 8-138QUERY WEBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-139

RELEASE DYNAMICDATA Subcommand . . . . . . . . . . . . . . . . . . . 8-139Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-139Examples of RELEASE DYNAMICDATA . . . . . . . . . . . . . . . . . . 8-142

RELEASE INTERVALDATA Subcommand . . . . . . . . . . . . . . . . . . . 8-143Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-143Examples of RELEASE INTERVALDATA . . . . . . . . . . . . . . . . . . 8-147

REPORT EVENTS Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-148Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148Examples of REPORT EVENTS . . . . . . . . . . . . . . . . . . . . . . . 8-150

RESUME RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . 8-151Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-151Examples of RESUME RELEASE . . . . . . . . . . . . . . . . . . . . . . 8-152

SEND Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-152SEND DSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-152SEND SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-153SEND SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-153SEND SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-154SEND VOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-154

SET Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-155SET CACHEREFRESHRATE . . . . . . . . . . . . . . . . . . . . . . . . . 8-155SET CASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-160SET CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-160SET CMDECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-161SET CONFIGPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-161SET DEBUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-162SET DESTINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-162SET DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-163SET ECAMDEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-164SET IMPEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-164SET JAVA_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-165SET LOGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-165SET MAXRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-165SET NONICEBERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-166SET PAGESIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-166SET SERVERIDLETIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-166SET SERVERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-167SET SERVERPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-167SET SERVERSCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168SET SIBHOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168SET SIBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168SET SSNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-169SET TITLEn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-169SET VOLUMEPREFERENCING . . . . . . . . . . . . . . . . . . . . . . . 8-169

November, 2006 — PN 311290512, Rev. Nviii SVAA Configuration and Administration

SET WEBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-171SNAP DATASET Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-172

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-173Examples of SNAP DATASET . . . . . . . . . . . . . . . . . . . . . . . . . 8-184

SNAP VOLUME Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-185Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-186Examples of SNAP VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . 8-194

START Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START DSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-197START VOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-197

START DRAIN Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-198Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-198Examples of START DRAIN . . . . . . . . . . . . . . . . . . . . . . . . . . 8-200

START RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-201Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-201Examples of START RELEASE . . . . . . . . . . . . . . . . . . . . . . . . 8-201

STOP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP DSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP VOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-203

STOP RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-203Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-203Examples of STOP RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . 8-203

SUSPEND RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . 8-204Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-204Examples of SUSPEND RELEASE . . . . . . . . . . . . . . . . . . . . . . 8-205

VARY CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-205Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-205Examples of VARY CHANNEL . . . . . . . . . . . . . . . . . . . . . . . . 8-206

VARY DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-207Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-207Examples of VARY DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . 8-210

Appendix A. Drive Module Status . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B. SMF Record Formats . . . . . . . . . . . . . . . . . . . . . . . . B-1DDSR Record (Subtype 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1SnapShot Record (Subtype 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-7

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-9

November, 2006 — PN 311290512, Rev. N Contents ix

November, 2006 — PN 311290512, Rev. Nx SVAA Configuration and Administration

Figures

3-1. Sample REXX profile macro for SIBADMIN . . . . . . . . . . . . . . . 3-33-2. Sample CLIST for customizing PROFSIBA . . . . . . . . . . . . . . . . 3-33-3. SIBBATCH example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54-1. DDSR task interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74-2. Task definition for both Dynamic and Interval DDSR . . . . . . . . . . 4-97-1. SVAA main menu (SIBMM00) . . . . . . . . . . . . . . . . . . . . . . . 7-57-2. SVAA Session Administration menu (SIBPX00) . . . . . . . . . . . . . 7-67-3. SVAA Session Profile panel (SIBPX10) . . . . . . . . . . . . . . . . . 7-77-4. SVAA Report Titles panel (SIBPX20) . . . . . . . . . . . . . . . . . . 7-97-5. Subsystem Administration menu (SIBAX00) . . . . . . . . . . . . . . 7-107-6. Subsystem Component Selection menu (SIBAX10) . . . . . . . . . 7-127-7. Subsystem Selection panel (SIBAX05) . . . . . . . . . . . . . . . . . 7-137-8. Subsystem Configuration panel for non-V2Xf subsystems (SIBCA00) 7-157-9. Subsystem Configuration panel for the V2Xf (SIBCA00) . . . . . . . 7-16

7-10. SSID Definition panel (SIBCA01) . . . . . . . . . . . . . . . . . . . . 7-187-11. SSID Definition panel, using SSIDBASE (SIBCA01) . . . . . . . . . 7-197-12. Channel Type Selection panel (SIBCA11) . . . . . . . . . . . . . . . 7-217-13. Channel Selection panel—All channels except FICON (SIBCA10) . 7-217-14. Channel Selection panel—Parallel channels (SIBCA10) . . . . . . . 7-227-15. Channel Selection panel—ESCON channels (SIBCA10) . . . . . . 7-227-16. Channel Selection panel—SCSI channels (SIBCA10) . . . . . . . . 7-237-17. Channel Selection panel—Fibre channels (SIBCA10) . . . . . . . . 7-237-18. Channel Selection panel—FICON channels (SIBCA10) . . . . . . . 7-247-19. Channel Configuration panel—Parallel channel (SIBCA15) . . . . . 7-257-20. Channel Configuration panel—ESCON channel (SIBCA16) . . . . . 7-277-21. Channel Configuration panel—SCSI I/O interface (SIBCA17) . . . . 7-297-22. Channel Configuration panel—Fibre channel interface (SIBCA18) . 7-317-23. Channel Configuration panel—FICON channel (SIBCA19) . . . . . . 7-337-24. Functional Device Selection panel for non-V2Xf subsystems

(SIBCA20) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-367-25. Functional Device Selection panel for V2Xf subsystems (SIBCA20) 7-367-26. Insert Functional Device panel for non-V2Xf subsytems (SIBCA25) 7-427-27. V2X and V2X2 subsystems with FlexVolume support (SIBCA25) . . 7-427-28. Insert Functional Device panel for V2Xf subsystems (SIBCA25) . . 7-437-29. Replicate Functional Device panel for non-V2Xf subsystems

(SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-497-30. Replicate Functional Device panel for Base on V2Xf subsystem

(SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-497-31. Replicate Functional Device panel for Alias on V2Xf subsystem . . 7-507-32. Initialize Functional Device panel (SIBCA25) . . . . . . . . . . . . . . 7-557-33. Update Functional Device panel for non-V2Xf subsystems

(SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-577-34. Update Functional Device panel for Base device on V2Xf

subsystems (SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . 7-577-35. Update Functional Device panel for Alias on V2Xf subsystems

(SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-587-36. Delete Functional Device panel for non-V2Xf subsystems (SIBCA25) 7-637-37. Delete Functional Device panel for Base on V2Xf subsystem

(SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-637-38. Delete Functional Device panel for Alias on V2Xf subsystems

(SIBCA25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-647-39. Drive Module Utilities menu (SIBCU30) . . . . . . . . . . . . . . . . 7-69

November, 2006 — PN 311290512, Rev. N Figures xi

7-40. Display Drive Module Status panel (SIBAX20) . . . . . . . . . . . . 7-717-41. Display Drive Module Status panel—MAT partition (SIBAX25) . . . 7-727-42. Display Drive Module Status panel—Spares partition (SIBAX25) . . 7-727-43. Allocate Spares panel (SIBCU40) . . . . . . . . . . . . . . . . . . . 7-747-44. Form Test Array(s) panel (SIBCU50) . . . . . . . . . . . . . . . . . . 7-777-45. Form Production Array(s) panel (SIBCU50) . . . . . . . . . . . . . . 7-807-46. Move Test into Production panel (SIBCU60) . . . . . . . . . . . . . 7-837-47. Drain Drive Module(s) panel (SIBCU25) . . . . . . . . . . . . . . . . 7-867-48. Event Selection panel (SIBEV00) . . . . . . . . . . . . . . . . . . . . 7-897-49. Event Summary panel (SIBEV05) . . . . . . . . . . . . . . . . . . . 7-907-50. Drive Module Drain Status panel (SIBEV20) . . . . . . . . . . . . . 7-917-51. Drive Module Test (MAT) Status panel (SIBEV30) . . . . . . . . . . 7-937-52. Drive Module Test (MAT) Detail Status panel (SIBEV35) . . . . . . 7-947-53. SnapShot Subcommand Selection panel (SIBSS00) . . . . . . . . . 7-967-54. Specify Snap Dataset Subcommand panel (SIBSD00) . . . . . . . 7-977-55. Specify Snap Volume Subcommand panel (SIBSV00) . . . . . . . 7-1017-56. Specify PPRC Remote SnapShot Volume Subcommand panel

(SIBSV01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1048-1. Example of Display Channel subcommand (OS/390 master console) 8-548-2. Example of Display Channel subcommand (OS/390 master console) 8-548-3. Example of Display Device subcommand (OS/390 master console) 8-578-4. Examples of Display Device subcommand for PAV Devices . . . . . 8-588-5. Example of Display NCL subcommand (OS/390 master console) . . 8-59

| 8-6. Example of PPRC QUERY DEVICE Output . . . . . . . . . . . . . 8-124| 8-7. Example of PPRC QUERY PATHS Output . . . . . . . . . . . . . . 8-125

B-1. Format of Snap Dataset or Snap Volume SMF Record . . . . . . . . B-4

Tables

1-1. Functional differences between StorageTek disk storage subsystems 1-25-1. PPRC/SnapShot Interactions for Non-SMS Environment . . . . . . . 5-125-2. PPRC/SnapShot Interactions for SMS Environment . . . . . . . . . 5-137-1. SVAA panel commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47-2. Valid configuration entries for a parallel channel . . . . . . . . . . . 7-268-1. Valid configuration entries for a parallel channel . . . . . . . . . . . 8-17

| 8-2. System Adapter ID (SAID) Values for V2Xf and V2X . . . . . . . . 8-120A-1. Drive module status descriptions . . . . . . . . . . . . . . . . . . . . . A-1B-1. SVAA SMF record header format (SIBSMFHD) . . . . . . . . . . . . . B-1B-2. SVAA DDSR record format (SIBSMF05) . . . . . . . . . . . . . . . . . B-2B-3. SnapShot record format (Subtype 8) . . . . . . . . . . . . . . . . . . . B-4

November, 2006 — PN 311290512, Rev. Nxii SVAA Configuration and Administration

About This Book

Shared Virtual Array Administrator (SVAA) consists of programs that provideconfiguration, administration, and reporting facilities for the Shared Virtual Array(SVA) subsystem. This book describes how to use the configuration andadministration facilities of SVAA.

Note: Although this book generally mentions only OS/390, the SVAA for OS/390software runs identically on z/OS, OS/390, and MVS host operating systems.

Who Should Read This Book

This book is for the system programmers or storage administrators responsible forconfiguring and managing the SVA subsystem. To carry out these activities, youshould be familiar with OS/390 and direct access storage devices (DASD) in the hostenvironment you use.

Organization of This Book

The book is organized as follows:

A glossary, a list of acronyms and abbreviations, and an index appear at the backof the book.

Chapter 1, Introduction Introduces SVAA configuration and administration.

Chapter 2, Overview Describes some basic terms and concepts used inSVA subsystem configuration.

Chapter 3, SVAA in theOS/390 Environment

Describes the OS/390 environment for SVAA.

Chapter 4, UsingDeleted Data SpaceRelease

Describes the Deleted Data Space Release (DDSR)facility.

Chapter 5, UsingSnapShot

Describes the SnapShot facility.

Chapter 6, SVAAConfiguration Tasks: AnOutline

Lists the steps required to perform SVAA configurationtasks and the pages in this book where the steps areexplained in detail.

Chapter 7, Using theSVAA Panels

Provides detailed instructions in using the SVAApanels to configure the SVA subsystem.

Chapter 8, SVAASubcommands andCommands

Provides a reference, in alphabetical order, of theSVAA configuration and administration subcommands.

Appendix A, DriveModule Status

Provides a table of drive module status codes andtheir descriptions.

Appendix B, SMFRecord Formats

Presents the content of SMF records (that can beproduced when DDSR releases back-end storage).

November, 2006 — PN 311290512, Rev. N About This Book xiii

Conventions Used in This Book

This book uses the following conventions in subcommand and panel descriptions:

� Commands and values that you enter are shown in bold type (for example, SETECAMDEV).

� Uppercase letters in subcommand or parameter names indicate the requiredletters; the lowercase letters can be omitted. For example, ALTer CHANnelshows that ALT CHAN is the short form of the ALTER CHANNEL subcommand.

� In the panel descriptions, field names and key names are shown in bold type(for example, the Dates field, the Enter key).

For more details of the conventions, see “Subcommand Descriptions” onpage 8-11.

Notation Used in Syntax DiagramsThroughout this library, diagrams are used to illustrate the programming syntax.The following list tells you how to interpret the syntax diagrams:

� Read the syntax diagrams from left to right, from top to bottom, following thepath of the line.

The symbol indicates the beginning of a statement.

The symbol indicates that the statement syntax continues on the next line.

The symbol indicates that a statement is continued from the previous line.

The symbol indicates the end of a statement.

� Items shown on the main path of the statement are required.

��──KEYWORD──keyword_name───────────────────────────────────────────────────────��

� Items shown on branches below the main path are optional.

��──KEYWORD──keyword_name─ ──┬ ┬─────── ──┬ ┬─────── ────────────────────────────────�� └ ┘ ─ITEM1─ └ ┘ ─ITEM2─

� Items shown on branches above the main path are default values.

┌ ┐─ITEM1─��──KEYWORD──keyword_name─ ──┴ ┴─────── ───────────────────────────────────────────��

� Items appearing in a stack indicate that only one of the items can be specified.When one of the items in a stack appears on the main path, you must includeone of the items.

For example, in the following diagram, you must include either ITEM1 or ITEM2.ITEM3 and ITEM4 both appear below the main path, so neither one is required.

November, 2006 — PN 311290512, Rev. Nxiv SVAA Configuration and Administration

��──KEYWORD──keyword_name─ ──┬ ┬─ITEM1─ ──┬ ┬─────── ────────────────────────────────�� └ ┘─ITEM2─ ├ ┤─ITEM3─ └ ┘─ITEM4─

� A repeat arrow shown above an item or a stack of items indicates that you canspecify the item multiple times or specify more than one of the items. Acharacter (such as a comma or a blank) on the repeat arrow indicates that theitems must be separated by that character.

For example, in the following syntax diagram, you can specify both ITEM1 andITEM2, but you must use a blank to separate your choices in your programmingsyntax.

┌ ┐─ ───────��──KEYWORD──keyword_name─ ───� ┴┬ ┬─ITEM1─ ─────────────────────────────────────────�� └ ┘─ITEM2─

� In some cases, when an item has additional items associated with it, anadditional syntax diagram is shown that represents the full syntax of that item.For example, in the following syntax diagram, additional information that can ormust be specified for ITEM1 appears in the “ITEM1 Variables” syntax diagram.

��──KEYWORD──keyword_name──┤ ITEM1 Variables ├──ITEMS2──────────────────────────��

ITEM1 variables:├─ ──┬ ┬─variable1─ ────────────────────────────────────────────────────────────────┤ ├ ┤─variable2─ └ ┘─variable3─

Shared Virtual Array Documentation

This section lists both software documentation and hardware documentation for theShared Virtual Array products.

How to Obtain Software DocumentationAll of the Shared Virtual Array software publications are available:

� On the “SVA Software Publications” CD-ROM (part number 3134524nn). Toorder a copy, contact StorageTek Publication Sales and Service at800-436-5554 or send a fax to 303-661-7367.

� Online (for viewing and printing), at the StorageTek Customer Resource Center(CRC) web site at: www.support.storagetek.comClick on Software and go to the Shared Virtual Array Software list.

Note: Access to the CRC site requires a password. To obtain a password,call StorageTek Customer Support at 800-678-4430.

November, 2006 — PN 311290512, Rev. N About This Book xv

SVA Administrator Library:SVA Administrator for OS/390

� Shared Virtual Array Administrator for OS/390Configuration and Administration3112905nn

� Shared Virtual Array Administrator for OS/390Installation, Customization, and Maintenance3112908nn

� Shared Virtual Array Administrator for OS/390Reporting3112906nn

� Shared Virtual Array SnapShot for OS/390Installation, Customization, and Maintenance3112913nn

SVA Administrator for VM

� Shared Virtual Array Administrator for VMConfiguration and Administration3134629nn

� Shared Virtual Array Administrator for VMInstallation, Customization, and Maintenance3134631nn

� Shared Virtual Array Administrator for VMReporting3134630nn

SVA Administrator for OS/390 and VM

� Shared Virtual Array Administrator for OS/390 and VMMessages and Codes3112907nn

For any StorageTek Software:� Requesting Help from Software Support

1121240nn

SVA Hardware PublicationsShared Virtual Array hardware publications are available:

� Online (for viewing and printing), at the StorageTek Customer Resource Center(CRC) web site at: www.support.storagetek.comClick on Disk Subsystems.

Note: Access to the CRC site requires a password. To obtain a password,call StorageTek Customer Support at 800-678-4430.

V2Xf SVA Library:

� V2Xf Shared Virtual ArrayGeneral InformationMO9216x

November, 2006 — PN 311290512, Rev. Nxvi SVAA Configuration and Administration

� V2Xf Shared Virtual ArrayIntroductionMO9217x

� V2Xf Shared Virtual ArrayOperation and RecoveryMO9219x

� V2Xf Shared Virtual ArrayPlanningMO9218x

� V2Xf Shared Virtual ArrayReferenceMO9220x

� V2Xf Shared Virtual ArraySystem AssuranceMO9221x

� V2Xf Shared Virtual ArrayPeer-to-Peer Remote Copy Configuration Guide (PPRCfcn)MO9211x

V2X SVA Library:

� V2X Shared Virtual ArrayGeneral InformationMO9133x

� V2X Shared Virtual ArrayIntroductionMO9135x

� V2X Shared Virtual ArrayOperation and RecoveryMO9137x

� V2X Shared Virtual ArrayPlanningMO9136x

� V2X Shared Virtual ArrayReferenceMO9139x

� V2X Shared Virtual ArraySystem AssuranceMO9138x

� V2X Shared Virtual ArraySystem AssuranceMO9138x

V960 SVA Library:

� V960 Shared Virtual ArrayGeneral InformationMO5011x

November, 2006 — PN 311290512, Rev. N About This Book xvii

� V960 Shared Virtual ArrayIntroductionMO5006x

� V960 Shared Virtual ArrayOperation and RecoveryMO5007x

� V960 Shared Virtual ArrayPlanningMO5008x

� V960 Shared Virtual ArrayReferenceMO5009x

� V960 Shared Virtual ArraySystem AssuranceMO5010x

Peer-to-Peer Remote Copy for V2X, V2X2, and V960:

� Peer-to-Peer Remote CopyConfiguration GuideMP4007x

Trademarks

The following terms are trademarks or registered trademarks of Storage TechnologyCorporation:

� Iceberg� Shared Virtual Array

� SnapVantage � StorageTek � SVA

The following terms are trademarks or registered trademarks of InternationalBusiness Machines Corporation:

� DFSMS/MVS � DFSMS/VM � ESCON � FICON � IBM � MVS � OS/390 � RACF � RMF � VM/ESA � z/OS � z/VM

The following terms are trademarks or registered trademarks of MicrosoftCorporation:

� DOS � Excel � Windows

November, 2006 — PN 311290512, Rev. Nxviii SVAA Configuration and Administration

The following terms are trademarks or registered trademarks of SAS Institute,Incorporated:

� SAS � SAS/C � SAS/GRAPH

The following terms are trademarks of Sun Microsystems, Inc.:

� Solaris � Java

HP-UX is a trademark of Hewlett-Packard Company.

UNIX is a registered trademark of The Open Group.

Note: Other terms and product names used herein may be trademarks of theirrespective owners.

November, 2006 — PN 311290512, Rev. N About This Book xix

Product Support

StorageTek Customer Services provides 24-hour assistance for questions orproblems related to StorageTek products. Calls from our customers receiveimmediate attention from trained diagnostic specialists. Call 800-678-4430.

Refer to the document Requesting Help from Software Support for detailedinformation about contacting StorageTek for technical support in your country orgeographical location.

During problem resolution, Software Support may request that you provide specificdiagnostic materials. Although printed data might be acceptable, data inmachine-readable form is much preferred.

OS/390 Diagnostic Materials

Software Support may request one or more of the following kinds of diagnosticmaterials, depending on the nature of the problem:

� Details of circumstances � OS/390 SYSLOG� SYSMSG data set� SYSPRINT data set� SYSxDUMP and SYS1.DUMPnn data sets� SYSHIST data set (LOG OFFLOAD)

� Database DUMPS/DEBUG� EREP records (hardware and/or software)� ISPF panel images� ISPF panel names and SPFLOG� External trace for SVAA via GTF

� CCW I/O traces � SMF records� Listings of SVAA files altered during installation, including the PROFSIBS and

PROFSIBA macros� Copies of logging files� Output of SVAA started-task job� Console dump with: SDATA=(ALLPSA,SQA,LSQA,RGN,LPA,

TRT,CSA,SWA,SUMDUMP,ALLNUC,Q=YES,GRSQ)

November, 2006 — PN 311290512, Rev. Nxx SVAA Configuration and Administration

Summary of Changes

| Revision N, November 2006 -- EC 132753

| This revision:

| � Updates the Functional Differences table in Chapter 1.

| � Modifies the overviews of Standard Peer-to-Peer Remote Copy and PPRCfcn| in Chapter 2.

| � Describes how to configure V2Xf PPRC with cascaded FICON switches in| Chapter 6.

| � Adds support for the PPRCopy ESTPATH, DELPATH, and QUERY| subcommands in Chapter 8.

| All significant changes are identified by a vertical bar in the left margin.

Revision M, May 2006 -- EC 132661

This revision:

� Adds support for the Capacity on Demand (COD) feature.

� Updates the paragraph that references the SACLINK data set in the “IssuingSubcommands in SVAA Batch Jobs or Macros” section in Chapter 3.

All significant changes are identified by a vertical bar in the left margin.

Revision L, December 2005 -- EC 132488

This revision:

� Introduces documentation changes for Virtual Cylinder Gauge support in SVAA:

- Updates the Functional Differences table in Chapter 1.

- Updates the Subsystem Configuration and Functional Device Selectionpanel examples for V2Xf and non-V2Xf subsystems in Chapter 7, addingvirtual cylinder fields. The “Display-only fields” and “Column Headings”sections describe the new fields.

- Updates the Listcfg Subsystem example for V2Xf and non-V2Xfsubsystems in Chapter 8, adding virtual cylinder fields and a componentlevel field. The “Definitions of LISTCFG Report Headings” sectiondescribes the new fields.

- Adds a definition of virtual cylinder to the glossary.


November, 2006 — PN 311290512, Rev. N Summary of Changes xxi

Revision K, August 2005 -- EC 132346

This edition:

� Introduces documentation changes for PPRC Remote SnapShot support inSVAA:


- Adds an overview of PPRC Remote SnapShot in Chapter 2.

- Repeats some of the PPRC Remote SnapShot restrictions in Chapter 5.

- Updates the Specifying SnapShot Commands section in Chapter 7.

- Updates the SNAP VOLUME command syntax and adds an example of aPPRC Remote SnapShot command in Chapter 8.

� Moves information formerly in the Standard PPRC section to a new sectiontitled Peer-to-Peer Remote Copy (PPRC) in Chapter 2.

� Updates the FlexVolumes and Large Volumes section in Chapter 2.

� Adds notes about manual PAV changes in a dynamic PAV environment toChapters 2 and 8.

� Updates the Interval DDSR section in Chapter 4.

� Makes a minor correction to the description of the DEVCYLS parameter of theDefine Device subcommand in Chapter 8.

� Documents the addition of the DEBUG parameter to the RELEASEINTERVALDATA subcommand in Chapter 8.


Tenth Edition (Rev J), March 2005 -- EC 132026

This edition:

� Introduces documentation changes for configuration support of FlexVolumes(available today) and Large Volumes (SVAA support available today; microcodesupport available in a future release) in SVAA:


- Provides an overview of FlexVolumes and Large Volumes and explainsPPRC, SnapShot, and PAV restrictions with FlexVolumes and LargeVolumes in Chapter 2.

- Explains that FlexVolumes and Large Volumes do not change theoperation of DDSR in Chapter 4.

- Reiterates SnapShot restrictions with FlexVolumes and Large Volumes inChapter 5.

- Explains how to define FlexVolumes and Large Volumes in Chapters 6, 7,and 8.

- Adds the DEVCYLS parameter to the DEFINE DEVICE subcommand forFlexVolume and Large Volume support in Chapter 8.

November, 2006 — PN 311290512, Rev. Nxxii SVAA Configuration and Administration

� Adds a section on First-Time User Considerations for PAV in Chapter 2.

� Renames the section formerly titled Hardware Feature Enable/DisableConsiderations for SVAA to Refreshing SVAA Feature or Device MappingStatus on MVS in Chapter 2.

� Documents some Interval DDSR and PPRC considerations in Chapter 4.

� Documents removal of the requirement to specify the FORCE parameter whendeleting Alias devices that are related to an offline Base device that containsuser data.


Ninth Edition (Rev I), April 2004 -- EC 128971

This edition:

� Adds the RELOCATE parameter to the SNAP VOLUME subcommand.

� Updates the ALTER DEVICE and DEFINE DEVICE subcommands to add thenew PAVBASE parameter.

� Updates the QUERY DEVICE subcommand to indicate that the subcommanddoes not display information about PAV Alias devices.

� Updates the output generated by the LISTCFG SUBSYSTEM subcommand.

� Adds PAV support to the Functional Differences table on page 1-2.

� Updates the SET ECAMDEVICE subcommand to note that PAV Alias devicescan not be defined as ECAM devices.

� Describes the QUIET parameter which has been added to the DISPLAYDEVICE and LISTCFG DEVICE subcommands to limit the amount ofgenerated output.

� Updates the ALTER DEVICE AND DEFINE DEVICE subcommands to notethat the CACHE and DASDFASTWRITE parameters have no effect on V2Xfoperations or performance. If these parameters are specified, warningmessages are issued as a reminder, but the subcommands are not rejected.

� Updates the DISPLAY DEVICE subcommand to add the new PAV parameterto display PAV relationships. The PAV parameter of DISPLAY DEVICE shouldnot be confused with the PAVBASE parameter of the ALTER DEVICE andDEFINE DEVICE subcommands.

� Adds OFFLINE flag bytes to the SnapShot SMF record format in Appendix B.


Eighth Edition (Rev H), November 2003 -- EC 128861

This edition:

� Documents SVAA changes introduced with the release of the V2Xf SVA whichsupports only FICON connections. These changes consist of:

- Using the term “ESCON” rather than “serial” to describe a channel type

- Updating the Functional Differences table on page 1-2

November, 2006 — PN 311290512, Rev. N Summary of Changes xxiii

- Including the term “Detached Operator Panel” or “DOP” wherever the LocalOperator Panel or LOP is mentioned

- Including information regarding support of FICON channels

- Adding the COPYLIM field to the LISTCFG SUBSYSTEM output inChapter 8

- Adding the COPYLIM parameter to the ALTER SUBSYSTEMsubcommand in Chapter 8

- Adding a description of PPRCFCN in Chapter 2

� Updates the SnapShot sections for the ability to snap offline volumes.

� Updates instructions for deleting functional devices in Chapters 7 and 8.

� Corrects a field in the SnapShot SMF record format in Appendix B.

� Adds new fields to the DDSR and SnapShot SMF record formats in AppendixB.

� Includes new subcommands that pertain to the SVAA Server. The newsubcommands are:

- QUERY CACHEREFRESHRATE

- QUERY SERVERIDLETIME

- SET CACHEREFRESHRATE

- SET SERVERIDLETIME

� Updates the table on page 1-2 which describes the functions available ondifferent SVA subsystems.


Seventh Edition (Rev G), February 2003 -- EC 128687

This edition:

� Includes new subcommands that pertain to the SVAA Server. The newsubcommands are:

- QUERY WEBPORT

- SET WEBPORT

� Adds an overview of the Snap to Primary feature in Chapter 2.

� Updates some PPRC sections in Chapter 2.

� Includes minor corrections to the SEND DSR and STOP RELEASEsubcommands in Chapter 8.


November, 2006 — PN 311290512, Rev. Nxxiv SVAA Configuration and Administration

Sixth Edition (Rev F), September 2002 -- EC 128567

This edition:

� Documents SVAA changes introduced with the release of the V2X SVA. Theseconsist of:

- Increasing from 1024 to 4096 the maximum number of functional devicesthat can be defined within an SVA subsystem. This new number is notedwherever the maximum number of FDIDs is discussed in the text.

- Increasing the maximum number of SSIDs from 4 to 16. As noted below,this change is accommodated with a new ISPF panel and two newparameters in the ALTER SUBSYSTEM subcommand.

� Provides a table (page 1-2) that summarizes the functional differences betweenthe various generations of StorageTek disk storage subsystems. (The greaterFDID and SSID numbers are not available on earlier subsystems.)

� Adds, in Chapter 2, a section describing actions you must take to have SVAArecognize that the availability of a hardware feature has changed after anySnapShot, PPRC, or PPRCSnapShot feature has been enabled or disabled.

� Adds the SSID DEFINITIONS panel (page 7-17) and revises the SUBSYSTEMCONFIGURATION panel.

� Adds the SSIDBASE and VCUSSID parameters to the ALTER SUBSYSTEMsubcommand (page 8-27). With the next release of SVAA, the existing SSID0through SSID3 parameters will no longer be documented.

� Adds, as a new SVAA feature, a set of ISPF panels that enable you to issueSnapShot subcommands (SNAP DATASET and SNAP VOLUME) via thefull-screen interface (pages 7-83 to 7-90). To navigate to the new panels, aSNAPSHOT option is added to the SVAA main menu (page 7-5).

� Notes two restrictions on the use of the INIT parameter of the DEFINE DEVICEsubcommand: It's only for specifying SCSI devices, and cannot be used if youare running as an MVS guest under VM (page 8-37).

� Makes minor corrections and edits throughout the document.


Fifth Edition (Rev E), January 2002 -- EC 123350

This edition:

� Documents SVAA changes for the V960 SVA. These include:

- The 5+2 array size is eliminated. The only array size supported on theV960 is 13+2. To remind the user of this change, notes are added whereAltering the Subsystem Configuration and Forming Arrays are discussed inChapters 6, 7, and 8.

- The terms “Cache Size” and “NVS size” are used throughout reports,replacing a variety of terms that were used inconsistently.

Page 1-2 summarizes the functions that are unavailable on the V960 and 9500SVA.

November, 2006 — PN 311290512, Rev. N Summary of Changes xxv

� Adds notes that you can snap a SCSI volume to an OS/390 3390 volume if theSCSI volume has been initialized, but you cannot snap an OS/390 volume to aSCSI volume (pages 5-3 and 8-124).

� Adds notes that, with the V960 (just as with the 9500 SVA), you cannot FormTest Arrays or perform the Move Test Partition operation (several places inChapters 6, 7, and 8).

� Adds the FORCE parameter to the INITIALIZE DEVICE subcommand (page8-54).

� Adds to the explanations of the “Physical Cap Used (MB)” terms in reports,regarding the way values are affected by snap operations (page 8-71).

� Shows an increase in the maximum acceptable value for the RESERVELIMITparameter of the RELEASE INTERVALDATA subcommand (page 8-90). Themaximum amount of time for which the DDSR interval task can hold aRESERVE on a volume increases to 90 seconds.

� Includes several corrections and improvements in the text.


Fourth Edition (Rev D), April 2001 -- EC 123253

This edition does not contain technical changes or enhancements to the SVAAproduct. It does incorporate many corrections and improvements in the text.

November, 2006 — PN 311290512, Rev. Nxxvi SVAA Configuration and Administration

Chapter 1. Introduction

Shared Virtual Array Administrator (SVAA) helps you manage the Shared VirtualArray (SVA) subsystem. SVAA provides both a TSO command-line interface and anISPF full-screen interface for configuring and administering SVA subsystems. Withthese same interfaces, SVAA also enables you to collect data and generate reportsabout the performance of SVA subsystems and traditional DASD subsystems.

SVAA consists of:

� Dynamic Configuration

� Deleted Data Space Release (DDSR)

� SnapShot

� Data collection and reporting with Reporter

The first three of these facilities are the subject of this manual. The Reporter facilityis documented in the SVAA for OS/390 Reporting manual.

Dynamic Configuration

Dynamic Configuration enables you to define up to 4096 functional devices within asingle SVA subsystem. You can define the functional devices to emulate differentIBM and SCSI devices (3380 and 3390 device types), all within the samesubsystem. You can also define and intermix larger than normal functional devices,called Large Volumes, with smaller than normal functional devices, calledFlexVolumes, along with your normal sized functional devices in the samesubsystem. Using the facilities described in this manual, you can also reconfigurethe subsystem at any time to meet your needs.

Deleted Data Space Release (DDSR)

The Deleted Data Space Release (DDSR) facility informs the subsystem that agiven functional volume extent no longer contains any useful information and thecontents of the corresponding track images can be discarded. Thus, DDSR enablesSVA to reduce its net capacity load, take better advantage of its extended capacity,and achieve lower overall storage costs.

A complete discussion of the DDSR facility is presented in Chapter 4, “UsingDeleted Data Space Release.”

SnapShot

StorageTek's data duplication method, SnapShot, duplicates data sets or wholevolumes without physically moving any data. SnapShot creates only new pointersto the original data set or volume. This dramatically reduces the time required fordata duplication operations—backups, for example. Furthermore, no additionalphysical disk or cache space is used in making the duplicate. The two sets ofpointers treat the data as if it were two physically separate images. Updates canoccur simultaneously to the original data and to the duplicate.

Chapter 5, “Using SnapShot” provides a description of the SnapShot facility.

November, 2006 — PN 311290512, Rev. N Introduction 1-1

Functional Differences between Subsystems

Earlier StorageTek disk storage subsystems supported some functions that are notavailable on the current SVA model. SVAA 3.1 is compatible with those earlierproducts; thus, the functions are documented in this manual for compatibility. Thecharacteristics of some other functions have changed. Table 1-1 summarizesthese differences.

Table 1-1 (Page 1 of 2). Functional differences between StorageTek disk storage subsystems

FunctionDisk Storage Subsystem

9393 "K" 9500 SVA V960 SVAV2X / V2X2

SVAV2Xf/V2X4f

Form Test Arrays Only withmicrocodelevel below

K05.02.07.00

No No No No

Move drive modulesfrom Test partition toProduction partition

Only withmicrocodelevel below

K05.02.07.00

No No No No

Array sizes available 5+2, 13+2 5+2, 13+2 13+2 13+2 13+2

Maximum FDIDs 1024 3390-3sor 341

3390-9s

1024 3390-3sor 341

3390-9s

1024 3390-3sor 341

3390-9s

4096 3390-3sor 13653390-9s

4096 3390-3sor 13653390-9s

Range of FDIDs 0 to 3FF(0 to 1023)

0 to 3FF(0 to 1023)

0 to 3FF(0 to 1023)

0 to FFF(0 to 4095)

0 to FFF(0 to 4095)

Maximum SSIDs 4 4 4 16 16

SCSI DeviceSupport

No No Yes Yes No

Power PPRC Bridgedevices supported

No No Yes Yes No

PPRCfcn supported No No No No Yes

PPRC RemoteSnapShot

No No No Yes, withmicrocode

B01.10.xx.00and above

No

PAV support No No No No Yes

FlexVolume support No No No Yes, withmicrocode


Yes, withmicrocode

G01.04.xx.00and above

Large Volumesupport

No No No No Yes, withmicrocode


Virtual CylinderGauge support



Yes, withmicrocode


November, 2006 — PN 311290512, Rev. N1-2 SVAA Configuration and Administration

Introduction

Table 1-1 (Page 2 of 2). Functional differences between StorageTek disk storage subsystems

FunctionDisk Storage Subsystem

9393 "K" 9500 SVA V960 SVAV2X / V2X2

SVAV2Xf/V2X4f

Capacity onDemand Feature



Yes, withmicrocode


| PPRC Cascaded| FICON Switches| No| No| No| No| Yes, with| microcode| G02.03.xx.00| and above

Note: The level of microcode running on a specific subsystem is displayed at theLocal Operator Panel (LOP) or the Detached Operator Panel (DOP). SelectSoftware Release Level (FU11) screen. The microcode level may also be found inthe output of the SIBADMIN LISTCFG SUBSYS command under COMPONENTLEVEL of COMPONENT ID=SRL.

Media Acceptance Testing is not supported in SVAA. However, the MAT partitionstill exists, but only as a status for drive modules that have not been allocated asspares.

Before You Begin Configuration

Before you begin defining and updating your subsystem using SVAA, you mustcomplete a minimum subsystem configuration using the Local Operator Panel (LOP)or the Detached Operator Panel (DOP). The minimum configuration requires:

� Forming at least one production array.

� Defining at least one subsystem identifier (SSID) within the valid SSID ranges.The SSID must be unique among all your DASD subsystem IDs.

� Defining at least one privileged ECAM device.

� Configuring and enabling at least one channel accessible to the host operatingsystem.

In addition to the minimum configuration steps at the LOP or DOP, you must definethe SVA subsystem to the host through the I/O configuration program (IOCP) orhardware configuration definition (HCD).

Note: Each SVA subsystem must have a unique subsystem name.

See the V2Xf Shared Virtual Array: Operation and Recovery manual for LOP andDOP configuration procedures.

November, 2006 — PN 311290512, Rev. N Introduction 1-3

Introduction


Chapter 2. Overview

Chapter SummaryConfiguration Terms and Concepts . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Forming Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3The First Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Forming Additional Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Draining Drive Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Single Drive Module Drains . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Array Drains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Tray or DAU Drains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Reporting on the Status of a Drain . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Peer-to-Peer Remote Copy (PPRC) . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

SVAA Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6z/VM Requirements for PPRC . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7SVAA Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Standard Peer-to-Peer Remote Copy (PPRC) . . . . . . . . . . . . . . . . . . . 2-7Power PPRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Bridge Device Definition Requirements . . . . . . . . . . . . . . . . . . . . . . 2-8Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Setting Up a Power PPRC Direct Mode Environment . . . . . . . . . . . . 2-9Breaking Down a Power PPRC Direct Mode Environment . . . . . . . . . 2-9Setting Up a Power PPRC WAN Mode Environment . . . . . . . . . . . . 2-9Breaking Down a Power PPRC Direct Mode Environment . . . . . . . . 2-10

Snap to Primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

PPRCfcn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11PowerPPRC Bridge Devices and SCSI Devices . . . . . . . . . . . . . . . . 2-11System Adapter IDentifier (SAID) Values . . . . . . . . . . . . . . . . . . . 2-11

| World Wide Node Name (WWNN) Values for FICON Cascaded Switch| Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

PPRC Remote SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11PPRC Remote SnapShot Operational Requirements . . . . . . . . . . . . . 2-12

General Requirements for Source, Secondary, and Target Volumes . . 2-12Source Volume Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2-12Secondary Volume Requirements . . . . . . . . . . . . . . . . . . . . . . 2-13Target Volume Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2-13

PPRC Remote SnapShot Operational Considerations . . . . . . . . . . . . 2-13Performing PPRC Remote SnapShots . . . . . . . . . . . . . . . . . . . . . 2-13

For More Information about PPRC . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Parallel Access Volume (PAV) Support . . . . . . . . . . . . . . . . . . . . . . 2-15

First-Time User Considerations for PAV . . . . . . . . . . . . . . . . . . . . 2-15Non-PAV to PAV Migration Process . . . . . . . . . . . . . . . . . . . . . 2-16

PAV Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . 2-17HCD Base but V2Xf Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

ICKDSF Implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18HCD Alias but V2Xf Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Static and Dynamic PAV Device Management . . . . . . . . . . . . . . . . 2-19PAV Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Refreshing SVAA Feature or Device Mapping Status on MVS . . . . . . . . . 2-21FlexVolumes and Large Volumes . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

FlexVolume Operational Requirements . . . . . . . . . . . . . . . . . . . . . 2-22

November, 2006 — PN 311290512, Rev. N Overview 2-1

Large Volume Operational Requirements . . . . . . . . . . . . . . . . . . . 2-23SnapShot and PPRC Considerations for FlexVolumes and Large Volumes 2-23


Terms and Concepts

Configuration Terms and Concepts

This section describes some basic terms and concepts of the configuration process.

Forming ArraysArrays in the SVA subsystem consist of either 7 or 15 drive modules. An array with7 drive modules is described as a “5+2” configuration, while a 15-drive array has a“13+2” configuration. In either case, the first value refers to the portion (in terms ofa number of drive modules) of the array's capacity that is available for user data.The second value (“2” in both cases) refers to the portion that is used forredundancy data.

Thus, for example, a 13+2 array provides storage capacity equivalent to:

� 13 drive modules of user data and� 2 drive modules of redundancy data.

Note: You can define a 5+2 array only on the 9393 or 9500 SVA—not on the V2Xor V960 SVA.

The size of any array you form (5+2 or 13+2) is determined by the current ArraySize value for the subsystem. You can change the Array Size value with the ALTERSUBSYSTEM subcommand (see page 8-29) or the SUBSYSTEM CONFIGURATIONpanel (see page 7-15). However, you can override the current subsystem valuewith the FORM ARRAY subcommand (see page 8-63) or the FORM TEST ARRAYSpanel (see page 7-77) or FORM PRODUCTION ARRAYS panel (see page 7-80) at thetime you form a new array.

The First Array

Note: The first array (a Production array) is formed at the Local Operator Panel(LOP) or the Detached Operator Panel (DOP) as part of the initial minimumconfiguration.

To form the first array in the subsystem, 16 spare drive modules are required for a13+2 array; 8 are required for a 5+2 array. In either case, the extra drive isreserved as a spare for the entire subsystem.

Forming Additional Arrays

After the first array in the subsystem has been defined at the LOP or the DOP, thenumber of spare drive modules required to form an additional array depends uponthe current subsystem Array Size or, if you override it, the Array Size that youspecify when you form the array.

To form n arrays (after the first array), the number of available spare drive modulesrequired is:

(n x 7) + 1 to form “5+2” arrays, or

(n x 15) + 1 to form “13+2” arrays.


Terms and Concepts

PartitionsEach drive module, depending upon its status, belongs to one of five partitions:

� MAT � Spares � Test � Production � Unavailable

The term partition indicates the current use or availability of a drive module—not aphysical location. Each drive module's status is more precisely defined by atwo-character status code. All status codes are listed and described in Appendix A,“Drive Module Status.”

The partitions are described briefly as follows:

� MAT

The MAT partition consists of all newly installed drive modules and all drivemodules that have just been drained (see “Draining Drive Modules” onpage 2-5). Assignment to this partition occurs automatically in both cases.With the ALLOCATE SPARES subcommand, drives are moved from the MATpartition to the Spares partition for the purpose of forming arrays. Drivemodules in the MAT partition cannot be accessed by host programs.

� Production

The Production partition consists of one or more arrays used for storing andretrieving data.

� Test

The Test partition consists of one or more arrays used for storing and retrievingnon-critical data. This partition provides a way for you to test new drivemodules before moving them in the Production partition. Before you can forma Test array, a Production array must exist.

Note: You cannot form Test arrays on the V2Xf, V2X, V960, or 9500SVA—only on subsystems running earlier microcode. See “FunctionalDifferences between Subsystems” on page 1-2 for more information.

The Test partition is normally used only for system installation and verification.Test data is physically partitioned from production data, and access time fordata in the Test partition is not guaranteed to be comparable to that in theProduction partition.

� Spares

Drive modules in the Spares partition are used to form test and Productionarrays, to reconstruct failed disks, and to receive data from devices beingdrained.

� Unavailable

The Unavailable partition consists of any slot (physical location of a drivemodule) or drive module that is not under your immediate control. Thisincludes slots that have not been installed and slots that contain inactive orbroken devices.


Draining Drive Modules

Draining Drive Modules

A drain is the process of migrating data off one or more drive modules. When thedesignated drive modules have been successfully drained, they are placed in theMAT partition for removal or reallocation.

You can select drive modules to be drained in one of four ways:

� individually (by unit, tray, slot) � by array � by tray� by disk array unit (DAU)

Subsystem capacity must be sufficient to receive data to be drained. If availablecapacity is inadequate, the drain request is rejected.

Single Drive Module Drains

To be selected for draining, a drive module must be in the Production, Test, orSpares partition and in the active state; that is, its status must be PA, TA, or SA.Explanations of all drive module status codes appear in Appendix A, “Drive ModuleStatus.”

In a single drive module drain, all the data on the drive is moved to a spare drivemodule. Thus, for each Production or Test partition drive module to be drained, aspare drive module must be available. No spare drive is required to drain a spare,however; draining a spare is instantaneous.

Array Drains

In an array drain, all the data in the array is moved to other arrays in the partition.If FDIDs are defined for the partition there must be another array in the samepartition for the drain to be performed. If no FDIDs are defined for the partition, youcan drain the array.

Tray or DAU Drains

The method used to drain a tray or an entire DAU depends upon the number ofspares available in addition to the 1-spare minimum requirement.

� If, for each drive module in the DAU or tray to be drained, a spare drive isavailable outside that DAU or tray, each drive module is drained into one of thespares.

� If the number of available spares is inadequate, the process involves drainingarrays. In this case, drain activity may be observed in “associated” drivemodules—modules that are part of an array being drained, but that lie outsidethe “target” DAU or tray.

Note: You cannot drain a DAU or tray if a Test partition is defined. (This isbecause DAU and tray drains can involve draining multiple arrays—and all arraysincluded in any one drain must belong to the same partition.)


Reporting Status

Reporting on the Status of a Drain

SVAA allows you to generate a detailed report, by subsystem, of drain events. Youobtain event reports with either the REPORT EVENTS subcommand or the sequenceof event status panels.

The report shows detailed information for an event, such as the time and date ofthe request, percentage of the drain complete, and a list of the individual drivemodules involved.

Peer-to-Peer Remote Copy (PPRC)

Peer-to-Peer Remote Copy (PPRC) is a way to synchronously propagate DASDupdates from local primary volumes to remote secondary volumes of a like-devicegeometry. A primary volume and an associated secondary volume are called apair. PPRC pairs are established and de-established using TSO or ICKDSFcommands.

| The SVAA has been enhanced with PTF L2P00CX (MVS) and L2P00CY (VM) to| provide the new PPRC configuration command PPRCopy and subcommands| ESTPATH, DELPATH, and QUERY.

| These commands may be used to establish and terminate PPRC paths and to| query PPRC status. Previously, these commands were only available using TSO or| ICKDSF commands. Once a PPRC path has been established, the remainder of the| PPRC configuration (to establish pairs, freeze, recover, etc.) must be done using| TSO or ICKDSF commands.

SVAA RequirementsThe following requirements apply to both z/OS and z/VM environments:

� You cannot alter a channel interface that is used by a PPRC pair.

� You cannot alter a functional device that is part of a PPRC pair.

� You cannot delete a functional device that is part of a PPRC pair.

� You cannot alter an SSID on a subsystem on which PPRC is enabled. Youmust first delete all PPRC pairs and paths, have your hardware supportrepresentative disable the PPRCSnapShot hardware feature (if installed), andthen disable the PPRCfcn or PPRC hardware feature. After you alter the SSID,PPRC can be re-enabled for the subsystem and paths and pairs re-established.

Since this process may be highly disruptive to your operations, you may wantto devise an SSID numbering scheme that will not need to change over timeand that can accomodate the addition of new subsystems without the need todisrupt PPRC pairs and paths or the status of SVA hardware features.

� The PPRCfcn or PPRC hardware feature must be enabled before thePPRCSnapShot hardware feature can be enabled; conversely, thePPRCSnapShot hardware feature must be disabled before the PPRCfcn orPPRC hardware feature can be disabled.


Power PPRC

z/VM Requirements for PPRCThe following requirements apply to z/VM environments only:

� Your z/VM user directory must include the following statement to be able toissue PPRC path and pair establish and delete commands:

STDEVOPT DASDSYS DATAMOVER

See IBM's z/VM CP Planning and Administration for more information aboutthis requirement.

SVAA ConsiderationsSome important considerations for SVAA and PPRC operations are as follows:

� Do not issue a SET ECAMDEVICE subcommand against a PPRC primary orsecondary volume; i.e., do not try to define a PPRC volume as an ECAM device.

� Do not issue a TSO CESTPAIR command (or an ICKDSF PPRCOPY ESTPAIRcommand) against an ECAM device; that is, do not attempt to establish a PPRCpair that includes an ECAM device.

� Vary offline, to all systems, all volumes intended to become PPRC secondaryvolumes.

� You may wish to add all PPRC secondary volumes to the SVAA DeviceExclusion Table so that they are excluded from SVAA processing, however, beaware that such definitions would have to be undone to be able to accessthese volumes during a disaster recovery.

Note: DDSR processing is still performed on PPRC secondary volumes,although indirectly.

� In SMS-managed environments, define all PPRC secondary volumes to an SMSstorage group that is disabled for all new allocations.

Standard Peer-to-Peer Remote Copy (PPRC)

Standard PPRC

Standard PPRC is supported only on the StorageTek 9500; Power PPRC issupported on the StorageTek V960, V2X, and V2X2.

In general, users may see significantly shorter PPRC synchronization times for SVAvolumes than for volumes on traditional DASD.

Power PPRC

The standard version of PPRC is limited to ESCON distances of approximately 40kilometers, and suffers severe performance penalties if connected to a longdistance medium via a converter/multiplexer box. This is due to the extreme“chatty” nature of the ESCON protocol, inefficient use of the PPRC link, and thecurrent limitation on the speed of light.

Standard PPRC is supported only on the StorageTek 9500; Power PPRC issupported on the StorageTek V960 and V2X.

Power PPRC improves standard PPRC performance and may extend the distancelimit by using one of the following modes of operation:


Power PPRC

� Direct Mode -- still uses ESCON connections but improves performance byusing Data Bridge devices. These devices almost completely eliminate ESCON“chatter” by serving as staging areas for the continuous transmission of data.Direct Mode requires one Data Bridge device on each subsystem associated ina peer-to-peer relationship.

� WAN Mode -- improves PPRC performance by using Data Bridge devices, butalso increases distance limits by using multiplexers and long distancehigh-speed communication lines like T1/T3. Status Bridge devices are used totransmit acknowledgments that data was successfully received. WAN Moderequires one Data Bridge device and one Status Bridge device on eachsubsystem associated in a peer-to-peer relationship.

Power PPRC also surpasses standard PPRC through the concept of a Bridge pair, aPPRC pair between two Bridge devices. Think of data traffic between eachstandard PPRC pair as driving on a two-lane road, stuck behind a large,slow-moving truck.

With Power PPRC, a Data Bridge pair acts like a multi-lane interstate highway for allstandard PPRC pairs between two subsystems, letting you get to your destinationfaster, more efficiently, and with less aggravation.

Bridge Device Definition RequirementsBridge devices are subject to the following requirements:

� Bridge devices must be defined to the operating system and hardware usingHCD and IOCP. It is recommended that all Bridge devices be defined to beoffline to avoid operator intervention at IPL time.

CAUTION:Bridge devices are not intended for use as data storage devices. Youshould not attempt to ICKDSF initialize and/or vary any Bridge deviceonline to a host operating system, since all user and system data (e.g.,VTOCs) can be destroyed during the establishment of a Power PPRCBridge pair.

� A previously unused FDID must be used to define a Bridge device. The newDATABRIDGE and STATUSBRIDGE parameters of the DEFINE DEVICEsubcommand must be used to specify the type of Bridge device to be defined.

� FDIDs already in use cannot be modified for use as Bridge devices.

� If you want to use a specific FDID as a Bridge device and it is already in usefor data storage, first move the data elsewhere, then delete and redefine thedesired FDID as a Bridge device of the appropriate type.

� A Data Bridge device must be defined as a 3390-9 CKD device.

� A Status Bridge device must be defined as a 3390-3 CKD device.

� Bridge devices must be defined with CKDENABLE(YES) andCKDREADWRITE(YES) attributes (which are the defaults) to be able tosuccessfully establish a Bridge pair.

� Bridge devices cannot be defined as Large Volumes or FlexVolumes.


Power PPRC

Operational ConsiderationsTo use Power PPRC, there are only a few operational considerations to be awareof. The principal consideration is that Bridge pairs must be established first, anddeleted last.

Other considerations are reflected in the following sample operational proceduresprovided as a general guide for implementing Power PPRC at your site.

Setting Up a Power PPRC Direct Mode Environment

� Define one Data Bridge device on subsystem A and another on subsystem B.

� Establish a PPRC path from subsystem A to subsystem B using the CESTPATHcommand.

� Establish a Bridge pair between the Data Bridge devices using the CESTPAIRcommand.

� Determine which data storage devices on each subsystem are to be used toestablish PPRC pairs (and remember that data on the Secondary device can beoverwritten when the pair is established!).

� Establish PPRC pairs between the desired devices using the CESTPAIRcommand.

Breaking Down a Power PPRC Direct Mode Environment

� Delete all PPRC pairs between non-Bridge devices using the CDELPAIRcommand.

� Delete the Bridge pair between the Bridge devices using the CDELPAIRcommand.

� Optionally, delete the PPRC path from subsystem A to subsystem B using theCDELPATH command.

Setting Up a Power PPRC WAN Mode Environment

� Define one Data Bridge device on subsystem A and another on subsystem B.

� Define one Status Bridge device on subsystem A and another on subsystem B.

� Establish two PPRC paths from subsystem A to subsystem B using theCESTPATH command. Two paths are required—one for Data Bridge use andthe other for Status Bridge use.

� Establish a Bridge pair between the Data Bridge devices using the CESTPAIRcommand. This also implicitly reverses the direction of one of the PPRC pathsso that now one path is from subsystem A to subsystem B for the Data Bridge,and the other path is from subsystem B to subsystem A for the Status Bridge.The Status Bridge pair is then implicitly established.

� Determine which data storage devices on each subsystem are to be used toestablish PPRC pairs (and remember that data on the Secondary device can beoverwritten when the pair is established!).

� Establish PPRC pairs between the desired devices using the CESTPAIRcommand.


Snap to Primary

Breaking Down a Power PPRC Direct Mode Environment

� Delete all PPRC pairs between non-Bridge devices using the CDELPAIRcommand.

� Delete the Bridge pair between the Bridge devices using the CDELPAIRcommand. This also implicitly deletes the Status Bridge pair and reverses theStatus Bridge path from subsystem B to subsystem A so that it once againappears as it was originally established from subsystem A to subsystem B.

� Optionally, delete the two PPRC paths from subsystem A to subsystem B usingthe CDELPATH command.

Snap to Primary

Before the PPRCSnapShot hardware feature and Snap to Primary becameavailable, data could only be snapped between two non-PPRC (simplex mode)devices or from a PPRC Primary device to a simplex device, but never from asimplex device to a PPRC Primary device.

With the PPRCSnapShot hardware feature but without Snap to Primary, data canbe snapped between two non-PPRC (simplex mode) devices or from one PPRCPrimary device to another PPRC Primary device when both pairs are established tothe same secondary StorageTek V960 or V2X.

When both the PPRCSnapShot hardware feature and Snap to Primary are present,all of the previously mentioned capabilities are supported plus the new capability ofsnapping data from non-PPRC simplex devices to PPRC Primary devices.

Note: The PPRCSnapShot hardware feature is a pre-requisite for Snap to Primary.

Operational ConsiderationsSnap to Primary has only one operational consideration to be aware of. Multiplesuccessive Snap to Primary operations to the same PPRC Primary may experiencefailures when the PPRC Primary is in the Duplex Pending state. This considerationapplies to both data set and volume level Snap to Primary operations to the samePPRC Primary volume.

You can choose to wait until the PPRC pair has returned to the Duplex state beforeattempting the next Snap to Primary or use the following technique:

1. Establish the appropriate PPRC paths as you normally would.

2. Establish the appropriate PPRC pairs and allow them to fully synchronize intothe Duplex state.

3. Suspend the appropriate PPRC pairs.

4. Execute Snap to Primary operations to the suspended PPRC Primaries.

5. Resynchronize (unsuspend) the PPRC pairs using the CESTPAIR commandwith the MODE(RESYNC) parameter and allow them to fully synchronize intothe Duplex state.

6. Re-suspend the appropriate PPRC pairs.

7. Repeat steps 4-6 as needed.


PPRC Remote SnapShot

PPRCfcn

PPRCfcn replaces Standard PPRC and PowerPPRC and is supported only on the| V2Xf/V2X4f. PPRCSnapShot continues to be a separate feature and includes| support for the Snap to Primary and Remote SnapShot functions.

PPRCfcn is neither pure FICON nor pure Fibre Channel. Instead, it is aStorageTek-proprietary, upper-level protocol based on both. As such, PPRCfcnnatively supports longer point-to-point distances than ESCON. PPRCfcn alsoperforms significantly better than ESCON due to less channel overhead and theincreased size of data frames.

PowerPPRC Bridge Devices and SCSI DevicesPowerPPRC Bridge devices and SCSI devices are no longer supported on the V2Xf.If you plan to upgrade an existing V2X or V2X2 subsystem to a V2Xf, you mustperform the following before first starting the hardware upgrade:

1. Delete all non-Bridge PPRC pairs on the affected V2X or V2X2

2. Delete all Bridge PPRC pairs on the affected V2X or V2X2

3. Delete all PPRC paths on the affected V2X or V2X2

4. Delete all Bridge devices

Note: Failure to delete all Bridge devices before the hardware upgrade will resultin the inability to IML the V2Xf. A backout of the hardware upgrade, deletion of allBridge devices, and a repeat of the hardware upgrade is then required to recoverfrom this condition.

System Adapter IDentifier (SAID) Values| The System Adapter IDentifier (SAID) values are specified in the LINKS parameter| of the SVAA PPRCopy ESTPATH command and are different between V2X and| V2Xf models. See Table 8-2 on page 8-120 for the SAID values defined for SVA| devices.

| The SAID values are also used when you are configuring PPRC ICKDSF or TSO| commands.

| World Wide Node Name (WWNN) Values for FICON Cascaded Switch| Support| To provide cascaded switch support in a PPRCfcn (FICON) Storage Area Network,| the PPRC path utilizes a World Wide Node Name (WWNN) for address resolution.| A WWNN value, 16 hexadecimal digits long, is unique to each SVA subsystem and| may be displayed from the Detached Operator Panel (DOP). It is specified in the| SVAA PPRCopy ESTPATH and PPRCopy DELPATH commands for the primary| and secondary subsystems. See Chapter 8, “SVAA Subcommands and| Commands” for the complete command syntax.


The primary benefit of PPRC Remote SnapShot is that you can now use SnapShotto replicate volumes on a remote SVA subsystem without the need for direct hostconnectivity to the remote subsystem.



PPRC Remote SnapShot allows a PPRC Secondary volume to be snapped toanother functional volume on the same remote SVA subsystem as the Secondaryvolume. A request for a PPRC Remote SnapShot is sent to a Source (PPRCPrimary) volume on the local subsystem, is transferred to the PPRC Secondaryvolume on the remote subsystem using the PPRC connection, and then theSecondary volume on the remote subsystem is snapped to the designated Targetvolume on the remote subsystem.

Note: A PPRC Remote SnapShot can be performed on a single subsystemassuming the necessary physical "loopback" connection has been made. While asingle subsystem configuration is not recommended for disaster recovery, such aconfiguration may be useful for testing purposes only.

The SVAA SNAP VOLUME subcommand has been enhanced to allow a remotefunctional volume to be specified as the Target volume.

PPRC Remote SnapShot Operational RequirementsPPRC Remote SnapShot has the following requirements:

� PPRC Remote SnapShot is a volume-level operation only; PPRC RemoteSnapShot of data sets is not supported.

� PPRC Remote SnapShot is supported between two V2X subsystems, betweentwo V2X2 subsystems, or between V2X and V2X2 subsystems

� The PPRCSnapShot hardware feature must be installed on the both the localand remote subsystems.

� The microcode support for PPRC Remote SnapShot must be installed on boththe local and remote subsystems.

� The SVAA PTF support (L2P00BI for MVS, L2P00BJ for VM) and SnapShotPTF support (L2P00AF for MVS, L2P00AG for VM) for PPRC RemoteSnapShot must be installed.

General Requirements for Source, Secondary, and TargetVolumes

1. The volumes must be defined as CKD or SCSI volumes

2. The volumes must be enabled - CKDENA(YES) or SCSIENA(YES)

3. The volumes must be write enabled - CKDRW(YES) or SCSIRW(YES)

4. The volumes cannot be PAV Aliases

5. The volumes cannot be PowerPPRC Bridge volumes

Source Volume Requirements

1. A Source volume must be a PPRC Primary volume in the Duplex state. ASource volume cannot be a PPRC Secondary volume, a simplex (non-PPRC)volume, or a PPRC Primary volume in the Suspended or Pending states

2. A Source volume may be online or offline to host systems



Secondary Volume Requirements

1. A Secondary volume must be a PPRC Secondary volume in the Duplex state.A Secondary volume cannot be a simplex (non-PPRC) volume or a PPRCPrimary volume

2. A Secondary volume must be offline to all host systems (i.e., no path groupsestablished)

3. A Secondary volume must have the same virtual device type (3380, 3390, orSCSI) as the Source volume

Target Volume Requirements

1. A Target volume must be a simplex (non-PPRC) volume. A Target volumecannot be a PPRC Primary volume or a PPRC Secondary volume

2. A Target volume must be offline to all host systems (i.e., no path groupsestablished)

3. A Target volume must have the same virtual device type (3380, 3390, or SCSI)as the Secondary volume

PPRC Remote SnapShot Operational ConsiderationsUsers of PPRC Remote SnapShot should be aware of the following:

� A PPRC pair cannot be established between volumes with different numbers ofcylinders if the Primary volume has a larger number of cylinders than theSecondary volume.

� A PPRC pair can be established between volumes with different numbers ofcylinders if the Secondary volume has a larger number of cylinders than thePrimary volume, but this is not recommended for the following reasons:

- This prevents the use of P/DAS to swap volumes back to the originalconfiguration since the Secondary volume is now smaller than the Primary;configuration symmetry is recommended for ease of diaster recovery

- Additional user action (ICKDSF REFVTOC) is required on z/OS systems tobe able to use the extra capacity on the Target volume since theVTOC/VTOCIX copied from the Secondary volume does not "know" aboutthis extra space

Performing PPRC Remote SnapShotsUse the following steps as a guide to setting up and performing PPRC RemoteSnapShots:

1. If you already know what volume you want to use as a Source volume on thelocal subsystem, proceed to the next step, otherwise:

a. Define the Source volume on the local subsystem. This will become aPPRC Primary volume once you fully establish the PPRC connection (pathand pair)

b. Initialize the newly-defined Source volume using ICKDSF

c. Vary the newly-defined Source volume online

d. Place your user data on the newly-defined Source volume


2. If you already know what volume you want to use as a Secondary volume onthe remote subsystem (Warning: any data that exists on this volume will bedestroyed when the PPRC pair is established) proceed to the next step,otherwise:

a. Define the volume on the remote subsystem that will become your PPRCSecondary volume once you fully establish the PPRC connection. Thisvolume must have the same virtual device type (3380, 3390, or SCSI) asthe Source volume

3. If you already know what volume you want to use as a Target volume on theremote subsystem (Warning: any data that exists on this volume will bedestroyed when the PPRC Remote SnapShot is performed) proceed to thenext step, otherwise:

a. Define the Target volume on the remote subsystem. This is the designatedtarget of the SnapShot and must have the same virtual device type (3380,3390, or SCSI) as the Source and Secondary volumes

4. Establish the appropriate PPRC path(s) between the local and remotesubsystems (refer to the PPRC Configuration Guide) using either the TSOCESTPATH command (MVS only) or the ICKDSF PPRCOPY ESTPATHcommand (MVS or VM)

5. Establish the PPRC pair between the Source (Primary) and Secondaryvolumes (refer to the PPRC Configuration Guide) using either the TSOCESTPAIR command (MVS only) or the ICKDSF PPRCOPY ESTPAIRcommand (MVS or VM). On z/OS systems, an IEA494I message should beissued that confirms the pair is in a Pending state. For example:

IEA494I 8�42,SW8�42,PPRC PAIR PENDING,SSID=8��,CCA=42

On z/VM systems, there is no equivalent message.

6. Wait for the PPRC pair to transition from the Pending state to the Duplex state.On z/OS systems, an IEA494I message should be issued that confirms the pairhas transitioned to the Duplex state. For example:

IEA494I 8�42,SW8�42,PPRC PAIR FULL DUPLEX,SSID=8��,CCA=42

On z/VM systems, you should see the following messages:

ICK�22�3I PPRCOPY ESTPAIR FUNCTION COMPLETED SUCCESSFULLYICK�2231I DEVICE IS NOW A PEER TO PEER REMOTE COPY VOLUME

7. Perform the PPRC Remote SnapShot operation by issuing a SVAA SNAPVOLUME subcommand or by using the SVAA ISPF panels to have thesubcommand issued on your behalf. Refer to Chapter 8 of SVAA for OS/390Configuration and Administration or Chapter 9 of SVAA for VM Configurationand Administration for the syntax of the SNAP VOLUME subcommand and anexample of a subcommand used to perform a PPRC Remote SnapShot.

For More Information about PPRC

For more information, refer to the section in this publication entitled How to ObtainSoftware Documentation or to the following publications located on the StorageTekCustomer Resource Center (CRC) web site at www.support.storagetek.com:

� For Standard PPRC, PowerPPRC, PPRCSnapShot, Remote SnapShot, andSnap to Primary:


9500 thru V2X2 Peer-to-Peer Remote Copy Configuration Guide

� For PPRCfcn:

V2Xf Peer-to-Peer Remote Copy Configuration Guide

For more information about PPRC in general, see IBM's DFSMS Advanced CopyServices and the DFSMS Remote Copy Administrator's Guide and Referencedocumentation.

Parallel Access Volume (PAV) Support

The V2Xf supports the definition and use of Parallel Access Volumes (PAV). PAVprovides the ability to assign multiple unit addresses or UCBs to a functional devicethrough the use of Base and Alias devices.

The Base device is the device on which data is stored. The Alias device representsan alternate unit address from which the Base volume can be accessed.

With PAV, instead of using one unit address to access a volume, the host can useseveral unit addresses: the address of the Base device and any Alias device.Multiple users or applications on the same system can perform multiple I/Os to thesame volume. PAV's ability to perform multiple concurrent I/Os to a volume resultsin a significant reduction in IOS queue times and volume contention. Consequently,I/O response times are also reduced and throughput is increased.

PAV has been implemented on OS/390 and z/OS platforms. Although z/VM doesnot exploit PAV, z/VM does support PAV for its OS/390 and z/OS guests.

The SVAA Server will tolerate an SVA with PAV enabled but does not providesupport for PAV device management. Alias devices and PAV attributes cannot bedisplayed or configured through the SVAA Server.

First-Time User Considerations for PAV� A new hardware feature, available only on the V2Xf, must be installed on your

V2Xf subsystem to enable PAV support. Until the hardware feature is installed,you won't be able to define Alias devices.

� There is no operational difference between CKD functional volumes that youdefined before you installed the PAV hardware feature and CKD functionalvolumes that you will define after you install the PAV hardware feature.

� You can confirm that the PAV hardware feature is installed by using SVAA.The feature will appear as "PAV" on the ISPF Subsystem Configuration Panels(SIBCA00 or SIBCR00) and on the Level 3 output of a LISTCFG SUBSYSTEMsubcommand. You may need to reinitialize SVAA for it to recognize that thehardware feature was installed. See Refreshing SVAA Feature or DeviceMapping Status on MVS later in this chapter to learn how to do this.

� If you fully defined your subsystem with 1365 3390-9 volumes or 4096 3390-3volumes (or some maximal combination thereof) before you installed the PAVhardware feature and now want to install the feature, define some Aliasdevices, and start reaping the performance benefits of PAV, you need to makeroom for your Alias devices. The Non-PAV to PAV Migration Process (below)will help you accomplish this and help insure that your SVAA and HCDdefinitions always match. See PAV Configuration Considerations later in thischapter on the importance of keeping your SVAA definitions consistent withyour HCD definitions.


� To disable the PAV hardware feature on a subsystem, you will have to vary allBase devices on the subsystem offline to all host operating systems to "unbind"the Alias devices, then delete all of the Alias devices on the subsystem. Onlythen can the PAV hardware feature be disabled. Because all Base devices onthe subsystem must be varied offline, this process may be disruptive to youroperations, so the decision to disable the PAV hardware feature on asubsystem should not be taken lightly. The disablement process may bedisruptive but is necessary to insure the integrity of your data.

Non-PAV to PAV Migration Process

1. Determine how many Alias devices that you need for each SVA Virtual ControlUnit (a VCU = 256 devices). Remember that Alias devices "belong" only to theVCU they are defined in. For example, VCU 2 might consist of 64 Basedevices and 192 Alias devices. The number of Alias devices that you needreally depends on your current I/O workload and on your own individualperformance needs.

2. Identify which CKD functional volumes that you want to turn into Alias devices.Many users reserve the lower range of devices in a VCU for Base devices andthe upper range for Aliases. For example, in VCU 2, you might reserve FDIDs200-23F for 64 Base devices, and FDIDs 240-2FF for 192 Alias devices.

3. Install the SVAA support PTFs for PAV. (L2P00AJ for MVS, L2P00AK for VM).HIPER PTF L2P00B5 (MVS only) is also strongly recommended.

4. Install the SVA hardware feature for PAV.

5. Move the data from the CKD functional volumes that you want to turn into Aliasdevices to the other CKD functional volumes that will remain Base devices.

6. Vary offline to all host operating systems the CKD functional volumes that youwant to turn into Alias devices.

7. Delete these offline CKD functional volumes using the SVAA ISPF panels orthe DELETE DEVICE subcommand. You won't be able to delete a functionalvolume unless it is varied offline to all host operating systems.

8. Have your systems programmer change the HCD definitions for these deleteddevices from Bases to Aliases, but remember that the device type (3380 or3390) of the Alias must be the same as the device type of the Base. 3380Bases cannot utilize 3390 Aliases; 3390 Bases cannot utilize 3380 Aliases. Forexample, unit address 7240 is currently genned as a 3390B. Use HCD tochange it to a 3390A. Also have your systems programmer review theappropriateness of the HCD WLMPAV parameter setting for the new Aliasdevices at this time.

9. Have your systems programmer activate the new HCD definitions. Device-levelchanges can usually be done dynamically and without a system or applicationoutage. The key HCD requirement is that the device to be changed must beoffline to all host operating systems. If you are following this process, you havealready satisfied that requirement.

10. Reinitialize SVAA for it to recognize that the HCD device definitions havechanged. Take one of the actions listed in Refreshing SVAA Feature orDevice Mapping Status on MVS later in this chapter.


11. Define the new Alias devices using the SVAA ISPF panels or the DEFINEDEVICE subcommand and relate each new Alias device to an existing Basedevice.

12. Use RMF reports or other performance-monitoring software products to confirmthat PAV is in use and to quantify the performance benefit of PAV on youroperations.

For additional information about PAV, consult IBM's TotalStorage Enterprise StorageServer Model 800 documentation.

PAV Configuration Considerations Important!

Always keep your V2Xf Base and Alias device definitions consistent with yourHCD Base and Alias device definitions.

The following sections demonstrate what can happen if definitions are notconsistent. The first scenario describes the situation where HCD has a devicedefined as a Base, but the device has been defined incorrectly as an Alias on theV2Xf. The second considers the reverse scenario where a device is defined as anAlias in HCD and as a Base to V2Xf.

HCD Base but V2Xf AliasIf a device is defined in HCD as a Base but is misdefined to the V2Xf as an Alias,you should correct this problem by deleting the misdefined V2Xf Alias and then, ifappropriate, redefining it as a Base. Do not allow misdefined Aliases to exist asthey can create a potential data integrity exposure, as explained below.

SVAA will attempt to identify misdefined Aliases and can issue SIB2950W andSIB2943E messages to help you correct this problem.

SIB2950W

Misdefined Aliases may be reported during SVAA initialization (or reinitialization ofthe Device Mapping Queue) by SIB2950W messages with Failure reason 5:

SIB295�W Devices not mapped to TSTA, Failure = 5: 7A��-7A5F,7AC�-7ADE.SIB295�W Devices not mapped to TSTA, Failure = 5: 7B�4-7B�6,7B13-7B18.

SIB2943E

If the related Base device of a misdefined Alias is online at the time SVAA isinitialized (or the Device Mapping Queue is reinitialized), the misdefined Alias maybe identified by a SIB2943E message with return code 105 and reason code 2, anda SIB2950W message with Failure reason 1:

SIB2943E Device mapping queue function request 7 failed fordevice 7B�4. Return code= 1�5, reason code= ��2.

SIB2943E Device mapping queue function request 7 failed fordevice 7B�5. Return code= 1�5, reason code= ��2.

SIB295�W Devices not mapped to TSTA, Failure = 1: 7B�4-7B�5.


Important!

Check your V2Xf definitions to confirm that the device is in fact a misdefinedalias before deleting any devices. A return code of 105 in the SIB2943Emessage and a Failure reason code of 1 in the SIB2950W message can occurfor reasons that are unrelated to misdefined Aliases.

Besides the SIB2950W message issued by SVAA, the DEVSERV QPAV commandcan be used to compare the HCD and V2Xf definitions and detect mismatches ofthis kind:

DS QP,7B12,VOLUMEIEE459I �8.53.11 DEVSERV QPAVS 863

Host Subsystem Configuration Configuration ---------------- ------------------- UNIT UNIT UA

NUM. UA TYPE STATUS SSID ADDR. TYPE---- -- ------ -------- ---- ---- ----------7B12 �� BASE NOT-BASE 7B12 �� ALIAS-�2�� 1 DEVICE(S) MET THE SELECTION CRITERIA

ICKDSF Implications

Because the misdefined Alias is genned as a Base, ICKDSF will not reject theattempt to initialize the device. Worse, because you have related the misdefinedAlias to a correctly defined Base, ICKDSF will initialize the Base and destroy anyuser data that was on the volume.

Example

1. Device 7B02 is genned as a Base and is correctly defined to the V2Xf as aBase.

2. Device 7B12 is genned as a Base and is misdefined to the V2Xf as an Alias.

3. Device 7B02 is initialized, varied online, and user data is written to the volume.

4. An ICKDSF INIT job is run that incorrectly specifies device 7B12 as the deviceto be initialized.

5. The contents of device 7B02 are destroyed because 7B12 was misdefined asan Alias of 7B02.

6. Typically, at this point the misdefined Alias is boxed by the operating system.

Note: Even though the ICKDSF initialization of a misdefined Alias appears tobe successful, you will not be able to vary the device online:

V 7B12,ONLINEIEE1�3I UNIT 7B12 NOT BROUGHT ONLINEIEE763I NAME= IOSCCMSG CODE= ��8��2AIOS291I CONFIGURATION DATA COULD NOT BE READ

ON PATH(7B12,FF) RC=2A # IEE763INAME= IECVIOPM CODE= ��4��

IOS554I CONFIGURATION DATA PROCESSING FAILEDIEE764I END OF IEE1�3I RELATED MESSAGES


HCD Alias but V2Xf BaseIf a device is defined in HCD as an Alias but is misdefined to the V2Xf as a Base,you won't be able to initialize the device:

INIT UNIT(7BFF),NOCHECK,NOVAL,NORCLM,DEVTYPE(339�) + VTOC(�,1,14),INDEX(1,�,15),VOLID(XX7BFF),OWNER(XXX) + PURGE,NOVERIFY

ICK31�23I INVALID UNITADDRESS, SYSNAME OR DDNAME SPECIFIED.ICK3��3I FUNCTION TERMINATED. CONDITION CODE IS 12

Furthermore, you won't be able to vary the device online:

V 7BFF,ONLINEIEE313I 7BFF UNIT REF. INVALID

Because the device is genned as an Alias and can't be initialized or varied online,there is no way to write user data to the device.

Even though no data integrity exposure exists for this case, you should still correctthe problem by deleting the misdefined V2Xf Base, and then, if appropriate,redefining the device as an Alias and relating it to a correctly defined Base.

Static and Dynamic PAV Device ManagementTo statically manage a PAV device, specify WLMPAV=NO when a device is definedin HCD. To dynamically manage a PAV device, specify WLMPAV=YES and enabledynamic alias management from the Workload Manager (WLM) ISPF panels. Referto IBM's MVS Planning: Workload Management and HCD Planning for moreinformation.

PAV DifferencesOn the V2Xf, PAV Base devices are exactly the same as the CKD functionalvolumes that you have used on previous SVA hardware. PAV Alias devices arenew and do not actually consume virtual capacity or additional back-end storage.

Other differences in SVAA operation for PAV Alias devices are as follows:

� Alias devices cannot be the source or target of an online or offline volume ordata set snap.

� Dynamic and Interval DDSR do not release space on Alias devices since spacecannot be allocated on Aliases.

� Alias devices are excluded from all SRP data collection, so performance andspace utilization statistics are not reported for Aliases.

� Even though the number of cylinders cannot be specified for an Alias deviceitself, an Alias device can be defined and related to a Base device that is aLarge Volume or a FlexVolume.

� In ISPF panel and SVAA command output, the number of cylinders andfunctional capacity of Alias devices is always reported as zero.

� Alias devices cannot be used as ECAM devices.

� Alias devices or paths to Alias devices cannot be varied online or offline toz/OS or OS/390 operating systems.

� Alias devices cannot be initialized using SVAA. As a rule, you should notattempt to initialize Alias devices using ICKDSF because of the potential data


integrity exposure when a genned Base is misdefined to the V2Xf as an Alias.See “PAV Configuration Considerations” on page 2-17 for more information.

� Alias devices are not mapped by SVAA Device Mapping. Specification ofAliases in a Device Inclusion or Device Exclusion table is ignored.

� The CACHE, CKDENABLE, CKDREADWRITE, DASDFASTWRITE, NAME,and PRIVILEGEDECAM attributes cannot be changed for Alias devices.

� The QUERY DEVICE subcommand does not display information about PAVAlias devices. Use the DISPLAY DEVICE and LISTCFG DEVICEsubcommands instead.

� You cannot change the PAV Type (Base or Alias) of a device without deletingand redefining the device. If you change the PAV Type of a device, make surethat the change is consistent with your device definitions in HCD.

� The device type (3380 or 3390) of an Alias device must always match that ofits related Base device. This requirement does not prevent an Alias from beingdefined to a Base device with a larger or smaller capacity, including a LargeVolume or a FlexVolume, but it does prevent any attempt to define an Alias ofone device type to a Base of a different device type. For example, a 3380-JAlias cannot be defined and related to a 3390-9 Base, but a 3390-9 Alias canbe defined and related to a 3390-3 Base.

This requirement also does not prevent an Alias from being reassigned to aBase device with a larger or smaller capacity, including a Large Volume or aFlexVolume, but it does prevent any attempt to reassign an Alias of one devicetype to a Base of a different device type. For example, a 3380-J Alias cannotbe reassigned to a 3390-9 Base, but a 3390-9 Alias can be reassigned to a3390-3 Base.

� An Alias device can be reassigned to a different Base device eitherautomatically by the Workload Manager (WLM) component of an OS/390 orz/OS operating system, or manually by using the ALTER DEVICEsubcommand. An Alias must be assigned to a Base device when the Alias isintially defined.

� A Base device is not required to have any related Alias devices; if a Base doeshave Aliases, they must all be defined within the same Virtual Control Unit(VCU); crossing VCU boundaries is not allowed. Since a VCU has a maximumof 256 devices, one Base device can be defined with up to 255 Aliases, or 128Base devices can be defined with 1 Alias each, etc..

� An Alias device can be defined only after its related Base device is defined.You cannot define a Base and its related Aliases in a single define operation.This ensures data integrity and the correct interaction of the V2Xf with hostoperating systems.

� The rules for deleting Base and Alias devices are as follows:

- To delete a CKD or SCSI device (non-PAV, has no Aliases)

1. Vary the device offline to all host operating systems

2. Delete the device

- To delete a PAV Base device that does not have Aliases

1. Vary the Base device offline to all host operating systems

2. Delete the Base device


- To delete a PAV Base device that has Aliases


2. Delete each Alias related to the Base; use DISPLAY DEVICE orLISTCFG DEVICE to determine the Aliases to be deleted. You cannotdelete a Base and its related Aliases in a single delete operation.


- To delete a PAV Alias device that is related to an online Base


2. Delete the Alias device

- To delete a PAV Alias device that is related to an offline Base

1. Simply delete the Alias device

- To delete a misdefined PAV Alias (genned as Base, defined as Alias)

1. Simply delete the Alias device

Note: In this special case only, it does not matter whether the Baseis online or offline. Since the host operating system did not establisha path group to the Alias when it was misdefined, it can be safelydeleted without requiring that the Base device be varied offline.

Refreshing SVAA Feature or Device Mapping Status on MVS

After the SnapShot, PPRC, PAV, or PPRCSnapShot features have been enabled ordisabled on the SVA hardware, the SVAA software generally does not recognize thata feature change has occurred.

If you configure channels online with the MVS CONFIG command, or attachdevices to a MVS guest system from VM, and these devices were not accessible atthe time the SVAA subsystem was initialized, SVAA has no knowledge of thesedevices and considers them as not defined to the host it is running on.

To make SVAA recognize that the availability of a hardware feature has changed, orrefresh SVAA's knowledge of newly accessible devices that have not yet beenvaried online, take one of the following two actions:

� Partially reinitialize the SVAA subsystem using the SIBMVSS program thatspecifies an ALTER SSNAME command of the following form:

ALTER SSNAME( NAME(ssname) REINIT RIM(DMQ)

For more information about SIBMVSS, refer to the step titled “Initializing theSVAA Subsystem with SIBMVSS” in the SVAA for OS/390 Installation,Customization, and Maintenance guide. If the SVAA address space (theSIBMAIN program) is running, it does not need to be stopped to reinitialize theSVAA subsystem.

� Terminate and initialize the SVAA subsystem using the SIBMVSS program.

Note: If the SVAA address space (the SIBMAIN program) is running, it must bestopped before the SVAA subsystem can be terminated.


Note that an IPL of the relevant MVS system and a subsequent initialization of theSVAA subsystem also accomplishes a refresh of feature and device information, butthis action should be taken only as a last resort.

FlexVolumes and Large Volumes

FlexVolume support allows the definition of variable sized 3380 or 3390 functionaldevices. Large Volume support allows the definition of 3390-9 functional deviceswith 32760 cylinders. See Table 1-1 for a summary of the SVA models andmicrocode levels that support Large Volumes and FlexVolumes.

FlexVolume Operational RequirementsFlexVolumes have the following requirements:

� FlexVolumes are supported only on V2X, V2X2, and V2Xf subsystems.

� The microcode support for FlexVolumes must be installed on a V2X/V2X2/V2Xfsubsystem before FlexVolumes can be defined.

� The SVAA PTF support (L2P00BF for MVS, L2P00BG for VM) for FlexVolumesand Large Volumes must be installed before FlexVolumes can be defined usingSVAA.

� The maximum virtual capacity of a V2X, V2X2, or V2Xf subsystem is notincreased by FlexVolume support. You cannot define more than 1365 3390-9or more than 4096 3390-3 functional devices just because some or all devicesare defined as FlexVolumes.

� FlexVolumes cannot be defined as SCSI, PPRC Bridge, or PAV Alias devices.

� FlexVolumes must be defined as 3380 or 3390 CKD devices subject to thefollowing further requirements:

- FlexVolumes cannot be defined as 3390-1 or 3390-2 devices in order tomaintain compatibility with the IBM 2105 ESS

- A 3380-J can only be defined with 1-885 cylinders

- A 3380-KE can only be defined with 886-1770 cylinders

- A 3380-K can only be defined with 1771-2655 cylinders

- A 3390-3 can only be defined with 1-3339 cylinders

- A 3390-9 can only be defined with 3340-10017 cylinders if the LargeVolume microcode support is not installed or the subsystem is a V2X orV2X2

- A 3390-9 can only be defined with 3340-32760 cylinders if the LargeVolume microcode support is installed and the subsystem is a V2Xf orV2X4f

Note: A 3390-9 device defined with 32759 cylinders is technically aFlexVolume; a 3390-9 device defined with 32760 cylinders is technically aLarge Volume.


Large Volume Operational RequirementsLarge Volumes have the following requirements:

� Large Volumes are supported only on V2Xf subsystems.

� The microcode support for Large Volumes must be installed on a V2Xfsubsystem before Large Volumes can be defined.

� The SVAA PTF support (L2P00BF for MVS, L2P00BG for VM) for FlexVolumesand Large Volumes must be installed before Large Volumes can be definedusing SVAA.

� The maximum virtual capacity of a V2Xf subsystem is not increased by LargeVolume support. You can define approximately 417 32760 cylinder devices -the equivalent to 1365 3390-9 devices or 4096 3390-3 devices.

� Large Volumes must be defined as 3390-9 CKD devices with 32760 cylinders.

� Large Volumes cannot be defined as SCSI, PPRC Bridge, or PAV Aliasdevices.

SnapShot and PPRC Considerations for FlexVolumes and Large VolumesLarge Volumes and FlexVolumes do not change the current behavior or impose anynew restrictions on SnapShot or PPRC, but users of Large Volumes andFlexVolumes should be aware of the following:

� Volume SnapShot between devices with different numbers of cylinders is notsupported.

� A PPRC pair cannot be established between devices with different numbers ofcylinders if the Primary device has a larger number of cylinders than theSecondary device.

� A PPRC pair can be established between devices with different numbers ofcylinders if the Secondary device has a larger number of cylinders than thePrimary device, but this is not recommended for the following reasons:

- This prevents the use of P/DAS to swap devices back to the originalconfiguration since the Secondary device is now smaller than the Primary;configuration symmetry is recommended for ease of diaster recovery

- Additional user action (ICKDSF REFVTOC) is required on z/OS systems tobe able to use the extra capacity on the Secondary volume since theVTOC/VTOCIX copied from the Primary volume does not "know" about thisextra space


Chapter 3. SVAA in the OS/390 Environment

Chapter SummarySVAA Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

SVAA Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2SVAA Initialization Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

SIBSTK00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2PROFSIBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Issuing Subcommands from TSO . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Issuing Subcommands in SVAA Batch Jobs or Macros . . . . . . . . . . . . 3-4

SIBBATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

November, 2006 — PN 311290512, Rev. N OS/390 Environment 3-1

OS/390 Environment

SVAA Input

In the OS/390 environment, there are two basic ways of entering input to SVAA:

� With the SVAA set of ISPF panels, as defined for your installation.

Chapter 7, “Using the SVAA Panels” explains how to use the panels.

� With SVAA subcommands.

Chapter 8, “SVAA Subcommands and Commands” is an alphabetical referenceof the SVAA subcommands and their parameters.

SVAA SubcommandsSVAA includes two utilities through which you enter the SVAA subcommands:

SIBADMIN Under TSO, the SIBADMIN command creates the environment inwhich you can issue SVAA subcommands.

SIBBATCH The SIBBATCH utility enables you to program a sequence of SVAAsubcommands to be run as a batch job.

Note: You cannot issue the SIBADMIN command within aSIBBATCH program.

SVAA subcommands can be issued in several ways:

� From within SVAA initialization routines.

� From TSO:

- at the SIB: prompt (which appears when you enter the SIBADMIN commandby itself).

- within a REXX EXEC

- within a CLIST

� From within a SIBBATCH file.

� On the command line of the SVAA panels (preceded by SIB). See “Using theSVAA Panels” on page 7-2.

SVAA Initialization RoutinesSVAA enables you to specify initialization information that sets or changes theconditions under which the SVAA subcommands are executed.

SIBSTK00

Optionally, you can place initialization information in a parameter library membernamed SIBSTK00 in the data set pointed to by the STKPARMS DD statement in theJCL (both for SIBADMIN and SIBBATCH). If STKPARMS is not defined in theexecuting environment, SVAA looks for SIBSTK00 in SYS1.PARMLIB. SVAAprocesses the commands in SIBSTK00 (or an alternative member) whenever youuse the SIBADMIN or SIBBATCH command.

Note: See “Issuing Subcommands from TSO” on page 3-4 or “SIBBATCH” onpage 3-4 for information about specifying an alternative SYS1.PARMLIB member forinitialization parameters.


OS/390 Environment

The initialization routine should include a SET ECAMDEVICE subcommand to specifythe host address of the device in the SVA subsystem that is to be used for ECAMcommunications. It should also include a SET NONICEBERG subcommand todesignate a 3990 device if you want to collect statistics from a non-SVA subsystem.

PROFSIBA

After processing the commands in SIBSTK00, if you are using SIBADMIN or the SVAApanels, SVAA looks for initialization information in an SVAA macro called PROFSIBA.Information in PROFSIBA overrides parameters specified in the SIBSTK00 member ofparmlib, except that SET ECAMDEVICE subcommands are cumulative (that is,subcommands in both sources are used).

When you are running SVAA under ISPF, you can specify the profile and parmlibnames by using the Session Administration option of the SVAA panels (the valuesyou specify for the Profile and Parmlib options do not take effect until the next timeSVAA is initialized).

Figure 3-1 is an example of REXX statements used to customize PROFSIBA. Youcan find this example in the PROFSIBA member of SIBSAMP. You may include asmany statements as you want in the profile. See Chapter 8, “SVAA Subcommandsand Commands” for information about SET subcommands.

/� REXX profile macro for SIBADMIN �/address SIB"set case(mixed)""set ecamdev(1��)"exit

Figure 3-1. Sample REXX profile macro for SIBADMIN

Figure 3-2 is an example of a CLIST for customizing PROFSIBA. You can find thisexample in the PROFSIBC member of SIBSAMP. You may include as manystatements as you want in the CLIST; see Chapter 8, “SVAA Subcommands andCommands” for information about SET subcommands.

Note: When you copy PROFSIBC from SIBSAMP, rename it PROFSIBA before youuse it.

PROC 1 PROGRAMCONTROL NOMSGDATASET CASE(U)SET ECAMDEV(2��)ENDDATAEXIT

Figure 3-2. Sample CLIST for customizing PROFSIBA


OS/390 Environment

Issuing Subcommands from TSOTo issue SVAA subcommands from TSO, use the SIBADMIN command. The generalform of the command is:

��──SIBADMIN─ ──┬ ┬───────────────────── ─subcommand─ ──┬ ┬─────────────────────────── ────��└ ┘──=PARMLIB=membername │ │┌ ┐─ ───────────────

└ ┘─(─ ───� ┴parameter(values) ─)─

Use the optional =PARMLIB= parameter to override SIBSTK00, the default parmlibmember that is used in SIBADMIN processing.

A subcommand of SIBADMIN can be:

� Any of the SVAA subcommands described in Chapter 8, “SVAA Subcommandsand Commands.”

� Any of the SVAA subcommands described in the SVAA for OS/390 Reportingmanual.

� A TSO command.

Note: The maximum allowable length of a SIBADMIN command, including itssubcommands and parameters, is 950 characters, including blanks.

To process the subcommands, a REXX addressing environment called SIB isestablished. When running, SVAA displays the SIB: prompt, at which you can enterSIBADMIN subcommands. Type end to leave SVAA.

Issuing Subcommands in SVAA Batch Jobs or MacrosIssuing SVAA subcommands in a batch program or a macro is especially effective ifyou want to issue the same set of subcommands at regular intervals, such as dailyor weekly. You can issue the same subcommands in batch jobs or macros that youcan issue in SIBADMIN.

In processing subcommands in SIBBATCH or macros, any error that exceeds thevalue set by the SET MAXRC subcommand causes the program to terminate with anappropriate error message and return code.

SIBBATCH

To run SVAA in batch mode, run the SIBBATCH JCL (shown in Figure 3-3 onpage 3-5) and include appropriate SYSIN statements containing subcommands ofSIBBATCH. The general form of these statements is:

��─ ─subcommand─ ──┬ ┬─────────────────────────── ───────────────────────────────────────�� │ │┌ ┐─ ─────────────── └ ┘─(─ ───� ┴parameter(values) ─)─

A subcommand of SIBBATCH can be:

� Any of the SVAA subcommands described in Chapter 8, “SVAA Subcommandsand Commands.”

� Any of the SVAA subcommands described in the SVAA for OS/390 Reportingmanual.


OS/390 Environment

// <jobcard>//STEP1 EXEC PGM=SIBBATCH//STEPLIB DD DSN=hlq.SIBLOAD,DISP=SHR//STKPARMS DD DSN=hlq.sibparm,DISP=SHR//SIBCTRAN DD DSN=hlq.SACLINK,DISP=SHR//CTRANS DD DSN=hlq.SACLINK,DISP=SHR//SYSTERM DD SYSOUT=�//SYSPRINT DD SYSOUT=�//SYSIN DD �<SVAA subcommands without a preceding SIBADMIN> � � �/�//

Figure 3-3. SIBBATCH example

It is not necessary to provide DCB parameters for the SYSTERM and SYSPRINT datasets. However, if you wish to do so, use:

RECFM=VBA,LRECL=137,BLKSIZE=23476

The SVAA parameter library contains a member called SIBSTK00, which can specifycommon startup options, such as SET ECAMDEVICE. Startup commands can alsoappear in the SYSIN data set. If there is no STKPARMS DD statement, but SIBSTK00appears in SYS1.PARMLIB, SVAA uses the version in SYS1.PARMLIB.

Note: To specify an alternative parmlib member for initialization, use the followingEXEC statement in the above JCL:

//STEP1 EXEC PGM=SIBBATCH,PARM='=PARMLIB=membername'

Here, membername, which can be up to eight characters, overrides SIBSTK00, thedefault SYS1.PARMLIB member used in SIBBATCH processing.

It is recommended to use either the SIBCTRAN or CTRANS DD statement to ensure theuse of the correct SAS/C macros contained in the SVAA SACLINK dataset. For anexample of the use of SIBCTRAN, see the SIBCTUM member of the SIBSAMP library.

Command Output

The output from the utility commands from a TSO user or batch program(informational messages, error messages, and report output) is handled by defaultas follows:

� In foreground TSO, SVAA sends the command’s message output to theterminal.

� In background TSO, SVAA sends the reports and error messages to the dataset named in the SYSTSPRT DD statement.

� In batch, SVAA sends reports and error messages to the data set named in theSYSPRINT DD statement.

� SAS/C writes program output to the data set named in the SYSPRINT DDstatement. The statement is optional, but recommended.


OS/390 Environment

� SAS/C writes program error output to the data set named in the SYSTERM DDstatement. The statement is optional, but recommended.

� When you start SVAA from the ISPF panels, SVAA sends reports and messagesto REXX variables.

You can change the destinations for messages and reports with the OUTMSG (formessages) and OUTFILE (for reports) parameters of the SET DESTINATIONsubcommand. However, you cannot change the default destination in ISPF.

If you specify a data set (that is, a file specification) as the destination for messagesor reports, SVAA handles the specification as follows:

� If the data set does not exist, SVAA creates it.

� If the data set exists but has not previously been used in this run of SIBADMINor SIBBATCH, SVAA replaces the previous content of the data set.

� If the data set exists and has been used previously by an SVAA subcommandin this run of SIBADMIN or SIBBATCH, SVAA appends the new output to theexisting content.

You can also redirect the message and report output of a particular subcommand ofSIBADMIN. See “Redirecting Subcommand Output” on page 8-10 for moreinformation.


Chapter 4. Using Deleted Data Space Release

Chapter SummaryDeleted Data Space Release (DDSR) . . . . . . . . . . . . . . . . . . . . . . . . 4-2Dynamic DDSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Dynamic DDSR Control Parameters . . . . . . . . . . . . . . . . . . . . . . 4-3Dynamic DDSR Diagnostic Facilities . . . . . . . . . . . . . . . . . . . . . 4-3

DDSR and the SVAA Address Space . . . . . . . . . . . . . . . . . . . . . . . . 4-4Interval DDSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Interval DDSR Control Parameters . . . . . . . . . . . . . . . . . . . . . . 4-5Interval DDSR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Interval DDSR Diagnostic Facilities . . . . . . . . . . . . . . . . . . . . . . 4-7

DDSR Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7DDSR Device Selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10DDSR SIMULATE Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

November, 2006 — PN 311290512, Rev. N Deleted Data Space Release 4-1

DDSR

Deleted Data Space Release (DDSR)

The SVA's disk array space is a limited resource that must be effectively managed.Reclaiming deleted data space is a critical part of space management. When theoperating system deletes a data set, the VTOC is updated and the space becomesa free extent on the volume. In the SVA, as well as in traditional DASD, this deleteddata still occupies the physical tracks. For traditional DASD, physical tracks resideon a physical volume and cannot be used by any other volume. In the SVAsubsystem, physical tracks (disk array space) are a shared resource and can beused by all functional devices.

To reclaim the tracks in a deleted extent, SVAA provides the Deleted Data SpaceRelease (DDSR) facility. DDSR executes on the OS/390 host and identifieshost-deleted tracks for future free space collection by the SVA Disk Array Controller.After free space collection, the space is available to the entire subsystem.

SVAA provides two methods for reclaiming the deleted tracks:

� Dynamic DDSR, which identifies tracks to release using the OS/390 DADSMexit, and

� Interval DDSR, which identifies tracks to release by scanning the VTOC.

The two functions differ in the way they operate and the way they are invoked onthe OS/390 host.

Dynamic DDSR can be activated without an SVAA address space. It is initializedduring SVAA subsystem initialization—either with the OS/390 Subsystem NameTable (SSN) entry for SVAA or with the SIBMVSS program.

It is invoked during OS/390 DADSM scratch and partial release processing, andcreates SVA subsystem commands that identify the host-deleted functional trackswhose physical space can be reclaimed.

Interval DDSR runs as a subtask of the SVAA address space. It is invoked atuser-specified time intervals to release space for specified subsystems and/orvolumes.

When activated, Interval DDSR scans the VTOCs of the requested SVA volumes thatare online, making note of the free space on each volume. It then creates SVAsubsystem commands that identify the unused functional tracks whose physicalspace can be reclaimed.

Notes:

1. Dynamic and Interval DDSR only identify host tracks whose back-end storage isno longer needed. The task of reclaiming (collecting) the space isaccomplished asynchronously in the Disk Array Controller by the Free SpaceCollection (FSC) function. The timing of the (FSC) task depends on theworkload in the SVA subsystem.

2. Dynamic and Interval DDSR do not release space on Power PPRC Bridgedevices. You should not initialize Bridge devices with ICKDSF or other utilities,vary them online to any host operating system, or place any data on them sinceall user and system data (e.g., VTOCs) can be destroyed during theestablishment of a Power PPRC Bridge pair.

Since the only way to release back-end space on a Bridge device is to deletethe device, move any user data from the Bridge device before deleting thedevice.


Dynamic DDSR

3. Dynamic and Interval DDSR do not release space on PAV Alias devicesbecause space cannot be allocated on these devices. Alias devices consumeno physical space.

Dynamic DDSR

The Dynamic DDSR intercept is normally installed in the OS/390 operating systemduring SVAA subsystem initialization. The OS/390 Subsystem Name Table (SSN)entry for SVAA is used to control whether the intercept is installed and whether it isactive or inactive at the time of system IPL. Dynamic DDSR status can also be setwhen the SVAA subsystem is initialized with the SIBMVSS program. (The SVAA forOS/390 Installation, Customization, and Maintenance manual discusses customizingthe SSN and initializing with SIBMVSS.)

Dynamic DDSR obtains control in the OS/390 DADSM (Direct Access Device StorageManagement) scratch and partial release functions, and issues subsystemcommands to reclaim the physical space for the extents that are being freed.

Note: When Dynamic DDSR is used, it should be active on every OS/390 systemthat has access to SVA volumes. Otherwise, deletions can go unnoticed by the SVAsubsystem.

The RELEASE DYNAMICDATA subcommand (see page 8-139) provides DynamicDDSR control and diagnostic facilities.

Dynamic DDSR Control Parameters

With parameters of the RELEASE DYNAMICDATA subcommand (see page 8-139),you control the status of Dynamic DDSR and specify the devices to be processedfor space release.

� Dynamic DDSR status. The STATUS parameter sets or queries the status ofDynamic DDSR. The status can be set to ACTIVE, INACTIVE, or SIMULATE (see“DDSR SIMULATE Processing” on page 4-13).

� Device selection. The VOLUME, EXCLUDEVOLUME, SUBSYSTEM andEXCLUDESUBSYSTEM parameters let you select or exclude specific devices forprocessing by Dynamic DDSR. The default is to include all functional devicesfor all installed subsystems. See “DDSR Device Selection Rules” onpage 4-10 for an explanation of the effects of inclusion and exclusionparameters on device selection.

Dynamic DDSR Diagnostic Facilities

Dynamic DDSR provides diagnostic facilities in the form of debugging messagesand GTF trace records. You enable the messages and trace records—to obtaindocumentation for problem resolution—by means of two additional parameters ofthe RELEASE DYNAMICDATA subcommand:

� Diagnostic messages. The DEBUG parameter enables or disables DynamicDDSR diagnostic messages.

� Trace records. The TRACE parameter enables or disables the generation ofDynamic DDSR GTF trace records.


SVAA Address Space

DDSR and the SVAA Address Space

Two types of DDSR tasks run in the SVAA address space:

� The DDSR Main Task� One or more DDSR interval tasks

The DDSR Main Task performs global DDSR initialization for DDSR interval tasks.It can also initialize the Dynamic DDSR function. The Main Task also processesexternal DDSR subcommands (issued by an OS/390 console operator, a TSO user,or a batch job), and provides communications services between DDSR tasks in theaddress space.

You can start the DDSR Main Task by means of a parmlib member when the SVAAaddress space is started, and stop the Main Task by terminating the SVAA addressspace.

When the SVAA address space is running, the following system operator commands(documented in Chapter 8, “SVAA Subcommands and Commands”) are used tostart and stop the DDSR Main Task.

� START DSR � STOP DSR

A DDSR interval task is established for each RELEASE INTERVALDATAsubcommand processed by the DDSR Main Task. You can place RELEASEINTERVALDATA subcommands in the DDSR parmlib member (SIBDSRxx), or issuethem from an OS/390 console, a TSO session, or a batch job. Each DDSR intervaltask is identified by a unique user-supplied task identifier.

Each interval task controls a specified set of subsystems and/or volumes. At auser-specified time interval, the task performs space release processing on all ofthe specified volumes that are online to the OS/390 host on which Interval DDSR isrunning. The interval task determines which extents on a volume were unallocatedsince the last interval, and issues subsystem commands to reclaim the disk arrayspace for the extents.

You can start, suspend, resume, or stop an interval task with the START RELEASE,SUSPEND RELEASE, RESUME RELEASE, and STOP RELEASE subcommands. Youcan even change the operating parameters of an interval task while the task isrunning (see the REPLACE parameter of the RELEASE INTERVALDATAsubcommand).


Interval DDSR

Interval DDSR

Interval DDSR runs as a subtask in the SVAA address space at user-specified timeintervals. The interval subtask should be run once a day on volumes that cannotbe processed by DADSM.

Interval DDSR is initialized by the SVAA RELEASE INTERVALDATA subcommand, withwhich you specify the time intervals at which it will be invoked and the subsystemsand/or volumes for which it will release space.

Notes:

1. Of the volumes specified, Interval DDSR processes only those volumes that areonline to the OS/390 host on which Interval DDSR is running.

2. During the initial synchronization of a PPRC pair, the PPRC Primary volume isin a PENDING state. Interval DDSR cannot process PPRC Primary volumes inthis state. To avoid this situation and also reduce the time it takes to initiallyestablish a PPRC pair, it is recommended that you run Interval DDSR against avolume before it is initially established as a PPRC Primary volume so thatdeleted tracks are not sent to the PPRC Secondary volume. Once the PPRCpair is synchronized and is in the DUPLEX state, Interval DDSR can be run onthe PPRC Primary volume at any time.

3. The time to complete Interval DDSR on a given volume is a function of thenumber of extents that need to be released on the volume; the fact that avolume is a Large Volume does not necessarily mean that Interval DDSR willtake longer to complete on that volume; the fact that a volume is a FlexVolumedoes not necessarily mean that Interval DDSR will take less time to complete onthat volume.

The following SVAA subcommands are used to manage Interval DDSR:

� RELEASE INTERVALDATA � START RELEASE � DISPLAY RELEASE � SUSPEND RELEASE � RESUME RELEASE � STOP RELEASE

All of these subcommands can be issued by a TSO user, an OS/390 consoleoperator, or a batch job.

Interval DDSR Control Parameters

You control the following aspects of DDSR interval tasks with parameters of theRELEASE INTERVALDATA subcommand (see page 8-143):

� Device selection. The VOLUME, EXCLUDEVOLUME, SUBSYSTEM andEXCLUDESUBSYSTEM parameters let you select or exclude specific devices forprocessing by the interval task. The default is to exclude all functional devicesfor all installed subsystems. See “DDSR Device Selection Rules” onpage 4-10 for an explanation of the effects of inclusion and exclusionparameters on device selection.

� Deferred processing. The DEFER parameter gives you the option of deferringspace release processing until after the first time interval has expired. Youmay want to select deferred processing for RELEASE INTERVALDATAsubcommands that are executed during OS/390 initialization, so that the space


Interval DDSR

release function does not immediately begin issuing RESERVEs on volumeswhen critical systems are starting.

� Space release interval. The INTERVAL parameter specifies the time intervalthat is to lapse between space release actions. You specify the releaseinterval as a number of whole minutes with a minimum setting of 0 (zero)minutes. An interval of zero minutes causes the DDSR task to executeimmediately and then terminate (a “one-time” space release).

� Device reserve limit. The RESERVELIMIT parameter sets a limit on the lengthof time that a DDSR task can reserve the VTOC of a volume.

Free Space Release Prioritization Enhancement

Prior to SVAA PTF L2P00BW, Interval DDSR might not finish processingon a volume before the RESERVELIMIT time limit is reached. This mightbe because the maximum value for RESERVELIMIT is in effect, or it mightbe because the value for RESERVELIMIT is set below the maximum butcannot be increased because of performance impacts on the rest of thesystem.

Prior to SVAA PTF L2P00BW, and for heavily fragmented volumes, thenumber of free space extents might be so large as to prevent IntervalDDSR from processing each extent before the RESERVELIMIT time limit isreached.

Prior to SVAA PTF L2P00BW, Interval DDSR did not prioritize spacerelease by free space extent size, consequently the possibility existed forfree space to remain unreleased from the physical back-end storagedevices despite repeated Interval DDSR runs. The problem could beaggravated by the ability to define Large Volumes, but Large Volumes bythemselves do not cause this problem.

With PTF L2P00BW, Interval DDSR now partially prioritizes space releaseby free space extent size. Because any method of prioritization addsoverhead to Interval DDSR processing, and because the number of freespace extents might be very large, free space is not always released in theexact order of descending size, however, the largest single free spaceextent on each volume should always be released first.

� Extent map retention. The EXTENTMAP parameter specifies whether theinterval task is to retain the map of free extents on each volume from oneinterval to the next. If the extent map is retained, it is compared to the freeextents on the volume during the next interval process. This optimizes theperformance of DDSR, although using the extent map can cause DDSR to missthe extents for a data set that is allocated, written, and deleted betweenintervals.

Note: Large Volumes and FlexVolumes do not increase the above-the-linevirtual storage required to retain the map of free extents since support forLarge Volumes and FlexVolumes does not increase the maximum virtualcapacity of the subsystem.

� Parameter replacement. The REPLACE parameter specifies whetherparameter values (volumes and subsystems controlled, processing interval,etc.) entered in the current subcommand are to replace the correspondingparameter values of a running space release task—if a release task with thesame name is already running.


DDSR Implementation

Interval DDSR Messages

Because messages can be issued from any DDSR task running in the SVAAaddress space, a task identifier is included in each message. For interval tasks, thetask identifier is the release identifier specified in the RELEASE INTERVALDATAsubcommand that initiated the task. For the Main Task, the task identifier is“DDSR__MAIN”.

Each Interval DDSR message also includes a time stamp indicating when themessage was issued. This enables you to determine more easily the sequence ofevents in DDSR processing.

Note: Messages issued from the DISPLAY RELEASE subcommand do not contain atime stamp or task identifier. Including this information on the output of theDISPLAY RELEASE subcommand would detract from the relevant information in thedisplay and make the subcommand output more difficult to read.

Interval DDSR Diagnostic Facilities

Interval DDSR provides diagnostic facilities in the form of debugging messages.You enable the messages—to obtain documentation for problem resolution—bymeans of an additional parameter on the RELEASE INTERVALDATA subcommand:

� Diagnostic messages. The DEBUG parameter enables or disables IntervalDDSR diagnostic messages. A SIB4195I message is issued once per volume.SIB4196I and SIB4197I messages are issued multiple times per volume.DEBUG(ON) should be used only at the specific direction of STK Supportpersonnel since a significant number of messages can result.

DDSR Implementation

Figure 4-1 illustrates the implementation of Interval and Dynamic DDSR in OS/390.The SVAA address space runs as a started task in OS/390. The DDSR Main Taskand interval tasks execute as subtasks of the address space. Dynamic DDSRexecutes as an extension to OS/390 DADSM for all jobs running on the system.

OS/390

C11000

DynamicDDSR

SVAA Subsystem

DDSRMainTask

DDSRIntervalTasks

SVAA Address Space

Figure 4-1. DDSR task interactions

In general, you should activate Dynamic DDSR for all SVA volumes in yourinstallation. This means activating Dynamic DDSR on all OS/390 systems that haveaccess to one or more SVA volumes. The syntax for such a subcommand is:


DDSR Implementation

RELEASE DYNAMICDATA(STATUS(ACTIVE) SUBSYSTEM(�) VOLUME(�))

Once Dynamic DDSR is running to routinely process SVA volume deletions, set upInterval DDSR to process each SVA volume once a day at a time when reserveactivity on volumes is least disruptive. Running Interval DDSR during periods ofheavy activity is undesirable because it places a RESERVE on each volume beingprocessed.

Note: It is not necessary to inactivate Dynamic DDSR to run Interval DDSR. Thetwo DDSR functions can run simultaneously.

If one OS/390 system has access to all SVA volumes, you can start a single IntervalDDSR task running on that one system to process all of the SVA volumes. Anexample of the subcommand syntax (with a release task ID of “INTDDSR”) is:

RELEASE INTERVALDATA(RELID(INTDDSR) INTERVAL(24H) SUBSYSTEM(�) VOLUME(�))

If SVA volumes are not shared among multiple OS/390 systems, set up separateInterval DDSR tasks to ensure that every SVA volume is processed by one of thesetasks.

Since it's possible that Dynamic DDSR may not have been active on all hosts duringthe day, running Interval DDSR on all SVA volumes ensures that any missedhost-deleted space is properly identified and processed.

Running Interval DDSR every day may not always be necessary. If you determinethat running it less often is appropriate, you can submit a “one-time release” with aSIBBATCH job whenever it's needed (once a week, for example). Note that theINTERVAL parameter is set to 0. The syntax for processing all volumes on all SVAsubsystems would be:

RELEASE INTERVALDATA(RELID(INTDDSR) INTERVAL(�) SUBSYSTEM(�) VOLUME(�))

The Space Utilization Summary Report provides a practical way to see if you needto run Interval DDSR. The ALLOC functional capacity is obtained from the VTOCwhile the STORED capacity reflects the functional track directory (FTD). If the datain the “STORED” column exceeds that in the “ALLOC” column, it's time to run IntervalDDSR.

It is also recommended that Interval DDSR be run immediately after reinitializing anSVA volume, after restoring a new SVA volume, and after running a utility such asIBM's DFDSS DEFRAG on a volume.

Notes:

1. When configuring DDSR: If a volume is controlled by Dynamic DDSR, theDynamic DDSR intercept should be activated on all hosts that have access tothat volume, and the volume selection lists for DDSR should include that volumeon all hosts.

2. However, note that: If a volume is controlled by Dynamic DDSR and theDynamic DDSR intercept is inactive on one or more hosts for any period of time,it may be necessary to execute Interval DDSR to reclaim space that may havebeen freed during that period.

Both Dynamic and Interval DDSR should be run to manage space release mosteffectively for SVA subsystems.

The example below assumes the following configuration:

� There are two OS/390 hosts: HOST1 and HOST2.


DDSR Implementation

� There are two SVA subsystems: SUBSYSA and SUBSYSB.

� HOST1 and HOST2 both have access to devices 00 to 4095 on SUBSYSA anddevices 00 to 4095 on SUBSYSB.

Note: For simplicity, the example refers to the device configuration in terms ofdevice numbers. Device selection for Dynamic and Interval DDSR is actuallyspecified in terms of subsystem name and/or volume serial number.

In Figure 4-2, both Dynamic and Interval DDSR are used to control space release:

� Interval Task 1 on HOST1 controls the volumes on devices 00 to 4095 onSUBSYSA.

� Interval Task 2 on HOST2 controls the volumes on devices 00 to 4095 onSUBSYSB.

� The Dynamic DDSR volume selection specification on HOST1 includes thevolumes on devices 00 to 4095 on SUBSYSA and devices 00 to 4095 onSUBSYSB.

� The Dynamic DDSR volume selection specification on HOST2 includes thevolumes on devices 00 to 4095 on SUBSYSA and devices 00 to 4095 onSUBSYSB.

OperatingSystem

OperatingSystem

SUBSYSA00 - 4095

SUBSYSB00 - 4095

SUBSYSA00 - 4095

SUBSYSB00 - 4095

SUBSYSA00 - 4095

SUBSYSB00 - 4095

HOST1

C46264

HOST2

IntervalTask 1

IntervalTask 2

SUBSYSA00 - 4095

SUBSYSB00 - 4095

DynamicDDSR

DynamicDDSR

SUBSYSA00 - 4095

SUBSYSB00 - 4095

SUBSYSA00 - 4095

SUBSYSB00 - 4095

Figure 4-2. Task definition for both Dynamic and Interval DDSR


Device Selection Rules

DDSR Device Selection Rules

When you use the VOLUME, EXCLUDEVOLUME, SUBSYSTEM, andEXCLUDESUBSYSTEM parameters with either the RELEASE INTERVALDATAsubcommand or the RELEASE DYNAMICDATA subcommand, SVAA uses thefollowing rules to select the devices to be processed:

1. If there are no inclusion or exclusion parameters:

� For Interval DDSR, no functional devices are selected.� For Dynamic DDSR, all functional devices on all installed subsystems are

selected.

2. If there are any SUBSYSTEM parameters, all devices in subsystems notspecified are excluded from selection, even if the devices are specified inVOLUME parameters.

3. If there are any EXSUBSYSTEM parameters, the devices they specify areexcluded from selection.

4. If there are any VOLUME parameters, any devices not specified are excludedfrom selection.

5. If there are any EXCLUDEVOLUME parameters, the devices they specify areexcluded from selection.

Note: Wildcards and ranges are allowed in inclusion and exclusion parameters.

All of the following examples apply to this sample configuration of three SVAsubsystems, each with five volumes defined:

SUBSYSA1 SUBSYSA2 SUBSYSA3-------- -------- --------PROD33 WORK�1 PAYR�1PROD44 PAYR22 PAYR�2TEST�1 PAYR23 TEST�3PROD34 TEST�2 PROD41WORK�4 PROD42 TEST�6

Example 1. Specifying a list of volumes

VOL(WORK�1 PAYR�1 PAYR�2)

The three volumes specified are selected. All other volumes are excluded.

The asterisks indicate the selected volumes:

SUBSYSA1 SUBSYSA2 SUBSYSA3-------- -------- --------

PROD33 � WORK�1 � PAYR�1 PROD44 PAYR22 � PAYR�2

TEST�1 PAYR23 TEST�3PROD34 TEST�2 PROD41WORK�4 PROD42 TEST�6



Example 2. Specifying subsystems and volumes

SUBSYS(SUBSYSA1 SUBSYSA2) VOL(PROD� WORK�)

To be selected, devices must be included by both parameters. SUBSYSA1 containsfour volumes that satisfy the VOL specification; SUBSYSA2 contains two.



� PROD33 � WORK�1 PAYR�1� PROD44 PAYR22 PAYR�2TEST�1 PAYR23 TEST�3

� PROD34 TEST�2 PROD41 � WORK�4 � PROD42 TEST�6

Example 3. Specifying ranges of volumes

VOL(TEST�1:TEST�4 PROD3�:PROD48) EXVOL(PROD4�:PROD42)

All volumes with volume serial numbers ranging from TEST�1 through TEST�4 andfrom PROD3� through PROD48, but excluding PROD4� through PROD42, are selected.


SUBSYSA1 SUBSYSA2 SUBSYSA3-------- -------- --------� PROD33 WORK�1 PAYR�1� PROD44 PAYR22 PAYR�2

� TEST�1 PAYR23 � TEST�3 � PROD34 � TEST�2 PROD41

WORK�4 PROD42 TEST�6

Example 4. Specifying inclusion and exclusion of subsystems,inclusion of volumes

SUBSYS(SUBSYSA�) EXSUBSYS(SUBSYSA3) VOL(PROD�)

All volumes in SUBSYSA1 and SUBSYSA2 with a volume serial number starting withPROD are selected.


SUBSYSA1 SUBSYSA2 SUBSYSA3-------- -------- --------� PROD33 WORK�1 PAYR�1� PROD44 PAYR22 PAYR�2TEST�1 PAYR23 TEST�3

� PROD34 TEST�2 PROD41 WORK�4 � PROD42 TEST�6



Example 5. Specifying a range of volumes, and exclusion of asubsystem

VOL(PROD4�:PROD48) EXSUBSYS(SUBSYSA2)

All volumes with volume serial numbers ranging from PROD4� through PROD48, butexcluding any volumes in SUBSYSA2, are selected.


SUBSYSA1 SUBSYSA2 SUBSYSA3-------- -------- --------PROD33 WORK�1 PAYR�1

� PROD44 PAYR22 PAYR�2TEST�1 PAYR23 TEST�3

PROD34 TEST�2 � PROD41WORK�4 PROD42 TEST�6

Example 6. Specifying selection because not excluded

EXSUBSYS(SUBSYSA3) EXVOL(PROD�)

All volumes in subsystem SUBSYSA3 and all volumes with volume serial numbersbeginning with PROD are excluded. All other volumes are included, because onlyexclusion parameters are specified.



PROD33 � WORK�1 PAYR�1 PROD44 � PAYR22 PAYR�2 � TEST�1 � PAYR23 TEST�3 PROD34 � TEST�2 PROD41� WORK�4 PROD42 TEST�6

Example 7. Specifying exclusion of volumes

EXVOL(PROD� WORK�)

All volumes in all subsystems, except for volumes with volume serial numbersbeginning with PROD or WORK, are selected.



PROD33 WORK�1 � PAYR�1 PROD44 � PAYR22 � PAYR�2 � TEST�1 � PAYR23 � TEST�3 PROD34 � TEST�2 PROD41 WORK�4 PROD42 � TEST�6


DDSR SIMULATE Processing


DDSR can operate in simulate mode. In this mode all DDSR functions areperformed, including SMF processing, but no disk array space is released. You caninitiate simulated space release in three different ways:

� You can initialize Dynamic DDSR in simulate mode at system IPL time byspecifying the DYNDDSR parameter in the subsystem name table (the IEFSSNxxmember of the SYS1.PARMLIB data set). For example:

SVAA,SIBSSIPL,'KEY(4),DYNDDSR(S)'

(The IEFSSNxx member is discussed in detail in the SVAA for OS/390Installation, Customization, and Maintenance manual.)

� You can place Dynamic DDSR in simulate mode with the RELEASEDYNAMICDATA subcommand. For example:

RELEASE DYNAMICDATA(STATUS(SIMULATE))

� You can place the DDSR Main Task in simulate mode with the SETCHECK(SIMULATE) subcommand. (Either include this subcommand in theDDSR initialization parmlib member, or direct it to the Main Task with the SENDDSR subcommand from a batch job, TSO session, or OS/390 operator console.)

When the Main Task is in simulate mode, any DDSR function that is started orresumed will reactivate in simulate mode. For example, the following commandsequence will suspend all DDSR functions (including Dynamic DDSR and allInterval DDSR tasks), place the Main Task in simulate mode, and thenreactivate all space release functions.

SUSPEND RELEASE (RELID(�) DYNAMIC)

SET CHECK(SIMULATE)

RESUME RELEASE (RELID(�) DYNAMIC)

SET CHECK(NONE)


Chapter 5. Using SnapShot

Chapter SummaryMethods of Duplicating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Conventional DASD Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Duplication Using SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Invoking SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Snapping Functional Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Snapping Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Considerations for Multivolume Data Sets . . . . . . . . . . . . . . . . . . 5-7Considerations for Source Data Sets . . . . . . . . . . . . . . . . . . . . . 5-7Snapping to Data Sets of the Same Name . . . . . . . . . . . . . . . . . . 5-7

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7VSAM Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Snapping to New VSAM Target Data Sets . . . . . . . . . . . . . . . . . . 5-8Snapping to Existing VSAM Target Data Sets . . . . . . . . . . . . . . . . 5-8Snapping VSAM Alternate Index Data Sets . . . . . . . . . . . . . . . . . 5-8

Net Capacity Load Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Using Volume Preferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Considerations for Data Sets Spanning SVAs . . . . . . . . . . . . . . . 5-10Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10SnapShot Volume Selection and PPRC . . . . . . . . . . . . . . . . . . . . . . 5-10

Non-SMS Managed Environment . . . . . . . . . . . . . . . . . . . . . . . . 5-12SMS-Managed Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

SnapShot and DFSMSdss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14DFSMSdss Restriction for SnapShot on V2X, V2X2, and V2Xf . . . . . . . 5-14

Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Using Mixed Device Types and Limiting . . . . . . . . . . . . . . . . . . 5-15Summary of Mitigation Techniques . . . . . . . . . . . . . . . . . . . . . 5-15

November, 2006 — PN 311290512, Rev. N SnapShot 5-1

SnapShot

Traditionally, the task of duplicating data in the computer room has consisted ofcopying the data from one place to another, as in copying the data from one diskdevice to the same or to another disk device. StorageTek's duplication method,SnapShot, duplicates data sets or whole volumes without physically moving anydata, thus dramatically reducing the time required for duplication.

Methods of Duplicating Data

This section compares the SnapShot feature with conventional DASD copyprocessing.

Conventional DASD DuplicationHistorically, conventional methods of duplicating DASD data consist of making aphysical copy of the data, either on disk or on tape. These methods require thatany applications updating the data be quiesced for the duration of the copyoperation so that the data being copied is not corrupted. These copies may beaccomplished using any of a variety of programs, such as the IBM DFSMSdss orother utilities.

The Concurrent Copy function is an improvement over the conventional methods inthat it allows data to be copied while applications accessing the data remain active.The data being copied is saved in cache (or elsewhere) until the copy function hasfinished processing; the updates can then be applied to the source data set.

Dual Copy is another improved copy method; it allows a user to copy a volume ontotwo different physical disks. Once the dual copy pair has been established, the3990 controller copies the data from one volume to the other to synchronize thedata. In all future operations, the controller writes updates simultaneously to eachdisk in the dual copy pair. Then, one of the volumes can be used to copy the datato tape while the other volume continues in use for updates.

All of these copying methods enable the user to copy data from one place toanother with some degree of disruption to the applications using the data. Thesemethods require involvement of the host processor, the channel, and the DASDcontroller, and sometimes real and expanded storage.

Duplication Using SnapShotThe StorageTek SnapShot feature dramatically reduces the time required for dataduplication when compared to traditional copying, thus minimizing the downtime forapplications using the data. Furthermore, no additional physical disk or cachespace is used in making the duplicate.

SnapShot accomplishes this duplication quickly because:

� No data is moved� Only new pointers to the original volume or data set are created

The two independent sets of pointers treat the data as if it were two physicallyseparate images. Updates can occur simultaneously to the original data and to theduplicate, without compromising the data in either.

Note: StorageTek uses the term “snap” for the duplication function provided bySnapShot. We also use this term for the result of a snap operation. The data setor volume being duplicated is called the “source” and the object of the duplication iscalled the “target.” That is, with SnapShot, we snap the source onto the target.


Snapping Volumes

These terms suggest that this new form of data duplication is quick, economical ofresources, and easy to use.

Snaps of a data set or volume require a minimum of host resources. The actualsnapping is performed within the disk subsystem. The only physical back-endstorage allocated by the subsystem is for:

� The original data set (shared between the source and target).� Any changes made to the source data set.� Any changes made to the target data set.

You can use a snapped data set as the source of a transfer to tape whileapplications continue to use the original data set or volume.

Invoking SnapShot

SVAA Version 3.1 is a prerequisite for SnapShot.

With SnapShot you can snap volumes or data sets. Use a SNAP DATASET or SNAPVOLUME subcommand of SIBADMIN or SIBBATCH to perform a snap:

� In a batch job� In a REXX EXEC or in a CLIST� Using the TSO command line interface

You can also issue SNAP DATASET or SNAP VOLUME subcommands from ISPFpanels.

The following sections describe how SnapShot snaps volumes and data sets.

Snapping Functional Volumes

You use the SNAP VOLUME subcommand to snap a disk volume on an SVAsubsystem. For data integrity reasons, target volumes shared in a multi-hostenvironment should be offline to all hosts except the host executing the snapoperation. Furthermore, the target volume must be of the same device type andmodel (geometry) as the source volume. FlexVolumes and Large Volumes do notchange this requirement.

Notes:

1. You can snap an offline SCSI volume to an OS/390 3390 volume if SNAPVOLUME's OFFLINE parameter is used. Or you can snap an online SCSIvolume to an OS/390 3390 volume if the SCSI volume has been initialized with adevice number or volser. (This is done with the INIT parameter of the DEFINEDEVICE subcommand or with the INITIALIZE DEVICE subcommand.) However,you cannot snap an OS/390 volume to a SCSI volume.

2. PAV Alias devices cannot be the source or target of a volume snap.

3. The PPRC Remote SnapShot feature allows a PPRC secondary device to besnapped to another functional device on the same remote SVA subsystem asthe secondary device. The PPRCSnapShot hardware feature is a prerequisitefor both the local and remote subsystems.

When the snap is finished, the target volume is an exact duplicate of the sourcevolume. If you specify the COPYVOLID(YES) parameter, the label is retained fromthe source volume and SnapShot varies the target volume offline. If you specify


Snapping Data Sets

COPYVOLID(NO), the label of the target is restored and SnapShot varies the targetvolume online.

If the target of a SNAP VOLUME subcommand is not in the same SVA subsystemand partition as the source volume, SnapShot can call a data mover (the DFSMSdssutility) to physically copy the volume.

Note: The fact that you can specify the functional volumes to be used as targetsimplies that there are extra defined volumes available for this use.

Parameters of the SNAP VOLUME subcommand enable you to specify:

� The source volume to be snapped, identified by volser, device number, or DDname (SOURCE, VOLUME, UNIT, and INDDNAME parameters).

� An existing target volume, identified by volser, device number, or DD name(TARGET, VOLUME, UNIT, and OUTDDNAME parameters).

� A data mover to be used in case the specified snap cannot be performed(DATAMOVERNAME parameter).

� Whether the source volume is to overwrite data on the target volume (REPLACEparameter).

� Whether the source volser is to be copied to the target (COPYVOLID parameter,described above).

� Whether, when using the COPYVOLID(N) parameter, the target volume is to beconditioned completely or only its label (CONDITIONVOLUME parameter).

� Whether to enable a volume to be snapped when exclusive serialization controlcannot be obtained (TOLERATEENQFAILURE parameter).

� Whether to log diagnostic messages (DEBUG parameter).

� Whether to generate GTF trace records (TRACE parameter).

� Whether the source or target volume can be offline (OFFLINE parameter).

� A remote target functional device when using the RemoteFunctionalDeviceIDand SerialNumber subparameters of the TaRGet parameter.

A complete description of the SNAP VOLUME subcommand and its parametersbegins on page 8-185.

You can specify the same parameters and submit the subcommand with theSPECIFY SNAP VOLUME SUBCOMMAND panel. The panel description begins onpage 7-101.

Snapping Data Sets

You use the SNAP DATASET subcommand to snap the following types of data sets:

� Physical Sequential (PS) data sets� Partitioned (PO) data sets (except TYPE=HFS)� Direct access (DA) data sets� Extended partitioned data sets (PDSE)� Extended format sequential data sets� Striped sequential data sets� Multivolume data sets� The following types of VSAM data sets:


Snapping Data Sets

- Alternate Index (AI) - ESDS - KSDS - Linear - RRDS - VRRDS - Extended Format

SnapShot does not snap the following types of data sets:

� Catalog data sets� Undefined data sets� ISAM data sets

� VTOCs � Indexed VTOCs� VSAM Volume Data Sets (VVDS)� Individual members of partitioned data sets� GDG base names� Page data sets� Concatenated data sets� Open Edition HFS data sets� Key range data sets� VSAM data sets with IMBED or REPLICATE� Non-VSAM multivolume extended format data sets

Notes:

1. The data set being snapped cannot have zero extents.

2. PAV Alias devices cannot be the source or target of a data set snap.

When you use the SNAP DATASET subcommand, you specify the source data seteither by the data set name or indirectly by referring to a preallocated DD name forthe data set. Similarly you specify the target data set either by its data set name orindirectly by a preallocated DD name. If the target data set does not exist,SnapShot assumes DISP=NEW and creates the data set. If the target does exist,SnapShot uses DISP=OLD or DISP=SHR, depending on whether you specifyEXCLUSIVE or SHARED on the HOSTCOPYMODE parameter and depending on theuse of the TOLERATEENQFAILURE parameter. When you snap to previouslyallocated data sets, all extents for the target data set must reside on a volume thatis currently online and accessible to the host requesting the snap.

SnapShot always attempts to perform a snap, but if a snap is not feasible,SnapShot can call a data mover (the DFSMSdss utility) to duplicate the data set.This is not a snap, but a conventional copy, which takes much longer than a snap.(A snap is not feasible if the target data set is not within the same SVA subsystemand partition as the source data set.)

Note: If the source and target data sets exist on device types other than 3380 or3390, the subcommand fails and the data mover is not invoked.

SnapShot duplicates disk tracks, whether the duplication is a snap or a copy. Tobe usable, the logical components of a defined target must agree with those of thesource. Therefore, a target allocation must have DCB attributes including the dataset organization (DSORG) identical to those of the source. If DCB attributes otherthan the DSORG are not identical, SnapShot uses those of the source, warns theuser that it is doing so, and continues processing. If the DSORG does not match,the snap will fail.


Snapping Data Sets

Normally, the size of a single extent is not important to the operation of snapping adata set. However, the Partitioned Dataset Access Method requires that themember directory reside within the first extent. For performance reasons, SnapShotdoes not check the size of the member directory, but issues a warning message ifthe first extent of the target is smaller than the first source extent.

SnapShot works with SMS as follows:

� If you specify storage, data, and management classes on the SNAP DATASETsubcommand, SnapShot supplies the classes to DYNALLOC.

� SnapShot does not modify SMS ACS rules in order to accomplish a snapoperation.

� SnapShot uses its “volume preferencing” facility to filter out SMS assignmentsthat are not to the same subsystem as the source. (See “Using VolumePreferencing” on page 5-9 for more information.)

� Prior to allocating a new target data set, SnapShot calls the ACS routines andpasses the following values from the SNAP DATASET subcommand: data setname and volume list, as well as storage class, management class, and dataclass, if specified. No other values are passed to the ACS routines during thisfirst call.

From the first call to the ACS routines, SnapShot obtains the validated SMSclasses. These SMS classes are used by SnapShot to allocate a target VSAMdata set. Thus, when allocating VSAM data sets, SnapShot supports only thefollowing ACS values: data set name, volume list, storage class, managementclass, and data class.

� Allocation of non-VSAM data sets is handled differently. Non-VSAM data setsare allocated using DYNALLOC. SnapShot ignores the SMS classes returned bythe first call of the ACS routines and allows DYNALLOC to handle the SMSprocessing. Thus, for the allocation of non-VSAM data sets, SnapShot supportsall ACS filter variables supported by DYNALLOC.

Parameters of the SNAP DATASET subcommand enable you to specify:

� A data set to be snapped, identified by data set name, style:filename, or DDstatement (SOURCE or INDDNAME parameters).

� A new or existing target data set, identified by data set name, an appropriatestyle and filename, or DD statement (TARGET or OUTDDNAME parameters).

� The volumes to which a data set is to be snapped (ESOTERIC or VOLUMEparameters).

� The SMS storage attributes and management class desired for the new targetdata set (DATACLASS, STORAGECLASS, and MANAGEMENTCLASS parameters).

� Whether a data mover is to be used when the SnapShot criteria for the sourceand target are not met (DATAMOVERNAME parameter).

� Error disposition—whether the target data set is to be kept or deleted when anerror occurs (ERRDISP parameter).

� Whether the target data set is to be cataloged (CATALOG parameter).

� That data sets are to be snapped when a requested level of serializationcontrol cannot be obtained (TOLERATEENQFAILURE parameter).


Terminology

� That a supported non-VSAM data set be truncated if the target data set issmaller than the source (TOLERATETRUNCATION parameter).

� The maximum number of volumes on which the target data set will be allocated(VOLUMECOUNT parameter).

� The level of serialization control to be obtained for the source and target datasets (HOSTCOPYMODE parameter).

� The name of the base cluster to which the target alternate index is to berelated (RELATE parameter).

� Whether the source data set is to overwrite data on an existing target data set(REPLACE parameter).

� Whether absolute track and unmovable data sets are to be snapped (FORCEparameter).

� Whether to log diagnostic messages (DEBUG parameter).

� Whether to generate GTF trace records (TRACE parameter).

A complete description of the SNAP DATASET subcommand and its parametersbegins on page 8-172.

You can specify the same parameters and submit the subcommand with theSPECIFY SNAP DATASET SUBCOMMAND panel. The panel description begins onpage 7-97.

Considerations for Multivolume Data Sets

SnapShot allows snapping of a single volume source data set to a multivolumetarget data set and vice versa. SnapShot handles multivolume data sets that spanSVAs as a datamover operation.

For multivolume target data sets, not managed by DFSMS, a volume list must bespecified.

Note: When you are using a multivolume data set as the source of a SnapShotoperation, OS/390 allows only 65535 tracks per data set per DASD volume. Youmust ensure that you have enough volumes and tracks available to hold your targetdata set. If they are not available, an error occurs and the snap fails.

Considerations for Source Data Sets

Data sets supplied using the SOURCE parameter must be cataloged. Uncatalogedsource data sets must use the INDD parameter. The source data set must alsohave a unique name, different from the TARGET, if it is supplied.

Snapping to Data Sets of the Same Name

If the source and target data sets of a snap have the same name, and they arenon-SMS, you must use the INDD and OUTDD parameters.

Terminology

This manual may indicate that an action you request is either not allowed or notsupported by SnapShot:


VSAM Considerations

� A request is not allowed when the request cannot be fulfilled by SnapShot. Inthe case of a failure or processing stop, SnapShot issues a message.

� A request is not supported if it cannot be evaluated by SnapShot. SnapShotissues no error message in this case and the results may be unpredictable.

VSAM Considerations

Snapping to New VSAM Target Data Sets

New targets for VSAM SnapShot are allocated differently depending on whetherthey are SMS managed. Non-SMS targets have their first volume's total allocationamount requested on the first target volume. Additional space is obtained viaextend processing, as with non-VSAM.

When allocating SMS-managed VSAM data sets, SnapShot supports only thefollowing ACS values: data set name, volume list, storage class, managementclass, and data class. SMS-managed VSAM targets that are single volume areallocated with their original primary and secondary amounts. Extend processingobtains additional space if required. Multivolume targets have their entire allocationquantity requested over the target volumes (supplied by VOLUME, VOLUMECOUNT,number of source volumes) with SMS allocating the extents as required.

A VSAM data set snapped to a multivolume target may have its data componentplaced on a different volume from its index component. If you need to have boththe data component and the index component on the same volume, use theVOLUME parameter of the SNAP DATASET subcommand to specify a target volume.

If the target space cannot be obtained, the SnapShot operation terminates.

Snapping to Existing VSAM Target Data SetsThe VSAM type (that is, KSDS, linear, etc.) for both the source and target data setsmust match or the snap will fail. SnapShot will extend an existing target data set tomatch the size of the source data set. If required, the target attributes will bealtered to match the source attributes, other than VSAM type.

Snapping VSAM Alternate Index Data Sets

An alternate index is a key-sequenced data set containing index entries organizedby the alternate keys of its associated base data cluster records. An alternateindex provides another way of locating records in the data component of a cluster.

SnapShot can be used to snap individual alternate indexes by name. It cannotsnap a Sphere (a related collection of base clusters and alternate indexes) or aPath (a unique catalog entry that provides a named relationship between a basecluster and an alternate index). After snapping an alternate index and a basecluster, it may be necessary to use the IDCAMS DEFINE PATH function to create aPath through which the alternate index can be used to access the base cluster.

Because SnapShot cannot snap a base cluster and all of its related alternateindexes at the same time, care must be taken to ensure the integrity of therelationship between the base cluster and the alternate index. If an alternate indexand its related base cluster are to be snapped together, update activity to the basecluster and alternate index should be quiesced while the snaps are taking place.

Use the RELATE parameter of the SNAP DATASET subcommand when snapping analternate index to specify the base cluster to which the TARGET alternate index will


Volume Preferencing

be related. If the TARGET alternate index has been preallocated, the RELATEparameter is ignored, and the TARGET alternate index will be related to the existingbase cluster name. If the TARGET alternate index is created by SnapShot, and theRELATE parameter is not specified, the TARGET alternate index will be related tothe same base cluster as the SOURCE alternate index.

If the TARGET is created by SnapShot, the UPGRADE attribute of the TARGETalternate index will match the UPGRADE attribute of the SOURCE alternate index. Ifthe TARGET is preallocated, the UPGRADE attribute of the TARGET will not beaffected by the snap.

An SMS-managed alternate index has the same management class and storageclass as its base cluster. The DATACLASS parameter can be used to assign anSMS data class to the TARGET alternate index that is different from the data class ofthe SOURCE.

If the base cluster specified in the RELATE parameter is an extended format dataset, the TARGET alternate index must also be extended format.

Net Capacity Load Considerations

When you are using SnapShot functions with an SVA subsystem, you shouldconsider the effect of the snapped volumes or data sets on the net capacity load(NCL) of the subsystem. When a source is first snapped, the snap consumes noback-end storage because the source and target share the same tracks. No extraspace is needed to accommodate the new volume or data set at this point.

As updates are made, however, new tracks are written to the disk arrays. Themore updates that occur to each of the snaps the more tracks are written on behalfof each. These new tracks occupy more back-end storage as the source and targetdiverge. It is possible that either the source or target are completely rewritten. Thepotential effect on NCL must be considered in this case.

If NCL becomes a concern, you may need to consider how long you keep snappedvolumes or data sets on the SVA subsystem. The length of time you keep thesnaps and the rate at which they become unique because of updates shoulddetermine when the snaps can be deleted to make room for other snaps, or tolower the overall subsystem NCL.

Using Volume Preferencing

Volume preferencing is a facility that enables SnapShot to filter the choice of anSMS target volume for newly allocated data sets. You initialize volume preferencingin one of two ways:

� During SVAA installation, by customizing the IEFSSNxx member ofSYS1.PARMLIB. Volume preferencing can be installed initially as active orinactive, for each OS/390 subsystem.

� During SVAA subsystem initialization or reinitialization, with the SIBMVSScommand. The initial active or inactive state of volume preferencing can bemodified at this time.

See the SVA SnapShot for OS/390 Installation, Customization, andMaintenance manual for more information.


Volume Preferencing

With volume preferencing initialized as inactive for each OS/390 subsystem, you canuse the SET VOLUMEPREFERENCING subcommand to make the facility active. (Youcan also make the facility inactive again later.)

The QUERY VOLUMEPREFERENCING subcommand enables you to determine thestatus of volume preferencing (active or inactive) for each OS/390 subsystem.

Considerations for Data Sets Spanning SVAs

For data sets with more than one component such as VSAM data sets, differentcomponents may reside on different SVAs. In this case, volume preferencingdictates that one component will be snapped, usually the largest, and the others willbe copied via a data mover. If the target data set is to be dynamically allocated,the allocation will be based on the snapped component.

Similarly, a data set may contain extents that reside on different SVAs. The extentson the volume-preferenced SVA will be snapped; the extents on other SVAs will becopied via a data mover.

Note: NCL will increase only for that portion of the data set that is copied via adata mover.

Security Considerations

SnapShot provides two levels of security: data set or volume-level security andSnapShot command-level security.

� To implement SNAP DATASET, no change is required to your existing securityprocess. The SNAP DATASET subcommand opens the source for input andopens the target for output to verify that the user has proper access to performthe snap.

� Similarly, to implement SNAP VOLUME, no change is required to your existingsecurity process. The SNAP VOLUME subcommand calls SAF with DASDVOLrequests to verify device level access.

� SnapShot implements command-level security by introducing a new resourcerule that can be defined to further enhance your security. Command levelsecurity is definable down to the device or data set level.

� SnapShot supplies user exits to enable you to customize security of commandprocessing to meet your needs.

See the SVA SnapShot for OS/390 Installation, Customization, and Maintenancemanual for more information about security procedures.

SnapShot Volume Selection and PPRC

Unless the Snap to Primary feature is present, a Peer-to-Peer Remote Copy (PPRC)volume is not allowed as a target of a SnapShot but is allowed as a source.Because only a subset of I/O operations is allowed, a PPRC secondary volume isnot allowed as either a source or a target of a SnapShot. If a PPRC secondaryvolume is used as a target or a source of a SnapShot, an error message is issued.However, if Snap to Primary is enabled, a PPRC volume can be the target of aSnapShot. See “Snap to Primary” on page 2-10 for more information.


PPRC

The user is responsible for controlling the interactions between PPRC volumes andSnapShot. The following tables describe situations in which PPRC and SnapShotcan interact, and give suggestions on how to handle such situations.


PPRC

Non-SMS Managed Environment

Table 5-1. PPRC/SnapShot Interactions for Non-SMS Environment

SITUATION SOLUTION

SNAP VOLUME

OUTDDNAME parameters hard-coded JCL VOL/UNIT

parameters.1. Change the hard-coded JCL VOL/UNIT to use a

non-PPRC volume.

2. Use a different volume for PPRC.

3. Delete the PPRC pair, run the SnapShot, andre-establish the PPRC pair.

TARGET parameter and hard-coded SnapShotVOLUME/UNIT parameters.

Same as above, except change the hard-codedSnapShot VOLUME/UNIT to use a non-PPRC volume.

SNAP DATASET: Static or dynamic old allocation

Static allocation: OUTDDNAME parameter and targetdata set is cataloged (JCL VOL/UNIT parameters areirrelevant).

1. Move target data set to a non-PPRC volume.



Dynamic allocation: TARGET parameter and target dataset is cataloged (SNAPSHOT VOLUME parameter isignored).

Same as above.

SNAP DATASET: Static or dynamic new demand allocation

Static allocation: OUTDDNAME parameter andhard-coded JCL VOL/UNIT parameters specifying a singlevolume or device number.

1. Change the hard-coded JCL VOL/UNIT to use anon-PPRC volume.



Dynamic allocation: TARGET parameter andhard-coded SnapShot VOLUME/UNIT parametersspecifying a single volume or device number.

Same as above, except change the hard-codedSnapShot VOLUME/UNIT to use a non-PPRC volume.

SNAP DATASET: Static or dynamic new esoteric

Static allocation: OUTDDNAME parameter andhard-coded JCL UNIT parameter specifying an OS/390generic or esoteric group name.

1. Change the hard-coded JCL UNIT parameter to usea group that does not contain PPRC volumes.


3. Remove the PPRC volumes from the esotericusing:

a. HCD and a dynamic I/O configuration change.

b. MVSCP and an IPL.

Dynamic allocation: TARGET parameter andhard-coded SnapShot ESOTERIC parameter specifyingan OS/390 generic or esoteric group name or devicenumber.

Same as above, except change the hard-codedSnapShot ESOTERIC parameter to use a group thatdoes not contain PPRC volumes.

SNAP DATASET: Third-party software volume selection

A third-party software package performs volumeselection using a rules-based language.

Change the rules to remove PPRC volumes fromselection.


SnapShot and DFSMSdss

SMS-Managed Environment

Table 5-2. PPRC/SnapShot Interactions for SMS Environment

Situation Solution

SNAP VOLUME

OUTDDNAME parameter hard-coded JCL VOL/UNIT

parameters.Same as Non-SMS Managed.

TARGET parameter and hard-coded SnapShotVOLUME/UNIT parameters

Same as above except Non-SMS Managed.

SNAP DATASET: Static or dynamic old allocation

Static allocation: OUTDDNAME parameter and targetdata set is cataloged (JCL VOL/UNIT parameters areirrelevant).

Same as Non-SMS Managed.

Dynamic allocation: TARGET parameter and target dataset is cataloged (SnapShot VOLUME parameter isignored).


SNAP DATASET: Static or dynamic new and Guaranteed Space

Static allocation: OUTDDNAME parameter andhard-coded JCL VOL/UNIT parameters specifying a singlevolume or device number (Guaranteed Spaceparameter is assumed).


Dynamic allocation: TARGET parameter andhard-coded SnapShot VOLUME/UNIT parametersspecifying a single volume or device number.


SNAP DATASET: Static or dynamic new demand allocation

Static allocation: OUTDDNAME parameter andhard-coded JCL DATACLAS, MGMTCLAS, and/or STORCLAS

parameters

1. Change the hard-coded JCL parameters to causeACS routines to select a Storage Group that doesnot contain PPRC volumes.


3. Remove the PPRC volumes from the assignedStorage Group.

4. Change the ACS routines to select a StorageGroup that does not contain PPRC volumes.

Dynamic allocation: TARGET parameter andhard-coded SnapShot DATACLAS, MGMTCLAS, and/orSTORCLAS parameters.

Same as above.

SNAP DATASET: Third-party software volume selection

A third-party software package performs volumeselection using a rules based language.

Change the rules to remove PPRC volumes fromselection.


DFSMSdss uses an API, SVAA's Low Level API (LLAPI), to invoke SnapShot. Thissection provides some helpful tips on diagnosing problems with the interactionbetween DFSMSdss, the API, and SnapShot.



SymptomsA problem detected by DFSMSdss typically results in an error message like the onebelow:

ADR735W (��2)-mmmmm(yy), date time USE OF CONCURRENT COPY FAILEDFOR DATA SET dsname ON VOLUME volser, �14.SERIALIZATION WILL BE HELD AND CONCURRENT COPY WILL NOT BE USED.

DIAGNOSTIC INFORMATION: ��1791-��5��F

IBM documents this message and its reason code in the MVS System Messagesmanuals. However, the following information may help you to diagnose theproblem:

� The 014 return code indicates that there was an error invoking concurrent copyor SnapShot.

� The system data mover return code and reason code are 00001791-0005000F.These codes are also documented in IBM's MVS System Messages manuals.

- The system data mover return code 00001791 (decimal 6033) indicatesthat the SnapShot operation failed.

- The 0005 portion of the 0005000F system data mover reason codeindicates that an SnapShot-related error has occurred.

- The 000F portion of the 0005000F system data mover reason codeindicates that the SnapShot target is a member of a PPRC pair. Thisreason code is documented in Appendix G's SIBLLRB section of theShared Virtual Array Administrator for OS/390 and VM Messages andCodes manual. This particular error occurs if you attempt to snap to aPPRC primary and you do not have the PPRCSnapShot feature installedalong with Snap to Primary support.

DFSMSdss Restriction for SnapShot on V2X, V2X2, and V2XfAn IBM restriction currently limits DFSMSdss-invoked SnapShots to a subset of2045 out of the 4096 possible online devices that can exist on a V2X, V2X2, orV2Xf. Because the IBM ANTRQST macro is limited to a 32K storage area forholding the results of queries (QRYSIZE parameter is only a halfword), only alimited number of devices (2045) can be returned to DFSMSdss.

Note: The source and target devices must both be present in the list of devicesreturned to DFSMSdss if SnapShot is to be used instead of a physical copy.

"Native" SnapShots (i.e., SnapShots invoked directly through SIBBATCH, the SVAAISPF panels, and the SVAA command-line interface) are not affected by thisrestriction. No similar restrictions are known to exist with any other softwareproduct's use of SnapShot.

Symptoms

Customers encountering this restriction in DFSMSdss batch jobs may receive thefollowing DFSMSdss error message and a return code of 4:

ADR934W (��1)-ALLOC(�1), THE ANTRQST MACRO FAILED DURING ANSQRYDVCS REQUEST WHILE PROCESSING DATA SET dsname.

DIAGNOSTIC INFORMATION: ��1CA4-��



The copy operation is still performed, but DFSMSdss makes a physical copy of thedata rather than use SnapShot. As a consequence, jobs will take longer tocomplete and they will consume additional disk array space.

Using Mixed Device Types and LimitingOnline Devices as a Mitigation Technique

On the V960 and earlier virtual subsystems, both the source and target functionaldevices are always guaranteed to be included in the list of SnapShot-eligibledevices that is returned to DFSMSdss, since less than 2045 online devices can existon these subsystems.

The general requirement for DFSMSdss SnapShot eligibility is that the devices mustbe online and have a 3380 or 3390 device type (if the PowerPPRC and/orPPRCSnapShot hardware features are installed, note that PPRC Secondarydevices are never eligible).

Note: Although offline devices are now supported by native SnapShot, thesedevices are not returned to DFSMSdss and do not count against the 2045 limit. Asnoted before, the 2045 restriction does not apply to native SnapShots.

Because DFSMSdss cannot handle more than 2045 online devices, you may beforced to manipulate two key factors to influence the composition of this list in yourfavor:

� Geometry — Volume SnapShot requires both source and target functionaldevices to have the same device type (3380/3390) and capacity (modelnumber, such as a 3390-3). Defining 2045 3380 functional devices (of thesame capacity) and 2045 3390 functional devices (of the same capacity),therefore avoids the IBM restriction. In this case, it's not where the devices aredefined that is important, it's how many devices are defined that is important.

Data set SnapShot requires both source and target functional devices to havethe same device type (3380/3390). Capacity (model number) is irrelevant, sosimply defining 2045 3380 functional devices (of any capacity) and 2045 3390functional devices (of any capacity) avoids the IBM restriction for data sets.

� Online / Offline status — DFSMSdss-invoked SnapShot requires both sourceand target functional devices to be online, so limiting the number of onlinedevices can avoid the IBM restriction. Again, although offline devices aresupported by native SnapShot, these devices are not returned to DFSMSdssand do not count against the 2045 limit.

Summary of Mitigation Techniques

1. Use native SnapShot instead of DFSMSdss. Other than the normal SnapShotrestrictions, there are no other limitations on the eligibility of source and targetfunctional devices

2. Limit the size of the SnapShot-eligible device list through one or more of thefollowing means:

� Define all functional devices as 3390-9 devices. Since the V2X, V2X2,and V2Xf disk arrays support a maximum of 1365 3390-9 devices (thesame virtual capacity as 4096 3390-3 devices), the restriction can beavoided with no sacrifice in virtual capacity



� Define 2045 functional devices as 3380s and 2045 functional devices as3390s

� Limit the number of online functional devices to 2045 or less for eachoperating system

� Define a combination of 3390-9 and 3390-3 functional devices below the2045 limit

3. Define two SMS storage groups, one for each half of the V2X, V2X2 or V2Xf,and modify your ACS routines to direct dynamically-created new targetallocations to the same half as the source device


Chapter 6. SVAA Configuration Tasks: An Outline

Chapter SummaryAltering Subsystem Global Characteristics . . . . . . . . . . . . . . . . . . . . . 6-2Altering Channel Interface Characteristics . . . . . . . . . . . . . . . . . . . . . 6-2

Altering a Parallel Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Altering an ESCON Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Altering a FICON Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Altering a SCSI I/O Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Altering a Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Configuring Functional Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Defining a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Altering Characteristics of a Functional Device . . . . . . . . . . . . . . . . . 6-6Changing the Partition of a Functional Device . . . . . . . . . . . . . . . . . 6-6Changing the Device Type of a Functional Device . . . . . . . . . . . . . . . 6-7Deleting a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Disabling a CKD Functional Device . . . . . . . . . . . . . . . . . . . . . . . . 6-9Disabling a SCSI Functional Device . . . . . . . . . . . . . . . . . . . . . . . 6-9

Defining Additional Privileged ECAM Devices . . . . . . . . . . . . . . . . . . 6-10Reconfiguring Subsystem Disk Array Capacity . . . . . . . . . . . . . . . . . . 6-11

Allocating Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Establishing the Test Partition's Disk Array Capacity . . . . . . . . . . . . . 6-12Forming Additional Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Moving Disk Array Capacity from Test Partition to Production . . . . . . . 6-13Removing the Test Partition's Disk Array Capacity . . . . . . . . . . . . . . 6-13Reconfiguring an Existing Array . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Displaying the Drive Module Configuration . . . . . . . . . . . . . . . . . . . . 6-15Starting a Drain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15Reporting on Drain Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

| Configuring V2Xf PPRC with Cascaded FICON Switches in a WWNN Domain 6-15

November, 2006 — PN 311290512, Rev. N Configuration Tasks 6-1

Configuration Tasks

This chapter lists the steps involved in performing configuration tasks and providesreferences to the places in this manual where you can find detailed informationabout those tasks.

Altering Subsystem Global Characteristics

The name of an SVA subsystem and a subsystem identifier (SSID) for at least onelogical 3990 controller emulated within the subsystem must be defined at the LOPor the DOP. With SVAA (using either a subcommand or ISPF panels) you can:

� Change the subsystem name

� Change SSIDs

� Change the site name (optional)

� On the 9393 or 9500 SVA: Change the default array size (5+2 or 13+2). Theonly array size available on the V2X or V960 SVA is 13+2.

The following table identifies the topics and pages in this manual that describesubsystem configuration tasks.

Subcommand Panel

Select subsystem ALTER SUBSYSTEM (page8-29): SUBSYSTEM

parameter

SVAA SUBSYSTEM SELECTION (page7-13): type S to select subsystem

Alter subsystemcharacteristics

ALTER SUBSYSTEM SUBSYSTEM CONFIGURATION (page7-15)

Altering Channel Interface Characteristics

For an SVA ESCON or FICON channel, SCSI I/O interface, or fibre channel, the onlycharacteristic you can alter is the interface name. No disabling or varying offline isinvolved, so the procedures require fewer tasks than for a parallel (bus and tagcables) channel interface.

Altering a Parallel ChannelTo change characteristics of one or more parallel channel interfaces:

1. Vary the channel offline from the host operating system.

2. Use SVAA subcommands or panels to perform the tasks in the table below.

3. Vary channel online to the host operating system.

Subcommand Panel

Select channel type CHANNEL TYPE SELECTION (page 7-21):type S to select channel type

Select channel ALTER CHANNEL (page8-13): IFID parameter

CHANNEL SELECTION (page 7-22):type S to select channel

Disable channel ALTER CHANNEL:DIS parameter

CHANNEL CONFIGURATION (page 7-25):type N in Enabled field

Alter channelcharacteristics

ALTER CHANNEL CHANNEL CONFIGURATION


Configuration Tasks

Subcommand Panel

Enable channel ALTER CHANNEL (secondexecution ofsubcommand): ENA

parameter

CHANNEL CONFIGURATION:type Y in Enabled field

Altering an ESCON ChannelTo change the name of the channel interface for one or more ESCON channels:

Subcommand Panel




Alter channelinterface name

ALTER CHANNEL: NAME

parameterCHANNEL CONFIGURATION (page 7-27)

Altering a FICON ChannelTo change the name of the channel interface for one or more FICON channels:

Subcommand Panel




Alter channelinterface name

ALTER CHANNEL: NAME


Altering a SCSI I/O InterfaceTo change the name of one or more SCSI I/O interfaces:

Subcommand Panel


Select I/O interface ALTER CHANNEL (page8-13): IFID parameter


Alter I/O interfacename

ALTER CHANNEL: NAME


Altering a Fibre ChannelTo change the name of one or more fibre channels:

Subcommand Panel





Configuration Tasks

Subcommand Panel

Alter channel name ALTER CHANNEL: NAME



Configuration Tasks

Configuring Functional Devices

The configuration of a functional device may consist of one or more of the followingactivities:

� Defining a device

� Altering the characteristics of a device

� Changing the partition of a device

� Changing the device type of a device

� Deleting a device

� Disabling host access to a CKD or SCSI device

Defining a Functional DeviceTo define the characteristics of a functional device:

1. Define the device to all host operating systems using the I/O configurationprogram (IOCP) or hardware configuration definition (HCD).

If you add devices using OS/390 HCD after the SVA subsystem is initialized, youmust run SIBMVSS using the command

ALTER SSNAME (NAME (ssname) REINIT RIM(DMQ) )

before devices can be accessed by SVAA.

2. Define the device to the subsystem using the SVAA subcommand or panelsnamed in the following table. A PAV Base device must be defined before anyof its related Alias devices can be defined.

3. Initialize the device with ICKDSF or other appropriate utility.

Note: If defining a PAV Alias or Power PPRC Bridge device, do not performthis step. Do not initialize PAV Alias or Power PPRC Bridge devices.

4. Vary the device online.

Note: If defining a PAV Alias or Power PPRC Bridge device, do not performthis step. Do not vary PAV Alias or Power PPRC Bridge devices online to anyz/OS or OS/390 operating system.

Note: Each SVA subsystem has a minimum missing-interrupt handler (MIH) timeoutvalue which must be set for all devices defined to the subsystem. For informationabout setting the MIH timeout value, see the steps for customizing the IECIOSxx andIEFSSNxx members of SYS1.PARMLIB in the SVAA for OS/390 Installation,Customization, and Maintenance manual.

Subcommand Panel

Define device DEFINE DEVICE (page 8-38) INSERT FUNCTIONAL DEVICE (page7-40) orREPLICATE FUNCTIONAL DEVICE (page7-48)


Configuration Tasks

Altering Characteristics of a Functional DeviceTo alter the characteristics of a functional device, use the SVAA subcommand orpanel named in the following table.

Notes:

1. You cannot change the device type or partition for a device in this process.See “Changing the Device Type of a Functional Device” on page 6-7 and“Changing the Partition of a Functional Device” for procedures for these tasks.

2. For Power PPRC Bridge devices, you cannot change the PRIVILEGEDECAM,SCSIENABLE, or SCSIREADWRITE values, or specify a value for theSCSIADDRESS parameter.

3. For PAV Alias devices, you cannot change the CACHE, CKDENABLE,CKDREADWRITE, DASDFASTWRITE, NAME, or PRIVILEGEDECAMattributes.

4. You cannot change the number of cylinders of a device without deleting(backup all data first) and then redefining the device.

Subcommand Panel

Alter characteristicsof device

ALTER DEVICE (page 8-20) UPDATE FUNCTIONAL DEVICE (page7-56)

Changing the Partition of a Functional DeviceNotes:

1. You cannot define new devices to the Test partition on the SVA.

2. All PAV and Power PPRC Bridge devices must be defined to the Productionpartition.

To change the partition (Test to Production) with which a device is associated:

1. Move all data on the functional device to an auxiliary device (tape or disk).

2. Vary the device offline to all host operating systems. Note that PAV Aliasdevices cannot be varied online or offline to MVS.

3. Use SVAA subcommands or panels to perform the tasks in the following table.

Subcommand Panel

Delete device DELETE DEVICE (page 7-61) DELETE FUNCTIONAL DEVICE (page7-63)

Define device(specifyingProduction partition)

DEFINE DEVICE (page 7-40):PARTITION parameter

INSERT FUNCTIONAL DEVICE (page7-42) orREPLICATE FUNCTIONAL DEVICE (page7-48): change Partition field

Enable CKD device DEFINE DEVICE (page 8-38):CKDENA parameter

INSERT FUNCTIONAL DEVICE (page7-42) orREPLICATE FUNCTIONAL DEVICE (page7-49): type Y in CKD Enabled field

Enable SCSI device DEFINE DEVICE (page 8-38):SCSIENA parameter

INSERT FUNCTIONAL DEVICE (page7-42) orREPLICATE FUNCTIONAL DEVICE (page7-49): type Y in SCSI Enabled field


Configuration Tasks


Note: Do not initialize PAV Alias or Power PPRC Bridge devices.

5. Vary the device online to all host operating systems.

Note: Do not vary PAV Alias or Power PPRC Bridge devices online to anyhost operating system.

6. Restore the functional device data from the auxiliary device.

Changing the Device Type of a Functional DeviceNote: You cannot change the device type for Power PPRC Bridge devices.

To change the device type of a functional device:

1. Move all data on the functional device to an auxiliary device (tape or disk).

2. Vary the device offline to all host operating systems.

Note: PAV Alias devices cannot be varied online or offline.


4. Redefine the device type to all host operating systems (using IOCP or HCD).


Note: Do not initialize PAV Alias or Power PPRC Bridge devices.

6. Vary the device online to all host operating systems.

Note: Do not vary PAV Alias or Power PPRC Bridge devices online to anyhost operating system.

7. Restore data to the functional device (which cannot be a PAV Alias device)from the auxiliary device.

Subcommand Panel


Define device(specifying newdevice type)

DEFINE DEVICE (page 8-38):DEVICETYPE parameter

INSERT FUNCTIONAL DEVICE (page7-42) orREPLICATE FUNCTIONAL DEVICE (page7-49): enter new device type

Enable CKD device DEFINE DEVICE (page 8-38):CKDENA parameter

INSERT FUNCTIONAL DEVICE (page7-42) orREPLICATE FUNCTIONAL DEVICE (page7-49): type Y in CKD Enabled field

Enable SCSI device DEFINE DEVICE (page 8-38):SCSIENA parameter

INSERT FUNCTIONAL DEVICE (page7-42) orREPLICATE FUNCTIONAL DEVICE (page7-49): type Y in SCSI Enabled field


Configuration Tasks

Deleting a Functional DeviceTo delete a functional device:


2. Vary all paths to the device offline from all hosts and LPARs.

3. Use the SVAA subcommand or panels named in the following table to deletethe functional device.

4. Optionally, remove all host operating system definitions for the device (usingIOCP or HCD).

The rules for deleting Base and Alias devices are as follows:

� To delete a CKD or SCSI device (non-PAV, has no Aliases)

1. Vary the device offline to all host operating systems

2. Delete the device using the SVAA subcommand or panels

3. Optionally, remove all host operating system definitions for the device

� To delete a PAV Base device that does not have Aliases using the SVAAsubcommands or panels:



� To delete a PAV Base device that has Aliases


2. Delete each Alias related to the Base; use DISPLAY DEVICE or LISTCFGDEVICE to determine the Aliases to be deleted. You cannot delete a Baseand its related aliases in a single delete operation.

3. Delete the Base device using the SVAA subcommand or panels


� To delete a PAV Alias device that is related to an online Base


2. Delete the Alias device using the SVAA subcommand or panels


� To delete a PAV Alias device that is related to an offline Base

1. Simply delete the Alias device using the SVAA subcommand or panels


� To delete a misdefined PAV Alias (genned as Base, defined as Alias)

1. Simply delete the Alias device using the SVAA subcommand or panels

Subcommand Panel



Configuration Tasks

Note: In this special case only, it does not matter whether the Base isonline or offline. Since the host operating system did not establish a pathgroup to the Alias when it was misdefined, it can be safely deleted withoutrequiring that the Base device be varied offline


Disabling a CKD Functional DeviceTo disable a CKD functional device:

1. Vary the device offline to all host operating systems. Note that PAV Aliasdevices cannot be varied online or offline.

2. Disable the CKD device using the SVAA subcommand or panels named in thefollowing table.

Subcommand Panel

Disable CKD device ALTER DEVICE (page 8-20)or VARY DEVICE (page8-207): CKDENA parameter

UPDATE FUNCTIONAL DEVICE (page7-56): type N in CKD Enabled field

Disabling a SCSI Functional DeviceTo disable a SCSI functional device:


2. Disable the SCSI device using the SVAA subcommand or panels named in thefollowing table.

Subcommand Panel

Disable SCSI device ALTER DEVICE (page 8-20)or VARY DEVICE (page8-207): SCSIENA parameter

UPDATE FUNCTIONAL DEVICE (page7-57): type N in SCSI Enabled field


Configuration Tasks

Defining Additional Privileged ECAM Devices

Note: You cannot define PAV Alias or Power PPRC Bridge devices as ECAMdevices.

To define a device as a privileged ECAM device:

1. Designate the device to be an ECAM device; that is, eligible to communicaterequests to the SVA subsystem.

2. Define the device as privileged; that is, eligible to communicateCategory 1-restricted messages (which alter the subsystem configuration).

The following table identifies the topics and pages in this manual that describe thetasks involved in defining privileged ECAM devices.

Note: It is recommended that you verify that the device is assigned privilegedECAM status. To do this, use the DISPLAY DEVICE subcommand (page 8-55) or theFUNCTIONAL DEVICE SELECTION panel (page 7-36).

Subcommand Panel

Define ECAMcommunicationsdevice

SET ECAMDEVICE (page8-164)

At the command line of any SVAApanel, issue SIB SET ECAMDEVICE

subcommand

Define device asprivileged

ALTER DEVICE (page 8-20)or DEFINE DEVICE (page8-38): specifyPRIVLG(YES)

INSERT FUNCTIONAL DEVICE (page7-42), REPLICATE FUNCTIONAL DEVICE

(page 7-49), or UPDATE FUNCTIONAL

DEVICE (page 7-57):set Privileged ECAM field to Y


Configuration Tasks

Reconfiguring Subsystem Disk Array Capacity

Reconfiguring a subsystem's disk array capacity can involve one or more of thefollowing activities:

� Allocating spares

� Establishing the Test partition's disk array capacity

� Forming additional disk arrays

� Moving disk array capacity from the Test partition to the Production partition

� Removing the Test partition's disk array capacity

� Reconfiguring an existing array

Allocating SparesAllocating spares is the process of re-assigning drive modules from the MATpartition to the Spares partition. To be eligible for allocation as a spare, a drivemodule must be in the MAT partition and have a status of M.A (MAT partition,active).

To allocate one or more spares, use SVAA subcommands or panels to perform thetasks in the following table.

Subcommand Panel

Check for drivemodules with astatus of M.A

LISTCFG DRIVEMODULE (page8-75)

DISPLAY DRIVE MODULE STATUS (page7-71)

Select one or moredrive modules toallocate as spares.

ALLOCATE SPARES (page8-12)

ALLOCATE SPARES (page 7-74)


Configuration Tasks

Establishing the Test Partition's Disk Array CapacityTo establish the Test partition's initial array capacity requires forming one or morearrays for that partition. The procedure is the same as that described in FormingAdditional Disk Arrays (see below).

Note: You cannot form Test arrays on the V2X, V960, or 9500 SVA—only onsubsystems running earlier microcode. See “Functional Differences betweenSubsystems” on page 1-2 for more information.

Forming Additional Disk ArraysTo form additional arrays in either the Production or the Test partition:

1. Decide upon the size of the arrays that you want to form (5+2 or 13+2), andset the Array Size value, if necessary.

Note: You can form a 5+2 array only on the 9393 or 9500 SVA—not on theV2X or V960 SVA.

2. Determine the number of spare drives necessary to form the arrays: multiplythe array size (7 or 15) by the number of arrays to be formed, and add 1 (theminimum number of reserved spares required).

3. Ensure that there are enough drive modules in the Spares partition to form thearrays. Allocate additional spare drive modules if necessary.

4. Form the additional production or test arrays.

5. Verify the increased disk array capacity.

The disk array capacity field or parameter should show an increase, while the% Net Capacity Load shows a decrease.

The following table identifies the topics and pages in this manual that describethese tasks.

Subcommand Panel

Change Array Sizevalue (optional)

ALTER SUBSYSTEM (page8-29): ARRAYSIZE

parameter

SUBSYSTEM CONFIGURATION (page7-15)

Allocate spares ALLOCATE SPARES (page8-12): DMOD parameter

ALLOCATE SPARES (page 7-74)

Form production ortest array

FORM ARRAY (page 8-63) FORM PRODUCTION ARRAYS (page7-80) or FORM TEST ARRAYS (page7-77)

Verify disk arraycapacity

LISTCFG SUBSYSTEM (page8-78) — level 1 report

SUBSYSTEM CONFIGURATION (page7-15): check Disk Array Capacityand % Net Capacity LD fields


Configuration Tasks

Moving Disk Array Capacity from Test Partition to ProductionAll drive modules associated with the Test partition can be moved to the Productionpartition. In this process, all Test partition functional device definitions andassociated data are carried forward to the Production partition.

Note: You cannot perform the Move Test Partition operation on the V2X, V960, or9500 SVA—only on subsystems running earlier microcode. See “FunctionalDifferences between Subsystems” on page 1-2 for more information.

To move disk array capacity, use SVAA subcommands or panels to perform thetasks in the following table.

Subcommand Panel

Move all Testpartition drives toProduction partition

MOVE TESTPARTITION (page8-116)

MOVE TEST INTO PRODUCTION (page7-83)

Verify that no drivemodules appear inthe Test partition

LISTCFG DEVICE (page 8-70)T should not appear in theT/P column.A zero count shouldappear in the Test partitionfield.

FUNCTIONAL DEVICE SELECTION (page7-36):T should not appear in the PTcolumn.

Removing the Test Partition's Disk Array CapacityRemoving the Test partition's capacity means deleting data sets. Therefore, beforebeginning, you must copy to the Production partition any data sets you need tosave.

Note: If your objective is to move the Test partition's disk array capacity to theProduction partition, see “Moving Disk Array Capacity from Test Partition toProduction.”

To remove the Test partition's disk array capacity:

1. Vary all Test partition functional devices offline to all hosts.


Subcommand Panel

Disable Test partitiondevices

ALTER DEVICE (page 8-20):DIS parameter

UPDATE FUNCTIONAL DEVICE (page7-57): type N in Enabled field

Delete Test partitiondevices

DELETE DEVICE (page 8-49) DELETE FUNCTIONAL DEVICE (page7-63)

Drain all test arrays START DRAIN (page 8-198) DRAIN DRIVE MODULES (page 7-86)

Verify that Testpartition's disk arraycapacity = 0


SUBSYSTEM CONFIGURATION (page7-15): check Disk Array Capacityand % Net Capacity LD fields


Configuration Tasks

Reconfiguring an Existing ArrayOn the 9393 or 9500 SVA, there are two array-size options: 5+2 and 13+2. Tochange an array's configuration from either of these arrangements to the other, useSVAA subcommands or panels to perform the tasks in the following table.

Subcommand Panel

Drain the array to bereconfigured

START DRAIN (page 8-198) DRAIN DRIVE MODULES (page 7-86)

Ensure adequatespare drive modulesto form an array

ALLOCATE SPARES (page8-12) if necessary

ALLOCATE SPARES (page 7-74) ifnecessary

Specify the ArraySize

ALTER SUBSYSTEM (page8-29): ARRAYSIZE

parameter

SUBSYSTEM CONFIGURATION (page7-15): Default Array Size field

Form new productionor test array

FORM ARRAY (page 8-63):NUMARYS parameter

FORM PRODUCTION ARRAYS (page7-80) or FORM TEST ARRAYS (page7-77)

Verify newconfiguration


SUBSYSTEM CONFIGURATION (page7-15): Number of Spares field


Configuration Tasks

Displaying the Drive Module Configuration

You can display the status, by partition, of all drive modules in a subsystem withSVAA subcommands or panels.

The following table identifies the topics and pages in this manual that describe thistask.

Subcommand Panel

Display drive modulestatus

LISTCFG SUBSYSTEM (page8-75)

DISPLAY DRIVE MODULE STATUS (page7-71)

Starting a Drain

A drain is used to move data off one or more drive modules. All drained modulesare automatically associated with the MAT partition.

To start a drain using SVAA subcommands or panels:

Subcommand Panel

Start the drain START DRAIN (page 8-198) DRAIN DRIVE MODULE(S) (page 7-86)

Reporting on Drain Events

You can generate a report on any or all drain events initiated within the most recent60 days using the following SVAA subcommands or panels.

The following table identifies the topics and pages in this manual that describeevent reporting.

Subcommand Panel

Generating a report REPORT EVENTS (page8-148)

Sequence of panels beginning withEVENT SELECTION (page 7-89)

| Configuring V2Xf PPRC with Cascaded FICON Switches in a WWNN| Domain

| To configure the V2Xf PPRC environment with cascaded FICON switches (i.e.,| greater than one switch in series), you need to establish PPRC paths using the| SVAA PPRC ESTPATH command with World Wide Node Name syntax. Once you| have established the PPRC paths, you create PPRC volume pairs using TSO or| ICKDSF. This section provides the necessary steps to configure PPRC for this| environment.

| PPRC configuration in a WWNN domain consists of the following activities:

| � Ensure SVAA PTF L2P00CX and SVA microcode G02.03.xx.00 is installed.

| � Identify the PPRC path configuration information (World Wide Node Name,| SSID, and VCU values) for the primary and secondary storage subsystems.


Configuration Tasks

| � Identify the PPRC pairs, which will be primary and secondary volumes within| those subsystems with the same device geometry.

| � Connect the FICON interface cables from the primary storage subsystem to the| secondary storage subsystem(s) to be used for PPRC communications. Make| note of the SAID values to be input for the ESTPATH command. These values| are found in Table 8-2 on page 8-120 under the SVAA ESTPATH command.

| � Define the PPRC devices using the SVAA DEFINE DEVICE command if they| do not exist.

| � Establish paths between the primary and up to four secondary storage| subsystems for each pair of VCUs included in the configuration using the SVAA| PPRC ESTPATH command.

| � Establish the volume pairs (primary and secondary) that are to be included in| the PPRC configuration using the ICKDSF PPRCOPY ESTPAIR or TSO| CESTPAIR command.

| � Query the configuration using the SVAA PPRC Query command and verify the| appropriate paths and pairs have been established.

| � Remove established paths by using the SVAA PPRC DELPATH command.

| To establish PPRC paths and pairs:

| � Issue the SVAA PPRC ESTPATH command using SIBADMIN or SIBBATCH| with the following parameters:

| - UNIT| - World Wide Node Name (primary and secondary)| - SSID (primary and secondary)| - VCU (primary and secondary)| - SAID values

| � Establish the PPRC pair(s) using ICKDSF or TSO commands. Refer to the| associated IBM documentation for the syntax and parameters.

| � Issue the SVAA PPRC QUERY and QUERY PATHS commands using| SIBADMIN or SIBBATCH and verify the results.


Chapter 7. Using the SVAA Panels

Chapter SummaryUsing the SVAA Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Using the Command or Option Field . . . . . . . . . . . . . . . . . . . . . . . 7-2Entering SVAA Subcommands in the Command or Option Field . . . . . . . 7-2Entering Values on the Panels . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Using the Panel Commands and Function Keys . . . . . . . . . . . . . . . . 7-3

SVAA Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Session Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Setting Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Specifying Report Titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Subsystem Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Subsystem Component Selection . . . . . . . . . . . . . . . . . . . . . . . . 7-11Subsystem Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Subsystem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14SSID Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Channel Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20Configuring a Parallel Channel . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Configuring an ESCON Channel . . . . . . . . . . . . . . . . . . . . . . . . 7-27Configuring a SCSI I/O Interface . . . . . . . . . . . . . . . . . . . . . . . . 7-29Configuring a Fibre Channel Interface . . . . . . . . . . . . . . . . . . . . . 7-31Configuring a FICON Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32

Functional Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35Inserting a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Replicating a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . 7-48Initializing a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Updating a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56Deleting a Functional Device . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61

Browsing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . 7-67Drive Module Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68

Displaying Drive Module Status . . . . . . . . . . . . . . . . . . . . . . . . . 7-70Allocating Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73Forming Test Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76Forming Production Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79Moving Test Partition into Production Partition . . . . . . . . . . . . . . . . 7-82Draining Drive Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85

Displaying Event Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88Drive Module Drain Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91Media Acceptance Test Status . . . . . . . . . . . . . . . . . . . . . . . . . 7-93Media Acceptance Test Detail Status . . . . . . . . . . . . . . . . . . . . . 7-94

Specifying SnapShot Subcommands . . . . . . . . . . . . . . . . . . . . . . . 7-96Selecting a SnapShot Subcommand . . . . . . . . . . . . . . . . . . . . . . 7-96Specifying the Snap Dataset Subcommand . . . . . . . . . . . . . . . . . . 7-97Specifying the Snap Volume Subcommand . . . . . . . . . . . . . . . . . 7-101Specifying the PPRC Remote SnapShot Volume Subcommand . . . . . 7-104

November, 2006 — PN 311290512, Rev. N SVAA Panels 7-1

SVAA Panels

This chapter describes how to use SVAA panels to:

� Set session profile options� Update one or more subsystem configurations� Browse through the current configuration data� Run the drive module utilities on one or more subsystems� Display the status of a drain� Perform Snap Dataset and Snap Volume operations—if you have SnapShot

installed.

You can also accomplish these tasks with interactive subcommands or withsubcommands issued in batch programs, as explained in Chapter 8, “SVAASubcommands and Commands.”

Using the SVAA Panels

This section describes how to use the SVAA panels: how to move through a panel,make field entries, and use the SVAA panel commands.

Using the Command or Option FieldIn the command or option field, you can type:

� An SVAA panel command, such as submit (see “Using the Panel Commandsand Function Keys” on page 7-3)

� An option number on a menu.� A TSO command.� An SVAA subcommand (see below)� An ISPF command. Some useful examples are:

keys Enables you to set your own function key definitions.

panelid Causes the panel ID to appear in the upper-left corner of eachpanel during the current session.

pfshow Displays your current function key definitions at the bottom of thepanel. pfshow off turns off function key display. pfshow tailorlets you specify the number and arrangement of key definitionsdisplayed.

See the ISPF documentation for the complete list of these commands and theirexplanations.

Entering SVAA Subcommands in the Command or Option FieldYou can execute SVAA subcommands from any panel by issuing the SIBCMDcommand. You do this by typing SIBCMD (or simply SIB—the short form) in thecommand (or option) field, followed by an SVAA subcommand, and pressing Enter.Refer to Chapter 8, “SVAA Subcommands and Commands” for detaileddescriptions of the SVAA subcommands.

Note: If you type only SIB and press Enter, SVAA displays another panel thatprovides more space for entering one or more subcommands.

Examples:

SIB LISTCFG SUBSYS(SUBSYS(SVASYS) LEVEL(1))

requests a report on functional device configuration.


SVAA Panels

SIB SET CASE(UPPER)

causes all lowercase characters you enter during the session to be translated touppercase.

Entering Values on the PanelsFields with an arrow (===>) after the field name are data-entry fields. Fields with acolon (:) after the field name are display-only; you cannot enter data in these fields.

You can enter values in uppercase, lowercase, or mixed case.

You use two keys to move around the panels to make selections or to enter data:

Tab Moves the cursor to the next field in which you can enter data.

Enter Verifies that the values you have entered on the current panel are valid.Where appropriate, SVAA then displays the next panel.

MessagesSVAA displays brief messages in the upper-right corner of the panel. Thesemessages might inform you of:

� The successful completion of a task, or � Error conditions.

Issue the HELP command to display an expanded explanation.

Note: When displaying an error message, SVAA places the cursor under the fieldin which it finds the error.

Using the Panel Commands and Function KeysThe standard ISPF commands are available on the SVAA panels as well. Thecommands that are specifically defined for SVAA are listed and described inTable 7-1 on page 7-4, together with their default key assignments.

Not all SVAA panel commands work on all panels. For a list of the commands thatyou can use with the current panel, enter ? in the command field.


SVAA Panels

Table 7-1. SVAA panel commands

Command Description DefaultKey

cancel Terminates processing of items selected anddisplays the selection panel again.

F15

detail Displays detailed test information for each drivemodule.

F19

end Terminates the current operation.

� On profile panels, end saves the changes you'vemade and returns to the previous panel.

� On configuration panels, end does not save datayou have entered. If you have selectedadditional items, the next panel appears; if not,the selection panel appears.

� On a menu panel, end returns to the previousmenu.

F3

help Displays help information for the panel. When amessage appears in the upper right corner of thepanel, pressing this key displays a longer explanationof the message.

F1, F13

next Displays the panel for the next selected item. F23

part (Partition) Displays the status of all drive modules ina partition.

F18

previous Displays the panel for the previous selected item. F22

refresh Displays the values that are currently in effect. F24

return Terminates processing of all selected items andreturns to the SVAA main menu.

F4, F16

sib Provides a quick way to enter an SVAAsubcommand. (Enter a subcommand in the panelcommand field and press the sib key. “sib” isprefixed to the subcommand and the wholecommand is executed.)

F20

submit Executes the function of the panel with the data youhave entered on it.

F6


SVAA Main Menu

SVAA Main Menu

To display the SVAA main menu, enter ISPF and go through the panels to get toSVAA, as defined for your installation.

SVAA displays a copyright panel and then the Shared Virtual Array Administratormain menu, as shown in Figure 7-1.

� � SIBMM�� SHARED VIRTUAL ARRAY ADMINISTRATOR �� OPTION ===>

� SVAA PARMS - Specify user parameters1 CONFIGURATION - Configure and administer SVA subsystems2 SELECTION - Maintain device selection lists3 REPORT - Perform subsystem data collection and reporting4 SNAPSHOT - Snap data set and snap volumeX EXIT - Terminate SVAA processing

Enter END command to terminate SVAA

� �

Figure 7-1. SVAA main menu (SIBMM00)

Select option 0, 1, or 4 on the SVAA main menu to begin one of the activitiesdescribed in this chapter:

0 SVAA PARMS. Set parameters for your SVAA session. See “SessionAdministration” on page 7-6.

1 CONFIGURATION. Alter the SVA subsystem configuration, browse the currentconfiguration information, execute drive module utilities, or view the status ofasynchronous events. See “Subsystem Administration” on page 7-10.

4 SNAPSHOT. Specify SNAP DATASET and SNAP VOLUME subcommands. See“Specifying SnapShot Subcommands” on page 7-96.

Options 2 and 3 are documented in the SVAA for OS/390 Reporting manual.

Enter X or issue the end command to terminate SVAA and return to ISPF.

Procedure

Type the number of an option and press Enter.


Session Administration


Session administration consists of setting parameters for your SVAA session.

To display the SVAA SESSION ADMINISTRATION menu:

SharedVirtual ArrayAdministrator

SVAASession

Administration

ReporterOptions

SVAASessionProfile

SVAAReportTitles

C11001

1 2 3

Enter 0

MM00

PX00

PX10 PX20 PX30

The SVAA SESSION ADMINISTRATION menu appears:

� � SIBPX�� SVAA SESSION ADMINISTRATION �� OPTION ===>

1 PROFILE - Specify user profile options2 TITLES - Specify report titles3 REPORTER - Specify Reporter options

� �

Figure 7-2. SVAA Session Administration menu (SIBPX00)

Procedure

Type 1 and press Enter to display the SVAA SESSION PROFILE panel.

Type 2 and press Enter to display the SVAA REPORT TITLES panel on which youcan enter title lines for your SVAA reports (see page 7-9).

(Option 3, REPORTER, is described in the SVAA for OS/390 Reporting manual.)



Setting Profile OptionsThe following panel appears when you select option 1 on the SVAA SESSIONADMINISTRATION panel.

� � SIBPX1� �� SVAA SESSION PROFILE �� COMMAND===>

Permanent Session Option Value Value Source-------- --------- -------- --------- Case ===> MIXED ===> MIXED perm Pagesize ===> ===> 5� profile Profile ===> PROFSIBA default

Parmlib ===> SIBSTK�� default SSName ===> ===> STK1 profile

Job Card -------- ===> //SPKS$ JOB (ACCOUNT),'NAME' ===> //� ===> //� ===> //�

� �

Figure 7-3. SVAA Session Profile panel (SIBPX10)

Use this panel to change your profile options, either for the current session only(use the Session Value fields), or for the current and future sessions as well (usethe Permanent Value fields).

Note: Values you enter on this panel override the corresponding values in yourSIBADMIN profile or in the SIBSTK00 member of parmlib (see “SVAA InitializationRoutines” on page 3-2).

Column Headings

Option The name of the option to be set.

Permanent Value The option value that applies to all sessions. This column isinitially blank, although the default values are in effect for alloptions. Any allowable value you type in this columnautomatically appears in the Session Value column as well.This value applies for the rest of the current session and forall future sessions—until you enter a new value.

Session Value The option value that applies to the current session. To set adifferent value for the current session, type a new value inthis column. (After you do so and press Enter, the value inthe Source column changes to session.) The new sessionvalue does not affect the permanent value.

Source The source of the current value:

default The value is the SVAA default value (which wasset during SVAA initialization).



session The value was typed in the Session Valuecolumn or entered via the appropriate SETSUBCOMMAND during the current session.

perm The value was typed in the Permanent Valuecolumn during this session or a previous session.

profile The value was set in the profile macro that wasexecuted when you used SIBADMIN.

parmlib The value was set via the parmlib member.

Job Card The job card that is used when SVAA submits a job toOS/390.

Procedure

1. Tab to and update the following optional fields as needed:

Case Specifies whether SVAA translates values that you enter forsubcommand parameters to uppercase or leaves them inmixed case.

Enter mixed (or m) to have the case of characters interpretedexactly as you type them, or upper (or u) to have allcharacters you type interpreted as uppercase.

Pagesize Sets the number of lines per page for SVAA reports. You canenter a number from 40 to 99.

Profile Specifies the SVAA profile to be executed whenever youenter the SVAA panels in future sessions. (You cannotchange the session value for the profile.)

Parmlib Specifies the parmlib member to be used during initializationof the next SVAA session. (You cannot change the sessionvalue for the parmlib.)

SSName Specifies the OS/390 subsystem name associated with theSVAA address space. Normally, you use this option onlywhen running a test version of SVAA.

job card line Replace the default job card with your own job cardinformation. (The job name is generated by adding a $ toyour TSO userid.)

2. Issue the end command to accept the new values and return to the SVAASESSION ADMINISTRATION menu.



Specifying Report TitlesThe following panel appears when you select option 2 on the SVAA SESSIONADMINISTRATION menu.

� � SIBPX2� �� SVAA REPORT TITLES �� COMMAND ===>

SOURCE: Title1- profile Title2- profile Title3- profile

SESSION: Title1 ===> _ ===>

Title2 ===> ===>

Title3 ===> ===>

PERMANENT: Title1 ===> ===>

Title2 ===> ===>

Title3 ===> ===>

� �

Figure 7-4. SVAA Report Titles panel (SIBPX20)

Use this panel to enter up to three title lines that will appear at the top center ofeach page of your reports. The three SOURCE fields show the source of the currenttext for each title. The default is a blank line.

Procedure

1. Tab to and update the following fields as needed:

Session Title 1 to 3 These titles apply only to reports produced duringthe current session.

If you leave these lines blank, the permanent titlesare used for this session.

Permanent Title 1 to 3 These titles apply to reports for future sessions.They are also used for the current session if youdon't enter session titles on this panel.

2. Issue the end command to accept the new values and return to the SVAASESSION ADMINISTRATION menu.


Subsystem Administration

Subsystem Administration

The SUBSYSTEM ADMINISTRATION menu appears when you select option 1 on theSVAA main menu (page 7-5).

� � SIBAX�� SUBSYSTEM ADMINISTRATION �� OPTION ===>

Subsystem ===>

1 ALTER - Alter subsystem configuration2 BROWSE - Display subsystem configuration3 UTILITIES - Execute drive module utilities4 EVENTS - Report the status of asynchronous events

� �

Figure 7-5. Subsystem Administration menu (SIBAX00)

Select options on this menu to begin any of the activities described in the remainderof this chapter:

1 ALTER. Update the characteristics of one or more subsystems, channelinterfaces, or functional devices. The diagram on the following page showsthe panel flow for these tasks.

2 BROWSE. View (but not update) panels displaying the current configurationinformation. For details, see “Browsing the Current Configuration” onpage 7-67.

3 UTILITIES. Execute one of eight different drive module utilities. For details,see “Drive Module Utilities” on page 7-68.

4 EVENTS. View the status of drain events. For details, see “Displaying EventStatus” on page 7-88.

Procedure

1. Type the number of an option.

2. Tab to Subsystem and type the name of the SVA subsystem—if SVAA iscommunicating with multiple SVA subsystems and you want to work with onlyone of them. (Skip this field if you want to work with more than onesubsystem.)

3. Press Enter.


Component Selection

Subsystem Component SelectionThe following flow diagram shows all of the Alter Subsystem Configuration panels.

To display the SUBSYSTEM COMPONENT SELECTION menu, select option 1 on themain menu and then option 1 on the SUBSYSTEM ADMINISTRATION menu.

SubsystemComponentSelection

SubsystemAdministration

SubsystemSelection

SubsystemConfiguration

FunctionalDevice

Selection

DeleteFunctional

Device

InsertFunctional

Device

UpdateFunctional

Device

ReplicateFunctional

Device

1

I R S D

2 3

C11039

Enter 1

Enter 1

MM00

AX00

AX10

AX05

CA20

CA25 CA25 CA25 CA25

CA00

Enter 1, 2, or 3

Panel appears only formultiple subsystems.

Enter S to select subsystems.


ChannelConfiguration

(Parallel)


(SCSI)


(ESCON)


(Fibre)

ChannelType

Selection

ChannelSelection

CA11

CA10

CA15 CA17CA16 CA18

S

SSIDDefinitions

CA01


(FICON)

CA19


Component Selection

The SUBSYSTEM COMPONENT SELECTION menu appears when you select option 1on the SUBSYSTEM ADMINISTRATION menu.

� � SIBAX1� �� SUBSYSTEM COMPONENT SELECTION �� OPTION ===>

Subsystem ===>

1 SUBSYSTEM - Global subsystem characteristics2 CHANNEL - Channel interface characteristics3 DEVICE - Functional device characteristics

� �

Figure 7-6. Subsystem Component Selection menu (SIBAX10)

Use this panel to select one of the following subsystem components:

1 SUBSYSTEM. Alter the characteristics of one or more subsystems. For details,see “Subsystem Configuration” on page 7-14.

2 CHANNEL. Alter the characteristics of one or more channel interfaces. Fordetails, see “Channel Interface Configuration” on page 7-20.

3 DEVICE. Define (through insert or replicate), update, or delete one or morefunctional devices. For details, see “Functional Device Configuration” onpage 7-35.

Procedure


Note: If you entered a subsystem name on the previous panel (SUBSYSTEMADMINISTRATION), that name appears in the Subsystem field and you can skipStep 2.

2. Tab to the Subsystem field and type the name of the SVA subsystem—if SVAAis communicating with multiple SVA subsystems and you want to work with onlyone of them. (Skip this field if you want to work with more than onesubsystem.)

3. Press Enter.

Result: The next panel to appear depends upon whether you still need to makea subsystem selection (that is, whether you are dealing with multiple subsystems atthis point).

� Multiple subsystems. If you have issued the SET ECAMDEVICE subcommandfor at least one device on two or more SVA subsystems during the currentSVAA session and you have skipped the Subsystem field on each menu panelso far:

The SUBSYSTEM SELECTION panel appears (see “Subsystem Selection” onpage 7-13).


Subsystem Selection

� One subsystem. If you have issued the SET ECAMDEVICE subcommand toonly one SVA subsystem during the current SVAA session or you have entereda subsystem name on one of the first menu panels:

The SUBSYSTEM CONFIGURATION panel (see page 7-15), the CHANNEL TYPESELECTION panel (see page 7-21), or the FUNCTIONAL DEVICE SELECTIONpanel (see page 7-36) appears, depending upon the option you have justselected.

Subsystem SelectionThe example in Figure 7-7 lists four subsystems.

� �SIBAX�5 �� SUBSYSTEM SELECTION �� Row 1 to 4 of 4COMMAND ===> SCROLL ===> PAGE

Type S to select subsystem, U to unselect subsystem.

Enter END command to process selections or CANCEL to exit the selection list.

Subsystem Action --------- -------- SYS�� SYS�1 ICEBOX6 ICEBOX8�� Bottom of data ��

� �

Figure 7-7. Subsystem Selection panel (SIBAX05)

On this panel you select one or more subsystems.

Procedure

1. Tab to each subsystem name you want to select and type S to the left of thename. (Type U to the left of a subsystem name to cancel its selection.)

The Action field displays the status of your selections, for example:

Selected The subsystem is selected for processing.

INVALID The line command is invalid (only S and U are accepted).

2. Issue the end command.

Result: The first panel appears for the task you have selected—to alter orbrowse the current configuration of a subsystem component, execute a drivemodule utility, or display the status of events.


Subsystem Configuration


The SUBSYSTEM CONFIGURATION panel enables you to update the globalcharacteristics of a subsystem:

� the subsystem name,� the site name,� the subsystem identifiers (SSIDs) for the logical 3990s emulated, and� the default array size (13+2 or 5+2)—that is, the number of drive modules (for

user data plus redundancy data) to be used to form new arrays. On the V2Xor V960 SVA, the only array size available is 13+2.

� the status of SCSI service information messages (either enabled or disabled).� the total number of concurrent PPRC pair synchronizations (copylim).

To display the SUBSYSTEM CONFIGURATION panel:




SubsystemSelection

C11040

Enter 1

Enter 1

Enter 1

MM00

AX00

AX10

AX05

CA00




SSIDDefinitions

CA01



Example of the SUBSYSTEM CONFIGURATION panel for all subsystems except theV2Xf:

� �SIBCA�� SUBSYSTEM CONFIGURATION �� Row 1 to 2 of 2COMMAND ===> SCROLL ===> PAGE

Site Name ===> STORTEK1 Subsystem Name ===> STK Site Loc No.: 978�2

Model: V2X S/N: 31��132��11 Cluster � - Channels: 1�SSIDs: 16 Maximum: 16 Display SSIDs ===> N Cluster 1 - Channels: 1�

SCSI SIM ===> ENABLED Max. SCSI Addr: 15.15.255Tot Vcyl: 1376544 Config Vcyl: 6869784 Unconfig Vcyl: 68�676�

Cache Size: 8192 MB Capacities: Prod Test OverallNVS Size: 256 MB DA Capacity: 466.4 �.� 466.4 GBNo. of Arrays: 1 Net Load: 226.3 �.� 226.3 GBGlobal Spares: 1 % Net Load: 48.5 �.� 48.5 %Def Array Size ===> 13+2 % Coll Free Space: 5�.1 �.� 5�.1 %No. Func. Devices: 4�96 % Uncoll Free Spc: �.6 �.� �.6 %------------------------------ Installed Features -----------------------------Maintenance SnapShotPPRC PPRCSnapShotPowerPPRC FlexVolumes�� Bottom of data ��

� �

Figure 7-8. Subsystem Configuration panel for non-V2Xf subsystems (SIBCA00)



Example of the SUBSYSTEM CONFIGURATION panel for the V2Xf:

� �SIBCA�� SUBSYSTEM CONFIGURATION �� Row 1 to 2 of 2COMMAND ===> SCROLL ===> PAGE

Site Name ===> STORTEK1 Subsystem Name ===> TEST Site Loc No.: 978�2

Model: V2Xf S/N: 481��132��11 Cluster � - Channels: 4SSIDs: 16 Maximum: 16 Display SSIDs ===> N Cluster 1 - Channels: 4Copylim ===> 1Tot Vcyl: 27353�88 Config Vcyl: 2��361 Unconfig Vcyl: 27152727

Cache Size: 8192 MB Capacities: Prod Test OverallNVS Size: 256 MB DA Capacity: 1868.7 �.� 1868.7 GBNo. of Arrays: 2 Net Load: 3.1 �.� 3.1 GBGlobal Spares: 1 % Net Load: �.2 �.� �.2 %Def Array Size ===> 13+2 % Coll Free Space: 99.8 �.� 99.8 %No. Func. Devices: 4�96 % Uncoll Free Spc: �.� �.� �.� %------------------------------ Installed Features -----------------------------Maintenance SnapShotHigh Speed Data Mover PPRCFCNPPRCSnapShot PAVFlexVolumes Large Volumes�� Bottom of data ��

� �

Figure 7-9. Subsystem Configuration panel for the V2Xf (SIBCA00)

Display-only Fields

Site Loc No. A number (assigned by StorageTek) that identifies your site.

Model The model number—identifies the general characteristics ofthe subsystem.

S/N The serial number—identifies the specific subsystem.

Cluster - Channels The number of channels installed for each cluster.

SSIDs The number of subsystem identifiers (SSIDs) currently definedon the SVA subsystem. (Each logical 3990 in your entireinstallation must have a unique SSID.)

Maximum The maximum number of SSIDs that can be defined on theSVA subsystem.

Tot Vcyl The total number of virtual cylinders that can be defined onthis SVA subsystem.

Config Vcyl The total number of configured virtual cylinders that havebeen defined on this SVA subsystem.

Unconfig Vcyl The total number of unconfigured virtual cylinders that remainavailable to be defined on this SVA subsystem.

Cache Size The cache size for the subsystem (in megabytes).

NVS Size The amount of nonvolatile storage (NVS).

No. of Arrays The number of arrays currently defined in the subsystem.

Global Spares The number of drive modules to be reserved as spares whenyou form new arrays.



No. Func. Devices The total number of functional devices defined for thesubsystem.

Max. SCSI Addr The maximum allowable SCSI address for the subsystem(shown as domain.target.lun).

DA Capacity Disk array capacity: The formatted physical capacities (ingigabytes) of the Test partition arrays, Production partitionarrays, and Overall disk array capacity. (Overall excludesthe capacity of drive modules not assigned to arrays.)

Net Load The physical space (in gigabytes) that is currently occupiedby data (after compression and compaction) in the Testpartition, Production partition, and Overall.

% Net Load The percentage of physical space that is currently occupiedby data in the Test partition, Production partition, andOverall.

% Coll Free Space The percentage of array cylinder bytes (in the Test partition,Production partition, and Overall) that are collected andentirely free of user data.

% Uncoll Free Spc The percentage of functional track bytes (in the Test partition,Production partition, and Overall) that are free butunavailable (uncollected).

Installed Features A list of the optional features you have installed.

Procedure

1. Tab to and update the following fields as required:

Site Name A name you can use to identify your company,organization, or location. Enter 1 to 8 characters in theset: a to z, A to Z, 0 to 9, $, @, _, #, -, +, &, ., /,or set the name to blanks.

Subsystem Name The name of the SVA subsystem. Each SVA subsystemname must be unique. Enter 1 to 8 characters in theset: a to z, A to Z, 0 to 9, $, @, _, #, -, +, &, ., /

Display SSIDs Enter Y (and press Enter) to display the SSIDDEFINITIONS panel (see page 7-18). The default is N.

Def Array Size The default array size: the number of drive modules (foruser data + redundancy data) to be used to form eachnew array.

Enter 5+2 or 13+2

Note: You cannot change an array's size once it isformed. For a different array size, first drain the arrayand then form a new array of the desired size.

SCSI SIM Status Specifies whether SCSI SIMs (service informationmessages) are to be displayed (enabled) or not(disabled).

Enter ENABLED or DISABLED


SSID Definition

Copylim Specifies the total number of concurrent PPRCsynchronizations.

Enter a decimal value between � and 32.

2. Issue the submit command to update the configuration. The panel displays thenew values.

Panel Command Options

To execute an SVAA panel command, type the command in the command field (andpress Enter) or press the corresponding function key.

end Displays the next panel (if you selected more than one subsystem), orreturns to the SUBSYSTEM COMPONENT SELECTION menu (if youselected no other subsystems).

cancel Stops the processing of all selected subsystems and returns to theprevious panel (SUBSYSTEM SELECTION or SUBSYSTEM COMPONENTSELECTION).

SSID DefinitionIf you entered Y (and pressed Enter) in the Display SSIDs field on the SUBSYSTEMCONFIGURATION panel, SVAA displays the SSID DEFINITIONS panel. This panelenables you to view, add, or change the current definitions of SSIDs—thesubsystem identifiers for the virtual control units (the 3990 controllers emulatedwithin the SVA subsystem).

� �SIBCA�1 �� SSID DEFINITIONS �� Row 1 to 4 of 4COMMAND ===> SCROLL ===> PAGE

Subsystem Name: STK

Defined: 8 Maximum: 16

SSIDBASE ===>

VCU SSID VCU SSID VCU SSID VCU SSID � AC�� 1 AD�� 2 AEOO 3 AF�� 4 B4�� 5 B5�� 6 B6OO 7 B7��

8 9 1� 1112 13 14 15

�� Bottom of data ��

� �

Figure 7-10. SSID Definition panel (SIBCA01)

In this example, only 8 of a possible 16 SSIDs have been defined. (This exampleapplies to the V2X SVA; earlier SVA subsystems are limited to 4 SSIDs.)


SSID Definition

Notes:

1. Each VCU (logical 3990) in your entire installation must have a unique SSID.

2. Once you define an SSID as non-zeroes, you cannot redefine it as zeroes.

3. You cannot redefine an SSID on a subsystem on which PPRC is enabled. Youmust first have your hardware support representative disable PPRC capabilityfor the subsystem. Then, after you have redefined the SSID, PPRC can bere-enabled for the subsystem.

You can define SSIDs in two different ways—by using the SSIDBASE field, or byspecifying SSIDs for each VCU individually.

Procedure for the SSIDBASE field

1. Tab to the SSIDBASE field and enter a “base” SSID (a 4-digit hexadecimal value)for VCU 0. SVAA assigns SSIDs to all other VCUs in ascending hexadecimalsequence, beginning with the base SSID.

Note: The SSID value you specify must not allow the last SSID to exceedFFFF. For example, on a subsystem that supports 16 SSIDs, FFF0 is thehighest valid entry for SSIDBASE.

2. Issue the submit command to update the configuration. The panel displays thenew SSID values. For example, entering an SSIDBASE value of �7�� results inthis display:

� �SIBCA�1 �� SSID DEFINITIONS �� Row 1 to 4 of 4COMMAND ===> SCROLL ===> PAGE

Subsystem Name: STK

Defined: 16 Maximum: 16

SSIDBASE ===> �7��

VCU SSID VCU SSID VCU SSID VCU SSID � �7�� 1 �7�1 2 �7O2 3 �7�3 4 �7�4 5 �7�5 6 �7�6 7 �7�7 8 �7�8 9 �7�9 1� �7�A 11 �7�B 12 �7�C 13 �7�D 14 �7�E 15 �7�F�� Bottom of data ��

� �Figure 7-11. SSID Definition panel, using SSIDBASE (SIBCA01)

3. Issue the end command to return to the SUBSYSTEM CONFIGURATION panel.

Procedure for assigning individual SSIDs

1. Tab to and enter or update the SSID for one more VCUs, using a 4-digithexadecimal value ranging from 0001 to FFFF.

2. Issue the submit command to update the configuration. The panel displays thenew SSID values.

3. Issue the end command to return to the SUBSYSTEM CONFIGURATION panel.


Channel Interface Configuration


SVAA enables you to alter interface characteristics for parallel, ESCON, FICON,fibre, and SCSI channels:

� For a parallel (bus and tag cables) channel, you can change the name of thechannel interface, the channel speed, the base address and range ofaddresses trapped by the channel interface, and the base functional device ID.

� For an ESCON, FICON, SCSI, or fibre channel, you can change only the nameof the channel interface.

Note: You cannot alter the characteristics of a channel interface that is used by aPPRC pair.

First, you use the CHANNEL TYPE SELECTION panel to select the type of channelinterface to be altered. To display the CHANNEL TYPE SELECTION panel:



(Parallel)


(SCSI)


(ESCON)


(Fibre)

ChannelType

Selection

ChannelSelection


SubsystemSelection

C11004

Enter 1

MM00

AX00

AX10

AX05

CA11

CA10

CA15 CA17CA16 CA18

Enter 1

Enter 2



S



(FICON)

CA19



Here is an example of the CHANNEL TYPE SELECTION panel.

� �SIBCA11 �� CHANNEL TYPE SELECTION ��OPTION ===>

Subsystem Name: STK

--Type-- Speed Total Enabled1 �� ALL �� 2� 2�

2 PARALLEL 3 ESCON 2�.� 1� 1� 4 SCSI 4�.� 5 FIBRE 1��.� 6 6 6 FICON 2��.� 4 4

� �

Figure 7-12. Channel Type Selection panel (SIBCA11)

Use this panel to select the type of channel you want to alter. Enter 1 to display aCHANNEL SELECTION panel that lists all channels on the subsystem. Enter a digitfrom 2 to 5 to list channels of only one type.

Here are examples of the six forms of the CHANNEL SELECTION panel. The firstexample is for all channels (except FICON) followed by examples for parallel,ESCON, SCSI, fibre, and finally FICON.

� �SIBCA1� �� CHANNEL SELECTION �� Row 1 to 12 of 12COMMAND===> SCROLL ===> PAGE

Subsystem Name: STK Type: ALL

Interface--Name-- Clust Chan Ena --Type-- Speed

___ ICE�� A Y ESCON 2�.�___ ICE�� C Y ESCON 2�.�___ � E Y FIBRE 1��.�___ � G Y FIBRE 1��.�___ � I Y SCSI 4�.�___ CHAN-�.K � K Y SCSI 4�.�___ 1 A Y ESCON 2�.�___ 1 C Y ESCON 2�.�___ FIBR_1.E 1 E Y FIBRE 1��.�___ 1 G Y FIBRE 1��.�___ TEST-1.I 1 I Y SCSI 4�.�___ TEST-1.K 1 K Y SCSI 4�.�� Bottom of data ��

� �

Figure 7-13. Channel Selection panel—All channels except FICON (SIBCA10)




Subsystem Name: STK Type: PARALLEL

Interface ----Address------Name-- Clust Chan Ena Base Range BFDID

___ INT_�_A � A Y �� 256 ��___ NOTINSTL � B N �� 256 ��___ NOTINSTL � C N �� 256 ��___ NOTINSTL � D N �� 256 ��___ LSTC8VM 1 A Y �� 256 ��___ NOTINSTL 1 B N �� 256 ��___ NOTINSTL 1 C N �� 256 ��___ NOTINSTL 1 D N �� 256 �� Bottom of data ��

� �

Figure 7-14. Channel Selection panel—Parallel channels (SIBCA10)


Subsystem Name: STK Type: ESCON

Interface ----Address------Name-- Clust Chan Ena Base Range FDID

___ ICE�� A Y �� 4�96 ��___ ICE�� B Y �� 4�96 ��___ � C Y �� 4�96 ��___ � D Y �� 4�96 ��___ 1 A Y �� 4�96 ��___ 1 B Y �� 4�96 ��___ 1 C Y �� 4�96 ��___ 1 D Y �� 4�96 �� Bottom of data ��

� �

Figure 7-15. Channel Selection panel—ESCON channels (SIBCA10)




Subsystem Name: STK Type: SCSI

Interface -DTL---Name-- Clust Chan Ena Count Domain SCSI Identifier

___ � I Y � �� 534E5241��12___ CHAN-�.K � K Y 7 ��1 ��7 47534241��81___ TEST-1.I 1 I Y �___ TEST-1.K 1 K Y � �� 4 FFFFFFFFFFFFFFFF�� Bottom of data ��

� �

Figure 7-16. Channel Selection panel—SCSI channels (SIBCA10)


Subsystem Name: STK Type: FIBRE

Interface ---World Wide-----Name-- Clust Chan Ena ---Node Name---- ---Port Name---- Address-

___ � E Y 5��1�4F��4118A2 5��1�4F��4118AC ��3___ � G Y 5��1�4F��4118A3 5��1�4F��4118AC ��3___ FIBR_1.E 1 E Y 5��1�4F��411885 5��1�4F��41188� ��3___ 1 G Y 5��1�4F��411886 5��1�4F��41188� ��3�� Bottom of data ��

� �

Figure 7-17. Channel Selection panel—Fibre channels (SIBCA10)




Subsystem Name: STKFI Type: FICON

Interface ----Address---- ---World Wide--- --Name-- Clust Chan Ena Base Range FDID ---Node Name---- ---Port Name----_ � A Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F14C_ � B Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F14D_ � C Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F12A_ � D Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F12B_ 1 A Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F13C_ 1 B Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F13D_ 1 C Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F144_ 1 D Y �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F145�� Bottom of data ��

� �

Figure 7-18. Channel Selection panel—FICON channels (SIBCA10)

The six panel examples above display the current characteristics of the channelinterfaces and let you select one or more channel interfaces to be altered.

Procedure (for all Channel Selection panels)

1. Tab to the desired channel and type S at the left end of the line. (Repeat forother channels, if necessary.)

Issue the forward command to display more channels, if more exist.

You can select a sequence of two or more channels by typing Sn (or Snn) atthe first channel in the sequence. (n or nn represents the number of channelsto be selected.)

2. Press Enter.

Result: The CHANNEL CONFIGURATION panel appears.

For parallel channel configuration, see page 7-25.

For ESCON channel configuration, see page 7-27.

For SCSI channel configuration, see page 7-29.

For fibre channel configuration, see page 7-31.

For FICON channel configuration, see page 7-32.



cancel Terminates channel configuration for all selected subsystems andreturns to the previous panel (SUBSYSTEM SELECTION or SUBSYSTEMCOMPONENT SELECTION).



Configuring a Parallel ChannelTo alter any parallel channel characteristics you must first vary the channel offlineto all hosts and disable the channel interface (see Procedure).

Example of the CHANNEL CONFIGURATION panel for a parallel channel:

� �SIBCA15 �� CHANNEL CONFIGURATION �� Row 1 to 1 of 1COMMAND===>

Subsystem Name: STK

-- Channel Interface -- Cluster Channel � A

Enabled ===> Y

Name ===> INT_�_A Channel Speed ===> 4.5 Channel Type: PARALLEL

Base Address ===> ��Address Range ===> 256

Base Functional Device ID ===> ��

SSIDs Spanned: VCU SSID VCU SSID VCU SSID VCU SSID � AC�� 1 AD�� 2 AEOO 3 AF�� Bottom of data ��

� �

Figure 7-19. Channel Configuration panel—Parallel channel (SIBCA15)

Display-only Fields

Subsystem Name The name of the SVA subsystem.

Cluster The cluster (0 or 1) to which the channel interfaces.

Channel The channel interface to which the channel isconnected—within the specified cluster. Channel interfacesare designated A through P.

Up to 32 channels can exist—16 per cluster.

Channel Type The type of channel interface (PARALLEL in this case).

SSIDs Spanned The subsystem identifiers, listed by VCU, associated with thecurrent address range and BFDID for this channel.

Procedure

1. Vary the channel offline to all hosts.

2. Type N in the Enabled field to disable the channel interface.

3. Tab to and update the following fields as needed:

Name Optional. The name of the channel interface.Enter 1 to 8 characters in the set:a to z, A to Z, 0 to 9, $, @, _, #, -, +, &, ., /, orset the name to blanks.



Channel Speed The channel's data transfer rate—the speed (inmegabytes per second) at which data travels betweenthe host and the SVA controller.Valid speeds for a parallel channel: 3.0 and 4.5

Base Address The starting base address (hexadecimal) that thischannel interface can trap. Refer to Table 7-2 for validbase addresses for a given address range.

Address Range The number of addresses (decimal) to be trapped by thechannel interface. Refer to Table 7-2 for valid addressranges.

Base Functional Device IDThe BFDID (hexadecimal) for the channel interface.Refer to Table 7-2 for valid BFDIDs for a given addressrange.

4. Issue the submit command.

Result: The channel interface characteristics are updated, and the paneldisplays the updated fields. The SSIDs listed in the SSIDs Spanned fieldreflect the information you enter.

5. Type Y in the Enabled field and issue the submit command.

6. Vary the channel online to all hosts.



next Displays the next CHANNEL CONFIGURATION panel—if you selectedmultiple channels.

previous Displays the previous CHANNEL CONFIGURATION panel—unless the firstchannel you selected is displayed.

end Cancels the entries you have made and displays the next CHANNELCONFIGURATION panel or, if this is the last channel selected, returns tothe CHANNEL SELECTION panel.

cancel Cancels the entries you have made, terminates all channel configuration,and returns to the CHANNEL SELECTION panel.

Table 7-2. Valid configuration entries for a parallel channel

Address Range(decimal)

Base Address and BFDID values (hexadecimal)

8 00 08 10 18 20 28 30 38 40 48 50 58 60 68 70 78 80 88 9098 A0 A8 B0 B8 C0 C8 D0 D8 E0 E8 F0 F8

16 00 10 20 30 40 50 60 70 80 90 A0 B0 C0 D0 E0 F0

32 00 20 40 60 80 A0 C0 E0

64 00 40 80 C0

128 00 80

256 00



Configuring an ESCON ChannelFor an ESCON channel, the only characteristic you can change is the channelinterface name.

Example of the CHANNEL CONFIGURATION panel for an ESCON channel:


Subsystem Name: STK


Enabled Y

Name ===> �.A Channel Speed: 2�.� Channel Type: ESCON

Base Address: ��Address Range: 4�96

Base Functional Device ID: ��

SSIDs Spanned: VCU SSID VCU SSID VCU SSID VCU SSID � AC�� 1 AD�� 2 AEOO 3 AF�� 4 B4�� 5 B5�� 6 B6OO 7 B7�� 8 B8�� 9 B9�� 1� BA�� 11 BB�� 12 BC�� 13 BD�� 14 BE�� 15 BF��

� �

Figure 7-20. Channel Configuration panel—ESCON channel (SIBCA16)

Display-only Fields





Enabled The current channel status (Y=Enabled, N=Disabled)

Channel Speed The channel's data transfer rate—the speed (in megabytesper second) at which data travels between the host and theSVA controller.

Channel Type The type of channel interface (ESCON in this case).

Base Address The starting base address (hexadecimal) that this channelinterface can trap.

Address Range The number of addresses (decimal) to be trapped by thechannel interface.

Base Functional Device IDThe BFDID (hexadecimal) for the channel interface.



SSIDs Spanned The subsystem identifiers, listed by VCU, associated with thecurrent address range and BFDID for this channel. (You candefine 16 SSIDs on the V2X SVA, but only 4 on earlier SVAs.)

Procedure

1. Tab to and update the following field:

Name The name of the channel interface. Enter 1 to 8characters in the set: a to z, A to Z, 0 to 9, $, @, _,#, -, +, &, ., /, or set the name to blanks.


Result: The channel interface name is updated and the panel displays the newname.









Configuring a SCSI I/O InterfaceFor a SCSI I/O interface, the only characteristic you can change is the channelinterface name.

Example of the CHANNEL CONFIGURATION panel for a SCSI I/O interface:

� �SIBCA17 �� CHANNEL CONFIGURATION ��COMMAND===>

Subsystem Name: STK


Enabled Y

Name ===> INT_�_A Channel Speed: 4�.� Channel Type: SCSI

DTL Count: 7SCSI Domain: ��1 ��7

SCSI Identifier: 47534241��81

Domains Supported: 16 Targets/Domain: 15 LUNs/Target: 8

� �

Figure 7-21. Channel Configuration panel—SCSI I/O interface (SIBCA17)

Display-only Fields







Channel Type The type of channel interface (SCSI in this case).

DTL Count The number of domain-target-LUNs (DTLs) that have beenidentified for this channel.

SCSI Domain The identifier(s) of the SCSI domain(s) for this channel.

SCSI Identifier The SCSI identifier for this channel.

Domains supported The maximum number of domains supported for this type ofinterface.

Targets/Domain The maximum number of targets per domain supported forthis type of interface.



LUNs/Target The maximum number of LUNs per target supported for thistype of interface.

Procedure













Configuring a Fibre Channel InterfaceFor a fibre channel interface, the only characteristic you can change is the channelinterface name.

Example of the CHANNEL CONFIGURATION panel for a fibre channel interface:

� �SIBCA18 �� CHANNEL CONFIGURATION ��COMMAND===>

Subsystem Name: STK

-- Channel Interface -- Cluster Channel 1 E

Enabled Y

Name ===> FIBR_1.E Channel Speed: 1��.� Channel Type: FIBRE

World Wide Node Name: 5��1�4F��411885SCSI Domain: ��5 Port Name: 5��1�4F��41188�

Address: ��3

Domains Supported: 16 Targets/Domain: 1 LUNs/Target: 256

� �

Figure 7-22. Channel Configuration panel—Fibre channel interface (SIBCA18)

Display-only Fields







Channel Type The type of channel interface (FIBRE in this case).

World Wide Node NameThe unique name for this fibre channel node.

SCSI Domain The identifier(s) of the SCSI domain(s) for this channel.

Port Name The fibre channel port name.

Address The fibre channel loop ID.

Domains supported The maximum number of domains supported for this type ofinterface.



Targets/Domain The maximum number of targets per domain supported forthis type of interface.

LUNs/Target The maximum number of LUNs per target supported for thistype of interface.

Procedure











Configuring a FICON ChannelFor a FICON channel, the only characteristic you can change is the channelinterface name.

Example of the CHANNEL CONFIGURATION panel for a FICON channel:




Subsystem Name: STK


Enabled Y

Name ===> �.A Channel Speed: 1��.� Channel Type: FICON

World Wide Node Name: 5��1�4F��6FDDD�Port Name: 5��1�4F��45F14C

Base Address: �� Address Range: 4�96 Base Functional Device ID: ��

SSIDs Spanned: VCU SSID VCU SSID VCU SSID VCU SSID � AC�� 1 AD�� 2 AEOO 3 AF�� 4 B4�� 5 B5�� 6 B6OO 7 B7�� 8 B8�� 9 B9�� 1� BA�� 11 BB�� 12 BC�� 13 BD�� 14 BE�� 15 BF��

� �

Figure 7-23. Channel Configuration panel—FICON channel (SIBCA19)

Display-only Fields







Channel Type The type of channel interface (FICON in this case).

Base Address The starting base address (hexadecimal) that this channelinterface can trap.

Address Range The number of addresses (decimal) to be trapped by thechannel interface.

Base Functional Device IDThe BFDID (hexadecimal) for the channel interface.

SSIDs Spanned The subsystem identifiers, listed by VCU, associated with thecurrent address range and BFDID for this channel. (You candefine 16 SSIDs on the V2X SVA, but only 4 on earlier SVAs.)



Procedure












Functional Device Configuration


The functional device configuration panels enable you to define additional functionaldevices (including privileged ECAM devices), update the definition and/or status offunctional devices, and delete functional devices.

You can define a maximum of 4096 functional devices on each V2X SVAsubsystem. The number is less than 4096 if you define any 3390-9 devices. If youdefine all devices as 3390-9s, the maximum number is only 1365 devices persubsystem.

Note: For the maximum number of FDIDs on subsystems earlier than the V2X, see“Functional Differences between Subsystems” on page 1-2.

The configuration process begins with the FUNCTIONAL DEVICE SELECTION panel.The entries you make on this panel lead to either an Insert, Replicate, Initialize,Update, or Delete panel.

To display the FUNCTIONAL DEVICE SELECTION panel:

SubsystemComponent

Selection

FunctionalDevice

Selection


SubsystemSelection

C11005

Enter 1

MM00

AX00

AX10

AX05

CA20

Enter 1

Enter 3






Examples of the FUNCTIONAL DEVICE SELECTION panels:

� �SIBCA2� �� FUNCTIONAL DEVICE SELECTION �� Row 1 to 14 of 1,�21COMMAND===> SCROLL ===> PAGE

Subsystem Name: TESTV2X Find FDID===>Fast Path Replicate ===> NO

Tot Vcyl: 27353�88 Config Vcyl: 1676�� Unconfig Vcyl: 27185488

Device -------Host--------- CKD SCSI SVAA --Functional--FDID P/T -Type- SSID Volser Unit -Status- R/W R/W Comm -Cyls Capacity

____ �� P 339�3 C��1 BH�� C�� MOUNTED Y N N 3339 2838.�____ �1 P 339�3 Y N N 3339 2838.�____ �2 P 339�3 C��1 BH��2 C�� MOUNTED Y N Y 3339 2838.�____ �3 P 339�3 Y N N 3339 2838.�____ �4 P 339�3 Y N N 42 35.7____ �5 P 339�3 Y N N 3339 2838.�____ �6 P 339�3 Y N N 3339 2838.�____ �7 P 339�3 Y N N 3339 2838.�____ �8 P SCSIB Y N N 1��17 3691.9____ �9 P SCSIB Y N N 1��17 3691.9____ �A P SCSIB Y N N 1��17 3691.9____ �B P SCSIB Y N N 1��17 3691.9____ �C P SCSIB Y N N 1��17 3691.9____ �D P SCSIB Y N N 1��17 3691.9

� �

Figure 7-24. Functional Device Selection panel for non-V2Xf subsystems (SIBCA20)

� �SIBCA2� �� FUNCTIONAL DEVICE SELECTION �� Row 76 of 93COMMAND===> SCROLL ===> CSR

Subsystem Name: PRODV2XF Find FDID===>Fast Path Replicate ===> NO

Tot Vcyl: 27353�88 Config Vcyl: 1676�� Unconfig Vcyl: 27185488

Device -------Host--------- CKD SCSI SVAA --Functional--FDID B/A -Type- SSID Volser Unit -Status- R/W R/W Comm -Cyls Capacity

____ 7�� B 339�3 77�� SW77�� 77�� MOUNTED Y N N 3339 2838.�____ 7�1 B 339�3 77�� Y N N 3339 2838.�____ 7�2 B 339�3 77�� Y N N 3339 2838.�____ 7EF B 339�3 77�� Y N N 3339 2838.�____ 7F� A 339�3 77�� Y N N � �.�____ 7FD A 339�3 77�� Y N N � �.�____ 7FE A 339�3 77�� Y N N � �.�____ 7FF A 339�3 77�� Y N N � �.�____ 8�� B 339�9 78�� Y N N 3276� 27844.7____ F11 B 339�3 7F�� Y N N 3339 2838.�____ F12 B 339�3 7F�� Y N N 3339 2838.�____ F13 B 339�3 7F�� Y N N 3339 2838.�____ F14 B 339�3 7F�� Y N N 3339 2838.�____ F15 B 339�3 7F�� Y N N 3339 2838.�____ F16 B 339�3 7F�� Y N N 3339 2838.�____ F17 B 339�3 7F�� Y N N 3339 2838.�

� �

Figure 7-25. Functional Device Selection panel for V2Xf subsystems (SIBCA20)

On this panel you can:

� Insert additional functional device definitions� Replicate lines for the purpose defining new functional devices



� Select SCSI devices to be initialized with volsers and host device numbers (onlyon non-V2Xf subsystems)

� Select functional device definitions to be updated� Delete functional device definitions

In addition:

� Fast Path Replicate lets you generate new definition lines and then updatethem—bypassing the REPLICATE FUNCTIONAL DEVICE panel.

� The sort command lets you reorder lines on the panel in the sequence that ismost useful to you.

The data in the columns on this panel reflect the current functional devicecharacteristics and are for display purposes only.

Column Headings

Tot Vcyl The total number of virtual cylinders that can be defined on thisSVA subsystem.

Config Vcyl The total number of configured virtual cylinders that have beendefined on this SVA subsystem.

Unconfig Vcyl The total number of unconfigured virtual cylinders that remainavailable to be defined on this SVA subsystem.

FDID The hexadecimal identifier of the functional device (0-3FF).

P/T The partition with which the device is associated (P=Production,T=Test). Appears only on non-V2Xf subsystems.

B/A The PAV type of the device (B=Base, A=Alias). Appears on V2Xfsubsystems only.

Device Type The type of DASD device the functional device emulates.

SSID The subsystem identifier for the emulated 3990 controller withwhich the functional device is associated.

Volser The volume serial number for the device.

Unit The host device number.

Status The host device status: ONLINE, OFFLINE, or MOUNTED.

CKD R/W Indicates whether the CKD functional device is write-protected.

SCSI R/W Indicates whether the SCSI functional device is write-protected.

SVAA Comm (SVAA Communications) Y in this field indicates the device isdesignated an ECAM device; that is, it is used to communicaterequests to the SVA subsystem.

Cyls The number of cylinders for this functional device. (Set to zero forPAV Alias devices.)

Capacity The functional capacity, in megabytes, of this type of functionaldevice (the device type being emulated). (Set to zero for PAVAlias devices.)



Using Line Commands

On some SVAA panels that display tables, you can enter commands called linecommands to the left of any line (row) of data. On the FUNCTIONAL DEVICESELECTION panel you can use the following line commands:

Innn Insert (add) one or more functional device definitionsRnnn Replicate the characteristics of a functional deviceNnnn Select one or more SCSI devices to be initialized with a volser and host

device numberSnnn Select one or more functional device definitions to be updatedDnnn Delete one or more functional device definitions

nnn, which is optional, ranges from 1 to 999 and indicates the number ofconsecutive definitions to be inserted, replicated, initialized, updated, or deleted(default is 1). The total number of device definitions cannot exceed 4096 (1024 onsubsystems earlier than the V2X). This number is lower if any 3390-9 devices aredefined.

Using the Sort Command

You can control the order in which functional devices appear on this panel byentering a sort command in the command field. You can sort the functional devicesin either ascending order (the sorta command) or descending order (the sortdcommand) by any one of the following parameters (column headings):

fdid, volser, unit, ba, pt, ssid, devtype, cyls, bytes

You can use either uppercase or lowercase.

Examples:

Type sorta fdid and press Enter to display the functional devices in ascendingorder by FDID.

Type SORTD UNIT and press Enter to display the functional devices indescending order by host device number.

Using Fast Path Replicate

Fast Path Replicate enables you to generate additional functional device definitionsbased upon an existing definition.

To add device definitions with Fast Path Replicate:

1. Type YES in the Fast Path Replicate field (near the top of the panel).

2. Tab to a functional device definition line to be replicated and enter Rnnn at theleft end of the line. nnn (optional) represents the number of times to replicatethe definition (maximum of 999). The default value for nnn is 1.

The total number of device definitions cannot exceed 4096 (1024 onsubsystems earlier than V2X). (Fewer devices can be defined if any 3390-9devices are included.) If you specify an nnn value that is greater than thenumber of undefined devices, SVAA generates as many definitions as possible.



For example, to define three functional devices with the characteristics ofENGV12:

� �Device -------Host--------- CKD SCSI SVAA --Functional--

FDID P/T -Type- SSID Volser Unit -Status- R/W R/W Comm -Cyls CapacityR3__ 1A P 339�1 C��1 ENGV12 C�� MOUNTED Y N N 1113 946.�

� �

Note: You can enter Rnnn on additional lines for more replications beforeproceeding to Step 3.

If you replicate a PAV Alias device, the PAVBASE value (the Base device towhich the Alias is related) is also replicated. This is a convenient way ofdefining multiple additional PAV Aliases to an existing Base device.


The panel displays the added (replicated) functional device definition lines.The added lines are identical except for the unit numbers; SVAA assigns thenext-available unit numbers automatically.

� �Device -------Host--------- CKD SCSI SVAA --Functional--

FDID P/T -Type- SSID Volser Unit -Status- R/W R/W Comm -Cyls Capacity____ 1A P 339�1 C��1 ENGV12 C�� MOUNTED Y N N 1113 946.�____ 1B P 339�1 C��1 C��1 MOUNTED Y N N 1113 946.�____ 1C P 339�1 C��1 C��2 MOUNTED Y N N 1113 946.�____ 1D P 339�1 C��1 C��3 MOUNTED Y N N 1113 946.�

� �

To replicate another functional device, repeat steps 1 to 3.

To change the characteristics of the added functional devices, tab to the first newdevice definition and, in the space at the left, type Snnn (where nnn is the number ofconsecutive definitions you want to update). When you press Enter, the UPDATEFUNCTIONAL DEVICE panel appears with the device characteristics of the first lineyou selected (see page 7-57).

Technique for Quick PAV Setup of a VCU

To quickly setup an entire VCU of Base and Alias devices, you might want to usethe following technique, which assumes that the VCU does not contain anypreviously defined devices:

1. Define one Base device using the lowest FDID in the VCU (e.g., 000 100,200...)

2. Fast Path Replicate the Base device to create as many Base devices as areneeded

3. Define one Alias device using the lowest unused FDID in the VCU and relate itto any Base device in the VCU

4. Fast Path Replicate the Alias device to fill out the remainder of the VCU withAlias devices

5. In a Static PAV environment, use the ISPF panels or the ALTER DEVICEcommand to reassign the Alias to Base relationships as desired


Insert Functional Device

This technique is especially useful in a Dynamic PAV environment since theWorkLoad Manager (WLM) will adjust these initial PAV relationships as needed; thelast step is therefore not required in a Dynamic PAV environment.

Example:

VCU 4 is completely undefined. You want to setup the VCU with 64 Basedevices and 192 Aliases. You first define FDID 400 as a Base, then use FastPath Replicate and a value of R63 on the line command to create the other 63Base devices. You next define FDID 440 as an Alias device that is related toFDID 400, then use Fast Path Replicate and a value of R191 on the linecommand to create the other 191 Alias devices. If a Static PAV environment isin effect, you reassign the Alias to Base relationships as desired using the ISPFpanels or the ALTER DEVICE command, or just let WLM reassign Aliases asneeded if a Dynamic PAV environment is in effect.

Procedure for Functional Device Selection

Type line commands at the left end of as many lines as you wish and press Enter.The next panel to appear is determined by the line commands you entered:

I Displays the INSERT FUNCTIONAL DEVICE panel (see 7-40).

R Displays the REPLICATE FUNCTIONAL DEVICE panel (see 7-48).

N Displays the INITIALIZE FUNCTIONAL DEVICE panel (see 7-54).

S Displays the UPDATE FUNCTIONAL DEVICE panel (see 7-56).

D Displays the DELETE FUNCTIONAL DEVICE panel (see 7-61).

Requests are processed in the sequence in which the devices appear on theFUNCTIONAL DEVICE SELECTION panel.



cancel Cancels the entries you have made, terminates functional deviceconfiguration, and returns to the previous panel (SUBSYSTEMSELECTION or SUBSYSTEM COMPONENT SELECTION).

Inserting a Functional DeviceThe INSERT FUNCTIONAL DEVICE panel appears when you enter the Insert (I)command on one or more lines on the FUNCTIONAL DEVICE SELECTION panel.

To display the INSERT FUNCTIONAL DEVICE panel:



SubsystemComponent

Selection

InsertFunctional

Device

FunctionalDevice

Selection


SubsystemSelection

C11006

Enter 1

MM00

AX00

AX10

AX05

CA20

CA25

Enter 1

Enter 3

Enter I






Examples of the INSERT FUNCTIONAL DEVICE panel:

� �SIBCA25 �� INSERT FUNCTIONAL DEVICE ��COMMAND===>

Subsystem Name: TESTV2X

Volume ID ===> ______ Operating System: MVS Subsystem ID: Unit Address ===> ____ Online: Mounted: SVAA Communication: Device Type ===> ______ Domain Target -LUN- ___ _____ _____

Functional Device ID (FDID) ===> ____ Name ===> ________ Partition (T=Test/P=Prod.) : P

------------- Capacity -------------- --- Device Status (Y=Yes/N=No) ---Functional --Phys. Used(MB)-- Y CKD Enabled N SCSI Enabled

Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary

� �.� Y DASD Fast Write N SecondaryN Privileged ECAM N Data Bridge

N Status BridgeN Request Dev Init

� �

Figure 7-26. Insert Functional Device panel for non-V2Xf subsytems (SIBCA25)



Volume ID ===> ______ Operating System: MVS Subsystem ID: Unit Address ===> ____ Online: Mounted: SVAA Communication: Device Type ===> ______ Domain Target -LUN- ___ _____ _____

Functional Device ID (FDID) ===> ____ Name ===> ________ Partition (T=Test/P=Prod.) : P


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary �____ �.� Y DASD Fast Write N Secondary

N Privileged ECAM N Data BridgeN Status Bridge

N Request Dev Init

� �

Figure 7-27. V2X and V2X2 subsystems with FlexVolume support (SIBCA25)




Subsystem Name: PRODV2XF

Volume ID ===> ______ Operating System: MVS Subsystem ID: Unit Address ===> ____ Online: Mounted: SVAA Communication: Device Type ===> ______

Functional Device ID (FDID) ===> ____ Name ===> ________ PAV Base Device ID (PAVBASE) ===> ____


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary �____ �.� Y DASD Fast Write N Secondary


� �

Figure 7-28. Insert Functional Device panel for V2Xf subsystems (SIBCA25)

These examples show how the fields are initialized. All fields are either blank or setto defaults.

Display-only Fields

Subsystem Name The name assigned to the SVA subsystem.

Operating System The host operating system under which SVAA is running.

Subsystem ID The subsystem identifier (SSID) for the emulated 3990controller with which the functional device is associated.

Online Indicates whether the functional volume has been variedonline to the host operating system.

Mounted Indicates whether the functional device is mounted to thehost operating system.

SVAA Communication YES in this field indicates the device has been designatedan ECAM device (with the SET ECAMDEVICEsubcommand); that is, it is used to communicaterequests to the SVA subsystem.

Partition The partition with which the device is associated.Appears only on non-V2Xf subsystems

Cyls The number of cylinders for this functional device. (Setto zero for PAV Alias devices.). This is a display-onlyfield on V960 and earlier subsystems.

Functional (MB) The device's functional capacity (in megabytes). (Set tozero for PAV Alias devices.)

Phys. Used(MB) Shared The amount of physical space (in megabytes) that isshared among functional devices as a result of aSnapShot command. (N/A indicates that SnapShotmicrocode is not installed on this subsystem.)



Phys. Used(MB) Total The physical space on the device (in megabytes) that isoccupied by data after compression and compaction.

Primary Indicates if the device is a PPRC Primary.

Secondary Indicates if the device is a PPRC Secondary.

Procedure


Volume ID Optional. The volume serial number to be assigned to aSCSI device (6 alphanumeric characters). (Device Typemust be SCSIA or SCSIB.)

Unit Address Optional. The host device number to be assigned to aSCSI device (1 to 4 hexadecimal digits). (Device Typemust be SCSIA or SCSIB.)

Note: If you enter a Volume ID and a Unit Address, youmust enter Y for Request Device Initialization (lower rightcorner of panel) to initialize the SCSI device.

Device Type Required. Valid types are: 3380J, 3380K, 3380KE,33901, 33902, 33903, 33909, SCSIA, SCSIB

Domain Target LUN Required on non-V2Xf subsystems only if you will needto access this device from an Open Systems platform.The SCSI address of the inserted device is initiallydisplayed and must be changed. Domain and Target areeach 1 to 2 digits; LUN is 1 to 3 digits.

SCSI Blksize On non-V2Xf subsystems, this field appears and displaysthe default logical block size (512) when you enter aDevice Type of SCSIA or SCSIB. Valid block sizes are:512, 2048, 4096, 8192, and 16384.

Functional Device ID (FDID)Required. Enter 1 to 2 hexadecimal digits. DuplicateFDIDs are rejected.

Name Optional. Device name does not have to be unique.Enter 1 to 8 characters in the set: a to z, A to Z, 0 to9, $, @, _, #, -, +, &, ., /, or set the name toblanks.

PAVBASE Required for an Alias. Specify the FDID of the Basedevice to which this Alias is related. Appears only onV2Xf subsystems.

Cyls The number of cylinders for this functional device. Thisfield is modifiable only on V2X, V2X2, and V2Xfsubsystems. This field must be zero when defining PAVAliases or defining functional devices with the normal(default) number of cylinders for the specified devicetype. Once microcode support for Large Volumes isavailable, Large Volumes must be defined with a 33909device type and 32760 cylinders. If defining aFlexVolume, the device type cannot be 33901 or 33902;the permissible number of cylinders depends on thespecified device type as follows:



� If 3380J, Cyls must be from 1-885 cylinders

� If 3380KE, Cyls must be from 886-1770 cylinders

� If 3380K, Cyls must be from 1771-2655 cylinders

� If 33903, Cyls must be from 1-3339 cylinders

� If 33909, Cyls must be from 3340-32760 cylinders

CKD Enabled Enter either Y or N.

Y Enables host access to the CKD functional device.N Disables host access to the CKD functional device.

Default: Y

SCSI Enabled Enter either Y or N.

Y Enables host access to the SCSI functional device.N Disables host access to the SCSI functional device.

Default: N

CKD R/W Enter either Y or N.

Y Enables host write access to the CKD device.N Disables host write access to the CKD device.

Default: Y

SCSI R/W Enter either Y or N.

Y Enables host write access to the SCSI device.N Disables host write access to the SCSI device.

Default: N

Cache Enabled Enter either Y or N.

Y Enables caching.N Disables caching.

Default: Y

When cache is disabled, caching is still turned on, butthe caching algorithm is changed. In a write operation,tracks are queued for immediate destaging to the arrays,instead of being held in cache. In a read operation, atrack is staged to cache and then queued fordeallocation from cache as soon as the read is complete.

DASD Fast Write This option only provides 3990 compatibility; its setting (Yor N) has no effect on SVA operations.

Default: Y

Privileged ECAM You must designate at least one functional device as aprivileged ECAM device—that is, as an eligibledestination for Category 1-restricted messages.However, you should limit the number of such devices.

Enter either Y or N.

Y Makes the device eligible forCategory 1-restricted messages.



N Makes the device ineligible forCategory 1-restricted messages.

Default: N

Note: For Y to take effect, the SVAA Communicationsfield on this panel must also be set to YES. (This is doneby issuing a SET ECAMDEVICE subcommand for thisdevice; see page 8-164 for details.)

Data Bridge Enter either Y or N.

Y Defines device as a Data Bridge.N Does not define device as a Data Bridge.

Default: N

Data Bridge devices must be defined using a 33909device type.

Status Bridge Enter either Y or N.

Y Defines device as a Status Bridge.N Does not define device as a Status Bridge.

Default: N

Status Bridge devices must be defined using a 33903device type.

Request Dev Init This field appears only on non-V2Xf subsystems andapplies only to SCSI devices. You can initialize a SCSIdevice with a volser and host device number at the timeyou define it.

Y Requests device initialization. Note: If you enter Y,you must also complete the Volume ID and UnitAddress fields on this panel.

N Skips device initialization. If you have completed theVolume ID and Unit Address fields, entering Ncauses an error.

Default: N


Result: The panel is redisplayed in update mode. The following fields arefilled in on the basis of the information you have entered:

� Subsystem ID � Cyls � Functional (MB)� Phys. Used(MB) Shared� Phys. Used(MB) Total



next Displays the next INSERT FUNCTIONAL DEVICE panel—if you insertedmultiple devices.



previous Displays the previous INSERT FUNCTIONAL DEVICE panel—unless thefirst device you inserted is displayed.

end Cancels the entries you have made and displays the next INSERTFUNCTIONAL DEVICE panel or, if this is the last device inserted, returnsto the FUNCTIONAL DEVICE SELECTION panel.

cancel Cancels the entries you have made, skips processing any additionalINSERT FUNCTIONAL DEVICE panels, and returns to the FUNCTIONALDEVICE SELECTION panel.


Replicate Functional Device

Replicating a Functional DeviceThe REPLICATE FUNCTIONAL DEVICE panel appears when you enter the Replicate(R) command on one or more lines on the FUNCTIONAL DEVICE SELECTION panel.

To display the REPLICATE FUNCTIONAL DEVICE panel:

SubsystemComponent

Selection

ReplicateFunctional

Device

FunctionalDevice

Selection


SubsystemSelection

C11007

Enter 1

MM00

AX00

AX10

AX05

CA20

CA25

Enter 1

Enter 3

Enter R






Examples of the REPLICATE FUNCTIONAL DEVICE panel:

The example below shows how the fields are initialized when a SCSI device hasbeen selected for replication.

� �SIBCA25 �� REPLICATE FUNCTIONAL DEVICE ��COMMAND===>


Volume ID ===> ______ Operating System: MVS Subsystem ID: Unit Address ===> ____ Online: Mounted: NO SVAA Communication: NO Device Type ===> SCSIA_ Domain Target -LUN-

SCSI Blksize ===> 512__ 7__ 3____ �____

Functional Device ID (FDID) ===> 21__ Name ===> DEV��21 Partition (T=Test/P=Prod.) : P

------------- Capacity -------------- --- Device Status (Y=Yes/N=No) ---Functional --Phys. Used(MB)-- Y CKD Enabled Y SCSI Enabled

Cyls (MB) Shared Total Y CKD R/W Y SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� Y DASD Fast Write N Secondary


N Request Dev Init

� �

Figure 7-29. Replicate Functional Device panel for non-V2Xf subsystems (SIBCA25)

The following example shows how fields are initialized when a Base device on aV2Xf has been selected for replication.



Volume ID : Operating System: MVS Subsystem ID: Unit Address : Online: Mounted: SVAA Communication: Device Type ===> 339�3_

Functional Device ID (FDID) ===> 7��_ Name ===> ABC_____ PAV Base Device ID (PAVBASE) :


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� Y DASD Fast Write N Secondary

Y Privileged ECAM N Data BridgeN Status Bridge

� �

Figure 7-30. Replicate Functional Device panel for Base on V2Xf subsystem (SIBCA25)

The next example shows how fields are initialized if an Alias device on a V2Xf hasbeen selected for replication.





Volume ID : Operating System: MVS Subsystem ID: Unit Address : Online: Mounted: SVAA Communication: Device Type ===> 339�3_

Functional Device ID (FDID) ===> 7F�_ Name ===> _______ PAV Base Device ID (PAVBASE) : 7��


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� Y DASD Fast Write N Secondary

Y Privileged ECAM N Data BridgeN Status Bridge

� �

Figure 7-31. Replicate Functional Device panel for Alias on V2Xf subsystem

Display-only Fields







Partition The partition with which the device is associated.Appears only on non-V2Xf subsystems.

Cyls The number of cylinders for this functional device. (Setto zero for PAV Alias devices)

Functional (MB) The device's functional capacity (in megabytes). (Set tozero for PAV Alias devices)

Phys. Used(MB) Shared The amount of physical space (in megabytes) that isshared among functional devices as a result of aSnapShot command. (N/A indicates that SnapShotmicrocode is not installed on this subsystem.)

Phys. Used(MB) Total The physical space on the device (in megabytes) that isoccupied by data after compression and compaction.





Procedure


Volume ID Optional. The volume serial number to be assigned to aSCSI device (6 alphanumeric characters). (Device Typemust be SCSIA or SCSIB.)

Unit Address Optional. The host device number to be assigned to aSCSI device (1 to 4 hexadecimal digits). (Device Typemust be SCSIA or SCSIB.)

Note: If you enter a Volume ID and a Unit Address, youmust enter Y for Request Device Initialization (lower rightcorner of panel) to initialize the SCSI device.

Device Type Valid SCSI device types are SCSIA and SCSIB.

Domain Target LUN Required on non-V2Xf subsystems only if you will needto access this device from an Open Systems platform.The SCSI address of the replicated device is initiallydisplayed and must be changed. Domain and Target areeach 1 to 2 digits; LUN is 1 to 3 digits.

SCSI Blksize Optional. The logical block size of the replicated deviceis initially displayed. Appears only on non-V2Xfsubsystems. Valid block sizes are: 512, 2048, 4096,8192, and 16384.

Functional Device ID (FDID)Required. Enter 1 to 2 hexadecimal digits. DuplicateFDIDs are rejected.

Name Optional. Device name does not have to be unique.Enter 1 to 8 characters in the set: a to z, A to Z, 0 to9, $, @, _, #, -, +, &, ., /, or set the name toblanks. (Cannot be changed for a PAV Alias.)

PAVBASE Required for an Alias. Specify the FDID of the Basedevice to which this Alias is related. Appears only onV2Xf subsystems.

CKD Enabled Enter either Y or N. (Cannot be changed for a PAVAlias.)




CKD R/W Enter either Y or N. (Cannot be changed for a PAVAlias.)

Y Enables host write access to the CKD device.N Disables host write access to the CKD device.


Y Enables host write access to the SCSI device.



N Disables host write access to the SCSI device.

Cache Enabled Enter either Y or N. (Cannot be changed for a PAVAlias.)


When cache is disabled, caching is still turned on, butthe caching algorithm is changed. In a write operation,tracks are queued for immediate destaging to the arrays,instead of being held in cache. In a read operation, atrack is staged to cache and then queued fordeallocation from cache as soon as the read is complete.

DASD Fast Write This option only provides 3990 compatibility; its setting (Yor N) has no effect on SVA operations. (Cannot bechanged for a PAV Alias.)

Privileged ECAM You must designate at least one functional device as aprivileged ECAM device—that is, as an eligibledestination for Category 1-restricted messages.However, you should limit the number of such devices.(Cannot be changed for a PAV Alias.)

Enter either Y or N.






Default: N




Default: N


Request Dev Init This field appears only on non-V2Xf and applies only toSCSI devices. You can initialize a SCSI device with avolser and host device number at the time you define it.



Y Requests device initialization. Note: If you enter Y,you must also complete the Volume ID and UnitAddress fields on this panel.

N Skips device initialization. If you have completed theVolume ID and Unit Address fields, entering Ncauses an error.


Result: The following fields are filled in on the basis of the information youhave entered:

� Subsystem ID� Phys. Used(MB) Shared� Phys. Used(MB) Total



next Displays the next REPLICATE FUNCTIONAL DEVICE panel—if youreplicated a device multiple times.

previous Displays the previous REPLICATE FUNCTIONAL DEVICE panel—unlessthe first replicate panel is displayed.

end Cancels the entries you have made and displays the next REPLICATEFUNCTIONAL DEVICE panel (if more panels remain) or returns to theFUNCTIONAL DEVICE SELECTION panel.

cancel Cancels the entries you have made, skips processing any otherREPLICATE FUNCTIONAL DEVICE panels, and returns to the FUNCTIONALDEVICE SELECTION panel.


Initialize Functional Device

Initializing a Functional DeviceThe INITIALIZE FUNCTIONAL DEVICE panel appears when you enter the Initialize (N)command on one or more lines on the FUNCTIONAL DEVICE SELECTION panel.This panel enables you to initialize a SCSI functional device with a volume serialnumber and a host device number.

The following example of the INITIALIZE FUNCTIONAL DEVICE panel shows howfields are initialized for a SCSI device

To display the INITIALIZE FUNCTIONAL DEVICE panel:

SubsystemComponent

Selection

InitializeFunctional

Device

FunctionalDevice

Selection


SubsystemSelection

C11036

Enter 1

MM00

AX00

AX10

AX05

CA20

CA25

Enter 1

Enter 3

Enter N





Initialize Functional Device

� �SIBCA25 �� INITIALIZE FUNCTIONAL DEVICE ��COMMAND===>

Subsystem Name: TEST

Volume ID ===> ______ Operating System: MVS Subsystem ID: C��4 Unit Address ===> ____ Online: NO Mounted: NO SVAA Communication: NO Device Type : SCSIA Domain Target -LUN- SCSI Blksize : 512 6__ �____ �____

Functional Device ID (FDID) : 3E� Name : DEV��21 Partition (T=Test/P=Prod.) : P


Cyls (MB) Shared Total Y CKD R/W Y SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 123�.2 �.� �.� Y DASD Fast Write N Secondary


� �

Figure 7-32. Initialize Functional Device panel (SIBCA25)

Procedure

1. Tab to and update the following two fields:

Volume ID Required. The volume serial number to be assigned tothe SCSI device (6 alphanumeric characters).

Unit Address Required. The host device number to be assigned to aSCSI device (1 to 4 hexadecimal digits).


Result: The panel is redisplayed in update mode.



next Displays the next INITIALIZE FUNCTIONAL DEVICE panel—if you selectedmultiple devices for initialization.

previous Displays the previous INITIALIZE FUNCTIONAL DEVICE panel—unless thefirst device you selected is displayed.

end Cancels the entries you have made and displays the next INITIALIZEFUNCTIONAL DEVICE panel or, if this is the last device selected, returnsto the FUNCTIONAL DEVICE SELECTION panel.

cancel Cancels the entries you have made, skips processing any additionalINITIALIZE FUNCTIONAL DEVICE panels, and returns to the FUNCTIONALDEVICE SELECTION panel.


Update Functional Device

Updating a Functional DeviceThe UPDATE FUNCTIONAL DEVICE panel appears when you enter the Select (S)command on one or more lines on the FUNCTIONAL DEVICE SELECTION panel.

If you select more than one functional device for update, the panels appear in theorder listed.

Notes:

1. You cannot update a functional device that is currently being used for privilegedECAM communications.

2. You cannot update a functional device that is part of a PPRC pair.

3. Question marks (?) will appear in certain fields for Bridge devices and Aliasdevices since they are not mapped by SVAA device mapping.

To display the UPDATE FUNCTIONAL DEVICE panel:

SubsystemComponent

Selection

UpdateFunctional

Device

FunctionalDevice

Selection


SubsystemSelection

C11008

Enter 1

MM00

AX00

AX10

AX05

CA20

CA25

Enter 1

Enter 3

Enter S






Examples of the UPDATE FUNCTIONAL DEVICE panel:

� �SIBCA25 �� UPDATE FUNCTIONAL DEVICE ��COMMAND===>


Volume ID : SC��33 Operating System: MVS Subsystem ID: C��1 Unit Address : 4�21 Online: YES Mounted: SVAA Communication: NO Device Type : SCSIA Domain Target -LUN- SCSI Blksize : 512 6__ 3____ 7____

Functional Device ID (FDID) : 21 Name ===> ________ Partition (T=Test/P=Prod.) : P


Cyls (MB) Shared Total Y CKD R/W Y SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� �.� 47.3 Y DASD Fast Write N Secondary

N Privileged ECAM N Data BridgeN Request Dev Attn N Status Bridge

� �

Figure 7-33. Update Functional Device panel for non-V2Xf subsystems (SIBCA25)



Volume ID : SW77�� Operating System: MVS Subsystem ID: 77�� Unit Address : 77�� Online: YES Mounted: YES SVAA Communication: NO Device Type : 339�3

Functional Device ID (FDID) : 7�� Name ===> ABC_____ Number of Aliases : ��2 PAV Type (B=Base/A=Alias) : B


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� �.� �.1 Y DASD Fast Write N Secondary

Y Privileged ECAM N Data BridgeN Request Dev Attn N Status Bridge

� �

Figure 7-34. Update Functional Device panel for Base device on V2Xf subsystems(SIBCA25)





Volume ID : Operating System: MVS Subsystem ID: 77�� Unit Address : Online: NO Mounted: NO SVAA Communication: NO Device Type : 339�3

Functional Device ID (FDID) : 7FF Name ===> ________ PAV Base Device ID (PAVBASE) : 7�� PAV Type (B=Base/A=Alias) : A


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� �.� �.1 Y DASD Fast Write N Secondary

Y Privileged ECAM N Data BridgeN Request Dev Attn N Status Bridge

� �

Figure 7-35. Update Functional Device panel for Alias on V2Xf subsystems (SIBCA25)

Display-only Fields


Volume ID The volume serial number for the device.



Unit Address The host device number. This field is blank if the unitaddress is not defined to the host operating system.




Device Type The type of DASD device the functional device emulates.

Domain Target LUN The SCSI address of the device, if applicable. Appearsonly on non-V2Xf subsystems.

SCSI Blksize The logical block size for the SCSI device, if applicable.Appears only on non-V2Xf subsystems.

Functional Device ID (FDID)The hexadecimal identifier (FDID) for the device.

Number of Aliases The number of Aliases for this Base. Appears only onV2Xf subsystems.



PAVBASE The FDID of the Base device to which this Alias isrelated. Appears only on V2Xf subsystems.

Partition The partition with which the device is associated.Appears only on non-V2Xf subsystems.

Cyls The number of cylinders for this functional device. (Setto zero for PAV Alias devices.)

Functional (MB) The device's functional capacity (in megabytes). (Set tozero for PAV Alias devices.)

Phys. Used(MB), SharedThe amount of physical space (in megabytes) that isshared among functional devices as a result of aSnapShot command. (N/A indicates that SnapShotmicrocode is not installed on this subsystem.)

Phys. Used(MB), Total The physical space on the device (in megabytes) that isoccupied by data after compression and compaction.



Procedure

1. Tab to and update the following fields as required.

Name Optional. The device name does not have to be unique.Enter 1 to 8 characters in the set: a to z, A to Z, 0 to9, $, @, _, #, -, +, &, ., /, or set the name toblanks. (Cannot be changed for a PAV Alias.)

CKD Enabled Enter either Y or N. (Cannot be changed for a PAVAlias.)




CKD R/W Enter either Y or N. (Cannot be changed for a PAVAlias.)

Y Enables host write access to the CKDdevice.N Disables host write access to the CKD device.


Y Enables host write access to the SCSI device.N Disables host write access to the SCSI device.

Cache Enabled Enter either Y or N. (Cannot be changed for a PAVAlias.)


When cache is disabled, caching is still turned on, butthe caching algorithm is changed. In a write operation,tracks are queued for immediate destaging to the arrays,



instead of being held in cache. In a read operation, atrack is staged to cache and then queued fordeallocation from cache as soon as the read is complete.

DASD Fast Write This option only provides 3990 compatibility; its setting (Yor N) has no effect on SVA operations. (Cannot bechanged for a PAV Alias.)

Privileged ECAM You must designate at least one functional device as aprivileged ECAM device—that is, as an eligibledestination for Category 1-restricted messages.However, you should limit the number of such devices.

Enter either Y or N. (Cannot be changed for a PAVAlias.)






Default: N


Request Dev Attn Enter either Y or N.

Y Enables the request.N Disables the request.

If Y, the Enabled field must also be set to Y.

When device attention is requested, a state-changeinterrupt is sent to all interfaces associated with a pathgroup for that device. This command may also be usedto free a hang condition in the host operating system.



Default: N



Result: The functional device is updated and the panel displays the data youhave entered.


Delete Functional Device



next Displays the next UPDATE FUNCTIONAL DEVICE panel—if you selectedmultiple devices.

previous Displays the previous UPDATE FUNCTIONAL DEVICE panel—unless thefirst update panel is displayed.

end Cancels the entries you have made and displays the next UPDATEFUNCTIONAL DEVICE panel (if more panels remain) or returns to theFUNCTIONAL DEVICE SELECTION panel.

cancel Cancels the entries you have made, skips processing any other UPDATEFUNCTIONAL DEVICE panels, and returns to the FUNCTIONAL DEVICESELECTION panel.

Deleting a Functional DeviceThe DELETE FUNCTIONAL DEVICE panel appears when you enter D on a devicedefinition line on the FUNCTIONAL DEVICE SELECTION panel. This sectiondescribes the procedure for deleting the following types of functional devices:

� A device residing on a non-V2Xf subsystem

� A Base device on a V2Xf subsystem

� An Alias device on a V2Xf subsystem

To display the DELETE FUNCTIONAL DEVICE panel:



SubsystemComponent

Selection

DeleteFunctional

Device

FunctionalDevice

Selection


SubsystemSelection

C11009

Enter 1

MM00

AX00

AX10

AX05

CA20

CA25

Enter 1

Enter 3

Enter D






Examples of the DELETE FUNCTIONAL DEVICE panel:

� �SIBCA25 �� DELETE FUNCTIONAL DEVICE ��COMMAND===>


Volume ID : Operating System: MVS Subsystem ID: C��1 Unit Address : Online: NO Mounted: NO SVAA Communication: NO Device Type : SCSIA Domain Target -LUN-

SCSI Blksize : 512 ___ _____ _____

Functional Device ID (FDID) : 23 Name ===> DEV��21 Partition (T=Test/P=Prod.) : P


Cyls (MB) Shared Total Y CKD R/W Y SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� �.� �.1 Y DASD Fast Write N Secondary


� �

Figure 7-36. Delete Functional Device panel for non-V2Xf subsystems (SIBCA25)



Volume ID : SW77�� Operating System: MVS Subsystem ID: 77�� Unit Address : 77�� Online: YES Mounted: YES SVAA Communication: NO Device Type : 339�3

Functional Device ID (FDID) : 7�� Name : ABC Number of Aliases : ��2 PAV Type (B=Base/A=Alias) : B


Cyls (MB) Shared Total Y CKD R/W Y SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary3339 2838.� �.� �.1 Y DASD Fast Write N Secondary


� �

Figure 7-37. Delete Functional Device panel for Base on V2Xf subsystem (SIBCA25)





Volume ID : Operating System: MVS Subsystem ID: 77�� Unit Address : Online: NO Mounted: NO SVAA Communication: NO Device Type : 339�3

Functional Device ID (FDID) : 7FF Name : PAV Base Device ID (PAVBASE) : 7�� PAV Type (B=Base/A=Alias) : A


Cyls (MB) Shared Total Y CKD R/W N SCSI R/W----- ---------- -------- -------- Y Cache Enabled N Primary

� �.� �.� �.� Y DASD Fast Write N SecondaryY Privileged ECAM N Data BridgeN Request Dev Attn N Status Bridge

� �

Figure 7-38. Delete Functional Device panel for Alias on V2Xf subsystems (SIBCA25)

Notes:

1. Deleting a functional device makes all data on the device inaccessible.Therefore, you should back up any critical data before deleting the device.

2. Before performing the deletion, you must vary the device offline to all hosts.Note that PAV Base devices must be varied offline before any related Aliasdevice can be deleted, and that Alias devices cannot be varied online or offline.

3. If OS/390 is running under VM, access to a device may be affected by a VMdevice status of BOXED. To remove the BOXED status in VM: (1) vary thedevice offline to ensure its status is OFFLINE, (2) vary the device online toreestablish a path, and then (3) vary it offline again.

4. You cannot delete a functional device that is part of a PPRC pair. You mustfirst delete the pair and then you may delete the device.

5. The FORCE parameter is no longer required when deleting an Alias that isrelated to an offline Base device that contains user data.

Procedure

1. Check the Online field to verify that the device is not online.

(This field should say NO.)

2. Check the Phys. Used(MB), Total field.

If this field shows a value greater than zero, back-end storage (user data)exists on the device.


SVAA verifies the device is offline and then issues the message:

Are you sure you want to delete this device?Reply Yes or No.



4. Type Y and press Enter.

Subsystem Checks Performed

The subsystem checks the following conditions:

� Device online � PAV Status � Back-end storage � Busy state

Device online

This check prevents you from deleting a functional device that is currently beingaccessed by another host system.

If the device is not offline to all hosts, the following message appears:

device online to another system.Reply Retry or Cancel.

Enter either R or C.

R Reissues the delete request.

But first, you should ensure that the functional device is offline to all hosts.

C Cancels the delete request.

PAV Status

This check prevents you from deleting a Base device (online or offline) that still hasAlias devices related to it and from deleting Alias devices from an online Basedevice. No operator prompt is issued. However, if the PAV status is not correct,the delete will fail, and an error message is issued.

Back-end storage

The subsystem also checks for back-end storage.

Note: PAV Alias devices do not actually consume additional back-end storage.

If the device is defined to the host:

The VTOC is scanned for user data. If user data is found, the following messageappears:

user data exists for this device.Reply FORCE or Cancel.

Enter either FORCE or C.

FORCE Deletes the back-end storage associated with the device. (Any tracksthat are associated with the device and are currently in cache are alsodeleted.)

Note: To force a delete when the device is defined to the host, youmust have RACF DASDVOL class ALTER authority for the volser. If theDASDVOL class is not active on this host, before you attempt to deletethe device you must either: 1) disable the device (use the ALTERDEVICE command and the CKDENA(NO) parameter), 2) vary all pathsoffline to the device on this host operating system, or 3) implement theSIBIOATX user exit, otherwise the delete will fail with a SIB1164E



message indicating that you have insufficient authority to access thesubsystem.


If the device is not defined to the host:

The subsystem checks the device for back-end storage. If user data is found, thefollowing message appears:

back-end storage exists for this device.Reply FORCE or Cancel.

Enter either FORCE or C.

FORCE Deletes the back-end storage associated with the device. (Any tracksthat are associated with the device and are currently in cache are alsodeleted.)

Note: To force a delete when the device is not defined to the host, youmust have RACF FACILITY class ALTER authority for the generalizedresource IXFP.FORCE.DELETE.FUNC.DEV. Since Alias devices arealways considered to not be defined to the host, the deletion of Aliaseswill always use the RACF FACILITY class and the generalized resourceIXFP.FORCE.DELETE.FUNC.DEV profile for security checking.


Busy state

The subsystem determines whether activity is occurring on the device. If the deviceis busy, the following message appears:

device is busy. Reply Retry or Cancel.

Enter either R or C.

R Reissues the delete request.

The subsystem repeats all checks—to verify that this functional device isoffline, contains no back-end storage, and is not busy.


The panel for the next functional device you selected appears. If there isnone, the UPDATE FUNCTIONAL DEVICE panel appears.

Result

With the satisfactory completion of all checks, the subsystem sends a state-changeinterrupt to all channels and deletes the device.

The subsystem issues a message that the delete is complete.


Browse Current Configuration

Browsing the Current Configuration

The Browse function enables you to view the current characteristics and status ofsubsystem configurations, channel interfaces, and functional devices. To begin“browsing,” select option 2, BROWSE, on the SUBSYSTEM ADMINISTRATION menu(page 7-10).

The following diagram shows the sequence of panels you can access whenbrowsing.



SubsystemSelection


FunctionalDevice

Selection

FunctionalDevice

1

S

2 3

C11041

Enter 1

MM00

AX00

AX10

AX05

CR00 CR20

CR25

Enter 2

Enter 1, 2, or 3





(Parallel)


(SCSI)


(ESCON)


(Fibre)

ChannelType

Selection

ChannelSelection

CA11

CA10

CR15 CA17CR15 CA18

S

SSIDDefinitions

CR01


(FICON)

CA19


Drive Module Utilities

The panels displayed with the Browse function are similar to many of the panelsyou use to update a subsystem configuration. Note the following differences:

� “BROWSE” appears below the command field on each panel.

� The arrows (===>) that indicate data entry fields on the configuration updatepanels are replaced with colons on the browse panels.

Most important: All fields on the browse panels are for display only; you cannotenter or modify data.


The DRIVE MODULE UTILITIES menu provides a selection of six different utilities formanaging the status of the drive modules in the subsystem. To display this menu:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

AX20 CU40 CU50 CU50 CU60 CU25

Enter 3

Enter an optionfrom 1 to 6



DrainDrive

Modules

FormTest Arrays

FormProduction

Arrays

MoveTest Into

Production

AllocateSpares

1 32 4 65

C11011

DisplayDrive Module

Status

Drive ModuleUtilities




Example of the DRIVE MODULE UTILITIES menu:

� �SIBCU3� �� DRIVE MODULE UTILITIES ��OPTION ===>

Subsystem ===>

1 DISPLAY - Display drive module status2 ALLOCATE - Allocate spare drive modules3 FORM TEST - Form test arrays4 FORM PROD - Form production arrays5 MOVE TEST - Move drive modules from test to production6 DRAIN - Drain drive modules

� �

Figure 7-39. Drive Module Utilities menu (SIBCU30)

Procedure


2. Tab to Subsystem and type the name of the SVA subsystem—if SVAA iscommunicating with multiple SVA subsystems and you want to work with onlyone of them. (Skip this field if you want to work with more than onesubsystem.)

3. Press Enter.

Result: The next panel to appear depends upon the number of SVA subsystemsfor which you have issued a SET ECAMDEVICE subcommand during the currentSVAA session.

� For only one SVA subsystem:

The next panel is the drive module utility panel for the option you have justselected.

� For multiple SVA subsystems:

The SUBSYSTEM SELECTION panel appears (see “Subsystem Selection” onpage 7-13).

Select one or more subsystems to be included in the drive module task youwant to perform.


Display Drive Module Status

Displaying Drive Module StatusTo display the DISPLAY DRIVE MODULE STATUS panel:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

AX20

Enter 3

Enter 1



C11012


DisplayDrive Module

Status




Example of the DISPLAY DRIVE MODULE STATUS panel:

� �SIBAX2� �� DISPLAY DRIVE MODULE STATUS �� Row 1 to 1� of 32COMMAND===> _ SCROLL ===> PAGEBROWSE

Subsystem Name: SVASYS��

�� All Drives by Slot ��Drive Modules: 32 Available Spares: 2

Ary� P 13+2=15 Ary1 P 13+2=15 Ary2 Ary3Ary4 Ary5 Ary6 Ary7

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary�.�.� P.A � �.�.1 P.A. � �.�.2 P.A � �.�.3 P.A ��.�.4 P.A 1 �.�.5 P.A. � �.�.6 P.A � �.�.7 P.A ��.1.� P.A � �.1.1 P.A. � �.1.2 P.A � �.1.3 S.A -�.1.4 P.A � �.1.5 P.A. 1 �.1.6 P.A 1 �.1.7 P.A 1�.2.� P.A 1 �.2.1 P.A. � �.2.2 P.A 1 �.2.3 P.A 1�.2.4 P.A 1 �.2.5 P.A. 1 �.2.6 P.A � �.2.7 P.A 1�.3.� P.A 1 �.3.1 P.A. 1 �.3.2 P.A 1 �.3.3 P.A 1�.3.4 P.A � �.3.5 S.A. - �.3.6 P.A 1 �.3.7 P.A �1.�.� U.N - 1.�.1 U.N. - 1.�.2 U.N - 1.�.3 U.N -1.�.4 U.N - 1.�.5 U.N. - 1.�.6 U.N - 1.�.7 U.N -

� �

Figure 7-40. Display Drive Module Status panel (SIBAX20)

This panel displays the status of all drive modules in the subsystem.

Display-only Fields


Drive Modules The total number of drive modules in the SVA subsystem (orin the specific partition displayed).

Available Spares The number of spare drive modules in the SVA subsystem.

Note: A negative number in this field indicates a seriouscondition—there are no spares available. You need toallocate or install at least one spare drive module.

Ary0 - Ary7 The array's partition (P or T) and its configuration.

Note: While a drive is being drained, the configuration candisplay a total that is too large (followed by a ?), for example:13+2=16?

Column Headings

U.T.S The SVA unit (0 to 3), tray (0 to 3), and slot (0 to 7) in whichthe drive is located.

Status The status of the drive module. For example, P.A indicatesthe drive is in the Production partition and active.

Explanations of all drive module status codes appear inAppendix A, “Drive Module Status.”

Ary The array (0 to 7) to which the drive is assigned, or “-” toindicate the drive is not assigned to an array.





The part command initiates a sequence of five panels that show drive modulestatus by partition:

part Displays the status of all drive modules in the MAT partition:

� �SIBAX25 �� DISPLAY DRIVE MODULE STATUS �� Row 1 to 1 of 1COMMAND===> _ SCROLL ===> PAGEBROWSE


�� Media Acceptance Test Partition ��Drive Modules: 1 Available Spares: 17

Ary� Ary1 Ary2 Ary3Ary4 Ary5 Ary6 Ary7

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary �.�.3 M.A -

� �Figure 7-41. Display Drive Module Status panel—MAT partition (SIBAX25)

Note that the Ary0 through Ary7 fields are empty in both the MATpartition and Spares partition displays because drive modules in thosepartitions are not assigned to any array.

next With the above panel displayed, next displays the status of drivemodules in the “next” partition (the Spares partition):

� �SIBAX25 �� DISPLAY DRIVE MODULE STATUS �� Row 1 to 5 of 5COMMAND===> _ SCROLL ===> PAGEBROWSE


�� Spares Partition ��Drive Modules: 17 Available Spares: 17

Ary� Ary1 Ary2 Ary3Ary4 Ary5 Ary6 Ary7

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary �.1.� S.A - �.1.1 S.A - �.1.2 S.A - �.1.3 S.A - �.1.4 S.A - �.1.5 S.A - �.1.6 S.A - �.1.7 S.A - �.2.� S.A - �.2.1 S.A - �.2.2 S.A - �.2.4 S.A - �.2.5 S.A - �.2.6 S.A - �.2.7 S.A - �.3.5 S.A �.3.7 S.A

� �Figure 7-42. Display Drive Module Status panel—Spares partition (SIBAX25)


Allocate Spares

You can issue the next command three more times to display the Testpartition, Production partition, and Unavailable partition (in that order).

previous Displays the previous drive module status panel—the reverse of the nextcommand (that is, from the Unavailable partition display, the order is:Production partition, Test partition, Spares partition, and MAT partition).

From any of the partition panels, issue the end command to return to theDISPLAY DRIVE MODULE STATUS panel.

end Returns to the DRIVE MODULE UTILITIES menu.

Allocating SparesTo display the ALLOCATE SPARES panel:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

CU40

Enter 3

Enter 2



C11013


AllocateSpares



Allocate Spares

Example of the ALLOCATE SPARES panel:

� �SIBCU4� �� ALLOCATE SPARES �� Row 1 to 2 of 2COMMAND===> SCROLL ===> PAGE


�� Media Acceptance Test Partition ��Drive Modules: 8 Available Spares: 15

Selection Mode ===> I (I = Include, X = Exclude)Type S to Select Drive Module (DEFAULT = ALL - valid for INCLUDE only)

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary_ 3.3.� M.A - _ 3.3.1 M.A - _ 3.3.2 M.A - _ 3.3.3 M.A -_ 3.3.4 M.A - _ 3.3.5 M.A - _ 3.3.6 M.A - _ 3.3.7 M.A -

� �

Figure 7-43. Allocate Spares panel (SIBCU40)

This panel enables you to move drive modules from the MAT partition to the Sparespartition. It lists all the drive modules eligible to be moved into the Spares partition;that is, all drives with a status of M.A.

This procedure is necessary before you can form an array, if the spares required forthe array are not available.

Display-only Fields


Drive Modules The number of drive modules in the MAT partition.

Available Spares The number of spare drive modules in the subsystem.


Column Headings


Status The status of the drive module (e.g., M.A indicates the driveis in the MAT partition and active).


Ary As drives in the MAT partition are not assigned to any array,a “-” appears in this field.


Allocate Spares

Procedure

1. Perform one of the following actions:

� To select all drives, issue the submit command.

� To select one or more drives, type S next to the drives you want to allocateas spares, and issue the submit command.

� To select most but not all drives, type X in the Selection Mode field, type Snext to the drives you want to exclude, and issue the submit command.

Result: The panel is refreshed and displays a message notifying youwhether the operation is successful. The value in the Available Spares field isincreased by the number of spares allocated. The value in the Drive Modulesfield is decreased by the same number.



part Displays the status of all drive modules in the MAT partition (see “PanelCommand Options” on page 7-72 for an example).

refresh Erases error messages and displays the field values currently in effect.



Form Test Arrays

Forming Test ArraysNote: You cannot form Test arrays on the V2Xf, V2X2, V2X, V960, or 9500SVA—only on subsystems running earlier microcode. See “Functional Differencesbetween Subsystems” on page 1-2 for more information. (Existing Test arrays arestill completely functional.)

To display the FORM TEST ARRAY(S) panel:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

CU50

Enter 3

Enter 3



C11014


FormTest

Arrays



Form Test Arrays

Example of the FORM TEST ARRAY(S) panel:

� �SIBCU5� �� FORM TEST ARRAY(S) �� Row 1 to 1� of 1�COMMAND===> SCROLL ===> PAGE


�� Spares Partition ��Drive Modules: 4� Available Spares: 4�

Number of Arrays ===> ALL (1 to 7 or ALL)Array size ===> 13+2 (5+2 or 13+2)

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary �.1.1 S.A - �.2.6 S.A - �.3.3 S.A - 1.3.5 S.A - 1.3.6 S.A - 2.�.3 S.A - 2.1.6 S.A - 2.2.7 S.A - 3.�.� S.A - 3.�.1 S.A - 3.�.2 S.A - 3.�.3 S.A - 3.�.4 S.A - 3.�.5 S.A - 3.�.6 S.A - 3.�.7 S.A - 3.1.� S.A - 3.1.1 S.A - 3.1.2 S.A - 3.1.3 S.A - 3.1.4 S.A - 3.1.5 S.A - 3.1.6 S.A - 3.1.7 S.A - 3.2.� S.A - 3.2.1 S.A - 3.2.2 S.A - 3.2.3 S.A - 3.2.4 S.A - 3.2.5 S.A - 3.2.6 S.A - 3.2.7 S.A - 3.3.� S.A - 3.3.1 S.A - 3.3.2 S.A - 3.3.3 S.A - 3.3.4 S.A - 3.3.5 S.A - 3.3.6 S.A - 3.3.7 S.A -

� �

Figure 7-44. Form Test Array(s) panel (SIBCU50)

This panel enables you to form one or more arrays for the Test partition. It lists allthe drive modules in the Spares partition eligible to be used to form arrays.

If too few spares are available to form all the arrays you request, the subsystemforms as many arrays as possible. For an explanation of the number of sparesrequired to form arrays, see “Forming Additional Arrays” on page 2-3.

Display-only Fields


Drive Modules The number of drive modules in the Spares partition.



Column Headings


Status The status of the drive module (e.g., S.A indicates the driveis in the Spares partition and active).


Ary As drives in the Spares partition are not assigned to anyarray, a “-” appears in this field.


Form Test Arrays

Procedure

1. You can enter an integer from 1 to 7 or ALL in the Number of Arrays field.However, you would seldom form more than one Test array.

If you enter ALL, the subsystem forms as many arrays as the number ofavailable spares allows.

2. Tab to Array Size and enter the size (5+2 or 13+2) of the arrays to beformed—if the size is to be different from the current subsystem default size,which is displayed.

Note: You can form 5+2 arrays only on the 9393 or 9500 SVA.


Result: The panel is refreshed, displaying the information you entered and amessage notifying you whether the operation is successful. The values in theDrive Modules and Available Spares fields are reduced by the number ofspares used to form arrays.



part Displays the status of all drive modules in the Spares partition (see“Panel Command Options” on page 7-72 for an example).




Form Production Arrays

Forming Production ArraysTo display the FORM PRODUCTION ARRAY(S) panel:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

CU50

Enter 3

Enter 4



C11015


FormProduction

Arrays




Example of the FORM PRODUCTION ARRAY(S) panel:

� �SIBCU5� �� FORM PRODUCTION ARRAY(S) �� Row 1 to 1� of 1�COMMAND===> SCROLL ===> PAGE


�� Spares Partition ��Drive Modules: 4� Available Spares: 4�

Number of Arrays ===> ALL (1 to 7 or ALL)Array size ===> 13+2 (5+2 or 13+2)

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary �.1.1 S.A - �.2.6 S.A - �.3.3 S.A - 1.3.5 S.A - 1.3.6 S.A - 2.�.3 S.A - 2.1.6 S.A - 2.2.7 S.A - 3.�.� S.A - 3.�.1 S.A - 3.�.2 S.A - 3.�.3 S.A - 3.�.4 S.A - 3.�.5 S.A - 3.�.6 S.A - 3.�.7 S.A - 3.1.� S.A - 3.1.1 S.A - 3.1.2 S.A - 3.1.3 S.A - 3.1.4 S.A - 3.1.5 S.A - 3.1.6 S.A - 3.1.7 S.A - 3.2.� S.A - 3.2.1 S.A - 3.2.2 S.A - 3.2.3 S.A - 3.2.4 S.A - 3.2.5 S.A - 3.2.6 S.A - 3.2.7 S.A - 3.3.� S.A - 3.3.1 S.A - 3.3.2 S.A - 3.3.3 S.A - 3.3.4 S.A - 3.3.5 S.A - 3.3.6 S.A - 3.3.7 S.A -

� �

Figure 7-45. Form Production Array(s) panel (SIBCU50)

This panel enables you to form one or more arrays for the Production partition. Itlists all the drive modules in the Spares partition eligible to be used to form arrays.

If too few spares are available to form all the arrays you request, the subsystemforms as many arrays as possible. For an explanation of the number of sparesrequired to form arrays, see “Forming Additional Arrays” on page 2-3.

Display-only Fields


Drive Modules The number of drive modules in the Spares partition.



Column Headings


Status The status of the drive module (e.g., S.A indicates the driveis in the Spares partition and active).


Ary As drives in the Spares partition are not assigned to anyarray, a “-” appears in this field.



Procedure

1. Enter an integer from 1 to 7 or ALL in the Number of Arrays field.

Note: The first array must be formed at the LOP or the DOP when thesubsystem is installed. Therefore, the maximum number of arrays you canform when you use this panel is 7.

If you enter ALL, the subsystem forms as many arrays as the number ofavailable spares allows.

Note: You can form 5+2 arrays only on the 9393 or 9500 SVA. On thosesubsystems, you can form up to eight 5+2 arrays, but only four 13+2 arrays.Both array sizes can exist on one subsystem. The possible array combinationson one subsystem are:

4 13+2 arrays and 0 5+2 arrays3 13+2 arrays and 2 5+2 arrays2 13+2 arrays and 4 5+2 arrays1 13+2 arrays and 6 5+2 arrays0 13+2 arrays and 8 5+2 arrays

2. Tab to Array Size and enter the size (5+2 or 13+2) of the arrays to beformed—if the size is to be different from the current subsystem default size,which is displayed.


Result: The panel is refreshed, displaying the information you entered and amessage notifying you whether the operation is successful. The values in theDrive Modules and Available Spares fields are reduced by the number ofspares used to form arrays.



part Displays the status of all drive modules in the Spares partition (see“Panel Command Options” on page 7-72 for an example).




Move Test into Production

Moving Test Partition into Production PartitionNote: This panel is not available on the V2Xf, V2X2, V2X, V960, or 9500 SVA.See “Functional Differences between Subsystems” on page 1-2 for moreinformation.

To display the MOVE TEST INTO PRODUCTION panel:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

CU60

Enter 3

Enter 5



C11016


MoveTest Into

Production


Example of the MOVE TEST INTO PRODUCTION panel:



� �SIBCU6� �� MOVE TEST INTO PRODUCTION �� Row 1 to 4 of 4COMMAND===> _ SCROLL ===> PAGE


�� Test Partition ��Drive Modules: 15 Available Spares: 4�

Ary� P 13+2=15 Ary1 T 13+2=15 Ary2 Ary3Ary4 Ary5 Ary6 Ary7

U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary �.�.1 T.A 1 �.1.1 T.A 1 �.2.1 T.A 1 �.2.7 T.A 1 �.3.1 T.A 1 1.�.1 T.A 1 1.1.1 T.A 1 1.2.1 T.A 1 1.3.1 T.A 1 2.�.1 T.A 1 2.1.1 T.A 1 2.2.1 T.A 1 3.�.1 T.A 1 3.1.1 T.A 1 3.2.1 T.A 1

� �

Figure 7-46. Move Test into Production panel (SIBCU60)

This panel enables you to move all drive modules associated with the Testpartition—including all functional device definitions and associated data—to theProduction partition.

Display-only Fields


Drive Modules The number of drive modules in the Test partition.

Available Spares The number of spare drive modules in the SVA subsystem.


Column Headings


Status The status of the drive module (e.g., T.A indicates the driveis in the Test partition and active).


Ary The array (0 to 7) to which the drive is assigned.

Procedure


Result: The panel is refreshed. The message “MOVE TEST COMPLETE.”appears if the operation is successful. The Drive Modules count is reduced bythe number of Test partition drives that are moved to the Production partition.





part Displays the status of all drive modules in the Test partition (see “PanelCommand Options” on page 7-72 for examples of similar panels).




Drain Drive Modules

Draining Drive ModulesTo display the DRAIN DRIVE MODULE(S) panel:


SubsystemSelection

Enter 1

MM00

AX00

CU30

AX05

CU25

Enter 3

Enter 6



C11017


DrainDrive

Modules



Drain Drive Modules

Example of the DRAIN DRIVE MODULE(S) panel:

� �SIBCU25 �� DRAIN DRIVE MODULE(S) �� Row 1 to 3 of 17COMMAND===> _ SCROLL ===> PAGE


Completion NotificationHost Node ID ===> MVSS��1 User ID===> SMITH

�� Array Selection (Type S to select only one) ��_ Ary� T 13+2=15 _ Ary1 P 13+2=15 _ Ary2 P 13+2=15 Ary3Ary4 Ary5 Ary6 Ary7

�� Disk Array Unit(DAU)/Tray Selection (Type S to select only one) ��_ DAU � _ DAU 1 DAU 2 DAU 3

_ Tray � _ Tray 2 _ Tray � _ Tray 2 Tray � Tray 2 Tray � Tray 2 _ Tray 1 _ Tray 3 _ Tray 1 _ Tray 3 Tray 1 Tray 3 Tray 1 Tray 3

�� Drive Module(s) Selection (Type S to select one or more) ��U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary U.T.S Status Ary

_ �.�.� S.A - _ �.�.1 S.A - _ �.�.2 S.A - _ �.�.3 T.A �_ �.�.4 T.A � _ �.�.5 P.A 1 _ �.�.6 P.A 1 _ �.�.7 P.A 2_ �.1.� S.A - _ �.1.1 S.A - _ �.1.2 T.A � _ �.1.3 T.A �

� �

Figure 7-47. Drain Drive Module(s) panel (SIBCU25)

This panel enables you to initiate a drain of specific drive modules. When driveshave been successfully drained, they are placed in the MAT partition for removal orreallocation. You can select drive modules to be drained in one of four ways:

� individually (by unit, tray, slot) � by array � by tray� by DAU (disk array unit)

Notes:

1. You cannot drain the last drive module, last array, last tray, or last DAU.

2. You cannot drain a DAU or a tray if a Test partition is defined.

3. You cannot terminate a drain once it has started.

Before the SVA subsystem starts a drain, it ensures that there is sufficientsubsystem capacity to hold the data to be drained. If available capacity isinsufficient, the drain request fails.

Procedure

1. (Optional) The Completion Notification fields display the default values. Tochange the destinations for notification, tab to and update the following fields:

Host Node ID The host Node ID to which notice of drain completionshould be sent.

Default: Node ID from which you initiate the drain.

User ID The user ID of the individual to be notified.

Default: Current user ID


Drain Drive Modules

2. To select components to be drained, type S to the left of:

� Ary — the array to be drained, or� DAU — the disk array unit to be drained, or� Tray — the tray to be drained, or� one or more U.T.S designations — the drive module(s) to be drained.

In a single drive module drain, all the data in the drive is moved to a sparedrive module. Thus, for each Production or Test partition drive module to bedrained, a spare drive module must be available. (No spare drive is required todrain a spare, however.) If the necessary spare drive modules are notavailable when a drain is requested, the drain request is rejected.

In an array drain, all the data in the array is moved to other existing arrays inthe same partition.

Note: While a drive is being drained, the configuration can display a total thatis too large (followed by a ?), for example: Ary1 P 13+2=16?. (When the drainis complete, the displayed total will be correct.)

The method used to drain a DAU or a tray depends upon the number of sparesavailable in addition to the number of spares reserved for existing arrays.

� If, for each drive module in the DAU or tray to be drained, a spare drive isavailable outside that DAU or tray, each drive module is drained into one ofthe spares.

� If the number of available spares is inadequate, the process involvesdraining arrays. In this case, drain activity may be observed in“associated” drive modules—modules that are part of an array beingdrained but are outside the “target” DAU or tray.


A confirm message appears:

Once initiated, this drain cannot be terminated.Are you sure you wish to continue? (Reply YES or NO)

4. Type YES to continue and press Enter.

Result: An SVAA message appears in the upper right corner of the panel.Issue the help command to get information about the message. If the drain issuccessfully initiated, a process identifier number for the drain is assigned.






Display Event Status

Displaying Event Status

You can view the status of drain events that have been run within the last 60 daysor are still in progress. You begin this activity by entering selection criteria on theEVENT SELECTION panel. In this way you shorten the list (which appears next)from which you select events for display.

To display the EVENT SELECTION panel:

EventSelection

EventSummary

Drive ModuleDrain Status

Drive ModuleTest (MAT)

Status

Drive ModuleTest (MAT)

Detail Status


SubsystemSelection

C11018

Enter 1

MM00

AX00

AX05

EV00

EV05

EV20 EV30

EV35

Enter 4

Enter event dates and eventtype or event identifier.



S S

Detail




Example of the EVENT SELECTION panel:

� �SIBEV�� EVENT SELECTION ��COMMAND===>

Subsystem Name: Multiple

From Date: �6MAY1999 Display events beginning with this date. Defaultis 7 days prior to today. Format is ddmmmyyyyor N format where N is from � to -6�.

To Date: 19MAY1999 Display events up to and including this date.Format is ddmmmyyyy or N from � to -6�.

Type: ALL__ Qualify selection by specific events.

Identifier: __________ Qualify selection by selecting a specific eventnumber. "LAST" may be used to indicate the last

event.

� �

Figure 7-48. Event Selection panel (SIBEV00)

Use this panel to specify selection criteria for drains for which you would like to seestatus or historical data.

Procedure

1. Tab to and update the following fields:

From Date Required unless you specify an Identifier. This is thestarting date for event reporting. It must be within 60 days oftoday's date and earlier than the To Date.

Enter the From Date in the form ddmmmyyyy, or enter aminus sign followed by a number to indicate the number ofdays prior to today. For example, -6 indicates that thestarting date is six days ago; 0 indicates today's date.

Default: 7 days prior to today's date

To Date Required unless you specify an Identifier. This is the endingdate for event reporting. It must be within 60 days of today'sdate and later than the From Date.

Enter the To Date in the form ddmmmyyyy, or enter a minussign followed by a number to indicate the number of daysprior to today. For example, -2 indicates that the ending dateis two days ago; 0 indicates today's date.

Default: Today's date

Type The type of events to be included in the report.

Enter DRAIN or ALL.

Default: ALL



Identifier The numeric process identifier of a specific drain to bereported upon or “LAST” to indicate the most recent drain.

If you enter a process identifier, only that process will bereported upon; the From Date, To Date, and Type fields areignored.

If you enter LAST, the From Date and To Date fields areignored. The Type field determines which last event(s) willbe reported upon.

Default: none

2. Press Enter.

Result: The EVENT SUMMARY panel appears.

� �SIBEV�5 �� EVENT SUMMARY ��COMMAND===> _

Subsystem Name: Multiple

Event Subsystem Initiating Initiation Completion Name Identifier Name Nodeid Userid Date Time Date Time_ MAT 15�7816�24 ICESUB�1 A�8�3 linda �1MAY1999 14:34S DRAIN �793394512 SVASYSD C1271 john �1MAY1999 13:33_ DRAIN 316578144� ICESUB�1 A�8�3 linda 27MAY1999 ��:42 27OCT1999 �2:23S MAT 22�9143271 SVASYSA F��48 dorothy 27MAY1999 �7:51 27OCT1999 �9:2�_ DRAIN 16238879�4 SVASYSC B1774 dave 15MAY1999 22:�1 16OCT1999 ��:25_ DRAIN �921568232 SVASYSA C1271 john 15MAY1999 23:18 16OCT1999 �2:18_ MAT 43591�3625 SVASYSA F��48 dorothy 11MAY1999 12:45 11OCT1999 14:22_ MAT 1142783432 SVASYSA F��48 dorothy 1�MAY1999 12:21 1�OCT1999 15:15_ MAT 1��2569�18 SVASYSC A�8�3 linda �8MAY1999 14:23 �8OCT1999 2�:21_ MAT 4339�22761 SVASYSA A�8�3 linda �7MAY1999 12:21 �7OCT1999 15:15

� �

Figure 7-49. Event Summary panel (SIBEV05)

The EVENT SUMMARY panel displays summary information for events meeting thecriteria you specified on the EVENT SELECTION panel.

Display-only Fields

Subsystem Name The name of the SVA subsystem selected on the SUBSYSTEMSELECTION panel. (Multiple indicates more than onesubsystem was selected.)

Event Name The type of event.

Event Identifier The process ID number.

Subsystem Name The name of the SVA subsystem in which the event wasinitiated.

Initiating Node ID The host node ID from which the event was initiated.

Initiating User ID The ID of the user who initiated the event.

Initiation Date The date the user initiated the event.


Drain Status

Initiation Time The time the user initiated the event.

Completion Date The date the event completed execution (blank if not yetcompleted).

Completion Time The time the event completed execution (blank if not yetcompleted).

Procedure

To display additional information about specific events:

1. Tab to the desired events and type S to the left of each event name.

2. Press Enter.

Result: A status display for the first selected event appears.

See “Drive Module Drain Status” (below) for drain events, or “MediaAcceptance Test Status” on page 7-93 for MAT events.

Drive Module Drain StatusThe DRIVE MODULE DRAIN STATUS panel appears after you type an S next to adrain event on the EVENT SUMMARY panel.

� �SIBEV2� �� DRIVE MODULE DRAIN STATUS ��COMMAND===> _

Subsystem Name: SVASYSD

Initiating Node ID: C1271 Started: �1MAY1999 13:33:�2Initiating User ID: john Completed:Drain Identifier: �793394512 Elapsed Time: �2:2�:21

Percent Complete: 86

Completion NotificationHost Node ID: C1271 User ID: john

Serial Serial SerialU.T.S Number Status U.T.S Number Status U.T.S Number Status�.�.� ��187256 P.A �.�.1 ��387256 P.A �.1.2 ��87256 S.A�.�.3 ��925618 P.A �.�.4 ��525618 P.A �.1.5 ��225618 S.A�.�.6 ��427831 P.A �.1.7 ��627831 P.A �.2.� ��527831 S.A�.2.1 ��567261 S.A �.2.2 ��767261 P.A �.2.3 ��667261 S.A�.2.4 ��4192�1 P.A �.2.5 ��8192�1 S.A �.2.6 ��7192�1 S.A�.2.7 ��4192�1 P.A �.3.� ��8192�1 S.A �.3.1 ��7192�1 S.A

� �

Figure 7-50. Drive Module Drain Status panel (SIBEV20)

This panel displays detailed status information for a drain.

Display-only Fields

Subsystem Name The name of the SVA subsystem in which the drain wasinitiated.

Initiating Node ID The host node ID from which the drain was initiated.


Drain Status

Started The date and time the drain started.

Initiating User ID The user ID of the person who initiated the drain.

Completed The time the drain completed (blank if not yet completed).

Drain Identifier The process ID of the drain.

Elapsed Time The elapsed execution time (hh:mm:ss) for the drain.

Percent Completed The percentage of the drain that is complete.

Host Node ID The host node ID to be notified when the drain completed.

User ID The user ID of the person to be notified when the draincompleted.


Serial Number The serial number of the drive module.

Device Status The status of the drive module (partition code followed by thestate code).




refresh Updates the display with current information.

next Displays the next selected event, if any.

previous Displays the previously displayed event, if any.

end Returns to the EVENT SUMMARY panel.

end (again) Returns to the EVENT SELECTION panel.


MAT Status

Media Acceptance Test StatusThe DRIVE MODULE TEST (MAT) STATUS panel appears after you type an S next toa MAT event on the EVENT SUMMARY panel.

� �SIBEV3� �� DRIVE MODULE TEST (MAT) STATUS ��COMMAND===> _

Subsystem Name: SVASYSA

Initiating Node ID: F��48 Started: 27MAY1999 �7:51:17Initiating User ID: dorothy Completed: 27MAY1999 �9:2�:38Terminating Node ID: F��48 Elapsed time: �1:29:21Terminating User ID: toto Iterations Completed: 1MAT Identifier: 22�9143271

Test Duration --------------- Media Tests ------------------Number of Iterations 2 S Sequential _ Read OnlyTime in Hours � _ High-Low

_ Random

Test data patterns (Default to "worst case" data pattern)Media: ____ ____ ____ ____ ____ ____ ____ ____Electronics: ____ ____ ____ ____ ____ ____ ____ ____

Completion NotificationHost Node ID: D�562 User ID: harry

� �

Figure 7-51. Drive Module Test (MAT) Status panel (SIBEV30)

This panel displays summary status information for a Media Acceptance Test.

Display-only Fields

Subsystem Name The name of the SVA subsystem in which the MAT wasinitiated.

Initiating Node ID The host node ID from which the MAT was initiated.

Started The date and time the MAT started.

Initiating User ID The user ID of the person who initiated the MAT.

Completed The time the MAT completed (blank if not yet completed).

Terminating Node ID The host node ID from which the test is stopped.

Elapsed Time The elapsed execution time (hh:mm:ss) for the MAT.

Terminating User ID The user ID of the person who stopped the test.

Iterations Completed The number of test iterations completed.

MAT Identifier The process ID of the Media Acceptance Test.

Number of Iterations The number of iterations requested when the MAT wasstarted.

Media Tests The type of MAT executed.

Time in Hours The test time requested when the MAT was initiated.


MAT Detail Status

Media This data pattern stresses the drive module's mediarecording capabilities.

Electronics This data pattern stresses the drive module's datatransfer capabilities.




detail Displays the DRIVE MODULE TEST (MAT) DETAIL STATUS panel (see thefollowing section).

next Displays the next selected event, if any.

previous Displays the previously displayed event, if any.

end Returns to the EVENT SUMMARY panel.

end (again) Returns to the EVENT SELECTION panel.

Media Acceptance Test Detail StatusThe DRIVE MODULE TEST (MAT) DETAIL STATUS panel appears after you issue thedetail command on the DRIVE MODULE TEST (MAT) STATUS panel.

� �SIBEV35 �� DRIVE MODULE TEST (MAT) DETAIL STATUS ��COMMAND===> _

Subsystem Name: SVASYSA

MAT Identifier: 22�9143271 Iterations Completed: 1 Elapsed Time: �1.29.21

Serial % of Iter % of Motion Seek Tracks SectorsU.T.S Number Status Total Count Iter. Seeks Errors Tested Assigned�.�.� ��187256 M.A 1��. 1 1�.3 8612 4�9�8 1�.�.1 ��925618 M.A 1��. 1 11.3 869� 41279 ��.�.2 ��427831 M.A 1��. 1 9.� 8511 4�426 ��.�.3 ��567261 M.A 1��. 1 9.3 8534 4�537 ��.�.4 ��4192�1 M.A 1��. 1 11.1 8674 412�5 ��.�.5 ��782722 M.A 1��. 1 8.3 8456 4�166 ��.�.6 ��325551 M.A 1��. 1 1�.� 8589 4�797 2�.�.7 ��719282 M.A 1��. 1 11.1 8672 41199 ��.1.� ��91�119 M.A 1��. 1 9.8 8573 4�723 ��.1.2 ��319222 M.A 1��. 1 8.9 85�3 4�389 �

� �

Figure 7-52. Drive Module Test (MAT) Detail Status panel (SIBEV35)

This panel displays detailed status information for a MAT.


MAT Detail Status

Display-only Fields

Subsystem Name The name of the SVA subsystem in which the MAT wasinitiated.

MAT Identifier The process ID of the Media Acceptance Test.

Iterations Completed The number of test iterations that have completed.

Elapsed Time The time that has elapsed since the MAT started.

U.T.S The SVA unit (0 to 3), tray (0 to 3), and slot (0 to 7) inwhich the drive is located.

Serial Number The serial number of the drive module.

Status The status of the drive module (the partition code followedby the state code).


% of Total The percentage of the test that is complete.

Iter Count The number of test iterations that have been completed.

% of Iter. The percentage of the current test iteration that iscomplete.

Motion Seeks The number of times the read/write head has beenpositioned on a track.

Seek Errors The number of errors encountered in trying to position theread/write head to a track.

Tracks Tested The number of disk tracks that have been tested.

Sectors Assigned The number of bad sectors on the disk.




end Returns to the DRIVE MODULE TEST (MAT) STATUS panel.


Specifying SnapShot Subcommands


You can submit SNAP DATASET and SNAP VOLUME subcommands from the panelsdescribed in this section. The following diagram illustrates the panel sequence.

Begin by selecting option 4 on the main menu to display the SNAPSHOTSUBCOMMAND SELECTION panel.

Selecting a SnapShot Subcommand

� �SIBSS�� SNAPSHOT SUBCOMMAND SELECTION ��OPTION ===>

1 SNAP DATASET - Specify Snap Dataset Subcommand2 SNAP VOLUME - Specify Snap Volume Subcommand3 PPRC SNAPSHOT - Specify Remote Snap Volume Subcommand

� �

Figure 7-53. SnapShot Subcommand Selection panel (SIBSS00)

Enter 1, 2, or 3 to select the SnapShot subcommand you want to submit—eitherSNAP DATASET, SNAP VOLUME, or PPRC Remote SnapShot.



Specifying the Snap Dataset SubcommandHere is an example of the SPECIFY SNAP DATASET SUBCOMMAND panel:

� �SIBSD�� SPECIFY SNAP DATASET SUBCOMMAND ��COMMAND===>

Source ===> ____________________________________________Enter Y to propagate source data set name to target ===> _

Target ===> ____________________________________________

Volume ===> ______ or Esoteric ===> ________ Volume Count ===> ___ Storage Class ===> ________ Mgmt Class ===> ________ Data Class ===> _______ Relate ===> ____________________________________________ Replace ===> NO_ (Yes, No) Host Copy Mode ===> EXC (EXC, SHR) Tolerate Enqueue Failure ===> NO_ (Yes, No) Tolerate Truncation ===> NO_ (Yes, No) Datamover Name ===> NONE___ (NONE, DFDSS, DSS, ADRDSSU) Catalog ===> YES (Yes, No) Error Disposition ===> DELETE (KEEP, DELETE) Force ===> NO_ (Yes, No) Debug ===> OFF (OFF, ON) Trace ===> OFF (OFF, ON)

� �

Figure 7-54. Specify Snap Dataset Subcommand panel (SIBSD00)

Procedure

Note: Complete descriptions of the following parameters, including restrictions ontheir use, are provided in the SNAP DATASET subcommand documentationbeginning on page 8-172.


Source The name of the data set to be snapped: 1 to 44alphanumeric or national ($ @ #) characters, and 2special (- {) characters, in “nodes” of one to eightcharacters separated by periods. Do not use a numeric(0-9) or special character (- or {) as the first character ofany node.

Both the source and target data sets must resolve tocompatible devices within the same SVA subsystem andpartition. All extents for the source data set must resideon devices that are currently online and accessible. PAVAlias devices cannot be used as the source of a snapoperation.

For a list of the types of data sets that you can snap anda list of data sets that are not supported by SnapShot,see page 5-4.

Enter Y to propagate source data set name to targetEnter Y to create a target dsname identical to the sourcedsname. (You must then alter the generated dsname.)



Target The data set name of the target data set: 1 to 44alphanumeric or national ($ @ #) characters, and 2special (- {) characters, in “nodes” of one to eightcharacters separated by periods. Do not use a numeric(0-9) or special character (- or {) as the first character ofany node.

Both the source and target data sets must resolve tocompatible devices in the same SVA subsystem andpartition. All extents for the target data set must resideon devices that are currently online and accessible. PAVAlias devices cannot be used as the target of a snapoperation.

In the TSO environment, OS/390 will prefix your user ID toyour data set name. Enclose the data set name inquotes to prevent prefixing.

Volume The target volume to which the data set is to besnapped. This is a volume serial number of a devicethat is online to the host attempting the snap.

Enter either the Volume parameter or the Esotericparameter—not both.

Note: When the source data set and the target volumedo not reside on the same SVA subsystem and partition,you must specify a valid data mover to perform the copyoperation.

Esoteric The generic locally defined device group name of theDASD devices onto which the source data set is to besnapped.

Enter either the Volume parameter or the Esotericparameter—not both.

Volume Count The maximum number of volumes on which a new targetdata set can be allocated: a decimal number from 1 to255 without quotes.

Storage Class An SMS storage class (the locally defined list of storageattributes) required for a newly allocated target data set.

Mgmt Class A locally defined SMS management class to be assignedto the target data set (used when SnapShot dynamicallyallocates the data set).

Data Class A locally defined SMS data class to be assigned to thetarget data set.

Relate The name of the base cluster to which the targetalternate index is to be related: 1 to 44 alphanumeric ornational ($ @ #) characters, and two special (- {)characters, in “nodes” of one to eight charactersseparated by periods. Do not use a numeric (0-9) orspecial character (- or {) as the first character of anynode.



In the TSO environment, OS/390 will prefix your user ID toyour base cluster name. Enclose the name in quotes toprevent prefixing.

Replace Specifies whether the source data set is to overwrite anydata in an existing target data set. If the target data setis allocated OLD or SHR, and you do not specify Y for thisparameter, the snap operation terminates.

Y Overwrite the existing target data set.N Do not overwrite the existing target data set.

Host Copy Mode The level of serialization control to be obtained for thesource and target data sets.

EXC Use dynamic allocations with disposition of OLD.Exclusive control offers better protection of dataintegrity than shared control. Enter this option ifyou want exclusive control over the source or targetduring a snap operation.

SHR Use dynamic allocations with a disposition of SHR.Enter this option if you want to modify the source ortarget during a snap operation.

Tolerate Enqueue FailureEnables you to snap data sets when exclusiveserialization control over them cannot be obtained.Integrity of the data set cannot be assured. If you alsospecify EXC for Host Copy Mode, you must use thisparameter to snap a data set that is unavailable at theexclusive serialization level.

Y Snap a data set that is unavailable at the exclusiveserialization level.

N Do not snap a data set if it is unavailable at theexclusive serialization level.

Tolerate Truncation Allows a data set to be truncated and a warningmessage to be issued if the target extent size is smallerthan the source. Otherwise, if the target cannot beextended, the snap fails. SnapShot truncates the dataset only if it cannot allocate more space. Truncation maycause loss of data.

Y Truncate a data set that is snapped to a smallerdata set.

N Do not truncate a data set if target is smaller thansource data set. The snap fails.

Datamover Name When the source and target data sets do not reside onthe same SVA subsystem and partition, you can specifya data mover program to physically copy the data setwithout SnapShot.

If you do not specify a data mover and one is needed, orif SnapShot is unable to access the data mover, theoperation is cancelled.

NONE Do not use a data mover.ADRDSSU Use ADRDSSU (IBM DFSMSdss utility).DFDSS Use DFDSS (IBM DFSMSdss utility).



DSS Use DSS (IBM DFSMSdss utility).

Catalog When SnapShot dynamically allocates the target dataset, this parameter specifies whether a new target dataset is to be cataloged when it is created by the SNAPDATASET subcommand. SnapShot supports ICF catalogentries only.

Y Catalog the the allocated target data set.N Do not catalog the the allocated target data set.

This option is supported only for target data setsthat must be created and are not SMS managed.

Error Disposition When SnapShot dynamically allocates the target dataset, this parameter specifies whether that data set will bekept or deleted when an error occurs.

KEEP Keep the target data set if an error occurs.DELETE Delete the target data set if an error occurs.

Force Allows you to snap a data set that was created asabsolute track (ABSTR) or as unmovable (PSU, POU orDAU). SnapShot makes no attempt to ensure that thetarget data set will be accessible. SnapShot does notallocate absolute track locations.

Unless Force is enabled, the target for an unmovable orabsolute track data set must reside or be allocated on adifferent device from that of the source and at the samephysical track location as the source.

Y Snap an unmovable or absolute track data set to adifferent physical track location on the same oranother device.

N Do not snap an unmovable or absolute track dataset unless the target location is identical to thesource.

Debug Enables or disables the logging of diagnostic messages.Use this parameter only at the request of your servicerepresentative.

OFF Disable the generation of diagnostic messages.ON Enable the generation of diagnostic messages.

Trace Specifies whether GTF trace records are to be generatedby the subcommand. GTF records can be used tofacilitate troubleshooting of SNAP DATASET subcommandprocessing. Use this parameter only at the request ofyour service representative.

For Trace to be effective, you must start an active tracewith GTF TYPE=USR before executing the SNAP DATASETsubcommand.

OFF Disable trace record generation.ON Enable trace record generation.

2. Issue the submit command to execute the SNAP DATASET subcommand.



Specifying the Snap Volume SubcommandHere is an example of the SPECIFY SNAP VOLUME SUBCOMMAND panel:

� �SIBSV�� SPECIFY SNAP VOLUME SUBCOMMAND ��COMMAND===>

Source Volume ===> ______ or Unit Addr ===> ____ Offline ===> NO (Yes, No)

Target Volume ===> ______ or Unit Addr ===> ____ Offline ===> NO (Yes, No)

Replace ===> NO (Yes, No) Datamover Name ===> NONE (NONE, DFDSS, DSS, ADRDSSU)

Tolerate Enqueue Failure ===> NO (Yes, No) Copy Volid ===> YES (Yes, No) Condition Volume ===> ALL (ALL, LaBeL) Debug ===> OFF (OFF, ON) Trace ===> OFF (OFF, ON)

� �

Figure 7-55. Specify Snap Volume Subcommand panel (SIBSV00)

Procedure

Note: Complete descriptions of the following parameters, including restrictions ontheir use, are provided in the SNAP VOLUME subcommand documentation beginningon page 8-185.


Source Volume The volume serial number of the volume to be snapped.You can specify the source by either Source Volume orUnit Addr—not both. The volume must be online to thehost attempting the snap operation unless the Unit Addrand Offline parameters are specified. In no case canPAV Alias devices be used as the source of a snapoperation.

When a device contains multivolume data sets, you mustsnap each volume individually (note that serialization isnot maintained across volumes).

Unit Addr The unit address (as known to the host operatingsystem) of the source or target volume. You can specifythe source or target by either Volume or Unit Addr—notboth. The volume must be online to the host attemptingthe snap operation unless both Unit Addr and Offlineare specified.

Target Volume The volume serial number of the target volume. You canspecify the target by either Target Volume or UnitAddr—not both. The volume must be online to the hostattempting the snap operation unless both Unit Addrand Offline are specified. In no case can PAV Aliasdevices be used as the target of a snap operation.



Offline Specifies whether a snap operation is allowed tocontinue if a volume is offline. This parameter is validonly when used with the Unit Addr parameter. In nocase can PAV Alias devices be used as the target of asnap operation.

If the volume is offline and you specify N, the snapoperation will fail if the volume is offline. If thisparameter is used for the target, Copy Volid andReplace must be Yes.

Y Volume may be offline.N Volume must be online.

Replace Specifies whether the snap operation is to overwrite anydata in an existing target volume.

If the target volume contains user data and you do notspecify Y, the snap operation terminates. If the targetvolume contains user data and you do not specify Y, thesnap operation terminates.

Y Overwrite the existing target volume.N Do not overwrite the existing target volume.

Datamover Name When the source and target volumes do not reside onthe same SVA subsystem and partition, you can specifya data mover program to physically copy the volumewithout SnapShot.

If you do not specify a data mover and one is needed,the operation is cancelled.

NONE Do not use a data mover.ADRDSSU Use ADRDSSU (IBM DFSMSdss utility).DFDSS Use DFDSS (IBM DFSMSdss utility).DSS Use DSS (IBM DFSMSdss utility).

Tolerate Enqueue FailureEnables you to snap a volume when exclusiveserialization control cannot be obtained. However,SnapShot cannot allocate a target volume that is alreadyheld as OLD. Integrity of the volume cannot be assured.You must use this parameter to snap a volume that isunavailable at the requested serialization level.

Y Snap a volume that is unavailable at the exclusiveserialization level.

N Do not snap a volume if it is unavailable at theexclusive serialization level.

Copy Volid Specifies whether, during a SNAP VOLUME operation,SnapShot is to retain the volume identity of the source ortarget.

Y Retain the volser of the source volume in the snapand make the target volume unavailable to the host(that is, SnapShot issues an OS/390 VARY OFFLINEcommand against the target volume).



N Retain the original volser of the target volume andmake the target volume available to the host (thatis, SnapShot issues a VARY ONLINE commandagainst the target volume).

Condition Volume Specifies, when the Copy Volid value is N, whether theentire target volume is to be conditioned or only its label.Conditioning only the label allows the target volume toremain online while the VTOC and VVDS retain theidentity of the source volume.

If Copy Volid is not used, or if you specify Y for CopyVolid, this parameter is ignored.

ALL Specifies that Copy Volid with N specified is tofunction normally.

LBL Specifies that the target volume label is to beupdated with the target volser. The target UCB willalso be updated with the target volser. The VVDS,VTOC, and VTOC index will be the same as theoriginal source volume. The target volume willremain ONLINE.



Trace Specifies whether GTF trace records are to be generatedby the subcommand. GTF records can be used tofacilitate troubleshooting of SNAP VOLUME subcommandprocessing. Use this parameter only at the request ofyour service representative.

For Trace to be effective, you must start an active tracewith GTF TYPE=USR before executing the SNAP VOLUMEsubcommand.


2. Issue the submit command to execute the SNAP VOLUME subcommand.



Specifying the PPRC Remote SnapShot Volume SubcommandHere is an example of the SPECIFY PPRC REMOTE SNAPSHOT VOLUMESUBCOMMAND panel:

� �SIBSV�1 �� PPRC REMOTE SNAPSHOT VOLUME SUBCOMMAND ��COMMAND===>

Source Volume ===> ______ or Unit Addr ===> AED7 Offline ===> NO (Yes, No)

Remote FDID ===> 3E7 and Serial Number ===> 7�25

Tolerate Enqueue Failure ===> NO (Yes, No) Relocate ===> YES (Yes, No) Debug ===> OFF (OFF, ON) Trace ===> OFF (OFF, ON)

� �

Figure 7-56. Specify PPRC Remote SnapShot Volume Subcommand panel (SIBSV01)

Procedure

Note: Complete descriptions of the following parameters, including restrictions ontheir use, are provided in the SNAP VOLUME subcommand documentation beginningon page 8-185.


Source Volume The volume serial number of the volume to be snapped.You can specify the source by either Source Volume orUnit Addr—not both. The volume must be online to thehost attempting the snap operation unless the Unit Addrand Offline parameters are specified. In no case canPAV Alias devices be used as the source of a snapoperation.

When a device contains multivolume data sets, you mustsnap each volume individually (note that serialization isnot maintained across volumes).

Unit Addr The unit address (as known to the host operatingsystem) of the source or target volume. You can specifythe source or target by either Volume or Unit Addr—notboth. The volume must be online to the host attemptingthe snap operation unless both Unit Addr and Offlineare specified.

Offline Specifies whether a snap operation is allowed tocontinue if a volume is offline. This parameter is validonly when used with the Unit Addr parameter. In nocase can PAV Alias devices be used as the target of asnap operation.

If the volume is offline and you specify No, the snapoperation will fail if the volume is offline. If this



parameter is used for the target, Copy Volid andReplace must be Yes.

Y Volume may be offline.N Volume must be online.

Remote FDID Identifies the target functional device ID for the SnapShotrequest.

Serial Number Specifies the serial number of the remote SVA that isconnected via PPRC.

Tolerate Enqueue FailureEnables you to snap a volume when exclusiveserialization control cannot be obtained. You must usethis parameter to snap a volume that is unavailable atthe requested serialization level.

Yes Snap a volume that is unavailable at the exclusiveserialization level.

No Do not snap a volume if it is unavailable at theexclusive serialization level.

Relocate Specifies whether or not count fields are to be relocatedon the target DASD volume.

Yes Create target count fields that match the realcylinder location. This value is valid only if thetarget device is defined to begin on real cylinder 0.

No Use the original source count fields for the targetvolume.



Trace Specifies whether GTF trace records are to be generatedby the subcommand. GTF records can be used tofacilitate troubleshooting of SNAP VOLUME subcommandprocessing. Use this parameter only at the request ofyour service representative.

For Trace to be effective, you must start an active tracewith GTF TYPE=USR before executing the SNAP VOLUMEsubcommand.


2. Issue the submit command to execute the SNAP VOLUME subcommand.


Chapter 8. SVAA Subcommands and Commands

Chapter SummarySubcommands of SIBBATCH and SIBADMIN . . . . . . . . . . . . . . . . . . . 8-5

Executing Commands from SIBADMIN . . . . . . . . . . . . . . . . . . . . . . 8-5Executing Commands from SIBBATCH . . . . . . . . . . . . . . . . . . . . . 8-6Executing Macros from SIBADMIN . . . . . . . . . . . . . . . . . . . . . . . . 8-6

System Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Rules for Entering Subcommands and Parameters . . . . . . . . . . . . . . . . 8-7

Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Wildcard Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Subcommand Continuation . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

Redirecting Subcommand Output . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Subcommand Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11ALLOCATE SPARES Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-12

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Examples of ALLOCATE SPARES . . . . . . . . . . . . . . . . . . . . . . . 8-13

ALTER CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Parallel Channel: Syntax and Subcommand Usage . . . . . . . . . . . . . 8-14ESCON or FICON Channel: Syntax and Subcommand Usage . . . . . . 8-15SCSI Bus or Fibre Channel: Syntax and Subcommand Usage . . . . . . 8-15Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Examples of ALTER CHANNEL . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

ALTER DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Examples of ALTER DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28

ALTER SUBSYSTEM Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-29Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Examples of ALTER SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . 8-35

ATTN DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Examples of ATTN DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

DEFINE DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Examples of DEFINE DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-47

DELETE DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Examples of DELETE DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-52

DISPLAY CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-53Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53Examples of DISPLAY CHANNEL . . . . . . . . . . . . . . . . . . . . . . . 8-54

DISPLAY DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-55Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-55Examples of DISPLAY DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-57

DISPLAY NCL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59Example of DISPLAY NCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59

DISPLAY RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-60Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-60Examples of DISPLAY RELEASE . . . . . . . . . . . . . . . . . . . . . . . . 8-61

November, 2006 — PN 311290512, Rev. N Subcommands and Commands 8-1

DROP Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62DROP ECAMDEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62DROP NONICEBERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62

FORM ARRAY Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63Examples of FORM ARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-64

INITIALIZE DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-65Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-65Example of INITIALIZE DEVICE . . . . . . . . . . . . . . . . . . . . . . . . 8-67

LISTCFG CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-68Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68Examples of LISTCFG CHANNEL . . . . . . . . . . . . . . . . . . . . . . . 8-69

LISTCFG DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-70Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-70Examples of LISTCFG DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . 8-73

LISTCFG DRIVEMODULE Subcommand . . . . . . . . . . . . . . . . . . . . . 8-75Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-75Examples of LISTCFG DRIVEMODULE . . . . . . . . . . . . . . . . . . . . 8-77

LISTCFG SUBSYSTEM Subcommand . . . . . . . . . . . . . . . . . . . . . . 8-78Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-79Example of LISTCFG SUBSYSTEM for non-V2Xf subsystems . . . . . . . 8-80Example of LISTCFG SUBSYSTEM for V2Xf subsystems . . . . . . . . . 8-85

Definitions of LISTCFG Report Headings . . . . . . . . . . . . . . . . . . . . 8-110MACRO Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-115MOVE TESTPARTITION Subcommand . . . . . . . . . . . . . . . . . . . . . 8-116

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-116Example of MOVE TESTPARTITION . . . . . . . . . . . . . . . . . . . . . 8-116

| PPRCOPY Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-117| PPRCopy ESTPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-117| Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118| PPRCopy DELPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-121| Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-122| PPRCopy QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-123| Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-123| Example of PPRC QUERY DEVICE Output . . . . . . . . . . . . . . . . . 8-124| Example of PPRC QUERY PATHS Output . . . . . . . . . . . . . . . . . 8-125| Definitions of PPRC QUERY Report Headings . . . . . . . . . . . . . . . 8-126

QUERY Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128QUERY CACHEREFRESHRATE . . . . . . . . . . . . . . . . . . . . . . . 8-128QUERY CASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-129QUERY CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-129QUERY CMDECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-130QUERY CONFIGPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-130QUERY DEBUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-130QUERY DESTINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-131QUERY DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-131QUERY DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-132QUERY ECAMDEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-132QUERY IMPEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-132QUERY JAVA_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-133QUERY LOGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-133QUERY MAXRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-133QUERY NONICEBERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-134QUERY PAGESIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-134QUERY PARMLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-134


QUERY PROFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-135QUERY SERVERIDLETIME . . . . . . . . . . . . . . . . . . . . . . . . . . 8-135QUERY SERVERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-135QUERY SERVERPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SERVERSCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SIBHOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SIBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-136QUERY SSNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-137QUERY SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-137QUERY TITLEn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-137QUERY VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138QUERY VOLUMEPREFERENCING . . . . . . . . . . . . . . . . . . . . . 8-138QUERY WEBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-139

RELEASE DYNAMICDATA Subcommand . . . . . . . . . . . . . . . . . . . 8-139Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-139Examples of RELEASE DYNAMICDATA . . . . . . . . . . . . . . . . . . 8-142

RELEASE INTERVALDATA Subcommand . . . . . . . . . . . . . . . . . . . 8-143Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-143Examples of RELEASE INTERVALDATA . . . . . . . . . . . . . . . . . . 8-147

REPORT EVENTS Subcommand . . . . . . . . . . . . . . . . . . . . . . . . 8-148Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148Examples of REPORT EVENTS . . . . . . . . . . . . . . . . . . . . . . . 8-150

RESUME RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . 8-151Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-151Examples of RESUME RELEASE . . . . . . . . . . . . . . . . . . . . . . 8-152

SEND Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-152SEND DSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-152SEND SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-153SEND SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-153SEND SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-154SEND VOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-154

SET Subcommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-155SET CACHEREFRESHRATE . . . . . . . . . . . . . . . . . . . . . . . . . 8-155SET CASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-160SET CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-160SET CMDECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-161SET CONFIGPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-161SET DEBUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-162SET DESTINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-162SET DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-163SET ECAMDEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-164SET IMPEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-164SET JAVA_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-165SET LOGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-165SET MAXRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-165SET NONICEBERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-166SET PAGESIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-166SET SERVERIDLETIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-166SET SERVERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-167SET SERVERPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-167SET SERVERSCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168SET SIBHOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168SET SIBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168SET SSNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-169SET TITLEn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-169


SET VOLUMEPREFERENCING . . . . . . . . . . . . . . . . . . . . . . . 8-169SET WEBPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-171

SNAP DATASET Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-172Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-173Examples of SNAP DATASET . . . . . . . . . . . . . . . . . . . . . . . . . 8-184

SNAP VOLUME Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-185Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-186Examples of SNAP VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . 8-194

START Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START DSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-196START SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-197START VOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-197

START DRAIN Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-198Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-198Examples of START DRAIN . . . . . . . . . . . . . . . . . . . . . . . . . . 8-200

START RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-201Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-201Examples of START RELEASE . . . . . . . . . . . . . . . . . . . . . . . . 8-201

STOP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP DSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-202STOP VOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-203

STOP RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-203Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-203Examples of STOP RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . 8-203

SUSPEND RELEASE Subcommand . . . . . . . . . . . . . . . . . . . . . . . 8-204Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-204Examples of SUSPEND RELEASE . . . . . . . . . . . . . . . . . . . . . . 8-205

VARY CHANNEL Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . 8-205Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-205Examples of VARY CHANNEL . . . . . . . . . . . . . . . . . . . . . . . . 8-206

VARY DEVICE Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-207Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-207Examples of VARY DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . 8-210


Subcommands

The SVAA subcommands can be issued in a variety of ways. Those referred to as“subcommands of SIBBATCH or SIBADMIN” can be executed both interactively andthrough batch processing. The “System Operator commands” are available to theoperator at the OS/390 system console. Many commands and subcommands fallinto both categories.

Subcommands of SIBBATCH and SIBADMIN

You can issue SVAA subcommands through both SIBADMIN and SIBBATCH. Thisenables you to configure the SVA subsystem from TSO or from an OS/390 batch job.

The general form of SVAA subcommands is shown in the following diagram (theconventions used in the syntax diagrams in this book are explained on page xiv):

��──subcommand──(──parameter──(──values──)──)──destination───────────────────────────��

where:

subcommand is a subcommand described in this chapter.

parameter is the name of a parameter described in this chapter. (More thanone parameter, together with its values, can be included in thesubcommand.)

values is one or more of the acceptable values for the specifiedparameter.

destination is a destination for the output of this particular subcommand tooverride the destination currently in effect for all SVAAsubcommands. For more information, see “RedirectingSubcommand Output” on page 8-10.

Note: You can include a destination for output at the end of anySVAA subcommand. However, because you would generally notuse it, the destination option is not shown in the subcommandsyntax diagrams in this chapter.

Note: You can use the PARM='=PARMLIB=membername' parameter on theSIBADMIN or SIBBATCH command to specify the name of the member to besearched for initialization parameters.

Executing Commands from SIBADMINIn the TSO environment, you can:

� Enter SIBADMIN followed by any SVAA subcommand (press Enter).

� Enter only SIBADMIN and press Enter. This establishes the “SIB” environment;SVAA returns the SIB: prompt, at which you can:

- Enter an SVAA subcommand. SVAA executes the subcommand and againdisplays the SIB: prompt. Enter another subcommand, or

- Enter end to return to the TSO environment.

See “Issuing Subcommands from TSO” on page 3-4 for more detail.


Operator Commands

Executing Commands from SIBBATCHWith SIBBATCH, you can code a set of commands and SVAA subcommands in asequential data set, use a SYSIN DD statement in the appropriate JCL to point to thedata set containing the commands, and then execute the JCL. Alternatively, youcan code the commands in a SYSIN DD * statement and execute the JCL.

You can include comments in sequential data sets following these rules:

1. Enclose comments between matching pairs of /* and */ characters.

2. Comments cannot be nested.

3. Comments can be used only between subcommand keywords and parameters(that is, only where blanks appear in the syntax diagrams in this chapter).

See also “Subcommand Continuation” on page 8-10.

Executing Macros from SIBADMINIn SIBADMIN, you can invoke an SVAA macro to execute a frequently used series ofcommands, which may include SVAA subcommands. Creating a macro eliminatesthe task of entering the commands individually. To execute a macro, either:

� Enter MACRO macroname, where macroname is the name of the file that containsthe macro (see “MACRO Subcommand” on page 8-115)

� If IMPEX is set on, simply enter the name of the macro in the appropriateenvironment

Include comments in an SVAA macro following the rules of the environment.

System Operator Commands

Some of the SVAA subcommands are also available to the OS/390 system operator,enabling the operator to interact with the SVA subsystem from a host console.These “subcommands” are marked “System Operator command” at the beginning oftheir descriptions in this chapter. They fall into two functional groups:

� Commands that display or alter the status of channels and functional devices:

ATTN DEVICE DISPLAY CHANNEL DISPLAY DEVICE DISPLAY NCL VARY CHANNEL VARY DEVICE

The ATTN and VARY subcommands provide the functions performed by thephysical channel and device switches that exist on earlier model direct accessstorage device (DASD) controllers.

� Commands that control SVAA tasks:

SEND DSR SEND SFC SEND SIM SEND SRP SEND VOP START DSR START SFC START SIM


Rules

START SRP START VOP STOP DSR STOP SFC STOP SIM STOP SRP STOP VOP

Specific subcommands control DDSR tasks:

DISPLAY RELEASE RELEASE DYNAMICDATA RELEASE INTERVALDATA RESUME RELEASE START RELEASE STOP RELEASE SUSPEND RELEASE

Note: Eight of the above commands—START DSR, START SIM, START SRP, STARTVOP, STOP DSR, STOP SIM, STOP SRP, and STOP VOP—can be issued only fromthe OS/390 system console; not as subcommands of SIBBATCH or SIBADMIN.

Additional operator subcommands control the Reporter data collection tasks. Seethe SVAA for OS/390 Reporting manual.

You use a modify (F) command to enter SVAA system operator commands. Thesyntax is:

��──F─ ──taskname,command ─────────────────────────────────────────────────────────────��

where taskname is the name of an SVAA started task, and command is one of thesubcommands or commands that are described in this chapter.

Rules for Entering Subcommands and Parameters

Follow these rules when entering SVAA subcommands and their parameters:

� Enter each parameter name only once—SVAA does not allow duplicateparameters.

� Follow each parameter name by the values for that parameter and enclose theset of values in a single pair of parentheses. You must enter a value betweenthe parentheses—for example, DEVPERF() and DEVPERF( ) are not allowed.

� Enter each parameter value only once where multiple values areallowed—SVAA ignores duplicate values.

� Arrange the whole set of parameters in any order.

� Enclose the whole set of parameters within parentheses.

� The SEND subcommands require that the subcommand you are sending (withinthe parentheses) be enclosed in quotes. If the enclosed subcommand alsocontains quotation marks (that is, nested quotation marks), the outer set ofquotes must be different from the inner set. For example: SEND DSR("STOPREL('task123')")

� Optionally, for ease of reading, start each new parameter on a new line (youcan add additional spaces or use new lines anywhere you want).


Rules

CaseYou can enter subcommands and parameters in either uppercase or lowercase, butSVAA treats both as uppercase. The values you enter for certain parametervariables, however, are case sensitive; e.g., “a” and “A” are interpreted as differentcharacters.

Whether uppercase and lowercase characters are actually interpreted differently forcase-sensitive values is determined by the current setting of the SET CASEsubcommand (see “SET CASE” on page 8-160). If you have issued the SETCASE(MIXED) subcommand, case is preserved; that is, uppercase and lowercasecharacters are interpreted differently. However, if SET CASE(UPPER), the default, isin effect, SVAA interprets all lowercase input as uppercase.

The values you assign to SVA subsystem names, site names, channel names,device names, release identifiers, and collection identifiers are all case sensitive. Areminder of this fact appears below the “Values:” line wherever one of theseparameters is described in this chapter.

To ensure that SVAA correctly interprets the lowercase characters you use for acase-sensitive name, regardless of the current setting of the SET CASEsubcommand, enclose the name in matching quotation marks, either single quotesor double quotes. For example: 'subsysA' and "Task123". However, in a SENDsubcommand, which may involve nested sets of quotation marks, use doublequotes for one set and single quotes for the other.

All other parameter values—i.e., those without a note regarding case—are not casesensitive. Such parameters include device addresses and volsers. For example,3A� and 3a� are the same unit address.

Wildcard CharactersWildcard characters (* and ?) provide a way for you to specify multiple values for aparameter without typing all of the values individually. You use wildcard charactersto indicate positions within a parameter value at which legitimate alphanumericcharacters can be substituted according to the following rules:

� The asterisk (*) is the generic wildcard character; it can be replaced by anynumber of alphanumeric characters or special characters that are acceptablefor the specific variable.

You can separate multiple generic wildcard characters by any number ofalphanumeric characters. For example:

VOLUME(�ROLL�)

Any volser containing the character sequence ROLL is included. Examples are:PYROLL and ROLLFW

� The question mark (?) is the specific wildcard character; it can be replaced byexactly one alphanumeric character. For example:

VOLUME(PR?D�) Includes all volumes that start with PR and have a D inthe fourth position.

VOLUME(PR??D�) Includes all volumes that start with PR and have a D inthe fifth position.

Leading zeros are not significant in matching wildcard specification of deviceaddresses. For example, if you specify 3�, in a device address, devices 3�� to


Rules

3FFF, 3�� to 3FF, 3� to 3F, and 3 match that specification. However, if you specify�3� in a device address, only devices 3�� to 3FF, 3� to 3F, and 3 match thatspecification.

RangesA range is a set of sequential values that is defined by the first and last values inthe set. Range specifications must adhere to these rules:

� The two values must be of the same data type but have different values.

� The two values must be separated by a colon.

� Except in ranges of units, the two values must contain the same number ofcharacters. Use leading zeroes if necessary.

� Except in unit ranges, both values must contain at least one numeric (decimal)character and the numerics must be in the same position in each value.(Numerics are not required in unit ranges, so AAA:FFF is a valid range of units.)

� The values can be times, single unit addresses, volume serial numbers, orsubsystem names. However, it is not necessary for all the values to representaddresses, volsers, or units, or names that exist.

For example, you can enter a pair of volume serial numbers (volsers), eachconsisting of 1 to 6 alphanumeric characters, such as:

P��1:P��9

� Except in time ranges, the first value must be less than the second.

� Elements in a range cannot contain wildcard characters.

� Multiple ranges within the same parameter must be separated by spaces.

� In time and date ranges, multiple ranges cannot overlap.

� Between two values, only the right-most numeric sequences can differ. Allother characters must match.

Note: In ranges of volsers or device names, hexadecimal “digits” are notconsidered to be numeric. For example, SYS��:SYS�FF is not a valid range. Also,SYS��9:SYS�15 is a valid range, but does not include SYS��A through SYS��F.

Examples of valid ranges:

Range Volsers DefinedA��B�:A��B8 A��B�, A��B1, ... , A��B8A3B2C5:A3B2C7 A3B2C5, A3B2C6, A3B2C72VM31C:2VM49C 2VM31C, 2VM32C, 2VM33C, ... 2VM49C��5:��9 ��5 to ��9�5:12 �5 to 12

Examples of invalid ranges:

Range Reason InvalidA2�B3�:A29B3� The varying sequence (20 ... 29) is not the right-most

numeric sequence.A2�B1:A2�B99 The elements have differing numbers of digits.SYS1A:SYSA2 The numerics are not in the same position and the

non-numeric portions do not match.


Redirecting Output

ListsA list consists of two or more parameter values or ranges separated by spaces.The entire list must be enclosed in parentheses. For example:

SUBSYS(SUBSYS1 SUBSYS3:SUBSYS6 SUBSYS9)

You can use wildcard characters (* and ?) within lists—if the parameter is one forwhich wildcard characters are allowed. For example:

EXCLUDEVOLUME(ABC�� ABC� TST??s TST5�)

Subcommand ContinuationBecause many of the SVAA subcommands are longer than the typical line or record,you may need to continue a subcommand across several records. The method ofcontinuation depends on the facilities of the execution environment:

� Under REXX in TSO, use the REXX method of continuation.

� Within a REXX EXEC, there is a limitation of 512 characters for a statement.You can overcome the limitation by building your command in a series ofconcatenated clauses.

� In a TSO CLIST, use the CLIST method of continuation.

� In a command at a TSO command prompt, use the TSO continuation.

� The SIBBATCH program uses the same method of continuation as the IDCAMSutility. Except for the last record, each record must have a hyphen or a plussign as the last non-blank character before the right margin to indicatecontinuation of the subcommand. You can place the hyphen or plus sign afterany character (even in the middle of a value) and continue the subcommand onthe next line.

� In TSO sessions, SVAA allows a maximum of 32,763 characters in a commandor subcommand. SVAA truncates longer commands to this limit and issues themessage:

SIB�714S Unexpected system failure of SUBCOMM processing.

The examples in this chapter use hyphens to show continuation.

Redirecting Subcommand Output

SVAA sends the output of SVAA subcommands to the destination specified in themost recent SET DESTINATION subcommand. For any specific subcommand, youcan override this destination by specifying a destination at the end of thesubcommand (as shown on page 8-5).

The syntax for the destination is:

��─ ──┬ ┬────────────────── ────────────────────────────────────────────────────────────�� ├ ┤──OUTMsg(options) ─ └ ┘──OUTFile(options)

where options are any of the subparameters allowed for the OUTFILE or OUTMSGparameters of the SET DESTINATION subcommand (that is, any of filespec,


Subcommand Descriptions

DEFAULT, OFF, TERMINAL, or VARIABLE). See “SET DESTINATION” onpage 8-162 for explanations of these subparameters.

Note: In the TSO environment, follow standard data set naming conventions; thatis, enclose a data set name in quotes if it is fully qualified.

Subcommand Descriptions

The SVAA subcommands are presented in alphabetical order beginning on page8-12. At the beginning of each subcommand description, the subcommand isidentified as a “Subcommand of SIBBATCH or SIBADMIN” or as a “SystemOperator command”—or both.

The description of each subcommand consists of:

� An explanation of the command's purpose� A syntax diagram� Descriptions of all parameters� Examples using the subcommand

Parameter DescriptionsImmediately under each parameter name, the parameter is identified as either“Required”, “Optional”, or “Conditional”. The term Conditional means that theparameter is neither required nor completely optional but that its use is related toother parameters. A parenthetical note explains the conditions for its use.

After a brief description of the parameter's purpose, some or all of the followingtypes of information may appear:

Abbreviation: The uppercase portion of the parameter name as shown in thesyntax box.

Values: A description of valid input, with any restrictions.

Default form: The default form for numeric input—either hexadecimal or decimal.To use the form that is not the default you must include the X or Dprefix. (Sometimes the default form is the only form allowed.)

Default value: The default value, if one exists, or “None,” if there is no default.

Examples: Some valid examples of parameter entries.


ALLOCATE SPARES

ALLOCATE SPARES Subcommand

* Subcommand of SIBBATCH or SIBADMIN

The ALLOCATE SPARES subcommand moves one or more drive modules from theMAT partition to the Spares partition.

Note: To be allocated as a spare, a drive module must be in the MAT partition andin an active state (i.e., it must have a status of M.A).

ALLOCATE SPARES

┌ ┐─ ─────��──ALLOCate SPares──(─ ──SUBSYStem(subsys) ──DriveMODule( ───� ┴─u.t.s─ ) ─)───────────────��

Parameters

SUBSYSTEM (subsys)Required

This parameter specifies the name of the SVA subsystem to which the sparesbelong.

Abbreviation: SUBSYS

Values: subsys is the SVA subsystem name.

Note: If the subsystem name contains lowercase characters andSET CASE(UPPER) is in effect, you must enclose the name inmatching quotes.

Default value: None

Examples: SUBSYSTEM(SUB1)SUBSYS(SUBSYS1)SUBSYS('IBsuba1')

DRIVEMODULE (u.t.s)Required

This parameter designates one or more drive modules to be moved from the MATpartition to the Spares partition.

Abbreviation: DMOD

Values: u.t.s (3 digits separated by periods) identifies a specific drivemodule, where:

u identifies the disk array unit (0 to 3)t identifies the tray (0 to 3)s identifies the slot (0 to 7)

You can use ranges, lists, and wildcard characters.

Default value: None

Examples: DRIVEMODULE(�.1.4)DMOD(1.2.2 1.2.7 1.3.?)DMOD(�.�)


ALTER CHANNEL

Examples of ALLOCATE SPARES Example 1.

ALLOCATE SPARES (- SUBSYS(STKSYS��)- DMOD(1.�) )

All drives with a status of M.A in disk array unit 1 will be moved to the Sparespartition.

Example 2.

ALLOCATE SPARES (- SUBSYS(STKSYS��)- DMOD(�.�.�:�.2.7) )

All drives with a status of M.A in slots 0.0.0 to 0.2.7 will be moved to the Sparespartition.

Example 3.

ALLOCATE SPARES (- SUBSYS(STKSYS��)-

DMOD(�.1.3 �.1.5 �.2.? �.3.?) )

All drives with a status of M.A in the following slots will be moved to the Sparespartition: slots 0.1.3, 0.1.5, and all slots in trays 0.2 and 0.3.

ALTER CHANNEL Subcommand


The ALTER CHANNEL subcommand alters the characteristics of a channel interface.The characteristics the subcommand can alter depend on the channel type:

� For a parallel (bus and tag cables) channel, you can alter one or more of sixcharacteristics.

� For an ESCON or FICON channel, you can change only the channel interfacename. To alter any other characteristics of an ESCON or FICON channel, youmust use the LOP or the DOP. (Disabling the channel does not apply—ESCONand FICON channels cannot be enabled or disabled.)

� For a SCSI or fibre channel I/O interface, you can change only the interfacename.

Note: You cannot alter the characteristics of a channel interface that is used by aPPRC pair.


ALTER CHANNEL

Parallel Channel: Syntax and Subcommand UsageALTER CHANNEL (Parallel Channel)

┌ ┐─ ───��──ALTer CHANnel──(─ ──SUBSYStem(subsys) ──InterFaceID( ───� ┴─c.i─ ) ──────────────────────�

┌ ┐─ ──────────────────────────────────�─ ───� ┴┬ ┬──ADDRessRange(addrrange) ───────── ────────────────────────────────────────────�

├ ┤──BaseADDRess(baseaddr) ───────────├ ┤──BaseFunctionalDeviceID(basefdid)

├ ┤──┬ ┬─ENAble── ───────────────────── │ │└ ┘─DISable─ │ │┌ ┐─ ──────

├ ┤──NaMe( ───� ┴─chname─ ) ──────────────└ ┘ ─ ─SPEED( ──┬ ┬─3.�─ ) ────────────────

└ ┘─4.5─

�─ ──┬ ┬────────────────────────────────────────────────────── ─)───────────────────────�� │ │┌ ┐─ ────────────────────────────────── └ ┘─VERify──(─ ───� ┴┬ ┬──ADDRessRange(addrrange) ───────── ─)─


├ ┤──┬ ┬─ENAble── ───────────────────── │ │└ ┘─DISable─ │ │┌ ┐─ ──────

├ ┤──NaMe( ───� ┴─chname─ ) ──────────────└ ┘ ─ ─SPEED( ──┬ ┬─3.�─ ) ────────────────

└ ┘─4.5─

Note: Before issuing this subcommand for a parallel channel, you must vary thechannel offline to all hosts.

The channel interface must be disabled before you can alter channel interfacecharacteristics. You can use the subcommand's ENABLE | DISABLE parameter toensure that this is handled properly. Whether the ENABLE | DISABLE parameter isprocessed first or last depends upon the existing status of the channel interface.To illustrate, here are two ways to use the parameter:

� Issue the subcommand, including the parameters to be changed, together withthe DISABLE parameter.

SVAA first processes the DISABLE parameter and then alters the channelinterface characteristics as specified.

� If you believe the channel is already disabled (by the operator or a previoussubcommand), issue the subcommand with the parameters to be changed, theENABLE parameter, and VERIFY(DISABLE).

SVAA first processes the VERIFY(DISABLE) parameter. If it verifies that thechannel interface is disabled, SVAA alters the channel interface characteristicsas specified and then processes the ENABLE parameter.

See Examples 1 and 2 on page 8-19 for examples of parallel channelsubcommand syntax.


ALTER CHANNEL

ESCON or FICON Channel: Syntax and Subcommand UsageALTER CHANNEL (ESCON or FICON Channel)

┌ ┐─ ─── ┌ ┐─ ──────��──ALTer CHANnel──(─ ──SUBSYStem(subsys) ──InterFaceID( ───� ┴─c.i─ ) ──NaMe( ───� ┴─chname─ ) ──�

�─ ──┬ ┬────────────────────────────────────────────────────── ─)───────────────────────�� │ │┌ ┐─ ────────────────────────────────── └ ┘─VERify──(─ ───� ┴┬ ┬──ADDRessRange(addrrange) ───────── ─)─


├ ┤──┬ ┬─ENAble── ───────────────────── │ │└ ┘─DISable─ │ │┌ ┐─ ──────

└ ┘──NaMe( ───� ┴─chname─ ) ──────────────

For an ESCON or FICON channel, you can change only the channel interfacename (with the NAME parameter). To alter any other characteristics of an ESCONor FICON channel, you must use the LOP or the DOP.

See Example 3 on page 8-20 for an example of ESCON channel subcommandsyntax. See Example 4 on page 8-20 for an example of FICON channelsubcommand syntax.

SCSI Bus or Fibre Channel: Syntax and Subcommand UsageALTER CHANNEL (SCSI or Fibre Channel)

┌ ┐─ ─── ┌ ┐─ ──────��──ALTer CHANnel──(─ ──SUBSYStem(subsys) ──InterFaceID( ───� ┴─c.i─ ) ──NaMe( ───� ┴─chname─ ) ──�

�─ ──┬ ┬──────────────────────────────────────── ─)─────────────────────────────────────�� │ │┌ ┐─ ──────────────────── └ ┘ ─VERify──(─ ───� ┴┬ ┬──┬ ┬─ENAble── ─────── ─)─ │ │└ ┘─DISable─ │ │┌ ┐─ ──────

└ ┘──NaMe( ───� ┴─chname─ )

For a SCSI bus or a fibre channel, you can change only the interface name (withthe NAME parameter).

Parameters


This parameter specifies the name of the SVA subsystem to which the channelinterface is attached.




Default value: None

Examples: SUBSYSTEM(SUB1)SUBSYS(SUBSYS1)


ALTER CHANNEL

INTERFACEID (c.i)Required

This parameter specifies one or more (up to 32) channel interfaces of the SVAsubsystem.

Abbreviation: IFID

Values: c.i (2 alphanumeric characters separated by a period) specifies achannel interface, where:

c identifies one of the two clusters (0 or 1) in the subsystemi is the interface ID (A through P) associated with a specific

cluster

You can use ranges and lists, but not wildcard characters.

Default value: None

Examples: INTERFACEID(�.A) (interface A on cluster 0)IFID(�.A:�.J) (interfaces A to J on cluster 0)IFID(�.P) (interface P on cluster 0)

ADDRESSRANGE (addrrange)For a parallel channel: This is one of a group of six parameters of which youmust enter at least one: ADDRR, BADDR, BFDID, ENA | DIS, NM, and SPEED.

For an ESCON or FICON channel: This parameter is not allowed. Address rangefor an ESCON or FICON channel can be changed only at the LOP or the DOP.

For a SCSI or fibre channel: This parameter is not allowed.

This parameter defines the range of addresses to be trapped by the channelinterface.

Abbreviation: ADDRR

Values: addrrange is one of the values in the Address Range columns inTable 8-1 on page 8-17.

Default form: Decimal (hexadecimal values require the X prefix)

Default value: None

Examples: ADDRR(128) (decimal 128)ADDRR(D'128') (decimal 128)ADDRR(X'8�') (decimal 128)


ALTER CHANNEL

Table 8-1. Valid configuration entries for a parallel channel

Address Range Base Address and BFDID values

(hex) (dec) (hexadecimal) (decimal)

8 8 00 08 10 18 20 28 30 38 4048 50 58 60 68 70 78 80 8890 98 A0 A8 B0 B8 C0 C8D0 D8 E0 E8 F0 F8

00 08 16 24 32 40 48 56 64 7280 88 96 104 112 120 128 136144 152 160 168 176 184 192200 208 216 224 232 240 248

10 16 00 10 20 30 40 50 60 70 8090 A0 B0 C0 D0 E0 F0

00 16 32 48 64 80 96 112 128144 160 176 192 208 224 240

20 32 00 20 40 60 80 A0 C0 E0 00 32 64 96 128 160 192 224

40 64 00 40 80 C0 00 64 128 192

80 128 00 80 00 128

100 256 00 00

BASEADDRESS (baseaddr)For a parallel channel: This is one of a group of six parameters of which youmust enter at least one: ADDRR, BADDR, BFDID, ENA | DIS, NM, and SPEED.

For an ESCON or FICON channel: This parameter is not allowed. Base addressfor an ESCON or FICON channel can be changed only at the LOP or the DOP.

For a SCSI or fibre channel: This parameter is not allowed. (Base address doesnot apply to these channel types.)

This parameter defines the base address to be trapped by the channel interface.

Abbreviation: BADDR

Values: baseaddr is one of the “Base Address and BFDID values” shown inTable 8-1.

Default form: Hexadecimal (decimal values require the D prefix)

Default value: None

Examples: BADDR(4�) (decimal 64)BADDR(X'4�') (decimal 64)BADDR(D'64') (decimal 64)

BASEFUNCTIONALDEVICEID (basefdid)For a parallel channel: This is one of a group of six parameters of which youmust enter at least one: ADDRR, BADDR, BFDID, ENA | DIS, NM, and SPEED.

For an ESCON or FICON channel: This parameter is not allowed. The base FDIDfor an ESCON or FICON channel can be changed only at the LOP or the DOP.

For a SCSI or fibre channel: This parameter is not allowed. (Base FDID does notapply to these channel types.)

This parameter identifies the base FDID for the channel interface.

Abbreviation: BFDID

Values: basefdid is one of the “Base Address and BFDID values” shown inTable 8-1.



ALTER CHANNEL

Default value: None

Examples: BFDID(4�) (decimal 64)BFDID(X'4�') (decimal 64)BFDID(D'64') (decimal 64)

ENABLE | DISABLEFor a parallel channel: This is one of a group of six parameters of which youmust enter at least one: ADDRR, BADDR, BFDID, ENA | DIS, NM, and SPEED.

For an ESCON, FICON, SCSI, or fibre channel: This parameter is not allowed.(These channel types cannot be enabled or disabled.)

This parameter enables or disables the channel interface. The channel interfacemust be disabled before you can alter channel characteristics (see the discussion atthe beginning of the ALTER CHANNEL description).

Abbreviation: ENA or DIS

Default value: None

NAME (chname)For a parallel channel: This is one of a group of six parameters of which youmust enter at least one: ADDRR, BADDR, BFDID, ENA | DIS, NM, and SPEED.

For an ESCON, FICON, SCSI, or fibre channel: You must enter this parameter;the channel (or I/O) interface name is the only characteristic you can alter for thesechannel types.

This parameter specifies the names to be assigned to the channel or I/O interfaces.

Abbreviation: NM

Values: chname is a name for a channel or I/O interface. You can enter 1to 8 characters or a null string. The following characters areaccepted, even as the first character: a to z, A to Z, 0 to 9, $,@, #, -, _, +, &, ., / A null string, entered as NAME('') orNAME(""), sets the name to all blanks.

Note: If SET CASE(UPPER) is in effect, and you use lowercasecharacters in a channel name and don't want them converted touppercase, you must enclose the name in matching quotes.


Notes:

1. When specifying a range, both names must contain at leastone numeric (decimal) character, which must be in theright-most position in each name (as in the third examplebelow).

2. In a range specification, hexadecimal “alphabetic digits” (A-F)are not recognized as numeric. See the rules and examplesfor specifying ranges (beginning on page 8-9).

Default value: None

Examples: NM('1stCHAN')NM(SYBSYS1)NM(CHAN��:CHAN1�)


ALTER CHANNEL

SPEED (3.0 | 4.5)For a parallel channel: This is one of a group of six parameters of which youmust enter at least one: ADDRR, BADDR, BFDID, ENA | DIS, NM, and SPEED.

For an ESCON, FICON, SCSI, or fibre channel: This parameter is not allowed.(The speed for these channel types cannot be altered.)

This parameter sets the channel's data transfer speed in megabytes/second.

Note: A speed must be set before a parallel channel interface can be enabled.

Values: 3.� or 4.5

Default value: None

VERIFY (subparameters)(Optional)

This parameter provides a way for you to insure that you are modifying the correctchannel/interface and characteristics. Enter one or more of the followingsubparameters, together with what you expect its current value to be.

ADDRR (addrrange) (not allowed for a SCSI or fibre interface)BADDR (baseaddr) (not allowed for a SCSI or fibre interface)BFDID (basefdid) (not allowed for a SCSI or fibre interface)ENA | DIS

NM (chname)SPEED (3.0 | 4.5) (not allowed for a SCSI or fibre interface)

The VERIFY parameter compares the value you specify to the actual currentchannel or I/O interface value. If all subparameter values you enter match thecurrent channel or I/O interface values, the ALTER continues. However, if theVERIFY fails, the ALTER CHANNEL subcommand is rejected.

Abbreviation: VER

Default value: None

Examples of ALTER CHANNEL Example 1. Parallel channel

ALTER CHANNEL (- SUBSYS(SVASUB�1)- IFID(�.A:�.H)- NM(CHAN�1:CHAN�8)- DIS- SPEED(4.5)- ADDRR(256)- BADDR(��)- BFDID(��)-

VER(NM(CH1:CH8) SPEED(3.�)) )

On SVA subsystem SVASUB�1, this subcommand selects channel interfaces A to Hon cluster � to be altered. With the VERIFY parameter present, it verifies that thecurrent channel names for the specified IFIDs are CH1 through CH8 and that the datatransfer speed for all eight channels is currently set to 3.�. If the VERIFY issuccessful, the DIS parameter disables the channel interfaces. It then renames thechannels CHAN�1 through CHAN�8. For all eight channels, it sets the data transferspeed to 4.5, sets the address range to 256, and sets the base address and baseFDID to ��.


ALTER DEVICE

Example 2. Parallel channel

ALT CHAN (- SUBSYS('sub�2')- IFID(1.A)- ENA- SPEED(3.�)- ADDRR(64)- BADDR(4�)- BFDID(4�)- VER(DIS) )

On SVA subsystem sub�2, this subcommand selects channel interface A on cluster1. It verifies that the channel interface is disabled and, if so, sets the data transferspeed to 3.�, sets the address range to 64, and sets the base address and baseFDID to 4�. Finally, it enables the channel interface.

Example 3. ESCON channel

ALTER CHANNEL (- SUBSYS(SVASYS�1)- IFID(�.I:�.L)- NM(ESCON�1:ESCON�4) )

On SVA subsystem SVASYS�1, this subcommand selects channel interfaces Ithrough L on cluster � and changes the names of those channels to ESCON�1through ESCON�4.

Example 4. FICON channel

ALTER CHANNEL (- SUBSYS(SVASYS�4)- IFID(�.I:�.L)- NM(FICON�1:FICON�4) )

On SVA subsystem SVASYS�4, this subcommand selects channel interfaces Ithrough L on cluster � and changes the names of those channels to FICON�1through FICON�4.

ALTER DEVICE Subcommand


The ALTER DEVICE subcommand changes the definition of one or more SVAfunctional devices. It has no defaults. Any parameter not specified retains itscurrent setting.

Notes:

1. You cannot alter a device's FDID, device type, PAV type (Base/Alias), orpartition. Instead, you must delete the device and then redefine it with the newcharacteristics. First, however, you must back up the data stored on thedevice—if you want to retain that data. Once you have redefined the device,you can restore the data. One exception: you can change the partition for alldrive modules in the Test partition with the MOVE TESTPARTITIONsubcommand.

If changing the device type or PAV type of a device, make sure that the changeis consistent with the device definitions in HCD.


ALTER DEVICE

2. You cannot alter the characteristics of a device that is part of a PPRC pair.

3. You cannot alter the PRIVILEGEDECAM, SCSIENABLE, or SCSIREADWRITEvalues for Power PPRC Bridge devices. Also, you cannot specify a value forthe SCSIADDRESS parameter for Power PPRC Bridge devices.

4. You cannot alter the CACHE, CKDENABLE, CKDREADWRITE, DASDFASTWRITE,NAME, or PRIVILEGEDECAM values for PAV Alias devices.

5. If an Alias device is reassigned to a different Base device, both must be definedwithin the same Virtual Control Unit (VCU); crossing VCU boundaries is notallowed.

6. The device type (3380 or 3390) of an Alias device must always match that of itsrelated Base device. This requirement does not prevent an Alias from beingreassigned to a Base device with a larger or smaller capacity, but it doesprevent any attempt to reassign an Alias of one device type to a Base of adifferent device type. For example, a 3380-J Alias cannot be reassigned to a3390-9 Base, but a 3390-9 Alias can be reassigned to a 3390-3 Base.

7. You should not use the ALTER DEVICE subcommand or the ISPF panels tomanually reassign PAV Base and Alias relationships for dynamically managedPAV devices (WLMPAV=YES in the HCD definition) since WLM will probablyoverride your reassignment with its own. If you want to manually manage yourPAV Base and Alias relationships, you will need to change your HCD definitionsto redefine your PAV devices as statically managed (WLMPAV=NO in the HCDdefinition). Refer to IBM's MVS Planning: Workload Management and HCDPlanning for more information.


ALTER DEVICE

ALTER DEVICE

┌ ┐─ ────��──ALTer DEVice──(─ ──SUBSYStem(subsys) ──┬ ┬──FunctionalDeviceID( ───� ┴─fdid─ ) ───────────� │ │┌ ┐─ ──────

└ ┘──UNIT( ───� ┴─device─ ) ────────────

┌ ┐─ ──────────────────────────────────────────�─ ───� ┴┬ ┬ ─ ─CACHE( ──┬ ┬─ENAble── ) ──────────────────── ────────────────────────────────────� │ │└ ┘─DISable─

├ ┤ ─ ─CKDENAble( ──┬ ┬─YES─ ) ──────────────────── │ │└ ┘─NO──

├ ┤──CKDReadWrite( ──┬ ┬─YES─ ) ───────────────── │ │└ ┘─NO──

├ ┤──DasdFastWrite( ──┬ ┬─ENAble── ) ──────────── │ │└ ┘─DISable─ │ │┌ ┐─ ───────

├ ┤──NaMe( ───� ┴─dvcname─ ) ───────────────────── │ │┌ ┐─ ─────────

├ ┤──PAVBase( ───� ┴─base_fdid─ ) ────────────────├ ┤──PRIViLeGedecam( ──┬ ┬─YES─ ) ───────────────

│ │└ ┘─NO── │ │┌ ┐─ ─────────────────

├ ┤──SCSIADDRess( ──┬ ┬───� ┴─domain.target.lun─ ) │ │└ ┘─DISable───────────────

├ ┤──SCSIENAble( ──┬ ┬─YES─ ) ─────────────────── │ │└ ┘─NO──

└ ┘──SCSIReadWrite( ──┬ ┬─YES─ ) ──────────────── └ ┘─NO──

�─ ──┬ ┬────────────────────────────────────────────────────────── ─)───────────────────�� │ │┌ ┐─ ────────────────────────────────────── │ ││ │┌ ┐─ ── └ ┘─VERify──(─ ───� ┴┬ ┬──FunctionalDeviceID( ───� ┴fdid ) ──────── ─)─

├ ┤──DEViceTYPe(dvctype) ─────────────────├ ┤──CACHE( ──┬ ┬─ENAble── ) ────────────────

│ │└ ┘─DISable─├ ┤──CKDENAble( ──┬ ┬─YES─ ) ────────────────

│ │└ ┘─NO──├ ┤──CKDReadWrite( ──┬ ┬─YES─ ) ─────────────

│ │└ ┘─NO──├ ┤──DasdFastWrite( ──┬ ┬─ENAble── ) ────────

│ │└ ┘─DISable─ │ │┌ ┐─ ───────

├ ┤──NaMe( ───� ┴─dvcname─ ) ─────────────────├ ┤──PARTition( ──┬ ┬─PRODuction─ ) ─────────

│ │└ ┘─TEST─────── │ │┌ ┐─ ─────────

├ ┤──PAVBase( ───� ┴─base_fdid─ ) ────────────├ ┤──PRIViLeGedecam( ──┬ ┬─YES─ ) ───────────

│ │└ ┘─NO── │ │┌ ┐─ ─────────────────

├ ┤──SCSIADDRess( ───� ┴─domain.target.lun─ )├ ┤──SCSIENAble( ──┬ ┬─YES─ ) ───────────────

│ │└ ┘─NO──└ ┘──SCSIReadWrite( ──┬ ┬─YES─ ) ────────────

└ ┘─NO──

Parameters


This parameter specifies the name of the SVA subsystem with which the functionaldevice is associated.





ALTER DEVICE

Default value: None

Examples: SUBSYSTEM(ICESUB�1)SUBSYS(SUBSYS_1)SUBSYS('subabc')

FUNCTIONALDEVICEID (fdid)Conditional (To identify the device, you must enter either this parameter or theUNIT parameter—not both.)

This parameter specifies devices by their SVA functional device identifiers (FDIDs).

Abbreviation: FDID

Values: fdid is a functional device identifier: 1 to 3 hexadecimal digits or 1to 4 decimal digits. See the table on page 1-2 for ranges of FDIDvalues by subsystem type.



Examples: FDID(4�) (decimal 64)FDID(X'4�') (decimal 64)FDID(D'64') (decimal 64)FDID(1� 12 2F) (decimal 16, 18, and 47)FDID(D'64':D'127') (decimal 64 through 127)

UNIT (device)Conditional (To identify the device, you must enter either this parameter or theFDID parameter—not both. However, if the device is not defined to the hostoperating system in which SVAA is running, you must use FDID.)

This parameter specifies devices as they are defined to the host in which SVAA isrunning.

Values: device is a host device number: 1 to 4 hexadecimal digits.

Decimal representation (D prefix) is not accepted.


Default form: Hexadecimal

Examples: UNIT(�234)UNIT(X'�234')UNIT(222:233)UNIT(2�� 3��)

CACHE (ENA | DIS)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter specifies whether caching for the device is to be enabled ordisabled. The CACHE parameter setting has no effect on V2Xf operations orperformance. If CACHE is specified, a warning message is issued as a reminder,but the subcommand is not rejected.

When cache is disabled, caching is still turned on, but the caching algorithm ischanged. In a write operation, tracks are queued for immediate destaging to the


ALTER DEVICE

arrays instead of being held in cache. In a read operation, a track is staged tocache and then queued for deallocation from cache as soon as the read iscomplete. You cannot alter this value for PAV Alias devices.

Values: ENA or DIS

Default value: None

Example: CACHE(DIS)

CKDENABLE (YES | NO)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter enables or disables host access to the CKD functional device.

Notes:

1. You must vary the device offline to all hosts before you disable the device(CKDENA(NO)) with this parameter.

2. You cannot alter this value for PAV Alias devices.

Abbreviation: CKDENA

Values: YES or NO

Default value: None

Example: CKDENA(YES)

CKDREADWRITE (YES | NO)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter specifies whether to allow write access to the CKD functional device.YES allows writes; NO allows no writes. You cannot alter this value for PAV Aliasdevices.

Abbreviation: CKDRW

Values: YES or NO

Default value: None

Example: CKDRW(NO)

DASDFASTWRITE (ENA | DIS)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter only provides 3990 compatibility; its setting has no effect on SVAoperations or performance. You cannot alter this value for PAV Alias devices. IfDASDFASTWRITE is specified for a V2Xf subsystem, a warning message is issuedas a reminder, but the subcommand is not rejected.

Abbreviation: DFW

Values: ENA or DIS


ALTER DEVICE

Default value: None

Example: DFW(DIS)

NAME (dvcname)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter specifies the names to be assigned to the devices identified by theFDID or UNIT parameter. You cannot alter this value for PAV Alias devices.

Abbreviation: NM

Values: dvcname is a name for a functional device. You can enter 1 to 8characters or a null string. The following characters are accepted,even as the first character: a to z, A to Z, 0 to 9, $, @, #, -,_, +, &, ., / A null string, entered as NAME('') or NAME(""), setsthe name to all blanks.



Notes:



Default value: None

Examples: NAME(PAYROLL)NM('financ��')NM(EMPLFIL1:EMPLFIL4)NM(PROJ71 PROJ112 PROJ149)NM("")

PAVBASE (base_fdid)Optional for Alias devices; invalid for Base devices

This parameter specifies the Base device to which this Alias is to be re-assigned.PAVBASE cannot specify an Alias device.

An Alias device can be reassigned to a different Base device either automatically bythe Workload Manager (WLM) component of an OS/390 or z/OS operating system,or manually by using the ALTER DEVICE subcommand. An Alias must be assignedto a Base device when the Alias is intially defined.

To reassign an Alias device to a different Base device using the ALTER DEVICEsubcommand, specify the FDID of the new Base (which must previously exist andcan be online or offline) in the PAVBASE parameter of the subcommand. To verifythe current PAV relationship before reassigning the Alias, add the VERIFYparameter and specify the FDID of the old Base in the PAVBASE sub-parameter.


ALTER DEVICE

You should not use the ALTER DEVICE subcommand or the ISPF panels tomanually reassign PAV Base and Alias relationships for dynamically managed PAVdevices (WLMPAV=YES in the HCD definition) since WLM will probably overrideyour reassignment with its own. If you want to manually manage your PAV Baseand Alias relationships, you will need to change your HCD definitions to redefineyour PAV devices as statically managed (WLMPAV=NO in the HCD definition).Refer to IBM's MVS Planning: Workload Management and HCD Planning for moreinformation.

Abbreviation: PAVB

Values: base_fdid is the same as a functional device identifier: 1 to 3hexadecimal digits (0 to FFF).

Ranges, lists, and wildcard characters cannot be used

Default value: None

Example: PAVB(411)

PRIVILEGEDECAM (YES | NO)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter specifies whether the functional device is eligible for use as thetransmission path for Category 1-restricted SVAA Extended Control and Monitoring(ECAM) messages to the SVA subsystem.

Note: For PRIVLG(YES) to take effect, the device must also be designated anECAM device with the SET ECAMDEVICE subcommand (see page 8-164 for details).

You can specify NO for most devices—to limit the number of privileged ECAMdevices—but you must specify PRIVLG(YES) for at least one device.

Note: You cannot specify PRIVLG(YES) for Power PPRC Bridge devices. Youcannot alter this value for PAV Alias devices

Abbreviation: PRIVLG

Values: YES or NO

Default value: None

Example: PRIVLG(YES)

SCSIADDRESS (domain.target.lun | DISable)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter either assigns or removes the SCSI address identifier for afunctional device. Entering a SCSI address (in the form of domain.target.lun)assigns it to the device. Entering DISable removes the current SCSI addressassignment from the device.

Note: You cannot specify a SCSIADDRESS for Power PPRC Bridge devices.

Abbreviation: SCSIADDR


ALTER DEVICE

Values: domain.target.lun or DISable

domain.target.lun (3 decimal numbers separated by periods)specifies a SCSI address, where:

domain is the logical domain address (1 to 2 decimal digits)target is the SCSI target identifier (1 to 2 decimal digits)lun is the logical unit number (LUN) for the SCSI physical

device (1 to 3 decimal digits)

Default value: None

Examples: SCSIADDRESS(�.8.15)SCSIADDR(1.�3.�3 �.�7.12)SCSIADDR(DIS)

SCSIENABLE (YES | NO)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter enables or disables host access to the SCSI functional device.

Note: You cannot specify SCSIENABLE(YES) for Power PPRC Bridge devices.

Abbreviation: SCSIENA

Values: YES or NO

Default value: None

Example: SCSIENA(NO)

SCSIREADWRITE (YES | NO)Conditional (This is one of a group of nine parameters of which you must enter atleast one: CACHE, CKDENA, CKDRW, DFW, NM, PRIVLG, SCSIADDR, SCSIEN, andSCSIRW.)

This parameter specifies whether write access to the SCSI functional device is to beallowed. YES allows writes; NO allows no writes.

Note: You cannot specify SCSIREADWRITE(YES) for Power PPRC Bridge devices.

Abbreviation: SCSIRW

Values: YES or NO

Default value: None

Example: SCSIRW(YES)

VERIFY (subparameters)Optional

This parameter provides a way for you to insure that you are modifying the correctdevices and values. Enter one or more of the following subparameters, togetherwith what you expect its current value to be.

FDID (fdid) DEVTYP (dvctype)

CACHE (ENA | DIS)CKDENA (YES | NO)CKDRW (YES | NO)


ALTER DEVICE

DFW (ENA | DIS) NM (dvcname)

PART (PROD | TEST) PAVB (base_fdid)

PRIVLG (YES | NO)SCSIADDR (domain.target.lun | DIS)SCSIEN (YES | NO)SCSIRW (YES | NO)

Notes:

1. To use VERIFY FDID you must specify the devices in the subcommand with theUNIT parameter (see example below).

2. You can verify the current DEVICETYPE and PARTITION for the devices,although you cannot alter these values with the ALTER DEVICE subcommand.

The VERIFY parameter compares the values you specify to the actual currentvalues for the device. If all subparameter values you enter match the currentvalues, the ALTER continues. However, if the VERIFY fails, the ALTER DEVICEsubcommand is rejected.

Abbreviation: VER

Default value: None

Examples of ALTER DEVICE Example 1.

ALTER DEVICE (- SUBSYS(SVASYS�2)- FDID(D'128':D'137' D'139')- CKDRW(YES) )

This subcommand allows write access to CKD functional devices 128 through 137and also 139 in SVA subsystem SVASYS�2.

Example 2.

ALT DEV (- SUBSYS('svasub1')- UNIT(22B)- PRIVLG(YES)-

VER(FDID(2B) PRIVLG(NO)) )

This subcommand first verifies that functional device 2B in SVA subsystem svasub1is defined to the host system as unit �22B and is not currently defined as aprivileged ECAM device. If the VERIFY succeeds, the subcommand redefinesfunctional device 2B as a privileged ECAM device.


ALTER SUBSYSTEM

Example 3.

ALT DEV (- SUBSYS(SVASUBA)- UNIT(22A:22F)- NM(SPECS�1:SPECS�6)- VER(FDID(2A:2F)) )

This subcommand first verifies that functional devices 2A through 2F in subsystemSVASUBA are defined to the host system as units �22A through �22F. If the VERIFYsucceeds, the subcommand names the devices SPECS�1 through SPECS�6.

Example 4.

ALT DEV (- SUBSYS(SVASUB3)- FDID(7FF)- PAVB(7�1)- VER(PAVB(7��)) )

On SVA subsystem SVASUB3 this subcommand verifies that functional device 7FF asan Alias device that is currently related to functional device 7��, a Base device. Ifverification is successful, Alias 7FF is reassigned to functional device 7�1, apreviously-existing Base device.

ALTER SUBSYSTEM Subcommand


The ALTER SUBSYSTEM subcommand enables you to:

� Change (only on the 9393 or 9500 SVA) the array-size setting for thesubsystem: 5+2 or 13+2. The only array size available on the V2Xf, V2X orV960 SVA is 13+2.

� Change an existing SVA subsystem name� Change your site name� Enable service information messages (SIMs) for SCSI devices� Assign subsystem IDs (SSIDs) for emulated 3990 controllers� Designate the total number of concurrent PPRC pair synchronizations

Notes:

1. Two individual parameters (SSIDBASE and VCUSSID) and a group of parameters(SSID0 through SSID3) are available for assigning SSIDs. These parameters aremutually exclusive; you can use only one method—either SSIDBASE, VCUSSID,or the SSID0 through SSID3 group.

2. You cannot redefine an SSID on a subsystem on which PPRC is enabled. Youmust first have your hardware support representative disable PPRC capabilityfor the subsystem. After you have redefined the SSID, PPRC can be re-enabledfor the subsystem.


ALTER SUBSYSTEM

ALTER SUBSYSTEM

┌ ┐─ ────────────────────────��──ALTer SUBSYStem──(─ ──SUBSYStem(subsys) ───� ┴┬ ┬──ARraYSIze( ──┬ ┬─5+2── ) ─ ──────────────� │ │└ ┘─13+2─

├ ┤──NEWNaMe(newsubsys) ────├ ┤──SCSISIM( ──┬ ┬─ENAble── )

│ │└ ┘─DISable─├ ┤──SITE(sitename) ────────├ ┤─┤ ssid(s) ├────────────└ ┘──COPYLim(limit) ────────

�─ ──┬ ┬──────────────────────────────────────────── ─)─────────────────────────────────�� │ │┌ ┐─ ──────────────────────── └ ┘─VERify──(─ ───� ┴┬ ┬──ARraYSIze( ──┬ ┬─5+2── ) ─ ─)─ │ │└ ┘─13+2─

├ ┤──COPYLim(limit) ────────├ ┤──SCSISIM( ──┬ ┬─ENAble── )

│ │└ ┘─DISable─├ ┤──SITE(sitename) ────────└ ┘─┤ ssid(s) ├────────────

ssid(s):├─ ──┬ ┬──SSIDBASE(ssid) ───────── ───────────────────────────────────────────────────────┤ │ │┌ ┐─ ────────

├ ┤──VCUSSID( ───� ┴─vcu.ssid─ ) │ │┌ ┐─ ──────────────

└ ┘───� ┴┬ ┬──SSID�(ssid�) ─────├ ┤──SSID1(ssid1)├ ┤──SSID2(ssid2)└ ┘──SSID3(ssid3)

ParametersIn addition to the SUBSYSTEM parameter, you must enter at least one of: ARYSI,NEWNM, SCSISIM, SITE, SSIDBASE, VCUSSID, SSID0, SSID1, SSID2, or SSID3.


This parameter specifies the existing name for the SVA subsystem.




Default value: None

Examples: SUBSYS(ICESYS2)SUBSYS('icesuba1')

ARRAYSIZE (5+2 | 13+2)Optional

This parameter specifies the number of drive modules to be used in forming a newarray (user data drives + redundancy data drives). This does not affect existingarrays.

Abbreviation: ARYSI

Values: 5+2 or 13+2

New arrays will have a drive module capacity equivalent to the firstvalue plus the second value—for example, 5+2 indicates acapacity equivalent to 5 user data drives and 2 redundancy drives.


ALTER SUBSYSTEM

Note: You can form a 5+2 array only on the 9393 or 9500SVA—not on earlier subsystems or on the V2X or V960 SVA.

Default value: None

Example: ARYSI(13+2)

COPYLIM (limit)Optional

This parameter specifies the total number of concurrent PPRC pair synchronzationsper SVA subsystem. The total includes the number of pairs being established withMODE(COPY) as well as the number of formerly suspended pairs beingre-established with MODE(RESYNC).

Abbreviation: COPYL

Values: limit is the total number of concurrent PPRC pair synchronzationsper SVA subsystem: 1 to 2 decimal digits from 0 to 32.

A value of 0 allows the SVA subsystem to limit synchronization toup to four PPRC pairs established between a primary andsecondary subsystem.

A non-zero value specifies the number of background copysessions allowed to execute concurrently while synchronizingprimary and secondary device pairs.

You cannot use ranges, lists, or wildcard characters.

Note: Changes to COPYLIM do not necessarily take effectimmediately. If the value of COPYLIM is increased, newsynchronizations are immediately added up to the new value.However, if the value is decreased, current synchronizations arenot immediately removed. As pairs complete synchronization, thetotal number of synchronizations is gradually reduced down to thenew value.

Default value: 0

Examples: COPYLIM(4)COPYL(4)

NEWNAME (newsubsys)Optional

This parameter specifies the new name to be assigned to the SVA subsystem.

Note: Within your site, each SVA subsystem name must be unique.

Abbreviation: NEWNM

Values: newsubsys is a new subsystem name, 1 to 8 characters long. Thefollowing characters are accepted, even as the first character: a toz, A to Z, 0 to 9, $, @, #, -, _, +, &, ., /

Note: If SET CASE(UPPER) is in effect, and you use lowercasecharacters in the name and don't want them converted touppercase, you must enclose the name in matching quotes.

Default value: None


ALTER SUBSYSTEM

Examples: NEWNAME(1SUBSYS)NEWNM(SUBSYS_2)NEWNM('subsys1')

SCSISIM (ENAble | DISable)Optional

This parameter specifies whether service information messages (SIMs) from SCSIdevices are to be enabled or disabled.

Values: ENA or DIS

Default value: None

Example: SCSISIM(ENA)

SITE (sitename)Optional

You can use this parameter to identify your company, organization, or location.Use this name when you call StorageTek Software Support

Values: sitename is a name of your choosing. You can enter 1 to 8characters or a null string. The following characters are accepted,even as the first character: a to z, A to Z, 0 to 9, $, @, #, -,_, +, &, ., / A null string, entered as SITE('') or SITE(""), setsthe name to all blanks.

Note: If SET CASE(UPPER) is in effect, and you use lowercasecharacters in the site name and don't want them converted touppercase, you must enclose the name in matching quotes.

Default value: None

Examples: SITE(“AcmeBank”)SITE(REMOTE1)

SSIDBASE (ssid)Optional If you enter this parameter, you cannot use the VCUSSID parameter orthe SSID0 through SSID3 parameters.

This parameter enables you to assign SSIDs to all virtual control units (VCUs) in thesubsystem by entering one SSID—for VCU 0 (the “base” SSID). Consecutivehexadecimal SSIDs are assigned to all VCUs in ascending order, beginning with thebase SSID.

Notes:

1. This parameter changes any existing SSIDs that are different from the sequenceof SSIDs defined by the SSIDBASE value.

2. You must assign a unique SSID to each VCU in your installation.

3. The actual number of SSIDs is governed by the maximum number of virtualcontrol units supported by the subsystem (see “Functional Differences betweenSubsystems” on page 1-2).



ALTER SUBSYSTEM

Values: 4 hexadecimal digits ranging from 0001 to FFFC.

You cannot use ranges or wildcard characters.

Note: The SSID value specified must not allow the last SSID toexceed FFFF. For example, on a subsystem that supports 16SSIDs, FFF0 is the highest valid entry for SSIDBASE.


Default value: None

Example: SSIDBASE(��F�)

VCUSSID (vcu.ssid ... )Optional If you enter this parameter, you cannot use the SSIDBASE parameter orthe SSID0 through SSID3 parameters.

Each SSID (subsystem identifier) is used to identify a different VCU (a 3990controller emulated by the SVA subsystem). This parameter enables you to assignSSIDs to one or more VCUs individually.

Notes:


2. The actual number of SSIDs is governed by the maximum number of virtualcontrol units supported by the subsystem (see “Functional Differences betweenSubsystems” on page 1-2).


Values: Each vcu.ssid entry assigns an SSID to a VCU, where:

vcu is a 1- or 2-digit (decimal) virtual control unit number.ssid is a unique 4-digit (hexadecimal) subsystem identifier

ranging from 0001 to FFFF.

You cannot use ranges or wildcard characters.

Default value: None

Examples: VCUSSID(�.��1�)VCUSSID(13.��F1 14.��F2 5.��E5)

SSID0 through SSID3 (ssid0 through ssid3)Optional If you enter any of these four parameters, you cannot use the SSIDBASEor VCUSSID parameter.

Note: The VCUSSID and SSIDBASE parameters are replacements for the SSID0,SSID1, SSID2 and SSID3 parameters. Therefore, SSID0, SSID1, SSID2 and SSID3 willbe removed from this document with the next release of SVAA.

Each SSID (subsystem identifier) is used to identify a different VCU (a 3990controller emulated by the SVA subsystem).


ALTER SUBSYSTEM

Notes:



Values: ssid� through ssid3 are unique, four-digit (hexadecimal)subsystem identifiers ranging from 0001 to FFFF.


Default value: None

Examples: SSID�(��F�)SSID1(X'��F1')


This parameter provides a way for you to insure that you are modifying the correctsubsystem value. The VERIFY parameter compares the values you specify to theactual current values for the SVA subsystem. If all subparameter values you entermatch the current values, the ALTER continues. However, if the VERIFY fails, theALTER SUBSYSTEM subcommand is rejected.

Enter one or more of the following subparameters (exceptions: see Notes below),together with what you expect its current value to be.

ARYSI (5+2 | 13+2) COPYLIM (limit)

SCSISIM (ENA | DIS) SITE (sitename) SSIDBASE (ssid)

VCUSSID (vcu.ssid ... ) SSID0 (ssid0) SSID1 (ssid1) SSID2 (ssid2) SSID3 (ssid3)

Notes:

1. The three forms of specifying SSIDs are mutually exclusive. You can entereither SSIDBASE or VCUSSID, or one or more of SSID0 through SSID3.

2. There must be match between the SSID-related subparameters (SSIDBASE,VCUSSID, SSID0, SSID1, SSID2, or SSID3) you specify in the VERIFY parameter,and the SSID-related parameters you specify in the non-VERIFY portion of theALTER SUBSYSTEM subcommand.

To illustrate, here are some correct and incorrect examples.

Correct examples:

ALT SUBSYS (SUBSYS(XYZ) SSIDBASE(4��) VERIFY(SSIDBASE(5��) ) )ALT SUBSYS (SUBSYS(XYZ) VCUSSID(�.1��) VERIFY(VCUSSID(�.2��) ) )ALT SUBSYS (SUBSYS(XYZ) SSID1(1��) SSID3(3��)-

VERIFY(SSID1(4��) SSID3(6��) ) )


ALTER SUBSYSTEM

Incorrect examples:

ALT SUBSYS (SUBSYS(XYZ) SSIDBASE(4��) VERIFY(VCUSSID(1.5��) ) )ALT SUBSYS (SUBSYS(XYZ) VCUSSID(�.1��) VERIFY(SSID2(2��) ) )ALT SUBSYS (SUBSYS(XYZ) SSID1(1��) SSID3(3��) VERIFY(SSIDBASE(9��) ) )ALT SUBSYS (SUBSYS(XYZ) SSID1(1��) VERIFY(SSID3(3��) ) )

Abbreviation: VER

Default value: None

Examples: VERIFY(ARYSI(13+2) )VER(SSIDBASE(��1�) )

Examples of ALTER SUBSYSTEM Example 1.

ALTER SUBSYSTEM (- SUBSYSTEM(IBSUB�1)- ARRAYSIZE(13+2)- SSIDBASE(�4��) )

For SVA subsystem IBSUB�1, this subcommand sets the array size for thesubsystem to 13+2 (newly formed arrays will have a capacity equivalent to 13 userdata drives and 2 redundancy data drives). SSIDs are assigned to all VCUs(emulated 3990 controllers) in the subsystem beginning with �4�� for VCU 0.

Example 2.

ALT SUBSYS (-VER(SITE('MainHQ') ARYSI(13+2) )-

SUBSYS(SUBSYSA1)- ARYSI(5+2)- NEWNM(ICESUBA1) )

This subcommand first verifies that, for SVA subsystem SUBSYSA1, the site name isdefined as MainHQ and that the current ARRAYSIZE setting for the subsystem is13+2. If the VERIFY succeeds, the subcommand renames the subsystem ICESUBA1and sets the array size for the subsystem to 5+2.


ATTN DEVICE

ATTN DEVICE Subcommand

* Subcommand of SIBBATCH or SIBADMIN* System Operator command

The ATTN DEVICE subcommand initiates a state-change interrupt for specificfunctional devices. State-change interrupts are sent to the interface in each pathgroup and all interfaces without path groups formed which are associated with adevice. If the host operating system misses a “device end” from the SVAsubsystem and experiences a hang condition, you can issue this subcommand inan attempt to free the condition. You cannot send attention interrupts to PAV Aliasdevices.

ATTN DEVICE

┌ ┐─ ────��──Attn DEVice──(─ ──SUBSYStem(subsys) ──┬ ┬──FunctionaDeviceID( ───� ┴─fdid─ ) ─)──────────�� │ │┌ ┐─ ──────

└ ┘──UNIT( ───� ┴─device─ ) ───────────

Parameters


This parameter specifies the name of the SVA subsystem with which the functionaldevice is associated.




Default value: None

Examples: SUBSYSTEM('icesubA')SUBSYS(SUBSYS1)


This parameter specifies devices by their SVA FDIDs.

Abbreviation: FDID




Examples: FDID(4�) (decimal 64)FDID(D'64') (decimal 64)FDID(21 22 2D) (decimal 33, 34, and 45)FDID(1�:12) (decimal 16 through 18)


ATTN DEVICE







Examples: UNIT(234)UNIT(X'�234')UNIT(222:233)UNIT(2�� 3��)

Examples of ATTN DEVICE Example 1.

ATTN DEVICE (- SUBSYSTEM(ICESUB1)- UNIT(123) )

This subcommand initiates a state-change interrupt for all interfaces associated withthe functional device (in subsystem ICESUB1) that is defined to the host as unit 123.

Example 2.

A DEV (- SUBSYS('subsysA')-

FDID(21 23 A1:A4) )

This subcommand initiates a state-change interrupt for all interfaces associated withfunctional devices 21, 23, and A1 through A4 in subsystem subsysA.


DEFINE DEVICE

DEFINE DEVICE Subcommand


The DEFINE DEVICE subcommand defines the characteristics of a functional device.You can define up to 4096 devices in a V2X SVA, but only 1024 in earlier SVAsubsystems. (These numbers are lower if any 3390-9 devices are defined.)

Notes:

1. In VM, a newly defined device may have an operating system status of BOXED.To gain access to a boxed device, you may have to vary it offline and thenonline again. (The VM BOXED status can also affect OS/390 operations whenOS/390 is running under VM.)

2. Once you have defined a device, you cannot alter its device type, FDID, PAVtype (Base/Alias), or partition. Instead, you must delete the device and thenredefine it with the new characteristics. If changing the device type or PAVtype, make sure that the change is consistent with the device definitions inHCD.

Important!

Always keep your V2Xf Base and Alias device definitions consistent withyour HCD.

It is extremely important to always keep your V2Xf Base and Alias devicedefinitions your HCD definitions. See “PAV Configuration Considerations” onpage 2-17 for more information.

3. A PAV Base device must be defined before any of its related Alias devices canbe defined. You cannot define a Base and its related Alias devices in a singledefine operation.

4. A Base device is not required to have any related Alias devices. However, ifthe Base device does have aliases, all Alias devices must be defined within thesame Virtual Control Unit (VCU); crossing VCU boundaries is not allowed.Since a VCU has a maximum of 256 devices, a single Base device can bedefined with up to 255 Aliases, or 128 Base devices can be defined with oneAlias each, etc.

5. Initialization of an Alias device during the device definition process is notallowed.

6. When defining an Alias device, any specified values for the CACHE,CKDENABLE, CKDREADWRITE, DASDFASTWRITE, and PRIVILEGEDECAMparameters are ignored. The values of the related Base device are insteadimplicitly assigned to the Alias.

7. The NAME parameter cannot be specified when defining an Alias device.


DEFINE DEVICE

DEFINE DEVICE

┌ ┐─ ────��──DEFine DEVice──(─ ──SUBSYStem(subsys) ──FunctionalDeviceID( ───� ┴─fdid─ ) ──────────────�

�─ ──DEViceTYPe(dvctype) ──┬ ┬────────────────────── ──┬ ┬────────────────────── ───────────� │ │┌ ┐─ENAble── │ │┌ ┐─YES─

└ ┘──CACHE( ──┴ ┴─DISable─ ) └ ┘──CKDENAble( ──┴ ┴─NO── )

�─ ──┬ ┬───────────────────────── ──┬ ┬────────────────────────────── ─────────────────────� │ │┌ ┐─YES─ │ │┌ ┐─ENAble──

└ ┘──CKDReadWrite( ──┴ ┴─NO── ) └ ┘──DasdFastWrite( ──┴ ┴─DISable─ )

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────────────────────────────────── ────�└ ┘──DevCYLS(cylinders) │ │┌ ┐─ ────── ┌ ┐─ ──────

└ ┘──INITialize(UNIT( ───� ┴─device─ )VOLume( ───� ┴─volser─ ))

�─ ──┬ ┬───────────────────── ──┬ ┬───────────────────────────── ──────────────────────────� │ │┌ ┐─ ─────── │ │┌ ┐─PRODuction─

└ ┘──NaMe( ───� ┴─dvcname─ ) └ ┘──PARTition( ──┴ ┴─TEST─────── )

�─ ──┬ ┬──────────────────── ──┬ ┬─────────────────────────── ─────────────────────────────�└ ┘──PAVBase(base_fdid) │ │┌ ┐─NO──

└ ┘──PRIViLeGedecam( ──┴ ┴─YES─ )

�─ ──┬ ┬────────────────────────────────────── ──┬ ┬──────────────────────────── ──────────� │ │┌ ┐─ ───────────────── │ │┌ ┐─512───

└ ┘──SCSIADDRess( ───� ┴─domain.target.lun─ ) └ ┘──SCSIBLocKSIze( ──┼ ┼─2�48── ) ├ ┤─4�96── ├ ┤─8192── └ ┘─16384─

�─ ──┬ ┬─────────────────────── ──┬ ┬────────────────────────── ───────────────────────────� │ │┌ ┐─NO── │ │┌ ┐─NO──

└ ┘──SCSIENAble( ──┴ ┴─YES─ ) └ ┘──SCSIReadWrite( ──┴ ┴─YES─ )

�─ ──┬ ┬─────────────────────── ──┬ ┬───────────────────────── ─)─────────────────────────�� │ │┌ ┐─NO── │ │┌ ┐─NO──

└ ┘──DATAbridge( ──┴ ┴─YES─ ) └ ┘──STATUSbridge( ──┴ ┴─YES─ )

Parameters


This parameter specifies the name of the SVA subsystem for the devices to bedefined.




Default value: None

Examples: SUBSYSTEM(SUB1)SUBSYS(SUBSYS1)SUBSYS('icebox1')

FUNCTIONALDEVICEID (fdid)Required

This parameter specifies the functional device identifiers (FDIDs) of the devices tobe defined.

Abbreviation: FDID



DEFINE DEVICE

FDID can be a range or list of Base devices, a range or list of Aliasdevices, but cannot be a range or list of Base and Alias devicesintermixed together in a single DEFINE DEVICE subcommand.


Examples: FDID(4�) (decimal 64)FDID(X'4�') (decimal 64)FDID(D'64') (decimal 64)

DEVICETYPE (dvctype)Required

This parameter specifies the type of functional device to be emulated.

Note: The device type (3380 or 3390) of an Alias device must always match thatof its related Base device. This requirement does not prevent an Alias from beingdefined to a Base device with a larger or smaller capacity, but it does prevent anyattempt to define an Alias of one device type to a Base of a different device type.For example, a 3380-J Alias cannot be defined and related to a 3390-9 Base, but a3390-9 Alias can be defined and related to a 3390-3 Base.

Abbreviation: DEVTYP

Values: dvctype identifies the device type and model descriptor andconsists of 5 to 6 alphanumeric characters.

Valid entries are: 338�J, 338�K, 338�KE, 339�1, 339�2, 339�3,339�9, SCSIA (3390-3 with SCSI format), and SCSIB (3390-9 withSCSI format).

Default value: None

Examples: DEVICETYPE(338�J)DEVTYP(339�1)DEVTYP(SCSIA)

CACHE (ENA | DIS)Optional

This parameter specifies whether caching for the functional device is to be enabledor disabled. This parameter setting has no effect on V2Xf operations orperformance. If CACHE is specified, a warning message is issued as a reminder,but the subcommand is not rejected.

When cache is disabled, caching is still turned on, but the caching algorithm ischanged. In a write operation, tracks are queued for immediate destaging to thearrays, instead of being held in cache. In a read operation, a track is staged tocache and then queued for deallocation from cache when the read is complete.

Values: ENA or DIS

Default value: ENA

Example: CACHE(DIS)


DEFINE DEVICE

CKDENABLE (YES | NO)Optional

This parameter enables or disables host access to the CKD functional device.


Values: YES or NO

Default value: YES

Example: CKDENA(NO)

CKDREADWRITE (YES | NO)Optional

This parameter specifies whether to allow write access to the CKD functional device.YES allows writes; NO allows no writes.

Abbreviation: CKDRW

Values: YES or NO

Default value: YES

Example: CKDRW(NO)

DASDFASTWRITE (ENA | DIS)Optional

This parameter only provides 3990 compatibility; its setting has no effect on SVAoperations or performance. This parameter setting has no effect on V2Xfoperations or performance. If DASDFASTWRITE is specified, a warning messageis issued as a reminder, but the subcommand is not rejected.

Abbreviation: DFW

Values: ENA or DIS

Default value: ENA

Example: DFW(DIS)

DATABRIDGE (NO | YES)Optional

This parameter specifies whether the CKD functional device is to be defined as aPower PPRC Data Bridge. NO does not define the device as a Power PPRC DataBridge. YES does define the device as a Power PPRC Data Bridge, and the devicetype must be specified as 33909 in this case.

Abbreviation: DATA

Values: NO or YES

Default value: NO

Example: DATA(YES)


DEFINE DEVICE

DEVCYLS (cylinders)Optional

This parameter specifies the number of cylinders to use when defining a CKDfunctional device as a FlexVolume or as a Large Volume. Use of the DEVCYLSparameter is subject to the following requirements:

� DEVCYLS is supported only on V2X, V2X2, and V2Xf subsystems.

� DEVCYLS cannot be specified with the DATABRIDGE or STATUSBRIDGE,parameters since Large Volumes and FlexVolumes cannot be defined asPPRC Bridge devices.

� DEVCYLS cannot be specified with the PAVBASE parameter. The PAVBASEparameter is used to define Alias devices. Large Volumes and FlexVolumescannot be defined as Alias devices. Even though DEVCYLS cannot bespecified for an Alias device itself, an Alias device can be defined and relatedto a Base device that is a Large Volume or a FlexVolume.

For example, FDID 400 defined as a 3390-9 Large Volume with 32760cylinders and its UCB is genned as a 3390B. FDID 4FF is currently not definedand its UCB is genned as a 3390A. You can define FDID 4FF as a 3390-9Alias device and relate it to FDID 400 as long as you don't specify theDEVCYLS parameter on the DEFINE DEVICE subcommand for FDID 4FF orchange the "Cyls" value on the SIBCA25 ISPF panel, if using ISPF to definethe Alias device.

� DEVCYLS cannot be specified when the DEVICETYPE parameter specifies aSCSI device type (SCSIA or SCSIB) since Large Volumes and FlexVolumescannot be defined as SCSI devices.

� Since SCSI devices are not supported on V2Xf subsystems, DEVCYLS cannotbe specified with the SCSIADDRESS, SCSIBLOCKSIZE, SCSIENABLE, orSCSIREADWRITE parameters on a V2Xf subsystem.

� Large Volumes can only be defined as 3390-9 CKD devices with 32760cylinders, so DEVICETYPE(33909) and DEVCYLS(32760) must be specifiedwhen defining a Large Volume.

� FlexVolumes can be defined as 3380 or 3390 CKD devices subject to thefollowing further requirements:

- DEVICETYPE(33901) or DEVICETYPE(33902) cannot be specified whendefining a FlexVolume in order to maintain compatibility with the IBM 2105ESS

- If DEVICETYPE(3380J) is specified, DEVCYLS must be a value from1-885 cylinders

- If DEVICETYPE(3380KE) is specified, DEVCYLS must be a value from886-1770 cylinders

- If DEVICETYPE(3380K) is specified, DEVCYLS must be a value from1771-2655 cylinders

- If DEVICETYPE(33903) is specified, DEVCYLS must be a value from1-3339 cylinders

- If DEVICETYPE(33909) is specified, DEVCYLS must be a value from3340-10017 cylinders if Large Volume microcode support is not installed orthe subsystem is a V2X or V2X2.


DEFINE DEVICE

- If DEVICETYPE(33909) is specified, DEVCYLS must be a value from3340-32760 cylinders if Large Volume microcode support is installed andthe subsystem is a V2Xf or V2X4f.

Note: A 3390-9 device defined with 32759 cylinders is technically aFlexVolume; a 3390-9 device defined with 32760 cylinders is technically aLarge Volume.

Abbreviation: DCYLS

Values: cylinders specifies the number of cylinders and must be a decimalvalue within the above limits. The absence of the DEVCYLSparameter on a DEFINE DEVICE subcommand implies that thedevice will be defined with the normal (default) number of cylindersfor that device type.

Default value: NO

Example: DCYLS(42)

INITIALIZE (UNIT (device) VOLUME (volser) )Optional

Use this parameter only if you are specifying a DEVICETYPE of SCSIA or SCSIB.

Note: If you are running as an MVS guest under VM, you cannot use thisparameter; there is no path. To initialize the device, you must first define thedevice (with this subcommand), then attach the device to the MVS system underVM, and finally initialize the device with the INITIALIZE DEVICE subcommand.

To initialize SCSI-format devices, this parameter specifies device numbers andvolume serial numbers (volsers) for each SCSIA or SCSIB device you are defining. Ifyou use this parameter, you must supply at least as many device numbers (units)and volsers as the number of FDIDs you are defining in this subcommand.

Abbreviation: INIT

The UNIT and VOLume subparameters are both required.

Values: UNIT(device) specifies one or more host device numbers (eachdevice is 1 to 4 hexadecimal digits).

VOL(volser) specifies one or more volume serial numbers (eachvolser is 6 alphanumeric characters).

You can enter lists and ranges of device numbers and volsers, butcannot use wildcard characters.

Default values: None

Examples: INIT( UNIT(22�) VOL(DATA12) )INIT( UNIT(2D4 2D6 2D7) VOLUME(PROD�2:PROD�4) )INIT( UNIT(3A�:3AD) VOL(FILE�1 FILE�2 FILE�5:FILE16) )

Notes:

1. The values for FDID, UNIT, and VOLUME can be specified in any order. Theorder of the values for one subparameter can be different from the order for theothers.

2. The values for FDID, UNIT, and VOLUME are associated by their relative positionwithin the expanded list of single values, lists of values, and ranges of values.


DEFINE DEVICE

3. If you specify more device numbers (units) and volsers than FDIDs (specifiedwith the FDID parameter), the excess unit and volser numbers are ignored.

NAME (dvcname)Optional

This parameter specifies the names to be assigned to the functional devicesidentified by the FDID parameter.

Abbreviation: NM

Values: dvcname is a name for a functional device. You can enter 1 to 8characters or a null string. The following characters are accepted,even as the first character: a to z, A to Z, 0 to 9, $, @, #, -,_, +, &, ., / A null string, entered as NAME('') or NAME(""), setsthe name to all blanks.



Notes:



Default value: None

Examples: NAME(PAYROLL)NM(PROJ71 PROJ112 PROJ149)NM(FILE��1:FILE��4)NM('myfile')

PARTITION (PRODUCTION | TEST)Optional

This parameter specifies the partition with which the device is to be associated.

Note: You cannot assign a device to the Test partition on the V2X, V960, or9500 SVA—only on subsystems running earlier microcode. See “FunctionalDifferences between Subsystems” on page 1-2 for more information.

Abbreviation: PART

Values: PROD or TEST

Default value: PROD

Example: PART(PROD)


DEFINE DEVICE

PAVBASE (base_fdid)Optional for Base devices; Required for Alias devices

This parameter specifies the Base device to which this Alias is related. PAVBASEcannot specify an Alias device.

To define a Base device, the PAVBASE parameter must not be specified on thedefine request, and the device must not already exist.

To define an Alias device, the PAVBASE parameter must be specified on thedefine request. The related Base device must already exist (it can be online oroffline), and the value of the PAVBASE parameter must specify the FDID of therelated Base.

Note: An Alias device can be reassigned to a different Base device in three ways:

1. automatically by the Workload Manager (WLM) component of a OS/390 orz/OS operating system

2. manually by using the SVAA ALTER DEVICE subcommand

3. manually by using the SVAA DEFINE DEVICE subcommand

Abbreviation: PAVB

Values: base_fdid is the same as a functional device identifier: 1 to 3hexadecimal digits (0 to FFF).

Ranges, lists, and wildcard characters cannot be used.

Default value: None

Example: PAVB(411)

PRIVILEGEDECAM (YES | NO)Optional

This parameter specifies whether the device is eligible for use as the transmissionpath for Category 1-restricted SVAA Extended Control and Monitoring (ECAM)messages to the SVA subsystem.

Note: For PRIVLG(YES) to take effect, the device must also be designated anECAM device with the SET ECAMDEVICE subcommand (see page 8-164 for details).

You can specify NO for most devices—to limit the number of privileged ECAMdevices—but you must specify PRIVLG(YES) for at least one device.

Abbreviation: PRIVLG

Values: YES or NO

Default value: NO

Example: PRIVLG(NO)


DEFINE DEVICE

SCSIADDRESS (domain.target.lun)Optional

This parameter specifies the SCSI address for the functional device.

Abbreviation: SCSIADDR

Values: domain.target.lun (3 decimal numbers separated by periods)specifies a SCSI address, where:

domain is the logical domain address (1 to 2 decimal digits)target is the SCSI target identifier (1 to 2 decimal digits)lun is the logical unit number (LUN) for the SCSI physical

device (1 to 3 decimal digits)

Default value: None

Examples: SCSIADDRESS(�.8.15)SCSIADDR(�1.�3.��3 ��.�7.�12)

SCSIBLOCKSIZE (512 | 2048 | 4096 | 8192 | 16384)Optional

This parameter defines the logical block size for a SCSI device.

Note: This parameter can be entered only if the device type is SCSIA or SCSIB.

Abbreviation: SCSIBLKSI

Values: 512, 2�48, 4�96, 8192, or 16384

Default value: 512

Example: SCSIBLKSI(2�48)

SCSIENABLE (YES | NO)Optional

This parameter enables or disables host access to the SCSI functional device.


Values: YES or NO

Default value: NO

Example: SCSIENA(YES)

SCSIREADWRITE (YES | NO)Optional

This parameter specifies whether write access to the SCSI functional device is to beallowed. YES allows writes; NO allows no writes.


Values: YES or NO

Default value: NO



DEFINE DEVICE

STATUSBRIDGE (NO | YES)Optional

This parameter specifies whether the CKD functional device is to be defined as aPower PPRC Status Bridge. NO does not define the device as a Power PPRCStatus Bridge. YES does define the device as a Power PPRC Status Bridge, andthe device type must be specified as 33903 in this case.

Abbreviation: STATUS

Values: NO or YES

Default value: NO

Example: STATUS(YES)

Examples of DEFINE DEVICE Example 1.

DEFINE DEVICE (- SUBSYS(IBSUB�1)- FDID(D'1':D'255')- DEVTYP(338�K)- NM(ICE��1:ICE255)- CACHE(ENA)- CKDENA- PART(PROD)- PRIVLG(NO) )

On SVA subsystem IBSUB�1, this subcommand defines the devices with FDIDsranging from 1 through 255 (decimal) as 338�K-type devices. It assigns namesranging from ICE��1 to ICE255, and assigns them to the Production partition. Itenables the CKD devices, enables caching for all of the devices, and specifies thatnone of the devices are to be privileged ECAM devices.

Example 2.

DEF DEV (- SUBSYS('subsysa')- FDID(8�)- DEVTYP(338�J)- NM(COMM�2)- CACHE(ENA)- CKDENA- CKDRW(NO) PRIVLG(YES) )

On SVA subsystem subsysa, this subcommand defines functional device 8� as a338�J-type device. It assigns the name COMM�2 to the device, enables it as a CKDdevice, disables write access, enables caching, and designates the device to be aprivileged ECAM device.

Example 3.

DEF DEV (- SUBSYS('subsysa')- FDID(7FF)- DEVTYP(339�3)- PAVB(7��) )


DEFINE DEVICE

On SVA subsystem subsysa, this subcommand defines functional device 7FF as anAlias with a device type of 339�-3. The Alias device is to be related to functionaldevice 7��, a previously-existing Base device.

Example 4.

DEF DEV (- SUBSYS(TEST)- FDID(�55)- DEVTYP(339�3)- DEVCYLS(42) )

On SVA subsystem TEST, this subcommand defines functional device �55 as aFlexVolume that is 42 cylinders in size.

Example 5.

DEF DEV (- SUBSYS(TEST)- FDID(FFF)- DEVTYP(339�9)- DEVCYLS(3276�) )

On SVA subsystem TEST, this subcommand defines functional device FFF as aLarge Volume. The device type must be 339�9 for a Large Volume.


DELETE DEVICE

DELETE DEVICE Subcommand


The DELETE DEVICE subcommand deletes the definition of one or more SVAfunctional devices.

Notes:

1. All data on the device is effectively erased by this subcommand. Therefore,before you delete the device, you must back up any data that you want topreserve or move it to another functional device.

2. You must vary the devices (to be deleted) offline to all hosts before you issuethis subcommand.

Note: PAV Base devices must be varied offline before any related Aliasdevices can be deleted. Also, PAV Alias devices cannot be varied online oroffline.

3. In VM, if the device has an operating system status of BOXED, you may have to(1) vary the device offline to ensure status is OFFLINE, (2) vary it online toreestablish a path, and then (3) vary it offline again. (The VM BOXED statuscan also affect OS/390 operations when OS/390 is running under VM.)

4. You cannot delete a device that is part of a PPRC pair. You must first deletethe pair and then you may delete the device.

5. All PAV Alias devices (for a given Base device) must be deleted before thegiven Base device can be deleted. You cannot delete a Base and all of itsrelated Aliases in a single operation.

6. Although PAV Alias devices can be defined only if the PAV feature is installed,the feature is not required in order to delete PAV Base and Alias devices.

7. Alias devices cannot be deleted from an online Base except for the specialcase when they have been genned as Bases in HCD and misdefined asAliases to the V2Xf. In this special case only, it does not matter whether theBase is online or offline. Since the host operating system did not establish apath group to the Alias when it was misdefined, it can be safely deleted withoutrequiring that the Base device be varied offline.

8. The FORCE parameter is no longer required when deleting an Alias that isrelated to an offline Base device that contains user data.

DELETE DEVICE

┌ ┐─ ────��──DELete DEVice──(─ ──SUBSYStem(subsys) ──┬ ┬──FunctionalDeviceID( ───� ┴─fdid─ ) ──────────� │ │┌ ┐─ ──────

└ ┘──UNIT( ───� ┴─device─ ) ────────────

�─ ──┬ ┬─────── ──┬ ┬──────────────────────────────────────────────────── ─)──────────────�� └ ┘ ─FORCE─ │ │┌ ┐─ ──────────────────────────────── │ ││ │┌ ┐─ ──── └ ┘─VERify──(─ ───� ┴┬ ┬──FunctionalDeviceID( ───� ┴─fdid─ ) ─)─ │ │┌ ┐─ ───────

└ ┘──NaMe( ───� ┴─dvcname─ ) ───────────


DELETE DEVICE

Parameters


This parameter specifies the name of the SVA subsystem containing the devicedefinitions to be deleted.




Default value: None

Examples: SUBSYSTEM(SUB1)SUBSYS(SUBSYS1)SUBSYS(1SUBSYS)


This parameter specifies the devices by their SVA FDIDs.

Abbreviation: FDID




Examples: FDID(4�) (decimal 64)FDID(D'64') (decimal 64)FDID(1�:12) (decimal 16 through 18)FDID(21 22 2D) (decimal 33, 34, and 45)


This parameter specifies the devices as they are defined to the host in which SVAAis running.

Values: device is a host device number: 1 to 4 hexadecimal digits.Decimal representation (D prefix) is not accepted.



Examples: UNIT(�234)UNIT(X'�234')UNIT(222:233)UNIT(2�� 3��)


DELETE DEVICE

FORCEOptional

This parameter indicates that a specified functional device is to be deleted eventhough it contains user data.

Notes:

1. You can use the FORCE parameter only for batch processing—not whenentering the subcommand interactively. Furthermore, you should use thisparameter in a batch file only after careful consideration (you cannot recoverthe data from a deleted device).

2. If user data exists on the device to be deleted, a message informs you of thefact and prompts you to enter FORCE if you still want to delete the device. Thismessage and prompt is no longer issued when deleting an Alias that is relatedto an offline Base device that contains user data.

You must have authorization to use the FORCE parameter. The kind ofauthorization depends upon whether the functional device is defined to the host(GENed); that is, whether the device is part of the host's current I/O configurationand is accessible to I/O requests.

Notes:

1. A device might be part of the a host's current I/O configuration, yet not mappedin SVAA's device mapping tables. This condition occurs when devices aremade available (but not varied online) to the MVS system that is running SVAA,after SVAA has been initialized.

For example, if you configure channels online with the MVS CONFIGcommand, or attach devices to a MVS guest system from VM, and thesedevices were not accessible at the time the SVAA subsystem was initialized,SVAA has no knowledge of these devices and considers them as not defined tothe host it is running on. If you attempt to delete one of these devices, thedelete may fail with a SIB1164E message indicating that you have insufficientauthority to access the subsystem.

In that case, you will need to either establish the proper security definitions(listed below and in SVAA for OS/390 Installation, Customization, andMaintenance) or refresh SVAA's knowledge of such devices (see RefreshingSVAA Feature or Device Mapping Status on MVS in Chapter 2).

2. If the device is defined to the host and the volser and VTOC can be accessed,you need RACF DASDVOL class ALTER authority for the device's volser.

3. If the DASDVOL class is not active on this host operating system, before youattempt to delete the device you must either: 1) disable the device (use theALTER DEVICE command and the CKDENA(NO) parameter), 2) vary all pathsoffline to the device on this host operating system, or 3) implement theSIBIOATX user exit, otherwise the delete will fail with a SIB1164E messageindicating that you have insufficient authority to access the subsystem.

4. If the device is not defined to the host, or is disabled, or the volser cannot beobtained, the VTOC cannot be checked for data sets and a more general classof authorization is required; you must have RACF FACILITY class ALTERauthority for the generalized resource IXFP.FORCE.DELETE.FUNC.DEV.Since Alias devices are always considered to not be defined to the host, thedeletion of Aliases will always use the RACF FACILITY class and the


DELETE DEVICE

generalized resource IXFP.FORCE.DELETE.FUNC.DEV profile for securitychecking.

5. See the SVAA for OS/390 Installation, Customization, and Maintenance manualfor information about defining security resources.


This parameter provides a way for you to insure that you are deleting the correctdevice. Enter one or both of the following subparameters.

FDID (fdid) NM (dvcname)

Note: To use VERIFY FDID, you must use the UNIT parameter to specify thedevices in the subcommand itself (see Example 1. below).

The VERIFY parameter compares the FDID you specify to the unit number definedto the host operating system. If these parameters identify the same device, theDELETE continues. However, if the VERIFY fails, the DELETE DEVICE subcommandis rejected.

Abbreviation: VER

Default value: None

Examples of DELETE DEVICE Example 1. (Batch processing)

DELETE DEVICE (- SUBSYS(SVASYS)- UNIT(�22B)- FORCE- VER(FDID(2B)) )

This subcommand specifies that the functional device identified to the host systemas unit �22B is to be deleted. If functional device 2B in SVA subsystem SVASYS isverified as being the same device as unit �22B, the delete request proceeds. If thedevice contains data, the FORCE parameter allows the data to be deleted. (TheFORCE parameter can be used only in batch processing.)

Example 2.

DEL DEV (- SUBSYS('svasub1')- FDID(A�:A3) )

This subcommand deletes the functional devices with FDIDs ranging from A�through A3 in SVA subsystem svasub1. (It specifies no verification; the devices areidentified only by FDID.)


DISPLAY CHANNEL

DISPLAY CHANNEL Subcommand


The DISPLAY CHANNEL subcommand displays the current channel interface status.

DISPLAY CHANNEL

┌ ┐─ ────── ┌ ┐─ ───��──Display CHANnel──(─ ──SUBSYStem( ───� ┴─subsys─ ) ──InterFaceID( ───� ┴─c.i─ ) ─)───────────��

Parameters


This parameter specifies the names of the SVA subsystems for which the channelinterface is installed.



Note: If a subsystem name contains lowercase characters andSET CASE(UPPER) is in effect, you must enclose the name inmatching quotes.


Default value: None

Examples: SUBSYSTEM(�)SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(SUBSYS1:SUBSYS5)



Abbreviation: IFID



cluster


Default value: None

Examples: INTERFACEID(�.A) (channel A on cluster 0)IFID(�.A:�.J) (channels A to J on cluster 0)IFID(�.�) (all channels on cluster 0)IFID(�.�) (all channels on clusters 0 and 1)IFID(�.C) (channel C on clusters 0 and 1)IFID(�) (all channels)


DISPLAY CHANNEL

Examples of DISPLAY CHANNEL Example 1.

� �F SVAA,D CHAN(SUBSYS(LUNAR) IFID(�,�))

SIB�561I -SUBSYS- IFID STAT TYPE BASE RANGE FDID DOMAIN IDENTIFIER SIB�562I LUNAR �.A ENAB ESCON �� 1�24 �� SIB�562I LUNAR �.C ENAB ESCON �� 1�24 ��SIB�562I LUNAR �.E ENAB FIBRE �2 5��1�4F��411882SIB�562I LUNAR �.G ENAB FIBRE �3 5��1�4F��411883SIB�562I LUNAR �.I ENAB SCSI � �� 1 534E5241��6SIB�562I LUNAR �.K ENAB SCSI 23 �1 ��7 47534241��81SIB�565I �� END OF DISPLAY ��

� �

Figure 8-1. Example of Display Channel subcommand (OS/390 master console). ADISPLAY CHANNEL subcommand was issued using the wildcard character “*” todisplay all interfaces associated with subsystem LUNAR. The TYPE field showsthe type of channel supported by each interface—in this case two ESCON, twofibre, and two SCSI channels.

Example 2.

� �F SVAA,D CHAN(SUBSYS(MAZUMA) IFID(�))

SIB�561I -SUBSYS- IFID STAT TYPE BASE RANGE FDID DOMAIN IDENTIFIERSIB�562I MAZUMA �.A ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA �.B ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA �.C ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA �.D ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA 1.A ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA 1.B ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA 1.C ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�562I MAZUMA 1.D ENAB FICON �� 4�96 �� 5��1�4F��6FDDD�SIB�565I �� END OF DISPLAY ��

� �

Figure 8-2. Example of Display Channel subcommand (OS/390 master console). ADISPLAY CHANNEL subcommand was issued using the wildcard character “*” todisplay all channels and all interfaces associated with subsystem MAZUMA. TheTYPE field shows the type of channel supported—in this case eight FICONchannels.


DISPLAY DEVICE

DISPLAY DEVICE Subcommand


The DISPLAY DEVICE subcommand displays the current status of one or morefunctional devices.

DISPLAY DEVICE

┌ ┐─ ────── ┌ ┐─ ────��──Display DEVice──(─ ──SUBSYStem( ───� ┴─subsys─ ) ──┬ ┬──FunctionaDeviceID( ───� ┴─fdid─ ) ────� │ │┌ ┐─ ──────

├ ┤──UNIT( ───� ┴─device─ ) ─────────── │ │┌ ┐─ ──────

└ ┘──VOLume( ───� ┴─volser─ ) ─────────

�─ ──┬ ┬───── ──┬ ┬─────── ─)─────────────────────────────────────────────────────────────�� └ ┘ ─PAV─ └ ┘ ─QUIET─

Parameters


This parameter specifies the SVA subsystem with which the device is associated.





Default value: None

Examples: SUBSYSTEM(�)SUBSYS(ICESUB1 ICESUB2)SUBSYS(SUBSYS1:SUBSYS5)SUBSYS('icesub')

FUNCTIONALDEVICEID (fdid)Conditional (This is one of a group of three parameters of which you must enterone and only one: FDID, UNIT, or VOL.)

This parameter specifies devices by their SVA functional device identifiers (FDIDs).

Abbreviation: FDID





DISPLAY DEVICE

Examples: FunctionalDeviceID(4�) (decimal 64)FDID(D'64') (decimal 64)FDID(1 22 35)FDID(1�:12)

PAVOptional

This parameter displays the FDIDs of the Aliases currently related to a Base device.Ranges, lists, and wildcard characters can be used in the FDID, UNIT, andVOLUME parameters to display the relationships for multiple Base devices.

Values: None


Default value: None

Example: PAV

QUIETOptional

This parameter reduces the amount of generated output by suppressing errormessages for non-existent devices. Messages SIB0675E, SIB0676E, andSIB0677E are suppressed for FDID, UNIT, and VOLUME inquiries respectively.

Note: When FDID(*), UNIT(*), or VOLUME(*) are specified, the addition of theQUIET parameter makes no difference.

Values: None


Default value: None

Example: QUIET

UNIT (device)Conditional (This is one of a group of three parameters of which you must enterone and only one: FDID, UNIT, or VOL. However, if the devices are not defined tothe host operating system in which SVAA is running, you must use FDID.)


Values: device is a host device number: 1 to 4 hexadecimal digits.Decimal representation (D prefix) is not accepted.



Examples: UNIT(234)UNIT(2�:22 1�� 11�)

VOLUME (volser)Conditional (This is one of a group of three parameters of which you must enterone and only one: FDID, UNIT, or VOL. However, if the devices are not defined tothe host operating system in which SVAA is running, you must use FDID.)


DISPLAY DEVICE

This parameter specifies the volume identifiers for the devices to be displayed.

Abbreviation: VOL

Values: volser is a valid volume serial number.


Default value: None

Examples: VOL(TSTPK1)VOLUME(WKPK)

Examples of DISPLAY DEVICE

� �F SVAA,D DEV(SUBSYS(LUNAR) FDID(�8�))SIB�651I --CKD-- -SCSI-- --SCSI ADDRESS-- PPRCSIB�663I -SUBSYS- UNIT FDID STAT VOLSER R/W ENA R/W ENA DOM TGT LUN INDX STATSIB�664I LUNAR 8� �� Y Y Y N P DSIB�665I �� END OF DISPLAY ��

F SVAA,D DEV(SUBSYS(LUNAR) FDID(�8B:�8F))SIB�651I --CKD-- -SCSI-- --SCSI ADDRESS-- PPRCSIB�663I -SUBSYS- UNIT FDID STAT VOLSER R/W ENA R/W ENA DOM TGT LUN INDX STATSIB�664I LUNAR 8B �� Y N Y N SSIB�664I LUNAR 8C �� Y N Y N DSIB�664I LUNAR 8D �� Y Y N N 1� 1� 1� �SIB�664I LUNAR 8E �� Y Y N N 1� 11 11 �SIB�664I LUNAR 8F �� Y Y N N 11 11 11 �SIB�665I �� END OF DISPLAY ��

� �

Figure 8-3. Example of Display Device subcommand (OS/390 master console). TwoDISPLAY DEVICE subcommands were issued to show status. The firstsubcommand specifies a single volume for display. The second subcommandspecifies a range of functional device IDs (FDIDs), which results in the display offive functional devices.

The PPRC STAT column indicates whether the device is part of a a PPRC pair and/orwhether the device is a Power PPRC Bridge device.

The PPRC pair status is shown in the left side of the column and may take on oneof the following values:

� A blank indicates the device is not part of any PPRC pair.� A P indicates the device is a PPRC Primary.� An S indicates the device is a PPRC Secondary.

The Power PPRC status is shown in the right side of the column and may take onone of the following values:

� A blank indicates the device is not a Power PPRC Bridge device.� A D indicates the device is a Power PPRC Data Bridge.� An S indicates the device is a Power PPRC Status Bridge.


DISPLAY DEVICE

Examples of DISPLAY DEVICE Subcommand and PAV Devices

� �D DEV(SUBSYS(SVASYS) FDID(7��:7�F) PAV QUIET)

FDID UNIT VOLSER ALIAS FDIDs ---- ---- ------ ----- ----------------------------------- 7�� 7F6 7FE 7�1 7�2 7�3 7�4 7�5 7F8 7FA 7FB 7�6 7�7 7�8 7�9�� END OF DISPLAY ��

D DEV(SUBSYS(SVASYS) FDID(7��:7�F) PAV) FDID UNIT VOLSER ALIAS FDIDs ---- ---- ------ ----- ----------------------------------- 7�� 7F6 7FE 7�1 7�2 7�3 7�4 7�5 7F8 7FA 7FB 7�6 7�7 7�8 7�9Subsystem SVASYS FDID 7�A: device does not exist.Subsystem SVASYS FDID 7�B: device does not exist.Subsystem SVASYS FDID 7�C: device does not exist.Subsystem SVASYS FDID 7�D: device does not exist.Subsystem SVASYS FDID 7�E: device does not exist.Subsystem SVASYS FDID 7�F: device does not exist.Device(s) not found or offline for FDID request�� END OF DISPLAY ��

� �

Figure 8-4. Examples of Display Device subcommand for PAV Devices. Two DISPLAY

DEVICE subcommands are issued for PAV devices. The first subcommandspecifies the QUIET parameter to reduce the amount of generated output. Thesecond subcommand does not use the Quiet parameter.


DISPLAY NCL

DISPLAY NCL Subcommand


The DISPLAY NCL subcommand displays net capacity load percentages forspecified subsystems, together with the total capacity in megabytes and collectedfree space in megabytes for each subsystem.

DISPLAY NCAPLODPCT

┌ ┐─ ──────��──Display NCapLodpct──(─ ──SUBSYStem( ───� ┴─subsys─ ) ─)────────────────────────────────��

Parameters


This parameter specifies the names of the SVA subsystems selected.





Default value: None

Examples: SUBSYSTEM(�)SUBSYS(SUBSYS1 SUBSYS2)

Example of DISPLAY NCL

� � F SVAA,D NCL(SUBSYS(�))SIB�654I SVA DISK ARRAY NET-CAPACITY-LOAD% COLL-FREE-SPACE% UNCOLL-FREE-SPACE%SIB�655I SUBSYS CAPACITY(MB) TOT PROD TEST TOT PROD TEST TOT PROD TESTSIB�656I ECCPRD�� 11352�.� 3�.4 3�.4 �.� 68.5 68.5 �.� 1.1 1.1 �.�SIB�656I EVT1 3784�.� 1.8 1.8 �.� 97.9 97.9 �.� �.3 �.3 �.�SIB�656I EVT2 3784�.� 81.2 81.2 �.� 17.4 17.4 �.� 1.4 1.4 �.� SIB�658I �� END OF DISPLAY ��

� �

Figure 8-5. Example of Display NCL subcommand (OS/390 master console). Thesubcommand was issued to display NCL percentages for all availablesubsystems. When issued as an OS/390 operator command, the SIBVOPnnparmlib member specifies the ECAM devices used to communicate the request.Each line has a message number for use by automated operations software.


DISPLAY RELEASE

DISPLAY RELEASE Subcommand


The DISPLAY RELEASE subcommand displays the status of DDSR interval tasks andthe Dynamic DDSR intercept.

DISPLAY RELEASE

��──Display RELease──(─ ──┬ ┬────────────────────────── ──┬ ┬───────── ──┬ ┬──────── ─)─────��└ ┘──RELeaseIDentifier(relid) └ ┘ ─DYNamic─ └ ┘ ─DETail─

Parameters

RELEASEIDENTIFIER (relid)Optional

This parameter specifies the DDSR interval task for which status is to be displayed.

Abbreviation: RELID

Values: relid is a release task identifier defined by the RELEASEINTERVALDATA subcommand.

Note: If the release task identifier contains lowercase charactersand SET CASE(UPPER) is in effect, you must enclose it in matchingquotes.

You can use wildcard characters but not lists or ranges.

Default value: If you specify neither the RELID parameter nor the DYN parameter,the default is to display the status of all DDSR interval tasks andthe Dynamic DDSR intercept.

DYNAMICOptional

This parameter specifies that the status of the Dynamic DDSR intercept is to bedisplayed.

Abbreviation: DYN

Default value: If you specify neither the RELID parameter nor the DYN parameter,the default is to display the status of all DDSR interval tasks andthe Dynamic DDSR intercept.

DETAILOptional

This parameter specifies that the device selection options for the DDSR task are tobe displayed. The options are displayed in order of specificity and matching—not inthe order they were entered in the RELEASE INTERVALDATA or RELEASEDYNAMICDATA subcommand.

Abbreviation: DETL

Default value: None


DISPLAY RELEASE

Examples of DISPLAY RELEASE Example 1.

DISPLAY RELEASE

This subcommand requests the display of the status of all DDSR interval tasks andthe Dynamic DDSR intercept.

Example 2.

DISPLAY RELEASE (- RELEASEIDENTIFIER(1234) )

This subcommand requests the display of the status of DDSR interval task 1234.

Example 3.

D REL (- RELID(TASK345)- DYNAMIC )

This subcommand requests the display of the status of both DDSR interval taskTASK345 and the Dynamic DDSR intercept.

Example 4.

D REL (- RELID('reltask777')- DYN- DETL )

This subcommand requests the display of the status of both DDSR interval taskreltask777 and the Dynamic DDSR intercept. The DETL parameter specifies thatthe device selection options for the DDSR task are to be included in the display.


DROP

DROP Subcommands

The DROP subcommands release devices that are being used by the host operatingsystem to communicate with either an SVA subsystem or a non-SVA subsystem.

DROP ECAMDEVICE* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies devices (as defined to the host) to be dropped from thelist of active ECAM devices.

DROP ECAMDEVICE

┌ ┐─ ────��─ ──DROP ECAMDEVice( ───� ┴device ) ─────────────────────────────────────────────────────��

Abbreviation: DROP ECAMDEV

Values: device is a host device number (1 to 4 hexadecimal digits).


Default value: None

Example: DROP ECAMDEV(2AE 73� 1D)

DROP NONICEBERG* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies devices (as defined to the host) to be dropped from thelist of active non-SVA communication devices (that is, devices over which statisticsare obtained from non-SVA subsystems).

DROP NONICEBERG

┌ ┐─ ────��─ ──DROP NONIceBerg( ───� ┴device ) ─────────────────────────────────────────────────────��

Abbreviation: DROP NONIB



Default value: None

Example: DROP NONIB(72� 1ED)


FORM ARRAY

FORM ARRAY Subcommand


The FORM ARRAY subcommand forms one or more arrays for either the Testpartition or the Production partition.

Note: You cannot form Test arrays on the V2X, V960, or 9500 SVA—only onsubsystems running earlier microcode. See “Functional Differences betweenSubsystems” on page 1-2 for more information.

FORM ARRAY

��──FORM ARraY──(─ ──SUBSYStem(subsys) ──┬ ┬─────────────────────── ──────────────────────�└ ┘──ARraYSIze( ──┬ ┬─5+2── )

└ ┘─13+2─

┌ ┐─PRODuction─�─ ──┬ ┬───────────────────────── ──┼ ┼──────────── ─)────────────────────────────────────�� │ │┌ ┐─ALL─ └ ┘─TEST───────

└ ┘──NUMberARraYS( ──┴ ┴─n─── )

Parameters


This parameter specifies the SVA subsystem in which the array is to be formed.




Default value: None

Example: SUBSYSTEM(SVA1)

ARRAYSIZE (5+2 | 13+2)Optional

This parameter specifies the number of drive modules (user data drives +redundancy data drives) in the array. If you enter this parameter, its valueoverrides the current subsystem array size for this FORM ARRAY operation only.

Note: You can form a 5+2 array only on the 9393 or 9500 SVA.

Abbreviation: ARYSI

Values: 5+2 or 13+2

The arrays formed will have a drive module capacity equivalent tothe first value plus the second value. For example, 13+2 indicatesa capacity equivalent to 13 user data drives and 2 redundancydrives.

Default value: Current subsystem array size value.

Example: ARYSI(13+2)


FORM ARRAY

NUMBERARRAYS (ALL | n)Optional

This parameter specifies the number of arrays to be formed. One Production arraymust be formed at the LOP or the DOP when the subsystem is installed. Therefore,the maximum number of arrays you can form with this subcommand is 7.

Note: You can form 5+2 arrays only on the 9393 or 9500 SVA. On thosesubsystems, you can form up to eight 5+2 arrays, but only four 13+2 arrays. Botharray sizes can exist on one subsystem in the following combinations:

4 13+2 arrays and 0 5+2 arrays3 13+2 arrays and 2 5+2 arrays2 13+2 arrays and 4 5+2 arrays1 13+2 arrays and 6 5+2 arrays0 13+2 arrays and 8 5+2 arrays

Abbreviation: NUMARYS

Values: n (an integer from 1 to 7) specifies the number of arrays to beformed. If the number of spares available is insufficient to form narrays, the subsystem forms as many arrays as possible.

ALL specifies that as many arrays are to be formed as the numberof available spares allows.

For an explanation of the number of spares required to formarrays, see “Forming Additional Arrays” on page 2-3.

Default value: ALL

Examples: NUMARYS(3)

TEST | PRODUCTIONOptional

This parameter specifies the partition to which the new arrays are assigned.

Note: You cannot form Test arrays on the V2X, V960, or 9500 SVA—only onsubsystems running earlier microcode.

Abbreviation: TEST or PROD

Default value: PROD

Examples of FORM ARRAY Example 1.

FORM ARRAY (ARYSI(13+2) SUBSYS('ice��1') PROD)

On SVA subsystem ice��1, this subcommand forms as many 13+2 (15-drive)Production arrays as the available number of spares allows.

Example 2.

FORM ARY (SUBSYS(ICESUBA) NUMARYS(1) PROD)

On SVA subsystem ICESUBA, this subcommand forms one Production array. Thenumber of drive modules in the array is determined by the current array size settingfor the subsystem.


INITIALIZE DEVICE

INITIALIZE DEVICE Subcommand


The INITIALIZE DEVICE subcommand initializes one or more previously definedSCSIA or SCSIB functional devices (FDIDs) with host device numbers (units) andvolume serial numbers (volsers). You cannot initialize PAV Base or Alias devicessince they are defined as CKD devices.

You must supply at least as many device numbers and volsers as the number ofFDIDs specified in this subcommand. If you specify more device numbers andvolsers than FDIDs, the extra device numbers and volsers are ignored.

The values for FDID, UNIT, and VOLUME are associated by their relative positionwithin the expanded list of single values, lists of values, and ranges of values.

Note: If you are running as an MVS guest under VM, you must attach the device tothe MVS system before you can initialize it with this subcommand.

INITIALIZE DEVICE

┌ ┐─ ────��──INITialize DEVice──(─ ──SUBSYStem(subsys) ──FunctionalDeviceID( ───� ┴─fdid─ ) ──────────�

┌ ┐─ ────── ┌ ┐─ ──────�─ ──UNIT( ───� ┴─device─ ) ──VOLume( ───� ┴─volser─ ) ──┬ ┬─────── ──┬ ┬─────────── ─)─────────────�� └ ┘ ─FORCE─ └ ┘ ─NOCONFIRM─

Parameters


This parameter specifies the name of the SVA subsystem containing the SCSIdevices to be initialized.




Default value: None

Example: SUBSYSTEM(SVA��1)

FUNCTIONALDEVICEID (fdid)Required

This parameter specifies the SCSI functional devices to be initialized.

Abbreviation: FDID


You can use lists and ranges but not wildcard characters.



INITIALIZE DEVICE

Examples: FDID(D'64')FDID(21 22 35)FDID(1�:22)

UNIT (device)Required

This parameter specifies the host device numbers of the devices to be initialized.

Values: device specifies one or more host device numbers (each device is1 to 4 hexadecimal digits).


Default value: None

Examples: UNIT(22�)UNIT(3A� 3A5 3AA:3AD)

VOLUME (volser)Required

This parameter specifies the volume serial numbers of the devices to be initialized.

Abbreviation: VOL

Values: volser specifies one or more volume serial numbers, 6alphanumeric characters in length.


Default value: None

Examples: VOLUME(PROD�2:PROD�4)VOL(FILE�1 FILE�2 FILE�5:FILE16)

FORCEOptional

This parameter indicates that the specified functional device is to be initialized evenif it contains a VOL1 record.

Values: (keyword only)

Default value: None

Notes:

1. You can use the FORCE parameter for processing in either the SIBBATCH orSIBADMIN environment.

2. If you include the FORCE parameter in the subcommand, you are prompted witha confirmation message. If you confirm with a Yes, the device will be initialized.In batch, no confirmation message is displayed if you also specify NOCONFIRMin the subcommand.

3. In SIBADMIN, if you omit the FORCE parameter, you are prompted with amessage stating that the volume is already initialized and requesting that youreply either FORCE or CANCEL.

4. No additional security definitions are required to use this parameter.


INITIALIZE DEVICE

NOCONFIRMOptional

This parameter specifies whether a prompt is to be issued during deviceinitialization from batch. NOCONFIRM applies only to batch processing; it is notaccepted when specified from an interactive session.

MVS authorization requires RACF FACILITY class ALTER authority for a newgeneralized resource SVAA.CONFIRM.INIT.FUNC.DEV.


Default value: Confirmation prompt is issued.

Example of INITIALIZE DEVICEINIT DEV (SUBSYS(NEWSVA)-

FDID(24:27 2A 2C) UNIT(3�2:3�9)-VOL(FILE�2 FILE�4 FILE�6:FILE�9) )

This subcommand initializes six SCSI devices (24, 25, 26, 27, 2A, and 2C) withhost device numbers and volsers—in the order they are specified in the UNIT andVOL parameters. In case of the device numbers, 3�2 through 3�7 are assigned, but3�8 and 3�9 are ignored because only six FDIDs are specified.


LISTCFG CHANNEL

LISTCFG CHANNEL Subcommand


The LISTCFG CHANNEL subcommand produces a report on the configuration of oneor more channel interfaces. The destination for the report (the terminal or a file) isdetermined by the OUTFILE parameter of the SET DESTINATION subcommand.

You can redirect the report output to a file (for later printing) by including theredirection option in the subcommand. For more information, see “RedirectingSubcommand Output” on page 8-10.

LISTCFG CHANNEL

┌ ┐─ ────── ┌ ┐─ ───��──LISTCFG CHANnel──(─ ──SUBSYStem( ───� ┴─subsys─ ) ──InterFaceID( ───� ┴─c.i─ ) ─)───────────��

Parameters


This parameter specifies the names of the SVA subsystems for which channelconfiguration reports are to be produced.





Default value: None

Examples: SUBSYSTEM(1SUBSYS)SUBSYSTEM(�)SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(SUBSYS1:SUBSYS4)



Abbreviation: IFID



cluster


Duplicate entries are ignored; each IFID is processed only once.


LISTCFG CHANNEL

Default value: None

Examples: INTERFACEID(�.A) (channel A on cluster 0)IFID(�.A:�.J) (channels A to J on cluster 0)IFID(�.�) (all channels on cluster 0)IFID(�.�) (all channels on clusters 0 and 1)IFID(�.C) (channel C on clusters 0 and 1)IFID(�) (all channels)

Examples of LISTCFG CHANNEL Example 1.

The following subcommand requests a report on all channel interfaces on the SVAsubsystem LUNAR.

LISTCFG CHAN (SUBSYS(LUNAR) IFID(�) )

Here is an example of the report.

REPORT DATE: Mon Apr 24, 2�� 8:22:1� SVA SUBSYSTEM CRLEVEL2 V�1R�1L�� PAGE: 1

CHANNEL CONFIGURATION REPORT (LEVEL 2)

�� SITE NAME = STORTEK � FRAME SERIAL NUMBER = 43��36 �

� SUBSYSTEM NAME = LUNAR � SUBSYSTEM MODEL = 95�� NO. OF CHANNELS = 12 � SITE LOCATION NO. = 22222 �

��

INTERFACE --- CHANNEL INTERFACE --- ----CHANNEL---- BASENAME CLUSTER ID ENABLED TYPE SPEED IDID RANGE FDID

--------- ------- ------- ------- -------- ----- ---- ----- ----ice�� A Y ESCON 2�.� �� 1�24 ��WARTHOG � C Y ESCON 2�.� �� 1�24 ��

1 A Y ESCON 2�.� �� 1�24 ��1 C Y ESCON 2�.� �� 1�24 ��

INTERFACE --- CHANNEL INTERFACE --- ----CHANNEL---- DTL SCSINAME CLUSTER ID ENABLED TYPE SPEED COUNT DOMAIN SCSI IDENTIFIER

--------- ------- ------- ------- -------- ----- ----- ------- ----------------� I Y SCSI 4�.� � �� 534E5241��12

CHAN-�.K � K Y SCSI 4�.� 8 ��1 ��7 47534241��81TEST-1.I 1 I Y SCSI 4�.� �TEST-1.K 1 K Y SCSI 4�.� � �� 4 FFFFFFFFFFFFFFFF

INTERFACE --- CHANNEL INTERFACE --- ----CHANNEL---- SCSI WORLD WIDENAME CLUSTER ID ENABLED TYPE SPEED DOMAIN NODE NAME PORT NAME ADDRESS

--------- ------- ------- ------- -------- ----- ------- ---------------- ---------------- --------� E Y FIBRE 1��.� ��2 5��1�4F��4118A2 5��1�4F��4118AC ��3� G Y FIBRE 1��.� ��3 5��1�4F��4118A3 5��1�4F��4118AC ��3

FIBR_1.E � E Y FIBRE 1��.� ��5 5��1�4F��411885 5��1�4F��41188� ��3� G Y FIBRE 1��.� ��6 5��1�4F��411886 5��1�4F��41188� ��3

Example 2.

The following subcommand requests a report on all channel interfaces on the V2Xfsubsystem MAZUMA which has only FICON channels.

LISTCFG CHAN (SUBSYS(MAZUMA) IFID(�) )



LISTCFG DEVICE

REPORT DATE: Tue Aug 12, 2��3 14:12:36 SVA SUBSYSTEM CRLEVEL2 V�3R�1L�� PAGE: 1



� SUBSYSTEM NAME = MAZUMA � SUBSYSTEM MODEL = V2Xf �� NO. OF CHANNELS = 8 � SITE LOCATION NO. = 22222 �

��

INTERFACE --- CHANNEL INTERFACE --- ----CHANNEL---- BASE WORLD WIDENAME CLUSTER ID ENABLED TYPE SPEED IDID RANGE FDID NODE NAME PORT NAME

--------- ------- ------- ------- -------- ----- ---- ----- ---- ---------------- ----------------� A Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F14C� B Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F14D� C Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F12A� D Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F12B1 A Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F13C1 B Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F13D1 C Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F1441 D Y FICON 1��.� �� 4�96 �� 5��1�4F��6FDDD� 5��1�4F��45F125

Note: The terms appearing in these reports are defined in “Definitions of LISTCFGReport Headings” on page 8-110.

LISTCFG DEVICE Subcommand


The LISTCFG DEVICE subcommand produces a report on functional devices. Thedestination for the report (the terminal or a file) is determined by the OUTFILEparameter of the SET DESTINATION subcommand.


LISTCFG DEVICE

┌ ┐─ALL────────┌ ┐──PARTition( ──┼ ┼─TEST─────── ) ───

┌ ┐─ ────── │ │└ ┘─PRODuction─��──LISTCFG DEVice──(─ ──SUBSYStem( ───� ┴─subsys─ ) ──┼ ┼──────────────────────────────── ───� │ │┌ ┐─ ────

├ ┤──FunctionalDeviceID( ───� ┴─fdid─ ) │ │┌ ┐─ ──────

├ ┤──UNIT( ───� ┴─device─ ) ──────────── │ │┌ ┐─ ──────

└ ┘──VOLume( ───� ┴─volser─ ) ──────────

�─ ──┬ ┬─────── ─)──────────────────────────────────────────────────────────────────────�� └ ┘ ─QUIET─

Parameters


This parameter specifies the names of the SVA subsystems containing thefunctional devices to be included in the report.



LISTCFG DEVICE




Default value: None

Examples: SUBSYSTEM(SUB1)SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(�)

FUNCTIONALDEVICEID (fdid)Conditional (This is one of a group of four parameters of which you can enter onlyone: FDID, PART, UNIT, or VOL. The default is PART.)

This parameter specifies devices to be included in the report.

Abbreviation: FDID




Examples: FunctionalDeviceID(4�) (decimal 64)FDID(D'64') (decimal 64)FDID(21 22 35)FDID(1�:22)

PARTITION (ALL | TEST | PRODUCTION)Conditional (This is one of a group of four parameters of which you can enter onlyone: FDID, PART, UNIT, or VOL. The default is PART.)

This parameter specifies that all functional devices associated with the designatedpartitions are to be included in the report.

Abbreviation: PART

Values: ALL, TEST, or PROD

Default value: ALL

Example: PART(PROD)

QUIETOptional

This parameter reduces the amount of generated output by suppressing errormessages for non-existent devices. Messages SIB0675E, SIB0676E, andSIB0677E are suppressed for FDID, UNIT, and VOLUME inquiries respectively.

Note: When FDID(*), UNIT(*), or VOLUME(*) are specified, the addition of theQUIET parameter makes no difference.


Default value: None


LISTCFG DEVICE

UNIT (device)Conditional (This is one of a group of four parameters of which you can enter onlyone: FDID, PART, UNIT, or VOL. The default is PART.)

This parameter specifies devices to be included in the report as they are defined tothe host in which SVAA is running.

Note: If the devices are not defined to the host, you must use the FDID parameterto specify devices. Information about PAV Alias devices is not displayed whenselecting devices using the UNIT parameter; the FDID parameter must be usedinstead.





Examples: UNIT(234)UNIT(2�:22)UNIT(1�� 11�)

VOLUME (volser)Conditional (This is one of a group of four parameters of which you can enter onlyone: FDID, PART, UNIT, or VOL. The default is PART.)

This parameter specifies the volume identifiers for one or more devices to beincluded in the report.

Note: If the devices are not defined to the host operating system in which SVAA isrunning, you must use the FDID parameter to specify devices. Information aboutPAV Alias devices is not displayed when selecting devices using the VOLUMEparameter; the FDID parameter must be used instead.

Abbreviation: VOL



Examples: VOL(TSTPK1)VOLUME(WKPK)


LISTCFG DEVICE

Examples of LISTCFG DEVICE Example 1.

The following subcommand requests a report on the functional devices with FDIDsranging from 86 to 8F in SVA subsystem LUNAR.

LISTCFG DEV (SUBSYS(LUNAR) FDID(86:8F) )

Here is an example of the report that might result.

REPORT DATE: Tue Jul 25, 2�� 1�:33:28 SVA SUBSYSTEM CRFUNDV V�3R�1M�� PAGE 1

FUNCTIONAL DEVICE CONFIGURATION REPORT


� SUBSYSTEM NAME = LUNAR � SUBSYSTEM MODEL = 95�� FUNCTIONAL DEVICES = 16 � FUNCTIONAL CAPACITY = 79564.42 �

��

FUNCT. ------- SCSI DEVICE -------CAPACITY -PHYSICAL CAP USE (MB)- --- ADDRESS --- PHYSICAL CAP

VOLSER NAME UNIT SSID FDID TYPE CYLS (MB) SHARED UNIQUE TOTAL DOM TGT LUN INDX LBLKS LBPTK ------ -------- ---- ---- ---- ------- ----- -------- -------- -------- -------- --- --- --- ---- ----- -----

D��1 86 339�3 3339 2838.� �.� �.� �.�D��1 87 339�9 1��17 8514.� �.� �.� �.�D��1 88 339�3 3339 2838.� �.� �.� �.�D��1 89 339�3 3339 2838.� �.� �.1 �.1D��1 8A 339�3 3339 2838.� �.� �.� �.�D��1 8B 339�3 3339 2838.� �.� �.� �.�D��1 8C 339�9 1��17 8514.� �.� �.1 �.1D��1 8D SCSIB 1��17 3691.9 �.� �.� �.� 1� 1� 1� � 512 48D��1 8E SCSIB 1��17 3691.9 �.� �.� �.� 1� 11 11 � 512 48D��1 8F SCSIA 3339 123�.2 �.� �.� �.� 11 11 11 � 512 48

DEVICE STATUS-------------

CKD CKD SCSI SCSI PPRCVOLSER UNIT FDID T/P CA DFW ECAM COMM ENABL R/W ENABL R/W STAT------ ---- ---- --- -- --- ---- ---- ----- --- ----- --- ----

86 P Y Y N N N N N N S87 P Y Y N N N N N N D88 P Y Y N N Y N N Y S89 P Y Y N N Y Y N N S8A P Y Y N N N Y N N S8B P Y Y N N N N N N S8C P Y Y N N N Y N Y D8D P Y Y N N Y Y N N8E P Y Y N N Y Y N N8F P Y Y N N Y Y N N

CAPACITY SUMMARY-------- -------SELECTED DEVICES SUMMARY========================

SELECTED FUNCTIONAL ---- PHYSICAL CAP USED (MB) ---PARTITION DEVICES CAPACITY(MB) SHARED UNIQUE TOTAL

---------- -------- ------------ --------- --------- ---------Production 16 79564.4 �.� 1.2 1.2

Test � �.� �.� �.� �.�Overall 16 79564.4 �.� 1.2 1.2

SUBSYSTEM SUMMARY================= TOTAL DISK ARRAY TOTAL FUNC. NET CAP. NET CAP. FREE_SPACE_PCT

PARTITION DEVICES CAPACITY(MB) CAPACITY(MB) LOAD(MB) LOAD PCT COLL'D UNCOLL ---------- ------- ------------ ------------ -------- -------- ------ ------

Production 16 85899.3 79564.4 17569.5 2�.5 79.5 �.�Test � �.� �.� �.� �.� �.� �.�

Overall 16 85899.3 79564.4 17569.5 2�.5 79.5 �.�

Note: The terms appearing in the report are defined in “Definitions of LISTCFGReport Headings” on page 8-110.


LISTCFG DEVICE

Example 2.

The following subcommand requests a report on the functional devices defined toMAZUMA which is a V2Xf subsystem.

LISTCFG DEV (SUBSYS(MAZUMA) )


REPORT DATE: Mon Oct 27, 2��3 12:49:17 SVA SUBSYSTEM CRFUNDV V�3R�1M�� PAGE 1

FUNCTIONAL DEVICE CONFIGURATION REPORT

�� SITE NAME = TESTSVA � FRAME SERIAL NUMBER = 481��7745 �

� SUBSYSTEM NAME = MAZUMA � SUBSYSTEM MODEL = V2Xf �� FUNCTIONAL DEVICES = 11 � FUNCTIONAL CAPACITY = 17�28.1� �

��



ABC 77�� 77�� 7�� 339�3 3339 2838.� �.� �.1 �.177�� 7�1 339�3 3339 2838.� �.� �.1 �.177�� 7�2 339�3 3339 2838.� �.� �.� �.�77�� 7�8 339�3 3339 2838.� �.� �.� �.�77�� 7�9 339�3 3339 2838.� �.� �.� �.�77�� 7EF 339�3 3339 2838.� �.� �.� �.�77�� 7F� 339�3 � �.� �.� �.� �.�77�� 7F1 339�3 � �.� �.� �.� �.�77�� 7F2 339�3 � �.� �.� �.� �.�77�� 7FE 339�3 � �.� �.� �.� �.�77�� 7FF 339�3 � �.� �.� �.� �.�


CKD CKD SCSI SCSI PPRC PAVVOLSER UNIT FDID T/P CA DFW ECAM COMM ENABL R/W ENABL R/W STAT STATUS------ ---- ---- --- -- --- ---- ---- ----- --- ----- --- ---- ------

77�� 7�� P Y Y Y N Y Y N N B(��4)7�1 P Y Y N N Y Y N N B(��1)7�2 P Y Y N N Y Y N N B7�8 P Y Y N N Y Y N N B7�9 P Y Y N N Y Y N N B7EF P Y Y N N Y Y N N B7F� P Y Y Y N Y Y N N A-7��7F1 P Y Y Y N Y Y N N A-7��7F2 P Y Y Y N Y Y N N A-7��7FE P Y Y N N Y Y N N A-7�17FF P Y Y Y N Y Y N N A-7��



---------- -------- ------------ --------- --------- ---------Production 11 17�28.1 �.� �.2 �.2

Test � �.� �.� �.� �.�Overall 11 17�28.1 �.� �.2 �.2


PARTITION DEVICES CAPACITY(MB) CAPACITY(MB) LOAD(MB) LOAD PCT COLL'D UNCOLL ---------- ------- ------------ ------------ -------- -------- ------ ------ Production 11 1868659.8 17�28.1 7353.2 �.4 99.6 �.1

Test � �.� �.� �.� �.� �.� �.� Overall 11 1868659.8 17�28.1 7353.2 �.4 99.6 �.1



LISTCFG DRIVEMODULE

LISTCFG DRIVEMODULE Subcommand


The LISTCFG DRIVEMODULE subcommand produces a report showing thecharacteristics of one or more drive modules. The destination for the report (theterminal or a file) is determined by the OUTFILE parameter of the SET DESTINATIONsubcommand.


LISTCFG DRIVEMODULE

┌ ┐─ ──────��──LISTCFG DriveMODule──(─ ──SUBSYStem( ───� ┴─subsys─ ) ──────────────────────────────────�

�─ ──┬ ┬────────────────────────────────────────────────── ─)───────────────────────────�� │ │┌ ┐──PARTition ──┬ ┬─────────────────────────────── │ ││ ││ │┌ ┐─ALL───────────────── │ ││ │└ ┘ ─(─ ──┼ ┼─MediaAcceptanceTest─ ─)─ │ ││ │├ ┤─PRODuction────────── │ ││ │├ ┤─SPareS────────────── │ ││ │├ ┤─TEST──────────────── │ ││ │└ ┘─UNAVailable───────── │ ││ │┌ ┐─ ─────── └ ┘──┼ ┼ ─ ─ARraYID( ───� ┴─arrayid─ ) ────────────────────── │ │┌ ┐─ ─────

└ ┘──DriveMODule( ───� ┴─u.t.s─ ) ────────────────────

Parameters


This parameter specifies the names of the SVA subsystems containing the drivemodules to be included in the report.




You can use ranges, lists, and wildcard characters, howeverwildcard characters are not allowed in ranges.

Default value: None

Examples: SUBSYSTEM(�)SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(SUBSYS1:SUBSYS5)SUBSYS(1SUBSYS)


LISTCFG DRIVEMODULE

ARRAYID (arrayid)Conditional (This is one of a group of three parameters of which you can enteronly one: ARYID, DMOD, or PART. If none is specified, the default is PART, anddrive modules in all partitions will be included.)

This parameter specifies the arrays that contain the drive modules to be included inthe report.

Abbreviation: ARYID

Values: arrayid (an integer from 0 to 7) is the array ID.


Default value: None

Examples: ARYID(�) (Drive modules in array 0)ARYID(�) (Drive modules in all arrays)ARYID(�:2) (Drive modules in arrays 0, 1, and 2)

DRIVEMODULE (u.t.s)Conditional (This is one of a group of three parameters of which you can enteronly one: ARYID, DMOD, or PART. If none is specified, the default is PART, anddrive modules in all partitions will be included.)

This parameter specifies the drive modules to be included in the report.

Abbreviation: DMOD

Values: u.t.s (3 digits separated by periods) identifies a specific drivemodule, where:


You can use ranges, lists, and wildcard characters, howeverwildcard characters are not allowed in ranges.

Default value: None

Examples: DRIVEMODULE(1.3.2)DRIVEMODULE(1.3.2 1.3.3 1.3.4 1.2.?)DMOD(1.3.�)DMOD(�.�.�:�.2.7)

PARTITION ( {ALL MAT PROD SPS TEST UNAV} )Conditional (This is one of a group of three parameters of which you can enteronly one: ARYID, DMOD, or PART. If none is specified, the default is PART, anddrive modules in all partitions will be included.)

This parameter specifies the partitions that contain the drive modules to be includedin the report.

Abbreviation: PART

Values: ALL specifies that the drive modules in all partitions are to beincluded in the report. ALL supersedes all other partitionspecifications.

MAT specifies the drive modules in the MAT partition.

PROD specifies the drive modules in the Production partition.


LISTCFG DRIVEMODULE

SPS specifies the drive modules in the Spares partition.

TEST specifies the drive modules in the Test partition.

UNAV specifies the drive modules in the Unavailable partition.

Default value: ALL

Examples: PART(PROD MAT) (Includes drive modules in Productionand MAT partitions only)

PARTITION (Includes drive modules in all partitions)

Examples of LISTCFG DRIVEMODULE Example 1.

The following subcommand requests a report on all drive modules in unit 0, tray 0,of SVA subsystem LUNAR.

LISTCFG DMOD (- SUBSYS(LUNAR)- DMOD(�.�.?) )


REPORT DATE: Tue May 9, 2�� 12:54:36 SVA SUBSYSTEM CRPHYDEV V�3R�1L�� PAGE: 1

DRIVE MODULE CONFIGURATION REPORT


� SUBSYSTEM NAME = LUNAR � SUBSYSTEM MODEL = 95�� AVAILABLE DRIVES = 32 � PHYSICAL CAPACITY = 291 (GB) �

��

DEVICE-LOCATION SERIAL DEVICE CAPACITY --DEVICE TYPE---UNIT TRAY SLOT NUMBER STATUS ARRAY (MB) CLASS SUB-CLASS---- ---- ---- -------- ------ ----- --------- ----- ---------

SELECTED DEVICES � � � ��572936 P.A � 9�91.4 � 5� � 1 ��572895 P.A 1 9�91.4 � 5� � 2 ��573�18 P.A � 9�91.4 � 5� � 3 ��574639 P.A � 9�91.4 � 5� � 4 ��572937 P.A � 9�91.4 � 5� � 5 ��572897 P.A � 9�91.4 � 5� � 6 ��573�15 P.A � 9�91.4 � 5� � 7 ��572932 P.A � 9�91.4 � 5

SELECTED DEVICES TOTAL PHYSICAL CAPACITY = 72.7

TOTAL PHYSICAL CAPACITY = 72.7


Example 2.

The following subcommand requests a report on all drive modules in the Sparespartition and Production partition in SVA subsystem V2XSYS�1.

LISTCFG DMOD (- SUBSYS(V2XSYSO1)-

PART(SPS PROD) )



LISTCFG SUBSYSTEM

REPORT DATE: Wed Aug 28, 2��2 �9:44:4� SVA SUBSYSTEM CRPHYDEV V�3R�1L�� PAGE: 1

DRIVE MODULE CONFIGURATION REPORT

�� SITE NAME = StorTek � FRAME SERIAL NUMBER = 481��7�25 �� SUBSYSTEM NAME = V2XSYS�1 � SUBSYSTEM MODEL = V2X �� AVAILABLE DRIVES = 32 � PHYSICAL CAPACITY = 1148(GB) �

��


SPARES PARTITION � 1 7 ��849� S.A - 35879.� � 7� 3 6 ��11719 S.A - 35879.� � 7

SPARES PARTITION TOTAL PHYSICAL CAPACITY = 71.8

PRODUCTION PARTITION � � � ��9331 P.A � 35879.� � 7� � 1 ��11789 P.A � 35879.� � 7� � 2 ��11�24 P.A � 35879.� � 7� � 3 ��11772 P.A � 35879.� � 7� � 4 ��1�571 P.A � 35879.� � 7� � 5 ��1�674 P.A � 35879.� � 7� � 6 ��11792 P.A � 35879.� � 7� � 7 ��118�2 P.A � 35879.� � 7� 1 � ��9644 P.A � 35879.� � 7� 1 1 ��1�219 P.A � 35879.� � 7� 1 2 ��1�216 P.A � 35879.� � 7� 1 3 ��1171� P.A � 35879.� � 7� 1 4 ��1�572 P.A � 35879.� � 7� 1 5 ��8964 P.A � 35879.� � 7� 1 6 ��11734 P.A � 35879.� � 7� 2 � ��8682 P.A 1 35879.� � 7� 2 1 ��11736 P.A 1 35879.� � 7� 2 2 ��115�9 P.A 1 35879.� � 7� 2 3 ��1�384 P.A 1 35879.� � 7� 2 4 ��11�96 P.A 1 35879.� � 7� 2 5 ��1172� P.A 1 35879.� � 7� 2 6 ��11766 P.A 1 35879.� � 7� 2 7 ��1�565 P.A 1 35879.� � 7� 3 � ��1179� P.A 1 35879.� � 7� 3 1 ��1178� P.A 1 35879.� � 7� 3 2 ��11894 P.A 1 35879.� � 7� 3 3 ��1�223 P.A 1 35879.� � 7� 3 4 ��118�� P.A 1 35879.� � 7� 3 5 ��951� P.A 1 35879.� � 7� 3 7 ��9365 P.A 1 35879.� � 7

PRODUCTION PARTITION TOTAL PHYSICAL CAPACITY = 1�76.4


LISTCFG SUBSYSTEM Subcommand


The LISTCFG SUBSYSTEM subcommand provides three types (or levels) of SVAsubsystem reports: on functional devices, channel interfaces, and drive modules.You can specify one, two, or all three report types. The destination for the report(the terminal or a file) is determined by the OUTFILE parameter of the SETDESTINATION subcommand.



LISTCFG SUBSYSTEM

LISTCFG SUBSYSTEM

��──LISTCFG SUBSYStem──(─ ──SUBSYStem(subsys) ──┬ ┬────────────────────── ─)─────────────�� │ │┌ ┐─ ───────

│ ││ │┌ ┐─1 2 3─ └ ┘──LEVEL( ───� ┴┼ ┼─1───── ) ├ ┤─2───── └ ┘─3─────

Parameters


This parameter specifies the names of the SVA subsystems for which a report is tobe produced.





Default value: None

Examples: SUBSYSTEM(�)SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(SUBSYS1:SUBSYS5)SUBSYS(1SUBSYS)

LEVEL (1 2 3)Optional

This parameter specifies the level of reporting. One or more levels of reporting canbe requested at one time.

Values: 1 provides information on functional device configuration.2 provides information on cache and channel configuration.3 provides information on drive module configuration.

A duplicate level entry, such as LEVEL(1 1), is ignored.

Default value: 1 2 3

Examples: LEVEL(1)LEVEL(3 2 1)


LISTCFG SUBSYSTEM

Example of LISTCFG SUBSYSTEM for non-V2Xf subsystemsThe following subcommand requests a report on all three levels on the SVAsubsystem V2XSYS�1 which is a non-PAV subsystem.

LISTCFG SUBSYS(SUBSYS(V2XSYS�1) )

On the following pages is an example of the report. For an example of a V2Xfreport with PAV devices, see “Example of LISTCFG SUBSYSTEM for V2Xfsubsystems” on page 8-85.



LISTCFG SUBSYSTEM

REPORT DATE: Wed Aug 28, 2��2 �9:44:4� SVA SUBSYSTEM CRLEVL1 V�3R�1L�� PAGE 2

FUNCTIONAL DEVICE CONFIGURATION REPORT (LEVEL 1)

�� SITE NAME = StorTek � FRAME SERIAL NUMBER = 481��7�25 �� SUBSYSTEM NAME = V2XSYS�1 � SUBSYSTEM MODEL = V2X �� FUNCTIONAL DEVICES = 3381 � FUNCTIONAL CAPACITY = 9637245.71 �

��



SWAC�� TEST�� AC�� 2�� 339�3 3339 2838.� �.� �.2 �.2TEST��1 �2�� 1 339�3 3339 2838.� �.� 49.4 49.4TEST��2 �2�� 2 339�3 3339 2838.� �.� 1�.3 1�.3TESE��3 �2�� 3 339�3 3339 2838.� �.� 5.1 5.1TEST��4 �2�� 4 339�3 3339 2838.� �.� �.2 �.2

... SWBB�� BB�� B�� SCSIA 3339 246�.3 �.� �.8 �.8 4 � � � 4�96 12

d12ecam BB�� B�1 SCSIA 3339 246�.3 �.� �.� �.� 12 � � � 4�96 12d13ecam BB�� B�2 SCSIA 3339 246�.3 �.� �.� �.� 13 � � � 4�96 12AlLgSrc BB�� B1� SCSIA 3339 246�.3 �.� 12.3 12.3 4 � 1� � 4�96 12AlLgSrc BB�� B11 SCSIA 3339 246�.3 �.� �.7 �.7 4 � 1� 1 4�96 12

...FIDO BFFC BF�� FFB 339�3 3339 2838.� �.� 124.5 124.5SMOKEY BFFC BF�� FFC 339�3 3339 2838.� �.� 287.9 287.9TIGER BFFD BF�� FFD 339�3 3339 2838.� �.� 716.8 716.8BARNEY BFFE BF�� FFE 339�3 3339 2838.� �.� �.4 �.4

SWBFFF ZIGGY BFFF BF�� FFF 339�3 3339 2838.� �.� �.2 �.2

DEVICE STATUS------------- CKD CKD SCSI SCSI PPRCVOLSER UNIT FDID T/P CA DFW ECAM COMM ENABL R/W ENABL R/W STAT------ ---- ---- --- -- --- ---- ---- ----- --- ----- --- ----

SWAC�� AC�� P Y Y Y Y Y Y N N�1 P Y Y Y N Y Y N N�2 P Y Y Y N Y Y N N�3 P Y Y Y N Y Y N N�4 P Y Y N N Y Y N N

...B�� P Y Y Y N N N Y YB�1 P Y Y Y N N N Y YB�2 P Y Y Y N N N Y YB1� P Y Y N N N N Y YB11 P Y Y N N N N Y Y

...BFFB FFB P Y Y N N Y Y N NBFFC FFC P Y Y N N Y Y N NBFFD FFD P Y Y N N Y Y N NBFFE FFE P Y Y N N Y Y N N

SWBFFF BFFF FFF P Y Y N N Y Y N N



---------- -------- ------------ --------- --------- ---------Production 3381 9637245.7 1565.8 5149.2 6715.�

Test � �.� �.� �.� �.� Overall 3381 9637245.7 1565.8 5149.2 6715.�


PARTITION DEVICES CAPACITY(MB) CAPACITY(MB) LOAD(MB) LOAD PCT COLL'D UNCOLL ---------- ------- ------------ ------------ -------- -------- ------ ------ Production 3381 932853.8 9637245.7 12316.8 1.3 98.5 �.1

Test � �.� �.� �.� �.� �.� �.� Overall 3381 932853.8 9637245.7 12316.8 1.3 98.5 �.1


LISTCFG SUBSYSTEM

REPORT DATE: Wed Aug 28, 2��2 �9:44:4� SVA SUBSYSTEM CRLEVEL2 V�3R�1L�� PAGE: 1


�� SITE NAME = StorTek � FRAME SERIAL NUMBER = 481��7�25 �� SUBSYSTEM NAME = V2XSYS�1 � SUBSYSTEM MODEL = V2X �� NO. OF CHANNELS = 2� � SITE LOCATION NO. = � �

��CACHE INFORMATION GENERAL INFORMATION----- ----------- ------- -----------CACHE SIZE = 8192NVS SIZE = 128

INTERFACE --- CHANNEL INTERFACE --- --- CHANNEL --- BASENAME CLUSTER ID ENABLED TYPE SPEED IDID RANGE FDID

--------- ------- ------- ------- -------- ----- ---- ----- ----CHAN_�.A � A Y ESCON 2�.� �� 4�96 ��

� B Y ESCON 2�.� �� 4�96 ��WARTHOG � C Y ESCON 2�.� �� 4�96 ��

� D Y ESCON 2�.� �� 4�96 �� E Y ESCON 2�.� �� 4�96 �� G Y ESCON 2�.� �� 4�96 ��1 A Y ESCON 2�.� �� 4�96 ��1 B Y ESCON 2�.� �� 4�96 ��1 C Y ESCON 2�.� �� 4�96 ��1 D Y ESCON 2�.� �� 4�96 ��1 E Y ESCON 2�.� �� 4�96 ��

RODENT 1 G Y ESCON 2�.� �� 4�96 ��1 M N UNINSTAL 2�.�

INTERFACE --- CHANNEL INTERFACE --- --- CHANNEL --- SCSI WORLD WIDENAME CLUSTER ID ENABLED TYPE SPEED DOMAIN NODE NAME PORT NAME ADDRESS

--------- ------- ------- ------- -------- ----- ------- ---------------- ---------------- --------� I Y FIBRE 1��.� ��4 5��1�4F��45CB34 5��1�4F��46128A ��4

SQUAINK � K Y FIBRE 1��.�� M Y FIBRE 1��.� ��6 5��1�4F��45CB36 5��1�4F��4612F� ��6� O Y FIBRE 1��.�1 I Y FIBRE 1��.� �12 5��1�4F��45CB3C 5��1�4F��461348 ��7E1 K Y FIBRE 1��.� �13 5��1�4F��45CB3D 5��1�4F��461349 ��7E1 O Y FIBRE 1��.� �15 5��1�4F��45CB3F 5��1�4F��4613A3 ��7E

REPORT DATE: Wed Aug 28, 2��2 �9:44:4� SVA SUBSYSTEM CRLEVEL3 V�3R�1L�� PAGE: 1

DRIVE MODULE CONFIGURATION REPORT (LEVEL 3)

�� SITE NAME = StorTek � FRAME SERIAL NUMBER = 481��7�25 �� SUBSYSTEM NAME = V2XSYS�1 � SUBSYSTEM MODEL = V2X �

� DRIVE MODULES = 32 � PHYSICAL CAPACITY = 1148.1(GB) � ��

GENERAL INFORMATION------- -----------

NUMBER OF SPARES = 2NUMBER OF ARRAYS = 2 DEFAULT GLOBAL SPARES = 1 DEFAULT ARRAY SIZE = 13+2NUMBER OF FUNCTIONAL DEVICES = 4�96 CACHE SIZE = 8192 NVS SIZE = 128REMOTE OPERATOR PANEL STATUS = ENABLED CSRC STATUS = Full SCSI SIMS STATUS = ENABLEDNUMBER OF SCSI DOMAINS = 16 NUMBER OF SCSI TARGETS = 16 NUMBER OF SCSI LUNS = 256

COPYLIM = �TOT VIRT CYLINDERS = 27353�88 CONFIG VIRT CYLS = 6115596 UNCONFIG VIRTCYLS = 21237492

SUBSYSTEM IDENTIFIERS =

�2�� AD�� AE�� AF�� B4�� B5�� B6�� B7�� B8�� B9�� BA�� BB�� BC�� BD�� BE�� BF��

SUPPORTED FEATURES--------- -------- Maintenance SnapShot


LISTCFG SUBSYSTEM

REVISION LEVEL INFORMATION-------- ----- -----------

COMPONENT ID = SRL COMPONENT LEVEL = B�111�7��COMPONENT ID = ISP COMPONENT LEVEL =COMPONENT ID = IUP COMPONENT LEVEL =COMPONENT ID = CIP COMPONENT LEVEL =COMPONENT ID = FIP COMPONENT LEVEL =

DRIVE MODULE INFORMATION----- ------ -----------


UNAVAILABLE PARTITION 1 � � �� U.N - �.� � �1 � 1 �� U.N - �.� � �1 � 2 �� U.N - �.� � �1 � 3 �� U.N - �.� � �1 � 4 �� U.N - �.� � �1 � 5 �� U.N - �.� � �1 � 6 �� U.N - �.� � �

...3 3 4 �� U.N - �.� � �3 3 5 �� U.N - �.� � �3 3 6 �� U.N - �.� � �3 3 7 �� U.N - �.� � �

UNAVAILABLE PARTITION TOTAL PHYSICAL CAPACITY = �.�

MAT PARTITION Contains No Drives

SPARES PARTITION � 1 7 ��849� S.A - 35879.� � 7� 3 6 ��11719 S.A - 35879.� � 7

SPARES PARTITION TOTAL PHYSICAL CAPACITY = 71758.�

TEST PARTITION Contains No Drives

PRODUCTION PARTITION � � � ��9331 P.A � 35879.� � 7� � 1 ��11789 P.A � 35879.� � 7� � 2 ��11�24 P.A � 35879.� � 7� � 3 ��11772 P.A � 35879.� � 7� � 4 ��1�571 P.A � 35879.� � 7� � 5 ��1�674 P.A � 35879.� � 7� � 6 ��11792 P.A � 35879.� � 7� � 7 ��118�2 P.A � 35879.� � 7� 1 � ��9644 P.A � 35879.� � 7� 1 1 ��1�219 P.A � 35879.� � 7� 1 2 ��1�216 P.A � 35879.� � 7� 1 3 ��1171� P.A � 35879.� � 7� 1 4 ��1�572 P.A � 35879.� � 7� 1 5 ��8964 P.A � 35879.� � 7� 1 6 ��11734 P.A � 35879.� � 7� 2 � ��8682 P.A 1 35879.� � 7� 2 1 ��11736 P.A 1 35879.� � 7� 2 2 ��115�9 P.A 1 35879.� � 7� 2 3 ��1�384 P.A 1 35879.� � 7� 2 4 ��11�96 P.A 1 35879.� � 7� 2 5 ��1172� P.A 1 35879.� � 7� 2 6 ��11766 P.A 1 35879.� � 7� 2 7 ��1�565 P.A 1 35879.� � 7� 3 � ��1179� P.A 1 35879.� � 7� 3 1 ��1178� P.A 1 35879.� � 7� 3 2 ��11894 P.A 1 35879.� � 7� 3 3 ��1�223 P.A 1 35879.� � 7� 3 4 ��118�� P.A 1 35879.� � 7� 3 5 ��951� P.A 1 35879.� � 7� 3 7 ��9365 P.A 1 35879.� � 7

PRODUCTION PARTITION TOTAL PHYSICAL CAPACITY = 1�76369.8



LISTCFG SUBSYSTEM

ARRAY INFORMATION----- -----------

FORMATION SPARE(S) TWO DRIVE GROUP DRAIN D E V I C E S T A T U S E SARRAY PARTITION CONFIG IN PROGRESS NEEDED FAILURE STATUS INITIALIZING DRAINING RECONSTRUCTION----- --------- ------ ----------- -------- --------- ----------- ------------ -------- --------------� PRODUCTION 13+2 NO NO NO N.A. NO N.A. N.A.1 PRODUCTION 13+2 NO NO NO N.A. NO N.A. N.A.2 H a s N o t B e e n C o n f i g u r e d3 H a s N o t B e e n C o n f i g u r e d4 H a s N o t B e e n C o n f i g u r e d5 H a s N o t B e e n C o n f i g u r e d6 H a s N o t B e e n C o n f i g u r e d7 H a s N o t B e e n C o n f i g u r e d


LISTCFG SUBSYSTEM for V2Xf subsystems

Example of LISTCFG SUBSYSTEM for V2Xf subsystemsThe following subcommand requests a report on all three levels on the SVA V2Xfsubsystem MAZUMA. This subsystem has PAV devices.

LISTCFG SUBSYS(SUBSYS(MAZUMA) )


REPORT DATE: Mon Dec 8, 2��3 1�:42:2� SVA SUBSYSTEM CRLEVL1 V�3R�1L�� PAGE 1



� SUBSYSTEM NAME = MAZUMA � SUBSYSTEM MODEL = V2Xf �� FUNCTIONAL DEVICES = 377 � FUNCTIONAL CAPACITY = 251��58.�7 �

��



SW7�� ECA�� 7�� 7�� 339�3 3339 2838.� �.� �.2 �.2 ECA��1 7�� 1 339�3 3339 2838.� �.� �.� �.� ECA��2 7�� 2 339�3 3339 2838.� �.� �.� �.� ECA��3 7�� 3 339�3 3339 2838.� �.� �.3 �.3 SW7��7 7�� 7 339�3 3339 2838.� �.� �.3 �.3 SW7��8 7�� 8 339�3 3339 2838.� �.� �.3 �.3 SW7��9 7�� 9 339�3 3339 2838.� �.� �.3 �.3 SW7��A 7�� A 339�3 3339 2838.� �.� �.3 �.3 SW7��B 7�� B 339�3 3339 2838.� �.� �.3 �.3

ECA�C 7�� C 339�3 3339 2838.� �.� �.1 �.1NAMEVAR 7�� D 339�3 3339 2838.� �.� �.1 �.1ECA�E 7�� E 339�3 3339 2838.� 6.1 �.1 6.2ECA�F 7�� F 339�3 3339 2838.� 36.9 12.4 49.2

7�� 5� 338�J 885 63�.2 �.� �.5 �.5 SAMPLE 7�� 51 339�1 1113 946.� �.� �.3 �.3 SAMPLE 7�� 52 339�1 1113 946.� �.� �.3 �.3 SAMPLE 7�� 53 339�1 1113 946.� �.� �.3 �.3 SAMPLE 7�� 54 339�1 1113 946.� �.� �.3 �.3 SAMPLE 7�� 55 339�1 1113 946.� �.� �.3 �.3

7�� 56 338�J 885 63�.2 �.� �.5 �.5 SW7�75 7�� 75 339�3 3339 2838.� 783.� �.� 783.� SW7�76 7�� 76 339�3 3339 2838.� �.� 1�3.8 1�3.8 SW7�77 7�� 77 339�3 3339 2838.� 659.1 �.� 659.1 SW7�78 7�� 78 339�3 3339 2838.� �.� 783.� 783.� SW7�79 7�� 79 339�3 3339 2838.� 783.� �.� 783.� SW7�7A 7�� 7A 339�3 3339 2838.� �.� 783.� 783.� SW7�7B 7�� 7B 339�3 3339 2838.� 783.� �.� 783.� SW7�7C 7�� 7C 339�3 3339 2838.� �.� �.3 �.3 SW7�7D 7�� 7D 339�3 3339 2838.� �.� �.3 �.3 SW7�7E 7�� 7E 339�3 3339 2838.� �.� �.3 �.3 SW7�7F 7�� 7F 339�3 3339 2838.� �.� �.3 �.3 SW7�8� 7�� 8� 339�9 1��17 8514.� �.� �.3 �.3 SW7�81 7�� 81 339�3 3339 2838.� 783.� �.� 783.� SW7�82 7�� 82 339�3 3339 2838.� 783.� �.� 783.� SW7�83 7�� 83 339�3 3339 2838.� 783.� �.� 783.� SW7�84 7�� 84 339�3 3339 2838.� 783.� �.� 783.� SW7�85 7�� 85 339�3 3339 2838.� �.� 783.� 783.� SW7�86 7�� 86 339�3 3339 2838.� �.� �.� �.� SW7�87 7�� 87 339�3 3339 2838.� 659.1 �.� 659.1 SW7�88 7�� 88 339�3 3339 2838.� 783.� �.� 783.�







��



SW7�89 7�� 89 339�3 3339 2838.� �.� �.� �.� SW7�8A 7�� 8A 339�3 3339 2838.� �.� �.� �.� SW7�8B 7�� 8B 339�3 3339 2838.� 659.1 �.� 659.1 SW7�8C 7�� 8C 339�3 3339 2838.� �.� �.� �.�

71�� 1�1 338�J 885 63�.2 �.� 5.7 5.771�� 1�2 338�J 885 63�.2 �.� �.� �.�71�� 1�3 338�J 885 63�.2 �.� �.� �.�71�� 1�4 338�J 885 63�.2 �.� �.� �.�71�� 1�5 338�J 885 63�.2 �.� �.� �.�71�� 1�6 338�J 885 63�.2 �.� �.� �.�71�� 1�7 338�J 885 63�.2 �.� �.� �.�71�� 1�8 338�J 885 63�.2 �.� �.� �.�71�� 1�9 338�J 885 63�.2 �.� �.� �.�71�� 1�A 338�J 885 63�.2 �.� �.� �.�

SW71�B 71�� 1�B 338�J 885 63�.2 �.� �.� �.� SW71�C 71�� 1�C 338�J 885 63�.2 �.� �.� �.� SW71�D 71�� 1�D 338�J 885 63�.2 �.� �.� �.� SW71�E 71�� 1�E 338�J 885 63�.2 �.� �.� �.� SW71�F 71�� 1�F 338�J 885 63�.2 �.� �.� �.�

71�� 153 338�J 885 63�.2 �.� �.5 �.571�� 154 338�J 885 63�.2 �.� �.5 �.5

SW7175 71�� 175 338�J 885 63�.2 �.� �.� �.� SW7176 71�� 176 338�J 885 63�.2 �.� �.� �.� SW7177 71�� 177 338�J 885 63�.2 �.� �.� �.� SW7178 71�� 178 338�J 885 63�.2 �.� �.� �.�

72�� 2�2 339�3 3339 2838.� 783.� �.� 783.�72�� 2�3 339�3 3339 2838.� �.� �.� �.�72�� 2�4 339�3 3339 2838.� �.� �.� �.�72�� 2�5 339�3 3339 2838.� �.� �.� �.�72�� 2�6 339�3 3339 2838.� �.� �.� �.�72�� 2�7 339�3 3339 2838.� �.� �.� �.�72�� 2�8 339�3 3339 2838.� �.� �.� �.�72�� 2�9 339�3 3339 2838.� �.� �.� �.�72�� 2�A 339�3 3339 2838.� �.1 �.1 �.172�� 2�B 339�3 3339 2838.� �.� �.3 �.372�� 2�C 339�3 3339 2838.� �.� �.3 �.372�� 2�D 339�3 3339 2838.� �.� �.3 �.372�� 2�E 339�3 3339 2838.� �.� �.3 �.372�� 2�F 339�3 3339 2838.� �.� �.3 �.372�� 21� 339�3 3339 2838.� �.� �.3 �.3







��



DJTEST 72�� 269 339�2 2226 1892.� �.� �.� �.� SW7275 72�� 275 339�9 1��17 8514.� �.� �.� �.� SW7276 72�� 276 339�9 1��17 8514.� �.� �.� �.� SW7277 72�� 277 339�9 1��17 8514.� �.� �.� �.� SW7278 72�� 278 339�9 1��17 8514.� �.� �.� �.� SW73�� 73�� 3�� 339�3 3339 2838.� �.� 659.1 659.1 SW73�1 73�� 3�1 339�9 1��17 8514.� 783.� �.� 783.� SW73�2 73�� 3�2 339�9 1��17 8514.� 783.� �.� 783.� SW73�3 73�� 3�3 339�9 1��17 8514.� �.� �.3 �.3 SW73�4 73�� 3�4 339�9 1��17 8514.� �.� �.3 �.3 SW73�5 73�� 3�5 339�9 1��17 8514.� �.� �.3 �.3 SW73�6 73�� 3�6 339�9 1��17 8514.� �.� �.3 �.3 SW73�7 73�� 3�7 339�3 3339 2838.� �.� �.3 �.3 SW73�8 73�� 3�8 339�3 3339 2838.� �.� �.3 �.3 SW73�9 73�� 3�9 339�3 3339 2838.� �.� �.3 �.3 SW73�A 73�� 3�A 339�3 3339 2838.� �.� �.3 �.3 SW73�B 73�� 3�B 339�3 3339 2838.� �.� �.3 �.3 SW73�C 73�� 3�C 339�3 3339 2838.� �.� �.1 �.1 SW73�D 73�� 3�D 339�3 3339 2838.� �.� 656.2 656.2 SW73�E 73�� 3�E 339�3 3339 2838.� �.� 782.8 782.8 SW73�F 73�� 3�F 339�3 3339 2838.� �.� �.� �.� SW77�� 77�� 7�� 339�3 3339 2838.� �.� �.1 �.1 SW77�1 77�� 7�1 339�3 3339 2838.� �.� �.1 �.1 SW77�3 77�� 7�3 339�3 3339 2838.� �.� �.3 �.3 SW77�4 77�� 7�4 339�3 3339 2838.� �.� �.� �.� SW77�5 77�� 7�5 339�3 3339 2838.� �.� �.� �.� SW77�6 77�� 7�6 339�3 3339 2838.� �.� �.� �.� SW77�7 77�� 7�7 339�3 3339 2838.� �.� �.� �.�

77�� 7�8 339�3 3339 2838.� �.� �.� �.�77�� 7�9 339�3 3339 2838.� �.� �.� �.�77�� 7EF 339�3 3339 2838.� �.� �.� �.�77�� 7FF 339�3 � �.� �.� �.� �.�78�� 8�� 339�3 3339 2838.� �.� �.1 �.178�� 8�1 339�3 3339 2838.� �.� �.1 �.1

SW78�2 78�� 8�2 339�9 1��17 8514.� 1.3 �.� 1.3 SW78�3 78�� 8�3 339�9 1��17 8514.� �.� �.1 �.1 SW78�4 78�� 8�4 339�9 1��17 8514.� 1.3 �.� 1.3 SW78�5 78�� 8�5 339�9 1��17 8514.� �.� �.1 �.1 SW78�6 78�� 8�6 339�9 1��17 8514.� �.� �.1 �.1 SW78�7 78�� 8�7 339�9 1��17 8514.� �.� �.1 �.1







��



SW78�8 78�� 8�8 339�9 1��17 8514.� �.� �.1 �.1 SW78�9 78�� 8�9 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 8�A 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 8�B 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 8�C 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 8�D 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 8�E 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 8�F 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81� 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 811 339�9 1��17 8514.� �.� 389.6 389.6 SW78�A 78�� 812 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 813 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 814 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 815 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 816 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 817 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 818 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 819 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81A 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81B 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81C 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81D 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81E 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 81F 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82� 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 821 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 822 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 823 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 824 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 825 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 826 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 827 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 828 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 829 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82A 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82B 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82C 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82D 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82E 339�9 1��17 8514.� �.� �.1 �.1 SW78�A 78�� 82F 339�9 1��17 8514.� �.� �.1 �.1







��



SW78�A 78�� 83� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 831 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 832 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 833 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 834 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 835 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 836 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 837 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 838 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 839 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 83A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 83B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 83C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 83D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 83E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 83F 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 841 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 842 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 843 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 844 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 845 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 846 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 847 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 848 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 849 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 84F 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 851 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 852 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 853 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 854 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 855 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 856 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 857 339�9 1��17 8514.� �.� �.1 �.1







��



SW78�A 78�� 858 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 859 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 85F 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 861 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 862 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 863 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 864 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 865 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 866 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 867 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 868 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 869 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 86F 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 871 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 872 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 873 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 874 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 875 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 876 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 877 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 878 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 879 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 87F 339�9 1��17 8514.� �.� �.1 �.1







��



SW78�A 78�� 88� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 881 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 882 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 883 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 884 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 885 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 886 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 887 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 888 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 889 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 88A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 88B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 88C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 88D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 88E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 88F 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 891 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 892 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 893 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 894 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 895 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 896 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 897 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 898 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 899 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89A 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89B 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89C 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89D 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89E 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 89F 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A1 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A2 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A3 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A4 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A5 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A6 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A7 339�9 1��17 8514.� �.� �.1 �.1







��



SW78�A 78�� 8A8 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8A9 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8AA 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8AB 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8AC 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8AD 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8AE 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8AF 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B1 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B2 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B3 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B4 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B5 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B6 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B7 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B8 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8B9 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8BA 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8BB 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8BC 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8BD 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8BE 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8BF 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C1 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C2 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C3 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C4 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C5 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C6 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C7 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C8 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8C9 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8CA 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8CB 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8CC 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8CD 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8CE 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8CF 339�9 1��17 8514.� �.� �.1 �.1







��



SW78�A 78�� 8D� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D1 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D2 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D3 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D4 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D5 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D6 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D7 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D8 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8D9 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8DA 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8DB 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8DC 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8DD 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8DE 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8DF 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E1 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E2 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E3 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E4 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E5 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E6 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E7 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E8 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8E9 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8EA 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8EB 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8EC 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8ED 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8EE 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8EF 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F� 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F1 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F2 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F3 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F4 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F5 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F6 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F7 339�9 1��17 8514.� �.� �.1 �.1



REPORT DATE: Mon Dec 8, 2��3 1�:42:2� SVA SUBSYSTEM CRLEVL1 V�3R�1L�� PAGE 1�




��



SW78�A 78�� 8F8 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8F9 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8FA 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8FB 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8FC 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8FD 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8FE 339�9 1��17 8514.� �.� �.1 �.1SW78�A 78�� 8FF 339�9 1��17 8514.� �.� �.1 �.1SW7F11 7F�� F11 339�3 3339 2838.� �.� �.� �.�SW7F12 7F�� F12 339�3 3339 2838.� �.� �.� �.�SW7F13 7F�� F13 339�3 3339 2838.� �.� �.� �.�SW7F14 7F�� F14 339�3 3339 2838.� �.� �.� �.�SW7F15 7F�� F15 339�3 3339 2838.� �.� �.� �.�SW7F16 7F�� F16 339�3 3339 2838.� �.� �.� �.�SW7F17 7F�� F17 339�3 3339 2838.� �.� �.� �.�SW7F18 7F�� F18 339�3 3339 2838.� �.� �.� �.�SW7F19 7F�� F19 339�3 3339 2838.� �.� �.� �.�



SW7�� 7�� P Y Y Y Y Y Y N N B�1 P Y Y Y N Y Y N N B�2 P Y Y Y N Y Y N N B�3 P Y Y Y N Y Y N N B�7 P Y Y Y N Y Y N N B�8 P Y Y N N Y Y N N P B�9 P Y Y N N Y Y N N P B�A P Y Y N N Y Y N N P B�B P Y Y N N Y Y N N P B�C P Y Y N N Y Y N N P B�D P Y Y N N Y Y N N B�E P Y Y N N Y Y N N B�F P Y Y N N Y Y N N B5� P Y Y N N Y Y N N P B51 P Y Y N N Y Y N N B52 P Y Y N N Y Y N N B







��



53 P Y Y N N Y Y N N B54 P Y Y Y N Y Y N N B55 P Y Y N N Y Y N N B56 P Y Y N N Y Y N N P B75 P Y Y N N Y Y N N P B76 P Y Y N N Y Y N N B77 P Y Y N N Y Y N N B78 P Y Y N N Y Y N N B79 P Y Y N N Y Y N N B7A P Y Y N N Y Y N N B7B P Y Y N N Y Y N N B7C P Y Y N N Y Y N N P B7D P Y Y N N Y Y N N P B7E P Y Y N N Y Y N N B7F P Y Y N N Y Y N N B8� P Y Y N N Y Y N N B81 P Y Y N N Y Y N N P B82 P Y Y N N Y Y N N B83 P Y Y N N Y Y N N P B84 P Y Y N N Y Y N N B85 P Y Y N N Y Y N N B86 P Y Y N N Y Y N N B87 P Y Y N N Y Y N N B88 P Y Y N N Y Y N N B89 P Y Y N N Y Y N N B8A P Y Y N N Y Y N N B8B P Y Y N N Y Y N N P B8C P Y Y N N Y Y N N B1�1 P Y Y N N Y Y N N B1�2 P Y Y N N Y Y N N B1�3 P Y Y N N Y Y N N B1�4 P Y Y N N Y Y N N B1�5 P Y Y N N Y Y N N B1�6 P Y Y N N Y Y N N B1�7 P Y Y N N Y Y N N B1�8 P Y Y N N Y Y N N B1�9 P Y Y N N Y Y N N B1�A P Y Y N N Y Y N N B







��



1�B P Y Y N N Y Y N N B1�C P Y Y N N Y Y N N B1�D P Y Y N N Y Y N N B1�E P Y Y N N Y Y N N B1�F P Y Y N N Y Y N N B153 P Y Y N N Y Y N N B154 P Y Y N N Y Y N N B175 P Y Y N N Y Y N N B176 P Y Y N N Y Y N N B177 P Y Y N N Y Y N N B178 P Y Y N N Y Y N N B2�2 P Y Y N N Y Y N N B2�3 P Y Y N N Y Y N N B2�4 P Y Y N N Y Y N N B2�5 P Y Y N N Y Y N N B2�6 P Y Y N N Y Y N N B2�7 P Y Y N N Y Y N N B2�8 P Y Y N N Y Y N N B2�9 P Y Y N N Y Y N N B2�A P Y Y N N Y Y N N B2�B P Y Y N N Y Y N N B2�C P Y Y N N Y Y N N B2�D P Y Y N N Y Y N N B2�E P Y Y N N Y Y N N B2�F P Y Y N N Y Y N N B21� P Y Y N N Y Y N N B269 P Y Y N N Y Y N N B275 P Y Y N N Y Y N N B276 P Y Y N N Y Y N N B277 P Y Y N N Y Y N N B278 P Y Y N N Y Y N N B3�� P Y Y N N Y Y N N S B3�1 P Y Y N N Y Y N N B3�2 P Y Y N N Y Y N N B3�3 P Y Y N N Y Y N N P B3�4 P Y Y N N Y Y N N B3�5 P Y Y N N Y Y N N P B3�6 P Y Y N N Y Y N N B



REPORT DATE: Mon Dec 8, 2��3 1�:42:2� SVA SUBSYSTEM CRLEVL1 V�3R�1L�� PAG# 13




��



3�7 P Y Y N N Y Y N N B3�8 P Y Y N N Y Y N N S B3�9 P Y Y N N Y Y N N S B3�A P Y Y N N Y Y N N S B3�B P Y Y N N Y Y N N S B3�C P Y Y N N Y Y N N S B3�D P Y Y N N Y Y N N B3�E P Y Y N N Y Y N N B3�F P Y Y N N Y Y N N B

SW77�� 77�� 7�� P Y Y N N Y Y N N B(��1)7�1 P Y Y N N Y Y N N B7�3 P Y Y N N Y Y N N B7�4 P Y Y N N Y Y N N B7�5 P Y Y N N Y Y N N B7�6 P Y Y N N Y Y N N B7�7 P Y Y Y N Y Y N N B7�8 P Y Y N N Y Y N N B7�9 P Y Y N N Y Y N N B7EF P Y Y N N Y Y N N B7FF P Y Y N N Y Y N N A-7��8�� P Y Y N N Y Y N N B8�1 P Y Y N N Y Y N N B8�2 P Y Y N N Y Y N N B8�3 P Y Y N N Y Y N N B8�4 P Y Y N N Y Y N N B8�5 P Y Y N N Y Y N N B8�6 P Y Y N N Y Y N N B8�7 P Y Y N N Y Y N N B8�8 P Y Y N N Y Y N N B8�9 P Y Y N N Y Y N N B8�A P Y Y N N Y Y N N B8�B P Y Y N N Y Y N N B8�C P Y Y N N Y Y N N B8�D P Y Y N N Y Y N N B8�E P Y Y N N Y Y N N B8�F P Y Y N N Y Y N N B81� P Y Y N N Y Y N N B811 P Y Y N N Y Y N N B







��



812 P Y Y N N Y Y N N B813 P Y Y N N Y Y N N B814 P Y Y N N Y Y N N B815 P Y Y N N Y Y N N B816 P Y Y N N Y Y N N B817 P Y Y N N Y Y N N B818 P Y Y N N Y Y N N B819 P Y Y N N Y Y N N B81A P Y Y N N Y Y N N B81B P Y Y N N Y Y N N B81C P Y Y N N Y Y N N B81D P Y Y N N Y Y N N B81E P Y Y N N Y Y N N B81F P Y Y N N Y Y N N B82� P Y Y N N Y Y N N B821 P Y Y N N Y Y N N B822 P Y Y N N Y Y N N B823 P Y Y N N Y Y N N B824 P Y Y N N Y Y N N B825 P Y Y N N Y Y N N B826 P Y Y N N Y Y N N B827 P Y Y N N Y Y N N B828 P Y Y N N Y Y N N B829 P Y Y N N Y Y N N B82A P Y Y N N Y Y N N B82B P Y Y N N Y Y N N B82C P Y Y N N Y Y N N B82D P Y Y N N Y Y N N B82E P Y Y N N Y Y N N B82F P Y Y N N Y Y N N B83� P Y Y N N Y Y N N B831 P Y Y N N Y Y N N B832 P Y Y N N Y Y N N B833 P Y Y N N Y Y N N B834 P Y Y N N Y Y N N B835 P Y Y N N Y Y N N B836 P Y Y N N Y Y N N B837 P Y Y N N Y Y N N B







��



838 P Y Y N N Y Y N N B839 P Y Y N N Y Y N N B83A P Y Y N N Y Y N N B83B P Y Y N N Y Y N N B83C P Y Y N N Y Y N N B83D P Y Y N N Y Y N N B83E P Y Y N N Y Y N N B83F P Y Y N N Y Y N N B84� P Y Y N N Y Y N N B841 P Y Y N N Y Y N N B842 P Y Y N N Y Y N N B843 P Y Y N N Y Y N N B844 P Y Y N N Y Y N N B845 P Y Y N N Y Y N N B846 P Y Y N N Y Y N N B847 P Y Y N N Y Y N N B848 P Y Y N N Y Y N N B849 P Y Y N N Y Y N N B84A P Y Y N N Y Y N N B84B P Y Y N N Y Y N N B84C P Y Y N N Y Y N N B84D P Y Y N N Y Y N N B84E P Y Y N N Y Y N N B84F P Y Y N N Y Y N N B85� P Y Y N N Y Y N N B851 P Y Y N N Y Y N N B852 P Y Y N N Y Y N N B853 P Y Y N N Y Y N N B854 P Y Y N N Y Y N N B855 P Y Y N N Y Y N N B856 P Y Y N N Y Y N N B857 P Y Y N N Y Y N N B858 P Y Y N N Y Y N N B859 P Y Y N N Y Y N N B85A P Y Y N N Y Y N N B85B P Y Y N N Y Y N N B85C P Y Y N N Y Y N N B85D P Y Y N N Y Y N N B







��



85E P Y Y N N Y Y N N B85F P Y Y N N Y Y N N B86� P Y Y N N Y Y N N B861 P Y Y N N Y Y N N B862 P Y Y N N Y Y N N B863 P Y Y N N Y Y N N B864 P Y Y N N Y Y N N B865 P Y Y N N Y Y N N B866 P Y Y N N Y Y N N B867 P Y Y N N Y Y N N B868 P Y Y N N Y Y N N B869 P Y Y N N Y Y N N B86A P Y Y N N Y Y N N B86B P Y Y N N Y Y N N B86C P Y Y N N Y Y N N B86D P Y Y N N Y Y N N B86E P Y Y N N Y Y N N B86F P Y Y N N Y Y N N B87� P Y Y N N Y Y N N B871 P Y Y N N Y Y N N B872 P Y Y N N Y Y N N B873 P Y Y N N Y Y N N B874 P Y Y N N Y Y N N B875 P Y Y N N Y Y N N B876 P Y Y N N Y Y N N B877 P Y Y N N Y Y N N B878 P Y Y N N Y Y N N B879 P Y Y N N Y Y N N B87A P Y Y N N Y Y N N B87B P Y Y N N Y Y N N B87C P Y Y N N Y Y N N B87D P Y Y N N Y Y N N B87E P Y Y N N Y Y N N B87F P Y Y N N Y Y N N B88� P Y Y N N Y Y N N B881 P Y Y N N Y Y N N B882 P Y Y N N Y Y N N B883 P Y Y N N Y Y N N B







��



884 P Y Y N N Y Y N N B885 P Y Y N N Y Y N N B886 P Y Y N N Y Y N N B887 P Y Y N N Y Y N N B888 P Y Y N N Y Y N N B889 P Y Y N N Y Y N N B88A P Y Y N N Y Y N N B88B P Y Y N N Y Y N N B88C P Y Y N N Y Y N N B88D P Y Y N N Y Y N N B88E P Y Y N N Y Y N N B88F P Y Y N N Y Y N N B89� P Y Y N N Y Y N N B891 P Y Y N N Y Y N N B892 P Y Y N N Y Y N N B893 P Y Y N N Y Y N N B894 P Y Y N N Y Y N N B895 P Y Y N N Y Y N N B896 P Y Y N N Y Y N N B897 P Y Y N N Y Y N N B898 P Y Y N N Y Y N N B899 P Y Y N N Y Y N N B89A P Y Y N N Y Y N N B89B P Y Y N N Y Y N N B89C P Y Y N N Y Y N N B89D P Y Y N N Y Y N N B89E P Y Y N N Y Y N N B89F P Y Y N N Y Y N N B8A� P Y Y N N Y Y N N B8A1 P Y Y N N Y Y N N B8A2 P Y Y N N Y Y N N B8A3 P Y Y N N Y Y N N B8A4 P Y Y N N Y Y N N B8A5 P Y Y N N Y Y N N B8A6 P Y Y N N Y Y N N B8A7 P Y Y N N Y Y N N B8A8 P Y Y N N Y Y N N B8A9 P Y Y N N Y Y N N B







��



8AA P Y Y N N Y Y N N B8AB P Y Y N N Y Y N N B8AC P Y Y N N Y Y N N B8AD P Y Y N N Y Y N N B8AE P Y Y N N Y Y N N B8AF P Y Y N N Y Y N N B8B� P Y Y N N Y Y N N B8B1 P Y Y N N Y Y N N B8B2 P Y Y N N Y Y N N B8B3 P Y Y N N Y Y N N B8B4 P Y Y N N Y Y N N B8B5 P Y Y N N Y Y N N B8B6 P Y Y N N Y Y N N B8B7 P Y Y N N Y Y N N B8B8 P Y Y N N Y Y N N B8B9 P Y Y N N Y Y N N B8BA P Y Y N N Y Y N N B8BB P Y Y N N Y Y N N B8BC P Y Y N N Y Y N N B8BD P Y Y N N Y Y N N B8BE P Y Y N N Y Y N N B8BF P Y Y N N Y Y N N B8C� P Y Y N N Y Y N N B8C1 P Y Y N N Y Y N N B8C2 P Y Y N N Y Y N N B8C3 P Y Y N N Y Y N N B8C4 P Y Y N N Y Y N N B8C5 P Y Y N N Y Y N N B8C6 P Y Y N N Y Y N N B8C7 P Y Y N N Y Y N N B8C8 P Y Y N N Y Y N N B8C9 P Y Y N N Y Y N N B8CA P Y Y N N Y Y N N B8CB P Y Y N N Y Y N N B8CC P Y Y N N Y Y N N B8CD P Y Y N N Y Y N N B8CE P Y Y N N Y Y N N B8CF P Y Y N N Y Y N N B







��



8D� P Y Y N N Y Y N N B8D1 P Y Y N N Y Y N N B8D2 P Y Y N N Y Y N N B8D3 P Y Y N N Y Y N N B8D4 P Y Y N N Y Y N N B8D5 P Y Y N N Y Y N N B8D6 P Y Y N N Y Y N N B8D7 P Y Y N N Y Y N N B8D8 P Y Y N N Y Y N N B8D9 P Y Y N N Y Y N N B8DA P Y Y N N Y Y N N B8DB P Y Y N N Y Y N N B8DC P Y Y N N Y Y N N B8DD P Y Y N N Y Y N N B8DE P Y Y N N Y Y N N B8DF P Y Y N N Y Y N N B8E� P Y Y N N Y Y N N B8E1 P Y Y N N Y Y N N B8E2 P Y Y N N Y Y N N B8E3 P Y Y N N Y Y N N B8E4 P Y Y N N Y Y N N B8E5 P Y Y N N Y Y N N B8E6 P Y Y N N Y Y N N B8E7 P Y Y N N Y Y N N B8E8 P Y Y N N Y Y N N B8E9 P Y Y N N Y Y N N B8EA P Y Y N N Y Y N N B8EB P Y Y N N Y Y N N B8EC P Y Y N N Y Y N N B8ED P Y Y N N Y Y N N B8EE P Y Y N N Y Y N N B8EF P Y Y N N Y Y N N B8F� P Y Y N N Y Y N N B8F1 P Y Y N N Y Y N N B8F2 P Y Y N N Y Y N N B8F3 P Y Y N N Y Y N N B8F4 P Y Y N N Y Y N N B8F5 P Y Y N N Y Y N N B



REPORT DATE: Mon Dec 8, 2��3 1�:42:2� SVA SUBSYSTEM CRLEVL1 V�3R�1L�� PAGE 2�




��



8F6 P Y Y N N Y Y N N B8F7 P Y Y N N Y Y N N B8F8 P Y Y N N Y Y N N B8F9 P Y Y N N Y Y N N B8FA P Y Y N N Y Y N N B8FB P Y Y N N Y Y N N B8FC P Y Y N N Y Y N N B8FD P Y Y N N Y Y N N B8FE P Y Y N N Y Y N N B8FF P Y Y N N Y Y N N BF11 P Y Y N N N Y N N BF12 P Y Y N N N Y N N BF13 P Y Y N N N Y N N BF14 P Y Y N N N Y N N BF15 P Y Y N N N Y N N BF16 P Y Y N N N Y N N BF17 P Y Y N N N Y N N BF18 P Y Y N N N Y N N BF19 P Y Y N N N N N N B

CAPACITY SUMMARY -------- ------- SELECTED DEVICES SUMMARY ========================

SELECTED FUNCTIONAL ---- PHYSICAL CAP USED (MB) --- PARTITION DEVICES CAPACITY(MB) SHARED UNIQUE TOTAL

---------- -------- ------------ --------- --------- ---------Production 377 251��58.1 1�636.� 4996.1 15632.1

Test � �.� �.� �.� �.� Overall 377 251��58.1 1�636.� 4996.1 15632.1

SUBSYSTEM SUMMARY ================= TOTAL DISK ARRAY TOTAL FUNC. NET CAP. NET CAP. FREE_SPACE_PCT PARTITION DEVICES CAPACITY(MB) CAPACITY(MB) LOAD(MB) LOAD PCT COLL'D UNCOLL

---------- ------- ------------ ------------ -------- -------- ------ ------Production 377 1868659.8 251��58.1 1�998.7 �.6 99.4 �.�

Test � �.� �.� �.� �.� �.� �.�





��

SUBSYSTEM SUMMARY ================= TOTAL DISK ARRAY TOTAL FUNC. NET CAP. NET CAP. FREE_SPACE_PCT PARTITION DEVICES CAPACITY(MB) CAPACITY(MB) LOAD(MB) LOAD PCT COLL'D UNCOLL

---------- ------- ------------ ------------ -------- -------- ------ ------ Overall 377 1868659.8 251��58.1 1�998.7 �.6 99.4 �.�



REPORT DATE: Mon Dec 8, 2��3 1�:42:2� SVA SUBSYSTEM CRLEVEL2 V�3R�1L�� PAGE: 1



� SUBSYSTEM NAME = MAZUMA � SUBSYSTEM MODEL = V2Xf �� NO. OF CHANNELS = 8 � SITE LOCATION NO. = � �

�� CACHE INFORMATION GENERAL INFORMATION ----- ----------- ------- ----------- CACHE SIZE = 8192 NVS SIZE = 256

INTERFACE --- CHANNEL INTERFACE --- --- CHANNEL --- BASE WORLD WIDENAME CLUSTER ID ENABLED TYPE SPEED IDID RANGE FDID NODE NAME PORT NAME

--------- ------- ------- ------- -------- ----- ---- ----- ---- ---------------- ----------------CHAN�A � A Y FICON 1��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1D�TEST � B Y FICON 1��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1D1TEST � C Y FICON 2��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1D2TEST � D Y FICON 1��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1D3

1 A Y FICON 2��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1D8 XYZ 1 B Y FICON 1��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1D9

1 C Y FICON 2��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1DA1 D Y FICON 1��.� �� 4�96 �� 5��1�4F��6FE1C� 5��1�4F��6FE1DB






� SUBSYSTEM NAME = MAZUMA � SUBSYSTEM MODEL = V2Xf � � DRIVE MODULES = 62 � PHYSICAL CAPACITY = 4599.8(GB) � ��

GENERAL INFORMATION ------- -----------

NUMBER OF SPARES = 17NUMBER OF ARRAYS = 2 DEFAULT GLOBAL SPARES = 1 DEFAULT ARRAY SIZE = 13+2NUMBER OF FUNCTIONAL DEVICES = 4�96 CACHE SIZE = 8192 NVS SIZE = 256REMOTE OPERATOR PANEL STATUS = DISABLE CSRC STATUS = None SCSI SIMS STATUS = DISABLEDNUMBER OF SCSI DOMAINS = � NUMBER OF SCSI TARGETS = � NUMBER OF SCSI LUNS = �

COPYLIM = 1TOT VIRT CYLINDERS = 27353�88 CONFIG VIRT CYLS = 6115596 UNCONFIG VIRTCYLS = 21237492

SUBSYSTEM IDENTIFIERS =

7�� 71�� 72�� 73�� 74�� 75�� 76�� 77�� 78�� 79�� 7A�� 7B�� 7C�� 7D�� 7E�� 7F��

SUPPORTED FEATURES --------- -------- Maintenance SnapShot PPRCFCN PPRCSnapShot

REVISION LEVEL INFORMATION -------- ----- -----------

COMPONENT ID = SRL COMPONENT LEVEL = G�2�1�7��COMPONENT ID = ISP COMPONENT LEVEL = gs�311�7.�COMPONENT ID = IUP COMPONENT LEVEL = gfpav11�8.COMPONENT ID = CIP COMPONENT LEVEL =COMPONENT ID = FIP COMPONENT LEVEL =

DRIVE MODULE INFORMATION ----- ------ -----------


UNAVAILABLE PARTITION � 1 � ��17593 U.B - 71871.5 8 81 � 4 ��1388� U.B - 71871.5 8 82 � � �� U.N - �.� � �2 � 1 �� U.N - �.� � �2 � 2 �� U.N - �.� � �2 � 3 �� U.N - �.� � �2 � 4 �� U.N - �.� � �2 � 5 �� U.N - �.� � �2 � 6 �� U.N - �.� � �2 � 7 �� U.N - �.� � �2 1 � �� U.N - �.� � �








DEVICE-LOCATION SERIAL DEVICE CAPACITY --DEVICE TYPE---UNIT TRAY SLOT NUMBER STATUS ARRAY (MB) CLASS SUB-CLASS---- ---- ---- -------- ------ ----- --------- ----- ---------2 1 1 �� U.N - �.� � �2 1 2 �� U.N - �.� � �2 1 3 �� U.N - �.� � �2 1 4 �� U.N - �.� � �2 1 5 �� U.N - �.� � �2 1 6 �� U.N - �.� � �2 1 7 �� U.N - �.� � �2 2 � �� U.N - �.� � �2 2 1 �� U.N - �.� � �2 2 2 �� U.N - �.� � �2 2 3 �� U.N - �.� � �2 2 4 �� U.N - �.� � �2 2 5 �� U.N - �.� � �2 2 6 �� U.N - �.� � �2 2 7 �� U.N - �.� � �2 3 � �� U.N - �.� � �2 3 1 �� U.N - �.� � �2 3 2 �� U.N - �.� � �2 3 3 �� U.N - �.� � �2 3 4 �� U.N - �.� � �2 3 5 �� U.N - �.� � �2 3 6 �� U.N - �.� � �2 3 7 �� U.N - �.� � �3 � � �� U.N - �.� � �3 � 1 �� U.N - �.� � �3 � 2 �� U.N - �.� � �3 � 3 �� U.N - �.� � �3 � 4 �� U.N - �.� � �3 � 5 �� U.N - �.� � �3 � 6 �� U.N - �.� � �3 � 7 �� U.N - �.� � �3 1 � �� U.N - �.� � �3 1 1 �� U.N - �.� � �3 1 2 �� U.N - �.� � �3 1 3 �� U.N - �.� � �3 1 4 �� U.N - �.� � �3 1 5 �� U.N - �.� � �3 1 6 �� U.N - �.� � �3 1 7 �� U.N - �.� � �








DEVICE-LOCATION SERIAL DEVICE CAPACITY --DEVICE TYPE---UNIT TRAY SLOT NUMBER STATUS ARRAY (MB) CLASS SUB-CLASS---- ---- ---- -------- ------ ----- --------- ----- ---------3 2 � �� U.N - �.� � �3 2 1 �� U.N - �.� � �3 2 2 �� U.N - �.� � �3 2 3 �� U.N - �.� � �3 2 4 �� U.N - �.� � �3 2 5 �� U.N - �.� � �3 2 6 �� U.N - �.� � �3 2 7 �� U.N - �.� � �3 3 � �� U.N - �.� � �3 3 1 �� U.N - �.� � �3 3 2 �� U.N - �.� � �3 3 3 �� U.N - �.� � �3 3 4 �� U.N - �.� � �3 3 5 �� U.N - �.� � �3 3 6 �� U.N - �.� � �3 3 7 �� U.N - �.� � �

UNAVAILABLE PARTITION TOTAL PHYSICAL CAPACITY = 143743.1

MAT PARTITION � � � ��17623 M.A - 71871.5 8 8� � 1 ��17�9� M.A - 71871.5 8 8� � 2 ��18234 M.A - 71871.5 8 8� � 3 ��642 M.A - 71871.5 8 8� � 4 ��17768 M.A - 71871.5 8 8� � 5 ��18531 M.A - 71871.5 8 8� � 6 ��17649 M.A - 71871.5 8 8� � 7 ��3783 M.A - 71871.5 8 8� 1 1 ��18416 M.A - 71871.5 8 8� 1 2 ��19199 M.A - 71871.5 8 8� 1 3 ��1854� M.A - 71871.5 8 8� 1 4 ��18�18 M.A - 71871.5 8 8� 1 5 ��18365 M.A - 71871.5 8 8� 1 6 ��177�2 M.A - 71871.5 8 8� 1 7 ��18�8� M.A - 71871.5 8 8

MAT PARTITION TOTAL PHYSICAL CAPACITY = 1�78�72.9

SPARES PARTITION � 3 6 ��18719 S.A - 71871.5 8 81 2 � ��17851 S.A - 71871.5 8 81 2 1 ��18543 S.A - 71871.5 8 81 2 2 ��14�16 S.A - 71871.5 8 8








DEVICE-LOCATION SERIAL DEVICE CAPACITY --DEVICE TYPE---UNIT TRAY SLOT NUMBER STATUS ARRAY (MB) CLASS SUB-CLASS---- ---- ---- -------- ------ ----- --------- ----- ---------1 2 3 ��13857 S.A - 71871.5 8 81 2 4 ��14243 S.A - 71871.5 8 81 2 5 ��14442 S.A - 71871.5 8 81 2 6 ��17656 S.A - 71871.5 8 81 2 7 ��17351 S.A - 71871.5 8 81 3 � ��18718 S.A - 71871.5 8 81 3 1 ��18�36 S.A - 71871.5 8 81 3 2 ��14�93 S.A - 71871.5 8 81 3 3 ��1413� S.A - 71871.5 8 81 3 4 ��14429 S.A - 71871.5 8 81 3 5 ��14252 S.A - 71871.5 8 81 3 6 ��187�7 S.A - 71871.5 8 81 3 7 ��18�27 S.A - 71871.5 8 8

SPARES PARTITION TOTAL PHYSICAL CAPACITY = 1221816.�

TEST PARTITION Contains No Drives

PRODUCTION PARTITION � 2 � ��187�8 P.A 1 71871.5 8 8� 2 1 ��18393 P.A 1 71871.5 8 8� 2 2 ��19188 P.A 1 71871.5 8 8� 2 3 ��1798� P.A 1 71871.5 8 8� 2 4 ��14528 P.A 1 71871.5 8 8� 2 5 ��18137 P.A 1 71871.5 8 8� 2 6 ��171�6 P.A 1 71871.5 8 8� 2 7 ��18414 P.A 1 71871.5 8 8� 3 � ��17991 P.A 1 71871.5 8 8� 3 1 ��1886� P.A 1 71871.5 8 8� 3 2 ��18544 P.A 1 71871.5 8 8� 3 3 ��14434 P.A 1 71871.5 8 8� 3 4 ��13666 P.A 1 71871.5 8 8� 3 5 ��18398 P.A 1 71871.5 8 8� 3 7 ��17985 P.A 1 71871.5 8 81 � � ��18629 P.A 2 71871.5 8 81 � 1 ��18483 P.A 2 71871.5 8 81 � 2 ��13882 P.A 2 71871.5 8 81 � 3 ��14��4 P.A 2 71871.5 8 81 � 5 ��14459 P.A 2 71871.5 8 81 � 6 ��181�3 P.A 2 71871.5 8 81 � 7 ��171�2 P.A 2 71871.5 8 8


LISTCFG Report Headings






DEVICE-LOCATION SERIAL DEVICE CAPACITY --DEVICE TYPE---UNIT TRAY SLOT NUMBER STATUS ARRAY (MB) CLASS SUB-CLASS---- ---- ---- -------- ------ ----- --------- ----- ---------1 1 � ��17�96 P.A 2 71871.5 8 81 1 1 ��17956 P.A 2 71871.5 8 81 1 2 ��14289 P.A 2 71871.5 8 81 1 3 ��14�84 P.A 2 71871.5 8 81 1 4 ��1423� P.A 2 71871.5 8 81 1 5 ��13416 P.A 2 71871.5 8 81 1 6 ��17634 P.A 2 71871.5 8 81 1 7 ��17343 P.A 2 71871.5 8 8

PRODUCTION PARTITION TOTAL PHYSICAL CAPACITY = 2156145.9


ARRAY INFORMATION ----- -----------

FORMATION SPARE(S) TWO DRIVE GROUP DRAIN D E V I C E S T A T U S E SARRAY PARTITION CONFIG IN PROGRESS NEEDED FAILURE STATUS INITIALIZING DRAINING RECONSTRUCTION----- --------- ------ ----------- -------- --------- ----------- ------------ -------- --------------� H a s N o t B e e n C o n f i g u r e d1 PRODUCTION 13+2 NO NO NO N.A. NO N.A. N.A.2 PRODUCTION 13+2 NO NO NO N.A. NO N.A. N.A.3 H a s N o t B e e n C o n f i g u r e d4 H a s N o t B e e n C o n f i g u r e d5 H a s N o t B e e n C o n f i g u r e d6 H a s N o t B e e n C o n f i g u r e d7 H a s N o t B e e n C o n f i g u r e d

Definitions of LISTCFG Report Headings

The terms that appear as column headings in the reports generated by the LISTCFGsubcommands are defined in the following list in alphabetical order.

ARRAY The number of the array to which a drive module is assigned.

BASE IDID The identifier of the base unit address trapped by the channel.

CA The status of caching for a functional device: Y = enabled;N = disabled.

CACHE SIZE The size (in megabytes) of volatile cache storage (lost if power isremoved).

CAPACITY (MB)The physical capacity (in megabytes) of the drive module.

CHANNEL INTERFACE - CLUSTERThe channel interface cluster identifier (values: 0 or 1).

CHANNEL INTERFACE - IDThe channel interface identifier associated with a specific cluster(values: A through P).



CHANNEL SPEEDThe transfer rate (in megabytes per second) of the channel interface.

CHANNEL TYPEThe type of channel interface: either parallel (bus and tag cables) orESCON or FICON.

CKD ENABL Indicates whether host access to the CKD device has been enabled.

CKD R/W Indicates whether write access to the CKD device is allowed.

COLL'D FREE SPACE PCT(See COLLECTED FREE SPACE %)

COLLECTED FREE SPACE % - OVERALLThe percentage of array cylinders in the subsystem that are free arraycylinders (that is, collected and entirely free of user data).

COLLECTED FREE SPACE % - PRODUCTIONThe percentage of array cylinders in the Production partition that arefree array cylinders.

COLLECTED FREE SPACE % - TESTThe percentage of array cylinders in the Test partition that are freearray cylinders.

COMM The status of a functional device's use for ECAM communications: Y =device is designated to be an ECAM device; N = device is not anECAM device.

COMPONENT ID/COMPONENT LEVELSRL is the microcode (software) release level for the subsystem.

CONFIG The configuration (size) of an array: 5+2 or 13+2.

CONFIG VCYL The total number of configured virtual cylinders that have been definedon this SVA subsystem.

COPYLIM The number of concurrent PPRC pair synchronizations for a givensubsystem across all of the secondary subsystems with which it haspairs.

CYLS The number of primary data cylinders for the functional device.

DEFAULT ARRAY SIZEThe current array size value (defined with the ALTER SUBSYSTEMsubcommand or SUBSYSTEM CONFIGURATION panel). This value, ifnot overridden when an array is formed, determines the size of newlyformed arrays.

DEFAULT GLOBAL SPARESThe minimum number of spare drive modules that must remainavailable on the subsystem for a specific array size. (A 5+2 or 13+2array requires 1 global spare.)

DEVICE STATUSThe current status of a drive module (2 characters: the first identifiesthe partition with which a drive is associated, the second shows thecurrent state of the drive. (Explanations of all drive module statuscodes appear in Appendix A, “Drive Module Status.”)

DEVICE-LOCATION - UNIT/TRAY/SLOTThe drive module location.



DEVICE TYPE - CLASSThe class of a physical drive in the SVA subsystem. Beginning withthe 9500 SVA, CLASS values are not used and the value shown inreports is always zero.

DEVICE TYPE SUB-CLASSThe sub-class of a physical drive in the SVA subsystem. Thesub-classes are defined as follows: 2 = ESDI or SCSI strapped, 3 =SCSI unstrapped, 4 = 4-GB drive, 5 = 9-GB drive, 6 = 18-GB drive, and7 = 36-GB drive.

DFW The status of DASD fast write for a functional device:Y = enabled; N = disabled.

DISK ARRAY CAPACITY (MB)The back-end storage (in megabytes) available in the subsystem(shown for the Production partition, Test partition, and overall).

ECAM The status of a functional device's use as a privileged ECAM device:Y = device is designated to be a privileged ECAM device; N = device isnot a privileged ECAM device.

FDID The SVA subsystem identifier for the functional device (values: 00 -FF).

FREE SPACE PCT(See COLLECTED FREE SPACE %, UNCOLLECTED FREE SPACE %)

FUNCTIONAL CAPACITY (MB)The functional capacity (in megabytes) defined for the device orpartition.

ID (See INTERFACE ID)

INTERFACE IDThe channel interface identifier associated with a specific cluster(values: A through P).

INTERFACE NAMEThe name you assigned to the channel interface.

NAME The name you assigned to the functional device.

NET CAP. LOAD (MB)The back-end physical capacity (in megabytes) that is currently in use.This includes user data and the system areas needed to maintain thearrays. NCL does not include data in the cache until that data iswritten to the back end.

Note: This value includes the storage used by the mapping tablesand functional track directories used to maintain the disk arrays.

NET CAP. LOAD PCTThe percentage of back-end physical capacity that is used (not free).This will display greater than 100% if Capacity on Demand support isinstalled and if PCAP is exceeded.

NUMBER OF FUNCTIONAL DEVICESThe number of functional devices defined with back-end storage in thesubsystem.

NUMBER OF SCSI DOMAINSThe total number of SCSI domains in the subsystem.



NUMBER OF SCSI LUNSThe total number of SCSI logical unit numbers in the subsystem.

NUMBER OF SCSI TARGETSThe total number of SCSI targets in the subsystem.

NVS SIZE The size (in megabytes) of nonvolatile cache storage (backed up bybattery).

OVERALL TOTALSThe sum of the test partition and production partition totals. Forstatistics that are ratios, including percentages, the totals are theweighted averages of the individual statistics.

PAV STATUS The PAV STATUS column indicates whether the device is a PAV Baseor Alias.

The PAV status may be one of the following values:

� B indicates the device is a Base device with no Aliases.� B(nnn) indicates the device is a Base device with nnn Aliases.� A—fff indicates the device is an Alias that is related to Base FDID

of fff.� A—??? indicates that the Alias is in error; contact StorageTek

Software Support.

PHYSICAL CAP USED (MB) - SHAREDThe back-end physical space (in megabytes) that is used (shared) bymultiple functional devices as a result of a SNAP subcommand.

Note: When a SNAP DATASET or SNAP VOLUME subcommand isexecuted, the space (megabytes) used by the source data set orvolume is shifted from the UNIQUE column to the SHARED column.Similarly, the space used by the target data set or volume is shifted tothe SHARED column, as well.

PHYSICAL CAP USED (MB) - UNIQUEThe back-end physical space (in megabytes) that is used by only onefunctional device. Amounts in this column represent space used bydata for which no SNAP subcommand has been executed.

PHYSICAL CAP USED (MB) - TOTALThe total (shared + unique) back-end physical space (in megabytes)that is used by a functional device. Due to snap operations, theTOTAL PHYSICAL CAP USED shown in the Selected Devices Summarycan be much higher than the NET CAP. LOAD(MB) figure shown in theSubsystem Summary section.

Note: The values reported for the three terms above do not includethe storage used by the mapping tables and functional trackdirectories used to maintain the disk arrays.

PPRC STAT The PPRC STAT column indicates whether the device is part of a aPPRC pair and/or whether the device is a Power PPRC Bridge device.

The PPRC pair status is shown in the left side of the column and maytake on one of the following values:

� A blank indicates the device is not part of any PPRC pair.� A P indicates the device is a PPRC Primary.� An S indicates the device is a PPRC Secondary.



The Power PPRC status is shown in the right side of the column andmay take on one of the following values:

� A blank indicates the device is not a Power PPRC Bridge device.� A D indicates the device is a Power PPRC Data Bridge.� As S indicates the device is a Power PPRC Status Bridge.

PRODUCTION PARTITIONIn a Drive Module Configuration report: Statistics for drive modulesthat form Production arrays.

In a Functional Device Configuration report: The totals of the abovestatistics for devices associated with the Production partition. Forstatistics that are ratios, including percentages, the totals are weightedaverages of the individual statistics.

RANGE The number of addresses to be trapped by the channel interface.

SCSI DEVICE ADDRESS - DOMAIN TARGET LUNThe SCSI identifier for the functional device.

SCSI ENABL Indicates whether host access to the SCSI device has been enabled.

SCSI R/W Indicates whether write access to the SCSI device is allowed.

SELECTED DEVICESIn a Functional Device Configuration report: The number of functionaldevices selected by using the FDID, VOLUME, UNIT, or PARTITIONparameters.

In a Drive Module Configuration report: The drive modules selectedby using the DMOD parameter.

SITE LOCATION NO.The number used by StorageTek to identify your site (must be thesame for all SVA subsystems at the site).

SITE NAME The name (up to 8 characters) used by StorageTek to identify yoursite (must be the same for all SVA subsystems at the site).

SSID The subsystem identifier (SSID) for the emulated 3990 controller withwhich the functional device is associated (values: 0001 - FFFF).

SUBSYSTEM IDENTIFIERS(See SSID)

SUBSYSTEM NAMEThe name of the SVAA subsystem to which the report applies.

T/P The partition with which a functional device is associated:T = Test; P = Production.

TEST PARTITIONIn a Drive Module Configuration report: Statistics for drive modulesthat form Test arrays.

In a Functional Device Configuration report: The totals of the abovestatistics for devices associated with the Test partition. For statisticsthat are ratios, including percentages, the totals are weightedaverages of the individual statistics.

TOTAL FUNC. CAPACITY (MB)The total capacity (in megabytes) of all defined functional devices.This is the functional capacity that would be available if every track of


MACRO

every device had a single record with a block length equal to the tracksize.

TOTAL PHYSICAL CAPACITYThe total physical capacity of the drive modules selected or in aspecific partition.

The total physical capacity of all drive modules installed (whether ornot they are assigned to an array) in the SVA subsystem.

Note that total capacity is shown in gigabytes at the end of the DriveModule Configuration report and in megabytes at the end of the Level3 Subsystem Configuration report.

TOTALS A field that shows the production partition and test partition totals. Forstatistics that are ratios, including percentages, the totals are averagesof the individual statistics.

TOT VCYL The total number of virtual cylinders that can be defined on this SVAsubsystem.

TYPE The DASD type of a functional device. Possible values are: 3380-J,3380-K, 3390-KE, 3390-1, 3390-2, 3390-3, 3390-9, SCSIA (3390-3 with SCSIformat), or SCSIB (3390-9 with SCSI format).

UNCOLL FREE SPACE PCT(See UNCOLLECTED FREE SPACE %)

UNCOLLECTED FREE SPACE %The percentage of functional track bytes (in the Test partition,Production partition, and overall) that are free but unavailable(uncollected).

UNCONFIG VCYLThe total number of unconfigured virtual cylinders that remainavailable to be defined on this SVA subsystem.

UNIT The host device address of the functional device as defined in theIOCP.

VOLSER The volume serial number for the functional device.

MACRO Subcommand

* Subcommand of SIBADMIN

The MACRO subcommand executes an SVAA macro.

MACRO

��──MACRO──macroname─ ──┬ ┬──────────── ────────────────────────────────────────────────�� └ ┘ ─parameters─

The macroname parameter specifies the name of the macro to be invoked.

In TSO, the macro is a CLIST or a REXX exec that has a member name ofmacroname and is located in a data set found in the SYSPROC DD statement.


MOVE TESTPARTITION

MOVE TESTPARTITION Subcommand


The MOVE TESTPARTITION subcommand reassigns all drive modules in the Testpartition to the Production partition. All functional device definitions and associateddata are preserved intact on the reassigned drive modules.

Note: You cannot use this subcommand on the V2X, V960, or 9500SVA—only on subsystems running earlier microcode. See “Functional Differencesbetween Subsystems” on page 1-2 for more information.

MOVE TESTPARTITION

��──MOVE TESTPARTition──(─ ──SUBSYStem(subsys) ─)──────────────────────────────────────��

Parameters


This parameter specifies the name of the SVA subsystem in which the move is tooccur.




Default value: None


Example of MOVE TESTPARTITION

MOVE TESTPART (- SUBSYS(YUKON�1) )

This example moves all drive modules associated with the Test partition in SVAsubsystem YUKON�1 to the Production partition of that subsystem.


PPRCOPY

| PPRCOPY Subcommand

| * Subcommand of SIBBATCH or SIBADMIN

| The PPRCOPY subcommand configures the Peer to Peer Remote Copy (PPRC)| paths. This subcommand may be used in place of the TSO or ICKDSF commands| to establish, terminate, and query PPRC paths.

| See the V2X or V2Xf Peer-to-Peer Remote Copy Configuration and User's Guide| for a complete description of PPRC configuration and administration.

| The SVAA PPRCOPY command provides support to establish, terminate, and query| PPRC paths.

| � Non-WWNN domain — For V2X or V2Xf, use the “Serial Number” syntax to| establish the path(s).

| � WWNN domain — For V2Xf, use the “World Wide Node Name” syntax to| establish the path(s). Use this syntax for cascaded switch support (greater than| one FICON switch in series).

| Once PPRC paths have been established, use TSO or ICKDSF to establish PPRC| pairs, and to freeze, terminate, recover, suspend, and run consistency groups.

| PPRCOPY implements command-level security by introducing new resource rules| that can be defined to further enhance your security by implementing restricted or| non-restricted commands. See the SVAA Installation, Customization, and| Maintenance manual, steps 15 and 16, for more information about security| procedures.

| PPRCopy ESTPATH| Use the PPRCopy ESTPATH command to establish ESCON or FCP (FICON)| PPRC paths between a primary (application) site control subsystem and a| secondary (recovery) site control subsystem. Mixing FCP and ESCON paths| between storage subsystems is not allowed.

| PPRCOPY ESTPATH is a “replace” function. Each command can establish up to| four paths for a V2X or eight paths for a V2Xf/V2X4f.

| Each primary virtual control unit (VCU) can, at any one time, be linked to a| maximum of four secondary virtual control units. A separate PPRCOPY ESTPATH| command is required for each VCU.

| Establish Path - V2X or V2Xf in a Non-WWNN Domain

| PPRCOPY ESTPATH - Serial Number|

| ��──PPRCcopy ESTPATH──(─ ──UNIT(unitattr) ──────────────────────────────────────────────�

| �─ ──PRImary(SSID(X'ssid')| ──SerialNumber(serialnum)| ──[VCU(x)]) ─────────────────────────�

| �─ ──SECondary(SSID(X'ssid')| ──SerialNumber(serialnum)| ──[VCU(x)]) ───────────────────────�

| �─ ──LINKS(linkaddrlist) ──┬ ┬───────────────────────────── ──┬ ┬────────────────── ─)─────��| │ │┌ ┐─NO── │ │┌ ┐─OFF─| └ ┘──ConsistencyGROUP( ──┴ ┴─YES─ ) └ ┘──DEBUG( ──┼ ┼─ON── )| └ ┘─CCW─

| Note: VCU is required when more than four paths are requested (PPRCfcn only).| VCU is optional when establishing PPRC paths by serial number and four| or fewer link addresses are specified.


PPRCOPY

| Table 8-2. System Adapter ID (SAID) Values for V2Xf and V2X

| Cluster/Interface| IFC or ICE2| Card Slot| V2Xf SAID Value| V2X SAID Value

| 0/A| 00 Top| X'0000'| X'0000'

| 0/B| 00 Bottom| X'0001'| X'0001'

| 0/C| 01 Top| X'0002'| X'0020'

| 0/D| 01 Bottom| X'0003'| X'0021'

| 0/E| 02 Top| X'0004'| X'0040'

| 0/F| 02 Bottom| X'0005'| X'0041'

| 0/G| 03 Top| X'0006'| X'0060'

| 0/H| 03 Bottom| X'0007'| X'0061'

| 1/A| 10 Top| X'0008'| X'0010'

| 1/B| 10 Bottom| X'0009'| X'0011'

| 1/C| 11 Top| X'000A'| X'0030'

| 1/D| 11 Bottom| X'000B'| X'0031'

| 1/E| 12 Top| X'000C'| X'0050'

| 1/F| 12 Bottom| X'000D'| X'0051'

| 1/G| 13 Top| X'000E'| X'0070'

| 1/H| 13 Bottom| X'000F'| X'0071'

| PRImary (SSID(X'ssid') SerialNumber(serialnum) [VCU(x)]) |

| PRImary (SSID(X'ssid') WWNN(wwnnspec) VCU(x))| Required

| This parameter specifies the primary (application) subsystem. It accepts serial| number or world wide node name syntax.

| Abbreviation: PRI

| Values: SerialNumber(serialnum) is the last 1-8 digits of the frame serial| number for the primary storage subsystem.

| SSID(ssid) is the storage control subsystem ID. ssid is the 4-digit| hexadecimal address of the primary control subsystem.

| VCU(x) is the VCU number for the primary control subsystem and| is identified with a 0-F hexadecimal value. VCU is required for WWNN| and optional for SerialNumber syntax.

| WWNN(wwnnspec) is a 16-digit hexadecimal value containing the| world wide node name of the primary storage subsystem.

| SECondary (SSID(X'ssid') SerialNumber(serialnum) [VCU(x)]) |

| SECondary (SSID(X'ssid') WWNN(wwnnspec) VCU(x))| Required

| This parameter specifies the secondary (recovery) subsystem. It accepts serial| number or world wide node name syntax.


PPRCOPY

| Abbreviation: SEC

| Values: SerialNumber(serialnum) is the last 1-8 digits of the frame serial| number for the secondary storage subsystem.

| SSID(ssid) is the storage control subsystem ID. ssid is the 4-digit| hexadecimal address of the secondary control subsystem.

| VCU(x) is the VCU number for the secondary control subsystem| and is identified with a 0-F hexadecimal value. VCU is required for| WWNN and optional for SerialNumber syntax.

| WWNN(wwnnspec) is a 16-digit hexadecimal value containing the| world wide node name of the secondary storage subsystem.

| UNIT(unitattr)| Required

| This parameter specifies the MVS volume address.

| Values: unitattr is a 3-4 digit hexadecimal address.

| PPRCopy DELPATH| Use the PPRCopy DELPATH command to terminate all PPRC paths between a| primary (application) site control subsystem and a secondary (recovery) site control| subsystem. Only active paths are affected by this command. You may terminate| the paths only if there are no active PPRC pairs.

| Terminate Path - V2X or V2Xf in a Non-WWNN Domain

| PPRCOPY DELPATH - Serial Number|

| ��──PPRCcopy DELPATH──(─ ──UNIT(unitattr) ──────────────────────────────────────────────�

| �─ ──PRImary(SSID(X'ssid')| ──SerialNumber(serialnum)| ──[VCU(x)]) ─────────────────────────�

| �─ ──SECondary(SSID(X'ssid')| ──SerialNumber(serialnum)| ──[VCU(x)]) ───────────────────────�

| �─ ──┬ ┬────────────────── ─)───────────────────────────────────────────────────────────��| │ │┌ ┐─OFF─| └ ┘──DEBUG( ──┼ ┼─ON── )| └ ┘─CCW─

| Note: VCU is required when more than four paths are requested (PPRCfcn only).| VCU is optional when establishing PPRC paths by serial number and four| or fewer link addresses are specified.

| Examples: PPRC DELPATH (UNIT(83��)| PRI(SSID(83�3) SN(��1��2))| SEC(SSID(73�6) SN(��1��1)))

| PPRC DELPATH (UNIT(83��)| PRI(SSID(83�3) SN(��1��2) (VCU(3))| SEC(SSID(73�6) SN(��1��1) VCU(6)))


PPRCOPY

| SECondary (SSID(X'ssid') SerialNumber(serialnum) [VCU(x)]) |

| SECondary (SSID(X'ssid') WWNN(wwnnspec) VCU(x))| Required

| This parameter specifies the secondary (recovery) subsystem. It accepts serial number or| world wide node name syntax.

| Abbreviation: SEC

| Values: SerialNumber(serialnum) is the last 1-8 digits of the frame serial| number for the secondary storage subsystem.

| SSID(ssid) is the storage control subsystem ID. ssid is the 4-digit| hexadecimal address of the secondary control subsystem.

| VCU(x) is the VCU number for the secondary control subsystem and is| identified with a 0-F hexadecimal value. VCU is required for WWNN and| optional for SerialNumber syntax.

| WWNN(wwnnspec) is a 16-digit hexadecimal value containing the world| wide node name of the secondary storage subsystem.




| Default Value: None

| PPRCopy QUERY| Use the PPRCopy QUERY command to display information about PPRC pairs to either a| primary or secondary PPRC volume. PPRC path information is available from the primary| volume only. Output generated by the QUERY command indicates primary and secondary| with respect to the PPRC relationship.

| If a host system is attached only to a primary volume, it cannot obtain status for the| secondary volume for that pair. The same is true for a host that is attached only to a| secondary volume; it cannot obtain status for a primary volume.

| PPRCOPY QUERY Device|

| ��──PPRCcopy QUERY──(─ ──UNIT(unitattr) ──┬ ┬────────────────── ──┬ ┬─────── ─)────────────��| │ │┌ ┐─OFF─ └ ┘──PATHS| └ ┘──DEBUG( ──┼ ┼─ON── )| └ ┘─CCW─

| Examples:

| PPRC QUERY (UNIT(83��))| PPRC QUERY (UNIT(83��) PATHS)

| Parameters




PPRCOPY


| Default Value: None

| DEBUG| Optional








| PATHS| Optional

| This parameter directs the QUERY command to display all paths associated with the PPRC| primary subsystem and the status of each path.

| Example of PPRC QUERY DEVICE Output

| �| �| SIB�7��I �9:29:57 PPRCOPY QUERY (UNIT(83��))| SVAA PPRCOPY QUERY DEVICE - DATE: Tues Sep 19, 2��6 TIME: �9:29:56

| UNIT STATUS DEVTYPE CYLS CUMODEL CUTYPE CRIT CGROUP| ----- ---------- ------- ----- ------- ------ ---- ------| 83�� SIMPLEX 339�-�3 3339 399� ��V2Xf NO NO

| STATE: (�) SIMPLEX| SSID VCU CCA SERIAL # WWNN| ---- --- --- ---------- ----------------| SIMPLEX 83�3 3 �� 1��2 5��1�4F��82155�

| SIB52�1I The QUERY command completed successfully, return code = �.

| �| �

| Figure 8-6. Example of PPRC QUERY DEVICE Output


PPRCOPY

| Example of PPRC QUERY PATHS Output

| �| �| SIB�7��I �9:29:57 PPRCOPY QUERY (UNIT(83��) PATHS)| SVAA PPRCOPY QUERY PATHS - DATE: Tue Sep 19, 2��6 TIME: �9:29:56

| UNIT STATUS DEVTYPE CYLS CUMODEL CUTYPE CRIT CGROUP| ----- ---------- ------- ----- ------- ------ ---- ------| 83�� SIMPLEX 339�-�3 3339 399� ��V2Xf NO NO

| STATE: (�) SIMPLEX

| SSID VCU CCA SERIAL # WWNN| ---- --- --- ---------- ----------------| SIMPLEX 83�3 3 �� 1��2 5��1�4F��82155�

| �� PATH INFORMATION ��

| SSID VCU SERIAL # WWNN| ---- --- ---------- ----------------| SCU.1 73�6 3 ��1��1 5��1�4F��82153�

| PATH PFCA SFCA STATUS DESCRIPTION| ----- ---- ---- ------ -----------| 1 ��1 ��1 �1 PATH ESTABLISHED| 2 ��3 ��3 �1 PATH ESTABLISHED| 3 ��9 ��9 �1 PATH ESTABLISHED| 4 ��B ��B .. PATH ESTABLISHED| 5 .... .... .. NO PATH| 6 .... .... .. NO PATH| 7 .... .... .. NO PATH| 8 .... .... .. NO PATH

| SIB52�1I The QUERY command completed successfully, return code = �.

| �| �

| Figure 8-7. Example of PPRC QUERY PATHS Output


PPRC QUERY Report Headings

| Definitions of PPRC QUERY Report Headings| The terms that appear as column headings in the reports generated by the PPRC QUERY| subcommands are defined in the following list in alphabetical order.

| CCA The 2-digit hexadecimal Channel Connection Address of the primary| volume.

| CRIT Specifies whether CRIT (Yes or No) has been specified for this device.

| CGROUP Specifies whether CGROUP (Yes or No) has been specified for this device.

| CUTYPE Control Unit Type (vendor).

| CUMODEL Control Unit Model emulation.

| CYLS Number of addressable cylinders on the device.

| DEST Displays up to a 4-digit hexadecimal LINK address made up of an outgoing| port (or 00) and a destination VCU. SAID and DEST make up the LINK| address in a non-WWNN domain.

| DEVTYPE Device Model emulation.

| FIRST CYL...| This information is presented only for volumes in duplex pending or| suspended duplex states. If this is a primary volume, this is the lowest| cylinder out of synch on the primary volume. If this is a secondary volume,| this is the lower cylinder number received from the primary which is staged| in cache and not yet written to the secondary volume (and may be affected| by staging in cache).

| LAST CYL... This information is presented only for volumes in duplex pending or| suspended duplex states. If this is a primary volume, this is the highest| cylinder out of sync on the primary volume. If this is a secondary volume,| this is the higher cylinder number received from the primary which is staged| in cache and not yet written to the secondary volume (and may be affected| by staging in cache).

| NUMBER OF TRACKS REMAINING| This is the number of tracks remaining to be copied from a primary to a| secondary PPRC pair. This information is only for primary volumes in| duplex pending or suspended states.

| PATH Logical path number of 1 to 8 for each secondary control unit (SCU.x).

| PFCA The 4-digit hexadecimal System Adapter ID (SAID) for the primary fibre| channel adapter. The PFCA and SFCA make up the LINK address in a| WWNN domain.

| SAID The 4-digit hexadecimal System Adapter ID of the primary storage contol| unit. SAID and DEST make up the LINK address in a non-WWNN domain.

| SERIAL # The 10-digit storage control unit serial number.

| SFCA The 4-digit System Adapter ID for the secondary fibre channel adapter. The| PFCA and SFCA make up the LINK address in a WWNN domain.

| SCU.x The Secondary Control Unit by index value.

| SSID The 4-digit hexadecimal Subsystem ID for the Primary Site Storage Control| Unit.


QUERY CACHEREFRESHRATE

| [12] VCU and link address miscompare.

| [13] Fibre path established.

| [14] Fibre channel path link down.

| [15] Fibre channel path retries exceeded.

| [16] Fibre channel path secondary adapter not PPRC capable.

| [17] Fibre channel path secondary adapter not available.

| [18] Fibre channel path primary login exceeded.

| [19] Fibre channel path secondary login exceeded.

| [nn] Status is undetermined.

| SUBSYSTEM The disk storage subsystem participating in the Peer-to-Peer Remote Copy| configuration.

| UNIT Host addressable device number.

| VCU Virtual Control Unit (synonymous with LSS in ICKDSF or TSO| commands).

| WWNN World Wide Node Name utilized by the Fibre (Ficon) channel protocol.

QUERY Subcommands

QUERY subcommands request the display of information about SVAA.

You use some QUERY subcommands to query a value set by a SET subcommand, by aprofile during initialization, or by default. SVAA responds to these QUERY subcommandswith a statement of the source of the setting, followed by the current value of the setting.SVAA responds to other QUERY subcommands with data in numbered SVAA messages.

QUERY CACHEREFRESHRATE* Subcommand of SIBSFC

This subcommand displays the cache refresh values used by the SVAA Server and thepoint-in-time reports.

QUERY CACHEREFRESHRATE

��──Query CacheRefreshRATE──(─ ──┬ ┬───────────────── ─)────────────────────────────────�� └ ┘ ──┬ ┬─ALLcache──── ├ ┤─ArySTATus─── ├ ┤─FdevPERF──── ├ ┤─FdevPROPs─── ├ ┤─FdevSPAce─── ├ ┤─IntfPERF──── ├ ┤─IntfPROPs─── ├ ┤─PdevPERF──── ├ ┤─PdevSTATus── ├ ┤─SubsysPERF── └ ┘─SubsysPROPs─

Abbreviation: Q CRRATE

Values: ALL displays all cache refresh interval values.

Note: The use of the ALLCACHE parameter is mutually exclusivewith the other parameters. Either use ALLCACHE to query all cacherefresh rates, or query each rate specifically.


QUERY CHECK

ASTAT displays the cache refresh interval for storage array statusinformation.

FPERF displays the cache refresh interval for functional deviceperformance information.

FPROP displays the cache refresh interval for functional device propertiesinformation.

FSPA displays the cache refresh interval for functional device spaceinformation.

IPERF displays the cache refresh interval for I/O interface performanceinformation.

IPROP displays the cache refresh interval for I/O interface propertiesinformation.

PPERF displays the cache refresh interval for physical device performanceinformation.

PSTAT displays the cache refresh interval for physical device statusinformation.

SPERF displays the cache refresh interval for SVA subsystemperformance information.

SPROP displays the cache refresh interval for SVA subsystem propertiesinformation.

Default value: ALL

Response: refresh_interval last set by source: seconds

where refresh_interval is one of the interval types described earlier;source is one of parmlib, subcommand, or default; and seconds isthe interval value.

QUERY CASE* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks whether values of parameters that normally allow lowercasecharacters are automatically translated to uppercase.

QUERY CASE

��──Query CASE───────────────────────────────────────────────────────────────────────��

Abbreviation: Q CASE

Response: CASE last set by source: UPPER or MIXED

where source is one of parmlib, profile, subcommand, or default.

QUERY CHECK* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks whether SVAA subcommand syntax-checking or simulation—orneither—is being performed.


QUERY CMDECHO

QUERY CHECK

��──Query CHECK──────────────────────────────────────────────────────────────────────��

Abbreviation: Q CHECK

Response: CHECK last set by source: NONE or SCAN or SIMU

where source is one of profile, subcommand, or default,

NONE indicates that neither syntax-checking nor simulation is in effect.

SCAN indicates that syntax-checking is in effect.

SIMU indicates that simulation is in effect.

QUERY CMDECHO* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks whether SVAA subcommands are displayed at the destinationspecified by SET DEST OUTMSG before being executed.

QUERY CMDECHO

��──Query CMDEcho────────────────────────────────────────────────────────────────────��

Abbreviation: Q CMDE

Response: CMDECHO last set by source: ON or OFF

where source is one of profile, subcommand, or default.

QUERY CONFIGPATH* Subcommand of SIBSFC

This subcommand asks for the location of the SVAA Server configuration file.

QUERY CONFIGPATH

��──Query ConFiGPaTH─────────────────────────────────────────────────────────────────��

Abbreviation: Q CFGPTH

Response: CONFIGPATH last set by source: pathname

where source is one of parmlib, subcommand, or default.

QUERY DEBUG* Subcommand of SIBSFC

This subcommand asks whether Debug mode is active for the SFC subtask.

QUERY DEBUG

��──Query DEBUG──────────────────────────────────────────────────────────────────────��

Abbreviation: Q DEBUG


QUERY DEVICE

Response: DEBUG last set by source: ON or OFF


QUERY DESTINATION* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the current destination for reports and messages, as set bydefault during SVAA initialization, by execution of a profile, or by a SET DESTINATIONsubcommand.

QUERY DESTINATION

��──Query DESTination─ ──┬ ┬─────────────────── ────────────────────────────────────────�� │ │┌ ┐─ALL───── └ ┘ ─(─ ──┼ ┼─OUTFile─ ─)─ └ ┘─OUTMsg──

Abbreviation: Q DEST

Values: ALL asks for the destinations for both report and message output.

OUTF asks for the destination for configuration reports (for example,LISTCFG subcommand output).

OUTM asks for the destination for message output.

Default value: ALL

Response: OUTMSG last set by source: destinationOUTFILE last set by source: destination

where source is one of profile, subcommand, or default,and destination is one of:

TERMINAL—output goes to the user's terminal.

filename filetype—the name of a file to which report or messageoutput is being sent.

EXEC VARIABLES—output is directed to EXEC stem variables

NULL DESTINATION—output is suppressed

QUERY DEVICE* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for SVA subsystem information about a host device.

Note: You cannot use this subcommand to display information about PAV Alias devicesor Power PPRC Bridge devices. Use the DISPLAY DEVICE or LISTCFG DEVICEsubcommands instead.

QUERY DEVICE

┌ ┐─ ──────��─ ──Query DEVice( ───� ┴─device─ ) ──────────────────────────────────────────────────────��

Abbreviation: Q DEV


QUERY DUMP


You can indicate devices with both lists and ranges.

Response: SVAA messages SIB1868I and SIB1869I.

QUERY DUMP* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks whether a dump is to be created if SVAA terminates abnormally,and, if so, the ID of the TSO user to be notified.

QUERY DUMP

��──Query DUMP───────────────────────────────────────────────────────────────────────��

Abbreviation: Q DUMP

Response: DUMP last set by source: ON or OFF DUMPID=� or id


QUERY ECAMDEVICE* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the addresses of the ECAM devices defined for the specifiedsubsystems (or all subsystems), or for the addresses of devices not currently active asECAM communications devices.

QUERY ECAMDEVICE

��──Query ECAMDEVice─ ──┬ ┬───────────────────────────── ───────────────────────────────�� │ │┌ ┐─ALL─────────────── └ ┘─(─ ──┼ ┼──SUBSYStem(subsys) ─)─ └ ┘─INACTive──────────

Abbreviation: Q ECAMDEV

Values: ALL asks for the addresses of all devices defined as ECAMcommunications devices on all SVA subsystems.

SUBSYS(subsys) asks for the addresses of all ECAM communicationsdevices for subsystem subsys.

INACT asks for the addresses of devices for which a SET ECAMDEVICEsubcommand was issued when the device was offline.

Default value: ALL


QUERY IMPEX* Subcommand of SIBADMIN

This subcommand asks for the status for executing SVAA macros. If IMPEX is on, SVAAmacros are executed (if they exist) before treating the subcommand as an SVAAsubcommand.


QUERY MAXRC

QUERY IMPEX

��──Query IMPex──────────────────────────────────────────────────────────────────────��

Abbreviation: Q IMP

Response: IMPEX last set by source: ON or OFF


QUERY JAVA_HOME* Subcommand of SIBSFC

This subcommand asks for the location of the Java Virtual Machine executable code on theOS/390 server.

QUERY JAVA_HOME

��──Query JAVA_HOME──────────────────────────────────────────────────────────────────��

Abbreviation: Q JAVA_HOME

Response: JAVA_HOME last set by source: pathname


QUERY LOGFILE* Subcommand of SIBSFC

This subcommand asks for the pathname of the server log file.

QUERY LOGFILE

��──Query LogFILE────────────────────────────────────────────────────────────────────��

Abbreviation: Q LFILE

Response: LOGFILE last set by source: pathname


QUERY MAXRC* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the current MAXRC value (the maximum severity return code).

QUERY MAXRC

��──Query MAXRC──────────────────────────────────────────────────────────────────────��

Abbreviation: Q MAXRC

Response: MAXRC last set by source: nn

where source is one of profile, subcommand, or default and nn isthe maximum return code.


QUERY NONICEBERG

QUERY NONICEBERG* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the addresses of devices over which non-SVA subsystemstatistics are obtained.

QUERY NONICEBERG

��──Query NONIceBerg─ ──┬ ┬──────────────────── ────────────────────────────────────────�� │ │┌ ┐─ALL────────

└ ┘──( ──┼ ┼──SSID(ssid) ) └ ┘─INACTive───

Abbreviation: Q NONIB

Values: ALL asks for the addresses of all devices over which statistics areobtained for non-SVA subsystems.

SSID(ssid) asks for the addresses of all devices on subsystem ssid.

INACT asks for the addresses of devices that were offline when the SETNONICEBERG subcommand was issued.

Default value: ALL


QUERY PAGESIZE* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the currently specified number of lines per page for SVAAreports.

QUERY PAGESIZE

��──Query PaGeSiZe───────────────────────────────────────────────────────────────────��

Abbreviation: Q PGSZ

Response: PAGESIZE last set by source: nn

where source is one of profile, subcommand, or default, and nn isthe number of lines per page.

QUERY PARMLIB* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the name of the parmlib member used in the initialization ofSVAA.

QUERY PARMLIB

��──Query PARMlib────────────────────────────────────────────────────────────────────��

Abbreviation: Q PARM


QUERY SERVERNAME

Response: PARMLIB last set by source: member

where source is one of profile, subcommand, environmental, ordefault, and member is the name of the PARMLIB member used in theinitialization of SVAA.

QUERY PROFILE* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the name of the SVAA profile macro.

QUERY PROFILE

��──Query PROFile────────────────────────────────────────────────────────────────────��

Abbreviation: Q PROF

Response: PROFILE last set by source

where source is either PROFSIBA or a filename.

QUERY SERVERIDLETIME* Subcommand of SIBSFC

This subcommand displays the server idle time value used by SVAA Server.

QUERY SERVERIDLETIME

��──Query ServerIdleTime─────────────────────────────────────────────────────────────��

Abbreviation: Q SIT

Response: SERVERIDLETIME last set by parmlib: value

where value is the number of minutes at which the cache refresh cyclehas been set.

QUERY SERVERNAME* Subcommand of SIBSFC

This subcommand asks for the name of the server.

QUERY SERVERNAME

��──Query SeRVerNAME─────────────────────────────────────────────────────────────────��

Abbreviation: Q SRVNAME

Response: SERVERNAME last set by source: servername



QUERY SERVERPROC

QUERY SERVERPROC* Subcommand of SIBSFC

This subcommand asks for the name of the proclib member to be executed when SFC isSTARTed.

QUERY SERVERPROC

��──Query SeRVerPRoC─────────────────────────────────────────────────────────────────��

Abbreviation: Q SRVPRC

Response: SERVERPROC last set by source: procname


QUERY SERVERSCRIPT* Subcommand of SIBSFC

This subcommand asks for the pathname of the script file to be executed when the serveris initialized as a result of STARTing the SFC.

QUERY SERVERSCRIPT

��──Query SeRVerSCRipt───────────────────────────────────────────────────────────────��

Abbreviation: Q SRVSCR

Response: SERVERSCRIPT last set by source: pathname


QUERY SIBHOME* Subcommand of SIBSFC

This subcommand asks for the directory on the OS/390 server into which SVAA wasinstalled for SVAA Server initialization.

QUERY SIBHOME

��──Query SIBHOME────────────────────────────────────────────────────────────────────��

Abbreviation: Q SIBHOME

Response: SIBHOME last set by source: directory


QUERY SIBPORT* Subcommand of SIBSFC

This subcommand asks for the TCP/IP port number of the server executing on a host.

QUERY SIBPORT

��──Query SIBPORT────────────────────────────────────────────────────────────────────��


QUERY TITLEn

Abbreviation: Q SIBPORT

Response: SIBPORT last set by source: port


QUERY SSNAME* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the OS/390 subsystem name assigned for SVAA services.

QUERY SSNAME

��──Query SSName─────────────────────────────────────────────────────────────────────��

Abbreviation: Q SSN

Response: SSNAME last set by source: ssname

where source is one of profile, subcommand, or default, andssname is the name of the OS/390 subsystem assigned for SVAA services.

QUERY SUBSYSTEM* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for information about SVA and non-SVA subsystems.

QUERY SUBSYSTEM

��──Query SUBSYStem─ ──┬ ┬──────────────────── ─────────────────────────────────────────�� │ │┌ ┐─ALL──────── └ ┘──( ──┼ ┼─ICEberg──── ) └ ┘─NONIceBerg─

Abbreviation: Q SUBSYS

Values: ALL asks for information about all SVA and non-SVA subsystems.

ICE asks for information about SVA subsystems only.

NONIB asks for information about non-SVA subsystems only.

Default value: ALL

Response: SVA subsys serial# serial has numdev ECAM devices.

where subsys is the subsystem name, serial is the serial number of thesubsystem, and numdev is the number of ECAM devices defined for theSVA subsystem.

QUERY TITLEn* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the text of a report title line—either Title1 (line 1), Title2(line 2), or Title3 (line 3).

QUERY TITLEn

��─ ──Query TITLEn ────────────────────────────────────────────────────────────────────��


QUERY VERSION

Abbreviation: Q TITLEn (where n is 1, 2, or 3)

Response: TITLEn last set by source: text

where source is one of profile, subcommand, or default, and text isthe text of the title.

QUERY VERSION* Subcommand of SIBBATCH or SIBADMIN

This subcommand asks for the version level of the SVAA software.

QUERY VERSION

��──Query VERSion────────────────────────────────────────────────────────────────────��

Abbreviation: Q VERS

Response: VERSION last set by source: Shared Virtual ArrayAdministrator v.r.m.

where source is one of profile, subcommand, or default, v.r.m isthe version, release, and level of SVAA installed at your location.

QUERY VOLUMEPREFERENCING* Subcommand of SIBBATCH or SIBADMIN* Command issued at VOP

This subcommand queries the current status and processing options of the intercept used toimplement volume preferencing for SnapShot. The status may be active, inactive, or notinstalled.

QUERY VOLUMEPREFERENCING

��──(──Query VOLumePREFerencing─ ──┬ ┬──────────────────── ─)───────────────────────────�� │ │┌ ┐─ ────

└ ┘──SSName( ───� ┴ssname )

The QUERY VOLUMEPREFERENCING subcommand has one parameter.

SSNAME (ssname)Optional

This parameter specifies the names of the OS/390 subsystems for which the status ofvolume preferencing is to be queried.

Abbreviation: SSN

Values: ssname identifies one or more OS/390 subsystems. You can use lists andwildcard characters.

Default value: If this parameter is omitted, SnapShot displays the volume preferencingstatus of all active OS/390 subsystems.

Examples of QUERY VOLUMEPREFERENCINGQuerying the current status of the intercept:


RELEASE DYNAMICDATA

Q VOLPREF (SSN(BUS1))Q VOLPREF (SSN(BUS1 BUS3))Q VOLPREF (SSN(BUS�))

QUERY WEBPORT* Subcommand of SIBSFC

This subcommand identifies the TCP/IP port used by SVAA Web Server.

QUERY WEBPORT

��──Query WEBPORT────────────────────────────────────────────────────────────────────��

Abbreviation: Q WEBPORT

Response: WEBPORT last set by source: port_status

where source is one of parmlib, subcommand, or default; and whereport_status is the number of the Web port or OFF.

RELEASE DYNAMICDATA Subcommand


The RELEASE DYNAMICDATA subcommand enables you to limit the scope of the space tobe managed for DDSR. You can select or exclude specific devices for space release. PAVAlias devices are always excluded for space release even if explicitly selected.

RELEASE DYNAMICDATA

��──RELease DYNamicDATa─ ──┬ ┬─────────────────────── ──────────────────────────────────�� └ ┘ ─(─ ──┬ ┬───────────── ─)─

└ ┘─┤ options ├─

options:├─ ──┬ ┬──────────────────────── ──┬ ┬───────────────────────── ───────────────────────────� │ │┌ ┐─ACTive─── │ │┌ ┐─ ──────

└ ┘──STATus( ──┼ ┼─INACTive─ ) └ ┘──SUBSYStem( ───� ┴─subsys─ ) ├ ┤─SIMUlate─ └ ┘─Query────

�─ ──┬ ┬────────────────────── ──┬ ┬──────────────────────────────── ──────────────────────� │ │┌ ┐─ ────── │ │┌ ┐─ ──────

└ ┘──VOLume( ───� ┴─volser─ ) └ ┘──EXcludeSUBSYStem( ───� ┴─subsys─ )

�─ ──┬ ┬───────────────────────────── ──┬ ┬────────────────── ──┬ ┬────────────────── ───────┤│ │┌ ┐─ ────── └ ┘──DEBUG( ──┬ ┬─ON── ) └ ┘──TRACE( ──┬ ┬─ON── )└ ┘──EXcludeVOLume( ───� ┴─volser─ ) └ ┘─OFF─ └ ┘─OFF─

Parameters

STATUS (ACTIVE | INACTIVE | SIMULATE | QUERY)Optional

This parameter sets or queries the status of the Dynamic DDSR function.

Abbreviation: STAT

Values: ACT activates Dynamic DDSR if it is currently inactive.

INACT suspends Dynamic DDSR if it is currently active.


RELEASE DYNAMICDATA

SIMU activates Dynamic DDSR if it is currently inactive. Space releasefunctions are simulated (all space release functions are performed, butstorage is not actually discarded).

Q displays the current status of Dynamic DDSR.

Default value: ACT

Example: STAT(INACT)

SUBSYSTEM (subsys)Optional

This parameter specifies the name of one or more SVA subsystems to be checked for spacethat can be released.



Note: If a subsystem name contains lowercase characters and SETCASE(UPPER) is in effect, you must enclose the name in matchingquotes.


Default value: If you do not enter any device selection parameter (SUBSYS, VOL,EXSUBSYS, or EXVOL), Dynamic DDSR is performed for all functionaldevices on all installed subsystems.

Examples: SUBSYSTEM(SUB1)SUBSYS(SUBSYS1:SUBSYS2)SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(�)

VOLUME (volser)Optional

This parameter specifies one or more volume serial numbers for which Dynamic DDSR isto be performed.

Abbreviation: VOL


SVAA converts all alphabetics in volsers to uppercase.



Example: VOL(ICE��1 ICE��2 ICE��3)

EXCLUDESUBSYSTEM (subsys)Optional

This parameter specifies the name of one or more SVA subsystems for which space releaseis to be bypassed.

Abbreviation: EXSUBSYS


RELEASE DYNAMICDATA





Examples: EXSUBSYSTEM(SUB1)EXSUBSYS(SUBSYS1)EXSUBSYS('subsysa')

EXCLUDEVOLUME (volser)Optional

This parameter specifies one or more volume serial numbers for which Dynamic DDSR isto be bypassed.

Abbreviation: EXVOL





Example: EXVOL(SYS��1)

DEBUG (ON | OFF)Optional

This parameter enables or disables Dynamic DDSR diagnostic messages.

Values: ON or OFF

Default value: None

Example: DEBUG(ON)

TRACE (ON | OFF)Optional

This parameter enables or disables the generation of Dynamic DDSR GTF tracerecords—useful in resolving problems with the Dynamic DDSR intercept. (This parametershould be set to ON only at the request of StorageTek Customer Support personnel.)

Values: ON or OFF

Default value: None

Example: TRACE(OFF)


RELEASE DYNAMICDATA

Examples of RELEASE DYNAMICDATA Example 1.

RELEASE DYNAMICDATA

The default for the STATUS parameter is taken, and Dynamic DDSR is activated. Thevolume list, if any, is not altered.

Example 2.

REL DYNDAT (- STATUS(ACTIVE)- VOLUME(�) )

Dynamic DDSR is activated. Space release is performed for all volumes.

Example 3. (Entered by the OS/390 operator)

F SVAA,RELEASE DYNAMICDATA (-VOL(ICE��1 ICE��2 ICE��3) )

Dynamic DDSR is activated. Space release is performed for volumes ICE��1, ICE��2, andICE��3. (SVAA is the name of the SVAA started task.)

Example 4.

REL DYNDAT (- EXVOL(SYS��1) )

Dynamic DDSR is activated. Space release is performed for all volumes except SYS��1.

Example 5.

RELEASE DYNAMICDATA (- STATUS(INACT) )

Dynamic DDSR is suspended.

Example 6.

REL DYNDAT (- STATUS(Q) )

The status of Dynamic DDSR is displayed.


RELEASE INTERVALDATA

RELEASE INTERVALDATA Subcommand


The RELEASE INTERVALDATA subcommand requests that the subsystem release the dataspace occupied by volume extents that are no longer in use. You designate volumes andsubsystems to be checked at specified time intervals for space that can be released. To beprocessed, volumes must be online to the host on which Interval DDSR is running. PAVAlias devices are always excluded from space release even if explicitly selected.

Note: You must include at least one device selection parameter (SUBSYS, VOL,EXSUBSYS, or EXVOL) in this subcommand for the specified task to process anyfunctional devices for space release.


��──RELease INTervalDATa──(─ ──RELeaseIDentifier(relid) ──┬ ┬────────────────── ──────────� │ │┌ ┐─NO──

└ ┘──DEFER( ──┴ ┴─YES─ )

�─ ──┬ ┬────────────────────────── ──┬ ┬───────────────────────────── ─────────────────────�│ │┌ ┐─RETain── └ ┘──INTerval( ──┬ ┬──nnnn ──┬ ┬─── )└ ┘──EXTentMAP( ──┴ ┴─DISCard─ ) │ │└ ┘ ─M─

└ ┘──nnH ────────

�─ ──┬ ┬──────────────────── ──┬ ┬───────────────────────── ───────────────────────────────�│ │┌ ┐─NO── └ ┘──REServeLIMit(nn ──┬ ┬─── )└ ┘──REPLACE( ──┴ ┴─YES─ ) └ ┘ ─S─

�─ ──┬ ┬───────────────────────── ──┬ ┬────────────────────── ─────────────────────────────� │ │┌ ┐─ ────── │ │┌ ┐─ ──────

└ ┘──SUBSYStem( ───� ┴─subsys─ ) └ ┘──VOLume( ───� ┴─volser─ )

�─ ──┬ ┬──────────────────────────────── ──┬ ┬───────────────────────────── ───────────────� │ │┌ ┐─ ────── │ │┌ ┐─ ──────

└ ┘──EXcludeSUBSYStem( ───� ┴─subsys─ ) └ ┘──EXcludeVOLume( ───� ┴─volser─ )

�─ ──┬ ┬────────────────── ─)───────────────────────────────────────────────────────────�� │ │┌ ┐─OFF─

└ ┘──DEBUG( ──┴ ┴─ON── )

Parameters

RELEASEIDENTIFIER (relid)Required

This parameter defines a unique name for the DDSR interval task.

Abbreviation: RELID

Values: relid is the release task identifier for this DDSR interval task. You canuse 1 to 16 characters in the set: a to z, A to Z, 0 to 9, $, @, #, -,+, _, &, ., /

Note: If SET CASE(UPPER) is in effect, and you use lowercasecharacters in the release task identifier and don't want them converted touppercase, you must enclose the identifier in matching quotes.

Default value: None

Example: RELID('task�11')



DEFER (YES | NO)Optional

This parameter specifies when the space release task is to begin processing.

Values: NO specifies that the space release task is to begin processingimmediately.

YES specifies that the space release task is to begin processing after thefirst time interval expires.

If the space release task is automatically started when the OS/390operating system is started, it is advisable to specify a YES on any RELINTDAT subcommand in the space release initialization parameters. Thisdelays space release processing and avoids potential volume contentionduring the critical system startup period.

Default value: NO

Example: DEFER(NO)

EXTENTMAP (RETAIN | DISCARD)Optional

This parameter specifies whether the DDSR interval task is to retain the map of free extentson each volume from one interval to the next. The retained extent map is compared to thefree extents on the volume during the next interval process. Retaining the extent mapoptimizes DDSR performance but can miss extents for a data set that is allocated, written,and deleted between intervals.

Abbreviation: EXTMAP

Values: RET specifies that the extent map is to be retained from interval tointerval.

DISC specifies that the space release task is to release all free extents onthe volume.

Default value: RET

Example: EXTMAP(DISC)

INTERVAL (nnnn[M] | nnH)Optional

This parameter specifies the space release interval in either minutes or hours.

Abbreviation: INT

Values: nnnn[M] specifies the number of minutes (0 to 1440) in the interval.Enter 1 to 4 digits; leading zeros are allowed. M is optional.

nnH specifies the number of hours (0 to 24) in the interval. Enter 1 or 2digits; a leading zero is allowed. H is required.

If you specify an interval of zero, the DDSR interval task beginsprocessing immediately. It terminates when space release processing forthe selected devices is complete (a “one-time” space release).

If you specify an interval greater than zero, the interval task remainsactive until it is stopped or suspended. When space release processing iscompleted for the selected devices, the task waits for the specifiedinterval before it resumes processing.



Default value: �M (zero minutes)

Example: INT(�3H)

REPLACE (YES | NO)Optional

This parameter indicates whether parameter values specified in this subcommand are toreplace the corresponding parameter values of a running space release task—if a releasetask with the same relid is already running.

Values: The effects of this parameter depend upon the current status of thespecified space release task:

NO specifies:

� If a space release task with an identical relid is currently running,the REL INTDAT subcommand is rejected.

� If no space release task with the specified relid is currentlyrunning, a new task is started.

YES specifies:

� If a space release task with an identical relid is currently running,the task immediately interrupts its processing, and restarts with thenew parameters.

Note that none of the previous parameter values are retained; youmust include all the necessary parameter values in the currentsubcommand.

� If no space release task with the specified relid is currentlyrunning, a new task is started.

Default value: NO (request to start a new space release task)

Example: REPLACE(NO)

RESERVELIMIT (nn[S] )Optional

This parameter sets the maximum length of time (in seconds) for which the DDSR intervaltask can hold an exclusive RESERVE on a volume.

If the interval task is unable to reserve a volume, it skips the device and continuesprocessing other selected devices. When all selected devices have been processed, theinterval task makes another attempt to process the volumes for which it was unable toobtain the RESERVE. If the second RESERVE fails, the volume is bypassed and processedwhen the next time interval expires.

Abbreviation: RESLIM

Values: nn[S] specifies the number of seconds (1 to 90) for the reserve limit.Enter 1 or 2 digits; a leading zero is allowed. S is optional.

Default value: 15 seconds

Example: RESLIM(1�S)



SUBSYSTEM (subsys)Optional

This parameter specifies the name of one or more SVA subsystems to be checked for spacethat can be released.





Default value: If you do not enter any device selection parameter (SUBSYS, VOL,EXSUBSYS, or EXVOL), no functional devices are processed for spacerelease.


VOLUME (volser)Optional

This parameter specifies one or more volume serial numbers to be checked for space thatcan be released.

Abbreviation: VOL





Example: VOL(PROD�1:PROD25)

EXCLUDESUBSYSTEM (subsys)Optional

This parameter specifies the name of one or more SVA subsystems for which space releaseis to be bypassed.

Abbreviation: EXSUBSYS







Example: EXSUBSYSTEM(SUB1)EXSUBSYS(SUBSYS1)EXSUBSYS(1SUBSYS)

EXCLUDEVOLUME (volser)Optional

This parameter specifies one or more volume serial numbers for which space release is tobe bypassed. Excluded volumes modify and override the list of volumes specified with theVOLUME parameter.

Abbreviation: EXVOL





Example: EXVOL(PROD�1)


This parameter enables or disables Interval DDSR diagnostic messages.

Values: ON or OFF

Default value: OFF

Example: DEBUG(ON)

Examples of RELEASE INTERVALDATA Example 1.

RELEASE INTERVALDATA (- RELID('Work_Vols')- VOL(WORK�)- INT(2H) )

The space release task Work_Vols is to release space at two-hour intervals for allfunctional volumes with a volume serial number starting with WORK on all subsystemsattached to the host in which the subcommand is issued.

Example 2.

REL INTDAT (- RELID(SUBSYSA&B)- INT(45M)- DEFER(YES)- SUBSYS(SUBSYSA SUBSYSB)- EXVOL(PROD�1:PROD�4) )

The space release task SUBSYSA&B is to release space at 45-minute intervals. The taskcontrols space release for all functional volumes on SUBSYSA and SUBSYSB except forvolumes PROD�1 through PROD�4. Processing begins after the first 45-minute interval haspassed.


REPORT EVENTS

Example 3. (Entered by the OS/390 operator)

F SVAA,REL INTDAT (- RELID('DSpaceRelease')- INT(2H) )

The space release task DSpaceRelease is to release space at two-hour intervals. However,no volume or subsystem is specified or excluded, so no volumes will be processed. (SVAAis the name of the SVAA started task.)

REPORT EVENTS Subcommand


The REPORT EVENTS subcommand generates a report on DRAIN events initiated withinthe most recent 60 days. You can limit the content of the report by specifying a singleevent number or by specifying an event type, dates, and/or level of detail.

REPORT EVENTS

┌ ┐─ ──────��──REPORT EVENTS──(─ ──SUBSYStem( ───� ┴─subsys─ ) ────────────────────────────────────────�

�─ ──┬ ┬──IDENTifier(eventid) ───────────────────────────────────────────────────────── ──� └ ┘ ──┬ ┬───────────────────── ──┬ ┬────────────────────────────── ──┬ ┬─────────────── │ │┌ ┐─ ─────── │ │┌ ┐─-7────────────── │ │┌ ┐─SUMmary─

│ ││ │┌ ┐─ALL─── └ ┘──DaTEs( ──┼ ┼──start ──┬ ┬────── ) └ ┘── ──┴ ┴─DETaiL──└ ┘──TYPE( ───� ┴┴ ┴─DRAIN─ ) │ │└ ┘──:end

└ ┘─LAST────────────

�──)─────────────────────────────────────────────────────────────────────────────────��

Parameters


This parameter specifies one or more SVA subsystem names for which events are to bereported.





Default value: None

Examples: SUBSYS(SUBSYS1 SUBSYS2)SUBSYS(SUBSYS1:SUBSYS5)SUBSYS(1SUBSYS)

IDENTIFIER (eventid)Optional

This parameter specifies the SVAA-generated identifier for the event.

Note: If you enter this parameter, you cannot use the TYPE, DATES, orSUMMARY | DETAIL parameters.


REPORT EVENTS

Abbreviation: IDENT

Values: eventid is the identifier of an event: 1 to 10 digits with a value rangingfrom 1 to 4294967295.

Default value: None

Example: IDENT(123456789�)

TYPE ({ ALL DRAIN })Optional

This parameter identifies one or more types of events to be reported.

Note: If you use the IDENT parameter, do not use the TYPE parameter.

Values: ALL specifies that all events are to be included in the report. ALLsupersedes any other entry.

DRAIN specifies that DRAIN events are to be included.

Default value: ALL

Examples: TYPE(DRAIN)TYPE(ALL)

DATES (start [:end] | LAST)Optional

This parameter specifies the dates for events to be included in the report.

Note: If you use the IDENT parameter, do not use the DATES parameter.

The start date and end date cannot be more than 60 days prior to the current date. (Amaximum of 60 days of event data is stored by the SVA subsystem.)

If you specify both start and end, the start date must be earlier than, or equal to, theend date. The report covers the entire day for each date in the range.

If you specify the same date for start and end, the report covers only that one day.

If you specify only a single date (i.e., no end date) the report includes all events from thatdate up to and including the current date and time.

Abbreviation: DTE

Values: start specifies the beginning date for the report period. You can enterit in one of four formats:

ddmmmyyyy A 9-character date string

-nn 1 or 2 digits (1 to 60) preceded by a minus sign, toindicate a number of days prior to the current date

� Specifies today's date.

� Specifies that all 60 dates up to and including the currentdate are to be included in the report period.

end (optional) specifies the last date to be included in the report period.You can enter it in either the ddmmmyyyy or the -nn format. The defaultis today's date.

LAST specifies that the report is to cover only the last event of the typesspecified by the TYPE parameter.


REPORT EVENTS

Default value: -7 (The seven-day period up to and including the current date, exceptwhen you use the IDENT parameter)

Examples: DTE(�) extracts all events for the last 60 days.

DTE(-1�) extracts all events for the 10 days up to and including thecurrent date.

DTE(-8:-2) extracts events for the period from 8 days prior to thecurrent date through 2 days prior to the current date.

DTE(LAST) extracts data for the most recent event.

DTE(�1JAN1999:�1FEB1999) extracts events for all dates within thedate range specified—provided the start date is not more than 60 daysbefore the current date.

SUMMARY | DETAILOptional

This parameter specifies the level of detail for the report.

Note: If you use the IDENT parameter, do not use the SUMMARY | DETAIL parameter.

Abbreviation: SUM or DETL

SUM generates a report that, for each specified event, lists only: eventtype, event identifier, SVA subsystem name, node ID, user ID, and thedate and time the event was initiated and completed.

DETL generates a report that provides detailed information on eachspecified event.

Default value: SUM

Examples of REPORT EVENTS Example 1.

REPORT EVENTS (- SUBSYS(�) )

This example uses default parameter values and provides a summary report of all MAT andDRAIN events initiated within the last seven days in all SVA subsystems with which SVAAis in communication.

Example 2.

REPORT EVENTS (- SUBSYS (SVA�X)- DATES(�5MAY1999)- SUM)

For SVA subsystems with names that begin with SVA and end with X, this exampleprovides a summary report on all events initiated on or after May 5th, 1999, up to andincluding the current date.


RESUME RELEASE

Example 3.

REPORT EVENTS (- SUBSYS (STKSYS1)- IDENTIFIER(7312156748) )

This example provides a detailed report on event number 7312156748 on SVA subsystemSTKSYS1.

Example 4.

REPORT EVENTS (- SUBSYS (�)- DATES(LAST) )

This example produces a summary report on the last MAT event and the last DRAIN eventinitiated in any SVA subsystem in communication with SVAA.

Example 5.

REPORT EVENTS (- SUBSYS (STKSYSA)- DATES(-5)- DETL )

This example produces a detailed report of all events that were initiated in the last fivedays on SVA subsystem STKSYSA.

RESUME RELEASE Subcommand


The RESUME RELEASE subcommand reactivates a suspended DDSR interval task and/orthe Dynamic DDSR intercept. When the task resumes, it starts processing “at thebeginning” (at the first device in a normal pass)—not at the device it was processing whensuspended.

RESUME RELEASE

┌ ┐─ ──────────────────────────��──RESume RELease──(─ ───� ┴┬ ┬──RELeaseIDentifier(relid) ─)─────────────────────────────�� └ ┘─DYNamic──────────────────

Parameters

RELEASEIDENTIFIER (relid)Conditional (You must enter this parameter or the DYN parameter—or both.)

This parameter specifies the DDSR interval task that is to be resumed.

Abbreviation: RELID

Values: relid is a release task identifier defined by the RELEASEINTERVALDATA subcommand.

Note: If the release task identifier contains lowercase characters andSET CASE(UPPER) is in effect, you must enclose it in matching quotes.



SEND

Default value: None

DYNAMICConditional (You must enter this parameter or the RELID parameter—or both.)

This parameter specifies that the Dynamic DDSR intercept is to resume processing.

Abbreviation: DYN

Default value: None

Examples of RESUME RELEASE Example 1.

RESUME RELEASE (- RELID(1234) )

This subcommand reactivates processing by DDSR interval task 1234.

Example 2.

RES REL (- DYNAMIC )

This subcommand reactivates processing by the Dynamic DDSR intercept.

Example 3.

RES REL (- RELID(TASK3�)- DYN )

This subcommand reactivates processing by all DDSR interval tasks with identifiersbeginning with the characters TASK3 and also by the Dynamic DDSR intercept.

SEND Subcommands

The SEND subcommand sends command requests to tasks executing in the SVAA addressspace.

SEND DSR* Subcommand of SIBBATCH or SIBADMIN* System Operator command

The SEND DSR subcommand sends a command request to the DDSR Main Task.

SEND DSR

��─ ──SEND DSR('command') ─────────────────────────────────────────────────────────────��

Values: command is any valid command (1 to 127 characters) enclosed inmatching quotes (single or double).

Default value: None

Examples: From SIBBATCH or SIBADMIN:

SEND DSR('REL INTDAT("task123")')


SEND

From the OS/390 operator console:

F taskname,SEND DSR('STOP RELEASE(RELID(�))')

SEND SFC* Subcommand of SIBBATCH or SIBADMIN* System Operator command

The SEND SFC subcommand sends a command request to the Server FrameworkComponent (SFC) task.

Note: Sending SFC SET subcommands to change parameters such as CONFIGPATH orSIBPORT has no impact; it does not change the Java address space. Java address spacevalues are taken only from parmlib member SIBSFCxx.

SEND SFC

��─ ──SEND SFC('command') ─────────────────────────────────────────────────────────────��


Default value: None


SEND SFC('STOP SFC')


F taskname,SEND SFC('STOP SFC')

SEND SIM* Subcommand of SIBBATCH or SIBADMIN* System Operator command

The SEND SIM subcommand sends a command request to the SVAA Service InformationMessage (SIM) task.

SEND SIM

��─ ──SEND SIM('command') ─────────────────────────────────────────────────────────────��


Default value: None


SEND SIM("QUERY SUBSYSTEM")


F taskname,SEND SIM("QUERY SUBSYSTEM")


SEND

SEND SRP* Subcommand of SIBBATCH or SIBADMIN* System Operator command

The SEND SRP subcommand sends a command request to the Reporter Data Collectiontask.

SEND SRP

��─ ──SEND SRP('command') ─────────────────────────────────────────────────────────────��


Default value: None


SEND SRP("D COLLTN(COLLID('daily'))")


F taskname,SEND SRP('DROP ECAMDEVICE(22�)')

SEND VOP* Subcommand of SIBBATCH or SIBADMIN* System Operator command

The SEND VOP subcommand sends a command request to the console operator interface(virtual operator panel) task.

SEND VOP

��─ ──SEND VOP('command') ─────────────────────────────────────────────────────────────��


Default value: None


SEND VOP('VARY DEVICE (UNIT (345) DISABLE)')


F taskname,SEND VOP('V DEV (UNIT (345) DIS)')


SET CACHEREFRESHRATE

SET Subcommands

The SET subcommands control the setting or define the value of SVAA variables. Thedefault values shown in the subcommand descriptions are the values that are in effect ifyou have not explicitly defined them with the SET subcommand.

Parameter values set with the SET subcommands are not saved from one invocation ofSIBADMIN or SIBBATCH to the next.

SET subcommands issued under SIBADMIN apply only to the current execution ofSIBADMIN (and SIBBATCH does not have access to the variables set under SIBADMIN).Issue SET subcommands for SIBBATCH in a REXX EXEC, or issue them in either theSIBSTK00 parmlib member or in another parmlib member specified with the =PARMLIBparameter of the SIBBATCH command.

SET CACHEREFRESHRATE* Subcommand of SIBSFC

This subcommand sets the cache refresh intervals used by the SVAA Server. These valuesare supplied during initialization of the SVAA Server address space.


��──SET CacheRefreshRATE──(─ ───┤ cache_element ├─ ─)──────────────────────────────────��

cache_element:├─ ──┬ ┬───────────────────────────────────────────── ───────────────────────────────────┤ ├ ┤──┬ ┬────────────────────────────────────── ───

│ │└ ┘──ALLcache( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬─────────────────────────────────────── ──

│ │└ ┘──ArySTATus( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬────────────────────────────────────── ───

│ │└ ┘──FdevPERF( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬─────────────────────────────────────── ──

│ │└ ┘──FdevPROPs( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬─────────────────────────────────────── ──

│ │└ ┘──FdevSPAce( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬────────────────────────────────────── ───

│ │└ ┘──IntfPERF( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬─────────────────────────────────────── ──

│ │└ ┘──IntfPROPs( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬────────────────────────────────────── ───

│ │└ ┘──PdevPERF( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬──────────────────────────────────────── ─

│ │└ ┘──PdevSTATus( ─── ──┤ refresh_interval ├─ ) ├ ┤──┬ ┬──────────────────────────────────────── ─

│ │└ ┘──SubsysPERF( ─── ──┤ refresh_interval ├─ ) └ ┘──┬ ┬─────────────────────────────────────────

└ ┘──SubsysPROPs( ─── ──┤ refresh_interval ├─ )

refresh_interval: ┌ ┐─DeFauLT─├─ ──┼ ┼─OFF───── ───────────────────────────────────────────────────────────────────────┤ └ ┘─seconds─

Point-in-Time ReportsThe settings for the cache refresh intervals determine how data for the point-in-time reportsis collected whether:

� at periodic intervals and saved in the SVAA server's cache

� or only when a report is requested

When a cache refresh rate is set to DEFAULT or a specific number of seconds, a thread iscreated to collect data at the requested interval. There are ten cache types for an SVA. If



each cache type has an associated interval, ten threads are created at SVAA Serverinitialization. An additional ten threads are created for each SVA being monitored.

At its specified interval, the thread collects data and stores it in the SVAA server's cache.When a point-in-time report is requested, the report is generated using data stored in theserver's cache. As a result, the report may represent the statistics from the last collection,but reports are generated quickly.

Note: Care should be taken when setting the refresh interval to a value lower than thedefault (900 seconds) since I/O, CPU, and memory resources may be affected. Be sure tomonitor your resource consumption after switching to a lower interval.

If the cache refresh interval is OFF, no thread is created, and data is not collected atintervals or stored in the server's cache. The use of cache is disabled. However,point-in-time reports can still be generated.

If the cache refresh interval is OFF and a report is requested, I/O is performed to obtainthe data necessary to produce the report. Consequently, reports are not produced until afterall I/O has completed, and producing reports using this method may take longer. On theother hand, the report's data may be more current.

Notes:

1. A SET CACHEREFRESHRATE subcommand has no impact after the SIBSFCxxmember of parmlib is processed.

2. Use the QUERY CACHEREFRESHRATE subcommand to display the currentcache refresh intervals.

3. Use the SET SERVERIDLETIME subcommand to control whether the SVAAserver cache should continue to collect SVA subsystem data during periodswhen the SVAA Server has no requests to process.

CAUTION:The output from the point-in-time reports can not be compared to thatproduced by the SAS reports. Many of the SAS reports use historical datawhich is not available to the point-in-time reports.

ALLCACHE (DeFauLT | OFF | seconds)Optional

This parameter sets the cache refresh rate for all parameters.

Note: The use of the ALLCACHE parameter is mutually exclusive with the otherparameters. Either use ALLCACHE to set all cache refresh rates, or set each ratespecifically.

Abbreviation: ALL

Values: DEFAULT (or DFLT) sets all cache refresh rates to the default of 900seconds.

OFF turns all point-in-time report caching off.

seconds sets all cache refresh rates to the specified number of seconds.Entry must be an integer from 60 to 86400 (1 minute to 24 hours).

Default value: 9�� seconds

Example: ALLCACHE(12��)

ALL(DFLT)



ARYSTATUS (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently storage array cache should be refreshed. Thisinformation includes current array status, such as draining or initializing.

Note: This parameter cannot be used with the ALLCACHE parameter.

Abbreviation: ASTAT

Values: DEFAULT (or DFLT) sets array cache refresh rate to the default of 900seconds.

OFF turns off the collection of array cache statistics.

seconds sets the rate to the specified number of seconds. Entry must bean integer from 60 to 86400.


Example: ASTAT(12��)

FDEVPERF (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently functional device performance cache should berefreshed. This information includes functional device capacity, number of requests perdevice, amount of data transferred, and time available.


Abbreviation: FPERF

Values: DEFAULT (or DFLT) sets the rate to the default of 900 seconds.

OFF turns functional device performance cache off.



Example: FPERF(12��)

FDEVPROPS (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently functional device property cache should berefreshed. This information varies depending on the type of device; it may include devicetype, device address, read/write enables status, ECAM-privlege status, etc.


Abbreviation: FPROP


OFF turns functional device property cache off.



Example: FPROP(12��)



FDEVSPACE (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently functional device space utilization cache should berefreshed. This information includes the number of device tracks available and used.


Abbreviation: FSPA


OFF turns off functional device space utilization cache.



Example: FSPA(DFLT)

INTFPERF (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently the I/O interface performance cache should berefreshed. This information includes I/O interface speed, number of I/Os, amount of timebusy, etc.


Abbreviation: IPERF


OFF turns off the I/O interface performance cache.



Example: INTFPERF(12��)

INTFPROPS (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently the I/O interface properties cache should berefreshed. This information includes I/O interface name, type and status.


Abbreviation: IPROP


OFF turns off the I/O interface properties cache.



Example: IPROP(12��)



PDEVPERF (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently the physical device performance cache should berefreshed. This information includes amount of time a device is busy and the number ofbytes for read/write operations.


Abbreviation: PPERF


OFF turns off the physical device performance cache.



Example: PPERF(12��)

PDEVSTATUS (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently the physical device status cache should berefreshed. This information includes physical device location, current status, arrayassignment, and capacity.


Abbreviation: PSTAT


OFF turns physical device status cache off.



Example: PSTAT(12��)

SUBSYSPERF (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently the subsystem performance cache should berefreshed. This information includes subsystem free space, NCL, back-end capacity, cachesizes, and number of ECAM messages processed and bypassed.


Abbreviation: SPERF


OFF turns off subsystem performance cache.



Example: SPERF(12��)


SET CASE

SUBSYSPROPS (DeFauLT | OFF | seconds)Optional

This parameter specifies how frequently the subsystem properties cache should berefreshed. This information includes installed features, number of devices, and number ofI/O interfaces supported.


Abbreviation: SPROP


OFF turns off subsystem properties cache.



Example: SPROP(12��)

Example of SET CACHEREFRESHRATESET CRRATE(FPERF(16��) FSPA(DFLT) ASTAT(OFF))

Sets the functional device performance cache to 1600 seconds; functional device spacecache is set to the default of 900 seconds. Array status cache is turned off.

SET CASE* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies whether values of parameters that normally allow lowercasecharacters are to be translated automatically to uppercase.

SET CASE

┌ ┐─Upper─��─ ──SET CASE( ──┴ ┴─Mixed─ ) ───────────────────────────────────────────────────────────��

Values: Upper or Mixed

Default value: U

Example: SET CASE(M)

SET CHECK* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies whether SVAA subcommand syntax checking or simulation—orneither one—is to be performed.

SET CHECK

┌ ┐─NONE─────��─ ──SET CHECK( ──┼ ┼─SCAN───── ) ───────────────────────────────────────────────────────�� └ ┘─SIMUlate─


SET CONFIGPATH

Values: NONE turns off both subcommand syntax checking and simulationprocessing.

SCAN turns on subcommand syntax checking. This option enables you tovalidate syntax for an entire batch file before it is executed.

SIMU turns on simulation processing of the DDSR facility. After youissue SET CHECK(SIMU), DDSR performs all space release functionsexcept for actually releasing space; that is, it does no I/O to thesubsystem. Turn simulation off with SET CHECK(NONE).

Default value: NONE

Example: SET CHECK(SCAN)

SET CMDECHO* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies whether SVAA subcommands are to be displayed at thedestination specified by SET DEST OUTMSG before execution.

SET CMDECHO

��─ ──SET CMDEcho( ──┬ ┬─ON── ) ──────────────────────────────────────────────────────────�� └ ┘─OFF─

Abbreviation: SET CMDE

Values: ON or OFF

Default value: ON for SIBBATCHOFF for SIBADMIN

Example: SET CMDE(ON)

SET CONFIGPATH* Subcommand of SIBSFC

This subcommand specifies the location of the SVAA Server configuration file.

Note: A SET CONFIGPATH subcommand has no impact after parmlib is processed.

SET CONFIGPATH

��─ ──SET ConFiGPaTH( pathname) ────────────────────────────────────────────────────────��

Abbreviation: SET CFGPTH

Values: pathname is 1 to 1024 characters, mixed case. It must conform to UNIXdirectory and file naming conventions.

Default value: $SIBHOME/install

where $SIBHOME is the value of SIBHOME

Example: SET CFGPTH(/home/svaa1.1/config)


SET DEBUG

SET DEBUG* Subcommand of SIBSFC

This subcommand specifies whether Debug mode is active for the SFC subtask.

Note: A SET DEBUG subcommand has no impact after parmlib is processed.

SET DEBUG

��─ ──SET DEBUG( ──┬ ┬─ON── ) ────────────────────────────────────────────────────────────�� └ ┘─OFF─

Values: ON or OFF

Default value: OFF

Example: SET DEBUG(ON)

SET DESTINATION* Subcommand of SIBBATCH or SIBADMIN

This subcommand enables you to redirect messages (via OUTMsg) and reports (via OUTFile)to alternate destinations. SET DESTINATION does not affect the destination of:

� SAS reports (Device Performance, Cache Effectiveness, and Space Utilization reports)� Command output or messages generated by ISPF requests (you must use REXX

variables)� Messages normally sent to SIBLOG, such as Interval DDSR messages

Note: You can redirect the output of any individual SVAA subcommand, thus overriding(for only that subcommand) the destination you specify with SET DESTINATION. For moreinformation, see “Redirecting Subcommand Output” on page 8-10.

SET DESTINATION

┌ ┐─ ───────────────────────── │ │┌ ┐─DeFauLT──��──SET DESTination──(─ ───� ┴┬ ┬──OUTFile( ──┼ ┼─filespec─ ) ─)─────────────────────────────�� │ │├ ┤─OFF────── │ │├ ┤─TERMinal─ │ │└ ┘─VARiable─ │ │┌ ┐─DeFauLT── └ ┘──OUTMsg( ──┼ ┼─filespec─ ) ─ ├ ┤─OFF────── ├ ┤─TERMinal─ └ ┘─VARiable─

Abbreviation: SET DEST

Values: OUTF redirects report output (for example, LISTCFG subcommand output)to the destination indicated by the subparameter value.

OUTM redirects a message to the destination indicated by the subparametervalue.

The subparameter is one of the following:

filespec Direct output to the file filespec (a SAS/C-style filename).

filespec has a maximum of 48 characters.


SET DUMP

Note: In the TSO environment, follow standard data setnaming conventions; that is, enclose a data set name inquotes if it is fully qualified.

DeFauLT In OS/390 batch, OUTFile defaults to the destinationspecified by the SYSPRINT DD name. OUTMsg defaults tothe destination specified by the SYSTERM DD name.

In TSO, both destinations default to TERMINAL.

In ISPF, both destinations default to VARIABLE.

OFF Suppress output.

TERMinal Display output at the terminal.

VARiable Direct output to exec stem variables (not valid inSIBBATCH environment).

SVAA output for destination OUTMSG is written to stemvariable SIBLMSG.n. This allows a REXX EXEC to issuean SVAA subcommand and analyze the returned results(messages and reports) in REXX variables.

Output for destination OUTFILE is written to the stemvariable SIBRMSG.n (n is the value of an occurrence ofSIBLMSG or SIBRMSG).

The variables with n=0 contain the number of variablesgenerated. For example, if SIBRMSG.0=17, then variablesSIBRMSG.1 through SIBRMSG.17 contain the data. TheSIBRMSGn and SIBLMSGn variables are set to 0 before theexecution of each SVAA subcommand.

Note: REXX must be available to use this value.

Default value: DFLT

Example: SET DEST(OUTFILE(ddn:systst) OUTMSG(VAR) )

SET DUMP* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies whether a dump is to be produced if SVAA terminatesabnormally. Additionally, you have the option of specifying a TSO userid to be notifiedthat the abend occurred.

SET DUMP

┌ ┐─OFF────────────────────��─ ──SET DUMP( ──┴ ┴ ─ON─ ──┬ ┬──────────────── ) ──────────────────────────────────────────��

└ ┘──DumpID(userid)

Values: ON or OFF and optionally: DID(userid)

userid is 1 to 8 characters

Default value: OFF

userid defaults to the user executing the subcommand.

Example: SET DUMP(ON DID(MAINT9) )


SET ECAMDEVICE

SET ECAMDEVICE* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies devices (as defined to the host) to be used for ECAMcommunications. You can specify multiple (up to 100) ECAM devices.

You must include the SET ECAMDEVICE subcommand in the PROFSIBA REXX EXEC (ifyou are using it), and in any of the following parmlib members you are using: SIBSTK,SIBSFC, SIBSIM, SIBSRP, and SIBVOP.

Notes:

1. Do not specify a device that does not exist or has not been mapped.

2. If you issue this subcommand while the target device is offline, the device isconsidered inactive and does not appear in response to a QUERY ECAMDEVICE(ALL) subcommand.

3. Do not issue this subcommand against a PPRC primary or secondary volume;that is, do not try to define a PPRC volume as an ECAM device.

4. You cannot use this subcommand on PAV Alias or Power PPRC Bridgedevices.

SET ECAMDEVICE

┌ ┐─ ────��─ ──SET ECAMDEVice( ───� ┴device ) ──────────────────────────────────────────────────────��

Abbreviation: SET ECAMDEV

Values: device is a host device number (1 to 4 hexadecimal digits). The devicemay be offline to OS/390.

You can specify both lists and ranges of devices.

Default value: None

Example: SET ECAMDEV(2aE 73� 112D)

SET IMPEX* Subcommand of SIBADMIN

This subcommand specifies the setting for the implied execution of SVAA macros. IfIMPEX is ON, an SVAA subcommand is treated as a potential SVAA macro. If the macrodoes not exist, normal SVAA subcommand processing is performed.

Note: If you specify IMPEX(ON), there should not be any members in the CLISTconcatenation with the same name as any SVAA subcommand or its abbreviation.

SET IMPEX

┌ ┐─OFF─��─ ──SET IMPex( ──┴ ┴─ON── ) ────────────────────────────────────────────────────────────��

Abbreviation: SET IMP

Values: ON or OFF

Default value: OFF

Example: SET IMPEX(OFF)


SET MAXRC

SET JAVA_HOME* Subcommand of SIBSFC

This subcommand specifies the location of the Java Virtual Machine executable code onthe OS/390 server.

Note: A SET JAVA_HOME subcommand has no impact after parmlib is processed.

SET JAVA_HOME

��─ ──SET JAVA_HOME( pathname) ─────────────────────────────────────────────────────────��


Default value: /usr/lpp/java/J1.1

Example: SET JAVA_HOME(/usr/lpp/java/J1.1)

SET LOGFILE* Subcommand of SIBSFC

This subcommand is used by SVAA Server initialization to specify the pathname of theserver log file.

Note: A SET LOGFILE subcommand has no impact after parmlib is processed.

SET LOGFILE

��─ ──SET LogFILE( pathname) ───────────────────────────────────────────────────────────��

Abbreviation: SET LFILE


Default value: $SIBHOME/SVAA-ServerLog


Example: SET LFILE(/home/svaa1.1/SrvrLog)

SET MAXRC* Subcommand of SIBBATCH or SIBADMIN

For SVAA initialization, this subcommand sets the maximum return code (severity) thatwill be accepted from the initialization routines and the SVAA profile macro and still allowinitialization to continue.

SIBBATCH also uses MAXRC to specify the maximum return code value SVAA toleratesfrom a subcommand. Any return code that exceeds the MAXRC value causes SIBBATCHto terminate processing and ignore any remaining subcommands in the input file.

SET MAXRC

��─ ──SET MAXRC(code) ─────────────────────────────────────────────────────────────────��

Values: code is an unsigned integer ≥ 0.


SET NONICEBERG

Default value: 8

Example: SET MAXRC(12)

SET NONICEBERG* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies devices (as defined to the host) over which non-SVA subsystemstatistics are obtained.

Note: If you issue this subcommand while the target device is offline, the device isconsidered inactive and does not appear in response to a QUERY NONICEBERG (ALL)subcommand.

SET NONICEBERG

┌ ┐─ ────��─ ──SET NONIceBerg( ───� ┴device ) ──────────────────────────────────────────────────────��

Abbreviation: SET NONIB

Values: device is a host device number (1 to 4 hexadecimal digits). The devicemay be offline to OS/390.

You can specify devices with both lists and ranges.

Default value: None

Example: SET NONIB(333 2aa)

SET PAGESIZE* Subcommand of SIBBATCH or SIBADMIN

This subcommand specifies the number of lines per page for SVAA reports.

SET PAGESIZE

��─ ──SET PaGeSiZe(lines) ─────────────────────────────────────────────────────────────��

Abbreviation: SET PGSZ

Values: lines is a 2-digit number ranging from 40 to 99.

Default value: 6�

Example: SET PGSZ(55)

SET SERVERIDLETIME* Subcommand of SIBSFC

This subcommand enables you to control whether the SVAA server cache should continueto collect SVA subsystem data during periods when the SVAA Server has no requests toprocess. This value is supplied during initialization of the SVAA Server address space.

When cache is refreshed, threads are created to collect data depending on the intervalsspecified by the SET CACHEREFRESHRATE subcommand. I/O is performed to the SVAsubsystem, and system resources are consumed. The SET SERVERIDLETIMEsubcommand can be used to reduce the amount of system resources required to keep thedata in cache current.


SET SERVERPROC

The time specified by SET SERVERIDLETIME indicates the number of minutes that haveelapsed since the last request for cache data. Once the threshold has been reached, thecache refresh cycle is suspended until the next time information from cache is requested.At this time, I/O to the subsystem is performed, and the cache refresh cycle resumes.

SET SERVERIDLETIME

��─ ──SET ServerIdleTime( ──┬ ┬─DeFauLT─ ) ───────────────────────────────────────────────�� ├ ┤─OFF───── └ ┘─minutes─

Abbreviation: SET SIT

Values: minutes specifies that the cache refresh cycle may be suspended if nocache requests have been received in the specified number of minutes.Value must be an integer from 1 to 10080 minutes (seven days).

DeFauLT sets the idle time to 60 minutes.

OFF causes the Server cache to always be active.

Default value: 6�

Example: SET SIT(9�)

SET SERVERNAME* Subcommand of SIBSFC

This subcommand is used by SVAA Server initialization to specify a unique name for theSVAA Server. You should assign a different name for each server.

Note: A SET SERVERNAME subcommand has no impact after parmlib is processed.

SET SERVERNAME

��─ ──SET SeRVerNAME( servername) ──────────────────────────────────────────────────────��

Abbreviation: SET SRVNAME

Values: servername is 1 to 27 characters, mixed case.

Default value: SVAA-Server

Example: SET SRVNAME(ABCserver)

SET SERVERPROC* Subcommand of SIBSFC

This subcommand is used by SVAA Server initialization to specify the name of the proclibmember to be executed when SFC is STARTed.

Note: A SET SERVERPROC subcommand has no impact after parmlib is processed.

SET SERVERPROC

��─ ──SET SeRVerPRoC( procname) ────────────────────────────────────────────────────────��

Abbreviation: SET SRVPRC

Values: procname is a 1-to-8 character standard OS/390 PDS member name.


SET SERVERSCRIPT

Default value: SVAASRVR

Example: SET SRVPRC(IBSRVR)

SET SERVERSCRIPT* Subcommand of SIBSFC

This subcommand is used by the SVAA Server to specify the pathname of the script file tobe executed when the server is initialized as a result of STARTing the SFC.

Note: A SET SERVERSCRIPT subcommand has no impact after parmlib is processed.

SET SERVERSCRIPT

��─ ──SET SeRVerSCRipt( pathname) ──────────────────────────────────────────────────────��

Abbreviation: SET SRVSCR


Default value: $SIBHOME/bin/sibserv


Example: SET SRVSCR(/home/svaa1.1/SIBSERV)

SET SIBHOME* Subcommand of SIBSFC

This subcommand is used by SVAA Server initialization to specify the OS/390 serverdirectory into which SVAA was installed. It sets the default directory value for SETCONFIGPATH, SET LOGFILE, and SET SERVERSCRIPT.

Note: A SET SIBHOME subcommand has no impact after parmlib is processed.

SET SIBHOME

��─ ──SET SIBHOME( directory) ──────────────────────────────────────────────────────────��

Values: directory is 1 to 1024 characters, mixed case. It must conform toUNIX directory naming conventions.

Default value: /svaa1.1

Example: SET SIBHOME(/home/svaa1.1)

SET SIBPORT* Subcommand of SIBSFC

SVAA Server initialization uses this subcommand to specify the TCP/IP port number of theserver executing on a host. When connecting to a server from the user interface, you mustspecify either a host name or an IP address and port number.

Note: A SET SIBPORT subcommand has no impact after the SIBSFCxx member ofparmlib is processed.


SET VOLPREF

SET SIBPORT

��─ ──SET SIBPORT( sibport) ────────────────────────────────────────────────────────────��

Values: sibport is a TCP/IP port number (1 to 65535).

Default value: 22753

Example: SET SIBPORT(12345)

SET SSNAME* Subcommand of SIBBATCH or SIBADMIN

This subcommand identifies the OS/390 subsystem that is to perform SVAA services (thatis, the subsystem to which subsequent SVAA commands will be directed). You wouldnormally use this subcommand only to perform installation verification after installing anew release of SVAA.

SET SSNAME

��─ ──SET SSName( ──┬ ┬─DeFauLT─ ) ───────────────────────────────────────────────────────�� └ ┘─ssname──

Abbreviation: SET SSN

Values: ssname is the name of the OS/390 subsystem that is to perform SVAAservices.

DEFAULT (or DFLT) sets ssname to the name of the first activated OS/390subsystem running SVAA.

Example: SET SSN(IBM3)

SET TITLEn* Subcommand of SIBBATCH or SIBADMIN

This subcommand (SET TITLE1, SET TITLE2, or SET TITLE3) defines the text string (suchas an organization name or address) that is to appear in one of the three title lines of SVAAreports. n is 1 (line 1), 2 (line 2), or 3 (line 3). SVAA converts all titles to uppercase.

SET TITLEn

��─ ──SET TITLEn('text') ──────────────────────────────────────────────────────────────��

Values: text is a text string (0 to 127 characters).

The text must be enclosed in parentheses and either single or doublequotation marks. However, if the text string contains no blanks, thequotation marks are optional.

Default value: None

Example: SET TITLE1('Line 1 of report title')

SET VOLUMEPREFERENCING* Subcommand of SIBBATCH or SIBADMIN* Subcommand issued at VOP


SET VOLPREF

This subcommand sets the current status (either active or inactive) of the intercept used toimplement volume preferencing for the named OS/390 subsystems.

This subcommand has effect only when the volume preferencing intercept was set to activeor inactive mode during SVAA initialization. If the volume preferencing intercept was notinstalled during SVAA initialization, this subcommand has no effect.

SET VOLUMEPREFERENCING Subcommand

��──SET VOLumePREFerencing──(─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────── ────� │ │┌ ┐─ ──── │ │┌ ┐─Active───

└ ┘──SSName( ───� ┴ssname ) └ ┘──STATus( ──┴ ┴─Inactive─ )

�─ ──┬ ┬────────────────── ──┬ ┬────────────────── ─)─────────────────────────────────────�� │ │┌ ┐─OFF─ │ │┌ ┐─OFF─

└ ┘──DEBUG( ──┴ ┴─ON── ) └ ┘──TRACE( ──┴ ┴─ON── )

The parameters of the SET VOLUMEPREFERENCING subcommand follow in alphabeticalorder.


This parameter enables or disables the generation of volume preferencing diagnosticmessages.

Note: This option should be set on only at the request of your service representative. Alarge amount of output can be generated at the console.

Abbreviation: DEBUG

Values: ON enables diagnostic messages to be generated.

OFF disables diagnostic messages from being generated.

Default value: OFF

Example: DEBUG(ON)

SSNAME (ssname)Optional

This parameter specifies the names of the OS/390 subsystems for which the status ofvolume preferencing is to be changed, as specified by the STATUS parameter.

Abbreviation: SSN

Values: ssname identifies one or more OS/390 subsystems. You can use lists andwildcard characters.

Default value: If this parameter is omitted, the volume preferencing status of all OS/390subsystems with SnapShot enabled is set to the value specified in theSTATUS parameter, or if not specified, to the default status, ACTIVE.

Examples: SSN(BUS1)SSN(BUS1 BUS3)

STATUS (ACTIVE | INACTIVE)Optional

This parameter specifies the status of the SnapShot volume preferencing intercept.

Abbreviation: STAT


SET WEBPORT

Values: ACTIVE enables the intercept and implements volume preferencing.

INACTIVE disables the intercept and prevents volume preferencing.

Default value: ACTIVE

Example: STATUS(I)


This parameter specifies whether GTF TYPE=USR trace records are to be generated by thesubcommand. GTF records may be used to facilitate troubleshooting of SETVOLUMEPREFERENCING subcommand processing. This parameter should only be used atthe request of your service representative.

For the TRACE parameter to be effective, you must start an active trace with GTFTYPE=USR before executing the SET VOLUMEPREFERENCING subcommand.

Note: Some of the information resulting from TRACE(ON) may be of use only to yourservice representative.

Abbreviation: TRACE

Values: ON enables trace records to be generated.

OFF disables trace records from being generated.

Default value: OFF

Example: TRACE(ON)

Example of SET VOLUMEPREFERENCINGSET VOLPREF( SSN(HQ5) STAT(I) DEBUG(OFF) TRACE(OFF) )

This example sets the intercept to inactive status and disables all messages and tracerecords.

SET WEBPORT* Subcommand of SIBSFC

This subcommand identifies the TCP/IP port to be used by the SVAA Web Server. Thisvalue is supplied to the SVAA Server during initialization of the SVAA Server addressspace.

Notes:

1. The SVAA Web Server is also called the SVAA Web-based interface or WBIand is used to generate the point-in-time reports.

2. A SET WEBPORT subcommand has no impact after the SIBSFCxx member ofparmlib is processed.

SET WEBPORT

┌ ┐─ ────── │ │┌ ┐─OFF──��─ ──Set WEBPORT( ───� ┴┴ ┴─port─ ) ───────────────────────────────────────────────────────��

Values: port is the TCP/IP port to be used for communication between SVAAWeb Server and the SVAA Server. The port number must be an integerfrom 1024 to 65535.


SNAP DATASET

Default value: OFF

Example: SET WEBPORT(61384)

SNAP DATASET Subcommand


This subcommand duplicates (“snaps”) one of the following types of data sets:

� Physical Sequential (PS) data sets� Partitioned (PO) data sets� Direct access (DA) data sets� Extended Partitioned data sets (PDSE)� Extended format sequential data sets� Striped Sequential data sets� Multivolume data sets� The following types of VSAM data sets:

- Alternate Index (AI) - ESDS - KSDS - Linear - RRDS - VRRDS - Extended Format

The source and target data sets may reside on the same functional device or differentfunctional devices. However, you cannot use SnapShot to snap between devices withdifferent track sizes, such as from 3380s to 3390s. PAV Alias devices cannot be used asthe source or target of SNAP DATASET.

CAUTION:Power PPRC Bridge devices are not intended for use as data storage devices.You should not attempt to ICKDSF initialize and/or vary any Bridge deviceonline to a host operating system, since all user and system data (forexample, VTOCs) can be destroyed during the establishment of a Power PPRCBridge pair. Therefore, you should not attempt to use SnapShot to snap datato or from Power PPRC Bridge devices.


SNAP DATASET

SNAP DATASET

��──SNAP DataSet──(─ ──┬ ┬──SOUrce(dsname) ── ──┬ ┬──TaRGet(dsname) ─── ─────────────────────�└ ┘──INDDname(ddname) └ ┘──OUTDDname(ddname)

�─ ──┬ ┬──────────────────────── ──┬ ┬──────────────────── ──┬ ┬────────────────────── ──────�│ │┌ ┐─ ────── │ │┌ ┐─Yes─ └ ┘──DATACLASs(classname)├ ┤──VOLume( ───� ┴─volser─ ) ── └ ┘──CATalog( ──┴ ┴─No── )└ ┘──ESOteric(esotericname)

�─ ──┬ ┬────────────────────────────── ──┬ ┬────────────────── ──┬ ┬────────────────── ──────� │ │┌ ┐─NONE──── │ │┌ ┐─OFF─ │ │┌ ┐─No──

└ ┘──DataMoverNaMe( ──┼ ┼─ADRDSSU─ ) └ ┘──DEBUG( ──┴ ┴─ON── ) └ ┘──FORCE( ──┴ ┴─Yes─ ) ├ ┤─DFDSS─── └ ┘─DSS─────

�─ ──┬ ┬─────────────────────── ──┬ ┬─────────────────────────────── ──────────────────────� │ │┌ ┐─DELETE─ │ │┌ ┐─EXClusive─

└ ┘──ERRDISP( ──┴ ┴─KEEP─── ) └ ┘──HostCoPYMODE( ──┴ ┴─SHaRed──── )

�─ ──┬ ┬──────────────────────────── ──┬ ┬───────────────────────── ──┬ ┬──────────────── ───�└ ┘──ManaGeMenTCLASs(classname) └ ┘──STORageCLASs(classname) └ ┘──RELate(dsname)

�─ ──┬ ┬──────────────────── ──┬ ┬────────────────── ──┬ ┬─────────────────────────────── ───� │ │┌ ┐─No── │ │┌ ┐─OFF─ │ │┌ ┐─No──

└ ┘──REPLace( ──┴ ┴─Yes─ ) └ ┘──TRACE( ──┴ ┴─ON── ) └ ┘──TOLerateENQFailure( ──┴ ┴─Yes─ )

�─ ──┬ ┬─────────────────────────────── ──┬ ┬────────────────────────── ─)────────────────��│ │┌ ┐─No── └ ┘──VOLumeCouNT(volumecount)└ ┘──TOLerateTRUNCation( ──┴ ┴─Yes─ )

ParametersThe parameters of the SNAP DATASET subcommand follow in alphabetical order.

CATALOG (YES | NO)Optional

When SnapShot dynamically allocates the target data set, this parameter determineswhether a new target data set is to be cataloged when it is created by the SNAP DATASETsubcommand. SnapShot supports Integrated Catalog Facility (ICF) catalog entries only.

Note: This parameter is for new data sets only. It is not used to evaluate or controlexisting non-cataloged target data sets, and has no effect on source data sets.

Abbreviation: CAT

Values: YES specifies that the allocated target data set is to be cataloged.

NO specifies that the allocated target data set is not to be cataloged. Thisoption is supported only for target data sets that must be created and arenot SMS managed.

Notes:

1. CAT(N) is ignored for SMS-managed data sets, because SMSonly allows the creation of cataloged data sets onSMS-managed volumes.

2. CAT(N) is ignored when the OUTDDNAME parameter is used.

3. CAT(N) is ignored for VSAM data sets.

4. If you specify CAT(N) for a PDSE data set, SnapShot issues amessage and catalogs the target data set.

Default value: YES

Example: CAT(N)


SNAP DATASET

DATACLASS (classname)Optional

This parameter specifies the SMS data class to be assigned to the target data set.

Abbreviation: DATACLAS

Values: classname specifies a locally defined data class to be assigned to thetarget data set.

Note: Contact your storage administrator to determine the valid dataclass names for your site.

Default value: None.

Security: You must have SAF or equivalent authorization for the data classspecified.

Example: DATACLAS(DCLASSX)

Notes:

1. SnapShot ignores this parameter if you specify OUTDDNAME.

2. No attempt is made to update data class information for an existing data set.

3. SnapShot will not assign the source data class to a target data setautomatically. You must ensure that the correct data class is assigned to thetarget data set by using the DATACLASS parameter or ACS selection.

DATAMOVERNAME (NONE | ADRDSSU | DFDSS | DSS)Optional

Snapping requires a data mover when the source and target data sets do not reside in thesame SVA subsystem and partition. This parameter specifies a data mover program tophysically copy the data set in cases when you cannot use SnapShot.

SnapShot dynamically invokes the data mover and supplies the commands to accomplishthe snap operation physically. A message notifies you that the data mover is beinginvoked.

The DFSMSdss utility control statement for a data set is:

COPY TRACK() OUTTRACKS() CANCELERROR PURGE OPTIMIZE(4)

If you do not specify the DATAMOVERNAME parameter and the data mover is needed, orif SnapShot is unable to access the data mover, the operation is cancelled. All copiesmade with a data mover mimic the physical copying nature of SnapShot (they are tracklevel, not logical).

Abbreviation: DMNM

Values: NONE specifies that a data mover is not to be used.

ADRDSSU, DFDSS, or DSS is the name of the data mover to be used (eachrefers to the IBM DFSMSdss utility).

Default value: NONE

Example: DMNM(ADRDSSU)


SNAP DATASET

Notes:

1. The time required to copy a data set of numerous tracks can be significantbecause the data mover program completes the entire copy operation beforereturning control to the user.

2. If you do not specify this parameter and the target is neither located nor createdwithin the same SVA subsystem and partition as the source, the snap operationterminates.


This parameter enables or disables the logging of diagnostic messages. Use it only at therequest of your service representative.

Abbreviation: DEBUG

Values: ON enables generation of diagnostic messages.

OFF disables generation of diagnostic messages.

Default value: OFF

Example: DEBUG(ON)

Note: Some of the information resulting from DEBUG(ON) may be of use only to yourservice representative.

ERRDISP (KEEP | DELETE)Optional

When SnapShot dynamically allocates the target data set, this parameter specifies whetherthe target data set will be kept or deleted when an error occurs.

Abbreviation: None

Values: KEEP specifies that the target data set will be kept if an error occurs.

DELETE specifies that the target data set will be deleted if an erroroccurs.

Default value: DELETE

Example: ERRDISP(KEEP)

ESOTERIC (esotericname)Conditional. You cannot also specify the VOLUME parameter. Use only with theTARGET parameter.

This parameter specifies the device group name of the DASD devices onto which thesource data set is snapped.

Abbreviation: ESO

Values: esotericname specifies the name of the generic locally defined group.


Example: ESO(DASD)


SNAP DATASET

Notes:

1. Using this parameter has no effect on cataloged, preallocated data sets.2. This parameter is not supported for VSAM targets.3. SnapShot ignores this parameter if you specify OUTDDNAME.4. The ESOTERIC parameter cannot be used for multivolume non-SMS target

data sets.

FORCE (YES | NO)Optional

This parameter allows you to snap a data set that was created as absolute track (ABSTR) oras unmovable (PSU, POU or DAU). SnapShot makes no attempt to ensure that the targetdata set will be accessible. SnapShot does not allocate absolute track locations.

Unless FORCE is enabled, the target for an unmovable or absolute track data set mustreside or be allocated on a different device from that of the source and at the samephysical track location as the source.

Abbreviation: None.

Values: YES specifies that an unmovable or absolute track data set can besnapped to a different physical track location on the same or anotherdevice.

Note: This option is required to snap an unmovable data set. It is notrequired to snap an absolute track data set if the space allocated for thetarget data set is preallocated on a target device at the same physicaltrack location as the source device. SnapShot does not allocate absolutetrack data sets. In this case, the OUTDDNAME parameter must be used.

NO specifies that an unmovable or absolute track data set is not to besnapped unless the target location is identical to the source.

Default value: NO

Example: FORCE(Y)

HOSTCOPYMODE (SHARED | EXCLUSIVE)Optional

This parameter specifies the level of serialization control to be obtained for the source andtarget data sets. See the SVA SnapShot for OS/390 Installation, Customization, andMaintenance guide for a description of serialization.

Abbreviation: HCPYMODE

Values: SHARED specifies the use of dynamic allocations with a disposition ofSHR. Choose this option if you want to modify the source or targetduring a snap operation.

Note: If the target is a VSAM data set, it must be closed beforesnapping. Otherwise the snap will fail and a message will be issued.The target data set must have the ability to get SHARE OPTION 1,1.

EXCLUSIVE specifies use of the dynamic allocations with disposition ofOLD. Exclusive control offers better protection of data integrity thanshared control. Choose this option if you want exclusive control overthe source or target during a snap operation.

Default value: EXCLUSIVE


SNAP DATASET

Example: HCPYMODE(SHR)

Notes:

1. SnapShot ignores this parameter for data sets specified by INDDNAME orOUTDDNAME.

2. If you are attempting to snap a data set previously opened within a Data BaseManagement System (DBMS) for which update activity has not been quiesced,you cannot obtain exclusive control because the data base has not been closedor deallocated. In this case, choosing the SHARED option actually providesuser managed exclusive control.

3. Use the HCPYMODE(SHARED) parameter if you know that the data set is sharedby another job; this uses less overhead than the TOLENQF(Y) parameter.

4. If the data set is held DISP=OLD, the allocation fails—even if TOLENQF(Y) isused.

5. If the data set is held DISP=SHR, the allocation success is determined asfollows:

HCPYMODE(EXCLUSIVE) TOLENQF(N) Allocation will fail.HCPYMODE(EXCLUSIVE) TOLENQF(Y) Allocation will succeed with DISP=SHRHCPYMODE(SHARED) TOLENQF(N) Allocation will succeed with DISP=SHRHCPYMODE(SHARED) TOLENQF(Y) Allocation will succeed with DISP=SHR

INDDNAME (ddname)Conditional. You must specify either this parameter or the SOURCE parameter.

This parameter specifies the DD statement that refers to a preallocated source data set to besnapped.

Abbreviation: INDD

Values: ddname identifies the DD statement that refers to the data set to besnapped. You should select a ddname that resolves to a data set and notto a device. DD name concatenation is not supported.


Example: INDD(DATADDIN)

Note: You must use this parameter if the source data set is not cataloged.

MANAGEMENTCLASS (classname)Optional

When SnapShot dynamically allocates the target data set, this parameter specifies the SMSmanagement class to be assigned to the target data set.

Abbreviation: MGMTCLAS

Values: classname specifies a locally defined management class to be assignedto the target data set.

Note: Contact your storage administrator to determine the validmanagement class names for your site.


Security: You must have SAF or equivalent authorization for the management classspecified.


SNAP DATASET

Example: MGMTCLAS(SITEMMCL)

Notes:


2. Local SMS ACS routines may place the target data set in a management classother than that specified by this parameter. As with all SMS data sets,specifying management class is only a suggestion to SMS and may or may notbe accepted by SMS.

3. No attempt is made to update management class information for an existingdata set.

4. SnapShot will not assign the source management class to a target data setautomatically. You must ensure that the correct management class is assignedto the target data set by using the MANAGEMENTCLASS parameter or ACSselection.

OUTDDNAME (ddname)Conditional. You must specify either this parameter or the TARGET parameter.

This parameter specifies the DD statement that refers to a preallocated target data set to besnapped to. You can use this parameter independently of INDDNAME.

When the source and target data sets do not reside on the same SVA subsystem andpartition, you can specify a valid data mover to complete the snap (see theDATAMOVERNAME parameter).

Abbreviation: OUTDD

Values: ddname identifies a DD name that refers to the preallocated target dataset. DD name concatenation is not supported.


Example: OUTDD(DATADDOUT)

Notes:

1. You cannot snap a data set onto itself. Therefore, the or INDDNAME parametercannot specify the same data set as the OUTDDNAME parameter, unless both:

� The target data set is on another volume than the source, and� You specify DISP=(,KEEP) in the DD statement for the target data set.

2. You must select a ddname that resolves to a data set and not to a device.

3. If this parameter is specified, SnapShot ignores volume preferencing (see“Using Volume Preferencing” on page 5-9).

4. If you use this parameter, SnapShot ignores the CATALOG, DATACLASS,ESOTERIC, HOSTCOPYMODE, MANAGEMENTCLASS, STORAGECLASS,TOLERATEENQFAILURE, VOLUME, and VOLUMECOUNT parameters for the targetdata set.

5. You cannot specify DISP=MOD for the data set named by this parameter.

6. You must use the OUTDDNAME parameter if the target data set is notcataloged.


SNAP DATASET

RELATE (dsname)Optional

This parameter specifies the name of the base cluster to which the target alternate index isto be related. The base cluster can be an entry-sequenced cluster or a key-sequencedcluster. You cannot relate an alternate index to a reusable cluster, to a relative recordcluster, or to a VVDS (data set name 'SYS1.VVDS.VVOLSER'). An SMS-managed alternateindex has the same management class and storage class as its base cluster.

The dsname specified in this parameter must be cataloged in the same catalog as the targetalternate index.

If this parameter is not specified, and the object of the SnapShot operation is an alternateindex, the target data set will be related to the same base cluster as the source data set.

The UPGRADE/NOUPGRADE attribute of the target alternate index will match the sourcealternate index.

Abbreviation: REL

Values: dsname specifies the name of the data set to which the target alternateindex will relate. The dsname can contain 1 to 44 alphanumeric ornational ($ @ #) characters, and two special (- {) characters, in “nodes”of one to eight characters separated by periods. Do not use a numeric(0-9) or special character (- or {) as the first character of any node.

In the TSO environment, OS/390 will prefix your user ID to your data setname. Enclose the data set name in quotes to prevent prefixing.


Security: You must have SAF ALTER or equivalent authorization for the data setspecified in the RELATE parameter.

Example: RELATE(SPSL1.BASE.CLUSTER)

REPLACE (YES | NO)Optional

This parameter specifies whether the source data set is to overwrite any data in an existingtarget data set. If the target data set is allocated OLD or SHR, and you do not specify YESfor this parameter, the snap operation terminates.

When the source data set is larger than the allocated space of the target data set, SnapShotattempts to obtain sufficient additional target extents needed to hold the source data, basedon the source allocation.

Abbreviation: REPL

Values: YES specifies that the existing target data set is to be overwritten.

NO specifies that the existing target data set is not to be overwritten.

Default value: NO

Example: REPL(Y)

Note: Use this parameter with caution because some data sets may appear to be emptywhen they actually contain data.


SNAP DATASET

SOURCE (dsname)Conditional. You must specify either this parameter or the INDDNAME parameter.

This parameter specifies the name of the data set to be snapped. To use SnapShot, boththe source and target data sets must resolve to compatible devices within the same SVAsubsystem and partition. All extents for the source data set must reside on devices that arecurrently online and accessible.

The data set is located by using the standard catalog search sequence. Use the INDDNAMEparameter if the data set is not cataloged. The source data set name must be different fromthe target dataset name.

For a list of the types of data sets that you can snap and a list of data sets that are notsupported by SnapShot, see page 5-4.

Abbreviation: SOU

Values: dsname is the name of the source data set: 1 to 44 alphanumeric ornational ($ @ #) characters, and 2 special (- {) characters, in “nodes” ofone to eight characters separated by periods. Do not use a numeric (0-9)or special character (- or {) as the first character of any node.

Notes:

1. Lists, ranges, and wildcards are not allowed.

2. PAV Alias devices cannot be used as the source of a snap.


Security: You must have SAF READ or equivalent authorization for the source dataset.

Example: SOURCE(PAYROLL.EMPLOYEE.MASTER) identifies the source by standarddata set name.

STORAGECLASS (classname)Conditional. Use only with the TARGET parameter.

This parameter requests an SMS storage class for a newly allocated target data set.

Abbreviation: STORCLAS

Values: classname specifies the locally defined list of storage attributes requiredfor the target data set.

Note: Contact your storage administrator to determine the valid storageclass names for your site.


Security: You must have SAF or equivalent authorization for the storage classrequested.

Example: STORCLAS(SITESSCL)

Notes:

1. SnapShot will not assign the source storage class to a target data setautomatically. You must ensure that the correct storage class is assigned tothe target data set by using the STORAGECLASS parameter or ACS selection.

2. SnapShot attempts to preference devices on the same SVA subsystem thatcontains the source device (see “Using Volume Preferencing” on page 5-9 for


SNAP DATASET

more information). If all source and target devices are not on the same SVAsubsystem and partition, SnapShot either uses a data mover to accomplish thecopy (if DATAMOVERNAME(DSS) is specified) or terminates the snap operation.

3. Local SMS ACS routines may place the target data set in a storage class otherthan that specified by this parameter. As with all SMS data sets, specifyingstorage class is only a suggestion to SMS and may or may not be accepted bySMS.


TARGET (dsname)Conditional. You must specify either this parameter or the OUTDDNAME parameter.

This parameter specifies the name of the target data set. To use SnapShot, both the sourceand target data sets must be on the same SVA subsystem and partition. All extents for thetarget data set must reside on devices that are currently online and accessible. If volumepreferencing is active, and if you are creating the target or obtaining secondary extents,SnapShot preferences SVA target volumes and volumes within the same SVA subsystem asthe source.

When the source and target data sets do not reside on the same SVA subsystem andpartition, you can specify a valid data mover to complete the snap (see theDATAMOVERNAME parameter).

For new non-VSAM target allocations, SnapShot copies the LSTAR, TRBAL, BLKSIZE,DSORG, RECFM, LRECL, RKP and KEYLEN attributes from the source data set to the targetdata set. For non-VSAM preallocated target data sets where the above DCB attributes donot match the source data set, SnapShot copies the LSTAR, TRBAL, BLKSIZE, RECFM,LRECL, RKP and KEYLEN attributes from the source data set to the target data set. TheDSORG of the target data set must match that of the source data set or the snap will fail.

Abbreviation: TRG

Values: dsname is the name of the target data set: 1 to 44 alphanumeric ornational ($ @ #) characters, and 2 special (- {) characters, in “nodes” ofone to eight characters separated by periods. Do not use a numeric (0-9)or special character (- or {) as the first character of any node.

Note: Lists, ranges, and wildcards are not allowed.


Security: You must have SAF CREATE and UPDATE or equivalent authorizationfor the target data set. SnapShot opens the data set for output to makesure the requestor has access to the target.

Example: TARGET(PAYROLL.EMPLOYEE.SNAP) identifies the target by standard dataset name.

Notes:

1. You cannot snap a data set onto itself. Therefore, the INDDNAME parametercannot specify the same data set as the OUTDDNAME parameter unless both:

� The target data set is on a different volume from the source, and� You specify CATALOG(NO) for a new non-SMS target data set.

2. You cannot specify the same data set name on both the SOURCE and TARGETparameters. Use the INDDNAME/OUTDDNAME parameters to snap an identicallynamed uncataloged data set to another volume.


SNAP DATASET

3. PAV Alias devices cannot be used as the target of a snap.

TOLERATEENQFAILURE (YES | NO)Optional

This parameter enables you to snap data sets when exclusive serialization control overthem cannot be obtained. Integrity of the data set cannot be assured. If you also specifyHOSTCOPYMODE(EXCL), you must use this parameter to snap a data set that is unavailableat the exclusive serialization level. (The SVA SnapShot for OS/390 Installation,Customization, and Maintenance guide discusses resource serialization.)

Abbreviation: TOLENQF

Values: YES enables the snapping of a data set that is unavailable at the exclusiveserialization level.

NO specifies that the data set is not to be snapped if it is unavailable atthe exclusive serialization level.

Default value: NO

Example: TOLENQF(Y)

Notes:

1. SnapShot ignores this parameter for source data sets accessed via theINDDNAME parameter and for target data sets accessed via the OUTDDNAMEparameter.

2. SnapShot cannot allocate a source or target data set that is already held asOLD.

TOLERATETRUNCATION (YES | NO)Optional

This parameter allows a data set to be truncated and a warning message to be issued if thetarget extent size is smaller than the source. Otherwise, if the target cannot be extended,the snap fails. SnapShot truncates the data set only if it cannot allocate more space.Truncation may cause loss of data.

Abbreviation: TOLTRUNC

Values: YES enables the truncation of a data set snapped to a smaller data set.

NO specifies that the data set is not to be truncated if the target is smallerthan the source data set. The snap fails.

Default value: NO

Example: TOLTRUNC(Y)

Notes:

1. This option has no effect on VSAM, PDSE, Striped, or Extended Addressabilitydata sets, as these data sets never allow truncation.

2. If the target data set cannot be allocated as large as the source data set (x37),SnapShot allows the snap operation but truncates the data being snapped tothe size of the target data set.

3. This parameter is active only when the target data set requires more spacethan its primary allocation.


SNAP DATASET


This parameter specifies whether GTF TYPE=USR trace records are to be generated by thesubcommand. GTF records can be used to facilitate troubleshooting of SNAP DATASETsubcommand processing.

For the TRACE parameter to be effective, you must start an active trace with GTFTYPE=USR before executing the SNAP DATASET subcommand.

Note: You should use this parameter only at the request of your service representative.

Abbreviation: TRACE



Default value: OFF

Example: TRACE(ON)

VOLUME (volser)Conditional. You cannot also specify the ESOTERIC parameter. Use only with theTARGET parameter.

This parameter specifies the target volume to which the data set is to be snapped.

When the source data set and the target volume do not reside on the same SVA subsystemand partition, you must specify a valid data mover to perform the copy operation.

The snap operation terminates when SnapShot makes a request to obtain an extent and:

� You supply volumes that do not exist.� An allocation cannot be satisfied on the specified volume.� The VOLUME parameter does not resolve to an eligible device (the specified device

has an invalid device type, is offline, or is unknown).

Abbreviation: VOL

Values: volser specifies the volume serial number of a device that is online tothe host attempting the snap.

Default value: None

Examples: VOL(BKUP44)VOL(BKUP44 BKUP45 BKUP46)

Notes:

1. Using this parameter has no effect on preallocated data sets.

2. If this parameter is used in an SMS environment, guaranteed space is requiredor SMS could ignore the request for a target volume.



SNAP DATASET

VOLUMECOUNT (volumecount)Optional

This parameter specifies the maximum number of volumes on which a new target data setcan be allocated.

Abbreviation: VOLCNT

Values: volumecount specifies the maximum number of volumes on which thetarget data set can be allocated. It must be a decimal number from 1 to255 without quotes.

Default value: None

Example: VOLCNT(4)

Notes:

1. SnapShot ignores this parameter if you specify OUTDDNAME or VOLUME.

2. SnapShot ignores this parameter for striped data sets.

3. For SMS data sets, VOLCNT will translate volumes to candidate volumes.

4. If you omit this parameter, SnapShot attempts to use the same number ofvolumes for the target as are used for the source.

Examples of SNAP DATASET Example 1.

SNAP DATASET ( SOURCE ('PROD.R1.DATA') -TARGET ( PROD.R1.DATA.SNAP ) )

This example snaps a data set, not allowing a data mover to be used (because no datamover is specified):

Example 2.

SNAP DATASET (INDDNAME (MASTER) OUTDDNAME (SNAP) REPLACE (YES))

This example snaps a data set, specified by the DD name MASTER to an existing data set,specified by the DD name SNAP, overwriting any data that may already be in the target dataset.

Example 3.

SNAP DATASET ( SOURCE (PROJECT1.OUTPUT.FILE) -TARGET (SNAP.PROJECT1) STORCLAS (PROJ1) -

TOLENQF (YES))

This example snaps a data set, to a target to be allocated using the storageclass PROJ1.The snap is to proceed even if exclusive serialization is not obtained for the source.

Example 4.

SNAP DATASET ( SOURCE ('DATA.SVA#1.FILE') -TARGET (BACKUP.SVA#1.FILE) VOLUME(PACK�1) -

HCPYMODE(SHR))

This example snaps a data set, that is being shared by another job to a target that will beallocated on volume PACK�1.


SNAP VOLUME

SNAP VOLUME Subcommand


This subcommand duplicates a single volume to another volume. You can snap onlybetween volumes of the same device type and model.

For data integrity reasons, target volumes shared in a multi-host environment should beoffline to all hosts except the host executing the snap operation.

Notes:

1. Volumes that are offline may be snapped if SNAP VOLUME's OFFLINEparameter has been specified. The offline devices must have a path availableand have been mapped in the SVAA device mapping tables (during subsysteminitialization or reinit).

2. You can snap a SCSI volume to an OS/390 3390 volume if the SCSI volume hasbeen initialized with a device number or volser. (This is done with the INITparameter of the DEFINE DEVICE subcommand or with the INITIALIZE DEVICEsubcommand.) However, you cannot snap an OS/390 volume to a SCSI volume.

3. PAV Alias devices can not be used as the source or target of a volume snap.

4. VM CPVOLUMEs can be used as the target of a volume snap if theRELOCATE=NO parameter is specified.

5. If you are requesting PPRC Remote SnapShot, some of the SNAP VOLUMEparameters are invalid and others are ignored. Refer to the SNAP VOLUMEparameter descriptions for more information.

CAUTION:Power PPRC Bridge devices are not intended for use as data storage devices.You should not attempt to ICKDSF initialize and/or vary any Bridge deviceonline to a host operating system, since all user and system data (forexample, VTOCs) can be destroyed during the establishment of a Power PPRCBridge pair. Therefore, you should not attempt to use SnapShot to snap datato or from Power PPRC Bridge devices.

Note: It is recommended that the volume status be set to DISNEW on all systems forSMS-managed target volumes before the SNAP VOLUME subcommand is issued.


SNAP VOLUME

SNAP VOLUME

��──SNAP VOLume──(─ ─── ───SOUrce( ──┬ ┬──VOLume(volser) ────────────────────── ) ───────────�├ ┤──INDDname(ddname) ────────────────────└ ┘──UNIT(device) ──┬ ┬────────────────────

│ │┌ ┐─No──└ ┘──OFFline( ──┴ ┴─Yes─ )

�─ ─── ───TaRGet( ──┬ ┬──VOLume(volser) ────────────────────── ) ────────────────────────────�├ ┤──OUTDDname(ddname) ───────────────────├ ┤──UNIT(device) ──┬ ┬────────────────────

│ ││ │┌ ┐─No──│ │└ ┘──OFFline( ──┴ ┴─Yes─ )├ ┤──RemoteFunctionalDeviceID(fdid) ──────└ ┘──SerialNumber(fraserno) ──────────────

�─ ──┬ ┬────────────────────────────── ──┬ ┬────────────────────────────── ────────────────� │ │┌ ┐─NONE──── │ │┌ ┐─ALL───

└ ┘──DataMoverNaMe( ──┼ ┼─ADRDSSU─ ) └ ┘──CONDitionVOLume( ──┴ ┴─LaBeL─ ) ├ ┤─DFDSS─── └ ┘─DSS─────

�─ ──┬ ┬────────────────────── ──┬ ┬────────────────── ──┬ ┬───────────────────── ───────────� │ │┌ ┐─Yes─ │ │┌ ┐─OFF─ │ │┌ ┐─Yes─

└ ┘──COPYVolid( ──┴ ┴─No── ) └ ┘──DEBUG( ──┴ ┴─ON── ) └ ┘──RELOCate( ──┴ ┴─No── )

�─ ──┬ ┬──────────────────── ──┬ ┬─────────────────────────────── ──┬ ┬────────────────── ───� │ │┌ ┐─No── │ │┌ ┐─No── │ │┌ ┐─OFF─

└ ┘──REPLace( ──┴ ┴─Yes─ ) └ ┘──TOLerateENQFailure( ──┴ ┴─Yes─ ) └ ┘──TRACE( ──┴ ┴─ON── )

�──)─────────────────────────────────────────────────────────────────────────────────��

ParametersThe parameters of the SNAP VOLUME subcommand follow in alphabetical order.

CONDITIONVOLUME (ALL | LABEL)Conditional. If you use this parameter, you must also use the COPYVOLID parameter.

Specifies, when using the COPYVOLID(N) parameter during a SNAP VOLUME operation,whether the entire target volume is to be conditioned or only its label. Conditioning onlythe label allows the target volume to remain online while the VTOC and VVDS retain theidentity of the source volume.

If the COPYVOLID parameter is not used, or if COPYVOLID(Y) is used, this parameter isignored.

Note: If PPRC Remote SnapShot is requested, this parameter is ignored.

Abbreviation: CONDVOL

Values: ALL specifies that COPYVOLID(N) is to function normally. See“COPYVOLID (YES | NO)” (below) for details.

LaBeL specifies that the target volume label will be updated with thetarget volser. The target UCB will also be updated with the target volser.The VVDS, VTOC, and VTOC index will be the same as the originalsource volume. The target volume will remain ONLINE.

Default value: ALL

Example: CONDVOL(LBL)


SNAP VOLUME

COPYVOLID (YES | NO)Optional

Specifies whether, during a SNAP VOLUME operation, SnapShot is to retain the source ortarget volume identity.

Note: If PPRC Remote SnapShot is requested, COPYVOLID(NO) results in an errormessage.

Abbreviation: COPYV

Values: Yes specifies that the volser of the source volume is to be retained in thesnap and the target volume is to be made unavailable to the host (that is,SnapShot issues an OS/390 VARY OFFLINE command against the targetvolume).

Note: If a SNAP VOLUME with COPYVOLID(Y) takes place in a JES3environment, the target volume must be manually varied offline to JES3after the SNAP VOLUME completes.

NO specifies that the original volser of the target volume is to be retainedand the target volume is to be made available to the host (that is,SnapShot issues a VARY ONLINE command against the target volume).

Default value: YES

Example: COPYV(Y)

Note: When you specify COPYV(N), the following additional changes are made aftersuccessful completion of the SNAP VOLUME subcommand:

1. If a VTOC index and VVDS are present and active on the target volume, SnapShotupdates any records for the VTOC index and VVDS files to reflect the new names ofthese files. VTOC index names have the form 'SYS1.VTOCIX.volser' and VVDSnames have the form 'SYS1.VVDS.Vvolser'. The volser portion of these names isthe same as the volser of the target volume.

If the volser begins with a numeric character, the default name for the VTOC index is'SYS1.VTOCIX.Vnnnnn', where nnnnn is the last five characters of the volser of thetarget volume.

2. SnapShot updates the VTOC records for the VTOC index and VVDS, if present, toreflect the new names for these files, with the same naming conventions as for theVTOC index updates.

DATAMOVERNAME (NONE | ADRDSSU | DFDSS | DSS)Optional

This parameter specifies a data mover to physically copy the volume (using the DFSMSdssutility with all the defaults) when SnapShot cannot snap the volume.

SnapShot requires a data mover when the source and target volumes do not reside in thesame SVA subsystem and partition.

The DFSMSdss utility control statement for a volume is:

COPY FULL ALLDATA(�) ALLEXCP COPYVOLID CANCELERROR PURGE OPTIMIZE(4)

SnapShot dynamically invokes the data mover and supplies the appropriate commands toaccomplish the copy operation. A message notifies you that a data mover is beinginvoked. If SnapShot is unable to access the data mover, the copy operation terminates.


SNAP VOLUME

If you do not specify the DATAMOVERNAME parameter and the target is not located in thesame subsystem and partition as the source, the SnapShot operation terminates. If youspecify this parameter but SnapShot can be used, SnapShot ignores the data mover request.

Notes:

1. The time required to copy numerous tracks using a data mover can besignificant because the data mover program takes considerably longer than asnap.

2. If PPRC Remote SnapShot is requested, only DATAMOVERNAME(NONE) isvalid. Other parameter options result in an error message.

Abbreviation: DMNM

Values: NONE specifies that a data mover is not to be used.

ADRDSSU, DFDSS, or DSS specifies the name of the data mover to beused (all refer to the DFSMSdss utility program).

Default value: NONE

Example: DMNM(ADRDSSU)


This parameter enables or disables the logging of diagnostic messages. Use it only at therequest of your service representative.

Abbreviation: DEBUG

Values: ON enables diagnostic messages to be generated.

OFF disables diagnostic messages from being generated.

Default value: OFF

Example: DEBUG(ON)

Note: The information resulting from specifying DEBUG(ON) may be of use only to yourservice representative.

INDDNAME (ddname)Conditional. You must specify either this parameter or the SOURCE parameter.

This parameter specifies a preallocated volume to be snapped. You can use this parameterindependently of the OUTDDNAME parameter.

Abbreviation: INDD

Values: ddname identifies the DD name that refers to the device to be snapped.You should select a ddname that resolves to a device. DD nameconcatenation is not supported.


Example: INDD(DVCDDIN)


SNAP VOLUME

Notes:

1. If you use this parameter, the TOLERATEENQFAILURE parameter is ignored forthe source volume.

2. You cannot snap a volume onto itself. Therefore, the INDDNAME or SOURCEparameter cannot specify the same volume or unit as the OUTDDNAME orTARGET parameters.

OFFLINE (Yes | No)Optional

This parameter specifies whether a snap operation is allowed if a volume is offline. Ifspecified, this parameter must be used along with the UNIT parameter.

If you specify YES with this parameter, the volume is not REQUIRED to be offline; that is,the snap operation will not fail if the volume happens to be online. However, a path to theunit must be online.

If the target volume is offline, COPYVOLID(YES) and REPLACE(YES) must also beused; these parameters confirm that the contents of the target volume can be overlaid.

Abbreviation: OFF

Values: YES specifies that, if the associated unit is offline, the snap operation cancontinue.

NO specifies that the associated unit must be online for the snap tocontine.

Default value: NO

Security: You must have SAF READ or equivalent authorization for the sourcevolume.

You must have SAF UPDATE or equivalent authorization for the targetvolume.

Example: OFF(Y)

Note: PAV Alias devices can not be used as the target of a volume snap.

OUTDDNAME (ddname)Conditional. You must specify either this parameter or the TARGET parameter.

This parameter specifies a preallocated target volume. You can use this parameterindependently of the INDDNAME parameter.

When the source and target volumes do not reside on the same SVA subsystem andpartition, you can specify a valid data mover to complete the copy.

Abbreviation: OUTDD

Values: ddname identifies the DD name that refers to the target volume. Youshould select a ddname that resolves to a device and you must alsospecify REPLACE(Y) if the volume has user data on it. DD nameconcatenation is not supported.


Example: OUTDD(DVCDDOUT)


SNAP VOLUME

Notes:

1. If you use this parameter, the TOLERATEENQFAILURE parameter is ignored forthe target volume.


RELOCATE (Yes | No)Optional.

This parameter specifies whether the count fields are to relocated to real cylinder 0 of thevolume.

Abbreviation: RELOC

Values: YES specifies that, on the target volume, the SVA is to create count fieldsthat match the real cylinder location. Yes is valid when the target deviceis defined to begin on real cylinder 0 (such as an OS/390-formattedvolume).

NO specifies that the SVA is to use the source volume's count fields forthe target's count fields (such as a VM CP-formatted volume).

Default value: YES

Example: RELOC(N)

REMOTEFUNCTIONALDEVICEID(fdid)Conditional.

This parameter requests a PPRC Remote SnapShot and identifies the target functionaldevice ID on the remote SVA subsystem. It is used in conjunction with SERIALNUMBERand precludes specifying either VOLUME or UNIT parameters.

Abbreviation: RFDID

Values: fdid specifies a target functional device identifier on the remote SVAsubsystem. fdid requirements:

� offline to all hosts, i.e., no path groups established

� device type must match the PPRC secondary device

� must be write-enabled (CKD R/W) and CKD enabled

� cannot be a PAV Alias device

� cannot be a PPRC bridge volume, secondary device, or primarydevice

Lists, ranges, and wildcards are not allowed.


Example: RFDID(3FE)


SNAP VOLUME

REPLACE (Yes | No)Optional

This parameter specifies whether the snap operation is to overwrite data on an existingtarget volume.

If the target volume contains user data and you do not specify YES for this parameter, thesnap operation terminates. A volume with no user data is defined as one with only aVTOC, a VTOC index, and a VVDS.

If you specify YES for this parameter and the target volume is not empty, old data on thatvolume is overwritten. Catalog entries for any data sets existing on the target volume maybecome invalid.

Note: If PPRC Remote SnapShot is requested, REPLACE(YES) is required andREPLACE(NO) results in an error message.

Abbreviation: REPL

Values: YES specifies that an existing target volume with user data is to beoverwritten.

NO specifies that an existing target volume with user data is not to beoverwritten.

Default value: NO

Example: REPL(Y)

Notes:

1. User data is any data other than the volume label, VTOC, VTOC index, andVVDS. An empty device is one that does not contain any other format-1 DSCBs.

2. Using REPLACE(Y) speeds up the snap operation by not querying the VTOC foruser data set names.

SERIALNUMBER(fraserno)Conditional.

This parameter requests a PPRC Remote SnapShot and identifies the frame serial numberof the remote SVA subsystem. It is used in conjunction withREMOTEFUNCTIONALDEVICEID and precludes specifying either VOLUME or UNITparameters.

Abbreviation: SN

Values: fraserno specifies the frame serial number of the remote SVAsubsystem. This is the same value that is used in establishing the PPRCpair between the primary and secondary devices.



Example: SN(��7�25)


SNAP VOLUME

SOURCE (VOLUME(volser) | UNIT(device))Conditional. You must specify either this parameter or the INDDNAME parameter.

This parameter defines the source volume to be snapped. You can specify either theVOLUME parameter or the UNIT parameter—not both.

Abbreviation: SOU

Values: See the UNIT and VOLUME parameters.


Notes:


2. In no case can PAV Alias devices be used as the source of a volume snap.

TARGET (VOLUME(volser) | UNIT(device)REMOTEFUNCTIONALDEVICEID(fdid) SERIALNUMBER(fraserno))

Conditional. You must specify either this parameter or the OUTDDNAME parameter.

This parameter defines the volume onto which the selected source volume is to be snapped.You can specify the VOLUME parameter, or the UNIT parameter. or the PPRC RemoteSnapShot parameters REMOTEFUNCTIONALDEVICEID and SERIALNUMBER.

Abbreviation: TRG

Values: See the UNIT, VOLUME , REMOTEFUNCTIONALDEVICEID, andSERIALNUMBER parameters.


Notes:


2. In no case can PAV Alias devices be used as the target of a volume snap.

3. If PPRC Remote SnapShot is requested, bothREMOTEFUNCTIONALDEVICEID and SERIALNUMBER parameters must bespecified.

TOLERATEENQFAILURE (YES | NO)Optional

This parameter enables you to snap a volume when exclusive serialization control cannotbe obtained. However, SnapShot cannot allocate a target volume that is already held asOLD. Integrity of the volume cannot be assured. You must use this parameter to snap avolume that is unavailable at the requested serialization level.

This parameter also is used for snapping a volume that must remain allocated during thesnap operation. An example is a volume in use by a Data Base Management System(DBMS).

Abbreviation: TOLENQF


SNAP VOLUME

Values: YES enables the snapping of a volume that is unavailable at the exclusiveserialization level.

NO specifies that the volume is not to be snapped if it is unavailable atthe requested serialization level.

Default value: NO

Example: TOLENQF(Y)

Notes:

1. Refer to the SVA SnapShot for OS/390 Installation, Customization, andMaintenance guide for a description of serialization control requests.

2. This parameter is ignored for source volumes specified with the INDDNAMEparameter and target volumes specified with the OUTDDNAME parameter.


This parameter specifies whether GTF TYPE=USR trace records are to be generated by thesubcommand. GTF records can be used to facilitate troubleshooting of SNAP VOLUMEsubcommand processing.

For the TRACE parameter to be effective, you must start an active trace with GTFTYPE=USR before executing the SNAP VOLUME subcommand.

Note: You should use this parameter only at the request of your service representative.

Abbreviation: TRACE



Default value: OFF

Example: TRACE(ON)

UNIT (device)Conditional. You cannot use both the UNIT parameter and the VOLUME parameter witheither the SOURCE or TARGET parameter. The TARGET parameter also precludesspecifying the PPRC Remote SnapShot parameters.

This parameter identifies the source or target volume by unit address, as known to the hostoperating system. You can specify only one of the UNIT or VOLUME parameters witheach of the SOURCE and TARGET parameters. However, you can use this parameter evenif you have specified VOLUME in the corresponding SOURCE or TARGET parameter.

Abbreviation: UNIT

Values: device specifies the unit address of the source or target volume of thesnap. The volume must be online to the host attempting the snapoperation unless the OFFLINE parameter has been specified.

You can specify hexadecimal digits. Decimal representation, lists,ranges, and wildcards are not accepted.


Examples: UNIT(14BE)UNIT(X'2�F')


SNAP VOLUME

VOLUME (volser)Conditional. You cannot use both the UNIT parameter and the VOLUME parameter witheither the SOURCE or TARGET parameter. The TARGET parameter also precludesspecifying the PPRC Remote SnapShot parameters.

This parameter identifies the source or target volume by volume serial number. You canspecify only one of the VOLUME or UNIT parameters with each of the SOURCE andTARGET parameters. However, you can use this parameter even if you have specifiedUNIT in the corresponding SOURCE or TARGET parameter.

When a device contains multivolume data sets, you must snap each volume individually(note that serialization is not maintained across volumes).

Abbreviation: VOL

Values: volser specifies the volume serial number of the source or targetvolume for the snap. The volume must be online to the host attemptingthe snap operation.



Examples: VOL(BKUP44)VOL(TEST�1)

Examples of SNAP VOLUME Example 1.

SNAP VOLUME ( -SOURCE (VOL (PROD��) ) -TARGET (UNIT (X'�FDC') ) )

This subcommand snaps a volume without using JCL DD statements.

Example 2.

SNAP VOLUME ( -SOURCE (VOL (TESTXX) ) -

OUTDD(ICETARG))

This subcommand snaps a volume using a JCL DD statement for the target device

Example 3.

SNAP VOLUME ( -SOURCE (VOL (SRC��1) ) -TARGET(RFDID(7DF) SN(��7�25) ) -

REPLACE(YES))

This subcommand performs a PPRC Remote SnapShot. The Source volume (SRC001) is aPPRC Primary volume in a PPRC pair. The associated PPRC Secondary volume is notexplicitly referred to in the subcommand, but the Secondary volume is implied to bedefined on the SVA subsystem with serial number 7025. Functional device 7DF also existson SVA subsystem #7025. As the result of the PPRC Remote SnapShot, the Secondaryvolume will be snapped to functional device 7DF.

The REPLACE(YES) parameter is required for all PPRC Remote SnapShots and must beexplicitly specified since the default is NO.


SNAP VOLUME

The COPYVOLID(YES) and DATAMOVER(NONE) parameters are defaults and must bedefaulted to or explicitly specified for all PPRC Remote SnapShots, otherwise the PPRCRemote SnapShot is not performed.


START

START Commands

The START commands are issued only from an OS/390 system console. They enable youto start tasks in the SVAA address space.

START DSR* System Operator command

The START DSR command initializes the DDSR Main Task, which in turn initializes DDSRInterval tasks or the Dynamic DDSR intercept. If the DDSR Main Task is already running,use the START RELEASE subcommand to start DDSR Interval tasks.

START DSR

��─ ──START DSR( ──┬ ┬──MEMBER(suffix) ) ─────────────────────────────────────────────────�� └ ┘─NOMEMBER───────

Note: The following parameter description applies to all four START commands.

MEMBER (suffix) | NOMEMBEROptional

This parameter specifies the suffix of the parmlib member to be used when initializing thespecified task—or that the task is to be initialized with no parmlib member.

Abbreviation: MEM or NOMEM

Values: suffix consists of 1 to 2 alphanumeric characters in the set: A to Z, 0to 9, $, #, @

Default value: If you specify neither MEM nor NOMEM, the parmlib member suffixdefaults to ��.

START SFC* System Operator command

The START SFC command initializes the Server Framework Component (SFC) task, whichin turn initializes the SVAA Server address space.

START SFC

��─ ──START SFC( ──┬ ┬──MEMBER(suffix) ) ─────────────────────────────────────────────────�� └ ┘─NOMEMBER───────

See “START DSR” for a description of the MEMBER and NOMEMBER parameters.

START SIM* System Operator command

The START SIM command initializes the Service Information Message (SIM) task.

START SIM

��─ ──START SIM( ──┬ ┬──MEMBER(suffix) ) ─────────────────────────────────────────────────�� └ ┘─NOMEMBER───────

See “START DSR” for a description of the MEMBER and NOMEMBER parameters.


START

START SRP* System Operator command

The START SRP command initializes the Reporter Data Collection task.

START SRP

��─ ──START SRP( ──┬ ┬──MEMBER(suffix) ) ─────────────────────────────────────────────────�� └ ┘─NOMEMBER───────

See “START DSR” on page 8-196 for a description of the MEMBER and NOMEMBERparameters.

START VOP* System Operator command

The START VOP command initializes the console operator interface (virtual operator panel)task.

START VOP

��─ ──START VOP( ──┬ ┬──MEMBER(suffix) ) ─────────────────────────────────────────────────�� └ ┘─NOMEMBER───────

See “START DSR” on page 8-196 for a description of the MEMBER and NOMEMBERparameters.


START DRAIN

START DRAIN Subcommand


The START DRAIN subcommand initiates a drain of one or more drive modules. You canspecify the drive modules individually, by array, by tray, or by DAU. When the designateddevices have been successfully drained (that is, all data has been moved), they are placedin the MAT partition for removal or reallocation as spares.

Note: You cannot drain the last drive module, last array, last tray, or last DAU.

START DRAIN

��──START DRAIN──(─ ──SUBSYStem(subsys) ──┬ ┬──ARraYID(arrayid) ──────── ──────────────────�├ ┤──DiskArrayUnit(dau) ──────

│ │┌ ┐─ ─────├ ┤──DriveMODule( ───� ┴─u.t.s─ )└ ┘──TRAY(u.t) ───────────────

�─ ──┬ ┬──────────────────────────────── ─)─────────────────────────────────────────────�� │ │┌ ┐─ ────────────────

└ ┘──NOTIFY( ───� ┴┬ ┬──NODEid(nodeid) )└ ┘──USERid(userid)

Parameters


This parameter specifies the name of the SVA subsystem that is to perform the drain.



Note: If the subsystem name contains lowercase characters and SETCASE(UPPER) is in effect, you must enclose the name in matchingquotes.

Default value: None

Examples: SUBSYSTEM(SUB1)SUBSYS(1SUBSYS)

ARRAYID (arrayid)Conditional (This is one of a group of four parameters of which you must enter one andonly one: ARYID, DAU, DMOD, or TRAY.)

This parameter specifies the array to be drained.

Abbreviation: ARYID

Values: arrayid (an integer from 0 to 7) is the array ID.

Default value: None

Example: ARYID(�)


START DRAIN

DISKARRAYUNIT (dau)Conditional (This is one of a group of four parameters of which you must enter one andonly one: ARYID, DAU, DMOD, or TRAY.)

This parameter specifies the disk array unit (DAU) to be drained.

Note: If a Test partition has been defined, you cannot initiate a drain of a DAU; that is,you cannot use this parameter. (All drive modules to be drained must be in the samepartition.)

Abbreviation: DAU

Values: dau is the disk array unit (a single digit from 0 to 3).

Default value: None

Example: DAU(�)

DRIVEMODULE (u.t.s)Conditional (This is one of a group of four parameters of which you must enter one andonly one: ARYID, DAU, DMOD, or TRAY.)

This parameter designates one or more individual drive modules to be drained.

When you specify a drain of individual drive modules, at least as many spares must beavailable as there are drives to be drained. If too few spares are available, thesubcommand is rejected.

Abbreviation: DMOD

Values: u.t.s (3 digits separated by periods) identifies a specific drive module,where:


You can specify lists but not ranges.

You cannot use wildcard characters.

Default value: None

Examples: DMOD(1.3.2)DMOD(�.�.1 �.�.5)

TRAY (u.t)Conditional (This is one of a group of four parameters of which you must enter one andonly one: ARYID, DAU, DMOD, or TRAY.)

This parameter specifies the tray to be drained.

Note: If a Test partition has been defined, you cannot initiate a drain of a tray; that is,you cannot use this parameter. (All drive modules to be drained must be in the samepartition.)

Values: u.t (2 digits separated by a period) identifies the tray, where:

u identifies the disk array unit (0 to 3)t identifies the tray (0 to 3)

Default value: None

Example: TRAY(1.�)


START DRAIN

NOTIFY ( {NODEID (nodeid) USERID (userid)} )Optional

This parameter's subparameters identify the node and/or the user to be notified when thedrain is completed.

NODEID (nodeid)

Abbreviation: NODE

Values: nodeid is 1 to 8 alphanumeric characters.

Default value: Node ID from which drain is initiated

Example: NODE(REMOTE1)

USERID (userid)

Abbreviation: USER

Values: userid is 1 to 8 alphanumeric characters.

Default value: User ID of user who initiates drain

Example: USER(JOHN)

Examples of START DRAIN Example 1.

START DRAIN (- SUBSYSTEM(SUBSYSA)-

DMOD(�.1.� �.1.3 �.1.4)- NOTIFY(USERID(JUDY)) )

This subcommand starts a drain of drive modules �.1.�, �.1.3, and �.1.4 (unit �, tray 1,slots �, 3, and 4) in SVA subsystem SUBSYSA. User ID JUDY will be notified when thedrain is complete. At least 3 spare drives must be available (1 per drive to be drained) forthe drain to begin.

Example 2.

START DRAIN (- SUBSYSTEM(ICESUB1)- ARYID(3)-

NOTIFY(NODEID(FOX) USERID(JOE)) )

This subcommand starts a drain of array 3 in SVA subsystem ICESUB1. Node ID FOX anduser ID JOE will be notified when the drain is complete. All data in array 3 will be movedto other arrays in the same partition.


START RELEASE

START RELEASE Subcommand


The START RELEASE subcommand starts DDSR interval tasks—provided the DDSR MainTask is already running.

START RELEASE

��──START RELease─ ──┬ ┬────────────────── ─────────────────────────────────────────────��└ ┘──(MEMber(suffix))

Parameter

MEMBER (suffix)Optional

This parameter defines the suffix of the member in the control file containing the spacerelease parameters. The suffix is appended to the string SIBDSR to produce the name ofthe member to be accessed in the library specified by the STKPARMS DD statement.

Abbreviation: MEM

Values: suffix consists of 1 to 2 alphanumeric characters in the set: A to Z, 0to 9, $, #, @

Default value: ��

Examples of START RELEASE Example 1.

START RELEASE

This subcommand starts DDSR interval tasks (if the DDSR Main Task is running). Bydefault, the suffix �� is appended to SIBDSR to form the name of the member to beaccessed in the library specified by the STKPARMS DD statement.

Example 2.

START REL (- MEM(A1) )

This subcommand starts DDSR interval tasks (if the DDSR Main Task is running). Thesuffix A1 is appended to SIBDSR.


STOP

STOP Commands

The STOP commands are issued only from an OS/390 system console. They enable you toterminate tasks that are running in the SVAA address space.

STOP DSR* System Operator command

The STOP DSR command stops all DDSR Interval tasks and the Dynamic DDSR intercept,and then terminates the DDSR Main Task.

STOP DSR

��──STOP DSR──(─ ──RELeaseIDentifier(relid) ─)─────────────────────────────────────────��

Values: relid is the release task identifier for this DDSR task. You can usewidcard characters but not ranges or lists.

Note: If SET CASE(UPPER) is in effect, and you use lowercasecharacters in the release task identifier and don't want them converted touppercase, you must enclose the identifier in matching quotes.

Default value: None

Example: RELID('task�11')

STOP SFC* System Operator command

The STOP SFC command stops the Server Framework Component (SFC) task.

STOP SFC

��──STOP SFC─────────────────────────────────────────────────────────────────────────��

STOP SIM* System Operator command

The STOP SIM command stops the Service Information Message (SIM) task.

STOP SIM

��──STOP SIM─────────────────────────────────────────────────────────────────────────��

STOP SRP* System Operator command

The STOP SRP command stops the Reporter Data Collection task. Reporter collects a finalset of statistics for each outstanding collection run, unless you specify the IMMEDparameter.

STOP SRP

��─ ──STOP SRP ──┬ ┬───────────── ───────────────────────────────────────────────────────�� └ ┘──(IMMEDiate)


STOP RELEASE

STOP VOP* System Operator command

The STOP VOP command stops the console operator interface (virtual operator panel) task.

STOP VOP

��──STOP VOP─────────────────────────────────────────────────────────────────────────��

STOP RELEASE Subcommand


The STOP RELEASE subcommand terminates an active DDSR interval task and/or theDynamic DDSR intercept, but does not stop the active DDSR Main Task.

STOP RELEASE

┌ ┐─ ──────────────────────────��──STOP RELease──(─ ───� ┴┬ ┬──RELeaseIDentifier(relid) ─)───────────────────────────────�� └ ┘ ─DYNamic──────────────────

Parameters


This parameter specifies the DDSR interval task that is to be terminated.

Abbreviation: RELID

Values: relid is a release task identifier defined by the RELEASEINTERVALDATA subcommand



Default value: None


This parameter terminates the Dynamic DDSR intercept.

Abbreviation: DYN

Default value: None

Examples of STOP RELEASE Example 1.

STOP RELEASE (- RELID('task123') )

This subcommand terminates DDSR interval task task123.


SUSPEND RELEASE

Example 2.

STOP REL (- DYNAMIC )

This subcommand terminates the Dynamic DDSR intercept.

Example 3.

STOP REL (- RELID(TASK3�)- DYN )

This subcommand terminates all DDSR interval tasks with identifiers beginning with thecharacters TASK3 and also terminates the Dynamic DDSR intercept.

SUSPEND RELEASE Subcommand


The SUSPEND RELEASE subcommand suspends an active DDSR interval task and/or theDynamic DDSR intercept. This enables you to halt DDSR temporarily without terminatingDDSR processing.

You can reactivate processing later with the RESUME RELEASE subcommand withoutre-entering control settings. Note that, when the task resumes, it starts processing “at thebeginning” (at the first device in a normal pass)—not at the device it was processing whensuspended.

SUSPEND RELEASE

┌ ┐─ ──────────────────────────��──SUSPend RELease──(─ ───� ┴┬ ┬──RELeaseIDentifier(relid) ─)────────────────────────────�� └ ┘─DYNamic──────────────────

Parameters


This parameter specifies the DDSR interval task that is to be suspended.

Abbreviation: RELID

Values: relid is a release task identifier defined by the RELEASEINTERVALDATA subcommand



Default value: None

Example: RELID(1�S)



VARY CHANNEL

This parameter specifies that the Dynamic DDSR intercept is to suspend processing.

Abbreviation: DYN

Default value: None

Examples of SUSPEND RELEASE Example 1.

SUSPEND RELEASE (- RELID(1234) )

This subcommand suspends processing by DDSR interval task 1234.

Example 2.

SUSP REL (- DYNAMIC )

This subcommand suspends processing by the Dynamic DDSR intercept.

Example 3.

SUSP REL (- RELID(TASK3�)- DYN )

This subcommand suspends processing by all DDSR interval tasks with identifiersbeginning with the characters TASK3 and also by the Dynamic DDSR intercept.

VARY CHANNEL Subcommand


The VARY CHANNEL subcommand enables or disables a parallel channel interface.

VARY CHANNEL

┌ ┐─ ───��──Vary CHANnel──(─ ──SUBSYStem(subsys) ──InterFaceID( ───� ┴─c.i─ ) ──┬ ┬─ENAble── ─)───────�� └ ┘─DISable─

Parameters


This parameter specifies the name of the SVA subsystem to which the channel interface isattached.




Default value: None


VARY CHANNEL



This parameter specifies one or more (up to 32) parallel channel interfaces of the SVAsubsystem.

Abbreviation: IFID


c identifies one of the two clusters (0 or 1) in the subsystemi is the interface ID (A through P) associated with a specific cluster


Default value: None

Examples: INTERFACEID(�.A) (channel A on cluster 0)IFID(�.A:�.J) (channels A to J on cluster 0)IFID(�.A �.C) (channels A and C on cluster 0)

ENABLE | DISABLERequired

This parameter specifies that the channel interface is to be either enabled or disabledimmediately.

Abbreviation: ENA or DIS

Default value: None

Examples of VARY CHANNEL Example 1.

VARY CHANNEL (- SUBSYSTEM(SUB1)- INTERFACEID(�.P)- ENABLE )

On SVA subsystem SUB1, this subcommand immediately enables channel interface �.P.

Example 2.

V CHAN (- SUBSYS('icesubA')- IFID(�.A 1.A)- DISABLE )

On SVA subsystem icesubA, this subcommand immediately disables channel interfaces�.A and 1.A.


VARY DEVICE

Example 3.

V CHAN (- SUBSYS(ICE1)- IFID(�.A:�.P)- ENA )

On SVA subsystem ICE1, this subcommand immediately enables channel interfaces �.Athrough �.P.

Example 4.

V CHAN (- SUBSYS(S1)- IFID(�.A:�.P 1.A:1.F)- DIS )

On SVA subsystem S1, this subcommand immediately disables channel interfaces �.Athrough �.P and 1.A through 1.F.

VARY DEVICE Subcommand


The VARY DEVICE subcommand enables or disables a functional device and/or enables ordisables write protection for the device.

Notes:

1. You cannot change the SCSIENABLE or SCSIREADWRITE values for PowerPPRC Bridge devices.

2. You cannot change any values for PAV Alias devices.

VARY DEVICE

┌ ┐─ ────��──Vary DEVice──(─ ──SUBSYStem(subsys) ──┬ ┬──FunctionalDeviceID( ───� ┴─fdid─ ) ────────────� │ │┌ ┐─ ──────

└ ┘──UNIT( ───� ┴─device─ ) ────────────

┌ ┐─ ──────────────────────────�─ ───� ┴┬ ┬──CKDENAble( ──┬ ┬─YES─ ) ──── ─)─────────────────────────────────────────────────�� │ │└ ┘─NO──

├ ┤──CKDReadWrite( ──┬ ┬─YES─ ) ─ │ │└ ┘─NO──

├ ┤──SCSIENAble( ──┬ ┬─YES─ ) ─── │ │└ ┘─NO──

└ ┘──SCSIReadWrite( ──┬ ┬─YES─ ) └ ┘─NO──

Parameters


This parameter specifies the name of the SVA subsystem with which the functional deviceis associated.



VARY DEVICE



Default value: None


FUNCTIONALDEVICEID (fdid)Conditional (To identify the device, you must enter either this parameter or the UNITparameter—not both.)

This parameter specifies the devices their SVA functional device identifiers (FDIDs).

Abbreviation: FDID

Values: fdid is a functional device identifier: 1 to 3 hexadecimal digits or 1 to4 decimal digits. See the table on page 1-2 for ranges of FDID values bysubsystem type.



Examples: FDID(2�) (decimal 32)FDID(D'32') (decimal 32)FDID(21 22 2D) (decimal 33, 34, and 45)FDID(2�:2E) (decimal 32 through 46)

UNIT (device)Conditional (To identify the device, you must enter either this parameter or the FDIDparameter—not both. However, if the device is not defined to the host operating system inwhich SVAA is running, you must use FDID.)

This parameter specifies the devices as they are defined to the host in which SVAA isrunning.





Examples: UNIT(�234)UNIT(234)UNIT(X'�234')UNIT(222:233)UNIT(2�� 3��)

CKDENABLE (YES | NO)Conditional (This is one of a group of four parameters of which you must enter at leastone: CKDENA, CKDRW, SCSIEN, and SCSIRW.)

This parameter enables or disables host access to the CKD functional device immediately.


VARY DEVICE

Notes:

1. You must vary the device offline to all hosts before you disable the device(CKDENA(NO)).

2. You cannot alter this value for PAV Alias devices.


Values: YES or NO

Default value: None

Example: CKDENA(YES)

CKDREADWRITE (YES | NO)Conditional (This is one of a group of four parameters of which you must enter at leastone: CKDENA, CKDRW, SCSIENA, and SCSIRW.)

Note: You cannot alter this value for PAV Alias devices.

This parameter specifies whether to allow write access to the CKD functional device. YESallows writes; NO allows no writes.

Abbreviation: CKDRW

Values: YES or NO

Default value: None

Example: CKDRW(NO)

SCSIENABLE (YES | NO)Conditional (This is one of a group of four parameters of which you must enter at leastone: CKDENA, CKDRW, SCSIEN, and SCSIRW.)

This parameter enables or disables host access to the SCSI functional device immediately.

Note: You cannot change the SCSIENABLE value for Power PPRC Bridge devices.


Values: YES or NO

Default value: None

Example: SCSIENA(NO)

SCSIREADWRITE (YES | NO)Conditional (This is one of a group of four parameters of which you must enter at leastone: CKDENA, CKDRW, SCSIEN, and SCSIRW.)

This parameter specifies whether to allow write access to the SCSI functional device. YESallows writes; NO allows no writes.

Note: You cannot change the SCSIREADWRITE value for Power PPRC Bridge devices.


Values: YES or NO

Default value: None



VARY DEVICE

Examples of VARY DEVICE Example 1.

VARY DEVICE (- SUBSYSTEM(SUB1)- UNIT(�234)- SCSIENA )

On SVA subsystem SUB1, this subcommand immediately enables the SCSI device defined tothe host operating system as �234.

Example 2.

VARY DEVICE (- SUBSYS('icesubA')- FDID(22)- CKDRW(NO) )

On SVA subsystem icesubA, this subcommand immediately disables write access to theCKD functional device 22.

Example 3.

V DEV (- SUBSYS(ICE1)-

UNIT(234 345 456)- SCSIENA- SCSIRW(YES) )

On SVA subsystem ICE1, this subcommand immediately enables the SCSI devices definedto the host operating system as 234, 345, and 456 and enables write access to thosedevices.

Example 4.

V DEV (- SUBSYS(S2)-

FDID(X'5�' D'2�' 25:28 2C)- CKDRW(NO) )

On SVA subsystem S2, this subcommand disables write access to the CKD functionaldevices 5�, 2� (decimal), 25 through 28, and 2C.


Drive Module Status

Appendix A. Drive Module Status

Table A-1 lists and describes the statuses that a drive module can acquire. Statusis indicated by a two-character code: the first character identifies the partition withwhich the drive is associated; the second character shows the current state of thedrive. Status codes are displayed either as two characters or as two charactersseparated by a period. For example, the status of a drive module associated withthe Production partition in the active state is “PA” or “P.A” .

Table A-1 (Page 1 of 2). Drive module status descriptions

Drive Module Status Status Code Description

MAT partition

MAT: Active M.A (MA) Drive module is active and available for allocation as aspare.

MAT: Fenced M.F (MF) Drive module is fenced for diagnostics for one of thefollowing reasons:

� New drive module pre-acceptance test (capacityupgrade)

� Guided FRU replacement (drive module removal)

Production partition

Production: Active P.A (PA) Drive module is a member of an array that is associated withthe Production partition.

Production: Copy (receivingdrain data)

P.C (PC) Drive module is receiving data from the drain of a singledrive module in the Production partition.

Production: Draining P.D (PD) Drive module is being drained.

Production: Initialize array P.I (PI) Drive module is part of an array initialization process.

Production: Pending drain P.P (PP) Drive module is waiting to be drained. The drain cannotbegin for one of the following reasons:

� A drive module reconstruction is in progress� Another drive in the array is being drained� The number of available spares is inadequate (this can

occur if the number of spares was reduced after thedrain request was accepted)

Production: Reconstruction P.R (PR) Drive module is being used to reconstruct data for aProduction partition drive module that failed.

Spares partition

Spare: Active S.A (SA) Drive module is available for forming arrays, for datareconstruction, or for receiving data from a drain of a singledrive module.

Spare: Fenced S.F (SF) Drive module is fenced for a periodic drive test.

Spare: Pending drain S.P (SP) Drive module is waiting to be drained pending completion ofa periodic drive test.

November, 2006 — PN 311290512, Rev. N Drive Module Status A-1

Drive Module Status

Table A-1 (Page 2 of 2). Drive module status descriptions

Drive Module Status Status Code Description

Test partition

Test: Active T.A (TA) Drive module is a member of an array that is associated withthe Test partition.

Test: Copy (receiving draindata)

T.C (TC) Drive module is receiving data from the drain of a singledrive module in the Test partition.

Test: Draining T.D (TD) Drive module is being drained.

Test: Initialize array T.I (TI) Drive module is part of an array initialization process.

Test: Pending drain T.P (TP) Drive module is waiting to be drained. The drain cannotbegin for one of the following reasons:

� A drive module reconstruction is in progress� Another drive in the array is being drained� The number of available spares is inadequate (this can

occur if the number of spares was reduced after thedrain request was accepted)

Test: Reconstruction T.R (TR) Drive module is being used to reconstruct data for a Testpartition drive module that failed.

Unavailable partition

Unavailable: Broken U.B (UB) Drive module in slot is broken.

Unavailable: No active drivemodule

U.N (UN) No active drive module is sensed in slot or slot has not beeninstalled.

November, 2006 — PN 311290512, Rev. NA-2 SVAA Configuration and Administration

SMF Record Formats

Appendix B. SMF Record Formats

DDSR (when back-end storage is released) and SnapShot (when a snap isexecuted) optionally produce SMF records. This appendix shows the layout of twoSMF record subtypes:

� Subtype 5: DDSR data� Subtype 8: SnapShot event data

Five other SVAA SMF record subtypes, for reporting data collection, are documentedin SVAA for OS/390 Reporting:

� Subtype 1: Subsystem Performance� Subtype 2: Channel Interface Statistics� Subtype 3: Functional Device Performance� Subtype 4: Drive Module Performance

� Subtype 7: Space Utilization

DDSR Record (Subtype 5)

To activate the production of SMF records for DDSR, specify subtype 5 in theSUBPARM parameter of SMFPRMxx. For details, see the step for “Customizing theSMFPRMxx Member” in the SVAA for OS/390 Installation, Customization, andMaintenance manual.

Table B-1 shows the format of the standard SMF record header. Table B-2 showsthe format of record subtype 5.

Table B-1 (Page 1 of 2). SVAA SMF record header format (SIBSMFHD)

Dec Hex Type Length Label Description

0 0 0 SIBSMFHD

0 0 Hexadecimal 2 LEN Record length

2 2 Hexadecimal 2 SEG Segment descriptor

4 4 Hexadecimal 1 SMFFLG Header flag byte

1... .... SMFRRF New SMF record format

.1.. .... SMFSUT Subtype utilized

..1. .... SMFF20 Not used

...1 .... SMFES4 SP4 MVS/SP v4

.... 1... SMFESA SP3 MVS/ESA

.... .1.. SMFVXA SP2 MVS/XA

.... ..1. SMFVS2 SP1 OS/VS2

.... ...1 SMFF01 Not used

5 5 Hexadecimal 1 SMFRTY Record type (SMF record number)

6 6 Hexadecimal 4 SMFTIME Time record written, in hundredths of secondssince midnight

10 A Packed 4 SMFDATE Date record written, in the form 0cyydddF c=0 for 1990 to 1999 c=1 for 2000 to 2099

14 E Character 4 SMFSID System ID

November, 2006 — PN 311290512, Rev. N SMF Record Formats B-1

SMF Record Formats

Table B-1 (Page 2 of 2). SVAA SMF record header format (SIBSMFHD)


18 12 Character 4 SMFSSI Subsystem ID for SMF

22 16 Hexadecimal 2 RECTYPE SMF record subtype

1 SRP Subsystem Performance

2 SRP Channel Interface Statistics

3 SRP Functional Device Performance

4 SRP Drive Module Performance

5 Deleted Data Space Release

6 (reserved)

7 SRP Space Utilization

8 SnapShot

24 18 LENGTH SMF header length

Table B-2 (Page 1 of 2). SVAA DDSR record format (SIBSMF05). This DSECT maps the DDSR SMF record producedby SVAA when back-end storage associated with free space extents is discarded.


DDSR SMF record 5 header

0 0 0 SIBSMF05

0 0 Structure SIBSMFHD SMF record header

DDSR SMF record 5 basic segment

24 18 Hexadecimal 1 REQTYPE Space release request type

1 REQINTVL Interval DDSR request

2 REQDYNAM Dynamic DDSR request

25 19 Hexadecimal 1 VERSION Version of this subtype

1 VRSN1 Version 1

2 VRSN2 Version 2

2 CURVRSN Current version

26 1A Hexadecimal 2 DEVNUM Device address on which space was released

28 1C Character 6 VOLID Volume ID on which space was released

34 22 Hexadecimal 2 FDID SVA functional device ID

36 24 Character 8 SUBSYS SVA subsystem name that owns the device

44 2C Hexadecimal 2 SSID SVA subsystem ID

46 2E Hexadecimal 2 IDID Channel unit address ID

48 30 Character 8 JOBNAME Jobname of the data space release requestor

56 38 Hexadecimal 2 EXTNUM Number of extents released

58 3A Hexadecimal 2 EXTOSET Offset from the start of the basic segment to thefirst extent segment

60 3C Hexadecimal 2 EXTSLEN Length of an extent list segment

62 3E Hexadecimal 1 RECNUM Current record number if SMF event is recordedby two or more records

November, 2006 — PN 311290512, Rev. NB-2 SVAA Configuration and Administration

SMF Record Formats

Table B-2 (Page 2 of 2). SVAA DDSR record format (SIBSMF05). This DSECT maps the DDSR SMF record producedby SVAA when back-end storage associated with free space extents is discarded.


63 3F Hexadecimal 1 RECTOT Total records if SMF event is recorded by two ormore records

64 40 4 *** Reserved

68 44 Hexadecimal 1 DADSMREQ IEXFUNC DADSM request code (DynamicDDSR only)

1 IEXALL Allocate

2 IEXEXT Extend

3 IEXSCR Scratch (*)

4 IEXPR Partial release (*)

5 IEXREN Rename

6 IEXPREL Partrel partial release (*)

7 IEXVEXT VSAM extend without a DEB

(*) indicates request codes processed byDynamic DDSR

69 45 Hexadecimal 1 FLAG1 Flags

1... .... F1SIM Simulated space release

70 46 2 *** Reserved

72 48 Character 44 DSNAME Data set name for which space was released(Dynamic DDSR only)

116 74 Character 16 RELEASID Task ID of the interval subtask that requestedspace release (Interval DDSR only)

132 84 4 *** Reserved

136 88 STRSIZE Length of basic segment

136 88 EXTLIST Start of extent segments

DDSR SMF record 5 extent list segment

0 0 0 SIBSMFEL

0 0 Hexadecimal 4 EXTBOE Beginning of extent address (CCHH)

4 4 Hexadecimal 4 EXTEOE End of extent address (CCHH)

8 8 Hexadecimal 4 IOTIME I/O time for space release (in milliseconds)

12 C EXTSIZE Length of an extent segment


SMF Record Formats

SnapShot Record (Subtype 8)

To activate the production of SMF records for SnapShot, specify subtype 8 in theSUBPARM parameter of SMFPRMxx. For details, see the step for “Customizing theSMFPRMxx Member” in the SVA SnapShot for OS/390 Installation, Customization,and Maintenance manual.

Figure B-1 shows the general format of the SVAA SMF record subtype 8 used forrecording SnapShot events. Table B-3 shows the detailed format of the SMFrecord. Each record consists of the SMF record header and a basic segment withone of the following four segment types attached to it.

1. The cluster definition segment2. The data set name segment (if the command is SNAP DATASET)3. The snapped extents list segment4. The DDSR extents list segment

SMF RecordHeader

SMF RecordHeader

SMF RecordHeader

SMF RecordHeader

BasicSegment

BasicSegment

BasicSegment

BasicSegment

Data SetName

Segment

ClusterDefinitionSegment

SnappedExtents

List Segment

SnappedExtents

List Segment

DDSRExtents

List Segment

DDSRExtents

List Segment

0 0 0 0

24 24 24 24

+0 +0

+0 +0 +0 +0

C46252

Figure B-1. Format of Snap Dataset or Snap Volume SMF Record

Table B-3 (Page 1 of 5). SnapShot record format (Subtype 8)

DecOffset

HexOffset

FieldName

Length Type Description

SMF Record Header

0 00 len 2 Binary Record length. This field and the next make up therecord descriptor word.

2 02 seg 2 Binary Segment descriptor

4 04 smfflg 1 Binary X'80' New SMF record formatX'40' Subtype utilizedX'20' (reserved)X'10' MVS/SP Version 4X'08' MVS/ESAX'04' MVS/XAX'02' OS/VS2X'01' (reserved)

5 05 smfrty 1 Binary SMF record number


SMF Record Formats


DecOffset

HexOffset

FieldName


6 06 smftime 4 Binary Time record written, in hundredths of seconds sincemidnight

10 0A smfdate 4 Packed Date record written, in the form 0cyydddF where: c=0 for 1990 to 1999 c=1 for 2000 to 2099

14 0E smfsid 4 Character System ID

18 12 smfssi 4 Character Subsystem identification for SMF

22 16 rectype 2 Binary SMF record subtype

X'0001' Subsystem PerformanceX'0002' Channel Interface StatisticsX'0003' Functional Device PerformanceX'0004' Drive Module PerformanceX'0005' DDSRX'0006' (reserved)X'0007' Space UtilizationX'0008' SnapShot

Basic Segment

24 18 reqtype 1 Character Type of snap request:1 = Snap Dataset request2 = Snap Volume request

25 19 version 1 Character SVAA version that produced this record

26 1A segtype 2 Character Type of attached segment:1 = Cluster Definition Segment2 = SnapShot Data Set Name Segment3 = SnapShot Extent List Segment4 = DDSR Extent List Segment

28 1C res01 4 Character (Reserved)

32 20 rectoken 8 Double Type 8 record token

40 28 compcode 4 Integer Return code from snap operation

44 2C strtime 4 Binary Time snap started, in hundredths of seconds sincemidnight

48 30 strtdate 4 Packed Date record written, in the form 0cyydddF where: c=0 for 1990 to 1999 c=1 for 2000 to 2099

52 34 snaptime 4 Integer Time to complete the snap in milliseconds (thousands)elapsed


SMF Record Formats


DecOffset

HexOffset

FieldName


56 38 flags 4 Binary Flags

Byte 1: X'80' COPYVOLID(YES) specified X'40' BYPASSACS(YES) specified X'20' CAT(YES) specified X'10' TOLENQ(YES) specified X'08' HCPYMODE(SHR) specified X'04' REPL(YES) specified X'02' DELETE(YES) specified X'01' FORCE(YES) specified

Byte 2: X'80' DEBUG(ON) specified X'40' TRACE(ON) specified X'20' VOLUME specified X'10' ESOTERIC specified X'08' TRUNCATION specified X'04' CONDVOL(LBL) specified X'02' ERRDISP(KEEP) specified X'01' ERRDISP(DELETE) specified

Byte 3: X'80' OFFLINE(YES) specified for source X'40' OFFLINE(YES) specified for target

(Other bytes and bits reserved)

60 3C jobname 8 Character Jobname of SnapShot requestor

68 44 userid 8 Character User ID of SnapShot requestor

76 4C datamovr 8 Character Name of data mover, or blank

84 54 storclas 8 Character Storage class name specified, or blank

92 5C mgmtclas 8 Character Management class name specified, or blank

100 64 dataclas 8 Character Data class name specified, or blank

108 6C esoteric 8 Character OS/390 esoteric name specified, or blank

116 74 volcnt 4 Integer Number of volumes snapped

120 78 res02 100 Character (Reserved)

220 DC segnum 2 Integer Number of segments of this type

222 DE seglen 2 Integer Length of segments of this type

224 E0 segoffst 2 Integer Offset to start of the attached segment from the start ofthe basic segment

226 E2 recnum 1 Integer Current record number if SMF event is recorded by twoor more records

227 E3 rectot 1 Integer Total records if SMF event is recorded by two or morerecords

228 E4 res03 92 Character (Reserved)

Cluster Definition Segment

+0 0 sclstnam 44 Character Name of source cluster

+44 2A sclstid 2 Integer ID number of source cluster

+46 2C res11 2 Integer (Reserved)


SMF Record Formats


DecOffset

HexOffset

FieldName


+48 2E tclstnam 44 Character Name of target cluster

+52 34 tclstid 2 Integer ID number of target cluster

+54 38 res12 2 Integer (Reserved)

+56 3A pathname 44 Character Name of path to cluster

+100 64 clstorg 8 Character VSAM cluster organization

+108 6C res13 204 Character (Reserved)

Data Set Name Segment

+0 0 srcdsn 44 Character Name of source data set (Snap data set only)

+44 2A srcclsid 2 Integer Cluster ID number of the source cluster

+48 2A srcdsnid 2 Integer Data set ID number of the source data set

+50 2C trgdsn 44 Character Name of target data set

+94 5E trgclsid 2 Integer Cluster ID number of the target cluster

+96 60 trgdsnid 2 Integer Data set ID number of the target data set

+98 62 res21 1 character (Reserved)

+91 63 dsntype 1 character Catalog DSNTYPE field

+92 64 res22 198 character (Reserved)

Snapped Extents List Segment

+0 0 1 Integer (Reserved for internal use only)

+1 1 res31 3 Character (Reserved)

+4 4 iosttime 4 Integer Start time of I/O for extent

+8 8 iostdate 4 Character Start date of I/O for extent

+12 C iotime 4 Integer Time to snap this extent in milliseconds

+16 10 snapret 2 Integer Return code from snap operation

+18 12 snapres 2 Integer Reason code from snap operation


+22 16 dmoveret 2 Integer Return code from data mover

+24 18 dmoveres 2 Integer Reason code from data mover

+26 1A 2 Integer (Reserved for internal use only)

+28 1C 4 Integer (Reserved for internal use only)

+32 20 srcfunc 2 Integer Source functional extent number

+34 22 srcsub 8 Character Subsystem name that owns the source extent (blank ifnon-SVA)

+42 2A srcdev 2 Integer Device address of source volume

+44 2C srcvol 6 Character ID number of source volume

+50 32 srcboe 4 Character Beginning of source extent address (cchh)

+54 36 srceoe 4 Character End of source extent address (cchh)

+58 3A trgfunc 2 Integer Functional extent number of target

+60 3C trgsub 8 Character Subsystem name that owns the target extent (blank ifnon-SVA)

+68 44 trgdev 2 Integer Device address of target volume


SMF Record Formats


DecOffset

HexOffset

FieldName


+70 46 trgvol 6 Character ID number of target volume

+76 4C trgboe 4 Character Beginning of target extent address (cchh)

+80 50 trgeoe 4 Character End of target extent address (cchh)

+84 54 sextdsid 2 Integer ID number of the source data set

+86 56 textdsid 2 Integer ID number of the target data set

+88 58 sextclid 2 Integer ID number of the source cluster

+90 5A textclid 2 Integer ID number of the target cluster

+92 5C res32 36 Character (Reserved)

DDSR Extents List Segment

+0 0 ddsrtype 1 Integer Type of DDSR extent segment1 = Source extent segment2 = Target extent segment

+1 1 ddsrtime 4 Integer Start time of I/O for extent

+5 5 ddsrdate 4 Character Start date of I/O for extent


+11 B ddsrfunc 2 Integer Functional extent number

+13 D ddsrsub 8 Character Name of SVA subsystem

+21 15 ddsrdev 2 Integer Device address

+23 17 ddsrvol 6 Character Volume identifier

+29 1D ddsrboe 4 Integer Beginning extent in cchh format

+33 21 ddsreoe 4 Integer Ending extent in cchh format

+37 25 tdsrdsid 2 Integer ID number of target data set

+39 27 tdsrclid 2 Integer ID number of target cluster

+41 29 res41 60 Character (Reserved)


Data Bridge

Glossary

This glossary is included in each book in the SharedVirtual Array Administrator library. All of the terms areassociated with SVAA, but not all are used in thisspecific document.

AAlias. A pseudo-device used by the operating systemto support an additional I/O path to a Base device.Each Alias device supports one additional I/O to aBase. See also: Base and Parallel Access Volume.

array. A group of storage devices that are usedcollectively to achieve data redundancy and/or improvedperformance. In the SVA, an array consists of either 7or 15 drive modules. See also: dual-redundancy array.

array cylinder. The collection of all physical cylindersin a dual-redundancy array that have the same physicalcylinder address (CC). The SVA allocates back-endspace in units of array cylinders. There are two typesof array cylinders: free and allocated.

array device. The disk devices that are logicallygrouped together when a FORM ARRAY command isissued at the local operator panel or from SVAA.

array track. The collection of all physical tracks in adual-redundancy array that have the same physicaltrack address (CC, HH).

Bback-end storage. The data storage portion of astorage subsystem. In the SVA, the disk arrays.

Base. A real device that supports additional I/O pathsto itself in the form of Alias devices. Each Alias devicesupports one additional I/O to a Base. Multiple Aliasdevices can be associated with a single Base. Seealso: Alias and Parallel Access Volume.

base functional device ID (BFDID). The functionaldevice identifier that maps to or from the lowest (base)interface address on a given channel.

Ccache. Solid state, random access memory that islocated in a controller. The cache retains frequentlyused data for faster access by the channel. In the SVA,all data access is through cache.

cache fast write (CFW). A form of fast write in which

data is written directly to cache storage without usingnonvolatile storage and is available for later destaging.

Capacity on Demand (COD). A feature that allowsSVA customers to exceed their purchased physicalcapacity (PCAP) limit by up to 860GB of additionaltemporary effective capacity to prevent writes frombeing blocked during temporary and sometimes criticalusage periods.

channel end. The indication from the channel that ithas completed an operation.

channel interface. The Disk Array Controller circuitrythat attaches to the host channels.

cluster. See storage cluster.

collected free space %. The percentage of arraycylinders that are free array cylinders (collected andcompletely free of user data).

compaction. The SVA process that eliminatesinter-record gaps normally associated with CKD DASD.Compaction reduces the amount of wasted disk arrayspace, thus reducing the net capacity load on thesubsystem.

compression. The SVA process that reduces the sizeof data records by translating them to a differentencoding scheme that requires fewer bytes of realstorage.

controller. See Disk Array Controller.

count-key-data (CKD). A recording format that writesvariable-length records. Each record consists of 1) acount field, which specifies the length of the (optional)key field and data field of the record, 2) the (optional)key field, and 3) a data field. The first record on eachtrack contains a fourth field, home address.

current data. User data, stored in a disk array, thathas valid pointers from internal SVA mapping tables.

DDASD fast write (DFW). A form of fast write to cachein which data is written concurrently to cache andnonvolatile storage (NVS) and is subsequentlyscheduled for destaging to the disk arrays. Both copiesare retained in the SVA Disk Array Controller until thedata is completely written to the disk arrays.

Data Bridge. A pair of devices used by Power PPRCto transmit all tracks on all primary devices from the

November, 2006 — PN 311290512, Rev. N Glossary X-1

dedicated connection

primary subsystem to the secondary subsystem. Thesedevices are not used to store customer data.

dedicated connection. In an Enterprise SystemsConnection Director (ESCD), a connection between twoports that is not affected by information contained in linkframes. This connection restricts these ports fromcommunicating with any other port. The two ports havea dedicated connection that appears as one continuouslink.

Deleted Data Space Release (DDSR). An SVAAfacility for OS/390 that informs the Disk Array Controllerwhen functional volume data sets are deleted. Thephysical disk array space occupied by the deleted datacan immediately become free space, thereby reducingthe net capacity load on the subsystem.

destage. The nonsynchronous write of new or updateddata from the cache storage or nonvolatile storage tothe Disk Array Units.

device. See (1) drive module and (2) functionaldevice.

device end. An indication from an I/O device that ithas ended an operation.

device reconstruction. The SVA automaticbackground function of recreating and rewriting all ofthe data that was stored on a failed device to a sparedevice using the functional track recovery process.

direct access storage device (DASD). A storagedevice in which the medium is always available to theread/write head without having to be mounted by anexternal agent.

disk array. The SVA's logical grouping of drivemodules. See also: dual-redundancy disk array.

disk array capacity. The formatted physical capacityof a disk array excluding redundancy data.

Disk Array Controller. The SVA control unit thatprovides the interface intelligence between the host(s)and the back-end storage.

Disk Array Unit (DAU). A single physical framecontaining drive modules that comprise the disk arraystorage in an SVA subsystem.

domain. See SCSI domain.

drain. The SVA process that gradually moves datastored on a device or a disk array to other devices.Drain operations allow for the nondisruptivedeinstallation of a device or a Disk Array Unit.

drive module. A disk storage device consisting of theaccess arms and heads, disk surfaces, and the

supporting electronics required to locate, write, and readdata. Each drive module is physically packaged as asingle field-replaceable unit (FRU) within the SVA.

drive reconstruction. See device reconstruction.

dual-redundancy disk array. A disk array that allowsfor real-time automatic recovery of data from up to twofailed devices within the array.

In the V2X and V960 SVAs, a dual-redundancy diskarray consists of 15 (13+2) drive modules. The arrayhas a capacity equivalent to 13 drives of user data and2 drives of redundancy data. (In the SVA, redundancydata is distributed among all 15 drives).

In the 9500 and earlier SVAs, arrays of 7 (5+2) drivemodules can also be formed.

Dynamic Configuration. An SVA feature that allowsthe channel interfaces and up to 4096 functionalvolumes to be defined and/or altered. The functionalconfiguration of an SVA subsystem can be determinedby user requirements rather than available drivemodules.

EECAM device. A functional device over whichSVAA-based communication between the SVA DiskArray Controller and the host CPU(s) takes place.

esoteric names. The names a user assigns to DASDvolumes that have the same device type.

ESCON channel. A channel that uses ESCON cablesto transmit data between the host and the Disk ArrayController.

Extended Control and Monitoring (ECAM). Thecommunications protocol that permits communicationbetween SVAA and the SVA.

extent. A range of disk addresses expressed as acylinder head range (CCHH) for a CKD device, or alogical block address (LBA) for a SCSI device.

Ffast write. A write operation that does not requireimmediate synchronous transfer of data to a DASDdevice, thus reducing the time an application must waitfor channel end and device end for an I/O operation.

fault symptom code (FSC). An error code, generatedby a control unit or subsystem, that points to the area orFRU most likely causing a problem.

fault tolerance. The capability of a subsystem tocontinue operating without interruption and/or

November, 2006 — PN 311290512, Rev. NX-2 SVAA Configuration and Administration

LLAPI

intervention despite a failure within the subsystem (e.g.,hardware, power, cooling). Fault tolerance is generallymeasured in relation to inherent reliability, availability,serviceability, and recoverability for the product.

FDID map. See functional device identifier mapping.

fence. The automatic or manual separation of a logicalpath or physical component from the remainingoperating portion of the subsystem. The fencingprocess provides for continuous operation of thesubsystem and allows for deferred nondisruptiveservicing of field-replaceable units (FRUs) viahot-plugging.

A logical barrier on a node or path that prevents the useof that node or path.

FICON channel. A channel that uses fiber connectionsto transmit data between the host and the Disk ArrayController.

field-replaceable unit (FRU). The smallestself-contained component that can be individuallyreplaced during a service or repair action.

fixed block architecture (FBA). (Contrast with CKD)A recording format in which every track of the device isformatted with a fixed number of fixed-length records(generally called sectors), each of which contains anidentifier (ID) field and a data field.

flexvolume. A 3380 or 3390 CKD volume defined withless than the maximum number of cylinders. The rangeof cylinders allowed depends on the device type.

free array cylinder. An array cylinder that contains nocurrent or non-current user data.

free space collection (FSC). The automatic SVAbackground task that relocates data from fragmentedarray cylinders in order to collect free space into emptyarray cylinders. Free space collection maximizes theefficiency of array cylinder writes.

free space collection load. The average percentageof array cylinder space that must be relocated in orderto create empty array cylinders in the SVA.

front end. The portion of the SVA Disk ArrayController data path that passes data between thechannels and the cache.

functional. The term used to describe the SVAinterface as viewed by the host, application, and users.This interface appears as a 3990-3 subsystem interface.

functional/allocated. The user-allocated portion of afunctional volume's space; that is, data sets as definedin the VTOC.

functional capacity. The data storage capacity thatthe host, application, and users view. Used inreference to the space available for storing data in (1) asingle functional device, or (2) all defined functionaldevices in an SVA subsystem.

functional device. The volume image that the hostoperating system receives when the “Read DeviceCharacteristics” CCW is issued.

functional device identifier (FDID). The identifier fora functional device as it is known to the SVA. FDIDsrange from 0 to FFF (hexadecimal) or from 0 to 4095(decimal).

functional free space. The unallocated/unusedportion of a functional volume's space, as defined in theVTOC.

functional track. The equivalent of a 3380- or3390-DASD track. A functional track record is storedon contiguous sectors in an allocated array cylinder.

functional track directory (FTD). The SVA internalmapping table that contains one entry for eachfunctional track associated with the functional volumescurrently defined by the user.

functional track recovery (FTR). The automatic SVAprocess of recovering data from a physical track that isunreadable due to a media defect or a failed device.The SVA accomplishes functional track recovery byreading and processing the user data and redundancydata at corresponding physical track locations on theremaining devices in the array.

functional volume. See functional device.

Ggeneration data group (GDG). A collection of datasets with the same base name, such as PAYROLL, thatare kept in chronological order. Each data set is calleda generation data set.

global spares. See spare devices.

Llarge volume. A 3390-9 CKD volume defined with32760 cylinders.

link address. An address assigned during initializationthat identifies a channel or control unit so that thechannel or control unit can send and receive frames,and perform I/O operations. See logical paths.

LLAPI. An ECAM device driver available to vendorswhich provides the ability to query an SVA subsystem


logical array

and its devices as well as the ability to manipulatefunctional tracks.

logical array. A grouping of devices into an array.The grouping of devices does not depend on theirphysical location.

logical partition. The subset of a processor unit thatis allocated to support the operation of a systemscontrol program.

logical paths. The relationship between a channel anda control unit that designates the physical path to beused for device-level communication between thechannel and the control unit. This relationship isdefined within the channel and control unit by a linkaddress assigned to the control unit and a link addressassigned to the channel.

MMAT partition. The SVA partition consisting of drivemodules that are not yet available for storing user data.Drive modules are automatically members of the MATpartition when they are first physically inserted in theSVA or when they have been drained of data.

Media Acceptance Test partition. See MAT partition.

Nnet capacity load (NCL). This number is two KBtimes the number of physical sectors actually used tostore user data, not including redundancy data. NCL isa percentage of the total number of sectors that arestoring user data and is based on physical capacityused.

nonquiesced snap. A snap taken when the system isin full read-write access mode.

nonvolatile storage (NVS). The redundant solid statememory in the Disk Array Controller that remains activewhen ac power is removed. NVS protects any data thathas not been written to the disk arrays.

PParallel Access Volume. A combination of a realdevice (Base) and one or more pseudo-devices(Aliases) that together support multiple concurrent I/Osto enhance performance.

parallel channel. A channel that uses bus-and-tagcables to transmit data between the host and the DiskArray Controller.

partition. The logical separation of devices, arrays, orgroups of arrays to allow different modes of operation.

The SVA supports a MAT partition, a Test partition, aProduction partition, a Spares partition, and anUnavailable partition.

Note: The Test partition is not available in the V2X,V960, or 9500 SVA.

PAV. See Parallel Access Volume.

physical capacity. The physical space contained in(1) a single drive module, (2) a partition, or (3) an SVAsubsystem.

physical device. See drive module.

privileged ECAM device. Privileged ECAM devicesare the only devices that SVAA can use to sendmessages to the subsystem to request a change in theSVA's state. Such messages include those that alterthe subsystem configuration or start a drain.

At least one privileged ECAM device must be defined ineach SVA; all functional volumes in an SVA subsystemcan be defined as privileged ECAM devices.

Production partition. The SVA partition consisting ofdrive modules assigned to production arrays for storinguser data.

PROFSIBA macro. The profile executed when theSVAA SIBADMIN program is started.

PROFSIBS macro. The profile executed when theSVAA Subsystem Reporting Program is started.

Qquiesce. To end a process by allowing operations tocomplete normally.

quiesced snap. A snap taken while the system isquiesced; all buffered transactions are flushed to diskstorage.

Rread hit. The situation in which data requested by theread operation is located in cache.

read miss. The situation in which data requested bythe read operation is not located in cache.

reconstruction. See device reconstruction

redundancy group. A logical grouping of devices thatare protected from data loss due to a device failure bythe use of redundancy (parity) data that is stored acrossthe devices. Arrays in the SVA are redundancy groupsthat protect data against two simultaneous devicefailures. See also: dual-redundancy disk array.


subsystem free space

Reporter. The SVAA subsystem reportingprogram—the SVAA component that collects subsystemperformance data and produces reports based on thatdata, as well as on space utilization.

SSCSI channel. See SCSI I/O interface.

SCSI domain. An SVA addressing scheme, prefixed toSCSI target and LUN addresses, that extends thenumber of addressable volumes from SCSI-attachedhost systems.

serial channel. A channel that uses fiber-optic(ESCON) cables to transmit data between the host andthe Disk Array Controller. See also: ESCON channel.

Service Information Message (SIM). A messagegenerated by the host processor upon receipt of senseinformation from the SVA that contains notification of aneed for repair or customer action, or statusinformation.

Shared Virtual Array (SVA). StorageTek's online,random access disk array storage subsystem composedof a Disk Array Controller and 16 to 64 disk drivemodules.

Shared Virtual Array Administrator (SVAA).StorageTek's host software product that enablesimplementation of the extended storage managementfacilities of the SVA, and offers additional functionsincluding SnapShot, DDSR, and reporting capabilities.

SIBADMIN module. The module used to invoke SVAAin command mode.

SIBBATCH module. The SVAA module for batchconfiguration and reporting.

SIBDSR module. The SVAA module for deleted dataspace release (DDSR).

SIBIOATX exit. The Subsystem I/O Authorization userexit that verifies a user's authority to send a controlmessage to a subsystem.

SIBSNDAX exit. The Command Authorization userexit that verifies a user's authority to send a commandto a subtask in the SVAA address space.

SIBSRP module. The SVAA module for thesubsystem reporting program.

SIBSRPSW exit. The Subsystem File Switch user exitthat is invoked by the SVAA SRP data collection taskbefore closing or switching a logging file.

SIBVOP module. The SVAA operator consolecommand program.

SIM alert. An operator console message that alerts theoperator that an action requiring attention has occurred.

slot. The physical location of an SVA subsystem drivemodule.

snap. (noun) A duplication of a source volume or dataset with SnapShot (see SnapShot). A snap is also theresult of a successful SnapShot operation (not the useof a data mover). Synonymous with SnapShot.Contrast with data mover copy.

snap. (verb) To duplicate a functional volume or dataset with SnapShot.

SnapShot. StorageTek's high-speed data-duplicationfacility, available only with the SVA and packaged withSVAA. SnapShot achieves great time-savings induplicating volumes or data sets because it only createsa second set of pointers to the data. No additionalphysical disk space is used in the process.

source. The minidisk or volume from which data issnapped.

spare devices. SVA drive modules that are physicallyinstalled but not logically associated with an array.Spare devices are used by the SVA to form new arraysor to automatically reconstruct and logically replacefailed devices.

spares. See spare devices.

Spares partition. The SVA partition consisting of all ofthe spare devices in the subsystem. See sparedevices.

SSID. See subsystem identifier (SSID)

Status Bridge. A pair of devices used by PowerPPRC to transmit acknowledgements that the data wasreceived at the other end. These devices are not usedto store customer data.

storage cluster. A power and service region thatprocesses channel commands and controls the datastorage devices. The SVA contains two storageclusters, each of which contains interfaces for up to 16channels.

Storage Management Subsystem (SMS). An IBMapproach to storage management in which a hostsystem determines data placement and an automaticdata manager handles data backup, movement, space,and security.

subsystem free space. Storage space in the diskarrays that does not contain user data.


subsystem identifier (SSID)

subsystem identifier (SSID). The identifier for a 3990controller emulated within the SVA. From one tosixteen SSIDs (logical 3990s) can be defined in eachsubsystem. Within an installation, each logical 3990 isdefined by a unique four-digit (hexadecimal) SSID.

subsystem reporting program (SRP). The SVAAcomponent that collects subsystem performance dataand produces reports based on that data, as well as onspace utilization. See also: Reporter.

SVAA profile facility. When invoked, this facilityallows the user to specify commands for an SVAAsession.

Ttarget. The minidisk or volume to which data issnapped.

Test partition. The SVA partition consisting of drivemodules assigned to a test array and containing testdata. The Test partition allows user-controlled,host-driven, testing of arrays, as though they wereproduction arrays.

Note: The Test partition is not available in the V2X,V960, or 9500 SVA.

tray. The physical packaging of eight drive moduleswithin the disk array area of the SVA.

UUnavailable partition. The SVA partition consisting ofdrive modules that are not available for use in an array.Drive modules that are not installed or have failed are inthis partition.

unit. See Disk Array Unit.

V| virtual control unit (VCU). Identifies a virtual control| unit emulated within the SVA. There are currently 16| VCUs within a V2X or V2Xf represented by| hexadecimal values 0-F. These VCUs are identified to| the host system as subsystem identifiers (SSID), which| are defined at installation time.

virtual cylinder. An operating system unit of measureavailable to allow a system administrator to view andmanage the total amount of functional cylindersavailable in an SVA subsystem.

virtual device identifier (VDID). Another term forFDID. See functional device identifier (FDID).

virtual operator panel (VOP). An SVAA facility thatallows operator interaction with, and control of, the SVAvia a host operator console in lieu of the local operatorpanel (LOP), the DOP, or remote operator panel.

volatile memory. See cache volatile memory.

volume. See functional volume.

volume preferencing (VP). A facility of SnapShot thatfilters the choice of an SMS target volume for newlyallocated data sets.

volume serial number. A six-character alphanumericname that identifies a disk volume to the host operatingsystem.

Wwrite hit. The situation in which data to be updated bya write operation is located in cache.

write miss. The situation in which data to be updatedby a write operation is not located in cache.


Abbreviations and Acronyms


API application programming interface

BFDID base functional device ID

CCHH cylinder-head address (CC is thetwo-byte cylinder number, HH is thetwo-byte head number

CCW channel command word

CFW cache fast write

CKD count-key-data

CLI command line interface

COD Capacity on Demand

CSA common service area

CSI consolidated software inventory

DADSM direct access device space management

DASD direct access storage device

DAU Disk Array Unit

DDSR Deleted Data Space Release

DFP Data Facility Product

DFSMS Data Facility Storage ManagementSubsystem

DFW DASD fast write

DLIB distribution library

DOP Detached Operator Panel

DSF Data Support Facilities

DTL domain-target-LUN

ECAM Extended Control and Monitoring

ECSA extended common service area

ESA Enterprise Systems Architecture

ESCON Enterprise Systems CONnection

ESDI enhanced small device interface

FDID functional device identifier

FICON FIbre CONnection

FMID function modification identifier

FRU field-replaceable unit

FSC fault symptom code, orfree space collection

FTD functional track directory

FTR functional track recovery

GB gigabyte

GDG generation data group

GRS Global Resource Serialization

GTF generalized trace facility

HCD hardware configuration definition

HSI Host Subsystem Interface

ICKDSF ICK Data Support Facilities

IDCAMS IDC access method services

IDID interface device identifier

IML initial microprogram/microcode load

IOCP I/O configuration program

IPL initial program load

ISPF Interactive System Productivity Facility

I/O input/output

LBA logical block address

LOP Local Operator Panel

LUN logical unit number

MAT Media Acceptance Test

MB megabyte

MIH missing interrupt handler

MVS Multiple Virtual Storage

NCL net capacity load

NVS nonvolatile storage

PAV Parallel Access Volume

PCAP physical capacity

PPRC peer-to-peer remote copy

PTF program temporary fix

RACF Resource Access Control Facility

RAID redundant array of inexpensive disks

REXX Restructured Extended Executor

RFA record format assist

RIM resource initialization module

RMF resource measurement facility

SAF Security Access Facility

SCP system control program

SCSI small computer system interface

SFC Server Framework Component

SIM service information message

SMF system management facility

SMP/E System Modification Program Extended

November, 2006 — PN 311290512, Rev. N Abbreviations and Acronyms X-7


SMS Storage Management Subsystem

SRP Subsystem Reporting Program

SSID subsystem identifier

SVA Shared Virtual Array

SVAA Shared Virtual Array Administrator

TSO Time Sharing Option

UCB unit control block

VCU virtual control unit

VDID virtual device identifier

volser volume serial number

VOP virtual operator panel

VP volume preferencing

VSAM Virtual Storage Access Method

VTOC volume table of contents

VVDS VSAM volume data set

VVR VSAM volume record


Index

Aadvantages of SnapShot 5-2Allocate Spares panel 7-74ALLOCATE SPARES subcommand 8-12allocating spares

steps in 6-11using panels 7-73using subcommand 8-12

ALTER CHANNEL subcommand 8-13ALTER DEVICE subcommand 8-20ALTER SUBSYSTEM subcommand 8-29altering channel interface characteristics 6-2, 7-20,

8-13array

capacity ofSee disk array capacity

changing size ofusing panels 7-17using subcommand 8-30, 8-63

draining 2-5, 7-86, 8-198forming

first 2-3overview 2-3steps in 6-12using panels 7-76, 7-79using subcommand 8-63

reconfiguring 6-14array spares

See sparesasterisk, used in commands 8-8ATTN DEVICE subcommand 8-36

Bbase address trapped by channel 8-17base functional device ID (BFDID) 8-17batch jobs

subcommands in OS/390 3-4batch, running SVAA in 3-2, 3-5, 8-6browsing (panels)

panel flow diagram 7-67

Ccache for functional device

disablingusing panels 7-45, 7-52, 7-59using subcommands 8-23, 8-40

enablingusing panels 7-45, 7-52, 7-59using subcommands 8-23, 8-40

cache size (term in reports) 8-110

capacity, of disk arraySee disk array capacity

cascaded FICON switches, configuring 6-15case

in commands 8-8querying 8-129setting, using panels 7-8setting, using subcommand 8-160upper or mixed, in subcommand entry 8-8

Channel Configuration panelESCON channel 7-27fibre channel 7-31FICON channel 7-33parallel channel 7-25SCSI I/O interface 7-29

channel interfaceaddresses trapped, range of 7-26, 7-27, 7-33, 8-16altering characteristics of 7-20, 8-13

ESCON channel 6-3, 7-27, 8-15fibre channel 6-3, 7-31, 8-15FICON channel 6-3, 7-32, 8-15parallel channel 6-2, 7-25, 8-14SCSI I/O interface 6-3, 7-29, 8-15

base address trapped 7-26, 7-27, 7-33, 8-17base functional device ID 7-26, 7-27, 7-33, 8-17changing name of

using panels 7-25, 7-28, 7-30, 7-32, 7-34using subcommand 8-18

configuring at DOP 1-3configuring at LOP 1-3disabling

using panels 7-25using subcommands 8-18, 8-206

display (subcommand) 8-53enabling


ID 8-16, 8-53, 8-68, 8-206SCSI identifier 7-29speed of data transfer 7-26, 7-27, 7-29, 7-31, 7-33,

8-19vary (subcommand) 8-205

Channel Selection panelall channels 7-21ESCON channel 7-22fibre I/O interface 7-23FICON I/O interface 7-24parallel channel 7-22SCSI I/O interface 7-23

channel speed (term in reports) 8-111Channel Type Selection panel 7-21CKD device

disabling 6-9

November, 2006 — PN 311290512, Rev. N Index X-9

CKD device (continued)host access to

using panels 7-45, 7-51, 7-59using subcommands 8-24, 8-41, 8-208

write access tousing panels 7-45, 7-51, 7-59using subcommands 8-24, 8-41, 8-209

cluster (term in reports) 8-110CMDECHO

querying 8-130setting 8-161

collected free space 7-17collected free space % (term in reports) 8-111command syntax notation xivcommands

See also subcommandsin SVAA 8-6output from 3-5

default destination 3-6querying destination 8-131redirecting 8-5, 8-10, 8-162

concurrent copy 5-2CONFIGPATH


configurationchanging for existing array 6-14displaying drive module 6-15minimum subsystem (defining at DOP) 1-3minimum subsystem (defining at LOP) 1-3of functional devices 6-5of subsystem array capacity 6-11task outline 6-1V2Xf PPRC with cascaded FICON switches in a

WWNN Domain 6-15considerations for multivolume data sets 5-7considerations for source data sets 5-7continuation of subcommands 8-10conventional duplication 5-2COPYLIM, updating

altering, using subcommand 8-31

DDASD fastwrite for functional device

disablingusing panels 7-45, 7-52, 7-60using subcommands 8-24, 8-41

enablingusing panels 7-45, 7-52, 7-60using subcommands 8-24, 8-41

DASDVOL class alter authority 7-66, 8-51data bridge, defining

using panels 7-46, 7-52, 7-60using subcommands 8-41

Data Collection task (SIBSRP task)send command request to 8-154

Data Collection task (SIBSRP task) (continued)SEND SRP subcommand 8-154START SRP command 8-197STOP SRP command 8-202

data mover 5-4, 5-5data sets

kinds not snapped 5-5kinds snapped 5-4

DCB attributes 5-5DDSR (Deleted Data Space Release)

display release status 8-60DISPLAY RELEASE subcommand 8-60dynamic DDSR 4-2, 4-3

control parameters 8-139Dynamic DDSR control parameters 4-3Dynamic DDSR diagnostics 4-3Dynamic DDSR intercept 4-3interval DDSR 4-2, 4-5

control parameters 8-143Interval DDSR control parameters 4-5Interval DDSR diagnostics 4-7interval task 4-4Main Task 4-4messages 4-7RELEASE DYNAMICDATA subcommand 4-3,

8-139release identifier 4-7RELEASE INTERVALDATA subcommand 4-5,

8-143release task identifier 8-143, 8-202RESUME RELEASE subcommand 8-151SEND DSR subcommand 8-152simulate processing 4-13SMF record format B-1START DSR command 8-196START RELEASE subcommand 8-201STOP DSR command 8-202STOP RELEASE subcommand 8-203SUSPEND RELEASE subcommand 8-204task identifier 4-7, 8-143, 8-202

DDSR tasksinterval task 4-4Main Task 4-4task identifier 4-7

DEBUGquerying 8-130setting 8-162

DEFINE DEVICE subcommand 8-38defining a data bridge


defining a functional device 6-5using panels 7-40, 7-48using subcommand 8-38

defining a status bridgeusing panels 7-46, 7-52, 7-60using subcommands 8-47


defining SSIDs 7-18DELETE DEVICE subcommand 8-49Delete Functional Device panel 7-63Deleted Data Space Release (DDSR) 1-1, 4-1deleting a functional device

FORCE parameter 8-51steps in 6-8using panels 7-61using subcommand 8-49

destination for messagesSee messages, destination of

destination for outputSee commands, output from

destinations for OUTMSG and OUTFILE 3-6querying 8-131setting 8-162

detached operator panel (DOP) 1-3, 2-3device

See CKD device, ECAM device, functional device,privileged ECAM device, non-Iceberg device, SCSIdevice

DFSMSdss, example of 8-174diagnostic materials for service xxdisabling a channel interface


disabling a CKD functional device 6-9disabling a SCSI functional device 6-9disabling cache

using panels 7-45, 7-52, 7-59using subcommands 8-23, 8-40

disabling DASD fastwriteusing panels 7-45, 7-52, 7-60using subcommands 8-24, 8-41

disk array capacityconfiguring for subsystem 6-11establishing for Test partition 6-12moving from Test to Production partition 6-13,

8-116removing from Test partition 6-13term in reports 8-112

disk array unit (DAU), draining 2-5, 7-86, 8-198DISPLAY CHANNEL subcommand 8-53DISPLAY DEVICE subcommand 8-55Display Drive Module Status panel 7-71, 7-72DISPLAY NCL subcommand 8-59DISPLAY RELEASE subcommand 8-60drain 7-86, 8-198

definition of 2-5displaying status of 7-91Drive Module Drain Status panel 7-91Event Selection panel 7-88Event Summary panel 7-90report events (subcommand) 8-148reporting events 2-6, 6-15starting 6-15

using panels 7-85using subcommand 8-198

Drain Drive Module(s) panel 7-86drive module

allocating, as spares 6-11, 7-73, 8-12configuration report 8-75displaying configuration 6-15displaying status, using panels 7-70draining 2-5, 7-86, 8-198status codes A-1

Drive Module Drain Status panel 7-91Drive Module Test (MAT) Detail Status panel 7-94Drive Module Test (MAT) Status panel 7-93Drive Module Utilities menu 7-69DROP ECAMDEVICE subcommand 8-62DROP NONICEBERG subcommand 8-62DROP subcommands 8-62DSR task (DDSR Main Task)

send command request to 8-152SEND DSR subcommand 8-152START DSR command 8-196STOP DSR command 8-202

dual copy 5-2dump


duplication using SnapShot 5-2duplication, conventional 5-2Dynamic Configuration 1-1dynamic DDSR 4-2, 4-3

See also DDSR (Deleted Data Space Release)control parameters 4-3diagnostics 4-3intercept 4-3

EECAM device

defining 8-164dropping 8-62privileged

See privileged ECAM device, definingquerying 8-132setting 8-164

enabling a channel interfaceusing panels 7-26using subcommands 8-18, 8-206

enabling cacheusing panels 7-52, 7-59using subcommands 8-23, 8-40

enabling DASD fastwriteusing panels 7-45, 7-52, 7-60using subcommands 8-24, 8-41

Enter key 7-3entering values on panels 7-3environment

OS/390 3-2SIB 3-4, 8-5

ESCON channel


ESCON channel (continued)See serial channel, changing name

eventdetail status, MAT 7-94identifier 8-148report 8-148selection 7-88status

displaying 7-88drain 7-91MAT 7-93

summary 7-90Event Selection panel 7-89Event Summary panel 7-90existing VSAM target data sets 5-8

FFACILITY class Alter authority 7-66, 8-51fast path replicate 7-38FDID (term in reports) 8-112fibre channel, changing name


FlexVolume, definingusing subcommands 8-42

FlexVolumesFlexVolume Operational Requirements 2-22

FORM ARRAY subcommand 8-63Form Production Array(s) panel 7-80Form Test Array(s) panel 7-77forming arrays 2-3

steps in 6-12using panels 7-76, 7-79using subcommand 8-63

function keys 7-3, 7-4functional capacity (term in reports) 8-112functional device 7-35

attn (subcommand) 8-36cache

disabling, using panels 7-52, 7-59disabling, using subcommands 8-23, 8-40enabling, using panels 7-45, 7-52, 7-59enabling, using subcommands 8-23, 8-40

changing characteristics of 6-6device type 6-7partition 6-6using subcommand 8-20

CKD, access 6-9using panels 7-45, 7-51, 7-59using subcommands 8-24, 8-41, 8-208

configuring 6-5, 7-35DASD fastwrite

disabling, using panels 7-45, 7-52, 7-60disabling, using subcommands 8-24, 8-41enabling, using panels 7-45, 7-52, 7-60enabling, using subcommands 8-24, 8-41

functional device (continued)defining 6-5

using panels 7-40, 7-48using subcommand 8-38

deletingsteps in 6-8using panels 7-61using subcommand 8-49

disabling 6-9displaying, using subcommand 8-55initializing

using panels 7-46, 7-52, 7-54with DEFINE DEVICE 8-43with INITIALIZE DEVICE 8-65

inserting 7-40number of 7-17privileged ECAM

See privileged ECAM device, definingreplicating 7-48report 8-70SCSI address, displayed 7-44, 7-51, 7-58SCSI block size, defining 7-44, 7-51, 8-46SCSI, access 6-9


SCSI, initializingusing panels 7-46, 7-52, 7-54with DEFINE DEVICE 8-43with INITIALIZE DEVICE 8-65

state-change interrupt 8-36type emulated 7-44, 7-51, 8-40updating 7-56vary (subcommand) 8-207write access

to CKD device 7-45, 7-51, 7-59, 8-24, 8-41,8-209

to SCSI device 7-45, 7-51, 7-59, 8-27, 8-46,8-209

Functional Device Selection panel 7-36

Gglobal spares

current setting displayed on panel 7-16glossary X-1

Hhardware configuration definition (HCD) 1-3host access

to CKD deviceusing panels 7-45, 7-51, 7-59using subcommands 8-24, 8-41, 8-208

to SCSI deviceusing panels 7-45, 7-51, 7-59using subcommands 8-27, 8-46, 8-209


II/O configuration program (IOCP) 1-3IMPEX


initialization of SVAA 3-2INITIALIZE DEVICE subcommand 8-65Initialize Functional Device panel 7-55initializing a SCSI device

using panels 7-46, 7-52, 7-54with DEFINE DEVICE 8-43with INITIALIZE DEVICE 8-65

Insert Functional Device panel 7-42interface ID (term in reports) 8-112interface name (term in reports) 8-112interval DDSR 4-2, 4-5

See also DDSR (Deleted Data Space Release)control parameters 4-5diagnostics 4-7interval task 4-4Main Task 4-4messages 4-7

invoking SnapShot 5-3ISPF, running SVAA from 7-2, 7-5

JJAVA_HOME


job card 7-8

LLarge Volume, defining

using subcommands 8-42Large Volumes

Large Volume Operational Requirements 2-23line commands 7-38LISTCFG CHANNEL subcommand 8-68LISTCFG DEVICE subcommand 8-70LISTCFG DRIVEMODULE subcommand 8-75LISTCFG report headings defined 8-110LISTCFG SUBSYSTEM subcommand 8-78lists (in parameter entry) 8-10local operator panel (LOP) 1-3, 2-3LOGFILE


MMACRO subcommand 8-115macros 3-4main DDSR task 4-4main menu, SVAA 7-5

management class 5-6MAT partition

allocating spares 7-74, 8-12description of 2-4starting drain 7-86, 8-198status codes A-1

MAXRCquerying 8-133setting 8-165

menusentering values on 7-3option field 7-2SVAA main menu 7-5

messagescategories 7-45, 7-52, 7-60destination of 3-5


help 7-4location on panel 7-3

microcode level 1-2MIH parameter 6-5minimum configuration (at DOP) 1-3minimum configuration (at LOP) 1-3missing-interrupt handler 6-5Move Test into Production panel 7-83MOVE TESTPARTITION subcommand 8-116moving drive modules from test to production 6-13


NNCL, effect on 5-9net capacity load (NCL)

display (subcommand) 8-59term in reports 8-112

net capacity load % (term in reports) 8-112non-Iceberg device

dropping 8-62querying 8-134setting 8-166

notation xivnumber of functional devices (term in reports) 8-112NVS size (term in reports) 8-113

Ooperating environment

OS/390 3-2SIB 3-4, 8-5

operator commands 8-6operator panel

See local operator panel (LOP), virtual operatorpanel (VOP)

OS/390 command output 3-5OS/390 environment 3-2


OUTFILESee commands, output from

OUTMSGSee messages, destination of

output destinationSee commands, output from

overall totals (term in reports) 8-113overview of SnapShot 1-1, 5-2

Ppage size

querying 8-134setting, using panels 7-8setting, using subcommand 8-166

panelAllocate Spares 7-74Channel Configuration (ESCON channel) 7-27Channel Configuration (fibre channel) 7-31Channel Configuration (FICON channel) 7-33Channel Configuration (parallel channel) 7-25Channel Configuration (SCSI I/O interface) 7-29Channel Selection 7-21, 7-22, 7-23, 7-24Channel Type Selection 7-21command field 7-2commands 7-3, 7-4Delete Functional Device 7-63Display Drive Module Status 7-71, 7-72Drain Drive Module(s) 7-86Drive Module Drain Status 7-91Drive Module Test (MAT) Detail Status 7-94Drive Module Test (MAT) Status 7-93Drive Module Utilities 7-69Enter key, using on 7-3entering values on 7-3Event Selection 7-89Event Summary 7-90Form Production Array(s) 7-80Form Test Array(s) 7-77function keys 7-3, 7-4Functional Device Selection 7-36ID 7-2Initialize Functional Device 7-55Insert Functional Device 7-42Move Test into Production 7-83option field 7-2Replicate Functional Device 7-49Shared Virtual Array Administrator Session

Administration 7-6SnapShot Subcommand Selection 7-96Specify Remote PPRC SnapShot Volume

Subcommand 7-104Specify Snap Dataset Subcommand 7-97Specify Snap Volume Subcommand 7-101SSID Definition 7-18starting 7-10Subsystem Administration 7-10

panel (continued)Subsystem Component Selection 7-12Subsystem Configuration 7-15Subsystem Configuration, V2Xf 7-16Subsystem Selection 7-13SVAA main menu 7-5SVAA Report Titles 7-9SVAA Session Profile 7-7Tab key, using on 7-3Update Functional Device 7-57

parallel channel, configuring 6-2using panels 7-25using subcommand 8-14

parameter descriptions 8-11PARMLIB member 3-3

querying 8-134setting, using panels 7-8

partition 2-4changing, of a functional device 6-6drive module status codes for each A-1MAT

See MAT partitionProduction

See Production partitionSpares

See Spares partitionTest

See Test partitionUnavailable

See Unavailable partitionPAV

First-Time User Considerations for PAV 2-15PAV Configuration Considerations 2-17PAV Differences 2-19

PAV status (term in reports) 8-113PAVBASE

specifying, for device 8-45peer-to-peer remote copy (PPRC) 2-7, 5-10PF keys 7-3, 7-4phys cap used (term in reports) 8-113Point-in-Time Reports 8-155Power PPRC 2-7PPRC 2-7PPRC and SnapShot 5-10PPRC QUERY report headings defined 8-126PPRC Remote SnapShot 2-11PPRC SNAPSHOT VOLUME

panel 7-104PPRC status (term in reports) 8-113PPRCfcn 2-11PPRCOPY subcommand 8-117privileged ECAM device, defining

See also ECAM deviceadditional 6-10at DOP 1-3at LOP 1-3using panels 7-45, 7-52, 7-60


privileged ECAM device, defining (continued)using subcommands 8-26, 8-45

product support xxProduction array, forming 7-79, 8-63Production partition

description of 2-4forming arrays 6-12, 6-13, 7-80, 8-63moving drives to 7-83, 8-116specifying, for device 8-44status codes A-1term in reports 8-114

profileoptions, setting 7-7querying 8-135setting case


setting page sizeusing panels 7-8using subcommand 8-166

setting PARMLIB memberusing panels 7-8

setting titlesusing panels 7-9using subcommand 8-169

PROFSIBA macro 3-3

QQUERY CACHEREFRESHRATE subcommand 8-128QUERY CASE subcommand 8-129QUERY CHECK subcommand 8-129QUERY CMDECHO subcommand 8-130QUERY CONFIGPATH subcommand 8-130QUERY DEBUG subcommand 8-130QUERY DESTINATION subcommand 8-131QUERY DEVICE subcommand 8-131QUERY DUMP subcommand 8-132QUERY ECAMDEVICE subcommand 8-132QUERY IMPEX subcommand 8-132QUERY JAVA_HOME subcommand 8-133QUERY LOGFILE subcommand 8-133QUERY MAXRC subcommand 8-133QUERY NONICEBERG subcommand 8-134QUERY PAGESIZE subcommand 8-134QUERY PARMLIB subcommand 8-134QUERY PROFILE subcommand 8-135QUERY SERVERIDLETIME subcommand 8-135QUERY SERVERNAME subcommand 8-135QUERY SERVERPROC subcommand 8-136QUERY SERVERSCRIPT subcommand 8-136QUERY SIBHOME subcommand 8-136QUERY SIBPORT subcommand 8-136QUERY SSNAME subcommand 8-137QUERY subcommands 8-128QUERY SUBSYSTEM subcommand 8-137QUERY TITLEn subcommand 8-137

QUERY VERSION subcommand 8-138QUERY VOLUMEPREFERENCING

subcommand 8-138QUERY WEBPORT subcommand 8-139query, used in commands 8-8question mark, used in commands 8-8

RRACF

DASDVOL class alter authority 7-66, 8-51FACILITY class Alter authority 7-66, 8-51

ranges (in parameter entry) 8-9redirecting subcommand output 3-6, 8-5, 8-10RELEASE DYNAMICDATA subcommand 8-139RELEASE INTERVALDATA subcommand 8-143release task identifier 8-143, 8-202releasing data space 8-139, 8-143removing Test partition array capacity 6-13Replicate Functional Device panel 7-49REPORT EVENTS subcommand 8-148report headings defined 8-110, 8-126report titles

querying 8-137specifying by subcommand 8-169specifying with panels 7-9

Report Titles panel 7-9reports

channel configuration 8-68drain 6-15, 8-148drive module configuration 8-75event 8-148functional device configuration 8-70subsystem configuration 8-78titles, querying 8-137titles, specifying by subcommand 8-169

RESUME RELEASE subcommand 8-151rules for entering subcommands 8-7

asterisk 8-8case 8-8colon 8-9lists 8-10parentheses 8-7question mark 8-8ranges 8-9subcommand continuation 8-10wildcard characters 8-8

SSCSI address

altering for a functional device 8-26defining for a functional device 8-46displayed 7-44, 7-51, 7-58maximum 7-17

SCSI block sizedefining 7-44, 7-51, 8-46displayed 7-58


SCSI channelSee SCSI I/O interface, changing name

SCSI devicedisabling 6-9host access to


initializingusing panels 7-46, 7-52, 7-54with DEFINE DEVICE 8-43with INITIALIZE DEVICE 8-65

write access tousing panels 7-45, 7-51, 7-59using subcommands 8-27, 8-46, 8-209

SCSI I/O interface, changing name 6-3using panels 7-29using subcommand 8-15

SCSI SIM statusdefining 7-17

security considerations 5-10SEND DSR subcommand 8-152SEND SFC subcommand 8-153SEND SIM subcommand 8-153SEND SRP subcommand 8-154SEND subcommands 8-152SEND VOP subcommand 8-154serial channel, changing name 6-3

using panels 7-27, 7-32using subcommand 8-15

Server Framework Component (SFC) tasksend command request to 8-153SEND SFC subcommand 8-153START SFC command 8-196STOP SFC command 8-202

SERVERNAMEquerying 8-135setting 8-167

SERVERPROCquerying 8-136setting 8-167

SERVERSCRIPTquerying 8-136setting 8-168

Service Information Message (SIM) tasksend command request to 8-153SEND SIM subcommand 8-153START SIM command 8-196STOP SIM command 8-202

service, product xxSession Administration menu 7-6Session Profile panel 7-7SET CACHEREFRESHRATE subcommand 8-155SET CASE subcommand 8-160SET CHECK subcommand 8-160SET CMDECHO subcommand 8-161SET CONFIGPATH subcommand 8-161

SET DEBUG subcommand 8-162SET DESTINATION subcommand 8-162SET DUMP subcommand 8-163SET ECAMDEVICE subcommand 8-164SET IMPEX subcommand 8-164SET JAVA_HOME subcommand 8-165SET LOGFILE subcommand 8-165SET MAXRC subcommand 3-4, 8-165SET NONICEBERG subcommand 8-166SET PAGESIZE subcommand 8-166SET SERVERNAME subcommand 8-167SET SERVERPROC subcommand 8-167SET SERVERSCRIPT subcommand 8-168SET SIBHOME subcommand 8-168SET SIBPORT subcommand 8-168SET SSNAME subcommand 8-169SET TITLEn subcommand 8-169SET VOLUMEPREFERENCING subcommand 8-170SET WEBPORT subcommand 8-171setting case


setting page sizeusing panels 7-8using subcommand 8-166

setting PARMLIB memberusing panels 7-8

setting titlesusing panels 7-9using subcommand 8-169

SFC (Server Framework Component) tasksend command request to 8-153SEND SFC subcommand 8-153START SFC command 8-196STOP SFC command 8-202

SIB environment 3-4, 8-5SIB: prompt 3-4, 8-5SIBADMIN 3-2, 3-4, 8-5

command 3-2, 3-4, 8-5executing SVAA macros from 8-6executing SVAA subcommands from 3-2, 8-5

SIBBATCH 3-2, 3-4, 8-6executing SVAA subcommands from 3-2, 3-4, 8-6input 3-5

SIBHOMEquerying 8-136setting 8-168

SIBPORTquerying 8-136setting 8-168

SIBSTK00 member 3-2overriding 3-4, 3-5

SIM (Service Information Message) tasksend command request to 8-153SEND SIM subcommand 8-153START SIM command 8-196STOP SIM command 8-202


site name, updatingusing panels 7-17using subcommand 8-32

SMF recordsDDSR record format B-1SnapShot record format B-4SVAA record subtype 5 format B-1SVAA record subtype 8 format B-4

SMS targets, choosing 5-9SNAP DATASET

overview 5-4panel 7-97subcommand 8-172

Snap to Primary 2-10SNAP VOLUME

overview 5-3panel 7-101subcommand 8-185

snap, definition of 5-2snapping data sets of the same name 5-7snapping data sets, overview 5-4snapping to data sets of the same name 5-7snapping to new VSAM target data sets 5-8snapping volumes, overview 5-3SnapShot

advantages of 5-2and PPRC 5-10and SMS 5-6effect on NCL 5-9invoking 5-3overview 1-1, 5-2PPRC considerations 5-10resources needed for 5-3security considerations 5-10using panels 7-96

SnapShot and DFSMSdss, diagnosis 5-13SnapShot panels

SnapShot Subcommand Selection 7-96Specify Remote PPRC SnapShot Volume

Subcommand 7-104Specify Snap Dataset Subcommand 7-97Specify Snap Volume Subcommand 7-101

SnapShot SMF record format B-4SnapShot subcommands

QUERY VOLUMEPREFERENCING 8-138SET VOLUMEPREFERENCING 8-170SNAP DATASET 8-172SNAP VOLUME 8-185

sort command 7-38source data setsspares

allocating 6-11, 7-73, 8-12available to form array 7-77, 7-80global 7-16number for array 2-3required for drain 7-87

Spares partitionallocating drives to 7-74, 8-12description of 2-4status codes A-1

Specify PPRC Remote SnapShot Volume Subcommandpanel 7-104

Specify Snap Dataset Subcommand panel 7-97Specify Snap Volume Subcommand panel 7-101speed, channel data transfer 7-26, 7-27, 7-29, 7-31,

7-33, 8-19SRP task (Reporter Data Collection task)

send command request to 8-154SEND SRP subcommand 8-154START SRP command 8-197STOP SRP command 8-202

SSIDdefining

at DOP 1-3at LOP 1-3using panels 7-18using subcommand 8-32, 8-33

term in reports 8-114SSID Definition panel 7-18SSNAME

querying 8-137setting, using panels 7-8setting, using subcommand 8-169

standard PPRC 2-7START DRAIN subcommand 8-198START DSR command 8-196START RELEASE subcommand 8-201START SFC command 8-196START SIM command 8-196START SRP command 8-197START VOP command 8-197status bridge, defining


STOP commands 8-202STOP DSR command 8-202STOP RELEASE subcommand 8-203STOP SFC command 8-202STOP SIM command 8-202STOP SRP command 8-202STOP VOP command 8-203storage class 5-6storage needed 5-3subcommands 8-1

See also commandsALLOCATE SPARES 8-12ALTER CHANNEL 8-13ALTER DEVICE 8-20ALTER SUBSYSTEM 8-29ATTN DEVICE 8-36continuation of 8-10conventions 8-7DEFINE DEVICE 8-38


subcommands (continued)definition of 3-4DELETE DEVICE 8-49DISPLAY CHANNEL 8-53DISPLAY DEVICE 8-55DISPLAY NCL 8-59DISPLAY RELEASE 8-60DROP ECAMDEVICE 8-62DROP NONICEBERG 8-62FORM ARRAY 8-63general form of 8-5INITIALIZE DEVICE 8-65LISTCFG CHANNEL 8-68LISTCFG DEVICE 8-70LISTCFG DRIVEMODULE 8-75LISTCFG SUBSYSTEM 8-78MACRO 8-115MOVE TESTPARTITION 8-116output from

See commands, output fromPPRCOPY 8-117QUERY CACHEREFRESHRATE 8-128QUERY CASE 8-129QUERY CHECK 8-129QUERY CMDECHO 8-130QUERY CONFIGPATH 8-130QUERY DEBUG 8-130QUERY DESTINATION 8-131QUERY DEVICE 8-131QUERY DUMP 8-132QUERY ECAMDEVICE 8-132QUERY IMPEX 8-132QUERY JAVA_HOME 8-133QUERY LOGFILE 8-133QUERY MAXRC 8-133QUERY NONICEBERG 8-134QUERY PAGESIZE 8-134QUERY PARMLIB 8-134QUERY PROFILE 8-135QUERY SERVERIDLETIME 8-135QUERY SERVERNAME 8-135QUERY SERVERPROC 8-136QUERY SERVERSCRIPT 8-136QUERY SIBHOME 8-136QUERY SIBPORT 8-136QUERY SSNAME 8-137QUERY SUBSYSTEM 8-137QUERY TITLEn 8-137QUERY VERSION 8-138QUERY VOLUMEPREFERENCING 8-138QUERY WEBPORT 8-139redirecting output 3-6RELEASE DYNAMICDATA 8-139RELEASE INTERVALDATA 8-143REPORT EVENTS 8-148RESUME RELEASE 8-151SEND DSR 8-152

subcommands (continued)SEND SFC 8-153SEND SIM 8-153SEND SRP 8-154SEND VOP 8-154SET CACHEREFRESHRATE 8-155SET CASE 8-160SET CHECK 8-160SET CMDECHO 8-161SET CONFIGPATH 8-161SET DEBUG 8-162SET DESTINATION 8-162SET DUMP 8-163SET ECAMDEVICE 8-164SET IMPEX 8-164SET JAVA_HOME 8-165SET LOGFILE 8-165SET MAXRC 8-165SET NONICEBERG 8-166SET PAGESIZE 8-166SET SERVERIDLETIME 8-166SET SERVERNAME 8-167SET SERVERPROC 8-167SET SERVERSCRIPT 8-168SET SIBHOME 8-168SET SIBPORT 8-168SET SSNAME 8-169SET TITLEn 8-169SET VOLUMEPREFERENCING 8-170SET WEBPORT 8-171SNAP DATASET 8-172SNAP VOLUME 8-185START DRAIN 8-198START DSR 8-196START RELEASE 8-201START SFC 8-196START SIM 8-196START SRP 8-197START VOP 8-197STOP DSR 8-202STOP RELEASE 8-203STOP SFC 8-202STOP SIM 8-202STOP SRP 8-202STOP VOP 8-203SUSPEND RELEASE 8-204using in batch jobs 3-4VARY CHANNEL 8-205VARY DEVICE 8-207

subsystemconfiguration 6-2

browsing 7-67updating using panels 7-14, 7-17updating using subcommand 8-29

disk array capacity for 6-11querying 8-137unique name for 1-3


Subsystem Administration menu 7-10Subsystem Component Selection menu 7-12Subsystem Configuration panel 7-15Subsystem Configuration panel for the V2Xf 7-16subsystem identifier (SSID)

definingat DOP 1-3at LOP 1-3using panels 7-18using subcommand 8-32, 8-33

term in reports 8-114subsystem name (term in reports) 8-114Subsystem Selection panel 7-13support, product xxSUSPEND RELEASE subcommand 8-204SVAA

commands 8-6input for 3-2output from 3-5SIBADMIN 3-2, 8-5, 8-6

configuration, introduction 1-1definition of 1-1initialization routines 3-2main menu 7-5options for running

from ISPF 7-2, 7-5in batch 3-2, 3-4, 3-5, 8-6in TSO 3-4, 8-5

OS/390 environment 3-2panel commands 7-3, 7-4panels 7-2session administration 7-6subcommands 8-1

SVAA Report Titles panel 7-9SVAA Session Administration menu 7-6SVAA Session Profile panel 7-7syntax diagram notation xivsystem operator commands 8-6

TT/P (term in reports) 8-114Tab key 7-3target data sets

alternate 5-8existing 5-8target 5-8

terminology 5-7Test array, forming 7-76, 8-63Test partition

description of 2-4forming arrays 6-12, 7-77, 8-63moving drives to Production partition 6-13, 7-83,

8-116removing arrays 6-13status codes A-2term in reports 8-114

titles for reportsquerying 8-137setting, using panels 7-9setting, using subcommand 8-169

total functional capacity (term in reports) 8-114totals (term in reports) 8-115tray, draining 2-5, 7-86, 8-198TSO environment 3-4, 8-5

UUnavailable partition

description of 2-4status codes A-2

uncollected free space 7-17term in reports 8-115

Update Functional Device panel 7-57utilities

drive module 7-68

VVARY CHANNEL subcommand 8-205VARY DEVICE subcommand 8-207VERIFY parameter

in ALTER CHANNEL 8-19in ALTER DEVICE 8-27in ALTER SUBSYSTEM 8-34in DELETE DEVICE 8-52

version, querying 8-138virtual operator panel (VOP) task

send command request to 8-154SEND VOP subcommand 8-154START VOP command 8-197STOP VOP command 8-203

volser (term in reports) 8-115volume preferencing

considerations for data sets spanning SVAs 5-10overview 5-9querying 8-138setting 8-170

VOP (virtual operator panel) tasksend command request to 8-154SEND VOP subcommand 8-154START VOP command 8-197STOP VOP command 8-203

VSAM alternate index data sets 5-8

Wwildcard characters 8-8write access

to CKD deviceusing panels 7-45, 7-51, 7-59using subcommands 8-24, 8-41, 8-209

to SCSI deviceusing panels 7-45, 7-51, 7-59using subcommands 8-27, 8-46, 8-209


Printed in U.S.A.

SUN™ THE NETWORK IS THE COMPUTER ©2006 Sun Microsystems, Inc. All rights reserved. Sun, Sun Microsystems, and the Sun logo are trademarks or registered trademarks of Sun Microsystems, Inc. in theUnited States and other countries.

Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 USA Phone 1-650-960-1300 or 1-800-555-9SUN Web sun.com

ARGENTINA: 5411-4317-5636 • AUSTRALIA: 1-800-550-786 • AUSTRIA: 43-1-601-26-0 • BALKANS: 301-6188-111 • BELGIUM: 32 2-704 89 83 • BRAZIL: 55-11-51872100 • BRUNEI: 65-216-8333 • CANADA: 1-800-422-8020 (GENERAL); 416-964-2001 (LEARNING MANAGEMENT SYSTEM SALES,TORONTO) • CHILE: 562-372-4500 • COLOMBIA: 571-629-2323CZECH REPUBLIC: 420 2 33009311 • DENMARK: 45 4556 5040 • EGYPT: 00 202 570 9442 • FINLAND: 358-9-525-561 • FRANCE: 33-1-41-33-17-17 • GERMANY: 49-89-460-08-2788 • GREECE: 30-01-6188101 • HONG KONG: 852-2877-7077 • HUNGARY: 361-202-4415 • INDIA: 91-80-229-8989 • INDONESIA: 65-216-8333 • IRELAND: 353-1-668-4377ISRAEL: 972-9-9710500 • ITALY: 39-02-9259511 • JAPAN: 81-3-5779-1820 • KOREA: 82-2-3453-6602 • MALAYSIA: 603-2116-1887 • MIDDLE EAST: 00 9714 3366333 • MEXICO: 525-261-0344 • NETHERLANDS: 31-33-4515200 • NEW ZEALAND: 0800-786-338 • NORTH WEST AFRICA: 00 9714 3366333 • NORWAY: FROM NORWAY: 47-22023950, TO NORWAY:47-23369650 • PAKISTAN: 00-9714-3366333 • PEOPLE'S REPUBLIC OF CHINA: 8610-6803-5588 • PHILIPPINES: 632-885-7867 • POLAND: 48-22-8747848 • PORTUGAL: 351-21-413-4000 • RUSSIA: 7-095-935-8411 • SAUDI ARABIA: 00 9714 3366333 • SINGAPORE: 65-216-8300 • SOUTH AFRICA: 27-11-256-6300 • SPAIN: 34-902-210-412 • SRI LANKA:65-2168333 • SWEDEN: 46-8-631 22 00 • SWITZERLAND: 41-1-908-90-50 (GERMAN) 41-22-999-0444 (FRENCH) • TAIWAN: 886-2-25185735 • THAILAND: 662-344-6855 • TURKEY: 90 212 335 22 00 • UNITED KINGDOM: 44-1276-416-520 • UNITED STATES: 1-800-422-8020 • VENEZUELA: 582-905-3800 • VIETNAM: 65-216-8333 • WORLDWIDE

HEADQUARTERS: 1-650-960-1300

Shared Virtual Array Administrator - Oracle Help Center

Documents

Transcript of Shared Virtual Array Administrator - Oracle Help Center