Managing Disk Space with

®
EMC Disk Library for mainframe (DLm)

Technical Note
P/N 300-010-458
REV A01
December 21, 2009

This technical note contains information on these topics:

Š Overview..................................................................................................... 2
Š Virtual Tape Engines ................................................................................. 2
Š Virtual Tape Library .................................................................................. 2
Š Tape volumes in the library...................................................................... 3
Š Allocating a new volume .......................................................................... 4
Š Scratching active volumes ........................................................................ 4
Š Automatic space recovery......................................................................... 5
Š Manual space recovery.............................................................................. 6
Š Best practices .............................................................................................. 7
Š Adding space to the library .................................................................... 10
Š Monitoring library space......................................................................... 10
Š Getting a Q SPACE report at the mainframe ....................................... 11
Š Using scratch pools.................................................................................. 11
Š Configuring partial replication .............................................................. 13
Š Managing different volume sizes .......................................................... 13

1
Overview

Overview
The EMC® Disk Library for mainframe (DLm) is an enterprise-class tape-
on-disk appliance for IBM or IBM-compatible mainframes. The DLm
utilizes disk storage arrays in place of physical tape libraries.
The two major components of a DLm are the Virtual Tape Emulation
Controller (VTEC) and the EMC Celerra® Network Server with
integrated disk storage arrays. The VTEC is a virtual tape subsystem
comprised of one to six Virtual Tape Engines (VTEs) that connects to an
IBM or IBM-compatible mainframe and provides the emulation power of
IBM 3480/3490/3590 tape drives. Celerra Network Server is the
subsystem that provides the VTEC with a highly available and feature-
rich disk storage system.
This technical note will discuss the procedures and best practices for
configuring, monitoring, and managing the disk space available with the
DLm.

Virtual Tape Engines

Each VTE connects to IBM mainframes via FICON or ESCON channels
and emulates standard IBM 3480, 3490, or 3590 tapes drives. As the
mainframe writes a tape volume, identified by its volume serial number
(VOLSER), to one of the emulated tape drives, the VTE writes the data to
its disk storage system. Each mainframe VOLSER equals one file on the
disk storage system.
A single virtual tape library in the VTE normally uses more than one
filesystem (disk) in order to provide performance and scalable capacity.
By using more than one filesystem, a virtual tape library can scale to
hundreds of thousands of tape volumes.
The VTE provides the 3480, 3490, or 3590 tape drive emulations that
respond to channel control words (CCWs) just as physical tape drives
would do. The VTE formats tape data received from the mainframe for
storage on disk and performs all input and output with its disk storage
subsystem.

Virtual Tape Library

Each VTE uses predefined directories that identify the filesystems to be
used. These directories may be shared by all of the VTEs and are
typically named “/tapelib<string>”. <string> may be up to eight

2 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note
 Tape volumes in the library

alphanumeric characters. Characters other than “A–Z, 0–9” are not

allowed, and the first character must be an uppercase letter. Leading and
trailing whitespaces are trimmed.
Most commonly, a single predefined directory, simply named “/tapelib”
and shared by all VTEs, is used. (Examples in this paper will use this
convention.)
Any filesystem that is mounted as a subdirectory to /tapelib will become
part of the virtual library. Subdirectory names assigned to filesystems
within /tapelib must have a two-character name that represents the first
two characters of the alphanumeric VOLSERs, which are stored in that
filesystem. For example, a filesystem mounted as “/tapelib/AA” would
contain all tape volumes written to the VTE with VOLSERs beginning
with the characters “AA”. This would include the volumes with
VOLSERs between AA0000 and AA9999. Likewise a filesystem mounted
at the location “tapelib/BB” would contain the VOLSERs BB0000 –
BB9999 if only numeric characters were used for the final four positions
of the VOLSER.
As an example, a VTE tape library with the following directory structure
would include four filesystems and hold 40,000 tape volumes with
VOLSER ranges of AA0000-AD9999:
/tapelib
/AA
/AB
/AC
/AD

Tape volumes in the library

Once the directory structure has been created and the filesystems have
been formatted and mounted, scratch tape volumes must be initialized
into each filesystem before the VTE can allocate a new volume for
output. Scratch tapes are initialized by the VTE using the INITIALIZE
command in each filesystem.
Each tape volume (VOLSER) stored on a filesystem is contained in one
file. The name of the file is the VOLSER. So, for example, a tape written
with VOLSER “AA0211” will be stored in a file named “AA0211” on the
filesystem mounted on the subdirectory “/tapelib/AA”.
Scratch tapes are distinguished from active tapes by a filename
beginning with “~”. So files named “~BB0055”, “~BA1010”, or
“~DB0000” would all be scratch tapes while files named “AC2043”,
“DD0011”, or “BB2222” would all be active tape volumes in the library.
When scratch volumes are initialized in a filesystem, new files will be

Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note 3
Allocating a new volume

created with a filename beginning with ”~”. For example, if you were to
initialize the VOLSER range “AA0000 – AA0999”, then 1,000 files would
be created on the filesystem mounted at “/tapelib/AA”. The files would
be named “~AA0000”, “~AA0001”, “~AA0002”, and so on through
filename “~AA0999”.
After configuring the tape library, configure the virtual devices. You can
define up to 256 virtual 3480, 3490, or 3590 tape devices on each DLm
VTE. In addition, up to six separate device configurations (up to four in
DLm 1.1 and 1.2) can be stored. The configurations are xmap0 through
xmap5. By default, these configurations are empty.
Finally, if DLm emulated tape drives are configured as a Manual Tape
Library (MTL) on z/OS, the mainframe’s Tape Control Data Base
(TCDB) must contain the same exact tape volumes (VOLSERs) as are
initialized in the DLm library. If you do not define newly initialized
VOLSERs to the TCDB they cannot be used by the DLm. The DLMLIB
utility provides a quick and convenient method of updating the TCDB
on the mainframe. Any time new VOLSERs are initialized in the DLm
the DLMLIB utility should be run on z/OS to add the new VOLSERs to
the MTL.

Allocating a new volume

When the mainframe wants to write a new tape, a load display
command (CCW) is forwarded to the DLm asking for a scratch tape. The
DLm will normally select the filesystem in the library that has the most
available space. Once a filesystem has been identified, the DLm will
search the filesystem for an available scratch tape (that is, a file whose
filename begins with “~”). When a scratch tape is found, the file will be
renamed to remove the “~” from its name, making it an active tape. It
will be mounted on the drive requesting the scratch tape and a
“READY” status will be returned to the mainframe. The mainframe will
read the header records on the tape volume to identify the VOLSER that
has been assigned. If the mainframe unloads the tape without writing
anything to it, the file will again be renamed to put back the “~”; this
returns the tape volume to scratch status. Otherwise the tape will remain
active.

Scratching active volumes

DLMSCR, a scratch utility that runs on the mainframe, is provided to
keep the DLm virtual tape library in sync with the mainframe tape
management system. The scratch utility will read a standard tape scratch

4 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note
 Automatic space recovery

report, identify any volumes stored on the DLm, and send a scratch
request to the DLm to scratch the VOLSER. The DLm will simply rename
the file, placing a “~” in front of the file name. For example, “AA2355”
becomes “~AA2355”. The data, however, is left in the file so that if a
volume has been incorrectly scratched it can be recovered.
Under normal circumstances, all data will persist in a scratched volume
until the volume is reused. However, if the filesystem (disk) begins to
run out of space, a space recovery routine will delete the data to free
space from older scratched volumes.

Automatic space recovery

There are three configuration parameters for controlling space recovery
within a DLm library: SET RECOVER, SET RECOVERAMT, and
SET WARNING.
Š SET RECOVER=nn
Indicates at what percentage of disk full the system should start a
space recovery. For example, SET RECOVER=90 would initiate
space recovery in a filesystem when 90% of that filesystem (disk) is
utilized.
Š SET RECOVERAMT=nn
Indicates how much space the DLm should recover before stopping
space recovery. For example, SET RECOVERAMT=20 would specify
that space recovery should continue until 20% of the filesystem has
been recovered. A system configured with SET RECOVER=90 and
SET RECOVERAMT=20 would start recovering space in any
filesystem reaching 90% utilization and stop recovering space when
that filesystem achieved 70% utilization.
Š SET WARNING=nn
Specifies the percentage full at which the DLm should issue warning
messages indicating a filesystem is becoming full. The SET
WARNING value should normally be higher than the SET
RECOVER value.
DLm space recovery uses a Least Recently Used (LRU) algorithm to
delete data from scratched volumes (files whose names begin with “~”)
leaving only the header records. In other words, when a disk is nearly
full, the DLm will delete data from the oldest scratched tapes to make
room for new tapes. The space recovery routine will continue to delete
data from old scratch volumes until it either reaches the amount of space
to be recovered or it runs out of scratch volumes containing old data.

Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note 5
Manual space recovery

The “Best practices” section below has specific recommendations.

Manual space recovery

Under normal operating conditions there is rarely any reason to
manually recover space from scratched tape volumes (VOLSERs). As
described above, the DLm will automatically recover space from any
filesystem that reaches the SET RECOVER amount that has been defined.
However, because automatic space recovery can initiate at any time, you
may decide that performing manual space recovery provides better
control of the library and prevents automatic space recovery from
starting at inappropriate times.
The mainframe-based scratch utility, DLMSCR, can be used to delete
data from previously scratched volumes (VOLSERs).
DLMSCR has a FREESPACE parameter that will result in deletion of
data on a volume. But the volume must already be in a scratch state (that
is, the filename must begin with “~”). Similar to auto-recovery, when
DLMSCR FREESPACE is used against a VOLSER, the data of the
VOLSER is deleted from the file, thus freeing the space for use in new
allocations. The volume’s headers are left in place to comply with TMS
verification requirements.
DLMSCR normally reads a scratch report from your TMS, identifies each
VOLSER on the scratch report that resides on the DLm, and sends a
scratch request for that VOLSER to the DLm. By default, you cannot free
space from a VOLSER at the same time you scratch it. The FREESPACE
option does not work when scratching an active VOLSER. However, for
tapes that have previously been scratched you can delete the data within
those tapes by re-running DLMSCR with the FREESPACE option. Keep
in mind, however, that once the FREESPACE option has been used
against a VOLSER that volume can no longer be recovered if a mistake
has been made.
Finally, DLMSCR also offers a FREEAFTERSCR option that will perform
a scratch of a VOLSER and delete the data in the VOLSER on a single
execution of DLMSCR. EMC recommends that FREEAFTERSCR not be
used as a standard option when running DLMSCR. Deleting data at the
time you scratch a VOLSER means that you can never recover the data
on a tape that has been accidentally scratched.

6 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note
 Best practices

Best practices

Setting up a new library

When defining a new library, the following guidelines are
recommended:
1. Use multiple filesystems.
Unless you are creating a very small library with limited throughput
and capacity requirements, it is best to spread the data across more
than one filesystem. A minimum of four filesystems should be used
for optimum performance.
For example, even if the total library will contain less than 2,000 tape
volumes, it is best to spread 500 volumes over four filesystems rather
than put all volumes in one filesystem.
2. Plan your filesystems based on tape volume size.
Most installations use only numeric VOLSERs for the last four
characters in the six-character VOLSER. This results in each
filesystem containing no more than 10,000 tape volumes, xx0000 –
xx9999, where xx is the fixed portion of the VOLSER relating to the
filesystem name.
The disk capacity required for a filesystem can be calculated based
on the maximum number of tape volumes times the average tape
volume size. SMF data can be used to determine the average size of
your tape volumes. But remember that the DLm will perform
hardware data compression when requested. (Please note that
compression ratios cannot be predicted with absolute certainty
beforehand – they are entirely dependent upon the nature of the data
being compressed.)
As an example, assume your average tape volume size according to
SMF is 1 GB. Further, for planning purposes, assume a 2-to-1 data
compression ratio. In other words, a 1 GB volume will be stored in
500 MB of space. In this example your total filesystem sizes should
not exceed 5 terabytes (500 MB x 10,000 volumes = 5,000,000 MB).
Remember, however, that you do not have to put 10,000 volumes in
each filesystem. If your entire library only needs to store 10,000
volumes then it is better to use four filesystems of 1.25 TB (500 MB x
10,000 / 4) to hold 2,500 volumes each.
3. Make your filesystems the same size.
The DLm VTE will work with filesystems of different sizes. But it is
much better if all are of the same capacity. When the DLm VTE

Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note 7
Best practices

attempts to mount a new scratch volume, it will use the free space
within the filesystems as selection criteria for allocation. If there are
three small filesystems and one very large filesystem allocated, then
most new writes will tend to go into the large filesystem until it
starts to fill up. Equal-size filesystems, on the other hand, cause the
DLm VTE to spread the work across the filesystems; this results in
overall improved performance of the system over time.
For these reasons, EMC recommends only using same-size file
systems within a tapelib. This is the only officially supported
configuration.
4. Do not overinitialize scratch tapes.
EMC recommends defining an adequate number of scratch tapes to
meet demand over the next 9 -12 months. This recommendation
minimizes the overhead required to manage an excessive number of
scratch tapes.
For example, if it is estimated that 4,000 tapes will be needed over
the next year, then set up four filesystems with 1,000 scratch tapes
initially, and add more scratch tapes during the year as needed.
While minimal, there is overhead and time involved in managing
more scratch tapes then you will use.
If over two years, you will need 20,000 tapes, then plan to have four
filesystems of 5,000 volumes at the end of two years. Begin by
initializing 1,000 volumes each into the four filesystems and then
add more scratch volumes as you go.
If disk space is at a premium, plan the initial four filesystems with
capacity needed for the next year. New filesystems can be added to
the DLm VTE configuration at any time without disrupting
operation of the DLm.
Finally, never initialize more scratch tapes within a filesystem then
you plan to write to that filesystem. If you plan your filesystem to
hold 2,000 volumes, do not initialize more than 2,000 volumes.
Initializing more volumes than needed results in consuming extra
disk space, lower performance, and an increased chance that a
filesystem will run out of space. If your volume sizes do not vary
widely from the average size, a well-planned filesystem with the
correct number of scratch tapes initialized should never run out of
space.
5. Set the parameters to control space recovery.
The SET RECOVER parameter should normally be set fairly high (it
defaults to 85%). Remember that this parameter indicates when the

8 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note
 Best practices

system should begin its space recovery routine on a filesystem. If

you set it too low, the system is going to be unnecessarily
performing space recovery when there is still plenty of space in the
filesystems.
Set the SET RECOVERAMT parameter to a reasonable amount. The
default value is 5%. Be aware that this default value could cause the
system to frequently run space recovery on a filesystem that is nearly
full, constantly trying to recover space 5% at a time. If you are
frequently scratching tapes, setting this number higher will
minimize the number of times space recovery will start. A number
like 10 or even 20% may be more appropriate.
Finally set the SET WARNING percentage higher than the SET
RECOVER parameter. (It defaults to 88%.) SET WARNING tells the
system when to issue warning messages indicating a filesystem is
nearly full. If you set recovery to begin at 90% full and your SET
WARNING parameter is set at 85%, you will be seeing warning
messages saying your disk is nearly full before the system has even
tried to free unneeded scratch data. On the other hand, if your SET
WARNING parameter is at 92%, then when you start getting
warning messages you know your disk is really almost full and there
may not be any more space that can be recovered.
After initial installation, as a DLm is placed into production, EMC
recommends that you change the default values of these space recovery
parameters (shown below) before the DLm is used in real time in your
company.
Š WARNINGPERCENT = 88
Š RECOVERYPERCENT = 85
Š RECOVERAMT = 5
In connection with these parameters, some customers have adopted the
practice of using Command Processor 501 via JCL from the mainframe to
initiate space recovery during times when the DLm is lightly loaded.
To do this, a batch job on the mainframe would use Command Processor
501 to set the RECOVERYPERCENT value on one of the VTEs to a very
low value. This causes that VTE to initiate space recovery. An hour or so
later a second batch job would be run on the mainframe to reset
RECOVERYPERCENT for that VTE back to the default. Note that space
recovery processing needs to be undertaken by only one of the VTEs that
have access to a given set of VOLSER ranges.
There are exceptions to these guidelines for recovering disk capacity. For
example, if your library grows rapidly in size, you may want to set these
thresholds lower so that space warnings give you plenty of time to add

Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note 9
Adding space to the library

additional space to the library. If your library contains mostly long-term

archive volumes that are rarely scratched, then you may want SET
RECOVER set very high so that the system is not spending time trying to
recover space in a filesystem with no scratched volumes. And you may
want to have SET WARNING set lower to give yourself plenty of
advanced warning.

Adding space to the library

Suppose you have built your library with four filesystems. Each
filesystem was originally set up with 2.5 TB of space and planned to
support 5,000 volumes. You have now reached the point where you have
in excess of 19,000 volumes in your library and all four filesystems are
95% full.
At this point, the best way to increase capacity is to add additional
filesystems. Let’s assume that you only need space for an additional
10,000 volumes. You can either add a fifth 5 TB filesystem and initialize it
with 10,000 VOLSERs, or you can add multiple filesystems.
Keep in mind that the DLm VTE will allocate new tapes to the filesystem
with the most free space. So, if you add a single filesystem, the DLm will
tend to allocate all new tape volumes to that filesystem. Instead of
having I/O spread across four filesystems as you do now, adding one
empty filesystem will cause write I/O to predominantly occur to that
one filesystem, lowering your overall system performance. A better
approach is to add multiple filesystems at once, allowing the system to
allocate new tape volumes across all those new filesystems so that no one
filesystem is overburdened.
In addition, when adding multiple new filesystems, best performance is
achieved when they are all the same size. If your existing library is
almost full, the new filesystems do not need to be the same size as the
existing filesystems. Making them equal in size ensures allocations will
be spread across all of them.

Monitoring library space

Monitoring a DLm library’s space is simple and straightforward. The
DLm VTE includes a QUERY SPACE command that provides the
information you need to easily monitor the status of your library space.
Q SPACE can be issued on any VTE’s console or it can be invoked from a
mainframe batch job via the z/OS DLMCMD program.

10 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note
 Getting a Q SPACE report at the mainframe

Getting a Q SPACE report at the mainframe

As previously indicated, Q SPACE is a command that can be issued at
the console on any DLm. On a DLm with an Access Control Point (ACP),
the operator could access any of the VTEs controlled by the ACP and
issue the Q SPACE command.
Most installations, however, do not actively monitor the DLm via its
console. For those customers the easiest approach to getting a Q SPACE
report is to periodically initiate a batch job on the mainframe that will
run the Q SPACE command on the controller and create a mainframe
report with the Q SPACE output.
To do this, the DLm provides a small mainframe-based utility,
DLMCMD, which can be run under z/OS to send commands over a
channel to a DLm VTE.
Additionally, a DLm-based command processor is provided that will
produce the Q SPACE output.
Once DLMCMD has been installed on the mainframe following
instructions in the EMC Disk Library for mainframe User Guide, and DLm
Command Processor 501 has been installed on the DLm following
instructions in the EMC Disk Library for mainframe Command Processors
User Guide, the following job can be executed to retrieve the Q SPACE
report:
//QSPACE JOB (A),'QSPACE',CLASS=A,MSGCLASS=X
//COMMAND EXEC PGM=DLMCMD
//STEPLIB DD DISP=SHR,DSN=apf.loadlib
//DLMCTRL DD UNIT=/xxxx,LABEL=(,SL),DISP=(NEW,DELETE),
// DSN=DLM.CMDPASS.EXAMPLE
//SYSUDUMP DD SYSOUT=*
//DLMLOG DD SYSOUT=*
//DLMCMD DD *
RUNWAIT (600) 501 "q space" "/tapelib" "BFL501.FLAT"
/*
//READBAC EXEC PGM=IEBGENER
//SYSUT1 DD UNIT=/xxxx,VOL=SER=BFL501,DISP=OLD,LABEL=(,NL),
// DSN=BFL501.FLAT,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132)
//SYSUT2 DD SYSOUT=*,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY

Using scratch pools

Most mainframe tape management systems (TMS) provide the ability to
divide scratch tapes into pools. These systems allow customers to use
different names to request a scratch tape. So, while the mainframe would

Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note 11
Using scratch pools

normally use “SCRTCH” and “PRIVAT” to request a scratch tape, using

scratch pools a customer can use any name (synonym) they wish. For
example, “WORK”, “PAYRLL”, and “TEMP” could all be used as a
scratch tape synonym.
DLm VTEs support scratch synonyms allowing customers to configure
character strings to be recognized as a request for scratch. As shipped,
the DLm VTE normally treats any load request for “SCRTCH“ or
“PRIVAT“ as a request for a new scratch tape. Any string other than
“SCRTCH“ or “PRIVAT“ sent as part of a load display will be assumed
to be a VOLSER. For example, if the DLm VTE had not been configured
with a scratch synonym, a load display containing “WORK“ would
result in a tape not found condition since the DLm would assume
“WORK“ was a valid VOLSER and when it could not find a directory
“/tapelib/WORK“, an error would occur.
However, if the DLm VTE was properly configured with “WORK“ as a
valid scratch synonym in the general configuration parameters for the
library, “WORK“ would be recognized as a valid request for scratch and
an available scratch volume would be mounted.
Scratch synonyms can be used to further separate tape volumes by
VOLSER. For instance, a customer can elect to have tapes from payroll
going to VOLSERs beginning with “AA“ and “BB“ while volumes from
other applications use VOLSERs beginning with “CC “,“DD“,“EE“, and
“FF“.
To do this a customer would set up two scratch synonyms, “PAYRLL“
and “SCRTCH“, for example. In the DLm VTE configuration they would
define the scratch synonyms “PAYRLL=AA,BB“ and
“SCRTCH=CC,DD,EE,FF“. The tape library would be structured as:
/tapelib
/AA
/BB
/CC
/DD
/EE
/FF

In this configuration, any time a request for “SCRTCH“ is received, the

DLm VTE would allocate a scratch tape from any of the filesystems at
CC, DD, EE, or FF. When a request for PAYRLL is received, the DLm
VTE would allocate a scratch tape from AA or BB.

12 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note
 Configuring partial replication

Configuring partial replication

One frequent use of scratch pools with the DLm VTE is for partial library
replication. Consider the configuration shown below. In this
environment, the installation wants to replicate all backup tapes and
archive tapes to their DR site. Work tapes that are not needed past job
execution do not need to be replicated.

Figure 1 Configuration for partial library replication

To accomplish this requirement the customer would define two scratch
pools, for example, “DRTAPE“ and “WORK“. DRTAPE would be
assigned to VOLSERs beginning with “AA“,“BB“, and “CC“. WORK
would be assigned to VOLSERs beginning with “DD“ and “EE“. The
library would be defined as:
/tapelib
/AA
/BB
/CC
/DD
/EE

The filesystems pointed to by …/AA, …/BB, and …/CC would all be

replicated by the storage subsystem to the remote location.
With this configuration any time a backup or archive tape is created the
scratch tape allocation request is made with the synonym “DRTAPE“.
This results in allocation of a VOLSER on the top three disks in the
picture. Any work tapes are allocated using the scratch synonym
“WORK“. This results in allocation of a VOLSER residing on the bottom
two disks at the production site.

Managing different volume sizes

Another possible use of scratch pools would be to separate large tape
volumes from small tape volumes. Consider the data center using tape to
perform large volume data archives. Assume, for example, that long-

Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note 13
Managing different volume sizes

term archive tapes have an average volume size of 1 TB. While most of
the data center’s other tapes have a volume size of 500 GB, for space
planning purposes, it may be desirable to separate these “large format”
tapes from the average tapes, which are half their size.
Separation by size can be easily accomplished using scratch pools.
Again, for example, assume a library structure defined as follows:
/tapelib
/AA
/BB
/CC
/DD
/EE

But unlike previous examples, assume that in this case filesystems

mounted at …/AA, …/BB, and …/CC are defined to hold 10,000
volumes with an average size of 500 GB each. And filesystems …/DD
and …/EE are defined to hold 1,000 volumes with an average size of 1
TB each.
Two tape pools would be defined. “SMTAPE=AA,BB,CC” would
identify a request for a scratch tape for a 500 GB volume.
“LGTAPE=DD,EE” would identify a request for a large format scratch
tape capable of holding a 1 TB volume.
In this configuration the entire library would hold 30,000 500 GB
volumes and 2,000 1 TB volumes. All 500 GB volumes would have serial
numbers in the range of AA0000 – CC9999. The library would also hold
2,000 1 TB volumes. These large volumes would have a serial number
from the ranges DD0000-DD0999 or EE0000-EE0999. And, as long as the
JCL allocating tape correctly used the scratch synonyms SMTAPE and
LGTAPE, the library should never run out of space.

Copyright © 2009 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC
CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires
an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks
on EMC.com.
All other trademarks used herein are the property of their respective owners.

14 Managing Disk Space with EMC Disk Library for mainframe (DLm) Technical Note