t l ibmtivolitape optimizer on z/os · 2016. 12. 1. · agent user’s guide (sc23-9738-nn), and...

Tivoli® IBM Tivoli Tape Optimizer on z/OS

User’s Guide

Version 2 Release 2

SC23-9735-00

��

Note:Before using this information and the product it supports, read the information in “Notices” on page 171.

This edition applies to Version 2 Release 2 of IBM Tivoli Tape Optimizer on z/OS (product number 5698–B26) and toall subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC18-9569-08.

© Copyright Rocket Software Inc., 2009

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

About this guide . . . . . . . . . . . . . . . . . . . . . . . . xiIntended audience . . . . . . . . . . . . . . . . . . . . . . . . xiPublications . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Tape Optimizer library. . . . . . . . . . . . . . . . . . . . . . xiAccessing publications online . . . . . . . . . . . . . . . . . . . xiReading CCR2 online . . . . . . . . . . . . . . . . . . . . . xiiOrdering publications . . . . . . . . . . . . . . . . . . . . . . xii

Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . xiiTerminology used in this guide . . . . . . . . . . . . . . . . . . . xiiiAccessing terminology online . . . . . . . . . . . . . . . . . . . xiiiMethods of obtaining support . . . . . . . . . . . . . . . . . . . xiiiConventions used in this guide . . . . . . . . . . . . . . . . . . . xiii

Summary of changes . . . . . . . . . . . . . . . . . . . . . . xv

Chapter 1. Tape Optimizer overview . . . . . . . . . . . . . . . . . 1What does Tape Optimizer do? . . . . . . . . . . . . . . . . . . . 1Tape Optimizer usage scenarios . . . . . . . . . . . . . . . . . . . 2Tape Optimizer features and benefits . . . . . . . . . . . . . . . . . 3

Tape Optimizer interface . . . . . . . . . . . . . . . . . . . . . 3Post-copy processing . . . . . . . . . . . . . . . . . . . . . . 3Supported tape media. . . . . . . . . . . . . . . . . . . . . . 4Mass tape-copy operations . . . . . . . . . . . . . . . . . . . . 4Manually created copy jobs . . . . . . . . . . . . . . . . . . . . 4

Copy process flow . . . . . . . . . . . . . . . . . . . . . . . . 4Required RACF privileges . . . . . . . . . . . . . . . . . . . . . 6Hardware and software prerequisites . . . . . . . . . . . . . . . . . 6

Chapter 2. Customizing Tape Optimizer . . . . . . . . . . . . . . . 7Before you begin customization . . . . . . . . . . . . . . . . . . . 7Customization steps . . . . . . . . . . . . . . . . . . . . . . . 7

Step 1: Running the customization script . . . . . . . . . . . . . . . 8Step 2: APF-authorizing the product load library . . . . . . . . . . . . 9Step 3: Ensuring that the LE routines are accessible . . . . . . . . . . 9Step 4: Creating a RACF profile for TCMEND files (optional) . . . . . . . 10

Product run-time libraries and files. . . . . . . . . . . . . . . . . . 10Manually allocating the product’s VSAM files . . . . . . . . . . . . . . 12Defining an additional Request Database . . . . . . . . . . . . . . . 12

Chapter 3. Getting started with Tape Optimizer . . . . . . . . . . . . 15About the Tape Optimizer interface . . . . . . . . . . . . . . . . . 15

Starting the Tape Optimizer interface . . . . . . . . . . . . . . . . 15Tape Optimizer Primary Menu . . . . . . . . . . . . . . . . . . 15Pull-down menus . . . . . . . . . . . . . . . . . . . . . . . 16Displaying online Help . . . . . . . . . . . . . . . . . . . . . 17

Task flow for copying tapes . . . . . . . . . . . . . . . . . . . . 17Supported wildcard characters . . . . . . . . . . . . . . . . . . . 18Default values for copy requests . . . . . . . . . . . . . . . . . . 19How to select the tapes or data sets to copy . . . . . . . . . . . . . . 19

iii

How expiration or retention dates are used in tape filtering . . . . . . . . . 22Factors affecting the release of copied tapes . . . . . . . . . . . . . . 26How Tape Optimizer selects the copy utility to use . . . . . . . . . . . . 27Strategies for optimizing performance of mass-copy operations . . . . . . . 28How SMS affects the allocation of tape drives . . . . . . . . . . . . . 28Special VTS considerations . . . . . . . . . . . . . . . . . . . . 29

Chapter 4. Setting default values for copy requests . . . . . . . . . . 31Setting defaults for general copy parameters . . . . . . . . . . . . . . 32Setting defaults for tape selection filters . . . . . . . . . . . . . . . . 38Setting defaults for stacked tape parameters . . . . . . . . . . . . . . 40Setting defaults for DFSMSrmm parameters . . . . . . . . . . . . . . 42Specifying the default DFSMSrmm control variables . . . . . . . . . . . 45Setting the copy utility to use for specific RECFM=U data sets by default . . . 47Setting default TEP options . . . . . . . . . . . . . . . . . . . . 49

Chapter 5. Defining and managing copy requests . . . . . . . . . . . 51Considerations for defining copy requests . . . . . . . . . . . . . . . 52Methods of selecting input and output tape devices . . . . . . . . . . . 53Criteria for renaming tape data sets . . . . . . . . . . . . . . . . . 53Task flow for defining a copy request . . . . . . . . . . . . . . . . . 56Defining a basic copy request based on volsers . . . . . . . . . . . . . 58Defining a basic copy request based on data set names . . . . . . . . . 61Creating a date filter . . . . . . . . . . . . . . . . . . . . . . . 65Creating a volser filter . . . . . . . . . . . . . . . . . . . . . . 68Creating a program-name filter . . . . . . . . . . . . . . . . . . . 69Creating a data-set-name filter . . . . . . . . . . . . . . . . . . . 70Creating a filter based on other tape criteria . . . . . . . . . . . . . . 72Specifying copy options for a copy request . . . . . . . . . . . . . . 75Specifying stacked tape parameters for a copy request . . . . . . . . . . 80Specifying criteria for renaming tape data sets . . . . . . . . . . . . . 82Specifying DFSMSrmm parameters for a copy request . . . . . . . . . . 84Specifying the DFSMSrmm control variables to use for a copy request . . . . 87Setting the copy utility to use for specific RECFM=U data sets . . . . . . . 89Specifying TEP options for a copy request . . . . . . . . . . . . . . . 90Editing a copy request . . . . . . . . . . . . . . . . . . . . . . 91Deleting a copy request . . . . . . . . . . . . . . . . . . . . . 93

Chapter 6. Running a copy request . . . . . . . . . . . . . . . . 95Sample copy request . . . . . . . . . . . . . . . . . . . . . . 95Performing a trial run of a copy request . . . . . . . . . . . . . . . . 97Submitting a copy request from the Tape Optimizer interface . . . . . . . . 98

Chapter 7. Verifying that tapes were copied properly . . . . . . . . . 101Return codes . . . . . . . . . . . . . . . . . . . . . . . . . 101Key log messages . . . . . . . . . . . . . . . . . . . . . . . 102Tape Selection Summary report . . . . . . . . . . . . . . . . . . 103Request Summary report. . . . . . . . . . . . . . . . . . . . . 104Reprinting the Request Summary report . . . . . . . . . . . . . . . 106Stacked Tape Summary report. . . . . . . . . . . . . . . . . . . 106Reprinting the Stacked Tape Summary report . . . . . . . . . . . . . 107Displaying summary copy statistics . . . . . . . . . . . . . . . . . 108Displaying the Tape Optimizer copy log . . . . . . . . . . . . . . . 110

Chapter 8. Stopping and restarting a copy request . . . . . . . . . . 113Stopping a copy request . . . . . . . . . . . . . . . . . . . . . 113

iv

Canceling a copy request . . . . . . . . . . . . . . . . . . . . 113Restarting a copy request . . . . . . . . . . . . . . . . . . . . 114

Chapter 9. Performing maintenance tasks . . . . . . . . . . . . . 115Releasing copied tapes to the scratch pool and updating tape status

information . . . . . . . . . . . . . . . . . . . . . . . . . 115Backing up the log file and re-creating it . . . . . . . . . . . . . . . 115Backing up the stats file and re-creating it . . . . . . . . . . . . . . 116Removing old records from the stats file . . . . . . . . . . . . . . . 116Removing records for a specific copy request from the stats file . . . . . . 116Redefining the parameters file . . . . . . . . . . . . . . . . . . . 116

Appendix A. Messages . . . . . . . . . . . . . . . . . . . . . 119

Appendix B. Manually creating JCL for a Tape Optimizer job . . . . . . 141Basic JCL for a tape-copy job . . . . . . . . . . . . . . . . . . . 141Required parameters . . . . . . . . . . . . . . . . . . . . . . 143

Volser parameters . . . . . . . . . . . . . . . . . . . . . . 143Data set name parameters . . . . . . . . . . . . . . . . . . . 144Input and output tape unit parameters . . . . . . . . . . . . . . . 145Tape library parameter . . . . . . . . . . . . . . . . . . . . 146

Optional parameters . . . . . . . . . . . . . . . . . . . . . . 146Request Database parameter . . . . . . . . . . . . . . . . . . 147Date filter parameters . . . . . . . . . . . . . . . . . . . . . 148Volser filter parameters . . . . . . . . . . . . . . . . . . . . 150Program name filter parameters . . . . . . . . . . . . . . . . . 150Data set name filter parameters . . . . . . . . . . . . . . . . . 151Other inclusion filter parameters . . . . . . . . . . . . . . . . . 151Other exclusion filter parameters . . . . . . . . . . . . . . . . . 152Data set renaming parameters. . . . . . . . . . . . . . . . . . 153Tape stacking parameters . . . . . . . . . . . . . . . . . . . 154DFSMSrmm parameters . . . . . . . . . . . . . . . . . . . . 156RECFM=U data set parameters . . . . . . . . . . . . . . . . . 158Other copy parameters . . . . . . . . . . . . . . . . . . . . 159Special use parameters . . . . . . . . . . . . . . . . . . . . 165

Parameters that should not be manually coded . . . . . . . . . . . . 165

Support for problem solving . . . . . . . . . . . . . . . . . . . 167Using IBM Support Assistant . . . . . . . . . . . . . . . . . . . 167Obtaining fixes . . . . . . . . . . . . . . . . . . . . . . . . 167Contacting IBM Software Support . . . . . . . . . . . . . . . . . 168

Determining the business impact . . . . . . . . . . . . . . . . . 168Describing problems and gathering information . . . . . . . . . . . 169Submitting problems . . . . . . . . . . . . . . . . . . . . . 169

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 172

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Contents v

Figures

1. Tape Optimizer Primary Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 162. A pull-down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173. Copy Request Defaults menu . . . . . . . . . . . . . . . . . . . . . . . . . . 324. General Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . 335. Tape Selection Filters window (for defaults) . . . . . . . . . . . . . . . . . . . . . 386. Program Filter Defaults window (for exclusion filter) . . . . . . . . . . . . . . . . . . 397. Stacked Tape Parameters window (for defaults) . . . . . . . . . . . . . . . . . . . 418. DFSMSrmm Parameters menu. . . . . . . . . . . . . . . . . . . . . . . . . . 429. Default DFSMS Parameters window. . . . . . . . . . . . . . . . . . . . . . . . 43

10. DFSMSrmm Control Variables panel . . . . . . . . . . . . . . . . . . . . . . . 4611. RECFM=U Specifications window (for defaults). . . . . . . . . . . . . . . . . . . . 4812. Default TEP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4913. Copy Requests panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5814. Create/Edit Request panel (for volsers) . . . . . . . . . . . . . . . . . . . . . . 5915. Create/Edit Request panel (for data set names) . . . . . . . . . . . . . . . . . . . 6316. Filters pull-down menu on the Create/Edit Request panel . . . . . . . . . . . . . . . . 6617. Date Filters pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . 6618. Filter Type pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . 6819. Copy Request VOLSER Filters pop-up window. . . . . . . . . . . . . . . . . . . . 6920. Copy Request Program Filters pop-up window . . . . . . . . . . . . . . . . . . . . 7021. Copy Request Data Set Name Filters pop-up window . . . . . . . . . . . . . . . . . 7222. Other Filters pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . 7323. Options pull-down menu on the Create/Edit Request panel . . . . . . . . . . . . . . . 7524. Copy Options pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . 7625. Stacked Tape Parameters pop-up window (for a copy request) . . . . . . . . . . . . . . 8126. Copy Request Data Set Rename pop-up window . . . . . . . . . . . . . . . . . . . 8327. DFSMSrmm Copy Request Parameters pop-up window . . . . . . . . . . . . . . . . 8428. RECFM=U Specifications window (for a copy request) . . . . . . . . . . . . . . . . . 9029. Request Action window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9230. Confirm Action window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9431. Tape Selection Summary report . . . . . . . . . . . . . . . . . . . . . . . . . 10432. Sample Request Summary report . . . . . . . . . . . . . . . . . . . . . . . . 10533. Sample Stacked Tape Summary report . . . . . . . . . . . . . . . . . . . . . . 10734. View VOLUME Copy Statistics panel . . . . . . . . . . . . . . . . . . . . . . . 10835. VOLUME Copy Statistics pop-up window . . . . . . . . . . . . . . . . . . . . . 10936. Sample copy log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

vii

Tables

1. Tape Optimizer usage scenarios . . . . . . . . . . . . . . . . . . . . . . . . . 22. Summary of customization steps . . . . . . . . . . . . . . . . . . . . . . . . . 73. Product run-time libraries and files . . . . . . . . . . . . . . . . . . . . . . . . 104. CNTL members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115. Task flow for copying tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . 186. Use of expiration dates for filtering under alternative scenarios . . . . . . . . . . . . . . 237. Tasks for defining a copy request . . . . . . . . . . . . . . . . . . . . . . . . . 568. Return code descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029. Key log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

10. Error message severity codes . . . . . . . . . . . . . . . . . . . . . . . . . 119

ix

About this guide

IBM® Tivoli® Tape Optimizer on z/OS® is a tape copy utility for z/OS systems withthe Data Facility System Managed Storage removable media managerDFSMSrmm™).This guide describes how to plan for, customize, and use TapeOptimizer.

Tape Optimizer can copy tape volumes and individual data sets to other tapes ortape-compatible media such as VTSs. The product supports numerous copy optionsand tape filtering criteria.

The technical changes for this edition are summarized under “Summary of changes”on page xv.

For installation instructions, refer to the Program Directory for IBM Tivoli TapeOptimizer on z/OS, which is included in the product package.

Intended audienceThis guide is intended to help storage administrators, tape managers, and tapeoperators work with Tape Optimizer.

The guide covers the following high-level tasks:

v Planning for the installation and use of Tape Optimizerv Customizing Tape Optimizer after installationv Defining and running tape-copy jobs

This guides assumes that readers have a working knowledge of:

v The z/OS operating systemv ISPFv Job Control Language (JCL)v DFSMSrmm

PublicationsThese topics identify the publications in the Tape Optimizer library and describehow to access Tivoli publications online and order Tivoli publications.

Tape Optimizer libraryThe Tape Optimizer library consists of this user’s guide (SC23-9735-nn), theMonitoring Agent Planning and Configuration Guide (SC23-9737-nn), the MonitoringAgent User’s Guide (SC23-9738-nn), and the Program Directory for IBM Tivoli TapeOptimizer on z/OS (GI11-4074-00).

Accessing publications onlineYou can access publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, from the Tivoli Information Center Website.

To access publications online:

1. Go to http://www.ibm.com/software/tivoli/library/.

xi

http://www.ibm.com/software/tivoli/library/

2. In the Tivoli Library window, click Tivoli product manuals.

3. Click the letter that matches the first letter of your product name to access yourproduct library. For example, click T to access the listing that includes the IBMTivoli Tape Optimizer on z/OS library.

4. Click the link for your product name.

Reading CCR2™ onlineIBM publishes CCR2, a useful monthly e-newsletter for the System z™ and zSeries®

software community.

You can find the latest issue of CCR2 at:

http://www-306.ibm.com/software/tivoli/features/ccr2/info.html

Ordering publicationsYou can order Tivoli publications from the IBM Web site or by telephone.

To order Tivoli publications online, go to the following Web site:

http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss

To order Tivoli publications by telephone, call one of these numbers:

v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:

1. Go to http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.

2. Select your country from the list and click Go.

3. Click About this site in the main panel to see an information page that includesthe telephone number of your local representative.

AccessibilityAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use a software product successfully.

The major accessibility features in Tape Optimizer enable users to:

v Use assistive technologies such as screen readers and screen magnifiersoftware. Consult the assistive technology documentation for specific informationwhen using it to access z/OS interfaces.

v Customize display attributes such as color, contrast, and font size.v Operate specific or equivalent features using only the keyboard. Refer to the

following publications for information about accessing ISPF interfaces:

– z/OS ISPF User’s Guide, Volume 1

– z/OS TSO/E Primer

– z/OS TSO/E User’s Guide

These guides describe how to use ISPF, including the use of keyboard shortcuts orfunction keys (PF keys). The guides provide the default settings for the PF keysand explain how to modify their functions.

xii

http://www-306.ibm.com/software/tivoli/features/ccr2/info.htmlhttp://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wsshttp://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss

Terminology used in this guideThis guide includes some terminology that is specific to Tape Optimizer.

Product-related terminology is defined in the “Glossary” on page 173 section.

Also, in this guide, the product name IBM Tivoli Tape Optimizer on z/OS isshortened to “Tape Optimizer” where the context makes the meaning clear.

Accessing terminology onlineThe definitions for many technical terms that are related to Tivoli software areavailable online in the IBM Terminology glossary.

You can access this glossary at the following Web site:

http://www-306.ibm.com/software/globalization/terminology

Methods of obtaining supportIf you have a problem with your IBM software and need assistance from IBM, youcan obtain support by using the following methods:

v IBM Support Assistant: You can search across a large collection of knownproblems and workarounds, Technotes, and other information athttp://www.ibm.com/software/support/isa.

v Obtaining fixes: You can locate the latest fixes that are available for your productonline.

v Contacting IBM Software Support: If you still cannot solve your problem andneed to work with someone from IBM, you can contact IBM Software Support ina variety of ways.

Conventions used in this guideThis guide uses several typeface and labeling conventions.

The following typeface conventions are used:

v Bold indicates user interface controls such as names of fields or menu choices.v Italics indicate parameter variables that you need to replace with a value, and

variables in messages. It is also used for book titles, new terms in text, and theemphasis of words.

v Monospace indicates examples of code, line commands, and text that you typeexactly as shown.

Additionally, the following labels are used to highlight certain types of information:

v Example: is used to identify example code or scenarios.v Restriction: is used to identify a restriction or limitation of the product.v Tip: is used to suggest an action that might simplify a task or improve some

aspect of the product.

About this guide xiii

http://www-306.ibm.com/software/globalization/terminologyhttp://www.ibm.com/software/support/isa

Summary of changes

This topic identifies the significant improvements and enhancements that have beenmade to IBM Tivoli Tape Optimizer on z/OS versions 1.1, 1.2, 2.1, and 2.2 BETA.The changes are listed for each edition of this guide, from most recent to oldest.

IBM Tivoli Tape Optimizer on z/OS 2.2

SC23–9735–00 ( BETA edition) - September 2009

v Deepens integration into Tivoli Enterprise Portal (TEP) by delivering take-actioncommands through the common user interface

v Consolidates DFSMSrmm copy calls to help reduce the total number ofDFSMSrmm calls

v Optimizes request database close calls to help reduce the number of open andclose calls per tape

v Supports tape drive-based encryption features with an option that allowsallocation of a tape drive using a user specified DATACLASS

v Allows users to pass special expiration dates, such as 99000, to systemmanaged storage (SMS) automatic class selection (ACS) routines to help drivemanagement class and vital record processing


SC23–9735–00 (tenth edition) - July 2008

v Support for Tivoli Enterprise Portal (TEP)v Improved rename masksv New filter allows selection of tapes pending replacement

In addition, Tape Optimizer on z/OS, V2.1:

v Can copy individual tape data sets by name, expiration date, catalog status, andmany other filter criteria

v Has options for renaming tape data sets during copy operationsv Includes support for 3592 tape drives and high-capacity tape mediav Includes options that continue copy processing after certain types of failures or

errors, such as tape I/O errors

v Supports relative generation data group (GDG) catalog entries to help identifygeneration data sets for a copy request

v Can edit some copy options for copy requests that have a status of pendingrestart

v Includes expiration date processing of input tapesv Delivers copy processing of dump files that were created by the ADRDSSU utility,

including the ability to create stacked tapes for these files based onbyte-threshold levels and to copy files that were created when the ADRDSSUutility was run from within another program

v Helps prevent enqueue copy tasks when you run multiple, concurrent copy tasksfor a copy request

v Delivers INCLUDE filter processing for multi-file and multi-volume tape chainsv Maintains the product log and status filesv Includes report processing and reporting for stacked tapes

xv

SC18-9560-08 (ninth edition) - October 2007

v The Test files for ADR Dump when LRECL is 0 field has been removed fromthe General Parameters panel (GTOP01A) and the Copy Options panel(GTOP02D). Tape Optimizer now automatically tests certain tape data sets todetermine if they are ADRDSSU dump files, which should be copied with theADRDSSU utility. Also, the corresponding parameterREQU_TEST_LRECL_FORADR has been deprecated. If specified, thisparameter will be ignored.

v The General Parameters panel (GTOP01A) and the Copy Options panel(GTOP02D) now include a new field named Call ADRDSSU when RECFM=Utest fails. In this field, you can indicate whether Tape Optimizer should use theADRDSSU utility or IEBGENER to copy a tape that has RECFM=U when thenormal Tape Optimizer testing of the tape cannot determine whether the tape isto be copied by ADRDSSU or not. The corresponding new parameter formanually coded copy jobs is REQU_CALL_ADRDSSU_TSTF. For moreinformation, see “Setting defaults for general copy parameters” on page 32;“Specifying copy options for a copy request” on page 75; and “Other copyparameters” on page 159.

v Two new ISPF panels (GTOP01H and GTOP02U), both named ″RECFM=USpecifications,″ have been added. On these panels, you can optionally identifythe copy utility to use for any specific RECFM=U data sets for which you expectTape Optimizer will be unable to select the copy utility automatically based on itsnormal testing. You specify default settings on the GTOP01H panel, and specifysettings for a particular copy request on the GTOP02U panel. The utility that youspecify for the data sets on these panels will override the utility that is selectedby the Call ADRDSSU when RECFM=U test fails field. The corresponding newparameters for manually coded copy jobs are REQU_FILT_ADRD_nnnn,REQU_FILT_ADRF_nnnn, and REQU_FILT_ADRV_nnnn. For more information,see “Setting the copy utility to use for specific RECFM=U data sets by default” onpage 47; “Setting the copy utility to use for specific RECFM=U data sets” onpage 89; and “RECFM=U data set parameters” on page 158.

SC18-9560-07 (eighth edition) - June 2007

v The General Parameters panel (GTOP01A) and the Copy Options panel(GTOP02D) include the new field Use Volume Expiration Date When no Dataset Expiration Date. In this field, you can indicate whether Tape Optimizershould use the expiration date of the input tape volume as the expiration date fora data set on the output tape when that data set had no data-set expiration dateon the input tape. The corresponding new parameter for manually coded copyjobs is REQU_USE_VOLEXP_IF_NODSNE. For more information, see “Settingdefaults for general copy parameters” on page 32; “Specifying copy options for acopy request” on page 75; and “Other copy parameters” on page 159.

SC18-9569-06 (seventh edition) - May 2007

v The General Parameters panel (GTOP01A) and the Copy Options panel(GTOP02D) include the new field Test files for ADR Dump when LRECL is 0.In this field, you indicate whether Tape Optimizer should test tape data sets todetermine if they are ADRDSSU dump files when the data sets have 1) a LRECLof zero or a RECFM of U and 2) a create program name other than ADRDSSU.If the test indicates that a data set is an ADR dump file, Tape Optimizer calls theADRDSSU utility to copy the data set. It is highly recommended that you enablethis test to run. The corresponding new parameter for manually coded copy jobsis REQU_TEST_LRECL_FORADR.

xvi

v Optional customization step: If you use a TVTOC to protect tape data sets, youwill probably need to define a RACF® tape-data-set profile for thehigh-level-qualifier ″TCMEND″ for Tape Optimizer to be able to generate aTCMEND control file after each tape volume that is copied to a stacked tape.

v Documentation clarification: For the Number of Days to Retain Input Tapes andApply New Expiration Date to Input Volume When Copy by Data Sets fieldsnow notes that Tape Optimizer does not calculate a new expiration date andapply it to input tapes if you also specify data-set renaming criteria for the copyrequest.

SC18-9569-05 (sixth edition) - April 2007

v The Stacked Tape Parameters panels (GTOP01D for copy request defaults andGTOP02E for a specific copy request) contain the new field Specify DefaultStacked Tape End Dataset Name Template. In this field, you define a templatefor generating the dummy data set name that Tape Optimizer records on astacked tape when either a tape media threshold or the maximum file count isreached and a new tape needs to be loaded. This data set name marks the endof a tape in a series of stacked tapes. The following new messages are relatedto this field: GTO480E and GTO481E. For more information, see “Setting defaultsfor stacked tape parameters” on page 40 and “Specifying stacked tapeparameters for a copy request” on page 80.

SC18-9569-04 (fifth edition) - September 2006

v The logic that Tape Optimizer uses to select a copy utility for a copy operationchanged. Tape Optimizer will always use the ADRDSSU backup utility to copy atape data set if the DFSMSrmm create program name is ADRDSSU, regardlessof how you set the Call ADRDSSU when Blocksize is 0 option on the GeneralParameters panel or the Copy Options panel.

v The General Parameters panel and the Copy Options panel include the newoption Enable Job Restart. If you select this option, Tape Optimizer locks theRequest Database when a copy job terminates abnormally so that you canrestart the job later from the point at which it abended. If you clear this option,Tape Optimizer will not lock the Request Database. As a result, you will not beable to restart the copy job. However, the Request Database will be available foruse by another copy job. The corresponding new parameter for manually codedcopy jobs is REQU_JOB_RESTARTABLE. For more information, see “Settingdefaults for general copy parameters” on page 32; “Specifying copy options for acopy request” on page 75; and “Other copy parameters” on page 159.

v The General Parameters panel includes the new field Number of Seconds toRetry Allocation. In this field, you can specify the maximum number of secondsthat Tape Optimizer should retry allocating input tape units for a copy requestwhen the initial allocation attempt fails. Valid values are from 0 through 9999. Thedefault value is 0, which causes Tape Optimizer to make no retry attempts. Thecorresponding new parameter for manually coded copy jobs isREQU_ALLOC_WAIT_SECS. For more information, see “Setting defaults forgeneral copy parameters” on page 32 and “Other copy parameters” on page 159.

v If you use generation data groups (GDGs), you can now specify a generationdata set name with a relative generation number when you create a copy requestbased on data set names or when you define a data-set-name filter. For moreinformation, see “Defining a basic copy request based on data set names” onpage 61 and “Creating a data-set-name filter” on page 70.

v You can now include a special percent sign (%) wildcard in criteria for renamingtape data sets as they are copied. This wildcard enables you to append a value

Summary of changes xvii

to existing data set names to generate new data set names. For moreinformation, see “Criteria for renaming tape data sets” on page 53.

v If you select the Perform unit name validity check option on the GeneralParameters panel, Tape Optimizer will display the new Invalid Unit Name windowwhenever you specify an invalid input or output unit name on the GeneralParameters panel or the Create/Edit Request panel. From this window, you candirect Tape Optimizer to accept an invalid name if your SMS routines caninterpret the name or if you intend to run the copy request on a processor wherethe name is valid. For more information, see “Setting defaults for general copyparameters” on page 32 and “Defining a basic copy request based on volsers” onpage 58.

v A new report, called the Tape Selection Summary, lists the tapes and data setsthat Tape Optimizer selects for copying based on the selection criteria that youspecify in the basic copy request and any filters that you define. This report isgenerated when you perform a trial run or the actual run of a copy job. If thereport is generated during a trial run, you can use it to check that the correcttapes and data sets will be copied when you actually run the copy job. For moreinformation, see “Tape Selection Summary report” on page 103.

v The following additional messages are documented: GTO004I, GTO216I,GTO250E, GTO363I, GTO435E, GTO437I, GTO438E, GTO439E, GTO440E,GTO441E, GTO442E, GTO443E, GTO444E, GTO445E, GTO446E, GTO447E,GTO448E, GTO449E, GTO450I, GTO451I, GTO452I, GTO453E, GTO454E,GTO455I, GTO456I, GTO457W, GTO458E, GTO459E, GTO460I, and GTO470E.


SC18-9569-03 (fourth edition) - March 2006

v Tape Optimizer provides improved support for IBM 3592 tape drives andhigh-capacity tape media, such as Write Once Read Many (WORM) media. Youcan now use tapes that have the enterprise recording format EFMT1 or EFMT2and a type of MEDIA5. The following new options and parameters are provided:

– The General Parameters panel and the Copy Options panel include the newoption Use Exact Data Set Name for Tape Unit Allocation. If you select thisoption, Tape Optimizer uses the exact name of the first data set that isselected for copying when allocating an output tape drive. If you specifieddata-set renaming criteria, Tape Optimizer uses the name that is generated forthe first output data set. For SMS-managed data sets, this feature enablesyour ACS routines to determine that a 3592 tape drive with high-capacitymedia is needed. The corresponding parameter for manually coded copy jobsis REQU_USE_EXACT_TDSN. For more information, see “Setting defaults forgeneral copy parameters” on page 32; “Specifying copy options for a copyrequest” on page 75; and “Other copy parameters” on page 159.

– The Stacked Tape Parameters panels (for defaults and for a specific copyrequest) provide two new options, EFMT1 and EFMT2, for setting themaximum threshold utilization levels (in MBs) for tapes that have the EFMT1or EFMT1 format. The corresponding parameters for manually coded copyjobs are REQU_EFMT1_THRESHOLD and REQU_EFMT2_THRESHOLD.For more information, see “Setting defaults for stacked tape parameters” onpage 40 and “Specifying stacked tape parameters for a copy request” on page80.

v Documentation clarification: Tape Optimizer does not support copying data fromtapes that are managed by hierarchical storage management (HSM).

v Documentation clarification: If you select the Copy Tape without Recatalogoption, Tape Optimizer ignores the following catalog-related options if selected:

xviii

Continue When Invalid Catalog Entries Found and Use FSEQ for CatalogMatches when DSSEQ Match Fails. Similarly, if you set theREQU_NO_RECATALOG parameter to Y in a manually created copy job, TapeOptimizer ignores the REQU_CONT_WHEN_INV_CATENT andREQU_USE_FSEQ_FOR_CAT parameters if specified.

v Documentation clarification: The REQU_TLIB_TYPE parameter must be includedin manually created tape-copy jobs. For more information, see “Tape libraryparameter” on page 146.

SC18-9569-02 (third edition) - January 2006

v Additional information about restarting a copy request has been added. For moreinformation, see “Restarting a copy request” on page 114.

v Clarified that if you manually allocate the Tape Optimizer VSAM files, you mustedit the FILEDEFS file to point to the correct file names. For more information,see “Manually allocating the product’s VSAM files” on page 12.

v The General Parameters panel and the Copy Options panel include a new fieldnamed Call ADRDSSU when Blocksize is 0. This field enables you to specifythe situations in which Tape Optimizer calls the ADRDSSU utility (rather thanIEBGENER) to copy a tape data set. A corresponding new batch job parameter isavailable: REQU_CALL_ADRDSSU_BLK0. For more information, see“Settingdefaults for general copy parameters” on page 32; “Specifying copy options for acopy request” on page 75; and “Other copy parameters” on page 159.

SC18-9569-01 (second edition) - November 2005

v Tape Optimizer can now copy individual data sets from input tapes and stackthem together onto output tapes. This copy strategy is an alternative to copyingthe entire tape chains that contain the data sets. The Create/Edit Request panelfor data sets now includes VOLSER and DSSEQ columns in support of thisfeature. For more information, see “Defining a basic copy request based on dataset names” on page 61.

v The Dates Filters panel includes a new field named Tapes/Data Sets ThatExpire After for including tapes or data sets in a copy request that expire after aparticular date. The pre-existing exclusion option Exclude tapes that expirebefore was renamed Tapes/Data Sets That Expire Before. For moreinformation, see “How expiration or retention dates are used in tape filtering” onpage 22 and “Creating a date filter” on page 65.

v The Other Filters panel includes a new inclusion option named Cataloged DataSets. You can use this option to include only the data sets that are in the systemcatalog in a copy request. For more information, see “Creating a filter based onother tape criteria” on page 72.

v The General Parameters panel now includes the following new options forspecifying default values for copy requests:

– Number of Copy Log Entries

– Number of Seconds to Retry Re-Allocation

– Continue Copy Following a Copy Utility Failure

– Continue When Invalid Catalog Entries Found

– Use FSEQ for Catalog Matches When DSSEQ Match Fails

Also, the pre-existing option Do Not Use Assign/Create Date for Data SetSearches was moved to this panel from the Copy Options panel. The defaultvalues for the Number of Days to Retain Input Tapes field and the Performunit name validity check field have changed.

Summary of changes xix

For information about all of these options, see “Setting defaults for general copyparameters” on page 32.

v The Copy Options panel now includes the following new options:– Continue Copy Following a Copy Utility Failure

– Apply New Expiration Date to Input Volume When Copy by Data Sets

– Print Summary Statistics Reports

– Continue When Invalid Catalog Entries Found

– Use FSEQ for Catalog Matches When DSSEQ Match Fails

For more information about these options, see “Specifying copy options for acopy request” on page 75.

Also, the options Do Not Use Assign/Create Date for Data Set Searches andPerform Unit Name Validity Check were removed from this panel. They nowappear on the General Parameters panel only.

v The Default DFSMSrmm Parameters panel and the DFSMSrmm Copy RequestParameters panel now include the following new options:

– Use Volume Expiration Date When a Volume Is Retained and No Data-SetExpiration Date or Retention Date Exists

– Use Old Data-Set Retention Date When No Data-Set Expiration DateExists

– Continue After RMM Variable Copy Failure

For descriptions of these options, see “Setting defaults for DFSMSrmmparameters” on page 42 and “Specifying DFSMSrmm parameters for a copyrequest” on page 84.

v You can now perform limited editing of copy requests that have the statusACTIVE or PEND RSTRT if these requests have actually terminated.

v Manually created copy jobs now include a GTOUTRPT DD statement forindicating the destination for the summary report output for the copy job. Formore information, see “Basic JCL for a tape-copy job” on page 141.

v You can now specify the following new parameters when manually creating theJCL for a copy job:

– REQU_CONT_COPY_AFTER_FAIL

– REQU_CONT_WHEN_INV_CATENT

– REQU_COPY_ONLY_CATALOGED

– REQU_DFRM_CONT_VARCOPYFAIL

– REQU_EXPR_DATE_INC

– REQU_EXPIRE_COPY_BY_DATASET

– REQU_PRINT_STATS_REPORTS

– REQU_TABLE_BY_DSNVOL_nnnn

– REQU_TABLE_BY_DSNDSQ_nnnn

– REQU_USE_DSRET_AS_DSNEXP

– REQU_USE_EXP_WHEN_DSNOTRET

– REQU_USE_FSEQ_FOR_CAT

For descriptions of these parameters, see Appendix B, “Manually creating JCL fora Tape Optimizer job,” on page 141.

v The following new messages, which are related to the new copy parameters,might be issued: GTO404W through GTO433W, GTO700E through GTO704W,GTO710E, GTO750I, and GTO755I. These messages are described inAppendix A, “Messages,” on page 119.

xx

v The runtime_HLQ.CNTL library contains two new members that contain sampleJCL for removing records from the stats file: GTOSTDEL and GTOSTREO. Also,the runtime_HLQ.CNTL library member GTOUTIL was renamed GTOUTILR todistinguish it from the member by the same name in the runtime_HLQ.LOADlibrary. For more information, see “Product run-time libraries and files” on page10.

Summary of changes xxi

Chapter 1. Tape Optimizer overview

IBM Tivoli Tape Optimizer on z/OS copies information from one or more tapevolumes to other tapes or tape-compatible media in a single batch job, called acopy request.

The product can work with any source or target media that is capable of storingphysical or logical tape volumes. It can copy most tape data sets; however, itcannot copy some data sets that are in a proprietary format such as HSM and FDR.

Besides copying the tape data, Tape Optimizer automatically applies the DataFacility System Managed Storage removable media manager (DFSMSrmm) tapelibrary information to the output tape definitions to preserve this information. TapeOptimizer also updates the system catalog to identify the new locations of thecopied tape data sets.

Review the following introductory topics to learn more about the product.

Topics:

v “What does Tape Optimizer do?”v “Tape Optimizer usage scenarios” on page 2v “Tape Optimizer features and benefits” on page 3v “Copy process flow” on page 4v “Required RACF privileges” on page 6v “Hardware and software prerequisites” on page 6

What does Tape Optimizer do?Tape Optimizer is a robust tape-copy utility. It can efficiently copy a multitude oftape volumes or data sets in a single copy request. Also, it provides many copyoptions for tailoring copy requests and releasing copied tapes.

The following list summarizes key product features:

v Copies data sets individually, or copies entire tape chains that include the tapevolumes or data sets that you specify

v Works with all tape media and tape devices that are compatible with your IBMsystem, including VTSs

v Runs up to 10 copy tasks concurrently for a single copy job to help you copytape volumes or data sets much more quickly

v Provides an ISPF interface with online Help for configuring and submitting copyrequests

v Enables you to define a variety of filters to specify precisely the input tapes ordata sets to copy

v Optionally stacks tape volumes or data sets on output tapes to reduce thenumber of tapes that need to be stored and maintained

v Optionally renames tape data sets as they are copied based on the renamingcriteria that you specify

v Generates a detailed copy log, online copy statistics by tape volume, and threesummary reports (the Tape Selection Summary report, Request Summary report,and Stacked Tape Summary report) for each copy request

1

v Applies the DFSMSrmm tape library information for the input tapes to the outputtape definitions to preserve this information

v Updates the system catalog information for the copied tape data sets to reflecttheir new tape locations

v Enables you to perform a trial run of a copy job to ensure that the correct tapevolumes or data sets will be copied

v Enables you to restart copy requests from the appropriate point

Tape Optimizer usage scenariosTape Optimizer is a versatile product that you can use in a variety of situations.

The following table describes several usage scenarios:

Table 1. Tape Optimizer usage scenarios

Task Use Frequency/user type

Migrate data from existingtapes to new tapes

v To prevent data loss due to thedegradation of old tapes

v To stack data on high-density tapesto reduce the number of tapes tostore and manage

v To release source tapes to thescratch pool for reuse

v To consolidate a file that spansmultiple tapes onto one tape

v To back up a particular data setv To move data to more durable tape

media

Routine task for tapemanagers andoperators

Migrate data from a VTSor ATL to other media

v To copy data that you do not expectto use in the near future to tapes foroffsite vaulting

v To clear volumes from a VTS or anautomated tape library (ATL) becauseit is becoming full

v To migrate data to less expensivetape media

Frequent task forstorageadministrators, tapemanagers, and tapeoperators

Migrate data from tapesto a VTS

v To load a new VTS with data fromtapes

v To reduce the number of tapes, tapedevices, floorspace, and tapeoperators that are needed

v To improve the availability of tapedata that is frequently used

Occasional task forstorage administratorsand tape managers

Migrate data betweenVTSs

v To upgrade to a new VTS that offershigher performance and greatercapacity

v To create a remote peer VTS fordisaster recovery

v To consolidate data that resides inmultiple VTSs onto one VTS

Infrequent task forstorage administratorsand tape managers

2

Tape Optimizer features and benefitsTape Optimizer provides many useful features for copying tapes and tape data sets.Learn about the major features that Tape Optimizer provides and the benefits thatyou can gain from using them.

Tape Optimizer interfaceTape Optimizer provides an ISPF interface from which you can define and submitcopy requests, perform a trial run of a copy request, and view the results of copyrequests that ran. The interface includes numerous copy options that you can useto tailor your copy requests.

When you define a specific copy request, you must identify the input tape volumesto copy by specifying either volser values or tape data set names. You must alsospecify the input and output tape drives to use. You can then refine the set of inputtape volumes or data sets by specifying a variety of optional filtering criteria, forexample, tape-creation dates and the names of programs that created tape datasets. By creating a combination of filters, you can identify precisely the tapevolumes or data sets to copy.

Tape Optimizer also provides copy options for controlling how the copy request isprocessed and how the tape media is handled. For example, you can specify thenumber of days to retain input tapes and whether to stack data on output tapes.

To save time in configuring copy requests, you can specify default values for manycopy options. If necessary, you can override these default values when defining aspecific copy request.

When you finish defining a copy request, Tape Optimizer generates the JCL for thecopy job and displays it for your review. If you are satisfied with the JCL, you cansubmit it for execution directly from the interface.

After a copy request runs, you can display the copy log and summary copystatistics by volume from the ISPF interface. You can also review the summaryreports that Tape Optimizer provides with the job output.

For more information about the Tape Optimizer interface, see Chapter 3, “Gettingstarted with Tape Optimizer,” on page 15.

Post-copy processingAfter Tape Optimizer copies the data on tapes, it automatically performs somepost-copy processing.

During post-copy processing, Tape Optimizer performs these tasks:

v Applies the tape library information for the input tapes to the output tapedefinitions to preserve this information. You can control which information isapplied by selecting DFSMSrmm control variables from the Tape Optimizerinterface.

v Recatalogs the tape data sets to point to their new locations.v Releases the copied input tapes to the scratch pool for reuse as soon as their

expiration dates are reached, provided that VRS retention criteria do not hold thetapes from release. For more information about the release of copied tapes, see“Factors affecting the release of copied tapes” on page 26.

Chapter 1. Tape Optimizer overview 3

Supported tape mediaTape Optimizer enables you to use any media that is capable of storing physical orlogical tape volumes and that is recognized as tape media by your IBM system asthe input or output tape media for copy jobs.

Supported media types include reel tapes (IBM 3420), cartridge tapes (IBM 3480,3490, 3492, 3590, or 3592), and logical tape volumes in a VTS. Tape Optimizer cancopy single- or multi-volume tapes, tapes with standard labels, unlabeled tapes, andtapes that contain either cataloged or uncataloged data sets.

Restriction: Tape Optimizer does not support copying data from HSM-managedtapes.

Mass tape-copy operationsA key feature of Tape Optimizer is its ability to copy numerous tapes in a singlecopy job. The product imposes no limit on the number of tapes that can be copiedper job.

This feature can provide the following benefits to your enterprise:

v Reduce the impact of copy operations on system performance and availability.Only one copy job is written to the JES queue, initiated, and scanned forcompletion status.

v Reduce the workload for tape operators and the related personnel costs.v Make recovery from a failed tape-copy operation easier. You restart just one copy

job to resume copy processing from the appropriate point.

Also, with Tape Optimizer, you can run multiple subtasks for a single copy job toaccommodate large copy operations. For more information, see “Strategies foroptimizing performance of mass-copy operations” on page 28.

Manually created copy jobsYou can manually create the JCL for copy jobs instead of generating it from theTape Optimizer ISPF interface, if necessary. You might want to manually define acopy job so that you can save it to a file and run it on a routine basis as part of abatch job.

To manually create a copy job, review the syntax of the required basic JCLstatements and of the required and optional parameters under Appendix B,“Manually creating JCL for a Tape Optimizer job,” on page 141.

Rather than define the copy job from scratch, it is recommended that you firstdefine and generate the copy job from the Tape Optimizer ISPF interface tominimize syntax errors. The interface will validate many of your entries, generatethe JCL, and display online Help upon request. You can then use the generatedJCL as a template; just edit the generated JCL, as needed, and save it to a file.

Copy process flowThis process flow indicates how a Tape Optimizer copy request is defined andprocessed.

4

1. A user defines a copy request from the Tape Optimizer interface. The basiccopy request specifies the tape volsers or data sets to be copied and the inputand output tape units to use. The user can also specify optional filtering criteriaand copy options.

This information is saved to a parameters file. The default name of this file isruntime_HLQ.PARMS, where runtime_HLQ is the high-level qualifier that wasspecified during customization.

Tip: When defining a copy request, the user can select an option to perform asimulated run of the copy job. By performing a simulated run, the user cancheck that all of the specified tape or data set selection criteria and filters willresult in the expected set of tape volumes or data sets being copied.

2. When the user exits the copy request, Tape Optimizer generates and displaysthe JCL for the copy job. The JCL includes any copy parameters that the userset and the copy request number that Tape Optimizer automatically generatesfor the request.

3. The user reviews the JCL.

4. The user submits the copy job to JES for execution.

5. Tape Optimizer temporarily acquires a lock on the Request Database (a VSAMfile) that the copy request uses. This file contains information about the tapevolumes to be copied. Its primary purpose is for restarting the copy request, ifnecessary. The file remains locked until the copy request finishes or until theuser deletes the copy request from the Tape Optimizer interface.

6. Tape Optimizer determines the tapes or series of tapes (called tape chains)that need to be mounted based on the copy parameters and filters that theuser specified for the copy request.

7. The copy job performs the following actions, in the order shown:

a. Copies all of the tape chains or data sets that were selected for copying. Ifthe user specified renaming criteria for the copy request, the tape data setsare renamed during the copy operation.

b. Applies the DFSMSrmm tape library information for the copied tapes to theoutput tape definitions.

c. Recatalogs the copied tape data sets to reflect their new locations.

d. Writes detailed information about the copy job to the Tape Optimizer logfile. The default name of this file is runtime_HLQ.MSGLOG, whereruntime_HLQ is the high-level qualifier that was specified duringcustomization.

e. Records summary copy statistics for the tape volumes in the stats file. Thedefault name of this file is runtime_HLQ.STATS.

The user can monitor the copy job from SDSF.

8. When the copy job finishes, Tape Optimizer releases the lock on the RequestDatabase file so that it can be reused for another copy request.

9. The user verifies that all of the selected tape volumes were copied properly.The user can review the job output and summary reports from SDSF or anequivalent tool and can review the copy log and summary copy statistics fromthe Tape Optimizer interface.

10. Tape Optimizer will release the copied tapes to the scratch pool for reusebased on their expiration dates (their original or new expiration dates,depending on how you configured expiration criteria). If any tapes are held byVRS retention criteria unnecessarily, the user can run a job that TapeOptimizer supplies to release the tapes immediately.

Chapter 1. Tape Optimizer overview 5

Required RACF privilegesTo customize the product and run tape copy requests, your TSO user ID must havecertain RACF privileges, which are typically granted to tape librarians.

These privileges are:

v CONTROL access to STGADMIN.EDG.LISTCONTROLv CONTROL access to STGADMIN.EDG.MASTERv CONTROL access to STGADMIN.EDG.VRSv UPDATE access to STGADMIN.EDG.OPERATORv UPDATE access to STGADMIN.EDG.FORCE

You do not need any special privileges to use the Tape Optimizer interface toconfigure copy requests and to view the copy log or summary statistics.

Hardware and software prerequisitesBefore you install Tape Optimizer, ensure that your system meets these hardwareand software prerequisites.

Hardware prerequisites

You must have a computer that is capable of running the required software.

Also, make sure that you have tape devices that are appropriate for reading datafrom your input tapes and for writing data to your output tapes. Tape Optimizerworks with any tape device that the operating system recognizes, including IBM3420, 3480, 3490, 3590, and 3592 tape drives. The tape drives can be stand-aloneunits or units in a system-managed automatic tape library (ATL) or VTS. TapeOptimizer can also work with tape devices such as tape stackers and autoloaders.

Software prerequisites

You must have the following software to use Tape Optimizer:

v z/OS operating system V1R7 or laterv Any version of TSO/E and ISPF that the operating system supportsv Any version of DFSMSrmm that the operating system supportsv JES2 or JES3

6

Chapter 2. Customizing Tape Optimizer

After you install Tape Optimizer, you must complete several customization stepsbefore you can use the product to copy tapes.

Tape Optimizer provides a customization script to simplify the customizationprocess. The script allocates the runtime libraries based on the SMP/E targetlibraries from installation. The script also performs some basic editing andunpacking tasks. For example, it adds a high-level qualifier that you specify to thesample JCL files, wherever needed. Optionally, the script automatically allocates theproduct’s VSAM files (the log file, parameters file, stats file, and Request Databasefile). This practice is recommended. However, you can manually define these files, ifyou prefer; sample JCL is provided for this purpose. Also, if you plan to run multipleTape Optimizer instances, you will need to define a Request Database file for eachone.

For installation instructions, see the IBM Program Directory for IBM Tivoli TapeOptimizer on z/OS.

Topics:

v “Before you begin customization”v “Customization steps”v “Product run-time libraries and files” on page 10v “Manually allocating the product’s VSAM files” on page 12v “Defining an additional Request Database” on page 12

Before you begin customizationBefore you begin customization, ensure that your TSO user ID has the RACFprivileges that are required for customization.

These privileges are:

v CONTROL access to STGADMIN.EDG.LISTCONTROLv CONTROL access to STGADMIN.EDG.MASTERv CONTROL access to STGADMIN.EDG.VRSv UPDATE access to STGADMIN.EDG.OPERATORv UPDATE access to STGADMIN.EDG.FORCE

Customization stepsYou must complete several customization steps to tailor Tape Optimizer for yourenvironment. You will not be able to use Tape Optimizer until you do so.

The following list summarizes the required and optional customization steps.

Table 2. Summary of customization steps

Step Required or optional

“Step 1: Running the customization script” on page 8 Required

“Step 2: APF-authorizing the product load library” on page 9 Required

“Step 3: Ensuring that the LE routines are accessible” on page 9 Required

7

Table 2. Summary of customization steps (continued)

Step Required or optional

“Step 4: Creating a RACF profile for TCMEND files (optional)” onpage 10

Optional

You also might need to perform these additional tasks:

v If you did not generate the VSAM files that the product requires when running thecustomization script, you will need to create these files manually. See “Manuallyallocating the product’s VSAM files” on page 12.

v If you are implementing multiple instances of Tape Optimizer, you will need todefine a Request Database file for each one. See “Defining an additionalRequest Database” on page 12.

Step 1: Running the customization scriptRun the customization script to allocate the product libraries and VSAM files and toperform basic editing tasks. This customization step is required.

1. From the ISPF command shell (ISPF Option 6), run the GTOINST EXEC that isin the SGTOEXEC target library by specifying the following statement:EXEC 'target_HLQ.SGTOEXEC(GTOINST)' 'runtime_HLQ target_HLQ'

where target_HLQ is the high-level qualifier that you specified at installation forthe SMP/E target libraries and runtime_HLQ is the high-level qualifier that youwant to use for the run-time libraries. For example, you could use userid.GTOas the runtime_HLQ.

While the script is running, informational messages regarding the progress ofthe customization process are displayed. When the script finishes, the defaultnames of the product run-time data sets are listed.

2. At the prompt Are these names OK?, indicate whether you want to accept thedefault names of the product run-time data sets, as follows:

v Type Y (for Yes) if you want to accept the default names (recommended).v Type N (for No) if you want to specify other names. Tape Optimizer will

prompt you to edit the customization script.

3. If Tape Optimizer prompts you to edit the customization script (because youspecified N in step 2), perform these substeps:

a. Exit customization.

b. Edit the following portion of the customization script. In the left column,replace the default names for the product run-time libraries and files with thenames that you want to use. Ensure that your values are enclosed in doublequotation marks.

Tip: To perform this task, you should be familiar with the REXXprogramming language./* >>>>>>>>>>>>>>>>>>>> note

execnam = "EXEC" /* Rexx EXECS */fildnam = "FILEDEFS" /* File Definition */rmmvnam = "RMMVARS" /* RMM MetaData */

c. Save your changes. Your new names will be used as the last qualifier of therun-time data set names.

d. Restart the customization script.

4. At the prompt OK to delete product files?, indicate whether you want thecustomization script to delete files from a previous installation of the product (forexample, files for a previous product version), as follows:

v Type Y (for Yes) if you want the customization script to delete the files from aprevious product installation and then continue.

v Type N (for No) if you want the customization script to terminate so that youcan back up or rename the files from a previous product installation. After youback up or rename the files, you will need to restart the customization script.

5. At the prompt Do you want to allocate the product VSAM files from thescript (Y) or from batch (N)?, indicate how you want the VSAM files that theproduct uses to be allocated:

v Type Y to have the customization script automatically allocate the VSAM filesby using the system defaults. (recommended)

v Type N to prevent the VSAM files from being automatically allocated and toend the customization script. You will need to manually allocate the VSAMfiles by running the JCL in the GTOVSAM member of the runtime_HLQ.CNTLlibrary. (For more information, see “Manually allocating the product’s VSAMfiles” on page 12.) You might want to choose this option if you need toallocate the files by means of a batch job or customize how the files areallocated in some way.

Step 2: APF-authorizing the product load libraryTape Optimizer requires that the run-time load library (runtime_HLQ.LOAD) beauthorized by the z/OS Authorized Program Facility (APF). You must include thisload library in your system APF-authorized list. This customization step is required.

If you need assistance, contact your system administrator or security administrator.

Step 3: Ensuring that the LE routines are accessibleTape Optimizer requires access to the z/OS LE (Language Environment) run-timeroutines. Usually, these routines are included in the system LINK LIST and areavailable to all programs. If they are not in the LINK LIST on your system, you mustensure that Tape Optimizer can access them by completing this procedure.

Note that the LE routines reside in the prefix.SCEERUN and prefix.SCEERUN2libraries, where prefix can be the default prefix ″CEE″ or another prefix that thesystem programmer specified for these libraries.

1. Add prefix.SCEERUN and prefix.SCEERUN2 to the TSO logon proc STEPLIBthat is used by the user ID under which the Tape Optimizer interface will run.

2. Add prefix.SCEERUN and prefix.SCEERUN2 to the STEPLIB DD in the TapeOptimizer run-time member runtime_HLQ.ISPSLIB(GTOSCOPY), whichcontains JCL skeletons for Tape Optimizer use. For example://COPY1 EXEC PGM=GTOCOPY,REGION=20M//STEPLIB DD DSN=PDUSER.GTO.LOAD,DISP=SHR// DD DSN=CEE.SCEERUN,DISP=SHR// DD DSN=CEE.SCEERUN2,DISP=SHR//FILEDEFS DD DSN=PDUSER.GTO.FILEDEFS,DISP=SHR//GTOUTRPT DD SYSOUT=*,DCB=(BLKSIZE=133,LRECL=133,RECFM=FBA),

Chapter 2. Customizing Tape Optimizer 9

// SPIN=UNALLOC//SYSUDUMP DD SYSOUT=*//CEEDUMP DD SYSOUT=*...

Step 4: Creating a RACF profile for TCMEND files (optional)If your RACF configuration uses a tape-volume table of contents (TVTOC) toprotect tape data sets, you will probably need to define a RACF tape-data-setprofile for the high-level-qualifier ″TCMEND″ to enable Tape Optimizer to create andcopy the TCMEND files.

Tape Optimizer writes a ″TCMEND″ control file after each tape volume that iscopied to a stacked tape to indicate the end of the tape volume. A TCMEND fileseparates one tape volume from another on a stacked tape. These control files areuniquely named TCMEND.Dnnn, where nnn is a number.

If you use a TVTOC to protect tape data sets, define a RACF tape-data-set profilefor the high-level-qualifier ″TCMEND.″ If you do not do so, the message IEC150Iwill be issued during tape copy operations that use tape stacking.

Product run-time libraries and filesThis topic describes the Tape Optimizer run-time libraries that should exist on yoursystem at the completion of customization.

The following table shows the default names for these libraries and files. If youspecified other names during customization, the libraries and files will have thosenames instead. The only library that you should need to access isruntime_HLQ.CNTL.

Table 3. Product run-time libraries and files

Library/File Description

runtime_HLQ.CNTL A library that contains sample JCL and the Tape Optimizertape-maintenance utility.

runtime_HLQ.EXEC A library that contains the REXX EXECs that invoke thecustomization script and the Tape Optimizer interface.

runtime_HLQ.FILEDEFS A file that defines Tape Optimizer file names and locations.It is used for finding the product’s files. If you chose toallocate the VSAM files from batch (that is, you specified″N″ at step 5 of running the customization script), you mustedit the FILEDEFS file to specify the names of the VSAMfiles that you manually defined.

runtime_HLQ.ISPMLIB A library that contains Tape Optimizer ISPF messages.

runtime_HLQ.ISPPLIB A library that contains the Tape Optimizer ISPF panels.

runtime_HLQ.ISPSLIB A library that contains JCL skeletons that Tape Optimizeruses to build copy jobs.

runtime_HLQ.JOBLIB A library that contains the JCL for the copy requests thatyou create from the Tape Optimizer interface.

runtime_HLQ.LOAD A library that contains the Tape Optimizer programs.

runtime_HLQ.MSGLOG A VSAM log file that contains saved Tape Optimizermessages.

runtime_HLQ.PARMS A VSAM file that contains the parameters and options thatyou set for copy requests.

10

Table 3. Product run-time libraries and files (continued)

Library/File Description

runtime_HLQ.RMMVARS A file that defines all of the DFSMSrmm control variables(or structured fields) to Tape Optimizer.

runtime_HLQ.RQDBnn A VSAM file, known as the Request Database, that storesinformation about the tape volumes or data sets to becopied for each copy request. Each instance of TapeOptimizer must have its own Request Database file. If youplan to run multiple instances of Tape Optimizer, you mustdefine a Request Database file for each one. The firstRequest database is named runtime_HLQ.RQDB00. Formore information, see “Defining an additional RequestDatabase” on page 12.

runtime_HLQ.STATS A VSAM file that stores saved tape-copy statistics.

The following table describes the contents of the runtime_HLQ.CNTL library in moredetail. You will need to use the sample JCL and maintenance utility in this libraryoccasionally.

Table 4. CNTL members

Member Description

GTODEFML Sample JCL for saving the contents of the existing messageslog file to a sequential file and creating a new log file. You willneed to use this JCL occasionally, when the log file becomestoo large. For more information, see “Backing up the log fileand re-creating it” on page 115.

GTODEFPM Sample JCL for deleting the existing Tape Optimizerparameters file and redefining it. Usually, you do not need touse this JCL. However, if an error occurs, the error messageor IBM Software Support might direct you to redefine thePARMS file by using this JCL. For more information, see“Redefining the parameters file” on page 116.

GTODEFRQ Sample JCL for defining additional Request Database files.For more information, see “Defining an additional RequestDatabase” on page 12.

GTODEFST Sample JCL for saving the contents of the existing TapeOptimizer stats file to a sequential file and creating a newstats file. Normally, you do not need to run this JCL. Youwould run this JCL only if you want to start the recording ofcopy statistics anew. For more information, see “Backing upthe stats file and re-creating it” on page 116.

GTOMSGLF IDCAMS control statements to define the log file. You will notneed to use this member.

GTOPARMF IDCAMS control statements to define the parameters file. Youwill not need to use this member.

GTORQDBF IDCAMS control statements to define the Request Databasefile. You will not need to use this member.

GTOSTATS Sample JCL for reprinting the Request Summary report for acopy request. Tape Optimizer automatically generates thisreport when a copy request runs. If the report is deleted, youcan reproduce it by using this JCL. For more information, see“Reprinting the Request Summary report” on page 106.


Table 4. CNTL members (continued)

Member Description

GTOSTDBF IDCAMS control statements to define the stats file. You willnot need to use this member.

GTOSTDEL Sample JCL for deleting records for a specific copy requestfrom the stats file. You should run this JCL for any copyrequest for which you did not retain the copy output. Formore information, see “Removing records for a specific copyrequest from the stats file” on page 116.

GTOSTKRP Sample JCL for reprinting the Stacked Tape Summary reportfor a copy request. Tape Optimizer automatically generatesthis report when a copy request runs. If the report is deleted,you can reproduce it by using this JCL. For more information,see “Reprinting the Stacked Tape Summary report” on page107.

GTOSTREO Sample JCL for removing old records from the stats file. Youshould run this JCL on a routine basis to ensure the file doesnot become too large. For more information, see “Removingold records from the stats file” on page 116.

GTOUTILR Sample JCL that you can use to release tapes that are beingheld by VRS even though their expiration dates haveelapsed. This JCL also synchronizes the Status field valuesin the Tape Optimizer stats file with the DFSMSrmm statusvalues. For more information, see “Releasing copied tapes tothe scratch pool and updating tape status information” onpage 115.

GTOVSAM Sample JCL for manually defining or redefining all of theTape Optimizer VSAM files (the log file, parameters file, statsfile, and Request Database file). For more information, seethe next section “Manually allocating the product’s VSAMfiles.”

Manually allocating the product’s VSAM filesYou can manually allocate the product’s VSAM files (the log file, parameters file,stats file, and Request Database file), if necessary.

Tip: It is recommended that you allow the customization script to automaticallyallocate the product’s VSAM files instead.

To manually allocate the files, you can use the sample JCL in the GTOVSAMmember of the runtime_HLQ.CNTL library. Edit the job card, as needed, and thensubmit the job.

After the VSAM files are allocated (by using the GTOVSAM member or some othermethod), ensure that you edit the runtime_HLQ.FILEDEFS file to specify the namesof the VSAM files that you created. Otherwise, Tape Optimizer will not be able tolocate these files.

Defining an additional Request DatabaseIf you plan to implement multiple Tape Optimizer instances, you will need to definean additional Request Database file for each instance.

12

Normally, a single Tape Optimizer instance is sufficient, even for very largetape-copy jobs. A single instance can run up to 10 copy subtasks concurrently onmultiple tape drives. However, if a single instance is not sufficient for your copyworkload, you can use multiple product instances. If you do so, you must define aRequest Database file for each additional instance by using the sample JCL in theGTODEFRQ member of the runtime_HLQ.CNTL library.

To define an additional Request Database:

1. In the GTODEFRQ member, edit all occurrences of RQDBxx to replace xx witha value that equals the numeric identifier of the last Request Database createdplus 1. For example, if the last Request Database has the identifier of RQDB01,you would replace xx with 02. Valid values are from 00 to 09. The originalRequest Database has the value of 00.

2. Run the job.

3. Add the following line to the runtime_HLQ.FILEDEFS file:'runtime_HLQ.RQDBxx'

where xx is the number that is one greater than the value for the last-createdRequest Database (the value that you specified in Step 1).


Chapter 3. Getting started with Tape Optimizer

Tape Optimizer provides an ISPF interface from which you can define and managetape copy requests. Before you start using the interface, review the following topicsto learn about interface usage and several key concepts that will affect how youdefine your copy requests.

Many of these concepts also pertain to manually-coded tape copy jobs.

Topics:

v “About the Tape Optimizer interface”v “Task flow for copying tapes” on page 17v “Supported wildcard characters” on page 18v “Default values for copy requests” on page 19v “How to select the tapes or data sets to copy” on page 19v “How expiration or retention dates are used in tape filtering” on page 22v “Factors affecting the release of copied tapes” on page 26v “How Tape Optimizer selects the copy utility to use” on page 27v “Strategies for optimizing performance of mass-copy operations” on page 28v “How SMS affects the allocation of tape drives” on page 28

About the Tape Optimizer interfaceTape Optimizer provides an ISPF interface for defining and running copy requests.

You should create your copy requests from this interface to reduce the chance ofsyntax errors. The interface validates entries for many copy options, generates theJCL, performs some optional validity checking, and includes online Help for everycopy option.

If you decide to create your copy jobs manually instead, you should still use theTape Optimizer interface to generate a basic copy request that you can use as atemplate. Then manually tailor the control cards in the generated JCL, as needed.

Starting the Tape Optimizer interface

To start the Tape Optimizer ISPF interface, run the GTOI EXEC that is in theruntime_HLQ.EXEC library. This REXX EXEC program is typically invoked from theISPF command shell (ISPF Option 6), as follows:EXEC 'runtime_HLQ.EXEC(GTOI)'

where runtime_HLQ is the high-level qualifier that you specified during productcustomization for the run-time libraries.

Tape Optimizer Primary MenuAfter you start the product, the first panel that is displayed is the Tape OptimizerPrimary Menu. From this menu, you can perform most product functions.

The following figure displays the Primary Menu:

15

To choose an option from this menu, type the number that corresponds to theoption at the OPTION prompt and press Enter.

Menu options

1 - Copy Request DefaultsChoose this option to set default values for copy options and for filters thatrefine the selection of input tape volumes or data sets. The default valueswill be applied to all copy requests; however, you can override them whendefining a specific request. For more information, see “Default values forcopy requests” on page 19.

2 - Copy RequestsChoose this option to define a new copy request or to edit, delete, orsubmit an existing copy request. For more information, see Chapter 5,“Defining and managing copy requests,” on page 51.

3 - LogChoose this option to view the copy log for a completed copy request. Thisinformation is useful for verifying that a copy request completedsuccessfully or for troubleshooting or diagnosing errors. For moreinformation, see “Displaying the Tape Optimizer copy log” on page 110.

4 - StatisticsChoose this option to view summary copy statistics for a tape volume todetermine whether it was copied successfully. For more information, see“Displaying summary copy statistics” on page 108.

Note: Options 1, 3, and 4 are for optional tasks.

Pull-down menusThe action bar at the top of each full panel displays the names of pull-down menusthat contain options for working with the Tape Optimizer interface and for defining acopy request.

Different panels have different pull-down menus, depending on the panel’s contextand functions. For example, the Create/Edit Request panel has four pull-downmenus: Menu, Filters, Options, and Help. If you tab to the Filters menu and pressEnter, a list of menu options drops down, as shown in the following figure:

Menu Help------------------------------------------------------------------------------

IBM Tivoli Tape Optimizer on z/OS - Primary MenuOPTION => ___________________________________________________________________

1. Copy Request Defaults Set defaults for copy requests System ID: SYSID2. Copy Requests Generate or edit copy requests OS Level : Z/OS 01.073. Log View copy log TTO Ver : V01.02.074. Statistics View copy statistics

Enter END to exit.

Figure 1. Tape Optimizer Primary Menu

16

To display a pull-down menu, you can either:

v Press the Tab key to move the cursor to the menu and then press Enter.v If you use a tn3270 emulator that supports mouse use, click the menu name and

press Enter.

To choose an option from a pull-down menu, type the number that corresponds tothe option and press Enter. For example, to choose By Program from the Filtersmenu (shown above), type 3 and press Enter.

To close a pull-down menu without making a selection, press F3 (End).

Displaying online HelpThe Tape Optimizer interface includes online Help information to help you use theproduct.

To access Help for the panel that you are working in, press F1 (Help) while thepanel is displayed.

Alternatively, on the action bar at the top of a panel, move the cursor to Help andpress Enter to display the Help pull-down menu. The menu will contain one or moreoptions for displaying context-sensitive Help information.

Task flow for copying tapesTo define and run a copy request from the Tape Optimizer interface, you will needto perform several tasks.

The following table lists these tasks in the order in which they should be performedand indicates whether each task is required or optional.

Menu Filters Options Help--------- +------------------------+ -----------------------------------------

IBM | 1. By DATE | S - Create/Edit Request - 00008COMMAND = | 2. By VOLSER | __________________________________________

| 3. By Program |Specify a | 4. By Data Set Name | lass (STORCLAS):

Input T | 5. Other | Name . . . . . . . . . INCART__Input T +------------------------+ . . . . . . . . . . . . ________

Output Tape Esoteric or Generic Unit Name. . . . . . . . . OUTCART_Output Tape SMS Storage Class. . . . . . . . . . . . . . . ________

Stack Input Tape Volumes on Output Tapes . . . . . . . . . . _ "/" to Select

Enter END to continue or CANCEL to return without saving.

Specify a list of single TAPE VOLSERs or TAPE VOLSER ranges to be copied.

- Starting VOLSER - - Ending VOLSER -C12345 C12350______ ____________ ____________ ____________ ______

******************************* Bottom of data ********************************

Figure 2. A pull-down menu

Chapter 3. Getting started with Tape Optimizer 17

Table 5. Task flow for copying tapes

TaskRequired oroptional For information

1 Setting default values for the copyoptions and input-tape filters that youexpect to use for most of your copyrequests (usually done when you firststart using the product)

Required for theinput and outputtape units and thebasic job cardinformation.Optional for otherparameters.

See “Default values forcopy requests” on page19.

2 Defining a specific copy request Required See Chapter 5,“Defining and managingcopy requests,” onpage 51.

3 Performing a simulated run of a copyrequest to verify your tape-selectioncriteria

Optional butrecommended

See “Performing a trialrun of a copy request”on page 97.

4 Running the copy request Required See “Submitting a copyrequest from the TapeOptimizer interface” onpage 98.

5 Verifying that tapes or data sets werecopied properly

Optional butrecommended

See Chapter 7,“Verifying that tapeswere copied properly,”on page 101.

Supported wildcard charactersWhen defining copy requests, you can specify masks for data set names, volservalues, and program names. A mask is composed of part of a name or volser valueand one or more wildcards that represent the remaining characters. Tape Optimizermatches your masks against actual data to determine which tapes or data sets toact upon.

The wildcards that you can use varies, depending on the task that you areperforming:

v If you are defining a basic copy request based on volsers, or if you are creating afilter based on program names, volsers, or data set names, you can use only thetrailing asterisk (*) wildcard. This wildcard represents one or more characters atthe end of a name or volser value.

v If you are specifying criteria for renaming the tape data sets to be copied, youcan use the standard asterisk (*) wildcard or a special percent sign (%) wildcard.Both wildcards represent zero or more characters. However, the asterisk (*)wildcard is used for ″find and replace″ type of renaming operations, whereas thepercent sign (%) wildcard is used for ″append″ type of renaming operations. Formore information, see “Criteria for renaming tape data sets” on page 53.

v If you are defining a basic copy request based on data set names, you can useany of the wildcards that DFSMSrmm supports for data-set-name masks. Thesewildcards include the following:

– A single trailing asterisk (*) to represent a qualifier or any number ofcharacters within a data set name, for example, PDUSER.*

– A percent sign (%) to represent a single character, for example,PDUSER.GT%.DATA

18

Default values for copy requestsYou must set default values for the input tape unit, output tape unit, and basic jobcard information. You can also optionally set default values for many other copyparameters.

To make defining new copy requests more efficient, you should set default valuesfor any copy parameters that you expect to use often. You then will not need tore-enter the same information repeatedly when defining new copy requests. TapeOptimizer will enter the default values for you automatically. You can override mostof the default values when you define a specific copy request, if necessary.

The copy parameters for which default values can be specified are categorized asfollows:

v General copy parameters, including the input and output tape devices, basic jobcard information, the number of days to retain input tapes, the maximum numberof copy log entries, and many other parameters

v Tape selection filters, including tape data set names and the names of programsthat created tape data sets

v Stacked tape parameters, including tape utilization limits that determine whenTape Optimizer loads a new output tape when tape-stacking is enabled

v DFSMSrmm parameters, including the DFSMSrmm locations of tapes to includein or exclude from copy requests, whether VRS retention rules are considered forinput tape selection, whether to use tape-volume expiration dates or expireddata-set retention dates for filtering data sets when data-set expiration dates arenot available, the DFSMSrmm control variables to use for transferring tape libraryinformation to output tape definitions, whether Tape Optimizer checks if thecontrol variables are supported on the system where a copy request runs,whether a copy request continues if a requested control variable cannot befound, and whether to apply the input tape volsers to the Accounting field onoutput tapes

v RECFM=U specifications that indicate the copy utility to use for certainRECFM=U data sets for which you expect Tape Optimizer will be unable toautomatically determine the copy utility

How to select the tapes or data sets to copyWhen you define a copy request (Option 2 on the Primary Menu), you select theinput tape volumes or data sets to copy by specifying their volser values or data setnames. Depending on the selection criteria you specify, Tape Optimizer copieseither individual tape data sets or entire tape chains.

v If you specify volsers, Tape Optimizer will build tape chains that are composed ofthe specified volsers and any related volsers. If a data set on a specified volsercontinues to another volser, that related volser will also be included in the tapechain. Tape Optimizer will copy the entire contents of an input tape chain, that is,all data sets on all tape volumes in the tape chain.

v If you specify data set names, you have the option of also specifying the data setsequence numbers (DSSEQ values). The presence of a DSSEQ valuedetermines the scope of what is copied.

– If you specify a data set name with a DSSEQ value (either a specific DSSEQvalue or only the asterisk (*) wildcard), Tape Optimizer will copy the data setsindividually from the input tapes. If a data set spans multiple tapes, TapeOptimizer will build an input tape chain that is composed of these tapes butwill copy only the specified data set from the tapes.

Chapter 3. Getting started with Tape Optimizer 19

– If you specify data set names without DSSEQ values, Tape Optimizer willbuild tape chains that are composed of the tape volumes that contain thespecified data sets and then copy the entire contents of the tape chains,including any other data sets on the tapes in the tape chains.

You can specify both types of data set name criteria (with or without DSSEQvalues) in the same copy request. If your selection criteria identify the same datasets multiple times, these data sets will be copied only once.

You can refine the set of input tapes or data sets by creating filters. Tape Optimizermatches your filtering criteria against tape library or system information for theselected tapes or data sets. You can specify default filtering criteria based on tapedata set names or program names. Later, when defining a specific copy request,you can override the default filtering criteria and specify additional types of filteringcriteria. By creating various types of filters, you can identify precisely the input tapevolumes or data sets to copy.

For most types of filtering criteria, you can create two types of filters:

v Inclusion filters implicitly include any tape chains or data sets that match yourinclusion criteria.

v Exclusion filters explicitly exclude any tape chains or data sets that match yourexclusion criteria.

If you create both inclusion and exclusion filters, Tape Optimizer first applies all ofthe inclusion criteria and then applies, to the resultant set of included tapes or datasets, the exclusion criteria.

If you configured a basic copy request based on volsers or on data set nameswithout corresponding DSSEQ values (tha

t l ibmtivolitape optimizer on z/os · 2016. 12. 1. · agent user’s guide (sc23-9738-nn), and...

Documents