DLM - User Guide PDF

EMC® Disk Library for mainframe
Version 3.0
User Guide
P/N 300-012-441
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2011 EMC Corporation. All rights reserved.
Published September, 2011
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 regulatory document for your product line, go to the Technical Documentation and
Advisories section on EMC support website.
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.
2 EMC Disk Library for mainframe Version 3.0 User Guide

Contents
Preface
Chapter 1 Overview of EMC Disk Library for Mainframe

Introduction to Disk Library for mainframe................................. 18
DLm6000 architecture and models................................................. 19
VTEC............................................................................................ 21
Backend storage ......................................................................... 24
Mainframe channel interfaces.................................................. 26
DLm devices and capacity............................................................... 30
Tape emulation .................................................................................. 32
Virtual tape drive states ............................................................ 32
Data formats ............................................................................... 33
Support for physical tape drives .................................................... 34
High availability features ................................................................ 35
VTEC............................................................................................ 35
VNX7500 ..................................................................................... 35
Data Domain .............................................................................. 36
Features and benefits........................................................................ 40
Chapter 2 DLm Operations

Management access to DLm............................................................ 44
Gather connection data ............................................................. 44
Access the DLm Console .......................................................... 45
Set date and time ....................................................................... 47
User administration................................................................... 49
Access a VTE...................................................................................... 54
VT console................................................................................... 55
VTE reboot .................................................................................. 56
EMC Disk Library for mainframe Version 3.0 User Guide 3

Contents
Power up DLm.................................................................................. 57
VNX power-up........................................................................... 57
DD890 power-up ....................................................................... 61
ACP power-up ........................................................................... 62
VTE power-up............................................................................ 63
Power down DLm ............................................................................ 67
Power down the VTE ................................................................ 68
Power down DD890 .................................................................. 69
Power down VNX7500 ............................................................. 70
Power down the ACP ............................................................... 73
Start and stop tape devices.............................................................. 74
Initialize scratch volumes ................................................................ 76
Support access to DLm .................................................................... 78
ESRS............................................................................................. 78
Modem support ......................................................................... 79
Chapter 3 DLm Administration

Tape libraries ..................................................................................... 82
Lock filesystem .......................................................................... 83
Backward compatibility............................................................ 84
Configure virtual devices ................................................................ 85
Planning considerations ........................................................... 85
DLm configuration files............................................................ 85
Configure global parameters ................................................... 85
Add devices................................................................................ 89
Scratch synonyms...................................................................... 96
Save configuration..................................................................... 99
Delete a device range ................................................................ 99
Manage configuration files............................................................ 101
Activate or install a configuration......................................... 101
Create a new configuration .................................................... 101
Copy a configuration .............................................................. 102
Modify or delete a configuration .......................................... 102
Tape Erase ........................................................................................ 103
Space erase policy.................................................................... 103
Time-to-Live erase policy ....................................................... 103
Manage VTE and ACP logs........................................................... 105
VTE logs .................................................................................... 105
Support data............................................................................. 106
Back-end tape support ................................................................... 108
Direct Tape ................................................................................ 108
Export to and import from tapes............................................ 111

Contents
DLm diagnostic reporting.............................................................. 113

SNMP..........................................................................................113
ConnectEMC..............................................................................114
Data Domain DD890 alert notifications.................................115
Configure message types and recipients ...............................115
AWSPRINT library utility............................................................ 117
Chapter 4 DLm Replication

Overview .......................................................................................... 120
Replication terminology................................................................. 122
VNX replication............................................................................... 124
Supported configurations ........................................................124
VNX replication procedure .....................................................125
VNX RepOutOfSyncHours feature ........................................126
DLm VNX replication and disaster recovery........................126
Tape catalog considerations ....................................................129
Deduplication storage replication ................................................ 130
Supported configurations ........................................................131
Replication session setup ........................................................ 131
Throttling .................................................................................. 132
Recovery point.......................................................................... 132
Recovery time ........................................................................... 132
Disaster recovery in Data Domain systems ..........................132
Directory replication flow........................................................134
Chapter 5 Mainframe Tasks

Configure devices............................................................................ 138
Real 3480, 3490, or 3590 .................................................................. 139
Manual tape library ........................................................................ 140
MTL considerations for VTE drive selection............................... 143
MTL-related IBM maintenance ..................................................... 145
EMC Unit Information Module .................................................... 146
Missing Interrupt Handler............................................................. 148
Mainframe configuration for deduplicated virtual tapes ......... 149
Dynamic device reconfiguration considerations ........................ 149
DFSMShsm considerations ............................................................ 149
Specify tape compaction ................................................................ 150
Locate and upload the DLm utilities and JCL for z/OS............ 151
Downloading and using the DLm utilities and JCL for z/OS .
151
GENSTATS utility .................................................................... 153

Contents
DLm scratch utility program .................................................. 153

DLMCMD utility program...................................................... 158
DLMVER utility program ....................................................... 160
Initial program load from a DLm virtual tape ........................... 162
Create a stand-alone IPL tape on DLm ................................. 162
IPL from the stand-alone IPL tape ......................................... 163
IPL condsiderations for DLm ................................................. 163
Chapter 6 Using DLm with Unisys

Unique DLm operations for Unisys mainframes....................... 166
Autodetection........................................................................... 166
Load displays ........................................................................... 166
Mount "Ready" interrupt........................................................ 166
Query Config command......................................................... 166
Ring-Out Mount request ........................................................ 166
Scratch request ......................................................................... 167
Configuring for Unisys .................................................................. 168
Device type ............................................................................... 168
Labels......................................................................................... 168
Scratch tapes............................................................................. 168
Initializing tapes for Unisys .......................................................... 170
Configuring the mainframe for DLm .......................................... 171
Chapter 7 z/OS Console Support

z/OS Console operation ................................................................ 174
DLMHOST....................................................................................... 175
Installing DLMHOST............................................................... 175
Running DLMHOST ................................................................ 176
DLMHOST configuration file ................................................. 177
Using z/OS Console support........................................................ 179
DLMHOST commands ............................................................ 180
WTOR command examples .................................................... 181
Appendix A Virtual Tape Operator Command Reference

Virtual Tape Operator command reference ................................ 184
Syntax ........................................................................................ 184
DISABLE ................................................................................... 184
ENABLE.................................................................................... 184
EXPORT .................................................................................... 184
FIND .......................................................................................... 185
HELP ......................................................................................... 186

Contents
IMPORT..................................................................................... 186
INITIALIZE............................................................................... 187
LOAD......................................................................................... 188
QUERY....................................................................................... 189
QUIESCE ................................................................................... 196
READY ...................................................................................... 197
RESET CHANNEL ADAPTER .............................................. 197
REWIND.................................................................................... 198
SAVE TRACE............................................................................ 198
SET ............................................................................................. 198
SHOW........................................................................................ 202
SNMP......................................................................................... 202
STARTVT................................................................................... 202
STOPVT ..................................................................................... 203
STOP CHANNEL ADAPTER ................................................ 203
UNLOAD .................................................................................. 203
UNQUIESCE............................................................................. 204
UNREADY ................................................................................ 204
Appendix B AWSTAPE Information

AWSTAPE format............................................................................ 206
Appendix C Load Display Command—CCW Opcode x'9F'

Load display messages................................................................... 208
Format Control Byte ................................................................ 208
Messages 0 and 1...................................................................... 208
Load display data............................................................................ 210
Format Control Byte .................................................................210
Appendix D Extract DLm statistics

DLm statistics files .......................................................................... 214
Extraction utility.............................................................................. 214
Hourly statistics ....................................................................... 214
Volume statistics....................................................................... 215
Mount statistics ........................................................................ 216
Unmount statistics ................................................................... 216
Example 1 .................................................................................. 217
Example 2 .................................................................................. 218
Example 3 .................................................................................. 219
Example 4 .................................................................................. 220

Contents
Appendix E System Messages

Message format ............................................................................... 222
DLm system messages ................................................................... 223
Call home messages ....................................................................... 366
EMCvts messages ........................................................................... 367
z/OS system messages .................................................................. 369
DLMCMD messages ............................................................... 369
DLMLIB message .................................................................... 370
DLMSCR messages ................................................................. 370
DLMVER messages ................................................................. 373
VTEC errors that generate ConnectEMC events........................ 374
Index

Figures
Title Page
1 DLm6000 overview ........................................................................................ 20
2 Front view of the VTE.................................................................................... 21
3 Rear view of a VTE......................................................................................... 22
4 Front view of the ACP ................................................................................... 23
5 Rear view of the ACP .................................................................................... 23
6 24-port AT-9924TL switch............................................................................. 24
7 Fujitsu XG2000R switch................................................................................. 24
8 DD890 Controller—Rear view ..................................................................... 25
9 DLm Console login page............................................................................... 46
10 DLm Console .................................................................................................. 47
11 DLm date and time ........................................................................................ 48
12 User ID creation.............................................................................................. 50
13 LDAP user authentication............................................................................. 52
14 VT console ....................................................................................................... 54
15 Rear of the SPS ................................................................................................ 58
16 Storage processor LEDs................................................................................. 58
17 VNX7500 cabinet ............................................................................................ 60
18 DD890 controller - front view....................................................................... 61
19 ACP indicators and controls......................................................................... 62
20 VTE indicators and controls ......................................................................... 64
21 VT console with VT application................................................................... 75
22 EMC Secure Remote Support ....................................................................... 78
23 Global options................................................................................................. 86
24 Control units ................................................................................................... 89
25 Add devices section ....................................................................................... 91
26 Scratch Synonyms .......................................................................................... 97
27 Save configuration.......................................................................................... 99
28 System status................................................................................................. 105
29 VTE logs......................................................................................................... 106
30 Gathering ACP and VTE support data ..................................................... 106

Figures
31 SNMP configuration .................................................................................... 114

32 Alert messages.............................................................................................. 116
33 DLm replication............................................................................................ 121
34 Unisys Device Panel .................................................................................... 169
35 AWSTAPE single disk file .......................................................................... 206

Tables
Title Page
1 DD890 stream count limits............................................................................. 25
2 FICON adapter LED indicators..................................................................... 29
3 DLm6000 device details.................................................................................. 30
4 Details of FICON connections ....................................................................... 31
5 DLm system access details............................................................................. 44
6 DD890 controller LEDs................................................................................... 62
7 Example of LIBRARY-ID and LIBPORT-ID .............................................. 141
8 Parameters in DLMSCR ............................................................................... 154
9 Error code from DLMCMD ......................................................................... 159
10 Load display data.......................................................................................... 210
11 Format Control Byte ..................................................................................... 210

Tables

Preface
As part of an effort to improve and enhance the performance and capabilities

of its product lines, EMC periodically releases revisions of its hardware and
software. Therefore, some functions described in this document may not be
supported by all versions of the software or hardware currently in use. For
the most up-to-date information on product features, refer to your product
release notes.
If a product does not function properly or does not function as described in
this document, please contact your EMC representative.
Note: This document was accurate as of the time of publication. However, as

information is added, new versions of this document may be released to the
EMC Online Support website. Check the EMC Online Support website to
ensure that you are using the latest version of this document.
Purpose EMC Disk Library for mainframe (DLm) provides IBM tape drive
emulation to the z/OS mainframe using disk storage systems in place
of physical tapes. This guide provides information about the features,
performance, and capacities of DLm 3.0 and later. It also includes
installation and configuration information that is required for
ongoing operation.
Audience This guide is part of the EMC DLm documentation set, and is
intended for use by system operators to assist in day-to-day
operation. Installation, configuration, and maintenance tasks must be
accomplished by qualified EMC service personnel only.
Readers of this document are expected to be familiar with tape library
operations and the associated tasks in the mainframe environment.

Preface
Related The following EMC publications provide additional information:

documentation
◆ EMC Disk Library for mainframe Physical Planning Guide
◆ EMC Disk Library for mainframe Release Notes
◆ EMC Disk Library for mainframe Command Processors User Guide
◆ Using VNX Replicator (V2)
◆ Using SnapSure on VNX
The EMC documents specified here and additional VNX information
are available in the EMC Online Support website.
The Data Domain documents specified here and additional Data
Domain information are available in the Data Domain portal:
https://my.datadomain.com
Data Domain documentation is also available on the Data Domain
documentation CD that is delivered with DD890.
Conventions used in EMC uses the following conventions for special notices:
this document
DANGER
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided,
could result in death or serious injury.
! CAUTION
CAUTION, used with the safety alert symbol, indicates a
hazardous situation which, if not avoided, could result in minor or
moderate injury.
Note: A note presents information that is important, but not hazard-related.
! IMPORTANT
An important notice contains information essential to software or
hardware operation.

Preface
Typographical conventions
EMC uses the following type style conventions in this document.
Normal Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
• Names of resources, attributes, pools, Boolean expressions,
buttons, DQL statements, keywords, clauses, environment
variables, functions, utilities
• URLs, pathnames, filenames, directory names, computer
names, filenames, links, groups, service keys, file systems,
notifications
Bold Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs,
processes, services, applications, utilities, kernels,
notifications, system calls, man pages
Used in procedures for:
• Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
• What user specifically selects, clicks, presses, or types
Italic Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
Courier Used for:
• System output, such as an error message or script
• URLs, complete paths, filenames, prompts, and syntax when
shown outside of running text
Courier bold Used for:
• Specific user input (such as commands)
Courier italic Used in procedures for:
• Variables on command line
• User input variables
<> Angle brackets enclose parameter or variable values supplied by
the user
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{} Braces indicate content that you must specify (that is, x or y or z)
... Ellipses indicate nonessential information omitted from the
example

Preface
Where to get help EMC support, product, and licensing information can be obtained as
follows.
Product information — For documentation, release notes, software
updates, or for information about EMC products, licensing, and
service, go to the EMC Online Support website.
Technical support — For technical support, go to EMC Online

Support website and choose Support. On the Support page, you will
see several options, including one for making a service request. Note
that to open a service request, you must have a valid support
agreement. Please contact your EMC sales representative for details
about obtaining a valid support agreement or with questions about
your account.
Your comments Your suggestions will help us continue to improve the accuracy,
organization, and overall quality of the user publications. Please send
your opinions of this document to:
techpubcomments@emc.com

1
Overview of EMC Disk
Library for Mainframe
This chapter provides an overview of EMC Disk Library for

mainframe. Topics include:
◆ Introduction to Disk Library for mainframe.................................. 18
◆ DLm6000 architecture and models.................................................. 19
◆ DLm devices and capacity................................................................ 30
◆ Tape emulation ................................................................................... 32
◆ Support for physical tape drives...................................................... 34
◆ High availability features.................................................................. 35
◆ Features and benefits......................................................................... 40
Overview of EMC Disk Library for Mainframe 17

Overview of EMC Disk Library for Mainframe
Introduction to Disk Library for mainframe

The EMC® Disk Library for mainframe (DLm) family of products
provides IBM System z mainframe customers the ability to replace
their physical tape libraries, including traditional virtual tape
libraries such as the IBM VTS and Sun/STK VSM, with dynamic
tapeless virtual tape solutions, eliminating the challenges tied to
traditional tape-based processing.
Some customers have already implemented mainframe host-based
tape-emulation solutions such as IBM VTFM (formally known as
CopyCross) and CA Vtape. However, these solutions utilize
expensive host CPU cycles to perform the tape operations, and use
expensive direct access storage device (DASD) space to keep the tape
volumes. DLm provides the option for these customers to offload the
tape emulation processes from the mainframe host and free up DASD
space.
DLm works seamlessly with the mainframe environment, including
the major tape management systems, DFSMS, DFHSM, and backup
applications such as DFDSS and FDR, and others without the need to
change any of the customer's JCL statements. There is no need to start
a task or define a specific subsystem to operate DLm, since the
mainframe host sees the DLm just as tape devices. DLm tape drives
can be shared across LPARs without the need for additional tape
sharing software through local device varying or through the
implementation of MTL definitions.
DLm provides disaster recovery protection using bidirectional
replication between two DLm systems in the same or different sites. It
also supports unidirectional replication from one DLm system to up
to four DLm systems that could be in different sites. Since the tape
information is kept on disk, DLm enables you to perform disaster
recovery tests without compromising your business continuance by
having to stop replication during testing.
DLm offers deduplication features that deliver the aggregate
throughput performance needed for enterprise data centers. DLm's
in-line deduplication provides the most efficient solution for storing
virtual tapes for backup and archive applications. This results in
lower storage costs and efficient use of replication links as only the
unique data is transported between the sites.

In summary, the DLm offers you many benefits over traditional tape
libraries and virtual tape libraries including high performance,
higher reliability, advanced information protection, and overall lower
total cost of ownership (TCO).
DLm6000 architecture and models

The major components of a DLm6000 system are the virtual tape
emulation controller (VTEC) and the backend storage system that can
be one of the following or a combination of both:
◆ EMC VNXTM (VNX7500) with integrated disk storage arrays
◆ Data Domain® storage system (DD890)
DLm provides deduplicated storage using Data Domain systems and
traditional disk storage using EMC VNX systems. You can have one
of the storage types or a combination of them. For documentation
purposes, we will use the following terms:
◆ Deduplication storage model: DLm with Data Domain storage
only
◆ VNX storage model: DLm with VNX storage only
◆ Combination model: DLm with both Data Domain and VNX
storage
Figure 1 on page 20 shows an overview of how the various
components of the DLm system are connected to each other.
DLm6000 architecture and models 19

Figure 1 DLm6000 overview

VTEC The VTEC is the subsystem that connects to an IBM or

IBM-compatible mainframe and provides the emulation of IBM
3480/3490/3590 tape drives. A VTEC contains the following
components:
◆ Virtual tape engine (VTE)
◆ Access control point (ACP)
◆ A pair of 24-port AT-9924TL switches (1 GbE switches)
◆ A pair of Fujitsu XG2000R 10 GbE switches
VTE Each DLm configuration can have 1—6 VTEs. The mainframe virtual
tape emulation software, Virtuent, executes on the VTEs. VTEs
emulate IBM tape drives and interface to the mainframe and direct
tape data to and from the backend storage arrays. This data is written
to the storage arrays and stored in NFS filesystems over a redundant
10G data network.
GEN-001774
Figure 2 Front view of the VTE

FICON Channel 1
FICON Channel 0
op e n
op e n
GEN-001775
Figure 3 Rear view of a VTE
ACP The ACPs are the Management Controller for the DLm6000. For high
availability reasons, the DLm6000 comes with two ACPs in a
primary-secondary configuration. This highly available configuration
requires a highly available IP address that is always associated with
the primary ACP. This ensures management access even when one of
the ACPs fail. If the primary ACP fails, the secondary ACP becomes
the primary.
Since the ACPs are the management interface for the DLm6000, they
provide a user-friendly console (DLm Console) to execute various
setup and configuration tasks. The ACPs connect to the DLm
management LAN of the DLm6000. The ACPs act as the firewall
isolating the internal DLm networks from the external LAN.
Note: You must connect both ACPs to your network.

1 2
GEN-001776
Figure 4 Front view of the ACP
B MG MT
CS
GEN-001777
Figure 5 Rear view of the ACP
DLm management The DLm6000 has an internal Gigabit Ethernet network for
network management purposes. The ACPs, VTEs, VNX, and Data Domain
systems management ports are connected to a pair of ATI9924TL
switches to protect against a single switch failure.

2
AT-9924TL-EMC
GEN-001778
Figure 6 24-port AT-9924TL switch
10G data network The data from the mainframe is transferred to the DLm storage
systems over 10 Giga bit Ethernet connections. The 10G Ethernet
network has a pair of Fujitsu XG2000R switches to protect against a
single switch failure.
FUJISU
1 3 5 7 9 11 13 15 17 19 XG2000 Status
Dump Alarm
Power
2 4 6 8 10 12 14 16 18 20
Mng-LAN Console RS-232C
GEN-001779
Figure 7 Fujitsu XG2000R switch
Backend storage DLm6000 uses either a VNX7500 or a Data Domain DD890 for storing
the data written to the virtual tapes.
The DD890 is to be used for data that deduplicates well and the
VNX7500 should be used for all other data. Both systems export NFS
filesystems and the VTEs then use these NFS filesystems to store the
data.
Deduplicating storage The Data Domain system provides DLm's deduplication feature.
DLm uses a highly optimized inline data deduplication technology
that reduces the footprint by storing only the unique data. This also
reduces power consumption and provides a significant total cost
saving. The data is streamed from the mainframe through the VTEs
to the backend Data Domain storage system. Due to the inline
implementation, only the deduplicated, unique data gets stored on
the drives.

Each Data Domain system contains:

◆ A storage controller that executes the Data Domain operating
system and supports redundant 12 Gb/s SAS connectivity to the
backend drive enclosures.
◆ Up to 12 ES30 storage shelves (each containing fifteen 2 TiB SATA
drives and providing 23.6 TiB of usable capacity).
The DD890 comes with RAID 6 configuration (12+2) and one hot
spare in each ES30 drive enclosure.
Choose deduplication backend storage for data that is stored long
term and is highly redundant.
Figure 8 DD890 Controller—Rear view
See Figure 18 on page 61 for the front view of a DD890 controller.

Although DD890 supports up to six VTEs, it has a total stream count
limit of 180 streams. This can include backup write streams, backup
read streams, directory replication at source, and directory replication
at destination. Each of these types of streams has a different limit as
listed in Table 1 on page 25.
Table 1 DD890 stream count limits
Stream type Stream count limit
Backup Write streams 180

Table 1 DD890 stream count limits
Stream type Stream count limit
Backup Read streams 50
Directory replication at source 90
Directory replication at destination 180
Irrespective of the type of streams, the total number of streams cannot

exceed 180.
VNX storage The DLm6000 can be configured with a maximum of two VNX7500
network file servers. Each VNX7500 file can have 2-8 storage
controllers called Data Movers. All VNX7500 storage systems are
configured with a standby storage controller.
Choose VNX file storage for a large volume of data that does not need
to be stored for long periods of time and is not extensively redundant
to warrant deduplication.
Mainframe channel A VTE contains mainframe channel interfaces. These channel

interfaces interfaces are two Fibre Connectivity (FICON) interfaces per VTE.
The FICON interfaces can be either single mode or multimode. A
DLm system configured with six VTEs provides 12 FICON interface
connections.
You must attach at least one mainframe channel to each VTE you
intend to configure and use. Any VTE not attached to a mainframe
channel will not be operational.
Figure 3 on page 22 shows the rear view of the VTE with the channel
interfaces to the right of center of the unit. DLm6000 supports only
FICON channels.
Each DLm VTE FICON interface has a single LC-type fiber-optic
connector. The type of cable you must use depends on the following:
◆ The type of connector on the mainframe (either LC or SC)
◆ The type of fiber-optic cable (single-mode or multi-mode)
supported by the mainframe channel
The DLm FICON interfaces are available either with single-mode or
multi-mode fiber-optic cable support. The micron rating for:
◆ Single-mode fiber-optic cable is 9/125

◆ Multi-mode fiber-optic cable is either 50/125 or 62.5/125
Connect DLm to a DLm can be connected directly to the mainframe FICON channel or it
FICON channel can be connected through a FICON switch. In either case, to properly
define a DLm V348x, or 3490, or 3480 device on a z/OS system, the
following parameters are required:
◆ TYPE must be FC.
◆ UNIT can be defined as one of the following:
• One of the virtual device types: V3480, V3481, V3482, or
V3483
• A real 3490
• A real 3480
◆ CHPID can be defined as any one of the following:
• SHARED
• DED
• REC
Note: When configuring DLm devices as device type 3490, the maximum
number of devices per control unit is 16.
Configuration for a Basic, dedicated non-shared (non-EMIF) mode

direct FICON CHPID PATH=(0A),DED,TYPE=FC
connection
CNTLUNIT CUNUMBR=EA80,PATH=(0A), +
UNITADD=((00,32)),UNIT=V3480
IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +
STADET=Y,UNIT=V3480
Note: With dedicated non-EMIF (non-shared) mode, specify LPAR=0 in the

DLm virtual device configuration program regardless of the LPAR to which it
will be connected.
Reconfigurable non-shared (non-EMIF) mode

CHPID PATH=(0A),REC,TYPE=FC
STADET=Y,UNIT=V3480

Note: With reconfigurable non-EMIF (non-shared) mode, in the DLm virtual

device configuration program, specify LPAR=0 regardless of the LPAR to
which it will be connected.
Shared (EMIF) mode

CHPID PATH=(0A),SHARED,TYPE=FC
STADET=Y,UNIT=V3480
Note: With EMIF (shared) mode, specify LPAR=n in the DLm virtual device
configuration program, where n is the LPAR to which the DLm device is
connected.
Alternate paths in shared (EMIF) mode

CHPID PATH=(0A),SHARED,TYPE=FC
CHPID PATH=(0B),SHARED,TYPE=FC
CNTLUNIT CUNUMBR=EA80,PATH=(0A,0B), +
STADET=Y,UNIT=V3480
Note: With EMIF (shared) mode, specify LPAR=n in the DLm virtual devices
configuration program, where n is the LPAR to which the DLm device is
connected.
Configuration for a FICON switch in basic mode

CHPID PATH=((22)),TYPE=FC,SWITCH=02
CNTLUNIT CUNUMBR=300,PATH=(22),LINK=(C2), +
IODEVICE ADDRESS=(300,32),CUNUMBR=(300),UNIT=V3480
`Status indicators Each FICON interface has a four-character display visible at the back
of the system adjacent to the interface connector. The display scrolls
the status of the interface. Under normal operating conditions, the
version of the emulation firmware interface is displayed.

The FICON adapter has three light-emitting diode (LED) indicators,

listed in Table 2 on page 29. These LEDs indicate the speed of the link:
1 Gbps, 2 Gbps, or 4 Gbps. When the link is up, the LED glows
steadily. It blinks if there is traffic. The numbers stamped on the
faceplate correspond to the speed.
Table 2 FICON adapter LED indicators
Yellow LED Green LED Amber LED Activity

4 Gbps 2 Gbps 1 Gbps
Off Off Off Power off
On On On Power on
Flashing Flashing Flashing Loss of synchronization
Flashing in Flashing in Flashing in Firmware error

sequence sequence sequence
On/blinking Off Off 4 Gbps link up/activity
Off On/blinking Off 2 Gbps link up/activity
Off Off On/blinking 1 Gbps link up/activity

DLm devices and capacity

Table 3 on page 30 provides details of the devices supported on DLm
and the minimum and maximum supported capacity.
Table 3 DLm6000 device details
Device Maximum Minimum
Number of maximum cabinets per system 12 2

(1 VTEC bay + backend storage bays)
Number of virtual tape engines (VTEs) 6 1
Number of access control points (ACPs) 2 2
Front-end 4G FICON channels (to the host) 12 (quatity in 2

multiples of 2)
Maximum active tape devices 1536 256
VNX7500 storage systems 2 1
DD890 storage systems 2 1
Number of storage controllers: VNX7500 8 per VNX (1 2 per VNX (1

active and 7 hot active and 1 hot
standby) standby)
Number of storage controllers: DD890 1 per DD890 1 per DD890
VNX7500 30 TiB DAEs 64 1

(2 TiB Nearline SAS drives only)
Storage (TiB) in VNX7500 DAEs 1158 57.9
DD890 30 TiB ES30 enclosures (2 TiB Nearline 12 2

SAS drives only)
Storage (TiB) in DD890 ES30 enclosures 384 (raw); 64 (raw);

285.6 (usable) 47.6 (usable)
Logical storage at 10:1 total compression (TiB) 2.856 PiB 476 TiB

Table 4 on page 31 provides details of the front-end 4G FICON

connections.
Table 4 Details of FICON connections
Component Supported number
Number of ports 1
Number of unique LPARs 256
Number of control units 16
Maximum number of paths supported per VTE 4096
DLm also supports low-volume access to enable the mainframe to

read from and write to physical tapes. Each VTE supports one
physical IBM 3592 tape drive attached by using point-to-point
connection. The Fibre Channel port provided for this connection uses
a standard multi-mode fiber-optic cable with LC-type connectors.
DLm devices and capacity 31

Tape emulation
DLm VTEs emulate the IBM tape drives to the mainframe and direct
the tape data to and from the backend storage arrays. Each VTE, once
configured, operates independently of the other VTEs in the VTEC
and can be configured with up to 256 tape drives. A DLm configured
with two VTEs can emulate up to 512 virtual tape devices, while one
with six VTEs can emulate up to 1,536 virtual tape devices at one
time.
The virtual tape emulation software:
◆ Receives and interprets channel command words (CCWs) from
the host
◆ Sends and receives the tape data records and reads and writes
corresponding disk data in response to the CCWs
◆ Presents initial, intermediate, and final status to the host
commands and asynchronous status as needed
◆ Sends and receives control information (such as sense and load
display data) to and from the host in response to the CCWs
Virtual tape drive A virtual tape drive is in one of the two basic states at any given
states time—Not Ready or Ready:
◆ In the Not Ready state, the virtual tape drive appears to the host
to be online but in an unmounted state. As on a real tape drive,
most channel commands are not accepted in this state and receive
a Unit Check status with an Intervention Required sense. While
in the Not Ready state, no disk file is opened on the disk
subsystem.
The Not Ready state is the initial state of all virtual tape drives,
and is entered whenever an Unload command is received from
the mainframe.
◆ In the Ready state, the virtual tape drive accepts all data
movement, read, and write commands from the host exactly like
the emulated tape drive. As the host reads, writes, and otherwise
positions the virtual tape, the application maintains
synchronization of the associated disk file to exactly match the
content and positioning of the virtual tape volume.

A virtual tape drive enters the Ready state when it receives a load
request from the host. When the Mount message is received, the
disk file associated with the volume specified in the Mount
message is opened, and the virtual tape drive comes Ready to the
host. The virtual tape drive remains in the Ready state, with the
associated disk file open, until an Unload command is received
from the host. On receiving an Unload command, the disk file is
closed and the virtual tape drive enters the Not Ready state.
Data formats The default file format for tape data written to the DLm disks is a
modified AWSTAPE format. This format keeps track of record
lengths as the file is being written so that the variable length records
can be read exactly as they were originally written.
Optionally, data can also be written as a plain, sequential (flat) file. In
this format, the original data record lengths, labels, and tapemarks
are lost, but any open-system application can read the data as a
sequential dataset.
Tape emulation 33
Support for physical tape drives

DLm also supports low-volume access to enable the mainframe to
read from and write to physical tapes. Each VTE contains a single
port Fibre Channel interface to support one physical tape drive that
can be attached by using point-to-point connection. The Fibre
Channel port provided uses standard multi-mode fiber-optic cable
with LC-type connectors.
Figure 3 on page 22 shows the single port HBA at the back of the
VTE.

High availability features

DLm includes failure recovery mechanisms in various parts of its
architecture to ensure optimum availability.
VTEC A VTEC with more than one VTE delivers enterprise-class

availability and scalability through a modular design based on
high-performance, highly available VTEs:
◆ VTEs have redundant power supplies, fans, and RAID-protected
internal disks. Emulated tape drives on each VTE can mount any
cartridge and any logical partition (LPAR) can access any
cartridge, delivering enterprise-class availability.
◆ There are two ACPs with a shared IP address to ensure high
availability. If the primary ACP fails, the secondary ACP takes
over as the primary and the shared IP address moves over to the
primary ACP.
◆ The configuration files are saved on the ACP to allow quick and
easy restoration of a VTE configuration if a VTE is replaced. The
files are also copied over to the secondary ACP. The redundant
copies of the configuration files protect against the single point
failure of an ACP.
◆ VTEs provide redundant data and control paths. Two 10 GbE
switches provide a redundant data path, and two 1 GbE switches
provide a redundant control path. The redundant data path
provides failover to protect against link failures, network card
failures, and switch failures.
◆ The 10 GbE ports on the VNX and Data Domain storage
controllers are bonded together in failover mode also.
VNX7500 Storage controller failover — The VNX server protects against

hardware or software failure by providing at least one standby
storage controller. A standby storage controller ensures that the VTEs
have continuous access to filesystems. When a primary storage
controller fails, the standby storage controller assumes the identity
and functionality of the failed storage controller.
Fail-Safe Network (FSN) — FSN is a high-availability networking
feature supported by the VNX storage controllers. An FSN appears as
a single link with a single Media Access Control (MAC) address and
potentially multiple IP addresses. An FSN connection may consist of
High availability features 35

a single link or multiple links. VNX defines each set of links to be a

single FSN connection. Only one link in an FSN is active at a time
although all connections making up the FSN share a single hardware
(MAC) address.
If the VNX storage controller detects that the active connection has
failed, the storage controller automatically switches to the standby
connection in the FSN, and that connection assumes the network
identity of the failed connection. The individual links in the FSN
connect to different switches so that, if the switch for the active
connection fails, the FSN fails over to a connection using a different
switch.
Control Station failover — The VNX server provides and secondary
Control Station that ensures uninterrupted file access to users when
the primary Control Station is rebooted, upgraded, or unavailable.
The Control Station software, which is used to configure and manage
the VNX server, operates independently of the file-access operations
and services provided by storage controllers.
The VNX network server uses the ConnectEMC or E-mail Home
utility to notify EMC Customer Support (or your service provider) of
the failure. After the primary Control Station is repaired or replaced
and the Control Stations are rebooted, either directly or as a result of a
powerdown and restart cycle, the first Control Station to start is
restored as the primary.
Data Domain Because the Data Domain operating system (DD OS) is designed for
data protection, the goal of its architecture is data invulnerability. Its
design includes:
◆ End-to-end verification
◆ Fault avoidance and containment
◆ Continuous fault detection and healing
◆ Filesystem recovery
End-to-end When the DD OS receives a write request from the backup software,
verification it computes a huge checksum over the data. After analyzing the data
for redundancy, it stores only the new data segments and all of the
checksums. After the backup is complete and all the data has been
synchronized to disk, the DD OS verifies that it can read the entire file
from the disk platter through the Data Domain filesystem, and that
the checksums of the data that is read back match the checksums
written. This ensures that the data on the disks is readable and

correct, can be recovered from every level of the system, and that the
filesystem metadata structures used to find the data are also readable
and correct.
Fault avoidance and The biggest risk to filesystem integrity is filesystem software errors
containment that occur when writing new data. New data can accidentally write
on existing data, and new updates to filesystem metadata can mangle
existing structures. Data Domain systems are equipped with a
specialized log-structured filesystem that has four important benefits:
◆ New data never overwrites good data
Unlike a traditional filesystem, which will often overwrite blocks
when data changes, Data Domain systems write only to new
blocks. This isolates any incorrect overwrite (for example, a
software defect issue) to only the newest backup data. Older
versions remain safe.
◆ Fewer complex data structures
The Data Domain filesystem was built to protect data in backup
applications, where the workload is primarily sequential writes of
new data. Because the application is simpler, fewer data
structures are required to support it. As long as the system can
keep track of the head of the log, new writes will not touch old
data. This design simplicity greatly reduces the chances of
software errors that could lead to data corruption.
◆ NVRAM for fast, safe restart
The system includes a non-volatile RAM write buffer into which
it puts all data not yet safely on disk. The filesystem leverages the
security of this write buffer to implement fast and safe restart
capability. The filesystem includes many internal logic and data
structure integrity checks. If any problem is found by one of these
checks, the filesystem restarts. The checks and restarts provide
early detection and recovery from the kinds of bugs that can
corrupt data.
As it restarts, the Data Domain filesystem verifies the integrity of
the data in the NVRAM buffer before applying it to the filesystem
and so ensures that no data is lost due to the restart. Data Domain
systems never update just one block in a stripe. Following the
no-overwrite policy, all new writes go to new RAID stripes and
those new RAID stripes are written in their entirety. The
verification after write ensures that the new stripe is consistent.
New writes do not put existing backups at risk.

Continuous fault As a basis of continuous fault detection and healing, the Data
detection and healing Domain system uses RAID 6 protection to protect against double disk
faults.
On-the-fly error detection and correction

To ensure that all data returned during a restore is correct, the Data
Domain filesystem stores its on-disk data structures in formatted data
blocks that are self-identifying and verified by a strong checksum. On
every read from disk, the system first verifies that the block read from
the disk is the block expected. It then uses the checksum to verify the
integrity of the data. If any issue is found, the system uses RAID 6
and its extra level of redundancy to correct the data error. Because the
RAID stripes are never partially updated, their consistency is ensured
and thus the ability to heal an error when it is discovered.
Scrub to ensure data does not go bad

Data Domain systems verify the integrity of all data weekly in an
ongoing background process. This scrub process finds and repairs
grown defects on the disk before they can become a problem.
The Data Domain storage array includes various recovery
mechanisms to ensure optimal availability on the storage controller,
network, and DD890 levels. The Data Domain DD OS Administration
Guide contains more information about the various DD890 recovery
features.
Filesystem recovey Data Domain systems include features for reconstructing lost or
corrupted filesystem metadata, as well as filesystem check tools that
can quickly bring an ailing system safely back online.
Self-describing data format to ensure metadata recovery

Metadata structures, such as indexes that accelerate access, are
rebuildable from the data on disk. All data is stored along with
metadata that describes it. If a metadata structure is somehow
corrupted, there are two levels of recovery. First, a snapshot of the
filesystem metadata is taken every several hours, creating
point-in-time copy for the recovery process to use. Second, the data
can be scanned on disk and the metadata structure can be rebuilt.
These features enable recovery even if with a worst-case corruption
of the filesystem or its metadata.

Redundant 10 Gb Ethernet data path

The Data Domain DD890 communicates with the VTE over DLm's
internal 10 Gb Ethernet (10 GbE) network. The 10 Gb card on the
DD890 is configured in failover mode to protect against single link
and switch failures.
Redundant 1 Gb Ethernet connectivity for management

The Data Domain DD890 in the DLm uses two GbE ports, Eth0 and
Eth2, to connect to the managment network in the DLm. These ports
are configured as a failover pair to protect against single link, switch,
and NIC failures.
Redundant 1 GbE ports for replication

The Data Domain DD890 includes two GbE ports that support
replication. These ports can be configured as a Failover pair or in
Aggregate Mode (LACP) to protect against single link or switch
failures.
Redundant backend/drive connectivity

Each Data Domain DD890 in the DLm comes with two quad-ported
SAS cards. Each ES30 drive enclosure also has two dual-ported SAS
cards that connect to the controller or the adjacent ES30 enclosure in
the chain. The eight SAS connections from the controller to the ES30
enclosures are configured as two failover pairs, distributed across the
two cards to protect against card failures. The failover pair is
active-passive.

Features and benefits

DLm offers many benefits over traditional tape including:
◆ Faster processing of tape mount requests (translating into shorter
overall job step processing)
◆ No requirement for physical tapes (reducing the cost, storage, and
potential for loss of tapes and data)
◆ Support for data sharing across multiple VTEs (creating a level of
data availability not found in previous mainframe virtual tape
systems)
◆ Support for low volume access of external physical tapes that
allow the mainframe to write to and read physical tapes
◆ Data integrity maintained by storing the tape data on internal
storage arrays and using RAID 6 technology to protect the data
from physical disk drive failures
◆ Built-in monitoring and reporting technologies, such as Simple
Network Management Protocol (SNMP) and ConnectEMC, that
raise alerts when attention is needed within the DLm
environment
◆ Support for replication of tape data between DLm systems and
up to two local or remote DLm systems
◆ No single point of failure of mainframe tape data if the DLm
system has more than one VTE
◆ Support for two erase policies for space reclamation (in DLm
release 2.3 and later):
• Space: This is the default policy. When a filesystem reaches a
specified percentage of space usage (Recovery Percent general
parameter), DLm begins erasing the oldest scratch tapes in
that filesystem until the amount specified in the Recovery
Amount parameter has been recovered.
• Time-to-live: This policy specifies a period of time that
scratched tapes will be retained after being scratched, before
being automatically erased. Once the period expires, the tapes
will automatically be erased regardless of current space
utilization. The time-to-live erase options are: Days and
Hours.

Note: If the VTE has tape libraries with VOLSER that reside on the Data
Domain DD890, the erase policy must be configured to one of the
Time-to-live options.
◆ Support for data deduplication:

• Support for the best inline data deduplication technology
available in the market that reduces the footprint due to
deduplication and reduces power consumption
• Significant cost savings for replication deployments as only
the unique data after deduplication is replicated
◆ Support for EMC Secure Remote Support (ESRS) that provides
secure, fast, and proactive remote support for maximum
information availability. Contact EMC Customer Support to
configure ESRS.
Features and benefits 41


2
DLm Operations
This chapter explains the routine DLm operations:

◆ Management access to DLm............................................................. 44
◆ Access a VTE....................................................................................... 54
◆ Power up DLm ................................................................................... 57
◆ Power down DLm.............................................................................. 67
◆ Start and stop tape devices ............................................................... 74
◆ Initialize scratch volumes ................................................................. 76
◆ Support access to DLm...................................................................... 78
DLm Operations 43
DLm Operations
Management access to DLm

The ACP provides management and support access to the DLm
system. ACPs also connect to the management LAN of the DLm
system. They act as the gateway, providing access to the VTEs, VNX
Control Stations, and Data Domain systems. The ACPs also function
as the firewall isolating the internal DLm networks from your LAN.
The ACP provides a user-friendly GUI, the DLm Console, to execute
various setup and configuration tasks.
Gather connection To connect to the DLm system, you will need some IP addresses and
data passwords.
You need three IP addresses for the ACPs: one for ACP1, one for
ACP2, and a third highly available IP address which is assigned to
the primary ACP. Use the highly available IP address to access the
DLm Console.
Table 5 on page 44 lists the details that you will need before you
access the DLm system.
Table 5 DLm system access details
Item Default Actual
DLm Console
HA IP address
Username dlmadmin
Password password (first login)
Note: The system prompts

you to change the
password at the initial
login.
ACP1
IP address
Username dlmadmin
Password password

DLm Operations
Table 5 DLm system access details
Item Default Actual
ACP2
IP address
Username dlmadmin
Password password
Access the DLm The DLm Console is a web-based console that is used to configure
Console and monitor the DLm system. It is the management interface to the
DLm system.
Connect to the DLm To connect to the DLm Console:

Console
Note: This procedure assumes that you have access to and are connected to
the Data Center LAN to which the ACP is connected to also.
1. Open a web browser.

2. Type the ACP address as follows:
https://ip_address
where ip_address is the address of the ACP on the customer LAN.
For example: https://10.242.29.26
The login screen opens as shown in Figure 9 on page 46.
Management access to DLm 45

DLm Operations
Figure 9 DLm Console login page
3. Type the username and password. For a first-time login, enter the
following user and password:
• User: dlmadmin
• Password: password
The DLm Console opens as shown in Figure 10 on page 47. At
first login, DLm prompts you to change the DLm Console
password.

DLm Operations
Figure 10 DLm Console
Exit DLm Console To exit the DLm Console, click Logout on the DLm Console menu
bar.
Set date and time The DLm system time is displayed in the status line at the bottom of
the VT console. If you need to adjust the system date or time you may
do so from the Time tab on the DLm Console:
1. Access the DLm Console as described in “Connect to the DLm
Console” on page 45.
2. Click External.
3. Click the Time tab if it is not already displayed.

DLm Operations
Figure 11 DLm date and time
4. Use one of these two methods to set the date and time on a VTE:
• Configure the system to use a Network Time Protocol (NTP)
server.
Note: EMC strongly recommends that you use an NTP server.
If the ATC is connected to the corporate network and one or

more NTP servers are accessible, configure the controller to
get date and time from an NTP server.
Enter either the network name or IP address of up to four NTP
servers. When you make this configuration active by installing
it, the ACPs in the configuration attempt to query the NTP
servers from 1 to 4 until they successfully get the date and
time.
Note: If you use a network name to identify an NTP server, you will
need to configure a Domain Name Server (DNS) as part of the
network configuration.
• Manually set a specific date and time.

DLm Operations
To manually set the date and time, adjust the date and time in
the Current date and time fields and click Set.
The date and time is set in all the VTEs in the system.
User administration By default, DLm ships with two default user IDs:
◆ dlmadmin
◆ dlmuser
The default password for these two usernames is password.
The dlmadmin user has full administrator rights and can create new
configurations or modify the existing configurations. This user can
monitor and control the operation of the VTE. The dlmadmin user
can create new users with the same rights as dlmuser; dlmadmin
cannot create another user with administrative rights.
The dlmuser user can view the configuration and check the status of
the VTEs but does not have the authority to modify configurations or
operate the VTEs.
From the Authentication tab of the DLm Console, the dlmadmin
user can add, delete, or modify usernames recognized by the system:
2. Click External.
3. Click the Authentication tab.

DLm Operations
Figure 12 User ID creation
4. Select the authentication type:

• Native
“Native” on page 50 provides instructions to add, modify, or
delete users of Native authentication type.
• LDAP (including Active Directory)
“LDAP” on page 51 provides instructions to add, modify, or
delete users of LDAP authentication type.
5. Under Automatic logout, in Logout perod (minutes), enter the
number of minutes after which the user will automatically be
logged out if the session is inactive. Leave this field blank to
disable automatic logout.
6. Click the Apply authentication changes link to apply the
changes.
Native Native user administration stores the usernames and passwords on

the VTE and is the default type.
◆ To modify a user, modify the content of the Name, Password, or
Readonly? fields.

DLm Operations
◆ To add a new user:

a. Click Add Next.
b. Enter the username under Name.
c. Enter the password for that user under Password.
d. Select the Readonly? option if the user should not make
changes to the configuration.
◆ To delete a user ID, click the X button corresponding to that user.
! CAUTION
Be careful not to delete all usernames with full administrator
privileges. If there are no administrator users you will not be
able to modify or operate the system.
LDAP When you configure DLm user authentication to use an external

Lightweight Directory Access Protocol (LDAP), the usernames and
passwords will no longer be maintained on the ACP. When a user
attempts to log in to DLm Console, DLm sends a message to the
LDAP server. The LDAP server searches for the use name and
password that has been entered and informs DLm if the user is found
and the password is correct. DLm then grants access to the user.
! CAUTION
Do not attempt to change the authentication type from Native to
LDAP unless your DLm system is attached to your corporate
network and you already have the appropriate directory server
installed and running on the network. Failure to successfully
attach to an external directory server could result in not being able
to log in to DLm.

DLm Operations
Figure 13 LDAP user authentication
◆ For administrative access, enter details under LDAP parameters

for administrative access:
• LDAP server: Enter the hostname or IP address of the LDAP
server.
• Base DN: Enter the Distinguished Name (DN) of the entry at
which the server must start the search for authentication
credentials.
• Filter: Criteria to use when selecting elements for
authentication credentials. The format is (cn=%s) where the
login name is substituted for %s.
• LDAP server bind credentials (optional):
– Bind DN: The DN to bind the server with

DLm Operations
– Bind password: The password for the Bind DN

◆ For readonly access, enter details under LDAP parameters for
readonly access:
• LDAP server: Enter the hostname or IP address of the LDAP
server.
• Base DN: Enter the Distinguished Name (DN) of the entry at
which the server must start the search for authentication
credentials. For example, dc=emc or dc=com.
• Filter: The criteria to be used in selecting the elements to be
used in authentication criteria. For example, (cn=%s) indicates
that the Common Name (cn) field should be compared against
the name entered in the User field of the login screen. (The
login name is substituted for %s.)
• LDAP server bind credentials (optional):
– Bind DN: The DN to bind the server with
– Bind password: The password for the Bind DN

DLm Operations
Access a VTE
You can access the VTE through the DLm Console.
The System status tab of the System menu opens by default.
The console displays icons for each configured VTE. From the
bottom up, the VTEs in your DLm cabinet are named VTE1,
VTE2, VTE3, and so on. Only the icons matching the VTEs
installed on DLm are displayed on the console.
2. In the Console column, double-click the icon corresponding
to the VTE you want to access.
Figure 14 VT console
The VT console for that VTE opens.

DLm Operations
The title bar displays the name of the VTE. The blue bar at the bottom
of the screen displays the status of the virtual tape application. The
informational, warning, and error messages from the VT application
scroll on the console window.
VT console A VT console does not need to be open for the VTE to be working.
You can open a specific VT console when you configure that VTE or
when you want to monitor the status of tape operations on that VTE.
You can have all VT consoles open simultaneously. All VTEs continue
to operate normally regardless of which console is open.
The VT console is divided into three sections:
◆ The larger, top section displays log messages as they are issued
from the VT application. On startup, the VT console displays the
messages in the log (up to the last 100,000 bytes) since the last
startup of the VT console.
The following navigation keys (or commands) can be used to
scroll through the messages:
• Home—Move to the top
• End—Move to the bottom
• PgUp—Move up one screen
• PgDn—Move down one screen
◆ The smaller, lower section of the VT console is blue and always
shows the current status of the VT application on this VTE. When
the VT application is not active, the VT status is Not running.
When the VT application is active, the VT status on the VT
console is Running. Use the START VT and STOP VT commands
to start and stop the VT applications, respectively. “Start and stop
tape devices” on page 74 provides information.
The DLm system time is displayed in the status line at the bottom
of the VT console.
◆ Below the VT Status line is a command line where you may enter
and edit VT commands.
The following navigation keys can be used on the command line:
• Up Arrow or Ctrl+P—Previous command in history
• Down Arrow or Ctrl+N—Next command in history
• Left Arrow—Move 1 character to the left in the command line
Access a VTE 55
DLm Operations
• Right Arrow or Ctrl+F—Move 1 character to the right in the

command line
• Ctrl+A—Move to the beginning of the command line
• Del or Ctrl+D—Delete one character
• Ctrl+E—Move to the end of the line
• Backspace or Ctrl+H—Backward delete character
• Ctrl+K—Erase to the end of the line
• Ctrl+T—Transpose characters
• Ctrl+U—Discard the line
• Ctrl+W—Word rubout
To close the VT console window, click the close window button in the
top right corner of the screen. Closing the console does not affect the
operation of the virtual tape application in any way.
VTE reboot To reboot a VTE:
Note: Vary all the devices on the VTE offline to the mainframe before you
reboot the VTE.

The System status tab of the System menu opens by default.
2. In the Reboot machine column, click Reboot against to the VTE
you want to reboot.

DLm Operations
Power up DLm
Note: You must coordinate planned powerdown and powerup events with
EMC Customer Support.
Powering up a DLm system is a multistep process. Power up the

following in this order:
1. Each VNX7500 Network Server (including the EMC CLARiiON
storage array)
2. Each DD890
3. Each ACP
4. Each VTE
Note: The Ethernet switches are powered up as soon as the cabinets are
powered up. Wait at least 10 minutes for the storage to power up before
powering up the ACPs and the VTEs.
VNX power-up 1. Ensure that the switches for SPS A and SPS B are turned OFF.
2. Verify that the cabinet circuit breakers are in the OFF position.
[1 in Figure 17 on page 60]
3. Connect the power cables as follows:
a. The standby power supply (SPS) A to power distribution
panel (PDU A). [2 in Figure 17 on page 60]
b. The SPS A to storage processors A & B (Ensure that the
retention bails are in place.) [3 in Figure 17 on page 60]
c. The DAE 0 to SPS A & SPS B. [4 in Figure 17 on page 60]
4. Turn on the circuit breakers using the Master switches.
5. Turn the SPS switches ON.
This powers up the storage subsystem of the VNX7500. This takes
about 10-12 minutes.
Power up DLm 57
DLm Operations
SPS Power SPS Power

Switch B Switch A
CL4847
Figure 15 Rear of the SPS
6. Check the following LEDS on the front and rear of the VNX7500:
• Amber warning LEDs flash during the power-on self-test
(POST) and then go off.
• The front fault LED and the SPS recharge LEDs commonly
stay on for several minutes while the SPSs are charging.
7. Ensure that the storage array is up and running.
The storage processors are immediately above the SPS. The
physical indication that the storage array is up and running:
• The Power LED on the storage processors is green.
• The Fault LED on the storage processor is not lit amber.
• DAE 0 status is green.
• The first four drives in the DAE are green.
Power Power Power Power

cooling cooling cooling cooling
Front
PS A0 PS A1 PS B0 PS B1
CPU A CPU B
AC AC AC AC
A B
SP CPU power SP enclosure Power SP CPU power

power enclosure
fault CL4848
Figure 16 Storage processor LEDs

DLm Operations
8. Connect DAE 1- 8 to PDUs A & B. [11 - 18 in Figure 17 on page 60]

9. Power up the DAEs in the DAE-only racks. This may require
switching on the power at the master switches of these DAE-only
racks. It may take some time for all the DAEs to be powered up
and available.
The indication that the DAEs have been detected:
• The green seven-segment display indicates the backend SAS
bus the DAE is on.
• The blue seven-segment display indicates the DAE
number/ID in a particular SAS chain.
• No amber LEDs are lit on the drives.
10. Connect each side of the Data Mover enclosures to the PDU
closest to it. [5 - 8 in Figure 17 on page 60]
The Data Movers now power up. The LED on the front of the
Data Movers are lit when the Data Movers have powered up.
Wait for 4-5 minutes, this ensures that the Data Movers are ready.
11. Connect Control Station 0 (CS 0) to PDU B. [9 in Figure 17 on
page 60]
Check the power LED on the front of the Control Station 0. If that
LED indicates that CS 0 has not started to power up, turn on the
Control Station by pressing the power button on the front. Wait 5
minutes to make sure that CS 0 is powered up before continuing.
12. Connect the Control Station (CS 1) to PDU A.
Check the power LED on the front of the Control Station 1. If that
LED indicates that CS 1 has not started to power up, turn on the
Control Station by pressing the power button on the front. Wait 5
minutes to make sure that CS 1 is powered up.
Power up DLm 59
DLm Operations
Figure 17 VNX7500 cabinet
! CAUTION
The DLm bays and power systems are designed to support DLm
equipment only. EMC does not support any other components in
these bays, and recommends that you do not install any additional
equipment in the DLm bays.

DLm Operations
DD890 power-up The ES30 shelves of the DD890 must be powered up before powering
up the DD890 controller. Make sure the SAS cabling to the ES30
drives are connected and plugged in before powering the systems
ON.
1. Ensure that the master switch on the DD890 rack is in the OFF
position.
2. Connect power cables to both the power receptacles of the ES30
shelves and make sure the retention clips at both ends are
engaged.
3. Power on the expansion shelves. The ES30 shelves take about 3-4
minutes to power ON. (Make sure you power on the ES30 shelves
before powering on the DD890 controller.)
4. Connect both power cables to the DD890 controller. Ensure that
the retention clips are engaged at the PDUs and the cable restraint
tie is connected at the controller.
If the DD890 controller does not automatically power on, push
the power button on the front of the controller.
! IMPORTANT
Wait for about 10-15 minutes for the DD890 System to power
up.
Figure 18 DD890 controller - front view
Power up DLm 61
DLm Operations
The system fault LED on the controller should stay green if there
are no faults detected. Table 6 on page 62 describes the status of
this LED.
Table 6 DD890 controller LEDs
Display Description
Steady Green Normal operation
Blinking Green Startup
Steady Amber Critical fault. Shut down system for service
Blinking Amber Non-fatal fault. Investigate; service the system
ACP power-up To power up and start the ACP:

1. Before powering up the ACP, make sure you are connected to the
mainframe and the storage systems.
Note: Ensure that the storage systems are powered up.
2. Press the power button located in the front of the ACP: button B
in Figure 19 on page 62.
You might hear the fans start and then slow down to adjust the
system temperature. Shortly thereafter, the system begins to boot
and the hard drive activity LED blinks.
A B C D E F G CNS-000979
Figure 19 ACP indicators and controls

DLm Operations
Figure 19 on page 62 shows these controls and indicators on the front

of an ACP.
A USB 2.0 port Allows you to attach a USB component to the front of the
ACP.
B Power button Toggles the system power on/off.
C System Status LED • Continuous green light indicates the system is

operating normally.
• Blinking green light indicates the system is operating in
a degraded condition.
• Blinking Amber light indicates a non-fatal error has
occurred. The system is likely to fail if corrective action
is not taken.
• Continuous amber light indicates the system is in a
critical or non-recoverable condition. The system has
failed.
• No light indicates POST is running or the system is off.
D Power LED • Continuous green light indicates the system has power
applied to it.
• No light indicates the power is off.
E Hard Disk Drive • A blinking green light indicates disk activity.

Activity LED • No light indicates no activity.
F LAN 1 Activity LED • Blinking green light indicates network activity.

• Continuous green light indicates a link between the
system and the network to which it is connected.
G LAN 2 Activity LED • Blinking green light indicates network activity.

• Continuous green light indicates a link between the
VTE power-up To power up a VTE:

1. Make sure that the ACPs are powered up before powering up the
VTEs.
2. Press the Power/sleep button on the front of the VTE: button C in
Figure 20 on page 64.
Note: You can power up the VTEs in any order as they operate
independently of each other.
Power up DLm 63
DLm Operations
You should hear the fans start and then slow down as they adjust for
system temperature. Shortly after that, the VTE's disk activity LED
begins blinking indicating startup of the VTE.
AB C D E F G
Disk 0 Disk 1
L K J
GEN-000718
Figure 20 VTE indicators and controls
Figure 20 on page 64 shows these controls and indicators on the front

of a VTE.
A LAN 2 activity LED • Blinking green light indicates network activity.

(eth0) • Continuous green light indicates a link between the
B LAN 1 activity LED • Blinking green light indicates network activity.

(eth1) • Continuous green light indicates a link between the
C Power/sleep Button Toggles the system power on/off.
Note: DO NOT press the Power/Sleep button while the VTE

is online to the host. Follow the shutdown procedures in
“Power down DLm” on page 67 for shutting down a VTE
before pressing the Power/Sleep button on any active VTE.

DLm Operations
D Power/sleep LED • Continuous green indicates the system is powered on.

• Blinking green indicates the system is sleeping.
• No light indicates the system does not have power applied
to it.
E Disk activity LED • A continuous light indicates drive ready status.

• The light blinks off to indicate disk activity.
F System status LED • Continuous green indicates the system is operating

normally.
• Blinking green indicates the system is operating in a
degraded condition.
• Continuous amber indicated the system is in a critical or
non-recoverable condition.
G System The ID LEDs allow you to easily identify the VTE you are
identification (ID) working on in a rack:
LED • A blue light that lights when the ID Button has been
pressed.
• A second blue ID LED on the back of the unit also lights
up when the ID Button has been pressed.
H ID button Toggles the ID LEDs that enable you to identify the VTE you
are working on in a rack.
I Reset button Reboots and initializes the system.
Note: DO NOT press the Reset button while the VTE is

online to the host. Follow the shutdown procedures in “Power
down DLm” on page 67 for shutting down a VTE before
pressing the Reset button on any active VTE.
J USB Connector Allows you to attach a USB component to the front of the
ACP.
K NMI button Pressing this recessed button with a paper clip or pin issues
a non-maskable interrupt and puts the system into a halt
state for diagnostic purposes.
L Video Connector
Note: All LEDs are visible through the front bezel. However, you must
remove the bezel to press the NMI, Power, Reset, or ID buttons.
Normal startup of a VTE takes 5 - 10 minutes. After the VTE starts its
network services, you will be able to access the VTE through the DLm
Console.
Power up DLm 65
DLm Operations
Note: If the entire VTEC bay is in the powered down state, some of the LED
panel indicators may light when power is applied. This is only an indication
that the units have power available, it is not an indication that the ACP or
VTEs are started. You must press the Power button on the ACPs and each
VTE to actually start them when appropriate.

DLm Operations
Power down DLm

Note: You must coordinate planned powerdown and powerup events with
EMC Customer Support.
Powering down DLm, like powering it up, is a multi-step process.

This process includes procedures to suspend processing and then
remove power to accomplish a full system shutdown. Power down
the following in this order:
1. Each VTE (You must vary off the tape devices from the host first.)
2. The storage systems:
a. Data Domain DD890 systems
b. VNX7500s
Note: The powerdown procedures are different for Data Domain DD890
and VNX7500.
3. The ACPs
a. The secondary ACP
b. The primary ACP
Note: The powerdown process takes up to 30 minutes after the tape drives
are varied offline.
When you use the poweroff or reboot command to shut down or

reboot an ACP, only that ACP is affected. All VTEs continue to
operate uninterrupted.
When you use the poweroff or reboot command to shut down or
reboot any DLm VTE, only that VTE is affected. All other VTEs
continue to operate uninterrupted.
Power down DLm 67

DLm Operations
Power down the VTE Always use the poweroff command to shut down a VTE in an
orderly manner. If you simply power off the VTE by pressing the
Power or Reset buttons, unpredictable errors occur on the host for
any active connections, possibly resulting in data loss. Before using
this command, you must stop all host programs using the VTE, and
vary off the tape devices from the host.
! CAUTION
Do not power off while the VTE is online to the host. Follow the
shutdown procedure before pressing the Power button.
To power down a VTE:

1. Vary off all the tape drives from the mainframe.
Note: Vary the tape drives offline from every LPAR and wait for it to go
offline. If a job is accessing the drive at that point, the drive does not go
offline until the job releases the drive. Depending on the usage, this could
take more than an hour.
2. Access the ACP:

a. Start an SSH client like PuTTY.
b. Select the SSH connection type.
c. Type the IP address of the primary ACP in the hostname (or IP
address) field. The The primary ACP is always assigned the
highly available IP (HA IP) address and can reside on either
ACP1 or ACP2.
d. Click Open.
3. Log in to the ACP as root. The password is Just4Eng&Use.
4. On the ACP console, enter this command to power down the
VTEs:
ssh -q vte<n> poweroff
where <n> is the VTE number (1, 2, 3, 4, 5, or 6).

The VTE you specified in the poweroff command enters the
shutdown state.

DLm Operations
Note: The virtual tape application automatically restarts the next time
you start the system.
After you execute the poweroff command, the VTE powers down.
Pressing the Power button after a poweroff command will turn the
VTE on again.
Power down DD890 If you have both VNX7500 and DD890, power down DD890 before
you power down VNX7500.
You can power down the DD890 system from the ACP by executing a
CLI command.
To shut down the power to the Data Domain system:
1. Log in as an administrative user and type this command:
# ssh -l sysadmin 192.168.100.110 system poweroff
2. When the system prompts for confirmation, type yes and press
Enter.
The command automatically performs an orderly shutdown of
DD OS processes.
! CAUTION
Do not use the chassis power switch to power off the system.
Use the system poweroff command instead.
The DD890 controller powers down. This may take a few

minutes. The LED on the power switch on the DD890 controller is
OFF and no longer lit. The green LEDs on the power supply at the
back of the rack are blinking.
3. After powering down the controller, power down the ES30
shelves using the master power switches at the back of DD890
rack. This powers down the DD890 cabinet.
Power down DLm 69

DLm Operations
Power down If you have both VNX7500 and DD890, power down DD890 before
VNX7500 you power down VNX7500.
Halt the VNX server
! CAUTION
A planned powerdown of the VNX server and integrated storage
array requires access to the VNX Control Station. Call EMC
Customer Support for assistance.
To perform a planned powerdown, you must be within close

proximity to the VNX server.
1. Before you power down the VNX7500 server, vary off all tape
drives and power down all VTEs to stop all I/O activity.
2. Log in to the primary ACP.
a. Start an SSH client, such as PuTTY.
address) field. The primary ACP is always assigned the
ACP1 or ACP2.
d. Click Open.
e. Log in to the ACP as root. The password is Just4Eng&Use.
3. If you want to verify the VNX system's health, type:
ssh -q 192.168.100.200 /nas/bin/nas_checkup
The checkup command reports back on the state of the Control

Station, storage controllers, and storage system.
Note: This healthcheck ensures that there are no major errors in the
system that would prevent the system from being turned on during the
power up process.
This step will take several minutes.

4. To halt the VNX server (Control Stations and storage controllers),
type:
ssh -q 192.168.100.200 /nasmcd/sbin/nas_halt now

DLm Operations
An output similar to this one appears:

[root@celerra156-cs0 root]# nas_halt now
******************** WARNING! ********************
You are about to HALT this VNX including all of its
Control Stations and Data Movers. DATA will be
UNAVAILABLE when the system is halted. Note that this
command does *not* halt the storage array.
ARE YOU SURE YOU WANT TO CONTINUE? [ yes or no ] : yes
5. Type yes and press Enter.

It can take as long as 20 minutes to halt the server, depending on
the configuration of the VNX system. Wait until the command
completes before continuing.
Verify Control Station To verify that the server has been shut down:
powerdown
1. Reboot the Control Station by pressing the power button in the
front of the Control Station. To reach the power button on the
Control Station, you might have to remove the front bezel.
2. Wait for 5 minutes, and then verify that the system is powered off.
3. Verify that the Data Movers are shut down using this command:
# ssh -q 192.168.100.200 /nasmcd/sbin/getreason
This is a sample output for a 6-Data Mover configuration:

6 - slot_0 primary control station
slot_1 secondary control station powered off
- slot_2 powered off
After ensuring that the Data Movers are shut down, you can now
proceed to powering down the Control station.
4. From the prompt, issue the following command to power down
the Control Station:
ssh -q 192.168.100.200 poweroff
You can now proceed to powering down the storage controller and
the drives.
Power down DLm 71

DLm Operations
Power down the To shut down the storage controllers (SPE and boot DAE), use only
storage controllers the power switches on the SPS.
! CAUTION
Failure to follow this procedure can result in the loss of data and
extended periods of data unavailability while the array is returned
to normal functionality.
SPE chassis and OS-Boot chassis DAEs are plugged into the SPS
units. From the rear of the cabinet, the left power supply of each
chassis (SPE and OS-boot) is plugged into the left SPS and the right
power supplies are plugged into the right SPS. To power down the
storage array:
1. Vary off all tape drives, power down all VTEs, and halt the VNX
server to stop all I/O activity.
2. Wait approximately five minutes to allow the write cache to finish
writing to the storage system.
3. Use the SPS power switches to power off the array. Turn off (0
position) the power switch on the standby power supplies (SPS).
Figure 15 on page 58 shows the SPS power switches. Make sure
the SPS power indicators are off before continuing.
WARNING
Never turn off the power directly to the SPE chassis or the
OS-boot chassis by using any switches on the power supplies.
Never unplug any of the AC cables going to the SPE or OS-boot
chassis to disconnect power.
4. Wait for two minutes to allow the storage system to write its
cache to disk and to power off. Then, disconnect the power cables
that run from the SPSs to the DAE.
5. If there are multiple DAEs present, disconnect the power cable
from each DAE to the PDU. This powers down the DAEs.
6. Disconnect the power cables for each Data Mover and Control
Station from the PDUs.
7. Make sure that the LEDs on all the management switches are off.
Once they are off, the server is completely powered down.

DLm Operations
Power down the You can power down and reboot the ACP without affecting the
ACP operation of the VTE.
To power down the ACP:
1. Access the ACP:
a. Start an SSH client, such as PuTTY.
address) field. The primary ACP is always assigned the
ACP1 or ACP2.
d. Click Open.
e. Log in to the ACP as root. The password is Just4Eng&Use.
2. Verify if the ACP that you are logged into is the primary ACP. At
the prompt, enter:
ha_status
The following is a sample output:

acp1:~ # ha_status
HEARTBEAT v2.1.4-0.15.3, host acp1, Primary/active,

link up, resource all
HEARTBEAT v2.1.4-0.15.3, host acp2, Secondary/active,
link up, resource none
INFO: High Availability Services - OK
Note: If the primary ACP is powered down, the secondary ACP will take
over as the primary ACP.
3. Power down the secondary ACP before you power down the
primary ACP.
a. To power down the secondary ACP:
ssh -q acp<n> poweroff
where <n> is 1 or 2.
b. After you have powered down the secondary ACP, power
down the primary ACP:
poweroff
Power down DLm 73

DLm Operations
Start and stop tape devices

To start or stop the virtual tape devices you must start or stop the VT
application. Control of the VT application is through the VTE console.
The commands for starting and/or stopping tape emulation on a
controller (node) are:
◆ STARTVT to start the VT application and activate devices in the
installed configuration file.
◆ STOPVT to stop the VT application. Once the application stops,
the channel links are disabled and all virtual drives cease to
respond to the host until the application restarts. Any I/O from
the host while the application is terminated will receive an I/O
error (device not operational). For this reason, you should wait
for all host applications using devices to finish, and the virtual
tape drives should be varied offline from the host operating
system before stopping the vt application.
STOPVT will not terminate the application if any virtual drives
currently have volumes loaded.
◆ STOPVT! to terminate the application while volumes are loaded.
Any virtual tapes currently loaded will be immediately unloaded
without any further processing.
Note: This may result in an incomplete output tape volume if the host
has not yet completed writing and properly closing the tape. For this
reason, the STOPVT! command should only be used in an emergency
situation where VTE must be brought down immediately. Any virtual
tape volumes currently being written should be considered invalid.
When the VT application is active, the VTE console shows the VT

status as "Running" and informational, warning, and error messages
from the VT application scroll on the console.
To start or stop the virtual tape devices:
1. Access the VTE console as described in “Access a VTE” on
page 54.
2. In the VTE console, type the appropriate command. For example,
to start the VT application, type:
STARTVT

DLm Operations
The blue bar at the bottom of the VTE console displays the changed
status of the VT application.
Figure 21 VT console with VT application
3. Type exit and press Enter to close the console window.
Start and stop tape devices 75

DLm Operations
Initialize scratch volumes

Before any of the VTEs can mount a virtual tape volume and present
it to the mainframe host, you must initialize the tape volumes that
you use. Execute at least one INITIALIZE command on a VTE
console when you start any tape drives on DLm. Otherwise, no
scratch tapes will be available for use within the DLm system.
A DLm tape library is made up of one or more filesystems and may
be sub-divided into storage classes. Since VTEs normally share tape
volumes within a tape library, you only need to initialize tape
volumes into each storage class to make them available to all VTEs
sharing the library. If there are no scratch volumes in a storage class,
DLm will not be able to satisfy a mount request for a scratch within
that storage class and the mount will remain pending.
If you have not defined storage classes (other than the default class 0),
you will only need to initialize a single range of tape volumes to the
library. But if you have defined multiple storage classes then you
must initialize a range of VOLSERs for each class you have defined.
The command to initialize tapes is:
INITIALIZE VOL=volser DEV=devname COUNT=count CLASS=n DIR=dirname
where:
◆ volser is the starting serial number to initialize.
◆ devname is the device name (address) of any tape drive pointing to
the tape library.
◆ count is the number of serial numbers to initialize.
◆ n is the class these volumes are to be added to.
◆ dirname is a specific directory the volumes should be placed in.
DIR is an optional parameter. DIR is not a requirement . If DIR is not
specified, INITIALIZE places the volumes into the first filesystem it
finds within the storage class. During processing, scratch tapes will
be automatically moved as needed from one directory (filesystem) to
another in the same storage class. However, if you wish to spread
scratch volumes across multiple filesystems within a class you may
use the DIR parameter to direct a range of tapes to a specific
filesystem. CLASS is a required parameter.

DLm Operations
Assuming device E980 is a configured device pointing to your tape

library then the command to initialize 500 serial numbers to the
storage class 0 beginning with VOLSER 000000 would be:
INITIALIZE VOL=000000 DEV=E980 COUNT=500 CLASS=0
This would result with volumes ranging from 000000 to 000499 being
created in the first filesystem in class 0.
If your library has two storage classes defined, class 1 and class 2, the
following commands would initialize 1000 VOLSERs per class in the
library making both classes ready for use:
Note: Since the INITIALIZE program automatically generates VOLSERs

starting with the VOLSER specified with VOL=, make sure you do not
overlap VOLSER ranges when entering these commands.
In the example above VOL=0000000 COUNT=1000 will result in the

1,000 tape volumes being created in the library with serial numbers
ranging from 000000 to 000999. VOL=001000 COUNT=1000 will
result in volumes ranging from 001000 to 001999 being created. The
result of these two commands is a virtual library with 2,000 volumes
whose serial numbers range from 000000 to 001999.
If you are initializing tapes on a Unisys mainframe, include the
LABEL parameter telling DLm the tape volume labels will be ANSI
format. For example:
INITIALIZE VOL=000000 DEV=E980 COUNT=500 LABEL=A CLASS=0
Note: If your tape devices are defined in a Manual Tape Library (MTL), you
must also define them in the mainframe's tape configuration database
(TCDB). You must run the DLMLIB utility to do this. Instructions for
running DLMLIB are provided in “Locate and upload the DLm utilities and
JCL for z/OS” on page 151.
Initialize scratch volumes 77

DLm Operations
Support access to DLm

DLm allows remote access to the ACPs for support and diagnostic
purposes. DLm supports EMC® Secure Remote Support (ESRS) that
monitors DLm operation. ACPs are provided with modem support to
communicate issues to EMC.
ESRS ESRS for VNX file storage monitors the operation of DLm for error
events and automatically notifies your service provider of error
events. It also provides a path for your service provider to use to
securely connect to your monitored DLm systems.
Figure 22 EMC Secure Remote Support

DLm Operations
Modem support DLm provides an external modem to allow remote access to the ACPs
for support and diagnostic purposes. The supplied modem is
normally attached to ACP1, the bottom ACP. A telephone line should
be connected to the ACP modem (which in turn should be cabled to
the COM1 port of the ACP). Figure 5 on page 23 shows the rear panel
of the ACP.
The ACP can be configured to send messages to EMC using the VNX
ConnectEMC function when problems are detected within the VNX
storage systems or the VTEC. The ConnectEMC options include
sending the messages via a modem through a customer-supplied
analog telephone line.
Support access to DLm 79

DLm Operations

3
DLm Administration
This chapter explains some of the DLm administrative tasks:

◆ Tape libraries....................................................................................... 82
◆ Configure virtual devices.................................................................. 85
◆ Manage configuration files ............................................................. 101
◆ Tape Erase ......................................................................................... 103
◆ Manage VTE and ACP logs ............................................................ 105
◆ Back-end tape support .................................................................... 108
◆ DLm diagnostic reporting............................................................... 113
◆ AWSPRINT library utility............................................................... 117
DLm Administration 81
DLm Administration
Tape libraries
A virtual tape library is controlled by a top level directory stored on
the VTE’s system disks. Each filesystem to be used as part of the tape
library must be mounted as a subdirectory within that top level
directory. The VTE automatically uses all filesystems mounted under
the top level directory to store tape volumes. For example,
/tapelib/CEL1_P1_FS1, where /tapelib is the top level directory and
/CEL1_P1_FS1 is the subdirectory.
DLm stores any number of VOLSERs in the filesytems within the
library until space within the filesystems is depleted. Additional
filesystems can be added to the library at any time without
disrupting the operation of the library. When a new filesystem is
available, DLm automatically begins using it when creating new tape
volumes. Each tape volume (VOLSER) is stored as a single file on one
filesystem.
Like real tape volumes, virtual volumes are written, read, and
scratched. Once a VOLSER has been scratched within the library, it
can be re-used during a future tape allocation process.
Tape libraries allow for multiple storage classes to be defined. Each
filesystem defined to a virtual library is assigned to only one storage
class. The storage classes are identified by numbers; for example: 0, 1,
2, etc. If you do not define a class, the filesystem you define is
assigned to the default storage class 0.
EMC service personnel define tape libraries during initial setup. The
steps to successfully define a tape library:
1. Create the filesystem on backend storage subsystems like VNX
and/or DD using DLm tools.
2. Define the lock file systems and other file systems in VTE
configuration.
3. Define the libraries to be used by each VTE and configure devices.
4. Install the configuration on all VTEs.
5. Initialize scratch tapes (VOLSERs) into the library.
At least one filesystem must be defined for each virtual tape library
you intend to define. It is also mandatory to define one small (10
MByte) filesystem to use as a lock directory.

DLm Administration
Note: To provide the best overall performance in FICON environments,

multiple filesystems in each library are desirable. While there is no strict
limitation, a minimum of four filesystems is recommended to enable the VTE
to balance output across all filesystems in the library.
Lock filesystem In addition to defining filesystems to the virtual tape libraries, DLm
also requires a small filesystem to use as a lock directory. A lock file
system is an NFS filesystem that is required during the allocation of
scratch volumes to keep temporary lock files. A 10 MB filesystem is
generally sufficient. EMC service personnel create the lock file during
initial system configuration and setup.
Some important considerations:
◆ The lock filesystem must be separate from the filesystems making
up your virtual tape library (libraries).
◆ When multiple VTEs share a virtual library, the lock filesystem
must be resident on the shared (NFS or fibre channel) storage that
all VTEs can access. It must be mounted on all the VTEs.
◆ Only one lock filesystem is required regardless of how many
virtual tape libraries you may be defining to the VTEs.
◆ Only one lock filesystem is required even if you have multiple
storage subsystems, such as VNX and DD.
◆ The same lock directory MUST be defined to each VTE accessing
a virtual tape library. The same lock directory can be used for
more than one virtual tape library.
◆ The lock filesytem is only used during the process of allocating a
new scratch volume for output. This filesystem is not used to
store tape volumes. (Therefore, the size of the lock filesystem
(directory) can be as small as 10 MB).
The lock directory is identified with a global parameter called
VOLSERLOCKDIR. This parameter is defined as an additional
parameter under the Global options on the Devices panel.
Note: If you do not define a lock directory filesystem, DLm assumes that you
want to operate in compatibility mode using an existing virtual library that
was created with an earlier version of VTE software.
Tape libraries 83
DLm Administration
Backward If you install a DLm 3.0-based VTE into an existing multiple-VTE

compatibility environment with an earlier version of software, you can operate the
new VTE in compatibility mode.
To operate in compatibility mode using an existing virtual library,
you simply do not define a lock directory filesystem in the
configuration. When the VOLSERLOCKDIR parameter has not been
defined on a VTE, the VTE assumes that the virtual tape library is an
existing library created with DLm software older than release 3.0.
Keep in mind that if the VTE is running in backward compatibility
mode the restrictions of the previous library architecture are all in
force. Specifically, each filesystem must be defined (mounted) in the
library using the first 2 characters of the VOLSERs that will be stored
in that filesystem. Filesystems are generally restricted to 10,000
VOLSERs per filesystem and new filesystems added to the library
must have VOLSERs initialized into them before they can be used.
If you are defining a new DLm virtual tape library, EMC strongly
recommends that you define a lock directory filesystem to take full
advantage of the DLm 3.0 enhanced filesystem architecture.

DLm Administration
Configure virtual devices

You can define up to 256 virtual 3480, 3490, or 3590 tape drives on
each DLm VTE.
Planning ◆ For z/OS systems, plan for one virtual device that will always be
considerations offline and can be used by DLm utilities to communicate with the
VTE.
◆ Additionally, if you plan to run the DLm z/OS started task
(DLMHOST), plan for one virtual device per VTE to remain
offline and be used by DLMHOST to communicate with the VTE.
DLm configuration The DLm Console allows you to configure the VTE and save your
files configuration as a configuration file. The default configuration file is
config. If you simply begin modifying the configuration, you will be
working with this default configuration file. Optionally, you can
create and use your own configuration files. DLm allows you to store
as many configuration files as you want. However, only one
configuration file will be the active configuration at any point in time.
The Configuration page shown in Figure 27 on page 99 allows you to
select the configuration file for a VTE. “Manage configuration files”
on page 101 provides more information. You must save your
configuration to a configuration file and install the configuration for
it to take effect on the VTE. The current active configuration file is
displayed in the Last installation field under the Description field.
Configure global Each DLm VTE includes a configuration utility, which is a

parameters browser-based graphical interface, to configure the virtual tape
drives on that VTE.
1. Access the DLm Console using the web browser. “Access the
DLm Console” on page 45 provides instructions.
2. Once connected, click Devices to display the Tape device
configuration panel. This panel contains a tab for each available
VTE.
3. Click the tab pertaining to the VTE you want to configure.
Configure virtual devices 85

DLm Administration
Figure 23 Global options
4. Enter values in the fields under Global options at the top of the
Devices panel:

DLm Administration
• Warn at: Sets the percentage of disk space usage at which

DLm will begin to warn about usage. Each time the contents
of a filesystem changes, the VTE checks the space used against
this value. If the used space in the filesystem is above this
value, a warning will be issued. The valid range is 0 to 100.
The default is 88%.
• Erase policy: Sets the erase policy you want the VTEs to use
when recovering space on scratched tapes: Space,
Time-to-Live (TTL) in days or hours, or Both. Erase policies
cannot be changed by a SET command. This is a global
parameter which applies to all tape library directories of a
VTE.
Note: If the VTE has tape libraries with VOLSERs that reside on
DD890, the erase policy must be configured to TTL.
“Tape Erase” on page 103 provides more information about

DLm’s erase policy.
• Start space recovery at: Sets the percentage of disk space
usage at which DLm starts to recover disk space by deleting
the data from scratch volumes. Valid values are 0 to 100. The
default is 85%. If the recovery percentage is set to 100, DLm
will never automatically delete scratch volume data to recover
disk space.
Note: This field is visible only if the Erase policy option, Space or
Both, is selected.
• Recover amount (1-100): When DLm starts to recover disk

space, it continues erasing data from scratch volumes until
this amount of free space has been recovered or until there are
no more scratch volumes that can be erased. Valid values are 1
to 100. The default is 5%. Setting recovery amount to 100%
causes DLm to erase the data from all scratch volumes on this
filesystem once the Start space recovery at value has been
reached.
Note: This field is visible only if the Erase policy option Space or
Both is selected.

DLm Administration
• Erase scratched tapes after: Indicates the duration for which

the data of a scratched tape must be retained before automatic
space recovery starts. You can specify this time period in days
or hours. Enter a value and select hours or days.
Note: This field is visible only if the Erase policy option TTL or Both
is selected.
! IMPORTANT
Stagger the Time-to-Live values across VTEs to ensure that
multiple VTEs do not start TTL cleanup at the same time.
“Time-to-Live erase policy” on page 103 provides more

information.
• Tape import/export enabled: Indicates whether or not this
VTE must provide export/import utilities. DLm allows the
physical attachment of a real IBM 3592 or TS1120 tape drive.
The VTE contains export/import that copy (export) a tape
volume (VOLSER) from the library to a physical 3592/TS1120
cartridge or copy (import) a physical 3592/TS1120 cartridge to
a tape volume (VOLSER) in the tape library. These utilities are
executed on the VTE and are independent of any mainframe
security programs (such as RACF and ACF/2). By default,
these utilities are disabled. Selecting the Tape export enabled
option enables the VTE’s export/import utilities.
• Write compatibility: Indicates whether or not the VTE needs
backward compatibility with previous generation VTEs. By
default, DLm is configured so that it will be backward
compatible with the previous version of DLm. This default
ensures that a new VTE can be installed into an existing
system and share tape volumes with older VTEs. Similarly,
volumes written by this VTE can be read by other, older VTEs.
For new installations, where there are no existing VTEs, this
option can be set to Allow new features but lose backward
compatibility. This allows the VTE to take full advantage of
all the features of the current generation VTE.
Note: If the VTE is running in backward compatibility mode, the

restrictions of the previous library architecture are in force. For
example, each filesystem must be defined (mounted) in the library
using the first 2 characters of the VOLSERs that will be stored in that

DLm Administration
filesystem; filesystems are restricted to 10,000 VOLSERs per

filesystem; and new filesystems added to the library must have
VOLSERs initialized into them before they can be used.
• Additional parameters: In addition to the pre-defined global

configuration parameters described above, there are global
free-form configuration parameters that can be manually
entered into the configuration. To add a free-form parmater,
click on the click to add free-form parameters link. The
currently available free-form parameter is
VOLSERLOCKDIR, seen as a link on the Tape device
configuration panel.
VOLSERLOCKDIR defines the location of the lock filesystem
to be used by the VTE. The mount point must have been
previously defined on the Available tab of the Storage panel
as well as on the VTE storage panel. Enter values in this
format:
VOLSERLOCKDIR </mountpoint>
For example, if the lock directory has been defined as the
filesystem located at mount point /lockfs/LOCK, enter:
VOLSERLOCKDIR /lockfs/LOCK
Note: If you have indicated that the VTE needs to be backward

compatible in the Write compatibility field, do not define a lock
directory filesystem in the configuration.
Add devices Define the virtual tape devices (drives) to be emulated to the
mainframe by this VTE in the Control units section.
Control unit Device Type
Figure 24 Control units

DLm Administration
1. Add one or more controllers to the configuration by entering a

valid control unit number and selecting a device type for the
devices to be defined on the VTE:
• Control unit
In the text box, type the hexadecimal control unit number that
you are configuring. For FICON, valid values are 00–FF.
• Device Type
Select the device type to be emulated: 3480, 3490, or 3590.
Note: All devices on the same Control Unit must be the same type.
2. Click the + button to complete the addition.

The control unit is added to the list and an Add devices
configuration section appears below the Global options section.

DLm Administration
Figure 25 Add devices section

DLm Administration
3. Enter values in the fields of the Add devices section to configure

the corresponding parameters for each device:
• Control unit
The hexadecimal control unit number that you are configuring
(from the list in the Control units section under Global
options).
• Add address range
The starting and ending hexadecimal device unit addresses
you wish to add to the VTE. You can define sets of 16 or
multiples of 16 (n0—nF).
• Initial device name
Each DLm system must have a unique device name. EMC
recommends using the same device name that is defined in the
UCB name in the mainframe operating system. The name you
type must end in hexadecimal digits, and the configuration
program increments the name for the number of devices you
are defining. For example, if you are defining 16 devices with
an address range of 00 - 0F and you type E900 in the Device
Name field, the configurator names the 16 devices E900, E901,
E902, ... E90F. The name you type may range from 1 to 8
characters long.
• Tape Library
The library to which this device is connected. To appear in the
list of available libraries, the storage must be defined on the
Available tab of the Storage panel and be connected to the
VTE on the VTE tab of the Storage panel.
Note: The /lockfs entry should never be selected as a tape library.
• IDRC
This parameter turns on or off write compression of the data
that DLm writes to the library. The available values are Yes,
No, and Force. The default value is IDRC=Yes.
When IDRC is set to Yes (IDRC=Yes), the VTE compresses the
data it writes to a virtual tape disk file, but only if the
mainframe instructs it to do so. Compression is controlled
differently by various host operating systems, but is generally
configurable in the JCL.

DLm Administration
When IDRC is set to No (IDRC=No), the VTE does not

compress the data it writes to a virtual tape disk file, despite
instruction from the mainframe. When IDRC is set to No, the
VTE still reports to the host that it supports compression but it
does not perform any compression on the data it writes to the
disk. This is because some host operating systems or tape
managers do not use drives that do not support compression.
Note: For devices attached to tape libraries that are configured for
deduplication, select No for IDRC during device configuration.
When writing to VOLSERs stored on deduplicated storage, the IDRC
setting is ignored. The VTEs do not compress the data before it is
written to the deduplicated storage. The deduplication device
deduplicates the data and compresses only the unique data before
writing to its drives.
IDRC=No affects only the writing of data. When IDRC is set

to No, the VTE can still read (decompress) virtual tape
volumes that it previously wrote with compression on.
IDRC=Force configures the DLm virtual tape device to
compress the data it writes to a virtual tape disk file regardless
of the mainframe's instructions to the VTE regarding the tape
file.
Note: Using Force with a deduplicating filesystem can severely limit

the ability of the storage system to de-duplicate and will, therefore,
use more real disk storage.
• Additional parameters
The Additional parameters field allows you to code a number
of optional keyword parameters which will be assigned to the
devices being created:
– GROUP=nn
nn is any decimal number. GROUP should be coded
whenever DLm is to be used on multiple LPARs. When
DLMMOUNT requests a mount, only virtual drives in the
same group are considered for the mount. When not coded
all drives default to GROUP=0.
– LABELS=S/N/A

DLm Administration
Most operating system mount requests specify a label type,

but for those that do not specify a label type, the LABELS
parameter sets the default label type for the drive. The
default label type is S for IBM standard (EBCDIC) labels.
Optional values are N for unlabeled, and A for ANSI
(ASCII) labels.
The label type affects only how new tapes are initialized by
DLm and what type of scratch tape to select when the host
does not specify a label in its mount request. The label type
setting has no effect on existing tape volumes. It has no
effect when the host requests a specific label type in its
mount request.
– SIZE=maxvolumesize
This parameter limits the maximum size of an individual
tape volume. The maximum volume size can be specified
in any of the following:- bytes (SIZE=nnnnnn)
- kilobytes (SIZE=nnnK)
- megabytes (SIZE=nnnM)
- gigabytes (SIZE=nnnG)
- terabytes (SIZE=nT).
When specifying kilobytes, megabytes, gigabytes, or
terabytes the value can contain a decimal point (that is,
SIZE=n.nT).
Size can range from 2 M to 32 T. If omitted, the maximum
volume size defaults to 2 G (two gigabytes) for 3480 or 3490
tape devices and 40 G (40 gigabytes) for 3590 tape drives.
The maximum allowable tape size for all drives is 32 T but
is limited to the amount of available storage in the
filesystem.
– TRACE=n
This parameter allows you to set the trace option for this
specific device:
0 — No tracing
1 — Trace errors only (default)
2 — Trace errors and status
3 — Trace errors, status, and headers

DLm Administration
4 — Trace errors, status, headers, and data

5 — Perform a full packet trace (for customer support only)
– VOL=(xx(,yy,…))
VOL allows new scratch volume allocations to be
restricted to a specific range of tape volumes beginning
with the prefixes defined in VOL.
xx can be from 1 to 6 characters in length. For example, 00,
001, 0011, 00111, and 001111 are all valid examples of a
VOLSER prefix.
VOLSER prefix(es) set with VOL are honored during
scratch mounts ONLY. The VOL prefixes filter is applied
after all other class, space, age, label-type, penalty, and
synonym filters have been applied. VOL prefixes do not
affect the determination of which directories are picked or
in which sequence directories are picked.
VOL prefixes do not affect the sequence that VOLSERs are
evaluated in. These prefixes are simply a filter that is
applied to the VOLSER candidates being considered. The
sequences of the prefixes does not change the evaluation
process in any way. If any one prefix matches a candidate
VOLSER, the VOLSER passes the test and is selected for
the scratch allocation.
For example, if VOL=(01,02) is specified for a range of
devices then those devices would only allocate new scratch
volumes to VOLSERs beginning with '01' or '02'. If no
scratch volumes beginning with '01' or '02' are available in
the storage class being allocated to them, the allocation will
be ignored and the device will remain in a Not Ready state.
4. When the parameters are set to your satisfaction, click Add range
to create the new devices.
A Current devices section appears at the bottom of your screen
showing the devices that have been created.
5. You can change the configuration of individual devices in the
Current devices section.

DLm Administration
Note: If you configure the tape devices into a Manual Tape Library (MTL) on
the mainframe, be aware that MTLs only allow 16 devices per control unit. In
that case, instead of defining 32 devices on a single control unit, define two
control units with 16 devices each.
Scratch synonyms When the mainframe wants a tape volume (VOLSER) mounted on a
tape device, it sends a load display command (CCW) over the
channel to the device identifying the VOLSER to be mounted. For
example, in z/OS, if a user codes JCL for a tape volume that reads
"VOL=SER=000001", z/OS sends DLm a load display CCW
indicating that the tape volume with VOLSER '000001' needs to be
mounted on the drive. After sending the load display CCW, z/OS
waits for the device to become ready and then reads the VOL1 label
to verify the serial number.
z/OS uses the default character strings SCRTCH and PRIVAT to
indicate a request for a scratch tape to be mounted for output. By
default, DLm recognizes these two strings as a request for a new
scratch tape and mounts an available scratch tape on the requested
device to be used for output.
Most commercial tape management systems (TMS) support the
concept of tape pools, allowing you to define your own scratch pools
for use when mounting a new scratch tape. In support of TMS tape
pools, DLm allows you to define unique “scratch synonyms” to the
VTEs. During installation, you can configure your own sub-pools of
scratch tapes to request tape mounts using meaningful names.
DLm accepts up to 64 scratch synonyms. It also tolerates the presence
of (but does not allow editing of) more than 64 scratch synonyms.
The field in the Scratch Synonyms section under Global options let
you include whatever names your installation uses to request scratch
tape mounts. DLm recognizes these synonyms, along with SCRTCH
and PRIVAT, as a request for a new scratch volume when they are in
a load display CCW.

DLm Administration
Figure 26 Scratch Synonyms
To add scratch synonyms (tape pool names):

1. Define a scratch synonym in the following format in the Scratch
Synonyms section under Global options :
synonym=(prefix1,prefix2,…CLASS=(CLASSn,CLASSn,…))
where:
• synonym is the character string to be used as the synonym.
Synonyms may be 1 - 8 characters in length and must contain
only letters A-Z and numbers 0-9.
Note: Synonyms are not case sensitive and may be entered in either
upper or lower case.
• prefixn is a scratch synonym that may be associated with a

specific set of VOLSERs. Each prefix can be from 1 to 6
characters in length. prefixn defines the prefix characters of
the VOLSERs that can be assigned in response to a scratch
request made with this synonym.
For example, SCRTCH=(00,01) would imply that any load
request received for SCRTCH must be satisfied with a
VOLSER that startes with either "00" or "01". Valid VOLSERs
that could be mounted by DLm would include any VOLSER
in the range 000000 - 019999; assuming only numeric
VOLSERs are in use. If there are no scratch tapes with
VOLSERs beginning with "00" or "01" then DLm does not
mount a tape and the mount will remain pending.
If a VOLSER prefix is not defined for a specific scratch
synonym then any available scratch tape will be used.

DLm Administration
• CLASSn - defines the storage class or classes associated with

this scratch synonym. For example,
PRIVAT=CLASS=CLASS1 would indicate that any load
request received for PRIVAT must be satisfied by allocating a
scratch VOLSER in storage class 1. DLm normally selects
which storage to write a new VOLSER to based on free space
and frequency of filesystem use. When a synonym specifies a
specific class of storage be used, DLm first identifies all
filesystems assigned to the storage class (or classes) and then
selects a filesystem from those filesystems based on free space
and frequency of use.
If a class is not specified, then the scratch synonym will by
default only apply to the default storage class of 0.
2. Click the + button to complete the addition.
Example Consider the following definitions of scratch synonyms:

WORK
SCRTCH=(00,01)
PRIVAT=CLASS=CLASS1
In this example any mount requested with the synonym WORK will
be assigned any available scratch tape in the default storage class 0.
A request for SCRTCH will also go to default storage (class 0), but
will only be assigned a volume with a serial number beginning with
00 or 01. If no scratch tapes with these prefixes are available the
mount will not be satisified and will remain pending.
PRIVAT tapes will go to storage assigned to storage CLASS 1. Any
available scratch tape within that class will be used. If there are no
available scratch tapes in CLASS 1, the mount will remain pending.
The syntax is very important when coding scratch synonyms. For
example defining:
◆ DRTAPE=(00,01),CLASS=(CLASS1,CLASS2)
defines two synonyms, DRTAPE and CLASS. DRTAPE will use
volume serial numbers beginning with 00 or 01 in Class 0 storage.
CLASS will use only VOLSERS of CLASS1 and CLASS2.
◆ DRTAPE=((00,01),CLASS=(CLASS1,CLASS2))

DLm Administration
establishes the scratch synonym DRTAPE using VOLSERs

beginning with 00 or 01 located in either storage class 1 or storage
class 2.
Note: It is not necessary to define any scratch synonyms. By default, DLm

allocates any request for SCRTCH or PRIVAT to any scratch tape available on
the default (class 0) storage class.
Save configuration 1. Select the Configurations menu at the top of the screen.
2. On the Configurations panel, click Save Changes to save your
configuration to disk.
Figure 27 Save configuration
3. To activate the configuration file, select the VTE on which it must

be installed at the bottom of the page and click Install on nodes.
“Activate or install a configuration” on page 101 provides more
information.
Delete a device 1. Select the Devices menu at the top of the page.
range

DLm Administration
2. Scroll down to the Current devices section.

3. Scroll to the device range you want to delete and click the X
button next it.
4. Select the Configurations menu at the top of the screen.
5. On the Configurations panel, click Save Changes to save your
configuration to disk.
“Manage configuration files” on page 101 describes the procedure to
install the updated configurations.
DLm Administration
Manage configuration files
Activate or install a You must install a configuration for it to be used by a VTE. If you
configuration modify the currently installed configuration, the changes will not
become active until you re-install the configuration.
To install (and activate) your configuration:
1. Select the Configuration menu at the top of the DLm Console
screen.
2. Select the VTE on which it must be installed at the bottom of the
page and click Install on nodes.
3. Click Install on the Configuration operations panel.
Note: In multiple-VTE configurations, all VTEs must be powered on and

running when you click Install.
! CAUTION
When you click Install, the virtual tape application (VTD) restarts.
If your VTE is currently online with the mainframe, DLm strongly
recommends that you idle all tape drives and vary them offline
before installing a new configuration.
If your DLm system has multiple VTEs, the VTD on every VTE
detecting a change to its current configuration will automatically
restart. However, if you are adding a new VTE to an existing system,
you can install the configuration while the existing VTEs are active as
long as you take care not to modify any of the existing VTE’s
configurations.
Create a new 1. Select the Configuration menu at the top of the DLm Console.
configuration 2. Enter a configuration name in the text box adjacent to the Create
configuration named: button.
3. Select the Devices menu at the top of the DLm Console and enter
the configuration values described in:
• “Configure global parameters” on page 85
• “Add devices” on page 89
• “Scratch synonyms” on page 96
Manage configuration files 101

DLm Administration
4. Save the configuration as described in “Save configuration” on

page 99.
Copy a 1. Select the Configuration menu at the top of the DLm Console.
configuration 2. At the top right corner of the page, select the configuration file
you wish to copy.
3. From the list box near the Copy to field select the config file to
which the configuration must be copied.
4. Click Copy to.
5. At the top right corner of the page, select the configuration file
you just copied changes to.
6. Click Save changes.
Modify or delete a 1. Select the Configuration menu at the top of the DLm Console.
configuration 2. Select the configuration file you wish to modify or delete.
3. Do one of the following:
• To modify the configuration file:
a. Select the Devices menu at the top of the DLm Console and
make the required changes.
b. Return to the Configuration menu and click Save changes.
• To delete the configuration file:
Click Delete.
DLm Administration
Tape Erase
DLm supports a space recovery feature that automatically erases data
from scratch tapes on the filesystem based on an erase policy.
The available erase policies are:
◆ Space
◆ Time-To-Live (TTL)
◆ Both (default)
Note: If the VTE has tape libraries with VOLSERs that reside on the Data
Domain DD890, the erase policy must be configured for one of the
Time-to-Live options.
The erase policy is a VTE-wide setting. The erase policy can be

different on different VTEs. These erase policies affect only
AWS-format scratch tapes residing on NFS filesystems. They affect
only automatic space recovery erasing. Erase policies have no effect
on erase actions performed by mainframe programs such as
DLMSCR. You can configure the erase policy using the fields
described in “Configure global parameters” on page 85.
Space erase policy When a filesystem reaches a specified percentage of space usage,
DLm begins erasing data in that filesystem until the amount of space
specified in the recovery amount parameter has been recovered. The
threshold value, which triggers DLm to erase data from scratch tapes
is specified using the Start space recovery at field.
This automatic space recovery erases the oldest scratch tapes first
(based on the time it was scratched). This method is used so that the
most recently scratched tapes can be available for sometime before
being erased.
Time-to-Live erase The TTL erase policy gives you better control over the length of time
policy that the data on a scratch tape is retained when the tape is in the
scratch pool. The data on a particular tape is erased when the amount
of time since this tape was moved from the active pool to the scratch
pool exceeds the duration specified for TTL in the erase scratched
tapes after option. Once the period expires, the tapes will
automatically be erased regardless of current space utilization. The
default TTL value is 365 days.
Tape Erase 103

DLm Administration
You can specify the time in:

◆ Days
◆ Hours
Note: If the VTE has tape libraries with VOLSERs that reside on the Data
Domain DD890, the erase policy must be configured to one of the
Time-to-Live options.
DLm6000 with integrated Data Domain storage does not

immediately return the deleted storage to the free-space pool.
! IMPORTANT
Stagger the Time-to-Live values across VTEs to ensure that
multiple VTEs do not start TTL cleanup at the same time.
Staggering the Time-to-Live values across VTEs ensures that only the
required number of VTEs are engaged in TTL cleanup. The VTE with
the minimum Time-to-Live value starts recovering space. If that VTE
cannot complete erasing the scratched tapes before the next higher
Time-to-Live value, the next VTE joins in and helps to complete the
space recovery.
For example, in a four-VTE system, if you set the Time-to-Live value
of VTE4 to 48 hours, set that of VTE3 to 36, that of VTE2 to 24 hours,
and that of VTE1 to 12 hours.
In the case of this example, VTE1 starts erasing tapes that were
scratched 12 hours ago. If it cannot complete the recovery, VTE2 starts
at the end of the twenty fourth hour. Both VTEs recover space until all
the tapes are cleaned up. If VTE1 and VTE2 cannot complete the
space recovery at the end of the thirty sixth hour, VTE3 joins VTE1
and VTE2 in recovering space.
Note: You can also select both options.
DLm Administration
Manage VTE and ACP logs

The DLm Console allows you to view the most recent VTE logs and
gather ACP and VTE logs for diagnostic purposes.
VTE logs VTEs maintain a log of all messages issued by the virtual tape
application. Log files are automatically rotated each day at midnight.
Old log files are compressed to minimize the space they take and then
kept for a period of time.
To view the latest VTE logs:
1. Access the DLm Console using the web browser. “Connect to the
The System status tab of the Status menu opens by default.
Figure 28 System status
2. Click the icon in the Logs column corresponding to VTE

for which you need the logs.
Manage VTE and ACP logs 105

DLm Administration
Figure 29 VTE logs
3. Use the browser’s navigation button (arrow) to return to the

System status tab. If you receive a page-expired message, refresh
the page to view the System status tab.
Support data To gather ACP and VTE details for diagnostic purposes:
1. On the Status menu, click the Gather logs menu.
The ACPs and VTEs are listed in the Machine name column.
Figure 30 Gathering ACP and VTE support data
DLm Administration
2. Under Support data, click Gather in the row corresponding to the

system for which you want to gather support data.
The Last gathered column displays a link with the time stamp of
the last gathered data.
A pop-up window confirms the request followed later by another
pop-up indicating that the Gather is complete.
3. Click the link in the Last gathered column to download the
support data.
The downloaded file is a zip file with the name
<machine-date-time-logs.zip>; for example,
acp2-2011-04-26_19-13-08_logs.zip. The zip file contains the
following directory structure when extracted:
logData-<date collected>
- sh.log
+ etc
- fstab
- hosts
- mtab
- system_params.json
+ app
+ snmp
- snmptrapd.conf
+ linuxsnap
- linuxsnap.txt
+ opt
+ webconsole
+ backup_config
- last_good_config
- last_install
- lastInput.json
- lastInput.msg
+ configs
- <configuration file name>.json
- <configuration file name>.msg
- rsaInit.cfg
- rsaInitClient.cfg
- rsaInitSvc.cfg
+ logs
- apply.log
- logAll.txt
- status.txt
+ proc
- mdstat
- mounts
+ var
+ log
+ apache2
- access_log
- error_log
Manage VTE and ACP logs 107

DLm Administration
Back-end tape support

The DLm allows the Fibre Channel attachment of IBM 3592 or
IBM-compatible tape drives. Each VTE supports one physical IBM
3592 tape drive attached using point-to-point connection. A Fibre
Channel port is provided at the rear of each VTE for physical tape
functions. You must provide the IBM 3592 drive and a Fibre Channel
cable to connect the drive to a port on the VTE.
Note: DLm supports only point-to-point attachment of a single 3592 tape

drive to the VTE. Connection through a Fibre Channel switch is not
supported.
After the drive is physically attached to a VTE, you have two choices:
◆ Map a single mainframe tape drive (device address) to the
physical tape drive for writing real tape cartridges from the
mainframe. This capability is referred to as Direct Tape.
◆ Use the DLm VTE-based Export and Import utilities to copy
individual volumes (VOLSERs) from or to the tape.
Direct Tape
DLm is primarily a tape-on-disk controller, which emulates tape
drives to the mainframe and stores tape volumes on a back-end disk
subsystem. However, it also allows a tape-drive-to-tape-drive
mapping of an emulated 3590 tape drive to a physical IBM tape drive
attached to a DLm VTE.
Device mapping To map a single mainframe device address through to a Fibre

Channel attached IBM 3592 or TS1120 tape drive, modify the virtual
device definition to point the device to the physical drive instead of a
virtual tape library on disk. (See Figure 25 on page 91.)
For the device being mapped to the physical drive, you must replace
the Tape Library parameter by coding the following parameter:
DRIVE-nnnnnnnnnnnn
where nnnnnnnnnnnn is a 12-digit serial number for the tape drive. If

your drive serial number is less than 12 characters in length then you
must pad the number to the left with zeros. For example, if your
serial number is 7818330, then you would enter
DRIVE-000007818330 into the Tape Library field for the mapped
DLm Administration
drive. The emulated tape drive must be configured to match the

characteristics of the physical tape drive. The device being configured
must be defined as Device Type 3590. (See Figure 24 on page 89.)
On the required VTEn tab under the Devices menu of the DLm
Console, make these changes:
1. In the Control Units section, specify the device type as 3590.
“Add devices” on page 89 provides more informaton.
2. In the Add devices section, enter DRIVE-12-digit drive serial
number>
To determine the drive serial number:
Note: This procedure requires restarting the Virtual Tape application a

minimum of two times. For this reason, you should vary the drives
defined on this VTE offline to the mainframe.
a. Vary the drives defined on this VTE offline to the mainframe.

b. Verify that the external tape drive is powered on.
c. Verify that the external tape drive is connected to the Fibre
Channel adapter of the VTE.
d. Verify that the VTE's operating system driver can see the
external tape drive. From the VT console type:
1. scsiadd to rebuild the SCSI device table
2. lsscsi and ensure that you see the external tape device in
the output
e. Stop and start the VTD to pick up the new tape drive
information. Type:
STOPVT
STARTVT
f. Obtain the drive serial number by typing the following on the

VT console:
show drive list
3. From the VT console, stop the VTD again:

STOPVT
4. Update the appropriate tape drive configuration.
Back-end tape support 109

DLm Administration
5. From the VT console, retart the VTD:

STOPVT
At this point, the tape application should start and verify the
external tape drive.
If you receive an error and the tape daemon stops, verify that the
tape drive displays "online" and try again.
6. Vary the drives defined on this VTE online to the mainframe.
7. Close the VT.
Segregate the After mapping a device as described in “Device mapping” on

devices page 108, isolate the mainframe device from other virtual devices in
the mainframe configuration in order to control when a real tape is
written versus a virtual tape written to disk. Specifically, if you are
using MTLs, you must assign a unique library ID (MTL) to this
device address. A physical cartridge is written to only when the
system ACS routine determines that a real cartridge is to be written to
and assigns the appropriate library ID. Otherwise, when the
mainframe allocates to the library IDs (MTL) representing the other
drives, a virtual volume is written.
When a mainframe device is mapped to a physical tape drive in this
manner, mount requests work just as they would if the drive were
directly attached to a mainframe channel. Allocation of the drive
results in a mount request being posted to the mainframe operator
console. The request remains outstanding until the physical drive
becomes ready. Normally, this requires an operator to mount a tape
and ready the drive.
The tape cartridge written will be compatible with 3590 cartridges
written from any mainframe-attached 3590 tape drive unless the
volume has been encrypted by DLm. DLm-created cartridges can be
sent to mainframe locations that do not have DLm installed as long as
those locations have real or compatible tape drives capable of reading
the 3590/3490E cartridge.
Compression
DLm supports IDRC data compression. If a mainframe tape device
mapped to a physical fibre channel attached drive requests
compression VTE will instruct the drive to compress the data before
writing it to tape. The tape drive, rather than DLm, will perform the
data compression in order to ensure compatibility with other IBM
drives that may later attempt to read the data.
DLm Administration
Export to and import As an alternative to Direct Tape, when a mainframe tape drive is
from tapes mapped directly to a physical IBM drive, DLm includes two utilities
for exporting and importing tape volumes between the DLm disk
library and a tape drive attached to a DLm VTE.
These commands are executed within the tape-on-disk application
running on the VTE, where the drive is attached. You can have either
pass-through or import/export functionality, not both.
The EXPORT and IMPORT utilities are disabled in the default DLm
VTE configuration because:
◆ These commands copy tape volumes based only on the VOLSER
irrespective of the data actually contained on the volume.
◆ A DLm VTE does not usually have a tape drive physically
attached to it.
To enable the EXPORT / IMPORT utilities:
1. Access the DLm Console using the web browser. “Access the
2. Click Devices to display the Tape device configuration panel.
This panel contains a tab for each configured VTE.
3. Click the tab pertaining to the VTE you want to configure. (The
screen shown in Figure 23 on page 86 opens.)
4. Select the Tape import/export enabled check box. “Configure
global parameters” on page 85 provides more information about
this field.
5. Save the configuration as described in “Save configuration” on
page 99 and install it on the VTE as described in “Activate or
install a configuration” on page 101.
The next time the VT application restarts, the EXPORT and
IMPORT utilities are available.
Note: DLm does not support import and export of scratch tapes.
To run these utilities:

1. Open the VT console of the VTE, where the tape drive is attached.
“Access a VTE” on page 54 provides instructions.
2. After connecting to the individual VTE, you can type the
EXPORT and IMPORT commands in the VT console.
Back-end tape support 111

DLm Administration
Note: EXPORT and IMPORT commands have no user interaction. If a

command is typed incorrectly, an error message is displayed. Retype the
command.
“EXPORT” on page 184 provides details about how to use the

EXPORT command. “IMPORT” on page 186 provides details about
how to use the IMPORT command.
DLm Administration
DLm diagnostic reporting

The VTEs continually generate informational, warning, and error
messages as they operate. These messages are written to the internal
system disk so that they can be retrieved as necessary during
problem determination. Messages will also be automatically
displayed on the VT console.
Additionally, DLm is capable of sending informational, warning, and
error messages to any of the following:
◆ An SNMP management console
◆ One or two customer e-mail addresses
◆ An EMC DLm support e-mail address
◆ The z/OS master console via a z/OS started task
You can configure which messages get sent to each destination using
the Messages panel of the DLm Console.
For sending messages to SNMP and to customer e-mail addresses:
1. Configure Virtuent with message destinations.
2. Configure which messages should be sent.
For DLm support e-mail, you need to specify an option for vendor
messages. For z/OS messages you must install the z/OS started task
and then configure which messages you want sent.
SNMP
Each VTE contains an SNMP agent and MIB files for monitoring and
analysis. Once configured, the VTE can send SNMP alerts to a
designated SNMP manager.
The VTEs are preconfigured so that once the agent has been given the
IP address of the management console, SNMP traffic flows from the
VTE to the ACP. The ACP forwards SNMP traffic to an SNMP
manager on your corporate network. The SNMP alerts are forwarded
to the VT console.
To configure a VTE to send SNMP alerts:
2. Click External.
DLm diagnostic reporting 113

DLm Administration
3. Select the Notify tab.
Figure 31 SNMP configuration
4. Under SNMP notifications, type the host name or IP address of

one or two systems where you want SNMP management
messages to be sent.
If either of the SNMP manager host fields contain a valid host
name or IP address, the VTE forwards messages to that host. If
both fields are blank then SNMP messaging is inactive.
ConnectEMC
The DLm ConnectEMC function can automatically notify the EMC
service center or other service providers if the VTEC or VNX system
detects a serious problem. ConnectEMC sends messages using one of
the following:
◆ Email
◆ FTP
◆ Modem (through a customer-supplied analog telephone line)
The FTP and e-mail connections require the DLm to have access to
your company's LAN.
ConnectEMC is configured by EMC personnel during initial setup.
You can have them configure the VTEC to generate ConnectEMC
events for error-level SNMP traps. “VTEC errors that generate
ConnectEMC events” on page 374 provides a list of traps that
generate ConnectEMC events.
DLm Administration
Data Domain DD890 alert notifications

The DD890 generates e-mail alerts when it identifies a problem with
either a software component or a hardware component. Not all
events generate an immediate e-mail notification.
Alert e-mail All events of CRITICAL or WARNING severity result in immediate

(generated notification to the EMC Data Domain support group. For events with
immediately) a CRITICAL severity level, the Data Domain DD890 can also be
configured to forward the e-mail notification to the e-mail address of
the system administrator.
Autosupport e-mails The Data Domain DD890 generates daily e-mails to the EMC Data
(generated once a Domain support group. These e-mails contain information about all
day) outstanding alerts and the status summary of the general health of
the DD890. You an also configure Autosupport emails to be sent to
the email address of the system administrator.
Configure message types and recipients

You can configure which message type get sent to each destination:
an SNMP management console, customer e-mail addresses, the DLm
support e-mail address, or the z/OS master console.
2. Click Messages.
Three tabs appear representing informational, warning, and error
messages:
• Error message routing
• Warning message routing
• Informational message routing
Each tab shows a complete list of all DLm messages in that
particular category.
3. Select the tab corresponding to the message type you want to
configure.
DLm diagnostic reporting 115

DLm Administration
Figure 32 Alert messages
4. Select the check boxes in the following columns to send alerts to

the corresponding recipient:
• SNMP
• Mainframe
5. Click the toggle all check boxes to reverse the selection.
DLm Administration
AWSPRINT library utility

The awsprint utility allows you to produce lists of the tapes in the
virtual tape library within the filing structure in DLm. You must use
the command processor CP503 to obtain the awsprint output. The
EMC Disk Library for mainframe Command Processors User Guide
provides information about CP503.
The FIND VOLUME command function is related to that of
awsprint. This command finds a specific volume (VOLSER) in the
DLm tape library and reports the current status of that volume.
“FIND” on page 185 provides the details of the command.
AWSPRINT library utility 117

DLm Administration
4
DLm Replication
This chapter explains the replication concepts and features of a DLm

system:
◆ Overview ........................................................................................... 120
◆ Replication terminology.................................................................. 122
◆ VNX replication................................................................................ 124
◆ DLm VNX replication and disaster recovery............................... 126
◆ Disaster recovery in Data Domain systems ................................. 132
◆ Deduplication storage replication ................................................. 130
DLm Replication 119

DLm Replication
Overview
DLm offers IP-based remote replication, which leverages your IP
network infrastructure, eliminating the need for channel extension
hardware. The replication is storage-based and therefore has no
impact on mainframe host operations or performance. DLm
replication is asynchronous and only the changes are replicated
between the remote sites.
DLm supports unidirectional and bidirectional replication, which
means that the source system can also be a target system and vice
versa. VNX replication supports up to four target sites per source
system, which means you can replicate data to four different sites.
The source and destination DLm systems do not have to be
configured with the same capacity.
DLm replication is a separately licensed feature. In the DLm6000,
VNX replication and deduplication storage replication are licensed
separately. There are some key differences in the way VNX
replication and Data Domain replication work.
Note: A separate license is required for each active storage controller.
VNX replication in DLm occurs at the filesystem level. A filesystem is

a virtual shelf of tapes in which a continuous range of VOLSER are
defined. VNX replication on DLm lets you maintain a remote copy of
a collection of virtual tape volumes. Figure 33 on page 121 depicts
DLm replication.
VNX replication is based on EMC VNX Replicator V2. Using VNX
Replicator (V2) provides more information on VNX V2 replication.
This document and the latest documentation for your specific version
of the VNX operating environment (OE) for file are available at EMC
Online Support website.
Data Domain replication occurs on directories corresponding to a
tape library and not at the filesystem level. A tape library is a
collection of virtual shelves of tapes. In each virtual shelf, a
continuous range of VOLSERs is defined. Data Domain replication is
based on the EMC Data Domain Replicator. Only unique data with
respect to the destination is replicated from the source Data Domain,
resulting in large savings in replication bandwidth utilization.
DLm Replication
Primary site Remote site

VNX
Celerra VNX
Celerra
Mainframe Mainframe
VTEC VTEC
Data Domain Data Domain GEN-001347
Figure 33 DLm replication
Overview 121
DLm Replication
Replication terminology
The following is some of the terminology used when describing
DLm replication:
◆ Replication
The process of sharing information to ensure consistency between
redundant resources.
◆ Source object (SO) is also known as:
• The production object (PO)
• The production filesystem (PFS)
• The source filesystem (SFS)
This is the original source collection of data to be replicated.
◆ Destination object (DO) is also known as:
• The destination filesystem (DFS)
• The target filesystem (TFS)
• The secondary filesystem (SDS)
This is the replicated copy of the original data.
◆ Replication session
The relationship that enables replication between the SO and the
DO, including two internal checkpoints or snapshots for both SO
and DO.
◆ Time-out-of-sync
Defines how closely you want to keep the destination object
synchronized with the source object. This is specified in minutes.
◆ Full copy
The complete copy of the source object that is sent to the
destination when a replication session is first started, or when a
common base is not found.
◆ Differential copy
The changes made to the source object (since the previous
replication) that are sent to the destination during replication.
DLm Replication
◆ Snapshot or checkpoint
A point-in-time copy of data. This view of data takes very little
space and are just pointers to where the actual files are stored.
Snapshots/checkpoints are used when transporting the full copy
after first synchronization. Using SnapSure on VNX provides
detailed information on snapshots. This document is available at
EMC Online Support website.
◆ Disaster recovery (DR)
The process, policies, and procedures for restoring operations
critical to the resumption of business, including regaining access
to data, communications, and other business processes after a
natural or human-induced disaster.
◆ Recovery point objective (RPO)
A description of the amount of data lost, measured in time. For
example, if the last available good copy of data was made 18
hours before an outage, then the RPO is 18 hours. You can define
different RPO values for different VOLSER ranges or tape
libraries based on information criticality.
◆ Recovery time objective (RTO)
A specified amount of time within which a business process must
be restored after a disaster to avoid unacceptable consequences
associated with a break in continuity. RPO and RTO form the
basis on which a disaster recovery strategy is developed.
◆ Storage controller interconnect is also known as:
• Data Mover interconnect (DMIC)
• DART interconnect (DIC)
The storage controller interconnect is a communication path
between two VNX storage controllers (Data Movers) that is used
for all replication sessions between those two storage controllers.
This connection defines all interfaces that can be used on each
storage controller, and also the bandwidth throttle schedule. This
interconnection must be created in both directions.
Replication terminology 123

DLm Replication
VNX replication
VNX replication is based on EMC VNX Replicator V2. Using VNX
Replicator (V2) provides more information on VNX V2 replication.
This document and the latest documentation for your specific version
of VNX operating environment (OE) code are available on the EMC
Online Support website.
Prerequisites for VNX replication are:
◆ The required replication licenses are installed in the source and
destination DLm systems.
◆ VNX7500 runs the VNX OE version 7.0.12.0 or later.
◆ You have the IP addresses that are assigned to the source and
destination storage controllers (Data Movers).
◆ The HTTPS connections between the source and destination
storage controllers (port 5085) and between the source and
destination Control Stations (port 443) are secure.
◆ Sufficient storage space is available for the source and destination
filesystems.
Supported configurations
DLm supports the following configurations for VNX replication:
◆ Local replication: Between two separate storage controllers
located within the same DLm.
◆ Remote replication: Between two separate DLm systems,
typically (but not necessarily) in different geographic locations.
This includes replicating from a single source to up to four
separate destinations.
◆ Bi-directional replication: DLm A replicates to DLm B, while
DLm B replicates a different filesystem to DLm A.
Currently, these configurations are not supported:
◆ Replication to more than four separate destinations
◆ Cascading (for example, DLm A replicates to DLm B which in
turn replicates to DLm C)
DLm Replication
VNX replication procedure

DLm uses VNX Replicator V2 to replicate VOLSERs stored in NFS file
systems on the source VNX. The filesystem on the VNX corresponds
to a VOLSER range in DLm.
The replication environment is initially set up for you at installation
by EMC service personnel. They use the DLm tools to create the
target filesystems and then connect the source to the target filesystem.
The target filesystem must have the same name and size as the source
filesystem. To make changes or additions to your replication
environment, contact EMC Customer Support.
VNX replication DLm allows many VNX replication sessions to be active

sessions simultaneously. Creating a replication session involves these tasks:
1. Ensure that the SO already exists.
2. Create and mount (read only) the DO with the same size and
properties as the SO (if it does not already exist).
3. Create internal snapshots at both the source and destination end.
Note: Using SnapSure on VNX provides detailed information on

snapshots. This document is available at EMC Online Support website.
4. Configure and start the replication scheduler that drives the

time-out-of-sync policy between the two ends.
5. Establish replication between the source and destination end.
Data replication The replication of source data occurs in the following way:
1. An application running under z/OS writes data to one or more
virtual tapes (VOLSERs) within a filesystem (VOLSER range) set
up for replication on DLm.
2. Replication creates a checkpoint—a point-in-time, block-level
copy of the underlying filesystem.
3. Using intelligent scheduling algorithms, checkpoints are
transferred to the remote destination asynchronously.
4. Only changed blocks are copied.
VNX replication 125

DLm Replication
VNX RepOutOfSyncHours feature

DLm version 2.1 and later provides a replication monitoring feature
called the RepOutOfSyncHours feature. The EMC VNX Replicator
monitors the synchronization status of each active replication session.
Every time a session goes out of synchronization, a timer starts
tracking the duration of the out-of-sync state. If that session does not
get synchronized within a specified time period, DLm generates a
ConnectEMC alert for an out-of-sync callhome condition. If the session
returns to synchronized state before the specified time period expires,
the timer is reset.
The default time period before the generation of an out-of-sync
callhome alert is eight hours. If you want to change the default time
period, contact EMC Customer Service.
Using VNX Replicator (V2) provides more information about the
RepOutOfSyncHours feature. This document and the latest
documentation for your specific level of VNX OE code are available
atEMC Online Support website.
DLm VNX replication and disaster recovery

This section explains the role of DLm replication in a disaster
recovery (DR) strategy. “Replication terminology” on page 122
explains terminology relevant to DLm replication in a disaster
recovery strategy.
Replication is not a complete disaster recovery strategy, although it
provides an essential enabling technology for accomplishing DR. A
DR workflow must take into consideration your environment,
potential scenarios, and the desired recovery objectives.
The disaster recovery procedure in DLm involve the following steps:
1. Mount the read only copy of the all the filesystems at the target
site on the VTEs.
2. Identify the tapes that have been lost due to the disaster event.
3. Perform a failover of the filesystems in the VNX.
4. Unmount and remount the filesystem as read/write.
5. When the source system becomes available, copy the changes
made at the target back to the source system.
DLm Replication
6. After all the changes have been copied to the source, change the
configuration to the original configuration.
Replication reduces both RPO and RTO. Each filesystem (VOLSER
range) maintains a unique and independent value for:
◆ Time-out-of-sync — This controls how often the destination site is
refreshed. Depending upon your load and bandwidth, this can be
nearly synchronous. This value is equivalent to the RPO
described in “Replication terminology” on page 122.
◆ Quality of service (QoS) — This controls bandwidth throttling by
specifying limits on specific days and hours.
Time-out-of-sync DLm replication uses an adaptive scheduling algorithm to determine

when to refresh replicated storage. RPO is typically set to less than 10
minutes. The replication scheduler uses best effort to maintain the
specified RPO for each range of VOLSERs, and automatically works
to catch up after any RPO violation. Advanced capacity planning is
required to make sure that RPO violations do not occur. However,
events (SNMP traps or email) can be configured in case RPO
violations do occur.
Quality of service Interconnect QoS defines up to six bandwidth schedules. These are
defined in terms of days, hours, and bandwidth.
Identifying lost tapes To identify tapes that have been lost due to the disaster event:
1. Use the awsprint utility to identify the list of scratch tapes in the
file systems that have been disrupted. Compare the output of the
utility with the list of scratch tapes for this VOLSER range
according to the Tape Management Catalog. Some will appear in
the awsprint output but not in the Tape Management Catalog as
they were no longer in scratch state when the disaster event
occurred. These tapes might not have completed replicating to the
target Celerra. “AWSPRINT library utility” on page 117 provides
information about the utility.
2. Identify the last snapshot that was transferred successfully to the
target using the command processor CP504. The output contains
the last successful sync time for a particular file system.
3. Execute GENSTATS with the following options:
a. STILLINUSE
b. PATHNAME=“name of tape library”
VNX replication 127

DLm Replication
The Genstat report provides a list of VOLSERs that were being

trasferred to the destination at the time of the disaster event.
Note: The DATESTART parameter may be used to indicate the start of

the search.
An example of param usage in the JCL to generate such the

report:
STILLINUSE PATHNAME=tapelib/BB
The sample output:

STILLINUSE PATHNAME=tapelib/BB
--------------------------------------------------------------
VOLSERS STILL MOUNTED :
NODENAME DEVICE VOLSER LAST MOUNTED PATH

VTE1 VTE1-01 BB0161 2011/04/29 23:35:14 tapelib/BB
This list indicates the VOLSERs that has been lost due to the
disaster event and these jobs will need to be re-run.
contains more information about GENSTATS and command
processor CP504.
DR testing from a copy DR testing is performed without interrupting data replication

of production data between the DR and production sites by using a copy of the
production data. Disk arrays allow the creation of both read-write
snaps and instant read-only copies:
◆ Read-write snaps:
• Confirm operation at the DR site
• Require twice the storage capacity of SO
◆ Read-only copies:
• Confirm that the tapes can be mounted and all required data
can be accessed
• Require minimal incremental storage capacity
DLm Replication
Tape catalog considerations

Tape catalog management is no different for DLm than it is for offsite
storage; that is, catalogs can be written to an emulated tape and
replicated to allow data to be recovered. However, in environments
that replicate the catalogs synchronously with a DASD replication
solution, tape catalog management includes some special
considerations.
VNX replication 129

DLm Replication
Deduplication storage replication

Replication on deduplication storage is executed by the Data Domain
Replicator software available with DD890. The replication
environment is initially set up for you at installation by EMC service
personnel. To make changes or additions to your replication
environment, contact EMC Customer Support.
The Data Domain Replicator software includes different replication
policies that use different logical levels of the system for different
effects. In a DLm environment, the DD890 is configured to only use
directory replication, which offers maximum flexibility in replication
implementation. With directory replication, a directory
(sub-directory, and all files and directories below it) on a source
system is replicated to a destination directory on a different system.
Directory replication transfers deduplicated changes of any file or
subdirectory within a Data Domain filesystem directory that has been
configured as a replication source to a directory configured as a
replication target on a different system.
In DLm, the directory replication context is established at the
directory that corresponds to a virtual tape library. Hence, replication
cannot be enabled or disabled for individual VOLSER ranges. Data
Domain replication uses a proprietary protocol to transfer only the
data that is unique at the destination. Replication transfer for a file is
triggered by a file closing. In cases where closes are infrequent, DD
Replicator forces data transfer periodically. Once the complete file has
been established on the replica, it is made immediately visible to the
replica namespace and may be restored or copied at once. The replica
at the destination is set to read only. All transfers between the source
and the destination use the Diffie-Hellman key exchange. Data
Domain Replicator uses its own large checksum to verify the
accuracy of all sent data, in addition to the verification that TCP
provides.
Note: The two replication ports on the DD890 are configured in Failover
mode to protect against link failures. Failover is the only configuration that
DLm supports for the DD890 replication ports. No other configuration is
supported for these replication ports.
DLm Replication
Prerequisites for DD replication are:

◆ Data Domain Replicator licenses are installed in the source and
destination DLm systems.
◆ The software version on the destination VTE must be the same as
or higher than the software version on the source VTE.
◆ You have the IP addresses that are assigned to the source and
destination DD890 systems.
◆ Cat5 Ethernet cables are available for each DD890 system and all
required WAN switches/ports are configures end-to-end.
◆ Sufficient storage space is available in the source and destination
filesystems. At initial replication setup, EMC recommends that
you plan disk capacity based on a deduplication ratio of zero.
Supported configurations
The following configurations are supported:
◆ Unidirectional from a single source to a single destination
◆ Bidirectional between a single source and destination pair
Note: Data Domain replication is supported only when both the source and
target systems are DLm DD systems. Replication from a DD890 to a VNX is
not supported.
Replication session The requirements for the successful setup of a Data Domain directory
setup replication are:
◆ The destination system must be large enough to store all the data
replicated from the source.
◆ The network link bandwidth must be large enough to replicate
data to the destination.
◆ The fully qualified domain names FQDN for the source and the
destination DD890 systems must be registered in the DNS
servers.
If the hostname of the DD890 is DD-1, the FQDN, for example,
may be"DD-1.customer.com."
Deduplication storage replication 131

DLm Replication
◆ The replication context directory is defined after the directories

are created at both the source and the destination. EMC
recommends that you set up replication before the system
restores backups to the source directory. Erase all files from the
destination directory if it is not empty before the initialization of
a directory context.
◆ Replication initialization must be executed from the source.
Throttling As a basic form of quality of service (QoS), times of day during which
data may or may not be sent, along with limits to the amount of
bandwidth that can be used.
Note: Contact EMC Service if this needs to be configured. By default, no

throttling is set.
Recovery point In a Data Domain system, deduplication is fast and inline, and
replication can be simultaneous with backup, so it can finish shortly
after backup. The restore image is available immediately from the
replica. The recovery point is from the current snapshot before the
delay represented by the backup window.
Recovery time The replica contains only deduplicated data. The recovery time is the
same as the restore rate from the deduplication pool in the replica.
This should be measured carefully with a large dataset to ensure
sustained performance characteristics.
The Data Domain Replicator uses the directory replication feature to
support replication at the tape library level.
Disaster recovery in Data Domain systems

Disaster recovery for data stored on a Data Domain system is
performed on the entire tape library. The DD890 system reports a
parameter called the Sync'd as of time for each tape library being
replicated. This Sync'd as of time indicates the timestamp of the most
recently replicated data for a replication-enabled tape library. All data
that was written to VOLSERs in the source tape library before the
Sync'd as of time has been replicated and data received after the
Sync'd as of time is in the process of being replicated. For example, if
the Sync'd as of time for the replication context /backup/tapelibZZZ
DLm Replication
is reported as 23:35:00 on 04/29/2010, it indicates that all the data

written to the tape library tapelibZZZ, as of this time 23:35:00 on
04/29/2010 at the source, has been replicated. The data written after
this time, for example, 23:36:00 on 04/29/2010, is in the process of
being replicated.
In the case of a disaster, the VOLSERs in the tape library accessed
after the Sync'd as of time reported for that tape library is lost and
cannot be recovered. You can use the GENSTAT utility with the
SYNCTIME, DATESTART, DATEEND, and PATHNAME
parameters to identify the data that is not replicated. The EMC Disk
Library for mainframe Command Processors User Guide contains more
information about GENSTATS.
To identify the unreplicated data stored on a Data Domain system:
1. Execute the command processor CP603 with the status option for
each replication-enabled tape library that stores its data on a
DD890.
2. Note the Sync’d as of time for each replication-enabled tape
library on the DD890 system.
3. Execute the command processor 998 to gather statistics .
4. Execute GENSTATS with the following options:
a. STILLINUSE
b. SYNCTIME=hr:mm:sec (the Sync’d as of time)
c. DATESTART=yr:mm:dd (the date to start the search)
d. DATEEND=yr:mm:dd (the date of the Sync’d as of time for
this context)
e. PATHNAME="name of tapelibrary" (for example,
“tapelibZZZ”)
Note: If you run GENSTATS with the PATHNAME option, the report
lists VOLSERs in the tape library that correspond to the specified
pathname, the updates of which have not been replicated.
DATESTART and DATEEND define the DLm production time

period to report in the GENSTATS reports. If you do not specify a
time period, you may see extraneous or irrelevant tape mounts in
the STILLINUSE report.

DLm Replication

contains more information about GENSTATS, command processor
998, and CP603.
This GENSTATS report provides a list of VOLSERs that were
accessed after the Sync’d as of time and might not have completed
replicating the data to the target.
This is an example of how the parameter is used in the JCL:
STILLINUSE DATEEND=10/04/29 SYNCTIME=23:36:00 PATHNAME=tapelibZZZ/
This is the report generated:

VOLSERS MOUNTED AFTER SYNCTIME (10/04/29 23:36:00)
2010/04/29 23:46:36 S10162
2010/04/29 23:46:36 S20181
2010/04/29 23:46:36 S30161
2010/04/29 23:57:59 S10163
2010/04/29 23:57:59 S20182
2010/04/29 23:58:00 S30162
2010/04/30 00:09:25 S10164
2010/04/30 00:09:25 S20183
2010/04/30 00:09:25 S30163
2010/04/30 00:20:49 S10165
2010/04/30 00:20:49 S20184
2010/04/30 00:20:50 S30164
----------------------------------------------------------------------
VOLSERS STILL MOUNTED :
NODENAME DEVICE VOLSER LAST MOUNTED PATH

VTE1 VTE1-01 S10161 2010/04/29 23:35:14 tapelibZZZ/S1
The report provides two lists of VOLSERs:

◆ VOLSERs that were mounted at the Sync'd as of time (23:36:00 on
04/29/10 in this example)
◆ VOLSERs that were mounted after the Sync'd as of time
Directory replication flow

This is how DD890 directory replication works:
◆ The source Data Domain system continuously sends segment
references (metadata) to the destination Data Domain system.
DLm Replication
◆ Destination Data Domain replica filters them by looking up its

index to check which segments it doesn't already have. This
could impact replication performance due to the high
restore/backup load.
◆ The source periodically asks the replica which segments need to
be sent.
◆ The destination responds with list of segment references that it
does not have.
◆ The Source reads the requested segments from its filesystem and
sends them.
◆ Replication code picks up the logged close records from a queue
and begins replication. The maximum amount of time between a
write and when replication will start is one hour.
Replication logs the close of a modified file based on the
following considerations:
• 10 minutes after the last access, NFS closes the file.
• Every hour (by default), all files are closed regardless of how
recently they were written.
• If many files are being accessed or written, files may be closed
sooner.

DLm Replication
5
Mainframe Tasks
This chapter discusses using DLm with z/OS:

◆ Configure devices ............................................................................ 138
◆ Real 3480, 3490, or 3590 ................................................................... 139
◆ Manual tape library ......................................................................... 140
◆ MTL considerations for VTE drive selection ............................... 143
◆ MTL-related IBM maintenance ...................................................... 145
◆ EMC Unit Information Module ..................................................... 146
◆ Missing Interrupt Handler.............................................................. 148
◆ Mainframe configuration for deduplicated virtual tapes .......... 149
◆ Mainframe configuration for deduplicated virtual tapes .......... 149
◆ Dynamic device reconfiguration considerations......................... 149
◆ DFSMShsm considerations............................................................. 149
◆ Specify tape compaction ................................................................. 150
◆ Locate and upload the DLm utilities and JCL for z/OS ............ 151
◆ Initial program load from a DLm virtual tape............................. 162
Mainframe Tasks 137

Mainframe Tasks
Configure devices
z/OS uses the Hardware Configuration Definition (HCD) utility to
define devices on the system. HCD provides an interactive interface
that allows you to define the system's hardware configuration to both
the channel subsystem and the operating system.
The three alternatives for configuring DLm devices on the mainframe
are:
◆ Configure the devices as real 3480, 3490, or 3590 tape drives.
◆ Configure the devices as MTL devices.
◆ Configure the devices with a unique device type using the EMC
UIM.
These alternatives are discussed in the following sections. The
preferred approach is to configure the devices as MTL devices.
If you are planning to use DLm with IBM's Object Access Method
(OAM), you must configure the devices as MTL devices. OAM needs
tape drives to be SMS-managed and treats them on the host as a
single tape library. The IBM document SC35-0427, DFSMS Object
Access Method Planning, Installation, and Storage Administration Guide
for Tape Libraries provides more information on using a library for
OAM object.
Mainframe Tasks
Real 3480, 3490, or 3590

DLm can emulate 3480, 3490, or 3590 tape drives. If your mainframe
installation does not have one of these device types installed, you can
select the particular device type to be installed. The advantage of
using 3480, 3490, or 3590 device types is that some applications or
access methods examine device types to make sure that they are
writing or reading to a known tape device. These applications
typically do not work with the EMC UIM.
However, if you have real 3480, 3490, and 3590 tape drives configured
in your system, do not attempt to define the DLm devices in this
manner. Configuring the devices as a device type that is already
present results in misallocation errors because z/OS requests a real
3480, 3490, or 3590 cartridge on a device or requests a tape-on-disk
volume on a real 3480, 3490, or 3590.
If you need to use one of these device types to define the DLm
devices, make sure that the tapes configured in your installation do
not include this device type. For example, if your JCL is using TAPE
(UNIT=TAPE), make sure that TAPE does not include the device type
(3480, 3490, or 3590) that you are using to define the DLm devices.
Real 3480, 3490, or 3590 139

Mainframe Tasks
Manual tape library

If you have installed 3480, 3490, and 3590 tape drives, you cannot
define the DLm devices as real tape drives. Doing so results in
misallocation errors as described previously. If you plan to use the
DLm devices with OAM or any application that verifies device type,
you cannot use the EMC UIM. In this case, you must define your
DLm devices as real 3490 or 3590 tape drives and include them in an
MTL, so that they are not misallocated.
IBM introduced the concept of an MTL with APAR OW45271. This
APAR allows stand-alone tape drives and their associated volumes to
be SMS-managed by treating a group of such drives as a logical tape
library. SMS manages allocations to such a logical library just as it
would any automated tape library dataserver (ATLDS), with the
exception that mount messages are routed to a tape operator console
rather than the ATLDS robotics. The IBM document DFSMS Object
Access Method Planning, Installation, and Storage Administration Guide
for Tape Libraries (SC35-0427) provides information about MTL
support.
To define DLm devices with HCD:
1. Configure the DLm devices as either 3490 or 3590 tape devices
using HCD.
Note: This does not require the use of the EMC UIM; use the standard
HCD 3490 or 3590 definitions.
2. On the Device/Parameter Feature definition screen for each

drive, choose YES for MTL and supply an artificial LIBRARY-ID
and LIBPORT-ID.
3. Define the control unit as a 3490 or 3590 with 16 tape drives
available.
4. Be sure that all the devices in the same logical library have the
same LIBRARY-ID, with each group of 16 devices having a
unique LIBPORT-ID.
IBM requires that there be only 16 tape drives to a LIBPORT-ID.
As a result, you must configure multiple control units on the
same channel using different logical control unit addresses when
you want to configure more than 16 drives.
Mainframe Tasks
5. Make sure that each control unit's devices have the same
LIBRARY-ID, but a unique LIBPORT-ID per control unit.
Table 7 on page 141 contains an example of having the same
LIBRARY-ID with its unique LIBPORT-IDs.
Table 7 Example of LIBRARY-ID and LIBPORT-ID
Dev Add CU Log CU LIBRARY-ID LIBPORT-ID
E800 CU800 00 12345 01
E801 CU800 00 12345 01
E80F CU800 00 12345 01
E810 CU810 01 12345 02
E811 CU810 01 12345 02
E81F CU810 01 12345 02
After defining DLm using HCD, it must be defined to SMS using the
library management function. Then your ACS routines must be
updated to allow jobs to select the new library with appropriate user
defined ACS management, data, and storage classes and groups. For
example, if you define a new esoteric called VTAPE, your ACS
routines could allocate the dataset to the SMS storage group using the
DLm MTL whenever UNIT=VTAPE is specified in JCL.
The characteristics of DLm virtual tape cartridges match the SMS
Media Type: "MEDIA2" for 3490 or "MEDIA4" for 3590. Make sure
that you specify the appropriate media type (MEDIA2 or MEDIA4)
on the Library Definition screen. In addition, since SMS requests
scratch tapes using media type, you must add MEDIA2 or MEDIA4
to the list of DLm scratch name synonyms as explained in “Scratch
synonyms” on page 96. Z/OS might request for mounts by media
type based upon the DATACLAS definition. The customer's ACS
routines or tape display exits may also change the mount request to
use storage group names, LPAR names, pool names etc. All such
names must be entered into the synonym list.
Manual tape library 141

Mainframe Tasks
Note: After you configure the MTL, it is treated as a real library; that is, you
must enter cartridges into the library before DLm can use them. Use the
DLMLIB utility to enter cartridges into the MTL.
Before using the DLMLIB utility, contact your specific tape management
system vendor for their customizations that interface with IBM's MTL.
You must execute DLMLIB out of an authorized library. EMC

provides an example of the JCL required for linking DLMLIB. The
sample JCL file is found in the LNKLIB member of
DLMZOS.JCL.CNTL. Step 4 on page 152 provides download
instructions.
EMC also provides an example of the JCL required to run DLMLIB.
The sample JCL file is found in the RUNLIB member of
instructions.
The log file lists the result of each cartridge entry request, including
any error codes. The utility invokes IBM's LCS External Services
(CBRXLCS) macro.
Return codes and reason codes can be found in the chapter “OAM
Diagnostic Aids,” of DFSMSdfp Diagnosis (GY27-7618).
Mainframe Tasks
MTL considerations for VTE drive selection

When a request is made for a tape drive defined in an MTL, the ACS
routines select the appropriate tape storage group for the library.
Allocation subsequently chooses any available drive in that library.
This is not a problem if only one VTE is defined as part of the library.
However, an MTL can span multiple VTEs for performance and
failover considerations. In this case, targeting a specific VTE for batch
utilities is required.
Note: MTL devices do not support the demand allocation (UNIT=xxxx)

method, which selects a specific drive on a particular VTE, thereby enabling a
batch utility to communicate with that VTE.
Use one of these methods to enable a batch utility to communicate

with a specific VTE in an MTL defined with multiple VTEs:
◆ Omit a single drive from the MTL in each VTE's device group.
For example, consider an MTL defined with two VTEs, each
configured with 64 devices:
a. In each VTE, define 63 devices as MTL=YES in the HCD. One
device would be MTL=NO in the HCD.
b. Subsequently, use demand allocation in JCL to select the
specific drive address that is outside the MTL.
EMC recommends that you leave this drive offline to prevent
inadvertent allocation by other jobs. One way to accomplish this
is to bookend your jobs with steps to vary the device online and
offline with an operator command utility program.
The DLMCMD, DLMSCR, and GENSTATS batch utility
programs now support the use of the EXEC statement parameter
DEV=xxxx, which allows access to an offline tape device.
Type the code as follows:
EXEC PGM=DLMCMD,PARM='DEV=xxxx'
where xxxx is the offline virtual tape device on the VTE you wish
to access.
For DLMCMD and DLMSCR steps, this parameter eliminates
the need to code a DLMCTRL DD statement.
MTL considerations for VTE drive selection 143

Mainframe Tasks
For GENSTATS, this parameter eliminates the need to code a

GENIN DD statement.
◆ Define a separate MTL for each VTE to enable VTE selection:
a. Similar to the previous method, define only 63 devices on each
VTE as part of the same MTL.
b. For each VTE, define a separate MTL (different LIB-ID) for the
remaining device, as well as a new esoteric.
c. Use ACS routines to select the appropriate library that limits
the available drive selection to that one drive.
Mainframe Tasks
MTL-related IBM maintenance

The program temporary fix (PTF) for each of the following APARs
must be applied when using DLm in an MTL environment:
◆ APAR OA03749 — More than one device fails to vary online.
◆ APAR OA06698 — Replacement tape drives get MSG IEA437I in
an MTL environment.
◆ APAR OA07945 — Mount hangs or times out using MTL with
OEM Automated Library.
◆ APAR OA08963 — Tape volume capacity is incorrect for OAM
object support users.
◆ APAR OA10482 — MTL scratch volume mount error occurs.
MTL-related IBM maintenance 145

Mainframe Tasks
EMC Unit Information Module

As an alternative to defining real 3480s, 3490s, or 3590s or using an
MTL, EMC provides a user UIM that allows DLm tape devices to be
configured to HCD using a unique device type. Using the EMC UIM
prevents the operating system from allocating the DLm virtual tape
drives to jobs requesting a mount of a real tape cartridge. If you are
not using OAM or an application that checks device types, the EMC
UIM is the easiest way to configure the DLm devices, so that no
misallocation errors occur with real tape drives. Information
regarding user UIM can be found in IBM's document, z/OS MVS
Device Validation Support (SA22-7586-0).
You must install the EMC UIM and associated Unit Data Table (UDT)
into SYS1.NUCLEUS before you configure the DLm devices in HCD.
Before you install the UIM, it is important to back up the SYSRES
volume containing the SYS1.NUCLEUS dataset to provide a recovery
mechanism if anything fails to operate properly.
Use ISPF function 3.3 (Utilities: Move or Copy) and copy CBDEC255
and CBDUC255 from DLMZOS.PGMS into SYS1.NUCLEUS, as
explained in “Locate and upload the DLm utilities and JCL for z/OS”
on page 151.
If CBDEC255 or CBDUC255 already exists in SYS1.NUCLEUS, then
another vendor has already supplied a user UIM using the same user
device number of 255. Contact EMC Customer Support for a different
module name to use.
After installing the UIM, you can configure the DLm devices in HCD.
The UIM provides the following:
◆ Four control unit types: V3480, V3481, V3482, and V3483
◆ Four supporting device types: V3480, V3481, V3482, and V3483
The generic names for these devices are also V3480, V3481, V3482,
and V3483. If you have already defined a generic name of V348x,
contact EMC for support. You must define multiple virtual device
types to support the multiple DLm systems or a single DLm with
multiple virtual tape libraries configured.
Mainframe Tasks
You must define a V348x tape drive for each virtual tape device that
you have configured in DLm. All virtual tape drives assigned to the
default virtual tape library in the DLm filing structure (/tapelib) are
normally defined with the same generic name (for example, V3480).
If you plan to have a drive assigned to a different tape library path in
the DLm filing structure, you should define that drive with a separate
generic name (for example, V3481).
Once the DLm device definitions are active, you must either specify
UNIT=V348x or hard code the unit address allocated to a device. In
this way, regular jobs that call for real tape drives or use tapes
previously cataloged on real 3480s are not allocated to the DLm
devices. After a tape is cataloged as created on a V348x device, it is
allocated to that same device type when called again. Conversely, a
tape cataloged as created on a real tape drive is not allocated to a
device.
EMC Unit Information Module 147

Mainframe Tasks
Missing Interrupt Handler

The MVS, OS/390, or z/OS Missing Interrupt Handler (MIH) timer
value is often set too low for the lengthy operations that can occur on
a large tape cartridge. If an operation takes longer than the MIH
value, the operating system reports I/O errors and often boxes the
device, taking it out of service. For this reason, IBM recommends a
minimum MIH timer value of 20 minutes for tape drives, including
virtual tape drives such as those on DLm.
DLm reports a preferred MIH timer value of 3000 seconds (50
minutes) to the host when it is varied online, and the host should take
this value as the DLm devices' MIH time.
To determine the current MIH timer value, you can use the following
z/OS operator command:
D IOS,MIH,DEV=xxxx
where xxxx is any DLm virtual tape drive address.

You can temporarily change the MIH value for DLm devices by
typing the following z/OS operator command:
SETIOS MIH,DEV=(xxxx-xxxx),TIME=mm:ss
where xxxx-xxxx is the range of DLm virtual tape drive addresses.

The IBM manual, 3490 Magnetic Tape Subsystem Introduction and
Planning Guide (GA32-0297), provides more information about the
MIH timer and tape drives.
Mainframe Tasks
Mainframe configuration for deduplicated virtual tapes

The deduplicated virtual tapes/VOLSERs need to be isolated from
non-deduplicated virtual tapes. All VOLSERs that reside on the Data
Domain DD890 are deduplicated and all VOLSERs that reside on the
VNX are non-deduplicated. This can be done by defining an MTL
that contains only deduplicated virtual tapes/VOLSERs. Update
your ACS routines so that you can direct specific VOLSERs to the
MTL supporting deduplication.
Dynamic device reconfiguration considerations

Since DLm is a virtual tape control unit, it cannot benefit from an
operator or a system-initiated 'swap' function. Accordingly, following
any message 'IGF500I SWAP xxxx TO xxxx - I/O ERROR' for any
device, you must reply NO to the subsequent "## IGF500D REPLY
'YES', DEVICE, OR 'NO' ."
If you configured the devices as V348x devices using the UIM,
Dynamic Device Reconfiguration (DDR) swap is automatically
disabled for those devices, and a swap cannot occur.
DFSMShsm considerations
If you plan to use DLm with HSM, the various SETSYS tape
parameters do not accept V348x generic names as valid. In that case,
it is necessary to define esoteric names that are unique to the various
V348x devices.
To identify esoteric tape unit names to DFSMShsm, you must first
define these esoteric tape unit names to z/OS during system I/O
generation (HCD). Then, you must include the esoteric tape unit
names in a DFSMShsm SETSYS USERUNITTABLE command.
Only after they have been successfully specified with the SETSYS
USERUNITTABLE command are they recognized and used as valid
unit names with subsequent DFSMShsm commands.
Mainframe configuration for deduplicated virtual tapes 149

Mainframe Tasks
Specify tape compaction

Compaction of the virtual tape data under z/OS is initiated like it is
initiated for a real compression-capable (IDRC) 3480/3490/3590E.
The default is NOCOMP for 3480, and COMP for 3490 and 3590E.
You can specify the use of compaction in the JCL by using the
DCB=TRTCH=COMP or DCB=TRTCH=NOCOMP parameter on the
appropriate DD cards for output tapes. No JCL parameter is required
for input tapes. The system automatically decompresses the tape data
on read requests.
Alternatively, the system programmer can specify the
COMPACT=YES parameter in the DEVSUPxx PARMLIB member.
This would result in compaction being the default option for all of the
virtual drives. The COMPACTION=Y/N option on the SMS
DATACLAS definition provides another method for activating and
disabling compaction.
It should be noted that while the compaction option significantly
reduces the amount of storage required on the DLm library, there is
some impact on the data transfer performance compared to
uncompressed data. The efficiency of the compaction, as well as the
performance impact, varies depending upon the data.
The file-size values reported by the QUERY command and the
awsprint utility (using CP503), reflect the compressed data size and
not the original uncompressed size.
Note: All data written to the deduplicating storage on the DD890 should be
written without IDRC.
Mainframe Tasks
Locate and upload the DLm utilities and JCL for z/OS
EMC provides a set of utilities and a UIM for the z/OS environments.
The utilities are:
◆ GENSTATS — A utility that generates reports from VTE and
VOLSER range statistics
◆ DLMSCR — A scratch utility that sends VOLSER scratch
requests to DLm
◆ DLMCMD — A utility that allows the mainframe to send DLm
commands
◆ DLMLIB — A utility that is required to define scratch volumes on
an MTL
◆ DLMVER — A utility that reports the versions of all the DLm
mainframe utilities on the mainframe and the z/OS release.
◆ DLMHOST — A host utility that provides z/OS Console
Operation support. Chapter 7, “z/OS Console Support,” provides
details about this utility.
Downloading and To use any of these utilities, or the UIM:

using the DLm 1. Download the file DLMZOS-<version number>.XMI from the
utilities and JCL for EMC support website (http://Powerlink.EMC.com). Select
z/OS Navigator > Disk Library Tools and transfer the file to the
mainframe as follows:
ftp target_system_name
(satisfy login requirements of the mainframe)
quote site recfm=fb lrecl=80

bin
put DLMZOS-<version number>.xmi
(the file will be placed on the host as

'uid.DLMZOS-<version number>.xmi', where uid is the
login user id used for the ftp. Alternatively, you may
use put DLMZOS-<version number>.xmi 'filename' to force
a specific filename of your choice.)
quit
2. After transferring the file, use ISPF function 6 (Command Shell)

and type:
Locate and upload the DLm utilities and JCL for z/OS 151
Mainframe Tasks
receive indataset('uid.dlmzos.xmi')
3. At the prompt, Enter restore parameters or delete or end, type:

da('DLMZOS.PGMS')
DLMZOS.PGMS is created for the following members:

• CBDEC255 — The unit data table for the UIM
• CBDUC255 — The UIM for the EMC DLm devices
• DLMLIB — The utility required to add volumes to a DLm
MTL
• DLMSCR — The DLm scratch utility
• DLMCMD — The DLm command utility
• DLMVER — The DLm utility version reporting utility
• GENSTATS — The report formatting utility
4. Transfer the DLMZOS.JCL file to the host.

The DLMZOS.JCL file contains a sample JCL to link and execute
these batch utilities. The file is available at the EMC support
website: http://Powerlink.EMC.com. Select Navigator > Disk
Library Tools. To transfer the file, type:
ftp target_system_name
(satisfy login requirements of the mainframe)
quote site recfm=fb lrecl=80

bin
put DLMZOS.jcl
(the file will be placed on the host as

'uid.DLMZOS.jcl', where uid is the login user
id used for the ftp. Alternatively, you may use
put DLMZOS.jcl 'filename' to force a specific
filename of your choice.)
quit
5. After transferring the file, use ISPF function 6 (Command Shell)

and type:
receive indataset('uid.dlmzos.jcl')
6. At the prompt, Enter restore parameters or delete or end, type:

da('DLMZOS.JCL.CNTL')
DLMZOS.JCL.CNTL will then be populated with the sample JCL.

See member $INDEX for a list of its contents.
Mainframe Tasks
GENSTATS utility The GENSTATS utility generates reports on the tape mount and
unmount statistics logged at the VTE level and at the VOLSER range
level. It can selectively present:
◆ Daily and hourly throughput numbers
◆ Mount rates
◆ Concurrent tape drive usage details
◆ Compression ratio
◆ Average and slow mount response information
GENSTATS uses command processors, such as CP998 and CP999, to
summarize virtual tape activity. A GENSTATS job consists of two
steps:
1. Execute a command processor which accesses the appropriate
statistics file and writes the data to a non-labeled tape file.
2. Run GENSTATS to generate a report from the non-labeled tape
file data.
contains more information about GENSTATS. It includes samples of
JCL for GENSTATS, which show how GENSTATS uses CP998 and
CP999 to generate reports. These sample jobs access VTE and
VOLSER range statistics and make the data available on the
mainframe.
DLm scratch utility program

DLm provides the DLMSCR utility that you can use with any of the
major tape management systems to keep your TMS scratch status
synchronized with the DLm scratch status.
You must link the DLMSCR utility as an authorized program into an
authorized library under the name DLMSCR. EMC recommends that
you use security software, such as Resource Access Control Facility
(RACF), to restrict the use of DLMSCR to authorized users only.
EMC provides an example of the JCL required to link DLMSCR. The
sample JCL file is found in the LNKSCR member of
instructions.
Mainframe Tasks
DLMSCR runs on the mainframe and sends volume scratch requests

to DLm. As the TMS may dynamically release tapes back to scratch
status, you must periodically run DLMSCR to maintain
synchronization between the TMS catalog and DLm. To use
DLMSCR, you must run a TMS scratch report and input that scratch
report into DLMSCR. DLMSCR scans the scratch report for the
DLm-owned volumes and sends the appropriate scratch requests to
DLm.
EMC provides an example of the JCL required to run DLMSCR. The
sample JCL is found in the RUNSCRA and RUNSCRB members of
DLMZOS.JCL.CNTL. RUNSCRB illustrates the use of the DEV=
parameter. Step 4 on page 152 provides download instructions.
Table 8 on page 154 lists the DLMSCR parameters that may need to
be specified.
Table 8 Parameters in DLMSCR (page 1 of 2)
Parameters Specification
TYPE=x Where x is used to select the tape management system. Valid types include RMM, TLMS,
TMS, TSM, ZARA, CTLM, AFM, or CTLT. This is the only required parameter.
PREFIX=y Where y is a string of prefix characters that limits processing to volumes whose VOLSER
begins with the characters specified. Unless otherwise specified by the PREFIXLN
parameter, the default prefix length is 2.
PREFIX=AAABAC would cause DLMSCR to process only volumes whose serial numbers
begin with AA, AB, or AC. Coding this parameter prevents DLMSCR from trying to
unnecessarily scratch volumes that are not stored on DLm. If no PREFIX is specified,
DLMSCR processes the entire scratch list.
PREFIXLN=n Where n can be a single digit between 1 and 5. This value replaces the default prefix length
of 2 for the PREFIX= parameter.
PARM='PREFIX=ABCD,PREFIXLN=1' causes DLMSCR to process only volumes whose
serial numbers begin with A, B, C, or D.
NODSNCHK DLm normally validates dataset names (dsname) if found in the scratch report as part of the
scratch process. A scratch is not successfully completed if the dsname in the scratch report
does not match the dsname in the HDR1 label on the volume being scratched. NODSNCHK
prevents the data set name check from being performed and is not recommended for
normal use.
Mainframe Tasks
Table 8 Parameters in DLMSCR (page 2 of 2)
Parameters Specification
FREESPACE By default, DLMSCR reclassifies volumes being scratched as eligible for scratch allocation
requests, without freeing the space occupied by that volume. The FREESPACE parameter
may be used to request that the space be freed.
Note: FREESPACE requires the volumes to already be in scratch status. Therefore to

immediately free the space, DLMSCR must be run twice. The first execution must run
without the FREESPACE parameter to scratch the volumes, and the second execution must
run with the FREESPACE parameter to release the space.
Keep in mind that DLm automatically frees the space of scratched volumes when it needs
space. So, it is generally not necessary to run DLMSCR with the FREESPACE parameter.
FREEAFTER While the FREESPACE parameter requires that a volume already be in a scratched state,
SCR FREEAFTERSCR frees space from a volume immediately after DLMSCR has scratched it.
Note: Once FREEAFTERSCR frees the space associated with the execution ofDLMSCR,
the volume cannot be recovered if it was scratched by mistake.
NODATECHK DLm normally checks the creation date of a tape volume and does not allow any volume to
be created and scratched in the same 24-hour period. Setting this parameter allows
volumes to be created and scratched on the same day. This parameter ignores the default
date check in DLMSCR.
IGNLCSERR This parameter ignores any errors reported by Library Call Subsystem (LCS) used by OAM
with the MTL volumes. Normally, DLMSCR logs any error returned by LCS and stops
processing scratch tapes when these errors occur. If this parameter is set, DLMSCR scratch
processing continues even when the LCS errors are encountered.
ALLVOLS This parameter allows scratch of volumes with dsnames of all zeros.
IGNLCSRC4 This allows DLMSCR processing to continue after receiving a return code of 4 from LCS
processing, but terminates if the return code from LCS processing is greater than 4.
NOTCDB This prevents DLMSCR from attempting any TCDB updates. This should be used only if the
TMS already performs this function.
NOTIFSCR This prevents DLMSCR from attempting to change the TCDB use attribute to scratch if DLm
reports that the VOLSER was already scratched.
TEST This parameter allows for testing—no actual changes will be performed.
DEV=xxxx This allows the specification of an offline virtual tape device and the elimination of the
DLMCTRL DD statement as shown on page 143.
Mainframe Tasks
Scratch utility output files

The two scratch utility output files are:
◆ The DLMLOG file maintains a history of the results of each delete
request. The file should have a logical record length (LRECL) of
133.
If an error occurs during a scratch request (such as scratching a
non-existent volume), the failure is recorded in the log file. The
program continues with the next scratch request and result in a
non-zero return code from the program execution.
◆ The DLMCTRL file allocates a DLm tape device for use as a
control path to pass the scratch requests. If multiple tape libraries
in the DLm filing structure are being used to contain the DLm
virtual volumes, you must select a tape device address associated
with the library in the DLm filing structure containing the
volumes to be scratched.
◆ The DEV=xxxx parameter allows an offline tape device to be used
instead of coding the DLMCTRL DD statement. For example, see
RUNSCRB in the sample JCL library.
Working with the DLm scratch utility

Note these considerations when working with the DLm scratch
utility:
◆ The DLMSCR file must point to the scratch report that you have
created using the appropriate TMS utility. Generate the scratch
report with a logical record length (LRECL) of 133.
◆ To avoid any confusion, use a single job to generate a current
scratch list file and run the DLMSCR utility against that file. This
eliminates the possibility of accidentally running the DLMSCR
program against an old scratch report and causing the TMS and
DLm to be out of sync.
◆ If the extract file creation time and the time that the report was
processed are different, DLm does not scratch a volume created
on the current day.
Also, the utility does not run against a scratch report that was not
created the same day.
◆ The Scratch utility uses the dsname information from the scratch
report to verify the volumes being scratched. If the dsname
written in the volume header does not match the dsname on the
scratch report for that volume, the scratch request is rejected.
Mainframe Tasks
◆ After completing the DLMSCR utility, you can use or reuse tapes
that the utility successfully scratched.
RMM considerations
Observe the following rules when using DLm with RMM:
◆ Predefine the DLm scratch volumes to RMM. If you have not
predefined DLm VOLSERs as scratch in RMM, RMM rejects the
new volumes, which results in an unsatisfied mount request on
the mainframe. To resolve the unsatisfied mount, define the DLm
scratches in RMM, and execute a LOAD command at the
appropriate VT console to satisfy a stalled request.
◆ When defining a new DLm scratch tape to RMM, set the initialize
option to no. If you select yes and RMM detects that the volume
must be initialized (or EDGINERS is run), RMM sends a request
to mount a 'blank' VOLSER on a DLm device. DLm is not
automatically ready as it cannot recognize which volume to
mount. Consequently, you must use the LOAD command at the
VT console to manually mount each volume being initialized.
◆ DLMSCR processes two types of RMM scratch reports:
• The scratch report that EGDRPTD creates
• The scratch report that EDGJRPT creates using the
EDGRRPTE exec (EDGRPT01)
Use the DATEFORM(I) parameter when running EDGRPTD to
create scratch reports to ensure the expected date format is used.
When the REXX exec form is used, DLMSCR may not accept a
user-tailored version of EDGRRPTE.
TMS considerations
DLMSCR expects Report-05, Report-06, or Report-87 to be used.
TLMS considerations
DLMSCR expects either the TLMS003 or the TLMS043 report as
input.
TSM considerations
DLMSCR expects a Tivoli Storage Manager (TSM) Volume History
Report to be used as input to the DLMSCR DD.
Mainframe Tasks
ZARA considerations
DLMSCR expects the LIST SCRATCH type of scratch report to be
used as input from ZARA.
DLMCMD utility program

The DLMCMD utility allows you to execute DLm commands from
the mainframe. You must link this utility as an authorized program to
an authorized library under the name DLMCMD. EMC highly
recommends that you use security software, such as RACF, to restrict
the use of DLMCMD to authorized users only.
EMC provides an example of the JCL required to run DLMCMD. The
sample JCL is found in the RUNCMDA and RUNCMDB members
of DLMZOS.JCL.CNTL. RUNCMDB illustrates the use of the DEV=
parameter. Step 4 on page 152 provides download instructions.
How the DLm command utility works:
◆ The DLMCMD utility reads one or more DLm commands from
the DLMCMD input file, and sends each command to DLm for
execution.
Note: The DLMCMD utility accepts input cards up to 256 characters in

length. Continuation lines are not allowed.
Indication of success or failure is logged to the file that the

DLMLOG DD statement points to.
Note: Any messages and other textual results of the command that
display on the DLm Console are not returned to the host.
DLMCMD does not respond to a mainframe command on the

communication tape device until the VTE processing for that
command is complete.
◆ Use the DLMCTRL file to allocate a DLm device for use as a
control path for passing the DLm commands. You can use any
available DLm virtual tape device as the DLMCTRL device.
“MTL considerations for VTE drive selection” on page 143
provides information about working with a Manual Tape Library.
The DEV=xxxx parameter allows an offline tape device to be used
instead of coding the DLMCTRL DD statement. See RUNCMDB
in the sample JCL library for an example.
Mainframe Tasks
◆ The DLMCMD DD statement should point to a list of DLm

commands to be sent. The LRECL of DLMCMD cannot exceed
256. If possible, create it using the NONUM ISPF edit option to
avoid sequence numbers at the end of the command line. This can
optionally be an in-stream input file (DLMCMD DD *) of
commands.
◆ The DLMLOG DD statement points to a sequential file for
logging the DLMCMD results. This file should have a logical
record length (LRECL) of 133. If an error occurs during command
processing, the failure is recorded in the log file, and a non-zero
return code from DLMCMD results. Table 9 on page 159 lists the
possible error codes from DLMCMD.
Table 9 Error code from DLMCMD
Error code Description
0x01 Invalid data length (must be between 1 and 256 bytes).
0x02 DLm does not accept Host-initiated console commands.
Note: This error code is generated when the HOSTCOMMAND option is set to
NO in the xmap file. To enable it, you must manually modify the xmap file.
0xFF(-1) A general syntax error occurred.

(The DLm console error message "DLM891E: Invalid command syntax" was
displayed.)
0xFC (-4) An "E" level error other than general syntax error occurred.
(A console error message other than DLM891E was displayed.)
This is a sample DLMLOG output:

DLMCMD VER 1.0 DLMCTRL = EA82
2004/09/10 12:47:49 CMD ERR=FF: this is an invalid command
2004/09/10 12:47:49 CMD ISSUED: q all
2004/09/10 12:47:49 CMD ERR=FC: q xxxxxxxx
2004/09/10 12:47:49 CMD ISSUED: set size=2g dev=EA80
The two optional methods to pass commands to DLMCMD:

1. Use of PARM='WTOR' — Sends the message DLm070I, ENTER
DLm COMMAND, to the operator, who can reply with the
command. The message is reissued after each command is
accepted until END is entered as the reply. This method does not
use the DLMCMD input file.
Mainframe Tasks
For example:
//LOG EXEC PGM=DLMCMD,PARM='WTOR'
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=V3480,VOL=SER=BT9999,
DISP=(,KEEP)
2. Use of PARM='CMD=' — Allows you to pass a single command

on the EXEC card instead of using the DLMCMD input file. This
method also allows you to call DLMCMD from another program,
and pass the command as an entry parameter. For example:
//LOG EXEC PGM=DLMCMD,PARM='CMD=Q SPACE'
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=V3480,VOL=SER=BT9999,
DISP=(,KEEP)
Note: If you experience issues with the DLMCMD, check the

/var/log/messages file for error messages.
DLMVER utility program

The DLMVER utility reports the versions of:
◆ The DLm mainframe modules on the mainframe:
• DLMCMD
• DLMLIB
• DLMSCR
• DLMVER
• GENSTATS
◆ The z/OS
The following are sample JCL for using DLMVER:
◆ Sample 1:
//S1 EXEC PGM=DLMVER,PARM=’WTO’
◆ Sample 2:
//S1 EXEC PGM=DLMVER
//DLMLOG DD DSN=logfile,DISP=SHR
A sample JCL file is also found in DLMZOS.JCL.CNTL. Step 4 on

page 152 provides download instructions.
Mainframe Tasks
A DLMVER sample output:

DLV010I UTILITY VERSIONS (Z/OS R9 ):
DLMCMD V 4.03
DLMLIB V 4.10
DLMSCR V 4.13
DLMVER V 1.00
GENSTATS V 1.13
The messages related to DLMVER are:

◆ DLV010I UTILITY VERSIONS ( ):
◆ DLV050I LOG FILE FAILED TO OPEN
“DLMVER messages” on page 373 provides the details.
Mainframe Tasks
Initial program load from a DLm virtual tape

Since the DLm virtual tape drives appear to the host as real tape
drives, it is possible to initiate an initial program load (IPL) on a
mainframe host from a virtual tape volume on DLm.
Create a stand-alone IPL tape on DLm

To create a stand-alone IPL tape:
1. On the DLm Console, initialize a non-labeled tape on DLm. For
example:
init vol=SAIPL label=nl dev=E980 scratch=no
The example creates a non-labeled tape called SAIPL in the tape

library assigned to the virtual tape drive named E980. You may
use any VOLSER of your choice. Replace E980 with the name of a
virtual tape drive configured on your DLm. Specify the
"scratch=no" parameter so that that no scratch tape mount request
can acquire the volume before you are ready to use it.
2. On the DLm Console, manually mount this tape on any virtual
tape drive assigned to the tape library where you initialized your
stand-alone IPL tape volume:
load SAIPL E980
This command causes the virtual tape volume SAIPL to be

mounted on the DLm virtual tape drive, E980. In your scenario,
replace E980 with the name of a virtual tape drive configured on
your DLm. It can be any DLm virtual tape drive that is assigned
to the tape library where the stand-alone IPL tape volume resides.
3. From the mainframe, write the stand-alone IPL tape to the virtual
tape drive where the target tape is mounted. Explicitly specify the
VOLSER you mounted in the previous step.
Once the stand-alone IPL tape has been created, it is ready to use.
Mainframe Tasks
IPL from the stand-alone IPL tape

On the DLm console, manually mount the stand-alone IPL tape on
any virtual tape drive assigned to the tape library where the tape
resides:
load SAIPL E980
This command causes the virtual tape volume SAIPL to be mounted

on DLm virtual tape drive, E980. In your scenario, replace E980 with
the name of a virtual tape drive configured on your DLm. It can be
any DLm virtual tape drive that is assigned to the tape library where
the stand-alone IPL tape volume resides.
On the mainframe console, select as IPL device the DLm virtual tape
drive where the stand-alone IPL tape is mounted, and perform the
IPL.
The mainframe will perform the IPL from the stand-alone IPL tape
mounted on DLm.
IPL condsiderations for DLm

The considerations for initiating an IPL on a mainframe host from
DLm are:
◆ Stand-alone restore programs might not send a Load Display
Mount message, which causes DLm to automatically mount the
desired volume. If you use a stand-alone program to restore
volumes that reside on the DLm system, you might have to
perform a manual Load command on DLm for each of the
volumes requested.
◆ If you need to initiate IPL a second time from the stand-alone IPL
tape, first make sure that the tape is rewound to loadpoint. To do
this, enter the Unready and Rewind commands at the VT
console.
◆ Tapes on which stand-alone programs exist typically are not
automatically unloaded. You may need to manually execute the
Unready and Unload commands at the DLm console to unload
the stand-alone IPL tape when you are done.
Initial program load from a DLm virtual tape 163

Mainframe Tasks
6
Using DLm with Unisys
DLm systems with FICON interfaces installed can connect to Unisys

2200 mainframes running OS-2200. This chapter discusses issues
unique to DLm support for Unisys mainframes.
◆ Unique DLm operations for Unisys mainframes ........................ 166
◆ Configuring for Unisys ................................................................... 168
◆ Initializing tapes for Unisys............................................................ 170
◆ Configuring the mainframe for DLm............................................ 171
Using DLm with Unisys 165

Unique DLm operations for Unisys mainframes

This section describes the unique DLm operations required for
Unisys mainframe systems.
Autodetection DLm automatically detects that it is attached to a Unisys host when it

receives a Load Display command containing data that is unique to a
Unisys mainframe. When this occurs, a message is displayed on the
DLm console ("DLm080I: Device devicename UNISYS detected").
You can confirm that DLm has recognized that a drive is attached to a
Unisys mainframe by reviewing the messages displayed on the DLm
console or by running a QUERY CONFIG command.
Load displays Unisys does not send the 'M' mount message sent by the z/OS
mainframe systems. DLm determines a Unisys mount request by the
FCB byte containing x'48', and then moves the VOLSER from the 1st
position into the 2nd position of the mount message and inserts an
'M' into the 1st position to form a standard mount message.
Mount "Ready" The Unisys mainframe does not expect a Not-Ready-to-Ready

interrupt interrupt when the DLm device comes ready. After sending the Load
Display, the Unisys mainframe performs repetitive senses to detect
when the device is ready. To accommodate the way Unisys
mainframe works, DLm does not send an interrupt when a mount is
initiated by a Load Display like it normally does. However, it sends
an interrupt when a manual mount is performed at the DLm console,
and when a manual Not-Ready-to-Ready transition is performed.
Query Config The DLm QUERY CONFIG command displays an additional

command parameter, HOST=UNISYS, for a device that has been determined to
be attached to a Unisys mainframe.
Ring-Out Mount The Unisys Load Display mount request uses the 8th position of the
request mount message as a file protect indicator. If that position contains the
character 'F', the Unisys mainframe expects to have the tape mounted
"ring-out" (read-only). DLm honors the 'F' indicator and mounts the
requested volume in read-only mode.
Scratch request When a Unisys host asks for a scratch tape, DLm ignores the label
type (either explicitly requested in the mount request or implied by
the LABEL=x configuration parameter) and picks any available
scratch tape. This behavior is applicable only to Unisys-attached
devices. All non-Unisys devices will continue to honor label type for
scratch mount requests.
Unique DLm operations for Unisys mainframes 167

Configuring for Unisys
Device type When configuring devices for use by a Unisys mainframe the Device
Type should be set to '3490'.
Labels When the Unisys operating system sends a Load Display mount
message, it does not specify a label type. Unisys always expects an
ANSI label by default. To accommodate this, you must configure
each Unisys-attached device with the LABEL=A parameter. This will
change the DLm default for this device to ANSI labels instead of IBM
standard labels. Figure 34 shows a sample device definition screen
where sixteen tape drives are being defined including the LABEL=A
parameter.
Scratch tapes The Unisys operating system does not send the "MSCRTCH" message
to request a scratch tape as an IBM mainframe would. Instead it
sends an L-BLNK command. To accommodate the L-BLNK
command, you must specify a scratch synonym equal to L-BLNK.
Figure 34 shows a properly configured scratch synonym for Unisys
mainframes.
Figure 34 Unisys Device Panel
Configuring for Unisys 169

Initializing tapes for Unisys

When initializing tape volumes to be used with Unisys you must
include the LABEL=A option on the initialize command to tell the
system that the tape labels will follow the ANSI standard.
For example, to initialize 100 tapes beginning with VOLSER B00000
using tape drive E980, you would enter the following initialize
command:
INITIALIZE VOL=B00000 DEV=E980 COUNT=100 LABEL=A
Configuring the mainframe for DLm

DLm devices are configured in OS2200 using SCMS / SCMS-II as one
or more CTS5136-VSM (non-library) subsystems of 1 to 16 units. The
resulting ODB or .PTN file must be installed and the OS rebooted
with the proper definitions.
The Unisys equipment code for DLm devices is U47M.
Configuring the mainframe for DLm 171

7
z/OS Console Support
This chapter discusses DLm support for the z/OS Console:

◆ z/OS Console operation ................................................................. 174
◆ DLMHOST ........................................................................................ 175
◆ Using z/OS Console support ......................................................... 179
z/OS Console Support 173

z/OS Console operation

DLm provides an optional z/OS utility that can be used to
communicate between a single logical partition's (LPAR) operator
console and the DLm.
To make use of the DLm z/OS Console operation, you must install
the z/OS DLMHOST utility and then configure the individual VTEs
to communicate with it.
Using the DLm Configuration program, you can configure which
type (informational, warning, or error) of messages and / or which
specific DLm messages are sent over the channel to the mainframe.
DLMHOST
DLMHOST is a host utility that provides z/OS Console Operation
support. The DLMHOST utility runs as a started task, and accepts
commands from the operator. By default, DLMHOST uses
Write-to-Operator (WTOR) capabilities for sending DLm commands.
Optionally, you may configure DLMHOST to use the z/OS MODIFY
function in place of WTOR.
At startup, DLMHOST reads a configuration file that defines the
VTEs to be supported as well as the device addresses, per VTE, to be
used for communication and logging. Each DLm VTE will be
identified with a unique name so that commands can be targeted to
specific VTEs. A tape drive device address must be selected from
each VTE's range of addresses that will be used as the
command/communication path. A second device address is
required on each VTE if you want DLm to send log messages to the
z/OS console. These devices will not be eligible for allocation once
DLMHOST has been started.
Only log messages that have passed message filtering will be
received by the host.
It should be noted that, depending upon the filtering options set on
the VTEs, there may be many log messages sent to the consoles.
Optionally, DLMHOST supports a configuration option to send the
messages to a host file instead of the operator's console.
Installing DLMHOST
DLMHOST is only supported in a single Logical Partition (LPAR).
You cannot connect multiple DLMHOST tasks running in multiple
LPARs to the same DLm VTE.
DLMHOST is distributed in the 3.0 DLMZOS.XMI and the package is
available on the EMC support website. “Downloading and using the
DLm utilities and JCL for z/OS” on page 151 provides more details.
The DLMHOST utility must be linked as an authorized program into
an authorized library under the name DLMHOST. It is highly
recommended that RACF be used to restrict the use of DLMHOST to
authorized users only.
DLMHOST 175
An example of the JCL required to link DLMHOST follows:

//L EXEC PGM=HEWL,PARM='MAP,LET,LIST,NCAL,AC=1'
//SYSLMOD DD DSN=USER.LIBRARY,DISP=SHR
//SYSUT1 DD DSN=&&SYSUT1,SPACE=(1024,(120,120),,,ROUND),
// UNIT=SYSALLDA,DCB=BUFNO=1
//SYSPRINT DD SYSOUT=*
//DDIN DD DSN=DLM.MODULE,DISP=SHR
//SYSLIN DD *
INCLUDE DDIN(DLMHOST)
NAME DLMHOST(R)
/*
Running DLMHOST
The following JCL is used to execute DLMHOST:
//DLMSTEP EXEC PGM=DLMHOST,PARM='parameters'
//DLMCFG DD DSN=PARMLIB(nodecfg),DISP=SHR
//DLMLOG DD DSN=logfilename,DISP=SHR
//* THE FORMAT OF THE CONFIG FILE IS AS FOLLOWS:
//* Col 1 -10 Nodename
//* Col 12-15 Command path device address
//* Col 17-20 Log path device address
//* Col 22-29 Console name
The parameters than can be specified are:

◆ DOCMDS—Requires the use of a DLMCMD DD card pointing to
a file of commands that are to be processed during DLMHOST
startup. The commands should be in the same format as used in
modify or WTOR processing.
Note: EOJ can be specified as the last command to terminate DLMHOST

after a series of commands.
◆ NOLOG—Prevents DLMHOST from receiving continuous log

data from any VTE. Set this parameter if you plan to use
DLMHOST only to send commands from the z/OS Console to the
DLm. Command responses will be returned even when NOLOG
is specified.
◆ NOWTOR—Prevents DLMHOST from issuing the normally
outstanding WTOR. When this parameter is specified, MDL
commands can be issued using the z/OS MODIFY command as
the method of communication in place of WTOR.
◆ LOGFILE—Causes any received log data from the DLm system

to be recorded in the file pointed to by the DLMLOG DD card.
When LOGFILE is specified, the log messages are not sent to any
console via WTO. If LOGFILE is not specified, the DLMLOG DD
card is not required in the JCL. The LOGFILE dataset should be
an FB LRECL 133 file, and will be opened for extend each time the
task is started.
EMC provides sample JCL to run DLMHOST. Step 4 of
“Downloading and using the DLm utilities and JCL for z/OS” on
page 151 provides instructions to download the sample JCL. The
sample JCL xmit file includes a sample PROC member to run the
DLMHOST utility. This proc must be customized to point to the APF
authorized load library that DLMHOST has been installed in. Also,
one or more configuration statements must be completed for the
DLMCFG DD. The customized proc should be placed into a
PROCLIB that is searched when the START DLMHOST command is
issued from the zOS Console.
DLMHOST configuration file

The configuration file pointed to by the DLMCFG DD card should be
an FB LRECL 80 file that has a single record for each VTE to be
supported. You can define upto 64 records.
Comments cards can be included in the input configuration file by
placing an asterisk in column 1.
The layout of the configuration file records is as follows:
Col. 1 - 10 : NODENAME
The name used by the mainframe operator to identify which VTE to
communicate with.
Col 12 - 15: CMDDEV

The 4-digit device address of the tape drive that is to be used for
operator commands and responses. If this field is left blank, no
operator commands can be sent to this nodename.
Col 17 - 20: LOGDEV

The 4-digit device address of the tape drive that is to be used for
logging activity whenever logging is active for this VTE. If left blank,
no host logging can occur from the VTE.
DLMHOST 177
Col 22 - 29: CONSNAME

The console that log messages should be directed to if logging is
active for this VTE. If this field is left blank, the log messages will go
to all routcde=5 (tape library) consoles.
The following is sample JCL for DLMHOST within a 3-VTE
configuration supporting both messaging and commands:
VTLNODE1 038E 038F TAPECON1
VTLNODE2 039E 039F TAPECON1
VTLNODE3 03AE 03AF TAPECON1
Using z/OS Console support

If DLMHOST is active and configured to receive DLm messages, it
automatically forwards any message received to the appropriate
console or log file.
When DLMHOST is executed without the NOWTOR parameter, the
following message is displayed on the z/OS console:
DLM001I ENTER COMMAND, EOJ,OR ? FOR HELP
An outstanding Write to Operator Reply (WTOR) message will

remain pending.
To send a command to DLMHOST, you need to know the message
reply number from the WTOR. To determine the WTOR message
number, enter the following z/OS command on the operator's
console:
d r,l (or /d r,l from SDSF)
This command returns the reply message number for any

outstanding WTORs on the system.
To issue a command to DLMHOST, enter the command using the
WTOR message number in the following format:
msg#,COMMAND
Where:
msg# is the reply message number returned from the d r,l command.
COMMAND is the DLMHOST command to be executed.
When DLMHOST is executed with the NOWTOR parameter, the
following message is returned:
DLM002I jobname USE MODIFY TO ENTER COMMAND, EOJ, OR ?
FOR HELP
Subsequently the z/OS Modify command can be used to issue

commands to DLMHOST using the 'jobname' indicated in the
DLM002I message.
The format of the z/OS Modify command is:
F jobname,command
Using z/OS Console support 179

where:
jobname is the job name of DLMHOST reported in the DLM002I
message.
command is the DLMHOST command to be executed.
DLMHOST commands
The following commands are recognized by DLMHOST:
◆ CMD
The CMD sends a DLm command to a specific VTE.
This command requires a nodename also be specified by using
the NODE= parameter (or N=).
A nodename of ALL can be specified to send the command to
every VTE.
All DLm Operator commands can be entered as parameters to
this command.
The following are examples of valid use of this command:
CMD=Q SPACE,NODE=NODE1
CMD=FIND VOLUME 000001,N=N1
◆ STOPLOG
The STOPLOG command requests that DLMHOST stop logging
VTE log messages for a specific VTE. This command requires that
a nodename be specified by using the NODE= parameter (or N=).
A nodename of ALL can be specified to stop host logging for all
defined VTEs.
For example:
STOPLOG,N=ALL
STOPLOG,N=VTLNODE1
◆ STARTLOG
The STARTLOG command requests that DLMHOST start host
logging of VTE log data for a specific VTE. This command
requires that a nodename be specified by using the NODE=
parameter (or N=). A nodename of ALL can be specified to start
logging for all defined VTEs.
For example:
STARTLOG,N=NODE2
STARTLOG,NODE=ALL
◆ STATUS
The STATUS command requests that DLMHOST display the
current configuration and status of the command and logging
functions.
DLMHOST will issue this message followed by the status of each
configured node:
DLM240I NODENAME CMDDEV LOGDEV CONSNAME
A y or n next to the device address indicates whether the
command/logging function is currently active or inactive for that
node name, respectively.
For example:
DLM2401 NODENAME CMDDEV LOGDEV CONSNAME
NODE1 038E Y 038F Y CON1
NODE2 048E N 048F Y
◆ EOJ
The EOJ Command will terminate the DLMHOST task.
◆ HELP or ?
The Help (?) command returns the DLM000I message with a list
of the valid DLMHOST commands.
The commands that DLM000I lists are:
STARTLOG,N=nodename/ALL
STOPLOG,N=nodename/ALL
C=Command,N=nodename/ALL
STATUS
WTOR command examples

When DLMHOST has been executed without the NOWTOR
parameter, an outstanding WTOR message reply is used to send
commands to DLMHOST. The following are valid examples of
DLMHOST commands:
msg#,STATUS
msg#,C=Q SPACE,N=N1
msg#,STOPLOG,N=ALL
Using z/OS Console support 181

where msg# is the message number returned from the d r,l (/d r,l
from SDSF).
The following are valid examples of the same DLMHOST commands
when DLMHOST has been executed with the NOWTOR parameter
using the job name DLMHOST:
F DLMHOST,STATUS
F DLMHOST,C=Q SPACE,N=N1
F DLMHOST,STOPLOG,N=ALL
A
Virtual Tape Operator
Command Reference
This appendix contains the Virtual Tape Operator command

reference:
◆ Virtual Tape Operator command reference.................................. 184
Virtual Tape Operator Command Reference 183

Virtual Tape Operator Command Reference
Virtual Tape Operator command reference

When a VTE is operational and the control window is open, you can
use the virtual tape commands to control the virtual tape drives on
the VTE.
Syntax
Virtual tape operator commands use the following syntax rules:
◆ UPPERCASE words are keywords and must be spelled as shown.
You can type the keywords in either uppercase or lowercase.
◆ Lowercase words in italics are values that you supply. Generally,
you can type these values in either uppercase or lowercase. The
exceptions are noted in the command description.
◆ Values in square brackets [] are optional.
◆ When multiple values are separated by a pipe symbol (|), enter
only one of the choices.
DISABLE DISABLE FIRMWARE TRACE

Use the DISABLE FIRMWARE TRACE command to turn off the
tracing feature of the channel interface adapters. Use this command
only under the direction of EMC Customer Support.
ENABLE ENABLE FIRMWARE TRACE

Use the ENABLE FIRMWARE TRACE command to turn on the
tracing feature of the channel interface adapters. Use this command
only under the direction of EMC Customer Support.
EXPORT EXPORT from to [norun compress]

where from is the full library name (within the filing structure) of the
tape volume (VOLSER) to be copied and to is the name of the device
driver for the tape drive that the volume must be written to.
For example:
EXPORT /tapelib/B0/B00104 DRIVE-nnnnnnnnnnnn
The example copies tape volume (VOLSER) B00104 from the

back-end tape library to the tape drive Drive-nnnnnnnnnnn, where
nnnnnnnnnnn is a 12-character serial number of the fibre channel
attached tape drive.
Note: Make sure that the volume does not exceed the physical capacity of the
cartridge being written to. If you attempt to write to tape a volume that
cannot fit on the cartridge, the export fails and invalidates the data on the
tape by rewinding and writing a tapemark in the front of the tape.
The options for the EXPORT command are:

◆ norun instructs DLm not to unload the tape when the export is
complete.
◆ compress indicates whether DLm should compress the tape
volume when it is written to the drive. The default is to write the
data without compression. If you include this option in the
command, DLm instructs the tape drive to compress the data
before writing it to the media.
If the volume is already compressed and unencrypted on the tape
library, DLm decompresses the data before writing it to the
physical tape. Then, if the compress option is specified, DLm
instructs the drive to compress the data.
If the volume is already encrypted on the tape library, the
compress option has no effect on the data. DLm copies the
encrypted volume as is to the physical tape.
FIND FIND VOLUME volser

The FIND command finds a specific volume (VOLSER) in the DLm
tape library and reports the current status of that volume.
For example:
FIND VOLUME 000001
The example returns the current status of the tape volume with the
serial number 000001.
Virtual Tape Operator command reference 185

HELP HELP [ command | message number | ABOUT ]

The HELP command displays the following information about the
virtual tape operator commands and messages:
◆ If the command HELP is typed by itself, a summary of all
commands is displayed.
◆ If a command is specified, a more detailed description of that
command is displayed.
◆ If a message number is specified, an explanation of the message is
displayed. For example, HELP 489 displays information about
message DLm489E. (Typing the message number as DLm489E,
DLm489, or 489 gives the same result.)
Note: A synonym for the word HELP is ?, that is, ? 489.
◆ HELP ABOUT displays information about the virtual tape

application.
Note: The Help information pertains to the virtual tape application (VT
Console) only.
IMPORT IMPORT from to [norun] [compress] [class=n|CLASSn]

where from is the device name of the tape drive to be read and to is the
complete library name (within the DLm filing structure) of the tape
volume (VOLSER) being imported.
For example:
IMPORT DRIVE-nnnnnnnnnnnn /tapelib
The example imports the tape-on-drive Drive-nnnnnnnnnnn, where

nnnnnnnnnnn is a 12-character serial number of the fibre channel
attached tape drive, and writes it to the library '/tapelib'.
The options for the IMPORT command are:
◆ norun instructs DLm not to unload the tape when the import is
complete.
◆ compress indicates that DLm should compress the tape volume
when it is written to the drive. DLm assumes that if the tape is
compressed on the cartridge, the drive will automatically
decompress it as it is being read from tape. If you include this
option in the command, DLm instructs the tape drive to compress

the data before writing it to the media. If you do not include this
option, DLm stores the uncompressed volume in the library.
◆ CLASS=CLASSn provides storage class in which DLm must store
the imported volume in the library. The default is CLASS0.
INITIALIZE INITIALIZE VOL=VOLSER DEVICE=devname [COUNT=count]

[CLASS=CLASSn] [DIR=dirname] [LABEL=S/A/N]
[SCRATCH=Y/N] [EPIC=N/Y]
Note: In DLm command syntax, you can use DEVICE and DEV
interchangeably.
Use the INITIALIZE command to pre-initialize any number of

scratch volumes in any DLm tape library filing structure. The
description of values within the command is as follows:
◆ If VOLSER is specified without a count, only the volume specified
is created.
◆ If count is specified, VOLSER becomes a template for creating a
number of sequential VOLSERs. VOLSER must end with numeric
digits that start with a value that is low enough and has sufficient
digits to contain the number of volumes specified in count.
For example, VOL=BT0000 COUNT=1000 would create volumes
BT0000 through BT0999. Similarly, VOL=XXX100 COUNT=500
would create volumes XXX100 through XXX599. However,
VOL=BTA100 COUNT=1000 would be illegal, as would
VOL=ABCDE0 COUNT=11 or VOL=ABCDEF COUNT=2.
◆ Any existing volume in the range is skipped. It will not be altered
in any way.
◆ Remember EMC only supports VOLSER ranges limited to 10,000
volumes.
◆ DEVICE=devname instructs the INITIALIZE function to use the
tape library pointed by devname to determine where to create the
new scratch tapes.
For example, if device E980 points to /tapelib, the following
command causes 100 scratch tapes to be created in the default
storage class (CLASS0) of the library /tapelib:
INIT VOL=B00000 DEVICE=E980 COUNT=100

◆ The CLASS parameter directs the new volumes being initialized

to a specific storage class within the library. You must initialize
scratch tapes into any new storage class before you attempt to
allocate a new scratch volume from that class.
◆ The DIR parameter is always optional and allows you to direct
the new volumes being initialized to a specific filesytem
(directory) within the library. When not specified, new volumes
will be initialized into the first filesystem within the storage class.
During operation, DLm automatically moves scratch volumes
between filesystems in the same class as needed. Therefore it is
not necessary to initialize tape volumes into all filesystems. You
only need to make sure that each storage class has scratch tapes.
◆ The LABEL parameter specifies whether the new volumes are
created with Standard IBM (EBCDIC) labels (S), ANSI (ASCII)
labels (A), or no labels (N). The default is Standard IBM labels.
◆ Volumes are initialized as scratch volumes by default and are
immediately available for allocation in response to a mount
scratch tape request from any VTE in the system. If you want to
initialize a volume and do not want it to assume the default
scratch status, specify SCRATCH=NO.
◆ EPIC=YES places an identifier on the HDR1 label signifying that
the volume is owned by BIM-EPIC tape manager causing
BIM-EPIC to accept the new volume without requiring any host
operator intervention. The default is EPIC=NO.
LOAD LOAD [VOL=]volser [ON] [DEVICE=]devicename|* [UNLABELED

| LABELED | NL | SL | AL] [PROTECTED]
Use the LOAD command to perform a manual load of a virtual tape
volume.
Use a manual load to load a volume for a host system that does not
send Load Display Mount messages, or in a situation where you want
to mount a tape other than the one the host is requesting.
The description of values within this command is as follows:
◆ If the devicename is specified as *, the volume is loaded on the first
available empty drive.
◆ The label options apply only to volumes that the VTE is yet to
initialize. DLm ignores these label specifications for existing
(non-scratch) volumes:
• LABELED and SL are synonymous and specify that the

volume must be initialized with standard IBM (EBCDIC)
labels.
• UNLABELED and NL are synonymous and specify that the
volume must be initialized as an unlabeled tape.
• AL specifies that the volume must be initialized with standard
ANSI (ASCII) labels.
◆ If no label option is specified, the volume is initialized according
to the device's LABEL= configuration parameter. The default is
standard IBM (EBCDIC) labels.
◆ The PROTECTED option loads the tape as read-only. Otherwise,
the volume is loaded in normal read-write mode.
QUERY QUERY [[DEVICE=]devicename[+] | ALL | COMPRESSION |

CONFIG | ENCRYPTION | LABELS | LOCKS| MOUNTED
|PATHS [ASSIGNED] | SPACE | SCRATCHNAMES |STCLASS
| VERSION]
Use the QUERY command to display the system information. The
following is a description of the values within the command:
◆ QUERY with no operands displays the current status of all virtual
tape drives, while DEVICE=devicename displays a single drive
or range of drives. Use * as a wildcard character to display a range
of drives. For example, Q E98* displays all the devices E980–E98F.
◆ QUERY ALL displays information about the virtual tape
application, the channel interface cards, and all virtual tape
devices.
◆ QUERY COMPRESSION lists the status of a FICON VTE's AHA
compression adapters.
◆ QUERY CONFIG shows detailed configuration information for
all devices.
◆ QUERY ENCRYPTION shows the status of the DLm encryption
keys.
◆ QUERY LABELS shows the header labels, if any, for all mounted
tapes.
◆ QUERY LOCKS shows any tape volumes with locks associated
with them.

◆ QUERY MOUNTED displays information only about the drives

that currently have virtual tape volumes mounted.
◆ QUERY PATHS shows all the channel paths established for the
VTE devices. If ASSIGNED is specified, only channel paths with
a current host assignment (typically those varied online) are
displayed.
◆ QUERY SPACE shows a summary of the disk space used and
available in all the tape libraries.
Note: You can enter additional commands while the QUERY SPACE
command is being processed.
◆ QUERY SCRATCHNAMES displays all the scratch VOLSER

synonyms currently in effect.
◆ QUERY STCLASS returns the storage classes defined to the
library.
◆ QUERY VERSION displays the tape-on-disk application release
number.
File-size values reported by the QUERY command reflect the
compressed data size, not the original uncompressed size.
QUERY sample output

06/01/2010 11:21:44 VTE1 VT: Devicename VOLSER/L
06/01/2010 11:21:44 VTE1 VT: ---------- --------
06/01/2010 11:21:44 VTE1 VT: 1D00 NR-UA
06/01/2010 11:21:44 VTE1 VT: 1D01 NR-UA
06/01/2010 11:21:44 VTE1 VT: 1D02 NR-UA
06/01/2010 11:21:44 VTE1 VT: 1D03 NR-UA
06/01/2010 11:21:44 VTE1 VT: 9200 AA2222 S R-A2 aws/rw LP
06/01/2010 11:21:44 VTE1 VT: 9210 FE0023 S R-A2 aws/ro LP
06/01/2010 11:21:44 VTE1 VT: 9211 FE0026 S R-A2 aws/mod LP
The four columns under VOLSER\L are:

◆ Volume currently mounted on the drive
◆ Type of label on the volume:
• S = Standard IBM
• A = ANSI
• N = Unlabeled
◆ Drive status:
• Q = Quiesced
• R = Ready
• NR = Not ready
• NA = Not accessible
• UA = Not currently allocated by a Host
• An = Allocated on n logical channel paths: A1 = allocated on
one logical channel path, A2 = allocated on two paths, A3 =
allocated to three paths, etc.
(For a non-autoswitched device, An means one Host has
varied online n paths and the device; for an autoswitched
device, or in a JES3 environment, An means the Host has
reserved the device for use on n logical channel paths.)
◆ Volume status:
• aws or flat is the virtual tape file format.
• scsi for a SCSI or Fibre-Channel-attached tape drive.
• rw is read-write.
• ro is read-only.
• lfp is logical file protect set by the Host.
• If a volume is mounted, the current block position or LP (for
loadpoint) is displayed, and whether the last operation was a
read or write.
Other notations might also be displayed when a volume is being
written:
• h-compr or s-compr signifies that the most recent write was
compressed by hardware or software, respectively. The total
volume size shown is after the compression notation, if any.
• crypt signifies that the most recent write was encrypted.
• AMDD signifies that the AMDD feature has modified one or
more blocks being written to this volume.
• GR signifies that the volume is being written to a replicating
filesystem and a replication-refresh will be performed when
the tape is closed.
If a mount previously failed, the most recently requested VOLSER
and the reason for the mount failure are displayed.

QUERY all sample output

06/01/2010 11:21:50 VTE1 VT:
06/01/2010 11:21:50 VTE1 VT: Version 6.10-10, build 7622, built May 7 2010
17:00:33
06/01/2010 11:21:50 VTE1 VT: Licensed Features Enabled:
06/01/2010 11:21:50 VTE1 VT: SCSI Tape Support
06/01/2010 11:21:50 VTE1 VT: Data Exchange (Flat File) Support
06/01/2010 11:21:50 VTE1 VT: Import-Export Support
06/01/2010 11:21:50 VTE1 VT: EMC DLm Support
06/01/2010 11:21:50 VTE1 VT: EMC GR Support
06/01/2010 11:21:50 VTE1 VT: AMDD Support for EMC
06/01/2010 11:21:50 VTE1 VT: Program started at Fri May 21 17:51:31 2010
06/01/2010 11:21:50 VTE1 VT: DLm056I: Channel driver version is 4.4.5,
06/01/2010 11:21:50 VTE1 VT: DLm075I: Interface #0: 199936 (0x030D00) bus:13
slot:0 type:15 (PEFA-LP) media:3 (FiCon)
06/01/2010 11:21:50 VTE1 VT: DLm076I: Interface #0: hardware s/n: 000D08356881
06/01/2010 11:21:50 VTE1 VT: DLm077I: Interface #0: Firmware emulation type:
TRANS, version: 1216 2010/05/04
06/01/2010 11:21:50 VTE1 VT: DLm070I: Interface #0: TRANSX emulation version set
to 3
06/01/2010 11:21:50 VTE1 VT: DLm081I: Interface #0: Current state: running;
Desired state: running; Media Up, Loop Up
06/01/2010 11:21:50 VTE1 VT: DLm075I: Interface #1: 199680 (0x030C00) bus:12
slot:0 type:15 (PEFA-LP) media:3 (FiCon)
06/01/2010 11:21:50 VTE1 VT: DLm076I: Interface #1: hardware s/n: 000D08356861
06/01/2010 11:21:50 VTE1 VT: DLm077I: Interface #1: Firmware emulation type:
TRANS, version: 1216 2010/05/04
06/01/2010 11:21:50 VTE1 VT: DLm070I: Interface #1: TRANSX emulation version set
to 3
06/01/2010 11:21:50 VTE1 VT: DLm081I: Interface #1: Current state: running;
Desired state: running; Media Up, Loop Up
06/01/2010 11:21:50 VTE1 VT: DLm790I: ST driver version: 1.40
06/01/2010 11:21:50 VTE1 VT: DLm841I: System tracelevel is currently set to 1
06/01/2010 11:21:50 VTE1 VT: DLm842I: System debuglevel is currently set to 0
06/01/2010 11:21:50 VTE1 VT: DLm856I: 0 scratch synonyms
06/01/2010 11:21:50 VTE1 VT: DLm078I: Disk usage WARNING level set to 88%
06/01/2010 11:21:50 VTE1 VT: DLm079I: Disk space RECOVER level is N/A
06/01/2010 11:21:50 VTE1 VT: DLm084I: Disk space RECOVERAMT set to 5%
06/01/2010 11:21:50 VTE1 VT: DLm096I: Erase Policy: TTL for 10 hours
06/01/2010 11:21:50 VTE1 VT: DLm097I: Maximum TTL Erase Time set to 30 seconds
06/01/2010 11:21:50 VTE1 VT: DLm099I: New mount on already-mounted drive will be
allowed
06/01/2010 11:21:50 VTE1 VT: DLm069I: Resetting Events will not be sent to firmware
06/01/2010 11:21:50 VTE1 VT: DLm112I: Using NEW standard scratch search method
06/01/2010 11:21:50 VTE1 VT: DLm114I: Using DEFAULT method of filesystem
allocation
06/01/2010 11:21:50 VTE1 VT: DLm109I: Scratch mounts will ignore full filesystems
(UseFullFS=FALSE)
06/01/2010 11:21:50 VTE1 VT: DLm083I: Compression level set to 1
(0=none,1=faster,9=smaller)
06/01/2010 11:21:50 VTE1 VT: DLm010I: Compression hardware available
06/01/2010 11:21:50 VTE1 VT: DLm011I: Compression driver version: 1.1.7

06/01/2010 11:21:50 VTE1 VT: DLm012I: Compression card #0: id=0x193F0363 (AHA363)
version=0x120 state=00000000
06/01/2010 11:21:50 VTE1 VT: DLm013I: Hardware compression set ON
06/01/2010 11:21:50 VTE1 VT: DLm013I: Hardware decompression set ON
06/01/2010 11:21:50 VTE1 VT: DLm873I: Attention set to PATHGROUP
06/01/2010 11:21:50 VTE1 VT: DLm871I: AttentionCount set to 45
06/01/2010 11:21:50 VTE1 VT: DLm067I: BusyType set to Busy
06/01/2010 11:21:50 VTE1 VT: DLm853I: Pending Mount Fairness (PMFAIR) set to 0
06/01/2010 11:21:50 VTE1 VT: DLm892I: Write Sync set to 0
06/01/2010 11:21:50 VTE1 VT: ---------- --------
06/01/2010 11:21:50 VTE1 VT: 1D00 NR-UA
06/01/2010 11:21:50 VTE1 VT: 1D01 NR-UA
06/01/2010 11:21:50 VTE1 VT: 1D02 NR-UA
06/01/2010 11:21:50 VTE1 VT: 1D03 NR-UA
06/01/2010 11:21:50 VTE1 VT: 1D04 NR-UA
QUERY COMPRESSION sample output

06/01/2010 11:19:24 VTE1 VT: DLm083I: Compression level set to 1
(0=none,1=faster,9=smaller)
06/01/2010 11:19:24 VTE1 VT: DLm010I: Compression hardware available
06/01/2010 11:19:24 VTE1 VT: DLm011I: Compression driver version: 1.1.7
06/01/2010 11:19:24 VTE1 VT: DLm012I: Compression card #0: id=0x193F0363 (AHA363)
version=0x120 state=00000000
06/01/2010 11:19:24 VTE1 VT: DLm013I: Hardware compression set ON
06/01/2010 11:19:24 VTE1 VT: DLm013I: Hardware decompression set ON
QUERY CONFIG sample output

06/01/2010 11:19:59 VTE1 VT: DLm102I: Configuration file is /etc/bti/xmap0
06/01/2010 11:19:59 VTE1 VT: Current Values Are:
06/01/2010 11:19:59 VTE1 VT: Index Devicename Type CU UA Options
06/01/2010 11:19:59 VTE1 VT: ------------------------------------
06/01/2010 11:19:59 VTE1 VT: 00 1D00 3490 00 00 PATH=/tapelib/ SIZE=2G
06/01/2010 11:19:59 VTE1 VT: 80 1D80 3490 08 00 PATH=/tapelibGRS2/ SIZE=2G
06/01/2010 11:19:59 VTE1 VT: GR=YES
06/01/2010 11:19:59 VTE1 VT: 4A 940A 3590 04 0A PATH=/tapelib/ SIZE=40G
QUERY LABELS sample output

06/01/2010 12:30:38 VTE1 VT: DLm409I: Command received: 'query labels'
06/01/2010 12:30:38 VTE1 VT: 1D00 S VOL1JJ0031
TCSBT

06/01/2010 12:30:38 VTE1 VT: HDR1LL6.DEMO.BACKUP02JJ003100010001

0101520000000000000IBM OS/VS 370
06/01/2010 12:30:38 VTE1 VT: HDR2U000000000000DPHILL6D/DUMP
00000 0000065520
QUERY LOCKS sample output

DLm409I: Command received: 'QUERY LOCKS'
===================================
dd lock files -- long term files
owner dd lock file
---------------------------------------------
dd lock file count 0
===================================
volser lock files -- short term files (dir: /lockfs/LOCK/)
owner volser
---------------------------------------------
volser lock count: 0
QUERY MOUNTED sample output

06/01/2010 12:30:30 VTE1 VT: DLm409I: Command received: 'query mounted'
06/01/2010 12:30:30 VTE1 VT: ---------- --------
06/01/2010 12:30:30 VTE1 VT: 1D00 JJ0031 S R-A2 aws/rw block 2514
(writing 135.6M)
QUERY PATHS sample output

06/01/2010 11:20:41 VTE1 VT: Device Interface/Path# Port LPAR CU Device Path
Group ID
06/01/2010 11:20:41 VTE1 VT: 1D00 0 0 0000 6 00 00
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 0 1 0000 7 00 00
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1 0 0000 6 00 00
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1 1 0000 7 00 00
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1D01 0 0 0000 6 00 01
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 0 1 0000 7 00 01
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1 0 0000 6 00 01
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1 1 0000 7 00 01
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1D02 0 0 0000 6 00 02
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 0 1 0000 7 00 02
0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1 0 0000 6 00 02

0000000000000000000000
06/01/2010 11:20:41 VTE1 VT: 1 1 0000 7 00 02
0000000000000000000000
QUERY SPACE sample output

Tape library space for drives: E000-E03F
Path Size Active Scratch/ Qty Free Filesystem

------ ----- -------- -------- ----- ----------
/tapelib/ 28G 0 0% 736 0% 04 25G 89% LABEL=root
/tapelib/F0 48G 25G 51% 329M 0% 1832 23G 48% /dev/sdb1
/tapelib/N0 877G 22G 2% 15K 0% 83 855G 97% 192.168.222.222:/FS2
/tapelib/FE 99G 1G 1% 1K 0% 07 98G 98% 10.1.2.219:/tapelib/FE
===============================================
Totals: 1052G 48G 5% 329M 1% 1926 1001G 95%
◆ Tape library space for drives: All devices sharing the same tape
library are grouped together.
◆ Path: The first (or only) entry is the tape library base directory. If
the base tape library contains subdirectories, they are listed
separately and a total is printed.
◆ Size: This is the size of the entire filesystem.
◆ Active: This is the amount of space being used by non-scratch
tape volumes.
◆ Scratch: This is the amount of space that scratch tape volumes
use. The system can reclaim scratch tape space at any time as
needed.
◆ Qty: This is the number of scratch tape volumes in this directory.
◆ Free: This is the amount of free space currently available on the
entire filesystem. Note that if the filesystem holds files in
directories other than the tape library directory, the space of all
other files will reduce the free space. For this reason (Size - Active
- Scratch) it may not add up (Unused), as seen in the first
example.
◆ Filesystem: The filesystem device name, typically a hard drive
partition name or an NFS or SMB mount point.
When a Data Domain DD890 is integrated with the DLm system, the
following differences appear:

◆ The Size column: The total may not reflect the actual total because
the Data Domain storage appliance uses one filesystem for all its
exports. In the above example, all the sizes will be equal and the
total will be the total of the exports.
◆ Active, Scratch, and Qty remain the same.
◆ Free: All exports reflect the same amount of free space due to the
single partition with many exports. The Totals column reflects
larger quantity than is really available because it is a total of the 3
individual free spaces.
QUERY SCRATCHNAMES sample output

06/01/2010 11:21:20 VTE1 VT: DLm409I: Command received: 'q scratchnames'
06/01/2010 11:21:21 VTE1 VT: DLm409I: Command received: 'query scratchnames'
06/01/2010 11:21:21 VTE1 VT: DLm856I: 2 scratch synonyms: GR,REPL
QUERY STCLASS sample output

DLm409I: Command received: 'QUERY STCLASS'
Class Path
---------------------------------
0 /tapelibREP/CR
0 /tapelibREP/R2
0 /tapelibREP/R1
0 /tapelibREP
0 /tapelib
0 /tapelibDD
QUERY VERSION sample output

06/01/2010 11:21:30 VTE1 VT: Version 6.10-10, build 7622, built May 7 2010
17:00:33
06/01/2010 11:21:30 VTE1 VT: Licensed Features Enabled:
06/01/2010 11:21:30 VTE1 VT: SCSI Tape Support
06/01/2010 11:21:30 VTE1 VT: Data Exchange (Flat File) Support
06/01/2010 11:21:30 VTE1 VT: Import-Export Support
06/01/2010 11:21:30 VTE1 VT: EMC DLm Support
06/01/2010 11:21:30 VTE1 VT: EMC GR Support
06/01/2010 11:21:30 VTE1 VT: AMDD Support for EMC
06/01/2010 11:21:30 VTE1 VT: Program started at Fri May 21 17:51:31 2010
QUIESCE QUIESCE [ [DEVICE=]devicename | ALL | * ]

The QUIESCE command sets one or all of the virtual drives into the
quiesced state. Quiesced drives cannot accept any further mount
requests until they are unquiesced. Any mount requests executed to a
quiesced drive are ignored and remain pending. The drive stays in
the Not Ready state. These ignored mount requests stay pending just
like other unsuccessful mounts, until the host cancels the mount
request. It is automatically retried when a drive is unquiesced.
Other than ignoring any new mount requests, quiesced drives
continue to function normally; any volume already loaded on the
drive continues to be normally accessible until it is unloaded.
Quiescing a drive does not send any signal to the host.
ALL and * are synonymous and mean quiesce all drives at once.
READY READY [DEVICE=]devicename

Use the READY command to change a virtual drive from the Not
Ready to the Ready state.
Typing the READY command for a virtual tape drive is equivalent to
pressing the Ready button on a physical tape drive.
To make a virtual drive ready, it must already have a volume
mounted and be in the Not Ready (Intervention Required) state. If the
specified drive does not have a volume mounted, or is already in the
Ready state, the READY command is ignored.
The READY command is not needed during normal processing to
make a drive Ready. Normally, a drive automatically becomes Ready
whenever a volume is mounted and stays Ready until the volume is
unloaded.
The Not Ready condition, while a volume is mounted, is an
exceptional condition that occurs only when:
◆ The DLm runs out of disk space in the tape library while writing
to a virtual volume.
or
◆ The UNREADY command was entered.
RESET CHANNEL ADAPTER

RESET CHANNEL ADAPTER n
The RESET command restarts the firmware in the specified FICON
channel adapter number n.

This command is rejected if there are any active paths established on

this adapter. Vary offline from the host all the devices or paths or
channels attached to this adapter before invoking this command.
REWIND REWIND [DEVICE=]devicename

Use the REWIND command to manually rewind the specified virtual
tape drive.
Using the REWIND command for a virtual tape drive is equivalent to
pressing the Rewind button on a physical tape drive. Like a physical
tape drive, the specified virtual tape drive must be in the Not Ready
state for the REWIND command to be accepted as described in
“UNREADY” on page 204.
DLm immediately executes the REWIND command regardless of
whether the host might currently be using the tape.
Note: If the host is still processing the volume and has not yet closed the tape,
manual repositioning may make the host read from or write to an incorrect
location of the virtual tape volume. For this reason, use the REWIND
command only in an emergency situation when a tape volume is known and
is not in use by a host application, but needs to be rewound to loadpoint
immediately.
SAVE TRACE SAVE [TRACE]

Use the SAVE TRACE command to write all trace buffers to disk
immediately. Normally, the traces are buffered in memory and only
written to disk periodically for performance reasons. Before
examining or copying the trace files, you must perform the SAVE
TRACE command to make sure that all currently buffered trace data
is written to disk. SAVE TRACE also saves channel adapter firmware
trace files to disk.
SET SET [HWCOMP=ON/OFF] [HWDECOMP=ON/OFF]

[IDRC=ON|OFF|FORCE] [PATH=pathname [NOCHECK]]
[PENALTYUP=n] [RECOVER=nn] [RECOVERAMT=nn]
[SIZE=xxx] [TIMESTAMPS=NO/YES] [TRACE=n]
[WARNING=nn] [DEVICE=devicename|ALL|SYSTEM]
Use the SET command to set various options for the virtual tape
devices. Any option set by the SET command is a temporary change,
and the setting reverts to the configuration file or default value the
next time the virtual tape application is started. To make permanent
changes, make the changes in the VTE configuration file. Following is
the description of options within the command:
◆ HWCOMP=ON/OFF indicates whether the VTE must perform
hardware data compression on a given drive. By default, the VTE
uses hardware data compression (HWCOMP=ON) if the
compression hardware is present and the mainframe has
requested IDRC. If you set HWCOMP=OFF, the VTE does not
use the compression hardware to do data compression. It
performs software compression when IDRC is requested by the
mainframe.
◆ HWDECOMP=ON/OFF indicates whether the VTE must
perform hardware decompression on a given drive. By default,
the VTE uses hardware decompression (HWDECOMP=ON)
whenever the compression hardware is present and
decompression is required. If HWDECOMP is set to OFF, the
VTE uses software decompression when decompression is
needed.
◆ IDRC=ON/OFF turns on or off write compression on a given
drive. IDRC=FORCE causes the VTE to compress all data even if
the host does not specify compression on the write. When IDRC is
set to OFF, the VTE still reports to the host that it supports
compression, although it does not actually perform any
compression when it writes data to disk. This is because some
host operating systems or tape managers do not use drives that
support compression. IDRC=OFF affects writing of data. If IDRC
is set to OFF, the VTE can read virtual tape volumes that it
previously wrote with compression ON.
When writing to VOLSERs stored on deduplicating storage, the
IDRC setting Yes is ignored and the VTEs do not compress the
data before it is written to the deduplicating storage. However,
using Force with a deduplicating file system can severely limit
the ability of the storage system to de-duplicate and will,
therefore, use more real disk storage.
◆ PATH=pathname sets the path for the virtual tape library for a
specific device. This option requires a specific DEVICE
specification. If a tape volume is not currently loaded on the
drive, the new pathname specification takes effect immediately.

Otherwise the change takes effect immediately after the current

volume is unloaded. The pathname is case-sensitive and must
exactly match the disk directory name within the filing structure
in DLm. Always specify the tape library base directory, that is,
/tapelib, not a subdirectory of the tape library (such as
/tapelib/BA). DLm checks the specified tape library and any
subdirectories for logical errors, such as a tape VOLSER being in
the wrong subdirectory, and if it finds any error, it leaves the path
unchanged. If you absolutely must set the path to a directory
which cannot pass validation, you can specify the NOCHECK
parameter to accept the path even if it fails validation.
SET PATH assigns a virtual device to a Fibre Channel tape drive
to use the Direct Tape feature. To use SET PATH in this manner,
specify the tape driver name. For example,
SET PATH=/dev/nst0.
◆ PENALTYUP=n helps to prevent filesystem overload. When the
VTE receives a mount request for a scratch tape, DLm tries to
distribute the data evenly across multiple filesystems. It is
important that, at a given time, multiple scratch mounts are not
all chosen from the same filesystem because this will cause that
filesystem to be overloaded and impact performance.
DLm prevents filesystem overload by applying a penalty to a
filesystem once it has been chosen (to decrease the chance that it
will be chosen again). Following that, every directory (including
the one that was chosen) has 1 subtracted from its current penalty
whenever any directory in that library is chosen. The selection
comparison criteria is (free space * (100% - penalty%.)
The following guidelines should be used to decide a
PENALTYUP value:
1. Never decrease the PENALTYUP value below 6.
2. Never increase the PENALTYUP value above the number of
mounted filesystems or 100, whichever is less. (This
essentially produces a "round robin" selection and does not
give any advantage based on available freespace.)
3. A good range is “50% * number of filesystems” for 2 VTE
systems and up to “75% * number of filesystems” for 4 or more
VTEs. This is just a guide based on field activity.
◆ RECOVER=nnn sets the percentage of disk space at which the
DLm starts to recover disk space by deleting the data from scratch
volumes. Valid values are from 0 to 100. The default is 85 percent.
Note: If the recovery percentage is set to 100, the DLm VTE never deletes
scratch volume data to recover disk space.
◆ RECOVERAMT=nn sets the maximum amount of space (in

percentage of disk space) that the DLm attempts to recover once
the recovery threshold is reached. The default is 5 percent.
◆ SIZE=xxx sets the maximum volume size for virtual tape
volumes. The valid range is 2 MB (2 megabytes) to 32 TiB (32
terabytes). The maximum allowable tape size for all drives is 32
TiB but is limited to the amount of available storage in the
filesystem. Since the maximum filesystem size in a DLm is 16 TiB,
a tape volume cannot be more than 16 TiB. You can specify a
single DEVICE, or ALL devices at the same time (the default). You
can specify the size in bytes, kilobytes, megabytes, gigabytes, or
terabytes.
For example:
"SIZE=1500000", "SIZE=500000K", "SIZE=500M",
"SIZE=1.5G", "SIZE=1T"
The new size specification takes effect immediately. If a tape is

being written at the time the SIZE is changed and the position on
the tape is already past the new SIZE value, DLm sends logical
end-of-volume warnings on all subsequent write/write tapemark
commands. DLm signals the physical end of the volume
approximately 1 MB past the current position.
Note: The SIZE= option is not allowed for SCSI tape devices.
◆ TIMESTAMPS=NO/YES indicates whether the date and time

should be included in each message that is sent to the console
display. The default is NO to reduce the amount of data
appearing on the console. Messages written to the log files are
always timestamped. This parameter affects only messages to the
console.
◆ TRACE=n sets the trace level for a specific device if you specify a
DEVICE=devicename. If SYSTEM is specified, the trace level is
set for the general, non-device-specific system trace. If ALL is
specified, the trace level is set for all devices plus the general
system trace at the same time. The default is ALL if no DEVICE is
specified. Valid trace levels are 0 (no tracing) to 5 (maximum
tracing); the default is 1 (trace errors only). This option affects

only the virtual tape application traces. “ENABLE” on page 184

provides information about enabling hardware trace in the
channel interface adapters.
◆ WARNING=nnn sets the percentage of disk space usage at which
the DLm VTE begins to warn about usage. The valid range is 0 to
100. The default is 75 percent.
SHOW SHOW CHANNEL ADAPTERS

SHOW REJECTED PATHS
Use the SHOW command to assist in debugging problems with the
configuration of the VTE or host devices. Following is the description
of options in the command:
◆ SHOW CHANNEL ADAPTERS displays information about all
channel adapters in the VTE.
◆ SHOW REJECTED PATHS displays connections that the host
has attempted to establish with the VTE, but which are not
configured.
SNMP SNMP [SET MESSAGE LEVEL [E | W | I]] | SHOW STATUS

SET MESSAGE LEVEL [E | W | I] allows the operator to set or
modify the SNMP message filter level to one of the following:
◆ E = Send error messages only
◆ W = Send error and warning messages (default)
◆ I = Send errors, warning, and informational messages
Configure SNMP as explained in “SNMP” on page 113.
SNMP SHOW STATUS shows the current SNMP settings.
STARTVT STARTVT
This command starts the virtual tape application on the VTE.
This command is only valid when the console window indicates that
the VT status is Not Running.
Once the VT application has initiated the VT Status indicates
Running. At this point, tape devices on this VTE may be varied
online on the mainframe.
STOPVT STOPVT[!]
This command stops the VT application running on the VTE.
This command is only valid when the console window indicates that
the VT status is Running.
This command causes all tape emulation to stop. To prevent input /
output errors from occurring on the mainframe, all tape devices on
this VTE should be varied offline before issuing the STOPVT
command.
STOPVT does not cause emulation to stop if any tape device on the
VTE is active. However, STOPVT! forces termination of the all tape
emulation regardless of the status of the tape devices. Stopping tape
emulation results in I/O errors and job termination on the mainframe
when tapes are actively being used when STOPVT! is issued.
STOP CHANNEL ADAPTER

STOP CHANNEL ADAPTER n
This command stops and takes out of service the specified FICON
channel adapter number n.
This command is rejected if any active paths established on this
adapter exist. Vary offline from the host all devices/paths/channels
attached to this adapter before invoking this command.
To bring the channel adapter back into service, use the RESET
CHANNEL ADAPTER command.
UNLOAD UNLOAD [DEVICE=]devicename

Use the UNLOAD command to perform a manual unload of the
specified virtual tape drive.
Entering the UNLOAD command for a virtual tape drive is
equivalent to pressing the Unload button on a physical tape drive.
Like a physical tape drive, the specified virtual tape drive must be in
the Not Ready state in order for the UNLOAD command to be
accepted as explained in “UNREADY” on page 204.
The UNLOAD command is executed immediately regardless of

Note: Unloading the tape results in an I/O error (Intervention Required) if

the host tries to read from or write to the drive after it is unloaded. For this
reason, use the UNLOAD command only in an emergency situation when a
tape volume is known and is not in use by a host application, but needs to be
unloaded immediately.
UNQUIESCE UNQUIESCE [ [DEVICE=]devicename | ALL | * ]

The UNQUIESCE command takes one or all of the virtual drives out
of the quiesced state. After being unquiesced, drives once again accept
mount requests. Any mount request that was ignored while a drive is
quiesced remains in a pending state; it is automatically retried when a
drive is unquiesced.
Unquiescing a drive does not send any signal to the host.
ALL and * are synonymous and mean unquiesce all drives at once.
UNREADY UNREADY [DEVICE=]devicename

Use the UNREADY command to change a virtual drive from the
Ready to the Not Ready (Intervention Required) state.
Using the UNREADY command for a virtual tape drive is equivalent
to pressing the Not Ready button on a physical tape drive.
The UNREADY command is executed immediately regardless of
Note: An I/O error (Intervention Required) occurs if the host tries to read
from or write to the drive when it is not ready. For this reason, use the
UNREADY command only in an emergency situation when a tape volume is
known and no host application is using it.
B
AWSTAPE Information
This appendix provides information on AWSTAPE:

◆ AWSTAPE format............................................................................. 206
AWSTAPE Information 205

AWSTAPE Information
AWSTAPE format
DLm stores virtual tape volumes on disk in the AWSTAPE format.
The AWS format allows DLm to maintain an exact representation of a
physical tape, including variable block sizes, tapemarks, labels, and
so on.
Each AWSTAPE disk file emulates one physical tape volume.
Each emulated physical record in the emulated tape volume is
represented by one or more pairs of block headers followed by data.
An emulated tapemark is represented only by a block header.
Figure 35 on page 206 illustrates an AWSTAPE disk file.
1 2 3 4 5 6 7 8
Physical Tape Volume data block tapemark
H H HH H H H HH H H
D 1 D 2 DD 3 D 4 D 5 D 6 DD 7 D 8 D
R R RR R R R RR R R
AWSTAPE-Single Disk File Representing One Physical Tape Volume GEN-001170
Figure 35 AWSTAPE single disk file
Data in an AWSTAPE data block is stored in the same format in

which the mainframe sent it. DLm does not convert any data that
passes through it in either direction. Data written by the mainframe is
stored unchanged in the virtual tape file, and returned to the
mainframe in exactly the same way.
Mainframe data is usually in the EBCDIC format. However, if the
mainframe application writes the data in ASCII mode, then the
AWSTAPE data block will contain ASCII data. In general, DLm
handles ASCII data in the same way it handles EBCDIC data or
binary data. The host software can write and read the data in the
desired format.
C
Load Display
Command—CCW
Opcode x'9F'
This appendix describes the Load Display command (CCW Opdcode

x’9F’). Major topics are:
◆ Load display messages.................................................................... 208
◆ Load display data............................................................................. 210
Load Display Command—CCW Opcode x'9F' 207

Load Display Command—CCW Opcode x'9F'
Load display messages

IBM-compatible 3480/3490/3590E tape drives support a Load
Display command (CCW Opdcode x’9F’) that is used to display
messages on the tape drive's LED display. The mainframe operating
system or the tape management system typically sends these
messages to request the operator to mount a specific volume.
DLm depends on the Load Display messages to determine when
virtual tape volumes should be mounted on its virtual tape drives.
When a VTE sees a Load Display message that it interprets as a
mount request of a specific VOLSER, it opens the volume's disk file
and makes the drive ready for the host, that is, it acts like a tape has
been mounted. If the VTE determines that the Load Display is
requesting a scratch volume, it identifies a suitable VOLSER and
opens the volume's disk file. The drive comes ready to the host. DLm
ignores any Load Display messages not determined to be a mount
message.
Since the Load Display messages are intended to be human readable,
they can possibly vary from mainframe system to system. DLm
requires a specific Load Display message format to determine that the
host is requesting a volume mount. Specifically, DLm has been
designed to recognize the Load Display Mount messages issued by
z/OS.
The format of the mount messages that DLm recognizes follows.
“Format Control Byte” on page 208 provides detailed information
about the Load Display messages format.
Format Control Byte DLm recognizes Function Select (bits 0–2) values of 000, 010, and 111
as potential mount messages.
Messages 0 and 1 If the Format Control Byte (FCB) Alternating Message bit (bit 3) is on,
0 is checked for a first mount message, then message 1.
If the FCB Alternating Message bit (bit 3) is off, the FCB Display
Low/High Message bit (bit 5) is checked to determine which message
(0 or 1) is to be checked for a mount message. If bit 5 is on, only
message 0 is checked for a mount message. If bit 5 is off, only
message 1 is checked for a mount message.
DLm recognizes a mount request by the EBCDIC character M in the

first position (byte 0) of the message. The EBCDIC VOLSER is located
in bytes 1–6 of the message. The last character (byte 7) of the message
is a label indicator. If byte 7 is EBCDIC A, an ANSI (ASCII) labeled
volume is being requested. If byte 7 is EBCDIC N, an unlabeled
volume is being requested; otherwise, a standard labeled tape is
presumed.
If the Load Display message does not pass all the tests to determine a
mount request, the message is simply ignored.
Load display messages 209

Load display data

Table 10 on page 210 provides information about load display.
Table 10 Load display data
Bits Description
0 Format Control Byte
1–8 Message 0
9–16 Message 1
Format Control Byte

Table 11 on page 210 describes the FCB.
Table 11 Format Control Byte (page 1 of 2)
Bits Value Description
0–2 Function select
000 The message specified in bytes 1–8 and 9–16 is maintained until the tape
drive next starts tape motion or the message is updated.
001 The message specified in bytes 1–8 is maintained until the tape cartridge is
physically removed from the tape drive or the next unload or load cycle.
010 The message specified in bytes 1–8 is maintained until the drive is next
loaded.
011 This value is used to physically access a drive without changing the message
display. This option can be used to test whether a control unit can physically
communicate with a drive.
100 to Reserved.
110
111 The message specified in bytes 1–8 and 9–16 is displayed. The message in
bytes 1–8 is displayed until a tape cartridge is physically removed from the
tape drive, or until the drive is next loaded. The message in bytes 9–16 is
displayed until the drive is next loaded (not including the loading of the cleaning
cartridge). If no cartridge is present in the drive, the first message is ignored
and only the second message is displayed until the drive is next loaded (not
including the loading of the cleaning cartridge).
Table 11 Format Control Byte (page 2 of 2)
Bits Value Description
3 Alternate messages
0 The tape drive displays only the message that is specified in bit 5.
1 The tape drive displays both messages specified in bytes 1–8 and 9–6,
respectively, alternating them on the message displays. The sequence repeats
until the message is replaced on the display. When bit 3 is set to 1, bits 4 and 5
are ignored.
4 Blink message
0 The message specified by setting bit 5 does not blink.
1 The message specified by setting bit 5 blinks repeatedly. When bit 3 is set to 1,
bit 4 is ignored.
5 Display low/high message
0 The message specified in bytes 1–8 is displayed. This bit is ignored if bit 3 is
set to 1.
1 The message specified in bytes 9–16 is displayed. This bit is ignored if bit 3 is
set to 1.
6 0 Reserved
7 0 Index automatic load (reserved)
The following are some sample Load Display messages. The hex
values are in EBCDIC:
48D4C2E3 F0F0F0F1 E2000000 00000000 00
Interpretation:
– Display message 0 (bytes 1–8) MBT0001S, blink, and retain
until loaded. In other words, mount volume BT0001.
Volume BT0001 is expected to be a standard labeled
volume.
– DLm would interpret this as a valid mount request for
standard labeled volume BT0001.
Load display data 211

28D9C2E3 F4F44040 40000000 00000000 00
Interpretation:
– Display message 0 (bytes 1–8) "RBT44," blink it, and retain
until the tape is removed from the drive. In other words,
Remove volume BT44.
– DLm would ignore this message because it is not a mount
request.
F0D9C2E3 F0F0F2F2 40D4C2E3 F2F7F2F7 E2
Interpretation:
– Display in an alternating fashion message 0 (bytes 1–8)
RBT0022 and message 1 (bytes 9–16) MBT2727S. Stop
displaying (or never display) message 0 when the tape is
removed from the drive. Stop displaying (or never display)
message 1 when the tape drive is next loaded. In other
words, remove volume BT0022, then mount volume
BT2727.
– DLm would interpret this as a valid mount request for
standard labeled volume BT2727.
D
Extract DLm statistics
This appendix describes how DLm maintains statistics files with

information about data throughput, virtual tape drive usage, and
virtual tape volume usage; the data can be extracted from the DLm
statistics files. Major topics are:
◆ DLm statistics files ........................................................................... 214
◆ Extraction utility............................................................................... 214
Extract DLm statistics 213

DLm statistics files

DLm statistics are kept in the following files:
◆ The first statistics file is /var/bti/stats/hourly. This file contains
overall DLm performance statistics. It contains minute-by-minute
read and write byte counts and hourly read and write block
counts, along with statistics such as the number of mounts and
peak number of drives in use in each hour.
◆ The second statistics file is /var/bti/stats/vstats. This file
contains statistics about every virtual tape mount and unmount,
including read and write byte and block counts.
Extraction utility
DLm is distributed with a Linux utility program that will extract the
statistics to a comma-delimited output format. The format of the
statfmt command line is:
statfmt [--help] [--hourly [--minutes]] [--mount] [--unmount] infile
Only one of the - -hourly (with or without - -minutes),

- -mount, or - -unmount options must be specified.
All fields that are either not applicable or not available (see notes
below) are output as -1.
The statfmt output is written to stdout.
Hourly statistics
To extract the hourly statistics, specify the - -hourly parameter. In this
case, the infile parameter must be a DLm hourly statistics file, that is,
/var/bti/stats/hourly.
If the optional - -minutes parameter is omitted, the following
comma-delimited fields are output to stdout:
Date — In the format MM/DD/YYYY.
Hour — In the format HH, where HH is 00-23.
Mounts — The number of successful mounts performed in this hour.
Drives — The maximum number of drives in use at any one time
within this hour.
BlocksRead — The number of tape blocks read by the host from

virtual tapes during this hour. This number does not include
tapemarks read.
BlocksWritten — The number of tape blocks written by the host to
virtual tapes during this hour. This number does not include
tapemarks written.
BytesRead — The number of bytes read by the host from virtual
tapes during this hour. This number reflects the uncompressed data
delivered to the host.
BytesWritten — The number of bytes written by the host to virtual
tapes during this hour. This number reflects the uncompressed data
delivered from the host.
If the optional - -minutes parameter is specified, the following
additional comma-delimited fields are output for each minute of the
hour, where [MM] is the minute (00-59):
BytesRead[MM] — The number of bytes read by the host from
virtual tapes during this minute. This number reflects the
uncompressed data delivered to the host.
BytesWritten[MM] — The number of bytes written by the host to
virtual tapes during this minute. This number reflects the
uncompressed data delivered from the host.
If no virtual tape activity occurs within a given hour, the statistics
record for that hour is omitted.
Volume statistics
To extract the volume statistics, specify the - -mount or - -unmount
parameter. In either of these cases, the infile parameter must be a
DLm volume statistics file, that is, /var/bti/stats/vstats.
Extraction utility 215

Mount statistics
If the - -mount parameter is specified, the following
comma-delimited fields are output for each virtual tape mount
recorded in the statistics file:
Time — In the format HH:MM:SS in 24-hour time.
Volser — Volume serial number; for scratch tapes, this is the actual
volume that was mounted.
Device — DLm device name.
Error — For a successful mount, this will be zero; for an unsuccessful
mount, that will be non-zero.
Scratch — For a scratch mount, this will be 1; for non-scratch
mounts, this will be zero.
Created — If the volume was created in response to the mount
request, this will be 1; otherwise, zero.
Protected — If the volume was mounted read-only ("ring out"), this
will be 1; otherwise, zero.
Howlong — How long it took to perform the mount, in milliseconds.
Filesize — The size of the virtual tape volume, in bytes, at the time it
was mounted.
Unmount statistics
If the - -unmount parameter is specified, the following
comma-delimited fields are output for each virtual tape unmount
recorded in the statistics file:
Time — In the format HH:MM:SS in 24-hour time.
Volser — Volume serial number; for scratch tapes, this is the actual
volume that was mounted.
BlocksRead — The number of tape blocks read by the host from this
virtual tape during this mounting. This number does not include
tapemarks read.
BytesRead — The number of bytes read by the host from this virtual
tape during this mounting. This number reflects the uncompressed
data delivered to the host.
BlocksWritten — The number of tape blocks written by the host to
this virtual tape during this mounting. This number does not include
tapemarks written.
BytesWritten — The number of bytes written by the host to this
virtual tape during this mounting. This number reflects the
uncompressed data delivered from the host.
LowWrite — The lowest byte offset where a host write, write
tapemark, or erase was performed to this virtual tape during this
mounting. If no data was written to the tape, -1 will be output to
distinguish it from a write at loadpoint.
Filesize — The size of the virtual tape volume, in bytes, at the time it
was unmounted. If no writes were performed during this mounting,
-1 is output to distinguish that the file is unchanged.
GoodLocates — The number of locates performed to valid block IDs
during this mounting.
BadLocates — The number of locates performed to invalid block IDs
during this mounting.
volumesMounted — The number of concurrent tape mounts there
at the time of that volume allocation (whether its read or write).
pendingMounts — The number of outstanding mounts that have
not been serviced at the volume allocation time. Usually these
mounts only last a few seconds.
Example 1
# statfmt --hourly /var/bti/stats/hourly
statfmt - DLm statistics extractor, version 5.00-24.
Copyright (c) 2007
input file is '/var/bti/stats/hourly'
Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-
BytesRead,BytesWritten
09/21/2007,14,4,1,-1,-1,968,0
09/21/2007,16,7,2,-1,-1,6198537240,1102968477
09/21/2007,17,4,2,-1,-1,7585128104,1100001400
09/22/2007,15,1,1,-1,-1,0,0
09/23/2007,21,3,3,-1,-1,1000480,1000400
09/23/2007,22,4,4,69,68,1000480,1000400

Example 2
# statfmt --hourly --minutes /var/bti/stats/hourly
Copyright (c) 2007
input file is '/var/bti/stats/hourly'
Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-
BytesRead[00],BytesWritten[00],BytesRead[01],BytesWritten[01],-
BytesRead[58],BytesWritten[58],BytesRead[59],BytesWritten[59]
09/21/2007,14,4,1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
240,0,0,0,0,0,240,0,240,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,248,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0
09/21/2007,16,7,2,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,160,533,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,160,-
370400240,0,531456000,176928720,198145160,287040160,82320,-
305952000,0,292832800,1016128,305952000,0,291872800,1868096,-
306752000,0,305700640,0,308448000,0,306336000,0,308448000,0,-
307168000,0,306880000,0,305056000,0,307776480,0,299392000,0,-
296288160,0,293440080,0,293056000,0,296480000,0,296737080,0
09/21/2007,17,4,2,-1,-1,0,0,0,0,0,0,0,0,0,0,160,216416240,248,-
516192000,63008720,367393160,305056248,0,293248240,0,-
271232000,0,301632008,0,306016000,0,308000000,0,305184000,0,-
306884640,0,306656000,0,299744000,0,291392000,0,293248000,0,-
293664000,0,291360000,0,293344640,0,290784080,0,288704080,0,-
295904080,0,296832160,0,298144080,0,295968080,0,289984240,0,-
291168240,0,295360000,0,297920080,0,114688080,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0
09/22/2007,15,1,1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0
09/23/2007,21,3,3,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
1000480,1000400,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
09/23/2007,22,4,4,69,68,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1000480,-
1000400,0,0,0,0,0,0,0,0,0,0,0,0
Example 3
# statfmt --mount /var/bti/stats/vstats
Copyright (c) 2007
input file is '/var/bti/stats/vstats'
Date,Time,Volser,Device,Error,Scratch,Created,Protected,-
Howlong,Filesize
09/21/2007,14:16:28,2500,N47061,0,0,0,0,47,5571614
09/21/2007,14:19:04,2500,N47061,0,0,0,0,37,5571614
09/21/2007,14:20:49,2500,N47061,0,0,0,0,8,5571614
09/21/2007,14:40:06,2500,N47061,0,0,0,0,119,5571614
09/21/2007,14:43:42,2500,N47061,0,0,0,0,38,5571614
09/21/2007,14:44:30,2500,N47061,0,0,0,0,6,5571614
09/21/2007,14:52:02,2500,N47061,0,0,0,1,73,106478280
09/21/2007,16:27:00,2500,N47062,0,1,0,0,274,184
09/21/2007,16:28:48,2500,D3L063,1,0,0,0,-1,-1
09/21/2007,16:37:18,2404,N47063,0,1,0,0,281,184
09/21/2007,16:40:03,2502,N47064,0,1,0,0,240,184
09/21/2007,16:42:33,250A,N47064,0,0,0,0,2,7880
09/21/2007,16:42:38,2501,N47064,0,0,0,0,1,15329
09/21/2007,16:44:23,2500,N47064,0,0,0,0,3,38466
09/21/2007,16:44:27,2500,N47064,0,0,0,0,2,61593
09/21/2007,17:05:37,2404,N47065,0,1,0,0,239,184

09/21/2007,17:06:21,2500,N47061,0,0,0,1,4,106478280
09/21/2007,17:08:13,2500,N47061,0,0,0,1,29,106478280
09/21/2007,17:09:34,2500,N47061,0,0,0,1,11,106478280
09/22/2007,15:32:50,2500,N47061,0,0,0,1,37,106478280
09/23/2007,21:08:08,2400,N47066,0,1,0,0,300,184
09/23/2007,21:08:10,2401,N47067,0,1,0,0,219,184
09/23/2007,21:09:43,2402,N47068,0,1,0,0,222,184
09/23/2007,22:53:03,2500,N47069,0,1,0,0,243,184
09/23/2007,22:53:08,2502,N47070,0,1,0,0,225,184
09/23/2007,22:53:11,2506,N47071,0,1,0,0,223,184
09/23/2007,22:53:36,2402,N47072,0,1,0,0,434,184
Example 4
# statfmt --unmount /var/bti/stats/vstats
Copyright (c) 2007 .
input file is '/var/bti/stats/vstats'
Date,Time,Volser,BlocksRead,BytesRead,Blockswritten,-
BytesWritten,LowWrite,Filesize,GoodLocates,BadLocates
09/21/2007,14:16:30,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:19:05,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,14:20:51,N47061,5,256,0,0,-1,-1,0,0
09/21/2007,14:40:07,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:43:43,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:44:31,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:52:11,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,16:27:01,N47062,2,160,6,533,0,593,0,0
09/21/2007,16:40:10,N47064,2,160,10,82320,0,7880,0,0
09/21/2007,16:42:36,N47064,5,400,7,82080,7690,15329,0,0
09/21/2007,16:42:41,N47064,5,400,59,934048,15139,38466,0,0
09/21/2007,16:44:26,N47064,5,400,59,934048,38276,61593,0,0
09/21/2007,16:44:30,N47064,5,400,59,934048,61403,84786,0,0
09/21/2007,17:04:03,N47063,231018,7391304720,34381,-
1100001400,0,1100207710,0,0
09/21/2007,17:06:31,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,17:08:24,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,17:11:17,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,17:33:22,N47065,237081,7585127360,34381,-
1100001400,0,1100207710,0,0
09/22/2007,15:33:30,N47061,0,0,0,0,-1,-1,0,0
09/23/2007,21:09:43,N47068,69,1000480,68,1000400,0,85185,0,0
09/23/2007,22:28:23,N47066,0,0,0,0,-1,-1,0,0
09/23/2007,22:28:24,N47067,0,0,0,0,-1,-1,0,0
09/23/2007,22:53:37,N47072,69,1000480,68,1000400,0,85185,0,0
09/24/2007,12:08:18,N47071,0,0,0,0,-1,-1,0,0
09/24/2007,12:08:18,N47069,0,0,0,0,-1,-1,0,0
09/24/2007,12:08:18,N47070,0,0,0,0,-1,-1,0,0
E
System Messages
This appendix lists the DLm system, EMCvts, and z/OS system
messages. The major topics are:
◆ Message format ................................................................................ 222
◆ DLm system messages .................................................................... 223
◆ Call home messages......................................................................... 366
◆ EMCvts messages ............................................................................ 367
◆ z/OS system messages.................................................................... 369
◆ VTEC errors that generate ConnectEMC events ......................... 374
System Messages 221

System Messages
Message format
The EMC DLm system message format is:
DLmxxxy
where:
xxx = message number
y = message class:
I (Informational)
W (Warning)
E (Error)
System Messages
DLm system messages

This section lists the DLm system messages, a description, the system
action, and the recommended user action.
DLm000I <debugging message>
Description: Various debugging messages are displayed if the DLm

application's debugging level is set to 1 or higher.
System action: None.
User action: You really should not be seeing any DLm000I messages
unless you have invoked a debugging mode. For best performance,
debugging should be left off unless directed otherwise by EMC
Customer Support. Type the command SET DEBUG=0 to turn
debugging off.
DLm010I Compression hardware [not] available
Description: Reports the availability of a hardware compression card

in the DLm.
System action: If a hardware compression card is present (and is not
disabled through configuration or operator command), the card is
used for compressing and decompressing virtual tape data.
User action: None.
DLm011I Compression driver version: x.x.x
Description: Displays the version number of the EMC hardware

compression card driver.
User action: None.
DLm012I Compression card #n:id=xx version=nnn state=xxxxxxxx
Description: Displays information about the hardware compression

cards installed in the DLm.
User action: None.
DLm system messages 223

System Messages
DLm013I Hardware compression/decompression set ON/OFF
Description: Reports the status of the DLm hardware compression

and decompression features.
User action: None.
Dlm014E Unknown hardware compression card, id=0xXXXX
Description: The identity of the hardware compression adapter

cannot be determined.
System action: Hardware compression and decompression will not
be available until the problem is resolved and the controller is
restarted.
User action: Contact EMC Customer Support for additional
assistance.
DLm015E Hardware compression driver error
Description: An error has occurred while initializing the DLm

hardware compression adapter.
System action: Hardware compression and decompression are not
available until the problem is resolved and the DLm is restarted.
User action: Contact EMC Customer Support for assistance.
DLm016E Device <devicename> Error opening hardware compression

driver: <error message>
Description: An error has occurred when opening the DLm

hardware compression adapter.
System action: Hardware compression and decompression are not
available for this device until the problem is resolved and the DLm is
restarted.
System Messages
DLm018E Error creating <processname> Thread: <error message>
Description: This internal error can only occur during application

startup.
System action: Application startup terminates.
DLm019E Error allocating memory for <name>: <error message>
Description: An internal memory allocation error has occurred in the

DLm application.
System action: Depending on the error, the DLm may abend or need
to be restarted to regain some functionality.
DLm020E Cannot verify <feature> license: <error message>
Description: The DLm was unable to validate the license for the
specified feature.
System action: The specified feature is not available.
DLm021E <parameter=value> incompatible with <license> license
Description: The specified parameter is not compatible with the

specified licensed feature.
System action: If the error is in the configuaration file, the application
startup terminates. If the error is in a SET command the command is
rejected.
User action: Contact EMC Customer Support for additional
assistance.
DLm022E Unable to find userid 'vtape'
Description: The DLm application must run under the user ID

'vtape,' but this user ID does not exist on the DLm.

System Messages
DLm023E Unable to switch to user and group 'vtape'
Description: The DLm application must run under the user ID

'vtape,' but the application was unable to switch to this ID.
DLm024E Program not started with effective userid 'root'
Description: The DLm application must be started under the userid

'root.'
DLm025E Invalid license combination, EMC+OEM.
Description: The combination of license files on the system is not

valid.
DLm026E Pid file <filename> must be full path name. Use -? f
Description: The command that starts the DLm virtual tape

application contains an invalid argument.
DLm027E Failed to fork daemon: <error message>
Description: The DLm application failed to daemonize itself.

DLm028E Internal Error calling setsid: <error message>

System Messages
DLm029E Internal Error changing working directory to '/': <error

message>

DLm030I Traces are [un]buffered
Description: The DLm application trace files are buffered (saved in

memory and written to disk periodically) by default for better
performance. If the environment variable BTITRACEUNBUFFERED
has been set to any value when the DLm application starts, trace files
are written in an unbuffered manner (every event is written to disk
immediately).
User action: The buffered default should be sufficient for most
tracing needs, unless directed otherwise by EMC Customer Support.
When traces are buffered, make sure to type the DLm command Save
Trace to write all trace buffers to disk before examining or copying
the trace files.
DLm031E Cannot Create PID file <filename>: error message
Description: The application failed to to create the process ID file.

DLm032E Trace task error reading pipe, errno=0x<xx> (<nnn>)
Description: An I/O error has occurred during DLm device tracing.

System action: The DLm attempts to continue tracing. One or more
events may be lost from the DLm device trace.

System Messages
DLm033E Error writing to <file type> file <filename>:<error

message>
Description: An I/O error occurred when writing to the specified

file.
System action: The DLm application continues running without
writing additional messages to the specified file.
User action: See any earlier messages and the 'error message' portion
of this message to determine the cause of the failure. If the problem
cannot be corrected, contact EMC Customer Support for assistance.
DLm035E Error creating directory 'directory': <error message>
Description: The specified DLm directory did not exist, and the DLm
application was not able to create the directory. This error can only
occur during application startup.
DLm036E Error closing <file type> file <filename>: <error

message>
Description: The specified file was not successfully closed. The 'error
message' text explains the reason for the failure.
System action: None
User action: If you are unable to correct the problem, contact EMC
DLm037E Error creating/opening <feature> message pipe: <error

message>
Description: An error occurred while initializing the specified

feature. This error can only occur during application startup.
System action: The DLm startup terminates or continues without the
specified feature. The 'error message' text explains the reason for the
failure.
System Messages
DLm038I Creating directory 'directory'
Description: The specified DLm directory did not exist, so the DLm
is now creating the directory.
System action: The specified directory is created.
User action: None.
DLm039E Error opening output <file type> file <filename>: <error

message>
Description: The specified output file was not successfully opened.

This error can only occur during application startup.
System action: Application startup terminates. The 'error message'
text explains the reason for the failure.
DLm041E Device <devicename> error <nnn> going online
Description: The specified device was not able to go online to the

channel. This error can only occur during application startup.
User action: Verify in the DLm configuration file that the channel
configuration data for the specified device is correct. If the problem
recurs, contact EMC Customer Support for assistance.
DLm042E Error <nnn> going live to channel. Interface=n,

slot=nnnnnn
Description: The channel interface number 'n' was not able to go

online to the channel.
System action: This channel interface is out of service until the
problem is corrected and the adapter is reset.
User action: The \RESET CHANNEL ADAPTER\ command might
be able to bring this adapter online. Contact EMC Customer Support
for more assistance.

System Messages
DLm044W WARNING: /var filesystem usage at nn%
Description: The specified critical system filesystem is starting to run

low in free disk space. If this filesystem were to fill, it might have a
detrimental affect on the system operation.
System action: Warning messages will continue to be displayed at
every percentage of change in usage as long as the usage exceeds the
designated warning level.
User action: Contact EMC Customer Support for assistance in freeing
space on the designated filesystem.
DLm045E Error getting status of <filesystem> filesystem: <error

message>
Description: An unexpected error occurred while trying to get

information about the specified filesystem.
System action: The system will continue to run, but some features
(such as warnings about the capacity limits of certain filesystems)
may not be functional.
User action: If this problem recurs, contact EMC Customer Support
for assistance.
DLm046W /var has <nnn> remaining bytes, debugging messages turned

off
Description: A debugging mode that writes messages to the console

log is active, and the /var filesystem, where the messages are stored,
is starting to fill.
System action: The debugging mode is turned off to suppress further
debugging messages.
User action: Contact EMC Customer Support for assistance in freeing
space on the designated filesystem.
DLm047E Internal Error <function>: <error message>
Description: An internal error has occurred.

System action: The function listed cannot be completed.
System Messages
DLm048E Internal Error <process>: <error message>
Description: An internal error has occurred.

System action: Application terminates.
DLm050E Invalid command line parameter: <value>. use -? for help
Description: The command line that starts the DLm application

contains an invalid argument.
User action: Correct the command line arguments and restart the
DLm application.
DLm052E Invalid command line Configuration File Name parameter:

<value>. Use -? for Help
Description: The command line that starts the DLm application

contains an invalid argument.
User action: Correct the command line arguments and restart the
DLm application.
DLm055E Error getting channel driver version number
Description: The DLm application was unable to determine the

version of the EMC channel adapter driver.
DLm056I Channel driver version is x.x.x
Description: Displays the version number of the EMC channel

adapter driver.
User action: None.

System Messages
DLm057E This application requires minimum channel driver version

x.x.x!
Description: The EMC channel adapter driver is below the minimum

release level required by this version of the DLm application.
Message DLm056I that precedes this message identifies the channel
adapter driver currently loaded.
DLm058I Device <devicename> MIHn set to nnn seconds
Description: The MIH (Missing Interupt Handler) timeout value that

DLm reports to the Host has been set to the specified value. MIHn
will be MIH1 or MIH2. MIH1 is the primary or fast MIH value that
most Host operating systems use for most CCWs, such as reads and
writes. MIH2 is the secondary or slow MIH value that some Hosts
use for certain long-running CCWs such as Locate, FSF, and Data
Security Erase commands. By default, DLm sets these values to 3000
and 18000 seconds, respectively.
System action: The specified value is reported to the Host on the next
Read Configuration Data command.
User action: None.
DLm060E There is already an instance of <program> running
Description: Another copy of the DLm application is currently

running.
System action: The second copy of the DLm application terminates.
User action: Make sure that the application is not already running
before starting a second copy.
DLm061E Cannot register <function> handler:<error message>

startup.
System Messages
DLm062E Error opening Alert FIFO <filename>: <error message>
Description: The DLm application was not able to open the pipe over
which it receives Alert (error and warning) information from the
channel adapter drivers.
System action: The DLm continues to function, but channel adapter
alerts are not noted by the DLm.
DLm064E Alert FIFO has been closed
Description: The EMC channel driver has closed the pipe over which
it sends alert messages, which are warning and error messages about
channel adapter problems, to the DLm application.
DLm065E Invalid data (nn bytes) read from Alert FIFO
Description: The EMC channel driver has sent an unrecognized alert

message to the DLm application.
DLm066E Error creating/opening Read named pipe <filename>: <error

message>

startup.

System Messages
DLm067I BusyType set to Busy/Immediate/Deferred
Description: DLm can be configured to send various status codes to

hold off the host under busy conditions. The default is to send a true
busy signal.
System action: DLm sends a busy status if BusyType is set to "Busy",
an immediate command retry for "immediate", and a deferred
command retry for "deferred".
User action: None. Do not change this setting unless directed to do so
by EMC Customer Support. This setting could cause channel errors.
DLm068I Double testing of compressed data set ON/OFF
Description: By default, the DLm application performs an extra CRC

check of data that has been compressed before writing it to the tape
library.
System action: If this option is ON (the default), the data is checked
just before it is written to the library. If a discrepancy is found, an
error is returned to the Host's write command. If this option is turned
OFF, no extra integrity check is performed.
User action: It is recommended that this option always be left ON.
DLm069I Resetting Events will [not] be sent to firmware
Description: A resetting event is any event that resets a DLm device's

pathgroup ID or assignment, such as a system or selective reset or
restarting of the DLm. Normally, after a resetting event has occurred
the next command sent by the Host receives a resetting event unit
check to notify the Host that the resetting event occurred. The Host
should respond appropriately by restoring the device's pathgroup ID
and assignment information, and reissue the unit-checked command.
In addition, some channels expect a low-level indication that a
resetting event has occurred. By default, the DLm sends this special
indication to the channel along with the unit check. For exceptional
conditions, the NAS can be configured to NOT send the low-level
resetting event indication to the channel when it sends a resetting
event unit check to the Host. This message is displayed at DLm
startup and whenever the low-level channel resetting event
notification option is switched on or off.
System action: Low-level channel resetting event status are not sent
to the channel when this option is set OFF.
System Messages
User action: None. Under normal conditions, the low-level channel

resetting event indication should NOT be configured OFF. Under rare
conditions, a channel may not correctly handle the low-level channel
resetting event indicator, and channel errors may occur. In this case,
consult EMC Customer Support before configuring this option
off.\n". Also see message DLm082I.
DLm070I <emulation type> emulation version set to n
Description: The DLm is configured to invoke the specified channel

adapter emulation version.
User action: None.
DLm071E No channel interface cards present!
Description: No channel interface adapters were detected in the

system. This error can only occur during application startup.
DLm072E This application requires minimum firmware version %d!
Description: The firmware in a channel adapter is below the

minimum release level required by this version of the DLm
application. Message DLm075I that precedes this message identifies
the channel adapter in question.
DLm073E Interface #<n> (slot <nnnnnn>) returned bad status =

<nnn>
Description: The specified channel interface adapter returned an

error status to the application. This error can only occur during
application startup.

System Messages
DLm074E Interface #<n> (slot <nnnnnn>) error getting <adapter

info>
Description: The specified channel interface adapter returned an

error status to the application. This error can only occur during
application startup.
DLm075I Interface #n: n (0xxxxxx) bus:n slot:n type:n

(adaptertype) media:n (mediatype)
Description: Displays information about the channel interface

adapters in the DLm. This message is displayed at application startup
and in response to the QUERY ALL or QUERY CHANNEL
ADAPTER command.
User action: None.
DLm076I Interface #n: [hardware s/n | s/n override] xxxxxxxxxxxx

ADAPTER command.
User action: None.
DLm077I Interface #n: Firmware emulation type: XXXX, version:

nnnn yyyy/mm/dd

ADAPTER command.
User action: None.
System Messages
DLm078I Disk usage WARNING level set to nn%
Description: The DLm is configured to warn about tape library disk

utilization when usage reaches nn percent full.
User action: None.
DLm079I Disk space RECOVER level [set to nn%]/[is N/A]
Description: The DLm is configured to start erasing scratch tape

volumes to recover disk space when disk utilization reaches nn
percent full. If is N/A is displayed, the erase policy is set to a
Time-to-live policy rather than a space-usage policy, so the
RECOVER setting is irrelevant.
User action: None.
DLm080I Device <devicename> UNISYS detected
Description: The DLm has detected that the specified virtual device
is attached to a Unisys Host. This message is displayed once for each
virtual device attached to a Unisys.
System action: The DLm automatically makes accommodations for
the differences between an IBM and a Unisys Host.
User action: None (unless the Host is not actually a Unisys Host, in
which case EMC Customer Support should be contacted for
assistance).
DLm081I Interface #n: Current state <state>; Desired state

<state>

ADAPTER command.
User action: None.

System Messages
DLm082I Resetting Events will [not] be ignored
Description: A resetting event is any channel event that resets a DLm

device's pathgroup ID or assignment, such as a system or selective
reset or restarting of the DLm. Normally, after a resetting event has
occurred, the next command sent by the Host receives a resetting
event unit check to notify the Host that the resetting event occurred.
The Host should respond appropriately by restoring the device's
pathgroup ID and assignment information, and reissue the
unit-checked command. Occasionally, especially with older
stand-alone IPL programs, a Host may not handle a resetting event
unit checked correctly. In this case, the DLm can be configured to
NOT send resetting event unit checks. This message is displayed
when resetting event notification is turned on or off.
System action: Resetting event unit checks are not sent to the Host
when this option is set.
User action: None. Under normal conditions, the DLm should NOT
be configured to ignore resetting events. Doing so can cause problems
when varying on devices to a Host that properly handles, and
actually expects, resetting event unit checks. Contact EMC Customer
Support for more information.
DLm083I Compression level set to n (0=none,1=faster,9=smaller)
Description: Displays the compression level set by default, in the

configuration file, or by the SET COMPRESSION command. The
compression level ranges from 0 (no compression at all) to 9
(maximum compression with maximum overhead). The default
compression level is 1 (minimum compression with minimum
overhead).
User action: None.
DLm084I Disk space RECOVERAMT set to nn%
Description: The DLm is configured to stop erasing scratch tape

volumes to recover disk when disk space usage falls to (RECOVER
minus RECOVERAMT) percent.
User action: None.
System Messages
DLm085I <feature> support enabled
Description: This message displays if support for an optional feature

has been enabled in the configuration file.
System action: The optional feature is enabled.
User action: None.
DLm087I Checking of CRCs from channel set ON|OFF
DLm088I Sending of CRCs to channel set ON|OFF
DLm089I UNISYS set ON/OFF for device <devicename> / ALL devices
Description: The SET UNISYS command has been accepted for a

device or all devices.
System action: The DLm adjusts the differences between an IBM and
a Unisys Host for the specified devices.
User action: None (unless the Host is not actually a Unisys Host, in
which case you should not do this).
DLm090I AMDD feature turned ON/OFF [for device devicename]/[for

all devices]
Description: The AMDD feature has been set ON or OFF.

User action: None.
DLm091I AMDD pad boundary set to <nnn>
Description: The AMDD pad boundary has been set to the

designated value.
User action: None.
DLm092E SET AMDD cannot specify a specific device
Description: AMDD is a global setting and cannot be SET by

individual device.
System action: The SET command is ignored.
User action: None.

System Messages
DLm096I Erase Policy: [TTL for <nn> hours/days] [Space needed]
Description: This message displays the current erase policies for this
controller. Space needed indicates that the erase policy is to erase
scratch tapes when the tape library disk usage reached the RECOVER
setting. TTL indicates that the erase policy is to erase scratch tapes as
soon as they reach the age specified in hours or days.
User action: None.
DLm097I Maximum TTL Erase Time set to <nn> seconds
Description: This message displays the current maximum amount of

continuous time that the application will spend erasing scratch tapes
that have exceeded the TTL erase policy period. If the TTL erase time
is exceeded, the application stops erasing for a short period before
resuming erasing. The default time is 30 seconds.
User action: None.
DLm098I Encryption initialized, <#keys> keys ready
Description: Encryption capability was initialized successfully, with

<#keys> keys available for encryption and decryption.
User action: None.
DLm099I New mount on already-mounted drive will be allowed
Description: The DLm system has been explicitly configured to

honor a mount request for a drive that already has a virtual tape
volume mounted.
System action: If the DLm receives a mount request on a drive that
already has a tape mounted, and the drive had received an Unassign
command from the host while that tape was mounted, DLm unloads
the tape and honors the new mount request.
User action: None. This option is not recommended except in specific
circumstances. Contact EMC Customer Support for more assistance.
System Messages
DLm100I Configuration file opened: <filename>
Description: The specified input configuration file was successfully

opened.
User action: None.
DLm101W Missing or invalid file \/etc/bti/ximl\, using config

file \/etc/bti/xmap0\
Description: The file /etc/bti/ximl should contain the name of the

configuration file that the DLm loads at startup. If /etc/bti/ximl does
not exist, the DLm loads the default configuration file
/etc/bti/xmap0.
System action: The default configuration file, /etc/bti/xmap0, is
used.
User action: The /etc/bti/ximl file should normally point to the
desired DLm configuration file. Reconfigure the DLm and \Select
Configuration for Next Startup\ to identify which of the four DLm
configuration files you want to use. Contact EMC Customer Support
if this problem recurs.
DLm102I Configuration file is <filename> [(changed!)]
Description: Displays the name of the configuration file currently in

use. \(changed!)\ means that the configuration file has changed since
the last DLm startup.
User action: None.
DLm104W Device <devicename> Warning. no tapelib found for

path:dir:<directory>
Description: During logging of volume statistics, the specified

directory was not found.
System action: The volume statistics record will not be recorded.

System Messages
DLm105E <command> command is no longer supported
Description: The DLm application no longer supports this command.

System action: None; the command is ignored.
User action: None.
DLm109I Scratch mounts will [not] ignore full filesystems

(UseFullFS=TRUE/FALSE)
Description:By default, filesystems with less than a full tape's worth

(based on the current SIZE= value) will be skipped when searching
for a scratch tape. This option can be overridden with the UseFullFS
TRUE configuration option or SET UseFullFS=TRUE command.
System action: Unless overridden, full filesystems will be bypassed
when a scratch tape mount is requested.
User action: None.
DLm110I Channel adapter firmware tracing by DEVICE/PATH
Description: The DLm has been configured to trace channel adapter

activity on a \Device\ or \Path\ basis. When tracing by Device, all of
the activity for a given device on all of that device's channel paths are
traced in a common trace buffer per device; the advantage is an
overall larger trace buffer per device; the disadvantage is that a lot of
activity on other channel paths can cause loss of trace entries for
events that occurred on another path. When tracing by Path, each
channel path per device has an independent trace buffer. The
advantage is that activity on one channel path cannot cause loss of
trace events on another channel path, but the overall size of the trace
buffer (per path per device) is smaller than with a full device trace.
User action: None.
System Messages
DLm111I Maximum tape block size set to nnn
Description: The DLm has been configured to support a maximum

tape block size different from the default of 256K.
System action: The DLm supports the host reads and writes up to the
specified block size.
User action: None. Do not change this setting unless directed to do so
by EMC Customer Support.
DLm112I Using NEW/FAST scratch search method
Description: The DLm application has been explicitly configured to

support either the standard documented scratch tape allocation
technique ("NEW") or an alternative faster method that ignores
scratch tapes' last-used dates.
System action: The DLm application will use the technique
described. The default method is "NEW".
User action: None.
DLm113E Using DEFAULT/RR method of filesystem allocation
Description: If "RR", the virtual tape application has been explicitly

configured to select filesystems in a round robin fashion when
allocating a scratch tape, as opposed to the default method which is
to pick the filesystem with the most free space.
System action: The application will use the technique described.
User action: None.
DLm114I ScratchSearchMethod=OLD is no longer a supported option
Description: The value "OLD" was specified for the

ScratchSearchMethod parameter. This value is no longer supported.
System action: The DLm uses the "NEW" (default) technique.
User action: Contact EMC Customer Support for more information.

System Messages
DLm115E Error returned from fsync. fd n. <description> file

<filename>: error <error message>
Description: Error returned from fsync.

System action: The specified file was not successfully fsynced.
Support for assistance.
DLm116I Query Space timeout set to <nnn> minutes
Description: The system is configured to wait <nnn> minutes for a

query space to complete. If query space does not complete within this
time, an error indication is displayed on the console.
User action: None.
DLm117I Query Space <status>
Description: If the Query Space is invoked while it is running an

<already in progress> message will be displayed. If the Query Space
exceeds the QSPACETIMOUT a <has exceeded the timeout value>
message will be displayed
User action: None.
DLm119E Error reading configuration file <filename> line nnn:

<error message>
Description: An I/O error occurred while reading the specified

configuration file.
User action: Use the DLm configuration program to reconfigure and
save the specified DLm configuration file. If the problem persists,
contact EMC Customer Support for assistance.
DLm121E Cannot open configuration file <filename>: <error

message>
Description: The specified configuration file was not successfully

opened.
System Messages

save the specified DLm configuration file. If the problem persists,
DLm122E No devices defined in configuration file
Description: There were no virtual tape drives configured in the

DLm configuration file.
save the DLm configuration file. If the problem persists, contact EMC

System Messages
DLm123E Error in config file, line nn: Unrecognized keyword

'<keyword>'
Description: The DLm configuration file contained an error.

save the DLm configuration file.
DLm124E Error in config file, line nn: Incorrect number of

<keyword> parameters

DLm125E Error in config file, line nn: Invalid <keyword> value

'<value>'

DLm126E Maximum number of devices (nnn) exceeded, terminating
Description: Too many devices have been defined in the

configuration file.
System action: Startup terminates.
User action:Use the configuration program to reconfigure with a
valid number of devices.
DLm129E Error in config file, line nn: <value> is not a valid

parameter

System Messages
DLm130E Error in config file, index xx: <value> is not a valid

parameter

DLm131E Error in config file, line nnn: No <keyword> parameter

DLm132E Error in config file, line nnn: Duplicate <keyword>

parameters

DLm134E Duplicate INDEX=0xXX in configuration file, line nnn

DLm135E Error attaching device index xx


System Messages
DLm137W Invalid TRACE= value 'value'

System action: DLm startup continues with the default value of 1.
DLm140E Error in config file, line nnn: <feature> not supported
Description: The DLm configuration file contains parameters for a

feature that is not licensed for use on this DLm.
System action: DLm startup terminates.
User action: Contact EMC for more information on enabling the
licensed feature.
DLm144E Duplicate NAME=value in configuration file, line nn

DLm155I Device <devicename> data path='<pathname>' [by default][,

volser prefix=<volid>]
Description: The specified pathname is the base tape library

directory for this device; virtual tape volumes for this device resides
in this directory and its immediate subdirectories. '[by default]'
signifies that PATH= was not specified for the device and it was set to
the standard default value; otherwise, PATH=pathname was
explicitly set in the device configuration. If a volser prefix is shown, it
signifies that virtual tape volumes that begin with the prefix <volid>
automatically creates as needed by the DLm, if they have not been
pre-initialized.
User action: None.
System Messages
DLm156W Device <devicename> Data path <pathname> is not

accessible!
Description: The specified virtual tape library directory cannot be

accessed.
System action: During system startup, this is a warning message and
application startup continues. However, no virtual tape volumes that
reside in this directory can be mounted on this drive until the
specified directory is made accessible. If this error occurs when
processing a SET PATH command, the SET PATH command fails
and the current tape library path is not changed.
User action: If the configured directory name is correct, make sure
that it is mounted and accessible to the user 'vtape.' If the directory
name was misconfigured, correct the PATH= parameter in the DLm
configuration file and restart the DLm application.
DLm157W Device <devicename> tapelib subdirectory 'xxx' is not

accessible!
Description: The specified virtual tape library subdirectory cannot be

accessed.
System action: During system startup, this is a warning message and
application startup continues. However, no virtual tape volumes that
reside in this subdirectory can be mounted on this drive until the
specified subdirectory is made accessible. If this error occurs when
processing a SET PATH command, the SET PATH command fails
and the current tape library path is not changed.
User action: Make sure that the proper filesystem is mounted on the
specified subdirectory and it is accessible to the user 'vtape.'
DLm161I Tape library pathname enabled for Replication
Description: Indicates that the tape library directory resides on a

filesystem that is enabled for replication.
User action: None.

System Messages
DLm162I nn of maximum mm SSH sessions in use
Description: SSH sessions are used to communicate certain special

requests to a VNX filesystem. This system is configured to support a
maximum of mm concurrent SSH sessions, of which nn are currently
being used.
User action: None.
DLm163I nn tasks are waiting to obtain an SSH session
Description: SSH sessions are used to communicate certain special

requests to a VNX filesystem. nn tasks are waiting for an available
SSH session.
User action: None.
DLm166E Unable to read VNX #n report file '/pathname/filename':

<reason>
Description: An unexpected error occurred while trying to determine

the current state of the specified VNX by reading the specified report
file.
System Action: VNX-related features such as Guaranteed Replication
and FLR may not function correctly.
User Action: If the error message describes a correctable problem,
correct the problem and restart the application. Contact EMC Support
if more assistance is needed.
DLm168W Invalid DEBUG= value 'value'
Description: The configuration file or operator SET DEBUG

command contained an error.
System action: If a configuration, DLm startup terminates. If a SET
DEBUG command error, the SET command is ignored.
User action: If a configuration error, reconfigure the DLm to correct
the configuration file. If a SET DEBUG command error, use the
HELP command to obtain correct syntax.
DLm171E File <filename> line nnn is too long
System Messages
Description: The configuration file contained an error.

User action: Reconfigure the specified DLm configuration file. If the
problem persists, contact EMC Customer Support for assistance.

System Messages
DLm180E Error [opening|configuring] <name> communication device

<details>
Description: An internal error has occurred within either the SNMP

or the IPMI subsystem. The IPMI subsystem is responsible for
monitoring and reporting system events other than those occurring
within the DLm application, the channel interface adapter, or the
adapter device drivers. The SNMP subsystem is responsible for
broadcasting all DLm event messages that were selected during DLm
configuration to the SNMP management station.
System action: The DLm application continues to function in a
degraded state. Data transfer and storage continue to operate
normally, but the SNMP and the IPMI subsystem facility is no longer
available.
User action: It may be possible to identify the resource that caused
the failure and correct the problem. If the problem persists, contact
EMC Customer Support for assistance.
DLm182W SNMP read failure (<xx>) [details], errno=<yy>: <error

message>
Description: The SNMP subsystem is unable to complete a read

operation and messages may have been lost. This message may be
accompanied by additional messages associated with the failure.
System action: The error is logged and operation continues. If the
failure persists SNMP is disabled.
User action: If SNMP is disabled as a result of this failure, the user
may reenable SNMP from the DLm Console.
DLm183W [SNMP|IPMI] [read|write] failure, <additional

information>
Description: A management subsystem operation has failed and

event messages may have been lost. This message may be
accompanied by additional information associated with the failure.
The IPMI subsystem is responsible for monitoring and reporting
system events other than those occurring within the DLm
application, the channel interface adapter, or the adapter device
drivers. The SNMP subsystem is responsible for broadcasting all
DLm event messages that were selected during DLm configuration to
the SNMP management station.
System Messages
System action: The error is logged and operation continues. If the

failure persists, the subsystem is disabled.
User action: If the SNMP subsystem is disabled as a result of this
failure, it can be reenabled from the DLm Console. If the problem
persists, or it cannot be corrected, contact EMC Customer Support for
assistance.
DLm184E Error <number> building SNMP OID. Disabling SNMP
Description: SNMP has detected an internal error and SNMP event

messages may have been lost.
System action: SNMP is disabled.
User action: It may be possible to restart SNMP from the DLm
Console. Contact EMC Customer Support for assistance.
DLm185E Error - SNMP <entity> initialization failed (<details>)
Description: Entity is 'thread,' 'library,' or 'IPMI.' A failure has

occurred during initialization of the entity. The IPMI subsystem is
responsible for monitoring and reporting system events other than
those occurring within the DLm application, the channel interface
adapter, or the adapter device drivers. The SNMP subsystem is
responsible for broadcasting all DLm event messages that were
selected during DLm configuration to the SNMP management
station.
System action: If the failure occurred within the SNMP subsystem,
initialization is aborted and the SNMP services are not available. If
the failure occurred within the IPMI subsystem, SNMP continues to
function, but no system platform events are reported.
DLm186I Disabling SNMP
Description: SNMP has been disabled in response to a console

command.
System action: SNMP is disabled.
User action: SNMP may be reenabled from the DLm Console.
DLm187W Invalid command syntax <additional information>
Description: An SNMP command has been typed at the DLm

Console that is not recognized.

System Messages
System action: The command is ignored.

User action: Use the HELP command to see the proper command
syntax.
DLm188I SNMP [ Disabled | Message Level set to report <level>

]\n"
Description: Used to display the current SNMP operating status.

User action: None.
DLm189W SNMP subagent service is unavailable
Description: SNMP is not initialized or it has terminated.

User action: None.
DLm190I DLM SNMP terminated
Description: The SNMP subsystem has shut down normally.

User action: None.
DLm191I Invalid SNMP message level (<value>)
Description: An invalid message level was typed.

User action: Type a valid message level from the DLm Console. The
HELP command may be used to display the command syntax.
DLm192I SNMP communication device has closed (flags = 0x<value>).

SNMP terminating
Description: The SNMP internal communication mechanism has

shut down normally.
System action: SNMP subsystem terminates.
User action: None.
DLm193I IPMI <informational message>
System Messages
Description: Describes some event that has occurred within the IPMI
subsystem. The IPMI subsystem is responsible for monitoring and
reporting system events other than those occurring within the DLm
application, the channel interface adapter, or the adapter device
drivers.
User action: None.
DLm194W IPMI <warning message>
Description: An internal failure has occurred. The system has

recovered, but event messages may have been lost. The IPMI
subsystem is responsible for monitoring and reporting system events
other than those occurring within the DLm application, the channel
interface adapter, or the adapter device drivers.
System action: The condition is logged and operation continues. If
the condition persists, the subsystem is shut down.
User action: If the problem persists, contact EMC Customer Support
for assistance.
DLm195E IPMI <error message>
Description: An error has occurred that has resulted in the loss of the
IPMI subsystem service. The IPMI subsystem is responsible for
adapter device drivers.
System action: The error is logged and the IPMI subsystem is shut
down.
User action: If the cause of the problem cannot be determined and
corrected, contact EMC Customer Support for assistance.
DLm196I (System Event) <informational message>
Description: This is an informational message describing a system

platform event that was detected by the IPMI subsystem. The IPMI
subsystem is responsible for monitoring and reporting system events
other than those occurring within the DLm application, the channel
interface adapter, or the adapter device drivers.
System action: The message is saved to both the system event log
and DLm event log.

System Messages
User action: None.
DLm197W (System Event) <warning or error message>
Description: Warns of a system platform event that was detected by

the IPMI subsystem. The event should be evaluated to determine if
corrective action is needed. The IPMI subsystem is responsible for
adapter device drivers.
System action: The message is saved to both the system event log as
well as the DLm event log.
User action: The user action varies with the event. In some cases,
such as a chassis intrusion warning following the replacement of a
system component, the warning may be ignored. In other cases, the
message may indicate a failure or loss of redundancy in a power
supply, fan, memory device, or other component and the component
should be replaced. Contact EMC Customer Support if assistance is
needed.
System Messages
DLm198E (System Event) <error message>
Description: This message indicates that the IPMI subsystem has

detected a system platform event that may result in significant
functional or security problems. The event should be evaluated to
determine if corrective action is needed. The IPMI subsystem is
responsible for monitoring and reporting system events other than
those occurring within the DLm application, the channel interface
adapter, or the adapter device drivers.
System action: The message is saved to both the system event log
and the DLm application event log.
User action: The user action will vary with the event. In some cases,
such as a chassis intrusion warning following the replacement of a
system component, the warning may be ignored. In other cases, the
message may indicate a failure or loss of redundancy in a power
supply, fan, memory device, or other component and the component
should be replaced. Contact EMC Customer Support if assistance is
needed.
DLm201I Validating tape library '<pathname>'...
Description: During startup, and any other time a tape library path
change is requested, the DLm validates the tape library for various
integrity issues.
System action: If any errors are found, subsequent messages report
the problems.
User action: If any errors are reported, correct the problems, then
SET PATH= to the desired path.
DLm202I Device <devicename> <nn> subdirectories under tape

library 'pathname'
Description: While validating the specified tape library, the DLm

displays the number of subdirectories found in that tape library.
System action: If any subdirectories exist, they are also validated.
User action: None.

System Messages
DLm203I There is no <volser> directory, using <pathname>
Description: When attempting to mount, scratch, unscratch, erase, or

delete a volume, the DLm found that there was no tape library
subdirectory matching the first two characters (\volser prefix\) of the
specified volume.
System action: The system searches only in the base tape library
directory for the desired volume.
User action: None.
DLm204E Device <devicename> tapelib directory '<pathname>' is not

browsable!
Description: While validating the tape library, the specified path was
found to be not browsable, which means the contents could not be
listed.
System action: During system startup, this is a warning message. If
this error occurs when processing a SET PATH command, the SET
PATH command fails.
User action: Make sure that the tape library is mounted correctly, and
that it is owned by user 'vtape' and has the 'x' permission set.
DLm205E Device <devicename> error while checking tape library

'<pathname>' subdirectories: error message
Description: An I/O error occurred while searching the specified

tape library for subdirectories.
PATH command fails.
User action: The 'error message' portion of this message describes the
error that occurred. Correct the error and retry the SET PATH
command to set the tape library path to the desired path.
System Messages
DLm206W Device <devicename> bypassing full filesystem <pathname>
Description: A filesystem with less than a full tape's worth of free

space (based on the current SIZE= value) will be skipped while
searching for a scratch tape. This option can be overridden with the
"UseFullFS TRUE" configuration option or "SET UseFullFS=TRUE"
command.
System action: The specified filesystem is bypassed during this
scratch tape search.
User action: None.
DLm210I Validating tape library '<pathname>'...
change is requested, DLm validates the tape library path.
System action: If any errors are found, subsequent messages will
report the problems.
User action: If any errors are reported, correct the problem(s), then
SET PATH= to the desired path.
DLm211I Tape Library <VTL-ID> <status>
Description: During startup DLm determines whether the

discovered tape library is supported or not.
System action: During system startup this is an informational
message.
User action: If a library is not supported the operator could change
the VTL back end to disable this library and enable a supported
library instead.
DLm212I VTL <VTL-ID> Volume List <status>
Description: During startup, and at any other time a VTL volume list
update is requested, DLm will display the VTL volume list state.
User action: None.

System Messages
DLm213I SCSI Media Changer Driver version: x.x.x
Description: This message displays the version number of the scsi

media changer driver.
User action: None.
DLm214E Error creating/mapping/opening ATL Volume List file:

<filename> : <error message>
Description: An error occurred while initializing the specified

feature. This error can only occur during startup.
System action: startup terminates or continues without the specified
feature. The 'error message' text explains the reason for the failure.
User action: If you are unable to correct the problem, contact contact
Bus-Tech Support for assistance.
DLm217W VTL-SN volumes in slots x to y exceed maximum and will

not be used.
Description: The VTL has defined more slots than the application can
support.
User action: Define the number of slots on the back-end VTL to
within our maximum of 20,000 slots.
DLm218I Scanning tape drive devices...
Description: The SCSI tape drives are being scanned and cataloged.
User action: None.
System Messages
DLm220I Validating tapelib subdirectory '<name>'...
change is requested, the DLm validates the tape library and each of
its subdirectories for various integrity issues.
System action: If any errors are found, subsequent messages report
the problems.
User action: If any errors are reported, correct the problems, then SET
PATH= to the desired path.
DLm221E Device <devicename> subdirectory name '<name>' is not a

valid volser prefix
Description: During validation of the tape library, the DLm found the
specified subdirectory, but the subdirectory name does not conform
to a valid volser prefix. Every subdirectory in a tape library must
have a two-character name that consists of valid volser characters
(A–Z, 0–9).
PATH command fails.
User action: Either remove the invalid subdirectory from the tape
library base directory, or rename the subdirectory to a valid volser
prefix.
DLm222E Device <devicename> subdirectory name '<name>' is not a

valid tape library subdirectory name
Description: During validation of the tape library, the virtual tape

application found the specified subdirectory, but the subdirectory
name is not a valid enhanced filesystem subdirectory name. Every
subdirectory in an enhanced filesystem tape library must have an
alpha-numeric name containing only upper-case letters and/or
numbers. This message will only occur if enhanced filesystem
support is enabled on this node.
PATH command will fail.
User action: Either remove the invalid subdirectory from the tape
library base directory, or rename the subdirectory to a valid enhanced
filesystem subdirectory name.

System Messages
DLm224E Device <devicename> tapelib subdirectory '<name>' is not

browsable!
Description: While validating this tape library subdirectory, the

specified path was found to be not browsable, which means the
contents could not be listed.
PATH command fails.
User action: Make sure the tape library is mounted correctly, and that
each subdirectory is owned by user 'vtape' and has the 'x' permission
set.
DLm225E Device <devicename> Error while checking tapelib

subdirectory '<name>': error message
Description: An I/O error occurred while searching the contents of

the specified tape library subdirectory.
PATH command fails.
error that occurred. Correct the error and retry the SET PATH
command to set the tape library path to the desired path.
DLm226W Device <devicename> file '<filename>' does not belong in

subdirectory '<name>'
Description: The specified file does not belong in the specified tape
library subdirectory because it does not begin with the same first two
characters (\volser prefix\) as the subdirectory name.
PATH command fails. If this message occurs during a tape volume
mount, the mount fails.
User action: Correct the error, then retry the SET PATH command to
set the tape library path to the desired path or retry the tape volume
mount.
System Messages
DLm227E Device <devicename> file '<filename>' in base library

belongs in subdirectory '<name>'
Description: The specified file does not belong in the base tape
library directory because it begins with the same first two characters
(\volser prefix\) as an existing subdirectory name. The file should
reside in that subdirectory.
PATH command fails. If this message occurs during a tape volume
mount, the mount fails.
User action: Correct the error, then retry the SET PATH command to
set the tape library path to the desired path or retry the tape volume
mount.
DLm230W WARNING: Device <devicename> path <dirname> is on root

filesystem!
Description: The directory assigned to hold the virtual tape volumes

for this device is mounted on the root filesystem. This usually means
that the real tape library filesystem was not mounted, since tapes are
not expected to be stored on the DLm system disks, but on a high
capacity external disk.
System action: The specified directory continues to be used as the
tape library for this drive. This message is displayed every time a
virtual tape volume is successfully mounted and the tape library is
still mounted on the root filesystem.
User action: Make sure that the proper disk filesystem is mounted on
the tape library path specified for this drive.
DLm231W Unable to determine <pathname> device name: <error

message>
Description: The DLm was unable to determine on which disk

filesystem the specified directory is mounted.
System action: Processing continues normally. This message is
displayed every time a virtual volume is successfully mounted and
the 'pathname' filesystem device cannot be determined.

System Messages
DLm232W Device <devicename> Unable to determine <pathname>

filesystem type: <error message>
Description: An unexpected error occurred while trying to determine

what type of filesystem holds the specified tape library.
System action: The DLm continues to run, but some features (such as
warnings about the capacity limits of certain filesystems) may not be
functional.
for assistance.
DLm233E Device <devicename> data path <pathname> is not

accessible
Description: During mounting of a tape volume, the DLm was not

able to access the specified tape library subdirectory.
System action: This subdirectory is ignored. If there are other tape
library subdirectories, they are considered to attempt to fulfill the
mount request.
User action: If the configured tape library is correct, make sure that
all of its subdirectories are mounted and accessible to the user 'vtape.'
If the tape library is misconfigured, correct the PATH= parameter in
the configuration file and restart the DLm application, or use the SET
PATH command to temporarily change the tapelib path.
DLm235E Device <devicename> failed deferred tapelib path change

to <path>
Description: A tape library change was previously deferred while a

volume was mounted on this drive. Now that there is no longer a
volume mounted, an attempt to change the tape library to the new
path has failed.
System action: The tape library path is not changed.
User action: This message should have been preceded by one or more
messages that explained the problem. See these messages, correct the
problems, and then SET PATH= to the desired path.
System Messages
DLm240E Unable to open tape library path <pathname>
Description: A tape library path couldn't be opened.

System action: The search for a particular volser was not completed.
User action: Check to be sure the path exists.
DLm241E Unable to read contents of volser lock file <volser>:

<error>
Description: While unlocking a volume, the contents (owner) of a

VOLSER lock file could not be read.
System action: The owner of the VOLSER lock could not be
determined. The lock remains in place.
User action: Verify that the VOLSER lock directory is mounted and
accessible.
DLm242E Device <devicename> error deleting lock file <filename>:

<error>
Description: While unlocking a volume, an error occurred while

trying to remove the lock file for this VOLSER.
System action: The status of the VOLSER lock is unknown.
User action: Verify that the VOLSER lock directory is mounted and
accessible.
DLm243E Unable to open lock file <file>: <error>
Description: An error occurred while opening a lock file for reading.

System action: The file could not be opened.
User action: Verify that the file exists.
DLm244E Error reading lock file <file>: <error>
Description: An error occurred while reading a volser lock file.

System action: The file could not be read.
User action: Verify the file exists.

System Messages
DLm245E Unable to open volser lock directory <directory>
Description: The system was unable to open the VOLSER lock

directory.
System action: The existing locks could not be read.
User action: Verify the lock directory is mounted and accessible.
DLm246E Device <device> error returned from stat command to file

<file>: <error>
Description: A stat command to a file failed.

System action: Information on the file could not be obtained.
User action: Verify that the path to the file is mounted and accessible.
DLm247E Device <device> error returned from statfs command to

directory <dir>: <error>
Description: An error occurred while getting information about a

directory.
System action: Directory information was not obtained.
User action: Verify the directory path is online, mounted, and
accessible.
DLm248E Device <device> error getting offset to file <file>:

<error>
Description: An lseek command to a file returned an error.

System action: The current file offset to a file could not be obtained.
User action: Verify that the file path is mounted and accessible.
DLm249E Device <device> error opening file <file>: <error>
Description: A new file could not be created.

System action: A new file could not be created. The volume will not
be moved.
User action: Verify that the file path is mounted and accessible.
System Messages
DLm250E Device <device> Incomplete read from file <file>: <error>
Description: A read of the file returned 0 bytes when data was

available.
System action: This volser will not be moved.
User action: None. If the problem persists, contact EMC Customer
Support.
DLm251E Problem accessing directory <dirname>: <error>
Description: A problem occurred while accessing the destination

directory for the new volume(s).
System action: No volumes will not be created in this directory.
User action: None. If the problem persists, contact EMC Customer
Support.
DLm252E Wrong storage class. REQ <requested class>, WAS <actual

class> for <dirname>
Description: The IMPORT command specified a storage class for the

request directory that was different than the indicated class.
System action: No volumes created.
User action: Retry the command with a different storage class or
directory.
DLm253E No subdirectory found at <base directory> with storage

class <requested storage class>
Description: No tape volume libraries of the requested class were

found at the tape library location.
System action: No volumes created.
User action: Retry the command with a different storage class.
DLm254I Invalid storage class file: <directory/filename>
Description: The class file (.CLASSx) found in this directory is

invalid.
System action: Storage class could not be determined.
User action: Rename or remove the offending file.

System Messages
DLm255I Max display count <count> exceeded for key: <key>
Description: The number of matches for the find volume exceeded

the limit.
System action: No more volumes will be displayed for this
command, command processing ended.
User action: Retry the find command with a key that will have fewer
matches.
DLm256I Volser Lock Directory set to: <directory>
Description: A volser lock directory has been specified for Enhanced

Filesystem Architecture operations.
User action: None.
DLm257I The Maximum Find Volume Display Count is: <count>
Description: This is the maximum number of volumes displayed by

the 'find volume' command.
System action: Not more than <count> volumes will be displayed for
the find volume command.
User action: None.
DLm258E Invalid storage class parameter: <class>
Description: The IMPORT command CLASS= parameter is invalid.

System action: The command will not be executed.
User action: Retry the command with valid parameters.
DLm259E No storage class <class> directory found.
Description: The IMPORT command CLASS= parameter specified a

storage class that cannot be found.
System action: The command will not be executed.
User action: Retry the command with valid parameters.
System Messages
DLm260E Could not determine the storage class of directory

<directory>: <reason>
Description: While processing an IMPORT command, the storage

class of the directory could not be determined.
System action: The operation will not be executed.
User action: Retry to a different directory.
DLm261E Device <devicename> Unable to lock volser <volser>:

<reason>
Description: A lock could not be placed on a volser.

System action: The operation will not be executed.
User action: Verify the VOLSERLOCKDIR setting the configuration
file.
DLm 263I Device <devicename> moved <volser path> to <volser path>

<size> bytes
Description: A device moved a newly acquired scratch volume from

one file system to another file system of the same class that had more
space.
System action: None
User action: None.
DLm269I Device <devicename> forcing CRC storing/large headers for

-onlock file system
Description: The device is writing to a file system mounted as

-onolock. This type of file system required large headers to be used.
User action: None.
DLm270I Device <devicename> Volume <volser> writing AMDD

optimized volume
Description: During a write operation, the data on this tape volume

has been modified by the AMDD feature to achieve better back-end
data deduplication. This message will be displayed only once per
volume.
System action: None. When the data is read back, the AMDD
modifications will be transparent to the host.

System Messages
User action: None.
DLm271I Device <devicename> Volume <volser> reading AMDD

optimized volume
Description: During a read operation, the data on this tape volume

was found to have been modified by the AMDD feature to achieve
better back-end data duplication. This message will be displayed
only once per volume.
System action: None. When the data is read back, the AMDD
modifications will be transparent to the host.
User action: None.
DLm273W Device devicename Volume <volser> AMDD skipping

incompatible type block #nnnnn
Description: While considering this block for AMDD processing

during a write, it was found that although the block was initially
thought to be of a <type> recognized by AMDD (DSS, FDR, etc),
some inconsistencies in the data prevented AMDD from being able to
process the block.
System action: The block is written without any AMDD
modification.
User action: Rarely, data that normally isn't handled by AMDD can
initially be mistaken as a recognized data type. In this case, this
message can be ignored. If this message is displayed while the
specified <type> of data (i.e. DSS, FDR, etc) is being written, it
signifies an incompatibily that should be reported to EMC Support
for evaluation.
DLm274I Device <devicename> Volume <volser> AMDD modified <nnnnn>

of <nnnnn> blocks
Description: AMDD has modified the specified number of blocks in

order to improve back-end data-deduplication performance. This
message is displayed when an AMDD-modified tape is unloaded.
User action: None.
System Messages
DLm276I Device <devicename> Volume <volser> AMDD read <nnnnn>

AMDD-modified blocks
Description: The specified number of blocks read from this tape were
found to have been AMDD-modified blocks. This informational
message is displayed at unload time whenever any AMDD-modified
blocks had been read.
User action: None.
DLm277E Device <devicename> Volume <volser> Invalid AMDD

identifier, block #nnn
Description: The specified block is flagged as an AMDD-modified

data block, but does not contain valid AMDD data.
System action: An equipment check error status is returned to the
Host I/O request.
User action: Contact EMC Support for assistance.
DLm278I Device <devicename> Volume <volser> Suppressing IDRC for

<type> library
Description: The Host has requested that the data it is writing should
be compressed, but the data will be written uncompressed because
the type of tape library filesystem it is being written to performs
better with uncompressed data. <type> may be "EMC DLm Data
Domain".
System action:The data being written is not compressed. If desired,
compression can be forced, regardless of filesystem, by setting the
IDRC=FORCE option on a device-by-device basis. This message will
display only once per volume as a reminder.
User action: None.
DLm281E EXPORT/IMPORT FROM file not found. EXPORT/IMPORT command

aborted.
Description: The file specified in the command does not exist. The
command stopped with no action.
User action: Execute the command with the correct file.

System Messages
DLm282E EXPORT TO device already in use. EXPORT command aborted.
Description: The TO device specified in the EXPORT command is

already in use. The EXPORT command stopped with no action.
User action: Execute the EXPORT command when the device
becomes free.
DLm283E EXPORT/IMPORT FROM/TO file already in use. EXPORT/IMPORT

command aborted.
Description: The file specified in the command is currently in use by

another device. The command stopped with no action.
User action: Execute the command again after the current operation
that is using the file has completed.
DLm284E EXPORT/IMPORT FROM/TO device block could not be created.

EXPORT/IMPORT command aborted.
Description: An internal error occurred while trying to set up to

execute the command. The command stopped with no action.
User action: Check for previous error message that may indicate
cause of problem. Verify that the physical device is properly attached
to the system. If this problem recurs, contact EMC Customer Support
for assistance.
DLm285E EXPORT/IMPORT FROM/TO device is not a valid device type

for this command. EXPORT/IMPORT command aborted.
Description: One of the parameters specified is not a valid type for

this command. The command stopped with no action.
User action: Execute the command again with valid parameters.
System Messages
DLm286E Could not allocate parameter structure for EXPORT thread.

EXPORT command aborted.
Description: An internal error occurred while trying to set up to

execute the command. The command stopped with no action.
for assistance.
DLm287E IMPORT SCSI device is already in use. IMPORT command

aborted.
Description: The SCSI device specified in the command is currently

in use. The command stopped with no action.
User action: Execute the IMPORT command when the device
becomes free.
Note: This message applies to Fibre Channel drives as well. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
DLm288E IMPORT TO file already exists. Import will not overwrite

an existing file. IMPORT command aborted.
Description: The file specified in the command to write to already

exists. Overwriting an existing file is not allowed. The command
stopped with no action.
User action: Execute the command again with a file that does not
exist.
DLm289E EXPORT/IMPORT FROM/TO file is invalid. Scratch file not

permitted. EXPORT/IMPORT command aborted.
Description: Scratch file specified in EXPORT or IMPORT command.

Scratch file use is not permitted in these operations.
User action: None.

System Messages
DLm290I EXPORT operation starting: FROM=file (dev=EXFROMxxxx)

TO=device (dev=EXTOxxxx)
Description: Message indicating that the EXPORT operation is

starting.
User action: None.
DLm291I EXPORT operation finished (successfully/with error):

FROM=file (dev=EXFROMxxxx) TO=device (dev=EXTOxxxx)
Description: Message indicating that the operation has completed. If

with error, check previous messages for cause of error.
User action: None.
DLm292I IMPORT operation starting: FROM=device (dev=IMFROMxxxx)

TO=file (dev=IMTOxxxx)
Description: Message indicating that the IMPORT operation is

starting.
User action: None.
DLm293I IMPORT operation finished (successfully/with error):

FROM=device (dev=IMFROMxxxx) TO=file (dev=IMTOxxxx)
Description: Message indicating that the operation has completed. If

with error, check previous messages for cause of error.
User action: None.
DLm294I EXPORT/IMPORT operation performing rewind or

rewind/unload: FROM=name (dev=EX/IMFROMxxxx) TO=name
(dev=IMTOxxxx)
Description: Message indicating that the operation has completed

and is now rewinding and unloading the tape device.
User action: None.
System Messages
DLm295E EXPORT operation reached PEOT. Tape invalid: FROM=name

(dev=EXFROMxxxx) TO=name (dev=EXTOxxxx)
Description: The EXPORT command reached the physical end of

tape before completing the export operation. The tape is invalid.
User action: Repeat the EXPORT operation with a larger tape.
DLm296E Error rewinding tape after PEOT: FROM=name

Description: The EXPORT command got an error when rewinding

the tape after it reached the physical end of tape.
User action: None.
DLm297E Error writing tapemark after PEOT: FROM=name

Description: The EXPORT command got an error writing tape marks

after a rewind of the tape after it reached the physical end of tape.
User action: None.
DLm298E SCSI device not ready, operation aborted: FROM=name

(dev=EX/IMFROMxxxx) TO=name (dev=EX/IMTOxxxx)
Description: The SCSI device specified in the command was not in

the ready state, and the operation was aborted.
User action: Ready the SCSI device and execute the command again.
Note: This message also applies to Fibre Channel drives. The message
DLm300W Device <devicename>, connection n, received pkt 0xXXXX

(packettype )
Description: The channel interface adapter sent an unexpected

message type to the DLm application.
System action: The message from the adapter is ignored.

System Messages

for assistance.
DLm301W Channel event 'eventtype' (0xXXXX) on device <devicename>

<pathinfo> [XXXX XXXX]
Description: The specified exceptional channel event 'eventtype' has

been detected. Some common event types which may occur include:
◆ Halt I/O: Host has issued a Halt I/O command, usually as a result
of a Host job being canceled.
◆ System Reset: Host has issued a System Reset, usually as a result
of the Host being reset.
◆ Link Error: An error has occurred at the channel link level. This is
usually the result of the channel 'dropping light,' most often
because the channel cable was unplugged or is faulty. This can
also be the result of a channel protocol error caused by a faulty
channel, director, or channel adapter hardware or firmware
problem.
◆ Selective Reset: The Host has issued a Selective Reset to this
device, usually because the device is being varied on or offline, or
because a serious I/O error has occurred on this device.
System action: Processing continues normally by the DLm; it is
presumed that the Host performs the proper error recovery
procedure to which the DLm responds like a real tape drive.
User action: Unless this is an expected occurrence (such as the Host
job is being canceled, the Host is being reset, or a channel or device is
being varied off or on), check the Host console logs to determine the
cause of the problem. Contact EMC Customer Support for assistance
if the problem persists.
DLm302I Device <devicename> <pathinfo> Offline to channel
Description: The specified device has been taken offline on the

specified channel interface. This is usually the result of the channel
being \varied offline\ or unplugged.
System action: This device is unavailable to the Host until it is
brought back online.
User action: None, unless this is an unexpected occurrence, in which
case you should investigate the cause at the Host.
DLm303I Device <devicename> <pathinfo> Online to channel
System Messages
Description: The specified device has been brought online on the

specified channel interface.
System action: This device is available to the Host on this channel
interface.
User action: None.
DLm304E Interface #n exceeded automatic restart limit of <count>,

NOT restarting
Description: The specified channel interface was reset because of an

error, or because of an operator action from outside the DLm
application. The DLm automatically recovers from this situation
<count> number of times, but this count has been exceeded.
System action: This channel interface remains offline to the DLm
devices.
User action: The situation causing the channel interface adapter to
reset should be investigated; contact EMC Customer Support for
more assistance if necessary. The channel interface can be brought
back online for the DLm devices by typing the DLm \RESET
CHANNEL ADAPTER n\ command.

System Messages
DLm305E Active path(s) on Interface #n, cannot stop adapter
Description: There was an attempt to reset or stop channel interface

#n while there were active devices online.
System action: The channel interface remains online without having
been stopped or reset.
User action: Before stopping or resetting a channel interface, all
channel paths using that channel adapter must be varied offline from
the Host.
DLm306W Active path on Interface #n, device <devicename>
Description: Channel interface #n is being forcefully stopped or reset

while there are active devices online. This may cause I/O errors on
the Host channel.
System action: Stopping or resetting of the channel interface
continues.
User action: None.
DLm308I Rebooting Interface #n, slot=nnnnnn
Description: Channel interface #n is being reset.

User action: None.
System Messages
DLm309I Device <devicename> NOT sending a resetting event unit

check
Description: A resetting event is any channel event that resets a DLm

application device's pathgroup ID or assignment, such as a system or
selective reset or restarting of the DLm application. Normally, after a
resetting event has occurred, the next command sent by the Host
receives a resetting event unit check to notify the Host that the
resetting event occurred. The Host should respond appropriately by
restoring the device's pathgroup ID and assignment information, and
reissue the unit-checked command. Occasionally, especially with
older standalone IPL programs, a Host may not handle a resetting
event unit check correctly. In this case, the DLm application can be
configured to NOT send resetting event unit checks. This message is
displayed when the DLm application is so configured and would
have normally sent a resetting event unit check to a Host command.
System action: Processing of Host commands continues without the
occurrence of a resetting event unit check.
User action: None. Under normal conditions, the DLm application
should NOT be configured to ignore resetting events. Doing so can
cause problems when varying on devices to a Host that does properly
handle, and actually expects, resetting event unit checks. Contact
EMC Customer Support for more information.
DLm310E <process> received unexpected packet type 0xXXXX

(packettype)
Description: An error was returned from the channel adapter. This

error can only occur during DLm startup.
DLm311W Device <devicename> received <info> on path <n> but in

chain on path <n>
Description: An unexpected message was returned from the channel

adapter.
System action: The application continues to run, but the device may
not continue to function properly.

System Messages
DLm312E Device <devicename> Error reading from Interface #n:

error message
Description: An error was returned from the channel adapter.

DLm313E Device <devicename> error sending <info>, error = nn

(0xXX)
Description: An error was returned from the channel adapter.

DLm314E Device <devicename> <path> unexpected <type> XX CCW while

inccw for XX
Description: An unexpected packet sequencing error occurred. This

is an internal error.
System action: A Unit Check is returned to the host.
DLm315W Device <devicename> selection (ccw XX) on path <n> not

assigned
Description: The DLm virtual tape device has been assigned

(reserved) by a specific Host LPAR, but it received an I/O command
over a channel path on which it is not currently assigned.
System action: The I/O command is ignored.
User action: Check that the DLm configuration for channel paths
matches the Host's configuration. Make sure that no other LPARs or
Hosts are also trying to talk to the same DLm device.
System Messages
DLm316E Device <devicename> received <info> on unexpected

connection nn, path=nn
Description: A message was received from the channel adapter from

a path that the DLm does not recognize as a valid path.
System action: The unexpected message is ignored. The application
continues to run, but the device may not continue to function
properly.
DLm317E Device <devicename> received data on unexpected

Description: Data was received from the channel adapter from a path
on which the DLm was not currently handling a CCW.
System action: The unexpected data is ignored. The application
properly.
DLm318E Device <devicename> received unexpected data on

Description: Data was received from the channel adapter while the
DLm was not currently handling a CCW that should return data.
System action: The unexpected data is ignored. The application
properly.
DLm319E Device <devicename> <path> invalid data chaining flags

(XXX) for XX CCW
Description: An invalid message was received from the channel

adapter. This is an internal error.
System action: The CCW is rejected with a Unit Check.

System Messages
DLm320I Firmware trace enabled/disabled interface #n, slot nnnnnn
Description: Firmware tracing was enabled or disabled on the

specified channel adapter.
System action: Channel adapter tracing remains in this state until the
DLm is next restarted.
User action: None. You can use the DLm \ENABLE FIRMWARE
TRACE\ or \DISABLE FIRMWARE TRACE\ command to turn
tracing on or off.
DLm326E Channel Adapter #n NOT reset/stopped/started
Description: A \RESET/STOP/START CHANNEL ADAPTER\

command was typed, but the specified action could not be
performed.
User action: Examine preceding related messages, if any, for
additional error messages that explain why the action could not be
performed, correct the problem, and try the command again.
DLm327I Channel Adapter #n reset/stopped/started
Description: The specified action was taken in response to the DLm

\RESET/STOP/START CHANNEL ADAPTER\ command.
User action: None.
DLm331E Device <devicename> <type of> paths to send Ready Status
Description: The virtual tape drive has become Ready, but there is no
online path to send the Ready Status message to the Host. Most likely
the drive, path, or channel was never configured/varied online on
the Host, or has been varied offline.
System action: The drive is mounted and ready from the DLm point
of view, but since a Ready Status was not presented, the Host most
likely reports that the drive is still not ready.
User action: Check that the specified device is varied online on the
Host. You can cause the DLm to present another 'Ready' signal to the
Host by typing an \Unready\ command, followed by a \Ready\
command. If this problem recurs, contact EMC Customer Support for
assistance.
System Messages
DLm332E Device <devicename> [pathNumber] Error sending Async

Ready Status, err=nnn
Description: An error has occurred while attempting to send an

unsolicited status ('Ready' signal) to the Host.
System action: The DLm attempts to present the status several more
times. If the Host never takes the status, the virtual volume remains
mounted on the drive, but the Host most likely reports that the drive
is still not ready.
User action: You can cause the DLm to present another 'Ready' signal
to the Host by typing an \Unready\ command, followed by a
\Ready\ command. If this problem recurs, contact EMC Customer
DLm333E Device <devicename> failed to send Ready interrupt to

Host
Description: After several retries, the DLm was unable to present the
asynchronous status ('Ready' signal) to the Host.
System action: The application continues without presenting the
status to the Host. The virtual volume remains mounted on the drive,
but the Host most likely reports that the drive is still not ready.
User action: You can cause the DLm to present another 'Ready' signal
to the Host by typing an \Unready\ command, followed by a
\Ready\ command. If this problem recurs, contact EMC Customer
DLm335I Device <devicename> unassigned while volume <volser>

mounted
Description: The host has sent an Unassign command to the device

while a tape was mounted on the device.
System action: The Unassign command is processed normally. The
tape remains ready and at its current position.
User action: This is a valid but unusual condition. Check that the
Host is not having some kind of problem with this virtual device.
Contact EMC Customer Support if you need additional assistance.

System Messages
DLm338I New path established: board=n, path=n, link=xx, lpar=xx,

cu=xx
Description: The Host has established a new channel path to the

DLm.
System action: This path is available now for channel I/O.
User action: None.
DLm339I Path removed: board=n, path=n, link=xx, lpar=xx, cu=xx
Description: The Host has removed the specified channel path to the
DLm.
System action: This path is no longer available for channel I/O.
User action: None.
DLm340E Device <devicename> path <pathname> Incorrect CRC in data

received from channel, failed/retrying...
Description: The DLm application has detected a corruption of

written data by the Host.
System action: The DLm application will instruct the Host to
retransmit the data up to ten times (displaying “retrying...” each of
these times). If the error occurs on eleven consecutive writes, the
DLm application will return a unit check error to the Host, with sense
of Bus-Out Error (displaying “failed” this time).
User action: A data CRC error may indicate failing hardware,
cabling, or a weak data link between the Host and the DLm
application. Contact your hardware support personnel for assistance.
DLm341E Device <devicename> CRC mismatch in data block...
Description: DLm has detected a corruption of data when comparing

the CRC value stored in the awsheader from a file with a newly
calculated CRC value after reading the data.
System action: DLm will return a unit check to the Host, with sense
of Bus Out Error.
User action: A data CRC error may indicate failing hardware.
Contact EMC Support for assistance.
System Messages
DLm350E Unable to get trace flags for interface #n
Description: The DLm is attempting to obtain the current trace

options from channel interface number #n, but has failed to do so.
System action: The current trace settings are not available to the
DLm. As a result, some subsequent function may not complete.
DLm351E Unable to set trace flags for interface #n
Description: The DLm is attempting to set the trace options in

channel interface number 'n,' but has failed to do so.
System action: The current trace settings are not changed.
DLm352I Firmware tracing stopped on interface #n
Description: The DLm has turned tracing off for channel interface #n.
System action: Firmware tracing in channel interface #n remains off
until turned back on.
User action: None.
DLm353I Firmware tracing restored on interface #n
Description: The DLm has restored the trace options for channel
interface #n.
System action: Firmware tracing resumes in channel interface #n.
User action: None.
DLm354E Error saving firmware trace
Description: An error has occurred while attempting to save the

firmware trace from channel interface #n.
System action: The trace was not saved.

System Messages
DLm355W Attempting to save firmware trace on interface #%d
Description: An error or other unusual event has occurred on

channel interface #n, and the DLm attempts to save a firmware trace
from that interface.
System action: The DLm attempts to stop the firmware trace and
save it to disk. After the trace is saved, firmware tracing resumes.
DLm356E Interface #n exceeded automatic save trace limit of nn,

NOT saving trace

channel interface #n. The DLm automatically saves a firmware trace
'nn' number of times, but this count has been exceeded for this
interface.
System action: The DLm continues running without automatically
saving the firmware trace.
DLm357E Interface #n NOT saving trace for unexpected packet

channel interface #n. Normally, saving of a firmware trace would be
triggered by this event, but DLm has been configured to not save a
trace for this kind of event.
System action: DLm continues running without automatically saving
the firmware trace.
DLm358I Tracing of unexpected packets set ON/OFF
Description: The automatic saving of a firmware trace when an

unexpected packet is received on a channel interface has been turned
ON or OFF.
System action: If ON (the default) a firmware trace is saved when
this type of unexpected event occurs. If set OFF, no firmware trace
will be automatically saved.
User action: Contact EMC Customer Support for assistance with this
option.
System Messages
DLm366E Device <devicename> <function> error, Interface #n,

error=0xXX (nnn)
Description: An error involving channel interface adapter #n has

occurred.
System action: This channel interface may not be available to this
DLm device until the adapter is reset.
DLm370E Unable to open connection to eslot 0xXXXXXX:err=nn

(0xXX)
Description: An error has occurred while opening a channel driver

during the DLm application startup.
System action: The DLm application startup terminates.
DLm379E <function>: <error message>
Description: An internal error has occurred in the DLm application

during shutdown.
System action: The DLm continues its shutdown.
for assistance.
DLm380E Severity n Alert Interface #n (XXX:YYY) <type:subtype

(additional parms)>
Description: The DLm has received an alert message from the

channel adapter driver, for channel adapter 'n'. XXX:YYY are the alert
type and subtype, which are also translated in <type:subtype>.
System action: Depending on the alert severity and type, the DLm
may continue to function normally, or it may require service or other
attention.

System Messages
DLm381I Channel Interface #n <message>
Description: The DLm has received an informational message from

channel adapter 'n.'
User action: None.
DLm390E Invalid encryption key file (rc=n)
Description: The encryption key file has been corrupted.

System action: Encryption or decryption will not be available on this
controlleruntil the encryption key file is restored or reconfigured.
User action: Restore the encryption key file from a backup copy, or
reconfigure the keys via the encryption key configuration program.
Contact EMC Support for more assistance.
DLm391I ENCRYPTKEY set to [KEYn|NONE] for device <devicename>
Description: Key #n will be used for encryption on device

<devicename>, or if 'NONE' is specified, no encryption will be
performedon device <devicename>
System action: The specified encryption key (or none, for 'NONE')
will be used for all data written to the specified device.
User action: None.
DLm392E Encryption is not available
Description: Encryption is not set up, or the encryption initialization

failed.
System action: Encryption and decryption will not be available for
any devices for which encryption was requested.
User action: Verify that the encryption key file is installed, or
reconfigure the keys via the encryption key configuration program.
System Messages
DLm393E No encryption key available for reading encrypted block

on <devicename>
Description: Encryption was not set up at all, or the encryption

initialization failed, and then an encrypted block was requested to be
read.
System action: The requested block will not be read. A unit check is
returned to the host.
User action: The user should check the encryption configuration.
DLm395E Device <devicename>, no matching decryption key, block

<block#>
Description: No key currently installed on Virtuent was able to

decrypt this encrypted block.
System action: If this error occurs during an I/O initiated by the host,
an I/O error (equipment check) will be returned to the host. During
an Import or Export operation this is a warning rather than an error;
the data will be copied it is original encrypted format to a new
location.
User action: Check that Virtuent is configured with the proper
encryption keys.
DLm397E Device <devicename> is not a supported tape type for

encryption
Description: Encryption is not supported on this device type.

System action: The encryption option is not changed for this device.
User action: The user should choose another device, or reconfigure
the given device.
DLm398E Device <devicename> must be unloaded before changing

encryption
Description: Encryption cannot be changed when a device has a tape

volume mounted.
System action: The encryption option is not changed for this device.
User action: Wait until the tape is unloaded before setting the
encryption key for a device.

System Messages
DLm400E Device <devicename> Data path <pathname> is not

accessible
Description: The specified virtual tape library directory cannot be

accessed at the time of a tape mount.
System action: The mount is ignored and the drive remains Not
Ready without mounting the virtual tape volume. Virtual tape
volumes cannot be mounted on this device until the specified
directory is made accessible to the application.
User action: If the configured directory name is correct, make sure
that it is mounted and accessible. If the directory name was
misconfigured, correct the DLm configuration file PATH= parameter
and restart the DLm application. (The path can be temporarily
corrected with the SET PATH= command.)
DLm401E Device <devicename> error opening <filename>, error=nnn;

<error message>
Description: The virtual volume file could not be opened.

System action: The mount is ignored and the drive remains not ready
without mounting the virtual tape volume.
User action: Examine any preceding related messages and the 'error
message' portion of this message for a description of the problem and
correct the problem. If the problem recurs, contact EMC Customer
DLm402E Device <devicename> cannot LOAD PROTECTED, volume

<volser> does not exist
Description: The specified virtual tape volume specified in the

operator command LOAD ... PROTECTED does not currently exist.
Only existing volumes can be mounted as protected (read-only)
volumes.
System action: The mount is ignored and the drive remains not ready
without mounting the virtual tape volume.
User action: Specify an existing volume in the LOAD ...
PROTECTED command.
System Messages
DLm403E Device <devicename> volume <volser> (filename) invalid

AWS block header at nnnnn (n) xxxxxxxx xxxx,
curblkl=xxxx, prvblkl=xxxx , flags1=xx, flags2=xx
Description: An invalid AWS block header was encountered at offset

'nnnnn' in the specified volume. (n) is one of the following error
codes: (1) error reading block header; (2) prvblkl not zero in first
block header; (3) unknown bit in flags1; (4) unknown bit in flags2; (5)
tapemark record with data length; (6) non-tapemark record with zero
data length; (7) prvblkl contains zero past first block header; (8)
curblkl or prvblkl contains an invalid length value; (10)–(12)
unsupported segmented aws block. The second line of the message
shows the block header contents.
System action: The operation reading the volume fails.
User action: Delete and recreate the volume that has the invalid
format. If this problem recurs, contact EMC Customer Support for
assistance.
DLm404E Device <devicename> Error deleting unused scratch volume

<volser>: error message
Description: The specified volume was created in response to a

scratch tape mount request. Because it was unloaded without ever
having been written to, the DLm tried to delete it. An I/O error
occurred during the attempt to delete.
System action: The volume may or may not been deleted from the
tape library.
error that occurred. Correct the error.
DLm405I Device <devicename> Display: 'message1' 'message2'

[(blink)]
Description: The Host has sent these messages to be displayed on the

virtual tape drive's LED operator display unit.
System action: If the message is a Mount message, and the virtual
drive is currently unloaded, and the VOLSER falls within the range
managed by the DLm, then the specified volume is mounted.
User action: None.

System Messages
DLm406I Device <devicename> CCW:XX @block id nnnnn; rejected due

to supervisor inhibit
Description: The Host sent a CCW that can only be executed while in
supervisor state but a prior Mode Set CCW had disabled this state.
System action: The CCW is not executed, and a unit check status
with command reject sense is sent to the Host.
User action: Investigate why the Host application is attempting to
illegally execute a supervisor state CCW.
DLm407E Device <devicename> Rejecting ACLON request - invalid

synonym
Description: The mainframe request for ACLON is rejected because

the synonym that was passed is not in the synonym list.
System action: The command is rejected.
User action: None.
DLm408I Device <devicename> ACL turned <ON/OFF> <synonym>

<reason>
Description: ACL turned <state>

System action: The ACLON or ACLOFF request was granted. If the
request was ON and a synonym was passed from the mainframe it
will become the default synonym If the request was OFF and there is
a reason, it will be displayed.
User action: None.
DLm409I Command received: 'command'
Description: The specified DLm console command was received

from an outside application.
System action: The specified command is processed.
User action: None.
System Messages
DLm410E Device <devicename> error nnn initializing Volume

<volser>: <error message>
Description: An error occurred while creating the specified virtual

tape volume.
System action: The volume is not mounted.
User action: Examine any preceding related messages and the 'error
DLm411E Device <devicename> AWS block #nnn too large (xxxxxx) to

handle (max=yyyyyy)
Description: The DLm has encountered a tape block in the virtual

tape volume that is larger than the maximum tape blocksize
('yyyyyy') it is capable of presenting to the Host. This block in the
virtual tape file is 'xxxxxx' bytes and is not compressed in the file.
System action: An I/O error is returned to the Host.
DLm412E Device <devicename> AWS block #nnn too large to handle

(max=yyyyyy)
Description: The DLm has encountered a tape block in the virtual

tape volume that is larger than the maximum tape blocksize
('yyyyyy') it is capable of presenting to the Host. This block in the
virtual tape file is compressed and the exact un-compressed block
length, while larger than 'yyyyyy,' is unknown.

System Messages
DLm413E Device <devicename> Unexpected EOF in block header at

nnnnn, file <filename>
Description: An error occurred while accessing the specified virtual

tape volume. 'nnnnn' is the file offset where the error occurred.
System action: The DLm returns an error status to the current Host
I/O request.
User action: Examine any preceding related messages, if any, for
additional error information, and correct the problem. If the problem
DLm414W Device <devicename> tape full writing <data/TM> at PEOT,

file <filename>
Description: The DLm received a write operation from the Host, but
the tape is full.
System action: The write operation fails (Unit Check status,
Intervention Required sense), and the virtual drive is put into the
'Not Ready' (Intervention Required) state. The DLm leaves the drive
in the Not Ready state until the DLm operator changes the drive to
Ready. Most Host systems reports the 'Intervention Required' to the
Host operator, pause the current job, and wait for the drive to come
ready.
User action: Insert another tape in this drive to resume.
DLm415E Device <devicename> Unexpected EOF in data block at

nnnnn, file <filename>
Description: An error occurred while accessing the specified virtual

tape volume. 'nnnnn' is the file offset where the error occurred.
I/O request.
DLm416E Device <devicename> not responding.
Description: The tape device is no longer responding to the DLm.

System action: The DLm sets the tape device to NA (Not Accessible).
User action: None.
System Messages
DLm417E Device <devicename> I/O error: <function description>;

error=nnn; <error message>
Description: An error occurred while reading a virtual tape file.

I/O request.
DLm418W Device <devicename> Hardware decompression not available,

using software only
Description: A hardware-compressed block has been read from the

virtual tape volume, but a hardware compression card is not
available on this DLm to decompress the data.
System action: The data is decompressed with software. This
message displays only once per volume as a reminder.
User action: For best performance, data compressed with a DLm
hardware compression adapter should be decompressed with a
compression adapter as well.
DLm419E Device <devicename> data read [backwards] returned error
Description: An error occurred while reading a virtual tape file.

System action: The Read command is unsuccessful and an error
indication (unit check) is returned to the Host. This message is
preceded by one or more messages that explain the I/O error.
DLm420W Device <devicename> write attempt to protected volume
Description: The volume on the specified device is mounted in

read-only mode, but the Host has attempted to perform a write
operation to the volume.
System action: The Host's write command is rejected (with unit
check status, command reject sense).
User action: Correct the condition that caused the Host to attempt to
write to a read-only volume.

System Messages
DLm421I Device <devicename> signaled end of volume to Host on

<command>
Description: While writing to a virtual tape volume, logical end of

volume (CSW status Control Unit End plus Unit Exception) was
signaled to the Host because the capacity of the virtual volume is
being approached. Command could be Write, Write Tapemark, or
Erase Gap.
System action: The Write command was successful. The logical end
of volume condition remains true and signaled for all subsequent
writes as long as the virtual tape volume remains positioned past the
logical end of volume point.
User action: The Host is expected to close the virtual tape volume
and open a new volume.
DLm422W Device <devicename> <command> at loadpoint
Description: The Host has read or spaced backwards from the virtual
tape volume's loadpoint.
System action: The DLm returns an error status (Read Backwards at
Loadpoint) to the Host I/O request.
User action: This is most likely a Host application error. Correct the
application causing the error.
DLm423W Device <devicename> <command> past <place>
Description: The Host read or positioned past the end of data on the
tape volume or physical end of tape on the physical tape volume.
System action: The DLm returns an error status (Data Check, Tape
Void) to the Host I/O request.
User action: This is most likely a Host application error. Correct the
application causing the error.
DLm424I Device <devicename> Volume <volser> rewound
Description: The operator REWIND command completed

successfully.
System action: The virtual tape volume is now at loadpoint.
User action: None.
System Messages
DLm425E Device <devicename> Data block exceeds maximum of yyyyyy

bytes
Description: The Host wrote a block larger than the maximum

blocksize supported by the DLm.
System action: The block is not written to the virtual tape file, and an
I/O error is returned to the Host's write command.
User action: Change the Host application or JCL to write data blocks
within the DLm capability ('yyyyyy' bytes or less).
DLm426E Device <devicename> write attempt required expanded

headers
Description: The Host attempted to write data with options set (such
as the 'store CRC' option) which requires expanded headers, but the
tape consists of blocks with regular headers. Tape header types
cannot be intermixed on the same tape.
System action: An error status (equipment check) is returned to the
host I/O request.
User action: Clear the options that require expanded headers.
Contact EMC Customer Support for assistance.
DLm427W Device <devicename> write [TM] attempt past end of tape
Description: The Host attempted to write data or a tapemark past the

absolute end of tape capacity.
System action: Application returns an error status (Equipment
Check, Physical End of Tape) to the Host I/O request.
User action: This is most likely a Host application error, since logical
end of tape signal would have been returned for many writes
preceding the failing one. Correct the application causing the error.

System Messages
DLm428I Device <devicename> possibly lengthy operation <command>

begun
Description: The DLm is executing the specified I/O command from

the Host. The DLm has determined that this command may take a
considerable period of time (more than a few seconds) and issues this
message for informational purposes.
System action: The command continues normally. If the command
takes a very long time, it is possible that the Host may cancel the
operation because it thinks a \missing interrupt\ situation has
occurred.
User action: If the Host cancels a job because it thinks a \missing
interrupt\ has occurred while a long positioning command is taking
place, consider increasing the Host's \missing interrupt timer\ for
the DLm devices.
DLm429E Device <devicename> <function description> while device

not ready>
Description: The operation requested requires a tape to be loaded in

the tape drive.
I/O request.
User action: Load the tape drive.
DLm430I Device <devicename> volume <volser> accommodated

old-style AWS header at offset nnnnnn
Description: Earlier DLm releases could write incorrect metadata in a

virtual tape block under certain specific rare conditions. Subsequent
backwards traversal over such a block would result in an I/O error
(Invalid block header). Later DLm releases, including this one,
automatically recover from this metadata error without returning an
I/O error to the host. This message is displayed strictly for
informational purposes.
System action: The virtual tape operation completes successfully.
There is no data loss or error indication returned to the host. The
invalid metadata in this virtual tape volume is NOT corrected by this
action, so this message may be seen in the future as long as this data
exists on this volume.
User action: None.
System Messages
DLm431I Device <devicename> fast operation <command> resumed
Description: The virtual tape application is executing a Host I/O

command that it had previously determined might take a
considerable period of time (more than a few seconds) to complete
(see message DLm427I).During the possibly lengthy operation, a
suitable index entry has been encountered to complete the operation
quickly.
System action: The command continues normally.
User action: None.
DLm432I Device <devicename> possibly lengthy operation (<command>

from <blockid>) complete (at <blockid>)
Description: The virtual tape application has completed executing a

Host I/O command that it had previously determined might take a
considerable period of time.
System action: The command completed normally, although possibly
slowly.
User action: None.
DLm434W WARNING: Path <pathname> disk usage at nn%
Description: The disk usage for the specified tape library has
exceeded the current WARNING value.
System action: The DLm continues to warn at every percentage
change as long as the usage exceeds the WARNING value.
User action: Consider scratching and erasing unneeded virtual tape
volumes to free some disk space.
DLm436I Attempting to recover space from scratch volumes in

<pathname>
Description: The disk usage for the specified tape library directory
has exceeded the current RECOVER value.
System action: The DLm erases the data from previously scratched
virtual tape volumes until the disk usage falls to (RECOVER minus
RECOVERAMT) percent.
User action: Consider scratching and erasing unneeded virtual tape
volumes to free some disk space.

System Messages
DLm437I Finished space recovery, nn bytes recovered from scratch

volumes in <pathname>
Description: The DLm has finished attempting to recover space for

the specified tape library directory because either (1) the disk space
has been reduced by RECOVERAMT, or (2) it has found no more
previously scratched volumes to erase. ‘nn’ bytes is the number of
bytes erased from scratch volumes and made available for reuse.
User action: None.
DLm438I Finished space recovery, nn bytes recovered from nn

scratch volumes in <pathname>
Description: The DLm application has recovered the specified

amount of space from scratch tapes that have surpassed the erase
policy retention time.
User action: None.
DLm439I Device <devicename> Volume <volser> unloaded without I/O
Description: The specified virtual tape volume was unloaded.

During the time that the volume was mounted, the Host did not
perform any reads from or writes to this volume.
System action: The specified drive enters the Not Ready state and is
available for another job. If the tape was a scratch tape when it was
mounted, it will be returned to the scratch state.
User action: None.
DLm440I Device <devicename> Volume <volser> mounted
Description: The specified virtual tape volume has been mounted;

the device now presents a \ready\ interrupt to the Host.
User action: None.
System Messages
DLm441I Device <devicename> initializing new [flat] volume

<volser> [(labeled)|(unlabeled)]
Description: A mount of a non-existent volume has been requested.

System action: The new virtual tape volume is created and
initialized.
User action: None.
DLm442E Device <devicename> unable to allocate an SL/AL/NL

scratch volume: <error message>
Description: Loading of a scratch volume was requested, but a

scratch volume with the requested label type could not be found. The
'error message' portion of this message explains the reason.
System action: The requested volume is not loaded and the drive
remains Not Ready.
User action: Correct the problem preventing the scratch volume
allocation and try to reload a scratch tape. If no scratch volumes are
available, consider scratching some old, unneeded volumes or
INITIALIZE some more scratch volumes.
DLm443E Device <devicename> unable to create new scratch volume

<volser>
Description: Loading of a new scratch volume was requested, but the

new virtual tape volume could not be created.
System action: The requested volume is not loaded and the driver
remains Not Ready.
User action: One or more previous messages should explain the
reason for the problem. Correct the problem preventing the scratch
volume allocation, and try to reload a scratch tape. For instance, type
the Query Space command to determine if any free space exists on
the tape library disk; if no space is available, delete some unneeded
volumes to free some disk space. Make sure that a valid, writable
directory is specified in the configuration file for this device, and that
the directory is currently mounted and accessible. If all possible
scratch tapes are already in use, scratch some existing volumes for
reuse.

System Messages
DLm444I Device <devicename> new scratch volume <volser> created
Description: Loading of a scratch volume was requested, and a new

virtual tape volume was created to accommodate the request.
System action: The specified volume was created, initialized, and
loaded on the specified drive.
User action: None.
DLm445I Device <devicename> cannot initialize protected new

volume <volser>
Description: The DLm has created the new volume 'volser', but is not
able to initialize it because it is read-only. This is only possible when a
manual LOAD command with the PROTECTED option is typed for
a new (non-existing) volume.
System action: The volume is created and mounted, but it appears to
the Host as an empty, un-initialized (and read-only) tape.
User action: Do not do this.
DLm446E Device <devicename> cannot create volume <volser>, path

<pathname> is read-only
Description: The specified volume does not exist and cannot be

opened for writing because the virtual tape library directory
'pathname' is write protected.
System action: The volume is not created, the mount request is
ignored, and the device remains not ready.
User action: To write new volumes, make sure that the virtual tape
library is correctly mounted and is write-enabled for user 'vtape.'
DLm447W Device <devicename> invalid volid 'volser', mount request

ignored
Description: The Host requested the mounting of a VOLSER that is

not a valid IBM VOLSER.
System action: The mount request is ignored and the device remains
not ready.
User action: Correct the Host JCL to request a valid IBM VOLSER. An
IBM standard VOLSER consists of the uppercase letters A–Z,
numbers 0–9, and the hyphen.
System Messages
DLm448W Device <devicename> volume <volser> already mounted, new

mount request ignored
Description: The Host requested the mounting of a volume, but the

specified drive already has a virtual tape volume mounted. The
currently mounted tape is not at loadpoint.
System action: The mount request is ignored. The volume already
mounted on the drive remains mounted.
User action: Correct the Host JCL that caused a mount request to be
sent to a drive that already has a volume mounted. If the Host is
finished with the volume that is currently mounted on the drive, you
can manually unload that volume and then manually mount the new
volume.
DLm449I Device <devicename> Label request changed from ' ' to

default 'X'
Description: The current mount request did not specify a desired

label type, so it was set to the default type configured on the DLm for
this virtual tape device. The only value which you see for 'X' is 'A' for
ANSI labels, because this message does not appear if the default label
type is 'S' for IBM standard labels.
System action: The mount process continues, using the default label
type configured for this device.
User action: None, unless the default label type is incorrect, in which
case the DLm configuration default should be changed or an explicit
label type should be requested in the JCL.
DLm450W Volume <volser> file is busy on device devicename1, mount

on devicename2 is ignored
Description: The mounting of a virtual tape volume has been

requested, but that volume is currently mounted on another virtual
tape drive. A volume can be mounted on only one drive at a time.
System action: The mount request is ignored.
User action: Correct the Host operational issue that resulted in the
duplicate request for the same volume. Restart the second job when
the virtual tape volume becomes available.

System Messages
DLm451E Volume <volser> file is open elsewhere, mount on

<devicename> ignored
Description: Mounting of the specified virtual tape volume has been

requested, but the volume is currently open by another program.
System action: The mount retries several times over several seconds.
If the volume does not become free, the mount request is ignored.
duplicate request for the same volume by two programs at the same
time. Restart the second job when the virtual tape volume becomes
available.
DLm452W Device <devicename> is quiesced, mount ignored

requested, but the specified drive is in the 'quiesced' state, meaning it
does not accept any tape mounts until it is 'unquiesced' (or until the
DLm is restarted).
User action: UNQUIESCE the drive, or use a different drive.

mount request honored
Description: The Host requested the mounting of a volume, and the

currently mounted tape is at loadpoint.
System action: The mount request is honored. The volume already
mounted on the drive is unloaded and the new mount request is
processed.
User action: Correct the Host JCL that caused a mount request to be
sent to a drive that already has a volume mounted.
System Messages
DLm454E Device <devicename> volume <volser> not found
Description: The DLm was requested to load a virtual tape volume

that does not exist in the DLm tape library.
System action: The drive remains unloaded and Not Ready.
User action: Verify that the correct volume is being requested. Also
check that the tape library directories are properly mounted and are
accessible to the DLm. If the requested volser is for a scratch tape,
make sure that there are scratch volumes, initialized with the correct
label type, available.
DLm455E Error locking volume <volser> (filename); <error message>
Description: An error occurred while trying to mount the specified

virtual tape volume.
User action: Consult any preceding related messages and the 'error

mount request honored
Description: The Host requested the mounting of a volume, and the

currently mounted tape is not at loadpoint, but the drive had
received an Unassign command from the Host while the currently
mounted tape was mounted.
System action: The mount request is honored. The volume already
mounted on the drive is unloaded and the new mount request is
processed.
User action: Consider correcting the Host JCL or Host operating
system that allowed a mount request to be sent to a drive that already
had a volume mounted. Contact EMC Customer Support for
additional assistance.

System Messages
DLm457E Device <devicename> volume <volser> already mounted, new

mount request ignored
Description: The Host requested the mounting of a volume, but the

specified drive already has a virtual tape volume mounted, and the
currently mounted tape is NOT at loadpoint, and the drive had not
received an Unassign command from the Host while the currently
mounted tape was mounted.
System action: The mount request is ignored. The volume already
mounted on the drive remains mounted.
User action: Consider correcting the Host JCL or Host operating
system that allowed a mount request to be sent to a drive that already
had a volume mounted. Contact EMC Customer Support for
additional assistance.

mount request deferred
Description: The Fujitsu Host requested the mounting of a volume,

and the specified drive already has a virtual tape volume mounted.
System action: The mount request will be honored after the Host
unloads the volume currently mounted on the drive.
User action: If possible, correct the Host JCL that caused a mount
request to be sent to a drive that already has a volume mounted.
DLm459W Device <devicename> volume <volser> has a corrupted

IBM/ANSI label set
Description: During opening of an existing virtual tape volume, the

DLm has determined that the volume contains a valid VOL1 label,
but the rest of the header label set is missing, incomplete, invalid, or
corrupted in some way.
System action: This is a warning message only. The mount completes
successfully and is available for normal use by the Host.
System Messages
User action: The Host most likely complains about the invalid labels;
take the appropriate action required by the Host. If the Host refuses
to use the corrupted volume as is, perform a reinitialization of the
virtual tape volume using the standard Host initialization
procedures. Try to determine the reason the Host previously wrote
invalid labels to this tape volume. This condition is most often caused
by an error on the Host during volume initialization or at some other
time when the Host is writing the volume labels. In particular, this
problem has been seen when a Host job is cancelled while it is
opening an output tape.
DLm460I Device <devicename> volume <volser> file renamed to

<filename>
Description: The Host has written a HDR1 label in a flat file.

System action: The virtual volume's disk file was successfully
renamed to the new filename as shown.
User action: None.
DLm461I Device <devicename> performing deferred mount request
Description: The Fujitsu Host requested the mounting of a volume

while the specified drive already had a virtual tape volume mounted.
The drive is now unloaded and the mount request will be
reevaluated.
System action: The mount request will be attempted at this time.
User action: If possible, correct the Host JCL that caused a mount
request to be sent to a drive that already had a volume mounted.
DLm462W Mount error renaming volume <volser> <pathname> to

<pathname>: <error message>; retrying…
Description: The host has asked for a previously scratched volume

by specific volser. DLm was unable to rename the scratch volume
(~VOLSER) to an active volume (VOLSER).
System action: The rename will be retried several times over several
seconds. If the rename does not succeed during this time the mount
request will be ignored.
User action: Refer to any earlier messages and the 'error message'
portion of this message to determine the cause of the failure.

System Messages
DLm463W Volume <volser> file is open elsewhere, retrying...

requested, but the volume is currently open by another program or
system.
System action: The mount will be retried several times over several
seconds. If the volume does not become free during this time, the
mount request will be ignored.
duplicate request for the same volume by two programs at the same
time. Restart the second job when the virtual tape volume becomes
available.
DLm464E Device <devicename> volser \volser\ prefix differs from

existing volser \volser\
Description: The Host is attempting to write a VOL1 label with a

different VOLSER onto the virtual tape volume, but the new volser
does not start with the same two character volser prefix as the
existing VOLSER.
System action: The DLm rejects the Host's write, returning a Unit
Check status and Command Reject sense.
User action: You can only write over an existing volser with a new
VOLSER of the same two character prefix. Correct the JCL or operator
procedure that attempted to rename the volume.
DLm465E Device <devicename> invalid volser 'volser' in VOL1 label
Description: The Host is attempting to write a new VOL1 label to the

virtual tape volume, but the VOLSER in the VOL1 label is invalid.
User action: Correct the Host job that is attempting to write the
invalid VOLSER to the DLm.
System Messages
DLm466E Device <devicename> volser 'volser' from VOL1 already

exists [as scratch]

different VOLSER onto the virtual tape volume, but the new volser is
the same as a volume that already exists in the DLm tape library.
User action: Correct the Host job that is attempting to write the
duplicate VOLSER to the DLm, or delete the existing volume on the
DLm before rerunning the job.
DLm467E Device <devicename> error renaming volume <volser1>

(filename) to <volser2> (filename); <error message>

different VOLSER onto the virtual tape volume, but the DLm is
failing in its attempt to rename the mounted volume to the new
volume name.
of this message to determine the cause of the failure. If the problem
cannot be corrected, contact EMC Customer Support for assistance.
DLm468I Device <devicename> overwrote VOL1 with [data|tapemark]

on volume <volser>
Description: The volume mounted on this device was previously a

labeled volume, but the Host has written either data or a tapemark at
loadpoint, erasing the VOL1 label. The virtual tape is now an
unlabeled volume.
User action: None.

System Messages
DLm469I Device <devicename> volume <volser1> renamed to <volser2>

(filename)
Description: The Host has written a VOL1 label with a different

VOLSER onto the virtual tape volume.
System action: The virtual volume file was successfully renamed to
the new VOLSER.
User action: None.
DLm470E MOUNT volume 'volser' failed
Description: Mounting of the specified virtual tape volume was

unsuccessful.
System action: The mount request is ignored and the drive remains
Not Ready.
User action: This message are preceded by one or more messages that
explain the reason for the mount failure. Correct the error indicated
in the preceding messages.
DLm471E Device address xxxx on GROUP n doesn't exist
Description: Mounting of a virtual tape volume on OSADDR 'xxxx'

was requested by the EMC mount program, but the specified device
does not exist in the specified GROUP.
Not Ready. A return code of 0x82 is returned to the Host program.
User action: Reconfigure the EMC mount program and DLm to use
the proper device addresses.
DLm472I Volume <volser1> is currently on <devicename>, cannot

mount <volser2>
Description: Mounting of volume 'volser2' on the specified drive was

requested by the EMC mount program, but the specified device
already has the virtual tape volume 'volser1' mounted.
User action: Correct the operational issues that resulted in the
attempt to mount on a busy drive.
System Messages
DLm473E Invalid mount request x'xx' 'aaaaaaaa' 'bbbbbbbb'
Description: Mounting of a virtual tape volume was requested by the

EMC mount program, but the second word of the request
('bbbbbbbb') did not contain a proper drive designation.
DLm474E No free device in default GROUP n to mount 'volser'
Description: Mounting of a virtual tape volume on any available

drive address was requested by the EMC mount program, but there is
no free drive in this GROUP.
User action: Retry the Host mount when a virtual drive becomes
available.
DLm475E No free device in GROUP n to mount 'volser'
Description: Mounting of a virtual tape volume on ANY available

drive address was requested by the EMC mount program, but there is
no free drive on this LPAR and GROUP.
User action: Retry the Host mount when a virtual drive becomes
available.
DLm476W WARNING: Device <devicename> OSADDR is 000

EMC mount program, but the device upon which the volume is being
mounted has an OSADDR of 000.
System action: The mount proceeds, but the mount device address of
000 is reported back to the Host program. If the mount request was
for a specific device address, this probably would not be of any
consequence, but if the request was for 'Any' drive, the Host program
is not able to determine on which drive the volume was mounted.
User action: Reconfigure the DLm and add the correct OSADDR
parameter for each DLm device that is attached to a VSE system.

System Messages
DLm477E Mount requested on <devicename1> by <devicename2> failed
Description: Mounting of a virtual tape volume on any available

drive address was requested by the EMC mount program, but the
volume could not be mounted on <devicename2>. This message is
preceded by one or more messages that explain the reason for the
mount failure.
User action: See any preceding messages for the reason for the mount
failure and correct the problems.
DLm478I Device <devicename> Requesting mount 'volser' on 'device'

mount program or a tape manager on the host.
System action: The DLm attempts to mount the requested volume on
the requested drive.
User action: None.
DLm479W Device <devicename> volume <volser> is completely empty!
Description: The specified tape volume was successfully mounted,

but contains no data or tape marks.
System action: The specified volume is mounted as requested, but
any attempts to read from the volume results in an I/O error (Unit
Check status, Tape Void sense) being presented to the Host.
User action: Be certain that the correct volume is being requested. If
necessary, delete and reinitialize the virtual tape volume.
DLm480E Both active and scratch volser volumes exist in

<pathname>, mount ignored
Description: While mounting a volume, the DLm found both active

(VOLSER) and scratch (~VOLSER) copies of the volume in the same
tape library.
System action: The mount request is ignored, and the drive remains
not ready.
User action: Determine which, if any, of the volumes is valid and
should be kept, and delete the invalid volume.
System Messages
DLm481E <function> error renaming volume <volser> (filename);

<error message>
Description: The Host has asked for a previously scratched volume

by specific volser. The DLm was unable to rename the scratch volume
(~VOLSER) to an active volume (VOLSER).
System action: The mount request is ignored, and the drive remains
Not Ready.
of this message to determine the cause of the failure.
DLm482I Scratch tape <volser> made active
Description: The Host has asked for a previously scratched volume

by specific volser.
System action: The DLm returns the requested volume to active
status by renaming it from ~VOLSER to VOLSER, then mounts the
volume.
User action: None.
DLm483E Error scratching/unscratching/erasing volume <volser>

(filename); <error message>
Description: An error has occurred while scratching, unscratching, or

erasing a scratch tape.
System action: The scratch, unscratch, or erase function fails.
of this message to determine the cause of the failure.

System Messages
DLm484W Mount loop on device <devicename>, volume <volser> mount

ignored
Description: The Host repeatedly requested the mounting of the

specified volume, but immediately unloaded the volume each time
without reading past labels or writing to it. This usually signifies that
the Host is not satisfied with the contents of the virtual tape volume,
so it unloads it and requests it again.
System action: The last mount request is ignored, and the drive
remains Not Ready.
User action: Examine the Host console to determine the problem
with the volume. Correct the Host JCL to use the correct volume or a
different volume.
DLm485W Device <devicename> Mount of unlabeled [SCRTCH/PRIVAT]

volume ignored
Description: The Host requested the mounting of an unlabeled

scratch tape. The DLm does not support the mounting of unlabeled
scratch tapes because there is no way to track the volume by volser
after the Host writes unlabeled data.
Not Ready.
User action: Specify a specific VOLSER for unlabeled usage, or
specify a labeled tape for scratch usage.
DLm486E Device <devicename> Unable to allocate a [SCRTCH/PRIVAT]

volume
Description: The mount request for a scratch tape failed.

Not Ready. This message is preceded with one or more messages that
explain the reason for the mount failure.
User action: Correct the error and rerun the job.
DLm487I Device <devicename> volume 'filename' mount will be

retried
Description: The specified virtual tape file mount request

automatically retries.
System action: The load request is retried.
User action: None.
System Messages
DLm488I Device <devicename> Unused scratch volume <volser>

deleted
Description: The specified volume was created in response to a

scratch tape mount request, but it was unloaded without ever being
written to.
System action: The volume is deleted from the DLm disk.
User action: None.
DLm489E Device <devicename> Error loading volume 'filename'
Description: The specified virtual tape file could not be opened.

System action: The load request is ignored and the device remains
Not Ready. This message is preceded with one or more messages that
explain the reason for the error.
User action: Correct the error and rerun the job.
DLm490I Device <devicename> Volume <volser> unloaded
Description: The specified virtual tape volume was unloaded.

System action: The specified drive enters the Not Ready state and is
available for another job.
User action: None.
DLm491I Device <devicename> on SMB filesystem, max volume size

changed to 2G
Description: The DLm has detected that the tape library for the
specified virtual tape drive is on a CIFS/SMB filesystem and the
current maximum volume setting for this drive was greater than 2
GB.
System action: The maximum volume size for this drive is adjusted
to 2 GB. If the tape library path is ever changed back to a non-SMB
filesystem, the maximum volume size automatically changes back to
the previous value.
User action: None.

System Messages
DLm492I Device <devicename> not on SMB filesystem, max volume

size changed back to size
Description: The DLm has detected that the tape library for the
specified virtual tape drive is no longer on a CIFS/SMB filesystem,
and the maximum volume setting for this drive was previously
adjusted to 2 GB.
System action: The maximum volume size for this device is adjusted
back to the previous value.
User action: None.
DLm493W Device <devicename> write [TM] attempt to protected

volume
Description: The Host attempted to write data or a tapemark to this

read-only tape volume.
System action: The DLm returns an error (Command Reject, File
Protected) to the Host application.
User action: Correct the JCL, program or operational procedure that
caused the Host to try to write to a protected volume, or mount the
volume in read-write mode.
DLm494W Device <devicename> disk full writing data/TM at nnnnnnn,

file <filename>
the tape library disk is full. 'nnnnnnn' is the number of bytes written
so far.
Intervention Required sense), and the virtual drive is put into the
'Not Ready' (Intervention Required) state. The DLm leaves the drive
in the Not Ready state until the DLm operator changes the drive to
Ready. Most Host systems reports the 'Intervention Required' to the
Host operator, pause the current job, and wait for the drive to come
ready.
User action: When space is available on the tape library disk, execute
the READY command to this drive to resume.
System Messages
DLm495E Device <devicename> disk full writing data/TM at nnnnnnn,

file <filename>
the tape library disk is full. The DLm cannot recover and continues
because the tape library is on an NFS filesystem. 'nnnnnnn' is the
number of bytes written so far.
Equipment Check sense). The contents of the volume being written is
unpredictable.
User action: Rerun the job after more space is made available on the
target tape library filesystem.
DLm496W Device <devicename> write compression suppressed by

IDRC=NO / forced by IDRC=FORCE>
Description: Either the Host requested compression of the output

data but the DLm virtual tape drive is currently set to IDRC=NO, or
the Host did not request compression but the drive is currently set to
IDRC=FORCE. This message is only displayed once per volume.
System action: If IDRC=NO is set, the data is written uncompressed
to the DLm tape library. If IDRC=FORCE is set, the data is
compressed.
User action: None, unless you truly wanted the data to be
compressed or not compressed in a different way. In that case,
reconfigure the DLm virtual tape drive with the correct IDRC
parameter, or type the DLm console command SET
IDRC=ON/OFF/FORCE [DEV=devicename] to temporarily
override the DLm configuration.

System Messages
DLm497W Device <devicename> Hardware [de]compression configured

off, using software only
Description: The DLm has hardware compression/decompression

capability but is currently configured to not use the hardware facility
for compression/decompression. This message displays once per
volume whenever this condition is true.
System action: The data is compressed or decompressed with
software rather than with the compression hardware.
User action: None, unless you truly wanted the data to be
compressed or decompressed with the compression hardware (which
is much faster than software compression/decompression). In that
case, type the DLm command SET HWCOMPRESSION=ON or SET
HWDECOMPRESSION=ON to reactivate the hardware
compression/decompression feature.
DLm498E Device <devicename> Volume <volser> error uncompressing

data block #nnnnn: nn (error message)
Description: An error occurred while reading compressed data from

the tape file.
System action: The DLm returns an error (Data Check) to the Host.
User action: If possible, recreate the corrupted volume. If this
problem recurs, contact EMC Customer Support for assistance.
DLm499W Device <devicename> Volume <volser> error compressing

data: nnn
Description: An error occurred while writing compressed data to the

virtual tape file.
System action: The data is written uncompressed to the tape library.
for assistance.
System Messages
DLm500I Scratchsing/Unscratching/Erasing of volume <volser>

requested by host via device <devicename>
[dsn='datasetname']
Description: Scratching, unscratching, or erasing of the specified

virtual tape volume was requested by the Host. If the request is
further qualified by a data set name, it is shown in the message.
System action: The DLm attempts to scratch, unscratch, or erase
(delete the data of a scratch volume) the specified volume on the
DLm tape library disk. If a data set name is specified, the volume is
first checked to confirm that it contains the specified dataset.
User action: None.
DLm501I Volume <volser> (filename)

scratched/unscratched/erased/deleted
Description: Scratching, unscratching, erasing, or deletion of the

specified virtual tape volume as requested by the Host was
successful.
System action: The specified virtual tape volume was scratched,
unscratched, erased (data deleted), or deleted (file deleted) from the
DLm tape library disk as requested. A return code of 0 (success) was
returned to the Host application.
User action: None.
DLm502W Volume <volser> is currently on <devicename>, cannot

scratch/unscratch/erase

virtual tape volume was requested by the Host, but the specified
volume is in use.
System action: The virtual tape volume status is not changed. A
return code of 0x06 is returned to the Host application.
User action: Change the tape status later when it is not in use.

System Messages
DLm503E Error scratching/unscratching/erasing volume <volser>

Description: An error occurred during the scratching, unscratching,

or erasing of the specified virtual tape volume requested by the Host.
System action: The volume is in an undefined state. It may have been
scratched or it may still be active, depending on the error that
occurred. A return code of 0x07 (volume does not exist) or 0x08 (any
other error) is returned to the Host application.
User action: Consult any preceding related messages and the 'error
DLm504E Scratching/unscratching/erasing of invalid volume

'volser' requested by host via device <devicename>

virtual tape volume was requested by the Host, but the requested
volser is an invalid VOLSER.
System action: The scratch, unscratch, or erase request is ignored. A
return code of 0x05 is returned to the Host application.
User action: Correct the VOLSER being sent by the Host program.
DLm505E Device <devicename> received invalid

scratch/unscratch/erase/execute request, length=nnn

virtual tape volume, or execution of a DLm console command, was
requested by the Host, but the data sent by the Host was of an
incorrect length.
System action: The Host initiated request is ignored. A return code of
0x01 is returned to the Host application.
User action: Correct the data being sent by the Host program.
System Messages
DLm506E Both active and scratch <volser> volumes exist in

<pathname>!
Description: Scratching or unscratching of the specified virtual tape

volume was requested by the Host, but the DLm found that the files
VOLSER (not scratch) and ~VOLSER (scratch) both exist in the same
tape library.
System action: The scratch or unscratch request is ignored. A return
code of 0x03 is returned to the Host application.
DLm507E Scratch/Unscratch Error renaming volume <volser>

Description: Scratching or unscratching of the specified virtual tape

volume was requested by the Host, but the DLm encountered a
problem while renaming the volume to the specified filename.
System action: The scratch or unscratch request is ignored. A return
code of 0x08 is returned to the Host program.
User action: See the error message portion of this message to
determine the reason for the error.
DLm508I Volume <VOLSER> (filename) erased
Description: The specified virtual tape volume was erased because

the length of time since it was scratched has surpassed the erase
policy retention time.
System Action: The specified virtual tape volume was erased (its
data deleted) and its storage space returned to free space for reuse.
User Action: None.

System Messages
DLm510W Device <devicename> data path <pathname> is not

accessible
Description: Scratching, unscratching, or erasing of a virtual tape

volume was requested by the Host, but the specified tape library
directory is not currently accessible.
return code of 0x0A is returned to the Host program.
User action: Make sure that the device through which
scratch/unscratch/ erase requests are sent by the Host application is
assigned to the correct tape library directory, and that the directory is
read-write accessible by the user 'vtape'.
DLm511W Device <devicename> data path <pathname> is not writable

volume was requested by the Host, but the specified tape library
directory is not currently writable.
return code of 0x0B is returned to the Host program.
scratch/unscratch/ erase requests are sent by the Host application is
assigned to the correct tape library directory, and that the directory is
read-write accessible by the user 'vtape.'
DLm512E Device <devicename>

Scratching/Erasing/Unscratching/Deleting not allowed on
<drive>

volume was requested by the Host, but the DLm virtual device is
currently assigned to a physical tape drive.
System action: The scratch, unscratch, erase, or delete request is
ignored. A return code of 0x0A is returned to the Host program.
scratch/unscratch/ erase/delete requests are sent by the Host
application is assigned to a virtual tape library directory, not a
physical tape drive.
System Messages
DLm515W Volume <volser> file is open elsewhere, cannot

scratch/unscratch/erase
Description: While considering the specified virtual tape volume for

scratching, unscratching, erasing, it was found that the specified
volume was currently being accessed on another program.
System action: The scratch/unscratch/erase request is ignored. If the
action was requested by the Host, a return code of 0x09 is returned to
the Host application.
User action: Scratch/unscratch/erase the volume later when it is not
in use.
DLm516E Error locking volume <volser> (filename); <error message>

scratching, unscratching, erasing, an I/O error occurred while trying
to lock the file for exclusive access.
action was requested by the Host, a return code of 0x08 is returned to
the Host program.
User action: Make sure that the specified volume exists, is owned by
the user 'vtape,' is writable, and is not in use by any other program.
Scratch/unscratch/erase the volume later when it is not in use. If the
problem recurs, contact EMC Customer Support for assistance.
DLm517E Invalid VOL1 label in volume <volser> (filename)

scratching, unscratching, erasing, it was found that the specified
volume does not contain a valid VOL1 label.
action was requested by the Host, a return code of 0x0C is returned to
the Host program.
User action: Specify a valid standard labeled tape in the request. If
the volume has somehow been overwritten with incorrect contents,
delete and reinitialize the volume.

System Messages
DLm518E Mismatched volser <volser1> found in <volser2>

(<filename>)

scratching, unscratching, erasing, it was found that the VOLSER
(volser1) found in the VOL1 label on the volume does not match the
one expected (volser2).
action was requested by the Host, a return code of 0x0D is returned to
the Host program.
User action: If the volume has somehow been overwritten with
incorrect contents, delete the volume manually and reinitialize the
volume.
DLm520E Invalid HDR1 label in volume <volser> (<filename>)

scratching, unscratching, erasing, it was found that the volume does
not contain a valid HDR1 label.
action was requested by the Host, a return code of 0x0E is returned to
the Host program.
User action: If the volume has somehow been overwritten with
incorrect contents, delete and reinitialize the virtual tape volume.
DLm521E Volume <volser> (filename) has data set 'dataset1', not

'dataset2'

scratching, unscratching, erasing, it was found that the volume
contains the data set 'dataset1,' not the data set specified by the Host
request ('dataset2').
System action: The scratch/unscratch/erase request is ignored. A
return code of 0x0F is returned to the Host program.
User action: Correct the data being sent by the Host application.
System Messages
DLm522E Invalid date in scratch request 'xxxxxxxxxxxx'
Description: Scratching, unscratching, or erasing of a volume was

requested by the Host, but the data sent by the Host program
contains an invalid date. The date shown (xxxxxxxxxxxxx) is in
hexadecimal as received from the Host program.
return code of 0x10 is returned to the Host program.
DLm523E Volume <volser> (filename) created too recently (nnnnnn)

to scratch today (nnnnnn)
Description: Scratching of a virtual tape volume was requested by

the Host, but the date found in the virtual tape volume's HDR1 label
shows that the file was created on the same date that (or later than)
the scratch request is being made. A volume can only be scratched
one or more days later than the day on which it was created.
System action: The scratch request is ignored. A return code of 0x11
is returned to the Host program.
User action: Resubmit the scratch request to the DLm at least one day
after the file on the volume was created.
DLm524W Volume <volser> (filename) already

scratched/unscratched/erased

volume was requested by the Host, but the specified virtual tape
volume is already in the state designated in the message.
return code of 0x02 is returned to the Host program.
User action: Be careful not to submit duplicate
scratch/unscratch/erase requests to the DLm.

System Messages
DLm525E Volume <volser> (filename) not a scratched/erased tape
Description: Erasing or deleting a scratch volume was requested by

the Host, but the specified virtual tape volume is not in the scratched
(for erase) or erased (for delete) state.
System action: The erase or delete request is ignored. A return code
of 0x04 is returned to the Host program.
User action: Be careful to submit erase requests for previously
scratched volumes only, or delete requests for previously erased
volumes only.
DLm526E Volume <volser> (filename) cannot un-scratch, already

erased
Description: Un-scratching of the specified virtual tape volume was

requested by the Host, but virtual tape volume has already been
erased and cannot be un-scratched. Its former data cannot be
recovered.
System action: The unscratch request is ignored. A return code of
0x02 is returned to the Host program.
User action: Once a virtual tape volume has been erased, it cannot be
un-scratched.
DLm532E Directory at <pathname> is not a DLM filesystem\n
Description: An OCFS/2 support license is installed, but the

Distributed Lock Manager directory doesn't exist.
System action: OCFS/2 support is disabled until the problem is
corrected and the DLm is restarted.
DLm534E OCFS/2 DLM initialize failed, error: error message
Description: OCFS/2 Distributed Lock Manager initialization failed.

corrected and the controller is restarted.
System Messages
DLm535E Error opening DLM log file 'filename', error:error

message
Description: An error occurred while attempting to open the

Distributed Lock Manager log file.
corrected and the controller is restarted.
User action: If the error messages describes a correctable problem,
correct the problem and restart the controller. Contact EMC Customer
Support if more assistance is needed.
DLm550I Command received from Host: device <devicename>: cmd =

'command'
Description: The specified DLm console command was sent from the
Host through the specified virtual tape device.
System action: The command is executed. Depending on the results
of the command, a return code returns to the Host program.
User action: If the command is successful, none. Otherwise,
determine the reason for the DLm console command failure and
correct the problem.

System Messages
DLm551E Host-initiated commands not allowed
Description: A DLm console command was sent from the Host, but
the DLm is not configured to allow Host-initiated commands.
System action: The command not be executed. A failure code be
returned to the Host program.
User action: If you want the Host to be able to initiate DLm console
commands, correct the DLm configuration to allow for this feature.
DLm552E Unable to locate script <scriptname>: <error msg>
Description: A DLm RUN console command was sent from the Host,
but the DLm is not able to locate the specified script.
System action: The command is not executed. A failure code returns
to the Host.
User action: Check that the correct script name was specified in the
RUN command, and that the script file has the proper permissions to
be executed by the DLm user 'vtape.'
DLm553E Unable to execute script <scriptname>
but the DLm is not able to execute the specified script.
to the Host.
User action: Check that the correct script name was specified in the
RUN command, and that the script file has the proper permissions to
be executed by the DLm user 'vtape.'
DLm555E RUN command not allowed
but the DLm is not configured to allow the RUN command.
to the Host.
User action: If you want the Host to be able to initiate DLm RUN
commands, correct the DLm configuration to allow for this feature.
System Messages
DLm556W RUN process #nnnnn has not finished in nn seconds
Description: A DLm RUN console command was sent from the Host
and executed by the DLm, but the specified script did not complete
within the specified time limit.
System action: The DLm cancels the process identified by process ID
#nnnnn. A failure code returns to the Host.
User action: If the specified script normally takes longer than the
time specified, specify a longer time on the RUN command.
DLm573E Error while validating directory <directory>: <error

message>
Description: During the directory validation process a problem was

discovered.
System action: The specified directory cannot be used for the
intended purpose.
User action: Verify the existence and properties of the directory.
Contact EMC Customer Support for assistance.
DLm580E Error getting <volser> file status; <error message>
Description: While closing a virtual tape file, an error occurred in

reading the file's current status information.
System action: Processing continues. There may be problems in
accessing this file later.
User action: The error message portion of this message identifies the
reason for the error. Correct the reason if possible. If the problem

System Messages
DLm581E Device <devicename> Error setting volser file status to

<status>; <error message>
Description: During closing of a virtual tape file, an error occurred

while setting the file's final status information.
System action: Processing continues. There may be problems in
accessing this file later.
User action: The error message portion of this message identifies the
reason for the error. Correct the reason if possible. If the problem
DLm582I Device <devicename> volume <volser> made/left read-only
Description: This message is displayed when an output virtual tape

volume written to a write-once filesystem is unloaded and the
volume has been made a read-only volume.
System action: The virtual tape volume is now permanently
read-only.
User action: None.
DLm607E Device <devicename>, Volume <volser>: error while setting

scratch state
Description: An error occurred while trying to scratch or unscratch a

virtual tape file.
I/O request.
DLm612E Device <devicename>, Volume <volser>: <message>
Description: The DLm experienced an internal error, and outputs a

detailed error message.
I/O request.
System Messages
DLm614E Device <devicename>, Volume <volser>: could not get hint

for block: %lld
Description: The DLm was unexpectedly unable to find an entry in

an index of block IDs while performing a LOCATE.
System action: The DLm returns an error status to the Host's
LOCATE request.
DLm631E Device <devicename>, Volume <volser>: could not find

block %lld
Description: The DLm was unable to locate a block specified in a

LOCATE request.
System action: The DLm returns an error status to the Host's
LOCATE request.
DLm660I Device <devicename>, Volume <volser>: For Unisys only,

trying again as SCRTCH
Description: The Host requested that the DLm mount volume

<volser>, but the volume does not exist. For Unisys devices only, the
DLm now performs a SCRTCH mount request.
System action: The DLm attempts to mount a scratch volume.
User action: None.
DLm671E Device <devicename>, Volume <volser>: error while closing

tape
Description: An error occurred while unmounting a virtual tape.

I/O request.

System Messages
DLm674E Device <devicename>, Volume <volser>: Bad path specified:

full path(%s)
Description: An internal error occurred while the DLm was

attempting to construct a path name.
I/O request.
DLm676E Device <devicename>, Volume <volser>: internal I/O error
Description: The DLm experienced an internal I/O error.

I/O request.
DLm677E Device <devicename>, Volume <volser>: error while

renaming tape to '%s'
Description: An error occurred while changing a tape's volser.

I/O request.
System Messages
DLm678E Device <devicename>, Volume <volser>:

Encryption/decryption failed
Description: An error occurred while encrypting or decrypting data.
System action: The DLm application returns an error status to the
current Host I/O request.
recurs, contact EMC Support for assistance.
DLm679E Cannot set FIPS mode for encryption
Description: The initialization of FIPS-mode-certified encryption

failed.
System action: The DLm application initialization terminates.
recurs, contact EMC Support for assistance.
DLm680E Device <devicename>, Volume <volser>: internal I/O error

while (un)reserving volser '%s'
Description: An error occurred while performing a distributed lock

or unlock on a virtual tape.
I/O request.
DLm681E Device <devicename> <path-type> path 'path' specified,

but no valid <path-type> license file exists.
Description: A Centera path was encountered, but the DLm is not

licensed for Centera support.
System action: The DLm does not accept mount requests using
Centera Paths.
User action: If the DLm should be licensed to support Centera usage,

System Messages
DLm682E Device <devicename> unable to initialize VirtualFile path

'path'
Description: An error occurred while X.

System action: The DLm does not accept mount requests using the
indicated Centera Path.
User action: Ensure that the indicated Centera Path is correctly
configured. If the problem persists, contact EMC Customer Support
for assistance.
DLm683W Nothing to recover for tape <volser>; cleaning up.
Description: A previous I/O failure caused recovery of a

partially-written tape to be attempted, but no recovery was possible.
System action: The DLm cleans up the remnants of the unrecoverable
tape.
User action: None.
DLm684E Device <devicename>, Volume <volser>: could not validate

SL tape
Description: There was a problem in the format of the tape headers in

a standard labeled tape.
I/O request.
DLm685E unable to initialize path 'pathname': error message
Description: An error occurred while setting the specified path.

System action: The path is not changed.
System Messages
DLm701E Device <devicename> Data Exchange Feature not licensed,

mount 'volser' ignored
Description: Mounting of a flat file (data exchange) volser was

requested, but this DLm is not licensed for flat file support.
User action: Only flat files can start with the volser prefix \BFL\. If
you want to use the DLm flat file/data exchange feature, you must
obtain a license for this feature. Contact EMC Customer Support for
assistance.
DLm704E Device <devicename> Error deleting unused flat volume

<volser>: error message
Description: The specified volume was created in response to a flat

tape mount request. Because it was unloaded without ever having
been written to, the DLm tried to delete it. An I/O error occurred
during the attempt to delete.
System action: The volume may or may not been deleted from the
tape library.
error that occurred. Correct the error.
DLm711I Device <devicename> Unused flat volume <volser> deleted
Description: The specified volume was created in response to a flat

tape mount request, but it was unloaded without ever being written
to.
System action: The volume is deleted from the DLm disk.
User action: None.
DLm714E Device <devicename> too many trailer labels!
Description: The DLm received too many labels to store (more than
legally allowed for standard label processing) while processing the
trailer labels for a standard labeled flat file.
System action: The Host write is canceled with a unit check.
User action: Correct the condition that is causing too many labels to
be written.

System Messages
DLm715E Device <devicename> data in trailer labels!
Description: The DLm received a non-label data record while

processing the trailer labels for a standard labeled flat file.
System action: The Host write request is canceled with a unit check.
User action: Correct the condition that is causing the invalid label or
data to be written within the trailer labels.
DLm720E Device <devicename> command in flat file
Description: The DLm application received a tape positioning

command from the Host while positioned within the data area of a
flat file.
System action: The Host command is canceled with a unit check.
User action: Spacing commands are not allowed within flat files;
correct the condition that is causing the spacing within the file.
DLm724E Device <devicename> read backwards/previous in flat file
Description: The DLm application received a Read Backwards or

Read Previous command from the Host while within the data area of
a flat file.
System action: The Host command is canceled with a unit check.
User action: Reading backwards is not allowed in a flat file; correct
the condition that is causing the backwards read within the file.
DLm766E Device <devicename> file 'filename' already exists [as

scratch]
Description: The Host wrote a HDR1 label to a flat file volume, and
the DLm attempted to change the volume's filename from
VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where
DATASETNAME is the data set name from the HDR1 label), but the
file VOLSER.DATASETNAME.FLAT already exists in the tape
library.
User action: Either delete or rename the existing file in the tape
library before writing a flat file with the same name, or use a different
data set name in the JCL for the new output file.
System Messages
DLm767E Device <devicename> error renaming volume <volser>

(oldfilename) to newfilename; <error message>
Description: The Host wrote a HDR1 label to a flat file volume, and
the DLm attempted to change the volume's filename from
VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where
DATASETNAME is the data set name from the HDR1 label), but an
error occurred while renaming.
User action: See the 'error message' portion of this message to
determine the reason for the error.

System Messages
DLm781W Device <devicename> is open as a read only tape
Description: The volume on the specified device is mounted in

read-only mode.
System action: The tape is mounted in read-only mode.
User action: To write new volumes, make sure the tape is correctly
mounted and is write-enabled.
DLm782E Command <command> not supported on Physical Tape Device

<devicename>
Description: The requested (rewind, unload, unready, ready)

command is not supported on real physical tape devices.
User action: Operator intervention is required to execute this
command at the physical tape device.
DLm783W Device <devicename> tape door is open
Description: The tape door is open.

System action: The system cannot mount the tape.
User action: Physically close the tape door.
DLm785E Device <devicename> Read Buffer too small
Description: The data block read from the tape is larger than the
maximum supported by DLm.
System action: The DLm returns an error status (equipment check) to
the Host.
User action: The tape is not compatible with the DLm because of the
large blocks it contains.
DLm786E Device <devicename> Failed to Open <device path>
Description: The physical tape device is not accessible.

System action: Application does not communicate with this tape
device.
User action: The tape most likely requires manual intervention.
System Messages
DLm787E Device %s Unable to set Compression %s errno %s
Description: The physical tape device did not accept the

compression command.
System action: Data written to this tape device is not compressed.
DLm788E Device <devicename> SCSI block #nnn too large (xxxxxx) to

handle <operation> (max=yyyyyy)
Description: The DLm has received a tape block with size ('xxxxxx')
that is larger than the maximum tape blocksize ('yyyyyy') that can be
presented to the SCSI Tape Device.
User action: Correct the Host application to send a blocksize that can
be handled by the tape drive.
DLm789I Device <device name> does not support the SCSI <cmd>
command
Description: The physical tape drive does not support the specified
command.
System action: DLm will continue, but the specified command
cannot be performed.
User action: Determine that the attached device is a supported device
type.

System Messages
DLm790I ST driver version info: <description>
Description: Displays the version number of the st (SCSI tape) driver.

User action: None.
DLm791I SMC driver version info: <description>
Description: This message displays the version number of the smc

(SCSI Media Changer) driver.
User action: None.
DLm795I Device <devicename> ready
Description: Displays when a SCSI tape drive assigned to a DLm

virtual tape device transitions from not ready to ready.
System action: A "Ready" interrupt is sent to the host.
User action: None.
DLm796I Device <devicename> offline and not ready
Description: Appears when a SCSI tape drive assigned to a DLm

virtual tape device transitions from ready to not ready.
System action: None. The drive appears not ready to the host.
User action: None.
System Messages
DLm797E Device devicename can not unload during tape activity
Description: This message displays when an operator requests a tape

unload while physical tape drive activity is in progress.
User action: Retry the command when tape activity has completed.
DLm801I Trace buffers saved to disk
Description: Normal response to the Save Trace command.

System action: All trace buffers currently held in memory have been
written to disk.
User action: None.
DLm804I Writing corefile to 'filename.gz' ...
Description: Normal response to the ' SAVE COREFILE' command.

System action: A diagnostic core file of the virtual tape application
will be saved to the specified file.
User action: None.
DLm805I corefile 'filename.gz' saved to disk
Description: Normal response to the 'SAVE COREFILE' command.

System action: A diagnostic core file of DLm has been to the specified
file.
User action: None.
DLm810E Command failed: command: <error message>
Description: The DLm received an error while trying to execute the

specified command in an external shell.
System action: The system continues running without executing the
specified external command.

System Messages
DLm811E Parameter n 'value' is not a valid FILENAME=parameter
Description: Syntax error on an operator command.

syntax.
DLm812E <command> feature is not licensed
Description: The specified command requires a feature that is not

licensed for use on this DLm.
licensed feature.
DLm813E Command <command> is not permitted
Description: The specified command is not permitted by the DLm

configuration.
User action: Refer to the EMC Disk Library for mainframe User Guide
for instructions about how to activate this command.
DLm814E Parameter #n 'keyword=value' is not a valid VOL= or DEV=

parameter

syntax.
DLm815E Parameter n 'value' is not a valid VOLSER or synonym

syntax.
System Messages
DLm816E No free device available to mount volume <volser>
Description: The operator LOAD command specified any drive ('*'),

but there was no free drive.
User action: Wait for a drive to be free, then retype the command.
DLm817E Parameter n 'keyword=value' is not a valid parameter

syntax.
DLm818E Invalid device name 'value' specified (too long)
Description: The <devicename> specified in an operator command is

invalid.
syntax.
DLm819E Unknown device name 'value' specified
Description: The <devicename> specified in an operator command is

invalid.
syntax.
DLm820E No devicenames match 'devicenames'

syntax.

System Messages
DLm825E Volume <volser> is currently mounted on <devicename>,LOAD

Command ignored
Description: The operator LOAD command specified a drive that

currently has a virtual volume loaded.
User action: Wait for the specified drive to be free, or choose a
different drive.
DLm826W Device <devicename> is already Ready/NotReady,

READY/UNREADY command ignored
Description: The operator Ready or Unready command specified a

drive that is currently in that state.
User action: Specify the correct device and desired state in the
command.
DLm828E Nothing is currently mounted on <devicename>, command

command ignored
Description: The operator Unload, Rewind, Ready, or Unready

command specified a drive that does not currently have a tape
loaded.
User action: Specify the correct drive in the Unload, Rewind, Ready,
or Unready command.
DLm829E Device <devicename> is Ready, UNLOAD/REWIND/SET PATH

command ignored
Description: The operator Unload or Rewind or SET PATH

command specified a drive that is in the Ready state.
User action: If you want to manually unload or rewind or change the
path of a device you must make it UNREADY first.
System Messages
DLm830I Device <devicename> made Ready/Unready
Description: The operator Ready or Unready command completed

successfully.
System action: The specified drive is now in the designated state.
User action: None.
DLm831E Invalid <parameter> value specified

syntax.
DLm832E Invalid <parameter> value specified
Description: Syntax error on an operator command. Cannot set the

same SCSI path to all devices.
syntax.
DLm834I Device <devicename> tracelevel changed from n to n
Description: Normal response to an operator Set Trace ... DEV=

command.
System action: The specified trace level was changed.
User action: None.
DLm836I ALL tracelevels set to n
Description: Normal response to an operator Set Trace ... ALL

command.
System action: The specified trace level was changed.
User action: None.

System Messages
DLm839E unable to assess space for <path> (nnn)
Description: The DLm was unable to obtain status information about

the specified tape library subdirectory, in response to the \Query
Space\ command.
System action: This tape library subdirectory is skipped in the
\Query Space\ output.
User action: Make sure that a valid tape library directory is specified
in the configuration file for this device, that the directory is currently
mounted and accessible, and that all subdirectories with in the tape
library are mounted and accessible. If the problem persists, contact
EMC Customer Support for assistance.
DLm841I System tracelevel is currently set to n
Description: The tracelevel is displayed in response to the Query All

command.
User action: None.
DLm842I System debuglevel is currently set to n
Description: The debuglevel is displayed in response to the Query

All command.
User action: None.
DLm844I Device <devicename> OSADDR set to 'XXXX'
Description: The OSADDR value for this device has been changed.
The OSADDR value is used with the VSE BTIMOUNT program to
identify the name by which VSE knows a DLm application virtual
device.
System action: The new OSADDR value will be used to find a virtual
device when BTIMOUNT requests a mount on a specific drive by
name, and DLm will report the OSADDR value to BTIMOUNT when
it completes a mount on ANY drive.
User action: None.
System Messages
DLm845I Device <devicename> GROUP set to 'n'
Description: The GROUP value for this device has been changed.
The GROUP value is used with the VSE BTIMOUNT program to
identify drives that belong to the same VSE group as the control
drive.
System action: The new GROUP value will be used to find a virtual
device when BTIMOUNT requests a mount on ANY drive.
User action: None.
DLm846I AWS maps usage default value set to OFF
Description: An AWS map will not be written to an AWS file.

User action: None.
DLm847I Confirm stored CRC value in awshdr default value set to

OFF
Description: With the value set to off, the stored CRC value in the
aws header will not be confirmed.
User action: None.
DLm848I Device <devicename> maximum volume size changed from

<oldsize> to <newsize>
Description: The operator SET SIZE= command was accepted for

the specified device.
System action: The maximum volume size was changed for the
specified device. The SIZE is changed effect immediately.
User action: None.
DLm849I Storing CRC value in awshdr default value set to OFF
Description: With the value set to off, the CRC value will not be
stored in the aws header.
User action: None.

System Messages
DLm850I Device <devicename> Label default changed from 'x' to 'x'
Description: The operator SET LABEL= command was accepted.

System action: The default label value was changed for the specified
device.
User action: None.
DLm852I Full-erase set ON
Description: The DLm has been configured to perform a more

extensive erasure of data when a erasing of a virtual tape volume is
requested. Most tape managers expect to find the complete original
header label set on every scratched tape, but under some
circumstances (for example, on a Unisys system), the full label set is
not desirable.
System action: By default, when erasing a virtual tape volume the
VOL1 label, all HDRn labels, and one tapemark are retained. When
the full erase option is set, only the VOL1 and two tapemarks are
retained.
User action: None.
DLm853I Pending Mount Fairness (PMFAIR) set to <nnn>
Description: The PMFAIR option allows the DLm to be configured to

delay read and write I/Os while a tape mount operation is in
progress. This can speed up tape mounts on a heavily loaded system,
at a slight expense to overall throughput during tape mount
operations. This option is off by default.
System action: Every read and write I/O is delayed by <nnn>
milliseconds while a tape mount is in progress.
User action: None.
DLm854W Requested path already assigned to device <devicename>
Description: The device path requested is already assigned to this

device.
System action: The path is not changed from the previous value.
System Messages
DLm855E SCSI Tape Device <device path> does not exist
Description: The device path requested does not exist.

DLm856I nn scratch synonyms: volser,volser,...
Description: Displays any scratch synonyms that are defined in the

configuration file.
User action: None.
DLm857E Error Invalid Path
Description: The Operator selected a path that requires a feature that

is not licensed for use on this DLm.
licensed feature.
DLm858I Device <devicename> Data path deferred change from

'oldpath' to 'newpath'
Description: The operator SET PATH= command was accepted, but

the specified device currently has a volume mounted.
System action: The new data path takes effect immediately after the
current volume is unmounted.
User action: None.

System Messages
DLm859I Device <devicename> Data path changed from 'oldpath' to

'newpath'
Description: The operator SET PATH= command was accepted.

System action: The new data path takes effect immediately on the
specified virtual tape drive.
User action: None.
DLm860E PATH= is no longer supported; use DEV= to specify the

tape library
Description: The operator INITIALIZE command specified the

obsolete PATH= parameter. Older versions of the DLm supported a
choice between using PATH= or DEVICE= to designate the tape
library where the volumes would be initialized. The PATH=
parameter is no longer supported, and DEV= is required.
System action: The INITIALIZE command is ignored.
User action: Do not specify PATH=, but use the required DEVICE=
parameter on the INITIALIZE command. See HELP INITIALIZE for
more information.
DLm861E Tape library path not changed
Description: The SET PATH command has failed.

DLm862E Invalid volser <volser> for volume initialization
Description: The INITIALIZE command specified a VOLSER of

'SCRTCH' or 'PRIVAT,' or beginning with 'BFL.' BFLxxx volsers are
reserved for Data Exchange (\flat\) volumes, which cannot be
pre-initialized on the DLm. Scratch volumes should be initialized
with the actual volser desired, not by using the word 'SCRTCH' or
'PRIVAT.'
User action: Specify a valid volser that does not start with the prefix
'BFL' or ‘SCRTCH’ or ‘PRIVAT’.
System Messages
DLm863E SCSI Tape path already in use
Description: The SET PATH command has failed.

User action: Set PATH= to a valid SCSI tape path that is not already in
use.
DLm864E You can only create <nnn> volumes starting from <volser>
Description: The INITIALIZE command COUNT= parameter was

too big for the specified starting volser.
System action: The INITIALIZE command is rejected.
User action: Use the HELP INIT command for more information
about using the INITIALIZE command. Make sure that the specified
COUNT value would not cause the numeric portion of the volser to
overflow or the first two characters of the volser to change.
DLm865E File '<filename>' [non-]scratch volume already exists
Description: While processing the INITIALIZE command, the DLm

found that the volume it is attempting to create already exists in the
tape library, as either a scratch or non-scratch volume.
System action: The new scratch volume is not created, and the
original volume is not changed.
User action: Be careful to not create new scratch volumes in the range
of existing volumes.
DLm866E File/Directory '<filename>' open failed, err=<nnn>:

<error message>
Description: An I/O error occurred while attempting to create a new

scratch volume.
System action: The specified new scratch volume has not been
created.
User action: Se the `error message' portion of this message for an
explanation of the error. Correct the error and try initializing the
volumes again.

System Messages
DLm867E Error writing to <filename>: <error message>
Description: An I/O error occurred while attempting to create a new

scratch volume.
System action: The specified new scratch volume has not been
created.
User action: See the `error message' portion of this message for an
explanation of the error. Correct the error and try initializing the
volumes again.
DLm868E Too many errors have occurred, terminating
Description: Multiple errors have occurred during processing of the

operator INITIALIZE command.
System action: One or more new scratch volumes may have been
created before the maximum number of errors occurred.
User action: Review the messages prior to this one to determine the
nature of the errors, and correct the errors and retype the correct
INITIALIZE command.
DLm869I nn Standard/ANSI-labeled volumes initialized
Description: The DLm has completed an INITIALIZE command.

System action: The specified number of new scratch volumes have
been created.
User action: None.
DLm870E Device <devicename> Initializations not allowed in

<tapelib>
Description: The tape library type assigned to this device does not
support tape initialization. Volumes can be initializedonly in tape
libraries on direct-access filesystems.
User action: Specify a DEVICE=device that has a tape library defined
on a valid direct-access filesystem.
System Messages
DLm871I AttentionCount set to <value>
Description: The configurable ATTENTIONCOUNT parameter has

been set as shown.
System action: The ATTENTIONCOUNT parameter defines how
many times the DLm should retry sending an asynchronous \Ready\
interrupt should it be rejected by the channel or Host. The default
number of retries is 45.
User action: None.
DLm872E Invalid SNn= value <value> (incorrect length)
Description: The operator SET command contained an incorrect

serial number. The new serial number must be exactly 12 characters
long.
System action: The SET command is ignored.
User action: Specify a valid value in the SET command. Use the
HELP command to see the proper command syntax.
DLm873I Attention set to <value>
Description: The configurable ATTENTION parameter has been set

as shown.
System action: The ATTENTION parameter defines which channel
paths the DLm should send a \Ready\ interrupt to when a virtual
tape drive comes ready. The possible values are:
◆ ALL — The interrupt is sent to every channel path established for
this device.
◆ NONE — No interrupt is sent to any Host when a drive comes
ready.
◆ ASSIGNED — The interrupt is sent to every channel path which
has an Assignment in effect. An Assignment is typically made
when a Host VARYs a drive online. This is the default action.
◆ PATHGROUP — The interrupt is sent to every channel path
which currently has a Path Group ID (PGID) set. A PGID is
typically set when a Host VARYs a path online.
◆ REQUESTER— The interrupt is sent only to the path from which
the Load Display mount request was received.
User action: None.

System Messages
DLm874E Setting <parameter> requires a DEVICE= parameter too
Description: The operator SET command was typed without

specifying a specific device to be set.
System action: The <parameter> specified is ignored.
User action: This particular SET command <parameter> requires
that a DEVICE= parameter be specified; retype the SET with a
specific DEVICE specified. Use the HELP command to see the proper
command syntax.
DLm875I Device <devicename> VOL= prefix changed from 'xx' to 'yy'
Description: The operator SET VOL= command was accepted.

System action: The new volume serial prefix value takes effect
immediately on the specified virtual tape drive.
User action: None.
DLm876I Unknown volumes will be treated as Scratch requests
Description: Normally, a request for a non-existent volume results in

message DLm454E and the drive remains Not Ready. However, this
DLm has been configured to treat mount requests for non-existent
volumes as if the request were for a scratch volume. This option only
applies for devices connected to a Unisys mainframe.
System action: The DLm proceeds as if a SCRTCH volume was
requested when a non-existent volume is requested, but only if the
device is connected to a Unisys mainframe at the time.
User action: None.
System Messages
DLm877I Non-supervisor Load Displays disallowed/allowed
Description: The DLm was configured or SET to allow Load Display

commands to be accepted by the DLm even when the Host has set
Supervisor Inhibit (such as when a normal user application is
running in z/OS). The default mode for the DLm is to disallow Load
Displays when Supervisor Inhibit is set by the Host, just like a real
tape drive would.
System action: If the message says 'allowed,' all Load Display
commands is accepted by the DLm at any time. If the message says
'disallowed,' Load Display commands are rejected by the DLm
whenever they are inhibited by the Host.
User action: If you need to configure the DLm to allow Load
Displays from your own application programs, contact EMC
Customer Support for more assistance. Otherwise, leave this DLm
feature in the default state.
DLm878I <feature> enabled
Description: A special DLm debugging feature was enabled through

configuration or with the SET command.
System action: The effect depends on the feature.
User action: Special debugging features should only be enabled
under direction of EMC Customer Support.
DLm879I [Device <devicename> / ALL devices] quiesced/unquiesced
Description: The QUIESCE or UNQUIESCE command was typed.

System action: A quiesced device is in a state where it does not
accept any new tape mounts until it is explicitly unquiesced (or until
the DLm is restarted). If a drive has a volume mounted at the time it
is quiesced, it continues to function completely normally; it does not
accept another mount after the current volume is unloaded.
User action: None.

System Messages
DLm880I GroupAccess set to 'R'
Description: By default, virtual tape files created by the DLm are

only accessible by the 'vtape' user. This message signifies that the
DLm is currently configured to allow other members of the 'vtape'
user group to have Read access to the virtual tape files created by the
DLm.
System action: All tapes created while this option is set to have group
accessibility.
User action: Reconfigure the DLm if you do not want other members
of the 'vtape' group to have access to virtual tape files. Files that were
created while this option was set to continue to be accessible by all
members of the 'vtape' group unless the file permissions are
manually changed by the administrator.
DLm881I OtherAccess set to 'R'
Description: By default, virtual tape files created by the DLm are

only accessible by the 'vtape' user. This message signifies that the
DLm is currently configured to allow any user to have Read access to
the virtual tape files created by the DLm.
System action: All tapes created while this option is set to have
global accessibility.
User action: Reconfigure the DLm if you do not want everyone to
have access to virtual tape files. Files that were created while this
option was set to continue to be accessible by anyone unless the file
permissions are manually changed by the administrator.
DLm882I Disk usage warning percent changed from nn% to nn%
Description: The operator SET WARNING= command was

accepted.
System action: The new disk usage warning value takes effect
immediately.
User action: None.
System Messages
DLm883I /var usage warning percent changed from nn% to nn%
Description: The operator SET VARWARNING= command was

accepted. The VarWarning value is the percentage of usage of the
/var filesystem at which point the system will begin warning that
/var space utilization is high.
System action: The new disk usage warning value takes effect
immediately.
User action: None.
DLm884I Disk space RECOVERAMT changed from nn% to nn%
Description: The operator SET RECOVERAMT= command was

accepted.
System action: The new disk space recovery amount takes effect
immediately.
User action: None.
DLm885E EXIT[!] and RESTART[!] are no longer supported.
Description: These commands are no longer supported.

User action: To start/stop the VT service, use the command 'vtd' at an
operating system prompt.
Lm886I Disk space RECOVER percent changed to nn%
Description: The operator SET RECOVER= command was accepted.

System action: The new disk space recovery threshold takes effect
immediately.
User action: None.

System Messages
DLm887I Channel adapter <n> serial number override set to

<xxxxxxxxxxxx>
Description: The operator SET SNn= command was accepted.

System action: The hardware serial number reported by the DLm to
the Host for channel adapter <n> has been set to the specified
override value. If <xxxxxxxxxxxx> is blank, the override has been
removed and the DLm reports the actual hardware serial number
once again.
User action: None. Use the SET SNn= command to remove the
override.
DLm888W Warning: New serial number contains lower case letters!
Description: The operator SET SNn= command was accepted, but

the serial number specified contained one or more lowercase
alphabetic characters.
System action: The specified serial number is accepted, and is
reported to the Host EXACTLY as you specified.
User action: None, unless you really meant to type uppercase letters
in the serial number. In that case, type the command again with the
proper value.
DLm889E Encryption key n is not available
Description: The specified encryption key is not installed.

System action: The ENCRYPTKEY value is not changed from the
previous setting.
User action: Specify a valid, installed key in the SET ENCRYPTKEY
command.
DLm890E Help has no additional information for 'something'
Description: The DLm command 'HELP something' was typed, but

'something' is not a valid DLm command or message number.
User action: Use the HELP command alone to see a summary of the
DLm commands available.
System Messages
DLm891E Invalid command syntax
Description: The preceding operator command was invalid.

syntax.
DLm893E <feature> feature not yet supported
Description: The preceding operator command used a DLm feature

that is not supported.
syntax.
DLm894I PenaltyUp/PenaltyDown value changed from <nn> to <nn>
Description: The operator SET PENALTYUP= or

PENALTYDOWN=command was accepted. The PenaltyUp value is
used to decrease the chance that a filesystem will be selected for the
next scratch mount; it is applied every time a filesystem is selected for
a scratch mount. PenaltyDown is used to reduce the penalty every
time a filesystem is NOT selected for a scratch mount.
System action: The new penalty value takes effect immediately.
User action: None.
DLm895I Read-back write verification set ON/OFF
Description: The operator SET WRITEVERIFY= command was

accepted.
System action: When the Write Verify feature is ON, after every
\"WRITESYNC\" amount of data has been written to a virtual tape
file, the data will be read back to verify its integrity. If an error is
found during the verification, a unit check is returned to the current
Host write CCW that triggered the verify action.
User action: None.

System Messages
DLm896I /var usage debugging limit changed from <nn> to <nn>
Description: The operator SET VARDEBUGLIMIT= command was

accepted. The VarDebugLimit is the number of bytes remaining on
the /var filesystem at which point the system will automatically turn
off any debugging mode that generates console messages which go to
/var.
System action: The new threshold takes effect immediately.
User action: None.
DLm897E Unexpected keyword parameter n 'keyword=value'
Description: Syntax error on an operator Load command.

syntax.
DLm898E Unknown parameter n 'something'
Description: Syntax error on an operator Load command.

syntax.
DLm901E Error reading Keyboard Data: <error message>
Description: An I/O error has occurred while reading a command

from the keyboard.
System action: The DLm application terminates.
DLm902E Zero Bytes read from Keyboard
Description: An I/O error has occurred while reading a command

from the keyboard.
System Messages
DLm908E Error formatting message for SNMP trap: error message
Description: An error has occurred while formatting a message

before evaluation by the SNMP agent.
System action: The message is sent to the SNMP agent as is, but
might not be perfectly formatted.
DLm909E Error writing message to console
Description: An error has occurred while writing a message to the

console.
System action: The following message may not be correctly
formatted.
DLm910W Device <devicename> <deliberate error message>
Description: This message immediately precedes a deliberate error

caused by the DLm, caused by setting a debugging mode on the DLm
for testing purposes.
System action: A deliberate error of some kind follows this message.
User action: None. Do not be surprised by the error that follows. If
you get this message unexpectedly, contact EMC Customer Support
for assistance.

for assistance.

System Messages

for assistance.
DLm950I Message from Host
Description: A Host program has sent this message to be displayed

on the DLm Console.
User action: None.
DLm951I Message from another program
Description: An external program has sent this message to be

displayed on the DLm Console.
User action: None.
DLm952E Unable to get hostname
Description: The application was unable to get the hostname of the

system
System action: Unable to continue.
User action: Verify thet the hostname of the system is set correctly.
DLm953I DD Lock Parameter Set
Description: The application has been configured for Volser Locking.

System action: Use external lock files when locking a volser (files:
.lkVOLSER)
User action: None.
System Messages
DLm954E Unable to open file <filename> <error>
Description: The system was unable to open a file.

System action: The operation being done on the file will be
terminated.
User action: Verify the permissions of the file.
DLm955E Error reading file <filename> <error>
Description: The system was unable to read a file.

System action: The contents of the file will be ignored.
User action: Verify the permissions of the file.
DLm956E Error closing <description> <filename>: <error> (will

retry <count> more times)
Description: An error occurred while closing a file

System action: The close will be retries <count> more times
User action: Check the directory where the file is mounted for
problems.
DLm971E Error closing input/output fifo: <filename>
Description: The DLm received an error while closing the specified

file. This error can only happen during program termination.
System action: The DLm continues to shut down.
for assistance.
DLm972E Error deleting input/output fifo: <filename>
Description: The DLm received an error while closing the specified

file. This error can only happen during program termination.
System action: The DLm continues to shut down.
for assistance.
DLm980E Program Check error in thread nnnn (processname),

state=XXXXXXXX
Description: An internal program error has occurred.

System Messages
System action: The DLm attempts to shut down all virtual devices.
All devices are taken offline to the Host, and the DLm application
terminates.
DLm981E Program Check type 'error type'
Description: An internal program error has occurred.

System Messages
DLm990I Shutting down this application...
Description: The DLm application is terminating.

User action: None.
DLm991E Error shutting down device <devicename>
Description: An error occurred while attempting to shut down a

virtual device.
System action: The DLm application continues to shut down.
DLm992W <n> volumes mounted; use vtd to force shutdown
Description: The operator 'EXIT' or 'RESTART' command was

entered while one or more virtual tape drives had a volume mounted.
User action: Before shutting down, wait for all Host applications to
finish and unload their tapes. If for some reason the Host cannot
unload all of the DLm devices, manually unload all virtual tape
volumes with the DLm 'UNLOAD' command. If, for some other
reason, the DLm 'UNLOAD' command cannot unload all the DLm
devices, the vtd force command will force a shutdown even while
tapes are mounted.

System Messages
Call home messages

This section lists the EMC Call home messages.
Mgmt001E ACP1 is not directly accessible from the base VNX primary
Control Station.
Description: Either ACP1, switch-1, or a related network connection

(like a cable or port) is down. This prevents the Data Domain storage
system (if available) from sending alerts to EMC and can cause other
connectivity issues.
System action: None
User action: Contact EMC Customer service to troubleshoot the
issue.
Mgmt002E ACP2 is not directly accessible from the base VNX primary
Control Station.
Description: Either ACP2, switch-2, or a related network connection

(like a cable or port) is down.
System action: None
User action: Contact EMC Customer service to troubleshoot the
issue.
System Messages
EMCvts messages
EMCvts is the script that starts the DLm application. The following
messages may be displayed by EMCvts while starting the DLm
application.
EMCvts: Interface #n fw version xxxx newer than filename version yyyy

Not loading older firmware
The script has determined that the firmware on the channel adapter
card (xxxx) is actually newer than the firmware file found on the
system disk (yyyy). The adapter firmware not be changed.
EMCvts: Interface #n fw version xxxx older than filename version yyyy

Loading newer firmware
The script has determined that the firmware on the channel adapter
card (xxxx) should be updated to a newer version found on the
system disk (yyyy), and is doing so.
EMCvts: Interface #n fw version xxxx same as filename version yyyy

No need to reload firmware
The script has determined that there is no need to update the

firmware on the channel adapter card.
EMCvts: EMC directory "directory" does not exist!

The directory containing the EMC DLm executable files cannot be
located. Contact EMC Customer Support if you need additional
assistance in determining the cause of this problem.
EMCvts: Error loading firmware into slot nnnnnn (Interface n)!

An error occurred while attempting to load new firmware into the
channel adapter card. Contact EMC Customer Support if you need
additional assistance in determining the cause of this problem.
EMCvts: Error occurred. Press Enter to exit.

This message follows all other EMCvts error messages. Press Enter to
terminate the DLm application. Correct the preceding error, or
contact EMC Customer Support for additional assistance in
determining the cause of the problem.
EMCvts messages 367

System Messages
EMCvts: Error rebooting slot nnnnnn (Interface n) firmware!

An error occurred while rebooting the firmware on the channel
adapter card. Contact EMC Customer Support if you need additional
EMCvts: n channel adapters found

Information message to display the number of channel interfaces
found in the system.
EMCvts: No channel adapters installed, or drivers not presently loaded

No channel adapters could be located. Contact EMC Customer
Support if you need additional assistance in determining the cause of
this problem.
EMCvts: The "file EMCDR" or "EMCDIR environment variable" contains an invalid directory!
This message is always preceded by the message stating that the
directory containing the EMC DLm executable files cannot be
located. Contact EMC Customer Support if you need additional
EMCvts: unable to determine filename firmware version!

An error occurred while trying to determine whether the channel
adapter firmware should be updated. Contact EMC Customer
Support if you need additional assistance in determining the cause of
this problem.
EMCvts: unknown parameter: "xxxxxx"

The script was invoked with an invalid command line value. This
error should not occur if the DLm is started with the normal Desktop
icons.
System Messages
z/OS system messages

This section list the z/OS system messages, that is DLMCMD,
DLMLIB, DLMSCR, and DLMVER message, and its description.
DLMCMD messages are prefixed with DLC; DLMLIB messages are
prefixed with DLL; and DLMSCR messages are prefixed with DLS.
Note: The Help command does not support z/OS system messages.
DLMCMD messages
The following messages can be returned by the DLMCMD program
running on the mainframe.
DLC010I I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX
An I/O error occurred on the DLMCMD control tape. See the CSW
and SENSE information and any additional messages on the z/OS
and controller consoles to resolve the problem.
DLC040I CONTROL PATH FAILED TO OPEN
DLMCMD was unable to open the DLMCTRL control tape. Check the
JCL and any additional messages on the joblog to resolve the
problem.
DLC050I LOG FILE FAILED TO OPEN
DLMCMD was unable to open the DLMLOG log file. Check the JCL
and any additional messages on the joblog to resolve the problem.
DLC060I COMMAND FILE FAILED TO OPEN
DLMCMD was unable to open the input DLMCMD file. Check the
JCL and any additional messages on the joblog to resolve the
problem.
DLC070I ENTER COMMAND
The PARM=WTOR parameter told DLMCMD to read input from the

console. Type a command to send to the controller, or END to
terminate DLMCMD.
z/OS system messages 369

System Messages
DLMLIB message
The following message can be returned by the DLMLIB program
DLL100I INVALID VOLSER xxxxxx SPECIFIED
An invalid volser was specified in the input file. Correct the input
and rerun.
DLMSCR messages
The following messages can be returned by the DLMSCR program
DLS010I I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX
The control tape that sends scratch requests to the controller had an
I/O error. Check to make sure the controller is still running. If this is
the case use the CSW and SENSE provided to correct the problem.
DLS012I UNEXPECTED HEADER IN SCRATCH REPORT
While processing the scratch report DLMSCR found a header it not

expecting. First make sure that the TYPE parameter is correct for the
scratch report you are running. If so make sure the scratch report is of
the correct format.
DLS020I NO VALID SCRATCH REQUESTS PROCESSED
DLMSCR processed the entire scratch report and found no valid

scratch requests. First check the PREFIX and PREFIXLN parameters
to make sure they correctly match the tape prefixes used on the VTE
controller. If they are correct make sure that the scratch report
contains tapes with those prefixes.
DLS030I INPUT SCRATCH REPORT FAILED TO OPEN
The DLMSCR input scratch report failed to open. Check the DD

statement for the DLMSCR input file and make sure it refers to a
valid scratch report file.
System Messages
DLS031I INPUT SCRATCH REPORT NOT RECFM=F OR FB
The scratch report, which is created by the customer's TMS, must

have a LRECL of 133 and a RECFM of F or FB.
DLS040I CONTROL PATH FAILED TO OPEN
The DLMSCR control tape failed to open. Make sure the controller is
up and running and the unit address used for the DLMSCR control
tape is a valid controller device and has been varied online to the
mainframe.
DLS050I LOG FILE FAILED TO OPEN
DLMSCR maintains a log file with all the error and informational
messages from any DLMSCR runs. Check the mainframe job log to
determine why it did not open properly.
DLS060I SORTIN FILE FALED TO OPEN
DLMSCR requires a sortin file when processing a Tivoli Storage

Manager (TSM) report.
DLS070I INPUT FILE IS NOT A NEW SCRATCH REPORT
DLMSCR requires the date on the Scratch Report that is created by

the customer's TMS to be today's date. This is to prevent the
inadvertent use of an old scratch report. Run a new scratch report.
DLS080I This is a request to free space from scratch tapes. Reply

YES to continue
DLMSCR requests operator intervention before it frees space from

scratched tapes. This is because after space is freed the data on
scratched tape cannot be retrieved.
DLS080I Did not receive a response of yes, scratched tapes will

not be erased.
DLS081I FREExxxxx NOT ALLOWED WITH TYPE RMMDV
RMMDV has its own format, See the documentation on RMMDV.
DLS100I NO INPUT PARAMETERS FOUND
DLMSCR requires at least the TYPE= parameter be configured. Check

the format of your input parameters.

System Messages
DLS110I NO type FOUND IN INPUT PARAMETERS
DLMSCR requires the TYPE= parameter. Check your input

parameters.
DLS111I UNKNOWN type FOUND IN INPUT PARMS
DLMSCR has found an incorrect TYPE= parameter. Check your input

parameters.
DLS120I Freespace not confirmed - terminating
DLS130I PREFIX LENGTH INVALID
The default for the PREFIXLN is 2. In most cases the customer using 2
for their prefix length. If the tape library resides on Centera a prefix
length of 1 is common. In that case PREFIXLN=1 should be coded.
Check your input parameters.
DLS140I SORT FAILED
The internal sort performed on a Tivoli Storage Manager (TSM)

report failed. See the preceding console messages for the reason.
DLS150I INVALID DEV SPECIFIED
The parameter specified in the DEV= field is < 3 or >4 characters, or

contains non-hexadecimal characters
DLS160I DEVICE NOT FOUND DURING UCBLOOK
The device specified on the DEV= parameter was not found in the
active configuration. Correct the parameter and retry.
DLS170I ERROR DURING UCB CAPTURE/UNCAPTURE
A failure occurred attempting to capture/uncapture a 24-bit UCB

address from a 31-bit one. Contact support.
DLS180I DRIVE IS ALREADY ALLOCATED or BOXED
The device specified on the DEV= parameter is either already in use

or is boxed and cannot be used. Select a different drive and retry the
job.
System Messages
DLS181I DRIVE HAS NO ONLINE PATHS
The device specified on the DEV= parameter has no online paths

available. Select a different drive and retry the job.
DLS190I DEBCHK FAILED
An internal DEBCHK macro returned a non-zero return code.

Contact EMC Customer Support.
DLMVER messages
DLV010I UTILITY VERSIONS (<z/os release level>):
This message is written to the file pointed to by the DLMLOG DD

card, or to the operator if the WTO parm is used. The execution
environment’s z/os release level is displayed within parentheses. The
release levels of the other DLm utilities follow the DLV010I header
line.
DLV050I LOG FILE FAILED TO OPEN
The file that the DLMLOG DD card points to failed to open, or no

DLMLOG DD card was present. Check the JOBLOG and JCL for the
reason, and resubmit the job. If no logfile is required, use
parm=’WTO’ to send the result to the operator instead of the logfile.

System Messages
VTEC errors that generate ConnectEMC events

DLm errors that generate ConnectEMC events are:
DLm015E DLm119E DLm326E DLm498E

DLm055E DLm226W DLm467E DLm812E
System Messages

VTEC errors that generate ConnectEMC events 375

System Messages
Index
Numerics QUIESCE 196

3480, 3490, or 3590 reboot 67
configure devices 85, 138 RESET CHANNEL ADAPTER 197
Direct Tape 108 REWIND 198
IDRC 150 SAVE TRACE 198
Load Display command 208 SET 198
Manual Tape Library 140 SHOW 202
real 139, 146 SNMP 202
size range 94 statfmt 214
UIM 146 STOP CHANNEL ADAPTER 203
Syntax 184
UNLOAD 203
A UNQUIESCE 204
ACP UNREADY 204
power down 73 z/OS operator 148
status indicators connect
FICON 28 FICON channel 26
awsprint library utility 117, 127 considerations
AWSTAPE 206 DDR 149
DFSMShsm 149
C RMM 157
Channel Command Words 208 TLMS 157
Command TMS 157
DFSMShsm 149 TSM 157
DISABLE 184 ZARA 158
ENABLE 184
EXPORT 184 D
HELP 186 Direct Tape 108
IMPORT 186 DLm
INITIALIZE 187 ASCII data/labels 209
LOAD 188 command 151, 152, 158
poweroff 67 compression 110
QUERY 189 ENTER command 159
Index
label type 94 DLMLIB 370

power down 67 DLMSCR 370
power up 57 EMC DLm 222
replication 120 EMCvts 367
tape drive mapping 108 format 222
utility version reporting 152 Format Control Byte 208
DLMCMD utility 158 number 222
DLMSCR utility 153 z/OS system 369
DLMVER utility 160
documentation, related 14
P
Dynamic Device Reconfiguration considerations
password
(DDR) 149
system 57
power down
E ACP 73
EMC publications 14 VNX 72
EMC support website 13 VTE 68
Powerlink website 13
F
FICON R
connection 26 replication
status indicators 28 copy 122
format creating 125
AWSTAPE 206 disaster recovery 126
Control Byte 210 disastory recovery 126
EMC DLm message 222 overview 120
Load display data 210 supported configurations 124
statfmt command 214 terminolgy 122
G T
GENSTAT utility 153 Tape
direct 108
export command 184
I
export/import utilities 111
indicators
import command 186
FICON 28
Tape Library unaccessible
DLm156W 249
L DLm400E 290
Library utility, awsprint 117
U
M utility
message DLm scratch 156
class 222 DLMCMD 158
DLm system 223 DLMSCR 153
DLMCMD 369 DLMVER 151
Index
GENSTAT 153 Z
z/OS
V compaction of the virtual tape data 150
VNX configuring the devices 138
halting 70 Load display message 208
power down 72 Missing Interrupt Handler 148
VTE operator command 148
configuring virtual device 85 utilities 151
power down 68
Index

DLM - User Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

DLM - User Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

EMC® Disk Library for mainframe

Published September, 2011

2 EMC Disk Library for mainframe Version 3.0 User Guide

Chapter 1 Overview of EMC Disk Library for Mainframe

Chapter 2 DLm Operations

EMC Disk Library for mainframe Version 3.0 User Guide 3

Chapter 3 DLm Administration

4 EMC Disk Library for mainframe Version 3.0 User Guide

DLm diagnostic reporting.............................................................. 113

Chapter 4 DLm Replication

Chapter 5 Mainframe Tasks

EMC Disk Library for mainframe Version 3.0 User Guide 5

DLm scratch utility program .................................................. 153

Chapter 6 Using DLm with Unisys

Chapter 7 z/OS Console Support

Appendix A Virtual Tape Operator Command Reference

6 EMC Disk Library for mainframe Version 3.0 User Guide

Appendix B AWSTAPE Information

Appendix C Load Display Command—CCW Opcode x'9F'

Appendix D Extract DLm statistics

EMC Disk Library for mainframe Version 3.0 User Guide 7

Appendix E System Messages

8 EMC Disk Library for mainframe Version 3.0 User Guide

EMC Disk Library for mainframe Version 3.0 User Guide 9

31 SNMP configuration .................................................................................... 114

10 EMC Disk Library for mainframe Version 3.0 User Guide

EMC Disk Library for mainframe Version 3.0 User Guide 11

12 EMC Disk Library for mainframe Version 3.0 User Guide

As part of an effort to improve and enhance the performance and capabilities

Note: This document was accurate as of the time of publication. However, as

EMC Disk Library for mainframe Version 3.0 User Guide 13

Related The following EMC publications provide additional information:

Note: A note presents information that is important, but not hazard-related.

14 EMC Disk Library for mainframe Version 3.0 User Guide

EMC Disk Library for mainframe Version 3.0 User Guide 15

Technical support — For technical support, go to EMC Online

16 EMC Disk Library for mainframe Version 3.0 User Guide

This chapter provides an overview of EMC Disk Library for

Overview of EMC Disk Library for Mainframe 17

Introduction to Disk Library for mainframe

18 EMC Disk Library for mainframe Version 3.0 User Guide

DLm6000 architecture and models

DLm6000 architecture and models 19

Figure 1 DLm6000 overview

20 EMC Disk Library for mainframe Version 3.0 User Guide

VTEC The VTEC is the subsystem that connects to an IBM or

Figure 2 Front view of the VTE

DLm6000 architecture and models 21

Figure 3 Rear view of a VTE

Note: You must connect both ACPs to your network.

22 EMC Disk Library for mainframe Version 3.0 User Guide

Figure 4 Front view of the ACP

Figure 5 Rear view of the ACP

DLm6000 architecture and models 23

Figure 6 24-port AT-9924TL switch

Figure 7 Fujitsu XG2000R switch

24 EMC Disk Library for mainframe Version 3.0 User Guide

Each Data Domain system contains:

Figure 8 DD890 Controller—Rear view

See Figure 18 on page 61 for the front view of a DD890 controller.

Table 1 DD890 stream count limits

Stream type Stream count limit

Backup Write streams 180