TM
For CA-1/TMS
User Guide
Tape Stacker
Mount Eliminator
Media Conversion
Disk Stacker
Release 3.6.0
1990-2001 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 3.6.0 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 310 15535 San Fernando Mission Blvd.
CARTS TMS User Guide ▼ iii
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 ... 11
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 ... 17
Control File Menu... 18
1 SELECT—Selecting a Control File... 19
2 CREATE—Creating a New Control File ... 20
4 MODEL—Copying a Control File... 23
5 ADD—Adding a File to the Control File List ... 25
6 DROP—Removing a File from the Control File List ... 26
7 MASTER—Specifying a New Master Control File List... 27
Changing Stacking Conditions ... 28
1 CRITERIA—Selection Criteria... 29
Input Fields of the Selection Criteria Screen 29 2 EXECUTION—Execution Options ... 33
Input Fields of the Execution Screen 33 3 DSNAMES—Selecting by Dataset Names ... 36
Input Fields of the Data Set Names Screen 37 Examples of Stacking by Dataset Name 38 4 ROBOTS—Controlling Robotic Use ... 39
Input Fields of the Robotic Units and Options Screen 39 5 VOLSERS—VOLSER Ranges ... 41
Selecting an Input Volume Group ... 41
Adding or Modifying a VOLSER Group ... 42
Input Fields of the VOLSER Group Screen 43 6 OUTCODES—Selecting by TMS OutCodes... 46
7 JOB/STEP—Job and Step Names ... 47
8 ACCTCODE—Accounting Codes ... 48
Changing Job Statements ... 49
Chapter 4 Meeting Stacking Objectives ...51
Testing a Control File ... 52
Running CARTS-TS ... 53
Submitting Batch Stacking Jobs... 53
Submitting Stacking Jobs from CARTS-TS ISPF Screens ... 53
Using Restacker ... 55
Unstacking a Stacked Tape with Restacker ... 55
Unloading a Single File from a Stacked Volume ... 56
Selecting Reports ... 57
Stacker Reports... 57
Restacker Reports... 58
Discontinuing a Report ... 58
Resuming a Report... 58
CARTS Integrity Checks ... 59
RESETCDS Utility 59 RESTCYC Utility 59 Setting the Number of Concurrent Stacking Jobs ... 61
Limiting the Number of Stacking Jobs... 62
Controlling Input/Output Type ... 63
Migrating to Tape Drives That Support Compaction... 64
Obtaining a Pull List Before Stacking... 65
Grouping Datasets on Stacked Volumes... 66
Scratch Tape Shortages ... 67
Inconsistent Scratch Tape Availability... 68
Reducing the Number of Off-Site Volumes... 69
Electronic Vaulting ... 70
CARTS TMS User Guide ▼ v
Volume Level Security... 71
Dataset Level Security ... 71
Chapter 5 Using the History Inquiry ... 73
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... 81
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 ... 100
Stopping Mount Eliminator ... 101
Chapter 7 Disk Stacker ... 103
Editing the Disk Stacker Control File... 104
Using a New Control File... 104
Preparing the CARTSDS Procedure... 105
Running Disk Stacker... 106
Chapter 8 Media Conversion ... 107
Editing the Media Conversion Control File ... 108
Using a New Control File ... 108
Running Media Conversion ... 109
Using Media Conversion with Virtual Tape Systems ... 110
Control File Recommendations for Virtual Tape Systems ... 111
Virtual Footage 111 VTS Unit Esoteric/Output Storage Class 111 Example Media Conversion Control File Settings for a VTS ... 112
Chapter 9 CARTS Maintenance ...113
Dependency File Maintenance ... 114
Editing Dependency File Records ... 114
Updating the Dependency File with Current SMF Data... 117
Backing Up the Dependency File ... 118
Controlling the Size of the Dependency File ... 118
History File Maintenance ... 118
Block File Updates ... 118
Running UPDTBLKF ... 119
Manually Updating the Block File ... 120
Control File Maintenance... 122
JES Maintenance ... 122
Audience
CARTS TMS User Guide ▼ vii
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 proceduresThis 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 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 GuideDescribes procedures to install and implement all CARTS components at sites managing their tape library with TMS.
•
CARTS For CA-1/TMS User GuideDescribes how to use all CARTS components at sites managing their tape library with TMS.
•
CARTS For CA-1/TMS Release NotesExplains CARTS TMS installation requirements, product enhancements, and a procedure to migrate to Release 3.6.0.
•
CARTS Messages and CodesLists messages and codes generated by all CARTS components.
•
CARTS Reports ManualPresents 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 3.6.0 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 (http://www.adobe.com/acrobat).
Customer Service
CARTS TMS User Guide ▼ ix
Customer Service
UNICOM Systems Customer Service can be reached by the following methods: Voice 818-838-0606 Fax 818-838-0776
Website http://www.unicomsi.com/support Email [email protected]
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 jobCARTS Tape Stacker
CARTS TMS User Guide ▼ 1
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.
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.
Stacked volume
Empty volumes returned to the scratch pool Active unstacked volumes
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
Stacking Jobs
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.
CARTS-TS 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.
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 1 File 2
File 3 File 4
CARTS Tape Stacker
CARTS TMS User Guide ▼ 3
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
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.
CARTS Tape Stacker
CARTS TMS User Guide ▼ 5
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.
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.
Scratch Pool Unstacked Prepare a Control file Test a Control File Control File RESTACKER Volumes DASD Control File STACKER Tape Archiving Stacked Volumes
Return to Scratch Pool
Restacked Volume
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.
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.
Mounts Without ME Mounts With ME ➀ Tape dataset is written to
DASD.
➁ 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. CPU DASD ➀ ➁ ➂ CPU
Mount Eliminator
CARTS TMS User Guide ▼ 7
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)
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.
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.
Disk Volume
Tape Volume Sequential
Datasets SequentialDatasets
Disk Stacker
Media Conversion
CARTS TMS User Guide ▼ 9
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.
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.
Stacking
Accessing CARTS Screens
CARTS TMS User Guide ▼ 11
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
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.
1 - CONTROL
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 80.
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 92612 Tape Management System: TMS Robotic Vendor: ATL CARTS 3.6.0 (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
CARTS Main Menu
CARTS TMS User Guide ▼ 13
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.
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 55. 4 - 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 --- 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 92612 Tape Management System: TMS Robotic Vendor: ATL CARTS 3.6.0 (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
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.:
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.:
CARTS includes all datasets with a second level qualifier of PRODx. This includes the following datasets: ABC.PRODA.SAMPLE XTSG.PRODB.INVENTORY DKGFHJ.PROD1.94223 ---INCLude/EXCLude Opt Grp 1--- 2--- 3--- 4--- 5--- 6--- EXC ABC ---INCLude/EXCLude Opt Grp 1--- 2--- 3--- 4--- 5--- 6--- INC 001 PROD*.
Using Online Help
CARTS TMS User Guide ▼ 15
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
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.
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.
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.
CARTS TMS User Guide ▼ 17
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)
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.
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.
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 ===>
Control File Menu
CARTS TMS User Guide ▼ 19
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.
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 --- 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/1999 10:45 PRH2 PRH.CTS360.CNTL TMS ME TS Test Control File 01/25/1999 10:50 PRH2 PRH.CTS360.CNTLME TMS DS Test Control File 04/08/1999 11:53 PRH1 PRH.CTS360.DSCNTL TMS MA Test Control File 04/08/1999 10:47 PRH1 PRH.CTS360.MACNTL TMS MC Test Control File 03/31/1999 16:24 PRH1 PRH.CTS360.MCCNTL TMS RS Test Control File 01/25/1999 10:51 PRH2 PRH.CTS360.RSCNTL TMS ST Test Control File 04/16/1999 14:23 PRH1 PRH.CTS360.STCNTL ******************************* Bottom of data ********************************
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
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. CARTS--- CreateNewControlFile ---COMMAND===> UserId-PROD
TocreateanewControl file, fill in the required informationandpressENTER.
Datasetname===>XYZ1.CTS360.CNTL
Description ===>WeeklyControl file
SMS allocation:
Management Class===>
Storage Class ===> Non-SMS allocation:
VolumeSerial===> (volumeonwhichtoallocatethefile)*
GenericUnit ===> (Genericgroupnameorunitaddress)*
Control File Menu
CARTS TMS User Guide ▼ 21
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.
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.
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.
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. 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/1999 11:59 PROD
PROD.CTS360.TEST2.FILE
test 3 file 04/07/1999 12:34 PROD PROD.CTS360.TEST3.FILE
USR's Control file 04/06/1999 14:52 PROD PROD.CTS360.TMS.CNTL
******************************* Bottom of data ********************************
COMMAND ===> User Id-PROD
--- CONFIRMDELETE ---COMMAND===> UserId-PROD
Dataset Name:XYZ1.CTS360.CNTL
Description: WeeklyControl file
INSTRUCTIONS:
PressENTERkey to confirm delete request.
(The dataset will be deleted and dropped from the Control file list)
Control File Menu
CARTS TMS User Guide ▼ 23
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.
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--- Select ModelControlFile --- ROW1OF3 COMMAND===> UserId-PROD To select the Control file to be copied, place the cursor on
the desired file name or description and press ENTER.
Description/DataSetName
---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
The following screen appears to confirm the request.
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.
CARTS--- CONFIRMOPERATION ---COMMAND===> UserId-PROD
XYZ1.CTS360.CNTL
WeeklyControl file
isabouttobeoverwrittenwithdatafrom
PROD.CTS360.CNTL
Backup of Weekly Control file
PressENTERtoPROCEED.
Control File Menu
CARTS TMS User Guide ▼ 25
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 “ 2CREATE—Creating a New Control File” on page 20.
1. 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.
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--- AddControlFiletoList ---COMMAND===> UserId-PROD
ToaddanexistingControl filetothemasterlist:
EntertherequiredinformationbelowandpressENTER.
Datasetname===>
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.
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.
CARTS--- Drop ControlFileFrom List --- ROW1OF3 COMMAND===> UserId-PROD
To remove a Control file from the list, place the cursor on
the file name or description and press ENTER.
---LastUpdated
Description/DataSetName Date Time UserID
---Daily Stacking Control File 04/21/1999 14:11 PROD
CTS.CTS360.CNTL
Weekly controlfile 04/21/1999 14:15 PROD
XYZ1.CTS360.CNTL
Weekend Stacking Control File 04/21/1999 14:35 PROD
CTS.CTS360.WKEND
Vaulting Control File 04/21/1999 14:14 PROD CTS.CTS360.VAULT
Control File Menu
CARTS TMS User Guide ▼ 27
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.
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--- SpecifyMasterListName ---COMMAND===> UserId-PROD
Enterthenameofthedatasetcontainingthemasterlistof
controlfilesbelow. Enterthenamefullyqualifiedwithout
apostrophesorquotationmarks.
Masterlist
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. Asingle 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.
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.
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
Changing Stacking Conditions
CARTS TMS User Guide ▼ 29
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.
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 --- 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 ===> 0000000 thru 0099999 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 > 32760 ===> YES (Yes/No) Stack files with block count = 0 ===> YES (Yes/No) Minimum file size (megabytes) ===> 0000000 Maximum file size (megabytes) ===> 9999999
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, 0000000 thru 0099999, includes all datasets for stacking in the 20th century.
Examples
0000000 and 0199999 All datasets created in both the 20th and 21st centuries
0100000 and 0199999 All datasets created in the 21st century 0000000 and 0099999 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.
Changing Stacking Conditions
CARTS TMS User Guide ▼ 31
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 > 32760
Choice (YES or NO) to stack datasets with a block size greater than 32760.
YES Stack datasets with a block size greater than 32760.
This option is intended for datasets whose block size exceeds the MVS maximum of 32760. 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 32760.
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
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 0000000 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 9999999 megabytes.
Changing Stacking Conditions
CARTS TMS User Guide ▼ 33
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.
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 999999, 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 --- Execution Options ---COMMAND ===> User Id-PROD Control file: PROD.CTS360.CNTL Default Control File Number of scratch tapes needed ===> 9999999 Minimum scratch pool to maintain ===> 9999999 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)
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, 999999, 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 000000. 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
