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: • 3420 • 3480 • 3490 • 3490E • Optical 3480/3490s • 3494 • 3495 • 3590
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.
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—00000 to 99999
Max percentage of tape used—99
Max datasets per output tape—999
3. 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
Running Media Conversion
CARTS TMS User Guide ▼ 109
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.
Datasets are transferred to the new media based upon values set with the active Media Conversion Control file when the job is submitted.
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
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.
Using Media Conversion with Virtual Tape Systems
CARTS TMS User Guide ▼ 111
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.
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.
Set the virtual footage to 0001900. Enter the esoteric unit name of your VTS on the Non-robotic unit field.
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 ===> 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) ===> 0000800
CARTS --- VOLSER Group 1 --- COMMAND ===> User Id-PROD Description ===> VOLSER GROUP 1 Group is active ===> YES Max DSNs per output tape ===> 09999 Virtual Footage ===> 0001900 (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 999999 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 ______
CARTS TMS User Guide ▼ 113