Vts With Tsm

IBM TotalStorage Virtual Tape ServerImplementation and Planning (Course Code SS23)

Student Notebook

ERC 2.0

Worldwide Certified MaterialIBM Learning Services

V1.2.2

cover

Student Notebook

The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis withoutany warranty either express or implied. The use of this information or the implementation of any of these techniques is a customerresponsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. Whileeach item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results willresult elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. The originalrepository material for this course has been certified as being Year 2000 compliant.

© Copyright International Business Machines Corporation 2001, 2002. All rights reserved.This document may not be reproduced in whole or in part without the prior written permission of IBM.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictionsset forth in GSA ADP Schedule Contract with IBM Corp.

Trademarks

IBM® is a registered trademark of International Business Machines Corporation.

The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both:

Other company, product, and service names may be trademarks or service marks of others.

AIX AS/400 CICSDB2 DFSMS/MVS DFSMSdfpDFSMSdss DFSMShsm DFSMSrmmESCON IBM IMSMagstar MVS OS/2OS/390 OS/400 PerformRACF RMF RS/6000S/390 System/390 TivoliTotalStorage VSE/ESA

December 2002 Edition

Student NotebookV1.2.2

TOC
Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Course Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Unit 1. VTS Configuratio n and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.1 VTS Configurations and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3VTS Minimum Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4VTS Maximum Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5VTS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Host and Library Manager Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7B18 ESCON High-Performance Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8B18 SCSI Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9B18 VTS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10B18 VTS Channel Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11D12 Features for VTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12B10/B20 VTS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13L!x Features for VTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Unit 2. Implementation and Inst allation Considerations . . . . . . . . . . . . . . . . . . 2-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.1 Implementation and Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . 2-3Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Defining a VTS to S/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5B18 Configuration Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6B18 Configuration Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Using HCD to Define a VTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8LIBPORT ID and Library ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Library ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Missing Interrupt Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11SCSI Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12SCSI Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13SCSI Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14SCSI 3490E Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15SCSI Library Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Addressing Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Emulated 3490E Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18SCSI Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Defining Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Library Manager Setup 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Volume Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

© Copyright IBM Corp. 2001, 2002 Contents iii

Student Notebook

Library Manager Setup 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-23Space Reclamation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24VTS Management Policies (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25VTS Management Policies (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26VTS Management Policies (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27Reclaim Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-28Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29

Unit 3. Software Interact ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3.1 Software Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3System Managed Tape Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4System-Managed Tape Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5SMS Tape Controls (prior to FC4001) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6SMS Tape Controls with FC 4001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7SMS Tape Implementation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8SYS1.PARMLIB Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9Library Identifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10Library Sequence Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11HCD Library Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12ISMF Library Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13Tape Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14SMS Tape Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15Data Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16Storage Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17Tape Storage Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18ACS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19Using Multiple Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20Using VTS Libraries with Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21Library Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22TCDB Display 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23TCDB Display 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24Tape SMS and BTLS Compared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26

Unit 4. Virtual Tape Se rver Partitioning and Sharing . . . . . . . . . . . . . . . . . . . . . 4-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

4.1 Partitioning and Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Challenges for Multisystem Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5Partitioning and Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6Basic Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7Volume Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9Assigning Volumes to Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10Partitioning with System-Managed Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11Partitioning with BTLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-12


iv IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002


TOC
Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Sharing with JES3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Sharing with JES2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Planning for Sharing Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Sharing Controls with SMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Unit 5. Virtual Tape Server Managem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

5.1 Virtual Tape Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Points to Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Information Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Initial State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7After Six Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Statistics After Six Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9What Happened . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Twelve Months Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12What Happened . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13After 15 Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14After 17 Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15After 18 Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Statistics After Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17What Happened After Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18After 20 Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Statistics After 20 Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Active Data Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21What Happened After 20 Months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Unit 6. Virtual Tape Server Operat ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.1 Virtual Tape Server Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Library Manager Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Mode Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Status Pull-Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Operational Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Component Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Queues Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10Database Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Search Database for Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12List Database Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Find Logical Volume Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Find Logical Volume Home LIC 527 LM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15List Stacked Volume Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16


© Copyright IBM Corp. 2001, 2002 Contents v

Student Notebook

List Stacked Volume Contents LIC 527 LM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-17Commands Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19Volume Ranges for Stacked Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20Volume Ranges for Stacked Volumes LIC 527 . . . . . . . . . . . . . . . . . . . . . . . . . . .6-21Inserting Logical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22Inserting Logical Volumes LIC 527 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-23Ejecting Stacked Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-24Ejecting Stacked Volumes LIC 527 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-25Set Category Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-26Set Management Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27Set Management Policies LIC 527 (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-28Set Management Policies LIC 527 (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-29Set Management Policies LIC 527 (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30Inserting Stacked Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31Set Up Stand-alone Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-33Interventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-34Options Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-36

Unit 7. Planning and Exploi ting VTS Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

7.1 Planning and Exploiting VTS Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3VTS Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4VMA Extract Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5VMA Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6Planning for VTS Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7Planning Volume Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8How Many Logical Volumes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9Logical Volumes Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10How Many Stacked Volumes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11Stacked Volumes Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12Choosing Workloads for the VTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13VTS Basic Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14Application Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15Common Types of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16VTS and DFSMShsm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17VTS and DFSMShsm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-18VTS and DFSMShsm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19DFSMShsm Copies and Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-20DFSMShsm ABARS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-21ADSM/Tivoli Storage Manager (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-22ADSM/Tivoli Storage Manager (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23ADSM/Tivoli Storage Manager (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24DFSMSdss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-25DFSMSdss Stand-alone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-26


vi IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002


TOC
DB2® Archive Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27DB2 Image Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28DB2 Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29CICS Journals and IMS Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30IMS Image Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31Batch Tape Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32Tape Mount Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Unit 8. Monitoring and Exploiti ng VTS Performance . . . . . . . . . . . . . . . . . . . . . 8-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

8.1 Monitoring and Exploiting VTS Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Basic Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Configuration Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Performance Accelerator Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7VTS Controller Processor Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Tape Volume Cache Access Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Physical 3590 Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Stacked Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11Internal Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Processes Using Tape Volume Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Tape Volume Cache Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Performance Evaluation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17Overall Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18Channel Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19Cache Miss Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Virtual Drive Mount Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21Mount Time for Specific Mounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Disconnect Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Library Manager Statistics Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24VTS Active Data Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25VTS Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26VTS Mount Hit Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27VTS Physical Device Mount History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28VTS Logical Mounts per Hour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29VTS Active Data Distribution (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30VTS Active Data Distribution (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Performance Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33

Unit 9. Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

9.1 Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3VTS Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4


© Copyright IBM Corp. 2001, 2002 Contents vii

Student Notebook

Active Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5Static Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6Identifying Static Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7Copying Static Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8Correct TMS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9Correct Catalog Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10Tape Copy Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11Tape Copy Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-12VTS Model Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13Model Upgrade Migration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-14MES Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15MES Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16MES Upgrade Outage Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17Parallel Operation with One Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-18Add SMS Tape Library for B18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-19Add SMS Storage Group for B18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-20Parallel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-21Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22Parallel Operations 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-23Parallel Operations 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-24Parallel Operation Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-25Physical Cartridge Movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-26Physical Cartridge Movement Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-27Physical Cartridge Movement Outage Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-28Comparing Migration Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-29Other Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-30Migrating to EHPO Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-31Effects of Adding EHPO Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-32Migrating to 3590E VTS Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-33Migrating to 3590E Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34Migrating to the Performance Accelerator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-35Migrating to the Performance Accelerator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-36Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-37

Unit 10. Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2

10.1 Import/export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3Import/Export Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4Import/Export Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5Import/Export Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6Import/Export Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7Import/Export Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8Import/Export Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-9VTS Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-10VTS Drives for Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11Import/Export Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-12Export Process Flow 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-13


viii IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002


TOC
Export Process Flow 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14Export Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15Export Hints Concerning APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16Export Process Flow 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17Export Process Flow 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18Export Status File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19Library Manager Export Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20Import Process Flow 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21Library Manager Unassigned Volumes Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22Import Process Flow 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23Import List File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24Import List File with APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25Import List File with APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26Import Process Flow 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27Import Process Flow 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28Import Process Flow 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29Library Manager Import Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30Starting Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31Starting Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32Library Manager Cancel Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33OAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34OAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35Display SMS,LIBRARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36Display SMS, LIBRARY with APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37Library Manager Queues Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38Tape Library Management Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39DFSMSrmm Support 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40DFSMSrmm Support 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41DFSMSrmm Volume Details 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42DFSMSrmm Volume Details 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43CA-1 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-44DITTO/ESA Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45Sample JCL for IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
Unit 11. Data Recovery and Prob lem Determination . . . . . . . . . . . . . . . . . . . . . 11-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

11.1 Data Recovery and Problem Determination. . . . . . . . . . . . . . . . . . . . . . . . . . 11-3VTS Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4IBM Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7SNMP Monitoring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8SNMP Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9SNMP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10Enhanced Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11Call Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12


© Copyright IBM Corp. 2001, 2002 Contents ix

Student Notebook

VTS Unique Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-13Read-only Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-14VTS Failure Impact 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-15VTS Failure Impact 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-16VTS Disaster Recovery Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-17VTS Disaster Recovery Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18VTS Disaster Recovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-19Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1


x IBM TotalStorage Virtual Tape Install & Planning © Copyright IBM Corp. 2001, 2002


TMK
Trademarks
The reader should recognize that the following terms, which appear in the content of this training document, are official trademarks of IBM or other companies:

IBM® is a registered trademark of International Business Machines Corporation.

The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both:

Other company, product, and service names may be trademarks or service marks of others.

AIX® AS/400® CICS®DB2® DFSMS/MVS® DFSMSdfp™DFSMSdss™ DFSMShsm™ DFSMSrmm™ESCON® IBM® IMS™Magstar® MVS™ OS/2®OS/390® OS/400®RACF® RMF™ RS/6000®S/390® System/390® Tivoli®TotalStorage™ VSE/ESA™


© Copyright IBM Corp. 2001, 2002 Trademarks xi

Student Notebook


xii IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002


pref
Course Description
IBM TotalStorage Virtual Tape Se rver Implementation and Planning

Duration : 3 days

Purpose

This course will cover the main topics that the students will need when planning for the installation of a VTS, choosing the data to move into a VTS, and setting up procedures for the continued monitoring of a VTS.

The course will follow on from SS22 and will introduce some topics and also cover some topics (such as definition and Tape SMS) in greater depth.

Audience

Information technology personnel who will use the VTS in their jobs to create, store, and retrieve data sets. Jobs would include operators, database administrators, storage administrators, and systems programmers.

Prerequisites

Students should have fundamental storage management skills. These skills could be obtained by attending Introduction to Data Storage Subsystems (SS05/J3700) and Storage Management Fundamentals, (SS06/J3701).

Students should also have a basic understanding of the VTS. This understanding could be obtained by attending Magstar VTS Concepts (SS22).

Objectives

• Enable the students to describe the different configuration options for a Virtual Tape Server and associated 3494 Tape Library.

• Enable the students to define a Virtual Tape Server to host systems

• Enable the students to identify the data that should be moved into a VTS


© Copyright IBM Corp. 2001, 2002 Course Description xiii

Student Notebook

• Enable the students to use the 3494 Library Manager to implement VTS management policies and operate the Virtual Tape Server

• Provide a basic understanding of partitioning and sharing a tape library

• Enable the students to set up the host software to use a Virtual Tape Server effectively

• Enable the students to understand how to perform problem determination for a Virtual Tape Server

Curriculum relationship

• SS05 is a prerequisite




xiv IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002


pref
Agenda
Day 1

Welcome Unit 1 - VTS configurations and options Unit 2 - Implementation and installation considerations Unit 3 - Software interactions Uit 4 - Partitioning and sharing Unit 5 - VTS management

Day 2

Unit 6 - VTS operations Unit 7 - Planning and exploiting VTS capacity Unit 8 - Monitoring and exploiting VTS performance Unit 9 - Data migration

Day 3

Unit 10 - Import/export Unit 11 - Data recovery and problem determination


© Copyright IBM Corp. 2001, 2002 Agenda xv

Student Notebook


xvi IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002

Student NotebookV1.0.1 BKM2MIF

Unit 1. VTS Configuration and Options

What This Unit Is About

This unit covers physical planning information and also looks at the main features that may be chosen.

What You Should Be Able to Do

After completing this unit, you should be able to:

• Understand the physical planning implications of a VTS • Understand the host attachment options

References

GA32-0279 Magstar 3494 Tape Library Introduction and Planning Guide

GA32-0329 Magstar 3590 Tape Subsystem Introduction and Planning Guide


© Copyright IBM Corp. 2001, 2002 Unit 1. VTS Configuration and Options 1-1

Student Notebook

Figure 1-1. Unit Objectives SS232.0

Notes:

Unit Objectives

At the end of this unit, you should be able to:

Understand key physical planning items

Understand the main 3494 and VTS features

Describe the host attachment options


1-2 IBM TotalStorage Virtual Tape Instal l & Planning © Copyright IBM Corp. 2001, 2002


1.1 VTS Configurations and Options



Student Notebook

Figure 1-2. VTS Minimum Configuration SS232.0

Notes:

The IBM TotalStorage Virtual Tape Server is housed in two frames of a 3494: an IBM Model Bxx VTS Frame and IBM D12 Frames. The D12 Frame is located anywhere in the 3494, whereas the Model Bxx VTS frame can be located at a distance of up to 14 m from the D12 Frame. The configuration shown above is a two-frame 3494 with a Model B18 VTS frame, which is the minimum configuration when a VTS is installed. The L1x Frame has the option of having additional non-VTS drives if required; the type and number of drives depend upon the L1x Frame model.

The minimum configuration can be enhanced to a library of up to 16 frames by adding other D1x Frames, IBM 3494-S10 Frames, and the D12 Frame for a second VTS in the same tape library.

3494-D12

3494-B18/B10/B20

LAN

SCSI

3494-L1x

VTS Minimum Configuration




Figure 1-3. VTS Maximum Configuration SS232.0

Notes:

The VTS is available in different configurations in terms of the number and type of channels, host system attachments, sizes of TVC, and the number of physical Magstar tape drives that are dedicated to the VTS. The diagram above shows the maximum configurations for a VTS. Maximum configuration is dependent on the VTS model. For example, up to six 3590 tape drives are supported on Model B10 VTS.

VTS Maximum configuration

Base LIC

Tape

Daemon

AIX

data compression

feature

pSeries 660 Model 6H1

PCI

SSA

Adapter

I/O Bus

PCI + 864 GB216/432 GB

ESCON / SCSI

SCSI

Adapter

hdisk

6+P

SSAhdisk

6+P

hdisk

6+P

hdisk

6+PSSA

hdisk

6+P

hdisk

6+P

hdisk

6+P

hdisk

6+PSSA SSA

ESCON ESCON ESCON ESCON ESCON ESCON ESCON ESCON

+ 432 GB

PCI

SCSI

3590

3590

3590

3590

3590

3590

SCSI

SCSI

3590

3590

3590

3590

3590

3590

SCSI

(1)Only 6 drives are configurable to a Model B10 VTS

(1)



Student Notebook

Figure 1-4. VTS Configurations SS232.0

Notes:

This table compares the possible configuration matrix between each VTS model with detailed configuration options and considerations.

VTS Configurations

*1 *1 *1

*1

*1

B18 B18 VTS

+EHPO B18 VTS

+ PAFB10 B20

Tape Volume Cache (GB) 72 - 288 216 - 864 648 - 5184 648 - 1296 2592 - 5184

Virtual Drives 32 32 / 64 64 / 128 64 128 / 256

Physical Tape Drives 3 - 6 3 - 6 4 - 12 4 - 6 6 - 12

Virtual Volumes 250,000 250,000 250,000 250,000 250,000

ESCON Only Attachments 2 2 / 4 4 / 8 2 / 4 8 / 16

SCSI Only Attachments No 2 / 4 2 / 4 2 / 4 / 8 8

ESCON / SCSI Channels No up to 2 / 2 up to 4 / 4 up to 4 / 8 up to 8 / 8

FICON Channels No No No up to 4 up to 8

FICON / ESCON Channels No No No 2 / 4 4 / 4

Logical Volume Size (GB) .4 / .8 1.2 / 2.4 1.2 / 2.4 1.2 / 2.4 1.2 / 2.4

Open System Support No Yes Yes Yes Yes

Import / Export No Yes Yes Yes Yes

*1 assumes a data compression factor of 3:1

*2 requires OS/390 or Z/OS

*1 *1 *1

*2*2 *2

*2




Figure 1-5. Host and Library Manager Attachment SS232.0

Notes:

Detailed physical planning information is in the Magstar 3494 Introduction and Planning Guide, GA32-0279. All frames except storage frames need front and rear service clearance. The storage frame does not need clearance at the rear.

ESCON host attachmentTwo ESCON channels (two or four with EHPO)Distance up to 43 km

Library Manager attachmentAttachment ConcentratorD12 FrameB18 Frame

D12-B18 frame connectionAll drives attached to both SCSI buses

Up to 14 m (46 ft) between B18 and D12

Host and Library Manager Attachment

��

��

��

��

��

��

��

� ��

!�"# �

��

!��#"�

� ��

��$��

��""��

�%�&

��

�%�&

��

�%�&

��

�%�&

��

�%�&

��

��'�

�%�&

��

��(�)



Student Notebook

Figure 1-6. B18 ESCON High-Performance Option SS232.0

Notes:

ESCON attachmentsCompression on ESCON AttachmentTwo Enhanced ESCON Channels replaces standard channelsTwo more Optional Enhanced ESCON Channels

Higher Subsystem Capacities (using compression)72, 144, 216, 288 GB uncompressed cache capacity Up to 216, 432, 648, 864 GB cache capacity (3:1 ratio)Up to 64 Virtual Drives per VTS requires 144 GB TVC requires EHPOUp to 250,000 Logical Volumes per VTS SubsystemUp to 500,000 Logical Volumes per 3494

B18 ESCON High-Performance Option




Figure 1-7. B18 SCSI Attachment SS232.0

Notes:

B18 SCSI Attachment

Optional feature #3422Still need ESCON attachment either #3200 or #3400

Feature adds SCSI cardTwo portsTwo connectorsTwo terminators

Microcode prerequisitesVTS 2.17.8.0 or higherLM 523.01 or higher



Student Notebook

Figure 1-8. B18 VTS Features SS232.0

Notes:

These are the main features that may be installed on a B18.

You may choose different host attachment options. The attachment features should match so that you get the right device drivers for SCSI attachment.

B18 VTS Features

Min. Qty.

Max. Qty.

Description

2710/11/12 0 1 Remote Support and Call Home

3400 0 1 Extended High Performance Option

3412 1 2 Extended Performance ESCON channels

3422 0 2 SCSI Host Attachment

3703 1 1 72 GB Disk Storage Capacity for TVC

3704 0 1 144/216 GB Disk Storage Capacity for TVC

3705 0 4 288/432 GB Disk Storage Capacity for TVC

4000 0 1 Advanced Function

5001-5004 0 2 SCSI cables

5234 1 1 18 m SCSI cables

5236 0 1 Performance Accelerator

9106 0 1 RS/6000 attachment

9109 0 1 ES/9000 attachment

9201 0 1 VTS Open Systems Device Drivers

9986 0 1 6 ft. Chicago Power cord

* No longer available for installation




Figure 1-9. B18 VTS Channel Combinations SS232.0

Notes:

Note that feature #3200 comprises both microcode and ESCON cards. Feature #3400 is microcode only so ESCON cards must be ordered in addition.

B18 VTS Channel Combinations

#3302 #3412 #3422

#3200

1

1

1

2

#3400 1

2

1 1

1 2

#3422 is SCSI attachment



Student Notebook

Figure 1-10. D12 Features for VTS SS232.0

Notes:

The SCSI extender feature is required for VTS attachment.

D12 Features for VTS

Min. Qty.

Max. Qty.

Description

5233 1 1 SCSI Extender

9010 1 1 VTS Attached Model D12




Figure 1-11. B10/B20 VTS Features SS232.0

Notes:

These Feature Codes can be installed on the Model B10 VTS and Model B20 VTS frame and determine the configuration of the VTS. The Feature Codes are used to specify the Remote Support Facility configuration, the size of the Tape Volume Cache (TVC), the type and number of channel attachments to be shipped with the Model B10 VTS or Model B20 VTS, and other options. The table above summarizes the Feature Codes required on the Model B10 VTS and Model B20 VTS.

Min. Qty.

Max. Qty.

Description

2710/11/12 0 1 Remote Support and Call Home

3412 0 4 Extended Performance ESCON channels

3422 0 4 SCSI Host Attachment

4000 0 1 Advanced Function

5001-5004 0 4 SCSI cables

5235 1 2 20 m SCSI cables

5264 0 2 64 additional virtual drives

9106 0 1 RS/6000 attachment (pseries)

9109 0 1 ES/9000 attachment (zseries)

9201 0 99 VTS Open Systems Device Drivers

9210 0 1 HP-UX attachment

9211 0 1 Sun attachment

9212 0 1 Windows attachment

9986 0 1 6 ft. Chicago Power cord

B10/B20 VTS Features



Student Notebook

Figure 1-12. L!x Features for VTS SS232.0

Notes:

The features shown in bold are required when you want to have a VTS in a library.

L1x Features for VTS

Min. Qty.

Max. Qty.

Description

2710 0 1 Remote Support Facility

2711 0 1 Remote Support Switch

2712 0 1 Remote Support Attachment

5210/5230 0 1 10/30 Cartridge Convenience I/O Station

5214 1 1 Second LM HDD (replaced by mirrored disk 11/99)

5215 0 1 Dual Gripper

5226 0 1 Remote Library Manager Console

5232 1 1 Attachment Concentrator

9020 1 1 3494-B18 VTS Attachment - forces 5045 (Enhanced LM)




Figure 1-13. Unit Summary SS232.0

Notes:

Unit Summary

At the end of this unit, you should understand:

Physical planningReview floor loadings for VTS frames

Attachment options



Student Notebook




Unit 2. Implementation and Installation Considerations


This unit discusses the initial work that needs to be done to attach a VTS to a host system. Both System/390 ESCON attachment and AIX® SCSI attachment are discussed. The unit also covers the tasks that a student will need to perform at the 3494 Library Manager to complete the installation.



• Define a VTS to OS/390 • Define a VTS to AIX • Set up VTS management policies using the 3494 Library Manager

References

SC26-3051 DFSMS/MVS OAM Planning, Installation and Storage Administration Guide for Tape Libraries

GC35-0154 IBM SCSI Tape Drive, Medium Changer and Library Device Drivers Installation and User's Guide


© Copyright IBM Corp. 2001, 2002 Unit 2. Implementation and In stallation Considerations 2-1

Student Notebook


Notes:

Unit Objectives

At the end of this unit, you should understand how to:

Plan for the main installation tasks

Define a VTS to S/390 using HCD or IOCP

Define a VTS to a SCSI host

Use the library manager to set up a VTS




2.1 Implementation and In stallation Considerations



Student Notebook

Figure 2-2. Installation Tasks SS232.0

Notes:

Installation Tasks

Physical installationPhysical planningHardware installation

Engineer's tasksTeachpart of installation: location of drives Inventorylocation of cells

Definition of VTSDefine device addressesDefine library to hostSet missing interrupt thresholdDefine volume rangesSet up library manager




Figure 2-3. Defining a VTS to S/390 SS232.0

Notes:

Defining a VTS to S/390

Define device addresses to S/390Define as 3490s

IOCPSupported for BTLS, VM, VM/VSE

HCDRequired for system managed tapeOtherwise optionalLIBPORT id



Student Notebook

Figure 2-4. B18 Configuration Example 1 SS232.0

Notes:

This example is for a VTS with two ESCON channels which are not attached using an ESCON Director.

We have 64 virtual drive addresses. These are defined as four virtual 3490E subsystems, each with 16 addresses. For each 3490E subsystem, there is a control unit definition and the definition of 16 device addresses.

The CUADD parameter is used for each of the logical control units.

B18 Configuration Example 1

Two channels, no ESCON Director

HCD Definitions

4 Control Unit, 4x16 3490 devicesLIBRARY = YESLIBID = 12345LIBPORTID = 01,02,03,04

��

ES

CO

N

ES

CO

N

Single Host

B18

40 50

440 443

441 442

CUADD=3CUADD=0

CUADD=1 CUADD=2

A40 - A4F A50 - A5F��

��

A60 - A6F A70 - A7F

CNTLUNIT CUNUMBER=440,PATH=(40,50), X UNIT=3490,UNITADD=((00,16)),CUADD=0

IODEVICE ADDRESS=(A40,16),UNIT=3490, X CUNUMBER=(440),UNITADD=00










Figure 2-5. B18 Configuration Example 2 SS232.0

Notes:

This example adds two ESCON channels to the VTS for a total of four. We also use an ESCON Director.

This means that we must define the additional paths and we must also define the link addresses for the ESCON Director ports.

B18 / B20 Configuration Example 2

HCD Definitions

4 Control Unit, 4x16 3490 devicesLIBRARY = YESLIBID = 12345LIBPORTID = 01,02,03,04

Four channels, ESCON Director

D6D7

ESCD

Single Host40 50

��

B18

440 443

441 442

CUADD=3CUADD=0

CUADD=1 CUADD=2

A40 - A4F A50 - A5F��A60 - A6F A70 - A7F

60 70

D8D9

CNTLUNIT CUNUMBER=440,PATH=(40,50,60,70), X UNIT=3490,UNITADD=((00,16)),LINK=(D6,D7,D8,D9),CUADD=0










Student Notebook

Figure 2-6. Using HCD to Define a VTS SS232.0

Notes:

It is better to use HCD rather than IOCP as you can avoid IODF reactivation if you have the correct service applied.

If you use system-managed tape, you must use HCD.

Using HCD to Define a VTS

Required for System Managed Tape

Optional with Basic Tape Library Support

Use of LIBPORT ID and Library IDAllows library to be offline at IPLOtherwise IODF reactivation neededFor any 3494, not just VTS

Define two or four control unitsEach with 16 drives

Specify LIBRARY = YES

Leave link address blank if no ESCON directors

LIBPORT APARs

OW25291, OW25292,

OW25293, OW27801,

OW29692




Figure 2-7. LIBPORT ID and Library ID SS232.0

Notes:

The library ID is usually taken from the serial number of the library frame or the VTS.

The Libport ID reflects the order in which the tape control units are connected to the library manager. In the diagram, we have:

L10 Library ID 12345, libport ID 01.

D12 None as the drives are attached to the first VTS.

D12 None as the drives are attached to the second VTS.

D14 There are native drives in this frame. We use the library frame library ID and libport ID 02.

D14 There are native drives in this frame. We use the library frame library ID and libport ID 03.

B18 We use the library ID of the first VTS, 60123, and libport IDs 01 to 04 (01 to 02 if we only have 32 virtual drives) to describe the logical control units.

B18 We use the library ID of the second VTS, 60124, and libport IDs 01 to 04.

LIBPORT ID and Library ID

3494

B18

3494

B18

SCSI

3494

L10

3494

D12 3494

D14

3494

D12

3494

D14

LAN

LANLIBRARY-ID=60124

LIBPORT-ID=01-04

LIBRARY-ID=60123

LIBPORT-ID=01-04

LIBRARY-ID=12345

LIBPORT-ID=01

LIBRARY-ID=12345

LIBPORT-ID=02

LIBRARY-ID=12345

LIBPORT-ID=03



Student Notebook

Figure 2-8. Library ID SS232.0

Notes:

Library ID

Used in Tape SMS Library definitionFive charactersAssigned by Customer Engineer at installation timeUsually last five digits of serial number

Find On Library Manager Operational Status panelUsing DEVSERV QTAPE,xxx,1,RDC

Up to three Library IDsOne for base 3494One for first VTSOne for second VTS (if installed)




Figure 2-9. Missing Interrupt Handler SS232.0

Notes:

You do not need to set MIH values for native 3590s. The control unit (3590-A00, A50 or A60) returns recommended MIH values when the Read Device Characteristics channel command is issued. This is done at IPL or vary time.

The communication of recommended MIH interval is not done for 3490E drives, whether real or virtual.

Missing Interrupt Handler

MVS component

Used to detect hardware problemsAction taken if no interrupt returned to signal completion

VTS recommendation45 minutesAllows VTS internal recovery to complete

Set in SYS1.PARMLIB(IECIOSxx)

MIH=(0A40-0A5F),TIME=45:00



Student Notebook

Figure 2-10. SCSI Attachment SS232.0

Notes:

A VTS may have SCSI host attachments but these are in addition to ESCON attachments.

SCSI addresses consist of two parts: a SCSI ID and a logical unit number (LUN) for that ID. VTS virtual drives emulate 3490Es exactly for addressing so the same scheme is used. There is one SCSI id for two drives which are distinguished by using a LUN of 0 or 1.

SCSI Attachment

Still need ESCON channels

One or two SCSI cards optionalUp to 16 SCSI addresses per cardCompression in adapter card

SCSI addresses set at installation timeOne SCSI ID for two drivesLUNs 0 and 1 used

SCSI reserve/release protocols supportedStill recommend dedicated addresses




Figure 2-11. SCSI Attachment SS232.0

Notes:

With ESCON, commands and data both flow down the channel.

With SCSI, drive commands and data flow down the SCSI bus. However, library commands use a separate path.

ESCON

Host

LM

ESCON Adapter

SCSI

Adapter

Library Commands LAN or RS232

Drive Commands/Data

ESCON All Commands/Data

SCSI Bus

B18

Internal LAN

SCSI Attachment

SCSI

Host



Student Notebook

Figure 2-12. SCSI Requirements SS232.0

Notes:

The SCSI adapters differ depending on the RS/6000 in which they are installed and whether they are SCSI-2 or UltraSCSI.

2412 Enhanced SCSI-2 fast/wide differential

6209 PCI SCSI-2 fast/wide differential

6207 PCI UltraSCSI differential

SCSI Requirements

RS/6000 and RS/6000 SP RS/6000 SCSI adapter feature codes 2412, 6209, or 6207AIX 3494 and 3490E device driver B18 feature code #9201AIX 4.2.1 and higher

SCSI attachmentsSCSI-2 Fast/Wide Differential (20 MB/s)Ultra Wide Differential (40 MB/s)(2) 0.8 mm SCSI connectors

External termination permits daisy-chaining

Note that the 3490E device driver is used




Figure 2-13. SCSI 3490E Device Driver SS232.0

Notes:

SCSI 3490E Device Driver

Install 3490E device driver (Atape driver)Need root authority to installUse smit or the installp utility

Configure device driverUse cfgmgr or mkdev command

Defines 3490E called rmt4 at SCSI ID 4, LUN 0

installp /dev/rfd0 Atape.driver

mkdev -s scsi -c tape -t 3490 -p scsi1 -w 4,0 -l rmt4 -a block_size=0



Student Notebook

Figure 2-14. SCSI Library Device Driver SS232.0

Notes:

SCSI Library Device Driver

PreparationEnsure RS-232 or LAN attachment to library manager is connected

InstallationInstall library device driverConfigure RS-232 port (if used) smit ttyConfigure 3490sDefine 3494 to the library control daemon edit /etc/ibmatl.confConfigure the library manager control point using smitLoad daemon using cfgmgr




Figure 2-15. Addressing Logical Drives SS232.0

Notes:

Internally, drives are given addresses which reflect the System/390 addresses. The SCSI adapters see drives depending on options set at installation time.

The default host addressing is for eight virtual drives, starting at SCSI ID 8, for each SCSI bus interface.

Addressing Logical Drives

Devices

Control Unit 0

Devices

Control Unit 1

SCSI Adapter 0

SCSI Bus 0

SCSI Bus 1

Devices

Control Unit 2

Devices

Control Unit 3

SCSI Adapter 1

SCSI Bus 2

SCSI Bus 3

ESCON Adapter 0

ESCON

ESCON Adapter 1

ESCON

0

15

0

15

0

15

0

15

0 to 16contiguousdevices *






Student Notebook

Figure 2-16. Emulated 3490E Addresses SS232.0

Notes:

The diagram shows how SCSI addresses real 3490E drives. The VTS emulates this exactly for virtual drives.

Control Unit

Drive 2Drive 1

(LUN 0) (LUN 1)

SCSI Interface 0 SCSI Interface 1

(Target ID:

0..15)

(Target ID:

0..15)

Emulated 3490E Addresses

VTS emulates 3490-C2A subsystems




Figure 2-17. SCSI Example SS232.0

Notes:

This shows a configuration using the defaults. There are eight virtual drives and they occupy SCSI ids 8, 9, 10 and 11. Each SCSI id has two LUNs.

SCSI Example

Control Unit

Drive 2

(LUN 0) (LUN 1)

Control Unit

Drive 2Drive 1

(LUN 0) (LUN 1)

Control Unit

Drive 2Drive 1

(LUN 0) (LUN 1)

Control Unit

Drive 2Drive 1

(LUN 0) (LUN 1)

Drive 1

Target ID: 8 Target ID: 9 Target ID: 10 Target ID: 11

RS/6000 HOST

SCSI Host Adapter

��"�*��

(Feature Code 5001, 5002, or 5003)

4.5,10, or 20 Meter SCSI cableTri-Link adapter

T

Terminator



Student Notebook

Figure 2-18. Defining Volumes SS232.0

Notes:

When setting up a VTS, you need to ensure that you define volumes correctly.

You must define your virtual volume range to your tape library management system. You may wish to define all the volumes that could possibly be used even though you will not define them to the VTS at first. You should also define the volume serial numbers of your stacked volume for additional protection.

You must also define your stacked volumes to the VTS before you insert them.

Defining Volumes

1000 volumes per 1 MB in the

CDS

DFSMSrmm

example

Define to hostVirtual volumes in Tape Management System control data set sizeStacked volumes for protection

Define to VTSStacked volumesDefine before inserting cartridgesStacked volumes owned by VTSHost not told of insert

Distinct volume serial ranges recommendedStacked volumesNative volumesLogical volumesCleaning and CE volumes




Figure 2-19. Library Manager Setup 1 SS232.0

Notes:

Library Manager Setup 1

Set VOLSER range for 3590 stacked volumesOwned by VTS - not known to hostIdentify these VOLSERs to the Library Manager before issuing inventory command to avoid host notification

Set FAST READY for VTS scratch categories

Set other VTS specific parametersFC4001 Outboard Policy Management ConstructsReclamation threshold and scheduleCleaning scheduleFree storage threshold

Perform inventory

Insert/define virtual volume range

Do not insert every logical volume

that you have defined!



Student Notebook

Figure 2-20. Volume Categories SS232.0

Notes:

The library manager assigns volumes to categories according to how they will be used. There are some additional categories for the VTS shown in bold.

Volume Categories

Category Description

0001 Media 1 Scratch Cartridge - Single Length - CST

0002 Media 2 Scratch Cartridge 3490 - Double Length - ECCST

000F Private (in use) Data Cartridge

FF00 Insert Volume

FF01 Stacked Volume Insert Category

FF03 Stacked Volume Scratch Category (not used after LM LIC level 527)

FF04 Stacked Volume Private Category (includes both scratch and private after LM LIC level 527)

FF05 Stacked Volume Disaster Recovery Category

FF06 Stacked Volume Disaster Recovery Category

FF12 Export Pending Category

FF13 Exported Category

FF14 Import Category

FF15 Import Pending Category

FF16 Unassigned Category

FF17 Export Hold Category




Figure 2-21. Library Manager Setup 2 SS232.0

Notes:

Library Manager Setup 2

Set VOLSER range for 3590 stacked volumesAssociates the VOLSERs with a VTS



Student Notebook

Figure 2-22. Space Reclamation SS232.0

Notes:

Space Reclamation

Stacked Magstar Cartridges Automatic processSelect tape with high amount of unusable space, based on specified threshold percentageMove all logical volumes to other stacked volumesReturn reclaimed volume to stacked scratch poolTape-to-tape process

Inhibit space reclamationThrough the Library Manager console During certain periods of time




Figure 2-23. VTS Management Policies (1 of 3) SS232.0

Notes:

This library manager panel is used to set up policies for the internal storage management functions in the VTS.

You can set up:

1. The inhibit reclamation schedule

2. The reclamation threshold

3. The free space warning threshold

VTS Management Policies (1 of 3)



Student Notebook


Notes:






Notes:


Used to limit access by web users to certain actions



Student Notebook

Figure 2-26. Reclaim Threshold SS232.0

Notes:

Reclaim Threshold

Library Manager panel System Management pulldown Set VTS Management PoliciesDynamically changeable

Reclamation ThresholdPercentage of active data before cartridge is eligible for reclamation can be changedDefault is 10% active data

Recommendations:Start off with 10% (default) Increase slowly by 5%Monitor with the LM Active Data Distribution panelDo not go above 30-40%





Notes:

Unit Summary


Define VTS device addresses using HCD or IOCPHCD with LIBPORT id preferred

Define both library and drives for SCSI attachment

Use the library manager to install a VTSSet volume serial ranges for stacked volumesSet fast ready for scratch categoriesSet VTS management policiesInsert logical volumes

Define new volumesTo host tape management system



Student Notebook




Unit 3. Software Interactions


This unit covers the changes that the students will need to make to support a VTS. Nearly all the tasks are relevant to the installation of a 3494 with native drives, too.

The two areas covered are the setup of system-managed tape and of OAM support for tape libraries.



• Understand how the different components of system-managed tape are related

• Set up OAM for tape library support • Define appropriate SMS constructs for tape • Understand the differences between Tape SMS and BTLS

References

SC26-3123 DFSMS/MVS Implementing System Managed Storage

SC26-4920 DFSMS/MVS DFSMSdfp Storage Administration Reference

SC26-4931 DFSMS/MVS DFSMSrmm Guide and Reference

SC26-3051 DFSMS/MVS OAM Planning, Installation and Storage Administration Guide for Tape Libraries


© Copyright IBM Corp. 2001, 2002 Un it 3. Software Interactions 3-1

Student Notebook


Notes:

Unit Objectives

At the end of this unit you should be able to:

Describe the system-managed tape components

Understand the functions provided by system-managed tape

Describe how system-managed tape influences tape allocations

Set up system-managed tape




3.1 Software Interactions



Student Notebook

Figure 3-2. System Managed Tape Overview SS232.0

Notes:

Capabilities:ACS routines determine media and libraryAutomatic volume insert processingExternal/internal label verificationAutomatic labeling at openISMF interfaceTMS interface through installation-wide exits Operator MVS LIBRARY and SMS commandsICL/ACL awareness

Limitations:Single scratch pool per media typeNon-library devices cannot be system-managed

System-Managed Tape Overview




Figure 3-3. System-Managed Tape Components SS232.0

Notes:

The diagram shows the host and library components of system-managed tape, how they communicate, and where they store information.

The host part of system-managed tape uses the SMS address space to define the system-managed libraries and the management policies. The library is controlled by Library Control Services (LCS) which runs in the OAM address space. Communication with tape library management systems is enabled by OAM exits which are taken when an event occurs that may change the tape library management system's information. The exits notify the tape library management system when:

• A cartridge should be in a library but is not (VNL for Volume Not in Library)

• A cartridge is entered into the library or ejected from it

• The status of a cartridge is changed

CBRXLCS provides a programming interface to call LCS functions.

The main library components of system-managed tape are the library manager and the managed drives and storage locations.

IBM 3494/3495

Tape

Drives

Library

Manager Library

Manager

Database

Volume

Location

ACDS

TCDB

SMS

Address

Space

OAM

Address

Space

LCS

MVS/ESA

CDS

ISMF

CBRUXVNL

CBRUXCUA

CBRUXEJC

CBRUXENT

Tape

Mgt

System

CBRXLCS

Virtual

Tape

Drives

IBM 3494 Tape Library Virtual Tape Server

System-Managed Tape Components



Student Notebook

Figure 3-4. SMS Tape Controls (prior to FC4001) SS232.0

Notes:

The basis of system-managed storage is that storage use should be defined and managed according to policies which separate the logical and physical views of the storage.

The data class, storage class, and management class define the logical view of the services required. The storage group defines the physical view of specific libraries.

SMS Tape Controls (prior to FC4001)

�

�

��

� ��

��

��

��

��

��

��

��

��

SG2SG1

��

CDSDC SC MC Exits

��!��"��

#��$�




Figure 3-5. SMS Tape Controls with FC 4001 SS232.0

Notes:

SMS Tape Controls with FC 4001

�

�

��

� ��

��

��

��

��

��

��

��

��%

��&��

��'��

SG2

SG3SG1

��

CDSDC SC MC Exits

��!��%

�(��'��%

��

��%�

��"��

#��$�%

��!��

)��'��%

Stacked Media pool 1

Stacked Media pool 2 3494 Native

Media



Student Notebook

Figure 3-6. SMS Tape Implementation Tasks SS232.0

Notes:

This is a checklist of tasks that you need to complete to implement system-managed tape.

SMS Tape Implementation Tasks

Use HCD panels to define the Virtual Drives as 3490E devices associated with the 3494 Library

Update PARMLIB

Update PROCLIB

Define TCDB VOLCAT catalogs

Use ISMF to define:Tape Management classesTape LibrariesTape Storage Groups Tape Storage ClassesTape Data Classes

Write, test, and validate ACS routines

Activate SMS configuration

Activate HCD configuration




Figure 3-7. SYS1.PARMLIB Changes SS232.0

Notes:

The specific changes to each member are described in SC26-3051, OAM Planning, Installation and Storage Administration for Tape Libraries.

SYS1.PARMLIB Changes

Update system datasets as for 3494 library

SCHEDxx PPT (OAM)IGDSMSxx (OAM)IEFSSNxx (OAM)DEVSUPxx (partitioning scratch pools for multiple

systems)IECIOSxx (MIH entry of 45 minutes)COMMNDxx (vary library and devices online/offline)GRSCNFxx optional (GRS serializes cartridge entry)LOADxx optional (TCDB hlq)COFVLFxx optional (use VLF for TCDB)ALLOCxx set timer for mount pending message



Student Notebook

Figure 3-8. Library Identifications SS232.0

Notes:

Library ID is assigned at HW installation timeLibrary drives are defined to MVS using HCD with a parameter LIBRARY=YES

Library ID and Libport ID are optionally defined in HCD with drive definitions

Avoids need to have library online at MVS startup time (OW25291)

Library name related to the specified ID is defined to DFSMS via ISMF

Storage Group related to one or more libraries is defined to DFSMS via ISMF

Output allocation targets Storage Group based on ACS routine assignments

Library Identifications




Figure 3-9. Library Sequence Number SS232.0

Notes:

The library ID is shown on the library manager operational status panel as the library sequence number. Here we have a panel from a 3494 with two VTSs and hence three library IDs.

Library Sequence Number



Student Notebook

Figure 3-10. HCD Library Definition SS232.0

Notes:

This represents the HCD panel where you define a tape library. The items specifically for a library are shown in bold.

HCD Library Definition

Command ===> __________________________________________ Scroll ===> PAGE Specify or revise the values below. Configuration ID . : AB MVS operating system Device number . . : 0A40 Number of devices :16 Device type . . . : 3490 Parameter/ Value P Req. Description Feature OFFLINE Yes Device considered online or offline at IPL DYNAMIC Yes Device supports dynamic configuration LOCANY Yes UCB can reside in 31 bit storage LIBRARY Yes Device supports auto tape library AUTOSWITCH Yes Device is automatically switchable LIBRARY-ID 10023 5 digit library serial number LIBPORT-ID 02 2 digit library string ID (port number) ALTCTRL No Separate physical control unit path SHARABLE No Device is Sharable between systems COMPACT Yes Compaction




Figure 3-11. ISMF Library Definition SS232.0

Notes:

This is the ISMF panel where we define a tape library.

Each library is given a name which is used in the SMS storage group definition.

You may set defaults for several attributes at a library level.

ISMF Library Definition

------------------------------------------------------------------------------ TAPE LIBRARY DEFINE Page 1 of 2 Command ===> SCDS Name . : SYS1.SCDSRLS Library Name : LIBVTS To Define Library, Specify: Description ==> ==> Library ID . . . . . . . . . . . 10023 (00001 to FFFFF) Console Name . . . . . . . . . . Entry Default Data Class . . . . DC3490 Entry Default Use Attribute . . SCRATCH (P=PRIVATE or S=SCRATCH) Eject Default . . . . . . . . . PURGE (P=PURGE or K=KEEP) Media Type: Scratch Threshold Media1 . . . . 200 Media3 . . . . 0 (0 to 999999) Media2 . . . . 300 Media4 . . . . 0 (0 to 999999) Use ENTER to Perform Verification; Use DOWN Command to View next Panel;



Student Notebook

Figure 3-12. Tape Configuration Database SS232.0

Notes:

Two facility class profiles are used to limit the ability to perform configuration changes. A storage administrator should be given read authority to both. The first profile allows the administrator to activate a new SMS configuration. This results in a new copy of the SMS ACDS. The second profile controls library changes which are reflected in changes to the TCDB.

A TCDB consists of one or more ICF catalogs which are defined with the VOLCAT parameter. You can split the TCDB across several catalogs by defining VOLCATs for ranges of volume serial numbers.

Tape Configuration Database

Define security profilesSTGADMIN.IGD.ACTIVATE.CONFIGURATIONSTGADMIN.IGG.LIBRARY

Create/update TCDB definitionsIDCAMS DEFINE hlq.VOLCAT.VGENERALhlq.VOLCAT.Vx (x is first character of volser range)user catalogs for up to 150,000 VTS volumes to improve performance

hlq equal to SYS1, Otherwise change LOADxx member of PARMLIB

IMPORT CONNECT to sharing systemsSpecify VOLCAT statement in IDCAMS command




Figure 3-13. SMS Tape Constructs SS232.0

Notes:

SMS Tape Constructs

Define or update DATACLAS

Define or update STORCLAS

Define or update MGMTCLAS

Define or update STORGROUPOne to one, one to many, or many to one

Write ACS routinesAssign classes for SMS managed tape

Validate and test SMS definitions



Student Notebook

Figure 3-14. Data Class SS232.0

Notes:

This is the ISMF data class application showing the section where you define the tape attributes for a storage class. The tape attributes are shown in bold case.

Data Class

------------------------------------------------------------------------------ DATA CLASS DEFINE Page 2 of 3 Command ===> SCDS Name . . . : SYS1.SCDSRLS Data Class Name : DC3490 To DEFINE Data Class, Specify: Retpd or Expdt . . . . . . (0 to 9999, YYYY/MM/DD or blank) Volume Count . . . . . . . (1 to 59 or blank) Add'l Volume Amount . . . (P=Primary, S=Secondary or blank) Imbed . . . . . . . . . . . (Y, N or blank) Replicate . . . . . . . . . (Y, N or blank) CIsize Data . . . . . . . . (1 to 32768 or blank) % Freespace CI . . . . . . (0 to 100 or blank) CA . . . . . . (0 to 100 or blank) Shareoptions Xregion . . . (1 to 4 or blank) Xsystem . . . (3, 4 or blank) Compaction . . . . . . . . Y (Y, N or blank) Media Interchange Media Type . . . . . . . 2 (1, 2, 3, 4 or blank) Recording Technology . . 36 (18, 36, 128, 256 or blank) Use ENTER to Perform Verification; Use UP/DOWN Command to View other Panels;




Figure 3-15. Storage Class SS232.0

Notes:

This is the ISMF storage class application. There are no storage class attributes that describe tape service levels so it is not important what you enter. The only choice by Tape SMS is whether a tape allocation has a storage class or not.

Storage Class

------------------------------------------------------------------------------ STORAGE CLASS DEFINE Page 1 of 2 Command ===> SCDS Name . . . . . : SYS1.SCDSRLS Storage Class Name : SCVTS1 To DEFINE Storage Class, Specify: Description ==> ==> Performance Objectives Direct Millisecond Response . . . . (1 to 999 or blank) Direct Bias . . . . . . . . . . . . (R, W or blank) Sequential Millisecond Response . . (1 to 999 or blank) Sequential Bias . . . . . . . . . . (R, W or blank) Initial Access Response Seconds . . (0 to 9999 or blank) Sustained Data Rate (MB/sec) . . . (0 to 999 or blank) Availability . . . . . . . . . . . . N (C, P ,S or N) Accessibility . . . . . . . . . . . N (C, P ,S or N) Guaranteed Space . . . . . . . . . . N (Y or N) Guaranteed Synchronous Write . . . . N (Y or N) Use ENTER to Perform Verification; Use DOWN Command to View next Page; . . . . . . . . . . . . . . . . . . . . . . . . . .



Student Notebook

Figure 3-16. Tape Storage Group SS232.0

Notes:

This is the ISMF storage group application.

You define a tape storage group by name and enter the libraries that may be used to satisfy an allocation request for this storage group. You may also define how the storage group is connected to different systems by choosing to define the SMS storage group status.

Tape Storage Group

------------------------------------------------------------------------------ TAPE STORAGE GROUP DEFINE Command ===> SCDS Name . . . . . : SYS1.SCDSRLS Storage Group Name : SGTAPE To DEFINE Storage Group, Specify: Description ==> Local VTS ==> Library Names (1 to 8 characters each): ===> LIBVTS ===> ===> ===> ===> ===> ===> ===> DEFINE SMS Storage Group Status . .... N (Y or N) Use ENTER to Perform Verification and Selection; . . . . . . . . . . . . . . . . . . . . . . . . . .




Figure 3-17. ACS Example SS232.0

Notes:

This ACS routine fragment shows the main elements of a routine using the storage group ACS routine as an example.

Conditions that we want to check on are described in filter lists, shown here as filters on data set names.

The logic that checks the data set names and assigns storage groups is shown within the SELECT statement.

ACS Example

FILTLIST hsmlocal INCLUDE(**.HMIGTAPE.DATASET, **.BACKTAPE.DATASET, **.DMP.LOCAL.V*.D*.T*)FILTLIST hsmremot INCLUDE(**.DMP.REMOTE.V*.D*.T*, **.COPY.BACKTAPE.**, **.COPY.MIGTAPE.**)

SELECT WHEN (&DSN = hsmlocal) DO SET &storgrp = 'LOCALVTS' EXIT END WHEN (&DSN = hsmremot) DO SET &storgrp = 'REMOTVTS' EXIT END

END



Student Notebook

Figure 3-18. Using Multiple Libraries SS232.0

Notes:

The relationship between storage groups and libraries is set on the storage group definition ISMF panel.

To allow a storage group to span more than one library you simply define more than one library name on the panel.

A library will contain more than one storage group when it is named in more than one storage group definition.

Using Multiple Libraries

Storage Group and library relationship

A storage group can span up to eight librariesA library can contain multiple storage groups

SG1 SG2

SG4

SG3

Library 2 Library 3Library 1

Library 1

Library 2VTS




Figure 3-19. Using VTS Libraries with Pooling SS232.0

Notes:

Using VTS Libraries with Pooling

Storage Group and VTS library relationship

A VTS with pooling can have 256 storage groups. A VTS can only have 32 stacked media pools.

��

��

VTS 1

VTS1 ��

��

��

POOL 3

POOL 10

POOL 31

STG1 STG21

STGJCART1

STGJCART2

STGKCART1

POOL 1



Student Notebook

Figure 3-20. Library Selection SS232.0

Notes:

Library Selection

Offline devices are excluded

Requested media and drive are selected based on SMS DATACLAS

Libraries with requested media below scratch threshold are excluded

Choice of library is randomized

NOT consideredNumber of available drivesNumber of available scratch cartridgesBusy condition of CU or accessor

Do NOT mix VTSs with unlike number of drives, size of TVC, or level of LIC within one STORGROUP

+

��)��*�




Figure 3-21. TCDB Display 1 SS232.0

Notes:

The ISMF Mountable Tape Volume List shows you what is in the TCDB for the volumes that you have selected.

TCDB Display 1

------------------------------------------------------------------------------ MOUNTABLE TAPE VOLUME LIST Command ===> Scroll ===> PAGE Entries 1-13 of 40 Enter Line Operators below: Data Columns 3-7 of 20 LINE VOLUME USE VOLUME CHECKPT LIBRARY STORAGE OPERATOR SERIAL ATTR ERROR STATUS VOLUME NAME GRP NAM ---(1)---- -(2)-- --(3)-- -------(4)-------- --(5)-- --(6)--- --(7)-- MXX960 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX961 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX962 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX963 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX964 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX965 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX966 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX967 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX968 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX969 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX970 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX971 SCRATCH NO ERROR NO ITSOATL *SCRTCH* MXX972 SCRATCH NO ERROR NO ITSOATL *SCRTCH*. . . . . . . . . . . . . . . . . . . . . . . . . . .



Student Notebook

Figure 3-22. TCDB Display 2 SS232.0

Notes:

TCDB Display 2

------------------------------------------------------------------------------ MOUNTABLE TAPE VOLUME LIST Command ===> Scroll ===> PAGE Entries 1-13 of 40 Enter Line Operators below: Data Columns 8-12 of 20 LINE VOLUME MEDIA RECORDING SPECIAL LAST OPERATOR SERIAL TYPE TECHNOLOGY COMPACTION ATTRIBUTE WRITTEN DATE ---(1)---- -(2)-- -(8)-- ---(9)---- ---(10)--- --(11)--- ----(12)---- MXX960 MEDIA2 36TRACK --- -------- ---------- MXX961 MEDIA2 36TRACK --- -------- ---------- MXX962 MEDIA2 36TRACK --- -------- ---------- MXX963 MEDIA2 36TRACK --- -------- ---------- MXX964 MEDIA2 36TRACK --- -------- ---------- MXX965 MEDIA2 36TRACK --- -------- ---------- MXX966 MEDIA2 36TRACK --- -------- ---------- MXX967 MEDIA2 36TRACK --- -------- ---------- MXX968 MEDIA2 36TRACK YES -------- 1997/11/25 MXX969 MEDIA2 36TRACK --- -------- ---------- MXX970 MEDIA2 36TRACK --- -------- ---------- MXX971 MEDIA2 36TRACK --- -------- ---------- MXX972 MEDIA2 36TRACK --- -------- ----------




Figure 3-23. Tape SMS and BTLS Compared SS232.0

Notes:

You also have the option of using Basic Tape Library Support instead of system-managed tape. This table shows the main differences; note that the main advantage of BTLS is that you may have multiple scratch pools.

BTLS is a separately chargeable program product. System-managed tape is part of DFSMS/MVS.

Tape SMS and BTLS Compared

Capability/Function BTLS Tape SMSTape Management System interface Manual/Clist Automatic via exits

ICL/ACL awareness No Yes

External/internal label verification No Yes

Volume insert/eject processing Manual/Clist Automatic

Labeling of unlabeled tapes Manual Automatic

Operator command interface No Yes

Storage Administrator interface IDCAMS ISMF

Return to scratch Manual/Clist Automatic

Scratch pool management 8 per BTLS 1 per media type

Allocation control technique(s)Jobname/

Procname, OREsoteric

Via SMS constructs

HCD required No Yes

Number of systems or system groups per library

8 32

Import/Export support No Yes



Student Notebook


Notes:

Unit Summary

After completing this unit, you should be able to understand:

System-managed tapeAutomatic insert processingConstructs define libraries and mediaACS routines select constructs

Using ISMF to define constructs

OAM communicates with librariesExitsTape Configuration Database

PARMLIB changes that are needed




Unit 4. Virtual Tape Server Partitioning and Sharing


This unit describes what partitioning and sharing are, the differences between them, and how to implement them.



• Describe the difference between partitioning and sharing • Understand when sharing may not be feasible • Understand the system-wide implications of sharing

References

SG24-4409 Guide to Sharing and Partitioning IBM Tape Library Dataservers


© Copyright IBM Corp. 2001, 2002 Unit 4. Virtual Tape Server Partitioning and Sharing 4-1

Student Notebook


Notes:

Unit Objectives


Describe the difference between partitioning and sharing

Understand the basic principles of partitioning

Understand the use of volume categories

Understand the tasks needed to share a VTS




4.1 Partitioning and Sharing



Student Notebook

Figure 4-2. Challenges for Multisystem Access SS232.0

Notes:

Sharing tape is very different to sharing disk. There are many controls to help you share disk volumes and disk data sets, for example, reserve/release processing, sysplex-wide enqueue propagation, VSAM share options, and database facilities. It is normal and desirable to share disk data.

However, sharing in a tape environment is very different. It is rare that you would wish to share a tape data set. However, it does make sense to share hardware resources such as drives and libraries. It is also useful to share tape data serially among systems for data interchange; a tape data set would be written on one system and read on another.

Challenges for Multisystem Access

Tape access different to disk access

Disk access Tape access

Simultaneous useof a volume Yes No

Volume online toseveral systems Yes Not usual

Simultaneous useof a data set Yes No




Figure 4-3. Platform Considerations SS232.0

Notes:

When we want to share tape resources (libraries, drives or volumes) we must consider differences between the systems that will be used.

The simplest case is when we share between like systems such as two different OS/390 systems. If we want to share between OS/390 and AIX, we have many more differences to consider, even to the point of different data formats if there is floating-point data.

Platform Considerations

Different handling by different host systems ofTape managementAllocation controlHost control data setsSecurityCartridge insertion

Format differencesEBCDIC/ASCII encodingNumeric data formatTape labels



Student Notebook

Figure 4-4. Partitioning and Sharing SS232.0

Notes:

There are two approaches, partitioning and sharing.

Partitioning means that we take a tape library and split it into separate partitions and let different systems use different partitions. Each partition is logically distinct and comprises drives and volumes. However, use of the library resources is common between partitions. If one system has no free drives in its partition and another system using the same library has free drives, the free drive could not be reassigned to the system that needed a drive.

In contrast, sharing allows several systems to share not only library resources but also drives and volumes, although a drive and a volume would only be used by one system at a time. Drives can be reassigned between systems.

We can also have a combination. A 3494 could be split into two partitions and one of the partitions could be shared by several systems.

Partitioning and Sharing

PartitioningShares library resourcesLogically dedicate drives and volumesVolumes cannot be shared unless moved between partitions

SharingSharing volumesPerhaps sharing drivesAll hosts have same access to all volumes




Figure 4-5. Basic Principles SS232.0

Notes:

In all cases, we must share access to the library manager as that is the single control point for the library.

Separation of volumes for partitioning purposes is done by making use of volume categories.

Sharing of drives makes use of commands that assign a drive to a system and then remove that assignment.

Basic Principles

Shared access to Library Manager

Library Manager controls access using volume categories

x'FF00' to x'FFFE' reserved for internal usex'0000' for insert categoryConventions for some other categories

Drive ownershipAssign/unassign for ESCONReserve/release for SCSI

No unique requirements for VTSConsiderations same as for native 3494Except not all platforms supported



Student Notebook

Figure 4-6. Volume Categories SS232.0

Notes:

The table shows the volume category numbers for both scratch and private volumes by different systems that support 3494 attachment.

Note that VSE/ESA native and OS/400 do not support VTS attachment but they can attach a native 3494 library.

In DFSMSdfp, the volume categories may be changed to allow two different systems to partition a library. The defaults are shown.

For AIX use, volume categories are your choice. However, you should not use categories that might be used by another system.

Volume Categories

Environment Scratch categoriesPrivate

categories

DFSMS SMT

x'0001' Media1 (CST) x'0002' Media2 (ECST)x'0003' Media3 (3590) x'0004' Media4 (3590 long)

x'000F'

BTLSx'0FFF' Defaultx'0FF2' - x'0FF8' provide 7 optional scratch categories

x'FFFF'

DFSMS/VMx'0080' - x'008F' provide 16 scratch categories

x'FFFF'

AIXx'012D' for TSM/ADSMDefine others via MTLIB

x'012C' for TSM/ADSMDefine via MTLIB

Othersx'00A0' - x'00BF' VSE/ESAx'0100' - x'0101' OS/400TPF user-defined




Figure 4-7. Partitioning SS232.0

Notes:

Partitioning

Partitioning shares library resourcesCreates multiple logical librariesLogical libraries dedicated to hosts

Split library using volume categoriesControl insert processingVolume serial number ranges

With Advanced Policy ManagementYou may create pools according to the partitions



Student Notebook

Figure 4-8. Assigning Volumes to Categories SS232.0

Notes:

Assigning Volumes to Categories

System-Managed TapeAutomaticControl ranges via cartridge entry exit CBRUXENTDFSMSrmm provides REJECT by system otherwise may need to change CBRUXENT

BTLSManually via LIBRARY commandAssign as private or to one of eight scratch pools

DFSMS/VMManually via RMS interfaceAutomatically by bulk insert processing

AIXManually via MTLIB command




Figure 4-9. Partitioning with System-Managed Tape SS232.0

Notes:

The default volume categories used for System Managed Tape are x'0001' to x'0004' depending on the media type. If you want to have separate partitions with System Managed Tape using each, only one system can use the defaults. You can change the categories to allow partitioning.

Partitioning with System-Managed Tape

Assign different category ranges to different systems

SYS1.PARMLIB(DEVSUPxx)DFSMS/MVS 1.2, 1.3 need PTFsBase function in DFSMS/MVS 1.4 and up

User modification in lower releases

MEDIA1=0011

MEDIA2=0012

MEDIA3=0013

ERROR=001E

PRIVATE=001F

DEVSUPxx

Use ranges 0010

to 007F to avoid

overlap with other

platforms



Student Notebook

Figure 4-10. Partitioning with BTLS SS232.0

Notes:

BTLPRMxx contains defaults for BTLS:

THRESHOLD(count) low scratch threshold to trigger warning message

SCRTCHn default category for scratch mounts

AUTODEMOUNT automatically demount volumes if mounted on an unallocated drive

LIBAFFINITY break UNIT=AFF affinity that cannot be fulfilled

EXPDT98000 allow duplicate volume serial number to be mounted if EXPDT=98000 coded

By specifying SCRTCH2 for a second BTLS system and SCRTCH3 for a third BTLS system in their respective PARMLIB members, we can ensure that different scratch volume categories are used to permit partitioning.

Partitioning with BTLS

Each partition needs its own BTLS catalogs

Different volume serial ranges recommended

BTLS categories set in SYS1.PARMLIB(BTLPRMxx)

Categories assigned using IDCAMS commands:

LIBRARY DEVICES(180,187) LIBNAME(LIB1)

LIBRARY SETCATEGORY CATEGORY(SCRTCH1) LIBNAME(LIB1)

LIBRARY DEVICES(188,18F) LIBNAME(LIB2)

LIBRARY SETCATEGORY CATEGORY(SCRTCH2) LIBNAME(LIB2)




Figure 4-11. Sharing SS232.0

Notes:

Drive sharing allows several systems to use the same pool of drives, dynamically assigning drives when needed and returning them to the pool when they are no longer needed.

JES3 has long provided drive sharing. In a JES2 environment, products are available from Independent Software Vendors and, since MVS 5.2, as part of MVS itself.

Volume sharing allows different systems to share the same volumes. To do this, you need to ensure that the relevant control data sets are shared. For example, if a volume is mounted on one system and is written on, it becomes a private volume. All sharing systems must be aware of the change of status to avoid the volume being mounted as a scratch volume.

Sharing

Drive sharingJES3JES2 plus sysplex tape sharingISV products

Volume sharingNeed to share inventory and control data sets Catalogs and Tape Management System inventory GRS or equivalentSystem-Managed Tape ACDS, COMMDS, TCDBBTLSBTLS catalogs



Student Notebook

Figure 4-12. Sharing with JES3 SS232.0

Notes:

JES3 drive sharing is set up in the JES3 initialization deck.

All the devices in the tape library must be defined in DEVICE statements. JES3 device names are set in the SETNAME statement while the HWSNAME statement defines which device names are subsets of other device names.

Sharing with JES3

Standard part of JES3

All drives online to all systems

JES3 manages drive assignment

Define devices (DEVICE)

Define device names (SETNAME)

Define device name subsets (HWSNAME)

JES3 initialization deck:




Figure 4-13. Sharing with JES2 SS232.0

Notes:

MVS 5.2 introduced sysplex tape sharing. Note that it stores information about which drives are available and who is using them in a coupling facility structure. This means that you need a coupling facility.

A coupling facility is used to provide fast access to the sharing information.

The vary operator command uses the assign and unassign functions provided by the 3480 onwards to prevent a drive being online to more than one system at the same time. However, reassigning drives using the vary command is time-consuming and will cause processing delays.

Sharing with JES2

Sysplex Tape SharingNeeds MVS 5.2 or higher and a coupling facilitySharing information stored in IEFAUTOS structureDrives online to all sharing systemsUnassigned if not in useDrive assignment managed by system

ISV productsComputer Associates MIM

Vary commands

JES2 vary devicenumber,online



Student Notebook

Figure 4-14. Planning for Sharing Tapes SS232.0

Notes:

You must plan a tape sharing implementation carefully. These are some of the questions you must ask to ensure that the status of each individual volume is the same in each system.

Planning for Sharing Tapes

Is host inventory shared?

Do all systems have access to catalogs?

Do all systems share the TMS inventory?

Who does insert processing?

Who manages expiration and movement?

How are hosts informed about status changes?




Figure 4-15. Sharing Controls with SMT SS232.0

Notes:

You may want to set up a limited form of sharing where you want some volumes to be shared but some to remain unshared.

You can only have a single shared scratch pool for each media type. However, there are three ways that you can restrict processing of private volumes. Use of RACF profiles will allow you to restrict use to users or groups in the access lists for the TAPEVOL or TAPEDSN profiles. The DFSMSrmm REJECT parameter, set in the EDGRMMxx PARMLIB member, can prevent output or any use at all from that system. This control is set by volume serial filtering. You can set different statuses for entire tape storage groups from ISMF.

Sharing Controls with SMT

Single shared scratch pool

Sharing private volumesRACF TAPEVOL/TAPEDSN profilesDFSMSrmm REJECT parameterTape Storage Group status

System/Sys Group SMS SG

name status

------------------------- -----------

SYS1A ===> ENABLE

SYS1B ===> DISALL

SYS1C ===> DISNEW

*PLEX1 ===> NOTCON



Student Notebook


Notes:

Unit Summary


Describe partitioning or sharing a VTSJust like a native libraryAssuming platforms supported by VTS

Describe partitioning using volume categories

Describe tape sharing support in OS/390JES2 Sysplex Tape SharingJES3

Understand that tape sharing requires control data to be shared




Unit 5. Virtual Tape Server Management


This unit looks at how you use different sources of information to monitor a VTS through different events. The unit is presented as a case study examining a VTS that sees an increasing workload and an upgrade from a B16 to a B18.



• Understand what items to monitor • Understand the effects of workload and configuration changes • Know when to add virtual or physical volumes to a VTS

References

SG24-2229 Magstar Virtual Tape Server: Planning Installation and Monitoring


© Copyright IBM Corp. 2001, 2002 Unit 5. Virtual Tape Server Management 5-1

Student Notebook


Notes:

Unit Objectives


Understand the effects of reclamation

Understand the importance of initial sizing

Understand how and when to add new virtual and stacked volumes




5.1 Virtual Tape Server Management



Student Notebook

Figure 5-2. Case Study SS232.0

Notes:

We will look at an example of how you would use different tools and techniques to monitor the status of a VTS over a period of time during which there is a constant growth in workload and an upgrade from a B16 to a B18.

Case Study

Look at effects of initial choices

VTS capacity and use over time

Configuration chosen3494-B16Upgrade to B18 with EHPO




Figure 5-3. Points to Note SS232.0

Notes:

In order to understand the statistics that we will use in the rest of the unit, we need to know that there is a difference between a scratch virtual volume that has never been mounted and one which has been mounted at least once. The difference lies in the order used by the VTS to select scratch volumes.

Also, a stacked volume has a life cycle as shown. It starts off empty, then it goes into filling status as the VTS writes virtual volumes to it and then it is demounted when full. As data is rewritten elsewhere, the stacked volume is partially full and the amount of data decreases until the volume is finally a candidate for reclamation, after which it is empty again.

Points to Note

Virtual volume statesNever mounted scratch volumesScratch volumes mounted at least oncePrivate volumes

Stacked volume statesEmpty (scratch)FillingFullPartially full

Empty

Filling

Full

Partially full

Reclamation

Expiration

Selected

by VTS

Data

written



Student Notebook

Figure 5-4. Information Sources SS232.0

Notes:

We will use the information described in this table as a snapshot of the VTS. The table shows where we can get the information.

Information Sources

Description Where to find it

Virtual volumes insertedTCDB or Tape Management System

catalog

Virtual volumes never mounted Virtual volumes inserted - SMF94VLA

Virtual volumes in scratch status

D SMS,LIB(name),DETAILSCRTCH VOLS field

Unexpired private virtual volumes

Virtual volumes inserted - Virtual volumes in scratch

Average size of virtual volumes SMF94VLZ

Stacked cartridges inserted Library Manager Volser Range panel

Scratch stacked volumes (free space)

D SMS,LIB(name),DETAILScratch stacked volume count

Private (in use) stacked volumes

Stacked cartridges inserted - Scratch stacked volume count




Figure 5-5. Initial State SS232.0

Notes:

Two stacked volumes are mounted immediately for the VTS to copy data out of the tape cache.

Description Count

Virtual volumes inserted 15,000

Virtual volumes never mounted 15,000

Virtual volumes in scratch status 15,000

Unexpired private virtual volumes 0

Average size of virtual volumes 0

Stacked cartridges inserted 300

Scratch stacked volumes (free space) 298

Private (in use) stacked volumes 2

Initial State

3494-B16 with 72 GB tape volume cache



Student Notebook

Figure 5-6. After Six Months SS232.0

Notes:

We take our first snapshot after six months.

The initial workload consists of data that is written on a 30-day cycle so that logical volumes expire after 30 days.

After Six Months

Six months of production useApplications expire data within 30 days

EventsSome reclaim activityOperator notified that free space threshold crossed

QuestionsWhy isn't the VTS in a steady state?Why does the free space continue to shrink?




Figure 5-7. Statistics After Six Months SS232.0

Notes:

The key item is that we only have 20 scratch stacked volumes left.

Statistics After Six Months

Description Count

Virtual volumes inserted 15000

Virtual volumes never mounted 2512

Virtual volumes in scratch status 7155


Average size of virtual volumes 224 MB






Student Notebook

Figure 5-8. What Happened SS232.0

Notes:

What Happened

ConclusionToo many virtual volumes defined

Explanation7845 private volumes retained for 30 days261 scratched and rewritten per dayShould have defined about 8500 volumesAssuming 2:1 compression and 50% full volumes8500 x 224 suggests about 190 stacked volumes

The VTS is selecting the volumes never mounted

ActionInsert 100 more stacked volumes




Figure 5-9. Twelve Months Later SS232.0

Notes:

Twelve Months Later

EventsVTS signals that free space threshold has been crossed



Student Notebook

Figure 5-10. Statistics SS232.0

Notes:

The key items are:

• We are down to 20 scratch stacked volumes again.

• We still have 411 virtual volumes that were never mounted.

• The average virtual volume size has increased.

Statistics

Description Count












Figure 5-11. What Happened SS232.0

Notes:

What Happened

Usage2101 more virtual volumes mounted for first timeAverage size increased from 224 to 260 MB

ConclusionExtra space needed because of application growthStill working through the volumes that have never been mounted

ActionAdd 200 more stacked cartridges



Student Notebook

Figure 5-12. After 15 Months SS232.0

Notes:

After 15 months

EventLibrary signaled shortage of scratch virtual volumes

ConclusionHad not happened before because many virtual volumes defined at startSign of workload growth

ActionInsert 2000 more virtual volumes





Notes:

This is a snapshot of the B16 just before it is upgraded to a B18 with EHPO channels.

There are free virtual and stacked volumes. The virtual volume size continues to grow, suggesting a change in workload.

After 17 Months

Description Count









VTS now upgraded to B18 with EHPO



Student Notebook


Notes:

After 18 Months

EventsOne month after B18 and EHPO upgradePerformance and mount time improvementsAverage virtual volume size falling




Figure 5-15. Statistics After Upgrade SS232.0

Notes:

The important changes are:

• The average virtual volume size has decreased for the first time.

• The number of scratch stacked volumes has fallen rapidly.

Statistics After Upgrading

Description Count











Student Notebook

Figure 5-16. What Happened After Upgrading SS232.0

Notes:

We can expect effects from two changes happening at the same time: there is a continual underlying workload growth but there are also effects from doing compression in the channel card as well as at the drive level.

What Happened After Upgrading

ConclusionsEHPO compressing new volumesVolume size shows effect of compressionSmall increase in tape usage as channel compression different to compression by driveNew applications with bigger volumesTransitional state

ActionsMeasure compression ratioAllow virtual scratch pool to decreaseAdd 200 stacked volumes





Notes:

After 20 Months

EventsSMF data showing that B18 not reaching throughput limitsFree space dropping fastShortage of available library slots

QuestionWhy is free space dropping?



Student Notebook

Figure 5-18. Statistics After 20 Months SS232.0

Notes:

The average volume size continues to fall. There are still some scratch virtual volumes. These statistics do not show why free space is falling.

Statistics After 20 Months

Description Count












Figure 5-19. Active Data Distribution SS232.0

Notes:

Notice the peak in the number of volumes with 10-25% valid data.

510

1520

2530

3540

4550

5560

6570

7580

8590

95100

Percentage of Active Data

0

10

20

30

40

50

60

70

80

90

100N

um

ber

of V

olu

mes

Active Data Distribution



Student Notebook

Figure 5-20. What Happened After 20 Months SS232.0

Notes:

ObservationMany volumes just above reclaim threshold

ConclusionVolumes contain many unexpirable virtual volumes

ActionAdjust reclaim threshold

What Happened After 20 Months





Notes:

Unit Summary

After completing this unit, you should be able to understand:

There are no simple rules of thumb

Interactions are based onWorkload changesInitial decisionsConfiguration changesTuning actions

The case study shows the effects of Number of virtual volumesSize of virtual volumesRetention period of virtual volumesReclaim thresholdCompression



Student Notebook




Unit 6. Virtual Tape Server Operations


This unit describes how to operate the VTS using the library manager console. The major library manager panels are shown to illustrate how you can accomplish common tasks during the installation and operation of a VTS.



• Navigate through the library manager panels • Understand the main uses for the library manager panels • Perform common tasks using the library manager

References

GA32-0288 Magstar 3494 Tape Library: Operator Guide

SG24-2229 IBM Magstar Virtual Tape Server:Planning, Implementing and Monitoring


© Copyright IBM Corp. 2001, 2002 Unit 6. Virtual Tape Server Operations 6-1

Student Notebook


Notes:

Unit Objectives


Understand the different operational modes

Understand how to use the library manager panels




6.1 Virtual Tape Server Operations



Student Notebook

Figure 6-2. Operational Modes SS232.0

Notes:

The Virtual Tape Server forms part of a 3494 library. The library can operate in one of three modes:

1. Automatic

2. Pause

3. Manual

The library should normally be in automatic mode.

Operational Modes

AutomaticAccessor working, doors closedUnder control of Library Manager

PauseMount, demount, eject or audit requests queuedAccessor parkedUse high-capacity I/O facility or correct problems

ManualVTS can be operated in manual modeLibrary Manager console provides mount requestsMounts done manually

Modes apply to the whole 3494




Figure 6-3. Library Manager Panels SS232.0

Notes:

• Menu along top of screen

• Select items using trackpoint in keyboard

• Scroll using trackpoint or cursor movement

• Window controls to:

- Minimize windows - Maximize windows - Close windows

• Keyboard shortcuts

Library Manager Panels



Student Notebook

Figure 6-4. Mode Pull-down SS232.0

Notes:

Select this by clicking Mode or pressing Alt-m .

The marker in front of Auto and Offline shows the current setting.

Mode Pull-down




Figure 6-5. Status Pull-Down SS232.0

Notes:

The status panel allows you to find out information about:

• The library operation status at a summary level

• Whether all the components are working properly

• The status of the VTS or VTSs

• Library performance

• VTS performance

Status Pull-down



Student Notebook

Figure 6-6. Operational Status SS232.0

Notes:

This panel shows configuration information.

Operational Status




Figure 6-7. Component Status SS232.0

Notes:

• Graphical representation of library internal components.

• Highlights hardware problems.

Component Status



Student Notebook

Figure 6-8. Queues Pull-down SS232.0

Notes:

Individual tasks in the library are placed on queues for execution. This pull-down lets you see the whole queue or individual queues for:

• mount

• demount

• eject

• insert

• audit

• clean

Queues Pull-down




Figure 6-9. Database Pull-down SS232.0

Notes:

The database menu pull-down allows you to find out information from the library manager and the VTS. You may:

• Search the database for volumes according to criteria you choose.

• Create a listing from the database.

• Find out which stacked volume holds a given logical volume.

• Request a map of stacked volume.

Database Pull-down



Student Notebook

Figure 6-10. Search Database for Volumes SS232.0

Notes:

Enter criteria in the entry boxes or by using the radio buttons and press the search button. The results are displayed on the screen.

Search Database for Volumes




Figure 6-11. List Database Volumes SS232.0

Notes:

This panel also allows database queries. There are two differences between this and the search panel. You can create a disk or diskette copy of the output and you can choose which five columns in the table to report on.

List Database Volumes

Up to 5 volume fields may be selected to be included in the output list. The data will be

sorted by the first two output columns.

The data may be decreased by selecting a specific rack, media type, category, a volume mask, or by specifying one or more indicator flags.

The output may be directed to a file on the A: disk or to the LISTDB.LST file on the C: drive.

List Database Volumes

Output device

Specific Rack

C:\LM\LISTDB.LSTA: Filename

Output Column 1

HelpCreate List... Cancel

Misplaced

IgnoreNoYes ��

��

��

��

��

��

��

��

��

��

Unreadable

Mounted

Inaccessible

Manual mode

��

��

��

��

Specific Media Type

Specific Category

Volume Mask

Output Column 2 Output Column 3 Output Column 4 Output Column 5



Student Notebook

Figure 6-12. Find Logical Volume Home SS232.0

Notes:

This panel allows you to find out which stacked volume holds a specific logical volume.

Find Logical Volume Home




Figure 6-13. Find Logical Volume Home LIC 527 LM SS232.0

Notes:

Find Logical Volume Home LIC 527 LM



Student Notebook

Figure 6-14. List Stacked Volume Contents SS232.0

Notes:

If there is a physical problem with a cartridge, you need to know which logical volumes are on it. This panel produces a list on a diskette.

List Stacked Volume Contents




Figure 6-15. List Stacked Volume Contents LIC 527 LM SS232.0

Notes:

List Stacked Volume Contents LIC 527 LM

Previous Maps are

listed

Up to 10 maps are

saved

Map can be copied to

diskette after map is

retrieved



Student Notebook

Figure 6-16. Commands Pull-down SS232.0

Notes:

The Commands pull-down menu contains a number of options that do not fit naturally under the other menu choices.

There are important submenus under System Management.

Commands Pull-down




Figure 6-17. Cleaning SS232.0

Notes:

The Cleaning dialog box allows you to set up a cleaning schedule and how long to use a cleaning cartridge.

Cleaning



Student Notebook

Figure 6-18. Volume Ranges for Stacked Volumes SS232.0

Notes:

This panel specifies which volumes will be stacked volumes.

Define the volumes as stacked volumes before entering them in the library.

Stacked volumes are only visible to the library manager and the VTS. No host can see them.

Volume Ranges for Stacked Volumes




Figure 6-19. Volume Ranges for Stacked Volumes LIC 527 SS232.0

Notes:

Volume Ranges for Stacked Volumes LIC 527



Student Notebook

Figure 6-20. Inserting Logical Volumes SS232.0

Notes:

Although logical volumes have no physical existence, you must insert them to make them known to the library manager.

Note: Do not insert many more logical volumes than you need.

Inserting Logical Volumes




Figure 6-21. Inserting Logical Volumes LIC 527 SS232.0

Notes:

Inserting Logical Volumes LIC 527



Student Notebook

Figure 6-22. Ejecting Stacked Volumes SS232.0

Notes:

Use this if you need to eject a stacked volume that is showing an excessive number of temporary errors.

The contents of the stacked volume being ejected are copied to other stacked volumes. When the stacked volume is ejected, it does not contain VTS data.

Ejecting Stacked Volumes




Figure 6-23. Ejecting Stacked Volumes LIC 527 SS232.0

Notes:

Ejecting Stacked Volumes LIC 527



Student Notebook

Figure 6-24. Set Category Attributes SS232.0

Notes:

Fast Ready mounts are done at electronic speeds. Make sure that you define your scratch categories here to exploit fast ready scratch mounts.

Set Category Attributes




Figure 6-25. Set Management Policies SS232.0

Notes:

This panel allows you to set three key VTS policies:

1. When reclamation may not be run.

2. The amount of used space that triggers reclamation of a volume.

3. At what threshold the VTS should alert you that it is short of free space.

Set Management Policies



Student Notebook

Figure 6-26. Set Management Policies LIC 527 (1 of 3) SS232.0

Notes:

Set Management Policies LIC 527 (1 of 3)





Notes:




Student Notebook


Notes:





Figure 6-29. Inserting Stacked Volumes SS232.0

Notes:

There are four similar panels to manage:

1. Unassigned volumes

2. Import volumes

3. Insert volumes

4. Export-hold volumes

The panel allows you move volumes between categories.

Inserting Stacked Volumes



Student Notebook

Figure 6-30. Set Up Stand-alone Device SS232.0

Notes:

DFSMSdss stand-alone restore of system volumes needs to be able to do this.

Set Up Stand-alone Device




Figure 6-31. Inventory SS232.0

Notes:

An inventory is done when:

• A 3494 or VTS is installed

• A 3494 or VTS is upgraded

• A door is opened

Inventory

Inventory new storageUsed after upgradeUpdate LM database about new frames

Re-inventory complete system

Inventory updateFull or partial (frames with doors opened)Checks cells, drives, reads bar codesUpdate LM database

Password protected



Student Notebook

Figure 6-32. Interventions SS232.0

Notes:

Before enhanced messaging, the message at an MVS console merely stated Intervention Required . You needed to go to the library manager and choose the Interventions option on the Commands pull-down menu.

Interventions




Figure 6-33. Options Pull-down SS232.0

Notes:

You may choose the language used for library manager dialogs. If you change it, the new language is used after the library manager is shut down.

Options Pull-down



Student Notebook


Notes:

Unit Summary


Operate VTS from library manager

Use panels forSetting up policiesInserting or importing volumes

Use panels forStatusPerformance




Unit 7. Planning and Exploiting VTS Capacity


This unit discusses how you can use the VMA analysis tool to estimate the number of virtual and stacked volumes needed and decide what the bandwidth requirements are. It then looks at common known workloads and discusses how well they use a VTS and identifies any changes that may be valuable to make best use of a VTS.



• Understand what tools to use in planning a VTS configuration, • Plan the number of volumes needed, and • Plan which common workloads to move to a VTS

References

SG24-2229 Magstar Virtual Tape Server:Planning, Implementing and Monitoring


© Copyright IBM Corp. 2001, 2002 Unit 7. Planning and Exploiting VTS Capacity 7-1

Student Notebook


Notes:

Unit Objectives


Understand how to estimate the VTS capacity you need

Plan for the number of volumes you will need

Understand which tape work to move to your VTS




7.1 Planning and Exploiting VTS Capacity



Student Notebook

Figure 7-2. VTS Sizing SS232.0

Notes:

The Volume Mount Analyzer needs SMF record types 14, 15 (for tape), 21 and either:

• Type 30, subtypes 4 and 5, or

• 4, 5, 34 and 35

Filtering allows you to model the effects of different subsets of your tape workload.

VTS Sizing

Answer configuration questionsHow many virtual volumes to define?How many stacked volumes are needed?

Volume Mount AnalyzerPart of DFSMSdfpAnalyzes historical SMF dataAPAR OW21238 recommended Run for at least one month, capture monthly peaksFiltering by job, data set, program, and so on




Figure 7-3. VMA Extract Processing SS232.0

Notes:

To get an accurate view, you need to run the Volume Mount Analyzer for a month. However, this can result in very large amounts of data. The PTF for APAR OW21238 provides a way to extract the data more frequently and so break the processing down into more manageable jobs.

VMA Extract Processing

After OW21238



Student Notebook

Figure 7-4. VMA Output SS232.0

Notes:

VMA Output

Filtering allows you to model the effect of moving different workloads.

Read/write ratioUnderstand the effect of fast ready scratch mounts.

Hourly mount rates

Hourly transfer ratesDetermine throughput requirements.




Figure 7-5. Planning for VTS Volumes SS232.0

Notes:

Planning for VTS Volumes

Volume serial numbers

How many volumes?Logical volumesPhysical stacked volumes



Student Notebook

Figure 7-6. Planning Volume Serial Numbers SS232.0

Notes:

Volume serial numbers must be unique

• Within a library

• Within systems sharing a TCDB

The diagram shows a possible naming convention that allows you to see instantly what is on a cartridge. This can help you interpret messages.

Planning Volume Serial Numbers

,�-�.�/� ��,��"

$�"# �,

"��"�$�"# �,

��0/�)0

�0

��(�(��'��

�"��/��

$�"# �,

&0�/��0�/�)0

��0�/��0

Volsers must be unique within library and systems sharing TCDB.




Figure 7-7. How Many Logical Volumes? SS232.0

Notes:

This formula allows you to estimate the number of logical volumes you should initially define for your VTS. It is easy to add more volumes but difficult to remove them.

If you have too many logical volumes defined, it can interfere with VTS internal space management.

How Many Logical Volumes?

Defining too many logical volumes uses up free space.

VTS prefers volumes that have never been used.

Logical volumes = Nst + Nds (Texp + Trts)

Nst = scratch threshold from ISMF

Nds = number of scratch volumes mounted each day

Texp = Average number of days before a volume expires

Trts= Number of days between TMS return to scratch runs



Student Notebook

Figure 7-8. Logical Volumes Example SS232.0

Notes:

Logical Volumes Example

Case study from Unit 5

Assume scratch threshold is 100

8500 leaves enough spare

Logical volumes = 100 + 261 x (30 + 1)

= 8191




Figure 7-9. How Many Stacked Volumes? SS232.0

Notes:

This formula allows you to estimate the number of stacked volumes you should insert into the VTS. You can always add additional volumes if you underestimate.

How Many Stacked Volumes?

Use information fromVolume Mount AnalyzerTape Management System

Nst = (MBact / MBsvol) + Nstemp

MBact = No. logical vols x avg vol. size

MBsvol = Native capacity x compression ratio x average utilization

Nstemp = No. empty stacked volumes



Student Notebook

Figure 7-10. Stacked Volumes Example SS232.0

Notes:

Stacked Volumes Example

Using the case study from Unit 5 assume that we want at least 20 scratch stacked volumes.

Nst = (MBact / MBsvol) + Nstemp

Nst = (7845 x 224)/(10,000 x 3 x 0.5) + 20

= 1,757,280/15,000 + 20

= about 140




Figure 7-11. Choosing Workloads for the VTS SS232.0

Notes:

You may have many different workloads that are candidates for a VTS. We need to understand what characteristics suit a VTS so that you can choose the best candidates, especially if you also have native 3590s.

Choosing Workloads for the VTS

DFSMShsm

DFSMSdss

ADSM

DB2

BATCHBATCH

IMS

CICS

...other database utilities

...other backup/archive utilities



Student Notebook

Figure 7-12. VTS Basic Characteristics SS232.0

Notes:

Although a VTS emulates 64 virtual 3490Es, it does not have the same bandwidth as this many drives.

The VTS is good at filling cartridges. A workload that is also good at filling cartridges does not gain the benefit from the VTS.

You can interchange data between a VTS and another VTS or native drives with import/export. If you do not have import/export, consider whether interchange or vaulting needs prevent data from being placed in a VTS.

Jobs that read tape data backwards perform particularly well in a VTS.

VTS Basic Characteristics

Throughput64 virtual drives, 4 ESCON paths, but finite bandwidth

Cartridge capacity utilizationUses and manages full 3590 capacityVery large data sets have less immediate benefit

Data locationClosed store - no off-site dataUnless Import/Export is used

Tape volume cacheRead access after write benefits from TVCFast read backwardsReduces elapsed time of jobsFrees virtual drive sooner for use by other jobs




Figure 7-13. Application Usage SS232.0

Notes:

If you have native 3590s and a VTS, this chart shows where each device type is well-suited when we consider data set size and throughput requirements.

size

throughput

?

?VTS

native 3590

Application Usage



Student Notebook

Figure 7-14. Common Types of Data SS232.0

Notes:

There is now a lot of practical experience running different workloads in a VTS environment. Often, you can make small changes that tune the workload to run better in a VTS. Equally, you may choose to select certain workloads for your VTS because they work particularly well.

Common Types of Data

DFSMShsmMigration, backup, dumpABARS

ADSM or Tivoli Storage Manager

DFSMSdssApplication point-in-time backupsOff-site dumps

Database logs and image copies

Batch applications




Figure 7-15. VTS and DFSMShsm SS232.0

Notes:

DFSMShsm has long been able to fill cartridges with incremental backup data, migration data and, more recently, by being able to stack volume dumps. From this perspective, DFSMShsm data may not be the best exploiter of a VTS. However, DFSMShsm also works best when it can use many drives in parallel where each individual task will not use the full bandwidth of a native 3590. The ability to give additional virtual drives to DFSMShsm can be very useful.

VTS and DFSMShsm

No special advantage in using VTS for DFSMShsm data.Already fills tapes.Recall activity faster from native drives.Dump data cannot be removed easily from the VTSwithout import/export.ABARS and AUTODUMP parameters allow stacking.

But...VTS can be an excellent choice for backup.Small installations benefit from additional virtual drives.Depending on the tasks performed and on the size of data sets, bandwidth is less of an issue if designed properly.



Student Notebook


Notes:

If DFSMShsm is asked to recover or recall datasets, it will mount the backup tapes or ML2 tapes to get the data back to a primary volume. If the volume needed is not already in the tape volume cache, the DFSMShsm task requesting data must wait until the entire volume is in the cache. It helps if the size of the volume being staged into the cache is limited as this reduces the wait time. One way to do this would be to use CST emulation rather than ECCST; however, it is better to use DFSMShsm control to limit the amount of data written to a logical volume so that you only need to define ECCST volumes in the VTS.

Use a scratch pool for DFSMShsm tapes to gain the benefits of fast ready mounts.

VTS and DFSMShsm

Use ECCST emulated cartridgesSETSYS parameter TAPEUTILIZATION(LIBRARYMIGRATION(PERCENTFULL(40)))TAPEUTILIZATION(LIBRARYBACKUP(PERCENTFULL(97)))

97% minimizes number of virtual volumes<50% can speed up recall process

Set parameters

SELECTVOLUME(SCRATCH) and TAPEDELETION(SCRATCHTAPE)

Global scratch pool benefits from scratch category fast ready attribute

Turn off DFSMShsm host compression





Notes:

Use of PARTIALTAPE(MARKFULL) increases the proportion of fast ready mounts and has no space penalty.

Use large TAPESPANSIZE to reduce occasions needing two specific mounts for one large data set and to speed up recycle processing.

A percentage full of 97% will allow you to move work between VTS and native drives, use TAPECOPY to native drives or duplex to native drives.

Avoid allowing recall to monopolize VTS physical drives.

There is no need to stack dumps when they are written to a VTS.

SETSYS PARTIALTAPE(MARKFULL)Partially full volumes waste no space in the VTS.

SETSYS TAPESPANSIZE(800)Reduce number of virtual volumes recalled.

SETSYS TAPEUTILIZATION(LIBRARYMIGRATION (PERCENTFULL(97))) will not distinguish between 3490 and emulated 3490 drives.

Number of recall tasks should not exceed number of physical VTS drives minus one.

AUTODUMPDo not use STACK option with VTS.Can be taken off-site if written electronically to off-site VTS or Advanced Function feature is installed.

VTS and DFSMShsm



Student Notebook

Figure 7-18. DFSMShsm Copies and Recycling SS232.0

Notes:

You can duplex and copy tapes outside the VTS if you follow these guidelines.

Consider when you run RECYCLE so that you choose a period when the VTS will have free drives.

TAPECOPY and DUPLEX functionOutput volume must be same device as input and the same size or larger.Do not copy from (compacted) tape to (uncompacted) virtual volume.Do not copy from (LZ1) virtual volume to (IDRC) tape.

RECYCLE functionReduces number of logical volumes but can cause bottlenecks.Use RECYCLE SELECT(INCLUDE(RANGE(nnnnn:mmmmm))) with lower percentage for VTS logical volumes to minimize recycle.

DFSMShsm Copies and Recycling




Figure 7-19. DFSMShsm ABARS SS232.0

Notes:

ABARS is usually used to provide disaster backups and hence there is a requirement that the data be off-site. If you have an off-site VTS, whether for electronic vaulting or as part of a peer-to-peer configuration, ABARS is a suitable workload. You may be able to use export if the amount of data is not excessive.

ABARS is a useful way of getting data out of a VTS.

DFSMShsm ABARS

Consider disaster recovery functionsABARS data can be written to off-site VTSPeer-to-Peer VTSExport ABARS data

ABARS used to move data out of VTSOption USERTAPES

Do not use STACK option on ABARSTAPES



Student Notebook

Figure 7-20. ADSM/Tivoli Storage Manager (1 of 3) SS232.0

Notes:

Several TSM functions request a new scratch volumes and, often, it is very unlikely that they will fill the volume. These are good VTS candidates.

These functions include:

• TSM database backup

• Incremental backup

• Incremental copy storage pool

• Sequential storage pool

Collocation keeps client data together on a small range of tape volumes. This will help recovery by reducing the number of specific mounts needed to recover the data for a TSM client.

Tivoli Storage Manager (1 of 3)

TSM database full and incremental backupFull backup for disaster recovery needs to be off-site.Incremental backup wastes less space using VTS.

Copy storage pool full and incrementalFull copy of primary storage pool to non-VTS drives for removal off-site.Incremental copy may be stored in the VTS.

Sequential storage pool for backup and archiveVTS suitable for sequential storage pool.VTS suitable for TSM server-server configurations.

Use collocation when using VTS Partially full tapes not an issue with VTS.





Notes:


MAXSCRATCHUse a scratch pool to benefit from scratch category fast ready attribute.

MOUNTLIMITConsider increasing drives available.Take into account VTS overall performance.

MOUNTRETENTIONSet to 0 to free virtual drive for other users.Virtual volume data will remain in TVC for fast reaccess.



Student Notebook


Notes:


MAXCAPACITYTailor maximum volume capacity. <100% full logical volumes can speed up recall process.

BACKUP DB and EXPORTUse SCRATCH=YES to use tapes from the Tape Management System scratch pool.Performance benefits with scratch category fast ready attribute.




Figure 7-23. DFSMSdss SS232.0

Notes:

The key points to consider are:

• Is the DFSMSdss dump for local recovery or disaster recovery?

• Is the dump for point-in-time recovery?

If you have large amounts of data being backed up for disaster recovery purposes, you may consider native drives to give high throughput and ease of cartridge transport.

However, at the other end of the spectrum, small uncontrolled application backups can be excellent VTS candidates as they will expire quickly and, if used, are very likely to be still in the tape cache.

If you are dumping for local recovery, the use of a VTS can avoid tape wastage without the extensive JCL changes needed for dump stacking.

DFSMSdss

Must export VTS volumes to physically remove from VTS.Not suitable for huge amounts of disaster recovery data.Not suitable for huge amounts of backup data for off-site vaulting.Potentially suitable for on-site recovery data.Suitable for remote vaulting over ESCON distances.

DFSMSdss full volume dumps in a VTS.DASD volume dump uses fraction of tape capacity.Stacking dumps involves extensive JCL changes.

VTS without channel compression.Use SMS DATACLAS to override default of five volumes.

COMPRESS keyword if EHPO is not installed.Uses host processor cycles to perform compression.



Student Notebook

Figure 7-24. DFSMSdss Stand-alone SS232.0

Notes:

If you use the Stand-Alone Services component of DFDSS 2.5 with PN77830 and PN74583 or DFSMSdss with OW16802 and OW14835, you can do a stand-alone restore from any library volume, whether VTS-resident or not.

DFSMSdss Stand-alone

VTS virtual drives can be put into stand-alone mode.Library Manager pull-down menusMust be offline to other systems

DFSMSdss allows restore from library.

Mount from input station not allowed.Since we cannot insert a virtual volume into the input station.

Restore is possible from any label on an input volume.

RESTORE FROMDEV(TAPE) FROMADDR(0A40) TOADDR(0900)

NOVERIFY TAPEVOL((V00000),(V00001))




Figure 7-25. DB2® Archive Logs SS232.0

Notes:

DB2 archive logs are an excellent VTS candidate as they do not fill tapes, and recovery from the logs uses read backwards and many drives.

Archive uses one scratch tape per log (150 MB - 1 GB)Suited to VTS where no space will be wastedTailor active log size so that archive fits on one virtual volume

Data remains cached on TVC for fast recoveryRead backwards used in DB2 recovery from tapeMuch better performance from VTS

DB2 recovery and backup can require many drivesVTS not constrained with 64 virtual drives

Dual archive for backup: one local and one remoteLocal copy can go to VTS instead of TMM Remote copy to non-VTS tape or to a remote VTS

DB2 Archive Logs



Student Notebook

Figure 7-26. DB2 Image Copies SS232.0

Notes:

DB2 image copies can vary in size depending on the size of the table space being backed up. You can take a full or an incremental image copy.

Small image copies work well in the VTS and incremental copies are often suitable.

Large, full image copies may be better on native drives.

Recovery uses many drives and this also suggests that the VTS is a good repository for incremental image copies.

DB2 Image Copies

Table space sizes vary from a few MB to several GBSmall and medium backups suit VTS avoids wasted spaceLarge backups less suited, may need greater bandwidth

Create only on-site incremental image copies in VTS daily

Create full image copies outside VTS weekly

Run multiple copies concurrently (no drive constraint)Each image copy can be on separate logical volumeSecond (off-site) small backup copy wastes real cartridge space

MERGECOPY DB2 utilityCreates off-site copies from VTS copiesFixed volume size helps to group table spaces to be copied




Figure 7-27. DB2 Recovery SS232.0

Notes:

Database recovery may need many drivesFull copy and all incrementals need to be allocated at the same timeVTS not constrained with 64 virtual drivesMay allow less frequent full image copies

DB2 Recovery



Student Notebook

Figure 7-28. CICS Journals and IMS Logs SS232.0

Notes:

The considerations for CICS journals and IMS logs are the same as for DB2 archive logs.

IMS has a change accumulation utility that consolidates many logs into a single log. As this needs many drives, it works well in a VTS.

CICS Journals and IMS Logs

Both CICS/IMS off-load to tape, local and remote copiesCan be written in separate jobs or in one jobLocal can go to VTS and remote to non-VTS or VTS in remote siteOne scratch tape used for every logSuited to VTS where no space will be wasted

IMS uses read backwards to recover from tape logMuch better performance through VTSRecovery operation faster with more available drives

IMS change accumulation utility Accumulates changes from several IMS logsMany input logs to one output requires multiple drives




Figure 7-29. IMS Image Copies SS232.0

Notes:

The considerations for IMS image copies are the same as for DB2 image copies except that all IMS image copies are full, not incremental.

Image copy is a backup copy of IMS databaseBatch utility copies one or more databases to tapeCan use one virtual volume per copy in VTSNo wasted capacityNo extra resource changing JCL or manual stacking

IMS recoveryWithout logs, must recover image copy before start of batch runLogs and checkpoints throughout batch activity allow recovery from consistent database imageFast access to image copies and logs from a VTS

IMS Image Copies



Student Notebook

Figure 7-30. Batch Tape Applications SS232.0

Notes:

The VTS can be an excellent place for point-in-time backups written by a range of utilities as there are no concerns about filling tapes and the jobs may well need drives, not throughput.

If the data is needed again to recover data for a rerun, it is very likely that it is still in the tape volume cache.

Batch Tape Applications

Batch application data benefits in VTS VSAM REPROIEBGENER / IEBCOPY / ICETOOLDFSMSdss data set DUMPAny general tape copy utility

Data can be tiny or hugeNo wasted capacity if data set does not fill a volume

No need to tune buffering

Review requirement to move backup copies off-site




Figure 7-31. Tape Mount Management SS232.0

Notes:

Tape Mount Management uses SMS automatic class selection routines to intercept tape allocations and direct them to a disk buffer in order to save tape mounts. The buffer is then swept to tape by DFSMShsm. This has some similarities to VTS processing.

It is likely that some TMM data is suitable for a VTS but some may not be because of disk functions exploited by the TMM buffer.

Tape Mount Management

Depends on workload

VTS easier to set upNo ACS changesFewer exceptions due to completeness of tape emulationNot just for OS/390

TMM to DASD aloneCan exploit remote copy for high availabilityCan exploit sequential striping for high throughputNeeds careful monitoring and management class design



Student Notebook


Notes:

Unit Summary


Estimate number of virtual and stacked volumesUse information from VMA and TMS catalogsAvoid problems later

Evaluate each type of tape workload

Exploit VTS strengthsFast scratch mountsGood cartridge capacity utilization for small data setsMany virtual drivesRead hits from cacheFast read backwards




Unit 8. Monitoring and Exploiting VTS Performance


This unit describes the configuration choices that influence VTS throughput, looks at the individual elements of a VTS to see how they have an effect, and suggests what should be monitored and how.



• Understand which components are involved in data transfers • Understand what performance measurements to make • Understand what tools to use


© Copyright IBM Corp. 2001, 2 002 Unit 8. Monitoring and Ex ploiting VTS Performance 8-1

Student Notebook


Notes:

Unit Objectives


Describe the configuration choices that influence performance

Use VTS functions to monitor performance

Understand key items to monitor

Understand the host data available for monitoring




8.1 Monitoring and Expl oiting VTS Performance



Student Notebook

Figure 8-2. Basic Performance Considerations SS232.0

Notes:

A native tape drive has relatively simple performance characteristics. The main characteristics are:

• Data transfer rate

• Tape speed

• Tape handling time

As there is almost invariably only one user of a tape, there are few queueing considerations. In contrast, a VTS is an effective tape subsystem because it does share components between users.

Basic Performance Considerations

VTS not as simple as non-VTS

Native drives have fixed bandwidth and characteristicsChannel throughput Drive mount timeDisconnect time

VTS performance depends on other factors like:Read/write ratioPercentage of virtual mounts causing recallTVC residence timeSpace reclamation activityInternal performance management algorithmsApplication use of tape drivesShared resources




Figure 8-3. Configuration Choices SS232.0

Notes:

Different VTS configurations will perform differently.

Compression in the channel adapters has the effect of making the tape cache contain more data. A larger cache contains more data than a small one; this increases the chance of rereading data and also allows the VTS to run at peak throughput for longer.

When it is necessary to read data from stacked cartridges or write it to stacked cartridges, more drives allows greater parallelism (and so throughput) and reduces queuing for a free drive.

The optional performance accelerator feature can be installed for the highest throughput.

Configuration Choices

Channel compressionMagnifies size of tape cache

Tape cache sizeLarger cache increases chance of rereadLarger cache smoothes out peaksLarger cache can defer copy operations to period of low load

Number of drivesReduce queuing for drives

Performance accelerator featureHigher throughput



Student Notebook

Figure 8-4. Performance Accelerator Feature SS232.0

Notes:

The Performance Accelerator is an optional chargeable feature. It comprises new microcode and new hardware.

Performance Accelerator Feature

New file system for Tape Volume CacheOptimized for sequential transferOptimized for large files

Designed for RAID disk arraysLarge blocksizes (256 KB)Each write spans a complete array

Parallel I/Os for reads and writes

Hardware upgrades match file system changesAdditional processors and memory




Figure 8-5. Shared Resources SS232.0

Notes:

There are several shared resources in a VTS system:

• Physical 3590 drives

• The tape volume cache

• The VTS controller

• Stacked volumes

• Internal queues

Shared Resources

The VTS has several shared resources

RISC/6000 Processors

Magstar Tape Drives Stacked Volume

TVC access paths

Queues

Copy

Recall

Channel Writes

Channel Reads

TVC

Re

ca

ll qu

eue

Co

py q

ueu

e

recall1

recall2

recall3

recall4

copy1

copy2

copy3

copy4



Student Notebook

Figure 8-6. VTS Controller Processor Use SS232.0

Notes:

The chart shows some of the tasks that use processor capacity. Some, such as the recall tasks, depend on workload; some, such as virtual drive emulation, depend on configuration; and some, such as AIX, are fixed.

VTS Controller Processor Use

��

��

��

��

��

��

��

��

��

��

��

AIX

SM Software

Virtual Drive Emulation

Up to 256 Tasks

VirtualVolume

CopyRecall

Reclaim

No scale implied




Figure 8-7. Tape Volume Cache Access Paths SS232.0

Notes:

There are four paths between the VTS controller and the tape volume cache. So, there can be a maximum of four concurrent transfers.

Tape Volume Cache Access Paths

Copy

Recall

Channel Writes

Channel Reads

TVC



Student Notebook

Figure 8-8. Physical 3590 Drives SS232.0

Notes:

Drives are used by reclamation tasks (two drives per task), recall tasks reading data from tape and copy tasks which write data from the cache to tape.

Physical 3590 Drives

RecallsUp to n-1*

drives

CopiesUp to n-1*

drives

Reclaim

Copy must keep up with write workload

Reclaim will start if scratch < 10 volumes

*n = number of installed drives (3-6)




Figure 8-9. Stacked Volumes SS232.0

Notes:

Since each stacked volume will contain hundreds of logical volumes, we can occasionally find that a recall is being done from a stacked volume while another recall request is queuing to recall a different logical volume from the same stacked volume.

Stacked Volumes

queuing

At times, multiple recall tasks need to access logical volumes on the same stacked volume,

causing queuing against the stacked volume.



Student Notebook

Figure 8-10. Internal Queues SS232.0

Notes:

The VTS maintains queues to manage contention for shared resources. Here we see queues for recall and for copy. Although the queues are logically separate, the entries in the queue are waiting for drives or volumes.

Internal Queues

Copy from cache to stacked volumes

Keeps cache from filling

VOL632

VOL211

VOL594

VOL603

VOL046

Recall Copy

Queues against drives and/or stacked volumes

Caused by specific mounts not satisfied from cache




Figure 8-11. Processes Using Tape Volume Cache SS232.0

Notes:

Processes Using Tape Volume Cache

HostWrite

Copy

Read

Recall

Fragment

��

��

��

TVC



Student Notebook

Figure 8-12. Tape Volume Cache Management SS232.0

Notes:

The contents of the tape volume cache must be managed to ensure that there is sufficient free space for virtual volumes to be held in the cache when requested and to maximize the number of read hits for virtual volumes in the cache.

Tape Volume Cache Management

Objectives of TVC managementEnsure sufficient free space availableMaximize number of read cache hitsMaximize TVC performance by avoiding read/write contention

What VTS uses to manage TVCInternal allocation of physical drivesImposing I/O delays (Throttling) Delay response to host write TVC Contents

��

��

��

��

��

��

Free Space

Copied and Not Migrated

Not Yet Copied

Fragments

Logical

Volumes{




Figure 8-13. Throttling SS232.0

Notes:

Throttling delays the response to host write requests.

It is done to ensure that the tape volume cache does not fill completely.

Throttling

Copy Queue HighDelay response to each host write until copy queue below trigger.

RecallDelay response to each host write until the recall queue is empty.The VTS will calculate a throttle delay based on the number of active recall tasks.

Cache Free Space LowDelay response to each host write until free space above trigger.Increase the number of drives available for copy.Reduce number of drives available for recall.



Student Notebook

Figure 8-14. Performance Evaluation Guidelines SS232.0

Notes:

When evaluating performance, we need to know what measurements are important and when to use them.

Performance Evaluation Guidelines

Guidelines for evaluating performanceOverall system performanceChannel throughputCache miss rateVirtual drive mount timeDisconnect timeTime in cache (TVC residence time)

Use Daily Statistics for high-level analysis

Use Hourly Statistics to have more detail




Figure 8-15. Tools SS232.0

Notes:

There are several sources of information about a VTS.

At the library manager console, you can see a number of performance-related displays. You can also install the VTSLOGRP tool, downloadable from the ftp site shown, which will run on the library manager itself.

OS/390 records tape library information in SMF type 94 records which can be analyzed by several different tools. We will refer to VTSSTATS (available from the ftp site) later in this unit.

Finally, there are tools to analyze EREP MDR records to identify jobs that write small blocks to tape (bad for any tape subsystem, not just VTS) and which show you the compression ratio that you are achieving.

Tools

Library ManagerLibrary Manager panelsVTSLOGRP *

SMF type 94 analysisPerformance Reporter for MVS (5695-101)VTSLOGRP *VTSSTATS *DFSORT reporting

EREP MDR analysisSmall block size *Compression ratios *

* Available for download from

ftp://ftp.software.ibm.com/storage/tapetool



Student Notebook

Figure 8-16. Overall Performance SS232.0

Notes:

If the tape workload is completed on time and the average mount time across one day is less than 30 seconds, there is no problem to analyze.

Overall Performance

Is the work getting done?

Yes Is daily average

mount time 30 sec or

less?

PerformanceOK

No

Determine cause

Start

Yes

No

Plan for growth

Determine cause




Figure 8-17. Channel Throughput SS232.0

Notes:

If the VTS is running at or close to the limit you expected when configuring it, you need to consider how you will accommodate any growth or peaks in workload.

Channel Throughput

Shift = or greater than

calculated max?

Room for

growth

No room for growth

Start

Yes

No



Student Notebook

Figure 8-18. Cache Miss Rate SS232.0

Notes:

The VTSSTATS Virtual Drive Activity report shows us the number of mounts not satisfied from the cache. If the miss rate over an hour averages more than 20%, it shows that the cache may not be large enough.

Cache Miss Rate

Start

Hourly % Miss

> than 20% ?

Never

Good workload -

Indicator of good health

Yes Other overload

indicators present?

No

Examine workload or add cache

capacity

Yes

Immediate relief needed

-Likely to show

poor performance

The number of virtual mounts that are cache misses divided by the total virtual mounts times 100 equals % Miss




Figure 8-19. Virtual Drive Mount Time SS232.0

Notes:

Two indicators are important:

1. How long was the longest mount.

2. How long did mounts take on average.

Virtual Drive Mount Time

Any Virtual mounts greater than900 sec?

Find the cause and

considermoving the workload

Yes

Hours with virtual

mountsavg.> 30

sec?

No No MountTime OK

Start

Yes

Remove workload or

add resources

Type of mount Expected mount time Delay causes

Scratch 1-3 seconds Never

Specific, cache hit 2-3 seconds Never

Specific, cache miss 2-3 minutes Drive or stacked volume



Student Notebook

Figure 8-20. Mount Time for Specific Mounts SS232.0

Notes:

Mount Time for Specific Mounts

Factors that can affect Specific Mount TimeNumber of installed drivesMount arrival rateMultiple recalls from same stacked cartridgeConcurrent reclamationCache size

Main factor is usually number of cache missesMounts for recall




Figure 8-21. Disconnect Time SS232.0

Notes:

A high disconnect time shows that the VTS was throttling writes.

Disconnect Time

Any RMF

Intervals with> 500 ms ?

Start

YesOnly

Occasionally?

YesSome

Serious Throttling

No

No Serious Throttling

Often

Immediate Relief

Required -VTS

Overloaded

Find the cause and consider

moving the workload

Possible Causes:- Cache full - Excessive recalls



Student Notebook

Figure 8-22. Library Manager Statistics Panels SS232.0

Notes:

We can see information on VTS workload and activity by using the statistics panels at the library manager.

Library Manager Statistics Panels




Figure 8-23. VTS Active Data Panel SS232.0

Notes:

This panel shows you the amount of active data and the converse, the amount of free space. Note that the active data figure includes invalid volumes that have not yet been reclaimed. It does not include volumes in the cache that have not yet been copied to tape.

The free storage alarm level is the level that is set at the library manager. The maximum active data level is calculated.

VTS Active Data Panel



Student Notebook

Figure 8-24. VTS Data Flow SS232.0

Notes:

This shows the amount of channel traffic for the previous 24 hours.

VTS Data Flow




Figure 8-25. VTS Mount Hit Data SS232.0

Notes:

This panel shows, over a 24 hour period, which mounts are:

• Fast ready hits

• Cache hits

• Cache misses

VTS Mount Hit Data



Student Notebook

Figure 8-26. VTS Physical Device Mount History SS232.0

Notes:

This shows the minimum, average and maximum number of drives used during the past 24 hours.

VTS Physical Device Mount History




Figure 8-27. VTS Logical Mounts per Hour SS232.0

Notes:

This shows the number of logical mounts each hour.

The number is the sum of the fast ready mounts, cache hits and cache misses. Use it together with the Mount Hit Data panel.

VTS Logical Mounts per Hour



Student Notebook

Figure 8-28. VTS Active Data Distribution (1 of 2) SS232.0

Notes:

This shows you the distribution of the percentage of active data across all stacked volumes. It helps you to decide whether the reclamation threshold suits your data.

VTS Active Data Distribution (1 of 2)




Figure 8-29. VTS Active Data Distribution (2 of 2) SS232.0

Notes:

VTS Active Data Distribution (2 of 2)



Student Notebook

Figure 8-30. Performance Tests SS232.0

Notes:

These numbers are purely illustrative and do not guarantee the throughput that you will see with your data and your workload. They were obtained in a laboratory environment with a mixture of data. Your results will vary.

In addition, these figures show a 100% write workload. Throughput will normally improve as the proportion of reads increases.

This information is shown for illustrative purposes, is based on initial performance tests, and does not as such provide a performance guarantee. Performance results may vary.

Note :

Performance Tests

B18 - 2 ESCONB18 EHPO - 2 ESCOB18 EHPO - 4 ESCOB18 PAF - 4 ESCON

B10 - 4 ESCONB18 PAF - 8 ESCON

B20 - 8 ESCON *B20 - 16 ESCONB20 - 8 FICON **

0 50 100 150 200

Bandwidth

Sustained Peak 32k blksize

100 % Write. 3:1 Compression; 800 MB Volume

Virtual Tape Server Performance

* 8 channel B20 performance is with > 6 drives

** 8 channel B20 performance is with 12 x 3590 drives





Notes:

Unit Summary


Describe the configuration choices that influence performance

Use VTS functions to monitor performance

Understand key items to monitor

Understand the host data available for monitoring



Student Notebook




Unit 9. Data Migration


This unit discusses two types of migration: getting data into a VTS and migrating from one VTS to a different configuration.



• Describe how to get active data into a VTS • Describe how to get static data into a VTS • Plan migration activity caused by VTS upgrades


© Copyright IBM Corp. 2001, 2 002 Unit 9. Data Migration 9-1

Student Notebook


Notes:

Unit Objectives


Describe how to move data into a VTS

Describe different ways of upgrading a VTS




9.1 Data Migration



Student Notebook

Figure 9-2. VTS Migrations SS232.0

Notes:

Any times given in this unit are solely for the purposes of illustration. The actual times needed to do upgrades depend on the initial status of the VTS and the number of trained personnel available to perform the upgrade.

VTS Migrations

Two main types of migrationMoving non-VTS data into a VTSUpgrading or moving an existing VTS

Moving non-VTS dataNew work into a VTSImplementing VTS for the first timeStatic data and active data

All elapsed times shown in this topic are only estimates. You should check with Customer

Engineers. Careful planning may allow overlaps.




Figure 9-3. Active Data SS232.0

Notes:

Active data is that which is continually being generated, new versions replacing old.

It is easy to get active data into the VTS. Normally, you can just use the ACS routines to let Tape SMS allocate the data into the VTS. Similarly, the old data expires so need not be moved anywhere.

Several types of data fall into this category. Typically, backup data is active data in that we usually keep a fixed number of backup generations.

Active Data

Data that is continually being generated

ExamplesDFSMShsm backup or migrationBatch generation data setsImage copies, log archives

Just direct the data to the VTSStorage group ACS routineBTLS unit name

Old data will disappearSpeed up with DFSMShsm RECYCLE or similar



Student Notebook

Figure 9-4. Static Data SS232.0

Notes:

Static data does not change. It is not rewritten. If we want it in the VTS, we must move it there. We must also correct location information in the tape management system and catalogs.

Static Data

Data for archival or long-term retention

Five-step processIdentify the dataMove the dataCorrect Tape Management System informationRecatalog if necessaryReturn old volume to scratch

Tape copy tools




Figure 9-5. Identifying Static Data SS232.0

Notes:

We can use a tape management system or catalog entries to locate static data. A tape management system will tell us when data was written and last accessed, both of which indicate archive data. If we know a naming convention, the catalog will help us locate the data.

Often, we can produce an extract file from a tape management system that we can use to produce JCL or commands.

Identifying Static Data

Sources of informationTape Management System databaseCatalog

Select by attributesApplicationExpiration

Beware applications tracking their own data sets

Store volume serial numberArchiving products

Flat file of

data sets

Tape Management

System database

Extract



Student Notebook

Figure 9-6. Copying Static Data SS232.0

Notes:

Whatever tools we use, we must ensure that the output of the copying operation actually goes into the VTS, so we will need to review ACS routines or use the correct unit names.

The tool that is used to copy the data depends to some extent on what the data format is. If the data is written in DFSMSdss dump format, DFSMSdss COPYDUMP should be used to copy it as the block size may exceed 32 KB.

Otherwise, there is a range of tools that can copy sequential data.

Copying Static Data

Ensure that output will go to VTS

Some tools to move dataDFSMSdss COPYDUMPSequential dataIEBGENERDITTO/ESADFSORT ICEGENERDFSORT ICETOOLISV tools




Figure 9-7. Correct TMS Information SS232.0

Notes:

When the data set is moved, we want to maintain some of the information about it. As an example, with archival data, the creation date is important yet the new copy will have the current date. We may want to use TMS functions to set it to the original creation date.

Correct TMS Information

Ensure that the VTS copy is managed correctlyFile sequence numberCreation data and timeLast read/write datesJobnameNew volser

DFSMSrmm exampleCHANGEDATASET command

CHANGEDATASET 'tape.dataset' -

CRDATE(original date) -

FILESEQ(n) -

JOBNAME(creating job name) -

VOLUME(new volume) -

FORCE



Student Notebook

Figure 9-8. Correct Catalog Information SS232.0

Notes:

Correct Catalog Information

Only if the data was catalogedRemove old catalog entry

Add new catalog entry

Beware TMS catalog retentionDo not wait before recataloging

DELETE NOSCRATCH ...

DEFINE NONVSAM ...




Figure 9-9. Tape Copy Tools SS232.0

Notes:

Independent Software Vendors have tools that may help with all or part of a data migration. Here are some that you may wish to evaluate for your own use.

Tape Copy Tools

Technology Plus Beta55Tape Stacker, can be used to copy data into the VTSwww.betasystems.com

BrightStor CA-1Tape Management Copycat Utilityca.com

OpenTech Tape/CopyISPF InterfaceVTS Supportwww.opentechsystems.com


© Copyright IBM Corp. 2001, 2002 Unit 9. Data Migration 9-11

Student Notebook

Figure 9-10. Tape Copy Tools SS232.0

Notes:

Tape Copy Tools

Seasoft Zela Removable Media MaximizerSoftware Engineering of America (US)www.seasoft.com




Figure 9-11. VTS Model Upgrades SS232.0

Notes:

A VTS model upgrade needs careful planning. Depending on circumstances, there may be more than one way that the upgrade can be done.

VTS Model Upgrades

B16

B18



Student Notebook

Figure 9-12. Model Upgrade Migration Scenarios SS232.0

Notes:

There are three different ways that a B16 to B18 migration may be done:

1. Within the same library with a model conversion.

2. Add a new B18 to the same library.

3. Add a new B18 in a new library.

Model Upgrade Migration Scenarios

Scenario 1: MES UpgradeModel upgrade from B16immediate migration (move VTS database)convert B16 to feature 5500 or 5502

Scenario 2: Parallel operation within one libraryAdd B18 in the same 3494 libraryParallel operation until migration complete

Scenario 3: Parallel operation with two librariesAdditional 3494 library with B18Parallel operation until migration completeImmediate migration move stacked volumes, LM database and VTS database Requires special tools or services3494 B16 to be kept or upgraded later




Figure 9-13. MES Upgrade SS232.0

Notes:

The left of the diagram shows the initial configuration with a 3494 containing a B16. The right shows the target configuration.

Note that the serial number is transferred from the B16 to the B18.

The frame that held the B16 becomes another type of frame: either a storage or a drive frame.

MES Upgrade

3494

Lxx3494

D12 3494

B16

Serial =12345

3494

B18

3494

5500/5502

Serial Removed

3494

Lxx3494

D12

Serial = 12345

LAN

SCSI

EXISTING

TARGET

CE moves VTS Data Base to Migrate Logical Volumes From B16 to B18

One or more phases required for upgrade

Cache and controller returned to IBM



Student Notebook

Figure 9-14. MES Upgrade Tasks SS232.0

Notes:

The upgrade has three tasks. The library manager upgrade can be done separately.

MES Upgrade Tasks (B16 to B18)

Update Library Manager

Model upgrade B16 to B18Vary VTS offlineForce migrate virtual volumes to tapeCopy VTS database and cache resident data to tapeConnect B18 to existing D12Restore data from tapeVary VTS online

Convert B16 to storage/drive frameRemove cache and controllerReturn parts to IBMRemove FC9006 and FC9007Add FC5500 (Storage Frame) orAdd FC5502 (Drive Frame for B18)




Figure 9-15. MES Upgrade Outage Time SS232.0

Notes:

You may not need to upgrade the library manager. If you do, it can be scheduled well in advance of the B16 upgrade.

The variation in B16 upgrade times depends on how much data must be copied from the cache.

MES Upgrade Outage Time

Activity3494 Offline

TimeVTS Offline

Time

Upgrade Library Manager

2 Hours 2 Hours

B16 Cache Capacity

3494 Offline Time

Minimum VTS Offline

Time

Maximum VTS Offline

Time

72 GBCache

3 Hours 6 Hours* 9 Hours*

144 GBCache

3 Hours 6 Hours* 12 Hours*

Update Library Manager

Convert B16 to B18

(*) Upgrade times can be minimized by scheduling configuration update after a period of low write activity



Student Notebook

Figure 9-16. Parallel Operation with One Library SS232.0

Notes:

Here we add a D12 and B18 and keep the old VTS for some time.

As we are adding a second VTS, we must define it to HCD and SMS.

Parallel Operation with One Library

3494

Lxx3494

D12 3494

B16

3494

Lxx 3494

D123494

B16 3494

D12

3494

B18

Serial =54321

Serial =12345

Serial =12345

EXISTING

1) Add D12

2) Add B18

Expand configurationUpdate Library Manager Add D12 with 3590sAttach B18 to new D12Vary B18 online




Figure 9-17. Add SMS Tape Library for B18 SS232.0

Notes:

As we have a second VTS, we must define it as a new SMS library.

Add SMS Tape Library for B18

------------------------------------------------------------------------------ TAPE LIBRARY DEFINE Page 1 of 2 Command ===> SCDS Name . : SYS1.SCDSRLS Library Name : LVTS18 To Define Library, Specify: Description ==> ==> Library ID . . . . . . . . . . . 54321 (00001 to FFFFF) Console Name . . . . . . . . . . Entry Default Data Class . . . . DC3490 Entry Default Use Attribute . . SCRATCH (P=PRIVATE or S=SCRATCH) Eject Default . . . . . . . . . PURGE (P=PURGE or K=KEEP) Media Type: Scratch Threshold Media1 . . . . 200 Media3 . . . . 0 (0 to 999999) Media2 . . . . 300 Media4 . . . . 0 (0 to 999999) Use ENTER to Perform Verification; Use DOWN Command to View next Panel;



Student Notebook

Figure 9-18. Add SMS Storage Group for B18 SS232.0

Notes:

We must have a storage group for the B18 only so that we can direct new work to the B18 alone.

Add SMS Storage Group for B18

------------------------------------------------------------------------------ TAPE STORAGE GROUP DEFINE Command ===> SCDS Name . . . . . : SYS1.SCDSRLS Storage Group Name : SGTAPE To DEFINE Storage Group, Specify: Description ==> Local VTS ==> Library Names (1 to 8 characters each): ===> LVTS18 ===> ===> ===> ===> ===> ===> ===> DEFINE SMS Storage Group Status . .... N (Y or N) Use ENTER to Perform Verification and Selection; . . . . . . . . . . . . . . . . . . . . . . . . . .




Figure 9-19. Parallel Operation SS232.0

Notes:

The B16 is drained by new work being written to the B18. At some stage, you will be left with a residue of volumes that you will need to copy.

Parallel Operation

Drain B16Workload redirected to new library using ACS routines (nondisruptive)Residual volumes copied at the end of transition period

3494

Lxx 3494

D12 3494

B163494

D12

3494

B18

Serial = 54321

Serial = 12345

read writecopy



Student Notebook

Figure 9-20. Migration Tasks SS232.0

Notes:

If you upgrade the B16 after it has been drained, the disruption is minimized. We have avoided the force migrate and database backup steps.

Migration Tasks

Migrate workload to B18Different logical and stacked volume ranges required for the new 3494 B18Define new ranges for B18Expand tape management and TCDB databases Redirect workload to B18 using nondisruptive changes to DFSMS ACS routines and constructsCopy remaining volumes at end of transition periodElapsed time may vary considerably

Complete model upgrade processUpgrade B16 to B18, orKeep B16 in use for specific applications or systems




Figure 9-21. Parallel Operations 1 SS232.0

Notes:

This is similar to the previous approach, the difference being that we add a new library and VTS, not just a VTS. This means that there is no disruption to the first VTS or library.

Parallel Operations 1

3494

Lxx3494

D12 3494

B16

Serial = 12345

EXISTING

3494

D12

3494

Lxx

3494

B18

Serial = 54321

LAN

SCSI

1) Add 3494 and VTS B18



Student Notebook

Figure 9-22. Parallel Operations 2 SS232.0

Notes:

Parallel Operations 2

2) DRAIN B16Workload redirected to new library using ACS routines (nondisruptive)

Residual volumes copied at the end of transition period

read

write

copy

3494

Lxx3494

D12 3494

B16

Serial = 12345

3494

D12

3494

Lxx

3494

B18

Serial = 54321

LAN

SCSI




Figure 9-23. Parallel Operation Migration Tasks SS232.0

Notes:

Parallel Operation Migration Tasks

Install new configurationDifferent logical and stacked volume ranges required for the new 3494 B18 define new ranges for B18 expand tape management system and TCDB databases Lxx, D12, B18Vary B18 online

Migrate workload to B18Redirect workload to B18 using nondisruptive adjustments to DFSMS ACS routines and constructsCopy residual volumesElapsed time may vary considerably

Complete model upgrade processUpgrade B16 to B18Keep B16 in use for specific applications or systems



Student Notebook

Figure 9-24. Physical Cartridge Movement SS232.0

Notes:

We may physically move the data from the B16 to the B18, either by taking the cartridges and database or by doing a controlled VTS disaster recovery.

Physical Cartridge Movement

3494

Lxx3494

D12 3494

B16

Serial = 123453494

Lxx

3494

B18

Serial = 54321

LAN

SCSI

EXISTING B16 1) Add 3494 and VTS B18

Move Stacked Volumes

CE moves VTS Database to migrate Logical Volumes from B16 to B18

3494

D12




Figure 9-25. Physical Cartridge Movement Tasks SS232.0

Notes:

The library manager database and the VTS database must be moved to the new VTS. After that, all the volumes (both scratch and private) should be moved from the old VTS to the new.

Physical Cartridge Movement Tasks

Install new configuration.

Move Library Manager Database and VTS Database. Requires specialized services and tools from the old B16 to the new B18.Can maintain the same Library Sequence Number (Library ID).

Move the stacked volumes to the new B18.Fill the B18 with Private and Scratch Stacked Volumes from the B16.

Complete Model Upgrade Process.Upgrade B16 to B18.Keep B16 in use for specific applications/systems.



Student Notebook

Figure 9-26. Physical Cartridge Movement Outage Time SS232.0

Notes:

Physical Cartridge Movement Outage Time

Activity Minimum 3494 Offline

Time

Maximum 3494 Offline

Time

Minimum VTS Offline Time

Maximum VTS Offline

Time

Add new 3494 with B18 and D12 frames

None None None None

Force Migrate72 GB*144 GB*

None None 1 Hour 6 Hours

Move Stacked Volumes to B18

0.5 Hour 1 Hour 0.5 Hour 1 Hour

Move LM and VTS database

to B180.5 Hour 2 Hours 0.5 Hour 2 Hour

Vary B18 online and test

0.5 Hour 2 Hours 0.5 Hour 2 Hours

(*) Upgrade times can be minimized by scheduling configuration

update after a period of low write activity.




Figure 9-27. Comparing Migration Paths SS232.0

Notes:

Upgrading the VTS in place is the lowest cost approach.

Adding a second VTS is more expensive but is good for fallback.

Adding a second VTS in a new library is the least disruptive.

Physical cartridge movement allows extended testing and frees the source VTS for upgrade quickly.

Comparing Migration Paths

Advantages Drawbacks

Scenario 1In Place Migration

no customer involvementno data movementno transition hardware to be installed

no additional SW definitions needed (HCD,DFSMS)

outage timelittle testing possiblelimited fallback possibilities

Scenario 2Parallel Operation within

one Library

Preferable solution if 2nd VTS subsystem planned

outage timetesting possiblegood fallbackpreferable solution if D12 for 2nd VTS is already installed

data movementadditional SW definitions needed (HCD, DFSMS)

Scenario 3Parallel Operation with

two Libraries

outage timeextended testing possibleexcellent fallback possible

transition hardware to be installed / de-installed

customer involvement-data movement-additional sw definitions needed (HCD, DFSMS)

Scenario 4Physical Cartridge

Movement

Extended testing possiblePreferable solution if 2nd 3494 library planned

Outage timeAdditional SW definitions needed (HCD, DFSMS)

needs specialized tools or services



Student Notebook

Figure 9-28. Other Migrations SS232.0

Notes:

These are upgrades that might be done to a B18.

Other Migrations

Migrating to EHPO channels

Migrating to 3590E drives

Migrating to Performance Accelerator Feature




Figure 9-29. Migrating to EHPO Channels SS232.0

Notes:

If you have a B18 without EHPO channels, you might choose to upgrade to improve performance and add extra channels. Note that simply adding EHPO cards is less disruptive.

Migrating to EHPO Channels

If you installed a B18 and are adding HPO function

Estimated upgrade and outage times

Activity Minimum 3494 Offline

Time


Time

Minimum VTS Offline

Time

Maximum VTS Offline

Time

Upgrade LIC on LM and VTS

2 Hours 3 Hours 2 Hours 3 Hours

Replace ESCON cards

Concurrent Concurrent 2 Hours 3 Hours



Student Notebook

Figure 9-30. Effects of Adding EHPO Channels SS232.0

Notes:

Before EHPO channels, virtual volumes in the tape volume cache would be uncompressed. All virtual volumes written after the installation of the EHPO channels will be compressed. As old data is copied out of the cache, the proportion of compressed virtual volumes will grow. Since we expect the compressed volumes to be smaller, we will get many more virtual volumes in cache.

Although the channel cards and the 3590 drives both use LZ1 compression, the algorithms are tuned differently. It is possible that there may be further compression at the drive; it is also possible that the data may grow slightly when written to tape.

Effects of Adding EHPO Channels

Volumes will be compressed in tape volume cache.As soon as writtenEffect of tape drive compression hard to quantify

Existing volumes remain uncompressed.Until rewrittenMixture of compressed and uncompressed volumes in cacheProportion of compressed volumes will grow

Increased throughput.




Figure 9-31. Migrating to 3590E VTS Drives SS232.0

Notes:

You might consider this to increase the capacity that you can store in your VTS.

All the drives in one VTS must be the same.

Migrating to 3590E VTS Drives

Why do it?Double cartridge capacity with same cartridgesGreater data rate improves VTS performance

VTS considerationsAll drives in one VTS must be the sameCould have different drives in two VTSs in one 3494Cannot export from 3590E and import on 3590BHost not aware of drive change

VTS migrationStarts to write in 256-track modeWill not complete partially-filled 128-track cartridgesCan read 128-track volumesMay want to increase Reclaim Threshold to rewrite 128-track cartridges sooner



Student Notebook

Figure 9-32. Migrating to 3590E Drives SS232.0

Notes:

Migrating to 3590E VTS Drives

Sample timings, may take separate steps

LIC may be at right levelActivity Minimum

3494 Offline Time


Time

Minimum VTS Offline

Time

Maximum VTS Offline

Time

Upgrade LM LIC to 523.00

1 hour 2 hours 1 hours 2 hours

Upgrade VTS LIC to 2.17.10

none none 2 hours 5 hours

Convert one 3590B drive

none none 1.5 hours 2 hours

Drive remove/install

none none1 hour for

first, 0.5 for others

1 hour for first, 0.5 for

others




Figure 9-33. Migrating to the Performance Accelerator SS232.0

Notes:

The upgrade may have several steps depending upon the configuration you start from. However, the key task is that the tape volume cache is rebuilt with a different RAID format and different file system. This means that the cache must be backed up and restored as part of the upgrade.

The intention of installing the Performance Accelerator Feature is to provide much higher levels of peak and especially sustained throughput than a B18 with EHPO channels.

Migrating to the Performance Accelerator

Completely rebuilds tape volume cacheDisruptiveMust force migrate to copy all volumes to tapeThen backup VTS database and volume fragments

May need LIC upgrade

May need upgrade of ESCON cardsNeed Extended Performance cards

May need to install prerequisitesTape volume cache (144 or 288 GB)At least four 3590 drives



Student Notebook

Figure 9-34. Migrating to the Performance Accelerator SS232.0

Notes:

The major variation is in the force migrate time.

Migrating to the Performance Accelerator

?Activity Minimum

3494 Offline Time


Time

Minimum VTS Offline

Time

Maximum VTS Offline

Time

Upgrade LM LIC to 523.01

1 hour 2 hours 1 hours 2 hours

Upgrade VTS LIC to 2.17.8

none none 2 hours 5 hours

Install new ESCON cards

none none 1.5 hours 1.5 hours

Force migrate and backup

none none 1.5 hours 7.5 hours

Install PAF none none 6 hours 6 hours





Notes:

Unit Summary

At the end of this unit, you should be able to understand:

Different approaches to move work into VTSStatic dataActive data

VTS upgradesCareful planning is crucialCan often overlap tasksYou may have a choice of techniques3494 often still available during VTS upgrades



Student Notebook




Unit 10. Import/Export


This unit describes what the optional VTS import/export feature does, why is might be used, and how to use it. Operational changes are also discussed.

Additionally, it describes the software and hardware prerequisites.



• Describe what import/export does • Identify the hardware and software prerequisites • Set up import and export • Understand how VTS operations change with import/export


© Copyright IBM Corp. 2001, 2 002 Unit 10. Import/Export 10-1

Student Notebook


Notes:

Unit Objectives


Describe the capabilities of import/export

Identify the hardware prerequisites

Understand the software requirements and interactions

Set up export and import

Understand the operational changes




10.1 Import/export



Student Notebook

Figure 10-2. Import/Export Objectives SS232.0

Notes:

Before import/export, the VTS was a closed store. This meant that data could only be put in to the VTS or taken out by writing or reading. Data could not be physically removed in a usable state save for the special case of disaster recovery.

This meant that the VTS was not suitable for some types of data where physical data movement was needed.

Import/export provides the ability for you to name groups of logical volumes which the VTS will move on to volumes that can be ejected from the library and taken to another library.

This widens the scope of include interchange data and data needing disaster backups.

Import/Export Objectives

VTS is no longer a closed storeCan get logical volumes out of a VTS

Widens scope of VTS forArchivalData needing disaster backupInterchange data




Figure 10-3. Import/Export Design SS232.0

Notes:

The main design features are:

• Import and export are command-driven.

• The commands refer to a list volume.

• The list volume contains a list of volumes and destinations.

• The logical volumes are moved to a volume that may be removed.

• The output volume contains logical volumes and a self-describing volume map.

Import/Export Design

EXPORT LIST 01

VOLSR1,DISASTER

VOLSR2,DISASTER

VOLSR3,BACKUP

VOLSR4,BACKUP

VOLSR5

TVC Fragments

Logical Volume

Volume Map

LI EXPORT,EXP001

EXP001

EXP001



Student Notebook

Figure 10-4. Import/Export Prerequisites SS232.0

Notes:

Available for B18 models with compression cards onlyMicrocode level supporting the I/E function is requiredMust have minimum four Magstar drivesMust have convenience I/O stationAvailable on B10 and B20Not peer-to-peer

Available only with DFSMS/MVS System Managed TapeNot BTLSNeeds DFSMS/MVS 1.4 or 1.5 plus SPEDFSMSrmm support included

I/E functional specification made available to vendorsComputer Associates (CA-1 and TLMS)Platinum (AutoMedia, formerly ZARA)BMC (Control-T)BETA Systems (BETA51)

Import/Export Prerequisites




Figure 10-5. Import/Export Fundamentals SS232.0

Notes:

Export takes data out of a VTS while import returns it into a VTS.

Import has additional options to bring a volume back as a scratch volume or as a newly initialized volume.

The volume that we remove from the VTS acts as a container. It has its own volume serial number but it also contains a number of exported logical volumes with their own logical volumes. The idea of a container volume is used by tape library management systems.

ExportAllows logical volumes to be moved to tape cartridges which are subsequently removed from the libraryExported logical volumes no longer exist in the library

ImportAllows logical volumes to be copied from exported tape cartridges back into a VTSCan import volumes as scratch or initialized states

Container volumesExported logical volumes stored in containerExported stacked volume

Import/Export Fundamentals



Student Notebook

Figure 10-6. Import/Export Terms SS232.0

Notes:

We tell a VTS what it should import or export by using list volumes.

As the name suggests, the primary contents are a list of volume serial numbers to be processed. The second file is reserved and not currently used. Nevertheless, it must still be written. There is also a status file which the VTS writes into in order to communicate the results of the import or export.

The exported logical volumes are written to an exported stacked volume or container volume.

Import/Export Terms

Export List VolumeLogical volume within VTS that containsExport List fileExport Status file

Import List VolumeLogical volume within VTS that containsImport List fileImport Status file

Exported Stacked VolumeHolds the exported logical volumesVolser reported to tape management system via CBRUXEJC exitSelected randomly at time of EXPORT from scratch stacked volume poolNew LM panels to make disposition decisions after EXPORT and before IMPORT




Figure 10-7. Import/Export Software Support SS232.0

Notes:

Import/export support is provided as PTFs for DFSMS/MVS 1.4 and 1.5 only.

Toleration PTFs are available for sharing systems running earlier levels of DFSMS/MVS. The toleration PTFs allow a VTS with import/export to be attached to earlier systems

Import/Export Software Support

Toleration:OAM 1.1 and above: OW36674RMM 1.2 and above: OW37516

Component 1.4 1.5

RMM OW36349 OW36350

OAM OW36342 OW36343

ISMF OW36351 OW36352

SMS OW36526 OW36527

Device Services OW36360 OW36362

OW36363 OW36364

Advanced Policy Management

Exploitation by DFSMS/MVS only (APAR OW54054)

SPE for OS/390 Version 2 Release 10

SPE for z/OS Version 1 Release 1

SPE for z/OS.e Version 1 Release 1

Toleration

PTFs for DFSMS/MVS 1.5 and higher (APAR OW54056)



Student Notebook

Figure 10-8. VTS Prerequisites SS232.0

Notes:

A convenience I/O station is required as you will need to move cartridges into and out of the VTS.

The VTS must have channel adapters that do compression and at least four 3590s. You have to order feature #4000 to get the import/export microcode.

VTS Prerequisites

Library frame#5210 10 cartridge convenience I/O station or#5230 30 cartridge convenience I/O station

B18 VTS#4000 Advanced Function or#4001 Advanced Policy Management#3200 ESCON High-Performance Option or#3400 Extended High-Performance Option

B10 / B20 VTS#4000 or #4001

Number of drivesFour minimumSix highly recommended




Figure 10-9. VTS Drives for Import/Export SS232.0

Notes:

Import or export uses two drives. It is a tape-to-tape copy. There can only be one import or export being processed at one time.

VTS Drives for Import/Export

PRE-MIGRATE

RECALL

RECLAIM

RECLAIM

IMPORTEXPORT

IMPORTEXPORT

Data copied from tape to tapeNo tape volume cache space used

Import/export uses two drivesNeed to have drives for other VTS purposes



Student Notebook

Figure 10-10. Import/Export Planning Considerations SS232.0

Notes:

While import or export are running, two drives are no longer available for recall or copying to stacked volumes. This effectively reduces the throughput of the VTS by about 15%.

Import/Export Planning Considerations

Expect overall VTS performance degradation of 15% while performing operation

Always use one Storage Group for every VTS with Import/Export function

ACS routines must address the correct VTS when setting up for import/export of logical volumes to write the list volume

Must drive export from OS/390 but can be for volumes for other platforms




Figure 10-11. Export Process Flow 1 SS232.0

Notes:

Normally, your tape management system will control what data is to be vaulted. Using its usual vaulting policies, the tape management system should construct a list of logical volumes to be removed from the VTS.

Volumes may optionally be given a destination. Logical volumes for different destinations will not be copied on to the same stacked volume.

Export Process Flow 1

Run tape management vaulting processing or equivalentBased on vaulting rules, find the volumes that have to be exported and their destinationCreate a list containing each volume with its destination (up to 16 characters)

EXPORT LIST 01

VOLSR1,DISASTER

VOLSR2,DISASTER

VOLSR3,BACKUP

VOLSR4,BACKUP

VOLSR5

.......

Export Destination

(optional)

Logical volume to be exported



Student Notebook


Notes:

Three files must be written to the export list volume.


Write the Export List Volume files to a logical volume

Export List fileList of logical volumes to be exported and destination

Reserved fileOnly header record

Export Status fileVTS writes status records for each logical volume

IEBGENER utility

Export List

Reserved

Export Status

Logical

Volume




Figure 10-13. Export Hints SS232.0

Notes:

Export Hints

List volume needs standard tape label

Must not use compaction for the list volume

Volume serial of export list volume passed to VTS when Export started

Easier to automate export operation by using specific volume serial numbers

To export volumes from more than one VTS, create one combined export volume list file and copy it to the export list volume in each exporting VTS

At LIC levels 527 (LM) or higherIf the number and size of logical volumes to be Exported fits upon a J type cartridge then it Will be chosen over a K type

ORIf no K type media is available then a J type (HPCT) will be chosen



Student Notebook

Figure 10-14. Export Hints Concerning APM SS232.0

Notes:

Export Hints Concerning APM

Export - Construct names can either be assigned

at Import time or

the LM default constructs can be assigned

Non APM to APM capable VTSs

Export - Construct names are passed with

exported logical volumes

APM to non APM capable VTSs

Export - Construct names are not intrepreted

APM to APM capable VTSs





Notes:

The export can be started by command or by using the CBRSPLCS batch interface. An interface is provided to allow a tape management system (or other program) to request an export.

When the export list is processed, the logical volumes are put in export pending status so that it cannot be used. A volume that is in use will not be exported.

Start the EXPORT operationUsing the LIBRARY EXPORT commandUsing the CBRSPLCS batch interface(shipped in SAMPLIB)

Logical Volumes to be exported are put in Export Pending category (FF12) when the Export Volume function starts


Logical VolumesExported Stacked Volumes

DISASTERBACKUPblank



Student Notebook


Notes:

You can cancel an export. If you restart it by reissuing the export command, the operation will restart at the last stacked volume boundary.


Wait for the EXPORT operation to completeCan take long time if exporting many volumes from different stacked cartridgesStop the operation if needed with LIBRARY EXPORT,CANCEL The EXPORT operation can be rerun at any timePreviously exported volumes not re-exported since they are no longer in the VTSRestart point is at exported stacked volume level

Once the output stacked volume is filledExported logical volumes deleted from VTSOAM and tape management system are notified via CBRUXEJC exit




Figure 10-17. Export Status File SS232.0

Notes:

We can check the results of the export by looking at the export status file. OAM issues messages that tell us of the progress of an export operation.

Export Status File

Check the results of the EXPORT operationCheck for OAM messagesCheck status file (3) for resultsUsing RMM commands and displaysUsing the ISMF panel interface

EXPORT STATUS 01 VOLSR1, ,18,*No Data Associated With Logical Volume VOLSR4, ,18,*No Data Associated With Logical Volume VOLSR5, ,05,*Logical volume not in VTS VOLSR2,STKD01,00, DISASTER VOLSR3,STKD02,00, BACKUP CBR3685I VOLUMES EXPORTED ...



Student Notebook

Figure 10-18. Library Manager Export Panel SS232.0

Notes:

After export completes, the exported stacked volumes are placed in the export hold volume category. You can use the library manager panel shown to re-import them or eject them.

Library Manager Export Panel




Figure 10-19. Import Process Flow 1 SS232.0

Notes:

We start with some volumes outside the VTS that are to be imported.

The volumes are inserted through the convenience I/O station and go into the unassigned category. This differs from a VTS without import/export.

To import, create an import list volume.

Import Process Flow 1

Insert Import Stacked Volumes via the convenience I/O station

New menu to control Insert volumesVolumes initially placed in unassigned entry categoryOperator indicates volumes as import stacked volumes through LM panelsVolume Category set to Import category (FF14)

Create a list of volumes to be importedWrite list on a logical volume in the importing VTSCan import specific logical volumes or all logical volumes from a stacked volumeCheck in tape management system the status of the volumes to be importedIf volume defined to RMM it must be known as an exported logical volume



Student Notebook

Figure 10-20. Library Manager Unassigned Volumes Panel SS232.0

Notes:

The panel shows a list of volumes that have been entered. They may be selected and moved to the insert, import or eject categories.

Library Manager Unassigned Volumes Panel





Notes:


Write the Import List Volume filesImport List file list of files to be imported optional scratch or initialize statusImport Status file VTS writes import status information

HintsStandard tape labelMust not be compactedUse IEBGENERVolser of import list volume passed to VTS when import startedEasier to automate import by using specific list volume

IEBGENER utilityImport List

Import Status

Logical

Volume



Student Notebook

Figure 10-22. Import List File SS232.0

Notes:

The import list is similar in format to the export list except that the first volume is the stacked volume serial number while the second is a specific logical volume serial number or a blank to signify all volumes on a stacked tape.

Import List File without APM

IMPORT LIST 01

STKD01,LOGCL1

STKD02,LOGCL2

STKD02,LOGCL3,SCRATCH

STKD03

.......

Importing a single Logical Volume

from stacked STKD01

Importing two Logical Volumes

from stacked STKD02

Importing all Logical Volumes

from stacked STKD03




Figure 10-23. Import List File with APM SS232.0

Notes:

Import List File with APM

IMPORT LIST 01

Allowed in APM enabled library

Volumes assigned default policies

IMPORT LIST 02

Not downward compatible

(Format and options not supported)

Rules for IMPORT lists

With Import previously IMPORT LIST 01 was

used

With APM IMPORT LIST 02 is now available

New IMPORT list



Student Notebook

Figure 10-24. Import List File with APM SS232.0

Notes:

Import List File with APM

With APM import list

IMPORT LIST 02

OPTIONS1,CREATENAME,SG=TAPESG1,SC=SCLASS1,DC=*RESET* VOL001,LOGCL1,,SG=TAPESG2,DC=DCMED

VOL002,LOGCL2,SCRATCH,SG=TAPESGX

VOL003,,,MC=COPY2

Import lvol LOGCL2

from VOL002 and

scratch the lvol + assign

storage group TAPESGX

New Import list number

LIST 02

New command line -

Sets session default

values for IMPORT

Import all logical vols

from VOL003 and

assign management

class of COPY2





Notes:

The import is the converse of an export. There are optional parameters scratch and initialize .


Start the Import OperationUsing the LIBRARY IMPORT commandUsing the CBRXLCS batch interfaceuse the SCRATCH or INITIALIZE parameters if requiredLogical Volumes to be imported are put in Import Pending category (FF15) when the Import process starts

Logical VolumesExported Stacked Volumes

TO VTS



Student Notebook


Notes:

Again, processing is the converse of export.

When the import has finished, the import stacked volumes are left in the import category. An operator must decide whether to insert them or eject them.


Wait for the IMPORT operation to completeStop the operation if needed using LIBRARY IMPORT,CANCEL commandThe IMPORT operation can be rerun at any timePreviously imported volumes not reimportedRestart point is import stacked volumeImported logical volumes are inserted into the library through standard entry processing (CBRUXENT) and assigned to a category (SCRATCH or PRIVATE)

Import Stacked Volumes are left in the libraryUse Manage Import Volumes panel to processConsider using "write protect" for containers





Notes:

The import status file gives you information about what happened. The two examples show a successful import of one logical volume (ending with return code 00) and an unsuccessful import. There were two failures in the unsuccessful import, the import tried to import a volume with a volume serial number that is already in the VTS and also tried to import from a stacked volume that had not been entered into the library.


Check the results of the IMPORT operationLook for OAM messagesCheck for status file (2) for resultsUsing RMM reports and commandsUsing ISMF panels

CBR3861I Import operation for logical list volume IMP001...

IMPORT STATUS 01

LOGCL1,STKD01,00,

IMPORT STATUS 01

LOGCL2,STKD02,13,*Duplicate volume in library

,STKD03,06,*Exported Stacked Volume not in the library



Student Notebook

Figure 10-28. Library Manager Import Panel SS232.0

Notes:

After an import completes, the stacked volumes remain in the library. This panel allows you either to eject the volumes or to insert them, when they will be used as native volumes or stacked volumes.

The volumes are not automatically ejected after you have used them.

Library Manager Import Panel




Figure 10-29. Starting Export SS232.0

Notes:

This shows the format of the export operator command. Note that you use the same command to cancel an export that is in progress.

You can also use CBRSPLCS, a sample program. You would write the three files needed to the export list volume, build the export request with that volume serial number and then pass that to CBRSPLCS.

Starting Export

Operator commandLIBRARY EXPORT,volserLIBRARY EXPORT,volser,CANCEL

Where volser specifies the export list volume containing the list of volumes to be exported

Canceling the export operation implies that you must restart with the last Exported Stacked Volume

CBRSPLCS batch sample

Write three files to export list

volume

Write command specifying export list

volume name

Issue export from

CBRSPLCS

X volser



Student Notebook

Figure 10-30. Starting Import SS232.0

Notes:

You issue an import request in exactly the same way as an export.

Starting Import

Operator commandLIBRARY IMPORT,volserLIBRARY IMPORT,volser,CANCELWhere volser specifies the import list volume containing the list of volumes to be importedCanceling the import operation implies that you must restart with the last Exported Stacked Volume

CBRSPLCS batch sample




Figure 10-31. Library Manager Cancel Panel SS232.0

Notes:

You may also cancel an import or an export from the library manager console using this panel. It shows you a list which may show two operations, one for each VTS in the library. Choose the one to cancel and then press the take action button.

Library Manager Cancel Panel



Student Notebook

Figure 10-32. OAM Messages SS232.0

Notes:

The import/export software support has changed the response to the operator commands shown.

Note that not all the changes are specific to import/export.

OAM Messages

CBR1180I Tape Volume Status DisplayD SMS,VOL(volser)LIBRARY CATEGORY field new meanings:MANEJECT volume manually removed from the libraryEXPPEND logical volume export pending in the libraryEXPORTED logical volume exported to a stacked volume

CBR1110I OAM Library Status DisplayD SMS,LIBRARY,DETAILLIB TYP heading new meaning:VL indicates that this library type is a Virtual Tape Server

CBR1100I OAM Status DisplayD SMS,OAMNew field added to the display header:TOT VL gives number of connected Virtual Tape Servers




Figure 10-33. OAM Messages SS232.0

Notes:

The Advanced Functions microcode includes the enhanced messaging function. This will send messages for:

• Operator intervention conditions

• Import status

• Export status

OAM Messages

CBR3750I MESSAGE FROM LIBRARY <libname>:<text>

Full text and explanation added to 3494 Operator's GuideMust be activated on LM "Intervention Request" Panel

Text can be OPxxx operator intervention messagesIxxxx import informationExxxx export information



Student Notebook

Figure 10-34. Display SMS,LIBRARY SS232.0

Notes:

Display SMS,LIBRARY

CBR1110I OAM library status: TAPE LIB DEVICE TOT ONL AVL TOTAL EMPTY SCRTCH ON OP LIBRARY TYP TYPE DRV DRV DRV SLOTS SLOTS VOLS ATLBA035 VL 3494-L10 16 2 2 494 13 1743 Y Y ---------------------------------------------------------------------- MEDIA SCRATCH SCRATCH TYPE COUNT THRESHOLD MEDIA1 1063 0 MEDIA2 680 0 ---------------------------------------------------------------------- OPERATIONAL STATE: AUTOMATED ERROR CATEGORY SCRATCH COUNT: 0 SCRATCH STACKED VOLUME COUNT: 79 ---------------------------------------------------------------------- Operator intervention required.Host initiated export in process. Convenience I/O station installed. Convenience I/O station in Output mode. Bulk input/output not configured.




Figure 10-35. Display SMS, LIBRARY with APM SS232.0

Notes:

Display SMS,LIBRARY with APM

CBR1110I OAM library status:TAPE LIB DEVICE TOT ONL AVL TOTAL EMPTY SCRTCH ON OPLIBRARY TYP TYPE DRV DRV DRV SLOTS SLOTS VOLSLIBVTS1 VL 3494-L10 128 100 50 1443 800 146 Y Y----------------------------------------------------------------------MEDIA SCRATCH SCRATCH SCRATCH TYPE COUNT THRESHOLD CATEGORY MEDIA1 16 25 0011 MEDIA2 130 25 0012 ----------------------------------------------------------------------OPERATIONAL STATE:AUTOMATEDERROR CATEGORY SCRATCH COUNT: 12SCRATCH STACKED VOLUME COUNT: 243PRIVATE STACKED VOLUME COUNT: 400----------------------------------------------------------------------Library supports import/export.Library supports outboard policy management.Host initiated import in process



Student Notebook

Figure 10-36. Library Manager Queues Panel SS232.0

Notes:

Library Manager Queues Panel




Figure 10-37. Tape Library Management Support SS232.0

Notes:

These tape library management systems have announced support for import/export.

Tape Library Management Support

DFSMSrmmDFSMSrmm 1.4 and upwardsVia SPE

Computer Associates CA-1CA/1 5.2 plus fixes



Student Notebook

Figure 10-38. DFSMSrmm Support 1 SS232.0

Notes:

DFSMSrmm is able to distinguish between logical and physical volumes. When exported, the logical volume record holds the container volume serial number.

DSTORE is the storage location management function in DFSMSrmm. It sets a destination for volumes to be exported according to vaulting rules.

DFSMSrmm Support 1

DFSMSrmm can distinguish between a logical or physical volume.

Default of logical type for volumes added to VTSNo need to have a rack number for logical volumes

CDS logical volume record.Container field for an exported logical volume contains stacked volser numberCleared on import

RMM DSTORE function sets the destination for the volumes to be exported.

Storage location management

RMM notified of exported/imported volumes via CBRUXEJC/CBRUXENT exits.

If a volume is not known as exported in RMM and has no TCDB entry, the ISMF Default Entry Status is used.




Figure 10-39. DFSMSrmm Support 2 SS232.0

Notes:

The DFSMSrmm movement report identifies exported stacked volumes, not logical volumes. It does not assign a bin number to these volumes.

When you use the CLIST option to store the output of a search command, extra information is provided for exported logical volumes.

DFSMSrmm Support 2

RMM utility changesEDGRPTD movement reports based on the Exported Stacked Volumes value

RMM command changesSV, AV, CV, DR commands updated for new functionsCLIST function updated for TYPE(LOGICAL) to return more information in the output file:

First six characters of the container name, The logical volume serial number, and The status value

RMM SV OWNER(*) LIMIT(*) VOLUME(*) -

TYPE(LOG) LOCATION(vtsname) -

CLIST(' ',',dest') DESTINATION(dest) INTRANSIT(N)



Student Notebook

Figure 10-40. DFSMSrmm Volume Details 1 SS232.0

Notes:

Changed items are shown in bold.

Panel Help ----------------------------------------------------------------------- EDGPT110 DFSMSrmm Volume Details - A05000 Command ===> Volume . . . . . . : LOGCL1 Rack number . . . . . . : Media name . . . . : 3490 Status . . . . . . . . . . : MASTER Volume type . . . : LOGICAL Expiration date . . . . . : 1999/017 Retention date . . : Original expiration date . : Description . . . : Data set name . . : Media type . . . . : * Release actions: Label . . . . . . : SL Return to SCRATCH pool . : YES Current version : Replace volume . . . . . : NO Required version : Return to owner . . . . : NO Density . . . . . : * Initialize volume . . . : NO Recording format . : * Erase volume . . . . . . : NO Compaction . . . . : * Notify owner . . . . . . : NO Attributes . . . . : NONE Expiry date ignore . . . : NO Availability . . . : Scratch immediate . . . : NO Owner . . . . . . : RMMUSER Owner access . . . . . . . : ALTER Assigned date . . : 1999/012 Assigned time . . . . . . : 04:44:44

DFSMSrmm Volume Details 1




Figure 10-41. DFSMSrmm Volume Details 2 SS232.0

Notes:

Changed items are shown in bold.

DFSMSrmm Volume Details 2

Actions pending: Return to SCRATCH pool . : NO Initialize volume . . . . : NO Replace volume . . . . . : NO Erase volume . . . . . . . : NO Return to owner . . . . : NO Notify owner . . . . . . . : NO Location . . . . . : SHELF Destination . . . . . . . : Location type . . : In transit . . . . . . . . : NO In container . . . : STKD01 Storage group . . : Home location . . . . . . : SHELF Required location . . . . : Move mode . . . . : AUTO Movement tracking date . . : Bin number . . . . : Media name . . . . . . . . : Old bin number . . : Media name . . . . . . . . : Product details: Product number . : Level . . . . . : Feature code . . : Enter SCROLL commands for more volume information, or END command to CANCEL.



Student Notebook

Figure 10-42. CA-1 Support SS232.0

Notes:

Please contact CA for details.

CA-1 Support

CA-1 Ver. 5.2 at level 9901 plus PTFsContact CA for information about Import/Export support

Maintains database record for container volumes and container field in volume record (ROBTY and ROBID)

Container volume uses PSEUDO data set nameNew value in ROBTY field indicates logical volume

New messages if specific mount and logical volume is exported

CTSSYNC utility to generate Import/Export list volumes




Figure 10-43. DITTO/ESA Support SS232.0

Notes:

Two new functions are provided in DITTO/ESA. You may copy logical volumes from an exported stacked cartridge to native cartridges which may then be used in any drive. You may also list the contents of an exported stacked volume.

DITTO/ESA Support

VTS Import/export support in DITTO/ESA Requires 1.2 plus APAR PQ26582

EVC exported stacked volume copyCopies up to five logical volumes to separate physical volumes (library or stand-alone)Target can be 3490 or 3590 volume (not disk)Directly from exported stacked volumeNo requirement to importOutput volser kept if present

EVL exported stacked volume listList contents of exported stacked volumeShort listing with volsersLong listing showing tape map



Student Notebook

Figure 10-44. Sample JCL for IMPORT SS232.0

Notes:

Sample JCL for IMPORT

//IMPORT JOB 1,¢ IMPORT¢ ,MSGLEVEL=(1,1)

//****************************************

//* FILE 1: IMPORT LIST FILE

//****************************************

//STEP1 EXEC PGM=IEBGENER

//SYSPRINT DD SYSOUT=*

//SYSIN DD DUMMY

//SYSUT2 DD DSN=HILEVELQ.IMPLIST,

// UNIT=VTS2,DISP=(NEW,KEEP),LABEL=(1,SL),

// VOL=(,RETAIN,,,SER=IMP001),

// DCB=(RECFM=FB,BLKSIZE=80,LRECL=80,TRTCH=NOCOMP)

//SYSUT1 DD *

IMPORT LIST 02

OPTIONS1,CREATENAME,SG=TAPESG1,SC=SCLASS1,DC=*RESET*

STKD01,LOGCL1

SVL001

SVL001,LVL001

SVL001,LVL001,SCRATCH

SVL001,,INITIALIZE

SVL001,LVL001,OPTION,SG=NAME,SC=NAME,MC=NAME,DC=*RESET*

SVL001,LOGICAL,,SG=NAME,SC=NAME,MC=NAME,DC=NAME

SVL001,,,SG=NAME,SC=*RESET*,MC=NAME,DC=NAME

SVL001,LVL001,SCRATCH,SG=NAME

SVL001,LVL001,DC=NAME,SC=NAME,MC=NAME

/*





Notes:

Unit Summary

After completing this unit, you should understand:

Import/Export removes closed store restrictionDisaster backupArchivalInterchange

Hardware and software prerequisites

Operational changesLibrary manager useChecking completion



Student Notebook




Unit 11. Data Recovery and Problem Determination


This unit discusses how the VTS handles errors, what resilience features there are to continue processing, and how errors are reported. VTS disaster recovery is also discussed.



• Understand the standard and optional features that enhance VTS availability

• Understand what symptoms a VTS can present • Understand how the VTS can notify you of errors • Plan for the use of the VTS disaster recovery function


© Copyright IBM Corp. 2001, 2002 Unit 11. Da ta Recovery and Prob lem Determination 11-1

Student Notebook


Notes:

Unit Objectives


Find VTS error notifications

Understand the causes of failure symptoms

Describe possible failures and their impact

Plan for disaster recovery




11.1 Data Recovery and Problem Determination



Student Notebook

Figure 11-2. VTS Resilience SS232.0

Notes:

The VTS has several design features specifically to give good availability. There are also some options that can improve availability.

The points of failure are shown for a VTS that is not configured in a peer-to-peer configuration. The peer-to-peer configuration removes these single points of failure.

VTS Resilience

Standard featuresRAID protected tape volume cacheTwo or four SCSI paths to 3590 drivesTwo to 16 ESCON pathsFour to twelve 3590 drives

Optional featuresDual gripperDual library manager or hard diskdual accessor and service bay

Points of failure (none for peer-to-peer)VTS controllerSSA adapters*

* Dual I/O Drawer in B20 eliminates this




Figure 11-3. IBM Support SS232.0

Notes:

It is very important to call an engineer at the first sign of a problem. Trained engineers have special tools to diagnose and fix problems.

Remote Support has always been available for dial-in to a VTS. Since late 1999, the VTS microcode has also been able to Call Home in the event of a problems. A modem is supplied with each VTS by specifying feature #2710.

IBM Support

Important to call engineersMicrocode problemsOrphan logical volumes

Special tools and techniquesVTS database repairKnowledge of microcode

Remote Support FacilityDial in to VTS via modemDiagnosis and repairCall Home to dial out

Support structureTrained engineersSpecialist engineersDevelopment



Student Notebook

Figure 11-4. Error Reporting SS232.0

Notes:

The VTS reports errors in several different ways:

• SIMs to the MVS console

• To an SNMP monitoring station

• Enhanced console messages

• Call Home

Error Reporting

Service Information MessagesMessage IEA480ESeverity

Enhanced Messaging

SNMP

Service Director

Call home

Service, Moderate, Serious, Acute




Figure 11-5. Simple Network Management Protocol SS232.0

Notes:

This is an optional function implemented by the library manager.

It requires a LAN connection with TCP/IP access to an existing monitoring station.

Optional way to monitor VTS status

Present in library manager

LAN connectivity requirementsTCP/IP access#5219 token ring card, or#5220 ethernet card

SNMP monitoring software also needed

Simple Network Management Protocol



Student Notebook

Figure 11-6. SNMP Monitoring Example SS232.0

Notes:

Two 3494s are LAN-attached to two distinct SNMP monitoring stations.

3494

RS/6000AS/400 MVS VM VSE

Customer SNMP

Monitoring Station

3494

LAN

Customer SNMP

Monitoring Station

SNMP Monitoring Example




Figure 11-7. SNMP Events SS232.0

Notes:

Four different types of event can be monitored. Use the library manager panel shown to choose which you want to see.

The following LM events can be monitoredOperator InterventionsUnsolicited Attention Messagesservice Request MessagesLibrary Manager Check1 Conditions

Not a replacement for the Remote Library Manager Feature (50xx)

SNMP Events



Student Notebook

Figure 11-8. SNMP Setup SS232.0

Notes:

You need to know the name and IP address of an SNMP monitoring station.

SNMP Setup

Add IP addresses of monitoring stationsSelect UDPEnter nameEnter address


11-10 IBM TotalStorage Virtual Tape Insta ll & Planning © Copyright IBM Corp. 2001, 2002


Figure 11-9. Enhanced Messaging SS232.0

Notes:

Enhanced messaging was introduced in 1999. Turn it on using the Library Manager Operator Intervention panel.

Enhanced Messaging

3494 library manager functionLibrary Manager microcode 521.06 or higherEnable using library manager operator intervention panel

Host console message when intervention requiredFirst 70 characters of message

Message to all hosts through all CUsOptional OAM PTFs to filter duplicate messages

CBR3750I Message from library name: name text

DFSMS/MVS 1.4 OW36342

DFSMS/MVS 1.5 OW26343



Student Notebook

Figure 11-10. Call Home SS232.0

Notes:

Call Home lets the VTS dial out if a problem is detected. This means that the time taken to fix a problem is minimized.

Call Home

Complements Service Director

Optional for serious or acute problems

Faster Service SupportProblem DetectionActivates ModemContacts IBMInitiates ActionOpen Problem Management ReportDispatch Service Representative

Supports B18 Virtual Tape ServerMagstar 3590 A60

L14 D14 D12 VTS

RISC

Modem

LM A60

Switch

3590

Remote Support Center

Retain Search

Open PMR

Service

Representative

Dispatched




Figure 11-11. VTS Unique Symptoms SS232.0

Notes:

There are two symptoms unique to a VTS:

1. Orphan logical volumes and

2. Read-only volumes

VTS Unique Symptoms

Orphan logical volumesVTS database has entry for logical volumeNo reference to physical locationCan occur after disaster recovery

Read-only volumesExcessive temporary errors on stacked volumePermanent read error



Student Notebook

Figure 11-12. Read-only Recovery SS232.0

Notes:

Automatic read-only recovery was introduced as a microcode enhancement.

The VTS now checks for volumes in read-only status each hour.

Read-only Recovery

VTS checks for read-only volumes every hourUses 3590 microcode SARS

Recovery processRead all volumes into tape volume cacheEligible to be written to other stacked volumesRead-only volume ejected

If unrecoverable read errorMessage producedSubsequent volumes skipped

Will not happen concurrently withReclaimEject




Figure 11-13. VTS Failure Impact 1 SS232.0

Notes:

This table shows the impact when different components fail.

When a peer-to-peer configuration is installed, failures that would make the VTS unavailable only result in reduced performance.

Component Action Impact

3590 drive Drive offline, repair Performance

Channel card Path unavailable, repair Performance, job failures

I/O drawer Repairno impact as there are twoin B20

SSA drive RAID protection, replace Performance

Power cord Repair no impact as there are two

VTS controller RepairVTS unavailable, peer to peer continues

VTS database Disaster recoveryVTS unavailable, peer to peer continues

VTS microcode VTS restart (worst case) Job failures

VTS Failure Impact 1



Student Notebook

Figure 11-14. VTS Failure Impact 2 SS232.0

Notes:

This table shows that failures in the library manager, accessor and gripper have reduced impact if the dual accessor feature is installed.

VTS Failure Impact 2

Component Action Impact

Library ManagerSpare takes over in HA1otherwise repair

VTS unavailable until take over or fix

AccessorSecond used in HA1 otherwise repair

Use manual mode

Gripper Use spare if dual gripper Use manual mode

Leader block Repair, reinsert then ejectCartridge unavailable until fixed

Cartridge Call engineerPossible lost data, peer to peer uses duplicate copy




Figure 11-15. VTS Disaster Recovery Overview SS232.0

Notes:

The VTS disaster recovery function is designed to allow recovery from a physical disaster where the only things that can be salvaged are cartridges.

It requires another VTS as the target for the recovery.

VTS Disaster Recovery Overview

Assumes it is not a peer-to-peer configuration

Assumes that cartridges can be salvagedMay not be all cartridges

Cannot use Disaster Recovery from EHPO to non-EHPO

Recover from stacked volumesAnother empty VTSPossibly another site

Involve engineersDetailed knowledgePrepare using force migrate if possible



Student Notebook

Figure 11-16. VTS Disaster Recovery Tasks SS232.0

Notes:

If you still have access to the VTS at the site suffering the disaster, you can use force migrate to clear the cache to tape.

At the recovery site, set up the tape infrastructure using backup copies of the tape management system catalog and the TCDB.

Disaster Recovery can be invoked from the library manager. When prompted, place the cartridges directly into the library storage locations. When disaster recovery completes, reinsert the logical volumes with the VTS online to the attached hosts. This synchronizes the TCDB, library manager database and Tape Management System inventory.

VTS Disaster Recovery Tasks

At damaged siteForce migrate if possibleRemove all stacked volumes

At recovery siteRestore TMS catalogSet up DFSMS tape catalognew TCDB or IMPORT RECONNECTInvoke Disaster Recovery from Library ManagerPlace stacked volumes in libraryReinsert logical volumesWait for synchronization of TCDB, LM database, and TMS catalog to complete




Figure 11-17. VTS Disaster Recovery Process SS232.0

Notes:

The duration of a disaster recovery depends on the number of stacked volumes, logical volumes and drives available for the recovery. It can be estimated in advance. However, it will typically take many hours.

VTS Disaster Recovery Process

Reinventory library

Find most recent database backup

Reload database and restart VTS

Add logical volumes

Upload LM inventory and sync

Recovery complete

Duration determined byStacked volsLogical volsDrives



Student Notebook


Notes:

Unit Summary

After completing this unit, you should understand that:

VTS has many resilience features

Peer-to-peer VTS provides the highest availability

Errors can be reported bySIMsEnhanced messagingSNMP

Automated recovery from read-only volumes

Disaster recovery function is available

Always involve CE early




bibl
Bibliography
• Manuals:

GA32-0279 Magstar 3494 Tape Library Introduction and Planning Guide GA32-0280 Magstar 3494 Tape Library Operator Guide GA32-0329 Magstar 3590 Tape Subsystem Introduction and Planning Guide SC26-3123 DFSMS/MVS® Implementing System Managed Storage SC26-4920 DFSMS/MVS DFSMSdfp™ Storage Administration Reference SC26-4931 DFSMS/MVS DFSMSrmm Guide and Reference SC26-3051 DFSMS/MVS OAM Planning, Installation and Storage

Administration Guide for Tape Libraries GC35-0154 IBM SCSI Tape Drive, Medium Changer and Library Device Drivers

Installation and User's Guide • Technical Bulletins:

SG24-2229 IBM Magstar Virtual Tape Server:Planning, Implementing and Monitoring

SG24-4409 Guide to Sharing and Partitioning IBM Tape Library Dataservers SG24-4632 IBM Magstar Tape Products Family:A Practical Guide SG24-2594 Magstar and IBM 3590 High Performance Tape

Subsystem:Multiplatform Implementation


© Copyright IBM Corp. 2001, 2002 Bibliography X-1

V1.2.2

backpg

Vts With Tsm

Documents

Transcript of Vts With Tsm