What’s Using Up All My Tapes? – Using Tape Management Catalog Data

BrettBy Dave Heggen

tape management catalog

Most of the data processed for IntelliMagic Vision for z/OS Tape is performance, event or activity driven, obtained from SMF and the Virtual Tape Hardware. Did you know that in addition to the SMF and TS7700 BVIR data, IntelliMagic Vision could also process information from a Tape Management Catalog (TMC)? Having this type of data available and processing it correctly is critical to answering the question “What’s using up all my tapes?”.

We’re all set up and distributed scratch lists. This is a necessary (and generally manual) part of maintaining a current tape library. It does require participation for compliance. Expiration Dates, Catalog and Cycle management also have their place to automate the expiration end of the tape volume cycle. This blog is intended to address issues that neither compliance nor automation address.

When is TMC Data Important?

I can think of two scenarios where analysis of the TMC data is helpful to uncover private tapes that need to be scratched. I’m certain there are other scenarios that also need investigation.

  1. ARCTVEXT is not working. As a hierarchical storage management (HSM) specialist, I was called into a customer’s shop to find out why HSM was using so many tapes and all efforts by the customer failed to free them. In this case, when the list of tapes known to HSM was compared to the list of tapes owned by HSM in the TMC, the list in the TMC was much larger. HSM recycle thought it was freeing the tapes, but the necessary communication to the Tape Management System was failing.
  2. Catalog Control (or lack thereof). Tapes under catalog control have an automatic scratch occurring when the Generation Data Groups (GDG) are filled, and the next +1 generation is created. What happens when the GDG used in the application is no longer creating a +1 generation? You then have a situation where the GDS’s remain as permanent tapes until someone finds and removes them.

IntelliMagic Vision Supports 5 Different TMC’s

Processing the TMC data is somewhat problematic. First, there are many products in use by customers to perform the function of a TMC. Fortunately, by using the utility available in IBM Tape Tools, IntelliMagic Vision can support 5 different TMCs. The TMCs supported by the FORMCATS utility are CA1, RMM, Zara, TLMS and Control T. By using this utility, the information extracted from these products is placed into a common format.

Once the TMC data is extracted and processed into the common format, the next step is to process this data alongside either SMF and/or BVIR data. The reason TMC data must be processed with other data is that by itself, this data has no date or timestamp. The data from a TMC represents a snapshot of what the library looked like at a particular moment in time. To determine when that moment in time was, we use the last date/timestamp from data containing intervals to assign a date. It is possible to process SMF or BVIR data containing multiple days. In contrast, TMC data must be from a single day and the day assigned is from the last interval of the companion data. It is possible to process multiple TMCs for a tape environment, each representing a unique cross section of the tape library.

Volume Group Definitions to Assign the Applications to Library Entries

Next, we need some meaningful Volume Group Definitions to assign the Applications to Library entries. IntelliMagic Vision for z/OS Tape already provides Volume Group Definitions to associate z/OS Workloads to Applications. An example would be:

‘VOLGROUP BACKUP, PGM = (ADRDSSU,FDR*);’.

This example assigns the workload Backup to all instances in the SMF data where PGM=ADRDSSU (DFSMS/dss) and PGM=FDR* (Fast Dump/Restore) were used by the job. This definition translates well from SMF data to the TMC data, because in all cases, the TMC data contains information about what the creating program was when the data was initially written. Another classification that may work well is DSN=. Volume Group Definitions that may not work would be based on DDNAME=, DEVICE=, or MEDIA=. In some cases, this information would not be available or may conflict with the information captured when the data set was initially created.

Trend Tape Volume/Space Usage

With this information in hand, it is possible to capture a snapshot of what the Tape Library was like on a particular day for a set of applications (number of volumes/number of MB). Plot this data across multiple days/weeks/months to see tape volume/space usage increase or decrease. Over a period of a few days this information is usually uninteresting, but over a period of months, this can be very helpful information. The intent is to spot data with a seemingly permanent retention and prompt discussions with the application owner concerning expiration criteria for now and for use in the future.

Example Drilldown Sequence

Intial Volumes

Start from initial Volumes by Volume Group report

Volume Group Report

Drill down into the Other category and display the Programs

Syncsort

Drill down into Syncsort and show detail from current TMC

In summary, if the Volume groups are set up with meaningful application/workload segments, then these reports are useful to spot unhealthy trends in private tape usage over time, and identify the location of likely suspects to restore a scratch pool back to safer levels.

Leave a Reply

Your email address will not be published. Required fields are marked *