For CA-1/TMS User Guide

Transcription

1 TM For CA-1/TMS User Guide Tape Stacker Mount Eliminator Media Conversion Disk Stacker Release 3.6.0

2 CRTSTUG Second edition printed April UNICOM Systems, Incorporated All Rights Reserved No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, without prior written permission from UNICOM Systems, Inc. This manual applies to CARTS release and to all subsequent releases of the product until otherwise indicated by new editions or updates to this publication. All products mentioned in this manual are trademarks of their respective companies. UNICOM Systems, Inc. UNICOM Plaza, Suite San Fernando Mission Blvd. Mission Hills, California 91345

3 Contents About This Manual... vii Audience...vii IVP Report and Installation Worksheet...vii CARTS TMS Documentation...viii Customer Service...ix Diagnostic Information...ix Chapter 1 Introduction... 1 CARTS Tape Stacker...1 How CARTS-TS Works...2 Analysis 2 Stacking Jobs 2 Makes an Exact Copy...2 Stacking More Than 127 Datasets per Volume...3 MagStar, Redwood, and Other High-Capacity Media 3 CARTS Reports...3 Selecting Datasets For Stacking...4 CARTS-TS Files...4 Running CARTS-TS...5 Mount Eliminator...6 How Mount Eliminator Works...6 Mount Eliminator Overview...7 Disk Stacker...8 Media Conversion...9 Chapter 2 CARTS ISPF Processing Accessing CARTS Screens...11 CARTS Main Menu...12 Generics and Wildcards...14 Wildcard Examples 14 Using Online Help...15 PF Keys...15 Exit and Save Screen Changes...16 Chapter 3...CARTS Control File Control File Menu SELECT Selecting a Control File CREATE Creating a New Control File DELETE Deleting a Control File...22 CARTS TMS User Guide iii

4 4 MODEL Copying a Control File ADD Adding a File to the Control File List DROP Removing a File from the Control File List MASTER Specifying a New Master Control File List Changing Stacking Conditions CRITERIA Selection Criteria Input Fields of the Selection Criteria Screen 29 2 EXECUTION Execution Options Input Fields of the Execution Screen 33 3 DSNAMES Selecting by Dataset Names Input Fields of the Data Set Names Screen 37 Examples of Stacking by Dataset Name 38 4 ROBOTS Controlling Robotic Use Input Fields of the Robotic Units and Options Screen 39 5 VOLSERS VOLSER Ranges...41 Selecting an Input Volume Group Adding or Modifying a VOLSER Group Input Fields of the VOLSER Group Screen 43 6 OUTCODES Selecting by TMS OutCodes JOB/STEP Job and Step Names ACCTCODE Accounting Codes Changing Job Statements Chapter 4 Meeting Stacking Objectives...51 Testing a Control File...52 Running CARTS-TS Submitting Batch Stacking Jobs Submitting Stacking Jobs from CARTS-TS ISPF Screens...53 Using Restacker Unstacking a Stacked Tape with Restacker Unloading a Single File from a Stacked Volume Selecting Reports Stacker Reports Restacker Reports Discontinuing a Report...58 Resuming a Report...58 CARTS Integrity Checks RESETCDS Utility 59 RESTCYC Utility 59 Setting the Number of Concurrent Stacking Jobs Limiting the Number of Stacking Jobs Controlling Input/Output Type...63 Migrating to Tape Drives That Support Compaction Obtaining a Pull List Before Stacking Grouping Datasets on Stacked Volumes Scratch Tape Shortages Inconsistent Scratch Tape Availability Reducing the Number of Off-Site Volumes...69 Electronic Vaulting Implementing Security on Stacked Volumes iv CARTS 3.6.0

5 Volume Level Security...71 Dataset Level Security...71 Chapter 5 Using the History Inquiry Selecting History File Records...74 Dataset Selection Screen...76 History Detail Screens...77 Cataloged/Uncataloged Dataset Detail Screen...77 Display Fields of the Cataloged/Uncataloged History Detail Screen 77 Pending Dataset Detail Screen...78 Display Fields of the Pending Dataset History Detail Screen 78 Viewing Other History Files...80 Chapter 6 Mount Eliminator Preparing Mount Eliminator...82 Preparing Control Files Used by Mount Eliminator...82 Customizing the CARTS-TS Control File for Use with Mount Eliminator 82 Customizing the Mount Eliminator Control File 84 Preparing Mount Eliminator Procedures and Started Tasks...89 CARTSFST 89 CARTSCHK Procedure 89 CARTSDSK 90 CARTSMOV 90 Starting Mount Eliminator...91 Monitoring the Status of Mount Eliminator...92 Displaying the Current Status...92 Displaying the Work in Progress Table...93 Viewing the Block File...95 Diagnosing Mount Eliminator Redirection Problems...97 Tracing Mount Eliminator Activity Stopping Mount Eliminator Chapter 7 Disk Stacker Editing the Disk Stacker Control File Using a New Control File Preparing the CARTSDS Procedure Running Disk Stacker Chapter 8 Media Conversion Editing the Media Conversion Control File Using a New Control File Running Media Conversion Using Media Conversion with Virtual Tape Systems Control File Recommendations for Virtual Tape Systems Virtual Footage 111 VTS Unit Esoteric/Output Storage Class 111 Example Media Conversion Control File Settings for a VTS CARTS TMS User Guide v

6 Chapter 9 CARTS Maintenance Dependency File Maintenance Editing Dependency File Records Updating the Dependency File with Current SMF Data Backing Up the Dependency File Controlling the Size of the Dependency File History File Maintenance Block File Updates Running UPDTBLKF Manually Updating the Block File Control File Maintenance JES Maintenance Index vi CARTS 3.6.0

7 Audience About This Manual CARTS is a family of base and optional components that help reduce MVS tape storage costs. This manual describes each component in a separate chapter. Each chapter includes a: conceptual description of the product procedures to use the product through ISPF screens procedures to run the products as batch jobs maintenance procedures This manual describes how to use CARTS at sites running Computer Associates CA-1/TMS tape library management system. Hereafter, CA-1/TMS is simply referred to as TMS. Audience This manual is intended for system administrators and operators responsible for managing tape storage with TMS at their site. Readers are expected to understand MVS and TMS tape management concepts. Also, many of the procedures described in this manual require site-specific JCL changes to run batch jobs. Readers should be proficient editing JCL and familiar with their site s system standards. IVP Report and Installation Worksheet References are made throughout this manual to the CARTS IVP reports and the installation worksheets located in Appendix C of the CARTS for CA-1/TMS Installation Guide. These worksheets should have been prepared when the CARTS components were installed. The worksheets contain information you need to operate and maintain CARTS. Obtain them before completing the procedures described in this manual. CARTS TMS User Guide vii

8 CARTS TMS Documentation The CARTS TMS product library consists of the manuals listed below. The top three manuals contain specific information about running CARTS with TMS. The other two manuals contain information that applies to all versions of CARTS. CARTS For CA-1/TMS Installation Guide Describes procedures to install and implement all CARTS components at sites managing their tape library with TMS. CARTS For CA-1/TMS User Guide Describes how to use all CARTS components at sites managing their tape library with TMS. CARTS For CA-1/TMS Release Notes Explains CARTS TMS installation requirements, product enhancements, and a procedure to migrate to Release CARTS Messages and Codes Lists messages and codes generated by all CARTS components. CARTS Reports Manual Presents an example of each CARTS report and a description of each report field. An online version of each manual is distributed on a compact disk (CD) as part of the CARTS Release product package. These manuals can be viewed with Acrobat Reader with Search, which is a free viewing tool available from Adobe Corporation. Included on the CARTS documentation CD is a file to install Acrobat Reader for PCs running a 32-bit release of Windows. Read the CD s readme.1st file for instructions to install Acrobat Reader. The latest version of Acrobat Reader with Search can be downloaded from the Adobe Corporation web site ( viii CARTS 3.6.0

9 Customer Service Customer Service UNICOM Systems Customer Service can be reached by the following methods: Voice Fax Website Normal business hours are from 6:00 a.m. to 4:30 p.m. Pacific Standard Time, Monday through Friday. Emergency assistance is available 24 hours a day, 7 days a week. An answering service receives Customer Service calls beyond normal business hours. You may leave a message if it is not an urgent problem. A Customer Service representative will return your call at the start of the next business day. Requests for urgent support outside of normal business hours are answered immediately. A Customer Service representative will be summoned to return your call. Leave a phone number where you can be reached. If you have not received a return call from a Customer Service representative within an hour of reporting the problem, please call back. Our representative may be experiencing difficulties returning your call. International customers should contact their local distributor to report any problems with a UNICOM Systems product. A separate password is required to activate each CARTS component. Contact UNICOM Systems or your sales representative to obtain a password. The CARTS For CA-1/TMS Installation Guide includes instructions to apply CARTS passwords. Diagnostic Information This section describes diagnostic data you should collect before reporting a CARTS problem to Customer Service. Having this information ready before placing a call to Customer Service will enable the representative to resolve your problem more quickly. List of installed CARTS components MVS and JES release numbers Version of TMS used at your site IVP report produced during installation Related error messages Command or JCL used to submit the failing job Dump, if one is generated, and register contents from the JES log CARTS TMS User Guide ix

10 x CARTS 3.6.0

11 CARTS Tape Stacker Chapter 1 Introduction CARTS is a family of common and optional components that help reduce tape storage costs. This chapter gives an overview of each component of the CARTS product family. It explains how each component works at sites managing their tape library with Computer Associates CA-1/TMS tape management system. CARTS Tape Stacker CARTS Tape Stacker (CARTS-TS) analyzes the TMS Tape Management Catalog (TMC) and generates jobs that combine two or more tape datasets onto a single output tape. Datasets are stacked and restacked onto an output tape according to parameters set with Control files. After datasets have been stacked, tape usage increases on average from 20% to 95% of capacity. Tapes can be returned to the scratch pool after their datasets have been stacked onto another volume. Active unstacked volumes managed by TMS Stacked volume Empty volumes returned to the scratch pool CARTS-TS is the base component in the CARTS family. CARTS-TS must be installed and operational before adding any optional CARTS component discussed in subsequent sections of this chapter. While originally designed to put you in control of your tape library growth, CARTS-TS has become a multi-faceted tool, useful for a wide variety of typical tape library management tasks. For example, customers have used CARTS-TS to perform electronic vaulting and to reduce the number of ejects from their robots. CARTS TMS User Guide 1

12 Chapter 1 Introduction How CARTS-TS Works CARTS-TS runs as a batch job to stack or restack tape datasets. Tapes are stacked according to operational values included in the job JCL and a Control file. CARTS-TS uses no system hooks. No user intervention is required during the period that tapes are stacked or restacked. Analysis CARTS-TS analyzes the tape library before stacking datasets. CARTS-TS calculates the amount of tape required to store each dataset and estimates how many datasets can fit on a volume. CARTS-TS produces batch jobs that stack datasets onto output volumes after analysis is complete. MVS does not permit more than one dataset to be open from a single tape volume at the same time. CARTS-TS uses data from a Dependency file to ensure that datasets required by the same job or jobstep are stacked on separate volumes. Only the last file on a tape can be modified. CARTS-TS uses data from the Dependency file again to place MOD files as the last file on a tape. CARTS-TS examines your site s vaulting conditions and excludes or includes datasets from stacking based upon their vault status and destination. CARTS-TS Stacking Jobs Tape mount requests are issued during a stacking job. Each job uses two drives, one for input, one for output. (If you use the Dual Copy feature, that is, make a duplicate of the stacked tape, CARTS-TS uses an additional output drive, for a total of 3.) Stacking jobs can run concurrently. Using Control file parameters, you specify how many jobs can run simultaneously and how many drives to assign to stacking jobs. If you are moving datasets out of a robot or into a vault, CARTS-TS copies all datasets to a scratch tape at the new location. If the tapes are to remain where they are, CARTS-TS requests one of the dataset volumes as output and copies the remaining datasets to that tape, beginning with file number two. (It doesn't make any sense to copy the first file to a scratch tape File 5 File 4 File 3 File 2 File 1 Makes an Exact Copy CARTS-TS does not change the characteristics of dataset as they are stacked. Dataset attributes such as block size, record length, and record format remain unchanged after stacking. CARTS-TS even maintains the original creating job name, step name, creation date, and time in the TMC catalog. 2 CARTS 3.6.0

13 CARTS Tape Stacker Stacking More Than 127 Datasets per Volume With the advent of new, high capacity storage devices such as StorageTek s Redwood and IBM s MagStar, a large number of datasets can be stored on a single tape volume. CARTS-TS can stack up to 9,999 datasets (MVS limitation) on a single cartridge depending on dataset size and cartridge capacity. For stacking jobs that place more than 127 datasets on a volume, CARTS-TS submits a separate stacking job for each group of 127 datasets. A special pseudo file is stored on disk with the remaining job information. When the initial job finishes, CARTS-TS automatically starts the next job in sequence. The pseudo file is deleted after the last job is finished. MagStar, Redwood, and Other High-Capacity Media Tapes used by the MagStar and Redwood families of tape devices have virtual footage lengths of 20,000 or more. To increase stacking efficiency, CARTS-TS mounts the output tape as resident during the stacking job. The output tape volume remains mounted between stacking job steps and any continuation jobs. This prevents the tape unit from unloading the volume for another job. When the last stacking job completes, an MVS UNLOAD command is issued to dismount the volume. CARTS Reports CARTS-TS produces a series of reports for each stacking operation. Reports are numbered and most match the DD name in the job output. This naming convention makes it easy to locate a specific report when you are reviewing a stacking jobs using SDSF or another spool browse tool. It is also easy to dummy out reports you do not want to produce. For information on including and excluding reports, see Selecting Reports on page 57. For information about a specific report, refer to the CARTS Reports Manual. CARTS TMS User Guide 3

14 Chapter 1 Introduction Selecting Datasets For Stacking You select which tape datasets will be included or excluded from CARTS-TS processing. Tape datasets are included or excluded from stacking based upon the following criteria: dataset name dataset size dataset usage catalog status volser ranges expiration dates volumes stored off site or volumes that are not stored at a particular off-site location TMS out codes job or step name accounting codes volumes inside/outside robots Refer to Changing Stacking Conditions on page 28 for a complete listing of all screen options to select stacking candidates from the CARTS Selection Rules Categories menu. Datasets or volumes are excluded from stacking if any of the following conditions occur: scratch tapes or volumes marked as deleted multi-volume datasets (Media Conversion and Restacker can stack multi-volume datasets) externally managed datasets, such as HSM datasets volumes not listed in the TMS Tape Management Catalog (TMC) The CARTSRPT99 and CARTSRPT14 reports explain why each dataset was rejected for stacking. CARTS-TS Files CARTS-TS uses information from three files to stack datasets to tape: The Control file contains user-defined stacking rules to select which datasets to stack, the input and output drives, and under what conditions. You prepare Control files by completing fields on CARTS ISPF screens. For more information about these screens, see Changing Stacking Conditions on page 28. The History File is an audit file that shows the complete stacking history of each dataset and tape from initial stacking through the various executions of restacking. You can display History File records using CARTS ISPF screens. See Chapter 5 Using the History Inquiry on page 73 for more information. Incidentally, the History File and the CARTS ISPF screens offer you a simple way to locate an uncataloged dataset. 4 CARTS 3.6.0

15 CARTS Tape Stacker The Dependency File prevents CARTS-TS from stacking invalid combinations of datasets on tape. The Dependency file lists datasets that are processed by the same job step and datasets that are processed as MOD. CARTS-TS uses information from the Dependency file to ensure that datasets needed by the same job step are placed on different volumes and that MOD datasets are placed only at the end of the tape. The Dependency File is built during installation with dataset information collected from SMF records. It requires regular updates with SMF records to maintain the current status of datasets. Maintenance procedures are described in Dependency File Maintenance on page 114. Running CARTS-TS Control files parameters are initialized by entering values on CARTS ISPF screen fields. These parameters determine which datasets to include or exclude from stacking, whether to include or exclude volumes mounted in robots, and which tape drives to use as the output device. You can create custom Control files that are adapted to each of your site s ongoing tape management tasks. After Control files are prepared and tested, you submit the CARTSTS procedure to stack tapes. You can automate the execution of CARTSTS by submitting it as a job through a batch scheduler. Or, you can submit CARTSTS from an ISPF screen. How often you run stacking jobs depends on the needs of your site. Typically, CARTSTS is run on Friday to free up as many scratch tapes as possible for weekend backups. You can run CARTSTS during your batch window or while your online systems are running. CARTSTS does not use significant amounts of system resources that could impact online performance. Prepare a Control file DASD Unstacked Volumes Test a Control File Restacked Volume Tape Archiving Stacked Volumes Control File Control File STACKER RESTACKER Scratch Pool Return to Scratch Pool Normally, datasets on a stacked volume have different expiration dates. Over time, some datasets expire and create space on the stacked tape. You can reclaim this space by periodically restacking these volumes. Restacking works in the same manner as stacking; unexpired tape datasets are combined onto fewer output volumes Restacker jobs are normally run on a monthly or quarterly schedule. CARTS TMS User Guide 5

16 Chapter 1 Introduction Mount Eliminator Mount Eliminator (CARTS-ME) is an optional CARTS component that temporarily redirects tape datasets to disk that are needed for a scheduled job. After the job is finished, datasets are off-loaded from disk and stacked to tape. Mount Eliminator redirects tape datasets transparently, without JCL changes. Mount Eliminator can significantly reduce the number of tape mount requests when dataset I/Os can be satisfied from disk rather than tape. Also, batch throughput is usually faster because there is less contention for tape drives with fewer mount requests. How Mount Eliminator Works Mount Eliminator redirects tape datasets to disk automatically based upon values set within the CARTS-TS and Mount Eliminator Control files. Then, Mount Eliminator off-loads these datasets back to tape if any one of the following triggering conditions occur: exceed a threshold number of datasets redirected to disk exceed a threshold percentage of disk space on the volumes that redirected datasets are placed scheduled interval Mount Eliminator off-loads datasets to tape using standard CARTS-TS processing. Fewer tape mounts are needed because datasets are stacked when they are written to tape. For example, suppose that five datasets can be stacked on a single cartridge (an average ratio). Mount Eliminator writes these five datasets to tape with a single mount, eliminating four potential mount requests. Mounts Without ME Mounts With ME ➀ Tape dataset is written to DASD. CPU ➀ ➁ CPU ➁ Dataset is read from DASD as part of regular batch processing or for tape stacking. No mounts. ➂ Datasets are stacked to tape on the fewest possible tapes. DASD ➂ Datasets can be read directly from tape after they have been stacked. Datasets do not have to be loaded back to disk to be read or written. Mount Eliminator maintains original dataset creation statistics in the TMC. MVS and TMC catalogs remain in control, just as they do with regular CARTS-TS stacking. You control the number of DASD volumes allocated to Mount Eliminator by specifying which DASD esoterics Mount Eliminator can use. You also control which datasets are redirected and which are written directly to tape, with Mount Eliminator Control files. If you like, you can have Mount Eliminator leave some datasets on disk permanently, thus changing dataset storage without having to change your JCL. 6 CARTS 3.6.0

17 Mount Eliminator Mount Eliminator Overview Mount Eliminator: requires no changes to JCL to redirect datasets to disk maintains all original creation job statistics in the TMS Tape management Catalog (TMC) leaves the MVS catalog in control You select: target DASD volumes that store redirected datasets datasets to be redirected to disk whether some datasets remain on disk or all are stacked to tape schedule to submit Mount Eliminator stacking jobs A tape dataset must meet the following requirements to be redirected to disk by Mount Eliminator: dataset must be stored on a single tape volume (no multi-volume datasets) Generation Data Groups (GDGs) are regarded as a single dataset and are redirected. dataset matches the selection criteria specified in the CARTS-TS Control file used by Mount Eliminator dataset DD statement specifies or defaults to DISP=(NEW,CATLG) dataset UNIT parameter specifies an esoteric specified for Mount Eliminator processing dataset with a LABEL parameter can only include file number 1 A dataset with any other file number is excluded. No EXPDT=98000 is coded dataset has four or more entries in the Mount Eliminator Block table dataset is within the size limit specified in the Mount Eliminator Control file Datasets are excluded from redirection by Mount Eliminator if the dataset s JCL contains the following: A LABEL parameter that includes a file number greater than 1. For example, LABEL=(2,SL,9000) A DD statement with a VOL parameter associated with it except VOL=(,RETAIN). CARTS TMS User Guide 7

18 Chapter 1 Introduction Disk Stacker CARTS-DS Disk Stacker is an optional CARTS component that off-loads sequential disk datasets and stacks them to tape. Datasets are selected as candidates for stacking by their name or residency time on disk. Datasets are written to tape using standard MVS read/write functions. The MVS catalog is updated to reflect the new location of each dataset on tape. Disk Volume Sequential Datasets Disk Stacker Sequential Datasets Tape Volume After they have been stacked, dataset are read or written directly from tape without requiring Disk Stacker. The MVS catalog retains the volume serial number and file sequence number of the tape dataset. All future access to the dataset is directed to the stacked tape volume. Datasets are deleted from DASD after they are stacked and recataloged to tape; freeing up disk space.subsequent I/O requests are directed to tape because there is only one copy of the dataset. Disk Stacker differs from other products that load datasets to disk each time they are read and then migrate it to a new tape, whether or not the file was modified. Disk Stacker is particularly suited for resolving acute storage shortages. Disk Stacker gives you the capability to quickly intervene and free up needed space on a specific DASD volume by off-loading qualified datasets to tape. Another common use for Disk Stacker is managing dataset migration to tape. By running Disk Stacker jobs in reports only mode, you can generate a set of reports that show which datasets are candidates to be archived to tape. You can distribute these reports to employees at your site to get their consent before you begin actually stacking their datasets to tape. 8 CARTS 3.6.0

19 Media Conversion Media Conversion CARTS-MC Media Conversion is an optional CARTS component that transfers datasets from one type of tape media to another. Media Conversion supports the full range of tape formats compatible with 3420, 3480, 3490, 3490E, 3494, or 3495 drives even Optical 3480/3490s (for long term storage). Media Conversion: converts both single volume and multi-volume datasets transfers datasets stored on reel to cartridge tape transfers datasets between 18, 36, or 128-track tape Migrates tape volumes into and out of a virtual tape system (VTS) transfers datasets on uncompacted volumes to volumes mounted on tape devices that support compaction maintains a dataset's original parameters, including job accounting updates the TMS TMC with new volume information provides Control file parameters to migrate an entire tape library with a single job or in series of smaller jobs provides options to stack single volume datasets on the output tape or simply duplicate the tapes without stacking. Duplicate Stacking You specify the location of the destination scratch tape through the use of esoteric device names or an SMS storage class. Using this technique, you can direct Media Conversion to transfer datasets to a scratch tape mounted on a robot at a remote location. Or, you can migrate your library of older non-compacted tapes to newer compacted tapes by selecting device esoterics that stack datasets on scratch tapes mounted on drives that supports compaction. Media Conversion is used frequently as a migration tool to transfer datasets stored on older reel tape to cartridge tape. Another common use for Media Conversion is in establishing a single tape media standard across all of a company s data centers. Media Conversion allows you to run a series of jobs that combine datasets stored on a variety of tape formats from local and remote sites and stack them on a common tape media. Because datasets can be stacked as they are copied, far fewer tape volumes are required to archive your library. CARTS TMS User Guide 9

20 Chapter 1 Introduction 10 CARTS 3.6.0

21 Accessing CARTS Screens Chapter 2 CARTS ISPF Processing This chapter contains introductory information that explains how to use CARTS ISPF screens. It gives an overview of common tasks that are part of using CARTS ISPF screens: Accessing screens Using standard PF keys Using wildcards to select a range of data for a screen field Accessing CARTS Screens There are two ways to access CARTS screens. If CARTS was added as an option to your site s ISPF menus, you can select CARTS as you would any other ISPF option. See the CARTS-TS worksheet for the menu option. If CARTS was not added as an ISPF menu option, access it through the ISPF TSO Command Processor: Select option 6 from the ISPF main menu and then enter CARTSTS to invoke the CLIST that presents the CARTS Main Menu shown on page 12. CARTS TMS User Guide 11

22 Chapter 2 CARTS ISPF Processing CARTS Main Menu The following figure shows an example of the CARTS Main Menu. The Main Menu options are described following the figure. If you are conducting a trial evaluation of CARTS, a message appears at the bottom right of of the Main menu. The message is a reminder that you are in trial status and cannot stack datasets until a permanent password has been applied. Status: TRIAL, NO STACKING Expires: 1999/000 Not all options are visible at all times. Options 3, 4, and 5 appear only after you have selected a Control file. Options 7 and 8 are visible only when Mount Eliminator is active or quiescent. Mount Eliminator enters a quiescent state just before it stops. Refer to Tracing Mount Eliminator Activity on page 97 for more information. ARTS Main Menu COMMAND ===> User Id-USR1 Choose one of these options: CARTS-TS 1 CONTROL Control file selection and maintenance 2 UTILITIES Utility functions CARTS-ME 6 CONTROL Mount Eliminator Customer: TECHNOGLIC SOFTWARE CONCEPTS IRVINE, CALIFORNIA Tape Management System: TMS Robotic Vendor: ATL CARTS (c) 1998 UNICOM Systems, Inc. 1 - CONTROL F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE Use this option to select a Control file from a menu that appears with a list of current Control files that can be modified. You can add another Control file, remove a Control file, and create a new Control file from the master list. See 1 SELECT Selecting a Control File on page 19, for more information. 2 - UTILITIES Use this option to display the CARTS Utilities menu. You can edit your Depedency file or display the contents of the History file by selecting these options from the Utilities menu. 6 - CONTROL Use this option to modify parameter values of the Mount Eliminator Control file. This file specifies operational values used by Mount Eliminator to redirect datasets to disk and stack them to tape. See Customizing the Mount Eliminator Control File on page CARTS 3.6.0

23 CARTS Main Menu After you have selected a Control file and returned to the Main Menu again, other CARTS options appear on the screen, as shown in the following example. CARTS Main Menu FILE OPENED COMMAND ===> User Id-PROD Choose one of these options: CARTS-TS 1 CONTROL Control file selection and maintenance 2 UTILITIES Utility functions 3 SUBMIT Submit stacking/restacking jobs for execution 4 RULES Specify criteria to select data sets for stacking 5 JOBCARDS Change job cards CARTS-ME 6 CONTROL Mount Eliminator Customer: TECHNOGLIC SOFTWARE CONCEPTS IRVINE, CALIFORNIA Tape Management System: TMS Robotic Vendor: ATL CARTS (c) 1998 UNICOM Systems, Inc. F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE A message appears at the upper right corner of the screen to indicate a Control file has been selected and is currently open. 3 - SUBMIT Use this option to submit online Stacker or Restacker jobs. See Submitting CARTS-TS Stacking Jobs from ISPF on page RULES Use this option to change tape stacking parameter values. These stacking parameters determine what datasets and volumes are selected for stacking and how stacking is performed. See Changing Stacking Conditions on page 28 for more information. 5 - JOBCARDS Use this option to change the JCL used to submit stacking jobs. See Changing Job Statements on page 50. CARTS TMS User Guide 13

24 Chapter 2 CARTS ISPF Processing Generics and Wildcards Wildcards can be used on any CARTS screen that has fields to specify parameter values based upon dataset or volume names. CARTS supports explicit and implied wildcards: Explicit wildcard The asterisk ( * ) wildcard character represents any character at a single position within the string. Implied wildcard An implied wildcard represents any combination of characters following a string of designated characters. For example, if you specify a job name that begins with the characters JE, all jobs beginning with JE are accepted. When you specify dataset name qualifiers, you can limit the match to the characters you entered by ending the string with a period. If you specify a qualifier of JE., only the qualifier JE is a match. If you specify JE without a period, a match is made for all datasets whose qualifier begins with JE. You cannot limit the match for job names, step names, and accounting codes. Trailing wildcards are always implied. Of course, if you specify all eight characters of a job or step name, you specify a complete match by default. Wildcard Examples You want to exclude all datasets beginning with ABC. You specify ABC at position 1 of the INCLude/EXCLude Statements screen.: INCLude/EXCLude Statements Opt Grp EXC ABC CARTS omits all datasets with ABC as the high-level qualifier. The following datasets are excluded from CARTS processing: ABC ABC123.TEST ABC123.TESTXXX.YY.JAN91 You want to include all datasets with a second level qualifier prefix of PROD that have a single-character suffix.: INCLude/EXCLude Statements Opt Grp INC 001 PROD*. CARTS includes all datasets with a second level qualifier of PRODx. This includes the following datasets: ABC.PRODA.SAMPLE XTSG.PRODB.INVENTORY DKGFHJ.PROD CARTS 3.6.0

25 Using Online Help However, CARTS would exclude a dataset named XCD.PROD22.TEST because the suffix of the second level qualifier has more than a single character. The asterisk wildcard indicates any character in a single position within the string. You want to include all jobs matching the generic name PAYxRUN. You specify PAY*RUN in the Job and Step Names screen. Using Online Help CARTS ISPF screens have online help. Press the PF1 HELP key for a description of the current screen s function and fields. PF Keys The following keys are assigned to most CARTS ISPF screens. PF1 Display online help PF3 Exit the current screen and return to the previous screen. Changes made to a Control file are saved in memory. CARTS redisplays the current screen if the screen input contains errors. You must correct the errors before exiting from the screen. When you exit from the CARTS Main Menu, you are presented with the option to save or discard your changes. PF7 Scroll the screen backwards one page. PF8 Scroll the screen forward one page. PF3 and PF4 keys work differently for the Mount Eliminator CONTROL option: PF3 Exit the screen you are in and return to the previous screen. If you have made changes to a Control file, they will be saved in memory. If you return to the CARTS Main Menu, your changes will have been saved to the Control file on which you were working. If errors are found in the screen input, CARTS will redisplay the screen. You must correct the errors to continue. PF4 Exit the CARTS ISPF screens and discard any changes to the Control file. CARTS TMS User Guide 15

26 Chapter 2 CARTS ISPF Processing Exit and Save Screen Changes 1. Press your END key to exit from a CARTS screen and return to the Main Menu. If you made changes to the CARTS-TS Control file, the CONFIRM UPDATE screen appears when exiting from a dialog or switching to a different Control file.this screen allows you to save or cancel your current changes. CARTS CONFIRM UPDATE Current Control file: PROD.CTS360T.CNTL TMS Default Control File The above-named Control file has been modified. Enter END (PF3) to save your changes. Enter CANCEL to exit without saving. COMMAND ===> User Id-PROD 2. Enter the END command or press your END key to save your changes and update the file. 3. Enter the CANCEL command instead to close the file without saving the current changes. 16 CARTS 3.6.0

27 Chapter 3 CARTS Control File A Control file contains parameters that set the operating conditions for all CARTS components. Each component has its own Control file. This chapter describes how to update your CARTS-TS Control files. The chapter consists of the following major topics that are described in separate chapter sections: Selecting and maintaining Control files (Main Menu option 1) Changing stacking rules (Main Menu option 4) Changing job statements (Main Menu option 5) CARTS TMS User Guide 17

28 Chapter 3 CARTS Control File Control File Menu Control files are managed from the Control files screen shown in the following figure. By selecting screen options you can create a new Control file or edit, add, drop, and delete existing Control files. 1. Select option 1, CONTROL, from the CARTS Main Menu The following figure shows the options that can be selected from the Control files screen. CARTS Control Files Choose one of the following options: 1 SELECT Open an existing Control file 2 CREATE Create a new Control file 3 DELETE Delete a Control file 4 MODEL Initialize a Control file using an existing file 5 ADD Add an existing Control file to the master list 6 DROP Remove a Control file from the master list 7 MASTER Specify master list data set name Current Control file ===> COMMAND ===> User Id-PROD 1 SELECT Select a Control file that is already in your Control file list. The Control file list is the working list of your CARTS-TS Control files. 2 CREATE Create a new Control file. The Control file is allocated, initialized, and placed in the Control file list. 3 DELETE Delete a Control file. The Control file is deleted from disk and the Control file list. 4 MODEL Copy the contents of one Control file to another. Model is useful when a Control file has been damaged and you want to begin over. 5 ADD Add an existing Control file to the Control file list. You need this option to upgrade from a previous release of CARTS if you want to continue using your existing Control files. 6 DROP Remove a Control file from the Control file list. This option only removes the file from the list. It does not delete the Control file from disk. 7 MASTER Specify a master dataset containing the Control file list. 18 CARTS 3.6.0

29 Control File Menu 1 SELECT Selecting a Control File You must select a Control file before changing its attributes or submitting a stacking job. 1. Select option 1, SELECT, from the Control Files screen. The following figure shows the Available Control Files screen that appears after selecting option 1.The Available Control Files screen lists CARTS Control files that can be browsed or updated. CARTS Available Control Files Row 1 from 7 COMMAND ===> User Id-PROD Place the cursor on the desired control file name and press ENTER Last Updated Description / Data Set Name Date Time User ID Default Control File 01/25/ :45 PRH2 PRH.CTS360.CNTL TMS ME TS Test Control File 01/25/ :50 PRH2 PRH.CTS360.CNTLME TMS DS Test Control File 04/08/ :53 PRH1 PRH.CTS360.DSCNTL TMS MA Test Control File 04/08/ :47 PRH1 PRH.CTS360.MACNTL TMS MC Test Control File 03/31/ :24 PRH1 PRH.CTS360.MCCNTL TMS RS Test Control File 01/25/ :51 PRH2 PRH.CTS360.RSCNTL TMS ST Test Control File 04/16/ :23 PRH1 PRH.CTS360.STCNTL ******************************* Bottom of data ******************************** 2. Place the cursor over the name or description of the Control file that you want to use and press ENTER. You return to the CARTS Main Menu after selecting a Control file. The SUBMIT, RULES, and JOBCARDS options are now displayed from the Main Menu. After these screen options are displayed, you can change Control file parameters and submit a stacking job. For more information on these options, see Submitting Stacking Jobs from CARTS-TS ISPF Screens on page 53, Changing Stacking Conditions on page 28, or Changing Job Statements on page 49. CARTS TMS User Guide 19

30 Chapter 3 CARTS Control File 2 CREATE Creating a New Control File The Create option is used to allocate a new Control file and add it to the list of available Control files. When creating a new Control file, you have a choice of either specifying where the new Control file is to be allocated, or you can let SMS (System Managed Storage) automatically assign the location. Regardless of which method you choose to allocate a Control file, you must enter the dataset name and description. If you choose the Non-SMS allocation method, you must provide either a volser or a unit esoteric to indicate where the Control file is to be placed. If you use SMS, you must leave the Volume Serial and Generic Unit fields blank and complete the Management class and Storage class fields instead. If you want to add an existing Control file from a prior CARTS release, use option 5, ADD, from the Control Files menu. Also, use the ADD option to add Control files of other CARTS components installed at your site. 1. Access the CARTS Control Files screen by selecting option 1 from the Main Menu. 2. Select option 2, CREATE, from the CARTS Control Files screen. The following figure shows the Create New Control File screen that appears after selecting option 2 CARTS Create New Control File COMMAND ===> User Id-PROD To create a new Control file, fill in the required information and press ENTER. Data set name ===> XYZ1.CTS360.CNTL Description ===> Weekly Control file SMS allocation: Management Class ===> Storage Class ===> Non-SMS allocation: Volume Serial ===> (volume on which to allocate the file) * Generic Unit ===> (Generic group name or unit address) * ( * Only one of these fields may be specified) 3. Enter the dataset name of the new Control file and a description up to 50 characters long. The name and description are displayed from the Available Control Files screen. 20 CARTS 3.6.0

31 Control File Menu 4. Specify the location where you want the Control file to be allocated. SMS allocation Enter an SMS management and storage class. The management class can be set to NULL. Non-SMS allocation Enter a value in either the Volume Serial or Generic Unit fields, but not both. Volume Serial VOLume SERial of the target volume Generic Unit Disk esoteric or unit address 5. Press ENTER. You will receive the Select Model Control File screen. CARTS initializes your new Control file by copying the contents of an existing Control file to the new file. 6. Place the cursor on the file name or description to select the file you want to copy as the model. 7. Press ENTER. You return to the Create New Control File screen. The message OK appears on the upper right corner of the screen to indicate the Control file was successfully created. You may create another Control file, or press PF3 to exit. CARTS TMS User Guide 21

32 Chapter 3 CARTS Control File 3 DELETE Deleting a Control File The Delete option removes a Control file from disk and the Control file list. This screen lists the Control files that your are authorized to delete. A Control file is deleted and removed from the master list by placing the cursor on the appropriate data set name or description line and pressing ENTER. 1. Select option 3, DELETE, from the Control Files screen. The following figure shows the Delete Control File screen that appears after selecting option 3. CARTS Delete Control File Row 1 to 3 of 3 To delete a Control file and remove it from the master list, place the cursor on the file name or description and press ENTER Last Updated Description / Data Set Name Date Time User ID test 2 file 04/06/ :59 PROD PROD.CTS360.TEST2.FILE test 3 file 04/07/ :34 PROD PROD.CTS360.TEST3.FILE USR's Control file 04/06/ :52 PROD PROD.CTS360.TMS.CNTL ******************************* Bottom of data ******************************** COMMAND ===> User Id-PROD 2. Place the cursor on the Control file name or its description and press ENTER to select the Control file you want to delete. The Confirm Delete screen shown in the following figure requests confirmation before deleting the Control file CONFIRM DELETE COMMAND ===> User Id-PROD Dataset Name: XYZ1.CTS360.CNTL Description: Weekly Control file INSTRUCTIONS: Press ENTER key to confirm delete request. (The dataset will be deleted and dropped from the Control file list) Enter END command to cancel delete request. 3. Press ENTER to confirm the request or enter END in the command line to cancel the delete request. You return to the Control File menu after confirming or cancelling the delete request. 22 CARTS 3.6.0

33 Control File Menu 4 MODEL Copying a Control File The Model option allows you to initialize a Control file by using another, existing file as a model. Model copies all parameters of an existing Control file into a designated target Control file. This option is useful when you need to create a set of Control files that use many of the same parameter values.! WARNING The target Control file is an exact copy of the model. All existing parameters of the target Control file are replaced by the corresponding model parameters. Both the target and model Control files must be current members of the Control file list. If they are not, add them using option 5, ADD, from the Control Files screen. See page 25 for instructions. 1. Access the CARTS Control Files screen by selecting option 1 from the Main Menu. 2. Select option 4, MODEL, from the Control Files screen. The Control file list shown in the following figure appears after selecting option 4. CARTS Select Model Control File ROW 1 OF 3 COMMAND ===> User Id-PROD To select the Control file to be copied, place the cursor on the desired file name or description and press ENTER. Description / Data Set Name Daily Stacking Control File CTS.CTS360.CNTL Weekly Control file XYZ1.CTS360.CNTL Weekend Stacking Control File CTS.CTS360.WKEND Vaulting Control File CTS.CTS360.VAULT 3. Select the Control file you want to use as the model by placing the cursor on the name or description of the model Control file and press ENTER. You will be presented with another Control file list. 4. Select the target Control file by placing the cursor on the name or description of the Control file and press ENTER. CARTS TMS User Guide 23

34 Chapter 3 CARTS Control File The following screen appears to confirm the request. CARTS CONFIRM OPERATION COMMAND ===> User Id-PROD XYZ1.CTS360.CNTL Weekly Control file is about to be overwritten with data from PROD.CTS360.CNTL Backup of Weekly Control file Press ENTER to PROCEED. Press PF3 to CANCEL. 5. Press ENTER to confirm the model request or enter END from the command line to cancel it. You return to the Control Files screen. 24 CARTS 3.6.0

35 Control File Menu 5 ADD Adding a File to the Control File List Use this option to add an existing Control file to the Control file list. ADD should be used to migrate your existing Control files to a new release of CARTS. Also, the ADD option can be used to add Control files from other CARTS components to the list. CARTS retains the existing Control file list after migrating to a new release. Make sure that you are in the appropriate Control file list for the release of CARTS that you are running. Refer to 7 MASTER Specifying a New Master Control File List on page 27 for instructions to specify the correct Control file list. If you want to create a completely new Control file, use option 2, CREATE. See 2 CREATE Creating a New Control File on page Access the CARTS Control Files screen by selecting option 1 from the Main Menu. 1. Select option 5, ADD, from the CARTS Control Files screen. The following screen appears with fields to select the Control file to add to the list. CARTS Add Control File to List COMMAND ===> User Id-PROD To add an existing Control file to the master list: Enter the required information below and press ENTER. Data set name ===> Description ===> 2. Enter the dataset name of the new Control file and a description up to 50 characters long. Both the Control file dataset name and description appear on the Control file list. A message appears at the upper right corner of the screen that indicates a Control file has been added. 3. Press PF3 to exit and return to the Control File menu. CARTS TMS User Guide 25

36 Chapter 3 CARTS Control File 6 DROP Removing a File from the Control File List DROP removes a Control file from the Control file list. DROP only removes the file from the list. It does not delete the Control file dataset from disk. 1. Access the CARTS Control Files screen by selecting option 1 from the Main Menu. 2. Select option 6, DROP, from the CARTS Control Files screen. The Drop Control File From List screen appears with a list of current Control files. CARTS Drop Control File From List ROW 1 OF 3 COMMAND ===> User Id-PROD To remove a Control file from the list, place the cursor on the file name or description and press ENTER Last Updated Description / Data Set Name Date Time User ID Daily Stacking Control File 04/21/ :11 PROD CTS.CTS360.CNTL Weekly control file 04/21/ :15 PROD XYZ1.CTS360.CNTL Weekend Stacking Control File 04/21/ :35 PROD CTS.CTS360.WKEND Vaulting Control File 04/21/ :14 PROD CTS.CTS360.VAULT 3. Select the Control file you want drop by placing the cursor on the name or description of the Control file and press ENTER. A message appears at the upper right corner of the screen that indicates the Control file has been dropped. 4. Press PF3 to exit back to the Control File menu. 26 CARTS 3.6.0

37 Control File Menu 7 MASTER Specifying a New Master Control File List MASTER specifies the name for a new master Control file list dataset 1. Access the CARTS Control Files screen by selecting option 1 from the Main Menu. 2. Select option 7, MASTER, from the Control Files screen. The Specify Master List Name screen appears with a field to enter the name of the dataset containing the Control file master list. CARTS Specify Master List Name COMMAND ===> User Id-PROD Enter the name of the data set containing the master list of control files below. Enter the name fully qualified without apostrophes or quotation marks. Master list data set name ===> PROD.CTS360.CNTFLIST 3. Enter the dataset name of your new Control file list. The dataset name should be fully qualified. Do not use quotes. Note: If you migrated from an earlier release of CARTS, you may need to change the default Master Control File list dataset. For example, if you have migrated from Release 3.57 to 3.60, you need to change hlq.cts357.ctlflist to hlq.cts360.ctlflist on the dataset name field of this screen. 4. Press PF3 to exit back to the Control File menu. CARTS TMS User Guide 27

38 Chapter 3 CARTS Control File Changing Stacking Conditions Control file parameters select which datasets and tapes are stacked by CARTS. A Control file also specifies the conditions of CARTS stacking jobs. You change these parameters with a set of options selected from the Rules screen. The Rules screen and its options are the subject of this section. A dataset or tape volume must meet all selection criteria specified by Control file. A single parameter mismatch disqualifies a dataset or volume from stacking. Select option 4, RULES, from the CARTS Main Menu to display the Selection Rule Categories screen shown in the following figure. There are eight categories of selection criteria to select or exclude candidates for stacking. CARTS Selection Rule Categories Control file: PROD.CTS360T.CNTL TMS Default Control File Choose one of the categories listed below: 1 CRITERIA Date ranges, cycle control, etc. 2 EXECUTION Scratch pool options, job numbering, etc. 3 DSNAMES Data set names to include/exclude 4 ROBOTS Robotic unit and options 5 VOLSERS VOLSER range(s) 6 OUTCODES Off-site codes to include 7 JOB/STEP Job and Step names to include/exclude 8 ACCTCODE Accounting codes to include/exclude COMMAND ===> User Id-PROD The menu options are: 1 CRITERIA Use this option to specify rules for selecting datasets. 2 EXECUTION Use this option to control stacking operation. 3 DSNAMES Use this option to include and exclude datasets from stacking by dataset name. You can also use it to group datasets together as they are stacked. 4 ROBOTS Use this option to specify robots to be used in stacking. 5 VOLSERS Use this option to specify the volser ranges of tapes to be stacked. 6 OUTCODES Use this option to specify TMS outcodes of tapes to be stacked. 7 JOB/STEP Use this option to include and exclude datasets from stacking by creating job and step names. 8 ACCTCODE Use this option to include and exclude datasets from stacking by the accounting codes of their creating jobs. 28 CARTS 3.6.0

39 Changing Stacking Conditions 1 CRITERIA Selection Criteria Use the Selection Criteria screen to set the conditions that select datasets for stacking. 1. Select option 1, CRITERIA, from the Rules menu. 2. Specify input fields. The fields are described following the example figure of the Selection Criteria screen. 3. Press PF3 to exit and save your changes. CARTS Selection Criteria COMMAND ===> User Id-PROD Control file: PROD.CTS360.CNTL Default Control File DATE Minimum days since creation ===> 000 (Exclude if less) SELECTION Maximum days before expiration ===> 999 (Exclude if more) Minimum days since last access ===> 000 (Exclude if less) Maximum days since last moved ===> 999 (Exclude if more) Creation date range ===> thru Maximum days elapsed between creation and last access ===> 999 (Exclude if less) OTHER Cartridges or reels ===> C (C or R) CRITERIA Cataloged or uncataloged data sets ===> C (C or U) Data sets due to be vaulted ===> IGN (INC/EXC/IGN) Stack cycle controlled tapes ===> YES (Yes/No) Stack files with blksize = 0 ===> YES (Yes/No) Stack files with blksize > ===> YES (Yes/No) Stack files with block count = 0 ===> YES (Yes/No) Minimum file size (megabytes) ===> Maximum file size (megabytes) ===> Input Fields of the Selection Criteria Screen Minimum days since creation Include only datasets for stacking that have been created at least nnn days ago. Place zeros in this field to include all datasets as candidates for stacking. Maximum days before expiration Exclude any dataset that expires in less than nnn days. The default, 999, includes all datasets as candidates for stacking. Minimum days since last access Exclude any dataset that has been accessed (created, read, or modified) within the last nnn days. Place a zero in this field to include all datasets as candidates for stacking. Maximum days since last moved Include any dataset that has moved within the last nnn days. The default, 999, includes all datasets. CARTS TMS User Guide 29

40 Chapter 3 CARTS Control File Creation date range Julian date range that datasets were created. Only datasets created within this range are included in stacking jobs. The first two digits of the beginning and ending dates specify the century the dataset was created. 00 or 19 20th century creation date 01 or 20 21st century creation date The default range, thru , includes all datasets for stacking in the 20th century. Examples and All datasets created in both the 20th and 21st centuries and All datasets created in the 21st century and All datasets created in the 20th century Use the Minimum days since creation field to dynamically set an include date range. Maximum days elapsed between creation and last access Number of days between a dataset s creation date and most recent access. Exclude datasets that have been accessed within this number of days of their creation date. The default, 999, includes all datasets for stacking. Cartridges or reels Type of tape media (cartridge or reel) of the output volume containing stacked datasets. This field is ignored by Media Conversion. C Cartridge tape. The default. R Reel tape. Cataloged or uncataloged datasets Status of datasets, cataloged (C) or uncataloged (U), that are included in stacking jobs. Catalog status (C) is the default. Restacker and Media Conversion ignore this field. Both components are able to process cataloged and uncataloged datasets during the same job. Cataloged and uncataloged datasets are separated and then Restacker and Media Conversion run the stacking routine twice to place cataloged and uncataloged datasets on separate volumes. Data sets due to be vaulted Choice to include or exclude datasets from stacking that are scheduled to be vaulted. INC Include datasets designated for vaulting. If you specify INC, the vaulting status of the dataset is verified with the TMS TMC before it is included. This option applies only to datasets scheduled to be vaulted. It does not apply to datasets that are already vaulted and have an offsite code. 30 CARTS 3.6.0

41 Changing Stacking Conditions EXC Exclude datasets designated for vaulting. If you specify EXC, the vaulting status of the dataset is verified with the TMS TMC before it is excluded. IGN Ignore the current vaulting status of a dataset and include the dataset for stacking. IGN is the default. If you specify IGN, be sure to use the Dataset Names screen to isolate and stack datasets with similar vaulting patterns. Also, edit the Location screen to specify which TMS location codes should be included in stacking Stack cycle controlled tapes Choice (YES or NO) to include or exclude datasets from stacking with cycle controlled retention. YES Stack Cycle control datasets and datasets with other kinds of retention. Cycle control datasets are stacked together. YES is the default. NO Exclude datasets with cycle retention from stacking. Stack files with blksize = 0 Choice (YES or NO) to stack datasets with a block size of 0 in the TMC. YES Stack datasets with a block size of 0 in the TMC. This option is intended for datasets whose format has been altered from the MVS standard by a vendor product like FDR. A block size of 0 in the TMC indicates the dataset has a non-standard format. YES is the default. NO Exclude datasets from stacking with a block size of 0. Stack file with blksize > Choice (YES or NO) to stack datasets with a block size greater than YES Stack datasets with a block size greater than This option is intended for datasets whose block size exceeds the MVS maximum of Several vendor products can create datasets with block sizes that exceed the MVS maximum. YES is the default. NO Exclude datasets from stacking with a block size greater than Stack files with block count = 0 Choice (YES or NO) to stack datasets with a block count of 0 in the TMC. YES Stack datasets with a block count of 0. This option is intended for datasets created by several vendor products that can have a block count of 0. NO Exclude datasets from stacking with a block count of 0. CARTS TMS User Guide 31

42 Chapter 3 CARTS Control File Minimum file size (megabytes) Minimum size of a dataset in megabytes (lower limit) that CARTS considers as a stacking candidate. A dataset is eligible for stacking if its size is in the range specified by the Minimum and Maximum file size fields. The default minimum dataset size is megabytes. Maximum file size (megabytes) Maximum size of a dataset in megabytes (upper limit) that CARTS considers as a stacking candidate. A dataset is eligible for stacking if its size is in the range specified by the Minimum and Maximum file size fields. The default maximum dataset size is megabytes. 32 CARTS 3.6.0

43 Changing Stacking Conditions 2 EXECUTION Execution Options The Execution Options screen sets the operating conditions of CARTS tape stacking jobs. 1. Select option 2, EXECUTION, from the Rules menu. The figure shown below is an example of the Execution Options screen. The fields are described following the figure. 2. Specify input fields, as you like. 3. Press PF3 to exit and save your changes. CARTS Execution Options COMMAND ===> User Id-PROD Control file: PROD.CTS360.CNTL Default Control File Number of scratch tapes needed ===> Minimum scratch pool to maintain ===> Dual Copy ===> NO (Yes/No) Job numbering ===> YES (Yes/No) - Starting column within jobname ===> 7 (2 to 8) - Number of digits ===> 2 (1 to 7) Number of concurrent jobs ===> 004 Bypass dependency checking ===> NO (Yes/No) Reject files pending stacking ===> NO (Yes/No) Pending stack timeout interval 01 : 00 (HH : MM or DA, MO, or YR) Input Fields of the Execution Screen Number of scratch tapes needed Number of scratch tapes created each time you run CARTS-TS. Stacking jobs are created until CARTS-TS estimates this number of scratch tapes will be created. The default is , which creates the maximum number of possible scratch tapes. Use the Minimum scratch pool to maintain field instead to create the required number of tapes needed in your scratch pool with the fewest number of CARTS-TS jobs. If you supply a value for Number of scratch tapes needed field, the Minimum scratch pool to maintain field is ignored. The value set with the Number of scratch tapes field is ignored by Restacker and Media Conversion stacking jobs CARTS TMS User Guide 33

44 Chapter 3 CARTS Control File Minimum scratch pool to maintain Minimum number of tapes to maintain in the scratch pool. CARTS-TS creates stacking jobs until the minimum number of scratch tapes within the pool is attained. The default, , creates the maximum number of possible scratch tapes. CARTS-TS subtracts the number of current tapes within the scratch pool (in the volser ranges selected for this Control file) from the minimum threshold number to calculate the number of needed scratch tapes. For example, if you specify 300 in this field and you currently have 275 tapes in the scratch pool, CARTS-TS generates enough jobs to reclaim an additional 25 scratch tapes. If you want to reclaim a specific number of scratch tapes each time you run CARTS-TS, use the Number of scratch tapes needed field. The Minimum Scratch Pool field is ignored unless the Number of scratch tapes field is set to This field is always ignored by Restacker and Media Conversion stacking jobs. Dual Copy Choice (YES or NO) to create a duplicate of each stacked tape. YES Dual copy datasets are given the same name as the original dataset. They are not cataloged. File 1 is given permanent expiration. Dual copy datasets are expired by the History File update procedure (UPDTHIST) when their corresponding original datasets have expired. NO Duplicate stacked tapes are not created. Job numbering Choice (YES or NO) to automatically assign numbers to CARTS-TS submitted jobnames when executing multiple, concurrent jobs. YES CARTS-TS increments the job name (some positions of which must be numeric) to create unique job names. To have concurrent executions, you must specify Yes in the Job Numbering field and a number greater than 1 in the Number of concurrent jobs field. NO Numbers are not assigned to CARTS-TS job names. Starting column within jobname Starting column position within the jobname to insert unique job numbers. Column 1 is considered to be at the first character of the job name. The Job numbering field must be set to Yes. Number of digits Length of a numeric sequence inserted into a jobname to create unique names to identify multiple, concurrent stacking jobs. The Job numbering field must be set to Yes. 34 CARTS 3.6.0

45 Changing Stacking Conditions The job name must have numbers in the inidcated positions. Job names are specified in the Job Cards screen. In the event of a conflict between the starting position or number of digits, a pop-up help window appears when you submit the stacking job. The pop-up help window allows you to change the job name on the job card or the starting position and number of digits to be inserted into the job name. Number of concurrent jobs Maximum number of concurrent stacking jobs. Each stacking job requires two tape drives. If you request Dual Copy, each job requires three drives. You must specify Yes on the Job Numbering field to assign unique jobnames to support concurrent stacking jobs. Bypass dependency checking Choice (YES or NO) to exclude datasets from Dependency file checking as they are stacked. Bypassing Dependency file checking allows a stacking job to complete in a shorter period of time. However, there is a possibility that tape volumes may contain datasets that are required by the same job step, or contain MOD datasets that are not placed at the end of the tape. Bypassing Dependency file checking is intended for archive tapes that are unlikely to be read again. NO is the default. Reject files pending stacking Choice (YES or NO) to exclude datasets from pending stacking jobs that have been selected as stacking candidates by a prior job. NO is the default. Excluding datasets that have been selected by an earlier stacking job prevents abends. These abends could occur if the second pending CARTS-TS job attempts to stack a dataset that is no longer at the specified location when the job was submitted because the previous job has already stacked the dataset. You can view the datasets of your pending stacking jobs with the History Inquiry utility. Chapter 5 Using the History Inquiry on page 73 describes how to select and view pending dataset records from the History file. Pending stack timeout interval Interval that pending dataset records are retained in the History file. Specify the length of interval in hours and minutes (HH:MM), days (xx:da), months (xx:mo), or years (xx:yr). The time-out interval begins when the stacking job is submitted. The default value is 00:00. If you receive a Value out of range message, enter a numeric value between 01 and 24 on this field. Pending records are deleted from the History file if the dataset has not been stacked within the time-out interval or the dataset was stacked. Refer to Pending Dataset Detail Screen on page 74 for more information about pending stack records in the History file. CARTS TMS User Guide 35

46 Chapter 3 CARTS Control File 3 DSNAMES Selecting by Dataset Names The Dataset Names screen is used to include or exclude datasets from stacking by their name. You can also use this screen to group datasets together. Datasets that are members of the same group are stacked together on the same tape. No other datasets are stacked as part of the group. This is useful for grouping datasets together on stacked volumes with a similar functions or security authorization. Datasets can be identified by using wildcard characters. 1. Select option 3, DSNAMES, from the Rules menu. CARTS Data Set Names Row 1 to 26 of 26 COMMAND ===> User Id-PROD Control file: PROD.CTS360.CNTL Default Control File INCLude/EXCLude Statements Opt Grp INC 002 * CTS360. TEST. FILE 2. Enter a separate line on the screen for each dataset generic you want to include or exclude from stacking. Input fields are described following the example figure of the Data Set Names screen. CARTS-TS takes the first include match it finds. Code the most specific INClude statements towards the top and the most general INClude statements towards the bottom. Exclude statements can be entered in any order on the Data Set Names screen. There must be at least one statement entered on the Data Set Names screen. The screen above shows an example of the default entry. Each INC statement specifies candidate datasets for stacking based upon their name. Datasets whose names match the name template specified by the INC statement are candidates for stacking. Likewise, datasets whose name matches the name template specified by the EXC statement are excluded from stacking. You can specify up to 25 entries at a time. If you need to specify more than 25 entries: code 25, press PF3 to exit the screen, then access the screen again to continue adding entries. You can enter up to a maximum of 3,000 entries per job. 3. Press PF3 to exit and save your changes. 36 CARTS 3.6.0

47 Changing Stacking Conditions Input Fields of the Data Set Names Screen Opt Choice to include (INC) or exclude (EXC) datasets from stacking by their name. If only EXC entries are entered, CARTS-TS excludes only those datasets that match the criteria. All other datasets are included. If any of your entries specify INC, CARTS-TS includes only datasets that match the rules for the Control file and a name specified here. If both EXC and INC statements are entered, CARTS-TS selects datasets that match the rules for the Control file and at least one include statement but do not match any exclude statements.: Opt Grp INC 001 * This entry matches all datasets. Any dataset that is not named by another INClude or EXClude statement will be controlled by this statement. Grp qualifiers Group number to combine datasets when they stacked to an output volume. It is available for included datasets only. Specify the names of all the datasets you want to group together. Then, assign them the same group number. The minimum group number is 001. Name(s) of dataset(s) to include or exclude from stacking. You can select a range of datasets using wildcards with their names. Briefly, the rules for specifying dataset names are: Specify names in qualifier segments. You may leave any qualifier blank. Trailing wildcards are implied. Use a period to indicate the end of a qualifier. Use a wildcard character (*) to indicate a single character within a dataset name. See Generics and Wildcards on page 14 for more information about wildcard usage. CARTS TMS User Guide 37

48 Chapter 3 CARTS Control File Examples of Stacking by Dataset Name This example shows how to group payroll datasets (PAY) accounts payable (AP) datasets to stack them on separate tape volumes. In this example, the prefix of the name indicates the dataset s function. Give the payroll datasets the group number 001. Assign all AP datasets group number 002. Place the following entries on the Data Set Names screen: Opt Grp INC 001 PAY INC 002 AP This creates PAY and AP dataset groups. It also excludes all other datasets from being stacked as members of these two groups. Other datasets need to be stacked. Add another INClude statement to select all remaining datasets and assign it group number 003. Now, all other datasets are candidates for stacking. Opt Grp INC 001 PAY INC 002 AP INC 003 * In this example, inventory datasets should be excluded from stacking. These datasets all begin with GEO. An EXClude statement is added at the bottom to exclude inventory datasets. Opt Grp INC 001 PAY INC 002 AP INC 003 * EXC GEO 38 CARTS 3.6.0

49 Changing Stacking Conditions 4 ROBOTS Controlling Robotic Use The Robotic Units and Options screen sets CARTS-TS stacking conditions for volumes mounted on tape robots. 1. Select option 4, ROBOTICS, from the Rules menu. The following figure is an example of the Robotic Units and Options screen. 2. Enter values on screen fields. Screen fields are described following the figure of the screen. 3. Press PF3To exit and save your screen changes. CARTS Robotic Units and Options COMMAND ===> User Id-PROD Control file: PROD.CTS360.CNTL Default Control File Robotic vendor ===> NONE (NONE, ACS, ATL, or GRAU) INPUT must be in robot ===> NO (Yes/No) OUTPUT to robot ===> NO (Yes/No) Immediate scratch ===> NO (Yes/No) Enter IDS of robotic units to participate in stacking/restacking Input Fields of the Robotic Units and Options Screen Robotic vendor Name of the tape robot vendor. Use the following values: ACS ATL GRAU NONE StorageTek Memorex (SUTMYN) Grau (Bosch) No robots are installed. Also, specify none for the IBM families of MagStar automated tape library products. The default. If you specified NONE on the Robotic vendor field, the following three fields of the Robotic Units and Options screen are set to NO. CARTS TMS User Guide 39

50 Chapter 3 CARTS Control File INPUT must be in a robot Choice (Yes or No) to stack input datasets residing on volumes mounted on a robot. Yes CARTS-TS stacks only datasets from volumes mounted on robots. No CARTS-TS stacks only datasets located outside of robots. OUTPUT to a robot Choice (Yes or No) to stack output datasets to volumes mounted on a robot. Yes CARTS-TS stacks to the robot identified by the esoteric specified for the Robotic Unit field of the VOLSER Group screen. No CARTS-TS stacks to a non-robotic tape unit identified by the esoteric specified on the Non-robotic Unit field of the VOLSER Group screen. A mixed environment occurs when values set in the Robotic Input and Robotic Output fields are different; YES/NO or NO/YES. In a mixed environment, CARTS-TS writes to a scratch tape rather than to an active volume (starting with File 2) because input volumes are not physically available to be used as output volumes. Immediate scratch Choice (Yes or No) to scratch input tapes as soon as all datasets have been successfully stacked. CARTS-TS informs the robot of the availability of new scratch tapes after stacking has occurred. Robotic IDs Yes No Input tapes are immediately scratched as soon as they are successfully stacked. (Tapes are given a scratch date of ) Immediate scratch is only available for cartridges resident in a robot. Input tapes become available as scratch when you run the TMS scratch job. Identity of the robot(s) you want CARTS-TS to use for input or output volumes. CARTS-TS verifies these IDs with your robot software. You can specify up to an 8-character ID, depending upon the robot manufacturer. All IDs must be left-justified. Use the keyword ALL to process volumes in all robots. If your site uses a StorageTek robot, enter the ACS string identifications. For CARTS purposes, an individual robotic ID consists of 3 characters: a 2-digit ACS number and a 1-digit module number representing the LSM within the ACS. For example, a 3-character ACS#LSM# would be 001 to identify ACS00/LSM1. If you use a Memorex (SUTMYN) robot, enter the ATL names. 40 CARTS 3.6.0

51 Changing Stacking Conditions 5 VOLSERS VOLSER Ranges The VOLSER Ranges screen is used to create or modify input tape volume groups. The VOLSER Ranges screen also includes a field to select an input group for a stacking job. Datasets are candidates to be stacked if the volumes they are stored on belong to the group selected from the VOLSER Ranges screen. There are two VOLSER Ranges screens. The VOLSER Ranges Submenu screen shown below lists active groups. Entering a group number on the Enter a volser group number for output field selects the volumes belonging to the group as stacking candidates. The characteristics of the group specify how datasets on the input group volumes are stacked to output volumes. The VOLSER Group screen shown on page 42 appears after entering a group number (1-8) on the Enter a volser group number to update field. You can either edit an existing group or add a new group by entering an unused group number. A number for a new group can be selected in any sequence (1-8). Selecting an Input Volume Group 1. Select option 5, VOLSERS, from the Rules menu. Active VOLSER groups are listed (from 1 to 8) on the VOLSER Ranges Submenu screen. 2. Enter the group number of an active group on the Enter a volser group number for output field. The datasets on the volumes that belong to the selected group are candidates to be stacked. CARTS VOLSER Ranges Submenu COMMAND ===> User Id-DRP1 Control file: PROD.CTS360.CNTL Default Control File Enter a volser group number to update ======> (1 thru 8): Enter a volser group number for output =====> 1 (1 thru 8): Group Description Number 1 VOLSER GROUP Press Enter to select the single volume group. CARTS TMS User Guide 41

52 Chapter 3 CARTS Control File Adding or Modifying a VOLSER Group 1. Enter a group number on the Enter a volser group number to update field. The following figure shows an example of the VOLSER Group screen that appears after entering a group number. The figure shows the default values when a new group has been selected. CARTS VOLSER Group COMMAND ===> User Id-PROD Description ===> VOLSER GROUP 1 Group is active ===> YES Max DSNs per output tape ===> Virtual Footage ===> (output tape capacity) Max percentage of tape used ===> 99 (exclude if higher) Robotic Unit ===> 3490 Non-robotic Unit ===> 3480 Output storage class ===> (to be assigned to output tapes) VOLSER Ranges (used for input selection only) From AAAAAA to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to 2. Enter values into the fields at the top half of the screen. Descriptions of each screen field begin on page Enter volser ranges in the appropriate fields shown at the bottom half of the screen. VOLSER ranges are used only to select input tape volumes for stacking. Volume serial ranges specified from the VOLSER Ranges screen must adhere to the following conventions: All six alphanumeric characters of the volume serial must be specified for the beginning and ending volumes of the range. The beginning volser must be less than or equal to the ending volser. Alphabetic characters are less than numbers; Z is less than 0. A volser range can consist of a single volume. The same volser is specified for the beginning and ending volumes of the range. Specify AAAAAA to to include all possible volsers for stacking. If you want CARTS to stack only a portion of your tape library, specify a limited range of volsers. Normally, you should you set the largest possible range of volsers on this screen and limit the number of stacking jobs by other means. For example, limit the number of 42 CARTS 3.6.0

53 Changing Stacking Conditions stacking jobs by setting a small number of scratch returns see 2 EXECUTION Execution Options on page Press PF3 to exit and save your changes. Input Fields of the VOLSER Group Screen Group is Active Choice (YES or NO) to activate or deactivate the specified input volume group. An active group is listed on the VOLSER Ranges Submenu screen. The characteristics of the group specify how CARTS stacks datasets on the output volumes. An inactive group is a defined set of volumes that do not participate in CARTS stacking. Inactive groups do not appear on the VOLSER Ranges Submenu. Max DSNs per output tape Maximum number of datasets that can be stacked on a single output tape volume. Stacking datasets to a volume stops when a tape has stored the maximum number of files, even if more space is still available on the tape. The default maximum number is If this field is 09999, CARTS-TS continues stacking datasets until the entire length of the tape is recorded. On average, there are usually no more than ten datasets stored on a tape. It is conceivable however, that many more small files could be stacked on a single tape. This field allows you to set a reasonable limit on the number of datasets stacked on a volume to minimize the potential risk of losing a large number of datasets if the tape was destroyed or inadvertently overwritten. Virtual footage Virtual footage of the output tapes that will store stacked datasets. The default virtual footage is The physical length of 3480-compatible tape cartridges is typically between 380 and 1100 feet. However, if you are using 3490 or 3490E-compatible drives, data can undergo hardware compaction as it is stored on tape. For example, if your drives provide an average 2:1 compaction ratio, a 520 foot tape stores as much data as a 1040 foot tape without compaction. In this example, the virtual footage of the tape volume is CARTS-TS estimates the number of datasets to stack based on the virtual footage of the output volume. If your drive is capable of 2:1 compaction, and you specify the physical length of 520, your tapes will be recorded only up to half of their capacity. If you specify 1040, CARTS can stack the full tape length to obtain the greatest benefit from hardware compaction. The table shown on page 44 is intended only as a reference. Standard compaction ratios of 2:1 and 3:1 are used to calculate the virtual footage. However, compaction ratios vary from one drive type to another. Refer to your tape drive documentation for the correct ratio. Contact your cartridge provider for the actual length of your tapes. CARTS TMS User Guide 43

54 Chapter 3 CARTS Control File Virtual footage is ignored for reel tapes. All reels are assumed to be 2400 feet in length. TABLE 1. Tape Cartridge Specifications Tape Footage Compaction Tape tracks Capacity in Megabytes Virtual Footage 520 no 18 track yes-2:1 18 track no 36 track yes-2:1 36 track no 18 track yes:2:1 18 track no 36 track yes-2:1 36 track MagStar no 128 track Magstar yes-3:1 128 track Calculating Virtual Footage The following formula is used to calculate the virtual footage (VF) of tape media not listed in the table above. You must know the storage capacity of the tape in megabytes (Mb). VF = Mb/210 * 520 Round the calculated virtual footage down to next lowest 1000 feet. Example You have a tape with a compacted capacity of 50 Gb, or 50,000 Mb. VF = Mb/210 * 520 VF = 50,000/210 * 520 VF = 123,760 or 123,000 rounded down to next lowest 1000 feet. Maximum percentage of tape used Discontinue stacking when the contents of an output tape volume exceed more than nn percent of its capacity. This percentage is calculated by a tape s virtual footage. For example, if you specify 50%, CARTS stacks datasets to the volume until it reaches half of its capacity and then stops. The default is 99%. Robotic Unit Esoteric name of the robot to be used for stacking input and output volumes when you have specified Robotic Input-YES on the Robotic Units and Options screen. You can specify any esoteric, whether it is a robot or not. This esoteric may refer to external drives or robot drives at an external location, such as a vault, or even a local robot. Refer to the installation worksheet for tape esoterics assigned at your site. 44 CARTS 3.6.0

55 Changing Stacking Conditions Non-robotic Unit Esoteric unit name of the stacking input tape drives when you have specified Robotic Input-NO on the Robotic Units and Options screen. You may specify any esoteric, whether it is a robot or not. This esoteric may refer to external drives or robot drives at an external location, such as a vault, or even a local robots. Refer to the installation worksheet for tape esoterics assigned at your site. Output storage class Name of the SMS storage class assigned to the output tape(s) created by the stacking job. VOLSER Ranges You can enter up to 24 volser ranges for each group. Ranges apply only to input volumes. Volser ranges must adhere to the following coding conventions: Ranges are used only to include volumes for stacking Ranges do not have to be entered in ascending order Blank entries are ignored The 'FROM' VOLSER volume must be less than or equal to the 'TO' VOLSER volume The 'TO' VOLSER volume must be equal to or greater than the 'FROM' VOLSER volume A range can consist of a single volser entered as both the beginning and ending volume CARTS TMS User Guide 45

56 Chapter 3 CARTS Control File 6 OUTCODES Selecting by TMS OutCodes This option specifies up to 16 TMS outcodes (or offsite codes) that identify remote locations. Tape volumes stored at these remote locations can be stacked if vaulted datasets are stacking candidates. Tape volumes are considered as stacking candidates when their location s outcode matches the selection criteria entered from the OutCodes screen and you did not specify automatic exclusion of vaulted tapes on the Selection Criteria screen. 1. Select option 6, OUTCODES, from the Rules menu. CARTS Out Codes COMMAND ===> User Id-PROD Control file: PROD.CTS360.CNTL Default Control File Enter the off-site codes ("out codes") to be included in the stacking or restacking operation 2. Enter the TMS outcode on the fields near the middle of the screen. If 4-character TMS outcodes are entered on these fields, only those volumes stored at the specified locations are candidates to be stacked. Alternatively, you can select locations by leaving the fields blank, using wildcards, or using the ALL parameter. blank If all off-site code fields are left blank on the OutCodes screen, all TMS volumes without a specified offsite code are candidates to be stacked. wildcards The Outcodes screen supports implied and explicit wildcards. For example: A*** All offsite codes beginning with A are selected. A**1 All offsite codes beginning with A and ending with 1 are selected. ALL If ALL is entered on the first outcode field, volumes from all TMS outcode locations are candidates to be stacked. 3. Exit and save your changes. 46 CARTS 3.6.0

57 Changing Stacking Conditions 7 JOB/STEP Job and Step Names The Job and Step Names screen includes or excludes datasets from stacking based upon their creating job or job step names. The screen is divided into quadrants. You enter the job or step name in the appropriate quadrant to either include or exclude datasets from stacking. Include Job Names (Up to 48 names) Exclude Job Names (Up to 48 names) Include Step Names (Up to 16 names) Exclude Step Names (Up to 16 names) If you specify a job or step name to include, all job or step names that are not included are excluded from stacking. 1. Select option 7, JOB/STEP, from the Rules menu. CARTS Job and Step Names COMMAND ===> User Id-PROD Control file: PRODCTS360.CNTL Default Control File INCLUDE JOBNAMES I EXCLUDE JOBNAMES Enter up to 48 reating JOBNAMEs Enter up to 48 creating JOBNAMEs of of datasets that should be included datasets that should be excluded for stacking. fromstacking. JOBNAMES are entered left-justified JOBNAMES are entered left-justified with with embedded wildcards (*) embedded wildcards (*) INCLUDE STEPNAMES I EXCLUDE STEPNAMES Enter up to 48 creating Enter up to 48 creating STEPNAMEs of STEPNAMEs of datasets that datasets that should be excluded from should be included for stacking. stacking. STEPNAMES are entered STEPNAMES are entered left-justified left-justified with embedded with embedded wildcards (*) wildcards (*) 2. Specify job and step names, up to 8 characters each. You may use wildcards (*) to specify any character in a single position. Trailing wildcards are implied. 3. Exit and save your changes. CARTS TMS User Guide 47

58 Chapter 3 CARTS Control File 8 ACCTCODE Accounting Codes The Accounting Codes screen includes or excludes datasets from stacking based upon the accounting codes of their creating jobs. 1. Select option 8, ACCTCODE, from the Selection Rules Categories screen. CARTS ---==== Accounting Codes COMMAND ===> User Id-PROD Control file: XYZ1.CTS360.CNTL Weekly Control file ---INCLUDE Accounting CodesS------I EXCLUDE Accounting Codes On this side of the screen you can enter up to 100 accounting codes of datasets that you want to include as candidates for stacking. On this side of the screen you can enter up to 100 accounting codes of datasets that you want to exclude as candidates for stacking. The accounting code can be up to 37 characters in length and can include single-position wildcards (*). The accounting code can be up to 37 characters in length and can include single-position wildcards (*). 2. Specify accounting codes of the datasets you want to include or exclude from stacking. Substitute asterisks for every comma in the accounting code. For Example, if your accounting code is 123,ABCD,400 type 123*ABCD*400 on this screen. 3. Exit and save your changes. 48 CARTS 3.6.0

59 Changing Job Statements Changing Job Statements Use the Job Cards screen to edit the JCL that submits Stacker and Restacker stacking jobs. 1. Select option 5, JOBCARDS, from the CARTS Main Menu. CARTS Default Job Cards User Id-PROD Control file: XYZ1.CTS360.CNTL Job Card for Foreground Job Submission //BPDJOB JOB (TSC),'CARTS JOB',CLASS=A,MSGCLASS=X, // MSGLEVEL=(1,1),NOTIFY=&SYSUID //PROCLIB JCLLIB ORDER='PROD.CTS360.PROCLIB' Job Card 1 - Specific Expiration Dates //BPD000 JOB (TSC),'CARTS JOB',CLASS=A,MSGCLASS=X, // MSGLEVEL=(1,1),NOTIFY=&SYSUID,TYPRUN=HOLD //PROCLIB JCLLIB ORDER='PROD.CTS360.PROCLIB' Job Card 2 - Catalog and Cycle Control //BPD000 JOB (TSC),'CARTS JOB',CLASS=A,MSGCLASS=X, // MSGLEVEL=(1,1),NOTIFY=&SYSUID,TYPRUN=HOLD //PROCLIB JCLLIB ORDER='PROD.CTS360.PROCLIB' Job Card 3 - Permanent Expiration Dates //BPD000 JOB (TSC),'CARTS JOB',CLASS=A,MSGCLASS=X, // MSGLEVEL=(1,1),NOTIFY=&SYSUID,TYPRUN=HOLD //PROCLIB JCLLIB ORDER='PROD.CTS360.PROCLIB' 2. Edit the job cards shown on the screen. The job cards are used for different types of CARTS-TS stacking jobs. JOB Card Foreground job submission The Stacker or Restacker job that is submitted from a CARTS ISPF screen. Job Card 1 Jobs that stack datasets with specific expiration dates. JOB Card 2 Jobs that stack datasets under catalog and Cycle control. JOB Card 3 Jobs that stack datasets with permanent expiration. Begin each job statement with // that follows standard JCL coding conventions. Each job statement may contain up to four lines. Job names must be 4-8 characters long. You should include the TIME=1440 parameter in all jobs to prevent 322 abends. For Job statements 1, 2, and 3, some part of the job name may be required to be numbers. For example, CARTS000. Numbers are required as part of job names when multiple, concurrent stacking jobs are submitted. The starting position and number of digits of the numeric sequence included within a job name are specified from the Starting Column and Number of digits fields of the Execution Options screen. CARTS TMS User Guide 49

60 Chapter 3 CARTS Control File Avoid specifying job names that conflict with job numbering required for concurrent stacking jobs. If a conflict occurs, a message appears indicating the job name must be changed. 3. Press PF3 to save your changes and return to the Main Menu. 50 CARTS 3.6.0

61 Chapter 4 Meeting Stacking Objectives This chapter describes how to prepare CARTS-TS Control files to complete common tape library tasks. Each section in this chapter includes a typical situation that shows practical uses of CARTS-TS stacking. Procedures are included that describe the steps to set Control file parameters and adapt stacking for this particular task. Most sites need several Control files. The following list shows typical dataset categories that require individual Control files to enable CARTS stacking: cataloged datasets in a robot uncataloged datasets in a robot cataloged datasets on cartridges outside a robot uncataloged datasets on cartridges outside a robot cataloged datasets on reels uncataloged datasets on reels You can create special Control files for other tasks that need to be completed as part of managing your site s tape library. For example, many sites create separate Control files for the following tasks: weekend backups dataset grouping on stacked volumes vault datasets CARTS TMS User Guide 51

62 Chapter 4 Meeting Stacking Objectives Testing a Control File This section explains how to test new Control file parameters. All Control files should be tested before running any CARTS job that actually stacks tape datasets. 1. Select a Control file from the Control Files List screen. 2. Edit and change any Control file parameters available from the options listed on the Rules screen. 3. Select option 3, SUBMIT, from the Main Menu. The Job Submission screen appears. An example of the Job Submission screen is shown on page Specify YES on the Reports Only field of the Job Submission screen. When you specify Reports Only-YES, CARTS-TS creates a set of reports that describe how your tape library will be stacked with these Control file parameters. The job does not actually stack datasets. The reports give you the opportunity to evaluate the effect Control file values have on stacking before submitting any jobs. 5. Enter 1 to submit a Stacker or 2 to submit a Restacker job from the Job Submission screen and press ENTER. CARTS-TS submits a job to generate stacking JCL. The submitted CARTS job and its JES job number appear on the screen. IKJ56250I JOB CARTSTST JOB003039) SUBMITTED *** 6. Press ENTER at the *** prompt to return to the Job Submission screen. See Submitting Stacking Jobs from CARTS-TS ISPF Screens on page 53 for more information about submitting online CARTS-TS jobs. 7. Review the CARTS-TS reports in your SYSOUT log. The Summary report, CARTSRPT04, CARTSRPT14, and CARTSRPT99 may be the most helpful. 8. If you are satisfied with the results, change the Reports Only field to NO on the Job Submission screen and resubmit the job to perform actual stacking. Otherwise, repeat this procedure and continue modifying your Control file and checking the reports until you are satisfied with the results. 52 CARTS 3.6.0

63 Running CARTS-TS Running CARTS-TS You can submit CARTS-TS Stacker and Restacker jobs from batch or ISPF screens. Both methods are discussed in the following sections. If you submit the jobs to the hold queue (your job statements specify TYPRUN=HOLD), you must release them in JES job order. Unpredictable results can occur if you release jobs out of sequence. Submitting Batch Stacking Jobs CARTS-TS stacking jobs are submitted in batch using the STACKER procedure. Submit a job like the example shown below to execute this procedure. Specify the name of your Control file with the CNTL parameter. //jobname JOB valid job statement //STEP1 EXEC STACKER,CNTL='carts.control.dsn' Restacker jobs can be submitted in batch using the RESTACK procedure. Use a job like the example shown below to execute the RESTACK procedure. Specify the name of your Control file with the CNTL parameter. //jobname JOB valid job statement //STEP1 EXEC RESTACK,CNTL='carts.control.dsn' Submitting Stacking Jobs from CARTS-TS ISPF Screens Submitting CARTS-TS Stacker or Restacker jobs from ISPF is slightly different than submitting batch jobs. CARTS-TS uses the current, active Control file to submit a job from ISPF. If you changed any Control file parameters before submitting a job, CARTS-TS uses the modified values for the execution of that job. You do not have to save your Control file changes before submitting a job. The changes remain in effect for a single execution of a job. Submitting from ISPF is an effective way to test new Control file parameter values. You should always perform a reports-only evaluation job to test new Control file values. If the results from the evaluation job are acceptable, you can resubmit the procedure and actually create stacking jobs. If the results are unacceptable, continue modifying Control file parameters and run reports-only jobs. For more help on testing your Control file, refer to Testing a Control File on page 52. CARTS-TS creates a temporary Control file dataset based on the values currently specified in the ISPF screens. The temporary Control file dataset has the following naming convention: your-tso-id.carts35n.dyyddd.thhmm.fn The ending n is a program-supplied sequence number. You can submit as many jobs as you like, as quickly as you like. The jobs do not interfere with each other. Complete the following procedure to submit a CARTS job from the Job Submission screen: CARTS TMS User Guide 53

64 Chapter 4 Meeting Stacking Objectives 1. Access the CARTS Main Menu. 2. Select option 3, SUBMIT, from the Main Menu. The Job Submission screen appears after selecting option 3. This example shows a standard Job Submission screen without Media Conversion being installed. When Media Conversion is installed, the Job Submission screen includes options 3 and 4 to submit Media Conversion jobs. You can see an example of the Job Submission screen that includes the additional options on page 109. CARTS Job Submission COMMAND ===> _ User Id-USR1 Control file: PROD.WEEKLY.CF1 Weekly Control File -- Unrestricted (everything) Choose one of the following jobs to submit: 1 STACK Stacker 2 RESTACK Restacker Reports only? ===> YES YES for simulation run NO to generate JCL 3. In the Reports only field, specify YES to run only analysis and generate reports, or NO to create the reports and perform actual stacking. 4. Enter a 1 on the command line to submit the a stacking job. Enter 2 to submit a restacking job. A message appears confirming that a CARTS-TS job was submitted with the assigned JES job number. 54 CARTS 3.6.0

65 Using Restacker Using Restacker CARTS-TS Restacker examines the TMS TMC to find volumes containing more than one dataset. Restacker maintains the original job name, step name, expiration date, and creation date and time in the TMC. If a tape contains any dataset that is excluded from restacking, Restacker does not process the volume. Restacker submits a restacking job if two or more tapes are found with expired datasets. The restacking job combines two or more volumes onto a scratch tape and returns empty input volumes to the scratch pool. If the input datasets were cataloged, Restacker recatalogs them to the new volser. You control restacking conditions with parameters set in the CARTS-TS Control file. You should use the same Control file to stack and restack the same tape volumes. Using the same Control file minimizes potential conflicts that could occur as a result of restacking datasets that were originally from volumes created by stacking jobs with different operational parameters. Not all stacker Control file values pertain to Restacker. Refer to Changing Stacking Conditions on page 28 for a description of Control file values that are affected by Restacker jobs. You can submit Restacker jobs online or in batch. Submitting online is explained in Submitting Stacking Jobs from CARTS-TS ISPF Screens on page 53. Unstacking a Stacked Tape with Restacker This procedure explains how to use Restacker to unstack a stacked tape and copy each dataset to a separate tape volume. 1. Access the CARTS ISPF screens and select the Control file that stacked the tape. 2. Select all datasets on the tape volume to be unstacked by entering INC 001 * from the Data Set Names screen. All datasets must be selected on the tape volume to be unstacked. 3. Go to the VOLSER Ranges screen. 4. Specify the tape volser as the starting and ending volser in a range. You may specify multiple tape volsers if you want to unstack more than one tape. But, each tape must be the starting and ending volser in a separate range from the VOLSER Ranges screen. 5. Specify 1 on the Max datasets per output tape field of the Volser Ranges screen. Only one dataset is copied to each output tape. 6. Run a Restacker job by entering option 2 from the Job Submission screen. Each dataset on the stacked tape is copied to a separate volume. The original stacked input tape is scratched. 7. Exit the screens without saving changes to the Control file. CARTS TMS User Guide 55

66 Chapter 4 Meeting Stacking Objectives Unloading a Single File from a Stacked Volume CARTS provides the CARTSEX procedure to unload a single file from a stacked volume. CARTSEX can be found in your CARTS JCLLIB dataset. 1. Edit CARTSEX. 2. Include values for the following parameters: CNTL Name of the CARTS-TS control used to stack the dataset to the volume. VOLSER Volume serial of the stacked volume containing the dataset to be unloaded. VOLSER must be exactly six characters. If the dataset is a multi-volume dataset, specify the base volume. FILESEQ Logical file Sequence number of the dataset to be unstacked. The File Sequence number must be exactly four digits. DSN Name of the dataset to be unstacked.the name can be 1 to 44 characters long. 3. Submit CARTSEX. CARTSEX creates the CARTSRPT13 report. Examine this report to verify the file you unloaded has been moved from the stacked volume. CARTSEX maintains the current catalog status of the dataset after it is unstacked. Use the CARTSRPT13 to verify the dataset s catalog status has been maintained. 56 CARTS 3.6.0

67 Selecting Reports Selecting Reports Both CARTS-TS Stacker and Restacker produce a series of reports when jobs are submitted. Some reports are more useful during the initial testing and implementation phase of CARTS-TS. You may want to discontinue producing these reports after establishing your site s CARTS-TS operational procedures. Only the first 100 lines and the last page of each report are printed during a CARTS trial evaluation. You must obtain a CARTS license and password to produce a full set of reports. Stacker Reports By default, Stacker generates the following listed reports when a stacking job is submitted: Reports STACKER DDname STACKER Job Step CARTSRPT00 RPT3 STEP1 CARTSRPT01, CARTSRPT02, CARTSRPT04, RPT1 STEP1 CARTSRPT14 CARTSRPT03 RPT2 STEP1 CARTSRPT05 RPT05 STEP8 CARTSRPT06 RPT06 STEP10 CARTSRPT07 RPT07 STEP12 CARTSRPT08 RPT08 STEP14 CARTSRPT09 RPT09 STEP15 CARTSRPT10 RPT10 STEP16 CARTSRPT11 RPT11 STEP18 CARTSRPT19 RPT19 STEP6 CARTSRPT21 RPT21 STEP3 CARTSRPT22 RPT22 STEP5 CARTSRPT23 RPT23 STEP5 CARTSRPT99 RPT99 STEP1 Summary Report SUMMARY STEP13 The CARTS Reports Manual gives a description of each report and report field. You can edit STACKER located in the CARTS procedure library and change the reports that you want to generate when you submit a stacking job. Discontinuing a Report and Resuming a Report on page 58 explain how to modify the JCL to generate specific reports with your stacking jobs. CARTS TMS User Guide 57

68 Chapter 4 Meeting Stacking Objectives Restacker Reports By default, Restacker generates the following listed reports when a restacking job is submitted: Reports CARTSRPT01 CARTSRPT02 CARTSRPT04 CARTSRPT14 CARTSRPT01 CARTSRPT02 CARTSRPT04 CARTSRPT14 RESTACK DDname RPT1 RPT1 The CARTS Reports Manual gives a description of each report and report field. You can edit RESTACK located in the CARTS procedure library and change the reports that you want to generate when you submit a restacking job. Discontinuing a Report and Resuming a Report on page 58 explain how to modify the JCL to generate specific reports with your restacking jobs. Discontinuing a Report This procedure explains how to stop producing selected reports when you submit CARTS stacking or restacking jobs. 1. Edit the STACKER or RESTACK members of the CARTS procedure library. These procedures actually run CARTS stacking and restacking jobs. 2. Search for the DDname corresponding to the number of the report you want to discontinue. DDnames and job steps for each report are listed on page Change the report DD statement to read: //ddname DD DUMMY,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=2660) Resuming a Report RESTACK Job Step STEP1 Selects Files 1 from multi-file tapes STEP3 Selects Files 2 and up from tapes selected in STEP1 CARTSRPT11 RPT11 STEP15-Pull List of volumes to be stacked. CARTSRPT13 RPT13 STEP9 Cataloged files CARTSRPT13 RPT13 STEP11 Uncataloged files CARTSRPT99 RPT99 STEP3 Reports rejections for Files 2 and up from tapes selected in STEP3 To resume printing a report, do the following. 1. Edit member STACKER or RESTACK of the CARTS procedure library. 2. Search for the ddname corresponding to the number of the report you want to resume. 3. Change the report DD statement to read: //ddname DD SYSOUT=&OUT 58 CARTS 3.6.0

69 CARTS Integrity Checks CARTS Integrity Checks CARTS provides the RESETCDS and RESTCYC utilities to ensure the integrity of stacked volumes managed by TMS. RESETCDS Utility The RESETCDS utility scans the TMS TMC and locates multi-dataset volumes that are candidates to be scratched because the File 1 dataset is expired. Under TMS, multi-dataset volumes are expired by the expiration of File 1, which should have the latest expiration date of all datasets on the volume. Occasionally, File 1 is expired prematurely. As a result, the remaining datasets on the volume are at risk of being lost when the volume is scratched. RESETCDS should be run before the TMS scratch and clean job. When a multi-dataset volume is a candidate to be scratched, RESETCDS examines the volume s datasets to see if any of them are not yet expired. If an active dataset is located, RESETCDS resets the volume s expiration date to latest active dataset. This prevents the premature expiration of multi-dataset volumes when a TMS scratch and clean job is run. Using RESETCDS, you have the option to process all active volumes, or just the volumes stacked by CARTS. Also, you have the choice of running in test mode if you simply want to generate reports without actually updating the CDS of any volume. The example below shows the OPT parameter included with RESETCDS that specifies how multi-dataset volumes are updated. //* //* EXECUTE RESETCDS PROCEDURE //* //RESETCDS EXEC RESETCDS,OPT='TEST' The following OPT parameter values specify whether RESETCDS updates or simply tests volumes, and which multi-dataset volumes are selected from the TMC. OPT= 'TEST No updates only test CARTS volumes OPT='TEST,ALL' No updates, test all volumes OPT='UPDATE' Update only CARTS volumes OPT= 'UPDATE,ALL' Update all volumes OPT= 'ALL' Update all volumes RESETCDS generates the CARTSRPTS1 report. Refer to the CARTS Reports Manual for a description of the report and each report field. RESTCYC Utility Under Cycle control, CARTS-TS stacks the dataset behind the File 1 pseudo file. CARTS-TS ensures the proper expiration of the Cycle control dataset based upon the expiration of File 1. All other datasets on a stacked Cycle controlled volume have expiration dates that occur before File 1. The RESETCYC job maintains the proper expiration of stacked datasets with Cycle control. RESETCYC examines Cycle controlled volumes to verify that File 1 has the latest dataset expiration date. If any datasets have an expiration date later than File 1, RESETCYC resets File 1 to the latest expiration date. RESETCYC scratches a stacked Cycle control volume after all of the datasets on the volume have expired. CARTS TMS User Guide 59

70 Chapter 4 Meeting Stacking Objectives RESETCYC should be scheduled to run before your scratch and clean job. Make sure the values for the CDAY and CJOB parameters agree with the corresponding parameter values in the TMS TMOOPTxx. See your CARTS-TS installation worksheet for RESETCYC scheduling. RESETCYC generates the following reports: CARTSRPT25 CARTSRPT31 CARTSRPT32 CARTSRPT33 Refer to the CARTS Reports Manual for a description of the report and each report field. 60 CARTS 3.6.0

71 Setting the Number of Concurrent Stacking Jobs Setting the Number of Concurrent Stacking Jobs You determine how many stacking jobs can execute concurrently with Control file parameters. You can set stacking parameters to execute either a single job, or multiple, concurrent jobs. 1. Access the CARTS-TS Main Menu and select a Control file. 2. Select option 4, Rules, from the Main Menu. 3. Select option 2, EXECUTION, from the Rules screen. 4. Specify the number of concurrent jobs you want to run in the Number of concurrent jobs field of the Execution Options screen. Each stacking job requires separate input and output drives. 5. Specify YES on the Job Numbering field to initialize job numbering. CARTS creates unique job names to identify stacking jobs that run at the same time. A repetitive sequence of numbers is inserted into the job names. You set the length of the numeric sequence and the starting position within the job name to insert the numbers. 6. Assign numeric values to the Starting column and Number of digits fields. Unique job numbers are inserted into the name of each stacking job. 7. Ensure the length and starting position of the numeric sequence are correct when inserted into Stacker job names. 8. Go to the Job Cards screen and change the job names for job statements 1-3. CARTS TMS User Guide 61

72 Chapter 4 Meeting Stacking Objectives Limiting the Number of Stacking Jobs CARTS-TS could generate potentially hundreds of stacking jobs if allowed complete access to your site s tape library. Running this many jobs is impractical at most data centers. Use any of the following standard methods to limit the number of CARTS-TS stacking jobs: Limit the number of scratch tapes returned using the Minimum scratch pool or Number of scratch tapes fields on the Execution Options screen. CARTS-TS runs just enough jobs to create the required number of scratch tapes.this is recommended method to limit the number of stacking jobs. Limit the number of datasets available for stacking by setting a narrow creation date range with the Creation date range or Minimum days since creation fields of the Selection Criteria screen. Limit the number of datasets available for stacking by entering fairly complete names on the fields of the Dataset Names, Job/Step Names, or Accounting codes screens. Limit the number of input tapes that can be stacked by selecting a narrow range of volsers from your library with the VOLSER Ranges screen. 62 CARTS 3.6.0

73 Controlling Input/Output Type Controlling Input/Output Type The output tape drive that stacks datasets is designated by esoteric values set in two fields of the VOLSER Group screen. The Robotic Unit field selects the stacking robot when you have specified Robotic Output-YES. Use the Non-robotic Unit field instead when you have specified Robotic Output-NO. You can specify any tape esoteric for either field, regardless of whether it is robot or not. This esoteric may refer to a local or remote drives. The esoteric can even refer to a remote robot at a vault. Refer to the installation worksheet for the esoterics assigned to tape drives at your site. Also, you specify whether reel or cartridge tapes are selected for stacking with the Cartridges or reels field of the Selection Criteria screen. CARTS-TS always stacks from reel to reel or cartridge to cartridge. Use CARTS Media Conversion instead to stack datasets from one type of tape media to another. CARTS TMS User Guide 63

74 Chapter 4 Meeting Stacking Objectives Migrating to Tape Drives That Support Compaction If your site is migrating from 3480 drives to newer 3490 or 3490E-compatible drives that support compaction, changes must be made to your existing uncompacted tapes. Because of limitations of compaction-enabled drives, CARTS can stack datasets only on scratch tapes, or to a tape that was originally created with compaction. Follow the listed recommendations to migrate your existing stacked uncompacted volumes to drives that support compaction: Discontinue stacking uncompacted tapes and only stack to compacted tapes. Specify the date compaction was implemented for all new tape datasets as the from date on the Creation Date Range field of the Selection Criteria screen. Use CARTS-TS to stack uncompacted tapes to scratch volumes and create compacted tapes. Use Media Conversion to convert your multi-file uncompacted tapes. This is the only option that can convert multi-volume tapes. There are a two ways to stack to a scratch tape using CARTS-TS. Remember, when you run stacking jobs, compaction must be enabled. Use Restacker to restack multi-file volumes. Restacker always copies datasets to a scratch tape. All multi-file volumes are candidates for Restacker, regardless if they were originally stacked by CARTS or not. Use Restacker to convert your existing multi-file volumes. If you have tape robots, prepare a mixed environment so that CARTS-TS stacks to a scratch tape. Go to the Robotic Units and Options screen and specify different values, YES and NO, for the INPUT must be in a robot and OUTPUT to a robot fields. It does not matter which field is YES and NO, either combination creates a mixed stacking environment. All that matters is that the fields have different values. Verify the Robotic Unit and Non-Robotic Unit fields of the Volser Range screen are correct for your environment. The input tape uses the UNIT parameter in the CARTS-TS generated JCL, as follows: Robotic Input-YES: Robotic device Robotic Input-NO: Non-robotic device The output (scratch) tape will use the UNIT parameter in the CARTS-TS generated JCL as follows: Robotic Output-YES: Robotic device Robotic Output-NO: Non-robotic device No matter whether you are stacking to scratch or active tapes, you should also change the Virtual Footage value, on the Execution Options screen. 64 CARTS 3.6.0

75 Obtaining a Pull List Before Stacking Obtaining a Pull List Before Stacking Complete the following procedure to pull tapes before running stacking jobs. 1. Place the TYPRUN=HOLD parameter on your CARTS-TS job statements. 2. Submit CARTS-TS and print the Pull List, CARTSRPT11, from the reports in SYSOUT. 3. Release the stacking jobs from the hold queue when you have collected the required tapes. Release the jobs in the same order they were submitted to JES. CARTS TMS User Guide 65

76 Chapter 4 Meeting Stacking Objectives Grouping Datasets on Stacked Volumes CARTS-TS stacks datasets selected by a Control file together on a selected number of output tape volumes. By default, CARTS-TS adheres to the following conventions when datasets are combined to create a stacked, multi-dataset volume: Place datasets with similar expiration dates on the same volume Maximize tape capacity by selecting a combination of datasets that use the largest percentage of tape footage. Place MOD datasets only at the end of a tape Stack datasets needed by the same job step on different volumes Group datasets from the same site identified by a TMS outcode on the same volume You have the choice to stack datasets together in a group. You can group datasets two ways: Create a Control file that selects only the limited number of datasets you want stacked together Group datasets by name on the stacked output volume Both methods are implemented from the Dataset Names screen. See 3 DSNAMES Selecting by Dataset Names on page 36 for more information. 66 CARTS 3.6.0

77 Scratch Tape Shortages Scratch Tape Shortages Most sites occasionally suffer from scratch tape shortages. Usually, scratch tape shortages become apparent during regularly scheduled backups. The procedure included in this section describes how to use CARTS-TS to create enough scratch tapes to complete daily batch backup jobs. The procedure explains how to create a sufficient number of scratch volumes based upon a site s daily backup requirements. Monday through Saturday, 200 scratch tapes a day are needed. On Sunday, 400 tapes are required to do full volume DASD backups. Complete the following procedure to generate the required number of daily scratch tapes: 1. Create two Control files. Control File 1 regulates stacking jobs that run from Monday through Saturday. Control File 2 is used with stacking jobs that provide enough scratch tapes for a full volume DASD backup done on Sunday. 2. Set the Minimum Scratch Pool field of both Control files to the number of scratch tapes needed for that day s backups. For Control File 1, specify 200. For Control File 2, specify Set the Number of scratch tapes field to in both Control files. Setting the value to disables the field s control over the number of returned scratch tapes. All other parameters may be set as you like. 4. Make two copies of the job that executes your batch STACKER procedure. Specify Control File 1 for one and Control File 2 for the other. 5. Schedule the jobs to run Sunday through Friday and Saturday, respectively. (See Submitting Batch Stacking Jobs on page 53.) CARTS-TS generates stacking jobs until the minimum number of scratch tapes are produced (200 and 400). CARTS-TS calculates the number of tapes required for the scratch pool by subtracting the number of currently available scratch tapes from the daily minimum. CARTS-TS stops stacking when the required number of daily scratch tapes have been created. CARTS TMS User Guide 67

78 Chapter 4 Meeting Stacking Objectives Inconsistent Scratch Tape Availability Scratch tape availability fluctuates according to a site s backup schedule. In the middle of the month there may be a plentiful supply of scratch tapes. The number of scratch tapes may dwindle toward the end of the month with larger monthly backup jobs. Most sites need to develop a strategy to run the minimum number of CARTS-TS jobs to maintain enough volumes in the scratch pool to complete all scheduled backup jobs. The strategy must account for restrictions in the number of tape mount requests that can occur during the work week. One solution is to run larger stacking jobs on the week end when systems are most idle. This section describes how to setup separate stacking jobs that are run during standard work days and on the week end. The stacking job run Monday through Friday recovers 200 scratch tapes. The week end job recovers 300 scratch tapes because there are enough available systems resources to run more stacking jobs. You implement CARTS-TS as follows. 1. Set up a Control file with Number of scratch tapes set to 200. CARTS-TS will produce stacking jobs until it returns 200 scratch tapes. Run this Control file on weekdays, from the 21st to the 4th. 2. Create another Control file, with Number of scratch tapes set to 300. Run this Control file on weekends, from the 21st to the 4th. From the 5th to the 20th of the month, your scratch pool is fine. You do not need to run CARTS-TS.- 68 CARTS 3.6.0

79 Reducing the Number of Off-Site Volumes Reducing the Number of Off-Site Volumes The following procedure explains how to reduce the number of volumes sent to an off-site vault. Reducing the number of off-site volumes can provide significant savings with reduced transportation costs and more scratch tapes returned at the local site. The procedure consists of a two-step process. The first step stacks only designated vault datasets. After that, all other eligible datasets are stacked to local volumes because the vault datasets have been already filtered out. 1. Prepare a Control file to stack only vaulted datasets. Enable all datasets as stacking candidates by entering INC on the Datasets to be vaulted field of the Selection Criteria screen. Select only those datasets you want sent to the vault with INClude and EXClude statements on the Dataset Names screen. Run a daily stacking job with this Control file to create stacked volumes that are sent to the vault. 2. Prepare another Control file to handle all remaining stacking jobs. Specify EXC on the Datasets to be vaulted field to exclude vaulted datasets. You do not need to select datasets with INCludes or EXCludes entries on your Dataset Names screen. CARTS TMS User Guide 69

80 Chapter 4 Meeting Stacking Objectives Electronic Vaulting The following procedure explains how to stack datasets directly from a robot at your local site to a remote drive located at a vault. Remote stacking eliminates shipping costs to transport tapes to the vault. To implement electronic vaulting, you need an on-site robot and a tape drive at your remote vault linked by a channel extender. 1. Create a Control file that selects datasets to be stacked at the vault. Reducing the Number of Off-Site Volumes on page 69 explains how to prepare a Control file to vault datasets. 2. Enter YES on the Robotic Input and NO on the Robotic Output fields of the Robotic Units and Options screen. 3. Go to the Volser Ranges screen and specify the following fields: Robotic Unit Specify the esoteric of the local robot that will be used for input. Non-Robotic UnitSpecify the esoteric of the remote drive at the vault. 4. Use this Control file to stack datasets directly to a remote drive located at your vault. 70 CARTS 3.6.0

81 Implementing Security on Stacked Volumes Implementing Security on Stacked Volumes You may have to make changes to Control files based upon the requirements of your site s security system. Typically, tape security is enforced at either the volume or dataset level. Volume Level Security Users have access to all datasets stacked on the tape if security grants them access to the volume. You must ensure that only datasets with the same security authorization are stacked together. You must set your Control file parameters to stack only datasets with the same security authorization on the same volume. 1. Edit a Control file. 2. Access the Data Set Names screen. 3. Add include statements for the datasets you want protected. 4. Assign datasets with similar security authorization to the same group. If you want other datasets to be stacked together, add a generic include statement. Example: INC 100 * You can think of stacked CARTS tape volumes as if they were disk volumes (many datasets on a single volume). Setting authorization at the dataset level allows you to enforce security much more efficiently and precisely on stacked volumes. Dataset Level Security If security is enforced at the dataset level, your security system prevents unauthorized access to datasets stacked together on the same tape. As a result, dissimilar datasets can be stacked on a single output volume. No Control file changes are necessary. CARTS TMS User Guide 71

82 Chapter 4 Meeting Stacking Objectives 72 CARTS 3.6.0

83 Chapter 5 Using the History Inquiry The History File contains information about each dataset and tape volume processed by CARTS-TS. Records are added to the History File each time CARTS-TS stacks or restacks a dataset or volume. The History Inquiry utility shows the chronology of tape stacking for individual datasets or volumes. In addition to showing completed stacking data, History Inquiry can show dataset and volume information for stacking jobs that are pending; submitted jobs held in the output queue, waiting to be run. This chapter describes how to display History File records with the History Inquiry utility. A History File record contains the following information about each dataset or volume processed by CARTS-TS: current volume serial current file sequence number time stamp of stacking/restacking jobs original creation job Dual Copy volume if applicable, dual copy volume serial input volume serial input file sequence number You can access History file information by dataset name, volser, stacking date, and other parameters. CARTS TMS User Guide 73

84 Chapter 5 Using the History Inquiry Selecting History File Records This section explains how to select records from your personal History file by dataset name based upon the user ID selected during CARTS-TS installation. Viewing Other History Files on page 80 explains how to select other History files with the CARTSHSS and CARTSHSY CLISTs that are members of the CLIST dataset. The following figure shows an example of the History Inquiry screen that appears after selecting option 1, HISTORY, from the Utility Functions menu. This screen uses the names of stacked datasets or the original volser of the tape on which they were stored to select history records for viewing CARTS-TS History Inquiry COMMAND ===> _ User Id-PROD DISPLAY SELECTION CRITERIA: Data set name (DSN) ===> Volume serial ===> Type ===> A (C=cat, U=uncat, A=both, P=pending) DISPLAY SEQUENCE (sort): (Enter Y or YES next to one choice only) YES Data set name (default) Original creating jobname Original creation date Current VOLSER Previous VOLSER Date/time stacked Ascending or ===> A (A or D) descending A dataset name or volser is required to initiate the inquiry process. A partial dataset name of two characters or more can be entered on the Data set name field. Trailing wildcards are implied. If a partial dataset name is entered, History Inquiry displays all datasets that match the portion of the dataset name entered on the screen. History Inquiry further refines the record selection process by providing the Type field. A record is selected for viewing if there is a match by dataset name or volume AND the current status of datasets. Datasets can be either: C Cataloged datasets that match the dataset name or volume selection criteria. U Uncataloged datasets that match the dataset name or volume selection criteria. A All entries that match the dataset name or volume selection criteria regardless if they are cataloged or not. The default. P Pending datasets selected for a stacking job that has not yet run Choices from the Type field are mutually exclusive. The screen fields that determine the sort criteria and order that records are displayed, are described on the following page. 74 CARTS 3.6.0

85 Selecting History File Records 1. Select option 1, HISTORY, from the CARTS Utility Functions menu. 2. Specify a generic dataset name in the Data set name field or a tape volser in the Volume serial field, or both. Trailing wildcards are implied on the Data set name field. You must specify at least two characters. 3. Specify whether you want to see cataloged datasets (C), uncataloged datasets (U), both cataloged/uncataloged datasets (A), or pending datasets (P). 4. Specify the sort criteria to display datasets records by entering YES on only one of the following screen fields: Dataset name (default) Original creating jobname Original creation date Current VOLSER Previous VOLSER Date/time stacked 5. Specify whether you want datasets displayed in ascending (A) or descending (D) order based upon the sort criteria selected in step Press ENTER. The screen that appears next depends upon whether you selected one or more datasets with the selection criteria entered on the History Inquiry screen. Both screens are discussed in the following sections. CARTS TMS User Guide 75

86 Chapter 5 Using the History Inquiry Dataset Selection Screen If the name or volser you specified in the History Inquiry screen match more than one dataset, the Dataset Selection screen appears, as shown in the following figure. This screen lists all tape datasets that met the search criteria. You can select and then display the stacking history of each dataset shown on the screen CARTS-TS History Inquiry Row 1 of 8 COMMAND ===> _ User Id-DNS1 For detail display, enter S next to desired entry(s) and press END (PF3) Pending Records Data Set Name Found _ PRH.CTS360T.TESTMV1.FILE01 1 _ PRH.CTS360T.TESTMV1.FILE02 1 _ PRH.CTS360T.TESTMV1.FILE03 1 _ PRH.CTS360T.TESTMV1.FILE04 1 _ PRH.CTS360T.TESTMV2.FILE01 1 _ PRH.CTS360T.TESTMV2.FILE02 1 _ PRH.CTS360T.TESTMV2.FILE03 1 _ PRH.CTS360T.TESTMV2.FILE04 2 ******************************* Bottom of data ***************************** The example of the Dataset Selection screen shown above is for pending datasets. This example shows a Pending Records Found field that lists the number of records for each pending dataset. There is an equivalent Dataset Selection screen for cataloged/uncataloged datasets. Instead of a Pending Records Found field, the Dataset Selection screen includes two fields that show the number of records for cataloged and uncataloged datasets. 1. Place an S next to the dataset name and press your END key to select a dataset for viewing. You will receive the History Detail screen, described in the next section. 2. Press PF3 to exit from the History Detail screen after viewing the record. You return to the Dataset Selection screen where you can select another dataset. 3. Press PF3 from the Dataset Selection screen to return to the History Inquiry screen. 76 CARTS 3.6.0

87 History Detail Screens History Detail Screens There are two types of History Detail screens based upon whether you have selected datasets from the Type field by cataloged/uncataloged status, or if they are pending datasets. These screens appear after selecting a dataset from the Dataset Selection screen shown on page 76, or if only a single dataset was selected from the primary selection screen shown on page 74. Cataloged/Uncataloged Dataset Detail Screen The following History Detail screen displays individual history file records of cataloged/uncataloged datasets selected by the Type field of the Dataset Selection screen. Display fields are described following the figure. Press your END key to exit from the screen and return to the Dataset Selection screen or the primary selection screen. - (History) --- C A R T S - T S T A P E S T A C K I N G ROW 1 TO 2 OF 21 COMMAND ===> User Id-PROD REQUEST IS FOR ALL DATASETS Depress END to return to previous panel Depress RETURN to Exit Seq by DSN QUALIFIERS DATASET NAME----> CARTS.TESTME.FILE1.G0015V00 Current VOLSER: TESTME Previous VOLSER: MVSW03 Device type: CART Current File Seq: 004 Previous File Seq: 001 Footage: 9 Cataloged: NO Expiration Date: 1999/080 Records: Create Job: DMH1GN21 Dual Copy: NO Create Step: GENER Dual VOLSER: Create Date: 1999/049 Stacked at: 13:24 on 1999/053 ******************************* Bottom of data ******************************** Display Fields of the Cataloged/Uncataloged History Detail Screen Dataset Name Current VOLSER Previous VOLSER Device type Current File Seq Name of the dataset to which this record belongs. Volume serial number of the tape to which this dataset has been stacked. Original volume serial number of the tape containing this dataset prior to stacking. UNIT esoteric used to stack this dataset. Dataset file sequence number on the stacked tape. Previous File Seq Dataset file sequence number on the tape from which it was stacked. Footage Cataloged Tape virtual footage used to store this dataset. Status (YES or NO) whether the dataset is cataloged or not. CARTS TMS User Guide 77

88 Chapter 5 Using the History Inquiry Expiration date Records Create Job Dual Copy Create Step Dual VOLSER Create Date Stacked at Julian expiration date specified for the dataset when it was stacked. This field is not updated when you update your TMC. Datasets expired by Cycle control are indicated by CYCLES/nnn, where nnn is the number of stacking iterations. Number of records written when this dataset was stacked. Name of the original dataset creation job. Status (YES or NO) whether Dual Copy was requested for this stacking run. Name of the original dataset creation step. Volume serial number of the duplicate tape if Dual Copy was used. Julian creation date (yyyy/ddd) of the dataset. Time and Julian date when the dataset was stacked on this tape. Pending Dataset Detail Screen The following History Detail screen displays individual history file records of pending datasets selected by the Type field of the Dataset Selection screen. Display fields are described following the figure CARTS-TS Pending History Inquiry Row 1 of 2 COMMAND ===> _ User Id-PROD Sorted by Data Set Name PRH.CTS360T.TESTMV1.FILE02 Current Volume Job name PRH1TC10 File Sequence 2 Job number JOB00116 This record created on 1998/007 at 12:59:43 This record expires on 1997/353 at 17:21:58 Job began execution on at PRH.CTS360T.TESTMV1.FILE03 Current Volume Job name PRH1TC10 File Sequence 3 Job number This record created on 1997/351 at 17:21:59 This record expires on 1997/353 at 17:21:58 Job began execution on at ******************************* Bottom of data***************************** Display Fields of the Pending Dataset History Detail Screen Dataset Name Current Volume Job name Name of the dataset to which this record belongs. Current volume serial of the tape this dataset is stored on prior to being stacked. Name of the job to stack this dataset. 78 CARTS 3.6.0

89 History Detail Screens File Sequence Dataset file sequence number on the current volume. Job Number Number of the job to stack this dataset. This record created onjulian date and time when the stacking job was originally submitted. This record expires on Julian date and time when this record is scheduled to be deleted from the History file. Records are deleted from the History file if the dataset is not stacked within the interval specified with the Pending stack timeout interval field of the Execution Options field. The expiration date and time is calculated by adding the interval specified from the Pending stack timeout interval field to the Julian date and time when the record was originally created. Also, pending records are removed from the History file if the dataset is stacked before the time-out interval is finished. Job began execution on Julian date and time when the job started to stack this dataset. This field remains blank while the dataset remains in pending status. CARTS TMS User Guide 79

90 Chapter 5 Using the History Inquiry Viewing Other History Files By default, CARTS-TS selects the History file based upon the TSO user ID specified during installation. The CARTS CLISTL dataset contains two CLISTs that allow you to view other History files. CARTSHSY starts the CARTS-TS History Inquiry interface by selecting option 1, HISTORY, from the Utilities Function menu. CARTSHSS is a stand-alone CLIST that allows you to start the History Inquiry interface directly without first starting CARTS-TS. Both CLISTs can be edited to change the dataset name of the History file. This procedure explains how to view records from an alternative History file with the CARTSHSS and CARTSHSY CLISTs. 1. Edit either the CARTSHSS or CARTSHSY CLISTs located in the CLISTL dataset. 2. Locate the line entry that identifies the History file. The following examples show the line entries for both CLISTs. CARTSHSS /* TAILOR FILE */ SET XSPFILE = &STR('DRP1.CTS360.TMS.TAILOR') /* CARTS-TS HISTORY FILE */ SET XISTORY = &STR('PROD.CTS360.HISTORY') /*******************************************************************/ CARTSHSY /*******************************************************************/ /* */ /* THIS CLIST STARTS THE CARTS-TS HISTORY INQUIRY INTERFACE */ /* */ /*******************************************************************/ /* CARTS-TS HISTORY FILE */ SET XISTORY = &STR('PROD.CTS360.HISTORY') /*******************************************************************/ 3. Change the dataset name to the History file whose records you want to view. 4. Save your changes and exit from the editing session. 5. Invoke either CLIST. CARTSHSS Invoke the CARTSHSS CLIST using standard TSO or ISPF facilities. exec 'prod.cts360.tms.clistl(cartshss)' The History Inquire screen appears. Complete the Select or VOLSER fields to select a range of records from the alternative History file identified in the CARTSHSS CLIST. CARTSHSY Invoke the CARTSTS CLIST using standard TSO or ISPF facilities. exec 'prod.cts360.tms.clistl(cartsts)' Select option 2, HISTORY, from the Main Menu. The History Inquire screen appears. Complete the Select or VOLSER fields to select a range of records from the alternative History file identified in the CARTSHSY CLIST. 80 CARTS 3.6.0

91 Chapter 6 Mount Eliminator Mount Eliminator (CARTS-ME) is an optional CARTS component that temporarily redirects tape datasets to disk that are needed for a scheduled job. These datasets are off-loaded from disk and stacked to tape after the completion of the job. Mount Eliminator substantially reduces the number of required tape mounts at most data centers. CARTS-TS must be installed and operational before completing any of the Mount Eliminator procedures described in this chapter. See Mount Eliminator on page 6 for an introduction to some of the functions provided by Mount Eliminator. The following figure summarizes the key steps in the sequence to select (1), redirect (2), and finally off-load (3) tape datasets. The Work In Progress (WIP) table monitors the progress of datasets as they proceed through each step. CARTS TMS User Guide 81

92 Chapter 6 Mount Eliminator Preparing Mount Eliminator After you have installed Mount Eliminator, several tasks need to be completed before redirecting your tape datasets to disk. The next several sections in this chapter describe how to prepare Control files and set parameter values in Mount Eliminator s procedures and started tasks. Preparing Control Files Used by Mount Eliminator Mount Eliminator uses two Control files to specify the conditions to redirect datasets to disk and then off-load and stack them to tape. CARTS -TS Control file Determines which datasets are eligible to be redirected to disk by Mount Eliminator. Mount Eliminator can redirect only single-volume tape datasets to disk. You must select only single-volume datasets with the CARTS-TS Control file. Mount Eliminator Control file Determines the operational aspects of redirecting datasets to disk and then off-loading them to tape. For example, the Mount Eliminator Control file specifies the interval at which datasets are off-loaded to tape and which datasets, if any, to leave on disk. Both Control files are specified by setting parameters within the Mount Eliminator CARTSFST start-up procedure. Refer to CARTSFST on page 89 for instructions to specify the Control files to be used with Mount Eliminator. Customizing the CARTS-TS Control File for Use with Mount Eliminator Use the procedures discussed in Changing Stacking Conditions on page 28 to create and update a CARTS-TS Control file used by Mount Eliminator. The values within the CARTS-TS Control file select which datasets are candidates for redirection and the conditions to stack the datasets back to tape. Stacking Conditions Most CARTS-TS parameters that set stacking conditions also apply to Mount Eliminator. Most of the fields on the Volser Ranges screen apply, such as Max datasets per output tape, Dual Copy, Number of concurrent jobs and Robotic Output, However, the Minimum scratch pool and Number of scratch tapes fields are ignored. The values within these fields stop CARTS-TS stacking after the requisite number of scratch tapes have been created. Mount Eliminator runs continuously. Values set from the fields of the Robotics screen also apply to Mount Eliminator. Set the conditions for the Mount Eliminator jobs from the Job Cards screen. You can run a reports only job to test stacking by setting the Reports Only field of the Job Submission screen All parameters on the Selection Criteria screen (Minimum days before expiration, Stack cycle controlled tapes) are ignored. 82 CARTS 3.6.0

93 Preparing Mount Eliminator Parameters on the Accounting codes, Job/Step Names, and Location Codes screens are also ignored. The include/exclude statements on the Dataset Names screen can be used to select datasets for redirection Datasets for Redirection A tape dataset must meet the following requirements to be redirected to disk by Mount Eliminator: dataset must be stored on a single tape volume (no multi-volume datasets) dataset matches the selection criteria specified in the CARTS-TS Control file used by Mount Eliminator dataset DD statement specifies or defaults to DISP=(NEW,CATLG) dataset UNIT parameter specifies an esoteric specified for Mount Eliminator processing dataset with a LABEL parameter can only include file number 1 A dataset with any other file number is excluded. No EXPDT=98000 is coded dataset has four or more entries in the Mount Eliminator Block table dataset is within the size limit specified in the Mount Eliminator Control file Datasets are excluded from redirection by Mount Eliminator if the dataset s JCL contains the following: A LABEL parameter that includes a file number greater than 1. For example, LABEL=(2,SL,9000) A DD statement with a VOL parameter associated with it except VOL=(,RETAIN). CARTS TMS User Guide 83

94 Chapter 6 Mount Eliminator Customizing the Mount Eliminator Control File Use the following procedure to customize the Mount Eliminator Control file. 1. Select option 6, CONTROL, from the CARTS Main Menu. The CARTS Mount Eliminator menu appears after selecting option 6 from the Main Menu CARTS Mount Eliminator COMMAND ===> _ User ID PROD File maintenance 1 CONTROL Control file selection and maintenance Status Displays 6 STATUS Mount Eliminator general status 7 WIP Mount Eliminator Work in Progress Table 8 BLOCKTAB Mount Eliminator Block Table 9 DIAG Mount Eliminator general diagnostics 10 TRACE Mount Eliminator trace table 2. Select option 1, CONTROL, from the Mount Eliminator menu. Mount Eliminator s Control Files menu appears with the same options that are used with other CARTS Control files Control Files COMMAND ===> _ User ID PROD Choose one of the following options: 1 SELECT Open an existing control file 2 CREATE Create a new control file 3 DELETE Delete a control file 4 MODEL Initialize a control file using an existing file 5 ADD Add an existing control file to the master list 6 DROP Remove a control file from the master list 7 MASTER Specify master list data set name 84 CARTS 3.6.0

95 Preparing Mount Eliminator 3. Select option 1, SELECT, to open an existing Mount Eliminator Control file. The Available Control Files menu appears with a list of Mount Eliminator Control files that you can select. The menu options are the same as the Control Files menu shown on page 18. If you want to create a new Control file, you must allocate and catalog a dataset. Allocate the dataset with the following attributes: DCB=(RECFM=VB,LRECL=5000,BLKSIZE=8000) SPACE=(TRK,(1,1)) Or, simply make a copy of an existing Mount Eliminator Control file and catalog the copy. A model Control file was created when Mount Eliminator was installed. The name of the dataset is listed on the IVP report. You can use the model Control file and avoid having to allocate and catalog a new file. 4. Place the cursor over the name or description of the Control file that you want to use and press ENTER. You return to the Mount Eliminator Main Menu after selecting a Control file. The REDIRECT, STACKING, and EXCEPTIONS options are now displayed from the Main Menu. After these screen options are displayed, you can select them to change the values of a Mount Eliminator Control file CARTS Mount Eliminator FILE OPENED COMMAND ===> _ User ID PROD File maintenance 1 CONTROL Control file selection and maintenance 2 REDIRECT Redirection controls 3 STACKING Stacking controls 4 EXCEPTIONS Data sets to remain on DASD Status Displays 6 STATUS Mount Eliminator general status 7 WIP Mount Eliminator Work in Progress Table 8 BLOCKTAB Mount Eliminator Block Table 9 DIAG Mount Eliminator general diagnostics 10 TRACE Mount Eliminator trace table Control file: PROD.ME.CNTL1 Mount Eliminator Control File 1 CARTS TMS User Guide 85

96 Chapter 6 Mount Eliminator 5. Select option 2, REDIRECT, from the Mount Eliminator menu. A menu appears with option fields to select your tape dataset source, target disk volume, and the maximum size of datasets that can be redirected. Maximum size data set to redirect Maximum size of datasets in megabytes that can be redirected to disk. If the average size of a dataset is larger than the maximum, the dataset remains on tape. Use this field to prevent large datasets from using a significant percentage of the available disk space is the default. Tape unit (redirect FROM) Esoteric of the tape drives that redirected datasets are off-loaded and stacked. If you want to specify more than one esoteric, Mount Eliminator checks the tape esoteric specified in the UNIT parameter of the creating JCL to determine whether a dataset should be redirected. The esoteric specified in the UNIT parameter must be one of the esoterics your installation has approved for redirection. You can specify one Mount Eliminator tape esoteric with CARTS ISPF screens. If you want to redirect datasets from more than one esoteric, you must modify the HASPXJDI member of the CARTS JCLLIB dataset. For information about modifying HASPXJDI, refer to Step 7: Update the Device Definition Table (Optional) on page 45 of the CARTS For CA-1/TMS Installation Guide. DASD unit (redirect TO) DASD esoteric that identifies the volumes that store redirected datasets. Mount Eliminator writes only to DASD volumes identified by this esoteric. Mount Eliminator redirects datasets to specified disk esoterics. These esoterics are specified from the Mount Eliminator Control file screen or in member HASPXJDI. You control the DASD volumes available to Mount Eliminator by controlling the disk esoterics it uses. To increase or decrease available disk space, increase or decrease the number of volumes defined to these esoterics. For instructions on creating or changing esoteric definitions, refer to the appropriate IBM manuals. 6. Press ENTER and return to the Mount Eliminator Main menu. 86 CARTS 3.6.0

97 Preparing Mount Eliminator 7. Select option 3, STACKING, from the Mount Eliminator Main menu. This menu provides option fields to specify the conditions to off-load and stack redirected datasets from disk back to tape CARTS Mount Eliminator COMMAND ===> _ User ID PROD What to stack -- which data sets are eligible for offloading to tape Minimum time a data set must remain on DASD before stacking ===> 01 : 14 Minimum size data set to stack ===> (HH:MM or DA, MO, or YR) (megabytes) When to stack -- offload data sets when any of the following occur Whenever this many data sets have been redirected ===> At this time interval ===> 01 : 30 (HH:MM or DA, MO, or YR) When DASD utilization reaches ===> 75 (percent) Minimum time a data set must remain on DASD before stacking Minimum time that redirected datasets must remain on disk before they can be stacked. Datasets cannot be off-loaded until they have been resident on disk for this minimum period. The default is 30 minutes expressed as 00:30. Set a long enough period to increase the likelihood that a dataset still remains on disk if it is read by a subsequent job or job step, Days are expressed as nn:da, where nn is the number of days datasets must reside on disk before they can be stacked. Months are expressed as nn:mo, where nn is the number of months datasets must reside on disk before they can be stacked. Years are expressed as nn:yr, where nn is the number of years datasets must reside on disk before they can be stacked. Minimum size data set to stack Minimum size of redirected datasets that are off-loaded and stacked after they have are resident on disk. Redirected datasets remain on disk if they are smaller than the size specified in this field. The dataset is retained according to your disk management standards, not its tape management retention. Whenever this many data sets have been redirected Maximum number of redirected datasets that can be stored on disk. Mount Eliminator begins off-loading and stacking these datasets to tape after the maximum has been reached. CARTS TMS User Guide 87

98 Chapter 6 Mount Eliminator At this time interval Time interval in hours (HH), minutes (MM), days (DA), months (MO), and years (YR) between Mount Eliminator stacking jobs to off-load and stack redirected datasets to tape. The default interval is two hours expressed as 02:00. Days are expressed as nn:da, where nn is the number of days between stacking jobs. Months are expressed as nn:mo, where nn is the number of months between stacking jobs. Years are expressed as nn:yr, where nn is the number of years between stacking jobs. When DASD utilization reaches Maximum percent usage of disk space on a volume before Mount Eliminator off-loads datasets back to tape. Percent usage is calculated for all datasets on a volume; not just Mount Eliminator datasets. The default is 99%. 8. Enter your Mount Eliminator redirection and stacking values and press ENTER. 9. Select option 4, EXCEPTIONS, from the Mount Eliminator Main menu. This menu allows you to specify the names of tape datasets that you want to redirect and keep permanently on disk. This screen displays the data set name exception table from the current control file. The entries in this table identify particular data sets that are to be kept permanently on DASD and never stacked back to tape. Whenever a data set becomes a candidate for stacking, Mount Eliminator checks it against this table. If the data set name matches any line in the table, it is not stacked. Each line represents one data set name mask. You can code up to seven dataset name qualifiers on each line. The qualifiers are compared left to right with the qualifiers in the data set name during the match process. Within each qualifier, trailing wildcards are assumed. For example, a qualifier coded as PA will match anything beginning with the letters PA -- 'PAYROLL', 'PAYABLE', and 'PA' would all be considered matches. You can restrict matches to just the characters coded by adding a trailing period. In the above example, if you coded PA. instead of PA then only PA would match. If you specify PA without a period, any qualifier beginning with the letters PA is considered a match. A blank qualifier is considered a wildcard that matches any qualifier in that position. For example, if you specify the following mask with node 2 as a blank entry: PAYROLL. PA then the following data set names would be considered as matches: PAYROLL.DAILY.PA45 PAYROLL.WEEKLY.PA60 PAYROLL.DUMMY.PA 10. Enter the name masks of the datasets that you want to exclude from redirection to disk by Mount Eliminator and return to the Main menu. Changes made to the Control file become effective the next time you start Mount Eliminator. 88 CARTS 3.6.0

99 Preparing Mount Eliminator Preparing Mount Eliminator Procedures and Started Tasks CARTSFST The following procedure explains how to select the CARTS-TS and Mount Eliminator Control files used by Mount Eliminator. The values set within these Control files become effective the next time Mount Eliminator is started. 1. Edit the CARTSFST procedure in the CARTS PROCLIB dataset. 2. Specify the dataset name of the new CARTS-TS Control file with the CNTL parameter. //* CARTS-TS STANDARD CONTROL FILE //CARTSFST PROC CNTL= PROD.CTS360.CTSCNTL 3. Specify the dataset name of the new Mount Eliminator Control file with the MECNTL parameter. //* CARTS-ME CONTROL FILE // MECNTL='PROD.CTS360.MECNTL', CARTSCHK Procedure The Mount Eliminator Check Point procedure, CARTSCHK, is a member of the CARTS PROCLIB. CARTSCHK is a started task activated by the CARTSFST. At scheduled check point intervals, CARTSCHK becomes active and performs the following tasks Writes the contents of the Block Table from memory to the Block File stored on disk. Writes the contents of the Work in Progress (WIP) table stored in memory to the check point dataset stored on disk. Sends a message to the console for the first 100 check points. After the 100th message, a final message indicates that subsequent check point messages are suppressed. Becomes quiescent until the next scheduled check point The default length of the CARTSCHK checkpoint interval is two minutes (120 seconds). If you want to change the length of the check point interval, edit CARTSCHK and set the new length of the interval in seconds with the EVERY parameter. *//* CHECK POINT INTERVAL-EVERY N SECONDS //CARTSCHK PROC EVERY='120', //* CARTS-ME BLOCK FILE DATASET NAME // BLKFILE='USR.CTS360.BLKFILE', //*! WARNING CARTSCHK must remain up (either active or in a wait) when Mount Eliminator is active. Should CARTSCHK ever abend or be inadvertently cancelled, it must be restarted as soon as possible by entering S CARTSCHK from the console. CARTS TMS User Guide 89

100 Chapter 6 Mount Eliminator CARTSDSK CARTSDSK is a started task that is initially activated by Mount Eliminator s CARTSFST start-up procedure. CARTSDSK checks the percent usage of available DASD volumes to redirect datasets. If the threshold specified in the Percentage of DASD Utilization field of the ME Control file screen has been exceeded, CARTSDSK initiates CARTSMOV to off-load redirected datasets to tape. The default DASD volume space threshold is 99% After verifying the available space on DASD volumes, CARTSDSK becomes quiescent until the next scheduled interval. CARTDSK runs at a specified time interval set by the EVERY parameter. The default interval is 180 seconds. //* EXAMINE DASD % USAGE EVERY N SECONDS //CARTSDSK PROC EVERY='180', Edit CARTSDSK and change the value of the EVERY parameter if you want to run CARTSDSK at a different interval. CARTSMOV CARTSMOV off-loads and stacks qualified redirected datasets to tape. CARTSMOV analyzes the datasets shown at the bottom half of the Work In Progress table (WIP). Qualified datasets are stacked according to values set in the CARTS-TS Control file. CARTSMOV is initiated by any of the following conditions: By the CARTS SMF IEFU83 exit when the current period is equal to or greater than the interval set with At this time interval field of the Mount Eliminator STACKING Control file screen. When the number of redirected datasets shown at the bottom half of the WIP table is equal to or greater than the value set in the Whenever this many data sets have been redirected field of the Mount Eliminator STACKING Control file screen. By CARTSDSK, if the average percent usage of DASD space meets or exceeds the threshold specified in the When DASD utilization reaches field of the Mount Eliminator STACKING Control file. CARTSMOV produces the following stacking reports: CARTSRPT01 CARTSRPT08 CARTSRPT09 CARTSRPT10 CARTSRPT15 CARTSRPT15 lists the status of every dataset analyzed in the bottom half of the WIP table. Refer to this report to see how your off-load implementation is working. If there are no datasets to off-load, the first step of CARTSMOV receives a condition code of 16 and all remaining steps are flushed. CARTSRPT15 is created in the first step and is always produced. CARTSRPT19 90 CARTS 3.6.0

101 Starting Mount Eliminator Starting Mount Eliminator The CARTSFST procedure initializes Mount Eliminator. CARTSFST is a started task and is normally run from a COMMNDxx member. Or, you can enter S CARTSFST from the console to manually start Mount Eliminator. CARTSFST starts the CARTSCHK and CARTSDSK started tasks. Progress messages are written to the console during initialization. Mount Eliminator becomes fully operational when CARTSFST ends. CARTS TMS User Guide 91

102 Chapter 6 Mount Eliminator Monitoring the Status of Mount Eliminator This section explains several online facilities to monitor ongoing Mount Eliminator activity. These facilities can be selected as options 6 through 10 of the Mount Eliminator menu CARTS Mount Eliminator FILE OPENED COMMAND ===> 6 User ID PROD File maintenance 1 CONTROL Control file selection and maintenance 2 REDIRECT Redirection controls 3 STACKING Stacking controls 4 EXCEPTIONS Data sets to remain on DASD Status Displays 6 STATUS Mount Eliminator general status 7 WIP Mount Eliminator Work in Progress Table 8 BLOCKTAB Mount Eliminator Block Table 9 DIAG Mount Eliminator general diagnostics 10 TRACE Mount Eliminator trace table Control file: PROD.ME.CNTL1 Mount Eliminator Control File 1 Displaying the Current Status After selecting option 6, STATUS, the screen shows the current operational status of Mount Eliminator CARTS Mount Eliminator COMMAND ===> _ User ID PROD Installed at TSC/DNS Mount Eliminator is presently ACTIVE It was started at 10:16:40 on 1999/021 Last Checkpoint was taken at 13:30:56 on 1999/021 Checkpoints are taken every 2 MINUTES Checkpoints taken so far 98 The status of Mount Eliminator can be ACTIVE, QUIESCING, or STOPPED. If the status is either ACTIVE or QUIESCING, the following information is also displayed from the status screen: It was started at Time and Julian date when Mount Eliminator became active. Last checkpoint was taken at Time and Julian date of the most recent Mount Eliminator check point. Checkpoints are taken every 92 CARTS 3.6.0

103 Monitoring the Status of Mount Eliminator Check point interval in seconds. This value is set with the EVERY parameter of the CARTSCHK procedure. Checkpoints taken so far Number of check points since Mount Eliminator became active. Displaying the Work in Progress Table A dataset undergoes several distinct processing steps during the period that Mount Eliminator redirects datasets to disk and then off-loads them to disk: identification as the JCL is read by MVS redirection to disk stacking to tape Mount Eliminator monitors the progress of datasets through these steps as entries in the Work In Progress (WIP) table. You can display the contents of the WIP table to find the current location of a dataset 1. Select option 7, WIP, from the CARTS Main Menu. Option 7 is displayed from the Main Menu only when Mount Eliminator is active or quiescent. The following figure shows an example of the WIP screen that appears after selecting option C A R T S - T S T A P E S T A C K I N G COMMAND ===> User Id- Depress PF3 key to return to the previous panel. DSNs awaiting creation= 3 DSNs awaiting stacking= 6 ME indicators: NO YES YES YES Job Step DDname DSName Block DASD Name Name Count VOLSER XOLDTTT1 STEPNAME OUTDD XOLD.CARTS360.TEST.FILE1 XOLDTTT5 COPYSTEP SYSUT2 XOLD.CARTS360.TEST.FILE5 XOLDTTT2 STEP1 OUTPUT XOLD.CARTS360.TEST.FILE2 ******** ******** ******** *************************************** ******* ****** XOLDTTAA STEP001 CUSTDB XOLD.CARTS360.TEST.FILE6 10 MVSW05 XOLDTTT9 SYSUT9 XOLD.CARTS360.TEST.FILE MVSW02 XOLDTTT4 IDCAMSTP OUTPUTFL XOLD.CARTS360.TEST.FILE8 68 MVSW06 XOLDTTT8 STEP5 PASSFILE XOLD.CARTS360.TEST.FILE3 144 MVSW02 XOLDTTCC STEP1 SYSUT1 XOLD.CARTS360.TEST.FILEXX 3221 MVSW01 XOLDTTBC STEP13 NMSTR XOLD.CARTS360.TEST.FILE MVSW03 The screen is divided into three major areas. The top portion of the screen includes summary and status fields: DSNs awaiting creationtotal number of datasets awaiting redirection to disk DSNs awaiting stackingtotal number of datasets that are currently redirected to disk ME indicator Processing status of SMF records used by Mount Eliminator. Possible SMF record types include 4, 5, 15, and 26 displayed in that order. Also, a Type 30 subtype 4 and 5 record can be substituted for the 4 and 5 records. CARTS TMS User Guide 93

104 Chapter 6 Mount Eliminator The remaining portion of the WIP screen is a table divided in half by a row of asterisks toward the middle of the screen. The top half of the WIP table lists the datasets awaiting redirection. These datasets have been identified as candidates for redirection but not yet written to disk. Beneath the row of asterisks is the bottom half of the WIP table. This portion of the screen lists those datasets that have been redirected and are now resident on disk. As Mount Eliminator off-loads each dataset to tape, the corresponding dataset entry is removed from the bottom half of the WIP table. If a dataset is scheduled to remain on DASD (because it is under the minimum size to off-load or its dataset name is specified for permanent residence on disk), Mount Eliminator includes the dataset in the CARTSRPT15, Mount Eliminator Dataset Disposition report and removes it from the WIP table. 2. Use the Find command to locate a specific WIP table entry. A WIP table can become very large. Mount Eliminator provides the Find command to locate a specific WIP table entry. The format of the Find command is: Find column-id data-value Find FIND can be abbreviated to F. You can retrieve the FIND command and reissue it to locate subsequent occurrences of the data-value in the table. If the search is successful, the requested line is displayed near the top of the screen. A message appears instead if the data value cannot be found. column-id Specify the name of the screen column you want the Find command to conduct the search. Valid values are: JOB or J STEP or S DDNAME or DD DSNAME or DS data-value Specify the character string to search for within the WIP. Trailing wildcards are implied; you need only to enter the first few characters of the string. Examples of the Find Command: FIND DSNAME CARTS.DEMO.FILE1 or F DS CARTS.DEMO.FILE1 If you want to skip directly to the bottom half of the WIP table that shows the list of redirected datasets waiting to be off-loaded, enter the number from the DSNs awaiting creation field on the Command line and press PF8 (page down). 94 CARTS 3.6.0

105 Monitoring the Status of Mount Eliminator Viewing the Block File The approximate size of each dataset must be known to make accurate disk space allocations for datasets redirected by Mount Eliminator. During installation, Mount Eliminator used SMF records to determine the average number of blocks written for each tape dataset. Mount Eliminator maintains this information in the Block file, which is updated with new averages for datasets that already have an entry. Datasets are not redirected until they have four or more entries in the Block file. It is safer to over-allocate than under-allocate the number of blocks required by a dataset. Mount Eliminator accepts only Block file entries that increase the average block number or leave it the same. Therefore, the average block size is not a true arithmetic mean. You can browse or edit Block file dataset entries. The following procedure explains how to display records in the Block file. Option 9, BLOCKUPD, from the CARTS Main Menu allows you to edit Block file records. You can add, delete, and change Block file records. Refer to Block File Updates on page 118 for instructions. 1. Access option 8 from the Mount Eliminator Main menu. Option 8 is displayed from the CARTS Main Menu only when Mount Eliminator is active or quiescent. The following figure shows an example of the Block file display that appears after selecting option 8 from the Main Menu. Screen fields are described following the figure C A R T S - T S T A P E S T A C K I N ROW 1 TO 22 OF 412 COMMAND ===> User Id-PROD Depress PF3 key to return to the previous panel. Average No of DSName Entry BlkCount Entries Updated PROD.CARTS360.TEST.FILEA PROD.CARTS360.TEST.FILEC YES PROD.CARTS360.TEST.FILEF PROD.CARTS360.TEST.FILEG PROD.CARTS360.TEST.FILEJ PROD.CARTS360.TEST.FILEL PROD.CARTS360.TEST.FILEM PROD.CARTS360.TEST.FILEN YES Average Blkcount Average number of blocks used to create this dataset. No of Entries Number of generations used to calculate the average block count DSName Dataset names are presented in alphabetic sequence. Generation data groups (GDGs) are shown without generation numbers. Entry Updated Indicator that shows whether this dataset entry has been updated since Mount Eliminator became active. CARTS TMS User Guide 95

106 Chapter 6 Mount Eliminator 2. Locate a specific Block file entry with the Find command. The format of the Find command is: Find column-id data-value Find FIND can be abbreviated to F. You can retrieve the command and reissue it to locate subsequent occurrences of the data-value in the table. If the search is successful, the requested line is displayed at the top of the screen. A message appears instead if the requested line cannot be found. column-id Specify the name of the column you want CARTS to search. Valid values are: AVERAGE or A No or N DSNAME or DS data-value Specify the character string to search for. Trailing wildcards are implied, so you need only type the first, identifying characters of the string. Examples of the Find Command: FIND DSNAME CARTS.DEMO.FILE1 or F DS CARTS.DEMO.FILE1 3. Scroll to the bottom of the Block file display. The summary line at the bottom indicates the total number of updates made to the Block file since Mount Eliminator became active TOTAL UPDATES TO ENTRIES CARTS 3.6.0

107 Monitoring the Status of Mount Eliminator Diagnosing Mount Eliminator Redirection Problems Option 9, DIAG, from the Mount Eliminator Main menu provides diagnostic information about problems that occur when Mount Eliminator attempts to redirect tape datasets to disk. This screen contains diagnostic information relating to Mount Eliminator internal processing. This information is intended to be used by TSC support personnel for troubleshooting purposes CARTS Mount Eliminator COMMAND ===> _ User ID PROD Date 1/21/1999 Time 13:31:32 SMF types encountered: TS Control record B090 Block table - base TS Control record 2 07DF entries 120 TS Control record updates 0 TS Control record B8 TS Control record Vault table - base 076AA418 TS Control record TS Control record 7 base 07DFE1D8 Nbr of type 7 records 1 Exits JES 07DF0CD0 CARTSM /14/ U83 80CD86D8 CARTSM /14/ U84 80CD9748 CARTSM /14/ Occasionally, some of the datasets you intended to be redirected by Mount Eliminator are never stored to disk. DIAGNOSE is a CARTS utility that produces a report showing which datasets were omitted from Mount Eliminator processing and a short explanation why they were not redirected. DIAGNOSE output is written to the system log, which you can display online or print as a permanent report. Complete the following procedure to display the online DIAGNOSE report. 1. Edit your TSO profile and change NOWTPMSG to WTPMSG. Command ===>TSO PROF WTPMSG 2. Enter diagnose from the command line of the CARTS Main Menu. Command ===>diagnose Mount Eliminator must be active to run DIAGNOSE. 3. Open up your SYSOUT log and find the report produced by the DIAGNOSE command. The example shown on page 99 is an excerpt from a DIAGNOSE report. CARTS TMS User Guide 97

108 Chapter 6 Mount Eliminator The report includes an entry for each dataset that was not redirected to disk by Mount Eliminator. The REASON field of each entry includes a short message that explains why the dataset was not redirected. Reason Explanation NO DSN ON JCL No DSN keyword on DD statement LABEL OTHER 1 SPECIFIED File sequence number on LABEL keyword is not 1 VOLUME SERIAL SPECIFIED VOLUME keyword specified on DD statement RET PERIOD INVALID FORMAT EXPDT RET format is unknown EXPIRATION DATE OF EXPDT=98000 specifies foreign tape not recognized by Mount Eliminator GENERIC UNIT MISMATCH Tape UNIT esoteric not specified for CARTS-ME BLOCK SIZE NOT NUMERIC' Dataset has invalid block size DISP NOT (,CATLG) Dataset is not cataloged. DATASET NAME No DSN keyword on DD statement NO MATCH IN BLOCK TABLE Dataset is not listed in the Block file BLOCK TABLE COUNT Dataset has less than four entries in the Block file TS CONTROL FILE DSN Dataset not selected by INCLUDE/EXCLUDE statements within CARTS-TS Control file MATCH ON VAULT TABLE Dataset has been previously designated as a vault dataset MEGABYTE SIZE EXCEEDED Dataset exceeds the maximum size that can be redirected to disk 98 CARTS 3.6.0

109 Monitoring the Status of Mount Eliminator =====DISPLAY ACTIVE SYSTEM NAME OF IPO51B =====DISPLAY OF LOCAL IMAGE MOUNT ELIMINATOR AS OF ON LOCAL IMAGE OF MOUNT ELIMINATOR IS CURRENTLY UP STARTED AT ON LAST CHECK POINT TAKEN AT ON CHECK POINTS ARE BEING TAKEN EVERY 2 MINUTES TOTAL CHECK POINTS TAKEN IS 4 ARE SMF RECORD TYPE 04 BEING PROCESSED? - YES ARE SMF RECORD TYPE 05 BEING PROCESSED? -YES ARE SMF RECORD TYPE 15 BEING PROCESSED? - YES ARE SMF RECORD TYPE 26 BEING PROCESSED? - YES ARE SMF RECORD TYPE 30 BEING PROCESSED? - NO ***** ONE OR MORE SMF RECORD TYPES NOT BEING PROCESSED***** HAS CARTS-TS CONTROL RECORD TYPE 1 BEEN LOADED? YES CONTROL RECORD TYPE 1 LOADED AT A0 HAS CARTS-TS CONTROL RECORD TYPE 2 BEEN LOADED? YES CONTROL RECORD TYPE 2 LOADED AT HAS CARTS-TS CONTROL RECORD TYPE 3 BEEN LOADED? YES CONTROL RECORD TYPE 3 LOADED AT HAS CARTS-TS CONTROL RECORD TYPE 4 BEEN LOADED? YES CONTROL RECORD TYPE 4 LOADED AT 0683A080 HAS CARTS-TS CONTROL RECORD TYPE 5 BEEN LOADED? YES CONTROL RECORD TYPE 5 LOADED AT HAS CARTS-TS CONTROL RECORD TYPE 6 BEEN LOADED? YES CONTROL RECORD TYPE 6 LOADED AT HAS CARTS-TS CONTROL RECORD TYPE 7 BEEN LOADED? YES CONTROL RECORD TYPE 7 LOADED AT B8 1 TYPE 7 RECORDS LOADED BLOCK TABLE LOADED AT 06509B18 WITH 11,384 ENTRIES VAULT TABLE LOADED AT JES EXIT IS LOADED AT E0 MODULE CARTSM00 IS RELEASE ASSEMBLED 07/03/ IEFU83 IS LOADED AT 80B3E3D0 MODULE CARTSM04 IS RELEASE ASSEMBLED 01/21/ *****IEFU84 IS NOT RECEIVING CONTROL***** ******NO LU 6.2 TRANSMISSIONS HAVE BEEN RECEIVED MOUNT ELIMINATOR TRACE TABLE ENTRIES FOLLOW TRACE TABLE ENTRY CREATED ON AT JOBNAME==>PRODTME1 STEPNAME=>GENDATA DDNAME===>SYSUT1 DSN======>PROD.CTS360S.APFLIB STEP #===>009 REASON===>GENERIC UNIT MISMATCH TRACE TABLE ENTRY CREATED ON AT JOBNAME==>PRODTME1 STEPNAME=>GENDATA DDNAME===>SYSUT1 DSN======>PROD.CTS360S.APFLIB STEP #===>008 REASON===>GENERIC UNIT MISMATCH CARTS TMS User Guide 99

110 Chapter 6 Mount Eliminator Tracing Mount Eliminator Activity The TRACE option screen contains diagnostic information about datasets selected for redirection to disk. This information is intended to be used by TSC support personnel for troubleshooting purposes CARTS Mount Eliminator Row 1 of 25 COMMAND ===> _ User ID PROD Date 1999/021 Job CICT410 Step CICS Step nbr 001 Time 13:21:23 DDname PC@OPTN Dsname PIE.CICT410.PIE320.PC@OPTN Reason rejected Non-tape data set (unrecognized unit) Date 1999/021 Job CICT410 Step CICS Step nbr 001 Time 13:21:23 DDname PC@REPS Dsname PIE.CICT410.PIE320.PC@REPS Reason rejected Non-tape data set (unrecognized unit) Date 1999/021 Job CICT410 Step CICS Step nbr 001 Time 13:21:23 DDname PIESEQFI Dsname PIE.CICT410.PIESEQF Reason rejected Non-tape data set (unrecognized unit) Date 1999/021 Job CICT410 Step CICS Step nbr 001 Time 13:21:23 DDname PIESEQFO Dsname PIE.CICT410.PIESEQF Reason rejected Non-tape data set (unrecognized unit) 100 CARTS 3.6.0

111 Stopping Mount Eliminator Stopping Mount Eliminator CARTSFDN and CARTSFIM are procedures located in the CARTS PROCLIB. Both procedures stop Mount Eliminator. Enter S CARTSFDN from the console to shutdown Mount Eliminator under normal conditions. CARTSFDN does not immediately terminate Mount Eliminator processing. Instead, a message is issued that indicates Mount Eliminator termination is pending. After the message is issued, Mount Eliminator does not accept any further datasets for redirection. Mount Eliminator has become quiescent. During this quiescent period, Mount Eliminator continues to process datasets registered in the WIP table, off-load datasets, and take check points. At each check point, the CARTSCHK procedure checks the WIP table to see if there are any datasets that have been targeted for redirection that are still awaiting creation. These datasets are listed in the top half of the WIP table. CARTSCHK then issues a message displaying the number of these datasets remaining in the WIP table. When CARTSCHK sees that all of these datasets have been redirected to disk (moved to the bottom half of the WIP table), it takes a check point, sends a final termination message to the console, and shuts down Mount Eliminator. When Mount Eliminator becomes active again, the bottom half of the WIP table includes entries for those datasets that were redirected to disk when Mount Eliminator was shut down. Mount Eliminator off-loads these datasets to tape as part of regular processing when Mount Eliminator is started again. CARTSFIM is intended to shutdown Mount Eliminator under emergency conditions. Enter S CARTSFIM from the console to perform an immediate Mount Eliminator shut down. Respond to the immediate shutdown prompt by entering CONFIRM. Based upon the value set with the PARM parameter, CARTSFIM either clears dataset entries in the upper half of the WIP table or retains them. The default, PARM=CLEAR, clears all datasets from the upper half of the WIP table that are scheduled to be redirected to disk. When CARTSCHK becomes active again, it takes a check point, sends a final termination message to the console, and shuts down Mount Eliminator. Alternatively, PARM=NOCLEAR causes CARTSFIM to retain entries in the upper half of the WIP table. CARTSFIM shuts down Mount Eliminator in the same way as the CARTSFDN procedure. Datasets currently redirected to disk are not affected when CARTSFIM shuts down Mount Eliminator.These datasets remain on disk and are not off-loaded to tape until Mount Eliminator becomes active again, After a system IPL or a restart, Mount Eliminator restores the WIP table to its last check point. It resumes processing all datasets in the WIP table as usual. However, dataset activity occurring between the last check point and the time Mount Eliminator is started again will not be known to Mount Eliminator. Datasets that were written to disk during this time still remain on disk. If JES is warm started, datasets that were identified for redirection will still be redirected. These datasets will also remain on disk. In any case, no data is lost. These datasets simply reside on disk, not on tape. Even if Mount Eliminator has been stopped, redirected datasets are catalogued on DASD and accessible to job streams. Because access to these datasets is controlled by the MVS catalog, all access will occur from disk automatically. The datasets are retained according to your disk management standards, not their tape management retention. CARTS TMS User Guide 101

112 Chapter 6 Mount Eliminator 102 CARTS 3.6.0

113 Chapter 7 Disk Stacker CARTS-DS Disk Stacker is an optional CARTS component that migrates sequential datasets from disk and stacks them to tape. It selects datasets to be off-loaded to tape based on their name, SMS characteristics, and residency time on disk. A separate Disk Stacker Control file includes parameters that specify how datasets are migrated from disk to tape. In addition, some Disk Stacker processing is controlled by statements set within the CARTSDS job. CARTS TMS User Guide 103

114 Chapter 7 Disk Stacker Editing the Disk Stacker Control File The Disk Stacker Control file is modified with the same screens used to edit the CARTS-TS Control file. Refer to Changing Stacking Conditions on page 28 for information about changing Control file parameters with these screens. 1. Access the CARTS Main Menu and select a Disk Stacker Control file. If the Disk Stacker Control file is not listed, add it to the list, and then select it. The name of the Control file is listed on the Disk Stacker IVP report. 2. Update the values set from the menu options of the Rules menu. The following list shows recommendations for the Disk Stacker Control file. Carefully change option fields of the Dataset Names screen. Disk Stacker off-loads all files that meet your include criteria. Include only the names of those datasets you want off-loaded. Exclude all other datasets with a statement like the following: EXC * Do not prepare a Disk Stacker Control file with a single exclude statement that only excludes a portion of the datasets available on the target disks. Using this Control file parameter, Disk Stacker could potentially off-load most or all of your disk files because all of the remaining datasets are included in the stacking by default. Leave the VOLSER Ranges at the maximum possible: AAAAAA to Edit the JCL shown on the Job Cards screen to submit Disk Stacker jobs rather than CARTS-TS jobs. 4. Save your changes to the Control file. Using a New Control File The DSCNTL parameter of the CARTSDS procedure specifies the Disk Stacker Control file. Edit CARTSDS and include the dataset name of the Control file you want to use with Disk Stacker. CARTSDS is a member of the CARTS JCLLIB dataset. To create new Control files, make copies of existing Disk Stacker Control files and catalog them. 104 CARTS 3.6.0

115 Preparing the CARTSDS Procedure Preparing the CARTSDS Procedure The CARTSDS procedure was configured initially when Disk Stacker was installed. However, you must update CARTSDS parameters to select the candidate disk volumes, dataset residency requirements on disk, and their retention on tape after they are stacked. You can select candidate disk volumes by their volume serial or their SMS characteristics. The following procedure shows both methods. If you wish to select volumes by their volume serial, leave the SMSPARMS parameter blank and complete steps 3 and 4 of the procedure. Complete the SMSPARMS parameter and omit steps 3 and 4 if you want to select volumes by their SMS characteristics. 1. Edit the CARTSDS member of the CARTS JCLLIB dataset. 2. Change the following parameters of the CARTSDS procedure: AGE KEEPFOR Minimum number of days that datasets must remain on disk after their creation date. This number can range from 0 to Disk Stacker bypasses all datasets this number of days or less. For example, if you specify AGE=50, Disk Stacker bypasses all datasets 50 days old or less. Only datasets 51 days or older are off-loaded. {020 nnn CATL PERM} nnn Number of days retention for all off-loaded datasets. This number can range from 1 to For example, if you specify KEEPFOR=30, all off-loaded datasets will be retained 30 days after they are off-loaded. The default is 020. CATL PERM Disk datasets are stacked on tape and retained according to TMS catalog control expiration. Disk datasets are stacked on tape and retained by permanent expiration date. If a disk file has an expiration date set in the VTOC, this expiration date supersedes the KEEPFOR value. SMSPARMS={'MANAGEMENT=class,STORAGE=class,DATA=class'} Optional parameter to select disk datasets for stacking by their SMS characteristics. Datasets that meet all SMS selection criteria are stacked to tape by Disk Stacker. CARTSDS selects disk datasets for stacking based solely on their SMS characteristics if the SMSPARMS parameter is included. When SMSPARMS is included, CARTSDS does not use DD volume statements to select volumes whose datasets can be stacked, as shown in Step 4 of this procedure. CARTS TMS User Guide 105

116 Chapter 7 Disk Stacker Up to three SMS class sub-parameters can be included with SMSPARMS. Each sub-parameter must be separated by a comma. All sub-parameters are enclosed within a single set of quotes. MANAGEMENT1-30 character alphanumeric string that identifies disk datasets by their SMS management class. STORAGE 1-30 character alphanumeric string that identifies datasets by their SMS storage class. DATA 1-30 character alphanumeric string that identifies disk datasets by SMS data class. If SMSPARMS is specified with multiple sub-parameters, datasets are selected on the basis of a Boolean AND operation. A dataset must meet all specified SMS criteria to be selected for stacking. Examples of SMSPARMS Usage SMSPARMS='MANAGEMENT=TEMP' Only disk datasets belonging to the TEMP SMS management class can be stacked to tape by Disk Stacker. SMSPARMS='MANAGEMENT=TEMP,STORAGE=STANDARD' Only datasets belonging to both the SMS TEMP management class and the STANDARD storage class can be stacked to tape by Disk Stacker. The remaining two steps of this procedure can be omitted if you included the SMSPARMS parameter to select the target datasets. Complete steps 3 and 4 if you want to select datasets from target DASD volumes identified by their volser instead of their SMS characteristics. 3. Find the ddname DDVOL1 statement within CARTSDS. 4. Include the volsers of all DASD volumes whose datasets you want stacked to tape by Disk Stacker. A separate DD statement must be included for each DASD volume. Add as many DD statements as required. DDVOL1 DD UNIT=SYSDA,VOL=SER=MVS345,DISP=SHR DDVOL2 DD UNIT=SYSDA,VOL=SER=MVS154,DISP=SHR DDVOL3 DD UNIT=SYSDA,VOL=SER=MVS234,DISP=SHR Some names are reserved and cannot be specified as DD names. Do not include the following DD names: JOBLIB SYSUDUMP SYSABEND SYSOUT SYSIN SYSPRINT STEPLIB VTOCLIST Running Disk Stacker Execute the CARTSDS procedure of the CARTS JCLLIB dataset to run Disk Stacker. CARTSDS generates JCL to off-load qualifying disk datasets to tape similar to the CARTS-TS procedure. The job is sent directly to JES for execution. 106 CARTS 3.6.0

117 Chapter 8 Media Conversion Media Conversion (CARTS-MC) is an optional CARTS component that transfers datasets from one type of tape media to another. Typically, Media Conversion transfers datasets from reel to cartridge, or from 18 to 36-track formatted tape. Media Conversion supports tape formats compatible with the following families of tape devices: E Optical 3480/3490s Media Conversion has the capability to: convert both single volume and multi-volume datasets maintain the dataset's original statistics migrate an entire tape library in a single job or in a series of smaller jobs. Media Conversion can stack datasets or retain the existing file structure as datasets are transferred to the new tape media. Separate procedures located in the CARTS JCLLIB dataset determine the method used to transfer datasets to the output tape. CARTSMC procedure Stacks datasets as they are transferred to the new tape media. CARTSMA procedure Transfers datasets from the source tape to the destination tape without stacking. Also, both Media Conversion procedures can be submitted from the CARTS Job Submission screen. An example of the Job Submission screen on page 109 shows the options to submit both Media Conversion jobs. Functionally, both procedures operate essentially the same. The TMS TMC and MVS catalogs are updated with new volume information. This chapter describes both procedures together. CARTS TMS User Guide 107

118 Chapter 8 Media Conversion Editing the Media Conversion Control File Parameters set in the Media Conversion Control file specify how datasets are transferred to the destination tape. The same screens used to edit the CARTS-TS Control file are used to edit the Media Conversion Control file, Refer to Changing Stacking Conditions on page 28 for information about editing a Control file. 1. Access the CARTS Main Menu and select the Media Conversion Control file. If the Media Conversion Control file is not listed, add it to the list, and then select it. The name of the Control file is listed on the Media Conversion IVP report. 2. Update the values set from the menu options of the Rules menu. The following list shows recommendations for the Media Conversion Control file. Enter a trial range of volsers to do initial testing. After you are satisfied with the results of testing, update the volser range each time you run a Media Conversion job Set the fields of the Selection Criteria, Execution Options, and Robotics screens to the following values to convert the maximum possible datasets from your old range to the new: Maximum days before expiration 0 Creation date range to Max percentage of tape used 99 Max datasets per output tape Edit the job statements shown on the Job Cards screen to submit Media Conversion jobs, rather than CARTS-TS jobs. 4. Save your changes to the Control file. Using a New Control File Edit either the CARTSMA or CARTSMC procedures located in the CARTS JCLLIB to change the Media Conversion Control file. Include the dataset name of the new Control file with the MCCNTL parameter of either procedure. //EXECMA EXEC CARTSMA, //* //* CARTS-MC CONTROL FILE // MCCNTL='PROD.CTS360.MCCNTL' Make a copy of your existing Media Conversion Control file and catalog it to create a new Control file. Media Conversion uses the active Control file when jobs are submitted from the Job Submission screen shown on page 109. Select the Control file that you want to use from the Available Control Files screen before submitting the job. 108 CARTS 3.6.0

119 Running Media Conversion Running Media Conversion 1. Select the range of volsers from the VOLSER Ranges screen that you want transferred to new tape media. Refer to Editing the Media Conversion Control File on page 108 for recommendations about changing Control file parameters to run Media Conversion jobs. 2. Submit the Media Conversion job. Media Conversion jobs can be submitted by two methods. Submit the job from batch by running either the CARTSMC or CARTSMA procedure located in the CARTS JCLLIB dataset. Datasets are transferred to the new media based upon values set with the Control file specified with the MCCNTL parameter of either procedure. Select either option 3 or 4 from the Job Submission screen for the type of Media Conversion procedure to transfer datasets. CARTS Job Submission COMMAND ===> _ User Id-USR1 Control file: USR1.WEEKLY.CF1 Weekly Control File Choose one of the following jobs to submit: 1 STACK Stacker 2 RESTACK Restacker 3 MC Media Conversion with stacking 4 MA Media Conversion as is Reports only? ===> YES YES for simulation run NO to generate JCL Datasets are transferred to the new media based upon values set with the active Media Conversion Control file when the job is submitted. CARTS TMS User Guide 109

120 Chapter 8 Media Conversion Using Media Conversion with Virtual Tape Systems IBM, Storage Tek, and Sutmyn offer integrated tape systems that use a disk cache to store virtual tape volumes. The virtual volumes are formatted on disk as a tape volume, usually a 3490E. The datasets on the virtual volumes are accessible from disk rather than tape. This significantly reduces the number of mount requests and access time. Collectively, these cache tape systems are called virtual tape systems or virtual tape servers (VTS). From a system perspective, a cached virtual volume appears as a standard tape volume. MVS and TMS consider a VTS virtual tape volume to be a real volume. Media Conversion also regards a VTS virtual volume as a real tape volume. As a result, CARTS is device independent. CARTS supports all VTS systems offered by all vendors. Currently, all VTS systems are limited in their ability to migrate existing tape datasets to or from the VTS. The figure below shows a typical situation faced by many data centers who have incorporated a VTS in their tape library. The first concern is importing existing tape volumes into the VTS. The second concern is exporting a VTS volume to another tape device, usually an offsite high-capacity unit like a Storage Tek Redwood or an IBM 3595 MagStar used for archival purposes. Media Conversion solves both concerns. Datasets from legacy reels and older 3480/3490 cartridges can be imported into a VTS and stored as virtual volumes. Media Conversion also exports virtual volumes to stacked tapes outside of the VTS system. This section describes how to prepare Media Conversion to migrate tape volumes into and out of a VTS. Media Conversion As Is mode is the preferred method to migrate existing datasets on real volumes into a VTS. The dataset sequence and catalog status are preserved. The TMC is updated to reflect the original dataset characteristics. 110 CARTS 3.6.0

121 Using Media Conversion with Virtual Tape Systems Media Conversion Stacking mode is the preferred method to migrate datasets stored on virtual volumes to real tape volumes outside of the VTS. There are no size considerations. Single and multi-datasets residing on single and multi-virtual volumes can be migrated to real volumes by Media Conversion. As in the case of As Is mode, the TMC is updated. Control File Recommendations for Virtual Tape Systems This section describes Media Conversion Control file recommendations to move tape volumes in and out of a VTS. Virtual Footage The best volume candidates to move into a VTS are single dataset volumes. For optimum performance, you should avoid migrating large multi-volume datasets or multi-dataset volumes into a VTS. You want to avoid the possibility that moving large volumes or datasets could cause a volume overflow within the VTS. You can control which volumes are candidates to be moved to a VTS by using the Virtual Footage parameter shown on the VOLSER GROUP screen. Volumes that exceed the specified virtual footage are excluded from the move operation. VTS Unit Esoteric/Output Storage Class CARTS is device independent. All that is required to control the movement of tape volumes into or from a VTS is to specify the correct unit esoteric or output storage class of the VTS tape drive. CARTS TMS User Guide 111

122 Chapter 8 Media Conversion Example Media Conversion Control File Settings for a VTS This section provides examples of the Selection Criteria and VOLSER Group screens. The screens show the recommended values entered into a CARTS Control file that can be used to run Media Conversion jobs on a VTS. Set the maximum dataset size to 800 MB from the Maximum file size field to restrict the size of input datasets migrated into the VTS. CARTS Selection Criteria COMMAND ===> User Id-PROD Control file: PRD.CTS360.MCCNTL TMS MC VTS Control File DATE Minimum days since creation ===> 000 (Exclude if less) SELECTION Maximum days before expiration ===> 000 (Exclude if more) Minimum days since last access ===> 000 (Exclude if less) Maximum days since last moved ===> 999 (Exclude if more) Creation date range ===> thru Maximum days elapsed between creation and last access ===> 999 (Exclude if less) OTHER Cartridges or reels ===> C (C or R) CRITERIA Cataloged or uncataloged data sets ===> C (C or U) Data sets due to be vaulted ===> IGN (INC/EXC/IGN) Stack cycle controlled tapes ===> YES (Yes/No) Stack files with blksize = 0 ===> YES (Yes/No) Stack files with blksize > ===> YES (Yes/No) Stack files with block count = 0 ===> YES (Yes/No) Minimum file size (megabytes) ===> Maximum file size (megabytes) ===> Set the virtual footage to Enter the esoteric unit name of your VTS on the Non-robotic unit field. CARTS VOLSER Group COMMAND ===> User Id-PROD Description ===> VOLSER GROUP 1 Group is active ===> YES Max DSNs per output tape ===> Virtual Footage ===> (output tape capacity) Max percentage of tape used ===> 99 (exclude if higher) Robotic Unit ===> ATL Non-robotic Unit ===> VTS1 Output storage class ===> (to be assigned to output tapes) VOLSER Ranges (used for input selection only) From AAAAAA to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to From to 112 CARTS 3.6.0

123 Chapter 9 CARTS Maintenance This chapter describes CARTS maintenance procedures. Please note: CARTS-TS requires regular file maintenance. Mount Eliminator requires maintenance when you upgrade to a new version of JES. Maintenance schedules should have been prepared during CARTS-TS installation. See your CARTS-TS installation worksheet for the frequency of scheduled maintenance. CARTS TMS User Guide 113

124 Chapter 9 CARTS Maintenance Dependency File Maintenance Regularly scheduled maintenance must be conducted to ensure accurate dataset records are kept in the Dependency File. This section describes Dependency file maintenance procedures listed below: Editing Dependency file records Update Dependency file with new SMF data Backup the current file Control growth and reorganize the file Editing Dependency File Records This section describes how to add, delete, and edit the records of Dependency file. 1. Select option 2, Utilities, from the CARTS Main menu. 2. Select option 2, Depfile, from the Utilities menu. The Dependency File Update screen appears, as shown in the following figure. 10: C A R T S -- Dependency File Update /04/27 COMMAND ===> Enter Dependency File data set name below: Data Set Name ===> 'PROD.CTS360.DEPEND' F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE 3. Enter the dataset name of your Dependency file. The Dependency Update menu appears with two fields to specify a range of Dependency file records based upon the names of existing dataset entries in the Dependency file. Enter key ranges to be processed below. Partial (generic) values are acceptable. From key ===> To key ===> 114 CARTS 3.6.0

125 Dependency File Maintenance The dependency file uses an 88 byte key consisting of two 44 byte data set names. Enter the low key of the range you wish to process in the From Key field and the high key in the To key field. Only records that fall within the range you specify are loaded into memory and made available for processing. The keys you specify are implicitly generic. For example, if you specify a From Key value of ABC.D, then any data set name beginning with ABC.D will be selected. The default values of the From Key and To key fields are the first and last records in the Dependency file, respectively. Thus, leaving both fields blank causes the entire Dependency file to be loaded into memory. This dialog loads the dependency records into main memory for processing. If the dependency file is large, this can cause slow performance. You can counteract this by limiting the number of records loaded into memory by restricting the size of your key range. 4. Browse the list of Dependency file records. After specifying keys values in the Dependency File Update menu, a scrollable list of the selected records appears on the screen. You can modify the records in the list by entering special codes in the Action field at the left of the screen or by entering commands from the Command field Dependency File Update Row 1 of 578 Command ===> _ Scroll ===> CURS Action _ 1st DSNAME: PROD.CARTS.MASTER.LIST 2nd DSNAME: PROD.CLIST JOB PROD STEP TSOPROD PROG IKJEFT01 MOD NO _ 1st DSNAME: PROD.CARTS.MASTER.LIST 2nd DSNAME: PROD.CTS360.CLISTL JOB PROD STEP TSOPROD PROG IKJEFT01 MOD NO _ 1st DSNAME: PROD.CARTS.MASTER.LIST 2nd DSNAME: PROD.CTS360R.LOADLIB JOB PROD STEP TSOPROD PROG IKJEFT01 MOD NO _ 1st DSNAME: PROD.CARTS.MASTER.LIST 2nd DSNAME: PROD.CTS360.PANELS JOB PROD STEP TSOPROD PROG IKJEFT01 MOD NO Deleting Records Enter the letter D in the action field of the record you wish to delete and press ENTER. Adding Records Enter the letter I in the action field of any line on the display. (It doesn't matter which line you choose.) Then press ENTER. A popup window appears to enter data about the record being added. If there are no detail lines displayed, you can also get the popup by entering ADD or INSERT from the Command field. CARTS TMS User Guide 115

126 Chapter 9 CARTS Maintenance In the popup window are entry areas for the data fields that occur in a dependency record. Fill in the fields with appropriate values and press ENTER Dependency File Update Row 1 to 2 of 2 Command ===> ADD Scroll ===> CSR E NEW DEPENDENCY RECORD Actio COMMAND ===> _ 1st DSNAME ===> 2nd DSNAME ===> JOB ===> STEP ===> _ PROG ===> MOD ===> NO (YES/NO) F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE F7=UP F8=DOWN F9=SWAP F10=LEFT st DSNAME: DNS1.CARTS.MASTER.LIST 2nd DSNAME: PROD.REXX JOB DNS1 STEP TSODNS1 PROG IKJEFT01 MOD NO _ 1st DSNAME: PROD.CARTS.MASTER.LIST 2nd DSNAME: SYS1.BRODCAST JOB DNS1 STEP TSODNS1 PROG IKJEFT01 MOD NO _ 1st DSNAME: PROD.CLIST 2nd DSNAME: DNS1.CTS357R.CLISTL JOB DNS1 STEP TSODNS1 PROG IKJEFT01 MOD NO If you entered any value(s) incorrectly, a message is displayed that describes the error. Otherwise, a message indicates that a new record has been added to the Dependency file. You can then modify one or more values and press ENTER again to add another record. Continue this process until you have added all of the records you need to add. Press END (PF3) to return to the Dependency Update screen. Editing Records Enter the letter E in the Action field of the record you wish to update and press ENTER. A pop-up window appears containing the current data values for the selected record. The pop-up is similar to the example shown above for adding a Dependency file record. Overtype the fields you wish to modify and press ENTER. If you have entered any value(s) incorrectly, a message appears that describes the error. Otherwise, a message indicates the record has been updated. Press END (PF3) to return to the Dependency Update screen. 116 CARTS 3.6.0

127 Dependency File Maintenance Updating the Dependency File with Current SMF Data During CARTS installation, the Dependency file was initialized with SMF 14, 15, and 30 records that monitor dataset activity. The Dependency File must be updated on a regularly scheduled basis with current SMF data to maintain an accurate assessment of your site s datasets. Updating the CARTS-TS Dependency File is a two step operation. Step 1: REBDDEP1 REBDDEP1, should be run on a daily or weekly schedule. REBDDEP1 extracts the required records (types 14, 15 and 30) from the SMF dump dataset and writes them to an interim output generation dataset. REBDDEP1 is designed to extract data from the dumped SMF data file. Schedule REBDDEP1 to run after your site s job to dump the contents of the SMF dataset to tape. Review the CARTSU90 report produced by REBDDEP1 to get a summary of the records read from the SMF dataset and written to an output generation dataset. Step 2: REBDDEP2 REBDDEP2 should be run less frequently than REBDDEP1. REBDDEP2 creates a new Dependency File by combining data from the various output generation datasets created by REBDDEP1 and the current Dependency File. Generation datasets created by REBDDEP1 are deleted after the Dependency file has been updated. You should run REBDDEP2 on a schedule determined by how often your dataset processing changes. REBBDEP2 should process REBDDEP1 generation datasets on disk. You should run REBDDEP2 often enough to avoid the interim output generation datasets from being off-loaded to tape or taking up too much DASD space. Review the CARTSU91 and the CARTSU92 reports generated by REBDDEP2. The CARTSU91 report lists datasets that cannot be stacked together because they are used by the same job or job step. The list also includes MOD datasets that must stacked last on tape. The CARTSU92 report summarizes the number of records used to create the updated Dependency file. CARTS TMS User Guide 117

128 Chapter 9 CARTS Maintenance Backing Up the Dependency File The Dependency File should be backed up regularly. Run the BKUPDEPN procedure located in the CARTS JCLLIB dataset to back up the Dependency file. Controlling the Size of the Dependency File The size of Dependency File increases each time it is updated with new SMF data. Periodically, obsolete records should be removed to prevent the file from becoming too large. Run the UPDTDEPN procedure located in the CARTS JCLLIB to control the size of the Dependency file. UPDTDEPN deletes obsolete records and reorganizes the file. UPDTDEPN generates the CARTSC16 Dependency File Housekeeping Report. History File Maintenance CARTS-TS writes a record to the History file each time a dataset is stacked or restacked. Accordingly, the size of the History file increases each time a stacking job is run. Run the UPDTHIST procedure located in the CARTS JCLLIB to remove obsolete records and control the growth of the History file. UPDTHIST eliminates dataset and tape records from the History file when: the dataset is no longer listed in the MVS catalog the dataset is no longer located on the volume listed in the TMS TMC History File maintenance also controls the expiration of duplicate volumes created by the CARTS-TS Dual Copy feature. When the original tape is scratched, UPDTHIST scratches the duplicate tape. You should run UPDTHIST frequently if your site creates duplicate volumes with Dual Copy. Block File Updates The Block File is used by Mount Eliminator to determine how much disk space needs to be allocated for each redirected dataset. The initial Block file is built by running CARTSSMF, which formats and initializes the dataset with SMF records. After that, Mount Eliminator dynamically updates existing dataset entries with their current average block size. But, Mount Eliminator does not add new datasets to the Block file. The calculated block size shown in the Block file is used as the primary disk space allocation for datasets redirected by Mount Eliminator. A secondary allocation is 10% of the primary allocation. If the block size is not coded in the JCL, the default is New datasets need to be added to an existing Block file so they will be eligible for redirection by Mount Eliminator This section explains how to add new datasets to an existing Block file. There are two methods to update a Block file with new dataset entries. You can submit the UPDTBLKF job to rebuild the Block file and include new datasets. Or, you can manually add new dataset entries by editing the Block file from an online session. Both methods are discussed in the following sections. 118 CARTS 3.6.0

129 Block File Updates Running UPDTBLKF UPDTBLKF is a procedure located in the CARTS JCLLIB dataset. UPDTBLKF processes SMF data and rebuilds an existing Block file used by Mount Eliminator. The following example shows UPDTBLKF parameters that must be completed before submitting the job. //PRODT010 JOB (CARTS),'CARTS 360 TMS 54',CLASS=A,NOTIFY=PROD, // MSGCLASS=X,TYPRUN=HOLD //PROCLIB JCLLIB ORDER=(PROD.CTS360T.PROCLIB) //* SYSOUT CLASS //UPDTBLKF PROC OUT='*', //* UNIT OR STORAGE CLASS FOR DASD WORK FILES // TEMPD='UNIT=SYSDA', //* UNIT OR STORAGE CLASS FOR SORT WORK FILES // SORTW='UNIT=SYSDA', //* CARTS-TS JCLLIB LIBRARY // JCLLIB='PROD.CTS360.JCLLIB', //* CARTS-TS LOAD LIBRARY // LOADLIB='PROD.CTS360.LOADLIB', //* CARTS-TS APF LIBRARY // APFLIB='PROD.CTS360.APFLIB', //* CARTS-ME BLOCK FILE TO BE LOADED // BLKFILE='PROD.CTS360.BLKFILE', //* YOUR TSO USERID // UID='PROD', //* SMF FILE DATASET NAME TO BE PROCESSED // SMFDATA= UPDTBLKF processes SMF type 4, 5, 14, 15, and 26 records to calculate the average block size of datasets that are candidates for redirection to disk. If possible, you should rebuild the Block file with the maximum amount of data held by your site s SMF dataset before it is normally stored to tape. Datasets are added based upon selection criteria used by CARTSSMF to create the original Block file. Refer to Step 4: Build the Block File on page 43 of the CARTS For CA-1/TMS Installation Guide for instructions to select those datasets you want Mount Eliminator to consider for redirection to disk. UPDTBLKF generates the following reports: CARTSRPT16 CARTSRPT17 CARTSRPT18 Refer to the CARTS Reports Manual for a description of each report and report field. CARTS TMS User Guide 119

130 Chapter 9 CARTS Maintenance Manually Updating the Block File Select Option 9, BLOCKUPD, from the CARTS-TS Main Menu panel to edit or prepare the Block File. Mount Eliminator must be quiescent or inactive to make any changes to the Block file. You can make the following editing changes to the Block File: CHANGE Change an existing Block File record. Overtype the record. DELETE Delete a Block File record. Type D in the field adjacent to record. ADD Add a new record. Type ADD in the command field. A popup window appears with fields to add records. The following procedure shows how to add an entry to the Block file. You should know the actual block size of the dataset you want to add to the Block file before starting this procedure. 1. Select option 9, B LOCKUPD, from the CARTS Main Menu. 2. Enter the name of the Block file dataset on the screen that appears after selecting option 9 from the Main Menu. After Block file records are loaded, the Edit Block File screen appears with a listing of dataset entries in the Block file. CARTS Edit Block File Row 1 to 18 of 5,674 Average No of Action BlkCount Entries DSName _ XYZ.ACCTNG.PAYROLL.WE0107 _ XYZ.ACCNTG.PAYROLL.WE0114 _ XYZ.FINANCE.PLANNG1 _ XYZ.ACCTNG.PAYROLL.WE1226 _ XYZ.ACCNTG.PAYROLL.WE1219 _ XYZ.FINANCE.PLANNG2 _ COMMAND ===> Scroll ===> PAGE 120 CARTS 3.6.0

131 Block File Updates 3. Enter ADD from the screen Command line. The following figure shows a pop-up window that appears with fields to add entries to the Block file. CARTS Edit Block File Row 1 to 18 of 5,675 Average No of Action BlkCount Entries DSName _ XYZ.ACCTNG.PAYROLL.WE0107 _ XYZ.ACCNTG.PAYROLL.WE0114 _ XYZ.FINANCE.PLANNG1 _ Add New Entry _ : : _ : Enter new values below: : _ : : _ : DSN ===> : _ : : _ : Avg blk : _ : count ===> 0 : _ : : _ : Nbr of : _ : entries ===> 0 : _ : : _ : : _ _ PROD.CTS360L.TEST.FI00A1 COMMAND ===> ADD Scroll ===> PAGE 4. Enter a dataset name on the DSN field, as shown below. PROD.CTS360.TEST 5. Enter the actual block size on the Avg blk count field for the dataset you selected to add to the Block file. 6. Enter a number on the Nbr of entries field at the bottom of the pop-up window and press ENTER. The pop-up window disappears and the Edit Block File screen reappears with your entry added to the Block file. 7. Save your changes to the Block file. 8. Run member SORTBLK of the CARTS JCLLIB. No changes are necessary. CARTS TMS User Guide 121

132 Chapter 9 CARTS Maintenance Control File Maintenance CARTS component Control files do not require regularly scheduled maintenance. However, Control file parameters do need to be updated each and every time new tape volumes are selected for a stacking or restacking job. Both Mount Eliminator and Disk Stacker use disk storage as part of their overall processing. Their respective Control files need to be updated when new disk volumes will be used with both components. JES Maintenance Member ASMLJES6 modifies the Mount Eliminator JES Exit 6 for the version of JES you are using. If you upgrade JES, you must rerun ASMLJES6 to reassemble the JES Exit 6. No modification is required. Simply rerun the ASMLJES6 job. Chapter 6 of the CARTS For CA-1/TMS Installation Guide describes how to use ASMLJES6 to customize the driver module for the Mount Eliminator JES Exit 6 for your current JES release. 122 CARTS 3.6.0

133 Index Symbols * wildcard 14 Numerics 3490 or 3490E drives and stacking 43 A abend access, last, including/excluding datasets in stacking by 29 accounting codes and trailing wildcards 14 ADD ISPF option 25 adding a Control file to ISPF 25 age of stacked datasets 29 AGE parameter 105 ALL keyword 40 allocation size 95, 120 analysis 2 At this time interval field 88 audience vii B batch window 5 BKUPDEPN job 118 Block file averages 95, 120 updating 95, viewing writing contents of the Block Table 89 Block table Mount Eliminator requirements 7, 83 option 95 required number of entries 7, 83 BLOCKUPD option 120 Bypass dependency checking field 35 BYPASS parameter, Disk Stacker (now AGE) 105 C CA-1/TMS grouping stacked datasets by outcodes 66 Cartridge Unit Parameter field 86 Cartridges or reels field 30, 63 CARTS Main Menu CARTSCHK procedure 89 CARTSDS procedure 105, 106 CARTS-DS. See Disk Stacker CARTSDSK procedure 90 CARTSEX procedure 56 CARTSFDN 101 CARTSFDN procedure 101 CARTSFIM procedure 101 CARTSFST procedure 82, 89, 91 CARTSHSS CLIST 80 CARTSHSY CLIST 80 CARTSMA procedure 107, 109 CARTSMC procedure 107, 109 CARTS-MC See Media Conversion CARTS-ME See Mount Eliminator CARTSMOVE procedure 90 CARTSRPT04 report 52 CARTSRPT14 report 52 reports CARTSRPT99 4 CARTSRPT15 report 90 CARTSRPT15, Mount Eliminator Dataset Disposition report 94 CARTSRPT99 report 4, 52 CARTS-TS concepts 2 Control file 4 Control file for Mount Eliminator 7, 83 Control file used by Mount Eliminator controlling execution 33 Dependency file 5 Dependency file stacking requirements 2 execution options 33 History file 4 integrity checks 59 JOB statements 49 maintenance 113 operation 5, 53 recommended JCL job parameters 49 reports 3 submitting batch jobs 53 unstacking

134 worksheet 11 CARTSTS CLIST 11 CARTSU90 report 117 CARTSU91 report 117 CARTSU92 report 117 Cataloged or uncataloged datasets field 30 Check Points are taken every field 93 Checkpoints taken so far field 93 CLISTs CARTSHSS 74, 80 CARTSHSY 74, 80 CARTSTS 11 commands DIAGNOSE Find 94, 96 compaction migrating to compaction-enabled drives 107 migrating uncompacted stacked volumes 64 concurrent jobs 34 contacting Customer Service ix CONTROL option 12 Control file CARTS-TS 4, 53 changing Mount Eliminator 89 copying 21 copying the contents 23 creating a new Control file 20 customization 12, 82 Disk Stacker 104 list 18 Media Conversion 108 meeting selection criteria for stacking 28 Model 23 model 23 Mount Eliminator 7, optional files 51 parameters required for stacking 51 rules 28 saving changes 15 selecting 19 specifying master list 27 target 23 temporary 53 temporary dataset 53 testing 52, 53, 54 updating 17 Control Files screen adding a file to the list 25 changing the list dataset 27 copying Control file contents 23 creating a Control file 20 deleting a Control file 22 description 18 dropping a file from the list 26 options MASTER 27 selecting a control file 19 copying another Control file 21 create date, including/excluding datasets in stacking by 29 CREATE ISPF option 20 creation date and last access difference, in stacking 30 Creation date range field 30, 62 CRITERIA ISPF option 29 current volser, stacked dataset 73 Customer Service ix customization Mount Eliminator Control file cycle control 31 D DASD Resident time before Stacking field 87 DASD unit field 86 DASD Unit Parameter field 86 Data Set Names screen description 36 Dataset Disposition report 94 Dataset Names screen fields Dataset Selection screen 76 datasets age of datasets in stacking 29 create date 29 exclude from stacking if they exceed percentage of tape capacity 44 excluded from stacking 4 excluding from redirection by Mount Eliminator 88 excluding from stacking 4 expiration after stacking 5 externally managed 4 grouping 66 grouping on stacked volumes 66 HSM 4 implementing security 71 including/excluding for stacking

135 including/excluding outcoded in stacking 46 ineligible for stacking 4 limiting number stacked on a tape volume 43 limiting stacking by creation date 62 locating uncataloged 4 migrating to tape from disk 8 minimum time on disk 87 MOD 2, 5 Mount Eliminator qualifications 7, 83 Mount Eliminator redirected 93 Mount Eliminator redirection 86 multi-volume 4 multi-volume stacking with Media Conversion 9 name nodes 14 needed by same job step 2 not redirecting large datasets 86 off-loading with Disk Stacker 8 product, names vii redirecting permanently to disk 87 required by same job step 5 requirements to be redirected to disk by Mount Eliminator 7, 83 residency time on disk 105 selecting by dataset names 36 selecting for stacking by size 32 size records for Mount Eliminator 95, 120 specifying Control file master list 27 stacking cataloged/uncataloged 30 stacking multi-volume 55 stacking to vault 2 stacking uncataloged with Media Conversion or Restacker 30 stacking vaulted 68 stacking with Disk Stacker 8 temporary 53 uncataloged for stacking 30 unloaded from disk by Mount Eliminator 6 unloading a single dataset from a stacked volume 56 unstacking a single dataset from a stacked volume 56 using wildcards to select 14 vaulted 2 vaulted, stacking 46 date of stacking 78 Days before expiration field 29 days since last access field 29 DELETE ISPF Option 22 deleting a Control file 22 Dependency File description 5 Dependency file bypassing 35 editing records , 117 update reports 117 use with CARTS-TS 2 DIAGNOSE command Disk Stacker Control file 104 description 8, 103 running 106 drives for redirection 86 used in stacking 35 used in stacking jobs 2 DROP ISPF option 26 DSNAMES ISPF option 36 DSNs awaiting creation field 93 DSNs awaiting stacking field 93 Dual Copy expiring duplicate volumes 34 number of required tape drives 2 record 73 removing expired volumes with UPDTHIST 118 specifying 34 tape drives 35 Dual Copy field 34 E Esoteric 45 esoterics Mount Eliminator 86 selecting DASD for Mount Eliminator 86 selecting robots 44 selecting tape drives 63 establishing rules for stacking 28 EVERY parameter 89, 90, 93 Exclude datasets to be vaulted field fields Exclude datasets to be vaulted 69 exclude datasets to be vaulted field 46 excluding datasets from stacking 28 EXECUTION ISPF option 33 exits JES Exit expiration 125

136 Dual Copy volumes 34 including/excluding datasets in stacking 29 off-loaded datasets 8 F fields At this time interval 88 Bypass dependency checking 35 Cartridge Unit Parameter 86 Cartridges or reels 30, 63 Cataloged or uncataloged datasets 30 Check Points are taken every 93 Checkpoints taken so far 93 Creation date range 62 DASD unit 86 DASD Unit Parameter 86 DSNs awaiting creation 93 DSNs awaiting stacking 93 Dual Copy 34 Group is active 43 Immediate scratch 40 INPUT must be in a robot 40 It was started 92 Job Numbering 61 Job numbering 34 Max data sets per output tape 43 Max datasets per output tape 55 Maximum file size 32 Maximum percentage of tape used 44 Maximum size data set to redirect field 86 ME started processing on 92 MEindicator 93 Minimum days since creation 62 Minimum file size 32 Minimum Scratch Pool 67 Minimum scratch pool 62 Minimum scratch pool to maintain field 34 Minimum size data set to stack 87 Minimun time a data set must remain of DASD 87 Non-robotic device 45 Non-robotic Unit 63 Number of concurrent jobs 35, 61 Number of digits 34, 61 Number of scratch tapes 62, 67 Number of scratch tapes needed 33 OUTPUT to a robot 40 Pending stack timeout interval 35 Reject files pending stacking 35 Reports Only 52 Reports only 54 Robotic device 44 Robotic IDs 40 Robotic Unit 63 Robotic vendor 39 Starting column 61 Starting column within jobname 34 Virtual footage VOLSER Ranges 45 When DASD utilization reaches 88, 90 Whenever this many data sets have been redirected 87, 90 file maintenance Block file CARTS-TS 113 Dependency file 114 History file 118 file sequence number 73, 77 Find command 94, 96 G generics Grau selecting robots for stacking 39 Group is active field 43 H HASPXJDI member 86 help 15 History Detail screen 77 History file contents 73 description 4 expiring Dual Copy volumes with the History file update procedure 34 maintenance 118 viewing alternative with CARTSHSS and CARTSHSY CLISTs 80 History Inquiry Main Menu option 12 History Inquiry screen I IBM MagStar tape drive 3 identifying datasets for redirection

137 IEFU83 exit 90 use with CARTSMOVE procedure 90 Immediate scratch field 40 including datasets in stacking 28 INPUT must be in a robot field 40 input volser of stacked datasets 73 installation worksheet vii, 11 ISPF accessing CARTS screens 11 CARTS PF keys 15 exiting from screens 16 submitting CARTS-TS jobs 53 It was started field 92 J JES upgrade with ASMLJES6 member 122 JES Exit job numbering 49 Job and Step Names screen 47 JOB Cards screen 48 job names and trailing wildcards 14 Job Numbering field 61 Job numbering field 34 JOB statements for CARTS-TS jobs 48 JOB/STEP ISPF option 47 JOBCARDS Main Menu option 13 jobs limiting the number of stacking 62 numbering jobs and job steps, including/excluding in stacking by 47 K KEEPFOR parameter 105 L last access and create date difference, in stacking 30 last access, including/excluding datasets in stacking by 29 library names vii M Main Menu Main menu Job Cards panel 48 maintenance 113 Mount Eliminator 122 Mount Eliminator for JES upgrade 122 MASTER ISPF option 27 MASTER option 27 Max datasets per output tape field 43, 55 Maximum days before expiration field 29 Maximum days elapsed between creation and last access field 30 Maximum file size field stacking selecting datasets by size 32 Maximum percentage of tape used field 44 Maximum size data set to redirect field 86 ME started processing on field 92 Media Conversion Control file 108 converting to new tape media 9 description 9, 107 running 109 stacking uncataloged datasets 30 support for VTS 9 use with virtual tape systems MEindicator field 93 Memorex selecting robots for stacking 39 Memorex (SUTMYN) assign robot IDs 40 designating robot with ATL parameter value 39 memory, saving in 15 Minimum days since creation field 29, 62 Minimum days since last access field 29 Minimum file size field 32 Minimum Scratch Pool field 67 Minimum scratch pool field 62 Minimum scratch pool to maintain field 34 Minimum size data set to stack field 87 Minimum time a data set must remain on DASD field 87 minimum time on disk 87 MOD datasets 2, 5 model Control file 21 MODEL ISPF option 23 modification, last, including/excluding datasets in stacking by

138 Mount Eliminator Block table 7, 83 CARTSDSK procedure 90 CARTSMOVE procedure 90 CARTS-TS Control file 7, 83 CARTS-TS control file customizing 82 changing Control files 89 check point procedure 89 Control file 7, 83 creating 85 customizing description 82 example figure of ISPF screen 84 Control File screens 12 DASD volumes used 86 dataset Block table requirements 7, 83 datasets excluding from redirection 88 leaving on disk 87 maximum size to redirect 86 minimum time on DASD 87 minimum time on disk 88 description 81 identifying Control files 89 introduction 6 leaving small datasets on disk 87 maintenance 122 monitoring Block file DIAGNOSE command WIP table percent usage of DASD 88 quiescence 101 quiescent mode 101 requirements to redirect datasets 83 requirments to redirect a dataset to disk 7, 83 shutting down with CARTSFDN 101 with CARTSFIM 101 specifying multiple DASD esoterics with HASPXJDI 86 stacking conditions 6 stacking interval 88 stages 93 starting 91 status trace activity 100 UNIT esoterics 7, 83 usage statistics 92 MVS catalog use with Disk Stacker 8 N Non-robotic device field 45 Non-robotic Unit field 63 Number of concurrent jobs field 35, 61 Number of digits field 34, 61 Number of scratch tapes field 62, 67 Number of scratch tapes needed field 33 O offloading datasets Disk Stacker 103 online screens. See ISPF screens original volser, stacked datasets 73 out codes 46 OUTCODES ISPF option 46 output environment, drives 63 OUTPUT to a robot field 40 P parameters AGE 105 KEEPFOR 105 Pending stack timeout interval field 35 PF keys 15 Phone and fax numbers, UNICOM Systems, Inc. ix PROCCART procedure (now STACKER) 53 PROCDASD job (now CARTSDS) 105, 106 PROCREST procedure (now RESTACK) 53 PROCRTS procedure (now CARTSMA or CARTSMC) 109 pull list 65 Q qualifiers dataset name 14 quiescence description 101 quiescent mode

139 R read, last, including/excluding datasets in stacking by 29 REBDDEP1job 117 REBDDEP2 job 117 redirection 93 reel to cartridge processing 107 Reject files pending stacking field 35 related documentation viii reports CARTSRPT04 52 CARTSRPT14 4, 52 CARTSRPT15 90 CARTSRPT99 52 CARTSU CARTSU CARTSU DIAGNOSE discontinuing 57, 58 dummying out 57 reports only mode 53 RESETCDS 59 RESETCYC 60 restrictions during CARTS evaluation period 57 resuming 58 Stacker 59 UPDTBLKF 119 Reports Only field 52 Reports only field 54 RESETCDS utility 59 RESTACK procedure 53 Restacker operation 55 stacking uncataloged datasets 30 submitting from ISPF 53 RETAIN parameter, Disk Stacker (now KEEPFOR) 105 Robotic device field 44 Robotic IDs field 40 Robotic Unit field 63 Robotic Units and Options screen description 39 Robotic vendor field 39 robots GRAU supply vendor name 39 identifying 40 immediate scratch of input tapes selected for stacking 40 Memorex (SUTMYN) identify to CARTS-TS 40 supply vendor name 39 scratch input volumes 40 scratching stacked tapes 40 specifying esoteric device name 44 specifying for stacking 39 stacking from 2, 44 StorageTek identify to CARTS-TS 40 supply vendor name 39 ROBOTS option 39 round to square processing 107 RULES Main Menu option 13, 28 Rules Categories screen accessing 28 overview 28 rules for stacking 28 Rules menu Accounting Codes panel 48 DSNAMES option 36 Execution Options panel 33 Job and Step Names screen 47 Out codes panel 46 Robotic Units and Options screen 39 Selection Criteria screen 29 VOLSER Ranges screen running CARTS-TS 5 S saving changes 15 scratch tapes maintaining a minimum number in the pool 34 number returned in stacking 33 producing a required minimum 68 recovering, sample control file 67 within a robot 40 security dataset level 71 grouping datasets 36, 66 volume level 71 SELECT ISPF option 19 Selection Criteria screen 29 SMF build the Block file 119 data used by Block file 95 data used by Dependency file 5 data used by Mount Eliminator 93 SMS 129

140 selecting datasets for stacking by management class 48 SMSPARMS parameter stack cycle controlled tapes field 31 STACKER procedure 53 stacking analysis 2 assigned security to stacked volumes 71 assigning job numbers 34 by TMS out codes 46 bypassing Dependency file 35 concurrent jobs 49 data transfer 2 datasets restricted from redirection by Mount Eliminator 4 date 78 description 2 disk datasets with Disk Stacker 8 Disk Stacker 8 electronic vaulting 70 establishing rules 28 excluding datasets 4 from disk by Mount Eliminator 6 grouping datasets 66 impact on performance of online systems 5 ineligible datasets 4 jobs concurrent executions 61 Disk Stacker 106 limiting 33 Media Conversion 109 obtaining a pull list 65 setting number of concurrent 35 specifying concurrent execution 34 when stacked tapes are scratched 40 limiting number of datasets placed on a single volume 43 limiting number of jobs 34 limiting the number of jobs 62 maintaining a minimum number of volumes in the scratch pool 34 Mount Eliminator 93 Mount Eliminator interval 88 Mount Eliminator trigger conditions 6 multi-dataset volumes 55 number of concurrent jobs 35 off-loading redirected datasets 90 off-site 70 on 3490 or 3490E drives 43 on compaction-enabled drives 43 reducing the number of off-site volumes 69 reject datasets from stacking that have been selected by a previous job 35 selecting by SMS management class 48 selecting by VRS management value 48 selecting output tape media 30 selecting volumes from VOLSER Ranges screen 45 setting the number of concurrent jobs 61 single job sample Control file 70 suppressing jobs 54 testing Control files 52 to a vault 70 to scratch tapes 2 to volumes mounted on a robot 40 unstacking a tape 55 volumes mounted on robots 40 stacking jobs introduction 2 JOB statements 48 Starting column field 61 Starting column within jobname field 34 statistics Mount Eliminator 92, 93 step names and trailing wildcards 14 steps, job, including/excluding in stacking by 47 Storage Tek selecting robots for stacking 39 Storage Tek Redwood tape drive 3 StorageTek assign robot IDs 40 designating robot with ACS parameter value 39 SUBMIT Main Menu option 13 T tape drives compaction and stacking 43, 64 input for stacking 63 output for stacking 63 selecting for Mount Eliminator 86 used in stacking 35, 44,

141 media 107 selecting cartridge or reel for stacking 30, 63 mounts reducing with Mount Eliminator 81 stacking requirements 2 restacking 55 robots selecting for stacking 39 unstacking 55 volumes creating a duplicate with Dual Copy 34 limiting number of stacked datasets 43 limiting stacking jobs by volsers 62 producing a required minimum 68 pulling before stacking 65 reducing mount requests 81 reducing number sent to a vault 68 scratching immediately when mounted on a robot 40 selecting number of scratch 33, 34 selecting range to stack 45 specifying virtual footage stacking multi-dataset 55 virtual footage tapes including/excluding for stacking 28 UNICOM Systems, Inc., phone and fax ix time of stacking 78 time on disk 87, 88 time stamp of stacking/restacking 73 TMC dataset creation statistics with Mount Eliminator 6 trial status message 12 U uncataloged datasets locating 4 selecting for stacking 30 UNIT esoterics for Mount Eliminator 86 unstacking a single dataset 56 updating CARTS-TS Control files 17 UPDTBLKF reports 119 UPDTDEPN job 118 UPDTHIST job 118 V vaulted datasets including/excluding in stacking 46 vaulting electronic 70 reducing number of volumes 69 stacked datasets 70 virtual footage 43 44, 77 Virtual footage field virtual tape system use with Media Conversion 9, VOLSER Ranges field 45 VOLSER Ranges screen description 41 example figure 41 volsers stacked datasets 73, 77, 78 VRS selecting datasets for stacking by management value 48 VTS See virtual tape system W When DASD utilization reaches field 88, 90 Whenever this many data sets have been redirected field 87, 90 wildcards explicit 14 implicit 14 specifying datasets specifying job or step names 47, 48 trailing 14 Work in Progress table (WIP) CARTSCHK 89 CARTSMOV 90 displaying contents

142 132